commit d59e3ef0e06d52453ba44d6c298a08334bc16ecf Author: Julien Palard Date: Mon Oct 17 21:42:06 2016 +0200 3.6: Initial commit diff --git a/about.po b/about.po new file mode 100644 index 00000000..837aca70 --- /dev/null +++ b/about.po @@ -0,0 +1,74 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/about.rst:3 +msgid "About these documents" +msgstr "" + +#: ../Doc/about.rst:6 +msgid "" +"These documents are generated from `reStructuredText`_ sources by `Sphinx`_, " +"a document processor specifically written for the Python documentation." +msgstr "" + +#: ../Doc/about.rst:15 +msgid "" +"Development of the documentation and its toolchain is an entirely volunteer " +"effort, just like Python itself. If you want to contribute, please take a " +"look at the :ref:`reporting-bugs` page for information on how to do so. New " +"volunteers are always welcome!" +msgstr "" + +#: ../Doc/about.rst:20 +msgid "Many thanks go to:" +msgstr "" + +#: ../Doc/about.rst:22 +msgid "" +"Fred L. Drake, Jr., the creator of the original Python documentation toolset " +"and writer of much of the content;" +msgstr "" + +#: ../Doc/about.rst:24 +msgid "" +"the `Docutils `_ project for creating " +"reStructuredText and the Docutils suite;" +msgstr "" + +#: ../Doc/about.rst:26 +msgid "" +"Fredrik Lundh for his `Alternative Python Reference `_ project from which Sphinx got many good ideas." +msgstr "" + +#: ../Doc/about.rst:32 +msgid "Contributors to the Python Documentation" +msgstr "" + +#: ../Doc/about.rst:34 +msgid "" +"Many people have contributed to the Python language, the Python standard " +"library, and the Python documentation. See :source:`Misc/ACKS` in the " +"Python source distribution for a partial list of contributors." +msgstr "" + +#: ../Doc/about.rst:38 +msgid "" +"It is only with the input and contributions of the Python community that " +"Python has such wonderful documentation -- Thank You!" +msgstr "" diff --git a/bugs.po b/bugs.po new file mode 100644 index 00000000..c3128270 --- /dev/null +++ b/bugs.po @@ -0,0 +1,155 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/bugs.rst:5 +msgid "Dealing with Bugs" +msgstr "" + +#: ../Doc/bugs.rst:7 +msgid "" +"Python is a mature programming language which has established a reputation " +"for stability. In order to maintain this reputation, the developers would " +"like to know of any deficiencies you find in Python." +msgstr "" + +#: ../Doc/bugs.rst:11 +msgid "" +"It can be sometimes faster to fix bugs yourself and contribute patches to " +"Python as it streamlines the process and involves less people. Learn how to :" +"ref:`contribute `." +msgstr "" + +#: ../Doc/bugs.rst:16 +msgid "Documentation bugs" +msgstr "" + +#: ../Doc/bugs.rst:18 +msgid "" +"If you find a bug in this documentation or would like to propose an " +"improvement, please submit a bug report on the :ref:`tracker `. If you have a suggestion how to fix it, include that as well." +msgstr "" + +#: ../Doc/bugs.rst:22 +msgid "" +"If you're short on time, you can also email documentation bug reports to " +"docs@python.org (behavioral bugs can be sent to python-list@python.org). " +"'docs@' is a mailing list run by volunteers; your request will be noticed, " +"though it may take a while to be processed." +msgstr "" + +#: ../Doc/bugs.rst:28 +msgid "`Documentation bugs`_ on the Python issue tracker" +msgstr "" + +#: ../Doc/bugs.rst:33 +msgid "Using the Python issue tracker" +msgstr "" + +#: ../Doc/bugs.rst:35 +msgid "" +"Bug reports for Python itself should be submitted via the Python Bug Tracker " +"(https://bugs.python.org/). The bug tracker offers a Web form which allows " +"pertinent information to be entered and submitted to the developers." +msgstr "" + +#: ../Doc/bugs.rst:39 +msgid "" +"The first step in filing a report is to determine whether the problem has " +"already been reported. The advantage in doing so, aside from saving the " +"developers time, is that you learn what has been done to fix it; it may be " +"that the problem has already been fixed for the next release, or additional " +"information is needed (in which case you are welcome to provide it if you " +"can!). To do this, search the bug database using the search box on the top " +"of the page." +msgstr "" + +#: ../Doc/bugs.rst:46 +msgid "" +"If the problem you're reporting is not already in the bug tracker, go back " +"to the Python Bug Tracker and log in. If you don't already have a tracker " +"account, select the \"Register\" link or, if you use OpenID, one of the " +"OpenID provider logos in the sidebar. It is not possible to submit a bug " +"report anonymously." +msgstr "" + +#: ../Doc/bugs.rst:51 +msgid "" +"Being now logged in, you can submit a bug. Select the \"Create New\" link " +"in the sidebar to open the bug reporting form." +msgstr "" + +#: ../Doc/bugs.rst:54 +msgid "" +"The submission form has a number of fields. For the \"Title\" field, enter " +"a *very* short description of the problem; less than ten words is good. In " +"the \"Type\" field, select the type of your problem; also select the " +"\"Component\" and \"Versions\" to which the bug relates." +msgstr "" + +#: ../Doc/bugs.rst:59 +msgid "" +"In the \"Comment\" field, describe the problem in detail, including what you " +"expected to happen and what did happen. Be sure to include whether any " +"extension modules were involved, and what hardware and software platform you " +"were using (including version information as appropriate)." +msgstr "" + +#: ../Doc/bugs.rst:64 +msgid "" +"Each bug report will be assigned to a developer who will determine what " +"needs to be done to correct the problem. You will receive an update each " +"time action is taken on the bug." +msgstr "" + +#: ../Doc/bugs.rst:73 +msgid "" +"`How to Report Bugs Effectively `_" +msgstr "" + +#: ../Doc/bugs.rst:72 +msgid "" +"Article which goes into some detail about how to create a useful bug report. " +"This describes what kind of information is useful and why it is useful." +msgstr "" + +#: ../Doc/bugs.rst:76 +msgid "" +"`Bug Writing Guidelines `_" +msgstr "" + +#: ../Doc/bugs.rst:76 +msgid "" +"Information about writing a good bug report. Some of this is specific to " +"the Mozilla project, but describes general good practices." +msgstr "" + +#: ../Doc/bugs.rst:82 +msgid "Getting started contributing to Python yourself" +msgstr "" + +#: ../Doc/bugs.rst:84 +msgid "" +"Beyond just reporting bugs that you find, you are also welcome to submit " +"patches to fix them. You can find more information on how to get started " +"patching Python in the `Python Developer's Guide`_. If you have questions, " +"the `core-mentorship mailing list`_ is a friendly place to get answers to " +"any and all questions pertaining to the process of fixing issues in Python." +msgstr "" diff --git a/c-api.po b/c-api.po new file mode 100644 index 00000000..f9657d5b --- /dev/null +++ b/c-api.po @@ -0,0 +1,15858 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/c-api/abstract.rst:7 +msgid "Abstract Objects Layer" +msgstr "" + +#: ../Doc/c-api/abstract.rst:9 +msgid "" +"The functions in this chapter interact with Python objects regardless of " +"their type, or with wide classes of object types (e.g. all numerical types, " +"or all sequence types). When used on object types for which they do not " +"apply, they will raise a Python exception." +msgstr "" + +#: ../Doc/c-api/abstract.rst:14 +msgid "" +"It is not possible to use these functions on objects that are not properly " +"initialized, such as a list object that has been created by :c:func:" +"`PyList_New`, but whose items have not been set to some non-\\ ``NULL`` " +"value yet." +msgstr "" + +#: ../Doc/c-api/allocation.rst:6 +msgid "Allocating Objects on the Heap" +msgstr "" + +#: ../Doc/c-api/allocation.rst:17 +msgid "" +"Initialize a newly-allocated object *op* with its type and initial " +"reference. Returns the initialized object. If *type* indicates that the " +"object participates in the cyclic garbage detector, it is added to the " +"detector's set of observed objects. Other fields of the object are not " +"affected." +msgstr "" + +#: ../Doc/c-api/allocation.rst:26 +msgid "" +"This does everything :c:func:`PyObject_Init` does, and also initializes the " +"length information for a variable-size object." +msgstr "" + +#: ../Doc/c-api/allocation.rst:32 +msgid "" +"Allocate a new Python object using the C structure type *TYPE* and the " +"Python type object *type*. Fields not defined by the Python object header " +"are not initialized; the object's reference count will be one. The size of " +"the memory allocation is determined from the :c:member:`~PyTypeObject." +"tp_basicsize` field of the type object." +msgstr "" + +#: ../Doc/c-api/allocation.rst:41 +msgid "" +"Allocate a new Python object using the C structure type *TYPE* and the " +"Python type object *type*. Fields not defined by the Python object header " +"are not initialized. The allocated memory allows for the *TYPE* structure " +"plus *size* fields of the size given by the :c:member:`~PyTypeObject." +"tp_itemsize` field of *type*. This is useful for implementing objects like " +"tuples, which are able to determine their size at construction time. " +"Embedding the array of fields into the same allocation decreases the number " +"of allocations, improving the memory management efficiency." +msgstr "" + +#: ../Doc/c-api/allocation.rst:53 +msgid "" +"Releases memory allocated to an object using :c:func:`PyObject_New` or :c:" +"func:`PyObject_NewVar`. This is normally called from the :c:member:" +"`~PyTypeObject.tp_dealloc` handler specified in the object's type. The " +"fields of the object should not be accessed after this call as the memory is " +"no longer a valid Python object." +msgstr "" + +#: ../Doc/c-api/allocation.rst:62 +msgid "" +"Object which is visible in Python as ``None``. This should only be accessed " +"using the :c:macro:`Py_None` macro, which evaluates to a pointer to this " +"object." +msgstr "" + +#: ../Doc/c-api/allocation.rst:69 +msgid ":c:func:`PyModule_Create`" +msgstr "" + +#: ../Doc/c-api/allocation.rst:70 +msgid "To allocate and create extension modules." +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:7 +msgid "API and ABI Versioning" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:9 +msgid "" +"``PY_VERSION_HEX`` is the Python version number encoded in a single integer." +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:11 +msgid "" +"For example if the ``PY_VERSION_HEX`` is set to ``0x030401a2``, the " +"underlying version information can be found by treating it as a 32 bit " +"number in the following manner:" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:16 +msgid "Bytes" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:16 +msgid "Bits (big endian order)" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:16 ../Doc/c-api/memory.rst:277 +#: ../Doc/c-api/memory.rst:414 ../Doc/c-api/structures.rst:129 +#: ../Doc/c-api/structures.rst:241 ../Doc/c-api/tuple.rst:145 +#: ../Doc/c-api/tuple.rst:168 +msgid "Meaning" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:18 +msgid "``1``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:18 +msgid "``1-8``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:18 +msgid "``PY_MAJOR_VERSION`` (the ``3`` in ``3.4.1a2``)" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:21 +msgid "``2``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:21 +msgid "``9-16``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:21 +msgid "``PY_MINOR_VERSION`` (the ``4`` in ``3.4.1a2``)" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:24 +msgid "``3``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:24 +msgid "``17-24``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:24 +msgid "``PY_MICRO_VERSION`` (the ``1`` in ``3.4.1a2``)" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:27 +msgid "``4``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:27 +msgid "``25-28``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:27 +msgid "" +"``PY_RELEASE_LEVEL`` (``0xA`` for alpha, ``0xB`` for beta, ``0xC`` for " +"release candidate and ``0xF`` for final), in this case it is alpha." +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:32 +msgid "``29-32``" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:32 +msgid "" +"``PY_RELEASE_SERIAL`` (the ``2`` in ``3.4.1a2``, zero for final releases)" +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:36 +msgid "Thus ``3.4.1a2`` is hexversion ``0x030401a2``." +msgstr "" + +#: ../Doc/c-api/apiabiversion.rst:38 +msgid "All the given macros are defined in :source:`Include/patchlevel.h`." +msgstr "" + +#: ../Doc/c-api/arg.rst:6 +msgid "Parsing arguments and building values" +msgstr "" + +#: ../Doc/c-api/arg.rst:8 +msgid "" +"These functions are useful when creating your own extensions functions and " +"methods. Additional information and examples are available in :ref:" +"`extending-index`." +msgstr "" + +#: ../Doc/c-api/arg.rst:12 +msgid "" +"The first three of these functions described, :c:func:`PyArg_ParseTuple`, :c:" +"func:`PyArg_ParseTupleAndKeywords`, and :c:func:`PyArg_Parse`, all use " +"*format strings* which are used to tell the function about the expected " +"arguments. The format strings use the same syntax for each of these " +"functions." +msgstr "" + +#: ../Doc/c-api/arg.rst:19 +msgid "Parsing arguments" +msgstr "" + +#: ../Doc/c-api/arg.rst:21 +msgid "" +"A format string consists of zero or more \"format units.\" A format unit " +"describes one Python object; it is usually a single character or a " +"parenthesized sequence of format units. With a few exceptions, a format " +"unit that is not a parenthesized sequence normally corresponds to a single " +"address argument to these functions. In the following description, the " +"quoted form is the format unit; the entry in (round) parentheses is the " +"Python object type that matches the format unit; and the entry in [square] " +"brackets is the type of the C variable(s) whose address should be passed." +msgstr "" + +#: ../Doc/c-api/arg.rst:31 +msgid "Strings and buffers" +msgstr "" + +#: ../Doc/c-api/arg.rst:33 +msgid "" +"These formats allow accessing an object as a contiguous chunk of memory. You " +"don't have to provide raw storage for the returned unicode or bytes area." +msgstr "" + +#: ../Doc/c-api/arg.rst:37 +msgid "" +"In general, when a format sets a pointer to a buffer, the buffer is managed " +"by the corresponding Python object, and the buffer shares the lifetime of " +"this object. You won't have to release any memory yourself. The only " +"exceptions are ``es``, ``es#``, ``et`` and ``et#``." +msgstr "" + +#: ../Doc/c-api/arg.rst:42 +msgid "" +"However, when a :c:type:`Py_buffer` structure gets filled, the underlying " +"buffer is locked so that the caller can subsequently use the buffer even " +"inside a :c:type:`Py_BEGIN_ALLOW_THREADS` block without the risk of mutable " +"data being resized or destroyed. As a result, **you have to call** :c:func:" +"`PyBuffer_Release` after you have finished processing the data (or in any " +"early abort case)." +msgstr "" + +#: ../Doc/c-api/arg.rst:49 +msgid "Unless otherwise stated, buffers are not NUL-terminated." +msgstr "" + +#: ../Doc/c-api/arg.rst:51 +msgid "" +"Some formats require a read-only :term:`bytes-like object`, and set a " +"pointer instead of a buffer structure. They work by checking that the " +"object's :c:member:`PyBufferProcs.bf_releasebuffer` field is *NULL*, which " +"disallows mutable objects such as :class:`bytearray`." +msgstr "" + +#: ../Doc/c-api/arg.rst:58 +msgid "" +"For all ``#`` variants of formats (``s#``, ``y#``, etc.), the type of the " +"length argument (int or :c:type:`Py_ssize_t`) is controlled by defining the " +"macro :c:macro:`PY_SSIZE_T_CLEAN` before including :file:`Python.h`. If the " +"macro was defined, length is a :c:type:`Py_ssize_t` rather than an :c:type:" +"`int`. This behavior will change in a future Python version to only support :" +"c:type:`Py_ssize_t` and drop :c:type:`int` support. It is best to always " +"define :c:macro:`PY_SSIZE_T_CLEAN`." +msgstr "" + +#: ../Doc/c-api/arg.rst:85 +msgid "``s`` (:class:`str`) [const char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:68 +msgid "" +"Convert a Unicode object to a C pointer to a character string. A pointer to " +"an existing string is stored in the character pointer variable whose address " +"you pass. The C string is NUL-terminated. The Python string must not " +"contain embedded null code points; if it does, a :exc:`ValueError` exception " +"is raised. Unicode objects are converted to C strings using ``'utf-8'`` " +"encoding. If this conversion fails, a :exc:`UnicodeError` is raised." +msgstr "" + +#: ../Doc/c-api/arg.rst:77 +msgid "" +"This format does not accept :term:`bytes-like objects `. " +"If you want to accept filesystem paths and convert them to C character " +"strings, it is preferable to use the ``O&`` format with :c:func:" +"`PyUnicode_FSConverter` as *converter*." +msgstr "" + +#: ../Doc/c-api/arg.rst:83 ../Doc/c-api/arg.rst:150 +msgid "" +"Previously, :exc:`TypeError` was raised when embedded null code points were " +"encountered in the Python string." +msgstr "" + +#: ../Doc/c-api/arg.rst:91 +msgid "``s*`` (:class:`str` or :term:`bytes-like object`) [Py_buffer]" +msgstr "" + +#: ../Doc/c-api/arg.rst:88 +msgid "" +"This format accepts Unicode objects as well as bytes-like objects. It fills " +"a :c:type:`Py_buffer` structure provided by the caller. In this case the " +"resulting C string may contain embedded NUL bytes. Unicode objects are " +"converted to C strings using ``'utf-8'`` encoding." +msgstr "" + +#: ../Doc/c-api/arg.rst:98 +msgid "" +"``s#`` (:class:`str`, read-only :term:`bytes-like object`) [const char \\*, " +"int or :c:type:`Py_ssize_t`]" +msgstr "" + +#: ../Doc/c-api/arg.rst:94 +msgid "" +"Like ``s*``, except that it doesn't accept mutable objects. The result is " +"stored into two C variables, the first one a pointer to a C string, the " +"second one its length. The string may contain embedded null bytes. Unicode " +"objects are converted to C strings using ``'utf-8'`` encoding." +msgstr "" + +#: ../Doc/c-api/arg.rst:102 +msgid "``z`` (:class:`str` or ``None``) [const char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:101 +msgid "" +"Like ``s``, but the Python object may also be ``None``, in which case the C " +"pointer is set to *NULL*." +msgstr "" + +#: ../Doc/c-api/arg.rst:106 +msgid "" +"``z*`` (:class:`str`, :term:`bytes-like object` or ``None``) [Py_buffer]" +msgstr "" + +#: ../Doc/c-api/arg.rst:105 +msgid "" +"Like ``s*``, but the Python object may also be ``None``, in which case the " +"``buf`` member of the :c:type:`Py_buffer` structure is set to *NULL*." +msgstr "" + +#: ../Doc/c-api/arg.rst:110 +msgid "" +"``z#`` (:class:`str`, read-only :term:`bytes-like object` or ``None``) " +"[const char \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:109 +msgid "" +"Like ``s#``, but the Python object may also be ``None``, in which case the C " +"pointer is set to *NULL*." +msgstr "" + +#: ../Doc/c-api/arg.rst:120 +msgid "``y`` (read-only :term:`bytes-like object`) [const char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:113 +msgid "" +"This format converts a bytes-like object to a C pointer to a character " +"string; it does not accept Unicode objects. The bytes buffer must not " +"contain embedded null bytes; if it does, a :exc:`ValueError` exception is " +"raised." +msgstr "" + +#: ../Doc/c-api/arg.rst:118 +msgid "" +"Previously, :exc:`TypeError` was raised when embedded null bytes were " +"encountered in the bytes buffer." +msgstr "" + +#: ../Doc/c-api/arg.rst:125 +msgid "``y*`` (:term:`bytes-like object`) [Py_buffer]" +msgstr "" + +#: ../Doc/c-api/arg.rst:123 +msgid "" +"This variant on ``s*`` doesn't accept Unicode objects, only bytes-like " +"objects. **This is the recommended way to accept binary data.**" +msgstr "" + +#: ../Doc/c-api/arg.rst:129 +msgid "``y#`` (read-only :term:`bytes-like object`) [const char \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:128 +msgid "" +"This variant on ``s#`` doesn't accept Unicode objects, only bytes-like " +"objects." +msgstr "" + +#: ../Doc/c-api/arg.rst:134 +msgid "``S`` (:class:`bytes`) [PyBytesObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:132 +msgid "" +"Requires that the Python object is a :class:`bytes` object, without " +"attempting any conversion. Raises :exc:`TypeError` if the object is not a " +"bytes object. The C variable may also be declared as :c:type:`PyObject\\*`." +msgstr "" + +#: ../Doc/c-api/arg.rst:139 +msgid "``Y`` (:class:`bytearray`) [PyByteArrayObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:137 +msgid "" +"Requires that the Python object is a :class:`bytearray` object, without " +"attempting any conversion. Raises :exc:`TypeError` if the object is not a :" +"class:`bytearray` object. The C variable may also be declared as :c:type:" +"`PyObject\\*`." +msgstr "" + +#: ../Doc/c-api/arg.rst:152 ../Doc/c-api/arg.rst:557 +msgid "``u`` (:class:`str`) [Py_UNICODE \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:142 +msgid "" +"Convert a Python Unicode object to a C pointer to a NUL-terminated buffer of " +"Unicode characters. You must pass the address of a :c:type:`Py_UNICODE` " +"pointer variable, which will be filled with the pointer to an existing " +"Unicode buffer. Please note that the width of a :c:type:`Py_UNICODE` " +"character depends on compilation options (it is either 16 or 32 bits). The " +"Python string must not contain embedded null code points; if it does, a :exc:" +"`ValueError` exception is raised." +msgstr "" + +#: ../Doc/c-api/arg.rst:157 ../Doc/c-api/arg.rst:562 +msgid "``u#`` (:class:`str`) [Py_UNICODE \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:155 +msgid "" +"This variant on ``u`` stores into two C variables, the first one a pointer " +"to a Unicode data buffer, the second one its length. This variant allows " +"null code points." +msgstr "" + +#: ../Doc/c-api/arg.rst:161 +msgid "``Z`` (:class:`str` or ``None``) [Py_UNICODE \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:160 +msgid "" +"Like ``u``, but the Python object may also be ``None``, in which case the :c:" +"type:`Py_UNICODE` pointer is set to *NULL*." +msgstr "" + +#: ../Doc/c-api/arg.rst:165 +msgid "``Z#`` (:class:`str` or ``None``) [Py_UNICODE \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:164 +msgid "" +"Like ``u#``, but the Python object may also be ``None``, in which case the :" +"c:type:`Py_UNICODE` pointer is set to *NULL*." +msgstr "" + +#: ../Doc/c-api/arg.rst:170 +msgid "``U`` (:class:`str`) [PyObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:168 +msgid "" +"Requires that the Python object is a Unicode object, without attempting any " +"conversion. Raises :exc:`TypeError` if the object is not a Unicode object. " +"The C variable may also be declared as :c:type:`PyObject\\*`." +msgstr "" + +#: ../Doc/c-api/arg.rst:176 +msgid "``w*`` (read-write :term:`bytes-like object`) [Py_buffer]" +msgstr "" + +#: ../Doc/c-api/arg.rst:173 +msgid "" +"This format accepts any object which implements the read-write buffer " +"interface. It fills a :c:type:`Py_buffer` structure provided by the caller. " +"The buffer may contain embedded null bytes. The caller have to call :c:func:" +"`PyBuffer_Release` when it is done with the buffer." +msgstr "" + +#: ../Doc/c-api/arg.rst:193 +msgid "``es`` (:class:`str`) [const char \\*encoding, char \\*\\*buffer]" +msgstr "" + +#: ../Doc/c-api/arg.rst:179 +msgid "" +"This variant on ``s`` is used for encoding Unicode into a character buffer. " +"It only works for encoded data without embedded NUL bytes." +msgstr "" + +#: ../Doc/c-api/arg.rst:182 +msgid "" +"This format requires two arguments. The first is only used as input, and " +"must be a :c:type:`const char\\*` which points to the name of an encoding as " +"a NUL-terminated string, or *NULL*, in which case ``'utf-8'`` encoding is " +"used. An exception is raised if the named encoding is not known to Python. " +"The second argument must be a :c:type:`char\\*\\*`; the value of the pointer " +"it references will be set to a buffer with the contents of the argument " +"text. The text will be encoded in the encoding specified by the first " +"argument." +msgstr "" + +#: ../Doc/c-api/arg.rst:190 +msgid "" +":c:func:`PyArg_ParseTuple` will allocate a buffer of the needed size, copy " +"the encoded data into this buffer and adjust *\\*buffer* to reference the " +"newly allocated storage. The caller is responsible for calling :c:func:" +"`PyMem_Free` to free the allocated buffer after use." +msgstr "" + +#: ../Doc/c-api/arg.rst:198 +msgid "" +"``et`` (:class:`str`, :class:`bytes` or :class:`bytearray`) [const char " +"\\*encoding, char \\*\\*buffer]" +msgstr "" + +#: ../Doc/c-api/arg.rst:196 +msgid "" +"Same as ``es`` except that byte string objects are passed through without " +"recoding them. Instead, the implementation assumes that the byte string " +"object uses the encoding passed in as parameter." +msgstr "" + +#: ../Doc/c-api/arg.rst:229 +msgid "" +"``es#`` (:class:`str`) [const char \\*encoding, char \\*\\*buffer, int " +"\\*buffer_length]" +msgstr "" + +#: ../Doc/c-api/arg.rst:201 +msgid "" +"This variant on ``s#`` is used for encoding Unicode into a character buffer. " +"Unlike the ``es`` format, this variant allows input data which contains NUL " +"characters." +msgstr "" + +#: ../Doc/c-api/arg.rst:205 +msgid "" +"It requires three arguments. The first is only used as input, and must be " +"a :c:type:`const char\\*` which points to the name of an encoding as a NUL-" +"terminated string, or *NULL*, in which case ``'utf-8'`` encoding is used. An " +"exception is raised if the named encoding is not known to Python. The " +"second argument must be a :c:type:`char\\*\\*`; the value of the pointer it " +"references will be set to a buffer with the contents of the argument text. " +"The text will be encoded in the encoding specified by the first argument. " +"The third argument must be a pointer to an integer; the referenced integer " +"will be set to the number of bytes in the output buffer." +msgstr "" + +#: ../Doc/c-api/arg.rst:215 +msgid "There are two modes of operation:" +msgstr "" + +#: ../Doc/c-api/arg.rst:217 +msgid "" +"If *\\*buffer* points a *NULL* pointer, the function will allocate a buffer " +"of the needed size, copy the encoded data into this buffer and set *" +"\\*buffer* to reference the newly allocated storage. The caller is " +"responsible for calling :c:func:`PyMem_Free` to free the allocated buffer " +"after usage." +msgstr "" + +#: ../Doc/c-api/arg.rst:222 +msgid "" +"If *\\*buffer* points to a non-*NULL* pointer (an already allocated " +"buffer), :c:func:`PyArg_ParseTuple` will use this location as the buffer and " +"interpret the initial value of *\\*buffer_length* as the buffer size. It " +"will then copy the encoded data into the buffer and NUL-terminate it. If " +"the buffer is not large enough, a :exc:`ValueError` will be set." +msgstr "" + +#: ../Doc/c-api/arg.rst:228 +msgid "" +"In both cases, *\\*buffer_length* is set to the length of the encoded data " +"without the trailing NUL byte." +msgstr "" + +#: ../Doc/c-api/arg.rst:234 +msgid "" +"``et#`` (:class:`str`, :class:`bytes` or :class:`bytearray`) [const char " +"\\*encoding, char \\*\\*buffer, int \\*buffer_length]" +msgstr "" + +#: ../Doc/c-api/arg.rst:232 +msgid "" +"Same as ``es#`` except that byte string objects are passed through without " +"recoding them. Instead, the implementation assumes that the byte string " +"object uses the encoding passed in as parameter." +msgstr "" + +#: ../Doc/c-api/arg.rst:237 +msgid "Numbers" +msgstr "" + +#: ../Doc/c-api/arg.rst:241 +msgid "``b`` (:class:`int`) [unsigned char]" +msgstr "" + +#: ../Doc/c-api/arg.rst:240 +msgid "" +"Convert a nonnegative Python integer to an unsigned tiny int, stored in a C :" +"c:type:`unsigned char`." +msgstr "" + +#: ../Doc/c-api/arg.rst:245 ../Doc/c-api/arg.rst:583 +msgid "``B`` (:class:`int`) [unsigned char]" +msgstr "" + +#: ../Doc/c-api/arg.rst:244 +msgid "" +"Convert a Python integer to a tiny int without overflow checking, stored in " +"a C :c:type:`unsigned char`." +msgstr "" + +#: ../Doc/c-api/arg.rst:248 ../Doc/c-api/arg.rst:577 +msgid "``h`` (:class:`int`) [short int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:248 +msgid "Convert a Python integer to a C :c:type:`short int`." +msgstr "" + +#: ../Doc/c-api/arg.rst:252 ../Doc/c-api/arg.rst:586 +msgid "``H`` (:class:`int`) [unsigned short int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:251 +msgid "" +"Convert a Python integer to a C :c:type:`unsigned short int`, without " +"overflow checking." +msgstr "" + +#: ../Doc/c-api/arg.rst:255 ../Doc/c-api/arg.rst:571 +msgid "``i`` (:class:`int`) [int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:255 +msgid "Convert a Python integer to a plain C :c:type:`int`." +msgstr "" + +#: ../Doc/c-api/arg.rst:259 ../Doc/c-api/arg.rst:589 +msgid "``I`` (:class:`int`) [unsigned int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:258 +msgid "" +"Convert a Python integer to a C :c:type:`unsigned int`, without overflow " +"checking." +msgstr "" + +#: ../Doc/c-api/arg.rst:262 ../Doc/c-api/arg.rst:580 +msgid "``l`` (:class:`int`) [long int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:262 +msgid "Convert a Python integer to a C :c:type:`long int`." +msgstr "" + +#: ../Doc/c-api/arg.rst:266 ../Doc/c-api/arg.rst:592 +msgid "``k`` (:class:`int`) [unsigned long]" +msgstr "" + +#: ../Doc/c-api/arg.rst:265 +msgid "" +"Convert a Python integer to a C :c:type:`unsigned long` without overflow " +"checking." +msgstr "" + +#: ../Doc/c-api/arg.rst:269 ../Doc/c-api/arg.rst:595 +msgid "``L`` (:class:`int`) [long long]" +msgstr "" + +#: ../Doc/c-api/arg.rst:269 +msgid "Convert a Python integer to a C :c:type:`long long`." +msgstr "" + +#: ../Doc/c-api/arg.rst:273 ../Doc/c-api/arg.rst:598 +msgid "``K`` (:class:`int`) [unsigned long long]" +msgstr "" + +#: ../Doc/c-api/arg.rst:272 +msgid "" +"Convert a Python integer to a C :c:type:`unsigned long long` without " +"overflow checking." +msgstr "" + +#: ../Doc/c-api/arg.rst:276 ../Doc/c-api/arg.rst:601 +msgid "``n`` (:class:`int`) [Py_ssize_t]" +msgstr "" + +#: ../Doc/c-api/arg.rst:276 +msgid "Convert a Python integer to a C :c:type:`Py_ssize_t`." +msgstr "" + +#: ../Doc/c-api/arg.rst:283 +msgid "``c`` (:class:`bytes` or :class:`bytearray` of length 1) [char]" +msgstr "" + +#: ../Doc/c-api/arg.rst:279 +msgid "" +"Convert a Python byte, represented as a :class:`bytes` or :class:`bytearray` " +"object of length 1, to a C :c:type:`char`." +msgstr "" + +#: ../Doc/c-api/arg.rst:282 +msgid "Allow :class:`bytearray` objects." +msgstr "" + +#: ../Doc/c-api/arg.rst:287 ../Doc/c-api/arg.rst:609 +msgid "``C`` (:class:`str` of length 1) [int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:286 +msgid "" +"Convert a Python character, represented as a :class:`str` object of length " +"1, to a C :c:type:`int`." +msgstr "" + +#: ../Doc/c-api/arg.rst:290 ../Doc/c-api/arg.rst:615 +msgid "``f`` (:class:`float`) [float]" +msgstr "" + +#: ../Doc/c-api/arg.rst:290 +msgid "Convert a Python floating point number to a C :c:type:`float`." +msgstr "" + +#: ../Doc/c-api/arg.rst:293 ../Doc/c-api/arg.rst:612 +msgid "``d`` (:class:`float`) [double]" +msgstr "" + +#: ../Doc/c-api/arg.rst:293 +msgid "Convert a Python floating point number to a C :c:type:`double`." +msgstr "" + +#: ../Doc/c-api/arg.rst:296 +msgid "``D`` (:class:`complex`) [Py_complex]" +msgstr "" + +#: ../Doc/c-api/arg.rst:296 +msgid "Convert a Python complex number to a C :c:type:`Py_complex` structure." +msgstr "" + +#: ../Doc/c-api/arg.rst:299 +msgid "Other objects" +msgstr "" + +#: ../Doc/c-api/arg.rst:304 ../Doc/c-api/arg.rst:626 +msgid "``O`` (object) [PyObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:302 +msgid "" +"Store a Python object (without any conversion) in a C object pointer. The C " +"program thus receives the actual object that was passed. The object's " +"reference count is not increased. The pointer stored is not *NULL*." +msgstr "" + +#: ../Doc/c-api/arg.rst:311 +msgid "``O!`` (object) [*typeobject*, PyObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:307 +msgid "" +"Store a Python object in a C object pointer. This is similar to ``O``, but " +"takes two C arguments: the first is the address of a Python type object, the " +"second is the address of the C variable (of type :c:type:`PyObject\\*`) into " +"which the object pointer is stored. If the Python object does not have the " +"required type, :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/c-api/arg.rst:336 ../Doc/c-api/arg.rst:640 +msgid "``O&`` (object) [*converter*, *anything*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:316 +msgid "" +"Convert a Python object to a C variable through a *converter* function. " +"This takes two arguments: the first is a function, the second is the address " +"of a C variable (of arbitrary type), converted to :c:type:`void \\*`. The " +"*converter* function in turn is called as follows::" +msgstr "" + +#: ../Doc/c-api/arg.rst:323 +msgid "" +"where *object* is the Python object to be converted and *address* is the :c:" +"type:`void\\*` argument that was passed to the :c:func:`PyArg_Parse\\*` " +"function. The returned *status* should be ``1`` for a successful conversion " +"and ``0`` if the conversion has failed. When the conversion fails, the " +"*converter* function should raise an exception and leave the content of " +"*address* unmodified." +msgstr "" + +#: ../Doc/c-api/arg.rst:329 +msgid "" +"If the *converter* returns ``Py_CLEANUP_SUPPORTED``, it may get called a " +"second time if the argument parsing eventually fails, giving the converter a " +"chance to release any memory that it had already allocated. In this second " +"call, the *object* parameter will be NULL; *address* will have the same " +"value as in the original call." +msgstr "" + +#: ../Doc/c-api/arg.rst:335 +msgid "``Py_CLEANUP_SUPPORTED`` was added." +msgstr "" + +#: ../Doc/c-api/arg.rst:345 +msgid "``p`` (:class:`bool`) [int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:339 +msgid "" +"Tests the value passed in for truth (a boolean **p**\\ redicate) and " +"converts the result to its equivalent C true/false integer value. Sets the " +"int to 1 if the expression was true and 0 if it was false. This accepts any " +"valid Python value. See :ref:`truth` for more information about how Python " +"tests values for truth." +msgstr "" + +#: ../Doc/c-api/arg.rst:350 ../Doc/c-api/arg.rst:643 +msgid "``(items)`` (:class:`tuple`) [*matching-items*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:348 +msgid "" +"The object must be a Python sequence whose length is the number of format " +"units in *items*. The C arguments must correspond to the individual format " +"units in *items*. Format units for sequences may be nested." +msgstr "" + +#: ../Doc/c-api/arg.rst:352 +msgid "" +"It is possible to pass \"long\" integers (integers whose value exceeds the " +"platform's :const:`LONG_MAX`) however no proper range checking is done --- " +"the most significant bits are silently truncated when the receiving field is " +"too small to receive the value (actually, the semantics are inherited from " +"downcasts in C --- your mileage may vary)." +msgstr "" + +#: ../Doc/c-api/arg.rst:358 +msgid "" +"A few other characters have a meaning in a format string. These may not " +"occur inside nested parentheses. They are:" +msgstr "" + +#: ../Doc/c-api/arg.rst:366 +msgid "``|``" +msgstr "" + +#: ../Doc/c-api/arg.rst:362 +msgid "" +"Indicates that the remaining arguments in the Python argument list are " +"optional. The C variables corresponding to optional arguments should be " +"initialized to their default value --- when an optional argument is not " +"specified, :c:func:`PyArg_ParseTuple` does not touch the contents of the " +"corresponding C variable(s)." +msgstr "" + +#: ../Doc/c-api/arg.rst:375 +msgid "``$``" +msgstr "" + +#: ../Doc/c-api/arg.rst:369 +msgid "" +":c:func:`PyArg_ParseTupleAndKeywords` only: Indicates that the remaining " +"arguments in the Python argument list are keyword-only. Currently, all " +"keyword-only arguments must also be optional arguments, so ``|`` must always " +"be specified before ``$`` in the format string." +msgstr "" + +#: ../Doc/c-api/arg.rst:380 +msgid "``:``" +msgstr "" + +#: ../Doc/c-api/arg.rst:378 +msgid "" +"The list of format units ends here; the string after the colon is used as " +"the function name in error messages (the \"associated value\" of the " +"exception that :c:func:`PyArg_ParseTuple` raises)." +msgstr "" + +#: ../Doc/c-api/arg.rst:385 +msgid "``;``" +msgstr "" + +#: ../Doc/c-api/arg.rst:383 +msgid "" +"The list of format units ends here; the string after the semicolon is used " +"as the error message *instead* of the default error message. ``:`` and ``;" +"`` mutually exclude each other." +msgstr "" + +#: ../Doc/c-api/arg.rst:387 +msgid "" +"Note that any Python object references which are provided to the caller are " +"*borrowed* references; do not decrement their reference count!" +msgstr "" + +#: ../Doc/c-api/arg.rst:390 +msgid "" +"Additional arguments passed to these functions must be addresses of " +"variables whose type is determined by the format string; these are used to " +"store values from the input tuple. There are a few cases, as described in " +"the list of format units above, where these parameters are used as input " +"values; they should match what is specified for the corresponding format " +"unit in that case." +msgstr "" + +#: ../Doc/c-api/arg.rst:396 +msgid "" +"For the conversion to succeed, the *arg* object must match the format and " +"the format must be exhausted. On success, the :c:func:`PyArg_Parse\\*` " +"functions return true, otherwise they return false and raise an appropriate " +"exception. When the :c:func:`PyArg_Parse\\*` functions fail due to " +"conversion failure in one of the format units, the variables at the " +"addresses corresponding to that and the following format units are left " +"untouched." +msgstr "" + +#: ../Doc/c-api/arg.rst:405 +msgid "API Functions" +msgstr "" + +#: ../Doc/c-api/arg.rst:409 +msgid "" +"Parse the parameters of a function that takes only positional parameters " +"into local variables. Returns true on success; on failure, it returns false " +"and raises the appropriate exception." +msgstr "" + +#: ../Doc/c-api/arg.rst:416 +msgid "" +"Identical to :c:func:`PyArg_ParseTuple`, except that it accepts a va_list " +"rather than a variable number of arguments." +msgstr "" + +#: ../Doc/c-api/arg.rst:422 +msgid "" +"Parse the parameters of a function that takes both positional and keyword " +"parameters into local variables. The *keywords* argument is a *NULL*-" +"terminated array of keyword parameter names. Empty names denote :ref:" +"`positional-only parameters `. Returns true on " +"success; on failure, it returns false and raises the appropriate exception." +msgstr "" + +#: ../Doc/c-api/arg.rst:429 +msgid "" +"Added support for :ref:`positional-only parameters `." +msgstr "" + +#: ../Doc/c-api/arg.rst:436 +msgid "" +"Identical to :c:func:`PyArg_ParseTupleAndKeywords`, except that it accepts a " +"va_list rather than a variable number of arguments." +msgstr "" + +#: ../Doc/c-api/arg.rst:442 +msgid "" +"Ensure that the keys in the keywords argument dictionary are strings. This " +"is only needed if :c:func:`PyArg_ParseTupleAndKeywords` is not used, since " +"the latter already does this check." +msgstr "" + +#: ../Doc/c-api/arg.rst:452 +msgid "" +"Function used to deconstruct the argument lists of \"old-style\" functions " +"--- these are functions which use the :const:`METH_OLDARGS` parameter " +"parsing method, which has been removed in Python 3. This is not recommended " +"for use in parameter parsing in new code, and most code in the standard " +"interpreter has been modified to no longer use this for that purpose. It " +"does remain a convenient way to decompose other tuples, however, and may " +"continue to be used for that purpose." +msgstr "" + +#: ../Doc/c-api/arg.rst:463 +msgid "" +"A simpler form of parameter retrieval which does not use a format string to " +"specify the types of the arguments. Functions which use this method to " +"retrieve their parameters should be declared as :const:`METH_VARARGS` in " +"function or method tables. The tuple containing the actual parameters " +"should be passed as *args*; it must actually be a tuple. The length of the " +"tuple must be at least *min* and no more than *max*; *min* and *max* may be " +"equal. Additional arguments must be passed to the function, each of which " +"should be a pointer to a :c:type:`PyObject\\*` variable; these will be " +"filled in with the values from *args*; they will contain borrowed " +"references. The variables which correspond to optional parameters not given " +"by *args* will not be filled in; these should be initialized by the caller. " +"This function returns true on success and false if *args* is not a tuple or " +"contains the wrong number of elements; an exception will be set if there was " +"a failure." +msgstr "" + +#: ../Doc/c-api/arg.rst:477 +msgid "" +"This is an example of the use of this function, taken from the sources for " +"the :mod:`_weakref` helper module for weak references::" +msgstr "" + +#: ../Doc/c-api/arg.rst:493 +msgid "" +"The call to :c:func:`PyArg_UnpackTuple` in this example is entirely " +"equivalent to this call to :c:func:`PyArg_ParseTuple`::" +msgstr "" + +#: ../Doc/c-api/arg.rst:501 +msgid "Building values" +msgstr "" + +#: ../Doc/c-api/arg.rst:505 +msgid "" +"Create a new value based on a format string similar to those accepted by " +"the :c:func:`PyArg_Parse\\*` family of functions and a sequence of values. " +"Returns the value or *NULL* in the case of an error; an exception will be " +"raised if *NULL* is returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:510 +msgid "" +":c:func:`Py_BuildValue` does not always build a tuple. It builds a tuple " +"only if its format string contains two or more format units. If the format " +"string is empty, it returns ``None``; if it contains exactly one format " +"unit, it returns whatever object is described by that format unit. To force " +"it to return a tuple of size 0 or one, parenthesize the format string." +msgstr "" + +#: ../Doc/c-api/arg.rst:516 +msgid "" +"When memory buffers are passed as parameters to supply data to build " +"objects, as for the ``s`` and ``s#`` formats, the required data is copied. " +"Buffers provided by the caller are never referenced by the objects created " +"by :c:func:`Py_BuildValue`. In other words, if your code invokes :c:func:" +"`malloc` and passes the allocated memory to :c:func:`Py_BuildValue`, your " +"code is responsible for calling :c:func:`free` for that memory once :c:func:" +"`Py_BuildValue` returns." +msgstr "" + +#: ../Doc/c-api/arg.rst:524 +msgid "" +"In the following description, the quoted form is the format unit; the entry " +"in (round) parentheses is the Python object type that the format unit will " +"return; and the entry in [square] brackets is the type of the C value(s) to " +"be passed." +msgstr "" + +#: ../Doc/c-api/arg.rst:528 +msgid "" +"The characters space, tab, colon and comma are ignored in format strings " +"(but not within format units such as ``s#``). This can be used to make long " +"format strings a tad more readable." +msgstr "" + +#: ../Doc/c-api/arg.rst:534 +msgid "``s`` (:class:`str` or ``None``) [char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:533 +msgid "" +"Convert a null-terminated C string to a Python :class:`str` object using " +"``'utf-8'`` encoding. If the C string pointer is *NULL*, ``None`` is used." +msgstr "" + +#: ../Doc/c-api/arg.rst:539 +msgid "``s#`` (:class:`str` or ``None``) [char \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:537 +msgid "" +"Convert a C string and its length to a Python :class:`str` object using " +"``'utf-8'`` encoding. If the C string pointer is *NULL*, the length is " +"ignored and ``None`` is returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:543 +msgid "``y`` (:class:`bytes`) [char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:542 +msgid "" +"This converts a C string to a Python :class:`bytes` object. If the C string " +"pointer is *NULL*, ``None`` is returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:547 +msgid "``y#`` (:class:`bytes`) [char \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:546 +msgid "" +"This converts a C string and its lengths to a Python object. If the C " +"string pointer is *NULL*, ``None`` is returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:550 +msgid "``z`` (:class:`str` or ``None``) [char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:550 ../Doc/c-api/arg.rst:565 +msgid "Same as ``s``." +msgstr "" + +#: ../Doc/c-api/arg.rst:553 +msgid "``z#`` (:class:`str` or ``None``) [char \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:553 ../Doc/c-api/arg.rst:568 +msgid "Same as ``s#``." +msgstr "" + +#: ../Doc/c-api/arg.rst:556 +msgid "" +"Convert a null-terminated buffer of Unicode (UCS-2 or UCS-4) data to a " +"Python Unicode object. If the Unicode buffer pointer is *NULL*, ``None`` is " +"returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:560 +msgid "" +"Convert a Unicode (UCS-2 or UCS-4) data buffer and its length to a Python " +"Unicode object. If the Unicode buffer pointer is *NULL*, the length is " +"ignored and ``None`` is returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:565 +msgid "``U`` (:class:`str` or ``None``) [char \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:568 +msgid "``U#`` (:class:`str` or ``None``) [char \\*, int]" +msgstr "" + +#: ../Doc/c-api/arg.rst:571 +msgid "Convert a plain C :c:type:`int` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:574 +msgid "``b`` (:class:`int`) [char]" +msgstr "" + +#: ../Doc/c-api/arg.rst:574 +msgid "Convert a plain C :c:type:`char` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:577 +msgid "Convert a plain C :c:type:`short int` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:580 +msgid "Convert a C :c:type:`long int` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:583 +msgid "Convert a C :c:type:`unsigned char` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:586 +msgid "Convert a C :c:type:`unsigned short int` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:589 +msgid "Convert a C :c:type:`unsigned int` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:592 +msgid "Convert a C :c:type:`unsigned long` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:595 +msgid "Convert a C :c:type:`long long` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:598 +msgid "Convert a C :c:type:`unsigned long long` to a Python integer object." +msgstr "" + +#: ../Doc/c-api/arg.rst:601 +msgid "Convert a C :c:type:`Py_ssize_t` to a Python integer." +msgstr "" + +#: ../Doc/c-api/arg.rst:605 +msgid "``c`` (:class:`bytes` of length 1) [char]" +msgstr "" + +#: ../Doc/c-api/arg.rst:604 +msgid "" +"Convert a C :c:type:`int` representing a byte to a Python :class:`bytes` " +"object of length 1." +msgstr "" + +#: ../Doc/c-api/arg.rst:608 +msgid "" +"Convert a C :c:type:`int` representing a character to Python :class:`str` " +"object of length 1." +msgstr "" + +#: ../Doc/c-api/arg.rst:612 +msgid "Convert a C :c:type:`double` to a Python floating point number." +msgstr "" + +#: ../Doc/c-api/arg.rst:615 +msgid "Convert a C :c:type:`float` to a Python floating point number." +msgstr "" + +#: ../Doc/c-api/arg.rst:618 +msgid "``D`` (:class:`complex`) [Py_complex \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:618 +msgid "Convert a C :c:type:`Py_complex` structure to a Python complex number." +msgstr "" + +#: ../Doc/c-api/arg.rst:621 +msgid "" +"Pass a Python object untouched (except for its reference count, which is " +"incremented by one). If the object passed in is a *NULL* pointer, it is " +"assumed that this was caused because the call producing the argument found " +"an error and set an exception. Therefore, :c:func:`Py_BuildValue` will " +"return *NULL* but won't raise an exception. If no exception has been raised " +"yet, :exc:`SystemError` is set." +msgstr "" + +#: ../Doc/c-api/arg.rst:629 +msgid "``S`` (object) [PyObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:629 +msgid "Same as ``O``." +msgstr "" + +#: ../Doc/c-api/arg.rst:634 +msgid "``N`` (object) [PyObject \\*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:632 +msgid "" +"Same as ``O``, except it doesn't increment the reference count on the " +"object. Useful when the object is created by a call to an object constructor " +"in the argument list." +msgstr "" + +#: ../Doc/c-api/arg.rst:637 +msgid "" +"Convert *anything* to a Python object through a *converter* function. The " +"function is called with *anything* (which should be compatible with :c:type:" +"`void \\*`) as its argument and should return a \"new\" Python object, or " +"*NULL* if an error occurred." +msgstr "" + +#: ../Doc/c-api/arg.rst:643 +msgid "" +"Convert a sequence of C values to a Python tuple with the same number of " +"items." +msgstr "" + +#: ../Doc/c-api/arg.rst:646 +msgid "``[items]`` (:class:`list`) [*matching-items*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:646 +msgid "" +"Convert a sequence of C values to a Python list with the same number of " +"items." +msgstr "" + +#: ../Doc/c-api/arg.rst:651 +msgid "``{items}`` (:class:`dict`) [*matching-items*]" +msgstr "" + +#: ../Doc/c-api/arg.rst:649 +msgid "" +"Convert a sequence of C values to a Python dictionary. Each pair of " +"consecutive C values adds one item to the dictionary, serving as key and " +"value, respectively." +msgstr "" + +#: ../Doc/c-api/arg.rst:653 +msgid "" +"If there is an error in the format string, the :exc:`SystemError` exception " +"is set and *NULL* returned." +msgstr "" + +#: ../Doc/c-api/arg.rst:658 +msgid "" +"Identical to :c:func:`Py_BuildValue`, except that it accepts a va_list " +"rather than a variable number of arguments." +msgstr "" + +#: ../Doc/c-api/bool.rst:6 +msgid "Boolean Objects" +msgstr "" + +#: ../Doc/c-api/bool.rst:8 +msgid "" +"Booleans in Python are implemented as a subclass of integers. There are " +"only two booleans, :const:`Py_False` and :const:`Py_True`. As such, the " +"normal creation and deletion functions don't apply to booleans. The " +"following macros are available, however." +msgstr "" + +#: ../Doc/c-api/bool.rst:16 +msgid "Return true if *o* is of type :c:data:`PyBool_Type`." +msgstr "" + +#: ../Doc/c-api/bool.rst:21 +msgid "" +"The Python ``False`` object. This object has no methods. It needs to be " +"treated just like any other object with respect to reference counts." +msgstr "" + +#: ../Doc/c-api/bool.rst:27 +msgid "" +"The Python ``True`` object. This object has no methods. It needs to be " +"treated just like any other object with respect to reference counts." +msgstr "" + +#: ../Doc/c-api/bool.rst:33 +msgid "" +"Return :const:`Py_False` from a function, properly incrementing its " +"reference count." +msgstr "" + +#: ../Doc/c-api/bool.rst:39 +msgid "" +"Return :const:`Py_True` from a function, properly incrementing its reference " +"count." +msgstr "" + +#: ../Doc/c-api/bool.rst:45 +msgid "" +"Return a new reference to :const:`Py_True` or :const:`Py_False` depending on " +"the truth value of *v*." +msgstr "" + +#: ../Doc/c-api/buffer.rst:11 +msgid "Buffer Protocol" +msgstr "" + +#: ../Doc/c-api/buffer.rst:18 +msgid "" +"Certain objects available in Python wrap access to an underlying memory " +"array or *buffer*. Such objects include the built-in :class:`bytes` and :" +"class:`bytearray`, and some extension types like :class:`array.array`. Third-" +"party libraries may define their own types for special purposes, such as " +"image processing or numeric analysis." +msgstr "" + +#: ../Doc/c-api/buffer.rst:24 +msgid "" +"While each of these types have their own semantics, they share the common " +"characteristic of being backed by a possibly large memory buffer. It is " +"then desirable, in some situations, to access that buffer directly and " +"without intermediate copying." +msgstr "" + +#: ../Doc/c-api/buffer.rst:29 +msgid "" +"Python provides such a facility at the C level in the form of the :ref:" +"`buffer protocol `. This protocol has two sides:" +msgstr "" + +#: ../Doc/c-api/buffer.rst:34 +msgid "" +"on the producer side, a type can export a \"buffer interface\" which allows " +"objects of that type to expose information about their underlying buffer. " +"This interface is described in the section :ref:`buffer-structs`;" +msgstr "" + +#: ../Doc/c-api/buffer.rst:38 +msgid "" +"on the consumer side, several means are available to obtain a pointer to the " +"raw underlying data of an object (for example a method parameter)." +msgstr "" + +#: ../Doc/c-api/buffer.rst:41 +msgid "" +"Simple objects such as :class:`bytes` and :class:`bytearray` expose their " +"underlying buffer in byte-oriented form. Other forms are possible; for " +"example, the elements exposed by an :class:`array.array` can be multi-byte " +"values." +msgstr "" + +#: ../Doc/c-api/buffer.rst:45 +msgid "" +"An example consumer of the buffer interface is the :meth:`~io.BufferedIOBase." +"write` method of file objects: any object that can export a series of bytes " +"through the buffer interface can be written to a file. While :meth:`write` " +"only needs read-only access to the internal contents of the object passed to " +"it, other methods such as :meth:`~io.BufferedIOBase.readinto` need write " +"access to the contents of their argument. The buffer interface allows " +"objects to selectively allow or reject exporting of read-write and read-only " +"buffers." +msgstr "" + +#: ../Doc/c-api/buffer.rst:53 +msgid "" +"There are two ways for a consumer of the buffer interface to acquire a " +"buffer over a target object:" +msgstr "" + +#: ../Doc/c-api/buffer.rst:56 +msgid "call :c:func:`PyObject_GetBuffer` with the right parameters;" +msgstr "" + +#: ../Doc/c-api/buffer.rst:58 +msgid "" +"call :c:func:`PyArg_ParseTuple` (or one of its siblings) with one of the " +"``y*``, ``w*`` or ``s*`` :ref:`format codes `." +msgstr "" + +#: ../Doc/c-api/buffer.rst:61 +msgid "" +"In both cases, :c:func:`PyBuffer_Release` must be called when the buffer " +"isn't needed anymore. Failure to do so could lead to various issues such as " +"resource leaks." +msgstr "" + +#: ../Doc/c-api/buffer.rst:69 +msgid "Buffer structure" +msgstr "" + +#: ../Doc/c-api/buffer.rst:71 +msgid "" +"Buffer structures (or simply \"buffers\") are useful as a way to expose the " +"binary data from another object to the Python programmer. They can also be " +"used as a zero-copy slicing mechanism. Using their ability to reference a " +"block of memory, it is possible to expose any data to the Python programmer " +"quite easily. The memory could be a large, constant array in a C extension, " +"it could be a raw block of memory for manipulation before passing to an " +"operating system library, or it could be used to pass around structured data " +"in its native, in-memory format." +msgstr "" + +#: ../Doc/c-api/buffer.rst:80 +msgid "" +"Contrary to most data types exposed by the Python interpreter, buffers are " +"not :c:type:`PyObject` pointers but rather simple C structures. This allows " +"them to be created and copied very simply. When a generic wrapper around a " +"buffer is needed, a :ref:`memoryview ` object can be " +"created." +msgstr "" + +#: ../Doc/c-api/buffer.rst:86 +msgid "" +"For short instructions how to write an exporting object, see :ref:`Buffer " +"Object Structures `. For obtaining a buffer, see :c:func:" +"`PyObject_GetBuffer`." +msgstr "" + +#: ../Doc/c-api/buffer.rst:94 +msgid "" +"A pointer to the start of the logical structure described by the buffer " +"fields. This can be any location within the underlying physical memory block " +"of the exporter. For example, with negative :c:member:`~Py_buffer.strides` " +"the value may point to the end of the memory block." +msgstr "" + +#: ../Doc/c-api/buffer.rst:99 +msgid "" +"For :term:`contiguous` arrays, the value points to the beginning of the " +"memory block." +msgstr "" + +#: ../Doc/c-api/buffer.rst:104 +msgid "" +"A new reference to the exporting object. The reference is owned by the " +"consumer and automatically decremented and set to *NULL* by :c:func:" +"`PyBuffer_Release`. The field is the equivalent of the return value of any " +"standard C-API function." +msgstr "" + +#: ../Doc/c-api/buffer.rst:109 +msgid "" +"As a special case, for *temporary* buffers that are wrapped by :c:func:" +"`PyMemoryView_FromBuffer` or :c:func:`PyBuffer_FillInfo` this field is " +"*NULL*. In general, exporting objects MUST NOT use this scheme." +msgstr "" + +#: ../Doc/c-api/buffer.rst:116 +msgid "" +"``product(shape) * itemsize``. For contiguous arrays, this is the length of " +"the underlying memory block. For non-contiguous arrays, it is the length " +"that the logical structure would have if it were copied to a contiguous " +"representation." +msgstr "" + +#: ../Doc/c-api/buffer.rst:121 +msgid "" +"Accessing ``((char *)buf)[0] up to ((char *)buf)[len-1]`` is only valid if " +"the buffer has been obtained by a request that guarantees contiguity. In " +"most cases such a request will be :c:macro:`PyBUF_SIMPLE` or :c:macro:" +"`PyBUF_WRITABLE`." +msgstr "" + +#: ../Doc/c-api/buffer.rst:127 +msgid "" +"An indicator of whether the buffer is read-only. This field is controlled by " +"the :c:macro:`PyBUF_WRITABLE` flag." +msgstr "" + +#: ../Doc/c-api/buffer.rst:132 +msgid "" +"Item size in bytes of a single element. Same as the value of :func:`struct." +"calcsize` called on non-NULL :c:member:`~Py_buffer.format` values." +msgstr "" + +#: ../Doc/c-api/buffer.rst:135 +msgid "" +"Important exception: If a consumer requests a buffer without the :c:macro:" +"`PyBUF_FORMAT` flag, :c:member:`~Py_buffer.format` will be set to *NULL*, " +"but :c:member:`~Py_buffer.itemsize` still has the value for the original " +"format." +msgstr "" + +#: ../Doc/c-api/buffer.rst:140 +msgid "" +"If :c:member:`~Py_buffer.shape` is present, the equality ``product(shape) * " +"itemsize == len`` still holds and the consumer can use :c:member:`~Py_buffer." +"itemsize` to navigate the buffer." +msgstr "" + +#: ../Doc/c-api/buffer.rst:144 +msgid "" +"If :c:member:`~Py_buffer.shape` is *NULL* as a result of a :c:macro:" +"`PyBUF_SIMPLE` or a :c:macro:`PyBUF_WRITABLE` request, the consumer must " +"disregard :c:member:`~Py_buffer.itemsize` and assume ``itemsize == 1``." +msgstr "" + +#: ../Doc/c-api/buffer.rst:150 +msgid "" +"A *NUL* terminated string in :mod:`struct` module style syntax describing " +"the contents of a single item. If this is *NULL*, ``\"B\"`` (unsigned bytes) " +"is assumed." +msgstr "" + +#: ../Doc/c-api/buffer.rst:154 +msgid "This field is controlled by the :c:macro:`PyBUF_FORMAT` flag." +msgstr "" + +#: ../Doc/c-api/buffer.rst:158 +msgid "" +"The number of dimensions the memory represents as an n-dimensional array. If " +"it is 0, :c:member:`~Py_buffer.buf` points to a single item representing a " +"scalar. In this case, :c:member:`~Py_buffer.shape`, :c:member:`~Py_buffer." +"strides` and :c:member:`~Py_buffer.suboffsets` MUST be *NULL*." +msgstr "" + +#: ../Doc/c-api/buffer.rst:163 +msgid "" +"The macro :c:macro:`PyBUF_MAX_NDIM` limits the maximum number of dimensions " +"to 64. Exporters MUST respect this limit, consumers of multi-dimensional " +"buffers SHOULD be able to handle up to :c:macro:`PyBUF_MAX_NDIM` dimensions." +msgstr "" + +#: ../Doc/c-api/buffer.rst:169 +msgid "" +"An array of :c:type:`Py_ssize_t` of length :c:member:`~Py_buffer.ndim` " +"indicating the shape of the memory as an n-dimensional array. Note that " +"``shape[0] * ... * shape[ndim-1] * itemsize`` MUST be equal to :c:member:" +"`~Py_buffer.len`." +msgstr "" + +#: ../Doc/c-api/buffer.rst:174 +msgid "" +"Shape values are restricted to ``shape[n] >= 0``. The case ``shape[n] == 0`` " +"requires special attention. See `complex arrays`_ for further information." +msgstr "" + +#: ../Doc/c-api/buffer.rst:178 +msgid "The shape array is read-only for the consumer." +msgstr "" + +#: ../Doc/c-api/buffer.rst:182 +msgid "" +"An array of :c:type:`Py_ssize_t` of length :c:member:`~Py_buffer.ndim` " +"giving the number of bytes to skip to get to a new element in each dimension." +msgstr "" + +#: ../Doc/c-api/buffer.rst:186 +msgid "" +"Stride values can be any integer. For regular arrays, strides are usually " +"positive, but a consumer MUST be able to handle the case ``strides[n] <= " +"0``. See `complex arrays`_ for further information." +msgstr "" + +#: ../Doc/c-api/buffer.rst:190 +msgid "The strides array is read-only for the consumer." +msgstr "" + +#: ../Doc/c-api/buffer.rst:194 +msgid "" +"An array of :c:type:`Py_ssize_t` of length :c:member:`~Py_buffer.ndim`. If " +"``suboffsets[n] >= 0``, the values stored along the nth dimension are " +"pointers and the suboffset value dictates how many bytes to add to each " +"pointer after de-referencing. A suboffset value that is negative indicates " +"that no de-referencing should occur (striding in a contiguous memory block)." +msgstr "" + +#: ../Doc/c-api/buffer.rst:201 +msgid "" +"If all suboffsets are negative (i.e. no de-referencing is needed, then this " +"field must be NULL (the default value)." +msgstr "" + +#: ../Doc/c-api/buffer.rst:204 +msgid "" +"This type of array representation is used by the Python Imaging Library " +"(PIL). See `complex arrays`_ for further information how to access elements " +"of such an array." +msgstr "" + +#: ../Doc/c-api/buffer.rst:208 +msgid "The suboffsets array is read-only for the consumer." +msgstr "" + +#: ../Doc/c-api/buffer.rst:212 +msgid "" +"This is for use internally by the exporting object. For example, this might " +"be re-cast as an integer by the exporter and used to store flags about " +"whether or not the shape, strides, and suboffsets arrays must be freed when " +"the buffer is released. The consumer MUST NOT alter this value." +msgstr "" + +#: ../Doc/c-api/buffer.rst:221 +msgid "Buffer request types" +msgstr "" + +#: ../Doc/c-api/buffer.rst:223 +msgid "" +"Buffers are usually obtained by sending a buffer request to an exporting " +"object via :c:func:`PyObject_GetBuffer`. Since the complexity of the logical " +"structure of the memory can vary drastically, the consumer uses the *flags* " +"argument to specify the exact buffer type it can handle." +msgstr "" + +#: ../Doc/c-api/buffer.rst:228 +msgid "" +"All :c:data:`Py_buffer` fields are unambiguously defined by the request type." +msgstr "" + +#: ../Doc/c-api/buffer.rst:232 +msgid "request-independent fields" +msgstr "" + +#: ../Doc/c-api/buffer.rst:233 +msgid "" +"The following fields are not influenced by *flags* and must always be filled " +"in with the correct values: :c:member:`~Py_buffer.obj`, :c:member:" +"`~Py_buffer.buf`, :c:member:`~Py_buffer.len`, :c:member:`~Py_buffer." +"itemsize`, :c:member:`~Py_buffer.ndim`." +msgstr "" + +#: ../Doc/c-api/buffer.rst:239 +msgid "readonly, format" +msgstr "" + +#: ../Doc/c-api/buffer.rst:243 +msgid "" +"Controls the :c:member:`~Py_buffer.readonly` field. If set, the exporter " +"MUST provide a writable buffer or else report failure. Otherwise, the " +"exporter MAY provide either a read-only or writable buffer, but the choice " +"MUST be consistent for all consumers." +msgstr "" + +#: ../Doc/c-api/buffer.rst:250 +msgid "" +"Controls the :c:member:`~Py_buffer.format` field. If set, this field MUST be " +"filled in correctly. Otherwise, this field MUST be *NULL*." +msgstr "" + +#: ../Doc/c-api/buffer.rst:254 +msgid "" +":c:macro:`PyBUF_WRITABLE` can be \\|'d to any of the flags in the next " +"section. Since :c:macro:`PyBUF_SIMPLE` is defined as 0, :c:macro:" +"`PyBUF_WRITABLE` can be used as a stand-alone flag to request a simple " +"writable buffer." +msgstr "" + +#: ../Doc/c-api/buffer.rst:258 +msgid "" +":c:macro:`PyBUF_FORMAT` can be \\|'d to any of the flags except :c:macro:" +"`PyBUF_SIMPLE`. The latter already implies format ``B`` (unsigned bytes)." +msgstr "" + +#: ../Doc/c-api/buffer.rst:263 +msgid "shape, strides, suboffsets" +msgstr "" + +#: ../Doc/c-api/buffer.rst:265 +msgid "" +"The flags that control the logical structure of the memory are listed in " +"decreasing order of complexity. Note that each flag contains all bits of the " +"flags below it." +msgstr "" + +#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296 +#: ../Doc/c-api/buffer.rst:321 +msgid "Request" +msgstr "" + +#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296 +#: ../Doc/c-api/buffer.rst:321 +msgid "shape" +msgstr "" + +#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296 +#: ../Doc/c-api/buffer.rst:321 +msgid "strides" +msgstr "" + +#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296 +#: ../Doc/c-api/buffer.rst:321 +msgid "suboffsets" +msgstr "" + +#: ../Doc/c-api/buffer.rst:274 ../Doc/c-api/buffer.rst:276 +#: ../Doc/c-api/buffer.rst:278 ../Doc/c-api/buffer.rst:298 +#: ../Doc/c-api/buffer.rst:300 ../Doc/c-api/buffer.rst:302 +#: ../Doc/c-api/buffer.rst:304 ../Doc/c-api/buffer.rst:323 +#: ../Doc/c-api/buffer.rst:325 ../Doc/c-api/buffer.rst:327 +#: ../Doc/c-api/buffer.rst:329 ../Doc/c-api/buffer.rst:331 +#: ../Doc/c-api/buffer.rst:333 ../Doc/c-api/buffer.rst:335 +#: ../Doc/c-api/buffer.rst:337 +msgid "yes" +msgstr "" + +#: ../Doc/c-api/buffer.rst:274 ../Doc/c-api/buffer.rst:323 +#: ../Doc/c-api/buffer.rst:325 +msgid "if needed" +msgstr "" + +#: ../Doc/c-api/buffer.rst:276 ../Doc/c-api/buffer.rst:278 +#: ../Doc/c-api/buffer.rst:280 ../Doc/c-api/buffer.rst:298 +#: ../Doc/c-api/buffer.rst:300 ../Doc/c-api/buffer.rst:302 +#: ../Doc/c-api/buffer.rst:304 ../Doc/c-api/buffer.rst:327 +#: ../Doc/c-api/buffer.rst:329 ../Doc/c-api/buffer.rst:331 +#: ../Doc/c-api/buffer.rst:333 ../Doc/c-api/buffer.rst:335 +#: ../Doc/c-api/buffer.rst:337 +msgid "NULL" +msgstr "" + +#: ../Doc/c-api/buffer.rst:287 +msgid "contiguity requests" +msgstr "" + +#: ../Doc/c-api/buffer.rst:289 +msgid "" +"C or Fortran :term:`contiguity ` can be explicitly requested, " +"with and without stride information. Without stride information, the buffer " +"must be C-contiguous." +msgstr "" + +#: ../Doc/c-api/buffer.rst:296 ../Doc/c-api/buffer.rst:321 +msgid "contig" +msgstr "" + +#: ../Doc/c-api/buffer.rst:298 ../Doc/c-api/buffer.rst:304 +#: ../Doc/c-api/buffer.rst:335 ../Doc/c-api/buffer.rst:337 +msgid "C" +msgstr "" + +#: ../Doc/c-api/buffer.rst:300 +msgid "F" +msgstr "" + +#: ../Doc/c-api/buffer.rst:302 +msgid "C or F" +msgstr "" + +#: ../Doc/c-api/buffer.rst:309 +msgid "compound requests" +msgstr "" + +#: ../Doc/c-api/buffer.rst:311 +msgid "" +"All possible requests are fully defined by some combination of the flags in " +"the previous section. For convenience, the buffer protocol provides " +"frequently used combinations as single flags." +msgstr "" + +#: ../Doc/c-api/buffer.rst:315 +msgid "" +"In the following table *U* stands for undefined contiguity. The consumer " +"would have to call :c:func:`PyBuffer_IsContiguous` to determine contiguity." +msgstr "" + +#: ../Doc/c-api/buffer.rst:321 +msgid "readonly" +msgstr "" + +#: ../Doc/c-api/buffer.rst:321 +msgid "format" +msgstr "" + +#: ../Doc/c-api/buffer.rst:323 ../Doc/c-api/buffer.rst:325 +#: ../Doc/c-api/buffer.rst:327 ../Doc/c-api/buffer.rst:329 +#: ../Doc/c-api/buffer.rst:331 ../Doc/c-api/buffer.rst:333 +msgid "U" +msgstr "" + +#: ../Doc/c-api/buffer.rst:323 ../Doc/c-api/buffer.rst:327 +#: ../Doc/c-api/buffer.rst:331 ../Doc/c-api/buffer.rst:335 +#: ../Doc/c-api/init.rst:1158 +msgid "0" +msgstr "" + +#: ../Doc/c-api/buffer.rst:325 ../Doc/c-api/buffer.rst:329 +#: ../Doc/c-api/buffer.rst:333 ../Doc/c-api/buffer.rst:337 +msgid "1 or 0" +msgstr "" + +#: ../Doc/c-api/buffer.rst:342 +msgid "Complex arrays" +msgstr "" + +#: ../Doc/c-api/buffer.rst:345 +msgid "NumPy-style: shape and strides" +msgstr "" + +#: ../Doc/c-api/buffer.rst:347 +msgid "" +"The logical structure of NumPy-style arrays is defined by :c:member:" +"`~Py_buffer.itemsize`, :c:member:`~Py_buffer.ndim`, :c:member:`~Py_buffer." +"shape` and :c:member:`~Py_buffer.strides`." +msgstr "" + +#: ../Doc/c-api/buffer.rst:350 +msgid "" +"If ``ndim == 0``, the memory location pointed to by :c:member:`~Py_buffer." +"buf` is interpreted as a scalar of size :c:member:`~Py_buffer.itemsize`. In " +"that case, both :c:member:`~Py_buffer.shape` and :c:member:`~Py_buffer." +"strides` are *NULL*." +msgstr "" + +#: ../Doc/c-api/buffer.rst:354 +msgid "" +"If :c:member:`~Py_buffer.strides` is *NULL*, the array is interpreted as a " +"standard n-dimensional C-array. Otherwise, the consumer must access an n-" +"dimensional array as follows:" +msgstr "" + +#: ../Doc/c-api/buffer.rst:358 +msgid "" +"``ptr = (char *)buf + indices[0] * strides[0] + ... + indices[n-1] * " +"strides[n-1]`` ``item = *((typeof(item) *)ptr);``" +msgstr "" + +#: ../Doc/c-api/buffer.rst:362 +msgid "" +"As noted above, :c:member:`~Py_buffer.buf` can point to any location within " +"the actual memory block. An exporter can check the validity of a buffer with " +"this function:" +msgstr "" + +#: ../Doc/c-api/buffer.rst:396 +msgid "PIL-style: shape, strides and suboffsets" +msgstr "" + +#: ../Doc/c-api/buffer.rst:398 +msgid "" +"In addition to the regular items, PIL-style arrays can contain pointers that " +"must be followed in order to get to the next element in a dimension. For " +"example, the regular three-dimensional C-array ``char v[2][2][3]`` can also " +"be viewed as an array of 2 pointers to 2 two-dimensional arrays: ``char " +"(*v[2])[2][3]``. In suboffsets representation, those two pointers can be " +"embedded at the start of :c:member:`~Py_buffer.buf`, pointing to two ``char " +"x[2][3]`` arrays that can be located anywhere in memory." +msgstr "" + +#: ../Doc/c-api/buffer.rst:407 +msgid "" +"Here is a function that returns a pointer to the element in an N-D array " +"pointed to by an N-dimensional index when there are both non-NULL strides " +"and suboffsets::" +msgstr "" + +#: ../Doc/c-api/buffer.rst:426 +msgid "Buffer-related functions" +msgstr "" + +#: ../Doc/c-api/buffer.rst:430 +msgid "" +"Return 1 if *obj* supports the buffer interface otherwise 0. When 1 is " +"returned, it doesn't guarantee that :c:func:`PyObject_GetBuffer` will " +"succeed." +msgstr "" + +#: ../Doc/c-api/buffer.rst:437 +msgid "" +"Send a request to *exporter* to fill in *view* as specified by *flags*. If " +"the exporter cannot provide a buffer of the exact type, it MUST raise :c:" +"data:`PyExc_BufferError`, set :c:member:`view->obj` to *NULL* and return -1." +msgstr "" + +#: ../Doc/c-api/buffer.rst:442 +msgid "" +"On success, fill in *view*, set :c:member:`view->obj` to a new reference to " +"*exporter* and return 0. In the case of chained buffer providers that " +"redirect requests to a single object, :c:member:`view->obj` MAY refer to " +"this object instead of *exporter* (See :ref:`Buffer Object Structures " +"`)." +msgstr "" + +#: ../Doc/c-api/buffer.rst:447 +msgid "" +"Successful calls to :c:func:`PyObject_GetBuffer` must be paired with calls " +"to :c:func:`PyBuffer_Release`, similar to :c:func:`malloc` and :c:func:" +"`free`. Thus, after the consumer is done with the buffer, :c:func:" +"`PyBuffer_Release` must be called exactly once." +msgstr "" + +#: ../Doc/c-api/buffer.rst:455 +msgid "" +"Release the buffer *view* and decrement the reference count for :c:member:" +"`view->obj`. This function MUST be called when the buffer is no longer being " +"used, otherwise reference leaks may occur." +msgstr "" + +#: ../Doc/c-api/buffer.rst:459 +msgid "" +"It is an error to call this function on a buffer that was not obtained via :" +"c:func:`PyObject_GetBuffer`." +msgstr "" + +#: ../Doc/c-api/buffer.rst:465 +msgid "" +"Return the implied :c:data:`~Py_buffer.itemsize` from :c:data:`~Py_buffer." +"format`. This function is not yet implemented." +msgstr "" + +#: ../Doc/c-api/buffer.rst:471 +msgid "" +"Return 1 if the memory defined by the *view* is C-style (*order* is ``'C'``) " +"or Fortran-style (*order* is ``'F'``) :term:`contiguous` or either one " +"(*order* is ``'A'``). Return 0 otherwise." +msgstr "" + +#: ../Doc/c-api/buffer.rst:478 +msgid "" +"Fill the *strides* array with byte-strides of a :term:`contiguous` (C-style " +"if *order* is ``'C'`` or Fortran-style if *order* is ``'F'``) array of the " +"given shape with the given number of bytes per element." +msgstr "" + +#: ../Doc/c-api/buffer.rst:485 +msgid "" +"Handle buffer requests for an exporter that wants to expose *buf* of size " +"*len* with writability set according to *readonly*. *buf* is interpreted as " +"a sequence of unsigned bytes." +msgstr "" + +#: ../Doc/c-api/buffer.rst:489 +msgid "" +"The *flags* argument indicates the request type. This function always fills " +"in *view* as specified by flags, unless *buf* has been designated as read-" +"only and :c:macro:`PyBUF_WRITABLE` is set in *flags*." +msgstr "" + +#: ../Doc/c-api/buffer.rst:493 +msgid "" +"On success, set :c:member:`view->obj` to a new reference to *exporter* and " +"return 0. Otherwise, raise :c:data:`PyExc_BufferError`, set :c:member:`view-" +">obj` to *NULL* and return -1;" +msgstr "" + +#: ../Doc/c-api/buffer.rst:497 +msgid "" +"If this function is used as part of a :ref:`getbufferproc `, " +"*exporter* MUST be set to the exporting object and *flags* must be passed " +"unmodified. Otherwise, *exporter* MUST be NULL." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:6 +msgid "Byte Array Objects" +msgstr "" + +#: ../Doc/c-api/bytearray.rst:13 +msgid "" +"This subtype of :c:type:`PyObject` represents a Python bytearray object." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:18 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python bytearray " +"type; it is the same object as :class:`bytearray` in the Python layer." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:23 +msgid "Type check macros" +msgstr "" + +#: ../Doc/c-api/bytearray.rst:27 +msgid "" +"Return true if the object *o* is a bytearray object or an instance of a " +"subtype of the bytearray type." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:33 +msgid "" +"Return true if the object *o* is a bytearray object, but not an instance of " +"a subtype of the bytearray type." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:38 +msgid "Direct API functions" +msgstr "" + +#: ../Doc/c-api/bytearray.rst:42 +msgid "" +"Return a new bytearray object from any object, *o*, that implements the :ref:" +"`buffer protocol `." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:50 +msgid "" +"Create a new bytearray object from *string* and its length, *len*. On " +"failure, *NULL* is returned." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:56 +msgid "" +"Concat bytearrays *a* and *b* and return a new bytearray with the result." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:61 +msgid "Return the size of *bytearray* after checking for a *NULL* pointer." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:66 +msgid "" +"Return the contents of *bytearray* as a char array after checking for a " +"*NULL* pointer. The returned array always has an extra null byte appended." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:73 +msgid "Resize the internal buffer of *bytearray* to *len*." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:76 +msgid "Macros" +msgstr "" + +#: ../Doc/c-api/bytearray.rst:78 +msgid "These macros trade safety for speed and they don't check pointers." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:82 +msgid "Macro version of :c:func:`PyByteArray_AsString`." +msgstr "" + +#: ../Doc/c-api/bytearray.rst:87 +msgid "Macro version of :c:func:`PyByteArray_Size`." +msgstr "" + +#: ../Doc/c-api/bytes.rst:6 +msgid "Bytes Objects" +msgstr "" + +#: ../Doc/c-api/bytes.rst:8 +msgid "" +"These functions raise :exc:`TypeError` when expecting a bytes parameter and " +"are called with a non-bytes parameter." +msgstr "" + +#: ../Doc/c-api/bytes.rst:16 +msgid "This subtype of :c:type:`PyObject` represents a Python bytes object." +msgstr "" + +#: ../Doc/c-api/bytes.rst:21 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python bytes type; it " +"is the same object as :class:`bytes` in the Python layer." +msgstr "" + +#: ../Doc/c-api/bytes.rst:27 +msgid "" +"Return true if the object *o* is a bytes object or an instance of a subtype " +"of the bytes type." +msgstr "" + +#: ../Doc/c-api/bytes.rst:33 +msgid "" +"Return true if the object *o* is a bytes object, but not an instance of a " +"subtype of the bytes type." +msgstr "" + +#: ../Doc/c-api/bytes.rst:39 +msgid "" +"Return a new bytes object with a copy of the string *v* as value on success, " +"and *NULL* on failure. The parameter *v* must not be *NULL*; it will not be " +"checked." +msgstr "" + +#: ../Doc/c-api/bytes.rst:46 +msgid "" +"Return a new bytes object with a copy of the string *v* as value and length " +"*len* on success, and *NULL* on failure. If *v* is *NULL*, the contents of " +"the bytes object are uninitialized." +msgstr "" + +#: ../Doc/c-api/bytes.rst:53 +msgid "" +"Take a C :c:func:`printf`\\ -style *format* string and a variable number of " +"arguments, calculate the size of the resulting Python bytes object and " +"return a bytes object with the values formatted into it. The variable " +"arguments must be C types and must correspond exactly to the format " +"characters in the *format* string. The following format characters are " +"allowed:" +msgstr "" + +#: ../Doc/c-api/bytes.rst:68 ../Doc/c-api/unicode.rst:447 +msgid "Format Characters" +msgstr "" + +#: ../Doc/c-api/bytes.rst:68 ../Doc/c-api/unicode.rst:447 +msgid "Type" +msgstr "" + +#: ../Doc/c-api/bytes.rst:68 ../Doc/c-api/unicode.rst:447 +msgid "Comment" +msgstr "" + +#: ../Doc/c-api/bytes.rst:70 ../Doc/c-api/unicode.rst:449 +msgid ":attr:`%%`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:70 ../Doc/c-api/unicode.rst:449 +msgid "*n/a*" +msgstr "" + +#: ../Doc/c-api/bytes.rst:70 ../Doc/c-api/unicode.rst:449 +msgid "The literal % character." +msgstr "" + +#: ../Doc/c-api/bytes.rst:72 ../Doc/c-api/unicode.rst:451 +msgid ":attr:`%c`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:72 ../Doc/c-api/bytes.rst:75 +#: ../Doc/c-api/bytes.rst:93 ../Doc/c-api/bytes.rst:96 +#: ../Doc/c-api/structures.rst:136 ../Doc/c-api/structures.rst:245 +#: ../Doc/c-api/structures.rst:252 ../Doc/c-api/structures.rst:268 +#: ../Doc/c-api/unicode.rst:451 ../Doc/c-api/unicode.rst:454 +#: ../Doc/c-api/unicode.rst:487 ../Doc/c-api/unicode.rst:490 +msgid "int" +msgstr "" + +#: ../Doc/c-api/bytes.rst:72 +msgid "A single byte, represented as a C int." +msgstr "" + +#: ../Doc/c-api/bytes.rst:75 ../Doc/c-api/unicode.rst:454 +msgid ":attr:`%d`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:75 ../Doc/c-api/unicode.rst:454 +msgid "Exactly equivalent to ``printf(\"%d\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:78 ../Doc/c-api/unicode.rst:457 +msgid ":attr:`%u`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:78 ../Doc/c-api/structures.rst:278 +#: ../Doc/c-api/unicode.rst:457 +msgid "unsigned int" +msgstr "" + +#: ../Doc/c-api/bytes.rst:78 ../Doc/c-api/unicode.rst:457 +msgid "Exactly equivalent to ``printf(\"%u\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:81 ../Doc/c-api/unicode.rst:460 +msgid ":attr:`%ld`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:81 ../Doc/c-api/structures.rst:269 +#: ../Doc/c-api/unicode.rst:460 ../Doc/c-api/unicode.rst:463 +msgid "long" +msgstr "" + +#: ../Doc/c-api/bytes.rst:81 ../Doc/c-api/unicode.rst:460 +msgid "Exactly equivalent to ``printf(\"%ld\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:84 ../Doc/c-api/unicode.rst:466 +msgid ":attr:`%lu`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:84 ../Doc/c-api/structures.rst:280 +#: ../Doc/c-api/unicode.rst:466 +msgid "unsigned long" +msgstr "" + +#: ../Doc/c-api/bytes.rst:84 ../Doc/c-api/unicode.rst:466 +msgid "Exactly equivalent to ``printf(\"%lu\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:87 ../Doc/c-api/unicode.rst:478 +msgid ":attr:`%zd`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:87 ../Doc/c-api/structures.rst:248 +#: ../Doc/c-api/structures.rst:284 ../Doc/c-api/unicode.rst:478 +#: ../Doc/c-api/unicode.rst:481 +msgid "Py_ssize_t" +msgstr "" + +#: ../Doc/c-api/bytes.rst:87 ../Doc/c-api/unicode.rst:478 +msgid "Exactly equivalent to ``printf(\"%zd\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:90 ../Doc/c-api/unicode.rst:484 +msgid ":attr:`%zu`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:90 ../Doc/c-api/unicode.rst:484 +msgid "size_t" +msgstr "" + +#: ../Doc/c-api/bytes.rst:90 ../Doc/c-api/unicode.rst:484 +msgid "Exactly equivalent to ``printf(\"%zu\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:93 ../Doc/c-api/unicode.rst:487 +msgid ":attr:`%i`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:93 ../Doc/c-api/unicode.rst:487 +msgid "Exactly equivalent to ``printf(\"%i\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:96 ../Doc/c-api/unicode.rst:490 +msgid ":attr:`%x`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:96 ../Doc/c-api/unicode.rst:490 +msgid "Exactly equivalent to ``printf(\"%x\")``." +msgstr "" + +#: ../Doc/c-api/bytes.rst:99 ../Doc/c-api/unicode.rst:493 +msgid ":attr:`%s`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:99 ../Doc/c-api/unicode.rst:493 +msgid "char\\*" +msgstr "" + +#: ../Doc/c-api/bytes.rst:99 ../Doc/c-api/unicode.rst:493 +msgid "A null-terminated C character array." +msgstr "" + +#: ../Doc/c-api/bytes.rst:102 ../Doc/c-api/unicode.rst:496 +msgid ":attr:`%p`" +msgstr "" + +#: ../Doc/c-api/bytes.rst:102 ../Doc/c-api/unicode.rst:496 +msgid "void\\*" +msgstr "" + +#: ../Doc/c-api/bytes.rst:102 ../Doc/c-api/unicode.rst:496 +msgid "" +"The hex representation of a C pointer. Mostly equivalent to ``printf(\"%p" +"\")`` except that it is guaranteed to start with the literal ``0x`` " +"regardless of what the platform's ``printf`` yields." +msgstr "" + +#: ../Doc/c-api/bytes.rst:111 +msgid "" +"An unrecognized format character causes all the rest of the format string to " +"be copied as-is to the result object, and any extra arguments discarded." +msgstr "" + +#: ../Doc/c-api/bytes.rst:117 +msgid "" +"Identical to :c:func:`PyBytes_FromFormat` except that it takes exactly two " +"arguments." +msgstr "" + +#: ../Doc/c-api/bytes.rst:123 +msgid "" +"Return the bytes representation of object *o* that implements the buffer " +"protocol." +msgstr "" + +#: ../Doc/c-api/bytes.rst:129 +msgid "Return the length of the bytes in bytes object *o*." +msgstr "" + +#: ../Doc/c-api/bytes.rst:134 +msgid "Macro form of :c:func:`PyBytes_Size` but without error checking." +msgstr "" + +#: ../Doc/c-api/bytes.rst:139 +msgid "" +"Return a pointer to the contents of *o*. The pointer refers to the internal " +"buffer of *o*, which consists of ``len(o) + 1`` bytes. The last byte in the " +"buffer is always null, regardless of whether there are any other null " +"bytes. The data must not be modified in any way, unless the object was just " +"created using ``PyBytes_FromStringAndSize(NULL, size)``. It must not be " +"deallocated. If *o* is not a bytes object at all, :c:func:" +"`PyBytes_AsString` returns *NULL* and raises :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/bytes.rst:151 +msgid "Macro form of :c:func:`PyBytes_AsString` but without error checking." +msgstr "" + +#: ../Doc/c-api/bytes.rst:156 +msgid "" +"Return the null-terminated contents of the object *obj* through the output " +"variables *buffer* and *length*." +msgstr "" + +#: ../Doc/c-api/bytes.rst:159 +msgid "" +"If *length* is *NULL*, the bytes object may not contain embedded null bytes; " +"if it does, the function returns ``-1`` and a :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/c-api/bytes.rst:163 +msgid "" +"The buffer refers to an internal buffer of *obj*, which includes an " +"additional null byte at the end (not counted in *length*). The data must " +"not be modified in any way, unless the object was just created using " +"``PyBytes_FromStringAndSize(NULL, size)``. It must not be deallocated. If " +"*obj* is not a bytes object at all, :c:func:`PyBytes_AsStringAndSize` " +"returns ``-1`` and raises :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/bytes.rst:170 +msgid "" +"Previously, :exc:`TypeError` was raised when embedded null bytes were " +"encountered in the bytes object." +msgstr "" + +#: ../Doc/c-api/bytes.rst:177 +msgid "" +"Create a new bytes object in *\\*bytes* containing the contents of *newpart* " +"appended to *bytes*; the caller will own the new reference. The reference " +"to the old value of *bytes* will be stolen. If the new object cannot be " +"created, the old reference to *bytes* will still be discarded and the value " +"of *\\*bytes* will be set to *NULL*; the appropriate exception will be set." +msgstr "" + +#: ../Doc/c-api/bytes.rst:186 +msgid "" +"Create a new bytes object in *\\*bytes* containing the contents of *newpart* " +"appended to *bytes*. This version decrements the reference count of " +"*newpart*." +msgstr "" + +#: ../Doc/c-api/bytes.rst:193 +msgid "" +"A way to resize a bytes object even though it is \"immutable\". Only use " +"this to build up a brand new bytes object; don't use this if the bytes may " +"already be known in other parts of the code. It is an error to call this " +"function if the refcount on the input bytes object is not one. Pass the " +"address of an existing bytes object as an lvalue (it may be written into), " +"and the new size desired. On success, *\\*bytes* holds the resized bytes " +"object and ``0`` is returned; the address in *\\*bytes* may differ from its " +"input value. If the reallocation fails, the original bytes object at *" +"\\*bytes* is deallocated, *\\*bytes* is set to *NULL*, :exc:`MemoryError` is " +"set, and ``-1`` is returned." +msgstr "" + +#: ../Doc/c-api/capsule.rst:6 +msgid "Capsules" +msgstr "" + +#: ../Doc/c-api/capsule.rst:10 +msgid "" +"Refer to :ref:`using-capsules` for more information on using these objects." +msgstr "" + +#: ../Doc/c-api/capsule.rst:15 +msgid "" +"This subtype of :c:type:`PyObject` represents an opaque value, useful for C " +"extension modules who need to pass an opaque value (as a :c:type:`void\\*` " +"pointer) through Python code to other C code. It is often used to make a C " +"function pointer defined in one module available to other modules, so the " +"regular import mechanism can be used to access C APIs defined in dynamically " +"loaded modules." +msgstr "" + +#: ../Doc/c-api/capsule.rst:24 +msgid "The type of a destructor callback for a capsule. Defined as::" +msgstr "" + +#: ../Doc/c-api/capsule.rst:28 +msgid "" +"See :c:func:`PyCapsule_New` for the semantics of PyCapsule_Destructor " +"callbacks." +msgstr "" + +#: ../Doc/c-api/capsule.rst:34 +msgid "Return true if its argument is a :c:type:`PyCapsule`." +msgstr "" + +#: ../Doc/c-api/capsule.rst:39 +msgid "" +"Create a :c:type:`PyCapsule` encapsulating the *pointer*. The *pointer* " +"argument may not be *NULL*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:42 +msgid "On failure, set an exception and return *NULL*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:44 +msgid "" +"The *name* string may either be *NULL* or a pointer to a valid C string. If " +"non-*NULL*, this string must outlive the capsule. (Though it is permitted " +"to free it inside the *destructor*.)" +msgstr "" + +#: ../Doc/c-api/capsule.rst:48 +msgid "" +"If the *destructor* argument is not *NULL*, it will be called with the " +"capsule as its argument when it is destroyed." +msgstr "" + +#: ../Doc/c-api/capsule.rst:51 +msgid "" +"If this capsule will be stored as an attribute of a module, the *name* " +"should be specified as ``modulename.attributename``. This will enable other " +"modules to import the capsule using :c:func:`PyCapsule_Import`." +msgstr "" + +#: ../Doc/c-api/capsule.rst:58 +msgid "" +"Retrieve the *pointer* stored in the capsule. On failure, set an exception " +"and return *NULL*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:61 +msgid "" +"The *name* parameter must compare exactly to the name stored in the capsule. " +"If the name stored in the capsule is *NULL*, the *name* passed in must also " +"be *NULL*. Python uses the C function :c:func:`strcmp` to compare capsule " +"names." +msgstr "" + +#: ../Doc/c-api/capsule.rst:69 +msgid "" +"Return the current destructor stored in the capsule. On failure, set an " +"exception and return *NULL*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:72 +msgid "" +"It is legal for a capsule to have a *NULL* destructor. This makes a *NULL* " +"return code somewhat ambiguous; use :c:func:`PyCapsule_IsValid` or :c:func:" +"`PyErr_Occurred` to disambiguate." +msgstr "" + +#: ../Doc/c-api/capsule.rst:79 +msgid "" +"Return the current context stored in the capsule. On failure, set an " +"exception and return *NULL*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:82 +msgid "" +"It is legal for a capsule to have a *NULL* context. This makes a *NULL* " +"return code somewhat ambiguous; use :c:func:`PyCapsule_IsValid` or :c:func:" +"`PyErr_Occurred` to disambiguate." +msgstr "" + +#: ../Doc/c-api/capsule.rst:89 +msgid "" +"Return the current name stored in the capsule. On failure, set an exception " +"and return *NULL*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:92 +msgid "" +"It is legal for a capsule to have a *NULL* name. This makes a *NULL* return " +"code somewhat ambiguous; use :c:func:`PyCapsule_IsValid` or :c:func:" +"`PyErr_Occurred` to disambiguate." +msgstr "" + +#: ../Doc/c-api/capsule.rst:99 +msgid "" +"Import a pointer to a C object from a capsule attribute in a module. The " +"*name* parameter should specify the full name to the attribute, as in " +"``module.attribute``. The *name* stored in the capsule must match this " +"string exactly. If *no_block* is true, import the module without blocking " +"(using :c:func:`PyImport_ImportModuleNoBlock`). If *no_block* is false, " +"import the module conventionally (using :c:func:`PyImport_ImportModule`)." +msgstr "" + +#: ../Doc/c-api/capsule.rst:106 +msgid "" +"Return the capsule's internal *pointer* on success. On failure, set an " +"exception and return *NULL*. However, if :c:func:`PyCapsule_Import` failed " +"to import the module, and *no_block* was true, no exception is set." +msgstr "" + +#: ../Doc/c-api/capsule.rst:112 +msgid "" +"Determines whether or not *capsule* is a valid capsule. A valid capsule is " +"non-*NULL*, passes :c:func:`PyCapsule_CheckExact`, has a non-*NULL* pointer " +"stored in it, and its internal name matches the *name* parameter. (See :c:" +"func:`PyCapsule_GetPointer` for information on how capsule names are " +"compared.)" +msgstr "" + +#: ../Doc/c-api/capsule.rst:118 +msgid "" +"In other words, if :c:func:`PyCapsule_IsValid` returns a true value, calls " +"to any of the accessors (any function starting with :c:func:`PyCapsule_Get`) " +"are guaranteed to succeed." +msgstr "" + +#: ../Doc/c-api/capsule.rst:122 +msgid "" +"Return a nonzero value if the object is valid and matches the name passed " +"in. Return 0 otherwise. This function will not fail." +msgstr "" + +#: ../Doc/c-api/capsule.rst:127 +msgid "Set the context pointer inside *capsule* to *context*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:129 ../Doc/c-api/capsule.rst:135 +#: ../Doc/c-api/capsule.rst:143 ../Doc/c-api/capsule.rst:150 +msgid "Return 0 on success. Return nonzero and set an exception on failure." +msgstr "" + +#: ../Doc/c-api/capsule.rst:133 +msgid "Set the destructor inside *capsule* to *destructor*." +msgstr "" + +#: ../Doc/c-api/capsule.rst:139 +msgid "" +"Set the name inside *capsule* to *name*. If non-*NULL*, the name must " +"outlive the capsule. If the previous *name* stored in the capsule was not " +"*NULL*, no attempt is made to free it." +msgstr "" + +#: ../Doc/c-api/capsule.rst:147 +msgid "" +"Set the void pointer inside *capsule* to *pointer*. The pointer may not be " +"*NULL*." +msgstr "" + +#: ../Doc/c-api/cell.rst:6 +msgid "Cell Objects" +msgstr "" + +#: ../Doc/c-api/cell.rst:8 +msgid "" +"\"Cell\" objects are used to implement variables referenced by multiple " +"scopes. For each such variable, a cell object is created to store the value; " +"the local variables of each stack frame that references the value contains a " +"reference to the cells from outer scopes which also use that variable. When " +"the value is accessed, the value contained in the cell is used instead of " +"the cell object itself. This de-referencing of the cell object requires " +"support from the generated byte-code; these are not automatically de-" +"referenced when accessed. Cell objects are not likely to be useful elsewhere." +msgstr "" + +#: ../Doc/c-api/cell.rst:20 +msgid "The C structure used for cell objects." +msgstr "" + +#: ../Doc/c-api/cell.rst:25 +msgid "The type object corresponding to cell objects." +msgstr "" + +#: ../Doc/c-api/cell.rst:30 +msgid "Return true if *ob* is a cell object; *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/cell.rst:35 +msgid "" +"Create and return a new cell object containing the value *ob*. The parameter " +"may be *NULL*." +msgstr "" + +#: ../Doc/c-api/cell.rst:41 +msgid "Return the contents of the cell *cell*." +msgstr "" + +#: ../Doc/c-api/cell.rst:46 +msgid "" +"Return the contents of the cell *cell*, but without checking that *cell* is " +"non-*NULL* and a cell object." +msgstr "" + +#: ../Doc/c-api/cell.rst:52 +msgid "" +"Set the contents of the cell object *cell* to *value*. This releases the " +"reference to any current content of the cell. *value* may be *NULL*. *cell* " +"must be non-*NULL*; if it is not a cell object, ``-1`` will be returned. On " +"success, ``0`` will be returned." +msgstr "" + +#: ../Doc/c-api/cell.rst:60 +msgid "" +"Sets the value of the cell object *cell* to *value*. No reference counts " +"are adjusted, and no checks are made for safety; *cell* must be non-*NULL* " +"and must be a cell object." +msgstr "" + +#: ../Doc/c-api/code.rst:8 +msgid "Code Objects" +msgstr "" + +#: ../Doc/c-api/code.rst:12 +msgid "" +"Code objects are a low-level detail of the CPython implementation. Each one " +"represents a chunk of executable code that hasn't yet been bound into a " +"function." +msgstr "" + +#: ../Doc/c-api/code.rst:18 +msgid "" +"The C structure of the objects used to describe code objects. The fields of " +"this type are subject to change at any time." +msgstr "" + +#: ../Doc/c-api/code.rst:24 +msgid "" +"This is an instance of :c:type:`PyTypeObject` representing the Python :class:" +"`code` type." +msgstr "" + +#: ../Doc/c-api/code.rst:30 +msgid "Return true if *co* is a :class:`code` object." +msgstr "" + +#: ../Doc/c-api/code.rst:34 +msgid "Return the number of free variables in *co*." +msgstr "" + +#: ../Doc/c-api/code.rst:38 +msgid "" +"Return a new code object. If you need a dummy code object to create a " +"frame, use :c:func:`PyCode_NewEmpty` instead. Calling :c:func:`PyCode_New` " +"directly can bind you to a precise Python version since the definition of " +"the bytecode changes often." +msgstr "" + +#: ../Doc/c-api/code.rst:46 +msgid "" +"Return a new empty code object with the specified filename, function name, " +"and first line number. It is illegal to :func:`exec` or :func:`eval` the " +"resulting code object." +msgstr "" + +#: ../Doc/c-api/codec.rst:4 +msgid "Codec registry and support functions" +msgstr "" + +#: ../Doc/c-api/codec.rst:8 +msgid "Register a new codec search function." +msgstr "" + +#: ../Doc/c-api/codec.rst:10 +msgid "" +"As side effect, this tries to load the :mod:`encodings` package, if not yet " +"done, to make sure that it is always first in the list of search functions." +msgstr "" + +#: ../Doc/c-api/codec.rst:15 +msgid "" +"Return ``1`` or ``0`` depending on whether there is a registered codec for " +"the given *encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:20 +msgid "Generic codec based encoding API." +msgstr "" + +#: ../Doc/c-api/codec.rst:22 +msgid "" +"*object* is passed through the encoder function found for the given " +"*encoding* using the error handling method defined by *errors*. *errors* " +"may be *NULL* to use the default method defined for the codec. Raises a :" +"exc:`LookupError` if no encoder can be found." +msgstr "" + +#: ../Doc/c-api/codec.rst:29 +msgid "Generic codec based decoding API." +msgstr "" + +#: ../Doc/c-api/codec.rst:31 +msgid "" +"*object* is passed through the decoder function found for the given " +"*encoding* using the error handling method defined by *errors*. *errors* " +"may be *NULL* to use the default method defined for the codec. Raises a :" +"exc:`LookupError` if no encoder can be found." +msgstr "" + +#: ../Doc/c-api/codec.rst:38 +msgid "Codec lookup API" +msgstr "" + +#: ../Doc/c-api/codec.rst:40 +msgid "" +"In the following functions, the *encoding* string is looked up converted to " +"all lower-case characters, which makes encodings looked up through this " +"mechanism effectively case-insensitive. If no codec is found, a :exc:" +"`KeyError` is set and *NULL* returned." +msgstr "" + +#: ../Doc/c-api/codec.rst:47 +msgid "Get an encoder function for the given *encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:51 +msgid "Get a decoder function for the given *encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:55 +msgid "" +"Get an :class:`~codecs.IncrementalEncoder` object for the given *encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:59 +msgid "" +"Get an :class:`~codecs.IncrementalDecoder` object for the given *encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:63 +msgid "" +"Get a :class:`~codecs.StreamReader` factory function for the given " +"*encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:67 +msgid "" +"Get a :class:`~codecs.StreamWriter` factory function for the given " +"*encoding*." +msgstr "" + +#: ../Doc/c-api/codec.rst:71 +msgid "Registry API for Unicode encoding error handlers" +msgstr "" + +#: ../Doc/c-api/codec.rst:75 +msgid "" +"Register the error handling callback function *error* under the given " +"*name*. This callback function will be called by a codec when it encounters " +"unencodable characters/undecodable bytes and *name* is specified as the " +"error parameter in the call to the encode/decode function." +msgstr "" + +#: ../Doc/c-api/codec.rst:80 +msgid "" +"The callback gets a single argument, an instance of :exc:" +"`UnicodeEncodeError`, :exc:`UnicodeDecodeError` or :exc:" +"`UnicodeTranslateError` that holds information about the problematic " +"sequence of characters or bytes and their offset in the original string " +"(see :ref:`unicodeexceptions` for functions to extract this information). " +"The callback must either raise the given exception, or return a two-item " +"tuple containing the replacement for the problematic sequence, and an " +"integer giving the offset in the original string at which encoding/decoding " +"should be resumed." +msgstr "" + +#: ../Doc/c-api/codec.rst:90 +msgid "Return ``0`` on success, ``-1`` on error." +msgstr "" + +#: ../Doc/c-api/codec.rst:94 +msgid "" +"Lookup the error handling callback function registered under *name*. As a " +"special case *NULL* can be passed, in which case the error handling callback " +"for \"strict\" will be returned." +msgstr "" + +#: ../Doc/c-api/codec.rst:100 +msgid "Raise *exc* as an exception." +msgstr "" + +#: ../Doc/c-api/codec.rst:104 +msgid "Ignore the unicode error, skipping the faulty input." +msgstr "" + +#: ../Doc/c-api/codec.rst:108 +msgid "Replace the unicode encode error with ``?`` or ``U+FFFD``." +msgstr "" + +#: ../Doc/c-api/codec.rst:112 +msgid "Replace the unicode encode error with XML character references." +msgstr "" + +#: ../Doc/c-api/codec.rst:116 +msgid "" +"Replace the unicode encode error with backslash escapes (``\\x``, ``\\u`` " +"and ``\\U``)." +msgstr "" + +#: ../Doc/c-api/codec.rst:121 +msgid "Replace the unicode encode error with ``\\N{...}`` escapes." +msgstr "" + +#: ../Doc/c-api/complex.rst:6 +msgid "Complex Number Objects" +msgstr "" + +#: ../Doc/c-api/complex.rst:10 +msgid "" +"Python's complex number objects are implemented as two distinct types when " +"viewed from the C API: one is the Python object exposed to Python programs, " +"and the other is a C structure which represents the actual complex number " +"value. The API provides functions for working with both." +msgstr "" + +#: ../Doc/c-api/complex.rst:17 +msgid "Complex Numbers as C Structures" +msgstr "" + +#: ../Doc/c-api/complex.rst:19 +msgid "" +"Note that the functions which accept these structures as parameters and " +"return them as results do so *by value* rather than dereferencing them " +"through pointers. This is consistent throughout the API." +msgstr "" + +#: ../Doc/c-api/complex.rst:26 +msgid "" +"The C structure which corresponds to the value portion of a Python complex " +"number object. Most of the functions for dealing with complex number " +"objects use structures of this type as input or output values, as " +"appropriate. It is defined as::" +msgstr "" + +#: ../Doc/c-api/complex.rst:39 +msgid "" +"Return the sum of two complex numbers, using the C :c:type:`Py_complex` " +"representation." +msgstr "" + +#: ../Doc/c-api/complex.rst:45 +msgid "" +"Return the difference between two complex numbers, using the C :c:type:" +"`Py_complex` representation." +msgstr "" + +#: ../Doc/c-api/complex.rst:51 +msgid "" +"Return the negation of the complex number *complex*, using the C :c:type:" +"`Py_complex` representation." +msgstr "" + +#: ../Doc/c-api/complex.rst:57 +msgid "" +"Return the product of two complex numbers, using the C :c:type:`Py_complex` " +"representation." +msgstr "" + +#: ../Doc/c-api/complex.rst:63 +msgid "" +"Return the quotient of two complex numbers, using the C :c:type:`Py_complex` " +"representation." +msgstr "" + +#: ../Doc/c-api/complex.rst:66 +msgid "" +"If *divisor* is null, this method returns zero and sets :c:data:`errno` to :" +"c:data:`EDOM`." +msgstr "" + +#: ../Doc/c-api/complex.rst:72 +msgid "" +"Return the exponentiation of *num* by *exp*, using the C :c:type:" +"`Py_complex` representation." +msgstr "" + +#: ../Doc/c-api/complex.rst:75 +msgid "" +"If *num* is null and *exp* is not a positive real number, this method " +"returns zero and sets :c:data:`errno` to :c:data:`EDOM`." +msgstr "" + +#: ../Doc/c-api/complex.rst:80 +msgid "Complex Numbers as Python Objects" +msgstr "" + +#: ../Doc/c-api/complex.rst:85 +msgid "" +"This subtype of :c:type:`PyObject` represents a Python complex number object." +msgstr "" + +#: ../Doc/c-api/complex.rst:90 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python complex number " +"type. It is the same object as :class:`complex` in the Python layer." +msgstr "" + +#: ../Doc/c-api/complex.rst:96 +msgid "" +"Return true if its argument is a :c:type:`PyComplexObject` or a subtype of :" +"c:type:`PyComplexObject`." +msgstr "" + +#: ../Doc/c-api/complex.rst:102 +msgid "" +"Return true if its argument is a :c:type:`PyComplexObject`, but not a " +"subtype of :c:type:`PyComplexObject`." +msgstr "" + +#: ../Doc/c-api/complex.rst:108 +msgid "" +"Create a new Python complex number object from a C :c:type:`Py_complex` " +"value." +msgstr "" + +#: ../Doc/c-api/complex.rst:113 +msgid "Return a new :c:type:`PyComplexObject` object from *real* and *imag*." +msgstr "" + +#: ../Doc/c-api/complex.rst:118 +msgid "Return the real part of *op* as a C :c:type:`double`." +msgstr "" + +#: ../Doc/c-api/complex.rst:123 +msgid "Return the imaginary part of *op* as a C :c:type:`double`." +msgstr "" + +#: ../Doc/c-api/complex.rst:128 +msgid "Return the :c:type:`Py_complex` value of the complex number *op*." +msgstr "" + +#: ../Doc/c-api/complex.rst:130 +msgid "" +"If *op* is not a Python complex number object but has a :meth:`__complex__` " +"method, this method will first be called to convert *op* to a Python complex " +"number object. Upon failure, this method returns ``-1.0`` as a real value." +msgstr "" + +#: ../Doc/c-api/concrete.rst:8 +msgid "Concrete Objects Layer" +msgstr "" + +#: ../Doc/c-api/concrete.rst:10 +msgid "" +"The functions in this chapter are specific to certain Python object types. " +"Passing them an object of the wrong type is not a good idea; if you receive " +"an object from a Python program and you are not sure that it has the right " +"type, you must perform a type check first; for example, to check that an " +"object is a dictionary, use :c:func:`PyDict_Check`. The chapter is " +"structured like the \"family tree\" of Python object types." +msgstr "" + +#: ../Doc/c-api/concrete.rst:19 +msgid "" +"While the functions described in this chapter carefully check the type of " +"the objects which are passed in, many of them do not check for *NULL* being " +"passed instead of a valid object. Allowing *NULL* to be passed in can cause " +"memory access violations and immediate termination of the interpreter." +msgstr "" + +#: ../Doc/c-api/concrete.rst:28 +msgid "Fundamental Objects" +msgstr "" + +#: ../Doc/c-api/concrete.rst:30 +msgid "" +"This section describes Python type objects and the singleton object ``None``." +msgstr "" + +#: ../Doc/c-api/concrete.rst:41 +msgid "Numeric Objects" +msgstr "" + +#: ../Doc/c-api/concrete.rst:56 +msgid "Sequence Objects" +msgstr "" + +#: ../Doc/c-api/concrete.rst:60 +msgid "" +"Generic operations on sequence objects were discussed in the previous " +"chapter; this section deals with the specific kinds of sequence objects that " +"are intrinsic to the Python language." +msgstr "" + +#: ../Doc/c-api/concrete.rst:78 +msgid "Container Objects" +msgstr "" + +#: ../Doc/c-api/concrete.rst:91 ../Doc/c-api/function.rst:6 +msgid "Function Objects" +msgstr "" + +#: ../Doc/c-api/concrete.rst:102 +msgid "Other Objects" +msgstr "" + +#: ../Doc/c-api/conversion.rst:6 +msgid "String conversion and formatting" +msgstr "" + +#: ../Doc/c-api/conversion.rst:8 +msgid "Functions for number conversion and formatted string output." +msgstr "" + +#: ../Doc/c-api/conversion.rst:13 +msgid "" +"Output not more than *size* bytes to *str* according to the format string " +"*format* and the extra arguments. See the Unix man page :manpage:" +"`snprintf(2)`." +msgstr "" + +#: ../Doc/c-api/conversion.rst:19 +msgid "" +"Output not more than *size* bytes to *str* according to the format string " +"*format* and the variable argument list *va*. Unix man page :manpage:" +"`vsnprintf(2)`." +msgstr "" + +#: ../Doc/c-api/conversion.rst:23 +msgid "" +":c:func:`PyOS_snprintf` and :c:func:`PyOS_vsnprintf` wrap the Standard C " +"library functions :c:func:`snprintf` and :c:func:`vsnprintf`. Their purpose " +"is to guarantee consistent behavior in corner cases, which the Standard C " +"functions do not." +msgstr "" + +#: ../Doc/c-api/conversion.rst:28 +msgid "" +"The wrappers ensure that *str*[*size*-1] is always ``'\\0'`` upon return. " +"They never write more than *size* bytes (including the trailing ``'\\0'``) " +"into str. Both functions require that ``str != NULL``, ``size > 0`` and " +"``format != NULL``." +msgstr "" + +#: ../Doc/c-api/conversion.rst:33 +msgid "" +"If the platform doesn't have :c:func:`vsnprintf` and the buffer size needed " +"to avoid truncation exceeds *size* by more than 512 bytes, Python aborts " +"with a *Py_FatalError*." +msgstr "" + +#: ../Doc/c-api/conversion.rst:37 +msgid "" +"The return value (*rv*) for these functions should be interpreted as follows:" +msgstr "" + +#: ../Doc/c-api/conversion.rst:39 +msgid "" +"When ``0 <= rv < size``, the output conversion was successful and *rv* " +"characters were written to *str* (excluding the trailing ``'\\0'`` byte at " +"*str*[*rv*])." +msgstr "" + +#: ../Doc/c-api/conversion.rst:43 +msgid "" +"When ``rv >= size``, the output conversion was truncated and a buffer with " +"``rv + 1`` bytes would have been needed to succeed. *str*[*size*-1] is " +"``'\\0'`` in this case." +msgstr "" + +#: ../Doc/c-api/conversion.rst:47 +msgid "" +"When ``rv < 0``, \"something bad happened.\" *str*[*size*-1] is ``'\\0'`` in " +"this case too, but the rest of *str* is undefined. The exact cause of the " +"error depends on the underlying platform." +msgstr "" + +#: ../Doc/c-api/conversion.rst:51 +msgid "" +"The following functions provide locale-independent string to number " +"conversions." +msgstr "" + +#: ../Doc/c-api/conversion.rst:56 +msgid "" +"Convert a string ``s`` to a :c:type:`double`, raising a Python exception on " +"failure. The set of accepted strings corresponds to the set of strings " +"accepted by Python's :func:`float` constructor, except that ``s`` must not " +"have leading or trailing whitespace. The conversion is independent of the " +"current locale." +msgstr "" + +#: ../Doc/c-api/conversion.rst:62 +msgid "" +"If ``endptr`` is ``NULL``, convert the whole string. Raise ValueError and " +"return ``-1.0`` if the string is not a valid representation of a floating-" +"point number." +msgstr "" + +#: ../Doc/c-api/conversion.rst:66 +msgid "" +"If endptr is not ``NULL``, convert as much of the string as possible and set " +"``*endptr`` to point to the first unconverted character. If no initial " +"segment of the string is the valid representation of a floating-point " +"number, set ``*endptr`` to point to the beginning of the string, raise " +"ValueError, and return ``-1.0``." +msgstr "" + +#: ../Doc/c-api/conversion.rst:73 +msgid "" +"If ``s`` represents a value that is too large to store in a float (for " +"example, ``\"1e500\"`` is such a string on many platforms) then if " +"``overflow_exception`` is ``NULL`` return ``Py_HUGE_VAL`` (with an " +"appropriate sign) and don't set any exception. Otherwise, " +"``overflow_exception`` must point to a Python exception object; raise that " +"exception and return ``-1.0``. In both cases, set ``*endptr`` to point to " +"the first character after the converted value." +msgstr "" + +#: ../Doc/c-api/conversion.rst:81 +msgid "" +"If any other error occurs during the conversion (for example an out-of-" +"memory error), set the appropriate Python exception and return ``-1.0``." +msgstr "" + +#: ../Doc/c-api/conversion.rst:90 +msgid "" +"Convert a :c:type:`double` *val* to a string using supplied *format_code*, " +"*precision*, and *flags*." +msgstr "" + +#: ../Doc/c-api/conversion.rst:93 +msgid "" +"*format_code* must be one of ``'e'``, ``'E'``, ``'f'``, ``'F'``, ``'g'``, " +"``'G'`` or ``'r'``. For ``'r'``, the supplied *precision* must be 0 and is " +"ignored. The ``'r'`` format code specifies the standard :func:`repr` format." +msgstr "" + +#: ../Doc/c-api/conversion.rst:98 +msgid "" +"*flags* can be zero or more of the values *Py_DTSF_SIGN*, " +"*Py_DTSF_ADD_DOT_0*, or *Py_DTSF_ALT*, or-ed together:" +msgstr "" + +#: ../Doc/c-api/conversion.rst:101 +msgid "" +"*Py_DTSF_SIGN* means to always precede the returned string with a sign " +"character, even if *val* is non-negative." +msgstr "" + +#: ../Doc/c-api/conversion.rst:104 +msgid "" +"*Py_DTSF_ADD_DOT_0* means to ensure that the returned string will not look " +"like an integer." +msgstr "" + +#: ../Doc/c-api/conversion.rst:107 +msgid "" +"*Py_DTSF_ALT* means to apply \"alternate\" formatting rules. See the " +"documentation for the :c:func:`PyOS_snprintf` ``'#'`` specifier for details." +msgstr "" + +#: ../Doc/c-api/conversion.rst:111 +msgid "" +"If *ptype* is non-NULL, then the value it points to will be set to one of " +"*Py_DTST_FINITE*, *Py_DTST_INFINITE*, or *Py_DTST_NAN*, signifying that " +"*val* is a finite number, an infinite number, or not a number, respectively." +msgstr "" + +#: ../Doc/c-api/conversion.rst:115 +msgid "" +"The return value is a pointer to *buffer* with the converted string or " +"*NULL* if the conversion failed. The caller is responsible for freeing the " +"returned string by calling :c:func:`PyMem_Free`." +msgstr "" + +#: ../Doc/c-api/conversion.rst:124 +msgid "" +"Case insensitive comparison of strings. The function works almost " +"identically to :c:func:`strcmp` except that it ignores the case." +msgstr "" + +#: ../Doc/c-api/conversion.rst:130 +msgid "" +"Case insensitive comparison of strings. The function works almost " +"identically to :c:func:`strncmp` except that it ignores the case." +msgstr "" + +#: ../Doc/c-api/coro.rst:6 +msgid "Coroutine Objects" +msgstr "" + +#: ../Doc/c-api/coro.rst:10 +msgid "" +"Coroutine objects are what functions declared with an ``async`` keyword " +"return." +msgstr "" + +#: ../Doc/c-api/coro.rst:16 +msgid "The C structure used for coroutine objects." +msgstr "" + +#: ../Doc/c-api/coro.rst:21 +msgid "The type object corresponding to coroutine objects." +msgstr "" + +#: ../Doc/c-api/coro.rst:26 +msgid "Return true if *ob*'s type is *PyCoro_Type*; *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/coro.rst:31 +msgid "" +"Create and return a new coroutine object based on the *frame* object, with " +"``__name__`` and ``__qualname__`` set to *name* and *qualname*. A reference " +"to *frame* is stolen by this function. The *frame* argument must not be " +"*NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:6 +msgid "DateTime Objects" +msgstr "" + +#: ../Doc/c-api/datetime.rst:8 +msgid "" +"Various date and time objects are supplied by the :mod:`datetime` module. " +"Before using any of these functions, the header file :file:`datetime.h` must " +"be included in your source (note that this is not included by :file:`Python." +"h`), and the macro :c:macro:`PyDateTime_IMPORT` must be invoked, usually as " +"part of the module initialisation function. The macro puts a pointer to a C " +"structure into a static variable, :c:data:`PyDateTimeAPI`, that is used by " +"the following macros." +msgstr "" + +#: ../Doc/c-api/datetime.rst:16 +msgid "Type-check macros:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:20 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_DateType` or a subtype " +"of :c:data:`PyDateTime_DateType`. *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:26 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_DateType`. *ob* must not " +"be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:32 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_DateTimeType` or a " +"subtype of :c:data:`PyDateTime_DateTimeType`. *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:38 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_DateTimeType`. *ob* must " +"not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:44 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_TimeType` or a subtype " +"of :c:data:`PyDateTime_TimeType`. *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:50 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_TimeType`. *ob* must not " +"be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:56 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_DeltaType` or a subtype " +"of :c:data:`PyDateTime_DeltaType`. *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:62 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_DeltaType`. *ob* must not " +"be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:68 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_TZInfoType` or a subtype " +"of :c:data:`PyDateTime_TZInfoType`. *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:74 +msgid "" +"Return true if *ob* is of type :c:data:`PyDateTime_TZInfoType`. *ob* must " +"not be *NULL*." +msgstr "" + +#: ../Doc/c-api/datetime.rst:78 +msgid "Macros to create objects:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:82 +msgid "" +"Return a ``datetime.date`` object with the specified year, month and day." +msgstr "" + +#: ../Doc/c-api/datetime.rst:87 +msgid "" +"Return a ``datetime.datetime`` object with the specified year, month, day, " +"hour, minute, second and microsecond." +msgstr "" + +#: ../Doc/c-api/datetime.rst:93 +msgid "" +"Return a ``datetime.time`` object with the specified hour, minute, second " +"and microsecond." +msgstr "" + +#: ../Doc/c-api/datetime.rst:99 +msgid "" +"Return a ``datetime.timedelta`` object representing the given number of " +"days, seconds and microseconds. Normalization is performed so that the " +"resulting number of microseconds and seconds lie in the ranges documented " +"for ``datetime.timedelta`` objects." +msgstr "" + +#: ../Doc/c-api/datetime.rst:105 +msgid "" +"Macros to extract fields from date objects. The argument must be an " +"instance of :c:data:`PyDateTime_Date`, including subclasses (such as :c:data:" +"`PyDateTime_DateTime`). The argument must not be *NULL*, and the type is " +"not checked:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:112 +msgid "Return the year, as a positive int." +msgstr "" + +#: ../Doc/c-api/datetime.rst:117 +msgid "Return the month, as an int from 1 through 12." +msgstr "" + +#: ../Doc/c-api/datetime.rst:122 +msgid "Return the day, as an int from 1 through 31." +msgstr "" + +#: ../Doc/c-api/datetime.rst:125 +msgid "" +"Macros to extract fields from datetime objects. The argument must be an " +"instance of :c:data:`PyDateTime_DateTime`, including subclasses. The " +"argument must not be *NULL*, and the type is not checked:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:131 ../Doc/c-api/datetime.rst:155 +msgid "Return the hour, as an int from 0 through 23." +msgstr "" + +#: ../Doc/c-api/datetime.rst:136 ../Doc/c-api/datetime.rst:160 +msgid "Return the minute, as an int from 0 through 59." +msgstr "" + +#: ../Doc/c-api/datetime.rst:141 ../Doc/c-api/datetime.rst:165 +msgid "Return the second, as an int from 0 through 59." +msgstr "" + +#: ../Doc/c-api/datetime.rst:146 ../Doc/c-api/datetime.rst:170 +msgid "Return the microsecond, as an int from 0 through 999999." +msgstr "" + +#: ../Doc/c-api/datetime.rst:149 +msgid "" +"Macros to extract fields from time objects. The argument must be an " +"instance of :c:data:`PyDateTime_Time`, including subclasses. The argument " +"must not be *NULL*, and the type is not checked:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:173 +msgid "" +"Macros to extract fields from time delta objects. The argument must be an " +"instance of :c:data:`PyDateTime_Delta`, including subclasses. The argument " +"must not be *NULL*, and the type is not checked:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:179 +msgid "Return the number of days, as an int from -999999999 to 999999999." +msgstr "" + +#: ../Doc/c-api/datetime.rst:186 +msgid "Return the number of seconds, as an int from 0 through 86399." +msgstr "" + +#: ../Doc/c-api/datetime.rst:193 +msgid "Return the number of microseconds, as an int from 0 through 999999." +msgstr "" + +#: ../Doc/c-api/datetime.rst:198 +msgid "Macros for the convenience of modules implementing the DB API:" +msgstr "" + +#: ../Doc/c-api/datetime.rst:202 +msgid "" +"Create and return a new ``datetime.datetime`` object given an argument tuple " +"suitable for passing to ``datetime.datetime.fromtimestamp()``." +msgstr "" + +#: ../Doc/c-api/datetime.rst:208 +msgid "" +"Create and return a new ``datetime.date`` object given an argument tuple " +"suitable for passing to ``datetime.date.fromtimestamp()``." +msgstr "" + +#: ../Doc/c-api/descriptor.rst:6 +msgid "Descriptor Objects" +msgstr "" + +#: ../Doc/c-api/descriptor.rst:8 +msgid "" +"\"Descriptors\" are objects that describe some attribute of an object. They " +"are found in the dictionary of type objects." +msgstr "" + +#: ../Doc/c-api/descriptor.rst:15 +msgid "The type object for the built-in descriptor types." +msgstr "" + +#: ../Doc/c-api/descriptor.rst:35 +msgid "" +"Return true if the descriptor objects *descr* describes a data attribute, or " +"false if it describes a method. *descr* must be a descriptor object; there " +"is no error checking." +msgstr "" + +#: ../Doc/c-api/dict.rst:6 +msgid "Dictionary Objects" +msgstr "" + +#: ../Doc/c-api/dict.rst:13 +msgid "" +"This subtype of :c:type:`PyObject` represents a Python dictionary object." +msgstr "" + +#: ../Doc/c-api/dict.rst:18 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python dictionary " +"type. This is the same object as :class:`dict` in the Python layer." +msgstr "" + +#: ../Doc/c-api/dict.rst:24 +msgid "" +"Return true if *p* is a dict object or an instance of a subtype of the dict " +"type." +msgstr "" + +#: ../Doc/c-api/dict.rst:30 +msgid "" +"Return true if *p* is a dict object, but not an instance of a subtype of the " +"dict type." +msgstr "" + +#: ../Doc/c-api/dict.rst:36 +msgid "Return a new empty dictionary, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/dict.rst:41 +msgid "" +"Return a :class:`types.MappingProxyType` object for a mapping which enforces " +"read-only behavior. This is normally used to create a view to prevent " +"modification of the dictionary for non-dynamic class types." +msgstr "" + +#: ../Doc/c-api/dict.rst:48 +msgid "Empty an existing dictionary of all key-value pairs." +msgstr "" + +#: ../Doc/c-api/dict.rst:53 +msgid "" +"Determine if dictionary *p* contains *key*. If an item in *p* is matches " +"*key*, return ``1``, otherwise return ``0``. On error, return ``-1``. This " +"is equivalent to the Python expression ``key in p``." +msgstr "" + +#: ../Doc/c-api/dict.rst:60 +msgid "Return a new dictionary that contains the same key-value pairs as *p*." +msgstr "" + +#: ../Doc/c-api/dict.rst:65 +msgid "" +"Insert *value* into the dictionary *p* with a key of *key*. *key* must be :" +"term:`hashable`; if it isn't, :exc:`TypeError` will be raised. Return ``0`` " +"on success or ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/dict.rst:74 +msgid "" +"Insert *value* into the dictionary *p* using *key* as a key. *key* should be " +"a :c:type:`char\\*`. The key object is created using " +"``PyUnicode_FromString(key)``. Return ``0`` on success or ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/dict.rst:82 +msgid "" +"Remove the entry in dictionary *p* with key *key*. *key* must be hashable; " +"if it isn't, :exc:`TypeError` is raised. Return ``0`` on success or ``-1`` " +"on failure." +msgstr "" + +#: ../Doc/c-api/dict.rst:89 +msgid "" +"Remove the entry in dictionary *p* which has a key specified by the string " +"*key*. Return ``0`` on success or ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/dict.rst:95 +msgid "" +"Return the object from dictionary *p* which has a key *key*. Return *NULL* " +"if the key *key* is not present, but *without* setting an exception." +msgstr "" + +#: ../Doc/c-api/dict.rst:101 +msgid "" +"Variant of :c:func:`PyDict_GetItem` that does not suppress exceptions. " +"Return *NULL* **with** an exception set if an exception occurred. Return " +"*NULL* **without** an exception set if the key wasn't present." +msgstr "" + +#: ../Doc/c-api/dict.rst:109 +msgid "" +"This is the same as :c:func:`PyDict_GetItem`, but *key* is specified as a :c:" +"type:`char\\*`, rather than a :c:type:`PyObject\\*`." +msgstr "" + +#: ../Doc/c-api/dict.rst:115 +msgid "" +"This is the same as the Python-level :meth:`dict.setdefault`. If present, " +"it returns the value corresponding to *key* from the dictionary *p*. If the " +"key is not in the dict, it is inserted with value *defaultobj* and " +"*defaultobj* is returned. This function evaluates the hash function of " +"*key* only once, instead of evaluating it independently for the lookup and " +"the insertion." +msgstr "" + +#: ../Doc/c-api/dict.rst:125 +msgid "" +"Return a :c:type:`PyListObject` containing all the items from the dictionary." +msgstr "" + +#: ../Doc/c-api/dict.rst:130 +msgid "" +"Return a :c:type:`PyListObject` containing all the keys from the dictionary." +msgstr "" + +#: ../Doc/c-api/dict.rst:135 +msgid "" +"Return a :c:type:`PyListObject` containing all the values from the " +"dictionary *p*." +msgstr "" + +#: ../Doc/c-api/dict.rst:143 +msgid "" +"Return the number of items in the dictionary. This is equivalent to " +"``len(p)`` on a dictionary." +msgstr "" + +#: ../Doc/c-api/dict.rst:149 +msgid "" +"Iterate over all key-value pairs in the dictionary *p*. The :c:type:" +"`Py_ssize_t` referred to by *ppos* must be initialized to ``0`` prior to the " +"first call to this function to start the iteration; the function returns " +"true for each pair in the dictionary, and false once all pairs have been " +"reported. The parameters *pkey* and *pvalue* should either point to :c:type:" +"`PyObject\\*` variables that will be filled in with each key and value, " +"respectively, or may be *NULL*. Any references returned through them are " +"borrowed. *ppos* should not be altered during iteration. Its value " +"represents offsets within the internal dictionary structure, and since the " +"structure is sparse, the offsets are not consecutive." +msgstr "" + +#: ../Doc/c-api/dict.rst:160 +msgid "For example::" +msgstr "" + +#: ../Doc/c-api/dict.rst:170 +msgid "" +"The dictionary *p* should not be mutated during iteration. It is safe to " +"modify the values of the keys as you iterate over the dictionary, but only " +"so long as the set of keys does not change. For example::" +msgstr "" + +#: ../Doc/c-api/dict.rst:195 +msgid "" +"Iterate over mapping object *b* adding key-value pairs to dictionary *a*. " +"*b* may be a dictionary, or any object supporting :c:func:`PyMapping_Keys` " +"and :c:func:`PyObject_GetItem`. If *override* is true, existing pairs in *a* " +"will be replaced if a matching key is found in *b*, otherwise pairs will " +"only be added if there is not a matching key in *a*. Return ``0`` on success " +"or ``-1`` if an exception was raised." +msgstr "" + +#: ../Doc/c-api/dict.rst:205 +msgid "" +"This is the same as ``PyDict_Merge(a, b, 1)`` in C, and is similar to ``a." +"update(b)`` in Python except that :c:func:`PyDict_Update` doesn't fall back " +"to the iterating over a sequence of key value pairs if the second argument " +"has no \"keys\" attribute. Return ``0`` on success or ``-1`` if an " +"exception was raised." +msgstr "" + +#: ../Doc/c-api/dict.rst:214 +msgid "" +"Update or merge into dictionary *a*, from the key-value pairs in *seq2*. " +"*seq2* must be an iterable object producing iterable objects of length 2, " +"viewed as key-value pairs. In case of duplicate keys, the last wins if " +"*override* is true, else the first wins. Return ``0`` on success or ``-1`` " +"if an exception was raised. Equivalent Python (except for the return value)::" +msgstr "" + +#: ../Doc/c-api/dict.rst:229 ../Doc/c-api/list.rst:149 +#: ../Doc/c-api/method.rst:99 ../Doc/c-api/set.rst:164 +#: ../Doc/c-api/tuple.rst:110 ../Doc/c-api/unicode.rst:202 +msgid "Clear the free list. Return the total number of freed items." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:8 +msgid "Exception Handling" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:10 +msgid "" +"The functions described in this chapter will let you handle and raise Python " +"exceptions. It is important to understand some of the basics of Python " +"exception handling. It works somewhat like the POSIX :c:data:`errno` " +"variable: there is a global indicator (per thread) of the last error that " +"occurred. Most C API functions don't clear this on success, but will set it " +"to indicate the cause of the error on failure. Most C API functions also " +"return an error indicator, usually *NULL* if they are supposed to return a " +"pointer, or ``-1`` if they return an integer (exception: the :c:func:`PyArg_" +"\\*` functions return ``1`` for success and ``0`` for failure)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:20 +msgid "" +"Concretely, the error indicator consists of three object pointers: the " +"exception's type, the exception's value, and the traceback object. Any of " +"those pointers can be NULL if non-set (although some combinations are " +"forbidden, for example you can't have a non-NULL traceback if the exception " +"type is NULL)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:26 +msgid "" +"When a function must fail because some function it called failed, it " +"generally doesn't set the error indicator; the function it called already " +"set it. It is responsible for either handling the error and clearing the " +"exception or returning after cleaning up any resources it holds (such as " +"object references or memory allocations); it should *not* continue normally " +"if it is not prepared to handle the error. If returning due to an error, it " +"is important to indicate to the caller that an error has been set. If the " +"error is not handled or carefully propagated, additional calls into the " +"Python/C API may not behave as intended and may fail in mysterious ways." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:37 +msgid "" +"The error indicator is **not** the result of :func:`sys.exc_info()`. The " +"former corresponds to an exception that is not yet caught (and is therefore " +"still propagating), while the latter returns an exception after it is caught " +"(and has therefore stopped propagating)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:44 +msgid "Printing and clearing" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:49 +msgid "" +"Clear the error indicator. If the error indicator is not set, there is no " +"effect." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:55 +msgid "" +"Print a standard traceback to ``sys.stderr`` and clear the error indicator. " +"Call this function only when the error indicator is set. (Otherwise it will " +"cause a fatal error!)" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:59 +msgid "" +"If *set_sys_last_vars* is nonzero, the variables :data:`sys.last_type`, :" +"data:`sys.last_value` and :data:`sys.last_traceback` will be set to the " +"type, value and traceback of the printed exception, respectively." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:66 +msgid "Alias for ``PyErr_PrintEx(1)``." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:71 +msgid "" +"This utility function prints a warning message to ``sys.stderr`` when an " +"exception has been set but it is impossible for the interpreter to actually " +"raise the exception. It is used, for example, when an exception occurs in " +"an :meth:`__del__` method." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:76 +msgid "" +"The function is called with a single argument *obj* that identifies the " +"context in which the unraisable exception occurred. If possible, the repr of " +"*obj* will be printed in the warning message." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:82 +msgid "Raising exceptions" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:84 +msgid "" +"These functions help you set the current thread's error indicator. For " +"convenience, some of these functions will always return a NULL pointer for " +"use in a ``return`` statement." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:91 +msgid "" +"This is the most common way to set the error indicator. The first argument " +"specifies the exception type; it is normally one of the standard exceptions, " +"e.g. :c:data:`PyExc_RuntimeError`. You need not increment its reference " +"count. The second argument is an error message; it is decoded from " +"``'utf-8``'." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:99 +msgid "" +"This function is similar to :c:func:`PyErr_SetString` but lets you specify " +"an arbitrary Python object for the \"value\" of the exception." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:105 +msgid "" +"This function sets the error indicator and returns *NULL*. *exception* " +"should be a Python exception class. The *format* and subsequent parameters " +"help format the error message; they have the same meaning and values as in :" +"c:func:`PyUnicode_FromFormat`. *format* is an ASCII-encoded string." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:114 +msgid "" +"Same as :c:func:`PyErr_Format`, but taking a :c:type:`va_list` argument " +"rather than a variable number of arguments." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:122 +msgid "This is a shorthand for ``PyErr_SetObject(type, Py_None)``." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:127 +msgid "" +"This is a shorthand for ``PyErr_SetString(PyExc_TypeError, message)``, where " +"*message* indicates that a built-in operation was invoked with an illegal " +"argument. It is mostly for internal use." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:134 +msgid "" +"This is a shorthand for ``PyErr_SetNone(PyExc_MemoryError)``; it returns " +"*NULL* so an object allocation function can write ``return PyErr_NoMemory();" +"`` when it runs out of memory." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:143 +msgid "" +"This is a convenience function to raise an exception when a C library " +"function has returned an error and set the C variable :c:data:`errno`. It " +"constructs a tuple object whose first item is the integer :c:data:`errno` " +"value and whose second item is the corresponding error message (gotten from :" +"c:func:`strerror`), and then calls ``PyErr_SetObject(type, object)``. On " +"Unix, when the :c:data:`errno` value is :const:`EINTR`, indicating an " +"interrupted system call, this calls :c:func:`PyErr_CheckSignals`, and if " +"that set the error indicator, leaves it set to that. The function always " +"returns *NULL*, so a wrapper function around a system call can write " +"``return PyErr_SetFromErrno(type);`` when the system call returns an error." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:157 +msgid "" +"Similar to :c:func:`PyErr_SetFromErrno`, with the additional behavior that " +"if *filenameObject* is not *NULL*, it is passed to the constructor of *type* " +"as a third parameter. In the case of :exc:`OSError` exception, this is used " +"to define the :attr:`filename` attribute of the exception instance." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:166 +msgid "" +"Similar to :c:func:`PyErr_SetFromErrnoWithFilenameObject`, but takes a " +"second filename object, for raising errors when a function that takes two " +"filenames fails." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:175 +msgid "" +"Similar to :c:func:`PyErr_SetFromErrnoWithFilenameObject`, but the filename " +"is given as a C string. *filename* is decoded from the filesystem encoding " +"(:func:`os.fsdecode`)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:182 +msgid "" +"This is a convenience function to raise :exc:`WindowsError`. If called with " +"*ierr* of :c:data:`0`, the error code returned by a call to :c:func:" +"`GetLastError` is used instead. It calls the Win32 function :c:func:" +"`FormatMessage` to retrieve the Windows description of error code given by " +"*ierr* or :c:func:`GetLastError`, then it constructs a tuple object whose " +"first item is the *ierr* value and whose second item is the corresponding " +"error message (gotten from :c:func:`FormatMessage`), and then calls " +"``PyErr_SetObject(PyExc_WindowsError, object)``. This function always " +"returns *NULL*. Availability: Windows." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:194 +msgid "" +"Similar to :c:func:`PyErr_SetFromWindowsErr`, with an additional parameter " +"specifying the exception type to be raised. Availability: Windows." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:200 +msgid "" +"Similar to :c:func:`PyErr_SetFromWindowsErrWithFilenameObject`, but the " +"filename is given as a C string. *filename* is decoded from the filesystem " +"encoding (:func:`os.fsdecode`). Availability: Windows." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:207 +msgid "" +"Similar to :c:func:`PyErr_SetFromWindowsErrWithFilenameObject`, with an " +"additional parameter specifying the exception type to be raised. " +"Availability: Windows." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:214 +msgid "" +"Similar to :c:func:`PyErr_SetExcFromWindowsErrWithFilenameObject`, but " +"accepts a second filename object. Availability: Windows." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:223 +msgid "" +"Similar to :c:func:`PyErr_SetFromWindowsErrWithFilename`, with an additional " +"parameter specifying the exception type to be raised. Availability: Windows." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:229 +msgid "" +"This is a convenience function to raise :exc:`ImportError`. *msg* will be " +"set as the exception's message string. *name* and *path*, both of which can " +"be ``NULL``, will be set as the :exc:`ImportError`'s respective ``name`` and " +"``path`` attributes." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:239 +msgid "" +"Set file, line, and offset information for the current exception. If the " +"current exception is not a :exc:`SyntaxError`, then it sets additional " +"attributes, which make the exception printing subsystem think the exception " +"is a :exc:`SyntaxError`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:249 +msgid "" +"Like :c:func:`PyErr_SyntaxLocationObject`, but *filename* is a byte string " +"decoded from the filesystem encoding (:func:`os.fsdecode`)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:257 +msgid "" +"Like :c:func:`PyErr_SyntaxLocationEx`, but the col_offset parameter is " +"omitted." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:263 +msgid "" +"This is a shorthand for ``PyErr_SetString(PyExc_SystemError, message)``, " +"where *message* indicates that an internal operation (e.g. a Python/C API " +"function) was invoked with an illegal argument. It is mostly for internal " +"use." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:270 +msgid "Issuing warnings" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:272 +msgid "" +"Use these functions to issue warnings from C code. They mirror similar " +"functions exported by the Python :mod:`warnings` module. They normally " +"print a warning message to *sys.stderr*; however, it is also possible that " +"the user has specified that warnings are to be turned into errors, and in " +"that case they will raise an exception. It is also possible that the " +"functions raise an exception because of a problem with the warning " +"machinery. The return value is ``0`` if no exception is raised, or ``-1`` if " +"an exception is raised. (It is not possible to determine whether a warning " +"message is actually printed, nor what the reason is for the exception; this " +"is intentional.) If an exception is raised, the caller should do its normal " +"exception handling (for example, :c:func:`Py_DECREF` owned references and " +"return an error value)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:287 +msgid "" +"Issue a warning message. The *category* argument is a warning category (see " +"below) or *NULL*; the *message* argument is a UTF-8 encoded string. " +"*stack_level* is a positive number giving a number of stack frames; the " +"warning will be issued from the currently executing line of code in that " +"stack frame. A *stack_level* of 1 is the function calling :c:func:" +"`PyErr_WarnEx`, 2 is the function above that, and so forth." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:294 +msgid "" +"Warning categories must be subclasses of :c:data:`Warning`; the default " +"warning category is :c:data:`RuntimeWarning`. The standard Python warning " +"categories are available as global variables whose names are ``PyExc_`` " +"followed by the Python exception name. These have the type :c:type:`PyObject" +"\\*`; they are all class objects. Their names are :c:data:`PyExc_Warning`, :" +"c:data:`PyExc_UserWarning`, :c:data:`PyExc_UnicodeWarning`, :c:data:" +"`PyExc_DeprecationWarning`, :c:data:`PyExc_SyntaxWarning`, :c:data:" +"`PyExc_RuntimeWarning`, and :c:data:`PyExc_FutureWarning`. :c:data:" +"`PyExc_Warning` is a subclass of :c:data:`PyExc_Exception`; the other " +"warning categories are subclasses of :c:data:`PyExc_Warning`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:305 +msgid "" +"For information about warning control, see the documentation for the :mod:" +"`warnings` module and the :option:`-W` option in the command line " +"documentation. There is no C API for warning control." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:311 +msgid "" +"Much like :c:func:`PyErr_SetImportError` but this function allows for " +"specifying a subclass of :exc:`ImportError` to raise." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:319 +msgid "" +"Issue a warning message with explicit control over all warning attributes. " +"This is a straightforward wrapper around the Python function :func:`warnings." +"warn_explicit`, see there for more information. The *module* and *registry* " +"arguments may be set to *NULL* to get the default effect described there." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:330 +msgid "" +"Similar to :c:func:`PyErr_WarnExplicitObject` except that *message* and " +"*module* are UTF-8 encoded strings, and *filename* is decoded from the " +"filesystem encoding (:func:`os.fsdecode`)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:337 +msgid "" +"Function similar to :c:func:`PyErr_WarnEx`, but use :c:func:" +"`PyUnicode_FromFormat` to format the warning message. *format* is an ASCII-" +"encoded string." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:346 +msgid "" +"Function similar to :c:func:`PyErr_WarnFormat`, but *category* is :exc:" +"`ResourceWarning` and pass *source* to :func:`warnings.WarningMessage`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:353 +msgid "Querying the error indicator" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:357 +msgid "" +"Test whether the error indicator is set. If set, return the exception " +"*type* (the first argument to the last call to one of the :c:func:`PyErr_Set" +"\\*` functions or to :c:func:`PyErr_Restore`). If not set, return *NULL*. " +"You do not own a reference to the return value, so you do not need to :c:" +"func:`Py_DECREF` it." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:365 +msgid "" +"Do not compare the return value to a specific exception; use :c:func:" +"`PyErr_ExceptionMatches` instead, shown below. (The comparison could easily " +"fail since the exception may be an instance instead of a class, in the case " +"of a class exception, or it may be a subclass of the expected exception.)" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:373 +msgid "" +"Equivalent to ``PyErr_GivenExceptionMatches(PyErr_Occurred(), exc)``. This " +"should only be called when an exception is actually set; a memory access " +"violation will occur if no exception has been raised." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:380 +msgid "" +"Return true if the *given* exception matches the exception type in *exc*. " +"If *exc* is a class object, this also returns true when *given* is an " +"instance of a subclass. If *exc* is a tuple, all exception types in the " +"tuple (and recursively in subtuples) are searched for a match." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:388 +msgid "" +"Retrieve the error indicator into three variables whose addresses are " +"passed. If the error indicator is not set, set all three variables to " +"*NULL*. If it is set, it will be cleared and you own a reference to each " +"object retrieved. The value and traceback object may be *NULL* even when " +"the type object is not." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:395 +msgid "" +"This function is normally only used by code that needs to catch exceptions " +"or by code that needs to save and restore the error indicator temporarily, e." +"g.::" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:410 +msgid "" +"Set the error indicator from the three objects. If the error indicator is " +"already set, it is cleared first. If the objects are *NULL*, the error " +"indicator is cleared. Do not pass a *NULL* type and non-*NULL* value or " +"traceback. The exception type should be a class. Do not pass an invalid " +"exception type or value. (Violating these rules will cause subtle problems " +"later.) This call takes away a reference to each object: you must own a " +"reference to each object before the call and after the call you no longer " +"own these references. (If you don't understand this, don't use this " +"function. I warned you.)" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:422 +msgid "" +"This function is normally only used by code that needs to save and restore " +"the error indicator temporarily. Use :c:func:`PyErr_Fetch` to save the " +"current error indicator." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:429 +msgid "" +"Under certain circumstances, the values returned by :c:func:`PyErr_Fetch` " +"below can be \"unnormalized\", meaning that ``*exc`` is a class object but " +"``*val`` is not an instance of the same class. This function can be used " +"to instantiate the class in that case. If the values are already " +"normalized, nothing happens. The delayed normalization is implemented to " +"improve performance." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:437 +msgid "" +"This function *does not* implicitly set the ``__traceback__`` attribute on " +"the exception value. If setting the traceback appropriately is desired, the " +"following additional snippet is needed::" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:448 +msgid "" +"Retrieve the exception info, as known from ``sys.exc_info()``. This refers " +"to an exception that was *already caught*, not to an exception that was " +"freshly raised. Returns new references for the three objects, any of which " +"may be *NULL*. Does not modify the exception info state." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:455 +msgid "" +"This function is not normally used by code that wants to handle exceptions. " +"Rather, it can be used when code needs to save and restore the exception " +"state temporarily. Use :c:func:`PyErr_SetExcInfo` to restore or clear the " +"exception state." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:465 +msgid "" +"Set the exception info, as known from ``sys.exc_info()``. This refers to an " +"exception that was *already caught*, not to an exception that was freshly " +"raised. This function steals the references of the arguments. To clear the " +"exception state, pass *NULL* for all three arguments. For general rules " +"about the three arguments, see :c:func:`PyErr_Restore`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:473 +msgid "" +"This function is not normally used by code that wants to handle exceptions. " +"Rather, it can be used when code needs to save and restore the exception " +"state temporarily. Use :c:func:`PyErr_GetExcInfo` to read the exception " +"state." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:482 +msgid "Signal Handling" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:492 +msgid "" +"This function interacts with Python's signal handling. It checks whether a " +"signal has been sent to the processes and if so, invokes the corresponding " +"signal handler. If the :mod:`signal` module is supported, this can invoke a " +"signal handler written in Python. In all cases, the default effect for :" +"const:`SIGINT` is to raise the :exc:`KeyboardInterrupt` exception. If an " +"exception is raised the error indicator is set and the function returns " +"``-1``; otherwise the function returns ``0``. The error indicator may or " +"may not be cleared if it was previously set." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:508 +msgid "" +"This function simulates the effect of a :const:`SIGINT` signal arriving --- " +"the next time :c:func:`PyErr_CheckSignals` is called, :exc:" +"`KeyboardInterrupt` will be raised. It may be called without holding the " +"interpreter lock." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:518 +msgid "" +"This utility function specifies a file descriptor to which the signal number " +"is written as a single byte whenever a signal is received. *fd* must be non-" +"blocking. It returns the previous such file descriptor." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:522 +msgid "" +"The value ``-1`` disables the feature; this is the initial state. This is " +"equivalent to :func:`signal.set_wakeup_fd` in Python, but without any error " +"checking. *fd* should be a valid file descriptor. The function should only " +"be called from the main thread." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:527 +msgid "On Windows, the function now also supports socket handles." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:532 +msgid "Exception Classes" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:536 +msgid "" +"This utility function creates and returns a new exception class. The *name* " +"argument must be the name of the new exception, a C string of the form " +"``module.classname``. The *base* and *dict* arguments are normally *NULL*. " +"This creates a class object derived from :exc:`Exception` (accessible in C " +"as :c:data:`PyExc_Exception`)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:542 +msgid "" +"The :attr:`__module__` attribute of the new class is set to the first part " +"(up to the last dot) of the *name* argument, and the class name is set to " +"the last part (after the last dot). The *base* argument can be used to " +"specify alternate base classes; it can either be only one class or a tuple " +"of classes. The *dict* argument can be used to specify a dictionary of class " +"variables and methods." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:551 +msgid "" +"Same as :c:func:`PyErr_NewException`, except that the new exception class " +"can easily be given a docstring: If *doc* is non-*NULL*, it will be used as " +"the docstring for the exception class." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:559 +msgid "Exception Objects" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:563 +msgid "" +"Return the traceback associated with the exception as a new reference, as " +"accessible from Python through :attr:`__traceback__`. If there is no " +"traceback associated, this returns *NULL*." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:570 +msgid "" +"Set the traceback associated with the exception to *tb*. Use ``Py_None`` to " +"clear it." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:576 +msgid "" +"Return the context (another exception instance during whose handling *ex* " +"was raised) associated with the exception as a new reference, as accessible " +"from Python through :attr:`__context__`. If there is no context associated, " +"this returns *NULL*." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:584 +msgid "" +"Set the context associated with the exception to *ctx*. Use *NULL* to clear " +"it. There is no type check to make sure that *ctx* is an exception " +"instance. This steals a reference to *ctx*." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:591 +msgid "" +"Return the cause (either an exception instance, or :const:`None`, set by " +"``raise ... from ...``) associated with the exception as a new reference, as " +"accessible from Python through :attr:`__cause__`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:598 +msgid "" +"Set the cause associated with the exception to *cause*. Use *NULL* to clear " +"it. There is no type check to make sure that *cause* is either an exception " +"instance or :const:`None`. This steals a reference to *cause*." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:602 +msgid "" +":attr:`__suppress_context__` is implicitly set to ``True`` by this function." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:608 +msgid "Unicode Exception Objects" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:610 +msgid "" +"The following functions are used to create and modify Unicode exceptions " +"from C." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:614 +msgid "" +"Create a :class:`UnicodeDecodeError` object with the attributes *encoding*, " +"*object*, *length*, *start*, *end* and *reason*. *encoding* and *reason* are " +"UTF-8 encoded strings." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:620 +msgid "" +"Create a :class:`UnicodeEncodeError` object with the attributes *encoding*, " +"*object*, *length*, *start*, *end* and *reason*. *encoding* and *reason* are " +"UTF-8 encoded strings." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:626 +msgid "" +"Create a :class:`UnicodeTranslateError` object with the attributes *object*, " +"*length*, *start*, *end* and *reason*. *reason* is a UTF-8 encoded string." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:632 +msgid "Return the *encoding* attribute of the given exception object." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:638 +msgid "Return the *object* attribute of the given exception object." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:644 +msgid "" +"Get the *start* attribute of the given exception object and place it into *" +"\\*start*. *start* must not be *NULL*. Return ``0`` on success, ``-1`` on " +"failure." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:652 +msgid "" +"Set the *start* attribute of the given exception object to *start*. Return " +"``0`` on success, ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:659 +msgid "" +"Get the *end* attribute of the given exception object and place it into *" +"\\*end*. *end* must not be *NULL*. Return ``0`` on success, ``-1`` on " +"failure." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:667 +msgid "" +"Set the *end* attribute of the given exception object to *end*. Return " +"``0`` on success, ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:674 +msgid "Return the *reason* attribute of the given exception object." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:680 +msgid "" +"Set the *reason* attribute of the given exception object to *reason*. " +"Return ``0`` on success, ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:685 +msgid "Recursion Control" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:687 +msgid "" +"These two functions provide a way to perform safe recursive calls at the C " +"level, both in the core and in extension modules. They are needed if the " +"recursive code does not necessarily invoke Python code (which tracks its " +"recursion depth automatically)." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:694 +msgid "Marks a point where a recursive C-level call is about to be performed." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:696 +msgid "" +"If :const:`USE_STACKCHECK` is defined, this function checks if the OS stack " +"overflowed using :c:func:`PyOS_CheckStack`. In this is the case, it sets a :" +"exc:`MemoryError` and returns a nonzero value." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:700 +msgid "" +"The function then checks if the recursion limit is reached. If this is the " +"case, a :exc:`RecursionError` is set and a nonzero value is returned. " +"Otherwise, zero is returned." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:704 +msgid "" +"*where* should be a string such as ``\" in instance check\"`` to be " +"concatenated to the :exc:`RecursionError` message caused by the recursion " +"depth limit." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:710 +msgid "" +"Ends a :c:func:`Py_EnterRecursiveCall`. Must be called once for each " +"*successful* invocation of :c:func:`Py_EnterRecursiveCall`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:713 +msgid "" +"Properly implementing :c:member:`~PyTypeObject.tp_repr` for container types " +"requires special recursion handling. In addition to protecting the stack, :" +"c:member:`~PyTypeObject.tp_repr` also needs to track objects to prevent " +"cycles. The following two functions facilitate this functionality. " +"Effectively, these are the C equivalent to :func:`reprlib.recursive_repr`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:721 +msgid "" +"Called at the beginning of the :c:member:`~PyTypeObject.tp_repr` " +"implementation to detect cycles." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:724 +msgid "" +"If the object has already been processed, the function returns a positive " +"integer. In that case the :c:member:`~PyTypeObject.tp_repr` implementation " +"should return a string object indicating a cycle. As examples, :class:" +"`dict` objects return ``{...}`` and :class:`list` objects return ``[...]``." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:730 +msgid "" +"The function will return a negative integer if the recursion limit is " +"reached. In that case the :c:member:`~PyTypeObject.tp_repr` implementation " +"should typically return ``NULL``." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:734 +msgid "" +"Otherwise, the function returns zero and the :c:member:`~PyTypeObject." +"tp_repr` implementation can continue normally." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:739 +msgid "" +"Ends a :c:func:`Py_ReprEnter`. Must be called once for each invocation of :" +"c:func:`Py_ReprEnter` that returns zero." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:746 +msgid "Standard Exceptions" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:748 +msgid "" +"All standard Python exceptions are available as global variables whose names " +"are ``PyExc_`` followed by the Python exception name. These have the type :" +"c:type:`PyObject\\*`; they are all class objects. For completeness, here " +"are all the variables:" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:754 ../Doc/c-api/exceptions.rst:858 +msgid "C Name" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:754 +msgid "Python Name" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:754 ../Doc/c-api/exceptions.rst:858 +msgid "Notes" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:756 +msgid ":c:data:`PyExc_BaseException`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:756 +msgid ":exc:`BaseException`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:756 ../Doc/c-api/exceptions.rst:758 +#: ../Doc/c-api/exceptions.rst:760 ../Doc/c-api/exceptions.rst:762 +#: ../Doc/c-api/exceptions.rst:812 +msgid "\\(1)" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:758 +msgid ":c:data:`PyExc_Exception`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:758 +msgid ":exc:`Exception`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:760 +msgid ":c:data:`PyExc_ArithmeticError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:760 +msgid ":exc:`ArithmeticError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:762 +msgid ":c:data:`PyExc_LookupError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:762 +msgid ":exc:`LookupError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:764 +msgid ":c:data:`PyExc_AssertionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:764 +msgid ":exc:`AssertionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:766 +msgid ":c:data:`PyExc_AttributeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:766 +msgid ":exc:`AttributeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:768 +msgid ":c:data:`PyExc_BlockingIOError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:768 +msgid ":exc:`BlockingIOError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:770 +msgid ":c:data:`PyExc_BrokenPipeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:770 +msgid ":exc:`BrokenPipeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:772 +msgid ":c:data:`PyExc_ChildProcessError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:772 +msgid ":exc:`ChildProcessError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:774 +msgid ":c:data:`PyExc_ConnectionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:774 +msgid ":exc:`ConnectionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:776 +msgid ":c:data:`PyExc_ConnectionAbortedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:776 +msgid ":exc:`ConnectionAbortedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:778 +msgid ":c:data:`PyExc_ConnectionRefusedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:778 +msgid ":exc:`ConnectionRefusedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:780 +msgid ":c:data:`PyExc_ConnectionResetError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:780 +msgid ":exc:`ConnectionResetError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:782 +msgid ":c:data:`PyExc_FileExistsError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:782 +msgid ":exc:`FileExistsError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:784 +msgid ":c:data:`PyExc_FileNotFoundError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:784 +msgid ":exc:`FileNotFoundError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:786 +msgid ":c:data:`PyExc_EOFError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:786 +msgid ":exc:`EOFError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:788 +msgid ":c:data:`PyExc_FloatingPointError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:788 +msgid ":exc:`FloatingPointError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:790 +msgid ":c:data:`PyExc_ImportError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:790 +msgid ":exc:`ImportError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:792 +msgid ":c:data:`PyExc_ModuleNotFoundError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:792 +msgid ":exc:`ModuleNotFoundError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:794 +msgid ":c:data:`PyExc_IndexError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:794 +msgid ":exc:`IndexError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:796 +msgid ":c:data:`PyExc_InterruptedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:796 +msgid ":exc:`InterruptedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:798 +msgid ":c:data:`PyExc_IsADirectoryError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:798 +msgid ":exc:`IsADirectoryError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:800 +msgid ":c:data:`PyExc_KeyError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:800 +msgid ":exc:`KeyError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:802 +msgid ":c:data:`PyExc_KeyboardInterrupt`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:802 +msgid ":exc:`KeyboardInterrupt`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:804 +msgid ":c:data:`PyExc_MemoryError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:804 +msgid ":exc:`MemoryError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:806 +msgid ":c:data:`PyExc_NameError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:806 +msgid ":exc:`NameError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:808 +msgid ":c:data:`PyExc_NotADirectoryError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:808 +msgid ":exc:`NotADirectoryError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:810 +msgid ":c:data:`PyExc_NotImplementedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:810 +msgid ":exc:`NotImplementedError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:812 +msgid ":c:data:`PyExc_OSError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:812 +msgid ":exc:`OSError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:814 +msgid ":c:data:`PyExc_OverflowError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:814 +msgid ":exc:`OverflowError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:816 +msgid ":c:data:`PyExc_PermissionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:816 +msgid ":exc:`PermissionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:818 +msgid ":c:data:`PyExc_ProcessLookupError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:818 +msgid ":exc:`ProcessLookupError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:820 +msgid ":c:data:`PyExc_RecursionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:820 +msgid ":exc:`RecursionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:822 +msgid ":c:data:`PyExc_ReferenceError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:822 +msgid ":exc:`ReferenceError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:822 +msgid "\\(2)" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:824 +msgid ":c:data:`PyExc_RuntimeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:824 +msgid ":exc:`RuntimeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:826 +msgid ":c:data:`PyExc_SyntaxError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:826 +msgid ":exc:`SyntaxError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:828 +msgid ":c:data:`PyExc_SystemError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:828 +msgid ":exc:`SystemError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:830 +msgid ":c:data:`PyExc_TimeoutError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:830 +msgid ":exc:`TimeoutError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:832 +msgid ":c:data:`PyExc_SystemExit`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:832 +msgid ":exc:`SystemExit`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:834 +msgid ":c:data:`PyExc_TypeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:834 +msgid ":exc:`TypeError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:836 +msgid ":c:data:`PyExc_ValueError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:836 +msgid ":exc:`ValueError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:838 +msgid ":c:data:`PyExc_ZeroDivisionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:838 +msgid ":exc:`ZeroDivisionError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:841 +msgid "" +":c:data:`PyExc_BlockingIOError`, :c:data:`PyExc_BrokenPipeError`, :c:data:" +"`PyExc_ChildProcessError`, :c:data:`PyExc_ConnectionError`, :c:data:" +"`PyExc_ConnectionAbortedError`, :c:data:`PyExc_ConnectionRefusedError`, :c:" +"data:`PyExc_ConnectionResetError`, :c:data:`PyExc_FileExistsError`, :c:data:" +"`PyExc_FileNotFoundError`, :c:data:`PyExc_InterruptedError`, :c:data:" +"`PyExc_IsADirectoryError`, :c:data:`PyExc_NotADirectoryError`, :c:data:" +"`PyExc_PermissionError`, :c:data:`PyExc_ProcessLookupError` and :c:data:" +"`PyExc_TimeoutError` were introduced following :pep:`3151`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:851 +msgid ":c:data:`PyExc_RecursionError`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:855 +msgid "These are compatibility aliases to :c:data:`PyExc_OSError`:" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:860 +msgid ":c:data:`PyExc_EnvironmentError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:862 +msgid ":c:data:`PyExc_IOError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:864 +msgid ":c:data:`PyExc_WindowsError`" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:864 +msgid "\\(3)" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:867 +msgid "These aliases used to be separate exception types." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:916 +msgid "Notes:" +msgstr "" + +#: ../Doc/c-api/exceptions.rst:919 +msgid "This is a base class for other standard exceptions." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:922 +msgid "This is the same as :exc:`weakref.ReferenceError`." +msgstr "" + +#: ../Doc/c-api/exceptions.rst:925 +msgid "" +"Only defined on Windows; protect code that uses this by testing that the " +"preprocessor macro ``MS_WINDOWS`` is defined." +msgstr "" + +#: ../Doc/c-api/file.rst:6 +msgid "File Objects" +msgstr "" + +#: ../Doc/c-api/file.rst:10 +msgid "" +"These APIs are a minimal emulation of the Python 2 C API for built-in file " +"objects, which used to rely on the buffered I/O (:c:type:`FILE\\*`) support " +"from the C standard library. In Python 3, files and streams use the new :" +"mod:`io` module, which defines several layers over the low-level unbuffered " +"I/O of the operating system. The functions described below are convenience " +"C wrappers over these new APIs, and meant mostly for internal error " +"reporting in the interpreter; third-party code is advised to access the :mod:" +"`io` APIs instead." +msgstr "" + +#: ../Doc/c-api/file.rst:22 +msgid "" +"Create a Python file object from the file descriptor of an already opened " +"file *fd*. The arguments *name*, *encoding*, *errors* and *newline* can be " +"*NULL* to use the defaults; *buffering* can be *-1* to use the default. " +"*name* is ignored and kept for backward compatibility. Return *NULL* on " +"failure. For a more comprehensive description of the arguments, please refer " +"to the :func:`io.open` function documentation." +msgstr "" + +#: ../Doc/c-api/file.rst:31 +msgid "" +"Since Python streams have their own buffering layer, mixing them with OS-" +"level file descriptors can produce various issues (such as unexpected " +"ordering of data)." +msgstr "" + +#: ../Doc/c-api/file.rst:35 +msgid "Ignore *name* attribute." +msgstr "" + +#: ../Doc/c-api/file.rst:41 +msgid "" +"Return the file descriptor associated with *p* as an :c:type:`int`. If the " +"object is an integer, its value is returned. If not, the object's :meth:" +"`~io.IOBase.fileno` method is called if it exists; the method must return an " +"integer, which is returned as the file descriptor value. Sets an exception " +"and returns ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/file.rst:52 +msgid "" +"Equivalent to ``p.readline([n])``, this function reads one line from the " +"object *p*. *p* may be a file object or any object with a :meth:`~io.IOBase." +"readline` method. If *n* is ``0``, exactly one line is read, regardless of " +"the length of the line. If *n* is greater than ``0``, no more than *n* " +"bytes will be read from the file; a partial line can be returned. In both " +"cases, an empty string is returned if the end of the file is reached " +"immediately. If *n* is less than ``0``, however, one line is read " +"regardless of length, but :exc:`EOFError` is raised if the end of the file " +"is reached immediately." +msgstr "" + +#: ../Doc/c-api/file.rst:67 +msgid "" +"Write object *obj* to file object *p*. The only supported flag for *flags* " +"is :const:`Py_PRINT_RAW`; if given, the :func:`str` of the object is written " +"instead of the :func:`repr`. Return ``0`` on success or ``-1`` on failure; " +"the appropriate exception will be set." +msgstr "" + +#: ../Doc/c-api/file.rst:75 +msgid "" +"Write string *s* to file object *p*. Return ``0`` on success or ``-1`` on " +"failure; the appropriate exception will be set." +msgstr "" + +#: ../Doc/c-api/float.rst:6 +msgid "Floating Point Objects" +msgstr "" + +#: ../Doc/c-api/float.rst:13 +msgid "" +"This subtype of :c:type:`PyObject` represents a Python floating point object." +msgstr "" + +#: ../Doc/c-api/float.rst:18 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python floating point " +"type. This is the same object as :class:`float` in the Python layer." +msgstr "" + +#: ../Doc/c-api/float.rst:24 +msgid "" +"Return true if its argument is a :c:type:`PyFloatObject` or a subtype of :c:" +"type:`PyFloatObject`." +msgstr "" + +#: ../Doc/c-api/float.rst:30 +msgid "" +"Return true if its argument is a :c:type:`PyFloatObject`, but not a subtype " +"of :c:type:`PyFloatObject`." +msgstr "" + +#: ../Doc/c-api/float.rst:36 +msgid "" +"Create a :c:type:`PyFloatObject` object based on the string value in *str*, " +"or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/float.rst:42 +msgid "Create a :c:type:`PyFloatObject` object from *v*, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/float.rst:47 +msgid "" +"Return a C :c:type:`double` representation of the contents of *pyfloat*. If " +"*pyfloat* is not a Python floating point object but has a :meth:`__float__` " +"method, this method will first be called to convert *pyfloat* into a float. " +"This method returns ``-1.0`` upon failure, so one should call :c:func:" +"`PyErr_Occurred` to check for errors." +msgstr "" + +#: ../Doc/c-api/float.rst:56 +msgid "" +"Return a C :c:type:`double` representation of the contents of *pyfloat*, but " +"without error checking." +msgstr "" + +#: ../Doc/c-api/float.rst:62 +msgid "" +"Return a structseq instance which contains information about the precision, " +"minimum and maximum values of a float. It's a thin wrapper around the header " +"file :file:`float.h`." +msgstr "" + +#: ../Doc/c-api/float.rst:69 +msgid "" +"Return the maximum representable finite float *DBL_MAX* as C :c:type:" +"`double`." +msgstr "" + +#: ../Doc/c-api/float.rst:74 +msgid "" +"Return the minimum normalized positive float *DBL_MIN* as C :c:type:`double`." +msgstr "" + +#: ../Doc/c-api/float.rst:78 +msgid "" +"Clear the float free list. Return the number of items that could not be " +"freed." +msgstr "" + +#: ../Doc/c-api/function.rst:10 +msgid "There are a few functions specific to Python functions." +msgstr "" + +#: ../Doc/c-api/function.rst:15 +msgid "The C structure used for functions." +msgstr "" + +#: ../Doc/c-api/function.rst:22 +msgid "" +"This is an instance of :c:type:`PyTypeObject` and represents the Python " +"function type. It is exposed to Python programmers as ``types." +"FunctionType``." +msgstr "" + +#: ../Doc/c-api/function.rst:28 +msgid "" +"Return true if *o* is a function object (has type :c:data:" +"`PyFunction_Type`). The parameter must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/function.rst:34 +msgid "" +"Return a new function object associated with the code object *code*. " +"*globals* must be a dictionary with the global variables accessible to the " +"function." +msgstr "" + +#: ../Doc/c-api/function.rst:37 +msgid "" +"The function's docstring and name are retrieved from the code object. " +"*__module__* is retrieved from *globals*. The argument defaults, annotations " +"and closure are set to *NULL*. *__qualname__* is set to the same value as " +"the function's name." +msgstr "" + +#: ../Doc/c-api/function.rst:44 +msgid "" +"As :c:func:`PyFunction_New`, but also allows setting the function object's " +"``__qualname__`` attribute. *qualname* should be a unicode object or NULL; " +"if NULL, the ``__qualname__`` attribute is set to the same value as its " +"``__name__`` attribute." +msgstr "" + +#: ../Doc/c-api/function.rst:54 +msgid "Return the code object associated with the function object *op*." +msgstr "" + +#: ../Doc/c-api/function.rst:59 +msgid "Return the globals dictionary associated with the function object *op*." +msgstr "" + +#: ../Doc/c-api/function.rst:64 +msgid "" +"Return the *__module__* attribute of the function object *op*. This is " +"normally a string containing the module name, but can be set to any other " +"object by Python code." +msgstr "" + +#: ../Doc/c-api/function.rst:71 +msgid "" +"Return the argument default values of the function object *op*. This can be " +"a tuple of arguments or *NULL*." +msgstr "" + +#: ../Doc/c-api/function.rst:77 +msgid "" +"Set the argument default values for the function object *op*. *defaults* " +"must be *Py_None* or a tuple." +msgstr "" + +#: ../Doc/c-api/function.rst:80 ../Doc/c-api/function.rst:94 +#: ../Doc/c-api/function.rst:108 +msgid "Raises :exc:`SystemError` and returns ``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/function.rst:85 +msgid "" +"Return the closure associated with the function object *op*. This can be " +"*NULL* or a tuple of cell objects." +msgstr "" + +#: ../Doc/c-api/function.rst:91 +msgid "" +"Set the closure associated with the function object *op*. *closure* must be " +"*Py_None* or a tuple of cell objects." +msgstr "" + +#: ../Doc/c-api/function.rst:99 +msgid "" +"Return the annotations of the function object *op*. This can be a mutable " +"dictionary or *NULL*." +msgstr "" + +#: ../Doc/c-api/function.rst:105 +msgid "" +"Set the annotations for the function object *op*. *annotations* must be a " +"dictionary or *Py_None*." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:6 +msgid "Supporting Cyclic Garbage Collection" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:8 +msgid "" +"Python's support for detecting and collecting garbage which involves " +"circular references requires support from object types which are \"containers" +"\" for other objects which may also be containers. Types which do not store " +"references to other objects, or which only store references to atomic types " +"(such as numbers or strings), do not need to provide any explicit support " +"for garbage collection." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:15 +msgid "" +"To create a container type, the :c:member:`~PyTypeObject.tp_flags` field of " +"the type object must include the :const:`Py_TPFLAGS_HAVE_GC` and provide an " +"implementation of the :c:member:`~PyTypeObject.tp_traverse` handler. If " +"instances of the type are mutable, a :c:member:`~PyTypeObject.tp_clear` " +"implementation must also be provided." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:24 +msgid "" +"Objects with a type with this flag set must conform with the rules " +"documented here. For convenience these objects will be referred to as " +"container objects." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:28 +msgid "Constructors for container types must conform to two rules:" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:30 +msgid "" +"The memory for the object must be allocated using :c:func:`PyObject_GC_New` " +"or :c:func:`PyObject_GC_NewVar`." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:33 +msgid "" +"Once all the fields which may contain references to other containers are " +"initialized, it must call :c:func:`PyObject_GC_Track`." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:39 +msgid "" +"Analogous to :c:func:`PyObject_New` but for container objects with the :" +"const:`Py_TPFLAGS_HAVE_GC` flag set." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:45 +msgid "" +"Analogous to :c:func:`PyObject_NewVar` but for container objects with the :" +"const:`Py_TPFLAGS_HAVE_GC` flag set." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:51 +msgid "" +"Resize an object allocated by :c:func:`PyObject_NewVar`. Returns the " +"resized object or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:57 +msgid "" +"Adds the object *op* to the set of container objects tracked by the " +"collector. The collector can run at unexpected times so objects must be " +"valid while being tracked. This should be called once all the fields " +"followed by the :c:member:`~PyTypeObject.tp_traverse` handler become valid, " +"usually near the end of the constructor." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:66 +msgid "" +"A macro version of :c:func:`PyObject_GC_Track`. It should not be used for " +"extension modules." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:69 +msgid "" +"Similarly, the deallocator for the object must conform to a similar pair of " +"rules:" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:72 +msgid "" +"Before fields which refer to other containers are invalidated, :c:func:" +"`PyObject_GC_UnTrack` must be called." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:75 +msgid "" +"The object's memory must be deallocated using :c:func:`PyObject_GC_Del`." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:80 +msgid "" +"Releases memory allocated to an object using :c:func:`PyObject_GC_New` or :c:" +"func:`PyObject_GC_NewVar`." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:86 +msgid "" +"Remove the object *op* from the set of container objects tracked by the " +"collector. Note that :c:func:`PyObject_GC_Track` can be called again on " +"this object to add it back to the set of tracked objects. The deallocator (:" +"c:member:`~PyTypeObject.tp_dealloc` handler) should call this for the object " +"before any of the fields used by the :c:member:`~PyTypeObject.tp_traverse` " +"handler become invalid." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:95 +msgid "" +"A macro version of :c:func:`PyObject_GC_UnTrack`. It should not be used for " +"extension modules." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:98 +msgid "" +"The :c:member:`~PyTypeObject.tp_traverse` handler accepts a function " +"parameter of this type:" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:103 +msgid "" +"Type of the visitor function passed to the :c:member:`~PyTypeObject." +"tp_traverse` handler. The function should be called with an object to " +"traverse as *object* and the third parameter to the :c:member:`~PyTypeObject." +"tp_traverse` handler as *arg*. The Python core uses several visitor " +"functions to implement cyclic garbage detection; it's not expected that " +"users will need to write their own visitor functions." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:110 +msgid "" +"The :c:member:`~PyTypeObject.tp_traverse` handler must have the following " +"type:" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:115 +msgid "" +"Traversal function for a container object. Implementations must call the " +"*visit* function for each object directly contained by *self*, with the " +"parameters to *visit* being the contained object and the *arg* value passed " +"to the handler. The *visit* function must not be called with a *NULL* " +"object argument. If *visit* returns a non-zero value that value should be " +"returned immediately." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:122 +msgid "" +"To simplify writing :c:member:`~PyTypeObject.tp_traverse` handlers, a :c:" +"func:`Py_VISIT` macro is provided. In order to use this macro, the :c:" +"member:`~PyTypeObject.tp_traverse` implementation must name its arguments " +"exactly *visit* and *arg*:" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:129 +msgid "" +"If *o* is not *NULL*, call the *visit* callback, with arguments *o* and " +"*arg*. If *visit* returns a non-zero value, then return it. Using this " +"macro, :c:member:`~PyTypeObject.tp_traverse` handlers look like::" +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:142 +msgid "" +"The :c:member:`~PyTypeObject.tp_clear` handler must be of the :c:type:" +"`inquiry` type, or *NULL* if the object is immutable." +msgstr "" + +#: ../Doc/c-api/gcsupport.rst:148 +msgid "" +"Drop references that may have created reference cycles. Immutable objects " +"do not have to define this method since they can never directly create " +"reference cycles. Note that the object must still be valid after calling " +"this method (don't just call :c:func:`Py_DECREF` on a reference). The " +"collector will call this method if it detects that this object is involved " +"in a reference cycle." +msgstr "" + +#: ../Doc/c-api/gen.rst:6 +msgid "Generator Objects" +msgstr "" + +#: ../Doc/c-api/gen.rst:8 +msgid "" +"Generator objects are what Python uses to implement generator iterators. " +"They are normally created by iterating over a function that yields values, " +"rather than explicitly calling :c:func:`PyGen_New` or :c:func:" +"`PyGen_NewWithQualName`." +msgstr "" + +#: ../Doc/c-api/gen.rst:15 +msgid "The C structure used for generator objects." +msgstr "" + +#: ../Doc/c-api/gen.rst:20 +msgid "The type object corresponding to generator objects." +msgstr "" + +#: ../Doc/c-api/gen.rst:25 +msgid "Return true if *ob* is a generator object; *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/gen.rst:30 +msgid "Return true if *ob*'s type is *PyGen_Type*; *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/gen.rst:35 +msgid "" +"Create and return a new generator object based on the *frame* object. A " +"reference to *frame* is stolen by this function. The argument must not be " +"*NULL*." +msgstr "" + +#: ../Doc/c-api/gen.rst:41 +msgid "" +"Create and return a new generator object based on the *frame* object, with " +"``__name__`` and ``__qualname__`` set to *name* and *qualname*. A reference " +"to *frame* is stolen by this function. The *frame* argument must not be " +"*NULL*." +msgstr "" + +#: ../Doc/c-api/import.rst:6 +msgid "Importing Modules" +msgstr "" + +#: ../Doc/c-api/import.rst:16 +msgid "" +"This is a simplified interface to :c:func:`PyImport_ImportModuleEx` below, " +"leaving the *globals* and *locals* arguments set to *NULL* and *level* set " +"to 0. When the *name* argument contains a dot (when it specifies a " +"submodule of a package), the *fromlist* argument is set to the list " +"``['*']`` so that the return value is the named module rather than the top-" +"level package containing it as would otherwise be the case. (Unfortunately, " +"this has an additional side effect when *name* in fact specifies a " +"subpackage instead of a submodule: the submodules specified in the package's " +"``__all__`` variable are loaded.) Return a new reference to the imported " +"module, or *NULL* with an exception set on failure. A failing import of a " +"module doesn't leave the module in :data:`sys.modules`." +msgstr "" + +#: ../Doc/c-api/import.rst:28 ../Doc/c-api/import.rst:89 +msgid "This function always uses absolute imports." +msgstr "" + +#: ../Doc/c-api/import.rst:33 +msgid "This function is a deprecated alias of :c:func:`PyImport_ImportModule`." +msgstr "" + +#: ../Doc/c-api/import.rst:35 +msgid "" +"This function used to fail immediately when the import lock was held by " +"another thread. In Python 3.3 though, the locking scheme switched to per-" +"module locks for most purposes, so this function's special behaviour isn't " +"needed anymore." +msgstr "" + +#: ../Doc/c-api/import.rst:46 +msgid "" +"Import a module. This is best described by referring to the built-in Python " +"function :func:`__import__`." +msgstr "" + +#: ../Doc/c-api/import.rst:49 ../Doc/c-api/import.rst:65 +msgid "" +"The return value is a new reference to the imported module or top-level " +"package, or *NULL* with an exception set on failure. Like for :func:" +"`__import__`, the return value when a submodule of a package was requested " +"is normally the top-level package, unless a non-empty *fromlist* was given." +msgstr "" + +#: ../Doc/c-api/import.rst:55 +msgid "" +"Failing imports remove incomplete module objects, like with :c:func:" +"`PyImport_ImportModule`." +msgstr "" + +#: ../Doc/c-api/import.rst:61 +msgid "" +"Import a module. This is best described by referring to the built-in Python " +"function :func:`__import__`, as the standard :func:`__import__` function " +"calls this function directly." +msgstr "" + +#: ../Doc/c-api/import.rst:75 +msgid "" +"Similar to :c:func:`PyImport_ImportModuleLevelObject`, but the name is a " +"UTF-8 encoded string instead of a Unicode object." +msgstr "" + +#: ../Doc/c-api/import.rst:78 +msgid "Negative values for *level* are no longer accepted." +msgstr "" + +#: ../Doc/c-api/import.rst:83 +msgid "" +"This is a higher-level interface that calls the current \"import hook " +"function\" (with an explicit *level* of 0, meaning absolute import). It " +"invokes the :func:`__import__` function from the ``__builtins__`` of the " +"current globals. This means that the import is done using whatever import " +"hooks are installed in the current environment." +msgstr "" + +#: ../Doc/c-api/import.rst:94 +msgid "" +"Reload a module. Return a new reference to the reloaded module, or *NULL* " +"with an exception set on failure (the module still exists in this case)." +msgstr "" + +#: ../Doc/c-api/import.rst:100 +msgid "" +"Return the module object corresponding to a module name. The *name* " +"argument may be of the form ``package.module``. First check the modules " +"dictionary if there's one there, and if not, create a new one and insert it " +"in the modules dictionary. Return *NULL* with an exception set on failure." +msgstr "" + +#: ../Doc/c-api/import.rst:107 +msgid "" +"This function does not load or import the module; if the module wasn't " +"already loaded, you will get an empty module object. Use :c:func:" +"`PyImport_ImportModule` or one of its variants to import a module. Package " +"structures implied by a dotted name for *name* are not created if not " +"already present." +msgstr "" + +#: ../Doc/c-api/import.rst:117 +msgid "" +"Similar to :c:func:`PyImport_AddModuleObject`, but the name is a UTF-8 " +"encoded string instead of a Unicode object." +msgstr "" + +#: ../Doc/c-api/import.rst:125 +msgid "" +"Given a module name (possibly of the form ``package.module``) and a code " +"object read from a Python bytecode file or obtained from the built-in " +"function :func:`compile`, load the module. Return a new reference to the " +"module object, or *NULL* with an exception set if an error occurred. *name* " +"is removed from :attr:`sys.modules` in error cases, even if *name* was " +"already in :attr:`sys.modules` on entry to :c:func:" +"`PyImport_ExecCodeModule`. Leaving incompletely initialized modules in :" +"attr:`sys.modules` is dangerous, as imports of such modules have no way to " +"know that the module object is an unknown (and probably damaged with respect " +"to the module author's intents) state." +msgstr "" + +#: ../Doc/c-api/import.rst:135 +msgid "" +"The module's :attr:`__spec__` and :attr:`__loader__` will be set, if not set " +"already, with the appropriate values. The spec's loader will be set to the " +"module's ``__loader__`` (if set) and to an instance of :class:" +"`SourceFileLoader` otherwise." +msgstr "" + +#: ../Doc/c-api/import.rst:140 +msgid "" +"The module's :attr:`__file__` attribute will be set to the code object's :c:" +"member:`co_filename`. If applicable, :attr:`__cached__` will also be set." +msgstr "" + +#: ../Doc/c-api/import.rst:144 +msgid "" +"This function will reload the module if it was already imported. See :c:" +"func:`PyImport_ReloadModule` for the intended way to reload a module." +msgstr "" + +#: ../Doc/c-api/import.rst:147 +msgid "" +"If *name* points to a dotted name of the form ``package.module``, any " +"package structures not already created will still not be created." +msgstr "" + +#: ../Doc/c-api/import.rst:150 +msgid "" +"See also :c:func:`PyImport_ExecCodeModuleEx` and :c:func:" +"`PyImport_ExecCodeModuleWithPathnames`." +msgstr "" + +#: ../Doc/c-api/import.rst:156 +msgid "" +"Like :c:func:`PyImport_ExecCodeModule`, but the :attr:`__file__` attribute " +"of the module object is set to *pathname* if it is non-``NULL``." +msgstr "" + +#: ../Doc/c-api/import.rst:159 +msgid "See also :c:func:`PyImport_ExecCodeModuleWithPathnames`." +msgstr "" + +#: ../Doc/c-api/import.rst:164 +msgid "" +"Like :c:func:`PyImport_ExecCodeModuleEx`, but the :attr:`__cached__` " +"attribute of the module object is set to *cpathname* if it is non-``NULL``. " +"Of the three functions, this is the preferred one to use." +msgstr "" + +#: ../Doc/c-api/import.rst:173 +msgid "" +"Like :c:func:`PyImport_ExecCodeModuleObject`, but *name*, *pathname* and " +"*cpathname* are UTF-8 encoded strings. Attempts are also made to figure out " +"what the value for *pathname* should be from *cpathname* if the former is " +"set to ``NULL``." +msgstr "" + +#: ../Doc/c-api/import.rst:179 +msgid "" +"Uses :func:`imp.source_from_cache()` in calculating the source path if only " +"the bytecode path is provided." +msgstr "" + +#: ../Doc/c-api/import.rst:186 +msgid "" +"Return the magic number for Python bytecode files (a.k.a. :file:`.pyc` " +"file). The magic number should be present in the first four bytes of the " +"bytecode file, in little-endian byte order. Returns -1 on error." +msgstr "" + +#: ../Doc/c-api/import.rst:190 +msgid "Return value of -1 upon failure." +msgstr "" + +#: ../Doc/c-api/import.rst:196 +msgid "" +"Return the magic tag string for :pep:`3147` format Python bytecode file " +"names. Keep in mind that the value at ``sys.implementation.cache_tag`` is " +"authoritative and should be used instead of this function." +msgstr "" + +#: ../Doc/c-api/import.rst:204 +msgid "" +"Return the dictionary used for the module administration (a.k.a. ``sys." +"modules``). Note that this is a per-interpreter variable." +msgstr "" + +#: ../Doc/c-api/import.rst:210 +msgid "" +"Return a finder object for a :data:`sys.path`/:attr:`pkg.__path__` item " +"*path*, possibly by fetching it from the :data:`sys.path_importer_cache` " +"dict. If it wasn't yet cached, traverse :data:`sys.path_hooks` until a hook " +"is found that can handle the path item. Return ``None`` if no hook could; " +"this tells our caller that the :term:`path based finder` could not find a " +"finder for this path item. Cache the result in :data:`sys." +"path_importer_cache`. Return a new reference to the finder object." +msgstr "" + +#: ../Doc/c-api/import.rst:221 +msgid "Initialize the import mechanism. For internal use only." +msgstr "" + +#: ../Doc/c-api/import.rst:226 +msgid "Empty the module table. For internal use only." +msgstr "" + +#: ../Doc/c-api/import.rst:231 +msgid "Finalize the import mechanism. For internal use only." +msgstr "" + +#: ../Doc/c-api/import.rst:236 +msgid "For internal use only." +msgstr "" + +#: ../Doc/c-api/import.rst:241 +msgid "" +"Load a frozen module named *name*. Return ``1`` for success, ``0`` if the " +"module is not found, and ``-1`` with an exception set if the initialization " +"failed. To access the imported module on a successful load, use :c:func:" +"`PyImport_ImportModule`. (Note the misnomer --- this function would reload " +"the module if it was already imported.)" +msgstr "" + +#: ../Doc/c-api/import.rst:249 +msgid "The ``__file__`` attribute is no longer set on the module." +msgstr "" + +#: ../Doc/c-api/import.rst:255 +msgid "" +"Similar to :c:func:`PyImport_ImportFrozenModuleObject`, but the name is a " +"UTF-8 encoded string instead of a Unicode object." +msgstr "" + +#: ../Doc/c-api/import.rst:263 +msgid "" +"This is the structure type definition for frozen module descriptors, as " +"generated by the :program:`freeze` utility (see :file:`Tools/freeze/` in the " +"Python source distribution). Its definition, found in :file:`Include/import." +"h`, is::" +msgstr "" + +#: ../Doc/c-api/import.rst:277 +msgid "" +"This pointer is initialized to point to an array of :c:type:`struct _frozen` " +"records, terminated by one whose members are all *NULL* or zero. When a " +"frozen module is imported, it is searched in this table. Third-party code " +"could play tricks with this to provide a dynamically created collection of " +"frozen modules." +msgstr "" + +#: ../Doc/c-api/import.rst:285 +msgid "" +"Add a single module to the existing table of built-in modules. This is a " +"convenience wrapper around :c:func:`PyImport_ExtendInittab`, returning " +"``-1`` if the table could not be extended. The new module can be imported " +"by the name *name*, and uses the function *initfunc* as the initialization " +"function called on the first attempted import. This should be called " +"before :c:func:`Py_Initialize`." +msgstr "" + +#: ../Doc/c-api/import.rst:295 +msgid "" +"Structure describing a single entry in the list of built-in modules. Each " +"of these structures gives the name and initialization function for a module " +"built into the interpreter. The name is an ASCII encoded string. Programs " +"which embed Python may use an array of these structures in conjunction with :" +"c:func:`PyImport_ExtendInittab` to provide additional built-in modules. The " +"structure is defined in :file:`Include/import.h` as::" +msgstr "" + +#: ../Doc/c-api/import.rst:310 +msgid "" +"Add a collection of modules to the table of built-in modules. The *newtab* " +"array must end with a sentinel entry which contains *NULL* for the :attr:" +"`name` field; failure to provide the sentinel value can result in a memory " +"fault. Returns ``0`` on success or ``-1`` if insufficient memory could be " +"allocated to extend the internal table. In the event of failure, no modules " +"are added to the internal table. This should be called before :c:func:" +"`Py_Initialize`." +msgstr "" + +#: ../Doc/c-api/index.rst:5 +msgid "Python/C API Reference Manual" +msgstr "" + +#: ../Doc/c-api/index.rst:7 +msgid "" +"This manual documents the API used by C and C++ programmers who want to " +"write extension modules or embed Python. It is a companion to :ref:" +"`extending-index`, which describes the general principles of extension " +"writing but does not document the API functions in detail." +msgstr "" + +#: ../Doc/c-api/init.rst:8 +msgid "Initialization, Finalization, and Threads" +msgstr "" + +#: ../Doc/c-api/init.rst:12 +msgid "Initializing and finalizing the interpreter" +msgstr "" + +#: ../Doc/c-api/init.rst:30 +msgid "" +"Initialize the Python interpreter. In an application embedding Python, " +"this should be called before using any other Python/C API functions; with " +"the exception of :c:func:`Py_SetProgramName`, :c:func:`Py_SetPythonHome` " +"and :c:func:`Py_SetPath`. This initializes the table of loaded modules " +"(``sys.modules``), and creates the fundamental modules :mod:`builtins`, :mod:" +"`__main__` and :mod:`sys`. It also initializes the module search path " +"(``sys.path``). It does not set ``sys.argv``; use :c:func:`PySys_SetArgvEx` " +"for that. This is a no-op when called for a second time (without calling :c:" +"func:`Py_FinalizeEx` first). There is no return value; it is a fatal error " +"if the initialization fails." +msgstr "" + +#: ../Doc/c-api/init.rst:41 +msgid "" +"On Windows, changes the console mode from ``O_TEXT`` to ``O_BINARY``, which " +"will also affect non-Python uses of the console using the C Runtime." +msgstr "" + +#: ../Doc/c-api/init.rst:47 +msgid "" +"This function works like :c:func:`Py_Initialize` if *initsigs* is 1. If " +"*initsigs* is 0, it skips initialization registration of signal handlers, " +"which might be useful when Python is embedded." +msgstr "" + +#: ../Doc/c-api/init.rst:54 +msgid "" +"Return true (nonzero) when the Python interpreter has been initialized, " +"false (zero) if not. After :c:func:`Py_FinalizeEx` is called, this returns " +"false until :c:func:`Py_Initialize` is called again." +msgstr "" + +#: ../Doc/c-api/init.rst:61 +msgid "" +"Undo all initializations made by :c:func:`Py_Initialize` and subsequent use " +"of Python/C API functions, and destroy all sub-interpreters (see :c:func:" +"`Py_NewInterpreter` below) that were created and not yet destroyed since the " +"last call to :c:func:`Py_Initialize`. Ideally, this frees all memory " +"allocated by the Python interpreter. This is a no-op when called for a " +"second time (without calling :c:func:`Py_Initialize` again first). Normally " +"the return value is 0. If there were errors during finalization (flushing " +"buffered data), -1 is returned." +msgstr "" + +#: ../Doc/c-api/init.rst:70 +msgid "" +"This function is provided for a number of reasons. An embedding application " +"might want to restart Python without having to restart the application " +"itself. An application that has loaded the Python interpreter from a " +"dynamically loadable library (or DLL) might want to free all memory " +"allocated by Python before unloading the DLL. During a hunt for memory leaks " +"in an application a developer might want to free all memory allocated by " +"Python before exiting from the application." +msgstr "" + +#: ../Doc/c-api/init.rst:78 +msgid "" +"**Bugs and caveats:** The destruction of modules and objects in modules is " +"done in random order; this may cause destructors (:meth:`__del__` methods) " +"to fail when they depend on other objects (even functions) or modules. " +"Dynamically loaded extension modules loaded by Python are not unloaded. " +"Small amounts of memory allocated by the Python interpreter may not be freed " +"(if you find a leak, please report it). Memory tied up in circular " +"references between objects is not freed. Some memory allocated by extension " +"modules may not be freed. Some extensions may not work properly if their " +"initialization routine is called more than once; this can happen if an " +"application calls :c:func:`Py_Initialize` and :c:func:`Py_FinalizeEx` more " +"than once." +msgstr "" + +#: ../Doc/c-api/init.rst:94 +msgid "" +"This is a backwards-compatible version of :c:func:`Py_FinalizeEx` that " +"disregards the return value." +msgstr "" + +#: ../Doc/c-api/init.rst:99 +msgid "Process-wide parameters" +msgstr "" + +#: ../Doc/c-api/init.rst:109 +msgid "" +"This function should be called before :c:func:`Py_Initialize`, if it is " +"called at all. It specifies which encoding and error handling to use with " +"standard IO, with the same meanings as in :func:`str.encode`." +msgstr "" + +#: ../Doc/c-api/init.rst:113 +msgid "" +"It overrides :envvar:`PYTHONIOENCODING` values, and allows embedding code to " +"control IO encoding when the environment variable does not work." +msgstr "" + +#: ../Doc/c-api/init.rst:116 +msgid "" +"``encoding`` and/or ``errors`` may be NULL to use :envvar:`PYTHONIOENCODING` " +"and/or default values (depending on other settings)." +msgstr "" + +#: ../Doc/c-api/init.rst:120 +msgid "" +"Note that :data:`sys.stderr` always uses the \"backslashreplace\" error " +"handler, regardless of this (or any other) setting." +msgstr "" + +#: ../Doc/c-api/init.rst:123 +msgid "" +"If :c:func:`Py_FinalizeEx` is called, this function will need to be called " +"again in order to affect subsequent calls to :c:func:`Py_Initialize`." +msgstr "" + +#: ../Doc/c-api/init.rst:126 +msgid "" +"Returns 0 if successful, a nonzero value on error (e.g. calling after the " +"interpreter has already been initialized)." +msgstr "" + +#: ../Doc/c-api/init.rst:139 +msgid "" +"This function should be called before :c:func:`Py_Initialize` is called for " +"the first time, if it is called at all. It tells the interpreter the value " +"of the ``argv[0]`` argument to the :c:func:`main` function of the program " +"(converted to wide characters). This is used by :c:func:`Py_GetPath` and " +"some other functions below to find the Python run-time libraries relative to " +"the interpreter executable. The default value is ``'python'``. The " +"argument should point to a zero-terminated wide character string in static " +"storage whose contents will not change for the duration of the program's " +"execution. No code in the Python interpreter will change the contents of " +"this storage." +msgstr "" + +#: ../Doc/c-api/init.rst:150 ../Doc/c-api/init.rst:264 +#: ../Doc/c-api/init.rst:366 ../Doc/c-api/init.rst:393 +#: ../Doc/c-api/init.rst:410 +msgid "" +"Use :c:func:`Py_DecodeLocale` to decode a bytes string to get a :c:type:" +"`wchar_*` string." +msgstr "" + +#: ../Doc/c-api/init.rst:158 +msgid "" +"Return the program name set with :c:func:`Py_SetProgramName`, or the " +"default. The returned string points into static storage; the caller should " +"not modify its value." +msgstr "" + +#: ../Doc/c-api/init.rst:165 +msgid "" +"Return the *prefix* for installed platform-independent files. This is " +"derived through a number of complicated rules from the program name set " +"with :c:func:`Py_SetProgramName` and some environment variables; for " +"example, if the program name is ``'/usr/local/bin/python'``, the prefix is " +"``'/usr/local'``. The returned string points into static storage; the caller " +"should not modify its value. This corresponds to the :makevar:`prefix` " +"variable in the top-level :file:`Makefile` and the ``--prefix`` argument to " +"the :program:`configure` script at build time. The value is available to " +"Python code as ``sys.prefix``. It is only useful on Unix. See also the next " +"function." +msgstr "" + +#: ../Doc/c-api/init.rst:178 +msgid "" +"Return the *exec-prefix* for installed platform-*dependent* files. This is " +"derived through a number of complicated rules from the program name set " +"with :c:func:`Py_SetProgramName` and some environment variables; for " +"example, if the program name is ``'/usr/local/bin/python'``, the exec-prefix " +"is ``'/usr/local'``. The returned string points into static storage; the " +"caller should not modify its value. This corresponds to the :makevar:" +"`exec_prefix` variable in the top-level :file:`Makefile` and the ``--exec-" +"prefix`` argument to the :program:`configure` script at build time. The " +"value is available to Python code as ``sys.exec_prefix``. It is only useful " +"on Unix." +msgstr "" + +#: ../Doc/c-api/init.rst:188 +msgid "" +"Background: The exec-prefix differs from the prefix when platform dependent " +"files (such as executables and shared libraries) are installed in a " +"different directory tree. In a typical installation, platform dependent " +"files may be installed in the :file:`/usr/local/plat` subtree while platform " +"independent may be installed in :file:`/usr/local`." +msgstr "" + +#: ../Doc/c-api/init.rst:194 +msgid "" +"Generally speaking, a platform is a combination of hardware and software " +"families, e.g. Sparc machines running the Solaris 2.x operating system are " +"considered the same platform, but Intel machines running Solaris 2.x are " +"another platform, and Intel machines running Linux are yet another " +"platform. Different major revisions of the same operating system generally " +"also form different platforms. Non-Unix operating systems are a different " +"story; the installation strategies on those systems are so different that " +"the prefix and exec-prefix are meaningless, and set to the empty string. " +"Note that compiled Python bytecode files are platform independent (but not " +"independent from the Python version by which they were compiled!)." +msgstr "" + +#: ../Doc/c-api/init.rst:205 +msgid "" +"System administrators will know how to configure the :program:`mount` or :" +"program:`automount` programs to share :file:`/usr/local` between platforms " +"while having :file:`/usr/local/plat` be a different filesystem for each " +"platform." +msgstr "" + +#: ../Doc/c-api/init.rst:217 +msgid "" +"Return the full program name of the Python executable; this is computed as " +"a side-effect of deriving the default module search path from the program " +"name (set by :c:func:`Py_SetProgramName` above). The returned string points " +"into static storage; the caller should not modify its value. The value is " +"available to Python code as ``sys.executable``." +msgstr "" + +#: ../Doc/c-api/init.rst:231 +msgid "" +"Return the default module search path; this is computed from the program " +"name (set by :c:func:`Py_SetProgramName` above) and some environment " +"variables. The returned string consists of a series of directory names " +"separated by a platform dependent delimiter character. The delimiter " +"character is ``':'`` on Unix and Mac OS X, ``';'`` on Windows. The returned " +"string points into static storage; the caller should not modify its value. " +"The list :data:`sys.path` is initialized with this value on interpreter " +"startup; it can be (and usually is) modified later to change the search path " +"for loading modules." +msgstr "" + +#: ../Doc/c-api/init.rst:251 +msgid "" +"Set the default module search path. If this function is called before :c:" +"func:`Py_Initialize`, then :c:func:`Py_GetPath` won't attempt to compute a " +"default search path but uses the one provided instead. This is useful if " +"Python is embedded by an application that has full knowledge of the location " +"of all modules. The path components should be separated by the platform " +"dependent delimiter character, which is ``':'`` on Unix and Mac OS X, " +"``';'`` on Windows." +msgstr "" + +#: ../Doc/c-api/init.rst:259 +msgid "" +"This also causes :data:`sys.executable` to be set only to the raw program " +"name (see :c:func:`Py_SetProgramName`) and for :data:`sys.prefix` and :data:" +"`sys.exec_prefix` to be empty. It is up to the caller to modify these if " +"required after calling :c:func:`Py_Initialize`." +msgstr "" + +#: ../Doc/c-api/init.rst:267 +msgid "" +"The path argument is copied internally, so the caller may free it after the " +"call completes." +msgstr "" + +#: ../Doc/c-api/init.rst:273 +msgid "" +"Return the version of this Python interpreter. This is a string that looks " +"something like ::" +msgstr "" + +#: ../Doc/c-api/init.rst:280 +msgid "" +"The first word (up to the first space character) is the current Python " +"version; the first three characters are the major and minor version " +"separated by a period. The returned string points into static storage; the " +"caller should not modify its value. The value is available to Python code " +"as :data:`sys.version`." +msgstr "" + +#: ../Doc/c-api/init.rst:290 +msgid "" +"Return the platform identifier for the current platform. On Unix, this is " +"formed from the \"official\" name of the operating system, converted to " +"lower case, followed by the major revision number; e.g., for Solaris 2.x, " +"which is also known as SunOS 5.x, the value is ``'sunos5'``. On Mac OS X, " +"it is ``'darwin'``. On Windows, it is ``'win'``. The returned string " +"points into static storage; the caller should not modify its value. The " +"value is available to Python code as ``sys.platform``." +msgstr "" + +#: ../Doc/c-api/init.rst:301 +msgid "" +"Return the official copyright string for the current Python version, for " +"example" +msgstr "" + +#: ../Doc/c-api/init.rst:303 +msgid "``'Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam'``" +msgstr "" + +#: ../Doc/c-api/init.rst:307 +msgid "" +"The returned string points into static storage; the caller should not modify " +"its value. The value is available to Python code as ``sys.copyright``." +msgstr "" + +#: ../Doc/c-api/init.rst:313 +msgid "" +"Return an indication of the compiler used to build the current Python " +"version, in square brackets, for example::" +msgstr "" + +#: ../Doc/c-api/init.rst:320 ../Doc/c-api/init.rst:334 +msgid "" +"The returned string points into static storage; the caller should not modify " +"its value. The value is available to Python code as part of the variable " +"``sys.version``." +msgstr "" + +#: ../Doc/c-api/init.rst:327 +msgid "" +"Return information about the sequence number and build date and time of the " +"current Python interpreter instance, for example ::" +msgstr "" + +#: ../Doc/c-api/init.rst:346 +msgid "" +"Set :data:`sys.argv` based on *argc* and *argv*. These parameters are " +"similar to those passed to the program's :c:func:`main` function with the " +"difference that the first entry should refer to the script file to be " +"executed rather than the executable hosting the Python interpreter. If " +"there isn't a script that will be run, the first entry in *argv* can be an " +"empty string. If this function fails to initialize :data:`sys.argv`, a " +"fatal condition is signalled using :c:func:`Py_FatalError`." +msgstr "" + +#: ../Doc/c-api/init.rst:354 +msgid "" +"If *updatepath* is zero, this is all the function does. If *updatepath* is " +"non-zero, the function also modifies :data:`sys.path` according to the " +"following algorithm:" +msgstr "" + +#: ../Doc/c-api/init.rst:358 +msgid "" +"If the name of an existing script is passed in ``argv[0]``, the absolute " +"path of the directory where the script is located is prepended to :data:`sys." +"path`." +msgstr "" + +#: ../Doc/c-api/init.rst:361 +msgid "" +"Otherwise (that is, if *argc* is 0 or ``argv[0]`` doesn't point to an " +"existing file name), an empty string is prepended to :data:`sys.path`, which " +"is the same as prepending the current working directory (``\".\"``)." +msgstr "" + +#: ../Doc/c-api/init.rst:370 +msgid "" +"It is recommended that applications embedding the Python interpreter for " +"purposes other than executing a single script pass 0 as *updatepath*, and " +"update :data:`sys.path` themselves if desired. See `CVE-2008-5983 `_." +msgstr "" + +#: ../Doc/c-api/init.rst:375 +msgid "" +"On versions before 3.1.3, you can achieve the same effect by manually " +"popping the first :data:`sys.path` element after having called :c:func:" +"`PySys_SetArgv`, for example using::" +msgstr "" + +#: ../Doc/c-api/init.rst:389 +msgid "" +"This function works like :c:func:`PySys_SetArgvEx` with *updatepath* set to " +"1 unless the :program:`python` interpreter was started with the :option:`-I`." +msgstr "" + +#: ../Doc/c-api/init.rst:396 +msgid "The *updatepath* value depends on :option:`-I`." +msgstr "" + +#: ../Doc/c-api/init.rst:401 +msgid "" +"Set the default \"home\" directory, that is, the location of the standard " +"Python libraries. See :envvar:`PYTHONHOME` for the meaning of the argument " +"string." +msgstr "" + +#: ../Doc/c-api/init.rst:405 +msgid "" +"The argument should point to a zero-terminated character string in static " +"storage whose contents will not change for the duration of the program's " +"execution. No code in the Python interpreter will change the contents of " +"this storage." +msgstr "" + +#: ../Doc/c-api/init.rst:416 +msgid "" +"Return the default \"home\", that is, the value set by a previous call to :c:" +"func:`Py_SetPythonHome`, or the value of the :envvar:`PYTHONHOME` " +"environment variable if it is set." +msgstr "" + +#: ../Doc/c-api/init.rst:424 +msgid "Thread State and the Global Interpreter Lock" +msgstr "" + +#: ../Doc/c-api/init.rst:431 +msgid "" +"The Python interpreter is not fully thread-safe. In order to support multi-" +"threaded Python programs, there's a global lock, called the :term:`global " +"interpreter lock` or :term:`GIL`, that must be held by the current thread " +"before it can safely access Python objects. Without the lock, even the " +"simplest operations could cause problems in a multi-threaded program: for " +"example, when two threads simultaneously increment the reference count of " +"the same object, the reference count could end up being incremented only " +"once instead of twice." +msgstr "" + +#: ../Doc/c-api/init.rst:441 +msgid "" +"Therefore, the rule exists that only the thread that has acquired the :term:" +"`GIL` may operate on Python objects or call Python/C API functions. In order " +"to emulate concurrency of execution, the interpreter regularly tries to " +"switch threads (see :func:`sys.setswitchinterval`). The lock is also " +"released around potentially blocking I/O operations like reading or writing " +"a file, so that other Python threads can run in the meantime." +msgstr "" + +#: ../Doc/c-api/init.rst:452 +msgid "" +"The Python interpreter keeps some thread-specific bookkeeping information " +"inside a data structure called :c:type:`PyThreadState`. There's also one " +"global variable pointing to the current :c:type:`PyThreadState`: it can be " +"retrieved using :c:func:`PyThreadState_Get`." +msgstr "" + +#: ../Doc/c-api/init.rst:458 +msgid "Releasing the GIL from extension code" +msgstr "" + +#: ../Doc/c-api/init.rst:460 +msgid "" +"Most extension code manipulating the :term:`GIL` has the following simple " +"structure::" +msgstr "" + +#: ../Doc/c-api/init.rst:469 +msgid "This is so common that a pair of macros exists to simplify it::" +msgstr "" + +#: ../Doc/c-api/init.rst:479 +msgid "" +"The :c:macro:`Py_BEGIN_ALLOW_THREADS` macro opens a new block and declares a " +"hidden local variable; the :c:macro:`Py_END_ALLOW_THREADS` macro closes the " +"block. These two macros are still available when Python is compiled without " +"thread support (they simply have an empty expansion)." +msgstr "" + +#: ../Doc/c-api/init.rst:484 +msgid "" +"When thread support is enabled, the block above expands to the following " +"code::" +msgstr "" + +#: ../Doc/c-api/init.rst:496 +msgid "" +"Here is how these functions work: the global interpreter lock is used to " +"protect the pointer to the current thread state. When releasing the lock " +"and saving the thread state, the current thread state pointer must be " +"retrieved before the lock is released (since another thread could " +"immediately acquire the lock and store its own thread state in the global " +"variable). Conversely, when acquiring the lock and restoring the thread " +"state, the lock must be acquired before storing the thread state pointer." +msgstr "" + +#: ../Doc/c-api/init.rst:505 +msgid "" +"Calling system I/O functions is the most common use case for releasing the " +"GIL, but it can also be useful before calling long-running computations " +"which don't need access to Python objects, such as compression or " +"cryptographic functions operating over memory buffers. For example, the " +"standard :mod:`zlib` and :mod:`hashlib` modules release the GIL when " +"compressing or hashing data." +msgstr "" + +#: ../Doc/c-api/init.rst:516 +msgid "Non-Python created threads" +msgstr "" + +#: ../Doc/c-api/init.rst:518 +msgid "" +"When threads are created using the dedicated Python APIs (such as the :mod:" +"`threading` module), a thread state is automatically associated to them and " +"the code showed above is therefore correct. However, when threads are " +"created from C (for example by a third-party library with its own thread " +"management), they don't hold the GIL, nor is there a thread state structure " +"for them." +msgstr "" + +#: ../Doc/c-api/init.rst:525 +msgid "" +"If you need to call Python code from these threads (often this will be part " +"of a callback API provided by the aforementioned third-party library), you " +"must first register these threads with the interpreter by creating a thread " +"state data structure, then acquiring the GIL, and finally storing their " +"thread state pointer, before you can start using the Python/C API. When you " +"are done, you should reset the thread state pointer, release the GIL, and " +"finally free the thread state data structure." +msgstr "" + +#: ../Doc/c-api/init.rst:533 +msgid "" +"The :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release` functions " +"do all of the above automatically. The typical idiom for calling into " +"Python from a C thread is::" +msgstr "" + +#: ../Doc/c-api/init.rst:547 +msgid "" +"Note that the :c:func:`PyGILState_\\*` functions assume there is only one " +"global interpreter (created automatically by :c:func:`Py_Initialize`). " +"Python supports the creation of additional interpreters (using :c:func:" +"`Py_NewInterpreter`), but mixing multiple interpreters and the :c:func:" +"`PyGILState_\\*` API is unsupported." +msgstr "" + +#: ../Doc/c-api/init.rst:553 +msgid "" +"Another important thing to note about threads is their behaviour in the face " +"of the C :c:func:`fork` call. On most systems with :c:func:`fork`, after a " +"process forks only the thread that issued the fork will exist. That also " +"means any locks held by other threads will never be released. Python solves " +"this for :func:`os.fork` by acquiring the locks it uses internally before " +"the fork, and releasing them afterwards. In addition, it resets any :ref:" +"`lock-objects` in the child. When extending or embedding Python, there is no " +"way to inform Python of additional (non-Python) locks that need to be " +"acquired before or reset after a fork. OS facilities such as :c:func:" +"`pthread_atfork` would need to be used to accomplish the same thing. " +"Additionally, when extending or embedding Python, calling :c:func:`fork` " +"directly rather than through :func:`os.fork` (and returning to or calling " +"into Python) may result in a deadlock by one of Python's internal locks " +"being held by a thread that is defunct after the fork. :c:func:" +"`PyOS_AfterFork` tries to reset the necessary locks, but is not always able " +"to." +msgstr "" + +#: ../Doc/c-api/init.rst:572 +msgid "High-level API" +msgstr "" + +#: ../Doc/c-api/init.rst:574 +msgid "" +"These are the most commonly used types and functions when writing C " +"extension code, or when embedding the Python interpreter:" +msgstr "" + +#: ../Doc/c-api/init.rst:579 +msgid "" +"This data structure represents the state shared by a number of cooperating " +"threads. Threads belonging to the same interpreter share their module " +"administration and a few other internal items. There are no public members " +"in this structure." +msgstr "" + +#: ../Doc/c-api/init.rst:584 +msgid "" +"Threads belonging to different interpreters initially share nothing, except " +"process state like available memory, open file descriptors and such. The " +"global interpreter lock is also shared by all threads, regardless of to " +"which interpreter they belong." +msgstr "" + +#: ../Doc/c-api/init.rst:592 +msgid "" +"This data structure represents the state of a single thread. The only " +"public data member is :c:type:`PyInterpreterState \\*`:attr:`interp`, which " +"points to this thread's interpreter state." +msgstr "" + +#: ../Doc/c-api/init.rst:605 +msgid "" +"Initialize and acquire the global interpreter lock. It should be called in " +"the main thread before creating a second thread or engaging in any other " +"thread operations such as ``PyEval_ReleaseThread(tstate)``. It is not needed " +"before calling :c:func:`PyEval_SaveThread` or :c:func:`PyEval_RestoreThread`." +msgstr "" + +#: ../Doc/c-api/init.rst:610 +msgid "This is a no-op when called for a second time." +msgstr "" + +#: ../Doc/c-api/init.rst:612 +msgid "" +"This function cannot be called before :c:func:`Py_Initialize()` anymore." +msgstr "" + +#: ../Doc/c-api/init.rst:619 +msgid "" +"When only the main thread exists, no GIL operations are needed. This is a " +"common situation (most Python programs do not use threads), and the lock " +"operations slow the interpreter down a bit. Therefore, the lock is not " +"created initially. This situation is equivalent to having acquired the " +"lock: when there is only a single thread, all object accesses are safe. " +"Therefore, when this function initializes the global interpreter lock, it " +"also acquires it. Before the Python :mod:`_thread` module creates a new " +"thread, knowing that either it has the lock or the lock hasn't been created " +"yet, it calls :c:func:`PyEval_InitThreads`. When this call returns, it is " +"guaranteed that the lock has been created and that the calling thread has " +"acquired it." +msgstr "" + +#: ../Doc/c-api/init.rst:630 +msgid "" +"It is **not** safe to call this function when it is unknown which thread (if " +"any) currently has the global interpreter lock." +msgstr "" + +#: ../Doc/c-api/init.rst:633 +msgid "" +"This function is not available when thread support is disabled at compile " +"time." +msgstr "" + +#: ../Doc/c-api/init.rst:638 +msgid "" +"Returns a non-zero value if :c:func:`PyEval_InitThreads` has been called. " +"This function can be called without holding the GIL, and therefore can be " +"used to avoid calls to the locking API when running single-threaded. This " +"function is not available when thread support is disabled at compile time." +msgstr "" + +#: ../Doc/c-api/init.rst:646 +msgid "" +"Release the global interpreter lock (if it has been created and thread " +"support is enabled) and reset the thread state to *NULL*, returning the " +"previous thread state (which is not *NULL*). If the lock has been created, " +"the current thread must have acquired it. (This function is available even " +"when thread support is disabled at compile time.)" +msgstr "" + +#: ../Doc/c-api/init.rst:655 +msgid "" +"Acquire the global interpreter lock (if it has been created and thread " +"support is enabled) and set the thread state to *tstate*, which must not be " +"*NULL*. If the lock has been created, the current thread must not have " +"acquired it, otherwise deadlock ensues. (This function is available even " +"when thread support is disabled at compile time.)" +msgstr "" + +#: ../Doc/c-api/init.rst:664 +msgid "" +"Return the current thread state. The global interpreter lock must be held. " +"When the current thread state is *NULL*, this issues a fatal error (so that " +"the caller needn't check for *NULL*)." +msgstr "" + +#: ../Doc/c-api/init.rst:671 +msgid "" +"Swap the current thread state with the thread state given by the argument " +"*tstate*, which may be *NULL*. The global interpreter lock must be held and " +"is not released." +msgstr "" + +#: ../Doc/c-api/init.rst:678 +msgid "" +"This function is called from :c:func:`PyOS_AfterFork` to ensure that newly " +"created child processes don't hold locks referring to threads which are not " +"running in the child process." +msgstr "" + +#: ../Doc/c-api/init.rst:683 +msgid "" +"The following functions use thread-local storage, and are not compatible " +"with sub-interpreters:" +msgstr "" + +#: ../Doc/c-api/init.rst:688 +msgid "" +"Ensure that the current thread is ready to call the Python C API regardless " +"of the current state of Python, or of the global interpreter lock. This may " +"be called as many times as desired by a thread as long as each call is " +"matched with a call to :c:func:`PyGILState_Release`. In general, other " +"thread-related APIs may be used between :c:func:`PyGILState_Ensure` and :c:" +"func:`PyGILState_Release` calls as long as the thread state is restored to " +"its previous state before the Release(). For example, normal usage of the :" +"c:macro:`Py_BEGIN_ALLOW_THREADS` and :c:macro:`Py_END_ALLOW_THREADS` macros " +"is acceptable." +msgstr "" + +#: ../Doc/c-api/init.rst:698 +msgid "" +"The return value is an opaque \"handle\" to the thread state when :c:func:" +"`PyGILState_Ensure` was called, and must be passed to :c:func:" +"`PyGILState_Release` to ensure Python is left in the same state. Even though " +"recursive calls are allowed, these handles *cannot* be shared - each unique " +"call to :c:func:`PyGILState_Ensure` must save the handle for its call to :c:" +"func:`PyGILState_Release`." +msgstr "" + +#: ../Doc/c-api/init.rst:705 +msgid "" +"When the function returns, the current thread will hold the GIL and be able " +"to call arbitrary Python code. Failure is a fatal error." +msgstr "" + +#: ../Doc/c-api/init.rst:711 +msgid "" +"Release any resources previously acquired. After this call, Python's state " +"will be the same as it was prior to the corresponding :c:func:" +"`PyGILState_Ensure` call (but generally this state will be unknown to the " +"caller, hence the use of the GILState API)." +msgstr "" + +#: ../Doc/c-api/init.rst:716 +msgid "" +"Every call to :c:func:`PyGILState_Ensure` must be matched by a call to :c:" +"func:`PyGILState_Release` on the same thread." +msgstr "" + +#: ../Doc/c-api/init.rst:722 +msgid "" +"Get the current thread state for this thread. May return ``NULL`` if no " +"GILState API has been used on the current thread. Note that the main thread " +"always has such a thread-state, even if no auto-thread-state call has been " +"made on the main thread. This is mainly a helper/diagnostic function." +msgstr "" + +#: ../Doc/c-api/init.rst:730 +msgid "" +"Return 1 if the current thread is holding the GIL and 0 otherwise. This " +"function can be called from any thread at any time. Only if it has had its " +"Python thread state initialized and currently is holding the GIL will it " +"return 1. This is mainly a helper/diagnostic function. It can be useful for " +"example in callback contexts or memory allocation functions when knowing " +"that the GIL is locked can allow the caller to perform sensitive actions or " +"otherwise behave differently." +msgstr "" + +#: ../Doc/c-api/init.rst:742 +msgid "" +"The following macros are normally used without a trailing semicolon; look " +"for example usage in the Python source distribution." +msgstr "" + +#: ../Doc/c-api/init.rst:748 +msgid "" +"This macro expands to ``{ PyThreadState *_save; _save = PyEval_SaveThread();" +"``. Note that it contains an opening brace; it must be matched with a " +"following :c:macro:`Py_END_ALLOW_THREADS` macro. See above for further " +"discussion of this macro. It is a no-op when thread support is disabled at " +"compile time." +msgstr "" + +#: ../Doc/c-api/init.rst:756 +msgid "" +"This macro expands to ``PyEval_RestoreThread(_save); }``. Note that it " +"contains a closing brace; it must be matched with an earlier :c:macro:" +"`Py_BEGIN_ALLOW_THREADS` macro. See above for further discussion of this " +"macro. It is a no-op when thread support is disabled at compile time." +msgstr "" + +#: ../Doc/c-api/init.rst:764 +msgid "" +"This macro expands to ``PyEval_RestoreThread(_save);``: it is equivalent to :" +"c:macro:`Py_END_ALLOW_THREADS` without the closing brace. It is a no-op " +"when thread support is disabled at compile time." +msgstr "" + +#: ../Doc/c-api/init.rst:771 +msgid "" +"This macro expands to ``_save = PyEval_SaveThread();``: it is equivalent to :" +"c:macro:`Py_BEGIN_ALLOW_THREADS` without the opening brace and variable " +"declaration. It is a no-op when thread support is disabled at compile time." +msgstr "" + +#: ../Doc/c-api/init.rst:777 +msgid "Low-level API" +msgstr "" + +#: ../Doc/c-api/init.rst:779 +msgid "" +"All of the following functions are only available when thread support is " +"enabled at compile time, and must be called only when the global interpreter " +"lock has been created." +msgstr "" + +#: ../Doc/c-api/init.rst:786 +msgid "" +"Create a new interpreter state object. The global interpreter lock need not " +"be held, but may be held if it is necessary to serialize calls to this " +"function." +msgstr "" + +#: ../Doc/c-api/init.rst:793 +msgid "" +"Reset all information in an interpreter state object. The global " +"interpreter lock must be held." +msgstr "" + +#: ../Doc/c-api/init.rst:799 +msgid "" +"Destroy an interpreter state object. The global interpreter lock need not " +"be held. The interpreter state must have been reset with a previous call " +"to :c:func:`PyInterpreterState_Clear`." +msgstr "" + +#: ../Doc/c-api/init.rst:806 +msgid "" +"Create a new thread state object belonging to the given interpreter object. " +"The global interpreter lock need not be held, but may be held if it is " +"necessary to serialize calls to this function." +msgstr "" + +#: ../Doc/c-api/init.rst:813 +msgid "" +"Reset all information in a thread state object. The global interpreter lock " +"must be held." +msgstr "" + +#: ../Doc/c-api/init.rst:819 +msgid "" +"Destroy a thread state object. The global interpreter lock need not be " +"held. The thread state must have been reset with a previous call to :c:func:" +"`PyThreadState_Clear`." +msgstr "" + +#: ../Doc/c-api/init.rst:826 +msgid "" +"Return a dictionary in which extensions can store thread-specific state " +"information. Each extension should use a unique key to use to store state " +"in the dictionary. It is okay to call this function when no current thread " +"state is available. If this function returns *NULL*, no exception has been " +"raised and the caller should assume no current thread state is available." +msgstr "" + +#: ../Doc/c-api/init.rst:835 +msgid "" +"Asynchronously raise an exception in a thread. The *id* argument is the " +"thread id of the target thread; *exc* is the exception object to be raised. " +"This function does not steal any references to *exc*. To prevent naive " +"misuse, you must write your own C extension to call this. Must be called " +"with the GIL held. Returns the number of thread states modified; this is " +"normally one, but will be zero if the thread id isn't found. If *exc* is :" +"const:`NULL`, the pending exception (if any) for the thread is cleared. This " +"raises no exceptions." +msgstr "" + +#: ../Doc/c-api/init.rst:846 +msgid "" +"Acquire the global interpreter lock and set the current thread state to " +"*tstate*, which should not be *NULL*. The lock must have been created " +"earlier. If this thread already has the lock, deadlock ensues." +msgstr "" + +#: ../Doc/c-api/init.rst:850 +msgid "" +":c:func:`PyEval_RestoreThread` is a higher-level function which is always " +"available (even when thread support isn't enabled or when threads have not " +"been initialized)." +msgstr "" + +#: ../Doc/c-api/init.rst:857 +msgid "" +"Reset the current thread state to *NULL* and release the global interpreter " +"lock. The lock must have been created earlier and must be held by the " +"current thread. The *tstate* argument, which must not be *NULL*, is only " +"used to check that it represents the current thread state --- if it isn't, a " +"fatal error is reported." +msgstr "" + +#: ../Doc/c-api/init.rst:863 +msgid "" +":c:func:`PyEval_SaveThread` is a higher-level function which is always " +"available (even when thread support isn't enabled or when threads have not " +"been initialized)." +msgstr "" + +#: ../Doc/c-api/init.rst:870 +msgid "" +"Acquire the global interpreter lock. The lock must have been created " +"earlier. If this thread already has the lock, a deadlock ensues." +msgstr "" + +#: ../Doc/c-api/init.rst:873 +msgid "" +"This function does not update the current thread state. Please use :c:func:" +"`PyEval_RestoreThread` or :c:func:`PyEval_AcquireThread` instead." +msgstr "" + +#: ../Doc/c-api/init.rst:881 +msgid "" +"Release the global interpreter lock. The lock must have been created " +"earlier." +msgstr "" + +#: ../Doc/c-api/init.rst:883 +msgid "" +"This function does not update the current thread state. Please use :c:func:" +"`PyEval_SaveThread` or :c:func:`PyEval_ReleaseThread` instead." +msgstr "" + +#: ../Doc/c-api/init.rst:892 +msgid "Sub-interpreter support" +msgstr "" + +#: ../Doc/c-api/init.rst:894 +msgid "" +"While in most uses, you will only embed a single Python interpreter, there " +"are cases where you need to create several independent interpreters in the " +"same process and perhaps even in the same thread. Sub-interpreters allow " +"you to do that. You can switch between sub-interpreters using the :c:func:" +"`PyThreadState_Swap` function. You can create and destroy them using the " +"following functions:" +msgstr "" + +#: ../Doc/c-api/init.rst:912 +msgid "" +"Create a new sub-interpreter. This is an (almost) totally separate " +"environment for the execution of Python code. In particular, the new " +"interpreter has separate, independent versions of all imported modules, " +"including the fundamental modules :mod:`builtins`, :mod:`__main__` and :mod:" +"`sys`. The table of loaded modules (``sys.modules``) and the module search " +"path (``sys.path``) are also separate. The new environment has no ``sys." +"argv`` variable. It has new standard I/O stream file objects ``sys.stdin``, " +"``sys.stdout`` and ``sys.stderr`` (however these refer to the same " +"underlying file descriptors)." +msgstr "" + +#: ../Doc/c-api/init.rst:922 +msgid "" +"The return value points to the first thread state created in the new sub-" +"interpreter. This thread state is made in the current thread state. Note " +"that no actual thread is created; see the discussion of thread states " +"below. If creation of the new interpreter is unsuccessful, *NULL* is " +"returned; no exception is set since the exception state is stored in the " +"current thread state and there may not be a current thread state. (Like all " +"other Python/C API functions, the global interpreter lock must be held " +"before calling this function and is still held when it returns; however, " +"unlike most other Python/C API functions, there needn't be a current thread " +"state on entry.)" +msgstr "" + +#: ../Doc/c-api/init.rst:937 +msgid "" +"Extension modules are shared between (sub-)interpreters as follows: the " +"first time a particular extension is imported, it is initialized normally, " +"and a (shallow) copy of its module's dictionary is squirreled away. When " +"the same extension is imported by another (sub-)interpreter, a new module is " +"initialized and filled with the contents of this copy; the extension's " +"``init`` function is not called. Note that this is different from what " +"happens when an extension is imported after the interpreter has been " +"completely re-initialized by calling :c:func:`Py_FinalizeEx` and :c:func:" +"`Py_Initialize`; in that case, the extension's ``initmodule`` function *is* " +"called again." +msgstr "" + +#: ../Doc/c-api/init.rst:954 +msgid "" +"Destroy the (sub-)interpreter represented by the given thread state. The " +"given thread state must be the current thread state. See the discussion of " +"thread states below. When the call returns, the current thread state is " +"*NULL*. All thread states associated with this interpreter are destroyed. " +"(The global interpreter lock must be held before calling this function and " +"is still held when it returns.) :c:func:`Py_FinalizeEx` will destroy all " +"sub-interpreters that haven't been explicitly destroyed at that point." +msgstr "" + +#: ../Doc/c-api/init.rst:964 +msgid "Bugs and caveats" +msgstr "" + +#: ../Doc/c-api/init.rst:966 +msgid "" +"Because sub-interpreters (and the main interpreter) are part of the same " +"process, the insulation between them isn't perfect --- for example, using " +"low-level file operations like :func:`os.close` they can (accidentally or " +"maliciously) affect each other's open files. Because of the way extensions " +"are shared between (sub-)interpreters, some extensions may not work " +"properly; this is especially likely when the extension makes use of (static) " +"global variables, or when the extension manipulates its module's dictionary " +"after its initialization. It is possible to insert objects created in one " +"sub-interpreter into a namespace of another sub-interpreter; this should be " +"done with great care to avoid sharing user-defined functions, methods, " +"instances or classes between sub-interpreters, since import operations " +"executed by such objects may affect the wrong (sub-)interpreter's dictionary " +"of loaded modules." +msgstr "" + +#: ../Doc/c-api/init.rst:980 +msgid "" +"Also note that combining this functionality with :c:func:`PyGILState_\\*` " +"APIs is delicate, because these APIs assume a bijection between Python " +"thread states and OS-level threads, an assumption broken by the presence of " +"sub-interpreters. It is highly recommended that you don't switch sub-" +"interpreters between a pair of matching :c:func:`PyGILState_Ensure` and :c:" +"func:`PyGILState_Release` calls. Furthermore, extensions (such as :mod:" +"`ctypes`) using these APIs to allow calling of Python code from non-Python " +"created threads will probably be broken when using sub-interpreters." +msgstr "" + +#: ../Doc/c-api/init.rst:991 +msgid "Asynchronous Notifications" +msgstr "" + +#: ../Doc/c-api/init.rst:993 +msgid "" +"A mechanism is provided to make asynchronous notifications to the main " +"interpreter thread. These notifications take the form of a function pointer " +"and a void pointer argument." +msgstr "" + +#: ../Doc/c-api/init.rst:1002 +msgid "" +"Schedule a function to be called from the main interpreter thread. On " +"success, 0 is returned and *func* is queued for being called in the main " +"thread. On failure, -1 is returned without setting any exception." +msgstr "" + +#: ../Doc/c-api/init.rst:1006 +msgid "" +"When successfully queued, *func* will be *eventually* called from the main " +"interpreter thread with the argument *arg*. It will be called " +"asynchronously with respect to normally running Python code, but with both " +"these conditions met:" +msgstr "" + +#: ../Doc/c-api/init.rst:1011 +msgid "on a :term:`bytecode` boundary;" +msgstr "" + +#: ../Doc/c-api/init.rst:1012 +msgid "" +"with the main thread holding the :term:`global interpreter lock` (*func* can " +"therefore use the full C API)." +msgstr "" + +#: ../Doc/c-api/init.rst:1015 +msgid "" +"*func* must return 0 on success, or -1 on failure with an exception set. " +"*func* won't be interrupted to perform another asynchronous notification " +"recursively, but it can still be interrupted to switch threads if the global " +"interpreter lock is released." +msgstr "" + +#: ../Doc/c-api/init.rst:1020 +msgid "" +"This function doesn't need a current thread state to run, and it doesn't " +"need the global interpreter lock." +msgstr "" + +#: ../Doc/c-api/init.rst:1024 +msgid "" +"This is a low-level function, only useful for very special cases. There is " +"no guarantee that *func* will be called as quick as possible. If the main " +"thread is busy executing a system call, *func* won't be called before the " +"system call returns. This function is generally **not** suitable for " +"calling Python code from arbitrary C threads. Instead, use the :ref:" +"`PyGILState API`." +msgstr "" + +#: ../Doc/c-api/init.rst:1036 +msgid "Profiling and Tracing" +msgstr "" + +#: ../Doc/c-api/init.rst:1041 +msgid "" +"The Python interpreter provides some low-level support for attaching " +"profiling and execution tracing facilities. These are used for profiling, " +"debugging, and coverage analysis tools." +msgstr "" + +#: ../Doc/c-api/init.rst:1045 +msgid "" +"This C interface allows the profiling or tracing code to avoid the overhead " +"of calling through Python-level callable objects, making a direct C function " +"call instead. The essential attributes of the facility have not changed; " +"the interface allows trace functions to be installed per-thread, and the " +"basic events reported to the trace function are the same as had been " +"reported to the Python-level trace functions in previous versions." +msgstr "" + +#: ../Doc/c-api/init.rst:1055 +msgid "" +"The type of the trace function registered using :c:func:`PyEval_SetProfile` " +"and :c:func:`PyEval_SetTrace`. The first parameter is the object passed to " +"the registration function as *obj*, *frame* is the frame object to which the " +"event pertains, *what* is one of the constants :const:`PyTrace_CALL`, :const:" +"`PyTrace_EXCEPTION`, :const:`PyTrace_LINE`, :const:`PyTrace_RETURN`, :const:" +"`PyTrace_C_CALL`, :const:`PyTrace_C_EXCEPTION`, or :const:" +"`PyTrace_C_RETURN`, and *arg* depends on the value of *what*:" +msgstr "" + +#: ../Doc/c-api/init.rst:1064 +msgid "Value of *what*" +msgstr "" + +#: ../Doc/c-api/init.rst:1064 +msgid "Meaning of *arg*" +msgstr "" + +#: ../Doc/c-api/init.rst:1066 +msgid ":const:`PyTrace_CALL`" +msgstr "" + +#: ../Doc/c-api/init.rst:1066 ../Doc/c-api/init.rst:1071 +msgid "Always *NULL*." +msgstr "" + +#: ../Doc/c-api/init.rst:1068 +msgid ":const:`PyTrace_EXCEPTION`" +msgstr "" + +#: ../Doc/c-api/init.rst:1068 +msgid "Exception information as returned by :func:`sys.exc_info`." +msgstr "" + +#: ../Doc/c-api/init.rst:1071 +msgid ":const:`PyTrace_LINE`" +msgstr "" + +#: ../Doc/c-api/init.rst:1073 +msgid ":const:`PyTrace_RETURN`" +msgstr "" + +#: ../Doc/c-api/init.rst:1073 +msgid "" +"Value being returned to the caller, or *NULL* if caused by an exception." +msgstr "" + +#: ../Doc/c-api/init.rst:1076 +msgid ":const:`PyTrace_C_CALL`" +msgstr "" + +#: ../Doc/c-api/init.rst:1076 ../Doc/c-api/init.rst:1078 +#: ../Doc/c-api/init.rst:1080 +msgid "Function object being called." +msgstr "" + +#: ../Doc/c-api/init.rst:1078 +msgid ":const:`PyTrace_C_EXCEPTION`" +msgstr "" + +#: ../Doc/c-api/init.rst:1080 +msgid ":const:`PyTrace_C_RETURN`" +msgstr "" + +#: ../Doc/c-api/init.rst:1086 +msgid "" +"The value of the *what* parameter to a :c:type:`Py_tracefunc` function when " +"a new call to a function or method is being reported, or a new entry into a " +"generator. Note that the creation of the iterator for a generator function " +"is not reported as there is no control transfer to the Python bytecode in " +"the corresponding frame." +msgstr "" + +#: ../Doc/c-api/init.rst:1095 +msgid "" +"The value of the *what* parameter to a :c:type:`Py_tracefunc` function when " +"an exception has been raised. The callback function is called with this " +"value for *what* when after any bytecode is processed after which the " +"exception becomes set within the frame being executed. The effect of this " +"is that as exception propagation causes the Python stack to unwind, the " +"callback is called upon return to each frame as the exception propagates. " +"Only trace functions receives these events; they are not needed by the " +"profiler." +msgstr "" + +#: ../Doc/c-api/init.rst:1106 +msgid "" +"The value passed as the *what* parameter to a trace function (but not a " +"profiling function) when a line-number event is being reported." +msgstr "" + +#: ../Doc/c-api/init.rst:1112 +msgid "" +"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when " +"a call is returning without propagating an exception." +msgstr "" + +#: ../Doc/c-api/init.rst:1118 +msgid "" +"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when " +"a C function is about to be called." +msgstr "" + +#: ../Doc/c-api/init.rst:1124 +msgid "" +"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when " +"a C function has raised an exception." +msgstr "" + +#: ../Doc/c-api/init.rst:1130 +msgid "" +"The value for the *what* parameter to :c:type:`Py_tracefunc` functions when " +"a C function has returned." +msgstr "" + +#: ../Doc/c-api/init.rst:1136 +msgid "" +"Set the profiler function to *func*. The *obj* parameter is passed to the " +"function as its first parameter, and may be any Python object, or *NULL*. " +"If the profile function needs to maintain state, using a different value for " +"*obj* for each thread provides a convenient and thread-safe place to store " +"it. The profile function is called for all monitored events except the line-" +"number events." +msgstr "" + +#: ../Doc/c-api/init.rst:1146 +msgid "" +"Set the tracing function to *func*. This is similar to :c:func:" +"`PyEval_SetProfile`, except the tracing function does receive line-number " +"events." +msgstr "" + +#: ../Doc/c-api/init.rst:1152 +msgid "" +"Return a tuple of function call counts. There are constants defined for the " +"positions within the tuple:" +msgstr "" + +#: ../Doc/c-api/init.rst:1156 +msgid "Name" +msgstr "" + +#: ../Doc/c-api/init.rst:1156 +msgid "Value" +msgstr "" + +#: ../Doc/c-api/init.rst:1158 +msgid ":const:`PCALL_ALL`" +msgstr "" + +#: ../Doc/c-api/init.rst:1160 +msgid ":const:`PCALL_FUNCTION`" +msgstr "" + +#: ../Doc/c-api/init.rst:1160 +msgid "1" +msgstr "" + +#: ../Doc/c-api/init.rst:1162 +msgid ":const:`PCALL_FAST_FUNCTION`" +msgstr "" + +#: ../Doc/c-api/init.rst:1162 +msgid "2" +msgstr "" + +#: ../Doc/c-api/init.rst:1164 +msgid ":const:`PCALL_FASTER_FUNCTION`" +msgstr "" + +#: ../Doc/c-api/init.rst:1164 +msgid "3" +msgstr "" + +#: ../Doc/c-api/init.rst:1166 +msgid ":const:`PCALL_METHOD`" +msgstr "" + +#: ../Doc/c-api/init.rst:1166 +msgid "4" +msgstr "" + +#: ../Doc/c-api/init.rst:1168 +msgid ":const:`PCALL_BOUND_METHOD`" +msgstr "" + +#: ../Doc/c-api/init.rst:1168 +msgid "5" +msgstr "" + +#: ../Doc/c-api/init.rst:1170 +msgid ":const:`PCALL_CFUNCTION`" +msgstr "" + +#: ../Doc/c-api/init.rst:1170 +msgid "6" +msgstr "" + +#: ../Doc/c-api/init.rst:1172 +msgid ":const:`PCALL_TYPE`" +msgstr "" + +#: ../Doc/c-api/init.rst:1172 +msgid "7" +msgstr "" + +#: ../Doc/c-api/init.rst:1174 +msgid ":const:`PCALL_GENERATOR`" +msgstr "" + +#: ../Doc/c-api/init.rst:1174 +msgid "8" +msgstr "" + +#: ../Doc/c-api/init.rst:1176 +msgid ":const:`PCALL_OTHER`" +msgstr "" + +#: ../Doc/c-api/init.rst:1176 +msgid "9" +msgstr "" + +#: ../Doc/c-api/init.rst:1178 +msgid ":const:`PCALL_POP`" +msgstr "" + +#: ../Doc/c-api/init.rst:1178 +msgid "10" +msgstr "" + +#: ../Doc/c-api/init.rst:1181 +msgid "" +":const:`PCALL_FAST_FUNCTION` means no argument tuple needs to be created. :" +"const:`PCALL_FASTER_FUNCTION` means that the fast-path frame setup code is " +"used." +msgstr "" + +#: ../Doc/c-api/init.rst:1184 +msgid "" +"If there is a method call where the call can be optimized by changing the " +"argument tuple and calling the function directly, it gets recorded twice." +msgstr "" + +#: ../Doc/c-api/init.rst:1188 +msgid "" +"This function is only present if Python is compiled with :const:" +"`CALL_PROFILE` defined." +msgstr "" + +#: ../Doc/c-api/init.rst:1194 +msgid "Advanced Debugger Support" +msgstr "" + +#: ../Doc/c-api/init.rst:1199 +msgid "" +"These functions are only intended to be used by advanced debugging tools." +msgstr "" + +#: ../Doc/c-api/init.rst:1204 +msgid "" +"Return the interpreter state object at the head of the list of all such " +"objects." +msgstr "" + +#: ../Doc/c-api/init.rst:1209 +msgid "" +"Return the next interpreter state object after *interp* from the list of all " +"such objects." +msgstr "" + +#: ../Doc/c-api/init.rst:1215 +msgid "" +"Return the pointer to the first :c:type:`PyThreadState` object in the list " +"of threads associated with the interpreter *interp*." +msgstr "" + +#: ../Doc/c-api/init.rst:1221 +msgid "" +"Return the next thread state object after *tstate* from the list of all such " +"objects belonging to the same :c:type:`PyInterpreterState` object." +msgstr "" + +#: ../Doc/c-api/intro.rst:8 +msgid "Introduction" +msgstr "" + +#: ../Doc/c-api/intro.rst:10 +msgid "" +"The Application Programmer's Interface to Python gives C and C++ programmers " +"access to the Python interpreter at a variety of levels. The API is equally " +"usable from C++, but for brevity it is generally referred to as the Python/C " +"API. There are two fundamentally different reasons for using the Python/C " +"API. The first reason is to write *extension modules* for specific purposes; " +"these are C modules that extend the Python interpreter. This is probably " +"the most common use. The second reason is to use Python as a component in a " +"larger application; this technique is generally referred to as :dfn:" +"`embedding` Python in an application." +msgstr "" + +#: ../Doc/c-api/intro.rst:20 +msgid "" +"Writing an extension module is a relatively well-understood process, where " +"a \"cookbook\" approach works well. There are several tools that automate " +"the process to some extent. While people have embedded Python in other " +"applications since its early existence, the process of embedding Python is " +"less straightforward than writing an extension." +msgstr "" + +#: ../Doc/c-api/intro.rst:26 +msgid "" +"Many API functions are useful independent of whether you're embedding or " +"extending Python; moreover, most applications that embed Python will need " +"to provide a custom extension as well, so it's probably a good idea to " +"become familiar with writing an extension before attempting to embed Python " +"in a real application." +msgstr "" + +#: ../Doc/c-api/intro.rst:36 +msgid "Include Files" +msgstr "" + +#: ../Doc/c-api/intro.rst:38 +msgid "" +"All function, type and macro definitions needed to use the Python/C API are " +"included in your code by the following line::" +msgstr "" + +#: ../Doc/c-api/intro.rst:43 +msgid "" +"This implies inclusion of the following standard headers: ````, " +"````, ````, ````, ```` and ```` (if available)." +msgstr "" + +#: ../Doc/c-api/intro.rst:49 +msgid "" +"Since Python may define some pre-processor definitions which affect the " +"standard headers on some systems, you *must* include :file:`Python.h` before " +"any standard headers are included." +msgstr "" + +#: ../Doc/c-api/intro.rst:53 +msgid "" +"All user visible names defined by Python.h (except those defined by the " +"included standard headers) have one of the prefixes ``Py`` or ``_Py``. " +"Names beginning with ``_Py`` are for internal use by the Python " +"implementation and should not be used by extension writers. Structure member " +"names do not have a reserved prefix." +msgstr "" + +#: ../Doc/c-api/intro.rst:58 +msgid "" +"**Important:** user code should never define names that begin with ``Py`` or " +"``_Py``. This confuses the reader, and jeopardizes the portability of the " +"user code to future Python versions, which may define additional names " +"beginning with one of these prefixes." +msgstr "" + +#: ../Doc/c-api/intro.rst:63 +msgid "" +"The header files are typically installed with Python. On Unix, these are " +"located in the directories :file:`{prefix}/include/pythonversion/` and :file:" +"`{exec_prefix}/include/pythonversion/`, where :envvar:`prefix` and :envvar:" +"`exec_prefix` are defined by the corresponding parameters to Python's :" +"program:`configure` script and *version* is ``'%d.%d' % sys." +"version_info[:2]``. On Windows, the headers are installed in :file:" +"`{prefix}/include`, where :envvar:`prefix` is the installation directory " +"specified to the installer." +msgstr "" + +#: ../Doc/c-api/intro.rst:72 +msgid "" +"To include the headers, place both directories (if different) on your " +"compiler's search path for includes. Do *not* place the parent directories " +"on the search path and then use ``#include ``; this will " +"break on multi-platform builds since the platform independent headers under :" +"envvar:`prefix` include the platform specific headers from :envvar:" +"`exec_prefix`." +msgstr "" + +#: ../Doc/c-api/intro.rst:79 +msgid "" +"C++ users should note that though the API is defined entirely using C, the " +"header files do properly declare the entry points to be ``extern \"C\"``, so " +"there is no need to do anything special to use the API from C++." +msgstr "" + +#: ../Doc/c-api/intro.rst:87 +msgid "Objects, Types and Reference Counts" +msgstr "" + +#: ../Doc/c-api/intro.rst:91 +msgid "" +"Most Python/C API functions have one or more arguments as well as a return " +"value of type :c:type:`PyObject\\*`. This type is a pointer to an opaque " +"data type representing an arbitrary Python object. Since all Python object " +"types are treated the same way by the Python language in most situations (e." +"g., assignments, scope rules, and argument passing), it is only fitting that " +"they should be represented by a single C type. Almost all Python objects " +"live on the heap: you never declare an automatic or static variable of type :" +"c:type:`PyObject`, only pointer variables of type :c:type:`PyObject\\*` can " +"be declared. The sole exception are the type objects; since these must " +"never be deallocated, they are typically static :c:type:`PyTypeObject` " +"objects." +msgstr "" + +#: ../Doc/c-api/intro.rst:102 +msgid "" +"All Python objects (even Python integers) have a :dfn:`type` and a :dfn:" +"`reference count`. An object's type determines what kind of object it is (e." +"g., an integer, a list, or a user-defined function; there are many more as " +"explained in :ref:`types`). For each of the well-known types there is a " +"macro to check whether an object is of that type; for instance, " +"``PyList_Check(a)`` is true if (and only if) the object pointed to by *a* is " +"a Python list." +msgstr "" + +#: ../Doc/c-api/intro.rst:113 +msgid "Reference Counts" +msgstr "" + +#: ../Doc/c-api/intro.rst:115 +msgid "" +"The reference count is important because today's computers have a finite " +"(and often severely limited) memory size; it counts how many different " +"places there are that have a reference to an object. Such a place could be " +"another object, or a global (or static) C variable, or a local variable in " +"some C function. When an object's reference count becomes zero, the object " +"is deallocated. If it contains references to other objects, their " +"reference count is decremented. Those other objects may be deallocated in " +"turn, if this decrement makes their reference count become zero, and so on. " +"(There's an obvious problem with objects that reference each other here; " +"for now, the solution is \"don't do that.\")" +msgstr "" + +#: ../Doc/c-api/intro.rst:130 +msgid "" +"Reference counts are always manipulated explicitly. The normal way is to " +"use the macro :c:func:`Py_INCREF` to increment an object's reference count " +"by one, and :c:func:`Py_DECREF` to decrement it by one. The :c:func:" +"`Py_DECREF` macro is considerably more complex than the incref one, since it " +"must check whether the reference count becomes zero and then cause the " +"object's deallocator to be called. The deallocator is a function pointer " +"contained in the object's type structure. The type-specific deallocator " +"takes care of decrementing the reference counts for other objects contained " +"in the object if this is a compound object type, such as a list, as well as " +"performing any additional finalization that's needed. There's no chance " +"that the reference count can overflow; at least as many bits are used to " +"hold the reference count as there are distinct memory locations in virtual " +"memory (assuming ``sizeof(Py_ssize_t) >= sizeof(void*)``). Thus, the " +"reference count increment is a simple operation." +msgstr "" + +#: ../Doc/c-api/intro.rst:144 +msgid "" +"It is not necessary to increment an object's reference count for every " +"local variable that contains a pointer to an object. In theory, the " +"object's reference count goes up by one when the variable is made to point " +"to it and it goes down by one when the variable goes out of scope. " +"However, these two cancel each other out, so at the end the reference count " +"hasn't changed. The only real reason to use the reference count is to " +"prevent the object from being deallocated as long as our variable is " +"pointing to it. If we know that there is at least one other reference to " +"the object that lives at least as long as our variable, there is no need to " +"increment the reference count temporarily. An important situation where " +"this arises is in objects that are passed as arguments to C functions in an " +"extension module that are called from Python; the call mechanism guarantees " +"to hold a reference to every argument for the duration of the call." +msgstr "" + +#: ../Doc/c-api/intro.rst:158 +msgid "" +"However, a common pitfall is to extract an object from a list and hold on to " +"it for a while without incrementing its reference count. Some other " +"operation might conceivably remove the object from the list, decrementing " +"its reference count and possible deallocating it. The real danger is that " +"innocent-looking operations may invoke arbitrary Python code which could do " +"this; there is a code path which allows control to flow back to the user " +"from a :c:func:`Py_DECREF`, so almost any operation is potentially dangerous." +msgstr "" + +#: ../Doc/c-api/intro.rst:166 +msgid "" +"A safe approach is to always use the generic operations (functions whose " +"name begins with ``PyObject_``, ``PyNumber_``, ``PySequence_`` or " +"``PyMapping_``). These operations always increment the reference count of " +"the object they return. This leaves the caller with the responsibility to " +"call :c:func:`Py_DECREF` when they are done with the result; this soon " +"becomes second nature." +msgstr "" + +#: ../Doc/c-api/intro.rst:176 +msgid "Reference Count Details" +msgstr "" + +#: ../Doc/c-api/intro.rst:178 +msgid "" +"The reference count behavior of functions in the Python/C API is best " +"explained in terms of *ownership of references*. Ownership pertains to " +"references, never to objects (objects are not owned: they are always " +"shared). \"Owning a reference\" means being responsible for calling " +"Py_DECREF on it when the reference is no longer needed. Ownership can also " +"be transferred, meaning that the code that receives ownership of the " +"reference then becomes responsible for eventually decref'ing it by calling :" +"c:func:`Py_DECREF` or :c:func:`Py_XDECREF` when it's no longer needed---or " +"passing on this responsibility (usually to its caller). When a function " +"passes ownership of a reference on to its caller, the caller is said to " +"receive a *new* reference. When no ownership is transferred, the caller is " +"said to *borrow* the reference. Nothing needs to be done for a borrowed " +"reference." +msgstr "" + +#: ../Doc/c-api/intro.rst:191 +msgid "" +"Conversely, when a calling function passes in a reference to an object, " +"there are two possibilities: the function *steals* a reference to the " +"object, or it does not. *Stealing a reference* means that when you pass a " +"reference to a function, that function assumes that it now owns that " +"reference, and you are not responsible for it any longer." +msgstr "" + +#: ../Doc/c-api/intro.rst:201 +msgid "" +"Few functions steal references; the two notable exceptions are :c:func:" +"`PyList_SetItem` and :c:func:`PyTuple_SetItem`, which steal a reference to " +"the item (but not to the tuple or list into which the item is put!). These " +"functions were designed to steal a reference because of a common idiom for " +"populating a tuple or list with newly created objects; for example, the code " +"to create the tuple ``(1, 2, \"three\")`` could look like this (forgetting " +"about error handling for the moment; a better way to code this is shown " +"below)::" +msgstr "" + +#: ../Doc/c-api/intro.rst:216 +msgid "" +"Here, :c:func:`PyLong_FromLong` returns a new reference which is immediately " +"stolen by :c:func:`PyTuple_SetItem`. When you want to keep using an object " +"although the reference to it will be stolen, use :c:func:`Py_INCREF` to grab " +"another reference before calling the reference-stealing function." +msgstr "" + +#: ../Doc/c-api/intro.rst:221 +msgid "" +"Incidentally, :c:func:`PyTuple_SetItem` is the *only* way to set tuple " +"items; :c:func:`PySequence_SetItem` and :c:func:`PyObject_SetItem` refuse to " +"do this since tuples are an immutable data type. You should only use :c:" +"func:`PyTuple_SetItem` for tuples that you are creating yourself." +msgstr "" + +#: ../Doc/c-api/intro.rst:226 +msgid "" +"Equivalent code for populating a list can be written using :c:func:" +"`PyList_New` and :c:func:`PyList_SetItem`." +msgstr "" + +#: ../Doc/c-api/intro.rst:229 +msgid "" +"However, in practice, you will rarely use these ways of creating and " +"populating a tuple or list. There's a generic function, :c:func:" +"`Py_BuildValue`, that can create most common objects from C values, directed " +"by a :dfn:`format string`. For example, the above two blocks of code could " +"be replaced by the following (which also takes care of the error checking)::" +msgstr "" + +#: ../Doc/c-api/intro.rst:240 +msgid "" +"It is much more common to use :c:func:`PyObject_SetItem` and friends with " +"items whose references you are only borrowing, like arguments that were " +"passed in to the function you are writing. In that case, their behaviour " +"regarding reference counts is much saner, since you don't have to increment " +"a reference count so you can give a reference away (\"have it be stolen\"). " +"For example, this function sets all items of a list (actually, any mutable " +"sequence) to a given item::" +msgstr "" + +#: ../Doc/c-api/intro.rst:270 +msgid "" +"The situation is slightly different for function return values. While " +"passing a reference to most functions does not change your ownership " +"responsibilities for that reference, many functions that return a reference " +"to an object give you ownership of the reference. The reason is simple: in " +"many cases, the returned object is created on the fly, and the reference " +"you get is the only reference to the object. Therefore, the generic " +"functions that return object references, like :c:func:`PyObject_GetItem` " +"and :c:func:`PySequence_GetItem`, always return a new reference (the caller " +"becomes the owner of the reference)." +msgstr "" + +#: ../Doc/c-api/intro.rst:279 +msgid "" +"It is important to realize that whether you own a reference returned by a " +"function depends on which function you call only --- *the plumage* (the type " +"of the object passed as an argument to the function) *doesn't enter into it!" +"* Thus, if you extract an item from a list using :c:func:`PyList_GetItem`, " +"you don't own the reference --- but if you obtain the same item from the " +"same list using :c:func:`PySequence_GetItem` (which happens to take exactly " +"the same arguments), you do own a reference to the returned object." +msgstr "" + +#: ../Doc/c-api/intro.rst:291 +msgid "" +"Here is an example of how you could write a function that computes the sum " +"of the items in a list of integers; once using :c:func:`PyList_GetItem`, " +"and once using :c:func:`PySequence_GetItem`. ::" +msgstr "" + +#: ../Doc/c-api/intro.rst:355 +msgid "Types" +msgstr "" + +#: ../Doc/c-api/intro.rst:357 +msgid "" +"There are few other data types that play a significant role in the Python/C " +"API; most are simple C types such as :c:type:`int`, :c:type:`long`, :c:type:" +"`double` and :c:type:`char\\*`. A few structure types are used to describe " +"static tables used to list the functions exported by a module or the data " +"attributes of a new object type, and another is used to describe the value " +"of a complex number. These will be discussed together with the functions " +"that use them." +msgstr "" + +#: ../Doc/c-api/intro.rst:369 +msgid "Exceptions" +msgstr "" + +#: ../Doc/c-api/intro.rst:371 +msgid "" +"The Python programmer only needs to deal with exceptions if specific error " +"handling is required; unhandled exceptions are automatically propagated to " +"the caller, then to the caller's caller, and so on, until they reach the top-" +"level interpreter, where they are reported to the user accompanied by a " +"stack traceback." +msgstr "" + +#: ../Doc/c-api/intro.rst:379 +msgid "" +"For C programmers, however, error checking always has to be explicit. All " +"functions in the Python/C API can raise exceptions, unless an explicit claim " +"is made otherwise in a function's documentation. In general, when a " +"function encounters an error, it sets an exception, discards any object " +"references that it owns, and returns an error indicator. If not documented " +"otherwise, this indicator is either *NULL* or ``-1``, depending on the " +"function's return type. A few functions return a Boolean true/false result, " +"with false indicating an error. Very few functions return no explicit error " +"indicator or have an ambiguous return value, and require explicit testing " +"for errors with :c:func:`PyErr_Occurred`. These exceptions are always " +"explicitly documented." +msgstr "" + +#: ../Doc/c-api/intro.rst:394 +msgid "" +"Exception state is maintained in per-thread storage (this is equivalent to " +"using global storage in an unthreaded application). A thread can be in one " +"of two states: an exception has occurred, or not. The function :c:func:" +"`PyErr_Occurred` can be used to check for this: it returns a borrowed " +"reference to the exception type object when an exception has occurred, and " +"*NULL* otherwise. There are a number of functions to set the exception " +"state: :c:func:`PyErr_SetString` is the most common (though not the most " +"general) function to set the exception state, and :c:func:`PyErr_Clear` " +"clears the exception state." +msgstr "" + +#: ../Doc/c-api/intro.rst:404 +msgid "" +"The full exception state consists of three objects (all of which can be " +"*NULL*): the exception type, the corresponding exception value, and the " +"traceback. These have the same meanings as the Python result of ``sys." +"exc_info()``; however, they are not the same: the Python objects represent " +"the last exception being handled by a Python :keyword:`try` ... :keyword:" +"`except` statement, while the C level exception state only exists while an " +"exception is being passed on between C functions until it reaches the Python " +"bytecode interpreter's main loop, which takes care of transferring it to " +"``sys.exc_info()`` and friends." +msgstr "" + +#: ../Doc/c-api/intro.rst:416 +msgid "" +"Note that starting with Python 1.5, the preferred, thread-safe way to access " +"the exception state from Python code is to call the function :func:`sys." +"exc_info`, which returns the per-thread exception state for Python code. " +"Also, the semantics of both ways to access the exception state have changed " +"so that a function which catches an exception will save and restore its " +"thread's exception state so as to preserve the exception state of its " +"caller. This prevents common bugs in exception handling code caused by an " +"innocent-looking function overwriting the exception being handled; it also " +"reduces the often unwanted lifetime extension for objects that are " +"referenced by the stack frames in the traceback." +msgstr "" + +#: ../Doc/c-api/intro.rst:427 +msgid "" +"As a general principle, a function that calls another function to perform " +"some task should check whether the called function raised an exception, and " +"if so, pass the exception state on to its caller. It should discard any " +"object references that it owns, and return an error indicator, but it " +"should *not* set another exception --- that would overwrite the exception " +"that was just raised, and lose important information about the exact cause " +"of the error." +msgstr "" + +#: ../Doc/c-api/intro.rst:436 +msgid "" +"A simple example of detecting exceptions and passing them on is shown in " +"the :c:func:`sum_sequence` example above. It so happens that this example " +"doesn't need to clean up any owned references when it detects an error. The " +"following example function shows some error cleanup. First, to remind you " +"why you like Python, we show the equivalent Python code::" +msgstr "" + +#: ../Doc/c-api/intro.rst:451 +msgid "Here is the corresponding C code, in all its glory::" +msgstr "" + +#: ../Doc/c-api/intro.rst:503 +msgid "" +"This example represents an endorsed use of the ``goto`` statement in C! It " +"illustrates the use of :c:func:`PyErr_ExceptionMatches` and :c:func:" +"`PyErr_Clear` to handle specific exceptions, and the use of :c:func:" +"`Py_XDECREF` to dispose of owned references that may be *NULL* (note the " +"``'X'`` in the name; :c:func:`Py_DECREF` would crash when confronted with a " +"*NULL* reference). It is important that the variables used to hold owned " +"references are initialized to *NULL* for this to work; likewise, the " +"proposed return value is initialized to ``-1`` (failure) and only set to " +"success after the final call made is successful." +msgstr "" + +#: ../Doc/c-api/intro.rst:517 +msgid "Embedding Python" +msgstr "" + +#: ../Doc/c-api/intro.rst:519 +msgid "" +"The one important task that only embedders (as opposed to extension writers) " +"of the Python interpreter have to worry about is the initialization, and " +"possibly the finalization, of the Python interpreter. Most functionality of " +"the interpreter can only be used after the interpreter has been initialized." +msgstr "" + +#: ../Doc/c-api/intro.rst:532 +msgid "" +"The basic initialization function is :c:func:`Py_Initialize`. This " +"initializes the table of loaded modules, and creates the fundamental " +"modules :mod:`builtins`, :mod:`__main__`, and :mod:`sys`. It also " +"initializes the module search path (``sys.path``)." +msgstr "" + +#: ../Doc/c-api/intro.rst:539 +msgid "" +":c:func:`Py_Initialize` does not set the \"script argument list\" (``sys." +"argv``). If this variable is needed by Python code that will be executed " +"later, it must be set explicitly with a call to ``PySys_SetArgvEx(argc, " +"argv, updatepath)`` after the call to :c:func:`Py_Initialize`." +msgstr "" + +#: ../Doc/c-api/intro.rst:544 +msgid "" +"On most systems (in particular, on Unix and Windows, although the details " +"are slightly different), :c:func:`Py_Initialize` calculates the module " +"search path based upon its best guess for the location of the standard " +"Python interpreter executable, assuming that the Python library is found in " +"a fixed location relative to the Python interpreter executable. In " +"particular, it looks for a directory named :file:`lib/python{X.Y}` relative " +"to the parent directory where the executable named :file:`python` is found " +"on the shell command search path (the environment variable :envvar:`PATH`)." +msgstr "" + +#: ../Doc/c-api/intro.rst:553 +msgid "" +"For instance, if the Python executable is found in :file:`/usr/local/bin/" +"python`, it will assume that the libraries are in :file:`/usr/local/lib/" +"python{X.Y}`. (In fact, this particular path is also the \"fallback\" " +"location, used when no executable file named :file:`python` is found along :" +"envvar:`PATH`.) The user can override this behavior by setting the " +"environment variable :envvar:`PYTHONHOME`, or insert additional directories " +"in front of the standard path by setting :envvar:`PYTHONPATH`." +msgstr "" + +#: ../Doc/c-api/intro.rst:568 +msgid "" +"The embedding application can steer the search by calling " +"``Py_SetProgramName(file)`` *before* calling :c:func:`Py_Initialize`. Note " +"that :envvar:`PYTHONHOME` still overrides this and :envvar:`PYTHONPATH` is " +"still inserted in front of the standard path. An application that requires " +"total control has to provide its own implementation of :c:func:" +"`Py_GetPath`, :c:func:`Py_GetPrefix`, :c:func:`Py_GetExecPrefix`, and :c:" +"func:`Py_GetProgramFullPath` (all defined in :file:`Modules/getpath.c`)." +msgstr "" + +#: ../Doc/c-api/intro.rst:578 +msgid "" +"Sometimes, it is desirable to \"uninitialize\" Python. For instance, the " +"application may want to start over (make another call to :c:func:" +"`Py_Initialize`) or the application is simply done with its use of Python " +"and wants to free memory allocated by Python. This can be accomplished by " +"calling :c:func:`Py_FinalizeEx`. The function :c:func:`Py_IsInitialized` " +"returns true if Python is currently in the initialized state. More " +"information about these functions is given in a later chapter. Notice that :" +"c:func:`Py_FinalizeEx` does *not* free all memory allocated by the Python " +"interpreter, e.g. memory allocated by extension modules currently cannot be " +"released." +msgstr "" + +#: ../Doc/c-api/intro.rst:592 +msgid "Debugging Builds" +msgstr "" + +#: ../Doc/c-api/intro.rst:594 +msgid "" +"Python can be built with several macros to enable extra checks of the " +"interpreter and extension modules. These checks tend to add a large amount " +"of overhead to the runtime so they are not enabled by default." +msgstr "" + +#: ../Doc/c-api/intro.rst:598 +msgid "" +"A full list of the various types of debugging builds is in the file :file:" +"`Misc/SpecialBuilds.txt` in the Python source distribution. Builds are " +"available that support tracing of reference counts, debugging the memory " +"allocator, or low-level profiling of the main interpreter loop. Only the " +"most frequently-used builds will be described in the remainder of this " +"section." +msgstr "" + +#: ../Doc/c-api/intro.rst:604 +msgid "" +"Compiling the interpreter with the :c:macro:`Py_DEBUG` macro defined " +"produces what is generally meant by \"a debug build\" of Python. :c:macro:" +"`Py_DEBUG` is enabled in the Unix build by adding ``--with-pydebug`` to the :" +"file:`./configure` command. It is also implied by the presence of the not-" +"Python-specific :c:macro:`_DEBUG` macro. When :c:macro:`Py_DEBUG` is " +"enabled in the Unix build, compiler optimization is disabled." +msgstr "" + +#: ../Doc/c-api/intro.rst:611 +msgid "" +"In addition to the reference count debugging described below, the following " +"extra checks are performed:" +msgstr "" + +#: ../Doc/c-api/intro.rst:614 +msgid "Extra checks are added to the object allocator." +msgstr "" + +#: ../Doc/c-api/intro.rst:616 +msgid "Extra checks are added to the parser and compiler." +msgstr "" + +#: ../Doc/c-api/intro.rst:618 +msgid "" +"Downcasts from wide types to narrow types are checked for loss of " +"information." +msgstr "" + +#: ../Doc/c-api/intro.rst:620 +msgid "" +"A number of assertions are added to the dictionary and set implementations. " +"In addition, the set object acquires a :meth:`test_c_api` method." +msgstr "" + +#: ../Doc/c-api/intro.rst:623 +msgid "Sanity checks of the input arguments are added to frame creation." +msgstr "" + +#: ../Doc/c-api/intro.rst:625 +msgid "" +"The storage for ints is initialized with a known invalid pattern to catch " +"reference to uninitialized digits." +msgstr "" + +#: ../Doc/c-api/intro.rst:628 +msgid "" +"Low-level tracing and extra exception checking are added to the runtime " +"virtual machine." +msgstr "" + +#: ../Doc/c-api/intro.rst:631 +msgid "Extra checks are added to the memory arena implementation." +msgstr "" + +#: ../Doc/c-api/intro.rst:633 +msgid "Extra debugging is added to the thread module." +msgstr "" + +#: ../Doc/c-api/intro.rst:635 +msgid "There may be additional checks not mentioned here." +msgstr "" + +#: ../Doc/c-api/intro.rst:637 +msgid "" +"Defining :c:macro:`Py_TRACE_REFS` enables reference tracing. When defined, " +"a circular doubly linked list of active objects is maintained by adding two " +"extra fields to every :c:type:`PyObject`. Total allocations are tracked as " +"well. Upon exit, all existing references are printed. (In interactive mode " +"this happens after every statement run by the interpreter.) Implied by :c:" +"macro:`Py_DEBUG`." +msgstr "" + +#: ../Doc/c-api/intro.rst:643 +msgid "" +"Please refer to :file:`Misc/SpecialBuilds.txt` in the Python source " +"distribution for more detailed information." +msgstr "" + +#: ../Doc/c-api/iter.rst:6 +msgid "Iterator Protocol" +msgstr "" + +#: ../Doc/c-api/iter.rst:8 +msgid "There are two functions specifically for working with iterators." +msgstr "" + +#: ../Doc/c-api/iter.rst:12 +msgid "Return true if the object *o* supports the iterator protocol." +msgstr "" + +#: ../Doc/c-api/iter.rst:17 +msgid "" +"Return the next value from the iteration *o*. The object must be an " +"iterator (it is up to the caller to check this). If there are no remaining " +"values, returns *NULL* with no exception set. If an error occurs while " +"retrieving the item, returns *NULL* and passes along the exception." +msgstr "" + +#: ../Doc/c-api/iter.rst:22 +msgid "" +"To write a loop which iterates over an iterator, the C code should look " +"something like this::" +msgstr "" + +#: ../Doc/c-api/iterator.rst:6 +msgid "Iterator Objects" +msgstr "" + +#: ../Doc/c-api/iterator.rst:8 +msgid "" +"Python provides two general-purpose iterator objects. The first, a sequence " +"iterator, works with an arbitrary sequence supporting the :meth:" +"`__getitem__` method. The second works with a callable object and a " +"sentinel value, calling the callable for each item in the sequence, and " +"ending the iteration when the sentinel value is returned." +msgstr "" + +#: ../Doc/c-api/iterator.rst:17 +msgid "" +"Type object for iterator objects returned by :c:func:`PySeqIter_New` and the " +"one-argument form of the :func:`iter` built-in function for built-in " +"sequence types." +msgstr "" + +#: ../Doc/c-api/iterator.rst:24 +msgid "Return true if the type of *op* is :c:data:`PySeqIter_Type`." +msgstr "" + +#: ../Doc/c-api/iterator.rst:29 +msgid "" +"Return an iterator that works with a general sequence object, *seq*. The " +"iteration ends when the sequence raises :exc:`IndexError` for the " +"subscripting operation." +msgstr "" + +#: ../Doc/c-api/iterator.rst:36 +msgid "" +"Type object for iterator objects returned by :c:func:`PyCallIter_New` and " +"the two-argument form of the :func:`iter` built-in function." +msgstr "" + +#: ../Doc/c-api/iterator.rst:42 +msgid "Return true if the type of *op* is :c:data:`PyCallIter_Type`." +msgstr "" + +#: ../Doc/c-api/iterator.rst:47 +msgid "" +"Return a new iterator. The first parameter, *callable*, can be any Python " +"callable object that can be called with no parameters; each call to it " +"should return the next item in the iteration. When *callable* returns a " +"value equal to *sentinel*, the iteration will be terminated." +msgstr "" + +#: ../Doc/c-api/list.rst:6 +msgid "List Objects" +msgstr "" + +#: ../Doc/c-api/list.rst:13 +msgid "This subtype of :c:type:`PyObject` represents a Python list object." +msgstr "" + +#: ../Doc/c-api/list.rst:18 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python list type. " +"This is the same object as :class:`list` in the Python layer." +msgstr "" + +#: ../Doc/c-api/list.rst:24 +msgid "" +"Return true if *p* is a list object or an instance of a subtype of the list " +"type." +msgstr "" + +#: ../Doc/c-api/list.rst:30 +msgid "" +"Return true if *p* is a list object, but not an instance of a subtype of the " +"list type." +msgstr "" + +#: ../Doc/c-api/list.rst:36 +msgid "Return a new list of length *len* on success, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/list.rst:40 +msgid "" +"If *len* is greater than zero, the returned list object's items are set to " +"``NULL``. Thus you cannot use abstract API functions such as :c:func:" +"`PySequence_SetItem` or expose the object to Python code before setting all " +"items to a real object with :c:func:`PyList_SetItem`." +msgstr "" + +#: ../Doc/c-api/list.rst:50 +msgid "" +"Return the length of the list object in *list*; this is equivalent to " +"``len(list)`` on a list object." +msgstr "" + +#: ../Doc/c-api/list.rst:56 +msgid "Macro form of :c:func:`PyList_Size` without error checking." +msgstr "" + +#: ../Doc/c-api/list.rst:61 +msgid "" +"Return the object at position *index* in the list pointed to by *list*. The " +"position must be positive, indexing from the end of the list is not " +"supported. If *index* is out of bounds, return *NULL* and set an :exc:" +"`IndexError` exception." +msgstr "" + +#: ../Doc/c-api/list.rst:69 +msgid "Macro form of :c:func:`PyList_GetItem` without error checking." +msgstr "" + +#: ../Doc/c-api/list.rst:74 +msgid "" +"Set the item at index *index* in list to *item*. Return ``0`` on success or " +"``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/list.rst:79 +msgid "" +"This function \"steals\" a reference to *item* and discards a reference to " +"an item already in the list at the affected position." +msgstr "" + +#: ../Doc/c-api/list.rst:85 +msgid "" +"Macro form of :c:func:`PyList_SetItem` without error checking. This is " +"normally only used to fill in new lists where there is no previous content." +msgstr "" + +#: ../Doc/c-api/list.rst:90 +msgid "" +"This macro \"steals\" a reference to *item*, and, unlike :c:func:" +"`PyList_SetItem`, does *not* discard a reference to any item that is being " +"replaced; any reference in *list* at position *i* will be leaked." +msgstr "" + +#: ../Doc/c-api/list.rst:98 +msgid "" +"Insert the item *item* into list *list* in front of index *index*. Return " +"``0`` if successful; return ``-1`` and set an exception if unsuccessful. " +"Analogous to ``list.insert(index, item)``." +msgstr "" + +#: ../Doc/c-api/list.rst:105 +msgid "" +"Append the object *item* at the end of list *list*. Return ``0`` if " +"successful; return ``-1`` and set an exception if unsuccessful. Analogous " +"to ``list.append(item)``." +msgstr "" + +#: ../Doc/c-api/list.rst:112 +msgid "" +"Return a list of the objects in *list* containing the objects *between* " +"*low* and *high*. Return *NULL* and set an exception if unsuccessful. " +"Analogous to ``list[low:high]``. Negative indices, as when slicing from " +"Python, are not supported." +msgstr "" + +#: ../Doc/c-api/list.rst:120 +msgid "" +"Set the slice of *list* between *low* and *high* to the contents of " +"*itemlist*. Analogous to ``list[low:high] = itemlist``. The *itemlist* may " +"be *NULL*, indicating the assignment of an empty list (slice deletion). " +"Return ``0`` on success, ``-1`` on failure. Negative indices, as when " +"slicing from Python, are not supported." +msgstr "" + +#: ../Doc/c-api/list.rst:129 +msgid "" +"Sort the items of *list* in place. Return ``0`` on success, ``-1`` on " +"failure. This is equivalent to ``list.sort()``." +msgstr "" + +#: ../Doc/c-api/list.rst:135 +msgid "" +"Reverse the items of *list* in place. Return ``0`` on success, ``-1`` on " +"failure. This is the equivalent of ``list.reverse()``." +msgstr "" + +#: ../Doc/c-api/list.rst:143 +msgid "" +"Return a new tuple object containing the contents of *list*; equivalent to " +"``tuple(list)``." +msgstr "" + +#: ../Doc/c-api/long.rst:6 +msgid "Integer Objects" +msgstr "" + +#: ../Doc/c-api/long.rst:11 +msgid "" +"All integers are implemented as \"long\" integer objects of arbitrary size." +msgstr "" + +#: ../Doc/c-api/long.rst:15 +msgid "This subtype of :c:type:`PyObject` represents a Python integer object." +msgstr "" + +#: ../Doc/c-api/long.rst:20 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python integer type. " +"This is the same object as :class:`int` in the Python layer." +msgstr "" + +#: ../Doc/c-api/long.rst:26 +msgid "" +"Return true if its argument is a :c:type:`PyLongObject` or a subtype of :c:" +"type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:32 +msgid "" +"Return true if its argument is a :c:type:`PyLongObject`, but not a subtype " +"of :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:38 +msgid "" +"Return a new :c:type:`PyLongObject` object from *v*, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:40 +msgid "" +"The current implementation keeps an array of integer objects for all " +"integers between ``-5`` and ``256``, when you create an int in that range " +"you actually just get back a reference to the existing object. So it should " +"be possible to change the value of ``1``. I suspect the behaviour of Python " +"in this case is undefined. :-)" +msgstr "" + +#: ../Doc/c-api/long.rst:49 +msgid "" +"Return a new :c:type:`PyLongObject` object from a C :c:type:`unsigned long`, " +"or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:55 +msgid "" +"Return a new :c:type:`PyLongObject` object from a C :c:type:`Py_ssize_t`, or " +"*NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:61 +msgid "" +"Return a new :c:type:`PyLongObject` object from a C :c:type:`size_t`, or " +"*NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:67 +msgid "" +"Return a new :c:type:`PyLongObject` object from a C :c:type:`long long`, or " +"*NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:73 +msgid "" +"Return a new :c:type:`PyLongObject` object from a C :c:type:`unsigned long " +"long`, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:79 +msgid "" +"Return a new :c:type:`PyLongObject` object from the integer part of *v*, or " +"*NULL* on failure." +msgstr "" + +#: ../Doc/c-api/long.rst:85 +msgid "" +"Return a new :c:type:`PyLongObject` based on the string value in *str*, " +"which is interpreted according to the radix in *base*. If *pend* is non-" +"*NULL*, *\\*pend* will point to the first character in *str* which follows " +"the representation of the number. If *base* is ``0``, the radix will be " +"determined based on the leading characters of *str*: if *str* starts with " +"``'0x'`` or ``'0X'``, radix 16 will be used; if *str* starts with ``'0o'`` " +"or ``'0O'``, radix 8 will be used; if *str* starts with ``'0b'`` or " +"``'0B'``, radix 2 will be used; otherwise radix 10 will be used. If *base* " +"is not ``0``, it must be between ``2`` and ``36``, inclusive. Leading " +"spaces are ignored. If there are no digits, :exc:`ValueError` will be " +"raised." +msgstr "" + +#: ../Doc/c-api/long.rst:99 +msgid "" +"Convert a sequence of Unicode digits to a Python integer value. The Unicode " +"string is first encoded to a byte string using :c:func:" +"`PyUnicode_EncodeDecimal` and then converted using :c:func:" +"`PyLong_FromString`." +msgstr "" + +#: ../Doc/c-api/long.rst:105 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyLong_FromUnicodeObject()." +msgstr "" + +#: ../Doc/c-api/long.rst:105 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyLong_FromUnicodeObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:110 +msgid "" +"Convert a sequence of Unicode digits in the string *u* to a Python integer " +"value. The Unicode string is first encoded to a byte string using :c:func:" +"`PyUnicode_EncodeDecimal` and then converted using :c:func:" +"`PyLong_FromString`." +msgstr "" + +#: ../Doc/c-api/long.rst:120 +msgid "" +"Create a Python integer from the pointer *p*. The pointer value can be " +"retrieved from the resulting value using :c:func:`PyLong_AsVoidPtr`." +msgstr "" + +#: ../Doc/c-api/long.rst:131 ../Doc/c-api/long.rst:141 +msgid "" +"Return a C :c:type:`long` representation of *obj*. If *obj* is not an " +"instance of :c:type:`PyLongObject`, first call its :meth:`__int__` method " +"(if present) to convert it to a :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:135 ../Doc/c-api/long.rst:160 +msgid "" +"Raise :exc:`OverflowError` if the value of *obj* is out of range for a :c:" +"type:`long`." +msgstr "" + +#: ../Doc/c-api/long.rst:145 +msgid "" +"If the value of *obj* is greater than :const:`LONG_MAX` or less than :const:" +"`LONG_MIN`, set *\\*overflow* to ``1`` or ``-1``, respectively, and return " +"``-1``; otherwise, set *\\*overflow* to ``0``. If any other exception " +"occurs set *\\*overflow* to ``0`` and return ``-1`` as usual." +msgstr "" + +#: ../Doc/c-api/long.rst:156 ../Doc/c-api/long.rst:166 +msgid "" +"Return a C :c:type:`long long` representation of *obj*. If *obj* is not an " +"instance of :c:type:`PyLongObject`, first call its :meth:`__int__` method " +"(if present) to convert it to a :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:170 +msgid "" +"If the value of *obj* is greater than :const:`PY_LLONG_MAX` or less than :" +"const:`PY_LLONG_MIN`, set *\\*overflow* to ``1`` or ``-1``, respectively, " +"and return ``-1``; otherwise, set *\\*overflow* to ``0``. If any other " +"exception occurs set *\\*overflow* to ``0`` and return ``-1`` as usual." +msgstr "" + +#: ../Doc/c-api/long.rst:184 +msgid "" +"Return a C :c:type:`Py_ssize_t` representation of *pylong*. *pylong* must " +"be an instance of :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:187 +msgid "" +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" +"type:`Py_ssize_t`." +msgstr "" + +#: ../Doc/c-api/long.rst:197 +msgid "" +"Return a C :c:type:`unsigned long` representation of *pylong*. *pylong* " +"must be an instance of :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:200 +msgid "" +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" +"type:`unsigned long`." +msgstr "" + +#: ../Doc/c-api/long.rst:206 +msgid "" +"Return a C :c:type:`size_t` representation of *pylong*. *pylong* must be an " +"instance of :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:209 +msgid "" +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" +"type:`size_t`." +msgstr "" + +#: ../Doc/c-api/long.rst:218 +msgid "" +"Return a C :c:type:`unsigned long long` representation of *pylong*. " +"*pylong* must be an instance of :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:221 +msgid "" +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for an :" +"c:type:`unsigned long long`." +msgstr "" + +#: ../Doc/c-api/long.rst:224 +msgid "" +"A negative *pylong* now raises :exc:`OverflowError`, not :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/long.rst:230 +msgid "" +"Return a C :c:type:`unsigned long` representation of *obj*. If *obj* is not " +"an instance of :c:type:`PyLongObject`, first call its :meth:`__int__` method " +"(if present) to convert it to a :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:234 +msgid "" +"If the value of *obj* is out of range for an :c:type:`unsigned long`, return " +"the reduction of that value modulo :const:`ULONG_MAX + 1`." +msgstr "" + +#: ../Doc/c-api/long.rst:240 +msgid "" +"Return a C :c:type:`unsigned long long` representation of *obj*. If *obj* " +"is not an instance of :c:type:`PyLongObject`, first call its :meth:`__int__` " +"method (if present) to convert it to a :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:244 +msgid "" +"If the value of *obj* is out of range for an :c:type:`unsigned long long`, " +"return the reduction of that value modulo :const:`PY_ULLONG_MAX + 1`." +msgstr "" + +#: ../Doc/c-api/long.rst:250 +msgid "" +"Return a C :c:type:`double` representation of *pylong*. *pylong* must be an " +"instance of :c:type:`PyLongObject`." +msgstr "" + +#: ../Doc/c-api/long.rst:253 +msgid "" +"Raise :exc:`OverflowError` if the value of *pylong* is out of range for a :c:" +"type:`double`." +msgstr "" + +#: ../Doc/c-api/long.rst:259 +msgid "" +"Convert a Python integer *pylong* to a C :c:type:`void` pointer. If *pylong* " +"cannot be converted, an :exc:`OverflowError` will be raised. This is only " +"assured to produce a usable :c:type:`void` pointer for values created with :" +"c:func:`PyLong_FromVoidPtr`." +msgstr "" + +#: ../Doc/c-api/mapping.rst:6 +msgid "Mapping Protocol" +msgstr "" + +#: ../Doc/c-api/mapping.rst:11 +msgid "" +"Return ``1`` if the object provides mapping protocol, and ``0`` otherwise. " +"This function always succeeds." +msgstr "" + +#: ../Doc/c-api/mapping.rst:20 +msgid "" +"Returns the number of keys in object *o* on success, and ``-1`` on failure. " +"For objects that do not provide mapping protocol, this is equivalent to the " +"Python expression ``len(o)``." +msgstr "" + +#: ../Doc/c-api/mapping.rst:27 ../Doc/c-api/mapping.rst:33 +msgid "" +"Remove the mapping for object *key* from the object *o*. Return ``-1`` on " +"failure. This is equivalent to the Python statement ``del o[key]``." +msgstr "" + +#: ../Doc/c-api/mapping.rst:39 +msgid "" +"On success, return ``1`` if the mapping object has the key *key* and ``0`` " +"otherwise. This is equivalent to the Python expression ``key in o``. This " +"function always succeeds." +msgstr "" + +#: ../Doc/c-api/mapping.rst:46 +msgid "" +"Return ``1`` if the mapping object has the key *key* and ``0`` otherwise. " +"This is equivalent to the Python expression ``key in o``. This function " +"always succeeds." +msgstr "" + +#: ../Doc/c-api/mapping.rst:53 +msgid "" +"On success, return a list or tuple of the keys in object *o*. On failure, " +"return *NULL*." +msgstr "" + +#: ../Doc/c-api/mapping.rst:59 +msgid "" +"On success, return a list or tuple of the values in object *o*. On failure, " +"return *NULL*." +msgstr "" + +#: ../Doc/c-api/mapping.rst:65 +msgid "" +"On success, return a list or tuple of the items in object *o*, where each " +"item is a tuple containing a key-value pair. On failure, return *NULL*." +msgstr "" + +#: ../Doc/c-api/mapping.rst:71 ../Doc/c-api/object.rst:385 +msgid "" +"Return element of *o* corresponding to the object *key* or *NULL* on " +"failure. This is the equivalent of the Python expression ``o[key]``." +msgstr "" + +#: ../Doc/c-api/mapping.rst:77 +msgid "" +"Map the object *key* to the value *v* in object *o*. Returns ``-1`` on " +"failure. This is the equivalent of the Python statement ``o[key] = v``." +msgstr "" + +#: ../Doc/c-api/marshal.rst:6 +msgid "Data marshalling support" +msgstr "" + +#: ../Doc/c-api/marshal.rst:8 +msgid "" +"These routines allow C code to work with serialized objects using the same " +"data format as the :mod:`marshal` module. There are functions to write data " +"into the serialization format, and additional functions that can be used to " +"read the data back. Files used to store marshalled data must be opened in " +"binary mode." +msgstr "" + +#: ../Doc/c-api/marshal.rst:14 +msgid "Numeric values are stored with the least significant byte first." +msgstr "" + +#: ../Doc/c-api/marshal.rst:16 +msgid "" +"The module supports two versions of the data format: version 0 is the " +"historical version, version 1 shares interned strings in the file, and upon " +"unmarshalling. Version 2 uses a binary format for floating point numbers. " +"*Py_MARSHAL_VERSION* indicates the current file format (currently 2)." +msgstr "" + +#: ../Doc/c-api/marshal.rst:24 +msgid "" +"Marshal a :c:type:`long` integer, *value*, to *file*. This will only write " +"the least-significant 32 bits of *value*; regardless of the size of the " +"native :c:type:`long` type. *version* indicates the file format." +msgstr "" + +#: ../Doc/c-api/marshal.rst:31 +msgid "" +"Marshal a Python object, *value*, to *file*. *version* indicates the file " +"format." +msgstr "" + +#: ../Doc/c-api/marshal.rst:37 +msgid "" +"Return a string object containing the marshalled representation of *value*. " +"*version* indicates the file format." +msgstr "" + +#: ../Doc/c-api/marshal.rst:41 +msgid "The following functions allow marshalled values to be read back in." +msgstr "" + +#: ../Doc/c-api/marshal.rst:43 +msgid "" +"XXX What about error detection? It appears that reading past the end of the " +"file will always result in a negative numeric value (where that's relevant), " +"but it's not clear that negative values won't be handled properly when " +"there's no error. What's the right way to tell? Should only non-negative " +"values be written using these routines?" +msgstr "" + +#: ../Doc/c-api/marshal.rst:52 +msgid "" +"Return a C :c:type:`long` from the data stream in a :c:type:`FILE\\*` opened " +"for reading. Only a 32-bit value can be read in using this function, " +"regardless of the native size of :c:type:`long`." +msgstr "" + +#: ../Doc/c-api/marshal.rst:56 ../Doc/c-api/marshal.rst:65 +msgid "On error, raise an exception and return ``-1``." +msgstr "" + +#: ../Doc/c-api/marshal.rst:61 +msgid "" +"Return a C :c:type:`short` from the data stream in a :c:type:`FILE\\*` " +"opened for reading. Only a 16-bit value can be read in using this function, " +"regardless of the native size of :c:type:`short`." +msgstr "" + +#: ../Doc/c-api/marshal.rst:70 +msgid "" +"Return a Python object from the data stream in a :c:type:`FILE\\*` opened " +"for reading." +msgstr "" + +#: ../Doc/c-api/marshal.rst:73 ../Doc/c-api/marshal.rst:87 +#: ../Doc/c-api/marshal.rst:96 +msgid "" +"On error, sets the appropriate exception (:exc:`EOFError` or :exc:" +"`TypeError`) and returns *NULL*." +msgstr "" + +#: ../Doc/c-api/marshal.rst:79 +msgid "" +"Return a Python object from the data stream in a :c:type:`FILE\\*` opened " +"for reading. Unlike :c:func:`PyMarshal_ReadObjectFromFile`, this function " +"assumes that no further objects will be read from the file, allowing it to " +"aggressively load file data into memory so that the de-serialization can " +"operate from data in memory rather than reading a byte at a time from the " +"file. Only use these variant if you are certain that you won't be reading " +"anything else from the file." +msgstr "" + +#: ../Doc/c-api/marshal.rst:93 +msgid "" +"Return a Python object from the data stream in a character buffer containing " +"*len* bytes pointed to by *string*." +msgstr "" + +#: ../Doc/c-api/memory.rst:8 +msgid "Memory Management" +msgstr "" + +#: ../Doc/c-api/memory.rst:17 +msgid "Overview" +msgstr "" + +#: ../Doc/c-api/memory.rst:19 +msgid "" +"Memory management in Python involves a private heap containing all Python " +"objects and data structures. The management of this private heap is ensured " +"internally by the *Python memory manager*. The Python memory manager has " +"different components which deal with various dynamic storage management " +"aspects, like sharing, segmentation, preallocation or caching." +msgstr "" + +#: ../Doc/c-api/memory.rst:25 +msgid "" +"At the lowest level, a raw memory allocator ensures that there is enough " +"room in the private heap for storing all Python-related data by interacting " +"with the memory manager of the operating system. On top of the raw memory " +"allocator, several object-specific allocators operate on the same heap and " +"implement distinct memory management policies adapted to the peculiarities " +"of every object type. For example, integer objects are managed differently " +"within the heap than strings, tuples or dictionaries because integers imply " +"different storage requirements and speed/space tradeoffs. The Python memory " +"manager thus delegates some of the work to the object-specific allocators, " +"but ensures that the latter operate within the bounds of the private heap." +msgstr "" + +#: ../Doc/c-api/memory.rst:36 +msgid "" +"It is important to understand that the management of the Python heap is " +"performed by the interpreter itself and that the user has no control over " +"it, even if she regularly manipulates object pointers to memory blocks " +"inside that heap. The allocation of heap space for Python objects and other " +"internal buffers is performed on demand by the Python memory manager through " +"the Python/C API functions listed in this document." +msgstr "" + +#: ../Doc/c-api/memory.rst:49 +msgid "" +"To avoid memory corruption, extension writers should never try to operate on " +"Python objects with the functions exported by the C library: :c:func:" +"`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`. This will " +"result in mixed calls between the C allocator and the Python memory manager " +"with fatal consequences, because they implement different algorithms and " +"operate on different heaps. However, one may safely allocate and release " +"memory blocks with the C library allocator for individual purposes, as shown " +"in the following example::" +msgstr "" + +#: ../Doc/c-api/memory.rst:68 +msgid "" +"In this example, the memory request for the I/O buffer is handled by the C " +"library allocator. The Python memory manager is involved only in the " +"allocation of the string object returned as a result." +msgstr "" + +#: ../Doc/c-api/memory.rst:72 +msgid "" +"In most situations, however, it is recommended to allocate memory from the " +"Python heap specifically because the latter is under control of the Python " +"memory manager. For example, this is required when the interpreter is " +"extended with new object types written in C. Another reason for using the " +"Python heap is the desire to *inform* the Python memory manager about the " +"memory needs of the extension module. Even when the requested memory is used " +"exclusively for internal, highly-specific purposes, delegating all memory " +"requests to the Python memory manager causes the interpreter to have a more " +"accurate image of its memory footprint as a whole. Consequently, under " +"certain circumstances, the Python memory manager may or may not trigger " +"appropriate actions, like garbage collection, memory compaction or other " +"preventive procedures. Note that by using the C library allocator as shown " +"in the previous example, the allocated memory for the I/O buffer escapes " +"completely the Python memory manager." +msgstr "" + +#: ../Doc/c-api/memory.rst:88 +msgid "" +"The :envvar:`PYTHONMALLOC` environment variable can be used to configure the " +"memory allocators used by Python." +msgstr "" + +#: ../Doc/c-api/memory.rst:91 +msgid "" +"The :envvar:`PYTHONMALLOCSTATS` environment variable can be used to print " +"statistics of the :ref:`pymalloc memory allocator ` every time a " +"new pymalloc object arena is created, and on shutdown." +msgstr "" + +#: ../Doc/c-api/memory.rst:97 +msgid "Raw Memory Interface" +msgstr "" + +#: ../Doc/c-api/memory.rst:99 +msgid "" +"The following function sets are wrappers to the system allocator. These " +"functions are thread-safe, the :term:`GIL ` does " +"not need to be held." +msgstr "" + +#: ../Doc/c-api/memory.rst:103 +msgid "" +"The default raw memory block allocator uses the following functions: :c:func:" +"`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`; call " +"``malloc(1)`` (or ``calloc(1, 1)``) when requesting zero bytes." +msgstr "" + +#: ../Doc/c-api/memory.rst:111 ../Doc/c-api/memory.rst:181 +msgid "" +"Allocates *n* bytes and returns a pointer of type :c:type:`void\\*` to the " +"allocated memory, or *NULL* if the request fails." +msgstr "" + +#: ../Doc/c-api/memory.rst:114 +msgid "" +"Requesting zero bytes returns a distinct non-*NULL* pointer if possible, as " +"if ``PyMem_RawMalloc(1)`` had been called instead. The memory will not have " +"been initialized in any way." +msgstr "" + +#: ../Doc/c-api/memory.rst:121 ../Doc/c-api/memory.rst:191 +msgid "" +"Allocates *nelem* elements each whose size in bytes is *elsize* and returns " +"a pointer of type :c:type:`void\\*` to the allocated memory, or *NULL* if " +"the request fails. The memory is initialized to zeros." +msgstr "" + +#: ../Doc/c-api/memory.rst:125 +msgid "" +"Requesting zero elements or elements of size zero bytes returns a distinct " +"non-*NULL* pointer if possible, as if ``PyMem_RawCalloc(1, 1)`` had been " +"called instead." +msgstr "" + +#: ../Doc/c-api/memory.rst:134 ../Doc/c-api/memory.rst:204 +msgid "" +"Resizes the memory block pointed to by *p* to *n* bytes. The contents will " +"be unchanged to the minimum of the old and the new sizes." +msgstr "" + +#: ../Doc/c-api/memory.rst:137 +msgid "" +"If *p* is *NULL*, the call is equivalent to ``PyMem_RawMalloc(n)``; else if " +"*n* is equal to zero, the memory block is resized but is not freed, and the " +"returned pointer is non-*NULL*." +msgstr "" + +#: ../Doc/c-api/memory.rst:141 +msgid "" +"Unless *p* is *NULL*, it must have been returned by a previous call to :c:" +"func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` or :c:func:" +"`PyMem_RawCalloc`." +msgstr "" + +#: ../Doc/c-api/memory.rst:145 +msgid "" +"If the request fails, :c:func:`PyMem_RawRealloc` returns *NULL* and *p* " +"remains a valid pointer to the previous memory area." +msgstr "" + +#: ../Doc/c-api/memory.rst:151 +msgid "" +"Frees the memory block pointed to by *p*, which must have been returned by a " +"previous call to :c:func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` or :c:" +"func:`PyMem_RawCalloc`. Otherwise, or if ``PyMem_Free(p)`` has been called " +"before, undefined behavior occurs." +msgstr "" + +#: ../Doc/c-api/memory.rst:156 ../Doc/c-api/memory.rst:225 +msgid "If *p* is *NULL*, no operation is performed." +msgstr "" + +#: ../Doc/c-api/memory.rst:162 +msgid "Memory Interface" +msgstr "" + +#: ../Doc/c-api/memory.rst:164 +msgid "" +"The following function sets, modeled after the ANSI C standard, but " +"specifying behavior when requesting zero bytes, are available for allocating " +"and releasing memory from the Python heap." +msgstr "" + +#: ../Doc/c-api/memory.rst:168 +msgid "" +"By default, these functions use :ref:`pymalloc memory allocator `." +msgstr "" + +#: ../Doc/c-api/memory.rst:172 +msgid "" +"The :term:`GIL ` must be held when using these " +"functions." +msgstr "" + +#: ../Doc/c-api/memory.rst:177 +msgid "" +"The default allocator is now pymalloc instead of system :c:func:`malloc`." +msgstr "" + +#: ../Doc/c-api/memory.rst:184 +msgid "" +"Requesting zero bytes returns a distinct non-*NULL* pointer if possible, as " +"if ``PyMem_Malloc(1)`` had been called instead. The memory will not have " +"been initialized in any way." +msgstr "" + +#: ../Doc/c-api/memory.rst:195 +msgid "" +"Requesting zero elements or elements of size zero bytes returns a distinct " +"non-*NULL* pointer if possible, as if ``PyMem_Calloc(1, 1)`` had been called " +"instead." +msgstr "" + +#: ../Doc/c-api/memory.rst:207 +msgid "" +"If *p* is *NULL*, the call is equivalent to ``PyMem_Malloc(n)``; else if *n* " +"is equal to zero, the memory block is resized but is not freed, and the " +"returned pointer is non-*NULL*." +msgstr "" + +#: ../Doc/c-api/memory.rst:211 +msgid "" +"Unless *p* is *NULL*, it must have been returned by a previous call to :c:" +"func:`PyMem_Malloc`, :c:func:`PyMem_Realloc` or :c:func:`PyMem_Calloc`." +msgstr "" + +#: ../Doc/c-api/memory.rst:214 +msgid "" +"If the request fails, :c:func:`PyMem_Realloc` returns *NULL* and *p* remains " +"a valid pointer to the previous memory area." +msgstr "" + +#: ../Doc/c-api/memory.rst:220 +msgid "" +"Frees the memory block pointed to by *p*, which must have been returned by a " +"previous call to :c:func:`PyMem_Malloc`, :c:func:`PyMem_Realloc` or :c:func:" +"`PyMem_Calloc`. Otherwise, or if ``PyMem_Free(p)`` has been called before, " +"undefined behavior occurs." +msgstr "" + +#: ../Doc/c-api/memory.rst:227 +msgid "" +"The following type-oriented macros are provided for convenience. Note that " +"*TYPE* refers to any C type." +msgstr "" + +#: ../Doc/c-api/memory.rst:233 +msgid "" +"Same as :c:func:`PyMem_Malloc`, but allocates ``(n * sizeof(TYPE))`` bytes " +"of memory. Returns a pointer cast to :c:type:`TYPE\\*`. The memory will " +"not have been initialized in any way." +msgstr "" + +#: ../Doc/c-api/memory.rst:240 +msgid "" +"Same as :c:func:`PyMem_Realloc`, but the memory block is resized to ``(n * " +"sizeof(TYPE))`` bytes. Returns a pointer cast to :c:type:`TYPE\\*`. On " +"return, *p* will be a pointer to the new memory area, or *NULL* in the event " +"of failure." +msgstr "" + +#: ../Doc/c-api/memory.rst:245 +msgid "" +"This is a C preprocessor macro; *p* is always reassigned. Save the original " +"value of *p* to avoid losing memory when handling errors." +msgstr "" + +#: ../Doc/c-api/memory.rst:251 +msgid "Same as :c:func:`PyMem_Free`." +msgstr "" + +#: ../Doc/c-api/memory.rst:253 +msgid "" +"In addition, the following macro sets are provided for calling the Python " +"memory allocator directly, without involving the C API functions listed " +"above. However, note that their use does not preserve binary compatibility " +"across Python versions and is therefore deprecated in extension modules." +msgstr "" + +#: ../Doc/c-api/memory.rst:258 +msgid "``PyMem_MALLOC(size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:259 +msgid "``PyMem_NEW(type, size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:260 +msgid "``PyMem_REALLOC(ptr, size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:261 +msgid "``PyMem_RESIZE(ptr, type, size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:262 +msgid "``PyMem_FREE(ptr)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:263 +msgid "``PyMem_DEL(ptr)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:267 +msgid "Customize Memory Allocators" +msgstr "" + +#: ../Doc/c-api/memory.rst:273 +msgid "" +"Structure used to describe a memory block allocator. The structure has four " +"fields:" +msgstr "" + +#: ../Doc/c-api/memory.rst:277 ../Doc/c-api/memory.rst:414 +#: ../Doc/c-api/structures.rst:129 ../Doc/c-api/structures.rst:241 +#: ../Doc/c-api/tuple.rst:145 ../Doc/c-api/tuple.rst:168 +msgid "Field" +msgstr "" + +#: ../Doc/c-api/memory.rst:279 ../Doc/c-api/memory.rst:416 +msgid "``void *ctx``" +msgstr "" + +#: ../Doc/c-api/memory.rst:279 ../Doc/c-api/memory.rst:416 +msgid "user context passed as first argument" +msgstr "" + +#: ../Doc/c-api/memory.rst:281 +msgid "``void* malloc(void *ctx, size_t size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:281 +msgid "allocate a memory block" +msgstr "" + +#: ../Doc/c-api/memory.rst:283 +msgid "``void* calloc(void *ctx, size_t nelem, size_t elsize)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:283 +msgid "allocate a memory block initialized with zeros" +msgstr "" + +#: ../Doc/c-api/memory.rst:286 +msgid "``void* realloc(void *ctx, void *ptr, size_t new_size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:286 +msgid "allocate or resize a memory block" +msgstr "" + +#: ../Doc/c-api/memory.rst:288 +msgid "``void free(void *ctx, void *ptr)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:288 +msgid "free a memory block" +msgstr "" + +#: ../Doc/c-api/memory.rst:291 +msgid "" +"The :c:type:`PyMemAllocator` structure was renamed to :c:type:" +"`PyMemAllocatorEx` and a new ``calloc`` field was added." +msgstr "" + +#: ../Doc/c-api/memory.rst:298 +msgid "Enum used to identify an allocator domain. Domains:" +msgstr "" + +#: ../Doc/c-api/memory.rst:302 ../Doc/c-api/memory.rst:311 +#: ../Doc/c-api/memory.rst:320 +msgid "Functions:" +msgstr "" + +#: ../Doc/c-api/memory.rst:304 +msgid ":c:func:`PyMem_RawMalloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:305 +msgid ":c:func:`PyMem_RawRealloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:306 +msgid ":c:func:`PyMem_RawCalloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:307 +msgid ":c:func:`PyMem_RawFree`" +msgstr "" + +#: ../Doc/c-api/memory.rst:313 +msgid ":c:func:`PyMem_Malloc`," +msgstr "" + +#: ../Doc/c-api/memory.rst:314 +msgid ":c:func:`PyMem_Realloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:315 +msgid ":c:func:`PyMem_Calloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:316 +msgid ":c:func:`PyMem_Free`" +msgstr "" + +#: ../Doc/c-api/memory.rst:322 +msgid ":c:func:`PyObject_Malloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:323 +msgid ":c:func:`PyObject_Realloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:324 +msgid ":c:func:`PyObject_Calloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:325 +msgid ":c:func:`PyObject_Free`" +msgstr "" + +#: ../Doc/c-api/memory.rst:329 +msgid "Get the memory block allocator of the specified domain." +msgstr "" + +#: ../Doc/c-api/memory.rst:334 +msgid "Set the memory block allocator of the specified domain." +msgstr "" + +#: ../Doc/c-api/memory.rst:336 +msgid "" +"The new allocator must return a distinct non-NULL pointer when requesting " +"zero bytes." +msgstr "" + +#: ../Doc/c-api/memory.rst:339 +msgid "" +"For the :c:data:`PYMEM_DOMAIN_RAW` domain, the allocator must be thread-" +"safe: the :term:`GIL ` is not held when the " +"allocator is called." +msgstr "" + +#: ../Doc/c-api/memory.rst:343 +msgid "" +"If the new allocator is not a hook (does not call the previous allocator), " +"the :c:func:`PyMem_SetupDebugHooks` function must be called to reinstall the " +"debug hooks on top on the new allocator." +msgstr "" + +#: ../Doc/c-api/memory.rst:350 +msgid "Setup hooks to detect bugs in the Python memory allocator functions." +msgstr "" + +#: ../Doc/c-api/memory.rst:352 +msgid "" +"Newly allocated memory is filled with the byte ``0xCB``, freed memory is " +"filled with the byte ``0xDB``." +msgstr "" + +#: ../Doc/c-api/memory.rst:355 +msgid "Runtime checks:" +msgstr "" + +#: ../Doc/c-api/memory.rst:357 +msgid "" +"Detect API violations, ex: :c:func:`PyObject_Free` called on a buffer " +"allocated by :c:func:`PyMem_Malloc`" +msgstr "" + +#: ../Doc/c-api/memory.rst:359 +msgid "Detect write before the start of the buffer (buffer underflow)" +msgstr "" + +#: ../Doc/c-api/memory.rst:360 +msgid "Detect write after the end of the buffer (buffer overflow)" +msgstr "" + +#: ../Doc/c-api/memory.rst:361 +msgid "" +"Check that the :term:`GIL ` is held when allocator " +"functions of :c:data:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) and :" +"c:data:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) domains are called" +msgstr "" + +#: ../Doc/c-api/memory.rst:366 +msgid "" +"On error, the debug hooks use the :mod:`tracemalloc` module to get the " +"traceback where a memory block was allocated. The traceback is only " +"displayed if :mod:`tracemalloc` is tracing Python memory allocations and the " +"memory block was traced." +msgstr "" + +#: ../Doc/c-api/memory.rst:371 +msgid "" +"These hooks are installed by default if Python is compiled in debug mode. " +"The :envvar:`PYTHONMALLOC` environment variable can be used to install debug " +"hooks on a Python compiled in release mode." +msgstr "" + +#: ../Doc/c-api/memory.rst:375 +msgid "" +"This function now also works on Python compiled in release mode. On error, " +"the debug hooks now use :mod:`tracemalloc` to get the traceback where a " +"memory block was allocated. The debug hooks now also check if the GIL is " +"held when functions of :c:data:`PYMEM_DOMAIN_OBJ` and :c:data:" +"`PYMEM_DOMAIN_MEM` domains are called." +msgstr "" + +#: ../Doc/c-api/memory.rst:386 +msgid "The pymalloc allocator" +msgstr "" + +#: ../Doc/c-api/memory.rst:388 +msgid "" +"Python has a *pymalloc* allocator optimized for small objects (smaller or " +"equal to 512 bytes) with a short lifetime. It uses memory mappings called " +"\"arenas\" with a fixed size of 256 KB. It falls back to :c:func:" +"`PyMem_RawMalloc` and :c:func:`PyMem_RawRealloc` for allocations larger than " +"512 bytes." +msgstr "" + +#: ../Doc/c-api/memory.rst:393 +msgid "" +"*pymalloc* is the default allocator of the :c:data:`PYMEM_DOMAIN_MEM` (ex: :" +"c:func:`PyObject_Malloc`) and :c:data:`PYMEM_DOMAIN_OBJ` (ex: :c:func:" +"`PyObject_Malloc`) domains." +msgstr "" + +#: ../Doc/c-api/memory.rst:397 +msgid "The arena allocator uses the following functions:" +msgstr "" + +#: ../Doc/c-api/memory.rst:399 +msgid ":c:func:`VirtualAlloc` and :c:func:`VirtualFree` on Windows," +msgstr "" + +#: ../Doc/c-api/memory.rst:400 +msgid ":c:func:`mmap` and :c:func:`munmap` if available," +msgstr "" + +#: ../Doc/c-api/memory.rst:401 +msgid ":c:func:`malloc` and :c:func:`free` otherwise." +msgstr "" + +#: ../Doc/c-api/memory.rst:404 +msgid "Customize pymalloc Arena Allocator" +msgstr "" + +#: ../Doc/c-api/memory.rst:410 +msgid "" +"Structure used to describe an arena allocator. The structure has three " +"fields:" +msgstr "" + +#: ../Doc/c-api/memory.rst:418 +msgid "``void* alloc(void *ctx, size_t size)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:418 +msgid "allocate an arena of size bytes" +msgstr "" + +#: ../Doc/c-api/memory.rst:420 +msgid "``void free(void *ctx, size_t size, void *ptr)``" +msgstr "" + +#: ../Doc/c-api/memory.rst:420 +msgid "free an arena" +msgstr "" + +#: ../Doc/c-api/memory.rst:425 +msgid "Get the arena allocator." +msgstr "" + +#: ../Doc/c-api/memory.rst:429 +msgid "Set the arena allocator." +msgstr "" + +#: ../Doc/c-api/memory.rst:435 +msgid "Examples" +msgstr "" + +#: ../Doc/c-api/memory.rst:437 +msgid "" +"Here is the example from section :ref:`memoryoverview`, rewritten so that " +"the I/O buffer is allocated from the Python heap by using the first function " +"set::" +msgstr "" + +#: ../Doc/c-api/memory.rst:450 +msgid "The same code using the type-oriented function set::" +msgstr "" + +#: ../Doc/c-api/memory.rst:462 +msgid "" +"Note that in the two examples above, the buffer is always manipulated via " +"functions belonging to the same set. Indeed, it is required to use the same " +"memory API family for a given memory block, so that the risk of mixing " +"different allocators is reduced to a minimum. The following code sequence " +"contains two errors, one of which is labeled as *fatal* because it mixes two " +"different allocators operating on different heaps. ::" +msgstr "" + +#: ../Doc/c-api/memory.rst:477 +msgid "" +"In addition to the functions aimed at handling raw memory blocks from the " +"Python heap, objects in Python are allocated and released with :c:func:" +"`PyObject_New`, :c:func:`PyObject_NewVar` and :c:func:`PyObject_Del`." +msgstr "" + +#: ../Doc/c-api/memory.rst:481 +msgid "" +"These will be explained in the next chapter on defining and implementing new " +"object types in C." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:9 +msgid "MemoryView objects" +msgstr "" + +#: ../Doc/c-api/memoryview.rst:11 +msgid "" +"A :class:`memoryview` object exposes the C level :ref:`buffer interface " +"` as a Python object which can then be passed around like any " +"other object." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:18 +msgid "" +"Create a memoryview object from an object that provides the buffer " +"interface. If *obj* supports writable buffer exports, the memoryview object " +"will be read/write, otherwise it may be either read-only or read/write at " +"the discretion of the exporter." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:25 +msgid "" +"Create a memoryview object using *mem* as the underlying buffer. *flags* can " +"be one of :c:macro:`PyBUF_READ` or :c:macro:`PyBUF_WRITE`." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:32 +msgid "" +"Create a memoryview object wrapping the given buffer structure *view*. For " +"simple byte buffers, :c:func:`PyMemoryView_FromMemory` is the preferred " +"function." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:38 +msgid "" +"Create a memoryview object to a :term:`contiguous` chunk of memory (in " +"either 'C' or 'F'ortran *order*) from an object that defines the buffer " +"interface. If memory is contiguous, the memoryview object points to the " +"original memory. Otherwise, a copy is made and the memoryview points to a " +"new bytes object." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:47 +msgid "" +"Return true if the object *obj* is a memoryview object. It is not currently " +"allowed to create subclasses of :class:`memoryview`." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:53 +msgid "" +"Return a pointer to the memoryview's private copy of the exporter's buffer. " +"*mview* **must** be a memoryview instance; this macro doesn't check its " +"type, you must do it yourself or you will risk crashes." +msgstr "" + +#: ../Doc/c-api/memoryview.rst:59 +msgid "" +"Return either a pointer to the exporting object that the memoryview is based " +"on or *NULL* if the memoryview has been created by one of the functions :c:" +"func:`PyMemoryView_FromMemory` or :c:func:`PyMemoryView_FromBuffer`. *mview* " +"**must** be a memoryview instance." +msgstr "" + +#: ../Doc/c-api/method.rst:6 +msgid "Instance Method Objects" +msgstr "" + +#: ../Doc/c-api/method.rst:10 +msgid "" +"An instance method is a wrapper for a :c:data:`PyCFunction` and the new way " +"to bind a :c:data:`PyCFunction` to a class object. It replaces the former " +"call ``PyMethod_New(func, NULL, class)``." +msgstr "" + +#: ../Doc/c-api/method.rst:17 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python instance " +"method type. It is not exposed to Python programs." +msgstr "" + +#: ../Doc/c-api/method.rst:23 +msgid "" +"Return true if *o* is an instance method object (has type :c:data:" +"`PyInstanceMethod_Type`). The parameter must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/method.rst:29 +msgid "" +"Return a new instance method object, with *func* being any callable object " +"*func* is the function that will be called when the instance method is " +"called." +msgstr "" + +#: ../Doc/c-api/method.rst:36 +msgid "Return the function object associated with the instance method *im*." +msgstr "" + +#: ../Doc/c-api/method.rst:41 +msgid "" +"Macro version of :c:func:`PyInstanceMethod_Function` which avoids error " +"checking." +msgstr "" + +#: ../Doc/c-api/method.rst:47 +msgid "Method Objects" +msgstr "" + +#: ../Doc/c-api/method.rst:51 +msgid "" +"Methods are bound function objects. Methods are always bound to an instance " +"of a user-defined class. Unbound methods (methods bound to a class object) " +"are no longer available." +msgstr "" + +#: ../Doc/c-api/method.rst:60 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python method type. " +"This is exposed to Python programs as ``types.MethodType``." +msgstr "" + +#: ../Doc/c-api/method.rst:66 +msgid "" +"Return true if *o* is a method object (has type :c:data:`PyMethod_Type`). " +"The parameter must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/method.rst:72 +msgid "" +"Return a new method object, with *func* being any callable object and *self* " +"the instance the method should be bound. *func* is the function that will be " +"called when the method is called. *self* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/method.rst:79 +msgid "Return the function object associated with the method *meth*." +msgstr "" + +#: ../Doc/c-api/method.rst:84 +msgid "" +"Macro version of :c:func:`PyMethod_Function` which avoids error checking." +msgstr "" + +#: ../Doc/c-api/method.rst:89 +msgid "Return the instance associated with the method *meth*." +msgstr "" + +#: ../Doc/c-api/method.rst:94 +msgid "Macro version of :c:func:`PyMethod_Self` which avoids error checking." +msgstr "" + +#: ../Doc/c-api/module.rst:6 +msgid "Module Objects" +msgstr "" + +#: ../Doc/c-api/module.rst:15 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python module type. " +"This is exposed to Python programs as ``types.ModuleType``." +msgstr "" + +#: ../Doc/c-api/module.rst:21 +msgid "Return true if *p* is a module object, or a subtype of a module object." +msgstr "" + +#: ../Doc/c-api/module.rst:26 +msgid "" +"Return true if *p* is a module object, but not a subtype of :c:data:" +"`PyModule_Type`." +msgstr "" + +#: ../Doc/c-api/module.rst:39 +msgid "" +"Return a new module object with the :attr:`__name__` attribute set to " +"*name*. The module's :attr:`__name__`, :attr:`__doc__`, :attr:`__package__`, " +"and :attr:`__loader__` attributes are filled in (all but :attr:`__name__` " +"are set to ``None``); the caller is responsible for providing a :attr:" +"`__file__` attribute." +msgstr "" + +#: ../Doc/c-api/module.rst:47 +msgid ":attr:`__package__` and :attr:`__loader__` are set to ``None``." +msgstr "" + +#: ../Doc/c-api/module.rst:53 +msgid "" +"Similar to :c:func:`PyImport_NewObject`, but the name is a UTF-8 encoded " +"string instead of a Unicode object." +msgstr "" + +#: ../Doc/c-api/module.rst:61 +msgid "" +"Return the dictionary object that implements *module*'s namespace; this " +"object is the same as the :attr:`~object.__dict__` attribute of the module " +"object. If *module* is not a module object (or a subtype of a module " +"object), :exc:`SystemError` is raised and *NULL* is returned." +msgstr "" + +#: ../Doc/c-api/module.rst:66 +msgid "" +"It is recommended extensions use other :c:func:`PyModule_\\*` and :c:func:" +"`PyObject_\\*` functions rather than directly manipulate a module's :attr:" +"`~object.__dict__`." +msgstr "" + +#: ../Doc/c-api/module.rst:77 +msgid "" +"Return *module*'s :attr:`__name__` value. If the module does not provide " +"one, or if it is not a string, :exc:`SystemError` is raised and *NULL* is " +"returned." +msgstr "" + +#: ../Doc/c-api/module.rst:85 +msgid "" +"Similar to :c:func:`PyModule_GetNameObject` but return the name encoded to " +"``'utf-8'``." +msgstr "" + +#: ../Doc/c-api/module.rst:90 +msgid "" +"Return the \"state\" of the module, that is, a pointer to the block of " +"memory allocated at module creation time, or *NULL*. See :c:member:" +"`PyModuleDef.m_size`." +msgstr "" + +#: ../Doc/c-api/module.rst:97 +msgid "" +"Return a pointer to the :c:type:`PyModuleDef` struct from which the module " +"was created, or *NULL* if the module wasn't created from a definition." +msgstr "" + +#: ../Doc/c-api/module.rst:107 +msgid "" +"Return the name of the file from which *module* was loaded using *module*'s :" +"attr:`__file__` attribute. If this is not defined, or if it is not a " +"unicode string, raise :exc:`SystemError` and return *NULL*; otherwise return " +"a reference to a Unicode object." +msgstr "" + +#: ../Doc/c-api/module.rst:117 +msgid "" +"Similar to :c:func:`PyModule_GetFilenameObject` but return the filename " +"encoded to 'utf-8'." +msgstr "" + +#: ../Doc/c-api/module.rst:120 +msgid "" +":c:func:`PyModule_GetFilename` raises :c:type:`UnicodeEncodeError` on " +"unencodable filenames, use :c:func:`PyModule_GetFilenameObject` instead." +msgstr "" + +#: ../Doc/c-api/module.rst:128 +msgid "Initializing C modules" +msgstr "" + +#: ../Doc/c-api/module.rst:130 +msgid "" +"Modules objects are usually created from extension modules (shared libraries " +"which export an initialization function), or compiled-in modules (where the " +"initialization function is added using :c:func:`PyImport_AppendInittab`). " +"See :ref:`building` or :ref:`extending-with-embedding` for details." +msgstr "" + +#: ../Doc/c-api/module.rst:135 +msgid "" +"The initialization function can either pass a module definition instance to :" +"c:func:`PyModule_Create`, and return the resulting module object, or request " +"\"multi-phase initialization\" by returning the definition struct itself." +msgstr "" + +#: ../Doc/c-api/module.rst:141 +msgid "" +"The module definition struct, which holds all information needed to create a " +"module object. There is usually only one statically initialized variable of " +"this type for each module." +msgstr "" + +#: ../Doc/c-api/module.rst:147 +msgid "Always initialize this member to :const:`PyModuleDef_HEAD_INIT`." +msgstr "" + +#: ../Doc/c-api/module.rst:151 +msgid "Name for the new module." +msgstr "" + +#: ../Doc/c-api/module.rst:155 +msgid "" +"Docstring for the module; usually a docstring variable created with :c:func:" +"`PyDoc_STRVAR` is used." +msgstr "" + +#: ../Doc/c-api/module.rst:160 +msgid "" +"Module state may be kept in a per-module memory area that can be retrieved " +"with :c:func:`PyModule_GetState`, rather than in static globals. This makes " +"modules safe for use in multiple sub-interpreters." +msgstr "" + +#: ../Doc/c-api/module.rst:164 +msgid "" +"This memory area is allocated based on *m_size* on module creation, and " +"freed when the module object is deallocated, after the :c:member:`m_free` " +"function has been called, if present." +msgstr "" + +#: ../Doc/c-api/module.rst:168 +msgid "" +"Setting ``m_size`` to ``-1`` means that the module does not support sub-" +"interpreters, because it has global state." +msgstr "" + +#: ../Doc/c-api/module.rst:171 +msgid "" +"Setting it to a non-negative value means that the module can be re-" +"initialized and specifies the additional amount of memory it requires for " +"its state. Non-negative ``m_size`` is required for multi-phase " +"initialization." +msgstr "" + +#: ../Doc/c-api/module.rst:176 +msgid "See :PEP:`3121` for more details." +msgstr "" + +#: ../Doc/c-api/module.rst:180 +msgid "" +"A pointer to a table of module-level functions, described by :c:type:" +"`PyMethodDef` values. Can be *NULL* if no functions are present." +msgstr "" + +#: ../Doc/c-api/module.rst:185 +msgid "" +"An array of slot definitions for multi-phase initialization, terminated by a " +"``{0, NULL}`` entry. When using single-phase initialization, *m_slots* must " +"be *NULL*." +msgstr "" + +#: ../Doc/c-api/module.rst:191 +msgid "" +"Prior to version 3.5, this member was always set to *NULL*, and was defined " +"as:" +msgstr "" + +#: ../Doc/c-api/module.rst:198 +msgid "" +"A traversal function to call during GC traversal of the module object, or " +"*NULL* if not needed." +msgstr "" + +#: ../Doc/c-api/module.rst:203 +msgid "" +"A clear function to call during GC clearing of the module object, or *NULL* " +"if not needed." +msgstr "" + +#: ../Doc/c-api/module.rst:208 +msgid "" +"A function to call during deallocation of the module object, or *NULL* if " +"not needed." +msgstr "" + +#: ../Doc/c-api/module.rst:212 +msgid "Single-phase initialization" +msgstr "" + +#: ../Doc/c-api/module.rst:214 +msgid "" +"The module initialization function may create and return the module object " +"directly. This is referred to as \"single-phase initialization\", and uses " +"one of the following two module creation functions:" +msgstr "" + +#: ../Doc/c-api/module.rst:220 +msgid "" +"Create a new module object, given the definition in *def*. This behaves " +"like :c:func:`PyModule_Create2` with *module_api_version* set to :const:" +"`PYTHON_API_VERSION`." +msgstr "" + +#: ../Doc/c-api/module.rst:227 +msgid "" +"Create a new module object, given the definition in *def*, assuming the API " +"version *module_api_version*. If that version does not match the version of " +"the running interpreter, a :exc:`RuntimeWarning` is emitted." +msgstr "" + +#: ../Doc/c-api/module.rst:233 +msgid "" +"Most uses of this function should be using :c:func:`PyModule_Create` " +"instead; only use this if you are sure you need it." +msgstr "" + +#: ../Doc/c-api/module.rst:236 +msgid "" +"Before it is returned from in the initialization function, the resulting " +"module object is typically populated using functions like :c:func:" +"`PyModule_AddObject`." +msgstr "" + +#: ../Doc/c-api/module.rst:242 +msgid "Multi-phase initialization" +msgstr "" + +#: ../Doc/c-api/module.rst:244 +msgid "" +"An alternate way to specify extensions is to request \"multi-phase " +"initialization\". Extension modules created this way behave more like Python " +"modules: the initialization is split between the *creation phase*, when the " +"module object is created, and the *execution phase*, when it is populated. " +"The distinction is similar to the :py:meth:`__new__` and :py:meth:`__init__` " +"methods of classes." +msgstr "" + +#: ../Doc/c-api/module.rst:251 +msgid "" +"Unlike modules created using single-phase initialization, these modules are " +"not singletons: if the *sys.modules* entry is removed and the module is re-" +"imported, a new module object is created, and the old module is subject to " +"normal garbage collection -- as with Python modules. By default, multiple " +"modules created from the same definition should be independent: changes to " +"one should not affect the others. This means that all state should be " +"specific to the module object (using e.g. using :c:func:" +"`PyModule_GetState`), or its contents (such as the module's :attr:`__dict__` " +"or individual classes created with :c:func:`PyType_FromSpec`)." +msgstr "" + +#: ../Doc/c-api/module.rst:261 +msgid "" +"All modules created using multi-phase initialization are expected to " +"support :ref:`sub-interpreters `. Making sure " +"multiple modules are independent is typically enough to achieve this." +msgstr "" + +#: ../Doc/c-api/module.rst:265 +msgid "" +"To request multi-phase initialization, the initialization function " +"(PyInit_modulename) returns a :c:type:`PyModuleDef` instance with non-empty :" +"c:member:`~PyModuleDef.m_slots`. Before it is returned, the ``PyModuleDef`` " +"instance must be initialized with the following function:" +msgstr "" + +#: ../Doc/c-api/module.rst:272 +msgid "" +"Ensures a module definition is a properly initialized Python object that " +"correctly reports its type and reference count." +msgstr "" + +#: ../Doc/c-api/module.rst:275 +msgid "Returns *def* cast to ``PyObject*``, or *NULL* if an error occurred." +msgstr "" + +#: ../Doc/c-api/module.rst:279 +msgid "" +"The *m_slots* member of the module definition must point to an array of " +"``PyModuleDef_Slot`` structures:" +msgstr "" + +#: ../Doc/c-api/module.rst:286 +msgid "A slot ID, chosen from the available values explained below." +msgstr "" + +#: ../Doc/c-api/module.rst:290 +msgid "Value of the slot, whose meaning depends on the slot ID." +msgstr "" + +#: ../Doc/c-api/module.rst:294 +msgid "The *m_slots* array must be terminated by a slot with id 0." +msgstr "" + +#: ../Doc/c-api/module.rst:296 +msgid "The available slot types are:" +msgstr "" + +#: ../Doc/c-api/module.rst:300 +msgid "" +"Specifies a function that is called to create the module object itself. The " +"*value* pointer of this slot must point to a function of the signature:" +msgstr "" + +#: ../Doc/c-api/module.rst:305 +msgid "" +"The function receives a :py:class:`~importlib.machinery.ModuleSpec` " +"instance, as defined in :PEP:`451`, and the module definition. It should " +"return a new module object, or set an error and return *NULL*." +msgstr "" + +#: ../Doc/c-api/module.rst:310 +msgid "" +"This function should be kept minimal. In particular, it should not call " +"arbitrary Python code, as trying to import the same module again may result " +"in an infinite loop." +msgstr "" + +#: ../Doc/c-api/module.rst:314 +msgid "" +"Multiple ``Py_mod_create`` slots may not be specified in one module " +"definition." +msgstr "" + +#: ../Doc/c-api/module.rst:317 +msgid "" +"If ``Py_mod_create`` is not specified, the import machinery will create a " +"normal module object using :c:func:`PyModule_New`. The name is taken from " +"*spec*, not the definition, to allow extension modules to dynamically adjust " +"to their place in the module hierarchy and be imported under different names " +"through symlinks, all while sharing a single module definition." +msgstr "" + +#: ../Doc/c-api/module.rst:323 +msgid "" +"There is no requirement for the returned object to be an instance of :c:type:" +"`PyModule_Type`. Any type can be used, as long as it supports setting and " +"getting import-related attributes. However, only ``PyModule_Type`` instances " +"may be returned if the ``PyModuleDef`` has non-*NULL* ``m_traverse``, " +"``m_clear``, ``m_free``; non-zero ``m_size``; or slots other than " +"``Py_mod_create``." +msgstr "" + +#: ../Doc/c-api/module.rst:332 +msgid "" +"Specifies a function that is called to *execute* the module. This is " +"equivalent to executing the code of a Python module: typically, this " +"function adds classes and constants to the module. The signature of the " +"function is:" +msgstr "" + +#: ../Doc/c-api/module.rst:339 +msgid "" +"If multiple ``Py_mod_exec`` slots are specified, they are processed in the " +"order they appear in the *m_slots* array." +msgstr "" + +#: ../Doc/c-api/module.rst:342 +msgid "See :PEP:`489` for more details on multi-phase initialization." +msgstr "" + +#: ../Doc/c-api/module.rst:345 +msgid "Low-level module creation functions" +msgstr "" + +#: ../Doc/c-api/module.rst:347 +msgid "" +"The following functions are called under the hood when using multi-phase " +"initialization. They can be used directly, for example when creating module " +"objects dynamically. Note that both ``PyModule_FromDefAndSpec`` and " +"``PyModule_ExecDef`` must be called to fully initialize a module." +msgstr "" + +#: ../Doc/c-api/module.rst:354 +msgid "" +"Create a new module object, given the definition in *module* and the " +"ModuleSpec *spec*. This behaves like :c:func:`PyModule_FromDefAndSpec2` " +"with *module_api_version* set to :const:`PYTHON_API_VERSION`." +msgstr "" + +#: ../Doc/c-api/module.rst:362 +msgid "" +"Create a new module object, given the definition in *module* and the " +"ModuleSpec *spec*, assuming the API version *module_api_version*. If that " +"version does not match the version of the running interpreter, a :exc:" +"`RuntimeWarning` is emitted." +msgstr "" + +#: ../Doc/c-api/module.rst:369 +msgid "" +"Most uses of this function should be using :c:func:`PyModule_FromDefAndSpec` " +"instead; only use this if you are sure you need it." +msgstr "" + +#: ../Doc/c-api/module.rst:376 +msgid "Process any execution slots (:c:data:`Py_mod_exec`) given in *def*." +msgstr "" + +#: ../Doc/c-api/module.rst:382 +msgid "" +"Set the docstring for *module* to *docstring*. This function is called " +"automatically when creating a module from ``PyModuleDef``, using either " +"``PyModule_Create`` or ``PyModule_FromDefAndSpec``." +msgstr "" + +#: ../Doc/c-api/module.rst:391 +msgid "" +"Add the functions from the *NULL* terminated *functions* array to *module*. " +"Refer to the :c:type:`PyMethodDef` documentation for details on individual " +"entries (due to the lack of a shared module namespace, module level " +"\"functions\" implemented in C typically receive the module as their first " +"parameter, making them similar to instance methods on Python classes). This " +"function is called automatically when creating a module from " +"``PyModuleDef``, using either ``PyModule_Create`` or " +"``PyModule_FromDefAndSpec``." +msgstr "" + +#: ../Doc/c-api/module.rst:403 +msgid "Support functions" +msgstr "" + +#: ../Doc/c-api/module.rst:405 +msgid "" +"The module initialization function (if using single phase initialization) or " +"a function called from a module execution slot (if using multi-phase " +"initialization), can use the following functions to help initialize the " +"module state:" +msgstr "" + +#: ../Doc/c-api/module.rst:412 +msgid "" +"Add an object to *module* as *name*. This is a convenience function which " +"can be used from the module's initialization function. This steals a " +"reference to *value*. Return ``-1`` on error, ``0`` on success." +msgstr "" + +#: ../Doc/c-api/module.rst:418 +msgid "" +"Add an integer constant to *module* as *name*. This convenience function " +"can be used from the module's initialization function. Return ``-1`` on " +"error, ``0`` on success." +msgstr "" + +#: ../Doc/c-api/module.rst:425 +msgid "" +"Add a string constant to *module* as *name*. This convenience function can " +"be used from the module's initialization function. The string *value* must " +"be *NULL*-terminated. Return ``-1`` on error, ``0`` on success." +msgstr "" + +#: ../Doc/c-api/module.rst:432 +msgid "" +"Add an int constant to *module*. The name and the value are taken from " +"*macro*. For example ``PyModule_AddIntMacro(module, AF_INET)`` adds the int " +"constant *AF_INET* with the value of *AF_INET* to *module*. Return ``-1`` on " +"error, ``0`` on success." +msgstr "" + +#: ../Doc/c-api/module.rst:440 +msgid "Add a string constant to *module*." +msgstr "" + +#: ../Doc/c-api/module.rst:444 +msgid "Module lookup" +msgstr "" + +#: ../Doc/c-api/module.rst:446 +msgid "" +"Single-phase initialization creates singleton modules that can be looked up " +"in the context of the current interpreter. This allows the module object to " +"be retrieved later with only a reference to the module definition." +msgstr "" + +#: ../Doc/c-api/module.rst:450 +msgid "" +"These functions will not work on modules created using multi-phase " +"initialization, since multiple such modules can be created from a single " +"definition." +msgstr "" + +#: ../Doc/c-api/module.rst:455 +msgid "" +"Returns the module object that was created from *def* for the current " +"interpreter. This method requires that the module object has been attached " +"to the interpreter state with :c:func:`PyState_AddModule` beforehand. In " +"case the corresponding module object is not found or has not been attached " +"to the interpreter state yet, it returns *NULL*." +msgstr "" + +#: ../Doc/c-api/module.rst:462 +msgid "" +"Attaches the module object passed to the function to the interpreter state. " +"This allows the module object to be accessible via :c:func:" +"`PyState_FindModule`." +msgstr "" + +#: ../Doc/c-api/module.rst:465 +msgid "Only effective on modules created using single-phase initialization." +msgstr "" + +#: ../Doc/c-api/module.rst:471 +msgid "" +"Removes the module object created from *def* from the interpreter state." +msgstr "" + +#: ../Doc/c-api/none.rst:6 +msgid "The None Object" +msgstr "" + +#: ../Doc/c-api/none.rst:10 +msgid "" +"Note that the :c:type:`PyTypeObject` for ``None`` is not directly exposed in " +"the Python/C API. Since ``None`` is a singleton, testing for object " +"identity (using ``==`` in C) is sufficient. There is no :c:func:" +"`PyNone_Check` function for the same reason." +msgstr "" + +#: ../Doc/c-api/none.rst:18 +msgid "" +"The Python ``None`` object, denoting lack of value. This object has no " +"methods. It needs to be treated just like any other object with respect to " +"reference counts." +msgstr "" + +#: ../Doc/c-api/none.rst:25 +msgid "" +"Properly handle returning :c:data:`Py_None` from within a C function (that " +"is, increment the reference count of None and return it.)" +msgstr "" + +#: ../Doc/c-api/number.rst:6 +msgid "Number Protocol" +msgstr "" + +#: ../Doc/c-api/number.rst:11 +msgid "" +"Returns ``1`` if the object *o* provides numeric protocols, and false " +"otherwise. This function always succeeds." +msgstr "" + +#: ../Doc/c-api/number.rst:17 +msgid "" +"Returns the result of adding *o1* and *o2*, or *NULL* on failure. This is " +"the equivalent of the Python expression ``o1 + o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:23 +msgid "" +"Returns the result of subtracting *o2* from *o1*, or *NULL* on failure. " +"This is the equivalent of the Python expression ``o1 - o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:29 +msgid "" +"Returns the result of multiplying *o1* and *o2*, or *NULL* on failure. This " +"is the equivalent of the Python expression ``o1 * o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:35 +msgid "" +"Returns the result of matrix multiplication on *o1* and *o2*, or *NULL* on " +"failure. This is the equivalent of the Python expression ``o1 @ o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:43 +msgid "" +"Return the floor of *o1* divided by *o2*, or *NULL* on failure. This is " +"equivalent to the \"classic\" division of integers." +msgstr "" + +#: ../Doc/c-api/number.rst:49 +msgid "" +"Return a reasonable approximation for the mathematical value of *o1* divided " +"by *o2*, or *NULL* on failure. The return value is \"approximate\" because " +"binary floating point numbers are approximate; it is not possible to " +"represent all real numbers in base two. This function can return a floating " +"point value when passed two integers." +msgstr "" + +#: ../Doc/c-api/number.rst:58 +msgid "" +"Returns the remainder of dividing *o1* by *o2*, or *NULL* on failure. This " +"is the equivalent of the Python expression ``o1 % o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:66 +msgid "" +"See the built-in function :func:`divmod`. Returns *NULL* on failure. This " +"is the equivalent of the Python expression ``divmod(o1, o2)``." +msgstr "" + +#: ../Doc/c-api/number.rst:74 +msgid "" +"See the built-in function :func:`pow`. Returns *NULL* on failure. This is " +"the equivalent of the Python expression ``pow(o1, o2, o3)``, where *o3* is " +"optional. If *o3* is to be ignored, pass :c:data:`Py_None` in its place " +"(passing *NULL* for *o3* would cause an illegal memory access)." +msgstr "" + +#: ../Doc/c-api/number.rst:82 +msgid "" +"Returns the negation of *o* on success, or *NULL* on failure. This is the " +"equivalent of the Python expression ``-o``." +msgstr "" + +#: ../Doc/c-api/number.rst:88 +msgid "" +"Returns *o* on success, or *NULL* on failure. This is the equivalent of the " +"Python expression ``+o``." +msgstr "" + +#: ../Doc/c-api/number.rst:96 +msgid "" +"Returns the absolute value of *o*, or *NULL* on failure. This is the " +"equivalent of the Python expression ``abs(o)``." +msgstr "" + +#: ../Doc/c-api/number.rst:102 +msgid "" +"Returns the bitwise negation of *o* on success, or *NULL* on failure. This " +"is the equivalent of the Python expression ``~o``." +msgstr "" + +#: ../Doc/c-api/number.rst:108 +msgid "" +"Returns the result of left shifting *o1* by *o2* on success, or *NULL* on " +"failure. This is the equivalent of the Python expression ``o1 << o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:114 +msgid "" +"Returns the result of right shifting *o1* by *o2* on success, or *NULL* on " +"failure. This is the equivalent of the Python expression ``o1 >> o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:120 +msgid "" +"Returns the \"bitwise and\" of *o1* and *o2* on success and *NULL* on " +"failure. This is the equivalent of the Python expression ``o1 & o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:126 +msgid "" +"Returns the \"bitwise exclusive or\" of *o1* by *o2* on success, or *NULL* " +"on failure. This is the equivalent of the Python expression ``o1 ^ o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:132 +msgid "" +"Returns the \"bitwise or\" of *o1* and *o2* on success, or *NULL* on " +"failure. This is the equivalent of the Python expression ``o1 | o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:138 +msgid "" +"Returns the result of adding *o1* and *o2*, or *NULL* on failure. The " +"operation is done *in-place* when *o1* supports it. This is the equivalent " +"of the Python statement ``o1 += o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:145 +msgid "" +"Returns the result of subtracting *o2* from *o1*, or *NULL* on failure. The " +"operation is done *in-place* when *o1* supports it. This is the equivalent " +"of the Python statement ``o1 -= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:152 +msgid "" +"Returns the result of multiplying *o1* and *o2*, or *NULL* on failure. The " +"operation is done *in-place* when *o1* supports it. This is the equivalent " +"of the Python statement ``o1 *= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:159 +msgid "" +"Returns the result of matrix multiplication on *o1* and *o2*, or *NULL* on " +"failure. The operation is done *in-place* when *o1* supports it. This is " +"the equivalent of the Python statement ``o1 @= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:168 +msgid "" +"Returns the mathematical floor of dividing *o1* by *o2*, or *NULL* on " +"failure. The operation is done *in-place* when *o1* supports it. This is " +"the equivalent of the Python statement ``o1 //= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:175 +msgid "" +"Return a reasonable approximation for the mathematical value of *o1* divided " +"by *o2*, or *NULL* on failure. The return value is \"approximate\" because " +"binary floating point numbers are approximate; it is not possible to " +"represent all real numbers in base two. This function can return a floating " +"point value when passed two integers. The operation is done *in-place* when " +"*o1* supports it." +msgstr "" + +#: ../Doc/c-api/number.rst:184 +msgid "" +"Returns the remainder of dividing *o1* by *o2*, or *NULL* on failure. The " +"operation is done *in-place* when *o1* supports it. This is the equivalent " +"of the Python statement ``o1 %= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:193 +msgid "" +"See the built-in function :func:`pow`. Returns *NULL* on failure. The " +"operation is done *in-place* when *o1* supports it. This is the equivalent " +"of the Python statement ``o1 **= o2`` when o3 is :c:data:`Py_None`, or an in-" +"place variant of ``pow(o1, o2, o3)`` otherwise. If *o3* is to be ignored, " +"pass :c:data:`Py_None` in its place (passing *NULL* for *o3* would cause an " +"illegal memory access)." +msgstr "" + +#: ../Doc/c-api/number.rst:202 +msgid "" +"Returns the result of left shifting *o1* by *o2* on success, or *NULL* on " +"failure. The operation is done *in-place* when *o1* supports it. This is " +"the equivalent of the Python statement ``o1 <<= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:209 +msgid "" +"Returns the result of right shifting *o1* by *o2* on success, or *NULL* on " +"failure. The operation is done *in-place* when *o1* supports it. This is " +"the equivalent of the Python statement ``o1 >>= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:216 +msgid "" +"Returns the \"bitwise and\" of *o1* and *o2* on success and *NULL* on " +"failure. The operation is done *in-place* when *o1* supports it. This is " +"the equivalent of the Python statement ``o1 &= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:223 +msgid "" +"Returns the \"bitwise exclusive or\" of *o1* by *o2* on success, or *NULL* " +"on failure. The operation is done *in-place* when *o1* supports it. This " +"is the equivalent of the Python statement ``o1 ^= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:230 +msgid "" +"Returns the \"bitwise or\" of *o1* and *o2* on success, or *NULL* on " +"failure. The operation is done *in-place* when *o1* supports it. This is " +"the equivalent of the Python statement ``o1 |= o2``." +msgstr "" + +#: ../Doc/c-api/number.rst:239 +msgid "" +"Returns the *o* converted to an integer object on success, or *NULL* on " +"failure. This is the equivalent of the Python expression ``int(o)``." +msgstr "" + +#: ../Doc/c-api/number.rst:247 +msgid "" +"Returns the *o* converted to a float object on success, or *NULL* on " +"failure. This is the equivalent of the Python expression ``float(o)``." +msgstr "" + +#: ../Doc/c-api/number.rst:253 +msgid "" +"Returns the *o* converted to a Python int on success or *NULL* with a :exc:" +"`TypeError` exception raised on failure." +msgstr "" + +#: ../Doc/c-api/number.rst:259 +msgid "" +"Returns the integer *n* converted to base *base* as a string. The *base* " +"argument must be one of 2, 8, 10, or 16. For base 2, 8, or 16, the returned " +"string is prefixed with a base marker of ``'0b'``, ``'0o'``, or ``'0x'``, " +"respectively. If *n* is not a Python int, it is converted with :c:func:" +"`PyNumber_Index` first." +msgstr "" + +#: ../Doc/c-api/number.rst:268 +msgid "" +"Returns *o* converted to a Py_ssize_t value if *o* can be interpreted as an " +"integer. If the call fails, an exception is raised and -1 is returned." +msgstr "" + +#: ../Doc/c-api/number.rst:271 +msgid "" +"If *o* can be converted to a Python int but the attempt to convert to a " +"Py_ssize_t value would raise an :exc:`OverflowError`, then the *exc* " +"argument is the type of exception that will be raised (usually :exc:" +"`IndexError` or :exc:`OverflowError`). If *exc* is *NULL*, then the " +"exception is cleared and the value is clipped to *PY_SSIZE_T_MIN* for a " +"negative integer or *PY_SSIZE_T_MAX* for a positive integer." +msgstr "" + +#: ../Doc/c-api/number.rst:281 +msgid "" +"Returns True if *o* is an index integer (has the nb_index slot of the " +"tp_as_number structure filled in)." +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:4 +msgid "Old Buffer Protocol" +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:8 +msgid "" +"These functions were part of the \"old buffer protocol\" API in Python 2. In " +"Python 3, this protocol doesn't exist anymore but the functions are still " +"exposed to ease porting 2.x code. They act as a compatibility wrapper " +"around the :ref:`new buffer protocol `, but they don't give " +"you control over the lifetime of the resources acquired when a buffer is " +"exported." +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:15 +msgid "" +"Therefore, it is recommended that you call :c:func:`PyObject_GetBuffer` (or " +"the ``y*`` or ``w*`` :ref:`format codes ` with the :c:func:" +"`PyArg_ParseTuple` family of functions) to get a buffer view over an object, " +"and :c:func:`PyBuffer_Release` when the buffer view can be released." +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:23 +msgid "" +"Returns a pointer to a read-only memory location usable as character-based " +"input. The *obj* argument must support the single-segment character buffer " +"interface. On success, returns ``0``, sets *buffer* to the memory location " +"and *buffer_len* to the buffer length. Returns ``-1`` and sets a :exc:" +"`TypeError` on error." +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:32 +msgid "" +"Returns a pointer to a read-only memory location containing arbitrary data. " +"The *obj* argument must support the single-segment readable buffer " +"interface. On success, returns ``0``, sets *buffer* to the memory location " +"and *buffer_len* to the buffer length. Returns ``-1`` and sets a :exc:" +"`TypeError` on error." +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:41 +msgid "" +"Returns ``1`` if *o* supports the single-segment readable buffer interface. " +"Otherwise returns ``0``." +msgstr "" + +#: ../Doc/c-api/objbuffer.rst:47 +msgid "" +"Returns a pointer to a writable memory location. The *obj* argument must " +"support the single-segment, character buffer interface. On success, returns " +"``0``, sets *buffer* to the memory location and *buffer_len* to the buffer " +"length. Returns ``-1`` and sets a :exc:`TypeError` on error." +msgstr "" + +#: ../Doc/c-api/object.rst:6 +msgid "Object Protocol" +msgstr "" + +#: ../Doc/c-api/object.rst:11 +msgid "" +"The ``NotImplemented`` singleton, used to signal that an operation is not " +"implemented for the given type combination." +msgstr "" + +#: ../Doc/c-api/object.rst:17 +msgid "" +"Properly handle returning :c:data:`Py_NotImplemented` from within a C " +"function (that is, increment the reference count of NotImplemented and " +"return it)." +msgstr "" + +#: ../Doc/c-api/object.rst:24 +msgid "" +"Print an object *o*, on file *fp*. Returns ``-1`` on error. The flags " +"argument is used to enable certain printing options. The only option " +"currently supported is :const:`Py_PRINT_RAW`; if given, the :func:`str` of " +"the object is written instead of the :func:`repr`." +msgstr "" + +#: ../Doc/c-api/object.rst:32 ../Doc/c-api/object.rst:39 +msgid "" +"Returns ``1`` if *o* has the attribute *attr_name*, and ``0`` otherwise. " +"This is equivalent to the Python expression ``hasattr(o, attr_name)``. This " +"function always succeeds." +msgstr "" + +#: ../Doc/c-api/object.rst:46 +msgid "" +"Retrieve an attribute named *attr_name* from object *o*. Returns the " +"attribute value on success, or *NULL* on failure. This is the equivalent of " +"the Python expression ``o.attr_name``." +msgstr "" + +#: ../Doc/c-api/object.rst:53 +msgid "" +"Retrieve an attribute named *attr_name* from object *o*. Returns the " +"attribute value on success, or *NULL* on failure. This is the equivalent of " +"the Python expression ``o.attr_name``." +msgstr "" + +#: ../Doc/c-api/object.rst:60 +msgid "" +"Generic attribute getter function that is meant to be put into a type " +"object's ``tp_getattro`` slot. It looks for a descriptor in the dictionary " +"of classes in the object's MRO as well as an attribute in the object's :attr:" +"`~object.__dict__` (if present). As outlined in :ref:`descriptors`, data " +"descriptors take preference over instance attributes, while non-data " +"descriptors don't. Otherwise, an :exc:`AttributeError` is raised." +msgstr "" + +#: ../Doc/c-api/object.rst:70 ../Doc/c-api/object.rst:81 +msgid "" +"Set the value of the attribute named *attr_name*, for object *o*, to the " +"value *v*. Raise an exception and return ``-1`` on failure; return ``0`` on " +"success. This is the equivalent of the Python statement ``o.attr_name = v``." +msgstr "" + +#: ../Doc/c-api/object.rst:75 +msgid "" +"If *v* is *NULL*, the attribute is deleted, however this feature is " +"deprecated in favour of using :c:func:`PyObject_DelAttr`." +msgstr "" + +#: ../Doc/c-api/object.rst:86 +msgid "" +"If *v* is *NULL*, the attribute is deleted, however this feature is " +"deprecated in favour of using :c:func:`PyObject_DelAttrString`." +msgstr "" + +#: ../Doc/c-api/object.rst:92 +msgid "" +"Generic attribute setter and deleter function that is meant to be put into a " +"type object's :c:member:`~PyTypeObject.tp_setattro` slot. It looks for a " +"data descriptor in the dictionary of classes in the object's MRO, and if " +"found it takes preference over setting or deleting the attribute in the " +"instance dictionary. Otherwise, the attribute is set or deleted in the " +"object's :attr:`~object.__dict__` (if present). On success, ``0`` is " +"returned, otherwise an :exc:`AttributeError` is raised and ``-1`` is " +"returned." +msgstr "" + +#: ../Doc/c-api/object.rst:104 ../Doc/c-api/object.rst:110 +msgid "" +"Delete attribute named *attr_name*, for object *o*. Returns ``-1`` on " +"failure. This is the equivalent of the Python statement ``del o.attr_name``." +msgstr "" + +#: ../Doc/c-api/object.rst:116 +msgid "" +"A generic implementation for the getter of a ``__dict__`` descriptor. It " +"creates the dictionary if necessary." +msgstr "" + +#: ../Doc/c-api/object.rst:124 +msgid "" +"A generic implementation for the setter of a ``__dict__`` descriptor. This " +"implementation does not allow the dictionary to be deleted." +msgstr "" + +#: ../Doc/c-api/object.rst:132 +msgid "" +"Compare the values of *o1* and *o2* using the operation specified by *opid*, " +"which must be one of :const:`Py_LT`, :const:`Py_LE`, :const:`Py_EQ`, :const:" +"`Py_NE`, :const:`Py_GT`, or :const:`Py_GE`, corresponding to ``<``, ``<=``, " +"``==``, ``!=``, ``>``, or ``>=`` respectively. This is the equivalent of the " +"Python expression ``o1 op o2``, where ``op`` is the operator corresponding " +"to *opid*. Returns the value of the comparison on success, or *NULL* on " +"failure." +msgstr "" + +#: ../Doc/c-api/object.rst:142 +msgid "" +"Compare the values of *o1* and *o2* using the operation specified by *opid*, " +"which must be one of :const:`Py_LT`, :const:`Py_LE`, :const:`Py_EQ`, :const:" +"`Py_NE`, :const:`Py_GT`, or :const:`Py_GE`, corresponding to ``<``, ``<=``, " +"``==``, ``!=``, ``>``, or ``>=`` respectively. Returns ``-1`` on error, " +"``0`` if the result is false, ``1`` otherwise. This is the equivalent of the " +"Python expression ``o1 op o2``, where ``op`` is the operator corresponding " +"to *opid*." +msgstr "" + +#: ../Doc/c-api/object.rst:151 +msgid "" +"If *o1* and *o2* are the same object, :c:func:`PyObject_RichCompareBool` " +"will always return ``1`` for :const:`Py_EQ` and ``0`` for :const:`Py_NE`." +msgstr "" + +#: ../Doc/c-api/object.rst:158 +msgid "" +"Compute a string representation of object *o*. Returns the string " +"representation on success, *NULL* on failure. This is the equivalent of the " +"Python expression ``repr(o)``. Called by the :func:`repr` built-in function." +msgstr "" + +#: ../Doc/c-api/object.rst:162 ../Doc/c-api/object.rst:186 +#: ../Doc/c-api/veryhigh.rst:332 +msgid "" +"This function now includes a debug assertion to help ensure that it does not " +"silently discard an active exception." +msgstr "" + +#: ../Doc/c-api/object.rst:170 +msgid "" +"As :c:func:`PyObject_Repr`, compute a string representation of object *o*, " +"but escape the non-ASCII characters in the string returned by :c:func:" +"`PyObject_Repr` with ``\\x``, ``\\u`` or ``\\U`` escapes. This generates a " +"string similar to that returned by :c:func:`PyObject_Repr` in Python 2. " +"Called by the :func:`ascii` built-in function." +msgstr "" + +#: ../Doc/c-api/object.rst:181 +msgid "" +"Compute a string representation of object *o*. Returns the string " +"representation on success, *NULL* on failure. This is the equivalent of the " +"Python expression ``str(o)``. Called by the :func:`str` built-in function " +"and, therefore, by the :func:`print` function." +msgstr "" + +#: ../Doc/c-api/object.rst:194 +msgid "" +"Compute a bytes representation of object *o*. *NULL* is returned on failure " +"and a bytes object on success. This is equivalent to the Python expression " +"``bytes(o)``, when *o* is not an integer. Unlike ``bytes(o)``, a TypeError " +"is raised when *o* is an integer instead of a zero-initialized bytes object." +msgstr "" + +#: ../Doc/c-api/object.rst:203 +msgid "" +"Return ``1`` if the class *derived* is identical to or derived from the " +"class *cls*, otherwise return ``0``. In case of an error, return ``-1``." +msgstr "" + +#: ../Doc/c-api/object.rst:206 ../Doc/c-api/object.rst:225 +msgid "" +"If *cls* is a tuple, the check will be done against every entry in *cls*. " +"The result will be ``1`` when at least one of the checks returns ``1``, " +"otherwise it will be ``0``." +msgstr "" + +#: ../Doc/c-api/object.rst:210 +msgid "" +"If *cls* has a :meth:`~class.__subclasscheck__` method, it will be called to " +"determine the subclass status as described in :pep:`3119`. Otherwise, " +"*derived* is a subclass of *cls* if it is a direct or indirect subclass, i." +"e. contained in ``cls.__mro__``." +msgstr "" + +#: ../Doc/c-api/object.rst:215 +msgid "" +"Normally only class objects, i.e. instances of :class:`type` or a derived " +"class, are considered classes. However, objects can override this by having " +"a :attr:`__bases__` attribute (which must be a tuple of base classes)." +msgstr "" + +#: ../Doc/c-api/object.rst:222 +msgid "" +"Return ``1`` if *inst* is an instance of the class *cls* or a subclass of " +"*cls*, or ``0`` if not. On error, returns ``-1`` and sets an exception." +msgstr "" + +#: ../Doc/c-api/object.rst:229 +msgid "" +"If *cls* has a :meth:`~class.__instancecheck__` method, it will be called to " +"determine the subclass status as described in :pep:`3119`. Otherwise, " +"*inst* is an instance of *cls* if its class is a subclass of *cls*." +msgstr "" + +#: ../Doc/c-api/object.rst:233 +msgid "" +"An instance *inst* can override what is considered its class by having a :" +"attr:`__class__` attribute." +msgstr "" + +#: ../Doc/c-api/object.rst:236 +msgid "" +"An object *cls* can override if it is considered a class, and what its base " +"classes are, by having a :attr:`__bases__` attribute (which must be a tuple " +"of base classes)." +msgstr "" + +#: ../Doc/c-api/object.rst:243 +msgid "" +"Determine if the object *o* is callable. Return ``1`` if the object is " +"callable and ``0`` otherwise. This function always succeeds." +msgstr "" + +#: ../Doc/c-api/object.rst:249 +msgid "" +"Call a callable Python object *callable_object*, with arguments given by the " +"tuple *args*, and named arguments given by the dictionary *kw*. If no named " +"arguments are needed, *kw* may be *NULL*. *args* must not be *NULL*, use an " +"empty tuple if no arguments are needed. Returns the result of the call on " +"success, or *NULL* on failure. This is the equivalent of the Python " +"expression ``callable_object(*args, **kw)``." +msgstr "" + +#: ../Doc/c-api/object.rst:259 +msgid "" +"Call a callable Python object *callable_object*, with arguments given by the " +"tuple *args*. If no arguments are needed, then *args* may be *NULL*. " +"Returns the result of the call on success, or *NULL* on failure. This is " +"the equivalent of the Python expression ``callable_object(*args)``." +msgstr "" + +#: ../Doc/c-api/object.rst:267 +msgid "" +"Call a callable Python object *callable*, with a variable number of C " +"arguments. The C arguments are described using a :c:func:`Py_BuildValue` " +"style format string. The format may be *NULL*, indicating that no arguments " +"are provided. Returns the result of the call on success, or *NULL* on " +"failure. This is the equivalent of the Python expression " +"``callable(*args)``. Note that if you only pass :c:type:`PyObject \\*` " +"args, :c:func:`PyObject_CallFunctionObjArgs` is a faster alternative." +msgstr "" + +#: ../Doc/c-api/object.rst:275 +msgid "The type of *format* was changed from ``char *``." +msgstr "" + +#: ../Doc/c-api/object.rst:281 +msgid "" +"Call the method named *method* of object *o* with a variable number of C " +"arguments. The C arguments are described by a :c:func:`Py_BuildValue` " +"format string that should produce a tuple. The format may be *NULL*, " +"indicating that no arguments are provided. Returns the result of the call on " +"success, or *NULL* on failure. This is the equivalent of the Python " +"expression ``o.method(args)``. Note that if you only pass :c:type:`PyObject " +"\\*` args, :c:func:`PyObject_CallMethodObjArgs` is a faster alternative." +msgstr "" + +#: ../Doc/c-api/object.rst:289 +msgid "The types of *method* and *format* were changed from ``char *``." +msgstr "" + +#: ../Doc/c-api/object.rst:295 +msgid "" +"Call a callable Python object *callable*, with a variable number of :c:type:" +"`PyObject\\*` arguments. The arguments are provided as a variable number of " +"parameters followed by *NULL*. Returns the result of the call on success, or " +"*NULL* on failure." +msgstr "" + +#: ../Doc/c-api/object.rst:303 +msgid "" +"Calls a method of the object *o*, where the name of the method is given as a " +"Python string object in *name*. It is called with a variable number of :c:" +"type:`PyObject\\*` arguments. The arguments are provided as a variable " +"number of parameters followed by *NULL*. Returns the result of the call on " +"success, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/object.rst:314 +msgid "" +"Compute and return the hash value of an object *o*. On failure, return " +"``-1``. This is the equivalent of the Python expression ``hash(o)``." +msgstr "" + +#: ../Doc/c-api/object.rst:317 +msgid "" +"The return type is now Py_hash_t. This is a signed integer the same size as " +"Py_ssize_t." +msgstr "" + +#: ../Doc/c-api/object.rst:324 +msgid "" +"Set a :exc:`TypeError` indicating that ``type(o)`` is not hashable and " +"return ``-1``. This function receives special treatment when stored in a " +"``tp_hash`` slot, allowing a type to explicitly indicate to the interpreter " +"that it is not hashable." +msgstr "" + +#: ../Doc/c-api/object.rst:332 +msgid "" +"Returns ``1`` if the object *o* is considered to be true, and ``0`` " +"otherwise. This is equivalent to the Python expression ``not not o``. On " +"failure, return ``-1``." +msgstr "" + +#: ../Doc/c-api/object.rst:339 +msgid "" +"Returns ``0`` if the object *o* is considered to be true, and ``1`` " +"otherwise. This is equivalent to the Python expression ``not o``. On " +"failure, return ``-1``." +msgstr "" + +#: ../Doc/c-api/object.rst:348 +msgid "" +"When *o* is non-*NULL*, returns a type object corresponding to the object " +"type of object *o*. On failure, raises :exc:`SystemError` and returns " +"*NULL*. This is equivalent to the Python expression ``type(o)``. This " +"function increments the reference count of the return value. There's really " +"no reason to use this function instead of the common expression ``o-" +">ob_type``, which returns a pointer of type :c:type:`PyTypeObject\\*`, " +"except when the incremented reference count is needed." +msgstr "" + +#: ../Doc/c-api/object.rst:359 +msgid "" +"Return true if the object *o* is of type *type* or a subtype of *type*. " +"Both parameters must be non-*NULL*." +msgstr "" + +#: ../Doc/c-api/object.rst:368 +msgid "" +"Return the length of object *o*. If the object *o* provides either the " +"sequence and mapping protocols, the sequence length is returned. On error, " +"``-1`` is returned. This is the equivalent to the Python expression " +"``len(o)``." +msgstr "" + +#: ../Doc/c-api/object.rst:375 +msgid "" +"Return an estimated length for the object *o*. First try to return its " +"actual length, then an estimate using :meth:`~object.__length_hint__`, and " +"finally return the default value. On error return ``-1``. This is the " +"equivalent to the Python expression ``operator.length_hint(o, default)``." +msgstr "" + +#: ../Doc/c-api/object.rst:391 +msgid "" +"Map the object *key* to the value *v*. Raise an exception and return ``-1`` " +"on failure; return ``0`` on success. This is the equivalent of the Python " +"statement ``o[key] = v``." +msgstr "" + +#: ../Doc/c-api/object.rst:398 +msgid "" +"Delete the mapping for *key* from *o*. Returns ``-1`` on failure. This is " +"the equivalent of the Python statement ``del o[key]``." +msgstr "" + +#: ../Doc/c-api/object.rst:404 +msgid "" +"This is equivalent to the Python expression ``dir(o)``, returning a " +"(possibly empty) list of strings appropriate for the object argument, or " +"*NULL* if there was an error. If the argument is *NULL*, this is like the " +"Python ``dir()``, returning the names of the current locals; in this case, " +"if no execution frame is active then *NULL* is returned but :c:func:" +"`PyErr_Occurred` will return false." +msgstr "" + +#: ../Doc/c-api/object.rst:413 +msgid "" +"This is equivalent to the Python expression ``iter(o)``. It returns a new " +"iterator for the object argument, or the object itself if the object is " +"already an iterator. Raises :exc:`TypeError` and returns *NULL* if the " +"object cannot be iterated." +msgstr "" + +#: ../Doc/c-api/objimpl.rst:7 +msgid "Object Implementation Support" +msgstr "" + +#: ../Doc/c-api/objimpl.rst:9 +msgid "" +"This chapter describes the functions, types, and macros used when defining " +"new object types." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:8 +msgid "Reference Counting" +msgstr "" + +#: ../Doc/c-api/refcounting.rst:10 +msgid "" +"The macros in this section are used for managing reference counts of Python " +"objects." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:16 +msgid "" +"Increment the reference count for object *o*. The object must not be " +"*NULL*; if you aren't sure that it isn't *NULL*, use :c:func:`Py_XINCREF`." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:22 +msgid "" +"Increment the reference count for object *o*. The object may be *NULL*, in " +"which case the macro has no effect." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:28 +msgid "" +"Decrement the reference count for object *o*. The object must not be " +"*NULL*; if you aren't sure that it isn't *NULL*, use :c:func:`Py_XDECREF`. " +"If the reference count reaches zero, the object's type's deallocation " +"function (which must not be *NULL*) is invoked." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:35 +msgid "" +"The deallocation function can cause arbitrary Python code to be invoked (e." +"g. when a class instance with a :meth:`__del__` method is deallocated). " +"While exceptions in such code are not propagated, the executed code has free " +"access to all Python global variables. This means that any object that is " +"reachable from a global variable should be in a consistent state before :c:" +"func:`Py_DECREF` is invoked. For example, code to delete an object from a " +"list should copy a reference to the deleted object in a temporary variable, " +"update the list data structure, and then call :c:func:`Py_DECREF` for the " +"temporary variable." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:47 +msgid "" +"Decrement the reference count for object *o*. The object may be *NULL*, in " +"which case the macro has no effect; otherwise the effect is the same as for :" +"c:func:`Py_DECREF`, and the same warning applies." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:54 +msgid "" +"Decrement the reference count for object *o*. The object may be *NULL*, in " +"which case the macro has no effect; otherwise the effect is the same as for :" +"c:func:`Py_DECREF`, except that the argument is also set to *NULL*. The " +"warning for :c:func:`Py_DECREF` does not apply with respect to the object " +"passed because the macro carefully uses a temporary variable and sets the " +"argument to *NULL* before decrementing its reference count." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:61 +msgid "" +"It is a good idea to use this macro whenever decrementing the value of a " +"variable that might be traversed during garbage collection." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:65 +msgid "" +"The following functions are for runtime dynamic embedding of Python: " +"``Py_IncRef(PyObject *o)``, ``Py_DecRef(PyObject *o)``. They are simply " +"exported function versions of :c:func:`Py_XINCREF` and :c:func:`Py_XDECREF`, " +"respectively." +msgstr "" + +#: ../Doc/c-api/refcounting.rst:70 +msgid "" +"The following functions or macros are only for use within the interpreter " +"core: :c:func:`_Py_Dealloc`, :c:func:`_Py_ForgetReference`, :c:func:" +"`_Py_NewReference`, as well as the global variable :c:data:`_Py_RefTotal`." +msgstr "" + +#: ../Doc/c-api/reflection.rst:6 +msgid "Reflection" +msgstr "" + +#: ../Doc/c-api/reflection.rst:10 +msgid "" +"Return a dictionary of the builtins in the current execution frame, or the " +"interpreter of the thread state if no frame is currently executing." +msgstr "" + +#: ../Doc/c-api/reflection.rst:16 +msgid "" +"Return a dictionary of the local variables in the current execution frame, " +"or *NULL* if no frame is currently executing." +msgstr "" + +#: ../Doc/c-api/reflection.rst:22 +msgid "" +"Return a dictionary of the global variables in the current execution frame, " +"or *NULL* if no frame is currently executing." +msgstr "" + +#: ../Doc/c-api/reflection.rst:28 +msgid "" +"Return the current thread state's frame, which is *NULL* if no frame is " +"currently executing." +msgstr "" + +#: ../Doc/c-api/reflection.rst:34 +msgid "Return the line number that *frame* is currently executing." +msgstr "" + +#: ../Doc/c-api/reflection.rst:39 +msgid "" +"Return the name of *func* if it is a function, class or instance object, " +"else the name of *func*\\s type." +msgstr "" + +#: ../Doc/c-api/reflection.rst:45 +msgid "" +"Return a description string, depending on the type of *func*. Return values " +"include \"()\" for functions and methods, \" constructor\", \" instance\", " +"and \" object\". Concatenated with the result of :c:func:" +"`PyEval_GetFuncName`, the result will be a description of *func*." +msgstr "" + +#: ../Doc/c-api/sequence.rst:6 +msgid "Sequence Protocol" +msgstr "" + +#: ../Doc/c-api/sequence.rst:11 +msgid "" +"Return ``1`` if the object provides sequence protocol, and ``0`` otherwise. " +"This function always succeeds." +msgstr "" + +#: ../Doc/c-api/sequence.rst:20 +msgid "" +"Returns the number of objects in sequence *o* on success, and ``-1`` on " +"failure. For objects that do not provide sequence protocol, this is " +"equivalent to the Python expression ``len(o)``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:27 +msgid "" +"Return the concatenation of *o1* and *o2* on success, and *NULL* on failure. " +"This is the equivalent of the Python expression ``o1 + o2``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:33 +msgid "" +"Return the result of repeating sequence object *o* *count* times, or *NULL* " +"on failure. This is the equivalent of the Python expression ``o * count``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:39 +msgid "" +"Return the concatenation of *o1* and *o2* on success, and *NULL* on failure. " +"The operation is done *in-place* when *o1* supports it. This is the " +"equivalent of the Python expression ``o1 += o2``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:46 +msgid "" +"Return the result of repeating sequence object *o* *count* times, or *NULL* " +"on failure. The operation is done *in-place* when *o* supports it. This is " +"the equivalent of the Python expression ``o *= count``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:53 +msgid "" +"Return the *i*\\ th element of *o*, or *NULL* on failure. This is the " +"equivalent of the Python expression ``o[i]``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:59 +msgid "" +"Return the slice of sequence object *o* between *i1* and *i2*, or *NULL* on " +"failure. This is the equivalent of the Python expression ``o[i1:i2]``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:65 +msgid "" +"Assign object *v* to the *i*\\ th element of *o*. Raise an exception and " +"return ``-1`` on failure; return ``0`` on success. This is the equivalent " +"of the Python statement ``o[i] = v``. This function *does not* steal a " +"reference to *v*." +msgstr "" + +#: ../Doc/c-api/sequence.rst:70 +msgid "" +"If *v* is *NULL*, the element is deleted, however this feature is deprecated " +"in favour of using :c:func:`PySequence_DelItem`." +msgstr "" + +#: ../Doc/c-api/sequence.rst:76 +msgid "" +"Delete the *i*\\ th element of object *o*. Returns ``-1`` on failure. This " +"is the equivalent of the Python statement ``del o[i]``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:82 +msgid "" +"Assign the sequence object *v* to the slice in sequence object *o* from *i1* " +"to *i2*. This is the equivalent of the Python statement ``o[i1:i2] = v``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:88 +msgid "" +"Delete the slice in sequence object *o* from *i1* to *i2*. Returns ``-1`` " +"on failure. This is the equivalent of the Python statement ``del o[i1:i2]``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:94 +msgid "" +"Return the number of occurrences of *value* in *o*, that is, return the " +"number of keys for which ``o[key] == value``. On failure, return ``-1``. " +"This is equivalent to the Python expression ``o.count(value)``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:101 +msgid "" +"Determine if *o* contains *value*. If an item in *o* is equal to *value*, " +"return ``1``, otherwise return ``0``. On error, return ``-1``. This is " +"equivalent to the Python expression ``value in o``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:108 +msgid "" +"Return the first index *i* for which ``o[i] == value``. On error, return " +"``-1``. This is equivalent to the Python expression ``o.index(value)``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:114 +msgid "" +"Return a list object with the same contents as the sequence or iterable *o*, " +"or *NULL* on failure. The returned list is guaranteed to be new. This is " +"equivalent to the Python expression ``list(o)``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:123 +msgid "" +"Return a tuple object with the same contents as the arbitrary sequence *o* " +"or *NULL* on failure. If *o* is a tuple, a new reference will be returned, " +"otherwise a tuple will be constructed with the appropriate contents. This " +"is equivalent to the Python expression ``tuple(o)``." +msgstr "" + +#: ../Doc/c-api/sequence.rst:131 +msgid "" +"Return the sequence *o* as a list, unless it is already a tuple or list, in " +"which case *o* is returned. Use :c:func:`PySequence_Fast_GET_ITEM` to " +"access the members of the result. Returns *NULL* on failure. If the object " +"is not a sequence, raises :exc:`TypeError` with *m* as the message text." +msgstr "" + +#: ../Doc/c-api/sequence.rst:139 +msgid "" +"Return the *i*\\ th element of *o*, assuming that *o* was returned by :c:" +"func:`PySequence_Fast`, *o* is not *NULL*, and that *i* is within bounds." +msgstr "" + +#: ../Doc/c-api/sequence.rst:145 +msgid "" +"Return the underlying array of PyObject pointers. Assumes that *o* was " +"returned by :c:func:`PySequence_Fast` and *o* is not *NULL*." +msgstr "" + +#: ../Doc/c-api/sequence.rst:148 +msgid "" +"Note, if a list gets resized, the reallocation may relocate the items array. " +"So, only use the underlying array pointer in contexts where the sequence " +"cannot change." +msgstr "" + +#: ../Doc/c-api/sequence.rst:155 +msgid "" +"Return the *i*\\ th element of *o* or *NULL* on failure. Macro form of :c:" +"func:`PySequence_GetItem` but without checking that :c:func:" +"`PySequence_Check` on *o* is true and without adjustment for negative " +"indices." +msgstr "" + +#: ../Doc/c-api/sequence.rst:163 +msgid "" +"Returns the length of *o*, assuming that *o* was returned by :c:func:" +"`PySequence_Fast` and that *o* is not *NULL*. The size can also be gotten " +"by calling :c:func:`PySequence_Size` on *o*, but :c:func:" +"`PySequence_Fast_GET_SIZE` is faster because it can assume *o* is a list or " +"tuple." +msgstr "" + +#: ../Doc/c-api/set.rst:6 +msgid "Set Objects" +msgstr "" + +#: ../Doc/c-api/set.rst:15 +msgid "" +"This section details the public API for :class:`set` and :class:`frozenset` " +"objects. Any functionality not listed below is best accessed using the " +"either the abstract object protocol (including :c:func:" +"`PyObject_CallMethod`, :c:func:`PyObject_RichCompareBool`, :c:func:" +"`PyObject_Hash`, :c:func:`PyObject_Repr`, :c:func:`PyObject_IsTrue`, :c:func:" +"`PyObject_Print`, and :c:func:`PyObject_GetIter`) or the abstract number " +"protocol (including :c:func:`PyNumber_And`, :c:func:`PyNumber_Subtract`, :c:" +"func:`PyNumber_Or`, :c:func:`PyNumber_Xor`, :c:func:`PyNumber_InPlaceAnd`, :" +"c:func:`PyNumber_InPlaceSubtract`, :c:func:`PyNumber_InPlaceOr`, and :c:func:" +"`PyNumber_InPlaceXor`)." +msgstr "" + +#: ../Doc/c-api/set.rst:29 +msgid "" +"This subtype of :c:type:`PyObject` is used to hold the internal data for " +"both :class:`set` and :class:`frozenset` objects. It is like a :c:type:" +"`PyDictObject` in that it is a fixed size for small sets (much like tuple " +"storage) and will point to a separate, variable sized block of memory for " +"medium and large sized sets (much like list storage). None of the fields of " +"this structure should be considered public and are subject to change. All " +"access should be done through the documented API rather than by manipulating " +"the values in the structure." +msgstr "" + +#: ../Doc/c-api/set.rst:40 +msgid "" +"This is an instance of :c:type:`PyTypeObject` representing the Python :class:" +"`set` type." +msgstr "" + +#: ../Doc/c-api/set.rst:46 +msgid "" +"This is an instance of :c:type:`PyTypeObject` representing the Python :class:" +"`frozenset` type." +msgstr "" + +#: ../Doc/c-api/set.rst:49 +msgid "" +"The following type check macros work on pointers to any Python object. " +"Likewise, the constructor functions work with any iterable Python object." +msgstr "" + +#: ../Doc/c-api/set.rst:55 +msgid "" +"Return true if *p* is a :class:`set` object or an instance of a subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:59 +msgid "" +"Return true if *p* is a :class:`frozenset` object or an instance of a " +"subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:64 +msgid "" +"Return true if *p* is a :class:`set` object, a :class:`frozenset` object, or " +"an instance of a subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:70 +msgid "" +"Return true if *p* is a :class:`set` object or a :class:`frozenset` object " +"but not an instance of a subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:76 +msgid "" +"Return true if *p* is a :class:`frozenset` object but not an instance of a " +"subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:82 +msgid "" +"Return a new :class:`set` containing objects returned by the *iterable*. " +"The *iterable* may be *NULL* to create a new empty set. Return the new set " +"on success or *NULL* on failure. Raise :exc:`TypeError` if *iterable* is " +"not actually iterable. The constructor is also useful for copying a set " +"(``c=set(s)``)." +msgstr "" + +#: ../Doc/c-api/set.rst:91 +msgid "" +"Return a new :class:`frozenset` containing objects returned by the " +"*iterable*. The *iterable* may be *NULL* to create a new empty frozenset. " +"Return the new set on success or *NULL* on failure. Raise :exc:`TypeError` " +"if *iterable* is not actually iterable." +msgstr "" + +#: ../Doc/c-api/set.rst:97 +msgid "" +"The following functions and macros are available for instances of :class:" +"`set` or :class:`frozenset` or instances of their subtypes." +msgstr "" + +#: ../Doc/c-api/set.rst:105 +msgid "" +"Return the length of a :class:`set` or :class:`frozenset` object. Equivalent " +"to ``len(anyset)``. Raises a :exc:`PyExc_SystemError` if *anyset* is not a :" +"class:`set`, :class:`frozenset`, or an instance of a subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:112 +msgid "Macro form of :c:func:`PySet_Size` without error checking." +msgstr "" + +#: ../Doc/c-api/set.rst:117 +msgid "" +"Return 1 if found, 0 if not found, and -1 if an error is encountered. " +"Unlike the Python :meth:`__contains__` method, this function does not " +"automatically convert unhashable sets into temporary frozensets. Raise a :" +"exc:`TypeError` if the *key* is unhashable. Raise :exc:`PyExc_SystemError` " +"if *anyset* is not a :class:`set`, :class:`frozenset`, or an instance of a " +"subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:126 +msgid "" +"Add *key* to a :class:`set` instance. Also works with :class:`frozenset` " +"instances (like :c:func:`PyTuple_SetItem` it can be used to fill-in the " +"values of brand new frozensets before they are exposed to other code). " +"Return 0 on success or -1 on failure. Raise a :exc:`TypeError` if the *key* " +"is unhashable. Raise a :exc:`MemoryError` if there is no room to grow. " +"Raise a :exc:`SystemError` if *set* is not an instance of :class:`set` or " +"its subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:135 +msgid "" +"The following functions are available for instances of :class:`set` or its " +"subtypes but not for instances of :class:`frozenset` or its subtypes." +msgstr "" + +#: ../Doc/c-api/set.rst:141 +msgid "" +"Return 1 if found and removed, 0 if not found (no action taken), and -1 if " +"an error is encountered. Does not raise :exc:`KeyError` for missing keys. " +"Raise a :exc:`TypeError` if the *key* is unhashable. Unlike the Python :" +"meth:`~set.discard` method, this function does not automatically convert " +"unhashable sets into temporary frozensets. Raise :exc:`PyExc_SystemError` if " +"*set* is not an instance of :class:`set` or its subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:151 +msgid "" +"Return a new reference to an arbitrary object in the *set*, and removes the " +"object from the *set*. Return *NULL* on failure. Raise :exc:`KeyError` if " +"the set is empty. Raise a :exc:`SystemError` if *set* is not an instance of :" +"class:`set` or its subtype." +msgstr "" + +#: ../Doc/c-api/set.rst:159 +msgid "Empty an existing set of all elements." +msgstr "" + +#: ../Doc/c-api/slice.rst:6 +msgid "Slice Objects" +msgstr "" + +#: ../Doc/c-api/slice.rst:11 +msgid "" +"The type object for slice objects. This is the same as :class:`slice` in " +"the Python layer." +msgstr "" + +#: ../Doc/c-api/slice.rst:17 +msgid "Return true if *ob* is a slice object; *ob* must not be *NULL*." +msgstr "" + +#: ../Doc/c-api/slice.rst:22 +msgid "" +"Return a new slice object with the given values. The *start*, *stop*, and " +"*step* parameters are used as the values of the slice object attributes of " +"the same names. Any of the values may be *NULL*, in which case the ``None`` " +"will be used for the corresponding attribute. Return *NULL* if the new " +"object could not be allocated." +msgstr "" + +#: ../Doc/c-api/slice.rst:31 +msgid "" +"Retrieve the start, stop and step indices from the slice object *slice*, " +"assuming a sequence of length *length*. Treats indices greater than *length* " +"as errors." +msgstr "" + +#: ../Doc/c-api/slice.rst:35 +msgid "" +"Returns 0 on success and -1 on error with no exception set (unless one of " +"the indices was not :const:`None` and failed to be converted to an integer, " +"in which case -1 is returned with an exception set)." +msgstr "" + +#: ../Doc/c-api/slice.rst:39 +msgid "You probably do not want to use this function." +msgstr "" + +#: ../Doc/c-api/slice.rst:41 ../Doc/c-api/slice.rst:56 +msgid "" +"The parameter type for the *slice* parameter was ``PySliceObject*`` before." +msgstr "" + +#: ../Doc/c-api/slice.rst:48 +msgid "" +"Usable replacement for :c:func:`PySlice_GetIndices`. Retrieve the start, " +"stop, and step indices from the slice object *slice* assuming a sequence of " +"length *length*, and store the length of the slice in *slicelength*. Out of " +"bounds indices are clipped in a manner consistent with the handling of " +"normal slices." +msgstr "" + +#: ../Doc/c-api/slice.rst:54 +msgid "Returns 0 on success and -1 on error with exception set." +msgstr "" + +#: ../Doc/c-api/stable.rst:7 +msgid "Stable Application Binary Interface" +msgstr "" + +#: ../Doc/c-api/stable.rst:9 +msgid "" +"Traditionally, the C API of Python will change with every release. Most " +"changes will be source-compatible, typically by only adding API, rather than " +"changing existing API or removing API (although some interfaces do get " +"removed after being deprecated first)." +msgstr "" + +#: ../Doc/c-api/stable.rst:14 +msgid "" +"Unfortunately, the API compatibility does not extend to binary compatibility " +"(the ABI). The reason is primarily the evolution of struct definitions, " +"where addition of a new field, or changing the type of a field, might not " +"break the API, but can break the ABI. As a consequence, extension modules " +"need to be recompiled for every Python release (although an exception is " +"possible on Unix when none of the affected interfaces are used). In " +"addition, on Windows, extension modules link with a specific pythonXY.dll " +"and need to be recompiled to link with a newer one." +msgstr "" + +#: ../Doc/c-api/stable.rst:23 +msgid "" +"Since Python 3.2, a subset of the API has been declared to guarantee a " +"stable ABI. Extension modules wishing to use this API (called \"limited API" +"\") need to define ``Py_LIMITED_API``. A number of interpreter details then " +"become hidden from the extension module; in return, a module is built that " +"works on any 3.x version (x>=2) without recompilation." +msgstr "" + +#: ../Doc/c-api/stable.rst:29 +msgid "" +"In some cases, the stable ABI needs to be extended with new functions. " +"Extension modules wishing to use these new APIs need to set " +"``Py_LIMITED_API`` to the ``PY_VERSION_HEX`` value (see :ref:" +"`apiabiversion`) of the minimum Python version they want to support (e.g. " +"``0x03030000`` for Python 3.3). Such modules will work on all subsequent " +"Python releases, but fail to load (because of missing symbols) on the older " +"releases." +msgstr "" + +#: ../Doc/c-api/stable.rst:36 +msgid "" +"As of Python 3.2, the set of functions available to the limited API is " +"documented in :pep:`384`. In the C API documentation, API elements that are " +"not part of the limited API are marked as \"Not part of the limited API.\"" +msgstr "" + +#: ../Doc/c-api/structures.rst:6 +msgid "Common Object Structures" +msgstr "" + +#: ../Doc/c-api/structures.rst:8 +msgid "" +"There are a large number of structures which are used in the definition of " +"object types for Python. This section describes these structures and how " +"they are used." +msgstr "" + +#: ../Doc/c-api/structures.rst:12 +msgid "" +"All Python objects ultimately share a small number of fields at the " +"beginning of the object's representation in memory. These are represented " +"by the :c:type:`PyObject` and :c:type:`PyVarObject` types, which are " +"defined, in turn, by the expansions of some macros also used, whether " +"directly or indirectly, in the definition of all other Python objects." +msgstr "" + +#: ../Doc/c-api/structures.rst:21 +msgid "" +"All object types are extensions of this type. This is a type which contains " +"the information Python needs to treat a pointer to an object as an object. " +"In a normal \"release\" build, it contains only the object's reference count " +"and a pointer to the corresponding type object. Nothing is actually declared " +"to be a :c:type:`PyObject`, but every pointer to a Python object can be cast " +"to a :c:type:`PyObject*`. Access to the members must be done by using the " +"macros :c:macro:`Py_REFCNT` and :c:macro:`Py_TYPE`." +msgstr "" + +#: ../Doc/c-api/structures.rst:33 +msgid "" +"This is an extension of :c:type:`PyObject` that adds the :attr:`ob_size` " +"field. This is only used for objects that have some notion of *length*. " +"This type does not often appear in the Python/C API. Access to the members " +"must be done by using the macros :c:macro:`Py_REFCNT`, :c:macro:`Py_TYPE`, " +"and :c:macro:`Py_SIZE`." +msgstr "" + +#: ../Doc/c-api/structures.rst:42 +msgid "" +"This is a macro used when declaring new types which represent objects " +"without a varying length. The PyObject_HEAD macro expands to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:47 +msgid "See documentation of :c:type:`PyObject` above." +msgstr "" + +#: ../Doc/c-api/structures.rst:52 +msgid "" +"This is a macro used when declaring new types which represent objects with a " +"length that varies from instance to instance. The PyObject_VAR_HEAD macro " +"expands to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:58 +msgid "See documentation of :c:type:`PyVarObject` above." +msgstr "" + +#: ../Doc/c-api/structures.rst:63 +msgid "" +"This macro is used to access the :attr:`ob_type` member of a Python object. " +"It expands to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:71 +msgid "" +"This macro is used to access the :attr:`ob_refcnt` member of a Python " +"object. It expands to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:80 +msgid "" +"This macro is used to access the :attr:`ob_size` member of a Python object. " +"It expands to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:88 +msgid "" +"This is a macro which expands to initialization values for a new :c:type:" +"`PyObject` type. This macro expands to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:97 +msgid "" +"This is a macro which expands to initialization values for a new :c:type:" +"`PyVarObject` type, including the :attr:`ob_size` field. This macro expands " +"to::" +msgstr "" + +#: ../Doc/c-api/structures.rst:107 +msgid "" +"Type of the functions used to implement most Python callables in C. " +"Functions of this type take two :c:type:`PyObject\\*` parameters and return " +"one such value. If the return value is *NULL*, an exception shall have been " +"set. If not *NULL*, the return value is interpreted as the return value of " +"the function as exposed in Python. The function must return a new reference." +msgstr "" + +#: ../Doc/c-api/structures.rst:117 +msgid "" +"Type of the functions used to implement Python callables in C that take " +"keyword arguments: they take three :c:type:`PyObject\\*` parameters and " +"return one such value. See :c:type:`PyCFunction` above for the meaning of " +"the return value." +msgstr "" + +#: ../Doc/c-api/structures.rst:125 +msgid "" +"Structure used to describe a method of an extension type. This structure " +"has four fields:" +msgstr "" + +#: ../Doc/c-api/structures.rst:129 ../Doc/c-api/structures.rst:241 +#: ../Doc/c-api/tuple.rst:145 ../Doc/c-api/tuple.rst:168 +msgid "C Type" +msgstr "" + +#: ../Doc/c-api/structures.rst:131 +msgid ":attr:`ml_name`" +msgstr "" + +#: ../Doc/c-api/structures.rst:131 ../Doc/c-api/structures.rst:139 +#: ../Doc/c-api/structures.rst:243 ../Doc/c-api/structures.rst:256 +#: ../Doc/c-api/structures.rst:272 +msgid "char \\*" +msgstr "" + +#: ../Doc/c-api/structures.rst:131 +msgid "name of the method" +msgstr "" + +#: ../Doc/c-api/structures.rst:133 +msgid ":attr:`ml_meth`" +msgstr "" + +#: ../Doc/c-api/structures.rst:133 +msgid "PyCFunction" +msgstr "" + +#: ../Doc/c-api/structures.rst:133 +msgid "pointer to the C implementation" +msgstr "" + +#: ../Doc/c-api/structures.rst:136 +msgid ":attr:`ml_flags`" +msgstr "" + +#: ../Doc/c-api/structures.rst:136 +msgid "flag bits indicating how the call should be constructed" +msgstr "" + +#: ../Doc/c-api/structures.rst:139 +msgid ":attr:`ml_doc`" +msgstr "" + +#: ../Doc/c-api/structures.rst:139 ../Doc/c-api/structures.rst:256 +msgid "points to the contents of the docstring" +msgstr "" + +#: ../Doc/c-api/structures.rst:143 +msgid "" +"The :attr:`ml_meth` is a C function pointer. The functions may be of " +"different types, but they always return :c:type:`PyObject\\*`. If the " +"function is not of the :c:type:`PyCFunction`, the compiler will require a " +"cast in the method table. Even though :c:type:`PyCFunction` defines the " +"first parameter as :c:type:`PyObject\\*`, it is common that the method " +"implementation uses the specific C type of the *self* object." +msgstr "" + +#: ../Doc/c-api/structures.rst:150 +msgid "" +"The :attr:`ml_flags` field is a bitfield which can include the following " +"flags. The individual flags indicate either a calling convention or a " +"binding convention. Of the calling convention flags, only :const:" +"`METH_VARARGS` and :const:`METH_KEYWORDS` can be combined (but note that :" +"const:`METH_KEYWORDS` alone is equivalent to ``METH_VARARGS | " +"METH_KEYWORDS``). Any of the calling convention flags can be combined with a " +"binding flag." +msgstr "" + +#: ../Doc/c-api/structures.rst:160 +msgid "" +"This is the typical calling convention, where the methods have the type :c:" +"type:`PyCFunction`. The function expects two :c:type:`PyObject\\*` values. " +"The first one is the *self* object for methods; for module functions, it is " +"the module object. The second parameter (often called *args*) is a tuple " +"object representing all arguments. This parameter is typically processed " +"using :c:func:`PyArg_ParseTuple` or :c:func:`PyArg_UnpackTuple`." +msgstr "" + +#: ../Doc/c-api/structures.rst:170 +msgid "" +"Methods with these flags must be of type :c:type:`PyCFunctionWithKeywords`. " +"The function expects three parameters: *self*, *args*, and a dictionary of " +"all the keyword arguments. The flag is typically combined with :const:" +"`METH_VARARGS`, and the parameters are typically processed using :c:func:" +"`PyArg_ParseTupleAndKeywords`." +msgstr "" + +#: ../Doc/c-api/structures.rst:179 +msgid "" +"Methods without parameters don't need to check whether arguments are given " +"if they are listed with the :const:`METH_NOARGS` flag. They need to be of " +"type :c:type:`PyCFunction`. The first parameter is typically named *self* " +"and will hold a reference to the module or object instance. In all cases " +"the second parameter will be *NULL*." +msgstr "" + +#: ../Doc/c-api/structures.rst:188 +msgid "" +"Methods with a single object argument can be listed with the :const:`METH_O` " +"flag, instead of invoking :c:func:`PyArg_ParseTuple` with a ``\"O\"`` " +"argument. They have the type :c:type:`PyCFunction`, with the *self* " +"parameter, and a :c:type:`PyObject\\*` parameter representing the single " +"argument." +msgstr "" + +#: ../Doc/c-api/structures.rst:194 +msgid "" +"These two constants are not used to indicate the calling convention but the " +"binding when use with methods of classes. These may not be used for " +"functions defined for modules. At most one of these flags may be set for " +"any given method." +msgstr "" + +#: ../Doc/c-api/structures.rst:204 +msgid "" +"The method will be passed the type object as the first parameter rather than " +"an instance of the type. This is used to create *class methods*, similar to " +"what is created when using the :func:`classmethod` built-in function." +msgstr "" + +#: ../Doc/c-api/structures.rst:214 +msgid "" +"The method will be passed *NULL* as the first parameter rather than an " +"instance of the type. This is used to create *static methods*, similar to " +"what is created when using the :func:`staticmethod` built-in function." +msgstr "" + +#: ../Doc/c-api/structures.rst:218 +msgid "" +"One other constant controls whether a method is loaded in place of another " +"definition with the same method name." +msgstr "" + +#: ../Doc/c-api/structures.rst:224 +msgid "" +"The method will be loaded in place of existing definitions. Without " +"*METH_COEXIST*, the default is to skip repeated definitions. Since slot " +"wrappers are loaded before the method table, the existence of a " +"*sq_contains* slot, for example, would generate a wrapped method named :meth:" +"`__contains__` and preclude the loading of a corresponding PyCFunction with " +"the same name. With the flag defined, the PyCFunction will be loaded in " +"place of the wrapper object and will co-exist with the slot. This is " +"helpful because calls to PyCFunctions are optimized more than wrapper object " +"calls." +msgstr "" + +#: ../Doc/c-api/structures.rst:237 +msgid "" +"Structure which describes an attribute of a type which corresponds to a C " +"struct member. Its fields are:" +msgstr "" + +#: ../Doc/c-api/structures.rst:243 +msgid ":attr:`name`" +msgstr "" + +#: ../Doc/c-api/structures.rst:243 +msgid "name of the member" +msgstr "" + +#: ../Doc/c-api/structures.rst:245 +msgid ":attr:`type`" +msgstr "" + +#: ../Doc/c-api/structures.rst:245 +msgid "the type of the member in the C struct" +msgstr "" + +#: ../Doc/c-api/structures.rst:248 +msgid ":attr:`offset`" +msgstr "" + +#: ../Doc/c-api/structures.rst:248 +msgid "" +"the offset in bytes that the member is located on the type's object struct" +msgstr "" + +#: ../Doc/c-api/structures.rst:252 +msgid ":attr:`flags`" +msgstr "" + +#: ../Doc/c-api/structures.rst:252 +msgid "flag bits indicating if the field should be read-only or writable" +msgstr "" + +#: ../Doc/c-api/structures.rst:256 +msgid ":attr:`doc`" +msgstr "" + +#: ../Doc/c-api/structures.rst:260 +msgid "" +":attr:`type` can be one of many ``T_`` macros corresponding to various C " +"types. When the member is accessed in Python, it will be converted to the " +"equivalent Python type." +msgstr "" + +#: ../Doc/c-api/structures.rst:265 +msgid "Macro name" +msgstr "" + +#: ../Doc/c-api/structures.rst:265 +msgid "C type" +msgstr "" + +#: ../Doc/c-api/structures.rst:267 +msgid "T_SHORT" +msgstr "" + +#: ../Doc/c-api/structures.rst:267 +msgid "short" +msgstr "" + +#: ../Doc/c-api/structures.rst:268 +msgid "T_INT" +msgstr "" + +#: ../Doc/c-api/structures.rst:269 +msgid "T_LONG" +msgstr "" + +#: ../Doc/c-api/structures.rst:270 +msgid "T_FLOAT" +msgstr "" + +#: ../Doc/c-api/structures.rst:270 +msgid "float" +msgstr "" + +#: ../Doc/c-api/structures.rst:271 +msgid "T_DOUBLE" +msgstr "" + +#: ../Doc/c-api/structures.rst:271 +msgid "double" +msgstr "" + +#: ../Doc/c-api/structures.rst:272 +msgid "T_STRING" +msgstr "" + +#: ../Doc/c-api/structures.rst:273 +msgid "T_OBJECT" +msgstr "" + +#: ../Doc/c-api/structures.rst:273 ../Doc/c-api/structures.rst:274 +msgid "PyObject \\*" +msgstr "" + +#: ../Doc/c-api/structures.rst:274 +msgid "T_OBJECT_EX" +msgstr "" + +#: ../Doc/c-api/structures.rst:275 +msgid "T_CHAR" +msgstr "" + +#: ../Doc/c-api/structures.rst:275 ../Doc/c-api/structures.rst:276 +#: ../Doc/c-api/structures.rst:281 +msgid "char" +msgstr "" + +#: ../Doc/c-api/structures.rst:276 +msgid "T_BYTE" +msgstr "" + +#: ../Doc/c-api/structures.rst:277 +msgid "T_UBYTE" +msgstr "" + +#: ../Doc/c-api/structures.rst:277 +msgid "unsigned char" +msgstr "" + +#: ../Doc/c-api/structures.rst:278 +msgid "T_UINT" +msgstr "" + +#: ../Doc/c-api/structures.rst:279 +msgid "T_USHORT" +msgstr "" + +#: ../Doc/c-api/structures.rst:279 +msgid "unsigned short" +msgstr "" + +#: ../Doc/c-api/structures.rst:280 +msgid "T_ULONG" +msgstr "" + +#: ../Doc/c-api/structures.rst:281 +msgid "T_BOOL" +msgstr "" + +#: ../Doc/c-api/structures.rst:282 +msgid "T_LONGLONG" +msgstr "" + +#: ../Doc/c-api/structures.rst:282 ../Doc/c-api/unicode.rst:469 +#: ../Doc/c-api/unicode.rst:472 +msgid "long long" +msgstr "" + +#: ../Doc/c-api/structures.rst:283 +msgid "T_ULONGLONG" +msgstr "" + +#: ../Doc/c-api/structures.rst:283 ../Doc/c-api/unicode.rst:475 +msgid "unsigned long long" +msgstr "" + +#: ../Doc/c-api/structures.rst:284 +msgid "T_PYSSIZET" +msgstr "" + +#: ../Doc/c-api/structures.rst:287 +msgid "" +":c:macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` differ in that :c:macro:" +"`T_OBJECT` returns ``None`` if the member is *NULL* and :c:macro:" +"`T_OBJECT_EX` raises an :exc:`AttributeError`. Try to use :c:macro:" +"`T_OBJECT_EX` over :c:macro:`T_OBJECT` because :c:macro:`T_OBJECT_EX` " +"handles use of the :keyword:`del` statement on that attribute more correctly " +"than :c:macro:`T_OBJECT`." +msgstr "" + +#: ../Doc/c-api/structures.rst:294 +msgid "" +":attr:`flags` can be 0 for write and read access or :c:macro:`READONLY` for " +"read-only access. Using :c:macro:`T_STRING` for :attr:`type` implies :c:" +"macro:`READONLY`. Only :c:macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` " +"members can be deleted. (They are set to *NULL*)." +msgstr "" + +#: ../Doc/c-api/sys.rst:6 +msgid "Operating System Utilities" +msgstr "" + +#: ../Doc/c-api/sys.rst:10 +msgid "" +"Return the file system representation for *path*. If the object is a :class:" +"`str` or :class:`bytes` object, then its reference count is incremented. If " +"the object implements the :class:`os.PathLike` interface, then :meth:`~os." +"PathLike.__fspath__` is returned as long as it is a :class:`str` or :class:" +"`bytes` object. Otherwise :exc:`TypeError` is raised and ``NULL`` is " +"returned." +msgstr "" + +#: ../Doc/c-api/sys.rst:22 +msgid "" +"Return true (nonzero) if the standard I/O file *fp* with name *filename* is " +"deemed interactive. This is the case for files for which " +"``isatty(fileno(fp))`` is true. If the global flag :c:data:" +"`Py_InteractiveFlag` is true, this function also returns true if the " +"*filename* pointer is *NULL* or if the name is equal to one of the strings " +"``''`` or ``'???'``." +msgstr "" + +#: ../Doc/c-api/sys.rst:31 +msgid "" +"Function to update some internal state after a process fork; this should be " +"called in the new process if the Python interpreter will continue to be " +"used. If a new executable is loaded into the new process, this function does " +"not need to be called." +msgstr "" + +#: ../Doc/c-api/sys.rst:39 +msgid "" +"Return true when the interpreter runs out of stack space. This is a " +"reliable check, but is only available when :const:`USE_STACKCHECK` is " +"defined (currently on Windows using the Microsoft Visual C++ compiler). :" +"const:`USE_STACKCHECK` will be defined automatically; you should never " +"change the definition in your own code." +msgstr "" + +#: ../Doc/c-api/sys.rst:48 +msgid "" +"Return the current signal handler for signal *i*. This is a thin wrapper " +"around either :c:func:`sigaction` or :c:func:`signal`. Do not call those " +"functions directly! :c:type:`PyOS_sighandler_t` is a typedef alias for :c:" +"type:`void (\\*)(int)`." +msgstr "" + +#: ../Doc/c-api/sys.rst:56 +msgid "" +"Set the signal handler for signal *i* to be *h*; return the old signal " +"handler. This is a thin wrapper around either :c:func:`sigaction` or :c:func:" +"`signal`. Do not call those functions directly! :c:type:" +"`PyOS_sighandler_t` is a typedef alias for :c:type:`void (\\*)(int)`." +msgstr "" + +#: ../Doc/c-api/sys.rst:63 +msgid "" +"Decode a byte string from the locale encoding with the :ref:`surrogateescape " +"error handler `: undecodable bytes are decoded as " +"characters in range U+DC80..U+DCFF. If a byte sequence can be decoded as a " +"surrogate character, escape the bytes using the surrogateescape error " +"handler instead of decoding them." +msgstr "" + +#: ../Doc/c-api/sys.rst:69 +msgid "" +"Return a pointer to a newly allocated wide character string, use :c:func:" +"`PyMem_RawFree` to free the memory. If size is not ``NULL``, write the " +"number of wide characters excluding the null character into ``*size``" +msgstr "" + +#: ../Doc/c-api/sys.rst:73 +msgid "" +"Return ``NULL`` on decoding error or memory allocation error. If *size* is " +"not ``NULL``, ``*size`` is set to ``(size_t)-1`` on memory error or set to " +"``(size_t)-2`` on decoding error." +msgstr "" + +#: ../Doc/c-api/sys.rst:77 +msgid "" +"Decoding errors should never happen, unless there is a bug in the C library." +msgstr "" + +#: ../Doc/c-api/sys.rst:80 +msgid "" +"Use the :c:func:`Py_EncodeLocale` function to encode the character string " +"back to a byte string." +msgstr "" + +#: ../Doc/c-api/sys.rst:85 +msgid "" +"The :c:func:`PyUnicode_DecodeFSDefaultAndSize` and :c:func:" +"`PyUnicode_DecodeLocaleAndSize` functions." +msgstr "" + +#: ../Doc/c-api/sys.rst:93 +msgid "" +"Encode a wide character string to the locale encoding with the :ref:" +"`surrogateescape error handler `: surrogate characters in " +"the range U+DC80..U+DCFF are converted to bytes 0x80..0xFF." +msgstr "" + +#: ../Doc/c-api/sys.rst:97 +msgid "" +"Return a pointer to a newly allocated byte string, use :c:func:`PyMem_Free` " +"to free the memory. Return ``NULL`` on encoding error or memory allocation " +"error" +msgstr "" + +#: ../Doc/c-api/sys.rst:101 +msgid "" +"If error_pos is not ``NULL``, ``*error_pos`` is set to the index of the " +"invalid character on encoding error, or set to ``(size_t)-1`` otherwise." +msgstr "" + +#: ../Doc/c-api/sys.rst:104 +msgid "" +"Use the :c:func:`Py_DecodeLocale` function to decode the bytes string back " +"to a wide character string." +msgstr "" + +#: ../Doc/c-api/sys.rst:109 +msgid "" +"The :c:func:`PyUnicode_EncodeFSDefault` and :c:func:`PyUnicode_EncodeLocale` " +"functions." +msgstr "" + +#: ../Doc/c-api/sys.rst:118 +msgid "System Functions" +msgstr "" + +#: ../Doc/c-api/sys.rst:120 +msgid "" +"These are utility functions that make functionality from the :mod:`sys` " +"module accessible to C code. They all work with the current interpreter " +"thread's :mod:`sys` module's dict, which is contained in the internal thread " +"state structure." +msgstr "" + +#: ../Doc/c-api/sys.rst:126 +msgid "" +"Return the object *name* from the :mod:`sys` module or *NULL* if it does not " +"exist, without setting an exception." +msgstr "" + +#: ../Doc/c-api/sys.rst:131 +msgid "" +"Set *name* in the :mod:`sys` module to *v* unless *v* is *NULL*, in which " +"case *name* is deleted from the sys module. Returns ``0`` on success, ``-1`` " +"on error." +msgstr "" + +#: ../Doc/c-api/sys.rst:137 +msgid "Reset :data:`sys.warnoptions` to an empty list." +msgstr "" + +#: ../Doc/c-api/sys.rst:141 +msgid "Append *s* to :data:`sys.warnoptions`." +msgstr "" + +#: ../Doc/c-api/sys.rst:145 +msgid "Append *unicode* to :data:`sys.warnoptions`." +msgstr "" + +#: ../Doc/c-api/sys.rst:149 +msgid "" +"Set :data:`sys.path` to a list object of paths found in *path* which should " +"be a list of paths separated with the platform's search path delimiter (``:" +"`` on Unix, ``;`` on Windows)." +msgstr "" + +#: ../Doc/c-api/sys.rst:155 +msgid "" +"Write the output string described by *format* to :data:`sys.stdout`. No " +"exceptions are raised, even if truncation occurs (see below)." +msgstr "" + +#: ../Doc/c-api/sys.rst:158 +msgid "" +"*format* should limit the total size of the formatted output string to 1000 " +"bytes or less -- after 1000 bytes, the output string is truncated. In " +"particular, this means that no unrestricted \"%s\" formats should occur; " +"these should be limited using \"%.s\" where is a decimal number " +"calculated so that plus the maximum size of other formatted text does " +"not exceed 1000 bytes. Also watch out for \"%f\", which can print hundreds " +"of digits for very large numbers." +msgstr "" + +#: ../Doc/c-api/sys.rst:166 +msgid "" +"If a problem occurs, or :data:`sys.stdout` is unset, the formatted message " +"is written to the real (C level) *stdout*." +msgstr "" + +#: ../Doc/c-api/sys.rst:171 +msgid "" +"As :c:func:`PySys_WriteStdout`, but write to :data:`sys.stderr` or *stderr* " +"instead." +msgstr "" + +#: ../Doc/c-api/sys.rst:176 +msgid "" +"Function similar to PySys_WriteStdout() but format the message using :c:func:" +"`PyUnicode_FromFormatV` and don't truncate the message to an arbitrary " +"length." +msgstr "" + +#: ../Doc/c-api/sys.rst:184 +msgid "" +"As :c:func:`PySys_FormatStdout`, but write to :data:`sys.stderr` or *stderr* " +"instead." +msgstr "" + +#: ../Doc/c-api/sys.rst:191 +msgid "" +"Parse *s* as a set of :option:`-X` options and add them to the current " +"options mapping as returned by :c:func:`PySys_GetXOptions`." +msgstr "" + +#: ../Doc/c-api/sys.rst:198 +msgid "" +"Return the current dictionary of :option:`-X` options, similarly to :data:" +"`sys._xoptions`. On error, *NULL* is returned and an exception is set." +msgstr "" + +#: ../Doc/c-api/sys.rst:208 +msgid "Process Control" +msgstr "" + +#: ../Doc/c-api/sys.rst:215 +msgid "" +"Print a fatal error message and kill the process. No cleanup is performed. " +"This function should only be invoked when a condition is detected that would " +"make it dangerous to continue using the Python interpreter; e.g., when the " +"object administration appears to be corrupted. On Unix, the standard C " +"library function :c:func:`abort` is called which will attempt to produce a :" +"file:`core` file." +msgstr "" + +#: ../Doc/c-api/sys.rst:229 +msgid "" +"Exit the current process. This calls :c:func:`Py_FinalizeEx` and then calls " +"the standard C library function ``exit(status)``. If :c:func:" +"`Py_FinalizeEx` indicates an error, the exit status is set to 120." +msgstr "" + +#: ../Doc/c-api/sys.rst:233 +msgid "Errors from finalization no longer ignored." +msgstr "" + +#: ../Doc/c-api/sys.rst:243 +msgid "" +"Register a cleanup function to be called by :c:func:`Py_FinalizeEx`. The " +"cleanup function will be called with no arguments and should return no " +"value. At most 32 cleanup functions can be registered. When the " +"registration is successful, :c:func:`Py_AtExit` returns ``0``; on failure, " +"it returns ``-1``. The cleanup function registered last is called first. " +"Each cleanup function will be called at most once. Since Python's internal " +"finalization will have completed before the cleanup function, no Python APIs " +"should be called by *func*." +msgstr "" + +#: ../Doc/c-api/tuple.rst:6 +msgid "Tuple Objects" +msgstr "" + +#: ../Doc/c-api/tuple.rst:13 +msgid "This subtype of :c:type:`PyObject` represents a Python tuple object." +msgstr "" + +#: ../Doc/c-api/tuple.rst:18 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python tuple type; it " +"is the same object as :class:`tuple` in the Python layer." +msgstr "" + +#: ../Doc/c-api/tuple.rst:24 +msgid "" +"Return true if *p* is a tuple object or an instance of a subtype of the " +"tuple type." +msgstr "" + +#: ../Doc/c-api/tuple.rst:30 +msgid "" +"Return true if *p* is a tuple object, but not an instance of a subtype of " +"the tuple type." +msgstr "" + +#: ../Doc/c-api/tuple.rst:36 +msgid "Return a new tuple object of size *len*, or *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/tuple.rst:41 +msgid "" +"Return a new tuple object of size *n*, or *NULL* on failure. The tuple " +"values are initialized to the subsequent *n* C arguments pointing to Python " +"objects. ``PyTuple_Pack(2, a, b)`` is equivalent to " +"``Py_BuildValue(\"(OO)\", a, b)``." +msgstr "" + +#: ../Doc/c-api/tuple.rst:48 +msgid "Take a pointer to a tuple object, and return the size of that tuple." +msgstr "" + +#: ../Doc/c-api/tuple.rst:53 +msgid "" +"Return the size of the tuple *p*, which must be non-*NULL* and point to a " +"tuple; no error checking is performed." +msgstr "" + +#: ../Doc/c-api/tuple.rst:59 +msgid "" +"Return the object at position *pos* in the tuple pointed to by *p*. If " +"*pos* is out of bounds, return *NULL* and sets an :exc:`IndexError` " +"exception." +msgstr "" + +#: ../Doc/c-api/tuple.rst:65 +msgid "Like :c:func:`PyTuple_GetItem`, but does no checking of its arguments." +msgstr "" + +#: ../Doc/c-api/tuple.rst:70 +msgid "" +"Take a slice of the tuple pointed to by *p* from *low* to *high* and return " +"it as a new tuple." +msgstr "" + +#: ../Doc/c-api/tuple.rst:76 +msgid "" +"Insert a reference to object *o* at position *pos* of the tuple pointed to " +"by *p*. Return ``0`` on success." +msgstr "" + +#: ../Doc/c-api/tuple.rst:81 ../Doc/c-api/tuple.rst:91 +#: ../Doc/c-api/tuple.rst:209 ../Doc/c-api/tuple.rst:218 +msgid "This function \"steals\" a reference to *o*." +msgstr "" + +#: ../Doc/c-api/tuple.rst:86 +msgid "" +"Like :c:func:`PyTuple_SetItem`, but does no error checking, and should " +"*only* be used to fill in brand new tuples." +msgstr "" + +#: ../Doc/c-api/tuple.rst:96 +msgid "" +"Can be used to resize a tuple. *newsize* will be the new length of the " +"tuple. Because tuples are *supposed* to be immutable, this should only be " +"used if there is only one reference to the object. Do *not* use this if the " +"tuple may already be known to some other part of the code. The tuple will " +"always grow or shrink at the end. Think of this as destroying the old tuple " +"and creating a new one, only more efficiently. Returns ``0`` on success. " +"Client code should never assume that the resulting value of ``*p`` will be " +"the same as before calling this function. If the object referenced by ``*p`` " +"is replaced, the original ``*p`` is destroyed. On failure, returns ``-1`` " +"and sets ``*p`` to *NULL*, and raises :exc:`MemoryError` or :exc:" +"`SystemError`." +msgstr "" + +#: ../Doc/c-api/tuple.rst:114 +msgid "Struct Sequence Objects" +msgstr "" + +#: ../Doc/c-api/tuple.rst:116 +msgid "" +"Struct sequence objects are the C equivalent of :func:`~collections." +"namedtuple` objects, i.e. a sequence whose items can also be accessed " +"through attributes. To create a struct sequence, you first have to create a " +"specific struct sequence type." +msgstr "" + +#: ../Doc/c-api/tuple.rst:123 +msgid "" +"Create a new struct sequence type from the data in *desc*, described below. " +"Instances of the resulting type can be created with :c:func:" +"`PyStructSequence_New`." +msgstr "" + +#: ../Doc/c-api/tuple.rst:129 +msgid "Initializes a struct sequence type *type* from *desc* in place." +msgstr "" + +#: ../Doc/c-api/tuple.rst:134 +msgid "" +"The same as ``PyStructSequence_InitType``, but returns ``0`` on success and " +"``-1`` on failure." +msgstr "" + +#: ../Doc/c-api/tuple.rst:142 +msgid "Contains the meta information of a struct sequence type to create." +msgstr "" + +#: ../Doc/c-api/tuple.rst:147 ../Doc/c-api/tuple.rst:170 +msgid "``name``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:147 ../Doc/c-api/tuple.rst:149 +#: ../Doc/c-api/tuple.rst:170 ../Doc/c-api/tuple.rst:175 +msgid "``char *``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:147 +msgid "name of the struct sequence type" +msgstr "" + +#: ../Doc/c-api/tuple.rst:149 ../Doc/c-api/tuple.rst:175 +msgid "``doc``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:149 +msgid "pointer to docstring for the type or NULL to omit" +msgstr "" + +#: ../Doc/c-api/tuple.rst:152 +msgid "``fields``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:152 +msgid "``PyStructSequence_Field *``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:152 +msgid "pointer to *NULL*-terminated array with field names of the new type" +msgstr "" + +#: ../Doc/c-api/tuple.rst:155 +msgid "``n_in_sequence``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:155 +msgid "``int``" +msgstr "" + +#: ../Doc/c-api/tuple.rst:155 +msgid "number of fields visible to the Python side (if used as tuple)" +msgstr "" + +#: ../Doc/c-api/tuple.rst:162 +msgid "" +"Describes a field of a struct sequence. As a struct sequence is modeled as a " +"tuple, all fields are typed as :c:type:`PyObject\\*`. The index in the :" +"attr:`fields` array of the :c:type:`PyStructSequence_Desc` determines which " +"field of the struct sequence is described." +msgstr "" + +#: ../Doc/c-api/tuple.rst:170 +msgid "" +"name for the field or *NULL* to end the list of named fields, set to " +"PyStructSequence_UnnamedField to leave unnamed" +msgstr "" + +#: ../Doc/c-api/tuple.rst:175 +msgid "field docstring or *NULL* to omit" +msgstr "" + +#: ../Doc/c-api/tuple.rst:181 +msgid "Special value for a field name to leave it unnamed." +msgstr "" + +#: ../Doc/c-api/tuple.rst:186 +msgid "" +"Creates an instance of *type*, which must have been created with :c:func:" +"`PyStructSequence_NewType`." +msgstr "" + +#: ../Doc/c-api/tuple.rst:192 +msgid "" +"Return the object at position *pos* in the struct sequence pointed to by " +"*p*. No bounds checking is performed." +msgstr "" + +#: ../Doc/c-api/tuple.rst:198 +msgid "Macro equivalent of :c:func:`PyStructSequence_GetItem`." +msgstr "" + +#: ../Doc/c-api/tuple.rst:203 +msgid "" +"Sets the field at index *pos* of the struct sequence *p* to value *o*. " +"Like :c:func:`PyTuple_SET_ITEM`, this should only be used to fill in brand " +"new instances." +msgstr "" + +#: ../Doc/c-api/tuple.rst:214 +msgid "Macro equivalent of :c:func:`PyStructSequence_SetItem`." +msgstr "" + +#: ../Doc/c-api/type.rst:6 ../Doc/c-api/typeobj.rst:6 +msgid "Type Objects" +msgstr "" + +#: ../Doc/c-api/type.rst:13 +msgid "The C structure of the objects used to describe built-in types." +msgstr "" + +#: ../Doc/c-api/type.rst:18 +msgid "" +"This is the type object for type objects; it is the same object as :class:" +"`type` in the Python layer." +msgstr "" + +#: ../Doc/c-api/type.rst:24 +msgid "" +"Return true if the object *o* is a type object, including instances of types " +"derived from the standard type object. Return false in all other cases." +msgstr "" + +#: ../Doc/c-api/type.rst:30 +msgid "" +"Return true if the object *o* is a type object, but not a subtype of the " +"standard type object. Return false in all other cases." +msgstr "" + +#: ../Doc/c-api/type.rst:36 +msgid "Clear the internal lookup cache. Return the current version tag." +msgstr "" + +#: ../Doc/c-api/type.rst:40 +msgid "" +"Return the :c:member:`~PyTypeObject.tp_flags` member of *type*. This " +"function is primarily meant for use with `Py_LIMITED_API`; the individual " +"flag bits are guaranteed to be stable across Python releases, but access to :" +"c:member:`~PyTypeObject.tp_flags` itself is not part of the limited API." +msgstr "" + +#: ../Doc/c-api/type.rst:50 +msgid "" +"Invalidate the internal lookup cache for the type and all of its subtypes. " +"This function must be called after any manual modification of the attributes " +"or base classes of the type." +msgstr "" + +#: ../Doc/c-api/type.rst:57 +msgid "" +"Return true if the type object *o* sets the feature *feature*. Type " +"features are denoted by single bit flags." +msgstr "" + +#: ../Doc/c-api/type.rst:63 +msgid "" +"Return true if the type object includes support for the cycle detector; this " +"tests the type flag :const:`Py_TPFLAGS_HAVE_GC`." +msgstr "" + +#: ../Doc/c-api/type.rst:69 +msgid "Return true if *a* is a subtype of *b*." +msgstr "" + +#: ../Doc/c-api/type.rst:71 +msgid "" +"This function only checks for actual subtypes, which means that :meth:" +"`~class.__subclasscheck__` is not called on *b*. Call :c:func:" +"`PyObject_IsSubclass` to do the same check that :func:`issubclass` would do." +msgstr "" + +#: ../Doc/c-api/type.rst:79 +msgid "" +"Generic handler for the :c:member:`~PyTypeObject.tp_alloc` slot of a type " +"object. Use Python's default memory allocation mechanism to allocate a new " +"instance and initialize all its contents to *NULL*." +msgstr "" + +#: ../Doc/c-api/type.rst:85 +msgid "" +"Generic handler for the :c:member:`~PyTypeObject.tp_new` slot of a type " +"object. Create a new instance using the type's :c:member:`~PyTypeObject." +"tp_alloc` slot." +msgstr "" + +#: ../Doc/c-api/type.rst:90 +msgid "" +"Finalize a type object. This should be called on all type objects to finish " +"their initialization. This function is responsible for adding inherited " +"slots from a type's base class. Return ``0`` on success, or return ``-1`` " +"and sets an exception on error." +msgstr "" + +#: ../Doc/c-api/type.rst:97 +msgid "" +"Creates and returns a heap type object from the *spec* passed to the " +"function." +msgstr "" + +#: ../Doc/c-api/type.rst:101 +msgid "" +"Creates and returns a heap type object from the *spec*. In addition to that, " +"the created heap type contains all types contained by the *bases* tuple as " +"base types. This allows the caller to reference other heap types as base " +"types." +msgstr "" + +#: ../Doc/c-api/type.rst:109 +msgid "" +"Return the function pointer stored in the given slot. If the result is " +"*NULL*, this indicates that either the slot is *NULL*, or that the function " +"was called with invalid parameters. Callers will typically cast the result " +"pointer into the appropriate function type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:8 +msgid "" +"Perhaps one of the most important structures of the Python object system is " +"the structure that defines a new type: the :c:type:`PyTypeObject` " +"structure. Type objects can be handled using any of the :c:func:`PyObject_" +"\\*` or :c:func:`PyType_\\*` functions, but do not offer much that's " +"interesting to most Python applications. These objects are fundamental to " +"how objects behave, so they are very important to the interpreter itself and " +"to any extension module that implements new types." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:16 +msgid "" +"Type objects are fairly large compared to most of the standard types. The " +"reason for the size is that each type object stores a large number of " +"values, mostly C function pointers, each of which implements a small part of " +"the type's functionality. The fields of the type object are examined in " +"detail in this section. The fields will be described in the order in which " +"they occur in the structure." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:23 +msgid "" +"Typedefs: unaryfunc, binaryfunc, ternaryfunc, inquiry, intargfunc, " +"intintargfunc, intobjargproc, intintobjargproc, objobjargproc, destructor, " +"freefunc, printfunc, getattrfunc, getattrofunc, setattrfunc, setattrofunc, " +"reprfunc, hashfunc" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:28 +msgid "" +"The structure definition for :c:type:`PyTypeObject` can be found in :file:" +"`Include/object.h`. For convenience of reference, this repeats the " +"definition found there:" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:35 +msgid "" +"The type object structure extends the :c:type:`PyVarObject` structure. The :" +"attr:`ob_size` field is used for dynamic types (created by :func:" +"`type_new`, usually called from a class statement). Note that :c:data:" +"`PyType_Type` (the metatype) initializes :c:member:`~PyTypeObject." +"tp_itemsize`, which means that its instances (i.e. type objects) *must* have " +"the :attr:`ob_size` field." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:45 +msgid "" +"These fields are only present when the macro ``Py_TRACE_REFS`` is defined. " +"Their initialization to *NULL* is taken care of by the " +"``PyObject_HEAD_INIT`` macro. For statically allocated objects, these " +"fields always remain *NULL*. For dynamically allocated objects, these two " +"fields are used to link the object into a doubly-linked list of *all* live " +"objects on the heap. This could be used for various debugging purposes; " +"currently the only use is to print the objects that are still alive at the " +"end of a run when the environment variable :envvar:`PYTHONDUMPREFS` is set." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:54 +msgid "These fields are not inherited by subtypes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:59 +msgid "" +"This is the type object's reference count, initialized to ``1`` by the " +"``PyObject_HEAD_INIT`` macro. Note that for statically allocated type " +"objects, the type's instances (objects whose :attr:`ob_type` points back to " +"the type) do *not* count as references. But for dynamically allocated type " +"objects, the instances *do* count as references." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:65 ../Doc/c-api/typeobj.rst:94 +#: ../Doc/c-api/typeobj.rst:122 +msgid "This field is not inherited by subtypes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:70 +msgid "" +"This is the type's type, in other words its metatype. It is initialized by " +"the argument to the ``PyObject_HEAD_INIT`` macro, and its value should " +"normally be ``&PyType_Type``. However, for dynamically loadable extension " +"modules that must be usable on Windows (at least), the compiler complains " +"that this is not a valid initializer. Therefore, the convention is to pass " +"*NULL* to the ``PyObject_HEAD_INIT`` macro and to initialize this field " +"explicitly at the start of the module's initialization function, before " +"doing anything else. This is typically done like this::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:81 +msgid "" +"This should be done before any instances of the type are created. :c:func:" +"`PyType_Ready` checks if :attr:`ob_type` is *NULL*, and if so, initializes " +"it to the :attr:`ob_type` field of the base class. :c:func:`PyType_Ready` " +"will not change this field if it is non-zero." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:86 ../Doc/c-api/typeobj.rst:188 +#: ../Doc/c-api/typeobj.rst:253 ../Doc/c-api/typeobj.rst:320 +#: ../Doc/c-api/typeobj.rst:338 ../Doc/c-api/typeobj.rst:664 +#: ../Doc/c-api/typeobj.rst:681 ../Doc/c-api/typeobj.rst:776 +#: ../Doc/c-api/typeobj.rst:871 ../Doc/c-api/typeobj.rst:964 +#: ../Doc/c-api/typeobj.rst:1019 +msgid "This field is inherited by subtypes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:91 +msgid "" +"For statically allocated type objects, this should be initialized to zero. " +"For dynamically allocated type objects, this field has a special internal " +"meaning." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:99 +msgid "" +"Pointer to a NUL-terminated string containing the name of the type. For " +"types that are accessible as module globals, the string should be the full " +"module name, followed by a dot, followed by the type name; for built-in " +"types, it should be just the type name. If the module is a submodule of a " +"package, the full package name is part of the full module name. For " +"example, a type named :class:`T` defined in module :mod:`M` in subpackage :" +"mod:`Q` in package :mod:`P` should have the :c:member:`~PyTypeObject." +"tp_name` initializer ``\"P.Q.M.T\"``." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:107 +msgid "" +"For dynamically allocated type objects, this should just be the type name, " +"and the module name explicitly stored in the type dict as the value for key " +"``'__module__'``." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:111 +msgid "" +"For statically allocated type objects, the tp_name field should contain a " +"dot. Everything before the last dot is made accessible as the :attr:" +"`__module__` attribute, and everything after the last dot is made accessible " +"as the :attr:`~definition.__name__` attribute." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:116 +msgid "" +"If no dot is present, the entire :c:member:`~PyTypeObject.tp_name` field is " +"made accessible as the :attr:`~definition.__name__` attribute, and the :attr:" +"`__module__` attribute is undefined (unless explicitly set in the " +"dictionary, as explained above). This means your type will be impossible to " +"pickle. Additionally, it will not be listed in module documentations " +"created with pydoc." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:128 +msgid "" +"These fields allow calculating the size in bytes of instances of the type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:130 +msgid "" +"There are two kinds of types: types with fixed-length instances have a zero :" +"c:member:`~PyTypeObject.tp_itemsize` field, types with variable-length " +"instances have a non-zero :c:member:`~PyTypeObject.tp_itemsize` field. For " +"a type with fixed-length instances, all instances have the same size, given " +"in :c:member:`~PyTypeObject.tp_basicsize`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:135 +msgid "" +"For a type with variable-length instances, the instances must have an :attr:" +"`ob_size` field, and the instance size is :c:member:`~PyTypeObject." +"tp_basicsize` plus N times :c:member:`~PyTypeObject.tp_itemsize`, where N is " +"the \"length\" of the object. The value of N is typically stored in the " +"instance's :attr:`ob_size` field. There are exceptions: for example, ints " +"use a negative :attr:`ob_size` to indicate a negative number, and N is " +"``abs(ob_size)`` there. Also, the presence of an :attr:`ob_size` field in " +"the instance layout doesn't mean that the instance structure is variable-" +"length (for example, the structure for the list type has fixed-length " +"instances, yet those instances have a meaningful :attr:`ob_size` field)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:146 +msgid "" +"The basic size includes the fields in the instance declared by the macro :c:" +"macro:`PyObject_HEAD` or :c:macro:`PyObject_VAR_HEAD` (whichever is used to " +"declare the instance struct) and this in turn includes the :attr:`_ob_prev` " +"and :attr:`_ob_next` fields if they are present. This means that the only " +"correct way to get an initializer for the :c:member:`~PyTypeObject." +"tp_basicsize` is to use the ``sizeof`` operator on the struct used to " +"declare the instance layout. The basic size does not include the GC header " +"size." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:154 +msgid "" +"These fields are inherited separately by subtypes. If the base type has a " +"non-zero :c:member:`~PyTypeObject.tp_itemsize`, it is generally not safe to " +"set :c:member:`~PyTypeObject.tp_itemsize` to a different non-zero value in a " +"subtype (though this depends on the implementation of the base type)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:159 +msgid "" +"A note about alignment: if the variable items require a particular " +"alignment, this should be taken care of by the value of :c:member:" +"`~PyTypeObject.tp_basicsize`. Example: suppose a type implements an array " +"of ``double``. :c:member:`~PyTypeObject.tp_itemsize` is ``sizeof(double)``. " +"It is the programmer's responsibility that :c:member:`~PyTypeObject." +"tp_basicsize` is a multiple of ``sizeof(double)`` (assuming this is the " +"alignment requirement for ``double``)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:169 +msgid "" +"A pointer to the instance destructor function. This function must be " +"defined unless the type guarantees that its instances will never be " +"deallocated (as is the case for the singletons ``None`` and ``Ellipsis``)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:173 +msgid "" +"The destructor function is called by the :c:func:`Py_DECREF` and :c:func:" +"`Py_XDECREF` macros when the new reference count is zero. At this point, " +"the instance is still in existence, but there are no references to it. The " +"destructor function should free all references which the instance owns, free " +"all memory buffers owned by the instance (using the freeing function " +"corresponding to the allocation function used to allocate the buffer), and " +"finally (as its last action) call the type's :c:member:`~PyTypeObject." +"tp_free` function. If the type is not subtypable (doesn't have the :const:" +"`Py_TPFLAGS_BASETYPE` flag bit set), it is permissible to call the object " +"deallocator directly instead of via :c:member:`~PyTypeObject.tp_free`. The " +"object deallocator should be the one used to allocate the instance; this is " +"normally :c:func:`PyObject_Del` if the instance was allocated using :c:func:" +"`PyObject_New` or :c:func:`PyObject_VarNew`, or :c:func:`PyObject_GC_Del` if " +"the instance was allocated using :c:func:`PyObject_GC_New` or :c:func:" +"`PyObject_GC_NewVar`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:193 +msgid "Reserved slot, formerly used for print formatting in Python 2.x." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:198 +msgid "An optional pointer to the get-attribute-string function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:200 +msgid "" +"This field is deprecated. When it is defined, it should point to a function " +"that acts the same as the :c:member:`~PyTypeObject.tp_getattro` function, " +"but taking a C string instead of a Python string object to give the " +"attribute name. The signature is the same as for :c:func:" +"`PyObject_GetAttrString`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:205 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_getattro`: a subtype inherits both :c:member:`~PyTypeObject.tp_getattr` " +"and :c:member:`~PyTypeObject.tp_getattro` from its base type when the " +"subtype's :c:member:`~PyTypeObject.tp_getattr` and :c:member:`~PyTypeObject." +"tp_getattro` are both *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:212 ../Doc/c-api/typeobj.rst:356 +msgid "" +"An optional pointer to the function for setting and deleting attributes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:214 +msgid "" +"This field is deprecated. When it is defined, it should point to a function " +"that acts the same as the :c:member:`~PyTypeObject.tp_setattro` function, " +"but taking a C string instead of a Python string object to give the " +"attribute name. The signature is the same as for :c:func:" +"`PyObject_SetAttrString`, but setting *v* to *NULL* to delete an attribute " +"must be supported." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:220 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_setattro`: a subtype inherits both :c:member:`~PyTypeObject.tp_setattr` " +"and :c:member:`~PyTypeObject.tp_setattro` from its base type when the " +"subtype's :c:member:`~PyTypeObject.tp_setattr` and :c:member:`~PyTypeObject." +"tp_setattro` are both *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:227 +msgid "" +"Pointer to an additional structure that contains fields relevant only to " +"objects which implement :term:`awaitable` and :term:`asynchronous iterator` " +"protocols at the C-level. See :ref:`async-structs` for details." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:231 +msgid "Formerly known as ``tp_compare`` and ``tp_reserved``." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:239 +msgid "" +"An optional pointer to a function that implements the built-in function :" +"func:`repr`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:242 +msgid "" +"The signature is the same as for :c:func:`PyObject_Repr`; it must return a " +"string or a Unicode object. Ideally, this function should return a string " +"that, when passed to :func:`eval`, given a suitable environment, returns an " +"object with the same value. If this is not feasible, it should return a " +"string starting with ``'<'`` and ending with ``'>'`` from which both the " +"type and the value of the object can be deduced." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:249 +msgid "" +"When this field is not set, a string of the form ``<%s object at %p>`` is " +"returned, where ``%s`` is replaced by the type name, and ``%p`` by the " +"object's memory address." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:257 +msgid "" +"Pointer to an additional structure that contains fields relevant only to " +"objects which implement the number protocol. These fields are documented " +"in :ref:`number-structs`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:261 +msgid "" +"The :c:member:`~PyTypeObject.tp_as_number` field is not inherited, but the " +"contained fields are inherited individually." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:267 +msgid "" +"Pointer to an additional structure that contains fields relevant only to " +"objects which implement the sequence protocol. These fields are documented " +"in :ref:`sequence-structs`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:271 +msgid "" +"The :c:member:`~PyTypeObject.tp_as_sequence` field is not inherited, but the " +"contained fields are inherited individually." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:277 +msgid "" +"Pointer to an additional structure that contains fields relevant only to " +"objects which implement the mapping protocol. These fields are documented " +"in :ref:`mapping-structs`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:281 +msgid "" +"The :c:member:`~PyTypeObject.tp_as_mapping` field is not inherited, but the " +"contained fields are inherited individually." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:289 +msgid "" +"An optional pointer to a function that implements the built-in function :" +"func:`hash`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:292 +msgid "" +"The signature is the same as for :c:func:`PyObject_Hash`; it must return a " +"value of the type Py_hash_t. The value ``-1`` should not be returned as a " +"normal return value; when an error occurs during the computation of the hash " +"value, the function should set an exception and return ``-1``." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:297 +msgid "" +"This field can be set explicitly to :c:func:`PyObject_HashNotImplemented` to " +"block inheritance of the hash method from a parent type. This is interpreted " +"as the equivalent of ``__hash__ = None`` at the Python level, causing " +"``isinstance(o, collections.Hashable)`` to correctly return ``False``. Note " +"that the converse is also true - setting ``__hash__ = None`` on a class at " +"the Python level will result in the ``tp_hash`` slot being set to :c:func:" +"`PyObject_HashNotImplemented`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:305 +msgid "" +"When this field is not set, an attempt to take the hash of the object " +"raises :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:308 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_richcompare`: a subtype inherits both of :c:member:`~PyTypeObject." +"tp_richcompare` and :c:member:`~PyTypeObject.tp_hash`, when the subtype's :c:" +"member:`~PyTypeObject.tp_richcompare` and :c:member:`~PyTypeObject.tp_hash` " +"are both *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:316 +msgid "" +"An optional pointer to a function that implements calling the object. This " +"should be *NULL* if the object is not callable. The signature is the same " +"as for :c:func:`PyObject_Call`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:325 +msgid "" +"An optional pointer to a function that implements the built-in operation :" +"func:`str`. (Note that :class:`str` is a type now, and :func:`str` calls " +"the constructor for that type. This constructor calls :c:func:" +"`PyObject_Str` to do the actual work, and :c:func:`PyObject_Str` will call " +"this handler.)" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:330 +msgid "" +"The signature is the same as for :c:func:`PyObject_Str`; it must return a " +"string or a Unicode object. This function should return a \"friendly\" " +"string representation of the object, as this is the representation that will " +"be used, among other things, by the :func:`print` function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:335 +msgid "" +"When this field is not set, :c:func:`PyObject_Repr` is called to return a " +"string representation." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:343 +msgid "An optional pointer to the get-attribute function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:345 +msgid "" +"The signature is the same as for :c:func:`PyObject_GetAttr`. It is usually " +"convenient to set this field to :c:func:`PyObject_GenericGetAttr`, which " +"implements the normal way of looking for object attributes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:349 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_getattr`: a subtype inherits both :c:member:`~PyTypeObject.tp_getattr` " +"and :c:member:`~PyTypeObject.tp_getattro` from its base type when the " +"subtype's :c:member:`~PyTypeObject.tp_getattr` and :c:member:`~PyTypeObject." +"tp_getattro` are both *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:358 +msgid "" +"The signature is the same as for :c:func:`PyObject_SetAttr`, but setting *v* " +"to *NULL* to delete an attribute must be supported. It is usually " +"convenient to set this field to :c:func:`PyObject_GenericSetAttr`, which " +"implements the normal way of setting object attributes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:363 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_setattr`: a subtype inherits both :c:member:`~PyTypeObject.tp_setattr` " +"and :c:member:`~PyTypeObject.tp_setattro` from its base type when the " +"subtype's :c:member:`~PyTypeObject.tp_setattr` and :c:member:`~PyTypeObject." +"tp_setattro` are both *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:370 +msgid "" +"Pointer to an additional structure that contains fields relevant only to " +"objects which implement the buffer interface. These fields are documented " +"in :ref:`buffer-structs`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:374 +msgid "" +"The :c:member:`~PyTypeObject.tp_as_buffer` field is not inherited, but the " +"contained fields are inherited individually." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:380 +msgid "" +"This field is a bit mask of various flags. Some flags indicate variant " +"semantics for certain situations; others are used to indicate that certain " +"fields in the type object (or in the extension structures referenced via :c:" +"member:`~PyTypeObject.tp_as_number`, :c:member:`~PyTypeObject." +"tp_as_sequence`, :c:member:`~PyTypeObject.tp_as_mapping`, and :c:member:" +"`~PyTypeObject.tp_as_buffer`) that were historically not always present are " +"valid; if such a flag bit is clear, the type fields it guards must not be " +"accessed and must be considered to have a zero or *NULL* value instead." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:388 +msgid "" +"Inheritance of this field is complicated. Most flag bits are inherited " +"individually, i.e. if the base type has a flag bit set, the subtype inherits " +"this flag bit. The flag bits that pertain to extension structures are " +"strictly inherited if the extension structure is inherited, i.e. the base " +"type's value of the flag bit is copied into the subtype together with a " +"pointer to the extension structure. The :const:`Py_TPFLAGS_HAVE_GC` flag " +"bit is inherited together with the :c:member:`~PyTypeObject.tp_traverse` " +"and :c:member:`~PyTypeObject.tp_clear` fields, i.e. if the :const:" +"`Py_TPFLAGS_HAVE_GC` flag bit is clear in the subtype and the :c:member:" +"`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject.tp_clear` fields in " +"the subtype exist and have *NULL* values." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:399 +msgid "" +"The following bit masks are currently defined; these can be ORed together " +"using the ``|`` operator to form the value of the :c:member:`~PyTypeObject." +"tp_flags` field. The macro :c:func:`PyType_HasFeature` takes a type and a " +"flags value, *tp* and *f*, and checks whether ``tp->tp_flags & f`` is non-" +"zero." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:407 +msgid "" +"This bit is set when the type object itself is allocated on the heap. In " +"this case, the :attr:`ob_type` field of its instances is considered a " +"reference to the type, and the type object is INCREF'ed when a new instance " +"is created, and DECREF'ed when an instance is destroyed (this does not apply " +"to instances of subtypes; only the type referenced by the instance's ob_type " +"gets INCREF'ed or DECREF'ed)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:417 +msgid "" +"This bit is set when the type can be used as the base type of another type. " +"If this bit is clear, the type cannot be subtyped (similar to a \"final\" " +"class in Java)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:424 +msgid "" +"This bit is set when the type object has been fully initialized by :c:func:" +"`PyType_Ready`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:430 +msgid "" +"This bit is set while :c:func:`PyType_Ready` is in the process of " +"initializing the type object." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:436 +msgid "" +"This bit is set when the object supports garbage collection. If this bit is " +"set, instances must be created using :c:func:`PyObject_GC_New` and destroyed " +"using :c:func:`PyObject_GC_Del`. More information in section :ref:" +"`supporting-cycle-detection`. This bit also implies that the GC-related " +"fields :c:member:`~PyTypeObject.tp_traverse` and :c:member:`~PyTypeObject." +"tp_clear` are present in the type object." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:446 +msgid "" +"This is a bitmask of all the bits that pertain to the existence of certain " +"fields in the type object and its extension structures. Currently, it " +"includes the following bits: :const:`Py_TPFLAGS_HAVE_STACKLESS_EXTENSION`, :" +"const:`Py_TPFLAGS_HAVE_VERSION_TAG`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:461 +msgid "" +"These flags are used by functions such as :c:func:`PyLong_Check` to quickly " +"determine if a type is a subclass of a built-in type; such specific checks " +"are faster than a generic check, like :c:func:`PyObject_IsInstance`. Custom " +"types that inherit from built-ins should have their :c:member:`~PyTypeObject." +"tp_flags` set appropriately, or the code that interacts with such types will " +"behave differently depending on what kind of check is used." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:472 +msgid "" +"This bit is set when the :c:member:`~PyTypeObject.tp_finalize` slot is " +"present in the type structure." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:480 +msgid "" +"An optional pointer to a NUL-terminated C string giving the docstring for " +"this type object. This is exposed as the :attr:`__doc__` attribute on the " +"type and instances of the type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:484 +msgid "This field is *not* inherited by subtypes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:489 +msgid "" +"An optional pointer to a traversal function for the garbage collector. This " +"is only used if the :const:`Py_TPFLAGS_HAVE_GC` flag bit is set. More " +"information about Python's garbage collection scheme can be found in " +"section :ref:`supporting-cycle-detection`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:494 +msgid "" +"The :c:member:`~PyTypeObject.tp_traverse` pointer is used by the garbage " +"collector to detect reference cycles. A typical implementation of a :c:" +"member:`~PyTypeObject.tp_traverse` function simply calls :c:func:`Py_VISIT` " +"on each of the instance's members that are Python objects. For example, " +"this is function :c:func:`local_traverse` from the :mod:`_thread` extension " +"module::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:509 +msgid "" +"Note that :c:func:`Py_VISIT` is called only on those members that can " +"participate in reference cycles. Although there is also a ``self->key`` " +"member, it can only be *NULL* or a Python string and therefore cannot be " +"part of a reference cycle." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:513 +msgid "" +"On the other hand, even if you know a member can never be part of a cycle, " +"as a debugging aid you may want to visit it anyway just so the :mod:`gc` " +"module's :func:`~gc.get_referents` function will include it." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:517 +msgid "" +"Note that :c:func:`Py_VISIT` requires the *visit* and *arg* parameters to :c:" +"func:`local_traverse` to have these specific names; don't name them just " +"anything." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:521 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_clear` and the :const:`Py_TPFLAGS_HAVE_GC` flag bit: the flag bit, :c:" +"member:`~PyTypeObject.tp_traverse`, and :c:member:`~PyTypeObject.tp_clear` " +"are all inherited from the base type if they are all zero in the subtype." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:529 +msgid "" +"An optional pointer to a clear function for the garbage collector. This is " +"only used if the :const:`Py_TPFLAGS_HAVE_GC` flag bit is set." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:532 +msgid "" +"The :c:member:`~PyTypeObject.tp_clear` member function is used to break " +"reference cycles in cyclic garbage detected by the garbage collector. Taken " +"together, all :c:member:`~PyTypeObject.tp_clear` functions in the system " +"must combine to break all reference cycles. This is subtle, and if in any " +"doubt supply a :c:member:`~PyTypeObject.tp_clear` function. For example, " +"the tuple type does not implement a :c:member:`~PyTypeObject.tp_clear` " +"function, because it's possible to prove that no reference cycle can be " +"composed entirely of tuples. Therefore the :c:member:`~PyTypeObject." +"tp_clear` functions of other types must be sufficient to break any cycle " +"containing a tuple. This isn't immediately obvious, and there's rarely a " +"good reason to avoid implementing :c:member:`~PyTypeObject.tp_clear`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:542 +msgid "" +"Implementations of :c:member:`~PyTypeObject.tp_clear` should drop the " +"instance's references to those of its members that may be Python objects, " +"and set its pointers to those members to *NULL*, as in the following " +"example::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:556 +msgid "" +"The :c:func:`Py_CLEAR` macro should be used, because clearing references is " +"delicate: the reference to the contained object must not be decremented " +"until after the pointer to the contained object is set to *NULL*. This is " +"because decrementing the reference count may cause the contained object to " +"become trash, triggering a chain of reclamation activity that may include " +"invoking arbitrary Python code (due to finalizers, or weakref callbacks, " +"associated with the contained object). If it's possible for such code to " +"reference *self* again, it's important that the pointer to the contained " +"object be *NULL* at that time, so that *self* knows the contained object can " +"no longer be used. The :c:func:`Py_CLEAR` macro performs the operations in " +"a safe order." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:567 +msgid "" +"Because the goal of :c:member:`~PyTypeObject.tp_clear` functions is to break " +"reference cycles, it's not necessary to clear contained objects like Python " +"strings or Python integers, which can't participate in reference cycles. On " +"the other hand, it may be convenient to clear all contained Python objects, " +"and write the type's :c:member:`~PyTypeObject.tp_dealloc` function to " +"invoke :c:member:`~PyTypeObject.tp_clear`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:573 +msgid "" +"More information about Python's garbage collection scheme can be found in " +"section :ref:`supporting-cycle-detection`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:576 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_traverse` and the :const:`Py_TPFLAGS_HAVE_GC` flag bit: the flag bit, :c:" +"member:`~PyTypeObject.tp_traverse`, and :c:member:`~PyTypeObject.tp_clear` " +"are all inherited from the base type if they are all zero in the subtype." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:584 +msgid "" +"An optional pointer to the rich comparison function, whose signature is " +"``PyObject *tp_richcompare(PyObject *a, PyObject *b, int op)``. The first " +"parameter is guaranteed to be an instance of the type that is defined by :c:" +"type:`PyTypeObject`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:589 +msgid "" +"The function should return the result of the comparison (usually ``Py_True`` " +"or ``Py_False``). If the comparison is undefined, it must return " +"``Py_NotImplemented``, if another error occurred it must return ``NULL`` and " +"set an exception condition." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:596 +msgid "" +"If you want to implement a type for which only a limited set of comparisons " +"makes sense (e.g. ``==`` and ``!=``, but not ``<`` and friends), directly " +"raise :exc:`TypeError` in the rich comparison function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:600 +msgid "" +"This field is inherited by subtypes together with :c:member:`~PyTypeObject." +"tp_hash`: a subtype inherits :c:member:`~PyTypeObject.tp_richcompare` and :c:" +"member:`~PyTypeObject.tp_hash` when the subtype's :c:member:`~PyTypeObject." +"tp_richcompare` and :c:member:`~PyTypeObject.tp_hash` are both *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:605 +msgid "" +"The following constants are defined to be used as the third argument for :c:" +"member:`~PyTypeObject.tp_richcompare` and for :c:func:`PyObject_RichCompare`:" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:609 +msgid "Constant" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:609 +msgid "Comparison" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:611 +msgid ":const:`Py_LT`" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:611 +msgid "``<``" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:613 +msgid ":const:`Py_LE`" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:613 +msgid "``<=``" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:615 +msgid ":const:`Py_EQ`" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:615 +msgid "``==``" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:617 +msgid ":const:`Py_NE`" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:617 +msgid "``!=``" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:619 +msgid ":const:`Py_GT`" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:619 +msgid "``>``" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:621 +msgid ":const:`Py_GE`" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:621 +msgid "``>=``" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:627 +msgid "" +"If the instances of this type are weakly referenceable, this field is " +"greater than zero and contains the offset in the instance structure of the " +"weak reference list head (ignoring the GC header, if present); this offset " +"is used by :c:func:`PyObject_ClearWeakRefs` and the :c:func:`PyWeakref_\\*` " +"functions. The instance structure needs to include a field of type :c:type:" +"`PyObject\\*` which is initialized to *NULL*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:634 +msgid "" +"Do not confuse this field with :c:member:`~PyTypeObject.tp_weaklist`; that " +"is the list head for weak references to the type object itself." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:637 +msgid "" +"This field is inherited by subtypes, but see the rules listed below. A " +"subtype may override this offset; this means that the subtype uses a " +"different weak reference list head than the base type. Since the list head " +"is always found via :c:member:`~PyTypeObject.tp_weaklistoffset`, this should " +"not be a problem." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:642 +msgid "" +"When a type defined by a class statement has no :attr:`~object.__slots__` " +"declaration, and none of its base types are weakly referenceable, the type " +"is made weakly referenceable by adding a weak reference list head slot to " +"the instance layout and setting the :c:member:`~PyTypeObject." +"tp_weaklistoffset` of that slot's offset." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:647 +msgid "" +"When a type's :attr:`__slots__` declaration contains a slot named :attr:" +"`__weakref__`, that slot becomes the weak reference list head for instances " +"of the type, and the slot's offset is stored in the type's :c:member:" +"`~PyTypeObject.tp_weaklistoffset`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:652 +msgid "" +"When a type's :attr:`__slots__` declaration does not contain a slot named :" +"attr:`__weakref__`, the type inherits its :c:member:`~PyTypeObject." +"tp_weaklistoffset` from its base type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:658 +msgid "" +"An optional pointer to a function that returns an iterator for the object. " +"Its presence normally signals that the instances of this type are iterable " +"(although sequences may be iterable without this function)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:662 +msgid "This function has the same signature as :c:func:`PyObject_GetIter`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:669 +msgid "" +"An optional pointer to a function that returns the next item in an iterator. " +"When the iterator is exhausted, it must return *NULL*; a :exc:" +"`StopIteration` exception may or may not be set. When another error occurs, " +"it must return *NULL* too. Its presence signals that the instances of this " +"type are iterators." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:675 +msgid "" +"Iterator types should also define the :c:member:`~PyTypeObject.tp_iter` " +"function, and that function should return the iterator instance itself (not " +"a new iterator instance)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:679 +msgid "This function has the same signature as :c:func:`PyIter_Next`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:686 +msgid "" +"An optional pointer to a static *NULL*-terminated array of :c:type:" +"`PyMethodDef` structures, declaring regular methods of this type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:689 +msgid "" +"For each entry in the array, an entry is added to the type's dictionary " +"(see :c:member:`~PyTypeObject.tp_dict` below) containing a method descriptor." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:692 +msgid "" +"This field is not inherited by subtypes (methods are inherited through a " +"different mechanism)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:698 +msgid "" +"An optional pointer to a static *NULL*-terminated array of :c:type:" +"`PyMemberDef` structures, declaring regular data members (fields or slots) " +"of instances of this type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:702 +msgid "" +"For each entry in the array, an entry is added to the type's dictionary " +"(see :c:member:`~PyTypeObject.tp_dict` below) containing a member descriptor." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:705 +msgid "" +"This field is not inherited by subtypes (members are inherited through a " +"different mechanism)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:711 +msgid "" +"An optional pointer to a static *NULL*-terminated array of :c:type:" +"`PyGetSetDef` structures, declaring computed attributes of instances of this " +"type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:714 +msgid "" +"For each entry in the array, an entry is added to the type's dictionary " +"(see :c:member:`~PyTypeObject.tp_dict` below) containing a getset descriptor." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:717 +msgid "" +"This field is not inherited by subtypes (computed attributes are inherited " +"through a different mechanism)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:722 +msgid "Docs for PyGetSetDef::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:738 +msgid "" +"An optional pointer to a base type from which type properties are " +"inherited. At this level, only single inheritance is supported; multiple " +"inheritance require dynamically creating a type object by calling the " +"metatype." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:742 +msgid "" +"This field is not inherited by subtypes (obviously), but it defaults to " +"``&PyBaseObject_Type`` (which to Python programmers is known as the type :" +"class:`object`)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:749 +msgid "The type's dictionary is stored here by :c:func:`PyType_Ready`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:751 +msgid "" +"This field should normally be initialized to *NULL* before PyType_Ready is " +"called; it may also be initialized to a dictionary containing initial " +"attributes for the type. Once :c:func:`PyType_Ready` has initialized the " +"type, extra attributes for the type may be added to this dictionary only if " +"they don't correspond to overloaded operations (like :meth:`__add__`)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:757 +msgid "" +"This field is not inherited by subtypes (though the attributes defined in " +"here are inherited through a different mechanism)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:762 +msgid "" +"It is not safe to use :c:func:`PyDict_SetItem` on or otherwise modify :c:" +"member:`~PyTypeObject.tp_dict` with the dictionary C-API." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:768 +msgid "An optional pointer to a \"descriptor get\" function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:770 ../Doc/c-api/typeobj.rst:784 +#: ../Doc/c-api/typeobj.rst:856 ../Doc/c-api/typeobj.rst:878 +#: ../Doc/c-api/typeobj.rst:909 +msgid "The function signature is ::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:781 +msgid "" +"An optional pointer to a function for setting and deleting a descriptor's " +"value." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:788 +msgid "" +"The *value* argument is set to *NULL* to delete the value. This field is " +"inherited by subtypes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:796 +msgid "" +"If the instances of this type have a dictionary containing instance " +"variables, this field is non-zero and contains the offset in the instances " +"of the type of the instance variable dictionary; this offset is used by :c:" +"func:`PyObject_GenericGetAttr`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:801 +msgid "" +"Do not confuse this field with :c:member:`~PyTypeObject.tp_dict`; that is " +"the dictionary for attributes of the type object itself." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:804 +msgid "" +"If the value of this field is greater than zero, it specifies the offset " +"from the start of the instance structure. If the value is less than zero, " +"it specifies the offset from the *end* of the instance structure. A " +"negative offset is more expensive to use, and should only be used when the " +"instance structure contains a variable-length part. This is used for " +"example to add an instance variable dictionary to subtypes of :class:`str` " +"or :class:`tuple`. Note that the :c:member:`~PyTypeObject.tp_basicsize` " +"field should account for the dictionary added to the end in that case, even " +"though the dictionary is not included in the basic object layout. On a " +"system with a pointer size of 4 bytes, :c:member:`~PyTypeObject." +"tp_dictoffset` should be set to ``-4`` to indicate that the dictionary is at " +"the very end of the structure." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:816 +msgid "" +"The real dictionary offset in an instance can be computed from a negative :c:" +"member:`~PyTypeObject.tp_dictoffset` as follows::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:823 +msgid "" +"where :c:member:`~PyTypeObject.tp_basicsize`, :c:member:`~PyTypeObject." +"tp_itemsize` and :c:member:`~PyTypeObject.tp_dictoffset` are taken from the " +"type object, and :attr:`ob_size` is taken from the instance. The absolute " +"value is taken because ints use the sign of :attr:`ob_size` to store the " +"sign of the number. (There's never a need to do this calculation yourself; " +"it is done for you by :c:func:`_PyObject_GetDictPtr`.)" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:829 +msgid "" +"This field is inherited by subtypes, but see the rules listed below. A " +"subtype may override this offset; this means that the subtype instances " +"store the dictionary at a difference offset than the base type. Since the " +"dictionary is always found via :c:member:`~PyTypeObject.tp_dictoffset`, this " +"should not be a problem." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:834 +msgid "" +"When a type defined by a class statement has no :attr:`~object.__slots__` " +"declaration, and none of its base types has an instance variable dictionary, " +"a dictionary slot is added to the instance layout and the :c:member:" +"`~PyTypeObject.tp_dictoffset` is set to that slot's offset." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:839 +msgid "" +"When a type defined by a class statement has a :attr:`__slots__` " +"declaration, the type inherits its :c:member:`~PyTypeObject.tp_dictoffset` " +"from its base type." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:842 +msgid "" +"(Adding a slot named :attr:`~object.__dict__` to the :attr:`__slots__` " +"declaration does not have the expected effect, it just causes confusion. " +"Maybe this should be added as a feature just like :attr:`__weakref__` " +"though.)" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:849 +msgid "An optional pointer to an instance initialization function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:851 +msgid "" +"This function corresponds to the :meth:`__init__` method of classes. Like :" +"meth:`__init__`, it is possible to create an instance without calling :meth:" +"`__init__`, and it is possible to reinitialize an instance by calling its :" +"meth:`__init__` method again." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:860 +msgid "" +"The self argument is the instance to be initialized; the *args* and *kwds* " +"arguments represent positional and keyword arguments of the call to :meth:" +"`__init__`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:864 +msgid "" +"The :c:member:`~PyTypeObject.tp_init` function, if not *NULL*, is called " +"when an instance is created normally by calling its type, after the type's :" +"c:member:`~PyTypeObject.tp_new` function has returned an instance of the " +"type. If the :c:member:`~PyTypeObject.tp_new` function returns an instance " +"of some other type that is not a subtype of the original type, no :c:member:" +"`~PyTypeObject.tp_init` function is called; if :c:member:`~PyTypeObject." +"tp_new` returns an instance of a subtype of the original type, the " +"subtype's :c:member:`~PyTypeObject.tp_init` is called." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:876 +msgid "An optional pointer to an instance allocation function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:882 +msgid "" +"The purpose of this function is to separate memory allocation from memory " +"initialization. It should return a pointer to a block of memory of adequate " +"length for the instance, suitably aligned, and initialized to zeros, but " +"with :attr:`ob_refcnt` set to ``1`` and :attr:`ob_type` set to the type " +"argument. If the type's :c:member:`~PyTypeObject.tp_itemsize` is non-zero, " +"the object's :attr:`ob_size` field should be initialized to *nitems* and the " +"length of the allocated memory block should be ``tp_basicsize + " +"nitems*tp_itemsize``, rounded up to a multiple of ``sizeof(void*)``; " +"otherwise, *nitems* is not used and the length of the block should be :c:" +"member:`~PyTypeObject.tp_basicsize`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:892 +msgid "" +"Do not use this function to do any other instance initialization, not even " +"to allocate additional memory; that should be done by :c:member:" +"`~PyTypeObject.tp_new`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:895 +msgid "" +"This field is inherited by static subtypes, but not by dynamic subtypes " +"(subtypes created by a class statement); in the latter, this field is always " +"set to :c:func:`PyType_GenericAlloc`, to force a standard heap allocation " +"strategy. That is also the recommended value for statically defined types." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:903 +msgid "An optional pointer to an instance creation function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:905 +msgid "" +"If this function is *NULL* for a particular type, that type cannot be called " +"to create new instances; presumably there is some other way to create " +"instances, like a factory function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:913 +msgid "" +"The subtype argument is the type of the object being created; the *args* and " +"*kwds* arguments represent positional and keyword arguments of the call to " +"the type. Note that subtype doesn't have to equal the type whose :c:member:" +"`~PyTypeObject.tp_new` function is called; it may be a subtype of that type " +"(but not an unrelated type)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:919 +msgid "" +"The :c:member:`~PyTypeObject.tp_new` function should call ``subtype-" +">tp_alloc(subtype, nitems)`` to allocate space for the object, and then do " +"only as much further initialization as is absolutely necessary. " +"Initialization that can safely be ignored or repeated should be placed in " +"the :c:member:`~PyTypeObject.tp_init` handler. A good rule of thumb is that " +"for immutable types, all initialization should take place in :c:member:" +"`~PyTypeObject.tp_new`, while for mutable types, most initialization should " +"be deferred to :c:member:`~PyTypeObject.tp_init`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:927 +msgid "" +"This field is inherited by subtypes, except it is not inherited by static " +"types whose :c:member:`~PyTypeObject.tp_base` is *NULL* or " +"``&PyBaseObject_Type``." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:933 +msgid "" +"An optional pointer to an instance deallocation function. Its signature is :" +"c:type:`freefunc`::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:938 +msgid "" +"An initializer that is compatible with this signature is :c:func:" +"`PyObject_Free`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:940 +msgid "" +"This field is inherited by static subtypes, but not by dynamic subtypes " +"(subtypes created by a class statement); in the latter, this field is set to " +"a deallocator suitable to match :c:func:`PyType_GenericAlloc` and the value " +"of the :const:`Py_TPFLAGS_HAVE_GC` flag bit." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:948 +msgid "An optional pointer to a function called by the garbage collector." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:950 +msgid "" +"The garbage collector needs to know whether a particular object is " +"collectible or not. Normally, it is sufficient to look at the object's " +"type's :c:member:`~PyTypeObject.tp_flags` field, and check the :const:" +"`Py_TPFLAGS_HAVE_GC` flag bit. But some types have a mixture of statically " +"and dynamically allocated instances, and the statically allocated instances " +"are not collectible. Such types should define this function; it should " +"return ``1`` for a collectible instance, and ``0`` for a non-collectible " +"instance. The signature is ::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:960 +msgid "" +"(The only example of this are types themselves. The metatype, :c:data:" +"`PyType_Type`, defines this function to distinguish between statically and " +"dynamically allocated types.)" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:969 +msgid "Tuple of base types." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:971 +msgid "" +"This is set for types created by a class statement. It should be *NULL* for " +"statically defined types." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:974 +msgid "This field is not inherited." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:979 +msgid "" +"Tuple containing the expanded set of base types, starting with the type " +"itself and ending with :class:`object`, in Method Resolution Order." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:982 +msgid "" +"This field is not inherited; it is calculated fresh by :c:func:" +"`PyType_Ready`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:987 +msgid "" +"An optional pointer to an instance finalization function. Its signature is :" +"c:type:`destructor`::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:992 +msgid "" +"If :c:member:`~PyTypeObject.tp_finalize` is set, the interpreter calls it " +"once when finalizing an instance. It is called either from the garbage " +"collector (if the instance is part of an isolated reference cycle) or just " +"before the object is deallocated. Either way, it is guaranteed to be called " +"before attempting to break reference cycles, ensuring that it finds the " +"object in a sane state." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:999 +msgid "" +":c:member:`~PyTypeObject.tp_finalize` should not mutate the current " +"exception status; therefore, a recommended way to write a non-trivial " +"finalizer is::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1016 +msgid "" +"For this field to be taken into account (even through inheritance), you must " +"also set the :const:`Py_TPFLAGS_HAVE_FINALIZE` flags bit." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1023 +msgid "\"Safe object finalization\" (:pep:`442`)" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1028 +msgid "Unused. Not inherited. Internal use only." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1033 +msgid "" +"List of weak references to subclasses. Not inherited. Internal use only." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1038 +msgid "" +"Weak reference list head, for weak references to this type object. Not " +"inherited. Internal use only." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1041 +msgid "" +"The remaining fields are only defined if the feature test macro :const:" +"`COUNT_ALLOCS` is defined, and are for internal use only. They are " +"documented here for completeness. None of these fields are inherited by " +"subtypes." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1049 +msgid "Number of allocations." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1054 +msgid "Number of frees." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1059 +msgid "Maximum simultaneously allocated objects." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1064 +msgid "" +"Pointer to the next type object with a non-zero :c:member:`~PyTypeObject." +"tp_allocs` field." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1066 +msgid "" +"Also, note that, in a garbage collected Python, tp_dealloc may be called " +"from any Python thread, not just the thread which created the object (if the " +"object becomes part of a refcount cycle, that cycle might be collected by a " +"garbage collection on any thread). This is not a problem for Python API " +"calls, since the thread on which tp_dealloc is called will own the Global " +"Interpreter Lock (GIL). However, if the object being destroyed in turn " +"destroys objects from some other C or C++ library, care should be taken to " +"ensure that destroying those objects on the thread which called tp_dealloc " +"will not violate any assumptions of the library." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1080 +msgid "Number Object Structures" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1087 +msgid "" +"This structure holds pointers to the functions which an object uses to " +"implement the number protocol. Each function is used by the function of " +"similar name documented in the :ref:`number` section." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1091 ../Doc/c-api/typeobj.rst:1364 +msgid "Here is the structure definition::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1138 +msgid "" +"Binary and ternary functions must check the type of all their operands, and " +"implement the necessary conversions (at least one of the operands is an " +"instance of the defined type). If the operation is not defined for the " +"given operands, binary and ternary functions must return " +"``Py_NotImplemented``, if another error occurred they must return ``NULL`` " +"and set an exception." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1147 +msgid "" +"The :c:data:`nb_reserved` field should always be ``NULL``. It was " +"previously called :c:data:`nb_long`, and was renamed in Python 3.0.1." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1155 +msgid "Mapping Object Structures" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1162 +msgid "" +"This structure holds pointers to the functions which an object uses to " +"implement the mapping protocol. It has three members:" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1167 +msgid "" +"This function is used by :c:func:`PyMapping_Length` and :c:func:" +"`PyObject_Size`, and has the same signature. This slot may be set to *NULL* " +"if the object has no defined length." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1173 +msgid "" +"This function is used by :c:func:`PyObject_GetItem` and has the same " +"signature. This slot must be filled for the :c:func:`PyMapping_Check` " +"function to return ``1``, it can be *NULL* otherwise." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1179 +msgid "" +"This function is used by :c:func:`PyObject_SetItem` and :c:func:" +"`PyObject_DelItem`. It has the same signature as :c:func:" +"`PyObject_SetItem`, but *v* can also be set to *NULL* to delete an item. If " +"this slot is *NULL*, the object does not support item assignment and " +"deletion." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1189 +msgid "Sequence Object Structures" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1196 +msgid "" +"This structure holds pointers to the functions which an object uses to " +"implement the sequence protocol." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1201 +msgid "" +"This function is used by :c:func:`PySequence_Size` and :c:func:" +"`PyObject_Size`, and has the same signature." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1206 +msgid "" +"This function is used by :c:func:`PySequence_Concat` and has the same " +"signature. It is also used by the ``+`` operator, after trying the numeric " +"addition via the :c:member:`~PyTypeObject.tp_as_number.nb_add` slot." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1212 +msgid "" +"This function is used by :c:func:`PySequence_Repeat` and has the same " +"signature. It is also used by the ``*`` operator, after trying numeric " +"multiplication via the :c:member:`~PyTypeObject.tp_as_number.nb_multiply` " +"slot." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1219 +msgid "" +"This function is used by :c:func:`PySequence_GetItem` and has the same " +"signature. This slot must be filled for the :c:func:`PySequence_Check` " +"function to return ``1``, it can be *NULL* otherwise." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1223 +msgid "" +"Negative indexes are handled as follows: if the :attr:`sq_length` slot is " +"filled, it is called and the sequence length is used to compute a positive " +"index which is passed to :attr:`sq_item`. If :attr:`sq_length` is *NULL*, " +"the index is passed as is to the function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1230 +msgid "" +"This function is used by :c:func:`PySequence_SetItem` and has the same " +"signature. This slot may be left to *NULL* if the object does not support " +"item assignment and deletion." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1236 +msgid "" +"This function may be used by :c:func:`PySequence_Contains` and has the same " +"signature. This slot may be left to *NULL*, in this case :c:func:" +"`PySequence_Contains` simply traverses the sequence until it finds a match." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1243 +msgid "" +"This function is used by :c:func:`PySequence_InPlaceConcat` and has the same " +"signature. It should modify its first operand, and return it." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1248 +msgid "" +"This function is used by :c:func:`PySequence_InPlaceRepeat` and has the same " +"signature. It should modify its first operand, and return it." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1258 +msgid "Buffer Object Structures" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1266 +msgid "" +"This structure holds pointers to the functions required by the :ref:`Buffer " +"protocol `. The protocol defines how an exporter object can " +"expose its internal data to consumer objects." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1272 ../Doc/c-api/typeobj.rst:1321 +#: ../Doc/c-api/typeobj.rst:1374 ../Doc/c-api/typeobj.rst:1385 +#: ../Doc/c-api/typeobj.rst:1396 +msgid "The signature of this function is::" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1276 +msgid "" +"Handle a request to *exporter* to fill in *view* as specified by *flags*. " +"Except for point (3), an implementation of this function MUST take these " +"steps:" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1280 +msgid "" +"Check if the request can be met. If not, raise :c:data:`PyExc_BufferError`, " +"set :c:data:`view->obj` to *NULL* and return -1." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1283 +msgid "Fill in the requested fields." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1285 +msgid "Increment an internal counter for the number of exports." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1287 +msgid "" +"Set :c:data:`view->obj` to *exporter* and increment :c:data:`view->obj`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1289 +msgid "Return 0." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1291 +msgid "" +"If *exporter* is part of a chain or tree of buffer providers, two main " +"schemes can be used:" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1294 +msgid "" +"Re-export: Each member of the tree acts as the exporting object and sets :c:" +"data:`view->obj` to a new reference to itself." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1297 +msgid "" +"Redirect: The buffer request is redirected to the root object of the tree. " +"Here, :c:data:`view->obj` will be a new reference to the root object." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1301 +msgid "" +"The individual fields of *view* are described in section :ref:`Buffer " +"structure `, the rules how an exporter must react to " +"specific requests are in section :ref:`Buffer request types `." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1306 +msgid "" +"All memory pointed to in the :c:type:`Py_buffer` structure belongs to the " +"exporter and must remain valid until there are no consumers left. :c:member:" +"`~Py_buffer.format`, :c:member:`~Py_buffer.shape`, :c:member:`~Py_buffer." +"strides`, :c:member:`~Py_buffer.suboffsets` and :c:member:`~Py_buffer." +"internal` are read-only for the consumer." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1313 +msgid "" +":c:func:`PyBuffer_FillInfo` provides an easy way of exposing a simple bytes " +"buffer while dealing correctly with all request types." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1316 +msgid "" +":c:func:`PyObject_GetBuffer` is the interface for the consumer that wraps " +"this function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1325 +msgid "" +"Handle a request to release the resources of the buffer. If no resources " +"need to be released, :c:member:`PyBufferProcs.bf_releasebuffer` may be " +"*NULL*. Otherwise, a standard implementation of this function will take " +"these optional steps:" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1330 +msgid "Decrement an internal counter for the number of exports." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1332 +msgid "If the counter is 0, free all memory associated with *view*." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1334 +msgid "" +"The exporter MUST use the :c:member:`~Py_buffer.internal` field to keep " +"track of buffer-specific resources. This field is guaranteed to remain " +"constant, while a consumer MAY pass a copy of the original buffer as the " +"*view* argument." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1340 +msgid "" +"This function MUST NOT decrement :c:data:`view->obj`, since that is done " +"automatically in :c:func:`PyBuffer_Release` (this scheme is useful for " +"breaking reference cycles)." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1345 +msgid "" +":c:func:`PyBuffer_Release` is the interface for the consumer that wraps this " +"function." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1353 +msgid "Async Object Structures" +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1361 +msgid "" +"This structure holds pointers to the functions required to implement :term:" +"`awaitable` and :term:`asynchronous iterator` objects." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1378 +msgid "" +"The returned object must be an iterator, i.e. :c:func:`PyIter_Check` must " +"return ``1`` for it." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1381 +msgid "" +"This slot may be set to *NULL* if an object is not an :term:`awaitable`." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1389 +msgid "" +"Must return an :term:`awaitable` object. See :meth:`__anext__` for details." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1391 +msgid "" +"This slot may be set to *NULL* if an object does not implement asynchronous " +"iteration protocol." +msgstr "" + +#: ../Doc/c-api/typeobj.rst:1400 +msgid "" +"Must return an :term:`awaitable` object. See :meth:`__anext__` for details. " +"This slot may be set to *NULL*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:6 +msgid "Unicode Objects and Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:12 +msgid "Unicode Objects" +msgstr "" + +#: ../Doc/c-api/unicode.rst:14 +msgid "" +"Since the implementation of :pep:`393` in Python 3.3, Unicode objects " +"internally use a variety of representations, in order to allow handling the " +"complete range of Unicode characters while staying memory efficient. There " +"are special cases for strings where all code points are below 128, 256, or " +"65536; otherwise, code points must be below 1114112 (which is the full " +"Unicode range)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:20 +msgid "" +":c:type:`Py_UNICODE*` and UTF-8 representations are created on demand and " +"cached in the Unicode object. The :c:type:`Py_UNICODE*` representation is " +"deprecated and inefficient; it should be avoided in performance- or memory-" +"sensitive situations." +msgstr "" + +#: ../Doc/c-api/unicode.rst:25 +msgid "" +"Due to the transition between the old APIs and the new APIs, unicode objects " +"can internally be in two states depending on how they were created:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:28 +msgid "" +"\"canonical\" unicode objects are all objects created by a non-deprecated " +"unicode API. They use the most efficient representation allowed by the " +"implementation." +msgstr "" + +#: ../Doc/c-api/unicode.rst:32 +msgid "" +"\"legacy\" unicode objects have been created through one of the deprecated " +"APIs (typically :c:func:`PyUnicode_FromUnicode`) and only bear the :c:type:" +"`Py_UNICODE*` representation; you will have to call :c:func:" +"`PyUnicode_READY` on them before calling any other API." +msgstr "" + +#: ../Doc/c-api/unicode.rst:39 +msgid "Unicode Type" +msgstr "" + +#: ../Doc/c-api/unicode.rst:41 +msgid "" +"These are the basic Unicode object types used for the Unicode implementation " +"in Python:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:48 +msgid "" +"These types are typedefs for unsigned integer types wide enough to contain " +"characters of 32 bits, 16 bits and 8 bits, respectively. When dealing with " +"single Unicode characters, use :c:type:`Py_UCS4`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:57 +msgid "" +"This is a typedef of :c:type:`wchar_t`, which is a 16-bit type or 32-bit " +"type depending on the platform." +msgstr "" + +#: ../Doc/c-api/unicode.rst:60 +msgid "" +"In previous versions, this was a 16-bit type or a 32-bit type depending on " +"whether you selected a \"narrow\" or \"wide\" Unicode version of Python at " +"build time." +msgstr "" + +#: ../Doc/c-api/unicode.rst:70 +msgid "" +"These subtypes of :c:type:`PyObject` represent a Python Unicode object. In " +"almost all cases, they shouldn't be used directly, since all API functions " +"that deal with Unicode objects take and return :c:type:`PyObject` pointers." +msgstr "" + +#: ../Doc/c-api/unicode.rst:79 +msgid "" +"This instance of :c:type:`PyTypeObject` represents the Python Unicode type. " +"It is exposed to Python code as ``str``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:83 +msgid "" +"The following APIs are really C macros and can be used to do fast checks and " +"to access internal read-only data of Unicode objects:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:88 +msgid "" +"Return true if the object *o* is a Unicode object or an instance of a " +"Unicode subtype." +msgstr "" + +#: ../Doc/c-api/unicode.rst:94 +msgid "" +"Return true if the object *o* is a Unicode object, but not an instance of a " +"subtype." +msgstr "" + +#: ../Doc/c-api/unicode.rst:100 +msgid "" +"Ensure the string object *o* is in the \"canonical\" representation. This " +"is required before using any of the access macros described below." +msgstr "" + +#: ../Doc/c-api/unicode.rst:105 +msgid "" +"Returns 0 on success and -1 with an exception set on failure, which in " +"particular happens if memory allocation fails." +msgstr "" + +#: ../Doc/c-api/unicode.rst:113 +msgid "" +"Return the length of the Unicode string, in code points. *o* has to be a " +"Unicode object in the \"canonical\" representation (not checked)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:123 +msgid "" +"Return a pointer to the canonical representation cast to UCS1, UCS2 or UCS4 " +"integer types for direct character access. No checks are performed if the " +"canonical representation has the correct character size; use :c:func:" +"`PyUnicode_KIND` to select the right macro. Make sure :c:func:" +"`PyUnicode_READY` has been called before accessing this." +msgstr "" + +#: ../Doc/c-api/unicode.rst:137 +msgid "Return values of the :c:func:`PyUnicode_KIND` macro." +msgstr "" + +#: ../Doc/c-api/unicode.rst:144 +msgid "" +"Return one of the PyUnicode kind constants (see above) that indicate how " +"many bytes per character this Unicode object uses to store its data. *o* " +"has to be a Unicode object in the \"canonical\" representation (not checked)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:155 +msgid "" +"Return a void pointer to the raw unicode buffer. *o* has to be a Unicode " +"object in the \"canonical\" representation (not checked)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:164 +msgid "" +"Write into a canonical representation *data* (as obtained with :c:func:" +"`PyUnicode_DATA`). This macro does not do any sanity checks and is intended " +"for usage in loops. The caller should cache the *kind* value and *data* " +"pointer as obtained from other macro calls. *index* is the index in the " +"string (starts at 0) and *value* is the new code point value which should be " +"written to that location." +msgstr "" + +#: ../Doc/c-api/unicode.rst:176 +msgid "" +"Read a code point from a canonical representation *data* (as obtained with :" +"c:func:`PyUnicode_DATA`). No checks or ready calls are performed." +msgstr "" + +#: ../Doc/c-api/unicode.rst:184 +msgid "" +"Read a character from a Unicode object *o*, which must be in the \"canonical" +"\" representation. This is less efficient than :c:func:`PyUnicode_READ` if " +"you do multiple consecutive reads." +msgstr "" + +#: ../Doc/c-api/unicode.rst:193 +msgid "" +"Return the maximum code point that is suitable for creating another string " +"based on *o*, which must be in the \"canonical\" representation. This is " +"always an approximation but more efficient than iterating over the string." +msgstr "" + +#: ../Doc/c-api/unicode.rst:207 +msgid "" +"Return the size of the deprecated :c:type:`Py_UNICODE` representation, in " +"code units (this includes surrogate pairs as 2 units). *o* has to be a " +"Unicode object (not checked)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:213 ../Doc/c-api/unicode.rst:223 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Unicode API, please migrate to using PyUnicode_GET_LENGTH()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:213 ../Doc/c-api/unicode.rst:223 +msgid "" +"Part of the old-style Unicode API, please migrate to using :c:func:" +"`PyUnicode_GET_LENGTH`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:218 +msgid "" +"Return the size of the deprecated :c:type:`Py_UNICODE` representation in " +"bytes. *o* has to be a Unicode object (not checked)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:229 +msgid "" +"Return a pointer to a :c:type:`Py_UNICODE` representation of the object. " +"The returned buffer is always terminated with an extra null code point. It " +"may also contain embedded null code points, which would cause the string to " +"be truncated when used in most C functions. The ``AS_DATA`` form casts the " +"pointer to :c:type:`const char *`. The *o* argument has to be a Unicode " +"object (not checked)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:236 +msgid "" +"This macro is now inefficient -- because in many cases the :c:type:" +"`Py_UNICODE` representation does not exist and needs to be created -- and " +"can fail (return *NULL* with an exception set). Try to port the code to use " +"the new :c:func:`PyUnicode_nBYTE_DATA` macros or use :c:func:" +"`PyUnicode_WRITE` or :c:func:`PyUnicode_READ`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:245 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Unicode API, please migrate to using the PyUnicode_nBYTE_DATA() " +"family of macros." +msgstr "" + +#: ../Doc/c-api/unicode.rst:245 +msgid "" +"Part of the old-style Unicode API, please migrate to using the :c:func:" +"`PyUnicode_nBYTE_DATA` family of macros." +msgstr "" + +#: ../Doc/c-api/unicode.rst:249 +msgid "Unicode Character Properties" +msgstr "" + +#: ../Doc/c-api/unicode.rst:251 +msgid "" +"Unicode provides many different character properties. The most often needed " +"ones are available through these macros which are mapped to C functions " +"depending on the Python configuration." +msgstr "" + +#: ../Doc/c-api/unicode.rst:258 +msgid "Return 1 or 0 depending on whether *ch* is a whitespace character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:263 +msgid "Return 1 or 0 depending on whether *ch* is a lowercase character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:268 +msgid "Return 1 or 0 depending on whether *ch* is an uppercase character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:273 +msgid "Return 1 or 0 depending on whether *ch* is a titlecase character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:278 +msgid "Return 1 or 0 depending on whether *ch* is a linebreak character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:283 +msgid "Return 1 or 0 depending on whether *ch* is a decimal character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:288 +msgid "Return 1 or 0 depending on whether *ch* is a digit character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:293 +msgid "Return 1 or 0 depending on whether *ch* is a numeric character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:298 +msgid "Return 1 or 0 depending on whether *ch* is an alphabetic character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:303 +msgid "Return 1 or 0 depending on whether *ch* is an alphanumeric character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:308 +msgid "" +"Return 1 or 0 depending on whether *ch* is a printable character. " +"Nonprintable characters are those characters defined in the Unicode " +"character database as \"Other\" or \"Separator\", excepting the ASCII space " +"(0x20) which is considered printable. (Note that printable characters in " +"this context are those which should not be escaped when :func:`repr` is " +"invoked on a string. It has no bearing on the handling of strings written " +"to :data:`sys.stdout` or :data:`sys.stderr`.)" +msgstr "" + +#: ../Doc/c-api/unicode.rst:317 +msgid "These APIs can be used for fast direct character conversions:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:322 +msgid "Return the character *ch* converted to lower case." +msgstr "" + +#: ../Doc/c-api/unicode.rst:324 ../Doc/c-api/unicode.rst:332 +#: ../Doc/c-api/unicode.rst:340 +msgid "This function uses simple case mappings." +msgstr "" + +#: ../Doc/c-api/unicode.rst:330 +msgid "Return the character *ch* converted to upper case." +msgstr "" + +#: ../Doc/c-api/unicode.rst:338 +msgid "Return the character *ch* converted to title case." +msgstr "" + +#: ../Doc/c-api/unicode.rst:346 +msgid "" +"Return the character *ch* converted to a decimal positive integer. Return " +"``-1`` if this is not possible. This macro does not raise exceptions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:352 +msgid "" +"Return the character *ch* converted to a single digit integer. Return ``-1`` " +"if this is not possible. This macro does not raise exceptions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:358 +msgid "" +"Return the character *ch* converted to a double. Return ``-1.0`` if this is " +"not possible. This macro does not raise exceptions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:362 +msgid "These APIs can be used to work with surrogates:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:366 +msgid "Check if *ch* is a surrogate (``0xD800 <= ch <= 0xDFFF``)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:370 +msgid "Check if *ch* is a high surrogate (``0xD800 <= ch <= 0xDBFF``)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:374 +msgid "Check if *ch* is a low surrogate (``0xDC00 <= ch <= 0xDFFF``)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:378 +msgid "" +"Join two surrogate characters and return a single Py_UCS4 value. *high* and " +"*low* are respectively the leading and trailing surrogates in a surrogate " +"pair." +msgstr "" + +#: ../Doc/c-api/unicode.rst:384 +msgid "Creating and accessing Unicode strings" +msgstr "" + +#: ../Doc/c-api/unicode.rst:386 +msgid "" +"To create Unicode objects and access their basic sequence properties, use " +"these APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:391 +msgid "" +"Create a new Unicode object. *maxchar* should be the true maximum code " +"point to be placed in the string. As an approximation, it can be rounded up " +"to the nearest value in the sequence 127, 255, 65535, 1114111." +msgstr "" + +#: ../Doc/c-api/unicode.rst:395 +msgid "" +"This is the recommended way to allocate a new Unicode object. Objects " +"created using this function are not resizable." +msgstr "" + +#: ../Doc/c-api/unicode.rst:404 +msgid "" +"Create a new Unicode object with the given *kind* (possible values are :c:" +"macro:`PyUnicode_1BYTE_KIND` etc., as returned by :c:func:" +"`PyUnicode_KIND`). The *buffer* must point to an array of *size* units of " +"1, 2 or 4 bytes per character, as given by the kind." +msgstr "" + +#: ../Doc/c-api/unicode.rst:414 +msgid "" +"Create a Unicode object from the char buffer *u*. The bytes will be " +"interpreted as being UTF-8 encoded. The buffer is copied into the new " +"object. If the buffer is not *NULL*, the return value might be a shared " +"object, i.e. modification of the data is not allowed." +msgstr "" + +#: ../Doc/c-api/unicode.rst:419 +msgid "" +"If *u* is *NULL*, this function behaves like :c:func:`PyUnicode_FromUnicode` " +"with the buffer set to *NULL*. This usage is deprecated in favor of :c:func:" +"`PyUnicode_New`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:426 +msgid "" +"Create a Unicode object from a UTF-8 encoded null-terminated char buffer *u*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:432 +msgid "" +"Take a C :c:func:`printf`\\ -style *format* string and a variable number of " +"arguments, calculate the size of the resulting Python unicode string and " +"return a string with the values formatted into it. The variable arguments " +"must be C types and must correspond exactly to the format characters in the " +"*format* ASCII-encoded string. The following format characters are allowed:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:451 +msgid "A single character, represented as a C int." +msgstr "" + +#: ../Doc/c-api/unicode.rst:463 +msgid ":attr:`%li`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:463 +msgid "Exactly equivalent to ``printf(\"%li\")``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:469 +msgid ":attr:`%lld`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:469 +msgid "Exactly equivalent to ``printf(\"%lld\")``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:472 +msgid ":attr:`%lli`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:472 +msgid "Exactly equivalent to ``printf(\"%lli\")``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:475 +msgid ":attr:`%llu`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:475 +msgid "Exactly equivalent to ``printf(\"%llu\")``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:481 +msgid ":attr:`%zi`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:481 +msgid "Exactly equivalent to ``printf(\"%zi\")``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:504 +msgid ":attr:`%A`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:504 ../Doc/c-api/unicode.rst:507 +#: ../Doc/c-api/unicode.rst:516 ../Doc/c-api/unicode.rst:519 +msgid "PyObject\\*" +msgstr "" + +#: ../Doc/c-api/unicode.rst:504 +msgid "The result of calling :func:`ascii`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:507 +msgid ":attr:`%U`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:507 +msgid "A unicode object." +msgstr "" + +#: ../Doc/c-api/unicode.rst:509 +msgid ":attr:`%V`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:509 +msgid "PyObject\\*, char \\*" +msgstr "" + +#: ../Doc/c-api/unicode.rst:509 +msgid "" +"A unicode object (which may be *NULL*) and a null-terminated C character " +"array as a second parameter (which will be used, if the first parameter is " +"*NULL*)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:516 +msgid ":attr:`%S`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:516 +msgid "The result of calling :c:func:`PyObject_Str`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:519 +msgid ":attr:`%R`" +msgstr "" + +#: ../Doc/c-api/unicode.rst:519 +msgid "The result of calling :c:func:`PyObject_Repr`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:523 +msgid "" +"An unrecognized format character causes all the rest of the format string to " +"be copied as-is to the result string, and any extra arguments discarded." +msgstr "" + +#: ../Doc/c-api/unicode.rst:527 +msgid "" +"The width formatter unit is number of characters rather than bytes. The " +"precision formatter unit is number of bytes for ``\"%s\"`` and ``\"%V\"`` " +"(if the ``PyObject*`` argument is NULL), and a number of characters for ``" +"\"%A\"``, ``\"%U\"``, ``\"%S\"``, ``\"%R\"`` and ``\"%V\"`` (if the " +"``PyObject*`` argument is not NULL)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:533 +msgid "Support for ``\"%lld\"`` and ``\"%llu\"`` added." +msgstr "" + +#: ../Doc/c-api/unicode.rst:536 +msgid "Support for ``\"%li\"``, ``\"%lli\"`` and ``\"%zi\"`` added." +msgstr "" + +#: ../Doc/c-api/unicode.rst:539 +msgid "" +"Support width and precision formatter for ``\"%s\"``, ``\"%A\"``, ``\"%U" +"\"``, ``\"%V\"``, ``\"%S\"``, ``\"%R\"`` added." +msgstr "" + +#: ../Doc/c-api/unicode.rst:546 +msgid "" +"Identical to :c:func:`PyUnicode_FromFormat` except that it takes exactly two " +"arguments." +msgstr "" + +#: ../Doc/c-api/unicode.rst:553 +msgid "Decode an encoded object *obj* to a Unicode object." +msgstr "" + +#: ../Doc/c-api/unicode.rst:555 +msgid "" +":class:`bytes`, :class:`bytearray` and other :term:`bytes-like objects " +"` are decoded according to the given *encoding* and using " +"the error handling defined by *errors*. Both can be *NULL* to have the " +"interface use the default values (see :ref:`builtincodecs` for details)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:561 +msgid "" +"All other objects, including Unicode objects, cause a :exc:`TypeError` to be " +"set." +msgstr "" + +#: ../Doc/c-api/unicode.rst:564 +msgid "" +"The API returns *NULL* if there was an error. The caller is responsible for " +"decref'ing the returned objects." +msgstr "" + +#: ../Doc/c-api/unicode.rst:570 +msgid "Return the length of the Unicode object, in code points." +msgstr "" + +#: ../Doc/c-api/unicode.rst:581 +msgid "" +"Copy characters from one Unicode object into another. This function " +"performs character conversion when necessary and falls back to :c:func:" +"`memcpy` if possible. Returns ``-1`` and sets an exception on error, " +"otherwise returns the number of copied characters." +msgstr "" + +#: ../Doc/c-api/unicode.rst:592 +msgid "" +"Fill a string with a character: write *fill_char* into ``unicode[start:start" +"+length]``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:595 +msgid "" +"Fail if *fill_char* is bigger than the string maximum character, or if the " +"string has more than 1 reference." +msgstr "" + +#: ../Doc/c-api/unicode.rst:598 +msgid "" +"Return the number of written character, or return ``-1`` and raise an " +"exception on error." +msgstr "" + +#: ../Doc/c-api/unicode.rst:607 +msgid "" +"Write a character to a string. The string must have been created through :c:" +"func:`PyUnicode_New`. Since Unicode strings are supposed to be immutable, " +"the string must not be shared, or have been hashed yet." +msgstr "" + +#: ../Doc/c-api/unicode.rst:611 +msgid "" +"This function checks that *unicode* is a Unicode object, that the index is " +"not out of bounds, and that the object can be modified safely (i.e. that it " +"its reference count is one)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:620 +msgid "" +"Read a character from a string. This function checks that *unicode* is a " +"Unicode object and the index is not out of bounds, in contrast to the macro " +"version :c:func:`PyUnicode_READ_CHAR`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:630 +msgid "" +"Return a substring of *str*, from character index *start* (included) to " +"character index *end* (excluded). Negative indices are not supported." +msgstr "" + +#: ../Doc/c-api/unicode.rst:639 +msgid "" +"Copy the string *u* into a UCS4 buffer, including a null character, if " +"*copy_null* is set. Returns *NULL* and sets an exception on error (in " +"particular, a :exc:`SystemError` if *buflen* is smaller than the length of " +"*u*). *buffer* is returned on success." +msgstr "" + +#: ../Doc/c-api/unicode.rst:649 +msgid "" +"Copy the string *u* into a new UCS4 buffer that is allocated using :c:func:" +"`PyMem_Malloc`. If this fails, *NULL* is returned with a :exc:`MemoryError` " +"set. The returned buffer always has an extra null code point appended." +msgstr "" + +#: ../Doc/c-api/unicode.rst:658 +msgid "Deprecated Py_UNICODE APIs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:661 +msgid "Deprecated since version 3.3, will be removed in version 4.0." +msgstr "" + +#: ../Doc/c-api/unicode.rst:662 +msgid "" +"These API functions are deprecated with the implementation of :pep:`393`. " +"Extension modules can continue using them, as they will not be removed in " +"Python 3.x, but need to be aware that their use can now cause performance " +"and memory hits." +msgstr "" + +#: ../Doc/c-api/unicode.rst:669 +msgid "" +"Create a Unicode object from the Py_UNICODE buffer *u* of the given size. " +"*u* may be *NULL* which causes the contents to be undefined. It is the " +"user's responsibility to fill in the needed data. The buffer is copied into " +"the new object." +msgstr "" + +#: ../Doc/c-api/unicode.rst:674 +msgid "" +"If the buffer is not *NULL*, the return value might be a shared object. " +"Therefore, modification of the resulting Unicode object is only allowed when " +"*u* is *NULL*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:678 +msgid "" +"If the buffer is *NULL*, :c:func:`PyUnicode_READY` must be called once the " +"string content has been filled before using any of the access macros such " +"as :c:func:`PyUnicode_KIND`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:682 +msgid "" +"Please migrate to using :c:func:`PyUnicode_FromKindAndData` or :c:func:" +"`PyUnicode_New`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:688 +msgid "" +"Return a read-only pointer to the Unicode object's internal :c:type:" +"`Py_UNICODE` buffer, or *NULL* on error. This will create the :c:type:" +"`Py_UNICODE*` representation of the object if it is not yet available. The " +"buffer is always terminated with an extra null code point. Note that the " +"resulting :c:type:`Py_UNICODE` string may also contain embedded null code " +"points, which would cause the string to be truncated when used in most C " +"functions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:696 +msgid "" +"Please migrate to using :c:func:`PyUnicode_AsUCS4`, :c:func:" +"`PyUnicode_Substring`, :c:func:`PyUnicode_ReadChar` or similar new APIs." +msgstr "" + +#: ../Doc/c-api/unicode.rst:703 +msgid "" +"Create a Unicode object by replacing all decimal digits in :c:type:" +"`Py_UNICODE` buffer of the given *size* by ASCII digits 0--9 according to " +"their decimal value. Return *NULL* if an exception occurs." +msgstr "" + +#: ../Doc/c-api/unicode.rst:710 +msgid "" +"Like :c:func:`PyUnicode_AsUnicode`, but also saves the :c:func:`Py_UNICODE` " +"array length (excluding the extra null terminator) in *size*. Note that the " +"resulting :c:type:`Py_UNICODE*` string may contain embedded null code " +"points, which would cause the string to be truncated when used in most C " +"functions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:721 +msgid "" +"Create a copy of a Unicode string ending with a null code point. Return " +"*NULL* and raise a :exc:`MemoryError` exception on memory allocation " +"failure, otherwise return a new allocated buffer (use :c:func:`PyMem_Free` " +"to free the buffer). Note that the resulting :c:type:`Py_UNICODE*` string " +"may contain embedded null code points, which would cause the string to be " +"truncated when used in most C functions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:730 +msgid "" +"Please migrate to using :c:func:`PyUnicode_AsUCS4Copy` or similar new APIs." +msgstr "" + +#: ../Doc/c-api/unicode.rst:735 +msgid "" +"Return the size of the deprecated :c:type:`Py_UNICODE` representation, in " +"code units (this includes surrogate pairs as 2 units)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:738 +msgid "Please migrate to using :c:func:`PyUnicode_GetLength`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:743 +msgid "" +"Copy an instance of a Unicode subtype to a new true Unicode object if " +"necessary. If *obj* is already a true Unicode object (not a subtype), return " +"the reference with incremented refcount." +msgstr "" + +#: ../Doc/c-api/unicode.rst:747 +msgid "" +"Objects other than Unicode or its subtypes will cause a :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:751 +msgid "Locale Encoding" +msgstr "" + +#: ../Doc/c-api/unicode.rst:753 +msgid "" +"The current locale encoding can be used to decode text from the operating " +"system." +msgstr "" + +#: ../Doc/c-api/unicode.rst:760 +msgid "" +"Decode a string from the current locale encoding. The supported error " +"handlers are ``\"strict\"`` and ``\"surrogateescape\"`` (:pep:`383`). The " +"decoder uses ``\"strict\"`` error handler if *errors* is ``NULL``. *str* " +"must end with a null character but cannot contain embedded null characters." +msgstr "" + +#: ../Doc/c-api/unicode.rst:766 +msgid "" +"Use :c:func:`PyUnicode_DecodeFSDefaultAndSize` to decode a string from :c:" +"data:`Py_FileSystemDefaultEncoding` (the locale encoding read at Python " +"startup)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:772 ../Doc/c-api/unicode.rst:860 +msgid "The :c:func:`Py_DecodeLocale` function." +msgstr "" + +#: ../Doc/c-api/unicode.rst:779 +msgid "" +"Similar to :c:func:`PyUnicode_DecodeLocaleAndSize`, but compute the string " +"length using :c:func:`strlen`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:787 +msgid "" +"Encode a Unicode object to the current locale encoding. The supported error " +"handlers are ``\"strict\"`` and ``\"surrogateescape\"`` (:pep:`383`). The " +"encoder uses ``\"strict\"`` error handler if *errors* is ``NULL``. Return a :" +"class:`bytes` object. *unicode* cannot contain embedded null characters." +msgstr "" + +#: ../Doc/c-api/unicode.rst:793 +msgid "" +"Use :c:func:`PyUnicode_EncodeFSDefault` to encode a string to :c:data:" +"`Py_FileSystemDefaultEncoding` (the locale encoding read at Python startup)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:799 ../Doc/c-api/unicode.rst:896 +msgid "The :c:func:`Py_EncodeLocale` function." +msgstr "" + +#: ../Doc/c-api/unicode.rst:805 +msgid "File System Encoding" +msgstr "" + +#: ../Doc/c-api/unicode.rst:807 +msgid "" +"To encode and decode file names and other environment strings, :c:data:" +"`Py_FileSystemDefaultEncoding` should be used as the encoding, and :c:data:" +"`Py_FileSystemDefaultEncodeErrors` should be used as the error handler (:pep:" +"`383` and :pep:`529`). To encode file names to :class:`bytes` during " +"argument parsing, the ``\"O&\"`` converter should be used, passing :c:func:" +"`PyUnicode_FSConverter` as the conversion function:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:816 +msgid "" +"ParseTuple converter: encode :class:`str` objects -- obtained directly or " +"through the :class:`os.PathLike` interface -- to :class:`bytes` using :c:" +"func:`PyUnicode_EncodeFSDefault`; :class:`bytes` objects are output as-is. " +"*result* must be a :c:type:`PyBytesObject*` which must be released when it " +"is no longer used." +msgstr "" + +#: ../Doc/c-api/unicode.rst:824 ../Doc/c-api/unicode.rst:841 +msgid "Accepts a :term:`path-like object`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:827 +msgid "" +"To decode file names to :class:`str` during argument parsing, the ``\"O&\"`` " +"converter should be used, passing :c:func:`PyUnicode_FSDecoder` as the " +"conversion function:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:833 +msgid "" +"ParseTuple converter: decode :class:`bytes` objects -- obtained either " +"directly or indirectly through the :class:`os.PathLike` interface -- to :" +"class:`str` using :c:func:`PyUnicode_DecodeFSDefaultAndSize`; :class:`str` " +"objects are output as-is. *result* must be a :c:type:`PyUnicodeObject*` " +"which must be released when it is no longer used." +msgstr "" + +#: ../Doc/c-api/unicode.rst:847 +msgid "" +"Decode a string using :c:data:`Py_FileSystemDefaultEncoding` and the :c:data:" +"`Py_FileSystemDefaultEncodeErrors` error handler." +msgstr "" + +#: ../Doc/c-api/unicode.rst:850 ../Doc/c-api/unicode.rst:871 +#: ../Doc/c-api/unicode.rst:887 +msgid "" +"If :c:data:`Py_FileSystemDefaultEncoding` is not set, fall back to the " +"locale encoding." +msgstr "" + +#: ../Doc/c-api/unicode.rst:853 +msgid "" +":c:data:`Py_FileSystemDefaultEncoding` is initialized at startup from the " +"locale encoding and cannot be modified later. If you need to decode a string " +"from the current locale encoding, use :c:func:" +"`PyUnicode_DecodeLocaleAndSize`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:862 ../Doc/c-api/unicode.rst:876 +#: ../Doc/c-api/unicode.rst:900 +msgid "Use :c:data:`Py_FileSystemDefaultEncodeErrors` error handler." +msgstr "" + +#: ../Doc/c-api/unicode.rst:868 +msgid "" +"Decode a null-terminated string using :c:data:`Py_FileSystemDefaultEncoding` " +"and the :c:data:`Py_FileSystemDefaultEncodeErrors` error handler." +msgstr "" + +#: ../Doc/c-api/unicode.rst:874 +msgid "" +"Use :c:func:`PyUnicode_DecodeFSDefaultAndSize` if you know the string length." +msgstr "" + +#: ../Doc/c-api/unicode.rst:882 +msgid "" +"Encode a Unicode object to :c:data:`Py_FileSystemDefaultEncoding` with the :" +"c:data:`Py_FileSystemDefaultEncodeErrors` error handler, and return :class:" +"`bytes`. Note that the resulting :class:`bytes` object may contain null " +"bytes." +msgstr "" + +#: ../Doc/c-api/unicode.rst:890 +msgid "" +":c:data:`Py_FileSystemDefaultEncoding` is initialized at startup from the " +"locale encoding and cannot be modified later. If you need to encode a string " +"to the current locale encoding, use :c:func:`PyUnicode_EncodeLocale`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:904 +msgid "wchar_t Support" +msgstr "" + +#: ../Doc/c-api/unicode.rst:906 +msgid ":c:type:`wchar_t` support for platforms which support it:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:910 +msgid "" +"Create a Unicode object from the :c:type:`wchar_t` buffer *w* of the given " +"*size*. Passing -1 as the *size* indicates that the function must itself " +"compute the length, using wcslen. Return *NULL* on failure." +msgstr "" + +#: ../Doc/c-api/unicode.rst:918 +msgid "" +"Copy the Unicode object contents into the :c:type:`wchar_t` buffer *w*. At " +"most *size* :c:type:`wchar_t` characters are copied (excluding a possibly " +"trailing null termination character). Return the number of :c:type:" +"`wchar_t` characters copied or -1 in case of an error. Note that the " +"resulting :c:type:`wchar_t*` string may or may not be null-terminated. It " +"is the responsibility of the caller to make sure that the :c:type:`wchar_t*` " +"string is null-terminated in case this is required by the application. Also, " +"note that the :c:type:`wchar_t*` string might contain null characters, which " +"would cause the string to be truncated when used with most C functions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:931 +msgid "" +"Convert the Unicode object to a wide character string. The output string " +"always ends with a null character. If *size* is not *NULL*, write the number " +"of wide characters (excluding the trailing null termination character) into *" +"\\*size*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:936 +msgid "" +"Returns a buffer allocated by :c:func:`PyMem_Alloc` (use :c:func:" +"`PyMem_Free` to free it) on success. On error, returns *NULL*, *\\*size* is " +"undefined and raises a :exc:`MemoryError`. Note that the resulting :c:type:" +"`wchar_t` string might contain null characters, which would cause the string " +"to be truncated when used with most C functions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:946 +msgid "UCS4 Support" +msgstr "" + +#: ../Doc/c-api/unicode.rst:961 +msgid "" +"These utility functions work on strings of :c:type:`Py_UCS4` characters and " +"otherwise behave like the C standard library functions with the same name." +msgstr "" + +#: ../Doc/c-api/unicode.rst:968 +msgid "Built-in Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:970 +msgid "" +"Python provides a set of built-in codecs which are written in C for speed. " +"All of these codecs are directly usable via the following functions." +msgstr "" + +#: ../Doc/c-api/unicode.rst:973 +msgid "" +"Many of the following APIs take two arguments encoding and errors, and they " +"have the same semantics as the ones of the built-in :func:`str` string " +"object constructor." +msgstr "" + +#: ../Doc/c-api/unicode.rst:977 +msgid "" +"Setting encoding to *NULL* causes the default encoding to be used which is " +"ASCII. The file system calls should use :c:func:`PyUnicode_FSConverter` for " +"encoding file names. This uses the variable :c:data:" +"`Py_FileSystemDefaultEncoding` internally. This variable should be treated " +"as read-only: on some systems, it will be a pointer to a static string, on " +"others, it will change at run-time (such as when the application invokes " +"setlocale)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:985 +msgid "" +"Error handling is set by errors which may also be set to *NULL* meaning to " +"use the default handling defined for the codec. Default error handling for " +"all built-in codecs is \"strict\" (:exc:`ValueError` is raised)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:989 +msgid "" +"The codecs all use a similar interface. Only deviation from the following " +"generic ones are documented for simplicity." +msgstr "" + +#: ../Doc/c-api/unicode.rst:994 +msgid "Generic Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:996 +msgid "These are the generic codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1002 +msgid "" +"Create a Unicode object by decoding *size* bytes of the encoded string *s*. " +"*encoding* and *errors* have the same meaning as the parameters of the same " +"name in the :func:`str` built-in function. The codec to be used is looked " +"up using the Python codec registry. Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1012 +msgid "" +"Encode a Unicode object and return the result as Python bytes object. " +"*encoding* and *errors* have the same meaning as the parameters of the same " +"name in the Unicode :meth:`~str.encode` method. The codec to be used is " +"looked up using the Python codec registry. Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1022 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer *s* of the given *size* and return a " +"Python bytes object. *encoding* and *errors* have the same meaning as the " +"parameters of the same name in the Unicode :meth:`~str.encode` method. The " +"codec to be used is looked up using the Python codec registry. Return " +"*NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1030 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using " +"PyUnicode_AsEncodedString()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1030 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsEncodedString`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1034 +msgid "UTF-8 Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1036 +msgid "These are the UTF-8 codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1041 +msgid "" +"Create a Unicode object by decoding *size* bytes of the UTF-8 encoded string " +"*s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1048 +msgid "" +"If *consumed* is *NULL*, behave like :c:func:`PyUnicode_DecodeUTF8`. If " +"*consumed* is not *NULL*, trailing incomplete UTF-8 byte sequences will not " +"be treated as an error. Those bytes will not be decoded and the number of " +"bytes that have been decoded will be stored in *consumed*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1056 +msgid "" +"Encode a Unicode object using UTF-8 and return the result as Python bytes " +"object. Error handling is \"strict\". Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1063 +msgid "" +"Return a pointer to the UTF-8 encoding of the Unicode object, and store the " +"size of the encoded representation (in bytes) in *size*. The *size* " +"argument can be *NULL*; in this case no size will be stored. The returned " +"buffer always has an extra null byte appended (not included in *size*), " +"regardless of whether there are any other null code points." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1069 +msgid "" +"In the case of an error, *NULL* is returned with an exception set and no " +"*size* is stored." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1072 +msgid "" +"This caches the UTF-8 representation of the string in the Unicode object, " +"and subsequent calls will return a pointer to the same buffer. The caller " +"is not responsible for deallocating the buffer." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1081 +msgid "As :c:func:`PyUnicode_AsUTF8AndSize`, but does not store the size." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1088 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer *s* of the given *size* using UTF-8 " +"and return a Python bytes object. Return *NULL* if an exception was raised " +"by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1094 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyUnicode_AsUTF8String() " +"or PyUnicode_AsUTF8AndSize()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1094 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsUTF8String` or :c:func:`PyUnicode_AsUTF8AndSize`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1098 +msgid "UTF-32 Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1100 +msgid "These are the UTF-32 codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1106 +msgid "" +"Decode *size* bytes from a UTF-32 encoded buffer string and return the " +"corresponding Unicode object. *errors* (if non-*NULL*) defines the error " +"handling. It defaults to \"strict\"." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1110 ../Doc/c-api/unicode.rst:1183 +msgid "" +"If *byteorder* is non-*NULL*, the decoder starts decoding using the given " +"byte order::" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1117 +msgid "" +"If ``*byteorder`` is zero, and the first four bytes of the input data are a " +"byte order mark (BOM), the decoder switches to this byte order and the BOM " +"is not copied into the resulting Unicode string. If ``*byteorder`` is " +"``-1`` or ``1``, any byte order mark is copied to the output." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1122 ../Doc/c-api/unicode.rst:1196 +msgid "" +"After completion, *\\*byteorder* is set to the current byte order at the end " +"of input data." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1125 ../Doc/c-api/unicode.rst:1199 +msgid "If *byteorder* is *NULL*, the codec starts in native order mode." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1127 ../Doc/c-api/unicode.rst:1163 +#: ../Doc/c-api/unicode.rst:1201 ../Doc/c-api/unicode.rst:1238 +msgid "Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1133 +msgid "" +"If *consumed* is *NULL*, behave like :c:func:`PyUnicode_DecodeUTF32`. If " +"*consumed* is not *NULL*, :c:func:`PyUnicode_DecodeUTF32Stateful` will not " +"treat trailing incomplete UTF-32 byte sequences (such as a number of bytes " +"not divisible by four) as an error. Those bytes will not be decoded and the " +"number of bytes that have been decoded will be stored in *consumed*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1142 +msgid "" +"Return a Python byte string using the UTF-32 encoding in native byte order. " +"The string always starts with a BOM mark. Error handling is \"strict\". " +"Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1150 +msgid "" +"Return a Python bytes object holding the UTF-32 encoded value of the Unicode " +"data in *s*. Output is written according to the following byte order::" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1157 ../Doc/c-api/unicode.rst:1231 +msgid "" +"If byteorder is ``0``, the output string will always start with the Unicode " +"BOM mark (U+FEFF). In the other two modes, no BOM mark is prepended." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1160 +msgid "" +"If *Py_UNICODE_WIDE* is not defined, surrogate pairs will be output as a " +"single code point." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1167 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyUnicode_AsUTF32String()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1167 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsUTF32String`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1171 +msgid "UTF-16 Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1173 +msgid "These are the UTF-16 codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1179 +msgid "" +"Decode *size* bytes from a UTF-16 encoded buffer string and return the " +"corresponding Unicode object. *errors* (if non-*NULL*) defines the error " +"handling. It defaults to \"strict\"." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1190 +msgid "" +"If ``*byteorder`` is zero, and the first two bytes of the input data are a " +"byte order mark (BOM), the decoder switches to this byte order and the BOM " +"is not copied into the resulting Unicode string. If ``*byteorder`` is " +"``-1`` or ``1``, any byte order mark is copied to the output (where it will " +"result in either a ``\\ufeff`` or a ``\\ufffe`` character)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1207 +msgid "" +"If *consumed* is *NULL*, behave like :c:func:`PyUnicode_DecodeUTF16`. If " +"*consumed* is not *NULL*, :c:func:`PyUnicode_DecodeUTF16Stateful` will not " +"treat trailing incomplete UTF-16 byte sequences (such as an odd number of " +"bytes or a split surrogate pair) as an error. Those bytes will not be " +"decoded and the number of bytes that have been decoded will be stored in " +"*consumed*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1216 +msgid "" +"Return a Python byte string using the UTF-16 encoding in native byte order. " +"The string always starts with a BOM mark. Error handling is \"strict\". " +"Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1224 +msgid "" +"Return a Python bytes object holding the UTF-16 encoded value of the Unicode " +"data in *s*. Output is written according to the following byte order::" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1234 +msgid "" +"If *Py_UNICODE_WIDE* is defined, a single :c:type:`Py_UNICODE` value may get " +"represented as a surrogate pair. If it is not defined, each :c:type:" +"`Py_UNICODE` values is interpreted as a UCS-2 character." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1242 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyUnicode_AsUTF16String()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1242 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsUTF16String`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1246 +msgid "UTF-7 Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1248 +msgid "These are the UTF-7 codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1253 +msgid "" +"Create a Unicode object by decoding *size* bytes of the UTF-7 encoded string " +"*s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1260 +msgid "" +"If *consumed* is *NULL*, behave like :c:func:`PyUnicode_DecodeUTF7`. If " +"*consumed* is not *NULL*, trailing incomplete UTF-7 base-64 sections will " +"not be treated as an error. Those bytes will not be decoded and the number " +"of bytes that have been decoded will be stored in *consumed*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1269 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given size using UTF-7 and " +"return a Python bytes object. Return *NULL* if an exception was raised by " +"the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1273 +msgid "" +"If *base64SetO* is nonzero, \"Set O\" (punctuation that has no otherwise " +"special meaning) will be encoded in base-64. If *base64WhiteSpace* is " +"nonzero, whitespace will be encoded in base-64. Both are set to zero for " +"the Python \"utf-7\" codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1280 ../Doc/c-api/unicode.rst:1471 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1280 ../Doc/c-api/unicode.rst:1471 +msgid "Part of the old-style :c:type:`Py_UNICODE` API." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1285 +msgid "Unicode-Escape Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1287 +msgid "These are the \"Unicode Escape\" codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1293 +msgid "" +"Create a Unicode object by decoding *size* bytes of the Unicode-Escape " +"encoded string *s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1299 +msgid "" +"Encode a Unicode object using Unicode-Escape and return the result as Python " +"string object. Error handling is \"strict\". Return *NULL* if an exception " +"was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1306 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given *size* using Unicode-" +"Escape and return a Python string object. Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1312 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using " +"PyUnicode_AsUnicodeEscapeString()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1312 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsUnicodeEscapeString`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1316 +msgid "Raw-Unicode-Escape Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1318 +msgid "These are the \"Raw Unicode Escape\" codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1324 +msgid "" +"Create a Unicode object by decoding *size* bytes of the Raw-Unicode-Escape " +"encoded string *s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1330 +msgid "" +"Encode a Unicode object using Raw-Unicode-Escape and return the result as " +"Python string object. Error handling is \"strict\". Return *NULL* if an " +"exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1338 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given *size* using Raw-Unicode-" +"Escape and return a Python string object. Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1344 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using " +"PyUnicode_AsRawUnicodeEscapeString()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1344 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsRawUnicodeEscapeString`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1348 +msgid "Latin-1 Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1350 +msgid "" +"These are the Latin-1 codec APIs: Latin-1 corresponds to the first 256 " +"Unicode ordinals and only these are accepted by the codecs during encoding." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1356 +msgid "" +"Create a Unicode object by decoding *size* bytes of the Latin-1 encoded " +"string *s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1362 +msgid "" +"Encode a Unicode object using Latin-1 and return the result as Python bytes " +"object. Error handling is \"strict\". Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1369 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given *size* using Latin-1 and " +"return a Python bytes object. Return *NULL* if an exception was raised by " +"the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1375 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyUnicode_AsLatin1String()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1375 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsLatin1String`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1379 +msgid "ASCII Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1381 +msgid "" +"These are the ASCII codec APIs. Only 7-bit ASCII data is accepted. All " +"other codes generate errors." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1387 +msgid "" +"Create a Unicode object by decoding *size* bytes of the ASCII encoded string " +"*s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1393 +msgid "" +"Encode a Unicode object using ASCII and return the result as Python bytes " +"object. Error handling is \"strict\". Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1400 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given *size* using ASCII and " +"return a Python bytes object. Return *NULL* if an exception was raised by " +"the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1406 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyUnicode_AsASCIIString()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1406 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsASCIIString`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1410 +msgid "Character Map Codecs" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1412 +msgid "" +"This codec is special in that it can be used to implement many different " +"codecs (and this is in fact what was done to obtain most of the standard " +"codecs included in the :mod:`encodings` package). The codec uses mapping to " +"encode and decode characters." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1417 +msgid "" +"Decoding mappings must map single string characters to single Unicode " +"characters, integers (which are then interpreted as Unicode ordinals) or " +"None (meaning \"undefined mapping\" and causing an error)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1421 +msgid "" +"Encoding mappings must map single Unicode characters to single string " +"characters, integers (which are then interpreted as Latin-1 ordinals) or " +"None (meaning \"undefined mapping\" and causing an error)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1425 +msgid "" +"The mapping objects provided must only support the __getitem__ mapping " +"interface." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1428 +msgid "" +"If a character lookup fails with a LookupError, the character is copied as-" +"is meaning that its ordinal value will be interpreted as Unicode or Latin-1 " +"ordinal resp. Because of this, mappings only need to contain those mappings " +"which map characters to different code points." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1433 +msgid "These are the mapping codec APIs:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1438 +msgid "" +"Create a Unicode object by decoding *size* bytes of the encoded string *s* " +"using the given *mapping* object. Return *NULL* if an exception was raised " +"by the codec. If *mapping* is *NULL* latin-1 decoding will be done. Else it " +"can be a dictionary mapping byte or a unicode string, which is treated as a " +"lookup table. Byte values greater that the length of the string and U+FFFE " +"\"characters\" are treated as \"undefined mapping\"." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1448 +msgid "" +"Encode a Unicode object using the given *mapping* object and return the " +"result as Python string object. Error handling is \"strict\". Return " +"*NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1452 +msgid "The following codec API is special in that maps Unicode to Unicode." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1458 +msgid "" +"Translate a :c:type:`Py_UNICODE` buffer of the given *size* by applying a " +"character mapping *table* to it and return the resulting Unicode object. " +"Return *NULL* when an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1462 +msgid "" +"The *mapping* table must map Unicode ordinal integers to Unicode ordinal " +"integers or None (causing deletion of the character)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1465 ../Doc/c-api/unicode.rst:1582 +msgid "" +"Mapping tables need only provide the :meth:`__getitem__` interface; " +"dictionaries and sequences work well. Unmapped character ordinals (ones " +"which cause a :exc:`LookupError`) are left untouched and are copied as-is." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1478 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given *size* using the given " +"*mapping* object and return a Python string object. Return *NULL* if an " +"exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1484 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using " +"PyUnicode_AsCharmapString()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1484 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsCharmapString`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1488 +msgid "MBCS codecs for Windows" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1490 +msgid "" +"These are the MBCS codec APIs. They are currently only available on Windows " +"and use the Win32 MBCS converters to implement the conversions. Note that " +"MBCS (or DBCS) is a class of encodings, not just one. The target encoding " +"is defined by the user settings on the machine running the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1497 +msgid "" +"Create a Unicode object by decoding *size* bytes of the MBCS encoded string " +"*s*. Return *NULL* if an exception was raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1504 +msgid "" +"If *consumed* is *NULL*, behave like :c:func:`PyUnicode_DecodeMBCS`. If " +"*consumed* is not *NULL*, :c:func:`PyUnicode_DecodeMBCSStateful` will not " +"decode trailing lead byte and the number of bytes that have been decoded " +"will be stored in *consumed*." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1512 +msgid "" +"Encode a Unicode object using MBCS and return the result as Python bytes " +"object. Error handling is \"strict\". Return *NULL* if an exception was " +"raised by the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1519 +msgid "" +"Encode the Unicode object using the specified code page and return a Python " +"bytes object. Return *NULL* if an exception was raised by the codec. Use :c:" +"data:`CP_ACP` code page to get the MBCS encoder." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1528 +msgid "" +"Encode the :c:type:`Py_UNICODE` buffer of the given *size* using MBCS and " +"return a Python bytes object. Return *NULL* if an exception was raised by " +"the codec." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1534 +msgid "" +"Deprecated since version 3.3, will be removed in version 4.0: Part of the " +"old-style Py_UNICODE API; please migrate to using PyUnicode_AsMBCSString() " +"or PyUnicode_EncodeCodePage()." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1534 +msgid "" +"Part of the old-style :c:type:`Py_UNICODE` API; please migrate to using :c:" +"func:`PyUnicode_AsMBCSString` or :c:func:`PyUnicode_EncodeCodePage`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1538 +msgid "Methods & Slots" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1544 +msgid "Methods and Slot Functions" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1546 +msgid "" +"The following APIs are capable of handling Unicode objects and strings on " +"input (we refer to them as strings in the descriptions) and return Unicode " +"objects or integers as appropriate." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1550 +msgid "They all return *NULL* or ``-1`` if an exception occurs." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1555 +msgid "Concat two strings giving a new Unicode string." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1560 +msgid "" +"Split a string giving a list of Unicode strings. If *sep* is *NULL*, " +"splitting will be done at all whitespace substrings. Otherwise, splits " +"occur at the given separator. At most *maxsplit* splits will be done. If " +"negative, no limit is set. Separators are not included in the resulting " +"list." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1568 +msgid "" +"Split a Unicode string at line breaks, returning a list of Unicode strings. " +"CRLF is considered to be one line break. If *keepend* is 0, the Line break " +"characters are not included in the resulting strings." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1576 +msgid "" +"Translate a string by applying a character mapping table to it and return " +"the resulting Unicode object." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1579 +msgid "" +"The mapping table must map Unicode ordinal integers to Unicode ordinal " +"integers or None (causing deletion of the character)." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1586 +msgid "" +"*errors* has the usual meaning for codecs. It may be *NULL* which indicates " +"to use the default error handling." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1592 +msgid "" +"Join a sequence of strings using the given *separator* and return the " +"resulting Unicode string." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1599 +msgid "" +"Return 1 if *substr* matches ``str[start:end]`` at the given tail end " +"(*direction* == -1 means to do a prefix match, *direction* == 1 a suffix " +"match), 0 otherwise. Return ``-1`` if an error occurred." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1607 +msgid "" +"Return the first position of *substr* in ``str[start:end]`` using the given " +"*direction* (*direction* == 1 means to do a forward search, *direction* == " +"-1 a backward search). The return value is the index of the first match; a " +"value of ``-1`` indicates that no match was found, and ``-2`` indicates that " +"an error occurred and an exception has been set." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1617 +msgid "" +"Return the first position of the character *ch* in ``str[start:end]`` using " +"the given *direction* (*direction* == 1 means to do a forward search, " +"*direction* == -1 a backward search). The return value is the index of the " +"first match; a value of ``-1`` indicates that no match was found, and ``-2`` " +"indicates that an error occurred and an exception has been set." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1629 +msgid "" +"Return the number of non-overlapping occurrences of *substr* in ``str[start:" +"end]``. Return ``-1`` if an error occurred." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1636 +msgid "" +"Replace at most *maxcount* occurrences of *substr* in *str* with *replstr* " +"and return the resulting Unicode object. *maxcount* == -1 means replace all " +"occurrences." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1643 +msgid "" +"Compare two strings and return -1, 0, 1 for less than, equal, and greater " +"than, respectively." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1649 +msgid "" +"Compare a unicode object, *uni*, with *string* and return -1, 0, 1 for less " +"than, equal, and greater than, respectively. It is best to pass only ASCII-" +"encoded strings, but the function interprets the input string as ISO-8859-1 " +"if it contains non-ASCII characters." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1657 +msgid "Rich compare two unicode strings and return one of the following:" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1659 +msgid "``NULL`` in case an exception was raised" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1660 +msgid ":const:`Py_True` or :const:`Py_False` for successful comparisons" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1661 +msgid ":const:`Py_NotImplemented` in case the type combination is unknown" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1663 +msgid "" +"Note that :const:`Py_EQ` and :const:`Py_NE` comparisons can cause a :exc:" +"`UnicodeWarning` in case the conversion of the arguments to Unicode fails " +"with a :exc:`UnicodeDecodeError`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1667 +msgid "" +"Possible values for *op* are :const:`Py_GT`, :const:`Py_GE`, :const:" +"`Py_EQ`, :const:`Py_NE`, :const:`Py_LT`, and :const:`Py_LE`." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1673 +msgid "" +"Return a new string object from *format* and *args*; this is analogous to " +"``format % args``." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1679 +msgid "" +"Check whether *element* is contained in *container* and return true or false " +"accordingly." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1682 +msgid "" +"*element* has to coerce to a one element Unicode string. ``-1`` is returned " +"if there was an error." +msgstr "" + +#: ../Doc/c-api/unicode.rst:1688 +msgid "" +"Intern the argument *\\*string* in place. The argument must be the address " +"of a pointer variable pointing to a Python unicode string object. If there " +"is an existing interned string that is the same as *\\*string*, it sets *" +"\\*string* to it (decrementing the reference count of the old string object " +"and incrementing the reference count of the interned string object), " +"otherwise it leaves *\\*string* alone and interns it (incrementing its " +"reference count). (Clarification: even though there is a lot of talk about " +"reference counts, think of this function as reference-count-neutral; you own " +"the object after the call if and only if you owned it before the call.)" +msgstr "" + +#: ../Doc/c-api/unicode.rst:1701 +msgid "" +"A combination of :c:func:`PyUnicode_FromString` and :c:func:" +"`PyUnicode_InternInPlace`, returning either a new unicode string object that " +"has been interned, or a new (\"owned\") reference to an earlier interned " +"string object with the same value." +msgstr "" + +#: ../Doc/c-api/utilities.rst:7 +msgid "Utilities" +msgstr "" + +#: ../Doc/c-api/utilities.rst:9 +msgid "" +"The functions in this chapter perform various utility tasks, ranging from " +"helping C code be more portable across platforms, using Python modules from " +"C, and parsing function arguments and constructing Python values from C " +"values." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:8 +msgid "The Very High Level Layer" +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:10 +msgid "" +"The functions in this chapter will let you execute Python source code given " +"in a file or a buffer, but they will not let you interact in a more detailed " +"way with the interpreter." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:14 +msgid "" +"Several of these functions accept a start symbol from the grammar as a " +"parameter. The available start symbols are :const:`Py_eval_input`, :const:" +"`Py_file_input`, and :const:`Py_single_input`. These are described " +"following the functions which accept them as parameters." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:19 +msgid "" +"Note also that several of these functions take :c:type:`FILE\\*` " +"parameters. One particular issue which needs to be handled carefully is " +"that the :c:type:`FILE` structure for different C libraries can be different " +"and incompatible. Under Windows (at least), it is possible for dynamically " +"linked extensions to actually use different libraries, so care should be " +"taken that :c:type:`FILE\\*` parameters are only passed to these functions " +"if it is certain that they were created by the same library that the Python " +"runtime is using." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:30 +msgid "" +"The main program for the standard interpreter. This is made available for " +"programs which embed Python. The *argc* and *argv* parameters should be " +"prepared exactly as those which are passed to a C program's :c:func:`main` " +"function (converted to wchar_t according to the user's locale). It is " +"important to note that the argument list may be modified (but the contents " +"of the strings pointed to by the argument list are not). The return value " +"will be ``0`` if the interpreter exits normally (i.e., without an " +"exception), ``1`` if the interpreter exits due to an exception, or ``2`` if " +"the parameter list does not represent a valid Python command line." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:40 +msgid "" +"Note that if an otherwise unhandled :exc:`SystemExit` is raised, this " +"function will not return ``1``, but exit the process, as long as " +"``Py_InspectFlag`` is not set." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:47 +msgid "" +"This is a simplified interface to :c:func:`PyRun_AnyFileExFlags` below, " +"leaving *closeit* set to ``0`` and *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:53 +msgid "" +"This is a simplified interface to :c:func:`PyRun_AnyFileExFlags` below, " +"leaving the *closeit* argument set to ``0``." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:59 +msgid "" +"This is a simplified interface to :c:func:`PyRun_AnyFileExFlags` below, " +"leaving the *flags* argument set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:65 +msgid "" +"If *fp* refers to a file associated with an interactive device (console or " +"terminal input or Unix pseudo-terminal), return the value of :c:func:" +"`PyRun_InteractiveLoop`, otherwise return the result of :c:func:" +"`PyRun_SimpleFile`. *filename* is decoded from the filesystem encoding (:" +"func:`sys.getfilesystemencoding`). If *filename* is *NULL*, this function " +"uses ``\"???\"`` as the filename." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:75 +msgid "" +"This is a simplified interface to :c:func:`PyRun_SimpleStringFlags` below, " +"leaving the *PyCompilerFlags\\** argument set to NULL." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:81 +msgid "" +"Executes the Python source code from *command* in the :mod:`__main__` module " +"according to the *flags* argument. If :mod:`__main__` does not already " +"exist, it is created. Returns ``0`` on success or ``-1`` if an exception " +"was raised. If there was an error, there is no way to get the exception " +"information. For the meaning of *flags*, see below." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:87 +msgid "" +"Note that if an otherwise unhandled :exc:`SystemExit` is raised, this " +"function will not return ``-1``, but exit the process, as long as " +"``Py_InspectFlag`` is not set." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:94 +msgid "" +"This is a simplified interface to :c:func:`PyRun_SimpleFileExFlags` below, " +"leaving *closeit* set to ``0`` and *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:100 +msgid "" +"This is a simplified interface to :c:func:`PyRun_SimpleFileExFlags` below, " +"leaving *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:106 +msgid "" +"Similar to :c:func:`PyRun_SimpleStringFlags`, but the Python source code is " +"read from *fp* instead of an in-memory string. *filename* should be the name " +"of the file, it is decoded from the filesystem encoding (:func:`sys." +"getfilesystemencoding`). If *closeit* is true, the file is closed before " +"PyRun_SimpleFileExFlags returns." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:115 +msgid "" +"This is a simplified interface to :c:func:`PyRun_InteractiveOneFlags` below, " +"leaving *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:121 +msgid "" +"Read and execute a single statement from a file associated with an " +"interactive device according to the *flags* argument. The user will be " +"prompted using ``sys.ps1`` and ``sys.ps2``. *filename* is decoded from the " +"filesystem encoding (:func:`sys.getfilesystemencoding`)." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:126 +msgid "" +"Returns ``0`` when the input was executed successfully, ``-1`` if there was " +"an exception, or an error code from the :file:`errcode.h` include file " +"distributed as part of Python if there was a parse error. (Note that :file:" +"`errcode.h` is not included by :file:`Python.h`, so must be included " +"specifically if needed.)" +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:135 +msgid "" +"This is a simplified interface to :c:func:`PyRun_InteractiveLoopFlags` " +"below, leaving *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:141 +msgid "" +"Read and execute statements from a file associated with an interactive " +"device until EOF is reached. The user will be prompted using ``sys.ps1`` " +"and ``sys.ps2``. *filename* is decoded from the filesystem encoding (:func:" +"`sys.getfilesystemencoding`). Returns ``0`` at EOF." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:149 +msgid "" +"Can be set to point to a function with the prototype ``int func(void)``. " +"The function will be called when Python's interpreter prompt is about to " +"become idle and wait for user input from the terminal. The return value is " +"ignored. Overriding this hook can be used to integrate the interpreter's " +"prompt with other event loops, as done in the :file:`Modules/_tkinter.c` in " +"the Python source code." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:160 +msgid "" +"Can be set to point to a function with the prototype ``char *func(FILE " +"*stdin, FILE *stdout, char *prompt)``, overriding the default function used " +"to read a single line of input at the interpreter's prompt. The function is " +"expected to output the string *prompt* if it's not *NULL*, and then read a " +"line of input from the provided standard input file, returning the resulting " +"string. For example, The :mod:`readline` module sets this hook to provide " +"line-editing and tab-completion features." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:169 +msgid "" +"The result must be a string allocated by :c:func:`PyMem_RawMalloc` or :c:" +"func:`PyMem_RawRealloc`, or *NULL* if an error occurred." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:172 +msgid "" +"The result must be allocated by :c:func:`PyMem_RawMalloc` or :c:func:" +"`PyMem_RawRealloc`, instead of being allocated by :c:func:`PyMem_Malloc` or :" +"c:func:`PyMem_Realloc`." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:180 +msgid "" +"This is a simplified interface to :c:func:" +"`PyParser_SimpleParseStringFlagsFilename` below, leaving *filename* set to " +"*NULL* and *flags* set to ``0``." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:187 +msgid "" +"This is a simplified interface to :c:func:" +"`PyParser_SimpleParseStringFlagsFilename` below, leaving *filename* set to " +"*NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:194 +msgid "" +"Parse Python source code from *str* using the start token *start* according " +"to the *flags* argument. The result can be used to create a code object " +"which can be evaluated efficiently. This is useful if a code fragment must " +"be evaluated many times. *filename* is decoded from the filesystem encoding " +"(:func:`sys.getfilesystemencoding`)." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:203 +msgid "" +"This is a simplified interface to :c:func:`PyParser_SimpleParseFileFlags` " +"below, leaving *flags* set to ``0``." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:209 +msgid "" +"Similar to :c:func:`PyParser_SimpleParseStringFlagsFilename`, but the Python " +"source code is read from *fp* instead of an in-memory string." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:215 +msgid "" +"This is a simplified interface to :c:func:`PyRun_StringFlags` below, leaving " +"*flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:221 +msgid "" +"Execute Python source code from *str* in the context specified by the " +"objects *globals* and *locals* with the compiler flags specified by " +"*flags*. *globals* must be a dictionary; *locals* can be any object that " +"implements the mapping protocol. The parameter *start* specifies the start " +"token that should be used to parse the source code." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:227 +msgid "" +"Returns the result of executing the code as a Python object, or *NULL* if an " +"exception was raised." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:233 +msgid "" +"This is a simplified interface to :c:func:`PyRun_FileExFlags` below, leaving " +"*closeit* set to ``0`` and *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:239 +msgid "" +"This is a simplified interface to :c:func:`PyRun_FileExFlags` below, leaving " +"*flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:245 +msgid "" +"This is a simplified interface to :c:func:`PyRun_FileExFlags` below, leaving " +"*closeit* set to ``0``." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:251 +msgid "" +"Similar to :c:func:`PyRun_StringFlags`, but the Python source code is read " +"from *fp* instead of an in-memory string. *filename* should be the name of " +"the file, it is decoded from the filesystem encoding (:func:`sys." +"getfilesystemencoding`). If *closeit* is true, the file is closed before :c:" +"func:`PyRun_FileExFlags` returns." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:260 +msgid "" +"This is a simplified interface to :c:func:`Py_CompileStringFlags` below, " +"leaving *flags* set to *NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:266 +msgid "" +"This is a simplified interface to :c:func:`Py_CompileStringExFlags` below, " +"with *optimize* set to ``-1``." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:272 +msgid "" +"Parse and compile the Python source code in *str*, returning the resulting " +"code object. The start token is given by *start*; this can be used to " +"constrain the code which can be compiled and should be :const:" +"`Py_eval_input`, :const:`Py_file_input`, or :const:`Py_single_input`. The " +"filename specified by *filename* is used to construct the code object and " +"may appear in tracebacks or :exc:`SyntaxError` exception messages. This " +"returns *NULL* if the code cannot be parsed or compiled." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:280 +msgid "" +"The integer *optimize* specifies the optimization level of the compiler; a " +"value of ``-1`` selects the optimization level of the interpreter as given " +"by :option:`-O` options. Explicit levels are ``0`` (no optimization; " +"``__debug__`` is true), ``1`` (asserts are removed, ``__debug__`` is false) " +"or ``2`` (docstrings are removed too)." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:291 +msgid "" +"Like :c:func:`Py_CompileStringObject`, but *filename* is a byte string " +"decoded from the filesystem encoding (:func:`os.fsdecode`)." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:298 +msgid "" +"This is a simplified interface to :c:func:`PyEval_EvalCodeEx`, with just the " +"code object, and global and local variables. The other arguments are set to " +"*NULL*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:305 +msgid "" +"Evaluate a precompiled code object, given a particular environment for its " +"evaluation. This environment consists of a dictionary of global variables, " +"a mapping object of local variables, arrays of arguments, keywords and " +"defaults, and a closure tuple of cells." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:313 +msgid "" +"The C structure of the objects used to describe frame objects. The fields of " +"this type are subject to change at any time." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:319 +msgid "" +"Evaluate an execution frame. This is a simplified interface to :c:func:" +"`PyEval_EvalFrameEx`, for backward compatibility." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:325 +msgid "" +"This is the main, unvarnished function of Python interpretation. It is " +"literally 2000 lines long. The code object associated with the execution " +"frame *f* is executed, interpreting bytecode and executing calls as needed. " +"The additional *throwflag* parameter can mostly be ignored - if true, then " +"it causes an exception to immediately be thrown; this is used for the :meth:" +"`~generator.throw` methods of generator objects." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:339 +msgid "" +"This function changes the flags of the current evaluation frame, and returns " +"true on success, false on failure." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:347 +msgid "" +"The start symbol from the Python grammar for isolated expressions; for use " +"with :c:func:`Py_CompileString`." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:355 +msgid "" +"The start symbol from the Python grammar for sequences of statements as read " +"from a file or other source; for use with :c:func:`Py_CompileString`. This " +"is the symbol to use when compiling arbitrarily long Python source code." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:364 +msgid "" +"The start symbol from the Python grammar for a single statement; for use " +"with :c:func:`Py_CompileString`. This is the symbol used for the interactive " +"interpreter loop." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:371 +msgid "" +"This is the structure used to hold compiler flags. In cases where code is " +"only being compiled, it is passed as ``int flags``, and in cases where code " +"is being executed, it is passed as ``PyCompilerFlags *flags``. In this " +"case, ``from __future__ import`` can modify *flags*." +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:376 +msgid "" +"Whenever ``PyCompilerFlags *flags`` is *NULL*, :attr:`cf_flags` is treated " +"as equal to ``0``, and any modification due to ``from __future__ import`` is " +"discarded. ::" +msgstr "" + +#: ../Doc/c-api/veryhigh.rst:387 +msgid "" +"This bit can be set in *flags* to cause division operator ``/`` to be " +"interpreted as \"true division\" according to :pep:`238`." +msgstr "" + +#: ../Doc/c-api/weakref.rst:6 +msgid "Weak Reference Objects" +msgstr "" + +#: ../Doc/c-api/weakref.rst:8 +msgid "" +"Python supports *weak references* as first-class objects. There are two " +"specific object types which directly implement weak references. The first " +"is a simple reference object, and the second acts as a proxy for the " +"original object as much as it can." +msgstr "" + +#: ../Doc/c-api/weakref.rst:16 +msgid "Return true if *ob* is either a reference or proxy object." +msgstr "" + +#: ../Doc/c-api/weakref.rst:21 +msgid "Return true if *ob* is a reference object." +msgstr "" + +#: ../Doc/c-api/weakref.rst:26 +msgid "Return true if *ob* is a proxy object." +msgstr "" + +#: ../Doc/c-api/weakref.rst:31 +msgid "" +"Return a weak reference object for the object *ob*. This will always return " +"a new reference, but is not guaranteed to create a new object; an existing " +"reference object may be returned. The second parameter, *callback*, can be " +"a callable object that receives notification when *ob* is garbage collected; " +"it should accept a single parameter, which will be the weak reference object " +"itself. *callback* may also be ``None`` or *NULL*. If *ob* is not a weakly-" +"referencable object, or if *callback* is not callable, ``None``, or *NULL*, " +"this will return *NULL* and raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/weakref.rst:43 +msgid "" +"Return a weak reference proxy object for the object *ob*. This will always " +"return a new reference, but is not guaranteed to create a new object; an " +"existing proxy object may be returned. The second parameter, *callback*, " +"can be a callable object that receives notification when *ob* is garbage " +"collected; it should accept a single parameter, which will be the weak " +"reference object itself. *callback* may also be ``None`` or *NULL*. If *ob* " +"is not a weakly-referencable object, or if *callback* is not callable, " +"``None``, or *NULL*, this will return *NULL* and raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/c-api/weakref.rst:55 +msgid "" +"Return the referenced object from a weak reference, *ref*. If the referent " +"is no longer live, returns :const:`Py_None`." +msgstr "" + +#: ../Doc/c-api/weakref.rst:60 +msgid "" +"This function returns a **borrowed reference** to the referenced object. " +"This means that you should always call :c:func:`Py_INCREF` on the object " +"except if you know that it cannot be destroyed while you are still using it." +msgstr "" + +#: ../Doc/c-api/weakref.rst:68 +msgid "" +"Similar to :c:func:`PyWeakref_GetObject`, but implemented as a macro that " +"does no error checking." +msgstr "" diff --git a/contents.po b/contents.po new file mode 100644 index 00000000..edd541ff --- /dev/null +++ b/contents.po @@ -0,0 +1,21 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/contents.rst:3 +msgid "Python Documentation contents" +msgstr "" diff --git a/copyright.po b/copyright.po new file mode 100644 index 00000000..39540dc5 --- /dev/null +++ b/copyright.po @@ -0,0 +1,50 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/copyright.rst:3 +msgid "Copyright" +msgstr "" + +#: ../Doc/copyright.rst:5 +msgid "Python and this documentation is:" +msgstr "" + +#: ../Doc/copyright.rst:7 +msgid "Copyright © 2001-2016 Python Software Foundation. All rights reserved." +msgstr "" + +#: ../Doc/copyright.rst:9 +msgid "Copyright © 2000 BeOpen.com. All rights reserved." +msgstr "" + +#: ../Doc/copyright.rst:11 +msgid "" +"Copyright © 1995-2000 Corporation for National Research Initiatives. All " +"rights reserved." +msgstr "" + +#: ../Doc/copyright.rst:14 +msgid "" +"Copyright © 1991-1995 Stichting Mathematisch Centrum. All rights reserved." +msgstr "" + +#: ../Doc/copyright.rst:18 +msgid "" +"See :ref:`history-and-license` for complete license and permissions " +"information." +msgstr "" diff --git a/distributing.po b/distributing.po new file mode 100644 index 00000000..39869e2e --- /dev/null +++ b/distributing.po @@ -0,0 +1,251 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/distributing/index.rst:5 +msgid "Distributing Python Modules" +msgstr "" + +#: ../Doc/distributing/index.rst:7 +msgid "distutils-sig@python.org" +msgstr "" + +#: ../Doc/distributing/index.rst:10 +msgid "" +"As a popular open source development project, Python has an active " +"supporting community of contributors and users that also make their software " +"available for other Python developers to use under open source license terms." +msgstr "" + +#: ../Doc/distributing/index.rst:14 +msgid "" +"This allows Python users to share and collaborate effectively, benefiting " +"from the solutions others have already created to common (and sometimes even " +"rare!) problems, as well as potentially contributing their own solutions to " +"the common pool." +msgstr "" + +#: ../Doc/distributing/index.rst:19 +msgid "" +"This guide covers the distribution part of the process. For a guide to " +"installing other Python projects, refer to the :ref:`installation guide " +"`." +msgstr "" + +#: ../Doc/distributing/index.rst:25 +msgid "" +"For corporate and other institutional users, be aware that many " +"organisations have their own policies around using and contributing to open " +"source software. Please take such policies into account when making use of " +"the distribution and installation tools provided with Python." +msgstr "" + +#: ../Doc/distributing/index.rst:32 +msgid "Key terms" +msgstr "" + +#: ../Doc/distributing/index.rst:34 +msgid "" +"the `Python Packaging Index `__ is a public " +"repository of open source licensed packages made available for use by other " +"Python users" +msgstr "" + +#: ../Doc/distributing/index.rst:37 +msgid "" +"the `Python Packaging Authority `__ are the group of " +"developers and documentation authors responsible for the maintenance and " +"evolution of the standard packaging tools and the associated metadata and " +"file format standards. They maintain a variety of tools, documentation and " +"issue trackers on both `GitHub `__ and `BitBucket " +"`__." +msgstr "" + +#: ../Doc/distributing/index.rst:44 +msgid "" +":mod:`distutils` is the original build and distribution system first added " +"to the Python standard library in 1998. While direct use of :mod:`distutils` " +"is being phased out, it still laid the foundation for the current packaging " +"and distribution infrastructure, and it not only remains part of the " +"standard library, but its name lives on in other ways (such as the name of " +"the mailing list used to coordinate Python packaging standards development)." +msgstr "" + +#: ../Doc/distributing/index.rst:51 +msgid "" +"`setuptools`_ is a (largely) drop-in replacement for :mod:`distutils` first " +"published in 2004. Its most notable addition over the unmodified :mod:" +"`distutils` tools was the ability to declare dependencies on other packages. " +"It is currently recommended as a more regularly updated alternative to :mod:" +"`distutils` that offers consistent support for more recent packaging " +"standards across a wide range of Python versions." +msgstr "" + +#: ../Doc/distributing/index.rst:57 +msgid "" +"`wheel`_ (in this context) is a project that adds the ``bdist_wheel`` " +"command to :mod:`distutils`/`setuptools`_. This produces a cross platform " +"binary packaging format (called \"wheels\" or \"wheel files\" and defined " +"in :pep:`427`) that allows Python libraries, even those including binary " +"extensions, to be installed on a system without needing to be built locally." +msgstr "" + +#: ../Doc/distributing/index.rst:68 +msgid "Open source licensing and collaboration" +msgstr "" + +#: ../Doc/distributing/index.rst:70 +msgid "" +"In most parts of the world, software is automatically covered by copyright. " +"This means that other developers require explicit permission to copy, use, " +"modify and redistribute the software." +msgstr "" + +#: ../Doc/distributing/index.rst:74 +msgid "" +"Open source licensing is a way of explicitly granting such permission in a " +"relatively consistent way, allowing developers to share and collaborate " +"efficiently by making common solutions to various problems freely available. " +"This leaves many developers free to spend more time focusing on the problems " +"that are relatively unique to their specific situation." +msgstr "" + +#: ../Doc/distributing/index.rst:80 +msgid "" +"The distribution tools provided with Python are designed to make it " +"reasonably straightforward for developers to make their own contributions " +"back to that common pool of software if they choose to do so." +msgstr "" + +#: ../Doc/distributing/index.rst:84 +msgid "" +"The same distribution tools can also be used to distribute software within " +"an organisation, regardless of whether that software is published as open " +"source software or not." +msgstr "" + +#: ../Doc/distributing/index.rst:90 +msgid "Installing the tools" +msgstr "" + +#: ../Doc/distributing/index.rst:92 +msgid "" +"The standard library does not include build tools that support modern Python " +"packaging standards, as the core development team has found that it is " +"important to have standard tools that work consistently, even on older " +"versions of Python." +msgstr "" + +#: ../Doc/distributing/index.rst:97 +msgid "" +"The currently recommended build and distribution tools can be installed by " +"invoking the ``pip`` module at the command line::" +msgstr "" + +#: ../Doc/distributing/index.rst:104 +msgid "" +"For POSIX users (including Mac OS X and Linux users), these instructions " +"assume the use of a :term:`virtual environment`." +msgstr "" + +#: ../Doc/distributing/index.rst:107 +msgid "" +"For Windows users, these instructions assume that the option to adjust the " +"system PATH environment variable was selected when installing Python." +msgstr "" + +#: ../Doc/distributing/index.rst:111 +msgid "" +"The Python Packaging User Guide includes more details on the `currently " +"recommended tools`_." +msgstr "" + +#: ../Doc/distributing/index.rst:117 +msgid "Reading the guide" +msgstr "" + +#: ../Doc/distributing/index.rst:119 +msgid "" +"The Python Packaging User Guide covers the various key steps and elements " +"involved in creating a project:" +msgstr "" + +#: ../Doc/distributing/index.rst:122 +msgid "`Project structure`_" +msgstr "" + +#: ../Doc/distributing/index.rst:123 +msgid "`Building and packaging the project`_" +msgstr "" + +#: ../Doc/distributing/index.rst:124 +msgid "`Uploading the project to the Python Packaging Index`_" +msgstr "" + +#: ../Doc/distributing/index.rst:135 +msgid "How do I...?" +msgstr "" + +#: ../Doc/distributing/index.rst:137 +msgid "These are quick answers or links for some common tasks." +msgstr "" + +#: ../Doc/distributing/index.rst:140 +msgid "... choose a name for my project?" +msgstr "" + +#: ../Doc/distributing/index.rst:142 +msgid "This isn't an easy topic, but here are a few tips:" +msgstr "" + +#: ../Doc/distributing/index.rst:144 +msgid "check the Python Packaging Index to see if the name is already in use" +msgstr "" + +#: ../Doc/distributing/index.rst:145 +msgid "" +"check popular hosting sites like GitHub, BitBucket, etc to see if there is " +"already a project with that name" +msgstr "" + +#: ../Doc/distributing/index.rst:147 +msgid "check what comes up in a web search for the name you're considering" +msgstr "" + +#: ../Doc/distributing/index.rst:148 +msgid "" +"avoid particularly common words, especially ones with multiple meanings, as " +"they can make it difficult for users to find your software when searching " +"for it" +msgstr "" + +#: ../Doc/distributing/index.rst:154 +msgid "... create and distribute binary extensions?" +msgstr "" + +#: ../Doc/distributing/index.rst:156 +msgid "" +"This is actually quite a complex topic, with a variety of alternatives " +"available depending on exactly what you're aiming to achieve. See the Python " +"Packaging User Guide for more information and recommendations." +msgstr "" + +#: ../Doc/distributing/index.rst:162 +msgid "" +"`Python Packaging User Guide: Binary Extensions `__" +msgstr "" diff --git a/distutils.po b/distutils.po new file mode 100644 index 00000000..ce127a09 --- /dev/null +++ b/distutils.po @@ -0,0 +1,5781 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/distutils/apiref.rst:5 +msgid "API Reference" +msgstr "" + +#: ../Doc/distutils/apiref.rst:9 +msgid ":mod:`distutils.core` --- Core Distutils functionality" +msgstr "" + +#: ../Doc/distutils/apiref.rst:15 +msgid "" +"The :mod:`distutils.core` module is the only module that needs to be " +"installed to use the Distutils. It provides the :func:`setup` (which is " +"called from the setup script). Indirectly provides the :class:`distutils." +"dist.Distribution` and :class:`distutils.cmd.Command` class." +msgstr "" + +#: ../Doc/distutils/apiref.rst:23 +msgid "" +"The basic do-everything function that does most everything you could ever " +"ask for from a Distutils method." +msgstr "" + +#: ../Doc/distutils/apiref.rst:26 +msgid "" +"The setup function takes a large number of arguments. These are laid out in " +"the following table." +msgstr "" + +#: ../Doc/distutils/apiref.rst:32 ../Doc/distutils/apiref.rst:175 +msgid "argument name" +msgstr "" + +#: ../Doc/distutils/apiref.rst:32 ../Doc/distutils/apiref.rst:133 +#: ../Doc/distutils/apiref.rst:175 +msgid "value" +msgstr "" + +#: ../Doc/distutils/apiref.rst:32 ../Doc/distutils/apiref.rst:175 +msgid "type" +msgstr "" + +#: ../Doc/distutils/apiref.rst:34 ../Doc/distutils/apiref.rst:177 +msgid "*name*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:34 +msgid "The name of the package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:34 ../Doc/distutils/apiref.rst:36 +#: ../Doc/distutils/apiref.rst:40 ../Doc/distutils/apiref.rst:43 +#: ../Doc/distutils/apiref.rst:46 ../Doc/distutils/apiref.rst:48 +#: ../Doc/distutils/apiref.rst:51 ../Doc/distutils/apiref.rst:58 +#: ../Doc/distutils/apiref.rst:62 ../Doc/distutils/apiref.rst:65 +#: ../Doc/distutils/apiref.rst:86 ../Doc/distutils/apiref.rst:96 +#: ../Doc/distutils/apiref.rst:177 ../Doc/distutils/apiref.rst:267 +msgid "a string" +msgstr "" + +#: ../Doc/distutils/apiref.rst:36 +msgid "*version*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:36 +msgid "The version number of the package; see :mod:`distutils.version`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:40 +msgid "*description*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:40 +msgid "A single line describing the package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:43 +msgid "*long_description*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:43 +msgid "Longer description of the package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:46 +msgid "*author*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:46 +msgid "The name of the package author" +msgstr "" + +#: ../Doc/distutils/apiref.rst:48 +msgid "*author_email*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:48 +msgid "The email address of the package author" +msgstr "" + +#: ../Doc/distutils/apiref.rst:51 +msgid "*maintainer*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:51 +msgid "" +"The name of the current maintainer, if different from the author. Note that " +"if the maintainer is provided, distutils will use it as the author in :file:" +"`PKG-INFO`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:58 +msgid "*maintainer_email*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:58 +msgid "" +"The email address of the current maintainer, if different from the author" +msgstr "" + +#: ../Doc/distutils/apiref.rst:62 +msgid "*url*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:62 +msgid "A URL for the package (homepage)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:65 +msgid "*download_url*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:65 +msgid "A URL to download the package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:67 +msgid "*packages*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:67 +msgid "A list of Python packages that distutils will manipulate" +msgstr "" + +#: ../Doc/distutils/apiref.rst:67 ../Doc/distutils/apiref.rst:70 +#: ../Doc/distutils/apiref.rst:73 ../Doc/distutils/apiref.rst:90 +#: ../Doc/distutils/apiref.rst:183 ../Doc/distutils/apiref.rst:196 +#: ../Doc/distutils/apiref.rst:212 ../Doc/distutils/apiref.rst:215 +#: ../Doc/distutils/apiref.rst:219 ../Doc/distutils/apiref.rst:223 +#: ../Doc/distutils/apiref.rst:229 ../Doc/distutils/apiref.rst:236 +#: ../Doc/distutils/apiref.rst:247 ../Doc/distutils/apiref.rst:256 +#: ../Doc/distutils/apiref.rst:264 +msgid "a list of strings" +msgstr "" + +#: ../Doc/distutils/apiref.rst:70 +msgid "*py_modules*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:70 +msgid "A list of Python modules that distutils will manipulate" +msgstr "" + +#: ../Doc/distutils/apiref.rst:73 +msgid "*scripts*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:73 +msgid "A list of standalone script files to be built and installed" +msgstr "" + +#: ../Doc/distutils/apiref.rst:77 +msgid "*ext_modules*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:77 +msgid "A list of Python extensions to be built" +msgstr "" + +#: ../Doc/distutils/apiref.rst:77 +msgid "a list of instances of :class:`distutils.core.Extension`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:80 +msgid "*classifiers*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:80 +msgid "A list of categories for the package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:80 +msgid "" +"a list of strings; valid classifiers are listed on `PyPI `_." +msgstr "" + +#: ../Doc/distutils/apiref.rst:83 +msgid "*distclass*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:83 +msgid "the :class:`Distribution` class to use" +msgstr "" + +#: ../Doc/distutils/apiref.rst:83 +msgid "a subclass of :class:`distutils.core.Distribution`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:86 +msgid "*script_name*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:86 +msgid "The name of the setup.py script - defaults to ``sys.argv[0]``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:90 +msgid "*script_args*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:90 +msgid "Arguments to supply to the setup script" +msgstr "" + +#: ../Doc/distutils/apiref.rst:93 +msgid "*options*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:93 +msgid "default options for the setup script" +msgstr "" + +#: ../Doc/distutils/apiref.rst:93 ../Doc/distutils/apiref.rst:103 +#: ../Doc/distutils/apiref.rst:109 +msgid "a dictionary" +msgstr "" + +#: ../Doc/distutils/apiref.rst:96 +msgid "*license*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:96 +msgid "The license for the package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:98 +msgid "*keywords*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:98 +msgid "Descriptive meta-data, see :pep:`314`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:98 ../Doc/distutils/apiref.rst:101 +msgid "a list of strings or a comma-separated string" +msgstr "" + +#: ../Doc/distutils/apiref.rst:101 +msgid "*platforms*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:103 +msgid "*cmdclass*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:103 +msgid "A mapping of command names to :class:`Command` subclasses" +msgstr "" + +#: ../Doc/distutils/apiref.rst:106 +msgid "*data_files*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:106 +msgid "A list of data files to install" +msgstr "" + +#: ../Doc/distutils/apiref.rst:106 +msgid "a list" +msgstr "" + +#: ../Doc/distutils/apiref.rst:109 +msgid "*package_dir*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:109 +msgid "A mapping of package to directory names" +msgstr "" + +#: ../Doc/distutils/apiref.rst:117 +msgid "" +"Run a setup script in a somewhat controlled environment, and return the :" +"class:`distutils.dist.Distribution` instance that drives things. This is " +"useful if you need to find out the distribution meta-data (passed as " +"keyword args from *script* to :func:`setup`), or the contents of the config " +"files or command-line." +msgstr "" + +#: ../Doc/distutils/apiref.rst:123 +msgid "" +"*script_name* is a file that will be read and run with :func:`exec`. ``sys." +"argv[0]`` will be replaced with *script* for the duration of the call. " +"*script_args* is a list of strings; if supplied, ``sys.argv[1:]`` will be " +"replaced by *script_args* for the duration of the call." +msgstr "" + +#: ../Doc/distutils/apiref.rst:128 +msgid "" +"*stop_after* tells :func:`setup` when to stop processing; possible values:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:133 ../Doc/distutils/apiref.rst:542 +#: ../Doc/distutils/apiref.rst:1566 +msgid "description" +msgstr "" + +#: ../Doc/distutils/apiref.rst:135 +msgid "*init*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:135 +msgid "" +"Stop after the :class:`Distribution` instance has been created and " +"populated with the keyword arguments to :func:`setup`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:139 +msgid "*config*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:139 +msgid "" +"Stop after config files have been parsed (and their data stored in the :" +"class:`Distribution` instance)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:143 +msgid "*commandline*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:143 +msgid "" +"Stop after the command-line (``sys.argv[1:]`` or *script_args*) have been " +"parsed (and the data stored in the :class:`Distribution` instance.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:148 +msgid "*run*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:148 +msgid "" +"Stop after all commands have been run (the same as if :func:`setup` had " +"been called in the usual way). This is the default value." +msgstr "" + +#: ../Doc/distutils/apiref.rst:154 +msgid "" +"In addition, the :mod:`distutils.core` module exposed a number of classes " +"that live elsewhere." +msgstr "" + +#: ../Doc/distutils/apiref.rst:157 +msgid ":class:`~distutils.extension.Extension` from :mod:`distutils.extension`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:159 +msgid ":class:`~distutils.cmd.Command` from :mod:`distutils.cmd`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:161 +msgid ":class:`~distutils.dist.Distribution` from :mod:`distutils.dist`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:163 +msgid "" +"A short description of each of these follows, but see the relevant module " +"for the full reference." +msgstr "" + +#: ../Doc/distutils/apiref.rst:169 +msgid "" +"The Extension class describes a single C or C++extension module in a setup " +"script. It accepts the following keyword arguments in its constructor:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:177 +msgid "" +"the full name of the extension, including any packages --- ie. *not* a " +"filename or pathname, but Python dotted name" +msgstr "" + +#: ../Doc/distutils/apiref.rst:183 +msgid "*sources*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:183 +msgid "" +"list of source filenames, relative to the distribution root (where the setup " +"script lives), in Unix form (slash- separated) for portability. Source files " +"may be C, C++, SWIG (.i), platform-specific resource files, or whatever else " +"is recognized by the :command:`build_ext` command as source for a Python " +"extension." +msgstr "" + +#: ../Doc/distutils/apiref.rst:196 +msgid "*include_dirs*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:196 +msgid "" +"list of directories to search for C/C++ header files (in Unix form for " +"portability)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:200 +msgid "*define_macros*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:200 +msgid "" +"list of macros to define; each macro is defined using a 2-tuple ``(name, " +"value)``, where *value* is either the string to define it to or ``None`` to " +"define it without a particular value (equivalent of ``#define FOO`` in " +"source or :option:`-DFOO` on Unix C compiler command line)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:200 +msgid "a list of tuples" +msgstr "" + +#: ../Doc/distutils/apiref.rst:212 +msgid "*undef_macros*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:212 +msgid "list of macros to undefine explicitly" +msgstr "" + +#: ../Doc/distutils/apiref.rst:215 +msgid "*library_dirs*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:215 +msgid "list of directories to search for C/C++ libraries at link time" +msgstr "" + +#: ../Doc/distutils/apiref.rst:219 +msgid "*libraries*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:219 +msgid "list of library names (not filenames or paths) to link against" +msgstr "" + +#: ../Doc/distutils/apiref.rst:223 +msgid "*runtime_library_dirs*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:223 +msgid "" +"list of directories to search for C/C++ libraries at run time (for shared " +"extensions, this is when the extension is loaded)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:229 +msgid "*extra_objects*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:229 +msgid "" +"list of extra files to link with (eg. object files not implied by 'sources', " +"static library that must be explicitly specified, binary resource files, " +"etc.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:236 +msgid "*extra_compile_args*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:236 +msgid "" +"any extra platform- and compiler-specific information to use when compiling " +"the source files in 'sources'. For platforms and compilers where a command " +"line makes sense, this is typically a list of command-line arguments, but " +"for other platforms it could be anything." +msgstr "" + +#: ../Doc/distutils/apiref.rst:247 +msgid "*extra_link_args*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:247 +msgid "" +"any extra platform- and compiler-specific information to use when linking " +"object files together to create the extension (or to create a new static " +"Python interpreter). Similar interpretation as for 'extra_compile_args'." +msgstr "" + +#: ../Doc/distutils/apiref.rst:256 +msgid "*export_symbols*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:256 +msgid "" +"list of symbols to be exported from a shared extension. Not used on all " +"platforms, and not generally necessary for Python extensions, which " +"typically export exactly one symbol: ``init`` + extension_name." +msgstr "" + +#: ../Doc/distutils/apiref.rst:264 +msgid "*depends*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:264 +msgid "list of files that the extension depends on" +msgstr "" + +#: ../Doc/distutils/apiref.rst:267 +msgid "*language*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:267 +msgid "" +"extension language (i.e. ``'c'``, ``'c++'``, ``'objc'``). Will be detected " +"from the source extensions if not provided." +msgstr "" + +#: ../Doc/distutils/apiref.rst:273 +msgid "*optional*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:273 +msgid "" +"specifies that a build failure in the extension should not abort the build " +"process, but simply skip the extension." +msgstr "" + +#: ../Doc/distutils/apiref.rst:273 +msgid "a boolean" +msgstr "" + +#: ../Doc/distutils/apiref.rst:282 +msgid "" +"A :class:`Distribution` describes how to build, install and package up a " +"Python software package." +msgstr "" + +#: ../Doc/distutils/apiref.rst:285 +msgid "" +"See the :func:`setup` function for a list of keyword arguments accepted by " +"the Distribution constructor. :func:`setup` creates a Distribution instance." +msgstr "" + +#: ../Doc/distutils/apiref.rst:291 +msgid "" +"A :class:`Command` class (or rather, an instance of one of its subclasses) " +"implement a single distutils command." +msgstr "" + +#: ../Doc/distutils/apiref.rst:296 +msgid ":mod:`distutils.ccompiler` --- CCompiler base class" +msgstr "" + +#: ../Doc/distutils/apiref.rst:302 +msgid "" +"This module provides the abstract base class for the :class:`CCompiler` " +"classes. A :class:`CCompiler` instance can be used for all the compile and " +"link steps needed to build a single project. Methods are provided to set " +"options for the compiler --- macro definitions, include directories, link " +"path, libraries and the like." +msgstr "" + +#: ../Doc/distutils/apiref.rst:308 +msgid "This module provides the following functions." +msgstr "" + +#: ../Doc/distutils/apiref.rst:313 +msgid "" +"Generate linker options for searching library directories and linking with " +"specific libraries. *libraries* and *library_dirs* are, respectively, lists " +"of library names (not filenames!) and search directories. Returns a list of " +"command-line options suitable for use with some compiler (depending on the " +"two format strings passed in)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:322 +msgid "" +"Generate C pre-processor options (:option:`-D`, :option:`!-U`, :option:`!-" +"I`) as used by at least two types of compilers: the typical Unix compiler " +"and Visual C++. *macros* is the usual thing, a list of 1- or 2-tuples, where " +"``(name,)`` means undefine (:option:`!-U`) macro *name*, and ``(name, " +"value)`` means define (:option:`-D`) macro *name* to *value*. " +"*include_dirs* is just a list of directory names to be added to the header " +"file search path (:option:`!-I`). Returns a list of command-line options " +"suitable for either Unix compilers or Visual C++." +msgstr "" + +#: ../Doc/distutils/apiref.rst:334 +msgid "Determine the default compiler to use for the given platform." +msgstr "" + +#: ../Doc/distutils/apiref.rst:336 +msgid "" +"*osname* should be one of the standard Python OS names (i.e. the ones " +"returned by ``os.name``) and *platform* the common value returned by ``sys." +"platform`` for the platform in question." +msgstr "" + +#: ../Doc/distutils/apiref.rst:340 +msgid "" +"The default values are ``os.name`` and ``sys.platform`` in case the " +"parameters are not given." +msgstr "" + +#: ../Doc/distutils/apiref.rst:346 +msgid "" +"Factory function to generate an instance of some CCompiler subclass for the " +"supplied platform/compiler combination. *plat* defaults to ``os.name`` (eg. " +"``'posix'``, ``'nt'``), and *compiler* defaults to the default compiler for " +"that platform. Currently only ``'posix'`` and ``'nt'`` are supported, and " +"the default compilers are \"traditional Unix interface\" (:class:" +"`UnixCCompiler` class) and Visual C++ (:class:`MSVCCompiler` class). Note " +"that it's perfectly possible to ask for a Unix compiler object under " +"Windows, and a Microsoft compiler object under Unix---if you supply a value " +"for *compiler*, *plat* is ignored." +msgstr "" + +#: ../Doc/distutils/apiref.rst:362 +msgid "" +"Print list of available compilers (used by the :option:`--help-compiler` " +"options to :command:`build`, :command:`build_ext`, :command:`build_clib`)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:368 +msgid "" +"The abstract base class :class:`CCompiler` defines the interface that must " +"be implemented by real compiler classes. The class also has some utility " +"methods used by several compiler classes." +msgstr "" + +#: ../Doc/distutils/apiref.rst:372 +msgid "" +"The basic idea behind a compiler abstraction class is that each instance can " +"be used for all the compile/link steps in building a single project. Thus, " +"attributes common to all of those compile and link steps --- include " +"directories, macros to define, libraries to link against, etc. --- are " +"attributes of the compiler instance. To allow for variability in how " +"individual files are treated, most of those attributes may be varied on a " +"per-compilation or per-link basis." +msgstr "" + +#: ../Doc/distutils/apiref.rst:380 +msgid "" +"The constructor for each subclass creates an instance of the Compiler " +"object. Flags are *verbose* (show verbose output), *dry_run* (don't actually " +"execute the steps) and *force* (rebuild everything, regardless of " +"dependencies). All of these flags default to ``0`` (off). Note that you " +"probably don't want to instantiate :class:`CCompiler` or one of its " +"subclasses directly - use the :func:`distutils.CCompiler.new_compiler` " +"factory function instead." +msgstr "" + +#: ../Doc/distutils/apiref.rst:387 +msgid "" +"The following methods allow you to manually alter compiler options for the " +"instance of the Compiler class." +msgstr "" + +#: ../Doc/distutils/apiref.rst:393 +msgid "" +"Add *dir* to the list of directories that will be searched for header files. " +"The compiler is instructed to search directories in the order in which they " +"are supplied by successive calls to :meth:`add_include_dir`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:400 +msgid "" +"Set the list of directories that will be searched to *dirs* (a list of " +"strings). Overrides any preceding calls to :meth:`add_include_dir`; " +"subsequent calls to :meth:`add_include_dir` add to the list passed to :meth:" +"`set_include_dirs`. This does not affect any list of standard include " +"directories that the compiler may search by default." +msgstr "" + +#: ../Doc/distutils/apiref.rst:409 +msgid "" +"Add *libname* to the list of libraries that will be included in all links " +"driven by this compiler object. Note that *libname* should \\*not\\* be the " +"name of a file containing a library, but the name of the library itself: the " +"actual filename will be inferred by the linker, the compiler, or the " +"compiler class (depending on the platform)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:415 +msgid "" +"The linker will be instructed to link against libraries in the order they " +"were supplied to :meth:`add_library` and/or :meth:`set_libraries`. It is " +"perfectly valid to duplicate library names; the linker will be instructed to " +"link against libraries as many times as they are mentioned." +msgstr "" + +#: ../Doc/distutils/apiref.rst:423 +msgid "" +"Set the list of libraries to be included in all links driven by this " +"compiler object to *libnames* (a list of strings). This does not affect any " +"standard system libraries that the linker may include by default." +msgstr "" + +#: ../Doc/distutils/apiref.rst:430 +msgid "" +"Add *dir* to the list of directories that will be searched for libraries " +"specified to :meth:`add_library` and :meth:`set_libraries`. The linker will " +"be instructed to search for libraries in the order they are supplied to :" +"meth:`add_library_dir` and/or :meth:`set_library_dirs`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:438 +msgid "" +"Set the list of library search directories to *dirs* (a list of strings). " +"This does not affect any standard library search path that the linker may " +"search by default." +msgstr "" + +#: ../Doc/distutils/apiref.rst:445 +msgid "" +"Add *dir* to the list of directories that will be searched for shared " +"libraries at runtime." +msgstr "" + +#: ../Doc/distutils/apiref.rst:451 +msgid "" +"Set the list of directories to search for shared libraries at runtime to " +"*dirs* (a list of strings). This does not affect any standard search path " +"that the runtime linker may search by default." +msgstr "" + +#: ../Doc/distutils/apiref.rst:458 +msgid "" +"Define a preprocessor macro for all compilations driven by this compiler " +"object. The optional parameter *value* should be a string; if it is not " +"supplied, then the macro will be defined without an explicit value and the " +"exact outcome depends on the compiler used." +msgstr "" + +#: ../Doc/distutils/apiref.rst:468 +msgid "" +"Undefine a preprocessor macro for all compilations driven by this compiler " +"object. If the same macro is defined by :meth:`define_macro` and undefined " +"by :meth:`undefine_macro` the last call takes precedence (including multiple " +"redefinitions or undefinitions). If the macro is redefined/undefined on a " +"per-compilation basis (ie. in the call to :meth:`compile`), then that takes " +"precedence." +msgstr "" + +#: ../Doc/distutils/apiref.rst:478 +msgid "" +"Add *object* to the list of object files (or analogues, such as explicitly " +"named library files or the output of \"resource compilers\") to be included " +"in every link driven by this compiler object." +msgstr "" + +#: ../Doc/distutils/apiref.rst:485 +msgid "" +"Set the list of object files (or analogues) to be included in every link to " +"*objects*. This does not affect any standard object files that the linker " +"may include by default (such as system libraries)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:489 +msgid "" +"The following methods implement methods for autodetection of compiler " +"options, providing some functionality similar to GNU :program:`autoconf`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:495 +msgid "" +"Detect the language of a given file, or list of files. Uses the instance " +"attributes :attr:`language_map` (a dictionary), and :attr:`language_order` " +"(a list) to do the job." +msgstr "" + +#: ../Doc/distutils/apiref.rst:502 +msgid "" +"Search the specified list of directories for a static or shared library file " +"*lib* and return the full path to that file. If *debug* is true, look for a " +"debugging version (if that makes sense on the current platform). Return " +"``None`` if *lib* wasn't found in any of the specified directories." +msgstr "" + +#: ../Doc/distutils/apiref.rst:510 +msgid "" +"Return a boolean indicating whether *funcname* is supported on the current " +"platform. The optional arguments can be used to augment the compilation " +"environment by providing additional include files and paths and libraries " +"and paths." +msgstr "" + +#: ../Doc/distutils/apiref.rst:518 +msgid "" +"Return the compiler option to add *dir* to the list of directories searched " +"for libraries." +msgstr "" + +#: ../Doc/distutils/apiref.rst:524 +msgid "" +"Return the compiler option to add *lib* to the list of libraries linked into " +"the shared library or executable." +msgstr "" + +#: ../Doc/distutils/apiref.rst:530 +msgid "" +"Return the compiler option to add *dir* to the list of directories searched " +"for runtime libraries." +msgstr "" + +#: ../Doc/distutils/apiref.rst:536 +msgid "" +"Define the executables (and options for them) that will be run to perform " +"the various stages of compilation. The exact set of executables that may be " +"specified here depends on the compiler class (via the 'executables' class " +"attribute), but most will have:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:542 +msgid "attribute" +msgstr "" + +#: ../Doc/distutils/apiref.rst:544 +msgid "*compiler*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:544 +msgid "the C/C++ compiler" +msgstr "" + +#: ../Doc/distutils/apiref.rst:546 +msgid "*linker_so*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:546 +msgid "linker used to create shared objects and libraries" +msgstr "" + +#: ../Doc/distutils/apiref.rst:549 +msgid "*linker_exe*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:549 +msgid "linker used to create binary executables" +msgstr "" + +#: ../Doc/distutils/apiref.rst:551 +msgid "*archiver*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:551 +msgid "static library creator" +msgstr "" + +#: ../Doc/distutils/apiref.rst:554 +msgid "" +"On platforms with a command-line (Unix, DOS/Windows), each of these is a " +"string that will be split into executable name and (optional) list of " +"arguments. (Splitting the string is done similarly to how Unix shells " +"operate: words are delimited by spaces, but quotes and backslashes can " +"override this. See :func:`distutils.util.split_quoted`.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:560 +msgid "The following methods invoke stages in the build process." +msgstr "" + +#: ../Doc/distutils/apiref.rst:565 +msgid "" +"Compile one or more source files. Generates object files (e.g. transforms " +"a :file:`.c` file to a :file:`.o` file.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:568 +msgid "" +"*sources* must be a list of filenames, most likely C/C++ files, but in " +"reality anything that can be handled by a particular compiler and compiler " +"class (eg. :class:`MSVCCompiler` can handle resource files in *sources*). " +"Return a list of object filenames, one per source filename in *sources*. " +"Depending on the implementation, not all source files will necessarily be " +"compiled, but all corresponding object filenames will be returned." +msgstr "" + +#: ../Doc/distutils/apiref.rst:575 +msgid "" +"If *output_dir* is given, object files will be put under it, while retaining " +"their original path component. That is, :file:`foo/bar.c` normally compiles " +"to :file:`foo/bar.o` (for a Unix implementation); if *output_dir* is " +"*build*, then it would compile to :file:`build/foo/bar.o`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:580 +msgid "" +"*macros*, if given, must be a list of macro definitions. A macro definition " +"is either a ``(name, value)`` 2-tuple or a ``(name,)`` 1-tuple. The former " +"defines a macro; if the value is ``None``, the macro is defined without an " +"explicit value. The 1-tuple case undefines a macro. Later definitions/" +"redefinitions/undefinitions take precedence." +msgstr "" + +#: ../Doc/distutils/apiref.rst:586 +msgid "" +"*include_dirs*, if given, must be a list of strings, the directories to add " +"to the default include file search path for this compilation only." +msgstr "" + +#: ../Doc/distutils/apiref.rst:589 +msgid "" +"*debug* is a boolean; if true, the compiler will be instructed to output " +"debug symbols in (or alongside) the object file(s)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:592 +msgid "" +"*extra_preargs* and *extra_postargs* are implementation-dependent. On " +"platforms that have the notion of a command-line (e.g. Unix, DOS/Windows), " +"they are most likely lists of strings: extra command-line arguments to " +"prepend/append to the compiler command line. On other platforms, consult " +"the implementation class documentation. In any event, they are intended as " +"an escape hatch for those occasions when the abstract compiler framework " +"doesn't cut the mustard." +msgstr "" + +#: ../Doc/distutils/apiref.rst:599 +msgid "" +"*depends*, if given, is a list of filenames that all targets depend on. If " +"a source file is older than any file in depends, then the source file will " +"be recompiled. This supports dependency tracking, but only at a coarse " +"granularity." +msgstr "" + +#: ../Doc/distutils/apiref.rst:604 +msgid "Raises :exc:`CompileError` on failure." +msgstr "" + +#: ../Doc/distutils/apiref.rst:609 +msgid "" +"Link a bunch of stuff together to create a static library file. The \"bunch " +"of stuff\" consists of the list of object files supplied as *objects*, the " +"extra object files supplied to :meth:`add_link_object` and/or :meth:" +"`set_link_objects`, the libraries supplied to :meth:`add_library` and/or :" +"meth:`set_libraries`, and the libraries supplied as *libraries* (if any)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:615 +msgid "" +"*output_libname* should be a library name, not a filename; the filename will " +"be inferred from the library name. *output_dir* is the directory where the " +"library file will be put." +msgstr "" + +#: ../Doc/distutils/apiref.rst:621 +msgid "" +"*debug* is a boolean; if true, debugging information will be included in the " +"library (note that on most platforms, it is the compile step where this " +"matters: the *debug* flag is included here just for consistency)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:625 ../Doc/distutils/apiref.rst:667 +msgid "" +"*target_lang* is the target language for which the given objects are being " +"compiled. This allows specific linkage time treatment of certain languages." +msgstr "" + +#: ../Doc/distutils/apiref.rst:628 +msgid "Raises :exc:`LibError` on failure." +msgstr "" + +#: ../Doc/distutils/apiref.rst:633 +msgid "" +"Link a bunch of stuff together to create an executable or shared library " +"file." +msgstr "" + +#: ../Doc/distutils/apiref.rst:635 +msgid "" +"The \"bunch of stuff\" consists of the list of object files supplied as " +"*objects*. *output_filename* should be a filename. If *output_dir* is " +"supplied, *output_filename* is relative to it (i.e. *output_filename* can " +"provide directory components if needed)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:640 +msgid "" +"*libraries* is a list of libraries to link against. These are library " +"names, not filenames, since they're translated into filenames in a platform-" +"specific way (eg. *foo* becomes :file:`libfoo.a` on Unix and :file:`foo.lib` " +"on DOS/Windows). However, they can include a directory component, which " +"means the linker will look in that specific directory rather than searching " +"all the normal locations." +msgstr "" + +#: ../Doc/distutils/apiref.rst:647 +msgid "" +"*library_dirs*, if supplied, should be a list of directories to search for " +"libraries that were specified as bare library names (ie. no directory " +"component). These are on top of the system default and those supplied to :" +"meth:`add_library_dir` and/or :meth:`set_library_dirs`. " +"*runtime_library_dirs* is a list of directories that will be embedded into " +"the shared library and used to search for other shared libraries that \\*it" +"\\* depends on at run-time. (This may only be relevant on Unix.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:655 +msgid "" +"*export_symbols* is a list of symbols that the shared library will export. " +"(This appears to be relevant only on Windows.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:658 +msgid "" +"*debug* is as for :meth:`compile` and :meth:`create_static_lib`, with the " +"slight distinction that it actually matters on most platforms (as opposed " +"to :meth:`create_static_lib`, which includes a *debug* flag mostly for " +"form's sake)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:663 +msgid "" +"*extra_preargs* and *extra_postargs* are as for :meth:`compile` (except of " +"course that they supply command-line arguments for the particular linker " +"being used)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:670 +msgid "Raises :exc:`LinkError` on failure." +msgstr "" + +#: ../Doc/distutils/apiref.rst:675 +msgid "" +"Link an executable. *output_progname* is the name of the file executable, " +"while *objects* are a list of object filenames to link in. Other arguments " +"are as for the :meth:`link` method." +msgstr "" + +#: ../Doc/distutils/apiref.rst:682 +msgid "" +"Link a shared library. *output_libname* is the name of the output library, " +"while *objects* is a list of object filenames to link in. Other arguments " +"are as for the :meth:`link` method." +msgstr "" + +#: ../Doc/distutils/apiref.rst:689 +msgid "" +"Link a shared object. *output_filename* is the name of the shared object " +"that will be created, while *objects* is a list of object filenames to link " +"in. Other arguments are as for the :meth:`link` method." +msgstr "" + +#: ../Doc/distutils/apiref.rst:696 +msgid "" +"Preprocess a single C/C++ source file, named in *source*. Output will be " +"written to file named *output_file*, or *stdout* if *output_file* not " +"supplied. *macros* is a list of macro definitions as for :meth:`compile`, " +"which will augment the macros set with :meth:`define_macro` and :meth:" +"`undefine_macro`. *include_dirs* is a list of directory names that will be " +"added to the default list, in the same way as :meth:`add_include_dir`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:703 +msgid "Raises :exc:`PreprocessError` on failure." +msgstr "" + +#: ../Doc/distutils/apiref.rst:705 +msgid "" +"The following utility methods are defined by the :class:`CCompiler` class, " +"for use by the various concrete subclasses." +msgstr "" + +#: ../Doc/distutils/apiref.rst:711 +msgid "" +"Returns the filename of the executable for the given *basename*. Typically " +"for non-Windows platforms this is the same as the basename, while Windows " +"will get a :file:`.exe` added." +msgstr "" + +#: ../Doc/distutils/apiref.rst:718 +msgid "" +"Returns the filename for the given library name on the current platform. On " +"Unix a library with *lib_type* of ``'static'`` will typically be of the " +"form :file:`liblibname.a`, while a *lib_type* of ``'dynamic'`` will be of " +"the form :file:`liblibname.so`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:726 +msgid "" +"Returns the name of the object files for the given source files. " +"*source_filenames* should be a list of filenames." +msgstr "" + +#: ../Doc/distutils/apiref.rst:732 +msgid "" +"Returns the name of a shared object file for the given file name *basename*." +msgstr "" + +#: ../Doc/distutils/apiref.rst:737 +msgid "" +"Invokes :func:`distutils.util.execute`. This method invokes a Python " +"function *func* with the given arguments *args*, after logging and taking " +"into account the *dry_run* flag." +msgstr "" + +#: ../Doc/distutils/apiref.rst:744 +msgid "" +"Invokes :func:`distutils.util.spawn`. This invokes an external process to " +"run the given command." +msgstr "" + +#: ../Doc/distutils/apiref.rst:750 +msgid "" +"Invokes :func:`distutils.dir_util.mkpath`. This creates a directory and any " +"missing ancestor directories." +msgstr "" + +#: ../Doc/distutils/apiref.rst:756 +msgid "Invokes :meth:`distutils.file_util.move_file`. Renames *src* to *dst*." +msgstr "" + +#: ../Doc/distutils/apiref.rst:761 +msgid "Write a message using :func:`distutils.log.debug`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:766 +msgid "Write a warning message *msg* to standard error." +msgstr "" + +#: ../Doc/distutils/apiref.rst:771 +msgid "" +"If the *debug* flag is set on this :class:`CCompiler` instance, print *msg* " +"to standard output, otherwise do nothing." +msgstr "" + +#: ../Doc/distutils/apiref.rst:783 +msgid ":mod:`distutils.unixccompiler` --- Unix C Compiler" +msgstr "" + +#: ../Doc/distutils/apiref.rst:789 +msgid "" +"This module provides the :class:`UnixCCompiler` class, a subclass of :class:" +"`CCompiler` that handles the typical Unix-style command-line C compiler:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:792 +msgid "macros defined with :option:`-Dname[=value]`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:794 +msgid "macros undefined with :option:`-Uname`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:796 +msgid "include search directories specified with :option:`-Idir`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:798 +msgid "libraries specified with :option:`-llib`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:800 +msgid "library search directories specified with :option:`-Ldir`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:802 +msgid "" +"compile handled by :program:`cc` (or similar) executable with :option:`!-c` " +"option: compiles :file:`.c` to :file:`.o`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:805 +msgid "" +"link static library handled by :program:`ar` command (possibly with :program:" +"`ranlib`)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:808 +msgid "link shared library handled by :program:`cc` :option:`-shared`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:812 +msgid ":mod:`distutils.msvccompiler` --- Microsoft Compiler" +msgstr "" + +#: ../Doc/distutils/apiref.rst:818 +msgid "" +"This module provides :class:`MSVCCompiler`, an implementation of the " +"abstract :class:`CCompiler` class for Microsoft Visual Studio. Typically, " +"extension modules need to be compiled with the same compiler that was used " +"to compile Python. For Python 2.3 and earlier, the compiler was Visual " +"Studio 6. For Python 2.4 and 2.5, the compiler is Visual Studio .NET 2003. " +"The AMD64 and Itanium binaries are created using the Platform SDK." +msgstr "" + +#: ../Doc/distutils/apiref.rst:825 +msgid "" +":class:`MSVCCompiler` will normally choose the right compiler, linker etc. " +"on its own. To override this choice, the environment variables " +"*DISTUTILS_USE_SDK* and *MSSdk* must be both set. *MSSdk* indicates that the " +"current environment has been setup by the SDK's ``SetEnv.Cmd`` script, or " +"that the environment variables had been registered when the SDK was " +"installed; *DISTUTILS_USE_SDK* indicates that the distutils user has made an " +"explicit choice to override the compiler selection by :class:`MSVCCompiler`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:835 +msgid ":mod:`distutils.bcppcompiler` --- Borland Compiler" +msgstr "" + +#: ../Doc/distutils/apiref.rst:840 +msgid "" +"This module provides :class:`BorlandCCompiler`, a subclass of the abstract :" +"class:`CCompiler` class for the Borland C++ compiler." +msgstr "" + +#: ../Doc/distutils/apiref.rst:845 +msgid ":mod:`distutils.cygwincompiler` --- Cygwin Compiler" +msgstr "" + +#: ../Doc/distutils/apiref.rst:850 +msgid "" +"This module provides the :class:`CygwinCCompiler` class, a subclass of :" +"class:`UnixCCompiler` that handles the Cygwin port of the GNU C compiler to " +"Windows. It also contains the Mingw32CCompiler class which handles the " +"mingw32 port of GCC (same as cygwin in no-cygwin mode)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:857 +msgid ":mod:`distutils.archive_util` --- Archiving utilities" +msgstr "" + +#: ../Doc/distutils/apiref.rst:863 +msgid "" +"This module provides a few functions for creating archive files, such as " +"tarballs or zipfiles." +msgstr "" + +#: ../Doc/distutils/apiref.rst:869 +msgid "" +"Create an archive file (eg. ``zip`` or ``tar``). *base_name* is the name " +"of the file to create, minus any format-specific extension; *format* is the " +"archive format: one of ``zip``, ``tar``, ``gztar``, ``bztar``, ``xztar``, or " +"``ztar``. *root_dir* is a directory that will be the root directory of the " +"archive; ie. we typically ``chdir`` into *root_dir* before creating the " +"archive. *base_dir* is the directory where we start archiving from; ie. " +"*base_dir* will be the common prefix of all files and directories in the " +"archive. *root_dir* and *base_dir* both default to the current directory. " +"Returns the name of the archive file." +msgstr "" + +#: ../Doc/distutils/apiref.rst:879 ../Doc/distutils/builtdist.rst:103 +#: ../Doc/distutils/sourcedist.rst:44 +msgid "Added support for the ``xztar`` format." +msgstr "" + +#: ../Doc/distutils/apiref.rst:885 +msgid "" +"'Create an (optional compressed) archive as a tar file from all files in and " +"under *base_dir*. *compress* must be ``'gzip'`` (the default), ``'bzip2'``, " +"``'xz'``, ``'compress'``, or ``None``. For the ``'compress'`` method the " +"compression utility named by :program:`compress` must be on the default " +"program search path, so this is probably Unix-specific. The output tar file " +"will be named :file:`base_dir.tar`, possibly plus the appropriate " +"compression extension (``.gz``, ``.bz2``, ``.xz`` or ``.Z``). Return the " +"output filename." +msgstr "" + +#: ../Doc/distutils/apiref.rst:894 +msgid "Added support for the ``xz`` compression." +msgstr "" + +#: ../Doc/distutils/apiref.rst:900 +msgid "" +"Create a zip file from all files in and under *base_dir*. The output zip " +"file will be named *base_name* + :file:`.zip`. Uses either the :mod:" +"`zipfile` Python module (if available) or the InfoZIP :file:`zip` utility " +"(if installed and found on the default search path). If neither tool is " +"available, raises :exc:`DistutilsExecError`. Returns the name of the " +"output zip file." +msgstr "" + +#: ../Doc/distutils/apiref.rst:908 +msgid ":mod:`distutils.dep_util` --- Dependency checking" +msgstr "" + +#: ../Doc/distutils/apiref.rst:914 +msgid "" +"This module provides functions for performing simple, timestamp-based " +"dependency of files and groups of files; also, functions based entirely on " +"such timestamp dependency analysis." +msgstr "" + +#: ../Doc/distutils/apiref.rst:921 +msgid "" +"Return true if *source* exists and is more recently modified than *target*, " +"or if *source* exists and *target* doesn't. Return false if both exist and " +"*target* is the same age or newer than *source*. Raise :exc:" +"`DistutilsFileError` if *source* does not exist." +msgstr "" + +#: ../Doc/distutils/apiref.rst:929 +msgid "" +"Walk two filename lists in parallel, testing if each source is newer than " +"its corresponding target. Return a pair of lists (*sources*, *targets*) " +"where source is newer than target, according to the semantics of :func:" +"`newer`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:938 +msgid "" +"Return true if *target* is out-of-date with respect to any file listed in " +"*sources* In other words, if *target* exists and is newer than every file " +"in *sources*, return false; otherwise return true. *missing* controls what " +"we do when a source file is missing; the default (``'error'``) is to blow up " +"with an :exc:`OSError` from inside :func:`os.stat`; if it is ``'ignore'``, " +"we silently drop any missing source files; if it is ``'newer'``, any missing " +"source files make us assume that *target* is out-of-date (this is handy in " +"\"dry-run\" mode: it'll make you pretend to carry out commands that wouldn't " +"work because inputs are missing, but that doesn't matter because you're not " +"actually going to run the commands)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:951 +msgid ":mod:`distutils.dir_util` --- Directory tree operations" +msgstr "" + +#: ../Doc/distutils/apiref.rst:957 +msgid "" +"This module provides functions for operating on directories and trees of " +"directories." +msgstr "" + +#: ../Doc/distutils/apiref.rst:963 +msgid "" +"Create a directory and any missing ancestor directories. If the directory " +"already exists (or if *name* is the empty string, which means the current " +"directory, which of course exists), then do nothing. Raise :exc:" +"`DistutilsFileError` if unable to create some directory along the way (eg. " +"some sub-path exists, but is a file rather than a directory). If *verbose* " +"is true, print a one-line summary of each mkdir to stdout. Return the list " +"of directories actually created." +msgstr "" + +#: ../Doc/distutils/apiref.rst:974 +msgid "" +"Create all the empty directories under *base_dir* needed to put *files* " +"there. *base_dir* is just the name of a directory which doesn't necessarily " +"exist yet; *files* is a list of filenames to be interpreted relative to " +"*base_dir*. *base_dir* + the directory portion of every file in *files* will " +"be created if it doesn't already exist. *mode*, *verbose* and *dry_run* " +"flags are as for :func:`mkpath`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:984 +msgid "" +"Copy an entire directory tree *src* to a new location *dst*. Both *src* and " +"*dst* must be directory names. If *src* is not a directory, raise :exc:" +"`DistutilsFileError`. If *dst* does not exist, it is created with :func:" +"`mkpath`. The end result of the copy is that every file in *src* is copied " +"to *dst*, and directories under *src* are recursively copied to *dst*. " +"Return the list of files that were copied or might have been copied, using " +"their output name. The return value is unaffected by *update* or *dry_run*: " +"it is simply the list of all files under *src*, with the names changed to be " +"under *dst*." +msgstr "" + +#: ../Doc/distutils/apiref.rst:994 +msgid "" +"*preserve_mode* and *preserve_times* are the same as for :func:`distutils." +"file_util.copy_file`; note that they only apply to regular files, not to " +"directories. If *preserve_symlinks* is true, symlinks will be copied as " +"symlinks (on platforms that support them!); otherwise (the default), the " +"destination of the symlink will be copied. *update* and *verbose* are the " +"same as for :func:`copy_file`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1002 +msgid "" +"Files in *src* that begin with :file:`.nfs` are skipped (more information on " +"these files is available in answer D2 of the `NFS FAQ page `_)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1006 +msgid "NFS files are ignored." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1011 +msgid "" +"Recursively remove *directory* and all files and directories underneath it. " +"Any errors are ignored (apart from being reported to ``sys.stdout`` if " +"*verbose* is true)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1017 +msgid ":mod:`distutils.file_util` --- Single file operations" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1023 +msgid "" +"This module contains some utility functions for operating on individual " +"files." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1028 +msgid "" +"Copy file *src* to *dst*. If *dst* is a directory, then *src* is copied " +"there with the same name; otherwise, it must be a filename. (If the file " +"exists, it will be ruthlessly clobbered.) If *preserve_mode* is true (the " +"default), the file's mode (type and permission bits, or whatever is " +"analogous on the current platform) is copied. If *preserve_times* is true " +"(the default), the last-modified and last-access times are copied as well. " +"If *update* is true, *src* will only be copied if *dst* does not exist, or " +"if *dst* does exist but is older than *src*." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1037 +msgid "" +"*link* allows you to make hard links (using :func:`os.link`) or symbolic " +"links (using :func:`os.symlink`) instead of copying: set it to ``'hard'`` or " +"``'sym'``; if it is ``None`` (the default), files are copied. Don't set " +"*link* on systems that don't support it: :func:`copy_file` doesn't check if " +"hard or symbolic linking is available. It uses :func:`_copy_file_contents` " +"to copy file contents." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1044 +msgid "" +"Return a tuple ``(dest_name, copied)``: *dest_name* is the actual name of " +"the output file, and *copied* is true if the file was copied (or would have " +"been copied, if *dry_run* true)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1058 +msgid "" +"Move file *src* to *dst*. If *dst* is a directory, the file will be moved " +"into it with the same name; otherwise, *src* is just renamed to *dst*. " +"Returns the new full name of the file." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1064 +msgid "" +"Handles cross-device moves on Unix using :func:`copy_file`. What about " +"other systems?" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1070 +msgid "" +"Create a file called *filename* and write *contents* (a sequence of strings " +"without line terminators) to it." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1075 +msgid ":mod:`distutils.util` --- Miscellaneous other utility functions" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1081 +msgid "" +"This module contains other assorted bits and pieces that don't fit into any " +"other utility module." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1087 +msgid "" +"Return a string that identifies the current platform. This is used mainly " +"to distinguish platform-specific build directories and platform-specific " +"built distributions. Typically includes the OS name and version and the " +"architecture (as supplied by 'os.uname()'), although the exact information " +"included depends on the OS; eg. for IRIX the architecture isn't particularly " +"important (IRIX only runs on SGI hardware), but for Linux the kernel version " +"isn't particularly important." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1095 +msgid "Examples of returned values:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1097 +msgid "``linux-i586``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1098 +msgid "``linux-alpha``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1099 +msgid "``solaris-2.6-sun4u``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1100 +msgid "``irix-5.3``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1101 +msgid "``irix64-6.2``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1103 +msgid "For non-POSIX platforms, currently just returns ``sys.platform``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1105 +msgid "" +"For Mac OS X systems the OS version reflects the minimal version on which " +"binaries will run (that is, the value of ``MACOSX_DEPLOYMENT_TARGET`` during " +"the build of Python), not the OS version of the current system." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1109 +msgid "" +"For universal binary builds on Mac OS X the architecture value reflects the " +"universal binary status instead of the architecture of the current " +"processor. For 32-bit universal binaries the architecture is ``fat``, for 64-" +"bit universal binaries the architecture is ``fat64``, and for 4-way " +"universal binaries the architecture is ``universal``. Starting from Python " +"2.7 and Python 3.2 the architecture ``fat3`` is used for a 3-way universal " +"build (ppc, i386, x86_64) and ``intel`` is used for a universal build with " +"the i386 and x86_64 architectures" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1118 +msgid "Examples of returned values on Mac OS X:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1120 +msgid "``macosx-10.3-ppc``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1122 +msgid "``macosx-10.3-fat``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1124 +msgid "``macosx-10.5-universal``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1126 +msgid "``macosx-10.6-intel``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1131 +msgid "" +"Return 'pathname' as a name that will work on the native filesystem, i.e. " +"split it on '/' and put it back together again using the current directory " +"separator. Needed because filenames in the setup script are always supplied " +"in Unix style, and have to be converted to the local convention before we " +"can actually use them in the filesystem. Raises :exc:`ValueError` on non-" +"Unix-ish systems if *pathname* either starts or ends with a slash." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1141 +msgid "" +"Return *pathname* with *new_root* prepended. If *pathname* is relative, " +"this is equivalent to ``os.path.join(new_root,pathname)`` Otherwise, it " +"requires making *pathname* relative and then joining the two, which is " +"tricky on DOS/Windows." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1148 +msgid "" +"Ensure that 'os.environ' has all the environment variables we guarantee that " +"users can use in config files, command-line options, etc. Currently this " +"includes:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1152 +msgid ":envvar:`HOME` - user's home directory (Unix only)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1153 +msgid "" +":envvar:`PLAT` - description of the current platform, including hardware and " +"OS (see :func:`get_platform`)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1159 +msgid "" +"Perform shell/Perl-style variable substitution on *s*. Every occurrence of " +"``$`` followed by a name is considered a variable, and variable is " +"substituted by the value found in the *local_vars* dictionary, or in ``os." +"environ`` if it's not in *local_vars*. *os.environ* is first checked/" +"augmented to guarantee that it contains certain values: see :func:" +"`check_environ`. Raise :exc:`ValueError` for any variables not found in " +"either *local_vars* or ``os.environ``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1166 +msgid "" +"Note that this is not a fully-fledged string interpolation function. A valid " +"``$variable`` can consist only of upper and lower case letters, numbers and " +"an underscore. No { } or ( ) style quoting is available." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1173 +msgid "" +"Split a string up according to Unix shell-like rules for quotes and " +"backslashes. In short: words are delimited by spaces, as long as those " +"spaces are not escaped by a backslash, or inside a quoted string. Single and " +"double quotes are equivalent, and the quote characters can be backslash-" +"escaped. The backslash is stripped from any two-character escape sequence, " +"leaving only the escaped character. The quote characters are stripped from " +"any quoted string. Returns a list of words." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1186 +msgid "" +"Perform some action that affects the outside world (for instance, writing to " +"the filesystem). Such actions are special because they are disabled by the " +"*dry_run* flag. This method takes care of all that bureaucracy for you; " +"all you have to do is supply the function to call and an argument tuple for " +"it (to embody the \"external action\" being performed), and an optional " +"message to print." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1195 +msgid "Convert a string representation of truth to true (1) or false (0)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1197 +msgid "" +"True values are ``y``, ``yes``, ``t``, ``true``, ``on`` and ``1``; false " +"values are ``n``, ``no``, ``f``, ``false``, ``off`` and ``0``. Raises :exc:" +"`ValueError` if *val* is anything else." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1204 +msgid "" +"Byte-compile a collection of Python source files to :file:`.pyc` files in a :" +"file:`__pycache__` subdirectory (see :pep:`3147` and :pep:`488`). *py_files* " +"is a list of files to compile; any files that don't end in :file:`.py` are " +"silently skipped. *optimize* must be one of the following:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1209 +msgid "``0`` - don't optimize" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1210 +msgid "``1`` - normal optimization (like ``python -O``)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1211 +msgid "``2`` - extra optimization (like ``python -OO``)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1213 +msgid "If *force* is true, all files are recompiled regardless of timestamps." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1215 +msgid "" +"The source filename encoded in each :term:`bytecode` file defaults to the " +"filenames listed in *py_files*; you can modify these with *prefix* and " +"*basedir*. *prefix* is a string that will be stripped off of each source " +"filename, and *base_dir* is a directory name that will be prepended (after " +"*prefix* is stripped). You can supply either or both (or neither) of " +"*prefix* and *base_dir*, as you wish." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1222 +msgid "" +"If *dry_run* is true, doesn't actually do anything that would affect the " +"filesystem." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1225 +msgid "" +"Byte-compilation is either done directly in this interpreter process with " +"the standard :mod:`py_compile` module, or indirectly by writing a temporary " +"script and executing it. Normally, you should let :func:`byte_compile` " +"figure out to use direct compilation or not (see the source for details). " +"The *direct* flag is used by the script generated in indirect mode; unless " +"you know what you're doing, leave it set to ``None``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1232 +msgid "" +"Create ``.pyc`` files with an :func:`import magic tag ` in " +"their name, in a :file:`__pycache__` subdirectory instead of files without " +"tag in the current directory." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1237 +msgid "Create ``.pyc`` files according to :pep:`488`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1243 +msgid "" +"Return a version of *header* escaped for inclusion in an :rfc:`822` header, " +"by ensuring there are 8 spaces space after each newline. Note that it does " +"no other modification of the string." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1253 +msgid ":mod:`distutils.dist` --- The Distribution class" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1260 +msgid "" +"This module provides the :class:`~distutils.core.Distribution` class, which " +"represents the module distribution being built/installed/distributed." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1265 +msgid ":mod:`distutils.extension` --- The Extension class" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1272 +msgid "" +"This module provides the :class:`Extension` class, used to describe C/C++ " +"extension modules in setup scripts." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1280 +msgid ":mod:`distutils.debug` --- Distutils debug mode" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1286 +msgid "This module provides the DEBUG flag." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1290 +msgid ":mod:`distutils.errors` --- Distutils exceptions" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1296 +msgid "" +"Provides exceptions used by the Distutils modules. Note that Distutils " +"modules may raise standard exceptions; in particular, SystemExit is usually " +"raised for errors that are obviously the end-user's fault (eg. bad command-" +"line arguments)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1300 +msgid "" +"This module is safe to use in ``from ... import *`` mode; it only exports " +"symbols whose names start with ``Distutils`` and end with ``Error``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1305 +msgid "" +":mod:`distutils.fancy_getopt` --- Wrapper around the standard getopt module" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1311 +msgid "" +"This module provides a wrapper around the standard :mod:`getopt` module " +"that provides the following additional features:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1314 +msgid "short and long options are tied together" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1316 +msgid "" +"options have help strings, so :func:`fancy_getopt` could potentially create " +"a complete usage summary" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1319 +msgid "options set attributes of a passed-in object" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1321 +msgid "" +"boolean options can have \"negative aliases\" --- eg. if :option:`--quiet` " +"is the \"negative alias\" of :option:`--verbose`, then :option:`--quiet` on " +"the command line sets *verbose* to false." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1327 +msgid "" +"Wrapper function. *options* is a list of ``(long_option, short_option, " +"help_string)`` 3-tuples as described in the constructor for :class:" +"`FancyGetopt`. *negative_opt* should be a dictionary mapping option names to " +"option names, both the key and value should be in the *options* list. " +"*object* is an object which will be used to store values (see the :meth:" +"`getopt` method of the :class:`FancyGetopt` class). *args* is the argument " +"list. Will use ``sys.argv[1:]`` if you pass ``None`` as *args*." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1338 +msgid "Wraps *text* to less than *width* wide." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1343 +msgid "" +"The option_table is a list of 3-tuples: ``(long_option, short_option, " +"help_string)``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1346 +msgid "" +"If an option takes an argument, its *long_option* should have ``'='`` " +"appended; *short_option* should just be a single character, no ``':'`` in " +"any case. *short_option* should be ``None`` if a *long_option* doesn't have " +"a corresponding *short_option*. All option tuples must have long options." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1351 +msgid "The :class:`FancyGetopt` class provides the following methods:" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1356 +msgid "Parse command-line options in args. Store as attributes on *object*." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1358 +msgid "" +"If *args* is ``None`` or not supplied, uses ``sys.argv[1:]``. If *object* " +"is ``None`` or not supplied, creates a new :class:`OptionDummy` instance, " +"stores option values there, and returns a tuple ``(args, object)``. If " +"*object* is supplied, it is modified in place and :func:`getopt` just " +"returns *args*; in both cases, the returned *args* is a modified copy of the " +"passed-in *args* list, which is left untouched." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1370 +msgid "" +"Returns the list of ``(option, value)`` tuples processed by the previous run " +"of :meth:`getopt` Raises :exc:`RuntimeError` if :meth:`getopt` hasn't been " +"called yet." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1377 +msgid "" +"Generate help text (a list of strings, one per suggested line of output) " +"from the option table for this :class:`FancyGetopt` object." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1380 +msgid "If supplied, prints the supplied *header* at the top of the help." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1384 +msgid ":mod:`distutils.filelist` --- The FileList class" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1391 +msgid "" +"This module provides the :class:`FileList` class, used for poking about the " +"filesystem and building lists of files." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1396 +msgid ":mod:`distutils.log` --- Simple PEP 282-style logging" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1403 +msgid ":mod:`distutils.spawn` --- Spawn a sub-process" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1409 +msgid "" +"This module provides the :func:`spawn` function, a front-end to various " +"platform-specific functions for launching another program in a sub-process. " +"Also provides :func:`find_executable` to search the path for a given " +"executable name." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1416 +msgid ":mod:`distutils.sysconfig` --- System configuration information" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1425 +msgid "" +"The :mod:`distutils.sysconfig` module provides access to Python's low-level " +"configuration information. The specific configuration variables available " +"depend heavily on the platform and configuration. The specific variables " +"depend on the build process for the specific version of Python being run; " +"the variables are those found in the :file:`Makefile` and configuration " +"header that are installed with Python on Unix systems. The configuration " +"header is called :file:`pyconfig.h` for Python versions starting with 2.2, " +"and :file:`config.h` for earlier versions of Python." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1434 +msgid "" +"Some additional functions are provided which perform some useful " +"manipulations for other parts of the :mod:`distutils` package." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1440 +msgid "The result of ``os.path.normpath(sys.prefix)``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1445 +msgid "The result of ``os.path.normpath(sys.exec_prefix)``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1450 +msgid "" +"Return the value of a single variable. This is equivalent to " +"``get_config_vars().get(name)``." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1456 +msgid "" +"Return a set of variable definitions. If there are no arguments, this " +"returns a dictionary mapping names of configuration variables to values. If " +"arguments are provided, they should be strings, and the return value will be " +"a sequence giving the associated values. If a given name does not have a " +"corresponding value, ``None`` will be included for that variable." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1465 +msgid "" +"Return the full path name of the configuration header. For Unix, this will " +"be the header generated by the :program:`configure` script; for other " +"platforms the header will have been supplied directly by the Python source " +"distribution. The file is a platform-specific text file." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1473 +msgid "" +"Return the full path name of the :file:`Makefile` used to build Python. For " +"Unix, this will be a file generated by the :program:`configure` script; the " +"meaning for other platforms will vary. The file is a platform-specific text " +"file, if it exists. This function is only useful on POSIX platforms." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1481 +msgid "" +"Return the directory for either the general or platform-dependent C include " +"files. If *plat_specific* is true, the platform-dependent include directory " +"is returned; if false or omitted, the platform-independent directory is " +"returned. If *prefix* is given, it is used as either the prefix instead of :" +"const:`PREFIX`, or as the exec-prefix instead of :const:`EXEC_PREFIX` if " +"*plat_specific* is true." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1491 +msgid "" +"Return the directory for either the general or platform-dependent library " +"installation. If *plat_specific* is true, the platform-dependent include " +"directory is returned; if false or omitted, the platform-independent " +"directory is returned. If *prefix* is given, it is used as either the " +"prefix instead of :const:`PREFIX`, or as the exec-prefix instead of :const:" +"`EXEC_PREFIX` if *plat_specific* is true. If *standard_lib* is true, the " +"directory for the standard library is returned rather than the directory for " +"the installation of third-party extensions." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1500 +msgid "" +"The following function is only intended for use within the :mod:`distutils` " +"package." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1506 +msgid "" +"Do any platform-specific customization of a :class:`distutils.ccompiler." +"CCompiler` instance." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1509 +msgid "" +"This function is only needed on Unix at this time, but should be called " +"consistently to support forward-compatibility. It inserts the information " +"that varies across Unix flavors and is stored in Python's :file:`Makefile`. " +"This information includes the selected compiler, compiler and linker " +"options, and the extension used by the linker for shared objects." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1515 +msgid "" +"This function is even more special-purpose, and should only be used from " +"Python's own build procedures." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1521 +msgid "" +"Inform the :mod:`distutils.sysconfig` module that it is being used as part " +"of the build process for Python. This changes a lot of relative locations " +"for files, allowing them to be located in the build area rather than in an " +"installed Python." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1528 +msgid ":mod:`distutils.text_file` --- The TextFile class" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1534 +msgid "" +"This module provides the :class:`TextFile` class, which gives an interface " +"to text files that (optionally) takes care of stripping comments, ignoring " +"blank lines, and joining lines with backslashes." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1541 +msgid "" +"This class provides a file-like object that takes care of all the things " +"you commonly want to do when processing a text file that has some line-by-" +"line syntax: strip comments (as long as ``#`` is your comment character), " +"skip blank lines, join adjacent lines by escaping the newline (ie. backslash " +"at end of line), strip leading and/or trailing whitespace. All of these are " +"optional and independently controllable." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1548 +msgid "" +"The class provides a :meth:`warn` method so you can generate warning " +"messages that report physical line number, even if the logical line in " +"question spans multiple physical lines. Also provides :meth:`unreadline` " +"for implementing line-at-a-time lookahead." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1553 +msgid "" +":class:`TextFile` instances are create with either *filename*, *file*, or " +"both. :exc:`RuntimeError` is raised if both are ``None``. *filename* should " +"be a string, and *file* a file object (or something that provides :meth:" +"`readline` and :meth:`close` methods). It is recommended that you supply " +"at least *filename*, so that :class:`TextFile` can include it in warning " +"messages. If *file* is not supplied, :class:`TextFile` creates its own " +"using the :func:`open` built-in function." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1561 +msgid "" +"The options are all boolean, and affect the values returned by :meth:" +"`readline`" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1566 +msgid "option name" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1566 +msgid "default" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1568 +msgid "*strip_comments*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1568 +msgid "" +"strip from ``'#'`` to end-of- line, as well as any whitespace leading up to " +"the ``'#'``\\ ---unless it is escaped by a backslash" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1568 ../Doc/distutils/apiref.rst:1577 +#: ../Doc/distutils/apiref.rst:1582 +msgid "true" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1574 +msgid "*lstrip_ws*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1574 +msgid "strip leading whitespace from each line before returning it" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1574 ../Doc/distutils/apiref.rst:1592 +#: ../Doc/distutils/apiref.rst:1603 +msgid "false" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1577 +msgid "*rstrip_ws*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1577 +msgid "" +"strip trailing whitespace (including line terminator!) from each line before " +"returning it." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1582 +msgid "*skip_blanks*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1582 +msgid "" +"skip lines that are empty \\*after\\* stripping comments and whitespace. " +"(If both lstrip_ws and rstrip_ws are false, then some lines may consist of " +"solely whitespace: these will \\*not\\* be skipped, even if *skip_blanks* is " +"true.)" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1592 +msgid "*join_lines*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1592 +msgid "" +"if a backslash is the last non-newline character on a line after stripping " +"comments and whitespace, join the following line to it to form one logical " +"line; if N consecutive lines end with a backslash, then N+1 physical lines " +"will be joined to form one logical line." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1603 +msgid "*collapse_join*" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1603 +msgid "" +"strip leading whitespace from lines that are joined to their predecessor; " +"only matters if ``(join_lines and not lstrip_ws)``" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1610 +msgid "" +"Note that since *rstrip_ws* can strip the trailing newline, the semantics " +"of :meth:`readline` must differ from those of the built-in file object's :" +"meth:`readline` method! In particular, :meth:`readline` returns ``None`` " +"for end-of-file: an empty string might just be a blank line (or an all-" +"whitespace line), if *rstrip_ws* is true but *skip_blanks* is not." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1619 +msgid "" +"Open a new file *filename*. This overrides any *file* or *filename* " +"constructor arguments." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1625 +msgid "" +"Close the current file and forget everything we know about it (including the " +"filename and the current line number)." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1631 +msgid "" +"Print (to stderr) a warning message tied to the current logical line in the " +"current file. If the current logical line in the file spans multiple " +"physical lines, the warning refers to the whole range, such as ``\"lines " +"3-5\"``. If *line* is supplied, it overrides the current line number; it " +"may be a list or tuple to indicate a range of physical lines, or an integer " +"for a single physical line." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1641 +msgid "" +"Read and return a single logical line from the current file (or from an " +"internal buffer if lines have previously been \"unread\" with :meth:" +"`unreadline`). If the *join_lines* option is true, this may involve " +"reading multiple physical lines concatenated into a single string. Updates " +"the current line number, so calling :meth:`warn` after :meth:`readline` " +"emits a warning about the physical line(s) just read. Returns ``None`` on " +"end-of-file, since the empty string can occur if *rstrip_ws* is true but " +"*strip_blanks* is not." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1652 +msgid "" +"Read and return the list of all logical lines remaining in the current file. " +"This updates the current line number to the last line of the file." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1658 +msgid "" +"Push *line* (a string) onto an internal buffer that will be checked by " +"future :meth:`readline` calls. Handy for implementing a parser with line-at-" +"a-time lookahead. Note that lines that are \"unread\" with :meth:" +"`unreadline` are not subsequently re-cleansed (whitespace stripped, or " +"whatever) when read with :meth:`readline`. If multiple calls are made to :" +"meth:`unreadline` before a call to :meth:`readline`, the lines will be " +"returned most in most recent first order." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1667 +msgid ":mod:`distutils.version` --- Version number classes" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1682 +msgid ":mod:`distutils.cmd` --- Abstract base class for Distutils commands" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1689 +msgid "This module supplies the abstract base class :class:`Command`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1694 +msgid "" +"Abstract base class for defining command classes, the \"worker bees\" of the " +"Distutils. A useful analogy for command classes is to think of them as " +"subroutines with local variables called *options*. The options are declared " +"in :meth:`initialize_options` and defined (given their final values) in :" +"meth:`finalize_options`, both of which must be defined by every command " +"class. The distinction between the two is necessary because option values " +"might come from the outside world (command line, config file, ...), and any " +"options dependent on other options must be computed after these outside " +"influences have been processed --- hence :meth:`finalize_options`. The body " +"of the subroutine, where it does all its work based on the values of its " +"options, is the :meth:`run` method, which must also be implemented by every " +"command class." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1707 +msgid "" +"The class constructor takes a single argument *dist*, a :class:`~distutils." +"core.Distribution` instance." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1712 +msgid "Creating a new Distutils command" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1714 +msgid "This section outlines the steps to create a new Distutils command." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1716 +msgid "" +"A new command lives in a module in the :mod:`distutils.command` package. " +"There is a sample template in that directory called :file:" +"`command_template`. Copy this file to a new module with the same name as " +"the new command you're implementing. This module should implement a class " +"with the same name as the module (and the command). So, for instance, to " +"create the command ``peel_banana`` (so that users can run ``setup.py " +"peel_banana``), you'd copy :file:`command_template` to :file:`distutils/" +"command/peel_banana.py`, then edit it so that it's implementing the class :" +"class:`peel_banana`, a subclass of :class:`distutils.cmd.Command`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1726 +msgid "Subclasses of :class:`Command` must define the following methods." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1730 +msgid "" +"Set default values for all the options that this command supports. Note " +"that these defaults may be overridden by other commands, by the setup " +"script, by config files, or by the command-line. Thus, this is not the " +"place to code dependencies between options; generally, :meth:" +"`initialize_options` implementations are just a bunch of ``self.foo = None`` " +"assignments." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1739 +msgid "" +"Set final values for all the options that this command supports. This is " +"always called as late as possible, ie. after any option assignments from " +"the command-line or from other commands have been done. Thus, this is the " +"place to code option dependencies: if *foo* depends on *bar*, then it is " +"safe to set *foo* from *bar* as long as *foo* still has the same value it " +"was assigned in :meth:`initialize_options`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1749 +msgid "" +"A command's raison d'etre: carry out the action it exists to perform, " +"controlled by the options initialized in :meth:`initialize_options`, " +"customized by other commands, the setup script, the command-line, and config " +"files, and finalized in :meth:`finalize_options`. All terminal output and " +"filesystem interaction should be done by :meth:`run`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1758 +msgid "" +"*sub_commands* formalizes the notion of a \"family\" of commands, e.g. " +"``install`` as the parent with sub-commands ``install_lib``, " +"``install_headers``, etc. The parent of a family of commands defines " +"*sub_commands* as a class attribute; it's a list of 2-tuples " +"``(command_name, predicate)``, with *command_name* a string and *predicate* " +"a function, a string or ``None``. *predicate* is a method of the parent " +"command that determines whether the corresponding command is applicable in " +"the current situation. (E.g. ``install_headers`` is only applicable if we " +"have any C header files to install.) If *predicate* is ``None``, that " +"command is always applicable." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1769 +msgid "" +"*sub_commands* is usually defined at the *end* of a class, because " +"predicates can be methods of the class, so they must already have been " +"defined. The canonical example is the :command:`install` command." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1775 +msgid ":mod:`distutils.command` --- Individual Distutils commands" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1786 +msgid ":mod:`distutils.command.bdist` --- Build a binary installer" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1796 +msgid "" +":mod:`distutils.command.bdist_packager` --- Abstract base class for packagers" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1806 +msgid ":mod:`distutils.command.bdist_dumb` --- Build a \"dumb\" installer" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1816 +msgid "" +":mod:`distutils.command.bdist_msi` --- Build a Microsoft Installer binary " +"package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1823 +msgid "Builds a `Windows Installer`_ (.msi) binary package." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1827 +msgid "" +"In most cases, the ``bdist_msi`` installer is a better choice than the " +"``bdist_wininst`` installer, because it provides better support for Win64 " +"platforms, allows administrators to perform non-interactive installations, " +"and allows installation through group policies." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1834 +msgid "" +":mod:`distutils.command.bdist_rpm` --- Build a binary distribution as a " +"Redhat RPM and SRPM" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1844 +msgid ":mod:`distutils.command.bdist_wininst` --- Build a Windows installer" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1854 +msgid ":mod:`distutils.command.sdist` --- Build a source distribution" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1864 +msgid ":mod:`distutils.command.build` --- Build all files of a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1874 +msgid "" +":mod:`distutils.command.build_clib` --- Build any C libraries in a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1884 +msgid "" +":mod:`distutils.command.build_ext` --- Build any extensions in a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1894 +msgid "" +":mod:`distutils.command.build_py` --- Build the .py/.pyc files of a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1904 +msgid "" +"Alternative implementation of build_py which also runs the 2to3 conversion " +"library on each .py file that is going to be installed. To use this in a " +"setup.py file for a distribution that is designed to run with both Python 2." +"x and 3.x, add::" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1914 +msgid "to your setup.py, and later::" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1918 +msgid "to the invocation of setup()." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1922 +msgid "" +":mod:`distutils.command.build_scripts` --- Build the scripts of a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1932 +msgid ":mod:`distutils.command.clean` --- Clean a package build area" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1937 +msgid "" +"This command removes the temporary files created by :command:`build` and its " +"subcommands, like intermediary compiled object files. With the ``--all`` " +"option, the complete build directory will be removed." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1941 +msgid "" +"Extension modules built :ref:`in place ` will " +"not be cleaned, as they are not in the build directory." +msgstr "" + +#: ../Doc/distutils/apiref.rst:1946 +msgid ":mod:`distutils.command.config` --- Perform package configuration" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1956 +msgid ":mod:`distutils.command.install` --- Install a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1966 +msgid "" +":mod:`distutils.command.install_data` --- Install data files from a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1976 +msgid "" +":mod:`distutils.command.install_headers` --- Install C/C++ header files from " +"a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1986 +msgid "" +":mod:`distutils.command.install_lib` --- Install library files from a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:1996 +msgid "" +":mod:`distutils.command.install_scripts` --- Install script files from a " +"package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:2006 +msgid "" +":mod:`distutils.command.register` --- Register a module with the Python " +"Package Index" +msgstr "" + +#: ../Doc/distutils/apiref.rst:2012 +msgid "" +"The ``register`` command registers the package with the Python Package " +"Index. This is described in more detail in :pep:`301`." +msgstr "" + +#: ../Doc/distutils/apiref.rst:2019 +msgid ":mod:`distutils.command.check` --- Check the meta-data of a package" +msgstr "" + +#: ../Doc/distutils/apiref.rst:2025 +msgid "" +"The ``check`` command performs some tests on the meta-data of a package. For " +"example, it verifies that all required meta-data are provided as the " +"arguments passed to the :func:`setup` function." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:5 +msgid "Creating Built Distributions" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:7 +msgid "" +"A \"built distribution\" is what you're probably used to thinking of either " +"as a \"binary package\" or an \"installer\" (depending on your background). " +"It's not necessarily binary, though, because it might contain only Python " +"source code and/or byte-code; and we don't call it a package, because that " +"word is already spoken for in Python. (And \"installer\" is a term specific " +"to the world of mainstream desktop systems.)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:14 +msgid "" +"A built distribution is how you make life as easy as possible for installers " +"of your module distribution: for users of RPM-based Linux systems, it's a " +"binary RPM; for Windows users, it's an executable installer; for Debian-" +"based Linux users, it's a Debian package; and so forth. Obviously, no one " +"person will be able to create built distributions for every platform under " +"the sun, so the Distutils are designed to enable module developers to " +"concentrate on their specialty---writing code and creating source " +"distributions---while an intermediary species called *packagers* springs up " +"to turn source distributions into built distributions for as many platforms " +"as there are packagers." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:24 +msgid "" +"Of course, the module developer could be his own packager; or the packager " +"could be a volunteer \"out there\" somewhere who has access to a platform " +"which the original developer does not; or it could be software periodically " +"grabbing new source distributions and turning them into built distributions " +"for as many platforms as the software has access to. Regardless of who they " +"are, a packager uses the setup script and the :command:`bdist` command " +"family to generate built distributions." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:32 +msgid "" +"As a simple example, if I run the following command in the Distutils source " +"tree::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:37 +msgid "" +"then the Distutils builds my module distribution (the Distutils itself in " +"this case), does a \"fake\" installation (also in the :file:`build` " +"directory), and creates the default type of built distribution for my " +"platform. The default format for built distributions is a \"dumb\" tar file " +"on Unix, and a simple executable installer on Windows. (That tar file is " +"considered \"dumb\" because it has to be unpacked in a specific location to " +"work.)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:44 +msgid "" +"Thus, the above command on a Unix system creates :file:`Distutils-1.0.{plat}." +"tar.gz`; unpacking this tarball from the right place installs the Distutils " +"just as though you had downloaded the source distribution and run ``python " +"setup.py install``. (The \"right place\" is either the root of the " +"filesystem or Python's :file:`{prefix}` directory, depending on the options " +"given to the :command:`bdist_dumb` command; the default is to make dumb " +"distributions relative to :file:`{prefix}`.)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:52 +msgid "" +"Obviously, for pure Python distributions, this isn't any simpler than just " +"running ``python setup.py install``\\ ---but for non-pure distributions, " +"which include extensions that would need to be compiled, it can mean the " +"difference between someone being able to use your extensions or not. And " +"creating \"smart\" built distributions, such as an RPM package or an " +"executable installer for Windows, is far more convenient for users even if " +"your distribution doesn't include any extensions." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:60 +msgid "" +"The :command:`bdist` command has a :option:`--formats` option, similar to " +"the :command:`sdist` command, which you can use to select the types of built " +"distribution to generate: for example, ::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:66 +msgid "" +"would, when run on a Unix system, create :file:`Distutils-1.0.{plat}.zip`\\ " +"---again, this archive would be unpacked from the root directory to install " +"the Distutils." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:70 +msgid "The available formats for built distributions are:" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:73 ../Doc/distutils/sourcedist.rst:25 +msgid "Format" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:73 ../Doc/distutils/commandref.rst:61 +#: ../Doc/distutils/setupscript.rst:562 ../Doc/distutils/sourcedist.rst:25 +msgid "Description" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:73 ../Doc/distutils/setupscript.rst:562 +#: ../Doc/distutils/sourcedist.rst:25 +msgid "Notes" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:75 ../Doc/distutils/sourcedist.rst:29 +msgid "``gztar``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:75 +msgid "gzipped tar file (:file:`.tar.gz`)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:75 ../Doc/distutils/setupscript.rst:564 +#: ../Doc/distutils/setupscript.rst:578 +msgid "\\(1)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:78 ../Doc/distutils/sourcedist.rst:32 +msgid "``bztar``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:78 +msgid "bzipped tar file (:file:`.tar.bz2`)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:81 ../Doc/distutils/sourcedist.rst:35 +msgid "``xztar``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:81 +msgid "xzipped tar file (:file:`.tar.xz`)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:84 ../Doc/distutils/sourcedist.rst:38 +msgid "``ztar``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:84 ../Doc/distutils/sourcedist.rst:38 +msgid "compressed tar file (:file:`.tar.Z`)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:84 ../Doc/distutils/setupscript.rst:568 +#: ../Doc/distutils/setupscript.rst:570 ../Doc/distutils/setupscript.rst:573 +#: ../Doc/distutils/setupscript.rst:575 +msgid "\\(3)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:87 ../Doc/distutils/sourcedist.rst:41 +msgid "``tar``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:87 ../Doc/distutils/sourcedist.rst:41 +msgid "tar file (:file:`.tar`)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:89 ../Doc/distutils/sourcedist.rst:27 +msgid "``zip``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:89 ../Doc/distutils/sourcedist.rst:27 +msgid "zip file (:file:`.zip`)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:89 +msgid "(2),(4)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:91 +msgid "``rpm``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:91 +msgid "RPM" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:91 ../Doc/distutils/setupscript.rst:584 +msgid "\\(5)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:93 +msgid "``pkgtool``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:93 +msgid "Solaris :program:`pkgtool`" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:95 +msgid "``sdux``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:95 +msgid "HP-UX :program:`swinstall`" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:97 +msgid "``wininst``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:97 +msgid "self-extracting ZIP file for Windows" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:97 ../Doc/distutils/setupscript.rst:587 +#: ../Doc/distutils/setupscript.rst:590 ../Doc/distutils/sourcedist.rst:38 +msgid "\\(4)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:100 +msgid "``msi``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:100 +msgid "Microsoft Installer." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:107 ../Doc/distutils/setupscript.rst:597 +#: ../Doc/distutils/sourcedist.rst:47 +msgid "Notes:" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:110 ../Doc/distutils/sourcedist.rst:53 +msgid "default on Unix" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:113 ../Doc/distutils/sourcedist.rst:50 +msgid "default on Windows" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:116 +msgid "requires external :program:`compress` utility." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:119 ../Doc/distutils/sourcedist.rst:56 +msgid "" +"requires either external :program:`zip` utility or :mod:`zipfile` module " +"(part of the standard Python library since Python 1.6)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:123 +msgid "" +"requires external :program:`rpm` utility, version 3.0.4 or better (use ``rpm " +"--version`` to find out which version you have)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:126 +msgid "" +"You don't have to use the :command:`bdist` command with the :option:`--" +"formats` option; you can also use the command that directly implements the " +"format you're interested in. Some of these :command:`bdist` \"sub-commands" +"\" actually generate several similar formats; for instance, the :command:" +"`bdist_dumb` command generates all the \"dumb\" archive formats (``tar``, " +"``gztar``, ``bztar``, ``xztar``, ``ztar``, and ``zip``), and :command:" +"`bdist_rpm` generates both binary and source RPMs. The :command:`bdist` sub-" +"commands, and the formats generated by each, are:" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:136 ../Doc/distutils/commandref.rst:61 +msgid "Command" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:136 +msgid "Formats" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:138 +msgid ":command:`bdist_dumb`" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:138 +msgid "tar, gztar, bztar, xztar, ztar, zip" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:140 +msgid ":command:`bdist_rpm`" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:140 +msgid "rpm, srpm" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:142 +msgid ":command:`bdist_wininst`" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:142 +msgid "wininst" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:144 +msgid ":command:`bdist_msi`" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:144 +msgid "msi" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:147 +msgid "" +"The following sections give details on the individual :command:`bdist_\\*` " +"commands." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:163 +msgid "Creating RPM packages" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:165 +msgid "" +"The RPM format is used by many popular Linux distributions, including Red " +"Hat, SuSE, and Mandrake. If one of these (or any of the other RPM-based " +"Linux distributions) is your usual environment, creating RPM packages for " +"other users of that same distribution is trivial. Depending on the " +"complexity of your module distribution and differences between Linux " +"distributions, you may also be able to create RPMs that work on different " +"RPM-based distributions." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:172 +msgid "" +"The usual way to create an RPM of your module distribution is to run the :" +"command:`bdist_rpm` command::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:177 +msgid "or the :command:`bdist` command with the :option:`--format` option::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:181 +msgid "" +"The former allows you to specify RPM-specific options; the latter allows " +"you to easily specify multiple formats in one run. If you need to do both, " +"you can explicitly specify multiple :command:`bdist_\\*` commands and their " +"options::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:188 +msgid "" +"Creating RPM packages is driven by a :file:`.spec` file, much as using the " +"Distutils is driven by the setup script. To make your life easier, the :" +"command:`bdist_rpm` command normally creates a :file:`.spec` file based on " +"the information you supply in the setup script, on the command line, and in " +"any Distutils configuration files. Various options and sections in the :" +"file:`.spec` file are derived from options in the setup script as follows:" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:196 ../Doc/distutils/builtdist.rst:220 +msgid "RPM :file:`.spec` file option or section" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:196 +msgid "Distutils setup script option" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:198 +msgid "Name" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:198 ../Doc/distutils/setupscript.rst:564 +msgid "``name``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:200 +msgid "Summary (in preamble)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:200 ../Doc/distutils/setupscript.rst:580 +msgid "``description``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:202 +msgid "Version" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:202 ../Doc/distutils/setupscript.rst:566 +msgid "``version``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:204 ../Doc/distutils/builtdist.rst:227 +msgid "Vendor" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:204 +msgid "" +"``author`` and ``author_email``, or --- & ``maintainer`` and " +"``maintainer_email``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:208 +msgid "Copyright" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:208 ../Doc/distutils/setupscript.rst:594 +msgid "``license``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:210 +msgid "Url" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:210 ../Doc/distutils/setupscript.rst:578 +msgid "``url``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:212 +msgid "%description (section)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:212 ../Doc/distutils/setupscript.rst:584 +msgid "``long_description``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:215 +msgid "" +"Additionally, there are many options in :file:`.spec` files that don't have " +"corresponding options in the setup script. Most of these are handled " +"through options to the :command:`bdist_rpm` command as follows:" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:220 +msgid ":command:`bdist_rpm` option" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:220 +msgid "default value" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:223 +msgid "Release" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:223 +msgid "``release``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:223 +msgid "\"1\"" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:225 +msgid "Group" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:225 +msgid "``group``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:225 +msgid "\"Development/Libraries\"" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:227 +msgid "``vendor``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:227 +msgid "(see above)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:229 +msgid "Packager" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:229 +msgid "``packager``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:229 ../Doc/distutils/builtdist.rst:231 +#: ../Doc/distutils/builtdist.rst:233 ../Doc/distutils/builtdist.rst:235 +#: ../Doc/distutils/builtdist.rst:237 ../Doc/distutils/builtdist.rst:239 +#: ../Doc/distutils/builtdist.rst:241 ../Doc/distutils/builtdist.rst:243 +msgid "(none)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:231 +msgid "Provides" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:231 +msgid "``provides``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:233 +msgid "Requires" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:233 +msgid "``requires``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:235 +msgid "Conflicts" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:235 +msgid "``conflicts``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:237 +msgid "Obsoletes" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:237 +msgid "``obsoletes``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:239 +msgid "Distribution" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:239 +msgid "``distribution_name``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:241 +msgid "BuildRequires" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:241 +msgid "``build_requires``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:243 +msgid "Icon" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:243 +msgid "``icon``" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:246 +msgid "" +"Obviously, supplying even a few of these options on the command-line would " +"be tedious and error-prone, so it's usually best to put them in the setup " +"configuration file, :file:`setup.cfg`\\ ---see section :ref:`setup-config`. " +"If you distribute or package many Python module distributions, you might " +"want to put options that apply to all of them in your personal Distutils " +"configuration file (:file:`~/.pydistutils.cfg`). If you want to temporarily " +"disable this file, you can pass the :option:`--no-user-cfg` option to :file:" +"`setup.py`." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:254 +msgid "" +"There are three steps to building a binary RPM package, all of which are " +"handled automatically by the Distutils:" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:257 +msgid "" +"create a :file:`.spec` file, which describes the package (analogous to the " +"Distutils setup script; in fact, much of the information in the setup " +"script winds up in the :file:`.spec` file)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:261 +msgid "create the source RPM" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:263 +msgid "" +"create the \"binary\" RPM (which may or may not contain binary code, " +"depending on whether your module distribution contains Python extensions)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:266 +msgid "" +"Normally, RPM bundles the last two steps together; when you use the " +"Distutils, all three steps are typically bundled together." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:269 +msgid "" +"If you wish, you can separate these three steps. You can use the :option:`--" +"spec-only` option to make :command:`bdist_rpm` just create the :file:`.spec` " +"file and exit; in this case, the :file:`.spec` file will be written to the " +"\"distribution directory\"---normally :file:`dist/`, but customizable with " +"the :option:`--dist-dir` option. (Normally, the :file:`.spec` file winds up " +"deep in the \"build tree,\" in a temporary directory created by :command:" +"`bdist_rpm`.)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:297 +msgid "Creating Windows Installers" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:299 +msgid "" +"Executable installers are the natural format for binary distributions on " +"Windows. They display a nice graphical user interface, display some " +"information about the module distribution to be installed taken from the " +"metadata in the setup script, let the user select a few options, and start " +"or cancel the installation." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:305 +msgid "" +"Since the metadata is taken from the setup script, creating Windows " +"installers is usually as easy as running::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:310 +msgid "or the :command:`bdist` command with the :option:`--formats` option::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:314 +msgid "" +"If you have a pure module distribution (only containing pure Python modules " +"and packages), the resulting installer will be version independent and have " +"a name like :file:`foo-1.0.win32.exe`. These installers can even be created " +"on Unix platforms or Mac OS X." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:319 +msgid "" +"If you have a non-pure distribution, the extensions can only be created on a " +"Windows platform, and will be Python version dependent. The installer " +"filename will reflect this and now has the form :file:`foo-1.0.win32-py2.0." +"exe`. You have to create a separate installer for every Python version you " +"want to support." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:325 +msgid "" +"The installer will try to compile pure modules into :term:`bytecode` after " +"installation on the target system in normal and optimizing mode. If you " +"don't want this to happen for some reason, you can run the :command:" +"`bdist_wininst` command with the :option:`--no-target-compile` and/or the :" +"option:`--no-target-optimize` option." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:331 +msgid "" +"By default the installer will display the cool \"Python Powered\" logo when " +"it is run, but you can also supply your own 152x261 bitmap which must be a " +"Windows :file:`.bmp` file with the :option:`--bitmap` option." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:335 +msgid "" +"The installer will also display a large title on the desktop background " +"window when it is run, which is constructed from the name of your " +"distribution and the version number. This can be changed to another text by " +"using the :option:`--title` option." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:340 +msgid "" +"The installer file will be written to the \"distribution directory\" --- " +"normally :file:`dist/`, but customizable with the :option:`--dist-dir` " +"option." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:346 +msgid "Cross-compiling on Windows" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:348 +msgid "" +"Starting with Python 2.6, distutils is capable of cross-compiling between " +"Windows platforms. In practice, this means that with the correct tools " +"installed, you can use a 32bit version of Windows to create 64bit extensions " +"and vice-versa." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:353 +msgid "" +"To build for an alternate platform, specify the :option:`--plat-name` option " +"to the build command. Valid values are currently 'win32', 'win-amd64' and " +"'win-ia64'. For example, on a 32bit version of Windows, you could execute::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:359 +msgid "" +"to build a 64bit version of your extension. The Windows Installers also " +"support this option, so the command::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:364 +msgid "" +"would create a 64bit installation executable on your 32bit version of " +"Windows." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:366 +msgid "" +"To cross-compile, you must download the Python source code and cross-compile " +"Python itself for the platform you are targeting - it is not possible from a " +"binary installation of Python (as the .lib etc file for other platforms are " +"not included.) In practice, this means the user of a 32 bit operating " +"system will need to use Visual Studio 2008 to open the :file:`PCBuild/" +"PCbuild.sln` solution in the Python source tree and build the \"x64\" " +"configuration of the 'pythoncore' project before cross-compiling extensions " +"is possible." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:375 +msgid "" +"Note that by default, Visual Studio 2008 does not install 64bit compilers or " +"tools. You may need to reexecute the Visual Studio setup process and select " +"these tools (using Control Panel->[Add/Remove] Programs is a convenient way " +"to check or modify your existing install.)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:383 +msgid "The Postinstallation script" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:385 +msgid "" +"Starting with Python 2.3, a postinstallation script can be specified with " +"the :option:`--install-script` option. The basename of the script must be " +"specified, and the script filename must also be listed in the scripts " +"argument to the setup function." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:390 +msgid "" +"This script will be run at installation time on the target system after all " +"the files have been copied, with ``argv[1]`` set to :option:`-install`, and " +"again at uninstallation time before the files are removed with ``argv[1]`` " +"set to :option:`-remove`." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:395 +msgid "" +"The installation script runs embedded in the windows installer, every output " +"(``sys.stdout``, ``sys.stderr``) is redirected into a buffer and will be " +"displayed in the GUI after the script has finished." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:399 +msgid "" +"Some functions especially useful in this context are available as additional " +"built-in functions in the installation script." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:406 +msgid "" +"These functions should be called when a directory or file is created by the " +"postinstall script at installation time. It will register *path* with the " +"uninstaller, so that it will be removed when the distribution is " +"uninstalled. To be safe, directories are only removed if they are empty." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:414 +msgid "" +"This function can be used to retrieve special folder locations on Windows " +"like the Start Menu or the Desktop. It returns the full path to the folder. " +"*csidl_string* must be one of the following strings::" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:434 +msgid "If the folder cannot be retrieved, :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:436 +msgid "" +"Which folders are available depends on the exact Windows version, and " +"probably also the configuration. For details refer to Microsoft's " +"documentation of the :c:func:`SHGetSpecialFolderPath` function." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:443 +msgid "" +"This function creates a shortcut. *target* is the path to the program to be " +"started by the shortcut. *description* is the description of the shortcut. " +"*filename* is the title of the shortcut that the user will see. *arguments* " +"specifies the command line arguments, if any. *workdir* is the working " +"directory for the program. *iconpath* is the file containing the icon for " +"the shortcut, and *iconindex* is the index of the icon in the file " +"*iconpath*. Again, for details consult the Microsoft documentation for the :" +"class:`IShellLink` interface." +msgstr "" + +#: ../Doc/distutils/builtdist.rst:454 +msgid "Vista User Access Control (UAC)" +msgstr "" + +#: ../Doc/distutils/builtdist.rst:456 +msgid "" +"Starting with Python 2.6, bdist_wininst supports a :option:`--user-access-" +"control` option. The default is 'none' (meaning no UAC handling is done), " +"and other valid values are 'auto' (meaning prompt for UAC elevation if " +"Python was installed for all users) and 'force' (meaning always prompt for " +"elevation)." +msgstr "" + +#: ../Doc/distutils/commandref.rst:5 +msgid "Command Reference" +msgstr "" + +#: ../Doc/distutils/commandref.rst:22 +msgid "Installing modules: the :command:`install` command family" +msgstr "" + +#: ../Doc/distutils/commandref.rst:24 +msgid "" +"The install command ensures that the build commands have been run and then " +"runs the subcommands :command:`install_lib`, :command:`install_data` and :" +"command:`install_scripts`." +msgstr "" + +#: ../Doc/distutils/commandref.rst:35 +msgid ":command:`install_data`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:37 +msgid "This command installs all data files provided with the distribution." +msgstr "" + +#: ../Doc/distutils/commandref.rst:43 +msgid ":command:`install_scripts`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:45 +msgid "This command installs all (Python) scripts in the distribution." +msgstr "" + +#: ../Doc/distutils/commandref.rst:54 +msgid "Creating a source distribution: the :command:`sdist` command" +msgstr "" + +#: ../Doc/distutils/commandref.rst:58 +msgid "The manifest template commands are:" +msgstr "" + +#: ../Doc/distutils/commandref.rst:63 +msgid ":command:`include pat1 pat2 ...`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:63 +msgid "include all files matching any of the listed patterns" +msgstr "" + +#: ../Doc/distutils/commandref.rst:66 +msgid ":command:`exclude pat1 pat2 ...`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:66 +msgid "exclude all files matching any of the listed patterns" +msgstr "" + +#: ../Doc/distutils/commandref.rst:69 +msgid ":command:`recursive-include dir pat1 pat2 ...`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:69 +msgid "include all files under *dir* matching any of the listed patterns" +msgstr "" + +#: ../Doc/distutils/commandref.rst:72 +msgid ":command:`recursive-exclude dir pat1 pat2 ...`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:72 +msgid "exclude all files under *dir* matching any of the listed patterns" +msgstr "" + +#: ../Doc/distutils/commandref.rst:75 +msgid ":command:`global-include pat1 pat2 ...`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:75 +msgid "" +"include all files anywhere in the source tree matching --- & any of the " +"listed patterns" +msgstr "" + +#: ../Doc/distutils/commandref.rst:78 +msgid ":command:`global-exclude pat1 pat2 ...`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:78 +msgid "" +"exclude all files anywhere in the source tree matching --- & any of the " +"listed patterns" +msgstr "" + +#: ../Doc/distutils/commandref.rst:81 +msgid ":command:`prune dir`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:81 +msgid "exclude all files under *dir*" +msgstr "" + +#: ../Doc/distutils/commandref.rst:83 +msgid ":command:`graft dir`" +msgstr "" + +#: ../Doc/distutils/commandref.rst:83 +msgid "include all files under *dir*" +msgstr "" + +#: ../Doc/distutils/commandref.rst:86 +msgid "" +"The patterns here are Unix-style \"glob\" patterns: ``*`` matches any " +"sequence of regular filename characters, ``?`` matches any single regular " +"filename character, and ``[range]`` matches any of the characters in *range* " +"(e.g., ``a-z``, ``a-zA-Z``, ``a-f0-9_.``). The definition of \"regular " +"filename character\" is platform-specific: on Unix it is anything except " +"slash; on Windows anything except backslash or colon." +msgstr "" + +#: ../Doc/distutils/configfile.rst:5 +msgid "Writing the Setup Configuration File" +msgstr "" + +#: ../Doc/distutils/configfile.rst:7 +msgid "" +"Often, it's not possible to write down everything needed to build a " +"distribution *a priori*: you may need to get some information from the user, " +"or from the user's system, in order to proceed. As long as that information " +"is fairly simple---a list of directories to search for C header files or " +"libraries, for example---then providing a configuration file, :file:`setup." +"cfg`, for users to edit is a cheap and easy way to solicit it. " +"Configuration files also let you provide default values for any command " +"option, which the installer can then override either on the command-line or " +"by editing the config file." +msgstr "" + +#: ../Doc/distutils/configfile.rst:16 +msgid "" +"The setup configuration file is a useful middle-ground between the setup " +"script ---which, ideally, would be opaque to installers [#]_---and the " +"command-line to the setup script, which is outside of your control and " +"entirely up to the installer. In fact, :file:`setup.cfg` (and any other " +"Distutils configuration files present on the target system) are processed " +"after the contents of the setup script, but before the command-line. This " +"has several useful consequences:" +msgstr "" + +#: ../Doc/distutils/configfile.rst:30 +msgid "" +"installers can override some of what you put in :file:`setup.py` by editing :" +"file:`setup.cfg`" +msgstr "" + +#: ../Doc/distutils/configfile.rst:33 +msgid "" +"you can provide non-standard defaults for options that are not easily set " +"in :file:`setup.py`" +msgstr "" + +#: ../Doc/distutils/configfile.rst:36 +msgid "" +"installers can override anything in :file:`setup.cfg` using the command-line " +"options to :file:`setup.py`" +msgstr "" + +#: ../Doc/distutils/configfile.rst:39 +msgid "The basic syntax of the configuration file is simple::" +msgstr "" + +#: ../Doc/distutils/configfile.rst:45 +msgid "" +"where *command* is one of the Distutils commands (e.g. :command:`build_py`, :" +"command:`install`), and *option* is one of the options that command " +"supports. Any number of options can be supplied for each command, and any " +"number of command sections can be included in the file. Blank lines are " +"ignored, as are comments, which run from a ``'#'`` character until the end " +"of the line. Long option values can be split across multiple lines simply " +"by indenting the continuation lines." +msgstr "" + +#: ../Doc/distutils/configfile.rst:53 +msgid "" +"You can find out the list of options supported by a particular command with " +"the universal :option:`!--help` option, e.g. ::" +msgstr "" + +#: ../Doc/distutils/configfile.rst:69 +msgid "" +"Note that an option spelled :option:`--foo-bar` on the command-line is " +"spelled ``foo_bar`` in configuration files." +msgstr "" + +#: ../Doc/distutils/configfile.rst:74 +msgid "" +"For example, say you want your extensions to be built \"in-place\"---that " +"is, you have an extension :mod:`pkg.ext`, and you want the compiled " +"extension file (:file:`ext.so` on Unix, say) to be put in the same source " +"directory as your pure Python modules :mod:`pkg.mod1` and :mod:`pkg.mod2`. " +"You can always use the :option:`--inplace` option on the command-line to " +"ensure this::" +msgstr "" + +#: ../Doc/distutils/configfile.rst:82 +msgid "" +"But this requires that you always specify the :command:`build_ext` command " +"explicitly, and remember to provide :option:`--inplace`. An easier way is to " +"\"set and forget\" this option, by encoding it in :file:`setup.cfg`, the " +"configuration file for this distribution::" +msgstr "" + +#: ../Doc/distutils/configfile.rst:90 +msgid "" +"This will affect all builds of this module distribution, whether or not you " +"explicitly specify :command:`build_ext`. If you include :file:`setup.cfg` " +"in your source distribution, it will also affect end-user builds---which is " +"probably a bad idea for this option, since always building extensions in-" +"place would break installation of the module distribution. In certain " +"peculiar cases, though, modules are built right in their installation " +"directory, so this is conceivably a useful ability. (Distributing " +"extensions that expect to be built in their installation directory is almost " +"always a bad idea, though.)" +msgstr "" + +#: ../Doc/distutils/configfile.rst:99 +msgid "" +"Another example: certain commands take a lot of options that don't change " +"from run to run; for example, :command:`bdist_rpm` needs to know everything " +"required to generate a \"spec\" file for creating an RPM distribution. Some " +"of this information comes from the setup script, and some is automatically " +"generated by the Distutils (such as the list of files installed). But some " +"of it has to be supplied as options to :command:`bdist_rpm`, which would be " +"very tedious to do on the command-line for every run. Hence, here is a " +"snippet from the Distutils' own :file:`setup.cfg`::" +msgstr "" + +#: ../Doc/distutils/configfile.rst:117 +msgid "" +"Note that the ``doc_files`` option is simply a whitespace-separated string " +"split across multiple lines for readability." +msgstr "" + +#: ../Doc/distutils/configfile.rst:124 +msgid ":ref:`inst-config-syntax` in \"Installing Python Modules\"" +msgstr "" + +#: ../Doc/distutils/configfile.rst:124 +msgid "" +"More information on the configuration files is available in the manual for " +"system administrators." +msgstr "" + +#: ../Doc/distutils/configfile.rst:129 +msgid "Footnotes" +msgstr "" + +#: ../Doc/distutils/configfile.rst:130 +msgid "" +"This ideal probably won't be achieved until auto-configuration is fully " +"supported by the Distutils." +msgstr "" + +#: ../Doc/distutils/examples.rst:5 +msgid "Examples" +msgstr "" + +#: ../Doc/distutils/examples.rst:7 +msgid "" +"This chapter provides a number of basic examples to help get started with " +"distutils. Additional information about using distutils can be found in the " +"Distutils Cookbook." +msgstr "" + +#: ../Doc/distutils/examples.rst:14 +msgid "`Distutils Cookbook `_" +msgstr "" + +#: ../Doc/distutils/examples.rst:15 +msgid "" +"Collection of recipes showing how to achieve more control over distutils." +msgstr "" + +#: ../Doc/distutils/examples.rst:21 +msgid "Pure Python distribution (by module)" +msgstr "" + +#: ../Doc/distutils/examples.rst:23 +msgid "" +"If you're just distributing a couple of modules, especially if they don't " +"live in a particular package, you can specify them individually using the " +"``py_modules`` option in the setup script." +msgstr "" + +#: ../Doc/distutils/examples.rst:27 +msgid "" +"In the simplest case, you'll have two files to worry about: a setup script " +"and the single module you're distributing, :file:`foo.py` in this example::" +msgstr "" + +#: ../Doc/distutils/examples.rst:34 +msgid "" +"(In all diagrams in this section, ** will refer to the distribution " +"root directory.) A minimal setup script to describe this situation would " +"be::" +msgstr "" + +#: ../Doc/distutils/examples.rst:43 +msgid "" +"Note that the name of the distribution is specified independently with the " +"``name`` option, and there's no rule that says it has to be the same as the " +"name of the sole module in the distribution (although that's probably a good " +"convention to follow). However, the distribution name is used to generate " +"filenames, so you should stick to letters, digits, underscores, and hyphens." +msgstr "" + +#: ../Doc/distutils/examples.rst:49 +msgid "" +"Since ``py_modules`` is a list, you can of course specify multiple modules, " +"eg. if you're distributing modules :mod:`foo` and :mod:`bar`, your setup " +"might look like this::" +msgstr "" + +#: ../Doc/distutils/examples.rst:58 +msgid "and the setup script might be ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:66 +msgid "" +"You can put module source files into another directory, but if you have " +"enough modules to do that, it's probably easier to specify modules by " +"package rather than listing them individually." +msgstr "" + +#: ../Doc/distutils/examples.rst:74 +msgid "Pure Python distribution (by package)" +msgstr "" + +#: ../Doc/distutils/examples.rst:76 +msgid "" +"If you have more than a couple of modules to distribute, especially if they " +"are in multiple packages, it's probably easier to specify whole packages " +"rather than individual modules. This works even if your modules are not in " +"a package; you can just tell the Distutils to process modules from the root " +"package, and that works the same as any other package (except that you don't " +"have to have an :file:`__init__.py` file)." +msgstr "" + +#: ../Doc/distutils/examples.rst:83 +msgid "The setup script from the last example could also be written as ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:91 +msgid "(The empty string stands for the root package.)" +msgstr "" + +#: ../Doc/distutils/examples.rst:93 +msgid "" +"If those two files are moved into a subdirectory, but remain in the root " +"package, e.g.::" +msgstr "" + +#: ../Doc/distutils/examples.rst:101 +msgid "" +"then you would still specify the root package, but you have to tell the " +"Distutils where source files in the root package live::" +msgstr "" + +#: ../Doc/distutils/examples.rst:111 +msgid "" +"More typically, though, you will want to distribute multiple modules in the " +"same package (or in sub-packages). For example, if the :mod:`foo` and :mod:" +"`bar` modules belong in package :mod:`foobar`, one way to layout your source " +"tree is ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:123 +msgid "" +"This is in fact the default layout expected by the Distutils, and the one " +"that requires the least work to describe in your setup script::" +msgstr "" + +#: ../Doc/distutils/examples.rst:132 +msgid "" +"If you want to put modules in directories not named for their package, then " +"you need to use the ``package_dir`` option again. For example, if the :file:" +"`src` directory holds modules in the :mod:`foobar` package::" +msgstr "" + +#: ../Doc/distutils/examples.rst:143 +msgid "an appropriate setup script would be ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:152 +msgid "" +"Or, you might put modules from your main package right in the distribution " +"root::" +msgstr "" + +#: ../Doc/distutils/examples.rst:161 +msgid "in which case your setup script would be ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:170 +msgid "(The empty string also stands for the current directory.)" +msgstr "" + +#: ../Doc/distutils/examples.rst:172 +msgid "" +"If you have sub-packages, they must be explicitly listed in ``packages``, " +"but any entries in ``package_dir`` automatically extend to sub-packages. (In " +"other words, the Distutils does *not* scan your source tree, trying to " +"figure out which directories correspond to Python packages by looking for :" +"file:`__init__.py` files.) Thus, if the default layout grows a sub-package::" +msgstr "" + +#: ../Doc/distutils/examples.rst:188 +msgid "then the corresponding setup script would be ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:200 +msgid "Single extension module" +msgstr "" + +#: ../Doc/distutils/examples.rst:202 +msgid "" +"Extension modules are specified using the ``ext_modules`` option. " +"``package_dir`` has no effect on where extension source files are found; it " +"only affects the source for pure Python modules. The simplest case, a " +"single extension module in a single C source file, is::" +msgstr "" + +#: ../Doc/distutils/examples.rst:211 +msgid "" +"If the :mod:`foo` extension belongs in the root package, the setup script " +"for this could be ::" +msgstr "" + +#: ../Doc/distutils/examples.rst:221 +msgid "If the extension actually belongs in a package, say :mod:`foopkg`, then" +msgstr "" + +#: ../Doc/distutils/examples.rst:223 +msgid "" +"With exactly the same source tree layout, this extension can be put in the :" +"mod:`foopkg` package simply by changing the name of the extension::" +msgstr "" + +#: ../Doc/distutils/examples.rst:234 +msgid "Checking a package" +msgstr "" + +#: ../Doc/distutils/examples.rst:236 +msgid "" +"The ``check`` command allows you to verify if your package meta-data meet " +"the minimum requirements to build a distribution." +msgstr "" + +#: ../Doc/distutils/examples.rst:239 +msgid "" +"To run it, just call it using your :file:`setup.py` script. If something is " +"missing, ``check`` will display a warning." +msgstr "" + +#: ../Doc/distutils/examples.rst:242 +msgid "Let's take an example with a simple script::" +msgstr "" + +#: ../Doc/distutils/examples.rst:248 +msgid "Running the ``check`` command will display some warnings:" +msgstr "" + +#: ../Doc/distutils/examples.rst:259 +msgid "" +"If you use the reStructuredText syntax in the ``long_description`` field and " +"`docutils`_ is installed you can check if the syntax is fine with the " +"``check`` command, using the ``restructuredtext`` option." +msgstr "" + +#: ../Doc/distutils/examples.rst:263 +msgid "For example, if the :file:`setup.py` script is changed like this::" +msgstr "" + +#: ../Doc/distutils/examples.rst:278 +msgid "" +"Where the long description is broken, ``check`` will be able to detect it by " +"using the :mod:`docutils` parser:" +msgstr "" + +#: ../Doc/distutils/examples.rst:289 +msgid "Reading the metadata" +msgstr "" + +#: ../Doc/distutils/examples.rst:291 +msgid "" +"The :func:`distutils.core.setup` function provides a command-line interface " +"that allows you to query the metadata fields of a project through the " +"``setup.py`` script of a given project:" +msgstr "" + +#: ../Doc/distutils/examples.rst:300 +msgid "" +"This call reads the ``name`` metadata by running the :func:`distutils.core." +"setup` function. Although, when a source or binary distribution is created " +"with Distutils, the metadata fields are written in a static file called :" +"file:`PKG-INFO`. When a Distutils-based project is installed in Python, the :" +"file:`PKG-INFO` file is copied alongside the modules and packages of the " +"distribution under :file:`NAME-VERSION-pyX.X.egg-info`, where ``NAME`` is " +"the name of the project, ``VERSION`` its version as defined in the Metadata, " +"and ``pyX.X`` the major and minor version of Python like ``2.7`` or ``3.2``." +msgstr "" + +#: ../Doc/distutils/examples.rst:310 +msgid "" +"You can read back this static file, by using the :class:`distutils.dist." +"DistributionMetadata` class and its :func:`read_pkg_file` method::" +msgstr "" + +#: ../Doc/distutils/examples.rst:324 +msgid "" +"Notice that the class can also be instanciated with a metadata file path to " +"loads its values::" +msgstr "" + +#: ../Doc/distutils/extending.rst:5 +msgid "Extending Distutils" +msgstr "" + +#: ../Doc/distutils/extending.rst:7 +msgid "" +"Distutils can be extended in various ways. Most extensions take the form of " +"new commands or replacements for existing commands. New commands may be " +"written to support new types of platform-specific packaging, for example, " +"while replacements for existing commands may be made to modify details of " +"how the command operates on a package." +msgstr "" + +#: ../Doc/distutils/extending.rst:13 +msgid "" +"Most extensions of the distutils are made within :file:`setup.py` scripts " +"that want to modify existing commands; many simply add a few file extensions " +"that should be copied into packages in addition to :file:`.py` files as a " +"convenience." +msgstr "" + +#: ../Doc/distutils/extending.rst:18 +msgid "" +"Most distutils command implementations are subclasses of the :class:" +"`distutils.cmd.Command` class. New commands may directly inherit from :" +"class:`Command`, while replacements often derive from :class:`Command` " +"indirectly, directly subclassing the command they are replacing. Commands " +"are required to derive from :class:`Command`." +msgstr "" + +#: ../Doc/distutils/extending.rst:33 +msgid "Integrating new commands" +msgstr "" + +#: ../Doc/distutils/extending.rst:35 +msgid "" +"There are different ways to integrate new command implementations into " +"distutils. The most difficult is to lobby for the inclusion of the new " +"features in distutils itself, and wait for (and require) a version of Python " +"that provides that support. This is really hard for many reasons." +msgstr "" + +#: ../Doc/distutils/extending.rst:40 +msgid "" +"The most common, and possibly the most reasonable for most needs, is to " +"include the new implementations with your :file:`setup.py` script, and cause " +"the :func:`distutils.core.setup` function use them::" +msgstr "" + +#: ../Doc/distutils/extending.rst:55 +msgid "" +"This approach is most valuable if the new implementations must be used to " +"use a particular package, as everyone interested in the package will need to " +"have the new command implementation." +msgstr "" + +#: ../Doc/distutils/extending.rst:59 +msgid "" +"Beginning with Python 2.4, a third option is available, intended to allow " +"new commands to be added which can support existing :file:`setup.py` scripts " +"without requiring modifications to the Python installation. This is " +"expected to allow third-party extensions to provide support for additional " +"packaging systems, but the commands can be used for anything distutils " +"commands can be used for. A new configuration option, ``command_packages`` " +"(command-line option :option:`--command-packages`), can be used to specify " +"additional packages to be searched for modules implementing commands. Like " +"all distutils options, this can be specified on the command line or in a " +"configuration file. This option can only be set in the ``[global]`` section " +"of a configuration file, or before any commands on the command line. If set " +"in a configuration file, it can be overridden from the command line; setting " +"it to an empty string on the command line causes the default to be used. " +"This should never be set in a configuration file provided with a package." +msgstr "" + +#: ../Doc/distutils/extending.rst:74 +msgid "" +"This new option can be used to add any number of packages to the list of " +"packages searched for command implementations; multiple package names should " +"be separated by commas. When not specified, the search is only performed in " +"the :mod:`distutils.command` package. When :file:`setup.py` is run with the " +"option ``--command-packages distcmds,buildcmds``, however, the packages :mod:" +"`distutils.command`, :mod:`distcmds`, and :mod:`buildcmds` will be searched " +"in that order. New commands are expected to be implemented in modules of " +"the same name as the command by classes sharing the same name. Given the " +"example command line option above, the command :command:`bdist_openpkg` " +"could be implemented by the class :class:`distcmds.bdist_openpkg." +"bdist_openpkg` or :class:`buildcmds.bdist_openpkg.bdist_openpkg`." +msgstr "" + +#: ../Doc/distutils/extending.rst:88 +msgid "Adding new distribution types" +msgstr "" + +#: ../Doc/distutils/extending.rst:90 +msgid "" +"Commands that create distributions (files in the :file:`dist/` directory) " +"need to add ``(command, filename)`` pairs to ``self.distribution." +"dist_files`` so that :command:`upload` can upload it to PyPI. The " +"*filename* in the pair contains no path information, only the name of the " +"file itself. In dry-run mode, pairs should still be added to represent what " +"would have been created." +msgstr "" + +#: ../Doc/distutils/index.rst:5 +msgid "Distributing Python Modules (Legacy version)" +msgstr "" + +#: ../Doc/distutils/index.rst:7 +msgid "Greg Ward, Anthony Baxter" +msgstr "" + +#: ../Doc/distutils/index.rst:8 +msgid "distutils-sig@python.org" +msgstr "" + +#: ../Doc/distutils/index.rst:12 +msgid ":ref:`distributing-index`" +msgstr "" + +#: ../Doc/distutils/index.rst:13 +msgid "The up to date module distribution documentations" +msgstr "" + +#: ../Doc/distutils/index.rst:15 +msgid "" +"This document describes the Python Distribution Utilities (\"Distutils\") " +"from the module developer's point of view, describing how to use the " +"Distutils to make Python modules and extensions easily available to a wider " +"audience with very little overhead for build/release/install mechanics." +msgstr "" + +#: ../Doc/distutils/index.rst:22 +msgid "" +"This guide only covers the basic tools for building and distributing " +"extensions that are provided as part of this version of Python. Third party " +"tools offer easier to use and more secure alternatives. Refer to the `quick " +"recommendations section `__ " +"in the Python Packaging User Guide for more information." +msgstr "" + +#: ../Doc/distutils/introduction.rst:5 +msgid "An Introduction to Distutils" +msgstr "" + +#: ../Doc/distutils/introduction.rst:7 +msgid "" +"This document covers using the Distutils to distribute your Python modules, " +"concentrating on the role of developer/distributor: if you're looking for " +"information on installing Python modules, you should refer to the :ref:" +"`install-index` chapter." +msgstr "" + +#: ../Doc/distutils/introduction.rst:16 +msgid "Concepts & Terminology" +msgstr "" + +#: ../Doc/distutils/introduction.rst:18 +msgid "" +"Using the Distutils is quite simple, both for module developers and for " +"users/administrators installing third-party modules. As a developer, your " +"responsibilities (apart from writing solid, well-documented and well-tested " +"code, of course!) are:" +msgstr "" + +#: ../Doc/distutils/introduction.rst:23 +msgid "write a setup script (:file:`setup.py` by convention)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:25 +msgid "(optional) write a setup configuration file" +msgstr "" + +#: ../Doc/distutils/introduction.rst:27 +msgid "create a source distribution" +msgstr "" + +#: ../Doc/distutils/introduction.rst:29 +msgid "(optional) create one or more built (binary) distributions" +msgstr "" + +#: ../Doc/distutils/introduction.rst:31 +msgid "Each of these tasks is covered in this document." +msgstr "" + +#: ../Doc/distutils/introduction.rst:33 +msgid "" +"Not all module developers have access to a multitude of platforms, so it's " +"not always feasible to expect them to create a multitude of built " +"distributions. It is hoped that a class of intermediaries, called " +"*packagers*, will arise to address this need. Packagers will take source " +"distributions released by module developers, build them on one or more " +"platforms, and release the resulting built distributions. Thus, users on " +"the most popular platforms will be able to install most popular Python " +"module distributions in the most natural way for their platform, without " +"having to run a single setup script or compile a line of code." +msgstr "" + +#: ../Doc/distutils/introduction.rst:47 +msgid "A Simple Example" +msgstr "" + +#: ../Doc/distutils/introduction.rst:49 +msgid "" +"The setup script is usually quite simple, although since it's written in " +"Python, there are no arbitrary limits to what you can do with it, though you " +"should be careful about putting arbitrarily expensive operations in your " +"setup script. Unlike, say, Autoconf-style configure scripts, the setup " +"script may be run multiple times in the course of building and installing " +"your module distribution." +msgstr "" + +#: ../Doc/distutils/introduction.rst:56 +msgid "" +"If all you want to do is distribute a module called :mod:`foo`, contained in " +"a file :file:`foo.py`, then your setup script can be as simple as this::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:65 +msgid "Some observations:" +msgstr "" + +#: ../Doc/distutils/introduction.rst:67 +msgid "" +"most information that you supply to the Distutils is supplied as keyword " +"arguments to the :func:`setup` function" +msgstr "" + +#: ../Doc/distutils/introduction.rst:70 +msgid "" +"those keyword arguments fall into two categories: package metadata (name, " +"version number) and information about what's in the package (a list of pure " +"Python modules, in this case)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:74 +msgid "" +"modules are specified by module name, not filename (the same will hold true " +"for packages and extensions)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:77 +msgid "" +"it's recommended that you supply a little more metadata, in particular your " +"name, email address and a URL for the project (see section :ref:`setup-" +"script` for an example)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:81 +msgid "" +"To create a source distribution for this module, you would create a setup " +"script, :file:`setup.py`, containing the above code, and run this command " +"from a terminal::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:87 +msgid "" +"For Windows, open a command prompt window (:menuselection:`Start --> " +"Accessories`) and change the command to::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:92 +msgid "" +":command:`sdist` will create an archive file (e.g., tarball on Unix, ZIP " +"file on Windows) containing your setup script :file:`setup.py`, and your " +"module :file:`foo.py`. The archive file will be named :file:`foo-1.0.tar.gz` " +"(or :file:`.zip`), and will unpack into a directory :file:`foo-1.0`." +msgstr "" + +#: ../Doc/distutils/introduction.rst:97 +msgid "" +"If an end-user wishes to install your :mod:`foo` module, all she has to do " +"is download :file:`foo-1.0.tar.gz` (or :file:`.zip`), unpack it, and---from " +"the :file:`foo-1.0` directory---run ::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:103 +msgid "" +"which will ultimately copy :file:`foo.py` to the appropriate directory for " +"third-party modules in their Python installation." +msgstr "" + +#: ../Doc/distutils/introduction.rst:106 +msgid "" +"This simple example demonstrates some fundamental concepts of the Distutils. " +"First, both developers and installers have the same basic user interface, i." +"e. the setup script. The difference is which Distutils *commands* they use: " +"the :command:`sdist` command is almost exclusively for module developers, " +"while :command:`install` is more often for installers (although most " +"developers will want to install their own code occasionally)." +msgstr "" + +#: ../Doc/distutils/introduction.rst:113 +msgid "" +"If you want to make things really easy for your users, you can create one or " +"more built distributions for them. For instance, if you are running on a " +"Windows machine, and want to make things easy for other Windows users, you " +"can create an executable installer (the most appropriate type of built " +"distribution for this platform) with the :command:`bdist_wininst` command. " +"For example::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:121 +msgid "" +"will create an executable installer, :file:`foo-1.0.win32.exe`, in the " +"current directory." +msgstr "" + +#: ../Doc/distutils/introduction.rst:124 +msgid "" +"Other useful built distribution formats are RPM, implemented by the :command:" +"`bdist_rpm` command, Solaris :program:`pkgtool` (:command:`bdist_pkgtool`), " +"and HP-UX :program:`swinstall` (:command:`bdist_sdux`). For example, the " +"following command will create an RPM file called :file:`foo-1.0.noarch.rpm`::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:132 +msgid "" +"(The :command:`bdist_rpm` command uses the :command:`rpm` executable, " +"therefore this has to be run on an RPM-based system such as Red Hat Linux, " +"SuSE Linux, or Mandrake Linux.)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:136 +msgid "" +"You can find out what distribution formats are available at any time by " +"running ::" +msgstr "" + +#: ../Doc/distutils/introduction.rst:145 +msgid "General Python terminology" +msgstr "" + +#: ../Doc/distutils/introduction.rst:147 +msgid "" +"If you're reading this document, you probably have a good idea of what " +"modules, extensions, and so forth are. Nevertheless, just to be sure that " +"everyone is operating from a common starting point, we offer the following " +"glossary of common Python terms:" +msgstr "" + +#: ../Doc/distutils/introduction.rst:155 +msgid "module" +msgstr "" + +#: ../Doc/distutils/introduction.rst:153 +msgid "" +"the basic unit of code reusability in Python: a block of code imported by " +"some other code. Three types of modules concern us here: pure Python " +"modules, extension modules, and packages." +msgstr "" + +#: ../Doc/distutils/introduction.rst:160 +msgid "pure Python module" +msgstr "" + +#: ../Doc/distutils/introduction.rst:158 +msgid "" +"a module written in Python and contained in a single :file:`.py` file (and " +"possibly associated :file:`.pyc` files). Sometimes referred to as a \"pure " +"module.\"" +msgstr "" + +#: ../Doc/distutils/introduction.rst:168 +msgid "extension module" +msgstr "" + +#: ../Doc/distutils/introduction.rst:163 +msgid "" +"a module written in the low-level language of the Python implementation: C/C+" +"+ for Python, Java for Jython. Typically contained in a single dynamically " +"loadable pre-compiled file, e.g. a shared object (:file:`.so`) file for " +"Python extensions on Unix, a DLL (given the :file:`.pyd` extension) for " +"Python extensions on Windows, or a Java class file for Jython extensions. " +"(Note that currently, the Distutils only handles C/C++ extensions for " +"Python.)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:173 +msgid "package" +msgstr "" + +#: ../Doc/distutils/introduction.rst:171 +msgid "" +"a module that contains other modules; typically contained in a directory in " +"the filesystem and distinguished from other directories by the presence of a " +"file :file:`__init__.py`." +msgstr "" + +#: ../Doc/distutils/introduction.rst:183 +msgid "root package" +msgstr "" + +#: ../Doc/distutils/introduction.rst:176 +msgid "" +"the root of the hierarchy of packages. (This isn't really a package, since " +"it doesn't have an :file:`__init__.py` file. But we have to call it " +"something.) The vast majority of the standard library is in the root " +"package, as are many small, standalone third-party modules that don't belong " +"to a larger module collection. Unlike regular packages, modules in the root " +"package can be found in many directories: in fact, every directory listed in " +"``sys.path`` contributes modules to the root package." +msgstr "" + +#: ../Doc/distutils/introduction.rst:188 +msgid "Distutils-specific terminology" +msgstr "" + +#: ../Doc/distutils/introduction.rst:190 +msgid "" +"The following terms apply more specifically to the domain of distributing " +"Python modules using the Distutils:" +msgstr "" + +#: ../Doc/distutils/introduction.rst:199 +msgid "module distribution" +msgstr "" + +#: ../Doc/distutils/introduction.rst:194 +msgid "" +"a collection of Python modules distributed together as a single downloadable " +"resource and meant to be installed *en masse*. Examples of some well-known " +"module distributions are NumPy, SciPy, PIL (the Python Imaging Library), or " +"mxBase. (This would be called a *package*, except that term is already " +"taken in the Python context: a single module distribution may contain zero, " +"one, or many Python packages.)" +msgstr "" + +#: ../Doc/distutils/introduction.rst:203 +msgid "pure module distribution" +msgstr "" + +#: ../Doc/distutils/introduction.rst:202 +msgid "" +"a module distribution that contains only pure Python modules and packages. " +"Sometimes referred to as a \"pure distribution.\"" +msgstr "" + +#: ../Doc/distutils/introduction.rst:207 +msgid "non-pure module distribution" +msgstr "" + +#: ../Doc/distutils/introduction.rst:206 +msgid "" +"a module distribution that contains at least one extension module. " +"Sometimes referred to as a \"non-pure distribution.\"" +msgstr "" + +#: ../Doc/distutils/introduction.rst:211 +msgid "distribution root" +msgstr "" + +#: ../Doc/distutils/introduction.rst:210 +msgid "" +"the top-level directory of your source tree (or source distribution); the " +"directory where :file:`setup.py` exists. Generally :file:`setup.py` will " +"be run from this directory." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:9 +msgid "The Python Package Index (PyPI)" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:11 +msgid "" +"The `Python Package Index (PyPI)`_ stores :ref:`meta-data ` " +"describing distributions packaged with distutils, as well as package data " +"like distribution files if a package author wishes." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:15 +msgid "" +"Distutils provides the :command:`register` and :command:`upload` commands " +"for pushing meta-data and distribution files to PyPI, respectively. See :" +"ref:`package-commands` for information on these commands." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:21 +msgid "PyPI overview" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:23 +msgid "" +"PyPI lets you submit any number of versions of your distribution to the " +"index. If you alter the meta-data for a particular version, you can submit " +"it again and the index will be updated." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:27 +msgid "" +"PyPI holds a record for each (name, version) combination submitted. The " +"first user to submit information for a given name is designated the Owner of " +"that name. Changes can be submitted through the :command:`register` command " +"or through the web interface. Owners can designate other users as Owners or " +"Maintainers. Maintainers can edit the package information, but not " +"designate new Owners or Maintainers." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:34 +msgid "" +"By default PyPI displays only the newest version of a given package. The " +"web interface lets one change this default behavior and manually select " +"which versions to display and hide." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:38 +msgid "" +"For each version, PyPI displays a home page. The home page is created from " +"the ``long_description`` which can be submitted via the :command:`register` " +"command. See :ref:`package-display` for more information." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:46 +msgid "Distutils commands" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:48 +msgid "" +"Distutils exposes two commands for submitting package data to PyPI: the :ref:" +"`register ` command for submitting meta-data to PyPI and " +"the :ref:`upload ` command for submitting distribution " +"files. Both commands read configuration data from a special file called a :" +"ref:`.pypirc file `." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:58 +msgid "The ``register`` command" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:60 +msgid "" +"The distutils command :command:`register` is used to submit your " +"distribution's meta-data to an index server. It is invoked as follows::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:65 +msgid "Distutils will respond with the following prompt::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:75 +msgid "" +"Note: if your username and password are saved locally, you will not see this " +"menu. Also, refer to :ref:`pypirc` for how to store your credentials in a :" +"file:`.pypirc` file." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:79 +msgid "" +"If you have not registered with PyPI, then you will need to do so now. You " +"should choose option 2, and enter your details as required. Soon after " +"submitting your details, you will receive an email which will be used to " +"confirm your registration." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:84 +msgid "" +"Once you are registered, you may choose option 1 from the menu. You will be " +"prompted for your PyPI username and password, and :command:`register` will " +"then submit your meta-data to the index." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:88 +msgid "" +"See :ref:`package-cmdoptions` for options to the :command:`register` command." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:94 +msgid "The ``upload`` command" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:96 +msgid "" +"The distutils command :command:`upload` pushes the distribution files to " +"PyPI." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:98 +msgid "" +"The command is invoked immediately after building one or more distribution " +"files. For example, the command ::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:103 +msgid "" +"will cause the source distribution and the Windows installer to be uploaded " +"to PyPI. Note that these will be uploaded even if they are built using an " +"earlier invocation of :file:`setup.py`, but that only distributions named on " +"the command line for the invocation including the :command:`upload` command " +"are uploaded." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:108 +msgid "" +"If a :command:`register` command was previously called in the same command, " +"and if the password was entered in the prompt, :command:`upload` will reuse " +"the entered password. This is useful if you do not want to store a password " +"in clear text in a :file:`.pypirc` file." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:113 +msgid "" +"You can use the ``--sign`` option to tell :command:`upload` to sign each " +"uploaded file using GPG (GNU Privacy Guard). The :program:`gpg` program " +"must be available for execution on the system :envvar:`PATH`. You can also " +"specify which key to use for signing using the ``--identity=name`` option." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:118 +msgid "" +"See :ref:`package-cmdoptions` for additional options to the :command:" +"`upload` command." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:125 +msgid "Additional command options" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:127 +msgid "" +"This section describes options common to both the :command:`register` and :" +"command:`upload` commands." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:130 +msgid "" +"The ``--repository`` or ``-r`` option lets you specify a PyPI server " +"different from the default. For example::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:135 +msgid "" +"For convenience, a name can be used in place of the URL when the :file:`." +"pypirc` file is configured to do so. For example::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:140 +msgid "See :ref:`pypirc` for more information on defining alternate servers." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:142 +msgid "" +"The ``--show-response`` option displays the full response text from the PyPI " +"server, which is useful when debugging problems with registering and " +"uploading." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:153 +msgid "The ``.pypirc`` file" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:155 +msgid "" +"The :command:`register` and :command:`upload` commands both check for the " +"existence of a :file:`.pypirc` file at the location :file:`$HOME/.pypirc`. " +"If this file exists, the command uses the username, password, and repository " +"URL configured in the file. The format of a :file:`.pypirc` file is as " +"follows::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:170 +msgid "" +"The *distutils* section defines an *index-servers* variable that lists the " +"name of all sections describing a repository." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:173 +msgid "Each section describing a repository defines three variables:" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:175 +msgid "*repository*, that defines the url of the PyPI server. Defaults to" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:176 +msgid "``https://www.python.org/pypi``." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:177 +msgid "*username*, which is the registered username on the PyPI server." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:179 +msgid "*password*, that will be used to authenticate. If omitted the user" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:179 +msgid "will be prompt to type it when needed." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:181 +msgid "" +"If you want to define another server a new section can be created and listed " +"in the *index-servers* variable::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:199 +msgid "" +"This allows the :command:`register` and :command:`upload` commands to be " +"called with the ``--repository`` option as described in :ref:`package-" +"cmdoptions`." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:203 +msgid "" +"Specifically, you might want to add the `PyPI Test Repository `_ to your ``.pypirc`` to facilitate testing before " +"doing your first upload to ``PyPI`` itself." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:211 +msgid "PyPI package display" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:213 +msgid "" +"The ``long_description`` field plays a special role at PyPI. It is used by " +"the server to display a home page for the registered package." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:216 +msgid "" +"If you use the `reStructuredText `_ syntax for this field, PyPI will parse it and display an HTML output " +"for the package home page." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:220 +msgid "" +"The ``long_description`` field can be attached to a text file located in the " +"package::" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:231 +msgid "" +"In that case, :file:`README.txt` is a regular reStructuredText text file " +"located in the root of the package besides :file:`setup.py`." +msgstr "" + +#: ../Doc/distutils/packageindex.rst:234 +msgid "" +"To prevent registering broken reStructuredText content, you can use the :" +"program:`rst2html` program that is provided by the :mod:`docutils` package " +"and check the ``long_description`` from the command line:" +msgstr "" + +#: ../Doc/distutils/packageindex.rst:242 +msgid "" +":mod:`docutils` will display a warning if there's something wrong with your " +"syntax. Because PyPI applies additional checks (e.g. by passing ``--no-" +"raw`` to ``rst2html.py`` in the command above), being able to run the " +"command above without warnings does not guarantee that PyPI will convert the " +"content successfully." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:5 +msgid "Writing the Setup Script" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:7 +msgid "" +"The setup script is the centre of all activity in building, distributing, " +"and installing modules using the Distutils. The main purpose of the setup " +"script is to describe your module distribution to the Distutils, so that the " +"various commands that operate on your modules do the right thing. As we saw " +"in section :ref:`distutils-simple-example` above, the setup script consists " +"mainly of a call to :func:`setup`, and most information supplied to the " +"Distutils by the module developer is supplied as keyword arguments to :func:" +"`setup`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:15 +msgid "" +"Here's a slightly more involved example, which we'll follow for the next " +"couple of sections: the Distutils' own setup script. (Keep in mind that " +"although the Distutils are included with Python 1.6 and later, they also " +"have an independent existence so that Python 1.5.2 users can use them to " +"install other module distributions. The Distutils' own setup script, shown " +"here, is used to install the package into Python 1.5.2.) ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:35 +msgid "" +"There are only two differences between this and the trivial one-file " +"distribution presented in section :ref:`distutils-simple-example`: more " +"metadata, and the specification of pure Python modules by package, rather " +"than by module. This is important since the Distutils consist of a couple " +"of dozen modules split into (so far) two packages; an explicit list of every " +"module would be tedious to generate and difficult to maintain. For more " +"information on the additional meta-data, see section :ref:`meta-data`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:43 +msgid "" +"Note that any pathnames (files or directories) supplied in the setup script " +"should be written using the Unix convention, i.e. slash-separated. The " +"Distutils will take care of converting this platform-neutral representation " +"into whatever is appropriate on your current platform before actually using " +"the pathname. This makes your setup script portable across operating " +"systems, which of course is one of the major goals of the Distutils. In " +"this spirit, all pathnames in this document are slash-separated." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:51 +msgid "" +"This, of course, only applies to pathnames given to Distutils functions. If " +"you, for example, use standard Python functions such as :func:`glob.glob` " +"or :func:`os.listdir` to specify files, you should be careful to write " +"portable code instead of hardcoding path separators::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:63 +msgid "Listing whole packages" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:65 +msgid "" +"The ``packages`` option tells the Distutils to process (build, distribute, " +"install, etc.) all pure Python modules found in each package mentioned in " +"the ``packages`` list. In order to do this, of course, there has to be a " +"correspondence between package names and directories in the filesystem. The " +"default correspondence is the most obvious one, i.e. package :mod:" +"`distutils` is found in the directory :file:`distutils` relative to the " +"distribution root. Thus, when you say ``packages = ['foo']`` in your setup " +"script, you are promising that the Distutils will find a file :file:`foo/" +"__init__.py` (which might be spelled differently on your system, but you get " +"the idea) relative to the directory where your setup script lives. If you " +"break this promise, the Distutils will issue a warning but still process the " +"broken package anyway." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:77 +msgid "" +"If you use a different convention to lay out your source directory, that's " +"no problem: you just have to supply the ``package_dir`` option to tell the " +"Distutils about your convention. For example, say you keep all Python " +"source under :file:`lib`, so that modules in the \"root package\" (i.e., not " +"in any package at all) are in :file:`lib`, modules in the :mod:`foo` package " +"are in :file:`lib/foo`, and so forth. Then you would put ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:86 +msgid "" +"in your setup script. The keys to this dictionary are package names, and an " +"empty package name stands for the root package. The values are directory " +"names relative to your distribution root. In this case, when you say " +"``packages = ['foo']``, you are promising that the file :file:`lib/foo/" +"__init__.py` exists." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:91 +msgid "" +"Another possible convention is to put the :mod:`foo` package right in :file:" +"`lib`, the :mod:`foo.bar` package in :file:`lib/bar`, etc. This would be " +"written in the setup script as ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:97 +msgid "" +"A ``package: dir`` entry in the ``package_dir`` dictionary implicitly " +"applies to all packages below *package*, so the :mod:`foo.bar` case is " +"automatically handled here. In this example, having ``packages = ['foo', " +"'foo.bar']`` tells the Distutils to look for :file:`lib/__init__.py` and :" +"file:`lib/bar/__init__.py`. (Keep in mind that although ``package_dir`` " +"applies recursively, you must explicitly list all packages in ``packages``: " +"the Distutils will *not* recursively scan your source tree looking for any " +"directory with an :file:`__init__.py` file.)" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:110 +msgid "Listing individual modules" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:112 +msgid "" +"For a small module distribution, you might prefer to list all modules rather " +"than listing packages---especially the case of a single module that goes in " +"the \"root package\" (i.e., no package at all). This simplest case was " +"shown in section :ref:`distutils-simple-example`; here is a slightly more " +"involved example::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:119 +msgid "" +"This describes two modules, one of them in the \"root\" package, the other " +"in the :mod:`pkg` package. Again, the default package/directory layout " +"implies that these two modules can be found in :file:`mod1.py` and :file:" +"`pkg/mod2.py`, and that :file:`pkg/__init__.py` exists as well. And again, " +"you can override the package/directory correspondence using the " +"``package_dir`` option." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:129 +msgid "Describing extension modules" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:131 +msgid "" +"Just as writing Python extension modules is a bit more complicated than " +"writing pure Python modules, describing them to the Distutils is a bit more " +"complicated. Unlike pure modules, it's not enough just to list modules or " +"packages and expect the Distutils to go out and find the right files; you " +"have to specify the extension name, source file(s), and any compile/link " +"requirements (include directories, libraries to link with, etc.)." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:140 +msgid "" +"All of this is done through another keyword argument to :func:`setup`, the " +"``ext_modules`` option. ``ext_modules`` is just a list of :class:" +"`~distutils.core.Extension` instances, each of which describes a single " +"extension module. Suppose your distribution includes a single extension, " +"called :mod:`foo` and implemented by :file:`foo.c`. If no additional " +"instructions to the compiler/linker are needed, describing this extension is " +"quite simple::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:150 +msgid "" +"The :class:`Extension` class can be imported from :mod:`distutils.core` " +"along with :func:`setup`. Thus, the setup script for a module distribution " +"that contains only this one extension and nothing else might be::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:160 +msgid "" +"The :class:`Extension` class (actually, the underlying extension-building " +"machinery implemented by the :command:`build_ext` command) supports a great " +"deal of flexibility in describing Python extensions, which is explained in " +"the following sections." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:167 +msgid "Extension names and packages" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:169 +msgid "" +"The first argument to the :class:`~distutils.core.Extension` constructor is " +"always the name of the extension, including any package names. For " +"example, ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:174 +msgid "describes an extension that lives in the root package, while ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:178 +msgid "" +"describes the same extension in the :mod:`pkg` package. The source files " +"and resulting object code are identical in both cases; the only difference " +"is where in the filesystem (and therefore where in Python's namespace " +"hierarchy) the resulting extension lives." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:183 +msgid "" +"If you have a number of extensions all in the same package (or all under the " +"same base package), use the ``ext_package`` keyword argument to :func:" +"`setup`. For example, ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:193 +msgid "" +"will compile :file:`foo.c` to the extension :mod:`pkg.foo`, and :file:`bar." +"c` to :mod:`pkg.subpkg.bar`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:198 +msgid "Extension source files" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:200 +msgid "" +"The second argument to the :class:`~distutils.core.Extension` constructor is " +"a list of source files. Since the Distutils currently only support C, C++, " +"and Objective-C extensions, these are normally C/C++/Objective-C source " +"files. (Be sure to use appropriate extensions to distinguish C++\\ source " +"files: :file:`.cc` and :file:`.cpp` seem to be recognized by both Unix and " +"Windows compilers.)" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:207 +msgid "" +"However, you can also include SWIG interface (:file:`.i`) files in the list; " +"the :command:`build_ext` command knows how to deal with SWIG extensions: it " +"will run SWIG on the interface file and compile the resulting C/C++ file " +"into your extension." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:214 +msgid "" +"This warning notwithstanding, options to SWIG can be currently passed like " +"this::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:223 +msgid "Or on the commandline like this::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:227 +msgid "" +"On some platforms, you can include non-source files that are processed by " +"the compiler and included in your extension. Currently, this just means " +"Windows message text (:file:`.mc`) files and resource definition (:file:`." +"rc`) files for Visual C++. These will be compiled to binary resource (:file:" +"`.res`) files and linked into the executable." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:235 +msgid "Preprocessor options" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:237 +msgid "" +"Three optional arguments to :class:`~distutils.core.Extension` will help if " +"you need to specify include directories to search or preprocessor macros to " +"define/undefine: ``include_dirs``, ``define_macros``, and ``undef_macros``." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:241 +msgid "" +"For example, if your extension requires header files in the :file:`include` " +"directory under your distribution root, use the ``include_dirs`` option::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:246 +msgid "" +"You can specify absolute directories there; if you know that your extension " +"will only be built on Unix systems with X11R6 installed to :file:`/usr`, you " +"can get away with ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:252 +msgid "" +"You should avoid this sort of non-portable usage if you plan to distribute " +"your code: it's probably better to write C code like ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:257 +msgid "" +"If you need to include header files from some other Python extension, you " +"can take advantage of the fact that header files are installed in a " +"consistent way by the Distutils :command:`install_headers` command. For " +"example, the Numerical Python header files are installed (on a standard Unix " +"installation) to :file:`/usr/local/include/python1.5/Numerical`. (The exact " +"location will differ according to your platform and Python installation.) " +"Since the Python include directory---\\ :file:`/usr/local/include/python1.5` " +"in this case---is always included in the search path when building Python " +"extensions, the best approach is to write C code like ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:269 +msgid "" +"If you must put the :file:`Numerical` include directory right into your " +"header search path, though, you can find that directory using the Distutils :" +"mod:`distutils.sysconfig` module::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:279 +msgid "" +"Even though this is quite portable---it will work on any Python " +"installation, regardless of platform---it's probably easier to just write " +"your C code in the sensible way." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:283 +msgid "" +"You can define and undefine pre-processor macros with the ``define_macros`` " +"and ``undef_macros`` options. ``define_macros`` takes a list of ``(name, " +"value)`` tuples, where ``name`` is the name of the macro to define (a " +"string) and ``value`` is its value: either a string or ``None``. (Defining " +"a macro ``FOO`` to ``None`` is the equivalent of a bare ``#define FOO`` in " +"your C source: with most compilers, this sets ``FOO`` to the string ``1``.) " +"``undef_macros`` is just a list of macros to undefine." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:291 +msgid "For example::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:298 +msgid "is the equivalent of having this at the top of every C source file::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:307 +msgid "Library options" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:309 +msgid "" +"You can also specify the libraries to link against when building your " +"extension, and the directories to search for those libraries. The " +"``libraries`` option is a list of libraries to link against, " +"``library_dirs`` is a list of directories to search for libraries at link-" +"time, and ``runtime_library_dirs`` is a list of directories to search for " +"shared (dynamically loaded) libraries at run-time." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:315 +msgid "" +"For example, if you need to link against libraries known to be in the " +"standard library search path on target systems ::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:321 +msgid "" +"If you need to link with libraries in a non-standard location, you'll have " +"to include the location in ``library_dirs``::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:328 +msgid "" +"(Again, this sort of non-portable construct should be avoided if you intend " +"to distribute your code.)" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:335 +msgid "Other options" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:337 +msgid "" +"There are still some other options which can be used to handle special cases." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:339 +msgid "" +"The ``optional`` option is a boolean; if it is true, a build failure in the " +"extension will not abort the build process, but instead simply not install " +"the failing extension." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:343 +msgid "" +"The ``extra_objects`` option is a list of object files to be passed to the " +"linker. These files must not have extensions, as the default extension for " +"the compiler is used." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:347 +msgid "" +"``extra_compile_args`` and ``extra_link_args`` can be used to specify " +"additional command line options for the respective compiler and linker " +"command lines." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:351 +msgid "" +"``export_symbols`` is only useful on Windows. It can contain a list of " +"symbols (functions or variables) to be exported. This option is not needed " +"when building compiled extensions: Distutils will automatically add " +"``initmodule`` to the list of exported symbols." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:356 +msgid "" +"The ``depends`` option is a list of files that the extension depends on (for " +"example header files). The build command will call the compiler on the " +"sources to rebuild extension if any on this files has been modified since " +"the previous build." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:362 +msgid "Relationships between Distributions and Packages" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:364 +msgid "A distribution may relate to packages in three specific ways:" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:366 +msgid "It can require packages or modules." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:368 +msgid "It can provide packages or modules." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:370 +msgid "It can obsolete packages or modules." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:372 +msgid "" +"These relationships can be specified using keyword arguments to the :func:" +"`distutils.core.setup` function." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:375 +msgid "" +"Dependencies on other Python modules and packages can be specified by " +"supplying the *requires* keyword argument to :func:`setup`. The value must " +"be a list of strings. Each string specifies a package that is required, and " +"optionally what versions are sufficient." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:380 +msgid "" +"To specify that any version of a module or package is required, the string " +"should consist entirely of the module or package name. Examples include " +"``'mymodule'`` and ``'xml.parsers.expat'``." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:384 +msgid "" +"If specific versions are required, a sequence of qualifiers can be supplied " +"in parentheses. Each qualifier may consist of a comparison operator and a " +"version number. The accepted comparison operators are::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:391 +msgid "" +"These can be combined by using multiple qualifiers separated by commas (and " +"optional whitespace). In this case, all of the qualifiers must be matched; " +"a logical AND is used to combine the evaluations." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:395 +msgid "Let's look at a bunch of examples:" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:398 +msgid "Requires Expression" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:398 ../Doc/distutils/setupscript.rst:416 +msgid "Explanation" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:400 +msgid "``==1.0``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:400 +msgid "Only version ``1.0`` is compatible" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:402 +msgid "``>1.0, !=1.5.1, <2.0``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:402 +msgid "" +"Any version after ``1.0`` and before ``2.0`` is compatible, except ``1.5.1``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:406 +msgid "" +"Now that we can specify dependencies, we also need to be able to specify " +"what we provide that other distributions can require. This is done using " +"the *provides* keyword argument to :func:`setup`. The value for this keyword " +"is a list of strings, each of which names a Python module or package, and " +"optionally identifies the version. If the version is not specified, it is " +"assumed to match that of the distribution." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:413 +msgid "Some examples:" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:416 +msgid "Provides Expression" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:418 +msgid "``mypkg``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:418 +msgid "Provide ``mypkg``, using the distribution version" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:421 +msgid "``mypkg (1.1)``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:421 +msgid "Provide ``mypkg`` version 1.1, regardless of the distribution version" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:425 +msgid "" +"A package can declare that it obsoletes other packages using the *obsoletes* " +"keyword argument. The value for this is similar to that of the *requires* " +"keyword: a list of strings giving module or package specifiers. Each " +"specifier consists of a module or package name optionally followed by one or " +"more version qualifiers. Version qualifiers are given in parentheses after " +"the module or package name." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:432 +msgid "" +"The versions identified by the qualifiers are those that are obsoleted by " +"the distribution being described. If no qualifiers are given, all versions " +"of the named module or package are understood to be obsoleted." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:439 +msgid "Installing Scripts" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:441 +msgid "" +"So far we have been dealing with pure and non-pure Python modules, which are " +"usually not run by themselves but imported by scripts." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:444 +msgid "" +"Scripts are files containing Python source code, intended to be started from " +"the command line. Scripts don't require Distutils to do anything very " +"complicated. The only clever feature is that if the first line of the script " +"starts with ``#!`` and contains the word \"python\", the Distutils will " +"adjust the first line to refer to the current interpreter location. By " +"default, it is replaced with the current interpreter location. The :option:" +"`--executable` (or :option:`-e`) option will allow the interpreter path to " +"be explicitly overridden." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:452 +msgid "" +"The ``scripts`` option simply is a list of files to be handled in this way. " +"From the PyXML setup script::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:459 +msgid "" +"All the scripts will also be added to the ``MANIFEST`` file if no template " +"is provided. See :ref:`manifest`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:467 +msgid "Installing Package Data" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:469 +msgid "" +"Often, additional files need to be installed into a package. These files " +"are often data that's closely related to the package's implementation, or " +"text files containing documentation that might be of interest to programmers " +"using the package. These files are called :dfn:`package data`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:474 +msgid "" +"Package data can be added to packages using the ``package_data`` keyword " +"argument to the :func:`setup` function. The value must be a mapping from " +"package name to a list of relative path names that should be copied into the " +"package. The paths are interpreted as relative to the directory containing " +"the package (information from the ``package_dir`` mapping is used if " +"appropriate); that is, the files are expected to be part of the package in " +"the source directories. They may contain glob patterns as well." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:482 +msgid "" +"The path names may contain directory portions; any necessary directories " +"will be created in the installation." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:485 +msgid "" +"For example, if a package should contain a subdirectory with several data " +"files, the files can be arranged like this in the source tree::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:498 +msgid "The corresponding call to :func:`setup` might be::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:507 +msgid "" +"All the files that match ``package_data`` will be added to the ``MANIFEST`` " +"file if no template is provided. See :ref:`manifest`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:515 +msgid "Installing Additional Files" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:517 +msgid "" +"The ``data_files`` option can be used to specify additional files needed by " +"the module distribution: configuration files, message catalogs, data files, " +"anything which doesn't fit in the previous categories." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:521 +msgid "" +"``data_files`` specifies a sequence of (*directory*, *files*) pairs in the " +"following way::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:530 +msgid "" +"Note that you can specify the directory names where the data files will be " +"installed, but you cannot rename the data files themselves." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:533 +msgid "" +"Each (*directory*, *files*) pair in the sequence specifies the installation " +"directory and the files to install there. If *directory* is a relative " +"path, it is interpreted relative to the installation prefix (Python's ``sys." +"prefix`` for pure-Python packages, ``sys.exec_prefix`` for packages that " +"contain extension modules). Each file name in *files* is interpreted " +"relative to the :file:`setup.py` script at the top of the package source " +"distribution. No directory information from *files* is used to determine " +"the final location of the installed file; only the name of the file is used." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:542 +msgid "" +"You can specify the ``data_files`` options as a simple sequence of files " +"without specifying a target directory, but this is not recommended, and the :" +"command:`install` command will print a warning in this case. To install data " +"files directly in the target directory, an empty string should be given as " +"the directory." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:548 +msgid "" +"All the files that match ``data_files`` will be added to the ``MANIFEST`` " +"file if no template is provided. See :ref:`manifest`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:556 +msgid "Additional meta-data" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:558 +msgid "" +"The setup script may include additional meta-data beyond the name and " +"version. This information includes:" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:562 +msgid "Meta-Data" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:562 +msgid "Value" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:564 +msgid "name of the package" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:564 ../Doc/distutils/setupscript.rst:566 +#: ../Doc/distutils/setupscript.rst:568 ../Doc/distutils/setupscript.rst:573 +#: ../Doc/distutils/setupscript.rst:580 ../Doc/distutils/setupscript.rst:594 +msgid "short string" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:566 +msgid "version of this release" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:566 +msgid "(1)(2)" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:568 +msgid "``author``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:568 +msgid "package author's name" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:570 +msgid "``author_email``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:570 +msgid "email address of the package author" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:570 ../Doc/distutils/setupscript.rst:575 +msgid "email address" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:573 +msgid "``maintainer``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:573 +msgid "package maintainer's name" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:575 +msgid "``maintainer_email``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:575 +msgid "email address of the package maintainer" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:578 +msgid "home page for the package" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:578 ../Doc/distutils/setupscript.rst:587 +msgid "URL" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:580 +msgid "short, summary description of the package" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:584 +msgid "longer description of the package" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:584 +msgid "long string" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:587 +msgid "``download_url``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:587 +msgid "location where the package may be downloaded" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:590 +msgid "``classifiers``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:590 +msgid "a list of classifiers" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:590 ../Doc/distutils/setupscript.rst:592 +msgid "list of strings" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:592 +msgid "``platforms``" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:592 +msgid "a list of platforms" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:594 +msgid "license for the package" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:594 +msgid "\\(6)" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:600 +msgid "These fields are required." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:603 +msgid "" +"It is recommended that versions take the form *major.minor[.patch[.sub]]*." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:606 +msgid "" +"Either the author or the maintainer must be identified. If maintainer is " +"provided, distutils lists it as the author in :file:`PKG-INFO`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:610 +msgid "" +"These fields should not be used if your package is to be compatible with " +"Python versions prior to 2.2.3 or 2.3. The list is available from the `PyPI " +"website `_." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:615 +msgid "" +"The ``long_description`` field is used by PyPI when you are :ref:" +"`registering ` a package, to :ref:`build its home page " +"`." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:620 +msgid "" +"The ``license`` field is a text indicating the license covering the package " +"where the license is not a selection from the \"License\" Trove classifiers. " +"See the ``Classifier`` field. Notice that there's a ``licence`` distribution " +"option which is deprecated but still acts as an alias for ``license``." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:627 +msgid "'short string'" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:627 +msgid "A single line of text, not more than 200 characters." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:631 +msgid "'long string'" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:630 +msgid "" +"Multiple lines of plain text in reStructuredText format (see http://docutils." +"sourceforge.net/)." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:634 +msgid "'list of strings'" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:634 +msgid "See below." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:636 +msgid "" +"Encoding the version information is an art in itself. Python packages " +"generally adhere to the version format *major.minor[.patch][sub]*. The major " +"number is 0 for initial, experimental releases of software. It is " +"incremented for releases that represent major milestones in a package. The " +"minor number is incremented when important new features are added to the " +"package. The patch number increments when bug-fix releases are made. " +"Additional trailing version information is sometimes used to indicate sub-" +"releases. These are \"a1,a2,...,aN\" (for alpha releases, where " +"functionality and API may change), \"b1,b2,...,bN\" (for beta releases, " +"which only fix bugs) and \"pr1,pr2,...,prN\" (for final pre-release release " +"testing). Some examples:" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:648 +msgid "0.1.0" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:648 +msgid "the first, experimental release of a package" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:651 +msgid "1.0.1a2" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:651 +msgid "the second alpha release of the first patch version of 1.0" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:653 +msgid "``classifiers`` are specified in a Python list::" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:677 +msgid "Debugging the setup script" +msgstr "" + +#: ../Doc/distutils/setupscript.rst:679 +msgid "" +"Sometimes things go wrong, and the setup script doesn't do what the " +"developer wants." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:682 +msgid "" +"Distutils catches any exceptions when running the setup script, and print a " +"simple error message before the script is terminated. The motivation for " +"this behaviour is to not confuse administrators who don't know much about " +"Python and are trying to install a package. If they get a big long " +"traceback from deep inside the guts of Distutils, they may think the package " +"or the Python installation is broken because they don't read all the way " +"down to the bottom and see that it's a permission problem." +msgstr "" + +#: ../Doc/distutils/setupscript.rst:690 +msgid "" +"On the other hand, this doesn't help the developer to find the cause of the " +"failure. For this purpose, the :envvar:`DISTUTILS_DEBUG` environment " +"variable can be set to anything except an empty string, and distutils will " +"now print detailed information about what it is doing, dump the full " +"traceback when an exception occurs, and print the whole command line when an " +"external program (like a C compiler) fails." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:5 +msgid "Creating a Source Distribution" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:7 +msgid "" +"As shown in section :ref:`distutils-simple-example`, you use the :command:" +"`sdist` command to create a source distribution. In the simplest case, ::" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:12 +msgid "" +"(assuming you haven't specified any :command:`sdist` options in the setup " +"script or config file), :command:`sdist` creates the archive of the default " +"format for the current platform. The default format is a gzip'ed tar file (:" +"file:`.tar.gz`) on Unix, and ZIP file on Windows." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:17 +msgid "" +"You can specify as many formats as you like using the :option:`--formats` " +"option, for example::" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:22 +msgid "to create a gzipped tarball and a zip file. The available formats are:" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:27 +msgid "(1),(3)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:29 +msgid "gzip'ed tar file (:file:`.tar.gz`)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:29 +msgid "\\(2)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:32 +msgid "bzip2'ed tar file (:file:`.tar.bz2`)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:35 +msgid "xz'ed tar file (:file:`.tar.xz`)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:60 +msgid "" +"requires the :program:`compress` program. Notice that this format is now " +"pending for deprecation and will be removed in the future versions of Python." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:63 +msgid "" +"When using any ``tar`` format (``gztar``, ``bztar``, ``xztar``, ``ztar`` or " +"``tar``), under Unix you can specify the ``owner`` and ``group`` names that " +"will be set for each member of the archive." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:67 +msgid "For example, if you want all files of the archive to be owned by root::" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:75 +msgid "Specifying the files to distribute" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:77 +msgid "" +"If you don't supply an explicit list of files (or instructions on how to " +"generate one), the :command:`sdist` command puts a minimal default set into " +"the source distribution:" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:81 +msgid "" +"all Python source files implied by the ``py_modules`` and ``packages`` " +"options" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:84 +msgid "" +"all C source files mentioned in the ``ext_modules`` or ``libraries`` options" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:90 +msgid "" +"scripts identified by the ``scripts`` option See :ref:`distutils-installing-" +"scripts`." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:93 +msgid "" +"anything that looks like a test script: :file:`test/test\\*.py` (currently, " +"the Distutils don't do anything with test scripts except include them in " +"source distributions, but in the future there will be a standard for testing " +"Python module distributions)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:98 +msgid "" +":file:`README.txt` (or :file:`README`), :file:`setup.py` (or whatever you " +"called your setup script), and :file:`setup.cfg`" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:101 +msgid "" +"all files that matches the ``package_data`` metadata. See :ref:`distutils-" +"installing-package-data`." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:104 +msgid "" +"all files that matches the ``data_files`` metadata. See :ref:`distutils-" +"additional-files`." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:107 +msgid "" +"Sometimes this is enough, but usually you will want to specify additional " +"files to distribute. The typical way to do this is to write a *manifest " +"template*, called :file:`MANIFEST.in` by default. The manifest template is " +"just a list of instructions for how to generate your manifest file, :file:" +"`MANIFEST`, which is the exact list of files to include in your source " +"distribution. The :command:`sdist` command processes this template and " +"generates a manifest based on its instructions and what it finds in the " +"filesystem." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:115 +msgid "" +"If you prefer to roll your own manifest file, the format is simple: one " +"filename per line, regular files (or symlinks to them) only. If you do " +"supply your own :file:`MANIFEST`, you must specify everything: the default " +"set of files described above does not apply in this case." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:120 +msgid "" +"An existing generated :file:`MANIFEST` will be regenerated without :command:" +"`sdist` comparing its modification time to the one of :file:`MANIFEST.in` " +"or :file:`setup.py`." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:125 +msgid "" +":file:`MANIFEST` files start with a comment indicating they are generated. " +"Files without this comment are not overwritten or removed." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:129 +msgid "" +":command:`sdist` will read a :file:`MANIFEST` file if no :file:`MANIFEST.in` " +"exists, like it used to do." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:134 +msgid "" +"The manifest template has one command per line, where each command specifies " +"a set of files to include or exclude from the source distribution. For an " +"example, again we turn to the Distutils' own manifest template:" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:144 +msgid "" +"The meanings should be fairly clear: include all files in the distribution " +"root matching :file:`\\*.txt`, all files anywhere under the :file:`examples` " +"directory matching :file:`\\*.txt` or :file:`\\*.py`, and exclude all " +"directories matching :file:`examples/sample?/build`. All of this is done " +"*after* the standard include set, so you can exclude files from the standard " +"set with explicit instructions in the manifest template. (Or, you can use " +"the :option:`--no-defaults` option to disable the standard set entirely.) " +"There are several other commands available in the manifest template mini-" +"language; see section :ref:`sdist-cmd`." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:154 +msgid "" +"The order of commands in the manifest template matters: initially, we have " +"the list of default files as described above, and each command in the " +"template adds to or removes from that list of files. Once we have fully " +"processed the manifest template, we remove files that should not be included " +"in the source distribution:" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:160 +msgid "all files in the Distutils \"build\" tree (default :file:`build/`)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:162 +msgid "" +"all files in directories named :file:`RCS`, :file:`CVS`, :file:`.svn`, :file:" +"`.hg`, :file:`.git`, :file:`.bzr` or :file:`_darcs`" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:165 +msgid "" +"Now we have our complete list of files, which is written to the manifest for " +"future reference, and then used to build the source distribution archive(s)." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:168 +msgid "" +"You can disable the default set of included files with the :option:`--no-" +"defaults` option, and you can disable the standard exclude set with :option:" +"`--no-prune`." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:172 +msgid "" +"Following the Distutils' own manifest template, let's trace how the :command:" +"`sdist` command builds the list of files to include in the Distutils source " +"distribution:" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:176 +msgid "" +"include all Python source files in the :file:`distutils` and :file:" +"`distutils/command` subdirectories (because packages corresponding to those " +"two directories were mentioned in the ``packages`` option in the setup " +"script---see section :ref:`setup-script`)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:181 +msgid "" +"include :file:`README.txt`, :file:`setup.py`, and :file:`setup.cfg` " +"(standard files)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:184 +msgid "include :file:`test/test\\*.py` (standard files)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:186 +msgid "" +"include :file:`\\*.txt` in the distribution root (this will find :file:" +"`README.txt` a second time, but such redundancies are weeded out later)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:189 +msgid "" +"include anything matching :file:`\\*.txt` or :file:`\\*.py` in the sub-tree " +"under :file:`examples`," +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:192 +msgid "" +"exclude all files in the sub-trees starting at directories matching :file:" +"`examples/sample?/build`\\ ---this may exclude files included by the " +"previous two steps, so it's important that the ``prune`` command in the " +"manifest template comes after the ``recursive-include`` command" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:197 +msgid "" +"exclude the entire :file:`build` tree, and any :file:`RCS`, :file:`CVS`, :" +"file:`.svn`, :file:`.hg`, :file:`.git`, :file:`.bzr` and :file:`_darcs` " +"directories" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:201 +msgid "" +"Just like in the setup script, file and directory names in the manifest " +"template should always be slash-separated; the Distutils will take care of " +"converting them to the standard representation on your platform. That way, " +"the manifest template is portable across operating systems." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:210 +msgid "Manifest-related options" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:212 +msgid "" +"The normal course of operations for the :command:`sdist` command is as " +"follows:" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:214 +msgid "" +"if the manifest file (:file:`MANIFEST` by default) exists and the first line " +"does not have a comment indicating it is generated from :file:`MANIFEST.in`, " +"then it is used as is, unaltered" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:218 +msgid "" +"if the manifest file doesn't exist or has been previously automatically " +"generated, read :file:`MANIFEST.in` and create the manifest" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:221 +msgid "" +"if neither :file:`MANIFEST` nor :file:`MANIFEST.in` exist, create a manifest " +"with just the default file set" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:224 +msgid "" +"use the list of files now in :file:`MANIFEST` (either just generated or read " +"in) to create the source distribution archive(s)" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:227 +msgid "" +"There are a couple of options that modify this behaviour. First, use the :" +"option:`--no-defaults` and :option:`--no-prune` to disable the standard " +"\"include\" and \"exclude\" sets." +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:231 +msgid "" +"Second, you might just want to (re)generate the manifest, but not create a " +"source distribution::" +msgstr "" + +#: ../Doc/distutils/sourcedist.rst:236 +msgid ":option:`-o` is a shortcut for :option:`--manifest-only`." +msgstr "" + +#: ../Doc/distutils/uploading.rst:5 +msgid "Uploading Packages to the Package Index" +msgstr "" + +#: ../Doc/distutils/uploading.rst:7 +msgid "" +"The contents of this page have moved to the section :ref:`package-index`." +msgstr "" diff --git a/extending.po b/extending.po new file mode 100644 index 00000000..aa9e2d07 --- /dev/null +++ b/extending.po @@ -0,0 +1,3381 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/extending/building.rst:7 +msgid "Building C and C++ Extensions" +msgstr "" + +#: ../Doc/extending/building.rst:9 +msgid "" +"A C extension for CPython is a shared library (e.g. a ``.so`` file on Linux, " +"``.pyd`` on Windows), which exports an *initialization function*." +msgstr "" + +#: ../Doc/extending/building.rst:12 +msgid "" +"To be importable, the shared library must be available on :envvar:" +"`PYTHONPATH`, and must be named after the module name, with an appropriate " +"extension. When using distutils, the correct filename is generated " +"automatically." +msgstr "" + +#: ../Doc/extending/building.rst:16 +msgid "The initialization function has the signature:" +msgstr "" + +#: ../Doc/extending/building.rst:20 +msgid "" +"It returns either a fully-initialized module, or a :c:type:`PyModuleDef` " +"instance. See :ref:`initializing-modules` for details." +msgstr "" + +#: ../Doc/extending/building.rst:25 +msgid "" +"For modules with ASCII-only names, the function must be named " +"``PyInit_``, with ```` replaced by the name of the " +"module. When using :ref:`multi-phase-initialization`, non-ASCII module names " +"are allowed. In this case, the initialization function name is " +"``PyInitU_``, with ```` encoded using Python's " +"*punycode* encoding with hyphens replaced by underscores. In Python::" +msgstr "" + +#: ../Doc/extending/building.rst:39 +msgid "" +"It is possible to export multiple modules from a single shared library by " +"defining multiple initialization functions. However, importing them requires " +"using symbolic links or a custom importer, because by default only the " +"function corresponding to the filename is found. See the *\"Multiple modules " +"in one library\"* section in :pep:`489` for details." +msgstr "" + +#: ../Doc/extending/building.rst:49 +msgid "Building C and C++ Extensions with distutils" +msgstr "" + +#: ../Doc/extending/building.rst:53 +msgid "" +"Extension modules can be built using distutils, which is included in " +"Python. Since distutils also supports creation of binary packages, users " +"don't necessarily need a compiler and distutils to install the extension." +msgstr "" + +#: ../Doc/extending/building.rst:57 +msgid "" +"A distutils package contains a driver script, :file:`setup.py`. This is a " +"plain Python file, which, in the most simple case, could look like this:" +msgstr "" + +#: ../Doc/extending/building.rst:73 +msgid "With this :file:`setup.py`, and a file :file:`demo.c`, running ::" +msgstr "" + +#: ../Doc/extending/building.rst:77 +msgid "" +"will compile :file:`demo.c`, and produce an extension module named ``demo`` " +"in the :file:`build` directory. Depending on the system, the module file " +"will end up in a subdirectory :file:`build/lib.system`, and may have a name " +"like :file:`demo.so` or :file:`demo.pyd`." +msgstr "" + +#: ../Doc/extending/building.rst:82 +msgid "" +"In the :file:`setup.py`, all execution is performed by calling the ``setup`` " +"function. This takes a variable number of keyword arguments, of which the " +"example above uses only a subset. Specifically, the example specifies meta-" +"information to build packages, and it specifies the contents of the " +"package. Normally, a package will contain additional modules, like Python " +"source modules, documentation, subpackages, etc. Please refer to the " +"distutils documentation in :ref:`distutils-index` to learn more about the " +"features of distutils; this section explains building extension modules only." +msgstr "" + +#: ../Doc/extending/building.rst:91 +msgid "" +"It is common to pre-compute arguments to :func:`setup`, to better structure " +"the driver script. In the example above, the ``ext_modules`` argument to :" +"func:`~distutils.core.setup` is a list of extension modules, each of which " +"is an instance of the :class:`~distutils.extension.Extension`. In the " +"example, the instance defines an extension named ``demo`` which is build by " +"compiling a single source file, :file:`demo.c`." +msgstr "" + +#: ../Doc/extending/building.rst:99 +msgid "" +"In many cases, building an extension is more complex, since additional " +"preprocessor defines and libraries may be needed. This is demonstrated in " +"the example below." +msgstr "" + +#: ../Doc/extending/building.rst:127 +msgid "" +"In this example, :func:`~distutils.core.setup` is called with additional " +"meta-information, which is recommended when distribution packages have to be " +"built. For the extension itself, it specifies preprocessor defines, include " +"directories, library directories, and libraries. Depending on the compiler, " +"distutils passes this information in different ways to the compiler. For " +"example, on Unix, this may result in the compilation commands ::" +msgstr "" + +#: ../Doc/extending/building.rst:139 +msgid "" +"These lines are for demonstration purposes only; distutils users should " +"trust that distutils gets the invocations right." +msgstr "" + +#: ../Doc/extending/building.rst:146 +msgid "Distributing your extension modules" +msgstr "" + +#: ../Doc/extending/building.rst:148 +msgid "" +"When an extension has been successfully build, there are three ways to use " +"it." +msgstr "" + +#: ../Doc/extending/building.rst:150 +msgid "" +"End-users will typically want to install the module, they do so by running ::" +msgstr "" + +#: ../Doc/extending/building.rst:154 +msgid "" +"Module maintainers should produce source packages; to do so, they run ::" +msgstr "" + +#: ../Doc/extending/building.rst:158 +msgid "" +"In some cases, additional files need to be included in a source " +"distribution; this is done through a :file:`MANIFEST.in` file; see :ref:" +"`manifest` for details." +msgstr "" + +#: ../Doc/extending/building.rst:161 +msgid "" +"If the source distribution has been build successfully, maintainers can also " +"create binary distributions. Depending on the platform, one of the following " +"commands can be used to do so. ::" +msgstr "" + +#: ../Doc/extending/embedding.rst:8 +msgid "Embedding Python in Another Application" +msgstr "" + +#: ../Doc/extending/embedding.rst:10 +msgid "" +"The previous chapters discussed how to extend Python, that is, how to extend " +"the functionality of Python by attaching a library of C functions to it. It " +"is also possible to do it the other way around: enrich your C/C++ " +"application by embedding Python in it. Embedding provides your application " +"with the ability to implement some of the functionality of your application " +"in Python rather than C or C++. This can be used for many purposes; one " +"example would be to allow users to tailor the application to their needs by " +"writing some scripts in Python. You can also use it yourself if some of the " +"functionality can be written in Python more easily." +msgstr "" + +#: ../Doc/extending/embedding.rst:20 +msgid "" +"Embedding Python is similar to extending it, but not quite. The difference " +"is that when you extend Python, the main program of the application is still " +"the Python interpreter, while if you embed Python, the main program may have " +"nothing to do with Python --- instead, some parts of the application " +"occasionally call the Python interpreter to run some Python code." +msgstr "" + +#: ../Doc/extending/embedding.rst:26 +msgid "" +"So if you are embedding Python, you are providing your own main program. " +"One of the things this main program has to do is initialize the Python " +"interpreter. At the very least, you have to call the function :c:func:" +"`Py_Initialize`. There are optional calls to pass command line arguments to " +"Python. Then later you can call the interpreter from any part of the " +"application." +msgstr "" + +#: ../Doc/extending/embedding.rst:32 +msgid "" +"There are several different ways to call the interpreter: you can pass a " +"string containing Python statements to :c:func:`PyRun_SimpleString`, or you " +"can pass a stdio file pointer and a file name (for identification in error " +"messages only) to :c:func:`PyRun_SimpleFile`. You can also call the lower-" +"level operations described in the previous chapters to construct and use " +"Python objects." +msgstr "" + +#: ../Doc/extending/embedding.rst:42 +msgid ":ref:`c-api-index`" +msgstr "" + +#: ../Doc/extending/embedding.rst:42 +msgid "" +"The details of Python's C interface are given in this manual. A great deal " +"of necessary information can be found here." +msgstr "" + +#: ../Doc/extending/embedding.rst:49 +msgid "Very High Level Embedding" +msgstr "" + +#: ../Doc/extending/embedding.rst:51 +msgid "" +"The simplest form of embedding Python is the use of the very high level " +"interface. This interface is intended to execute a Python script without " +"needing to interact with the application directly. This can for example be " +"used to perform some operation on a file. ::" +msgstr "" + +#: ../Doc/extending/embedding.rst:77 +msgid "" +"The :c:func:`Py_SetProgramName` function should be called before :c:func:" +"`Py_Initialize` to inform the interpreter about paths to Python run-time " +"libraries. Next, the Python interpreter is initialized with :c:func:" +"`Py_Initialize`, followed by the execution of a hard-coded Python script " +"that prints the date and time. Afterwards, the :c:func:`Py_FinalizeEx` call " +"shuts the interpreter down, followed by the end of the program. In a real " +"program, you may want to get the Python script from another source, perhaps " +"a text-editor routine, a file, or a database. Getting the Python code from " +"a file can better be done by using the :c:func:`PyRun_SimpleFile` function, " +"which saves you the trouble of allocating memory space and loading the file " +"contents." +msgstr "" + +#: ../Doc/extending/embedding.rst:92 +msgid "Beyond Very High Level Embedding: An overview" +msgstr "" + +#: ../Doc/extending/embedding.rst:94 +msgid "" +"The high level interface gives you the ability to execute arbitrary pieces " +"of Python code from your application, but exchanging data values is quite " +"cumbersome to say the least. If you want that, you should use lower level " +"calls. At the cost of having to write more C code, you can achieve almost " +"anything." +msgstr "" + +#: ../Doc/extending/embedding.rst:99 +msgid "" +"It should be noted that extending Python and embedding Python is quite the " +"same activity, despite the different intent. Most topics discussed in the " +"previous chapters are still valid. To show this, consider what the extension " +"code from Python to C really does:" +msgstr "" + +#: ../Doc/extending/embedding.rst:104 +msgid "Convert data values from Python to C," +msgstr "" + +#: ../Doc/extending/embedding.rst:106 +msgid "Perform a function call to a C routine using the converted values, and" +msgstr "" + +#: ../Doc/extending/embedding.rst:108 +msgid "Convert the data values from the call from C to Python." +msgstr "" + +#: ../Doc/extending/embedding.rst:110 +msgid "When embedding Python, the interface code does:" +msgstr "" + +#: ../Doc/extending/embedding.rst:112 +msgid "Convert data values from C to Python," +msgstr "" + +#: ../Doc/extending/embedding.rst:114 +msgid "" +"Perform a function call to a Python interface routine using the converted " +"values, and" +msgstr "" + +#: ../Doc/extending/embedding.rst:117 +msgid "Convert the data values from the call from Python to C." +msgstr "" + +#: ../Doc/extending/embedding.rst:119 +msgid "" +"As you can see, the data conversion steps are simply swapped to accommodate " +"the different direction of the cross-language transfer. The only difference " +"is the routine that you call between both data conversions. When extending, " +"you call a C routine, when embedding, you call a Python routine." +msgstr "" + +#: ../Doc/extending/embedding.rst:124 +msgid "" +"This chapter will not discuss how to convert data from Python to C and vice " +"versa. Also, proper use of references and dealing with errors is assumed to " +"be understood. Since these aspects do not differ from extending the " +"interpreter, you can refer to earlier chapters for the required information." +msgstr "" + +#: ../Doc/extending/embedding.rst:133 +msgid "Pure Embedding" +msgstr "" + +#: ../Doc/extending/embedding.rst:135 +msgid "" +"The first program aims to execute a function in a Python script. Like in the " +"section about the very high level interface, the Python interpreter does not " +"directly interact with the application (but that will change in the next " +"section)." +msgstr "" + +#: ../Doc/extending/embedding.rst:140 +msgid "The code to run a function defined in a Python script is:" +msgstr "" + +#: ../Doc/extending/embedding.rst:145 +msgid "" +"This code loads a Python script using ``argv[1]``, and calls the function " +"named in ``argv[2]``. Its integer arguments are the other values of the " +"``argv`` array. If you :ref:`compile and link ` this program " +"(let's call the finished executable :program:`call`), and use it to execute " +"a Python script, such as:" +msgstr "" + +#: ../Doc/extending/embedding.rst:160 +msgid "then the result should be:" +msgstr "" + +#: ../Doc/extending/embedding.rst:168 +msgid "" +"Although the program is quite large for its functionality, most of the code " +"is for data conversion between Python and C, and for error reporting. The " +"interesting part with respect to embedding Python starts with ::" +msgstr "" + +#: ../Doc/extending/embedding.rst:177 +msgid "" +"After initializing the interpreter, the script is loaded using :c:func:" +"`PyImport_Import`. This routine needs a Python string as its argument, " +"which is constructed using the :c:func:`PyUnicode_FromString` data " +"conversion routine. ::" +msgstr "" + +#: ../Doc/extending/embedding.rst:190 +msgid "" +"Once the script is loaded, the name we're looking for is retrieved using :c:" +"func:`PyObject_GetAttrString`. If the name exists, and the object returned " +"is callable, you can safely assume that it is a function. The program then " +"proceeds by constructing a tuple of arguments as normal. The call to the " +"Python function is then made with::" +msgstr "" + +#: ../Doc/extending/embedding.rst:198 +msgid "" +"Upon return of the function, ``pValue`` is either *NULL* or it contains a " +"reference to the return value of the function. Be sure to release the " +"reference after examining the value." +msgstr "" + +#: ../Doc/extending/embedding.rst:206 +msgid "Extending Embedded Python" +msgstr "" + +#: ../Doc/extending/embedding.rst:208 +msgid "" +"Until now, the embedded Python interpreter had no access to functionality " +"from the application itself. The Python API allows this by extending the " +"embedded interpreter. That is, the embedded interpreter gets extended with " +"routines provided by the application. While it sounds complex, it is not so " +"bad. Simply forget for a while that the application starts the Python " +"interpreter. Instead, consider the application to be a set of subroutines, " +"and write some glue code that gives Python access to those routines, just " +"like you would write a normal Python extension. For example::" +msgstr "" + +#: ../Doc/extending/embedding.rst:245 +msgid "" +"Insert the above code just above the :c:func:`main` function. Also, insert " +"the following two statements before the call to :c:func:`Py_Initialize`::" +msgstr "" + +#: ../Doc/extending/embedding.rst:251 +msgid "" +"These two lines initialize the ``numargs`` variable, and make the :func:`emb." +"numargs` function accessible to the embedded Python interpreter. With these " +"extensions, the Python script can do things like" +msgstr "" + +#: ../Doc/extending/embedding.rst:260 +msgid "" +"In a real application, the methods will expose an API of the application to " +"Python." +msgstr "" + +#: ../Doc/extending/embedding.rst:270 +msgid "Embedding Python in C++" +msgstr "" + +#: ../Doc/extending/embedding.rst:272 +msgid "" +"It is also possible to embed Python in a C++ program; precisely how this is " +"done will depend on the details of the C++ system used; in general you will " +"need to write the main program in C++, and use the C++ compiler to compile " +"and link your program. There is no need to recompile Python itself using C+" +"+." +msgstr "" + +#: ../Doc/extending/embedding.rst:281 +msgid "Compiling and Linking under Unix-like systems" +msgstr "" + +#: ../Doc/extending/embedding.rst:283 +msgid "" +"It is not necessarily trivial to find the right flags to pass to your " +"compiler (and linker) in order to embed the Python interpreter into your " +"application, particularly because Python needs to load library modules " +"implemented as C dynamic extensions (:file:`.so` files) linked against it." +msgstr "" + +#: ../Doc/extending/embedding.rst:289 +msgid "" +"To find out the required compiler and linker flags, you can execute the :" +"file:`python{X.Y}-config` script which is generated as part of the " +"installation process (a :file:`python3-config` script may also be " +"available). This script has several options, of which the following will be " +"directly useful to you:" +msgstr "" + +#: ../Doc/extending/embedding.rst:295 +msgid "" +"``pythonX.Y-config --cflags`` will give you the recommended flags when " +"compiling:" +msgstr "" + +#: ../Doc/extending/embedding.rst:303 +msgid "" +"``pythonX.Y-config --ldflags`` will give you the recommended flags when " +"linking:" +msgstr "" + +#: ../Doc/extending/embedding.rst:312 +msgid "" +"To avoid confusion between several Python installations (and especially " +"between the system Python and your own compiled Python), it is recommended " +"that you use the absolute path to :file:`python{X.Y}-config`, as in the " +"above example." +msgstr "" + +#: ../Doc/extending/embedding.rst:317 +msgid "" +"If this procedure doesn't work for you (it is not guaranteed to work for all " +"Unix-like platforms; however, we welcome :ref:`bug reports `) you will have to read your system's documentation about dynamic " +"linking and/or examine Python's :file:`Makefile` (use :func:`sysconfig." +"get_makefile_filename` to find its location) and compilation options. In " +"this case, the :mod:`sysconfig` module is a useful tool to programmatically " +"extract the configuration values that you will want to combine together. " +"For example:" +msgstr "" + +#: ../Doc/extending/extending.rst:8 +msgid "Extending Python with C or C++" +msgstr "" + +#: ../Doc/extending/extending.rst:10 +msgid "" +"It is quite easy to add new built-in modules to Python, if you know how to " +"program in C. Such :dfn:`extension modules` can do two things that can't be " +"done directly in Python: they can implement new built-in object types, and " +"they can call C library functions and system calls." +msgstr "" + +#: ../Doc/extending/extending.rst:15 +msgid "" +"To support extensions, the Python API (Application Programmers Interface) " +"defines a set of functions, macros and variables that provide access to most " +"aspects of the Python run-time system. The Python API is incorporated in a " +"C source file by including the header ``\"Python.h\"``." +msgstr "" + +#: ../Doc/extending/extending.rst:20 +msgid "" +"The compilation of an extension module depends on its intended use as well " +"as on your system setup; details are given in later chapters." +msgstr "" + +#: ../Doc/extending/extending.rst:25 +msgid "" +"The C extension interface is specific to CPython, and extension modules do " +"not work on other Python implementations. In many cases, it is possible to " +"avoid writing C extensions and preserve portability to other " +"implementations. For example, if your use case is calling C library " +"functions or system calls, you should consider using the :mod:`ctypes` " +"module or the `cffi `_ library rather than " +"writing custom C code. These modules let you write Python code to interface " +"with C code and are more portable between implementations of Python than " +"writing and compiling a C extension module." +msgstr "" + +#: ../Doc/extending/extending.rst:39 +msgid "A Simple Example" +msgstr "" + +#: ../Doc/extending/extending.rst:41 +msgid "" +"Let's create an extension module called ``spam`` (the favorite food of Monty " +"Python fans...) and let's say we want to create a Python interface to the C " +"library function :c:func:`system`. [#]_ This function takes a null-" +"terminated character string as argument and returns an integer. We want " +"this function to be callable from Python as follows::" +msgstr "" + +#: ../Doc/extending/extending.rst:50 +msgid "" +"Begin by creating a file :file:`spammodule.c`. (Historically, if a module " +"is called ``spam``, the C file containing its implementation is called :file:" +"`spammodule.c`; if the module name is very long, like ``spammify``, the " +"module name can be just :file:`spammify.c`.)" +msgstr "" + +#: ../Doc/extending/extending.rst:55 +msgid "The first line of our file can be::" +msgstr "" + +#: ../Doc/extending/extending.rst:59 +msgid "" +"which pulls in the Python API (you can add a comment describing the purpose " +"of the module and a copyright notice if you like)." +msgstr "" + +#: ../Doc/extending/extending.rst:64 +msgid "" +"Since Python may define some pre-processor definitions which affect the " +"standard headers on some systems, you *must* include :file:`Python.h` before " +"any standard headers are included." +msgstr "" + +#: ../Doc/extending/extending.rst:68 +msgid "" +"All user-visible symbols defined by :file:`Python.h` have a prefix of ``Py`` " +"or ``PY``, except those defined in standard header files. For convenience, " +"and since they are used extensively by the Python interpreter, ``\"Python.h" +"\"`` includes a few standard header files: ````, ````, " +"````, and ````. If the latter header file does not exist " +"on your system, it declares the functions :c:func:`malloc`, :c:func:`free` " +"and :c:func:`realloc` directly." +msgstr "" + +#: ../Doc/extending/extending.rst:76 +msgid "" +"The next thing we add to our module file is the C function that will be " +"called when the Python expression ``spam.system(string)`` is evaluated " +"(we'll see shortly how it ends up being called)::" +msgstr "" + +#: ../Doc/extending/extending.rst:92 +msgid "" +"There is a straightforward translation from the argument list in Python (for " +"example, the single expression ``\"ls -l\"``) to the arguments passed to the " +"C function. The C function always has two arguments, conventionally named " +"*self* and *args*." +msgstr "" + +#: ../Doc/extending/extending.rst:97 +msgid "" +"The *self* argument points to the module object for module-level functions; " +"for a method it would point to the object instance." +msgstr "" + +#: ../Doc/extending/extending.rst:100 +msgid "" +"The *args* argument will be a pointer to a Python tuple object containing " +"the arguments. Each item of the tuple corresponds to an argument in the " +"call's argument list. The arguments are Python objects --- in order to do " +"anything with them in our C function we have to convert them to C values. " +"The function :c:func:`PyArg_ParseTuple` in the Python API checks the " +"argument types and converts them to C values. It uses a template string to " +"determine the required types of the arguments as well as the types of the C " +"variables into which to store the converted values. More about this later." +msgstr "" + +#: ../Doc/extending/extending.rst:109 +msgid "" +":c:func:`PyArg_ParseTuple` returns true (nonzero) if all arguments have the " +"right type and its components have been stored in the variables whose " +"addresses are passed. It returns false (zero) if an invalid argument list " +"was passed. In the latter case it also raises an appropriate exception so " +"the calling function can return *NULL* immediately (as we saw in the " +"example)." +msgstr "" + +#: ../Doc/extending/extending.rst:119 +msgid "Intermezzo: Errors and Exceptions" +msgstr "" + +#: ../Doc/extending/extending.rst:121 +msgid "" +"An important convention throughout the Python interpreter is the following: " +"when a function fails, it should set an exception condition and return an " +"error value (usually a *NULL* pointer). Exceptions are stored in a static " +"global variable inside the interpreter; if this variable is *NULL* no " +"exception has occurred. A second global variable stores the \"associated " +"value\" of the exception (the second argument to :keyword:`raise`). A third " +"variable contains the stack traceback in case the error originated in Python " +"code. These three variables are the C equivalents of the result in Python " +"of :meth:`sys.exc_info` (see the section on module :mod:`sys` in the Python " +"Library Reference). It is important to know about them to understand how " +"errors are passed around." +msgstr "" + +#: ../Doc/extending/extending.rst:132 +msgid "" +"The Python API defines a number of functions to set various types of " +"exceptions." +msgstr "" + +#: ../Doc/extending/extending.rst:134 +msgid "" +"The most common one is :c:func:`PyErr_SetString`. Its arguments are an " +"exception object and a C string. The exception object is usually a " +"predefined object like :c:data:`PyExc_ZeroDivisionError`. The C string " +"indicates the cause of the error and is converted to a Python string object " +"and stored as the \"associated value\" of the exception." +msgstr "" + +#: ../Doc/extending/extending.rst:140 +msgid "" +"Another useful function is :c:func:`PyErr_SetFromErrno`, which only takes an " +"exception argument and constructs the associated value by inspection of the " +"global variable :c:data:`errno`. The most general function is :c:func:" +"`PyErr_SetObject`, which takes two object arguments, the exception and its " +"associated value. You don't need to :c:func:`Py_INCREF` the objects passed " +"to any of these functions." +msgstr "" + +#: ../Doc/extending/extending.rst:147 +msgid "" +"You can test non-destructively whether an exception has been set with :c:" +"func:`PyErr_Occurred`. This returns the current exception object, or *NULL* " +"if no exception has occurred. You normally don't need to call :c:func:" +"`PyErr_Occurred` to see whether an error occurred in a function call, since " +"you should be able to tell from the return value." +msgstr "" + +#: ../Doc/extending/extending.rst:153 +msgid "" +"When a function *f* that calls another function *g* detects that the latter " +"fails, *f* should itself return an error value (usually *NULL* or ``-1``). " +"It should *not* call one of the :c:func:`PyErr_\\*` functions --- one has " +"already been called by *g*. *f*'s caller is then supposed to also return an " +"error indication to *its* caller, again *without* calling :c:func:`PyErr_" +"\\*`, and so on --- the most detailed cause of the error was already " +"reported by the function that first detected it. Once the error reaches the " +"Python interpreter's main loop, this aborts the currently executing Python " +"code and tries to find an exception handler specified by the Python " +"programmer." +msgstr "" + +#: ../Doc/extending/extending.rst:163 +msgid "" +"(There are situations where a module can actually give a more detailed error " +"message by calling another :c:func:`PyErr_\\*` function, and in such cases " +"it is fine to do so. As a general rule, however, this is not necessary, and " +"can cause information about the cause of the error to be lost: most " +"operations can fail for a variety of reasons.)" +msgstr "" + +#: ../Doc/extending/extending.rst:169 +msgid "" +"To ignore an exception set by a function call that failed, the exception " +"condition must be cleared explicitly by calling :c:func:`PyErr_Clear`. The " +"only time C code should call :c:func:`PyErr_Clear` is if it doesn't want to " +"pass the error on to the interpreter but wants to handle it completely by " +"itself (possibly by trying something else, or pretending nothing went wrong)." +msgstr "" + +#: ../Doc/extending/extending.rst:175 +msgid "" +"Every failing :c:func:`malloc` call must be turned into an exception --- the " +"direct caller of :c:func:`malloc` (or :c:func:`realloc`) must call :c:func:" +"`PyErr_NoMemory` and return a failure indicator itself. All the object-" +"creating functions (for example, :c:func:`PyLong_FromLong`) already do this, " +"so this note is only relevant to those who call :c:func:`malloc` directly." +msgstr "" + +#: ../Doc/extending/extending.rst:181 +msgid "" +"Also note that, with the important exception of :c:func:`PyArg_ParseTuple` " +"and friends, functions that return an integer status usually return a " +"positive value or zero for success and ``-1`` for failure, like Unix system " +"calls." +msgstr "" + +#: ../Doc/extending/extending.rst:185 +msgid "" +"Finally, be careful to clean up garbage (by making :c:func:`Py_XDECREF` or :" +"c:func:`Py_DECREF` calls for objects you have already created) when you " +"return an error indicator!" +msgstr "" + +#: ../Doc/extending/extending.rst:189 +msgid "" +"The choice of which exception to raise is entirely yours. There are " +"predeclared C objects corresponding to all built-in Python exceptions, such " +"as :c:data:`PyExc_ZeroDivisionError`, which you can use directly. Of course, " +"you should choose exceptions wisely --- don't use :c:data:`PyExc_TypeError` " +"to mean that a file couldn't be opened (that should probably be :c:data:" +"`PyExc_IOError`). If something's wrong with the argument list, the :c:func:" +"`PyArg_ParseTuple` function usually raises :c:data:`PyExc_TypeError`. If " +"you have an argument whose value must be in a particular range or must " +"satisfy other conditions, :c:data:`PyExc_ValueError` is appropriate." +msgstr "" + +#: ../Doc/extending/extending.rst:199 +msgid "" +"You can also define a new exception that is unique to your module. For this, " +"you usually declare a static object variable at the beginning of your file::" +msgstr "" + +#: ../Doc/extending/extending.rst:204 +msgid "" +"and initialize it in your module's initialization function (:c:func:" +"`PyInit_spam`) with an exception object (leaving out the error checking for " +"now)::" +msgstr "" + +#: ../Doc/extending/extending.rst:222 +msgid "" +"Note that the Python name for the exception object is :exc:`spam.error`. " +"The :c:func:`PyErr_NewException` function may create a class with the base " +"class being :exc:`Exception` (unless another class is passed in instead of " +"*NULL*), described in :ref:`bltin-exceptions`." +msgstr "" + +#: ../Doc/extending/extending.rst:227 +msgid "" +"Note also that the :c:data:`SpamError` variable retains a reference to the " +"newly created exception class; this is intentional! Since the exception " +"could be removed from the module by external code, an owned reference to the " +"class is needed to ensure that it will not be discarded, causing :c:data:" +"`SpamError` to become a dangling pointer. Should it become a dangling " +"pointer, C code which raises the exception could cause a core dump or other " +"unintended side effects." +msgstr "" + +#: ../Doc/extending/extending.rst:234 +msgid "" +"We discuss the use of ``PyMODINIT_FUNC`` as a function return type later in " +"this sample." +msgstr "" + +#: ../Doc/extending/extending.rst:237 +msgid "" +"The :exc:`spam.error` exception can be raised in your extension module using " +"a call to :c:func:`PyErr_SetString` as shown below::" +msgstr "" + +#: ../Doc/extending/extending.rst:260 +msgid "Back to the Example" +msgstr "" + +#: ../Doc/extending/extending.rst:262 +msgid "" +"Going back to our example function, you should now be able to understand " +"this statement::" +msgstr "" + +#: ../Doc/extending/extending.rst:268 +msgid "" +"It returns *NULL* (the error indicator for functions returning object " +"pointers) if an error is detected in the argument list, relying on the " +"exception set by :c:func:`PyArg_ParseTuple`. Otherwise the string value of " +"the argument has been copied to the local variable :c:data:`command`. This " +"is a pointer assignment and you are not supposed to modify the string to " +"which it points (so in Standard C, the variable :c:data:`command` should " +"properly be declared as ``const char *command``)." +msgstr "" + +#: ../Doc/extending/extending.rst:276 +msgid "" +"The next statement is a call to the Unix function :c:func:`system`, passing " +"it the string we just got from :c:func:`PyArg_ParseTuple`::" +msgstr "" + +#: ../Doc/extending/extending.rst:281 +msgid "" +"Our :func:`spam.system` function must return the value of :c:data:`sts` as a " +"Python object. This is done using the function :c:func:`PyLong_FromLong`. ::" +msgstr "" + +#: ../Doc/extending/extending.rst:286 +msgid "" +"In this case, it will return an integer object. (Yes, even integers are " +"objects on the heap in Python!)" +msgstr "" + +#: ../Doc/extending/extending.rst:289 +msgid "" +"If you have a C function that returns no useful argument (a function " +"returning :c:type:`void`), the corresponding Python function must return " +"``None``. You need this idiom to do so (which is implemented by the :c:" +"macro:`Py_RETURN_NONE` macro)::" +msgstr "" + +#: ../Doc/extending/extending.rst:297 +msgid "" +":c:data:`Py_None` is the C name for the special Python object ``None``. It " +"is a genuine Python object rather than a *NULL* pointer, which means \"error" +"\" in most contexts, as we have seen." +msgstr "" + +#: ../Doc/extending/extending.rst:305 +msgid "The Module's Method Table and Initialization Function" +msgstr "" + +#: ../Doc/extending/extending.rst:307 +msgid "" +"I promised to show how :c:func:`spam_system` is called from Python programs. " +"First, we need to list its name and address in a \"method table\"::" +msgstr "" + +#: ../Doc/extending/extending.rst:318 +msgid "" +"Note the third entry (``METH_VARARGS``). This is a flag telling the " +"interpreter the calling convention to be used for the C function. It should " +"normally always be ``METH_VARARGS`` or ``METH_VARARGS | METH_KEYWORDS``; a " +"value of ``0`` means that an obsolete variant of :c:func:`PyArg_ParseTuple` " +"is used." +msgstr "" + +#: ../Doc/extending/extending.rst:323 +msgid "" +"When using only ``METH_VARARGS``, the function should expect the Python-" +"level parameters to be passed in as a tuple acceptable for parsing via :c:" +"func:`PyArg_ParseTuple`; more information on this function is provided below." +msgstr "" + +#: ../Doc/extending/extending.rst:327 +msgid "" +"The :const:`METH_KEYWORDS` bit may be set in the third field if keyword " +"arguments should be passed to the function. In this case, the C function " +"should accept a third ``PyObject *`` parameter which will be a dictionary of " +"keywords. Use :c:func:`PyArg_ParseTupleAndKeywords` to parse the arguments " +"to such a function." +msgstr "" + +#: ../Doc/extending/extending.rst:333 +msgid "" +"The method table must be referenced in the module definition structure::" +msgstr "" + +#: ../Doc/extending/extending.rst:344 +msgid "" +"This structure, in turn, must be passed to the interpreter in the module's " +"initialization function. The initialization function must be named :c:func:" +"`PyInit_name`, where *name* is the name of the module, and should be the " +"only non-\\ ``static`` item defined in the module file::" +msgstr "" + +#: ../Doc/extending/extending.rst:355 +msgid "" +"Note that PyMODINIT_FUNC declares the function as ``PyObject *`` return " +"type, declares any special linkage declarations required by the platform, " +"and for C++ declares the function as ``extern \"C\"``." +msgstr "" + +#: ../Doc/extending/extending.rst:359 +msgid "" +"When the Python program imports module :mod:`spam` for the first time, :c:" +"func:`PyInit_spam` is called. (See below for comments about embedding " +"Python.) It calls :c:func:`PyModule_Create`, which returns a module object, " +"and inserts built-in function objects into the newly created module based " +"upon the table (an array of :c:type:`PyMethodDef` structures) found in the " +"module definition. :c:func:`PyModule_Create` returns a pointer to the module " +"object that it creates. It may abort with a fatal error for certain errors, " +"or return *NULL* if the module could not be initialized satisfactorily. The " +"init function must return the module object to its caller, so that it then " +"gets inserted into ``sys.modules``." +msgstr "" + +#: ../Doc/extending/extending.rst:370 +msgid "" +"When embedding Python, the :c:func:`PyInit_spam` function is not called " +"automatically unless there's an entry in the :c:data:`PyImport_Inittab` " +"table. To add the module to the initialization table, use :c:func:" +"`PyImport_AppendInittab`, optionally followed by an import of the module::" +msgstr "" + +#: ../Doc/extending/extending.rst:406 +msgid "" +"Removing entries from ``sys.modules`` or importing compiled modules into " +"multiple interpreters within a process (or following a :c:func:`fork` " +"without an intervening :c:func:`exec`) can create problems for some " +"extension modules. Extension module authors should exercise caution when " +"initializing internal data structures." +msgstr "" + +#: ../Doc/extending/extending.rst:412 +msgid "" +"A more substantial example module is included in the Python source " +"distribution as :file:`Modules/xxmodule.c`. This file may be used as a " +"template or simply read as an example." +msgstr "" + +#: ../Doc/extending/extending.rst:418 +msgid "" +"Unlike our ``spam`` example, ``xxmodule`` uses *multi-phase initialization* " +"(new in Python 3.5), where a PyModuleDef structure is returned from " +"``PyInit_spam``, and creation of the module is left to the import machinery. " +"For details on multi-phase initialization, see :PEP:`489`." +msgstr "" + +#: ../Doc/extending/extending.rst:427 +msgid "Compilation and Linkage" +msgstr "" + +#: ../Doc/extending/extending.rst:429 +msgid "" +"There are two more things to do before you can use your new extension: " +"compiling and linking it with the Python system. If you use dynamic " +"loading, the details may depend on the style of dynamic loading your system " +"uses; see the chapters about building extension modules (chapter :ref:" +"`building`) and additional information that pertains only to building on " +"Windows (chapter :ref:`building-on-windows`) for more information about this." +msgstr "" + +#: ../Doc/extending/extending.rst:436 +msgid "" +"If you can't use dynamic loading, or if you want to make your module a " +"permanent part of the Python interpreter, you will have to change the " +"configuration setup and rebuild the interpreter. Luckily, this is very " +"simple on Unix: just place your file (:file:`spammodule.c` for example) in " +"the :file:`Modules/` directory of an unpacked source distribution, add a " +"line to the file :file:`Modules/Setup.local` describing your file::" +msgstr "" + +#: ../Doc/extending/extending.rst:445 +msgid "" +"and rebuild the interpreter by running :program:`make` in the toplevel " +"directory. You can also run :program:`make` in the :file:`Modules/` " +"subdirectory, but then you must first rebuild :file:`Makefile` there by " +"running ':program:`make` Makefile'. (This is necessary each time you change " +"the :file:`Setup` file.)" +msgstr "" + +#: ../Doc/extending/extending.rst:451 +msgid "" +"If your module requires additional libraries to link with, these can be " +"listed on the line in the configuration file as well, for instance::" +msgstr "" + +#: ../Doc/extending/extending.rst:460 +msgid "Calling Python Functions from C" +msgstr "" + +#: ../Doc/extending/extending.rst:462 +msgid "" +"So far we have concentrated on making C functions callable from Python. The " +"reverse is also useful: calling Python functions from C. This is especially " +"the case for libraries that support so-called \"callback\" functions. If a " +"C interface makes use of callbacks, the equivalent Python often needs to " +"provide a callback mechanism to the Python programmer; the implementation " +"will require calling the Python callback functions from a C callback. Other " +"uses are also imaginable." +msgstr "" + +#: ../Doc/extending/extending.rst:470 +msgid "" +"Fortunately, the Python interpreter is easily called recursively, and there " +"is a standard interface to call a Python function. (I won't dwell on how to " +"call the Python parser with a particular string as input --- if you're " +"interested, have a look at the implementation of the :option:`-c` command " +"line option in :file:`Modules/main.c` from the Python source code.)" +msgstr "" + +#: ../Doc/extending/extending.rst:476 +msgid "" +"Calling a Python function is easy. First, the Python program must somehow " +"pass you the Python function object. You should provide a function (or some " +"other interface) to do this. When this function is called, save a pointer " +"to the Python function object (be careful to :c:func:`Py_INCREF` it!) in a " +"global variable --- or wherever you see fit. For example, the following " +"function might be part of a module definition::" +msgstr "" + +#: ../Doc/extending/extending.rst:506 +msgid "" +"This function must be registered with the interpreter using the :const:" +"`METH_VARARGS` flag; this is described in section :ref:`methodtable`. The :" +"c:func:`PyArg_ParseTuple` function and its arguments are documented in " +"section :ref:`parsetuple`." +msgstr "" + +#: ../Doc/extending/extending.rst:511 +msgid "" +"The macros :c:func:`Py_XINCREF` and :c:func:`Py_XDECREF` increment/decrement " +"the reference count of an object and are safe in the presence of *NULL* " +"pointers (but note that *temp* will not be *NULL* in this context). More " +"info on them in section :ref:`refcounts`." +msgstr "" + +#: ../Doc/extending/extending.rst:518 +msgid "" +"Later, when it is time to call the function, you call the C function :c:func:" +"`PyObject_CallObject`. This function has two arguments, both pointers to " +"arbitrary Python objects: the Python function, and the argument list. The " +"argument list must always be a tuple object, whose length is the number of " +"arguments. To call the Python function with no arguments, pass in NULL, or " +"an empty tuple; to call it with one argument, pass a singleton tuple. :c:" +"func:`Py_BuildValue` returns a tuple when its format string consists of zero " +"or more format codes between parentheses. For example::" +msgstr "" + +#: ../Doc/extending/extending.rst:538 +msgid "" +":c:func:`PyObject_CallObject` returns a Python object pointer: this is the " +"return value of the Python function. :c:func:`PyObject_CallObject` is " +"\"reference-count-neutral\" with respect to its arguments. In the example a " +"new tuple was created to serve as the argument list, which is :c:func:" +"`Py_DECREF`\\ -ed immediately after the :c:func:`PyObject_CallObject` call." +msgstr "" + +#: ../Doc/extending/extending.rst:544 +msgid "" +"The return value of :c:func:`PyObject_CallObject` is \"new\": either it is a " +"brand new object, or it is an existing object whose reference count has been " +"incremented. So, unless you want to save it in a global variable, you " +"should somehow :c:func:`Py_DECREF` the result, even (especially!) if you are " +"not interested in its value." +msgstr "" + +#: ../Doc/extending/extending.rst:550 +msgid "" +"Before you do this, however, it is important to check that the return value " +"isn't *NULL*. If it is, the Python function terminated by raising an " +"exception. If the C code that called :c:func:`PyObject_CallObject` is called " +"from Python, it should now return an error indication to its Python caller, " +"so the interpreter can print a stack trace, or the calling Python code can " +"handle the exception. If this is not possible or desirable, the exception " +"should be cleared by calling :c:func:`PyErr_Clear`. For example::" +msgstr "" + +#: ../Doc/extending/extending.rst:563 +msgid "" +"Depending on the desired interface to the Python callback function, you may " +"also have to provide an argument list to :c:func:`PyObject_CallObject`. In " +"some cases the argument list is also provided by the Python program, through " +"the same interface that specified the callback function. It can then be " +"saved and used in the same manner as the function object. In other cases, " +"you may have to construct a new tuple to pass as the argument list. The " +"simplest way to do this is to call :c:func:`Py_BuildValue`. For example, if " +"you want to pass an integral event code, you might use the following code::" +msgstr "" + +#: ../Doc/extending/extending.rst:582 +msgid "" +"Note the placement of ``Py_DECREF(arglist)`` immediately after the call, " +"before the error check! Also note that strictly speaking this code is not " +"complete: :c:func:`Py_BuildValue` may run out of memory, and this should be " +"checked." +msgstr "" + +#: ../Doc/extending/extending.rst:586 +msgid "" +"You may also call a function with keyword arguments by using :c:func:" +"`PyObject_Call`, which supports arguments and keyword arguments. As in the " +"above example, we use :c:func:`Py_BuildValue` to construct the dictionary. ::" +msgstr "" + +#: ../Doc/extending/extending.rst:604 +msgid "Extracting Parameters in Extension Functions" +msgstr "" + +#: ../Doc/extending/extending.rst:608 +msgid "The :c:func:`PyArg_ParseTuple` function is declared as follows::" +msgstr "" + +#: ../Doc/extending/extending.rst:612 +msgid "" +"The *arg* argument must be a tuple object containing an argument list passed " +"from Python to a C function. The *format* argument must be a format string, " +"whose syntax is explained in :ref:`arg-parsing` in the Python/C API " +"Reference Manual. The remaining arguments must be addresses of variables " +"whose type is determined by the format string." +msgstr "" + +#: ../Doc/extending/extending.rst:618 +msgid "" +"Note that while :c:func:`PyArg_ParseTuple` checks that the Python arguments " +"have the required types, it cannot check the validity of the addresses of C " +"variables passed to the call: if you make mistakes there, your code will " +"probably crash or at least overwrite random bits in memory. So be careful!" +msgstr "" + +#: ../Doc/extending/extending.rst:623 +msgid "" +"Note that any Python object references which are provided to the caller are " +"*borrowed* references; do not decrement their reference count!" +msgstr "" + +#: ../Doc/extending/extending.rst:626 +msgid "Some example calls::" +msgstr "" + +#: ../Doc/extending/extending.rst:696 +msgid "Keyword Parameters for Extension Functions" +msgstr "" + +#: ../Doc/extending/extending.rst:700 +msgid "" +"The :c:func:`PyArg_ParseTupleAndKeywords` function is declared as follows::" +msgstr "" + +#: ../Doc/extending/extending.rst:705 +msgid "" +"The *arg* and *format* parameters are identical to those of the :c:func:" +"`PyArg_ParseTuple` function. The *kwdict* parameter is the dictionary of " +"keywords received as the third parameter from the Python runtime. The " +"*kwlist* parameter is a *NULL*-terminated list of strings which identify the " +"parameters; the names are matched with the type information from *format* " +"from left to right. On success, :c:func:`PyArg_ParseTupleAndKeywords` " +"returns true, otherwise it returns false and raises an appropriate exception." +msgstr "" + +#: ../Doc/extending/extending.rst:715 +msgid "" +"Nested tuples cannot be parsed when using keyword arguments! Keyword " +"parameters passed in which are not present in the *kwlist* will cause :exc:" +"`TypeError` to be raised." +msgstr "" + +#: ../Doc/extending/extending.rst:721 +msgid "" +"Here is an example module which uses keywords, based on an example by Geoff " +"Philbrick (philbrick@hks.com)::" +msgstr "" + +#: ../Doc/extending/extending.rst:775 +msgid "Building Arbitrary Values" +msgstr "" + +#: ../Doc/extending/extending.rst:777 +msgid "" +"This function is the counterpart to :c:func:`PyArg_ParseTuple`. It is " +"declared as follows::" +msgstr "" + +#: ../Doc/extending/extending.rst:782 +msgid "" +"It recognizes a set of format units similar to the ones recognized by :c:" +"func:`PyArg_ParseTuple`, but the arguments (which are input to the function, " +"not output) must not be pointers, just values. It returns a new Python " +"object, suitable for returning from a C function called from Python." +msgstr "" + +#: ../Doc/extending/extending.rst:787 +msgid "" +"One difference with :c:func:`PyArg_ParseTuple`: while the latter requires " +"its first argument to be a tuple (since Python argument lists are always " +"represented as tuples internally), :c:func:`Py_BuildValue` does not always " +"build a tuple. It builds a tuple only if its format string contains two or " +"more format units. If the format string is empty, it returns ``None``; if it " +"contains exactly one format unit, it returns whatever object is described by " +"that format unit. To force it to return a tuple of size 0 or one, " +"parenthesize the format string." +msgstr "" + +#: ../Doc/extending/extending.rst:795 +msgid "" +"Examples (to the left the call, to the right the resulting Python value):" +msgstr "" + +#: ../Doc/extending/extending.rst:821 +msgid "Reference Counts" +msgstr "" + +#: ../Doc/extending/extending.rst:823 +msgid "" +"In languages like C or C++, the programmer is responsible for dynamic " +"allocation and deallocation of memory on the heap. In C, this is done using " +"the functions :c:func:`malloc` and :c:func:`free`. In C++, the operators " +"``new`` and ``delete`` are used with essentially the same meaning and we'll " +"restrict the following discussion to the C case." +msgstr "" + +#: ../Doc/extending/extending.rst:829 +msgid "" +"Every block of memory allocated with :c:func:`malloc` should eventually be " +"returned to the pool of available memory by exactly one call to :c:func:" +"`free`. It is important to call :c:func:`free` at the right time. If a " +"block's address is forgotten but :c:func:`free` is not called for it, the " +"memory it occupies cannot be reused until the program terminates. This is " +"called a :dfn:`memory leak`. On the other hand, if a program calls :c:func:" +"`free` for a block and then continues to use the block, it creates a " +"conflict with re-use of the block through another :c:func:`malloc` call. " +"This is called :dfn:`using freed memory`. It has the same bad consequences " +"as referencing uninitialized data --- core dumps, wrong results, mysterious " +"crashes." +msgstr "" + +#: ../Doc/extending/extending.rst:840 +msgid "" +"Common causes of memory leaks are unusual paths through the code. For " +"instance, a function may allocate a block of memory, do some calculation, " +"and then free the block again. Now a change in the requirements for the " +"function may add a test to the calculation that detects an error condition " +"and can return prematurely from the function. It's easy to forget to free " +"the allocated memory block when taking this premature exit, especially when " +"it is added later to the code. Such leaks, once introduced, often go " +"undetected for a long time: the error exit is taken only in a small fraction " +"of all calls, and most modern machines have plenty of virtual memory, so the " +"leak only becomes apparent in a long-running process that uses the leaking " +"function frequently. Therefore, it's important to prevent leaks from " +"happening by having a coding convention or strategy that minimizes this kind " +"of errors." +msgstr "" + +#: ../Doc/extending/extending.rst:853 +msgid "" +"Since Python makes heavy use of :c:func:`malloc` and :c:func:`free`, it " +"needs a strategy to avoid memory leaks as well as the use of freed memory. " +"The chosen method is called :dfn:`reference counting`. The principle is " +"simple: every object contains a counter, which is incremented when a " +"reference to the object is stored somewhere, and which is decremented when a " +"reference to it is deleted. When the counter reaches zero, the last " +"reference to the object has been deleted and the object is freed." +msgstr "" + +#: ../Doc/extending/extending.rst:861 +msgid "" +"An alternative strategy is called :dfn:`automatic garbage collection`. " +"(Sometimes, reference counting is also referred to as a garbage collection " +"strategy, hence my use of \"automatic\" to distinguish the two.) The big " +"advantage of automatic garbage collection is that the user doesn't need to " +"call :c:func:`free` explicitly. (Another claimed advantage is an " +"improvement in speed or memory usage --- this is no hard fact however.) The " +"disadvantage is that for C, there is no truly portable automatic garbage " +"collector, while reference counting can be implemented portably (as long as " +"the functions :c:func:`malloc` and :c:func:`free` are available --- which " +"the C Standard guarantees). Maybe some day a sufficiently portable automatic " +"garbage collector will be available for C. Until then, we'll have to live " +"with reference counts." +msgstr "" + +#: ../Doc/extending/extending.rst:873 +msgid "" +"While Python uses the traditional reference counting implementation, it also " +"offers a cycle detector that works to detect reference cycles. This allows " +"applications to not worry about creating direct or indirect circular " +"references; these are the weakness of garbage collection implemented using " +"only reference counting. Reference cycles consist of objects which contain " +"(possibly indirect) references to themselves, so that each object in the " +"cycle has a reference count which is non-zero. Typical reference counting " +"implementations are not able to reclaim the memory belonging to any objects " +"in a reference cycle, or referenced from the objects in the cycle, even " +"though there are no further references to the cycle itself." +msgstr "" + +#: ../Doc/extending/extending.rst:884 +msgid "" +"The cycle detector is able to detect garbage cycles and can reclaim them. " +"The :mod:`gc` module exposes a way to run the detector (the :func:`~gc." +"collect` function), as well as configuration interfaces and the ability to " +"disable the detector at runtime. The cycle detector is considered an " +"optional component; though it is included by default, it can be disabled at " +"build time using the :option:`--without-cycle-gc` option to the :program:" +"`configure` script on Unix platforms (including Mac OS X). If the cycle " +"detector is disabled in this way, the :mod:`gc` module will not be available." +msgstr "" + +#: ../Doc/extending/extending.rst:898 +msgid "Reference Counting in Python" +msgstr "" + +#: ../Doc/extending/extending.rst:900 +msgid "" +"There are two macros, ``Py_INCREF(x)`` and ``Py_DECREF(x)``, which handle " +"the incrementing and decrementing of the reference count. :c:func:" +"`Py_DECREF` also frees the object when the count reaches zero. For " +"flexibility, it doesn't call :c:func:`free` directly --- rather, it makes a " +"call through a function pointer in the object's :dfn:`type object`. For " +"this purpose (and others), every object also contains a pointer to its type " +"object." +msgstr "" + +#: ../Doc/extending/extending.rst:907 +msgid "" +"The big question now remains: when to use ``Py_INCREF(x)`` and " +"``Py_DECREF(x)``? Let's first introduce some terms. Nobody \"owns\" an " +"object; however, you can :dfn:`own a reference` to an object. An object's " +"reference count is now defined as the number of owned references to it. The " +"owner of a reference is responsible for calling :c:func:`Py_DECREF` when the " +"reference is no longer needed. Ownership of a reference can be " +"transferred. There are three ways to dispose of an owned reference: pass it " +"on, store it, or call :c:func:`Py_DECREF`. Forgetting to dispose of an owned " +"reference creates a memory leak." +msgstr "" + +#: ../Doc/extending/extending.rst:916 +msgid "" +"It is also possible to :dfn:`borrow` [#]_ a reference to an object. The " +"borrower of a reference should not call :c:func:`Py_DECREF`. The borrower " +"must not hold on to the object longer than the owner from which it was " +"borrowed. Using a borrowed reference after the owner has disposed of it " +"risks using freed memory and should be avoided completely. [#]_" +msgstr "" + +#: ../Doc/extending/extending.rst:922 +msgid "" +"The advantage of borrowing over owning a reference is that you don't need to " +"take care of disposing of the reference on all possible paths through the " +"code --- in other words, with a borrowed reference you don't run the risk of " +"leaking when a premature exit is taken. The disadvantage of borrowing over " +"owning is that there are some subtle situations where in seemingly correct " +"code a borrowed reference can be used after the owner from which it was " +"borrowed has in fact disposed of it." +msgstr "" + +#: ../Doc/extending/extending.rst:930 +msgid "" +"A borrowed reference can be changed into an owned reference by calling :c:" +"func:`Py_INCREF`. This does not affect the status of the owner from which " +"the reference was borrowed --- it creates a new owned reference, and gives " +"full owner responsibilities (the new owner must dispose of the reference " +"properly, as well as the previous owner)." +msgstr "" + +#: ../Doc/extending/extending.rst:940 +msgid "Ownership Rules" +msgstr "" + +#: ../Doc/extending/extending.rst:942 +msgid "" +"Whenever an object reference is passed into or out of a function, it is part " +"of the function's interface specification whether ownership is transferred " +"with the reference or not." +msgstr "" + +#: ../Doc/extending/extending.rst:946 +msgid "" +"Most functions that return a reference to an object pass on ownership with " +"the reference. In particular, all functions whose function it is to create " +"a new object, such as :c:func:`PyLong_FromLong` and :c:func:`Py_BuildValue`, " +"pass ownership to the receiver. Even if the object is not actually new, you " +"still receive ownership of a new reference to that object. For instance, :c:" +"func:`PyLong_FromLong` maintains a cache of popular values and can return a " +"reference to a cached item." +msgstr "" + +#: ../Doc/extending/extending.rst:954 +msgid "" +"Many functions that extract objects from other objects also transfer " +"ownership with the reference, for instance :c:func:" +"`PyObject_GetAttrString`. The picture is less clear, here, however, since a " +"few common routines are exceptions: :c:func:`PyTuple_GetItem`, :c:func:" +"`PyList_GetItem`, :c:func:`PyDict_GetItem`, and :c:func:" +"`PyDict_GetItemString` all return references that you borrow from the tuple, " +"list or dictionary." +msgstr "" + +#: ../Doc/extending/extending.rst:961 +msgid "" +"The function :c:func:`PyImport_AddModule` also returns a borrowed reference, " +"even though it may actually create the object it returns: this is possible " +"because an owned reference to the object is stored in ``sys.modules``." +msgstr "" + +#: ../Doc/extending/extending.rst:965 +msgid "" +"When you pass an object reference into another function, in general, the " +"function borrows the reference from you --- if it needs to store it, it will " +"use :c:func:`Py_INCREF` to become an independent owner. There are exactly " +"two important exceptions to this rule: :c:func:`PyTuple_SetItem` and :c:func:" +"`PyList_SetItem`. These functions take over ownership of the item passed to " +"them --- even if they fail! (Note that :c:func:`PyDict_SetItem` and friends " +"don't take over ownership --- they are \"normal.\")" +msgstr "" + +#: ../Doc/extending/extending.rst:973 +msgid "" +"When a C function is called from Python, it borrows references to its " +"arguments from the caller. The caller owns a reference to the object, so " +"the borrowed reference's lifetime is guaranteed until the function returns. " +"Only when such a borrowed reference must be stored or passed on, it must be " +"turned into an owned reference by calling :c:func:`Py_INCREF`." +msgstr "" + +#: ../Doc/extending/extending.rst:979 +msgid "" +"The object reference returned from a C function that is called from Python " +"must be an owned reference --- ownership is transferred from the function to " +"its caller." +msgstr "" + +#: ../Doc/extending/extending.rst:987 +msgid "Thin Ice" +msgstr "" + +#: ../Doc/extending/extending.rst:989 +msgid "" +"There are a few situations where seemingly harmless use of a borrowed " +"reference can lead to problems. These all have to do with implicit " +"invocations of the interpreter, which can cause the owner of a reference to " +"dispose of it." +msgstr "" + +#: ../Doc/extending/extending.rst:993 +msgid "" +"The first and most important case to know about is using :c:func:`Py_DECREF` " +"on an unrelated object while borrowing a reference to a list item. For " +"instance::" +msgstr "" + +#: ../Doc/extending/extending.rst:1005 +msgid "" +"This function first borrows a reference to ``list[0]``, then replaces " +"``list[1]`` with the value ``0``, and finally prints the borrowed reference. " +"Looks harmless, right? But it's not!" +msgstr "" + +#: ../Doc/extending/extending.rst:1009 +msgid "" +"Let's follow the control flow into :c:func:`PyList_SetItem`. The list owns " +"references to all its items, so when item 1 is replaced, it has to dispose " +"of the original item 1. Now let's suppose the original item 1 was an " +"instance of a user-defined class, and let's further suppose that the class " +"defined a :meth:`__del__` method. If this class instance has a reference " +"count of 1, disposing of it will call its :meth:`__del__` method." +msgstr "" + +#: ../Doc/extending/extending.rst:1016 +msgid "" +"Since it is written in Python, the :meth:`__del__` method can execute " +"arbitrary Python code. Could it perhaps do something to invalidate the " +"reference to ``item`` in :c:func:`bug`? You bet! Assuming that the list " +"passed into :c:func:`bug` is accessible to the :meth:`__del__` method, it " +"could execute a statement to the effect of ``del list[0]``, and assuming " +"this was the last reference to that object, it would free the memory " +"associated with it, thereby invalidating ``item``." +msgstr "" + +#: ../Doc/extending/extending.rst:1024 +msgid "" +"The solution, once you know the source of the problem, is easy: temporarily " +"increment the reference count. The correct version of the function reads::" +msgstr "" + +#: ../Doc/extending/extending.rst:1038 +msgid "" +"This is a true story. An older version of Python contained variants of this " +"bug and someone spent a considerable amount of time in a C debugger to " +"figure out why his :meth:`__del__` methods would fail..." +msgstr "" + +#: ../Doc/extending/extending.rst:1042 +msgid "" +"The second case of problems with a borrowed reference is a variant involving " +"threads. Normally, multiple threads in the Python interpreter can't get in " +"each other's way, because there is a global lock protecting Python's entire " +"object space. However, it is possible to temporarily release this lock " +"using the macro :c:macro:`Py_BEGIN_ALLOW_THREADS`, and to re-acquire it " +"using :c:macro:`Py_END_ALLOW_THREADS`. This is common around blocking I/O " +"calls, to let other threads use the processor while waiting for the I/O to " +"complete. Obviously, the following function has the same problem as the " +"previous one::" +msgstr "" + +#: ../Doc/extending/extending.rst:1065 +msgid "NULL Pointers" +msgstr "" + +#: ../Doc/extending/extending.rst:1067 +msgid "" +"In general, functions that take object references as arguments do not expect " +"you to pass them *NULL* pointers, and will dump core (or cause later core " +"dumps) if you do so. Functions that return object references generally " +"return *NULL* only to indicate that an exception occurred. The reason for " +"not testing for *NULL* arguments is that functions often pass the objects " +"they receive on to other function --- if each function were to test for " +"*NULL*, there would be a lot of redundant tests and the code would run more " +"slowly." +msgstr "" + +#: ../Doc/extending/extending.rst:1075 +msgid "" +"It is better to test for *NULL* only at the \"source:\" when a pointer that " +"may be *NULL* is received, for example, from :c:func:`malloc` or from a " +"function that may raise an exception." +msgstr "" + +#: ../Doc/extending/extending.rst:1079 +msgid "" +"The macros :c:func:`Py_INCREF` and :c:func:`Py_DECREF` do not check for " +"*NULL* pointers --- however, their variants :c:func:`Py_XINCREF` and :c:func:" +"`Py_XDECREF` do." +msgstr "" + +#: ../Doc/extending/extending.rst:1083 +msgid "" +"The macros for checking for a particular object type (``Pytype_Check()``) " +"don't check for *NULL* pointers --- again, there is much code that calls " +"several of these in a row to test an object against various different " +"expected types, and this would generate redundant tests. There are no " +"variants with *NULL* checking." +msgstr "" + +#: ../Doc/extending/extending.rst:1089 +msgid "" +"The C function calling mechanism guarantees that the argument list passed to " +"C functions (``args`` in the examples) is never *NULL* --- in fact it " +"guarantees that it is always a tuple. [#]_" +msgstr "" + +#: ../Doc/extending/extending.rst:1093 +msgid "" +"It is a severe error to ever let a *NULL* pointer \"escape\" to the Python " +"user." +msgstr "" + +#: ../Doc/extending/extending.rst:1104 +msgid "Writing Extensions in C++" +msgstr "" + +#: ../Doc/extending/extending.rst:1106 +msgid "" +"It is possible to write extension modules in C++. Some restrictions apply. " +"If the main program (the Python interpreter) is compiled and linked by the C " +"compiler, global or static objects with constructors cannot be used. This " +"is not a problem if the main program is linked by the C++ compiler. " +"Functions that will be called by the Python interpreter (in particular, " +"module initialization functions) have to be declared using ``extern \"C\"``. " +"It is unnecessary to enclose the Python header files in ``extern \"C\" {...}" +"`` --- they use this form already if the symbol ``__cplusplus`` is defined " +"(all recent C++ compilers define this symbol)." +msgstr "" + +#: ../Doc/extending/extending.rst:1120 +msgid "Providing a C API for an Extension Module" +msgstr "" + +#: ../Doc/extending/extending.rst:1125 +msgid "" +"Many extension modules just provide new functions and types to be used from " +"Python, but sometimes the code in an extension module can be useful for " +"other extension modules. For example, an extension module could implement a " +"type \"collection\" which works like lists without order. Just like the " +"standard Python list type has a C API which permits extension modules to " +"create and manipulate lists, this new collection type should have a set of C " +"functions for direct manipulation from other extension modules." +msgstr "" + +#: ../Doc/extending/extending.rst:1133 +msgid "" +"At first sight this seems easy: just write the functions (without declaring " +"them ``static``, of course), provide an appropriate header file, and " +"document the C API. And in fact this would work if all extension modules " +"were always linked statically with the Python interpreter. When modules are " +"used as shared libraries, however, the symbols defined in one module may not " +"be visible to another module. The details of visibility depend on the " +"operating system; some systems use one global namespace for the Python " +"interpreter and all extension modules (Windows, for example), whereas others " +"require an explicit list of imported symbols at module link time (AIX is one " +"example), or offer a choice of different strategies (most Unices). And even " +"if symbols are globally visible, the module whose functions one wishes to " +"call might not have been loaded yet!" +msgstr "" + +#: ../Doc/extending/extending.rst:1145 +msgid "" +"Portability therefore requires not to make any assumptions about symbol " +"visibility. This means that all symbols in extension modules should be " +"declared ``static``, except for the module's initialization function, in " +"order to avoid name clashes with other extension modules (as discussed in " +"section :ref:`methodtable`). And it means that symbols that *should* be " +"accessible from other extension modules must be exported in a different way." +msgstr "" + +#: ../Doc/extending/extending.rst:1152 +msgid "" +"Python provides a special mechanism to pass C-level information (pointers) " +"from one extension module to another one: Capsules. A Capsule is a Python " +"data type which stores a pointer (:c:type:`void \\*`). Capsules can only be " +"created and accessed via their C API, but they can be passed around like any " +"other Python object. In particular, they can be assigned to a name in an " +"extension module's namespace. Other extension modules can then import this " +"module, retrieve the value of this name, and then retrieve the pointer from " +"the Capsule." +msgstr "" + +#: ../Doc/extending/extending.rst:1160 +msgid "" +"There are many ways in which Capsules can be used to export the C API of an " +"extension module. Each function could get its own Capsule, or all C API " +"pointers could be stored in an array whose address is published in a " +"Capsule. And the various tasks of storing and retrieving the pointers can be " +"distributed in different ways between the module providing the code and the " +"client modules." +msgstr "" + +#: ../Doc/extending/extending.rst:1166 +msgid "" +"Whichever method you choose, it's important to name your Capsules properly. " +"The function :c:func:`PyCapsule_New` takes a name parameter (:c:type:`const " +"char \\*`); you're permitted to pass in a *NULL* name, but we strongly " +"encourage you to specify a name. Properly named Capsules provide a degree " +"of runtime type-safety; there is no feasible way to tell one unnamed Capsule " +"from another." +msgstr "" + +#: ../Doc/extending/extending.rst:1173 +msgid "" +"In particular, Capsules used to expose C APIs should be given a name " +"following this convention::" +msgstr "" + +#: ../Doc/extending/extending.rst:1178 +msgid "" +"The convenience function :c:func:`PyCapsule_Import` makes it easy to load a " +"C API provided via a Capsule, but only if the Capsule's name matches this " +"convention. This behavior gives C API users a high degree of certainty that " +"the Capsule they load contains the correct C API." +msgstr "" + +#: ../Doc/extending/extending.rst:1183 +msgid "" +"The following example demonstrates an approach that puts most of the burden " +"on the writer of the exporting module, which is appropriate for commonly " +"used library modules. It stores all C API pointers (just one in the " +"example!) in an array of :c:type:`void` pointers which becomes the value of " +"a Capsule. The header file corresponding to the module provides a macro that " +"takes care of importing the module and retrieving its C API pointers; client " +"modules only have to call this macro before accessing the C API." +msgstr "" + +#: ../Doc/extending/extending.rst:1191 +msgid "" +"The exporting module is a modification of the :mod:`spam` module from " +"section :ref:`extending-simpleexample`. The function :func:`spam.system` " +"does not call the C library function :c:func:`system` directly, but a " +"function :c:func:`PySpam_System`, which would of course do something more " +"complicated in reality (such as adding \"spam\" to every command). This " +"function :c:func:`PySpam_System` is also exported to other extension modules." +msgstr "" + +#: ../Doc/extending/extending.rst:1198 +msgid "" +"The function :c:func:`PySpam_System` is a plain C function, declared " +"``static`` like everything else::" +msgstr "" + +#: ../Doc/extending/extending.rst:1207 +msgid "The function :c:func:`spam_system` is modified in a trivial way::" +msgstr "" + +#: ../Doc/extending/extending.rst:1221 +msgid "In the beginning of the module, right after the line ::" +msgstr "" + +#: ../Doc/extending/extending.rst:1225 +msgid "two more lines must be added::" +msgstr "" + +#: ../Doc/extending/extending.rst:1230 +msgid "" +"The ``#define`` is used to tell the header file that it is being included in " +"the exporting module, not a client module. Finally, the module's " +"initialization function must take care of initializing the C API pointer " +"array::" +msgstr "" + +#: ../Doc/extending/extending.rst:1256 +msgid "" +"Note that ``PySpam_API`` is declared ``static``; otherwise the pointer array " +"would disappear when :func:`PyInit_spam` terminates!" +msgstr "" + +#: ../Doc/extending/extending.rst:1259 +msgid "" +"The bulk of the work is in the header file :file:`spammodule.h`, which looks " +"like this::" +msgstr "" + +#: ../Doc/extending/extending.rst:1310 +msgid "" +"All that a client module must do in order to have access to the function :c:" +"func:`PySpam_System` is to call the function (or rather macro) :c:func:" +"`import_spam` in its initialization function::" +msgstr "" + +#: ../Doc/extending/extending.rst:1328 +msgid "" +"The main disadvantage of this approach is that the file :file:`spammodule.h` " +"is rather complicated. However, the basic structure is the same for each " +"function that is exported, so it has to be learned only once." +msgstr "" + +#: ../Doc/extending/extending.rst:1332 +msgid "" +"Finally it should be mentioned that Capsules offer additional functionality, " +"which is especially useful for memory allocation and deallocation of the " +"pointer stored in a Capsule. The details are described in the Python/C API " +"Reference Manual in the section :ref:`capsules` and in the implementation of " +"Capsules (files :file:`Include/pycapsule.h` and :file:`Objects/pycapsule.c` " +"in the Python source code distribution)." +msgstr "" + +#: ../Doc/extending/extending.rst:1340 ../Doc/extending/newtypes.rst:1506 +msgid "Footnotes" +msgstr "" + +#: ../Doc/extending/extending.rst:1341 +msgid "" +"An interface for this function already exists in the standard module :mod:" +"`os` --- it was chosen as a simple and straightforward example." +msgstr "" + +#: ../Doc/extending/extending.rst:1344 +msgid "" +"The metaphor of \"borrowing\" a reference is not completely correct: the " +"owner still has a copy of the reference." +msgstr "" + +#: ../Doc/extending/extending.rst:1347 +msgid "" +"Checking that the reference count is at least 1 **does not work** --- the " +"reference count itself could be in freed memory and may thus be reused for " +"another object!" +msgstr "" + +#: ../Doc/extending/extending.rst:1351 +msgid "" +"These guarantees don't hold when you use the \"old\" style calling " +"convention --- this is still found in much existing code." +msgstr "" + +#: ../Doc/extending/index.rst:5 +msgid "Extending and Embedding the Python Interpreter" +msgstr "" + +#: ../Doc/extending/index.rst:7 +msgid "" +"This document describes how to write modules in C or C++ to extend the " +"Python interpreter with new modules. Those modules can not only define new " +"functions but also new object types and their methods. The document also " +"describes how to embed the Python interpreter in another application, for " +"use as an extension language. Finally, it shows how to compile and link " +"extension modules so that they can be loaded dynamically (at run time) into " +"the interpreter, if the underlying operating system supports this feature." +msgstr "" + +#: ../Doc/extending/index.rst:15 +msgid "" +"This document assumes basic knowledge about Python. For an informal " +"introduction to the language, see :ref:`tutorial-index`. :ref:`reference-" +"index` gives a more formal definition of the language. :ref:`library-index` " +"documents the existing object types, functions and modules (both built-in " +"and written in Python) that give the language its wide application range." +msgstr "" + +#: ../Doc/extending/index.rst:21 +msgid "" +"For a detailed description of the whole Python/C API, see the separate :ref:" +"`c-api-index`." +msgstr "" + +#: ../Doc/extending/index.rst:26 +msgid "Recommended third party tools" +msgstr "" + +#: ../Doc/extending/index.rst:28 +msgid "" +"This guide only covers the basic tools for creating extensions provided as " +"part of this version of CPython. Third party tools like Cython, ``cffi``, " +"SWIG and Numba offer both simpler and more sophisticated approaches to " +"creating C and C++ extensions for Python." +msgstr "" + +#: ../Doc/extending/index.rst:38 +msgid "" +"`Python Packaging User Guide: Binary Extensions `_" +msgstr "" + +#: ../Doc/extending/index.rst:36 +msgid "" +"The Python Packaging User Guide not only covers several available tools that " +"simplify the creation of binary extensions, but also discusses the various " +"reasons why creating an extension module may be desirable in the first place." +msgstr "" + +#: ../Doc/extending/index.rst:43 +msgid "Creating extensions without third party tools" +msgstr "" + +#: ../Doc/extending/index.rst:45 +msgid "" +"This section of the guide covers creating C and C++ extensions without " +"assistance from third party tools. It is intended primarily for creators of " +"those tools, rather than being a recommended way to create your own C " +"extensions." +msgstr "" + +#: ../Doc/extending/index.rst:60 +msgid "Embedding the CPython runtime in a larger application" +msgstr "" + +#: ../Doc/extending/index.rst:62 +msgid "" +"Sometimes, rather than creating an extension that runs inside the Python " +"interpreter as the main application, it is desirable to instead embed the " +"CPython runtime inside a larger application. This section covers some of the " +"details involved in doing that successfully." +msgstr "" + +#: ../Doc/extending/newtypes.rst:8 +msgid "Defining New Types" +msgstr "" + +#: ../Doc/extending/newtypes.rst:15 +msgid "" +"As mentioned in the last chapter, Python allows the writer of an extension " +"module to define new types that can be manipulated from Python code, much " +"like strings and lists in core Python." +msgstr "" + +#: ../Doc/extending/newtypes.rst:19 +msgid "" +"This is not hard; the code for all extension types follows a pattern, but " +"there are some details that you need to understand before you can get " +"started." +msgstr "" + +#: ../Doc/extending/newtypes.rst:26 +msgid "The Basics" +msgstr "" + +#: ../Doc/extending/newtypes.rst:28 +msgid "" +"The Python runtime sees all Python objects as variables of type :c:type:" +"`PyObject\\*`, which serves as a \"base type\" for all Python objects. :c:" +"type:`PyObject` itself only contains the refcount and a pointer to the " +"object's \"type object\". This is where the action is; the type object " +"determines which (C) functions get called when, for instance, an attribute " +"gets looked up on an object or it is multiplied by another object. These C " +"functions are called \"type methods\"." +msgstr "" + +#: ../Doc/extending/newtypes.rst:36 +msgid "" +"So, if you want to define a new object type, you need to create a new type " +"object." +msgstr "" + +#: ../Doc/extending/newtypes.rst:39 +msgid "" +"This sort of thing can only be explained by example, so here's a minimal, " +"but complete, module that defines a new type:" +msgstr "" + +#: ../Doc/extending/newtypes.rst:45 +msgid "" +"Now that's quite a bit to take in at once, but hopefully bits will seem " +"familiar from the last chapter." +msgstr "" + +#: ../Doc/extending/newtypes.rst:48 +msgid "The first bit that will be new is::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:54 +msgid "" +"This is what a Noddy object will contain---in this case, nothing more than " +"what every Python object contains---a field called ``ob_base`` of type :c:" +"type:`PyObject`. :c:type:`PyObject` in turn, contains an ``ob_refcnt`` " +"field and a pointer to a type object. These can be accessed using the " +"macros :c:macro:`Py_REFCNT` and :c:macro:`Py_TYPE` respectively. These are " +"the fields the :c:macro:`PyObject_HEAD` macro brings in. The reason for the " +"macro is to standardize the layout and to enable special debugging fields in " +"debug builds." +msgstr "" + +#: ../Doc/extending/newtypes.rst:62 +msgid "" +"Note that there is no semicolon after the :c:macro:`PyObject_HEAD` macro; " +"one is included in the macro definition. Be wary of adding one by accident; " +"it's easy to do from habit, and your compiler might not complain, but " +"someone else's probably will! (On Windows, MSVC is known to call this an " +"error and refuse to compile the code.)" +msgstr "" + +#: ../Doc/extending/newtypes.rst:68 +msgid "" +"For contrast, let's take a look at the corresponding definition for standard " +"Python floats::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:76 +msgid "Moving on, we come to the crunch --- the type object. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:102 +msgid "" +"Now if you go and look up the definition of :c:type:`PyTypeObject` in :file:" +"`object.h` you'll see that it has many more fields that the definition " +"above. The remaining fields will be filled with zeros by the C compiler, " +"and it's common practice to not specify them explicitly unless you need them." +msgstr "" + +#: ../Doc/extending/newtypes.rst:107 +msgid "" +"This is so important that we're going to pick the top of it apart still " +"further::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:112 +msgid "This line is a bit of a wart; what we'd like to write is::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:116 +msgid "" +"as the type of a type object is \"type\", but this isn't strictly conforming " +"C and some compilers complain. Fortunately, this member will be filled in " +"for us by :c:func:`PyType_Ready`. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:122 +msgid "" +"The name of our type. This will appear in the default textual " +"representation of our objects and in some error messages, for example::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:130 +msgid "" +"Note that the name is a dotted name that includes both the module name and " +"the name of the type within the module. The module in this case is :mod:" +"`noddy` and the type is :class:`Noddy`, so we set the type name to :class:" +"`noddy.Noddy`. One side effect of using an undotted name is that the pydoc " +"documentation tool will not list the new type in the module documentation. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:138 +msgid "" +"This is so that Python knows how much memory to allocate when you call :c:" +"func:`PyObject_New`." +msgstr "" + +#: ../Doc/extending/newtypes.rst:143 +msgid "" +"If you want your type to be subclassable from Python, and your type has the " +"same :c:member:`~PyTypeObject.tp_basicsize` as its base type, you may have " +"problems with multiple inheritance. A Python subclass of your type will " +"have to list your type first in its :attr:`~class.__bases__`, or else it " +"will not be able to call your type's :meth:`__new__` method without getting " +"an error. You can avoid this problem by ensuring that your type has a " +"larger value for :c:member:`~PyTypeObject.tp_basicsize` than its base type " +"does. Most of the time, this will be true anyway, because either your base " +"type will be :class:`object`, or else you will be adding data members to " +"your base type, and therefore increasing its size." +msgstr "" + +#: ../Doc/extending/newtypes.rst:157 +msgid "" +"This has to do with variable length objects like lists and strings. Ignore " +"this for now." +msgstr "" + +#: ../Doc/extending/newtypes.rst:160 +msgid "" +"Skipping a number of type methods that we don't provide, we set the class " +"flags to :const:`Py_TPFLAGS_DEFAULT`. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:165 +msgid "" +"All types should include this constant in their flags. It enables all of " +"the members defined until at least Python 3.3. If you need further members, " +"you will need to OR the corresponding flags." +msgstr "" + +#: ../Doc/extending/newtypes.rst:169 +msgid "" +"We provide a doc string for the type in :c:member:`~PyTypeObject.tp_doc`. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:173 +msgid "" +"Now we get into the type methods, the things that make your objects " +"different from the others. We aren't going to implement any of these in " +"this version of the module. We'll expand this example later to have more " +"interesting behavior." +msgstr "" + +#: ../Doc/extending/newtypes.rst:177 +msgid "" +"For now, all we want to be able to do is to create new :class:`Noddy` " +"objects. To enable object creation, we have to provide a :c:member:" +"`~PyTypeObject.tp_new` implementation. In this case, we can just use the " +"default implementation provided by the API function :c:func:" +"`PyType_GenericNew`. We'd like to just assign this to the :c:member:" +"`~PyTypeObject.tp_new` slot, but we can't, for portability sake, On some " +"platforms or compilers, we can't statically initialize a structure member " +"with a function defined in another C module, so, instead, we'll assign the :" +"c:member:`~PyTypeObject.tp_new` slot in the module initialization function " +"just before calling :c:func:`PyType_Ready`::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:191 +msgid "" +"All the other type methods are *NULL*, so we'll go over them later --- " +"that's for a later section!" +msgstr "" + +#: ../Doc/extending/newtypes.rst:194 +msgid "" +"Everything else in the file should be familiar, except for some code in :c:" +"func:`PyInit_noddy`::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:200 +msgid "" +"This initializes the :class:`Noddy` type, filing in a number of members, " +"including :attr:`ob_type` that we initially set to *NULL*. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:205 +msgid "" +"This adds the type to the module dictionary. This allows us to create :" +"class:`Noddy` instances by calling the :class:`Noddy` class::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:211 +msgid "" +"That's it! All that remains is to build it; put the above code in a file " +"called :file:`noddy.c` and ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:218 +msgid "in a file called :file:`setup.py`; then typing" +msgstr "" + +#: ../Doc/extending/newtypes.rst:224 +msgid "" +"at a shell should produce a file :file:`noddy.so` in a subdirectory; move to " +"that directory and fire up Python --- you should be able to ``import noddy`` " +"and play around with Noddy objects." +msgstr "" + +#: ../Doc/extending/newtypes.rst:228 +msgid "That wasn't so hard, was it?" +msgstr "" + +#: ../Doc/extending/newtypes.rst:230 +msgid "" +"Of course, the current Noddy type is pretty uninteresting. It has no data " +"and doesn't do anything. It can't even be subclassed." +msgstr "" + +#: ../Doc/extending/newtypes.rst:235 +msgid "Adding data and methods to the Basic example" +msgstr "" + +#: ../Doc/extending/newtypes.rst:237 +msgid "" +"Let's extend the basic example to add some data and methods. Let's also " +"make the type usable as a base class. We'll create a new module, :mod:" +"`noddy2` that adds these capabilities:" +msgstr "" + +#: ../Doc/extending/newtypes.rst:244 +msgid "This version of the module has a number of changes." +msgstr "" + +#: ../Doc/extending/newtypes.rst:246 +msgid "We've added an extra include::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:250 +msgid "" +"This include provides declarations that we use to handle attributes, as " +"described a bit later." +msgstr "" + +#: ../Doc/extending/newtypes.rst:253 +msgid "" +"The name of the :class:`Noddy` object structure has been shortened to :class:" +"`Noddy`. The type object name has been shortened to :class:`NoddyType`." +msgstr "" + +#: ../Doc/extending/newtypes.rst:256 +msgid "" +"The :class:`Noddy` type now has three data attributes, *first*, *last*, and " +"*number*. The *first* and *last* variables are Python strings containing " +"first and last names. The *number* attribute is an integer." +msgstr "" + +#: ../Doc/extending/newtypes.rst:260 +msgid "The object structure is updated accordingly::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:269 +msgid "" +"Because we now have data to manage, we have to be more careful about object " +"allocation and deallocation. At a minimum, we need a deallocation method::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:280 +msgid "which is assigned to the :c:member:`~PyTypeObject.tp_dealloc` member::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:284 +msgid "" +"This method decrements the reference counts of the two Python attributes. We " +"use :c:func:`Py_XDECREF` here because the :attr:`first` and :attr:`last` " +"members could be *NULL*. It then calls the :c:member:`~PyTypeObject." +"tp_free` member of the object's type to free the object's memory. Note that " +"the object's type might not be :class:`NoddyType`, because the object may be " +"an instance of a subclass." +msgstr "" + +#: ../Doc/extending/newtypes.rst:290 +msgid "" +"We want to make sure that the first and last names are initialized to empty " +"strings, so we provide a new method::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:318 +msgid "and install it in the :c:member:`~PyTypeObject.tp_new` member::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:322 +msgid "" +"The new member is responsible for creating (as opposed to initializing) " +"objects of the type. It is exposed in Python as the :meth:`__new__` " +"method. See the paper titled \"Unifying types and classes in Python\" for a " +"detailed discussion of the :meth:`__new__` method. One reason to implement " +"a new method is to assure the initial values of instance variables. In this " +"case, we use the new method to make sure that the initial values of the " +"members :attr:`first` and :attr:`last` are not *NULL*. If we didn't care " +"whether the initial values were *NULL*, we could have used :c:func:" +"`PyType_GenericNew` as our new method, as we did before. :c:func:" +"`PyType_GenericNew` initializes all of the instance variable members to " +"*NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:333 +msgid "" +"The new method is a static method that is passed the type being instantiated " +"and any arguments passed when the type was called, and that returns the new " +"object created. New methods always accept positional and keyword arguments, " +"but they often ignore the arguments, leaving the argument handling to " +"initializer methods. Note that if the type supports subclassing, the type " +"passed may not be the type being defined. The new method calls the :c:" +"member:`~PyTypeObject.tp_alloc` slot to allocate memory. We don't fill the :" +"c:member:`~PyTypeObject.tp_alloc` slot ourselves. Rather :c:func:" +"`PyType_Ready` fills it for us by inheriting it from our base class, which " +"is :class:`object` by default. Most types use the default allocation." +msgstr "" + +#: ../Doc/extending/newtypes.rst:345 +msgid "" +"If you are creating a co-operative :c:member:`~PyTypeObject.tp_new` (one " +"that calls a base type's :c:member:`~PyTypeObject.tp_new` or :meth:" +"`__new__`), you must *not* try to determine what method to call using method " +"resolution order at runtime. Always statically determine what type you are " +"going to call, and call its :c:member:`~PyTypeObject.tp_new` directly, or " +"via ``type->tp_base->tp_new``. If you do not do this, Python subclasses of " +"your type that also inherit from other Python-defined classes may not work " +"correctly. (Specifically, you may not be able to create instances of such " +"subclasses without getting a :exc:`TypeError`.)" +msgstr "" + +#: ../Doc/extending/newtypes.rst:354 +msgid "We provide an initialization function::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:385 +msgid "by filling the :c:member:`~PyTypeObject.tp_init` slot. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:389 +msgid "" +"The :c:member:`~PyTypeObject.tp_init` slot is exposed in Python as the :meth:" +"`__init__` method. It is used to initialize an object after it's created. " +"Unlike the new method, we can't guarantee that the initializer is called. " +"The initializer isn't called when unpickling objects and it can be " +"overridden. Our initializer accepts arguments to provide initial values for " +"our instance. Initializers always accept positional and keyword arguments. " +"Initializers should return either 0 on success or -1 on error." +msgstr "" + +#: ../Doc/extending/newtypes.rst:397 +msgid "" +"Initializers can be called multiple times. Anyone can call the :meth:" +"`__init__` method on our objects. For this reason, we have to be extra " +"careful when assigning the new values. We might be tempted, for example to " +"assign the :attr:`first` member like this::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:408 +msgid "" +"But this would be risky. Our type doesn't restrict the type of the :attr:" +"`first` member, so it could be any kind of object. It could have a " +"destructor that causes code to be executed that tries to access the :attr:" +"`first` member. To be paranoid and protect ourselves against this " +"possibility, we almost always reassign members before decrementing their " +"reference counts. When don't we have to do this?" +msgstr "" + +#: ../Doc/extending/newtypes.rst:415 +msgid "when we absolutely know that the reference count is greater than 1" +msgstr "" + +#: ../Doc/extending/newtypes.rst:417 +msgid "" +"when we know that deallocation of the object [#]_ will not cause any calls " +"back into our type's code" +msgstr "" + +#: ../Doc/extending/newtypes.rst:420 +msgid "" +"when decrementing a reference count in a :c:member:`~PyTypeObject." +"tp_dealloc` handler when garbage-collections is not supported [#]_" +msgstr "" + +#: ../Doc/extending/newtypes.rst:423 +msgid "" +"We want to expose our instance variables as attributes. There are a number " +"of ways to do that. The simplest way is to define member definitions::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:436 +msgid "" +"and put the definitions in the :c:member:`~PyTypeObject.tp_members` slot::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:440 +msgid "" +"Each member definition has a member name, type, offset, access flags and " +"documentation string. See the :ref:`Generic-Attribute-Management` section " +"below for details." +msgstr "" + +#: ../Doc/extending/newtypes.rst:444 +msgid "" +"A disadvantage of this approach is that it doesn't provide a way to restrict " +"the types of objects that can be assigned to the Python attributes. We " +"expect the first and last names to be strings, but any Python objects can be " +"assigned. Further, the attributes can be deleted, setting the C pointers to " +"*NULL*. Even though we can make sure the members are initialized to non-" +"*NULL* values, the members can be set to *NULL* if the attributes are " +"deleted." +msgstr "" + +#: ../Doc/extending/newtypes.rst:451 +msgid "" +"We define a single method, :meth:`name`, that outputs the objects name as " +"the concatenation of the first and last names. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:470 +msgid "" +"The method is implemented as a C function that takes a :class:`Noddy` (or :" +"class:`Noddy` subclass) instance as the first argument. Methods always take " +"an instance as the first argument. Methods often take positional and keyword " +"arguments as well, but in this case we don't take any and don't need to " +"accept a positional argument tuple or keyword argument dictionary. This " +"method is equivalent to the Python method::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:480 +msgid "" +"Note that we have to check for the possibility that our :attr:`first` and :" +"attr:`last` members are *NULL*. This is because they can be deleted, in " +"which case they are set to *NULL*. It would be better to prevent deletion " +"of these attributes and to restrict the attribute values to be strings. " +"We'll see how to do that in the next section." +msgstr "" + +#: ../Doc/extending/newtypes.rst:486 +msgid "" +"Now that we've defined the method, we need to create an array of method " +"definitions::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:496 +msgid "and assign them to the :c:member:`~PyTypeObject.tp_methods` slot::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:500 +msgid "" +"Note that we used the :const:`METH_NOARGS` flag to indicate that the method " +"is passed no arguments." +msgstr "" + +#: ../Doc/extending/newtypes.rst:503 +msgid "" +"Finally, we'll make our type usable as a base class. We've written our " +"methods carefully so far so that they don't make any assumptions about the " +"type of the object being created or used, so all we need to do is to add " +"the :const:`Py_TPFLAGS_BASETYPE` to our class flag definition::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:510 +msgid "" +"We rename :c:func:`PyInit_noddy` to :c:func:`PyInit_noddy2` and update the " +"module name in the :c:type:`PyModuleDef` struct." +msgstr "" + +#: ../Doc/extending/newtypes.rst:513 +msgid "Finally, we update our :file:`setup.py` file to build the new module::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:524 +msgid "Providing finer control over data attributes" +msgstr "" + +#: ../Doc/extending/newtypes.rst:526 +msgid "" +"In this section, we'll provide finer control over how the :attr:`first` and :" +"attr:`last` attributes are set in the :class:`Noddy` example. In the " +"previous version of our module, the instance variables :attr:`first` and :" +"attr:`last` could be set to non-string values or even deleted. We want to " +"make sure that these attributes always contain strings." +msgstr "" + +#: ../Doc/extending/newtypes.rst:535 +msgid "" +"To provide greater control, over the :attr:`first` and :attr:`last` " +"attributes, we'll use custom getter and setter functions. Here are the " +"functions for getting and setting the :attr:`first` attribute::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:566 +msgid "" +"The getter function is passed a :class:`Noddy` object and a \"closure\", " +"which is void pointer. In this case, the closure is ignored. (The closure " +"supports an advanced usage in which definition data is passed to the getter " +"and setter. This could, for example, be used to allow a single set of getter " +"and setter functions that decide the attribute to get or set based on data " +"in the closure.)" +msgstr "" + +#: ../Doc/extending/newtypes.rst:572 +msgid "" +"The setter function is passed the :class:`Noddy` object, the new value, and " +"the closure. The new value may be *NULL*, in which case the attribute is " +"being deleted. In our setter, we raise an error if the attribute is deleted " +"or if the attribute value is not a string." +msgstr "" + +#: ../Doc/extending/newtypes.rst:577 +msgid "We create an array of :c:type:`PyGetSetDef` structures::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:591 +msgid "and register it in the :c:member:`~PyTypeObject.tp_getset` slot::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:595 +msgid "to register our attribute getters and setters." +msgstr "" + +#: ../Doc/extending/newtypes.rst:597 +msgid "" +"The last item in a :c:type:`PyGetSetDef` structure is the closure mentioned " +"above. In this case, we aren't using the closure, so we just pass *NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:600 +msgid "We also remove the member definitions for these attributes::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:608 +msgid "" +"We also need to update the :c:member:`~PyTypeObject.tp_init` handler to only " +"allow strings [#]_ to be passed::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:640 +msgid "" +"With these changes, we can assure that the :attr:`first` and :attr:`last` " +"members are never *NULL* so we can remove checks for *NULL* values in almost " +"all cases. This means that most of the :c:func:`Py_XDECREF` calls can be " +"converted to :c:func:`Py_DECREF` calls. The only place we can't change these " +"calls is in the deallocator, where there is the possibility that the " +"initialization of these members failed in the constructor." +msgstr "" + +#: ../Doc/extending/newtypes.rst:647 +msgid "" +"We also rename the module initialization function and module name in the " +"initialization function, as we did before, and we add an extra definition to " +"the :file:`setup.py` file." +msgstr "" + +#: ../Doc/extending/newtypes.rst:653 +msgid "Supporting cyclic garbage collection" +msgstr "" + +#: ../Doc/extending/newtypes.rst:655 +msgid "" +"Python has a cyclic-garbage collector that can identify unneeded objects " +"even when their reference counts are not zero. This can happen when objects " +"are involved in cycles. For example, consider::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:663 +msgid "" +"In this example, we create a list that contains itself. When we delete it, " +"it still has a reference from itself. Its reference count doesn't drop to " +"zero. Fortunately, Python's cyclic-garbage collector will eventually figure " +"out that the list is garbage and free it." +msgstr "" + +#: ../Doc/extending/newtypes.rst:668 +msgid "" +"In the second version of the :class:`Noddy` example, we allowed any kind of " +"object to be stored in the :attr:`first` or :attr:`last` attributes. [#]_ " +"This means that :class:`Noddy` objects can participate in cycles::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:677 +msgid "" +"This is pretty silly, but it gives us an excuse to add support for the " +"cyclic-garbage collector to the :class:`Noddy` example. To support cyclic " +"garbage collection, types need to fill two slots and set a class flag that " +"enables these slots:" +msgstr "" + +#: ../Doc/extending/newtypes.rst:685 +msgid "" +"The traversal method provides access to subobjects that could participate in " +"cycles::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:707 +msgid "" +"For each subobject that can participate in cycles, we need to call the :c:" +"func:`visit` function, which is passed to the traversal method. The :c:func:" +"`visit` function takes as arguments the subobject and the extra argument " +"*arg* passed to the traversal method. It returns an integer value that must " +"be returned if it is non-zero." +msgstr "" + +#: ../Doc/extending/newtypes.rst:713 +msgid "" +"Python provides a :c:func:`Py_VISIT` macro that automates calling visit " +"functions. With :c:func:`Py_VISIT`, :c:func:`Noddy_traverse` can be " +"simplified::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:726 +msgid "" +"Note that the :c:member:`~PyTypeObject.tp_traverse` implementation must name " +"its arguments exactly *visit* and *arg* in order to use :c:func:`Py_VISIT`. " +"This is to encourage uniformity across these boring implementations." +msgstr "" + +#: ../Doc/extending/newtypes.rst:730 +msgid "" +"We also need to provide a method for clearing any subobjects that can " +"participate in cycles. We implement the method and reimplement the " +"deallocator to use it::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:757 +msgid "" +"Notice the use of a temporary variable in :c:func:`Noddy_clear`. We use the " +"temporary variable so that we can set each member to *NULL* before " +"decrementing its reference count. We do this because, as was discussed " +"earlier, if the reference count drops to zero, we might cause code to run " +"that calls back into the object. In addition, because we now support " +"garbage collection, we also have to worry about code being run that triggers " +"garbage collection. If garbage collection is run, our :c:member:" +"`~PyTypeObject.tp_traverse` handler could get called. We can't take a chance " +"of having :c:func:`Noddy_traverse` called when a member's reference count " +"has dropped to zero and its value hasn't been set to *NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:767 +msgid "" +"Python provides a :c:func:`Py_CLEAR` that automates the careful decrementing " +"of reference counts. With :c:func:`Py_CLEAR`, the :c:func:`Noddy_clear` " +"function can be simplified::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:779 +msgid "" +"Finally, we add the :const:`Py_TPFLAGS_HAVE_GC` flag to the class flags::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:783 +msgid "" +"That's pretty much it. If we had written custom :c:member:`~PyTypeObject." +"tp_alloc` or :c:member:`~PyTypeObject.tp_free` slots, we'd need to modify " +"them for cyclic-garbage collection. Most extensions will use the versions " +"automatically provided." +msgstr "" + +#: ../Doc/extending/newtypes.rst:789 +msgid "Subclassing other types" +msgstr "" + +#: ../Doc/extending/newtypes.rst:791 +msgid "" +"It is possible to create new extension types that are derived from existing " +"types. It is easiest to inherit from the built in types, since an extension " +"can easily use the :class:`PyTypeObject` it needs. It can be difficult to " +"share these :class:`PyTypeObject` structures between extension modules." +msgstr "" + +#: ../Doc/extending/newtypes.rst:796 +msgid "" +"In this example we will create a :class:`Shoddy` type that inherits from the " +"built-in :class:`list` type. The new type will be completely compatible with " +"regular lists, but will have an additional :meth:`increment` method that " +"increases an internal counter. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:814 +msgid "" +"As you can see, the source code closely resembles the :class:`Noddy` " +"examples in previous sections. We will break down the main differences " +"between them. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:822 +msgid "" +"The primary difference for derived type objects is that the base type's " +"object structure must be the first value. The base type will already include " +"the :c:func:`PyObject_HEAD` at the beginning of its structure." +msgstr "" + +#: ../Doc/extending/newtypes.rst:826 +msgid "" +"When a Python object is a :class:`Shoddy` instance, its *PyObject\\** " +"pointer can be safely cast to both *PyListObject\\** and *Shoddy\\**. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:838 +msgid "" +"In the :attr:`__init__` method for our type, we can see how to call through " +"to the :attr:`__init__` method of the base type." +msgstr "" + +#: ../Doc/extending/newtypes.rst:841 +msgid "" +"This pattern is important when writing a type with custom :attr:`new` and :" +"attr:`dealloc` methods. The :attr:`new` method should not actually create " +"the memory for the object with :c:member:`~PyTypeObject.tp_alloc`, that will " +"be handled by the base class when calling its :c:member:`~PyTypeObject." +"tp_new`." +msgstr "" + +#: ../Doc/extending/newtypes.rst:846 +msgid "" +"When filling out the :c:func:`PyTypeObject` for the :class:`Shoddy` type, " +"you see a slot for :c:func:`tp_base`. Due to cross platform compiler issues, " +"you can't fill that field directly with the :c:func:`PyList_Type`; it can be " +"done later in the module's :c:func:`init` function. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:869 +msgid "" +"Before calling :c:func:`PyType_Ready`, the type structure must have the :c:" +"member:`~PyTypeObject.tp_base` slot filled in. When we are deriving a new " +"type, it is not necessary to fill out the :c:member:`~PyTypeObject.tp_alloc` " +"slot with :c:func:`PyType_GenericNew` -- the allocate function from the base " +"type will be inherited." +msgstr "" + +#: ../Doc/extending/newtypes.rst:874 +msgid "" +"After that, calling :c:func:`PyType_Ready` and adding the type object to the " +"module is the same as with the basic :class:`Noddy` examples." +msgstr "" + +#: ../Doc/extending/newtypes.rst:881 +msgid "Type Methods" +msgstr "" + +#: ../Doc/extending/newtypes.rst:883 +msgid "" +"This section aims to give a quick fly-by on the various type methods you can " +"implement and what they do." +msgstr "" + +#: ../Doc/extending/newtypes.rst:886 +msgid "" +"Here is the definition of :c:type:`PyTypeObject`, with some fields only used " +"in debug builds omitted:" +msgstr "" + +#: ../Doc/extending/newtypes.rst:892 +msgid "" +"Now that's a *lot* of methods. Don't worry too much though - if you have a " +"type you want to define, the chances are very good that you will only " +"implement a handful of these." +msgstr "" + +#: ../Doc/extending/newtypes.rst:896 +msgid "" +"As you probably expect by now, we're going to go over this and give more " +"information about the various handlers. We won't go in the order they are " +"defined in the structure, because there is a lot of historical baggage that " +"impacts the ordering of the fields; be sure your type initialization keeps " +"the fields in the right order! It's often easiest to find an example that " +"includes all the fields you need (even if they're initialized to ``0``) and " +"then change the values to suit your new type. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:906 +msgid "" +"The name of the type - as mentioned in the last section, this will appear in " +"various places, almost entirely for diagnostic purposes. Try to choose " +"something that will be helpful in such a situation! ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:912 +msgid "" +"These fields tell the runtime how much memory to allocate when new objects " +"of this type are created. Python has some built-in support for variable " +"length structures (think: strings, lists) which is where the :c:member:" +"`~PyTypeObject.tp_itemsize` field comes in. This will be dealt with " +"later. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:919 +msgid "" +"Here you can put a string (or its address) that you want returned when the " +"Python script references ``obj.__doc__`` to retrieve the doc string." +msgstr "" + +#: ../Doc/extending/newtypes.rst:922 +msgid "" +"Now we come to the basic type methods---the ones most extension types will " +"implement." +msgstr "" + +#: ../Doc/extending/newtypes.rst:927 +msgid "Finalization and De-allocation" +msgstr "" + +#: ../Doc/extending/newtypes.rst:939 +msgid "" +"This function is called when the reference count of the instance of your " +"type is reduced to zero and the Python interpreter wants to reclaim it. If " +"your type has memory to free or other clean-up to perform, you can put it " +"here. The object itself needs to be freed here as well. Here is an example " +"of this function::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:956 +msgid "" +"One important requirement of the deallocator function is that it leaves any " +"pending exceptions alone. This is important since deallocators are " +"frequently called as the interpreter unwinds the Python stack; when the " +"stack is unwound due to an exception (rather than normal returns), nothing " +"is done to protect the deallocators from seeing that an exception has " +"already been set. Any actions which a deallocator performs which may cause " +"additional Python code to be executed may detect that an exception has been " +"set. This can lead to misleading errors from the interpreter. The proper " +"way to protect against this is to save a pending exception before performing " +"the unsafe action, and restoring it when done. This can be done using the :" +"c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore` functions::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:995 +msgid "" +"There are limitations to what you can safely do in a deallocator function. " +"First, if your type supports garbage collection (using :c:member:" +"`~PyTypeObject.tp_traverse` and/or :c:member:`~PyTypeObject.tp_clear`), some " +"of the object's members can have been cleared or finalized by the time :c:" +"member:`~PyTypeObject.tp_dealloc` is called. Second, in :c:member:" +"`~PyTypeObject.tp_dealloc`, your object is in an unstable state: its " +"reference count is equal to zero. Any call to a non-trivial object or API " +"(as in the example above) might end up calling :c:member:`~PyTypeObject." +"tp_dealloc` again, causing a double free and a crash." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1004 +msgid "" +"Starting with Python 3.4, it is recommended not to put any complex " +"finalization code in :c:member:`~PyTypeObject.tp_dealloc`, and instead use " +"the new :c:member:`~PyTypeObject.tp_finalize` type method." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1009 +msgid ":pep:`442` explains the new finalization scheme." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1016 +msgid "Object Presentation" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1018 +msgid "" +"In Python, there are two ways to generate a textual representation of an " +"object: the :func:`repr` function, and the :func:`str` function. (The :func:" +"`print` function just calls :func:`str`.) These handlers are both optional." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1027 +msgid "" +"The :c:member:`~PyTypeObject.tp_repr` handler should return a string object " +"containing a representation of the instance for which it is called. Here is " +"a simple example::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1038 +msgid "" +"If no :c:member:`~PyTypeObject.tp_repr` handler is specified, the " +"interpreter will supply a representation that uses the type's :c:member:" +"`~PyTypeObject.tp_name` and a uniquely-identifying value for the object." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1042 +msgid "" +"The :c:member:`~PyTypeObject.tp_str` handler is to :func:`str` what the :c:" +"member:`~PyTypeObject.tp_repr` handler described above is to :func:`repr`; " +"that is, it is called when Python code calls :func:`str` on an instance of " +"your object. Its implementation is very similar to the :c:member:" +"`~PyTypeObject.tp_repr` function, but the resulting string is intended for " +"human consumption. If :c:member:`~PyTypeObject.tp_str` is not specified, " +"the :c:member:`~PyTypeObject.tp_repr` handler is used instead." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1049 +msgid "Here is a simple example::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1061 +msgid "Attribute Management" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1063 +msgid "" +"For every object which can support attributes, the corresponding type must " +"provide the functions that control how the attributes are resolved. There " +"needs to be a function which can retrieve attributes (if any are defined), " +"and another to set attributes (if setting attributes is allowed). Removing " +"an attribute is a special case, for which the new value passed to the " +"handler is *NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1069 +msgid "" +"Python supports two pairs of attribute handlers; a type that supports " +"attributes only needs to implement the functions for one pair. The " +"difference is that one pair takes the name of the attribute as a :c:type:" +"`char\\*`, while the other accepts a :c:type:`PyObject\\*`. Each type can " +"use whichever pair makes more sense for the implementation's convenience. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1081 +msgid "" +"If accessing attributes of an object is always a simple operation (this will " +"be explained shortly), there are generic implementations which can be used " +"to provide the :c:type:`PyObject\\*` version of the attribute management " +"functions. The actual need for type-specific attribute handlers almost " +"completely disappeared starting with Python 2.2, though there are many " +"examples which have not been updated to use some of the new generic " +"mechanism that is available." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1092 +msgid "Generic Attribute Management" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1094 +msgid "" +"Most extension types only use *simple* attributes. So, what makes the " +"attributes simple? There are only a couple of conditions that must be met:" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1097 +msgid "" +"The name of the attributes must be known when :c:func:`PyType_Ready` is " +"called." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1100 +msgid "" +"No special processing is needed to record that an attribute was looked up or " +"set, nor do actions need to be taken based on the value." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1103 +msgid "" +"Note that this list does not place any restrictions on the values of the " +"attributes, when the values are computed, or how relevant data is stored." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1106 +msgid "" +"When :c:func:`PyType_Ready` is called, it uses three tables referenced by " +"the type object to create :term:`descriptor`\\s which are placed in the " +"dictionary of the type object. Each descriptor controls access to one " +"attribute of the instance object. Each of the tables is optional; if all " +"three are *NULL*, instances of the type will only have attributes that are " +"inherited from their base type, and should leave the :c:member:" +"`~PyTypeObject.tp_getattro` and :c:member:`~PyTypeObject.tp_setattro` fields " +"*NULL* as well, allowing the base type to handle attributes." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1114 +msgid "The tables are declared as three fields of the type object::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1120 +msgid "" +"If :c:member:`~PyTypeObject.tp_methods` is not *NULL*, it must refer to an " +"array of :c:type:`PyMethodDef` structures. Each entry in the table is an " +"instance of this structure::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1131 +msgid "" +"One entry should be defined for each method provided by the type; no entries " +"are needed for methods inherited from a base type. One additional entry is " +"needed at the end; it is a sentinel that marks the end of the array. The :" +"attr:`ml_name` field of the sentinel must be *NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1136 +msgid "" +"The second table is used to define attributes which map directly to data " +"stored in the instance. A variety of primitive C types are supported, and " +"access may be read-only or read-write. The structures in the table are " +"defined as::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1148 +msgid "" +"For each entry in the table, a :term:`descriptor` will be constructed and " +"added to the type which will be able to extract a value from the instance " +"structure. The :attr:`type` field should contain one of the type codes " +"defined in the :file:`structmember.h` header; the value will be used to " +"determine how to convert Python values to and from C values. The :attr:" +"`flags` field is used to store flags which control how the attribute can be " +"accessed." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1155 +msgid "" +"The following flag constants are defined in :file:`structmember.h`; they may " +"be combined using bitwise-OR." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1159 +msgid "Constant" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1159 +msgid "Meaning" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1161 +msgid ":const:`READONLY`" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1161 +msgid "Never writable." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1163 +msgid ":const:`READ_RESTRICTED`" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1163 +msgid "Not readable in restricted mode." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1165 +msgid ":const:`WRITE_RESTRICTED`" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1165 +msgid "Not writable in restricted mode." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1167 +msgid ":const:`RESTRICTED`" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1167 +msgid "Not readable or writable in restricted mode." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1176 +msgid "" +"An interesting advantage of using the :c:member:`~PyTypeObject.tp_members` " +"table to build descriptors that are used at runtime is that any attribute " +"defined this way can have an associated doc string simply by providing the " +"text in the table. An application can use the introspection API to retrieve " +"the descriptor from the class object, and get the doc string using its :attr:" +"`__doc__` attribute." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1182 +msgid "" +"As with the :c:member:`~PyTypeObject.tp_methods` table, a sentinel entry " +"with a :attr:`name` value of *NULL* is required." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1196 +msgid "Type-specific Attribute Management" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1198 +msgid "" +"For simplicity, only the :c:type:`char\\*` version will be demonstrated " +"here; the type of the name parameter is the only difference between the :c:" +"type:`char\\*` and :c:type:`PyObject\\*` flavors of the interface. This " +"example effectively does the same thing as the generic example above, but " +"does not use the generic support added in Python 2.2. It explains how the " +"handler functions are called, so that if you do need to extend their " +"functionality, you'll understand what needs to be done." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1206 +msgid "" +"The :c:member:`~PyTypeObject.tp_getattr` handler is called when the object " +"requires an attribute look-up. It is called in the same situations where " +"the :meth:`__getattr__` method of a class would be called." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1210 +msgid "Here is an example::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1226 +msgid "" +"The :c:member:`~PyTypeObject.tp_setattr` handler is called when the :meth:" +"`__setattr__` or :meth:`__delattr__` method of a class instance would be " +"called. When an attribute should be deleted, the third parameter will be " +"*NULL*. Here is an example that simply raises an exception; if this were " +"really all you wanted, the :c:member:`~PyTypeObject.tp_setattr` handler " +"should be set to *NULL*. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1240 +msgid "Object Comparison" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1246 +msgid "" +"The :c:member:`~PyTypeObject.tp_richcompare` handler is called when " +"comparisons are needed. It is analogous to the :ref:`rich comparison " +"methods `, like :meth:`__lt__`, and also called by :c:func:" +"`PyObject_RichCompare` and :c:func:`PyObject_RichCompareBool`." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1251 +msgid "" +"This function is called with two Python objects and the operator as " +"arguments, where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, " +"``Py_GT``, ``Py_LT`` or ``Py_GT``. It should compare the two objects with " +"respect to the specified operator and return ``Py_True`` or ``Py_False`` if " +"the comparison is successful, ``Py_NotImplemented`` to indicate that " +"comparison is not implemented and the other object's comparison method " +"should be tried, or *NULL* if an exception was set." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1259 +msgid "" +"Here is a sample implementation, for a datatype that is considered equal if " +"the size of an internal pointer is equal::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1289 +msgid "Abstract Protocol Support" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1291 +msgid "" +"Python supports a variety of *abstract* 'protocols;' the specific interfaces " +"provided to use these interfaces are documented in :ref:`abstract`." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1295 +msgid "" +"A number of these abstract interfaces were defined early in the development " +"of the Python implementation. In particular, the number, mapping, and " +"sequence protocols have been part of Python since the beginning. Other " +"protocols have been added over time. For protocols which depend on several " +"handler routines from the type implementation, the older protocols have been " +"defined as optional blocks of handlers referenced by the type object. For " +"newer protocols there are additional slots in the main type object, with a " +"flag bit being set to indicate that the slots are present and should be " +"checked by the interpreter. (The flag bit does not indicate that the slot " +"values are non-*NULL*. The flag may be set to indicate the presence of a " +"slot, but a slot may still be unfilled.) ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1310 +msgid "" +"If you wish your object to be able to act like a number, a sequence, or a " +"mapping object, then you place the address of a structure that implements " +"the C type :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, or :c:" +"type:`PyMappingMethods`, respectively. It is up to you to fill in this " +"structure with appropriate values. You can find examples of the use of each " +"of these in the :file:`Objects` directory of the Python source " +"distribution. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1319 +msgid "" +"This function, if you choose to provide it, should return a hash number for " +"an instance of your data type. Here is a moderately pointless example::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1335 +msgid "" +"This function is called when an instance of your data type is \"called\", " +"for example, if ``obj1`` is an instance of your data type and the Python " +"script contains ``obj1('hello')``, the :c:member:`~PyTypeObject.tp_call` " +"handler is invoked." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1339 +msgid "This function takes three arguments:" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1341 +msgid "" +"*arg1* is the instance of the data type which is the subject of the call. If " +"the call is ``obj1('hello')``, then *arg1* is ``obj1``." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1344 +msgid "" +"*arg2* is a tuple containing the arguments to the call. You can use :c:func:" +"`PyArg_ParseTuple` to extract the arguments." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1347 +msgid "" +"*arg3* is a dictionary of keyword arguments that were passed. If this is non-" +"*NULL* and you support keyword arguments, use :c:func:" +"`PyArg_ParseTupleAndKeywords` to extract the arguments. If you do not want " +"to support keyword arguments and this is non-*NULL*, raise a :exc:" +"`TypeError` with a message saying that keyword arguments are not supported." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1353 +msgid "" +"Here is a desultory example of the implementation of the call function. ::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1384 +msgid "" +"These functions provide support for the iterator protocol. Any object which " +"wishes to support iteration over its contents (which may be generated during " +"iteration) must implement the ``tp_iter`` handler. Objects which are " +"returned by a ``tp_iter`` handler must implement both the ``tp_iter`` and " +"``tp_iternext`` handlers. Both handlers take exactly one parameter, the " +"instance for which they are being called, and return a new reference. In " +"the case of an error, they should set an exception and return *NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1392 +msgid "" +"For an object which represents an iterable collection, the ``tp_iter`` " +"handler must return an iterator object. The iterator object is responsible " +"for maintaining the state of the iteration. For collections which can " +"support multiple iterators which do not interfere with each other (as lists " +"and tuples do), a new iterator should be created and returned. Objects " +"which can only be iterated over once (usually due to side effects of " +"iteration) should implement this handler by returning a new reference to " +"themselves, and should also implement the ``tp_iternext`` handler. File " +"objects are an example of such an iterator." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1402 +msgid "" +"Iterator objects should implement both handlers. The ``tp_iter`` handler " +"should return a new reference to the iterator (this is the same as the " +"``tp_iter`` handler for objects which can only be iterated over " +"destructively). The ``tp_iternext`` handler should return a new reference " +"to the next object in the iteration if there is one. If the iteration has " +"reached the end, it may return *NULL* without setting an exception or it may " +"set :exc:`StopIteration`; avoiding the exception can yield slightly better " +"performance. If an actual error occurs, it should set an exception and " +"return *NULL*." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1415 +msgid "Weak Reference Support" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1417 +msgid "" +"One of the goals of Python's weak-reference implementation is to allow any " +"type to participate in the weak reference mechanism without incurring the " +"overhead on those objects which do not benefit by weak referencing (such as " +"numbers)." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1421 +msgid "" +"For an object to be weakly referencable, the extension must include a :c:" +"type:`PyObject\\*` field in the instance structure for the use of the weak " +"reference mechanism; it must be initialized to *NULL* by the object's " +"constructor. It must also set the :c:member:`~PyTypeObject." +"tp_weaklistoffset` field of the corresponding type object to the offset of " +"the field. For example, the instance type is defined with the following " +"structure::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1435 +msgid "The statically-declared type object for instances is defined this way::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1452 +msgid "" +"The type constructor is responsible for initializing the weak reference list " +"to *NULL*::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1464 +msgid "" +"The only further addition is that the destructor needs to call the weak " +"reference manager to clear any weak references. This is only required if " +"the weak reference list is non-*NULL*::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1483 +msgid "More Suggestions" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1485 +msgid "" +"Remember that you can omit most of these functions, in which case you " +"provide ``0`` as a value. There are type definitions for each of the " +"functions you must provide. They are in :file:`object.h` in the Python " +"include directory that comes with the source distribution of Python." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1490 +msgid "" +"In order to learn how to implement any specific method for your new data " +"type, do the following: Download and unpack the Python source distribution. " +"Go to the :file:`Objects` directory, then search the C source files for " +"``tp_`` plus the function you want (for example, ``tp_richcompare``). You " +"will find examples of the function you want to implement." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1496 +msgid "" +"When you need to verify that an object is an instance of the type you are " +"implementing, use the :c:func:`PyObject_TypeCheck` function. A sample of its " +"use might be something like the following::" +msgstr "" + +#: ../Doc/extending/newtypes.rst:1507 +msgid "" +"This is true when we know that the object is a basic type, like a string or " +"a float." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1510 +msgid "" +"We relied on this in the :c:member:`~PyTypeObject.tp_dealloc` handler in " +"this example, because our type doesn't support garbage collection. Even if a " +"type supports garbage collection, there are calls that can be made to " +"\"untrack\" the object from garbage collection, however, these calls are " +"advanced and not covered here." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1515 +msgid "" +"We now know that the first and last members are strings, so perhaps we could " +"be less careful about decrementing their reference counts, however, we " +"accept instances of string subclasses. Even though deallocating normal " +"strings won't call back into our objects, we can't guarantee that " +"deallocating an instance of a string subclass won't call back into our " +"objects." +msgstr "" + +#: ../Doc/extending/newtypes.rst:1521 +msgid "" +"Even in the third version, we aren't guaranteed to avoid cycles. Instances " +"of string subclasses are allowed and string subclasses could allow cycles " +"even if normal strings don't." +msgstr "" + +#: ../Doc/extending/windows.rst:8 +msgid "Building C and C++ Extensions on Windows" +msgstr "" + +#: ../Doc/extending/windows.rst:10 +msgid "" +"This chapter briefly explains how to create a Windows extension module for " +"Python using Microsoft Visual C++, and follows with more detailed background " +"information on how it works. The explanatory material is useful for both " +"the Windows programmer learning to build Python extensions and the Unix " +"programmer interested in producing software which can be successfully built " +"on both Unix and Windows." +msgstr "" + +#: ../Doc/extending/windows.rst:17 +msgid "" +"Module authors are encouraged to use the distutils approach for building " +"extension modules, instead of the one described in this section. You will " +"still need the C compiler that was used to build Python; typically Microsoft " +"Visual C++." +msgstr "" + +#: ../Doc/extending/windows.rst:24 +msgid "" +"This chapter mentions a number of filenames that include an encoded Python " +"version number. These filenames are represented with the version number " +"shown as ``XY``; in practice, ``'X'`` will be the major version number and " +"``'Y'`` will be the minor version number of the Python release you're " +"working with. For example, if you are using Python 2.2.1, ``XY`` will " +"actually be ``22``." +msgstr "" + +#: ../Doc/extending/windows.rst:34 +msgid "A Cookbook Approach" +msgstr "" + +#: ../Doc/extending/windows.rst:36 +msgid "" +"There are two approaches to building extension modules on Windows, just as " +"there are on Unix: use the :mod:`distutils` package to control the build " +"process, or do things manually. The distutils approach works well for most " +"extensions; documentation on using :mod:`distutils` to build and package " +"extension modules is available in :ref:`distutils-index`. If you find you " +"really need to do things manually, it may be instructive to study the " +"project file for the :source:`winsound ` standard " +"library module." +msgstr "" + +#: ../Doc/extending/windows.rst:48 +msgid "Differences Between Unix and Windows" +msgstr "" + +#: ../Doc/extending/windows.rst:53 +msgid "" +"Unix and Windows use completely different paradigms for run-time loading of " +"code. Before you try to build a module that can be dynamically loaded, be " +"aware of how your system works." +msgstr "" + +#: ../Doc/extending/windows.rst:57 +msgid "" +"In Unix, a shared object (:file:`.so`) file contains code to be used by the " +"program, and also the names of functions and data that it expects to find in " +"the program. When the file is joined to the program, all references to " +"those functions and data in the file's code are changed to point to the " +"actual locations in the program where the functions and data are placed in " +"memory. This is basically a link operation." +msgstr "" + +#: ../Doc/extending/windows.rst:64 +msgid "" +"In Windows, a dynamic-link library (:file:`.dll`) file has no dangling " +"references. Instead, an access to functions or data goes through a lookup " +"table. So the DLL code does not have to be fixed up at runtime to refer to " +"the program's memory; instead, the code already uses the DLL's lookup table, " +"and the lookup table is modified at runtime to point to the functions and " +"data." +msgstr "" + +#: ../Doc/extending/windows.rst:70 +msgid "" +"In Unix, there is only one type of library file (:file:`.a`) which contains " +"code from several object files (:file:`.o`). During the link step to create " +"a shared object file (:file:`.so`), the linker may find that it doesn't know " +"where an identifier is defined. The linker will look for it in the object " +"files in the libraries; if it finds it, it will include all the code from " +"that object file." +msgstr "" + +#: ../Doc/extending/windows.rst:76 +msgid "" +"In Windows, there are two types of library, a static library and an import " +"library (both called :file:`.lib`). A static library is like a Unix :file:`." +"a` file; it contains code to be included as necessary. An import library is " +"basically used only to reassure the linker that a certain identifier is " +"legal, and will be present in the program when the DLL is loaded. So the " +"linker uses the information from the import library to build the lookup " +"table for using identifiers that are not included in the DLL. When an " +"application or a DLL is linked, an import library may be generated, which " +"will need to be used for all future DLLs that depend on the symbols in the " +"application or DLL." +msgstr "" + +#: ../Doc/extending/windows.rst:86 +msgid "" +"Suppose you are building two dynamic-load modules, B and C, which should " +"share another block of code A. On Unix, you would *not* pass :file:`A.a` to " +"the linker for :file:`B.so` and :file:`C.so`; that would cause it to be " +"included twice, so that B and C would each have their own copy. In Windows, " +"building :file:`A.dll` will also build :file:`A.lib`. You *do* pass :file:" +"`A.lib` to the linker for B and C. :file:`A.lib` does not contain code; it " +"just contains information which will be used at runtime to access A's code." +msgstr "" + +#: ../Doc/extending/windows.rst:94 +msgid "" +"In Windows, using an import library is sort of like using ``import spam``; " +"it gives you access to spam's names, but does not create a separate copy. " +"On Unix, linking with a library is more like ``from spam import *``; it does " +"create a separate copy." +msgstr "" + +#: ../Doc/extending/windows.rst:103 +msgid "Using DLLs in Practice" +msgstr "" + +#: ../Doc/extending/windows.rst:108 +msgid "" +"Windows Python is built in Microsoft Visual C++; using other compilers may " +"or may not work (though Borland seems to). The rest of this section is MSVC+" +"+ specific." +msgstr "" + +#: ../Doc/extending/windows.rst:112 +msgid "" +"When creating DLLs in Windows, you must pass :file:`pythonXY.lib` to the " +"linker. To build two DLLs, spam and ni (which uses C functions found in " +"spam), you could use these commands::" +msgstr "" + +#: ../Doc/extending/windows.rst:119 +msgid "" +"The first command created three files: :file:`spam.obj`, :file:`spam.dll` " +"and :file:`spam.lib`. :file:`Spam.dll` does not contain any Python " +"functions (such as :c:func:`PyArg_ParseTuple`), but it does know how to find " +"the Python code thanks to :file:`pythonXY.lib`." +msgstr "" + +#: ../Doc/extending/windows.rst:124 +msgid "" +"The second command created :file:`ni.dll` (and :file:`.obj` and :file:`." +"lib`), which knows how to find the necessary functions from spam, and also " +"from the Python executable." +msgstr "" + +#: ../Doc/extending/windows.rst:128 +msgid "" +"Not every identifier is exported to the lookup table. If you want any other " +"modules (including Python) to be able to see your identifiers, you have to " +"say ``_declspec(dllexport)``, as in ``void _declspec(dllexport) " +"initspam(void)`` or ``PyObject _declspec(dllexport) *NiGetSpamData(void)``." +msgstr "" + +#: ../Doc/extending/windows.rst:133 +msgid "" +"Developer Studio will throw in a lot of import libraries that you do not " +"really need, adding about 100K to your executable. To get rid of them, use " +"the Project Settings dialog, Link tab, to specify *ignore default " +"libraries*. Add the correct :file:`msvcrtxx.lib` to the list of libraries." +msgstr "" diff --git a/faq.po b/faq.po new file mode 100644 index 00000000..404a4e2d --- /dev/null +++ b/faq.po @@ -0,0 +1,5675 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/faq/design.rst:3 +msgid "Design and History FAQ" +msgstr "" + +#: ../Doc/faq/design.rst:6 +msgid "Why does Python use indentation for grouping of statements?" +msgstr "" + +#: ../Doc/faq/design.rst:8 +msgid "" +"Guido van Rossum believes that using indentation for grouping is extremely " +"elegant and contributes a lot to the clarity of the average Python program. " +"Most people learn to love this feature after a while." +msgstr "" + +#: ../Doc/faq/design.rst:12 +msgid "" +"Since there are no begin/end brackets there cannot be a disagreement between " +"grouping perceived by the parser and the human reader. Occasionally C " +"programmers will encounter a fragment of code like this::" +msgstr "" + +#: ../Doc/faq/design.rst:21 +msgid "" +"Only the ``x++`` statement is executed if the condition is true, but the " +"indentation leads you to believe otherwise. Even experienced C programmers " +"will sometimes stare at it a long time wondering why ``y`` is being " +"decremented even for ``x > y``." +msgstr "" + +#: ../Doc/faq/design.rst:26 +msgid "" +"Because there are no begin/end brackets, Python is much less prone to coding-" +"style conflicts. In C there are many different ways to place the braces. If " +"you're used to reading and writing code that uses one style, you will feel " +"at least slightly uneasy when reading (or being required to write) another " +"style." +msgstr "" + +#: ../Doc/faq/design.rst:31 +msgid "" +"Many coding styles place begin/end brackets on a line by themselves. This " +"makes programs considerably longer and wastes valuable screen space, making " +"it harder to get a good overview of a program. Ideally, a function should " +"fit on one screen (say, 20-30 lines). 20 lines of Python can do a lot more " +"work than 20 lines of C. This is not solely due to the lack of begin/end " +"brackets -- the lack of declarations and the high-level data types are also " +"responsible -- but the indentation-based syntax certainly helps." +msgstr "" + +#: ../Doc/faq/design.rst:41 +msgid "Why am I getting strange results with simple arithmetic operations?" +msgstr "" + +#: ../Doc/faq/design.rst:43 +msgid "See the next question." +msgstr "" + +#: ../Doc/faq/design.rst:47 +msgid "Why are floating-point calculations so inaccurate?" +msgstr "" + +#: ../Doc/faq/design.rst:49 +msgid "Users are often surprised by results like this::" +msgstr "" + +#: ../Doc/faq/design.rst:54 +msgid "" +"and think it is a bug in Python. It's not. This has little to do with " +"Python, and much more to do with how the underlying platform handles " +"floating-point numbers." +msgstr "" + +#: ../Doc/faq/design.rst:58 +msgid "" +"The :class:`float` type in CPython uses a C ``double`` for storage. A :" +"class:`float` object's value is stored in binary floating-point with a fixed " +"precision (typically 53 bits) and Python uses C operations, which in turn " +"rely on the hardware implementation in the processor, to perform floating-" +"point operations. This means that as far as floating-point operations are " +"concerned, Python behaves like many popular languages including C and Java." +msgstr "" + +#: ../Doc/faq/design.rst:65 +msgid "" +"Many numbers that can be written easily in decimal notation cannot be " +"expressed exactly in binary floating-point. For example, after::" +msgstr "" + +#: ../Doc/faq/design.rst:70 +msgid "" +"the value stored for ``x`` is a (very good) approximation to the decimal " +"value ``1.2``, but is not exactly equal to it. On a typical machine, the " +"actual stored value is::" +msgstr "" + +#: ../Doc/faq/design.rst:76 +msgid "which is exactly::" +msgstr "" + +#: ../Doc/faq/design.rst:80 +msgid "" +"The typical precision of 53 bits provides Python floats with 15-16 decimal " +"digits of accuracy." +msgstr "" + +#: ../Doc/faq/design.rst:83 +msgid "" +"For a fuller explanation, please see the :ref:`floating point arithmetic " +"` chapter in the Python tutorial." +msgstr "" + +#: ../Doc/faq/design.rst:88 +msgid "Why are Python strings immutable?" +msgstr "" + +#: ../Doc/faq/design.rst:90 +msgid "There are several advantages." +msgstr "" + +#: ../Doc/faq/design.rst:92 +msgid "" +"One is performance: knowing that a string is immutable means we can allocate " +"space for it at creation time, and the storage requirements are fixed and " +"unchanging. This is also one of the reasons for the distinction between " +"tuples and lists." +msgstr "" + +#: ../Doc/faq/design.rst:97 +msgid "" +"Another advantage is that strings in Python are considered as \"elemental\" " +"as numbers. No amount of activity will change the value 8 to anything else, " +"and in Python, no amount of activity will change the string \"eight\" to " +"anything else." +msgstr "" + +#: ../Doc/faq/design.rst:105 +msgid "Why must 'self' be used explicitly in method definitions and calls?" +msgstr "" + +#: ../Doc/faq/design.rst:107 +msgid "" +"The idea was borrowed from Modula-3. It turns out to be very useful, for a " +"variety of reasons." +msgstr "" + +#: ../Doc/faq/design.rst:110 +msgid "" +"First, it's more obvious that you are using a method or instance attribute " +"instead of a local variable. Reading ``self.x`` or ``self.meth()`` makes it " +"absolutely clear that an instance variable or method is used even if you " +"don't know the class definition by heart. In C++, you can sort of tell by " +"the lack of a local variable declaration (assuming globals are rare or " +"easily recognizable) -- but in Python, there are no local variable " +"declarations, so you'd have to look up the class definition to be sure. " +"Some C++ and Java coding standards call for instance attributes to have an " +"``m_`` prefix, so this explicitness is still useful in those languages, too." +msgstr "" + +#: ../Doc/faq/design.rst:120 +msgid "" +"Second, it means that no special syntax is necessary if you want to " +"explicitly reference or call the method from a particular class. In C++, if " +"you want to use a method from a base class which is overridden in a derived " +"class, you have to use the ``::`` operator -- in Python you can write " +"``baseclass.methodname(self, )``. This is particularly " +"useful for :meth:`__init__` methods, and in general in cases where a derived " +"class method wants to extend the base class method of the same name and thus " +"has to call the base class method somehow." +msgstr "" + +#: ../Doc/faq/design.rst:129 +msgid "" +"Finally, for instance variables it solves a syntactic problem with " +"assignment: since local variables in Python are (by definition!) those " +"variables to which a value is assigned in a function body (and that aren't " +"explicitly declared global), there has to be some way to tell the " +"interpreter that an assignment was meant to assign to an instance variable " +"instead of to a local variable, and it should preferably be syntactic (for " +"efficiency reasons). C++ does this through declarations, but Python doesn't " +"have declarations and it would be a pity having to introduce them just for " +"this purpose. Using the explicit ``self.var`` solves this nicely. " +"Similarly, for using instance variables, having to write ``self.var`` means " +"that references to unqualified names inside a method don't have to search " +"the instance's directories. To put it another way, local variables and " +"instance variables live in two different namespaces, and you need to tell " +"Python which namespace to use." +msgstr "" + +#: ../Doc/faq/design.rst:145 +msgid "Why can't I use an assignment in an expression?" +msgstr "" + +#: ../Doc/faq/design.rst:147 +msgid "" +"Many people used to C or Perl complain that they want to use this C idiom:" +msgstr "" + +#: ../Doc/faq/design.rst:155 +msgid "where in Python you're forced to write this::" +msgstr "" + +#: ../Doc/faq/design.rst:163 +msgid "" +"The reason for not allowing assignment in Python expressions is a common, " +"hard-to-find bug in those other languages, caused by this construct:" +msgstr "" + +#: ../Doc/faq/design.rst:175 +msgid "" +"The error is a simple typo: ``x = 0``, which assigns 0 to the variable " +"``x``, was written while the comparison ``x == 0`` is certainly what was " +"intended." +msgstr "" + +#: ../Doc/faq/design.rst:178 +msgid "" +"Many alternatives have been proposed. Most are hacks that save some typing " +"but use arbitrary or cryptic syntax or keywords, and fail the simple " +"criterion for language change proposals: it should intuitively suggest the " +"proper meaning to a human reader who has not yet been introduced to the " +"construct." +msgstr "" + +#: ../Doc/faq/design.rst:183 +msgid "" +"An interesting phenomenon is that most experienced Python programmers " +"recognize the ``while True`` idiom and don't seem to be missing the " +"assignment in expression construct much; it's only newcomers who express a " +"strong desire to add this to the language." +msgstr "" + +#: ../Doc/faq/design.rst:188 +msgid "" +"There's an alternative way of spelling this that seems attractive but is " +"generally less robust than the \"while True\" solution::" +msgstr "" + +#: ../Doc/faq/design.rst:196 +msgid "" +"The problem with this is that if you change your mind about exactly how you " +"get the next line (e.g. you want to change it into ``sys.stdin.readline()``) " +"you have to remember to change two places in your program -- the second " +"occurrence is hidden at the bottom of the loop." +msgstr "" + +#: ../Doc/faq/design.rst:201 +msgid "" +"The best approach is to use iterators, making it possible to loop through " +"objects using the ``for`` statement. For example, :term:`file objects ` support the iterator protocol, so you can write simply::" +msgstr "" + +#: ../Doc/faq/design.rst:211 +msgid "" +"Why does Python use methods for some functionality (e.g. list.index()) but " +"functions for other (e.g. len(list))?" +msgstr "" + +#: ../Doc/faq/design.rst:213 +msgid "" +"The major reason is history. Functions were used for those operations that " +"were generic for a group of types and which were intended to work even for " +"objects that didn't have methods at all (e.g. tuples). It is also " +"convenient to have a function that can readily be applied to an amorphous " +"collection of objects when you use the functional features of Python " +"(``map()``, ``zip()`` et al)." +msgstr "" + +#: ../Doc/faq/design.rst:219 +msgid "" +"In fact, implementing ``len()``, ``max()``, ``min()`` as a built-in function " +"is actually less code than implementing them as methods for each type. One " +"can quibble about individual cases but it's a part of Python, and it's too " +"late to make such fundamental changes now. The functions have to remain to " +"avoid massive code breakage." +msgstr "" + +#: ../Doc/faq/design.rst:229 +msgid "" +"For string operations, Python has moved from external functions (the " +"``string`` module) to methods. However, ``len()`` is still a function." +msgstr "" + +#: ../Doc/faq/design.rst:234 +msgid "Why is join() a string method instead of a list or tuple method?" +msgstr "" + +#: ../Doc/faq/design.rst:236 +msgid "" +"Strings became much more like other standard types starting in Python 1.6, " +"when methods were added which give the same functionality that has always " +"been available using the functions of the string module. Most of these new " +"methods have been widely accepted, but the one which appears to make some " +"programmers feel uncomfortable is::" +msgstr "" + +#: ../Doc/faq/design.rst:244 +msgid "which gives the result::" +msgstr "" + +#: ../Doc/faq/design.rst:248 +msgid "There are two common arguments against this usage." +msgstr "" + +#: ../Doc/faq/design.rst:250 +msgid "" +"The first runs along the lines of: \"It looks really ugly using a method of " +"a string literal (string constant)\", to which the answer is that it might, " +"but a string literal is just a fixed value. If the methods are to be allowed " +"on names bound to strings there is no logical reason to make them " +"unavailable on literals." +msgstr "" + +#: ../Doc/faq/design.rst:256 +msgid "" +"The second objection is typically cast as: \"I am really telling a sequence " +"to join its members together with a string constant\". Sadly, you aren't. " +"For some reason there seems to be much less difficulty with having :meth:" +"`~str.split` as a string method, since in that case it is easy to see that ::" +msgstr "" + +#: ../Doc/faq/design.rst:263 +msgid "" +"is an instruction to a string literal to return the substrings delimited by " +"the given separator (or, by default, arbitrary runs of white space)." +msgstr "" + +#: ../Doc/faq/design.rst:266 +msgid "" +":meth:`~str.join` is a string method because in using it you are telling the " +"separator string to iterate over a sequence of strings and insert itself " +"between adjacent elements. This method can be used with any argument which " +"obeys the rules for sequence objects, including any new classes you might " +"define yourself. Similar methods exist for bytes and bytearray objects." +msgstr "" + +#: ../Doc/faq/design.rst:274 +msgid "How fast are exceptions?" +msgstr "" + +#: ../Doc/faq/design.rst:276 +msgid "" +"A try/except block is extremely efficient if no exceptions are raised. " +"Actually catching an exception is expensive. In versions of Python prior to " +"2.0 it was common to use this idiom::" +msgstr "" + +#: ../Doc/faq/design.rst:286 +msgid "" +"This only made sense when you expected the dict to have the key almost all " +"the time. If that wasn't the case, you coded it like this::" +msgstr "" + +#: ../Doc/faq/design.rst:294 +msgid "" +"For this specific case, you could also use ``value = dict.setdefault(key, " +"getvalue(key))``, but only if the ``getvalue()`` call is cheap enough " +"because it is evaluated in all cases." +msgstr "" + +#: ../Doc/faq/design.rst:300 +msgid "Why isn't there a switch or case statement in Python?" +msgstr "" + +#: ../Doc/faq/design.rst:302 +msgid "" +"You can do this easily enough with a sequence of ``if... elif... elif... " +"else``. There have been some proposals for switch statement syntax, but " +"there is no consensus (yet) on whether and how to do range tests. See :pep:" +"`275` for complete details and the current status." +msgstr "" + +#: ../Doc/faq/design.rst:307 +msgid "" +"For cases where you need to choose from a very large number of " +"possibilities, you can create a dictionary mapping case values to functions " +"to call. For example::" +msgstr "" + +#: ../Doc/faq/design.rst:321 +msgid "" +"For calling methods on objects, you can simplify yet further by using the :" +"func:`getattr` built-in to retrieve methods with a particular name::" +msgstr "" + +#: ../Doc/faq/design.rst:333 +msgid "" +"It's suggested that you use a prefix for the method names, such as " +"``visit_`` in this example. Without such a prefix, if values are coming " +"from an untrusted source, an attacker would be able to call any method on " +"your object." +msgstr "" + +#: ../Doc/faq/design.rst:339 +msgid "" +"Can't you emulate threads in the interpreter instead of relying on an OS-" +"specific thread implementation?" +msgstr "" + +#: ../Doc/faq/design.rst:341 +msgid "" +"Answer 1: Unfortunately, the interpreter pushes at least one C stack frame " +"for each Python stack frame. Also, extensions can call back into Python at " +"almost random moments. Therefore, a complete threads implementation " +"requires thread support for C." +msgstr "" + +#: ../Doc/faq/design.rst:346 +msgid "" +"Answer 2: Fortunately, there is `Stackless Python `_, which has a completely redesigned interpreter loop that avoids the C " +"stack." +msgstr "" + +#: ../Doc/faq/design.rst:351 +msgid "Why can't lambda expressions contain statements?" +msgstr "" + +#: ../Doc/faq/design.rst:353 +msgid "" +"Python lambda expressions cannot contain statements because Python's " +"syntactic framework can't handle statements nested inside expressions. " +"However, in Python, this is not a serious problem. Unlike lambda forms in " +"other languages, where they add functionality, Python lambdas are only a " +"shorthand notation if you're too lazy to define a function." +msgstr "" + +#: ../Doc/faq/design.rst:359 +msgid "" +"Functions are already first class objects in Python, and can be declared in " +"a local scope. Therefore the only advantage of using a lambda instead of a " +"locally-defined function is that you don't need to invent a name for the " +"function -- but that's just a local variable to which the function object " +"(which is exactly the same type of object that a lambda expression yields) " +"is assigned!" +msgstr "" + +#: ../Doc/faq/design.rst:367 +msgid "Can Python be compiled to machine code, C or some other language?" +msgstr "" + +#: ../Doc/faq/design.rst:369 +msgid "Practical answer:" +msgstr "" + +#: ../Doc/faq/design.rst:371 +msgid "" +"`Cython `_ and `Pyrex `_ compile a modified version of Python with " +"optional annotations into C extensions. `Weave `_ makes it easy to intermingle Python and C " +"code in various ways to increase performance. `Nuitka `_ is an up-and-coming compiler of Python into C++ code, aiming to support " +"the full Python language." +msgstr "" + +#: ../Doc/faq/design.rst:378 +msgid "Theoretical answer:" +msgstr "" + +#: ../Doc/faq/design.rst:382 +msgid "" +"Not trivially. Python's high level data types, dynamic typing of objects " +"and run-time invocation of the interpreter (using :func:`eval` or :func:" +"`exec`) together mean that a naïvely \"compiled\" Python program would " +"probably consist mostly of calls into the Python run-time system, even for " +"seemingly simple operations like ``x+1``." +msgstr "" + +#: ../Doc/faq/design.rst:388 +msgid "" +"Several projects described in the Python newsgroup or at past `Python " +"conferences `_ have shown that " +"this approach is feasible, although the speedups reached so far are only " +"modest (e.g. 2x). Jython uses the same strategy for compiling to Java " +"bytecode. (Jim Hugunin has demonstrated that in combination with whole-" +"program analysis, speedups of 1000x are feasible for small demo programs. " +"See the proceedings from the `1997 Python conference `_ for more information.)" +msgstr "" + +#: ../Doc/faq/design.rst:399 +msgid "How does Python manage memory?" +msgstr "" + +#: ../Doc/faq/design.rst:401 +msgid "" +"The details of Python memory management depend on the implementation. The " +"standard implementation of Python, :term:`CPython`, uses reference counting " +"to detect inaccessible objects, and another mechanism to collect reference " +"cycles, periodically executing a cycle detection algorithm which looks for " +"inaccessible cycles and deletes the objects involved. The :mod:`gc` module " +"provides functions to perform a garbage collection, obtain debugging " +"statistics, and tune the collector's parameters." +msgstr "" + +#: ../Doc/faq/design.rst:409 +msgid "" +"Other implementations (such as `Jython `_ or `PyPy " +"`_), however, can rely on a different mechanism such as " +"a full-blown garbage collector. This difference can cause some subtle " +"porting problems if your Python code depends on the behavior of the " +"reference counting implementation." +msgstr "" + +#: ../Doc/faq/design.rst:415 +msgid "" +"In some Python implementations, the following code (which is fine in " +"CPython) will probably run out of file descriptors::" +msgstr "" + +#: ../Doc/faq/design.rst:422 +msgid "" +"Indeed, using CPython's reference counting and destructor scheme, each new " +"assignment to *f* closes the previous file. With a traditional GC, however, " +"those file objects will only get collected (and closed) at varying and " +"possibly long intervals." +msgstr "" + +#: ../Doc/faq/design.rst:427 +msgid "" +"If you want to write code that will work with any Python implementation, you " +"should explicitly close the file or use the :keyword:`with` statement; this " +"will work regardless of memory management scheme::" +msgstr "" + +#: ../Doc/faq/design.rst:437 +msgid "Why doesn't CPython use a more traditional garbage collection scheme?" +msgstr "" + +#: ../Doc/faq/design.rst:439 +msgid "" +"For one thing, this is not a C standard feature and hence it's not portable. " +"(Yes, we know about the Boehm GC library. It has bits of assembler code for " +"*most* common platforms, not for all of them, and although it is mostly " +"transparent, it isn't completely transparent; patches are required to get " +"Python to work with it.)" +msgstr "" + +#: ../Doc/faq/design.rst:445 +msgid "" +"Traditional GC also becomes a problem when Python is embedded into other " +"applications. While in a standalone Python it's fine to replace the " +"standard malloc() and free() with versions provided by the GC library, an " +"application embedding Python may want to have its *own* substitute for " +"malloc() and free(), and may not want Python's. Right now, CPython works " +"with anything that implements malloc() and free() properly." +msgstr "" + +#: ../Doc/faq/design.rst:454 +msgid "Why isn't all memory freed when CPython exits?" +msgstr "" + +#: ../Doc/faq/design.rst:456 +msgid "" +"Objects referenced from the global namespaces of Python modules are not " +"always deallocated when Python exits. This may happen if there are circular " +"references. There are also certain bits of memory that are allocated by the " +"C library that are impossible to free (e.g. a tool like Purify will complain " +"about these). Python is, however, aggressive about cleaning up memory on " +"exit and does try to destroy every single object." +msgstr "" + +#: ../Doc/faq/design.rst:463 +msgid "" +"If you want to force Python to delete certain things on deallocation use " +"the :mod:`atexit` module to run a function that will force those deletions." +msgstr "" + +#: ../Doc/faq/design.rst:468 +msgid "Why are there separate tuple and list data types?" +msgstr "" + +#: ../Doc/faq/design.rst:470 +msgid "" +"Lists and tuples, while similar in many respects, are generally used in " +"fundamentally different ways. Tuples can be thought of as being similar to " +"Pascal records or C structs; they're small collections of related data which " +"may be of different types which are operated on as a group. For example, a " +"Cartesian coordinate is appropriately represented as a tuple of two or three " +"numbers." +msgstr "" + +#: ../Doc/faq/design.rst:477 +msgid "" +"Lists, on the other hand, are more like arrays in other languages. They " +"tend to hold a varying number of objects all of which have the same type and " +"which are operated on one-by-one. For example, ``os.listdir('.')`` returns " +"a list of strings representing the files in the current directory. " +"Functions which operate on this output would generally not break if you " +"added another file or two to the directory." +msgstr "" + +#: ../Doc/faq/design.rst:484 +msgid "" +"Tuples are immutable, meaning that once a tuple has been created, you can't " +"replace any of its elements with a new value. Lists are mutable, meaning " +"that you can always change a list's elements. Only immutable elements can " +"be used as dictionary keys, and hence only tuples and not lists can be used " +"as keys." +msgstr "" + +#: ../Doc/faq/design.rst:491 +msgid "How are lists implemented?" +msgstr "" + +#: ../Doc/faq/design.rst:493 +msgid "" +"Python's lists are really variable-length arrays, not Lisp-style linked " +"lists. The implementation uses a contiguous array of references to other " +"objects, and keeps a pointer to this array and the array's length in a list " +"head structure." +msgstr "" + +#: ../Doc/faq/design.rst:497 +msgid "" +"This makes indexing a list ``a[i]`` an operation whose cost is independent " +"of the size of the list or the value of the index." +msgstr "" + +#: ../Doc/faq/design.rst:500 +msgid "" +"When items are appended or inserted, the array of references is resized. " +"Some cleverness is applied to improve the performance of appending items " +"repeatedly; when the array must be grown, some extra space is allocated so " +"the next few times don't require an actual resize." +msgstr "" + +#: ../Doc/faq/design.rst:507 +msgid "How are dictionaries implemented?" +msgstr "" + +#: ../Doc/faq/design.rst:509 +msgid "" +"Python's dictionaries are implemented as resizable hash tables. Compared to " +"B-trees, this gives better performance for lookup (the most common operation " +"by far) under most circumstances, and the implementation is simpler." +msgstr "" + +#: ../Doc/faq/design.rst:513 +msgid "" +"Dictionaries work by computing a hash code for each key stored in the " +"dictionary using the :func:`hash` built-in function. The hash code varies " +"widely depending on the key and a per-process seed; for example, \"Python\" " +"could hash to -539294296 while \"python\", a string that differs by a single " +"bit, could hash to 1142331976. The hash code is then used to calculate a " +"location in an internal array where the value will be stored. Assuming that " +"you're storing keys that all have different hash values, this means that " +"dictionaries take constant time -- O(1), in computer science notation -- to " +"retrieve a key. It also means that no sorted order of the keys is " +"maintained, and traversing the array as the ``.keys()`` and ``.items()`` do " +"will output the dictionary's content in some arbitrary jumbled order that " +"can change with every invocation of a program." +msgstr "" + +#: ../Doc/faq/design.rst:528 +msgid "Why must dictionary keys be immutable?" +msgstr "" + +#: ../Doc/faq/design.rst:530 +msgid "" +"The hash table implementation of dictionaries uses a hash value calculated " +"from the key value to find the key. If the key were a mutable object, its " +"value could change, and thus its hash could also change. But since whoever " +"changes the key object can't tell that it was being used as a dictionary " +"key, it can't move the entry around in the dictionary. Then, when you try " +"to look up the same object in the dictionary it won't be found because its " +"hash value is different. If you tried to look up the old value it wouldn't " +"be found either, because the value of the object found in that hash bin " +"would be different." +msgstr "" + +#: ../Doc/faq/design.rst:539 +msgid "" +"If you want a dictionary indexed with a list, simply convert the list to a " +"tuple first; the function ``tuple(L)`` creates a tuple with the same entries " +"as the list ``L``. Tuples are immutable and can therefore be used as " +"dictionary keys." +msgstr "" + +#: ../Doc/faq/design.rst:543 +msgid "Some unacceptable solutions that have been proposed:" +msgstr "" + +#: ../Doc/faq/design.rst:545 +msgid "" +"Hash lists by their address (object ID). This doesn't work because if you " +"construct a new list with the same value it won't be found; e.g.::" +msgstr "" + +#: ../Doc/faq/design.rst:551 +msgid "" +"would raise a KeyError exception because the id of the ``[1, 2]`` used in " +"the second line differs from that in the first line. In other words, " +"dictionary keys should be compared using ``==``, not using :keyword:`is`." +msgstr "" + +#: ../Doc/faq/design.rst:555 +msgid "" +"Make a copy when using a list as a key. This doesn't work because the list, " +"being a mutable object, could contain a reference to itself, and then the " +"copying code would run into an infinite loop." +msgstr "" + +#: ../Doc/faq/design.rst:559 +msgid "" +"Allow lists as keys but tell the user not to modify them. This would allow " +"a class of hard-to-track bugs in programs when you forgot or modified a list " +"by accident. It also invalidates an important invariant of dictionaries: " +"every value in ``d.keys()`` is usable as a key of the dictionary." +msgstr "" + +#: ../Doc/faq/design.rst:564 +msgid "" +"Mark lists as read-only once they are used as a dictionary key. The problem " +"is that it's not just the top-level object that could change its value; you " +"could use a tuple containing a list as a key. Entering anything as a key " +"into a dictionary would require marking all objects reachable from there as " +"read-only -- and again, self-referential objects could cause an infinite " +"loop." +msgstr "" + +#: ../Doc/faq/design.rst:570 +msgid "" +"There is a trick to get around this if you need to, but use it at your own " +"risk: You can wrap a mutable structure inside a class instance which has " +"both a :meth:`__eq__` and a :meth:`__hash__` method. You must then make " +"sure that the hash value for all such wrapper objects that reside in a " +"dictionary (or other hash based structure), remain fixed while the object is " +"in the dictionary (or other structure). ::" +msgstr "" + +#: ../Doc/faq/design.rst:594 +msgid "" +"Note that the hash computation is complicated by the possibility that some " +"members of the list may be unhashable and also by the possibility of " +"arithmetic overflow." +msgstr "" + +#: ../Doc/faq/design.rst:598 +msgid "" +"Furthermore it must always be the case that if ``o1 == o2`` (ie ``o1." +"__eq__(o2) is True``) then ``hash(o1) == hash(o2)`` (ie, ``o1.__hash__() == " +"o2.__hash__()``), regardless of whether the object is in a dictionary or " +"not. If you fail to meet these restrictions dictionaries and other hash " +"based structures will misbehave." +msgstr "" + +#: ../Doc/faq/design.rst:603 +msgid "" +"In the case of ListWrapper, whenever the wrapper object is in a dictionary " +"the wrapped list must not change to avoid anomalies. Don't do this unless " +"you are prepared to think hard about the requirements and the consequences " +"of not meeting them correctly. Consider yourself warned." +msgstr "" + +#: ../Doc/faq/design.rst:610 +msgid "Why doesn't list.sort() return the sorted list?" +msgstr "" + +#: ../Doc/faq/design.rst:612 +msgid "" +"In situations where performance matters, making a copy of the list just to " +"sort it would be wasteful. Therefore, :meth:`list.sort` sorts the list in " +"place. In order to remind you of that fact, it does not return the sorted " +"list. This way, you won't be fooled into accidentally overwriting a list " +"when you need a sorted copy but also need to keep the unsorted version " +"around." +msgstr "" + +#: ../Doc/faq/design.rst:618 +msgid "" +"If you want to return a new list, use the built-in :func:`sorted` function " +"instead. This function creates a new list from a provided iterable, sorts " +"it and returns it. For example, here's how to iterate over the keys of a " +"dictionary in sorted order::" +msgstr "" + +#: ../Doc/faq/design.rst:628 +msgid "How do you specify and enforce an interface spec in Python?" +msgstr "" + +#: ../Doc/faq/design.rst:630 +msgid "" +"An interface specification for a module as provided by languages such as C++ " +"and Java describes the prototypes for the methods and functions of the " +"module. Many feel that compile-time enforcement of interface specifications " +"helps in the construction of large programs." +msgstr "" + +#: ../Doc/faq/design.rst:635 +msgid "" +"Python 2.6 adds an :mod:`abc` module that lets you define Abstract Base " +"Classes (ABCs). You can then use :func:`isinstance` and :func:`issubclass` " +"to check whether an instance or a class implements a particular ABC. The :" +"mod:`collections.abc` module defines a set of useful ABCs such as :class:" +"`~collections.abc.Iterable`, :class:`~collections.abc.Container`, and :class:" +"`~collections.abc.MutableMapping`." +msgstr "" + +#: ../Doc/faq/design.rst:642 +msgid "" +"For Python, many of the advantages of interface specifications can be " +"obtained by an appropriate test discipline for components. There is also a " +"tool, PyChecker, which can be used to find problems due to subclassing." +msgstr "" + +#: ../Doc/faq/design.rst:646 +msgid "" +"A good test suite for a module can both provide a regression test and serve " +"as a module interface specification and a set of examples. Many Python " +"modules can be run as a script to provide a simple \"self test.\" Even " +"modules which use complex external interfaces can often be tested in " +"isolation using trivial \"stub\" emulations of the external interface. The :" +"mod:`doctest` and :mod:`unittest` modules or third-party test frameworks can " +"be used to construct exhaustive test suites that exercise every line of code " +"in a module." +msgstr "" + +#: ../Doc/faq/design.rst:654 +msgid "" +"An appropriate testing discipline can help build large complex applications " +"in Python as well as having interface specifications would. In fact, it can " +"be better because an interface specification cannot test certain properties " +"of a program. For example, the :meth:`append` method is expected to add new " +"elements to the end of some internal list; an interface specification cannot " +"test that your :meth:`append` implementation will actually do this " +"correctly, but it's trivial to check this property in a test suite." +msgstr "" + +#: ../Doc/faq/design.rst:662 +msgid "" +"Writing test suites is very helpful, and you might want to design your code " +"with an eye to making it easily tested. One increasingly popular technique, " +"test-directed development, calls for writing parts of the test suite first, " +"before you write any of the actual code. Of course Python allows you to be " +"sloppy and not write test cases at all." +msgstr "" + +#: ../Doc/faq/design.rst:670 +msgid "Why is there no goto?" +msgstr "" + +#: ../Doc/faq/design.rst:672 +msgid "" +"You can use exceptions to provide a \"structured goto\" that even works " +"across function calls. Many feel that exceptions can conveniently emulate " +"all reasonable uses of the \"go\" or \"goto\" constructs of C, Fortran, and " +"other languages. For example::" +msgstr "" + +#: ../Doc/faq/design.rst:687 +msgid "" +"This doesn't allow you to jump into the middle of a loop, but that's usually " +"considered an abuse of goto anyway. Use sparingly." +msgstr "" + +#: ../Doc/faq/design.rst:692 +msgid "Why can't raw strings (r-strings) end with a backslash?" +msgstr "" + +#: ../Doc/faq/design.rst:694 +msgid "" +"More precisely, they can't end with an odd number of backslashes: the " +"unpaired backslash at the end escapes the closing quote character, leaving " +"an unterminated string." +msgstr "" + +#: ../Doc/faq/design.rst:698 +msgid "" +"Raw strings were designed to ease creating input for processors (chiefly " +"regular expression engines) that want to do their own backslash escape " +"processing. Such processors consider an unmatched trailing backslash to be " +"an error anyway, so raw strings disallow that. In return, they allow you to " +"pass on the string quote character by escaping it with a backslash. These " +"rules work well when r-strings are used for their intended purpose." +msgstr "" + +#: ../Doc/faq/design.rst:705 +msgid "" +"If you're trying to build Windows pathnames, note that all Windows system " +"calls accept forward slashes too::" +msgstr "" + +#: ../Doc/faq/design.rst:710 +msgid "" +"If you're trying to build a pathname for a DOS command, try e.g. one of ::" +msgstr "" + +#: ../Doc/faq/design.rst:718 +msgid "Why doesn't Python have a \"with\" statement for attribute assignments?" +msgstr "" + +#: ../Doc/faq/design.rst:720 +msgid "" +"Python has a 'with' statement that wraps the execution of a block, calling " +"code on the entrance and exit from the block. Some language have a " +"construct that looks like this::" +msgstr "" + +#: ../Doc/faq/design.rst:728 +msgid "In Python, such a construct would be ambiguous." +msgstr "" + +#: ../Doc/faq/design.rst:730 +msgid "" +"Other languages, such as Object Pascal, Delphi, and C++, use static types, " +"so it's possible to know, in an unambiguous way, what member is being " +"assigned to. This is the main point of static typing -- the compiler " +"*always* knows the scope of every variable at compile time." +msgstr "" + +#: ../Doc/faq/design.rst:735 +msgid "" +"Python uses dynamic types. It is impossible to know in advance which " +"attribute will be referenced at runtime. Member attributes may be added or " +"removed from objects on the fly. This makes it impossible to know, from a " +"simple reading, what attribute is being referenced: a local one, a global " +"one, or a member attribute?" +msgstr "" + +#: ../Doc/faq/design.rst:741 +msgid "For instance, take the following incomplete snippet::" +msgstr "" + +#: ../Doc/faq/design.rst:747 +msgid "" +"The snippet assumes that \"a\" must have a member attribute called \"x\". " +"However, there is nothing in Python that tells the interpreter this. What " +"should happen if \"a\" is, let us say, an integer? If there is a global " +"variable named \"x\", will it be used inside the with block? As you see, " +"the dynamic nature of Python makes such choices much harder." +msgstr "" + +#: ../Doc/faq/design.rst:753 +msgid "" +"The primary benefit of \"with\" and similar language features (reduction of " +"code volume) can, however, easily be achieved in Python by assignment. " +"Instead of::" +msgstr "" + +#: ../Doc/faq/design.rst:760 +msgid "write this::" +msgstr "" + +#: ../Doc/faq/design.rst:767 +msgid "" +"This also has the side-effect of increasing execution speed because name " +"bindings are resolved at run-time in Python, and the second version only " +"needs to perform the resolution once." +msgstr "" + +#: ../Doc/faq/design.rst:773 +msgid "Why are colons required for the if/while/def/class statements?" +msgstr "" + +#: ../Doc/faq/design.rst:775 +msgid "" +"The colon is required primarily to enhance readability (one of the results " +"of the experimental ABC language). Consider this::" +msgstr "" + +#: ../Doc/faq/design.rst:781 +msgid "versus ::" +msgstr "" + +#: ../Doc/faq/design.rst:786 +msgid "" +"Notice how the second one is slightly easier to read. Notice further how a " +"colon sets off the example in this FAQ answer; it's a standard usage in " +"English." +msgstr "" + +#: ../Doc/faq/design.rst:789 +msgid "" +"Another minor reason is that the colon makes it easier for editors with " +"syntax highlighting; they can look for colons to decide when indentation " +"needs to be increased instead of having to do a more elaborate parsing of " +"the program text." +msgstr "" + +#: ../Doc/faq/design.rst:795 +msgid "Why does Python allow commas at the end of lists and tuples?" +msgstr "" + +#: ../Doc/faq/design.rst:797 +msgid "" +"Python lets you add a trailing comma at the end of lists, tuples, and " +"dictionaries::" +msgstr "" + +#: ../Doc/faq/design.rst:808 +msgid "There are several reasons to allow this." +msgstr "" + +#: ../Doc/faq/design.rst:810 +msgid "" +"When you have a literal value for a list, tuple, or dictionary spread across " +"multiple lines, it's easier to add more elements because you don't have to " +"remember to add a comma to the previous line. The lines can also be " +"reordered without creating a syntax error." +msgstr "" + +#: ../Doc/faq/design.rst:815 +msgid "" +"Accidentally omitting the comma can lead to errors that are hard to " +"diagnose. For example::" +msgstr "" + +#: ../Doc/faq/design.rst:825 +msgid "" +"This list looks like it has four elements, but it actually contains three: " +"\"fee\", \"fiefoo\" and \"fum\". Always adding the comma avoids this source " +"of error." +msgstr "" + +#: ../Doc/faq/design.rst:828 +msgid "" +"Allowing the trailing comma may also make programmatic code generation " +"easier." +msgstr "" + +#: ../Doc/faq/extending.rst:3 +msgid "Extending/Embedding FAQ" +msgstr "" + +#: ../Doc/faq/extending.rst:16 +msgid "Can I create my own functions in C?" +msgstr "" + +#: ../Doc/faq/extending.rst:18 +msgid "" +"Yes, you can create built-in modules containing functions, variables, " +"exceptions and even new types in C. This is explained in the document :ref:" +"`extending-index`." +msgstr "" + +#: ../Doc/faq/extending.rst:22 +msgid "Most intermediate or advanced Python books will also cover this topic." +msgstr "" + +#: ../Doc/faq/extending.rst:26 +msgid "Can I create my own functions in C++?" +msgstr "" + +#: ../Doc/faq/extending.rst:28 +msgid "" +"Yes, using the C compatibility features found in C++. Place ``extern \"C" +"\" { ... }`` around the Python include files and put ``extern \"C\"`` before " +"each function that is going to be called by the Python interpreter. Global " +"or static C++ objects with constructors are probably not a good idea." +msgstr "" + +#: ../Doc/faq/extending.rst:37 +msgid "Writing C is hard; are there any alternatives?" +msgstr "" + +#: ../Doc/faq/extending.rst:39 +msgid "" +"There are a number of alternatives to writing your own C extensions, " +"depending on what you're trying to do." +msgstr "" + +#: ../Doc/faq/extending.rst:44 +msgid "" +"`Cython `_ and its relative `Pyrex `_ are compilers that accept a " +"slightly modified form of Python and generate the corresponding C code. " +"Cython and Pyrex make it possible to write an extension without having to " +"learn Python's C API." +msgstr "" + +#: ../Doc/faq/extending.rst:50 +msgid "" +"If you need to interface to some C or C++ library for which no Python " +"extension currently exists, you can try wrapping the library's data types " +"and functions with a tool such as `SWIG `_. `SIP " +"`__, `CXX `_ `Boost `_, or `Weave `_ " +"are also alternatives for wrapping C++ libraries." +msgstr "" + +#: ../Doc/faq/extending.rst:61 +msgid "How can I execute arbitrary Python statements from C?" +msgstr "" + +#: ../Doc/faq/extending.rst:63 +msgid "" +"The highest-level function to do this is :c:func:`PyRun_SimpleString` which " +"takes a single string argument to be executed in the context of the module " +"``__main__`` and returns 0 for success and -1 when an exception occurred " +"(including ``SyntaxError``). If you want more control, use :c:func:" +"`PyRun_String`; see the source for :c:func:`PyRun_SimpleString` in ``Python/" +"pythonrun.c``." +msgstr "" + +#: ../Doc/faq/extending.rst:72 +msgid "How can I evaluate an arbitrary Python expression from C?" +msgstr "" + +#: ../Doc/faq/extending.rst:74 +msgid "" +"Call the function :c:func:`PyRun_String` from the previous question with the " +"start symbol :c:data:`Py_eval_input`; it parses an expression, evaluates it " +"and returns its value." +msgstr "" + +#: ../Doc/faq/extending.rst:80 +msgid "How do I extract C values from a Python object?" +msgstr "" + +#: ../Doc/faq/extending.rst:82 +msgid "" +"That depends on the object's type. If it's a tuple, :c:func:`PyTuple_Size` " +"returns its length and :c:func:`PyTuple_GetItem` returns the item at a " +"specified index. Lists have similar functions, :c:func:`PyListSize` and :c:" +"func:`PyList_GetItem`." +msgstr "" + +#: ../Doc/faq/extending.rst:87 +msgid "" +"For bytes, :c:func:`PyBytes_Size` returns its length and :c:func:" +"`PyBytes_AsStringAndSize` provides a pointer to its value and its length. " +"Note that Python bytes objects may contain null bytes so C's :c:func:" +"`strlen` should not be used." +msgstr "" + +#: ../Doc/faq/extending.rst:92 +msgid "" +"To test the type of an object, first make sure it isn't *NULL*, and then " +"use :c:func:`PyBytes_Check`, :c:func:`PyTuple_Check`, :c:func:" +"`PyList_Check`, etc." +msgstr "" + +#: ../Doc/faq/extending.rst:95 +msgid "" +"There is also a high-level API to Python objects which is provided by the so-" +"called 'abstract' interface -- read ``Include/abstract.h`` for further " +"details. It allows interfacing with any kind of Python sequence using calls " +"like :c:func:`PySequence_Length`, :c:func:`PySequence_GetItem`, etc. as well " +"as many other useful protocols such as numbers (:c:func:`PyNumber_Index` et " +"al.) and mappings in the PyMapping APIs." +msgstr "" + +#: ../Doc/faq/extending.rst:104 +msgid "How do I use Py_BuildValue() to create a tuple of arbitrary length?" +msgstr "" + +#: ../Doc/faq/extending.rst:106 +msgid "You can't. Use :c:func:`PyTuple_Pack` instead." +msgstr "" + +#: ../Doc/faq/extending.rst:110 +msgid "How do I call an object's method from C?" +msgstr "" + +#: ../Doc/faq/extending.rst:112 +msgid "" +"The :c:func:`PyObject_CallMethod` function can be used to call an arbitrary " +"method of an object. The parameters are the object, the name of the method " +"to call, a format string like that used with :c:func:`Py_BuildValue`, and " +"the argument values::" +msgstr "" + +#: ../Doc/faq/extending.rst:121 +msgid "" +"This works for any object that has methods -- whether built-in or user-" +"defined. You are responsible for eventually :c:func:`Py_DECREF`\\ 'ing the " +"return value." +msgstr "" + +#: ../Doc/faq/extending.rst:124 +msgid "" +"To call, e.g., a file object's \"seek\" method with arguments 10, 0 " +"(assuming the file object pointer is \"f\")::" +msgstr "" + +#: ../Doc/faq/extending.rst:135 +msgid "" +"Note that since :c:func:`PyObject_CallObject` *always* wants a tuple for the " +"argument list, to call a function without arguments, pass \"()\" for the " +"format, and to call a function with one argument, surround the argument in " +"parentheses, e.g. \"(i)\"." +msgstr "" + +#: ../Doc/faq/extending.rst:142 +msgid "" +"How do I catch the output from PyErr_Print() (or anything that prints to " +"stdout/stderr)?" +msgstr "" + +#: ../Doc/faq/extending.rst:144 +msgid "" +"In Python code, define an object that supports the ``write()`` method. " +"Assign this object to :data:`sys.stdout` and :data:`sys.stderr`. Call " +"print_error, or just allow the standard traceback mechanism to work. Then, " +"the output will go wherever your ``write()`` method sends it." +msgstr "" + +#: ../Doc/faq/extending.rst:149 +msgid "The easiest way to do this is to use the :class:`io.StringIO` class:" +msgstr "" + +#: ../Doc/faq/extending.rst:161 +msgid "A custom object to do the same would look like this:" +msgstr "" + +#: ../Doc/faq/extending.rst:182 +msgid "How do I access a module written in Python from C?" +msgstr "" + +#: ../Doc/faq/extending.rst:184 +msgid "You can get a pointer to the module object as follows::" +msgstr "" + +#: ../Doc/faq/extending.rst:188 +msgid "" +"If the module hasn't been imported yet (i.e. it is not yet present in :data:" +"`sys.modules`), this initializes the module; otherwise it simply returns the " +"value of ``sys.modules[\"\"]``. Note that it doesn't enter the " +"module into any namespace -- it only ensures it has been initialized and is " +"stored in :data:`sys.modules`." +msgstr "" + +#: ../Doc/faq/extending.rst:194 +msgid "" +"You can then access the module's attributes (i.e. any name defined in the " +"module) as follows::" +msgstr "" + +#: ../Doc/faq/extending.rst:199 +msgid "" +"Calling :c:func:`PyObject_SetAttrString` to assign to variables in the " +"module also works." +msgstr "" + +#: ../Doc/faq/extending.rst:204 +msgid "How do I interface to C++ objects from Python?" +msgstr "" + +#: ../Doc/faq/extending.rst:206 +msgid "" +"Depending on your requirements, there are many approaches. To do this " +"manually, begin by reading :ref:`the \"Extending and Embedding\" document " +"`. Realize that for the Python run-time system, there " +"isn't a whole lot of difference between C and C++ -- so the strategy of " +"building a new Python type around a C structure (pointer) type will also " +"work for C++ objects." +msgstr "" + +#: ../Doc/faq/extending.rst:212 +msgid "For C++ libraries, see :ref:`c-wrapper-software`." +msgstr "" + +#: ../Doc/faq/extending.rst:216 +msgid "I added a module using the Setup file and the make fails; why?" +msgstr "" + +#: ../Doc/faq/extending.rst:218 +msgid "" +"Setup must end in a newline, if there is no newline there, the build process " +"fails. (Fixing this requires some ugly shell script hackery, and this bug " +"is so minor that it doesn't seem worth the effort.)" +msgstr "" + +#: ../Doc/faq/extending.rst:224 +msgid "How do I debug an extension?" +msgstr "" + +#: ../Doc/faq/extending.rst:226 +msgid "" +"When using GDB with dynamically loaded extensions, you can't set a " +"breakpoint in your extension until your extension is loaded." +msgstr "" + +#: ../Doc/faq/extending.rst:229 +msgid "In your ``.gdbinit`` file (or interactively), add the command:" +msgstr "" + +#: ../Doc/faq/extending.rst:235 +msgid "Then, when you run GDB:" +msgstr "" + +#: ../Doc/faq/extending.rst:247 +msgid "" +"I want to compile a Python module on my Linux system, but some files are " +"missing. Why?" +msgstr "" + +#: ../Doc/faq/extending.rst:249 +msgid "" +"Most packaged versions of Python don't include the :file:`/usr/lib/python2." +"{x}/config/` directory, which contains various files required for compiling " +"Python extensions." +msgstr "" + +#: ../Doc/faq/extending.rst:253 +msgid "For Red Hat, install the python-devel RPM to get the necessary files." +msgstr "" + +#: ../Doc/faq/extending.rst:255 +msgid "For Debian, run ``apt-get install python-dev``." +msgstr "" + +#: ../Doc/faq/extending.rst:259 +msgid "How do I tell \"incomplete input\" from \"invalid input\"?" +msgstr "" + +#: ../Doc/faq/extending.rst:261 +msgid "" +"Sometimes you want to emulate the Python interactive interpreter's behavior, " +"where it gives you a continuation prompt when the input is incomplete (e.g. " +"you typed the start of an \"if\" statement or you didn't close your " +"parentheses or triple string quotes), but it gives you a syntax error " +"message immediately when the input is invalid." +msgstr "" + +#: ../Doc/faq/extending.rst:267 +msgid "" +"In Python you can use the :mod:`codeop` module, which approximates the " +"parser's behavior sufficiently. IDLE uses this, for example." +msgstr "" + +#: ../Doc/faq/extending.rst:270 +msgid "" +"The easiest way to do it in C is to call :c:func:`PyRun_InteractiveLoop` " +"(perhaps in a separate thread) and let the Python interpreter handle the " +"input for you. You can also set the :c:func:`PyOS_ReadlineFunctionPointer` " +"to point at your custom input function. See ``Modules/readline.c`` and " +"``Parser/myreadline.c`` for more hints." +msgstr "" + +#: ../Doc/faq/extending.rst:276 +msgid "" +"However sometimes you have to run the embedded Python interpreter in the " +"same thread as your rest application and you can't allow the :c:func:" +"`PyRun_InteractiveLoop` to stop while waiting for user input. The one " +"solution then is to call :c:func:`PyParser_ParseString` and test for ``e." +"error`` equal to ``E_EOF``, which means the input is incomplete). Here's a " +"sample code fragment, untested, inspired by code from Alex Farber::" +msgstr "" + +#: ../Doc/faq/extending.rst:309 +msgid "" +"Another solution is trying to compile the received string with :c:func:" +"`Py_CompileString`. If it compiles without errors, try to execute the " +"returned code object by calling :c:func:`PyEval_EvalCode`. Otherwise save " +"the input for later. If the compilation fails, find out if it's an error or " +"just more input is required - by extracting the message string from the " +"exception tuple and comparing it to the string \"unexpected EOF while parsing" +"\". Here is a complete example using the GNU readline library (you may want " +"to ignore **SIGINT** while calling readline())::" +msgstr "" + +#: ../Doc/faq/extending.rst:430 +msgid "How do I find undefined g++ symbols __builtin_new or __pure_virtual?" +msgstr "" + +#: ../Doc/faq/extending.rst:432 +msgid "" +"To dynamically load g++ extension modules, you must recompile Python, relink " +"it using g++ (change LINKCC in the Python Modules Makefile), and link your " +"extension module using g++ (e.g., ``g++ -shared -o mymodule.so mymodule.o``)." +msgstr "" + +#: ../Doc/faq/extending.rst:438 +msgid "" +"Can I create an object class with some methods implemented in C and others " +"in Python (e.g. through inheritance)?" +msgstr "" + +#: ../Doc/faq/extending.rst:440 +msgid "" +"Yes, you can inherit from built-in classes such as :class:`int`, :class:" +"`list`, :class:`dict`, etc." +msgstr "" + +#: ../Doc/faq/extending.rst:443 +msgid "" +"The Boost Python Library (BPL, http://www.boost.org/libs/python/doc/index." +"html) provides a way of doing this from C++ (i.e. you can inherit from an " +"extension class written in C++ using the BPL)." +msgstr "" + +#: ../Doc/faq/general.rst:5 +msgid "General Python FAQ" +msgstr "" + +#: ../Doc/faq/general.rst:13 +msgid "General Information" +msgstr "" + +#: ../Doc/faq/general.rst:16 ../Doc/faq/installed.rst:6 +msgid "What is Python?" +msgstr "" + +#: ../Doc/faq/general.rst:18 +msgid "" +"Python is an interpreted, interactive, object-oriented programming " +"language. It incorporates modules, exceptions, dynamic typing, very high " +"level dynamic data types, and classes. Python combines remarkable power " +"with very clear syntax. It has interfaces to many system calls and " +"libraries, as well as to various window systems, and is extensible in C or C+" +"+. It is also usable as an extension language for applications that need a " +"programmable interface. Finally, Python is portable: it runs on many Unix " +"variants, on the Mac, and on Windows 2000 and later." +msgstr "" + +#: ../Doc/faq/general.rst:27 +msgid "" +"To find out more, start with :ref:`tutorial-index`. The `Beginner's Guide " +"to Python `_ links to other " +"introductory tutorials and resources for learning Python." +msgstr "" + +#: ../Doc/faq/general.rst:33 +msgid "What is the Python Software Foundation?" +msgstr "" + +#: ../Doc/faq/general.rst:35 +msgid "" +"The Python Software Foundation is an independent non-profit organization " +"that holds the copyright on Python versions 2.1 and newer. The PSF's " +"mission is to advance open source technology related to the Python " +"programming language and to publicize the use of Python. The PSF's home " +"page is at https://www.python.org/psf/." +msgstr "" + +#: ../Doc/faq/general.rst:41 +msgid "" +"Donations to the PSF are tax-exempt in the US. If you use Python and find " +"it helpful, please contribute via `the PSF donation page `_." +msgstr "" + +#: ../Doc/faq/general.rst:47 +msgid "Are there copyright restrictions on the use of Python?" +msgstr "" + +#: ../Doc/faq/general.rst:49 +msgid "" +"You can do anything you want with the source, as long as you leave the " +"copyrights in and display those copyrights in any documentation about Python " +"that you produce. If you honor the copyright rules, it's OK to use Python " +"for commercial use, to sell copies of Python in source or binary form " +"(modified or unmodified), or to sell products that incorporate Python in " +"some form. We would still like to know about all commercial use of Python, " +"of course." +msgstr "" + +#: ../Doc/faq/general.rst:56 +msgid "" +"See `the PSF license page `_ to find " +"further explanations and a link to the full text of the license." +msgstr "" + +#: ../Doc/faq/general.rst:59 +msgid "" +"The Python logo is trademarked, and in certain cases permission is required " +"to use it. Consult `the Trademark Usage Policy `__ for more information." +msgstr "" + +#: ../Doc/faq/general.rst:65 +msgid "Why was Python created in the first place?" +msgstr "" + +#: ../Doc/faq/general.rst:67 +msgid "" +"Here's a *very* brief summary of what started it all, written by Guido van " +"Rossum:" +msgstr "" + +#: ../Doc/faq/general.rst:70 +msgid "" +"I had extensive experience with implementing an interpreted language in the " +"ABC group at CWI, and from working with this group I had learned a lot about " +"language design. This is the origin of many Python features, including the " +"use of indentation for statement grouping and the inclusion of very-high-" +"level data types (although the details are all different in Python)." +msgstr "" + +#: ../Doc/faq/general.rst:77 +msgid "" +"I had a number of gripes about the ABC language, but also liked many of its " +"features. It was impossible to extend the ABC language (or its " +"implementation) to remedy my complaints -- in fact its lack of extensibility " +"was one of its biggest problems. I had some experience with using Modula-2+ " +"and talked with the designers of Modula-3 and read the Modula-3 report. " +"Modula-3 is the origin of the syntax and semantics used for exceptions, and " +"some other Python features." +msgstr "" + +#: ../Doc/faq/general.rst:85 +msgid "" +"I was working in the Amoeba distributed operating system group at CWI. We " +"needed a better way to do system administration than by writing either C " +"programs or Bourne shell scripts, since Amoeba had its own system call " +"interface which wasn't easily accessible from the Bourne shell. My " +"experience with error handling in Amoeba made me acutely aware of the " +"importance of exceptions as a programming language feature." +msgstr "" + +#: ../Doc/faq/general.rst:92 +msgid "" +"It occurred to me that a scripting language with a syntax like ABC but with " +"access to the Amoeba system calls would fill the need. I realized that it " +"would be foolish to write an Amoeba-specific language, so I decided that I " +"needed a language that was generally extensible." +msgstr "" + +#: ../Doc/faq/general.rst:97 +msgid "" +"During the 1989 Christmas holidays, I had a lot of time on my hand, so I " +"decided to give it a try. During the next year, while still mostly working " +"on it in my own time, Python was used in the Amoeba project with increasing " +"success, and the feedback from colleagues made me add many early " +"improvements." +msgstr "" + +#: ../Doc/faq/general.rst:103 +msgid "" +"In February 1991, after just over a year of development, I decided to post " +"to USENET. The rest is in the ``Misc/HISTORY`` file." +msgstr "" + +#: ../Doc/faq/general.rst:108 +msgid "What is Python good for?" +msgstr "" + +#: ../Doc/faq/general.rst:110 +msgid "" +"Python is a high-level general-purpose programming language that can be " +"applied to many different classes of problems." +msgstr "" + +#: ../Doc/faq/general.rst:113 +msgid "" +"The language comes with a large standard library that covers areas such as " +"string processing (regular expressions, Unicode, calculating differences " +"between files), Internet protocols (HTTP, FTP, SMTP, XML-RPC, POP, IMAP, CGI " +"programming), software engineering (unit testing, logging, profiling, " +"parsing Python code), and operating system interfaces (system calls, " +"filesystems, TCP/IP sockets). Look at the table of contents for :ref:" +"`library-index` to get an idea of what's available. A wide variety of third-" +"party extensions are also available. Consult `the Python Package Index " +"`_ to find packages of interest to you." +msgstr "" + +#: ../Doc/faq/general.rst:125 +msgid "How does the Python version numbering scheme work?" +msgstr "" + +#: ../Doc/faq/general.rst:127 +msgid "" +"Python versions are numbered A.B.C or A.B. A is the major version number -- " +"it is only incremented for really major changes in the language. B is the " +"minor version number, incremented for less earth-shattering changes. C is " +"the micro-level -- it is incremented for each bugfix release. See :pep:`6` " +"for more information about bugfix releases." +msgstr "" + +#: ../Doc/faq/general.rst:133 +msgid "" +"Not all releases are bugfix releases. In the run-up to a new major release, " +"a series of development releases are made, denoted as alpha, beta, or " +"release candidate. Alphas are early releases in which interfaces aren't yet " +"finalized; it's not unexpected to see an interface change between two alpha " +"releases. Betas are more stable, preserving existing interfaces but possibly " +"adding new modules, and release candidates are frozen, making no changes " +"except as needed to fix critical bugs." +msgstr "" + +#: ../Doc/faq/general.rst:141 +msgid "" +"Alpha, beta and release candidate versions have an additional suffix. The " +"suffix for an alpha version is \"aN\" for some small number N, the suffix " +"for a beta version is \"bN\" for some small number N, and the suffix for a " +"release candidate version is \"cN\" for some small number N. In other " +"words, all versions labeled 2.0aN precede the versions labeled 2.0bN, which " +"precede versions labeled 2.0cN, and *those* precede 2.0." +msgstr "" + +#: ../Doc/faq/general.rst:148 +msgid "" +"You may also find version numbers with a \"+\" suffix, e.g. \"2.2+\". These " +"are unreleased versions, built directly from the CPython development " +"repository. In practice, after a final minor release is made, the version " +"is incremented to the next minor version, which becomes the \"a0\" version, " +"e.g. \"2.4a0\"." +msgstr "" + +#: ../Doc/faq/general.rst:153 +msgid "" +"See also the documentation for :data:`sys.version`, :data:`sys.hexversion`, " +"and :data:`sys.version_info`." +msgstr "" + +#: ../Doc/faq/general.rst:158 +msgid "How do I obtain a copy of the Python source?" +msgstr "" + +#: ../Doc/faq/general.rst:160 +msgid "" +"The latest Python source distribution is always available from python.org, " +"at https://www.python.org/downloads/. The latest development sources can be " +"obtained via anonymous Mercurial access at https://hg.python.org/cpython." +msgstr "" + +#: ../Doc/faq/general.rst:164 +msgid "" +"The source distribution is a gzipped tar file containing the complete C " +"source, Sphinx-formatted documentation, Python library modules, example " +"programs, and several useful pieces of freely distributable software. The " +"source will compile and run out of the box on most UNIX platforms." +msgstr "" + +#: ../Doc/faq/general.rst:169 +msgid "" +"Consult the `Getting Started section of the Python Developer's Guide " +"`__ for more information on " +"getting the source code and compiling it." +msgstr "" + +#: ../Doc/faq/general.rst:175 +msgid "How do I get documentation on Python?" +msgstr "" + +#: ../Doc/faq/general.rst:179 +msgid "" +"The standard documentation for the current stable version of Python is " +"available at https://docs.python.org/3/. PDF, plain text, and downloadable " +"HTML versions are also available at https://docs.python.org/3/download.html." +msgstr "" + +#: ../Doc/faq/general.rst:183 +msgid "" +"The documentation is written in reStructuredText and processed by `the " +"Sphinx documentation tool `__. The reStructuredText " +"source for the documentation is part of the Python source distribution." +msgstr "" + +#: ../Doc/faq/general.rst:189 +msgid "I've never programmed before. Is there a Python tutorial?" +msgstr "" + +#: ../Doc/faq/general.rst:191 +msgid "" +"There are numerous tutorials and books available. The standard " +"documentation includes :ref:`tutorial-index`." +msgstr "" + +#: ../Doc/faq/general.rst:194 +msgid "" +"Consult `the Beginner's Guide `_ to find information for beginning Python programmers, " +"including lists of tutorials." +msgstr "" + +#: ../Doc/faq/general.rst:199 +msgid "Is there a newsgroup or mailing list devoted to Python?" +msgstr "" + +#: ../Doc/faq/general.rst:201 +msgid "" +"There is a newsgroup, :newsgroup:`comp.lang.python`, and a mailing list, " +"`python-list `_. The " +"newsgroup and mailing list are gatewayed into each other -- if you can read " +"news it's unnecessary to subscribe to the mailing list. :newsgroup:`comp." +"lang.python` is high-traffic, receiving hundreds of postings every day, and " +"Usenet readers are often more able to cope with this volume." +msgstr "" + +#: ../Doc/faq/general.rst:208 +msgid "" +"Announcements of new software releases and events can be found in comp.lang." +"python.announce, a low-traffic moderated list that receives about five " +"postings per day. It's available as `the python-announce mailing list " +"`_." +msgstr "" + +#: ../Doc/faq/general.rst:213 +msgid "" +"More info about other mailing lists and newsgroups can be found at https://" +"www.python.org/community/lists/." +msgstr "" + +#: ../Doc/faq/general.rst:218 +msgid "How do I get a beta test version of Python?" +msgstr "" + +#: ../Doc/faq/general.rst:220 +msgid "" +"Alpha and beta releases are available from https://www.python.org/" +"downloads/. All releases are announced on the comp.lang.python and comp." +"lang.python.announce newsgroups and on the Python home page at https://www." +"python.org/; an RSS feed of news is available." +msgstr "" + +#: ../Doc/faq/general.rst:225 +msgid "" +"You can also access the development version of Python through Mercurial. " +"See https://docs.python.org/devguide/faq.html for details." +msgstr "" + +#: ../Doc/faq/general.rst:230 +msgid "How do I submit bug reports and patches for Python?" +msgstr "" + +#: ../Doc/faq/general.rst:232 +msgid "" +"To report a bug or submit a patch, please use the Roundup installation at " +"https://bugs.python.org/." +msgstr "" + +#: ../Doc/faq/general.rst:235 +msgid "" +"You must have a Roundup account to report bugs; this makes it possible for " +"us to contact you if we have follow-up questions. It will also enable " +"Roundup to send you updates as we act on your bug. If you had previously " +"used SourceForge to report bugs to Python, you can obtain your Roundup " +"password through Roundup's `password reset procedure `_." +msgstr "" + +#: ../Doc/faq/general.rst:241 +msgid "" +"For more information on how Python is developed, consult `the Python " +"Developer's Guide `_." +msgstr "" + +#: ../Doc/faq/general.rst:246 +msgid "Are there any published articles about Python that I can reference?" +msgstr "" + +#: ../Doc/faq/general.rst:248 +msgid "It's probably best to cite your favorite book about Python." +msgstr "" + +#: ../Doc/faq/general.rst:250 +msgid "" +"The very first article about Python was written in 1991 and is now quite " +"outdated." +msgstr "" + +#: ../Doc/faq/general.rst:253 +msgid "" +"Guido van Rossum and Jelke de Boer, \"Interactively Testing Remote Servers " +"Using the Python Programming Language\", CWI Quarterly, Volume 4, Issue 4 " +"(December 1991), Amsterdam, pp 283-303." +msgstr "" + +#: ../Doc/faq/general.rst:259 +msgid "Are there any books on Python?" +msgstr "" + +#: ../Doc/faq/general.rst:261 +msgid "" +"Yes, there are many, and more are being published. See the python.org wiki " +"at https://wiki.python.org/moin/PythonBooks for a list." +msgstr "" + +#: ../Doc/faq/general.rst:264 +msgid "" +"You can also search online bookstores for \"Python\" and filter out the " +"Monty Python references; or perhaps search for \"Python\" and \"language\"." +msgstr "" + +#: ../Doc/faq/general.rst:269 +msgid "Where in the world is www.python.org located?" +msgstr "" + +#: ../Doc/faq/general.rst:271 +msgid "" +"The Python project's infrastructure is located all over the world. `www." +"python.org `_ is graciously hosted by `Rackspace " +"`_, with CDN caching provided by `Fastly `_. `Upfront Systems `_ " +"hosts `bugs.python.org `_. Many other Python " +"services like `the Wiki `_ are hosted by `Oregon " +"State University Open Source Lab `_." +msgstr "" + +#: ../Doc/faq/general.rst:282 +msgid "Why is it called Python?" +msgstr "" + +#: ../Doc/faq/general.rst:284 +msgid "" +"When he began implementing Python, Guido van Rossum was also reading the " +"published scripts from `\"Monty Python's Flying Circus\" `__, a BBC comedy series from the 1970s. " +"Van Rossum thought he needed a name that was short, unique, and slightly " +"mysterious, so he decided to call the language Python." +msgstr "" + +#: ../Doc/faq/general.rst:292 +msgid "Do I have to like \"Monty Python's Flying Circus\"?" +msgstr "" + +#: ../Doc/faq/general.rst:294 +msgid "No, but it helps. :)" +msgstr "" + +#: ../Doc/faq/general.rst:298 +msgid "Python in the real world" +msgstr "" + +#: ../Doc/faq/general.rst:301 +msgid "How stable is Python?" +msgstr "" + +#: ../Doc/faq/general.rst:303 +msgid "" +"Very stable. New, stable releases have been coming out roughly every 6 to " +"18 months since 1991, and this seems likely to continue. Currently there " +"are usually around 18 months between major releases." +msgstr "" + +#: ../Doc/faq/general.rst:307 +msgid "" +"The developers issue \"bugfix\" releases of older versions, so the stability " +"of existing releases gradually improves. Bugfix releases, indicated by a " +"third component of the version number (e.g. 2.5.3, 2.6.2), are managed for " +"stability; only fixes for known problems are included in a bugfix release, " +"and it's guaranteed that interfaces will remain the same throughout a series " +"of bugfix releases." +msgstr "" + +#: ../Doc/faq/general.rst:314 +msgid "" +"The latest stable releases can always be found on the `Python download page " +"`_. There are two recommended production-" +"ready versions at this point in time, because at the moment there are two " +"branches of stable releases: 2.x and 3.x. Python 3.x may be less useful " +"than 2.x, since currently there is more third party software available for " +"Python 2 than for Python 3. Python 2 code will generally not run unchanged " +"in Python 3." +msgstr "" + +#: ../Doc/faq/general.rst:323 +msgid "How many people are using Python?" +msgstr "" + +#: ../Doc/faq/general.rst:325 +msgid "" +"There are probably tens of thousands of users, though it's difficult to " +"obtain an exact count." +msgstr "" + +#: ../Doc/faq/general.rst:328 +msgid "" +"Python is available for free download, so there are no sales figures, and " +"it's available from many different sites and packaged with many Linux " +"distributions, so download statistics don't tell the whole story either." +msgstr "" + +#: ../Doc/faq/general.rst:332 +msgid "" +"The comp.lang.python newsgroup is very active, but not all Python users post " +"to the group or even read it." +msgstr "" + +#: ../Doc/faq/general.rst:337 +msgid "Have any significant projects been done in Python?" +msgstr "" + +#: ../Doc/faq/general.rst:339 +msgid "" +"See https://www.python.org/about/success for a list of projects that use " +"Python. Consulting the proceedings for `past Python conferences `_ will reveal contributions from many " +"different companies and organizations." +msgstr "" + +#: ../Doc/faq/general.rst:344 +msgid "" +"High-profile Python projects include `the Mailman mailing list manager " +"`_ and `the Zope application server `_. Several Linux distributions, most notably `Red Hat `_, have written part or all of their installer and system " +"administration software in Python. Companies that use Python internally " +"include Google, Yahoo, and Lucasfilm Ltd." +msgstr "" + +#: ../Doc/faq/general.rst:353 +msgid "What new developments are expected for Python in the future?" +msgstr "" + +#: ../Doc/faq/general.rst:355 +msgid "" +"See https://www.python.org/dev/peps/ for the Python Enhancement Proposals " +"(PEPs). PEPs are design documents describing a suggested new feature for " +"Python, providing a concise technical specification and a rationale. Look " +"for a PEP titled \"Python X.Y Release Schedule\", where X.Y is a version " +"that hasn't been publicly released yet." +msgstr "" + +#: ../Doc/faq/general.rst:361 +msgid "" +"New development is discussed on `the python-dev mailing list `_." +msgstr "" + +#: ../Doc/faq/general.rst:366 +msgid "Is it reasonable to propose incompatible changes to Python?" +msgstr "" + +#: ../Doc/faq/general.rst:368 +msgid "" +"In general, no. There are already millions of lines of Python code around " +"the world, so any change in the language that invalidates more than a very " +"small fraction of existing programs has to be frowned upon. Even if you can " +"provide a conversion program, there's still the problem of updating all " +"documentation; many books have been written about Python, and we don't want " +"to invalidate them all at a single stroke." +msgstr "" + +#: ../Doc/faq/general.rst:375 +msgid "" +"Providing a gradual upgrade path is necessary if a feature has to be " +"changed. :pep:`5` describes the procedure followed for introducing backward-" +"incompatible changes while minimizing disruption for users." +msgstr "" + +#: ../Doc/faq/general.rst:381 +msgid "Is Python a good language for beginning programmers?" +msgstr "" + +#: ../Doc/faq/general.rst:383 ../Doc/faq/library.rst:790 +#: ../Doc/faq/programming.rst:17 ../Doc/faq/programming.rst:60 +msgid "Yes." +msgstr "" + +#: ../Doc/faq/general.rst:385 +msgid "" +"It is still common to start students with a procedural and statically typed " +"language such as Pascal, C, or a subset of C++ or Java. Students may be " +"better served by learning Python as their first language. Python has a very " +"simple and consistent syntax and a large standard library and, most " +"importantly, using Python in a beginning programming course lets students " +"concentrate on important programming skills such as problem decomposition " +"and data type design. With Python, students can be quickly introduced to " +"basic concepts such as loops and procedures. They can probably even work " +"with user-defined objects in their very first course." +msgstr "" + +#: ../Doc/faq/general.rst:395 +msgid "" +"For a student who has never programmed before, using a statically typed " +"language seems unnatural. It presents additional complexity that the " +"student must master and slows the pace of the course. The students are " +"trying to learn to think like a computer, decompose problems, design " +"consistent interfaces, and encapsulate data. While learning to use a " +"statically typed language is important in the long term, it is not " +"necessarily the best topic to address in the students' first programming " +"course." +msgstr "" + +#: ../Doc/faq/general.rst:403 +msgid "" +"Many other aspects of Python make it a good first language. Like Java, " +"Python has a large standard library so that students can be assigned " +"programming projects very early in the course that *do* something. " +"Assignments aren't restricted to the standard four-function calculator and " +"check balancing programs. By using the standard library, students can gain " +"the satisfaction of working on realistic applications as they learn the " +"fundamentals of programming. Using the standard library also teaches " +"students about code reuse. Third-party modules such as PyGame are also " +"helpful in extending the students' reach." +msgstr "" + +#: ../Doc/faq/general.rst:412 +msgid "" +"Python's interactive interpreter enables students to test language features " +"while they're programming. They can keep a window with the interpreter " +"running while they enter their program's source in another window. If they " +"can't remember the methods for a list, they can do something like this::" +msgstr "" + +#: ../Doc/faq/general.rst:441 +msgid "" +"With the interpreter, documentation is never far from the student as they " +"are programming." +msgstr "" + +#: ../Doc/faq/general.rst:444 +msgid "" +"There are also good IDEs for Python. IDLE is a cross-platform IDE for " +"Python that is written in Python using Tkinter. PythonWin is a Windows-" +"specific IDE. Emacs users will be happy to know that there is a very good " +"Python mode for Emacs. All of these programming environments provide syntax " +"highlighting, auto-indenting, and access to the interactive interpreter " +"while coding. Consult `the Python wiki `_ for a full list of Python editing environments." +msgstr "" + +#: ../Doc/faq/general.rst:452 +msgid "" +"If you want to discuss Python's use in education, you may be interested in " +"joining `the edu-sig mailing list `_." +msgstr "" + +#: ../Doc/faq/gui.rst:5 +msgid "Graphic User Interface FAQ" +msgstr "" + +#: ../Doc/faq/gui.rst:15 +msgid "General GUI Questions" +msgstr "" + +#: ../Doc/faq/gui.rst:18 +msgid "What platform-independent GUI toolkits exist for Python?" +msgstr "" + +#: ../Doc/faq/gui.rst:20 +msgid "" +"Depending on what platform(s) you are aiming at, there are several. Some of " +"them haven't been ported to Python 3 yet. At least `Tkinter`_ and `Qt`_ are " +"known to be Python 3-compatible." +msgstr "" + +#: ../Doc/faq/gui.rst:27 +msgid "Tkinter" +msgstr "" + +#: ../Doc/faq/gui.rst:29 +msgid "" +"Standard builds of Python include an object-oriented interface to the Tcl/Tk " +"widget set, called :ref:`tkinter `. This is probably the easiest " +"to install (since it comes included with most `binary distributions `_ of Python) and use. For more info about Tk, " +"including pointers to the source, see the `Tcl/Tk home page `_. Tcl/Tk is fully portable to the Mac OS X, Windows, and Unix " +"platforms." +msgstr "" + +#: ../Doc/faq/gui.rst:38 +msgid "wxWidgets" +msgstr "" + +#: ../Doc/faq/gui.rst:40 +msgid "" +"wxWidgets (https://www.wxwidgets.org) is a free, portable GUI class library " +"written in C++ that provides a native look and feel on a number of " +"platforms, with Windows, Mac OS X, GTK, X11, all listed as current stable " +"targets. Language bindings are available for a number of languages " +"including Python, Perl, Ruby, etc." +msgstr "" + +#: ../Doc/faq/gui.rst:46 +msgid "" +"wxPython (http://www.wxpython.org) is the Python binding for wxwidgets. " +"While it often lags slightly behind the official wxWidgets releases, it also " +"offers a number of features via pure Python extensions that are not " +"available in other language bindings. There is an active wxPython user and " +"developer community." +msgstr "" + +#: ../Doc/faq/gui.rst:52 +msgid "" +"Both wxWidgets and wxPython are free, open source, software with permissive " +"licences that allow their use in commercial products as well as in freeware " +"or shareware." +msgstr "" + +#: ../Doc/faq/gui.rst:58 +msgid "Qt" +msgstr "" + +#: ../Doc/faq/gui.rst:60 +msgid "" +"There are bindings available for the Qt toolkit (using either `PyQt `_ or `PySide `_) and for KDE (`PyKDE4 `__). PyQt is currently more mature than PySide, but you must " +"buy a PyQt license from `Riverbank Computing `_ if you want to write proprietary " +"applications. PySide is free for all applications." +msgstr "" + +#: ../Doc/faq/gui.rst:67 +msgid "" +"Qt 4.5 upwards is licensed under the LGPL license; also, commercial licenses " +"are available from `The Qt Company `_." +msgstr "" + +#: ../Doc/faq/gui.rst:71 +msgid "Gtk+" +msgstr "" + +#: ../Doc/faq/gui.rst:73 +msgid "" +"The `GObject introspection bindings `_ for Python allow you to write GTK+ 3 applications. There is " +"also a `Python GTK+ 3 Tutorial `_." +msgstr "" + +#: ../Doc/faq/gui.rst:77 +msgid "" +"The older PyGtk bindings for the `Gtk+ 2 toolkit `_ have " +"been implemented by James Henstridge; see ." +msgstr "" + +#: ../Doc/faq/gui.rst:81 +msgid "FLTK" +msgstr "" + +#: ../Doc/faq/gui.rst:83 +msgid "" +"Python bindings for `the FLTK toolkit `_, a simple yet " +"powerful and mature cross-platform windowing system, are available from `the " +"PyFLTK project `_." +msgstr "" + +#: ../Doc/faq/gui.rst:89 +msgid "FOX" +msgstr "" + +#: ../Doc/faq/gui.rst:91 +msgid "" +"A wrapper for `the FOX toolkit `_ called `FXpy " +"`_ is available. FOX supports both Unix " +"variants and Windows." +msgstr "" + +#: ../Doc/faq/gui.rst:97 +msgid "OpenGL" +msgstr "" + +#: ../Doc/faq/gui.rst:99 +msgid "For OpenGL bindings, see `PyOpenGL `_." +msgstr "" + +#: ../Doc/faq/gui.rst:103 +msgid "What platform-specific GUI toolkits exist for Python?" +msgstr "" + +#: ../Doc/faq/gui.rst:105 +msgid "" +"By installing the `PyObjc Objective-C bridge `_, Python programs can use Mac OS X's Cocoa libraries." +msgstr "" + +#: ../Doc/faq/gui.rst:109 +msgid "" +":ref:`Pythonwin ` by Mark Hammond includes an interface to the " +"Microsoft Foundation Classes and a Python programming environment that's " +"written mostly in Python using the MFC classes." +msgstr "" + +#: ../Doc/faq/gui.rst:115 +msgid "Tkinter questions" +msgstr "" + +#: ../Doc/faq/gui.rst:118 +msgid "How do I freeze Tkinter applications?" +msgstr "" + +#: ../Doc/faq/gui.rst:120 +msgid "" +"Freeze is a tool to create stand-alone applications. When freezing Tkinter " +"applications, the applications will not be truly stand-alone, as the " +"application will still need the Tcl and Tk libraries." +msgstr "" + +#: ../Doc/faq/gui.rst:124 +msgid "" +"One solution is to ship the application with the Tcl and Tk libraries, and " +"point to them at run-time using the :envvar:`TCL_LIBRARY` and :envvar:" +"`TK_LIBRARY` environment variables." +msgstr "" + +#: ../Doc/faq/gui.rst:128 +msgid "" +"To get truly stand-alone applications, the Tcl scripts that form the library " +"have to be integrated into the application as well. One tool supporting that " +"is SAM (stand-alone modules), which is part of the Tix distribution (http://" +"tix.sourceforge.net/)." +msgstr "" + +#: ../Doc/faq/gui.rst:133 +msgid "" +"Build Tix with SAM enabled, perform the appropriate call to :c:func:" +"`Tclsam_init`, etc. inside Python's :file:`Modules/tkappinit.c`, and link " +"with libtclsam and libtksam (you might include the Tix libraries as well)." +msgstr "" + +#: ../Doc/faq/gui.rst:140 +msgid "Can I have Tk events handled while waiting for I/O?" +msgstr "" + +#: ../Doc/faq/gui.rst:142 +msgid "" +"On platforms other than Windows, yes, and you don't even need threads! But " +"you'll have to restructure your I/O code a bit. Tk has the equivalent of " +"Xt's :c:func:`XtAddInput()` call, which allows you to register a callback " +"function which will be called from the Tk mainloop when I/O is possible on a " +"file descriptor. See :ref:`tkinter-file-handlers`." +msgstr "" + +#: ../Doc/faq/gui.rst:150 +msgid "I can't get key bindings to work in Tkinter: why?" +msgstr "" + +#: ../Doc/faq/gui.rst:152 +msgid "" +"An often-heard complaint is that event handlers bound to events with the :" +"meth:`bind` method don't get handled even when the appropriate key is " +"pressed." +msgstr "" + +#: ../Doc/faq/gui.rst:155 +msgid "" +"The most common cause is that the widget to which the binding applies " +"doesn't have \"keyboard focus\". Check out the Tk documentation for the " +"focus command. Usually a widget is given the keyboard focus by clicking in " +"it (but not for labels; see the takefocus option)." +msgstr "" + +#: ../Doc/faq/index.rst:5 +msgid "Python Frequently Asked Questions" +msgstr "" + +#: ../Doc/faq/installed.rst:3 +msgid "\"Why is Python Installed on my Computer?\" FAQ" +msgstr "" + +#: ../Doc/faq/installed.rst:8 +msgid "" +"Python is a programming language. It's used for many different " +"applications. It's used in some high schools and colleges as an introductory " +"programming language because Python is easy to learn, but it's also used by " +"professional software developers at places such as Google, NASA, and " +"Lucasfilm Ltd." +msgstr "" + +#: ../Doc/faq/installed.rst:13 +msgid "" +"If you wish to learn more about Python, start with the `Beginner's Guide to " +"Python `_." +msgstr "" + +#: ../Doc/faq/installed.rst:18 +msgid "Why is Python installed on my machine?" +msgstr "" + +#: ../Doc/faq/installed.rst:20 +msgid "" +"If you find Python installed on your system but don't remember installing " +"it, there are several possible ways it could have gotten there." +msgstr "" + +#: ../Doc/faq/installed.rst:23 +msgid "" +"Perhaps another user on the computer wanted to learn programming and " +"installed it; you'll have to figure out who's been using the machine and " +"might have installed it." +msgstr "" + +#: ../Doc/faq/installed.rst:26 +msgid "" +"A third-party application installed on the machine might have been written " +"in Python and included a Python installation. There are many such " +"applications, from GUI programs to network servers and administrative " +"scripts." +msgstr "" + +#: ../Doc/faq/installed.rst:29 +msgid "" +"Some Windows machines also have Python installed. At this writing we're " +"aware of computers from Hewlett-Packard and Compaq that include Python. " +"Apparently some of HP/Compaq's administrative tools are written in Python." +msgstr "" + +#: ../Doc/faq/installed.rst:32 +msgid "" +"Many Unix-compatible operating systems, such as Mac OS X and some Linux " +"distributions, have Python installed by default; it's included in the base " +"installation." +msgstr "" + +#: ../Doc/faq/installed.rst:38 +msgid "Can I delete Python?" +msgstr "" + +#: ../Doc/faq/installed.rst:40 +msgid "That depends on where Python came from." +msgstr "" + +#: ../Doc/faq/installed.rst:42 +msgid "" +"If someone installed it deliberately, you can remove it without hurting " +"anything. On Windows, use the Add/Remove Programs icon in the Control Panel." +msgstr "" + +#: ../Doc/faq/installed.rst:45 +msgid "" +"If Python was installed by a third-party application, you can also remove " +"it, but that application will no longer work. You should use that " +"application's uninstaller rather than removing Python directly." +msgstr "" + +#: ../Doc/faq/installed.rst:49 +msgid "" +"If Python came with your operating system, removing it is not recommended. " +"If you remove it, whatever tools were written in Python will no longer run, " +"and some of them might be important to you. Reinstalling the whole system " +"would then be required to fix things again." +msgstr "" + +#: ../Doc/faq/library.rst:5 +msgid "Library and Extension FAQ" +msgstr "" + +#: ../Doc/faq/library.rst:12 +msgid "General Library Questions" +msgstr "" + +#: ../Doc/faq/library.rst:15 +msgid "How do I find a module or application to perform task X?" +msgstr "" + +#: ../Doc/faq/library.rst:17 +msgid "" +"Check :ref:`the Library Reference ` to see if there's a " +"relevant standard library module. (Eventually you'll learn what's in the " +"standard library and will be able to skip this step.)" +msgstr "" + +#: ../Doc/faq/library.rst:21 +msgid "" +"For third-party packages, search the `Python Package Index `_ or try `Google `_ or another Web " +"search engine. Searching for \"Python\" plus a keyword or two for your " +"topic of interest will usually find something helpful." +msgstr "" + +#: ../Doc/faq/library.rst:28 +msgid "Where is the math.py (socket.py, regex.py, etc.) source file?" +msgstr "" + +#: ../Doc/faq/library.rst:30 +msgid "" +"If you can't find a source file for a module it may be a built-in or " +"dynamically loaded module implemented in C, C++ or other compiled language. " +"In this case you may not have the source file or it may be something like :" +"file:`mathmodule.c`, somewhere in a C source directory (not on the Python " +"Path)." +msgstr "" + +#: ../Doc/faq/library.rst:35 +msgid "There are (at least) three kinds of modules in Python:" +msgstr "" + +#: ../Doc/faq/library.rst:37 +msgid "modules written in Python (.py);" +msgstr "" + +#: ../Doc/faq/library.rst:38 +msgid "" +"modules written in C and dynamically loaded (.dll, .pyd, .so, .sl, etc);" +msgstr "" + +#: ../Doc/faq/library.rst:39 +msgid "" +"modules written in C and linked with the interpreter; to get a list of " +"these, type::" +msgstr "" + +#: ../Doc/faq/library.rst:47 +msgid "How do I make a Python script executable on Unix?" +msgstr "" + +#: ../Doc/faq/library.rst:49 +msgid "" +"You need to do two things: the script file's mode must be executable and the " +"first line must begin with ``#!`` followed by the path of the Python " +"interpreter." +msgstr "" + +#: ../Doc/faq/library.rst:53 +msgid "" +"The first is done by executing ``chmod +x scriptfile`` or perhaps ``chmod " +"755 scriptfile``." +msgstr "" + +#: ../Doc/faq/library.rst:56 +msgid "" +"The second can be done in a number of ways. The most straightforward way is " +"to write ::" +msgstr "" + +#: ../Doc/faq/library.rst:61 +msgid "" +"as the very first line of your file, using the pathname for where the Python " +"interpreter is installed on your platform." +msgstr "" + +#: ../Doc/faq/library.rst:64 +msgid "" +"If you would like the script to be independent of where the Python " +"interpreter lives, you can use the :program:`env` program. Almost all Unix " +"variants support the following, assuming the Python interpreter is in a " +"directory on the user's :envvar:`PATH`::" +msgstr "" + +#: ../Doc/faq/library.rst:71 +msgid "" +"*Don't* do this for CGI scripts. The :envvar:`PATH` variable for CGI " +"scripts is often very minimal, so you need to use the actual absolute " +"pathname of the interpreter." +msgstr "" + +#: ../Doc/faq/library.rst:75 +msgid "" +"Occasionally, a user's environment is so full that the :program:`/usr/bin/" +"env` program fails; or there's no env program at all. In that case, you can " +"try the following hack (due to Alex Rezinsky)::" +msgstr "" + +#: ../Doc/faq/library.rst:84 +msgid "" +"The minor disadvantage is that this defines the script's __doc__ string. " +"However, you can fix that by adding ::" +msgstr "" + +#: ../Doc/faq/library.rst:92 +msgid "Is there a curses/termcap package for Python?" +msgstr "" + +#: ../Doc/faq/library.rst:96 +msgid "" +"For Unix variants: The standard Python source distribution comes with a " +"curses module in the :source:`Modules` subdirectory, though it's not " +"compiled by default. (Note that this is not available in the Windows " +"distribution -- there is no curses module for Windows.)" +msgstr "" + +#: ../Doc/faq/library.rst:101 +msgid "" +"The :mod:`curses` module supports basic curses features as well as many " +"additional functions from ncurses and SYSV curses such as colour, " +"alternative character set support, pads, and mouse support. This means the " +"module isn't compatible with operating systems that only have BSD curses, " +"but there don't seem to be any currently maintained OSes that fall into this " +"category." +msgstr "" + +#: ../Doc/faq/library.rst:107 +msgid "" +"For Windows: use `the consolelib module `_." +msgstr "" + +#: ../Doc/faq/library.rst:112 +msgid "Is there an equivalent to C's onexit() in Python?" +msgstr "" + +#: ../Doc/faq/library.rst:114 +msgid "" +"The :mod:`atexit` module provides a register function that is similar to " +"C's :c:func:`onexit`." +msgstr "" + +#: ../Doc/faq/library.rst:119 +msgid "Why don't my signal handlers work?" +msgstr "" + +#: ../Doc/faq/library.rst:121 +msgid "" +"The most common problem is that the signal handler is declared with the " +"wrong argument list. It is called as ::" +msgstr "" + +#: ../Doc/faq/library.rst:126 +msgid "so it should be declared with two arguments::" +msgstr "" + +#: ../Doc/faq/library.rst:133 +msgid "Common tasks" +msgstr "" + +#: ../Doc/faq/library.rst:136 +msgid "How do I test a Python program or component?" +msgstr "" + +#: ../Doc/faq/library.rst:138 +msgid "" +"Python comes with two testing frameworks. The :mod:`doctest` module finds " +"examples in the docstrings for a module and runs them, comparing the output " +"with the expected output given in the docstring." +msgstr "" + +#: ../Doc/faq/library.rst:142 +msgid "" +"The :mod:`unittest` module is a fancier testing framework modelled on Java " +"and Smalltalk testing frameworks." +msgstr "" + +#: ../Doc/faq/library.rst:145 +msgid "" +"To make testing easier, you should use good modular design in your program. " +"Your program should have almost all functionality encapsulated in either " +"functions or class methods -- and this sometimes has the surprising and " +"delightful effect of making the program run faster (because local variable " +"accesses are faster than global accesses). Furthermore the program should " +"avoid depending on mutating global variables, since this makes testing much " +"more difficult to do." +msgstr "" + +#: ../Doc/faq/library.rst:153 +msgid "The \"global main logic\" of your program may be as simple as ::" +msgstr "" + +#: ../Doc/faq/library.rst:158 +msgid "at the bottom of the main module of your program." +msgstr "" + +#: ../Doc/faq/library.rst:160 +msgid "" +"Once your program is organized as a tractable collection of functions and " +"class behaviours you should write test functions that exercise the " +"behaviours. A test suite that automates a sequence of tests can be " +"associated with each module. This sounds like a lot of work, but since " +"Python is so terse and flexible it's surprisingly easy. You can make coding " +"much more pleasant and fun by writing your test functions in parallel with " +"the \"production code\", since this makes it easy to find bugs and even " +"design flaws earlier." +msgstr "" + +#: ../Doc/faq/library.rst:168 +msgid "" +"\"Support modules\" that are not intended to be the main module of a program " +"may include a self-test of the module. ::" +msgstr "" + +#: ../Doc/faq/library.rst:174 +msgid "" +"Even programs that interact with complex external interfaces may be tested " +"when the external interfaces are unavailable by using \"fake\" interfaces " +"implemented in Python." +msgstr "" + +#: ../Doc/faq/library.rst:180 +msgid "How do I create documentation from doc strings?" +msgstr "" + +#: ../Doc/faq/library.rst:182 +msgid "" +"The :mod:`pydoc` module can create HTML from the doc strings in your Python " +"source code. An alternative for creating API documentation purely from " +"docstrings is `epydoc `_. `Sphinx `_ can also include docstring content." +msgstr "" + +#: ../Doc/faq/library.rst:189 +msgid "How do I get a single keypress at a time?" +msgstr "" + +#: ../Doc/faq/library.rst:191 +msgid "" +"For Unix variants there are several solutions. It's straightforward to do " +"this using curses, but curses is a fairly large module to learn." +msgstr "" + +#: ../Doc/faq/library.rst:235 +msgid "Threads" +msgstr "" + +#: ../Doc/faq/library.rst:238 +msgid "How do I program using threads?" +msgstr "" + +#: ../Doc/faq/library.rst:240 +msgid "" +"Be sure to use the :mod:`threading` module and not the :mod:`_thread` " +"module. The :mod:`threading` module builds convenient abstractions on top of " +"the low-level primitives provided by the :mod:`_thread` module." +msgstr "" + +#: ../Doc/faq/library.rst:244 +msgid "" +"Aahz has a set of slides from his threading tutorial that are helpful; see " +"http://www.pythoncraft.com/OSCON2001/." +msgstr "" + +#: ../Doc/faq/library.rst:249 +msgid "None of my threads seem to run: why?" +msgstr "" + +#: ../Doc/faq/library.rst:251 +msgid "" +"As soon as the main thread exits, all threads are killed. Your main thread " +"is running too quickly, giving the threads no time to do any work." +msgstr "" + +#: ../Doc/faq/library.rst:254 +msgid "" +"A simple fix is to add a sleep to the end of the program that's long enough " +"for all the threads to finish::" +msgstr "" + +#: ../Doc/faq/library.rst:269 +msgid "" +"But now (on many platforms) the threads don't run in parallel, but appear to " +"run sequentially, one at a time! The reason is that the OS thread scheduler " +"doesn't start a new thread until the previous thread is blocked." +msgstr "" + +#: ../Doc/faq/library.rst:273 +msgid "A simple fix is to add a tiny sleep to the start of the run function::" +msgstr "" + +#: ../Doc/faq/library.rst:286 +msgid "" +"Instead of trying to guess a good delay value for :func:`time.sleep`, it's " +"better to use some kind of semaphore mechanism. One idea is to use the :mod:" +"`queue` module to create a queue object, let each thread append a token to " +"the queue when it finishes, and let the main thread read as many tokens from " +"the queue as there are threads." +msgstr "" + +#: ../Doc/faq/library.rst:294 +msgid "How do I parcel out work among a bunch of worker threads?" +msgstr "" + +#: ../Doc/faq/library.rst:296 +msgid "" +"The easiest way is to use the new :mod:`concurrent.futures` module, " +"especially the :mod:`~concurrent.futures.ThreadPoolExecutor` class." +msgstr "" + +#: ../Doc/faq/library.rst:299 +msgid "" +"Or, if you want fine control over the dispatching algorithm, you can write " +"your own logic manually. Use the :mod:`queue` module to create a queue " +"containing a list of jobs. The :class:`~queue.Queue` class maintains a list " +"of objects and has a ``.put(obj)`` method that adds items to the queue and a " +"``.get()`` method to return them. The class will take care of the locking " +"necessary to ensure that each job is handed out exactly once." +msgstr "" + +#: ../Doc/faq/library.rst:306 +msgid "Here's a trivial example::" +msgstr "" + +#: ../Doc/faq/library.rst:344 +msgid "When run, this will produce the following output:" +msgstr "" + +#: ../Doc/faq/library.rst:362 +msgid "" +"Consult the module's documentation for more details; the :class:`~queue." +"Queue` class provides a featureful interface." +msgstr "" + +#: ../Doc/faq/library.rst:367 +msgid "What kinds of global value mutation are thread-safe?" +msgstr "" + +#: ../Doc/faq/library.rst:369 +msgid "" +"A :term:`global interpreter lock` (GIL) is used internally to ensure that " +"only one thread runs in the Python VM at a time. In general, Python offers " +"to switch among threads only between bytecode instructions; how frequently " +"it switches can be set via :func:`sys.setswitchinterval`. Each bytecode " +"instruction and therefore all the C implementation code reached from each " +"instruction is therefore atomic from the point of view of a Python program." +msgstr "" + +#: ../Doc/faq/library.rst:376 +msgid "" +"In theory, this means an exact accounting requires an exact understanding of " +"the PVM bytecode implementation. In practice, it means that operations on " +"shared variables of built-in data types (ints, lists, dicts, etc) that " +"\"look atomic\" really are." +msgstr "" + +#: ../Doc/faq/library.rst:381 +msgid "" +"For example, the following operations are all atomic (L, L1, L2 are lists, " +"D, D1, D2 are dicts, x, y are objects, i, j are ints)::" +msgstr "" + +#: ../Doc/faq/library.rst:396 +msgid "These aren't::" +msgstr "" + +#: ../Doc/faq/library.rst:403 +msgid "" +"Operations that replace other objects may invoke those other objects' :meth:" +"`__del__` method when their reference count reaches zero, and that can " +"affect things. This is especially true for the mass updates to dictionaries " +"and lists. When in doubt, use a mutex!" +msgstr "" + +#: ../Doc/faq/library.rst:410 +msgid "Can't we get rid of the Global Interpreter Lock?" +msgstr "" + +#: ../Doc/faq/library.rst:414 +msgid "" +"The :term:`global interpreter lock` (GIL) is often seen as a hindrance to " +"Python's deployment on high-end multiprocessor server machines, because a " +"multi-threaded Python program effectively only uses one CPU, due to the " +"insistence that (almost) all Python code can only run while the GIL is held." +msgstr "" + +#: ../Doc/faq/library.rst:419 +msgid "" +"Back in the days of Python 1.5, Greg Stein actually implemented a " +"comprehensive patch set (the \"free threading\" patches) that removed the " +"GIL and replaced it with fine-grained locking. Adam Olsen recently did a " +"similar experiment in his `python-safethread `_ project. Unfortunately, both experiments exhibited a " +"sharp drop in single-thread performance (at least 30% slower), due to the " +"amount of fine-grained locking necessary to compensate for the removal of " +"the GIL." +msgstr "" + +#: ../Doc/faq/library.rst:427 +msgid "" +"This doesn't mean that you can't make good use of Python on multi-CPU " +"machines! You just have to be creative with dividing the work up between " +"multiple *processes* rather than multiple *threads*. The :class:" +"`~concurrent.futures.ProcessPoolExecutor` class in the new :mod:`concurrent." +"futures` module provides an easy way of doing so; the :mod:`multiprocessing` " +"module provides a lower-level API in case you want more control over " +"dispatching of tasks." +msgstr "" + +#: ../Doc/faq/library.rst:435 +msgid "" +"Judicious use of C extensions will also help; if you use a C extension to " +"perform a time-consuming task, the extension can release the GIL while the " +"thread of execution is in the C code and allow other threads to get some " +"work done. Some standard library modules such as :mod:`zlib` and :mod:" +"`hashlib` already do this." +msgstr "" + +#: ../Doc/faq/library.rst:441 +msgid "" +"It has been suggested that the GIL should be a per-interpreter-state lock " +"rather than truly global; interpreters then wouldn't be able to share " +"objects. Unfortunately, this isn't likely to happen either. It would be a " +"tremendous amount of work, because many object implementations currently " +"have global state. For example, small integers and short strings are cached; " +"these caches would have to be moved to the interpreter state. Other object " +"types have their own free list; these free lists would have to be moved to " +"the interpreter state. And so on." +msgstr "" + +#: ../Doc/faq/library.rst:450 +msgid "" +"And I doubt that it can even be done in finite time, because the same " +"problem exists for 3rd party extensions. It is likely that 3rd party " +"extensions are being written at a faster rate than you can convert them to " +"store all their global state in the interpreter state." +msgstr "" + +#: ../Doc/faq/library.rst:455 +msgid "" +"And finally, once you have multiple interpreters not sharing any state, what " +"have you gained over running each interpreter in a separate process?" +msgstr "" + +#: ../Doc/faq/library.rst:460 +msgid "Input and Output" +msgstr "" + +#: ../Doc/faq/library.rst:463 +msgid "How do I delete a file? (And other file questions...)" +msgstr "" + +#: ../Doc/faq/library.rst:465 +msgid "" +"Use ``os.remove(filename)`` or ``os.unlink(filename)``; for documentation, " +"see the :mod:`os` module. The two functions are identical; :func:`~os." +"unlink` is simply the name of the Unix system call for this function." +msgstr "" + +#: ../Doc/faq/library.rst:469 +msgid "" +"To remove a directory, use :func:`os.rmdir`; use :func:`os.mkdir` to create " +"one. ``os.makedirs(path)`` will create any intermediate directories in " +"``path`` that don't exist. ``os.removedirs(path)`` will remove intermediate " +"directories as long as they're empty; if you want to delete an entire " +"directory tree and its contents, use :func:`shutil.rmtree`." +msgstr "" + +#: ../Doc/faq/library.rst:475 +msgid "To rename a file, use ``os.rename(old_path, new_path)``." +msgstr "" + +#: ../Doc/faq/library.rst:477 +msgid "" +"To truncate a file, open it using ``f = open(filename, \"rb+\")``, and use " +"``f.truncate(offset)``; offset defaults to the current seek position. " +"There's also ``os.ftruncate(fd, offset)`` for files opened with :func:`os." +"open`, where *fd* is the file descriptor (a small integer)." +msgstr "" + +#: ../Doc/faq/library.rst:482 +msgid "" +"The :mod:`shutil` module also contains a number of functions to work on " +"files including :func:`~shutil.copyfile`, :func:`~shutil.copytree`, and :" +"func:`~shutil.rmtree`." +msgstr "" + +#: ../Doc/faq/library.rst:488 +msgid "How do I copy a file?" +msgstr "" + +#: ../Doc/faq/library.rst:490 +msgid "" +"The :mod:`shutil` module contains a :func:`~shutil.copyfile` function. Note " +"that on MacOS 9 it doesn't copy the resource fork and Finder info." +msgstr "" + +#: ../Doc/faq/library.rst:495 +msgid "How do I read (or write) binary data?" +msgstr "" + +#: ../Doc/faq/library.rst:497 +msgid "" +"To read or write complex binary data formats, it's best to use the :mod:" +"`struct` module. It allows you to take a string containing binary data " +"(usually numbers) and convert it to Python objects; and vice versa." +msgstr "" + +#: ../Doc/faq/library.rst:501 +msgid "" +"For example, the following code reads two 2-byte integers and one 4-byte " +"integer in big-endian format from a file::" +msgstr "" + +#: ../Doc/faq/library.rst:510 +msgid "" +"The '>' in the format string forces big-endian data; the letter 'h' reads " +"one \"short integer\" (2 bytes), and 'l' reads one \"long integer\" (4 " +"bytes) from the string." +msgstr "" + +#: ../Doc/faq/library.rst:514 +msgid "" +"For data that is more regular (e.g. a homogeneous list of ints or floats), " +"you can also use the :mod:`array` module." +msgstr "" + +#: ../Doc/faq/library.rst:519 +msgid "" +"To read and write binary data, it is mandatory to open the file in binary " +"mode (here, passing ``\"rb\"`` to :func:`open`). If you use ``\"r\"`` " +"instead (the default), the file will be open in text mode and ``f.read()`` " +"will return :class:`str` objects rather than :class:`bytes` objects." +msgstr "" + +#: ../Doc/faq/library.rst:527 +msgid "I can't seem to use os.read() on a pipe created with os.popen(); why?" +msgstr "" + +#: ../Doc/faq/library.rst:529 +msgid "" +":func:`os.read` is a low-level function which takes a file descriptor, a " +"small integer representing the opened file. :func:`os.popen` creates a high-" +"level file object, the same type returned by the built-in :func:`open` " +"function. Thus, to read *n* bytes from a pipe *p* created with :func:`os." +"popen`, you need to use ``p.read(n)``." +msgstr "" + +#: ../Doc/faq/library.rst:616 +msgid "How do I access the serial (RS232) port?" +msgstr "" + +#: ../Doc/faq/library.rst:618 +msgid "For Win32, POSIX (Linux, BSD, etc.), Jython:" +msgstr "" + +#: ../Doc/faq/library.rst:620 +msgid "http://pyserial.sourceforge.net" +msgstr "" + +#: ../Doc/faq/library.rst:622 +msgid "For Unix, see a Usenet post by Mitch Chapman:" +msgstr "" + +#: ../Doc/faq/library.rst:624 +msgid "https://groups.google.com/groups?selm=34A04430.CF9@ohioee.com" +msgstr "" + +#: ../Doc/faq/library.rst:628 +msgid "Why doesn't closing sys.stdout (stdin, stderr) really close it?" +msgstr "" + +#: ../Doc/faq/library.rst:630 +msgid "" +"Python :term:`file objects ` are a high-level layer of " +"abstraction on low-level C file descriptors." +msgstr "" + +#: ../Doc/faq/library.rst:633 +msgid "" +"For most file objects you create in Python via the built-in :func:`open` " +"function, ``f.close()`` marks the Python file object as being closed from " +"Python's point of view, and also arranges to close the underlying C file " +"descriptor. This also happens automatically in ``f``'s destructor, when " +"``f`` becomes garbage." +msgstr "" + +#: ../Doc/faq/library.rst:639 +msgid "" +"But stdin, stdout and stderr are treated specially by Python, because of the " +"special status also given to them by C. Running ``sys.stdout.close()`` " +"marks the Python-level file object as being closed, but does *not* close the " +"associated C file descriptor." +msgstr "" + +#: ../Doc/faq/library.rst:644 +msgid "" +"To close the underlying C file descriptor for one of these three, you should " +"first be sure that's what you really want to do (e.g., you may confuse " +"extension modules trying to do I/O). If it is, use :func:`os.close`::" +msgstr "" + +#: ../Doc/faq/library.rst:652 +msgid "Or you can use the numeric constants 0, 1 and 2, respectively." +msgstr "" + +#: ../Doc/faq/library.rst:656 +msgid "Network/Internet Programming" +msgstr "" + +#: ../Doc/faq/library.rst:659 +msgid "What WWW tools are there for Python?" +msgstr "" + +#: ../Doc/faq/library.rst:661 +msgid "" +"See the chapters titled :ref:`internet` and :ref:`netdata` in the Library " +"Reference Manual. Python has many modules that will help you build server-" +"side and client-side web systems." +msgstr "" + +#: ../Doc/faq/library.rst:667 +msgid "" +"A summary of available frameworks is maintained by Paul Boddie at https://" +"wiki.python.org/moin/WebProgramming\\ ." +msgstr "" + +#: ../Doc/faq/library.rst:670 +msgid "" +"Cameron Laird maintains a useful set of pages about Python web technologies " +"at http://phaseit.net/claird/comp.lang.python/web_python." +msgstr "" + +#: ../Doc/faq/library.rst:675 +msgid "How can I mimic CGI form submission (METHOD=POST)?" +msgstr "" + +#: ../Doc/faq/library.rst:677 +msgid "" +"I would like to retrieve web pages that are the result of POSTing a form. Is " +"there existing code that would let me do this easily?" +msgstr "" + +#: ../Doc/faq/library.rst:680 +msgid "Yes. Here's a simple example that uses urllib.request::" +msgstr "" + +#: ../Doc/faq/library.rst:695 +msgid "" +"Note that in general for percent-encoded POST operations, query strings must " +"be quoted using :func:`urllib.parse.urlencode`. For example, to send " +"``name=Guy Steele, Jr.``::" +msgstr "" + +#: ../Doc/faq/library.rst:703 +msgid ":ref:`urllib-howto` for extensive examples." +msgstr "" + +#: ../Doc/faq/library.rst:707 +msgid "What module should I use to help with generating HTML?" +msgstr "" + +#: ../Doc/faq/library.rst:711 +msgid "" +"You can find a collection of useful links on the `Web Programming wiki page " +"`_." +msgstr "" + +#: ../Doc/faq/library.rst:716 +msgid "How do I send mail from a Python script?" +msgstr "" + +#: ../Doc/faq/library.rst:718 +msgid "Use the standard library module :mod:`smtplib`." +msgstr "" + +#: ../Doc/faq/library.rst:720 +msgid "" +"Here's a very simple interactive mail sender that uses it. This method will " +"work on any host that supports an SMTP listener. ::" +msgstr "" + +#: ../Doc/faq/library.rst:740 +msgid "" +"A Unix-only alternative uses sendmail. The location of the sendmail program " +"varies between systems; sometimes it is ``/usr/lib/sendmail``, sometimes ``/" +"usr/sbin/sendmail``. The sendmail manual page will help you out. Here's " +"some sample code::" +msgstr "" + +#: ../Doc/faq/library.rst:760 +msgid "How do I avoid blocking in the connect() method of a socket?" +msgstr "" + +#: ../Doc/faq/library.rst:762 +msgid "" +"The :mod:`select` module is commonly used to help with asynchronous I/O on " +"sockets." +msgstr "" + +#: ../Doc/faq/library.rst:765 +msgid "" +"To prevent the TCP connect from blocking, you can set the socket to non-" +"blocking mode. Then when you do the ``connect()``, you will either connect " +"immediately (unlikely) or get an exception that contains the error number as " +"``.errno``. ``errno.EINPROGRESS`` indicates that the connection is in " +"progress, but hasn't finished yet. Different OSes will return different " +"values, so you're going to have to check what's returned on your system." +msgstr "" + +#: ../Doc/faq/library.rst:772 +msgid "" +"You can use the ``connect_ex()`` method to avoid creating an exception. It " +"will just return the errno value. To poll, you can call ``connect_ex()`` " +"again later -- ``0`` or ``errno.EISCONN`` indicate that you're connected -- " +"or you can pass this socket to select to check if it's writable." +msgstr "" + +#: ../Doc/faq/library.rst:778 +msgid "" +"The :mod:`asyncore` module presents a framework-like approach to the problem " +"of writing non-blocking networking code. The third-party `Twisted `_ library is a popular and feature-rich alternative." +msgstr "" + +#: ../Doc/faq/library.rst:785 +msgid "Databases" +msgstr "" + +#: ../Doc/faq/library.rst:788 +msgid "Are there any interfaces to database packages in Python?" +msgstr "" + +#: ../Doc/faq/library.rst:792 +msgid "" +"Interfaces to disk-based hashes such as :mod:`DBM ` and :mod:`GDBM " +"` are also included with standard Python. There is also the :mod:" +"`sqlite3` module, which provides a lightweight disk-based relational " +"database." +msgstr "" + +#: ../Doc/faq/library.rst:797 +msgid "" +"Support for most relational databases is available. See the " +"`DatabaseProgramming wiki page `_ for details." +msgstr "" + +#: ../Doc/faq/library.rst:803 +msgid "How do you implement persistent objects in Python?" +msgstr "" + +#: ../Doc/faq/library.rst:805 +msgid "" +"The :mod:`pickle` library module solves this in a very general way (though " +"you still can't store things like open files, sockets or windows), and the :" +"mod:`shelve` library module uses pickle and (g)dbm to create persistent " +"mappings containing arbitrary Python objects." +msgstr "" + +#: ../Doc/faq/library.rst:812 +msgid "Mathematics and Numerics" +msgstr "" + +#: ../Doc/faq/library.rst:815 +msgid "How do I generate random numbers in Python?" +msgstr "" + +#: ../Doc/faq/library.rst:817 +msgid "" +"The standard module :mod:`random` implements a random number generator. " +"Usage is simple::" +msgstr "" + +#: ../Doc/faq/library.rst:823 +msgid "This returns a random floating point number in the range [0, 1)." +msgstr "" + +#: ../Doc/faq/library.rst:825 +msgid "" +"There are also many other specialized generators in this module, such as:" +msgstr "" + +#: ../Doc/faq/library.rst:827 +msgid "``randrange(a, b)`` chooses an integer in the range [a, b)." +msgstr "" + +#: ../Doc/faq/library.rst:828 +msgid "``uniform(a, b)`` chooses a floating point number in the range [a, b)." +msgstr "" + +#: ../Doc/faq/library.rst:829 +msgid "" +"``normalvariate(mean, sdev)`` samples the normal (Gaussian) distribution." +msgstr "" + +#: ../Doc/faq/library.rst:831 +msgid "Some higher-level functions operate on sequences directly, such as:" +msgstr "" + +#: ../Doc/faq/library.rst:833 +msgid "``choice(S)`` chooses random element from a given sequence" +msgstr "" + +#: ../Doc/faq/library.rst:834 +msgid "``shuffle(L)`` shuffles a list in-place, i.e. permutes it randomly" +msgstr "" + +#: ../Doc/faq/library.rst:836 +msgid "" +"There's also a ``Random`` class you can instantiate to create independent " +"multiple random number generators." +msgstr "" + +#: ../Doc/faq/programming.rst:5 +msgid "Programming FAQ" +msgstr "" + +#: ../Doc/faq/programming.rst:12 +msgid "General Questions" +msgstr "" + +#: ../Doc/faq/programming.rst:15 +msgid "" +"Is there a source code level debugger with breakpoints, single-stepping, " +"etc.?" +msgstr "" + +#: ../Doc/faq/programming.rst:19 +msgid "" +"The pdb module is a simple but adequate console-mode debugger for Python. It " +"is part of the standard Python library, and is :mod:`documented in the " +"Library Reference Manual `. You can also write your own debugger by " +"using the code for pdb as an example." +msgstr "" + +#: ../Doc/faq/programming.rst:24 +msgid "" +"The IDLE interactive development environment, which is part of the standard " +"Python distribution (normally available as Tools/scripts/idle), includes a " +"graphical debugger." +msgstr "" + +#: ../Doc/faq/programming.rst:28 +msgid "" +"PythonWin is a Python IDE that includes a GUI debugger based on pdb. The " +"Pythonwin debugger colors breakpoints and has quite a few cool features such " +"as debugging non-Pythonwin programs. Pythonwin is available as part of the " +"`Python for Windows Extensions `__ project and as a part of the ActivePython distribution (see https://www." +"activestate.com/activepython\\ )." +msgstr "" + +#: ../Doc/faq/programming.rst:35 +msgid "" +"`Boa Constructor `_ is an IDE and " +"GUI builder that uses wxWidgets. It offers visual frame creation and " +"manipulation, an object inspector, many views on the source like object " +"browsers, inheritance hierarchies, doc string generated html documentation, " +"an advanced debugger, integrated help, and Zope support." +msgstr "" + +#: ../Doc/faq/programming.rst:41 +msgid "" +"`Eric `_ is an IDE built on PyQt and " +"the Scintilla editing component." +msgstr "" + +#: ../Doc/faq/programming.rst:44 +msgid "" +"Pydb is a version of the standard Python debugger pdb, modified for use with " +"DDD (Data Display Debugger), a popular graphical debugger front end. Pydb " +"can be found at http://bashdb.sourceforge.net/pydb/ and DDD can be found at " +"https://www.gnu.org/software/ddd." +msgstr "" + +#: ../Doc/faq/programming.rst:49 +msgid "" +"There are a number of commercial Python IDEs that include graphical " +"debuggers. They include:" +msgstr "" + +#: ../Doc/faq/programming.rst:52 +msgid "Wing IDE (https://wingware.com/)" +msgstr "" + +#: ../Doc/faq/programming.rst:53 +msgid "Komodo IDE (https://komodoide.com/)" +msgstr "" + +#: ../Doc/faq/programming.rst:54 +msgid "PyCharm (https://www.jetbrains.com/pycharm/)" +msgstr "" + +#: ../Doc/faq/programming.rst:58 +msgid "Is there a tool to help find bugs or perform static analysis?" +msgstr "" + +#: ../Doc/faq/programming.rst:62 +msgid "" +"PyChecker is a static analysis tool that finds bugs in Python source code " +"and warns about code complexity and style. You can get PyChecker from " +"http://pychecker.sourceforge.net/." +msgstr "" + +#: ../Doc/faq/programming.rst:66 +msgid "" +"`Pylint `_ is another tool that checks if a module " +"satisfies a coding standard, and also makes it possible to write plug-ins to " +"add a custom feature. In addition to the bug checking that PyChecker " +"performs, Pylint offers some additional features such as checking line " +"length, whether variable names are well-formed according to your coding " +"standard, whether declared interfaces are fully implemented, and more. " +"https://docs.pylint.org/ provides a full list of Pylint's features." +msgstr "" + +#: ../Doc/faq/programming.rst:76 +msgid "How can I create a stand-alone binary from a Python script?" +msgstr "" + +#: ../Doc/faq/programming.rst:78 +msgid "" +"You don't need the ability to compile Python to C code if all you want is a " +"stand-alone program that users can download and run without having to " +"install the Python distribution first. There are a number of tools that " +"determine the set of modules required by a program and bind these modules " +"together with a Python binary to produce a single executable." +msgstr "" + +#: ../Doc/faq/programming.rst:84 +msgid "" +"One is to use the freeze tool, which is included in the Python source tree " +"as ``Tools/freeze``. It converts Python byte code to C arrays; a C compiler " +"you can embed all your modules into a new program, which is then linked with " +"the standard Python modules." +msgstr "" + +#: ../Doc/faq/programming.rst:89 +msgid "" +"It works by scanning your source recursively for import statements (in both " +"forms) and looking for the modules in the standard Python path as well as in " +"the source directory (for built-in modules). It then turns the bytecode for " +"modules written in Python into C code (array initializers that can be turned " +"into code objects using the marshal module) and creates a custom-made config " +"file that only contains those built-in modules which are actually used in " +"the program. It then compiles the generated C code and links it with the " +"rest of the Python interpreter to form a self-contained binary which acts " +"exactly like your script." +msgstr "" + +#: ../Doc/faq/programming.rst:98 +msgid "" +"Obviously, freeze requires a C compiler. There are several other utilities " +"which don't. One is Thomas Heller's py2exe (Windows only) at" +msgstr "" + +#: ../Doc/faq/programming.rst:101 +msgid "http://www.py2exe.org/" +msgstr "" + +#: ../Doc/faq/programming.rst:103 +msgid "" +"Another tool is Anthony Tuininga's `cx_Freeze `_." +msgstr "" + +#: ../Doc/faq/programming.rst:107 +msgid "Are there coding standards or a style guide for Python programs?" +msgstr "" + +#: ../Doc/faq/programming.rst:109 +msgid "" +"Yes. The coding style required for standard library modules is documented " +"as :pep:`8`." +msgstr "" + +#: ../Doc/faq/programming.rst:114 +msgid "Core Language" +msgstr "" + +#: ../Doc/faq/programming.rst:117 +msgid "Why am I getting an UnboundLocalError when the variable has a value?" +msgstr "" + +#: ../Doc/faq/programming.rst:119 +msgid "" +"It can be a surprise to get the UnboundLocalError in previously working code " +"when it is modified by adding an assignment statement somewhere in the body " +"of a function." +msgstr "" + +#: ../Doc/faq/programming.rst:123 +msgid "This code:" +msgstr "" + +#: ../Doc/faq/programming.rst:131 +msgid "works, but this code:" +msgstr "" + +#: ../Doc/faq/programming.rst:138 +msgid "results in an UnboundLocalError:" +msgstr "" + +#: ../Doc/faq/programming.rst:145 +msgid "" +"This is because when you make an assignment to a variable in a scope, that " +"variable becomes local to that scope and shadows any similarly named " +"variable in the outer scope. Since the last statement in foo assigns a new " +"value to ``x``, the compiler recognizes it as a local variable. " +"Consequently when the earlier ``print(x)`` attempts to print the " +"uninitialized local variable and an error results." +msgstr "" + +#: ../Doc/faq/programming.rst:152 +msgid "" +"In the example above you can access the outer scope variable by declaring it " +"global:" +msgstr "" + +#: ../Doc/faq/programming.rst:163 +msgid "" +"This explicit declaration is required in order to remind you that (unlike " +"the superficially analogous situation with class and instance variables) you " +"are actually modifying the value of the variable in the outer scope:" +msgstr "" + +#: ../Doc/faq/programming.rst:170 +msgid "" +"You can do a similar thing in a nested scope using the :keyword:`nonlocal` " +"keyword:" +msgstr "" + +#: ../Doc/faq/programming.rst:187 +msgid "What are the rules for local and global variables in Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:189 +msgid "" +"In Python, variables that are only referenced inside a function are " +"implicitly global. If a variable is assigned a value anywhere within the " +"function's body, it's assumed to be a local unless explicitly declared as " +"global." +msgstr "" + +#: ../Doc/faq/programming.rst:193 +msgid "" +"Though a bit surprising at first, a moment's consideration explains this. " +"On one hand, requiring :keyword:`global` for assigned variables provides a " +"bar against unintended side-effects. On the other hand, if ``global`` was " +"required for all global references, you'd be using ``global`` all the time. " +"You'd have to declare as global every reference to a built-in function or to " +"a component of an imported module. This clutter would defeat the usefulness " +"of the ``global`` declaration for identifying side-effects." +msgstr "" + +#: ../Doc/faq/programming.rst:203 +msgid "" +"Why do lambdas defined in a loop with different values all return the same " +"result?" +msgstr "" + +#: ../Doc/faq/programming.rst:205 +msgid "" +"Assume you use a for loop to define a few different lambdas (or even plain " +"functions), e.g.::" +msgstr "" + +#: ../Doc/faq/programming.rst:212 +msgid "" +"This gives you a list that contains 5 lambdas that calculate ``x**2``. You " +"might expect that, when called, they would return, respectively, ``0``, " +"``1``, ``4``, ``9``, and ``16``. However, when you actually try you will " +"see that they all return ``16``::" +msgstr "" + +#: ../Doc/faq/programming.rst:222 +msgid "" +"This happens because ``x`` is not local to the lambdas, but is defined in " +"the outer scope, and it is accessed when the lambda is called --- not when " +"it is defined. At the end of the loop, the value of ``x`` is ``4``, so all " +"the functions now return ``4**2``, i.e. ``16``. You can also verify this by " +"changing the value of ``x`` and see how the results of the lambdas change::" +msgstr "" + +#: ../Doc/faq/programming.rst:232 +msgid "" +"In order to avoid this, you need to save the values in variables local to " +"the lambdas, so that they don't rely on the value of the global ``x``::" +msgstr "" + +#: ../Doc/faq/programming.rst:239 +msgid "" +"Here, ``n=x`` creates a new variable ``n`` local to the lambda and computed " +"when the lambda is defined so that it has the same value that ``x`` had at " +"that point in the loop. This means that the value of ``n`` will be ``0`` in " +"the first lambda, ``1`` in the second, ``2`` in the third, and so on. " +"Therefore each lambda will now return the correct result::" +msgstr "" + +#: ../Doc/faq/programming.rst:250 +msgid "" +"Note that this behaviour is not peculiar to lambdas, but applies to regular " +"functions too." +msgstr "" + +#: ../Doc/faq/programming.rst:255 +msgid "How do I share global variables across modules?" +msgstr "" + +#: ../Doc/faq/programming.rst:257 +msgid "" +"The canonical way to share information across modules within a single " +"program is to create a special module (often called config or cfg). Just " +"import the config module in all modules of your application; the module then " +"becomes available as a global name. Because there is only one instance of " +"each module, any changes made to the module object get reflected " +"everywhere. For example:" +msgstr "" + +#: ../Doc/faq/programming.rst:263 +msgid "config.py::" +msgstr "" + +#: ../Doc/faq/programming.rst:267 +msgid "mod.py::" +msgstr "" + +#: ../Doc/faq/programming.rst:272 +msgid "main.py::" +msgstr "" + +#: ../Doc/faq/programming.rst:278 +msgid "" +"Note that using a module is also the basis for implementing the Singleton " +"design pattern, for the same reason." +msgstr "" + +#: ../Doc/faq/programming.rst:283 +msgid "What are the \"best practices\" for using import in a module?" +msgstr "" + +#: ../Doc/faq/programming.rst:285 +msgid "" +"In general, don't use ``from modulename import *``. Doing so clutters the " +"importer's namespace, and makes it much harder for linters to detect " +"undefined names." +msgstr "" + +#: ../Doc/faq/programming.rst:289 +msgid "" +"Import modules at the top of a file. Doing so makes it clear what other " +"modules your code requires and avoids questions of whether the module name " +"is in scope. Using one import per line makes it easy to add and delete " +"module imports, but using multiple imports per line uses less screen space." +msgstr "" + +#: ../Doc/faq/programming.rst:294 +msgid "It's good practice if you import modules in the following order:" +msgstr "" + +#: ../Doc/faq/programming.rst:296 +msgid "standard library modules -- e.g. ``sys``, ``os``, ``getopt``, ``re``" +msgstr "" + +#: ../Doc/faq/programming.rst:297 +msgid "" +"third-party library modules (anything installed in Python's site-packages " +"directory) -- e.g. mx.DateTime, ZODB, PIL.Image, etc." +msgstr "" + +#: ../Doc/faq/programming.rst:299 +msgid "locally-developed modules" +msgstr "" + +#: ../Doc/faq/programming.rst:301 +msgid "" +"It is sometimes necessary to move imports to a function or class to avoid " +"problems with circular imports. Gordon McMillan says:" +msgstr "" + +#: ../Doc/faq/programming.rst:304 +msgid "" +"Circular imports are fine where both modules use the \"import \" " +"form of import. They fail when the 2nd module wants to grab a name out of " +"the first (\"from module import name\") and the import is at the top level. " +"That's because names in the 1st are not yet available, because the first " +"module is busy importing the 2nd." +msgstr "" + +#: ../Doc/faq/programming.rst:310 +msgid "" +"In this case, if the second module is only used in one function, then the " +"import can easily be moved into that function. By the time the import is " +"called, the first module will have finished initializing, and the second " +"module can do its import." +msgstr "" + +#: ../Doc/faq/programming.rst:315 +msgid "" +"It may also be necessary to move imports out of the top level of code if " +"some of the modules are platform-specific. In that case, it may not even be " +"possible to import all of the modules at the top of the file. In this case, " +"importing the correct modules in the corresponding platform-specific code is " +"a good option." +msgstr "" + +#: ../Doc/faq/programming.rst:320 +msgid "" +"Only move imports into a local scope, such as inside a function definition, " +"if it's necessary to solve a problem such as avoiding a circular import or " +"are trying to reduce the initialization time of a module. This technique is " +"especially helpful if many of the imports are unnecessary depending on how " +"the program executes. You may also want to move imports into a function if " +"the modules are only ever used in that function. Note that loading a module " +"the first time may be expensive because of the one time initialization of " +"the module, but loading a module multiple times is virtually free, costing " +"only a couple of dictionary lookups. Even if the module name has gone out " +"of scope, the module is probably available in :data:`sys.modules`." +msgstr "" + +#: ../Doc/faq/programming.rst:333 +msgid "Why are default values shared between objects?" +msgstr "" + +#: ../Doc/faq/programming.rst:335 +msgid "" +"This type of bug commonly bites neophyte programmers. Consider this " +"function::" +msgstr "" + +#: ../Doc/faq/programming.rst:342 +msgid "" +"The first time you call this function, ``mydict`` contains a single item. " +"The second time, ``mydict`` contains two items because when ``foo()`` begins " +"executing, ``mydict`` starts out with an item already in it." +msgstr "" + +#: ../Doc/faq/programming.rst:346 +msgid "" +"It is often expected that a function call creates new objects for default " +"values. This is not what happens. Default values are created exactly once, " +"when the function is defined. If that object is changed, like the " +"dictionary in this example, subsequent calls to the function will refer to " +"this changed object." +msgstr "" + +#: ../Doc/faq/programming.rst:351 +msgid "" +"By definition, immutable objects such as numbers, strings, tuples, and " +"``None``, are safe from change. Changes to mutable objects such as " +"dictionaries, lists, and class instances can lead to confusion." +msgstr "" + +#: ../Doc/faq/programming.rst:355 +msgid "" +"Because of this feature, it is good programming practice to not use mutable " +"objects as default values. Instead, use ``None`` as the default value and " +"inside the function, check if the parameter is ``None`` and create a new " +"list/dictionary/whatever if it is. For example, don't write::" +msgstr "" + +#: ../Doc/faq/programming.rst:363 +msgid "but::" +msgstr "" + +#: ../Doc/faq/programming.rst:369 +msgid "" +"This feature can be useful. When you have a function that's time-consuming " +"to compute, a common technique is to cache the parameters and the resulting " +"value of each call to the function, and return the cached value if the same " +"value is requested again. This is called \"memoizing\", and can be " +"implemented like this::" +msgstr "" + +#: ../Doc/faq/programming.rst:384 +msgid "" +"You could use a global variable containing a dictionary instead of the " +"default value; it's a matter of taste." +msgstr "" + +#: ../Doc/faq/programming.rst:389 +msgid "" +"How can I pass optional or keyword parameters from one function to another?" +msgstr "" + +#: ../Doc/faq/programming.rst:391 +msgid "" +"Collect the arguments using the ``*`` and ``**`` specifiers in the " +"function's parameter list; this gives you the positional arguments as a " +"tuple and the keyword arguments as a dictionary. You can then pass these " +"arguments when calling another function by using ``*`` and ``**``::" +msgstr "" + +#: ../Doc/faq/programming.rst:410 +msgid "What is the difference between arguments and parameters?" +msgstr "" + +#: ../Doc/faq/programming.rst:412 +msgid "" +":term:`Parameters ` are defined by the names that appear in a " +"function definition, whereas :term:`arguments ` are the values " +"actually passed to a function when calling it. Parameters define what types " +"of arguments a function can accept. For example, given the function " +"definition::" +msgstr "" + +#: ../Doc/faq/programming.rst:420 +msgid "" +"*foo*, *bar* and *kwargs* are parameters of ``func``. However, when calling " +"``func``, for example::" +msgstr "" + +#: ../Doc/faq/programming.rst:425 +msgid "the values ``42``, ``314``, and ``somevar`` are arguments." +msgstr "" + +#: ../Doc/faq/programming.rst:429 +msgid "Why did changing list 'y' also change list 'x'?" +msgstr "" + +#: ../Doc/faq/programming.rst:431 +msgid "If you wrote code like::" +msgstr "" + +#: ../Doc/faq/programming.rst:441 +msgid "" +"you might be wondering why appending an element to ``y`` changed ``x`` too." +msgstr "" + +#: ../Doc/faq/programming.rst:443 +msgid "There are two factors that produce this result:" +msgstr "" + +#: ../Doc/faq/programming.rst:445 +msgid "" +"Variables are simply names that refer to objects. Doing ``y = x`` doesn't " +"create a copy of the list -- it creates a new variable ``y`` that refers to " +"the same object ``x`` refers to. This means that there is only one object " +"(the list), and both ``x`` and ``y`` refer to it." +msgstr "" + +#: ../Doc/faq/programming.rst:449 +msgid "" +"Lists are :term:`mutable`, which means that you can change their content." +msgstr "" + +#: ../Doc/faq/programming.rst:451 +msgid "" +"After the call to :meth:`~list.append`, the content of the mutable object " +"has changed from ``[]`` to ``[10]``. Since both the variables refer to the " +"same object, using either name accesses the modified value ``[10]``." +msgstr "" + +#: ../Doc/faq/programming.rst:455 +msgid "If we instead assign an immutable object to ``x``::" +msgstr "" + +#: ../Doc/faq/programming.rst:465 +msgid "" +"we can see that in this case ``x`` and ``y`` are not equal anymore. This is " +"because integers are :term:`immutable`, and when we do ``x = x + 1`` we are " +"not mutating the int ``5`` by incrementing its value; instead, we are " +"creating a new object (the int ``6``) and assigning it to ``x`` (that is, " +"changing which object ``x`` refers to). After this assignment we have two " +"objects (the ints ``6`` and ``5``) and two variables that refer to them " +"(``x`` now refers to ``6`` but ``y`` still refers to ``5``)." +msgstr "" + +#: ../Doc/faq/programming.rst:473 +msgid "" +"Some operations (for example ``y.append(10)`` and ``y.sort()``) mutate the " +"object, whereas superficially similar operations (for example ``y = y + " +"[10]`` and ``sorted(y)``) create a new object. In general in Python (and in " +"all cases in the standard library) a method that mutates an object will " +"return ``None`` to help avoid getting the two types of operations confused. " +"So if you mistakenly write ``y.sort()`` thinking it will give you a sorted " +"copy of ``y``, you'll instead end up with ``None``, which will likely cause " +"your program to generate an easily diagnosed error." +msgstr "" + +#: ../Doc/faq/programming.rst:482 +msgid "" +"However, there is one class of operations where the same operation sometimes " +"has different behaviors with different types: the augmented assignment " +"operators. For example, ``+=`` mutates lists but not tuples or ints " +"(``a_list += [1, 2, 3]`` is equivalent to ``a_list.extend([1, 2, 3])`` and " +"mutates ``a_list``, whereas ``some_tuple += (1, 2, 3)`` and ``some_int += " +"1`` create new objects)." +msgstr "" + +#: ../Doc/faq/programming.rst:489 +msgid "In other words:" +msgstr "" + +#: ../Doc/faq/programming.rst:491 +msgid "" +"If we have a mutable object (:class:`list`, :class:`dict`, :class:`set`, " +"etc.), we can use some specific operations to mutate it and all the " +"variables that refer to it will see the change." +msgstr "" + +#: ../Doc/faq/programming.rst:494 +msgid "" +"If we have an immutable object (:class:`str`, :class:`int`, :class:`tuple`, " +"etc.), all the variables that refer to it will always see the same value, " +"but operations that transform that value into a new value always return a " +"new object." +msgstr "" + +#: ../Doc/faq/programming.rst:499 +msgid "" +"If you want to know if two variables refer to the same object or not, you " +"can use the :keyword:`is` operator, or the built-in function :func:`id`." +msgstr "" + +#: ../Doc/faq/programming.rst:504 +msgid "How do I write a function with output parameters (call by reference)?" +msgstr "" + +#: ../Doc/faq/programming.rst:506 +msgid "" +"Remember that arguments are passed by assignment in Python. Since " +"assignment just creates references to objects, there's no alias between an " +"argument name in the caller and callee, and so no call-by-reference per se. " +"You can achieve the desired effect in a number of ways." +msgstr "" + +#: ../Doc/faq/programming.rst:511 +msgid "By returning a tuple of the results::" +msgstr "" + +#: ../Doc/faq/programming.rst:522 +msgid "This is almost always the clearest solution." +msgstr "" + +#: ../Doc/faq/programming.rst:524 +msgid "" +"By using global variables. This isn't thread-safe, and is not recommended." +msgstr "" + +#: ../Doc/faq/programming.rst:526 +msgid "By passing a mutable (changeable in-place) object::" +msgstr "" + +#: ../Doc/faq/programming.rst:536 +msgid "By passing in a dictionary that gets mutated::" +msgstr "" + +#: ../Doc/faq/programming.rst:546 +msgid "Or bundle up values in a class instance::" +msgstr "" + +#: ../Doc/faq/programming.rst:562 +msgid "There's almost never a good reason to get this complicated." +msgstr "" + +#: ../Doc/faq/programming.rst:564 +msgid "Your best choice is to return a tuple containing the multiple results." +msgstr "" + +#: ../Doc/faq/programming.rst:568 +msgid "How do you make a higher order function in Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:570 +msgid "" +"You have two choices: you can use nested scopes or you can use callable " +"objects. For example, suppose you wanted to define ``linear(a,b)`` which " +"returns a function ``f(x)`` that computes the value ``a*x+b``. Using nested " +"scopes::" +msgstr "" + +#: ../Doc/faq/programming.rst:579 +msgid "Or using a callable object::" +msgstr "" + +#: ../Doc/faq/programming.rst:589 +msgid "In both cases, ::" +msgstr "" + +#: ../Doc/faq/programming.rst:593 +msgid "gives a callable object where ``taxes(10e6) == 0.3 * 10e6 + 2``." +msgstr "" + +#: ../Doc/faq/programming.rst:595 +msgid "" +"The callable object approach has the disadvantage that it is a bit slower " +"and results in slightly longer code. However, note that a collection of " +"callables can share their signature via inheritance::" +msgstr "" + +#: ../Doc/faq/programming.rst:604 +msgid "Object can encapsulate state for several methods::" +msgstr "" + +#: ../Doc/faq/programming.rst:622 +msgid "" +"Here ``inc()``, ``dec()`` and ``reset()`` act like functions which share the " +"same counting variable." +msgstr "" + +#: ../Doc/faq/programming.rst:627 +msgid "How do I copy an object in Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:629 +msgid "" +"In general, try :func:`copy.copy` or :func:`copy.deepcopy` for the general " +"case. Not all objects can be copied, but most can." +msgstr "" + +#: ../Doc/faq/programming.rst:632 +msgid "" +"Some objects can be copied more easily. Dictionaries have a :meth:`~dict." +"copy` method::" +msgstr "" + +#: ../Doc/faq/programming.rst:637 +msgid "Sequences can be copied by slicing::" +msgstr "" + +#: ../Doc/faq/programming.rst:643 +msgid "How can I find the methods or attributes of an object?" +msgstr "" + +#: ../Doc/faq/programming.rst:645 +msgid "" +"For an instance x of a user-defined class, ``dir(x)`` returns an " +"alphabetized list of the names containing the instance attributes and " +"methods and attributes defined by its class." +msgstr "" + +#: ../Doc/faq/programming.rst:651 +msgid "How can my code discover the name of an object?" +msgstr "" + +#: ../Doc/faq/programming.rst:653 +msgid "" +"Generally speaking, it can't, because objects don't really have names. " +"Essentially, assignment always binds a name to a value; The same is true of " +"``def`` and ``class`` statements, but in that case the value is a callable. " +"Consider the following code::" +msgstr "" + +#: ../Doc/faq/programming.rst:669 +msgid "" +"Arguably the class has a name: even though it is bound to two names and " +"invoked through the name B the created instance is still reported as an " +"instance of class A. However, it is impossible to say whether the " +"instance's name is a or b, since both names are bound to the same value." +msgstr "" + +#: ../Doc/faq/programming.rst:674 +msgid "" +"Generally speaking it should not be necessary for your code to \"know the " +"names\" of particular values. Unless you are deliberately writing " +"introspective programs, this is usually an indication that a change of " +"approach might be beneficial." +msgstr "" + +#: ../Doc/faq/programming.rst:679 +msgid "" +"In comp.lang.python, Fredrik Lundh once gave an excellent analogy in answer " +"to this question:" +msgstr "" + +#: ../Doc/faq/programming.rst:682 +msgid "" +"The same way as you get the name of that cat you found on your porch: the " +"cat (object) itself cannot tell you its name, and it doesn't really care -- " +"so the only way to find out what it's called is to ask all your neighbours " +"(namespaces) if it's their cat (object)..." +msgstr "" + +#: ../Doc/faq/programming.rst:687 +msgid "" +"....and don't be surprised if you'll find that it's known by many names, or " +"no name at all!" +msgstr "" + +#: ../Doc/faq/programming.rst:692 +msgid "What's up with the comma operator's precedence?" +msgstr "" + +#: ../Doc/faq/programming.rst:694 +msgid "Comma is not an operator in Python. Consider this session::" +msgstr "" + +#: ../Doc/faq/programming.rst:699 +msgid "" +"Since the comma is not an operator, but a separator between expressions the " +"above is evaluated as if you had entered::" +msgstr "" + +#: ../Doc/faq/programming.rst:704 +msgid "not::" +msgstr "" + +#: ../Doc/faq/programming.rst:708 +msgid "" +"The same is true of the various assignment operators (``=``, ``+=`` etc). " +"They are not truly operators but syntactic delimiters in assignment " +"statements." +msgstr "" + +#: ../Doc/faq/programming.rst:713 +msgid "Is there an equivalent of C's \"?:\" ternary operator?" +msgstr "" + +#: ../Doc/faq/programming.rst:715 +msgid "Yes, there is. The syntax is as follows::" +msgstr "" + +#: ../Doc/faq/programming.rst:722 +msgid "" +"Before this syntax was introduced in Python 2.5, a common idiom was to use " +"logical operators::" +msgstr "" + +#: ../Doc/faq/programming.rst:727 +msgid "" +"However, this idiom is unsafe, as it can give wrong results when *on_true* " +"has a false boolean value. Therefore, it is always better to use the ``... " +"if ... else ...`` form." +msgstr "" + +#: ../Doc/faq/programming.rst:733 +msgid "Is it possible to write obfuscated one-liners in Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:735 +msgid "" +"Yes. Usually this is done by nesting :keyword:`lambda` within :keyword:" +"`lambda`. See the following three examples, due to Ulf Bartelt::" +msgstr "" + +#: ../Doc/faq/programming.rst:762 +msgid "Don't try this at home, kids!" +msgstr "" + +#: ../Doc/faq/programming.rst:766 +msgid "Numbers and strings" +msgstr "" + +#: ../Doc/faq/programming.rst:769 +msgid "How do I specify hexadecimal and octal integers?" +msgstr "" + +#: ../Doc/faq/programming.rst:771 +msgid "" +"To specify an octal digit, precede the octal value with a zero, and then a " +"lower or uppercase \"o\". For example, to set the variable \"a\" to the " +"octal value \"10\" (8 in decimal), type::" +msgstr "" + +#: ../Doc/faq/programming.rst:779 +msgid "" +"Hexadecimal is just as easy. Simply precede the hexadecimal number with a " +"zero, and then a lower or uppercase \"x\". Hexadecimal digits can be " +"specified in lower or uppercase. For example, in the Python interpreter::" +msgstr "" + +#: ../Doc/faq/programming.rst:792 +msgid "Why does -22 // 10 return -3?" +msgstr "" + +#: ../Doc/faq/programming.rst:794 +msgid "" +"It's primarily driven by the desire that ``i % j`` have the same sign as " +"``j``. If you want that, and also want::" +msgstr "" + +#: ../Doc/faq/programming.rst:799 +msgid "" +"then integer division has to return the floor. C also requires that " +"identity to hold, and then compilers that truncate ``i // j`` need to make " +"``i % j`` have the same sign as ``i``." +msgstr "" + +#: ../Doc/faq/programming.rst:803 +msgid "" +"There are few real use cases for ``i % j`` when ``j`` is negative. When " +"``j`` is positive, there are many, and in virtually all of them it's more " +"useful for ``i % j`` to be ``>= 0``. If the clock says 10 now, what did it " +"say 200 hours ago? ``-190 % 12 == 2`` is useful; ``-190 % 12 == -10`` is a " +"bug waiting to bite." +msgstr "" + +#: ../Doc/faq/programming.rst:811 +msgid "How do I convert a string to a number?" +msgstr "" + +#: ../Doc/faq/programming.rst:813 +msgid "" +"For integers, use the built-in :func:`int` type constructor, e.g. " +"``int('144') == 144``. Similarly, :func:`float` converts to floating-point, " +"e.g. ``float('144') == 144.0``." +msgstr "" + +#: ../Doc/faq/programming.rst:817 +msgid "" +"By default, these interpret the number as decimal, so that ``int('0144') == " +"144`` and ``int('0x144')`` raises :exc:`ValueError`. ``int(string, base)`` " +"takes the base to convert from as a second optional argument, so " +"``int('0x144', 16) == 324``. If the base is specified as 0, the number is " +"interpreted using Python's rules: a leading '0o' indicates octal, and '0x' " +"indicates a hex number." +msgstr "" + +#: ../Doc/faq/programming.rst:823 +msgid "" +"Do not use the built-in function :func:`eval` if all you need is to convert " +"strings to numbers. :func:`eval` will be significantly slower and it " +"presents a security risk: someone could pass you a Python expression that " +"might have unwanted side effects. For example, someone could pass " +"``__import__('os').system(\"rm -rf $HOME\")`` which would erase your home " +"directory." +msgstr "" + +#: ../Doc/faq/programming.rst:830 +msgid "" +":func:`eval` also has the effect of interpreting numbers as Python " +"expressions, so that e.g. ``eval('09')`` gives a syntax error because Python " +"does not allow leading '0' in a decimal number (except '0')." +msgstr "" + +#: ../Doc/faq/programming.rst:836 +msgid "How do I convert a number to a string?" +msgstr "" + +#: ../Doc/faq/programming.rst:838 +msgid "" +"To convert, e.g., the number 144 to the string '144', use the built-in type " +"constructor :func:`str`. If you want a hexadecimal or octal representation, " +"use the built-in functions :func:`hex` or :func:`oct`. For fancy " +"formatting, see the :ref:`f-strings` and :ref:`formatstrings` sections, e.g. " +"``\"{:04d}\".format(144)`` yields ``'0144'`` and ``\"{:.3f}\"." +"format(1.0/3.0)`` yields ``'0.333'``." +msgstr "" + +#: ../Doc/faq/programming.rst:847 +msgid "How do I modify a string in place?" +msgstr "" + +#: ../Doc/faq/programming.rst:849 +msgid "" +"You can't, because strings are immutable. In most situations, you should " +"simply construct a new string from the various parts you want to assemble it " +"from. However, if you need an object with the ability to modify in-place " +"unicode data, try using an :class:`io.StringIO` object or the :mod:`array` " +"module::" +msgstr "" + +#: ../Doc/faq/programming.rst:879 +msgid "How do I use strings to call functions/methods?" +msgstr "" + +#: ../Doc/faq/programming.rst:881 +msgid "There are various techniques." +msgstr "" + +#: ../Doc/faq/programming.rst:883 +msgid "" +"The best is to use a dictionary that maps strings to functions. The primary " +"advantage of this technique is that the strings do not need to match the " +"names of the functions. This is also the primary technique used to emulate " +"a case construct::" +msgstr "" + +#: ../Doc/faq/programming.rst:898 +msgid "Use the built-in function :func:`getattr`::" +msgstr "" + +#: ../Doc/faq/programming.rst:903 +msgid "" +"Note that :func:`getattr` works on any object, including classes, class " +"instances, modules, and so on." +msgstr "" + +#: ../Doc/faq/programming.rst:906 +msgid "This is used in several places in the standard library, like this::" +msgstr "" + +#: ../Doc/faq/programming.rst:919 +msgid "Use :func:`locals` or :func:`eval` to resolve the function name::" +msgstr "" + +#: ../Doc/faq/programming.rst:932 +msgid "" +"Note: Using :func:`eval` is slow and dangerous. If you don't have absolute " +"control over the contents of the string, someone could pass a string that " +"resulted in an arbitrary function being executed." +msgstr "" + +#: ../Doc/faq/programming.rst:937 +msgid "" +"Is there an equivalent to Perl's chomp() for removing trailing newlines from " +"strings?" +msgstr "" + +#: ../Doc/faq/programming.rst:939 +msgid "" +"You can use ``S.rstrip(\"\\r\\n\")`` to remove all occurrences of any line " +"terminator from the end of the string ``S`` without removing other trailing " +"whitespace. If the string ``S`` represents more than one line, with several " +"empty lines at the end, the line terminators for all the blank lines will be " +"removed::" +msgstr "" + +#: ../Doc/faq/programming.rst:951 +msgid "" +"Since this is typically only desired when reading text one line at a time, " +"using ``S.rstrip()`` this way works well." +msgstr "" + +#: ../Doc/faq/programming.rst:956 +msgid "Is there a scanf() or sscanf() equivalent?" +msgstr "" + +#: ../Doc/faq/programming.rst:958 +msgid "Not as such." +msgstr "" + +#: ../Doc/faq/programming.rst:960 +msgid "" +"For simple input parsing, the easiest approach is usually to split the line " +"into whitespace-delimited words using the :meth:`~str.split` method of " +"string objects and then convert decimal strings to numeric values using :" +"func:`int` or :func:`float`. ``split()`` supports an optional \"sep\" " +"parameter which is useful if the line uses something other than whitespace " +"as a separator." +msgstr "" + +#: ../Doc/faq/programming.rst:966 +msgid "" +"For more complicated input parsing, regular expressions are more powerful " +"than C's :c:func:`sscanf` and better suited for the task." +msgstr "" + +#: ../Doc/faq/programming.rst:971 +msgid "What does 'UnicodeDecodeError' or 'UnicodeEncodeError' error mean?" +msgstr "" + +#: ../Doc/faq/programming.rst:973 +msgid "See the :ref:`unicode-howto`." +msgstr "" + +#: ../Doc/faq/programming.rst:977 +msgid "Performance" +msgstr "" + +#: ../Doc/faq/programming.rst:980 +msgid "My program is too slow. How do I speed it up?" +msgstr "" + +#: ../Doc/faq/programming.rst:982 +msgid "" +"That's a tough one, in general. First, here are a list of things to " +"remember before diving further:" +msgstr "" + +#: ../Doc/faq/programming.rst:985 +msgid "" +"Performance characteristics vary across Python implementations. This FAQ " +"focusses on :term:`CPython`." +msgstr "" + +#: ../Doc/faq/programming.rst:987 +msgid "" +"Behaviour can vary across operating systems, especially when talking about I/" +"O or multi-threading." +msgstr "" + +#: ../Doc/faq/programming.rst:989 +msgid "" +"You should always find the hot spots in your program *before* attempting to " +"optimize any code (see the :mod:`profile` module)." +msgstr "" + +#: ../Doc/faq/programming.rst:991 +msgid "" +"Writing benchmark scripts will allow you to iterate quickly when searching " +"for improvements (see the :mod:`timeit` module)." +msgstr "" + +#: ../Doc/faq/programming.rst:993 +msgid "" +"It is highly recommended to have good code coverage (through unit testing or " +"any other technique) before potentially introducing regressions hidden in " +"sophisticated optimizations." +msgstr "" + +#: ../Doc/faq/programming.rst:997 +msgid "" +"That being said, there are many tricks to speed up Python code. Here are " +"some general principles which go a long way towards reaching acceptable " +"performance levels:" +msgstr "" + +#: ../Doc/faq/programming.rst:1001 +msgid "" +"Making your algorithms faster (or changing to faster ones) can yield much " +"larger benefits than trying to sprinkle micro-optimization tricks all over " +"your code." +msgstr "" + +#: ../Doc/faq/programming.rst:1005 +msgid "" +"Use the right data structures. Study documentation for the :ref:`bltin-" +"types` and the :mod:`collections` module." +msgstr "" + +#: ../Doc/faq/programming.rst:1008 +msgid "" +"When the standard library provides a primitive for doing something, it is " +"likely (although not guaranteed) to be faster than any alternative you may " +"come up with. This is doubly true for primitives written in C, such as " +"builtins and some extension types. For example, be sure to use either the :" +"meth:`list.sort` built-in method or the related :func:`sorted` function to " +"do sorting (and see the :ref:`sortinghowto` for examples of moderately " +"advanced usage)." +msgstr "" + +#: ../Doc/faq/programming.rst:1016 +msgid "" +"Abstractions tend to create indirections and force the interpreter to work " +"more. If the levels of indirection outweigh the amount of useful work done, " +"your program will be slower. You should avoid excessive abstraction, " +"especially under the form of tiny functions or methods (which are also often " +"detrimental to readability)." +msgstr "" + +#: ../Doc/faq/programming.rst:1022 +msgid "" +"If you have reached the limit of what pure Python can allow, there are tools " +"to take you further away. For example, `Cython `_ can " +"compile a slightly modified version of Python code into a C extension, and " +"can be used on many different platforms. Cython can take advantage of " +"compilation (and optional type annotations) to make your code significantly " +"faster than when interpreted. If you are confident in your C programming " +"skills, you can also :ref:`write a C extension module ` " +"yourself." +msgstr "" + +#: ../Doc/faq/programming.rst:1032 +msgid "" +"The wiki page devoted to `performance tips `_." +msgstr "" + +#: ../Doc/faq/programming.rst:1038 +msgid "What is the most efficient way to concatenate many strings together?" +msgstr "" + +#: ../Doc/faq/programming.rst:1040 +msgid "" +":class:`str` and :class:`bytes` objects are immutable, therefore " +"concatenating many strings together is inefficient as each concatenation " +"creates a new object. In the general case, the total runtime cost is " +"quadratic in the total string length." +msgstr "" + +#: ../Doc/faq/programming.rst:1045 +msgid "" +"To accumulate many :class:`str` objects, the recommended idiom is to place " +"them into a list and call :meth:`str.join` at the end::" +msgstr "" + +#: ../Doc/faq/programming.rst:1053 +msgid "(another reasonably efficient idiom is to use :class:`io.StringIO`)" +msgstr "" + +#: ../Doc/faq/programming.rst:1055 +msgid "" +"To accumulate many :class:`bytes` objects, the recommended idiom is to " +"extend a :class:`bytearray` object using in-place concatenation (the ``+=`` " +"operator)::" +msgstr "" + +#: ../Doc/faq/programming.rst:1064 +msgid "Sequences (Tuples/Lists)" +msgstr "" + +#: ../Doc/faq/programming.rst:1067 +msgid "How do I convert between tuples and lists?" +msgstr "" + +#: ../Doc/faq/programming.rst:1069 +msgid "" +"The type constructor ``tuple(seq)`` converts any sequence (actually, any " +"iterable) into a tuple with the same items in the same order." +msgstr "" + +#: ../Doc/faq/programming.rst:1072 +msgid "" +"For example, ``tuple([1, 2, 3])`` yields ``(1, 2, 3)`` and ``tuple('abc')`` " +"yields ``('a', 'b', 'c')``. If the argument is a tuple, it does not make a " +"copy but returns the same object, so it is cheap to call :func:`tuple` when " +"you aren't sure that an object is already a tuple." +msgstr "" + +#: ../Doc/faq/programming.rst:1077 +msgid "" +"The type constructor ``list(seq)`` converts any sequence or iterable into a " +"list with the same items in the same order. For example, ``list((1, 2, " +"3))`` yields ``[1, 2, 3]`` and ``list('abc')`` yields ``['a', 'b', 'c']``. " +"If the argument is a list, it makes a copy just like ``seq[:]`` would." +msgstr "" + +#: ../Doc/faq/programming.rst:1084 +msgid "What's a negative index?" +msgstr "" + +#: ../Doc/faq/programming.rst:1086 +msgid "" +"Python sequences are indexed with positive numbers and negative numbers. " +"For positive numbers 0 is the first index 1 is the second index and so " +"forth. For negative indices -1 is the last index and -2 is the penultimate " +"(next to last) index and so forth. Think of ``seq[-n]`` as the same as " +"``seq[len(seq)-n]``." +msgstr "" + +#: ../Doc/faq/programming.rst:1091 +msgid "" +"Using negative indices can be very convenient. For example ``S[:-1]`` is " +"all of the string except for its last character, which is useful for " +"removing the trailing newline from a string." +msgstr "" + +#: ../Doc/faq/programming.rst:1097 +msgid "How do I iterate over a sequence in reverse order?" +msgstr "" + +#: ../Doc/faq/programming.rst:1099 +msgid "" +"Use the :func:`reversed` built-in function, which is new in Python 2.4::" +msgstr "" + +#: ../Doc/faq/programming.rst:1104 +msgid "" +"This won't touch your original sequence, but build a new copy with reversed " +"order to iterate over." +msgstr "" + +#: ../Doc/faq/programming.rst:1107 +msgid "With Python 2.3, you can use an extended slice syntax::" +msgstr "" + +#: ../Doc/faq/programming.rst:1114 +msgid "How do you remove duplicates from a list?" +msgstr "" + +#: ../Doc/faq/programming.rst:1116 +msgid "See the Python Cookbook for a long discussion of many ways to do this:" +msgstr "" + +#: ../Doc/faq/programming.rst:1118 +msgid "https://code.activestate.com/recipes/52560/" +msgstr "" + +#: ../Doc/faq/programming.rst:1120 +msgid "" +"If you don't mind reordering the list, sort it and then scan from the end of " +"the list, deleting duplicates as you go::" +msgstr "" + +#: ../Doc/faq/programming.rst:1132 +msgid "" +"If all elements of the list may be used as set keys (i.e. they are all :term:" +"`hashable`) this is often faster ::" +msgstr "" + +#: ../Doc/faq/programming.rst:1137 +msgid "" +"This converts the list into a set, thereby removing duplicates, and then " +"back into a list." +msgstr "" + +#: ../Doc/faq/programming.rst:1142 +msgid "How do you make an array in Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:1144 +msgid "Use a list::" +msgstr "" + +#: ../Doc/faq/programming.rst:1148 +msgid "" +"Lists are equivalent to C or Pascal arrays in their time complexity; the " +"primary difference is that a Python list can contain objects of many " +"different types." +msgstr "" + +#: ../Doc/faq/programming.rst:1151 +msgid "" +"The ``array`` module also provides methods for creating arrays of fixed " +"types with compact representations, but they are slower to index than " +"lists. Also note that the Numeric extensions and others define array-like " +"structures with various characteristics as well." +msgstr "" + +#: ../Doc/faq/programming.rst:1156 +msgid "" +"To get Lisp-style linked lists, you can emulate cons cells using tuples::" +msgstr "" + +#: ../Doc/faq/programming.rst:1160 +msgid "" +"If mutability is desired, you could use lists instead of tuples. Here the " +"analogue of lisp car is ``lisp_list[0]`` and the analogue of cdr is " +"``lisp_list[1]``. Only do this if you're sure you really need to, because " +"it's usually a lot slower than using Python lists." +msgstr "" + +#: ../Doc/faq/programming.rst:1169 +msgid "How do I create a multidimensional list?" +msgstr "" + +#: ../Doc/faq/programming.rst:1171 +msgid "You probably tried to make a multidimensional array like this::" +msgstr "" + +#: ../Doc/faq/programming.rst:1175 +msgid "This looks correct if you print it:" +msgstr "" + +#: ../Doc/faq/programming.rst:1186 +msgid "But when you assign a value, it shows up in multiple places:" +msgstr "" + +#: ../Doc/faq/programming.rst:1198 +msgid "" +"The reason is that replicating a list with ``*`` doesn't create copies, it " +"only creates references to the existing objects. The ``*3`` creates a list " +"containing 3 references to the same list of length two. Changes to one row " +"will show in all rows, which is almost certainly not what you want." +msgstr "" + +#: ../Doc/faq/programming.rst:1203 +msgid "" +"The suggested approach is to create a list of the desired length first and " +"then fill in each element with a newly created list::" +msgstr "" + +#: ../Doc/faq/programming.rst:1210 +msgid "" +"This generates a list containing 3 different lists of length two. You can " +"also use a list comprehension::" +msgstr "" + +#: ../Doc/faq/programming.rst:1216 +msgid "" +"Or, you can use an extension that provides a matrix datatype; `NumPy `_ is the best known." +msgstr "" + +#: ../Doc/faq/programming.rst:1221 +msgid "How do I apply a method to a sequence of objects?" +msgstr "" + +#: ../Doc/faq/programming.rst:1223 +msgid "Use a list comprehension::" +msgstr "" + +#: ../Doc/faq/programming.rst:1230 +msgid "" +"Why does a_tuple[i] += ['item'] raise an exception when the addition works?" +msgstr "" + +#: ../Doc/faq/programming.rst:1232 +msgid "" +"This is because of a combination of the fact that augmented assignment " +"operators are *assignment* operators, and the difference between mutable and " +"immutable objects in Python." +msgstr "" + +#: ../Doc/faq/programming.rst:1236 +msgid "" +"This discussion applies in general when augmented assignment operators are " +"applied to elements of a tuple that point to mutable objects, but we'll use " +"a ``list`` and ``+=`` as our exemplar." +msgstr "" + +#: ../Doc/faq/programming.rst:1240 +msgid "If you wrote::" +msgstr "" + +#: ../Doc/faq/programming.rst:1248 +msgid "" +"The reason for the exception should be immediately clear: ``1`` is added to " +"the object ``a_tuple[0]`` points to (``1``), producing the result object, " +"``2``, but when we attempt to assign the result of the computation, ``2``, " +"to element ``0`` of the tuple, we get an error because we can't change what " +"an element of a tuple points to." +msgstr "" + +#: ../Doc/faq/programming.rst:1254 +msgid "" +"Under the covers, what this augmented assignment statement is doing is " +"approximately this::" +msgstr "" + +#: ../Doc/faq/programming.rst:1263 +msgid "" +"It is the assignment part of the operation that produces the error, since a " +"tuple is immutable." +msgstr "" + +#: ../Doc/faq/programming.rst:1266 +msgid "When you write something like::" +msgstr "" + +#: ../Doc/faq/programming.rst:1274 +msgid "" +"The exception is a bit more surprising, and even more surprising is the fact " +"that even though there was an error, the append worked::" +msgstr "" + +#: ../Doc/faq/programming.rst:1280 +msgid "" +"To see why this happens, you need to know that (a) if an object implements " +"an ``__iadd__`` magic method, it gets called when the ``+=`` augmented " +"assignment is executed, and its return value is what gets used in the " +"assignment statement; and (b) for lists, ``__iadd__`` is equivalent to " +"calling ``extend`` on the list and returning the list. That's why we say " +"that for lists, ``+=`` is a \"shorthand\" for ``list.extend``::" +msgstr "" + +#: ../Doc/faq/programming.rst:1292 +msgid "This is equivalent to::" +msgstr "" + +#: ../Doc/faq/programming.rst:1297 +msgid "" +"The object pointed to by a_list has been mutated, and the pointer to the " +"mutated object is assigned back to ``a_list``. The end result of the " +"assignment is a no-op, since it is a pointer to the same object that " +"``a_list`` was previously pointing to, but the assignment still happens." +msgstr "" + +#: ../Doc/faq/programming.rst:1302 +msgid "Thus, in our tuple example what is happening is equivalent to::" +msgstr "" + +#: ../Doc/faq/programming.rst:1310 +msgid "" +"The ``__iadd__`` succeeds, and thus the list is extended, but even though " +"``result`` points to the same object that ``a_tuple[0]`` already points to, " +"that final assignment still results in an error, because tuples are " +"immutable." +msgstr "" + +#: ../Doc/faq/programming.rst:1316 +msgid "Dictionaries" +msgstr "" + +#: ../Doc/faq/programming.rst:1319 +msgid "" +"How can I get a dictionary to store and display its keys in a consistent " +"order?" +msgstr "" + +#: ../Doc/faq/programming.rst:1321 +msgid "Use :class:`collections.OrderedDict`." +msgstr "" + +#: ../Doc/faq/programming.rst:1324 +msgid "" +"I want to do a complicated sort: can you do a Schwartzian Transform in " +"Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:1326 +msgid "" +"The technique, attributed to Randal Schwartz of the Perl community, sorts " +"the elements of a list by a metric which maps each element to its \"sort " +"value\". In Python, use the ``key`` argument for the :meth:`list.sort` " +"method::" +msgstr "" + +#: ../Doc/faq/programming.rst:1335 +msgid "How can I sort one list by values from another list?" +msgstr "" + +#: ../Doc/faq/programming.rst:1337 +msgid "" +"Merge them into an iterator of tuples, sort the resulting list, and then " +"pick out the element you want. ::" +msgstr "" + +#: ../Doc/faq/programming.rst:1351 +msgid "An alternative for the last step is::" +msgstr "" + +#: ../Doc/faq/programming.rst:1356 +msgid "" +"If you find this more legible, you might prefer to use this instead of the " +"final list comprehension. However, it is almost twice as slow for long " +"lists. Why? First, the ``append()`` operation has to reallocate memory, and " +"while it uses some tricks to avoid doing that each time, it still has to do " +"it occasionally, and that costs quite a bit. Second, the expression " +"\"result.append\" requires an extra attribute lookup, and third, there's a " +"speed reduction from having to make all those function calls." +msgstr "" + +#: ../Doc/faq/programming.rst:1366 +msgid "Objects" +msgstr "" + +#: ../Doc/faq/programming.rst:1369 +msgid "What is a class?" +msgstr "" + +#: ../Doc/faq/programming.rst:1371 +msgid "" +"A class is the particular object type created by executing a class " +"statement. Class objects are used as templates to create instance objects, " +"which embody both the data (attributes) and code (methods) specific to a " +"datatype." +msgstr "" + +#: ../Doc/faq/programming.rst:1375 +msgid "" +"A class can be based on one or more other classes, called its base " +"class(es). It then inherits the attributes and methods of its base classes. " +"This allows an object model to be successively refined by inheritance. You " +"might have a generic ``Mailbox`` class that provides basic accessor methods " +"for a mailbox, and subclasses such as ``MboxMailbox``, ``MaildirMailbox``, " +"``OutlookMailbox`` that handle various specific mailbox formats." +msgstr "" + +#: ../Doc/faq/programming.rst:1384 +msgid "What is a method?" +msgstr "" + +#: ../Doc/faq/programming.rst:1386 +msgid "" +"A method is a function on some object ``x`` that you normally call as ``x." +"name(arguments...)``. Methods are defined as functions inside the class " +"definition::" +msgstr "" + +#: ../Doc/faq/programming.rst:1396 +msgid "What is self?" +msgstr "" + +#: ../Doc/faq/programming.rst:1398 +msgid "" +"Self is merely a conventional name for the first argument of a method. A " +"method defined as ``meth(self, a, b, c)`` should be called as ``x.meth(a, b, " +"c)`` for some instance ``x`` of the class in which the definition occurs; " +"the called method will think it is called as ``meth(x, a, b, c)``." +msgstr "" + +#: ../Doc/faq/programming.rst:1403 +msgid "See also :ref:`why-self`." +msgstr "" + +#: ../Doc/faq/programming.rst:1407 +msgid "" +"How do I check if an object is an instance of a given class or of a subclass " +"of it?" +msgstr "" + +#: ../Doc/faq/programming.rst:1409 +msgid "" +"Use the built-in function ``isinstance(obj, cls)``. You can check if an " +"object is an instance of any of a number of classes by providing a tuple " +"instead of a single class, e.g. ``isinstance(obj, (class1, class2, ...))``, " +"and can also check whether an object is one of Python's built-in types, e.g. " +"``isinstance(obj, str)`` or ``isinstance(obj, (int, float, complex))``." +msgstr "" + +#: ../Doc/faq/programming.rst:1415 +msgid "" +"Note that most programs do not use :func:`isinstance` on user-defined " +"classes very often. If you are developing the classes yourself, a more " +"proper object-oriented style is to define methods on the classes that " +"encapsulate a particular behaviour, instead of checking the object's class " +"and doing a different thing based on what class it is. For example, if you " +"have a function that does something::" +msgstr "" + +#: ../Doc/faq/programming.rst:1429 +msgid "" +"A better approach is to define a ``search()`` method on all the classes and " +"just call it::" +msgstr "" + +#: ../Doc/faq/programming.rst:1444 +msgid "What is delegation?" +msgstr "" + +#: ../Doc/faq/programming.rst:1446 +msgid "" +"Delegation is an object oriented technique (also called a design pattern). " +"Let's say you have an object ``x`` and want to change the behaviour of just " +"one of its methods. You can create a new class that provides a new " +"implementation of the method you're interested in changing and delegates all " +"other methods to the corresponding method of ``x``." +msgstr "" + +#: ../Doc/faq/programming.rst:1452 +msgid "" +"Python programmers can easily implement delegation. For example, the " +"following class implements a class that behaves like a file but converts all " +"written data to uppercase::" +msgstr "" + +#: ../Doc/faq/programming.rst:1467 +msgid "" +"Here the ``UpperOut`` class redefines the ``write()`` method to convert the " +"argument string to uppercase before calling the underlying ``self.__outfile." +"write()`` method. All other methods are delegated to the underlying ``self." +"__outfile`` object. The delegation is accomplished via the ``__getattr__`` " +"method; consult :ref:`the language reference ` for more " +"information about controlling attribute access." +msgstr "" + +#: ../Doc/faq/programming.rst:1474 +msgid "" +"Note that for more general cases delegation can get trickier. When " +"attributes must be set as well as retrieved, the class must define a :meth:" +"`__setattr__` method too, and it must do so carefully. The basic " +"implementation of :meth:`__setattr__` is roughly equivalent to the " +"following::" +msgstr "" + +#: ../Doc/faq/programming.rst:1485 +msgid "" +"Most :meth:`__setattr__` implementations must modify ``self.__dict__`` to " +"store local state for self without causing an infinite recursion." +msgstr "" + +#: ../Doc/faq/programming.rst:1490 +msgid "" +"How do I call a method defined in a base class from a derived class that " +"overrides it?" +msgstr "" + +#: ../Doc/faq/programming.rst:1492 +msgid "Use the built-in :func:`super` function::" +msgstr "" + +#: ../Doc/faq/programming.rst:1498 +msgid "" +"For version prior to 3.0, you may be using classic classes: For a class " +"definition such as ``class Derived(Base): ...`` you can call method " +"``meth()`` defined in ``Base`` (or one of ``Base``'s base classes) as ``Base." +"meth(self, arguments...)``. Here, ``Base.meth`` is an unbound method, so " +"you need to provide the ``self`` argument." +msgstr "" + +#: ../Doc/faq/programming.rst:1506 +msgid "How can I organize my code to make it easier to change the base class?" +msgstr "" + +#: ../Doc/faq/programming.rst:1508 +msgid "" +"You could define an alias for the base class, assign the real base class to " +"it before your class definition, and use the alias throughout your class. " +"Then all you have to change is the value assigned to the alias. " +"Incidentally, this trick is also handy if you want to decide dynamically (e." +"g. depending on availability of resources) which base class to use. " +"Example::" +msgstr "" + +#: ../Doc/faq/programming.rst:1523 +msgid "How do I create static class data and static class methods?" +msgstr "" + +#: ../Doc/faq/programming.rst:1525 +msgid "" +"Both static data and static methods (in the sense of C++ or Java) are " +"supported in Python." +msgstr "" + +#: ../Doc/faq/programming.rst:1528 +msgid "" +"For static data, simply define a class attribute. To assign a new value to " +"the attribute, you have to explicitly use the class name in the assignment::" +msgstr "" + +#: ../Doc/faq/programming.rst:1540 +msgid "" +"``c.count`` also refers to ``C.count`` for any ``c`` such that " +"``isinstance(c, C)`` holds, unless overridden by ``c`` itself or by some " +"class on the base-class search path from ``c.__class__`` back to ``C``." +msgstr "" + +#: ../Doc/faq/programming.rst:1544 +msgid "" +"Caution: within a method of C, an assignment like ``self.count = 42`` " +"creates a new and unrelated instance named \"count\" in ``self``'s own " +"dict. Rebinding of a class-static data name must always specify the class " +"whether inside a method or not::" +msgstr "" + +#: ../Doc/faq/programming.rst:1551 +msgid "Static methods are possible::" +msgstr "" + +#: ../Doc/faq/programming.rst:1559 +msgid "" +"However, a far more straightforward way to get the effect of a static method " +"is via a simple module-level function::" +msgstr "" + +#: ../Doc/faq/programming.rst:1565 +msgid "" +"If your code is structured so as to define one class (or tightly related " +"class hierarchy) per module, this supplies the desired encapsulation." +msgstr "" + +#: ../Doc/faq/programming.rst:1570 +msgid "How can I overload constructors (or methods) in Python?" +msgstr "" + +#: ../Doc/faq/programming.rst:1572 +msgid "" +"This answer actually applies to all methods, but the question usually comes " +"up first in the context of constructors." +msgstr "" + +#: ../Doc/faq/programming.rst:1575 +msgid "In C++ you'd write" +msgstr "" + +#: ../Doc/faq/programming.rst:1584 +msgid "" +"In Python you have to write a single constructor that catches all cases " +"using default arguments. For example::" +msgstr "" + +#: ../Doc/faq/programming.rst:1594 +msgid "This is not entirely equivalent, but close enough in practice." +msgstr "" + +#: ../Doc/faq/programming.rst:1596 +msgid "You could also try a variable-length argument list, e.g. ::" +msgstr "" + +#: ../Doc/faq/programming.rst:1601 +msgid "The same approach works for all method definitions." +msgstr "" + +#: ../Doc/faq/programming.rst:1605 +msgid "I try to use __spam and I get an error about _SomeClassName__spam." +msgstr "" + +#: ../Doc/faq/programming.rst:1607 +msgid "" +"Variable names with double leading underscores are \"mangled\" to provide a " +"simple but effective way to define class private variables. Any identifier " +"of the form ``__spam`` (at least two leading underscores, at most one " +"trailing underscore) is textually replaced with ``_classname__spam``, where " +"``classname`` is the current class name with any leading underscores " +"stripped." +msgstr "" + +#: ../Doc/faq/programming.rst:1613 +msgid "" +"This doesn't guarantee privacy: an outside user can still deliberately " +"access the \"_classname__spam\" attribute, and private values are visible in " +"the object's ``__dict__``. Many Python programmers never bother to use " +"private variable names at all." +msgstr "" + +#: ../Doc/faq/programming.rst:1620 +msgid "My class defines __del__ but it is not called when I delete the object." +msgstr "" + +#: ../Doc/faq/programming.rst:1622 +msgid "There are several possible reasons for this." +msgstr "" + +#: ../Doc/faq/programming.rst:1624 +msgid "" +"The del statement does not necessarily call :meth:`__del__` -- it simply " +"decrements the object's reference count, and if this reaches zero :meth:" +"`__del__` is called." +msgstr "" + +#: ../Doc/faq/programming.rst:1628 +msgid "" +"If your data structures contain circular links (e.g. a tree where each child " +"has a parent reference and each parent has a list of children) the reference " +"counts will never go back to zero. Once in a while Python runs an algorithm " +"to detect such cycles, but the garbage collector might run some time after " +"the last reference to your data structure vanishes, so your :meth:`__del__` " +"method may be called at an inconvenient and random time. This is " +"inconvenient if you're trying to reproduce a problem. Worse, the order in " +"which object's :meth:`__del__` methods are executed is arbitrary. You can " +"run :func:`gc.collect` to force a collection, but there *are* pathological " +"cases where objects will never be collected." +msgstr "" + +#: ../Doc/faq/programming.rst:1639 +msgid "" +"Despite the cycle collector, it's still a good idea to define an explicit " +"``close()`` method on objects to be called whenever you're done with them. " +"The ``close()`` method can then remove attributes that refer to subobjecs. " +"Don't call :meth:`__del__` directly -- :meth:`__del__` should call " +"``close()`` and ``close()`` should make sure that it can be called more than " +"once for the same object." +msgstr "" + +#: ../Doc/faq/programming.rst:1646 +msgid "" +"Another way to avoid cyclical references is to use the :mod:`weakref` " +"module, which allows you to point to objects without incrementing their " +"reference count. Tree data structures, for instance, should use weak " +"references for their parent and sibling references (if they need them!)." +msgstr "" + +#: ../Doc/faq/programming.rst:1659 +msgid "" +"Finally, if your :meth:`__del__` method raises an exception, a warning " +"message is printed to :data:`sys.stderr`." +msgstr "" + +#: ../Doc/faq/programming.rst:1664 +msgid "How do I get a list of all instances of a given class?" +msgstr "" + +#: ../Doc/faq/programming.rst:1666 +msgid "" +"Python does not keep track of all instances of a class (or of a built-in " +"type). You can program the class's constructor to keep track of all " +"instances by keeping a list of weak references to each instance." +msgstr "" + +#: ../Doc/faq/programming.rst:1672 +msgid "Why does the result of ``id()`` appear to be not unique?" +msgstr "" + +#: ../Doc/faq/programming.rst:1674 +msgid "" +"The :func:`id` builtin returns an integer that is guaranteed to be unique " +"during the lifetime of the object. Since in CPython, this is the object's " +"memory address, it happens frequently that after an object is deleted from " +"memory, the next freshly created object is allocated at the same position in " +"memory. This is illustrated by this example:" +msgstr "" + +#: ../Doc/faq/programming.rst:1685 +msgid "" +"The two ids belong to different integer objects that are created before, and " +"deleted immediately after execution of the ``id()`` call. To be sure that " +"objects whose id you want to examine are still alive, create another " +"reference to the object:" +msgstr "" + +#: ../Doc/faq/programming.rst:1698 +msgid "Modules" +msgstr "" + +#: ../Doc/faq/programming.rst:1701 +msgid "How do I create a .pyc file?" +msgstr "" + +#: ../Doc/faq/programming.rst:1703 +msgid "" +"When a module is imported for the first time (or when the source file has " +"changed since the current compiled file was created) a ``.pyc`` file " +"containing the compiled code should be created in a ``__pycache__`` " +"subdirectory of the directory containing the ``.py`` file. The ``.pyc`` " +"file will have a filename that starts with the same name as the ``.py`` " +"file, and ends with ``.pyc``, with a middle component that depends on the " +"particular ``python`` binary that created it. (See :pep:`3147` for details.)" +msgstr "" + +#: ../Doc/faq/programming.rst:1711 +msgid "" +"One reason that a ``.pyc`` file may not be created is a permissions problem " +"with the directory containing the source file, meaning that the " +"``__pycache__`` subdirectory cannot be created. This can happen, for " +"example, if you develop as one user but run as another, such as if you are " +"testing with a web server." +msgstr "" + +#: ../Doc/faq/programming.rst:1716 +msgid "" +"Unless the :envvar:`PYTHONDONTWRITEBYTECODE` environment variable is set, " +"creation of a .pyc file is automatic if you're importing a module and Python " +"has the ability (permissions, free space, etc...) to create a " +"``__pycache__`` subdirectory and write the compiled module to that " +"subdirectory." +msgstr "" + +#: ../Doc/faq/programming.rst:1721 +msgid "" +"Running Python on a top level script is not considered an import and no ``." +"pyc`` will be created. For example, if you have a top-level module ``foo." +"py`` that imports another module ``xyz.py``, when you run ``foo`` (by typing " +"``python foo.py`` as a shell command), a ``.pyc`` will be created for " +"``xyz`` because ``xyz`` is imported, but no ``.pyc`` file will be created " +"for ``foo`` since ``foo.py`` isn't being imported." +msgstr "" + +#: ../Doc/faq/programming.rst:1728 +msgid "" +"If you need to create a ``.pyc`` file for ``foo`` -- that is, to create a ``." +"pyc`` file for a module that is not imported -- you can, using the :mod:" +"`py_compile` and :mod:`compileall` modules." +msgstr "" + +#: ../Doc/faq/programming.rst:1732 +msgid "" +"The :mod:`py_compile` module can manually compile any module. One way is to " +"use the ``compile()`` function in that module interactively::" +msgstr "" + +#: ../Doc/faq/programming.rst:1738 +msgid "" +"This will write the ``.pyc`` to a ``__pycache__`` subdirectory in the same " +"location as ``foo.py`` (or you can override that with the optional parameter " +"``cfile``)." +msgstr "" + +#: ../Doc/faq/programming.rst:1742 +msgid "" +"You can also automatically compile all files in a directory or directories " +"using the :mod:`compileall` module. You can do it from the shell prompt by " +"running ``compileall.py`` and providing the path of a directory containing " +"Python files to compile::" +msgstr "" + +#: ../Doc/faq/programming.rst:1751 +msgid "How do I find the current module name?" +msgstr "" + +#: ../Doc/faq/programming.rst:1753 +msgid "" +"A module can find out its own module name by looking at the predefined " +"global variable ``__name__``. If this has the value ``'__main__'``, the " +"program is running as a script. Many modules that are usually used by " +"importing them also provide a command-line interface or a self-test, and " +"only execute this code after checking ``__name__``::" +msgstr "" + +#: ../Doc/faq/programming.rst:1768 +msgid "How can I have modules that mutually import each other?" +msgstr "" + +#: ../Doc/faq/programming.rst:1770 +msgid "Suppose you have the following modules:" +msgstr "" + +#: ../Doc/faq/programming.rst:1772 +msgid "foo.py::" +msgstr "" + +#: ../Doc/faq/programming.rst:1777 +msgid "bar.py::" +msgstr "" + +#: ../Doc/faq/programming.rst:1782 +msgid "The problem is that the interpreter will perform the following steps:" +msgstr "" + +#: ../Doc/faq/programming.rst:1784 +msgid "main imports foo" +msgstr "" + +#: ../Doc/faq/programming.rst:1785 +msgid "Empty globals for foo are created" +msgstr "" + +#: ../Doc/faq/programming.rst:1786 +msgid "foo is compiled and starts executing" +msgstr "" + +#: ../Doc/faq/programming.rst:1787 +msgid "foo imports bar" +msgstr "" + +#: ../Doc/faq/programming.rst:1788 +msgid "Empty globals for bar are created" +msgstr "" + +#: ../Doc/faq/programming.rst:1789 +msgid "bar is compiled and starts executing" +msgstr "" + +#: ../Doc/faq/programming.rst:1790 +msgid "" +"bar imports foo (which is a no-op since there already is a module named foo)" +msgstr "" + +#: ../Doc/faq/programming.rst:1791 +msgid "bar.foo_var = foo.foo_var" +msgstr "" + +#: ../Doc/faq/programming.rst:1793 +msgid "" +"The last step fails, because Python isn't done with interpreting ``foo`` yet " +"and the global symbol dictionary for ``foo`` is still empty." +msgstr "" + +#: ../Doc/faq/programming.rst:1796 +msgid "" +"The same thing happens when you use ``import foo``, and then try to access " +"``foo.foo_var`` in global code." +msgstr "" + +#: ../Doc/faq/programming.rst:1799 +msgid "There are (at least) three possible workarounds for this problem." +msgstr "" + +#: ../Doc/faq/programming.rst:1801 +msgid "" +"Guido van Rossum recommends avoiding all uses of ``from import ..." +"``, and placing all code inside functions. Initializations of global " +"variables and class variables should use constants or built-in functions " +"only. This means everything from an imported module is referenced as " +"``.``." +msgstr "" + +#: ../Doc/faq/programming.rst:1806 +msgid "" +"Jim Roskind suggests performing steps in the following order in each module:" +msgstr "" + +#: ../Doc/faq/programming.rst:1808 +msgid "" +"exports (globals, functions, and classes that don't need imported base " +"classes)" +msgstr "" + +#: ../Doc/faq/programming.rst:1810 +msgid "``import`` statements" +msgstr "" + +#: ../Doc/faq/programming.rst:1811 +msgid "" +"active code (including globals that are initialized from imported values)." +msgstr "" + +#: ../Doc/faq/programming.rst:1813 +msgid "" +"van Rossum doesn't like this approach much because the imports appear in a " +"strange place, but it does work." +msgstr "" + +#: ../Doc/faq/programming.rst:1816 +msgid "" +"Matthias Urlichs recommends restructuring your code so that the recursive " +"import is not necessary in the first place." +msgstr "" + +#: ../Doc/faq/programming.rst:1819 +msgid "These solutions are not mutually exclusive." +msgstr "" + +#: ../Doc/faq/programming.rst:1823 +msgid "__import__('x.y.z') returns ; how do I get z?" +msgstr "" + +#: ../Doc/faq/programming.rst:1825 +msgid "" +"Consider using the convenience function :func:`~importlib.import_module` " +"from :mod:`importlib` instead::" +msgstr "" + +#: ../Doc/faq/programming.rst:1832 +msgid "" +"When I edit an imported module and reimport it, the changes don't show up. " +"Why does this happen?" +msgstr "" + +#: ../Doc/faq/programming.rst:1834 +msgid "" +"For reasons of efficiency as well as consistency, Python only reads the " +"module file on the first time a module is imported. If it didn't, in a " +"program consisting of many modules where each one imports the same basic " +"module, the basic module would be parsed and re-parsed many times. To force " +"re-reading of a changed module, do this::" +msgstr "" + +#: ../Doc/faq/programming.rst:1844 +msgid "" +"Warning: this technique is not 100% fool-proof. In particular, modules " +"containing statements like ::" +msgstr "" + +#: ../Doc/faq/programming.rst:1849 +msgid "" +"will continue to work with the old version of the imported objects. If the " +"module contains class definitions, existing class instances will *not* be " +"updated to use the new class definition. This can result in the following " +"paradoxical behaviour:" +msgstr "" + +#: ../Doc/faq/programming.rst:1862 +msgid "" +"The nature of the problem is made clear if you print out the \"identity\" of " +"the class objects:" +msgstr "" + +#: ../Doc/faq/windows.rst:7 +msgid "Python on Windows FAQ" +msgstr "" + +#: ../Doc/faq/windows.rst:18 +msgid "How do I run a Python program under Windows?" +msgstr "" + +#: ../Doc/faq/windows.rst:20 +msgid "" +"This is not necessarily a straightforward question. If you are already " +"familiar with running programs from the Windows command line then everything " +"will seem obvious; otherwise, you might need a little more guidance." +msgstr "" + +#: ../Doc/faq/windows.rst:0 +msgid "|Python Development on XP|_" +msgstr "" + +#: ../Doc/faq/windows.rst:27 +msgid "" +"This series of screencasts aims to get you up and running with Python on " +"Windows XP. The knowledge is distilled into 1.5 hours and will get you up " +"and running with the right Python distribution, coding in your choice of " +"IDE, and debugging and writing solid code with unit-tests." +msgstr "" + +#: ../Doc/faq/windows.rst:36 +msgid "" +"Unless you use some sort of integrated development environment, you will end " +"up *typing* Windows commands into what is variously referred to as a \"DOS " +"window\" or \"Command prompt window\". Usually you can create such a window " +"from your Start menu; under Windows 7 the menu selection is :menuselection:" +"`Start --> Programs --> Accessories --> Command Prompt`. You should be able " +"to recognize when you have started such a window because you will see a " +"Windows \"command prompt\", which usually looks like this::" +msgstr "" + +#: ../Doc/faq/windows.rst:46 +msgid "" +"The letter may be different, and there might be other things after it, so " +"you might just as easily see something like::" +msgstr "" + +#: ../Doc/faq/windows.rst:51 +msgid "" +"depending on how your computer has been set up and what else you have " +"recently done with it. Once you have started such a window, you are well on " +"the way to running Python programs." +msgstr "" + +#: ../Doc/faq/windows.rst:55 +msgid "" +"You need to realize that your Python scripts have to be processed by another " +"program called the Python *interpreter*. The interpreter reads your script, " +"compiles it into bytecodes, and then executes the bytecodes to run your " +"program. So, how do you arrange for the interpreter to handle your Python?" +msgstr "" + +#: ../Doc/faq/windows.rst:60 +msgid "" +"First, you need to make sure that your command window recognises the word " +"\"python\" as an instruction to start the interpreter. If you have opened a " +"command window, you should try entering the command ``python`` and hitting " +"return.::" +msgstr "" + +#: ../Doc/faq/windows.rst:67 +msgid "You should then see something like::" +msgstr "" + +#: ../Doc/faq/windows.rst:73 +msgid "" +"You have started the interpreter in \"interactive mode\". That means you can " +"enter Python statements or expressions interactively and have them executed " +"or evaluated while you wait. This is one of Python's strongest features. " +"Check it by entering a few expressions of your choice and seeing the " +"results::" +msgstr "" + +#: ../Doc/faq/windows.rst:83 +msgid "" +"Many people use the interactive mode as a convenient yet highly programmable " +"calculator. When you want to end your interactive Python session, hold the :" +"kbd:`Ctrl` key down while you enter a :kbd:`Z`, then hit the \":kbd:`Enter`" +"\" key to get back to your Windows command prompt." +msgstr "" + +#: ../Doc/faq/windows.rst:88 +msgid "" +"You may also find that you have a Start-menu entry such as :menuselection:" +"`Start --> Programs --> Python 3.3 --> Python (command line)` that results " +"in you seeing the ``>>>`` prompt in a new window. If so, the window will " +"disappear after you enter the :kbd:`Ctrl-Z` character; Windows is running a " +"single \"python\" command in the window, and closes it when you terminate " +"the interpreter." +msgstr "" + +#: ../Doc/faq/windows.rst:94 +msgid "" +"If the ``python`` command, instead of displaying the interpreter prompt " +"``>>>``, gives you a message like::" +msgstr "" + +#: ../Doc/faq/windows.rst:0 +msgid "|Adding Python to DOS Path|_" +msgstr "" + +#: ../Doc/faq/windows.rst:102 +msgid "" +"Python is not added to the DOS path by default. This screencast will walk " +"you through the steps to add the correct entry to the `System Path`, " +"allowing Python to be executed from the command-line by all users." +msgstr "" + +#: ../Doc/faq/windows.rst:111 +msgid "or::" +msgstr "" + +#: ../Doc/faq/windows.rst:115 +msgid "" +"then you need to make sure that your computer knows where to find the Python " +"interpreter. To do this you will have to modify a setting called PATH, " +"which is a list of directories where Windows will look for programs." +msgstr "" + +#: ../Doc/faq/windows.rst:119 +msgid "" +"You should arrange for Python's installation directory to be added to the " +"PATH of every command window as it starts. If you installed Python fairly " +"recently then the command ::" +msgstr "" + +#: ../Doc/faq/windows.rst:125 +msgid "" +"will probably tell you where it is installed; the usual location is " +"something like ``C:\\Python33``. Otherwise you will be reduced to a search " +"of your whole disk ... use :menuselection:`Tools --> Find` or hit the :" +"guilabel:`Search` button and look for \"python.exe\". Supposing you " +"discover that Python is installed in the ``C:\\Python33`` directory (the " +"default at the time of writing), you should make sure that entering the " +"command ::" +msgstr "" + +#: ../Doc/faq/windows.rst:134 +msgid "" +"starts up the interpreter as above (and don't forget you'll need a \":kbd:" +"`Ctrl-Z`\" and an \":kbd:`Enter`\" to get out of it). Once you have verified " +"the directory, you can add it to the system path to make it easier to start " +"Python by just running the ``python`` command. This is currently an option " +"in the installer as of CPython 3.3." +msgstr "" + +#: ../Doc/faq/windows.rst:140 +msgid "" +"More information about environment variables can be found on the :ref:`Using " +"Python on Windows ` page." +msgstr "" + +#: ../Doc/faq/windows.rst:144 +msgid "How do I make Python scripts executable?" +msgstr "" + +#: ../Doc/faq/windows.rst:146 +msgid "" +"On Windows, the standard Python installer already associates the .py " +"extension with a file type (Python.File) and gives that file type an open " +"command that runs the interpreter (``D:\\Program Files\\Python\\python.exe " +"\"%1\" %*``). This is enough to make scripts executable from the command " +"prompt as 'foo.py'. If you'd rather be able to execute the script by simple " +"typing 'foo' with no extension you need to add .py to the PATHEXT " +"environment variable." +msgstr "" + +#: ../Doc/faq/windows.rst:154 +msgid "Why does Python sometimes take so long to start?" +msgstr "" + +#: ../Doc/faq/windows.rst:156 +msgid "" +"Usually Python starts very quickly on Windows, but occasionally there are " +"bug reports that Python suddenly begins to take a long time to start up. " +"This is made even more puzzling because Python will work fine on other " +"Windows systems which appear to be configured identically." +msgstr "" + +#: ../Doc/faq/windows.rst:161 +msgid "" +"The problem may be caused by a misconfiguration of virus checking software " +"on the problem machine. Some virus scanners have been known to introduce " +"startup overhead of two orders of magnitude when the scanner is configured " +"to monitor all reads from the filesystem. Try checking the configuration of " +"virus scanning software on your systems to ensure that they are indeed " +"configured identically. McAfee, when configured to scan all file system read " +"activity, is a particular offender." +msgstr "" + +#: ../Doc/faq/windows.rst:171 +msgid "How do I make an executable from a Python script?" +msgstr "" + +#: ../Doc/faq/windows.rst:173 +msgid "" +"See http://cx-freeze.sourceforge.net/ for a distutils extension that allows " +"you to create console and GUI executables from Python code. `py2exe `_, the most popular extension for building Python 2.x-based " +"executables, does not yet support Python 3 but a version that does is in " +"development." +msgstr "" + +#: ../Doc/faq/windows.rst:181 +msgid "Is a ``*.pyd`` file the same as a DLL?" +msgstr "" + +#: ../Doc/faq/windows.rst:183 +msgid "" +"Yes, .pyd files are dll's, but there are a few differences. If you have a " +"DLL named ``foo.pyd``, then it must have a function ``PyInit_foo()``. You " +"can then write Python \"import foo\", and Python will search for foo.pyd (as " +"well as foo.py, foo.pyc) and if it finds it, will attempt to call " +"``PyInit_foo()`` to initialize it. You do not link your .exe with foo.lib, " +"as that would cause Windows to require the DLL to be present." +msgstr "" + +#: ../Doc/faq/windows.rst:190 +msgid "" +"Note that the search path for foo.pyd is PYTHONPATH, not the same as the " +"path that Windows uses to search for foo.dll. Also, foo.pyd need not be " +"present to run your program, whereas if you linked your program with a dll, " +"the dll is required. Of course, foo.pyd is required if you want to say " +"``import foo``. In a DLL, linkage is declared in the source code with " +"``__declspec(dllexport)``. In a .pyd, linkage is defined in a list of " +"available functions." +msgstr "" + +#: ../Doc/faq/windows.rst:199 +msgid "How can I embed Python into a Windows application?" +msgstr "" + +#: ../Doc/faq/windows.rst:201 +msgid "" +"Embedding the Python interpreter in a Windows app can be summarized as " +"follows:" +msgstr "" + +#: ../Doc/faq/windows.rst:203 +msgid "" +"Do _not_ build Python into your .exe file directly. On Windows, Python must " +"be a DLL to handle importing modules that are themselves DLL's. (This is " +"the first key undocumented fact.) Instead, link to :file:`python{NN}.dll`; " +"it is typically installed in ``C:\\Windows\\System``. *NN* is the Python " +"version, a number such as \"33\" for Python 3.3." +msgstr "" + +#: ../Doc/faq/windows.rst:209 +msgid "" +"You can link to Python in two different ways. Load-time linking means " +"linking against :file:`python{NN}.lib`, while run-time linking means linking " +"against :file:`python{NN}.dll`. (General note: :file:`python{NN}.lib` is " +"the so-called \"import lib\" corresponding to :file:`python{NN}.dll`. It " +"merely defines symbols for the linker.)" +msgstr "" + +#: ../Doc/faq/windows.rst:215 +msgid "" +"Run-time linking greatly simplifies link options; everything happens at run " +"time. Your code must load :file:`python{NN}.dll` using the Windows " +"``LoadLibraryEx()`` routine. The code must also use access routines and " +"data in :file:`python{NN}.dll` (that is, Python's C API's) using pointers " +"obtained by the Windows ``GetProcAddress()`` routine. Macros can make using " +"these pointers transparent to any C code that calls routines in Python's C " +"API." +msgstr "" + +#: ../Doc/faq/windows.rst:222 +msgid "" +"Borland note: convert :file:`python{NN}.lib` to OMF format using Coff2Omf." +"exe first." +msgstr "" + +#: ../Doc/faq/windows.rst:227 +msgid "" +"If you use SWIG, it is easy to create a Python \"extension module\" that " +"will make the app's data and methods available to Python. SWIG will handle " +"just about all the grungy details for you. The result is C code that you " +"link *into* your .exe file (!) You do _not_ have to create a DLL file, and " +"this also simplifies linking." +msgstr "" + +#: ../Doc/faq/windows.rst:233 +msgid "" +"SWIG will create an init function (a C function) whose name depends on the " +"name of the extension module. For example, if the name of the module is " +"leo, the init function will be called initleo(). If you use SWIG shadow " +"classes, as you should, the init function will be called initleoc(). This " +"initializes a mostly hidden helper class used by the shadow class." +msgstr "" + +#: ../Doc/faq/windows.rst:239 +msgid "" +"The reason you can link the C code in step 2 into your .exe file is that " +"calling the initialization function is equivalent to importing the module " +"into Python! (This is the second key undocumented fact.)" +msgstr "" + +#: ../Doc/faq/windows.rst:243 +msgid "" +"In short, you can use the following code to initialize the Python " +"interpreter with your extension module." +msgstr "" + +#: ../Doc/faq/windows.rst:254 +msgid "" +"There are two problems with Python's C API which will become apparent if you " +"use a compiler other than MSVC, the compiler used to build pythonNN.dll." +msgstr "" + +#: ../Doc/faq/windows.rst:257 +msgid "" +"Problem 1: The so-called \"Very High Level\" functions that take FILE * " +"arguments will not work in a multi-compiler environment because each " +"compiler's notion of a struct FILE will be different. From an " +"implementation standpoint these are very _low_ level functions." +msgstr "" + +#: ../Doc/faq/windows.rst:262 +msgid "" +"Problem 2: SWIG generates the following code when generating wrappers to " +"void functions:" +msgstr "" + +#: ../Doc/faq/windows.rst:271 +msgid "" +"Alas, Py_None is a macro that expands to a reference to a complex data " +"structure called _Py_NoneStruct inside pythonNN.dll. Again, this code will " +"fail in a mult-compiler environment. Replace such code by:" +msgstr "" + +#: ../Doc/faq/windows.rst:279 +msgid "" +"It may be possible to use SWIG's ``%typemap`` command to make the change " +"automatically, though I have not been able to get this to work (I'm a " +"complete SWIG newbie)." +msgstr "" + +#: ../Doc/faq/windows.rst:283 +msgid "" +"Using a Python shell script to put up a Python interpreter window from " +"inside your Windows app is not a good idea; the resulting window will be " +"independent of your app's windowing system. Rather, you (or the " +"wxPythonWindow class) should create a \"native\" interpreter window. It is " +"easy to connect that window to the Python interpreter. You can redirect " +"Python's i/o to _any_ object that supports read and write, so all you need " +"is a Python object (defined in your extension module) that contains read() " +"and write() methods." +msgstr "" + +#: ../Doc/faq/windows.rst:292 +msgid "How do I keep editors from inserting tabs into my Python source?" +msgstr "" + +#: ../Doc/faq/windows.rst:294 +msgid "" +"The FAQ does not recommend using tabs, and the Python style guide, :pep:`8`, " +"recommends 4 spaces for distributed Python code; this is also the Emacs " +"python-mode default." +msgstr "" + +#: ../Doc/faq/windows.rst:298 +msgid "" +"Under any editor, mixing tabs and spaces is a bad idea. MSVC is no " +"different in this respect, and is easily configured to use spaces: Take :" +"menuselection:`Tools --> Options --> Tabs`, and for file type \"Default\" " +"set \"Tab size\" and \"Indent size\" to 4, and select the \"Insert spaces\" " +"radio button." +msgstr "" + +#: ../Doc/faq/windows.rst:303 +msgid "" +"If you suspect mixed tabs and spaces are causing problems in leading " +"whitespace, run Python with the :option:`-t` switch or run ``Tools/Scripts/" +"tabnanny.py`` to check a directory tree in batch mode." +msgstr "" + +#: ../Doc/faq/windows.rst:309 +msgid "How do I check for a keypress without blocking?" +msgstr "" + +#: ../Doc/faq/windows.rst:311 +msgid "" +"Use the msvcrt module. This is a standard Windows-specific extension " +"module. It defines a function ``kbhit()`` which checks whether a keyboard " +"hit is present, and ``getch()`` which gets one character without echoing it." +msgstr "" + +#: ../Doc/faq/windows.rst:317 +msgid "How do I emulate os.kill() in Windows?" +msgstr "" + +#: ../Doc/faq/windows.rst:319 +msgid "" +"Prior to Python 2.7 and 3.2, to terminate a process, you can use :mod:" +"`ctypes`::" +msgstr "" + +#: ../Doc/faq/windows.rst:329 +msgid "" +"In 2.7 and 3.2, :func:`os.kill` is implemented similar to the above " +"function, with the additional feature of being able to send :kbd:`Ctrl+C` " +"and :kbd:`Ctrl+Break` to console subprocesses which are designed to handle " +"those signals. See :func:`os.kill` for further details." +msgstr "" + +#: ../Doc/faq/windows.rst:335 +msgid "How do I extract the downloaded documentation on Windows?" +msgstr "" + +#: ../Doc/faq/windows.rst:337 +msgid "" +"Sometimes, when you download the documentation package to a Windows machine " +"using a web browser, the file extension of the saved file ends up being ." +"EXE. This is a mistake; the extension should be .TGZ." +msgstr "" + +#: ../Doc/faq/windows.rst:341 +msgid "" +"Simply rename the downloaded file to have the .TGZ extension, and WinZip " +"will be able to handle it. (If your copy of WinZip doesn't, get a newer one " +"from https://www.winzip.com.)" +msgstr "" diff --git a/glossary.po b/glossary.po new file mode 100644 index 00000000..e23f866c --- /dev/null +++ b/glossary.po @@ -0,0 +1,1702 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \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 `). " +"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 `, " +"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 `_, 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 " +"`." +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 `." +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 `_. 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 ` and :ref:`class " +"definitions ` 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 `.) 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 " +"`, buffered :term:`binary files ` and :term:`text " +"files `. 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 " +"` for use with :data:`sys.meta_path`, and :term:`path " +"entry finders ` 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 ` 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 `) 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 `. 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 `, 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 ` 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 `. 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 `." +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 `_ 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 ` or as a :term:`keyword 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 `, " +"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 ` 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 "" diff --git a/howto.po b/howto.po new file mode 100644 index 00000000..ab736afe --- /dev/null +++ b/howto.po @@ -0,0 +1,13516 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/howto/argparse.rst:3 +msgid "Argparse Tutorial" +msgstr "" + +#: ../Doc/howto/argparse.rst:5 +msgid "Tshepang Lekhonkhobe" +msgstr "" + +#: ../Doc/howto/argparse.rst:9 +msgid "" +"This tutorial is intended to be a gentle introduction to :mod:`argparse`, " +"the recommended command-line parsing module in the Python standard library." +msgstr "" + +#: ../Doc/howto/argparse.rst:14 +msgid "" +"There are two other modules that fulfill the same task, namely :mod:`getopt` " +"(an equivalent for :c:func:`getopt` from the C language) and the deprecated :" +"mod:`optparse`. Note also that :mod:`argparse` is based on :mod:`optparse`, " +"and therefore very similar in terms of usage." +msgstr "" + +#: ../Doc/howto/argparse.rst:22 +msgid "Concepts" +msgstr "" + +#: ../Doc/howto/argparse.rst:24 +msgid "" +"Let's show the sort of functionality that we are going to explore in this " +"introductory tutorial by making use of the :command:`ls` command:" +msgstr "" + +#: ../Doc/howto/argparse.rst:46 +msgid "A few concepts we can learn from the four commands:" +msgstr "" + +#: ../Doc/howto/argparse.rst:48 +msgid "" +"The :command:`ls` command is useful when run without any options at all. It " +"defaults to displaying the contents of the current directory." +msgstr "" + +#: ../Doc/howto/argparse.rst:51 +msgid "" +"If we want beyond what it provides by default, we tell it a bit more. In " +"this case, we want it to display a different directory, ``pypy``. What we " +"did is specify what is known as a positional argument. It's named so because " +"the program should know what to do with the value, solely based on where it " +"appears on the command line. This concept is more relevant to a command " +"like :command:`cp`, whose most basic usage is ``cp SRC DEST``. The first " +"position is *what you want copied,* and the second position is *where you " +"want it copied to*." +msgstr "" + +#: ../Doc/howto/argparse.rst:60 +msgid "" +"Now, say we want to change behaviour of the program. In our example, we " +"display more info for each file instead of just showing the file names. The " +"``-l`` in that case is known as an optional argument." +msgstr "" + +#: ../Doc/howto/argparse.rst:64 +msgid "" +"That's a snippet of the help text. It's very useful in that you can come " +"across a program you have never used before, and can figure out how it works " +"simply by reading its help text." +msgstr "" + +#: ../Doc/howto/argparse.rst:70 +msgid "The basics" +msgstr "" + +#: ../Doc/howto/argparse.rst:72 +msgid "Let us start with a very simple example which does (almost) nothing::" +msgstr "" + +#: ../Doc/howto/argparse.rst:78 ../Doc/howto/argparse.rst:186 +#: ../Doc/howto/argparse.rst:207 +msgid "Following is a result of running the code:" +msgstr "" + +#: ../Doc/howto/argparse.rst:95 ../Doc/howto/argparse.rst:252 +#: ../Doc/howto/argparse.rst:296 +msgid "Here is what is happening:" +msgstr "" + +#: ../Doc/howto/argparse.rst:97 +msgid "" +"Running the script without any options results in nothing displayed to " +"stdout. Not so useful." +msgstr "" + +#: ../Doc/howto/argparse.rst:100 +msgid "" +"The second one starts to display the usefulness of the :mod:`argparse` " +"module. We have done almost nothing, but already we get a nice help message." +msgstr "" + +#: ../Doc/howto/argparse.rst:103 +msgid "" +"The ``--help`` option, which can also be shortened to ``-h``, is the only " +"option we get for free (i.e. no need to specify it). Specifying anything " +"else results in an error. But even then, we do get a useful usage message, " +"also for free." +msgstr "" + +#: ../Doc/howto/argparse.rst:110 +msgid "Introducing Positional arguments" +msgstr "" + +#: ../Doc/howto/argparse.rst:112 +msgid "An example::" +msgstr "" + +#: ../Doc/howto/argparse.rst:120 +msgid "And running the code:" +msgstr "" + +#: ../Doc/howto/argparse.rst:138 +msgid "Here is what's happening:" +msgstr "" + +#: ../Doc/howto/argparse.rst:140 +msgid "" +"We've added the :meth:`add_argument` method, which is what we use to specify " +"which command-line options the program is willing to accept. In this case, " +"I've named it ``echo`` so that it's in line with its function." +msgstr "" + +#: ../Doc/howto/argparse.rst:144 +msgid "Calling our program now requires us to specify an option." +msgstr "" + +#: ../Doc/howto/argparse.rst:146 +msgid "" +"The :meth:`parse_args` method actually returns some data from the options " +"specified, in this case, ``echo``." +msgstr "" + +#: ../Doc/howto/argparse.rst:149 +msgid "" +"The variable is some form of 'magic' that :mod:`argparse` performs for free " +"(i.e. no need to specify which variable that value is stored in). You will " +"also notice that its name matches the string argument given to the method, " +"``echo``." +msgstr "" + +#: ../Doc/howto/argparse.rst:154 +msgid "" +"Note however that, although the help display looks nice and all, it " +"currently is not as helpful as it can be. For example we see that we got " +"``echo`` as a positional argument, but we don't know what it does, other " +"than by guessing or by reading the source code. So, let's make it a bit more " +"useful::" +msgstr "" + +#: ../Doc/howto/argparse.rst:165 +msgid "And we get:" +msgstr "" + +#: ../Doc/howto/argparse.rst:178 +msgid "Now, how about doing something even more useful::" +msgstr "" + +#: ../Doc/howto/argparse.rst:196 +msgid "" +"That didn't go so well. That's because :mod:`argparse` treats the options we " +"give it as strings, unless we tell it otherwise. So, let's tell :mod:" +"`argparse` to treat that input as an integer::" +msgstr "" + +#: ../Doc/howto/argparse.rst:217 +msgid "" +"That went well. The program now even helpfully quits on bad illegal input " +"before proceeding." +msgstr "" + +#: ../Doc/howto/argparse.rst:222 +msgid "Introducing Optional arguments" +msgstr "" + +#: ../Doc/howto/argparse.rst:224 +msgid "" +"So far we, have been playing with positional arguments. Let us have a look " +"on how to add optional ones::" +msgstr "" + +#: ../Doc/howto/argparse.rst:234 ../Doc/howto/argparse.rst:280 +#: ../Doc/howto/argparse.rst:396 ../Doc/howto/argparse.rst:430 +msgid "And the output:" +msgstr "" + +#: ../Doc/howto/argparse.rst:254 +msgid "" +"The program is written so as to display something when ``--verbosity`` is " +"specified and display nothing when not." +msgstr "" + +#: ../Doc/howto/argparse.rst:257 +msgid "" +"To show that the option is actually optional, there is no error when running " +"the program without it. Note that by default, if an optional argument isn't " +"used, the relevant variable, in this case :attr:`args.verbosity`, is given " +"``None`` as a value, which is the reason it fails the truth test of the :" +"keyword:`if` statement." +msgstr "" + +#: ../Doc/howto/argparse.rst:263 +msgid "The help message is a bit different." +msgstr "" + +#: ../Doc/howto/argparse.rst:265 +msgid "" +"When using the ``--verbosity`` option, one must also specify some value, any " +"value." +msgstr "" + +#: ../Doc/howto/argparse.rst:268 +msgid "" +"The above example accepts arbitrary integer values for ``--verbosity``, but " +"for our simple program, only two values are actually useful, ``True`` or " +"``False``. Let's modify the code accordingly::" +msgstr "" + +#: ../Doc/howto/argparse.rst:298 +msgid "" +"The option is now more of a flag than something that requires a value. We " +"even changed the name of the option to match that idea. Note that we now " +"specify a new keyword, ``action``, and give it the value ``\"store_true\"``. " +"This means that, if the option is specified, assign the value ``True`` to :" +"data:`args.verbose`. Not specifying it implies ``False``." +msgstr "" + +#: ../Doc/howto/argparse.rst:305 +msgid "" +"It complains when you specify a value, in true spirit of what flags actually " +"are." +msgstr "" + +#: ../Doc/howto/argparse.rst:308 +msgid "Notice the different help text." +msgstr "" + +#: ../Doc/howto/argparse.rst:312 +msgid "Short options" +msgstr "" + +#: ../Doc/howto/argparse.rst:314 +msgid "" +"If you are familiar with command line usage, you will notice that I haven't " +"yet touched on the topic of short versions of the options. It's quite " +"simple::" +msgstr "" + +#: ../Doc/howto/argparse.rst:326 +msgid "And here goes:" +msgstr "" + +#: ../Doc/howto/argparse.rst:339 +msgid "Note that the new ability is also reflected in the help text." +msgstr "" + +#: ../Doc/howto/argparse.rst:343 +msgid "Combining Positional and Optional arguments" +msgstr "" + +#: ../Doc/howto/argparse.rst:345 +msgid "Our program keeps growing in complexity::" +msgstr "" + +#: ../Doc/howto/argparse.rst:360 +msgid "And now the output:" +msgstr "" + +#: ../Doc/howto/argparse.rst:374 +msgid "We've brought back a positional argument, hence the complaint." +msgstr "" + +#: ../Doc/howto/argparse.rst:376 +msgid "Note that the order does not matter." +msgstr "" + +#: ../Doc/howto/argparse.rst:378 +msgid "" +"How about we give this program of ours back the ability to have multiple " +"verbosity values, and actually get to use them::" +msgstr "" + +#: ../Doc/howto/argparse.rst:412 +msgid "" +"These all look good except the last one, which exposes a bug in our program. " +"Let's fix it by restricting the values the ``--verbosity`` option can " +"accept::" +msgstr "" + +#: ../Doc/howto/argparse.rst:448 +msgid "" +"Note that the change also reflects both in the error message as well as the " +"help string." +msgstr "" + +#: ../Doc/howto/argparse.rst:451 +msgid "" +"Now, let's use a different approach of playing with verbosity, which is " +"pretty common. It also matches the way the CPython executable handles its " +"own verbosity argument (check the output of ``python --help``)::" +msgstr "" + +#: ../Doc/howto/argparse.rst:470 +msgid "" +"We have introduced another action, \"count\", to count the number of " +"occurrences of a specific optional arguments:" +msgstr "" + +#: ../Doc/howto/argparse.rst:498 +msgid "" +"Yes, it's now more of a flag (similar to ``action=\"store_true\"``) in the " +"previous version of our script. That should explain the complaint." +msgstr "" + +#: ../Doc/howto/argparse.rst:501 +msgid "It also behaves similar to \"store_true\" action." +msgstr "" + +#: ../Doc/howto/argparse.rst:503 +msgid "" +"Now here's a demonstration of what the \"count\" action gives. You've " +"probably seen this sort of usage before." +msgstr "" + +#: ../Doc/howto/argparse.rst:506 +msgid "" +"And if you don't specify the ``-v`` flag, that flag is considered to have " +"``None`` value." +msgstr "" + +#: ../Doc/howto/argparse.rst:509 +msgid "" +"As should be expected, specifying the long form of the flag, we should get " +"the same output." +msgstr "" + +#: ../Doc/howto/argparse.rst:512 +msgid "" +"Sadly, our help output isn't very informative on the new ability our script " +"has acquired, but that can always be fixed by improving the documentation " +"for our script (e.g. via the ``help`` keyword argument)." +msgstr "" + +#: ../Doc/howto/argparse.rst:516 +msgid "That last output exposes a bug in our program." +msgstr "" + +#: ../Doc/howto/argparse.rst:519 +msgid "Let's fix::" +msgstr "" + +#: ../Doc/howto/argparse.rst:538 +msgid "And this is what it gives:" +msgstr "" + +#: ../Doc/howto/argparse.rst:553 +msgid "" +"First output went well, and fixes the bug we had before. That is, we want " +"any value >= 2 to be as verbose as possible." +msgstr "" + +#: ../Doc/howto/argparse.rst:556 +msgid "Third output not so good." +msgstr "" + +#: ../Doc/howto/argparse.rst:558 +msgid "Let's fix that bug::" +msgstr "" + +#: ../Doc/howto/argparse.rst:575 +msgid "" +"We've just introduced yet another keyword, ``default``. We've set it to " +"``0`` in order to make it comparable to the other int values. Remember that " +"by default, if an optional argument isn't specified, it gets the ``None`` " +"value, and that cannot be compared to an int value (hence the :exc:" +"`TypeError` exception)." +msgstr "" + +#: ../Doc/howto/argparse.rst:582 +msgid "And:" +msgstr "" + +#: ../Doc/howto/argparse.rst:589 +msgid "" +"You can go quite far just with what we've learned so far, and we have only " +"scratched the surface. The :mod:`argparse` module is very powerful, and " +"we'll explore a bit more of it before we end this tutorial." +msgstr "" + +#: ../Doc/howto/argparse.rst:596 +msgid "Getting a little more advanced" +msgstr "" + +#: ../Doc/howto/argparse.rst:598 +msgid "" +"What if we wanted to expand our tiny program to perform other powers, not " +"just squares::" +msgstr "" + +#: ../Doc/howto/argparse.rst:615 ../Doc/howto/argparse.rst:653 +msgid "Output:" +msgstr "" + +#: ../Doc/howto/argparse.rst:636 +msgid "" +"Notice that so far we've been using verbosity level to *change* the text " +"that gets displayed. The following example instead uses verbosity level to " +"display *more* text instead::" +msgstr "" + +#: ../Doc/howto/argparse.rst:667 +msgid "Conflicting options" +msgstr "" + +#: ../Doc/howto/argparse.rst:669 +msgid "" +"So far, we have been working with two methods of an :class:`argparse." +"ArgumentParser` instance. Let's introduce a third one, :meth:" +"`add_mutually_exclusive_group`. It allows for us to specify options that " +"conflict with each other. Let's also change the rest of the program so that " +"the new functionality makes more sense: we'll introduce the ``--quiet`` " +"option, which will be the opposite of the ``--verbose`` one::" +msgstr "" + +#: ../Doc/howto/argparse.rst:695 +msgid "" +"Our program is now simpler, and we've lost some functionality for the sake " +"of demonstration. Anyways, here's the output:" +msgstr "" + +#: ../Doc/howto/argparse.rst:713 +msgid "" +"That should be easy to follow. I've added that last output so you can see " +"the sort of flexibility you get, i.e. mixing long form options with short " +"form ones." +msgstr "" + +#: ../Doc/howto/argparse.rst:717 +msgid "" +"Before we conclude, you probably want to tell your users the main purpose of " +"your program, just in case they don't know::" +msgstr "" + +#: ../Doc/howto/argparse.rst:738 +msgid "" +"Note that slight difference in the usage text. Note the ``[-v | -q]``, which " +"tells us that we can either use ``-v`` or ``-q``, but not both at the same " +"time:" +msgstr "" + +#: ../Doc/howto/argparse.rst:760 +msgid "Conclusion" +msgstr "" + +#: ../Doc/howto/argparse.rst:762 +msgid "" +"The :mod:`argparse` module offers a lot more than shown here. Its docs are " +"quite detailed and thorough, and full of examples. Having gone through this " +"tutorial, you should easily digest them without feeling overwhelmed." +msgstr "" + +#: ../Doc/howto/clinic.rst:3 +msgid "Argument Clinic How-To" +msgstr "" + +#: ../Doc/howto/clinic.rst:5 +msgid "Larry Hastings" +msgstr "" + +#: ../Doc/howto/clinic.rst:0 ../Doc/howto/cporting.rst:0 +#: ../Doc/howto/curses.rst:0 ../Doc/howto/descriptor.rst:11 +#: ../Doc/howto/pyporting.rst:0 ../Doc/howto/regex.rst:0 +#: ../Doc/howto/sockets.rst:0 +msgid "Abstract" +msgstr "" + +#: ../Doc/howto/clinic.rst:10 +msgid "" +"Argument Clinic is a preprocessor for CPython C files. Its purpose is to " +"automate all the boilerplate involved with writing argument parsing code for " +"\"builtins\". This document shows you how to convert your first C function " +"to work with Argument Clinic, and then introduces some advanced topics on " +"Argument Clinic usage." +msgstr "" + +#: ../Doc/howto/clinic.rst:17 +msgid "" +"Currently Argument Clinic is considered internal-only for CPython. Its use " +"is not supported for files outside CPython, and no guarantees are made " +"regarding backwards compatibility for future versions. In other words: if " +"you maintain an external C extension for CPython, you're welcome to " +"experiment with Argument Clinic in your own code. But the version of " +"Argument Clinic that ships with CPython 3.5 *could* be totally incompatible " +"and break all your code." +msgstr "" + +#: ../Doc/howto/clinic.rst:27 +msgid "The Goals Of Argument Clinic" +msgstr "" + +#: ../Doc/howto/clinic.rst:29 +msgid "" +"Argument Clinic's primary goal is to take over responsibility for all " +"argument parsing code inside CPython. This means that, when you convert a " +"function to work with Argument Clinic, that function should no longer do any " +"of its own argument parsing--the code generated by Argument Clinic should be " +"a \"black box\" to you, where CPython calls in at the top, and your code " +"gets called at the bottom, with ``PyObject *args`` (and maybe ``PyObject " +"*kwargs``) magically converted into the C variables and types you need." +msgstr "" + +#: ../Doc/howto/clinic.rst:39 +msgid "" +"In order for Argument Clinic to accomplish its primary goal, it must be easy " +"to use. Currently, working with CPython's argument parsing library is a " +"chore, requiring maintaining redundant information in a surprising number of " +"places. When you use Argument Clinic, you don't have to repeat yourself." +msgstr "" + +#: ../Doc/howto/clinic.rst:45 +msgid "" +"Obviously, no one would want to use Argument Clinic unless it's solving " +"their problem--and without creating new problems of its own. So it's " +"paramount that Argument Clinic generate correct code. It'd be nice if the " +"code was faster, too, but at the very least it should not introduce a major " +"speed regression. (Eventually Argument Clinic *should* make a major speedup " +"possible--we could rewrite its code generator to produce tailor-made " +"argument parsing code, rather than calling the general-purpose CPython " +"argument parsing library. That would make for the fastest argument parsing " +"possible!)" +msgstr "" + +#: ../Doc/howto/clinic.rst:57 +msgid "" +"Additionally, Argument Clinic must be flexible enough to work with any " +"approach to argument parsing. Python has some functions with some very " +"strange parsing behaviors; Argument Clinic's goal is to support all of them." +msgstr "" + +#: ../Doc/howto/clinic.rst:62 +msgid "" +"Finally, the original motivation for Argument Clinic was to provide " +"introspection \"signatures\" for CPython builtins. It used to be, the " +"introspection query functions would throw an exception if you passed in a " +"builtin. With Argument Clinic, that's a thing of the past!" +msgstr "" + +#: ../Doc/howto/clinic.rst:68 +msgid "" +"One idea you should keep in mind, as you work with Argument Clinic: the more " +"information you give it, the better job it'll be able to do. Argument Clinic " +"is admittedly relatively simple right now. But as it evolves it will get " +"more sophisticated, and it should be able to do many interesting and smart " +"things with all the information you give it." +msgstr "" + +#: ../Doc/howto/clinic.rst:78 +msgid "Basic Concepts And Usage" +msgstr "" + +#: ../Doc/howto/clinic.rst:80 +msgid "" +"Argument Clinic ships with CPython; you'll find it in ``Tools/clinic/clinic." +"py``. If you run that script, specifying a C file as an argument::" +msgstr "" + +#: ../Doc/howto/clinic.rst:85 +msgid "" +"Argument Clinic will scan over the file looking for lines that look exactly " +"like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:90 +msgid "" +"When it finds one, it reads everything up to a line that looks exactly like " +"this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:95 +msgid "" +"Everything in between these two lines is input for Argument Clinic. All of " +"these lines, including the beginning and ending comment lines, are " +"collectively called an Argument Clinic \"block\"." +msgstr "" + +#: ../Doc/howto/clinic.rst:99 +msgid "" +"When Argument Clinic parses one of these blocks, it generates output. This " +"output is rewritten into the C file immediately after the block, followed by " +"a comment containing a checksum. The Argument Clinic block now looks like " +"this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:110 +msgid "" +"If you run Argument Clinic on the same file a second time, Argument Clinic " +"will discard the old output and write out the new output with a fresh " +"checksum line. However, if the input hasn't changed, the output won't " +"change either." +msgstr "" + +#: ../Doc/howto/clinic.rst:114 +msgid "" +"You should never modify the output portion of an Argument Clinic block. " +"Instead, change the input until it produces the output you want. (That's " +"the purpose of the checksum--to detect if someone changed the output, as " +"these edits would be lost the next time Argument Clinic writes out fresh " +"output.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:119 +msgid "" +"For the sake of clarity, here's the terminology we'll use with Argument " +"Clinic:" +msgstr "" + +#: ../Doc/howto/clinic.rst:121 +msgid "" +"The first line of the comment (``/*[clinic input]``) is the *start line*." +msgstr "" + +#: ../Doc/howto/clinic.rst:122 +msgid "" +"The last line of the initial comment (``[clinic start generated code]*/``) " +"is the *end line*." +msgstr "" + +#: ../Doc/howto/clinic.rst:123 +msgid "" +"The last line (``/*[clinic end generated code: checksum=...]*/``) is the " +"*checksum line*." +msgstr "" + +#: ../Doc/howto/clinic.rst:124 +msgid "In between the start line and the end line is the *input*." +msgstr "" + +#: ../Doc/howto/clinic.rst:125 +msgid "In between the end line and the checksum line is the *output*." +msgstr "" + +#: ../Doc/howto/clinic.rst:126 +msgid "" +"All the text collectively, from the start line to the checksum line " +"inclusively, is the *block*. (A block that hasn't been successfully " +"processed by Argument Clinic yet doesn't have output or a checksum line, but " +"it's still considered a block.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:133 +msgid "Converting Your First Function" +msgstr "" + +#: ../Doc/howto/clinic.rst:135 +msgid "" +"The best way to get a sense of how Argument Clinic works is to convert a " +"function to work with it. Here, then, are the bare minimum steps you'd need " +"to follow to convert a function to work with Argument Clinic. Note that for " +"code you plan to check in to CPython, you really should take the conversion " +"farther, using some of the advanced concepts you'll see later on in the " +"document (like \"return converters\" and \"self converters\"). But we'll " +"keep it simple for this walkthrough so you can learn." +msgstr "" + +#: ../Doc/howto/clinic.rst:144 +msgid "Let's dive in!" +msgstr "" + +#: ../Doc/howto/clinic.rst:146 +msgid "" +"Make sure you're working with a freshly updated checkout of the CPython " +"trunk." +msgstr "" + +#: ../Doc/howto/clinic.rst:149 +msgid "" +"Find a Python builtin that calls either :c:func:`PyArg_ParseTuple` or :c:" +"func:`PyArg_ParseTupleAndKeywords`, and hasn't been converted to work with " +"Argument Clinic yet. For my example I'm using ``_pickle.Pickler.dump()``." +msgstr "" + +#: ../Doc/howto/clinic.rst:154 +msgid "" +"If the call to the ``PyArg_Parse`` function uses any of the following format " +"units:" +msgstr "" + +#: ../Doc/howto/clinic.rst:166 +msgid "" +"or if it has multiple calls to :c:func:`PyArg_ParseTuple`, you should choose " +"a different function. Argument Clinic *does* support all of these " +"scenarios. But these are advanced topics--let's do something simpler for " +"your first function." +msgstr "" + +#: ../Doc/howto/clinic.rst:171 +msgid "" +"Also, if the function has multiple calls to :c:func:`PyArg_ParseTuple` or :c:" +"func:`PyArg_ParseTupleAndKeywords` where it supports different types for the " +"same argument, or if the function uses something besides PyArg_Parse " +"functions to parse its arguments, it probably isn't suitable for conversion " +"to Argument Clinic. Argument Clinic doesn't support generic functions or " +"polymorphic parameters." +msgstr "" + +#: ../Doc/howto/clinic.rst:178 +msgid "Add the following boilerplate above the function, creating our block::" +msgstr "" + +#: ../Doc/howto/clinic.rst:183 +msgid "" +"Cut the docstring and paste it in between the ``[clinic]`` lines, removing " +"all the junk that makes it a properly quoted C string. When you're done you " +"should have just the text, based at the left margin, with no line wider than " +"80 characters. (Argument Clinic will preserve indents inside the docstring.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:189 +msgid "" +"If the old docstring had a first line that looked like a function signature, " +"throw that line away. (The docstring doesn't need it anymore--when you use " +"``help()`` on your builtin in the future, the first line will be built " +"automatically based on the function's signature.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:195 ../Doc/howto/clinic.rst:216 +#: ../Doc/howto/clinic.rst:240 ../Doc/howto/clinic.rst:294 +#: ../Doc/howto/clinic.rst:334 ../Doc/howto/clinic.rst:361 +#: ../Doc/howto/clinic.rst:470 ../Doc/howto/clinic.rst:522 +msgid "Sample::" +msgstr "" + +#: ../Doc/howto/clinic.rst:201 +msgid "" +"If your docstring doesn't have a \"summary\" line, Argument Clinic will " +"complain. So let's make sure it has one. The \"summary\" line should be a " +"paragraph consisting of a single 80-column line at the beginning of the " +"docstring." +msgstr "" + +#: ../Doc/howto/clinic.rst:206 +msgid "" +"(Our example docstring consists solely of a summary line, so the sample code " +"doesn't have to change for this step.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:209 +msgid "" +"Above the docstring, enter the name of the function, followed by a blank " +"line. This should be the Python name of the function, and should be the " +"full dotted path to the function--it should start with the name of the " +"module, include any sub-modules, and if the function is a method on a class " +"it should include the class name too." +msgstr "" + +#: ../Doc/howto/clinic.rst:224 +msgid "" +"If this is the first time that module or class has been used with Argument " +"Clinic in this C file, you must declare the module and/or class. Proper " +"Argument Clinic hygiene prefers declaring these in a separate block " +"somewhere near the top of the C file, in the same way that include files and " +"statics go at the top. (In our sample code we'll just show the two blocks " +"next to each other.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:232 +msgid "" +"The name of the class and module should be the same as the one seen by " +"Python. Check the name defined in the :c:type:`PyModuleDef` or :c:type:" +"`PyTypeObject` as appropriate." +msgstr "" + +#: ../Doc/howto/clinic.rst:236 +msgid "" +"When you declare a class, you must also specify two aspects of its type in " +"C: the type declaration you'd use for a pointer to an instance of this " +"class, and a pointer to the :c:type:`PyTypeObject` for this class." +msgstr "" + +#: ../Doc/howto/clinic.rst:256 +msgid "" +"Declare each of the parameters to the function. Each parameter should get " +"its own line. All the parameter lines should be indented from the function " +"name and the docstring." +msgstr "" + +#: ../Doc/howto/clinic.rst:260 +msgid "The general form of these parameter lines is as follows::" +msgstr "" + +#: ../Doc/howto/clinic.rst:264 +msgid "If the parameter has a default value, add that after the converter::" +msgstr "" + +#: ../Doc/howto/clinic.rst:269 +msgid "" +"Argument Clinic's support for \"default values\" is quite sophisticated; " +"please see :ref:`the section below on default values ` for " +"more information." +msgstr "" + +#: ../Doc/howto/clinic.rst:273 +msgid "Add a blank line below the parameters." +msgstr "" + +#: ../Doc/howto/clinic.rst:275 +msgid "" +"What's a \"converter\"? It establishes both the type of the variable used " +"in C, and the method to convert the Python value into a C value at runtime. " +"For now you're going to use what's called a \"legacy converter\"--a " +"convenience syntax intended to make porting old code into Argument Clinic " +"easier." +msgstr "" + +#: ../Doc/howto/clinic.rst:282 +msgid "" +"For each parameter, copy the \"format unit\" for that parameter from the " +"``PyArg_Parse()`` format argument and specify *that* as its converter, as a " +"quoted string. (\"format unit\" is the formal name for the one-to-three " +"character substring of the ``format`` parameter that tells the argument " +"parsing function what the type of the variable is and how to convert it. " +"For more on format units please see :ref:`arg-parsing`.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:291 +msgid "" +"For multicharacter format units like ``z#``, use the entire two-or-three " +"character string." +msgstr "" + +#: ../Doc/howto/clinic.rst:309 +msgid "" +"If your function has ``|`` in the format string, meaning some parameters " +"have default values, you can ignore it. Argument Clinic infers which " +"parameters are optional based on whether or not they have default values." +msgstr "" + +#: ../Doc/howto/clinic.rst:314 +msgid "" +"If your function has ``$`` in the format string, meaning it takes keyword-" +"only arguments, specify ``*`` on a line by itself before the first keyword-" +"only argument, indented the same as the parameter lines." +msgstr "" + +#: ../Doc/howto/clinic.rst:319 +msgid "(``_pickle.Pickler.dump`` has neither, so our sample is unchanged.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:322 +msgid "" +"If the existing C function calls :c:func:`PyArg_ParseTuple` (as opposed to :" +"c:func:`PyArg_ParseTupleAndKeywords`), then all its arguments are positional-" +"only." +msgstr "" + +#: ../Doc/howto/clinic.rst:326 +msgid "" +"To mark all parameters as positional-only in Argument Clinic, add a ``/`` on " +"a line by itself after the last parameter, indented the same as the " +"parameter lines." +msgstr "" + +#: ../Doc/howto/clinic.rst:330 +msgid "" +"Currently this is all-or-nothing; either all parameters are positional-only, " +"or none of them are. (In the future Argument Clinic may relax this " +"restriction.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:350 +msgid "" +"It's helpful to write a per-parameter docstring for each parameter. But per-" +"parameter docstrings are optional; you can skip this step if you prefer." +msgstr "" + +#: ../Doc/howto/clinic.rst:354 +msgid "" +"Here's how to add a per-parameter docstring. The first line of the per-" +"parameter docstring must be indented further than the parameter definition. " +"The left margin of this first line establishes the left margin for the whole " +"per-parameter docstring; all the text you write will be outdented by this " +"amount. You can write as much text as you like, across multiple lines if " +"you wish." +msgstr "" + +#: ../Doc/howto/clinic.rst:378 +msgid "" +"Save and close the file, then run ``Tools/clinic/clinic.py`` on it. With " +"luck everything worked and your block now has output! Reopen the file in " +"your text editor to see::" +msgstr "" + +#: ../Doc/howto/clinic.rst:406 +msgid "" +"Obviously, if Argument Clinic didn't produce any output, it's because it " +"found an error in your input. Keep fixing your errors and retrying until " +"Argument Clinic processes your file without complaint." +msgstr "" + +#: ../Doc/howto/clinic.rst:410 +msgid "" +"Double-check that the argument-parsing code Argument Clinic generated looks " +"basically the same as the existing code." +msgstr "" + +#: ../Doc/howto/clinic.rst:413 +msgid "" +"First, ensure both places use the same argument-parsing function. The " +"existing code must call either :c:func:`PyArg_ParseTuple` or :c:func:" +"`PyArg_ParseTupleAndKeywords`; ensure that the code generated by Argument " +"Clinic calls the *exact* same function." +msgstr "" + +#: ../Doc/howto/clinic.rst:419 +msgid "" +"Second, the format string passed in to :c:func:`PyArg_ParseTuple` or :c:func:" +"`PyArg_ParseTupleAndKeywords` should be *exactly* the same as the hand-" +"written one in the existing function, up to the colon or semi-colon." +msgstr "" + +#: ../Doc/howto/clinic.rst:424 +msgid "" +"(Argument Clinic always generates its format strings with a ``:`` followed " +"by the name of the function. If the existing code's format string ends with " +"``;``, to provide usage help, this change is harmless--don't worry about it.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:429 +msgid "" +"Third, for parameters whose format units require two arguments (like a " +"length variable, or an encoding string, or a pointer to a conversion " +"function), ensure that the second argument is *exactly* the same between the " +"two invocations." +msgstr "" + +#: ../Doc/howto/clinic.rst:434 +msgid "" +"Fourth, inside the output portion of the block you'll find a preprocessor " +"macro defining the appropriate static :c:type:`PyMethodDef` structure for " +"this builtin::" +msgstr "" + +#: ../Doc/howto/clinic.rst:441 +msgid "" +"This static structure should be *exactly* the same as the existing static :c:" +"type:`PyMethodDef` structure for this builtin." +msgstr "" + +#: ../Doc/howto/clinic.rst:444 +msgid "" +"If any of these items differ in *any way*, adjust your Argument Clinic " +"function specification and rerun ``Tools/clinic/clinic.py`` until they *are* " +"the same." +msgstr "" + +#: ../Doc/howto/clinic.rst:449 +msgid "" +"Notice that the last line of its output is the declaration of your \"impl\" " +"function. This is where the builtin's implementation goes. Delete the " +"existing prototype of the function you're modifying, but leave the opening " +"curly brace. Now delete its argument parsing code and the declarations of " +"all the variables it dumps the arguments into. Notice how the Python " +"arguments are now arguments to this impl function; if the implementation " +"used different names for these variables, fix it." +msgstr "" + +#: ../Doc/howto/clinic.rst:457 +msgid "" +"Let's reiterate, just because it's kind of weird. Your code should now look " +"like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:466 +msgid "" +"Argument Clinic generated the checksum line and the function prototype just " +"above it. You should write the opening (and closing) curly braces for the " +"function, and the implementation inside." +msgstr "" + +#: ../Doc/howto/clinic.rst:511 +msgid "" +"Remember the macro with the :c:type:`PyMethodDef` structure for this " +"function? Find the existing :c:type:`PyMethodDef` structure for this " +"function and replace it with a reference to the macro. (If the builtin is " +"at module scope, this will probably be very near the end of the file; if the " +"builtin is a class method, this will probably be below but relatively near " +"to the implementation.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:518 +msgid "" +"Note that the body of the macro contains a trailing comma. So when you " +"replace the existing static :c:type:`PyMethodDef` structure with the macro, " +"*don't* add a comma to the end." +msgstr "" + +#: ../Doc/howto/clinic.rst:531 +msgid "" +"Compile, then run the relevant portions of the regression-test suite. This " +"change should not introduce any new compile-time warnings or errors, and " +"there should be no externally-visible change to Python's behavior." +msgstr "" + +#: ../Doc/howto/clinic.rst:535 +msgid "" +"Well, except for one difference: ``inspect.signature()`` run on your " +"function should now provide a valid signature!" +msgstr "" + +#: ../Doc/howto/clinic.rst:538 +msgid "" +"Congratulations, you've ported your first function to work with Argument " +"Clinic!" +msgstr "" + +#: ../Doc/howto/clinic.rst:541 +msgid "Advanced Topics" +msgstr "" + +#: ../Doc/howto/clinic.rst:543 +msgid "" +"Now that you've had some experience working with Argument Clinic, it's time " +"for some advanced topics." +msgstr "" + +#: ../Doc/howto/clinic.rst:548 +msgid "Symbolic default values" +msgstr "" + +#: ../Doc/howto/clinic.rst:550 +msgid "" +"The default value you provide for a parameter can't be any arbitrary " +"expression. Currently the following are explicitly supported:" +msgstr "" + +#: ../Doc/howto/clinic.rst:553 +msgid "Numeric constants (integer and float)" +msgstr "" + +#: ../Doc/howto/clinic.rst:554 +msgid "String constants" +msgstr "" + +#: ../Doc/howto/clinic.rst:555 +msgid "``True``, ``False``, and ``None``" +msgstr "" + +#: ../Doc/howto/clinic.rst:556 +msgid "" +"Simple symbolic constants like ``sys.maxsize``, which must start with the " +"name of the module" +msgstr "" + +#: ../Doc/howto/clinic.rst:559 +msgid "" +"In case you're curious, this is implemented in ``from_builtin()`` in ``Lib/" +"inspect.py``." +msgstr "" + +#: ../Doc/howto/clinic.rst:562 +msgid "" +"(In the future, this may need to get even more elaborate, to allow full " +"expressions like ``CONSTANT - 1``.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:567 +msgid "Renaming the C functions and variables generated by Argument Clinic" +msgstr "" + +#: ../Doc/howto/clinic.rst:569 +msgid "" +"Argument Clinic automatically names the functions it generates for you. " +"Occasionally this may cause a problem, if the generated name collides with " +"the name of an existing C function. There's an easy solution: override the " +"names used for the C functions. Just add the keyword ``\"as\"`` to your " +"function declaration line, followed by the function name you wish to use. " +"Argument Clinic will use that function name for the base (generated) " +"function, then add ``\"_impl\"`` to the end and use that for the name of the " +"impl function." +msgstr "" + +#: ../Doc/howto/clinic.rst:577 +msgid "" +"For example, if we wanted to rename the C function names generated for " +"``pickle.Pickler.dump``, it'd look like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:585 +msgid "" +"The base function would now be named ``pickler_dumper()``, and the impl " +"function would now be named ``pickler_dumper_impl()``." +msgstr "" + +#: ../Doc/howto/clinic.rst:589 +msgid "" +"Similarly, you may have a problem where you want to give a parameter a " +"specific Python name, but that name may be inconvenient in C. Argument " +"Clinic allows you to give a parameter different names in Python and in C, " +"using the same ``\"as\"`` syntax::" +msgstr "" + +#: ../Doc/howto/clinic.rst:603 +msgid "" +"Here, the name used in Python (in the signature and the ``keywords`` array) " +"would be ``file``, but the C variable would be named ``file_obj``." +msgstr "" + +#: ../Doc/howto/clinic.rst:606 +msgid "You can use this to rename the ``self`` parameter too!" +msgstr "" + +#: ../Doc/howto/clinic.rst:610 +msgid "Converting functions using PyArg_UnpackTuple" +msgstr "" + +#: ../Doc/howto/clinic.rst:612 +msgid "" +"To convert a function parsing its arguments with :c:func:" +"`PyArg_UnpackTuple`, simply write out all the arguments, specifying each as " +"an ``object``. You may specify the ``type`` argument to cast the type as " +"appropriate. All arguments should be marked positional-only (add a ``/`` on " +"a line by itself after the last argument)." +msgstr "" + +#: ../Doc/howto/clinic.rst:618 +msgid "" +"Currently the generated code will use :c:func:`PyArg_ParseTuple`, but this " +"will change soon." +msgstr "" + +#: ../Doc/howto/clinic.rst:622 +msgid "Optional Groups" +msgstr "" + +#: ../Doc/howto/clinic.rst:624 +msgid "" +"Some legacy functions have a tricky approach to parsing their arguments: " +"they count the number of positional arguments, then use a ``switch`` " +"statement to call one of several different :c:func:`PyArg_ParseTuple` calls " +"depending on how many positional arguments there are. (These functions " +"cannot accept keyword-only arguments.) This approach was used to simulate " +"optional arguments back before :c:func:`PyArg_ParseTupleAndKeywords` was " +"created." +msgstr "" + +#: ../Doc/howto/clinic.rst:631 +msgid "" +"While functions using this approach can often be converted to use :c:func:" +"`PyArg_ParseTupleAndKeywords`, optional arguments, and default values, it's " +"not always possible. Some of these legacy functions have behaviors :c:func:" +"`PyArg_ParseTupleAndKeywords` doesn't directly support. The most obvious " +"example is the builtin function ``range()``, which has an optional argument " +"on the *left* side of its required argument! Another example is ``curses." +"window.addch()``, which has a group of two arguments that must always be " +"specified together. (The arguments are called ``x`` and ``y``; if you call " +"the function passing in ``x``, you must also pass in ``y``--and if you don't " +"pass in ``x`` you may not pass in ``y`` either.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:643 +msgid "" +"In any case, the goal of Argument Clinic is to support argument parsing for " +"all existing CPython builtins without changing their semantics. Therefore " +"Argument Clinic supports this alternate approach to parsing, using what are " +"called *optional groups*. Optional groups are groups of arguments that must " +"all be passed in together. They can be to the left or the right of the " +"required arguments. They can *only* be used with positional-only parameters." +msgstr "" + +#: ../Doc/howto/clinic.rst:651 +msgid "" +"Optional groups are *only* intended for use when converting functions that " +"make multiple calls to :c:func:`PyArg_ParseTuple`! Functions that use *any* " +"other approach for parsing arguments should *almost never* be converted to " +"Argument Clinic using optional groups. Functions using optional groups " +"currently cannot have accurate signatures in Python, because Python just " +"doesn't understand the concept. Please avoid using optional groups wherever " +"possible." +msgstr "" + +#: ../Doc/howto/clinic.rst:660 +msgid "" +"To specify an optional group, add a ``[`` on a line by itself before the " +"parameters you wish to group together, and a ``]`` on a line by itself after " +"these parameters. As an example, here's how ``curses.window.addch`` uses " +"optional groups to make the first two parameters and the last parameter " +"optional::" +msgstr "" + +#: ../Doc/howto/clinic.rst:689 +msgid "Notes:" +msgstr "" + +#: ../Doc/howto/clinic.rst:691 +msgid "" +"For every optional group, one additional parameter will be passed into the " +"impl function representing the group. The parameter will be an int named " +"``group_{direction}_{number}``, where ``{direction}`` is either ``right`` or " +"``left`` depending on whether the group is before or after the required " +"parameters, and ``{number}`` is a monotonically increasing number (starting " +"at 1) indicating how far away the group is from the required parameters. " +"When the impl is called, this parameter will be set to zero if this group " +"was unused, and set to non-zero if this group was used. (By used or unused, " +"I mean whether or not the parameters received arguments in this invocation.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:702 +msgid "" +"If there are no required arguments, the optional groups will behave as if " +"they're to the right of the required arguments." +msgstr "" + +#: ../Doc/howto/clinic.rst:705 +msgid "" +"In the case of ambiguity, the argument parsing code favors parameters on the " +"left (before the required parameters)." +msgstr "" + +#: ../Doc/howto/clinic.rst:708 +msgid "Optional groups can only contain positional-only parameters." +msgstr "" + +#: ../Doc/howto/clinic.rst:710 +msgid "" +"Optional groups are *only* intended for legacy code. Please do not use " +"optional groups for new code." +msgstr "" + +#: ../Doc/howto/clinic.rst:715 +msgid "Using real Argument Clinic converters, instead of \"legacy converters\"" +msgstr "" + +#: ../Doc/howto/clinic.rst:717 +msgid "" +"To save time, and to minimize how much you need to learn to achieve your " +"first port to Argument Clinic, the walkthrough above tells you to use " +"\"legacy converters\". \"Legacy converters\" are a convenience, designed " +"explicitly to make porting existing code to Argument Clinic easier. And to " +"be clear, their use is acceptable when porting code for Python 3.4." +msgstr "" + +#: ../Doc/howto/clinic.rst:724 +msgid "" +"However, in the long term we probably want all our blocks to use Argument " +"Clinic's real syntax for converters. Why? A couple reasons:" +msgstr "" + +#: ../Doc/howto/clinic.rst:728 +msgid "" +"The proper converters are far easier to read and clearer in their intent." +msgstr "" + +#: ../Doc/howto/clinic.rst:729 +msgid "" +"There are some format units that are unsupported as \"legacy converters\", " +"because they require arguments, and the legacy converter syntax doesn't " +"support specifying arguments." +msgstr "" + +#: ../Doc/howto/clinic.rst:732 +msgid "" +"In the future we may have a new argument parsing library that isn't " +"restricted to what :c:func:`PyArg_ParseTuple` supports; this flexibility " +"won't be available to parameters using legacy converters." +msgstr "" + +#: ../Doc/howto/clinic.rst:736 +msgid "" +"Therefore, if you don't mind a little extra effort, please use the normal " +"converters instead of legacy converters." +msgstr "" + +#: ../Doc/howto/clinic.rst:739 +msgid "" +"In a nutshell, the syntax for Argument Clinic (non-legacy) converters looks " +"like a Python function call. However, if there are no explicit arguments to " +"the function (all functions take their default values), you may omit the " +"parentheses. Thus ``bool`` and ``bool()`` are exactly the same converters." +msgstr "" + +#: ../Doc/howto/clinic.rst:745 +msgid "" +"All arguments to Argument Clinic converters are keyword-only. All Argument " +"Clinic converters accept the following arguments:" +msgstr "" + +#: ../Doc/howto/clinic.rst:753 ../Doc/howto/clinic.rst:1223 +msgid "``c_default``" +msgstr "" + +#: ../Doc/howto/clinic.rst:749 +msgid "" +"The default value for this parameter when defined in C. Specifically, this " +"will be the initializer for the variable declared in the \"parse function" +"\". See :ref:`the section on default values ` for how to " +"use this. Specified as a string." +msgstr "" + +#: ../Doc/howto/clinic.rst:758 +msgid "``annotation``" +msgstr "" + +#: ../Doc/howto/clinic.rst:756 +msgid "" +"The annotation value for this parameter. Not currently supported, because " +"PEP 8 mandates that the Python library may not use annotations." +msgstr "" + +#: ../Doc/howto/clinic.rst:760 +msgid "" +"In addition, some converters accept additional arguments. Here is a list of " +"these arguments, along with their meanings:" +msgstr "" + +#: ../Doc/howto/clinic.rst:769 +msgid "``accept``" +msgstr "" + +#: ../Doc/howto/clinic.rst:764 +msgid "" +"A set of Python types (and possibly pseudo-types); this restricts the " +"allowable Python argument to values of these types. (This is not a general-" +"purpose facility; as a rule it only supports specific lists of types as " +"shown in the legacy converter table.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:769 +msgid "To accept ``None``, add ``NoneType`` to this set." +msgstr "" + +#: ../Doc/howto/clinic.rst:774 +msgid "``bitwise``" +msgstr "" + +#: ../Doc/howto/clinic.rst:772 +msgid "" +"Only supported for unsigned integers. The native integer value of this " +"Python argument will be written to the parameter without any range checking, " +"even for negative values." +msgstr "" + +#: ../Doc/howto/clinic.rst:779 ../Doc/howto/clinic.rst:1237 +msgid "``converter``" +msgstr "" + +#: ../Doc/howto/clinic.rst:777 +msgid "" +"Only supported by the ``object`` converter. Specifies the name of a :ref:`C " +"\"converter function\" ` to use to convert this object to a " +"native type." +msgstr "" + +#: ../Doc/howto/clinic.rst:784 +msgid "``encoding``" +msgstr "" + +#: ../Doc/howto/clinic.rst:782 +msgid "" +"Only supported for strings. Specifies the encoding to use when converting " +"this string from a Python str (Unicode) value into a C ``char *`` value." +msgstr "" + +#: ../Doc/howto/clinic.rst:788 +msgid "``subclass_of``" +msgstr "" + +#: ../Doc/howto/clinic.rst:787 +msgid "" +"Only supported for the ``object`` converter. Requires that the Python value " +"be a subclass of a Python type, as expressed in C." +msgstr "" + +#: ../Doc/howto/clinic.rst:793 ../Doc/howto/clinic.rst:1209 +msgid "``type``" +msgstr "" + +#: ../Doc/howto/clinic.rst:791 +msgid "" +"Only supported for the ``object`` and ``self`` converters. Specifies the C " +"type that will be used to declare the variable. Default value is ``" +"\"PyObject *\"``." +msgstr "" + +#: ../Doc/howto/clinic.rst:799 +msgid "``zeroes``" +msgstr "" + +#: ../Doc/howto/clinic.rst:796 +msgid "" +"Only supported for strings. If true, embedded NUL bytes (``'\\\\0'``) are " +"permitted inside the value. The length of the string will be passed in to " +"the impl function, just after the string parameter, as a parameter named " +"``_length``." +msgstr "" + +#: ../Doc/howto/clinic.rst:801 +msgid "" +"Please note, not every possible combination of arguments will work. Usually " +"these arguments are implemented by specific ``PyArg_ParseTuple`` *format " +"units*, with specific behavior. For example, currently you cannot call " +"``unsigned_short`` without also specifying ``bitwise=True``. Although it's " +"perfectly reasonable to think this would work, these semantics don't map to " +"any existing format unit. So Argument Clinic doesn't support it. (Or, at " +"least, not yet.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:809 +msgid "" +"Below is a table showing the mapping of legacy converters into real Argument " +"Clinic converters. On the left is the legacy converter, on the right is the " +"text you'd replace it with." +msgstr "" + +#: ../Doc/howto/clinic.rst:814 +msgid "``'B'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:814 +msgid "``unsigned_char(bitwise=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:815 +msgid "``'b'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:815 +msgid "``unsigned_char``" +msgstr "" + +#: ../Doc/howto/clinic.rst:816 +msgid "``'c'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:816 +msgid "``char``" +msgstr "" + +#: ../Doc/howto/clinic.rst:817 +msgid "``'C'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:817 +msgid "``int(accept={str})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:818 +msgid "``'d'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:818 +msgid "``double``" +msgstr "" + +#: ../Doc/howto/clinic.rst:819 +msgid "``'D'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:819 +msgid "``Py_complex``" +msgstr "" + +#: ../Doc/howto/clinic.rst:820 +msgid "``'es'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:820 +msgid "``str(encoding='name_of_encoding')``" +msgstr "" + +#: ../Doc/howto/clinic.rst:821 +msgid "``'es#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:821 +msgid "``str(encoding='name_of_encoding', zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:822 +msgid "``'et'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:822 +msgid "``str(encoding='name_of_encoding', accept={bytes, bytearray, str})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:823 +msgid "``'et#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:823 +msgid "" +"``str(encoding='name_of_encoding', accept={bytes, bytearray, str}, " +"zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:824 +msgid "``'f'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:824 +msgid "``float``" +msgstr "" + +#: ../Doc/howto/clinic.rst:825 +msgid "``'h'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:825 +msgid "``short``" +msgstr "" + +#: ../Doc/howto/clinic.rst:826 +msgid "``'H'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:826 +msgid "``unsigned_short(bitwise=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:827 +msgid "``'i'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:827 +msgid "``int``" +msgstr "" + +#: ../Doc/howto/clinic.rst:828 +msgid "``'I'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:828 +msgid "``unsigned_int(bitwise=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:829 +msgid "``'k'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:829 +msgid "``unsigned_long(bitwise=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:830 +msgid "``'K'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:830 +msgid "``unsigned_long_long(bitwise=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:831 +msgid "``'l'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:831 +msgid "``long``" +msgstr "" + +#: ../Doc/howto/clinic.rst:832 +msgid "``'L'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:832 +msgid "``long long``" +msgstr "" + +#: ../Doc/howto/clinic.rst:833 +msgid "``'n'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:833 +msgid "``Py_ssize_t``" +msgstr "" + +#: ../Doc/howto/clinic.rst:834 +msgid "``'O'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:834 +msgid "``object``" +msgstr "" + +#: ../Doc/howto/clinic.rst:835 +msgid "``'O!'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:835 +msgid "``object(subclass_of='&PySomething_Type')``" +msgstr "" + +#: ../Doc/howto/clinic.rst:836 +msgid "``'O&'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:836 +msgid "``object(converter='name_of_c_function')``" +msgstr "" + +#: ../Doc/howto/clinic.rst:837 +msgid "``'p'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:837 +msgid "``bool``" +msgstr "" + +#: ../Doc/howto/clinic.rst:838 +msgid "``'S'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:838 +msgid "``PyBytesObject``" +msgstr "" + +#: ../Doc/howto/clinic.rst:839 +msgid "``'s'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:839 +msgid "``str``" +msgstr "" + +#: ../Doc/howto/clinic.rst:840 +msgid "``'s#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:840 +msgid "``str(zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:841 +msgid "``'s*'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:841 +msgid "``Py_buffer(accept={buffer, str})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:842 +msgid "``'U'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:842 +msgid "``unicode``" +msgstr "" + +#: ../Doc/howto/clinic.rst:843 +msgid "``'u'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:843 +msgid "``Py_UNICODE``" +msgstr "" + +#: ../Doc/howto/clinic.rst:844 +msgid "``'u#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:844 +msgid "``Py_UNICODE(zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:845 +msgid "``'w*'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:845 +msgid "``Py_buffer(accept={rwbuffer})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:846 +msgid "``'Y'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:846 +msgid "``PyByteArrayObject``" +msgstr "" + +#: ../Doc/howto/clinic.rst:847 +msgid "``'y'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:847 +msgid "``str(accept={bytes})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:848 +msgid "``'y#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:848 +msgid "``str(accept={robuffer}, zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:849 +msgid "``'y*'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:849 +msgid "``Py_buffer``" +msgstr "" + +#: ../Doc/howto/clinic.rst:850 +msgid "``'Z'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:850 +msgid "``Py_UNICODE(accept={str, NoneType})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:851 +msgid "``'Z#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:851 +msgid "``Py_UNICODE(accept={str, NoneType}, zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:852 +msgid "``'z'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:852 +msgid "``str(accept={str, NoneType})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:853 +msgid "``'z#'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:853 +msgid "``str(accept={str, NoneType}, zeroes=True)``" +msgstr "" + +#: ../Doc/howto/clinic.rst:854 +msgid "``'z*'``" +msgstr "" + +#: ../Doc/howto/clinic.rst:854 +msgid "``Py_buffer(accept={buffer, str, NoneType})``" +msgstr "" + +#: ../Doc/howto/clinic.rst:857 +msgid "" +"As an example, here's our sample ``pickle.Pickler.dump`` using the proper " +"converter::" +msgstr "" + +#: ../Doc/howto/clinic.rst:870 +msgid "" +"Argument Clinic will show you all the converters it has available. For each " +"converter it'll show you all the parameters it accepts, along with the " +"default value for each parameter. Just run ``Tools/clinic/clinic.py --" +"converters`` to see the full list." +msgstr "" + +#: ../Doc/howto/clinic.rst:876 +msgid "Py_buffer" +msgstr "" + +#: ../Doc/howto/clinic.rst:878 +msgid "" +"When using the ``Py_buffer`` converter (or the ``'s*'``, ``'w*'``, ``'*y'``, " +"or ``'z*'`` legacy converters), you *must* not call :c:func:" +"`PyBuffer_Release` on the provided buffer. Argument Clinic generates code " +"that does it for you (in the parsing function)." +msgstr "" + +#: ../Doc/howto/clinic.rst:886 +msgid "Advanced converters" +msgstr "" + +#: ../Doc/howto/clinic.rst:888 +msgid "" +"Remember those format units you skipped for your first time because they " +"were advanced? Here's how to handle those too." +msgstr "" + +#: ../Doc/howto/clinic.rst:891 +msgid "" +"The trick is, all those format units take arguments--either conversion " +"functions, or types, or strings specifying an encoding. (But \"legacy " +"converters\" don't support arguments. That's why we skipped them for your " +"first function.) The argument you specified to the format unit is now an " +"argument to the converter; this argument is either ``converter`` (for " +"``O&``), ``subclass_of`` (for ``O!``), or ``encoding`` (for all the format " +"units that start with ``e``)." +msgstr "" + +#: ../Doc/howto/clinic.rst:899 +msgid "" +"When using ``subclass_of``, you may also want to use the other custom " +"argument for ``object()``: ``type``, which lets you set the type actually " +"used for the parameter. For example, if you want to ensure that the object " +"is a subclass of ``PyUnicode_Type``, you probably want to use the converter " +"``object(type='PyUnicodeObject *', subclass_of='&PyUnicode_Type')``." +msgstr "" + +#: ../Doc/howto/clinic.rst:905 +msgid "" +"One possible problem with using Argument Clinic: it takes away some possible " +"flexibility for the format units starting with ``e``. When writing a " +"``PyArg_Parse`` call by hand, you could theoretically decide at runtime what " +"encoding string to pass in to :c:func:`PyArg_ParseTuple`. But now this " +"string must be hard-coded at Argument-Clinic-preprocessing-time. This " +"limitation is deliberate; it made supporting this format unit much easier, " +"and may allow for future optimizations. This restriction doesn't seem " +"unreasonable; CPython itself always passes in static hard-coded encoding " +"strings for parameters whose format units start with ``e``." +msgstr "" + +#: ../Doc/howto/clinic.rst:918 +msgid "Parameter default values" +msgstr "" + +#: ../Doc/howto/clinic.rst:920 +msgid "" +"Default values for parameters can be any of a number of values. At their " +"simplest, they can be string, int, or float literals::" +msgstr "" + +#: ../Doc/howto/clinic.rst:927 +msgid "They can also use any of Python's built-in constants::" +msgstr "" + +#: ../Doc/howto/clinic.rst:933 +msgid "" +"There's also special support for a default value of ``NULL``, and for simple " +"expressions, documented in the following sections." +msgstr "" + +#: ../Doc/howto/clinic.rst:938 +msgid "The ``NULL`` default value" +msgstr "" + +#: ../Doc/howto/clinic.rst:940 +msgid "" +"For string and object parameters, you can set them to ``None`` to indicate " +"that there's no default. However, that means the C variable will be " +"initialized to ``Py_None``. For convenience's sakes, there's a special " +"value called ``NULL`` for just this reason: from Python's perspective it " +"behaves like a default value of ``None``, but the C variable is initialized " +"with ``NULL``." +msgstr "" + +#: ../Doc/howto/clinic.rst:948 +msgid "Expressions specified as default values" +msgstr "" + +#: ../Doc/howto/clinic.rst:950 +msgid "" +"The default value for a parameter can be more than just a literal value. It " +"can be an entire expression, using math operators and looking up attributes " +"on objects. However, this support isn't exactly simple, because of some non-" +"obvious semantics." +msgstr "" + +#: ../Doc/howto/clinic.rst:955 +msgid "Consider the following example::" +msgstr "" + +#: ../Doc/howto/clinic.rst:959 +msgid "" +"``sys.maxsize`` can have different values on different platforms. Therefore " +"Argument Clinic can't simply evaluate that expression locally and hard-code " +"it in C. So it stores the default in such a way that it will get evaluated " +"at runtime, when the user asks for the function's signature." +msgstr "" + +#: ../Doc/howto/clinic.rst:964 +msgid "" +"What namespace is available when the expression is evaluated? It's " +"evaluated in the context of the module the builtin came from. So, if your " +"module has an attribute called \"``max_widgets``\", you may simply use it::" +msgstr "" + +#: ../Doc/howto/clinic.rst:970 +msgid "" +"If the symbol isn't found in the current module, it fails over to looking in " +"``sys.modules``. That's how it can find ``sys.maxsize`` for example. " +"(Since you don't know in advance what modules the user will load into their " +"interpreter, it's best to restrict yourself to modules that are preloaded by " +"Python itself.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:975 +msgid "" +"Evaluating default values only at runtime means Argument Clinic can't " +"compute the correct equivalent C default value. So you need to tell it " +"explicitly. When you use an expression, you must also specify the equivalent " +"expression in C, using the ``c_default`` parameter to the converter::" +msgstr "" + +#: ../Doc/howto/clinic.rst:982 +msgid "" +"Another complication: Argument Clinic can't know in advance whether or not " +"the expression you supply is valid. It parses it to make sure it looks " +"legal, but it can't *actually* know. You must be very careful when using " +"expressions to specify values that are guaranteed to be valid at runtime!" +msgstr "" + +#: ../Doc/howto/clinic.rst:987 +msgid "" +"Finally, because expressions must be representable as static C values, there " +"are many restrictions on legal expressions. Here's a list of Python " +"features you're not permitted to use:" +msgstr "" + +#: ../Doc/howto/clinic.rst:991 +msgid "Function calls." +msgstr "" + +#: ../Doc/howto/clinic.rst:992 +msgid "Inline if statements (``3 if foo else 5``)." +msgstr "" + +#: ../Doc/howto/clinic.rst:993 +msgid "Automatic sequence unpacking (``*[1, 2, 3]``)." +msgstr "" + +#: ../Doc/howto/clinic.rst:994 +msgid "List/set/dict comprehensions and generator expressions." +msgstr "" + +#: ../Doc/howto/clinic.rst:995 +msgid "Tuple/list/set/dict literals." +msgstr "" + +#: ../Doc/howto/clinic.rst:1000 +msgid "Using a return converter" +msgstr "" + +#: ../Doc/howto/clinic.rst:1002 +msgid "" +"By default the impl function Argument Clinic generates for you returns " +"``PyObject *``. But your C function often computes some C type, then " +"converts it into the ``PyObject *`` at the last moment. Argument Clinic " +"handles converting your inputs from Python types into native C types--why " +"not have it convert your return value from a native C type into a Python " +"type too?" +msgstr "" + +#: ../Doc/howto/clinic.rst:1008 +msgid "" +"That's what a \"return converter\" does. It changes your impl function to " +"return some C type, then adds code to the generated (non-impl) function to " +"handle converting that value into the appropriate ``PyObject *``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1012 +msgid "" +"The syntax for return converters is similar to that of parameter converters. " +"You specify the return converter like it was a return annotation on the " +"function itself. Return converters behave much the same as parameter " +"converters; they take arguments, the arguments are all keyword-only, and if " +"you're not changing any of the default arguments you can omit the " +"parentheses." +msgstr "" + +#: ../Doc/howto/clinic.rst:1018 +msgid "" +"(If you use both ``\"as\"`` *and* a return converter for your function, the " +"``\"as\"`` should come before the return converter.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1021 +msgid "" +"There's one additional complication when using return converters: how do you " +"indicate an error has occurred? Normally, a function returns a valid (non-" +"``NULL``) pointer for success, and ``NULL`` for failure. But if you use an " +"integer return converter, all integers are valid. How can Argument Clinic " +"detect an error? Its solution: each return converter implicitly looks for a " +"special value that indicates an error. If you return that value, and an " +"error has been set (``PyErr_Occurred()`` returns a true value), then the " +"generated code will propagate the error. Otherwise it will encode the value " +"you return like normal." +msgstr "" + +#: ../Doc/howto/clinic.rst:1030 +msgid "Currently Argument Clinic supports only a few return converters::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1043 +msgid "" +"None of these take parameters. For the first three, return -1 to indicate " +"error. For ``DecodeFSDefault``, the return type is ``char *``; return a " +"NULL pointer to indicate an error." +msgstr "" + +#: ../Doc/howto/clinic.rst:1047 +msgid "" +"(There's also an experimental ``NoneType`` converter, which lets you return " +"``Py_None`` on success or ``NULL`` on failure, without having to increment " +"the reference count on ``Py_None``. I'm not sure it adds enough clarity to " +"be worth using.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1052 +msgid "" +"To see all the return converters Argument Clinic supports, along with their " +"parameters (if any), just run ``Tools/clinic/clinic.py --converters`` for " +"the full list." +msgstr "" + +#: ../Doc/howto/clinic.rst:1058 +msgid "Cloning existing functions" +msgstr "" + +#: ../Doc/howto/clinic.rst:1060 +msgid "" +"If you have a number of functions that look similar, you may be able to use " +"Clinic's \"clone\" feature. When you clone an existing function, you reuse:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1064 +msgid "its parameters, including" +msgstr "" + +#: ../Doc/howto/clinic.rst:1066 +msgid "their names," +msgstr "" + +#: ../Doc/howto/clinic.rst:1068 +msgid "their converters, with all parameters," +msgstr "" + +#: ../Doc/howto/clinic.rst:1070 +msgid "their default values," +msgstr "" + +#: ../Doc/howto/clinic.rst:1072 +msgid "their per-parameter docstrings," +msgstr "" + +#: ../Doc/howto/clinic.rst:1074 +msgid "" +"their *kind* (whether they're positional only, positional or keyword, or " +"keyword only), and" +msgstr "" + +#: ../Doc/howto/clinic.rst:1077 +msgid "its return converter." +msgstr "" + +#: ../Doc/howto/clinic.rst:1079 +msgid "" +"The only thing not copied from the original function is its docstring; the " +"syntax allows you to specify a new docstring." +msgstr "" + +#: ../Doc/howto/clinic.rst:1082 +msgid "Here's the syntax for cloning a function::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1090 +msgid "" +"(The functions can be in different modules or classes. I wrote ``module." +"class`` in the sample just to illustrate that you must use the full path to " +"*both* functions.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1094 +msgid "" +"Sorry, there's no syntax for partially-cloning a function, or cloning a " +"function then modifying it. Cloning is an all-or nothing proposition." +msgstr "" + +#: ../Doc/howto/clinic.rst:1097 +msgid "" +"Also, the function you are cloning from must have been previously defined in " +"the current file." +msgstr "" + +#: ../Doc/howto/clinic.rst:1101 +msgid "Calling Python code" +msgstr "" + +#: ../Doc/howto/clinic.rst:1103 +msgid "" +"The rest of the advanced topics require you to write Python code which lives " +"inside your C file and modifies Argument Clinic's runtime state. This is " +"simple: you simply define a Python block." +msgstr "" + +#: ../Doc/howto/clinic.rst:1107 +msgid "" +"A Python block uses different delimiter lines than an Argument Clinic " +"function block. It looks like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1114 +msgid "" +"All the code inside the Python block is executed at the time it's parsed. " +"All text written to stdout inside the block is redirected into the \"output" +"\" after the block." +msgstr "" + +#: ../Doc/howto/clinic.rst:1118 +msgid "" +"As an example, here's a Python block that adds a static integer variable to " +"the C code::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1129 +msgid "Using a \"self converter\"" +msgstr "" + +#: ../Doc/howto/clinic.rst:1131 +msgid "" +"Argument Clinic automatically adds a \"self\" parameter for you using a " +"default converter. It automatically sets the ``type`` of this parameter to " +"the \"pointer to an instance\" you specified when you declared the type. " +"However, you can override Argument Clinic's converter and specify one " +"yourself. Just add your own ``self`` parameter as the first parameter in a " +"block, and ensure that its converter is an instance of ``self_converter`` or " +"a subclass thereof." +msgstr "" + +#: ../Doc/howto/clinic.rst:1140 +msgid "" +"What's the point? This lets you override the type of ``self``, or give it a " +"different default name." +msgstr "" + +#: ../Doc/howto/clinic.rst:1143 +msgid "" +"How do you specify the custom type you want to cast ``self`` to? If you only " +"have one or two functions with the same type for ``self``, you can directly " +"use Argument Clinic's existing ``self`` converter, passing in the type you " +"want to use as the ``type`` parameter::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1159 +msgid "" +"On the other hand, if you have a lot of functions that will use the same " +"type for ``self``, it's best to create your own converter, subclassing " +"``self_converter`` but overwriting the ``type`` member::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1182 +msgid "Writing a custom converter" +msgstr "" + +#: ../Doc/howto/clinic.rst:1184 +msgid "" +"As we hinted at in the previous section... you can write your own " +"converters! A converter is simply a Python class that inherits from " +"``CConverter``. The main purpose of a custom converter is if you have a " +"parameter using the ``O&`` format unit--parsing this parameter means calling " +"a :c:func:`PyArg_ParseTuple` \"converter function\"." +msgstr "" + +#: ../Doc/howto/clinic.rst:1190 +msgid "" +"Your converter class should be named ``*something*_converter``. If the name " +"follows this convention, then your converter class will be automatically " +"registered with Argument Clinic; its name will be the name of your class " +"with the ``_converter`` suffix stripped off. (This is accomplished with a " +"metaclass.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1196 +msgid "" +"You shouldn't subclass ``CConverter.__init__``. Instead, you should write a " +"``converter_init()`` function. ``converter_init()`` always accepts a " +"``self`` parameter; after that, all additional parameters *must* be keyword-" +"only. Any arguments passed in to the converter in Argument Clinic will be " +"passed along to your ``converter_init()``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1203 +msgid "" +"There are some additional members of ``CConverter`` you may wish to specify " +"in your subclass. Here's the current list:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1207 +msgid "" +"The C type to use for this variable. ``type`` should be a Python string " +"specifying the type, e.g. ``int``. If this is a pointer type, the type " +"string should end with ``' *'``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1213 +msgid "``default``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1212 +msgid "" +"The Python default value for this parameter, as a Python value. Or the magic " +"value ``unspecified`` if there is no default." +msgstr "" + +#: ../Doc/howto/clinic.rst:1218 +msgid "``py_default``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1216 +msgid "" +"``default`` as it should appear in Python code, as a string. Or ``None`` if " +"there is no default." +msgstr "" + +#: ../Doc/howto/clinic.rst:1221 +msgid "" +"``default`` as it should appear in C code, as a string. Or ``None`` if there " +"is no default." +msgstr "" + +#: ../Doc/howto/clinic.rst:1234 +msgid "``c_ignored_default``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1226 +msgid "" +"The default value used to initialize the C variable when there is no " +"default, but not specifying a default may result in an \"uninitialized " +"variable\" warning. This can easily happen when using option groups--" +"although properly-written code will never actually use this value, the " +"variable does get passed in to the impl, and the C compiler will complain " +"about the \"use\" of the uninitialized value. This value should always be a " +"non-empty string." +msgstr "" + +#: ../Doc/howto/clinic.rst:1237 +msgid "The name of the C converter function, as a string." +msgstr "" + +#: ../Doc/howto/clinic.rst:1242 +msgid "``impl_by_reference``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1240 +msgid "" +"A boolean value. If true, Argument Clinic will add a ``&`` in front of the " +"name of the variable when passing it into the impl function." +msgstr "" + +#: ../Doc/howto/clinic.rst:1248 +msgid "``parse_by_reference``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1245 +msgid "" +"A boolean value. If true, Argument Clinic will add a ``&`` in front of the " +"name of the variable when passing it into :c:func:`PyArg_ParseTuple`." +msgstr "" + +#: ../Doc/howto/clinic.rst:1250 +msgid "" +"Here's the simplest example of a custom converter, from ``Modules/zlibmodule." +"c``::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1261 +msgid "" +"This block adds a converter to Argument Clinic named ``ssize_t``. " +"Parameters declared as ``ssize_t`` will be declared as type ``Py_ssize_t``, " +"and will be parsed by the ``'O&'`` format unit, which will call the " +"``ssize_t_converter`` converter function. ``ssize_t`` variables " +"automatically support default values." +msgstr "" + +#: ../Doc/howto/clinic.rst:1267 +msgid "" +"More sophisticated custom converters can insert custom C code to handle " +"initialization and cleanup. You can see more examples of custom converters " +"in the CPython source tree; grep the C files for the string ``CConverter``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1273 +msgid "Writing a custom return converter" +msgstr "" + +#: ../Doc/howto/clinic.rst:1275 +msgid "" +"Writing a custom return converter is much like writing a custom converter. " +"Except it's somewhat simpler, because return converters are themselves much " +"simpler." +msgstr "" + +#: ../Doc/howto/clinic.rst:1279 +msgid "" +"Return converters must subclass ``CReturnConverter``. There are no examples " +"yet of custom return converters, because they are not widely used yet. If " +"you wish to write your own return converter, please read ``Tools/clinic/" +"clinic.py``, specifically the implementation of ``CReturnConverter`` and all " +"its subclasses." +msgstr "" + +#: ../Doc/howto/clinic.rst:1287 +msgid "METH_O and METH_NOARGS" +msgstr "" + +#: ../Doc/howto/clinic.rst:1289 +msgid "" +"To convert a function using ``METH_O``, make sure the function's single " +"argument is using the ``object`` converter, and mark the arguments as " +"positional-only::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1301 +msgid "" +"To convert a function using ``METH_NOARGS``, just don't specify any " +"arguments." +msgstr "" + +#: ../Doc/howto/clinic.rst:1304 +msgid "" +"You can still use a self converter, a return converter, and specify a " +"``type`` argument to the object converter for ``METH_O``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1308 +msgid "tp_new and tp_init functions" +msgstr "" + +#: ../Doc/howto/clinic.rst:1310 +msgid "" +"You can convert ``tp_new`` and ``tp_init`` functions. Just name them " +"``__new__`` or ``__init__`` as appropriate. Notes:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1313 +msgid "" +"The function name generated for ``__new__`` doesn't end in ``__new__`` like " +"it would by default. It's just the name of the class, converted into a " +"valid C identifier." +msgstr "" + +#: ../Doc/howto/clinic.rst:1317 +msgid "No ``PyMethodDef`` ``#define`` is generated for these functions." +msgstr "" + +#: ../Doc/howto/clinic.rst:1319 +msgid "``__init__`` functions return ``int``, not ``PyObject *``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1321 +msgid "Use the docstring as the class docstring." +msgstr "" + +#: ../Doc/howto/clinic.rst:1323 +msgid "" +"Although ``__new__`` and ``__init__`` functions must always accept both the " +"``args`` and ``kwargs`` objects, when converting you may specify any " +"signature for these functions that you like. (If your function doesn't " +"support keywords, the parsing function generated will throw an exception if " +"it receives any.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1330 +msgid "Changing and redirecting Clinic's output" +msgstr "" + +#: ../Doc/howto/clinic.rst:1332 +msgid "" +"It can be inconvenient to have Clinic's output interspersed with your " +"conventional hand-edited C code. Luckily, Clinic is configurable: you can " +"buffer up its output for printing later (or earlier!), or write its output " +"to a separate file. You can also add a prefix or suffix to every line of " +"Clinic's generated output." +msgstr "" + +#: ../Doc/howto/clinic.rst:1338 +msgid "" +"While changing Clinic's output in this manner can be a boon to readability, " +"it may result in Clinic code using types before they are defined, or your " +"code attempting to use Clinic-generated code before it is defined. These " +"problems can be easily solved by rearranging the declarations in your file, " +"or moving where Clinic's generated code goes. (This is why the default " +"behavior of Clinic is to output everything into the current block; while " +"many people consider this hampers readability, it will never require " +"rearranging your code to fix definition-before-use problems.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1347 +msgid "Let's start with defining some terminology:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1372 +msgid "*field*" +msgstr "" + +#: ../Doc/howto/clinic.rst:1350 +msgid "" +"A field, in this context, is a subsection of Clinic's output. For example, " +"the ``#define`` for the ``PyMethodDef`` structure is a field, called " +"``methoddef_define``. Clinic has seven different fields it can output per " +"function definition::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1363 +msgid "" +"All the names are of the form ``\"_\"``, where ``\"\"`` is the " +"semantic object represented (the parsing function, the impl function, the " +"docstring, or the methoddef structure) and ``\"\"`` represents what kind " +"of statement the field is. Field names that end in ``\"_prototype\"`` " +"represent forward declarations of that thing, without the actual body/data " +"of the thing; field names that end in ``\"_definition\"`` represent the " +"actual definition of the thing, with the body/data of the thing. (``" +"\"methoddef\"`` is special, it's the only one that ends with ``\"_define" +"\"``, representing that it's a preprocessor #define.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1406 +msgid "*destination*" +msgstr "" + +#: ../Doc/howto/clinic.rst:1375 +msgid "" +"A destination is a place Clinic can write output to. There are five built-" +"in destinations:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1380 ../Doc/howto/clinic.rst:1449 +#: ../Doc/howto/clinic.rst:1523 +msgid "``block``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1379 +msgid "" +"The default destination: printed in the output section of the current Clinic " +"block." +msgstr "" + +#: ../Doc/howto/clinic.rst:1386 ../Doc/howto/clinic.rst:1476 +#: ../Doc/howto/clinic.rst:1526 +msgid "``buffer``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1383 +msgid "" +"A text buffer where you can save text for later. Text sent here is appended " +"to the end of any existing text. It's an error to have any text left in the " +"buffer when Clinic finishes processing a file." +msgstr "" + +#: ../Doc/howto/clinic.rst:1397 ../Doc/howto/clinic.rst:1462 +#: ../Doc/howto/clinic.rst:1552 +msgid "``file``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1389 +msgid "" +"A separate \"clinic file\" that will be created automatically by Clinic. The " +"filename chosen for the file is ``{basename}.clinic{extension}``, where " +"``basename`` and ``extension`` were assigned the output from ``os.path." +"splitext()`` run on the current file. (Example: the ``file`` destination " +"for ``_pickle.c`` would be written to ``_pickle.clinic.c``.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1396 +msgid "" +"**Important: When using a** ``file`` **destination, you** *must check in* " +"**the generated file!**" +msgstr "" + +#: ../Doc/howto/clinic.rst:1402 ../Doc/howto/clinic.rst:1489 +#: ../Doc/howto/clinic.rst:1556 +msgid "``two-pass``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1400 +msgid "" +"A buffer like ``buffer``. However, a two-pass buffer can only be written " +"once, and it prints out all text sent to it during all of processing, even " +"from Clinic blocks *after* the" +msgstr "" + +#: ../Doc/howto/clinic.rst:1406 ../Doc/howto/clinic.rst:1519 +msgid "``suppress``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1405 +msgid "The text is suppressed--thrown away." +msgstr "" + +#: ../Doc/howto/clinic.rst:1408 +msgid "Clinic defines five new directives that let you reconfigure its output." +msgstr "" + +#: ../Doc/howto/clinic.rst:1410 +msgid "The first new directive is ``dump``::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1414 +msgid "" +"This dumps the current contents of the named destination into the output of " +"the current block, and empties it. This only works with ``buffer`` and " +"``two-pass`` destinations." +msgstr "" + +#: ../Doc/howto/clinic.rst:1418 +msgid "" +"The second new directive is ``output``. The most basic form of ``output`` " +"is like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1423 +msgid "" +"This tells Clinic to output *field* to *destination*. ``output`` also " +"supports a special meta-destination, called ``everything``, which tells " +"Clinic to output *all* fields to that *destination*." +msgstr "" + +#: ../Doc/howto/clinic.rst:1427 +msgid "``output`` has a number of other functions::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1434 +msgid "" +"``output push`` and ``output pop`` allow you to push and pop configurations " +"on an internal configuration stack, so that you can temporarily modify the " +"output configuration, then easily restore the previous configuration. " +"Simply push before your change to save the current configuration, then pop " +"when you wish to restore the previous configuration." +msgstr "" + +#: ../Doc/howto/clinic.rst:1441 +msgid "" +"``output preset`` sets Clinic's output to one of several built-in preset " +"configurations, as follows:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1445 +msgid "" +"Clinic's original starting configuration. Writes everything immediately " +"after the input block." +msgstr "" + +#: ../Doc/howto/clinic.rst:1448 +msgid "" +"Suppress the ``parser_prototype`` and ``docstring_prototype``, write " +"everything else to ``block``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1452 +msgid "" +"Designed to write everything to the \"clinic file\" that it can. You then " +"``#include`` this file near the top of your file. You may need to rearrange " +"your file to make this work, though usually this just means creating forward " +"declarations for various ``typedef`` and ``PyTypeObject`` definitions." +msgstr "" + +#: ../Doc/howto/clinic.rst:1458 +msgid "" +"Suppress the ``parser_prototype`` and ``docstring_prototype``, write the " +"``impl_definition`` to ``block``, and write everything else to ``file``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1462 +msgid "The default filename is ``\"{dirname}/clinic/{basename}.h\"``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1465 +msgid "" +"Save up all most of the output from Clinic, to be written into your file " +"near the end. For Python files implementing modules or builtin types, it's " +"recommended that you dump the buffer just above the static structures for " +"your module or builtin type; these are normally very near the end. Using " +"``buffer`` may require even more editing than ``file``, if your file has " +"static ``PyMethodDef`` arrays defined in the middle of the file." +msgstr "" + +#: ../Doc/howto/clinic.rst:1474 +msgid "" +"Suppress the ``parser_prototype``, ``impl_prototype``, and " +"``docstring_prototype``, write the ``impl_definition`` to ``block``, and " +"write everything else to ``file``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1479 +msgid "" +"Similar to the ``buffer`` preset, but writes forward declarations to the " +"``two-pass`` buffer, and definitions to the ``buffer``. This is similar to " +"the ``buffer`` preset, but may require less editing than ``buffer``. Dump " +"the ``two-pass`` buffer near the top of your file, and dump the ``buffer`` " +"near the end just like you would when using the ``buffer`` preset." +msgstr "" + +#: ../Doc/howto/clinic.rst:1486 +msgid "" +"Suppresses the ``impl_prototype``, write the ``impl_definition`` to " +"``block``, write ``docstring_prototype``, ``methoddef_define``, and " +"``parser_prototype`` to ``two-pass``, write everything else to ``buffer``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1500 +msgid "``partial-buffer``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1492 +msgid "" +"Similar to the ``buffer`` preset, but writes more things to ``block``, only " +"writing the really big chunks of generated code to ``buffer``. This avoids " +"the definition-before-use problem of ``buffer`` completely, at the small " +"cost of having slightly more stuff in the block's output. Dump the " +"``buffer`` near the end, just like you would when using the ``buffer`` " +"preset." +msgstr "" + +#: ../Doc/howto/clinic.rst:1499 +msgid "" +"Suppresses the ``impl_prototype``, write the ``docstring_definition`` and " +"``parser_definition`` to ``buffer``, write everything else to ``block``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1502 +msgid "The third new directive is ``destination``::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1506 +msgid "This performs an operation on the destination named ``name``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1508 +msgid "There are two defined subcommands: ``new`` and ``clear``." +msgstr "" + +#: ../Doc/howto/clinic.rst:1510 +msgid "The ``new`` subcommand works like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1514 +msgid "" +"This creates a new destination with name ```` and type ````." +msgstr "" + +#: ../Doc/howto/clinic.rst:1516 +msgid "There are five destination types:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1519 +msgid "Throws the text away." +msgstr "" + +#: ../Doc/howto/clinic.rst:1522 +msgid "" +"Writes the text to the current block. This is what Clinic originally did." +msgstr "" + +#: ../Doc/howto/clinic.rst:1526 +msgid "A simple text buffer, like the \"buffer\" builtin destination above." +msgstr "" + +#: ../Doc/howto/clinic.rst:1529 +msgid "" +"A text file. The file destination takes an extra argument, a template to " +"use for building the filename, like so:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1532 +msgid "destination new " +msgstr "" + +#: ../Doc/howto/clinic.rst:1534 +msgid "" +"The template can use three strings internally that will be replaced by bits " +"of the filename:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1537 +msgid "{path}" +msgstr "" + +#: ../Doc/howto/clinic.rst:1538 +msgid "The full path to the file, including directory and full filename." +msgstr "" + +#: ../Doc/howto/clinic.rst:1539 +msgid "{dirname}" +msgstr "" + +#: ../Doc/howto/clinic.rst:1540 +msgid "The name of the directory the file is in." +msgstr "" + +#: ../Doc/howto/clinic.rst:1541 +msgid "{basename}" +msgstr "" + +#: ../Doc/howto/clinic.rst:1542 +msgid "Just the name of the file, not including the directory." +msgstr "" + +#: ../Doc/howto/clinic.rst:1544 +msgid "{basename_root}" +msgstr "" + +#: ../Doc/howto/clinic.rst:1544 +msgid "" +"Basename with the extension clipped off (everything up to but not including " +"the last '.')." +msgstr "" + +#: ../Doc/howto/clinic.rst:1548 +msgid "{basename_extension}" +msgstr "" + +#: ../Doc/howto/clinic.rst:1547 +msgid "" +"The last '.' and everything after it. If the basename does not contain a " +"period, this will be the empty string." +msgstr "" + +#: ../Doc/howto/clinic.rst:1550 +msgid "" +"If there are no periods in the filename, {basename} and {filename} are the " +"same, and {extension} is empty. \"{basename}{extension}\" is always exactly " +"the same as \"{filename}\".\"" +msgstr "" + +#: ../Doc/howto/clinic.rst:1555 +msgid "A two-pass buffer, like the \"two-pass\" builtin destination above." +msgstr "" + +#: ../Doc/howto/clinic.rst:1558 +msgid "The ``clear`` subcommand works like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1562 +msgid "" +"It removes all the accumulated text up to this point in the destination. (I " +"don't know what you'd need this for, but I thought maybe it'd be useful " +"while someone's experimenting.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1566 +msgid "The fourth new directive is ``set``::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1571 +msgid "" +"``set`` lets you set two internal variables in Clinic. ``line_prefix`` is a " +"string that will be prepended to every line of Clinic's output; " +"``line_suffix`` is a string that will be appended to every line of Clinic's " +"output." +msgstr "" + +#: ../Doc/howto/clinic.rst:1575 +msgid "Both of these support two format strings:" +msgstr "" + +#: ../Doc/howto/clinic.rst:1578 +msgid "``{block comment start}``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1578 +msgid "" +"Turns into the string ``/*``, the start-comment text sequence for C files." +msgstr "" + +#: ../Doc/howto/clinic.rst:1581 +msgid "``{block comment end}``" +msgstr "" + +#: ../Doc/howto/clinic.rst:1581 +msgid "" +"Turns into the string ``*/``, the end-comment text sequence for C files." +msgstr "" + +#: ../Doc/howto/clinic.rst:1583 +msgid "" +"The final new directive is one you shouldn't need to use directly, called " +"``preserve``::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1588 +msgid "" +"This tells Clinic that the current contents of the output should be kept, " +"unmodified. This is used internally by Clinic when dumping output into " +"``file`` files; wrapping it in a Clinic block lets Clinic use its existing " +"checksum functionality to ensure the file was not modified by hand before it " +"gets overwritten." +msgstr "" + +#: ../Doc/howto/clinic.rst:1595 +msgid "The #ifdef trick" +msgstr "" + +#: ../Doc/howto/clinic.rst:1597 +msgid "" +"If you're converting a function that isn't available on all platforms, " +"there's a trick you can use to make life a little easier. The existing code " +"probably looks like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1608 +msgid "" +"And then in the ``PyMethodDef`` structure at the bottom the existing code " +"will have::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1615 +msgid "" +"In this scenario, you should enclose the body of your impl function inside " +"the ``#ifdef``, like so::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1629 +msgid "" +"Then, remove those three lines from the ``PyMethodDef`` structure, replacing " +"them with the macro Argument Clinic generated::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1634 +msgid "" +"(You can find the real name for this macro inside the generated code. Or you " +"can calculate it yourself: it's the name of your function as defined on the " +"first line of your block, but with periods changed to underscores, " +"uppercased, and ``\"_METHODDEF\"`` added to the end.)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1639 +msgid "" +"Perhaps you're wondering: what if ``HAVE_FUNCTIONNAME`` isn't defined? The " +"``MODULE_FUNCTIONNAME_METHODDEF`` macro won't be defined either!" +msgstr "" + +#: ../Doc/howto/clinic.rst:1642 +msgid "" +"Here's where Argument Clinic gets very clever. It actually detects that the " +"Argument Clinic block might be deactivated by the ``#ifdef``. When that " +"happens, it generates a little extra code that looks like this::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1650 +msgid "" +"That means the macro always works. If the function is defined, this turns " +"into the correct structure, including the trailing comma. If the function " +"is undefined, this turns into nothing." +msgstr "" + +#: ../Doc/howto/clinic.rst:1654 +msgid "" +"However, this causes one ticklish problem: where should Argument Clinic put " +"this extra code when using the \"block\" output preset? It can't go in the " +"output block, because that could be deactivated by the ``#ifdef``. (That's " +"the whole point!)" +msgstr "" + +#: ../Doc/howto/clinic.rst:1658 +msgid "" +"In this situation, Argument Clinic writes the extra code to the \"buffer\" " +"destination. This may mean that you get a complaint from Argument Clinic::" +msgstr "" + +#: ../Doc/howto/clinic.rst:1664 +msgid "" +"When this happens, just open your file, find the ``dump buffer`` block that " +"Argument Clinic added to your file (it'll be at the very bottom), then move " +"it above the ``PyMethodDef`` structure where that macro is used." +msgstr "" + +#: ../Doc/howto/clinic.rst:1671 +msgid "Using Argument Clinic in Python files" +msgstr "" + +#: ../Doc/howto/clinic.rst:1673 +msgid "" +"It's actually possible to use Argument Clinic to preprocess Python files. " +"There's no point to using Argument Clinic blocks, of course, as the output " +"wouldn't make any sense to the Python interpreter. But using Argument " +"Clinic to run Python blocks lets you use Python as a Python preprocessor!" +msgstr "" + +#: ../Doc/howto/clinic.rst:1678 +msgid "" +"Since Python comments are different from C comments, Argument Clinic blocks " +"embedded in Python files look slightly different. They look like this::" +msgstr "" + +#: ../Doc/howto/cporting.rst:7 +msgid "Porting Extension Modules to Python 3" +msgstr "" + +#: ../Doc/howto/cporting.rst:9 +msgid "Benjamin Peterson" +msgstr "" + +#: ../Doc/howto/cporting.rst:14 +msgid "" +"Although changing the C-API was not one of Python 3's objectives, the many " +"Python-level changes made leaving Python 2's API intact impossible. In " +"fact, some changes such as :func:`int` and :func:`long` unification are more " +"obvious on the C level. This document endeavors to document " +"incompatibilities and how they can be worked around." +msgstr "" + +#: ../Doc/howto/cporting.rst:23 +msgid "Conditional compilation" +msgstr "" + +#: ../Doc/howto/cporting.rst:25 +msgid "" +"The easiest way to compile only some code for Python 3 is to check if :c:" +"macro:`PY_MAJOR_VERSION` is greater than or equal to 3. ::" +msgstr "" + +#: ../Doc/howto/cporting.rst:32 +msgid "" +"API functions that are not present can be aliased to their equivalents " +"within conditional blocks." +msgstr "" + +#: ../Doc/howto/cporting.rst:37 +msgid "Changes to Object APIs" +msgstr "" + +#: ../Doc/howto/cporting.rst:39 +msgid "" +"Python 3 merged together some types with similar functions while cleanly " +"separating others." +msgstr "" + +#: ../Doc/howto/cporting.rst:44 +msgid "str/unicode Unification" +msgstr "" + +#: ../Doc/howto/cporting.rst:46 +msgid "" +"Python 3's :func:`str` type is equivalent to Python 2's :func:`unicode`; the " +"C functions are called ``PyUnicode_*`` for both. The old 8-bit string type " +"has become :func:`bytes`, with C functions called ``PyBytes_*``. Python 2.6 " +"and later provide a compatibility header, :file:`bytesobject.h`, mapping " +"``PyBytes`` names to ``PyString`` ones. For best compatibility with Python " +"3, :c:type:`PyUnicode` should be used for textual data and :c:type:`PyBytes` " +"for binary data. It's also important to remember that :c:type:`PyBytes` " +"and :c:type:`PyUnicode` in Python 3 are not interchangeable like :c:type:" +"`PyString` and :c:type:`PyUnicode` are in Python 2. The following example " +"shows best practices with regards to :c:type:`PyUnicode`, :c:type:" +"`PyString`, and :c:type:`PyBytes`. ::" +msgstr "" + +#: ../Doc/howto/cporting.rst:95 +msgid "long/int Unification" +msgstr "" + +#: ../Doc/howto/cporting.rst:97 +msgid "" +"Python 3 has only one integer type, :func:`int`. But it actually " +"corresponds to Python 2's :func:`long` type--the :func:`int` type used in " +"Python 2 was removed. In the C-API, ``PyInt_*`` functions are replaced by " +"their ``PyLong_*`` equivalents." +msgstr "" + +#: ../Doc/howto/cporting.rst:104 +msgid "Module initialization and state" +msgstr "" + +#: ../Doc/howto/cporting.rst:106 +msgid "" +"Python 3 has a revamped extension module initialization system. (See :pep:" +"`3121`.) Instead of storing module state in globals, they should be stored " +"in an interpreter specific structure. Creating modules that act correctly " +"in both Python 2 and Python 3 is tricky. The following simple example " +"demonstrates how. ::" +msgstr "" + +#: ../Doc/howto/cporting.rst:197 +msgid "CObject replaced with Capsule" +msgstr "" + +#: ../Doc/howto/cporting.rst:199 +msgid "" +"The :c:type:`Capsule` object was introduced in Python 3.1 and 2.7 to " +"replace :c:type:`CObject`. CObjects were useful, but the :c:type:`CObject` " +"API was problematic: it didn't permit distinguishing between valid CObjects, " +"which allowed mismatched CObjects to crash the interpreter, and some of its " +"APIs relied on undefined behavior in C. (For further reading on the " +"rationale behind Capsules, please see :issue:`5630`.)" +msgstr "" + +#: ../Doc/howto/cporting.rst:206 +msgid "" +"If you're currently using CObjects, and you want to migrate to 3.1 or newer, " +"you'll need to switch to Capsules. :c:type:`CObject` was deprecated in 3.1 " +"and 2.7 and completely removed in Python 3.2. If you only support 2.7, or " +"3.1 and above, you can simply switch to :c:type:`Capsule`. If you need to " +"support Python 3.0, or versions of Python earlier than 2.7, you'll have to " +"support both CObjects and Capsules. (Note that Python 3.0 is no longer " +"supported, and it is not recommended for production use.)" +msgstr "" + +#: ../Doc/howto/cporting.rst:216 +msgid "" +"The following example header file :file:`capsulethunk.h` may solve the " +"problem for you. Simply write your code against the :c:type:`Capsule` API " +"and include this header file after :file:`Python.h`. Your code will " +"automatically use Capsules in versions of Python with Capsules, and switch " +"to CObjects when Capsules are unavailable." +msgstr "" + +#: ../Doc/howto/cporting.rst:223 +msgid "" +":file:`capsulethunk.h` simulates Capsules using CObjects. However, :c:type:" +"`CObject` provides no place to store the capsule's \"name\". As a result " +"the simulated :c:type:`Capsule` objects created by :file:`capsulethunk.h` " +"behave slightly differently from real Capsules. Specifically:" +msgstr "" + +#: ../Doc/howto/cporting.rst:228 +msgid "The name parameter passed in to :c:func:`PyCapsule_New` is ignored." +msgstr "" + +#: ../Doc/howto/cporting.rst:230 +msgid "" +"The name parameter passed in to :c:func:`PyCapsule_IsValid` and :c:func:" +"`PyCapsule_GetPointer` is ignored, and no error checking of the name is " +"performed." +msgstr "" + +#: ../Doc/howto/cporting.rst:234 +msgid ":c:func:`PyCapsule_GetName` always returns NULL." +msgstr "" + +#: ../Doc/howto/cporting.rst:236 +msgid "" +":c:func:`PyCapsule_SetName` always raises an exception and returns failure. " +"(Since there's no way to store a name in a CObject, noisy failure of :c:func:" +"`PyCapsule_SetName` was deemed preferable to silent failure here. If this " +"is inconvenient, feel free to modify your local copy as you see fit.)" +msgstr "" + +#: ../Doc/howto/cporting.rst:243 +msgid "" +"You can find :file:`capsulethunk.h` in the Python source distribution as :" +"source:`Doc/includes/capsulethunk.h`. We also include it here for your " +"convenience:" +msgstr "" + +#: ../Doc/howto/cporting.rst:252 +msgid "Other options" +msgstr "" + +#: ../Doc/howto/cporting.rst:254 +msgid "" +"If you are writing a new extension module, you might consider `Cython " +"`_. It translates a Python-like language to C. The " +"extension modules it creates are compatible with Python 3 and Python 2." +msgstr "" + +#: ../Doc/howto/curses.rst:5 +msgid "Curses Programming with Python" +msgstr "" + +#: ../Doc/howto/curses.rst:7 +msgid "A.M. Kuchling, Eric S. Raymond" +msgstr "" + +#: ../Doc/howto/curses.rst:8 +msgid "2.04" +msgstr "" + +#: ../Doc/howto/curses.rst:13 +msgid "" +"This document describes how to use the :mod:`curses` extension module to " +"control text-mode displays." +msgstr "" + +#: ../Doc/howto/curses.rst:18 +msgid "What is curses?" +msgstr "" + +#: ../Doc/howto/curses.rst:20 +msgid "" +"The curses library supplies a terminal-independent screen-painting and " +"keyboard-handling facility for text-based terminals; such terminals include " +"VT100s, the Linux console, and the simulated terminal provided by various " +"programs. Display terminals support various control codes to perform common " +"operations such as moving the cursor, scrolling the screen, and erasing " +"areas. Different terminals use widely differing codes, and often have their " +"own minor quirks." +msgstr "" + +#: ../Doc/howto/curses.rst:28 +msgid "" +"In a world of graphical displays, one might ask \"why bother\"? It's true " +"that character-cell display terminals are an obsolete technology, but there " +"are niches in which being able to do fancy things with them are still " +"valuable. One niche is on small-footprint or embedded Unixes that don't run " +"an X server. Another is tools such as OS installers and kernel " +"configurators that may have to run before any graphical support is available." +msgstr "" + +#: ../Doc/howto/curses.rst:36 +msgid "" +"The curses library provides fairly basic functionality, providing the " +"programmer with an abstraction of a display containing multiple non-" +"overlapping windows of text. The contents of a window can be changed in " +"various ways---adding text, erasing it, changing its appearance---and the " +"curses library will figure out what control codes need to be sent to the " +"terminal to produce the right output. curses doesn't provide many user-" +"interface concepts such as buttons, checkboxes, or dialogs; if you need such " +"features, consider a user interface library such as `Urwid `_." +msgstr "" + +#: ../Doc/howto/curses.rst:46 +msgid "" +"The curses library was originally written for BSD Unix; the later System V " +"versions of Unix from AT&T added many enhancements and new functions. BSD " +"curses is no longer maintained, having been replaced by ncurses, which is an " +"open-source implementation of the AT&T interface. If you're using an open-" +"source Unix such as Linux or FreeBSD, your system almost certainly uses " +"ncurses. Since most current commercial Unix versions are based on System V " +"code, all the functions described here will probably be available. The " +"older versions of curses carried by some proprietary Unixes may not support " +"everything, though." +msgstr "" + +#: ../Doc/howto/curses.rst:56 +msgid "" +"The Windows version of Python doesn't include the :mod:`curses` module. A " +"ported version called `UniCurses `_ " +"is available. You could also try `the Console module `_ written by Fredrik Lundh, which doesn't use the " +"same API as curses but provides cursor-addressable text output and full " +"support for mouse and keyboard input." +msgstr "" + +#: ../Doc/howto/curses.rst:66 +msgid "The Python curses module" +msgstr "" + +#: ../Doc/howto/curses.rst:68 +msgid "" +"Thy Python module is a fairly simple wrapper over the C functions provided " +"by curses; if you're already familiar with curses programming in C, it's " +"really easy to transfer that knowledge to Python. The biggest difference is " +"that the Python interface makes things simpler by merging different C " +"functions such as :c:func:`addstr`, :c:func:`mvaddstr`, and :c:func:" +"`mvwaddstr` into a single :meth:`~curses.window.addstr` method. You'll see " +"this covered in more detail later." +msgstr "" + +#: ../Doc/howto/curses.rst:76 +msgid "" +"This HOWTO is an introduction to writing text-mode programs with curses and " +"Python. It doesn't attempt to be a complete guide to the curses API; for " +"that, see the Python library guide's section on ncurses, and the C manual " +"pages for ncurses. It will, however, give you the basic ideas." +msgstr "" + +#: ../Doc/howto/curses.rst:83 +msgid "Starting and ending a curses application" +msgstr "" + +#: ../Doc/howto/curses.rst:85 +msgid "" +"Before doing anything, curses must be initialized. This is done by calling " +"the :func:`~curses.initscr` function, which will determine the terminal " +"type, send any required setup codes to the terminal, and create various " +"internal data structures. If successful, :func:`initscr` returns a window " +"object representing the entire screen; this is usually called ``stdscr`` " +"after the name of the corresponding C variable. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:96 +msgid "" +"Usually curses applications turn off automatic echoing of keys to the " +"screen, in order to be able to read keys and only display them under certain " +"circumstances. This requires calling the :func:`~curses.noecho` function. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:103 +msgid "" +"Applications will also commonly need to react to keys instantly, without " +"requiring the Enter key to be pressed; this is called cbreak mode, as " +"opposed to the usual buffered input mode. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:109 +msgid "" +"Terminals usually return special keys, such as the cursor keys or navigation " +"keys such as Page Up and Home, as a multibyte escape sequence. While you " +"could write your application to expect such sequences and process them " +"accordingly, curses can do it for you, returning a special value such as :" +"const:`curses.KEY_LEFT`. To get curses to do the job, you'll have to enable " +"keypad mode. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:118 +msgid "" +"Terminating a curses application is much easier than starting one. You'll " +"need to call::" +msgstr "" + +#: ../Doc/howto/curses.rst:125 +msgid "" +"to reverse the curses-friendly terminal settings. Then call the :func:" +"`~curses.endwin` function to restore the terminal to its original operating " +"mode. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:131 +msgid "" +"A common problem when debugging a curses application is to get your terminal " +"messed up when the application dies without restoring the terminal to its " +"previous state. In Python this commonly happens when your code is buggy and " +"raises an uncaught exception. Keys are no longer echoed to the screen when " +"you type them, for example, which makes using the shell difficult." +msgstr "" + +#: ../Doc/howto/curses.rst:137 +msgid "" +"In Python you can avoid these complications and make debugging much easier " +"by importing the :func:`curses.wrapper` function and using it like this::" +msgstr "" + +#: ../Doc/howto/curses.rst:156 +msgid "" +"The :func:`~curses.wrapper` function takes a callable object and does the " +"initializations described above, also initializing colors if color support " +"is present. :func:`wrapper` then runs your provided callable. Once the " +"callable returns, :func:`wrapper` will restore the original state of the " +"terminal. The callable is called inside a :keyword:`try`...\\ :keyword:" +"`except` that catches exceptions, restores the state of the terminal, and " +"then re-raises the exception. Therefore your terminal won't be left in a " +"funny state on exception and you'll be able to read the exception's message " +"and traceback." +msgstr "" + +#: ../Doc/howto/curses.rst:168 +msgid "Windows and Pads" +msgstr "" + +#: ../Doc/howto/curses.rst:170 +msgid "" +"Windows are the basic abstraction in curses. A window object represents a " +"rectangular area of the screen, and supports methods to display text, erase " +"it, allow the user to input strings, and so forth." +msgstr "" + +#: ../Doc/howto/curses.rst:174 +msgid "" +"The ``stdscr`` object returned by the :func:`~curses.initscr` function is a " +"window object that covers the entire screen. Many programs may need only " +"this single window, but you might wish to divide the screen into smaller " +"windows, in order to redraw or clear them separately. The :func:`~curses." +"newwin` function creates a new window of a given size, returning the new " +"window object. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:185 +msgid "" +"Note that the coordinate system used in curses is unusual. Coordinates are " +"always passed in the order *y,x*, and the top-left corner of a window is " +"coordinate (0,0). This breaks the normal convention for handling " +"coordinates where the *x* coordinate comes first. This is an unfortunate " +"difference from most other computer applications, but it's been part of " +"curses since it was first written, and it's too late to change things now." +msgstr "" + +#: ../Doc/howto/curses.rst:193 +msgid "" +"Your application can determine the size of the screen by using the :data:" +"`curses.LINES` and :data:`curses.COLS` variables to obtain the *y* and *x* " +"sizes. Legal coordinates will then extend from ``(0,0)`` to ``(curses.LINES " +"- 1, curses.COLS - 1)``." +msgstr "" + +#: ../Doc/howto/curses.rst:198 +msgid "" +"When you call a method to display or erase text, the effect doesn't " +"immediately show up on the display. Instead you must call the :meth:" +"`~curses.window.refresh` method of window objects to update the screen." +msgstr "" + +#: ../Doc/howto/curses.rst:203 +msgid "" +"This is because curses was originally written with slow 300-baud terminal " +"connections in mind; with these terminals, minimizing the time required to " +"redraw the screen was very important. Instead curses accumulates changes to " +"the screen and displays them in the most efficient manner when you call :" +"meth:`refresh`. For example, if your program displays some text in a window " +"and then clears the window, there's no need to send the original text " +"because they're never visible." +msgstr "" + +#: ../Doc/howto/curses.rst:212 +msgid "" +"In practice, explicitly telling curses to redraw a window doesn't really " +"complicate programming with curses much. Most programs go into a flurry of " +"activity, and then pause waiting for a keypress or some other action on the " +"part of the user. All you have to do is to be sure that the screen has been " +"redrawn before pausing to wait for user input, by first calling ``stdscr." +"refresh()`` or the :meth:`refresh` method of some other relevant window." +msgstr "" + +#: ../Doc/howto/curses.rst:220 +msgid "" +"A pad is a special case of a window; it can be larger than the actual " +"display screen, and only a portion of the pad displayed at a time. Creating " +"a pad requires the pad's height and width, while refreshing a pad requires " +"giving the coordinates of the on-screen area where a subsection of the pad " +"will be displayed. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:241 +msgid "" +"The :meth:`refresh` call displays a section of the pad in the rectangle " +"extending from coordinate (5,5) to coordinate (20,75) on the screen; the " +"upper left corner of the displayed section is coordinate (0,0) on the pad. " +"Beyond that difference, pads are exactly like ordinary windows and support " +"the same methods." +msgstr "" + +#: ../Doc/howto/curses.rst:247 +msgid "" +"If you have multiple windows and pads on screen there is a more efficient " +"way to update the screen and prevent annoying screen flicker as each part of " +"the screen gets updated. :meth:`refresh` actually does two things:" +msgstr "" + +#: ../Doc/howto/curses.rst:252 +msgid "" +"Calls the :meth:`~curses.window.noutrefresh` method of each window to update " +"an underlying data structure representing the desired state of the screen." +msgstr "" + +#: ../Doc/howto/curses.rst:255 +msgid "" +"Calls the function :func:`~curses.doupdate` function to change the physical " +"screen to match the desired state recorded in the data structure." +msgstr "" + +#: ../Doc/howto/curses.rst:258 +msgid "" +"Instead you can call :meth:`noutrefresh` on a number of windows to update " +"the data structure, and then call :func:`doupdate` to update the screen." +msgstr "" + +#: ../Doc/howto/curses.rst:264 +msgid "Displaying Text" +msgstr "" + +#: ../Doc/howto/curses.rst:266 +msgid "" +"From a C programmer's point of view, curses may sometimes look like a twisty " +"maze of functions, all subtly different. For example, :c:func:`addstr` " +"displays a string at the current cursor location in the ``stdscr`` window, " +"while :c:func:`mvaddstr` moves to a given y,x coordinate first before " +"displaying the string. :c:func:`waddstr` is just like :c:func:`addstr`, but " +"allows specifying a window to use instead of using ``stdscr`` by default. :c:" +"func:`mvwaddstr` allows specifying both a window and a coordinate." +msgstr "" + +#: ../Doc/howto/curses.rst:275 +msgid "" +"Fortunately the Python interface hides all these details. ``stdscr`` is a " +"window object like any other, and methods such as :meth:`~curses.window." +"addstr` accept multiple argument forms. Usually there are four different " +"forms." +msgstr "" + +#: ../Doc/howto/curses.rst:281 +msgid "Form" +msgstr "" + +#: ../Doc/howto/curses.rst:281 ../Doc/howto/curses.rst:350 +msgid "Description" +msgstr "" + +#: ../Doc/howto/curses.rst:283 +msgid "*str* or *ch*" +msgstr "" + +#: ../Doc/howto/curses.rst:283 +msgid "Display the string *str* or character *ch* at the current position" +msgstr "" + +#: ../Doc/howto/curses.rst:286 +msgid "*str* or *ch*, *attr*" +msgstr "" + +#: ../Doc/howto/curses.rst:286 +msgid "" +"Display the string *str* or character *ch*, using attribute *attr* at the " +"current position" +msgstr "" + +#: ../Doc/howto/curses.rst:290 +msgid "*y*, *x*, *str* or *ch*" +msgstr "" + +#: ../Doc/howto/curses.rst:290 +msgid "Move to position *y,x* within the window, and display *str* or *ch*" +msgstr "" + +#: ../Doc/howto/curses.rst:293 +msgid "*y*, *x*, *str* or *ch*, *attr*" +msgstr "" + +#: ../Doc/howto/curses.rst:293 +msgid "" +"Move to position *y,x* within the window, and display *str* or *ch*, using " +"attribute *attr*" +msgstr "" + +#: ../Doc/howto/curses.rst:297 +msgid "" +"Attributes allow displaying text in highlighted forms such as boldface, " +"underline, reverse code, or in color. They'll be explained in more detail " +"in the next subsection." +msgstr "" + +#: ../Doc/howto/curses.rst:302 +msgid "" +"The :meth:`~curses.window.addstr` method takes a Python string or bytestring " +"as the value to be displayed. The contents of bytestrings are sent to the " +"terminal as-is. Strings are encoded to bytes using the value of the " +"window's :attr:`encoding` attribute; this defaults to the default system " +"encoding as returned by :func:`locale.getpreferredencoding`." +msgstr "" + +#: ../Doc/howto/curses.rst:309 +msgid "" +"The :meth:`~curses.window.addch` methods take a character, which can be " +"either a string of length 1, a bytestring of length 1, or an integer." +msgstr "" + +#: ../Doc/howto/curses.rst:312 +msgid "" +"Constants are provided for extension characters; these constants are " +"integers greater than 255. For example, :const:`ACS_PLMINUS` is a +/- " +"symbol, and :const:`ACS_ULCORNER` is the upper left corner of a box (handy " +"for drawing borders). You can also use the appropriate Unicode character." +msgstr "" + +#: ../Doc/howto/curses.rst:318 +msgid "" +"Windows remember where the cursor was left after the last operation, so if " +"you leave out the *y,x* coordinates, the string or character will be " +"displayed wherever the last operation left off. You can also move the " +"cursor with the ``move(y,x)`` method. Because some terminals always display " +"a flashing cursor, you may want to ensure that the cursor is positioned in " +"some location where it won't be distracting; it can be confusing to have the " +"cursor blinking at some apparently random location." +msgstr "" + +#: ../Doc/howto/curses.rst:326 +msgid "" +"If your application doesn't need a blinking cursor at all, you can call " +"``curs_set(False)`` to make it invisible. For compatibility with older " +"curses versions, there's a ``leaveok(bool)`` function that's a synonym for :" +"func:`~curses.curs_set`. When *bool* is true, the curses library will " +"attempt to suppress the flashing cursor, and you won't need to worry about " +"leaving it in odd locations." +msgstr "" + +#: ../Doc/howto/curses.rst:335 +msgid "Attributes and Color" +msgstr "" + +#: ../Doc/howto/curses.rst:337 +msgid "" +"Characters can be displayed in different ways. Status lines in a text-based " +"application are commonly shown in reverse video, or a text viewer may need " +"to highlight certain words. curses supports this by allowing you to specify " +"an attribute for each cell on the screen." +msgstr "" + +#: ../Doc/howto/curses.rst:342 +msgid "" +"An attribute is an integer, each bit representing a different attribute. " +"You can try to display text with multiple attribute bits set, but curses " +"doesn't guarantee that all the possible combinations are available, or that " +"they're all visually distinct. That depends on the ability of the terminal " +"being used, so it's safest to stick to the most commonly available " +"attributes, listed here." +msgstr "" + +#: ../Doc/howto/curses.rst:350 +msgid "Attribute" +msgstr "" + +#: ../Doc/howto/curses.rst:352 +msgid ":const:`A_BLINK`" +msgstr "" + +#: ../Doc/howto/curses.rst:352 +msgid "Blinking text" +msgstr "" + +#: ../Doc/howto/curses.rst:354 +msgid ":const:`A_BOLD`" +msgstr "" + +#: ../Doc/howto/curses.rst:354 +msgid "Extra bright or bold text" +msgstr "" + +#: ../Doc/howto/curses.rst:356 +msgid ":const:`A_DIM`" +msgstr "" + +#: ../Doc/howto/curses.rst:356 +msgid "Half bright text" +msgstr "" + +#: ../Doc/howto/curses.rst:358 +msgid ":const:`A_REVERSE`" +msgstr "" + +#: ../Doc/howto/curses.rst:358 +msgid "Reverse-video text" +msgstr "" + +#: ../Doc/howto/curses.rst:360 +msgid ":const:`A_STANDOUT`" +msgstr "" + +#: ../Doc/howto/curses.rst:360 +msgid "The best highlighting mode available" +msgstr "" + +#: ../Doc/howto/curses.rst:362 +msgid ":const:`A_UNDERLINE`" +msgstr "" + +#: ../Doc/howto/curses.rst:362 +msgid "Underlined text" +msgstr "" + +#: ../Doc/howto/curses.rst:365 +msgid "" +"So, to display a reverse-video status line on the top line of the screen, " +"you could code::" +msgstr "" + +#: ../Doc/howto/curses.rst:372 +msgid "" +"The curses library also supports color on those terminals that provide it. " +"The most common such terminal is probably the Linux console, followed by " +"color xterms." +msgstr "" + +#: ../Doc/howto/curses.rst:376 +msgid "" +"To use color, you must call the :func:`~curses.start_color` function soon " +"after calling :func:`~curses.initscr`, to initialize the default color set " +"(the :func:`curses.wrapper` function does this automatically). Once that's " +"done, the :func:`~curses.has_colors` function returns TRUE if the terminal " +"in use can actually display color. (Note: curses uses the American spelling " +"'color', instead of the Canadian/British spelling 'colour'. If you're used " +"to the British spelling, you'll have to resign yourself to misspelling it " +"for the sake of these functions.)" +msgstr "" + +#: ../Doc/howto/curses.rst:386 +msgid "" +"The curses library maintains a finite number of color pairs, containing a " +"foreground (or text) color and a background color. You can get the " +"attribute value corresponding to a color pair with the :func:`~curses." +"color_pair` function; this can be bitwise-OR'ed with other attributes such " +"as :const:`A_REVERSE`, but again, such combinations are not guaranteed to " +"work on all terminals." +msgstr "" + +#: ../Doc/howto/curses.rst:393 +msgid "An example, which displays a line of text using color pair 1::" +msgstr "" + +#: ../Doc/howto/curses.rst:398 +msgid "" +"As I said before, a color pair consists of a foreground and background " +"color. The ``init_pair(n, f, b)`` function changes the definition of color " +"pair *n*, to foreground color f and background color b. Color pair 0 is " +"hard-wired to white on black, and cannot be changed." +msgstr "" + +#: ../Doc/howto/curses.rst:403 +msgid "" +"Colors are numbered, and :func:`start_color` initializes 8 basic colors when " +"it activates color mode. They are: 0:black, 1:red, 2:green, 3:yellow, 4:" +"blue, 5:magenta, 6:cyan, and 7:white. The :mod:`curses` module defines " +"named constants for each of these colors: :const:`curses.COLOR_BLACK`, :" +"const:`curses.COLOR_RED`, and so forth." +msgstr "" + +#: ../Doc/howto/curses.rst:409 +msgid "" +"Let's put all this together. To change color 1 to red text on a white " +"background, you would call::" +msgstr "" + +#: ../Doc/howto/curses.rst:414 +msgid "" +"When you change a color pair, any text already displayed using that color " +"pair will change to the new colors. You can also display new text in this " +"color with::" +msgstr "" + +#: ../Doc/howto/curses.rst:420 +msgid "" +"Very fancy terminals can change the definitions of the actual colors to a " +"given RGB value. This lets you change color 1, which is usually red, to " +"purple or blue or any other color you like. Unfortunately, the Linux " +"console doesn't support this, so I'm unable to try it out, and can't provide " +"any examples. You can check if your terminal can do this by calling :func:" +"`~curses.can_change_color`, which returns ``True`` if the capability is " +"there. If you're lucky enough to have such a talented terminal, consult " +"your system's man pages for more information." +msgstr "" + +#: ../Doc/howto/curses.rst:431 +msgid "User Input" +msgstr "" + +#: ../Doc/howto/curses.rst:433 +msgid "" +"The C curses library offers only very simple input mechanisms. Python's :mod:" +"`curses` module adds a basic text-input widget. (Other libraries such as " +"`Urwid `_ have more extensive " +"collections of widgets.)" +msgstr "" + +#: ../Doc/howto/curses.rst:438 +msgid "There are two methods for getting input from a window:" +msgstr "" + +#: ../Doc/howto/curses.rst:440 +msgid "" +":meth:`~curses.window.getch` refreshes the screen and then waits for the " +"user to hit a key, displaying the key if :func:`~curses.echo` has been " +"called earlier. You can optionally specify a coordinate to which the cursor " +"should be moved before pausing." +msgstr "" + +#: ../Doc/howto/curses.rst:445 +msgid "" +":meth:`~curses.window.getkey` does the same thing but converts the integer " +"to a string. Individual characters are returned as 1-character strings, and " +"special keys such as function keys return longer strings containing a key " +"name such as ``KEY_UP`` or ``^G``." +msgstr "" + +#: ../Doc/howto/curses.rst:450 +msgid "" +"It's possible to not wait for the user using the :meth:`~curses.window." +"nodelay` window method. After ``nodelay(True)``, :meth:`getch` and :meth:" +"`getkey` for the window become non-blocking. To signal that no input is " +"ready, :meth:`getch` returns ``curses.ERR`` (a value of -1) and :meth:" +"`getkey` raises an exception. There's also a :func:`~curses.halfdelay` " +"function, which can be used to (in effect) set a timer on each :meth:" +"`getch`; if no input becomes available within a specified delay (measured in " +"tenths of a second), curses raises an exception." +msgstr "" + +#: ../Doc/howto/curses.rst:460 +msgid "" +"The :meth:`getch` method returns an integer; if it's between 0 and 255, it " +"represents the ASCII code of the key pressed. Values greater than 255 are " +"special keys such as Page Up, Home, or the cursor keys. You can compare the " +"value returned to constants such as :const:`curses.KEY_PPAGE`, :const:" +"`curses.KEY_HOME`, or :const:`curses.KEY_LEFT`. The main loop of your " +"program may look something like this::" +msgstr "" + +#: ../Doc/howto/curses.rst:476 +msgid "" +"The :mod:`curses.ascii` module supplies ASCII class membership functions " +"that take either integer or 1-character string arguments; these may be " +"useful in writing more readable tests for such loops. It also supplies " +"conversion functions that take either integer or 1-character-string " +"arguments and return the same type. For example, :func:`curses.ascii.ctrl` " +"returns the control character corresponding to its argument." +msgstr "" + +#: ../Doc/howto/curses.rst:483 +msgid "" +"There's also a method to retrieve an entire string, :meth:`~curses.window." +"getstr`. It isn't used very often, because its functionality is quite " +"limited; the only editing keys available are the backspace key and the Enter " +"key, which terminates the string. It can optionally be limited to a fixed " +"number of characters. ::" +msgstr "" + +#: ../Doc/howto/curses.rst:494 +msgid "" +"The :mod:`curses.textpad` module supplies a text box that supports an Emacs-" +"like set of keybindings. Various methods of the :class:`~curses.textpad." +"Textbox` class support editing with input validation and gathering the edit " +"results either with or without trailing spaces. Here's an example::" +msgstr "" + +#: ../Doc/howto/curses.rst:518 +msgid "" +"See the library documentation on :mod:`curses.textpad` for more details." +msgstr "" + +#: ../Doc/howto/curses.rst:522 +msgid "For More Information" +msgstr "" + +#: ../Doc/howto/curses.rst:524 +msgid "" +"This HOWTO doesn't cover some advanced topics, such as reading the contents " +"of the screen or capturing mouse events from an xterm instance, but the " +"Python library page for the :mod:`curses` module is now reasonably " +"complete. You should browse it next." +msgstr "" + +#: ../Doc/howto/curses.rst:529 +msgid "" +"If you're in doubt about the detailed behavior of the curses functions, " +"consult the manual pages for your curses implementation, whether it's " +"ncurses or a proprietary Unix vendor's. The manual pages will document any " +"quirks, and provide complete lists of all the functions, attributes, and :" +"const:`ACS_\\*` characters available to you." +msgstr "" + +#: ../Doc/howto/curses.rst:536 +msgid "" +"Because the curses API is so large, some functions aren't supported in the " +"Python interface. Often this isn't because they're difficult to implement, " +"but because no one has needed them yet. Also, Python doesn't yet support " +"the menu library associated with ncurses. Patches adding support for these " +"would be welcome; see `the Python Developer's Guide `_ to learn more about submitting patches to Python." +msgstr "" + +#: ../Doc/howto/curses.rst:544 +msgid "" +"`Writing Programs with NCURSES `_: a lengthy tutorial for C programmers." +msgstr "" + +#: ../Doc/howto/curses.rst:546 +msgid "`The ncurses man page `_" +msgstr "" + +#: ../Doc/howto/curses.rst:547 +msgid "" +"`The ncurses FAQ `_" +msgstr "" + +#: ../Doc/howto/curses.rst:548 +msgid "" +"`\"Use curses... don't swear\" `_: video of a PyCon 2013 talk on controlling terminals using " +"curses or Urwid." +msgstr "" + +#: ../Doc/howto/curses.rst:550 +msgid "" +"`\"Console Applications with Urwid\" `_: video of a PyCon CA 2012 talk " +"demonstrating some applications written using Urwid." +msgstr "" + +#: ../Doc/howto/descriptor.rst:3 +msgid "Descriptor HowTo Guide" +msgstr "" + +#: ../Doc/howto/descriptor.rst:5 +msgid "Raymond Hettinger" +msgstr "" + +#: ../Doc/howto/descriptor.rst:6 +msgid "" +msgstr "" + +#: ../Doc/howto/descriptor.rst:0 +msgid "Contents" +msgstr "" + +#: ../Doc/howto/descriptor.rst:13 +msgid "" +"Defines descriptors, summarizes the protocol, and shows how descriptors are " +"called. Examines a custom descriptor and several built-in python " +"descriptors including functions, properties, static methods, and class " +"methods. Shows how each works by giving a pure Python equivalent and a " +"sample application." +msgstr "" + +#: ../Doc/howto/descriptor.rst:18 +msgid "" +"Learning about descriptors not only provides access to a larger toolset, it " +"creates a deeper understanding of how Python works and an appreciation for " +"the elegance of its design." +msgstr "" + +#: ../Doc/howto/descriptor.rst:24 +msgid "Definition and Introduction" +msgstr "" + +#: ../Doc/howto/descriptor.rst:26 +msgid "" +"In general, a descriptor is an object attribute with \"binding behavior\", " +"one whose attribute access has been overridden by methods in the descriptor " +"protocol. Those methods are :meth:`__get__`, :meth:`__set__`, and :meth:" +"`__delete__`. If any of those methods are defined for an object, it is said " +"to be a descriptor." +msgstr "" + +#: ../Doc/howto/descriptor.rst:32 +msgid "" +"The default behavior for attribute access is to get, set, or delete the " +"attribute from an object's dictionary. For instance, ``a.x`` has a lookup " +"chain starting with ``a.__dict__['x']``, then ``type(a).__dict__['x']``, and " +"continuing through the base classes of ``type(a)`` excluding metaclasses. If " +"the looked-up value is an object defining one of the descriptor methods, " +"then Python may override the default behavior and invoke the descriptor " +"method instead. Where this occurs in the precedence chain depends on which " +"descriptor methods were defined." +msgstr "" + +#: ../Doc/howto/descriptor.rst:41 +msgid "" +"Descriptors are a powerful, general purpose protocol. They are the " +"mechanism behind properties, methods, static methods, class methods, and :" +"func:`super()`. They are used throughout Python itself to implement the new " +"style classes introduced in version 2.2. Descriptors simplify the " +"underlying C-code and offer a flexible set of new tools for everyday Python " +"programs." +msgstr "" + +#: ../Doc/howto/descriptor.rst:49 +msgid "Descriptor Protocol" +msgstr "" + +#: ../Doc/howto/descriptor.rst:51 +msgid "``descr.__get__(self, obj, type=None) --> value``" +msgstr "" + +#: ../Doc/howto/descriptor.rst:53 +msgid "``descr.__set__(self, obj, value) --> None``" +msgstr "" + +#: ../Doc/howto/descriptor.rst:55 +msgid "``descr.__delete__(self, obj) --> None``" +msgstr "" + +#: ../Doc/howto/descriptor.rst:57 +msgid "" +"That is all there is to it. Define any of these methods and an object is " +"considered a descriptor and can override default behavior upon being looked " +"up as an attribute." +msgstr "" + +#: ../Doc/howto/descriptor.rst:61 +msgid "" +"If an object defines both :meth:`__get__` and :meth:`__set__`, it is " +"considered a data descriptor. Descriptors that only define :meth:`__get__` " +"are called non-data descriptors (they are typically used for methods but " +"other uses are possible)." +msgstr "" + +#: ../Doc/howto/descriptor.rst:66 +msgid "" +"Data and non-data descriptors differ in how overrides are calculated with " +"respect to entries in an instance's dictionary. If an instance's dictionary " +"has an entry with the same name as a data descriptor, the data descriptor " +"takes precedence. If an instance's dictionary has an entry with the same " +"name as a non-data descriptor, the dictionary entry takes precedence." +msgstr "" + +#: ../Doc/howto/descriptor.rst:72 +msgid "" +"To make a read-only data descriptor, define both :meth:`__get__` and :meth:" +"`__set__` with the :meth:`__set__` raising an :exc:`AttributeError` when " +"called. Defining the :meth:`__set__` method with an exception raising " +"placeholder is enough to make it a data descriptor." +msgstr "" + +#: ../Doc/howto/descriptor.rst:79 +msgid "Invoking Descriptors" +msgstr "" + +#: ../Doc/howto/descriptor.rst:81 +msgid "" +"A descriptor can be called directly by its method name. For example, ``d." +"__get__(obj)``." +msgstr "" + +#: ../Doc/howto/descriptor.rst:84 +msgid "" +"Alternatively, it is more common for a descriptor to be invoked " +"automatically upon attribute access. For example, ``obj.d`` looks up ``d`` " +"in the dictionary of ``obj``. If ``d`` defines the method :meth:`__get__`, " +"then ``d.__get__(obj)`` is invoked according to the precedence rules listed " +"below." +msgstr "" + +#: ../Doc/howto/descriptor.rst:89 +msgid "" +"The details of invocation depend on whether ``obj`` is an object or a class." +msgstr "" + +#: ../Doc/howto/descriptor.rst:91 +msgid "" +"For objects, the machinery is in :meth:`object.__getattribute__` which " +"transforms ``b.x`` into ``type(b).__dict__['x'].__get__(b, type(b))``. The " +"implementation works through a precedence chain that gives data descriptors " +"priority over instance variables, instance variables priority over non-data " +"descriptors, and assigns lowest priority to :meth:`__getattr__` if provided. " +"The full C implementation can be found in :c:func:" +"`PyObject_GenericGetAttr()` in :source:`Objects/object.c`." +msgstr "" + +#: ../Doc/howto/descriptor.rst:99 +msgid "" +"For classes, the machinery is in :meth:`type.__getattribute__` which " +"transforms ``B.x`` into ``B.__dict__['x'].__get__(None, B)``. In pure " +"Python, it looks like::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:110 +msgid "The important points to remember are:" +msgstr "" + +#: ../Doc/howto/descriptor.rst:112 +msgid "descriptors are invoked by the :meth:`__getattribute__` method" +msgstr "" + +#: ../Doc/howto/descriptor.rst:113 +msgid "overriding :meth:`__getattribute__` prevents automatic descriptor calls" +msgstr "" + +#: ../Doc/howto/descriptor.rst:114 +msgid "" +":meth:`object.__getattribute__` and :meth:`type.__getattribute__` make " +"different calls to :meth:`__get__`." +msgstr "" + +#: ../Doc/howto/descriptor.rst:116 +msgid "data descriptors always override instance dictionaries." +msgstr "" + +#: ../Doc/howto/descriptor.rst:117 +msgid "non-data descriptors may be overridden by instance dictionaries." +msgstr "" + +#: ../Doc/howto/descriptor.rst:119 +msgid "" +"The object returned by ``super()`` also has a custom :meth:" +"`__getattribute__` method for invoking descriptors. The call ``super(B, " +"obj).m()`` searches ``obj.__class__.__mro__`` for the base class ``A`` " +"immediately following ``B`` and then returns ``A.__dict__['m'].__get__(obj, " +"B)``. If not a descriptor, ``m`` is returned unchanged. If not in the " +"dictionary, ``m`` reverts to a search using :meth:`object.__getattribute__`." +msgstr "" + +#: ../Doc/howto/descriptor.rst:126 +msgid "" +"The implementation details are in :c:func:`super_getattro()` in :source:" +"`Objects/typeobject.c`. and a pure Python equivalent can be found in " +"`Guido's Tutorial`_." +msgstr "" + +#: ../Doc/howto/descriptor.rst:132 +msgid "" +"The details above show that the mechanism for descriptors is embedded in " +"the :meth:`__getattribute__()` methods for :class:`object`, :class:`type`, " +"and :func:`super`. Classes inherit this machinery when they derive from :" +"class:`object` or if they have a meta-class providing similar functionality. " +"Likewise, classes can turn-off descriptor invocation by overriding :meth:" +"`__getattribute__()`." +msgstr "" + +#: ../Doc/howto/descriptor.rst:141 +msgid "Descriptor Example" +msgstr "" + +#: ../Doc/howto/descriptor.rst:143 +msgid "" +"The following code creates a class whose objects are data descriptors which " +"print a message for each get or set. Overriding :meth:`__getattribute__` is " +"alternate approach that could do this for every attribute. However, this " +"descriptor is useful for monitoring just a few chosen attributes::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:181 +msgid "" +"The protocol is simple and offers exciting possibilities. Several use cases " +"are so common that they have been packaged into individual function calls. " +"Properties, bound and unbound methods, static methods, and class methods are " +"all based on the descriptor protocol." +msgstr "" + +#: ../Doc/howto/descriptor.rst:188 +msgid "Properties" +msgstr "" + +#: ../Doc/howto/descriptor.rst:190 +msgid "" +"Calling :func:`property` is a succinct way of building a data descriptor " +"that triggers function calls upon access to an attribute. Its signature is::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:195 +msgid "" +"The documentation shows a typical use to define a managed attribute ``x``::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:203 +msgid "" +"To see how :func:`property` is implemented in terms of the descriptor " +"protocol, here is a pure Python equivalent::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:243 +msgid "" +"The :func:`property` builtin helps whenever a user interface has granted " +"attribute access and then subsequent changes require the intervention of a " +"method." +msgstr "" + +#: ../Doc/howto/descriptor.rst:247 +msgid "" +"For instance, a spreadsheet class may grant access to a cell value through " +"``Cell('b10').value``. Subsequent improvements to the program require the " +"cell to be recalculated on every access; however, the programmer does not " +"want to affect existing client code accessing the attribute directly. The " +"solution is to wrap access to the value attribute in a property data " +"descriptor::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:263 +msgid "Functions and Methods" +msgstr "" + +#: ../Doc/howto/descriptor.rst:265 +msgid "" +"Python's object oriented features are built upon a function based " +"environment. Using non-data descriptors, the two are merged seamlessly." +msgstr "" + +#: ../Doc/howto/descriptor.rst:268 +msgid "" +"Class dictionaries store methods as functions. In a class definition, " +"methods are written using :keyword:`def` and :keyword:`lambda`, the usual " +"tools for creating functions. The only difference from regular functions is " +"that the first argument is reserved for the object instance. By Python " +"convention, the instance reference is called *self* but may be called *this* " +"or any other variable name." +msgstr "" + +#: ../Doc/howto/descriptor.rst:275 +msgid "" +"To support method calls, functions include the :meth:`__get__` method for " +"binding methods during attribute access. This means that all functions are " +"non-data descriptors which return bound or unbound methods depending whether " +"they are invoked from an object or a class. In pure python, it works like " +"this::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:287 +msgid "" +"Running the interpreter shows how the function descriptor works in practice::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:301 +msgid "" +"The output suggests that bound and unbound methods are two different types. " +"While they could have been implemented that way, the actual C implementation " +"of :c:type:`PyMethod_Type` in :source:`Objects/classobject.c` is a single " +"object with two different representations depending on whether the :attr:" +"`im_self` field is set or is *NULL* (the C equivalent of *None*)." +msgstr "" + +#: ../Doc/howto/descriptor.rst:307 +msgid "" +"Likewise, the effects of calling a method object depend on the :attr:" +"`im_self` field. If set (meaning bound), the original function (stored in " +"the :attr:`im_func` field) is called as expected with the first argument set " +"to the instance. If unbound, all of the arguments are passed unchanged to " +"the original function. The actual C implementation of :func:" +"`instancemethod_call()` is only slightly more complex in that it includes " +"some type checking." +msgstr "" + +#: ../Doc/howto/descriptor.rst:316 +msgid "Static Methods and Class Methods" +msgstr "" + +#: ../Doc/howto/descriptor.rst:318 +msgid "" +"Non-data descriptors provide a simple mechanism for variations on the usual " +"patterns of binding functions into methods." +msgstr "" + +#: ../Doc/howto/descriptor.rst:321 +msgid "" +"To recap, functions have a :meth:`__get__` method so that they can be " +"converted to a method when accessed as attributes. The non-data descriptor " +"transforms an ``obj.f(*args)`` call into ``f(obj, *args)``. Calling ``klass." +"f(*args)`` becomes ``f(*args)``." +msgstr "" + +#: ../Doc/howto/descriptor.rst:326 +msgid "This chart summarizes the binding and its two most useful variants:" +msgstr "" + +#: ../Doc/howto/descriptor.rst:329 +msgid "Transformation" +msgstr "" + +#: ../Doc/howto/descriptor.rst:329 +msgid "Called from an Object" +msgstr "" + +#: ../Doc/howto/descriptor.rst:329 +msgid "Called from a Class" +msgstr "" + +#: ../Doc/howto/descriptor.rst:332 +msgid "function" +msgstr "" + +#: ../Doc/howto/descriptor.rst:332 +msgid "f(obj, \\*args)" +msgstr "" + +#: ../Doc/howto/descriptor.rst:332 ../Doc/howto/descriptor.rst:334 +msgid "f(\\*args)" +msgstr "" + +#: ../Doc/howto/descriptor.rst:334 +msgid "staticmethod" +msgstr "" + +#: ../Doc/howto/descriptor.rst:336 +msgid "classmethod" +msgstr "" + +#: ../Doc/howto/descriptor.rst:336 +msgid "f(type(obj), \\*args)" +msgstr "" + +#: ../Doc/howto/descriptor.rst:336 +msgid "f(klass, \\*args)" +msgstr "" + +#: ../Doc/howto/descriptor.rst:339 +msgid "" +"Static methods return the underlying function without changes. Calling " +"either ``c.f`` or ``C.f`` is the equivalent of a direct lookup into ``object." +"__getattribute__(c, \"f\")`` or ``object.__getattribute__(C, \"f\")``. As a " +"result, the function becomes identically accessible from either an object or " +"a class." +msgstr "" + +#: ../Doc/howto/descriptor.rst:345 +msgid "" +"Good candidates for static methods are methods that do not reference the " +"``self`` variable." +msgstr "" + +#: ../Doc/howto/descriptor.rst:348 +msgid "" +"For instance, a statistics package may include a container class for " +"experimental data. The class provides normal methods for computing the " +"average, mean, median, and other descriptive statistics that depend on the " +"data. However, there may be useful functions which are conceptually related " +"but do not depend on the data. For instance, ``erf(x)`` is handy conversion " +"routine that comes up in statistical work but does not directly depend on a " +"particular dataset. It can be called either from an object or the class: " +"``s.erf(1.5) --> .9332`` or ``Sample.erf(1.5) --> .9332``." +msgstr "" + +#: ../Doc/howto/descriptor.rst:357 +msgid "" +"Since staticmethods return the underlying function with no changes, the " +"example calls are unexciting::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:370 +msgid "" +"Using the non-data descriptor protocol, a pure Python version of :func:" +"`staticmethod` would look like this::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:382 +msgid "" +"Unlike static methods, class methods prepend the class reference to the " +"argument list before calling the function. This format is the same for " +"whether the caller is an object or a class::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:397 +msgid "" +"This behavior is useful whenever the function only needs to have a class " +"reference and does not care about any underlying data. One use for " +"classmethods is to create alternate class constructors. In Python 2.3, the " +"classmethod :func:`dict.fromkeys` creates a new dictionary from a list of " +"keys. The pure Python equivalent is::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:413 +msgid "Now a new dictionary of unique keys can be constructed like this::" +msgstr "" + +#: ../Doc/howto/descriptor.rst:418 +msgid "" +"Using the non-data descriptor protocol, a pure Python version of :func:" +"`classmethod` would look like this::" +msgstr "" + +#: ../Doc/howto/functional.rst:3 +msgid "Functional Programming HOWTO" +msgstr "" + +#: ../Doc/howto/functional.rst:5 +msgid "A. M. Kuchling" +msgstr "" + +#: ../Doc/howto/functional.rst:6 +msgid "0.32" +msgstr "" + +#: ../Doc/howto/functional.rst:8 +msgid "" +"In this document, we'll take a tour of Python's features suitable for " +"implementing programs in a functional style. After an introduction to the " +"concepts of functional programming, we'll look at language features such as :" +"term:`iterator`\\s and :term:`generator`\\s and relevant library modules " +"such as :mod:`itertools` and :mod:`functools`." +msgstr "" + +#: ../Doc/howto/functional.rst:16 ../Doc/howto/regex.rst:24 +#: ../Doc/howto/urllib2.rst:18 +msgid "Introduction" +msgstr "" + +#: ../Doc/howto/functional.rst:18 +msgid "" +"This section explains the basic concept of functional programming; if you're " +"just interested in learning about Python language features, skip to the next " +"section on :ref:`functional-howto-iterators`." +msgstr "" + +#: ../Doc/howto/functional.rst:22 +msgid "" +"Programming languages support decomposing problems in several different ways:" +msgstr "" + +#: ../Doc/howto/functional.rst:24 +msgid "" +"Most programming languages are **procedural**: programs are lists of " +"instructions that tell the computer what to do with the program's input. C, " +"Pascal, and even Unix shells are procedural languages." +msgstr "" + +#: ../Doc/howto/functional.rst:28 +msgid "" +"In **declarative** languages, you write a specification that describes the " +"problem to be solved, and the language implementation figures out how to " +"perform the computation efficiently. SQL is the declarative language you're " +"most likely to be familiar with; a SQL query describes the data set you want " +"to retrieve, and the SQL engine decides whether to scan tables or use " +"indexes, which subclauses should be performed first, etc." +msgstr "" + +#: ../Doc/howto/functional.rst:35 +msgid "" +"**Object-oriented** programs manipulate collections of objects. Objects " +"have internal state and support methods that query or modify this internal " +"state in some way. Smalltalk and Java are object-oriented languages. C++ " +"and Python are languages that support object-oriented programming, but don't " +"force the use of object-oriented features." +msgstr "" + +#: ../Doc/howto/functional.rst:41 +msgid "" +"**Functional** programming decomposes a problem into a set of functions. " +"Ideally, functions only take inputs and produce outputs, and don't have any " +"internal state that affects the output produced for a given input. Well-" +"known functional languages include the ML family (Standard ML, OCaml, and " +"other variants) and Haskell." +msgstr "" + +#: ../Doc/howto/functional.rst:47 +msgid "" +"The designers of some computer languages choose to emphasize one particular " +"approach to programming. This often makes it difficult to write programs " +"that use a different approach. Other languages are multi-paradigm languages " +"that support several different approaches. Lisp, C++, and Python are multi-" +"paradigm; you can write programs or libraries that are largely procedural, " +"object-oriented, or functional in all of these languages. In a large " +"program, different sections might be written using different approaches; the " +"GUI might be object-oriented while the processing logic is procedural or " +"functional, for example." +msgstr "" + +#: ../Doc/howto/functional.rst:58 +msgid "" +"In a functional program, input flows through a set of functions. Each " +"function operates on its input and produces some output. Functional style " +"discourages functions with side effects that modify internal state or make " +"other changes that aren't visible in the function's return value. Functions " +"that have no side effects at all are called **purely functional**. Avoiding " +"side effects means not using data structures that get updated as a program " +"runs; every function's output must only depend on its input." +msgstr "" + +#: ../Doc/howto/functional.rst:66 +msgid "" +"Some languages are very strict about purity and don't even have assignment " +"statements such as ``a=3`` or ``c = a + b``, but it's difficult to avoid all " +"side effects. Printing to the screen or writing to a disk file are side " +"effects, for example. For example, in Python a call to the :func:`print` " +"or :func:`time.sleep` function both return no useful value; they're only " +"called for their side effects of sending some text to the screen or pausing " +"execution for a second." +msgstr "" + +#: ../Doc/howto/functional.rst:74 +msgid "" +"Python programs written in functional style usually won't go to the extreme " +"of avoiding all I/O or all assignments; instead, they'll provide a " +"functional-appearing interface but will use non-functional features " +"internally. For example, the implementation of a function will still use " +"assignments to local variables, but won't modify global variables or have " +"other side effects." +msgstr "" + +#: ../Doc/howto/functional.rst:80 +msgid "" +"Functional programming can be considered the opposite of object-oriented " +"programming. Objects are little capsules containing some internal state " +"along with a collection of method calls that let you modify this state, and " +"programs consist of making the right set of state changes. Functional " +"programming wants to avoid state changes as much as possible and works with " +"data flowing between functions. In Python you might combine the two " +"approaches by writing functions that take and return instances representing " +"objects in your application (e-mail messages, transactions, etc.)." +msgstr "" + +#: ../Doc/howto/functional.rst:89 +msgid "" +"Functional design may seem like an odd constraint to work under. Why should " +"you avoid objects and side effects? There are theoretical and practical " +"advantages to the functional style:" +msgstr "" + +#: ../Doc/howto/functional.rst:93 +msgid "Formal provability." +msgstr "" + +#: ../Doc/howto/functional.rst:94 +msgid "Modularity." +msgstr "" + +#: ../Doc/howto/functional.rst:95 +msgid "Composability." +msgstr "" + +#: ../Doc/howto/functional.rst:96 +msgid "Ease of debugging and testing." +msgstr "" + +#: ../Doc/howto/functional.rst:100 +msgid "Formal provability" +msgstr "" + +#: ../Doc/howto/functional.rst:102 +msgid "" +"A theoretical benefit is that it's easier to construct a mathematical proof " +"that a functional program is correct." +msgstr "" + +#: ../Doc/howto/functional.rst:105 +msgid "" +"For a long time researchers have been interested in finding ways to " +"mathematically prove programs correct. This is different from testing a " +"program on numerous inputs and concluding that its output is usually " +"correct, or reading a program's source code and concluding that the code " +"looks right; the goal is instead a rigorous proof that a program produces " +"the right result for all possible inputs." +msgstr "" + +#: ../Doc/howto/functional.rst:112 +msgid "" +"The technique used to prove programs correct is to write down " +"**invariants**, properties of the input data and of the program's variables " +"that are always true. For each line of code, you then show that if " +"invariants X and Y are true **before** the line is executed, the slightly " +"different invariants X' and Y' are true **after** the line is executed. " +"This continues until you reach the end of the program, at which point the " +"invariants should match the desired conditions on the program's output." +msgstr "" + +#: ../Doc/howto/functional.rst:120 +msgid "" +"Functional programming's avoidance of assignments arose because assignments " +"are difficult to handle with this technique; assignments can break " +"invariants that were true before the assignment without producing any new " +"invariants that can be propagated onward." +msgstr "" + +#: ../Doc/howto/functional.rst:125 +msgid "" +"Unfortunately, proving programs correct is largely impractical and not " +"relevant to Python software. Even trivial programs require proofs that are " +"several pages long; the proof of correctness for a moderately complicated " +"program would be enormous, and few or none of the programs you use daily " +"(the Python interpreter, your XML parser, your web browser) could be proven " +"correct. Even if you wrote down or generated a proof, there would then be " +"the question of verifying the proof; maybe there's an error in it, and you " +"wrongly believe you've proved the program correct." +msgstr "" + +#: ../Doc/howto/functional.rst:136 +msgid "Modularity" +msgstr "" + +#: ../Doc/howto/functional.rst:138 +msgid "" +"A more practical benefit of functional programming is that it forces you to " +"break apart your problem into small pieces. Programs are more modular as a " +"result. It's easier to specify and write a small function that does one " +"thing than a large function that performs a complicated transformation. " +"Small functions are also easier to read and to check for errors." +msgstr "" + +#: ../Doc/howto/functional.rst:146 +msgid "Ease of debugging and testing" +msgstr "" + +#: ../Doc/howto/functional.rst:148 +msgid "Testing and debugging a functional-style program is easier." +msgstr "" + +#: ../Doc/howto/functional.rst:150 +msgid "" +"Debugging is simplified because functions are generally small and clearly " +"specified. When a program doesn't work, each function is an interface point " +"where you can check that the data are correct. You can look at the " +"intermediate inputs and outputs to quickly isolate the function that's " +"responsible for a bug." +msgstr "" + +#: ../Doc/howto/functional.rst:155 +msgid "" +"Testing is easier because each function is a potential subject for a unit " +"test. Functions don't depend on system state that needs to be replicated " +"before running a test; instead you only have to synthesize the right input " +"and then check that the output matches expectations." +msgstr "" + +#: ../Doc/howto/functional.rst:162 +msgid "Composability" +msgstr "" + +#: ../Doc/howto/functional.rst:164 +msgid "" +"As you work on a functional-style program, you'll write a number of " +"functions with varying inputs and outputs. Some of these functions will be " +"unavoidably specialized to a particular application, but others will be " +"useful in a wide variety of programs. For example, a function that takes a " +"directory path and returns all the XML files in the directory, or a function " +"that takes a filename and returns its contents, can be applied to many " +"different situations." +msgstr "" + +#: ../Doc/howto/functional.rst:171 +msgid "" +"Over time you'll form a personal library of utilities. Often you'll " +"assemble new programs by arranging existing functions in a new configuration " +"and writing a few functions specialized for the current task." +msgstr "" + +#: ../Doc/howto/functional.rst:179 +msgid "Iterators" +msgstr "" + +#: ../Doc/howto/functional.rst:181 +msgid "" +"I'll start by looking at a Python language feature that's an important " +"foundation for writing functional-style programs: iterators." +msgstr "" + +#: ../Doc/howto/functional.rst:184 +msgid "" +"An iterator is an object representing a stream of data; this object returns " +"the data one element at a time. A Python iterator must support a method " +"called :meth:`~iterator.__next__` that takes no arguments and always returns " +"the next element of the stream. If there are no more elements in the " +"stream, :meth:`~iterator.__next__` must raise the :exc:`StopIteration` " +"exception. Iterators don't have to be finite, though; it's perfectly " +"reasonable to write an iterator that produces an infinite stream of data." +msgstr "" + +#: ../Doc/howto/functional.rst:192 +msgid "" +"The built-in :func:`iter` function takes an arbitrary object and tries to " +"return an iterator that will return the object's contents or elements, " +"raising :exc:`TypeError` if the object doesn't support iteration. Several " +"of Python's built-in data types support iteration, the most common being " +"lists and dictionaries. An object is called :term:`iterable` if you can get " +"an iterator for it." +msgstr "" + +#: ../Doc/howto/functional.rst:199 +msgid "You can experiment with the iteration interface manually:" +msgstr "" + +#: ../Doc/howto/functional.rst:217 +msgid "" +"Python expects iterable objects in several different contexts, the most " +"important being the :keyword:`for` statement. In the statement ``for X in " +"Y``, Y must be an iterator or some object for which :func:`iter` can create " +"an iterator. These two statements are equivalent::" +msgstr "" + +#: ../Doc/howto/functional.rst:229 +msgid "" +"Iterators can be materialized as lists or tuples by using the :func:`list` " +"or :func:`tuple` constructor functions:" +msgstr "" + +#: ../Doc/howto/functional.rst:238 +msgid "" +"Sequence unpacking also supports iterators: if you know an iterator will " +"return N elements, you can unpack them into an N-tuple:" +msgstr "" + +#: ../Doc/howto/functional.rst:247 +msgid "" +"Built-in functions such as :func:`max` and :func:`min` can take a single " +"iterator argument and will return the largest or smallest element. The ``" +"\"in\"`` and ``\"not in\"`` operators also support iterators: ``X in " +"iterator`` is true if X is found in the stream returned by the iterator. " +"You'll run into obvious problems if the iterator is infinite; :func:`max`, :" +"func:`min` will never return, and if the element X never appears in the " +"stream, the ``\"in\"`` and ``\"not in\"`` operators won't return either." +msgstr "" + +#: ../Doc/howto/functional.rst:255 +msgid "" +"Note that you can only go forward in an iterator; there's no way to get the " +"previous element, reset the iterator, or make a copy of it. Iterator " +"objects can optionally provide these additional capabilities, but the " +"iterator protocol only specifies the :meth:`~iterator.__next__` method. " +"Functions may therefore consume all of the iterator's output, and if you " +"need to do something different with the same stream, you'll have to create a " +"new iterator." +msgstr "" + +#: ../Doc/howto/functional.rst:265 +msgid "Data Types That Support Iterators" +msgstr "" + +#: ../Doc/howto/functional.rst:267 +msgid "" +"We've already seen how lists and tuples support iterators. In fact, any " +"Python sequence type, such as strings, will automatically support creation " +"of an iterator." +msgstr "" + +#: ../Doc/howto/functional.rst:271 +msgid "" +"Calling :func:`iter` on a dictionary returns an iterator that will loop over " +"the dictionary's keys::" +msgstr "" + +#: ../Doc/howto/functional.rst:291 +msgid "" +"Note that the order is essentially random, because it's based on the hash " +"ordering of the objects in the dictionary." +msgstr "" + +#: ../Doc/howto/functional.rst:294 +msgid "" +"Applying :func:`iter` to a dictionary always loops over the keys, but " +"dictionaries have methods that return other iterators. If you want to " +"iterate over values or key/value pairs, you can explicitly call the :meth:" +"`~dict.values` or :meth:`~dict.items` methods to get an appropriate iterator." +msgstr "" + +#: ../Doc/howto/functional.rst:300 +msgid "" +"The :func:`dict` constructor can accept an iterator that returns a finite " +"stream of ``(key, value)`` tuples:" +msgstr "" + +#: ../Doc/howto/functional.rst:307 +msgid "" +"Files also support iteration by calling the :meth:`~io.TextIOBase.readline` " +"method until there are no more lines in the file. This means you can read " +"each line of a file like this::" +msgstr "" + +#: ../Doc/howto/functional.rst:315 +msgid "" +"Sets can take their contents from an iterable and let you iterate over the " +"set's elements::" +msgstr "" + +#: ../Doc/howto/functional.rst:325 +msgid "Generator expressions and list comprehensions" +msgstr "" + +#: ../Doc/howto/functional.rst:327 +msgid "" +"Two common operations on an iterator's output are 1) performing some " +"operation for every element, 2) selecting a subset of elements that meet " +"some condition. For example, given a list of strings, you might want to " +"strip off trailing whitespace from each line or extract all the strings " +"containing a given substring." +msgstr "" + +#: ../Doc/howto/functional.rst:333 +msgid "" +"List comprehensions and generator expressions (short form: \"listcomps\" and " +"\"genexps\") are a concise notation for such operations, borrowed from the " +"functional programming language Haskell (https://www.haskell.org/). You can " +"strip all the whitespace from a stream of strings with the following code::" +msgstr "" + +#: ../Doc/howto/functional.rst:346 +msgid "" +"You can select only certain elements by adding an ``\"if\"`` condition::" +msgstr "" + +#: ../Doc/howto/functional.rst:351 +msgid "" +"With a list comprehension, you get back a Python list; ``stripped_list`` is " +"a list containing the resulting lines, not an iterator. Generator " +"expressions return an iterator that computes the values as necessary, not " +"needing to materialize all the values at once. This means that list " +"comprehensions aren't useful if you're working with iterators that return an " +"infinite stream or a very large amount of data. Generator expressions are " +"preferable in these situations." +msgstr "" + +#: ../Doc/howto/functional.rst:358 +msgid "" +"Generator expressions are surrounded by parentheses (\"()\") and list " +"comprehensions are surrounded by square brackets (\"[]\"). Generator " +"expressions have the form::" +msgstr "" + +#: ../Doc/howto/functional.rst:371 +msgid "" +"Again, for a list comprehension only the outside brackets are different " +"(square brackets instead of parentheses)." +msgstr "" + +#: ../Doc/howto/functional.rst:374 +msgid "" +"The elements of the generated output will be the successive values of " +"``expression``. The ``if`` clauses are all optional; if present, " +"``expression`` is only evaluated and added to the result when ``condition`` " +"is true." +msgstr "" + +#: ../Doc/howto/functional.rst:378 +msgid "" +"Generator expressions always have to be written inside parentheses, but the " +"parentheses signalling a function call also count. If you want to create an " +"iterator that will be immediately passed to a function you can write::" +msgstr "" + +#: ../Doc/howto/functional.rst:384 +msgid "" +"The ``for...in`` clauses contain the sequences to be iterated over. The " +"sequences do not have to be the same length, because they are iterated over " +"from left to right, **not** in parallel. For each element in ``sequence1``, " +"``sequence2`` is looped over from the beginning. ``sequence3`` is then " +"looped over for each resulting pair of elements from ``sequence1`` and " +"``sequence2``." +msgstr "" + +#: ../Doc/howto/functional.rst:390 +msgid "" +"To put it another way, a list comprehension or generator expression is " +"equivalent to the following Python code::" +msgstr "" + +#: ../Doc/howto/functional.rst:407 +msgid "" +"This means that when there are multiple ``for...in`` clauses but no ``if`` " +"clauses, the length of the resulting output will be equal to the product of " +"the lengths of all the sequences. If you have two lists of length 3, the " +"output list is 9 elements long:" +msgstr "" + +#: ../Doc/howto/functional.rst:419 +msgid "" +"To avoid introducing an ambiguity into Python's grammar, if ``expression`` " +"is creating a tuple, it must be surrounded with parentheses. The first list " +"comprehension below is a syntax error, while the second one is correct::" +msgstr "" + +#: ../Doc/howto/functional.rst:430 +msgid "Generators" +msgstr "" + +#: ../Doc/howto/functional.rst:432 +msgid "" +"Generators are a special class of functions that simplify the task of " +"writing iterators. Regular functions compute a value and return it, but " +"generators return an iterator that returns a stream of values." +msgstr "" + +#: ../Doc/howto/functional.rst:436 +msgid "" +"You're doubtless familiar with how regular function calls work in Python or " +"C. When you call a function, it gets a private namespace where its local " +"variables are created. When the function reaches a ``return`` statement, " +"the local variables are destroyed and the value is returned to the caller. " +"A later call to the same function creates a new private namespace and a " +"fresh set of local variables. But, what if the local variables weren't " +"thrown away on exiting a function? What if you could later resume the " +"function where it left off? This is what generators provide; they can be " +"thought of as resumable functions." +msgstr "" + +#: ../Doc/howto/functional.rst:445 +msgid "Here's the simplest example of a generator function:" +msgstr "" + +#: ../Doc/howto/functional.rst:451 +msgid "" +"Any function containing a :keyword:`yield` keyword is a generator function; " +"this is detected by Python's :term:`bytecode` compiler which compiles the " +"function specially as a result." +msgstr "" + +#: ../Doc/howto/functional.rst:455 +msgid "" +"When you call a generator function, it doesn't return a single value; " +"instead it returns a generator object that supports the iterator protocol. " +"On executing the ``yield`` expression, the generator outputs the value of " +"``i``, similar to a ``return`` statement. The big difference between " +"``yield`` and a ``return`` statement is that on reaching a ``yield`` the " +"generator's state of execution is suspended and local variables are " +"preserved. On the next call to the generator's :meth:`~generator.__next__` " +"method, the function will resume executing." +msgstr "" + +#: ../Doc/howto/functional.rst:464 +msgid "Here's a sample usage of the ``generate_ints()`` generator:" +msgstr "" + +#: ../Doc/howto/functional.rst:481 +msgid "" +"You could equally write ``for i in generate_ints(5)``, or ``a,b,c = " +"generate_ints(3)``." +msgstr "" + +#: ../Doc/howto/functional.rst:484 +msgid "" +"Inside a generator function, ``return value`` causes " +"``StopIteration(value)`` to be raised from the :meth:`~generator.__next__` " +"method. Once this happens, or the bottom of the function is reached, the " +"procession of values ends and the generator cannot yield any further values." +msgstr "" + +#: ../Doc/howto/functional.rst:489 +msgid "" +"You could achieve the effect of generators manually by writing your own " +"class and storing all the local variables of the generator as instance " +"variables. For example, returning a list of integers could be done by " +"setting ``self.count`` to 0, and having the :meth:`~iterator.__next__` " +"method increment ``self.count`` and return it. However, for a moderately " +"complicated generator, writing a corresponding class can be much messier." +msgstr "" + +#: ../Doc/howto/functional.rst:497 +msgid "" +"The test suite included with Python's library, :source:`Lib/test/" +"test_generators.py`, contains a number of more interesting examples. Here's " +"one generator that implements an in-order traversal of a tree using " +"generators recursively. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:513 +msgid "" +"Two other examples in ``test_generators.py`` produce solutions for the N-" +"Queens problem (placing N queens on an NxN chess board so that no queen " +"threatens another) and the Knight's Tour (finding a route that takes a " +"knight to every square of an NxN chessboard without visiting any square " +"twice)." +msgstr "" + +#: ../Doc/howto/functional.rst:521 +msgid "Passing values into a generator" +msgstr "" + +#: ../Doc/howto/functional.rst:523 +msgid "" +"In Python 2.4 and earlier, generators only produced output. Once a " +"generator's code was invoked to create an iterator, there was no way to pass " +"any new information into the function when its execution is resumed. You " +"could hack together this ability by making the generator look at a global " +"variable or by passing in some mutable object that callers then modify, but " +"these approaches are messy." +msgstr "" + +#: ../Doc/howto/functional.rst:530 +msgid "" +"In Python 2.5 there's a simple way to pass values into a generator. :keyword:" +"`yield` became an expression, returning a value that can be assigned to a " +"variable or otherwise operated on::" +msgstr "" + +#: ../Doc/howto/functional.rst:536 +msgid "" +"I recommend that you **always** put parentheses around a ``yield`` " +"expression when you're doing something with the returned value, as in the " +"above example. The parentheses aren't always necessary, but it's easier to " +"always add them instead of having to remember when they're needed." +msgstr "" + +#: ../Doc/howto/functional.rst:541 +msgid "" +"(:pep:`342` explains the exact rules, which are that a ``yield``-expression " +"must always be parenthesized except when it occurs at the top-level " +"expression on the right-hand side of an assignment. This means you can " +"write ``val = yield i`` but have to use parentheses when there's an " +"operation, as in ``val = (yield i) + 12``.)" +msgstr "" + +#: ../Doc/howto/functional.rst:547 +msgid "" +"Values are sent into a generator by calling its :meth:`send(value) " +"` method. This method resumes the generator's code and the " +"``yield`` expression returns the specified value. If the regular :meth:" +"`~generator.__next__` method is called, the ``yield`` returns ``None``." +msgstr "" + +#: ../Doc/howto/functional.rst:552 +msgid "" +"Here's a simple counter that increments by 1 and allows changing the value " +"of the internal counter." +msgstr "" + +#: ../Doc/howto/functional.rst:567 +msgid "And here's an example of changing the counter:" +msgstr "" + +#: ../Doc/howto/functional.rst:584 +msgid "" +"Because ``yield`` will often be returning ``None``, you should always check " +"for this case. Don't just use its value in expressions unless you're sure " +"that the :meth:`~generator.send` method will be the only method used to " +"resume your generator function." +msgstr "" + +#: ../Doc/howto/functional.rst:589 +msgid "" +"In addition to :meth:`~generator.send`, there are two other methods on " +"generators:" +msgstr "" + +#: ../Doc/howto/functional.rst:592 +msgid "" +":meth:`throw(type, value=None, traceback=None) ` is used to " +"raise an exception inside the generator; the exception is raised by the " +"``yield`` expression where the generator's execution is paused." +msgstr "" + +#: ../Doc/howto/functional.rst:596 +msgid "" +":meth:`~generator.close` raises a :exc:`GeneratorExit` exception inside the " +"generator to terminate the iteration. On receiving this exception, the " +"generator's code must either raise :exc:`GeneratorExit` or :exc:" +"`StopIteration`; catching the exception and doing anything else is illegal " +"and will trigger a :exc:`RuntimeError`. :meth:`~generator.close` will also " +"be called by Python's garbage collector when the generator is garbage-" +"collected." +msgstr "" + +#: ../Doc/howto/functional.rst:604 +msgid "" +"If you need to run cleanup code when a :exc:`GeneratorExit` occurs, I " +"suggest using a ``try: ... finally:`` suite instead of catching :exc:" +"`GeneratorExit`." +msgstr "" + +#: ../Doc/howto/functional.rst:607 +msgid "" +"The cumulative effect of these changes is to turn generators from one-way " +"producers of information into both producers and consumers." +msgstr "" + +#: ../Doc/howto/functional.rst:610 +msgid "" +"Generators also become **coroutines**, a more generalized form of " +"subroutines. Subroutines are entered at one point and exited at another " +"point (the top of the function, and a ``return`` statement), but coroutines " +"can be entered, exited, and resumed at many different points (the ``yield`` " +"statements)." +msgstr "" + +#: ../Doc/howto/functional.rst:617 +msgid "Built-in functions" +msgstr "" + +#: ../Doc/howto/functional.rst:619 +msgid "" +"Let's look in more detail at built-in functions often used with iterators." +msgstr "" + +#: ../Doc/howto/functional.rst:621 +msgid "" +"Two of Python's built-in functions, :func:`map` and :func:`filter` duplicate " +"the features of generator expressions:" +msgstr "" + +#: ../Doc/howto/functional.rst:633 +msgid "" +":func:`map(f, iterA, iterB, ...) ` returns an iterator over the sequence" +msgstr "" + +#: ../Doc/howto/functional.rst:625 +msgid "" +"``f(iterA[0], iterB[0]), f(iterA[1], iterB[1]), f(iterA[2], iterB[2]), ...``." +msgstr "" + +#: ../Doc/howto/functional.rst:635 +msgid "You can of course achieve the same effect with a list comprehension." +msgstr "" + +#: ../Doc/howto/functional.rst:637 +msgid "" +":func:`filter(predicate, iter) ` returns an iterator over all the " +"sequence elements that meet a certain condition, and is similarly duplicated " +"by list comprehensions. A **predicate** is a function that returns the " +"truth value of some condition; for use with :func:`filter`, the predicate " +"must take a single value." +msgstr "" + +#: ../Doc/howto/functional.rst:650 +msgid "This can also be written as a list comprehension:" +msgstr "" + +#: ../Doc/howto/functional.rst:656 +msgid "" +":func:`enumerate(iter) ` counts off the elements in the iterable, " +"returning 2-tuples containing the count and each element. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:665 +msgid "" +":func:`enumerate` is often used when looping through a list and recording " +"the indexes at which certain conditions are met::" +msgstr "" + +#: ../Doc/howto/functional.rst:673 +msgid "" +":func:`sorted(iterable, key=None, reverse=False) ` collects all the " +"elements of the iterable into a list, sorts the list, and returns the sorted " +"result. The *key* and *reverse* arguments are passed through to the " +"constructed list's :meth:`~list.sort` method. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:688 +msgid "" +"(For a more detailed discussion of sorting, see the :ref:`sortinghowto`.)" +msgstr "" + +#: ../Doc/howto/functional.rst:691 +msgid "" +"The :func:`any(iter) ` and :func:`all(iter) ` built-ins look at " +"the truth values of an iterable's contents. :func:`any` returns ``True`` if " +"any element in the iterable is a true value, and :func:`all` returns " +"``True`` if all of the elements are true values:" +msgstr "" + +#: ../Doc/howto/functional.rst:710 +msgid "" +":func:`zip(iterA, iterB, ...) ` takes one element from each iterable " +"and returns them in a tuple::" +msgstr "" + +#: ../Doc/howto/functional.rst:716 +msgid "" +"It doesn't construct an in-memory list and exhaust all the input iterators " +"before returning; instead tuples are constructed and returned only if " +"they're requested. (The technical term for this behaviour is `lazy " +"evaluation `__.)" +msgstr "" + +#: ../Doc/howto/functional.rst:721 +msgid "" +"This iterator is intended to be used with iterables that are all of the same " +"length. If the iterables are of different lengths, the resulting stream " +"will be the same length as the shortest iterable. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:728 +msgid "" +"You should avoid doing this, though, because an element may be taken from " +"the longer iterators and discarded. This means you can't go on to use the " +"iterators further because you risk skipping a discarded element." +msgstr "" + +#: ../Doc/howto/functional.rst:734 +msgid "The itertools module" +msgstr "" + +#: ../Doc/howto/functional.rst:736 +msgid "" +"The :mod:`itertools` module contains a number of commonly-used iterators as " +"well as functions for combining several iterators. This section will " +"introduce the module's contents by showing small examples." +msgstr "" + +#: ../Doc/howto/functional.rst:740 +msgid "The module's functions fall into a few broad classes:" +msgstr "" + +#: ../Doc/howto/functional.rst:742 +msgid "Functions that create a new iterator based on an existing iterator." +msgstr "" + +#: ../Doc/howto/functional.rst:743 +msgid "Functions for treating an iterator's elements as function arguments." +msgstr "" + +#: ../Doc/howto/functional.rst:744 +msgid "Functions for selecting portions of an iterator's output." +msgstr "" + +#: ../Doc/howto/functional.rst:745 +msgid "A function for grouping an iterator's output." +msgstr "" + +#: ../Doc/howto/functional.rst:748 +msgid "Creating new iterators" +msgstr "" + +#: ../Doc/howto/functional.rst:750 +msgid "" +":func:`itertools.count(n) ` returns an infinite stream of " +"integers, increasing by 1 each time. You can optionally supply the starting " +"number, which defaults to 0::" +msgstr "" + +#: ../Doc/howto/functional.rst:759 +msgid "" +":func:`itertools.cycle(iter) ` saves a copy of the contents " +"of a provided iterable and returns a new iterator that returns its elements " +"from first to last. The new iterator will repeat these elements " +"infinitely. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:766 +msgid "" +":func:`itertools.repeat(elem, [n]) ` returns the provided " +"element *n* times, or returns the element endlessly if *n* is not " +"provided. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:774 +msgid "" +":func:`itertools.chain(iterA, iterB, ...) ` takes an " +"arbitrary number of iterables as input, and returns all the elements of the " +"first iterator, then all the elements of the second, and so on, until all of " +"the iterables have been exhausted. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:782 +msgid "" +":func:`itertools.islice(iter, [start], stop, [step]) ` " +"returns a stream that's a slice of the iterator. With a single *stop* " +"argument, it will return the first *stop* elements. If you supply a " +"starting index, you'll get *stop-start* elements, and if you supply a value " +"for *step*, elements will be skipped accordingly. Unlike Python's string " +"and list slicing, you can't use negative values for *start*, *stop*, or " +"*step*. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:796 +msgid "" +":func:`itertools.tee(iter, [n]) ` replicates an iterator; it " +"returns *n* independent iterators that will all return the contents of the " +"source iterator. If you don't supply a value for *n*, the default is 2. " +"Replicating iterators requires saving some of the contents of the source " +"iterator, so this can consume significant memory if the iterator is large " +"and one of the new iterators is consumed more than the others. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:815 +msgid "Calling functions on elements" +msgstr "" + +#: ../Doc/howto/functional.rst:817 +msgid "" +"The :mod:`operator` module contains a set of functions corresponding to " +"Python's operators. Some examples are :func:`operator.add(a, b) ` (adds two values), :func:`operator.ne(a, b) ` (same as " +"``a != b``), and :func:`operator.attrgetter('id') ` " +"(returns a callable that fetches the ``.id`` attribute)." +msgstr "" + +#: ../Doc/howto/functional.rst:823 +msgid "" +":func:`itertools.starmap(func, iter) ` assumes that the " +"iterable will return a stream of tuples, and calls *func* using these tuples " +"as the arguments::" +msgstr "" + +#: ../Doc/howto/functional.rst:835 +msgid "Selecting elements" +msgstr "" + +#: ../Doc/howto/functional.rst:837 +msgid "" +"Another group of functions chooses a subset of an iterator's elements based " +"on a predicate." +msgstr "" + +#: ../Doc/howto/functional.rst:840 +msgid "" +":func:`itertools.filterfalse(predicate, iter) ` is " +"the opposite of :func:`filter`, returning all elements for which the " +"predicate returns false::" +msgstr "" + +#: ../Doc/howto/functional.rst:847 +msgid "" +":func:`itertools.takewhile(predicate, iter) ` returns " +"elements for as long as the predicate returns true. Once the predicate " +"returns false, the iterator will signal the end of its results. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:860 +msgid "" +":func:`itertools.dropwhile(predicate, iter) ` discards " +"elements while the predicate returns true, and then returns the rest of the " +"iterable's results. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:870 +msgid "" +":func:`itertools.compress(data, selectors) ` takes two " +"iterators and returns only those elements of *data* for which the " +"corresponding element of *selectors* is true, stopping whenever either one " +"is exhausted::" +msgstr "" + +#: ../Doc/howto/functional.rst:879 +msgid "Combinatoric functions" +msgstr "" + +#: ../Doc/howto/functional.rst:881 +msgid "" +"The :func:`itertools.combinations(iterable, r) ` " +"returns an iterator giving all possible *r*-tuple combinations of the " +"elements contained in *iterable*. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:896 +msgid "" +"The elements within each tuple remain in the same order as *iterable* " +"returned them. For example, the number 1 is always before 2, 3, 4, or 5 in " +"the examples above. A similar function, :func:`itertools." +"permutations(iterable, r=None) `, removes this " +"constraint on the order, returning all possible arrangements of length *r*::" +msgstr "" + +#: ../Doc/howto/functional.rst:915 +msgid "" +"If you don't supply a value for *r* the length of the iterable is used, " +"meaning that all the elements are permuted." +msgstr "" + +#: ../Doc/howto/functional.rst:918 +msgid "" +"Note that these functions produce all of the possible combinations by " +"position and don't require that the contents of *iterable* are unique::" +msgstr "" + +#: ../Doc/howto/functional.rst:925 +msgid "" +"The identical tuple ``('a', 'a', 'b')`` occurs twice, but the two 'a' " +"strings came from different positions." +msgstr "" + +#: ../Doc/howto/functional.rst:928 +msgid "" +"The :func:`itertools.combinations_with_replacement(iterable, r) ` function relaxes a different constraint: " +"elements can be repeated within a single tuple. Conceptually an element is " +"selected for the first position of each tuple and then is replaced before " +"the second element is selected. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:943 +msgid "Grouping elements" +msgstr "" + +#: ../Doc/howto/functional.rst:945 +msgid "" +"The last function I'll discuss, :func:`itertools.groupby(iter, " +"key_func=None) `, is the most complicated. " +"``key_func(elem)`` is a function that can compute a key value for each " +"element returned by the iterable. If you don't supply a key function, the " +"key is simply each element itself." +msgstr "" + +#: ../Doc/howto/functional.rst:950 +msgid "" +":func:`~itertools.groupby` collects all the consecutive elements from the " +"underlying iterable that have the same key value, and returns a stream of 2-" +"tuples containing a key value and an iterator for the elements with that key." +msgstr "" + +#: ../Doc/howto/functional.rst:978 +msgid "" +":func:`~itertools.groupby` assumes that the underlying iterable's contents " +"will already be sorted based on the key. Note that the returned iterators " +"also use the underlying iterable, so you have to consume the results of " +"iterator-1 before requesting iterator-2 and its corresponding key." +msgstr "" + +#: ../Doc/howto/functional.rst:985 +msgid "The functools module" +msgstr "" + +#: ../Doc/howto/functional.rst:987 +msgid "" +"The :mod:`functools` module in Python 2.5 contains some higher-order " +"functions. A **higher-order function** takes one or more functions as input " +"and returns a new function. The most useful tool in this module is the :" +"func:`functools.partial` function." +msgstr "" + +#: ../Doc/howto/functional.rst:992 +msgid "" +"For programs written in a functional style, you'll sometimes want to " +"construct variants of existing functions that have some of the parameters " +"filled in. Consider a Python function ``f(a, b, c)``; you may wish to create " +"a new function ``g(b, c)`` that's equivalent to ``f(1, b, c)``; you're " +"filling in a value for one of ``f()``'s parameters. This is called " +"\"partial function application\"." +msgstr "" + +#: ../Doc/howto/functional.rst:998 +msgid "" +"The constructor for :func:`~functools.partial` takes the arguments " +"``(function, arg1, arg2, ..., kwarg1=value1, kwarg2=value2)``. The " +"resulting object is callable, so you can just call it to invoke ``function`` " +"with the filled-in arguments." +msgstr "" + +#: ../Doc/howto/functional.rst:1003 +msgid "Here's a small but realistic example::" +msgstr "" + +#: ../Doc/howto/functional.rst:1015 +msgid "" +":func:`functools.reduce(func, iter, [initial_value]) ` " +"cumulatively performs an operation on all the iterable's elements and, " +"therefore, can't be applied to infinite iterables. *func* must be a function " +"that takes two elements and returns a single value. :func:`functools." +"reduce` takes the first two elements A and B returned by the iterator and " +"calculates ``func(A, B)``. It then requests the third element, C, " +"calculates ``func(func(A, B), C)``, combines this result with the fourth " +"element returned, and continues until the iterable is exhausted. If the " +"iterable returns no values at all, a :exc:`TypeError` exception is raised. " +"If the initial value is supplied, it's used as a starting point and " +"``func(initial_value, A)`` is the first calculation. ::" +msgstr "" + +#: ../Doc/howto/functional.rst:1039 +msgid "" +"If you use :func:`operator.add` with :func:`functools.reduce`, you'll add up " +"all the elements of the iterable. This case is so common that there's a " +"special built-in called :func:`sum` to compute it:" +msgstr "" + +#: ../Doc/howto/functional.rst:1051 +msgid "" +"For many uses of :func:`functools.reduce`, though, it can be clearer to just " +"write the obvious :keyword:`for` loop::" +msgstr "" + +#: ../Doc/howto/functional.rst:1063 +msgid "" +"A related function is `itertools.accumulate(iterable, func=operator.add) " +"`__, `part 2 `__, and `part 3 `__," +msgstr "" + +#: ../Doc/howto/functional.rst:1234 +msgid "Python documentation" +msgstr "" + +#: ../Doc/howto/functional.rst:1236 +msgid "Documentation for the :mod:`itertools` module." +msgstr "" + +#: ../Doc/howto/functional.rst:1238 +msgid "Documentation for the :mod:`operator` module." +msgstr "" + +#: ../Doc/howto/functional.rst:1240 +msgid ":pep:`289`: \"Generator Expressions\"" +msgstr "" + +#: ../Doc/howto/functional.rst:1242 +msgid "" +":pep:`342`: \"Coroutines via Enhanced Generators\" describes the new " +"generator features in Python 2.5." +msgstr "" + +#: ../Doc/howto/index.rst:3 +msgid "Python HOWTOs" +msgstr "" + +#: ../Doc/howto/index.rst:5 +msgid "" +"Python HOWTOs are documents that cover a single, specific topic, and attempt " +"to cover it fairly completely. Modelled on the Linux Documentation Project's " +"HOWTO collection, this collection is an effort to foster documentation " +"that's more detailed than the Python Library Reference." +msgstr "" + +#: ../Doc/howto/index.rst:11 +msgid "Currently, the HOWTOs are:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:5 +msgid "Instrumenting CPython with DTrace and SystemTap" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:7 +msgid "David Malcolm" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:8 +msgid "Łukasz Langa" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:10 +msgid "" +"DTrace and SystemTap are monitoring tools, each providing a way to inspect " +"what the processes on a computer system are doing. They both use domain-" +"specific languages allowing a user to write scripts which:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:14 +msgid "filter which processes are to be observed" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:15 +msgid "gather data from the processes of interest" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:16 +msgid "generate reports on the data" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:18 +msgid "" +"As of Python 3.6, CPython can be built with embedded \"markers\", also known " +"as \"probes\", that can be observed by a DTrace or SystemTap script, making " +"it easier to monitor what the CPython processes on a system are doing." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:28 +msgid "" +"DTrace markers are implementation details of the CPython interpreter. No " +"guarantees are made about probe compatibility between versions of CPython. " +"DTrace scripts can stop working or work incorrectly without warning when " +"changing CPython versions." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:35 +msgid "Enabling the static markers" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:37 +msgid "" +"macOS comes with built-in support for DTrace. On Linux, in order to build " +"CPython with the embedded markers for SystemTap, the SystemTap development " +"tools must be installed." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:41 +msgid "On a Linux machine, this can be done via::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:45 +msgid "or::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:50 +msgid "CPython must then be configured `--with-dtrace`::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:54 +msgid "" +"On macOS, you can list available DTrace probes by running a Python process " +"in the background and listing all probes made available by the Python " +"provider::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:71 +msgid "" +"On Linux, you can verify if the SystemTap static markers are present in the " +"built binary by seeing if it contains a \".note.stapsdt\" section." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:79 +msgid "" +"If you've built Python as a shared library (with --enable-shared), you need " +"to look instead within the shared library. For example:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:87 +msgid "Sufficiently modern readelf can print the metadata:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:126 +msgid "" +"The above metadata contains information for SystemTap describing how it can " +"patch strategically-placed machine code instructions to enable the tracing " +"hooks used by a SystemTap script." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:132 +msgid "Static DTrace probes" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:134 +msgid "" +"The following example DTrace script can be used to show the call/return " +"hierarchy of a Python script, only tracing within the invocation of a " +"function called \"start\". In other words, import-time function invocations " +"are not going to be listed:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:173 ../Doc/howto/instrumentation.rst:231 +msgid "It can be invoked like this:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:179 ../Doc/howto/instrumentation.rst:239 +#: ../Doc/howto/logging-cookbook.rst:75 +msgid "The output looks like this::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:202 +msgid "Static SystemTap markers" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:204 +msgid "" +"The low-level way to use the SystemTap integration is to use the static " +"markers directly. This requires you to explicitly state the binary file " +"containing them." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:208 +msgid "" +"For example, this SystemTap script can be used to show the call/return " +"hierarchy of a Python script:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:248 +msgid "where the columns are:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:250 +msgid "time in microseconds since start of script" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:252 +msgid "name of executable" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:254 +msgid "PID of process" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:256 +msgid "" +"and the remainder indicates the call/return hierarchy as the script executes." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:258 +msgid "" +"For a `--enable-shared` build of CPython, the markers are contained within " +"the libpython shared library, and the probe's dotted path needs to reflect " +"this. For example, this line from the above example::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:264 +msgid "should instead read::" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:268 +msgid "(assuming a debug build of CPython 3.6)" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:272 +msgid "Available static markers" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:278 +msgid "" +"This marker indicates that execution of a Python function has begun. It is " +"only triggered for pure-Python (bytecode) functions." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:281 +msgid "" +"The filename, function name, and line number are provided back to the " +"tracing script as positional arguments, which must be accessed using ``" +"$arg1``, ``$arg2``, ``$arg3``:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:285 +msgid "" +"``$arg1`` : ``(const char *)`` filename, accessible using " +"``user_string($arg1)``" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:287 +msgid "" +"``$arg2`` : ``(const char *)`` function name, accessible using " +"``user_string($arg2)``" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:290 +msgid "``$arg3`` : ``int`` line number" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:294 +msgid "" +"This marker is the converse of :c:func:`function__entry`, and indicates that " +"execution of a Python function has ended (either via ``return``, or via an " +"exception). It is only triggered for pure-Python (bytecode) functions." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:298 +msgid "The arguments are the same as for :c:func:`function__entry`" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:302 +msgid "" +"This marker indicates a Python line is about to be executed. It is the " +"equivalent of line-by-line tracing with a Python profiler. It is not " +"triggered within C functions." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:306 +msgid "The arguments are the same as for :c:func:`function__entry`." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:310 +msgid "" +"Fires when the Python interpreter starts a garbage collection cycle. " +"``arg0`` is the generation to scan, like :func:`gc.collect()`." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:315 +msgid "" +"Fires when the Python interpreter finishes a garbage collection cycle. " +"``arg0`` is the number of collected objects." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:320 +msgid "SystemTap Tapsets" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:322 +msgid "" +"The higher-level way to use the SystemTap integration is to use a \"tapset" +"\": SystemTap's equivalent of a library, which hides some of the lower-level " +"details of the static markers." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:326 +msgid "Here is a tapset file, based on a non-shared build of CPython:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:349 +msgid "" +"If this file is installed in SystemTap's tapset directory (e.g. ``/usr/share/" +"systemtap/tapset``), then these additional probepoints become available:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:355 +msgid "" +"This probe point indicates that execution of a Python function has begun. It " +"is only triggered for pure-python (bytecode) functions." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:360 +msgid "" +"This probe point is the converse of :c:func:`python.function.return`, and " +"indicates that execution of a Python function has ended (either via " +"``return``, or via an exception). It is only triggered for pure-python " +"(bytecode) functions." +msgstr "" + +#: ../Doc/howto/instrumentation.rst:367 +msgid "Examples" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:368 +msgid "" +"This SystemTap script uses the tapset above to more cleanly implement the " +"example given above of tracing the Python function-call hierarchy, without " +"needing to directly name the static markers:" +msgstr "" + +#: ../Doc/howto/instrumentation.rst:387 +msgid "" +"The following script uses the tapset above to provide a top-like view of all " +"running CPython code, showing the top 20 most frequently-entered bytecode " +"frames, each second, across the whole system:" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:9 +msgid "An introduction to the ipaddress module" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:11 +msgid "Peter Moody" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:12 +msgid "Nick Coghlan" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:0 +msgid "Overview" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:16 +msgid "" +"This document aims to provide a gentle introduction to the :mod:`ipaddress` " +"module. It is aimed primarily at users that aren't already familiar with IP " +"networking terminology, but may also be useful to network engineers wanting " +"an overview of how :mod:`ipaddress` represents IP network addressing " +"concepts." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:24 +msgid "Creating Address/Network/Interface objects" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:26 +msgid "" +"Since :mod:`ipaddress` is a module for inspecting and manipulating IP " +"addresses, the first thing you'll want to do is create some objects. You " +"can use :mod:`ipaddress` to create objects from strings and integers." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:32 +msgid "A Note on IP Versions" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:34 +msgid "" +"For readers that aren't particularly familiar with IP addressing, it's " +"important to know that the Internet Protocol is currently in the process of " +"moving from version 4 of the protocol to version 6. This transition is " +"occurring largely because version 4 of the protocol doesn't provide enough " +"addresses to handle the needs of the whole world, especially given the " +"increasing number of devices with direct connections to the internet." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:41 +msgid "" +"Explaining the details of the differences between the two versions of the " +"protocol is beyond the scope of this introduction, but readers need to at " +"least be aware that these two versions exist, and it will sometimes be " +"necessary to force the use of one version or the other." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:48 +msgid "IP Host Addresses" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:50 +msgid "" +"Addresses, often referred to as \"host addresses\" are the most basic unit " +"when working with IP addressing. The simplest way to create addresses is to " +"use the :func:`ipaddress.ip_address` factory function, which automatically " +"determines whether to create an IPv4 or IPv6 address based on the passed in " +"value:" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:61 +msgid "" +"Addresses can also be created directly from integers. Values that will fit " +"within 32 bits are assumed to be IPv4 addresses::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:69 +msgid "" +"To force the use of IPv4 or IPv6 addresses, the relevant classes can be " +"invoked directly. This is particularly useful to force creation of IPv6 " +"addresses for small integers::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:82 +msgid "Defining Networks" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:84 +msgid "" +"Host addresses are usually grouped together into IP networks, so :mod:" +"`ipaddress` provides a way to create, inspect and manipulate network " +"definitions. IP network objects are constructed from strings that define the " +"range of host addresses that are part of that network. The simplest form for " +"that information is a \"network address/network prefix\" pair, where the " +"prefix defines the number of leading bits that are compared to determine " +"whether or not an address is part of the network and the network address " +"defines the expected value of those bits." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:93 +msgid "" +"As for addresses, a factory function is provided that determines the correct " +"IP version automatically::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:101 +msgid "" +"Network objects cannot have any host bits set. The practical effect of this " +"is that ``192.0.2.1/24`` does not describe a network. Such definitions are " +"referred to as interface objects since the ip-on-a-network notation is " +"commonly used to describe network interfaces of a computer on a given " +"network and are described further in the next section." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:107 +msgid "" +"By default, attempting to create a network object with host bits set will " +"result in :exc:`ValueError` being raised. To request that the additional " +"bits instead be coerced to zero, the flag ``strict=False`` can be passed to " +"the constructor::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:119 +msgid "" +"While the string form offers significantly more flexibility, networks can " +"also be defined with integers, just like host addresses. In this case, the " +"network is considered to contain only the single address identified by the " +"integer, so the network prefix includes the entire network address::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:129 +msgid "" +"As with addresses, creation of a particular kind of network can be forced by " +"calling the class constructor directly instead of using the factory function." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:135 +msgid "Host Interfaces" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:137 +msgid "" +"As mentioned just above, if you need to describe an address on a particular " +"network, neither the address nor the network classes are sufficient. " +"Notation like ``192.0.2.1/24`` is commonly used by network engineers and the " +"people who write tools for firewalls and routers as shorthand for \"the host " +"``192.0.2.1`` on the network ``192.0.2.0/24``\", Accordingly, :mod:" +"`ipaddress` provides a set of hybrid classes that associate an address with " +"a particular network. The interface for creation is identical to that for " +"defining network objects, except that the address portion isn't constrained " +"to being a network address." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:152 +msgid "" +"Integer inputs are accepted (as with networks), and use of a particular IP " +"version can be forced by calling the relevant constructor directly." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:157 +msgid "Inspecting Address/Network/Interface Objects" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:159 +msgid "" +"You've gone to the trouble of creating an IPv(4|6)(Address|Network|" +"Interface) object, so you probably want to get information about it. :mod:" +"`ipaddress` tries to make doing this easy and intuitive." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:163 +msgid "Extracting the IP version::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:172 +msgid "Obtaining the network from an interface::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:181 +msgid "Finding out how many individual addresses are in a network::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:190 +msgid "Iterating through the \"usable\" addresses on a network::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:205 +msgid "" +"Obtaining the netmask (i.e. set bits corresponding to the network prefix) or " +"the hostmask (any bits that are not part of the netmask):" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:220 +msgid "Exploding or compressing the address::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:231 +msgid "" +"While IPv4 doesn't support explosion or compression, the associated objects " +"still provide the relevant properties so that version neutral code can " +"easily ensure the most concise or most verbose form is used for IPv6 " +"addresses while still correctly handling IPv4 addresses." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:238 +msgid "Networks as lists of Addresses" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:240 +msgid "" +"It's sometimes useful to treat networks as lists. This means it is possible " +"to index them like this::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:253 +msgid "" +"It also means that network objects lend themselves to using the list " +"membership test syntax like this::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:259 +msgid "Containment testing is done efficiently based on the network prefix::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:269 +msgid "Comparisons" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:271 +msgid "" +":mod:`ipaddress` provides some simple, hopefully intuitive ways to compare " +"objects, where it makes sense::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:277 +msgid "" +"A :exc:`TypeError` exception is raised if you try to compare objects of " +"different versions or different types." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:282 +msgid "Using IP Addresses with other modules" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:284 +msgid "" +"Other modules that use IP addresses (such as :mod:`socket`) usually won't " +"accept objects from this module directly. Instead, they must be coerced to " +"an integer or string that the other module will accept::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:296 +msgid "Getting more detail when instance creation fails" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:298 +msgid "" +"When creating address/network/interface objects using the version-agnostic " +"factory functions, any errors will be reported as :exc:`ValueError` with a " +"generic error message that simply says the passed in value was not " +"recognized as an object of that type. The lack of a specific error is " +"because it's necessary to know whether the value is *supposed* to be IPv4 or " +"IPv6 in order to provide more detail on why it has been rejected." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:305 +msgid "" +"To support use cases where it is useful to have access to this additional " +"detail, the individual class constructors actually raise the :exc:" +"`ValueError` subclasses :exc:`ipaddress.AddressValueError` and :exc:" +"`ipaddress.NetmaskValueError` to indicate exactly which part of the " +"definition failed to parse correctly." +msgstr "" + +#: ../Doc/howto/ipaddress.rst:311 +msgid "" +"The error messages are significantly more detailed when using the class " +"constructors directly. For example::" +msgstr "" + +#: ../Doc/howto/ipaddress.rst:332 +msgid "" +"However, both of the module specific exceptions have :exc:`ValueError` as " +"their parent class, so if you're not concerned with the particular type of " +"error, you can still write code like the following::" +msgstr "" + +#: ../Doc/howto/logging.rst:3 +msgid "Logging HOWTO" +msgstr "" + +#: ../Doc/howto/logging.rst:5 ../Doc/howto/logging-cookbook.rst:7 +msgid "Vinay Sajip " +msgstr "" + +#: ../Doc/howto/logging.rst:12 +msgid "Basic Logging Tutorial" +msgstr "" + +#: ../Doc/howto/logging.rst:14 +msgid "" +"Logging is a means of tracking events that happen when some software runs. " +"The software's developer adds logging calls to their code to indicate that " +"certain events have occurred. An event is described by a descriptive message " +"which can optionally contain variable data (i.e. data that is potentially " +"different for each occurrence of the event). Events also have an importance " +"which the developer ascribes to the event; the importance can also be called " +"the *level* or *severity*." +msgstr "" + +#: ../Doc/howto/logging.rst:23 +msgid "When to use logging" +msgstr "" + +#: ../Doc/howto/logging.rst:25 +msgid "" +"Logging provides a set of convenience functions for simple logging usage. " +"These are :func:`debug`, :func:`info`, :func:`warning`, :func:`error` and :" +"func:`critical`. To determine when to use logging, see the table below, " +"which states, for each of a set of common tasks, the best tool to use for it." +msgstr "" + +#: ../Doc/howto/logging.rst:31 +msgid "Task you want to perform" +msgstr "" + +#: ../Doc/howto/logging.rst:31 +msgid "The best tool for the task" +msgstr "" + +#: ../Doc/howto/logging.rst:33 +msgid "" +"Display console output for ordinary usage of a command line script or program" +msgstr "" + +#: ../Doc/howto/logging.rst:33 +msgid ":func:`print`" +msgstr "" + +#: ../Doc/howto/logging.rst:37 +msgid "" +"Report events that occur during normal operation of a program (e.g. for " +"status monitoring or fault investigation)" +msgstr "" + +#: ../Doc/howto/logging.rst:37 +msgid "" +":func:`logging.info` (or :func:`logging.debug` for very detailed output for " +"diagnostic purposes)" +msgstr "" + +#: ../Doc/howto/logging.rst:42 +msgid "Issue a warning regarding a particular runtime event" +msgstr "" + +#: ../Doc/howto/logging.rst:42 +msgid "" +":func:`warnings.warn` in library code if the issue is avoidable and the " +"client application should be modified to eliminate the warning" +msgstr "" + +#: ../Doc/howto/logging.rst:47 +msgid "" +":func:`logging.warning` if there is nothing the client application can do " +"about the situation, but the event should still be noted" +msgstr "" + +#: ../Doc/howto/logging.rst:52 +msgid "Report an error regarding a particular runtime event" +msgstr "" + +#: ../Doc/howto/logging.rst:52 +msgid "Raise an exception" +msgstr "" + +#: ../Doc/howto/logging.rst:55 +msgid "" +"Report suppression of an error without raising an exception (e.g. error " +"handler in a long-running server process)" +msgstr "" + +#: ../Doc/howto/logging.rst:55 +msgid "" +":func:`logging.error`, :func:`logging.exception` or :func:`logging.critical` " +"as appropriate for the specific error and application domain" +msgstr "" + +#: ../Doc/howto/logging.rst:62 +msgid "" +"The logging functions are named after the level or severity of the events " +"they are used to track. The standard levels and their applicability are " +"described below (in increasing order of severity):" +msgstr "" + +#: ../Doc/howto/logging.rst:69 ../Doc/howto/logging.rst:826 +msgid "Level" +msgstr "" + +#: ../Doc/howto/logging.rst:69 +msgid "When it's used" +msgstr "" + +#: ../Doc/howto/logging.rst:71 ../Doc/howto/logging.rst:836 +msgid "``DEBUG``" +msgstr "" + +#: ../Doc/howto/logging.rst:71 +msgid "" +"Detailed information, typically of interest only when diagnosing problems." +msgstr "" + +#: ../Doc/howto/logging.rst:74 ../Doc/howto/logging.rst:834 +msgid "``INFO``" +msgstr "" + +#: ../Doc/howto/logging.rst:74 +msgid "Confirmation that things are working as expected." +msgstr "" + +#: ../Doc/howto/logging.rst:77 ../Doc/howto/logging.rst:832 +msgid "``WARNING``" +msgstr "" + +#: ../Doc/howto/logging.rst:77 +msgid "" +"An indication that something unexpected happened, or indicative of some " +"problem in the near future (e.g. 'disk space low'). The software is still " +"working as expected." +msgstr "" + +#: ../Doc/howto/logging.rst:82 ../Doc/howto/logging.rst:830 +msgid "``ERROR``" +msgstr "" + +#: ../Doc/howto/logging.rst:82 +msgid "" +"Due to a more serious problem, the software has not been able to perform " +"some function." +msgstr "" + +#: ../Doc/howto/logging.rst:85 ../Doc/howto/logging.rst:828 +msgid "``CRITICAL``" +msgstr "" + +#: ../Doc/howto/logging.rst:85 +msgid "" +"A serious error, indicating that the program itself may be unable to " +"continue running." +msgstr "" + +#: ../Doc/howto/logging.rst:89 +msgid "" +"The default level is ``WARNING``, which means that only events of this level " +"and above will be tracked, unless the logging package is configured to do " +"otherwise." +msgstr "" + +#: ../Doc/howto/logging.rst:93 +msgid "" +"Events that are tracked can be handled in different ways. The simplest way " +"of handling tracked events is to print them to the console. Another common " +"way is to write them to a disk file." +msgstr "" + +#: ../Doc/howto/logging.rst:101 +msgid "A simple example" +msgstr "" + +#: ../Doc/howto/logging.rst:103 +msgid "A very simple example is::" +msgstr "" + +#: ../Doc/howto/logging.rst:109 +msgid "If you type these lines into a script and run it, you'll see:" +msgstr "" + +#: ../Doc/howto/logging.rst:115 +msgid "" +"printed out on the console. The ``INFO`` message doesn't appear because the " +"default level is ``WARNING``. The printed message includes the indication of " +"the level and the description of the event provided in the logging call, i." +"e. 'Watch out!'. Don't worry about the 'root' part for now: it will be " +"explained later. The actual output can be formatted quite flexibly if you " +"need that; formatting options will also be explained later." +msgstr "" + +#: ../Doc/howto/logging.rst:124 +msgid "Logging to a file" +msgstr "" + +#: ../Doc/howto/logging.rst:126 +msgid "" +"A very common situation is that of recording logging events in a file, so " +"let's look at that next. Be sure to try the following in a newly-started " +"Python interpreter, and don't just continue from the session described " +"above::" +msgstr "" + +#: ../Doc/howto/logging.rst:136 +msgid "" +"And now if we open the file and look at what we have, we should find the log " +"messages::" +msgstr "" + +#: ../Doc/howto/logging.rst:143 +msgid "" +"This example also shows how you can set the logging level which acts as the " +"threshold for tracking. In this case, because we set the threshold to " +"``DEBUG``, all of the messages were printed." +msgstr "" + +#: ../Doc/howto/logging.rst:147 +msgid "" +"If you want to set the logging level from a command-line option such as::" +msgstr "" + +#: ../Doc/howto/logging.rst:151 +msgid "" +"and you have the value of the parameter passed for ``--log`` in some " +"variable *loglevel*, you can use::" +msgstr "" + +#: ../Doc/howto/logging.rst:156 +msgid "" +"to get the value which you'll pass to :func:`basicConfig` via the *level* " +"argument. You may want to error check any user input value, perhaps as in " +"the following example::" +msgstr "" + +#: ../Doc/howto/logging.rst:168 +msgid "" +"The call to :func:`basicConfig` should come *before* any calls to :func:" +"`debug`, :func:`info` etc. As it's intended as a one-off simple " +"configuration facility, only the first call will actually do anything: " +"subsequent calls are effectively no-ops." +msgstr "" + +#: ../Doc/howto/logging.rst:173 +msgid "" +"If you run the above script several times, the messages from successive runs " +"are appended to the file *example.log*. If you want each run to start " +"afresh, not remembering the messages from earlier runs, you can specify the " +"*filemode* argument, by changing the call in the above example to::" +msgstr "" + +#: ../Doc/howto/logging.rst:180 +msgid "" +"The output will be the same as before, but the log file is no longer " +"appended to, so the messages from earlier runs are lost." +msgstr "" + +#: ../Doc/howto/logging.rst:185 +msgid "Logging from multiple modules" +msgstr "" + +#: ../Doc/howto/logging.rst:187 +msgid "" +"If your program consists of multiple modules, here's an example of how you " +"could organize logging in it::" +msgstr "" + +#: ../Doc/howto/logging.rst:211 +msgid "If you run *myapp.py*, you should see this in *myapp.log*::" +msgstr "" + +#: ../Doc/howto/logging.rst:217 +msgid "" +"which is hopefully what you were expecting to see. You can generalize this " +"to multiple modules, using the pattern in *mylib.py*. Note that for this " +"simple usage pattern, you won't know, by looking in the log file, *where* in " +"your application your messages came from, apart from looking at the event " +"description. If you want to track the location of your messages, you'll need " +"to refer to the documentation beyond the tutorial level -- see :ref:`logging-" +"advanced-tutorial`." +msgstr "" + +#: ../Doc/howto/logging.rst:227 +msgid "Logging variable data" +msgstr "" + +#: ../Doc/howto/logging.rst:229 +msgid "" +"To log variable data, use a format string for the event description message " +"and append the variable data as arguments. For example::" +msgstr "" + +#: ../Doc/howto/logging.rst:235 +msgid "will display:" +msgstr "" + +#: ../Doc/howto/logging.rst:241 +msgid "" +"As you can see, merging of variable data into the event description message " +"uses the old, %-style of string formatting. This is for backwards " +"compatibility: the logging package pre-dates newer formatting options such " +"as :meth:`str.format` and :class:`string.Template`. These newer formatting " +"options *are* supported, but exploring them is outside the scope of this " +"tutorial: see :ref:`formatting-styles` for more information." +msgstr "" + +#: ../Doc/howto/logging.rst:250 +msgid "Changing the format of displayed messages" +msgstr "" + +#: ../Doc/howto/logging.rst:252 +msgid "" +"To change the format which is used to display messages, you need to specify " +"the format you want to use::" +msgstr "" + +#: ../Doc/howto/logging.rst:261 +msgid "which would print::" +msgstr "" + +#: ../Doc/howto/logging.rst:267 +msgid "" +"Notice that the 'root' which appeared in earlier examples has disappeared. " +"For a full set of things that can appear in format strings, you can refer to " +"the documentation for :ref:`logrecord-attributes`, but for simple usage, you " +"just need the *levelname* (severity), *message* (event description, " +"including variable data) and perhaps to display when the event occurred. " +"This is described in the next section." +msgstr "" + +#: ../Doc/howto/logging.rst:276 +msgid "Displaying the date/time in messages" +msgstr "" + +#: ../Doc/howto/logging.rst:278 +msgid "" +"To display the date and time of an event, you would place '%(asctime)s' in " +"your format string::" +msgstr "" + +#: ../Doc/howto/logging.rst:285 +msgid "which should print something like this::" +msgstr "" + +#: ../Doc/howto/logging.rst:289 +msgid "" +"The default format for date/time display (shown above) is ISO8601. If you " +"need more control over the formatting of the date/time, provide a *datefmt* " +"argument to ``basicConfig``, as in this example::" +msgstr "" + +#: ../Doc/howto/logging.rst:297 +msgid "which would display something like this::" +msgstr "" + +#: ../Doc/howto/logging.rst:301 +msgid "" +"The format of the *datefmt* argument is the same as supported by :func:`time." +"strftime`." +msgstr "" + +#: ../Doc/howto/logging.rst:306 +msgid "Next Steps" +msgstr "" + +#: ../Doc/howto/logging.rst:308 +msgid "" +"That concludes the basic tutorial. It should be enough to get you up and " +"running with logging. There's a lot more that the logging package offers, " +"but to get the best out of it, you'll need to invest a little more of your " +"time in reading the following sections. If you're ready for that, grab some " +"of your favourite beverage and carry on." +msgstr "" + +#: ../Doc/howto/logging.rst:314 +msgid "" +"If your logging needs are simple, then use the above examples to incorporate " +"logging into your own scripts, and if you run into problems or don't " +"understand something, please post a question on the comp.lang.python Usenet " +"group (available at https://groups.google.com/group/comp.lang.python) and " +"you should receive help before too long." +msgstr "" + +#: ../Doc/howto/logging.rst:320 +msgid "" +"Still here? You can carry on reading the next few sections, which provide a " +"slightly more advanced/in-depth tutorial than the basic one above. After " +"that, you can take a look at the :ref:`logging-cookbook`." +msgstr "" + +#: ../Doc/howto/logging.rst:328 +msgid "Advanced Logging Tutorial" +msgstr "" + +#: ../Doc/howto/logging.rst:330 +msgid "" +"The logging library takes a modular approach and offers several categories " +"of components: loggers, handlers, filters, and formatters." +msgstr "" + +#: ../Doc/howto/logging.rst:333 +msgid "Loggers expose the interface that application code directly uses." +msgstr "" + +#: ../Doc/howto/logging.rst:334 +msgid "" +"Handlers send the log records (created by loggers) to the appropriate " +"destination." +msgstr "" + +#: ../Doc/howto/logging.rst:336 +msgid "" +"Filters provide a finer grained facility for determining which log records " +"to output." +msgstr "" + +#: ../Doc/howto/logging.rst:338 +msgid "Formatters specify the layout of log records in the final output." +msgstr "" + +#: ../Doc/howto/logging.rst:340 +msgid "" +"Log event information is passed between loggers, handlers, filters and " +"formatters in a :class:`LogRecord` instance." +msgstr "" + +#: ../Doc/howto/logging.rst:343 +msgid "" +"Logging is performed by calling methods on instances of the :class:`Logger` " +"class (hereafter called :dfn:`loggers`). Each instance has a name, and they " +"are conceptually arranged in a namespace hierarchy using dots (periods) as " +"separators. For example, a logger named 'scan' is the parent of loggers " +"'scan.text', 'scan.html' and 'scan.pdf'. Logger names can be anything you " +"want, and indicate the area of an application in which a logged message " +"originates." +msgstr "" + +#: ../Doc/howto/logging.rst:350 +msgid "" +"A good convention to use when naming loggers is to use a module-level " +"logger, in each module which uses logging, named as follows::" +msgstr "" + +#: ../Doc/howto/logging.rst:355 +msgid "" +"This means that logger names track the package/module hierarchy, and it's " +"intuitively obvious where events are logged just from the logger name." +msgstr "" + +#: ../Doc/howto/logging.rst:358 +msgid "" +"The root of the hierarchy of loggers is called the root logger. That's the " +"logger used by the functions :func:`debug`, :func:`info`, :func:`warning`, :" +"func:`error` and :func:`critical`, which just call the same-named method of " +"the root logger. The functions and the methods have the same signatures. The " +"root logger's name is printed as 'root' in the logged output." +msgstr "" + +#: ../Doc/howto/logging.rst:364 +msgid "" +"It is, of course, possible to log messages to different destinations. " +"Support is included in the package for writing log messages to files, HTTP " +"GET/POST locations, email via SMTP, generic sockets, queues, or OS-specific " +"logging mechanisms such as syslog or the Windows NT event log. Destinations " +"are served by :dfn:`handler` classes. You can create your own log " +"destination class if you have special requirements not met by any of the " +"built-in handler classes." +msgstr "" + +#: ../Doc/howto/logging.rst:371 +msgid "" +"By default, no destination is set for any logging messages. You can specify " +"a destination (such as console or file) by using :func:`basicConfig` as in " +"the tutorial examples. If you call the functions :func:`debug`, :func:" +"`info`, :func:`warning`, :func:`error` and :func:`critical`, they will check " +"to see if no destination is set; and if one is not set, they will set a " +"destination of the console (``sys.stderr``) and a default format for the " +"displayed message before delegating to the root logger to do the actual " +"message output." +msgstr "" + +#: ../Doc/howto/logging.rst:379 +msgid "The default format set by :func:`basicConfig` for messages is::" +msgstr "" + +#: ../Doc/howto/logging.rst:383 +msgid "" +"You can change this by passing a format string to :func:`basicConfig` with " +"the *format* keyword argument. For all options regarding how a format string " +"is constructed, see :ref:`formatter-objects`." +msgstr "" + +#: ../Doc/howto/logging.rst:388 +msgid "Logging Flow" +msgstr "" + +#: ../Doc/howto/logging.rst:390 +msgid "" +"The flow of log event information in loggers and handlers is illustrated in " +"the following diagram." +msgstr "" + +#: ../Doc/howto/logging.rst:396 +msgid "Loggers" +msgstr "" + +#: ../Doc/howto/logging.rst:398 +msgid "" +":class:`Logger` objects have a threefold job. First, they expose several " +"methods to application code so that applications can log messages at " +"runtime. Second, logger objects determine which log messages to act upon " +"based upon severity (the default filtering facility) or filter objects. " +"Third, logger objects pass along relevant log messages to all interested log " +"handlers." +msgstr "" + +#: ../Doc/howto/logging.rst:404 +msgid "" +"The most widely used methods on logger objects fall into two categories: " +"configuration and message sending." +msgstr "" + +#: ../Doc/howto/logging.rst:407 +msgid "These are the most common configuration methods:" +msgstr "" + +#: ../Doc/howto/logging.rst:409 +msgid "" +":meth:`Logger.setLevel` specifies the lowest-severity log message a logger " +"will handle, where debug is the lowest built-in severity level and critical " +"is the highest built-in severity. For example, if the severity level is " +"INFO, the logger will handle only INFO, WARNING, ERROR, and CRITICAL " +"messages and will ignore DEBUG messages." +msgstr "" + +#: ../Doc/howto/logging.rst:415 +msgid "" +":meth:`Logger.addHandler` and :meth:`Logger.removeHandler` add and remove " +"handler objects from the logger object. Handlers are covered in more detail " +"in :ref:`handler-basic`." +msgstr "" + +#: ../Doc/howto/logging.rst:419 +msgid "" +":meth:`Logger.addFilter` and :meth:`Logger.removeFilter` add and remove " +"filter objects from the logger object. Filters are covered in more detail " +"in :ref:`filter`." +msgstr "" + +#: ../Doc/howto/logging.rst:423 +msgid "" +"You don't need to always call these methods on every logger you create. See " +"the last two paragraphs in this section." +msgstr "" + +#: ../Doc/howto/logging.rst:426 +msgid "" +"With the logger object configured, the following methods create log messages:" +msgstr "" + +#: ../Doc/howto/logging.rst:428 +msgid "" +":meth:`Logger.debug`, :meth:`Logger.info`, :meth:`Logger.warning`, :meth:" +"`Logger.error`, and :meth:`Logger.critical` all create log records with a " +"message and a level that corresponds to their respective method names. The " +"message is actually a format string, which may contain the standard string " +"substitution syntax of ``%s``, ``%d``, ``%f``, and so on. The rest of their " +"arguments is a list of objects that correspond with the substitution fields " +"in the message. With regard to ``**kwargs``, the logging methods care only " +"about a keyword of ``exc_info`` and use it to determine whether to log " +"exception information." +msgstr "" + +#: ../Doc/howto/logging.rst:438 +msgid "" +":meth:`Logger.exception` creates a log message similar to :meth:`Logger." +"error`. The difference is that :meth:`Logger.exception` dumps a stack trace " +"along with it. Call this method only from an exception handler." +msgstr "" + +#: ../Doc/howto/logging.rst:442 +msgid "" +":meth:`Logger.log` takes a log level as an explicit argument. This is a " +"little more verbose for logging messages than using the log level " +"convenience methods listed above, but this is how to log at custom log " +"levels." +msgstr "" + +#: ../Doc/howto/logging.rst:446 +msgid "" +":func:`getLogger` returns a reference to a logger instance with the " +"specified name if it is provided, or ``root`` if not. The names are period-" +"separated hierarchical structures. Multiple calls to :func:`getLogger` with " +"the same name will return a reference to the same logger object. Loggers " +"that are further down in the hierarchical list are children of loggers " +"higher up in the list. For example, given a logger with a name of ``foo``, " +"loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all " +"descendants of ``foo``." +msgstr "" + +#: ../Doc/howto/logging.rst:454 +msgid "" +"Loggers have a concept of *effective level*. If a level is not explicitly " +"set on a logger, the level of its parent is used instead as its effective " +"level. If the parent has no explicit level set, *its* parent is examined, " +"and so on - all ancestors are searched until an explicitly set level is " +"found. The root logger always has an explicit level set (``WARNING`` by " +"default). When deciding whether to process an event, the effective level of " +"the logger is used to determine whether the event is passed to the logger's " +"handlers." +msgstr "" + +#: ../Doc/howto/logging.rst:462 +msgid "" +"Child loggers propagate messages up to the handlers associated with their " +"ancestor loggers. Because of this, it is unnecessary to define and configure " +"handlers for all the loggers an application uses. It is sufficient to " +"configure handlers for a top-level logger and create child loggers as " +"needed. (You can, however, turn off propagation by setting the *propagate* " +"attribute of a logger to *False*.)" +msgstr "" + +#: ../Doc/howto/logging.rst:473 +msgid "Handlers" +msgstr "" + +#: ../Doc/howto/logging.rst:475 +msgid "" +":class:`~logging.Handler` objects are responsible for dispatching the " +"appropriate log messages (based on the log messages' severity) to the " +"handler's specified destination. :class:`Logger` objects can add zero or " +"more handler objects to themselves with an :meth:`~Logger.addHandler` " +"method. As an example scenario, an application may want to send all log " +"messages to a log file, all log messages of error or higher to stdout, and " +"all messages of critical to an email address. This scenario requires three " +"individual handlers where each handler is responsible for sending messages " +"of a specific severity to a specific location." +msgstr "" + +#: ../Doc/howto/logging.rst:485 +msgid "" +"The standard library includes quite a few handler types (see :ref:`useful-" +"handlers`); the tutorials use mainly :class:`StreamHandler` and :class:" +"`FileHandler` in its examples." +msgstr "" + +#: ../Doc/howto/logging.rst:489 +msgid "" +"There are very few methods in a handler for application developers to " +"concern themselves with. The only handler methods that seem relevant for " +"application developers who are using the built-in handler objects (that is, " +"not creating custom handlers) are the following configuration methods:" +msgstr "" + +#: ../Doc/howto/logging.rst:494 +msgid "" +"The :meth:`~Handler.setLevel` method, just as in logger objects, specifies " +"the lowest severity that will be dispatched to the appropriate destination. " +"Why are there two :func:`setLevel` methods? The level set in the logger " +"determines which severity of messages it will pass to its handlers. The " +"level set in each handler determines which messages that handler will send " +"on." +msgstr "" + +#: ../Doc/howto/logging.rst:500 +msgid "" +":meth:`~Handler.setFormatter` selects a Formatter object for this handler to " +"use." +msgstr "" + +#: ../Doc/howto/logging.rst:503 +msgid "" +":meth:`~Handler.addFilter` and :meth:`~Handler.removeFilter` respectively " +"configure and deconfigure filter objects on handlers." +msgstr "" + +#: ../Doc/howto/logging.rst:506 +msgid "" +"Application code should not directly instantiate and use instances of :class:" +"`Handler`. Instead, the :class:`Handler` class is a base class that defines " +"the interface that all handlers should have and establishes some default " +"behavior that child classes can use (or override)." +msgstr "" + +#: ../Doc/howto/logging.rst:513 +msgid "Formatters" +msgstr "" + +#: ../Doc/howto/logging.rst:515 +msgid "" +"Formatter objects configure the final order, structure, and contents of the " +"log message. Unlike the base :class:`logging.Handler` class, application " +"code may instantiate formatter classes, although you could likely subclass " +"the formatter if your application needs special behavior. The constructor " +"takes three optional arguments -- a message format string, a date format " +"string and a style indicator." +msgstr "" + +#: ../Doc/howto/logging.rst:524 +msgid "" +"If there is no message format string, the default is to use the raw " +"message. If there is no date format string, the default date format is::" +msgstr "" + +#: ../Doc/howto/logging.rst:529 +msgid "" +"with the milliseconds tacked on at the end. The ``style`` is one of `%`, '{' " +"or '$'. If one of these is not specified, then '%' will be used." +msgstr "" + +#: ../Doc/howto/logging.rst:532 +msgid "" +"If the ``style`` is '%', the message format string uses ``%()s`` styled string substitution; the possible keys are documented in :" +"ref:`logrecord-attributes`. If the style is '{', the message format string " +"is assumed to be compatible with :meth:`str.format` (using keyword " +"arguments), while if the style is '$' then the message format string should " +"conform to what is expected by :meth:`string.Template.substitute`." +msgstr "" + +#: ../Doc/howto/logging.rst:539 +msgid "Added the ``style`` parameter." +msgstr "" + +#: ../Doc/howto/logging.rst:542 +msgid "" +"The following message format string will log the time in a human-readable " +"format, the severity of the message, and the contents of the message, in " +"that order::" +msgstr "" + +#: ../Doc/howto/logging.rst:548 +msgid "" +"Formatters use a user-configurable function to convert the creation time of " +"a record to a tuple. By default, :func:`time.localtime` is used; to change " +"this for a particular formatter instance, set the ``converter`` attribute of " +"the instance to a function with the same signature as :func:`time.localtime` " +"or :func:`time.gmtime`. To change it for all formatters, for example if you " +"want all logging times to be shown in GMT, set the ``converter`` attribute " +"in the Formatter class (to ``time.gmtime`` for GMT display)." +msgstr "" + +#: ../Doc/howto/logging.rst:558 +msgid "Configuring Logging" +msgstr "" + +#: ../Doc/howto/logging.rst:562 +msgid "Programmers can configure logging in three ways:" +msgstr "" + +#: ../Doc/howto/logging.rst:564 +msgid "" +"Creating loggers, handlers, and formatters explicitly using Python code that " +"calls the configuration methods listed above." +msgstr "" + +#: ../Doc/howto/logging.rst:566 +msgid "" +"Creating a logging config file and reading it using the :func:`fileConfig` " +"function." +msgstr "" + +#: ../Doc/howto/logging.rst:568 +msgid "" +"Creating a dictionary of configuration information and passing it to the :" +"func:`dictConfig` function." +msgstr "" + +#: ../Doc/howto/logging.rst:571 +msgid "" +"For the reference documentation on the last two options, see :ref:`logging-" +"config-api`. The following example configures a very simple logger, a " +"console handler, and a simple formatter using Python code::" +msgstr "" + +#: ../Doc/howto/logging.rst:601 +msgid "" +"Running this module from the command line produces the following output:" +msgstr "" + +#: ../Doc/howto/logging.rst:612 +msgid "" +"The following Python module creates a logger, handler, and formatter nearly " +"identical to those in the example listed above, with the only difference " +"being the names of the objects::" +msgstr "" + +#: ../Doc/howto/logging.rst:631 +msgid "Here is the logging.conf file::" +msgstr "" + +#: ../Doc/howto/logging.rst:662 +msgid "" +"The output is nearly identical to that of the non-config-file-based example:" +msgstr "" + +#: ../Doc/howto/logging.rst:673 +msgid "" +"You can see that the config file approach has a few advantages over the " +"Python code approach, mainly separation of configuration and code and the " +"ability of noncoders to easily modify the logging properties." +msgstr "" + +#: ../Doc/howto/logging.rst:677 +msgid "" +"The :func:`fileConfig` function takes a default parameter, " +"``disable_existing_loggers``, which defaults to ``True`` for reasons of " +"backward compatibility. This may or may not be what you want, since it will " +"cause any loggers existing before the :func:`fileConfig` call to be disabled " +"unless they (or an ancestor) are explicitly named in the configuration. " +"Please refer to the reference documentation for more information, and " +"specify ``False`` for this parameter if you wish." +msgstr "" + +#: ../Doc/howto/logging.rst:685 +msgid "" +"The dictionary passed to :func:`dictConfig` can also specify a Boolean value " +"with key ``disable_existing_loggers``, which if not specified explicitly in " +"the dictionary also defaults to being interpreted as ``True``. This leads " +"to the logger-disabling behaviour described above, which may not be what you " +"want - in which case, provide the key explicitly with a value of ``False``." +msgstr "" + +#: ../Doc/howto/logging.rst:695 +msgid "" +"Note that the class names referenced in config files need to be either " +"relative to the logging module, or absolute values which can be resolved " +"using normal import mechanisms. Thus, you could use either :class:`~logging." +"handlers.WatchedFileHandler` (relative to the logging module) or ``mypackage." +"mymodule.MyHandler`` (for a class defined in package ``mypackage`` and " +"module ``mymodule``, where ``mypackage`` is available on the Python import " +"path)." +msgstr "" + +#: ../Doc/howto/logging.rst:703 +msgid "" +"In Python 3.2, a new means of configuring logging has been introduced, using " +"dictionaries to hold configuration information. This provides a superset of " +"the functionality of the config-file-based approach outlined above, and is " +"the recommended configuration method for new applications and deployments. " +"Because a Python dictionary is used to hold configuration information, and " +"since you can populate that dictionary using different means, you have more " +"options for configuration. For example, you can use a configuration file in " +"JSON format, or, if you have access to YAML processing functionality, a file " +"in YAML format, to populate the configuration dictionary. Or, of course, you " +"can construct the dictionary in Python code, receive it in pickled form over " +"a socket, or use whatever approach makes sense for your application." +msgstr "" + +#: ../Doc/howto/logging.rst:715 +msgid "" +"Here's an example of the same configuration as above, in YAML format for the " +"new dictionary-based approach::" +msgstr "" + +#: ../Doc/howto/logging.rst:737 +msgid "" +"For more information about logging using a dictionary, see :ref:`logging-" +"config-api`." +msgstr "" + +#: ../Doc/howto/logging.rst:741 +msgid "What happens if no configuration is provided" +msgstr "" + +#: ../Doc/howto/logging.rst:743 +msgid "" +"If no logging configuration is provided, it is possible to have a situation " +"where a logging event needs to be output, but no handlers can be found to " +"output the event. The behaviour of the logging package in these " +"circumstances is dependent on the Python version." +msgstr "" + +#: ../Doc/howto/logging.rst:748 +msgid "For versions of Python prior to 3.2, the behaviour is as follows:" +msgstr "" + +#: ../Doc/howto/logging.rst:750 +msgid "" +"If *logging.raiseExceptions* is *False* (production mode), the event is " +"silently dropped." +msgstr "" + +#: ../Doc/howto/logging.rst:753 +msgid "" +"If *logging.raiseExceptions* is *True* (development mode), a message 'No " +"handlers could be found for logger X.Y.Z' is printed once." +msgstr "" + +#: ../Doc/howto/logging.rst:756 +msgid "In Python 3.2 and later, the behaviour is as follows:" +msgstr "" + +#: ../Doc/howto/logging.rst:758 +msgid "" +"The event is output using a 'handler of last resort', stored in ``logging." +"lastResort``. This internal handler is not associated with any logger, and " +"acts like a :class:`~logging.StreamHandler` which writes the event " +"description message to the current value of ``sys.stderr`` (therefore " +"respecting any redirections which may be in effect). No formatting is done " +"on the message - just the bare event description message is printed. The " +"handler's level is set to ``WARNING``, so all events at this and greater " +"severities will be output." +msgstr "" + +#: ../Doc/howto/logging.rst:767 +msgid "" +"To obtain the pre-3.2 behaviour, ``logging.lastResort`` can be set to *None*." +msgstr "" + +#: ../Doc/howto/logging.rst:772 +msgid "Configuring Logging for a Library" +msgstr "" + +#: ../Doc/howto/logging.rst:774 +msgid "" +"When developing a library which uses logging, you should take care to " +"document how the library uses logging - for example, the names of loggers " +"used. Some consideration also needs to be given to its logging " +"configuration. If the using application does not use logging, and library " +"code makes logging calls, then (as described in the previous section) events " +"of severity ``WARNING`` and greater will be printed to ``sys.stderr``. This " +"is regarded as the best default behaviour." +msgstr "" + +#: ../Doc/howto/logging.rst:782 +msgid "" +"If for some reason you *don't* want these messages printed in the absence of " +"any logging configuration, you can attach a do-nothing handler to the top-" +"level logger for your library. This avoids the message being printed, since " +"a handler will be always be found for the library's events: it just doesn't " +"produce any output. If the library user configures logging for application " +"use, presumably that configuration will add some handlers, and if levels are " +"suitably configured then logging calls made in library code will send output " +"to those handlers, as normal." +msgstr "" + +#: ../Doc/howto/logging.rst:791 +msgid "" +"A do-nothing handler is included in the logging package: :class:`~logging." +"NullHandler` (since Python 3.1). An instance of this handler could be added " +"to the top-level logger of the logging namespace used by the library (*if* " +"you want to prevent your library's logged events being output to ``sys." +"stderr`` in the absence of logging configuration). If all logging by a " +"library *foo* is done using loggers with names matching 'foo.x', 'foo.x.y', " +"etc. then the code::" +msgstr "" + +#: ../Doc/howto/logging.rst:802 +msgid "" +"should have the desired effect. If an organisation produces a number of " +"libraries, then the logger name specified can be 'orgname.foo' rather than " +"just 'foo'." +msgstr "" + +#: ../Doc/howto/logging.rst:806 +msgid "" +"It is strongly advised that you *do not add any handlers other than* :class:" +"`~logging.NullHandler` *to your library's loggers*. This is because the " +"configuration of handlers is the prerogative of the application developer " +"who uses your library. The application developer knows their target audience " +"and what handlers are most appropriate for their application: if you add " +"handlers 'under the hood', you might well interfere with their ability to " +"carry out unit tests and deliver logs which suit their requirements." +msgstr "" + +#: ../Doc/howto/logging.rst:817 +msgid "Logging Levels" +msgstr "" + +#: ../Doc/howto/logging.rst:819 +msgid "" +"The numeric values of logging levels are given in the following table. These " +"are primarily of interest if you want to define your own levels, and need " +"them to have specific values relative to the predefined levels. If you " +"define a level with the same numeric value, it overwrites the predefined " +"value; the predefined name is lost." +msgstr "" + +#: ../Doc/howto/logging.rst:826 +msgid "Numeric value" +msgstr "" + +#: ../Doc/howto/logging.rst:828 +msgid "50" +msgstr "" + +#: ../Doc/howto/logging.rst:830 +msgid "40" +msgstr "" + +#: ../Doc/howto/logging.rst:832 +msgid "30" +msgstr "" + +#: ../Doc/howto/logging.rst:834 +msgid "20" +msgstr "" + +#: ../Doc/howto/logging.rst:836 +msgid "10" +msgstr "" + +#: ../Doc/howto/logging.rst:838 +msgid "``NOTSET``" +msgstr "" + +#: ../Doc/howto/logging.rst:838 +msgid "0" +msgstr "" + +#: ../Doc/howto/logging.rst:841 +msgid "" +"Levels can also be associated with loggers, being set either by the " +"developer or through loading a saved logging configuration. When a logging " +"method is called on a logger, the logger compares its own level with the " +"level associated with the method call. If the logger's level is higher than " +"the method call's, no logging message is actually generated. This is the " +"basic mechanism controlling the verbosity of logging output." +msgstr "" + +#: ../Doc/howto/logging.rst:848 +msgid "" +"Logging messages are encoded as instances of the :class:`~logging.LogRecord` " +"class. When a logger decides to actually log an event, a :class:`~logging." +"LogRecord` instance is created from the logging message." +msgstr "" + +#: ../Doc/howto/logging.rst:852 +msgid "" +"Logging messages are subjected to a dispatch mechanism through the use of :" +"dfn:`handlers`, which are instances of subclasses of the :class:`Handler` " +"class. Handlers are responsible for ensuring that a logged message (in the " +"form of a :class:`LogRecord`) ends up in a particular location (or set of " +"locations) which is useful for the target audience for that message (such as " +"end users, support desk staff, system administrators, developers). Handlers " +"are passed :class:`LogRecord` instances intended for particular " +"destinations. Each logger can have zero, one or more handlers associated " +"with it (via the :meth:`~Logger.addHandler` method of :class:`Logger`). In " +"addition to any handlers directly associated with a logger, *all handlers " +"associated with all ancestors of the logger* are called to dispatch the " +"message (unless the *propagate* flag for a logger is set to a false value, " +"at which point the passing to ancestor handlers stops)." +msgstr "" + +#: ../Doc/howto/logging.rst:866 +msgid "" +"Just as for loggers, handlers can have levels associated with them. A " +"handler's level acts as a filter in the same way as a logger's level does. " +"If a handler decides to actually dispatch an event, the :meth:`~Handler." +"emit` method is used to send the message to its destination. Most user-" +"defined subclasses of :class:`Handler` will need to override this :meth:" +"`~Handler.emit`." +msgstr "" + +#: ../Doc/howto/logging.rst:875 +msgid "Custom Levels" +msgstr "" + +#: ../Doc/howto/logging.rst:877 +msgid "" +"Defining your own levels is possible, but should not be necessary, as the " +"existing levels have been chosen on the basis of practical experience. " +"However, if you are convinced that you need custom levels, great care should " +"be exercised when doing this, and it is possibly *a very bad idea to define " +"custom levels if you are developing a library*. That's because if multiple " +"library authors all define their own custom levels, there is a chance that " +"the logging output from such multiple libraries used together will be " +"difficult for the using developer to control and/or interpret, because a " +"given numeric value might mean different things for different libraries." +msgstr "" + +#: ../Doc/howto/logging.rst:890 +msgid "Useful Handlers" +msgstr "" + +#: ../Doc/howto/logging.rst:892 +msgid "" +"In addition to the base :class:`Handler` class, many useful subclasses are " +"provided:" +msgstr "" + +#: ../Doc/howto/logging.rst:895 +msgid "" +":class:`StreamHandler` instances send messages to streams (file-like " +"objects)." +msgstr "" + +#: ../Doc/howto/logging.rst:898 +msgid ":class:`FileHandler` instances send messages to disk files." +msgstr "" + +#: ../Doc/howto/logging.rst:900 +msgid "" +":class:`~handlers.BaseRotatingHandler` is the base class for handlers that " +"rotate log files at a certain point. It is not meant to be instantiated " +"directly. Instead, use :class:`~handlers.RotatingFileHandler` or :class:" +"`~handlers.TimedRotatingFileHandler`." +msgstr "" + +#: ../Doc/howto/logging.rst:905 +msgid "" +":class:`~handlers.RotatingFileHandler` instances send messages to disk " +"files, with support for maximum log file sizes and log file rotation." +msgstr "" + +#: ../Doc/howto/logging.rst:908 +msgid "" +":class:`~handlers.TimedRotatingFileHandler` instances send messages to disk " +"files, rotating the log file at certain timed intervals." +msgstr "" + +#: ../Doc/howto/logging.rst:911 +msgid "" +":class:`~handlers.SocketHandler` instances send messages to TCP/IP sockets. " +"Since 3.4, Unix domain sockets are also supported." +msgstr "" + +#: ../Doc/howto/logging.rst:914 +msgid "" +":class:`~handlers.DatagramHandler` instances send messages to UDP sockets. " +"Since 3.4, Unix domain sockets are also supported." +msgstr "" + +#: ../Doc/howto/logging.rst:917 +msgid "" +":class:`~handlers.SMTPHandler` instances send messages to a designated email " +"address." +msgstr "" + +#: ../Doc/howto/logging.rst:920 +msgid "" +":class:`~handlers.SysLogHandler` instances send messages to a Unix syslog " +"daemon, possibly on a remote machine." +msgstr "" + +#: ../Doc/howto/logging.rst:923 +msgid "" +":class:`~handlers.NTEventLogHandler` instances send messages to a Windows " +"NT/2000/XP event log." +msgstr "" + +#: ../Doc/howto/logging.rst:926 +msgid "" +":class:`~handlers.MemoryHandler` instances send messages to a buffer in " +"memory, which is flushed whenever specific criteria are met." +msgstr "" + +#: ../Doc/howto/logging.rst:929 +msgid "" +":class:`~handlers.HTTPHandler` instances send messages to an HTTP server " +"using either ``GET`` or ``POST`` semantics." +msgstr "" + +#: ../Doc/howto/logging.rst:932 +msgid "" +":class:`~handlers.WatchedFileHandler` instances watch the file they are " +"logging to. If the file changes, it is closed and reopened using the file " +"name. This handler is only useful on Unix-like systems; Windows does not " +"support the underlying mechanism used." +msgstr "" + +#: ../Doc/howto/logging.rst:937 +msgid "" +":class:`~handlers.QueueHandler` instances send messages to a queue, such as " +"those implemented in the :mod:`queue` or :mod:`multiprocessing` modules." +msgstr "" + +#: ../Doc/howto/logging.rst:940 +msgid "" +":class:`NullHandler` instances do nothing with error messages. They are used " +"by library developers who want to use logging, but want to avoid the 'No " +"handlers could be found for logger XXX' message which can be displayed if " +"the library user has not configured logging. See :ref:`library-config` for " +"more information." +msgstr "" + +#: ../Doc/howto/logging.rst:946 +msgid "The :class:`NullHandler` class." +msgstr "" + +#: ../Doc/howto/logging.rst:949 +msgid "The :class:`~handlers.QueueHandler` class." +msgstr "" + +#: ../Doc/howto/logging.rst:952 +msgid "" +"The :class:`NullHandler`, :class:`StreamHandler` and :class:`FileHandler` " +"classes are defined in the core logging package. The other handlers are " +"defined in a sub- module, :mod:`logging.handlers`. (There is also another " +"sub-module, :mod:`logging.config`, for configuration functionality.)" +msgstr "" + +#: ../Doc/howto/logging.rst:957 +msgid "" +"Logged messages are formatted for presentation through instances of the :" +"class:`Formatter` class. They are initialized with a format string suitable " +"for use with the % operator and a dictionary." +msgstr "" + +#: ../Doc/howto/logging.rst:961 +msgid "" +"For formatting multiple messages in a batch, instances of :class:`~handlers." +"BufferingFormatter` can be used. In addition to the format string (which is " +"applied to each message in the batch), there is provision for header and " +"trailer format strings." +msgstr "" + +#: ../Doc/howto/logging.rst:966 +msgid "" +"When filtering based on logger level and/or handler level is not enough, " +"instances of :class:`Filter` can be added to both :class:`Logger` and :class:" +"`Handler` instances (through their :meth:`~Handler.addFilter` method). " +"Before deciding to process a message further, both loggers and handlers " +"consult all their filters for permission. If any filter returns a false " +"value, the message is not processed further." +msgstr "" + +#: ../Doc/howto/logging.rst:973 +msgid "" +"The basic :class:`Filter` functionality allows filtering by specific logger " +"name. If this feature is used, messages sent to the named logger and its " +"children are allowed through the filter, and all others dropped." +msgstr "" + +#: ../Doc/howto/logging.rst:981 +msgid "Exceptions raised during logging" +msgstr "" + +#: ../Doc/howto/logging.rst:983 +msgid "" +"The logging package is designed to swallow exceptions which occur while " +"logging in production. This is so that errors which occur while handling " +"logging events - such as logging misconfiguration, network or other similar " +"errors - do not cause the application using logging to terminate prematurely." +msgstr "" + +#: ../Doc/howto/logging.rst:988 +msgid "" +":class:`SystemExit` and :class:`KeyboardInterrupt` exceptions are never " +"swallowed. Other exceptions which occur during the :meth:`~Handler.emit` " +"method of a :class:`Handler` subclass are passed to its :meth:`~Handler." +"handleError` method." +msgstr "" + +#: ../Doc/howto/logging.rst:993 +msgid "" +"The default implementation of :meth:`~Handler.handleError` in :class:" +"`Handler` checks to see if a module-level variable, :data:`raiseExceptions`, " +"is set. If set, a traceback is printed to :data:`sys.stderr`. If not set, " +"the exception is swallowed." +msgstr "" + +#: ../Doc/howto/logging.rst:998 +msgid "" +"The default value of :data:`raiseExceptions` is ``True``. This is because " +"during development, you typically want to be notified of any exceptions that " +"occur. It's advised that you set :data:`raiseExceptions` to ``False`` for " +"production usage." +msgstr "" + +#: ../Doc/howto/logging.rst:1008 +msgid "Using arbitrary objects as messages" +msgstr "" + +#: ../Doc/howto/logging.rst:1010 +msgid "" +"In the preceding sections and examples, it has been assumed that the message " +"passed when logging the event is a string. However, this is not the only " +"possibility. You can pass an arbitrary object as a message, and its :meth:" +"`~object.__str__` method will be called when the logging system needs to " +"convert it to a string representation. In fact, if you want to, you can " +"avoid computing a string representation altogether - for example, the :class:" +"`~handlers.SocketHandler` emits an event by pickling it and sending it over " +"the wire." +msgstr "" + +#: ../Doc/howto/logging.rst:1021 +msgid "Optimization" +msgstr "" + +#: ../Doc/howto/logging.rst:1023 +msgid "" +"Formatting of message arguments is deferred until it cannot be avoided. " +"However, computing the arguments passed to the logging method can also be " +"expensive, and you may want to avoid doing it if the logger will just throw " +"away your event. To decide what to do, you can call the :meth:`~Logger." +"isEnabledFor` method which takes a level argument and returns true if the " +"event would be created by the Logger for that level of call. You can write " +"code like this::" +msgstr "" + +#: ../Doc/howto/logging.rst:1035 +msgid "" +"so that if the logger's threshold is set above ``DEBUG``, the calls to :func:" +"`expensive_func1` and :func:`expensive_func2` are never made." +msgstr "" + +#: ../Doc/howto/logging.rst:1038 +msgid "" +"In some cases, :meth:`~Logger.isEnabledFor` can itself be more expensive " +"than you'd like (e.g. for deeply nested loggers where an explicit level is " +"only set high up in the logger hierarchy). In such cases (or if you want to " +"avoid calling a method in tight loops), you can cache the result of a call " +"to :meth:`~Logger.isEnabledFor` in a local or instance variable, and use " +"that instead of calling the method each time. Such a cached value would only " +"need to be recomputed when the logging configuration changes dynamically " +"while the application is running (which is not all that common)." +msgstr "" + +#: ../Doc/howto/logging.rst:1047 +msgid "" +"There are other optimizations which can be made for specific applications " +"which need more precise control over what logging information is collected. " +"Here's a list of things you can do to avoid processing during logging which " +"you don't need:" +msgstr "" + +#: ../Doc/howto/logging.rst:1053 +msgid "What you don't want to collect" +msgstr "" + +#: ../Doc/howto/logging.rst:1053 +msgid "How to avoid collecting it" +msgstr "" + +#: ../Doc/howto/logging.rst:1055 +msgid "Information about where calls were made from." +msgstr "" + +#: ../Doc/howto/logging.rst:1055 +msgid "" +"Set ``logging._srcfile`` to ``None``. This avoids calling :func:`sys." +"_getframe`, which may help to speed up your code in environments like PyPy " +"(which can't speed up code that uses :func:`sys._getframe`), if and when " +"PyPy supports Python 3.x." +msgstr "" + +#: ../Doc/howto/logging.rst:1063 +msgid "Threading information." +msgstr "" + +#: ../Doc/howto/logging.rst:1063 +msgid "Set ``logging.logThreads`` to ``0``." +msgstr "" + +#: ../Doc/howto/logging.rst:1065 +msgid "Process information." +msgstr "" + +#: ../Doc/howto/logging.rst:1065 +msgid "Set ``logging.logProcesses`` to ``0``." +msgstr "" + +#: ../Doc/howto/logging.rst:1068 +msgid "" +"Also note that the core logging module only includes the basic handlers. If " +"you don't import :mod:`logging.handlers` and :mod:`logging.config`, they " +"won't take up any memory." +msgstr "" + +#: ../Doc/howto/logging.rst:1075 ../Doc/howto/logging-cookbook.rst:1306 +msgid "Module :mod:`logging`" +msgstr "" + +#: ../Doc/howto/logging.rst:1075 ../Doc/howto/logging-cookbook.rst:1306 +msgid "API reference for the logging module." +msgstr "" + +#: ../Doc/howto/logging.rst:1078 ../Doc/howto/logging-cookbook.rst:1309 +msgid "Module :mod:`logging.config`" +msgstr "" + +#: ../Doc/howto/logging.rst:1078 ../Doc/howto/logging-cookbook.rst:1309 +msgid "Configuration API for the logging module." +msgstr "" + +#: ../Doc/howto/logging.rst:1081 ../Doc/howto/logging-cookbook.rst:1312 +msgid "Module :mod:`logging.handlers`" +msgstr "" + +#: ../Doc/howto/logging.rst:1081 ../Doc/howto/logging-cookbook.rst:1312 +msgid "Useful handlers included with the logging module." +msgstr "" + +#: ../Doc/howto/logging.rst:1083 +msgid ":ref:`A logging cookbook `" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:5 +msgid "Logging Cookbook" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:9 +msgid "" +"This page contains a number of recipes related to logging, which have been " +"found useful in the past." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:15 +msgid "Using logging in multiple modules" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:17 +msgid "" +"Multiple calls to ``logging.getLogger('someLogger')`` return a reference to " +"the same logger object. This is true not only within the same module, but " +"also across modules as long as it is in the same Python interpreter " +"process. It is true for references to the same object; additionally, " +"application code can define and configure a parent logger in one module and " +"create (but not configure) a child logger in a separate module, and all " +"logger calls to the child will pass up to the parent. Here is a main " +"module::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:55 +msgid "Here is the auxiliary module::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:99 +msgid "Logging from multiple threads" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:101 +msgid "" +"Logging from multiple threads requires no special effort. The following " +"example shows logging from the main (initial) thread and another thread::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:130 +msgid "When run, the script should print something like the following::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:150 +msgid "" +"This shows the logging output interspersed as one might expect. This " +"approach works for more threads than shown here, of course." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:154 +msgid "Multiple handlers and formatters" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:156 +msgid "" +"Loggers are plain Python objects. The :meth:`~Logger.addHandler` method has " +"no minimum or maximum quota for the number of handlers you may add. " +"Sometimes it will be beneficial for an application to log all messages of " +"all severities to a text file while simultaneously logging errors or above " +"to the console. To set this up, simply configure the appropriate handlers. " +"The logging calls in the application code will remain unchanged. Here is a " +"slight modification to the previous simple module-based configuration " +"example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:189 +msgid "" +"Notice that the 'application' code does not care about multiple handlers. " +"All that changed was the addition and configuration of a new handler named " +"*fh*." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:192 +msgid "" +"The ability to create new handlers with higher- or lower-severity filters " +"can be very helpful when writing and testing an application. Instead of " +"using many ``print`` statements for debugging, use ``logger.debug``: Unlike " +"the print statements, which you will have to delete or comment out later, " +"the logger.debug statements can remain intact in the source code and remain " +"dormant until you need them again. At that time, the only change that needs " +"to happen is to modify the severity level of the logger and/or handler to " +"debug." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:203 +msgid "Logging to multiple destinations" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:205 +msgid "" +"Let's say you want to log to console and file with different message formats " +"and in differing circumstances. Say you want to log messages with levels of " +"DEBUG and higher to file, and those messages at level INFO and higher to the " +"console. Let's also assume that the file should contain timestamps, but the " +"console messages should not. Here's how you can achieve this::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:243 +msgid "When you run this, on the console you will see ::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:250 +msgid "and in the file you will see something like ::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:258 +msgid "" +"As you can see, the DEBUG message only shows up in the file. The other " +"messages are sent to both destinations." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:261 +msgid "" +"This example uses console and file handlers, but you can use any number and " +"combination of handlers you choose." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:266 +msgid "Configuration server example" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:268 +msgid "Here is an example of a module using the logging configuration server::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:299 +msgid "" +"And here is a script that takes a filename and sends that file to the " +"server, properly preceded with the binary-encoded length, as the new logging " +"configuration::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:322 +msgid "Dealing with handlers that block" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:326 +msgid "" +"Sometimes you have to get your logging handlers to do their work without " +"blocking the thread you're logging from. This is common in Web applications, " +"though of course it also occurs in other scenarios." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:330 +msgid "" +"A common culprit which demonstrates sluggish behaviour is the :class:" +"`SMTPHandler`: sending emails can take a long time, for a number of reasons " +"outside the developer's control (for example, a poorly performing mail or " +"network infrastructure). But almost any network-based handler can block: " +"Even a :class:`SocketHandler` operation may do a DNS query under the hood " +"which is too slow (and this query can be deep in the socket library code, " +"below the Python layer, and outside your control)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:338 +msgid "" +"One solution is to use a two-part approach. For the first part, attach only " +"a :class:`QueueHandler` to those loggers which are accessed from performance-" +"critical threads. They simply write to their queue, which can be sized to a " +"large enough capacity or initialized with no upper bound to their size. The " +"write to the queue will typically be accepted quickly, though you will " +"probably need to catch the :exc:`queue.Full` exception as a precaution in " +"your code. If you are a library developer who has performance-critical " +"threads in their code, be sure to document this (together with a suggestion " +"to attach only ``QueueHandlers`` to your loggers) for the benefit of other " +"developers who will use your code." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:349 +msgid "" +"The second part of the solution is :class:`QueueListener`, which has been " +"designed as the counterpart to :class:`QueueHandler`. A :class:" +"`QueueListener` is very simple: it's passed a queue and some handlers, and " +"it fires up an internal thread which listens to its queue for LogRecords " +"sent from ``QueueHandlers`` (or any other source of ``LogRecords``, for that " +"matter). The ``LogRecords`` are removed from the queue and passed to the " +"handlers for processing." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:357 +msgid "" +"The advantage of having a separate :class:`QueueListener` class is that you " +"can use the same instance to service multiple ``QueueHandlers``. This is " +"more resource-friendly than, say, having threaded versions of the existing " +"handler classes, which would eat up one thread per handler for no particular " +"benefit." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:362 +msgid "An example of using these two classes follows (imports omitted)::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:380 +msgid "which, when run, will produce:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:386 +msgid "" +"Prior to Python 3.5, the :class:`QueueListener` always passed every message " +"received from the queue to every handler it was initialized with. (This was " +"because it was assumed that level filtering was all done on the other side, " +"where the queue is filled.) From 3.5 onwards, this behaviour can be changed " +"by passing a keyword argument ``respect_handler_level=True`` to the " +"listener's constructor. When this is done, the listener compares the level " +"of each message with the handler's level, and only passes a message to a " +"handler if it's appropriate to do so." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:399 +msgid "Sending and receiving logging events across a network" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:401 +msgid "" +"Let's say you want to send logging events across a network, and handle them " +"at the receiving end. A simple way of doing this is attaching a :class:" +"`SocketHandler` instance to the root logger at the sending end::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:429 +msgid "" +"At the receiving end, you can set up a receiver using the :mod:" +"`socketserver` module. Here is a basic working example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:517 +msgid "" +"First run the server, and then the client. On the client side, nothing is " +"printed on the console; on the server side, you should see something like::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:527 +msgid "" +"Note that there are some security issues with pickle in some scenarios. If " +"these affect you, you can use an alternative serialization scheme by " +"overriding the :meth:`~handlers.SocketHandler.makePickle` method and " +"implementing your alternative there, as well as adapting the above script to " +"use your alternative serialization." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:537 +msgid "Adding contextual information to your logging output" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:539 +msgid "" +"Sometimes you want logging output to contain contextual information in " +"addition to the parameters passed to the logging call. For example, in a " +"networked application, it may be desirable to log client-specific " +"information in the log (e.g. remote client's username, or IP address). " +"Although you could use the *extra* parameter to achieve this, it's not " +"always convenient to pass the information in this way. While it might be " +"tempting to create :class:`Logger` instances on a per-connection basis, this " +"is not a good idea because these instances are not garbage collected. While " +"this is not a problem in practice, when the number of :class:`Logger` " +"instances is dependent on the level of granularity you want to use in " +"logging an application, it could be hard to manage if the number of :class:" +"`Logger` instances becomes effectively unbounded." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:554 +msgid "Using LoggerAdapters to impart contextual information" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:556 +msgid "" +"An easy way in which you can pass contextual information to be output along " +"with logging event information is to use the :class:`LoggerAdapter` class. " +"This class is designed to look like a :class:`Logger`, so that you can call :" +"meth:`debug`, :meth:`info`, :meth:`warning`, :meth:`error`, :meth:" +"`exception`, :meth:`critical` and :meth:`log`. These methods have the same " +"signatures as their counterparts in :class:`Logger`, so you can use the two " +"types of instances interchangeably." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:564 +msgid "" +"When you create an instance of :class:`LoggerAdapter`, you pass it a :class:" +"`Logger` instance and a dict-like object which contains your contextual " +"information. When you call one of the logging methods on an instance of :" +"class:`LoggerAdapter`, it delegates the call to the underlying instance of :" +"class:`Logger` passed to its constructor, and arranges to pass the " +"contextual information in the delegated call. Here's a snippet from the code " +"of :class:`LoggerAdapter`::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:580 +msgid "" +"The :meth:`~LoggerAdapter.process` method of :class:`LoggerAdapter` is where " +"the contextual information is added to the logging output. It's passed the " +"message and keyword arguments of the logging call, and it passes back " +"(potentially) modified versions of these to use in the call to the " +"underlying logger. The default implementation of this method leaves the " +"message alone, but inserts an 'extra' key in the keyword argument whose " +"value is the dict-like object passed to the constructor. Of course, if you " +"had passed an 'extra' keyword argument in the call to the adapter, it will " +"be silently overwritten." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:589 +msgid "" +"The advantage of using 'extra' is that the values in the dict-like object " +"are merged into the :class:`LogRecord` instance's __dict__, allowing you to " +"use customized strings with your :class:`Formatter` instances which know " +"about the keys of the dict-like object. If you need a different method, e.g. " +"if you want to prepend or append the contextual information to the message " +"string, you just need to subclass :class:`LoggerAdapter` and override :meth:" +"`~LoggerAdapter.process` to do what you need. Here is a simple example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:605 +msgid "which you can use like this::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:610 +msgid "" +"Then any events that you log to the adapter will have the value of " +"``some_conn_id`` prepended to the log messages." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:614 +msgid "Using objects other than dicts to pass contextual information" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:616 +msgid "" +"You don't need to pass an actual dict to a :class:`LoggerAdapter` - you " +"could pass an instance of a class which implements ``__getitem__`` and " +"``__iter__`` so that it looks like a dict to logging. This would be useful " +"if you want to generate values dynamically (whereas the values in a dict " +"would be constant)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:625 +msgid "Using Filters to impart contextual information" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:627 +msgid "" +"You can also add contextual information to log output using a user-defined :" +"class:`Filter`. ``Filter`` instances are allowed to modify the " +"``LogRecords`` passed to them, including adding additional attributes which " +"can then be output using a suitable format string, or if needed a custom :" +"class:`Formatter`." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:632 +msgid "" +"For example in a web application, the request being processed (or at least, " +"the interesting parts of it) can be stored in a threadlocal (:class:" +"`threading.local`) variable, and then accessed from a ``Filter`` to add, " +"say, information from the request - say, the remote IP address and remote " +"user's username - to the ``LogRecord``, using the attribute names 'ip' and " +"'user' as in the ``LoggerAdapter`` example above. In that case, the same " +"format string can be used to get similar output to that shown above. Here's " +"an example script::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:678 +msgid "which, when run, produces something like::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:697 +msgid "Logging to a single file from multiple processes" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:699 +msgid "" +"Although logging is thread-safe, and logging to a single file from multiple " +"threads in a single process *is* supported, logging to a single file from " +"*multiple processes* is *not* supported, because there is no standard way to " +"serialize access to a single file across multiple processes in Python. If " +"you need to log to a single file from multiple processes, one way of doing " +"this is to have all the processes log to a :class:`~handlers.SocketHandler`, " +"and have a separate process which implements a socket server which reads " +"from the socket and logs to file. (If you prefer, you can dedicate one " +"thread in one of the existing processes to perform this function.) :ref:" +"`This section ` documents this approach in more detail and " +"includes a working socket receiver which can be used as a starting point for " +"you to adapt in your own applications." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:712 +msgid "" +"If you are using a recent version of Python which includes the :mod:" +"`multiprocessing` module, you could write your own handler which uses the :" +"class:`~multiprocessing.Lock` class from this module to serialize access to " +"the file from your processes. The existing :class:`FileHandler` and " +"subclasses do not make use of :mod:`multiprocessing` at present, though they " +"may do so in the future. Note that at present, the :mod:`multiprocessing` " +"module does not provide working lock functionality on all platforms (see " +"https://bugs.python.org/issue3770)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:723 +msgid "" +"Alternatively, you can use a ``Queue`` and a :class:`QueueHandler` to send " +"all logging events to one of the processes in your multi-process " +"application. The following example script demonstrates how you can do this; " +"in the example a separate listener process listens for events sent by other " +"processes and logs them according to its own logging configuration. Although " +"the example only demonstrates one way of doing it (for example, you may want " +"to use a listener thread rather than a separate listener process -- the " +"implementation would be analogous) it does allow for completely different " +"logging configurations for the listener and the other processes in your " +"application, and can be used as the basis for code meeting your own specific " +"requirements::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:839 +msgid "" +"A variant of the above script keeps the logging in the main process, in a " +"separate thread::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:934 +msgid "" +"This variant shows how you can e.g. apply configuration for particular " +"loggers - e.g. the ``foo`` logger has a special handler which stores all " +"events in the ``foo`` subsystem in a file ``mplog-foo.log``. This will be " +"used by the logging machinery in the main process (even though the logging " +"events are generated in the worker processes) to direct the messages to the " +"appropriate destinations." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:941 +msgid "Using file rotation" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:946 +msgid "" +"Sometimes you want to let a log file grow to a certain size, then open a new " +"file and log to that. You may want to keep a certain number of these files, " +"and when that many files have been created, rotate the files so that the " +"number of files and the size of the files both remain bounded. For this " +"usage pattern, the logging package provides a :class:`~handlers." +"RotatingFileHandler`::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:978 +msgid "" +"The result should be 6 separate files, each with part of the log history for " +"the application::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:988 +msgid "" +"The most current file is always :file:`logging_rotatingfile_example.out`, " +"and each time it reaches the size limit it is renamed with the suffix " +"``.1``. Each of the existing backup files is renamed to increment the suffix " +"(``.1`` becomes ``.2``, etc.) and the ``.6`` file is erased." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:993 +msgid "" +"Obviously this example sets the log length much too small as an extreme " +"example. You would want to set *maxBytes* to an appropriate value." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:999 +msgid "Use of alternative formatting styles" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1001 +msgid "" +"When logging was added to the Python standard library, the only way of " +"formatting messages with variable content was to use the %-formatting " +"method. Since then, Python has gained two new formatting approaches: :class:" +"`string.Template` (added in Python 2.4) and :meth:`str.format` (added in " +"Python 2.6)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1007 +msgid "" +"Logging (as of 3.2) provides improved support for these two additional " +"formatting styles. The :class:`Formatter` class been enhanced to take an " +"additional, optional keyword parameter named ``style``. This defaults to " +"``'%'``, but other possible values are ``'{'`` and ``'$'``, which correspond " +"to the other two formatting styles. Backwards compatibility is maintained by " +"default (as you would expect), but by explicitly specifying a style " +"parameter, you get the ability to specify format strings which work with :" +"meth:`str.format` or :class:`string.Template`. Here's an example console " +"session to show the possibilities:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1041 +msgid "" +"Note that the formatting of logging messages for final output to logs is " +"completely independent of how an individual logging message is constructed. " +"That can still use %-formatting, as shown here::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1049 +msgid "" +"Logging calls (``logger.debug()``, ``logger.info()`` etc.) only take " +"positional parameters for the actual logging message itself, with keyword " +"parameters used only for determining options for how to handle the actual " +"logging call (e.g. the ``exc_info`` keyword parameter to indicate that " +"traceback information should be logged, or the ``extra`` keyword parameter " +"to indicate additional contextual information to be added to the log). So " +"you cannot directly make logging calls using :meth:`str.format` or :class:" +"`string.Template` syntax, because internally the logging package uses %-" +"formatting to merge the format string and the variable arguments. There " +"would no changing this while preserving backward compatibility, since all " +"logging calls which are out there in existing code will be using %-format " +"strings." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1062 +msgid "" +"There is, however, a way that you can use {}- and $- formatting to construct " +"your individual log messages. Recall that for a message you can use an " +"arbitrary object as a message format string, and that the logging package " +"will call ``str()`` on that object to get the actual format string. Consider " +"the following two classes::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1086 +msgid "" +"Either of these can be used in place of a format string, to allow {}- or $-" +"formatting to be used to build the actual \"message\" part which appears in " +"the formatted log output in place of \"%(message)s\" or \"{message}\" or " +"\"$message\". It's a little unwieldy to use the class names whenever you " +"want to log something, but it's quite palatable if you use an alias such as " +"__ (double underscore – not to be confused with _, the single underscore " +"used as a synonym/alias for :func:`gettext.gettext` or its brethren)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1094 +msgid "" +"The above classes are not included in Python, though they're easy enough to " +"copy and paste into your own code. They can be used as follows (assuming " +"that they're declared in a module called ``wherever``):" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1116 +msgid "" +"While the above examples use ``print()`` to show how the formatting works, " +"you would of course use ``logger.debug()`` or similar to actually log using " +"this approach." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1120 +msgid "" +"One thing to note is that you pay no significant performance penalty with " +"this approach: the actual formatting happens not when you make the logging " +"call, but when (and if) the logged message is actually about to be output to " +"a log by a handler. So the only slightly unusual thing which might trip you " +"up is that the parentheses go around the format string and the arguments, " +"not just the format string. That's because the __ notation is just syntax " +"sugar for a constructor call to one of the XXXMessage classes." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1128 +msgid "" +"If you prefer, you can use a :class:`LoggerAdapter` to achieve a similar " +"effect to the above, as in the following example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1159 +msgid "" +"The above script should log the message ``Hello, world!`` when run with " +"Python 3.2 or later." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1168 +msgid "Customizing ``LogRecord``" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1170 +msgid "" +"Every logging event is represented by a :class:`LogRecord` instance. When an " +"event is logged and not filtered out by a logger's level, a :class:" +"`LogRecord` is created, populated with information about the event and then " +"passed to the handlers for that logger (and its ancestors, up to and " +"including the logger where further propagation up the hierarchy is " +"disabled). Before Python 3.2, there were only two places where this creation " +"was done:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1177 +msgid "" +":meth:`Logger.makeRecord`, which is called in the normal process of logging " +"an event. This invoked :class:`LogRecord` directly to create an instance." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1180 +msgid "" +":func:`makeLogRecord`, which is called with a dictionary containing " +"attributes to be added to the LogRecord. This is typically invoked when a " +"suitable dictionary has been received over the network (e.g. in pickle form " +"via a :class:`~handlers.SocketHandler`, or in JSON form via an :class:" +"`~handlers.HTTPHandler`)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1186 +msgid "" +"This has usually meant that if you need to do anything special with a :class:" +"`LogRecord`, you've had to do one of the following." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1189 +msgid "" +"Create your own :class:`Logger` subclass, which overrides :meth:`Logger." +"makeRecord`, and set it using :func:`~logging.setLoggerClass` before any " +"loggers that you care about are instantiated." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1192 +msgid "" +"Add a :class:`Filter` to a logger or handler, which does the necessary " +"special manipulation you need when its :meth:`~Filter.filter` method is " +"called." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1196 +msgid "" +"The first approach would be a little unwieldy in the scenario where (say) " +"several different libraries wanted to do different things. Each would " +"attempt to set its own :class:`Logger` subclass, and the one which did this " +"last would win." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1201 +msgid "" +"The second approach works reasonably well for many cases, but does not allow " +"you to e.g. use a specialized subclass of :class:`LogRecord`. Library " +"developers can set a suitable filter on their loggers, but they would have " +"to remember to do this every time they introduced a new logger (which they " +"would do simply by adding new packages or modules and doing ::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1209 +msgid "" +"at module level). It's probably one too many things to think about. " +"Developers could also add the filter to a :class:`~logging.NullHandler` " +"attached to their top-level logger, but this would not be invoked if an " +"application developer attached a handler to a lower-level library logger – " +"so output from that handler would not reflect the intentions of the library " +"developer." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1215 +msgid "" +"In Python 3.2 and later, :class:`~logging.LogRecord` creation is done " +"through a factory, which you can specify. The factory is just a callable you " +"can set with :func:`~logging.setLogRecordFactory`, and interrogate with :" +"func:`~logging.getLogRecordFactory`. The factory is invoked with the same " +"signature as the :class:`~logging.LogRecord` constructor, as :class:" +"`LogRecord` is the default setting for the factory." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1222 +msgid "" +"This approach allows a custom factory to control all aspects of LogRecord " +"creation. For example, you could return a subclass, or just add some " +"additional attributes to the record once created, using a pattern similar to " +"this::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1235 +msgid "" +"This pattern allows different libraries to chain factories together, and as " +"long as they don't overwrite each other's attributes or unintentionally " +"overwrite the attributes provided as standard, there should be no surprises. " +"However, it should be borne in mind that each link in the chain adds run-" +"time overhead to all logging operations, and the technique should only be " +"used when the use of a :class:`Filter` does not provide the desired result." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1246 +msgid "Subclassing QueueHandler - a ZeroMQ example" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1248 +msgid "" +"You can use a :class:`QueueHandler` subclass to send messages to other kinds " +"of queues, for example a ZeroMQ 'publish' socket. In the example below,the " +"socket is created separately and passed to the handler (as its 'queue')::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1267 +msgid "" +"Of course there are other ways of organizing this, for example passing in " +"the data needed by the handler to create the socket::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1286 +msgid "Subclassing QueueListener - a ZeroMQ example" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1288 +msgid "" +"You can also subclass :class:`QueueListener` to get messages from other " +"kinds of queues, for example a ZeroMQ 'subscribe' socket. Here's an example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1314 +msgid ":ref:`A basic logging tutorial `" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1316 +msgid ":ref:`A more advanced logging tutorial `" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1320 +msgid "An example dictionary-based configuration" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1322 +msgid "" +"Below is an example of a logging configuration dictionary - it's taken from " +"the `documentation on the Django project `_. This dictionary is passed to :" +"func:`~config.dictConfig` to put the configuration into effect::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1378 +msgid "" +"For more information about this configuration, you can see the `relevant " +"section `_ of the Django documentation." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1385 +msgid "Using a rotator and namer to customize log rotation processing" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1387 +msgid "" +"An example of how you can define a namer and rotator is given in the " +"following snippet, which shows zlib-based compression of the log file::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1405 +msgid "" +"These are not \"true\" .gz files, as they are bare compressed data, with no " +"\"container\" such as you’d find in an actual gzip file. This snippet is " +"just for illustration purposes." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1410 +msgid "A more elaborate multiprocessing example" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1412 +msgid "" +"The following working example shows how logging can be used with " +"multiprocessing using configuration files. The configurations are fairly " +"simple, but serve to illustrate how more complex ones could be implemented " +"in a real multiprocessing scenario." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1417 +msgid "" +"In the example, the main process spawns a listener process and some worker " +"processes. Each of the main process, the listener and the workers have three " +"separate configurations (the workers all share the same configuration). We " +"can see logging in the main process, how the workers log to a QueueHandler " +"and how the listener implements a QueueListener and a more complex logging " +"configuration, and arranges to dispatch events received via the queue to the " +"handlers specified in the configuration. Note that these configurations are " +"purely illustrative, but you should be able to adapt this example to your " +"own scenario." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1427 +msgid "" +"Here's the script - the docstrings and the comments hopefully explain how it " +"works::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1639 +msgid "Inserting a BOM into messages sent to a SysLogHandler" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1641 +msgid "" +"`RFC 5424 `_ requires that a Unicode " +"message be sent to a syslog daemon as a set of bytes which have the " +"following structure: an optional pure-ASCII component, followed by a UTF-8 " +"Byte Order Mark (BOM), followed by Unicode encoded using UTF-8. (See the " +"`relevant section of the specification `_.)" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1647 +msgid "" +"In Python 3.1, code was added to :class:`~logging.handlers.SysLogHandler` to " +"insert a BOM into the message, but unfortunately, it was implemented " +"incorrectly, with the BOM appearing at the beginning of the message and " +"hence not allowing any pure-ASCII component to appear before it." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1653 +msgid "" +"As this behaviour is broken, the incorrect BOM insertion code is being " +"removed from Python 3.2.4 and later. However, it is not being replaced, and " +"if you want to produce RFC 5424-compliant messages which include a BOM, an " +"optional pure-ASCII sequence before it and arbitrary Unicode after it, " +"encoded using UTF-8, then you need to do the following:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1659 +msgid "" +"Attach a :class:`~logging.Formatter` instance to your :class:`~logging." +"handlers.SysLogHandler` instance, with a format string such as::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1665 +msgid "" +"The Unicode code point U+FEFF, when encoded using UTF-8, will be encoded as " +"a UTF-8 BOM -- the byte-string ``b'\\xef\\xbb\\xbf'``." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1668 +msgid "" +"Replace the ASCII section with whatever placeholders you like, but make sure " +"that the data that appears in there after substitution is always ASCII (that " +"way, it will remain unchanged after UTF-8 encoding)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1672 +msgid "" +"Replace the Unicode section with whatever placeholders you like; if the data " +"which appears there after substitution contains characters outside the ASCII " +"range, that's fine -- it will be encoded using UTF-8." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1676 +msgid "" +"The formatted message *will* be encoded using UTF-8 encoding by " +"``SysLogHandler``. If you follow the above rules, you should be able to " +"produce RFC 5424-compliant messages. If you don't, logging may not complain, " +"but your messages will not be RFC 5424-compliant, and your syslog daemon may " +"complain." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1683 +msgid "Implementing structured logging" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1685 +msgid "" +"Although most logging messages are intended for reading by humans, and thus " +"not readily machine-parseable, there might be cirumstances where you want to " +"output messages in a structured format which *is* capable of being parsed by " +"a program (without needing complex regular expressions to parse the log " +"message). This is straightforward to achieve using the logging package. " +"There are a number of ways in which this could be achieved, but the " +"following is a simple approach which uses JSON to serialise the event in a " +"machine-parseable manner::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1709 +msgid "If the above script is run, it prints::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1713 +#: ../Doc/howto/logging-cookbook.rst:1760 +msgid "" +"Note that the order of items might be different according to the version of " +"Python used." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1716 +msgid "" +"If you need more specialised processing, you can use a custom JSON encoder, " +"as in the following complete example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1756 +msgid "When the above script is run, it prints::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1769 +msgid "Customizing handlers with :func:`dictConfig`" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1771 +msgid "" +"There are times when you want to customize logging handlers in particular " +"ways, and if you use :func:`dictConfig` you may be able to do this without " +"subclassing. As an example, consider that you may want to set the ownership " +"of a log file. On POSIX, this is easily done using :func:`shutil.chown`, but " +"the file handlers in the stdlib don't offer built-in support. You can " +"customize handler creation using a plain function such as::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1785 +msgid "" +"You can then specify, in a logging configuration passed to :func:" +"`dictConfig`, that a logging handler be created by calling this function::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1818 +msgid "" +"In this example I am setting the ownership using the ``pulse`` user and " +"group, just for the purposes of illustration. Putting it together into a " +"working script, ``chowntest.py``::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1865 +msgid "To run this, you will probably need to run as ``root``:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1875 +msgid "" +"Note that this example uses Python 3.3 because that's where :func:`shutil." +"chown` makes an appearance. This approach should work with any Python " +"version that supports :func:`dictConfig` - namely, Python 2.7, 3.2 or later. " +"With pre-3.3 versions, you would need to implement the actual ownership " +"change using e.g. :func:`os.chown`." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1881 +msgid "" +"In practice, the handler-creating function may be in a utility module " +"somewhere in your project. Instead of the line in the configuration::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1886 +msgid "you could use e.g.::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1890 +msgid "" +"where ``project.util`` can be replaced with the actual name of the package " +"where the function resides. In the above working script, using ``'ext://" +"__main__.owned_file_handler'`` should work. Here, the actual callable is " +"resolved by :func:`dictConfig` from the ``ext://`` specification." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1895 +msgid "" +"This example hopefully also points the way to how you could implement other " +"types of file change - e.g. setting specific POSIX permission bits - in the " +"same way, using :func:`os.chmod`." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1899 +msgid "" +"Of course, the approach could also be extended to types of handler other " +"than a :class:`~logging.FileHandler` - for example, one of the rotating file " +"handlers, or a different type of handler altogether." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1909 +msgid "Using particular formatting styles throughout your application" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1911 +msgid "" +"In Python 3.2, the :class:`~logging.Formatter` gained a ``style`` keyword " +"parameter which, while defaulting to ``%`` for backward compatibility, " +"allowed the specification of ``{`` or ``$`` to support the formatting " +"approaches supported by :meth:`str.format` and :class:`string.Template`. " +"Note that this governs the formatting of logging messages for final output " +"to logs, and is completely orthogonal to how an individual logging message " +"is constructed." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1918 +msgid "" +"Logging calls (:meth:`~Logger.debug`, :meth:`~Logger.info` etc.) only take " +"positional parameters for the actual logging message itself, with keyword " +"parameters used only for determining options for how to handle the logging " +"call (e.g. the ``exc_info`` keyword parameter to indicate that traceback " +"information should be logged, or the ``extra`` keyword parameter to indicate " +"additional contextual information to be added to the log). So you cannot " +"directly make logging calls using :meth:`str.format` or :class:`string." +"Template` syntax, because internally the logging package uses %-formatting " +"to merge the format string and the variable arguments. There would no " +"changing this while preserving backward compatibility, since all logging " +"calls which are out there in existing code will be using %-format strings." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1930 +msgid "" +"There have been suggestions to associate format styles with specific " +"loggers, but that approach also runs into backward compatibility problems " +"because any existing code could be using a given logger name and using %-" +"formatting." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1934 +msgid "" +"For logging to work interoperably between any third-party libraries and your " +"code, decisions about formatting need to be made at the level of the " +"individual logging call. This opens up a couple of ways in which alternative " +"formatting styles can be accommodated." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1941 +msgid "Using LogRecord factories" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1943 +msgid "" +"In Python 3.2, along with the :class:`~logging.Formatter` changes mentioned " +"above, the logging package gained the ability to allow users to set their " +"own :class:`LogRecord` subclasses, using the :func:`setLogRecordFactory` " +"function. You can use this to set your own subclass of :class:`LogRecord`, " +"which does the Right Thing by overriding the :meth:`~LogRecord.getMessage` " +"method. The base class implementation of this method is where the ``msg % " +"args`` formatting happens, and where you can substitute your alternate " +"formatting; however, you should be careful to support all formatting styles " +"and allow %-formatting as the default, to ensure interoperability with other " +"code. Care should also be taken to call ``str(self.msg)``, just as the base " +"implementation does." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1954 +msgid "" +"Refer to the reference documentation on :func:`setLogRecordFactory` and :" +"class:`LogRecord` for more information." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1959 +msgid "Using custom message objects" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1961 +msgid "" +"There is another, perhaps simpler way that you can use {}- and $- formatting " +"to construct your individual log messages. You may recall (from :ref:" +"`arbitrary-object-messages`) that when logging you can use an arbitrary " +"object as a message format string, and that the logging package will call :" +"func:`str` on that object to get the actual format string. Consider the " +"following two classes::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1986 +msgid "" +"Either of these can be used in place of a format string, to allow {}- or $-" +"formatting to be used to build the actual \"message\" part which appears in " +"the formatted log output in place of “%(message)s” or “{message}” or " +"“$message”. If you find it a little unwieldy to use the class names whenever " +"you want to log something, you can make it more palatable if you use an " +"alias such as ``M`` or ``_`` for the message (or perhaps ``__``, if you are " +"using ``_`` for localization)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:1994 +msgid "" +"Examples of this approach are given below. Firstly, formatting with :meth:" +"`str.format`::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2008 +msgid "Secondly, formatting with :class:`string.Template`::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2015 +msgid "" +"One thing to note is that you pay no significant performance penalty with " +"this approach: the actual formatting happens not when you make the logging " +"call, but when (and if) the logged message is actually about to be output to " +"a log by a handler. So the only slightly unusual thing which might trip you " +"up is that the parentheses go around the format string and the arguments, " +"not just the format string. That’s because the __ notation is just syntax " +"sugar for a constructor call to one of the ``XXXMessage`` classes shown " +"above." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2029 +msgid "Configuring filters with :func:`dictConfig`" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2031 +msgid "" +"You *can* configure filters using :func:`~logging.config.dictConfig`, though " +"it might not be obvious at first glance how to do it (hence this recipe). " +"Since :class:`~logging.Filter` is the only filter class included in the " +"standard library, and it is unlikely to cater to many requirements (it's " +"only there as a base class), you will typically need to define your own :" +"class:`~logging.Filter` subclass with an overridden :meth:`~logging.Filter." +"filter` method. To do this, specify the ``()`` key in the configuration " +"dictionary for the filter, specifying a callable which will be used to " +"create the filter (a class is the most obvious, but you can provide any " +"callable which returns a :class:`~logging.Filter` instance). Here is a " +"complete example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2084 +msgid "" +"This example shows how you can pass configuration data to the callable which " +"constructs the instance, in the form of keyword parameters. When run, the " +"above script will print::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2090 +msgid "which shows that the filter is working as configured." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2092 +msgid "A couple of extra points to note:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2094 +msgid "" +"If you can't refer to the callable directly in the configuration (e.g. if it " +"lives in a different module, and you can't import it directly where the " +"configuration dictionary is), you can use the form ``ext://...`` as " +"described in :ref:`logging-config-dict-externalobj`. For example, you could " +"have used the text ``'ext://__main__.MyFilter'`` instead of ``MyFilter`` in " +"the above example." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2101 +msgid "" +"As well as for filters, this technique can also be used to configure custom " +"handlers and formatters. See :ref:`logging-config-dict-userdef` for more " +"information on how logging supports using user-defined objects in its " +"configuration, and see the other cookbook recipe :ref:`custom-handlers` " +"above." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2110 +msgid "Customized exception formatting" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2112 +msgid "" +"There might be times when you want to do customized exception formatting - " +"for argument's sake, let's say you want exactly one line per logged event, " +"even when exception information is present. You can do this with a custom " +"formatter class, as shown in the following example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2153 +msgid "When run, this produces a file with exactly two lines::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2158 +msgid "" +"While the above treatment is simplistic, it points the way to how exception " +"information can be formatted to your liking. The :mod:`traceback` module may " +"be helpful for more specialized needs." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2165 +msgid "Speaking logging messages" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2167 +msgid "" +"There might be situations when it is desirable to have logging messages " +"rendered in an audible rather than a visible format. This is easy to do if " +"you have text- to-speech (TTS) functionality available in your system, even " +"if it doesn't have a Python binding. Most TTS systems have a command line " +"program you can run, and this can be invoked from a handler using :mod:" +"`subprocess`. It's assumed here that TTS command line programs won't expect " +"to interact with users or take a long time to complete, and that the " +"frequency of logged messages will be not so high as to swamp the user with " +"messages, and that it's acceptable to have the messages spoken one at a time " +"rather than concurrently, The example implementation below waits for one " +"message to be spoken before the next is processed, and this might cause " +"other handlers to be kept waiting. Here is a short example showing the " +"approach, which assumes that the ``espeak`` TTS package is available::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2209 +msgid "" +"When run, this script should say \"Hello\" and then \"Goodbye\" in a female " +"voice." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2211 +msgid "" +"The above approach can, of course, be adapted to other TTS systems and even " +"other systems altogether which can process messages via external programs " +"run from a command line." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2219 +msgid "Buffering logging messages and outputting them conditionally" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2221 +msgid "" +"There might be situations where you want to log messages in a temporary area " +"and only output them if a certain condition occurs. For example, you may " +"want to start logging debug events in a function, and if the function " +"completes without errors, you don't want to clutter the log with the " +"collected debug information, but if there is an error, you want all the " +"debug information to be output as well as the error." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2228 +msgid "" +"Here is an example which shows how you could do this using a decorator for " +"your functions where you want logging to behave this way. It makes use of " +"the :class:`logging.handlers.MemoryHandler`, which allows buffering of " +"logged events until some condition occurs, at which point the buffered " +"events are ``flushed`` - passed to another handler (the ``target`` handler) " +"for processing. By default, the ``MemoryHandler`` flushed when its buffer " +"gets filled up or an event whose level is greater than or equal to a " +"specified threshold is seen. You can use this recipe with a more specialised " +"subclass of ``MemoryHandler`` if you want custom flushing behavior." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2238 +msgid "" +"The example script has a simple function, ``foo``, which just cycles through " +"all the logging levels, writing to ``sys.stderr`` to say what level it's " +"about to log at, and then actually logging a message at that level. You can " +"pass a parameter to ``foo`` which, if true, will log at ERROR and CRITICAL " +"levels - otherwise, it only logs at DEBUG, INFO and WARNING levels." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2244 +msgid "" +"The script just arranges to decorate ``foo`` with a decorator which will do " +"the conditional logging that's required. The decorator takes a logger as a " +"parameter and attaches a memory handler for the duration of the call to the " +"decorated function. The decorator can be additionally parameterised using a " +"target handler, a level at which flushing should occur, and a capacity for " +"the buffer. These default to a :class:`~logging.StreamHandler` which writes " +"to ``sys.stderr``, ``logging.ERROR`` and ``100`` respectively." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2252 +msgid "Here's the script::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2315 +msgid "When this script is run, the following output should be observed::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2343 +msgid "" +"As you can see, actual logging output only occurs when an event is logged " +"whose severity is ERROR or greater, but in that case, any previous events at " +"lower severities are also logged." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2347 +msgid "You can of course use the conventional means of decoration::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2357 +msgid "Formatting times using UTC (GMT) via configuration" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2359 +msgid "" +"Sometimes you want to format times using UTC, which can be done using a " +"class such as `UTCFormatter`, shown below::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2368 +msgid "" +"and you can then use the ``UTCFormatter`` in your code instead of :class:" +"`~logging.Formatter`. If you want to do that via configuration, you can use " +"the :func:`~logging.config.dictConfig` API with an approach illustrated by " +"the following complete example::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2411 +msgid "When this script is run, it should print something like::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2416 +msgid "" +"showing how the time is formatted both as local time and UTC, one for each " +"handler." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2423 +msgid "Using a context manager for selective logging" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2425 +msgid "" +"There are times when it would be useful to temporarily change the logging " +"configuration and revert it back after doing something. For this, a context " +"manager is the most obvious way of saving and restoring the logging context. " +"Here is a simple example of such a context manager, which allows you to " +"optionally change the logging level and add a logging handler purely in the " +"scope of the context manager::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2458 +msgid "" +"If you specify a level value, the logger's level is set to that value in the " +"scope of the with block covered by the context manager. If you specify a " +"handler, it is added to the logger on entry to the block and removed on exit " +"from the block. You can also ask the manager to close the handler for you on " +"block exit - you could do this if you don't need the handler any more." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2464 +msgid "" +"To illustrate how it works, we can add the following block of code to the " +"above::" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2482 +msgid "" +"We initially set the logger's level to ``INFO``, so message #1 appears and " +"message #2 doesn't. We then change the level to ``DEBUG`` temporarily in the " +"following ``with`` block, and so message #3 appears. After the block exits, " +"the logger's level is restored to ``INFO`` and so message #4 doesn't appear. " +"In the next ``with`` block, we set the level to ``DEBUG`` again but also add " +"a handler writing to ``sys.stdout``. Thus, message #5 appears twice on the " +"console (once via ``stderr`` and once via ``stdout``). After the ``with`` " +"statement's completion, the status is as it was before so message #6 appears " +"(like message #1) whereas message #7 doesn't (just like message #2)." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2492 +msgid "If we run the resulting script, the result is as follows:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2503 +msgid "" +"If we run it again, but pipe ``stderr`` to ``/dev/null``, we see the " +"following, which is the only message written to ``stdout``:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2511 +msgid "Once again, but piping ``stdout`` to ``/dev/null``, we get:" +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2521 +msgid "" +"In this case, the message #5 printed to ``stdout`` doesn't appear, as " +"expected." +msgstr "" + +#: ../Doc/howto/logging-cookbook.rst:2523 +msgid "" +"Of course, the approach described here can be generalised, for example to " +"attach logging filters temporarily. Note that the above code works in Python " +"2 as well as Python 3." +msgstr "" + +#: ../Doc/howto/pyporting.rst:5 +msgid "Porting Python 2 Code to Python 3" +msgstr "" + +#: ../Doc/howto/pyporting.rst:7 +msgid "Brett Cannon" +msgstr "" + +#: ../Doc/howto/pyporting.rst:11 +msgid "" +"With Python 3 being the future of Python while Python 2 is still in active " +"use, it is good to have your project available for both major releases of " +"Python. This guide is meant to help you figure out how best to support both " +"Python 2 & 3 simultaneously." +msgstr "" + +#: ../Doc/howto/pyporting.rst:16 +msgid "" +"If you are looking to port an extension module instead of pure Python code, " +"please see :ref:`cporting-howto`." +msgstr "" + +#: ../Doc/howto/pyporting.rst:19 +msgid "" +"If you would like to read one core Python developer's take on why Python 3 " +"came into existence, you can read Nick Coghlan's `Python 3 Q & A`_." +msgstr "" + +#: ../Doc/howto/pyporting.rst:22 +msgid "" +"For help with porting, you can email the python-porting_ mailing list with " +"questions." +msgstr "" + +#: ../Doc/howto/pyporting.rst:26 +msgid "The Short Explanation" +msgstr "" + +#: ../Doc/howto/pyporting.rst:28 +msgid "" +"To make your project be single-source Python 2/3 compatible, the basic steps " +"are:" +msgstr "" + +#: ../Doc/howto/pyporting.rst:31 +msgid "Only worry about supporting Python 2.7" +msgstr "" + +#: ../Doc/howto/pyporting.rst:32 +msgid "" +"Make sure you have good test coverage (coverage.py_ can help; ``pip install " +"coverage``)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:34 ../Doc/howto/pyporting.rst:114 +#: ../Doc/howto/pyporting.rst:415 +msgid "Learn the differences between Python 2 & 3" +msgstr "" + +#: ../Doc/howto/pyporting.rst:35 +msgid "" +"Use Modernize_ or Futurize_ to update your code (``pip install modernize`` " +"or ``pip install future``, respectively)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:37 +msgid "" +"Use Pylint_ to help make sure you don't regress on your Python 3 support " +"(``pip install pylint``)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:39 +msgid "" +"Use caniusepython3_ to find out which of your dependencies are blocking your " +"use of Python 3 (``pip install caniusepython3``)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:41 +msgid "" +"Once your dependencies are no longer blocking you, use continuous " +"integration to make sure you stay compatible with Python 2 & 3 (tox_ can " +"help test against multiple versions of Python; ``pip install tox``)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:45 +msgid "" +"If you are dropping support for Python 2 entirely, then after you learn the " +"differences between Python 2 & 3 you can run 2to3_ over your code and skip " +"the rest of the steps outlined above." +msgstr "" + +#: ../Doc/howto/pyporting.rst:51 +msgid "Details" +msgstr "" + +#: ../Doc/howto/pyporting.rst:53 +msgid "" +"A key point about supporting Python 2 & 3 simultaneously is that you can " +"start **today**! Even if your dependencies are not supporting Python 3 yet " +"that does not mean you can't modernize your code **now** to support Python " +"3. Most changes required to support Python 3 lead to cleaner code using " +"newer practices even in Python 2." +msgstr "" + +#: ../Doc/howto/pyporting.rst:59 +msgid "" +"Another key point is that modernizing your Python 2 code to also support " +"Python 3 is largely automated for you. While you might have to make some API " +"decisions thanks to Python 3 clarifying text data versus binary data, the " +"lower-level work is now mostly done for you and thus can at least benefit " +"from the automated changes immediately." +msgstr "" + +#: ../Doc/howto/pyporting.rst:65 +msgid "" +"Keep those key points in mind while you read on about the details of porting " +"your code to support Python 2 & 3 simultaneously." +msgstr "" + +#: ../Doc/howto/pyporting.rst:70 +msgid "Drop support for Python 2.6 and older" +msgstr "" + +#: ../Doc/howto/pyporting.rst:72 +msgid "" +"While you can make Python 2.5 work with Python 3, it is **much** easier if " +"you only have to work with Python 2.7. If dropping Python 2.5 is not an " +"option then the six_ project can help you support Python 2.5 & 3 " +"simultaneously (``pip install six``). Do realize, though, that nearly all " +"the projects listed in this HOWTO will not be available to you." +msgstr "" + +#: ../Doc/howto/pyporting.rst:78 +msgid "" +"If you are able to skip Python 2.5 and older, then the required changes to " +"your code should continue to look and feel like idiomatic Python code. At " +"worst you will have to use a function instead of a method in some instances " +"or have to import a function instead of using a built-in one, but otherwise " +"the overall transformation should not feel foreign to you." +msgstr "" + +#: ../Doc/howto/pyporting.rst:84 +msgid "" +"But you should aim for only supporting Python 2.7. Python 2.6 is no longer " +"supported and thus is not receiving bugfixes. This means **you** will have " +"to work around any issues you come across with Python 2.6. There are also " +"some tools mentioned in this HOWTO which do not support Python 2.6 (e.g., " +"Pylint_), and this will become more commonplace as time goes on. It will " +"simply be easier for you if you only support the versions of Python that you " +"have to support." +msgstr "" + +#: ../Doc/howto/pyporting.rst:92 +msgid "" +"Make sure you specify the proper version support in your ``setup.py`` file" +msgstr "" + +#: ../Doc/howto/pyporting.rst:94 +msgid "" +"In your ``setup.py`` file you should have the proper `trove classifier`_ " +"specifying what versions of Python you support. As your project does not " +"support Python 3 yet you should at least have ``Programming Language :: " +"Python :: 2 :: Only`` specified. Ideally you should also specify each major/" +"minor version of Python that you do support, e.g. ``Programming Language :: " +"Python :: 2.7``." +msgstr "" + +#: ../Doc/howto/pyporting.rst:102 +msgid "Have good test coverage" +msgstr "" + +#: ../Doc/howto/pyporting.rst:104 +msgid "" +"Once you have your code supporting the oldest version of Python 2 you want " +"it to, you will want to make sure your test suite has good coverage. A good " +"rule of thumb is that if you want to be confident enough in your test suite " +"that any failures that appear after having tools rewrite your code are " +"actual bugs in the tools and not in your code. If you want a number to aim " +"for, try to get over 80% coverage (and don't feel bad if you can't easily " +"get past 90%). If you don't already have a tool to measure test coverage " +"then coverage.py_ is recommended." +msgstr "" + +#: ../Doc/howto/pyporting.rst:116 +msgid "" +"Once you have your code well-tested you are ready to begin porting your code " +"to Python 3! But to fully understand how your code is going to change and " +"what you want to look out for while you code, you will want to learn what " +"changes Python 3 makes in terms of Python 2. Typically the two best ways of " +"doing that is reading the `\"What's New\"`_ doc for each release of Python 3 " +"and the `Porting to Python 3`_ book (which is free online). There is also a " +"handy `cheat sheet`_ from the Python-Future project." +msgstr "" + +#: ../Doc/howto/pyporting.rst:126 +msgid "Update your code" +msgstr "" + +#: ../Doc/howto/pyporting.rst:128 +msgid "" +"Once you feel like you know what is different in Python 3 compared to Python " +"2, it's time to update your code! You have a choice between two tools in " +"porting your code automatically: Modernize_ and Futurize_. Which tool you " +"choose will depend on how much like Python 3 you want your code to be. " +"Futurize_ does its best to make Python 3 idioms and practices exist in " +"Python 2, e.g. backporting the ``bytes`` type from Python 3 so that you have " +"semantic parity between the major versions of Python. Modernize_, on the " +"other hand, is more conservative and targets a Python 2/3 subset of Python, " +"relying on six_ to help provide compatibility." +msgstr "" + +#: ../Doc/howto/pyporting.rst:138 +msgid "" +"Regardless of which tool you choose, they will update your code to run under " +"Python 3 while staying compatible with the version of Python 2 you started " +"with. Depending on how conservative you want to be, you may want to run the " +"tool over your test suite first and visually inspect the diff to make sure " +"the transformation is accurate. After you have transformed your test suite " +"and verified that all the tests still pass as expected, then you can " +"transform your application code knowing that any tests which fail is a " +"translation failure." +msgstr "" + +#: ../Doc/howto/pyporting.rst:146 +msgid "" +"Unfortunately the tools can't automate everything to make your code work " +"under Python 3 and so there are a handful of things you will need to update " +"manually to get full Python 3 support (which of these steps are necessary " +"vary between the tools). Read the documentation for the tool you choose to " +"use to see what it fixes by default and what it can do optionally to know " +"what will (not) be fixed for you and what you may have to fix on your own (e." +"g. using ``io.open()`` over the built-in ``open()`` function is off by " +"default in Modernize). Luckily, though, there are only a couple of things to " +"watch out for which can be considered large issues that may be hard to debug " +"if not watched for." +msgstr "" + +#: ../Doc/howto/pyporting.rst:157 +msgid "Division" +msgstr "" + +#: ../Doc/howto/pyporting.rst:159 +msgid "" +"In Python 3, ``5 / 2 == 2.5`` and not ``2``; all division between ``int`` " +"values result in a ``float``. This change has actually been planned since " +"Python 2.2 which was released in 2002. Since then users have been encouraged " +"to add ``from __future__ import division`` to any and all files which use " +"the ``/`` and ``//`` operators or to be running the interpreter with the ``-" +"Q`` flag. If you have not been doing this then you will need to go through " +"your code and do two things:" +msgstr "" + +#: ../Doc/howto/pyporting.rst:167 +msgid "Add ``from __future__ import division`` to your files" +msgstr "" + +#: ../Doc/howto/pyporting.rst:168 +msgid "" +"Update any division operator as necessary to either use ``//`` to use floor " +"division or continue using ``/`` and expect a float" +msgstr "" + +#: ../Doc/howto/pyporting.rst:171 +msgid "" +"The reason that ``/`` isn't simply translated to ``//`` automatically is " +"that if an object defines a ``__truediv__`` method but not ``__floordiv__`` " +"then your code would begin to fail (e.g. a user-defined class that uses ``/" +"`` to signify some operation but not ``//`` for the same thing or at all)." +msgstr "" + +#: ../Doc/howto/pyporting.rst:177 +msgid "Text versus binary data" +msgstr "" + +#: ../Doc/howto/pyporting.rst:179 +msgid "" +"In Python 2 you could use the ``str`` type for both text and binary data. " +"Unfortunately this confluence of two different concepts could lead to " +"brittle code which sometimes worked for either kind of data, sometimes not. " +"It also could lead to confusing APIs if people didn't explicitly state that " +"something that accepted ``str`` accepted either text or binary data instead " +"of one specific type. This complicated the situation especially for anyone " +"supporting multiple languages as APIs wouldn't bother explicitly supporting " +"``unicode`` when they claimed text data support." +msgstr "" + +#: ../Doc/howto/pyporting.rst:188 +msgid "" +"To make the distinction between text and binary data clearer and more " +"pronounced, Python 3 did what most languages created in the age of the " +"internet have done and made text and binary data distinct types that cannot " +"blindly be mixed together (Python predates widespread access to the " +"internet). For any code that only deals with text or only binary data, this " +"separation doesn't pose an issue. But for code that has to deal with both, " +"it does mean you might have to now care about when you are using text " +"compared to binary data, which is why this cannot be entirely automated." +msgstr "" + +#: ../Doc/howto/pyporting.rst:197 +msgid "" +"To start, you will need to decide which APIs take text and which take binary " +"(it is **highly** recommended you don't design APIs that can take both due " +"to the difficulty of keeping the code working; as stated earlier it is " +"difficult to do well). In Python 2 this means making sure the APIs that take " +"text can work with ``unicode`` in Python 2 and those that work with binary " +"data work with the ``bytes`` type from Python 3 and thus a subset of ``str`` " +"in Python 2 (which the ``bytes`` type in Python 2 is an alias for). Usually " +"the biggest issue is realizing which methods exist for which types in Python " +"2 & 3 simultaneously (for text that's ``unicode`` in Python 2 and ``str`` in " +"Python 3, for binary that's ``str``/``bytes`` in Python 2 and ``bytes`` in " +"Python 3). The following table lists the **unique** methods of each data " +"type across Python 2 & 3 (e.g., the ``decode()`` method is usable on the " +"equivalent binary data type in either Python 2 or 3, but it can't be used by " +"the text data type consistently between Python 2 and 3 because ``str`` in " +"Python 3 doesn't have the method). Do note that as of Python 3.5 the " +"``__mod__`` method was added to the bytes type." +msgstr "" + +#: ../Doc/howto/pyporting.rst:214 +msgid "**Text data**" +msgstr "" + +#: ../Doc/howto/pyporting.rst:214 +msgid "**Binary data**" +msgstr "" + +#: ../Doc/howto/pyporting.rst:216 +msgid "\\" +msgstr "" + +#: ../Doc/howto/pyporting.rst:216 +msgid "decode" +msgstr "" + +#: ../Doc/howto/pyporting.rst:218 +msgid "encode" +msgstr "" + +#: ../Doc/howto/pyporting.rst:220 +msgid "format" +msgstr "" + +#: ../Doc/howto/pyporting.rst:222 +msgid "isdecimal" +msgstr "" + +#: ../Doc/howto/pyporting.rst:224 +msgid "isnumeric" +msgstr "" + +#: ../Doc/howto/pyporting.rst:227 +msgid "" +"Making the distinction easier to handle can be accomplished by encoding and " +"decoding between binary data and text at the edge of your code. This means " +"that when you receive text in binary data, you should immediately decode it. " +"And if your code needs to send text as binary data then encode it as late as " +"possible. This allows your code to work with only text internally and thus " +"eliminates having to keep track of what type of data you are working with." +msgstr "" + +#: ../Doc/howto/pyporting.rst:234 +msgid "" +"The next issue is making sure you know whether the string literals in your " +"code represent text or binary data. At minimum you should add a ``b`` prefix " +"to any literal that presents binary data. For text you should either use the " +"``from __future__ import unicode_literals`` statement or add a ``u`` prefix " +"to the text literal." +msgstr "" + +#: ../Doc/howto/pyporting.rst:240 +msgid "" +"As part of this dichotomy you also need to be careful about opening files. " +"Unless you have been working on Windows, there is a chance you have not " +"always bothered to add the ``b`` mode when opening a binary file (e.g., " +"``rb`` for binary reading). Under Python 3, binary files and text files are " +"clearly distinct and mutually incompatible; see the :mod:`io` module for " +"details. Therefore, you **must** make a decision of whether a file will be " +"used for binary access (allowing binary data to be read and/or written) or " +"text access (allowing text data to be read and/or written). You should also " +"use :func:`io.open` for opening files instead of the built-in :func:`open` " +"function as the :mod:`io` module is consistent from Python 2 to 3 while the " +"built-in :func:`open` function is not (in Python 3 it's actually :func:`io." +"open`)." +msgstr "" + +#: ../Doc/howto/pyporting.rst:252 +msgid "" +"The constructors of both ``str`` and ``bytes`` have different semantics for " +"the same arguments between Python 2 & 3. Passing an integer to ``bytes`` in " +"Python 2 will give you the string representation of the integer: ``bytes(3) " +"== '3'``. But in Python 3, an integer argument to ``bytes`` will give you a " +"bytes object as long as the integer specified, filled with null bytes: " +"``bytes(3) == b'\\x00\\x00\\x00'``. A similar worry is necessary when " +"passing a bytes object to ``str``. In Python 2 you just get the bytes object " +"back: ``str(b'3') == b'3'``. But in Python 3 you get the string " +"representation of the bytes object: ``str(b'3') == \"b'3'\"``." +msgstr "" + +#: ../Doc/howto/pyporting.rst:262 +msgid "" +"Finally, the indexing of binary data requires careful handling (slicing does " +"**not** require any special handling). In Python 2, ``b'123'[1] == b'2'`` " +"while in Python 3 ``b'123'[1] == 50``. Because binary data is simply a " +"collection of binary numbers, Python 3 returns the integer value for the " +"byte you index on. But in Python 2 because ``bytes == str``, indexing " +"returns a one-item slice of bytes. The six_ project has a function named " +"``six.indexbytes()`` which will return an integer like in Python 3: ``six." +"indexbytes(b'123', 1)``." +msgstr "" + +#: ../Doc/howto/pyporting.rst:271 +msgid "To summarize:" +msgstr "" + +#: ../Doc/howto/pyporting.rst:273 +msgid "Decide which of your APIs take text and which take binary data" +msgstr "" + +#: ../Doc/howto/pyporting.rst:274 +msgid "" +"Make sure that your code that works with text also works with ``unicode`` " +"and code for binary data works with ``bytes`` in Python 2 (see the table " +"above for what methods you cannot use for each type)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:277 +msgid "" +"Mark all binary literals with a ``b`` prefix, use a ``u`` prefix or :mod:" +"`__future__` import statement for text literals" +msgstr "" + +#: ../Doc/howto/pyporting.rst:279 +msgid "" +"Decode binary data to text as soon as possible, encode text as binary data " +"as late as possible" +msgstr "" + +#: ../Doc/howto/pyporting.rst:281 +msgid "" +"Open files using :func:`io.open` and make sure to specify the ``b`` mode " +"when appropriate" +msgstr "" + +#: ../Doc/howto/pyporting.rst:283 +msgid "Be careful when indexing binary data" +msgstr "" + +#: ../Doc/howto/pyporting.rst:287 +msgid "Use feature detection instead of version detection" +msgstr "" + +#: ../Doc/howto/pyporting.rst:288 +msgid "" +"Inevitably you will have code that has to choose what to do based on what " +"version of Python is running. The best way to do this is with feature " +"detection of whether the version of Python you're running under supports " +"what you need. If for some reason that doesn't work then you should make the " +"version check is against Python 2 and not Python 3. To help explain this, " +"let's look at an example." +msgstr "" + +#: ../Doc/howto/pyporting.rst:295 +msgid "" +"Let's pretend that you need access to a feature of importlib_ that is " +"available in Python's standard library since Python 3.3 and available for " +"Python 2 through importlib2_ on PyPI. You might be tempted to write code to " +"access e.g. the ``importlib.abc`` module by doing the following::" +msgstr "" + +#: ../Doc/howto/pyporting.rst:307 +msgid "" +"The problem with this code is what happens when Python 4 comes out? It would " +"be better to treat Python 2 as the exceptional case instead of Python 3 and " +"assume that future Python versions will be more compatible with Python 3 " +"than Python 2::" +msgstr "" + +#: ../Doc/howto/pyporting.rst:319 +msgid "" +"The best solution, though, is to do no version detection at all and instead " +"rely on feature detection. That avoids any potential issues of getting the " +"version detection wrong and helps keep you future-compatible::" +msgstr "" + +#: ../Doc/howto/pyporting.rst:330 +msgid "Prevent compatibility regressions" +msgstr "" + +#: ../Doc/howto/pyporting.rst:332 +msgid "" +"Once you have fully translated your code to be compatible with Python 3, you " +"will want to make sure your code doesn't regress and stop working under " +"Python 3. This is especially true if you have a dependency which is blocking " +"you from actually running under Python 3 at the moment." +msgstr "" + +#: ../Doc/howto/pyporting.rst:337 +msgid "" +"To help with staying compatible, any new modules you create should have at " +"least the following block of code at the top of it::" +msgstr "" + +#: ../Doc/howto/pyporting.rst:345 +msgid "" +"You can also run Python 2 with the ``-3`` flag to be warned about various " +"compatibility issues your code triggers during execution. If you turn " +"warnings into errors with ``-Werror`` then you can make sure that you don't " +"accidentally miss a warning." +msgstr "" + +#: ../Doc/howto/pyporting.rst:351 +msgid "" +"You can also use the Pylint_ project and its ``--py3k`` flag to lint your " +"code to receive warnings when your code begins to deviate from Python 3 " +"compatibility. This also prevents you from having to run Modernize_ or " +"Futurize_ over your code regularly to catch compatibility regressions. This " +"does require you only support Python 2.7 and Python 3.4 or newer as that is " +"Pylint's minimum Python version support." +msgstr "" + +#: ../Doc/howto/pyporting.rst:360 +msgid "Check which dependencies block your transition" +msgstr "" + +#: ../Doc/howto/pyporting.rst:362 +msgid "" +"**After** you have made your code compatible with Python 3 you should begin " +"to care about whether your dependencies have also been ported. The " +"caniusepython3_ project was created to help you determine which projects -- " +"directly or indirectly -- are blocking you from supporting Python 3. There " +"is both a command-line tool as well as a web interface at https://" +"caniusepython3.com ." +msgstr "" + +#: ../Doc/howto/pyporting.rst:369 +msgid "" +"The project also provides code which you can integrate into your test suite " +"so that you will have a failing test when you no longer have dependencies " +"blocking you from using Python 3. This allows you to avoid having to " +"manually check your dependencies and to be notified quickly when you can " +"start running on Python 3." +msgstr "" + +#: ../Doc/howto/pyporting.rst:375 +msgid "Update your ``setup.py`` file to denote Python 3 compatibility" +msgstr "" + +#: ../Doc/howto/pyporting.rst:377 +msgid "" +"Once your code works under Python 3, you should update the classifiers in " +"your ``setup.py`` to contain ``Programming Language :: Python :: 3`` and to " +"not specify sole Python 2 support. This will tell anyone using your code " +"that you support Python 2 **and** 3. Ideally you will also want to add " +"classifiers for each major/minor version of Python you now support." +msgstr "" + +#: ../Doc/howto/pyporting.rst:385 +msgid "Use continuous integration to stay compatible" +msgstr "" + +#: ../Doc/howto/pyporting.rst:387 +msgid "" +"Once you are able to fully run under Python 3 you will want to make sure " +"your code always works under both Python 2 & 3. Probably the best tool for " +"running your tests under multiple Python interpreters is tox_. You can then " +"integrate tox with your continuous integration system so that you never " +"accidentally break Python 2 or 3 support." +msgstr "" + +#: ../Doc/howto/pyporting.rst:393 +msgid "" +"You may also want to use the ``-bb`` flag with the Python 3 interpreter to " +"trigger an exception when you are comparing bytes to strings or bytes to an " +"int (the latter is available starting in Python 3.5). By default type-" +"differing comparisons simply return ``False``, but if you made a mistake in " +"your separation of text/binary data handling or indexing on bytes you " +"wouldn't easily find the mistake. This flag will raise an exception when " +"these kinds of comparisons occur, making the mistake much easier to track " +"down." +msgstr "" + +#: ../Doc/howto/pyporting.rst:401 +msgid "" +"And that's mostly it! At this point your code base is compatible with both " +"Python 2 and 3 simultaneously. Your testing will also be set up so that you " +"don't accidentally break Python 2 or 3 compatibility regardless of which " +"version you typically run your tests under while developing." +msgstr "" + +#: ../Doc/howto/pyporting.rst:408 +msgid "Dropping Python 2 support completely" +msgstr "" + +#: ../Doc/howto/pyporting.rst:410 +msgid "" +"If you are able to fully drop support for Python 2, then the steps required " +"to transition to Python 3 simplify greatly." +msgstr "" + +#: ../Doc/howto/pyporting.rst:413 +msgid "Update your code to only support Python 2.7" +msgstr "" + +#: ../Doc/howto/pyporting.rst:414 +msgid "Make sure you have good test coverage (coverage.py_ can help)" +msgstr "" + +#: ../Doc/howto/pyporting.rst:416 +msgid "Use 2to3_ to rewrite your code to run only under Python 3" +msgstr "" + +#: ../Doc/howto/pyporting.rst:418 +msgid "" +"After this your code will be fully Python 3 compliant but in a way that is " +"not supported by Python 2. You should also update the classifiers in your " +"``setup.py`` to contain ``Programming Language :: Python :: 3 :: Only``." +msgstr "" + +#: ../Doc/howto/regex.rst:5 +msgid "Regular Expression HOWTO" +msgstr "" + +#: ../Doc/howto/regex.rst:7 +msgid "A.M. Kuchling " +msgstr "" + +#: ../Doc/howto/regex.rst:18 +msgid "" +"This document is an introductory tutorial to using regular expressions in " +"Python with the :mod:`re` module. It provides a gentler introduction than " +"the corresponding section in the Library Reference." +msgstr "" + +#: ../Doc/howto/regex.rst:26 +msgid "" +"Regular expressions (called REs, or regexes, or regex patterns) are " +"essentially a tiny, highly specialized programming language embedded inside " +"Python and made available through the :mod:`re` module. Using this little " +"language, you specify the rules for the set of possible strings that you " +"want to match; this set might contain English sentences, or e-mail " +"addresses, or TeX commands, or anything you like. You can then ask " +"questions such as \"Does this string match the pattern?\", or \"Is there a " +"match for the pattern anywhere in this string?\". You can also use REs to " +"modify a string or to split it apart in various ways." +msgstr "" + +#: ../Doc/howto/regex.rst:35 +msgid "" +"Regular expression patterns are compiled into a series of bytecodes which " +"are then executed by a matching engine written in C. For advanced use, it " +"may be necessary to pay careful attention to how the engine will execute a " +"given RE, and write the RE in a certain way in order to produce bytecode " +"that runs faster. Optimization isn't covered in this document, because it " +"requires that you have a good understanding of the matching engine's " +"internals." +msgstr "" + +#: ../Doc/howto/regex.rst:42 +msgid "" +"The regular expression language is relatively small and restricted, so not " +"all possible string processing tasks can be done using regular expressions. " +"There are also tasks that *can* be done with regular expressions, but the " +"expressions turn out to be very complicated. In these cases, you may be " +"better off writing Python code to do the processing; while Python code will " +"be slower than an elaborate regular expression, it will also probably be " +"more understandable." +msgstr "" + +#: ../Doc/howto/regex.rst:51 +msgid "Simple Patterns" +msgstr "" + +#: ../Doc/howto/regex.rst:53 +msgid "" +"We'll start by learning about the simplest possible regular expressions. " +"Since regular expressions are used to operate on strings, we'll begin with " +"the most common task: matching characters." +msgstr "" + +#: ../Doc/howto/regex.rst:57 +msgid "" +"For a detailed explanation of the computer science underlying regular " +"expressions (deterministic and non-deterministic finite automata), you can " +"refer to almost any textbook on writing compilers." +msgstr "" + +#: ../Doc/howto/regex.rst:63 +msgid "Matching Characters" +msgstr "" + +#: ../Doc/howto/regex.rst:65 +msgid "" +"Most letters and characters will simply match themselves. For example, the " +"regular expression ``test`` will match the string ``test`` exactly. (You " +"can enable a case-insensitive mode that would let this RE match ``Test`` or " +"``TEST`` as well; more about this later.)" +msgstr "" + +#: ../Doc/howto/regex.rst:70 +msgid "" +"There are exceptions to this rule; some characters are special :dfn:" +"`metacharacters`, and don't match themselves. Instead, they signal that " +"some out-of-the-ordinary thing should be matched, or they affect other " +"portions of the RE by repeating them or changing their meaning. Much of " +"this document is devoted to discussing various metacharacters and what they " +"do." +msgstr "" + +#: ../Doc/howto/regex.rst:76 +msgid "" +"Here's a complete list of the metacharacters; their meanings will be " +"discussed in the rest of this HOWTO." +msgstr "" + +#: ../Doc/howto/regex.rst:83 +msgid "" +"The first metacharacters we'll look at are ``[`` and ``]``. They're used for " +"specifying a character class, which is a set of characters that you wish to " +"match. Characters can be listed individually, or a range of characters can " +"be indicated by giving two characters and separating them by a ``'-'``. For " +"example, ``[abc]`` will match any of the characters ``a``, ``b``, or ``c``; " +"this is the same as ``[a-c]``, which uses a range to express the same set of " +"characters. If you wanted to match only lowercase letters, your RE would be " +"``[a-z]``." +msgstr "" + +#: ../Doc/howto/regex.rst:92 +msgid "" +"Metacharacters are not active inside classes. For example, ``[akm$]`` will " +"match any of the characters ``'a'``, ``'k'``, ``'m'``, or ``'$'``; ``'$'`` " +"is usually a metacharacter, but inside a character class it's stripped of " +"its special nature." +msgstr "" + +#: ../Doc/howto/regex.rst:97 +msgid "" +"You can match the characters not listed within the class by :dfn:" +"`complementing` the set. This is indicated by including a ``'^'`` as the " +"first character of the class; ``'^'`` outside a character class will simply " +"match the ``'^'`` character. For example, ``[^5]`` will match any character " +"except ``'5'``." +msgstr "" + +#: ../Doc/howto/regex.rst:102 +msgid "" +"Perhaps the most important metacharacter is the backslash, ``\\``. As in " +"Python string literals, the backslash can be followed by various characters " +"to signal various special sequences. It's also used to escape all the " +"metacharacters so you can still match them in patterns; for example, if you " +"need to match a ``[`` or ``\\``, you can precede them with a backslash to " +"remove their special meaning: ``\\[`` or ``\\\\``." +msgstr "" + +#: ../Doc/howto/regex.rst:109 +msgid "" +"Some of the special sequences beginning with ``'\\'`` represent predefined " +"sets of characters that are often useful, such as the set of digits, the set " +"of letters, or the set of anything that isn't whitespace." +msgstr "" + +#: ../Doc/howto/regex.rst:114 +msgid "" +"Let's take an example: ``\\w`` matches any alphanumeric character. If the " +"regex pattern is expressed in bytes, this is equivalent to the class ``[a-zA-" +"Z0-9_]``. If the regex pattern is a string, ``\\w`` will match all the " +"characters marked as letters in the Unicode database provided by the :mod:" +"`unicodedata` module. You can use the more restricted definition of ``\\w`` " +"in a string pattern by supplying the :const:`re.ASCII` flag when compiling " +"the regular expression." +msgstr "" + +#: ../Doc/howto/regex.rst:122 +msgid "" +"The following list of special sequences isn't complete. For a complete list " +"of sequences and expanded class definitions for Unicode string patterns, see " +"the last part of :ref:`Regular Expression Syntax ` in the " +"Standard Library reference. In general, the Unicode versions match any " +"character that's in the appropriate category in the Unicode database." +msgstr "" + +#: ../Doc/howto/regex.rst:130 +msgid "``\\d``" +msgstr "" + +#: ../Doc/howto/regex.rst:130 +msgid "Matches any decimal digit; this is equivalent to the class ``[0-9]``." +msgstr "" + +#: ../Doc/howto/regex.rst:133 +msgid "``\\D``" +msgstr "" + +#: ../Doc/howto/regex.rst:133 +msgid "" +"Matches any non-digit character; this is equivalent to the class ``[^0-9]``." +msgstr "" + +#: ../Doc/howto/regex.rst:137 +msgid "``\\s``" +msgstr "" + +#: ../Doc/howto/regex.rst:136 +msgid "" +"Matches any whitespace character; this is equivalent to the class ``[ \\t\\n" +"\\r\\f\\v]``." +msgstr "" + +#: ../Doc/howto/regex.rst:141 +msgid "``\\S``" +msgstr "" + +#: ../Doc/howto/regex.rst:140 +msgid "" +"Matches any non-whitespace character; this is equivalent to the class ``[^ " +"\\t\\n\\r\\f\\v]``." +msgstr "" + +#: ../Doc/howto/regex.rst:145 +msgid "``\\w``" +msgstr "" + +#: ../Doc/howto/regex.rst:144 +msgid "" +"Matches any alphanumeric character; this is equivalent to the class ``[a-zA-" +"Z0-9_]``." +msgstr "" + +#: ../Doc/howto/regex.rst:149 +msgid "``\\W``" +msgstr "" + +#: ../Doc/howto/regex.rst:148 +msgid "" +"Matches any non-alphanumeric character; this is equivalent to the class " +"``[^a-zA-Z0-9_]``." +msgstr "" + +#: ../Doc/howto/regex.rst:151 +msgid "" +"These sequences can be included inside a character class. For example, " +"``[\\s,.]`` is a character class that will match any whitespace character, " +"or ``','`` or ``'.'``." +msgstr "" + +#: ../Doc/howto/regex.rst:155 +msgid "" +"The final metacharacter in this section is ``.``. It matches anything " +"except a newline character, and there's an alternate mode (``re.DOTALL``) " +"where it will match even a newline. ``'.'`` is often used where you want to " +"match \"any character\"." +msgstr "" + +#: ../Doc/howto/regex.rst:162 +msgid "Repeating Things" +msgstr "" + +#: ../Doc/howto/regex.rst:164 +msgid "" +"Being able to match varying sets of characters is the first thing regular " +"expressions can do that isn't already possible with the methods available on " +"strings. However, if that was the only additional capability of regexes, " +"they wouldn't be much of an advance. Another capability is that you can " +"specify that portions of the RE must be repeated a certain number of times." +msgstr "" + +#: ../Doc/howto/regex.rst:170 +msgid "" +"The first metacharacter for repeating things that we'll look at is ``*``. " +"``*`` doesn't match the literal character ``*``; instead, it specifies that " +"the previous character can be matched zero or more times, instead of exactly " +"once." +msgstr "" + +#: ../Doc/howto/regex.rst:174 +msgid "" +"For example, ``ca*t`` will match ``ct`` (0 ``a`` characters), ``cat`` (1 " +"``a``), ``caaat`` (3 ``a`` characters), and so forth. The RE engine has " +"various internal limitations stemming from the size of C's ``int`` type that " +"will prevent it from matching over 2 billion ``a`` characters; patterns are " +"usually not written to match that much data." +msgstr "" + +#: ../Doc/howto/regex.rst:180 +msgid "" +"Repetitions such as ``*`` are :dfn:`greedy`; when repeating a RE, the " +"matching engine will try to repeat it as many times as possible. If later " +"portions of the pattern don't match, the matching engine will then back up " +"and try again with fewer repetitions." +msgstr "" + +#: ../Doc/howto/regex.rst:185 +msgid "" +"A step-by-step example will make this more obvious. Let's consider the " +"expression ``a[bcd]*b``. This matches the letter ``'a'``, zero or more " +"letters from the class ``[bcd]``, and finally ends with a ``'b'``. Now " +"imagine matching this RE against the string ``abcbd``." +msgstr "" + +#: ../Doc/howto/regex.rst:191 +msgid "Step" +msgstr "" + +#: ../Doc/howto/regex.rst:191 +msgid "Matched" +msgstr "" + +#: ../Doc/howto/regex.rst:191 +msgid "Explanation" +msgstr "" + +#: ../Doc/howto/regex.rst:193 +msgid "1" +msgstr "" + +#: ../Doc/howto/regex.rst:193 +msgid "``a``" +msgstr "" + +#: ../Doc/howto/regex.rst:193 +msgid "The ``a`` in the RE matches." +msgstr "" + +#: ../Doc/howto/regex.rst:195 +msgid "2" +msgstr "" + +#: ../Doc/howto/regex.rst:195 +msgid "``abcbd``" +msgstr "" + +#: ../Doc/howto/regex.rst:195 +msgid "" +"The engine matches ``[bcd]*``, going as far as it can, which is to the end " +"of the string." +msgstr "" + +#: ../Doc/howto/regex.rst:199 +msgid "3" +msgstr "" + +#: ../Doc/howto/regex.rst:199 ../Doc/howto/regex.rst:207 +msgid "*Failure*" +msgstr "" + +#: ../Doc/howto/regex.rst:199 +msgid "" +"The engine tries to match ``b``, but the current position is at the end of " +"the string, so it fails." +msgstr "" + +#: ../Doc/howto/regex.rst:204 +msgid "4" +msgstr "" + +#: ../Doc/howto/regex.rst:204 ../Doc/howto/regex.rst:215 +msgid "``abcb``" +msgstr "" + +#: ../Doc/howto/regex.rst:204 +msgid "Back up, so that ``[bcd]*`` matches one less character." +msgstr "" + +#: ../Doc/howto/regex.rst:207 +msgid "5" +msgstr "" + +#: ../Doc/howto/regex.rst:207 +msgid "" +"Try ``b`` again, but the current position is at the last character, which is " +"a ``'d'``." +msgstr "" + +#: ../Doc/howto/regex.rst:211 ../Doc/howto/regex.rst:215 +msgid "6" +msgstr "" + +#: ../Doc/howto/regex.rst:211 +msgid "``abc``" +msgstr "" + +#: ../Doc/howto/regex.rst:211 +msgid "Back up again, so that ``[bcd]*`` is only matching ``bc``." +msgstr "" + +#: ../Doc/howto/regex.rst:215 +msgid "" +"Try ``b`` again. This time the character at the current position is " +"``'b'``, so it succeeds." +msgstr "" + +#: ../Doc/howto/regex.rst:221 +msgid "" +"The end of the RE has now been reached, and it has matched ``abcb``. This " +"demonstrates how the matching engine goes as far as it can at first, and if " +"no match is found it will then progressively back up and retry the rest of " +"the RE again and again. It will back up until it has tried zero matches for " +"``[bcd]*``, and if that subsequently fails, the engine will conclude that " +"the string doesn't match the RE at all." +msgstr "" + +#: ../Doc/howto/regex.rst:228 +msgid "" +"Another repeating metacharacter is ``+``, which matches one or more times. " +"Pay careful attention to the difference between ``*`` and ``+``; ``*`` " +"matches *zero* or more times, so whatever's being repeated may not be " +"present at all, while ``+`` requires at least *one* occurrence. To use a " +"similar example, ``ca+t`` will match ``cat`` (1 ``a``), ``caaat`` (3 " +"``a``'s), but won't match ``ct``." +msgstr "" + +#: ../Doc/howto/regex.rst:235 +msgid "" +"There are two more repeating qualifiers. The question mark character, ``?" +"``, matches either once or zero times; you can think of it as marking " +"something as being optional. For example, ``home-?brew`` matches either " +"``homebrew`` or ``home-brew``." +msgstr "" + +#: ../Doc/howto/regex.rst:240 +msgid "" +"The most complicated repeated qualifier is ``{m,n}``, where *m* and *n* are " +"decimal integers. This qualifier means there must be at least *m* " +"repetitions, and at most *n*. For example, ``a/{1,3}b`` will match ``a/b``, " +"``a//b``, and ``a///b``. It won't match ``ab``, which has no slashes, or " +"``a////b``, which has four." +msgstr "" + +#: ../Doc/howto/regex.rst:246 +msgid "" +"You can omit either *m* or *n*; in that case, a reasonable value is assumed " +"for the missing value. Omitting *m* is interpreted as a lower limit of 0, " +"while omitting *n* results in an upper bound of infinity --- actually, the " +"upper bound is the 2-billion limit mentioned earlier, but that might as well " +"be infinity." +msgstr "" + +#: ../Doc/howto/regex.rst:251 +msgid "" +"Readers of a reductionist bent may notice that the three other qualifiers " +"can all be expressed using this notation. ``{0,}`` is the same as ``*``, " +"``{1,}`` is equivalent to ``+``, and ``{0,1}`` is the same as ``?``. It's " +"better to use ``*``, ``+``, or ``?`` when you can, simply because they're " +"shorter and easier to read." +msgstr "" + +#: ../Doc/howto/regex.rst:259 +msgid "Using Regular Expressions" +msgstr "" + +#: ../Doc/howto/regex.rst:261 +msgid "" +"Now that we've looked at some simple regular expressions, how do we actually " +"use them in Python? The :mod:`re` module provides an interface to the " +"regular expression engine, allowing you to compile REs into objects and then " +"perform matches with them." +msgstr "" + +#: ../Doc/howto/regex.rst:268 +msgid "Compiling Regular Expressions" +msgstr "" + +#: ../Doc/howto/regex.rst:270 +msgid "" +"Regular expressions are compiled into pattern objects, which have methods " +"for various operations such as searching for pattern matches or performing " +"string substitutions. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:279 +msgid "" +":func:`re.compile` also accepts an optional *flags* argument, used to enable " +"various special features and syntax variations. We'll go over the available " +"settings later, but for now a single example will do::" +msgstr "" + +#: ../Doc/howto/regex.rst:285 +msgid "" +"The RE is passed to :func:`re.compile` as a string. REs are handled as " +"strings because regular expressions aren't part of the core Python language, " +"and no special syntax was created for expressing them. (There are " +"applications that don't need REs at all, so there's no need to bloat the " +"language specification by including them.) Instead, the :mod:`re` module is " +"simply a C extension module included with Python, just like the :mod:" +"`socket` or :mod:`zlib` modules." +msgstr "" + +#: ../Doc/howto/regex.rst:292 +msgid "" +"Putting REs in strings keeps the Python language simpler, but has one " +"disadvantage which is the topic of the next section." +msgstr "" + +#: ../Doc/howto/regex.rst:297 +msgid "The Backslash Plague" +msgstr "" + +#: ../Doc/howto/regex.rst:299 +msgid "" +"As stated earlier, regular expressions use the backslash character " +"(``'\\'``) to indicate special forms or to allow special characters to be " +"used without invoking their special meaning. This conflicts with Python's " +"usage of the same character for the same purpose in string literals." +msgstr "" + +#: ../Doc/howto/regex.rst:304 +msgid "" +"Let's say you want to write a RE that matches the string ``\\section``, " +"which might be found in a LaTeX file. To figure out what to write in the " +"program code, start with the desired string to be matched. Next, you must " +"escape any backslashes and other metacharacters by preceding them with a " +"backslash, resulting in the string ``\\\\section``. The resulting string " +"that must be passed to :func:`re.compile` must be ``\\\\section``. However, " +"to express this as a Python string literal, both backslashes must be escaped " +"*again*." +msgstr "" + +#: ../Doc/howto/regex.rst:313 +msgid "Characters" +msgstr "" + +#: ../Doc/howto/regex.rst:313 +msgid "Stage" +msgstr "" + +#: ../Doc/howto/regex.rst:315 +msgid "``\\section``" +msgstr "" + +#: ../Doc/howto/regex.rst:315 +msgid "Text string to be matched" +msgstr "" + +#: ../Doc/howto/regex.rst:317 +msgid "``\\\\section``" +msgstr "" + +#: ../Doc/howto/regex.rst:317 +msgid "Escaped backslash for :func:`re.compile`" +msgstr "" + +#: ../Doc/howto/regex.rst:319 ../Doc/howto/regex.rst:339 +msgid "``\"\\\\\\\\section\"``" +msgstr "" + +#: ../Doc/howto/regex.rst:319 +msgid "Escaped backslashes for a string literal" +msgstr "" + +#: ../Doc/howto/regex.rst:322 +msgid "" +"In short, to match a literal backslash, one has to write ``'\\\\\\\\'`` as " +"the RE string, because the regular expression must be ``\\\\``, and each " +"backslash must be expressed as ``\\\\`` inside a regular Python string " +"literal. In REs that feature backslashes repeatedly, this leads to lots of " +"repeated backslashes and makes the resulting strings difficult to understand." +msgstr "" + +#: ../Doc/howto/regex.rst:328 +msgid "" +"The solution is to use Python's raw string notation for regular expressions; " +"backslashes are not handled in any special way in a string literal prefixed " +"with ``'r'``, so ``r\"\\n\"`` is a two-character string containing ``'\\'`` " +"and ``'n'``, while ``\"\\n\"`` is a one-character string containing a " +"newline. Regular expressions will often be written in Python code using this " +"raw string notation." +msgstr "" + +#: ../Doc/howto/regex.rst:335 +msgid "Regular String" +msgstr "" + +#: ../Doc/howto/regex.rst:335 +msgid "Raw string" +msgstr "" + +#: ../Doc/howto/regex.rst:337 +msgid "``\"ab*\"``" +msgstr "" + +#: ../Doc/howto/regex.rst:337 +msgid "``r\"ab*\"``" +msgstr "" + +#: ../Doc/howto/regex.rst:339 +msgid "``r\"\\\\section\"``" +msgstr "" + +#: ../Doc/howto/regex.rst:341 +msgid "``\"\\\\w+\\\\s+\\\\1\"``" +msgstr "" + +#: ../Doc/howto/regex.rst:341 +msgid "``r\"\\w+\\s+\\1\"``" +msgstr "" + +#: ../Doc/howto/regex.rst:346 +msgid "Performing Matches" +msgstr "" + +#: ../Doc/howto/regex.rst:348 +msgid "" +"Once you have an object representing a compiled regular expression, what do " +"you do with it? Pattern objects have several methods and attributes. Only " +"the most significant ones will be covered here; consult the :mod:`re` docs " +"for a complete listing." +msgstr "" + +#: ../Doc/howto/regex.rst:354 ../Doc/howto/regex.rst:412 +#: ../Doc/howto/regex.rst:1029 +msgid "Method/Attribute" +msgstr "" + +#: ../Doc/howto/regex.rst:354 ../Doc/howto/regex.rst:412 +#: ../Doc/howto/regex.rst:1029 +msgid "Purpose" +msgstr "" + +#: ../Doc/howto/regex.rst:356 +msgid "``match()``" +msgstr "" + +#: ../Doc/howto/regex.rst:356 +msgid "Determine if the RE matches at the beginning of the string." +msgstr "" + +#: ../Doc/howto/regex.rst:359 +msgid "``search()``" +msgstr "" + +#: ../Doc/howto/regex.rst:359 +msgid "Scan through a string, looking for any location where this RE matches." +msgstr "" + +#: ../Doc/howto/regex.rst:362 +msgid "``findall()``" +msgstr "" + +#: ../Doc/howto/regex.rst:362 +msgid "Find all substrings where the RE matches, and returns them as a list." +msgstr "" + +#: ../Doc/howto/regex.rst:365 +msgid "``finditer()``" +msgstr "" + +#: ../Doc/howto/regex.rst:365 +msgid "" +"Find all substrings where the RE matches, and returns them as an :term:" +"`iterator`." +msgstr "" + +#: ../Doc/howto/regex.rst:369 +msgid "" +":meth:`~re.regex.match` and :meth:`~re.regex.search` return ``None`` if no " +"match can be found. If they're successful, a :ref:`match object ` instance is returned, containing information about the match: " +"where it starts and ends, the substring it matched, and more." +msgstr "" + +#: ../Doc/howto/regex.rst:374 +msgid "" +"You can learn about this by interactively experimenting with the :mod:`re` " +"module. If you have :mod:`tkinter` available, you may also want to look at :" +"source:`Tools/demo/redemo.py`, a demonstration program included with the " +"Python distribution. It allows you to enter REs and strings, and displays " +"whether the RE matches or fails. :file:`redemo.py` can be quite useful when " +"trying to debug a complicated RE." +msgstr "" + +#: ../Doc/howto/regex.rst:381 +msgid "" +"This HOWTO uses the standard Python interpreter for its examples. First, run " +"the Python interpreter, import the :mod:`re` module, and compile a RE::" +msgstr "" + +#: ../Doc/howto/regex.rst:389 +msgid "" +"Now, you can try matching various strings against the RE ``[a-z]+``. An " +"empty string shouldn't match at all, since ``+`` means 'one or more " +"repetitions'. :meth:`match` should return ``None`` in this case, which will " +"cause the interpreter to print no output. You can explicitly print the " +"result of :meth:`match` to make this clear. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:399 +msgid "" +"Now, let's try it on a string that it should match, such as ``tempo``. In " +"this case, :meth:`match` will return a :ref:`match object `, " +"so you should store the result in a variable for later use. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:407 +msgid "" +"Now you can query the :ref:`match object ` for information " +"about the matching string. :ref:`match object ` instances " +"also have several methods and attributes; the most important ones are:" +msgstr "" + +#: ../Doc/howto/regex.rst:414 +msgid "``group()``" +msgstr "" + +#: ../Doc/howto/regex.rst:414 +msgid "Return the string matched by the RE" +msgstr "" + +#: ../Doc/howto/regex.rst:416 +msgid "``start()``" +msgstr "" + +#: ../Doc/howto/regex.rst:416 +msgid "Return the starting position of the match" +msgstr "" + +#: ../Doc/howto/regex.rst:418 +msgid "``end()``" +msgstr "" + +#: ../Doc/howto/regex.rst:418 +msgid "Return the ending position of the match" +msgstr "" + +#: ../Doc/howto/regex.rst:420 +msgid "``span()``" +msgstr "" + +#: ../Doc/howto/regex.rst:420 +msgid "Return a tuple containing the (start, end) positions of the match" +msgstr "" + +#: ../Doc/howto/regex.rst:424 +msgid "Trying these methods will soon clarify their meaning::" +msgstr "" + +#: ../Doc/howto/regex.rst:433 +msgid "" +":meth:`~re.match.group` returns the substring that was matched by the RE. :" +"meth:`~re.match.start` and :meth:`~re.match.end` return the starting and " +"ending index of the match. :meth:`~re.match.span` returns both start and end " +"indexes in a single tuple. Since the :meth:`match` method only checks if " +"the RE matches at the start of a string, :meth:`start` will always be zero. " +"However, the :meth:`search` method of patterns scans through the string, so " +"the match may not start at zero in that case. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:450 +msgid "" +"In actual programs, the most common style is to store the :ref:`match object " +"` in a variable, and then check if it was ``None``. This " +"usually looks like::" +msgstr "" + +#: ../Doc/howto/regex.rst:461 +msgid "" +"Two pattern methods return all of the matches for a pattern. :meth:`~re." +"regex.findall` returns a list of matching strings::" +msgstr "" + +#: ../Doc/howto/regex.rst:468 +msgid "" +":meth:`findall` has to create the entire list before it can be returned as " +"the result. The :meth:`~re.regex.finditer` method returns a sequence of :" +"ref:`match object ` instances as an :term:`iterator`::" +msgstr "" + +#: ../Doc/howto/regex.rst:484 +msgid "Module-Level Functions" +msgstr "" + +#: ../Doc/howto/regex.rst:486 +msgid "" +"You don't have to create a pattern object and call its methods; the :mod:" +"`re` module also provides top-level functions called :func:`~re.match`, :" +"func:`~re.search`, :func:`~re.findall`, :func:`~re.sub`, and so forth. " +"These functions take the same arguments as the corresponding pattern method " +"with the RE string added as the first argument, and still return either " +"``None`` or a :ref:`match object ` instance. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:498 +msgid "" +"Under the hood, these functions simply create a pattern object for you and " +"call the appropriate method on it. They also store the compiled object in a " +"cache, so future calls using the same RE won't need to parse the pattern " +"again and again." +msgstr "" + +#: ../Doc/howto/regex.rst:503 +msgid "" +"Should you use these module-level functions, or should you get the pattern " +"and call its methods yourself? If you're accessing a regex within a loop, " +"pre-compiling it will save a few function calls. Outside of loops, there's " +"not much difference thanks to the internal cache." +msgstr "" + +#: ../Doc/howto/regex.rst:511 +msgid "Compilation Flags" +msgstr "" + +#: ../Doc/howto/regex.rst:513 +msgid "" +"Compilation flags let you modify some aspects of how regular expressions " +"work. Flags are available in the :mod:`re` module under two names, a long " +"name such as :const:`IGNORECASE` and a short, one-letter form such as :const:" +"`I`. (If you're familiar with Perl's pattern modifiers, the one-letter " +"forms use the same letters; the short form of :const:`re.VERBOSE` is :const:" +"`re.X`, for example.) Multiple flags can be specified by bitwise OR-ing " +"them; ``re.I | re.M`` sets both the :const:`I` and :const:`M` flags, for " +"example." +msgstr "" + +#: ../Doc/howto/regex.rst:521 +msgid "" +"Here's a table of the available flags, followed by a more detailed " +"explanation of each one." +msgstr "" + +#: ../Doc/howto/regex.rst:525 +msgid "Flag" +msgstr "" + +#: ../Doc/howto/regex.rst:525 +msgid "Meaning" +msgstr "" + +#: ../Doc/howto/regex.rst:527 +msgid ":const:`ASCII`, :const:`A`" +msgstr "" + +#: ../Doc/howto/regex.rst:527 +msgid "" +"Makes several escapes like ``\\w``, ``\\b``, ``\\s`` and ``\\d`` match only " +"on ASCII characters with the respective property." +msgstr "" + +#: ../Doc/howto/regex.rst:531 +msgid ":const:`DOTALL`, :const:`S`" +msgstr "" + +#: ../Doc/howto/regex.rst:531 +msgid "Make ``.`` match any character, including newlines" +msgstr "" + +#: ../Doc/howto/regex.rst:534 +msgid ":const:`IGNORECASE`, :const:`I`" +msgstr "" + +#: ../Doc/howto/regex.rst:534 +msgid "Do case-insensitive matches" +msgstr "" + +#: ../Doc/howto/regex.rst:536 +msgid ":const:`LOCALE`, :const:`L`" +msgstr "" + +#: ../Doc/howto/regex.rst:536 +msgid "Do a locale-aware match" +msgstr "" + +#: ../Doc/howto/regex.rst:538 +msgid ":const:`MULTILINE`, :const:`M`" +msgstr "" + +#: ../Doc/howto/regex.rst:538 +msgid "Multi-line matching, affecting ``^`` and ``$``" +msgstr "" + +#: ../Doc/howto/regex.rst:541 +msgid ":const:`VERBOSE`, :const:`X` (for 'extended')" +msgstr "" + +#: ../Doc/howto/regex.rst:541 +msgid "" +"Enable verbose REs, which can be organized more cleanly and understandably." +msgstr "" + +#: ../Doc/howto/regex.rst:550 +msgid "" +"Perform case-insensitive matching; character class and literal strings will " +"match letters by ignoring case. For example, ``[A-Z]`` will match lowercase " +"letters, too, and ``Spam`` will match ``Spam``, ``spam``, or ``spAM``. This " +"lowercasing doesn't take the current locale into account; it will if you " +"also set the :const:`LOCALE` flag." +msgstr "" + +#: ../Doc/howto/regex.rst:561 +msgid "" +"Make ``\\w``, ``\\W``, ``\\b``, and ``\\B``, dependent on the current locale " +"instead of the Unicode database." +msgstr "" + +#: ../Doc/howto/regex.rst:564 +msgid "" +"Locales are a feature of the C library intended to help in writing programs " +"that take account of language differences. For example, if you're " +"processing French text, you'd want to be able to write ``\\w+`` to match " +"words, but ``\\w`` only matches the character class ``[A-Za-z]``; it won't " +"match ``'é'`` or ``'ç'``. If your system is configured properly and a " +"French locale is selected, certain C functions will tell the program that " +"``'é'`` should also be considered a letter. Setting the :const:`LOCALE` flag " +"when compiling a regular expression will cause the resulting compiled object " +"to use these C functions for ``\\w``; this is slower, but also enables ``\\w" +"+`` to match French words as you'd expect." +msgstr "" + +#: ../Doc/howto/regex.rst:579 +msgid "" +"(``^`` and ``$`` haven't been explained yet; they'll be introduced in " +"section :ref:`more-metacharacters`.)" +msgstr "" + +#: ../Doc/howto/regex.rst:582 +msgid "" +"Usually ``^`` matches only at the beginning of the string, and ``$`` matches " +"only at the end of the string and immediately before the newline (if any) at " +"the end of the string. When this flag is specified, ``^`` matches at the " +"beginning of the string and at the beginning of each line within the string, " +"immediately following each newline. Similarly, the ``$`` metacharacter " +"matches either at the end of the string and at the end of each line " +"(immediately preceding each newline)." +msgstr "" + +#: ../Doc/howto/regex.rst:595 +msgid "" +"Makes the ``'.'`` special character match any character at all, including a " +"newline; without this flag, ``'.'`` will match anything *except* a newline." +msgstr "" + +#: ../Doc/howto/regex.rst:603 +msgid "" +"Make ``\\w``, ``\\W``, ``\\b``, ``\\B``, ``\\s`` and ``\\S`` perform ASCII-" +"only matching instead of full Unicode matching. This is only meaningful for " +"Unicode patterns, and is ignored for byte patterns." +msgstr "" + +#: ../Doc/howto/regex.rst:612 +msgid "" +"This flag allows you to write regular expressions that are more readable by " +"granting you more flexibility in how you can format them. When this flag " +"has been specified, whitespace within the RE string is ignored, except when " +"the whitespace is in a character class or preceded by an unescaped " +"backslash; this lets you organize and indent the RE more clearly. This flag " +"also lets you put comments within a RE that will be ignored by the engine; " +"comments are marked by a ``'#'`` that's neither in a character class or " +"preceded by an unescaped backslash." +msgstr "" + +#: ../Doc/howto/regex.rst:621 +msgid "" +"For example, here's a RE that uses :const:`re.VERBOSE`; see how much easier " +"it is to read? ::" +msgstr "" + +#: ../Doc/howto/regex.rst:634 +msgid "Without the verbose setting, the RE would look like this::" +msgstr "" + +#: ../Doc/howto/regex.rst:640 +msgid "" +"In the above example, Python's automatic concatenation of string literals " +"has been used to break up the RE into smaller pieces, but it's still more " +"difficult to understand than the version using :const:`re.VERBOSE`." +msgstr "" + +#: ../Doc/howto/regex.rst:646 +msgid "More Pattern Power" +msgstr "" + +#: ../Doc/howto/regex.rst:648 +msgid "" +"So far we've only covered a part of the features of regular expressions. In " +"this section, we'll cover some new metacharacters, and how to use groups to " +"retrieve portions of the text that was matched." +msgstr "" + +#: ../Doc/howto/regex.rst:656 +msgid "More Metacharacters" +msgstr "" + +#: ../Doc/howto/regex.rst:658 +msgid "" +"There are some metacharacters that we haven't covered yet. Most of them " +"will be covered in this section." +msgstr "" + +#: ../Doc/howto/regex.rst:661 +msgid "" +"Some of the remaining metacharacters to be discussed are :dfn:`zero-width " +"assertions`. They don't cause the engine to advance through the string; " +"instead, they consume no characters at all, and simply succeed or fail. For " +"example, ``\\b`` is an assertion that the current position is located at a " +"word boundary; the position isn't changed by the ``\\b`` at all. This means " +"that zero-width assertions should never be repeated, because if they match " +"once at a given location, they can obviously be matched an infinite number " +"of times." +msgstr "" + +#: ../Doc/howto/regex.rst:677 +msgid "``|``" +msgstr "" + +#: ../Doc/howto/regex.rst:670 +msgid "" +"Alternation, or the \"or\" operator. If A and B are regular expressions, " +"``A|B`` will match any string that matches either ``A`` or ``B``. ``|`` has " +"very low precedence in order to make it work reasonably when you're " +"alternating multi-character strings. ``Crow|Servo`` will match either " +"``Crow`` or ``Servo``, not ``Cro``, a ``'w'`` or an ``'S'``, and ``ervo``." +msgstr "" + +#: ../Doc/howto/regex.rst:676 +msgid "" +"To match a literal ``'|'``, use ``\\|``, or enclose it inside a character " +"class, as in ``[|]``." +msgstr "" + +#: ../Doc/howto/regex.rst:693 +msgid "``^``" +msgstr "" + +#: ../Doc/howto/regex.rst:680 +msgid "" +"Matches at the beginning of lines. Unless the :const:`MULTILINE` flag has " +"been set, this will only match at the beginning of the string. In :const:" +"`MULTILINE` mode, this also matches immediately after each newline within " +"the string." +msgstr "" + +#: ../Doc/howto/regex.rst:684 +msgid "" +"For example, if you wish to match the word ``From`` only at the beginning of " +"a line, the RE to use is ``^From``. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:707 +msgid "``$``" +msgstr "" + +#: ../Doc/howto/regex.rst:696 +msgid "" +"Matches at the end of a line, which is defined as either the end of the " +"string, or any location followed by a newline character. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:706 +msgid "" +"To match a literal ``'$'``, use ``\\$`` or enclose it inside a character " +"class, as in ``[$]``." +msgstr "" + +#: ../Doc/howto/regex.rst:713 +msgid "``\\A``" +msgstr "" + +#: ../Doc/howto/regex.rst:710 +msgid "" +"Matches only at the start of the string. When not in :const:`MULTILINE` " +"mode, ``\\A`` and ``^`` are effectively the same. In :const:`MULTILINE` " +"mode, they're different: ``\\A`` still matches only at the beginning of the " +"string, but ``^`` may match at any location inside the string that follows a " +"newline character." +msgstr "" + +#: ../Doc/howto/regex.rst:716 +msgid "``\\Z``" +msgstr "" + +#: ../Doc/howto/regex.rst:716 +msgid "Matches only at the end of the string." +msgstr "" + +#: ../Doc/howto/regex.rst:751 +msgid "``\\b``" +msgstr "" + +#: ../Doc/howto/regex.rst:719 +msgid "" +"Word boundary. This is a zero-width assertion that matches only at the " +"beginning or end of a word. A word is defined as a sequence of alphanumeric " +"characters, so the end of a word is indicated by whitespace or a non-" +"alphanumeric character." +msgstr "" + +#: ../Doc/howto/regex.rst:724 +msgid "" +"The following example matches ``class`` only when it's a complete word; it " +"won't match when it's contained inside another word. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:735 +msgid "" +"There are two subtleties you should remember when using this special " +"sequence. First, this is the worst collision between Python's string " +"literals and regular expression sequences. In Python's string literals, ``" +"\\b`` is the backspace character, ASCII value 8. If you're not using raw " +"strings, then Python will convert the ``\\b`` to a backspace, and your RE " +"won't match as you expect it to. The following example looks the same as our " +"previous RE, but omits the ``'r'`` in front of the RE string. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:749 +msgid "" +"Second, inside a character class, where there's no use for this assertion, ``" +"\\b`` represents the backspace character, for compatibility with Python's " +"string literals." +msgstr "" + +#: ../Doc/howto/regex.rst:756 +msgid "``\\B``" +msgstr "" + +#: ../Doc/howto/regex.rst:754 +msgid "" +"Another zero-width assertion, this is the opposite of ``\\b``, only matching " +"when the current position is not at a word boundary." +msgstr "" + +#: ../Doc/howto/regex.rst:759 +msgid "Grouping" +msgstr "" + +#: ../Doc/howto/regex.rst:761 +msgid "" +"Frequently you need to obtain more information than just whether the RE " +"matched or not. Regular expressions are often used to dissect strings by " +"writing a RE divided into several subgroups which match different components " +"of interest. For example, an RFC-822 header line is divided into a header " +"name and a value, separated by a ``':'``, like this::" +msgstr "" + +#: ../Doc/howto/regex.rst:772 +msgid "" +"This can be handled by writing a regular expression which matches an entire " +"header line, and has one group which matches the header name, and another " +"group which matches the header's value." +msgstr "" + +#: ../Doc/howto/regex.rst:776 +msgid "" +"Groups are marked by the ``'('``, ``')'`` metacharacters. ``'('`` and " +"``')'`` have much the same meaning as they do in mathematical expressions; " +"they group together the expressions contained inside them, and you can " +"repeat the contents of a group with a repeating qualifier, such as ``*``, ``" +"+``, ``?``, or ``{m,n}``. For example, ``(ab)*`` will match zero or more " +"repetitions of ``ab``. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:787 +msgid "" +"Groups indicated with ``'('``, ``')'`` also capture the starting and ending " +"index of the text that they match; this can be retrieved by passing an " +"argument to :meth:`group`, :meth:`start`, :meth:`end`, and :meth:`span`. " +"Groups are numbered starting with 0. Group 0 is always present; it's the " +"whole RE, so :ref:`match object ` methods all have group 0 as " +"their default argument. Later we'll see how to express groups that don't " +"capture the span of text that they match. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:802 +msgid "" +"Subgroups are numbered from left to right, from 1 upward. Groups can be " +"nested; to determine the number, just count the opening parenthesis " +"characters, going from left to right. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:815 +msgid "" +":meth:`group` can be passed multiple group numbers at a time, in which case " +"it will return a tuple containing the corresponding values for those " +"groups. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:821 +msgid "" +"The :meth:`groups` method returns a tuple containing the strings for all the " +"subgroups, from 1 up to however many there are. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:827 +msgid "" +"Backreferences in a pattern allow you to specify that the contents of an " +"earlier capturing group must also be found at the current location in the " +"string. For example, ``\\1`` will succeed if the exact contents of group 1 " +"can be found at the current position, and fails otherwise. Remember that " +"Python's string literals also use a backslash followed by numbers to allow " +"including arbitrary characters in a string, so be sure to use a raw string " +"when incorporating backreferences in a RE." +msgstr "" + +#: ../Doc/howto/regex.rst:835 +msgid "For example, the following RE detects doubled words in a string. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:841 +msgid "" +"Backreferences like this aren't often useful for just searching through a " +"string --- there are few text formats which repeat data in this way --- but " +"you'll soon find out that they're *very* useful when performing string " +"substitutions." +msgstr "" + +#: ../Doc/howto/regex.rst:847 +msgid "Non-capturing and Named Groups" +msgstr "" + +#: ../Doc/howto/regex.rst:849 +msgid "" +"Elaborate REs may use many groups, both to capture substrings of interest, " +"and to group and structure the RE itself. In complex REs, it becomes " +"difficult to keep track of the group numbers. There are two features which " +"help with this problem. Both of them use a common syntax for regular " +"expression extensions, so we'll look at that first." +msgstr "" + +#: ../Doc/howto/regex.rst:855 +msgid "" +"Perl 5 is well known for its powerful additions to standard regular " +"expressions. For these new features the Perl developers couldn't choose new " +"single-keystroke metacharacters or new special sequences beginning with ``" +"\\`` without making Perl's regular expressions confusingly different from " +"standard REs. If they chose ``&`` as a new metacharacter, for example, old " +"expressions would be assuming that ``&`` was a regular character and " +"wouldn't have escaped it by writing ``\\&`` or ``[&]``." +msgstr "" + +#: ../Doc/howto/regex.rst:862 +msgid "" +"The solution chosen by the Perl developers was to use ``(?...)`` as the " +"extension syntax. ``?`` immediately after a parenthesis was a syntax error " +"because the ``?`` would have nothing to repeat, so this didn't introduce any " +"compatibility problems. The characters immediately after the ``?`` " +"indicate what extension is being used, so ``(?=foo)`` is one thing (a " +"positive lookahead assertion) and ``(?:foo)`` is something else (a non-" +"capturing group containing the subexpression ``foo``)." +msgstr "" + +#: ../Doc/howto/regex.rst:870 +msgid "" +"Python supports several of Perl's extensions and adds an extension syntax to " +"Perl's extension syntax. If the first character after the question mark is " +"a ``P``, you know that it's an extension that's specific to Python." +msgstr "" + +#: ../Doc/howto/regex.rst:875 +msgid "" +"Now that we've looked at the general extension syntax, we can return to the " +"features that simplify working with groups in complex REs." +msgstr "" + +#: ../Doc/howto/regex.rst:878 +msgid "" +"Sometimes you'll want to use a group to denote a part of a regular " +"expression, but aren't interested in retrieving the group's contents. You " +"can make this fact explicit by using a non-capturing group: ``(?:...)``, " +"where you can replace the ``...`` with any other regular expression. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:890 +msgid "" +"Except for the fact that you can't retrieve the contents of what the group " +"matched, a non-capturing group behaves exactly the same as a capturing " +"group; you can put anything inside it, repeat it with a repetition " +"metacharacter such as ``*``, and nest it within other groups (capturing or " +"non-capturing). ``(?:...)`` is particularly useful when modifying an " +"existing pattern, since you can add new groups without changing how all the " +"other groups are numbered. It should be mentioned that there's no " +"performance difference in searching between capturing and non-capturing " +"groups; neither form is any faster than the other." +msgstr "" + +#: ../Doc/howto/regex.rst:899 +msgid "" +"A more significant feature is named groups: instead of referring to them by " +"numbers, groups can be referenced by a name." +msgstr "" + +#: ../Doc/howto/regex.rst:902 +msgid "" +"The syntax for a named group is one of the Python-specific extensions: ``(?" +"P...)``. *name* is, obviously, the name of the group. Named groups " +"behave exactly like capturing groups, and additionally associate a name with " +"a group. The :ref:`match object ` methods that deal with " +"capturing groups all accept either integers that refer to the group by " +"number or strings that contain the desired group's name. Named groups are " +"still given numbers, so you can retrieve information about a group in two " +"ways::" +msgstr "" + +#: ../Doc/howto/regex.rst:917 +msgid "" +"Named groups are handy because they let you use easily-remembered names, " +"instead of having to remember numbers. Here's an example RE from the :mod:" +"`imaplib` module::" +msgstr "" + +#: ../Doc/howto/regex.rst:928 +msgid "" +"It's obviously much easier to retrieve ``m.group('zonem')``, instead of " +"having to remember to retrieve group 9." +msgstr "" + +#: ../Doc/howto/regex.rst:931 +msgid "" +"The syntax for backreferences in an expression such as ``(...)\\1`` refers " +"to the number of the group. There's naturally a variant that uses the group " +"name instead of the number. This is another Python extension: ``(?P=name)`` " +"indicates that the contents of the group called *name* should again be " +"matched at the current point. The regular expression for finding doubled " +"words, ``(\\b\\w+)\\s+\\1`` can also be written as ``(?P\\b\\w+)\\s+(?" +"P=word)``::" +msgstr "" + +#: ../Doc/howto/regex.rst:944 +msgid "Lookahead Assertions" +msgstr "" + +#: ../Doc/howto/regex.rst:946 +msgid "" +"Another zero-width assertion is the lookahead assertion. Lookahead " +"assertions are available in both positive and negative form, and look like " +"this:" +msgstr "" + +#: ../Doc/howto/regex.rst:954 +msgid "``(?=...)``" +msgstr "" + +#: ../Doc/howto/regex.rst:950 +msgid "" +"Positive lookahead assertion. This succeeds if the contained regular " +"expression, represented here by ``...``, successfully matches at the current " +"location, and fails otherwise. But, once the contained expression has been " +"tried, the matching engine doesn't advance at all; the rest of the pattern " +"is tried right where the assertion started." +msgstr "" + +#: ../Doc/howto/regex.rst:959 +msgid "``(?!...)``" +msgstr "" + +#: ../Doc/howto/regex.rst:957 +msgid "" +"Negative lookahead assertion. This is the opposite of the positive " +"assertion; it succeeds if the contained expression *doesn't* match at the " +"current position in the string." +msgstr "" + +#: ../Doc/howto/regex.rst:961 +msgid "" +"To make this concrete, let's look at a case where a lookahead is useful. " +"Consider a simple pattern to match a filename and split it apart into a base " +"name and an extension, separated by a ``.``. For example, in ``news.rc``, " +"``news`` is the base name, and ``rc`` is the filename's extension." +msgstr "" + +#: ../Doc/howto/regex.rst:966 +msgid "The pattern to match this is quite simple:" +msgstr "" + +#: ../Doc/howto/regex.rst:968 +msgid "``.*[.].*$``" +msgstr "" + +#: ../Doc/howto/regex.rst:970 +msgid "" +"Notice that the ``.`` needs to be treated specially because it's a " +"metacharacter, so it's inside a character class to only match that specific " +"character. Also notice the trailing ``$``; this is added to ensure that all " +"the rest of the string must be included in the extension. This regular " +"expression matches ``foo.bar`` and ``autoexec.bat`` and ``sendmail.cf`` and " +"``printers.conf``." +msgstr "" + +#: ../Doc/howto/regex.rst:977 +msgid "" +"Now, consider complicating the problem a bit; what if you want to match " +"filenames where the extension is not ``bat``? Some incorrect attempts:" +msgstr "" + +#: ../Doc/howto/regex.rst:980 +msgid "" +"``.*[.][^b].*$`` The first attempt above tries to exclude ``bat`` by " +"requiring that the first character of the extension is not a ``b``. This is " +"wrong, because the pattern also doesn't match ``foo.bar``." +msgstr "" + +#: ../Doc/howto/regex.rst:984 +msgid "``.*[.]([^b]..|.[^a].|..[^t])$``" +msgstr "" + +#: ../Doc/howto/regex.rst:986 +msgid "" +"The expression gets messier when you try to patch up the first solution by " +"requiring one of the following cases to match: the first character of the " +"extension isn't ``b``; the second character isn't ``a``; or the third " +"character isn't ``t``. This accepts ``foo.bar`` and rejects ``autoexec." +"bat``, but it requires a three-letter extension and won't accept a filename " +"with a two-letter extension such as ``sendmail.cf``. We'll complicate the " +"pattern again in an effort to fix it." +msgstr "" + +#: ../Doc/howto/regex.rst:994 +msgid "``.*[.]([^b].?.?|.[^a]?.?|..?[^t]?)$``" +msgstr "" + +#: ../Doc/howto/regex.rst:996 +msgid "" +"In the third attempt, the second and third letters are all made optional in " +"order to allow matching extensions shorter than three characters, such as " +"``sendmail.cf``." +msgstr "" + +#: ../Doc/howto/regex.rst:1000 +msgid "" +"The pattern's getting really complicated now, which makes it hard to read " +"and understand. Worse, if the problem changes and you want to exclude both " +"``bat`` and ``exe`` as extensions, the pattern would get even more " +"complicated and confusing." +msgstr "" + +#: ../Doc/howto/regex.rst:1005 +msgid "A negative lookahead cuts through all this confusion:" +msgstr "" + +#: ../Doc/howto/regex.rst:1007 +msgid "" +"``.*[.](?!bat$)[^.]*$`` The negative lookahead means: if the expression " +"``bat`` doesn't match at this point, try the rest of the pattern; if ``bat" +"$`` does match, the whole pattern will fail. The trailing ``$`` is required " +"to ensure that something like ``sample.batch``, where the extension only " +"starts with ``bat``, will be allowed. The ``[^.]*`` makes sure that the " +"pattern works when there are multiple dots in the filename." +msgstr "" + +#: ../Doc/howto/regex.rst:1014 +msgid "" +"Excluding another filename extension is now easy; simply add it as an " +"alternative inside the assertion. The following pattern excludes filenames " +"that end in either ``bat`` or ``exe``:" +msgstr "" + +#: ../Doc/howto/regex.rst:1018 +msgid "``.*[.](?!bat$|exe$)[^.]*$``" +msgstr "" + +#: ../Doc/howto/regex.rst:1022 +msgid "Modifying Strings" +msgstr "" + +#: ../Doc/howto/regex.rst:1024 +msgid "" +"Up to this point, we've simply performed searches against a static string. " +"Regular expressions are also commonly used to modify strings in various " +"ways, using the following pattern methods:" +msgstr "" + +#: ../Doc/howto/regex.rst:1031 +msgid "``split()``" +msgstr "" + +#: ../Doc/howto/regex.rst:1031 +msgid "Split the string into a list, splitting it wherever the RE matches" +msgstr "" + +#: ../Doc/howto/regex.rst:1034 +msgid "``sub()``" +msgstr "" + +#: ../Doc/howto/regex.rst:1034 +msgid "" +"Find all substrings where the RE matches, and replace them with a different " +"string" +msgstr "" + +#: ../Doc/howto/regex.rst:1037 +msgid "``subn()``" +msgstr "" + +#: ../Doc/howto/regex.rst:1037 +msgid "" +"Does the same thing as :meth:`sub`, but returns the new string and the " +"number of replacements" +msgstr "" + +#: ../Doc/howto/regex.rst:1044 +msgid "Splitting Strings" +msgstr "" + +#: ../Doc/howto/regex.rst:1046 +msgid "" +"The :meth:`split` method of a pattern splits a string apart wherever the RE " +"matches, returning a list of the pieces. It's similar to the :meth:`split` " +"method of strings but provides much more generality in the delimiters that " +"you can split by; string :meth:`split` only supports splitting by whitespace " +"or by a fixed string. As you'd expect, there's a module-level :func:`re." +"split` function, too." +msgstr "" + +#: ../Doc/howto/regex.rst:1057 +msgid "" +"Split *string* by the matches of the regular expression. If capturing " +"parentheses are used in the RE, then their contents will also be returned as " +"part of the resulting list. If *maxsplit* is nonzero, at most *maxsplit* " +"splits are performed." +msgstr "" + +#: ../Doc/howto/regex.rst:1062 +msgid "" +"You can limit the number of splits made, by passing a value for *maxsplit*. " +"When *maxsplit* is nonzero, at most *maxsplit* splits will be made, and the " +"remainder of the string is returned as the final element of the list. In " +"the following example, the delimiter is any sequence of non-alphanumeric " +"characters. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1074 +msgid "" +"Sometimes you're not only interested in what the text between delimiters is, " +"but also need to know what the delimiter was. If capturing parentheses are " +"used in the RE, then their values are also returned as part of the list. " +"Compare the following calls::" +msgstr "" + +#: ../Doc/howto/regex.rst:1086 +msgid "" +"The module-level function :func:`re.split` adds the RE to be used as the " +"first argument, but is otherwise the same. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1098 +msgid "Search and Replace" +msgstr "" + +#: ../Doc/howto/regex.rst:1100 +msgid "" +"Another common task is to find all the matches for a pattern, and replace " +"them with a different string. The :meth:`sub` method takes a replacement " +"value, which can be either a string or a function, and the string to be " +"processed." +msgstr "" + +#: ../Doc/howto/regex.rst:1107 +msgid "" +"Returns the string obtained by replacing the leftmost non-overlapping " +"occurrences of the RE in *string* by the replacement *replacement*. If the " +"pattern isn't found, *string* is returned unchanged." +msgstr "" + +#: ../Doc/howto/regex.rst:1111 +msgid "" +"The optional argument *count* is the maximum number of pattern occurrences " +"to be replaced; *count* must be a non-negative integer. The default value " +"of 0 means to replace all occurrences." +msgstr "" + +#: ../Doc/howto/regex.rst:1115 +msgid "" +"Here's a simple example of using the :meth:`sub` method. It replaces colour " +"names with the word ``colour``::" +msgstr "" + +#: ../Doc/howto/regex.rst:1124 +msgid "" +"The :meth:`subn` method does the same work, but returns a 2-tuple containing " +"the new string value and the number of replacements that were performed::" +msgstr "" + +#: ../Doc/howto/regex.rst:1133 +msgid "" +"Empty matches are replaced only when they're not adjacent to a previous " +"match. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1140 +msgid "" +"If *replacement* is a string, any backslash escapes in it are processed. " +"That is, ``\\n`` is converted to a single newline character, ``\\r`` is " +"converted to a carriage return, and so forth. Unknown escapes such as ``" +"\\&`` are left alone. Backreferences, such as ``\\6``, are replaced with the " +"substring matched by the corresponding group in the RE. This lets you " +"incorporate portions of the original text in the resulting replacement " +"string." +msgstr "" + +#: ../Doc/howto/regex.rst:1147 +msgid "" +"This example matches the word ``section`` followed by a string enclosed in " +"``{``, ``}``, and changes ``section`` to ``subsection``::" +msgstr "" + +#: ../Doc/howto/regex.rst:1154 +msgid "" +"There's also a syntax for referring to named groups as defined by the ``(?" +"P...)`` syntax. ``\\g`` will use the substring matched by the " +"group named ``name``, and ``\\g`` uses the corresponding group " +"number. ``\\g<2>`` is therefore equivalent to ``\\2``, but isn't ambiguous " +"in a replacement string such as ``\\g<2>0``. (``\\20`` would be interpreted " +"as a reference to group 20, not a reference to group 2 followed by the " +"literal character ``'0'``.) The following substitutions are all equivalent, " +"but use all three variations of the replacement string. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1171 +msgid "" +"*replacement* can also be a function, which gives you even more control. If " +"*replacement* is a function, the function is called for every non-" +"overlapping occurrence of *pattern*. On each call, the function is passed " +"a :ref:`match object ` argument for the match and can use " +"this information to compute the desired replacement string and return it." +msgstr "" + +#: ../Doc/howto/regex.rst:1177 +msgid "" +"In the following example, the replacement function translates decimals into " +"hexadecimal::" +msgstr "" + +#: ../Doc/howto/regex.rst:1189 +msgid "" +"When using the module-level :func:`re.sub` function, the pattern is passed " +"as the first argument. The pattern may be provided as an object or as a " +"string; if you need to specify regular expression flags, you must either use " +"a pattern object as the first parameter, or use embedded modifiers in the " +"pattern string, e.g. ``sub(\"(?i)b+\", \"x\", \"bbbb BBBB\")`` returns ``'x " +"x'``." +msgstr "" + +#: ../Doc/howto/regex.rst:1197 +msgid "Common Problems" +msgstr "" + +#: ../Doc/howto/regex.rst:1199 +msgid "" +"Regular expressions are a powerful tool for some applications, but in some " +"ways their behaviour isn't intuitive and at times they don't behave the way " +"you may expect them to. This section will point out some of the most common " +"pitfalls." +msgstr "" + +#: ../Doc/howto/regex.rst:1205 +msgid "Use String Methods" +msgstr "" + +#: ../Doc/howto/regex.rst:1207 +msgid "" +"Sometimes using the :mod:`re` module is a mistake. If you're matching a " +"fixed string, or a single character class, and you're not using any :mod:" +"`re` features such as the :const:`IGNORECASE` flag, then the full power of " +"regular expressions may not be required. Strings have several methods for " +"performing operations with fixed strings and they're usually much faster, " +"because the implementation is a single small C loop that's been optimized " +"for the purpose, instead of the large, more generalized regular expression " +"engine." +msgstr "" + +#: ../Doc/howto/regex.rst:1215 +msgid "" +"One example might be replacing a single fixed string with another one; for " +"example, you might replace ``word`` with ``deed``. ``re.sub()`` seems like " +"the function to use for this, but consider the :meth:`replace` method. Note " +"that :func:`replace` will also replace ``word`` inside words, turning " +"``swordfish`` into ``sdeedfish``, but the naive RE ``word`` would have done " +"that, too. (To avoid performing the substitution on parts of words, the " +"pattern would have to be ``\\bword\\b``, in order to require that ``word`` " +"have a word boundary on either side. This takes the job beyond :meth:" +"`replace`'s abilities.)" +msgstr "" + +#: ../Doc/howto/regex.rst:1224 +msgid "" +"Another common task is deleting every occurrence of a single character from " +"a string or replacing it with another single character. You might do this " +"with something like ``re.sub('\\n', ' ', S)``, but :meth:`translate` is " +"capable of doing both tasks and will be faster than any regular expression " +"operation can be." +msgstr "" + +#: ../Doc/howto/regex.rst:1230 +msgid "" +"In short, before turning to the :mod:`re` module, consider whether your " +"problem can be solved with a faster and simpler string method." +msgstr "" + +#: ../Doc/howto/regex.rst:1235 +msgid "match() versus search()" +msgstr "" + +#: ../Doc/howto/regex.rst:1237 +msgid "" +"The :func:`match` function only checks if the RE matches at the beginning of " +"the string while :func:`search` will scan forward through the string for a " +"match. It's important to keep this distinction in mind. Remember, :func:" +"`match` will only report a successful match which will start at 0; if the " +"match wouldn't start at zero, :func:`match` will *not* report it. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1248 +msgid "" +"On the other hand, :func:`search` will scan forward through the string, " +"reporting the first match it finds. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1256 +msgid "" +"Sometimes you'll be tempted to keep using :func:`re.match`, and just add ``." +"*`` to the front of your RE. Resist this temptation and use :func:`re." +"search` instead. The regular expression compiler does some analysis of REs " +"in order to speed up the process of looking for a match. One such analysis " +"figures out what the first character of a match must be; for example, a " +"pattern starting with ``Crow`` must match starting with a ``'C'``. The " +"analysis lets the engine quickly scan through the string looking for the " +"starting character, only trying the full match if a ``'C'`` is found." +msgstr "" + +#: ../Doc/howto/regex.rst:1265 +msgid "" +"Adding ``.*`` defeats this optimization, requiring scanning to the end of " +"the string and then backtracking to find a match for the rest of the RE. " +"Use :func:`re.search` instead." +msgstr "" + +#: ../Doc/howto/regex.rst:1271 +msgid "Greedy versus Non-Greedy" +msgstr "" + +#: ../Doc/howto/regex.rst:1273 +msgid "" +"When repeating a regular expression, as in ``a*``, the resulting action is " +"to consume as much of the pattern as possible. This fact often bites you " +"when you're trying to match a pair of balanced delimiters, such as the angle " +"brackets surrounding an HTML tag. The naive pattern for matching a single " +"HTML tag doesn't work because of the greedy nature of ``.*``. ::" +msgstr "" + +#: ../Doc/howto/regex.rst:1287 +msgid "" +"The RE matches the ``'<'`` in ````, and the ``.*`` consumes the rest " +"of the string. There's still more left in the RE, though, and the ``>`` " +"can't match at the end of the string, so the regular expression engine has " +"to backtrack character by character until it finds a match for the ``>``. " +"The final match extends from the ``'<'`` in ```` to the ``'>'`` in ````, which isn't what you want." +msgstr "" + +#: ../Doc/howto/regex.rst:1294 +msgid "" +"In this case, the solution is to use the non-greedy qualifiers ``*?``, ``+?" +"``, ``??``, or ``{m,n}?``, which match as *little* text as possible. In the " +"above example, the ``'>'`` is tried immediately after the first ``'<'`` " +"matches, and when it fails, the engine advances a character at a time, " +"retrying the ``'>'`` at every step. This produces just the right result::" +msgstr "" + +#: ../Doc/howto/regex.rst:1303 +msgid "" +"(Note that parsing HTML or XML with regular expressions is painful. Quick-" +"and-dirty patterns will handle common cases, but HTML and XML have special " +"cases that will break the obvious regular expression; by the time you've " +"written a regular expression that handles all of the possible cases, the " +"patterns will be *very* complicated. Use an HTML or XML parser module for " +"such tasks.)" +msgstr "" + +#: ../Doc/howto/regex.rst:1311 +msgid "Using re.VERBOSE" +msgstr "" + +#: ../Doc/howto/regex.rst:1313 +msgid "" +"By now you've probably noticed that regular expressions are a very compact " +"notation, but they're not terribly readable. REs of moderate complexity can " +"become lengthy collections of backslashes, parentheses, and metacharacters, " +"making them difficult to read and understand." +msgstr "" + +#: ../Doc/howto/regex.rst:1318 +msgid "" +"For such REs, specifying the ``re.VERBOSE`` flag when compiling the regular " +"expression can be helpful, because it allows you to format the regular " +"expression more clearly." +msgstr "" + +#: ../Doc/howto/regex.rst:1322 +msgid "" +"The ``re.VERBOSE`` flag has several effects. Whitespace in the regular " +"expression that *isn't* inside a character class is ignored. This means " +"that an expression such as ``dog | cat`` is equivalent to the less readable " +"``dog|cat``, but ``[a b]`` will still match the characters ``'a'``, ``'b'``, " +"or a space. In addition, you can also put comments inside a RE; comments " +"extend from a ``#`` character to the next newline. When used with triple-" +"quoted strings, this enables REs to be formatted more neatly::" +msgstr "" + +#: ../Doc/howto/regex.rst:1339 +msgid "This is far more readable than::" +msgstr "" + +#: ../Doc/howto/regex.rst:1345 +msgid "Feedback" +msgstr "" + +#: ../Doc/howto/regex.rst:1347 +msgid "" +"Regular expressions are a complicated topic. Did this document help you " +"understand them? Were there parts that were unclear, or Problems you " +"encountered that weren't covered here? If so, please send suggestions for " +"improvements to the author." +msgstr "" + +#: ../Doc/howto/regex.rst:1352 +msgid "" +"The most complete book on regular expressions is almost certainly Jeffrey " +"Friedl's Mastering Regular Expressions, published by O'Reilly. " +"Unfortunately, it exclusively concentrates on Perl and Java's flavours of " +"regular expressions, and doesn't contain any Python material at all, so it " +"won't be useful as a reference for programming in Python. (The first " +"edition covered Python's now-removed :mod:`regex` module, which won't help " +"you much.) Consider checking it out from your library." +msgstr "" + +#: ../Doc/howto/sockets.rst:5 +msgid "Socket Programming HOWTO" +msgstr "" + +#: ../Doc/howto/sockets.rst:7 +msgid "Gordon McMillan" +msgstr "" + +#: ../Doc/howto/sockets.rst:12 +msgid "" +"Sockets are used nearly everywhere, but are one of the most severely " +"misunderstood technologies around. This is a 10,000 foot overview of " +"sockets. It's not really a tutorial - you'll still have work to do in " +"getting things operational. It doesn't cover the fine points (and there are " +"a lot of them), but I hope it will give you enough background to begin using " +"them decently." +msgstr "" + +#: ../Doc/howto/sockets.rst:20 +msgid "Sockets" +msgstr "" + +#: ../Doc/howto/sockets.rst:22 +msgid "" +"I'm only going to talk about INET (i.e. IPv4) sockets, but they account for " +"at least 99% of the sockets in use. And I'll only talk about STREAM (i.e. " +"TCP) sockets - unless you really know what you're doing (in which case this " +"HOWTO isn't for you!), you'll get better behavior and performance from a " +"STREAM socket than anything else. I will try to clear up the mystery of what " +"a socket is, as well as some hints on how to work with blocking and non-" +"blocking sockets. But I'll start by talking about blocking sockets. You'll " +"need to know how they work before dealing with non-blocking sockets." +msgstr "" + +#: ../Doc/howto/sockets.rst:31 +msgid "" +"Part of the trouble with understanding these things is that \"socket\" can " +"mean a number of subtly different things, depending on context. So first, " +"let's make a distinction between a \"client\" socket - an endpoint of a " +"conversation, and a \"server\" socket, which is more like a switchboard " +"operator. The client application (your browser, for example) uses \"client\" " +"sockets exclusively; the web server it's talking to uses both \"server\" " +"sockets and \"client\" sockets." +msgstr "" + +#: ../Doc/howto/sockets.rst:40 +msgid "History" +msgstr "" + +#: ../Doc/howto/sockets.rst:42 +msgid "" +"Of the various forms of :abbr:`IPC (Inter Process Communication)`, sockets " +"are by far the most popular. On any given platform, there are likely to be " +"other forms of IPC that are faster, but for cross-platform communication, " +"sockets are about the only game in town." +msgstr "" + +#: ../Doc/howto/sockets.rst:47 +msgid "" +"They were invented in Berkeley as part of the BSD flavor of Unix. They " +"spread like wildfire with the Internet. With good reason --- the combination " +"of sockets with INET makes talking to arbitrary machines around the world " +"unbelievably easy (at least compared to other schemes)." +msgstr "" + +#: ../Doc/howto/sockets.rst:54 +msgid "Creating a Socket" +msgstr "" + +#: ../Doc/howto/sockets.rst:56 +msgid "" +"Roughly speaking, when you clicked on the link that brought you to this " +"page, your browser did something like the following::" +msgstr "" + +#: ../Doc/howto/sockets.rst:64 +msgid "" +"When the ``connect`` completes, the socket ``s`` can be used to send in a " +"request for the text of the page. The same socket will read the reply, and " +"then be destroyed. That's right, destroyed. Client sockets are normally only " +"used for one exchange (or a small set of sequential exchanges)." +msgstr "" + +#: ../Doc/howto/sockets.rst:70 +msgid "" +"What happens in the web server is a bit more complex. First, the web server " +"creates a \"server socket\"::" +msgstr "" + +#: ../Doc/howto/sockets.rst:80 +msgid "" +"A couple things to notice: we used ``socket.gethostname()`` so that the " +"socket would be visible to the outside world. If we had used ``s." +"bind(('localhost', 80))`` or ``s.bind(('127.0.0.1', 80))`` we would still " +"have a \"server\" socket, but one that was only visible within the same " +"machine. ``s.bind(('', 80))`` specifies that the socket is reachable by any " +"address the machine happens to have." +msgstr "" + +#: ../Doc/howto/sockets.rst:87 +msgid "" +"A second thing to note: low number ports are usually reserved for \"well " +"known\" services (HTTP, SNMP etc). If you're playing around, use a nice high " +"number (4 digits)." +msgstr "" + +#: ../Doc/howto/sockets.rst:91 +msgid "" +"Finally, the argument to ``listen`` tells the socket library that we want it " +"to queue up as many as 5 connect requests (the normal max) before refusing " +"outside connections. If the rest of the code is written properly, that " +"should be plenty." +msgstr "" + +#: ../Doc/howto/sockets.rst:95 +msgid "" +"Now that we have a \"server\" socket, listening on port 80, we can enter the " +"mainloop of the web server::" +msgstr "" + +#: ../Doc/howto/sockets.rst:106 +msgid "" +"There's actually 3 general ways in which this loop could work - dispatching " +"a thread to handle ``clientsocket``, create a new process to handle " +"``clientsocket``, or restructure this app to use non-blocking sockets, and " +"multiplex between our \"server\" socket and any active ``clientsocket``\\ s " +"using ``select``. More about that later. The important thing to understand " +"now is this: this is *all* a \"server\" socket does. It doesn't send any " +"data. It doesn't receive any data. It just produces \"client\" sockets. Each " +"``clientsocket`` is created in response to some *other* \"client\" socket " +"doing a ``connect()`` to the host and port we're bound to. As soon as we've " +"created that ``clientsocket``, we go back to listening for more connections. " +"The two \"clients\" are free to chat it up - they are using some dynamically " +"allocated port which will be recycled when the conversation ends." +msgstr "" + +#: ../Doc/howto/sockets.rst:121 +msgid "IPC" +msgstr "" + +#: ../Doc/howto/sockets.rst:123 +msgid "" +"If you need fast IPC between two processes on one machine, you should look " +"into pipes or shared memory. If you do decide to use AF_INET sockets, bind " +"the \"server\" socket to ``'localhost'``. On most platforms, this will take " +"a shortcut around a couple of layers of network code and be quite a bit " +"faster." +msgstr "" + +#: ../Doc/howto/sockets.rst:129 +msgid "" +"The :mod:`multiprocessing` integrates cross-platform IPC into a higher-level " +"API." +msgstr "" + +#: ../Doc/howto/sockets.rst:134 +msgid "Using a Socket" +msgstr "" + +#: ../Doc/howto/sockets.rst:136 +msgid "" +"The first thing to note, is that the web browser's \"client\" socket and the " +"web server's \"client\" socket are identical beasts. That is, this is a " +"\"peer to peer\" conversation. Or to put it another way, *as the designer, " +"you will have to decide what the rules of etiquette are for a conversation*. " +"Normally, the ``connect``\\ ing socket starts the conversation, by sending " +"in a request, or perhaps a signon. But that's a design decision - it's not a " +"rule of sockets." +msgstr "" + +#: ../Doc/howto/sockets.rst:143 +msgid "" +"Now there are two sets of verbs to use for communication. You can use " +"``send`` and ``recv``, or you can transform your client socket into a file-" +"like beast and use ``read`` and ``write``. The latter is the way Java " +"presents its sockets. I'm not going to talk about it here, except to warn " +"you that you need to use ``flush`` on sockets. These are buffered \"files\", " +"and a common mistake is to ``write`` something, and then ``read`` for a " +"reply. Without a ``flush`` in there, you may wait forever for the reply, " +"because the request may still be in your output buffer." +msgstr "" + +#: ../Doc/howto/sockets.rst:152 +msgid "" +"Now we come to the major stumbling block of sockets - ``send`` and ``recv`` " +"operate on the network buffers. They do not necessarily handle all the bytes " +"you hand them (or expect from them), because their major focus is handling " +"the network buffers. In general, they return when the associated network " +"buffers have been filled (``send``) or emptied (``recv``). They then tell " +"you how many bytes they handled. It is *your* responsibility to call them " +"again until your message has been completely dealt with." +msgstr "" + +#: ../Doc/howto/sockets.rst:160 +msgid "" +"When a ``recv`` returns 0 bytes, it means the other side has closed (or is " +"in the process of closing) the connection. You will not receive any more " +"data on this connection. Ever. You may be able to send data successfully; " +"I'll talk more about this later." +msgstr "" + +#: ../Doc/howto/sockets.rst:165 +msgid "" +"A protocol like HTTP uses a socket for only one transfer. The client sends a " +"request, then reads a reply. That's it. The socket is discarded. This means " +"that a client can detect the end of the reply by receiving 0 bytes." +msgstr "" + +#: ../Doc/howto/sockets.rst:169 +msgid "" +"But if you plan to reuse your socket for further transfers, you need to " +"realize that *there is no* :abbr:`EOT (End of Transfer)` *on a socket.* I " +"repeat: if a socket ``send`` or ``recv`` returns after handling 0 bytes, the " +"connection has been broken. If the connection has *not* been broken, you " +"may wait on a ``recv`` forever, because the socket will *not* tell you that " +"there's nothing more to read (for now). Now if you think about that a bit, " +"you'll come to realize a fundamental truth of sockets: *messages must either " +"be fixed length* (yuck), *or be delimited* (shrug), *or indicate how long " +"they are* (much better), *or end by shutting down the connection*. The " +"choice is entirely yours, (but some ways are righter than others)." +msgstr "" + +#: ../Doc/howto/sockets.rst:180 +msgid "" +"Assuming you don't want to end the connection, the simplest solution is a " +"fixed length message::" +msgstr "" + +#: ../Doc/howto/sockets.rst:217 +msgid "" +"The sending code here is usable for almost any messaging scheme - in Python " +"you send strings, and you can use ``len()`` to determine its length (even if " +"it has embedded ``\\0`` characters). It's mostly the receiving code that " +"gets more complex. (And in C, it's not much worse, except you can't use " +"``strlen`` if the message has embedded ``\\0``\\ s.)" +msgstr "" + +#: ../Doc/howto/sockets.rst:223 +msgid "" +"The easiest enhancement is to make the first character of the message an " +"indicator of message type, and have the type determine the length. Now you " +"have two ``recv``\\ s - the first to get (at least) that first character so " +"you can look up the length, and the second in a loop to get the rest. If you " +"decide to go the delimited route, you'll be receiving in some arbitrary " +"chunk size, (4096 or 8192 is frequently a good match for network buffer " +"sizes), and scanning what you've received for a delimiter." +msgstr "" + +#: ../Doc/howto/sockets.rst:231 +msgid "" +"One complication to be aware of: if your conversational protocol allows " +"multiple messages to be sent back to back (without some kind of reply), and " +"you pass ``recv`` an arbitrary chunk size, you may end up reading the start " +"of a following message. You'll need to put that aside and hold onto it, " +"until it's needed." +msgstr "" + +#: ../Doc/howto/sockets.rst:237 +msgid "" +"Prefixing the message with its length (say, as 5 numeric characters) gets " +"more complex, because (believe it or not), you may not get all 5 characters " +"in one ``recv``. In playing around, you'll get away with it; but in high " +"network loads, your code will very quickly break unless you use two ``recv`` " +"loops - the first to determine the length, the second to get the data part " +"of the message. Nasty. This is also when you'll discover that ``send`` does " +"not always manage to get rid of everything in one pass. And despite having " +"read this, you will eventually get bit by it!" +msgstr "" + +#: ../Doc/howto/sockets.rst:246 +msgid "" +"In the interests of space, building your character, (and preserving my " +"competitive position), these enhancements are left as an exercise for the " +"reader. Lets move on to cleaning up." +msgstr "" + +#: ../Doc/howto/sockets.rst:252 +msgid "Binary Data" +msgstr "" + +#: ../Doc/howto/sockets.rst:254 +msgid "" +"It is perfectly possible to send binary data over a socket. The major " +"problem is that not all machines use the same formats for binary data. For " +"example, a Motorola chip will represent a 16 bit integer with the value 1 as " +"the two hex bytes 00 01. Intel and DEC, however, are byte-reversed - that " +"same 1 is 01 00. Socket libraries have calls for converting 16 and 32 bit " +"integers - ``ntohl, htonl, ntohs, htons`` where \"n\" means *network* and \"h" +"\" means *host*, \"s\" means *short* and \"l\" means *long*. Where network " +"order is host order, these do nothing, but where the machine is byte-" +"reversed, these swap the bytes around appropriately." +msgstr "" + +#: ../Doc/howto/sockets.rst:264 +msgid "" +"In these days of 32 bit machines, the ascii representation of binary data is " +"frequently smaller than the binary representation. That's because a " +"surprising amount of the time, all those longs have the value 0, or maybe 1. " +"The string \"0\" would be two bytes, while binary is four. Of course, this " +"doesn't fit well with fixed-length messages. Decisions, decisions." +msgstr "" + +#: ../Doc/howto/sockets.rst:272 +msgid "Disconnecting" +msgstr "" + +#: ../Doc/howto/sockets.rst:274 +msgid "" +"Strictly speaking, you're supposed to use ``shutdown`` on a socket before " +"you ``close`` it. The ``shutdown`` is an advisory to the socket at the " +"other end. Depending on the argument you pass it, it can mean \"I'm not " +"going to send anymore, but I'll still listen\", or \"I'm not listening, good " +"riddance!\". Most socket libraries, however, are so used to programmers " +"neglecting to use this piece of etiquette that normally a ``close`` is the " +"same as ``shutdown(); close()``. So in most situations, an explicit " +"``shutdown`` is not needed." +msgstr "" + +#: ../Doc/howto/sockets.rst:282 +msgid "" +"One way to use ``shutdown`` effectively is in an HTTP-like exchange. The " +"client sends a request and then does a ``shutdown(1)``. This tells the " +"server \"This client is done sending, but can still receive.\" The server " +"can detect \"EOF\" by a receive of 0 bytes. It can assume it has the " +"complete request. The server sends a reply. If the ``send`` completes " +"successfully then, indeed, the client was still receiving." +msgstr "" + +#: ../Doc/howto/sockets.rst:289 +msgid "" +"Python takes the automatic shutdown a step further, and says that when a " +"socket is garbage collected, it will automatically do a ``close`` if it's " +"needed. But relying on this is a very bad habit. If your socket just " +"disappears without doing a ``close``, the socket at the other end may hang " +"indefinitely, thinking you're just being slow. *Please* ``close`` your " +"sockets when you're done." +msgstr "" + +#: ../Doc/howto/sockets.rst:297 +msgid "When Sockets Die" +msgstr "" + +#: ../Doc/howto/sockets.rst:299 +msgid "" +"Probably the worst thing about using blocking sockets is what happens when " +"the other side comes down hard (without doing a ``close``). Your socket is " +"likely to hang. TCP is a reliable protocol, and it will wait a long, long " +"time before giving up on a connection. If you're using threads, the entire " +"thread is essentially dead. There's not much you can do about it. As long as " +"you aren't doing something dumb, like holding a lock while doing a blocking " +"read, the thread isn't really consuming much in the way of resources. Do " +"*not* try to kill the thread - part of the reason that threads are more " +"efficient than processes is that they avoid the overhead associated with the " +"automatic recycling of resources. In other words, if you do manage to kill " +"the thread, your whole process is likely to be screwed up." +msgstr "" + +#: ../Doc/howto/sockets.rst:313 +msgid "Non-blocking Sockets" +msgstr "" + +#: ../Doc/howto/sockets.rst:315 +msgid "" +"If you've understood the preceding, you already know most of what you need " +"to know about the mechanics of using sockets. You'll still use the same " +"calls, in much the same ways. It's just that, if you do it right, your app " +"will be almost inside-out." +msgstr "" + +#: ../Doc/howto/sockets.rst:320 +msgid "" +"In Python, you use ``socket.setblocking(0)`` to make it non-blocking. In C, " +"it's more complex, (for one thing, you'll need to choose between the BSD " +"flavor ``O_NONBLOCK`` and the almost indistinguishable Posix flavor " +"``O_NDELAY``, which is completely different from ``TCP_NODELAY``), but it's " +"the exact same idea. You do this after creating the socket, but before using " +"it. (Actually, if you're nuts, you can switch back and forth.)" +msgstr "" + +#: ../Doc/howto/sockets.rst:327 +msgid "" +"The major mechanical difference is that ``send``, ``recv``, ``connect`` and " +"``accept`` can return without having done anything. You have (of course) a " +"number of choices. You can check return code and error codes and generally " +"drive yourself crazy. If you don't believe me, try it sometime. Your app " +"will grow large, buggy and suck CPU. So let's skip the brain-dead solutions " +"and do it right." +msgstr "" + +#: ../Doc/howto/sockets.rst:334 +msgid "Use ``select``." +msgstr "" + +#: ../Doc/howto/sockets.rst:336 +msgid "" +"In C, coding ``select`` is fairly complex. In Python, it's a piece of cake, " +"but it's close enough to the C version that if you understand ``select`` in " +"Python, you'll have little trouble with it in C::" +msgstr "" + +#: ../Doc/howto/sockets.rst:347 +msgid "" +"You pass ``select`` three lists: the first contains all sockets that you " +"might want to try reading; the second all the sockets you might want to try " +"writing to, and the last (normally left empty) those that you want to check " +"for errors. You should note that a socket can go into more than one list. " +"The ``select`` call is blocking, but you can give it a timeout. This is " +"generally a sensible thing to do - give it a nice long timeout (say a " +"minute) unless you have good reason to do otherwise." +msgstr "" + +#: ../Doc/howto/sockets.rst:355 +msgid "" +"In return, you will get three lists. They contain the sockets that are " +"actually readable, writable and in error. Each of these lists is a subset " +"(possibly empty) of the corresponding list you passed in." +msgstr "" + +#: ../Doc/howto/sockets.rst:359 +msgid "" +"If a socket is in the output readable list, you can be as-close-to-certain-" +"as-we-ever-get-in-this-business that a ``recv`` on that socket will return " +"*something*. Same idea for the writable list. You'll be able to send " +"*something*. Maybe not all you want to, but *something* is better than " +"nothing. (Actually, any reasonably healthy socket will return as writable - " +"it just means outbound network buffer space is available.)" +msgstr "" + +#: ../Doc/howto/sockets.rst:366 +msgid "" +"If you have a \"server\" socket, put it in the potential_readers list. If it " +"comes out in the readable list, your ``accept`` will (almost certainly) " +"work. If you have created a new socket to ``connect`` to someone else, put " +"it in the potential_writers list. If it shows up in the writable list, you " +"have a decent chance that it has connected." +msgstr "" + +#: ../Doc/howto/sockets.rst:372 +msgid "" +"Actually, ``select`` can be handy even with blocking sockets. It's one way " +"of determining whether you will block - the socket returns as readable when " +"there's something in the buffers. However, this still doesn't help with the " +"problem of determining whether the other end is done, or just busy with " +"something else." +msgstr "" + +#: ../Doc/howto/sockets.rst:377 +msgid "" +"**Portability alert**: On Unix, ``select`` works both with the sockets and " +"files. Don't try this on Windows. On Windows, ``select`` works with sockets " +"only. Also note that in C, many of the more advanced socket options are done " +"differently on Windows. In fact, on Windows I usually use threads (which " +"work very, very well) with my sockets." +msgstr "" + +#: ../Doc/howto/sorting.rst:4 +msgid "Sorting HOW TO" +msgstr "" + +#: ../Doc/howto/sorting.rst:6 +msgid "Andrew Dalke and Raymond Hettinger" +msgstr "" + +#: ../Doc/howto/sorting.rst:7 +msgid "0.1" +msgstr "" + +#: ../Doc/howto/sorting.rst:10 +msgid "" +"Python lists have a built-in :meth:`list.sort` method that modifies the list " +"in-place. There is also a :func:`sorted` built-in function that builds a " +"new sorted list from an iterable." +msgstr "" + +#: ../Doc/howto/sorting.rst:14 +msgid "" +"In this document, we explore the various techniques for sorting data using " +"Python." +msgstr "" + +#: ../Doc/howto/sorting.rst:18 +msgid "Sorting Basics" +msgstr "" + +#: ../Doc/howto/sorting.rst:20 +msgid "" +"A simple ascending sort is very easy: just call the :func:`sorted` function. " +"It returns a new sorted list::" +msgstr "" + +#: ../Doc/howto/sorting.rst:26 +msgid "" +"You can also use the :meth:`list.sort` method. It modifies the list in-place " +"(and returns *None* to avoid confusion). Usually it's less convenient than :" +"func:`sorted` - but if you don't need the original list, it's slightly more " +"efficient." +msgstr "" + +#: ../Doc/howto/sorting.rst:36 +msgid "" +"Another difference is that the :meth:`list.sort` method is only defined for " +"lists. In contrast, the :func:`sorted` function accepts any iterable." +msgstr "" + +#: ../Doc/howto/sorting.rst:43 +msgid "Key Functions" +msgstr "" + +#: ../Doc/howto/sorting.rst:45 +msgid "" +"Both :meth:`list.sort` and :func:`sorted` have a *key* parameter to specify " +"a function to be called on each list element prior to making comparisons." +msgstr "" + +#: ../Doc/howto/sorting.rst:48 +msgid "For example, here's a case-insensitive string comparison:" +msgstr "" + +#: ../Doc/howto/sorting.rst:53 +msgid "" +"The value of the *key* parameter should be a function that takes a single " +"argument and returns a key to use for sorting purposes. This technique is " +"fast because the key function is called exactly once for each input record." +msgstr "" + +#: ../Doc/howto/sorting.rst:57 +msgid "" +"A common pattern is to sort complex objects using some of the object's " +"indices as keys. For example:" +msgstr "" + +#: ../Doc/howto/sorting.rst:68 +msgid "" +"The same technique works for objects with named attributes. For example:" +msgstr "" + +#: ../Doc/howto/sorting.rst:87 +msgid "Operator Module Functions" +msgstr "" + +#: ../Doc/howto/sorting.rst:89 +msgid "" +"The key-function patterns shown above are very common, so Python provides " +"convenience functions to make accessor functions easier and faster. The :mod:" +"`operator` module has :func:`~operator.itemgetter`, :func:`~operator." +"attrgetter`, and a :func:`~operator.methodcaller` function." +msgstr "" + +#: ../Doc/howto/sorting.rst:94 +msgid "Using those functions, the above examples become simpler and faster:" +msgstr "" + +#: ../Doc/howto/sorting.rst:104 +msgid "" +"The operator module functions allow multiple levels of sorting. For example, " +"to sort by *grade* then by *age*:" +msgstr "" + +#: ../Doc/howto/sorting.rst:114 +msgid "Ascending and Descending" +msgstr "" + +#: ../Doc/howto/sorting.rst:116 +msgid "" +"Both :meth:`list.sort` and :func:`sorted` accept a *reverse* parameter with " +"a boolean value. This is used to flag descending sorts. For example, to get " +"the student data in reverse *age* order:" +msgstr "" + +#: ../Doc/howto/sorting.rst:127 +msgid "Sort Stability and Complex Sorts" +msgstr "" + +#: ../Doc/howto/sorting.rst:129 +msgid "" +"Sorts are guaranteed to be `stable `_\\. That means that when multiple records have " +"the same key, their original order is preserved." +msgstr "" + +#: ../Doc/howto/sorting.rst:137 +msgid "" +"Notice how the two records for *blue* retain their original order so that " +"``('blue', 1)`` is guaranteed to precede ``('blue', 2)``." +msgstr "" + +#: ../Doc/howto/sorting.rst:140 +msgid "" +"This wonderful property lets you build complex sorts in a series of sorting " +"steps. For example, to sort the student data by descending *grade* and then " +"ascending *age*, do the *age* sort first and then sort again using *grade*:" +msgstr "" + +#: ../Doc/howto/sorting.rst:148 +msgid "" +"The `Timsort `_ algorithm used in " +"Python does multiple sorts efficiently because it can take advantage of any " +"ordering already present in a dataset." +msgstr "" + +#: ../Doc/howto/sorting.rst:153 +msgid "The Old Way Using Decorate-Sort-Undecorate" +msgstr "" + +#: ../Doc/howto/sorting.rst:155 +msgid "This idiom is called Decorate-Sort-Undecorate after its three steps:" +msgstr "" + +#: ../Doc/howto/sorting.rst:157 +msgid "" +"First, the initial list is decorated with new values that control the sort " +"order." +msgstr "" + +#: ../Doc/howto/sorting.rst:159 +msgid "Second, the decorated list is sorted." +msgstr "" + +#: ../Doc/howto/sorting.rst:161 +msgid "" +"Finally, the decorations are removed, creating a list that contains only the " +"initial values in the new order." +msgstr "" + +#: ../Doc/howto/sorting.rst:164 +msgid "" +"For example, to sort the student data by *grade* using the DSU approach:" +msgstr "" + +#: ../Doc/howto/sorting.rst:171 +msgid "" +"This idiom works because tuples are compared lexicographically; the first " +"items are compared; if they are the same then the second items are compared, " +"and so on." +msgstr "" + +#: ../Doc/howto/sorting.rst:175 +msgid "" +"It is not strictly necessary in all cases to include the index *i* in the " +"decorated list, but including it gives two benefits:" +msgstr "" + +#: ../Doc/howto/sorting.rst:178 +msgid "" +"The sort is stable -- if two items have the same key, their order will be " +"preserved in the sorted list." +msgstr "" + +#: ../Doc/howto/sorting.rst:181 +msgid "" +"The original items do not have to be comparable because the ordering of the " +"decorated tuples will be determined by at most the first two items. So for " +"example the original list could contain complex numbers which cannot be " +"sorted directly." +msgstr "" + +#: ../Doc/howto/sorting.rst:186 +msgid "" +"Another name for this idiom is `Schwartzian transform `_\\, after Randal L. Schwartz, who " +"popularized it among Perl programmers." +msgstr "" + +#: ../Doc/howto/sorting.rst:190 +msgid "" +"Now that Python sorting provides key-functions, this technique is not often " +"needed." +msgstr "" + +#: ../Doc/howto/sorting.rst:194 +msgid "The Old Way Using the *cmp* Parameter" +msgstr "" + +#: ../Doc/howto/sorting.rst:196 +msgid "" +"Many constructs given in this HOWTO assume Python 2.4 or later. Before that, " +"there was no :func:`sorted` builtin and :meth:`list.sort` took no keyword " +"arguments. Instead, all of the Py2.x versions supported a *cmp* parameter to " +"handle user specified comparison functions." +msgstr "" + +#: ../Doc/howto/sorting.rst:201 +msgid "" +"In Py3.0, the *cmp* parameter was removed entirely (as part of a larger " +"effort to simplify and unify the language, eliminating the conflict between " +"rich comparisons and the :meth:`__cmp__` magic method)." +msgstr "" + +#: ../Doc/howto/sorting.rst:205 +msgid "" +"In Py2.x, sort allowed an optional function which can be called for doing " +"the comparisons. That function should take two arguments to be compared and " +"then return a negative value for less-than, return zero if they are equal, " +"or return a positive value for greater-than. For example, we can do:" +msgstr "" + +#: ../Doc/howto/sorting.rst:215 +msgid "Or you can reverse the order of comparison with:" +msgstr "" + +#: ../Doc/howto/sorting.rst:222 +msgid "" +"When porting code from Python 2.x to 3.x, the situation can arise when you " +"have the user supplying a comparison function and you need to convert that " +"to a key function. The following wrapper makes that easy to do::" +msgstr "" + +#: ../Doc/howto/sorting.rst:245 +msgid "To convert to a key function, just wrap the old comparison function:" +msgstr "" + +#: ../Doc/howto/sorting.rst:256 +msgid "" +"In Python 3.2, the :func:`functools.cmp_to_key` function was added to the :" +"mod:`functools` module in the standard library." +msgstr "" + +#: ../Doc/howto/sorting.rst:260 +msgid "Odd and Ends" +msgstr "" + +#: ../Doc/howto/sorting.rst:262 +msgid "" +"For locale aware sorting, use :func:`locale.strxfrm` for a key function or :" +"func:`locale.strcoll` for a comparison function." +msgstr "" + +#: ../Doc/howto/sorting.rst:265 +msgid "" +"The *reverse* parameter still maintains sort stability (so that records with " +"equal keys retain the original order). Interestingly, that effect can be " +"simulated without the parameter by using the builtin :func:`reversed` " +"function twice:" +msgstr "" + +#: ../Doc/howto/sorting.rst:277 +msgid "" +"The sort routines are guaranteed to use :meth:`__lt__` when making " +"comparisons between two objects. So, it is easy to add a standard sort order " +"to a class by defining an :meth:`__lt__` method::" +msgstr "" + +#: ../Doc/howto/sorting.rst:285 +msgid "" +"Key functions need not depend directly on the objects being sorted. A key " +"function can also access external resources. For instance, if the student " +"grades are stored in a dictionary, they can be used to sort a separate list " +"of student names:" +msgstr "" + +#: ../Doc/howto/unicode.rst:5 +msgid "Unicode HOWTO" +msgstr "" + +#: ../Doc/howto/unicode.rst:7 +msgid "1.12" +msgstr "" + +#: ../Doc/howto/unicode.rst:9 +msgid "" +"This HOWTO discusses Python support for Unicode, and explains various " +"problems that people commonly encounter when trying to work with Unicode." +msgstr "" + +#: ../Doc/howto/unicode.rst:14 +msgid "Introduction to Unicode" +msgstr "" + +#: ../Doc/howto/unicode.rst:17 +msgid "History of Character Codes" +msgstr "" + +#: ../Doc/howto/unicode.rst:19 +msgid "" +"In 1968, the American Standard Code for Information Interchange, better " +"known by its acronym ASCII, was standardized. ASCII defined numeric codes " +"for various characters, with the numeric values running from 0 to 127. For " +"example, the lowercase letter 'a' is assigned 97 as its code value." +msgstr "" + +#: ../Doc/howto/unicode.rst:24 +msgid "" +"ASCII was an American-developed standard, so it only defined unaccented " +"characters. There was an 'e', but no 'é' or 'Í'. This meant that languages " +"which required accented characters couldn't be faithfully represented in " +"ASCII. (Actually the missing accents matter for English, too, which contains " +"words such as 'naïve' and 'café', and some publications have house styles " +"which require spellings such as 'coöperate'.)" +msgstr "" + +#: ../Doc/howto/unicode.rst:31 +msgid "" +"For a while people just wrote programs that didn't display accents. In the " +"mid-1980s an Apple II BASIC program written by a French speaker might have " +"lines like these::" +msgstr "" + +#: ../Doc/howto/unicode.rst:38 +msgid "" +"Those messages should contain accents (terminée, paramètre, enregistrés) and " +"they just look wrong to someone who can read French." +msgstr "" + +#: ../Doc/howto/unicode.rst:41 +msgid "" +"In the 1980s, almost all personal computers were 8-bit, meaning that bytes " +"could hold values ranging from 0 to 255. ASCII codes only went up to 127, " +"so some machines assigned values between 128 and 255 to accented " +"characters. Different machines had different codes, however, which led to " +"problems exchanging files. Eventually various commonly used sets of values " +"for the 128--255 range emerged. Some were true standards, defined by the " +"International Standards Organization, and some were *de facto* conventions " +"that were invented by one company or another and managed to catch on." +msgstr "" + +#: ../Doc/howto/unicode.rst:50 +msgid "" +"255 characters aren't very many. For example, you can't fit both the " +"accented characters used in Western Europe and the Cyrillic alphabet used " +"for Russian into the 128--255 range because there are more than 128 such " +"characters." +msgstr "" + +#: ../Doc/howto/unicode.rst:54 +msgid "" +"You could write files using different codes (all your Russian files in a " +"coding system called KOI8, all your French files in a different coding " +"system called Latin1), but what if you wanted to write a French document " +"that quotes some Russian text? In the 1980s people began to want to solve " +"this problem, and the Unicode standardization effort began." +msgstr "" + +#: ../Doc/howto/unicode.rst:60 +msgid "" +"Unicode started out using 16-bit characters instead of 8-bit characters. 16 " +"bits means you have 2^16 = 65,536 distinct values available, making it " +"possible to represent many different characters from many different " +"alphabets; an initial goal was to have Unicode contain the alphabets for " +"every single human language. It turns out that even 16 bits isn't enough to " +"meet that goal, and the modern Unicode specification uses a wider range of " +"codes, 0 through 1,114,111 ( ``0x10FFFF`` in base 16)." +msgstr "" + +#: ../Doc/howto/unicode.rst:68 +msgid "" +"There's a related ISO standard, ISO 10646. Unicode and ISO 10646 were " +"originally separate efforts, but the specifications were merged with the 1.1 " +"revision of Unicode." +msgstr "" + +#: ../Doc/howto/unicode.rst:72 +msgid "" +"(This discussion of Unicode's history is highly simplified. The precise " +"historical details aren't necessary for understanding how to use Unicode " +"effectively, but if you're curious, consult the Unicode consortium site " +"listed in the References or the `Wikipedia entry for Unicode `_ for more information.)" +msgstr "" + +#: ../Doc/howto/unicode.rst:81 +msgid "Definitions" +msgstr "" + +#: ../Doc/howto/unicode.rst:83 +msgid "" +"A **character** is the smallest possible component of a text. 'A', 'B', " +"'C', etc., are all different characters. So are 'È' and 'Í'. Characters " +"are abstractions, and vary depending on the language or context you're " +"talking about. For example, the symbol for ohms (Ω) is usually drawn much " +"like the capital letter omega (Ω) in the Greek alphabet (they may even be " +"the same in some fonts), but these are two different characters that have " +"different meanings." +msgstr "" + +#: ../Doc/howto/unicode.rst:91 +msgid "" +"The Unicode standard describes how characters are represented by **code " +"points**. A code point is an integer value, usually denoted in base 16. In " +"the standard, a code point is written using the notation ``U+12CA`` to mean " +"the character with value ``0x12ca`` (4,810 decimal). The Unicode standard " +"contains a lot of tables listing characters and their corresponding code " +"points:" +msgstr "" + +#: ../Doc/howto/unicode.rst:105 +msgid "" +"Strictly, these definitions imply that it's meaningless to say 'this is " +"character ``U+12CA``'. ``U+12CA`` is a code point, which represents some " +"particular character; in this case, it represents the character 'ETHIOPIC " +"SYLLABLE WI'. In informal contexts, this distinction between code points " +"and characters will sometimes be forgotten." +msgstr "" + +#: ../Doc/howto/unicode.rst:111 +msgid "" +"A character is represented on a screen or on paper by a set of graphical " +"elements that's called a **glyph**. The glyph for an uppercase A, for " +"example, is two diagonal strokes and a horizontal stroke, though the exact " +"details will depend on the font being used. Most Python code doesn't need " +"to worry about glyphs; figuring out the correct glyph to display is " +"generally the job of a GUI toolkit or a terminal's font renderer." +msgstr "" + +#: ../Doc/howto/unicode.rst:120 +msgid "Encodings" +msgstr "" + +#: ../Doc/howto/unicode.rst:122 +msgid "" +"To summarize the previous section: a Unicode string is a sequence of code " +"points, which are numbers from 0 through ``0x10FFFF`` (1,114,111 decimal). " +"This sequence needs to be represented as a set of bytes (meaning, values " +"from 0 through 255) in memory. The rules for translating a Unicode string " +"into a sequence of bytes are called an **encoding**." +msgstr "" + +#: ../Doc/howto/unicode.rst:128 +msgid "" +"The first encoding you might think of is an array of 32-bit integers. In " +"this representation, the string \"Python\" would look like this:" +msgstr "" + +#: ../Doc/howto/unicode.rst:137 +msgid "" +"This representation is straightforward but using it presents a number of " +"problems." +msgstr "" + +#: ../Doc/howto/unicode.rst:140 +msgid "It's not portable; different processors order the bytes differently." +msgstr "" + +#: ../Doc/howto/unicode.rst:142 +msgid "" +"It's very wasteful of space. In most texts, the majority of the code points " +"are less than 127, or less than 255, so a lot of space is occupied by " +"``0x00`` bytes. The above string takes 24 bytes compared to the 6 bytes " +"needed for an ASCII representation. Increased RAM usage doesn't matter too " +"much (desktop computers have gigabytes of RAM, and strings aren't usually " +"that large), but expanding our usage of disk and network bandwidth by a " +"factor of 4 is intolerable." +msgstr "" + +#: ../Doc/howto/unicode.rst:150 +msgid "" +"It's not compatible with existing C functions such as ``strlen()``, so a new " +"family of wide string functions would need to be used." +msgstr "" + +#: ../Doc/howto/unicode.rst:153 +msgid "" +"Many Internet standards are defined in terms of textual data, and can't " +"handle content with embedded zero bytes." +msgstr "" + +#: ../Doc/howto/unicode.rst:156 +msgid "" +"Generally people don't use this encoding, instead choosing other encodings " +"that are more efficient and convenient. UTF-8 is probably the most commonly " +"supported encoding; it will be discussed below." +msgstr "" + +#: ../Doc/howto/unicode.rst:160 +msgid "" +"Encodings don't have to handle every possible Unicode character, and most " +"encodings don't. The rules for converting a Unicode string into the ASCII " +"encoding, for example, are simple; for each code point:" +msgstr "" + +#: ../Doc/howto/unicode.rst:164 +msgid "" +"If the code point is < 128, each byte is the same as the value of the code " +"point." +msgstr "" + +#: ../Doc/howto/unicode.rst:167 +msgid "" +"If the code point is 128 or greater, the Unicode string can't be represented " +"in this encoding. (Python raises a :exc:`UnicodeEncodeError` exception in " +"this case.)" +msgstr "" + +#: ../Doc/howto/unicode.rst:171 +msgid "" +"Latin-1, also known as ISO-8859-1, is a similar encoding. Unicode code " +"points 0--255 are identical to the Latin-1 values, so converting to this " +"encoding simply requires converting code points to byte values; if a code " +"point larger than 255 is encountered, the string can't be encoded into " +"Latin-1." +msgstr "" + +#: ../Doc/howto/unicode.rst:176 +msgid "" +"Encodings don't have to be simple one-to-one mappings like Latin-1. " +"Consider IBM's EBCDIC, which was used on IBM mainframes. Letter values " +"weren't in one block: 'a' through 'i' had values from 129 to 137, but 'j' " +"through 'r' were 145 through 153. If you wanted to use EBCDIC as an " +"encoding, you'd probably use some sort of lookup table to perform the " +"conversion, but this is largely an internal detail." +msgstr "" + +#: ../Doc/howto/unicode.rst:183 +msgid "" +"UTF-8 is one of the most commonly used encodings. UTF stands for \"Unicode " +"Transformation Format\", and the '8' means that 8-bit numbers are used in " +"the encoding. (There are also a UTF-16 and UTF-32 encodings, but they are " +"less frequently used than UTF-8.) UTF-8 uses the following rules:" +msgstr "" + +#: ../Doc/howto/unicode.rst:188 +msgid "" +"If the code point is < 128, it's represented by the corresponding byte value." +msgstr "" + +#: ../Doc/howto/unicode.rst:189 +msgid "" +"If the code point is >= 128, it's turned into a sequence of two, three, or " +"four bytes, where each byte of the sequence is between 128 and 255." +msgstr "" + +#: ../Doc/howto/unicode.rst:192 +msgid "UTF-8 has several convenient properties:" +msgstr "" + +#: ../Doc/howto/unicode.rst:194 +msgid "It can handle any Unicode code point." +msgstr "" + +#: ../Doc/howto/unicode.rst:195 +msgid "" +"A Unicode string is turned into a sequence of bytes containing no embedded " +"zero bytes. This avoids byte-ordering issues, and means UTF-8 strings can " +"be processed by C functions such as ``strcpy()`` and sent through protocols " +"that can't handle zero bytes." +msgstr "" + +#: ../Doc/howto/unicode.rst:199 +msgid "A string of ASCII text is also valid UTF-8 text." +msgstr "" + +#: ../Doc/howto/unicode.rst:200 +msgid "" +"UTF-8 is fairly compact; the majority of commonly used characters can be " +"represented with one or two bytes." +msgstr "" + +#: ../Doc/howto/unicode.rst:202 +msgid "" +"If bytes are corrupted or lost, it's possible to determine the start of the " +"next UTF-8-encoded code point and resynchronize. It's also unlikely that " +"random 8-bit data will look like valid UTF-8." +msgstr "" + +#: ../Doc/howto/unicode.rst:211 +msgid "" +"The `Unicode Consortium site `_ has character " +"charts, a glossary, and PDF versions of the Unicode specification. Be " +"prepared for some difficult reading. `A chronology `_ of the origin and development of Unicode is also available on " +"the site." +msgstr "" + +#: ../Doc/howto/unicode.rst:216 +msgid "" +"To help understand the standard, Jukka Korpela has written `an introductory " +"guide `_ to reading the " +"Unicode character tables." +msgstr "" + +#: ../Doc/howto/unicode.rst:220 +msgid "" +"Another `good introductory article `_ was written by Joel Spolsky. If this introduction didn't " +"make things clear to you, you should try reading this alternate article " +"before continuing." +msgstr "" + +#: ../Doc/howto/unicode.rst:225 +msgid "" +"Wikipedia entries are often helpful; see the entries for \"`character " +"encoding `_\" and `UTF-8 " +"`_, for example." +msgstr "" + +#: ../Doc/howto/unicode.rst:231 +msgid "Python's Unicode Support" +msgstr "" + +#: ../Doc/howto/unicode.rst:233 +msgid "" +"Now that you've learned the rudiments of Unicode, we can look at Python's " +"Unicode features." +msgstr "" + +#: ../Doc/howto/unicode.rst:237 +msgid "The String Type" +msgstr "" + +#: ../Doc/howto/unicode.rst:239 +msgid "" +"Since Python 3.0, the language features a :class:`str` type that contain " +"Unicode characters, meaning any string created using ``\"unicode rocks!\"``, " +"``'unicode rocks!'``, or the triple-quoted string syntax is stored as " +"Unicode." +msgstr "" + +#: ../Doc/howto/unicode.rst:243 +msgid "" +"The default encoding for Python source code is UTF-8, so you can simply " +"include a Unicode character in a string literal::" +msgstr "" + +#: ../Doc/howto/unicode.rst:253 +msgid "" +"You can use a different encoding from UTF-8 by putting a specially-formatted " +"comment as the first or second line of the source code::" +msgstr "" + +#: ../Doc/howto/unicode.rst:258 +msgid "" +"Side note: Python 3 also supports using Unicode characters in identifiers::" +msgstr "" + +#: ../Doc/howto/unicode.rst:264 +msgid "" +"If you can't enter a particular character in your editor or want to keep the " +"source code ASCII-only for some reason, you can also use escape sequences in " +"string literals. (Depending on your system, you may see the actual capital-" +"delta glyph instead of a \\u escape.) ::" +msgstr "" + +#: ../Doc/howto/unicode.rst:276 +msgid "" +"In addition, one can create a string using the :func:`~bytes.decode` method " +"of :class:`bytes`. This method takes an *encoding* argument, such as " +"``UTF-8``, and optionally an *errors* argument." +msgstr "" + +#: ../Doc/howto/unicode.rst:280 +msgid "" +"The *errors* argument specifies the response when the input string can't be " +"converted according to the encoding's rules. Legal values for this argument " +"are ``'strict'`` (raise a :exc:`UnicodeDecodeError` exception), " +"``'replace'`` (use ``U+FFFD``, ``REPLACEMENT CHARACTER``), ``'ignore'`` " +"(just leave the character out of the Unicode result), or " +"``'backslashreplace'`` (inserts a ``\\xNN`` escape sequence). The following " +"examples show the differences::" +msgstr "" + +#: ../Doc/howto/unicode.rst:300 +msgid "" +"Encodings are specified as strings containing the encoding's name. Python " +"3.2 comes with roughly 100 different encodings; see the Python Library " +"Reference at :ref:`standard-encodings` for a list. Some encodings have " +"multiple names; for example, ``'latin-1'``, ``'iso_8859_1'`` and ``'8859``' " +"are all synonyms for the same encoding." +msgstr "" + +#: ../Doc/howto/unicode.rst:306 +msgid "" +"One-character Unicode strings can also be created with the :func:`chr` built-" +"in function, which takes integers and returns a Unicode string of length 1 " +"that contains the corresponding code point. The reverse operation is the " +"built-in :func:`ord` function that takes a one-character Unicode string and " +"returns the code point value::" +msgstr "" + +#: ../Doc/howto/unicode.rst:318 +msgid "Converting to Bytes" +msgstr "" + +#: ../Doc/howto/unicode.rst:320 +msgid "" +"The opposite method of :meth:`bytes.decode` is :meth:`str.encode`, which " +"returns a :class:`bytes` representation of the Unicode string, encoded in " +"the requested *encoding*." +msgstr "" + +#: ../Doc/howto/unicode.rst:324 +msgid "" +"The *errors* parameter is the same as the parameter of the :meth:`~bytes." +"decode` method but supports a few more possible handlers. As well as " +"``'strict'``, ``'ignore'``, and ``'replace'`` (which in this case inserts a " +"question mark instead of the unencodable character), there is also " +"``'xmlcharrefreplace'`` (inserts an XML character reference), " +"``backslashreplace`` (inserts a ``\\uNNNN`` escape sequence) and " +"``namereplace`` (inserts a ``\\N{...}`` escape sequence)." +msgstr "" + +#: ../Doc/howto/unicode.rst:332 +msgid "The following example shows the different results::" +msgstr "" + +#: ../Doc/howto/unicode.rst:353 +msgid "" +"The low-level routines for registering and accessing the available encodings " +"are found in the :mod:`codecs` module. Implementing new encodings also " +"requires understanding the :mod:`codecs` module. However, the encoding and " +"decoding functions returned by this module are usually more low-level than " +"is comfortable, and writing new encodings is a specialized task, so the " +"module won't be covered in this HOWTO." +msgstr "" + +#: ../Doc/howto/unicode.rst:362 +msgid "Unicode Literals in Python Source Code" +msgstr "" + +#: ../Doc/howto/unicode.rst:364 +msgid "" +"In Python source code, specific Unicode code points can be written using the " +"``\\u`` escape sequence, which is followed by four hex digits giving the " +"code point. The ``\\U`` escape sequence is similar, but expects eight hex " +"digits, not four::" +msgstr "" + +#: ../Doc/howto/unicode.rst:376 +msgid "" +"Using escape sequences for code points greater than 127 is fine in small " +"doses, but becomes an annoyance if you're using many accented characters, as " +"you would in a program with messages in French or some other accent-using " +"language. You can also assemble strings using the :func:`chr` built-in " +"function, but this is even more tedious." +msgstr "" + +#: ../Doc/howto/unicode.rst:382 +msgid "" +"Ideally, you'd want to be able to write literals in your language's natural " +"encoding. You could then edit Python source code with your favorite editor " +"which would display the accented characters naturally, and have the right " +"characters used at runtime." +msgstr "" + +#: ../Doc/howto/unicode.rst:387 +msgid "" +"Python supports writing source code in UTF-8 by default, but you can use " +"almost any encoding if you declare the encoding being used. This is done by " +"including a special comment as either the first or second line of the source " +"file::" +msgstr "" + +#: ../Doc/howto/unicode.rst:397 +msgid "" +"The syntax is inspired by Emacs's notation for specifying variables local to " +"a file. Emacs supports many different variables, but Python only supports " +"'coding'. The ``-*-`` symbols indicate to Emacs that the comment is " +"special; they have no significance to Python but are a convention. Python " +"looks for ``coding: name`` or ``coding=name`` in the comment." +msgstr "" + +#: ../Doc/howto/unicode.rst:403 +msgid "" +"If you don't include such a comment, the default encoding used will be UTF-8 " +"as already mentioned. See also :pep:`263` for more information." +msgstr "" + +#: ../Doc/howto/unicode.rst:408 +msgid "Unicode Properties" +msgstr "" + +#: ../Doc/howto/unicode.rst:410 +msgid "" +"The Unicode specification includes a database of information about code " +"points. For each defined code point, the information includes the " +"character's name, its category, the numeric value if applicable (Unicode has " +"characters representing the Roman numerals and fractions such as one-third " +"and four-fifths). There are also properties related to the code point's use " +"in bidirectional text and other display-related properties." +msgstr "" + +#: ../Doc/howto/unicode.rst:417 +msgid "" +"The following program displays some information about several characters, " +"and prints the numeric value of one particular character::" +msgstr "" + +#: ../Doc/howto/unicode.rst:431 +msgid "When run, this prints:" +msgstr "" + +#: ../Doc/howto/unicode.rst:442 +msgid "" +"The category codes are abbreviations describing the nature of the character. " +"These are grouped into categories such as \"Letter\", \"Number\", " +"\"Punctuation\", or \"Symbol\", which in turn are broken up into " +"subcategories. To take the codes from the above output, ``'Ll'`` means " +"'Letter, lowercase', ``'No'`` means \"Number, other\", ``'Mn'`` is \"Mark, " +"nonspacing\", and ``'So'`` is \"Symbol, other\". See `the General Category " +"Values section of the Unicode Character Database documentation `_ for a list of category " +"codes." +msgstr "" + +#: ../Doc/howto/unicode.rst:453 +msgid "Unicode Regular Expressions" +msgstr "" + +#: ../Doc/howto/unicode.rst:455 +msgid "" +"The regular expressions supported by the :mod:`re` module can be provided " +"either as bytes or strings. Some of the special character sequences such as " +"``\\d`` and ``\\w`` have different meanings depending on whether the pattern " +"is supplied as bytes or a string. For example, ``\\d`` will match the " +"characters ``[0-9]`` in bytes but in strings will match any character that's " +"in the ``'Nd'`` category." +msgstr "" + +#: ../Doc/howto/unicode.rst:462 +msgid "" +"The string in this example has the number 57 written in both Thai and Arabic " +"numerals::" +msgstr "" + +#: ../Doc/howto/unicode.rst:472 +msgid "" +"When executed, ``\\d+`` will match the Thai numerals and print them out. If " +"you supply the :const:`re.ASCII` flag to :func:`~re.compile`, ``\\d+`` will " +"match the substring \"57\" instead." +msgstr "" + +#: ../Doc/howto/unicode.rst:476 +msgid "" +"Similarly, ``\\w`` matches a wide variety of Unicode characters but only " +"``[a-zA-Z0-9_]`` in bytes or if :const:`re.ASCII` is supplied, and ``\\s`` " +"will match either Unicode whitespace characters or ``[ \\t\\n\\r\\f\\v]``." +msgstr "" + +#: ../Doc/howto/unicode.rst:487 +msgid "Some good alternative discussions of Python's Unicode support are:" +msgstr "" + +#: ../Doc/howto/unicode.rst:489 +msgid "" +"`Processing Text Files in Python 3 `_, by Nick Coghlan." +msgstr "" + +#: ../Doc/howto/unicode.rst:490 +msgid "" +"`Pragmatic Unicode `_, a PyCon " +"2012 presentation by Ned Batchelder." +msgstr "" + +#: ../Doc/howto/unicode.rst:492 +msgid "" +"The :class:`str` type is described in the Python library reference at :ref:" +"`textseq`." +msgstr "" + +#: ../Doc/howto/unicode.rst:495 +msgid "The documentation for the :mod:`unicodedata` module." +msgstr "" + +#: ../Doc/howto/unicode.rst:497 +msgid "The documentation for the :mod:`codecs` module." +msgstr "" + +#: ../Doc/howto/unicode.rst:499 +msgid "" +"Marc-André Lemburg gave `a presentation titled \"Python and Unicode\" (PDF " +"slides) `_ at " +"EuroPython 2002. The slides are an excellent overview of the design of " +"Python 2's Unicode features (where the Unicode string type is called " +"``unicode`` and literals start with ``u``)." +msgstr "" + +#: ../Doc/howto/unicode.rst:507 +msgid "Reading and Writing Unicode Data" +msgstr "" + +#: ../Doc/howto/unicode.rst:509 +msgid "" +"Once you've written some code that works with Unicode data, the next problem " +"is input/output. How do you get Unicode strings into your program, and how " +"do you convert Unicode into a form suitable for storage or transmission?" +msgstr "" + +#: ../Doc/howto/unicode.rst:513 +msgid "" +"It's possible that you may not need to do anything depending on your input " +"sources and output destinations; you should check whether the libraries used " +"in your application support Unicode natively. XML parsers often return " +"Unicode data, for example. Many relational databases also support Unicode-" +"valued columns and can return Unicode values from an SQL query." +msgstr "" + +#: ../Doc/howto/unicode.rst:519 +msgid "" +"Unicode data is usually converted to a particular encoding before it gets " +"written to disk or sent over a socket. It's possible to do all the work " +"yourself: open a file, read an 8-bit bytes object from it, and convert the " +"bytes with ``bytes.decode(encoding)``. However, the manual approach is not " +"recommended." +msgstr "" + +#: ../Doc/howto/unicode.rst:524 +msgid "" +"One problem is the multi-byte nature of encodings; one Unicode character can " +"be represented by several bytes. If you want to read the file in arbitrary-" +"sized chunks (say, 1024 or 4096 bytes), you need to write error-handling " +"code to catch the case where only part of the bytes encoding a single " +"Unicode character are read at the end of a chunk. One solution would be to " +"read the entire file into memory and then perform the decoding, but that " +"prevents you from working with files that are extremely large; if you need " +"to read a 2 GiB file, you need 2 GiB of RAM. (More, really, since for at " +"least a moment you'd need to have both the encoded string and its Unicode " +"version in memory.)" +msgstr "" + +#: ../Doc/howto/unicode.rst:534 +msgid "" +"The solution would be to use the low-level decoding interface to catch the " +"case of partial coding sequences. The work of implementing this has already " +"been done for you: the built-in :func:`open` function can return a file-like " +"object that assumes the file's contents are in a specified encoding and " +"accepts Unicode parameters for methods such as :meth:`~io.TextIOBase.read` " +"and :meth:`~io.TextIOBase.write`. This works through :func:`open`\\'s " +"*encoding* and *errors* parameters which are interpreted just like those in :" +"meth:`str.encode` and :meth:`bytes.decode`." +msgstr "" + +#: ../Doc/howto/unicode.rst:543 +msgid "Reading Unicode from a file is therefore simple::" +msgstr "" + +#: ../Doc/howto/unicode.rst:549 +msgid "" +"It's also possible to open files in update mode, allowing both reading and " +"writing::" +msgstr "" + +#: ../Doc/howto/unicode.rst:557 +msgid "" +"The Unicode character ``U+FEFF`` is used as a byte-order mark (BOM), and is " +"often written as the first character of a file in order to assist with " +"autodetection of the file's byte ordering. Some encodings, such as UTF-16, " +"expect a BOM to be present at the start of a file; when such an encoding is " +"used, the BOM will be automatically written as the first character and will " +"be silently dropped when the file is read. There are variants of these " +"encodings, such as 'utf-16-le' and 'utf-16-be' for little-endian and big-" +"endian encodings, that specify one particular byte ordering and don't skip " +"the BOM." +msgstr "" + +#: ../Doc/howto/unicode.rst:566 +msgid "" +"In some areas, it is also convention to use a \"BOM\" at the start of UTF-8 " +"encoded files; the name is misleading since UTF-8 is not byte-order " +"dependent. The mark simply announces that the file is encoded in UTF-8. Use " +"the 'utf-8-sig' codec to automatically skip the mark if present for reading " +"such files." +msgstr "" + +#: ../Doc/howto/unicode.rst:574 +msgid "Unicode filenames" +msgstr "" + +#: ../Doc/howto/unicode.rst:576 +msgid "" +"Most of the operating systems in common use today support filenames that " +"contain arbitrary Unicode characters. Usually this is implemented by " +"converting the Unicode string into some encoding that varies depending on " +"the system. For example, Mac OS X uses UTF-8 while Windows uses a " +"configurable encoding; on Windows, Python uses the name \"mbcs\" to refer to " +"whatever the currently configured encoding is. On Unix systems, there will " +"only be a filesystem encoding if you've set the ``LANG`` or ``LC_CTYPE`` " +"environment variables; if you haven't, the default encoding is UTF-8." +msgstr "" + +#: ../Doc/howto/unicode.rst:585 +msgid "" +"The :func:`sys.getfilesystemencoding` function returns the encoding to use " +"on your current system, in case you want to do the encoding manually, but " +"there's not much reason to bother. When opening a file for reading or " +"writing, you can usually just provide the Unicode string as the filename, " +"and it will be automatically converted to the right encoding for you::" +msgstr "" + +#: ../Doc/howto/unicode.rst:595 +msgid "" +"Functions in the :mod:`os` module such as :func:`os.stat` will also accept " +"Unicode filenames." +msgstr "" + +#: ../Doc/howto/unicode.rst:598 +msgid "" +"The :func:`os.listdir` function returns filenames and raises an issue: " +"should it return the Unicode version of filenames, or should it return bytes " +"containing the encoded versions? :func:`os.listdir` will do both, depending " +"on whether you provided the directory path as bytes or a Unicode string. If " +"you pass a Unicode string as the path, filenames will be decoded using the " +"filesystem's encoding and a list of Unicode strings will be returned, while " +"passing a byte path will return the filenames as bytes. For example, " +"assuming the default filesystem encoding is UTF-8, running the following " +"program::" +msgstr "" + +#: ../Doc/howto/unicode.rst:616 +msgid "will produce the following output:" +msgstr "" + +#: ../Doc/howto/unicode.rst:624 +msgid "" +"The first list contains UTF-8-encoded filenames, and the second list " +"contains the Unicode versions." +msgstr "" + +#: ../Doc/howto/unicode.rst:627 +msgid "" +"Note that on most occasions, the Unicode APIs should be used. The bytes " +"APIs should only be used on systems where undecodable file names can be " +"present, i.e. Unix systems." +msgstr "" + +#: ../Doc/howto/unicode.rst:633 +msgid "Tips for Writing Unicode-aware Programs" +msgstr "" + +#: ../Doc/howto/unicode.rst:635 +msgid "" +"This section provides some suggestions on writing software that deals with " +"Unicode." +msgstr "" + +#: ../Doc/howto/unicode.rst:638 +msgid "The most important tip is:" +msgstr "" + +#: ../Doc/howto/unicode.rst:640 +msgid "" +"Software should only work with Unicode strings internally, decoding the " +"input data as soon as possible and encoding the output only at the end." +msgstr "" + +#: ../Doc/howto/unicode.rst:643 +msgid "" +"If you attempt to write processing functions that accept both Unicode and " +"byte strings, you will find your program vulnerable to bugs wherever you " +"combine the two different kinds of strings. There is no automatic encoding " +"or decoding: if you do e.g. ``str + bytes``, a :exc:`TypeError` will be " +"raised." +msgstr "" + +#: ../Doc/howto/unicode.rst:648 +msgid "" +"When using data coming from a web browser or some other untrusted source, a " +"common technique is to check for illegal characters in a string before using " +"the string in a generated command line or storing it in a database. If " +"you're doing this, be careful to check the decoded string, not the encoded " +"bytes data; some encodings may have interesting properties, such as not " +"being bijective or not being fully ASCII-compatible. This is especially " +"true if the input data also specifies the encoding, since the attacker can " +"then choose a clever way to hide malicious text in the encoded bytestream." +msgstr "" + +#: ../Doc/howto/unicode.rst:659 +msgid "Converting Between File Encodings" +msgstr "" + +#: ../Doc/howto/unicode.rst:661 +msgid "" +"The :class:`~codecs.StreamRecoder` class can transparently convert between " +"encodings, taking a stream that returns data in encoding #1 and behaving " +"like a stream returning data in encoding #2." +msgstr "" + +#: ../Doc/howto/unicode.rst:665 +msgid "" +"For example, if you have an input file *f* that's in Latin-1, you can wrap " +"it with a :class:`~codecs.StreamRecoder` to return bytes encoded in UTF-8::" +msgstr "" + +#: ../Doc/howto/unicode.rst:679 +msgid "Files in an Unknown Encoding" +msgstr "" + +#: ../Doc/howto/unicode.rst:681 +msgid "" +"What can you do if you need to make a change to a file, but don't know the " +"file's encoding? If you know the encoding is ASCII-compatible and only want " +"to examine or modify the ASCII parts, you can open the file with the " +"``surrogateescape`` error handler::" +msgstr "" + +#: ../Doc/howto/unicode.rst:695 +msgid "" +"The ``surrogateescape`` error handler will decode any non-ASCII bytes as " +"code points in the Unicode Private Use Area ranging from U+DC80 to U+DCFF. " +"These private code points will then be turned back into the same bytes when " +"the ``surrogateescape`` error handler is used when encoding the data and " +"writing it back out." +msgstr "" + +#: ../Doc/howto/unicode.rst:705 +msgid "" +"One section of `Mastering Python 3 Input/Output `_, a PyCon 2010 talk by David " +"Beazley, discusses text processing and binary data handling." +msgstr "" + +#: ../Doc/howto/unicode.rst:709 +msgid "" +"The `PDF slides for Marc-André Lemburg's presentation \"Writing Unicode-" +"aware Applications in Python\" `_ discuss questions of " +"character encodings as well as how to internationalize and localize an " +"application. These slides cover Python 2.x only." +msgstr "" + +#: ../Doc/howto/unicode.rst:715 +msgid "" +"`The Guts of Unicode in Python `_ is a PyCon 2013 talk by Benjamin Peterson that " +"discusses the internal Unicode representation in Python 3.3." +msgstr "" + +#: ../Doc/howto/unicode.rst:722 +msgid "Acknowledgements" +msgstr "" + +#: ../Doc/howto/unicode.rst:724 +msgid "" +"The initial draft of this document was written by Andrew Kuchling. It has " +"since been revised further by Alexander Belopolsky, Georg Brandl, Andrew " +"Kuchling, and Ezio Melotti." +msgstr "" + +#: ../Doc/howto/unicode.rst:728 +msgid "" +"Thanks to the following people who have noted errors or offered suggestions " +"on this article: Éric Araujo, Nicholas Bastin, Nick Coghlan, Marius " +"Gedminas, Kent Johnson, Ken Krugler, Marc-André Lemburg, Martin von Löwis, " +"Terry J. Reedy, Chad Whitacre." +msgstr "" + +#: ../Doc/howto/urllib2.rst:5 +msgid "HOWTO Fetch Internet Resources Using The urllib Package" +msgstr "" + +#: ../Doc/howto/urllib2.rst:7 +msgid "`Michael Foord `_" +msgstr "" + +#: ../Doc/howto/urllib2.rst:11 +msgid "" +"There is a French translation of an earlier revision of this HOWTO, " +"available at `urllib2 - Le Manuel manquant `_." +msgstr "" + +#: ../Doc/howto/urllib2.rst:0 +msgid "Related Articles" +msgstr "" + +#: ../Doc/howto/urllib2.rst:22 +msgid "" +"You may also find useful the following article on fetching web resources " +"with Python:" +msgstr "" + +#: ../Doc/howto/urllib2.rst:25 +msgid "" +"`Basic Authentication `_" +msgstr "" + +#: ../Doc/howto/urllib2.rst:27 +msgid "A tutorial on *Basic Authentication*, with examples in Python." +msgstr "" + +#: ../Doc/howto/urllib2.rst:29 +msgid "" +"**urllib.request** is a Python module for fetching URLs (Uniform Resource " +"Locators). It offers a very simple interface, in the form of the *urlopen* " +"function. This is capable of fetching URLs using a variety of different " +"protocols. It also offers a slightly more complex interface for handling " +"common situations - like basic authentication, cookies, proxies and so on. " +"These are provided by objects called handlers and openers." +msgstr "" + +#: ../Doc/howto/urllib2.rst:36 +msgid "" +"urllib.request supports fetching URLs for many \"URL schemes\" (identified " +"by the string before the \":\" in URL - for example \"ftp\" is the URL " +"scheme of \"ftp://python.org/\") using their associated network protocols (e." +"g. FTP, HTTP). This tutorial focuses on the most common case, HTTP." +msgstr "" + +#: ../Doc/howto/urllib2.rst:41 +msgid "" +"For straightforward situations *urlopen* is very easy to use. But as soon as " +"you encounter errors or non-trivial cases when opening HTTP URLs, you will " +"need some understanding of the HyperText Transfer Protocol. The most " +"comprehensive and authoritative reference to HTTP is :rfc:`2616`. This is a " +"technical document and not intended to be easy to read. This HOWTO aims to " +"illustrate using *urllib*, with enough detail about HTTP to help you " +"through. It is not intended to replace the :mod:`urllib.request` docs, but " +"is supplementary to them." +msgstr "" + +#: ../Doc/howto/urllib2.rst:51 +msgid "Fetching URLs" +msgstr "" + +#: ../Doc/howto/urllib2.rst:53 +msgid "The simplest way to use urllib.request is as follows::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:59 +msgid "" +"If you wish to retrieve a resource via URL and store it in a temporary " +"location, you can do so via the :func:`~urllib.request.urlretrieve` " +"function::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:66 +msgid "" +"Many uses of urllib will be that simple (note that instead of an 'http:' URL " +"we could have used a URL starting with 'ftp:', 'file:', etc.). However, " +"it's the purpose of this tutorial to explain the more complicated cases, " +"concentrating on HTTP." +msgstr "" + +#: ../Doc/howto/urllib2.rst:71 +msgid "" +"HTTP is based on requests and responses - the client makes requests and " +"servers send responses. urllib.request mirrors this with a ``Request`` " +"object which represents the HTTP request you are making. In its simplest " +"form you create a Request object that specifies the URL you want to fetch. " +"Calling ``urlopen`` with this Request object returns a response object for " +"the URL requested. This response is a file-like object, which means you can " +"for example call ``.read()`` on the response::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:85 +msgid "" +"Note that urllib.request makes use of the same Request interface to handle " +"all URL schemes. For example, you can make an FTP request like so::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:90 +msgid "" +"In the case of HTTP, there are two extra things that Request objects allow " +"you to do: First, you can pass data to be sent to the server. Second, you " +"can pass extra information (\"metadata\") *about* the data or the about " +"request itself, to the server - this information is sent as HTTP \"headers" +"\". Let's look at each of these in turn." +msgstr "" + +#: ../Doc/howto/urllib2.rst:97 +msgid "Data" +msgstr "" + +#: ../Doc/howto/urllib2.rst:99 +msgid "" +"Sometimes you want to send data to a URL (often the URL will refer to a CGI " +"(Common Gateway Interface) script or other web application). With HTTP, this " +"is often done using what's known as a **POST** request. This is often what " +"your browser does when you submit a HTML form that you filled in on the web. " +"Not all POSTs have to come from forms: you can use a POST to transmit " +"arbitrary data to your own application. In the common case of HTML forms, " +"the data needs to be encoded in a standard way, and then passed to the " +"Request object as the ``data`` argument. The encoding is done using a " +"function from the :mod:`urllib.parse` library. ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:123 +msgid "" +"Note that other encodings are sometimes required (e.g. for file upload from " +"HTML forms - see `HTML Specification, Form Submission `_ for more details)." +msgstr "" + +#: ../Doc/howto/urllib2.rst:128 +msgid "" +"If you do not pass the ``data`` argument, urllib uses a **GET** request. One " +"way in which GET and POST requests differ is that POST requests often have " +"\"side-effects\": they change the state of the system in some way (for " +"example by placing an order with the website for a hundredweight of tinned " +"spam to be delivered to your door). Though the HTTP standard makes it clear " +"that POSTs are intended to *always* cause side-effects, and GET requests " +"*never* to cause side-effects, nothing prevents a GET request from having " +"side-effects, nor a POST requests from having no side-effects. Data can also " +"be passed in an HTTP GET request by encoding it in the URL itself." +msgstr "" + +#: ../Doc/howto/urllib2.rst:138 +msgid "This is done as follows::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:153 +msgid "" +"Notice that the full URL is created by adding a ``?`` to the URL, followed " +"by the encoded values." +msgstr "" + +#: ../Doc/howto/urllib2.rst:157 +msgid "Headers" +msgstr "" + +#: ../Doc/howto/urllib2.rst:159 +msgid "" +"We'll discuss here one particular HTTP header, to illustrate how to add " +"headers to your HTTP request." +msgstr "" + +#: ../Doc/howto/urllib2.rst:162 +msgid "" +"Some websites [#]_ dislike being browsed by programs, or send different " +"versions to different browsers [#]_. By default urllib identifies itself as " +"``Python-urllib/x.y`` (where ``x`` and ``y`` are the major and minor version " +"numbers of the Python release, e.g. ``Python-urllib/2.5``), which may " +"confuse the site, or just plain not work. The way a browser identifies " +"itself is through the ``User-Agent`` header [#]_. When you create a Request " +"object you can pass a dictionary of headers in. The following example makes " +"the same request as above, but identifies itself as a version of Internet " +"Explorer [#]_. ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:189 +msgid "" +"The response also has two useful methods. See the section on `info and " +"geturl`_ which comes after we have a look at what happens when things go " +"wrong." +msgstr "" + +#: ../Doc/howto/urllib2.rst:194 +msgid "Handling Exceptions" +msgstr "" + +#: ../Doc/howto/urllib2.rst:196 +msgid "" +"*urlopen* raises :exc:`URLError` when it cannot handle a response (though as " +"usual with Python APIs, built-in exceptions such as :exc:`ValueError`, :exc:" +"`TypeError` etc. may also be raised)." +msgstr "" + +#: ../Doc/howto/urllib2.rst:200 +msgid "" +":exc:`HTTPError` is the subclass of :exc:`URLError` raised in the specific " +"case of HTTP URLs." +msgstr "" + +#: ../Doc/howto/urllib2.rst:203 +msgid "The exception classes are exported from the :mod:`urllib.error` module." +msgstr "" + +#: ../Doc/howto/urllib2.rst:206 +msgid "URLError" +msgstr "" + +#: ../Doc/howto/urllib2.rst:208 +msgid "" +"Often, URLError is raised because there is no network connection (no route " +"to the specified server), or the specified server doesn't exist. In this " +"case, the exception raised will have a 'reason' attribute, which is a tuple " +"containing an error code and a text error message." +msgstr "" + +#: ../Doc/howto/urllib2.rst:213 ../Doc/howto/urllib2.rst:460 +msgid "e.g. ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:224 +msgid "HTTPError" +msgstr "" + +#: ../Doc/howto/urllib2.rst:226 +msgid "" +"Every HTTP response from the server contains a numeric \"status code\". " +"Sometimes the status code indicates that the server is unable to fulfil the " +"request. The default handlers will handle some of these responses for you " +"(for example, if the response is a \"redirection\" that requests the client " +"fetch the document from a different URL, urllib will handle that for you). " +"For those it can't handle, urlopen will raise an :exc:`HTTPError`. Typical " +"errors include '404' (page not found), '403' (request forbidden), and " +"'401' (authentication required)." +msgstr "" + +#: ../Doc/howto/urllib2.rst:234 +msgid "See section 10 of RFC 2616 for a reference on all the HTTP error codes." +msgstr "" + +#: ../Doc/howto/urllib2.rst:236 +msgid "" +"The :exc:`HTTPError` instance raised will have an integer 'code' attribute, " +"which corresponds to the error sent by the server." +msgstr "" + +#: ../Doc/howto/urllib2.rst:240 +msgid "Error Codes" +msgstr "" + +#: ../Doc/howto/urllib2.rst:242 +msgid "" +"Because the default handlers handle redirects (codes in the 300 range), and " +"codes in the 100-299 range indicate success, you will usually only see error " +"codes in the 400-599 range." +msgstr "" + +#: ../Doc/howto/urllib2.rst:246 +msgid "" +":attr:`http.server.BaseHTTPRequestHandler.responses` is a useful dictionary " +"of response codes in that shows all the response codes used by RFC 2616. The " +"dictionary is reproduced here for convenience ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:318 +msgid "" +"When an error is raised the server responds by returning an HTTP error code " +"*and* an error page. You can use the :exc:`HTTPError` instance as a response " +"on the page returned. This means that as well as the code attribute, it also " +"has read, geturl, and info, methods as returned by the ``urllib.response`` " +"module::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:338 +msgid "Wrapping it Up" +msgstr "" + +#: ../Doc/howto/urllib2.rst:340 +msgid "" +"So if you want to be prepared for :exc:`HTTPError` *or* :exc:`URLError` " +"there are two basic approaches. I prefer the second approach." +msgstr "" + +#: ../Doc/howto/urllib2.rst:344 +msgid "Number 1" +msgstr "" + +#: ../Doc/howto/urllib2.rst:366 +msgid "" +"The ``except HTTPError`` *must* come first, otherwise ``except URLError`` " +"will *also* catch an :exc:`HTTPError`." +msgstr "" + +#: ../Doc/howto/urllib2.rst:370 +msgid "Number 2" +msgstr "" + +#: ../Doc/howto/urllib2.rst:391 +msgid "info and geturl" +msgstr "" + +#: ../Doc/howto/urllib2.rst:393 +msgid "" +"The response returned by urlopen (or the :exc:`HTTPError` instance) has two " +"useful methods :meth:`info` and :meth:`geturl` and is defined in the module :" +"mod:`urllib.response`.." +msgstr "" + +#: ../Doc/howto/urllib2.rst:397 +msgid "" +"**geturl** - this returns the real URL of the page fetched. This is useful " +"because ``urlopen`` (or the opener object used) may have followed a " +"redirect. The URL of the page fetched may not be the same as the URL " +"requested." +msgstr "" + +#: ../Doc/howto/urllib2.rst:401 +msgid "" +"**info** - this returns a dictionary-like object that describes the page " +"fetched, particularly the headers sent by the server. It is currently an :" +"class:`http.client.HTTPMessage` instance." +msgstr "" + +#: ../Doc/howto/urllib2.rst:405 +msgid "" +"Typical headers include 'Content-length', 'Content-type', and so on. See the " +"`Quick Reference to HTTP Headers `_ for a useful listing of HTTP headers with brief explanations of " +"their meaning and use." +msgstr "" + +#: ../Doc/howto/urllib2.rst:412 +msgid "Openers and Handlers" +msgstr "" + +#: ../Doc/howto/urllib2.rst:414 +msgid "" +"When you fetch a URL you use an opener (an instance of the perhaps " +"confusingly-named :class:`urllib.request.OpenerDirector`). Normally we have " +"been using the default opener - via ``urlopen`` - but you can create custom " +"openers. Openers use handlers. All the \"heavy lifting\" is done by the " +"handlers. Each handler knows how to open URLs for a particular URL scheme " +"(http, ftp, etc.), or how to handle an aspect of URL opening, for example " +"HTTP redirections or HTTP cookies." +msgstr "" + +#: ../Doc/howto/urllib2.rst:422 +msgid "" +"You will want to create openers if you want to fetch URLs with specific " +"handlers installed, for example to get an opener that handles cookies, or to " +"get an opener that does not handle redirections." +msgstr "" + +#: ../Doc/howto/urllib2.rst:426 +msgid "" +"To create an opener, instantiate an ``OpenerDirector``, and then call ``." +"add_handler(some_handler_instance)`` repeatedly." +msgstr "" + +#: ../Doc/howto/urllib2.rst:429 +msgid "" +"Alternatively, you can use ``build_opener``, which is a convenience function " +"for creating opener objects with a single function call. ``build_opener`` " +"adds several handlers by default, but provides a quick way to add more and/" +"or override the default handlers." +msgstr "" + +#: ../Doc/howto/urllib2.rst:434 +msgid "" +"Other sorts of handlers you might want to can handle proxies, " +"authentication, and other common but slightly specialised situations." +msgstr "" + +#: ../Doc/howto/urllib2.rst:437 +msgid "" +"``install_opener`` can be used to make an ``opener`` object the (global) " +"default opener. This means that calls to ``urlopen`` will use the opener you " +"have installed." +msgstr "" + +#: ../Doc/howto/urllib2.rst:441 +msgid "" +"Opener objects have an ``open`` method, which can be called directly to " +"fetch urls in the same way as the ``urlopen`` function: there's no need to " +"call ``install_opener``, except as a convenience." +msgstr "" + +#: ../Doc/howto/urllib2.rst:447 +msgid "Basic Authentication" +msgstr "" + +#: ../Doc/howto/urllib2.rst:449 +msgid "" +"To illustrate creating and installing a handler we will use the " +"``HTTPBasicAuthHandler``. For a more detailed discussion of this subject -- " +"including an explanation of how Basic Authentication works - see the `Basic " +"Authentication Tutorial `_." +msgstr "" + +#: ../Doc/howto/urllib2.rst:455 +msgid "" +"When authentication is required, the server sends a header (as well as the " +"401 error code) requesting authentication. This specifies the " +"authentication scheme and a 'realm'. The header looks like: ``WWW-" +"Authenticate: SCHEME realm=\"REALM\"``." +msgstr "" + +#: ../Doc/howto/urllib2.rst:465 +msgid "" +"The client should then retry the request with the appropriate name and " +"password for the realm included as a header in the request. This is 'basic " +"authentication'. In order to simplify this process we can create an instance " +"of ``HTTPBasicAuthHandler`` and an opener to use this handler." +msgstr "" + +#: ../Doc/howto/urllib2.rst:470 +msgid "" +"The ``HTTPBasicAuthHandler`` uses an object called a password manager to " +"handle the mapping of URLs and realms to passwords and usernames. If you " +"know what the realm is (from the authentication header sent by the server), " +"then you can use a ``HTTPPasswordMgr``. Frequently one doesn't care what the " +"realm is. In that case, it is convenient to use " +"``HTTPPasswordMgrWithDefaultRealm``. This allows you to specify a default " +"username and password for a URL. This will be supplied in the absence of you " +"providing an alternative combination for a specific realm. We indicate this " +"by providing ``None`` as the realm argument to the ``add_password`` method." +msgstr "" + +#: ../Doc/howto/urllib2.rst:480 +msgid "" +"The top-level URL is the first URL that requires authentication. URLs " +"\"deeper\" than the URL you pass to .add_password() will also match. ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:505 +msgid "" +"In the above example we only supplied our ``HTTPBasicAuthHandler`` to " +"``build_opener``. By default openers have the handlers for normal situations " +"-- ``ProxyHandler`` (if a proxy setting such as an :envvar:`http_proxy` " +"environment variable is set), ``UnknownHandler``, ``HTTPHandler``, " +"``HTTPDefaultErrorHandler``, ``HTTPRedirectHandler``, ``FTPHandler``, " +"``FileHandler``, ``DataHandler``, ``HTTPErrorProcessor``." +msgstr "" + +#: ../Doc/howto/urllib2.rst:512 +msgid "" +"``top_level_url`` is in fact *either* a full URL (including the 'http:' " +"scheme component and the hostname and optionally the port number) e.g. " +"\"http://example.com/\" *or* an \"authority\" (i.e. the hostname, optionally " +"including the port number) e.g. \"example.com\" or \"example.com:8080\" (the " +"latter example includes a port number). The authority, if present, must NOT " +"contain the \"userinfo\" component - for example \"joe:password@example.com" +"\" is not correct." +msgstr "" + +#: ../Doc/howto/urllib2.rst:522 +msgid "Proxies" +msgstr "" + +#: ../Doc/howto/urllib2.rst:524 +msgid "" +"**urllib** will auto-detect your proxy settings and use those. This is " +"through the ``ProxyHandler``, which is part of the normal handler chain when " +"a proxy setting is detected. Normally that's a good thing, but there are " +"occasions when it may not be helpful [#]_. One way to do this is to setup " +"our own ``ProxyHandler``, with no proxies defined. This is done using " +"similar steps to setting up a `Basic Authentication`_ handler: ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:537 +msgid "" +"Currently ``urllib.request`` *does not* support fetching of ``https`` " +"locations through a proxy. However, this can be enabled by extending urllib." +"request as shown in the recipe [#]_." +msgstr "" + +#: ../Doc/howto/urllib2.rst:543 +msgid "" +"``HTTP_PROXY`` will be ignored if a variable ``REQUEST_METHOD`` is set; see " +"the documentation on :func:`~urllib.request.getproxies`." +msgstr "" + +#: ../Doc/howto/urllib2.rst:548 +msgid "Sockets and Layers" +msgstr "" + +#: ../Doc/howto/urllib2.rst:550 +msgid "" +"The Python support for fetching resources from the web is layered. urllib " +"uses the :mod:`http.client` library, which in turn uses the socket library." +msgstr "" + +#: ../Doc/howto/urllib2.rst:553 +msgid "" +"As of Python 2.3 you can specify how long a socket should wait for a " +"response before timing out. This can be useful in applications which have to " +"fetch web pages. By default the socket module has *no timeout* and can hang. " +"Currently, the socket timeout is not exposed at the http.client or urllib." +"request levels. However, you can set the default timeout globally for all " +"sockets using ::" +msgstr "" + +#: ../Doc/howto/urllib2.rst:576 +msgid "Footnotes" +msgstr "" + +#: ../Doc/howto/urllib2.rst:578 +msgid "This document was reviewed and revised by John Lee." +msgstr "" + +#: ../Doc/howto/urllib2.rst:580 +msgid "Google for example." +msgstr "" + +#: ../Doc/howto/urllib2.rst:581 +msgid "" +"Browser sniffing is a very bad practise for website design - building sites " +"using web standards is much more sensible. Unfortunately a lot of sites " +"still send different versions to different browsers." +msgstr "" + +#: ../Doc/howto/urllib2.rst:584 +msgid "" +"The user agent for MSIE 6 is *'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT " +"5.1; SV1; .NET CLR 1.1.4322)'*" +msgstr "" + +#: ../Doc/howto/urllib2.rst:586 +msgid "" +"For details of more HTTP request headers, see `Quick Reference to HTTP " +"Headers`_." +msgstr "" + +#: ../Doc/howto/urllib2.rst:588 +msgid "" +"In my case I have to use a proxy to access the internet at work. If you " +"attempt to fetch *localhost* URLs through this proxy it blocks them. IE is " +"set to use the proxy, which urllib picks up on. In order to test scripts " +"with a localhost server, I have to prevent urllib from using the proxy." +msgstr "" + +#: ../Doc/howto/urllib2.rst:593 +msgid "" +"urllib opener for SSL proxy (CONNECT method): `ASPN Cookbook Recipe `_." +msgstr "" diff --git a/install.po b/install.po new file mode 100644 index 00000000..ad5875bc --- /dev/null +++ b/install.po @@ -0,0 +1,1495 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/install/index.rst:7 +msgid "Installing Python Modules (Legacy version)" +msgstr "" + +#: ../Doc/install/index.rst:9 +msgid "Greg Ward" +msgstr "" + +#: ../Doc/install/index.rst:15 +msgid ":ref:`installing-index`" +msgstr "" + +#: ../Doc/install/index.rst:16 +msgid "The up to date module installation documentations" +msgstr "" + +#: ../Doc/install/index.rst:28 +msgid "" +"This document describes the Python Distribution Utilities (\"Distutils\") " +"from the end-user's point-of-view, describing how to extend the capabilities " +"of a standard Python installation by building and installing third-party " +"Python modules and extensions." +msgstr "" + +#: ../Doc/install/index.rst:36 +msgid "" +"This guide only covers the basic tools for building and distributing " +"extensions that are provided as part of this version of Python. Third party " +"tools offer easier to use and more secure alternatives. Refer to the `quick " +"recommendations section `__ " +"in the Python Packaging User Guide for more information." +msgstr "" + +#: ../Doc/install/index.rst:47 +msgid "Introduction" +msgstr "" + +#: ../Doc/install/index.rst:49 +msgid "" +"Although Python's extensive standard library covers many programming needs, " +"there often comes a time when you need to add some new functionality to your " +"Python installation in the form of third-party modules. This might be " +"necessary to support your own programming, or to support an application that " +"you want to use and that happens to be written in Python." +msgstr "" + +#: ../Doc/install/index.rst:55 +msgid "" +"In the past, there has been little support for adding third-party modules to " +"an existing Python installation. With the introduction of the Python " +"Distribution Utilities (Distutils for short) in Python 2.0, this changed." +msgstr "" + +#: ../Doc/install/index.rst:59 +msgid "" +"This document is aimed primarily at the people who need to install third-" +"party Python modules: end-users and system administrators who just need to " +"get some Python application running, and existing Python programmers who " +"want to add some new goodies to their toolbox. You don't need to know " +"Python to read this document; there will be some brief forays into using " +"Python's interactive mode to explore your installation, but that's it. If " +"you're looking for information on how to distribute your own Python modules " +"so that others may use them, see the :ref:`distutils-index` manual. :ref:" +"`debug-setup-script` may also be of interest." +msgstr "" + +#: ../Doc/install/index.rst:73 +msgid "Best case: trivial installation" +msgstr "" + +#: ../Doc/install/index.rst:75 +msgid "" +"In the best case, someone will have prepared a special version of the module " +"distribution you want to install that is targeted specifically at your " +"platform and is installed just like any other software on your platform. " +"For example, the module developer might make an executable installer " +"available for Windows users, an RPM package for users of RPM-based Linux " +"systems (Red Hat, SuSE, Mandrake, and many others), a Debian package for " +"users of Debian-based Linux systems, and so forth." +msgstr "" + +#: ../Doc/install/index.rst:83 +msgid "" +"In that case, you would download the installer appropriate to your platform " +"and do the obvious thing with it: run it if it's an executable installer, " +"``rpm --install`` it if it's an RPM, etc. You don't need to run Python or a " +"setup script, you don't need to compile anything---you might not even need " +"to read any instructions (although it's always a good idea to do so anyway)." +msgstr "" + +#: ../Doc/install/index.rst:89 +msgid "" +"Of course, things will not always be that easy. You might be interested in " +"a module distribution that doesn't have an easy-to-use installer for your " +"platform. In that case, you'll have to start with the source distribution " +"released by the module's author/maintainer. Installing from a source " +"distribution is not too hard, as long as the modules are packaged in the " +"standard way. The bulk of this document is about building and installing " +"modules from standard source distributions." +msgstr "" + +#: ../Doc/install/index.rst:101 +msgid "The new standard: Distutils" +msgstr "" + +#: ../Doc/install/index.rst:103 +msgid "" +"If you download a module source distribution, you can tell pretty quickly if " +"it was packaged and distributed in the standard way, i.e. using the " +"Distutils. First, the distribution's name and version number will be " +"featured prominently in the name of the downloaded archive, e.g. :file:" +"`foo-1.0.tar.gz` or :file:`widget-0.9.7.zip`. Next, the archive will unpack " +"into a similarly-named directory: :file:`foo-1.0` or :file:`widget-0.9.7`. " +"Additionally, the distribution will contain a setup script :file:`setup.py`, " +"and a file named :file:`README.txt` or possibly just :file:`README`, which " +"should explain that building and installing the module distribution is a " +"simple matter of running one command from a terminal::" +msgstr "" + +#: ../Doc/install/index.rst:116 +msgid "" +"For Windows, this command should be run from a command prompt window (:" +"menuselection:`Start --> Accessories`)::" +msgstr "" + +#: ../Doc/install/index.rst:121 +msgid "" +"If all these things are true, then you already know how to build and install " +"the modules you've just downloaded: Run the command above. Unless you need " +"to install things in a non-standard way or customize the build process, you " +"don't really need this manual. Or rather, the above command is everything " +"you need to get out of this manual." +msgstr "" + +#: ../Doc/install/index.rst:131 +msgid "Standard Build and Install" +msgstr "" + +#: ../Doc/install/index.rst:133 +msgid "" +"As described in section :ref:`inst-new-standard`, building and installing a " +"module distribution using the Distutils is usually one simple command to run " +"from a terminal::" +msgstr "" + +#: ../Doc/install/index.rst:143 +msgid "Platform variations" +msgstr "" + +#: ../Doc/install/index.rst:145 +msgid "" +"You should always run the setup command from the distribution root " +"directory, i.e. the top-level subdirectory that the module source " +"distribution unpacks into. For example, if you've just downloaded a module " +"source distribution :file:`foo-1.0.tar.gz` onto a Unix system, the normal " +"thing to do is::" +msgstr "" + +#: ../Doc/install/index.rst:154 +msgid "" +"On Windows, you'd probably download :file:`foo-1.0.zip`. If you downloaded " +"the archive file to :file:`C:\\\\Temp`, then it would unpack into :file:`C:\\" +"\\Temp\\\\foo-1.0`; you can use either an archive manipulator with a " +"graphical user interface (such as WinZip) or a command-line tool (such as :" +"program:`unzip` or :program:`pkunzip`) to unpack the archive. Then, open a " +"command prompt window and run::" +msgstr "" + +#: ../Doc/install/index.rst:168 +msgid "Splitting the job up" +msgstr "" + +#: ../Doc/install/index.rst:170 +msgid "" +"Running ``setup.py install`` builds and installs all modules in one run. If " +"you prefer to work incrementally---especially useful if you want to " +"customize the build process, or if things are going wrong---you can use the " +"setup script to do one thing at a time. This is particularly helpful when " +"the build and install will be done by different users---for example, you " +"might want to build a module distribution and hand it off to a system " +"administrator for installation (or do it yourself, with super-user " +"privileges)." +msgstr "" + +#: ../Doc/install/index.rst:178 +msgid "" +"For example, you can build everything in one step, and then install " +"everything in a second step, by invoking the setup script twice::" +msgstr "" + +#: ../Doc/install/index.rst:184 +msgid "" +"If you do this, you will notice that running the :command:`install` command " +"first runs the :command:`build` command, which---in this case---quickly " +"notices that it has nothing to do, since everything in the :file:`build` " +"directory is up-to-date." +msgstr "" + +#: ../Doc/install/index.rst:189 +msgid "" +"You may not need this ability to break things down often if all you do is " +"install modules downloaded off the 'net, but it's very handy for more " +"advanced tasks. If you get into distributing your own Python modules and " +"extensions, you'll run lots of individual Distutils commands on their own." +msgstr "" + +#: ../Doc/install/index.rst:198 +msgid "How building works" +msgstr "" + +#: ../Doc/install/index.rst:200 +msgid "" +"As implied above, the :command:`build` command is responsible for putting " +"the files to install into a *build directory*. By default, this is :file:" +"`build` under the distribution root; if you're excessively concerned with " +"speed, or want to keep the source tree pristine, you can change the build " +"directory with the :option:`--build-base` option. For example::" +msgstr "" + +#: ../Doc/install/index.rst:208 +msgid "" +"(Or you could do this permanently with a directive in your system or " +"personal Distutils configuration file; see section :ref:`inst-config-" +"files`.) Normally, this isn't necessary." +msgstr "" + +#: ../Doc/install/index.rst:212 +msgid "The default layout for the build tree is as follows::" +msgstr "" + +#: ../Doc/install/index.rst:219 +msgid "" +"where ```` expands to a brief description of the current OS/hardware " +"platform and Python version. The first form, with just a :file:`lib` " +"directory, is used for \"pure module distributions\"---that is, module " +"distributions that include only pure Python modules. If a module " +"distribution contains any extensions (modules written in C/C++), then the " +"second form, with two ```` directories, is used. In that case, the :" +"file:`temp.{plat}` directory holds temporary files generated by the compile/" +"link process that don't actually get installed. In either case, the :file:" +"`lib` (or :file:`lib.{plat}`) directory contains all Python modules (pure " +"Python and extensions) that will be installed." +msgstr "" + +#: ../Doc/install/index.rst:229 +msgid "" +"In the future, more directories will be added to handle Python scripts, " +"documentation, binary executables, and whatever else is needed to handle the " +"job of installing Python modules and applications." +msgstr "" + +#: ../Doc/install/index.rst:237 +msgid "How installation works" +msgstr "" + +#: ../Doc/install/index.rst:239 +msgid "" +"After the :command:`build` command runs (whether you run it explicitly, or " +"the :command:`install` command does it for you), the work of the :command:" +"`install` command is relatively simple: all it has to do is copy everything " +"under :file:`build/lib` (or :file:`build/lib.{plat}`) to your chosen " +"installation directory." +msgstr "" + +#: ../Doc/install/index.rst:245 +msgid "" +"If you don't choose an installation directory---i.e., if you just run " +"``setup.py install``\\ ---then the :command:`install` command installs to " +"the standard location for third-party Python modules. This location varies " +"by platform and by how you built/installed Python itself. On Unix (and Mac " +"OS X, which is also Unix-based), it also depends on whether the module " +"distribution being installed is pure Python or contains extensions (\"non-" +"pure\"):" +msgstr "" + +#: ../Doc/install/index.rst:255 +msgid "Platform" +msgstr "" + +#: ../Doc/install/index.rst:255 +msgid "Standard installation location" +msgstr "" + +#: ../Doc/install/index.rst:255 +msgid "Default value" +msgstr "" + +#: ../Doc/install/index.rst:255 ../Doc/install/index.rst:773 +#: ../Doc/install/index.rst:785 +msgid "Notes" +msgstr "" + +#: ../Doc/install/index.rst:257 +msgid "Unix (pure)" +msgstr "" + +#: ../Doc/install/index.rst:257 ../Doc/install/index.rst:468 +msgid ":file:`{prefix}/lib/python{X.Y}/site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:257 ../Doc/install/index.rst:259 +msgid ":file:`/usr/local/lib/python{X.Y}/site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:257 ../Doc/install/index.rst:259 +#: ../Doc/install/index.rst:775 +msgid "\\(1)" +msgstr "" + +#: ../Doc/install/index.rst:259 +msgid "Unix (non-pure)" +msgstr "" + +#: ../Doc/install/index.rst:259 ../Doc/install/index.rst:469 +msgid ":file:`{exec-prefix}/lib/python{X.Y}/site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:261 +msgid "Windows" +msgstr "" + +#: ../Doc/install/index.rst:261 ../Doc/install/index.rst:520 +msgid ":file:`{prefix}\\\\Lib\\\\site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:261 +msgid ":file:`C:\\\\Python{XY}\\\\Lib\\\\site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:261 ../Doc/install/index.rst:777 +msgid "\\(2)" +msgstr "" + +#: ../Doc/install/index.rst:264 ../Doc/install/index.rst:797 +msgid "Notes:" +msgstr "" + +#: ../Doc/install/index.rst:267 +msgid "" +"Most Linux distributions include Python as a standard part of the system, " +"so :file:`{prefix}` and :file:`{exec-prefix}` are usually both :file:`/usr` " +"on Linux. If you build Python yourself on Linux (or any Unix-like system), " +"the default :file:`{prefix}` and :file:`{exec-prefix}` are :file:`/usr/" +"local`." +msgstr "" + +#: ../Doc/install/index.rst:273 +msgid "" +"The default installation directory on Windows was :file:`C:\\\\Program Files" +"\\\\Python` under Python 1.6a1, 1.5.2, and earlier." +msgstr "" + +#: ../Doc/install/index.rst:276 +msgid "" +":file:`{prefix}` and :file:`{exec-prefix}` stand for the directories that " +"Python is installed to, and where it finds its libraries at run-time. They " +"are always the same under Windows, and very often the same under Unix and " +"Mac OS X. You can find out what your Python installation uses for :file:" +"`{prefix}` and :file:`{exec-prefix}` by running Python in interactive mode " +"and typing a few simple commands. Under Unix, just type ``python`` at the " +"shell prompt. Under Windows, choose :menuselection:`Start --> Programs --> " +"Python X.Y --> Python (command line)`. Once the interpreter is started, " +"you type Python code at the prompt. For example, on my Linux system, I type " +"the three Python statements shown below, and get the output as shown, to " +"find out my :file:`{prefix}` and :file:`{exec-prefix}`::" +msgstr "" + +#: ../Doc/install/index.rst:296 +msgid "" +"A few other placeholders are used in this document: :file:`{X.Y}` stands for " +"the version of Python, for example ``3.2``; :file:`{abiflags}` will be " +"replaced by the value of :data:`sys.abiflags` or the empty string for " +"platforms which don't define ABI flags; :file:`{distname}` will be replaced " +"by the name of the module distribution being installed. Dots and " +"capitalization are important in the paths; for example, a value that uses " +"``python3.2`` on UNIX will typically use ``Python32`` on Windows." +msgstr "" + +#: ../Doc/install/index.rst:304 +msgid "" +"If you don't want to install modules to the standard location, or if you " +"don't have permission to write there, then you need to read about alternate " +"installations in section :ref:`inst-alt-install`. If you want to customize " +"your installation directories more heavily, see section :ref:`inst-custom-" +"install` on custom installations." +msgstr "" + +#: ../Doc/install/index.rst:314 +msgid "Alternate Installation" +msgstr "" + +#: ../Doc/install/index.rst:316 +msgid "" +"Often, it is necessary or desirable to install modules to a location other " +"than the standard location for third-party Python modules. For example, on " +"a Unix system you might not have permission to write to the standard third-" +"party module directory. Or you might wish to try out a module before making " +"it a standard part of your local Python installation. This is especially " +"true when upgrading a distribution already present: you want to make sure " +"your existing base of scripts still works with the new version before " +"actually upgrading." +msgstr "" + +#: ../Doc/install/index.rst:324 +msgid "" +"The Distutils :command:`install` command is designed to make installing " +"module distributions to an alternate location simple and painless. The " +"basic idea is that you supply a base directory for the installation, and " +"the :command:`install` command picks a set of directories (called an " +"*installation scheme*) under this base directory in which to install files. " +"The details differ across platforms, so read whichever of the following " +"sections applies to you." +msgstr "" + +#: ../Doc/install/index.rst:332 +msgid "" +"Note that the various alternate installation schemes are mutually exclusive: " +"you can pass ``--user``, or ``--home``, or ``--prefix`` and ``--exec-" +"prefix``, or ``--install-base`` and ``--install-platbase``, but you can't " +"mix from these groups." +msgstr "" + +#: ../Doc/install/index.rst:341 +msgid "Alternate installation: the user scheme" +msgstr "" + +#: ../Doc/install/index.rst:343 +msgid "" +"This scheme is designed to be the most convenient solution for users that " +"don't have write permission to the global site-packages directory or don't " +"want to install into it. It is enabled with a simple option::" +msgstr "" + +#: ../Doc/install/index.rst:349 +msgid "" +"Files will be installed into subdirectories of :data:`site.USER_BASE` " +"(written as :file:`{userbase}` hereafter). This scheme installs pure Python " +"modules and extension modules in the same location (also known as :data:" +"`site.USER_SITE`). Here are the values for UNIX, including Mac OS X:" +msgstr "" + +#: ../Doc/install/index.rst:355 ../Doc/install/index.rst:366 +#: ../Doc/install/index.rst:417 ../Doc/install/index.rst:466 +#: ../Doc/install/index.rst:518 ../Doc/install/index.rst:543 +#: ../Doc/install/index.rst:773 ../Doc/install/index.rst:785 +msgid "Type of file" +msgstr "" + +#: ../Doc/install/index.rst:355 ../Doc/install/index.rst:366 +#: ../Doc/install/index.rst:417 ../Doc/install/index.rst:466 +#: ../Doc/install/index.rst:518 +msgid "Installation directory" +msgstr "" + +#: ../Doc/install/index.rst:357 ../Doc/install/index.rst:368 +#: ../Doc/install/index.rst:419 ../Doc/install/index.rst:520 +msgid "modules" +msgstr "" + +#: ../Doc/install/index.rst:357 +msgid ":file:`{userbase}/lib/python{X.Y}/site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:358 ../Doc/install/index.rst:369 +#: ../Doc/install/index.rst:420 ../Doc/install/index.rst:470 +#: ../Doc/install/index.rst:521 ../Doc/install/index.rst:548 +msgid "scripts" +msgstr "" + +#: ../Doc/install/index.rst:358 +msgid ":file:`{userbase}/bin`" +msgstr "" + +#: ../Doc/install/index.rst:359 ../Doc/install/index.rst:370 +#: ../Doc/install/index.rst:421 ../Doc/install/index.rst:471 +#: ../Doc/install/index.rst:522 ../Doc/install/index.rst:549 +msgid "data" +msgstr "" + +#: ../Doc/install/index.rst:359 ../Doc/install/index.rst:370 +msgid ":file:`{userbase}`" +msgstr "" + +#: ../Doc/install/index.rst:360 ../Doc/install/index.rst:371 +#: ../Doc/install/index.rst:422 ../Doc/install/index.rst:472 +#: ../Doc/install/index.rst:523 ../Doc/install/index.rst:550 +msgid "C headers" +msgstr "" + +#: ../Doc/install/index.rst:360 +msgid ":file:`{userbase}/include/python{X.Y}{abiflags}/{distname}`" +msgstr "" + +#: ../Doc/install/index.rst:363 +msgid "And here are the values used on Windows:" +msgstr "" + +#: ../Doc/install/index.rst:368 +msgid ":file:`{userbase}\\\\Python{XY}\\\\site-packages`" +msgstr "" + +#: ../Doc/install/index.rst:369 +msgid ":file:`{userbase}\\\\Python{XY}\\\\Scripts`" +msgstr "" + +#: ../Doc/install/index.rst:371 +msgid ":file:`{userbase}\\\\Python{XY}\\\\Include\\\\{distname}`" +msgstr "" + +#: ../Doc/install/index.rst:374 +msgid "" +"The advantage of using this scheme compared to the other ones described " +"below is that the user site-packages directory is under normal conditions " +"always included in :data:`sys.path` (see :mod:`site` for more information), " +"which means that there is no additional step to perform after running the :" +"file:`setup.py` script to finalize the installation." +msgstr "" + +#: ../Doc/install/index.rst:380 +msgid "" +"The :command:`build_ext` command also has a ``--user`` option to add :file:" +"`{userbase}/include` to the compiler search path for header files and :file:" +"`{userbase}/lib` to the compiler search path for libraries as well as to the " +"runtime search path for shared C libraries (rpath)." +msgstr "" + +#: ../Doc/install/index.rst:389 +msgid "Alternate installation: the home scheme" +msgstr "" + +#: ../Doc/install/index.rst:391 +msgid "" +"The idea behind the \"home scheme\" is that you build and maintain a " +"personal stash of Python modules. This scheme's name is derived from the " +"idea of a \"home\" directory on Unix, since it's not unusual for a Unix user " +"to make their home directory have a layout similar to :file:`/usr/` or :file:" +"`/usr/local/`. This scheme can be used by anyone, regardless of the " +"operating system they are installing for." +msgstr "" + +#: ../Doc/install/index.rst:398 +msgid "Installing a new module distribution is as simple as ::" +msgstr "" + +#: ../Doc/install/index.rst:402 +msgid "" +"where you can supply any directory you like for the :option:`--home` " +"option. On Unix, lazy typists can just type a tilde (``~``); the :command:" +"`install` command will expand this to your home directory::" +msgstr "" + +#: ../Doc/install/index.rst:408 +msgid "" +"To make Python find the distributions installed with this scheme, you may " +"have to :ref:`modify Python's search path ` or edit :mod:" +"`sitecustomize` (see :mod:`site`) to call :func:`site.addsitedir` or edit :" +"data:`sys.path`." +msgstr "" + +#: ../Doc/install/index.rst:413 +msgid "" +"The :option:`--home` option defines the installation base directory. Files " +"are installed to the following directories under the installation base as " +"follows:" +msgstr "" + +#: ../Doc/install/index.rst:419 +msgid ":file:`{home}/lib/python`" +msgstr "" + +#: ../Doc/install/index.rst:420 +msgid ":file:`{home}/bin`" +msgstr "" + +#: ../Doc/install/index.rst:421 +msgid ":file:`{home}`" +msgstr "" + +#: ../Doc/install/index.rst:422 +msgid ":file:`{home}/include/python/{distname}`" +msgstr "" + +#: ../Doc/install/index.rst:425 +msgid "(Mentally replace slashes with backslashes if you're on Windows.)" +msgstr "" + +#: ../Doc/install/index.rst:431 +msgid "Alternate installation: Unix (the prefix scheme)" +msgstr "" + +#: ../Doc/install/index.rst:433 +msgid "" +"The \"prefix scheme\" is useful when you wish to use one Python installation " +"to perform the build/install (i.e., to run the setup script), but install " +"modules into the third-party module directory of a different Python " +"installation (or something that looks like a different Python " +"installation). If this sounds a trifle unusual, it is---that's why the user " +"and home schemes come before. However, there are at least two known cases " +"where the prefix scheme will be useful." +msgstr "" + +#: ../Doc/install/index.rst:440 +msgid "" +"First, consider that many Linux distributions put Python in :file:`/usr`, " +"rather than the more traditional :file:`/usr/local`. This is entirely " +"appropriate, since in those cases Python is part of \"the system\" rather " +"than a local add-on. However, if you are installing Python modules from " +"source, you probably want them to go in :file:`/usr/local/lib/python2.{X}` " +"rather than :file:`/usr/lib/python2.{X}`. This can be done with ::" +msgstr "" + +#: ../Doc/install/index.rst:449 +msgid "" +"Another possibility is a network filesystem where the name used to write to " +"a remote directory is different from the name used to read it: for example, " +"the Python interpreter accessed as :file:`/usr/local/bin/python` might " +"search for modules in :file:`/usr/local/lib/python2.{X}`, but those modules " +"would have to be installed to, say, :file:`/mnt/{@server}/export/lib/python2." +"{X}`. This could be done with ::" +msgstr "" + +#: ../Doc/install/index.rst:458 +msgid "" +"In either case, the :option:`--prefix` option defines the installation base, " +"and the :option:`--exec-prefix` option defines the platform-specific " +"installation base, which is used for platform-specific files. (Currently, " +"this just means non-pure module distributions, but could be expanded to C " +"libraries, binary executables, etc.) If :option:`--exec-prefix` is not " +"supplied, it defaults to :option:`--prefix`. Files are installed as follows:" +msgstr "" + +#: ../Doc/install/index.rst:468 ../Doc/install/index.rst:545 +msgid "Python modules" +msgstr "" + +#: ../Doc/install/index.rst:469 ../Doc/install/index.rst:546 +msgid "extension modules" +msgstr "" + +#: ../Doc/install/index.rst:470 +msgid ":file:`{prefix}/bin`" +msgstr "" + +#: ../Doc/install/index.rst:471 ../Doc/install/index.rst:522 +msgid ":file:`{prefix}`" +msgstr "" + +#: ../Doc/install/index.rst:472 +msgid ":file:`{prefix}/include/python{X.Y}{abiflags}/{distname}`" +msgstr "" + +#: ../Doc/install/index.rst:475 +msgid "" +"There is no requirement that :option:`--prefix` or :option:`--exec-prefix` " +"actually point to an alternate Python installation; if the directories " +"listed above do not already exist, they are created at installation time." +msgstr "" + +#: ../Doc/install/index.rst:479 +msgid "" +"Incidentally, the real reason the prefix scheme is important is simply that " +"a standard Unix installation uses the prefix scheme, but with :option:`--" +"prefix` and :option:`--exec-prefix` supplied by Python itself as ``sys." +"prefix`` and ``sys.exec_prefix``. Thus, you might think you'll never use " +"the prefix scheme, but every time you run ``python setup.py install`` " +"without any other options, you're using it." +msgstr "" + +#: ../Doc/install/index.rst:486 +msgid "" +"Note that installing extensions to an alternate Python installation has no " +"effect on how those extensions are built: in particular, the Python header " +"files (:file:`Python.h` and friends) installed with the Python interpreter " +"used to run the setup script will be used in compiling extensions. It is " +"your responsibility to ensure that the interpreter used to run extensions " +"installed in this way is compatible with the interpreter used to build " +"them. The best way to do this is to ensure that the two interpreters are " +"the same version of Python (possibly different builds, or possibly copies of " +"the same build). (Of course, if your :option:`--prefix` and :option:`--exec-" +"prefix` don't even point to an alternate Python installation, this is " +"immaterial.)" +msgstr "" + +#: ../Doc/install/index.rst:501 +msgid "Alternate installation: Windows (the prefix scheme)" +msgstr "" + +#: ../Doc/install/index.rst:503 +msgid "" +"Windows has no concept of a user's home directory, and since the standard " +"Python installation under Windows is simpler than under Unix, the :option:`--" +"prefix` option has traditionally been used to install additional packages in " +"separate locations on Windows. ::" +msgstr "" + +#: ../Doc/install/index.rst:510 +msgid "" +"to install modules to the :file:`\\\\Temp\\\\Python` directory on the " +"current drive." +msgstr "" + +#: ../Doc/install/index.rst:512 +msgid "" +"The installation base is defined by the :option:`--prefix` option; the :" +"option:`--exec-prefix` option is not supported under Windows, which means " +"that pure Python modules and extension modules are installed into the same " +"location. Files are installed as follows:" +msgstr "" + +#: ../Doc/install/index.rst:521 +msgid ":file:`{prefix}\\\\Scripts`" +msgstr "" + +#: ../Doc/install/index.rst:523 +msgid ":file:`{prefix}\\\\Include\\\\{distname}`" +msgstr "" + +#: ../Doc/install/index.rst:530 +msgid "Custom Installation" +msgstr "" + +#: ../Doc/install/index.rst:532 +msgid "" +"Sometimes, the alternate installation schemes described in section :ref:" +"`inst-alt-install` just don't do what you want. You might want to tweak " +"just one or two directories while keeping everything under the same base " +"directory, or you might want to completely redefine the installation " +"scheme. In either case, you're creating a *custom installation scheme*." +msgstr "" + +#: ../Doc/install/index.rst:538 +msgid "" +"To create a custom installation scheme, you start with one of the alternate " +"schemes and override some of the installation directories used for the " +"various types of files, using these options:" +msgstr "" + +#: ../Doc/install/index.rst:543 +msgid "Override option" +msgstr "" + +#: ../Doc/install/index.rst:545 +msgid "``--install-purelib``" +msgstr "" + +#: ../Doc/install/index.rst:546 +msgid "``--install-platlib``" +msgstr "" + +#: ../Doc/install/index.rst:547 +msgid "all modules" +msgstr "" + +#: ../Doc/install/index.rst:547 +msgid "``--install-lib``" +msgstr "" + +#: ../Doc/install/index.rst:548 +msgid "``--install-scripts``" +msgstr "" + +#: ../Doc/install/index.rst:549 +msgid "``--install-data``" +msgstr "" + +#: ../Doc/install/index.rst:550 +msgid "``--install-headers``" +msgstr "" + +#: ../Doc/install/index.rst:553 +msgid "" +"These override options can be relative, absolute, or explicitly defined in " +"terms of one of the installation base directories. (There are two " +"installation base directories, and they are normally the same--- they only " +"differ when you use the Unix \"prefix scheme\" and supply different ``--" +"prefix`` and ``--exec-prefix`` options; using ``--install-lib`` will " +"override values computed or given for ``--install-purelib`` and ``--install-" +"platlib``, and is recommended for schemes that don't make a difference " +"between Python and extension modules.)" +msgstr "" + +#: ../Doc/install/index.rst:562 +msgid "" +"For example, say you're installing a module distribution to your home " +"directory under Unix---but you want scripts to go in :file:`~/scripts` " +"rather than :file:`~/bin`. As you might expect, you can override this " +"directory with the :option:`--install-scripts` option; in this case, it " +"makes most sense to supply a relative path, which will be interpreted " +"relative to the installation base directory (your home directory, in this " +"case)::" +msgstr "" + +#: ../Doc/install/index.rst:571 +msgid "" +"Another Unix example: suppose your Python installation was built and " +"installed with a prefix of :file:`/usr/local/python`, so under a standard " +"installation scripts will wind up in :file:`/usr/local/python/bin`. If you " +"want them in :file:`/usr/local/bin` instead, you would supply this absolute " +"directory for the :option:`--install-scripts` option::" +msgstr "" + +#: ../Doc/install/index.rst:579 +msgid "" +"(This performs an installation using the \"prefix scheme,\" where the prefix " +"is whatever your Python interpreter was installed with--- :file:`/usr/local/" +"python` in this case.)" +msgstr "" + +#: ../Doc/install/index.rst:583 +msgid "" +"If you maintain Python on Windows, you might want third-party modules to " +"live in a subdirectory of :file:`{prefix}`, rather than right in :file:" +"`{prefix}` itself. This is almost as easy as customizing the script " +"installation directory ---you just have to remember that there are two types " +"of modules to worry about, Python and extension modules, which can " +"conveniently be both controlled by one option::" +msgstr "" + +#: ../Doc/install/index.rst:592 +msgid "" +"The specified installation directory is relative to :file:`{prefix}`. Of " +"course, you also have to ensure that this directory is in Python's module " +"search path, such as by putting a :file:`.pth` file in a site directory " +"(see :mod:`site`). See section :ref:`inst-search-path` to find out how to " +"modify Python's search path." +msgstr "" + +#: ../Doc/install/index.rst:598 +msgid "" +"If you want to define an entire installation scheme, you just have to supply " +"all of the installation directory options. The recommended way to do this " +"is to supply relative paths; for example, if you want to maintain all Python " +"module-related files under :file:`python` in your home directory, and you " +"want a separate directory for each platform that you use your home directory " +"from, you might define the following installation scheme::" +msgstr "" + +#: ../Doc/install/index.rst:611 ../Doc/install/index.rst:634 +msgid "or, equivalently, ::" +msgstr "" + +#: ../Doc/install/index.rst:619 +msgid "" +"``$PLAT`` is not (necessarily) an environment variable---it will be expanded " +"by the Distutils as it parses your command line options, just as it does " +"when parsing your configuration file(s)." +msgstr "" + +#: ../Doc/install/index.rst:623 +msgid "" +"Obviously, specifying the entire installation scheme every time you install " +"a new module distribution would be very tedious. Thus, you can put these " +"options into your Distutils config file (see section :ref:`inst-config-" +"files`)::" +msgstr "" + +#: ../Doc/install/index.rst:643 +msgid "" +"Note that these two are *not* equivalent if you supply a different " +"installation base directory when you run the setup script. For example, ::" +msgstr "" + +#: ../Doc/install/index.rst:648 +msgid "" +"would install pure modules to :file:`/tmp/python/lib` in the first case, and " +"to :file:`/tmp/lib` in the second case. (For the second case, you probably " +"want to supply an installation base of :file:`/tmp/python`.)" +msgstr "" + +#: ../Doc/install/index.rst:652 +msgid "" +"You probably noticed the use of ``$HOME`` and ``$PLAT`` in the sample " +"configuration file input. These are Distutils configuration variables, " +"which bear a strong resemblance to environment variables. In fact, you can " +"use environment variables in config files on platforms that have such a " +"notion but the Distutils additionally define a few extra variables that may " +"not be in your environment, such as ``$PLAT``. (And of course, on systems " +"that don't have environment variables, such as Mac OS 9, the configuration " +"variables supplied by the Distutils are the only ones you can use.) See " +"section :ref:`inst-config-files` for details." +msgstr "" + +#: ../Doc/install/index.rst:662 +msgid "" +"When a :ref:`virtual environment ` is activated, any options that " +"change the installation path will be ignored from all distutils " +"configuration files to prevent inadvertently installing projects outside of " +"the virtual environment." +msgstr "" + +#: ../Doc/install/index.rst:676 +msgid "Modifying Python's Search Path" +msgstr "" + +#: ../Doc/install/index.rst:678 +msgid "" +"When the Python interpreter executes an :keyword:`import` statement, it " +"searches for both Python code and extension modules along a search path. A " +"default value for the path is configured into the Python binary when the " +"interpreter is built. You can determine the path by importing the :mod:`sys` " +"module and printing the value of ``sys.path``. ::" +msgstr "" + +#: ../Doc/install/index.rst:695 +msgid "" +"The null string in ``sys.path`` represents the current working directory." +msgstr "" + +#: ../Doc/install/index.rst:697 +msgid "" +"The expected convention for locally installed packages is to put them in " +"the :file:`{...}/site-packages/` directory, but you may want to install " +"Python modules into some arbitrary directory. For example, your site may " +"have a convention of keeping all software related to the web server under :" +"file:`/www`. Add-on Python modules might then belong in :file:`/www/python`, " +"and in order to import them, this directory must be added to ``sys.path``. " +"There are several different ways to add the directory." +msgstr "" + +#: ../Doc/install/index.rst:705 +msgid "" +"The most convenient way is to add a path configuration file to a directory " +"that's already on Python's path, usually to the :file:`.../site-packages/` " +"directory. Path configuration files have an extension of :file:`.pth`, and " +"each line must contain a single path that will be appended to ``sys.path``. " +"(Because the new paths are appended to ``sys.path``, modules in the added " +"directories will not override standard modules. This means you can't use " +"this mechanism for installing fixed versions of standard modules.)" +msgstr "" + +#: ../Doc/install/index.rst:713 +msgid "" +"Paths can be absolute or relative, in which case they're relative to the " +"directory containing the :file:`.pth` file. See the documentation of the :" +"mod:`site` module for more information." +msgstr "" + +#: ../Doc/install/index.rst:717 +msgid "" +"A slightly less convenient way is to edit the :file:`site.py` file in " +"Python's standard library, and modify ``sys.path``. :file:`site.py` is " +"automatically imported when the Python interpreter is executed, unless the :" +"option:`-S` switch is supplied to suppress this behaviour. So you could " +"simply edit :file:`site.py` and add two lines to it::" +msgstr "" + +#: ../Doc/install/index.rst:726 +msgid "" +"However, if you reinstall the same major version of Python (perhaps when " +"upgrading from 2.2 to 2.2.2, for example) :file:`site.py` will be " +"overwritten by the stock version. You'd have to remember that it was " +"modified and save a copy before doing the installation." +msgstr "" + +#: ../Doc/install/index.rst:731 +msgid "" +"There are two environment variables that can modify ``sys.path``. :envvar:" +"`PYTHONHOME` sets an alternate value for the prefix of the Python " +"installation. For example, if :envvar:`PYTHONHOME` is set to ``/www/" +"python``, the search path will be set to ``['', '/www/python/lib/pythonX." +"Y/', '/www/python/lib/pythonX.Y/plat-linux2', ...]``." +msgstr "" + +#: ../Doc/install/index.rst:737 +msgid "" +"The :envvar:`PYTHONPATH` variable can be set to a list of paths that will be " +"added to the beginning of ``sys.path``. For example, if :envvar:" +"`PYTHONPATH` is set to ``/www/python:/opt/py``, the search path will begin " +"with ``['/www/python', '/opt/py']``. (Note that directories must exist in " +"order to be added to ``sys.path``; the :mod:`site` module removes paths that " +"don't exist.)" +msgstr "" + +#: ../Doc/install/index.rst:744 +msgid "" +"Finally, ``sys.path`` is just a regular Python list, so any Python " +"application can modify it by adding or removing entries." +msgstr "" + +#: ../Doc/install/index.rst:751 +msgid "Distutils Configuration Files" +msgstr "" + +#: ../Doc/install/index.rst:753 +msgid "" +"As mentioned above, you can use Distutils configuration files to record " +"personal or site preferences for any Distutils options. That is, any option " +"to any command can be stored in one of two or three (depending on your " +"platform) configuration files, which will be consulted before the command-" +"line is parsed. This means that configuration files will override default " +"values, and the command-line will in turn override configuration files. " +"Furthermore, if multiple configuration files apply, values from \"earlier\" " +"files are overridden by \"later\" files." +msgstr "" + +#: ../Doc/install/index.rst:766 +msgid "Location and names of config files" +msgstr "" + +#: ../Doc/install/index.rst:768 +msgid "" +"The names and locations of the configuration files vary slightly across " +"platforms. On Unix and Mac OS X, the three configuration files (in the " +"order they are processed) are:" +msgstr "" + +#: ../Doc/install/index.rst:773 ../Doc/install/index.rst:785 +msgid "Location and filename" +msgstr "" + +#: ../Doc/install/index.rst:775 ../Doc/install/index.rst:787 +msgid "system" +msgstr "" + +#: ../Doc/install/index.rst:775 +msgid ":file:`{prefix}/lib/python{ver}/distutils/distutils.cfg`" +msgstr "" + +#: ../Doc/install/index.rst:777 ../Doc/install/index.rst:789 +msgid "personal" +msgstr "" + +#: ../Doc/install/index.rst:777 +msgid ":file:`$HOME/.pydistutils.cfg`" +msgstr "" + +#: ../Doc/install/index.rst:779 ../Doc/install/index.rst:791 +msgid "local" +msgstr "" + +#: ../Doc/install/index.rst:779 ../Doc/install/index.rst:791 +msgid ":file:`setup.cfg`" +msgstr "" + +#: ../Doc/install/index.rst:779 ../Doc/install/index.rst:791 +msgid "\\(3)" +msgstr "" + +#: ../Doc/install/index.rst:782 +msgid "And on Windows, the configuration files are:" +msgstr "" + +#: ../Doc/install/index.rst:787 +msgid ":file:`{prefix}\\\\Lib\\\\distutils\\\\distutils.cfg`" +msgstr "" + +#: ../Doc/install/index.rst:787 +msgid "\\(4)" +msgstr "" + +#: ../Doc/install/index.rst:789 +msgid ":file:`%HOME%\\\\pydistutils.cfg`" +msgstr "" + +#: ../Doc/install/index.rst:789 +msgid "\\(5)" +msgstr "" + +#: ../Doc/install/index.rst:794 +msgid "" +"On all platforms, the \"personal\" file can be temporarily disabled by " +"passing the `--no-user-cfg` option." +msgstr "" + +#: ../Doc/install/index.rst:800 +msgid "" +"Strictly speaking, the system-wide configuration file lives in the directory " +"where the Distutils are installed; under Python 1.6 and later on Unix, this " +"is as shown. For Python 1.5.2, the Distutils will normally be installed to :" +"file:`{prefix}/lib/python1.5/site-packages/distutils`, so the system " +"configuration file should be put there under Python 1.5.2." +msgstr "" + +#: ../Doc/install/index.rst:807 +msgid "" +"On Unix, if the :envvar:`HOME` environment variable is not defined, the " +"user's home directory will be determined with the :func:`getpwuid` function " +"from the standard :mod:`pwd` module. This is done by the :func:`os.path." +"expanduser` function used by Distutils." +msgstr "" + +#: ../Doc/install/index.rst:813 +msgid "" +"I.e., in the current directory (usually the location of the setup script)." +msgstr "" + +#: ../Doc/install/index.rst:816 +msgid "" +"(See also note (1).) Under Python 1.6 and later, Python's default " +"\"installation prefix\" is :file:`C:\\\\Python`, so the system configuration " +"file is normally :file:`C:\\\\Python\\\\Lib\\\\distutils\\\\distutils.cfg`. " +"Under Python 1.5.2, the default prefix was :file:`C:\\\\Program Files\\" +"\\Python`, and the Distutils were not part of the standard library---so the " +"system configuration file would be :file:`C:\\\\Program Files\\\\Python\\" +"\\distutils\\\\distutils.cfg` in a standard Python 1.5.2 installation under " +"Windows." +msgstr "" + +#: ../Doc/install/index.rst:825 +msgid "" +"On Windows, if the :envvar:`HOME` environment variable is not defined, :" +"envvar:`USERPROFILE` then :envvar:`HOMEDRIVE` and :envvar:`HOMEPATH` will be " +"tried. This is done by the :func:`os.path.expanduser` function used by " +"Distutils." +msgstr "" + +#: ../Doc/install/index.rst:834 +msgid "Syntax of config files" +msgstr "" + +#: ../Doc/install/index.rst:836 +msgid "" +"The Distutils configuration files all have the same syntax. The config " +"files are grouped into sections. There is one section for each Distutils " +"command, plus a ``global`` section for global options that affect every " +"command. Each section consists of one option per line, specified as " +"``option=value``." +msgstr "" + +#: ../Doc/install/index.rst:841 +msgid "" +"For example, the following is a complete config file that just forces all " +"commands to run quietly by default::" +msgstr "" + +#: ../Doc/install/index.rst:847 +msgid "" +"If this is installed as the system config file, it will affect all " +"processing of any Python module distribution by any user on the current " +"system. If it is installed as your personal config file (on systems that " +"support them), it will affect only module distributions processed by you. " +"And if it is used as the :file:`setup.cfg` for a particular module " +"distribution, it affects only that distribution." +msgstr "" + +#: ../Doc/install/index.rst:854 +msgid "" +"You could override the default \"build base\" directory and make the :" +"command:`build\\*` commands always forcibly rebuild all files with the " +"following::" +msgstr "" + +#: ../Doc/install/index.rst:862 +msgid "which corresponds to the command-line arguments ::" +msgstr "" + +#: ../Doc/install/index.rst:866 +msgid "" +"except that including the :command:`build` command on the command-line means " +"that command will be run. Including a particular command in config files " +"has no such implication; it only means that if the command is run, the " +"options in the config file will apply. (Or if other commands that derive " +"values from it are run, they will use the values in the config file.)" +msgstr "" + +#: ../Doc/install/index.rst:872 +msgid "" +"You can find out the complete list of options for any command using the :" +"option:`!--help` option, e.g.::" +msgstr "" + +#: ../Doc/install/index.rst:877 +msgid "" +"and you can find out the complete list of global options by using :option:" +"`!--help` without a command::" +msgstr "" + +#: ../Doc/install/index.rst:882 +msgid "" +"See also the \"Reference\" section of the \"Distributing Python Modules\" " +"manual." +msgstr "" + +#: ../Doc/install/index.rst:888 +msgid "Building Extensions: Tips and Tricks" +msgstr "" + +#: ../Doc/install/index.rst:890 +msgid "" +"Whenever possible, the Distutils try to use the configuration information " +"made available by the Python interpreter used to run the :file:`setup.py` " +"script. For example, the same compiler and linker flags used to compile " +"Python will also be used for compiling extensions. Usually this will work " +"well, but in complicated situations this might be inappropriate. This " +"section discusses how to override the usual Distutils behaviour." +msgstr "" + +#: ../Doc/install/index.rst:901 +msgid "Tweaking compiler/linker flags" +msgstr "" + +#: ../Doc/install/index.rst:903 +msgid "" +"Compiling a Python extension written in C or C++ will sometimes require " +"specifying custom flags for the compiler and linker in order to use a " +"particular library or produce a special kind of object code. This is " +"especially true if the extension hasn't been tested on your platform, or if " +"you're trying to cross-compile Python." +msgstr "" + +#: ../Doc/install/index.rst:909 +msgid "" +"In the most general case, the extension author might have foreseen that " +"compiling the extensions would be complicated, and provided a :file:`Setup` " +"file for you to edit. This will likely only be done if the module " +"distribution contains many separate extension modules, or if they often " +"require elaborate sets of compiler flags in order to work." +msgstr "" + +#: ../Doc/install/index.rst:915 +msgid "" +"A :file:`Setup` file, if present, is parsed in order to get a list of " +"extensions to build. Each line in a :file:`Setup` describes a single " +"module. Lines have the following structure::" +msgstr "" + +#: ../Doc/install/index.rst:922 +msgid "Let's examine each of the fields in turn." +msgstr "" + +#: ../Doc/install/index.rst:924 +msgid "" +"*module* is the name of the extension module to be built, and should be a " +"valid Python identifier. You can't just change this in order to rename a " +"module (edits to the source code would also be needed), so this should be " +"left alone." +msgstr "" + +#: ../Doc/install/index.rst:928 +msgid "" +"*sourcefile* is anything that's likely to be a source code file, at least " +"judging by the filename. Filenames ending in :file:`.c` are assumed to be " +"written in C, filenames ending in :file:`.C`, :file:`.cc`, and :file:`.c++` " +"are assumed to be C++, and filenames ending in :file:`.m` or :file:`.mm` are " +"assumed to be in Objective C." +msgstr "" + +#: ../Doc/install/index.rst:934 +msgid "" +"*cpparg* is an argument for the C preprocessor, and is anything starting " +"with :option:`!-I`, :option:`-D`, :option:`!-U` or :option:`-C`." +msgstr "" + +#: ../Doc/install/index.rst:937 +msgid "" +"*library* is anything ending in :file:`.a` or beginning with :option:`-l` " +"or :option:`-L`." +msgstr "" + +#: ../Doc/install/index.rst:940 +msgid "" +"If a particular platform requires a special library on your platform, you " +"can add it by editing the :file:`Setup` file and running ``python setup.py " +"build``. For example, if the module defined by the line ::" +msgstr "" + +#: ../Doc/install/index.rst:946 +msgid "" +"must be linked with the math library :file:`libm.a` on your platform, simply " +"add :option:`-lm` to the line::" +msgstr "" + +#: ../Doc/install/index.rst:951 +msgid "" +"Arbitrary switches intended for the compiler or the linker can be supplied " +"with the :option:`-Xcompiler` *arg* and :option:`-Xlinker` *arg* options::" +msgstr "" + +#: ../Doc/install/index.rst:956 +msgid "" +"The next option after :option:`-Xcompiler` and :option:`-Xlinker` will be " +"appended to the proper command line, so in the above example the compiler " +"will be passed the :option:`-o32` option, and the linker will be passed :" +"option:`-shared`. If a compiler option requires an argument, you'll have to " +"supply multiple :option:`-Xcompiler` options; for example, to pass ``-x c+" +"+`` the :file:`Setup` file would have to contain ``-Xcompiler -x -Xcompiler c" +"++``." +msgstr "" + +#: ../Doc/install/index.rst:963 +msgid "" +"Compiler flags can also be supplied through setting the :envvar:`CFLAGS` " +"environment variable. If set, the contents of :envvar:`CFLAGS` will be " +"added to the compiler flags specified in the :file:`Setup` file." +msgstr "" + +#: ../Doc/install/index.rst:971 +msgid "Using non-Microsoft compilers on Windows" +msgstr "" + +#: ../Doc/install/index.rst:978 +msgid "Borland/CodeGear C++" +msgstr "" + +#: ../Doc/install/index.rst:980 +msgid "" +"This subsection describes the necessary steps to use Distutils with the " +"Borland C++ compiler version 5.5. First you have to know that Borland's " +"object file format (OMF) is different from the format used by the Python " +"version you can download from the Python or ActiveState Web site. (Python " +"is built with Microsoft Visual C++, which uses COFF as the object file " +"format.) For this reason you have to convert Python's library :file:" +"`python25.lib` into the Borland format. You can do this as follows:" +msgstr "" + +#: ../Doc/install/index.rst:995 +msgid "" +"The :file:`coff2omf` program comes with the Borland compiler. The file :" +"file:`python25.lib` is in the :file:`Libs` directory of your Python " +"installation. If your extension uses other libraries (zlib, ...) you have " +"to convert them too." +msgstr "" + +#: ../Doc/install/index.rst:1000 +msgid "" +"The converted files have to reside in the same directories as the normal " +"libraries." +msgstr "" + +#: ../Doc/install/index.rst:1003 +msgid "" +"How does Distutils manage to use these libraries with their changed names? " +"If the extension needs a library (eg. :file:`foo`) Distutils checks first if " +"it finds a library with suffix :file:`_bcpp` (eg. :file:`foo_bcpp.lib`) and " +"then uses this library. In the case it doesn't find such a special library " +"it uses the default name (:file:`foo.lib`.) [#]_" +msgstr "" + +#: ../Doc/install/index.rst:1009 +msgid "" +"To let Distutils compile your extension with Borland C++ you now have to " +"type::" +msgstr "" + +#: ../Doc/install/index.rst:1013 +msgid "" +"If you want to use the Borland C++ compiler as the default, you could " +"specify this in your personal or system-wide configuration file for " +"Distutils (see section :ref:`inst-config-files`.)" +msgstr "" + +#: ../Doc/install/index.rst:1022 +msgid "`C++Builder Compiler `_" +msgstr "" + +#: ../Doc/install/index.rst:1021 +msgid "" +"Information about the free C++ compiler from Borland, including links to the " +"download pages." +msgstr "" + +#: ../Doc/install/index.rst:1025 +msgid "" +"`Creating Python Extensions Using Borland's Free Compiler `_" +msgstr "" + +#: ../Doc/install/index.rst:1025 +msgid "" +"Document describing how to use Borland's free command-line C++ compiler to " +"build Python." +msgstr "" + +#: ../Doc/install/index.rst:1030 +msgid "GNU C / Cygwin / MinGW" +msgstr "" + +#: ../Doc/install/index.rst:1032 +msgid "" +"This section describes the necessary steps to use Distutils with the GNU C/C+" +"+ compilers in their Cygwin and MinGW distributions. [#]_ For a Python " +"interpreter that was built with Cygwin, everything should work without any " +"of these following steps." +msgstr "" + +#: ../Doc/install/index.rst:1037 +msgid "" +"Not all extensions can be built with MinGW or Cygwin, but many can. " +"Extensions most likely to not work are those that use C++ or depend on " +"Microsoft Visual C extensions." +msgstr "" + +#: ../Doc/install/index.rst:1041 +msgid "To let Distutils compile your extension with Cygwin you have to type::" +msgstr "" + +#: ../Doc/install/index.rst:1045 +msgid "and for Cygwin in no-cygwin mode [#]_ or for MinGW type::" +msgstr "" + +#: ../Doc/install/index.rst:1049 +msgid "" +"If you want to use any of these options/compilers as default, you should " +"consider writing it in your personal or system-wide configuration file for " +"Distutils (see section :ref:`inst-config-files`.)" +msgstr "" + +#: ../Doc/install/index.rst:1054 +msgid "Older Versions of Python and MinGW" +msgstr "" + +#: ../Doc/install/index.rst:1055 +msgid "" +"The following instructions only apply if you're using a version of Python " +"inferior to 2.4.1 with a MinGW inferior to 3.0.0 (with " +"binutils-2.13.90-20030111-1)." +msgstr "" + +#: ../Doc/install/index.rst:1059 +msgid "" +"These compilers require some special libraries. This task is more complex " +"than for Borland's C++, because there is no program to convert the library. " +"First you have to create a list of symbols which the Python DLL exports. " +"(You can find a good program for this task at https://sourceforge.net/" +"projects/mingw/files/MinGW/Extension/pexports/)." +msgstr "" + +#: ../Doc/install/index.rst:1072 +msgid "" +"The location of an installed :file:`python25.dll` will depend on the " +"installation options and the version and language of Windows. In a \"just " +"for me\" installation, it will appear in the root of the installation " +"directory. In a shared installation, it will be located in the system " +"directory." +msgstr "" + +#: ../Doc/install/index.rst:1077 +msgid "" +"Then you can create from these information an import library for gcc. ::" +msgstr "" + +#: ../Doc/install/index.rst:1081 +msgid "" +"The resulting library has to be placed in the same directory as :file:" +"`python25.lib`. (Should be the :file:`libs` directory under your Python " +"installation directory.)" +msgstr "" + +#: ../Doc/install/index.rst:1085 +msgid "" +"If your extension uses other libraries (zlib,...) you might have to convert " +"them too. The converted files have to reside in the same directories as the " +"normal libraries do." +msgstr "" + +#: ../Doc/install/index.rst:1092 +msgid "" +"`Building Python modules on MS Windows platform with MinGW `_" +msgstr "" + +#: ../Doc/install/index.rst:1093 +msgid "" +"Information about building the required libraries for the MinGW environment." +msgstr "" + +#: ../Doc/install/index.rst:1097 +msgid "Footnotes" +msgstr "" + +#: ../Doc/install/index.rst:1098 +msgid "" +"This also means you could replace all existing COFF-libraries with OMF-" +"libraries of the same name." +msgstr "" + +#: ../Doc/install/index.rst:1101 +msgid "" +"Check https://www.sourceware.org/cygwin/ and http://www.mingw.org/ for more " +"information" +msgstr "" + +#: ../Doc/install/index.rst:1104 +msgid "" +"Then you have no POSIX emulation available, but you also don't need :file:" +"`cygwin1.dll`." +msgstr "" diff --git a/installing.po b/installing.po new file mode 100644 index 00000000..f4611a82 --- /dev/null +++ b/installing.po @@ -0,0 +1,327 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/installing/index.rst:7 +msgid "Installing Python Modules" +msgstr "" + +#: ../Doc/installing/index.rst:9 +msgid "distutils-sig@python.org" +msgstr "" + +#: ../Doc/installing/index.rst:11 +msgid "" +"As a popular open source development project, Python has an active " +"supporting community of contributors and users that also make their software " +"available for other Python developers to use under open source license terms." +msgstr "" + +#: ../Doc/installing/index.rst:15 +msgid "" +"This allows Python users to share and collaborate effectively, benefiting " +"from the solutions others have already created to common (and sometimes even " +"rare!) problems, as well as potentially contributing their own solutions to " +"the common pool." +msgstr "" + +#: ../Doc/installing/index.rst:20 +msgid "" +"This guide covers the installation part of the process. For a guide to " +"creating and sharing your own Python projects, refer to the :ref:" +"`distribution guide `." +msgstr "" + +#: ../Doc/installing/index.rst:26 +msgid "" +"For corporate and other institutional users, be aware that many " +"organisations have their own policies around using and contributing to open " +"source software. Please take such policies into account when making use of " +"the distribution and installation tools provided with Python." +msgstr "" + +#: ../Doc/installing/index.rst:33 +msgid "Key terms" +msgstr "" + +#: ../Doc/installing/index.rst:35 +msgid "" +"``pip`` is the preferred installer program. Starting with Python 3.4, it is " +"included by default with the Python binary installers." +msgstr "" + +#: ../Doc/installing/index.rst:37 +msgid "" +"A *virtual environment* is a semi-isolated Python environment that allows " +"packages to be installed for use by a particular application, rather than " +"being installed system wide." +msgstr "" + +#: ../Doc/installing/index.rst:40 +msgid "" +"``venv`` is the standard tool for creating virtual environments, and has " +"been part of Python since Python 3.3. Starting with Python 3.4, it defaults " +"to installing ``pip`` into all created virtual environments." +msgstr "" + +#: ../Doc/installing/index.rst:43 +msgid "" +"``virtualenv`` is a third party alternative (and predecessor) to ``venv``. " +"It allows virtual environments to be used on versions of Python prior to " +"3.4, which either don't provide ``venv`` at all, or aren't able to " +"automatically install ``pip`` into created environments." +msgstr "" + +#: ../Doc/installing/index.rst:47 +msgid "" +"The `Python Packaging Index `__ is a public " +"repository of open source licensed packages made available for use by other " +"Python users." +msgstr "" + +#: ../Doc/installing/index.rst:50 +msgid "" +"the `Python Packaging Authority `__ are the " +"group of developers and documentation authors responsible for the " +"maintenance and evolution of the standard packaging tools and the associated " +"metadata and file format standards. They maintain a variety of tools, " +"documentation, and issue trackers on both `GitHub `__ and `BitBucket `__." +msgstr "" + +#: ../Doc/installing/index.rst:57 +msgid "" +"``distutils`` is the original build and distribution system first added to " +"the Python standard library in 1998. While direct use of ``distutils`` is " +"being phased out, it still laid the foundation for the current packaging and " +"distribution infrastructure, and it not only remains part of the standard " +"library, but its name lives on in other ways (such as the name of the " +"mailing list used to coordinate Python packaging standards development)." +msgstr "" + +#: ../Doc/installing/index.rst:65 +msgid "" +"``pyvenv`` was the recommended tool for creating virtual environments for " +"Python 3.3 and 3.4, and is `deprecated in Python 3.6 `_." +msgstr "" + +#: ../Doc/installing/index.rst:70 +msgid "" +"The use of ``venv`` is now recommended for creating virtual environments." +msgstr "" + +#: ../Doc/installing/index.rst:75 +msgid "" +"`Python Packaging User Guide: Creating and using virtual environments " +"`__" +msgstr "" + +#: ../Doc/installing/index.rst:80 +msgid "Basic usage" +msgstr "" + +#: ../Doc/installing/index.rst:82 +msgid "" +"The standard packaging tools are all designed to be used from the command " +"line." +msgstr "" + +#: ../Doc/installing/index.rst:85 +msgid "" +"The following command will install the latest version of a module and its " +"dependencies from the Python Packaging Index::" +msgstr "" + +#: ../Doc/installing/index.rst:92 +msgid "" +"For POSIX users (including Mac OS X and Linux users), the examples in this " +"guide assume the use of a :term:`virtual environment`." +msgstr "" + +#: ../Doc/installing/index.rst:95 +msgid "" +"For Windows users, the examples in this guide assume that the option to " +"adjust the system PATH environment variable was selected when installing " +"Python." +msgstr "" + +#: ../Doc/installing/index.rst:99 +msgid "" +"It's also possible to specify an exact or minimum version directly on the " +"command line. When using comparator operators such as ``>``, ``<`` or some " +"other special character which get interpreted by shell, the package name and " +"the version should be enclosed within double quotes::" +msgstr "" + +#: ../Doc/installing/index.rst:107 +msgid "" +"Normally, if a suitable module is already installed, attempting to install " +"it again will have no effect. Upgrading existing modules must be requested " +"explicitly::" +msgstr "" + +#: ../Doc/installing/index.rst:113 +msgid "" +"More information and resources regarding ``pip`` and its capabilities can be " +"found in the `Python Packaging User Guide `__." +msgstr "" + +#: ../Doc/installing/index.rst:116 +msgid "" +"Creation of virtual environments is done through the :mod:`venv` module. " +"Installing packages into an active virtual environment uses the commands " +"shown above." +msgstr "" + +#: ../Doc/installing/index.rst:122 +msgid "" +"`Python Packaging User Guide: Installing Python Distribution Packages " +"`__" +msgstr "" + +#: ../Doc/installing/index.rst:127 +msgid "How do I ...?" +msgstr "" + +#: ../Doc/installing/index.rst:129 +msgid "These are quick answers or links for some common tasks." +msgstr "" + +#: ../Doc/installing/index.rst:132 +msgid "... install ``pip`` in versions of Python prior to Python 3.4?" +msgstr "" + +#: ../Doc/installing/index.rst:134 +msgid "" +"Python only started bundling ``pip`` with Python 3.4. For earlier versions, " +"``pip`` needs to be \"bootstrapped\" as described in the Python Packaging " +"User Guide." +msgstr "" + +#: ../Doc/installing/index.rst:140 +msgid "" +"`Python Packaging User Guide: Requirements for Installing Packages `__" +msgstr "" + +#: ../Doc/installing/index.rst:147 +msgid "... install packages just for the current user?" +msgstr "" + +#: ../Doc/installing/index.rst:149 +msgid "" +"Passing the ``--user`` option to ``python -m pip install`` will install a " +"package just for the current user, rather than for all users of the system." +msgstr "" + +#: ../Doc/installing/index.rst:154 +msgid "... install scientific Python packages?" +msgstr "" + +#: ../Doc/installing/index.rst:156 +msgid "" +"A number of scientific Python packages have complex binary dependencies, and " +"aren't currently easy to install using ``pip`` directly. At this point in " +"time, it will often be easier for users to install these packages by `other " +"means `__ rather than attempting to " +"install them with ``pip``." +msgstr "" + +#: ../Doc/installing/index.rst:164 +msgid "" +"`Python Packaging User Guide: Installing Scientific Packages `__" +msgstr "" + +#: ../Doc/installing/index.rst:169 +msgid "... work with multiple versions of Python installed in parallel?" +msgstr "" + +#: ../Doc/installing/index.rst:171 +msgid "" +"On Linux, Mac OS X, and other POSIX systems, use the versioned Python " +"commands in combination with the ``-m`` switch to run the appropriate copy " +"of ``pip``::" +msgstr "" + +#: ../Doc/installing/index.rst:180 +msgid "Appropriately versioned ``pip`` commands may also be available." +msgstr "" + +#: ../Doc/installing/index.rst:182 +msgid "" +"On Windows, use the ``py`` Python launcher in combination with the ``-m`` " +"switch::" +msgstr "" + +#: ../Doc/installing/index.rst:199 +msgid "Common installation issues" +msgstr "" + +#: ../Doc/installing/index.rst:202 +msgid "Installing into the system Python on Linux" +msgstr "" + +#: ../Doc/installing/index.rst:204 +msgid "" +"On Linux systems, a Python installation will typically be included as part " +"of the distribution. Installing into this Python installation requires root " +"access to the system, and may interfere with the operation of the system " +"package manager and other components of the system if a component is " +"unexpectedly upgraded using ``pip``." +msgstr "" + +#: ../Doc/installing/index.rst:210 +msgid "" +"On such systems, it is often better to use a virtual environment or a per-" +"user installation when installing packages with ``pip``." +msgstr "" + +#: ../Doc/installing/index.rst:215 +msgid "Installing binary extensions" +msgstr "" + +#: ../Doc/installing/index.rst:217 +msgid "" +"Python has typically relied heavily on source based distribution, with end " +"users being expected to compile extension modules from source as part of the " +"installation process." +msgstr "" + +#: ../Doc/installing/index.rst:221 +msgid "" +"With the introduction of support for the binary ``wheel`` format, and the " +"ability to publish wheels for at least Windows and Mac OS X through the " +"Python Packaging Index, this problem is expected to diminish over time, as " +"users are more regularly able to install pre-built extensions rather than " +"needing to build them themselves." +msgstr "" + +#: ../Doc/installing/index.rst:227 +msgid "" +"Some of the solutions for installing `scientific software `__ that are not yet available as pre-built ``wheel`` " +"files may also help with obtaining other binary extensions without needing " +"to build them locally." +msgstr "" + +#: ../Doc/installing/index.rst:234 +msgid "" +"`Python Packaging User Guide: Binary Extensions `__" +msgstr "" diff --git a/library.po b/library.po new file mode 100644 index 00000000..08dfe011 --- /dev/null +++ b/library.po @@ -0,0 +1,151337 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/library/2to3.rst:4 +msgid "2to3 - Automated Python 2 to 3 code translation" +msgstr "" + +#: ../Doc/library/2to3.rst:8 +msgid "" +"2to3 is a Python program that reads Python 2.x source code and applies a " +"series of *fixers* to transform it into valid Python 3.x code. The standard " +"library contains a rich set of fixers that will handle almost all code. " +"2to3 supporting library :mod:`lib2to3` is, however, a flexible and generic " +"library, so it is possible to write your own fixers for 2to3. :mod:" +"`lib2to3` could also be adapted to custom applications in which Python code " +"needs to be edited automatically." +msgstr "" + +#: ../Doc/library/2to3.rst:20 +msgid "Using 2to3" +msgstr "" + +#: ../Doc/library/2to3.rst:22 +msgid "" +"2to3 will usually be installed with the Python interpreter as a script. It " +"is also located in the :file:`Tools/scripts` directory of the Python root." +msgstr "" + +#: ../Doc/library/2to3.rst:25 +msgid "" +"2to3's basic arguments are a list of files or directories to transform. The " +"directories are recursively traversed for Python sources." +msgstr "" + +#: ../Doc/library/2to3.rst:28 +msgid "Here is a sample Python 2.x source file, :file:`example.py`::" +msgstr "" + +#: ../Doc/library/2to3.rst:36 +msgid "It can be converted to Python 3.x code via 2to3 on the command line:" +msgstr "" + +#: ../Doc/library/2to3.rst:42 +msgid "" +"A diff against the original source file is printed. 2to3 can also write the " +"needed modifications right back to the source file. (A backup of the " +"original file is made unless :option:`-n` is also given.) Writing the " +"changes back is enabled with the :option:`-w` flag:" +msgstr "" + +#: ../Doc/library/2to3.rst:51 +msgid "After transformation, :file:`example.py` looks like this::" +msgstr "" + +#: ../Doc/library/2to3.rst:59 +msgid "" +"Comments and exact indentation are preserved throughout the translation " +"process." +msgstr "" + +#: ../Doc/library/2to3.rst:61 +msgid "" +"By default, 2to3 runs a set of :ref:`predefined fixers <2to3-fixers>`. The :" +"option:`!-l` flag lists all available fixers. An explicit set of fixers to " +"run can be given with :option:`-f`. Likewise the :option:`!-x` explicitly " +"disables a fixer. The following example runs only the ``imports`` and " +"``has_key`` fixers:" +msgstr "" + +#: ../Doc/library/2to3.rst:70 +msgid "This command runs every fixer except the ``apply`` fixer:" +msgstr "" + +#: ../Doc/library/2to3.rst:76 +msgid "" +"Some fixers are *explicit*, meaning they aren't run by default and must be " +"listed on the command line to be run. Here, in addition to the default " +"fixers, the ``idioms`` fixer is run:" +msgstr "" + +#: ../Doc/library/2to3.rst:84 +msgid "Notice how passing ``all`` enables all default fixers." +msgstr "" + +#: ../Doc/library/2to3.rst:86 +msgid "" +"Sometimes 2to3 will find a place in your source code that needs to be " +"changed, but 2to3 cannot fix automatically. In this case, 2to3 will print a " +"warning beneath the diff for a file. You should address the warning in " +"order to have compliant 3.x code." +msgstr "" + +#: ../Doc/library/2to3.rst:91 +msgid "" +"2to3 can also refactor doctests. To enable this mode, use the :option:`!-d` " +"flag. Note that *only* doctests will be refactored. This also doesn't " +"require the module to be valid Python. For example, doctest like examples " +"in a reST document could also be refactored with this option." +msgstr "" + +#: ../Doc/library/2to3.rst:96 +msgid "" +"The :option:`!-v` option enables output of more information on the " +"translation process." +msgstr "" + +#: ../Doc/library/2to3.rst:99 +msgid "" +"Since some print statements can be parsed as function calls or statements, " +"2to3 cannot always read files containing the print function. When 2to3 " +"detects the presence of the ``from __future__ import print_function`` " +"compiler directive, it modifies its internal grammar to interpret :func:" +"`print` as a function. This change can also be enabled manually with the :" +"option:`-p` flag. Use :option:`-p` to run fixers on code that already has " +"had its print statements converted." +msgstr "" + +#: ../Doc/library/2to3.rst:107 +msgid "" +"The :option:`-o` or :option:`--output-dir` option allows specification of an " +"alternate directory for processed output files to be written to. The :" +"option:`-n` flag is required when using this as backup files do not make " +"sense when not overwriting the input files." +msgstr "" + +#: ../Doc/library/2to3.rst:112 +msgid "The :option:`-o` option was added." +msgstr "" + +#: ../Doc/library/2to3.rst:115 +msgid "" +"The :option:`!-W` or :option:`--write-unchanged-files` flag tells 2to3 to " +"always write output files even if no changes were required to the file. " +"This is most useful with :option:`-o` so that an entire Python source tree " +"is copied with translation from one directory to another. This option " +"implies the :option:`-w` flag as it would not make sense otherwise." +msgstr "" + +#: ../Doc/library/2to3.rst:121 +msgid "The :option:`!-W` flag was added." +msgstr "" + +#: ../Doc/library/2to3.rst:124 +msgid "" +"The :option:`--add-suffix` option specifies a string to append to all output " +"filenames. The :option:`-n` flag is required when specifying this as " +"backups are not necessary when writing to different filenames. Example:" +msgstr "" + +#: ../Doc/library/2to3.rst:132 +msgid "Will cause a converted file named ``example.py3`` to be written." +msgstr "" + +#: ../Doc/library/2to3.rst:134 +msgid "The :option:`--add-suffix` option was added." +msgstr "" + +#: ../Doc/library/2to3.rst:137 +msgid "To translate an entire project from one directory tree to another use:" +msgstr "" + +#: ../Doc/library/2to3.rst:147 +msgid "Fixers" +msgstr "" + +#: ../Doc/library/2to3.rst:149 +msgid "" +"Each step of transforming code is encapsulated in a fixer. The command " +"``2to3 -l`` lists them. As :ref:`documented above <2to3-using>`, each can " +"be turned on and off individually. They are described here in more detail." +msgstr "" + +#: ../Doc/library/2to3.rst:156 +msgid "" +"Removes usage of :func:`apply`. For example ``apply(function, *args, " +"**kwargs)`` is converted to ``function(*args, **kwargs)``." +msgstr "" + +#: ../Doc/library/2to3.rst:161 +msgid "Replaces deprecated :mod:`unittest` method names with the correct ones." +msgstr "" + +#: ../Doc/library/2to3.rst:164 ../Doc/library/2to3.rst:358 +#: ../Doc/library/time.rst:93 +msgid "From" +msgstr "" + +#: ../Doc/library/2to3.rst:164 ../Doc/library/2to3.rst:358 +#: ../Doc/library/time.rst:93 +msgid "To" +msgstr "" + +#: ../Doc/library/2to3.rst:166 +msgid "``failUnlessEqual(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:166 ../Doc/library/2to3.rst:168 +msgid ":meth:`assertEqual(a, b) `" +msgstr "" + +#: ../Doc/library/2to3.rst:168 +msgid "``assertEquals(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:170 +msgid "``failIfEqual(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:170 ../Doc/library/2to3.rst:172 +msgid ":meth:`assertNotEqual(a, b) `" +msgstr "" + +#: ../Doc/library/2to3.rst:172 +msgid "``assertNotEquals(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:174 +msgid "``failUnless(a)``" +msgstr "" + +#: ../Doc/library/2to3.rst:174 ../Doc/library/2to3.rst:176 +msgid ":meth:`assertTrue(a) `" +msgstr "" + +#: ../Doc/library/2to3.rst:176 +msgid "``assert_(a)``" +msgstr "" + +#: ../Doc/library/2to3.rst:178 +msgid "``failIf(a)``" +msgstr "" + +#: ../Doc/library/2to3.rst:178 +msgid ":meth:`assertFalse(a) `" +msgstr "" + +#: ../Doc/library/2to3.rst:180 +msgid "``failUnlessRaises(exc, cal)``" +msgstr "" + +#: ../Doc/library/2to3.rst:180 +msgid ":meth:`assertRaises(exc, cal) `" +msgstr "" + +#: ../Doc/library/2to3.rst:182 +msgid "``failUnlessAlmostEqual(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:182 ../Doc/library/2to3.rst:184 +msgid ":meth:`assertAlmostEqual(a, b) `" +msgstr "" + +#: ../Doc/library/2to3.rst:184 +msgid "``assertAlmostEquals(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:186 +msgid "``failIfAlmostEqual(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:186 ../Doc/library/2to3.rst:188 +msgid "" +":meth:`assertNotAlmostEqual(a, b) `" +msgstr "" + +#: ../Doc/library/2to3.rst:188 +msgid "``assertNotAlmostEquals(a, b)``" +msgstr "" + +#: ../Doc/library/2to3.rst:194 +msgid "Converts :class:`basestring` to :class:`str`." +msgstr "" + +#: ../Doc/library/2to3.rst:198 +msgid "" +"Converts :class:`buffer` to :class:`memoryview`. This fixer is optional " +"because the :class:`memoryview` API is similar but not exactly the same as " +"that of :class:`buffer`." +msgstr "" + +#: ../Doc/library/2to3.rst:204 +msgid "" +"Converts ``callable(x)`` to ``isinstance(x, collections.Callable)``, adding " +"an import to :mod:`collections` if needed. Note ``callable(x)`` has returned " +"in Python 3.2, so if you do not intend to support Python 3.1, you can " +"disable this fixer." +msgstr "" + +#: ../Doc/library/2to3.rst:211 +msgid "" +"Fixes dictionary iteration methods. :meth:`dict.iteritems` is converted to :" +"meth:`dict.items`, :meth:`dict.iterkeys` to :meth:`dict.keys`, and :meth:" +"`dict.itervalues` to :meth:`dict.values`. Similarly, :meth:`dict." +"viewitems`, :meth:`dict.viewkeys` and :meth:`dict.viewvalues` are converted " +"respectively to :meth:`dict.items`, :meth:`dict.keys` and :meth:`dict." +"values`. It also wraps existing usages of :meth:`dict.items`, :meth:`dict." +"keys`, and :meth:`dict.values` in a call to :class:`list`." +msgstr "" + +#: ../Doc/library/2to3.rst:221 +msgid "Converts ``except X, T`` to ``except X as T``." +msgstr "" + +#: ../Doc/library/2to3.rst:225 +msgid "Converts the ``exec`` statement to the :func:`exec` function." +msgstr "" + +#: ../Doc/library/2to3.rst:229 +msgid "" +"Removes usage of :func:`execfile`. The argument to :func:`execfile` is " +"wrapped in calls to :func:`open`, :func:`compile`, and :func:`exec`." +msgstr "" + +#: ../Doc/library/2to3.rst:234 +msgid "" +"Changes assignment of :attr:`sys.exitfunc` to use of the :mod:`atexit` " +"module." +msgstr "" + +#: ../Doc/library/2to3.rst:239 +msgid "Wraps :func:`filter` usage in a :class:`list` call." +msgstr "" + +#: ../Doc/library/2to3.rst:243 +msgid "" +"Fixes function attributes that have been renamed. For example, " +"``my_function.func_closure`` is converted to ``my_function.__closure__``." +msgstr "" + +#: ../Doc/library/2to3.rst:248 +msgid "Removes ``from __future__ import new_feature`` statements." +msgstr "" + +#: ../Doc/library/2to3.rst:252 +msgid "Renames :func:`os.getcwdu` to :func:`os.getcwd`." +msgstr "" + +#: ../Doc/library/2to3.rst:256 +msgid "Changes ``dict.has_key(key)`` to ``key in dict``." +msgstr "" + +#: ../Doc/library/2to3.rst:260 +msgid "" +"This optional fixer performs several transformations that make Python code " +"more idiomatic. Type comparisons like ``type(x) is SomeClass`` and " +"``type(x) == SomeClass`` are converted to ``isinstance(x, SomeClass)``. " +"``while 1`` becomes ``while True``. This fixer also tries to make use of :" +"func:`sorted` in appropriate places. For example, this block ::" +msgstr "" + +#: ../Doc/library/2to3.rst:269 +msgid "is changed to ::" +msgstr "" + +#: ../Doc/library/2to3.rst:275 +msgid "Detects sibling imports and converts them to relative imports." +msgstr "" + +#: ../Doc/library/2to3.rst:279 +msgid "Handles module renames in the standard library." +msgstr "" + +#: ../Doc/library/2to3.rst:283 +msgid "" +"Handles other modules renames in the standard library. It is separate from " +"the :2to3fixer:`imports` fixer only because of technical limitations." +msgstr "" + +#: ../Doc/library/2to3.rst:288 +msgid "Converts ``input(prompt)`` to ``eval(input(prompt))``." +msgstr "" + +#: ../Doc/library/2to3.rst:292 +msgid "Converts :func:`intern` to :func:`sys.intern`." +msgstr "" + +#: ../Doc/library/2to3.rst:296 +msgid "" +"Fixes duplicate types in the second argument of :func:`isinstance`. For " +"example, ``isinstance(x, (int, int))`` is converted to ``isinstance(x, " +"(int))``." +msgstr "" + +#: ../Doc/library/2to3.rst:302 +msgid "" +"Removes imports of :func:`itertools.ifilter`, :func:`itertools.izip`, and :" +"func:`itertools.imap`. Imports of :func:`itertools.ifilterfalse` are also " +"changed to :func:`itertools.filterfalse`." +msgstr "" + +#: ../Doc/library/2to3.rst:308 +msgid "" +"Changes usage of :func:`itertools.ifilter`, :func:`itertools.izip`, and :" +"func:`itertools.imap` to their built-in equivalents. :func:`itertools." +"ifilterfalse` is changed to :func:`itertools.filterfalse`." +msgstr "" + +#: ../Doc/library/2to3.rst:314 +msgid "Renames :class:`long` to :class:`int`." +msgstr "" + +#: ../Doc/library/2to3.rst:318 +msgid "" +"Wraps :func:`map` in a :class:`list` call. It also changes ``map(None, x)`` " +"to ``list(x)``. Using ``from future_builtins import map`` disables this " +"fixer." +msgstr "" + +#: ../Doc/library/2to3.rst:324 +msgid "" +"Converts the old metaclass syntax (``__metaclass__ = Meta`` in the class " +"body) to the new (``class X(metaclass=Meta)``)." +msgstr "" + +#: ../Doc/library/2to3.rst:329 +msgid "" +"Fixes old method attribute names. For example, ``meth.im_func`` is " +"converted to ``meth.__func__``." +msgstr "" + +#: ../Doc/library/2to3.rst:334 +msgid "Converts the old not-equal syntax, ``<>``, to ``!=``." +msgstr "" + +#: ../Doc/library/2to3.rst:338 +msgid "" +"Converts the use of iterator's :meth:`~iterator.next` methods to the :func:" +"`next` function. It also renames :meth:`next` methods to :meth:`~iterator." +"__next__`." +msgstr "" + +#: ../Doc/library/2to3.rst:344 +msgid "Renames :meth:`__nonzero__` to :meth:`~object.__bool__`." +msgstr "" + +#: ../Doc/library/2to3.rst:348 +msgid "Converts octal literals into the new syntax." +msgstr "" + +#: ../Doc/library/2to3.rst:352 +msgid "" +"Converts calls to various functions in the :mod:`operator` module to other, " +"but equivalent, function calls. When needed, the appropriate ``import`` " +"statements are added, e.g. ``import collections``. The following mapping " +"are made:" +msgstr "" + +#: ../Doc/library/2to3.rst:360 +msgid "``operator.isCallable(obj)``" +msgstr "" + +#: ../Doc/library/2to3.rst:360 +msgid "``hasattr(obj, '__call__')``" +msgstr "" + +#: ../Doc/library/2to3.rst:361 +msgid "``operator.sequenceIncludes(obj)``" +msgstr "" + +#: ../Doc/library/2to3.rst:361 +msgid "``operator.contains(obj)``" +msgstr "" + +#: ../Doc/library/2to3.rst:362 +msgid "``operator.isSequenceType(obj)``" +msgstr "" + +#: ../Doc/library/2to3.rst:362 +msgid "``isinstance(obj, collections.Sequence)``" +msgstr "" + +#: ../Doc/library/2to3.rst:363 +msgid "``operator.isMappingType(obj)``" +msgstr "" + +#: ../Doc/library/2to3.rst:363 +msgid "``isinstance(obj, collections.Mapping)``" +msgstr "" + +#: ../Doc/library/2to3.rst:364 +msgid "``operator.isNumberType(obj)``" +msgstr "" + +#: ../Doc/library/2to3.rst:364 +msgid "``isinstance(obj, numbers.Number)``" +msgstr "" + +#: ../Doc/library/2to3.rst:365 +msgid "``operator.repeat(obj, n)``" +msgstr "" + +#: ../Doc/library/2to3.rst:365 +msgid "``operator.mul(obj, n)``" +msgstr "" + +#: ../Doc/library/2to3.rst:366 +msgid "``operator.irepeat(obj, n)``" +msgstr "" + +#: ../Doc/library/2to3.rst:366 +msgid "``operator.imul(obj, n)``" +msgstr "" + +#: ../Doc/library/2to3.rst:371 +msgid "" +"Add extra parenthesis where they are required in list comprehensions. For " +"example, ``[x for x in 1, 2]`` becomes ``[x for x in (1, 2)]``." +msgstr "" + +#: ../Doc/library/2to3.rst:376 +msgid "Converts the ``print`` statement to the :func:`print` function." +msgstr "" + +#: ../Doc/library/2to3.rst:380 +msgid "" +"Converts ``raise E, V`` to ``raise E(V)``, and ``raise E, V, T`` to ``raise " +"E(V).with_traceback(T)``. If ``E`` is a tuple, the translation will be " +"incorrect because substituting tuples for exceptions has been removed in 3.0." +msgstr "" + +#: ../Doc/library/2to3.rst:386 +msgid "Converts :func:`raw_input` to :func:`input`." +msgstr "" + +#: ../Doc/library/2to3.rst:390 +msgid "Handles the move of :func:`reduce` to :func:`functools.reduce`." +msgstr "" + +#: ../Doc/library/2to3.rst:394 +msgid "Converts :func:`reload` to :func:`imp.reload`." +msgstr "" + +#: ../Doc/library/2to3.rst:398 +msgid "Changes :data:`sys.maxint` to :data:`sys.maxsize`." +msgstr "" + +#: ../Doc/library/2to3.rst:402 +msgid "Replaces backtick repr with the :func:`repr` function." +msgstr "" + +#: ../Doc/library/2to3.rst:406 +msgid "" +"Replaces use of the :class:`set` constructor with set literals. This fixer " +"is optional." +msgstr "" + +#: ../Doc/library/2to3.rst:411 +msgid "Renames :exc:`StandardError` to :exc:`Exception`." +msgstr "" + +#: ../Doc/library/2to3.rst:415 +msgid "" +"Changes the deprecated :data:`sys.exc_value`, :data:`sys.exc_type`, :data:" +"`sys.exc_traceback` to use :func:`sys.exc_info`." +msgstr "" + +#: ../Doc/library/2to3.rst:420 +msgid "Fixes the API change in generator's :meth:`throw` method." +msgstr "" + +#: ../Doc/library/2to3.rst:424 +msgid "" +"Removes implicit tuple parameter unpacking. This fixer inserts temporary " +"variables." +msgstr "" + +#: ../Doc/library/2to3.rst:429 +msgid "" +"Fixes code broken from the removal of some members in the :mod:`types` " +"module." +msgstr "" + +#: ../Doc/library/2to3.rst:434 +msgid "Renames :class:`unicode` to :class:`str`." +msgstr "" + +#: ../Doc/library/2to3.rst:438 +msgid "" +"Handles the rename of :mod:`urllib` and :mod:`urllib2` to the :mod:`urllib` " +"package." +msgstr "" + +#: ../Doc/library/2to3.rst:443 +msgid "" +"Removes excess whitespace from comma separated items. This fixer is " +"optional." +msgstr "" + +#: ../Doc/library/2to3.rst:448 +msgid "" +"Renames :func:`xrange` to :func:`range` and wraps existing :func:`range` " +"calls with :class:`list`." +msgstr "" + +#: ../Doc/library/2to3.rst:453 +msgid "Changes ``for x in file.xreadlines()`` to ``for x in file``." +msgstr "" + +#: ../Doc/library/2to3.rst:457 +msgid "" +"Wraps :func:`zip` usage in a :class:`list` call. This is disabled when " +"``from future_builtins import zip`` appears." +msgstr "" + +#: ../Doc/library/2to3.rst:462 +msgid ":mod:`lib2to3` - 2to3's library" +msgstr "" + +#: ../Doc/library/2to3.rst:471 +msgid "**Source code:** :source:`Lib/lib2to3/`" +msgstr "" + +#: ../Doc/library/2to3.rst:477 +msgid "" +"The :mod:`lib2to3` API should be considered unstable and may change " +"drastically in the future." +msgstr "" + +#: ../Doc/library/__future__.rst:2 +msgid ":mod:`__future__` --- Future statement definitions" +msgstr "" + +#: ../Doc/library/__future__.rst:7 +msgid "**Source code:** :source:`Lib/__future__.py`" +msgstr "" + +#: ../Doc/library/__future__.rst:11 +msgid ":mod:`__future__` is a real module, and serves three purposes:" +msgstr "" + +#: ../Doc/library/__future__.rst:13 +msgid "" +"To avoid confusing existing tools that analyze import statements and expect " +"to find the modules they're importing." +msgstr "" + +#: ../Doc/library/__future__.rst:16 +msgid "" +"To ensure that :ref:`future statements ` run under releases prior to " +"2.1 at least yield runtime exceptions (the import of :mod:`__future__` will " +"fail, because there was no module of that name prior to 2.1)." +msgstr "" + +#: ../Doc/library/__future__.rst:20 +msgid "" +"To document when incompatible changes were introduced, and when they will be " +"--- or were --- made mandatory. This is a form of executable documentation, " +"and can be inspected programmatically via importing :mod:`__future__` and " +"examining its contents." +msgstr "" + +#: ../Doc/library/__future__.rst:25 +msgid "Each statement in :file:`__future__.py` is of the form::" +msgstr "" + +#: ../Doc/library/__future__.rst:31 +msgid "" +"where, normally, *OptionalRelease* is less than *MandatoryRelease*, and both " +"are 5-tuples of the same form as :data:`sys.version_info`::" +msgstr "" + +#: ../Doc/library/__future__.rst:41 +msgid "" +"*OptionalRelease* records the first release in which the feature was " +"accepted." +msgstr "" + +#: ../Doc/library/__future__.rst:43 +msgid "" +"In the case of a *MandatoryRelease* that has not yet occurred, " +"*MandatoryRelease* predicts the release in which the feature will become " +"part of the language." +msgstr "" + +#: ../Doc/library/__future__.rst:47 +msgid "" +"Else *MandatoryRelease* records when the feature became part of the " +"language; in releases at or after that, modules no longer need a future " +"statement to use the feature in question, but may continue to use such " +"imports." +msgstr "" + +#: ../Doc/library/__future__.rst:51 +msgid "" +"*MandatoryRelease* may also be ``None``, meaning that a planned feature got " +"dropped." +msgstr "" + +#: ../Doc/library/__future__.rst:54 +msgid "" +"Instances of class :class:`_Feature` have two corresponding methods, :meth:" +"`getOptionalRelease` and :meth:`getMandatoryRelease`." +msgstr "" + +#: ../Doc/library/__future__.rst:57 +msgid "" +"*CompilerFlag* is the (bitfield) flag that should be passed in the fourth " +"argument to the built-in function :func:`compile` to enable the feature in " +"dynamically compiled code. This flag is stored in the :attr:`compiler_flag` " +"attribute on :class:`_Feature` instances." +msgstr "" + +#: ../Doc/library/__future__.rst:62 +msgid "" +"No feature description will ever be deleted from :mod:`__future__`. Since " +"its introduction in Python 2.1 the following features have found their way " +"into the language using this mechanism:" +msgstr "" + +#: ../Doc/library/__future__.rst:67 +msgid "feature" +msgstr "" + +#: ../Doc/library/__future__.rst:67 +msgid "optional in" +msgstr "" + +#: ../Doc/library/__future__.rst:67 +msgid "mandatory in" +msgstr "" + +#: ../Doc/library/__future__.rst:67 +msgid "effect" +msgstr "" + +#: ../Doc/library/__future__.rst:69 +msgid "nested_scopes" +msgstr "" + +#: ../Doc/library/__future__.rst:69 +msgid "2.1.0b1" +msgstr "" + +#: ../Doc/library/__future__.rst:69 +msgid "2.2" +msgstr "" + +#: ../Doc/library/__future__.rst:69 +msgid ":pep:`227`: *Statically Nested Scopes*" +msgstr "" + +#: ../Doc/library/__future__.rst:72 +msgid "generators" +msgstr "" + +#: ../Doc/library/__future__.rst:72 +msgid "2.2.0a1" +msgstr "" + +#: ../Doc/library/__future__.rst:72 +msgid "2.3" +msgstr "" + +#: ../Doc/library/__future__.rst:72 +msgid ":pep:`255`: *Simple Generators*" +msgstr "" + +#: ../Doc/library/__future__.rst:75 +msgid "division" +msgstr "" + +#: ../Doc/library/__future__.rst:75 +msgid "2.2.0a2" +msgstr "" + +#: ../Doc/library/__future__.rst:75 ../Doc/library/__future__.rst:78 +#: ../Doc/library/__future__.rst:84 ../Doc/library/__future__.rst:87 +msgid "3.0" +msgstr "" + +#: ../Doc/library/__future__.rst:75 +msgid ":pep:`238`: *Changing the Division Operator*" +msgstr "" + +#: ../Doc/library/__future__.rst:78 +msgid "absolute_import" +msgstr "" + +#: ../Doc/library/__future__.rst:78 ../Doc/library/__future__.rst:81 +msgid "2.5.0a1" +msgstr "" + +#: ../Doc/library/__future__.rst:78 +msgid ":pep:`328`: *Imports: Multi-Line and Absolute/Relative*" +msgstr "" + +#: ../Doc/library/__future__.rst:81 +msgid "with_statement" +msgstr "" + +#: ../Doc/library/__future__.rst:81 +msgid "2.6" +msgstr "" + +#: ../Doc/library/__future__.rst:81 +msgid ":pep:`343`: *The \"with\" Statement*" +msgstr "" + +#: ../Doc/library/__future__.rst:84 +msgid "print_function" +msgstr "" + +#: ../Doc/library/__future__.rst:84 ../Doc/library/__future__.rst:87 +msgid "2.6.0a2" +msgstr "" + +#: ../Doc/library/__future__.rst:84 +msgid ":pep:`3105`: *Make print a function*" +msgstr "" + +#: ../Doc/library/__future__.rst:87 +msgid "unicode_literals" +msgstr "" + +#: ../Doc/library/__future__.rst:87 +msgid ":pep:`3112`: *Bytes literals in Python 3000*" +msgstr "" + +#: ../Doc/library/__future__.rst:90 +msgid "generator_stop" +msgstr "" + +#: ../Doc/library/__future__.rst:90 +msgid "3.5.0b1" +msgstr "" + +#: ../Doc/library/__future__.rst:90 +msgid "3.7" +msgstr "" + +#: ../Doc/library/__future__.rst:90 +msgid ":pep:`479`: *StopIteration handling inside generators*" +msgstr "" + +#: ../Doc/library/__future__.rst:97 +msgid ":ref:`future`" +msgstr "" + +#: ../Doc/library/__future__.rst:98 +msgid "How the compiler treats future imports." +msgstr "" + +#: ../Doc/library/__main__.rst:3 +msgid ":mod:`__main__` --- Top-level script environment" +msgstr "" + +#: ../Doc/library/__main__.rst:10 +msgid "" +"``'__main__'`` is the name of the scope in which top-level code executes. A " +"module's __name__ is set equal to ``'__main__'`` when read from standard " +"input, a script, or from an interactive prompt." +msgstr "" + +#: ../Doc/library/__main__.rst:14 +msgid "" +"A module can discover whether or not it is running in the main scope by " +"checking its own ``__name__``, which allows a common idiom for conditionally " +"executing code in a module when it is run as a script or with ``python -m`` " +"but not when it is imported::" +msgstr "" + +#: ../Doc/library/__main__.rst:23 +msgid "" +"For a package, the same effect can be achieved by including a ``__main__." +"py`` module, the contents of which will be executed when the module is run " +"with ``-m``." +msgstr "" + +#: ../Doc/library/_dummy_thread.rst:2 +msgid "" +":mod:`_dummy_thread` --- Drop-in replacement for the :mod:`_thread` module" +msgstr "" + +#: ../Doc/library/_dummy_thread.rst:7 +msgid "**Source code:** :source:`Lib/_dummy_thread.py`" +msgstr "" + +#: ../Doc/library/_dummy_thread.rst:11 +msgid "" +"This module provides a duplicate interface to the :mod:`_thread` module. It " +"is meant to be imported when the :mod:`_thread` module is not provided on a " +"platform." +msgstr "" + +#: ../Doc/library/_dummy_thread.rst:15 ../Doc/library/dummy_threading.rst:15 +msgid "Suggested usage is::" +msgstr "" + +#: ../Doc/library/_dummy_thread.rst:22 ../Doc/library/dummy_threading.rst:22 +msgid "" +"Be careful to not use this module where deadlock might occur from a thread " +"being created that blocks waiting for another thread to be created. This " +"often occurs with blocking I/O." +msgstr "" + +#: ../Doc/library/_thread.rst:2 +msgid ":mod:`_thread` --- Low-level threading API" +msgstr "" + +#: ../Doc/library/_thread.rst:15 +msgid "" +"This module provides low-level primitives for working with multiple threads " +"(also called :dfn:`light-weight processes` or :dfn:`tasks`) --- multiple " +"threads of control sharing their global data space. For synchronization, " +"simple locks (also called :dfn:`mutexes` or :dfn:`binary semaphores`) are " +"provided. The :mod:`threading` module provides an easier to use and higher-" +"level threading API built on top of this module." +msgstr "" + +#: ../Doc/library/_thread.rst:26 +msgid "" +"The module is optional. It is supported on Windows, Linux, SGI IRIX, " +"Solaris 2.x, as well as on systems that have a POSIX thread (a.k.a. \"pthread" +"\") implementation. For systems lacking the :mod:`_thread` module, the :mod:" +"`_dummy_thread` module is available. It duplicates this module's interface " +"and can be used as a drop-in replacement." +msgstr "" + +#: ../Doc/library/_thread.rst:32 +msgid "It defines the following constants and functions:" +msgstr "" + +#: ../Doc/library/_thread.rst:37 +msgid "Raised on thread-specific errors." +msgstr "" + +#: ../Doc/library/_thread.rst:39 +msgid "This is now a synonym of the built-in :exc:`RuntimeError`." +msgstr "" + +#: ../Doc/library/_thread.rst:45 +msgid "This is the type of lock objects." +msgstr "" + +#: ../Doc/library/_thread.rst:50 +msgid "" +"Start a new thread and return its identifier. The thread executes the " +"function *function* with the argument list *args* (which must be a tuple). " +"The optional *kwargs* argument specifies a dictionary of keyword arguments. " +"When the function returns, the thread silently exits. When the function " +"terminates with an unhandled exception, a stack trace is printed and then " +"the thread exits (but other threads continue to run)." +msgstr "" + +#: ../Doc/library/_thread.rst:60 +msgid "" +"Raise a :exc:`KeyboardInterrupt` exception in the main thread. A subthread " +"can use this function to interrupt the main thread." +msgstr "" + +#: ../Doc/library/_thread.rst:66 +msgid "" +"Raise the :exc:`SystemExit` exception. When not caught, this will cause the " +"thread to exit silently." +msgstr "" + +#: ../Doc/library/_thread.rst:80 +msgid "" +"Return a new lock object. Methods of locks are described below. The lock " +"is initially unlocked." +msgstr "" + +#: ../Doc/library/_thread.rst:86 ../Doc/library/threading.rst:43 +msgid "" +"Return the 'thread identifier' of the current thread. This is a nonzero " +"integer. Its value has no direct meaning; it is intended as a magic cookie " +"to be used e.g. to index a dictionary of thread-specific data. Thread " +"identifiers may be recycled when a thread exits and another thread is " +"created." +msgstr "" + +#: ../Doc/library/_thread.rst:94 ../Doc/library/threading.rst:89 +msgid "" +"Return the thread stack size used when creating new threads. The optional " +"*size* argument specifies the stack size to be used for subsequently created " +"threads, and must be 0 (use platform or configured default) or a positive " +"integer value of at least 32,768 (32 KiB). If *size* is not specified, 0 is " +"used. If changing the thread stack size is unsupported, a :exc:" +"`RuntimeError` is raised. If the specified stack size is invalid, a :exc:" +"`ValueError` is raised and the stack size is unmodified. 32 KiB is " +"currently the minimum supported stack size value to guarantee sufficient " +"stack space for the interpreter itself. Note that some platforms may have " +"particular restrictions on values for the stack size, such as requiring a " +"minimum stack size > 32 KiB or requiring allocation in multiples of the " +"system memory page size - platform documentation should be referred to for " +"more information (4 KiB pages are common; using multiples of 4096 for the " +"stack size is the suggested approach in the absence of more specific " +"information). Availability: Windows, systems with POSIX threads." +msgstr "" + +#: ../Doc/library/_thread.rst:113 +msgid "" +"The maximum value allowed for the *timeout* parameter of :meth:`Lock." +"acquire`. Specifying a timeout greater than this value will raise an :exc:" +"`OverflowError`." +msgstr "" + +#: ../Doc/library/_thread.rst:120 +msgid "Lock objects have the following methods:" +msgstr "" + +#: ../Doc/library/_thread.rst:125 +msgid "" +"Without any optional argument, this method acquires the lock " +"unconditionally, if necessary waiting until it is released by another thread " +"(only one thread at a time can acquire a lock --- that's their reason for " +"existence)." +msgstr "" + +#: ../Doc/library/_thread.rst:129 +msgid "" +"If the integer *waitflag* argument is present, the action depends on its " +"value: if it is zero, the lock is only acquired if it can be acquired " +"immediately without waiting, while if it is nonzero, the lock is acquired " +"unconditionally as above." +msgstr "" + +#: ../Doc/library/_thread.rst:134 +msgid "" +"If the floating-point *timeout* argument is present and positive, it " +"specifies the maximum wait time in seconds before returning. A negative " +"*timeout* argument specifies an unbounded wait. You cannot specify a " +"*timeout* if *waitflag* is zero." +msgstr "" + +#: ../Doc/library/_thread.rst:139 +msgid "" +"The return value is ``True`` if the lock is acquired successfully, ``False`` " +"if not." +msgstr "" + +#: ../Doc/library/_thread.rst:142 ../Doc/library/threading.rst:398 +#: ../Doc/library/threading.rst:476 ../Doc/library/threading.rst:721 +msgid "The *timeout* parameter is new." +msgstr "" + +#: ../Doc/library/_thread.rst:145 ../Doc/library/threading.rst:401 +msgid "Lock acquires can now be interrupted by signals on POSIX." +msgstr "" + +#: ../Doc/library/_thread.rst:151 +msgid "" +"Releases the lock. The lock must have been acquired earlier, but not " +"necessarily by the same thread." +msgstr "" + +#: ../Doc/library/_thread.rst:157 +msgid "" +"Return the status of the lock: ``True`` if it has been acquired by some " +"thread, ``False`` if not." +msgstr "" + +#: ../Doc/library/_thread.rst:160 +msgid "" +"In addition to these methods, lock objects can also be used via the :keyword:" +"`with` statement, e.g.::" +msgstr "" + +#: ../Doc/library/_thread.rst:170 +msgid "**Caveats:**" +msgstr "" + +#: ../Doc/library/_thread.rst:174 +msgid "" +"Threads interact strangely with interrupts: the :exc:`KeyboardInterrupt` " +"exception will be received by an arbitrary thread. (When the :mod:`signal` " +"module is available, interrupts always go to the main thread.)" +msgstr "" + +#: ../Doc/library/_thread.rst:178 +msgid "" +"Calling :func:`sys.exit` or raising the :exc:`SystemExit` exception is " +"equivalent to calling :func:`_thread.exit`." +msgstr "" + +#: ../Doc/library/_thread.rst:181 +msgid "" +"It is not possible to interrupt the :meth:`acquire` method on a lock --- " +"the :exc:`KeyboardInterrupt` exception will happen after the lock has been " +"acquired." +msgstr "" + +#: ../Doc/library/_thread.rst:184 +msgid "" +"When the main thread exits, it is system defined whether the other threads " +"survive. On most systems, they are killed without executing :keyword:" +"`try` ... :keyword:`finally` clauses or executing object destructors." +msgstr "" + +#: ../Doc/library/_thread.rst:189 +msgid "" +"When the main thread exits, it does not do any of its usual cleanup (except " +"that :keyword:`try` ... :keyword:`finally` clauses are honored), and the " +"standard I/O files are not flushed." +msgstr "" + +#: ../Doc/library/abc.rst:2 +msgid ":mod:`abc` --- Abstract Base Classes" +msgstr "" + +#: ../Doc/library/abc.rst:11 +msgid "**Source code:** :source:`Lib/abc.py`" +msgstr "" + +#: ../Doc/library/abc.rst:15 +msgid "" +"This module provides the infrastructure for defining :term:`abstract base " +"classes ` (ABCs) in Python, as outlined in :pep:`3119`; " +"see the PEP for why this was added to Python. (See also :pep:`3141` and the :" +"mod:`numbers` module regarding a type hierarchy for numbers based on ABCs.)" +msgstr "" + +#: ../Doc/library/abc.rst:20 +msgid "" +"The :mod:`collections` module has some concrete classes that derive from " +"ABCs; these can, of course, be further derived. In addition the :mod:" +"`collections.abc` submodule has some ABCs that can be used to test whether a " +"class or instance provides a particular interface, for example, is it " +"hashable or a mapping." +msgstr "" + +#: ../Doc/library/abc.rst:27 +msgid "This module provides the following classes:" +msgstr "" + +#: ../Doc/library/abc.rst:31 +msgid "Metaclass for defining Abstract Base Classes (ABCs)." +msgstr "" + +#: ../Doc/library/abc.rst:33 +msgid "" +"Use this metaclass to create an ABC. An ABC can be subclassed directly, and " +"then acts as a mix-in class. You can also register unrelated concrete " +"classes (even built-in classes) and unrelated ABCs as \"virtual subclasses\" " +"-- these and their descendants will be considered subclasses of the " +"registering ABC by the built-in :func:`issubclass` function, but the " +"registering ABC won't show up in their MRO (Method Resolution Order) nor " +"will method implementations defined by the registering ABC be callable (not " +"even via :func:`super`). [#]_" +msgstr "" + +#: ../Doc/library/abc.rst:42 +msgid "" +"Classes created with a metaclass of :class:`ABCMeta` have the following " +"method:" +msgstr "" + +#: ../Doc/library/abc.rst:46 +msgid "" +"Register *subclass* as a \"virtual subclass\" of this ABC. For example::" +msgstr "" + +#: ../Doc/library/abc.rst:59 +msgid "Returns the registered subclass, to allow usage as a class decorator." +msgstr "" + +#: ../Doc/library/abc.rst:62 +msgid "" +"To detect calls to :meth:`register`, you can use the :func:`get_cache_token` " +"function." +msgstr "" + +#: ../Doc/library/abc.rst:66 +msgid "You can also override this method in an abstract base class:" +msgstr "" + +#: ../Doc/library/abc.rst:70 +msgid "(Must be defined as a class method.)" +msgstr "" + +#: ../Doc/library/abc.rst:72 +msgid "" +"Check whether *subclass* is considered a subclass of this ABC. This means " +"that you can customize the behavior of ``issubclass`` further without the " +"need to call :meth:`register` on every class you want to consider a subclass " +"of the ABC. (This class method is called from the :meth:`__subclasscheck__` " +"method of the ABC.)" +msgstr "" + +#: ../Doc/library/abc.rst:78 +msgid "" +"This method should return ``True``, ``False`` or ``NotImplemented``. If it " +"returns ``True``, the *subclass* is considered a subclass of this ABC. If it " +"returns ``False``, the *subclass* is not considered a subclass of this ABC, " +"even if it would normally be one. If it returns ``NotImplemented``, the " +"subclass check is continued with the usual mechanism." +msgstr "" + +#: ../Doc/library/abc.rst:88 +msgid "" +"For a demonstration of these concepts, look at this example ABC definition::" +msgstr "" + +#: ../Doc/library/abc.rst:117 +msgid "" +"The ABC ``MyIterable`` defines the standard iterable method, :meth:" +"`~iterator.__iter__`, as an abstract method. The implementation given here " +"can still be called from subclasses. The :meth:`get_iterator` method is " +"also part of the ``MyIterable`` abstract base class, but it does not have to " +"be overridden in non-abstract derived classes." +msgstr "" + +#: ../Doc/library/abc.rst:123 +msgid "" +"The :meth:`__subclasshook__` class method defined here says that any class " +"that has an :meth:`~iterator.__iter__` method in its :attr:`~object." +"__dict__` (or in that of one of its base classes, accessed via the :attr:" +"`~class.__mro__` list) is considered a ``MyIterable`` too." +msgstr "" + +#: ../Doc/library/abc.rst:128 +msgid "" +"Finally, the last line makes ``Foo`` a virtual subclass of ``MyIterable``, " +"even though it does not define an :meth:`~iterator.__iter__` method (it uses " +"the old-style iterable protocol, defined in terms of :meth:`__len__` and :" +"meth:`__getitem__`). Note that this will not make ``get_iterator`` " +"available as a method of ``Foo``, so it is provided separately." +msgstr "" + +#: ../Doc/library/abc.rst:137 +msgid "" +"A helper class that has :class:`ABCMeta` as its metaclass. With this class, " +"an abstract base class can be created by simply deriving from :class:`ABC`, " +"avoiding sometimes confusing metaclass usage." +msgstr "" + +#: ../Doc/library/abc.rst:141 +msgid "" +"Note that the type of :class:`ABC` is still :class:`ABCMeta`, therefore " +"inheriting from :class:`ABC` requires the usual precautions regarding " +"metaclass usage, as multiple inheritance may lead to metaclass conflicts." +msgstr "" + +#: ../Doc/library/abc.rst:148 +msgid "The :mod:`abc` module also provides the following decorators:" +msgstr "" + +#: ../Doc/library/abc.rst:152 +msgid "A decorator indicating abstract methods." +msgstr "" + +#: ../Doc/library/abc.rst:154 +msgid "" +"Using this decorator requires that the class's metaclass is :class:`ABCMeta` " +"or is derived from it. A class that has a metaclass derived from :class:" +"`ABCMeta` cannot be instantiated unless all of its abstract methods and " +"properties are overridden. The abstract methods can be called using any of " +"the normal 'super' call mechanisms. :func:`abstractmethod` may be used to " +"declare abstract methods for properties and descriptors." +msgstr "" + +#: ../Doc/library/abc.rst:161 +msgid "" +"Dynamically adding abstract methods to a class, or attempting to modify the " +"abstraction status of a method or class once it is created, are not " +"supported. The :func:`abstractmethod` only affects subclasses derived using " +"regular inheritance; \"virtual subclasses\" registered with the ABC's :meth:" +"`register` method are not affected." +msgstr "" + +#: ../Doc/library/abc.rst:167 +msgid "" +"When :func:`abstractmethod` is applied in combination with other method " +"descriptors, it should be applied as the innermost decorator, as shown in " +"the following usage examples::" +msgstr "" + +#: ../Doc/library/abc.rst:201 +msgid "" +"In order to correctly interoperate with the abstract base class machinery, " +"the descriptor must identify itself as abstract using :attr:" +"`__isabstractmethod__`. In general, this attribute should be ``True`` if any " +"of the methods used to compose the descriptor are abstract. For example, " +"Python's built-in property does the equivalent of::" +msgstr "" + +#: ../Doc/library/abc.rst:216 +msgid "" +"Unlike Java abstract methods, these abstract methods may have an " +"implementation. This implementation can be called via the :func:`super` " +"mechanism from the class that overrides it. This could be useful as an end-" +"point for a super-call in a framework that uses cooperative multiple-" +"inheritance." +msgstr "" + +#: ../Doc/library/abc.rst:226 +msgid "" +"A subclass of the built-in :func:`classmethod`, indicating an abstract " +"classmethod. Otherwise it is similar to :func:`abstractmethod`." +msgstr "" + +#: ../Doc/library/abc.rst:229 +msgid "" +"This special case is deprecated, as the :func:`classmethod` decorator is now " +"correctly identified as abstract when applied to an abstract method::" +msgstr "" + +#: ../Doc/library/abc.rst:240 +msgid "" +"It is now possible to use :class:`classmethod` with :func:`abstractmethod`, " +"making this decorator redundant." +msgstr "" + +#: ../Doc/library/abc.rst:247 +msgid "" +"A subclass of the built-in :func:`staticmethod`, indicating an abstract " +"staticmethod. Otherwise it is similar to :func:`abstractmethod`." +msgstr "" + +#: ../Doc/library/abc.rst:250 +msgid "" +"This special case is deprecated, as the :func:`staticmethod` decorator is " +"now correctly identified as abstract when applied to an abstract method::" +msgstr "" + +#: ../Doc/library/abc.rst:261 +msgid "" +"It is now possible to use :class:`staticmethod` with :func:`abstractmethod`, " +"making this decorator redundant." +msgstr "" + +#: ../Doc/library/abc.rst:268 +msgid "" +"A subclass of the built-in :func:`property`, indicating an abstract property." +msgstr "" + +#: ../Doc/library/abc.rst:271 +msgid "" +"Using this function requires that the class's metaclass is :class:`ABCMeta` " +"or is derived from it. A class that has a metaclass derived from :class:" +"`ABCMeta` cannot be instantiated unless all of its abstract methods and " +"properties are overridden. The abstract properties can be called using any " +"of the normal 'super' call mechanisms." +msgstr "" + +#: ../Doc/library/abc.rst:277 +msgid "" +"This special case is deprecated, as the :func:`property` decorator is now " +"correctly identified as abstract when applied to an abstract method::" +msgstr "" + +#: ../Doc/library/abc.rst:287 +msgid "" +"The above example defines a read-only property; you can also define a read-" +"write abstract property by appropriately marking one or more of the " +"underlying methods as abstract::" +msgstr "" + +#: ../Doc/library/abc.rst:301 +msgid "" +"If only some components are abstract, only those components need to be " +"updated to create a concrete property in a subclass::" +msgstr "" + +#: ../Doc/library/abc.rst:310 +msgid "" +"It is now possible to use :class:`property`, :meth:`property.getter`, :meth:" +"`property.setter` and :meth:`property.deleter` with :func:`abstractmethod`, " +"making this decorator redundant." +msgstr "" + +#: ../Doc/library/abc.rst:316 +msgid "The :mod:`abc` module also provides the following functions:" +msgstr "" + +#: ../Doc/library/abc.rst:320 +msgid "Returns the current abstract base class cache token." +msgstr "" + +#: ../Doc/library/abc.rst:322 +msgid "" +"The token is an opaque object (that supports equality testing) identifying " +"the current version of the abstract base class cache for virtual subclasses. " +"The token changes with every call to :meth:`ABCMeta.register` on any ABC." +msgstr "" + +#: ../Doc/library/abc.rst:330 ../Doc/library/cgi.rst:534 +#: ../Doc/library/chunk.rst:134 ../Doc/library/configparser.rst:1313 +#: ../Doc/library/csv.rst:542 ../Doc/library/datetime.rst:2166 +#: ../Doc/library/doctest.rst:1847 ../Doc/library/email.contentmanager.rst:205 +#: ../Doc/library/email.encoders.rst:67 ../Doc/library/email.examples.rst:66 +#: ../Doc/library/email.generator.rst:271 +#: ../Doc/library/email.headerregistry.rst:453 +#: ../Doc/library/email.message.rst:748 ../Doc/library/email.policy.rst:649 +#: ../Doc/library/email.util.rst:215 ../Doc/library/functions.rst:1619 +#: ../Doc/library/gettext.rst:652 ../Doc/library/heapq.rst:299 +#: ../Doc/library/html.entities.rst:46 ../Doc/library/json.rst:718 +#: ../Doc/library/marshal.rst:115 ../Doc/library/pdb.rst:517 +#: ../Doc/library/pickle.rst:914 ../Doc/library/pyexpat.rst:871 +#: ../Doc/library/sqlite3.rst:1008 ../Doc/library/ssl.rst:206 +#: ../Doc/library/stdtypes.rst:4626 ../Doc/library/time.rst:692 +#: ../Doc/library/unicodedata.rst:170 ../Doc/library/webbrowser.rst:211 +#: ../Doc/library/xml.dom.minidom.rst:250 +#: ../Doc/library/xml.etree.elementtree.rst:1194 +#: ../Doc/library/xmlrpc.client.rst:601 +msgid "Footnotes" +msgstr "" + +#: ../Doc/library/abc.rst:331 +msgid "" +"C++ programmers should note that Python's virtual base class concept is not " +"the same as C++'s." +msgstr "" + +#: ../Doc/library/aifc.rst:2 +msgid ":mod:`aifc` --- Read and write AIFF and AIFC files" +msgstr "" + +#: ../Doc/library/aifc.rst:7 +msgid "**Source code:** :source:`Lib/aifc.py`" +msgstr "" + +#: ../Doc/library/aifc.rst:16 +msgid "" +"This module provides support for reading and writing AIFF and AIFF-C files. " +"AIFF is Audio Interchange File Format, a format for storing digital audio " +"samples in a file. AIFF-C is a newer version of the format that includes " +"the ability to compress the audio data." +msgstr "" + +#: ../Doc/library/aifc.rst:23 +msgid "" +"Some operations may only work under IRIX; these will raise :exc:" +"`ImportError` when attempting to import the :mod:`cl` module, which is only " +"available on IRIX." +msgstr "" + +#: ../Doc/library/aifc.rst:27 +msgid "" +"Audio files have a number of parameters that describe the audio data. The " +"sampling rate or frame rate is the number of times per second the sound is " +"sampled. The number of channels indicate if the audio is mono, stereo, or " +"quadro. Each frame consists of one sample per channel. The sample size is " +"the size in bytes of each sample. Thus a frame consists of ``nchannels * " +"samplesize`` bytes, and a second's worth of audio consists of ``nchannels * " +"samplesize * framerate`` bytes." +msgstr "" + +#: ../Doc/library/aifc.rst:35 +msgid "" +"For example, CD quality audio has a sample size of two bytes (16 bits), uses " +"two channels (stereo) and has a frame rate of 44,100 frames/second. This " +"gives a frame size of 4 bytes (2\\*2), and a second's worth occupies " +"2\\*2\\*44100 bytes (176,400 bytes)." +msgstr "" + +#: ../Doc/library/aifc.rst:40 +msgid "Module :mod:`aifc` defines the following function:" +msgstr "" + +#: ../Doc/library/aifc.rst:45 +msgid "" +"Open an AIFF or AIFF-C file and return an object instance with methods that " +"are described below. The argument *file* is either a string naming a file " +"or a :term:`file object`. *mode* must be ``'r'`` or ``'rb'`` when the file " +"must be opened for reading, or ``'w'`` or ``'wb'`` when the file must be " +"opened for writing. If omitted, ``file.mode`` is used if it exists, " +"otherwise ``'rb'`` is used. When used for writing, the file object should " +"be seekable, unless you know ahead of time how many samples you are going to " +"write in total and use :meth:`writeframesraw` and :meth:`setnframes`. The :" +"func:`.open` function may be used in a :keyword:`with` statement. When the :" +"keyword:`with` block completes, the :meth:`~aifc.close` method is called." +msgstr "" + +#: ../Doc/library/aifc.rst:56 ../Doc/library/bz2.rst:112 +#: ../Doc/library/ftplib.rst:68 ../Doc/library/imaplib.rst:50 +#: ../Doc/library/nntplib.rst:86 ../Doc/library/smtplib.rst:58 +msgid "Support for the :keyword:`with` statement was added." +msgstr "" + +#: ../Doc/library/aifc.rst:59 +msgid "" +"Objects returned by :func:`.open` when a file is opened for reading have the " +"following methods:" +msgstr "" + +#: ../Doc/library/aifc.rst:65 +msgid "Return the number of audio channels (1 for mono, 2 for stereo)." +msgstr "" + +#: ../Doc/library/aifc.rst:70 +msgid "Return the size in bytes of individual samples." +msgstr "" + +#: ../Doc/library/aifc.rst:75 +msgid "Return the sampling rate (number of audio frames per second)." +msgstr "" + +#: ../Doc/library/aifc.rst:80 +msgid "Return the number of audio frames in the file." +msgstr "" + +#: ../Doc/library/aifc.rst:85 +msgid "" +"Return a bytes array of length 4 describing the type of compression used in " +"the audio file. For AIFF files, the returned value is ``b'NONE'``." +msgstr "" + +#: ../Doc/library/aifc.rst:92 +msgid "" +"Return a bytes array convertible to a human-readable description of the type " +"of compression used in the audio file. For AIFF files, the returned value " +"is ``b'not compressed'``." +msgstr "" + +#: ../Doc/library/aifc.rst:99 ../Doc/library/sunau.rst:154 +#: ../Doc/library/wave.rst:108 +msgid "" +"Returns a :func:`~collections.namedtuple` ``(nchannels, sampwidth, " +"framerate, nframes, comptype, compname)``, equivalent to output of the :meth:" +"`get\\*` methods." +msgstr "" + +#: ../Doc/library/aifc.rst:106 +msgid "" +"Return a list of markers in the audio file. A marker consists of a tuple of " +"three elements. The first is the mark ID (an integer), the second is the " +"mark position in frames from the beginning of the data (an integer), the " +"third is the name of the mark (a string)." +msgstr "" + +#: ../Doc/library/aifc.rst:114 +msgid "" +"Return the tuple as described in :meth:`getmarkers` for the mark with the " +"given *id*." +msgstr "" + +#: ../Doc/library/aifc.rst:120 +msgid "" +"Read and return the next *nframes* frames from the audio file. The returned " +"data is a string containing for each frame the uncompressed samples of all " +"channels." +msgstr "" + +#: ../Doc/library/aifc.rst:127 +msgid "" +"Rewind the read pointer. The next :meth:`readframes` will start from the " +"beginning." +msgstr "" + +#: ../Doc/library/aifc.rst:133 +msgid "Seek to the specified frame number." +msgstr "" + +#: ../Doc/library/aifc.rst:138 +msgid "Return the current frame number." +msgstr "" + +#: ../Doc/library/aifc.rst:143 +msgid "" +"Close the AIFF file. After calling this method, the object can no longer be " +"used." +msgstr "" + +#: ../Doc/library/aifc.rst:146 +msgid "" +"Objects returned by :func:`.open` when a file is opened for writing have all " +"the above methods, except for :meth:`readframes` and :meth:`setpos`. In " +"addition the following methods exist. The :meth:`get\\*` methods can only " +"be called after the corresponding :meth:`set\\*` methods have been called. " +"Before the first :meth:`writeframes` or :meth:`writeframesraw`, all " +"parameters except for the number of frames must be filled in." +msgstr "" + +#: ../Doc/library/aifc.rst:156 +msgid "" +"Create an AIFF file. The default is that an AIFF-C file is created, unless " +"the name of the file ends in ``'.aiff'`` in which case the default is an " +"AIFF file." +msgstr "" + +#: ../Doc/library/aifc.rst:162 +msgid "" +"Create an AIFF-C file. The default is that an AIFF-C file is created, " +"unless the name of the file ends in ``'.aiff'`` in which case the default is " +"an AIFF file." +msgstr "" + +#: ../Doc/library/aifc.rst:169 +msgid "Specify the number of channels in the audio file." +msgstr "" + +#: ../Doc/library/aifc.rst:174 +msgid "Specify the size in bytes of audio samples." +msgstr "" + +#: ../Doc/library/aifc.rst:179 +msgid "Specify the sampling frequency in frames per second." +msgstr "" + +#: ../Doc/library/aifc.rst:184 +msgid "" +"Specify the number of frames that are to be written to the audio file. If " +"this parameter is not set, or not set correctly, the file needs to support " +"seeking." +msgstr "" + +#: ../Doc/library/aifc.rst:195 +msgid "" +"Specify the compression type. If not specified, the audio data will not be " +"compressed. In AIFF files, compression is not possible. The name parameter " +"should be a human-readable description of the compression type as a bytes " +"array, the type parameter should be a bytes array of length 4. Currently " +"the following compression types are supported: ``b'NONE'``, ``b'ULAW'``, " +"``b'ALAW'``, ``b'G722'``." +msgstr "" + +#: ../Doc/library/aifc.rst:205 +msgid "" +"Set all the above parameters at once. The argument is a tuple consisting of " +"the various parameters. This means that it is possible to use the result of " +"a :meth:`getparams` call as argument to :meth:`setparams`." +msgstr "" + +#: ../Doc/library/aifc.rst:212 +msgid "" +"Add a mark with the given id (larger than 0), and the given name at the " +"given position. This method can be called at any time before :meth:`close`." +msgstr "" + +#: ../Doc/library/aifc.rst:218 +msgid "" +"Return the current write position in the output file. Useful in combination " +"with :meth:`setmark`." +msgstr "" + +#: ../Doc/library/aifc.rst:224 +msgid "" +"Write data to the output file. This method can only be called after the " +"audio file parameters have been set." +msgstr "" + +#: ../Doc/library/aifc.rst:227 ../Doc/library/aifc.rst:236 +#: ../Doc/library/sunau.rst:254 ../Doc/library/sunau.rst:262 +#: ../Doc/library/wave.rst:229 ../Doc/library/wave.rst:240 +msgid "Any :term:`bytes-like object` is now accepted." +msgstr "" + +#: ../Doc/library/aifc.rst:233 +msgid "" +"Like :meth:`writeframes`, except that the header of the audio file is not " +"updated." +msgstr "" + +#: ../Doc/library/aifc.rst:242 +msgid "" +"Close the AIFF file. The header of the file is updated to reflect the " +"actual size of the audio data. After calling this method, the object can no " +"longer be used." +msgstr "" + +#: ../Doc/library/allos.rst:5 +msgid "Generic Operating System Services" +msgstr "" + +#: ../Doc/library/allos.rst:7 +msgid "" +"The modules described in this chapter provide interfaces to operating system " +"features that are available on (almost) all operating systems, such as files " +"and a clock. The interfaces are generally modeled after the Unix or C " +"interfaces, but they are available on most other systems as well. Here's an " +"overview:" +msgstr "" + +#: ../Doc/library/archiving.rst:5 +msgid "Data Compression and Archiving" +msgstr "" + +#: ../Doc/library/archiving.rst:7 +msgid "" +"The modules described in this chapter support data compression with the " +"zlib, gzip, bzip2 and lzma algorithms, and the creation of ZIP- and tar-" +"format archives. See also :ref:`archiving-operations` provided by the :mod:" +"`shutil` module." +msgstr "" + +#: ../Doc/library/argparse.rst:2 +msgid "" +":mod:`argparse` --- Parser for command-line options, arguments and sub-" +"commands" +msgstr "" + +#: ../Doc/library/argparse.rst:12 +msgid "**Source code:** :source:`Lib/argparse.py`" +msgstr "" + +#: ../Doc/library/argparse.rst:0 ../Doc/library/optparse.rst:246 +#: ../Doc/library/xml.etree.elementtree.rst:28 +msgid "Tutorial" +msgstr "" + +#: ../Doc/library/argparse.rst:18 +msgid "" +"This page contains the API reference information. For a more gentle " +"introduction to Python command-line parsing, have a look at the :ref:" +"`argparse tutorial `." +msgstr "" + +#: ../Doc/library/argparse.rst:22 +msgid "" +"The :mod:`argparse` module makes it easy to write user-friendly command-line " +"interfaces. The program defines what arguments it requires, and :mod:" +"`argparse` will figure out how to parse those out of :data:`sys.argv`. The :" +"mod:`argparse` module also automatically generates help and usage messages " +"and issues errors when users give the program invalid arguments." +msgstr "" + +#: ../Doc/library/argparse.rst:30 ../Doc/library/copyreg.rst:46 +#: ../Doc/library/datetime.rst:1966 ../Doc/library/datetime.rst:2072 +#: ../Doc/library/faulthandler.rst:153 ../Doc/library/fpectl.rst:74 +#: ../Doc/library/http.cookies.rst:241 ../Doc/library/itertools.rst:38 +#: ../Doc/library/itertools.rst:48 ../Doc/library/pprint.rst:212 +#: ../Doc/library/pty.rst:57 ../Doc/library/pyexpat.rst:528 +#: ../Doc/library/readline.rst:280 ../Doc/library/shelve.rst:160 +#: ../Doc/library/signal.rst:440 ../Doc/library/socket.rst:1508 +#: ../Doc/library/termios.rst:86 ../Doc/library/tkinter.rst:430 +#: ../Doc/library/uuid.rst:222 ../Doc/library/weakref.rst:415 +#: ../Doc/library/xml.etree.elementtree.rst:376 +msgid "Example" +msgstr "" + +#: ../Doc/library/argparse.rst:32 +msgid "" +"The following code is a Python program that takes a list of integers and " +"produces either the sum or the max::" +msgstr "" + +#: ../Doc/library/argparse.rst:47 +msgid "" +"Assuming the Python code above is saved into a file called ``prog.py``, it " +"can be run at the command line and provides useful help messages:" +msgstr "" + +#: ../Doc/library/argparse.rst:64 +msgid "" +"When run with the appropriate arguments, it prints either the sum or the max " +"of the command-line integers:" +msgstr "" + +#: ../Doc/library/argparse.rst:75 +msgid "If invalid arguments are passed in, it will issue an error:" +msgstr "" + +#: ../Doc/library/argparse.rst:83 +msgid "The following sections walk you through this example." +msgstr "" + +#: ../Doc/library/argparse.rst:87 +msgid "Creating a parser" +msgstr "" + +#: ../Doc/library/argparse.rst:89 +msgid "" +"The first step in using the :mod:`argparse` is creating an :class:" +"`ArgumentParser` object::" +msgstr "" + +#: ../Doc/library/argparse.rst:94 +msgid "" +"The :class:`ArgumentParser` object will hold all the information necessary " +"to parse the command line into Python data types." +msgstr "" + +#: ../Doc/library/argparse.rst:99 +msgid "Adding arguments" +msgstr "" + +#: ../Doc/library/argparse.rst:101 +msgid "" +"Filling an :class:`ArgumentParser` with information about program arguments " +"is done by making calls to the :meth:`~ArgumentParser.add_argument` method. " +"Generally, these calls tell the :class:`ArgumentParser` how to take the " +"strings on the command line and turn them into objects. This information is " +"stored and used when :meth:`~ArgumentParser.parse_args` is called. For " +"example::" +msgstr "" + +#: ../Doc/library/argparse.rst:113 +msgid "" +"Later, calling :meth:`~ArgumentParser.parse_args` will return an object with " +"two attributes, ``integers`` and ``accumulate``. The ``integers`` attribute " +"will be a list of one or more ints, and the ``accumulate`` attribute will be " +"either the :func:`sum` function, if ``--sum`` was specified at the command " +"line, or the :func:`max` function if it was not." +msgstr "" + +#: ../Doc/library/argparse.rst:121 ../Doc/library/optparse.rst:1321 +msgid "Parsing arguments" +msgstr "" + +#: ../Doc/library/argparse.rst:123 +msgid "" +":class:`ArgumentParser` parses arguments through the :meth:`~ArgumentParser." +"parse_args` method. This will inspect the command line, convert each " +"argument to the appropriate type and then invoke the appropriate action. In " +"most cases, this means a simple :class:`Namespace` object will be built up " +"from attributes parsed out of the command line::" +msgstr "" + +#: ../Doc/library/argparse.rst:132 +msgid "" +"In a script, :meth:`~ArgumentParser.parse_args` will typically be called " +"with no arguments, and the :class:`ArgumentParser` will automatically " +"determine the command-line arguments from :data:`sys.argv`." +msgstr "" + +#: ../Doc/library/argparse.rst:138 +msgid "ArgumentParser objects" +msgstr "" + +#: ../Doc/library/argparse.rst:147 +msgid "" +"Create a new :class:`ArgumentParser` object. All parameters should be passed " +"as keyword arguments. Each parameter has its own more detailed description " +"below, but in short they are:" +msgstr "" + +#: ../Doc/library/argparse.rst:151 +msgid "prog_ - The name of the program (default: ``sys.argv[0]``)" +msgstr "" + +#: ../Doc/library/argparse.rst:153 +msgid "" +"usage_ - The string describing the program usage (default: generated from " +"arguments added to parser)" +msgstr "" + +#: ../Doc/library/argparse.rst:156 +msgid "description_ - Text to display before the argument help (default: none)" +msgstr "" + +#: ../Doc/library/argparse.rst:158 +msgid "epilog_ - Text to display after the argument help (default: none)" +msgstr "" + +#: ../Doc/library/argparse.rst:160 +msgid "" +"parents_ - A list of :class:`ArgumentParser` objects whose arguments should " +"also be included" +msgstr "" + +#: ../Doc/library/argparse.rst:163 +msgid "formatter_class_ - A class for customizing the help output" +msgstr "" + +#: ../Doc/library/argparse.rst:165 +msgid "" +"prefix_chars_ - The set of characters that prefix optional arguments " +"(default: '-')" +msgstr "" + +#: ../Doc/library/argparse.rst:168 +msgid "" +"fromfile_prefix_chars_ - The set of characters that prefix files from which " +"additional arguments should be read (default: ``None``)" +msgstr "" + +#: ../Doc/library/argparse.rst:171 +msgid "" +"argument_default_ - The global default value for arguments (default: " +"``None``)" +msgstr "" + +#: ../Doc/library/argparse.rst:174 +msgid "" +"conflict_handler_ - The strategy for resolving conflicting optionals " +"(usually unnecessary)" +msgstr "" + +#: ../Doc/library/argparse.rst:177 +msgid "add_help_ - Add a -h/--help option to the parser (default: ``True``)" +msgstr "" + +#: ../Doc/library/argparse.rst:179 +msgid "" +"allow_abbrev_ - Allows long options to be abbreviated if the abbreviation is " +"unambiguous. (default: ``True``)" +msgstr "" + +#: ../Doc/library/argparse.rst:182 +msgid "*allow_abbrev* parameter was added." +msgstr "" + +#: ../Doc/library/argparse.rst:185 ../Doc/library/argparse.rst:681 +msgid "The following sections describe how each of these are used." +msgstr "" + +#: ../Doc/library/argparse.rst:189 +msgid "prog" +msgstr "" + +#: ../Doc/library/argparse.rst:191 +msgid "" +"By default, :class:`ArgumentParser` objects use ``sys.argv[0]`` to determine " +"how to display the name of the program in help messages. This default is " +"almost always desirable because it will make the help messages match how the " +"program was invoked on the command line. For example, consider a file named " +"``myprogram.py`` with the following code::" +msgstr "" + +#: ../Doc/library/argparse.rst:202 +msgid "" +"The help for this program will display ``myprogram.py`` as the program name " +"(regardless of where the program was invoked from):" +msgstr "" + +#: ../Doc/library/argparse.rst:221 +msgid "" +"To change this default behavior, another value can be supplied using the " +"``prog=`` argument to :class:`ArgumentParser`::" +msgstr "" + +#: ../Doc/library/argparse.rst:231 +msgid "" +"Note that the program name, whether determined from ``sys.argv[0]`` or from " +"the ``prog=`` argument, is available to help messages using the ``%(prog)s`` " +"format specifier." +msgstr "" + +#: ../Doc/library/argparse.rst:248 +msgid "usage" +msgstr "" + +#: ../Doc/library/argparse.rst:250 +msgid "" +"By default, :class:`ArgumentParser` calculates the usage message from the " +"arguments it contains::" +msgstr "" + +#: ../Doc/library/argparse.rst:266 +msgid "" +"The default message can be overridden with the ``usage=`` keyword argument::" +msgstr "" + +#: ../Doc/library/argparse.rst:281 +msgid "" +"The ``%(prog)s`` format specifier is available to fill in the program name " +"in your usage messages." +msgstr "" + +#: ../Doc/library/argparse.rst:286 ../Doc/library/tracemalloc.rst:520 +msgid "description" +msgstr "" + +#: ../Doc/library/argparse.rst:288 +msgid "" +"Most calls to the :class:`ArgumentParser` constructor will use the " +"``description=`` keyword argument. This argument gives a brief description " +"of what the program does and how it works. In help messages, the " +"description is displayed between the command-line usage string and the help " +"messages for the various arguments::" +msgstr "" + +#: ../Doc/library/argparse.rst:303 +msgid "" +"By default, the description will be line-wrapped so that it fits within the " +"given space. To change this behavior, see the formatter_class_ argument." +msgstr "" + +#: ../Doc/library/argparse.rst:308 +msgid "epilog" +msgstr "" + +#: ../Doc/library/argparse.rst:310 +msgid "" +"Some programs like to display additional description of the program after " +"the description of the arguments. Such text can be specified using the " +"``epilog=`` argument to :class:`ArgumentParser`::" +msgstr "" + +#: ../Doc/library/argparse.rst:327 +msgid "" +"As with the description_ argument, the ``epilog=`` text is by default line-" +"wrapped, but this behavior can be adjusted with the formatter_class_ " +"argument to :class:`ArgumentParser`." +msgstr "" + +#: ../Doc/library/argparse.rst:333 +msgid "parents" +msgstr "" + +#: ../Doc/library/argparse.rst:335 +msgid "" +"Sometimes, several parsers share a common set of arguments. Rather than " +"repeating the definitions of these arguments, a single parser with all the " +"shared arguments and passed to ``parents=`` argument to :class:" +"`ArgumentParser` can be used. The ``parents=`` argument takes a list of :" +"class:`ArgumentParser` objects, collects all the positional and optional " +"actions from them, and adds these actions to the :class:`ArgumentParser` " +"object being constructed::" +msgstr "" + +#: ../Doc/library/argparse.rst:355 +msgid "" +"Note that most parent parsers will specify ``add_help=False``. Otherwise, " +"the :class:`ArgumentParser` will see two ``-h/--help`` options (one in the " +"parent and one in the child) and raise an error." +msgstr "" + +#: ../Doc/library/argparse.rst:360 +msgid "" +"You must fully initialize the parsers before passing them via ``parents=``. " +"If you change the parent parsers after the child parser, those changes will " +"not be reflected in the child." +msgstr "" + +#: ../Doc/library/argparse.rst:366 +msgid "formatter_class" +msgstr "" + +#: ../Doc/library/argparse.rst:368 +msgid "" +":class:`ArgumentParser` objects allow the help formatting to be customized " +"by specifying an alternate formatting class. Currently, there are four such " +"classes:" +msgstr "" + +#: ../Doc/library/argparse.rst:377 +msgid "" +":class:`RawDescriptionHelpFormatter` and :class:`RawTextHelpFormatter` give " +"more control over how textual descriptions are displayed. By default, :class:" +"`ArgumentParser` objects line-wrap the description_ and epilog_ texts in " +"command-line help messages::" +msgstr "" + +#: ../Doc/library/argparse.rst:402 +msgid "" +"Passing :class:`RawDescriptionHelpFormatter` as ``formatter_class=`` " +"indicates that description_ and epilog_ are already correctly formatted and " +"should not be line-wrapped::" +msgstr "" + +#: ../Doc/library/argparse.rst:428 +msgid "" +":class:`RawTextHelpFormatter` maintains whitespace for all sorts of help " +"text, including argument descriptions." +msgstr "" + +#: ../Doc/library/argparse.rst:431 +msgid "" +":class:`ArgumentDefaultsHelpFormatter` automatically adds information about " +"default values to each of the argument help messages::" +msgstr "" + +#: ../Doc/library/argparse.rst:449 +msgid "" +":class:`MetavarTypeHelpFormatter` uses the name of the type_ argument for " +"each argument as the display name for its values (rather than using the " +"dest_ as the regular formatter does)::" +msgstr "" + +#: ../Doc/library/argparse.rst:470 +msgid "prefix_chars" +msgstr "" + +#: ../Doc/library/argparse.rst:472 +msgid "" +"Most command-line options will use ``-`` as the prefix, e.g. ``-f/--foo``. " +"Parsers that need to support different or additional prefix characters, e.g. " +"for options like ``+f`` or ``/foo``, may specify them using the " +"``prefix_chars=`` argument to the ArgumentParser constructor::" +msgstr "" + +#: ../Doc/library/argparse.rst:484 +msgid "" +"The ``prefix_chars=`` argument defaults to ``'-'``. Supplying a set of " +"characters that does not include ``-`` will cause ``-f/--foo`` options to be " +"disallowed." +msgstr "" + +#: ../Doc/library/argparse.rst:490 +msgid "fromfile_prefix_chars" +msgstr "" + +#: ../Doc/library/argparse.rst:492 +msgid "" +"Sometimes, for example when dealing with a particularly long argument lists, " +"it may make sense to keep the list of arguments in a file rather than typing " +"it out at the command line. If the ``fromfile_prefix_chars=`` argument is " +"given to the :class:`ArgumentParser` constructor, then arguments that start " +"with any of the specified characters will be treated as files, and will be " +"replaced by the arguments they contain. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:506 +msgid "" +"Arguments read from a file must by default be one per line (but see also :" +"meth:`~ArgumentParser.convert_arg_line_to_args`) and are treated as if they " +"were in the same place as the original file referencing argument on the " +"command line. So in the example above, the expression ``['-f', 'foo', " +"'@args.txt']`` is considered equivalent to the expression ``['-f', 'foo', '-" +"f', 'bar']``." +msgstr "" + +#: ../Doc/library/argparse.rst:512 +msgid "" +"The ``fromfile_prefix_chars=`` argument defaults to ``None``, meaning that " +"arguments will never be treated as file references." +msgstr "" + +#: ../Doc/library/argparse.rst:517 +msgid "argument_default" +msgstr "" + +#: ../Doc/library/argparse.rst:519 +msgid "" +"Generally, argument defaults are specified either by passing a default to :" +"meth:`~ArgumentParser.add_argument` or by calling the :meth:`~ArgumentParser." +"set_defaults` methods with a specific set of name-value pairs. Sometimes " +"however, it may be useful to specify a single parser-wide default for " +"arguments. This can be accomplished by passing the ``argument_default=`` " +"keyword argument to :class:`ArgumentParser`. For example, to globally " +"suppress attribute creation on :meth:`~ArgumentParser.parse_args` calls, we " +"supply ``argument_default=SUPPRESS``::" +msgstr "" + +#: ../Doc/library/argparse.rst:539 +msgid "allow_abbrev" +msgstr "" + +#: ../Doc/library/argparse.rst:541 +msgid "" +"Normally, when you pass an argument list to the :meth:`~ArgumentParser." +"parse_args` method of an :class:`ArgumentParser`, it :ref:`recognizes " +"abbreviations ` of long options." +msgstr "" + +#: ../Doc/library/argparse.rst:545 +msgid "This feature can be disabled by setting ``allow_abbrev`` to ``False``::" +msgstr "" + +#: ../Doc/library/argparse.rst:558 +msgid "conflict_handler" +msgstr "" + +#: ../Doc/library/argparse.rst:560 +msgid "" +":class:`ArgumentParser` objects do not allow two actions with the same " +"option string. By default, :class:`ArgumentParser` objects raise an " +"exception if an attempt is made to create an argument with an option string " +"that is already in use::" +msgstr "" + +#: ../Doc/library/argparse.rst:572 +msgid "" +"Sometimes (e.g. when using parents_) it may be useful to simply override any " +"older arguments with the same option string. To get this behavior, the " +"value ``'resolve'`` can be supplied to the ``conflict_handler=`` argument " +"of :class:`ArgumentParser`::" +msgstr "" + +#: ../Doc/library/argparse.rst:588 +msgid "" +"Note that :class:`ArgumentParser` objects only remove an action if all of " +"its option strings are overridden. So, in the example above, the old ``-f/--" +"foo`` action is retained as the ``-f`` action, because only the ``--foo`` " +"option string was overridden." +msgstr "" + +#: ../Doc/library/argparse.rst:595 +msgid "add_help" +msgstr "" + +#: ../Doc/library/argparse.rst:597 +msgid "" +"By default, ArgumentParser objects add an option which simply displays the " +"parser's help message. For example, consider a file named ``myprogram.py`` " +"containing the following code::" +msgstr "" + +#: ../Doc/library/argparse.rst:606 +msgid "" +"If ``-h`` or ``--help`` is supplied at the command line, the ArgumentParser " +"help will be printed:" +msgstr "" + +#: ../Doc/library/argparse.rst:618 +msgid "" +"Occasionally, it may be useful to disable the addition of this help option. " +"This can be achieved by passing ``False`` as the ``add_help=`` argument to :" +"class:`ArgumentParser`::" +msgstr "" + +#: ../Doc/library/argparse.rst:630 +msgid "" +"The help option is typically ``-h/--help``. The exception to this is if the " +"``prefix_chars=`` is specified and does not include ``-``, in which case ``-" +"h`` and ``--help`` are not valid options. In this case, the first character " +"in ``prefix_chars`` is used to prefix the help options::" +msgstr "" + +#: ../Doc/library/argparse.rst:645 +msgid "The add_argument() method" +msgstr "" + +#: ../Doc/library/argparse.rst:651 +msgid "" +"Define how a single command-line argument should be parsed. Each parameter " +"has its own more detailed description below, but in short they are:" +msgstr "" + +#: ../Doc/library/argparse.rst:654 +msgid "" +"`name or flags`_ - Either a name or a list of option strings, e.g. ``foo`` " +"or ``-f, --foo``." +msgstr "" + +#: ../Doc/library/argparse.rst:657 +msgid "" +"action_ - The basic type of action to be taken when this argument is " +"encountered at the command line." +msgstr "" + +#: ../Doc/library/argparse.rst:660 +msgid "nargs_ - The number of command-line arguments that should be consumed." +msgstr "" + +#: ../Doc/library/argparse.rst:662 +msgid "" +"const_ - A constant value required by some action_ and nargs_ selections." +msgstr "" + +#: ../Doc/library/argparse.rst:664 +msgid "" +"default_ - The value produced if the argument is absent from the command " +"line." +msgstr "" + +#: ../Doc/library/argparse.rst:667 +msgid "" +"type_ - The type to which the command-line argument should be converted." +msgstr "" + +#: ../Doc/library/argparse.rst:669 +msgid "choices_ - A container of the allowable values for the argument." +msgstr "" + +#: ../Doc/library/argparse.rst:671 +msgid "" +"required_ - Whether or not the command-line option may be omitted (optionals " +"only)." +msgstr "" + +#: ../Doc/library/argparse.rst:674 +msgid "help_ - A brief description of what the argument does." +msgstr "" + +#: ../Doc/library/argparse.rst:676 +msgid "metavar_ - A name for the argument in usage messages." +msgstr "" + +#: ../Doc/library/argparse.rst:678 +msgid "" +"dest_ - The name of the attribute to be added to the object returned by :" +"meth:`parse_args`." +msgstr "" + +#: ../Doc/library/argparse.rst:685 +msgid "name or flags" +msgstr "" + +#: ../Doc/library/argparse.rst:687 +msgid "" +"The :meth:`~ArgumentParser.add_argument` method must know whether an " +"optional argument, like ``-f`` or ``--foo``, or a positional argument, like " +"a list of filenames, is expected. The first arguments passed to :meth:" +"`~ArgumentParser.add_argument` must therefore be either a series of flags, " +"or a simple argument name. For example, an optional argument could be " +"created like::" +msgstr "" + +#: ../Doc/library/argparse.rst:696 +msgid "while a positional argument could be created like::" +msgstr "" + +#: ../Doc/library/argparse.rst:700 +msgid "" +"When :meth:`~ArgumentParser.parse_args` is called, optional arguments will " +"be identified by the ``-`` prefix, and the remaining arguments will be " +"assumed to be positional::" +msgstr "" + +#: ../Doc/library/argparse.rst:717 ../Doc/library/tarfile.rst:50 +msgid "action" +msgstr "" + +#: ../Doc/library/argparse.rst:719 +msgid "" +":class:`ArgumentParser` objects associate command-line arguments with " +"actions. These actions can do just about anything with the command-line " +"arguments associated with them, though most actions simply add an attribute " +"to the object returned by :meth:`~ArgumentParser.parse_args`. The " +"``action`` keyword argument specifies how the command-line arguments should " +"be handled. The supplied actions are:" +msgstr "" + +#: ../Doc/library/argparse.rst:725 +msgid "" +"``'store'`` - This just stores the argument's value. This is the default " +"action. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:733 +msgid "" +"``'store_const'`` - This stores the value specified by the const_ keyword " +"argument. The ``'store_const'`` action is most commonly used with optional " +"arguments that specify some sort of flag. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:742 +msgid "" +"``'store_true'`` and ``'store_false'`` - These are special cases of " +"``'store_const'`` used for storing the values ``True`` and ``False`` " +"respectively. In addition, they create default values of ``False`` and " +"``True`` respectively. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:754 +msgid "" +"``'append'`` - This stores a list, and appends each argument value to the " +"list. This is useful to allow an option to be specified multiple times. " +"Example usage::" +msgstr "" + +#: ../Doc/library/argparse.rst:763 +msgid "" +"``'append_const'`` - This stores a list, and appends the value specified by " +"the const_ keyword argument to the list. (Note that the const_ keyword " +"argument defaults to ``None``.) The ``'append_const'`` action is typically " +"useful when multiple arguments need to store constants to the same list. For " +"example::" +msgstr "" + +#: ../Doc/library/argparse.rst:775 +msgid "" +"``'count'`` - This counts the number of times a keyword argument occurs. For " +"example, this is useful for increasing verbosity levels::" +msgstr "" + +#: ../Doc/library/argparse.rst:783 +msgid "" +"``'help'`` - This prints a complete help message for all the options in the " +"current parser and then exits. By default a help action is automatically " +"added to the parser. See :class:`ArgumentParser` for details of how the " +"output is created." +msgstr "" + +#: ../Doc/library/argparse.rst:788 +msgid "" +"``'version'`` - This expects a ``version=`` keyword argument in the :meth:" +"`~ArgumentParser.add_argument` call, and prints version information and " +"exits when invoked::" +msgstr "" + +#: ../Doc/library/argparse.rst:798 +msgid "" +"You may also specify an arbitrary action by passing an Action subclass or " +"other object that implements the same interface. The recommended way to do " +"this is to extend :class:`Action`, overriding the ``__call__`` method and " +"optionally the ``__init__`` method." +msgstr "" + +#: ../Doc/library/argparse.rst:803 +msgid "An example of a custom action::" +msgstr "" + +#: ../Doc/library/argparse.rst:823 +msgid "For more details, see :class:`Action`." +msgstr "" + +#: ../Doc/library/argparse.rst:826 +msgid "nargs" +msgstr "" + +#: ../Doc/library/argparse.rst:828 +msgid "" +"ArgumentParser objects usually associate a single command-line argument with " +"a single action to be taken. The ``nargs`` keyword argument associates a " +"different number of command-line arguments with a single action. The " +"supported values are:" +msgstr "" + +#: ../Doc/library/argparse.rst:833 +msgid "" +"``N`` (an integer). ``N`` arguments from the command line will be gathered " +"together into a list. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:842 +msgid "" +"Note that ``nargs=1`` produces a list of one item. This is different from " +"the default, in which the item is produced by itself." +msgstr "" + +#: ../Doc/library/argparse.rst:845 +msgid "" +"``'?'``. One argument will be consumed from the command line if possible, " +"and produced as a single item. If no command-line argument is present, the " +"value from default_ will be produced. Note that for optional arguments, " +"there is an additional case - the option string is present but not followed " +"by a command-line argument. In this case the value from const_ will be " +"produced. Some examples to illustrate this::" +msgstr "" + +#: ../Doc/library/argparse.rst:862 +msgid "" +"One of the more common uses of ``nargs='?'`` is to allow optional input and " +"output files::" +msgstr "" + +#: ../Doc/library/argparse.rst:877 +msgid "" +"``'*'``. All command-line arguments present are gathered into a list. Note " +"that it generally doesn't make much sense to have more than one positional " +"argument with ``nargs='*'``, but multiple optional arguments with " +"``nargs='*'`` is possible. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:889 +msgid "" +"``'+'``. Just like ``'*'``, all command-line args present are gathered into " +"a list. Additionally, an error message will be generated if there wasn't at " +"least one command-line argument present. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:901 +msgid "" +"``argparse.REMAINDER``. All the remaining command-line arguments are " +"gathered into a list. This is commonly useful for command line utilities " +"that dispatch to other command line utilities::" +msgstr "" + +#: ../Doc/library/argparse.rst:912 +msgid "" +"If the ``nargs`` keyword argument is not provided, the number of arguments " +"consumed is determined by the action_. Generally this means a single " +"command-line argument will be consumed and a single item (not a list) will " +"be produced." +msgstr "" + +#: ../Doc/library/argparse.rst:918 +msgid "const" +msgstr "" + +#: ../Doc/library/argparse.rst:920 +msgid "" +"The ``const`` argument of :meth:`~ArgumentParser.add_argument` is used to " +"hold constant values that are not read from the command line but are " +"required for the various :class:`ArgumentParser` actions. The two most " +"common uses of it are:" +msgstr "" + +#: ../Doc/library/argparse.rst:924 +msgid "" +"When :meth:`~ArgumentParser.add_argument` is called with " +"``action='store_const'`` or ``action='append_const'``. These actions add " +"the ``const`` value to one of the attributes of the object returned by :meth:" +"`~ArgumentParser.parse_args`. See the action_ description for examples." +msgstr "" + +#: ../Doc/library/argparse.rst:929 +msgid "" +"When :meth:`~ArgumentParser.add_argument` is called with option strings " +"(like ``-f`` or ``--foo``) and ``nargs='?'``. This creates an optional " +"argument that can be followed by zero or one command-line arguments. When " +"parsing the command line, if the option string is encountered with no " +"command-line argument following it, the value of ``const`` will be assumed " +"instead. See the nargs_ description for examples." +msgstr "" + +#: ../Doc/library/argparse.rst:936 +msgid "" +"With the ``'store_const'`` and ``'append_const'`` actions, the ``const`` " +"keyword argument must be given. For other actions, it defaults to ``None``." +msgstr "" + +#: ../Doc/library/argparse.rst:941 +msgid "default" +msgstr "" + +#: ../Doc/library/argparse.rst:943 +msgid "" +"All optional arguments and some positional arguments may be omitted at the " +"command line. The ``default`` keyword argument of :meth:`~ArgumentParser." +"add_argument`, whose value defaults to ``None``, specifies what value should " +"be used if the command-line argument is not present. For optional arguments, " +"the ``default`` value is used when the option string was not present at the " +"command line::" +msgstr "" + +#: ../Doc/library/argparse.rst:957 +msgid "" +"If the ``default`` value is a string, the parser parses the value as if it " +"were a command-line argument. In particular, the parser applies any type_ " +"conversion argument, if provided, before setting the attribute on the :class:" +"`Namespace` return value. Otherwise, the parser uses the value as is::" +msgstr "" + +#: ../Doc/library/argparse.rst:968 +msgid "" +"For positional arguments with nargs_ equal to ``?`` or ``*``, the " +"``default`` value is used when no command-line argument was present::" +msgstr "" + +#: ../Doc/library/argparse.rst:979 +msgid "" +"Providing ``default=argparse.SUPPRESS`` causes no attribute to be added if " +"the command-line argument was not present.::" +msgstr "" + +#: ../Doc/library/argparse.rst:991 ../Doc/library/tkinter.rst:732 +msgid "type" +msgstr "" + +#: ../Doc/library/argparse.rst:993 +msgid "" +"By default, :class:`ArgumentParser` objects read command-line arguments in " +"as simple strings. However, quite often the command-line string should " +"instead be interpreted as another type, like a :class:`float` or :class:" +"`int`. The ``type`` keyword argument of :meth:`~ArgumentParser." +"add_argument` allows any necessary type-checking and type conversions to be " +"performed. Common built-in types and functions can be used directly as the " +"value of the ``type`` argument::" +msgstr "" + +#: ../Doc/library/argparse.rst:1006 +msgid "" +"See the section on the default_ keyword argument for information on when the " +"``type`` argument is applied to default arguments." +msgstr "" + +#: ../Doc/library/argparse.rst:1009 +msgid "" +"To ease the use of various types of files, the argparse module provides the " +"factory FileType which takes the ``mode=``, ``bufsize=``, ``encoding=`` and " +"``errors=`` arguments of the :func:`open` function. For example, " +"``FileType('w')`` can be used to create a writable file::" +msgstr "" + +#: ../Doc/library/argparse.rst:1019 +msgid "" +"``type=`` can take any callable that takes a single string argument and " +"returns the converted value::" +msgstr "" + +#: ../Doc/library/argparse.rst:1038 +msgid "" +"The choices_ keyword argument may be more convenient for type checkers that " +"simply check against a range of values::" +msgstr "" + +#: ../Doc/library/argparse.rst:1049 +msgid "See the choices_ section for more details." +msgstr "" + +#: ../Doc/library/argparse.rst:1053 +msgid "choices" +msgstr "" + +#: ../Doc/library/argparse.rst:1055 +msgid "" +"Some command-line arguments should be selected from a restricted set of " +"values. These can be handled by passing a container object as the *choices* " +"keyword argument to :meth:`~ArgumentParser.add_argument`. When the command " +"line is parsed, argument values will be checked, and an error message will " +"be displayed if the argument was not one of the acceptable values::" +msgstr "" + +#: ../Doc/library/argparse.rst:1070 +msgid "" +"Note that inclusion in the *choices* container is checked after any type_ " +"conversions have been performed, so the type of the objects in the *choices* " +"container should match the type_ specified::" +msgstr "" + +#: ../Doc/library/argparse.rst:1082 +msgid "" +"Any object that supports the ``in`` operator can be passed as the *choices* " +"value, so :class:`dict` objects, :class:`set` objects, custom containers, " +"etc. are all supported." +msgstr "" + +#: ../Doc/library/argparse.rst:1088 +msgid "required" +msgstr "" + +#: ../Doc/library/argparse.rst:1090 +msgid "" +"In general, the :mod:`argparse` module assumes that flags like ``-f`` and " +"``--bar`` indicate *optional* arguments, which can always be omitted at the " +"command line. To make an option *required*, ``True`` can be specified for " +"the ``required=`` keyword argument to :meth:`~ArgumentParser.add_argument`::" +msgstr "" + +#: ../Doc/library/argparse.rst:1103 +msgid "" +"As the example shows, if an option is marked as ``required``, :meth:" +"`~ArgumentParser.parse_args` will report an error if that option is not " +"present at the command line." +msgstr "" + +#: ../Doc/library/argparse.rst:1109 +msgid "" +"Required options are generally considered bad form because users expect " +"*options* to be *optional*, and thus they should be avoided when possible." +msgstr "" + +#: ../Doc/library/argparse.rst:1114 +msgid "help" +msgstr "" + +#: ../Doc/library/argparse.rst:1116 +msgid "" +"The ``help`` value is a string containing a brief description of the " +"argument. When a user requests help (usually by using ``-h`` or ``--help`` " +"at the command line), these ``help`` descriptions will be displayed with " +"each argument::" +msgstr "" + +#: ../Doc/library/argparse.rst:1136 +msgid "" +"The ``help`` strings can include various format specifiers to avoid " +"repetition of things like the program name or the argument default_. The " +"available specifiers include the program name, ``%(prog)s`` and most keyword " +"arguments to :meth:`~ArgumentParser.add_argument`, e.g. ``%(default)s``, ``" +"%(type)s``, etc.::" +msgstr "" + +#: ../Doc/library/argparse.rst:1153 +msgid "" +"As the help string supports %-formatting, if you want a literal ``%`` to " +"appear in the help string, you must escape it as ``%%``." +msgstr "" + +#: ../Doc/library/argparse.rst:1156 +msgid "" +":mod:`argparse` supports silencing the help entry for certain options, by " +"setting the ``help`` value to ``argparse.SUPPRESS``::" +msgstr "" + +#: ../Doc/library/argparse.rst:1169 +msgid "metavar" +msgstr "" + +#: ../Doc/library/argparse.rst:1171 +msgid "" +"When :class:`ArgumentParser` generates help messages, it needs some way to " +"refer to each expected argument. By default, ArgumentParser objects use the " +"dest_ value as the \"name\" of each object. By default, for positional " +"argument actions, the dest_ value is used directly, and for optional " +"argument actions, the dest_ value is uppercased. So, a single positional " +"argument with ``dest='bar'`` will be referred to as ``bar``. A single " +"optional argument ``--foo`` that should be followed by a single command-line " +"argument will be referred to as ``FOO``. An example::" +msgstr "" + +#: ../Doc/library/argparse.rst:1195 +msgid "An alternative name can be specified with ``metavar``::" +msgstr "" + +#: ../Doc/library/argparse.rst:1212 +msgid "" +"Note that ``metavar`` only changes the *displayed* name - the name of the " +"attribute on the :meth:`~ArgumentParser.parse_args` object is still " +"determined by the dest_ value." +msgstr "" + +#: ../Doc/library/argparse.rst:1216 +msgid "" +"Different values of ``nargs`` may cause the metavar to be used multiple " +"times. Providing a tuple to ``metavar`` specifies a different display for " +"each of the arguments::" +msgstr "" + +#: ../Doc/library/argparse.rst:1233 +msgid "dest" +msgstr "" + +#: ../Doc/library/argparse.rst:1235 +msgid "" +"Most :class:`ArgumentParser` actions add some value as an attribute of the " +"object returned by :meth:`~ArgumentParser.parse_args`. The name of this " +"attribute is determined by the ``dest`` keyword argument of :meth:" +"`~ArgumentParser.add_argument`. For positional argument actions, ``dest`` " +"is normally supplied as the first argument to :meth:`~ArgumentParser." +"add_argument`::" +msgstr "" + +#: ../Doc/library/argparse.rst:1247 +msgid "" +"For optional argument actions, the value of ``dest`` is normally inferred " +"from the option strings. :class:`ArgumentParser` generates the value of " +"``dest`` by taking the first long option string and stripping away the " +"initial ``--`` string. If no long option strings were supplied, ``dest`` " +"will be derived from the first short option string by stripping the initial " +"``-`` character. Any internal ``-`` characters will be converted to ``_`` " +"characters to make sure the string is a valid attribute name. The examples " +"below illustrate this behavior::" +msgstr "" + +#: ../Doc/library/argparse.rst:1264 +msgid "``dest`` allows a custom attribute name to be provided::" +msgstr "" + +#: ../Doc/library/argparse.rst:1272 +msgid "Action classes" +msgstr "" + +#: ../Doc/library/argparse.rst:1274 +msgid "" +"Action classes implement the Action API, a callable which returns a callable " +"which processes arguments from the command-line. Any object which follows " +"this API may be passed as the ``action`` parameter to :meth:`add_argument`." +msgstr "" + +#: ../Doc/library/argparse.rst:1283 +msgid "" +"Action objects are used by an ArgumentParser to represent the information " +"needed to parse a single argument from one or more strings from the command " +"line. The Action class must accept the two positional arguments plus any " +"keyword arguments passed to :meth:`ArgumentParser.add_argument` except for " +"the ``action`` itself." +msgstr "" + +#: ../Doc/library/argparse.rst:1289 +msgid "" +"Instances of Action (or return value of any callable to the ``action`` " +"parameter) should have attributes \"dest\", \"option_strings\", \"default\", " +"\"type\", \"required\", \"help\", etc. defined. The easiest way to ensure " +"these attributes are defined is to call ``Action.__init__``." +msgstr "" + +#: ../Doc/library/argparse.rst:1294 +msgid "" +"Action instances should be callable, so subclasses must override the " +"``__call__`` method, which should accept four parameters:" +msgstr "" + +#: ../Doc/library/argparse.rst:1297 +msgid "``parser`` - The ArgumentParser object which contains this action." +msgstr "" + +#: ../Doc/library/argparse.rst:1299 +msgid "" +"``namespace`` - The :class:`Namespace` object that will be returned by :meth:" +"`~ArgumentParser.parse_args`. Most actions add an attribute to this object " +"using :func:`setattr`." +msgstr "" + +#: ../Doc/library/argparse.rst:1303 +msgid "" +"``values`` - The associated command-line arguments, with any type " +"conversions applied. Type conversions are specified with the type_ keyword " +"argument to :meth:`~ArgumentParser.add_argument`." +msgstr "" + +#: ../Doc/library/argparse.rst:1307 +msgid "" +"``option_string`` - The option string that was used to invoke this action. " +"The ``option_string`` argument is optional, and will be absent if the action " +"is associated with a positional argument." +msgstr "" + +#: ../Doc/library/argparse.rst:1311 +msgid "" +"The ``__call__`` method may perform arbitrary actions, but will typically " +"set attributes on the ``namespace`` based on ``dest`` and ``values``." +msgstr "" + +#: ../Doc/library/argparse.rst:1316 +msgid "The parse_args() method" +msgstr "" + +#: ../Doc/library/argparse.rst:1320 +msgid "" +"Convert argument strings to objects and assign them as attributes of the " +"namespace. Return the populated namespace." +msgstr "" + +#: ../Doc/library/argparse.rst:1323 +msgid "" +"Previous calls to :meth:`add_argument` determine exactly what objects are " +"created and how they are assigned. See the documentation for :meth:" +"`add_argument` for details." +msgstr "" + +#: ../Doc/library/argparse.rst:1327 +msgid "" +"By default, the argument strings are taken from :data:`sys.argv`, and a new " +"empty :class:`Namespace` object is created for the attributes." +msgstr "" + +#: ../Doc/library/argparse.rst:1332 +msgid "Option value syntax" +msgstr "" + +#: ../Doc/library/argparse.rst:1334 +msgid "" +"The :meth:`~ArgumentParser.parse_args` method supports several ways of " +"specifying the value of an option (if it takes one). In the simplest case, " +"the option and its value are passed as two separate arguments::" +msgstr "" + +#: ../Doc/library/argparse.rst:1346 +msgid "" +"For long options (options with names longer than a single character), the " +"option and value can also be passed as a single command-line argument, using " +"``=`` to separate them::" +msgstr "" + +#: ../Doc/library/argparse.rst:1353 +msgid "" +"For short options (options only one character long), the option and its " +"value can be concatenated::" +msgstr "" + +#: ../Doc/library/argparse.rst:1359 +msgid "" +"Several short options can be joined together, using only a single ``-`` " +"prefix, as long as only the last option (or none of them) requires a value::" +msgstr "" + +#: ../Doc/library/argparse.rst:1371 +msgid "Invalid arguments" +msgstr "" + +#: ../Doc/library/argparse.rst:1373 +msgid "" +"While parsing the command line, :meth:`~ArgumentParser.parse_args` checks " +"for a variety of errors, including ambiguous options, invalid types, invalid " +"options, wrong number of positional arguments, etc. When it encounters such " +"an error, it exits and prints the error along with a usage message::" +msgstr "" + +#: ../Doc/library/argparse.rst:1399 +msgid "Arguments containing ``-``" +msgstr "" + +#: ../Doc/library/argparse.rst:1401 +msgid "" +"The :meth:`~ArgumentParser.parse_args` method attempts to give errors " +"whenever the user has clearly made a mistake, but some situations are " +"inherently ambiguous. For example, the command-line argument ``-1`` could " +"either be an attempt to specify an option or an attempt to provide a " +"positional argument. The :meth:`~ArgumentParser.parse_args` method is " +"cautious here: positional arguments may only begin with ``-`` if they look " +"like negative numbers and there are no options in the parser that look like " +"negative numbers::" +msgstr "" + +#: ../Doc/library/argparse.rst:1439 +msgid "" +"If you have positional arguments that must begin with ``-`` and don't look " +"like negative numbers, you can insert the pseudo-argument ``'--'`` which " +"tells :meth:`~ArgumentParser.parse_args` that everything after that is a " +"positional argument::" +msgstr "" + +#: ../Doc/library/argparse.rst:1450 +msgid "Argument abbreviations (prefix matching)" +msgstr "" + +#: ../Doc/library/argparse.rst:1452 +msgid "" +"The :meth:`~ArgumentParser.parse_args` method :ref:`by default " +"` allows long options to be abbreviated to a prefix, if the " +"abbreviation is unambiguous (the prefix matches a unique option)::" +msgstr "" + +#: ../Doc/library/argparse.rst:1467 +msgid "" +"An error is produced for arguments that could produce more than one options. " +"This feature can be disabled by setting :ref:`allow_abbrev` to ``False``." +msgstr "" + +#: ../Doc/library/argparse.rst:1472 +msgid "Beyond ``sys.argv``" +msgstr "" + +#: ../Doc/library/argparse.rst:1474 +msgid "" +"Sometimes it may be useful to have an ArgumentParser parse arguments other " +"than those of :data:`sys.argv`. This can be accomplished by passing a list " +"of strings to :meth:`~ArgumentParser.parse_args`. This is useful for " +"testing at the interactive prompt::" +msgstr "" + +#: ../Doc/library/argparse.rst:1493 +msgid "The Namespace object" +msgstr "" + +#: ../Doc/library/argparse.rst:1497 +msgid "" +"Simple class used by default by :meth:`~ArgumentParser.parse_args` to create " +"an object holding attributes and return it." +msgstr "" + +#: ../Doc/library/argparse.rst:1500 +msgid "" +"This class is deliberately simple, just an :class:`object` subclass with a " +"readable string representation. If you prefer to have dict-like view of the " +"attributes, you can use the standard Python idiom, :func:`vars`::" +msgstr "" + +#: ../Doc/library/argparse.rst:1510 +msgid "" +"It may also be useful to have an :class:`ArgumentParser` assign attributes " +"to an already existing object, rather than a new :class:`Namespace` object. " +"This can be achieved by specifying the ``namespace=`` keyword argument::" +msgstr "" + +#: ../Doc/library/argparse.rst:1526 +msgid "Other utilities" +msgstr "" + +#: ../Doc/library/argparse.rst:1529 +msgid "Sub-commands" +msgstr "" + +#: ../Doc/library/argparse.rst:1536 +msgid "" +"Many programs split up their functionality into a number of sub-commands, " +"for example, the ``svn`` program can invoke sub-commands like ``svn " +"checkout``, ``svn update``, and ``svn commit``. Splitting up functionality " +"this way can be a particularly good idea when a program performs several " +"different functions which require different kinds of command-line " +"arguments. :class:`ArgumentParser` supports the creation of such sub-" +"commands with the :meth:`add_subparsers` method. The :meth:`add_subparsers` " +"method is normally called with no arguments and returns a special action " +"object. This object has a single method, :meth:`~ArgumentParser." +"add_parser`, which takes a command name and any :class:`ArgumentParser` " +"constructor arguments, and returns an :class:`ArgumentParser` object that " +"can be modified as usual." +msgstr "" + +#: ../Doc/library/argparse.rst:1548 +msgid "Description of parameters:" +msgstr "" + +#: ../Doc/library/argparse.rst:1550 +msgid "" +"title - title for the sub-parser group in help output; by default " +"\"subcommands\" if description is provided, otherwise uses title for " +"positional arguments" +msgstr "" + +#: ../Doc/library/argparse.rst:1554 +msgid "" +"description - description for the sub-parser group in help output, by " +"default None" +msgstr "" + +#: ../Doc/library/argparse.rst:1557 +msgid "" +"prog - usage information that will be displayed with sub-command help, by " +"default the name of the program and any positional arguments before the " +"subparser argument" +msgstr "" + +#: ../Doc/library/argparse.rst:1561 +msgid "" +"parser_class - class which will be used to create sub-parser instances, by " +"default the class of the current parser (e.g. ArgumentParser)" +msgstr "" + +#: ../Doc/library/argparse.rst:1564 +msgid "" +"action_ - the basic type of action to be taken when this argument is " +"encountered at the command line" +msgstr "" + +#: ../Doc/library/argparse.rst:1567 +msgid "" +"dest_ - name of the attribute under which sub-command name will be stored; " +"by default None and no value is stored" +msgstr "" + +#: ../Doc/library/argparse.rst:1570 +msgid "help_ - help for sub-parser group in help output, by default None" +msgstr "" + +#: ../Doc/library/argparse.rst:1572 +msgid "" +"metavar_ - string presenting available sub-commands in help; by default it " +"is None and presents sub-commands in form {cmd1, cmd2, ..}" +msgstr "" + +#: ../Doc/library/argparse.rst:1575 +msgid "Some example usage::" +msgstr "" + +#: ../Doc/library/argparse.rst:1596 +msgid "" +"Note that the object returned by :meth:`parse_args` will only contain " +"attributes for the main parser and the subparser that was selected by the " +"command line (and not any other subparsers). So in the example above, when " +"the ``a`` command is specified, only the ``foo`` and ``bar`` attributes are " +"present, and when the ``b`` command is specified, only the ``foo`` and " +"``baz`` attributes are present." +msgstr "" + +#: ../Doc/library/argparse.rst:1603 +msgid "" +"Similarly, when a help message is requested from a subparser, only the help " +"for that particular parser will be printed. The help message will not " +"include parent parser or sibling parser messages. (A help message for each " +"subparser command, however, can be given by supplying the ``help=`` argument " +"to :meth:`add_parser` as above.)" +msgstr "" + +#: ../Doc/library/argparse.rst:1639 +msgid "" +"The :meth:`add_subparsers` method also supports ``title`` and " +"``description`` keyword arguments. When either is present, the subparser's " +"commands will appear in their own group in the help output. For example::" +msgstr "" + +#: ../Doc/library/argparse.rst:1660 +msgid "" +"Furthermore, ``add_parser`` supports an additional ``aliases`` argument, " +"which allows multiple strings to refer to the same subparser. This example, " +"like ``svn``, aliases ``co`` as a shorthand for ``checkout``::" +msgstr "" + +#: ../Doc/library/argparse.rst:1671 +msgid "" +"One particularly effective way of handling sub-commands is to combine the " +"use of the :meth:`add_subparsers` method with calls to :meth:`set_defaults` " +"so that each subparser knows which Python function it should execute. For " +"example::" +msgstr "" + +#: ../Doc/library/argparse.rst:1708 +msgid "" +"This way, you can let :meth:`parse_args` do the job of calling the " +"appropriate function after argument parsing is complete. Associating " +"functions with actions like this is typically the easiest way to handle the " +"different actions for each of your subparsers. However, if it is necessary " +"to check the name of the subparser that was invoked, the ``dest`` keyword " +"argument to the :meth:`add_subparsers` call will work::" +msgstr "" + +#: ../Doc/library/argparse.rst:1726 +msgid "FileType objects" +msgstr "" + +#: ../Doc/library/argparse.rst:1730 +msgid "" +"The :class:`FileType` factory creates objects that can be passed to the type " +"argument of :meth:`ArgumentParser.add_argument`. Arguments that have :class:" +"`FileType` objects as their type will open command-line arguments as files " +"with the requested modes, buffer sizes, encodings and error handling (see " +"the :func:`open` function for more details)::" +msgstr "" + +#: ../Doc/library/argparse.rst:1742 +msgid "" +"FileType objects understand the pseudo-argument ``'-'`` and automatically " +"convert this into ``sys.stdin`` for readable :class:`FileType` objects and " +"``sys.stdout`` for writable :class:`FileType` objects::" +msgstr "" + +#: ../Doc/library/argparse.rst:1751 +msgid "The *encodings* and *errors* keyword arguments." +msgstr "" + +#: ../Doc/library/argparse.rst:1756 +msgid "Argument groups" +msgstr "" + +#: ../Doc/library/argparse.rst:1760 +msgid "" +"By default, :class:`ArgumentParser` groups command-line arguments into " +"\"positional arguments\" and \"optional arguments\" when displaying help " +"messages. When there is a better conceptual grouping of arguments than this " +"default one, appropriate groups can be created using the :meth:" +"`add_argument_group` method::" +msgstr "" + +#: ../Doc/library/argparse.rst:1777 +msgid "" +"The :meth:`add_argument_group` method returns an argument group object which " +"has an :meth:`~ArgumentParser.add_argument` method just like a regular :" +"class:`ArgumentParser`. When an argument is added to the group, the parser " +"treats it just like a normal argument, but displays the argument in a " +"separate group for help messages. The :meth:`add_argument_group` method " +"accepts *title* and *description* arguments which can be used to customize " +"this display::" +msgstr "" + +#: ../Doc/library/argparse.rst:1803 +msgid "" +"Note that any arguments not in your user-defined groups will end up back in " +"the usual \"positional arguments\" and \"optional arguments\" sections." +msgstr "" + +#: ../Doc/library/argparse.rst:1808 +msgid "Mutual exclusion" +msgstr "" + +#: ../Doc/library/argparse.rst:1812 +msgid "" +"Create a mutually exclusive group. :mod:`argparse` will make sure that only " +"one of the arguments in the mutually exclusive group was present on the " +"command line::" +msgstr "" + +#: ../Doc/library/argparse.rst:1828 +msgid "" +"The :meth:`add_mutually_exclusive_group` method also accepts a *required* " +"argument, to indicate that at least one of the mutually exclusive arguments " +"is required::" +msgstr "" + +#: ../Doc/library/argparse.rst:1840 +msgid "" +"Note that currently mutually exclusive argument groups do not support the " +"*title* and *description* arguments of :meth:`~ArgumentParser." +"add_argument_group`." +msgstr "" + +#: ../Doc/library/argparse.rst:1846 +msgid "Parser defaults" +msgstr "" + +#: ../Doc/library/argparse.rst:1850 +msgid "" +"Most of the time, the attributes of the object returned by :meth:" +"`parse_args` will be fully determined by inspecting the command-line " +"arguments and the argument actions. :meth:`set_defaults` allows some " +"additional attributes that are determined without any inspection of the " +"command line to be added::" +msgstr "" + +#: ../Doc/library/argparse.rst:1862 +msgid "" +"Note that parser-level defaults always override argument-level defaults::" +msgstr "" + +#: ../Doc/library/argparse.rst:1870 +msgid "" +"Parser-level defaults can be particularly useful when working with multiple " +"parsers. See the :meth:`~ArgumentParser.add_subparsers` method for an " +"example of this type." +msgstr "" + +#: ../Doc/library/argparse.rst:1876 +msgid "" +"Get the default value for a namespace attribute, as set by either :meth:" +"`~ArgumentParser.add_argument` or by :meth:`~ArgumentParser.set_defaults`::" +msgstr "" + +#: ../Doc/library/argparse.rst:1887 +msgid "Printing help" +msgstr "" + +#: ../Doc/library/argparse.rst:1889 +msgid "" +"In most typical applications, :meth:`~ArgumentParser.parse_args` will take " +"care of formatting and printing any usage or error messages. However, " +"several formatting methods are available:" +msgstr "" + +#: ../Doc/library/argparse.rst:1895 +msgid "" +"Print a brief description of how the :class:`ArgumentParser` should be " +"invoked on the command line. If *file* is ``None``, :data:`sys.stdout` is " +"assumed." +msgstr "" + +#: ../Doc/library/argparse.rst:1901 +msgid "" +"Print a help message, including the program usage and information about the " +"arguments registered with the :class:`ArgumentParser`. If *file* is " +"``None``, :data:`sys.stdout` is assumed." +msgstr "" + +#: ../Doc/library/argparse.rst:1905 +msgid "" +"There are also variants of these methods that simply return a string instead " +"of printing it:" +msgstr "" + +#: ../Doc/library/argparse.rst:1910 +msgid "" +"Return a string containing a brief description of how the :class:" +"`ArgumentParser` should be invoked on the command line." +msgstr "" + +#: ../Doc/library/argparse.rst:1915 +msgid "" +"Return a string containing a help message, including the program usage and " +"information about the arguments registered with the :class:`ArgumentParser`." +msgstr "" + +#: ../Doc/library/argparse.rst:1920 +msgid "Partial parsing" +msgstr "" + +#: ../Doc/library/argparse.rst:1924 +msgid "" +"Sometimes a script may only parse a few of the command-line arguments, " +"passing the remaining arguments on to another script or program. In these " +"cases, the :meth:`~ArgumentParser.parse_known_args` method can be useful. " +"It works much like :meth:`~ArgumentParser.parse_args` except that it does " +"not produce an error when extra arguments are present. Instead, it returns " +"a two item tuple containing the populated namespace and the list of " +"remaining argument strings." +msgstr "" + +#: ../Doc/library/argparse.rst:1940 +msgid "" +":ref:`Prefix matching ` rules apply to :meth:" +"`parse_known_args`. The parser may consume an option even if it's just a " +"prefix of one of its known options, instead of leaving it in the remaining " +"arguments list." +msgstr "" + +#: ../Doc/library/argparse.rst:1947 +msgid "Customizing file parsing" +msgstr "" + +#: ../Doc/library/argparse.rst:1951 +msgid "" +"Arguments that are read from a file (see the *fromfile_prefix_chars* keyword " +"argument to the :class:`ArgumentParser` constructor) are read one argument " +"per line. :meth:`convert_arg_line_to_args` can be overridden for fancier " +"reading." +msgstr "" + +#: ../Doc/library/argparse.rst:1956 +msgid "" +"This method takes a single argument *arg_line* which is a string read from " +"the argument file. It returns a list of arguments parsed from this string. " +"The method is called once per line read from the argument file, in order." +msgstr "" + +#: ../Doc/library/argparse.rst:1960 +msgid "" +"A useful override of this method is one that treats each space-separated " +"word as an argument. The following example demonstrates how to do this::" +msgstr "" + +#: ../Doc/library/argparse.rst:1969 +msgid "Exiting methods" +msgstr "" + +#: ../Doc/library/argparse.rst:1973 +msgid "" +"This method terminates the program, exiting with the specified *status* and, " +"if given, it prints a *message* before that." +msgstr "" + +#: ../Doc/library/argparse.rst:1978 +msgid "" +"This method prints a usage message including the *message* to the standard " +"error and terminates the program with a status code of 2." +msgstr "" + +#: ../Doc/library/argparse.rst:1984 +msgid "Upgrading optparse code" +msgstr "" + +#: ../Doc/library/argparse.rst:1986 +msgid "" +"Originally, the :mod:`argparse` module had attempted to maintain " +"compatibility with :mod:`optparse`. However, :mod:`optparse` was difficult " +"to extend transparently, particularly with the changes required to support " +"the new ``nargs=`` specifiers and better usage messages. When most " +"everything in :mod:`optparse` had either been copy-pasted over or monkey-" +"patched, it no longer seemed practical to try to maintain the backwards " +"compatibility." +msgstr "" + +#: ../Doc/library/argparse.rst:1993 +msgid "" +"The :mod:`argparse` module improves on the standard library :mod:`optparse` " +"module in a number of ways including:" +msgstr "" + +#: ../Doc/library/argparse.rst:1996 +msgid "Handling positional arguments." +msgstr "" + +#: ../Doc/library/argparse.rst:1997 +msgid "Supporting sub-commands." +msgstr "" + +#: ../Doc/library/argparse.rst:1998 +msgid "Allowing alternative option prefixes like ``+`` and ``/``." +msgstr "" + +#: ../Doc/library/argparse.rst:1999 +msgid "Handling zero-or-more and one-or-more style arguments." +msgstr "" + +#: ../Doc/library/argparse.rst:2000 +msgid "Producing more informative usage messages." +msgstr "" + +#: ../Doc/library/argparse.rst:2001 +msgid "Providing a much simpler interface for custom ``type`` and ``action``." +msgstr "" + +#: ../Doc/library/argparse.rst:2003 +msgid "A partial upgrade path from :mod:`optparse` to :mod:`argparse`:" +msgstr "" + +#: ../Doc/library/argparse.rst:2005 +msgid "" +"Replace all :meth:`optparse.OptionParser.add_option` calls with :meth:" +"`ArgumentParser.add_argument` calls." +msgstr "" + +#: ../Doc/library/argparse.rst:2008 +msgid "" +"Replace ``(options, args) = parser.parse_args()`` with ``args = parser." +"parse_args()`` and add additional :meth:`ArgumentParser.add_argument` calls " +"for the positional arguments. Keep in mind that what was previously called " +"``options``, now in :mod:`argparse` context is called ``args``." +msgstr "" + +#: ../Doc/library/argparse.rst:2013 +msgid "" +"Replace callback actions and the ``callback_*`` keyword arguments with " +"``type`` or ``action`` arguments." +msgstr "" + +#: ../Doc/library/argparse.rst:2016 +msgid "" +"Replace string names for ``type`` keyword arguments with the corresponding " +"type objects (e.g. int, float, complex, etc)." +msgstr "" + +#: ../Doc/library/argparse.rst:2019 +msgid "" +"Replace :class:`optparse.Values` with :class:`Namespace` and :exc:`optparse." +"OptionError` and :exc:`optparse.OptionValueError` with :exc:`ArgumentError`." +msgstr "" + +#: ../Doc/library/argparse.rst:2023 +msgid "" +"Replace strings with implicit arguments such as ``%default`` or ``%prog`` " +"with the standard Python syntax to use dictionaries to format strings, that " +"is, ``%(default)s`` and ``%(prog)s``." +msgstr "" + +#: ../Doc/library/argparse.rst:2027 +msgid "" +"Replace the OptionParser constructor ``version`` argument with a call to " +"``parser.add_argument('--version', action='version', version='')``." +msgstr "" + +#: ../Doc/library/array.rst:2 +msgid ":mod:`array` --- Efficient arrays of numeric values" +msgstr "" + +#: ../Doc/library/array.rst:11 +msgid "" +"This module defines an object type which can compactly represent an array of " +"basic values: characters, integers, floating point numbers. Arrays are " +"sequence types and behave very much like lists, except that the type of " +"objects stored in them is constrained. The type is specified at object " +"creation time by using a :dfn:`type code`, which is a single character. The " +"following type codes are defined:" +msgstr "" + +#: ../Doc/library/array.rst:19 +msgid "Type code" +msgstr "" + +#: ../Doc/library/array.rst:19 ../Doc/library/struct.rst:186 +msgid "C Type" +msgstr "" + +#: ../Doc/library/array.rst:19 ../Doc/library/xml.dom.rst:981 +msgid "Python Type" +msgstr "" + +#: ../Doc/library/array.rst:19 +msgid "Minimum size in bytes" +msgstr "" + +#: ../Doc/library/array.rst:19 ../Doc/library/binhex.rst:50 +#: ../Doc/library/datetime.rst:1966 ../Doc/library/datetime.rst:2072 +#: ../Doc/library/stdtypes.rst:90 ../Doc/library/stdtypes.rst:276 +#: ../Doc/library/stdtypes.rst:413 ../Doc/library/stdtypes.rst:849 +#: ../Doc/library/stdtypes.rst:1042 ../Doc/library/stdtypes.rst:2153 +#: ../Doc/library/stdtypes.rst:3253 ../Doc/library/struct.rst:186 +#: ../Doc/library/subprocess.rst:1205 ../Doc/library/time.rst:380 +#: ../Doc/library/webbrowser.rst:103 +msgid "Notes" +msgstr "" + +#: ../Doc/library/array.rst:21 ../Doc/library/functions.rst:915 +#: ../Doc/library/stdtypes.rst:3286 ../Doc/library/string.rst:425 +msgid "``'b'``" +msgstr "" + +#: ../Doc/library/array.rst:21 +msgid "signed char" +msgstr "" + +#: ../Doc/library/array.rst:21 ../Doc/library/array.rst:23 +#: ../Doc/library/array.rst:27 ../Doc/library/array.rst:29 +#: ../Doc/library/array.rst:31 ../Doc/library/array.rst:33 +#: ../Doc/library/array.rst:35 ../Doc/library/array.rst:37 +#: ../Doc/library/array.rst:39 ../Doc/library/array.rst:41 +#: ../Doc/library/ctypes.rst:239 ../Doc/library/ctypes.rst:241 +#: ../Doc/library/ctypes.rst:243 ../Doc/library/ctypes.rst:245 +#: ../Doc/library/ctypes.rst:247 ../Doc/library/ctypes.rst:249 +#: ../Doc/library/ctypes.rst:251 ../Doc/library/ctypes.rst:253 +#: ../Doc/library/ctypes.rst:255 ../Doc/library/ctypes.rst:257 +#: ../Doc/library/ctypes.rst:260 ../Doc/library/ctypes.rst:262 +#: ../Doc/library/json.rst:301 +msgid "int" +msgstr "" + +#: ../Doc/library/array.rst:21 ../Doc/library/array.rst:23 +#: ../Doc/library/ctypes.rst:1662 ../Doc/library/grp.rst:22 +#: ../Doc/library/pwd.rst:22 ../Doc/library/spwd.rst:25 +#: ../Doc/library/struct.rst:190 ../Doc/library/struct.rst:192 +#: ../Doc/library/struct.rst:194 ../Doc/library/struct.rst:196 +#: ../Doc/library/time.rst:540 ../Doc/library/tkinter.rst:434 +#: ../Doc/library/urllib.parse.rst:96 ../Doc/library/urllib.parse.rst:217 +#: ../Doc/library/urllib.parse.rst:302 +msgid "1" +msgstr "" + +#: ../Doc/library/array.rst:23 +msgid "``'B'``" +msgstr "" + +#: ../Doc/library/array.rst:23 +msgid "unsigned char" +msgstr "" + +#: ../Doc/library/array.rst:25 ../Doc/library/dbm.rst:188 +#: ../Doc/library/stdtypes.rst:2161 ../Doc/library/stdtypes.rst:3261 +msgid "``'u'``" +msgstr "" + +#: ../Doc/library/array.rst:25 +msgid "Py_UNICODE" +msgstr "" + +#: ../Doc/library/array.rst:25 +msgid "Unicode character" +msgstr "" + +#: ../Doc/library/array.rst:25 ../Doc/library/array.rst:27 +#: ../Doc/library/array.rst:29 ../Doc/library/array.rst:31 +#: ../Doc/library/array.rst:33 ../Doc/library/ctypes.rst:1665 +#: ../Doc/library/grp.rst:25 ../Doc/library/pwd.rst:24 +#: ../Doc/library/spwd.rst:27 ../Doc/library/struct.rst:198 +#: ../Doc/library/struct.rst:200 ../Doc/library/struct.rst:219 +#: ../Doc/library/time.rst:542 ../Doc/library/tkinter.rst:436 +#: ../Doc/library/urllib.parse.rst:98 ../Doc/library/urllib.parse.rst:219 +msgid "2" +msgstr "" + +#: ../Doc/library/array.rst:25 ../Doc/library/datetime.rst:910 +#: ../Doc/library/datetime.rst:1968 ../Doc/library/datetime.rst:1973 +#: ../Doc/library/datetime.rst:1985 ../Doc/library/datetime.rst:1990 +#: ../Doc/library/datetime.rst:2049 ../Doc/library/datetime.rst:2054 +#: ../Doc/library/datetime.rst:2058 ../Doc/library/stdtypes.rst:92 +#: ../Doc/library/stdtypes.rst:286 ../Doc/library/stdtypes.rst:851 +#: ../Doc/library/stdtypes.rst:854 ../Doc/library/stdtypes.rst:1053 +#: ../Doc/library/stdtypes.rst:2159 ../Doc/library/stdtypes.rst:3259 +#: ../Doc/library/struct.rst:196 ../Doc/library/time.rst:413 +#: ../Doc/library/webbrowser.rst:117 ../Doc/library/webbrowser.rst:119 +#: ../Doc/library/webbrowser.rst:121 +msgid "\\(1)" +msgstr "" + +#: ../Doc/library/array.rst:27 +msgid "``'h'``" +msgstr "" + +#: ../Doc/library/array.rst:27 +msgid "signed short" +msgstr "" + +#: ../Doc/library/array.rst:29 ../Doc/library/logging.handlers.rst:337 +msgid "``'H'``" +msgstr "" + +#: ../Doc/library/array.rst:29 +msgid "unsigned short" +msgstr "" + +#: ../Doc/library/array.rst:31 ../Doc/library/stdtypes.rst:2157 +#: ../Doc/library/stdtypes.rst:3257 +msgid "``'i'``" +msgstr "" + +#: ../Doc/library/array.rst:31 +msgid "signed int" +msgstr "" + +#: ../Doc/library/array.rst:33 +msgid "``'I'``" +msgstr "" + +#: ../Doc/library/array.rst:33 +msgid "unsigned int" +msgstr "" + +#: ../Doc/library/array.rst:35 +msgid "``'l'``" +msgstr "" + +#: ../Doc/library/array.rst:35 +msgid "signed long" +msgstr "" + +#: ../Doc/library/array.rst:35 ../Doc/library/array.rst:37 +#: ../Doc/library/array.rst:43 ../Doc/library/chunk.rst:31 +#: ../Doc/library/chunk.rst:33 ../Doc/library/ctypes.rst:1668 +#: ../Doc/library/pwd.rst:28 ../Doc/library/spwd.rst:32 +#: ../Doc/library/struct.rst:202 ../Doc/library/struct.rst:204 +#: ../Doc/library/struct.rst:206 ../Doc/library/struct.rst:208 +#: ../Doc/library/struct.rst:221 ../Doc/library/time.rst:546 +#: ../Doc/library/tkinter.rst:441 ../Doc/library/urllib.parse.rst:103 +#: ../Doc/library/urllib.parse.rst:223 +msgid "4" +msgstr "" + +#: ../Doc/library/array.rst:37 +msgid "``'L'``" +msgstr "" + +#: ../Doc/library/array.rst:37 +msgid "unsigned long" +msgstr "" + +#: ../Doc/library/array.rst:39 +msgid "``'q'``" +msgstr "" + +#: ../Doc/library/array.rst:39 +msgid "signed long long" +msgstr "" + +#: ../Doc/library/array.rst:39 ../Doc/library/array.rst:41 +#: ../Doc/library/array.rst:45 ../Doc/library/chunk.rst:37 +#: ../Doc/library/hashlib-blake2.rst:70 ../Doc/library/spwd.rst:45 +#: ../Doc/library/struct.rst:210 ../Doc/library/struct.rst:212 +#: ../Doc/library/struct.rst:223 ../Doc/library/time.rst:555 +msgid "8" +msgstr "" + +#: ../Doc/library/array.rst:39 ../Doc/library/array.rst:41 +#: ../Doc/library/datetime.rst:912 ../Doc/library/datetime.rst:2001 +#: ../Doc/library/stdtypes.rst:95 ../Doc/library/stdtypes.rst:289 +#: ../Doc/library/stdtypes.rst:309 ../Doc/library/stdtypes.rst:1081 +#: ../Doc/library/stdtypes.rst:2163 ../Doc/library/stdtypes.rst:2165 +#: ../Doc/library/stdtypes.rst:3263 ../Doc/library/stdtypes.rst:3265 +#: ../Doc/library/time.rst:416 ../Doc/library/webbrowser.rst:137 +msgid "\\(2)" +msgstr "" + +#: ../Doc/library/array.rst:41 +msgid "``'Q'``" +msgstr "" + +#: ../Doc/library/array.rst:41 +msgid "unsigned long long" +msgstr "" + +#: ../Doc/library/array.rst:43 ../Doc/library/dbm.rst:181 +#: ../Doc/library/stdtypes.rst:2171 ../Doc/library/stdtypes.rst:3271 +#: ../Doc/library/string.rst:464 +msgid "``'f'``" +msgstr "" + +#: ../Doc/library/array.rst:43 ../Doc/library/array.rst:45 +#: ../Doc/library/ctypes.rst:265 ../Doc/library/ctypes.rst:267 +#: ../Doc/library/ctypes.rst:269 ../Doc/library/json.rst:303 +#: ../Doc/library/struct.rst:219 ../Doc/library/struct.rst:221 +#: ../Doc/library/struct.rst:223 +msgid "float" +msgstr "" + +#: ../Doc/library/array.rst:45 ../Doc/library/stdtypes.rst:2155 +#: ../Doc/library/stdtypes.rst:3255 ../Doc/library/string.rst:430 +msgid "``'d'``" +msgstr "" + +#: ../Doc/library/array.rst:45 +msgid "double" +msgstr "" + +#: ../Doc/library/array.rst:48 ../Doc/library/datetime.rst:295 +#: ../Doc/library/datetime.rst:490 ../Doc/library/datetime.rst:2092 +#: ../Doc/library/stdtypes.rst:107 ../Doc/library/stdtypes.rst:320 +#: ../Doc/library/stdtypes.rst:431 ../Doc/library/stdtypes.rst:890 +#: ../Doc/library/stdtypes.rst:1092 ../Doc/library/stdtypes.rst:2199 +#: ../Doc/library/stdtypes.rst:3303 ../Doc/library/struct.rst:160 +#: ../Doc/library/struct.rst:235 ../Doc/library/subprocess.rst:1026 +#: ../Doc/library/time.rst:462 ../Doc/library/tkinter.rst:231 +#: ../Doc/library/tkinter.ttk.rst:831 ../Doc/library/webbrowser.rst:152 +msgid "Notes:" +msgstr "" + +#: ../Doc/library/array.rst:51 +msgid "" +"The ``'u'`` type code corresponds to Python's obsolete unicode character (:c:" +"type:`Py_UNICODE` which is :c:type:`wchar_t`). Depending on the platform, it " +"can be 16 bits or 32 bits." +msgstr "" + +#: ../Doc/library/array.rst:55 +msgid "" +"``'u'`` will be removed together with the rest of the :c:type:`Py_UNICODE` " +"API." +msgstr "" + +#: ../Doc/library/array.rst:59 +msgid "Deprecated since version 3.3, will be removed in version 4.0." +msgstr "" + +#: ../Doc/library/array.rst:61 +msgid "" +"The ``'q'`` and ``'Q'`` type codes are available only if the platform C " +"compiler used to build Python supports C :c:type:`long long`, or, on " +"Windows, :c:type:`__int64`." +msgstr "" + +#: ../Doc/library/array.rst:67 +msgid "" +"The actual representation of values is determined by the machine " +"architecture (strictly speaking, by the C implementation). The actual size " +"can be accessed through the :attr:`itemsize` attribute." +msgstr "" + +#: ../Doc/library/array.rst:71 +msgid "The module defines the following type:" +msgstr "" + +#: ../Doc/library/array.rst:76 +msgid "" +"A new array whose items are restricted by *typecode*, and initialized from " +"the optional *initializer* value, which must be a list, a :term:`bytes-like " +"object`, or iterable over elements of the appropriate type." +msgstr "" + +#: ../Doc/library/array.rst:81 +msgid "" +"If given a list or string, the initializer is passed to the new array's :" +"meth:`fromlist`, :meth:`frombytes`, or :meth:`fromunicode` method (see " +"below) to add initial items to the array. Otherwise, the iterable " +"initializer is passed to the :meth:`extend` method." +msgstr "" + +#: ../Doc/library/array.rst:89 +msgid "A string with all available type codes." +msgstr "" + +#: ../Doc/library/array.rst:91 +msgid "" +"Array objects support the ordinary sequence operations of indexing, slicing, " +"concatenation, and multiplication. When using slice assignment, the " +"assigned value must be an array object with the same type code; in all other " +"cases, :exc:`TypeError` is raised. Array objects also implement the buffer " +"interface, and may be used wherever :term:`bytes-like objects ` are supported." +msgstr "" + +#: ../Doc/library/array.rst:97 +msgid "The following data items and methods are also supported:" +msgstr "" + +#: ../Doc/library/array.rst:101 +msgid "The typecode character used to create the array." +msgstr "" + +#: ../Doc/library/array.rst:106 +msgid "The length in bytes of one array item in the internal representation." +msgstr "" + +#: ../Doc/library/array.rst:111 +msgid "Append a new item with value *x* to the end of the array." +msgstr "" + +#: ../Doc/library/array.rst:116 +msgid "" +"Return a tuple ``(address, length)`` giving the current memory address and " +"the length in elements of the buffer used to hold array's contents. The " +"size of the memory buffer in bytes can be computed as ``array.buffer_info()" +"[1] * array.itemsize``. This is occasionally useful when working with low-" +"level (and inherently unsafe) I/O interfaces that require memory addresses, " +"such as certain :c:func:`ioctl` operations. The returned numbers are valid " +"as long as the array exists and no length-changing operations are applied to " +"it." +msgstr "" + +#: ../Doc/library/array.rst:126 +msgid "" +"When using array objects from code written in C or C++ (the only way to " +"effectively make use of this information), it makes more sense to use the " +"buffer interface supported by array objects. This method is maintained for " +"backward compatibility and should be avoided in new code. The buffer " +"interface is documented in :ref:`bufferobjects`." +msgstr "" + +#: ../Doc/library/array.rst:135 +msgid "" +"\"Byteswap\" all items of the array. This is only supported for values " +"which are 1, 2, 4, or 8 bytes in size; for other types of values, :exc:" +"`RuntimeError` is raised. It is useful when reading data from a file " +"written on a machine with a different byte order." +msgstr "" + +#: ../Doc/library/array.rst:143 +msgid "Return the number of occurrences of *x* in the array." +msgstr "" + +#: ../Doc/library/array.rst:148 +msgid "" +"Append items from *iterable* to the end of the array. If *iterable* is " +"another array, it must have *exactly* the same type code; if not, :exc:" +"`TypeError` will be raised. If *iterable* is not an array, it must be " +"iterable and its elements must be the right type to be appended to the array." +msgstr "" + +#: ../Doc/library/array.rst:156 +msgid "" +"Appends items from the string, interpreting the string as an array of " +"machine values (as if it had been read from a file using the :meth:" +"`fromfile` method)." +msgstr "" + +#: ../Doc/library/array.rst:159 +msgid ":meth:`fromstring` is renamed to :meth:`frombytes` for clarity." +msgstr "" + +#: ../Doc/library/array.rst:165 +msgid "" +"Read *n* items (as machine values) from the :term:`file object` *f* and " +"append them to the end of the array. If less than *n* items are available, :" +"exc:`EOFError` is raised, but the items that were available are still " +"inserted into the array. *f* must be a real built-in file object; something " +"else with a :meth:`read` method won't do." +msgstr "" + +#: ../Doc/library/array.rst:174 +msgid "" +"Append items from the list. This is equivalent to ``for x in list: a." +"append(x)`` except that if there is a type error, the array is unchanged." +msgstr "" + +#: ../Doc/library/array.rst:180 +msgid "Deprecated alias for :meth:`frombytes`." +msgstr "" + +#: ../Doc/library/array.rst:185 +msgid "" +"Extends this array with data from the given unicode string. The array must " +"be a type ``'u'`` array; otherwise a :exc:`ValueError` is raised. Use " +"``array.frombytes(unicodestring.encode(enc))`` to append Unicode data to an " +"array of some other type." +msgstr "" + +#: ../Doc/library/array.rst:193 +msgid "" +"Return the smallest *i* such that *i* is the index of the first occurrence " +"of *x* in the array." +msgstr "" + +#: ../Doc/library/array.rst:199 +msgid "" +"Insert a new item with value *x* in the array before position *i*. Negative " +"values are treated as being relative to the end of the array." +msgstr "" + +#: ../Doc/library/array.rst:205 +msgid "" +"Removes the item with the index *i* from the array and returns it. The " +"optional argument defaults to ``-1``, so that by default the last item is " +"removed and returned." +msgstr "" + +#: ../Doc/library/array.rst:212 +msgid "Remove the first occurrence of *x* from the array." +msgstr "" + +#: ../Doc/library/array.rst:217 +msgid "Reverse the order of the items in the array." +msgstr "" + +#: ../Doc/library/array.rst:222 +msgid "" +"Convert the array to an array of machine values and return the bytes " +"representation (the same sequence of bytes that would be written to a file " +"by the :meth:`tofile` method.)" +msgstr "" + +#: ../Doc/library/array.rst:226 +msgid ":meth:`tostring` is renamed to :meth:`tobytes` for clarity." +msgstr "" + +#: ../Doc/library/array.rst:232 +msgid "Write all items (as machine values) to the :term:`file object` *f*." +msgstr "" + +#: ../Doc/library/array.rst:237 +msgid "Convert the array to an ordinary list with the same items." +msgstr "" + +#: ../Doc/library/array.rst:242 +msgid "Deprecated alias for :meth:`tobytes`." +msgstr "" + +#: ../Doc/library/array.rst:247 +msgid "" +"Convert the array to a unicode string. The array must be a type ``'u'`` " +"array; otherwise a :exc:`ValueError` is raised. Use ``array.tobytes()." +"decode(enc)`` to obtain a unicode string from an array of some other type." +msgstr "" + +#: ../Doc/library/array.rst:252 +msgid "" +"When an array object is printed or converted to a string, it is represented " +"as ``array(typecode, initializer)``. The *initializer* is omitted if the " +"array is empty, otherwise it is a string if the *typecode* is ``'u'``, " +"otherwise it is a list of numbers. The string is guaranteed to be able to " +"be converted back to an array with the same type and value using :func:" +"`eval`, so long as the :func:`array` function has been imported using ``from " +"array import array``. Examples::" +msgstr "" + +#: ../Doc/library/array.rst:269 +msgid "Module :mod:`struct`" +msgstr "" + +#: ../Doc/library/array.rst:269 +msgid "Packing and unpacking of heterogeneous binary data." +msgstr "" + +#: ../Doc/library/array.rst:273 ../Doc/library/struct.rst:384 +msgid "Module :mod:`xdrlib`" +msgstr "" + +#: ../Doc/library/array.rst:272 +msgid "" +"Packing and unpacking of External Data Representation (XDR) data as used in " +"some remote procedure call systems." +msgstr "" + +#: ../Doc/library/array.rst:276 +msgid "`The Numerical Python Documentation `_" +msgstr "" + +#: ../Doc/library/array.rst:276 +msgid "" +"The Numeric Python extension (NumPy) defines another array type; see http://" +"www.numpy.org/ for further information about Numerical Python." +msgstr "" + +#: ../Doc/library/ast.rst:2 +msgid ":mod:`ast` --- Abstract Syntax Trees" +msgstr "" + +#: ../Doc/library/ast.rst:10 +msgid "**Source code:** :source:`Lib/ast.py`" +msgstr "" + +#: ../Doc/library/ast.rst:14 +msgid "" +"The :mod:`ast` module helps Python applications to process trees of the " +"Python abstract syntax grammar. The abstract syntax itself might change " +"with each Python release; this module helps to find out programmatically " +"what the current grammar looks like." +msgstr "" + +#: ../Doc/library/ast.rst:19 +msgid "" +"An abstract syntax tree can be generated by passing :data:`ast." +"PyCF_ONLY_AST` as a flag to the :func:`compile` built-in function, or using " +"the :func:`parse` helper provided in this module. The result will be a tree " +"of objects whose classes all inherit from :class:`ast.AST`. An abstract " +"syntax tree can be compiled into a Python code object using the built-in :" +"func:`compile` function." +msgstr "" + +#: ../Doc/library/ast.rst:27 +msgid "Node classes" +msgstr "" + +#: ../Doc/library/ast.rst:31 +msgid "" +"This is the base of all AST node classes. The actual node classes are " +"derived from the :file:`Parser/Python.asdl` file, which is reproduced :ref:" +"`below `. They are defined in the :mod:`_ast` C module " +"and re-exported in :mod:`ast`." +msgstr "" + +#: ../Doc/library/ast.rst:36 +msgid "" +"There is one class defined for each left-hand side symbol in the abstract " +"grammar (for example, :class:`ast.stmt` or :class:`ast.expr`). In addition, " +"there is one class defined for each constructor on the right-hand side; " +"these classes inherit from the classes for the left-hand side trees. For " +"example, :class:`ast.BinOp` inherits from :class:`ast.expr`. For production " +"rules with alternatives (aka \"sums\"), the left-hand side class is " +"abstract: only instances of specific constructor nodes are ever created." +msgstr "" + +#: ../Doc/library/ast.rst:46 +msgid "" +"Each concrete class has an attribute :attr:`_fields` which gives the names " +"of all child nodes." +msgstr "" + +#: ../Doc/library/ast.rst:49 +msgid "" +"Each instance of a concrete class has one attribute for each child node, of " +"the type as defined in the grammar. For example, :class:`ast.BinOp` " +"instances have an attribute :attr:`left` of type :class:`ast.expr`." +msgstr "" + +#: ../Doc/library/ast.rst:53 +msgid "" +"If these attributes are marked as optional in the grammar (using a question " +"mark), the value might be ``None``. If the attributes can have zero-or-more " +"values (marked with an asterisk), the values are represented as Python " +"lists. All possible attributes must be present and have valid values when " +"compiling an AST with :func:`compile`." +msgstr "" + +#: ../Doc/library/ast.rst:62 +msgid "" +"Instances of :class:`ast.expr` and :class:`ast.stmt` subclasses have :attr:" +"`lineno` and :attr:`col_offset` attributes. The :attr:`lineno` is the line " +"number of source text (1-indexed so the first line is line 1) and the :attr:" +"`col_offset` is the UTF-8 byte offset of the first token that generated the " +"node. The UTF-8 offset is recorded because the parser uses UTF-8 internally." +msgstr "" + +#: ../Doc/library/ast.rst:69 +msgid "" +"The constructor of a class :class:`ast.T` parses its arguments as follows:" +msgstr "" + +#: ../Doc/library/ast.rst:71 +msgid "" +"If there are positional arguments, there must be as many as there are items " +"in :attr:`T._fields`; they will be assigned as attributes of these names." +msgstr "" + +#: ../Doc/library/ast.rst:73 +msgid "" +"If there are keyword arguments, they will set the attributes of the same " +"names to the given values." +msgstr "" + +#: ../Doc/library/ast.rst:76 +msgid "" +"For example, to create and populate an :class:`ast.UnaryOp` node, you could " +"use ::" +msgstr "" + +#: ../Doc/library/ast.rst:88 +msgid "or the more compact ::" +msgstr "" + +#: ../Doc/library/ast.rst:97 +msgid "Abstract Grammar" +msgstr "" + +#: ../Doc/library/ast.rst:99 +msgid "The abstract grammar is currently defined as follows:" +msgstr "" + +#: ../Doc/library/ast.rst:106 +msgid ":mod:`ast` Helpers" +msgstr "" + +#: ../Doc/library/ast.rst:108 +msgid "" +"Apart from the node classes, the :mod:`ast` module defines these utility " +"functions and classes for traversing abstract syntax trees:" +msgstr "" + +#: ../Doc/library/ast.rst:113 +msgid "" +"Parse the source into an AST node. Equivalent to ``compile(source, " +"filename, mode, ast.PyCF_ONLY_AST)``." +msgstr "" + +#: ../Doc/library/ast.rst:119 +msgid "" +"Safely evaluate an expression node or a string containing a Python literal " +"or container display. The string or node provided may only consist of the " +"following Python literal structures: strings, bytes, numbers, tuples, lists, " +"dicts, sets, booleans, and ``None``." +msgstr "" + +#: ../Doc/library/ast.rst:124 +msgid "" +"This can be used for safely evaluating strings containing Python values from " +"untrusted sources without the need to parse the values oneself. It is not " +"capable of evaluating arbitrarily complex expressions, for example involving " +"operators or indexing." +msgstr "" + +#: ../Doc/library/ast.rst:129 +msgid "Now allows bytes and set literals." +msgstr "" + +#: ../Doc/library/ast.rst:135 +msgid "" +"Return the docstring of the given *node* (which must be a :class:" +"`FunctionDef`, :class:`ClassDef` or :class:`Module` node), or ``None`` if it " +"has no docstring. If *clean* is true, clean up the docstring's indentation " +"with :func:`inspect.cleandoc`." +msgstr "" + +#: ../Doc/library/ast.rst:143 +msgid "" +"When you compile a node tree with :func:`compile`, the compiler expects :" +"attr:`lineno` and :attr:`col_offset` attributes for every node that supports " +"them. This is rather tedious to fill in for generated nodes, so this helper " +"adds these attributes recursively where not already set, by setting them to " +"the values of the parent node. It works recursively starting at *node*." +msgstr "" + +#: ../Doc/library/ast.rst:152 +msgid "" +"Increment the line number of each node in the tree starting at *node* by " +"*n*. This is useful to \"move code\" to a different location in a file." +msgstr "" + +#: ../Doc/library/ast.rst:158 +msgid "" +"Copy source location (:attr:`lineno` and :attr:`col_offset`) from *old_node* " +"to *new_node* if possible, and return *new_node*." +msgstr "" + +#: ../Doc/library/ast.rst:164 +msgid "" +"Yield a tuple of ``(fieldname, value)`` for each field in ``node._fields`` " +"that is present on *node*." +msgstr "" + +#: ../Doc/library/ast.rst:170 +msgid "" +"Yield all direct child nodes of *node*, that is, all fields that are nodes " +"and all items of fields that are lists of nodes." +msgstr "" + +#: ../Doc/library/ast.rst:176 +msgid "" +"Recursively yield all descendant nodes in the tree starting at *node* " +"(including *node* itself), in no specified order. This is useful if you " +"only want to modify nodes in place and don't care about the context." +msgstr "" + +#: ../Doc/library/ast.rst:183 +msgid "" +"A node visitor base class that walks the abstract syntax tree and calls a " +"visitor function for every node found. This function may return a value " +"which is forwarded by the :meth:`visit` method." +msgstr "" + +#: ../Doc/library/ast.rst:187 +msgid "" +"This class is meant to be subclassed, with the subclass adding visitor " +"methods." +msgstr "" + +#: ../Doc/library/ast.rst:192 +msgid "" +"Visit a node. The default implementation calls the method called :samp:" +"`self.visit_{classname}` where *classname* is the name of the node class, " +"or :meth:`generic_visit` if that method doesn't exist." +msgstr "" + +#: ../Doc/library/ast.rst:198 +msgid "This visitor calls :meth:`visit` on all children of the node." +msgstr "" + +#: ../Doc/library/ast.rst:200 +msgid "" +"Note that child nodes of nodes that have a custom visitor method won't be " +"visited unless the visitor calls :meth:`generic_visit` or visits them itself." +msgstr "" + +#: ../Doc/library/ast.rst:204 +msgid "" +"Don't use the :class:`NodeVisitor` if you want to apply changes to nodes " +"during traversal. For this a special visitor exists (:class:" +"`NodeTransformer`) that allows modifications." +msgstr "" + +#: ../Doc/library/ast.rst:211 +msgid "" +"A :class:`NodeVisitor` subclass that walks the abstract syntax tree and " +"allows modification of nodes." +msgstr "" + +#: ../Doc/library/ast.rst:214 +msgid "" +"The :class:`NodeTransformer` will walk the AST and use the return value of " +"the visitor methods to replace or remove the old node. If the return value " +"of the visitor method is ``None``, the node will be removed from its " +"location, otherwise it is replaced with the return value. The return value " +"may be the original node in which case no replacement takes place." +msgstr "" + +#: ../Doc/library/ast.rst:220 +msgid "" +"Here is an example transformer that rewrites all occurrences of name lookups " +"(``foo``) to ``data['foo']``::" +msgstr "" + +#: ../Doc/library/ast.rst:232 +msgid "" +"Keep in mind that if the node you're operating on has child nodes you must " +"either transform the child nodes yourself or call the :meth:`generic_visit` " +"method for the node first." +msgstr "" + +#: ../Doc/library/ast.rst:236 +msgid "" +"For nodes that were part of a collection of statements (that applies to all " +"statement nodes), the visitor may also return a list of nodes rather than " +"just a single node." +msgstr "" + +#: ../Doc/library/ast.rst:240 +msgid "Usually you use the transformer like this::" +msgstr "" + +#: ../Doc/library/ast.rst:247 +msgid "" +"Return a formatted dump of the tree in *node*. This is mainly useful for " +"debugging purposes. The returned string will show the names and the values " +"for fields. This makes the code impossible to evaluate, so if evaluation is " +"wanted *annotate_fields* must be set to ``False``. Attributes such as line " +"numbers and column offsets are not dumped by default. If this is wanted, " +"*include_attributes* can be set to ``True``." +msgstr "" + +#: ../Doc/library/ast.rst:256 +msgid "" +"`Green Tree Snakes `_, an external " +"documentation resource, has good details on working with Python ASTs." +msgstr "" + +#: ../Doc/library/asynchat.rst:2 +msgid ":mod:`asynchat` --- Asynchronous socket command/response handler" +msgstr "" + +#: ../Doc/library/asynchat.rst:10 +msgid "**Source code:** :source:`Lib/asynchat.py`" +msgstr "" + +#: ../Doc/library/asynchat.rst:16 ../Doc/library/asyncore.rst:19 +msgid "" +"This module exists for backwards compatibility only. For new code we " +"recommend using :mod:`asyncio`." +msgstr "" + +#: ../Doc/library/asynchat.rst:19 +msgid "" +"This module builds on the :mod:`asyncore` infrastructure, simplifying " +"asynchronous clients and servers and making it easier to handle protocols " +"whose elements are terminated by arbitrary strings, or are of variable " +"length. :mod:`asynchat` defines the abstract class :class:`async_chat` that " +"you subclass, providing implementations of the :meth:`collect_incoming_data` " +"and :meth:`found_terminator` methods. It uses the same asynchronous loop as :" +"mod:`asyncore`, and the two types of channel, :class:`asyncore.dispatcher` " +"and :class:`asynchat.async_chat`, can freely be mixed in the channel map. " +"Typically an :class:`asyncore.dispatcher` server channel generates new :" +"class:`asynchat.async_chat` channel objects as it receives incoming " +"connection requests." +msgstr "" + +#: ../Doc/library/asynchat.rst:34 +msgid "" +"This class is an abstract subclass of :class:`asyncore.dispatcher`. To make " +"practical use of the code you must subclass :class:`async_chat`, providing " +"meaningful :meth:`collect_incoming_data` and :meth:`found_terminator` " +"methods. The :class:`asyncore.dispatcher` methods can be used, although not " +"all make sense in a message/response context." +msgstr "" + +#: ../Doc/library/asynchat.rst:41 +msgid "" +"Like :class:`asyncore.dispatcher`, :class:`async_chat` defines a set of " +"events that are generated by an analysis of socket conditions after a :c:" +"func:`select` call. Once the polling loop has been started the :class:" +"`async_chat` object's methods are called by the event-processing framework " +"with no action on the part of the programmer." +msgstr "" + +#: ../Doc/library/asynchat.rst:47 +msgid "" +"Two class attributes can be modified, to improve performance, or possibly " +"even to conserve memory." +msgstr "" + +#: ../Doc/library/asynchat.rst:53 +msgid "The asynchronous input buffer size (default ``4096``)." +msgstr "" + +#: ../Doc/library/asynchat.rst:58 +msgid "The asynchronous output buffer size (default ``4096``)." +msgstr "" + +#: ../Doc/library/asynchat.rst:60 +msgid "" +"Unlike :class:`asyncore.dispatcher`, :class:`async_chat` allows you to " +"define a :abbr:`FIFO (first-in, first-out)` queue of *producers*. A producer " +"need have only one method, :meth:`more`, which should return data to be " +"transmitted on the channel. The producer indicates exhaustion (*i.e.* that " +"it contains no more data) by having its :meth:`more` method return the empty " +"bytes object. At this point the :class:`async_chat` object removes the " +"producer from the queue and starts using the next producer, if any. When the " +"producer queue is empty the :meth:`handle_write` method does nothing. You " +"use the channel object's :meth:`set_terminator` method to describe how to " +"recognize the end of, or an important breakpoint in, an incoming " +"transmission from the remote endpoint." +msgstr "" + +#: ../Doc/library/asynchat.rst:73 +msgid "" +"To build a functioning :class:`async_chat` subclass your input methods :" +"meth:`collect_incoming_data` and :meth:`found_terminator` must handle the " +"data that the channel receives asynchronously. The methods are described " +"below." +msgstr "" + +#: ../Doc/library/asynchat.rst:81 +msgid "" +"Pushes a ``None`` on to the producer queue. When this producer is popped off " +"the queue it causes the channel to be closed." +msgstr "" + +#: ../Doc/library/asynchat.rst:87 +msgid "" +"Called with *data* holding an arbitrary amount of received data. The " +"default method, which must be overridden, raises a :exc:" +"`NotImplementedError` exception." +msgstr "" + +#: ../Doc/library/asynchat.rst:94 +msgid "" +"In emergencies this method will discard any data held in the input and/or " +"output buffers and the producer queue." +msgstr "" + +#: ../Doc/library/asynchat.rst:100 +msgid "" +"Called when the incoming data stream matches the termination condition set " +"by :meth:`set_terminator`. The default method, which must be overridden, " +"raises a :exc:`NotImplementedError` exception. The buffered input data " +"should be available via an instance attribute." +msgstr "" + +#: ../Doc/library/asynchat.rst:108 +msgid "Returns the current terminator for the channel." +msgstr "" + +#: ../Doc/library/asynchat.rst:113 +msgid "" +"Pushes data on to the channel's queue to ensure its transmission. This is " +"all you need to do to have the channel write the data out to the network, " +"although it is possible to use your own producers in more complex schemes to " +"implement encryption and chunking, for example." +msgstr "" + +#: ../Doc/library/asynchat.rst:121 +msgid "" +"Takes a producer object and adds it to the producer queue associated with " +"the channel. When all currently-pushed producers have been exhausted the " +"channel will consume this producer's data by calling its :meth:`more` method " +"and send the data to the remote endpoint." +msgstr "" + +#: ../Doc/library/asynchat.rst:129 +msgid "" +"Sets the terminating condition to be recognized on the channel. ``term`` " +"may be any of three types of value, corresponding to three different ways to " +"handle incoming protocol data." +msgstr "" + +#: ../Doc/library/asynchat.rst:134 +msgid "term" +msgstr "" + +#: ../Doc/library/asynchat.rst:134 ../Doc/library/asyncio-task.rst:685 +#: ../Doc/library/asyncore.rst:90 ../Doc/library/concurrent.futures.rst:380 +#: ../Doc/library/curses.rst:754 ../Doc/library/inspect.rst:38 +#: ../Doc/library/logging.rst:740 ../Doc/library/logging.rst:1104 +#: ../Doc/library/ossaudiodev.rst:201 ../Doc/library/ossaudiodev.rst:255 +#: ../Doc/library/stdtypes.rst:1886 ../Doc/library/tkinter.ttk.rst:112 +#: ../Doc/library/tkinter.ttk.rst:147 ../Doc/library/tkinter.ttk.rst:173 +#: ../Doc/library/tkinter.ttk.rst:216 ../Doc/library/tkinter.ttk.rst:232 +#: ../Doc/library/tkinter.ttk.rst:319 ../Doc/library/tkinter.ttk.rst:400 +#: ../Doc/library/tkinter.ttk.rst:426 ../Doc/library/tkinter.ttk.rst:590 +#: ../Doc/library/tkinter.ttk.rst:661 ../Doc/library/tkinter.ttk.rst:729 +#: ../Doc/library/tkinter.ttk.rst:780 ../Doc/library/tkinter.ttk.rst:808 +#: ../Doc/library/tkinter.ttk.rst:853 ../Doc/library/turtle.rst:2312 +#: ../Doc/library/warnings.rst:60 +msgid "Description" +msgstr "" + +#: ../Doc/library/asynchat.rst:136 +msgid "*string*" +msgstr "" + +#: ../Doc/library/asynchat.rst:136 +msgid "" +"Will call :meth:`found_terminator` when the string is found in the input " +"stream" +msgstr "" + +#: ../Doc/library/asynchat.rst:139 +msgid "*integer*" +msgstr "" + +#: ../Doc/library/asynchat.rst:139 +msgid "" +"Will call :meth:`found_terminator` when the indicated number of characters " +"have been received" +msgstr "" + +#: ../Doc/library/asynchat.rst:143 ../Doc/library/stdtypes.rst:47 +#: ../Doc/library/xml.dom.rst:993 +msgid "``None``" +msgstr "" + +#: ../Doc/library/asynchat.rst:143 +msgid "The channel continues to collect data forever" +msgstr "" + +#: ../Doc/library/asynchat.rst:147 +msgid "" +"Note that any data following the terminator will be available for reading by " +"the channel after :meth:`found_terminator` is called." +msgstr "" + +#: ../Doc/library/asynchat.rst:154 +msgid "asynchat Example" +msgstr "" + +#: ../Doc/library/asynchat.rst:156 +msgid "" +"The following partial example shows how HTTP requests can be read with :" +"class:`async_chat`. A web server might create an :class:" +"`http_request_handler` object for each incoming client connection. Notice " +"that initially the channel terminator is set to match the blank line at the " +"end of the HTTP headers, and a flag indicates that the headers are being " +"read." +msgstr "" + +#: ../Doc/library/asynchat.rst:163 +msgid "" +"Once the headers have been read, if the request is of type POST (indicating " +"that further data are present in the input stream) then the ``Content-Length:" +"`` header is used to set a numeric terminator to read the right amount of " +"data from the channel." +msgstr "" + +#: ../Doc/library/asynchat.rst:168 +msgid "" +"The :meth:`handle_request` method is called once all relevant input has been " +"marshalled, after setting the channel terminator to ``None`` to ensure that " +"any extraneous data sent by the web client are ignored. ::" +msgstr "" + +#: ../Doc/library/asyncio.rst:2 +msgid ":mod:`asyncio` -- Asynchronous I/O, event loop, coroutines and tasks" +msgstr "" + +#: ../Doc/library/asyncio.rst:9 +msgid "**Source code:** :source:`Lib/asyncio/`" +msgstr "" + +#: ../Doc/library/asyncio.rst:13 +msgid "" +"The asyncio package has been included in the standard library on a :term:" +"`provisional basis `. Backwards incompatible changes " +"(up to and including removal of the module) may occur if deemed necessary by " +"the core developers." +msgstr "" + +#: ../Doc/library/asyncio.rst:20 +msgid "" +"This module provides infrastructure for writing single-threaded concurrent " +"code using coroutines, multiplexing I/O access over sockets and other " +"resources, running network clients and servers, and other related " +"primitives. Here is a more detailed list of the package contents:" +msgstr "" + +#: ../Doc/library/asyncio.rst:25 +msgid "" +"a pluggable :ref:`event loop ` with various system-" +"specific implementations;" +msgstr "" + +#: ../Doc/library/asyncio.rst:28 +msgid "" +":ref:`transport ` and :ref:`protocol ` " +"abstractions (similar to those in `Twisted `_);" +msgstr "" + +#: ../Doc/library/asyncio.rst:31 +msgid "" +"concrete support for TCP, UDP, SSL, subprocess pipes, delayed calls, and " +"others (some may be system-dependent);" +msgstr "" + +#: ../Doc/library/asyncio.rst:34 +msgid "" +"a :class:`Future` class that mimics the one in the :mod:`concurrent.futures` " +"module, but adapted for use with the event loop;" +msgstr "" + +#: ../Doc/library/asyncio.rst:37 +msgid "" +"coroutines and tasks based on ``yield from`` (:PEP:`380`), to help write " +"concurrent code in a sequential fashion;" +msgstr "" + +#: ../Doc/library/asyncio.rst:40 +msgid "cancellation support for :class:`Future`\\s and coroutines;" +msgstr "" + +#: ../Doc/library/asyncio.rst:42 +msgid "" +":ref:`synchronization primitives ` for use between coroutines " +"in a single thread, mimicking those in the :mod:`threading` module;" +msgstr "" + +#: ../Doc/library/asyncio.rst:45 +msgid "" +"an interface for passing work off to a threadpool, for times when you " +"absolutely, positively have to use a library that makes blocking I/O calls." +msgstr "" + +#: ../Doc/library/asyncio.rst:49 +msgid "" +"Asynchronous programming is more complex than classical \"sequential\" " +"programming: see the :ref:`Develop with asyncio ` page which " +"lists common traps and explains how to avoid them. :ref:`Enable the debug " +"mode ` during development to detect common issues." +msgstr "" + +#: ../Doc/library/asyncio.rst:54 +msgid "Table of contents:" +msgstr "" + +#: ../Doc/library/asyncio.rst:71 +msgid "" +"The :mod:`asyncio` module was designed in :PEP:`3156`. For a motivational " +"primer on transports and protocols, see :PEP:`3153`." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:6 +msgid "Develop with asyncio" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:8 +msgid "" +"Asynchronous programming is different than classical \"sequential\" " +"programming. This page lists common traps and explains how to avoid them." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:15 +msgid "Debug mode of asyncio" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:17 +msgid "" +"The implementation of :mod:`asyncio` has been written for performance. In " +"order to ease the development of asynchronous code, you may wish to enable " +"*debug mode*." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:21 +msgid "To enable all debug checks for an application:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:23 +msgid "" +"Enable the asyncio debug mode globally by setting the environment variable :" +"envvar:`PYTHONASYNCIODEBUG` to ``1``, or by calling :meth:`AbstractEventLoop." +"set_debug`." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:25 +msgid "" +"Set the log level of the :ref:`asyncio logger ` to :py:data:" +"`logging.DEBUG`. For example, call ``logging.basicConfig(level=logging." +"DEBUG)`` at startup." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:28 +msgid "" +"Configure the :mod:`warnings` module to display :exc:`ResourceWarning` " +"warnings. For example, use the ``-Wdefault`` command line option of Python " +"to display them." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:32 +msgid "Examples debug checks:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:34 +msgid "" +"Log :ref:`coroutines defined but never \"yielded from\" `" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:36 +msgid "" +":meth:`~AbstractEventLoop.call_soon` and :meth:`~AbstractEventLoop.call_at` " +"methods raise an exception if they are called from the wrong thread." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:38 +msgid "Log the execution time of the selector" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:39 +msgid "" +"Log callbacks taking more than 100 ms to be executed. The :attr:" +"`AbstractEventLoop.slow_callback_duration` attribute is the minimum duration " +"in seconds of \"slow\" callbacks." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:42 +msgid "" +":exc:`ResourceWarning` warnings are emitted when transports and event loops " +"are :ref:`not closed explicitly `." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:47 +msgid "" +"The :meth:`AbstractEventLoop.set_debug` method and the :ref:`asyncio logger " +"`." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:52 +msgid "Cancellation" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:54 +msgid "" +"Cancellation of tasks is not common in classic programming. In asynchronous " +"programming, not only it is something common, but you have to prepare your " +"code to handle it." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:58 +msgid "" +"Futures and tasks can be cancelled explicitly with their :meth:`Future." +"cancel` method. The :func:`wait_for` function cancels the waited task when " +"the timeout occurs. There are many other cases where a task can be cancelled " +"indirectly." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:62 +msgid "" +"Don't call :meth:`~Future.set_result` or :meth:`~Future.set_exception` " +"method of :class:`Future` if the future is cancelled: it would fail with an " +"exception. For example, write::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:69 +msgid "" +"Don't schedule directly a call to the :meth:`~Future.set_result` or the :" +"meth:`~Future.set_exception` method of a future with :meth:" +"`AbstractEventLoop.call_soon`: the future can be cancelled before its method " +"is called." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:74 +msgid "" +"If you wait for a future, you should check early if the future was cancelled " +"to avoid useless operations. Example::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:85 +msgid "The :func:`shield` function can also be used to ignore cancellation." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:91 +msgid "Concurrency and multithreading" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:93 +msgid "" +"An event loop runs in a thread and executes all callbacks and tasks in the " +"same thread. While a task is running in the event loop, no other task is " +"running in the same thread. But when the task uses ``yield from``, the task " +"is suspended and the event loop executes the next task." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:98 +msgid "" +"To schedule a callback from a different thread, the :meth:`AbstractEventLoop." +"call_soon_threadsafe` method should be used. Example::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:103 +msgid "" +"Most asyncio objects are not thread safe. You should only worry if you " +"access objects outside the event loop. For example, to cancel a future, " +"don't call directly its :meth:`Future.cancel` method, but::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:109 +msgid "" +"To handle signals and to execute subprocesses, the event loop must be run in " +"the main thread." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:112 +msgid "" +"To schedule a coroutine object from a different thread, the :func:" +"`run_coroutine_threadsafe` function should be used. It returns a :class:" +"`concurrent.futures.Future` to access the result::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:119 +msgid "" +"The :meth:`AbstractEventLoop.run_in_executor` method can be used with a " +"thread pool executor to execute a callback in different thread to not block " +"the thread of the event loop." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:125 +msgid "" +"The :ref:`Synchronization primitives ` section describes ways " +"to synchronize tasks." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:128 +msgid "" +"The :ref:`Subprocess and threads ` section lists " +"asyncio limitations to run subprocesses from different threads." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:137 +msgid "Handle blocking functions correctly" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:139 +msgid "" +"Blocking functions should not be called directly. For example, if a function " +"blocks for 1 second, other tasks are delayed by 1 second which can have an " +"important impact on reactivity." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:143 +msgid "" +"For networking and subprocesses, the :mod:`asyncio` module provides high-" +"level APIs like :ref:`protocols `." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:146 +msgid "" +"An executor can be used to run a task in a different thread or even in a " +"different process, to not block the thread of the event loop. See the :meth:" +"`AbstractEventLoop.run_in_executor` method." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:152 +msgid "" +"The :ref:`Delayed calls ` section details how the " +"event loop handles time." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:159 ../Doc/library/multiprocessing.rst:2528 +msgid "Logging" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:161 +msgid "" +"The :mod:`asyncio` module logs information with the :mod:`logging` module in " +"the logger ``'asyncio'``." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:164 +msgid "" +"The default log level for the :mod:`asyncio` module is :py:data:`logging." +"INFO`. For those not wanting such verbosity from :mod:`asyncio` the log " +"level can be changed. For example, to change the level to :py:data:`logging." +"WARNING`:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:176 +msgid "Detect coroutine objects never scheduled" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:178 +msgid "" +"When a coroutine function is called and its result is not passed to :func:" +"`ensure_future` or to the :meth:`AbstractEventLoop.create_task` method, the " +"execution of the coroutine object will never be scheduled which is probably " +"a bug. :ref:`Enable the debug mode of asyncio ` to :ref:" +"`log a warning ` to detect it." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:184 +msgid "Example with the bug::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:194 +msgid "Output in debug mode::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:201 +msgid "" +"The fix is to call the :func:`ensure_future` function or the :meth:" +"`AbstractEventLoop.create_task` method with the coroutine object." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:206 +msgid ":ref:`Pending task destroyed `." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:210 +msgid "Detect exceptions never consumed" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:212 +msgid "" +"Python usually calls :func:`sys.displayhook` on unhandled exceptions. If :" +"meth:`Future.set_exception` is called, but the exception is never consumed, :" +"func:`sys.displayhook` is not called. Instead, :ref:`a log is emitted " +"` when the future is deleted by the garbage collector, with " +"the traceback where the exception was raised." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:218 +msgid "Example of unhandled exception::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:231 ../Doc/library/asyncio-task.rst:492 +#: ../Doc/library/tracemalloc.rst:668 +msgid "Output::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:244 +msgid "" +":ref:`Enable the debug mode of asyncio ` to get the " +"traceback where the task was created. Output in debug mode::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:263 +msgid "" +"There are different options to fix this issue. The first option is to chain " +"the coroutine in another coroutine and use classic try/except::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:278 +msgid "" +"Another option is to use the :meth:`AbstractEventLoop.run_until_complete` " +"function::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:289 +msgid "The :meth:`Future.exception` method." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:293 +msgid "Chain coroutines correctly" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:295 +msgid "" +"When a coroutine function calls other coroutine functions and tasks, they " +"should be chained explicitly with ``yield from``. Otherwise, the execution " +"is not guaranteed to be sequential." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:299 +msgid "" +"Example with different bugs using :func:`asyncio.sleep` to simulate slow " +"operations::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:332 +msgid "Expected output:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:341 +msgid "Actual output:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:351 +msgid "" +"The loop stopped before the ``create()`` finished, ``close()`` has been " +"called before ``write()``, whereas coroutine functions were called in this " +"order: ``create()``, ``write()``, ``close()``." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:355 +msgid "To fix the example, tasks must be marked with ``yield from``::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:365 +msgid "Or without ``asyncio.ensure_future()``::" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:379 +msgid "Pending task destroyed" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:381 +msgid "" +"If a pending task is destroyed, the execution of its wrapped :ref:`coroutine " +"` did not complete. It is probably a bug and so a warning is " +"logged." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:384 +msgid "Example of log:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:391 +msgid "" +":ref:`Enable the debug mode of asyncio ` to get the " +"traceback where the task was created. Example of log in debug mode:" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:405 +msgid "" +":ref:`Detect coroutine objects never scheduled `." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:410 +msgid "Close transports and event loops" +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:412 +msgid "" +"When a transport is no more needed, call its ``close()`` method to release " +"resources. Event loops must also be closed explicitly." +msgstr "" + +#: ../Doc/library/asyncio-dev.rst:415 +msgid "" +"If a transport or an event loop is not closed explicitly, a :exc:" +"`ResourceWarning` warning will be emitted in its destructor. By default, :" +"exc:`ResourceWarning` warnings are ignored. The :ref:`Debug mode of asyncio " +"` section explains how to display them." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:6 +msgid "Base Event Loop" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:8 +msgid "" +"The event loop is the central execution device provided by :mod:`asyncio`. " +"It provides multiple facilities, including:" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:11 +msgid "Registering, executing and cancelling delayed calls (timeouts)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:13 +msgid "" +"Creating client and server :ref:`transports ` for various " +"kinds of communication." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:16 +msgid "" +"Launching subprocesses and the associated :ref:`transports ` for communication with an external program." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:19 +msgid "Delegating costly function calls to a pool of threads." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:23 +msgid "" +"This class is an implementation detail. It is a subclass of :class:" +"`AbstractEventLoop` and may be a base class of concrete event loop " +"implementations found in :mod:`asyncio`. It should not be used directly; " +"use :class:`AbstractEventLoop` instead. ``BaseEventLoop`` should not be " +"subclassed by third-party code; the internal interface is not stable." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:32 +msgid "Abstract base class of event loops." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:34 ../Doc/library/asyncio-queue.rst:33 +#: ../Doc/library/asyncio-stream.rst:91 ../Doc/library/asyncio-stream.rst:187 +#: ../Doc/library/asyncio-sync.rst:57 ../Doc/library/asyncio-sync.rst:122 +#: ../Doc/library/asyncio-sync.rst:167 ../Doc/library/asyncio-sync.rst:261 +#: ../Doc/library/asyncio-task.rst:232 ../Doc/library/asyncio-task.rst:401 +msgid "This class is :ref:`not thread safe `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:37 +msgid "Run an event loop" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:41 +msgid "" +"Run until :meth:`stop` is called. If :meth:`stop` is called before :meth:" +"`run_forever()` is called, this polls the I/O selector once with a timeout " +"of zero, runs all callbacks scheduled in response to I/O events (and those " +"that were already scheduled), and then exits. If :meth:`stop` is called " +"while :meth:`run_forever` is running, this will run the current batch of " +"callbacks and then exit. Note that callbacks scheduled by callbacks will " +"not run in that case; they will run the next time :meth:`run_forever` is " +"called." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:54 +msgid "Run until the :class:`Future` is done." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:56 +msgid "" +"If the argument is a :ref:`coroutine object `, it is wrapped by :" +"func:`ensure_future`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:59 +msgid "Return the Future's result, or raise its exception." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:63 +msgid "Returns running status of event loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:67 +msgid "Stop running the event loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:69 +msgid "" +"This causes :meth:`run_forever` to exit at the next suitable opportunity " +"(see there for more details)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:76 +msgid "Returns ``True`` if the event loop was closed." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:82 +msgid "" +"Close the event loop. The loop must not be running. Pending callbacks will " +"be lost." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:85 +msgid "" +"This clears the queues and shuts down the executor, but does not wait for " +"the executor to finish." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:88 +msgid "" +"This is idempotent and irreversible. No other methods should be called after " +"this one." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:94 +msgid "Calls" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:96 +msgid "" +"Most :mod:`asyncio` functions don't accept keywords. If you want to pass " +"keywords to your callback, use :func:`functools.partial`. For example, " +"``loop.call_soon(functools.partial(print, \"Hello\", flush=True))`` will " +"call ``print(\"Hello\", flush=True)``." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:102 +msgid "" +":func:`functools.partial` is better than ``lambda`` functions, because :mod:" +"`asyncio` can inspect :func:`functools.partial` object to display parameters " +"in debug mode, whereas ``lambda`` functions have a poor representation." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:109 +msgid "" +"Arrange for a callback to be called as soon as possible. The callback is " +"called after :meth:`call_soon` returns, when control returns to the event " +"loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:113 +msgid "" +"This operates as a :abbr:`FIFO (first-in, first-out)` queue, callbacks are " +"called in the order in which they are registered. Each callback will be " +"called exactly once." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:117 +msgid "" +"Any positional arguments after the callback will be passed to the callback " +"when it is called." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:120 +#: ../Doc/library/asyncio-eventloop.rst:154 +#: ../Doc/library/asyncio-eventloop.rst:176 +msgid "" +"An instance of :class:`asyncio.Handle` is returned, which can be used to " +"cancel the callback." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:123 +#: ../Doc/library/asyncio-eventloop.rst:165 +#: ../Doc/library/asyncio-eventloop.rst:179 +#: ../Doc/library/asyncio-eventloop.rst:475 +#: ../Doc/library/asyncio-eventloop.rst:487 +#: ../Doc/library/asyncio-eventloop.rst:641 +msgid "" +":ref:`Use functools.partial to pass keywords to the callback `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:128 +msgid "Like :meth:`call_soon`, but thread safe." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:130 ../Doc/library/asyncio-task.rst:616 +msgid "" +"See the :ref:`concurrency and multithreading ` " +"section of the documentation." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:137 +msgid "Delayed calls" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:139 +msgid "" +"The event loop has its own internal clock for computing timeouts. Which " +"clock is used depends on the (platform-specific) event loop implementation; " +"ideally it is a monotonic clock. This will generally be a different clock " +"than :func:`time.time`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:146 +msgid "" +"Timeouts (relative *delay* or absolute *when*) should not exceed one day." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:151 +msgid "" +"Arrange for the *callback* to be called after the given *delay* seconds " +"(either an int or float)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:157 +msgid "" +"*callback* will be called exactly once per call to :meth:`call_later`. If " +"two callbacks are scheduled for exactly the same time, it is undefined which " +"will be called first." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:161 +msgid "" +"The optional positional *args* will be passed to the callback when it is " +"called. If you want the callback to be called with some named arguments, use " +"a closure or :func:`functools.partial`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:170 +msgid "" +"Arrange for the *callback* to be called at the given absolute timestamp " +"*when* (an int or float), using the same time reference as :meth:" +"`AbstractEventLoop.time`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:174 +msgid "This method's behavior is the same as :meth:`call_later`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:184 +msgid "" +"Return the current time, as a :class:`float` value, according to the event " +"loop's internal clock." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:189 +msgid "The :func:`asyncio.sleep` function." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:193 +msgid "Futures" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:197 +msgid "Create an :class:`asyncio.Future` object attached to the loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:199 +msgid "" +"This is a preferred way to create futures in asyncio, as event loop " +"implementations can provide alternative implementations of the Future class " +"(with better performance or instrumentation)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:207 +msgid "Tasks" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:211 ../Doc/library/asyncio-task.rst:537 +msgid "" +"Schedule the execution of a :ref:`coroutine object `: wrap it in " +"a future. Return a :class:`Task` object." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:214 +msgid "" +"Third-party event loops can use their own subclass of :class:`Task` for " +"interoperability. In this case, the result type is a subclass of :class:" +"`Task`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:218 +msgid "" +"This method was added in Python 3.4.2. Use the :func:`async` function to " +"support also older Python versions." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:225 +msgid "" +"Set a task factory that will be used by :meth:`AbstractEventLoop." +"create_task`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:228 +msgid "If *factory* is ``None`` the default task factory will be set." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:230 +msgid "" +"If *factory* is a *callable*, it should have a signature matching ``(loop, " +"coro)``, where *loop* will be a reference to the active event loop, *coro* " +"will be a coroutine object. The callable must return an :class:`asyncio." +"Future` compatible object." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:239 +msgid "Return a task factory, or ``None`` if the default one is in use." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:245 +msgid "Creating connections" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:249 +msgid "" +"Create a streaming transport connection to a given Internet *host* and " +"*port*: socket family :py:data:`~socket.AF_INET` or :py:data:`~socket." +"AF_INET6` depending on *host* (or *family* if specified), socket type :py:" +"data:`~socket.SOCK_STREAM`. *protocol_factory* must be a callable returning " +"a :ref:`protocol ` instance." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:255 +#: ../Doc/library/asyncio-eventloop.rst:329 +#: ../Doc/library/asyncio-eventloop.rst:380 +msgid "" +"This method is a :ref:`coroutine ` which will try to establish " +"the connection in the background. When successful, the coroutine returns a " +"``(transport, protocol)`` pair." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:259 +msgid "The chronological synopsis of the underlying operation is as follows:" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:261 +msgid "" +"The connection is established, and a :ref:`transport ` is " +"created to represent it." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:264 +msgid "" +"*protocol_factory* is called without arguments and must return a :ref:" +"`protocol ` instance." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:267 +msgid "" +"The protocol instance is tied to the transport, and its :meth:" +"`connection_made` method is called." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:270 +msgid "" +"The coroutine returns successfully with the ``(transport, protocol)`` pair." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:273 +msgid "" +"The created transport is an implementation-dependent bidirectional stream." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:276 +msgid "" +"*protocol_factory* can be any kind of callable, not necessarily a class. " +"For example, if you want to use a pre-created protocol instance, you can " +"pass ``lambda: my_protocol``." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:280 +msgid "Options that change how the connection is created:" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:282 +msgid "" +"*ssl*: if given and not false, a SSL/TLS transport is created (by default a " +"plain TCP transport is created). If *ssl* is a :class:`ssl.SSLContext` " +"object, this context is used to create the transport; if *ssl* is :const:" +"`True`, a context with some unspecified default settings is used." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:288 +msgid ":ref:`SSL/TLS security considerations `" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:290 +msgid "" +"*server_hostname*, is only for use together with *ssl*, and sets or " +"overrides the hostname that the target server's certificate will be matched " +"against. By default the value of the *host* argument is used. If *host* is " +"empty, there is no default and you must pass a value for *server_hostname*. " +"If *server_hostname* is an empty string, hostname matching is disabled " +"(which is a serious security risk, allowing for man-in-the-middle-attacks)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:298 +msgid "" +"*family*, *proto*, *flags* are the optional address family, protocol and " +"flags to be passed through to getaddrinfo() for *host* resolution. If given, " +"these should all be integers from the corresponding :mod:`socket` module " +"constants." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:303 +msgid "" +"*sock*, if given, should be an existing, already connected :class:`socket." +"socket` object to be used by the transport. If *sock* is given, none of " +"*host*, *port*, *family*, *proto*, *flags* and *local_addr* should be " +"specified." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:308 +msgid "" +"*local_addr*, if given, is a ``(local_host, local_port)`` tuple used to bind " +"the socket to locally. The *local_host* and *local_port* are looked up " +"using getaddrinfo(), similarly to *host* and *port*." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:314 +#: ../Doc/library/asyncio-eventloop.rst:440 +msgid "On Windows with :class:`ProactorEventLoop`, SSL/TLS is now supported." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:318 +msgid "" +"The :func:`open_connection` function can be used to get a pair of (:class:" +"`StreamReader`, :class:`StreamWriter`) instead of a protocol." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:324 +msgid "" +"Create datagram connection: socket family :py:data:`~socket.AF_INET` or :py:" +"data:`~socket.AF_INET6` depending on *host* (or *family* if specified), " +"socket type :py:data:`~socket.SOCK_DGRAM`. *protocol_factory* must be a " +"callable returning a :ref:`protocol ` instance." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:333 +msgid "Options changing how the connection is created:" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:335 +msgid "" +"*local_addr*, if given, is a ``(local_host, local_port)`` tuple used to bind " +"the socket to locally. The *local_host* and *local_port* are looked up " +"using :meth:`getaddrinfo`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:339 +msgid "" +"*remote_addr*, if given, is a ``(remote_host, remote_port)`` tuple used to " +"connect the socket to a remote address. The *remote_host* and *remote_port* " +"are looked up using :meth:`getaddrinfo`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:343 +msgid "" +"*family*, *proto*, *flags* are the optional address family, protocol and " +"flags to be passed through to :meth:`getaddrinfo` for *host* resolution. If " +"given, these should all be integers from the corresponding :mod:`socket` " +"module constants." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:348 +#: ../Doc/library/asyncio-eventloop.rst:426 +msgid "" +"*reuse_address* tells the kernel to reuse a local socket in TIME_WAIT state, " +"without waiting for its natural timeout to expire. If not specified will " +"automatically be set to True on UNIX." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:353 +msgid "" +"*reuse_port* tells the kernel to allow this endpoint to be bound to the same " +"port as other existing endpoints are bound to, so long as they all set this " +"flag when being created. This option is not supported on Windows and some " +"UNIX's. If the :py:data:`~socket.SO_REUSEPORT` constant is not defined then " +"this capability is unsupported." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:359 +msgid "" +"*allow_broadcast* tells the kernel to allow this endpoint to send messages " +"to the broadcast address." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:362 +msgid "" +"*sock* can optionally be specified in order to use a preexisting, already " +"connected, :class:`socket.socket` object to be used by the transport. If " +"specified, *local_addr* and *remote_addr* should be omitted (must be :const:" +"`None`)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:367 +msgid "" +"On Windows with :class:`ProactorEventLoop`, this method is not supported." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:369 +msgid "" +"See :ref:`UDP echo client protocol ` and :" +"ref:`UDP echo server protocol ` examples." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:375 +msgid "" +"Create UNIX connection: socket family :py:data:`~socket.AF_UNIX`, socket " +"type :py:data:`~socket.SOCK_STREAM`. The :py:data:`~socket.AF_UNIX` socket " +"family is used to communicate between processes on the same machine " +"efficiently." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:384 +msgid "" +"See the :meth:`AbstractEventLoop.create_connection` method for parameters." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:386 +#: ../Doc/library/asyncio-eventloop.rst:459 +#: ../Doc/library/asyncio-stream.rst:72 ../Doc/library/asyncio-stream.rst:83 +msgid "Availability: UNIX." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:390 +msgid "Creating listening connections" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:394 +msgid "" +"Create a TCP server (socket type :data:`~socket.SOCK_STREAM`) bound to " +"*host* and *port*." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:397 +msgid "" +"Return a :class:`Server` object, its :attr:`~Server.sockets` attribute " +"contains created sockets. Use the :meth:`Server.close` method to stop the " +"server: close listening sockets." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:401 +msgid "Parameters:" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:403 +msgid "" +"The *host* parameter can be a string, in that case the TCP server is bound " +"to *host* and *port*. The *host* parameter can also be a sequence of strings " +"and in that case the TCP server is bound to all hosts of the sequence. If " +"*host* is an empty string or ``None``, all interfaces are assumed and a list " +"of multiple sockets will be returned (most likely one for IPv4 and another " +"one for IPv6)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:410 +msgid "" +"*family* can be set to either :data:`socket.AF_INET` or :data:`~socket." +"AF_INET6` to force the socket to use IPv4 or IPv6. If not set it will be " +"determined from host (defaults to :data:`socket.AF_UNSPEC`)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:414 +msgid "*flags* is a bitmask for :meth:`getaddrinfo`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:416 +msgid "" +"*sock* can optionally be specified in order to use a preexisting socket " +"object. If specified, *host* and *port* should be omitted (must be :const:" +"`None`)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:420 +msgid "" +"*backlog* is the maximum number of queued connections passed to :meth:" +"`~socket.socket.listen` (defaults to 100)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:423 +msgid "" +"*ssl* can be set to an :class:`~ssl.SSLContext` to enable SSL over the " +"accepted connections." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:431 +msgid "" +"*reuse_port* tells the kernel to allow this endpoint to be bound to the same " +"port as other existing endpoints are bound to, so long as they all set this " +"flag when being created. This option is not supported on Windows." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:436 +#: ../Doc/library/asyncio-eventloop.rst:457 +#: ../Doc/library/asyncio-eventloop.rst:514 +#: ../Doc/library/asyncio-eventloop.rst:530 +#: ../Doc/library/asyncio-eventloop.rst:540 +#: ../Doc/library/asyncio-eventloop.rst:568 +#: ../Doc/library/asyncio-eventloop.rst:607 +#: ../Doc/library/asyncio-eventloop.rst:621 +#: ../Doc/library/asyncio-eventloop.rst:672 +#: ../Doc/library/asyncio-eventloop.rst:784 ../Doc/library/asyncio-queue.rst:56 +#: ../Doc/library/asyncio-queue.rst:79 ../Doc/library/asyncio-queue.rst:88 +#: ../Doc/library/asyncio-stream.rst:122 ../Doc/library/asyncio-stream.rst:134 +#: ../Doc/library/asyncio-stream.rst:143 ../Doc/library/asyncio-stream.rst:221 +#: ../Doc/library/asyncio-subprocess.rst:115 +#: ../Doc/library/asyncio-subprocess.rst:142 +#: ../Doc/library/asyncio-subprocess.rst:204 +#: ../Doc/library/asyncio-subprocess.rst:232 ../Doc/library/asyncio-sync.rst:95 +#: ../Doc/library/asyncio-sync.rst:148 ../Doc/library/asyncio-sync.rst:176 +#: ../Doc/library/asyncio-sync.rst:228 ../Doc/library/asyncio-sync.rst:237 +#: ../Doc/library/asyncio-sync.rst:272 +msgid "This method is a :ref:`coroutine `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:444 +msgid "" +"The function :func:`start_server` creates a (:class:`StreamReader`, :class:" +"`StreamWriter`) pair and calls back a function with this pair." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:449 +msgid "The *host* parameter can now be a sequence of strings." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:454 +msgid "" +"Similar to :meth:`AbstractEventLoop.create_server`, but specific to the " +"socket family :py:data:`~socket.AF_UNIX`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:463 +msgid "Watch file descriptors" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:465 +msgid "" +"On Windows with :class:`SelectorEventLoop`, only socket handles are " +"supported (ex: pipe file descriptors are not supported)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:468 +msgid "" +"On Windows with :class:`ProactorEventLoop`, these methods are not supported." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:472 +msgid "" +"Start watching the file descriptor for read availability and then call the " +"*callback* with specified arguments." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:480 +msgid "Stop watching the file descriptor for read availability." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:484 +msgid "" +"Start watching the file descriptor for write availability and then call the " +"*callback* with specified arguments." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:492 +msgid "Stop watching the file descriptor for write availability." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:494 +#: ../Doc/library/asyncio-protocol.rst:709 +#: ../Doc/library/asyncio-stream.rst:463 +msgid "" +"The :ref:`watch a file descriptor for read events ` example uses the low-level :meth:`AbstractEventLoop.add_reader` " +"method to register the file descriptor of a socket." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:500 +msgid "Low-level socket operations" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:504 +msgid "" +"Receive data from the socket. Modeled after blocking :meth:`socket.socket." +"recv` method." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:507 +msgid "" +"The return value is a bytes object representing the data received. The " +"maximum amount of data to be received at once is specified by *nbytes*." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:511 +#: ../Doc/library/asyncio-eventloop.rst:527 +#: ../Doc/library/asyncio-eventloop.rst:537 +msgid "" +"With :class:`SelectorEventLoop` event loop, the socket *sock* must be non-" +"blocking." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:518 +msgid "" +"Send data to the socket. Modeled after blocking :meth:`socket.socket." +"sendall` method." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:521 +msgid "" +"The socket must be connected to a remote socket. This method continues to " +"send data from *data* until either all data has been sent or an error " +"occurs. ``None`` is returned on success. On error, an exception is raised, " +"and there is no way to determine how much data, if any, was successfully " +"processed by the receiving end of the connection." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:534 +msgid "" +"Connect to a remote socket at *address*. Modeled after blocking :meth:" +"`socket.socket.connect` method." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:542 +msgid "" +"``address`` no longer needs to be resolved. ``sock_connect`` will try to " +"check if the *address* is already resolved by calling :func:`socket." +"inet_pton`. If not, :meth:`AbstractEventLoop.getaddrinfo` will be used to " +"resolve the *address*." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:551 +msgid "" +":meth:`AbstractEventLoop.create_connection` and :func:`asyncio." +"open_connection() `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:557 +msgid "" +"Accept a connection. Modeled after blocking :meth:`socket.socket.accept`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:560 +msgid "" +"The socket must be bound to an address and listening for connections. The " +"return value is a pair ``(conn, address)`` where *conn* is a *new* socket " +"object usable to send and receive data on the connection, and *address* is " +"the address bound to the socket on the other end of the connection." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:566 +msgid "The socket *sock* must be non-blocking." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:572 +msgid ":meth:`AbstractEventLoop.create_server` and :func:`start_server`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:576 +msgid "Resolve host name" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:580 +msgid "" +"This method is a :ref:`coroutine `, similar to :meth:`socket." +"getaddrinfo` function but non-blocking." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:585 +msgid "" +"This method is a :ref:`coroutine `, similar to :meth:`socket." +"getnameinfo` function but non-blocking." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:590 +msgid "Connect pipes" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:592 +msgid "" +"On Windows with :class:`SelectorEventLoop`, these methods are not supported. " +"Use :class:`ProactorEventLoop` to support pipes on Windows." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:597 +msgid "Register read pipe in eventloop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:599 +msgid "" +"*protocol_factory* should instantiate object with :class:`Protocol` " +"interface. *pipe* is a :term:`file-like object `. Return pair " +"``(transport, protocol)``, where *transport* supports the :class:" +"`ReadTransport` interface." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:604 +#: ../Doc/library/asyncio-eventloop.rst:618 +msgid "" +"With :class:`SelectorEventLoop` event loop, the *pipe* is set to non-" +"blocking mode." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:611 +msgid "Register write pipe in eventloop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:613 +msgid "" +"*protocol_factory* should instantiate object with :class:`BaseProtocol` " +"interface. *pipe* is :term:`file-like object `. Return pair " +"``(transport, protocol)``, where *transport* supports :class:" +"`WriteTransport` interface." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:625 +msgid "" +"The :meth:`AbstractEventLoop.subprocess_exec` and :meth:`AbstractEventLoop." +"subprocess_shell` methods." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:630 +msgid "UNIX signals" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:632 +msgid "Availability: UNIX only." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:636 +msgid "Add a handler for a signal." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:638 +msgid "" +"Raise :exc:`ValueError` if the signal number is invalid or uncatchable. " +"Raise :exc:`RuntimeError` if there is a problem setting up the handler." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:646 +msgid "Remove a handler for a signal." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:648 +msgid "Return ``True`` if a signal handler was removed, ``False`` if not." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:652 +msgid "The :mod:`signal` module." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:656 +msgid "Executor" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:658 +msgid "" +"Call a function in an :class:`~concurrent.futures.Executor` (pool of threads " +"or pool of processes). By default, an event loop uses a thread pool executor " +"(:class:`~concurrent.futures.ThreadPoolExecutor`)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:664 +msgid "Arrange for a *func* to be called in the specified executor." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:666 +msgid "" +"The *executor* argument should be an :class:`~concurrent.futures.Executor` " +"instance. The default executor is used if *executor* is ``None``." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:669 +msgid "" +":ref:`Use functools.partial to pass keywords to the *func* `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:676 +msgid "Set the default executor used by :meth:`run_in_executor`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:680 +msgid "Error Handling API" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:682 +msgid "Allows customizing how exceptions are handled in the event loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:686 +msgid "Set *handler* as the new event loop exception handler." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:688 +msgid "If *handler* is ``None``, the default exception handler will be set." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:691 +msgid "" +"If *handler* is a callable object, it should have a matching signature to " +"``(loop, context)``, where ``loop`` will be a reference to the active event " +"loop, ``context`` will be a ``dict`` object (see :meth:" +"`call_exception_handler` documentation for details about context)." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:699 +msgid "Return the exception handler, or ``None`` if the default one is in use." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:706 +msgid "Default exception handler." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:708 +msgid "" +"This is called when an exception occurs and no exception handler is set, and " +"can be called by a custom exception handler that wants to defer to the " +"default behavior." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:712 +msgid "" +"*context* parameter has the same meaning as in :meth:" +"`call_exception_handler`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:717 +msgid "Call the current event loop exception handler." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:719 +msgid "" +"*context* is a ``dict`` object containing the following keys (new keys may " +"be introduced later):" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:722 +msgid "'message': Error message;" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:723 +msgid "'exception' (optional): Exception object;" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:724 +msgid "'future' (optional): :class:`asyncio.Future` instance;" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:725 +msgid "'handle' (optional): :class:`asyncio.Handle` instance;" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:726 +msgid "'protocol' (optional): :ref:`Protocol ` instance;" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:727 +msgid "'transport' (optional): :ref:`Transport ` instance;" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:728 +msgid "'socket' (optional): :class:`socket.socket` instance." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:732 +msgid "" +"Note: this method should not be overloaded in subclassed event loops. For " +"any custom exception handling, use :meth:`set_exception_handler()` method." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:737 +msgid "Debug mode" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:741 +msgid "Get the debug mode (:class:`bool`) of the event loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:743 +msgid "" +"The default value is ``True`` if the environment variable :envvar:" +"`PYTHONASYNCIODEBUG` is set to a non-empty string, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:751 +msgid "Set the debug mode of the event loop." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:757 +msgid "The :ref:`debug mode of asyncio `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:760 +msgid "Server" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:764 +msgid "Server listening on sockets." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:766 +msgid "" +"Object created by the :meth:`AbstractEventLoop.create_server` method and " +"the :func:`start_server` function. Don't instantiate the class directly." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:771 +msgid "" +"Stop serving: close listening sockets and set the :attr:`sockets` attribute " +"to ``None``." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:774 +msgid "" +"The sockets that represent existing incoming client connections are left " +"open." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:777 +msgid "" +"The server is closed asynchronously, use the :meth:`wait_closed` coroutine " +"to wait until the server is closed." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:782 +msgid "Wait until the :meth:`close` method completes." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:788 +msgid "" +"List of :class:`socket.socket` objects the server is listening to, or " +"``None`` if the server is closed." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:793 +msgid "Handle" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:797 +msgid "" +"A callback wrapper object returned by :func:`AbstractEventLoop.call_soon`, :" +"func:`AbstractEventLoop.call_soon_threadsafe`, :func:`AbstractEventLoop." +"call_later`, and :func:`AbstractEventLoop.call_at`." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:803 +msgid "" +"Cancel the call. If the callback is already canceled or executed, this " +"method has no effect." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:808 +msgid "Event loop examples" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:813 +msgid "Hello World with call_soon()" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:815 +msgid "" +"Example using the :meth:`AbstractEventLoop.call_soon` method to schedule a " +"callback. The callback displays ``\"Hello World\"`` and then stops the event " +"loop::" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:836 +msgid "" +"The :ref:`Hello World coroutine ` example " +"uses a :ref:`coroutine `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:843 +msgid "Display the current date with call_later()" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:845 +msgid "" +"Example of callback displaying the current date every second. The callback " +"uses the :meth:`AbstractEventLoop.call_later` method to reschedule itself " +"during 5 seconds, and then stops the event loop::" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:871 +msgid "" +"The :ref:`coroutine displaying the current date ` " +"example uses a :ref:`coroutine `." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:879 +msgid "Watch a file descriptor for read events" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:881 +msgid "" +"Wait until a file descriptor received some data using the :meth:" +"`AbstractEventLoop.add_reader` method and then close the event loop::" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:918 +#: ../Doc/library/asyncio-stream.rst:459 +msgid "" +"The :ref:`register an open socket to wait for data using a protocol ` example uses a low-level protocol created by the :meth:" +"`AbstractEventLoop.create_connection` method." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:922 +#: ../Doc/library/asyncio-protocol.rst:714 +msgid "" +"The :ref:`register an open socket to wait for data using streams ` example uses high-level streams created by the :" +"func:`open_connection` function in a coroutine." +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:928 +msgid "Set signal handlers for SIGINT and SIGTERM" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:930 +msgid "" +"Register handlers for signals :py:data:`SIGINT` and :py:data:`SIGTERM` using " +"the :meth:`AbstractEventLoop.add_signal_handler` method::" +msgstr "" + +#: ../Doc/library/asyncio-eventloop.rst:954 +msgid "This example only works on UNIX." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:4 +msgid "Event loops" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:7 +msgid "Event loop functions" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:9 +msgid "" +"The following functions are convenient shortcuts to accessing the methods of " +"the global policy. Note that this provides access to the default policy, " +"unless an alternative policy was set by calling :func:" +"`set_event_loop_policy` earlier in the execution of the process." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:16 +msgid "Equivalent to calling ``get_event_loop_policy().get_event_loop()``." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:20 +msgid "Equivalent to calling ``get_event_loop_policy().set_event_loop(loop)``." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:24 +msgid "Equivalent to calling ``get_event_loop_policy().new_event_loop()``." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:30 +msgid "Available event loops" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:32 +msgid "" +"asyncio currently provides two implementations of event loops: :class:" +"`SelectorEventLoop` and :class:`ProactorEventLoop`." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:37 +msgid "" +"Event loop based on the :mod:`selectors` module. Subclass of :class:" +"`AbstractEventLoop`." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:40 +msgid "Use the most efficient selector available on the platform." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:42 +msgid "" +"On Windows, only sockets are supported (ex: pipes are not supported): see " +"the `MSDN documentation of select `_." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:48 +msgid "" +"Proactor event loop for Windows using \"I/O Completion Ports\" aka IOCP. " +"Subclass of :class:`AbstractEventLoop`." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:51 ../Doc/library/os.rst:1325 +#: ../Doc/library/os.rst:1331 ../Doc/library/os.rst:3365 +#: ../Doc/library/os.rst:3394 ../Doc/library/signal.rst:109 +#: ../Doc/library/signal.rst:119 ../Doc/library/socket.rst:511 +#: ../Doc/library/socket.rst:1423 ../Doc/library/ssl.rst:498 +#: ../Doc/library/ssl.rst:513 ../Doc/library/sys.rst:588 +msgid "Availability: Windows." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:55 +msgid "" +"`MSDN documentation on I/O Completion Ports `_." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:58 +msgid "Example to use a :class:`ProactorEventLoop` on Windows::" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:69 +msgid "Platform support" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:71 +msgid "" +"The :mod:`asyncio` module has been designed to be portable, but each " +"platform still has subtle differences and may not support all :mod:`asyncio` " +"features." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:75 ../Doc/library/socket.rst:1026 +#: ../Doc/library/sys.rst:902 ../Doc/using/venv-create.inc:102 +msgid "Windows" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:77 +msgid "Common limits of Windows event loops:" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:79 +msgid "" +":meth:`~AbstractEventLoop.create_unix_connection` and :meth:" +"`~AbstractEventLoop.create_unix_server` are not supported: the socket " +"family :data:`socket.AF_UNIX` is specific to UNIX" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:82 +msgid "" +":meth:`~AbstractEventLoop.add_signal_handler` and :meth:`~AbstractEventLoop." +"remove_signal_handler` are not supported" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:84 +msgid "" +":meth:`EventLoopPolicy.set_child_watcher` is not supported. :class:" +"`ProactorEventLoop` supports subprocesses. It has only one implementation to " +"watch child processes, there is no need to configure it." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:88 +msgid ":class:`SelectorEventLoop` specific limits:" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:90 +msgid "" +":class:`~selectors.SelectSelector` is used which only supports sockets and " +"is limited to 512 sockets." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:92 +msgid "" +":meth:`~AbstractEventLoop.add_reader` and :meth:`~AbstractEventLoop." +"add_writer` only accept file descriptors of sockets" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:94 +msgid "" +"Pipes are not supported (ex: :meth:`~AbstractEventLoop.connect_read_pipe`, :" +"meth:`~AbstractEventLoop.connect_write_pipe`)" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:97 +msgid "" +":ref:`Subprocesses ` are not supported (ex: :meth:" +"`~AbstractEventLoop.subprocess_exec`, :meth:`~AbstractEventLoop." +"subprocess_shell`)" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:101 +msgid ":class:`ProactorEventLoop` specific limits:" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:103 +msgid "" +":meth:`~AbstractEventLoop.create_datagram_endpoint` (UDP) is not supported" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:104 +msgid "" +":meth:`~AbstractEventLoop.add_reader` and :meth:`~AbstractEventLoop." +"add_writer` are not supported" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:107 +msgid "" +"The resolution of the monotonic clock on Windows is usually around 15.6 " +"msec. The best resolution is 0.5 msec. The resolution depends on the " +"hardware (availability of `HPET `_) and on the Windows configuration. See :ref:" +"`asyncio delayed calls `." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:115 +msgid ":class:`ProactorEventLoop` now supports SSL." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:119 ../Doc/library/sys.rst:904 +msgid "Mac OS X" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:121 +msgid "" +"Character devices like PTY are only well supported since Mavericks (Mac OS " +"10.9). They are not supported at all on Mac OS 10.5 and older." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:124 +msgid "" +"On Mac OS 10.6, 10.7 and 10.8, the default event loop is :class:" +"`SelectorEventLoop` which uses :class:`selectors.KqueueSelector`. :class:" +"`selectors.KqueueSelector` does not support character devices on these " +"versions. The :class:`SelectorEventLoop` can be used with :class:" +"`~selectors.SelectSelector` or :class:`~selectors.PollSelector` to support " +"character devices on these versions of Mac OS X. Example::" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:140 +msgid "Event loop policies and the default policy" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:142 +msgid "" +"Event loop management is abstracted with a *policy* pattern, to provide " +"maximal flexibility for custom platforms and frameworks. Throughout the " +"execution of a process, a single global policy object manages the event " +"loops available to the process based on the calling context. A policy is an " +"object implementing the :class:`AbstractEventLoopPolicy` interface." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:148 +msgid "" +"For most users of :mod:`asyncio`, policies never have to be dealt with " +"explicitly, since the default global policy is sufficient." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:151 +msgid "" +"The default policy defines context as the current thread, and manages an " +"event loop per thread that interacts with :mod:`asyncio`. The module-level " +"functions :func:`get_event_loop` and :func:`set_event_loop` provide " +"convenient access to event loops managed by the default policy." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:158 +msgid "Event loop policy interface" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:160 +msgid "An event loop policy must implement the following interface:" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:164 +msgid "Event loop policy." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:168 +msgid "Get the event loop for the current context." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:170 +msgid "" +"Returns an event loop object implementing the :class:`AbstractEventLoop` " +"interface." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:173 +msgid "" +"Raises an exception in case no event loop has been set for the current " +"context and the current policy does not specify to create one. It must never " +"return ``None``." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:179 +msgid "Set the event loop for the current context to *loop*." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:183 +msgid "" +"Create and return a new event loop object according to this policy's rules." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:186 +msgid "" +"If there's need to set this loop as the event loop for the current context, :" +"meth:`set_event_loop` must be called explicitly." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:191 +msgid "Access to the global loop policy" +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:195 +msgid "Get the current event loop policy." +msgstr "" + +#: ../Doc/library/asyncio-eventloops.rst:199 +msgid "" +"Set the current event loop policy. If *policy* is ``None``, the default " +"policy is restored." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:5 +msgid "Transports and protocols (callback based API)" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:10 +msgid "Transports" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:12 +msgid "" +"Transports are classes provided by :mod:`asyncio` in order to abstract " +"various kinds of communication channels. You generally won't instantiate a " +"transport yourself; instead, you will call an :class:`AbstractEventLoop` " +"method which will create the transport and try to initiate the underlying " +"communication channel, calling you back when it succeeds." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:18 +msgid "" +"Once the communication channel is established, a transport is always paired " +"with a :ref:`protocol ` instance. The protocol can then " +"call the transport's methods for various purposes." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:22 +msgid "" +":mod:`asyncio` currently implements transports for TCP, UDP, SSL, and " +"subprocess pipes. The methods available on a transport depend on the " +"transport's kind." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:26 +msgid "" +"The transport classes are :ref:`not thread safe `." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:30 +msgid "BaseTransport" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:34 +msgid "Base class for transports." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:38 +msgid "" +"Close the transport. If the transport has a buffer for outgoing data, " +"buffered data will be flushed asynchronously. No more data will be " +"received. After all buffered data is flushed, the protocol's :meth:" +"`connection_lost` method will be called with :const:`None` as its argument." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:46 +msgid "Return ``True`` if the transport is closing or is closed." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:52 +msgid "" +"Return optional transport information. *name* is a string representing the " +"piece of transport-specific information to get, *default* is the value to " +"return if the information doesn't exist." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:56 +msgid "" +"This method allows transport implementations to easily expose channel-" +"specific information." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:59 +msgid "socket:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:61 +msgid "" +"``'peername'``: the remote address to which the socket is connected, result " +"of :meth:`socket.socket.getpeername` (``None`` on error)" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:63 +msgid "``'socket'``: :class:`socket.socket` instance" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:64 +msgid "" +"``'sockname'``: the socket's own address, result of :meth:`socket.socket." +"getsockname`" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:67 +msgid "SSL socket:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:69 +msgid "" +"``'compression'``: the compression algorithm being used as a string, or " +"``None`` if the connection isn't compressed; result of :meth:`ssl.SSLSocket." +"compression`" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:72 +msgid "" +"``'cipher'``: a three-value tuple containing the name of the cipher being " +"used, the version of the SSL protocol that defines its use, and the number " +"of secret bits being used; result of :meth:`ssl.SSLSocket.cipher`" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:76 +msgid "" +"``'peercert'``: peer certificate; result of :meth:`ssl.SSLSocket.getpeercert`" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:78 +msgid "``'sslcontext'``: :class:`ssl.SSLContext` instance" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:79 +msgid "" +"``'ssl_object'``: :class:`ssl.SSLObject` or :class:`ssl.SSLSocket` instance" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:82 +msgid "pipe:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:84 +msgid "``'pipe'``: pipe object" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:86 +msgid "subprocess:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:88 +msgid "``'subprocess'``: :class:`subprocess.Popen` instance" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:90 +msgid "``'ssl_object'`` info was added to SSL sockets." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:95 +msgid "ReadTransport" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:99 +msgid "Interface for read-only transports." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:103 +msgid "" +"Pause the receiving end of the transport. No data will be passed to the " +"protocol's :meth:`data_received` method until :meth:`resume_reading` is " +"called." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:109 +msgid "" +"Resume the receiving end. The protocol's :meth:`data_received` method will " +"be called once again if some data is available for reading." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:114 +msgid "WriteTransport" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:118 +msgid "Interface for write-only transports." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:122 +#: ../Doc/library/asyncio-protocol.rst:204 +msgid "" +"Close the transport immediately, without waiting for pending operations to " +"complete. Buffered data will be lost. No more data will be received. The " +"protocol's :meth:`connection_lost` method will eventually be called with :" +"const:`None` as its argument." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:129 +msgid "" +"Return :const:`True` if the transport supports :meth:`write_eof`, :const:" +"`False` if not." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:134 +msgid "Return the current size of the output buffer used by the transport." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:138 +msgid "" +"Get the *high*- and *low*-water limits for write flow control. Return a " +"tuple ``(low, high)`` where *low* and *high* are positive number of bytes." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:142 +msgid "Use :meth:`set_write_buffer_limits` to set the limits." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:148 +msgid "Set the *high*- and *low*-water limits for write flow control." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:150 +msgid "" +"These two values control when call the protocol's :meth:`pause_writing` and :" +"meth:`resume_writing` methods are called. If specified, the low-water limit " +"must be less than or equal to the high-water limit. Neither *high* nor " +"*low* can be negative." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:155 +msgid "" +"The defaults are implementation-specific. If only the high-water limit is " +"given, the low-water limit defaults to an implementation-specific value less " +"than or equal to the high-water limit. Setting *high* to zero forces *low* " +"to zero as well, and causes :meth:`pause_writing` to be called whenever the " +"buffer becomes non-empty. Setting *low* to zero causes :meth:" +"`resume_writing` to be called only once the buffer is empty. Use of zero for " +"either limit is generally sub-optimal as it reduces opportunities for doing " +"I/O and computation concurrently." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:166 +msgid "Use :meth:`get_write_buffer_limits` to get the limits." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:170 +msgid "Write some *data* bytes to the transport." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:172 +#: ../Doc/library/asyncio-protocol.rst:199 +msgid "" +"This method does not block; it buffers the data and arranges for it to be " +"sent out asynchronously." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:177 +msgid "" +"Write a list (or any iterable) of data bytes to the transport. This is " +"functionally equivalent to calling :meth:`write` on each element yielded by " +"the iterable, but may be implemented more efficiently." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:183 +msgid "" +"Close the write end of the transport after flushing buffered data. Data may " +"still be received." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:186 +msgid "" +"This method can raise :exc:`NotImplementedError` if the transport (e.g. SSL) " +"doesn't support half-closes." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:191 +msgid "DatagramTransport" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:195 +msgid "" +"Send the *data* bytes to the remote peer given by *addr* (a transport-" +"dependent target address). If *addr* is :const:`None`, the data is sent to " +"the target address given on transport creation." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:211 +msgid "BaseSubprocessTransport" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:217 +msgid "Return the subprocess process id as an integer." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:221 +msgid "" +"Return the transport for the communication pipe corresponding to the integer " +"file descriptor *fd*:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:224 +msgid "" +"``0``: readable streaming transport of the standard input (*stdin*), or :" +"const:`None` if the subprocess was not created with ``stdin=PIPE``" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:226 +msgid "" +"``1``: writable streaming transport of the standard output (*stdout*), or :" +"const:`None` if the subprocess was not created with ``stdout=PIPE``" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:228 +msgid "" +"``2``: writable streaming transport of the standard error (*stderr*), or :" +"const:`None` if the subprocess was not created with ``stderr=PIPE``" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:230 +msgid "other *fd*: :const:`None`" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:234 +msgid "" +"Return the subprocess returncode as an integer or :const:`None` if it hasn't " +"returned, similarly to the :attr:`subprocess.Popen.returncode` attribute." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:240 +msgid "Kill the subprocess, as in :meth:`subprocess.Popen.kill`." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:242 +msgid "" +"On POSIX systems, the function sends SIGKILL to the subprocess. On Windows, " +"this method is an alias for :meth:`terminate`." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:247 +msgid "" +"Send the *signal* number to the subprocess, as in :meth:`subprocess.Popen." +"send_signal`." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:252 +msgid "" +"Ask the subprocess to stop, as in :meth:`subprocess.Popen.terminate`. This " +"method is an alias for the :meth:`close` method." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:255 +msgid "" +"On POSIX systems, this method sends SIGTERM to the subprocess. On Windows, " +"the Windows API function TerminateProcess() is called to stop the subprocess." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:261 +msgid "" +"Ask the subprocess to stop by calling the :meth:`terminate` method if the " +"subprocess hasn't returned yet, and close transports of all pipes (*stdin*, " +"*stdout* and *stderr*)." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:269 +msgid "Protocols" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:271 +msgid "" +":mod:`asyncio` provides base classes that you can subclass to implement your " +"network protocols. Those classes are used in conjunction with :ref:" +"`transports ` (see below): the protocol parses incoming " +"data and asks for the writing of outgoing data, while the transport is " +"responsible for the actual I/O and buffering." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:277 +msgid "" +"When subclassing a protocol class, it is recommended you override certain " +"methods. Those methods are callbacks: they will be called by the transport " +"on certain events (for example when some data is received); you shouldn't " +"call them yourself, unless you are implementing a transport." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:283 +msgid "" +"All callbacks have default implementations, which are empty. Therefore, you " +"only need to implement the callbacks for the events in which you are " +"interested." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:289 +msgid "Protocol classes" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:293 +msgid "" +"The base class for implementing streaming protocols (for use with e.g. TCP " +"and SSL transports)." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:298 +msgid "" +"The base class for implementing datagram protocols (for use with e.g. UDP " +"transports)." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:303 +msgid "" +"The base class for implementing protocols communicating with child processes " +"(through a set of unidirectional pipes)." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:308 +msgid "Connection callbacks" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:310 +#: ../Doc/library/asyncio-protocol.rst:422 +msgid "" +"These callbacks may be called on :class:`Protocol`, :class:" +"`DatagramProtocol` and :class:`SubprocessProtocol` instances:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:315 +msgid "Called when a connection is made." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:317 +msgid "" +"The *transport* argument is the transport representing the connection. You " +"are responsible for storing it somewhere (e.g. as an attribute) if you need " +"to." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:323 +msgid "Called when the connection is lost or closed." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:325 +msgid "" +"The argument is either an exception object or :const:`None`. The latter " +"means a regular EOF is received, or the connection was aborted or closed by " +"this side of the connection." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:329 +msgid "" +":meth:`~BaseProtocol.connection_made` and :meth:`~BaseProtocol." +"connection_lost` are called exactly once per successful connection. All " +"other callbacks will be called between those two methods, which allows for " +"easier resource management in your protocol implementation." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:334 +msgid "" +"The following callbacks may be called only on :class:`SubprocessProtocol` " +"instances:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:339 +msgid "" +"Called when the child process writes data into its stdout or stderr pipe. " +"*fd* is the integer file descriptor of the pipe. *data* is a non-empty " +"bytes object containing the data." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:345 +msgid "" +"Called when one of the pipes communicating with the child process is " +"closed. *fd* is the integer file descriptor that was closed." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:350 +msgid "Called when the child process has exited." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:354 +msgid "Streaming protocols" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:356 +msgid "The following callbacks are called on :class:`Protocol` instances:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:360 +msgid "" +"Called when some data is received. *data* is a non-empty bytes object " +"containing the incoming data." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:364 +msgid "" +"Whether the data is buffered, chunked or reassembled depends on the " +"transport. In general, you shouldn't rely on specific semantics and instead " +"make your parsing generic and flexible enough. However, data is always " +"received in the correct order." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:371 +msgid "" +"Calls when the other end signals it won't send any more data (for example by " +"calling :meth:`write_eof`, if the other end also uses asyncio)." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:375 +msgid "" +"This method may return a false value (including None), in which case the " +"transport will close itself. Conversely, if this method returns a true " +"value, closing the transport is up to the protocol. Since the default " +"implementation returns None, it implicitly closes the connection." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:381 +msgid "" +"Some transports such as SSL don't support half-closed connections, in which " +"case returning true from this method will not prevent closing the connection." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:385 +msgid "" +":meth:`data_received` can be called an arbitrary number of times during a " +"connection. However, :meth:`eof_received` is called at most once and, if " +"called, :meth:`data_received` won't be called after it." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:389 +msgid "State machine:" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:391 +msgid "" +"start -> :meth:`~BaseProtocol.connection_made` [-> :meth:`~Protocol." +"data_received` \\*] [-> :meth:`~Protocol.eof_received` ?] -> :meth:" +"`~BaseProtocol.connection_lost` -> end" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:398 +msgid "Datagram protocols" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:400 +msgid "" +"The following callbacks are called on :class:`DatagramProtocol` instances." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:404 +msgid "" +"Called when a datagram is received. *data* is a bytes object containing the " +"incoming data. *addr* is the address of the peer sending the data; the " +"exact format depends on the transport." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:410 +msgid "" +"Called when a previous send or receive operation raises an :class:" +"`OSError`. *exc* is the :class:`OSError` instance." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:413 +msgid "" +"This method is called in rare conditions, when the transport (e.g. UDP) " +"detects that a datagram couldn't be delivered to its recipient. In many " +"conditions though, undeliverable datagrams will be silently dropped." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:420 +msgid "Flow control callbacks" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:427 +msgid "Called when the transport's buffer goes over the high-water mark." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:431 +msgid "Called when the transport's buffer drains below the low-water mark." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:434 +msgid "" +":meth:`pause_writing` and :meth:`resume_writing` calls are paired -- :meth:" +"`pause_writing` is called once when the buffer goes strictly over the high-" +"water mark (even if subsequent writes increases the buffer size even more), " +"and eventually :meth:`resume_writing` is called once when the buffer size " +"reaches the low-water mark." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:441 +msgid "" +"If the buffer size equals the high-water mark, :meth:`pause_writing` is not " +"called -- it must go strictly over. Conversely, :meth:`resume_writing` is " +"called when the buffer size is equal or lower than the low-water mark. " +"These end conditions are important to ensure that things go as expected when " +"either mark is zero." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:449 +msgid "" +"On BSD systems (OS X, FreeBSD, etc.) flow control is not supported for :" +"class:`DatagramProtocol`, because send failures caused by writing too many " +"packets cannot be detected easily. The socket always appears 'ready' and " +"excess packets are dropped; an :class:`OSError` with errno set to :const:" +"`errno.ENOBUFS` may or may not be raised; if it is raised, it will be " +"reported to :meth:`DatagramProtocol.error_received` but otherwise ignored." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:459 +msgid "Coroutines and protocols" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:461 +msgid "" +"Coroutines can be scheduled in a protocol method using :func:" +"`ensure_future`, but there is no guarantee made about the execution order. " +"Protocols are not aware of coroutines created in protocol methods and so " +"will not wait for them." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:465 +msgid "" +"To have a reliable execution order, use :ref:`stream objects ` in a coroutine with ``yield from``. For example, the :meth:" +"`StreamWriter.drain` coroutine can be used to wait until the write buffer is " +"flushed." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:471 +msgid "Protocol examples" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:476 +msgid "TCP echo client protocol" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:478 +msgid "" +"TCP echo client using the :meth:`AbstractEventLoop.create_connection` " +"method, send data and wait until the connection is closed::" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:508 +msgid "" +"The event loop is running twice. The :meth:`~AbstractEventLoop." +"run_until_complete` method is preferred in this short example to raise an " +"exception if the server is not listening, instead of having to write a short " +"coroutine to handle the exception and stop the running loop. At :meth:" +"`~AbstractEventLoop.run_until_complete` exit, the loop is no longer running, " +"so there is no need to stop the loop in case of an error." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:517 +msgid "" +"The :ref:`TCP echo client using streams ` " +"example uses the :func:`asyncio.open_connection` function." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:524 +msgid "TCP echo server protocol" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:526 +msgid "" +"TCP echo server using the :meth:`AbstractEventLoop.create_server` method, " +"send back received data and close the connection::" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:564 +msgid "" +":meth:`Transport.close` can be called immediately after :meth:" +"`WriteTransport.write` even if data are not sent yet on the socket: both " +"methods are asynchronous. ``yield from`` is not needed because these " +"transport methods are not coroutines." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:571 +msgid "" +"The :ref:`TCP echo server using streams ` " +"example uses the :func:`asyncio.start_server` function." +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:578 +msgid "UDP echo client protocol" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:580 +msgid "" +"UDP echo client using the :meth:`AbstractEventLoop.create_datagram_endpoint` " +"method, send data and close the transport when we received the answer::" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:624 +msgid "UDP echo server protocol" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:626 +msgid "" +"UDP echo server using the :meth:`AbstractEventLoop.create_datagram_endpoint` " +"method, send back received data::" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:660 +msgid "Register an open socket to wait for data using a protocol" +msgstr "" + +#: ../Doc/library/asyncio-protocol.rst:662 +msgid "" +"Wait until a socket receives data using the :meth:`AbstractEventLoop." +"create_connection` method with a protocol, and then close the event loop ::" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:4 +msgid "Queues" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:6 +msgid "Queues:" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:8 +msgid ":class:`Queue`" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:9 +msgid ":class:`PriorityQueue`" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:10 +msgid ":class:`LifoQueue`" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:12 +msgid "" +"asyncio queue API was designed to be close to classes of the :mod:`queue` " +"module (:class:`~queue.Queue`, :class:`~queue.PriorityQueue`, :class:`~queue." +"LifoQueue`), but it has no *timeout* parameter. The :func:`asyncio.wait_for` " +"function can be used to cancel a task after a timeout." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:18 +msgid "Queue" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:22 +msgid "A queue, useful for coordinating producer and consumer coroutines." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:24 +msgid "" +"If *maxsize* is less than or equal to zero, the queue size is infinite. If " +"it is an integer greater than ``0``, then ``yield from put()`` will block " +"when the queue reaches *maxsize*, until an item is removed by :meth:`get`." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:28 +msgid "" +"Unlike the standard library :mod:`queue`, you can reliably know this Queue's " +"size with :meth:`qsize`, since your single-threaded asyncio application " +"won't be interrupted between calling :meth:`qsize` and doing an operation on " +"the Queue." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:35 +msgid "New :meth:`join` and :meth:`task_done` methods." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:40 ../Doc/library/multiprocessing.rst:839 +msgid "Return ``True`` if the queue is empty, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:44 +msgid "Return ``True`` if there are :attr:`maxsize` items in the queue." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:48 +msgid "" +"If the Queue was initialized with ``maxsize=0`` (the default), then :meth:" +"`full()` is never ``True``." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:53 +msgid "" +"Remove and return an item from the queue. If queue is empty, wait until an " +"item is available." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:60 +msgid "The :meth:`empty` method." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:64 ../Doc/library/multiprocessing.rst:843 +msgid "Remove and return an item from the queue." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:66 +msgid "" +"Return an item if one is immediately available, else raise :exc:`QueueEmpty`." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:71 ../Doc/library/multiprocessing.rst:872 +msgid "Block until all items in the queue have been gotten and processed." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:73 +msgid "" +"The count of unfinished tasks goes up whenever an item is added to the " +"queue. The count goes down whenever a consumer thread calls :meth:" +"`task_done` to indicate that the item was retrieved and all work on it is " +"complete. When the count of unfinished tasks drops to zero, :meth:`join` " +"unblocks." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:85 +msgid "" +"Put an item into the queue. If the queue is full, wait until a free slot is " +"available before adding item." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:92 +msgid "The :meth:`full` method." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:96 +msgid "Put an item into the queue without blocking." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:98 +msgid "If no free slot is immediately available, raise :exc:`QueueFull`." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:102 +msgid "Number of items in the queue." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:106 +msgid "Indicate that a formerly enqueued task is complete." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:108 +msgid "" +"Used by queue consumers. For each :meth:`~Queue.get` used to fetch a task, a " +"subsequent call to :meth:`task_done` tells the queue that the processing on " +"the task is complete." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:112 +msgid "" +"If a :meth:`join` is currently blocking, it will resume when all items have " +"been processed (meaning that a :meth:`task_done` call was received for every " +"item that had been :meth:`~Queue.put` into the queue)." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:116 +msgid "" +"Raises :exc:`ValueError` if called more times than there were items placed " +"in the queue." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:123 +msgid "Number of items allowed in the queue." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:127 +msgid "PriorityQueue" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:131 +msgid "" +"A subclass of :class:`Queue`; retrieves entries in priority order (lowest " +"first)." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:134 +msgid "Entries are typically tuples of the form: (priority number, data)." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:138 +msgid "LifoQueue" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:142 +msgid "" +"A subclass of :class:`Queue` that retrieves most recently added entries " +"first." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:147 ../Doc/library/configparser.rst:1235 +#: ../Doc/library/json.rst:498 ../Doc/library/mailbox.rst:1489 +#: ../Doc/library/socket.rst:187 ../Doc/library/sqlite3.rst:732 +#: ../Doc/library/statistics.rst:442 ../Doc/library/subprocess.rst:529 +#: ../Doc/library/xdrlib.rst:255 ../Doc/library/xml.dom.rst:809 +#: ../Doc/library/xml.etree.elementtree.rst:1175 +msgid "Exceptions" +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:151 +msgid "" +"Exception raised when the :meth:`~Queue.get_nowait` method is called on a :" +"class:`Queue` object which is empty." +msgstr "" + +#: ../Doc/library/asyncio-queue.rst:157 +msgid "" +"Exception raised when the :meth:`~Queue.put_nowait` method is called on a :" +"class:`Queue` object which is full." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:7 +msgid "Streams (coroutine based API)" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:10 +msgid "Stream functions" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:14 +msgid "" +"The top-level functions in this module are meant as convenience wrappers " +"only; there's really nothing special there, and if they don't do exactly " +"what you want, feel free to copy their code." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:21 +msgid "" +"A wrapper for :meth:`~AbstractEventLoop.create_connection()` returning a " +"(reader, writer) pair." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:24 +msgid "" +"The reader returned is a :class:`StreamReader` instance; the writer is a :" +"class:`StreamWriter` instance." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:27 +msgid "" +"The arguments are all the usual arguments to :meth:`AbstractEventLoop." +"create_connection` except *protocol_factory*; most common are positional " +"host and port, with various optional keyword arguments following." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:32 ../Doc/library/asyncio-stream.rst:56 +msgid "" +"Additional optional keyword arguments are *loop* (to set the event loop " +"instance to use) and *limit* (to set the buffer limit passed to the :class:" +"`StreamReader`)." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:36 ../Doc/library/asyncio-stream.rst:60 +#: ../Doc/library/asyncio-stream.rst:70 ../Doc/library/asyncio-stream.rst:81 +#: ../Doc/library/asyncio-subprocess.rst:40 +#: ../Doc/library/asyncio-subprocess.rst:59 ../Doc/library/asyncio-task.rst:636 +#: ../Doc/library/asyncio-task.rst:700 +msgid "This function is a :ref:`coroutine `." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:40 +msgid "" +"Start a socket server, with a callback for each client connected. The return " +"value is the same as :meth:`~AbstractEventLoop.create_server()`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:43 +msgid "" +"The *client_connected_cb* parameter is called with two parameters: " +"*client_reader*, *client_writer*. *client_reader* is a :class:" +"`StreamReader` object, while *client_writer* is a :class:`StreamWriter` " +"object. The *client_connected_cb* parameter can either be a plain callback " +"function or a :ref:`coroutine function `; if it is a coroutine " +"function, it will be automatically converted into a :class:`Task`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:51 +msgid "" +"The rest of the arguments are all the usual arguments to :meth:" +"`~AbstractEventLoop.create_server()` except *protocol_factory*; most common " +"are positional *host* and *port*, with various optional keyword arguments " +"following." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:64 +msgid "" +"A wrapper for :meth:`~AbstractEventLoop.create_unix_connection()` returning " +"a (reader, writer) pair." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:67 +msgid "" +"See :func:`open_connection` for information about return value and other " +"details." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:76 +msgid "" +"Start a UNIX Domain Socket server, with a callback for each client connected." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:78 +msgid "" +"See :func:`start_server` for information about return value and other " +"details." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:87 +msgid "StreamReader" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:95 +msgid "Get the exception." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:99 +msgid "Acknowledge the EOF." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:103 +msgid "" +"Feed *data* bytes in the internal buffer. Any operations waiting for the " +"data will be resumed." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:108 +msgid "Set the exception." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:112 +msgid "Set the transport." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:116 +msgid "" +"Read up to *n* bytes. If *n* is not provided, or set to ``-1``, read until " +"EOF and return all read bytes." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:119 ../Doc/library/asyncio-stream.rst:131 +msgid "" +"If the EOF was received and the internal buffer is empty, return an empty " +"``bytes`` object." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:126 +msgid "" +"Read one line, where \"line\" is a sequence of bytes ending with ``\\n``." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:128 +msgid "" +"If EOF is received, and ``\\n`` was not found, the method will return the " +"partial read bytes." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:138 +msgid "" +"Read exactly *n* bytes. Raise an :exc:`IncompleteReadError` if the end of " +"the stream is reached before *n* can be read, the :attr:`IncompleteReadError." +"partial` attribute of the exception contains the partial read bytes." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:147 +msgid "Read data from the stream until ``separator`` is found." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:149 +msgid "" +"On success, the data and separator will be removed from the internal buffer " +"(consumed). Returned data will include the separator at the end." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:153 +msgid "" +"Configured stream limit is used to check result. Limit sets the maximal " +"length of data that can be returned, not counting the separator." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:157 +msgid "" +"If an EOF occurs and the complete separator is still not found, an :exc:" +"`IncompleteReadError` exception will be raised, and the internal buffer will " +"be reset. The :attr:`IncompleteReadError.partial` attribute may contain the " +"separator partially." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:163 +msgid "" +"If the data cannot be read because of over limit, a :exc:`LimitOverrunError` " +"exception will be raised, and the data will be left in the internal buffer, " +"so it can be read again." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:171 +msgid "Return ``True`` if the buffer is empty and :meth:`feed_eof` was called." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:175 +msgid "StreamWriter" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:179 +msgid "Wraps a Transport." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:181 +msgid "" +"This exposes :meth:`write`, :meth:`writelines`, :meth:`can_write_eof()`, :" +"meth:`write_eof`, :meth:`get_extra_info` and :meth:`close`. It adds :meth:" +"`drain` which returns an optional :class:`Future` on which you can wait for " +"flow control. It also adds a transport attribute which references the :" +"class:`Transport` directly." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:191 +msgid "Transport." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:195 +msgid "" +"Return :const:`True` if the transport supports :meth:`write_eof`, :const:" +"`False` if not. See :meth:`WriteTransport.can_write_eof`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:200 +msgid "Close the transport: see :meth:`BaseTransport.close`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:204 +msgid "" +"Let the write buffer of the underlying transport a chance to be flushed." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:206 +msgid "The intended use is to write::" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:211 +msgid "" +"When the size of the transport buffer reaches the high-water limit (the " +"protocol is paused), block until the size of the buffer is drained down to " +"the low-water limit and the protocol is resumed. When there is nothing to " +"wait for, the yield-from continues immediately." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:216 +msgid "" +"Yielding from :meth:`drain` gives the opportunity for the loop to schedule " +"the write operation and flush the buffer. It should especially be used when " +"a possibly large amount of data is written to the transport, and the " +"coroutine does not yield-from between calls to :meth:`write`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:225 +msgid "" +"Return optional transport information: see :meth:`BaseTransport." +"get_extra_info`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:230 +msgid "" +"Write some *data* bytes to the transport: see :meth:`WriteTransport.write`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:235 +msgid "" +"Write a list (or any iterable) of data bytes to the transport: see :meth:" +"`WriteTransport.writelines`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:240 +msgid "" +"Close the write end of the transport after flushing buffered data: see :meth:" +"`WriteTransport.write_eof`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:245 +msgid "StreamReaderProtocol" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:249 +msgid "" +"Trivial helper class to adapt between :class:`Protocol` and :class:" +"`StreamReader`. Subclass of :class:`Protocol`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:252 +msgid "" +"*stream_reader* is a :class:`StreamReader` instance, *client_connected_cb* " +"is an optional function called with (stream_reader, stream_writer) when a " +"connection is made, *loop* is the event loop instance to use." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:256 +msgid "" +"(This is a helper class instead of making :class:`StreamReader` itself a :" +"class:`Protocol` subclass, because the :class:`StreamReader` has other " +"potential uses, and to prevent the user of the :class:`StreamReader` from " +"accidentally calling inappropriate methods of the protocol.)" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:263 +msgid "IncompleteReadError" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:267 +msgid "Incomplete read error, subclass of :exc:`EOFError`." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:271 +msgid "Total number of expected bytes (:class:`int`)." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:275 +msgid "" +"Read bytes string before the end of stream was reached (:class:`bytes`)." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:279 +msgid "LimitOverrunError" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:283 +msgid "Reached the buffer limit while looking for a separator." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:287 +msgid "Total number of to be consumed bytes." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:291 +msgid "Stream examples" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:296 +msgid "TCP echo client using streams" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:298 +msgid "TCP echo client using the :func:`asyncio.open_connection` function::" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:323 +msgid "" +"The :ref:`TCP echo client protocol ` " +"example uses the :meth:`AbstractEventLoop.create_connection` method." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:330 +msgid "TCP echo server using streams" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:332 +msgid "TCP echo server using the :func:`asyncio.start_server` function::" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:368 +msgid "" +"The :ref:`TCP echo server protocol ` " +"example uses the :meth:`AbstractEventLoop.create_server` method." +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:373 +msgid "Get HTTP headers" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:375 +msgid "" +"Simple example querying HTTP headers of the URL passed on the command line::" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:410 ../Doc/library/asyncio-sync.rst:59 +#: ../Doc/library/asyncio-task.rst:702 ../Doc/library/http.rst:34 +#: ../Doc/library/typing.rst:371 ../Doc/library/typing.rst:684 +msgid "Usage::" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:414 +msgid "or with HTTPS::" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:421 +msgid "Register an open socket to wait for data using streams" +msgstr "" + +#: ../Doc/library/asyncio-stream.rst:423 +msgid "" +"Coroutine waiting until a socket receives data using the :func:" +"`open_connection` function::" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:6 +msgid "Subprocess" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:9 +msgid "Windows event loop" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:11 +msgid "" +"On Windows, the default event loop is :class:`SelectorEventLoop` which does " +"not support subprocesses. :class:`ProactorEventLoop` should be used instead. " +"Example to use it on Windows::" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:23 +msgid "" +":ref:`Available event loops ` and :ref:`Platform " +"support `." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:28 +msgid "Create a subprocess: high-level API using Process" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:32 +msgid "Create a subprocess." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:34 +msgid "" +"The *limit* parameter sets the buffer limit passed to the :class:" +"`StreamReader`. See :meth:`AbstractEventLoop.subprocess_exec` for other " +"parameters." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:38 +#: ../Doc/library/asyncio-subprocess.rst:50 +msgid "Return a :class:`~asyncio.subprocess.Process` instance." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:44 +msgid "Run the shell command *cmd*." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:46 +msgid "" +"The *limit* parameter sets the buffer limit passed to the :class:" +"`StreamReader`. See :meth:`AbstractEventLoop.subprocess_shell` for other " +"parameters." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:52 +#: ../Doc/library/asyncio-subprocess.rst:135 +msgid "" +"It is the application's responsibility to ensure that all whitespace and " +"metacharacters are quoted appropriately to avoid `shell injection `_ vulnerabilities. " +"The :func:`shlex.quote` function can be used to properly escape whitespace " +"and shell metacharacters in strings that are going to be used to construct " +"shell commands." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:61 +msgid "" +"Use the :meth:`AbstractEventLoop.connect_read_pipe` and :meth:" +"`AbstractEventLoop.connect_write_pipe` methods to connect pipes." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:66 +msgid "Create a subprocess: low-level API using subprocess.Popen" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:68 +msgid "Run subprocesses asynchronously using the :mod:`subprocess` module." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:72 +msgid "" +"Create a subprocess from one or more string arguments (character strings or " +"bytes strings encoded to the :ref:`filesystem encoding `), where the first string specifies the program to execute, and " +"the remaining strings specify the program's arguments. (Thus, together the " +"string arguments form the ``sys.argv`` value of the program, assuming it is " +"a Python script.) This is similar to the standard library :class:`subprocess." +"Popen` class called with shell=False and the list of strings passed as the " +"first argument; however, where :class:`~subprocess.Popen` takes a single " +"argument which is list of strings, :func:`subprocess_exec` takes multiple " +"string arguments." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:83 +#: ../Doc/library/asyncio-subprocess.rst:126 +msgid "" +"The *protocol_factory* must instanciate a subclass of the :class:`asyncio." +"SubprocessProtocol` class." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:86 +msgid "Other parameters:" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:88 +msgid "" +"*stdin*: Either a file-like object representing the pipe to be connected to " +"the subprocess's standard input stream using :meth:`~AbstractEventLoop." +"connect_write_pipe`, or the constant :const:`subprocess.PIPE` (the default). " +"By default a new pipe will be created and connected." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:94 +msgid "" +"*stdout*: Either a file-like object representing the pipe to be connected to " +"the subprocess's standard output stream using :meth:`~AbstractEventLoop." +"connect_read_pipe`, or the constant :const:`subprocess.PIPE` (the default). " +"By default a new pipe will be created and connected." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:100 +msgid "" +"*stderr*: Either a file-like object representing the pipe to be connected to " +"the subprocess's standard error stream using :meth:`~AbstractEventLoop." +"connect_read_pipe`, or one of the constants :const:`subprocess.PIPE` (the " +"default) or :const:`subprocess.STDOUT`. By default a new pipe will be " +"created and connected. When :const:`subprocess.STDOUT` is specified, the " +"subprocess's standard error stream will be connected to the same pipe as the " +"standard output stream." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:108 +msgid "" +"All other keyword arguments are passed to :class:`subprocess.Popen` without " +"interpretation, except for *bufsize*, *universal_newlines* and *shell*, " +"which should not be specified at all." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:112 +#: ../Doc/library/asyncio-subprocess.rst:132 +msgid "" +"Returns a pair of ``(transport, protocol)``, where *transport* is an " +"instance of :class:`BaseSubprocessTransport`." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:117 +msgid "" +"See the constructor of the :class:`subprocess.Popen` class for parameters." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:121 +msgid "" +"Create a subprocess from *cmd*, which is a character string or a bytes " +"string encoded to the :ref:`filesystem encoding `, " +"using the platform's \"shell\" syntax. This is similar to the standard " +"library :class:`subprocess.Popen` class called with ``shell=True``." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:129 +msgid "" +"See :meth:`~AbstractEventLoop.subprocess_exec` for more details about the " +"remaining arguments." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:146 +msgid "" +"The :meth:`AbstractEventLoop.connect_read_pipe` and :meth:`AbstractEventLoop." +"connect_write_pipe` methods." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:151 ../Doc/library/cmath.rst:244 +#: ../Doc/library/curses.rst:1252 ../Doc/library/decimal.rst:1453 +#: ../Doc/library/hashlib-blake2.rst:114 ../Doc/library/math.rst:418 +#: ../Doc/library/socket.rst:236 ../Doc/library/ssl.rst:519 +#: ../Doc/library/subprocess.rst:799 ../Doc/library/winreg.rst:493 +msgid "Constants" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:155 +msgid "" +"Special value that can be used as the *stdin*, *stdout* or *stderr* argument " +"to :func:`create_subprocess_shell` and :func:`create_subprocess_exec` and " +"indicates that a pipe to the standard stream should be opened." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:161 +msgid "" +"Special value that can be used as the *stderr* argument to :func:" +"`create_subprocess_shell` and :func:`create_subprocess_exec` and indicates " +"that standard error should go into the same handle as standard output." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:168 +msgid "" +"Special value that can be used as the *stdin*, *stdout* or *stderr* argument " +"to :func:`create_subprocess_shell` and :func:`create_subprocess_exec` and " +"indicates that the special file :data:`os.devnull` will be used." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:174 +msgid "Process" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:178 +msgid "" +"A subprocess created by the :func:`create_subprocess_exec` or the :func:" +"`create_subprocess_shell` function." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:181 +msgid "" +"The API of the :class:`~asyncio.subprocess.Process` class was designed to be " +"close to the API of the :class:`subprocess.Popen` class, but there are some " +"differences:" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:185 +msgid "There is no explicit :meth:`~subprocess.Popen.poll` method" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:186 +msgid "" +"The :meth:`~subprocess.Popen.communicate` and :meth:`~subprocess.Popen.wait` " +"methods don't take a *timeout* parameter: use the :func:`wait_for` function" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:189 +msgid "" +"The *universal_newlines* parameter is not supported (only bytes strings are " +"supported)" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:191 +msgid "" +"The :meth:`~asyncio.subprocess.Process.wait` method of the :class:`~asyncio." +"subprocess.Process` class is asynchronous whereas the :meth:`~subprocess." +"Popen.wait` method of the :class:`~subprocess.Popen` class is implemented as " +"a busy loop." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:196 +msgid "" +"This class is :ref:`not thread safe `. See also the :" +"ref:`Subprocess and threads ` section." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:201 +msgid "" +"Wait for child process to terminate. Set and return :attr:`returncode` " +"attribute." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:208 +msgid "" +"This will deadlock when using ``stdout=PIPE`` or ``stderr=PIPE`` and the " +"child process generates enough output to a pipe such that it blocks waiting " +"for the OS pipe buffer to accept more data. Use the :meth:`communicate` " +"method when using pipes to avoid that." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:215 +msgid "" +"Interact with process: Send data to stdin. Read data from stdout and " +"stderr, until end-of-file is reached. Wait for process to terminate. The " +"optional *input* argument should be data to be sent to the child process, or " +"``None``, if no data should be sent to the child. The type of *input* must " +"be bytes." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:221 +msgid ":meth:`communicate` returns a tuple ``(stdout_data, stderr_data)``." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:223 +msgid "" +"If a :exc:`BrokenPipeError` or :exc:`ConnectionResetError` exception is " +"raised when writing *input* into stdin, the exception is ignored. It occurs " +"when the process exits before all data are written into stdin." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:227 +msgid "" +"Note that if you want to send data to the process's stdin, you need to " +"create the Process object with ``stdin=PIPE``. Similarly, to get anything " +"other than ``None`` in the result tuple, you need to give ``stdout=PIPE`` " +"and/or ``stderr=PIPE`` too." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:236 ../Doc/library/subprocess.rst:651 +msgid "" +"The data read is buffered in memory, so do not use this method if the data " +"size is large or unlimited." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:239 +msgid "" +"The method now ignores :exc:`BrokenPipeError` and :exc:" +"`ConnectionResetError`." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:245 +msgid "Sends the signal *signal* to the child process." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:249 +msgid "" +"On Windows, :py:data:`SIGTERM` is an alias for :meth:`terminate`. " +"``CTRL_C_EVENT`` and ``CTRL_BREAK_EVENT`` can be sent to processes started " +"with a *creationflags* parameter which includes ``CREATE_NEW_PROCESS_GROUP``." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:256 +msgid "" +"Stop the child. On Posix OSs the method sends :py:data:`signal.SIGTERM` to " +"the child. On Windows the Win32 API function :c:func:`TerminateProcess` is " +"called to stop the child." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:262 +msgid "" +"Kills the child. On Posix OSs the function sends :py:data:`SIGKILL` to the " +"child. On Windows :meth:`kill` is an alias for :meth:`terminate`." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:267 +msgid "" +"Standard input stream (:class:`StreamWriter`), ``None`` if the process was " +"created with ``stdin=None``." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:272 +msgid "" +"Standard output stream (:class:`StreamReader`), ``None`` if the process was " +"created with ``stdout=None``." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:277 +msgid "" +"Standard error stream (:class:`StreamReader`), ``None`` if the process was " +"created with ``stderr=None``." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:282 +msgid "" +"Use the :meth:`communicate` method rather than :attr:`.stdin.write " +"`, :attr:`.stdout.read ` or :attr:`.stderr.read ` to " +"avoid deadlocks due to streams pausing reading or writing and blocking the " +"child process." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:289 +msgid "The identifier of the process." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:291 +msgid "" +"Note that for processes created by the :func:`create_subprocess_shell` " +"function, this attribute is the process identifier of the spawned shell." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:296 +msgid "" +"Return code of the process when it exited. A ``None`` value indicates that " +"the process has not terminated yet." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:299 +msgid "" +"A negative value ``-N`` indicates that the child was terminated by signal " +"``N`` (Unix only)." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:306 +msgid "Subprocess and threads" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:308 +msgid "" +"asyncio supports running subprocesses from different threads, but there are " +"limits:" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:311 +msgid "An event loop must run in the main thread" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:312 +msgid "" +"The child watcher must be instantiated in the main thread, before executing " +"subprocesses from other threads. Call the :func:`get_child_watcher` function " +"in the main thread to instantiate the child watcher." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:316 +msgid "The :class:`asyncio.subprocess.Process` class is not thread safe." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:320 +msgid "" +"The :ref:`Concurrency and multithreading in asyncio ` section." +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:325 +msgid "Subprocess examples" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:328 +msgid "Subprocess using transport and protocol" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:330 +msgid "" +"Example of a subprocess protocol using to get the output of a subprocess and " +"to wait for the subprocess exit. The subprocess is created by the :meth:" +"`AbstractEventLoop.subprocess_exec` method::" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:384 +msgid "Subprocess using streams" +msgstr "" + +#: ../Doc/library/asyncio-subprocess.rst:386 +msgid "" +"Example using the :class:`~asyncio.subprocess.Process` class to control the " +"subprocess and the :class:`StreamReader` class to read from the standard " +"output. The subprocess is created by the :func:`create_subprocess_exec` " +"function::" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:5 ../Doc/library/multiprocessing.rst:1144 +msgid "Synchronization primitives" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:7 +msgid "Locks:" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:9 +msgid ":class:`Lock`" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:10 +msgid ":class:`Event`" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:11 +msgid ":class:`Condition`" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:13 +msgid "Semaphores:" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:15 +msgid ":class:`Semaphore`" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:16 +msgid ":class:`BoundedSemaphore`" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:18 +msgid "" +"asyncio lock API was designed to be close to classes of the :mod:`threading` " +"module (:class:`~threading.Lock`, :class:`~threading.Event`, :class:" +"`~threading.Condition`, :class:`~threading.Semaphore`, :class:`~threading." +"BoundedSemaphore`), but it has no *timeout* parameter. The :func:`asyncio." +"wait_for` function can be used to cancel a task after a timeout." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:25 +msgid "Locks" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:28 +msgid "Lock" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:32 +msgid "Primitive lock objects." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:34 +msgid "" +"A primitive lock is a synchronization primitive that is not owned by a " +"particular coroutine when locked. A primitive lock is in one of two states, " +"'locked' or 'unlocked'." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:38 +msgid "" +"It is created in the unlocked state. It has two basic methods, :meth:" +"`acquire` and :meth:`release`. When the state is unlocked, acquire() " +"changes the state to locked and returns immediately. When the state is " +"locked, acquire() blocks until a call to release() in another coroutine " +"changes it to unlocked, then the acquire() call resets it to locked and " +"returns. The release() method should only be called in the locked state; it " +"changes the state to unlocked and returns immediately. If an attempt is " +"made to release an unlocked lock, a :exc:`RuntimeError` will be raised." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:47 +msgid "" +"When more than one coroutine is blocked in acquire() waiting for the state " +"to turn to unlocked, only one coroutine proceeds when a release() call " +"resets the state to unlocked; first coroutine which is blocked in acquire() " +"is being processed." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:52 +msgid "" +":meth:`acquire` is a coroutine and should be called with ``yield from``." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:54 +msgid "" +"Locks also support the context management protocol. ``(yield from lock)`` " +"should be used as the context manager expression." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:69 +msgid "Context manager usage::" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:76 +msgid "Lock objects can be tested for locking state::" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:86 +msgid "Return ``True`` if the lock is acquired." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:90 +msgid "Acquire a lock." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:92 ../Doc/library/asyncio-sync.rst:173 +msgid "" +"This method blocks until the lock is unlocked, then sets it to locked and " +"returns ``True``." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:99 +msgid "Release a lock." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:101 +msgid "" +"When the lock is locked, reset it to unlocked, and return. If any other " +"coroutines are blocked waiting for the lock to become unlocked, allow " +"exactly one of them to proceed." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:105 ../Doc/library/asyncio-sync.rst:212 +#: ../Doc/library/threading.rst:414 +msgid "When invoked on an unlocked lock, a :exc:`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:107 ../Doc/library/asyncio-sync.rst:214 +#: ../Doc/library/threading.rst:416 ../Doc/library/threading.rst:492 +msgid "There is no return value." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:111 ../Doc/library/asyncore.rst:90 +#: ../Doc/library/tkinter.ttk.rst:853 +msgid "Event" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:115 +msgid "" +"An Event implementation, asynchronous equivalent to :class:`threading.Event`." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:117 +msgid "" +"Class implementing event objects. An event manages a flag that can be set to " +"true with the :meth:`set` method and reset to false with the :meth:`clear` " +"method. The :meth:`wait` method blocks until the flag is true. The flag is " +"initially false." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:126 +msgid "" +"Reset the internal flag to false. Subsequently, coroutines calling :meth:" +"`wait` will block until :meth:`set` is called to set the internal flag to " +"true again." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:132 +msgid "Return ``True`` if and only if the internal flag is true." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:136 +msgid "" +"Set the internal flag to true. All coroutines waiting for it to become true " +"are awakened. Coroutine that call :meth:`wait` once the flag is true will " +"not block at all." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:142 +msgid "Block until the internal flag is true." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:144 +msgid "" +"If the internal flag is true on entry, return ``True`` immediately. " +"Otherwise, block until another coroutine calls :meth:`set` to set the flag " +"to true, then return ``True``." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:152 +msgid "Condition" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:156 +msgid "" +"A Condition implementation, asynchronous equivalent to :class:`threading." +"Condition`." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:159 +msgid "" +"This class implements condition variable objects. A condition variable " +"allows one or more coroutines to wait until they are notified by another " +"coroutine." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:163 +msgid "" +"If the *lock* argument is given and not ``None``, it must be a :class:`Lock` " +"object, and it is used as the underlying lock. Otherwise, a new :class:" +"`Lock` object is created and used as the underlying lock." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:171 +msgid "Acquire the underlying lock." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:180 +msgid "" +"By default, wake up one coroutine waiting on this condition, if any. If the " +"calling coroutine has not acquired the lock when this method is called, a :" +"exc:`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:184 +msgid "" +"This method wakes up at most *n* of the coroutines waiting for the condition " +"variable; it is a no-op if no coroutines are waiting." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:189 +msgid "" +"An awakened coroutine does not actually return from its :meth:`wait` call " +"until it can reacquire the lock. Since :meth:`notify` does not release the " +"lock, its caller should." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:195 +msgid "Return ``True`` if the underlying lock is acquired." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:199 +msgid "" +"Wake up all coroutines waiting on this condition. This method acts like :" +"meth:`notify`, but wakes up all waiting coroutines instead of one. If the " +"calling coroutine has not acquired the lock when this method is called, a :" +"exc:`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:206 +msgid "Release the underlying lock." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:208 +msgid "" +"When the lock is locked, reset it to unlocked, and return. If any other " +"coroutines are blocked waiting for the lock to become unlocked, allow " +"exactly one of them to proceed." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:218 +msgid "Wait until notified." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:220 +msgid "" +"If the calling coroutine has not acquired the lock when this method is " +"called, a :exc:`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:223 +msgid "" +"This method releases the underlying lock, and then blocks until it is " +"awakened by a :meth:`notify` or :meth:`notify_all` call for the same " +"condition variable in another coroutine. Once awakened, it re-acquires the " +"lock and returns ``True``." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:232 +msgid "Wait until a predicate becomes true." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:234 +msgid "" +"The predicate should be a callable which result will be interpreted as a " +"boolean value. The final predicate value is the return value." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:241 +msgid "Semaphores" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:244 +msgid "Semaphore" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:248 +msgid "A Semaphore implementation." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:250 +msgid "" +"A semaphore manages an internal counter which is decremented by each :meth:" +"`acquire` call and incremented by each :meth:`release` call. The counter can " +"never go below zero; when :meth:`acquire` finds that it is zero, it blocks, " +"waiting until some other coroutine calls :meth:`release`." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:255 +msgid "Semaphores also support the context management protocol." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:257 +msgid "" +"The optional argument gives the initial value for the internal counter; it " +"defaults to ``1``. If the value given is less than ``0``, :exc:`ValueError` " +"is raised." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:265 ../Doc/library/threading.rst:701 +msgid "Acquire a semaphore." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:267 +msgid "" +"If the internal counter is larger than zero on entry, decrement it by one " +"and return ``True`` immediately. If it is zero on entry, block, waiting " +"until some other coroutine has called :meth:`release` to make it larger than " +"``0``, and then return ``True``." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:276 +msgid "Returns ``True`` if semaphore can not be acquired immediately." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:280 +msgid "" +"Release a semaphore, incrementing the internal counter by one. When it was " +"zero on entry and another coroutine is waiting for it to become larger than " +"zero again, wake up that coroutine." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:286 +msgid "BoundedSemaphore" +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:290 +msgid "A bounded semaphore implementation. Inherit from :class:`Semaphore`." +msgstr "" + +#: ../Doc/library/asyncio-sync.rst:292 +msgid "" +"This raises :exc:`ValueError` in :meth:`~Semaphore.release` if it would " +"increase the value above the initial value." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:4 +msgid "Tasks and coroutines" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:9 +msgid "Coroutines" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:11 +msgid "" +"Coroutines used with :mod:`asyncio` may be implemented using the :keyword:" +"`async def` statement, or by using :term:`generators `. The :" +"keyword:`async def` type of coroutine was added in Python 3.5, and is " +"recommended if there is no need to support older Python versions." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:16 +msgid "" +"Generator-based coroutines should be decorated with :func:`@asyncio." +"coroutine `, although this is not strictly enforced. The " +"decorator enables compatibility with :keyword:`async def` coroutines, and " +"also serves as documentation. Generator-based coroutines use the ``yield " +"from`` syntax introduced in :pep:`380`, instead of the original ``yield`` " +"syntax." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:23 +msgid "" +"The word \"coroutine\", like the word \"generator\", is used for two " +"different (though related) concepts:" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:26 +msgid "" +"The function that defines a coroutine (a function definition using :keyword:" +"`async def` or decorated with ``@asyncio.coroutine``). If disambiguation is " +"needed we will call this a *coroutine function* (:func:`iscoroutinefunction` " +"returns ``True``)." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:32 +msgid "" +"The object obtained by calling a coroutine function. This object represents " +"a computation or an I/O operation (usually a combination) that will complete " +"eventually. If disambiguation is needed we will call it a *coroutine " +"object* (:func:`iscoroutine` returns ``True``)." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:37 +msgid "Things a coroutine can do:" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:39 +msgid "" +"``result = await future`` or ``result = yield from future`` -- suspends the " +"coroutine until the future is done, then returns the future's result, or " +"raises an exception, which will be propagated. (If the future is cancelled, " +"it will raise a ``CancelledError`` exception.) Note that tasks are futures, " +"and everything said about futures also applies to tasks." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:46 +msgid "" +"``result = await coroutine`` or ``result = yield from coroutine`` -- wait " +"for another coroutine to produce a result (or raise an exception, which will " +"be propagated). The ``coroutine`` expression must be a *call* to another " +"coroutine." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:51 +msgid "" +"``return expression`` -- produce a result to the coroutine that is waiting " +"for this one using :keyword:`await` or ``yield from``." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:54 +msgid "" +"``raise exception`` -- raise an exception in the coroutine that is waiting " +"for this one using :keyword:`await` or ``yield from``." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:57 +msgid "" +"Calling a coroutine does not start its code running -- the coroutine object " +"returned by the call doesn't do anything until you schedule its execution. " +"There are two basic ways to start it running: call ``await coroutine`` or " +"``yield from coroutine`` from another coroutine (assuming the other " +"coroutine is already running!), or schedule its execution using the :func:" +"`ensure_future` function or the :meth:`AbstractEventLoop.create_task` method." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:66 +msgid "Coroutines (and tasks) can only run when the event loop is running." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:70 +msgid "" +"Decorator to mark generator-based coroutines. This enables the generator " +"use :keyword:`!yield from` to call :keyword:`async def` coroutines, and also " +"enables the generator to be called by :keyword:`async def` coroutines, for " +"instance using an :keyword:`await` expression." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:76 +msgid "" +"There is no need to decorate :keyword:`async def` coroutines themselves." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:78 +msgid "" +"If the generator is not yielded from before it is destroyed, an error " +"message is logged. See :ref:`Detect coroutines never scheduled `." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:84 +msgid "" +"In this documentation, some methods are documented as coroutines, even if " +"they are plain Python functions returning a :class:`Future`. This is " +"intentional to have a freedom of tweaking the implementation of these " +"functions in the future. If such a function is needed to be used in a " +"callback-style code, wrap its result with :func:`ensure_future`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:94 +msgid "Example: Hello World coroutine" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:96 +msgid "Example of coroutine displaying ``\"Hello World\"``::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:110 +msgid "" +"The :ref:`Hello World with call_soon() ` " +"example uses the :meth:`AbstractEventLoop.call_soon` method to schedule a " +"callback." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:118 +msgid "Example: Coroutine displaying the current date" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:120 +msgid "" +"Example of coroutine displaying the current date every second during 5 " +"seconds using the :meth:`sleep` function::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:139 +msgid "The same coroutine implemented using a generator::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:152 +msgid "" +"The :ref:`display the current date with call_later() ` example uses a callback with the :meth:`AbstractEventLoop." +"call_later` method." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:158 +msgid "Example: Chain coroutines" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:160 +msgid "Example chaining coroutines::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:177 +msgid "" +"``compute()`` is chained to ``print_sum()``: ``print_sum()`` coroutine waits " +"until ``compute()`` is completed before returning its result." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:180 +msgid "Sequence diagram of the example:" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:185 +msgid "" +"The \"Task\" is created by the :meth:`AbstractEventLoop.run_until_complete` " +"method when it gets a coroutine object instead of a task." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:188 +msgid "" +"The diagram shows the control flow, it does not describe exactly how things " +"work internally. For example, the sleep coroutine creates an internal future " +"which uses :meth:`AbstractEventLoop.call_later` to wake up the task in 1 " +"second." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:194 +msgid "InvalidStateError" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:198 +msgid "The operation is not allowed in this state." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:202 +msgid "TimeoutError" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:206 +msgid "The operation exceeded the given deadline." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:210 +msgid "" +"This exception is different from the builtin :exc:`TimeoutError` exception!" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:214 +msgid "Future" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:218 +msgid "" +"This class is *almost* compatible with :class:`concurrent.futures.Future`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:220 +msgid "Differences:" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:222 +msgid "" +":meth:`result` and :meth:`exception` do not take a timeout argument and " +"raise an exception when the future isn't done yet." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:225 +msgid "" +"Callbacks registered with :meth:`add_done_callback` are always called via " +"the event loop's :meth:`~AbstractEventLoop.call_soon_threadsafe`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:228 +msgid "" +"This class is not compatible with the :func:`~concurrent.futures.wait` and :" +"func:`~concurrent.futures.as_completed` functions in the :mod:`concurrent." +"futures` package." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:236 +msgid "Cancel the future and schedule callbacks." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:238 +msgid "" +"If the future is already done or cancelled, return ``False``. Otherwise, " +"change the future's state to cancelled, schedule the callbacks and return " +"``True``." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:244 +msgid "Return ``True`` if the future was cancelled." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:248 +msgid "Return True if the future is done." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:250 +msgid "" +"Done means either that a result / exception are available, or that the " +"future was cancelled." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:255 +msgid "Return the result this future represents." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:257 +msgid "" +"If the future has been cancelled, raises :exc:`CancelledError`. If the " +"future's result isn't yet available, raises :exc:`InvalidStateError`. If the " +"future is done and has an exception set, this exception is raised." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:263 +msgid "Return the exception that was set on this future." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:265 +msgid "" +"The exception (or ``None`` if no exception was set) is returned only if the " +"future is done. If the future has been cancelled, raises :exc:" +"`CancelledError`. If the future isn't done yet, raises :exc:" +"`InvalidStateError`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:272 +msgid "Add a callback to be run when the future becomes done." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:274 +msgid "" +"The callback is called with a single argument - the future object. If the " +"future is already done when this is called, the callback is scheduled with :" +"meth:`~AbstractEventLoop.call_soon`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:278 +msgid "" +":ref:`Use functools.partial to pass parameters to the callback `. For example, ``fut.add_done_callback(functools.partial(print, " +"\"Future:\", flush=True))`` will call ``print(\"Future:\", fut, " +"flush=True)``." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:285 +msgid "Remove all instances of a callback from the \"call when done\" list." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:287 +msgid "Returns the number of callbacks removed." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:291 +msgid "Mark the future done and set its result." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:293 ../Doc/library/asyncio-task.rst:300 +msgid "" +"If the future is already done when this method is called, raises :exc:" +"`InvalidStateError`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:298 +msgid "Mark the future done and set an exception." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:305 +msgid "Example: Future with run_until_complete()" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:307 +msgid "" +"Example combining a :class:`Future` and a :ref:`coroutine function " +"`::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:324 +msgid "" +"The coroutine function is responsible for the computation (which takes 1 " +"second) and it stores the result into the future. The :meth:" +"`~AbstractEventLoop.run_until_complete` method waits for the completion of " +"the future." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:330 +msgid "" +"The :meth:`~AbstractEventLoop.run_until_complete` method uses internally " +"the :meth:`~Future.add_done_callback` method to be notified when the future " +"is done." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:336 +msgid "Example: Future with run_forever()" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:338 +msgid "" +"The previous example can be written differently using the :meth:`Future." +"add_done_callback` method to describe explicitly the control flow::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:362 +msgid "" +"In this example, the future is used to link ``slow_operation()`` to " +"``got_result()``: when ``slow_operation()`` is done, ``got_result()`` is " +"called with the result." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:368 +msgid "Task" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:372 +msgid "" +"Schedule the execution of a :ref:`coroutine `: wrap it in a " +"future. A task is a subclass of :class:`Future`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:375 +msgid "" +"A task is responsible for executing a coroutine object in an event loop. If " +"the wrapped coroutine yields from a future, the task suspends the execution " +"of the wrapped coroutine and waits for the completion of the future. When " +"the future is done, the execution of the wrapped coroutine restarts with the " +"result or the exception of the future." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:381 +msgid "" +"Event loops use cooperative scheduling: an event loop only runs one task at " +"a time. Other tasks may run in parallel if other event loops are running in " +"different threads. While a task waits for the completion of a future, the " +"event loop executes a new task." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:386 +msgid "" +"The cancellation of a task is different from the cancelation of a future. " +"Calling :meth:`cancel` will throw a :exc:`~concurrent.futures." +"CancelledError` to the wrapped coroutine. :meth:`~Future.cancelled` only " +"returns ``True`` if the wrapped coroutine did not catch the :exc:" +"`~concurrent.futures.CancelledError` exception, or raised a :exc:" +"`~concurrent.futures.CancelledError` exception." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:394 +msgid "" +"If a pending task is destroyed, the execution of its wrapped :ref:`coroutine " +"` did not complete. It is probably a bug and a warning is logged: " +"see :ref:`Pending task destroyed `." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:398 +msgid "" +"Don't directly create :class:`Task` instances: use the :func:`ensure_future` " +"function or the :meth:`AbstractEventLoop.create_task` method." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:405 +msgid "Return a set of all tasks for an event loop." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:407 +msgid "By default all tasks for the current event loop are returned." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:411 +msgid "Return the currently running task in an event loop or ``None``." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:413 +msgid "By default the current task for the current event loop is returned." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:415 +msgid "``None`` is returned when called not in the context of a :class:`Task`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:419 +msgid "Request that this task cancel itself." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:421 +msgid "" +"This arranges for a :exc:`~concurrent.futures.CancelledError` to be thrown " +"into the wrapped coroutine on the next cycle through the event loop. The " +"coroutine then has a chance to clean up or even deny the request using try/" +"except/finally." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:426 +msgid "" +"Unlike :meth:`Future.cancel`, this does not guarantee that the task will be " +"cancelled: the exception might be caught and acted upon, delaying " +"cancellation of the task or preventing cancellation completely. The task may " +"also return a value or raise a different exception." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:431 +msgid "" +"Immediately after this method is called, :meth:`~Future.cancelled` will not " +"return ``True`` (unless the task was already cancelled). A task will be " +"marked as cancelled when the wrapped coroutine terminates with a :exc:" +"`~concurrent.futures.CancelledError` exception (even if :meth:`cancel` was " +"not called)." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:439 +msgid "Return the list of stack frames for this task's coroutine." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:441 +msgid "" +"If the coroutine is not done, this returns the stack where it is suspended. " +"If the coroutine has completed successfully or was cancelled, this returns " +"an empty list. If the coroutine was terminated by an exception, this " +"returns the list of traceback frames." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:447 +msgid "The frames are always ordered from oldest to newest." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:449 +msgid "" +"The optional limit gives the maximum number of frames to return; by default " +"all available frames are returned. Its meaning differs depending on whether " +"a stack or a traceback is returned: the newest frames of a stack are " +"returned, but the oldest frames of a traceback are returned. (This matches " +"the behavior of the traceback module.)" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:455 +msgid "" +"For reasons beyond our control, only one stack frame is returned for a " +"suspended coroutine." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:460 +msgid "Print the stack or traceback for this task's coroutine." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:462 +msgid "" +"This produces output similar to that of the traceback module, for the frames " +"retrieved by get_stack(). The limit argument is passed to get_stack(). The " +"file argument is an I/O stream to which the output is written; by default " +"output is written to sys.stderr." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:469 +msgid "Example: Parallel execution of tasks" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:471 +msgid "Example executing 3 tasks (A, B, C) in parallel::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:504 +msgid "" +"A task is automatically scheduled for execution when it is created. The " +"event loop stops when all tasks are done." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:509 +msgid "Task functions" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:513 +msgid "" +"In the functions below, the optional *loop* argument allows explicitly " +"setting the event loop object used by the underlying task or coroutine. If " +"it's not provided, the default event loop is used." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:519 +msgid "" +"Return an iterator whose values, when waited for, are :class:`Future` " +"instances." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:522 +msgid "" +"Raises :exc:`asyncio.TimeoutError` if the timeout occurs before all Futures " +"are done." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:525 ../Doc/library/colorsys.rst:59 +#: ../Doc/library/dis.rst:91 ../Doc/library/functools.rst:37 +#: ../Doc/library/functools.rst:220 ../Doc/library/imaplib.rst:410 +#: ../Doc/library/imghdr.rst:76 ../Doc/library/linecache.rst:60 +#: ../Doc/library/locale.rst:471 ../Doc/library/optparse.rst:1103 +#: ../Doc/library/optparse.rst:1123 ../Doc/library/optparse.rst:1145 +#: ../Doc/library/optparse.rst:1163 ../Doc/library/optparse.rst:1202 +#: ../Doc/library/optparse.rst:1240 ../Doc/library/os.rst:2229 +#: ../Doc/library/pipes.rst:27 ../Doc/library/rlcompleter.rst:20 +#: ../Doc/library/sched.rst:37 ../Doc/library/socket.rst:1198 +#: ../Doc/library/sqlite3.rst:513 ../Doc/library/ssl.rst:492 +#: ../Doc/library/ssl.rst:1360 ../Doc/library/ssl.rst:1608 +#: ../Doc/library/stat.rst:101 ../Doc/library/tkinter.rst:444 +#: ../Doc/library/tracemalloc.rst:662 ../Doc/library/unittest.rst:1077 +#: ../Doc/library/xml.dom.pulldom.rst:29 ../Doc/library/xmlrpc.server.rst:298 +msgid "Example::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:533 +msgid "The futures ``f`` are not necessarily members of fs." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:540 +msgid "If the argument is a :class:`Future`, it is returned directly." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:544 +msgid "The function accepts any :term:`awaitable` object." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:549 +msgid "The :meth:`AbstractEventLoop.create_task` method." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:553 +msgid "A deprecated alias to :func:`ensure_future`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:559 +msgid "" +"Return a future aggregating results from the given coroutine objects or " +"futures." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:562 +msgid "" +"All futures must share the same event loop. If all the tasks are done " +"successfully, the returned future's result is the list of results (in the " +"order of the original sequence, not necessarily the order of results " +"arrival). If *return_exceptions* is True, exceptions in the tasks are " +"treated the same as successful results, and gathered in the result list; " +"otherwise, the first raised exception will be immediately propagated to the " +"returned future." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:570 +msgid "" +"Cancellation: if the outer Future is cancelled, all children (that have not " +"completed yet) are also cancelled. If any child is cancelled, this is " +"treated as if it raised :exc:`~concurrent.futures.CancelledError` -- the " +"outer Future is *not* cancelled in this case. (This is to prevent the " +"cancellation of one child to cause other children to be cancelled.)" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:578 +msgid "" +"Return ``True`` if *obj* is a :ref:`coroutine object `, which may " +"be based on a generator or an :keyword:`async def` coroutine." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:583 +msgid "" +"Return ``True`` if *func* is determined to be a :ref:`coroutine function " +"`, which may be a decorated generator function or an :keyword:" +"`async def` function." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:589 +msgid "Submit a :ref:`coroutine object ` to a given event loop." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:591 +msgid "Return a :class:`concurrent.futures.Future` to access the result." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:593 +msgid "" +"This function is meant to be called from a different thread than the one " +"where the event loop is running. Usage::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:603 +msgid "" +"If an exception is raised in the coroutine, the returned future will be " +"notified. It can also be used to cancel the task in the event loop::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:621 +msgid "" +"Unlike other functions from the module, :func:`run_coroutine_threadsafe` " +"requires the *loop* argument to be passed explicitly." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:629 +msgid "" +"Create a :ref:`coroutine ` that completes after a given time (in " +"seconds). If *result* is provided, it is produced to the caller when the " +"coroutine completes." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:633 +msgid "" +"The resolution of the sleep depends on the :ref:`granularity of the event " +"loop `." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:640 +msgid "Wait for a future, shielding it from cancellation." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:642 +msgid "The statement::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:646 +msgid "is exactly equivalent to the statement::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:650 +msgid "" +"*except* that if the coroutine containing it is cancelled, the task running " +"in ``something()`` is not cancelled. From the point of view of " +"``something()``, the cancellation did not happen. But its caller is still " +"cancelled, so the yield-from expression still raises :exc:`~concurrent." +"futures.CancelledError`. Note: If ``something()`` is cancelled by other " +"means this will still cancel ``shield()``." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:657 +msgid "" +"If you want to completely ignore cancellation (not recommended) you can " +"combine ``shield()`` with a try/except clause, as follows::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:669 +msgid "" +"Wait for the Futures and coroutine objects given by the sequence *futures* " +"to complete. Coroutines will be wrapped in Tasks. Returns two sets of :" +"class:`Future`: (done, pending)." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:673 +msgid "The sequence *futures* must not be empty." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:675 +#: ../Doc/library/concurrent.futures.rst:370 +msgid "" +"*timeout* can be used to control the maximum number of seconds to wait " +"before returning. *timeout* can be an int or float. If *timeout* is not " +"specified or ``None``, there is no limit to the wait time." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:679 +msgid "" +"*return_when* indicates when this function should return. It must be one of " +"the following constants of the :mod:`concurrent.futures` module:" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:685 +#: ../Doc/library/concurrent.futures.rst:380 ../Doc/library/curses.rst:1504 +#: ../Doc/library/curses.rst:1621 ../Doc/library/curses.rst:1745 +#: ../Doc/library/select.rst:272 ../Doc/library/select.rst:384 +#: ../Doc/library/select.rst:503 ../Doc/library/select.rst:532 +#: ../Doc/library/select.rst:563 ../Doc/library/select.rst:571 +#: ../Doc/library/select.rst:591 ../Doc/library/select.rst:614 +#: ../Doc/library/selectors.rst:60 ../Doc/library/sys.rst:568 +#: ../Doc/library/xml.dom.rst:928 +msgid "Constant" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:687 +#: ../Doc/library/concurrent.futures.rst:382 +msgid ":const:`FIRST_COMPLETED`" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:687 +#: ../Doc/library/concurrent.futures.rst:382 +msgid "The function will return when any future finishes or is cancelled." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:690 +#: ../Doc/library/concurrent.futures.rst:385 +msgid ":const:`FIRST_EXCEPTION`" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:690 +#: ../Doc/library/concurrent.futures.rst:385 +msgid "" +"The function will return when any future finishes by raising an exception. " +"If no future raises an exception then it is equivalent to :const:" +"`ALL_COMPLETED`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:696 +#: ../Doc/library/concurrent.futures.rst:391 +msgid ":const:`ALL_COMPLETED`" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:696 +#: ../Doc/library/concurrent.futures.rst:391 +msgid "The function will return when all futures finish or are cancelled." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:708 +msgid "" +"This does not raise :exc:`asyncio.TimeoutError`! Futures that aren't done " +"when the timeout occurs are returned in the second set." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:714 +msgid "" +"Wait for the single :class:`Future` or :ref:`coroutine object ` " +"to complete with timeout. If *timeout* is ``None``, block until the future " +"completes." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:718 +msgid "Coroutine will be wrapped in :class:`Task`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:720 +msgid "" +"Returns result of the Future or coroutine. When a timeout occurs, it " +"cancels the task and raises :exc:`asyncio.TimeoutError`. To avoid the task " +"cancellation, wrap it in :func:`shield`." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:724 +msgid "If the wait is cancelled, the future *fut* is also cancelled." +msgstr "" + +#: ../Doc/library/asyncio-task.rst:726 +msgid "This function is a :ref:`coroutine `, usage::" +msgstr "" + +#: ../Doc/library/asyncio-task.rst:730 +msgid "If the wait is cancelled, the future *fut* is now also cancelled." +msgstr "" + +#: ../Doc/library/asyncore.rst:2 +msgid ":mod:`asyncore` --- Asynchronous socket handler" +msgstr "" + +#: ../Doc/library/asyncore.rst:13 +msgid "**Source code:** :source:`Lib/asyncore.py`" +msgstr "" + +#: ../Doc/library/asyncore.rst:22 +msgid "" +"This module provides the basic infrastructure for writing asynchronous " +"socket service clients and servers." +msgstr "" + +#: ../Doc/library/asyncore.rst:25 +msgid "" +"There are only two ways to have a program on a single processor do \"more " +"than one thing at a time.\" Multi-threaded programming is the simplest and " +"most popular way to do it, but there is another very different technique, " +"that lets you have nearly all the advantages of multi-threading, without " +"actually using multiple threads. It's really only practical if your " +"program is largely I/O bound. If your program is processor bound, then pre-" +"emptive scheduled threads are probably what you really need. Network " +"servers are rarely processor bound, however." +msgstr "" + +#: ../Doc/library/asyncore.rst:34 +msgid "" +"If your operating system supports the :c:func:`select` system call in its I/" +"O library (and nearly all do), then you can use it to juggle multiple " +"communication channels at once; doing other work while your I/O is taking " +"place in the \"background.\" Although this strategy can seem strange and " +"complex, especially at first, it is in many ways easier to understand and " +"control than multi-threaded programming. The :mod:`asyncore` module solves " +"many of the difficult problems for you, making the task of building " +"sophisticated high-performance network servers and clients a snap. For " +"\"conversational\" applications and protocols the companion :mod:`asynchat` " +"module is invaluable." +msgstr "" + +#: ../Doc/library/asyncore.rst:45 +msgid "" +"The basic idea behind both modules is to create one or more network " +"*channels*, instances of class :class:`asyncore.dispatcher` and :class:" +"`asynchat.async_chat`. Creating the channels adds them to a global map, " +"used by the :func:`loop` function if you do not provide it with your own " +"*map*." +msgstr "" + +#: ../Doc/library/asyncore.rst:51 +msgid "" +"Once the initial channel(s) is(are) created, calling the :func:`loop` " +"function activates channel service, which continues until the last channel " +"(including any that have been added to the map during asynchronous service) " +"is closed." +msgstr "" + +#: ../Doc/library/asyncore.rst:58 +msgid "" +"Enter a polling loop that terminates after count passes or all open channels " +"have been closed. All arguments are optional. The *count* parameter " +"defaults to None, resulting in the loop terminating only when all channels " +"have been closed. The *timeout* argument sets the timeout parameter for the " +"appropriate :func:`~select.select` or :func:`~select.poll` call, measured in " +"seconds; the default is 30 seconds. The *use_poll* parameter, if true, " +"indicates that :func:`~select.poll` should be used in preference to :func:" +"`~select.select` (the default is ``False``)." +msgstr "" + +#: ../Doc/library/asyncore.rst:67 +msgid "" +"The *map* parameter is a dictionary whose items are the channels to watch. " +"As channels are closed they are deleted from their map. If *map* is " +"omitted, a global map is used. Channels (instances of :class:`asyncore." +"dispatcher`, :class:`asynchat.async_chat` and subclasses thereof) can freely " +"be mixed in the map." +msgstr "" + +#: ../Doc/library/asyncore.rst:76 +msgid "" +"The :class:`dispatcher` class is a thin wrapper around a low-level socket " +"object. To make it more useful, it has a few methods for event-handling " +"which are called from the asynchronous loop. Otherwise, it can be treated " +"as a normal non-blocking socket object." +msgstr "" + +#: ../Doc/library/asyncore.rst:81 +msgid "" +"The firing of low-level events at certain times or in certain connection " +"states tells the asynchronous loop that certain higher-level events have " +"taken place. For example, if we have asked for a socket to connect to " +"another host, we know that the connection has been made when the socket " +"becomes writable for the first time (at this point you know that you may " +"write to it with the expectation of success). The implied higher-level " +"events are:" +msgstr "" + +#: ../Doc/library/asyncore.rst:92 +msgid "``handle_connect()``" +msgstr "" + +#: ../Doc/library/asyncore.rst:92 +msgid "Implied by the first read or write event" +msgstr "" + +#: ../Doc/library/asyncore.rst:95 +msgid "``handle_close()``" +msgstr "" + +#: ../Doc/library/asyncore.rst:95 +msgid "Implied by a read event with no data available" +msgstr "" + +#: ../Doc/library/asyncore.rst:98 +msgid "``handle_accepted()``" +msgstr "" + +#: ../Doc/library/asyncore.rst:98 +msgid "Implied by a read event on a listening socket" +msgstr "" + +#: ../Doc/library/asyncore.rst:102 +msgid "" +"During asynchronous processing, each mapped channel's :meth:`readable` and :" +"meth:`writable` methods are used to determine whether the channel's socket " +"should be added to the list of channels :c:func:`select`\\ ed or :c:func:" +"`poll`\\ ed for read and write events." +msgstr "" + +#: ../Doc/library/asyncore.rst:107 +msgid "" +"Thus, the set of channel events is larger than the basic socket events. The " +"full set of methods that can be overridden in your subclass follows:" +msgstr "" + +#: ../Doc/library/asyncore.rst:113 +msgid "" +"Called when the asynchronous loop detects that a :meth:`read` call on the " +"channel's socket will succeed." +msgstr "" + +#: ../Doc/library/asyncore.rst:119 +msgid "" +"Called when the asynchronous loop detects that a writable socket can be " +"written. Often this method will implement the necessary buffering for " +"performance. For example::" +msgstr "" + +#: ../Doc/library/asyncore.rst:130 +msgid "" +"Called when there is out of band (OOB) data for a socket connection. This " +"will almost never happen, as OOB is tenuously supported and rarely used." +msgstr "" + +#: ../Doc/library/asyncore.rst:136 +msgid "" +"Called when the active opener's socket actually makes a connection. Might " +"send a \"welcome\" banner, or initiate a protocol negotiation with the " +"remote endpoint, for example." +msgstr "" + +#: ../Doc/library/asyncore.rst:143 +msgid "Called when the socket is closed." +msgstr "" + +#: ../Doc/library/asyncore.rst:148 +msgid "" +"Called when an exception is raised and not otherwise handled. The default " +"version prints a condensed traceback." +msgstr "" + +#: ../Doc/library/asyncore.rst:154 +msgid "" +"Called on listening channels (passive openers) when a connection can be " +"established with a new remote endpoint that has issued a :meth:`connect` " +"call for the local endpoint. Deprecated in version 3.2; use :meth:" +"`handle_accepted` instead." +msgstr "" + +#: ../Doc/library/asyncore.rst:164 +msgid "" +"Called on listening channels (passive openers) when a connection has been " +"established with a new remote endpoint that has issued a :meth:`connect` " +"call for the local endpoint. *sock* is a *new* socket object usable to send " +"and receive data on the connection, and *addr* is the address bound to the " +"socket on the other end of the connection." +msgstr "" + +#: ../Doc/library/asyncore.rst:175 +msgid "" +"Called each time around the asynchronous loop to determine whether a " +"channel's socket should be added to the list on which read events can " +"occur. The default method simply returns ``True``, indicating that by " +"default, all channels will be interested in read events." +msgstr "" + +#: ../Doc/library/asyncore.rst:183 +msgid "" +"Called each time around the asynchronous loop to determine whether a " +"channel's socket should be added to the list on which write events can " +"occur. The default method simply returns ``True``, indicating that by " +"default, all channels will be interested in write events." +msgstr "" + +#: ../Doc/library/asyncore.rst:189 +msgid "" +"In addition, each channel delegates or extends many of the socket methods. " +"Most of these are nearly identical to their socket partners." +msgstr "" + +#: ../Doc/library/asyncore.rst:195 +msgid "" +"This is identical to the creation of a normal socket, and will use the same " +"options for creation. Refer to the :mod:`socket` documentation for " +"information on creating sockets." +msgstr "" + +#: ../Doc/library/asyncore.rst:199 +msgid "*family* and *type* arguments can be omitted." +msgstr "" + +#: ../Doc/library/asyncore.rst:205 +msgid "" +"As with the normal socket object, *address* is a tuple with the first " +"element the host to connect to, and the second the port number." +msgstr "" + +#: ../Doc/library/asyncore.rst:211 +msgid "Send *data* to the remote end-point of the socket." +msgstr "" + +#: ../Doc/library/asyncore.rst:216 +msgid "" +"Read at most *buffer_size* bytes from the socket's remote end-point. An " +"empty bytes object implies that the channel has been closed from the other " +"end." +msgstr "" + +#: ../Doc/library/asyncore.rst:220 +msgid "" +"Note that :meth:`recv` may raise :exc:`BlockingIOError` , even though :func:" +"`select.select` or :func:`select.poll` has reported the socket ready for " +"reading." +msgstr "" + +#: ../Doc/library/asyncore.rst:227 +msgid "" +"Listen for connections made to the socket. The *backlog* argument specifies " +"the maximum number of queued connections and should be at least 1; the " +"maximum value is system-dependent (usually 5)." +msgstr "" + +#: ../Doc/library/asyncore.rst:234 +msgid "" +"Bind the socket to *address*. The socket must not already be bound. (The " +"format of *address* depends on the address family --- refer to the :mod:" +"`socket` documentation for more information.) To mark the socket as re-" +"usable (setting the :const:`SO_REUSEADDR` option), call the :class:" +"`dispatcher` object's :meth:`set_reuse_addr` method." +msgstr "" + +#: ../Doc/library/asyncore.rst:243 +msgid "" +"Accept a connection. The socket must be bound to an address and listening " +"for connections. The return value can be either ``None`` or a pair ``(conn, " +"address)`` where *conn* is a *new* socket object usable to send and receive " +"data on the connection, and *address* is the address bound to the socket on " +"the other end of the connection. When ``None`` is returned it means the " +"connection didn't take place, in which case the server should just ignore " +"this event and keep listening for further incoming connections." +msgstr "" + +#: ../Doc/library/asyncore.rst:255 +msgid "" +"Close the socket. All future operations on the socket object will fail. The " +"remote end-point will receive no more data (after queued data is flushed). " +"Sockets are automatically closed when they are garbage-collected." +msgstr "" + +#: ../Doc/library/asyncore.rst:263 +msgid "" +"A :class:`dispatcher` subclass which adds simple buffered output capability, " +"useful for simple clients. For more sophisticated usage use :class:`asynchat." +"async_chat`." +msgstr "" + +#: ../Doc/library/asyncore.rst:269 +msgid "" +"A file_dispatcher takes a file descriptor or :term:`file object` along with " +"an optional map argument and wraps it for use with the :c:func:`poll` or :c:" +"func:`loop` functions. If provided a file object or anything with a :c:func:" +"`fileno` method, that method will be called and passed to the :class:" +"`file_wrapper` constructor. Availability: UNIX." +msgstr "" + +#: ../Doc/library/asyncore.rst:277 +msgid "" +"A file_wrapper takes an integer file descriptor and calls :func:`os.dup` to " +"duplicate the handle so that the original handle may be closed independently " +"of the file_wrapper. This class implements sufficient methods to emulate a " +"socket for use by the :class:`file_dispatcher` class. Availability: UNIX." +msgstr "" + +#: ../Doc/library/asyncore.rst:286 +msgid "asyncore Example basic HTTP client" +msgstr "" + +#: ../Doc/library/asyncore.rst:288 +msgid "" +"Here is a very basic HTTP client that uses the :class:`dispatcher` class to " +"implement its socket handling::" +msgstr "" + +#: ../Doc/library/asyncore.rst:325 +msgid "asyncore Example basic echo server" +msgstr "" + +#: ../Doc/library/asyncore.rst:327 +msgid "" +"Here is a basic echo server that uses the :class:`dispatcher` class to " +"accept connections and dispatches the incoming connections to a handler::" +msgstr "" + +#: ../Doc/library/atexit.rst:2 +msgid ":mod:`atexit` --- Exit handlers" +msgstr "" + +#: ../Doc/library/atexit.rst:12 +msgid "" +"The :mod:`atexit` module defines functions to register and unregister " +"cleanup functions. Functions thus registered are automatically executed " +"upon normal interpreter termination. :mod:`atexit` runs these functions in " +"the *reverse* order in which they were registered; if you register ``A``, " +"``B``, and ``C``, at interpreter termination time they will be run in the " +"order ``C``, ``B``, ``A``." +msgstr "" + +#: ../Doc/library/atexit.rst:19 +msgid "" +"**Note:** The functions registered via this module are not called when the " +"program is killed by a signal not handled by Python, when a Python fatal " +"internal error is detected, or when :func:`os._exit` is called." +msgstr "" + +#: ../Doc/library/atexit.rst:26 +msgid "" +"Register *func* as a function to be executed at termination. Any optional " +"arguments that are to be passed to *func* must be passed as arguments to :" +"func:`register`. It is possible to register the same function and arguments " +"more than once." +msgstr "" + +#: ../Doc/library/atexit.rst:31 +msgid "" +"At normal program termination (for instance, if :func:`sys.exit` is called " +"or the main module's execution completes), all functions registered are " +"called in last in, first out order. The assumption is that lower level " +"modules will normally be imported before higher level modules and thus must " +"be cleaned up later." +msgstr "" + +#: ../Doc/library/atexit.rst:37 +msgid "" +"If an exception is raised during execution of the exit handlers, a traceback " +"is printed (unless :exc:`SystemExit` is raised) and the exception " +"information is saved. After all exit handlers have had a chance to run the " +"last exception to be raised is re-raised." +msgstr "" + +#: ../Doc/library/atexit.rst:42 +msgid "" +"This function returns *func*, which makes it possible to use it as a " +"decorator." +msgstr "" + +#: ../Doc/library/atexit.rst:48 +msgid "" +"Remove *func* from the list of functions to be run at interpreter shutdown. " +"After calling :func:`unregister`, *func* is guaranteed not to be called when " +"the interpreter shuts down, even if it was registered more than once. :func:" +"`unregister` silently does nothing if *func* was not previously registered." +msgstr "" + +#: ../Doc/library/atexit.rst:58 +msgid "Module :mod:`readline`" +msgstr "" + +#: ../Doc/library/atexit.rst:58 +msgid "" +"Useful example of :mod:`atexit` to read and write :mod:`readline` history " +"files." +msgstr "" + +#: ../Doc/library/atexit.rst:65 +msgid ":mod:`atexit` Example" +msgstr "" + +#: ../Doc/library/atexit.rst:67 +msgid "" +"The following simple example demonstrates how a module can initialize a " +"counter from a file when it is imported and save the counter's updated value " +"automatically when the program terminates without relying on the application " +"making an explicit call into this module at termination. ::" +msgstr "" + +#: ../Doc/library/atexit.rst:89 +msgid "" +"Positional and keyword arguments may also be passed to :func:`register` to " +"be passed along to the registered function when it is called::" +msgstr "" + +#: ../Doc/library/atexit.rst:101 +msgid "Usage as a :term:`decorator`::" +msgstr "" + +#: ../Doc/library/atexit.rst:109 +msgid "This only works with functions that can be called without arguments." +msgstr "" + +#: ../Doc/library/audioop.rst:2 +msgid ":mod:`audioop` --- Manipulate raw audio data" +msgstr "" + +#: ../Doc/library/audioop.rst:9 +msgid "" +"The :mod:`audioop` module contains some useful operations on sound " +"fragments. It operates on sound fragments consisting of signed integer " +"samples 8, 16, 24 or 32 bits wide, stored in :term:`bytes-like objects " +"`. All scalar items are integers, unless specified " +"otherwise." +msgstr "" + +#: ../Doc/library/audioop.rst:14 +msgid "" +"Support for 24-bit samples was added. All functions now accept any :term:" +"`bytes-like object`. String input now results in an immediate error." +msgstr "" + +#: ../Doc/library/audioop.rst:25 +msgid "" +"This module provides support for a-LAW, u-LAW and Intel/DVI ADPCM encodings." +msgstr "" + +#: ../Doc/library/audioop.rst:29 +msgid "" +"A few of the more complicated operations only take 16-bit samples, otherwise " +"the sample size (in bytes) is always a parameter of the operation." +msgstr "" + +#: ../Doc/library/audioop.rst:32 +msgid "The module defines the following variables and functions:" +msgstr "" + +#: ../Doc/library/audioop.rst:37 +msgid "" +"This exception is raised on all errors, such as unknown number of bytes per " +"sample, etc." +msgstr "" + +#: ../Doc/library/audioop.rst:43 +msgid "" +"Return a fragment which is the addition of the two samples passed as " +"parameters. *width* is the sample width in bytes, either ``1``, ``2``, ``3`` " +"or ``4``. Both fragments should have the same length. Samples are " +"truncated in case of overflow." +msgstr "" + +#: ../Doc/library/audioop.rst:50 +msgid "" +"Decode an Intel/DVI ADPCM coded fragment to a linear fragment. See the " +"description of :func:`lin2adpcm` for details on ADPCM coding. Return a tuple " +"``(sample, newstate)`` where the sample has the width specified in *width*." +msgstr "" + +#: ../Doc/library/audioop.rst:57 +msgid "" +"Convert sound fragments in a-LAW encoding to linearly encoded sound " +"fragments. a-LAW encoding always uses 8 bits samples, so *width* refers only " +"to the sample width of the output fragment here." +msgstr "" + +#: ../Doc/library/audioop.rst:64 +msgid "Return the average over all samples in the fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:69 +msgid "" +"Return the average peak-peak value over all samples in the fragment. No " +"filtering is done, so the usefulness of this routine is questionable." +msgstr "" + +#: ../Doc/library/audioop.rst:75 +msgid "" +"Return a fragment that is the original fragment with a bias added to each " +"sample. Samples wrap around in case of overflow." +msgstr "" + +#: ../Doc/library/audioop.rst:81 +msgid "" +"\"Byteswap\" all samples in a fragment and returns the modified fragment. " +"Converts big-endian samples to little-endian and vice versa." +msgstr "" + +#: ../Doc/library/audioop.rst:89 +msgid "" +"Return the number of zero crossings in the fragment passed as an argument." +msgstr "" + +#: ../Doc/library/audioop.rst:94 +msgid "" +"Return a factor *F* such that ``rms(add(fragment, mul(reference, -F)))`` is " +"minimal, i.e., return the factor with which you should multiply *reference* " +"to make it match as well as possible to *fragment*. The fragments should " +"both contain 2-byte samples." +msgstr "" + +#: ../Doc/library/audioop.rst:99 +msgid "The time taken by this routine is proportional to ``len(fragment)``." +msgstr "" + +#: ../Doc/library/audioop.rst:104 +msgid "" +"Try to match *reference* as well as possible to a portion of *fragment* " +"(which should be the longer fragment). This is (conceptually) done by " +"taking slices out of *fragment*, using :func:`findfactor` to compute the " +"best match, and minimizing the result. The fragments should both contain 2-" +"byte samples. Return a tuple ``(offset, factor)`` where *offset* is the " +"(integer) offset into *fragment* where the optimal match started and " +"*factor* is the (floating-point) factor as per :func:`findfactor`." +msgstr "" + +#: ../Doc/library/audioop.rst:115 +msgid "" +"Search *fragment* for a slice of length *length* samples (not bytes!) with " +"maximum energy, i.e., return *i* for which ``rms(fragment[i*2:(i" +"+length)*2])`` is maximal. The fragments should both contain 2-byte samples." +msgstr "" + +#: ../Doc/library/audioop.rst:119 +msgid "The routine takes time proportional to ``len(fragment)``." +msgstr "" + +#: ../Doc/library/audioop.rst:124 +msgid "Return the value of sample *index* from the fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:129 +msgid "" +"Convert samples to 4 bit Intel/DVI ADPCM encoding. ADPCM coding is an " +"adaptive coding scheme, whereby each 4 bit number is the difference between " +"one sample and the next, divided by a (varying) step. The Intel/DVI ADPCM " +"algorithm has been selected for use by the IMA, so it may well become a " +"standard." +msgstr "" + +#: ../Doc/library/audioop.rst:134 +msgid "" +"*state* is a tuple containing the state of the coder. The coder returns a " +"tuple ``(adpcmfrag, newstate)``, and the *newstate* should be passed to the " +"next call of :func:`lin2adpcm`. In the initial call, ``None`` can be passed " +"as the state. *adpcmfrag* is the ADPCM coded fragment packed 2 4-bit values " +"per byte." +msgstr "" + +#: ../Doc/library/audioop.rst:142 +msgid "" +"Convert samples in the audio fragment to a-LAW encoding and return this as a " +"bytes object. a-LAW is an audio encoding format whereby you get a dynamic " +"range of about 13 bits using only 8 bit samples. It is used by the Sun " +"audio hardware, among others." +msgstr "" + +#: ../Doc/library/audioop.rst:150 +msgid "Convert samples between 1-, 2-, 3- and 4-byte formats." +msgstr "" + +#: ../Doc/library/audioop.rst:154 +msgid "" +"In some audio formats, such as .WAV files, 16, 24 and 32 bit samples are " +"signed, but 8 bit samples are unsigned. So when converting to 8 bit wide " +"samples for these formats, you need to also add 128 to the result::" +msgstr "" + +#: ../Doc/library/audioop.rst:161 +msgid "" +"The same, in reverse, has to be applied when converting from 8 to 16, 24 or " +"32 bit width samples." +msgstr "" + +#: ../Doc/library/audioop.rst:167 +msgid "" +"Convert samples in the audio fragment to u-LAW encoding and return this as a " +"bytes object. u-LAW is an audio encoding format whereby you get a dynamic " +"range of about 14 bits using only 8 bit samples. It is used by the Sun " +"audio hardware, among others." +msgstr "" + +#: ../Doc/library/audioop.rst:175 +msgid "" +"Return the maximum of the *absolute value* of all samples in a fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:180 +msgid "Return the maximum peak-peak value in the sound fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:185 +msgid "" +"Return a tuple consisting of the minimum and maximum values of all samples " +"in the sound fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:191 +msgid "" +"Return a fragment that has all samples in the original fragment multiplied " +"by the floating-point value *factor*. Samples are truncated in case of " +"overflow." +msgstr "" + +#: ../Doc/library/audioop.rst:197 +msgid "Convert the frame rate of the input fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:199 +msgid "" +"*state* is a tuple containing the state of the converter. The converter " +"returns a tuple ``(newfragment, newstate)``, and *newstate* should be passed " +"to the next call of :func:`ratecv`. The initial call should pass ``None`` " +"as the state." +msgstr "" + +#: ../Doc/library/audioop.rst:203 +msgid "" +"The *weightA* and *weightB* arguments are parameters for a simple digital " +"filter and default to ``1`` and ``0`` respectively." +msgstr "" + +#: ../Doc/library/audioop.rst:209 +msgid "Reverse the samples in a fragment and returns the modified fragment." +msgstr "" + +#: ../Doc/library/audioop.rst:214 +msgid "" +"Return the root-mean-square of the fragment, i.e. ``sqrt(sum(S_i^2)/n)``." +msgstr "" + +#: ../Doc/library/audioop.rst:216 +msgid "This is a measure of the power in an audio signal." +msgstr "" + +#: ../Doc/library/audioop.rst:221 +msgid "" +"Convert a stereo fragment to a mono fragment. The left channel is " +"multiplied by *lfactor* and the right channel by *rfactor* before adding the " +"two channels to give a mono signal." +msgstr "" + +#: ../Doc/library/audioop.rst:228 +msgid "" +"Generate a stereo fragment from a mono fragment. Each pair of samples in " +"the stereo fragment are computed from the mono sample, whereby left channel " +"samples are multiplied by *lfactor* and right channel samples by *rfactor*." +msgstr "" + +#: ../Doc/library/audioop.rst:235 +msgid "" +"Convert sound fragments in u-LAW encoding to linearly encoded sound " +"fragments. u-LAW encoding always uses 8 bits samples, so *width* refers only " +"to the sample width of the output fragment here." +msgstr "" + +#: ../Doc/library/audioop.rst:239 +msgid "" +"Note that operations such as :func:`.mul` or :func:`.max` make no " +"distinction between mono and stereo fragments, i.e. all samples are treated " +"equal. If this is a problem the stereo fragment should be split into two " +"mono fragments first and recombined later. Here is an example of how to do " +"that::" +msgstr "" + +#: ../Doc/library/audioop.rst:253 +msgid "" +"If you use the ADPCM coder to build network packets and you want your " +"protocol to be stateless (i.e. to be able to tolerate packet loss) you " +"should not only transmit the data but also the state. Note that you should " +"send the *initial* state (the one you passed to :func:`lin2adpcm`) along to " +"the decoder, not the final state (as returned by the coder). If you want to " +"use :class:`struct.Struct` to store the state in binary you can code the " +"first element (the predicted value) in 16 bits and the second (the delta " +"index) in 8." +msgstr "" + +#: ../Doc/library/audioop.rst:261 +msgid "" +"The ADPCM coders have never been tried against other ADPCM coders, only " +"against themselves. It could well be that I misinterpreted the standards in " +"which case they will not be interoperable with the respective standards." +msgstr "" + +#: ../Doc/library/audioop.rst:265 +msgid "" +"The :func:`find\\*` routines might look a bit funny at first sight. They are " +"primarily meant to do echo cancellation. A reasonably fast way to do this " +"is to pick the most energetic piece of the output sample, locate that in the " +"input sample and subtract the whole output sample from the input sample::" +msgstr "" + +#: ../Doc/library/base64.rst:2 +msgid ":mod:`base64` --- Base16, Base32, Base64, Base85 Data Encodings" +msgstr "" + +#: ../Doc/library/base64.rst:8 +msgid "**Source code:** :source:`Lib/base64.py`" +msgstr "" + +#: ../Doc/library/base64.rst:16 +msgid "" +"This module provides functions for encoding binary data to printable ASCII " +"characters and decoding such encodings back to binary data. It provides " +"encoding and decoding functions for the encodings specified in :rfc:`3548`, " +"which defines the Base16, Base32, and Base64 algorithms, and for the de-" +"facto standard Ascii85 and Base85 encodings." +msgstr "" + +#: ../Doc/library/base64.rst:22 +msgid "" +"The :rfc:`3548` encodings are suitable for encoding binary data so that it " +"can safely sent by email, used as parts of URLs, or included as part of an " +"HTTP POST request. The encoding algorithm is not the same as the :program:" +"`uuencode` program." +msgstr "" + +#: ../Doc/library/base64.rst:27 +msgid "" +"There are two interfaces provided by this module. The modern interface " +"supports encoding :term:`bytes-like objects ` to ASCII :" +"class:`bytes`, and decoding :term:`bytes-like objects ` " +"or strings containing ASCII to :class:`bytes`. Both base-64 alphabets " +"defined in :rfc:`3548` (normal, and URL- and filesystem-safe) are supported." +msgstr "" + +#: ../Doc/library/base64.rst:33 +msgid "" +"The legacy interface does not support decoding from strings, but it does " +"provide functions for encoding and decoding to and from :term:`file objects " +"`. It only supports the Base64 standard alphabet, and it adds " +"newlines every 76 characters as per :rfc:`2045`. Note that if you are " +"looking for :rfc:`2045` support you probably want to be looking at the :mod:" +"`email` package instead." +msgstr "" + +#: ../Doc/library/base64.rst:41 +msgid "" +"ASCII-only Unicode strings are now accepted by the decoding functions of the " +"modern interface." +msgstr "" + +#: ../Doc/library/base64.rst:45 +msgid "" +"Any :term:`bytes-like objects ` are now accepted by all " +"encoding and decoding functions in this module. Ascii85/Base85 support " +"added." +msgstr "" + +#: ../Doc/library/base64.rst:49 +msgid "The modern interface provides:" +msgstr "" + +#: ../Doc/library/base64.rst:53 +msgid "" +"Encode the :term:`bytes-like object` *s* using Base64 and return the " +"encoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:56 +msgid "" +"Optional *altchars* must be a :term:`bytes-like object` of at least length 2 " +"(additional characters are ignored) which specifies an alternative alphabet " +"for the ``+`` and ``/`` characters. This allows an application to e.g. " +"generate URL or filesystem safe Base64 strings. The default is ``None``, " +"for which the standard Base64 alphabet is used." +msgstr "" + +#: ../Doc/library/base64.rst:65 +msgid "" +"Decode the Base64 encoded :term:`bytes-like object` or ASCII string *s* and " +"return the decoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:68 +msgid "" +"Optional *altchars* must be a :term:`bytes-like object` or ASCII string of " +"at least length 2 (additional characters are ignored) which specifies the " +"alternative alphabet used instead of the ``+`` and ``/`` characters." +msgstr "" + +#: ../Doc/library/base64.rst:72 +msgid "" +"A :exc:`binascii.Error` exception is raised if *s* is incorrectly padded." +msgstr "" + +#: ../Doc/library/base64.rst:75 +msgid "" +"If *validate* is ``False`` (the default), characters that are neither in the " +"normal base-64 alphabet nor the alternative alphabet are discarded prior to " +"the padding check. If *validate* is ``True``, these non-alphabet characters " +"in the input result in a :exc:`binascii.Error`." +msgstr "" + +#: ../Doc/library/base64.rst:84 +msgid "" +"Encode :term:`bytes-like object` *s* using the standard Base64 alphabet and " +"return the encoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:90 +msgid "" +"Decode :term:`bytes-like object` or ASCII string *s* using the standard " +"Base64 alphabet and return the decoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:96 +msgid "" +"Encode :term:`bytes-like object` *s* using the URL- and filesystem-safe " +"alphabet, which substitutes ``-`` instead of ``+`` and ``_`` instead of ``/" +"`` in the standard Base64 alphabet, and return the encoded :class:`bytes`. " +"The result can still contain ``=``." +msgstr "" + +#: ../Doc/library/base64.rst:105 +msgid "" +"Decode :term:`bytes-like object` or ASCII string *s* using the URL- and " +"filesystem-safe alphabet, which substitutes ``-`` instead of ``+`` and ``_`` " +"instead of ``/`` in the standard Base64 alphabet, and return the decoded :" +"class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:114 +msgid "" +"Encode the :term:`bytes-like object` *s* using Base32 and return the " +"encoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:120 +msgid "" +"Decode the Base32 encoded :term:`bytes-like object` or ASCII string *s* and " +"return the decoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:123 ../Doc/library/base64.rst:150 +msgid "" +"Optional *casefold* is a flag specifying whether a lowercase alphabet is " +"acceptable as input. For security purposes, the default is ``False``." +msgstr "" + +#: ../Doc/library/base64.rst:127 +msgid "" +":rfc:`3548` allows for optional mapping of the digit 0 (zero) to the letter " +"O (oh), and for optional mapping of the digit 1 (one) to either the letter I " +"(eye) or letter L (el). The optional argument *map01* when not ``None``, " +"specifies which letter the digit 1 should be mapped to (when *map01* is not " +"``None``, the digit 0 is always mapped to the letter O). For security " +"purposes the default is ``None``, so that 0 and 1 are not allowed in the " +"input." +msgstr "" + +#: ../Doc/library/base64.rst:134 ../Doc/library/base64.rst:154 +msgid "" +"A :exc:`binascii.Error` is raised if *s* is incorrectly padded or if there " +"are non-alphabet characters present in the input." +msgstr "" + +#: ../Doc/library/base64.rst:141 +msgid "" +"Encode the :term:`bytes-like object` *s* using Base16 and return the " +"encoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:147 +msgid "" +"Decode the Base16 encoded :term:`bytes-like object` or ASCII string *s* and " +"return the decoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:161 +msgid "" +"Encode the :term:`bytes-like object` *b* using Ascii85 and return the " +"encoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:164 +msgid "" +"*foldspaces* is an optional flag that uses the special short sequence 'y' " +"instead of 4 consecutive spaces (ASCII 0x20) as supported by 'btoa'. This " +"feature is not supported by the \"standard\" Ascii85 encoding." +msgstr "" + +#: ../Doc/library/base64.rst:168 +msgid "" +"*wrapcol* controls whether the output should have newline (``b'\\n'``) " +"characters added to it. If this is non-zero, each output line will be at " +"most this many characters long." +msgstr "" + +#: ../Doc/library/base64.rst:172 +msgid "" +"*pad* controls whether the input is padded to a multiple of 4 before " +"encoding. Note that the ``btoa`` implementation always pads." +msgstr "" + +#: ../Doc/library/base64.rst:175 +msgid "" +"*adobe* controls whether the encoded byte sequence is framed with ``<~`` and " +"``~>``, which is used by the Adobe implementation." +msgstr "" + +#: ../Doc/library/base64.rst:183 +msgid "" +"Decode the Ascii85 encoded :term:`bytes-like object` or ASCII string *b* and " +"return the decoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:186 +msgid "" +"*foldspaces* is a flag that specifies whether the 'y' short sequence should " +"be accepted as shorthand for 4 consecutive spaces (ASCII 0x20). This feature " +"is not supported by the \"standard\" Ascii85 encoding." +msgstr "" + +#: ../Doc/library/base64.rst:190 +msgid "" +"*adobe* controls whether the input sequence is in Adobe Ascii85 format (i.e. " +"is framed with <~ and ~>)." +msgstr "" + +#: ../Doc/library/base64.rst:193 +msgid "" +"*ignorechars* should be a :term:`bytes-like object` or ASCII string " +"containing characters to ignore from the input. This should only contain " +"whitespace characters, and by default contains all whitespace characters in " +"ASCII." +msgstr "" + +#: ../Doc/library/base64.rst:203 +msgid "" +"Encode the :term:`bytes-like object` *b* using base85 (as used in e.g. git-" +"style binary diffs) and return the encoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/base64.rst:206 +msgid "" +"If *pad* is true, the input is padded with ``b'\\0'`` so its length is a " +"multiple of 4 bytes before encoding." +msgstr "" + +#: ../Doc/library/base64.rst:214 +msgid "" +"Decode the base85-encoded :term:`bytes-like object` or ASCII string *b* and " +"return the decoded :class:`bytes`. Padding is implicitly removed, if " +"necessary." +msgstr "" + +#: ../Doc/library/base64.rst:222 +msgid "" +"Both Base85 and Ascii85 have an expansion factor of 5 to 4 (5 Base85 or " +"Ascii85 characters can encode 4 binary bytes), while the better-known Base64 " +"has an expansion factor of 6 to 4. They are therefore more efficient when " +"space expensive. They differ by details such as the character map used for " +"encoding." +msgstr "" + +#: ../Doc/library/base64.rst:229 +msgid "The legacy interface:" +msgstr "" + +#: ../Doc/library/base64.rst:233 +msgid "" +"Decode the contents of the binary *input* file and write the resulting " +"binary data to the *output* file. *input* and *output* must be :term:`file " +"objects `. *input* will be read until ``input.readline()`` " +"returns an empty bytes object." +msgstr "" + +#: ../Doc/library/base64.rst:242 +msgid "" +"Decode the :term:`bytes-like object` *s*, which must contain one or more " +"lines of base64 encoded data, and return the decoded :class:`bytes`. " +"``decodestring`` is a deprecated alias." +msgstr "" + +#: ../Doc/library/base64.rst:251 +msgid "" +"Encode the contents of the binary *input* file and write the resulting " +"base64 encoded data to the *output* file. *input* and *output* must be :term:" +"`file objects `. *input* will be read until ``input.read()`` " +"returns an empty bytes object. :func:`encode` inserts a newline character " +"(``b'\\n'``) after every 76 bytes of the output, as well as ensuring that " +"the output always ends with a newline, as per :rfc:`2045` (MIME)." +msgstr "" + +#: ../Doc/library/base64.rst:262 +msgid "" +"Encode the :term:`bytes-like object` *s*, which can contain arbitrary binary " +"data, and return :class:`bytes` containing the base64-encoded data, with " +"newlines (``b'\\n'``) inserted after every 76 bytes of output, and ensuring " +"that there is a trailing newline, as per :rfc:`2045` (MIME)." +msgstr "" + +#: ../Doc/library/base64.rst:267 +msgid "``encodestring`` is a deprecated alias." +msgstr "" + +#: ../Doc/library/base64.rst:270 +msgid "An example usage of the module:" +msgstr "" + +#: ../Doc/library/base64.rst:284 ../Doc/library/binhex.rst:43 +#: ../Doc/library/uu.rst:61 +msgid "Module :mod:`binascii`" +msgstr "" + +#: ../Doc/library/base64.rst:284 ../Doc/library/binhex.rst:44 +#: ../Doc/library/uu.rst:62 +msgid "" +"Support module containing ASCII-to-binary and binary-to-ASCII conversions." +msgstr "" + +#: ../Doc/library/base64.rst:287 +msgid "" +":rfc:`1521` - MIME (Multipurpose Internet Mail Extensions) Part One: " +"Mechanisms for Specifying and Describing the Format of Internet Message " +"Bodies" +msgstr "" + +#: ../Doc/library/base64.rst:287 +msgid "" +"Section 5.2, \"Base64 Content-Transfer-Encoding,\" provides the definition " +"of the base64 encoding." +msgstr "" + +#: ../Doc/library/bdb.rst:2 +msgid ":mod:`bdb` --- Debugger framework" +msgstr "" + +#: ../Doc/library/bdb.rst:7 +msgid "**Source code:** :source:`Lib/bdb.py`" +msgstr "" + +#: ../Doc/library/bdb.rst:11 +msgid "" +"The :mod:`bdb` module handles basic debugger functions, like setting " +"breakpoints or managing execution via the debugger." +msgstr "" + +#: ../Doc/library/bdb.rst:14 ../Doc/library/webbrowser.rst:44 +msgid "The following exception is defined:" +msgstr "" + +#: ../Doc/library/bdb.rst:18 +msgid "Exception raised by the :class:`Bdb` class for quitting the debugger." +msgstr "" + +#: ../Doc/library/bdb.rst:21 +msgid "The :mod:`bdb` module also defines two classes:" +msgstr "" + +#: ../Doc/library/bdb.rst:25 +msgid "" +"This class implements temporary breakpoints, ignore counts, disabling and " +"(re-)enabling, and conditionals." +msgstr "" + +#: ../Doc/library/bdb.rst:28 +msgid "" +"Breakpoints are indexed by number through a list called :attr:`bpbynumber` " +"and by ``(file, line)`` pairs through :attr:`bplist`. The former points to " +"a single instance of class :class:`Breakpoint`. The latter points to a list " +"of such instances since there may be more than one breakpoint per line." +msgstr "" + +#: ../Doc/library/bdb.rst:33 +msgid "" +"When creating a breakpoint, its associated filename should be in canonical " +"form. If a *funcname* is defined, a breakpoint hit will be counted when the " +"first line of that function is executed. A conditional breakpoint always " +"counts a hit." +msgstr "" + +#: ../Doc/library/bdb.rst:38 +msgid ":class:`Breakpoint` instances have the following methods:" +msgstr "" + +#: ../Doc/library/bdb.rst:42 +msgid "" +"Delete the breakpoint from the list associated to a file/line. If it is the " +"last breakpoint in that position, it also deletes the entry for the file/" +"line." +msgstr "" + +#: ../Doc/library/bdb.rst:49 +msgid "Mark the breakpoint as enabled." +msgstr "" + +#: ../Doc/library/bdb.rst:54 +msgid "Mark the breakpoint as disabled." +msgstr "" + +#: ../Doc/library/bdb.rst:59 +msgid "" +"Return a string with all the information about the breakpoint, nicely " +"formatted:" +msgstr "" + +#: ../Doc/library/bdb.rst:62 +msgid "The breakpoint number." +msgstr "" + +#: ../Doc/library/bdb.rst:63 +msgid "If it is temporary or not." +msgstr "" + +#: ../Doc/library/bdb.rst:64 +msgid "Its file,line position." +msgstr "" + +#: ../Doc/library/bdb.rst:65 +msgid "The condition that causes a break." +msgstr "" + +#: ../Doc/library/bdb.rst:66 +msgid "If it must be ignored the next N times." +msgstr "" + +#: ../Doc/library/bdb.rst:67 +msgid "The breakpoint hit count." +msgstr "" + +#: ../Doc/library/bdb.rst:73 +msgid "" +"Print the output of :meth:`bpformat` to the file *out*, or if it is " +"``None``, to standard output." +msgstr "" + +#: ../Doc/library/bdb.rst:79 +msgid "The :class:`Bdb` class acts as a generic Python debugger base class." +msgstr "" + +#: ../Doc/library/bdb.rst:81 +msgid "" +"This class takes care of the details of the trace facility; a derived class " +"should implement user interaction. The standard debugger class (:class:`pdb." +"Pdb`) is an example." +msgstr "" + +#: ../Doc/library/bdb.rst:85 +msgid "" +"The *skip* argument, if given, must be an iterable of glob-style module name " +"patterns. The debugger will not step into frames that originate in a module " +"that matches one of these patterns. Whether a frame is considered to " +"originate in a certain module is determined by the ``__name__`` in the frame " +"globals." +msgstr "" + +#: ../Doc/library/bdb.rst:91 ../Doc/library/pdb.rst:170 +msgid "The *skip* argument." +msgstr "" + +#: ../Doc/library/bdb.rst:94 +msgid "" +"The following methods of :class:`Bdb` normally don't need to be overridden." +msgstr "" + +#: ../Doc/library/bdb.rst:98 +msgid "" +"Auxiliary method for getting a filename in a canonical form, that is, as a " +"case-normalized (on case-insensitive filesystems) absolute path, stripped of " +"surrounding angle brackets." +msgstr "" + +#: ../Doc/library/bdb.rst:104 +msgid "" +"Set the :attr:`botframe`, :attr:`stopframe`, :attr:`returnframe` and :attr:" +"`quitting` attributes with values ready to start debugging." +msgstr "" + +#: ../Doc/library/bdb.rst:109 +msgid "" +"This function is installed as the trace function of debugged frames. Its " +"return value is the new trace function (in most cases, that is, itself)." +msgstr "" + +#: ../Doc/library/bdb.rst:112 +msgid "" +"The default implementation decides how to dispatch a frame, depending on the " +"type of event (passed as a string) that is about to be executed. *event* can " +"be one of the following:" +msgstr "" + +#: ../Doc/library/bdb.rst:116 +msgid "``\"line\"``: A new line of code is going to be executed." +msgstr "" + +#: ../Doc/library/bdb.rst:117 +msgid "" +"``\"call\"``: A function is about to be called, or another code block " +"entered." +msgstr "" + +#: ../Doc/library/bdb.rst:119 +msgid "``\"return\"``: A function or other code block is about to return." +msgstr "" + +#: ../Doc/library/bdb.rst:120 +msgid "``\"exception\"``: An exception has occurred." +msgstr "" + +#: ../Doc/library/bdb.rst:121 +msgid "``\"c_call\"``: A C function is about to be called." +msgstr "" + +#: ../Doc/library/bdb.rst:122 +msgid "``\"c_return\"``: A C function has returned." +msgstr "" + +#: ../Doc/library/bdb.rst:123 +msgid "``\"c_exception\"``: A C function has raised an exception." +msgstr "" + +#: ../Doc/library/bdb.rst:125 +msgid "" +"For the Python events, specialized functions (see below) are called. For " +"the C events, no action is taken." +msgstr "" + +#: ../Doc/library/bdb.rst:128 +msgid "The *arg* parameter depends on the previous event." +msgstr "" + +#: ../Doc/library/bdb.rst:130 +msgid "" +"See the documentation for :func:`sys.settrace` for more information on the " +"trace function. For more information on code and frame objects, refer to :" +"ref:`types`." +msgstr "" + +#: ../Doc/library/bdb.rst:136 +msgid "" +"If the debugger should stop on the current line, invoke the :meth:" +"`user_line` method (which should be overridden in subclasses). Raise a :exc:" +"`BdbQuit` exception if the :attr:`Bdb.quitting` flag is set (which can be " +"set from :meth:`user_line`). Return a reference to the :meth:" +"`trace_dispatch` method for further tracing in that scope." +msgstr "" + +#: ../Doc/library/bdb.rst:144 +msgid "" +"If the debugger should stop on this function call, invoke the :meth:" +"`user_call` method (which should be overridden in subclasses). Raise a :exc:" +"`BdbQuit` exception if the :attr:`Bdb.quitting` flag is set (which can be " +"set from :meth:`user_call`). Return a reference to the :meth:" +"`trace_dispatch` method for further tracing in that scope." +msgstr "" + +#: ../Doc/library/bdb.rst:152 +msgid "" +"If the debugger should stop on this function return, invoke the :meth:" +"`user_return` method (which should be overridden in subclasses). Raise a :" +"exc:`BdbQuit` exception if the :attr:`Bdb.quitting` flag is set (which can " +"be set from :meth:`user_return`). Return a reference to the :meth:" +"`trace_dispatch` method for further tracing in that scope." +msgstr "" + +#: ../Doc/library/bdb.rst:160 +msgid "" +"If the debugger should stop at this exception, invokes the :meth:" +"`user_exception` method (which should be overridden in subclasses). Raise a :" +"exc:`BdbQuit` exception if the :attr:`Bdb.quitting` flag is set (which can " +"be set from :meth:`user_exception`). Return a reference to the :meth:" +"`trace_dispatch` method for further tracing in that scope." +msgstr "" + +#: ../Doc/library/bdb.rst:166 +msgid "" +"Normally derived classes don't override the following methods, but they may " +"if they want to redefine the definition of stopping and breakpoints." +msgstr "" + +#: ../Doc/library/bdb.rst:171 +msgid "" +"This method checks if the *frame* is somewhere below :attr:`botframe` in the " +"call stack. :attr:`botframe` is the frame in which debugging started." +msgstr "" + +#: ../Doc/library/bdb.rst:176 +msgid "" +"This method checks if there is a breakpoint in the filename and line " +"belonging to *frame* or, at least, in the current function. If the " +"breakpoint is a temporary one, this method deletes it." +msgstr "" + +#: ../Doc/library/bdb.rst:182 +msgid "" +"This method checks if there is a breakpoint in the filename of the current " +"frame." +msgstr "" + +#: ../Doc/library/bdb.rst:185 +msgid "" +"Derived classes should override these methods to gain control over debugger " +"operation." +msgstr "" + +#: ../Doc/library/bdb.rst:190 +msgid "" +"This method is called from :meth:`dispatch_call` when there is the " +"possibility that a break might be necessary anywhere inside the called " +"function." +msgstr "" + +#: ../Doc/library/bdb.rst:196 +msgid "" +"This method is called from :meth:`dispatch_line` when either :meth:" +"`stop_here` or :meth:`break_here` yields ``True``." +msgstr "" + +#: ../Doc/library/bdb.rst:201 +msgid "" +"This method is called from :meth:`dispatch_return` when :meth:`stop_here` " +"yields ``True``." +msgstr "" + +#: ../Doc/library/bdb.rst:206 +msgid "" +"This method is called from :meth:`dispatch_exception` when :meth:`stop_here` " +"yields ``True``." +msgstr "" + +#: ../Doc/library/bdb.rst:211 +msgid "Handle how a breakpoint must be removed when it is a temporary one." +msgstr "" + +#: ../Doc/library/bdb.rst:213 +msgid "This method must be implemented by derived classes." +msgstr "" + +#: ../Doc/library/bdb.rst:216 +msgid "" +"Derived classes and clients can call the following methods to affect the " +"stepping state." +msgstr "" + +#: ../Doc/library/bdb.rst:221 +msgid "Stop after one line of code." +msgstr "" + +#: ../Doc/library/bdb.rst:225 +msgid "Stop on the next line in or below the given frame." +msgstr "" + +#: ../Doc/library/bdb.rst:229 +msgid "Stop when returning from the given frame." +msgstr "" + +#: ../Doc/library/bdb.rst:233 +msgid "" +"Stop when the line with the line no greater than the current one is reached " +"or when returning from current frame." +msgstr "" + +#: ../Doc/library/bdb.rst:238 +msgid "" +"Start debugging from *frame*. If *frame* is not specified, debugging starts " +"from caller's frame." +msgstr "" + +#: ../Doc/library/bdb.rst:243 +msgid "" +"Stop only at breakpoints or when finished. If there are no breakpoints, set " +"the system trace function to None." +msgstr "" + +#: ../Doc/library/bdb.rst:248 +msgid "" +"Set the :attr:`quitting` attribute to ``True``. This raises :exc:`BdbQuit` " +"in the next call to one of the :meth:`dispatch_\\*` methods." +msgstr "" + +#: ../Doc/library/bdb.rst:252 +msgid "" +"Derived classes and clients can call the following methods to manipulate " +"breakpoints. These methods return a string containing an error message if " +"something went wrong, or ``None`` if all is well." +msgstr "" + +#: ../Doc/library/bdb.rst:258 +msgid "" +"Set a new breakpoint. If the *lineno* line doesn't exist for the *filename* " +"passed as argument, return an error message. The *filename* should be in " +"canonical form, as described in the :meth:`canonic` method." +msgstr "" + +#: ../Doc/library/bdb.rst:264 +msgid "" +"Delete the breakpoints in *filename* and *lineno*. If none were set, an " +"error message is returned." +msgstr "" + +#: ../Doc/library/bdb.rst:269 +msgid "" +"Delete the breakpoint which has the index *arg* in the :attr:`Breakpoint." +"bpbynumber`. If *arg* is not numeric or out of range, return an error " +"message." +msgstr "" + +#: ../Doc/library/bdb.rst:275 +msgid "" +"Delete all breakpoints in *filename*. If none were set, an error message is " +"returned." +msgstr "" + +#: ../Doc/library/bdb.rst:280 +msgid "Delete all existing breakpoints." +msgstr "" + +#: ../Doc/library/bdb.rst:284 +msgid "" +"Return a breakpoint specified by the given number. If *arg* is a string, it " +"will be converted to a number. If *arg* is a non-numeric string, if the " +"given breakpoint never existed or has been deleted, a :exc:`ValueError` is " +"raised." +msgstr "" + +#: ../Doc/library/bdb.rst:293 +msgid "Check if there is a breakpoint for *lineno* of *filename*." +msgstr "" + +#: ../Doc/library/bdb.rst:297 +msgid "" +"Return all breakpoints for *lineno* in *filename*, or an empty list if none " +"are set." +msgstr "" + +#: ../Doc/library/bdb.rst:302 +msgid "Return all breakpoints in *filename*, or an empty list if none are set." +msgstr "" + +#: ../Doc/library/bdb.rst:306 +msgid "Return all breakpoints that are set." +msgstr "" + +#: ../Doc/library/bdb.rst:309 +msgid "" +"Derived classes and clients can call the following methods to get a data " +"structure representing a stack trace." +msgstr "" + +#: ../Doc/library/bdb.rst:314 +msgid "" +"Get a list of records for a frame and all higher (calling) and lower frames, " +"and the size of the higher part." +msgstr "" + +#: ../Doc/library/bdb.rst:319 +msgid "" +"Return a string with information about a stack entry, identified by a " +"``(frame, lineno)`` tuple:" +msgstr "" + +#: ../Doc/library/bdb.rst:322 +msgid "The canonical form of the filename which contains the frame." +msgstr "" + +#: ../Doc/library/bdb.rst:323 +msgid "The function name, or ``\"\"``." +msgstr "" + +#: ../Doc/library/bdb.rst:324 +msgid "The input arguments." +msgstr "" + +#: ../Doc/library/bdb.rst:325 +msgid "The return value." +msgstr "" + +#: ../Doc/library/bdb.rst:326 +msgid "The line of code (if it exists)." +msgstr "" + +#: ../Doc/library/bdb.rst:329 +msgid "" +"The following two methods can be called by clients to use a debugger to " +"debug a :term:`statement`, given as a string." +msgstr "" + +#: ../Doc/library/bdb.rst:334 +msgid "" +"Debug a statement executed via the :func:`exec` function. *globals* " +"defaults to :attr:`__main__.__dict__`, *locals* defaults to *globals*." +msgstr "" + +#: ../Doc/library/bdb.rst:339 +msgid "" +"Debug an expression executed via the :func:`eval` function. *globals* and " +"*locals* have the same meaning as in :meth:`run`." +msgstr "" + +#: ../Doc/library/bdb.rst:344 +msgid "For backwards compatibility. Calls the :meth:`run` method." +msgstr "" + +#: ../Doc/library/bdb.rst:348 +msgid "Debug a single function call, and return its result." +msgstr "" + +#: ../Doc/library/bdb.rst:351 +msgid "Finally, the module defines the following functions:" +msgstr "" + +#: ../Doc/library/bdb.rst:355 +msgid "" +"Check whether we should break here, depending on the way the breakpoint *b* " +"was set." +msgstr "" + +#: ../Doc/library/bdb.rst:358 +msgid "" +"If it was set via line number, it checks if ``b.line`` is the same as the " +"one in the frame also passed as argument. If the breakpoint was set via " +"function name, we have to check we are in the right frame (the right " +"function) and if we are in its first executable line." +msgstr "" + +#: ../Doc/library/bdb.rst:365 +msgid "" +"Determine if there is an effective (active) breakpoint at this line of code. " +"Return a tuple of the breakpoint and a boolean that indicates if it is ok to " +"delete a temporary breakpoint. Return ``(None, None)`` if there is no " +"matching breakpoint." +msgstr "" + +#: ../Doc/library/bdb.rst:372 +msgid "Start debugging with a :class:`Bdb` instance from caller's frame." +msgstr "" + +#: ../Doc/library/binary.rst:5 +msgid "Binary Data Services" +msgstr "" + +#: ../Doc/library/binary.rst:7 +msgid "" +"The modules described in this chapter provide some basic services operations " +"for manipulation of binary data. Other operations on binary data, " +"specifically in relation to file formats and network protocols, are " +"described in the relevant sections." +msgstr "" + +#: ../Doc/library/binary.rst:12 +msgid "" +"Some libraries described under :ref:`textservices` also work with either " +"ASCII-compatible binary formats (for example, :mod:`re`) or all binary data " +"(for example, :mod:`difflib`)." +msgstr "" + +#: ../Doc/library/binary.rst:16 +msgid "" +"In addition, see the documentation for Python's built-in binary data types " +"in :ref:`binaryseq`." +msgstr "" + +#: ../Doc/library/binascii.rst:2 +msgid ":mod:`binascii` --- Convert between binary and ASCII" +msgstr "" + +#: ../Doc/library/binascii.rst:15 +msgid "" +"The :mod:`binascii` module contains a number of methods to convert between " +"binary and various ASCII-encoded binary representations. Normally, you will " +"not use these functions directly but use wrapper modules like :mod:`uu`, :" +"mod:`base64`, or :mod:`binhex` instead. The :mod:`binascii` module contains " +"low-level functions written in C for greater speed that are used by the " +"higher-level modules." +msgstr "" + +#: ../Doc/library/binascii.rst:24 +msgid "" +"``a2b_*`` functions accept Unicode strings containing only ASCII characters. " +"Other functions only accept :term:`bytes-like objects ` " +"(such as :class:`bytes`, :class:`bytearray` and other objects that support " +"the buffer protocol)." +msgstr "" + +#: ../Doc/library/binascii.rst:29 +msgid "ASCII-only unicode strings are now accepted by the ``a2b_*`` functions." +msgstr "" + +#: ../Doc/library/binascii.rst:33 +msgid "The :mod:`binascii` module defines the following functions:" +msgstr "" + +#: ../Doc/library/binascii.rst:38 +msgid "" +"Convert a single line of uuencoded data back to binary and return the binary " +"data. Lines normally contain 45 (binary) bytes, except for the last line. " +"Line data may be followed by whitespace." +msgstr "" + +#: ../Doc/library/binascii.rst:45 +msgid "" +"Convert binary data to a line of ASCII characters, the return value is the " +"converted line, including a newline char. The length of *data* should be at " +"most 45." +msgstr "" + +#: ../Doc/library/binascii.rst:52 +msgid "" +"Convert a block of base64 data back to binary and return the binary data. " +"More than one line may be passed at a time." +msgstr "" + +#: ../Doc/library/binascii.rst:58 +msgid "" +"Convert binary data to a line of ASCII characters in base64 coding. The " +"return value is the converted line, including a newline char if *newline* is " +"true. The output of this function conforms to :rfc:`3548`." +msgstr "" + +#: ../Doc/library/binascii.rst:62 +msgid "Added the *newline* parameter." +msgstr "" + +#: ../Doc/library/binascii.rst:68 +msgid "" +"Convert a block of quoted-printable data back to binary and return the " +"binary data. More than one line may be passed at a time. If the optional " +"argument *header* is present and true, underscores will be decoded as spaces." +msgstr "" + +#: ../Doc/library/binascii.rst:75 +msgid "" +"Convert binary data to a line(s) of ASCII characters in quoted-printable " +"encoding. The return value is the converted line(s). If the optional " +"argument *quotetabs* is present and true, all tabs and spaces will be " +"encoded. If the optional argument *istext* is present and true, newlines " +"are not encoded but trailing whitespace will be encoded. If the optional " +"argument *header* is present and true, spaces will be encoded as underscores " +"per RFC1522. If the optional argument *header* is present and false, newline " +"characters will be encoded as well; otherwise linefeed conversion might " +"corrupt the binary data stream." +msgstr "" + +#: ../Doc/library/binascii.rst:88 +msgid "" +"Convert binhex4 formatted ASCII data to binary, without doing RLE-" +"decompression. The string should contain a complete number of binary bytes, " +"or (in case of the last portion of the binhex4 data) have the remaining bits " +"zero." +msgstr "" + +#: ../Doc/library/binascii.rst:95 +msgid "" +"Perform RLE-decompression on the data, as per the binhex4 standard. The " +"algorithm uses ``0x90`` after a byte as a repeat indicator, followed by a " +"count. A count of ``0`` specifies a byte value of ``0x90``. The routine " +"returns the decompressed data, unless data input data ends in an orphaned " +"repeat indicator, in which case the :exc:`Incomplete` exception is raised." +msgstr "" + +#: ../Doc/library/binascii.rst:101 +msgid "Accept only bytestring or bytearray objects as input." +msgstr "" + +#: ../Doc/library/binascii.rst:107 +msgid "Perform binhex4 style RLE-compression on *data* and return the result." +msgstr "" + +#: ../Doc/library/binascii.rst:112 +msgid "" +"Perform hexbin4 binary-to-ASCII translation and return the resulting string. " +"The argument should already be RLE-coded, and have a length divisible by 3 " +"(except possibly the last fragment)." +msgstr "" + +#: ../Doc/library/binascii.rst:119 +msgid "" +"Compute the binhex4 crc value of *data*, starting with *value* as the " +"initial crc, and return the result." +msgstr "" + +#: ../Doc/library/binascii.rst:125 +msgid "" +"Compute CRC-32, the 32-bit checksum of *data*, starting with an initial CRC " +"of *value*. The default initial CRC is zero. The algorithm is consistent " +"with the ZIP file checksum. Since the algorithm is designed for use as a " +"checksum algorithm, it is not suitable for use as a general hash algorithm. " +"Use as follows::" +msgstr "" + +#: ../Doc/library/binascii.rst:137 +msgid "" +"The result is always unsigned. To generate the same numeric value across all " +"Python versions and platforms, use ``crc32(data) & 0xffffffff``." +msgstr "" + +#: ../Doc/library/binascii.rst:146 +msgid "" +"Return the hexadecimal representation of the binary *data*. Every byte of " +"*data* is converted into the corresponding 2-digit hex representation. The " +"returned bytes object is therefore twice as long as the length of *data*." +msgstr "" + +#: ../Doc/library/binascii.rst:154 +msgid "" +"Return the binary data represented by the hexadecimal string *hexstr*. This " +"function is the inverse of :func:`b2a_hex`. *hexstr* must contain an even " +"number of hexadecimal digits (which can be upper or lower case), otherwise " +"an :exc:`Error` exception is raised." +msgstr "" + +#: ../Doc/library/binascii.rst:162 +msgid "Exception raised on errors. These are usually programming errors." +msgstr "" + +#: ../Doc/library/binascii.rst:167 +msgid "" +"Exception raised on incomplete data. These are usually not programming " +"errors, but may be handled by reading a little more data and trying again." +msgstr "" + +#: ../Doc/library/binascii.rst:175 ../Doc/library/hashlib.rst:290 +#: ../Doc/library/quopri.rst:61 +msgid "Module :mod:`base64`" +msgstr "" + +#: ../Doc/library/binascii.rst:174 +msgid "" +"Support for RFC compliant base64-style encoding in base 16, 32, 64, and 85." +msgstr "" + +#: ../Doc/library/binascii.rst:178 +msgid "Module :mod:`binhex`" +msgstr "" + +#: ../Doc/library/binascii.rst:178 +msgid "Support for the binhex format used on the Macintosh." +msgstr "" + +#: ../Doc/library/binascii.rst:181 +msgid "Module :mod:`uu`" +msgstr "" + +#: ../Doc/library/binascii.rst:181 +msgid "Support for UU encoding used on Unix." +msgstr "" + +#: ../Doc/library/binascii.rst:183 +msgid "Module :mod:`quopri`" +msgstr "" + +#: ../Doc/library/binascii.rst:184 +msgid "Support for quoted-printable encoding used in MIME email messages." +msgstr "" + +#: ../Doc/library/binhex.rst:2 +msgid ":mod:`binhex` --- Encode and decode binhex4 files" +msgstr "" + +#: ../Doc/library/binhex.rst:7 +msgid "**Source code:** :source:`Lib/binhex.py`" +msgstr "" + +#: ../Doc/library/binhex.rst:11 +msgid "" +"This module encodes and decodes files in binhex4 format, a format allowing " +"representation of Macintosh files in ASCII. Only the data fork is handled." +msgstr "" + +#: ../Doc/library/binhex.rst:14 +msgid "The :mod:`binhex` module defines the following functions:" +msgstr "" + +#: ../Doc/library/binhex.rst:19 +msgid "" +"Convert a binary file with filename *input* to binhex file *output*. The " +"*output* parameter can either be a filename or a file-like object (any " +"object supporting a :meth:`write` and :meth:`close` method)." +msgstr "" + +#: ../Doc/library/binhex.rst:26 +msgid "" +"Decode a binhex file *input*. *input* may be a filename or a file-like " +"object supporting :meth:`read` and :meth:`close` methods. The resulting file " +"is written to a file named *output*, unless the argument is ``None`` in " +"which case the output filename is read from the binhex file." +msgstr "" + +#: ../Doc/library/binhex.rst:31 +msgid "The following exception is also defined:" +msgstr "" + +#: ../Doc/library/binhex.rst:36 +msgid "" +"Exception raised when something can't be encoded using the binhex format " +"(for example, a filename is too long to fit in the filename field), or when " +"input is not properly encoded binhex data." +msgstr "" + +#: ../Doc/library/binhex.rst:52 +msgid "" +"There is an alternative, more powerful interface to the coder and decoder, " +"see the source for details." +msgstr "" + +#: ../Doc/library/binhex.rst:55 +msgid "" +"If you code or decode textfiles on non-Macintosh platforms they will still " +"use the old Macintosh newline convention (carriage-return as end of line)." +msgstr "" + +#: ../Doc/library/binhex.rst:58 +msgid "As of this writing, :func:`hexbin` appears to not work in all cases." +msgstr "" + +#: ../Doc/library/bisect.rst:2 +msgid ":mod:`bisect` --- Array bisection algorithm" +msgstr "" + +#: ../Doc/library/bisect.rst:10 +msgid "**Source code:** :source:`Lib/bisect.py`" +msgstr "" + +#: ../Doc/library/bisect.rst:14 +msgid "" +"This module provides support for maintaining a list in sorted order without " +"having to sort the list after each insertion. For long lists of items with " +"expensive comparison operations, this can be an improvement over the more " +"common approach. The module is called :mod:`bisect` because it uses a basic " +"bisection algorithm to do its work. The source code may be most useful as a " +"working example of the algorithm (the boundary conditions are already " +"right!)." +msgstr "" + +#: ../Doc/library/bisect.rst:21 ../Doc/library/heapq.rst:40 +msgid "The following functions are provided:" +msgstr "" + +#: ../Doc/library/bisect.rst:26 +msgid "" +"Locate the insertion point for *x* in *a* to maintain sorted order. The " +"parameters *lo* and *hi* may be used to specify a subset of the list which " +"should be considered; by default the entire list is used. If *x* is already " +"present in *a*, the insertion point will be before (to the left of) any " +"existing entries. The return value is suitable for use as the first " +"parameter to ``list.insert()`` assuming that *a* is already sorted." +msgstr "" + +#: ../Doc/library/bisect.rst:33 +msgid "" +"The returned insertion point *i* partitions the array *a* into two halves so " +"that ``all(val < x for val in a[lo:i])`` for the left side and ``all(val >= " +"x for val in a[i:hi])`` for the right side." +msgstr "" + +#: ../Doc/library/bisect.rst:40 +msgid "" +"Similar to :func:`bisect_left`, but returns an insertion point which comes " +"after (to the right of) any existing entries of *x* in *a*." +msgstr "" + +#: ../Doc/library/bisect.rst:43 +msgid "" +"The returned insertion point *i* partitions the array *a* into two halves so " +"that ``all(val <= x for val in a[lo:i])`` for the left side and ``all(val > " +"x for val in a[i:hi])`` for the right side." +msgstr "" + +#: ../Doc/library/bisect.rst:49 +msgid "" +"Insert *x* in *a* in sorted order. This is equivalent to ``a.insert(bisect." +"bisect_left(a, x, lo, hi), x)`` assuming that *a* is already sorted. Keep " +"in mind that the O(log n) search is dominated by the slow O(n) insertion " +"step." +msgstr "" + +#: ../Doc/library/bisect.rst:57 +msgid "" +"Similar to :func:`insort_left`, but inserting *x* in *a* after any existing " +"entries of *x*." +msgstr "" + +#: ../Doc/library/bisect.rst:62 +msgid "" +"`SortedCollection recipe `_ that uses bisect to build a full-featured collection " +"class with straight-forward search methods and support for a key-function. " +"The keys are precomputed to save unnecessary calls to the key function " +"during searches." +msgstr "" + +#: ../Doc/library/bisect.rst:70 +msgid "Searching Sorted Lists" +msgstr "" + +#: ../Doc/library/bisect.rst:72 +msgid "" +"The above :func:`bisect` functions are useful for finding insertion points " +"but can be tricky or awkward to use for common searching tasks. The " +"following five functions show how to transform them into the standard " +"lookups for sorted lists::" +msgstr "" + +#: ../Doc/library/bisect.rst:114 +msgid "Other Examples" +msgstr "" + +#: ../Doc/library/bisect.rst:118 +msgid "" +"The :func:`bisect` function can be useful for numeric table lookups. This " +"example uses :func:`bisect` to look up a letter grade for an exam score " +"(say) based on a set of ordered numeric breakpoints: 90 and up is an 'A', 80 " +"to 89 is a 'B', and so on::" +msgstr "" + +#: ../Doc/library/bisect.rst:130 +msgid "" +"Unlike the :func:`sorted` function, it does not make sense for the :func:" +"`bisect` functions to have *key* or *reversed* arguments because that would " +"lead to an inefficient design (successive calls to bisect functions would " +"not \"remember\" all of the previous key lookups)." +msgstr "" + +#: ../Doc/library/bisect.rst:135 +msgid "" +"Instead, it is better to search a list of precomputed keys to find the index " +"of the record in question::" +msgstr "" + +#: ../Doc/library/builtins.rst:2 +msgid ":mod:`builtins` --- Built-in objects" +msgstr "" + +#: ../Doc/library/builtins.rst:9 +msgid "" +"This module provides direct access to all 'built-in' identifiers of Python; " +"for example, ``builtins.open`` is the full name for the built-in function :" +"func:`open`. See :ref:`built-in-funcs` and :ref:`built-in-consts` for " +"documentation." +msgstr "" + +#: ../Doc/library/builtins.rst:15 +msgid "" +"This module is not normally accessed explicitly by most applications, but " +"can be useful in modules that provide objects with the same name as a built-" +"in value, but in which the built-in of that name is also needed. For " +"example, in a module that wants to implement an :func:`open` function that " +"wraps the built-in :func:`open`, this module can be used directly::" +msgstr "" + +#: ../Doc/library/builtins.rst:38 +msgid "" +"As an implementation detail, most modules have the name ``__builtins__`` " +"made available as part of their globals. The value of ``__builtins__`` is " +"normally either this module or the value of this module's :attr:`~object." +"__dict__` attribute. Since this is an implementation detail, it may not be " +"used by alternate implementations of Python." +msgstr "" + +#: ../Doc/library/bz2.rst:2 +msgid ":mod:`bz2` --- Support for :program:`bzip2` compression" +msgstr "" + +#: ../Doc/library/bz2.rst:12 +msgid "**Source code:** :source:`Lib/bz2.py`" +msgstr "" + +#: ../Doc/library/bz2.rst:16 +msgid "" +"This module provides a comprehensive interface for compressing and " +"decompressing data using the bzip2 compression algorithm." +msgstr "" + +#: ../Doc/library/bz2.rst:19 +msgid "The :mod:`bz2` module contains:" +msgstr "" + +#: ../Doc/library/bz2.rst:21 +msgid "" +"The :func:`.open` function and :class:`BZ2File` class for reading and " +"writing compressed files." +msgstr "" + +#: ../Doc/library/bz2.rst:23 +msgid "" +"The :class:`BZ2Compressor` and :class:`BZ2Decompressor` classes for " +"incremental (de)compression." +msgstr "" + +#: ../Doc/library/bz2.rst:25 +msgid "" +"The :func:`compress` and :func:`decompress` functions for one-shot " +"(de)compression." +msgstr "" + +#: ../Doc/library/bz2.rst:28 +msgid "" +"All of the classes in this module may safely be accessed from multiple " +"threads." +msgstr "" + +#: ../Doc/library/bz2.rst:32 +msgid "(De)compression of files" +msgstr "" + +#: ../Doc/library/bz2.rst:36 +msgid "" +"Open a bzip2-compressed file in binary or text mode, returning a :term:`file " +"object`." +msgstr "" + +#: ../Doc/library/bz2.rst:39 +msgid "" +"As with the constructor for :class:`BZ2File`, the *filename* argument can be " +"an actual filename (a :class:`str` or :class:`bytes` object), or an existing " +"file object to read from or write to." +msgstr "" + +#: ../Doc/library/bz2.rst:43 +msgid "" +"The *mode* argument can be any of ``'r'``, ``'rb'``, ``'w'``, ``'wb'``, " +"``'x'``, ``'xb'``, ``'a'`` or ``'ab'`` for binary mode, or ``'rt'``, " +"``'wt'``, ``'xt'``, or ``'at'`` for text mode. The default is ``'rb'``." +msgstr "" + +#: ../Doc/library/bz2.rst:47 +msgid "" +"The *compresslevel* argument is an integer from 1 to 9, as for the :class:" +"`BZ2File` constructor." +msgstr "" + +#: ../Doc/library/bz2.rst:50 +msgid "" +"For binary mode, this function is equivalent to the :class:`BZ2File` " +"constructor: ``BZ2File(filename, mode, compresslevel=compresslevel)``. In " +"this case, the *encoding*, *errors* and *newline* arguments must not be " +"provided." +msgstr "" + +#: ../Doc/library/bz2.rst:55 +msgid "" +"For text mode, a :class:`BZ2File` object is created, and wrapped in an :" +"class:`io.TextIOWrapper` instance with the specified encoding, error " +"handling behavior, and line ending(s)." +msgstr "" + +#: ../Doc/library/bz2.rst:61 ../Doc/library/bz2.rst:127 +#: ../Doc/library/tarfile.rst:146 ../Doc/library/tarfile.rst:319 +msgid "The ``'x'`` (exclusive creation) mode was added." +msgstr "" + +#: ../Doc/library/bz2.rst:64 ../Doc/library/bz2.rst:134 +#: ../Doc/library/compileall.rst:156 ../Doc/library/gzip.rst:59 +#: ../Doc/library/gzip.rst:156 ../Doc/library/imghdr.rst:23 +#: ../Doc/library/importlib.rst:1152 ../Doc/library/importlib.rst:1168 +#: ../Doc/library/importlib.rst:1307 ../Doc/library/lzma.rst:68 +#: ../Doc/library/lzma.rst:126 ../Doc/library/os.rst:936 +#: ../Doc/library/os.rst:1435 ../Doc/library/os.rst:1462 +#: ../Doc/library/os.rst:1491 ../Doc/library/os.rst:1535 +#: ../Doc/library/os.rst:1567 ../Doc/library/os.rst:1598 +#: ../Doc/library/os.rst:1611 ../Doc/library/os.rst:1622 +#: ../Doc/library/os.rst:1675 ../Doc/library/os.rst:1731 +#: ../Doc/library/os.rst:1767 ../Doc/library/os.rst:1790 +#: ../Doc/library/os.rst:1812 ../Doc/library/os.rst:1853 +#: ../Doc/library/os.rst:1889 ../Doc/library/os.rst:1910 +#: ../Doc/library/os.rst:1927 ../Doc/library/os.rst:1998 +#: ../Doc/library/os.rst:2248 ../Doc/library/os.rst:2486 +#: ../Doc/library/os.rst:2635 ../Doc/library/os.rst:2649 +#: ../Doc/library/os.rst:2689 ../Doc/library/os.rst:2782 +#: ../Doc/library/os.rst:2841 ../Doc/library/os.rst:2876 +#: ../Doc/library/os.rst:3017 ../Doc/library/os.rst:3330 +#: ../Doc/library/os.path.rst:64 ../Doc/library/os.path.rst:77 +#: ../Doc/library/os.path.rst:116 ../Doc/library/os.path.rst:125 +#: ../Doc/library/os.path.rst:141 ../Doc/library/os.path.rst:151 +#: ../Doc/library/os.path.rst:175 ../Doc/library/os.path.rst:189 +#: ../Doc/library/os.path.rst:212 ../Doc/library/os.path.rst:224 +#: ../Doc/library/os.path.rst:233 ../Doc/library/os.path.rst:243 +#: ../Doc/library/os.path.rst:252 ../Doc/library/os.path.rst:261 +#: ../Doc/library/os.path.rst:270 ../Doc/library/os.path.rst:288 +#: ../Doc/library/os.path.rst:321 ../Doc/library/os.path.rst:333 +#: ../Doc/library/os.path.rst:342 ../Doc/library/os.path.rst:357 +#: ../Doc/library/os.path.rst:375 ../Doc/library/os.path.rst:388 +#: ../Doc/library/os.path.rst:404 ../Doc/library/os.path.rst:420 +#: ../Doc/library/os.path.rst:441 ../Doc/library/os.path.rst:452 +msgid "Accepts a :term:`path-like object`." +msgstr "" + +#: ../Doc/library/bz2.rst:70 +msgid "Open a bzip2-compressed file in binary mode." +msgstr "" + +#: ../Doc/library/bz2.rst:72 +msgid "" +"If *filename* is a :class:`str` or :class:`bytes` object, open the named " +"file directly. Otherwise, *filename* should be a :term:`file object`, which " +"will be used to read or write the compressed data." +msgstr "" + +#: ../Doc/library/bz2.rst:76 +msgid "" +"The *mode* argument can be either ``'r'`` for reading (default), ``'w'`` for " +"overwriting, ``'x'`` for exclusive creation, or ``'a'`` for appending. These " +"can equivalently be given as ``'rb'``, ``'wb'``, ``'xb'`` and ``'ab'`` " +"respectively." +msgstr "" + +#: ../Doc/library/bz2.rst:81 +msgid "" +"If *filename* is a file object (rather than an actual file name), a mode of " +"``'w'`` does not truncate the file, and is instead equivalent to ``'a'``." +msgstr "" + +#: ../Doc/library/bz2.rst:84 +msgid "The *buffering* argument is ignored. Its use is deprecated." +msgstr "" + +#: ../Doc/library/bz2.rst:86 +msgid "" +"If *mode* is ``'w'`` or ``'a'``, *compresslevel* can be a number between " +"``1`` and ``9`` specifying the level of compression: ``1`` produces the " +"least compression, and ``9`` (default) produces the most compression." +msgstr "" + +#: ../Doc/library/bz2.rst:90 +msgid "" +"If *mode* is ``'r'``, the input file may be the concatenation of multiple " +"compressed streams." +msgstr "" + +#: ../Doc/library/bz2.rst:93 +msgid "" +":class:`BZ2File` provides all of the members specified by the :class:`io." +"BufferedIOBase`, except for :meth:`detach` and :meth:`truncate`. Iteration " +"and the :keyword:`with` statement are supported." +msgstr "" + +#: ../Doc/library/bz2.rst:97 +msgid ":class:`BZ2File` also provides the following method:" +msgstr "" + +#: ../Doc/library/bz2.rst:101 +msgid "" +"Return buffered data without advancing the file position. At least one byte " +"of data will be returned (unless at EOF). The exact number of bytes returned " +"is unspecified." +msgstr "" + +#: ../Doc/library/bz2.rst:105 +msgid "" +"While calling :meth:`peek` does not change the file position of the :class:" +"`BZ2File`, it may change the position of the underlying file object (e.g. if " +"the :class:`BZ2File` was constructed by passing a file object for " +"*filename*)." +msgstr "" + +#: ../Doc/library/bz2.rst:115 +msgid "" +"The :meth:`fileno`, :meth:`readable`, :meth:`seekable`, :meth:`writable`, :" +"meth:`read1` and :meth:`readinto` methods were added." +msgstr "" + +#: ../Doc/library/bz2.rst:119 +msgid "" +"Support was added for *filename* being a :term:`file object` instead of an " +"actual filename." +msgstr "" + +#: ../Doc/library/bz2.rst:123 +msgid "" +"The ``'a'`` (append) mode was added, along with support for reading multi-" +"stream files." +msgstr "" + +#: ../Doc/library/bz2.rst:130 ../Doc/library/lzma.rst:122 +msgid "" +"The :meth:`~io.BufferedIOBase.read` method now accepts an argument of " +"``None``." +msgstr "" + +#: ../Doc/library/bz2.rst:139 +msgid "Incremental (de)compression" +msgstr "" + +#: ../Doc/library/bz2.rst:143 +msgid "" +"Create a new compressor object. This object may be used to compress data " +"incrementally. For one-shot compression, use the :func:`compress` function " +"instead." +msgstr "" + +#: ../Doc/library/bz2.rst:147 ../Doc/library/bz2.rst:235 +msgid "" +"*compresslevel*, if given, must be a number between ``1`` and ``9``. The " +"default is ``9``." +msgstr "" + +#: ../Doc/library/bz2.rst:152 +msgid "" +"Provide data to the compressor object. Returns a chunk of compressed data if " +"possible, or an empty byte string otherwise." +msgstr "" + +#: ../Doc/library/bz2.rst:155 +msgid "" +"When you have finished providing data to the compressor, call the :meth:" +"`flush` method to finish the compression process." +msgstr "" + +#: ../Doc/library/bz2.rst:161 +msgid "" +"Finish the compression process. Returns the compressed data left in internal " +"buffers." +msgstr "" + +#: ../Doc/library/bz2.rst:164 +msgid "" +"The compressor object may not be used after this method has been called." +msgstr "" + +#: ../Doc/library/bz2.rst:169 +msgid "" +"Create a new decompressor object. This object may be used to decompress data " +"incrementally. For one-shot compression, use the :func:`decompress` function " +"instead." +msgstr "" + +#: ../Doc/library/bz2.rst:174 +msgid "" +"This class does not transparently handle inputs containing multiple " +"compressed streams, unlike :func:`decompress` and :class:`BZ2File`. If you " +"need to decompress a multi-stream input with :class:`BZ2Decompressor`, you " +"must use a new decompressor for each stream." +msgstr "" + +#: ../Doc/library/bz2.rst:181 ../Doc/library/lzma.rst:242 +msgid "" +"Decompress *data* (a :term:`bytes-like object`), returning uncompressed data " +"as bytes. Some of *data* may be buffered internally, for use in later calls " +"to :meth:`decompress`. The returned data should be concatenated with the " +"output of any previous calls to :meth:`decompress`." +msgstr "" + +#: ../Doc/library/bz2.rst:187 ../Doc/library/lzma.rst:248 +msgid "" +"If *max_length* is nonnegative, returns at most *max_length* bytes of " +"decompressed data. If this limit is reached and further output can be " +"produced, the :attr:`~.needs_input` attribute will be set to ``False``. In " +"this case, the next call to :meth:`~.decompress` may provide *data* as " +"``b''`` to obtain more of the output." +msgstr "" + +#: ../Doc/library/bz2.rst:194 ../Doc/library/lzma.rst:255 +msgid "" +"If all of the input data was decompressed and returned (either because this " +"was less than *max_length* bytes, or because *max_length* was negative), " +"the :attr:`~.needs_input` attribute will be set to ``True``." +msgstr "" + +#: ../Doc/library/bz2.rst:199 ../Doc/library/lzma.rst:260 +msgid "" +"Attempting to decompress data after the end of stream is reached raises an " +"`EOFError`. Any data found after the end of the stream is ignored and saved " +"in the :attr:`~.unused_data` attribute." +msgstr "" + +#: ../Doc/library/bz2.rst:203 ../Doc/library/lzma.rst:264 +msgid "Added the *max_length* parameter." +msgstr "" + +#: ../Doc/library/bz2.rst:208 ../Doc/library/lzma.rst:275 +msgid "``True`` if the end-of-stream marker has been reached." +msgstr "" + +#: ../Doc/library/bz2.rst:215 ../Doc/library/lzma.rst:279 +msgid "Data found after the end of the compressed stream." +msgstr "" + +#: ../Doc/library/bz2.rst:217 +msgid "" +"If this attribute is accessed before the end of the stream has been reached, " +"its value will be ``b''``." +msgstr "" + +#: ../Doc/library/bz2.rst:222 ../Doc/library/lzma.rst:285 +msgid "" +"``False`` if the :meth:`.decompress` method can provide more decompressed " +"data before requiring new uncompressed input." +msgstr "" + +#: ../Doc/library/bz2.rst:229 +msgid "One-shot (de)compression" +msgstr "" + +#: ../Doc/library/bz2.rst:233 +msgid "Compress *data*." +msgstr "" + +#: ../Doc/library/bz2.rst:238 +msgid "For incremental compression, use a :class:`BZ2Compressor` instead." +msgstr "" + +#: ../Doc/library/bz2.rst:243 +msgid "Decompress *data*." +msgstr "" + +#: ../Doc/library/bz2.rst:245 +msgid "" +"If *data* is the concatenation of multiple compressed streams, decompress " +"all of the streams." +msgstr "" + +#: ../Doc/library/bz2.rst:248 +msgid "For incremental decompression, use a :class:`BZ2Decompressor` instead." +msgstr "" + +#: ../Doc/library/bz2.rst:250 +msgid "Support for multi-stream inputs was added." +msgstr "" + +#: ../Doc/library/calendar.rst:2 +msgid ":mod:`calendar` --- General calendar-related functions" +msgstr "" + +#: ../Doc/library/calendar.rst:10 +msgid "**Source code:** :source:`Lib/calendar.py`" +msgstr "" + +#: ../Doc/library/calendar.rst:14 +msgid "" +"This module allows you to output calendars like the Unix :program:`cal` " +"program, and provides additional useful functions related to the calendar. " +"By default, these calendars have Monday as the first day of the week, and " +"Sunday as the last (the European convention). Use :func:`setfirstweekday` to " +"set the first day of the week to Sunday (6) or to any other weekday. " +"Parameters that specify dates are given as integers. For related " +"functionality, see also the :mod:`datetime` and :mod:`time` modules." +msgstr "" + +#: ../Doc/library/calendar.rst:22 +msgid "" +"Most of these functions and classes rely on the :mod:`datetime` module which " +"uses an idealized calendar, the current Gregorian calendar extended in both " +"directions. This matches the definition of the \"proleptic Gregorian\" " +"calendar in Dershowitz and Reingold's book \"Calendrical Calculations\", " +"where it's the base calendar for all computations." +msgstr "" + +#: ../Doc/library/calendar.rst:31 +msgid "" +"Creates a :class:`Calendar` object. *firstweekday* is an integer specifying " +"the first day of the week. ``0`` is Monday (the default), ``6`` is Sunday." +msgstr "" + +#: ../Doc/library/calendar.rst:34 +msgid "" +"A :class:`Calendar` object provides several methods that can be used for " +"preparing the calendar data for formatting. This class doesn't do any " +"formatting itself. This is the job of subclasses." +msgstr "" + +#: ../Doc/library/calendar.rst:39 +msgid ":class:`Calendar` instances have the following methods:" +msgstr "" + +#: ../Doc/library/calendar.rst:43 +msgid "" +"Return an iterator for the week day numbers that will be used for one week. " +"The first value from the iterator will be the same as the value of the :attr:" +"`firstweekday` property." +msgstr "" + +#: ../Doc/library/calendar.rst:50 +msgid "" +"Return an iterator for the month *month* (1-12) in the year *year*. This " +"iterator will return all days (as :class:`datetime.date` objects) for the " +"month and all days before the start of the month or after the end of the " +"month that are required to get a complete week." +msgstr "" + +#: ../Doc/library/calendar.rst:58 +msgid "" +"Return an iterator for the month *month* in the year *year* similar to :meth:" +"`itermonthdates`. Days returned will be tuples consisting of a day number " +"and a week day number." +msgstr "" + +#: ../Doc/library/calendar.rst:65 +msgid "" +"Return an iterator for the month *month* in the year *year* similar to :meth:" +"`itermonthdates`. Days returned will simply be day numbers." +msgstr "" + +#: ../Doc/library/calendar.rst:71 +msgid "" +"Return a list of the weeks in the month *month* of the *year* as full " +"weeks. Weeks are lists of seven :class:`datetime.date` objects." +msgstr "" + +#: ../Doc/library/calendar.rst:77 +msgid "" +"Return a list of the weeks in the month *month* of the *year* as full " +"weeks. Weeks are lists of seven tuples of day numbers and weekday numbers." +msgstr "" + +#: ../Doc/library/calendar.rst:84 +msgid "" +"Return a list of the weeks in the month *month* of the *year* as full " +"weeks. Weeks are lists of seven day numbers." +msgstr "" + +#: ../Doc/library/calendar.rst:90 +msgid "" +"Return the data for the specified year ready for formatting. The return " +"value is a list of month rows. Each month row contains up to *width* months " +"(defaulting to 3). Each month contains between 4 and 6 weeks and each week " +"contains 1--7 days. Days are :class:`datetime.date` objects." +msgstr "" + +#: ../Doc/library/calendar.rst:98 +msgid "" +"Return the data for the specified year ready for formatting (similar to :" +"meth:`yeardatescalendar`). Entries in the week lists are tuples of day " +"numbers and weekday numbers. Day numbers outside this month are zero." +msgstr "" + +#: ../Doc/library/calendar.rst:105 +msgid "" +"Return the data for the specified year ready for formatting (similar to :" +"meth:`yeardatescalendar`). Entries in the week lists are day numbers. Day " +"numbers outside this month are zero." +msgstr "" + +#: ../Doc/library/calendar.rst:112 +msgid "This class can be used to generate plain text calendars." +msgstr "" + +#: ../Doc/library/calendar.rst:114 +msgid ":class:`TextCalendar` instances have the following methods:" +msgstr "" + +#: ../Doc/library/calendar.rst:118 +msgid "" +"Return a month's calendar in a multi-line string. If *w* is provided, it " +"specifies the width of the date columns, which are centered. If *l* is " +"given, it specifies the number of lines that each week will use. Depends on " +"the first weekday as specified in the constructor or set by the :meth:" +"`setfirstweekday` method." +msgstr "" + +#: ../Doc/library/calendar.rst:127 +msgid "Print a month's calendar as returned by :meth:`formatmonth`." +msgstr "" + +#: ../Doc/library/calendar.rst:132 +msgid "" +"Return a *m*-column calendar for an entire year as a multi-line string. " +"Optional parameters *w*, *l*, and *c* are for date column width, lines per " +"week, and number of spaces between month columns, respectively. Depends on " +"the first weekday as specified in the constructor or set by the :meth:" +"`setfirstweekday` method. The earliest year for which a calendar can be " +"generated is platform-dependent." +msgstr "" + +#: ../Doc/library/calendar.rst:142 +msgid "" +"Print the calendar for an entire year as returned by :meth:`formatyear`." +msgstr "" + +#: ../Doc/library/calendar.rst:147 +msgid "This class can be used to generate HTML calendars." +msgstr "" + +#: ../Doc/library/calendar.rst:150 +msgid ":class:`HTMLCalendar` instances have the following methods:" +msgstr "" + +#: ../Doc/library/calendar.rst:154 +msgid "" +"Return a month's calendar as an HTML table. If *withyear* is true the year " +"will be included in the header, otherwise just the month name will be used." +msgstr "" + +#: ../Doc/library/calendar.rst:161 +msgid "" +"Return a year's calendar as an HTML table. *width* (defaulting to 3) " +"specifies the number of months per row." +msgstr "" + +#: ../Doc/library/calendar.rst:167 +msgid "" +"Return a year's calendar as a complete HTML page. *width* (defaulting to 3) " +"specifies the number of months per row. *css* is the name for the cascading " +"style sheet to be used. :const:`None` can be passed if no style sheet should " +"be used. *encoding* specifies the encoding to be used for the output " +"(defaulting to the system default encoding)." +msgstr "" + +#: ../Doc/library/calendar.rst:176 +msgid "" +"This subclass of :class:`TextCalendar` can be passed a locale name in the " +"constructor and will return month and weekday names in the specified locale. " +"If this locale includes an encoding all strings containing month and weekday " +"names will be returned as unicode." +msgstr "" + +#: ../Doc/library/calendar.rst:184 +msgid "" +"This subclass of :class:`HTMLCalendar` can be passed a locale name in the " +"constructor and will return month and weekday names in the specified locale. " +"If this locale includes an encoding all strings containing month and weekday " +"names will be returned as unicode." +msgstr "" + +#: ../Doc/library/calendar.rst:191 +msgid "" +"The :meth:`formatweekday` and :meth:`formatmonthname` methods of these two " +"classes temporarily change the current locale to the given *locale*. " +"Because the current locale is a process-wide setting, they are not thread-" +"safe." +msgstr "" + +#: ../Doc/library/calendar.rst:196 +msgid "For simple text calendars this module provides the following functions." +msgstr "" + +#: ../Doc/library/calendar.rst:200 +msgid "" +"Sets the weekday (``0`` is Monday, ``6`` is Sunday) to start each week. The " +"values :const:`MONDAY`, :const:`TUESDAY`, :const:`WEDNESDAY`, :const:" +"`THURSDAY`, :const:`FRIDAY`, :const:`SATURDAY`, and :const:`SUNDAY` are " +"provided for convenience. For example, to set the first weekday to Sunday::" +msgstr "" + +#: ../Doc/library/calendar.rst:211 +msgid "Returns the current setting for the weekday to start each week." +msgstr "" + +#: ../Doc/library/calendar.rst:216 +msgid "" +"Returns :const:`True` if *year* is a leap year, otherwise :const:`False`." +msgstr "" + +#: ../Doc/library/calendar.rst:221 +msgid "" +"Returns the number of leap years in the range from *y1* to *y2* (exclusive), " +"where *y1* and *y2* are years." +msgstr "" + +#: ../Doc/library/calendar.rst:224 +msgid "This function works for ranges spanning a century change." +msgstr "" + +#: ../Doc/library/calendar.rst:229 +msgid "" +"Returns the day of the week (``0`` is Monday) for *year* (``1970``--...), " +"*month* (``1``--``12``), *day* (``1``--``31``)." +msgstr "" + +#: ../Doc/library/calendar.rst:235 +msgid "" +"Return a header containing abbreviated weekday names. *n* specifies the " +"width in characters for one weekday." +msgstr "" + +#: ../Doc/library/calendar.rst:241 +msgid "" +"Returns weekday of first day of the month and number of days in month, for " +"the specified *year* and *month*." +msgstr "" + +#: ../Doc/library/calendar.rst:247 +msgid "" +"Returns a matrix representing a month's calendar. Each row represents a " +"week; days outside of the month a represented by zeros. Each week begins " +"with Monday unless set by :func:`setfirstweekday`." +msgstr "" + +#: ../Doc/library/calendar.rst:254 +msgid "Prints a month's calendar as returned by :func:`month`." +msgstr "" + +#: ../Doc/library/calendar.rst:259 +msgid "" +"Returns a month's calendar in a multi-line string using the :meth:" +"`formatmonth` of the :class:`TextCalendar` class." +msgstr "" + +#: ../Doc/library/calendar.rst:265 +msgid "" +"Prints the calendar for an entire year as returned by :func:`calendar`." +msgstr "" + +#: ../Doc/library/calendar.rst:270 +msgid "" +"Returns a 3-column calendar for an entire year as a multi-line string using " +"the :meth:`formatyear` of the :class:`TextCalendar` class." +msgstr "" + +#: ../Doc/library/calendar.rst:276 +msgid "" +"An unrelated but handy function that takes a time tuple such as returned by " +"the :func:`~time.gmtime` function in the :mod:`time` module, and returns the " +"corresponding Unix timestamp value, assuming an epoch of 1970, and the POSIX " +"encoding. In fact, :func:`time.gmtime` and :func:`timegm` are each others' " +"inverse." +msgstr "" + +#: ../Doc/library/calendar.rst:283 +msgid "The :mod:`calendar` module exports the following data attributes:" +msgstr "" + +#: ../Doc/library/calendar.rst:287 +msgid "An array that represents the days of the week in the current locale." +msgstr "" + +#: ../Doc/library/calendar.rst:292 +msgid "" +"An array that represents the abbreviated days of the week in the current " +"locale." +msgstr "" + +#: ../Doc/library/calendar.rst:297 +msgid "" +"An array that represents the months of the year in the current locale. This " +"follows normal convention of January being month number 1, so it has a " +"length of 13 and ``month_name[0]`` is the empty string." +msgstr "" + +#: ../Doc/library/calendar.rst:304 +msgid "" +"An array that represents the abbreviated months of the year in the current " +"locale. This follows normal convention of January being month number 1, so " +"it has a length of 13 and ``month_abbr[0]`` is the empty string." +msgstr "" + +#: ../Doc/library/calendar.rst:313 ../Doc/library/time.rst:681 +msgid "Module :mod:`datetime`" +msgstr "" + +#: ../Doc/library/calendar.rst:312 +msgid "" +"Object-oriented interface to dates and times with similar functionality to " +"the :mod:`time` module." +msgstr "" + +#: ../Doc/library/calendar.rst:315 ../Doc/library/datetime.rst:70 +msgid "Module :mod:`time`" +msgstr "" + +#: ../Doc/library/calendar.rst:316 +msgid "Low-level time related functions." +msgstr "" + +#: ../Doc/library/cgi.rst:2 +msgid ":mod:`cgi` --- Common Gateway Interface support" +msgstr "" + +#: ../Doc/library/cgi.rst:7 +msgid "**Source code:** :source:`Lib/cgi.py`" +msgstr "" + +#: ../Doc/library/cgi.rst:19 +msgid "Support module for Common Gateway Interface (CGI) scripts." +msgstr "" + +#: ../Doc/library/cgi.rst:21 +msgid "" +"This module defines a number of utilities for use by CGI scripts written in " +"Python." +msgstr "" + +#: ../Doc/library/cgi.rst:26 ../Doc/library/importlib.rst:17 +#: ../Doc/library/intro.rst:5 ../Doc/library/multiprocessing.rst:12 +#: ../Doc/library/selectors.rst:14 ../Doc/library/sqlite3.rst:766 +#: ../Doc/library/turtle.rst:20 +msgid "Introduction" +msgstr "" + +#: ../Doc/library/cgi.rst:30 +msgid "" +"A CGI script is invoked by an HTTP server, usually to process user input " +"submitted through an HTML ``
`` or ```` element." +msgstr "" + +#: ../Doc/library/cgi.rst:33 +msgid "" +"Most often, CGI scripts live in the server's special :file:`cgi-bin` " +"directory. The HTTP server places all sorts of information about the request " +"(such as the client's hostname, the requested URL, the query string, and " +"lots of other goodies) in the script's shell environment, executes the " +"script, and sends the script's output back to the client." +msgstr "" + +#: ../Doc/library/cgi.rst:39 +msgid "" +"The script's input is connected to the client too, and sometimes the form " +"data is read this way; at other times the form data is passed via the " +"\"query string\" part of the URL. This module is intended to take care of " +"the different cases and provide a simpler interface to the Python script. " +"It also provides a number of utilities that help in debugging scripts, and " +"the latest addition is support for file uploads from a form (if your browser " +"supports it)." +msgstr "" + +#: ../Doc/library/cgi.rst:46 +msgid "" +"The output of a CGI script should consist of two sections, separated by a " +"blank line. The first section contains a number of headers, telling the " +"client what kind of data is following. Python code to generate a minimal " +"header section looks like this::" +msgstr "" + +#: ../Doc/library/cgi.rst:54 +msgid "" +"The second section is usually HTML, which allows the client software to " +"display nicely formatted text with header, in-line images, etc. Here's " +"Python code that prints a simple piece of HTML::" +msgstr "" + +#: ../Doc/library/cgi.rst:66 +msgid "Using the cgi module" +msgstr "" + +#: ../Doc/library/cgi.rst:68 +msgid "Begin by writing ``import cgi``." +msgstr "" + +#: ../Doc/library/cgi.rst:70 +msgid "When you write a new script, consider adding these lines::" +msgstr "" + +#: ../Doc/library/cgi.rst:75 +msgid "" +"This activates a special exception handler that will display detailed " +"reports in the Web browser if any errors occur. If you'd rather not show " +"the guts of your program to users of your script, you can have the reports " +"saved to files instead, with code like this::" +msgstr "" + +#: ../Doc/library/cgi.rst:83 +msgid "" +"It's very helpful to use this feature during script development. The reports " +"produced by :mod:`cgitb` provide information that can save you a lot of time " +"in tracking down bugs. You can always remove the ``cgitb`` line later when " +"you have tested your script and are confident that it works correctly." +msgstr "" + +#: ../Doc/library/cgi.rst:88 +msgid "" +"To get at submitted form data, use the :class:`FieldStorage` class. If the " +"form contains non-ASCII characters, use the *encoding* keyword parameter set " +"to the value of the encoding defined for the document. It is usually " +"contained in the META tag in the HEAD section of the HTML document or by " +"the :mailheader:`Content-Type` header). This reads the form contents from " +"the standard input or the environment (depending on the value of various " +"environment variables set according to the CGI standard). Since it may " +"consume standard input, it should be instantiated only once." +msgstr "" + +#: ../Doc/library/cgi.rst:97 +msgid "" +"The :class:`FieldStorage` instance can be indexed like a Python dictionary. " +"It allows membership testing with the :keyword:`in` operator, and also " +"supports the standard dictionary method :meth:`~dict.keys` and the built-in " +"function :func:`len`. Form fields containing empty strings are ignored and " +"do not appear in the dictionary; to keep such values, provide a true value " +"for the optional *keep_blank_values* keyword parameter when creating the :" +"class:`FieldStorage` instance." +msgstr "" + +#: ../Doc/library/cgi.rst:105 +msgid "" +"For instance, the following code (which assumes that the :mailheader:" +"`Content-Type` header and blank line have already been printed) checks that " +"the fields ``name`` and ``addr`` are both set to a non-empty string::" +msgstr "" + +#: ../Doc/library/cgi.rst:119 +msgid "" +"Here the fields, accessed through ``form[key]``, are themselves instances " +"of :class:`FieldStorage` (or :class:`MiniFieldStorage`, depending on the " +"form encoding). The :attr:`~FieldStorage.value` attribute of the instance " +"yields the string value of the field. The :meth:`~FieldStorage.getvalue` " +"method returns this string value directly; it also accepts an optional " +"second argument as a default to return if the requested key is not present." +msgstr "" + +#: ../Doc/library/cgi.rst:126 +msgid "" +"If the submitted form data contains more than one field with the same name, " +"the object retrieved by ``form[key]`` is not a :class:`FieldStorage` or :" +"class:`MiniFieldStorage` instance but a list of such instances. Similarly, " +"in this situation, ``form.getvalue(key)`` would return a list of strings. If " +"you expect this possibility (when your HTML form contains multiple fields " +"with the same name), use the :meth:`~FieldStorage.getlist` method, which " +"always returns a list of values (so that you do not need to special-case the " +"single item case). For example, this code concatenates any number of " +"username fields, separated by commas::" +msgstr "" + +#: ../Doc/library/cgi.rst:139 +msgid "" +"If a field represents an uploaded file, accessing the value via the :attr:" +"`~FieldStorage.value` attribute or the :meth:`~FieldStorage.getvalue` method " +"reads the entire file in memory as bytes. This may not be what you want. " +"You can test for an uploaded file by testing either the :attr:`~FieldStorage." +"filename` attribute or the :attr:`~FieldStorage.file` attribute. You can " +"then read the data from the :attr:`!file` attribute before it is " +"automatically closed as part of the garbage collection of the :class:" +"`FieldStorage` instance (the :func:`~io.RawIOBase.read` and :func:`~io." +"IOBase.readline` methods will return bytes)::" +msgstr "" + +#: ../Doc/library/cgi.rst:159 +msgid "" +":class:`FieldStorage` objects also support being used in a :keyword:`with` " +"statement, which will automatically close them when done." +msgstr "" + +#: ../Doc/library/cgi.rst:162 +msgid "" +"If an error is encountered when obtaining the contents of an uploaded file " +"(for example, when the user interrupts the form submission by clicking on a " +"Back or Cancel button) the :attr:`~FieldStorage.done` attribute of the " +"object for the field will be set to the value -1." +msgstr "" + +#: ../Doc/library/cgi.rst:167 +msgid "" +"The file upload draft standard entertains the possibility of uploading " +"multiple files from one field (using a recursive :mimetype:`multipart/\\*` " +"encoding). When this occurs, the item will be a dictionary-like :class:" +"`FieldStorage` item. This can be determined by testing its :attr:`!type` " +"attribute, which should be :mimetype:`multipart/form-data` (or perhaps " +"another MIME type matching :mimetype:`multipart/\\*`). In this case, it can " +"be iterated over recursively just like the top-level form object." +msgstr "" + +#: ../Doc/library/cgi.rst:175 +msgid "" +"When a form is submitted in the \"old\" format (as the query string or as a " +"single data part of type :mimetype:`application/x-www-form-urlencoded`), the " +"items will actually be instances of the class :class:`MiniFieldStorage`. In " +"this case, the :attr:`!list`, :attr:`!file`, and :attr:`filename` attributes " +"are always ``None``." +msgstr "" + +#: ../Doc/library/cgi.rst:180 +msgid "" +"A form submitted via POST that also has a query string will contain both :" +"class:`FieldStorage` and :class:`MiniFieldStorage` items." +msgstr "" + +#: ../Doc/library/cgi.rst:183 +msgid "" +"The :attr:`~FieldStorage.file` attribute is automatically closed upon the " +"garbage collection of the creating :class:`FieldStorage` instance." +msgstr "" + +#: ../Doc/library/cgi.rst:187 +msgid "" +"Added support for the context management protocol to the :class:" +"`FieldStorage` class." +msgstr "" + +#: ../Doc/library/cgi.rst:193 +msgid "Higher Level Interface" +msgstr "" + +#: ../Doc/library/cgi.rst:195 +msgid "" +"The previous section explains how to read CGI form data using the :class:" +"`FieldStorage` class. This section describes a higher level interface which " +"was added to this class to allow one to do it in a more readable and " +"intuitive way. The interface doesn't make the techniques described in " +"previous sections obsolete --- they are still useful to process file uploads " +"efficiently, for example." +msgstr "" + +#: ../Doc/library/cgi.rst:204 +msgid "" +"The interface consists of two simple methods. Using the methods you can " +"process form data in a generic way, without the need to worry whether only " +"one or more values were posted under one name." +msgstr "" + +#: ../Doc/library/cgi.rst:208 +msgid "" +"In the previous section, you learned to write following code anytime you " +"expected a user to post more than one value under one name::" +msgstr "" + +#: ../Doc/library/cgi.rst:217 +msgid "" +"This situation is common for example when a form contains a group of " +"multiple checkboxes with the same name::" +msgstr "" + +#: ../Doc/library/cgi.rst:223 +msgid "" +"In most situations, however, there's only one form control with a particular " +"name in a form and then you expect and need only one value associated with " +"this name. So you write a script containing for example this code::" +msgstr "" + +#: ../Doc/library/cgi.rst:229 +msgid "" +"The problem with the code is that you should never expect that a client will " +"provide valid input to your scripts. For example, if a curious user appends " +"another ``user=foo`` pair to the query string, then the script would crash, " +"because in this situation the ``getvalue(\"user\")`` method call returns a " +"list instead of a string. Calling the :meth:`~str.upper` method on a list " +"is not valid (since lists do not have a method of this name) and results in " +"an :exc:`AttributeError` exception." +msgstr "" + +#: ../Doc/library/cgi.rst:237 +msgid "" +"Therefore, the appropriate way to read form data values was to always use " +"the code which checks whether the obtained value is a single value or a list " +"of values. That's annoying and leads to less readable scripts." +msgstr "" + +#: ../Doc/library/cgi.rst:241 +msgid "" +"A more convenient approach is to use the methods :meth:`~FieldStorage." +"getfirst` and :meth:`~FieldStorage.getlist` provided by this higher level " +"interface." +msgstr "" + +#: ../Doc/library/cgi.rst:247 +msgid "" +"This method always returns only one value associated with form field *name*. " +"The method returns only the first value in case that more values were posted " +"under such name. Please note that the order in which the values are " +"received may vary from browser to browser and should not be counted on. " +"[#]_ If no such form field or value exists then the method returns the " +"value specified by the optional parameter *default*. This parameter " +"defaults to ``None`` if not specified." +msgstr "" + +#: ../Doc/library/cgi.rst:258 +msgid "" +"This method always returns a list of values associated with form field " +"*name*. The method returns an empty list if no such form field or value " +"exists for *name*. It returns a list consisting of one item if only one " +"such value exists." +msgstr "" + +#: ../Doc/library/cgi.rst:262 +msgid "Using these methods you can write nice compact code::" +msgstr "" + +#: ../Doc/library/cgi.rst:274 ../Doc/library/curses.rst:58 +#: ../Doc/library/curses.panel.rst:19 ../Doc/library/importlib.rst:78 +#: ../Doc/library/socket.rst:410 ../Doc/library/stdtypes.rst:4393 +#: ../Doc/library/tracemalloc.rst:259 ../Doc/library/winreg.rst:26 +#: ../Doc/library/xml.etree.elementtree.rst:461 +msgid "Functions" +msgstr "" + +#: ../Doc/library/cgi.rst:276 +msgid "" +"These are useful if you want more control, or if you want to employ some of " +"the algorithms implemented in this module in other circumstances." +msgstr "" + +#: ../Doc/library/cgi.rst:282 +msgid "" +"Parse a query in the environment or from a file (the file defaults to ``sys." +"stdin``). The *keep_blank_values* and *strict_parsing* parameters are " +"passed to :func:`urllib.parse.parse_qs` unchanged." +msgstr "" + +#: ../Doc/library/cgi.rst:289 +msgid "" +"This function is deprecated in this module. Use :func:`urllib.parse." +"parse_qs` instead. It is maintained here only for backward compatibility." +msgstr "" + +#: ../Doc/library/cgi.rst:294 +msgid "" +"This function is deprecated in this module. Use :func:`urllib.parse." +"parse_qsl` instead. It is maintained here only for backward compatibility." +msgstr "" + +#: ../Doc/library/cgi.rst:299 +msgid "" +"Parse input of type :mimetype:`multipart/form-data` (for file uploads). " +"Arguments are *fp* for the input file and *pdict* for a dictionary " +"containing other parameters in the :mailheader:`Content-Type` header." +msgstr "" + +#: ../Doc/library/cgi.rst:303 +msgid "" +"Returns a dictionary just like :func:`urllib.parse.parse_qs` keys are the " +"field names, each value is a list of values for that field. This is easy to " +"use but not much good if you are expecting megabytes to be uploaded --- in " +"that case, use the :class:`FieldStorage` class instead which is much more " +"flexible." +msgstr "" + +#: ../Doc/library/cgi.rst:308 +msgid "" +"Note that this does not parse nested multipart parts --- use :class:" +"`FieldStorage` for that." +msgstr "" + +#: ../Doc/library/cgi.rst:314 +msgid "" +"Parse a MIME header (such as :mailheader:`Content-Type`) into a main value " +"and a dictionary of parameters." +msgstr "" + +#: ../Doc/library/cgi.rst:320 +msgid "" +"Robust test CGI script, usable as main program. Writes minimal HTTP headers " +"and formats all information provided to the script in HTML form." +msgstr "" + +#: ../Doc/library/cgi.rst:326 +msgid "Format the shell environment in HTML." +msgstr "" + +#: ../Doc/library/cgi.rst:331 +msgid "Format a form in HTML." +msgstr "" + +#: ../Doc/library/cgi.rst:336 +msgid "Format the current directory in HTML." +msgstr "" + +#: ../Doc/library/cgi.rst:341 +msgid "Print a list of useful (used by CGI) environment variables in HTML." +msgstr "" + +#: ../Doc/library/cgi.rst:346 +msgid "" +"Convert the characters ``'&'``, ``'<'`` and ``'>'`` in string *s* to HTML-" +"safe sequences. Use this if you need to display text that might contain " +"such characters in HTML. If the optional flag *quote* is true, the " +"quotation mark character (``\"``) is also translated; this helps for " +"inclusion in an HTML attribute value delimited by double quotes, as in ````. Note that single quotes are never translated." +msgstr "" + +#: ../Doc/library/cgi.rst:353 +msgid "" +"This function is unsafe because *quote* is false by default, and therefore " +"deprecated. Use :func:`html.escape` instead." +msgstr "" + +#: ../Doc/library/cgi.rst:361 +msgid "Caring about security" +msgstr "" + +#: ../Doc/library/cgi.rst:365 +msgid "" +"There's one important rule: if you invoke an external program (via the :func:" +"`os.system` or :func:`os.popen` functions. or others with similar " +"functionality), make very sure you don't pass arbitrary strings received " +"from the client to the shell. This is a well-known security hole whereby " +"clever hackers anywhere on the Web can exploit a gullible CGI script to " +"invoke arbitrary shell commands. Even parts of the URL or field names " +"cannot be trusted, since the request doesn't have to come from your form!" +msgstr "" + +#: ../Doc/library/cgi.rst:373 +msgid "" +"To be on the safe side, if you must pass a string gotten from a form to a " +"shell command, you should make sure the string contains only alphanumeric " +"characters, dashes, underscores, and periods." +msgstr "" + +#: ../Doc/library/cgi.rst:379 +msgid "Installing your CGI script on a Unix system" +msgstr "" + +#: ../Doc/library/cgi.rst:381 +msgid "" +"Read the documentation for your HTTP server and check with your local system " +"administrator to find the directory where CGI scripts should be installed; " +"usually this is in a directory :file:`cgi-bin` in the server tree." +msgstr "" + +#: ../Doc/library/cgi.rst:385 +msgid "" +"Make sure that your script is readable and executable by \"others\"; the " +"Unix file mode should be ``0o755`` octal (use ``chmod 0755 filename``). " +"Make sure that the first line of the script contains ``#!`` starting in " +"column 1 followed by the pathname of the Python interpreter, for instance::" +msgstr "" + +#: ../Doc/library/cgi.rst:392 +msgid "" +"Make sure the Python interpreter exists and is executable by \"others\"." +msgstr "" + +#: ../Doc/library/cgi.rst:394 +msgid "" +"Make sure that any files your script needs to read or write are readable or " +"writable, respectively, by \"others\" --- their mode should be ``0o644`` for " +"readable and ``0o666`` for writable. This is because, for security reasons, " +"the HTTP server executes your script as user \"nobody\", without any special " +"privileges. It can only read (write, execute) files that everybody can read " +"(write, execute). The current directory at execution time is also different " +"(it is usually the server's cgi-bin directory) and the set of environment " +"variables is also different from what you get when you log in. In " +"particular, don't count on the shell's search path for executables (:envvar:" +"`PATH`) or the Python module search path (:envvar:`PYTHONPATH`) to be set to " +"anything interesting." +msgstr "" + +#: ../Doc/library/cgi.rst:405 +msgid "" +"If you need to load modules from a directory which is not on Python's " +"default module search path, you can change the path in your script, before " +"importing other modules. For example::" +msgstr "" + +#: ../Doc/library/cgi.rst:413 +msgid "(This way, the directory inserted last will be searched first!)" +msgstr "" + +#: ../Doc/library/cgi.rst:415 +msgid "" +"Instructions for non-Unix systems will vary; check your HTTP server's " +"documentation (it will usually have a section on CGI scripts)." +msgstr "" + +#: ../Doc/library/cgi.rst:420 +msgid "Testing your CGI script" +msgstr "" + +#: ../Doc/library/cgi.rst:422 +msgid "" +"Unfortunately, a CGI script will generally not run when you try it from the " +"command line, and a script that works perfectly from the command line may " +"fail mysteriously when run from the server. There's one reason why you " +"should still test your script from the command line: if it contains a syntax " +"error, the Python interpreter won't execute it at all, and the HTTP server " +"will most likely send a cryptic error to the client." +msgstr "" + +#: ../Doc/library/cgi.rst:429 +msgid "" +"Assuming your script has no syntax errors, yet it does not work, you have no " +"choice but to read the next section." +msgstr "" + +#: ../Doc/library/cgi.rst:434 +msgid "Debugging CGI scripts" +msgstr "" + +#: ../Doc/library/cgi.rst:438 +msgid "" +"First of all, check for trivial installation errors --- reading the section " +"above on installing your CGI script carefully can save you a lot of time. " +"If you wonder whether you have understood the installation procedure " +"correctly, try installing a copy of this module file (:file:`cgi.py`) as a " +"CGI script. When invoked as a script, the file will dump its environment " +"and the contents of the form in HTML form. Give it the right mode etc, and " +"send it a request. If it's installed in the standard :file:`cgi-bin` " +"directory, it should be possible to send it a request by entering a URL into " +"your browser of the form:" +msgstr "" + +#: ../Doc/library/cgi.rst:451 +msgid "" +"If this gives an error of type 404, the server cannot find the script -- " +"perhaps you need to install it in a different directory. If it gives " +"another error, there's an installation problem that you should fix before " +"trying to go any further. If you get a nicely formatted listing of the " +"environment and form content (in this example, the fields should be listed " +"as \"addr\" with value \"At Home\" and \"name\" with value \"Joe Blow\"), " +"the :file:`cgi.py` script has been installed correctly. If you follow the " +"same procedure for your own script, you should now be able to debug it." +msgstr "" + +#: ../Doc/library/cgi.rst:460 +msgid "" +"The next step could be to call the :mod:`cgi` module's :func:`test` function " +"from your script: replace its main code with the single statement ::" +msgstr "" + +#: ../Doc/library/cgi.rst:465 +msgid "" +"This should produce the same results as those gotten from installing the :" +"file:`cgi.py` file itself." +msgstr "" + +#: ../Doc/library/cgi.rst:468 +msgid "" +"When an ordinary Python script raises an unhandled exception (for whatever " +"reason: of a typo in a module name, a file that can't be opened, etc.), the " +"Python interpreter prints a nice traceback and exits. While the Python " +"interpreter will still do this when your CGI script raises an exception, " +"most likely the traceback will end up in one of the HTTP server's log files, " +"or be discarded altogether." +msgstr "" + +#: ../Doc/library/cgi.rst:475 +msgid "" +"Fortunately, once you have managed to get your script to execute *some* " +"code, you can easily send tracebacks to the Web browser using the :mod:" +"`cgitb` module. If you haven't done so already, just add the lines::" +msgstr "" + +#: ../Doc/library/cgi.rst:482 +msgid "" +"to the top of your script. Then try running it again; when a problem " +"occurs, you should see a detailed report that will likely make apparent the " +"cause of the crash." +msgstr "" + +#: ../Doc/library/cgi.rst:486 +msgid "" +"If you suspect that there may be a problem in importing the :mod:`cgitb` " +"module, you can use an even more robust approach (which only uses built-in " +"modules)::" +msgstr "" + +#: ../Doc/library/cgi.rst:495 +msgid "" +"This relies on the Python interpreter to print the traceback. The content " +"type of the output is set to plain text, which disables all HTML " +"processing. If your script works, the raw HTML will be displayed by your " +"client. If it raises an exception, most likely after the first two lines " +"have been printed, a traceback will be displayed. Because no HTML " +"interpretation is going on, the traceback will be readable." +msgstr "" + +#: ../Doc/library/cgi.rst:504 +msgid "Common problems and solutions" +msgstr "" + +#: ../Doc/library/cgi.rst:506 +msgid "" +"Most HTTP servers buffer the output from CGI scripts until the script is " +"completed. This means that it is not possible to display a progress report " +"on the client's display while the script is running." +msgstr "" + +#: ../Doc/library/cgi.rst:510 +msgid "Check the installation instructions above." +msgstr "" + +#: ../Doc/library/cgi.rst:512 +msgid "" +"Check the HTTP server's log files. (``tail -f logfile`` in a separate " +"window may be useful!)" +msgstr "" + +#: ../Doc/library/cgi.rst:515 +msgid "" +"Always check a script for syntax errors first, by doing something like " +"``python script.py``." +msgstr "" + +#: ../Doc/library/cgi.rst:518 +msgid "" +"If your script does not have any syntax errors, try adding ``import cgitb; " +"cgitb.enable()`` to the top of the script." +msgstr "" + +#: ../Doc/library/cgi.rst:521 +msgid "" +"When invoking external programs, make sure they can be found. Usually, this " +"means using absolute path names --- :envvar:`PATH` is usually not set to a " +"very useful value in a CGI script." +msgstr "" + +#: ../Doc/library/cgi.rst:525 +msgid "" +"When reading or writing external files, make sure they can be read or " +"written by the userid under which your CGI script will be running: this is " +"typically the userid under which the web server is running, or some " +"explicitly specified userid for a web server's ``suexec`` feature." +msgstr "" + +#: ../Doc/library/cgi.rst:530 +msgid "" +"Don't try to give a CGI script a set-uid mode. This doesn't work on most " +"systems, and is a security liability as well." +msgstr "" + +#: ../Doc/library/cgi.rst:535 +msgid "" +"Note that some recent versions of the HTML specification do state what order " +"the field values should be supplied in, but knowing whether a request was " +"received from a conforming browser, or even from a browser at all, is " +"tedious and error-prone." +msgstr "" + +#: ../Doc/library/cgitb.rst:2 +msgid ":mod:`cgitb` --- Traceback manager for CGI scripts" +msgstr "" + +#: ../Doc/library/cgitb.rst:10 +msgid "**Source code:** :source:`Lib/cgitb.py`" +msgstr "" + +#: ../Doc/library/cgitb.rst:20 +msgid "" +"The :mod:`cgitb` module provides a special exception handler for Python " +"scripts. (Its name is a bit misleading. It was originally designed to " +"display extensive traceback information in HTML for CGI scripts. It was " +"later generalized to also display this information in plain text.) After " +"this module is activated, if an uncaught exception occurs, a detailed, " +"formatted report will be displayed. The report includes a traceback showing " +"excerpts of the source code for each level, as well as the values of the " +"arguments and local variables to currently running functions, to help you " +"debug the problem. Optionally, you can save this information to a file " +"instead of sending it to the browser." +msgstr "" + +#: ../Doc/library/cgitb.rst:30 +msgid "To enable this feature, simply add this to the top of your CGI script::" +msgstr "" + +#: ../Doc/library/cgitb.rst:35 +msgid "" +"The options to the :func:`enable` function control whether the report is " +"displayed in the browser and whether the report is logged to a file for " +"later analysis." +msgstr "" + +#: ../Doc/library/cgitb.rst:44 +msgid "" +"This function causes the :mod:`cgitb` module to take over the interpreter's " +"default handling for exceptions by setting the value of :attr:`sys." +"excepthook`." +msgstr "" + +#: ../Doc/library/cgitb.rst:47 +msgid "" +"The optional argument *display* defaults to ``1`` and can be set to ``0`` to " +"suppress sending the traceback to the browser. If the argument *logdir* is " +"present, the traceback reports are written to files. The value of *logdir* " +"should be a directory where these files will be placed. The optional " +"argument *context* is the number of lines of context to display around the " +"current line of source code in the traceback; this defaults to ``5``. If the " +"optional argument *format* is ``\"html\"``, the output is formatted as " +"HTML. Any other value forces plain text output. The default value is ``" +"\"html\"``." +msgstr "" + +#: ../Doc/library/cgitb.rst:59 +msgid "" +"This function handles an exception using the default settings (that is, show " +"a report in the browser, but don't log to a file). This can be used when " +"you've caught an exception and want to report it using :mod:`cgitb`. The " +"optional *info* argument should be a 3-tuple containing an exception type, " +"exception value, and traceback object, exactly like the tuple returned by :" +"func:`sys.exc_info`. If the *info* argument is not supplied, the current " +"exception is obtained from :func:`sys.exc_info`." +msgstr "" + +#: ../Doc/library/chunk.rst:2 +msgid ":mod:`chunk` --- Read IFF chunked data" +msgstr "" + +#: ../Doc/library/chunk.rst:10 +msgid "**Source code:** :source:`Lib/chunk.py`" +msgstr "" + +#: ../Doc/library/chunk.rst:21 +msgid "" +"This module provides an interface for reading files that use EA IFF 85 " +"chunks. [#]_ This format is used in at least the Audio Interchange File " +"Format (AIFF/AIFF-C) and the Real Media File Format (RMFF). The WAVE audio " +"file format is closely related and can also be read using this module." +msgstr "" + +#: ../Doc/library/chunk.rst:26 +msgid "A chunk has the following structure:" +msgstr "" + +#: ../Doc/library/chunk.rst:29 +msgid "Offset" +msgstr "" + +#: ../Doc/library/chunk.rst:29 +msgid "Length" +msgstr "" + +#: ../Doc/library/chunk.rst:29 ../Doc/library/sunau.rst:21 +msgid "Contents" +msgstr "" + +#: ../Doc/library/chunk.rst:31 ../Doc/library/grp.rst:20 +#: ../Doc/library/logging.rst:351 ../Doc/library/pwd.rst:20 +#: ../Doc/library/spwd.rst:23 ../Doc/library/time.rst:538 +#: ../Doc/library/tkinter.rst:432 ../Doc/library/urllib.parse.rst:94 +#: ../Doc/library/urllib.parse.rst:215 ../Doc/library/urllib.parse.rst:300 +msgid "0" +msgstr "" + +#: ../Doc/library/chunk.rst:31 +msgid "Chunk ID" +msgstr "" + +#: ../Doc/library/chunk.rst:33 +msgid "Size of chunk in big-endian byte order, not including the header" +msgstr "" + +#: ../Doc/library/chunk.rst:37 +msgid "*n*" +msgstr "" + +#: ../Doc/library/chunk.rst:37 +msgid "Data bytes, where *n* is the size given in the preceding field" +msgstr "" + +#: ../Doc/library/chunk.rst:41 +msgid "8 + *n*" +msgstr "" + +#: ../Doc/library/chunk.rst:41 +msgid "0 or 1" +msgstr "" + +#: ../Doc/library/chunk.rst:41 +msgid "Pad byte needed if *n* is odd and chunk alignment is used" +msgstr "" + +#: ../Doc/library/chunk.rst:45 +msgid "The ID is a 4-byte string which identifies the type of chunk." +msgstr "" + +#: ../Doc/library/chunk.rst:47 +msgid "" +"The size field (a 32-bit value, encoded using big-endian byte order) gives " +"the size of the chunk data, not including the 8-byte header." +msgstr "" + +#: ../Doc/library/chunk.rst:50 +msgid "" +"Usually an IFF-type file consists of one or more chunks. The proposed usage " +"of the :class:`Chunk` class defined here is to instantiate an instance at " +"the start of each chunk and read from the instance until it reaches the end, " +"after which a new instance can be instantiated. At the end of the file, " +"creating a new instance will fail with an :exc:`EOFError` exception." +msgstr "" + +#: ../Doc/library/chunk.rst:59 +msgid "" +"Class which represents a chunk. The *file* argument is expected to be a " +"file-like object. An instance of this class is specifically allowed. The " +"only method that is needed is :meth:`~io.IOBase.read`. If the methods :meth:" +"`~io.IOBase.seek` and :meth:`~io.IOBase.tell` are present and don't raise an " +"exception, they are also used. If these methods are present and raise an " +"exception, they are expected to not have altered the object. If the " +"optional argument *align* is true, chunks are assumed to be aligned on 2-" +"byte boundaries. If *align* is false, no alignment is assumed. The default " +"value is true. If the optional argument *bigendian* is false, the chunk " +"size is assumed to be in little-endian order. This is needed for WAVE audio " +"files. The default value is true. If the optional argument *inclheader* is " +"true, the size given in the chunk header includes the size of the header. " +"The default value is false." +msgstr "" + +#: ../Doc/library/chunk.rst:73 +msgid "A :class:`Chunk` object supports the following methods:" +msgstr "" + +#: ../Doc/library/chunk.rst:78 +msgid "" +"Returns the name (ID) of the chunk. This is the first 4 bytes of the chunk." +msgstr "" + +#: ../Doc/library/chunk.rst:84 +msgid "Returns the size of the chunk." +msgstr "" + +#: ../Doc/library/chunk.rst:89 +msgid "" +"Close and skip to the end of the chunk. This does not close the underlying " +"file." +msgstr "" + +#: ../Doc/library/chunk.rst:92 +msgid "" +"The remaining methods will raise :exc:`OSError` if called after the :meth:" +"`close` method has been called. Before Python 3.3, they used to raise :exc:" +"`IOError`, now an alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/chunk.rst:99 +msgid "Returns ``False``." +msgstr "" + +#: ../Doc/library/chunk.rst:104 +msgid "" +"Set the chunk's current position. The *whence* argument is optional and " +"defaults to ``0`` (absolute file positioning); other values are ``1`` (seek " +"relative to the current position) and ``2`` (seek relative to the file's " +"end). There is no return value. If the underlying file does not allow seek, " +"only forward seeks are allowed." +msgstr "" + +#: ../Doc/library/chunk.rst:113 +msgid "Return the current position into the chunk." +msgstr "" + +#: ../Doc/library/chunk.rst:118 +msgid "" +"Read at most *size* bytes from the chunk (less if the read hits the end of " +"the chunk before obtaining *size* bytes). If the *size* argument is " +"negative or omitted, read all data until the end of the chunk. An empty " +"bytes object is returned when the end of the chunk is encountered " +"immediately." +msgstr "" + +#: ../Doc/library/chunk.rst:127 +msgid "" +"Skip to the end of the chunk. All further calls to :meth:`read` for the " +"chunk will return ``b''``. If you are not interested in the contents of the " +"chunk, this method should be called so that the file points to the start of " +"the next chunk." +msgstr "" + +#: ../Doc/library/chunk.rst:135 +msgid "" +"\"EA IFF 85\" Standard for Interchange Format Files, Jerry Morrison, " +"Electronic Arts, January 1985." +msgstr "" + +#: ../Doc/library/cmath.rst:2 +msgid ":mod:`cmath` --- Mathematical functions for complex numbers" +msgstr "" + +#: ../Doc/library/cmath.rst:9 +msgid "" +"This module is always available. It provides access to mathematical " +"functions for complex numbers. The functions in this module accept " +"integers, floating-point numbers or complex numbers as arguments. They will " +"also accept any Python object that has either a :meth:`__complex__` or a :" +"meth:`__float__` method: these methods are used to convert the object to a " +"complex or floating-point number, respectively, and the function is then " +"applied to the result of the conversion." +msgstr "" + +#: ../Doc/library/cmath.rst:19 +msgid "" +"On platforms with hardware and system-level support for signed zeros, " +"functions involving branch cuts are continuous on *both* sides of the branch " +"cut: the sign of the zero distinguishes one side of the branch cut from the " +"other. On platforms that do not support signed zeros the continuity is as " +"specified below." +msgstr "" + +#: ../Doc/library/cmath.rst:27 +msgid "Conversions to and from polar coordinates" +msgstr "" + +#: ../Doc/library/cmath.rst:29 +msgid "" +"A Python complex number ``z`` is stored internally using *rectangular* or " +"*Cartesian* coordinates. It is completely determined by its *real part* ``z." +"real`` and its *imaginary part* ``z.imag``. In other words::" +msgstr "" + +#: ../Doc/library/cmath.rst:36 +msgid "" +"*Polar coordinates* give an alternative way to represent a complex number. " +"In polar coordinates, a complex number *z* is defined by the modulus *r* and " +"the phase angle *phi*. The modulus *r* is the distance from *z* to the " +"origin, while the phase *phi* is the counterclockwise angle, measured in " +"radians, from the positive x-axis to the line segment that joins the origin " +"to *z*." +msgstr "" + +#: ../Doc/library/cmath.rst:43 +msgid "" +"The following functions can be used to convert from the native rectangular " +"coordinates to polar coordinates and back." +msgstr "" + +#: ../Doc/library/cmath.rst:48 +msgid "" +"Return the phase of *x* (also known as the *argument* of *x*), as a float. " +"``phase(x)`` is equivalent to ``math.atan2(x.imag, x.real)``. The result " +"lies in the range [-π, π], and the branch cut for this operation lies along " +"the negative real axis, continuous from above. On systems with support for " +"signed zeros (which includes most systems in current use), this means that " +"the sign of the result is the same as the sign of ``x.imag``, even when ``x." +"imag`` is zero::" +msgstr "" + +#: ../Doc/library/cmath.rst:65 +msgid "" +"The modulus (absolute value) of a complex number *x* can be computed using " +"the built-in :func:`abs` function. There is no separate :mod:`cmath` module " +"function for this operation." +msgstr "" + +#: ../Doc/library/cmath.rst:72 +msgid "" +"Return the representation of *x* in polar coordinates. Returns a pair ``(r, " +"phi)`` where *r* is the modulus of *x* and phi is the phase of *x*. " +"``polar(x)`` is equivalent to ``(abs(x), phase(x))``." +msgstr "" + +#: ../Doc/library/cmath.rst:80 +msgid "" +"Return the complex number *x* with polar coordinates *r* and *phi*. " +"Equivalent to ``r * (math.cos(phi) + math.sin(phi)*1j)``." +msgstr "" + +#: ../Doc/library/cmath.rst:85 ../Doc/library/math.rst:198 +msgid "Power and logarithmic functions" +msgstr "" + +#: ../Doc/library/cmath.rst:89 +msgid "Return the exponential value ``e**x``." +msgstr "" + +#: ../Doc/library/cmath.rst:94 +msgid "" +"Returns the logarithm of *x* to the given *base*. If the *base* is not " +"specified, returns the natural logarithm of *x*. There is one branch cut, " +"from 0 along the negative real axis to -∞, continuous from above." +msgstr "" + +#: ../Doc/library/cmath.rst:101 +msgid "" +"Return the base-10 logarithm of *x*. This has the same branch cut as :func:" +"`log`." +msgstr "" + +#: ../Doc/library/cmath.rst:107 +msgid "" +"Return the square root of *x*. This has the same branch cut as :func:`log`." +msgstr "" + +#: ../Doc/library/cmath.rst:111 ../Doc/library/math.rst:273 +msgid "Trigonometric functions" +msgstr "" + +#: ../Doc/library/cmath.rst:115 +msgid "" +"Return the arc cosine of *x*. There are two branch cuts: One extends right " +"from 1 along the real axis to ∞, continuous from below. The other extends " +"left from -1 along the real axis to -∞, continuous from above." +msgstr "" + +#: ../Doc/library/cmath.rst:122 +msgid "" +"Return the arc sine of *x*. This has the same branch cuts as :func:`acos`." +msgstr "" + +#: ../Doc/library/cmath.rst:127 +msgid "" +"Return the arc tangent of *x*. There are two branch cuts: One extends from " +"``1j`` along the imaginary axis to ``∞j``, continuous from the right. The " +"other extends from ``-1j`` along the imaginary axis to ``-∞j``, continuous " +"from the left." +msgstr "" + +#: ../Doc/library/cmath.rst:135 +msgid "Return the cosine of *x*." +msgstr "" + +#: ../Doc/library/cmath.rst:140 +msgid "Return the sine of *x*." +msgstr "" + +#: ../Doc/library/cmath.rst:145 +msgid "Return the tangent of *x*." +msgstr "" + +#: ../Doc/library/cmath.rst:149 ../Doc/library/math.rst:335 +msgid "Hyperbolic functions" +msgstr "" + +#: ../Doc/library/cmath.rst:153 +msgid "" +"Return the inverse hyperbolic cosine of *x*. There is one branch cut, " +"extending left from 1 along the real axis to -∞, continuous from above." +msgstr "" + +#: ../Doc/library/cmath.rst:159 +msgid "" +"Return the inverse hyperbolic sine of *x*. There are two branch cuts: One " +"extends from ``1j`` along the imaginary axis to ``∞j``, continuous from the " +"right. The other extends from ``-1j`` along the imaginary axis to ``-∞j``, " +"continuous from the left." +msgstr "" + +#: ../Doc/library/cmath.rst:167 +msgid "" +"Return the inverse hyperbolic tangent of *x*. There are two branch cuts: One " +"extends from ``1`` along the real axis to ``∞``, continuous from below. The " +"other extends from ``-1`` along the real axis to ``-∞``, continuous from " +"above." +msgstr "" + +#: ../Doc/library/cmath.rst:175 ../Doc/library/math.rst:358 +msgid "Return the hyperbolic cosine of *x*." +msgstr "" + +#: ../Doc/library/cmath.rst:180 ../Doc/library/math.rst:363 +msgid "Return the hyperbolic sine of *x*." +msgstr "" + +#: ../Doc/library/cmath.rst:185 ../Doc/library/math.rst:368 +msgid "Return the hyperbolic tangent of *x*." +msgstr "" + +#: ../Doc/library/cmath.rst:189 +msgid "Classification functions" +msgstr "" + +#: ../Doc/library/cmath.rst:193 +msgid "" +"Return ``True`` if both the real and imaginary parts of *x* are finite, and " +"``False`` otherwise." +msgstr "" + +#: ../Doc/library/cmath.rst:201 +msgid "" +"Return ``True`` if either the real or the imaginary part of *x* is an " +"infinity, and ``False`` otherwise." +msgstr "" + +#: ../Doc/library/cmath.rst:207 +msgid "" +"Return ``True`` if either the real or the imaginary part of *x* is a NaN, " +"and ``False`` otherwise." +msgstr "" + +#: ../Doc/library/cmath.rst:213 ../Doc/library/math.rst:117 +msgid "" +"Return ``True`` if the values *a* and *b* are close to each other and " +"``False`` otherwise." +msgstr "" + +#: ../Doc/library/cmath.rst:216 ../Doc/library/math.rst:120 +msgid "" +"Whether or not two values are considered close is determined according to " +"given absolute and relative tolerances." +msgstr "" + +#: ../Doc/library/cmath.rst:219 ../Doc/library/math.rst:123 +msgid "" +"*rel_tol* is the relative tolerance -- it is the maximum allowed difference " +"between *a* and *b*, relative to the larger absolute value of *a* or *b*. " +"For example, to set a tolerance of 5%, pass ``rel_tol=0.05``. The default " +"tolerance is ``1e-09``, which assures that the two values are the same " +"within about 9 decimal digits. *rel_tol* must be greater than zero." +msgstr "" + +#: ../Doc/library/cmath.rst:225 ../Doc/library/math.rst:129 +msgid "" +"*abs_tol* is the minimum absolute tolerance -- useful for comparisons near " +"zero. *abs_tol* must be at least zero." +msgstr "" + +#: ../Doc/library/cmath.rst:228 ../Doc/library/math.rst:132 +msgid "" +"If no errors occur, the result will be: ``abs(a-b) <= max(rel_tol * " +"max(abs(a), abs(b)), abs_tol)``." +msgstr "" + +#: ../Doc/library/cmath.rst:231 ../Doc/library/math.rst:135 +msgid "" +"The IEEE 754 special values of ``NaN``, ``inf``, and ``-inf`` will be " +"handled according to IEEE rules. Specifically, ``NaN`` is not considered " +"close to any other value, including ``NaN``. ``inf`` and ``-inf`` are only " +"considered close to themselves." +msgstr "" + +#: ../Doc/library/cmath.rst:240 ../Doc/library/math.rst:144 +msgid ":pep:`485` -- A function for testing approximate equality" +msgstr "" + +#: ../Doc/library/cmath.rst:249 +msgid "The mathematical constant *π*, as a float." +msgstr "" + +#: ../Doc/library/cmath.rst:254 +msgid "The mathematical constant *e*, as a float." +msgstr "" + +#: ../Doc/library/cmath.rst:258 +msgid "The mathematical constant *τ*, as a float." +msgstr "" + +#: ../Doc/library/cmath.rst:264 +msgid "Floating-point positive infinity. Equivalent to ``float('inf')``." +msgstr "" + +#: ../Doc/library/cmath.rst:270 +msgid "" +"Complex number with zero real part and positive infinity imaginary part. " +"Equivalent to ``complex(0.0, float('inf'))``." +msgstr "" + +#: ../Doc/library/cmath.rst:277 +msgid "" +"A floating-point \"not a number\" (NaN) value. Equivalent to " +"``float('nan')``." +msgstr "" + +#: ../Doc/library/cmath.rst:284 +msgid "" +"Complex number with zero real part and NaN imaginary part. Equivalent to " +"``complex(0.0, float('nan'))``." +msgstr "" + +#: ../Doc/library/cmath.rst:292 +msgid "" +"Note that the selection of functions is similar, but not identical, to that " +"in module :mod:`math`. The reason for having two modules is that some users " +"aren't interested in complex numbers, and perhaps don't even know what they " +"are. They would rather have ``math.sqrt(-1)`` raise an exception than " +"return a complex number. Also note that the functions defined in :mod:" +"`cmath` always return a complex number, even if the answer can be expressed " +"as a real number (in which case the complex number has an imaginary part of " +"zero)." +msgstr "" + +#: ../Doc/library/cmath.rst:300 +msgid "" +"A note on branch cuts: They are curves along which the given function fails " +"to be continuous. They are a necessary feature of many complex functions. " +"It is assumed that if you need to compute with complex functions, you will " +"understand about branch cuts. Consult almost any (not too elementary) book " +"on complex variables for enlightenment. For information of the proper " +"choice of branch cuts for numerical purposes, a good reference should be the " +"following:" +msgstr "" + +#: ../Doc/library/cmath.rst:310 +msgid "" +"Kahan, W: Branch cuts for complex elementary functions; or, Much ado about " +"nothing's sign bit. In Iserles, A., and Powell, M. (eds.), The state of the " +"art in numerical analysis. Clarendon Press (1987) pp165-211." +msgstr "" + +#: ../Doc/library/cmd.rst:2 +msgid ":mod:`cmd` --- Support for line-oriented command interpreters" +msgstr "" + +#: ../Doc/library/cmd.rst:9 +msgid "**Source code:** :source:`Lib/cmd.py`" +msgstr "" + +#: ../Doc/library/cmd.rst:13 +msgid "" +"The :class:`Cmd` class provides a simple framework for writing line-oriented " +"command interpreters. These are often useful for test harnesses, " +"administrative tools, and prototypes that will later be wrapped in a more " +"sophisticated interface." +msgstr "" + +#: ../Doc/library/cmd.rst:20 +msgid "" +"A :class:`Cmd` instance or subclass instance is a line-oriented interpreter " +"framework. There is no good reason to instantiate :class:`Cmd` itself; " +"rather, it's useful as a superclass of an interpreter class you define " +"yourself in order to inherit :class:`Cmd`'s methods and encapsulate action " +"methods." +msgstr "" + +#: ../Doc/library/cmd.rst:25 +msgid "" +"The optional argument *completekey* is the :mod:`readline` name of a " +"completion key; it defaults to :kbd:`Tab`. If *completekey* is not :const:" +"`None` and :mod:`readline` is available, command completion is done " +"automatically." +msgstr "" + +#: ../Doc/library/cmd.rst:29 +msgid "" +"The optional arguments *stdin* and *stdout* specify the input and output " +"file objects that the Cmd instance or subclass instance will use for input " +"and output. If not specified, they will default to :data:`sys.stdin` and :" +"data:`sys.stdout`." +msgstr "" + +#: ../Doc/library/cmd.rst:34 +msgid "" +"If you want a given *stdin* to be used, make sure to set the instance's :" +"attr:`use_rawinput` attribute to ``False``, otherwise *stdin* will be " +"ignored." +msgstr "" + +#: ../Doc/library/cmd.rst:42 +msgid "Cmd Objects" +msgstr "" + +#: ../Doc/library/cmd.rst:44 +msgid "A :class:`Cmd` instance has the following methods:" +msgstr "" + +#: ../Doc/library/cmd.rst:49 +msgid "" +"Repeatedly issue a prompt, accept input, parse an initial prefix off the " +"received input, and dispatch to action methods, passing them the remainder " +"of the line as argument." +msgstr "" + +#: ../Doc/library/cmd.rst:53 +msgid "" +"The optional argument is a banner or intro string to be issued before the " +"first prompt (this overrides the :attr:`intro` class attribute)." +msgstr "" + +#: ../Doc/library/cmd.rst:56 +msgid "" +"If the :mod:`readline` module is loaded, input will automatically inherit :" +"program:`bash`\\ -like history-list editing (e.g. :kbd:`Control-P` scrolls " +"back to the last command, :kbd:`Control-N` forward to the next one, :kbd:" +"`Control-F` moves the cursor to the right non-destructively, :kbd:`Control-" +"B` moves the cursor to the left non-destructively, etc.)." +msgstr "" + +#: ../Doc/library/cmd.rst:62 +msgid "An end-of-file on input is passed back as the string ``'EOF'``." +msgstr "" + +#: ../Doc/library/cmd.rst:64 +msgid "" +"An interpreter instance will recognize a command name ``foo`` if and only if " +"it has a method :meth:`do_foo`. As a special case, a line beginning with " +"the character ``'?'`` is dispatched to the method :meth:`do_help`. As " +"another special case, a line beginning with the character ``'!'`` is " +"dispatched to the method :meth:`do_shell` (if such a method is defined)." +msgstr "" + +#: ../Doc/library/cmd.rst:70 +msgid "" +"This method will return when the :meth:`postcmd` method returns a true " +"value. The *stop* argument to :meth:`postcmd` is the return value from the " +"command's corresponding :meth:`do_\\*` method." +msgstr "" + +#: ../Doc/library/cmd.rst:74 +msgid "" +"If completion is enabled, completing commands will be done automatically, " +"and completing of commands args is done by calling :meth:`complete_foo` with " +"arguments *text*, *line*, *begidx*, and *endidx*. *text* is the string " +"prefix we are attempting to match: all returned matches must begin with it. " +"*line* is the current input line with leading whitespace removed, *begidx* " +"and *endidx* are the beginning and ending indexes of the prefix text, which " +"could be used to provide different completion depending upon which position " +"the argument is in." +msgstr "" + +#: ../Doc/library/cmd.rst:82 +msgid "" +"All subclasses of :class:`Cmd` inherit a predefined :meth:`do_help`. This " +"method, called with an argument ``'bar'``, invokes the corresponding method :" +"meth:`help_bar`, and if that is not present, prints the docstring of :meth:" +"`do_bar`, if available. With no argument, :meth:`do_help` lists all " +"available help topics (that is, all commands with corresponding :meth:`help_" +"\\*` methods or commands that have docstrings), and also lists any " +"undocumented commands." +msgstr "" + +#: ../Doc/library/cmd.rst:93 +msgid "" +"Interpret the argument as though it had been typed in response to the " +"prompt. This may be overridden, but should not normally need to be; see the :" +"meth:`precmd` and :meth:`postcmd` methods for useful execution hooks. The " +"return value is a flag indicating whether interpretation of commands by the " +"interpreter should stop. If there is a :meth:`do_\\*` method for the " +"command *str*, the return value of that method is returned, otherwise the " +"return value from the :meth:`default` method is returned." +msgstr "" + +#: ../Doc/library/cmd.rst:104 +msgid "" +"Method called when an empty line is entered in response to the prompt. If " +"this method is not overridden, it repeats the last nonempty command entered." +msgstr "" + +#: ../Doc/library/cmd.rst:110 +msgid "" +"Method called on an input line when the command prefix is not recognized. If " +"this method is not overridden, it prints an error message and returns." +msgstr "" + +#: ../Doc/library/cmd.rst:116 +msgid "" +"Method called to complete an input line when no command-specific :meth:" +"`complete_\\*` method is available. By default, it returns an empty list." +msgstr "" + +#: ../Doc/library/cmd.rst:122 +msgid "" +"Hook method executed just before the command line *line* is interpreted, but " +"after the input prompt is generated and issued. This method is a stub in :" +"class:`Cmd`; it exists to be overridden by subclasses. The return value is " +"used as the command which will be executed by the :meth:`onecmd` method; " +"the :meth:`precmd` implementation may re-write the command or simply return " +"*line* unchanged." +msgstr "" + +#: ../Doc/library/cmd.rst:132 +msgid "" +"Hook method executed just after a command dispatch is finished. This method " +"is a stub in :class:`Cmd`; it exists to be overridden by subclasses. *line* " +"is the command line which was executed, and *stop* is a flag which indicates " +"whether execution will be terminated after the call to :meth:`postcmd`; this " +"will be the return value of the :meth:`onecmd` method. The return value of " +"this method will be used as the new value for the internal flag which " +"corresponds to *stop*; returning false will cause interpretation to continue." +msgstr "" + +#: ../Doc/library/cmd.rst:143 +msgid "" +"Hook method executed once when :meth:`cmdloop` is called. This method is a " +"stub in :class:`Cmd`; it exists to be overridden by subclasses." +msgstr "" + +#: ../Doc/library/cmd.rst:149 +msgid "" +"Hook method executed once when :meth:`cmdloop` is about to return. This " +"method is a stub in :class:`Cmd`; it exists to be overridden by subclasses." +msgstr "" + +#: ../Doc/library/cmd.rst:153 +msgid "" +"Instances of :class:`Cmd` subclasses have some public instance variables:" +msgstr "" + +#: ../Doc/library/cmd.rst:157 +msgid "The prompt issued to solicit input." +msgstr "" + +#: ../Doc/library/cmd.rst:162 +msgid "The string of characters accepted for the command prefix." +msgstr "" + +#: ../Doc/library/cmd.rst:167 +msgid "The last nonempty command prefix seen." +msgstr "" + +#: ../Doc/library/cmd.rst:172 +msgid "" +"A list of queued input lines. The cmdqueue list is checked in :meth:" +"`cmdloop` when new input is needed; if it is nonempty, its elements will be " +"processed in order, as if entered at the prompt." +msgstr "" + +#: ../Doc/library/cmd.rst:179 +msgid "" +"A string to issue as an intro or banner. May be overridden by giving the :" +"meth:`cmdloop` method an argument." +msgstr "" + +#: ../Doc/library/cmd.rst:185 +msgid "" +"The header to issue if the help output has a section for documented commands." +msgstr "" + +#: ../Doc/library/cmd.rst:190 +msgid "" +"The header to issue if the help output has a section for miscellaneous help " +"topics (that is, there are :meth:`help_\\*` methods without corresponding :" +"meth:`do_\\*` methods)." +msgstr "" + +#: ../Doc/library/cmd.rst:197 +msgid "" +"The header to issue if the help output has a section for undocumented " +"commands (that is, there are :meth:`do_\\*` methods without corresponding :" +"meth:`help_\\*` methods)." +msgstr "" + +#: ../Doc/library/cmd.rst:204 +msgid "" +"The character used to draw separator lines under the help-message headers. " +"If empty, no ruler line is drawn. It defaults to ``'='``." +msgstr "" + +#: ../Doc/library/cmd.rst:210 +msgid "" +"A flag, defaulting to true. If true, :meth:`cmdloop` uses :func:`input` to " +"display a prompt and read the next command; if false, :meth:`sys.stdout." +"write` and :meth:`sys.stdin.readline` are used. (This means that by " +"importing :mod:`readline`, on systems that support it, the interpreter will " +"automatically support :program:`Emacs`\\ -like line editing and command-" +"history keystrokes.)" +msgstr "" + +#: ../Doc/library/cmd.rst:220 +msgid "Cmd Example" +msgstr "" + +#: ../Doc/library/cmd.rst:224 +msgid "" +"The :mod:`cmd` module is mainly useful for building custom shells that let a " +"user work with a program interactively." +msgstr "" + +#: ../Doc/library/cmd.rst:227 +msgid "" +"This section presents a simple example of how to build a shell around a few " +"of the commands in the :mod:`turtle` module." +msgstr "" + +#: ../Doc/library/cmd.rst:230 +msgid "" +"Basic turtle commands such as :meth:`~turtle.forward` are added to a :class:" +"`Cmd` subclass with method named :meth:`do_forward`. The argument is " +"converted to a number and dispatched to the turtle module. The docstring is " +"used in the help utility provided by the shell." +msgstr "" + +#: ../Doc/library/cmd.rst:235 +msgid "" +"The example also includes a basic record and playback facility implemented " +"with the :meth:`~Cmd.precmd` method which is responsible for converting the " +"input to lowercase and writing the commands to a file. The :meth:" +"`do_playback` method reads the file and adds the recorded commands to the :" +"attr:`cmdqueue` for immediate playback::" +msgstr "" + +#: ../Doc/library/cmd.rst:316 +msgid "" +"Here is a sample session with the turtle shell showing the help functions, " +"using blank lines to repeat commands, and the simple record and playback " +"facility:" +msgstr "" + +#: ../Doc/library/code.rst:2 +msgid ":mod:`code` --- Interpreter base classes" +msgstr "" + +#: ../Doc/library/code.rst:7 +msgid "**Source code:** :source:`Lib/code.py`" +msgstr "" + +#: ../Doc/library/code.rst:11 +msgid "" +"The ``code`` module provides facilities to implement read-eval-print loops " +"in Python. Two classes and convenience functions are included which can be " +"used to build applications which provide an interactive interpreter prompt." +msgstr "" + +#: ../Doc/library/code.rst:18 +msgid "" +"This class deals with parsing and interpreter state (the user's namespace); " +"it does not deal with input buffering or prompting or input file naming (the " +"filename is always passed in explicitly). The optional *locals* argument " +"specifies the dictionary in which code will be executed; it defaults to a " +"newly created dictionary with key ``'__name__'`` set to ``'__console__'`` " +"and key ``'__doc__'`` set to ``None``." +msgstr "" + +#: ../Doc/library/code.rst:28 +msgid "" +"Closely emulate the behavior of the interactive Python interpreter. This " +"class builds on :class:`InteractiveInterpreter` and adds prompting using the " +"familiar ``sys.ps1`` and ``sys.ps2``, and input buffering." +msgstr "" + +#: ../Doc/library/code.rst:35 +msgid "" +"Convenience function to run a read-eval-print loop. This creates a new " +"instance of :class:`InteractiveConsole` and sets *readfunc* to be used as " +"the :meth:`InteractiveConsole.raw_input` method, if provided. If *local* is " +"provided, it is passed to the :class:`InteractiveConsole` constructor for " +"use as the default namespace for the interpreter loop. The :meth:`interact` " +"method of the instance is then run with *banner* and *exitmsg* passed as the " +"banner and exit message to use, if provided. The console object is " +"discarded after use." +msgstr "" + +#: ../Doc/library/code.rst:44 +msgid "Added *exitmsg* parameter." +msgstr "" + +#: ../Doc/library/code.rst:50 +msgid "" +"This function is useful for programs that want to emulate Python's " +"interpreter main loop (a.k.a. the read-eval-print loop). The tricky part is " +"to determine when the user has entered an incomplete command that can be " +"completed by entering more text (as opposed to a complete command or a " +"syntax error). This function *almost* always makes the same decision as the " +"real interpreter main loop." +msgstr "" + +#: ../Doc/library/code.rst:57 +msgid "" +"*source* is the source string; *filename* is the optional filename from " +"which source was read, defaulting to ``''``; and *symbol* is the " +"optional grammar start symbol, which should be either ``'single'`` (the " +"default) or ``'eval'``." +msgstr "" + +#: ../Doc/library/code.rst:62 +msgid "" +"Returns a code object (the same as ``compile(source, filename, symbol)``) if " +"the command is complete and valid; ``None`` if the command is incomplete; " +"raises :exc:`SyntaxError` if the command is complete and contains a syntax " +"error, or raises :exc:`OverflowError` or :exc:`ValueError` if the command " +"contains an invalid literal." +msgstr "" + +#: ../Doc/library/code.rst:72 +msgid "Interactive Interpreter Objects" +msgstr "" + +#: ../Doc/library/code.rst:77 +msgid "" +"Compile and run some source in the interpreter. Arguments are the same as " +"for :func:`compile_command`; the default for *filename* is ``''``, " +"and for *symbol* is ``'single'``. One several things can happen:" +msgstr "" + +#: ../Doc/library/code.rst:81 +msgid "" +"The input is incorrect; :func:`compile_command` raised an exception (:exc:" +"`SyntaxError` or :exc:`OverflowError`). A syntax traceback will be printed " +"by calling the :meth:`showsyntaxerror` method. :meth:`runsource` returns " +"``False``." +msgstr "" + +#: ../Doc/library/code.rst:86 +msgid "" +"The input is incomplete, and more input is required; :func:`compile_command` " +"returned ``None``. :meth:`runsource` returns ``True``." +msgstr "" + +#: ../Doc/library/code.rst:89 +msgid "" +"The input is complete; :func:`compile_command` returned a code object. The " +"code is executed by calling the :meth:`runcode` (which also handles run-time " +"exceptions, except for :exc:`SystemExit`). :meth:`runsource` returns " +"``False``." +msgstr "" + +#: ../Doc/library/code.rst:93 +msgid "" +"The return value can be used to decide whether to use ``sys.ps1`` or ``sys." +"ps2`` to prompt the next line." +msgstr "" + +#: ../Doc/library/code.rst:99 +msgid "" +"Execute a code object. When an exception occurs, :meth:`showtraceback` is " +"called to display a traceback. All exceptions are caught except :exc:" +"`SystemExit`, which is allowed to propagate." +msgstr "" + +#: ../Doc/library/code.rst:103 +msgid "" +"A note about :exc:`KeyboardInterrupt`: this exception may occur elsewhere in " +"this code, and may not always be caught. The caller should be prepared to " +"deal with it." +msgstr "" + +#: ../Doc/library/code.rst:110 +msgid "" +"Display the syntax error that just occurred. This does not display a stack " +"trace because there isn't one for syntax errors. If *filename* is given, it " +"is stuffed into the exception instead of the default filename provided by " +"Python's parser, because it always uses ``''`` when reading from a " +"string. The output is written by the :meth:`write` method." +msgstr "" + +#: ../Doc/library/code.rst:119 +msgid "" +"Display the exception that just occurred. We remove the first stack item " +"because it is within the interpreter object implementation. The output is " +"written by the :meth:`write` method." +msgstr "" + +#: ../Doc/library/code.rst:123 +msgid "" +"The full chained traceback is displayed instead of just the primary " +"traceback." +msgstr "" + +#: ../Doc/library/code.rst:129 +msgid "" +"Write a string to the standard error stream (``sys.stderr``). Derived " +"classes should override this to provide the appropriate output handling as " +"needed." +msgstr "" + +#: ../Doc/library/code.rst:136 +msgid "Interactive Console Objects" +msgstr "" + +#: ../Doc/library/code.rst:138 +msgid "" +"The :class:`InteractiveConsole` class is a subclass of :class:" +"`InteractiveInterpreter`, and so offers all the methods of the interpreter " +"objects as well as the following additions." +msgstr "" + +#: ../Doc/library/code.rst:145 +msgid "" +"Closely emulate the interactive Python console. The optional *banner* " +"argument specify the banner to print before the first interaction; by " +"default it prints a banner similar to the one printed by the standard Python " +"interpreter, followed by the class name of the console object in parentheses " +"(so as not to confuse this with the real interpreter -- since it's so " +"close!)." +msgstr "" + +#: ../Doc/library/code.rst:151 +msgid "" +"The optional *exitmsg* argument specifies an exit message printed when " +"exiting. Pass the empty string to suppress the exit message. If *exitmsg* is " +"not given or None, a default message is printed." +msgstr "" + +#: ../Doc/library/code.rst:155 +msgid "To suppress printing any banner, pass an empty string." +msgstr "" + +#: ../Doc/library/code.rst:158 +msgid "Print an exit message when exiting." +msgstr "" + +#: ../Doc/library/code.rst:164 +msgid "" +"Push a line of source text to the interpreter. The line should not have a " +"trailing newline; it may have internal newlines. The line is appended to a " +"buffer and the interpreter's :meth:`runsource` method is called with the " +"concatenated contents of the buffer as source. If this indicates that the " +"command was executed or invalid, the buffer is reset; otherwise, the command " +"is incomplete, and the buffer is left as it was after the line was " +"appended. The return value is ``True`` if more input is required, ``False`` " +"if the line was dealt with in some way (this is the same as :meth:" +"`runsource`)." +msgstr "" + +#: ../Doc/library/code.rst:176 +msgid "Remove any unhandled source text from the input buffer." +msgstr "" + +#: ../Doc/library/code.rst:181 +msgid "" +"Write a prompt and read a line. The returned line does not include the " +"trailing newline. When the user enters the EOF key sequence, :exc:" +"`EOFError` is raised. The base implementation reads from ``sys.stdin``; a " +"subclass may replace this with a different implementation." +msgstr "" + +#: ../Doc/library/codecs.rst:2 +msgid ":mod:`codecs` --- Codec registry and base classes" +msgstr "" + +#: ../Doc/library/codecs.rst:11 +msgid "**Source code:** :source:`Lib/codecs.py`" +msgstr "" + +#: ../Doc/library/codecs.rst:23 +msgid "" +"This module defines base classes for standard Python codecs (encoders and " +"decoders) and provides access to the internal Python codec registry, which " +"manages the codec and error handling lookup process. Most standard codecs " +"are :term:`text encodings `, which encode text to bytes, but " +"there are also codecs provided that encode text to text, and bytes to bytes. " +"Custom codecs may encode and decode between arbitrary types, but some module " +"features are restricted to use specifically with :term:`text encodings `, or with codecs that encode to :class:`bytes`." +msgstr "" + +#: ../Doc/library/codecs.rst:33 +msgid "" +"The module defines the following functions for encoding and decoding with " +"any codec:" +msgstr "" + +#: ../Doc/library/codecs.rst:38 +msgid "Encodes *obj* using the codec registered for *encoding*." +msgstr "" + +#: ../Doc/library/codecs.rst:40 +msgid "" +"*Errors* may be given to set the desired error handling scheme. The default " +"error handler is ``'strict'`` meaning that encoding errors raise :exc:" +"`ValueError` (or a more codec specific subclass, such as :exc:" +"`UnicodeEncodeError`). Refer to :ref:`codec-base-classes` for more " +"information on codec error handling." +msgstr "" + +#: ../Doc/library/codecs.rst:48 +msgid "Decodes *obj* using the codec registered for *encoding*." +msgstr "" + +#: ../Doc/library/codecs.rst:50 +msgid "" +"*Errors* may be given to set the desired error handling scheme. The default " +"error handler is ``'strict'`` meaning that decoding errors raise :exc:" +"`ValueError` (or a more codec specific subclass, such as :exc:" +"`UnicodeDecodeError`). Refer to :ref:`codec-base-classes` for more " +"information on codec error handling." +msgstr "" + +#: ../Doc/library/codecs.rst:56 +msgid "The full details for each codec can also be looked up directly:" +msgstr "" + +#: ../Doc/library/codecs.rst:60 +msgid "" +"Looks up the codec info in the Python codec registry and returns a :class:" +"`CodecInfo` object as defined below." +msgstr "" + +#: ../Doc/library/codecs.rst:63 +msgid "" +"Encodings are first looked up in the registry's cache. If not found, the " +"list of registered search functions is scanned. If no :class:`CodecInfo` " +"object is found, a :exc:`LookupError` is raised. Otherwise, the :class:" +"`CodecInfo` object is stored in the cache and returned to the caller." +msgstr "" + +#: ../Doc/library/codecs.rst:70 +msgid "" +"Codec details when looking up the codec registry. The constructor arguments " +"are stored in attributes of the same name:" +msgstr "" + +#: ../Doc/library/codecs.rst:76 +msgid "The name of the encoding." +msgstr "" + +#: ../Doc/library/codecs.rst:82 +msgid "" +"The stateless encoding and decoding functions. These must be functions or " +"methods which have the same interface as the :meth:`~Codec.encode` and :meth:" +"`~Codec.decode` methods of Codec instances (see :ref:`Codec Interface `). The functions or methods are expected to work in a stateless " +"mode." +msgstr "" + +#: ../Doc/library/codecs.rst:92 +msgid "" +"Incremental encoder and decoder classes or factory functions. These have to " +"provide the interface defined by the base classes :class:" +"`IncrementalEncoder` and :class:`IncrementalDecoder`, respectively. " +"Incremental codecs can maintain state." +msgstr "" + +#: ../Doc/library/codecs.rst:101 +msgid "" +"Stream writer and reader classes or factory functions. These have to provide " +"the interface defined by the base classes :class:`StreamWriter` and :class:" +"`StreamReader`, respectively. Stream codecs can maintain state." +msgstr "" + +#: ../Doc/library/codecs.rst:106 +msgid "" +"To simplify access to the various codec components, the module provides " +"these additional functions which use :func:`lookup` for the codec lookup:" +msgstr "" + +#: ../Doc/library/codecs.rst:111 +msgid "" +"Look up the codec for the given encoding and return its encoder function." +msgstr "" + +#: ../Doc/library/codecs.rst:113 ../Doc/library/codecs.rst:120 +#: ../Doc/library/codecs.rst:146 ../Doc/library/codecs.rst:154 +msgid "Raises a :exc:`LookupError` in case the encoding cannot be found." +msgstr "" + +#: ../Doc/library/codecs.rst:118 +msgid "" +"Look up the codec for the given encoding and return its decoder function." +msgstr "" + +#: ../Doc/library/codecs.rst:125 +msgid "" +"Look up the codec for the given encoding and return its incremental encoder " +"class or factory function." +msgstr "" + +#: ../Doc/library/codecs.rst:128 +msgid "" +"Raises a :exc:`LookupError` in case the encoding cannot be found or the " +"codec doesn't support an incremental encoder." +msgstr "" + +#: ../Doc/library/codecs.rst:134 +msgid "" +"Look up the codec for the given encoding and return its incremental decoder " +"class or factory function." +msgstr "" + +#: ../Doc/library/codecs.rst:137 +msgid "" +"Raises a :exc:`LookupError` in case the encoding cannot be found or the " +"codec doesn't support an incremental decoder." +msgstr "" + +#: ../Doc/library/codecs.rst:143 +msgid "" +"Look up the codec for the given encoding and return its :class:" +"`StreamReader` class or factory function." +msgstr "" + +#: ../Doc/library/codecs.rst:151 +msgid "" +"Look up the codec for the given encoding and return its :class:" +"`StreamWriter` class or factory function." +msgstr "" + +#: ../Doc/library/codecs.rst:156 +msgid "" +"Custom codecs are made available by registering a suitable codec search " +"function:" +msgstr "" + +#: ../Doc/library/codecs.rst:161 +msgid "" +"Register a codec search function. Search functions are expected to take one " +"argument, being the encoding name in all lower case letters, and return a :" +"class:`CodecInfo` object. In case a search function cannot find a given " +"encoding, it should return ``None``." +msgstr "" + +#: ../Doc/library/codecs.rst:168 +msgid "" +"Search function registration is not currently reversible, which may cause " +"problems in some cases, such as unit testing or module reloading." +msgstr "" + +#: ../Doc/library/codecs.rst:172 +msgid "" +"While the builtin :func:`open` and the associated :mod:`io` module are the " +"recommended approach for working with encoded text files, this module " +"provides additional utility functions and classes that allow the use of a " +"wider range of codecs when working with binary files:" +msgstr "" + +#: ../Doc/library/codecs.rst:179 +msgid "" +"Open an encoded file using the given *mode* and return an instance of :class:" +"`StreamReaderWriter`, providing transparent encoding/decoding. The default " +"file mode is ``'r'``, meaning to open the file in read mode." +msgstr "" + +#: ../Doc/library/codecs.rst:185 +msgid "" +"Underlying encoded files are always opened in binary mode. No automatic " +"conversion of ``'\\n'`` is done on reading and writing. The *mode* argument " +"may be any binary mode acceptable to the built-in :func:`open` function; the " +"``'b'`` is automatically added." +msgstr "" + +#: ../Doc/library/codecs.rst:190 +msgid "" +"*encoding* specifies the encoding which is to be used for the file. Any " +"encoding that encodes to and decodes from bytes is allowed, and the data " +"types supported by the file methods depend on the codec used." +msgstr "" + +#: ../Doc/library/codecs.rst:194 +msgid "" +"*errors* may be given to define the error handling. It defaults to " +"``'strict'`` which causes a :exc:`ValueError` to be raised in case an " +"encoding error occurs." +msgstr "" + +#: ../Doc/library/codecs.rst:197 +msgid "" +"*buffering* has the same meaning as for the built-in :func:`open` function. " +"It defaults to line buffered." +msgstr "" + +#: ../Doc/library/codecs.rst:203 +msgid "" +"Return a :class:`StreamRecoder` instance, a wrapped version of *file* which " +"provides transparent transcoding. The original file is closed when the " +"wrapped version is closed." +msgstr "" + +#: ../Doc/library/codecs.rst:207 +msgid "" +"Data written to the wrapped file is decoded according to the given " +"*data_encoding* and then written to the original file as bytes using " +"*file_encoding*. Bytes read from the original file are decoded according to " +"*file_encoding*, and the result is encoded using *data_encoding*." +msgstr "" + +#: ../Doc/library/codecs.rst:213 +msgid "If *file_encoding* is not given, it defaults to *data_encoding*." +msgstr "" + +#: ../Doc/library/codecs.rst:215 +msgid "" +"*errors* may be given to define the error handling. It defaults to " +"``'strict'``, which causes :exc:`ValueError` to be raised in case an " +"encoding error occurs." +msgstr "" + +#: ../Doc/library/codecs.rst:222 +msgid "" +"Uses an incremental encoder to iteratively encode the input provided by " +"*iterator*. This function is a :term:`generator`. The *errors* argument (as " +"well as any other keyword argument) is passed through to the incremental " +"encoder." +msgstr "" + +#: ../Doc/library/codecs.rst:227 +msgid "" +"This function requires that the codec accept text :class:`str` objects to " +"encode. Therefore it does not support bytes-to-bytes encoders such as " +"``base64_codec``." +msgstr "" + +#: ../Doc/library/codecs.rst:234 +msgid "" +"Uses an incremental decoder to iteratively decode the input provided by " +"*iterator*. This function is a :term:`generator`. The *errors* argument (as " +"well as any other keyword argument) is passed through to the incremental " +"decoder." +msgstr "" + +#: ../Doc/library/codecs.rst:239 +msgid "" +"This function requires that the codec accept :class:`bytes` objects to " +"decode. Therefore it does not support text-to-text encoders such as " +"``rot_13``, although ``rot_13`` may be used equivalently with :func:" +"`iterencode`." +msgstr "" + +#: ../Doc/library/codecs.rst:245 +msgid "" +"The module also provides the following constants which are useful for " +"reading and writing to platform dependent files:" +msgstr "" + +#: ../Doc/library/codecs.rst:260 +msgid "" +"These constants define various byte sequences, being Unicode byte order " +"marks (BOMs) for several encodings. They are used in UTF-16 and UTF-32 data " +"streams to indicate the byte order used, and in UTF-8 as a Unicode " +"signature. :const:`BOM_UTF16` is either :const:`BOM_UTF16_BE` or :const:" +"`BOM_UTF16_LE` depending on the platform's native byte order, :const:`BOM` " +"is an alias for :const:`BOM_UTF16`, :const:`BOM_LE` for :const:" +"`BOM_UTF16_LE` and :const:`BOM_BE` for :const:`BOM_UTF16_BE`. The others " +"represent the BOM in UTF-8 and UTF-32 encodings." +msgstr "" + +#: ../Doc/library/codecs.rst:274 +msgid "Codec Base Classes" +msgstr "" + +#: ../Doc/library/codecs.rst:276 +msgid "" +"The :mod:`codecs` module defines a set of base classes which define the " +"interfaces for working with codec objects, and can also be used as the basis " +"for custom codec implementations." +msgstr "" + +#: ../Doc/library/codecs.rst:280 +msgid "" +"Each codec has to define four interfaces to make it usable as codec in " +"Python: stateless encoder, stateless decoder, stream reader and stream " +"writer. The stream reader and writers typically reuse the stateless encoder/" +"decoder to implement the file protocols. Codec authors also need to define " +"how the codec will handle encoding and decoding errors." +msgstr "" + +#: ../Doc/library/codecs.rst:291 +msgid "Error Handlers" +msgstr "" + +#: ../Doc/library/codecs.rst:293 +msgid "" +"To simplify and standardize error handling, codecs may implement different " +"error handling schemes by accepting the *errors* string argument. The " +"following string values are defined and implemented by all standard Python " +"codecs:" +msgstr "" + +#: ../Doc/library/codecs.rst:301 ../Doc/library/codecs.rst:316 +#: ../Doc/library/codecs.rst:349 ../Doc/library/datetime.rst:223 +#: ../Doc/library/dbm.rst:48 ../Doc/library/dbm.rst:160 +#: ../Doc/library/dbm.rst:179 ../Doc/library/dbm.rst:275 +#: ../Doc/library/difflib.rst:489 ../Doc/library/imghdr.rst:30 +#: ../Doc/library/locale.rst:130 ../Doc/library/logging.handlers.rst:331 +#: ../Doc/library/urllib.parse.rst:92 ../Doc/library/urllib.parse.rst:213 +#: ../Doc/library/urllib.parse.rst:298 ../Doc/library/warnings.rst:124 +#: ../Doc/library/zipfile.rst:539 +msgid "Value" +msgstr "" + +#: ../Doc/library/codecs.rst:301 ../Doc/library/codecs.rst:316 +#: ../Doc/library/codecs.rst:349 ../Doc/library/curses.rst:1277 +#: ../Doc/library/curses.rst:1529 ../Doc/library/curses.ascii.rst:17 +#: ../Doc/library/datetime.rst:1966 ../Doc/library/datetime.rst:2072 +#: ../Doc/library/dbm.rst:48 ../Doc/library/dbm.rst:160 +#: ../Doc/library/dbm.rst:179 ../Doc/library/dbm.rst:275 +#: ../Doc/library/difflib.rst:68 ../Doc/library/difflib.rst:489 +#: ../Doc/library/fnmatch.rst:20 ../Doc/library/functions.rst:909 +#: ../Doc/library/grp.rst:18 ../Doc/library/inspect.rst:658 +#: ../Doc/library/locale.rst:65 ../Doc/library/mailbox.rst:817 +#: ../Doc/library/mailbox.rst:984 ../Doc/library/mailbox.rst:1354 +#: ../Doc/library/profile.rst:372 ../Doc/library/pwd.rst:18 +#: ../Doc/library/select.rst:272 ../Doc/library/select.rst:384 +#: ../Doc/library/select.rst:503 ../Doc/library/select.rst:532 +#: ../Doc/library/select.rst:563 ../Doc/library/select.rst:571 +#: ../Doc/library/select.rst:591 ../Doc/library/select.rst:614 +#: ../Doc/library/selectors.rst:60 ../Doc/library/spwd.rst:21 +#: ../Doc/library/stdtypes.rst:148 ../Doc/library/stdtypes.rst:2130 +#: ../Doc/library/stdtypes.rst:2153 ../Doc/library/stdtypes.rst:3230 +#: ../Doc/library/stdtypes.rst:3253 ../Doc/library/string.rst:324 +#: ../Doc/library/string.rst:350 ../Doc/library/string.rst:412 +#: ../Doc/library/string.rst:423 ../Doc/library/string.rst:455 +#: ../Doc/library/sys.rst:568 ../Doc/library/time.rst:380 +#: ../Doc/library/tkinter.rst:430 ../Doc/library/uuid.rst:69 +#: ../Doc/library/winreg.rst:210 ../Doc/library/winreg.rst:317 +#: ../Doc/library/winreg.rst:361 ../Doc/library/xml.etree.elementtree.rst:408 +msgid "Meaning" +msgstr "" + +#: ../Doc/library/codecs.rst:303 +msgid "``'strict'``" +msgstr "" + +#: ../Doc/library/codecs.rst:303 +msgid "" +"Raise :exc:`UnicodeError` (or a subclass); this is the default. Implemented " +"in :func:`strict_errors`." +msgstr "" + +#: ../Doc/library/codecs.rst:307 +msgid "``'ignore'``" +msgstr "" + +#: ../Doc/library/codecs.rst:307 +msgid "" +"Ignore the malformed data and continue without further notice. Implemented " +"in :func:`ignore_errors`." +msgstr "" + +#: ../Doc/library/codecs.rst:312 +msgid "" +"The following error handlers are only applicable to :term:`text encodings " +"`:" +msgstr "" + +#: ../Doc/library/codecs.rst:318 ../Doc/library/difflib.rst:491 +msgid "``'replace'``" +msgstr "" + +#: ../Doc/library/codecs.rst:318 +msgid "" +"Replace with a suitable replacement marker; Python will use the official ``U" +"+FFFD`` REPLACEMENT CHARACTER for the built-in codecs on decoding, and '?' " +"on encoding. Implemented in :func:`replace_errors`." +msgstr "" + +#: ../Doc/library/codecs.rst:325 +msgid "``'xmlcharrefreplace'``" +msgstr "" + +#: ../Doc/library/codecs.rst:325 +msgid "" +"Replace with the appropriate XML character reference (only for encoding). " +"Implemented in :func:`xmlcharrefreplace_errors`." +msgstr "" + +#: ../Doc/library/codecs.rst:329 +msgid "``'backslashreplace'``" +msgstr "" + +#: ../Doc/library/codecs.rst:329 +msgid "" +"Replace with backslashed escape sequences. Implemented in :func:" +"`backslashreplace_errors`." +msgstr "" + +#: ../Doc/library/codecs.rst:333 +msgid "``'namereplace'``" +msgstr "" + +#: ../Doc/library/codecs.rst:333 +msgid "" +"Replace with ``\\N{...}`` escape sequences (only for encoding). Implemented " +"in :func:`namereplace_errors`." +msgstr "" + +#: ../Doc/library/codecs.rst:337 +msgid "``'surrogateescape'``" +msgstr "" + +#: ../Doc/library/codecs.rst:337 +msgid "" +"On decoding, replace byte with individual surrogate code ranging from ``U" +"+DC80`` to ``U+DCFF``. This code will then be turned back into the same " +"byte when the ``'surrogateescape'`` error handler is used when encoding the " +"data. (See :pep:`383` for more.)" +msgstr "" + +#: ../Doc/library/codecs.rst:346 +msgid "" +"In addition, the following error handler is specific to the given codecs:" +msgstr "" + +#: ../Doc/library/codecs.rst:349 +msgid "Codecs" +msgstr "" + +#: ../Doc/library/codecs.rst:351 +msgid "``'surrogatepass'``" +msgstr "" + +#: ../Doc/library/codecs.rst:351 +msgid "utf-8, utf-16, utf-32, utf-16-be, utf-16-le, utf-32-be, utf-32-le" +msgstr "" + +#: ../Doc/library/codecs.rst:351 +msgid "" +"Allow encoding and decoding of surrogate codes. These codecs normally treat " +"the presence of surrogates as an error." +msgstr "" + +#: ../Doc/library/codecs.rst:356 +msgid "The ``'surrogateescape'`` and ``'surrogatepass'`` error handlers." +msgstr "" + +#: ../Doc/library/codecs.rst:359 +msgid "" +"The ``'surrogatepass'`` error handlers now works with utf-16\\* and " +"utf-32\\* codecs." +msgstr "" + +#: ../Doc/library/codecs.rst:362 +msgid "The ``'namereplace'`` error handler." +msgstr "" + +#: ../Doc/library/codecs.rst:365 +msgid "" +"The ``'backslashreplace'`` error handlers now works with decoding and " +"translating." +msgstr "" + +#: ../Doc/library/codecs.rst:369 +msgid "" +"The set of allowed values can be extended by registering a new named error " +"handler:" +msgstr "" + +#: ../Doc/library/codecs.rst:374 +msgid "" +"Register the error handling function *error_handler* under the name *name*. " +"The *error_handler* argument will be called during encoding and decoding in " +"case of an error, when *name* is specified as the errors parameter." +msgstr "" + +#: ../Doc/library/codecs.rst:378 +msgid "" +"For encoding, *error_handler* will be called with a :exc:" +"`UnicodeEncodeError` instance, which contains information about the location " +"of the error. The error handler must either raise this or a different " +"exception, or return a tuple with a replacement for the unencodable part of " +"the input and a position where encoding should continue. The replacement may " +"be either :class:`str` or :class:`bytes`. If the replacement is bytes, the " +"encoder will simply copy them into the output buffer. If the replacement is " +"a string, the encoder will encode the replacement. Encoding continues on " +"original input at the specified position. Negative position values will be " +"treated as being relative to the end of the input string. If the resulting " +"position is out of bound an :exc:`IndexError` will be raised." +msgstr "" + +#: ../Doc/library/codecs.rst:390 +msgid "" +"Decoding and translating works similarly, except :exc:`UnicodeDecodeError` " +"or :exc:`UnicodeTranslateError` will be passed to the handler and that the " +"replacement from the error handler will be put into the output directly." +msgstr "" + +#: ../Doc/library/codecs.rst:395 +msgid "" +"Previously registered error handlers (including the standard error handlers) " +"can be looked up by name:" +msgstr "" + +#: ../Doc/library/codecs.rst:400 +msgid "Return the error handler previously registered under the name *name*." +msgstr "" + +#: ../Doc/library/codecs.rst:402 +msgid "Raises a :exc:`LookupError` in case the handler cannot be found." +msgstr "" + +#: ../Doc/library/codecs.rst:404 +msgid "" +"The following standard error handlers are also made available as module " +"level functions:" +msgstr "" + +#: ../Doc/library/codecs.rst:409 +msgid "" +"Implements the ``'strict'`` error handling: each encoding or decoding error " +"raises a :exc:`UnicodeError`." +msgstr "" + +#: ../Doc/library/codecs.rst:415 +msgid "" +"Implements the ``'replace'`` error handling (for :term:`text encodings ` only): substitutes ``'?'`` for encoding errors (to be encoded by " +"the codec), and ``'\\ufffd'`` (the Unicode replacement character) for " +"decoding errors." +msgstr "" + +#: ../Doc/library/codecs.rst:423 +msgid "" +"Implements the ``'ignore'`` error handling: malformed data is ignored and " +"encoding or decoding is continued without further notice." +msgstr "" + +#: ../Doc/library/codecs.rst:429 +msgid "" +"Implements the ``'xmlcharrefreplace'`` error handling (for encoding with :" +"term:`text encodings ` only): the unencodable character is " +"replaced by an appropriate XML character reference." +msgstr "" + +#: ../Doc/library/codecs.rst:436 +msgid "" +"Implements the ``'backslashreplace'`` error handling (for :term:`text " +"encodings ` only): malformed data is replaced by a " +"backslashed escape sequence." +msgstr "" + +#: ../Doc/library/codecs.rst:442 +msgid "" +"Implements the ``'namereplace'`` error handling (for encoding with :term:" +"`text encodings ` only): the unencodable character is " +"replaced by a ``\\N{...}`` escape sequence." +msgstr "" + +#: ../Doc/library/codecs.rst:452 +msgid "Stateless Encoding and Decoding" +msgstr "" + +#: ../Doc/library/codecs.rst:454 +msgid "" +"The base :class:`Codec` class defines these methods which also define the " +"function interfaces of the stateless encoder and decoder:" +msgstr "" + +#: ../Doc/library/codecs.rst:460 +msgid "" +"Encodes the object *input* and returns a tuple (output object, length " +"consumed). For instance, :term:`text encoding` converts a string object to a " +"bytes object using a particular character set encoding (e.g., ``cp1252`` or " +"``iso-8859-1``)." +msgstr "" + +#: ../Doc/library/codecs.rst:465 ../Doc/library/codecs.rst:487 +msgid "" +"The *errors* argument defines the error handling to apply. It defaults to " +"``'strict'`` handling." +msgstr "" + +#: ../Doc/library/codecs.rst:468 +msgid "" +"The method may not store state in the :class:`Codec` instance. Use :class:" +"`StreamWriter` for codecs which have to keep state in order to make encoding " +"efficient." +msgstr "" + +#: ../Doc/library/codecs.rst:472 +msgid "" +"The encoder must be able to handle zero length input and return an empty " +"object of the output object type in this situation." +msgstr "" + +#: ../Doc/library/codecs.rst:478 +msgid "" +"Decodes the object *input* and returns a tuple (output object, length " +"consumed). For instance, for a :term:`text encoding`, decoding converts a " +"bytes object encoded using a particular character set encoding to a string " +"object." +msgstr "" + +#: ../Doc/library/codecs.rst:483 +msgid "" +"For text encodings and bytes-to-bytes codecs, *input* must be a bytes object " +"or one which provides the read-only buffer interface -- for example, buffer " +"objects and memory mapped files." +msgstr "" + +#: ../Doc/library/codecs.rst:490 +msgid "" +"The method may not store state in the :class:`Codec` instance. Use :class:" +"`StreamReader` for codecs which have to keep state in order to make decoding " +"efficient." +msgstr "" + +#: ../Doc/library/codecs.rst:494 +msgid "" +"The decoder must be able to handle zero length input and return an empty " +"object of the output object type in this situation." +msgstr "" + +#: ../Doc/library/codecs.rst:499 +msgid "Incremental Encoding and Decoding" +msgstr "" + +#: ../Doc/library/codecs.rst:501 +msgid "" +"The :class:`IncrementalEncoder` and :class:`IncrementalDecoder` classes " +"provide the basic interface for incremental encoding and decoding. Encoding/" +"decoding the input isn't done with one call to the stateless encoder/decoder " +"function, but with multiple calls to the :meth:`~IncrementalEncoder.encode`/:" +"meth:`~IncrementalDecoder.decode` method of the incremental encoder/decoder. " +"The incremental encoder/decoder keeps track of the encoding/decoding process " +"during method calls." +msgstr "" + +#: ../Doc/library/codecs.rst:509 +msgid "" +"The joined output of calls to the :meth:`~IncrementalEncoder.encode`/:meth:" +"`~IncrementalDecoder.decode` method is the same as if all the single inputs " +"were joined into one, and this input was encoded/decoded with the stateless " +"encoder/decoder." +msgstr "" + +#: ../Doc/library/codecs.rst:518 +msgid "IncrementalEncoder Objects" +msgstr "" + +#: ../Doc/library/codecs.rst:520 +msgid "" +"The :class:`IncrementalEncoder` class is used for encoding an input in " +"multiple steps. It defines the following methods which every incremental " +"encoder must define in order to be compatible with the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:527 +msgid "Constructor for an :class:`IncrementalEncoder` instance." +msgstr "" + +#: ../Doc/library/codecs.rst:529 +msgid "" +"All incremental encoders must provide this constructor interface. They are " +"free to add additional keyword arguments, but only the ones defined here are " +"used by the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:533 +msgid "" +"The :class:`IncrementalEncoder` may implement different error handling " +"schemes by providing the *errors* keyword argument. See :ref:`error-" +"handlers` for possible values." +msgstr "" + +#: ../Doc/library/codecs.rst:537 +msgid "" +"The *errors* argument will be assigned to an attribute of the same name. " +"Assigning to this attribute makes it possible to switch between different " +"error handling strategies during the lifetime of the :class:" +"`IncrementalEncoder` object." +msgstr "" + +#: ../Doc/library/codecs.rst:545 +msgid "" +"Encodes *object* (taking the current state of the encoder into account) and " +"returns the resulting encoded object. If this is the last call to :meth:" +"`encode` *final* must be true (the default is false)." +msgstr "" + +#: ../Doc/library/codecs.rst:552 +msgid "" +"Reset the encoder to the initial state. The output is discarded: call ``." +"encode(object, final=True)``, passing an empty byte or text string if " +"necessary, to reset the encoder and to get the output." +msgstr "" + +#: ../Doc/library/codecs.rst:559 +msgid "" +"Return the current state of the encoder which must be an integer. The " +"implementation should make sure that ``0`` is the most common state. (States " +"that are more complicated than integers can be converted into an integer by " +"marshaling/pickling the state and encoding the bytes of the resulting string " +"into an integer)." +msgstr "" + +#: ../Doc/library/codecs.rst:568 +msgid "" +"Set the state of the encoder to *state*. *state* must be an encoder state " +"returned by :meth:`getstate`." +msgstr "" + +#: ../Doc/library/codecs.rst:575 +msgid "IncrementalDecoder Objects" +msgstr "" + +#: ../Doc/library/codecs.rst:577 +msgid "" +"The :class:`IncrementalDecoder` class is used for decoding an input in " +"multiple steps. It defines the following methods which every incremental " +"decoder must define in order to be compatible with the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:584 +msgid "Constructor for an :class:`IncrementalDecoder` instance." +msgstr "" + +#: ../Doc/library/codecs.rst:586 +msgid "" +"All incremental decoders must provide this constructor interface. They are " +"free to add additional keyword arguments, but only the ones defined here are " +"used by the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:590 +msgid "" +"The :class:`IncrementalDecoder` may implement different error handling " +"schemes by providing the *errors* keyword argument. See :ref:`error-" +"handlers` for possible values." +msgstr "" + +#: ../Doc/library/codecs.rst:594 +msgid "" +"The *errors* argument will be assigned to an attribute of the same name. " +"Assigning to this attribute makes it possible to switch between different " +"error handling strategies during the lifetime of the :class:" +"`IncrementalDecoder` object." +msgstr "" + +#: ../Doc/library/codecs.rst:602 +msgid "" +"Decodes *object* (taking the current state of the decoder into account) and " +"returns the resulting decoded object. If this is the last call to :meth:" +"`decode` *final* must be true (the default is false). If *final* is true the " +"decoder must decode the input completely and must flush all buffers. If this " +"isn't possible (e.g. because of incomplete byte sequences at the end of the " +"input) it must initiate error handling just like in the stateless case " +"(which might raise an exception)." +msgstr "" + +#: ../Doc/library/codecs.rst:613 +msgid "Reset the decoder to the initial state." +msgstr "" + +#: ../Doc/library/codecs.rst:618 +msgid "" +"Return the current state of the decoder. This must be a tuple with two " +"items, the first must be the buffer containing the still undecoded input. " +"The second must be an integer and can be additional state info. (The " +"implementation should make sure that ``0`` is the most common additional " +"state info.) If this additional state info is ``0`` it must be possible to " +"set the decoder to the state which has no input buffered and ``0`` as the " +"additional state info, so that feeding the previously buffered input to the " +"decoder returns it to the previous state without producing any output. " +"(Additional state info that is more complicated than integers can be " +"converted into an integer by marshaling/pickling the info and encoding the " +"bytes of the resulting string into an integer.)" +msgstr "" + +#: ../Doc/library/codecs.rst:633 +msgid "" +"Set the state of the encoder to *state*. *state* must be a decoder state " +"returned by :meth:`getstate`." +msgstr "" + +#: ../Doc/library/codecs.rst:638 +msgid "Stream Encoding and Decoding" +msgstr "" + +#: ../Doc/library/codecs.rst:641 +msgid "" +"The :class:`StreamWriter` and :class:`StreamReader` classes provide generic " +"working interfaces which can be used to implement new encoding submodules " +"very easily. See :mod:`encodings.utf_8` for an example of how this is done." +msgstr "" + +#: ../Doc/library/codecs.rst:649 +msgid "StreamWriter Objects" +msgstr "" + +#: ../Doc/library/codecs.rst:651 +msgid "" +"The :class:`StreamWriter` class is a subclass of :class:`Codec` and defines " +"the following methods which every stream writer must define in order to be " +"compatible with the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:658 +msgid "Constructor for a :class:`StreamWriter` instance." +msgstr "" + +#: ../Doc/library/codecs.rst:660 +msgid "" +"All stream writers must provide this constructor interface. They are free to " +"add additional keyword arguments, but only the ones defined here are used by " +"the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:664 +msgid "" +"The *stream* argument must be a file-like object open for writing text or " +"binary data, as appropriate for the specific codec." +msgstr "" + +#: ../Doc/library/codecs.rst:667 +msgid "" +"The :class:`StreamWriter` may implement different error handling schemes by " +"providing the *errors* keyword argument. See :ref:`error-handlers` for the " +"standard error handlers the underlying stream codec may support." +msgstr "" + +#: ../Doc/library/codecs.rst:671 +msgid "" +"The *errors* argument will be assigned to an attribute of the same name. " +"Assigning to this attribute makes it possible to switch between different " +"error handling strategies during the lifetime of the :class:`StreamWriter` " +"object." +msgstr "" + +#: ../Doc/library/codecs.rst:677 +msgid "Writes the object's contents encoded to the stream." +msgstr "" + +#: ../Doc/library/codecs.rst:682 +msgid "" +"Writes the concatenated list of strings to the stream (possibly by reusing " +"the :meth:`write` method). The standard bytes-to-bytes codecs do not support " +"this method." +msgstr "" + +#: ../Doc/library/codecs.rst:689 +msgid "Flushes and resets the codec buffers used for keeping state." +msgstr "" + +#: ../Doc/library/codecs.rst:691 +msgid "" +"Calling this method should ensure that the data on the output is put into a " +"clean state that allows appending of new fresh data without having to rescan " +"the whole stream to recover state." +msgstr "" + +#: ../Doc/library/codecs.rst:696 +msgid "" +"In addition to the above methods, the :class:`StreamWriter` must also " +"inherit all other methods and attributes from the underlying stream." +msgstr "" + +#: ../Doc/library/codecs.rst:703 +msgid "StreamReader Objects" +msgstr "" + +#: ../Doc/library/codecs.rst:705 +msgid "" +"The :class:`StreamReader` class is a subclass of :class:`Codec` and defines " +"the following methods which every stream reader must define in order to be " +"compatible with the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:712 +msgid "Constructor for a :class:`StreamReader` instance." +msgstr "" + +#: ../Doc/library/codecs.rst:714 +msgid "" +"All stream readers must provide this constructor interface. They are free to " +"add additional keyword arguments, but only the ones defined here are used by " +"the Python codec registry." +msgstr "" + +#: ../Doc/library/codecs.rst:718 +msgid "" +"The *stream* argument must be a file-like object open for reading text or " +"binary data, as appropriate for the specific codec." +msgstr "" + +#: ../Doc/library/codecs.rst:721 +msgid "" +"The :class:`StreamReader` may implement different error handling schemes by " +"providing the *errors* keyword argument. See :ref:`error-handlers` for the " +"standard error handlers the underlying stream codec may support." +msgstr "" + +#: ../Doc/library/codecs.rst:725 +msgid "" +"The *errors* argument will be assigned to an attribute of the same name. " +"Assigning to this attribute makes it possible to switch between different " +"error handling strategies during the lifetime of the :class:`StreamReader` " +"object." +msgstr "" + +#: ../Doc/library/codecs.rst:729 +msgid "" +"The set of allowed values for the *errors* argument can be extended with :" +"func:`register_error`." +msgstr "" + +#: ../Doc/library/codecs.rst:735 +msgid "Decodes data from the stream and returns the resulting object." +msgstr "" + +#: ../Doc/library/codecs.rst:737 +msgid "" +"The *chars* argument indicates the number of decoded code points or bytes to " +"return. The :func:`read` method will never return more data than requested, " +"but it might return less, if there is not enough available." +msgstr "" + +#: ../Doc/library/codecs.rst:742 +msgid "" +"The *size* argument indicates the approximate maximum number of encoded " +"bytes or code points to read for decoding. The decoder can modify this " +"setting as appropriate. The default value -1 indicates to read and decode as " +"much as possible. This parameter is intended to prevent having to decode " +"huge files in one step." +msgstr "" + +#: ../Doc/library/codecs.rst:749 +msgid "" +"The *firstline* flag indicates that it would be sufficient to only return " +"the first line, if there are decoding errors on later lines." +msgstr "" + +#: ../Doc/library/codecs.rst:753 +msgid "" +"The method should use a greedy read strategy meaning that it should read as " +"much data as is allowed within the definition of the encoding and the given " +"size, e.g. if optional encoding endings or state markers are available on " +"the stream, these should be read too." +msgstr "" + +#: ../Doc/library/codecs.rst:761 +msgid "Read one line from the input stream and return the decoded data." +msgstr "" + +#: ../Doc/library/codecs.rst:763 +msgid "" +"*size*, if given, is passed as size argument to the stream's :meth:`read` " +"method." +msgstr "" + +#: ../Doc/library/codecs.rst:766 +msgid "" +"If *keepends* is false line-endings will be stripped from the lines returned." +msgstr "" + +#: ../Doc/library/codecs.rst:772 +msgid "" +"Read all lines available on the input stream and return them as a list of " +"lines." +msgstr "" + +#: ../Doc/library/codecs.rst:775 +msgid "" +"Line-endings are implemented using the codec's decoder method and are " +"included in the list entries if *keepends* is true." +msgstr "" + +#: ../Doc/library/codecs.rst:778 +msgid "" +"*sizehint*, if given, is passed as the *size* argument to the stream's :meth:" +"`read` method." +msgstr "" + +#: ../Doc/library/codecs.rst:784 +msgid "Resets the codec buffers used for keeping state." +msgstr "" + +#: ../Doc/library/codecs.rst:786 +msgid "" +"Note that no stream repositioning should take place. This method is " +"primarily intended to be able to recover from decoding errors." +msgstr "" + +#: ../Doc/library/codecs.rst:790 +msgid "" +"In addition to the above methods, the :class:`StreamReader` must also " +"inherit all other methods and attributes from the underlying stream." +msgstr "" + +#: ../Doc/library/codecs.rst:796 +msgid "StreamReaderWriter Objects" +msgstr "" + +#: ../Doc/library/codecs.rst:798 +msgid "" +"The :class:`StreamReaderWriter` is a convenience class that allows wrapping " +"streams which work in both read and write modes." +msgstr "" + +#: ../Doc/library/codecs.rst:801 ../Doc/library/codecs.rst:825 +msgid "" +"The design is such that one can use the factory functions returned by the :" +"func:`lookup` function to construct the instance." +msgstr "" + +#: ../Doc/library/codecs.rst:807 +msgid "" +"Creates a :class:`StreamReaderWriter` instance. *stream* must be a file-like " +"object. *Reader* and *Writer* must be factory functions or classes providing " +"the :class:`StreamReader` and :class:`StreamWriter` interface resp. Error " +"handling is done in the same way as defined for the stream readers and " +"writers." +msgstr "" + +#: ../Doc/library/codecs.rst:812 +msgid "" +":class:`StreamReaderWriter` instances define the combined interfaces of :" +"class:`StreamReader` and :class:`StreamWriter` classes. They inherit all " +"other methods and attributes from the underlying stream." +msgstr "" + +#: ../Doc/library/codecs.rst:820 +msgid "StreamRecoder Objects" +msgstr "" + +#: ../Doc/library/codecs.rst:822 +msgid "" +"The :class:`StreamRecoder` translates data from one encoding to another, " +"which is sometimes useful when dealing with different encoding environments." +msgstr "" + +#: ../Doc/library/codecs.rst:831 +msgid "" +"Creates a :class:`StreamRecoder` instance which implements a two-way " +"conversion: *encode* and *decode* work on the frontend — the data visible to " +"code calling :meth:`read` and :meth:`write`, while *Reader* and *Writer* " +"work on the backend — the data in *stream*." +msgstr "" + +#: ../Doc/library/codecs.rst:836 +msgid "" +"You can use these objects to do transparent transcodings from e.g. Latin-1 " +"to UTF-8 and back." +msgstr "" + +#: ../Doc/library/codecs.rst:839 +msgid "The *stream* argument must be a file-like object." +msgstr "" + +#: ../Doc/library/codecs.rst:841 +msgid "" +"The *encode* and *decode* arguments must adhere to the :class:`Codec` " +"interface. *Reader* and *Writer* must be factory functions or classes " +"providing objects of the :class:`StreamReader` and :class:`StreamWriter` " +"interface respectively." +msgstr "" + +#: ../Doc/library/codecs.rst:846 +msgid "" +"Error handling is done in the same way as defined for the stream readers and " +"writers." +msgstr "" + +#: ../Doc/library/codecs.rst:850 +msgid "" +":class:`StreamRecoder` instances define the combined interfaces of :class:" +"`StreamReader` and :class:`StreamWriter` classes. They inherit all other " +"methods and attributes from the underlying stream." +msgstr "" + +#: ../Doc/library/codecs.rst:858 +msgid "Encodings and Unicode" +msgstr "" + +#: ../Doc/library/codecs.rst:860 +msgid "" +"Strings are stored internally as sequences of code points in range ``0x0``-" +"``0x10FFFF``. (See :pep:`393` for more details about the implementation.) " +"Once a string object is used outside of CPU and memory, endianness and how " +"these arrays are stored as bytes become an issue. As with other codecs, " +"serialising a string into a sequence of bytes is known as *encoding*, and " +"recreating the string from the sequence of bytes is known as *decoding*. " +"There are a variety of different text serialisation codecs, which are " +"collectivity referred to as :term:`text encodings `." +msgstr "" + +#: ../Doc/library/codecs.rst:870 +msgid "" +"The simplest text encoding (called ``'latin-1'`` or ``'iso-8859-1'``) maps " +"the code points 0-255 to the bytes ``0x0``-``0xff``, which means that a " +"string object that contains code points above ``U+00FF`` can't be encoded " +"with this codec. Doing so will raise a :exc:`UnicodeEncodeError` that looks " +"like the following (although the details of the error message may differ): " +"``UnicodeEncodeError: 'latin-1' codec can't encode character '\\u1234' in " +"position 3: ordinal not in range(256)``." +msgstr "" + +#: ../Doc/library/codecs.rst:878 +msgid "" +"There's another group of encodings (the so called charmap encodings) that " +"choose a different subset of all Unicode code points and how these code " +"points are mapped to the bytes ``0x0``-``0xff``. To see how this is done " +"simply open e.g. :file:`encodings/cp1252.py` (which is an encoding that is " +"used primarily on Windows). There's a string constant with 256 characters " +"that shows you which character is mapped to which byte value." +msgstr "" + +#: ../Doc/library/codecs.rst:885 +msgid "" +"All of these encodings can only encode 256 of the 1114112 code points " +"defined in Unicode. A simple and straightforward way that can store each " +"Unicode code point, is to store each code point as four consecutive bytes. " +"There are two possibilities: store the bytes in big endian or in little " +"endian order. These two encodings are called ``UTF-32-BE`` and ``UTF-32-LE`` " +"respectively. Their disadvantage is that if e.g. you use ``UTF-32-BE`` on a " +"little endian machine you will always have to swap bytes on encoding and " +"decoding. ``UTF-32`` avoids this problem: bytes will always be in natural " +"endianness. When these bytes are read by a CPU with a different endianness, " +"then bytes have to be swapped though. To be able to detect the endianness of " +"a ``UTF-16`` or ``UTF-32`` byte sequence, there's the so called BOM (\"Byte " +"Order Mark\"). This is the Unicode character ``U+FEFF``. This character can " +"be prepended to every ``UTF-16`` or ``UTF-32`` byte sequence. The byte " +"swapped version of this character (``0xFFFE``) is an illegal character that " +"may not appear in a Unicode text. So when the first character in an " +"``UTF-16`` or ``UTF-32`` byte sequence appears to be a ``U+FFFE`` the bytes " +"have to be swapped on decoding. Unfortunately the character ``U+FEFF`` had a " +"second purpose as a ``ZERO WIDTH NO-BREAK SPACE``: a character that has no " +"width and doesn't allow a word to be split. It can e.g. be used to give " +"hints to a ligature algorithm. With Unicode 4.0 using ``U+FEFF`` as a ``ZERO " +"WIDTH NO-BREAK SPACE`` has been deprecated (with ``U+2060`` (``WORD " +"JOINER``) assuming this role). Nevertheless Unicode software still must be " +"able to handle ``U+FEFF`` in both roles: as a BOM it's a device to determine " +"the storage layout of the encoded bytes, and vanishes once the byte sequence " +"has been decoded into a string; as a ``ZERO WIDTH NO-BREAK SPACE`` it's a " +"normal character that will be decoded like any other." +msgstr "" + +#: ../Doc/library/codecs.rst:911 +msgid "" +"There's another encoding that is able to encoding the full range of Unicode " +"characters: UTF-8. UTF-8 is an 8-bit encoding, which means there are no " +"issues with byte order in UTF-8. Each byte in a UTF-8 byte sequence consists " +"of two parts: marker bits (the most significant bits) and payload bits. The " +"marker bits are a sequence of zero to four ``1`` bits followed by a ``0`` " +"bit. Unicode characters are encoded like this (with x being payload bits, " +"which when concatenated give the Unicode character):" +msgstr "" + +#: ../Doc/library/codecs.rst:920 +msgid "Range" +msgstr "" + +#: ../Doc/library/codecs.rst:920 +msgid "Encoding" +msgstr "" + +#: ../Doc/library/codecs.rst:922 +msgid "``U-00000000`` ... ``U-0000007F``" +msgstr "" + +#: ../Doc/library/codecs.rst:922 +msgid "0xxxxxxx" +msgstr "" + +#: ../Doc/library/codecs.rst:924 +msgid "``U-00000080`` ... ``U-000007FF``" +msgstr "" + +#: ../Doc/library/codecs.rst:924 +msgid "110xxxxx 10xxxxxx" +msgstr "" + +#: ../Doc/library/codecs.rst:926 +msgid "``U-00000800`` ... ``U-0000FFFF``" +msgstr "" + +#: ../Doc/library/codecs.rst:926 +msgid "1110xxxx 10xxxxxx 10xxxxxx" +msgstr "" + +#: ../Doc/library/codecs.rst:928 +msgid "``U-00010000`` ... ``U-0010FFFF``" +msgstr "" + +#: ../Doc/library/codecs.rst:928 +msgid "11110xxx 10xxxxxx 10xxxxxx 10xxxxxx" +msgstr "" + +#: ../Doc/library/codecs.rst:931 +msgid "" +"The least significant bit of the Unicode character is the rightmost x bit." +msgstr "" + +#: ../Doc/library/codecs.rst:933 +msgid "" +"As UTF-8 is an 8-bit encoding no BOM is required and any ``U+FEFF`` " +"character in the decoded string (even if it's the first character) is " +"treated as a ``ZERO WIDTH NO-BREAK SPACE``." +msgstr "" + +#: ../Doc/library/codecs.rst:937 +msgid "" +"Without external information it's impossible to reliably determine which " +"encoding was used for encoding a string. Each charmap encoding can decode " +"any random byte sequence. However that's not possible with UTF-8, as UTF-8 " +"byte sequences have a structure that doesn't allow arbitrary byte sequences. " +"To increase the reliability with which a UTF-8 encoding can be detected, " +"Microsoft invented a variant of UTF-8 (that Python 2.5 calls ``\"utf-8-sig" +"\"``) for its Notepad program: Before any of the Unicode characters is " +"written to the file, a UTF-8 encoded BOM (which looks like this as a byte " +"sequence: ``0xef``, ``0xbb``, ``0xbf``) is written. As it's rather " +"improbable that any charmap encoded file starts with these byte values " +"(which would e.g. map to" +msgstr "" + +#: ../Doc/library/codecs.rst:0 +msgid "LATIN SMALL LETTER I WITH DIAERESIS" +msgstr "" + +#: ../Doc/library/codecs.rst:0 +msgid "RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK" +msgstr "" + +#: ../Doc/library/codecs.rst:0 +msgid "INVERTED QUESTION MARK" +msgstr "" + +#: ../Doc/library/codecs.rst:953 +msgid "" +"in iso-8859-1), this increases the probability that a ``utf-8-sig`` encoding " +"can be correctly guessed from the byte sequence. So here the BOM is not used " +"to be able to determine the byte order used for generating the byte " +"sequence, but as a signature that helps in guessing the encoding. On " +"encoding the utf-8-sig codec will write ``0xef``, ``0xbb``, ``0xbf`` as the " +"first three bytes to the file. On decoding ``utf-8-sig`` will skip those " +"three bytes if they appear as the first three bytes in the file. In UTF-8, " +"the use of the BOM is discouraged and should generally be avoided." +msgstr "" + +#: ../Doc/library/codecs.rst:966 +msgid "Standard Encodings" +msgstr "" + +#: ../Doc/library/codecs.rst:968 +msgid "" +"Python comes with a number of codecs built-in, either implemented as C " +"functions or with dictionaries as mapping tables. The following table lists " +"the codecs by name, together with a few common aliases, and the languages " +"for which the encoding is likely used. Neither the list of aliases nor the " +"list of languages is meant to be exhaustive. Notice that spelling " +"alternatives that only differ in case or use a hyphen instead of an " +"underscore are also valid aliases; therefore, e.g. ``'utf-8'`` is a valid " +"alias for the ``'utf_8'`` codec." +msgstr "" + +#: ../Doc/library/codecs.rst:978 +msgid "" +"Some common encodings can bypass the codecs lookup machinery to improve " +"performance. These optimization opportunities are only recognized by " +"CPython for a limited set of aliases: utf-8, utf8, latin-1, latin1, " +"iso-8859-1, mbcs (Windows only), ascii, utf-16, and utf-32. Using " +"alternative spellings for these encodings may result in slower execution." +msgstr "" + +#: ../Doc/library/codecs.rst:985 +msgid "" +"Many of the character sets support the same languages. They vary in " +"individual characters (e.g. whether the EURO SIGN is supported or not), and " +"in the assignment of characters to code positions. For the European " +"languages in particular, the following variants typically exist:" +msgstr "" + +#: ../Doc/library/codecs.rst:990 +msgid "an ISO 8859 codeset" +msgstr "" + +#: ../Doc/library/codecs.rst:992 +msgid "" +"a Microsoft Windows code page, which is typically derived from an 8859 " +"codeset, but replaces control characters with additional graphic characters" +msgstr "" + +#: ../Doc/library/codecs.rst:995 +msgid "an IBM EBCDIC code page" +msgstr "" + +#: ../Doc/library/codecs.rst:997 +msgid "an IBM PC code page, which is ASCII compatible" +msgstr "" + +#: ../Doc/library/codecs.rst:1002 ../Doc/library/codecs.rst:1258 +#: ../Doc/library/codecs.rst:1331 ../Doc/library/codecs.rst:1386 +msgid "Codec" +msgstr "" + +#: ../Doc/library/codecs.rst:1002 ../Doc/library/codecs.rst:1258 +#: ../Doc/library/codecs.rst:1331 ../Doc/library/codecs.rst:1386 +msgid "Aliases" +msgstr "" + +#: ../Doc/library/codecs.rst:1002 +msgid "Languages" +msgstr "" + +#: ../Doc/library/codecs.rst:1004 +msgid "ascii" +msgstr "" + +#: ../Doc/library/codecs.rst:1004 +msgid "646, us-ascii" +msgstr "" + +#: ../Doc/library/codecs.rst:1004 ../Doc/library/codecs.rst:1010 +#: ../Doc/library/codecs.rst:1018 +msgid "English" +msgstr "" + +#: ../Doc/library/codecs.rst:1006 +msgid "big5" +msgstr "" + +#: ../Doc/library/codecs.rst:1006 +msgid "big5-tw, csbig5" +msgstr "" + +#: ../Doc/library/codecs.rst:1006 ../Doc/library/codecs.rst:1008 +#: ../Doc/library/codecs.rst:1066 +msgid "Traditional Chinese" +msgstr "" + +#: ../Doc/library/codecs.rst:1008 +msgid "big5hkscs" +msgstr "" + +#: ../Doc/library/codecs.rst:1008 +msgid "big5-hkscs, hkscs" +msgstr "" + +#: ../Doc/library/codecs.rst:1010 +msgid "cp037" +msgstr "" + +#: ../Doc/library/codecs.rst:1010 +msgid "IBM037, IBM039" +msgstr "" + +#: ../Doc/library/codecs.rst:1012 +msgid "cp273" +msgstr "" + +#: ../Doc/library/codecs.rst:1012 +msgid "273, IBM273, csIBM273" +msgstr "" + +#: ../Doc/library/codecs.rst:1012 +msgid "German" +msgstr "" + +#: ../Doc/library/codecs.rst:1016 +msgid "cp424" +msgstr "" + +#: ../Doc/library/codecs.rst:1016 +msgid "EBCDIC-CP-HE, IBM424" +msgstr "" + +#: ../Doc/library/codecs.rst:1016 ../Doc/library/codecs.rst:1036 +#: ../Doc/library/codecs.rst:1046 ../Doc/library/codecs.rst:1089 +#: ../Doc/library/codecs.rst:1157 +msgid "Hebrew" +msgstr "" + +#: ../Doc/library/codecs.rst:1018 +msgid "cp437" +msgstr "" + +#: ../Doc/library/codecs.rst:1018 +msgid "437, IBM437" +msgstr "" + +#: ../Doc/library/codecs.rst:1020 +msgid "cp500" +msgstr "" + +#: ../Doc/library/codecs.rst:1020 +msgid "EBCDIC-CP-BE, EBCDIC-CP-CH, IBM500" +msgstr "" + +#: ../Doc/library/codecs.rst:1020 ../Doc/library/codecs.rst:1029 +#: ../Doc/library/codecs.rst:1040 ../Doc/library/codecs.rst:1076 +#: ../Doc/library/codecs.rst:1083 ../Doc/library/codecs.rst:1169 +#: ../Doc/library/codecs.rst:1196 +msgid "Western Europe" +msgstr "" + +#: ../Doc/library/codecs.rst:1023 +msgid "cp720" +msgstr "" + +#: ../Doc/library/codecs.rst:1023 ../Doc/library/codecs.rst:1050 +#: ../Doc/library/codecs.rst:1091 ../Doc/library/codecs.rst:1153 +msgid "Arabic" +msgstr "" + +#: ../Doc/library/codecs.rst:1025 +msgid "cp737" +msgstr "" + +#: ../Doc/library/codecs.rst:1025 ../Doc/library/codecs.rst:1056 +#: ../Doc/library/codecs.rst:1060 ../Doc/library/codecs.rst:1085 +#: ../Doc/library/codecs.rst:1155 ../Doc/library/codecs.rst:1190 +msgid "Greek" +msgstr "" + +#: ../Doc/library/codecs.rst:1027 +msgid "cp775" +msgstr "" + +#: ../Doc/library/codecs.rst:1027 +msgid "IBM775" +msgstr "" + +#: ../Doc/library/codecs.rst:1027 ../Doc/library/codecs.rst:1093 +#: ../Doc/library/codecs.rst:1148 ../Doc/library/codecs.rst:1165 +msgid "Baltic languages" +msgstr "" + +#: ../Doc/library/codecs.rst:1029 +msgid "cp850" +msgstr "" + +#: ../Doc/library/codecs.rst:1029 +msgid "850, IBM850" +msgstr "" + +#: ../Doc/library/codecs.rst:1031 +msgid "cp852" +msgstr "" + +#: ../Doc/library/codecs.rst:1031 +msgid "852, IBM852" +msgstr "" + +#: ../Doc/library/codecs.rst:1031 ../Doc/library/codecs.rst:1078 +#: ../Doc/library/codecs.rst:1144 ../Doc/library/codecs.rst:1194 +msgid "Central and Eastern Europe" +msgstr "" + +#: ../Doc/library/codecs.rst:1033 +msgid "cp855" +msgstr "" + +#: ../Doc/library/codecs.rst:1033 +msgid "855, IBM855" +msgstr "" + +#: ../Doc/library/codecs.rst:1033 ../Doc/library/codecs.rst:1080 +#: ../Doc/library/codecs.rst:1150 ../Doc/library/codecs.rst:1187 +msgid "Bulgarian, Byelorussian, Macedonian, Russian, Serbian" +msgstr "" + +#: ../Doc/library/codecs.rst:1036 +msgid "cp856" +msgstr "" + +#: ../Doc/library/codecs.rst:1038 +msgid "cp857" +msgstr "" + +#: ../Doc/library/codecs.rst:1038 +msgid "857, IBM857" +msgstr "" + +#: ../Doc/library/codecs.rst:1038 ../Doc/library/codecs.rst:1070 +#: ../Doc/library/codecs.rst:1087 ../Doc/library/codecs.rst:1159 +#: ../Doc/library/codecs.rst:1198 +msgid "Turkish" +msgstr "" + +#: ../Doc/library/codecs.rst:1040 +msgid "cp858" +msgstr "" + +#: ../Doc/library/codecs.rst:1040 +msgid "858, IBM858" +msgstr "" + +#: ../Doc/library/codecs.rst:1042 +msgid "cp860" +msgstr "" + +#: ../Doc/library/codecs.rst:1042 +msgid "860, IBM860" +msgstr "" + +#: ../Doc/library/codecs.rst:1042 +msgid "Portuguese" +msgstr "" + +#: ../Doc/library/codecs.rst:1044 +msgid "cp861" +msgstr "" + +#: ../Doc/library/codecs.rst:1044 +msgid "861, CP-IS, IBM861" +msgstr "" + +#: ../Doc/library/codecs.rst:1044 ../Doc/library/codecs.rst:1192 +msgid "Icelandic" +msgstr "" + +#: ../Doc/library/codecs.rst:1046 +msgid "cp862" +msgstr "" + +#: ../Doc/library/codecs.rst:1046 +msgid "862, IBM862" +msgstr "" + +#: ../Doc/library/codecs.rst:1048 +msgid "cp863" +msgstr "" + +#: ../Doc/library/codecs.rst:1048 +msgid "863, IBM863" +msgstr "" + +#: ../Doc/library/codecs.rst:1048 +msgid "Canadian" +msgstr "" + +#: ../Doc/library/codecs.rst:1050 +msgid "cp864" +msgstr "" + +#: ../Doc/library/codecs.rst:1050 +msgid "IBM864" +msgstr "" + +#: ../Doc/library/codecs.rst:1052 +msgid "cp865" +msgstr "" + +#: ../Doc/library/codecs.rst:1052 +msgid "865, IBM865" +msgstr "" + +#: ../Doc/library/codecs.rst:1052 +msgid "Danish, Norwegian" +msgstr "" + +#: ../Doc/library/codecs.rst:1054 +msgid "cp866" +msgstr "" + +#: ../Doc/library/codecs.rst:1054 +msgid "866, IBM866" +msgstr "" + +#: ../Doc/library/codecs.rst:1054 ../Doc/library/codecs.rst:1175 +msgid "Russian" +msgstr "" + +#: ../Doc/library/codecs.rst:1056 +msgid "cp869" +msgstr "" + +#: ../Doc/library/codecs.rst:1056 +msgid "869, CP-GR, IBM869" +msgstr "" + +#: ../Doc/library/codecs.rst:1058 +msgid "cp874" +msgstr "" + +#: ../Doc/library/codecs.rst:1058 +msgid "Thai" +msgstr "" + +#: ../Doc/library/codecs.rst:1060 +msgid "cp875" +msgstr "" + +#: ../Doc/library/codecs.rst:1062 +msgid "cp932" +msgstr "" + +#: ../Doc/library/codecs.rst:1062 +msgid "932, ms932, mskanji, ms-kanji" +msgstr "" + +#: ../Doc/library/codecs.rst:1062 ../Doc/library/codecs.rst:1102 +#: ../Doc/library/codecs.rst:1104 ../Doc/library/codecs.rst:1106 +#: ../Doc/library/codecs.rst:1123 ../Doc/library/codecs.rst:1126 +#: ../Doc/library/codecs.rst:1131 ../Doc/library/codecs.rst:1134 +#: ../Doc/library/codecs.rst:1136 ../Doc/library/codecs.rst:1203 +#: ../Doc/library/codecs.rst:1206 ../Doc/library/codecs.rst:1209 +msgid "Japanese" +msgstr "" + +#: ../Doc/library/codecs.rst:1064 +msgid "cp949" +msgstr "" + +#: ../Doc/library/codecs.rst:1064 +msgid "949, ms949, uhc" +msgstr "" + +#: ../Doc/library/codecs.rst:1064 ../Doc/library/codecs.rst:1108 +#: ../Doc/library/codecs.rst:1138 ../Doc/library/codecs.rst:1173 +msgid "Korean" +msgstr "" + +#: ../Doc/library/codecs.rst:1066 +msgid "cp950" +msgstr "" + +#: ../Doc/library/codecs.rst:1066 +msgid "950, ms950" +msgstr "" + +#: ../Doc/library/codecs.rst:1068 +msgid "cp1006" +msgstr "" + +#: ../Doc/library/codecs.rst:1068 +msgid "Urdu" +msgstr "" + +#: ../Doc/library/codecs.rst:1070 +msgid "cp1026" +msgstr "" + +#: ../Doc/library/codecs.rst:1070 +msgid "ibm1026" +msgstr "" + +#: ../Doc/library/codecs.rst:1072 +msgid "cp1125" +msgstr "" + +#: ../Doc/library/codecs.rst:1072 +msgid "1125, ibm1125, cp866u, ruscii" +msgstr "" + +#: ../Doc/library/codecs.rst:1072 ../Doc/library/codecs.rst:1181 +msgid "Ukrainian" +msgstr "" + +#: ../Doc/library/codecs.rst:1076 +msgid "cp1140" +msgstr "" + +#: ../Doc/library/codecs.rst:1076 +msgid "ibm1140" +msgstr "" + +#: ../Doc/library/codecs.rst:1078 +msgid "cp1250" +msgstr "" + +#: ../Doc/library/codecs.rst:1078 +msgid "windows-1250" +msgstr "" + +#: ../Doc/library/codecs.rst:1080 +msgid "cp1251" +msgstr "" + +#: ../Doc/library/codecs.rst:1080 +msgid "windows-1251" +msgstr "" + +#: ../Doc/library/codecs.rst:1083 +msgid "cp1252" +msgstr "" + +#: ../Doc/library/codecs.rst:1083 +msgid "windows-1252" +msgstr "" + +#: ../Doc/library/codecs.rst:1085 +msgid "cp1253" +msgstr "" + +#: ../Doc/library/codecs.rst:1085 +msgid "windows-1253" +msgstr "" + +#: ../Doc/library/codecs.rst:1087 +msgid "cp1254" +msgstr "" + +#: ../Doc/library/codecs.rst:1087 +msgid "windows-1254" +msgstr "" + +#: ../Doc/library/codecs.rst:1089 +msgid "cp1255" +msgstr "" + +#: ../Doc/library/codecs.rst:1089 +msgid "windows-1255" +msgstr "" + +#: ../Doc/library/codecs.rst:1091 +msgid "cp1256" +msgstr "" + +#: ../Doc/library/codecs.rst:1091 +msgid "windows-1256" +msgstr "" + +#: ../Doc/library/codecs.rst:1093 +msgid "cp1257" +msgstr "" + +#: ../Doc/library/codecs.rst:1093 +msgid "windows-1257" +msgstr "" + +#: ../Doc/library/codecs.rst:1095 +msgid "cp1258" +msgstr "" + +#: ../Doc/library/codecs.rst:1095 +msgid "windows-1258" +msgstr "" + +#: ../Doc/library/codecs.rst:1095 +msgid "Vietnamese" +msgstr "" + +#: ../Doc/library/codecs.rst:1097 +msgid "cp65001" +msgstr "" + +#: ../Doc/library/codecs.rst:1097 +msgid "Windows only: Windows UTF-8 (``CP_UTF8``)" +msgstr "" + +#: ../Doc/library/codecs.rst:1102 +msgid "euc_jp" +msgstr "" + +#: ../Doc/library/codecs.rst:1102 +msgid "eucjp, ujis, u-jis" +msgstr "" + +#: ../Doc/library/codecs.rst:1104 +msgid "euc_jis_2004" +msgstr "" + +#: ../Doc/library/codecs.rst:1104 +msgid "jisx0213, eucjis2004" +msgstr "" + +#: ../Doc/library/codecs.rst:1106 +msgid "euc_jisx0213" +msgstr "" + +#: ../Doc/library/codecs.rst:1106 +msgid "eucjisx0213" +msgstr "" + +#: ../Doc/library/codecs.rst:1108 +msgid "euc_kr" +msgstr "" + +#: ../Doc/library/codecs.rst:1108 +msgid "euckr, korean, ksc5601, ks_c-5601, ks_c-5601-1987, ksx1001, ks_x-1001" +msgstr "" + +#: ../Doc/library/codecs.rst:1112 +msgid "gb2312" +msgstr "" + +#: ../Doc/library/codecs.rst:1112 +msgid "" +"chinese, csiso58gb231280, euc- cn, euccn, eucgb2312-cn, gb2312-1980, " +"gb2312-80, iso- ir-58" +msgstr "" + +#: ../Doc/library/codecs.rst:1112 ../Doc/library/codecs.rst:1121 +msgid "Simplified Chinese" +msgstr "" + +#: ../Doc/library/codecs.rst:1117 +msgid "gbk" +msgstr "" + +#: ../Doc/library/codecs.rst:1117 +msgid "936, cp936, ms936" +msgstr "" + +#: ../Doc/library/codecs.rst:1117 ../Doc/library/codecs.rst:1119 +msgid "Unified Chinese" +msgstr "" + +#: ../Doc/library/codecs.rst:1119 +msgid "gb18030" +msgstr "" + +#: ../Doc/library/codecs.rst:1119 +msgid "gb18030-2000" +msgstr "" + +#: ../Doc/library/codecs.rst:1121 +msgid "hz" +msgstr "" + +#: ../Doc/library/codecs.rst:1121 +msgid "hzgb, hz-gb, hz-gb-2312" +msgstr "" + +#: ../Doc/library/codecs.rst:1123 +msgid "iso2022_jp" +msgstr "" + +#: ../Doc/library/codecs.rst:1123 +msgid "csiso2022jp, iso2022jp, iso-2022-jp" +msgstr "" + +#: ../Doc/library/codecs.rst:1126 +msgid "iso2022_jp_1" +msgstr "" + +#: ../Doc/library/codecs.rst:1126 +msgid "iso2022jp-1, iso-2022-jp-1" +msgstr "" + +#: ../Doc/library/codecs.rst:1128 +msgid "iso2022_jp_2" +msgstr "" + +#: ../Doc/library/codecs.rst:1128 +msgid "iso2022jp-2, iso-2022-jp-2" +msgstr "" + +#: ../Doc/library/codecs.rst:1128 +msgid "Japanese, Korean, Simplified Chinese, Western Europe, Greek" +msgstr "" + +#: ../Doc/library/codecs.rst:1131 +msgid "iso2022_jp_2004" +msgstr "" + +#: ../Doc/library/codecs.rst:1131 +msgid "iso2022jp-2004, iso-2022-jp-2004" +msgstr "" + +#: ../Doc/library/codecs.rst:1134 +msgid "iso2022_jp_3" +msgstr "" + +#: ../Doc/library/codecs.rst:1134 +msgid "iso2022jp-3, iso-2022-jp-3" +msgstr "" + +#: ../Doc/library/codecs.rst:1136 +msgid "iso2022_jp_ext" +msgstr "" + +#: ../Doc/library/codecs.rst:1136 +msgid "iso2022jp-ext, iso-2022-jp-ext" +msgstr "" + +#: ../Doc/library/codecs.rst:1138 +msgid "iso2022_kr" +msgstr "" + +#: ../Doc/library/codecs.rst:1138 +msgid "csiso2022kr, iso2022kr, iso-2022-kr" +msgstr "" + +#: ../Doc/library/codecs.rst:1141 +msgid "latin_1" +msgstr "" + +#: ../Doc/library/codecs.rst:1141 +msgid "iso-8859-1, iso8859-1, 8859, cp819, latin, latin1, L1" +msgstr "" + +#: ../Doc/library/codecs.rst:1141 +msgid "West Europe" +msgstr "" + +#: ../Doc/library/codecs.rst:1144 +msgid "iso8859_2" +msgstr "" + +#: ../Doc/library/codecs.rst:1144 +msgid "iso-8859-2, latin2, L2" +msgstr "" + +#: ../Doc/library/codecs.rst:1146 +msgid "iso8859_3" +msgstr "" + +#: ../Doc/library/codecs.rst:1146 +msgid "iso-8859-3, latin3, L3" +msgstr "" + +#: ../Doc/library/codecs.rst:1146 +msgid "Esperanto, Maltese" +msgstr "" + +#: ../Doc/library/codecs.rst:1148 +msgid "iso8859_4" +msgstr "" + +#: ../Doc/library/codecs.rst:1148 +msgid "iso-8859-4, latin4, L4" +msgstr "" + +#: ../Doc/library/codecs.rst:1150 +msgid "iso8859_5" +msgstr "" + +#: ../Doc/library/codecs.rst:1150 +msgid "iso-8859-5, cyrillic" +msgstr "" + +#: ../Doc/library/codecs.rst:1153 +msgid "iso8859_6" +msgstr "" + +#: ../Doc/library/codecs.rst:1153 +msgid "iso-8859-6, arabic" +msgstr "" + +#: ../Doc/library/codecs.rst:1155 +msgid "iso8859_7" +msgstr "" + +#: ../Doc/library/codecs.rst:1155 +msgid "iso-8859-7, greek, greek8" +msgstr "" + +#: ../Doc/library/codecs.rst:1157 +msgid "iso8859_8" +msgstr "" + +#: ../Doc/library/codecs.rst:1157 +msgid "iso-8859-8, hebrew" +msgstr "" + +#: ../Doc/library/codecs.rst:1159 +msgid "iso8859_9" +msgstr "" + +#: ../Doc/library/codecs.rst:1159 +msgid "iso-8859-9, latin5, L5" +msgstr "" + +#: ../Doc/library/codecs.rst:1161 +msgid "iso8859_10" +msgstr "" + +#: ../Doc/library/codecs.rst:1161 +msgid "iso-8859-10, latin6, L6" +msgstr "" + +#: ../Doc/library/codecs.rst:1161 +msgid "Nordic languages" +msgstr "" + +#: ../Doc/library/codecs.rst:1163 +msgid "iso8859_11" +msgstr "" + +#: ../Doc/library/codecs.rst:1163 +msgid "iso-8859-11, thai" +msgstr "" + +#: ../Doc/library/codecs.rst:1163 +msgid "Thai languages" +msgstr "" + +#: ../Doc/library/codecs.rst:1165 +msgid "iso8859_13" +msgstr "" + +#: ../Doc/library/codecs.rst:1165 +msgid "iso-8859-13, latin7, L7" +msgstr "" + +#: ../Doc/library/codecs.rst:1167 +msgid "iso8859_14" +msgstr "" + +#: ../Doc/library/codecs.rst:1167 +msgid "iso-8859-14, latin8, L8" +msgstr "" + +#: ../Doc/library/codecs.rst:1167 +msgid "Celtic languages" +msgstr "" + +#: ../Doc/library/codecs.rst:1169 +msgid "iso8859_15" +msgstr "" + +#: ../Doc/library/codecs.rst:1169 +msgid "iso-8859-15, latin9, L9" +msgstr "" + +#: ../Doc/library/codecs.rst:1171 +msgid "iso8859_16" +msgstr "" + +#: ../Doc/library/codecs.rst:1171 +msgid "iso-8859-16, latin10, L10" +msgstr "" + +#: ../Doc/library/codecs.rst:1171 +msgid "South-Eastern Europe" +msgstr "" + +#: ../Doc/library/codecs.rst:1173 +msgid "johab" +msgstr "" + +#: ../Doc/library/codecs.rst:1173 +msgid "cp1361, ms1361" +msgstr "" + +#: ../Doc/library/codecs.rst:1175 +msgid "koi8_r" +msgstr "" + +#: ../Doc/library/codecs.rst:1177 +msgid "koi8_t" +msgstr "" + +#: ../Doc/library/codecs.rst:1177 +msgid "Tajik" +msgstr "" + +#: ../Doc/library/codecs.rst:1181 +msgid "koi8_u" +msgstr "" + +#: ../Doc/library/codecs.rst:1183 +msgid "kz1048" +msgstr "" + +#: ../Doc/library/codecs.rst:1183 +msgid "kz_1048, strk1048_2002, rk1048" +msgstr "" + +#: ../Doc/library/codecs.rst:1183 ../Doc/library/codecs.rst:1200 +msgid "Kazakh" +msgstr "" + +#: ../Doc/library/codecs.rst:1187 +msgid "mac_cyrillic" +msgstr "" + +#: ../Doc/library/codecs.rst:1187 +msgid "maccyrillic" +msgstr "" + +#: ../Doc/library/codecs.rst:1190 +msgid "mac_greek" +msgstr "" + +#: ../Doc/library/codecs.rst:1190 +msgid "macgreek" +msgstr "" + +#: ../Doc/library/codecs.rst:1192 +msgid "mac_iceland" +msgstr "" + +#: ../Doc/library/codecs.rst:1192 +msgid "maciceland" +msgstr "" + +#: ../Doc/library/codecs.rst:1194 +msgid "mac_latin2" +msgstr "" + +#: ../Doc/library/codecs.rst:1194 +msgid "maclatin2, maccentraleurope" +msgstr "" + +#: ../Doc/library/codecs.rst:1196 +msgid "mac_roman" +msgstr "" + +#: ../Doc/library/codecs.rst:1196 +msgid "macroman, macintosh" +msgstr "" + +#: ../Doc/library/codecs.rst:1198 +msgid "mac_turkish" +msgstr "" + +#: ../Doc/library/codecs.rst:1198 +msgid "macturkish" +msgstr "" + +#: ../Doc/library/codecs.rst:1200 +msgid "ptcp154" +msgstr "" + +#: ../Doc/library/codecs.rst:1200 +msgid "csptcp154, pt154, cp154, cyrillic-asian" +msgstr "" + +#: ../Doc/library/codecs.rst:1203 +msgid "shift_jis" +msgstr "" + +#: ../Doc/library/codecs.rst:1203 +msgid "csshiftjis, shiftjis, sjis, s_jis" +msgstr "" + +#: ../Doc/library/codecs.rst:1206 +msgid "shift_jis_2004" +msgstr "" + +#: ../Doc/library/codecs.rst:1206 +msgid "shiftjis2004, sjis_2004, sjis2004" +msgstr "" + +#: ../Doc/library/codecs.rst:1209 +msgid "shift_jisx0213" +msgstr "" + +#: ../Doc/library/codecs.rst:1209 +msgid "shiftjisx0213, sjisx0213, s_jisx0213" +msgstr "" + +#: ../Doc/library/codecs.rst:1212 +msgid "utf_32" +msgstr "" + +#: ../Doc/library/codecs.rst:1212 +msgid "U32, utf32" +msgstr "" + +#: ../Doc/library/codecs.rst:1212 ../Doc/library/codecs.rst:1214 +#: ../Doc/library/codecs.rst:1216 ../Doc/library/codecs.rst:1218 +#: ../Doc/library/codecs.rst:1220 ../Doc/library/codecs.rst:1222 +#: ../Doc/library/codecs.rst:1224 ../Doc/library/codecs.rst:1226 +#: ../Doc/library/codecs.rst:1228 +msgid "all languages" +msgstr "" + +#: ../Doc/library/codecs.rst:1214 +msgid "utf_32_be" +msgstr "" + +#: ../Doc/library/codecs.rst:1214 +msgid "UTF-32BE" +msgstr "" + +#: ../Doc/library/codecs.rst:1216 +msgid "utf_32_le" +msgstr "" + +#: ../Doc/library/codecs.rst:1216 +msgid "UTF-32LE" +msgstr "" + +#: ../Doc/library/codecs.rst:1218 +msgid "utf_16" +msgstr "" + +#: ../Doc/library/codecs.rst:1218 +msgid "U16, utf16" +msgstr "" + +#: ../Doc/library/codecs.rst:1220 +msgid "utf_16_be" +msgstr "" + +#: ../Doc/library/codecs.rst:1220 +msgid "UTF-16BE" +msgstr "" + +#: ../Doc/library/codecs.rst:1222 +msgid "utf_16_le" +msgstr "" + +#: ../Doc/library/codecs.rst:1222 +msgid "UTF-16LE" +msgstr "" + +#: ../Doc/library/codecs.rst:1224 +msgid "utf_7" +msgstr "" + +#: ../Doc/library/codecs.rst:1224 +msgid "U7, unicode-1-1-utf-7" +msgstr "" + +#: ../Doc/library/codecs.rst:1226 +msgid "utf_8" +msgstr "" + +#: ../Doc/library/codecs.rst:1226 +msgid "U8, UTF, utf8" +msgstr "" + +#: ../Doc/library/codecs.rst:1228 +msgid "utf_8_sig" +msgstr "" + +#: ../Doc/library/codecs.rst:1231 +msgid "" +"The utf-16\\* and utf-32\\* encoders no longer allow surrogate code points " +"(``U+D800``--``U+DFFF``) to be encoded. The utf-32\\* decoders no longer " +"decode byte sequences that correspond to surrogate code points." +msgstr "" + +#: ../Doc/library/codecs.rst:1239 +msgid "Python Specific Encodings" +msgstr "" + +#: ../Doc/library/codecs.rst:1241 +msgid "" +"A number of predefined codecs are specific to Python, so their codec names " +"have no meaning outside Python. These are listed in the tables below based " +"on the expected input and output types (note that while text encodings are " +"the most common use case for codecs, the underlying codec infrastructure " +"supports arbitrary data transforms rather than just text encodings). For " +"asymmetric codecs, the stated purpose describes the encoding direction." +msgstr "" + +#: ../Doc/library/codecs.rst:1249 +msgid "Text Encodings" +msgstr "" + +#: ../Doc/library/codecs.rst:1251 +msgid "" +"The following codecs provide :class:`str` to :class:`bytes` encoding and :" +"term:`bytes-like object` to :class:`str` decoding, similar to the Unicode " +"text encodings." +msgstr "" + +#: ../Doc/library/codecs.rst:1258 ../Doc/library/codecs.rst:1331 +#: ../Doc/library/codecs.rst:1386 ../Doc/library/xml.dom.rst:162 +msgid "Purpose" +msgstr "" + +#: ../Doc/library/codecs.rst:1260 +msgid "idna" +msgstr "" + +#: ../Doc/library/codecs.rst:1260 +msgid "" +"Implements :rfc:`3490`, see also :mod:`encodings.idna`. Only " +"``errors='strict'`` is supported." +msgstr "" + +#: ../Doc/library/codecs.rst:1266 +msgid "mbcs" +msgstr "" + +#: ../Doc/library/codecs.rst:1266 +msgid "ansi, dbcs" +msgstr "" + +#: ../Doc/library/codecs.rst:1266 +msgid "Windows only: Encode operand according to the ANSI codepage (CP_ACP)" +msgstr "" + +#: ../Doc/library/codecs.rst:1270 +msgid "oem" +msgstr "" + +#: ../Doc/library/codecs.rst:1270 +msgid "Windows only: Encode operand according to the OEM codepage (CP_OEMCP)" +msgstr "" + +#: ../Doc/library/codecs.rst:1276 +msgid "palmos" +msgstr "" + +#: ../Doc/library/codecs.rst:1276 +msgid "Encoding of PalmOS 3.5" +msgstr "" + +#: ../Doc/library/codecs.rst:1278 +msgid "punycode" +msgstr "" + +#: ../Doc/library/codecs.rst:1278 +msgid "Implements :rfc:`3492`. Stateful codecs are not supported." +msgstr "" + +#: ../Doc/library/codecs.rst:1282 +msgid "raw_unicode_escape" +msgstr "" + +#: ../Doc/library/codecs.rst:1282 +msgid "" +"Latin-1 encoding with ``\\uXXXX`` and ``\\UXXXXXXXX`` for other code points. " +"Existing backslashes are not escaped in any way. It is used in the Python " +"pickle protocol." +msgstr "" + +#: ../Doc/library/codecs.rst:1291 +msgid "undefined" +msgstr "" + +#: ../Doc/library/codecs.rst:1291 +msgid "" +"Raise an exception for all conversions, even empty strings. The error " +"handler is ignored." +msgstr "" + +#: ../Doc/library/codecs.rst:1296 +msgid "unicode_escape" +msgstr "" + +#: ../Doc/library/codecs.rst:1296 +msgid "" +"Encoding suitable as the contents of a Unicode literal in ASCII-encoded " +"Python source code, except that quotes are not escaped. Decodes from Latin-1 " +"source code. Beware that Python source code actually uses UTF-8 by default." +msgstr "" + +#: ../Doc/library/codecs.rst:1307 +msgid "unicode_internal" +msgstr "" + +#: ../Doc/library/codecs.rst:1307 +msgid "" +"Return the internal representation of the operand. Stateful codecs are not " +"supported." +msgstr "" + +#: ../Doc/library/codecs.rst:1312 +msgid "This representation is obsoleted by :pep:`393`." +msgstr "" + +#: ../Doc/library/codecs.rst:1321 +msgid "Binary Transforms" +msgstr "" + +#: ../Doc/library/codecs.rst:1323 +msgid "" +"The following codecs provide binary transforms: :term:`bytes-like object` " +"to :class:`bytes` mappings. They are not supported by :meth:`bytes.decode` " +"(which only produces :class:`str` output)." +msgstr "" + +#: ../Doc/library/codecs.rst:1331 +msgid "Encoder / decoder" +msgstr "" + +#: ../Doc/library/codecs.rst:1333 +msgid "base64_codec [#b64]_" +msgstr "" + +#: ../Doc/library/codecs.rst:1333 +msgid "base64, base_64" +msgstr "" + +#: ../Doc/library/codecs.rst:1333 +msgid "" +"Convert operand to multiline MIME base64 (the result always includes a " +"trailing ``'\\n'``)" +msgstr "" + +#: ../Doc/library/codecs.rst:1338 +msgid "" +"accepts any :term:`bytes-like object` as input for encoding and decoding" +msgstr "" + +#: ../Doc/library/codecs.rst:1333 +msgid ":meth:`base64.encodebytes` / :meth:`base64.decodebytes`" +msgstr "" + +#: ../Doc/library/codecs.rst:1344 +msgid "bz2_codec" +msgstr "" + +#: ../Doc/library/codecs.rst:1344 +msgid "bz2" +msgstr "" + +#: ../Doc/library/codecs.rst:1344 +msgid "Compress the operand using bz2" +msgstr "" + +#: ../Doc/library/codecs.rst:1344 +msgid ":meth:`bz2.compress` / :meth:`bz2.decompress`" +msgstr "" + +#: ../Doc/library/codecs.rst:1347 +msgid "hex_codec" +msgstr "" + +#: ../Doc/library/codecs.rst:1347 +msgid "hex" +msgstr "" + +#: ../Doc/library/codecs.rst:1347 +msgid "Convert operand to hexadecimal representation, with two digits per byte" +msgstr "" + +#: ../Doc/library/codecs.rst:1347 +msgid ":meth:`binascii.b2a_hex` / :meth:`binascii.a2b_hex`" +msgstr "" + +#: ../Doc/library/codecs.rst:1352 +msgid "quopri_codec" +msgstr "" + +#: ../Doc/library/codecs.rst:1352 +msgid "quopri, quotedprintable, quoted_printable" +msgstr "" + +#: ../Doc/library/codecs.rst:1352 +msgid "Convert operand to MIME quoted printable" +msgstr "" + +#: ../Doc/library/codecs.rst:1352 +msgid ":meth:`quopri.encode` with ``quotetabs=True`` / :meth:`quopri.decode`" +msgstr "" + +#: ../Doc/library/codecs.rst:1356 +msgid "uu_codec" +msgstr "" + +#: ../Doc/library/codecs.rst:1356 +msgid "uu" +msgstr "" + +#: ../Doc/library/codecs.rst:1356 +msgid "Convert the operand using uuencode" +msgstr "" + +#: ../Doc/library/codecs.rst:1356 +msgid ":meth:`uu.encode` / :meth:`uu.decode`" +msgstr "" + +#: ../Doc/library/codecs.rst:1359 +msgid "zlib_codec" +msgstr "" + +#: ../Doc/library/codecs.rst:1359 +msgid "zip, zlib" +msgstr "" + +#: ../Doc/library/codecs.rst:1359 +msgid "Compress the operand using gzip" +msgstr "" + +#: ../Doc/library/codecs.rst:1359 +msgid ":meth:`zlib.compress` / :meth:`zlib.decompress`" +msgstr "" + +#: ../Doc/library/codecs.rst:1363 +msgid "" +"In addition to :term:`bytes-like objects `, " +"``'base64_codec'`` also accepts ASCII-only instances of :class:`str` for " +"decoding" +msgstr "" + +#: ../Doc/library/codecs.rst:1367 +msgid "Restoration of the binary transforms." +msgstr "" + +#: ../Doc/library/codecs.rst:1370 +msgid "Restoration of the aliases for the binary transforms." +msgstr "" + +#: ../Doc/library/codecs.rst:1377 +msgid "Text Transforms" +msgstr "" + +#: ../Doc/library/codecs.rst:1379 +msgid "" +"The following codec provides a text transform: a :class:`str` to :class:" +"`str` mapping. It is not supported by :meth:`str.encode` (which only " +"produces :class:`bytes` output)." +msgstr "" + +#: ../Doc/library/codecs.rst:1388 +msgid "rot_13" +msgstr "" + +#: ../Doc/library/codecs.rst:1388 +msgid "rot13" +msgstr "" + +#: ../Doc/library/codecs.rst:1388 +msgid "Returns the Caesar-cypher encryption of the operand" +msgstr "" + +#: ../Doc/library/codecs.rst:1392 +msgid "Restoration of the ``rot_13`` text transform." +msgstr "" + +#: ../Doc/library/codecs.rst:1395 +msgid "Restoration of the ``rot13`` alias." +msgstr "" + +#: ../Doc/library/codecs.rst:1400 +msgid "" +":mod:`encodings.idna` --- Internationalized Domain Names in Applications" +msgstr "" + +#: ../Doc/library/codecs.rst:1406 +msgid "" +"This module implements :rfc:`3490` (Internationalized Domain Names in " +"Applications) and :rfc:`3492` (Nameprep: A Stringprep Profile for " +"Internationalized Domain Names (IDN)). It builds upon the ``punycode`` " +"encoding and :mod:`stringprep`." +msgstr "" + +#: ../Doc/library/codecs.rst:1411 +msgid "" +"These RFCs together define a protocol to support non-ASCII characters in " +"domain names. A domain name containing non-ASCII characters (such as ``www." +"Alliancefrançaise.nu``) is converted into an ASCII-compatible encoding (ACE, " +"such as ``www.xn--alliancefranaise-npb.nu``). The ACE form of the domain " +"name is then used in all places where arbitrary characters are not allowed " +"by the protocol, such as DNS queries, HTTP :mailheader:`Host` fields, and so " +"on. This conversion is carried out in the application; if possible invisible " +"to the user: The application should transparently convert Unicode domain " +"labels to IDNA on the wire, and convert back ACE labels to Unicode before " +"presenting them to the user." +msgstr "" + +#: ../Doc/library/codecs.rst:1422 +msgid "" +"Python supports this conversion in several ways: the ``idna`` codec " +"performs conversion between Unicode and ACE, separating an input string into " +"labels based on the separator characters defined in `section 3.1`_ (1) of :" +"rfc:`3490` and converting each label to ACE as required, and conversely " +"separating an input byte string into labels based on the ``.`` separator and " +"converting any ACE labels found into unicode. Furthermore, the :mod:" +"`socket` module transparently converts Unicode host names to ACE, so that " +"applications need not be concerned about converting host names themselves " +"when they pass them to the socket module. On top of that, modules that have " +"host names as function parameters, such as :mod:`http.client` and :mod:" +"`ftplib`, accept Unicode host names (:mod:`http.client` then also " +"transparently sends an IDNA hostname in the :mailheader:`Host` field if it " +"sends that field at all)." +msgstr "" + +#: ../Doc/library/codecs.rst:1437 +msgid "" +"When receiving host names from the wire (such as in reverse name lookup), no " +"automatic conversion to Unicode is performed: Applications wishing to " +"present such host names to the user should decode them to Unicode." +msgstr "" + +#: ../Doc/library/codecs.rst:1441 +msgid "" +"The module :mod:`encodings.idna` also implements the nameprep procedure, " +"which performs certain normalizations on host names, to achieve case-" +"insensitivity of international domain names, and to unify similar " +"characters. The nameprep functions can be used directly if desired." +msgstr "" + +#: ../Doc/library/codecs.rst:1449 +msgid "" +"Return the nameprepped version of *label*. The implementation currently " +"assumes query strings, so ``AllowUnassigned`` is true." +msgstr "" + +#: ../Doc/library/codecs.rst:1455 +msgid "" +"Convert a label to ASCII, as specified in :rfc:`3490`. ``UseSTD3ASCIIRules`` " +"is assumed to be false." +msgstr "" + +#: ../Doc/library/codecs.rst:1461 +msgid "Convert a label to Unicode, as specified in :rfc:`3490`." +msgstr "" + +#: ../Doc/library/codecs.rst:1465 +msgid ":mod:`encodings.mbcs` --- Windows ANSI codepage" +msgstr "" + +#: ../Doc/library/codecs.rst:1470 +msgid "Encode operand according to the ANSI codepage (CP_ACP)." +msgstr "" + +#: ../Doc/library/codecs.rst:1472 +msgid "Availability: Windows only." +msgstr "" + +#: ../Doc/library/codecs.rst:1474 +msgid "Support any error handler." +msgstr "" + +#: ../Doc/library/codecs.rst:1477 +msgid "" +"Before 3.2, the *errors* argument was ignored; ``'replace'`` was always used " +"to encode, and ``'ignore'`` to decode." +msgstr "" + +#: ../Doc/library/codecs.rst:1483 +msgid ":mod:`encodings.utf_8_sig` --- UTF-8 codec with BOM signature" +msgstr "" + +#: ../Doc/library/codecs.rst:1489 +msgid "" +"This module implements a variant of the UTF-8 codec: On encoding a UTF-8 " +"encoded BOM will be prepended to the UTF-8 encoded bytes. For the stateful " +"encoder this is only done once (on the first write to the byte stream). For " +"decoding an optional UTF-8 encoded BOM at the start of the data will be " +"skipped." +msgstr "" + +#: ../Doc/library/codeop.rst:2 +msgid ":mod:`codeop` --- Compile Python code" +msgstr "" + +#: ../Doc/library/codeop.rst:10 +msgid "**Source code:** :source:`Lib/codeop.py`" +msgstr "" + +#: ../Doc/library/codeop.rst:14 +msgid "" +"The :mod:`codeop` module provides utilities upon which the Python read-eval-" +"print loop can be emulated, as is done in the :mod:`code` module. As a " +"result, you probably don't want to use the module directly; if you want to " +"include such a loop in your program you probably want to use the :mod:`code` " +"module instead." +msgstr "" + +#: ../Doc/library/codeop.rst:20 +msgid "There are two parts to this job:" +msgstr "" + +#: ../Doc/library/codeop.rst:22 +msgid "" +"Being able to tell if a line of input completes a Python statement: in " +"short, telling whether to print '``>>>``' or '``...``' next." +msgstr "" + +#: ../Doc/library/codeop.rst:25 +msgid "" +"Remembering which future statements the user has entered, so subsequent " +"input can be compiled with these in effect." +msgstr "" + +#: ../Doc/library/codeop.rst:28 +msgid "" +"The :mod:`codeop` module provides a way of doing each of these things, and a " +"way of doing them both." +msgstr "" + +#: ../Doc/library/codeop.rst:31 +msgid "To do just the former:" +msgstr "" + +#: ../Doc/library/codeop.rst:35 +msgid "" +"Tries to compile *source*, which should be a string of Python code and " +"return a code object if *source* is valid Python code. In that case, the " +"filename attribute of the code object will be *filename*, which defaults to " +"``''``. Returns ``None`` if *source* is *not* valid Python code, but " +"is a prefix of valid Python code." +msgstr "" + +#: ../Doc/library/codeop.rst:41 +msgid "" +"If there is a problem with *source*, an exception will be raised. :exc:" +"`SyntaxError` is raised if there is invalid Python syntax, and :exc:" +"`OverflowError` or :exc:`ValueError` if there is an invalid literal." +msgstr "" + +#: ../Doc/library/codeop.rst:45 +msgid "" +"The *symbol* argument determines whether *source* is compiled as a statement " +"(``'single'``, the default) or as an :term:`expression` (``'eval'``). Any " +"other value will cause :exc:`ValueError` to be raised." +msgstr "" + +#: ../Doc/library/codeop.rst:51 +msgid "" +"It is possible (but not likely) that the parser stops parsing with a " +"successful outcome before reaching the end of the source; in this case, " +"trailing symbols may be ignored instead of causing an error. For example, a " +"backslash followed by two newlines may be followed by arbitrary garbage. " +"This will be fixed once the API for the parser is better." +msgstr "" + +#: ../Doc/library/codeop.rst:60 +msgid "" +"Instances of this class have :meth:`__call__` methods identical in signature " +"to the built-in function :func:`compile`, but with the difference that if " +"the instance compiles program text containing a :mod:`__future__` statement, " +"the instance 'remembers' and compiles all subsequent program texts with the " +"statement in force." +msgstr "" + +#: ../Doc/library/codeop.rst:69 +msgid "" +"Instances of this class have :meth:`__call__` methods identical in signature " +"to :func:`compile_command`; the difference is that if the instance compiles " +"program text containing a ``__future__`` statement, the instance 'remembers' " +"and compiles all subsequent program texts with the statement in force." +msgstr "" + +#: ../Doc/library/collections.rst:2 +msgid ":mod:`collections` --- Container datatypes" +msgstr "" + +#: ../Doc/library/collections.rst:10 +msgid "**Source code:** :source:`Lib/collections/__init__.py`" +msgstr "" + +#: ../Doc/library/collections.rst:20 +msgid "" +"This module implements specialized container datatypes providing " +"alternatives to Python's general purpose built-in containers, :class:" +"`dict`, :class:`list`, :class:`set`, and :class:`tuple`." +msgstr "" + +#: ../Doc/library/collections.rst:25 +msgid ":func:`namedtuple`" +msgstr "" + +#: ../Doc/library/collections.rst:25 +msgid "factory function for creating tuple subclasses with named fields" +msgstr "" + +#: ../Doc/library/collections.rst:26 +msgid ":class:`deque`" +msgstr "" + +#: ../Doc/library/collections.rst:26 +msgid "list-like container with fast appends and pops on either end" +msgstr "" + +#: ../Doc/library/collections.rst:27 +msgid ":class:`ChainMap`" +msgstr "" + +#: ../Doc/library/collections.rst:27 +msgid "dict-like class for creating a single view of multiple mappings" +msgstr "" + +#: ../Doc/library/collections.rst:28 +msgid ":class:`Counter`" +msgstr "" + +#: ../Doc/library/collections.rst:28 +msgid "dict subclass for counting hashable objects" +msgstr "" + +#: ../Doc/library/collections.rst:29 +msgid ":class:`OrderedDict`" +msgstr "" + +#: ../Doc/library/collections.rst:29 +msgid "dict subclass that remembers the order entries were added" +msgstr "" + +#: ../Doc/library/collections.rst:30 +msgid ":class:`defaultdict`" +msgstr "" + +#: ../Doc/library/collections.rst:30 +msgid "dict subclass that calls a factory function to supply missing values" +msgstr "" + +#: ../Doc/library/collections.rst:31 +msgid ":class:`UserDict`" +msgstr "" + +#: ../Doc/library/collections.rst:31 +msgid "wrapper around dictionary objects for easier dict subclassing" +msgstr "" + +#: ../Doc/library/collections.rst:32 +msgid ":class:`UserList`" +msgstr "" + +#: ../Doc/library/collections.rst:32 +msgid "wrapper around list objects for easier list subclassing" +msgstr "" + +#: ../Doc/library/collections.rst:33 +msgid ":class:`UserString`" +msgstr "" + +#: ../Doc/library/collections.rst:33 +msgid "wrapper around string objects for easier string subclassing" +msgstr "" + +#: ../Doc/library/collections.rst:36 +msgid "" +"Moved :ref:`collections-abstract-base-classes` to the :mod:`collections.abc` " +"module. For backwards compatibility, they continue to be visible in this " +"module as well." +msgstr "" + +#: ../Doc/library/collections.rst:43 +msgid ":class:`ChainMap` objects" +msgstr "" + +#: ../Doc/library/collections.rst:47 +msgid "" +"A :class:`ChainMap` class is provided for quickly linking a number of " +"mappings so they can be treated as a single unit. It is often much faster " +"than creating a new dictionary and running multiple :meth:`~dict.update` " +"calls." +msgstr "" + +#: ../Doc/library/collections.rst:51 +msgid "" +"The class can be used to simulate nested scopes and is useful in templating." +msgstr "" + +#: ../Doc/library/collections.rst:55 +msgid "" +"A :class:`ChainMap` groups multiple dicts or other mappings together to " +"create a single, updateable view. If no *maps* are specified, a single " +"empty dictionary is provided so that a new chain always has at least one " +"mapping." +msgstr "" + +#: ../Doc/library/collections.rst:59 +msgid "" +"The underlying mappings are stored in a list. That list is public and can " +"be accessed or updated using the *maps* attribute. There is no other state." +msgstr "" + +#: ../Doc/library/collections.rst:62 +msgid "" +"Lookups search the underlying mappings successively until a key is found. " +"In contrast, writes, updates, and deletions only operate on the first " +"mapping." +msgstr "" + +#: ../Doc/library/collections.rst:65 +msgid "" +"A :class:`ChainMap` incorporates the underlying mappings by reference. So, " +"if one of the underlying mappings gets updated, those changes will be " +"reflected in :class:`ChainMap`." +msgstr "" + +#: ../Doc/library/collections.rst:69 +msgid "" +"All of the usual dictionary methods are supported. In addition, there is a " +"*maps* attribute, a method for creating new subcontexts, and a property for " +"accessing all but the first mapping:" +msgstr "" + +#: ../Doc/library/collections.rst:75 +msgid "" +"A user updateable list of mappings. The list is ordered from first-searched " +"to last-searched. It is the only stored state and can be modified to change " +"which mappings are searched. The list should always contain at least one " +"mapping." +msgstr "" + +#: ../Doc/library/collections.rst:82 +msgid "" +"Returns a new :class:`ChainMap` containing a new map followed by all of the " +"maps in the current instance. If ``m`` is specified, it becomes the new map " +"at the front of the list of mappings; if not specified, an empty dict is " +"used, so that a call to ``d.new_child()`` is equivalent to: ``ChainMap({}, " +"*d.maps)``. This method is used for creating subcontexts that can be " +"updated without altering values in any of the parent mappings." +msgstr "" + +#: ../Doc/library/collections.rst:90 +msgid "The optional ``m`` parameter was added." +msgstr "" + +#: ../Doc/library/collections.rst:95 +msgid "" +"Property returning a new :class:`ChainMap` containing all of the maps in the " +"current instance except the first one. This is useful for skipping the " +"first map in the search. Use cases are similar to those for the :keyword:" +"`nonlocal` keyword used in :term:`nested scopes `. The use " +"cases also parallel those for the built-in :func:`super` function. A " +"reference to ``d.parents`` is equivalent to: ``ChainMap(*d.maps[1:])``." +msgstr "" + +#: ../Doc/library/collections.rst:106 +msgid "" +"The `MultiContext class `_ in the Enthought `CodeTools package " +"`_ has options to support writing to " +"any mapping in the chain." +msgstr "" + +#: ../Doc/library/collections.rst:112 +msgid "" +"Django's `Context class `_ for templating is a read-only chain of mappings. It " +"also features pushing and popping of contexts similar to the :meth:" +"`~collections.ChainMap.new_child` method and the :meth:`~collections." +"ChainMap.parents` property." +msgstr "" + +#: ../Doc/library/collections.rst:119 +msgid "" +"The `Nested Contexts recipe `_ " +"has options to control whether writes and other mutations apply only to the " +"first mapping or to any mapping in the chain." +msgstr "" + +#: ../Doc/library/collections.rst:124 +msgid "" +"A `greatly simplified read-only version of Chainmap `_." +msgstr "" + +#: ../Doc/library/collections.rst:129 +msgid ":class:`ChainMap` Examples and Recipes" +msgstr "" + +#: ../Doc/library/collections.rst:131 +msgid "This section shows various approaches to working with chained maps." +msgstr "" + +#: ../Doc/library/collections.rst:134 +msgid "Example of simulating Python's internal lookup chain::" +msgstr "" + +#: ../Doc/library/collections.rst:139 +msgid "" +"Example of letting user specified command-line arguments take precedence " +"over environment variables which in turn take precedence over default " +"values::" +msgstr "" + +#: ../Doc/library/collections.rst:156 +msgid "" +"Example patterns for using the :class:`ChainMap` class to simulate nested " +"contexts::" +msgstr "" + +#: ../Doc/library/collections.rst:175 +msgid "" +"The :class:`ChainMap` class only makes updates (writes and deletions) to the " +"first mapping in the chain while lookups will search the full chain. " +"However, if deep writes and deletions are desired, it is easy to make a " +"subclass that updates keys found deeper in the chain::" +msgstr "" + +#: ../Doc/library/collections.rst:205 +msgid ":class:`Counter` objects" +msgstr "" + +#: ../Doc/library/collections.rst:207 +msgid "" +"A counter tool is provided to support convenient and rapid tallies. For " +"example::" +msgstr "" + +#: ../Doc/library/collections.rst:226 +msgid "" +"A :class:`Counter` is a :class:`dict` subclass for counting hashable " +"objects. It is an unordered collection where elements are stored as " +"dictionary keys and their counts are stored as dictionary values. Counts " +"are allowed to be any integer value including zero or negative counts. The :" +"class:`Counter` class is similar to bags or multisets in other languages." +msgstr "" + +#: ../Doc/library/collections.rst:232 +msgid "" +"Elements are counted from an *iterable* or initialized from another " +"*mapping* (or counter):" +msgstr "" + +#: ../Doc/library/collections.rst:240 +msgid "" +"Counter objects have a dictionary interface except that they return a zero " +"count for missing items instead of raising a :exc:`KeyError`:" +msgstr "" + +#: ../Doc/library/collections.rst:247 +msgid "" +"Setting a count to zero does not remove an element from a counter. Use " +"``del`` to remove it entirely:" +msgstr "" + +#: ../Doc/library/collections.rst:256 +msgid "" +"Counter objects support three methods beyond those available for all " +"dictionaries:" +msgstr "" + +#: ../Doc/library/collections.rst:261 +msgid "" +"Return an iterator over elements repeating each as many times as its count. " +"Elements are returned in arbitrary order. If an element's count is less " +"than one, :meth:`elements` will ignore it." +msgstr "" + +#: ../Doc/library/collections.rst:271 +msgid "" +"Return a list of the *n* most common elements and their counts from the most " +"common to the least. If *n* is omitted or ``None``, :func:`most_common` " +"returns *all* elements in the counter. Elements with equal counts are " +"ordered arbitrarily:" +msgstr "" + +#: ../Doc/library/collections.rst:281 +msgid "" +"Elements are subtracted from an *iterable* or from another *mapping* (or " +"counter). Like :meth:`dict.update` but subtracts counts instead of " +"replacing them. Both inputs and outputs may be zero or negative." +msgstr "" + +#: ../Doc/library/collections.rst:293 +msgid "" +"The usual dictionary methods are available for :class:`Counter` objects " +"except for two which work differently for counters." +msgstr "" + +#: ../Doc/library/collections.rst:298 +msgid "This class method is not implemented for :class:`Counter` objects." +msgstr "" + +#: ../Doc/library/collections.rst:302 +msgid "" +"Elements are counted from an *iterable* or added-in from another *mapping* " +"(or counter). Like :meth:`dict.update` but adds counts instead of replacing " +"them. Also, the *iterable* is expected to be a sequence of elements, not a " +"sequence of ``(key, value)`` pairs." +msgstr "" + +#: ../Doc/library/collections.rst:307 +msgid "Common patterns for working with :class:`Counter` objects::" +msgstr "" + +#: ../Doc/library/collections.rst:319 +msgid "" +"Several mathematical operations are provided for combining :class:`Counter` " +"objects to produce multisets (counters that have counts greater than zero). " +"Addition and subtraction combine counters by adding or subtracting the " +"counts of corresponding elements. Intersection and union return the minimum " +"and maximum of corresponding counts. Each operation can accept inputs with " +"signed counts, but the output will exclude results with counts of zero or " +"less." +msgstr "" + +#: ../Doc/library/collections.rst:337 +msgid "" +"Unary addition and subtraction are shortcuts for adding an empty counter or " +"subtracting from an empty counter." +msgstr "" + +#: ../Doc/library/collections.rst:346 +msgid "" +"Added support for unary plus, unary minus, and in-place multiset operations." +msgstr "" + +#: ../Doc/library/collections.rst:351 +msgid "" +"Counters were primarily designed to work with positive integers to represent " +"running counts; however, care was taken to not unnecessarily preclude use " +"cases needing other types or negative values. To help with those use cases, " +"this section documents the minimum range and type restrictions." +msgstr "" + +#: ../Doc/library/collections.rst:356 +msgid "" +"The :class:`Counter` class itself is a dictionary subclass with no " +"restrictions on its keys and values. The values are intended to be numbers " +"representing counts, but you *could* store anything in the value field." +msgstr "" + +#: ../Doc/library/collections.rst:360 +msgid "" +"The :meth:`most_common` method requires only that the values be orderable." +msgstr "" + +#: ../Doc/library/collections.rst:362 +msgid "" +"For in-place operations such as ``c[key] += 1``, the value type need only " +"support addition and subtraction. So fractions, floats, and decimals would " +"work and negative values are supported. The same is also true for :meth:" +"`update` and :meth:`subtract` which allow negative and zero values for both " +"inputs and outputs." +msgstr "" + +#: ../Doc/library/collections.rst:368 +msgid "" +"The multiset methods are designed only for use cases with positive values. " +"The inputs may be negative or zero, but only outputs with positive values " +"are created. There are no type restrictions, but the value type needs to " +"support addition, subtraction, and comparison." +msgstr "" + +#: ../Doc/library/collections.rst:373 +msgid "" +"The :meth:`elements` method requires integer counts. It ignores zero and " +"negative counts." +msgstr "" + +#: ../Doc/library/collections.rst:378 +msgid "" +"`Bag class `_ in Smalltalk." +msgstr "" + +#: ../Doc/library/collections.rst:381 +msgid "" +"Wikipedia entry for `Multisets `_." +msgstr "" + +#: ../Doc/library/collections.rst:383 +msgid "" +"`C++ multisets `_ tutorial with examples." +msgstr "" + +#: ../Doc/library/collections.rst:386 +msgid "" +"For mathematical operations on multisets and their use cases, see *Knuth, " +"Donald. The Art of Computer Programming Volume II, Section 4.6.3, Exercise " +"19*." +msgstr "" + +#: ../Doc/library/collections.rst:390 +msgid "" +"To enumerate all distinct multisets of a given size over a given set of " +"elements, see :func:`itertools.combinations_with_replacement`:" +msgstr "" + +#: ../Doc/library/collections.rst:393 +msgid "" +"map(Counter, combinations_with_replacement('ABC', 2)) --> AA AB AC BB BC CC" +msgstr "" + +#: ../Doc/library/collections.rst:397 +msgid ":class:`deque` objects" +msgstr "" + +#: ../Doc/library/collections.rst:401 +msgid "" +"Returns a new deque object initialized left-to-right (using :meth:`append`) " +"with data from *iterable*. If *iterable* is not specified, the new deque is " +"empty." +msgstr "" + +#: ../Doc/library/collections.rst:404 +msgid "" +"Deques are a generalization of stacks and queues (the name is pronounced " +"\"deck\" and is short for \"double-ended queue\"). Deques support thread-" +"safe, memory efficient appends and pops from either side of the deque with " +"approximately the same O(1) performance in either direction." +msgstr "" + +#: ../Doc/library/collections.rst:409 +msgid "" +"Though :class:`list` objects support similar operations, they are optimized " +"for fast fixed-length operations and incur O(n) memory movement costs for " +"``pop(0)`` and ``insert(0, v)`` operations which change both the size and " +"position of the underlying data representation." +msgstr "" + +#: ../Doc/library/collections.rst:415 +msgid "" +"If *maxlen* is not specified or is *None*, deques may grow to an arbitrary " +"length. Otherwise, the deque is bounded to the specified maximum length. " +"Once a bounded length deque is full, when new items are added, a " +"corresponding number of items are discarded from the opposite end. Bounded " +"length deques provide functionality similar to the ``tail`` filter in Unix. " +"They are also useful for tracking transactions and other pools of data where " +"only the most recent activity is of interest." +msgstr "" + +#: ../Doc/library/collections.rst:424 +msgid "Deque objects support the following methods:" +msgstr "" + +#: ../Doc/library/collections.rst:428 +msgid "Add *x* to the right side of the deque." +msgstr "" + +#: ../Doc/library/collections.rst:433 +msgid "Add *x* to the left side of the deque." +msgstr "" + +#: ../Doc/library/collections.rst:438 +msgid "Remove all elements from the deque leaving it with length 0." +msgstr "" + +#: ../Doc/library/collections.rst:443 +msgid "Create a shallow copy of the deque." +msgstr "" + +#: ../Doc/library/collections.rst:450 +msgid "Count the number of deque elements equal to *x*." +msgstr "" + +#: ../Doc/library/collections.rst:457 +msgid "" +"Extend the right side of the deque by appending elements from the iterable " +"argument." +msgstr "" + +#: ../Doc/library/collections.rst:463 +msgid "" +"Extend the left side of the deque by appending elements from *iterable*. " +"Note, the series of left appends results in reversing the order of elements " +"in the iterable argument." +msgstr "" + +#: ../Doc/library/collections.rst:470 +msgid "" +"Return the position of *x* in the deque (at or after index *start* and " +"before index *stop*). Returns the first match or raises :exc:`ValueError` " +"if not found." +msgstr "" + +#: ../Doc/library/collections.rst:479 +msgid "Insert *x* into the deque at position *i*." +msgstr "" + +#: ../Doc/library/collections.rst:481 +msgid "" +"If the insertion would cause a bounded deque to grow beyond *maxlen*, an :" +"exc:`IndexError` is raised." +msgstr "" + +#: ../Doc/library/collections.rst:489 +msgid "" +"Remove and return an element from the right side of the deque. If no " +"elements are present, raises an :exc:`IndexError`." +msgstr "" + +#: ../Doc/library/collections.rst:495 +msgid "" +"Remove and return an element from the left side of the deque. If no elements " +"are present, raises an :exc:`IndexError`." +msgstr "" + +#: ../Doc/library/collections.rst:501 +msgid "" +"Remove the first occurrence of *value*. If not found, raises a :exc:" +"`ValueError`." +msgstr "" + +#: ../Doc/library/collections.rst:507 +msgid "Reverse the elements of the deque in-place and then return ``None``." +msgstr "" + +#: ../Doc/library/collections.rst:514 +msgid "" +"Rotate the deque *n* steps to the right. If *n* is negative, rotate to the " +"left. Rotating one step to the right is equivalent to: ``d.appendleft(d." +"pop())``." +msgstr "" + +#: ../Doc/library/collections.rst:519 +msgid "Deque objects also provide one read-only attribute:" +msgstr "" + +#: ../Doc/library/collections.rst:523 +msgid "Maximum size of a deque or *None* if unbounded." +msgstr "" + +#: ../Doc/library/collections.rst:528 +msgid "" +"In addition to the above, deques support iteration, pickling, ``len(d)``, " +"``reversed(d)``, ``copy.copy(d)``, ``copy.deepcopy(d)``, membership testing " +"with the :keyword:`in` operator, and subscript references such as " +"``d[-1]``. Indexed access is O(1) at both ends but slows to O(n) in the " +"middle. For fast random access, use lists instead." +msgstr "" + +#: ../Doc/library/collections.rst:534 +msgid "" +"Starting in version 3.5, deques support ``__add__()``, ``__mul__()``, and " +"``__imul__()``." +msgstr "" + +#: ../Doc/library/collections.rst:537 ../Doc/library/datetime.rst:1583 +#: ../Doc/library/difflib.rst:262 ../Doc/library/fnmatch.rst:79 +#: ../Doc/library/sqlite3.rst:344 ../Doc/library/sqlite3.rst:361 +#: ../Doc/library/sqlite3.rst:471 ../Doc/library/sqlite3.rst:571 +#: ../Doc/library/turtle.rst:2076 +msgid "Example:" +msgstr "" + +#: ../Doc/library/collections.rst:594 +msgid ":class:`deque` Recipes" +msgstr "" + +#: ../Doc/library/collections.rst:596 +msgid "This section shows various approaches to working with deques." +msgstr "" + +#: ../Doc/library/collections.rst:598 +msgid "" +"Bounded length deques provide functionality similar to the ``tail`` filter " +"in Unix::" +msgstr "" + +#: ../Doc/library/collections.rst:606 +msgid "" +"Another approach to using deques is to maintain a sequence of recently added " +"elements by appending to the right and popping to the left::" +msgstr "" + +#: ../Doc/library/collections.rst:621 +msgid "" +"The :meth:`rotate` method provides a way to implement :class:`deque` slicing " +"and deletion. For example, a pure Python implementation of ``del d[n]`` " +"relies on the :meth:`rotate` method to position elements to be popped::" +msgstr "" + +#: ../Doc/library/collections.rst:630 +msgid "" +"To implement :class:`deque` slicing, use a similar approach applying :meth:" +"`rotate` to bring a target element to the left side of the deque. Remove old " +"entries with :meth:`popleft`, add new entries with :meth:`extend`, and then " +"reverse the rotation. With minor variations on that approach, it is easy to " +"implement Forth style stack manipulations such as ``dup``, ``drop``, " +"``swap``, ``over``, ``pick``, ``rot``, and ``roll``." +msgstr "" + +#: ../Doc/library/collections.rst:640 +msgid ":class:`defaultdict` objects" +msgstr "" + +#: ../Doc/library/collections.rst:644 +msgid "" +"Returns a new dictionary-like object. :class:`defaultdict` is a subclass of " +"the built-in :class:`dict` class. It overrides one method and adds one " +"writable instance variable. The remaining functionality is the same as for " +"the :class:`dict` class and is not documented here." +msgstr "" + +#: ../Doc/library/collections.rst:649 +msgid "" +"The first argument provides the initial value for the :attr:" +"`default_factory` attribute; it defaults to ``None``. All remaining " +"arguments are treated the same as if they were passed to the :class:`dict` " +"constructor, including keyword arguments." +msgstr "" + +#: ../Doc/library/collections.rst:655 +msgid "" +":class:`defaultdict` objects support the following method in addition to the " +"standard :class:`dict` operations:" +msgstr "" + +#: ../Doc/library/collections.rst:660 +msgid "" +"If the :attr:`default_factory` attribute is ``None``, this raises a :exc:" +"`KeyError` exception with the *key* as argument." +msgstr "" + +#: ../Doc/library/collections.rst:663 +msgid "" +"If :attr:`default_factory` is not ``None``, it is called without arguments " +"to provide a default value for the given *key*, this value is inserted in " +"the dictionary for the *key*, and returned." +msgstr "" + +#: ../Doc/library/collections.rst:667 +msgid "" +"If calling :attr:`default_factory` raises an exception this exception is " +"propagated unchanged." +msgstr "" + +#: ../Doc/library/collections.rst:670 +msgid "" +"This method is called by the :meth:`__getitem__` method of the :class:`dict` " +"class when the requested key is not found; whatever it returns or raises is " +"then returned or raised by :meth:`__getitem__`." +msgstr "" + +#: ../Doc/library/collections.rst:674 +msgid "" +"Note that :meth:`__missing__` is *not* called for any operations besides :" +"meth:`__getitem__`. This means that :meth:`get` will, like normal " +"dictionaries, return ``None`` as a default rather than using :attr:" +"`default_factory`." +msgstr "" + +#: ../Doc/library/collections.rst:680 +msgid ":class:`defaultdict` objects support the following instance variable:" +msgstr "" + +#: ../Doc/library/collections.rst:685 +msgid "" +"This attribute is used by the :meth:`__missing__` method; it is initialized " +"from the first argument to the constructor, if present, or to ``None``, if " +"absent." +msgstr "" + +#: ../Doc/library/collections.rst:691 +msgid ":class:`defaultdict` Examples" +msgstr "" + +#: ../Doc/library/collections.rst:693 +msgid "" +"Using :class:`list` as the :attr:`default_factory`, it is easy to group a " +"sequence of key-value pairs into a dictionary of lists:" +msgstr "" + +#: ../Doc/library/collections.rst:704 +msgid "" +"When each key is encountered for the first time, it is not already in the " +"mapping; so an entry is automatically created using the :attr:" +"`default_factory` function which returns an empty :class:`list`. The :meth:" +"`list.append` operation then attaches the value to the new list. When keys " +"are encountered again, the look-up proceeds normally (returning the list for " +"that key) and the :meth:`list.append` operation adds another value to the " +"list. This technique is simpler and faster than an equivalent technique " +"using :meth:`dict.setdefault`:" +msgstr "" + +#: ../Doc/library/collections.rst:719 +msgid "" +"Setting the :attr:`default_factory` to :class:`int` makes the :class:" +"`defaultdict` useful for counting (like a bag or multiset in other " +"languages):" +msgstr "" + +#: ../Doc/library/collections.rst:731 +msgid "" +"When a letter is first encountered, it is missing from the mapping, so the :" +"attr:`default_factory` function calls :func:`int` to supply a default count " +"of zero. The increment operation then builds up the count for each letter." +msgstr "" + +#: ../Doc/library/collections.rst:735 +msgid "" +"The function :func:`int` which always returns zero is just a special case of " +"constant functions. A faster and more flexible way to create constant " +"functions is to use a lambda function which can supply any constant value " +"(not just zero):" +msgstr "" + +#: ../Doc/library/collections.rst:747 +msgid "" +"Setting the :attr:`default_factory` to :class:`set` makes the :class:" +"`defaultdict` useful for building a dictionary of sets:" +msgstr "" + +#: ../Doc/library/collections.rst:760 +msgid ":func:`namedtuple` Factory Function for Tuples with Named Fields" +msgstr "" + +#: ../Doc/library/collections.rst:762 +msgid "" +"Named tuples assign meaning to each position in a tuple and allow for more " +"readable, self-documenting code. They can be used wherever regular tuples " +"are used, and they add the ability to access fields by name instead of " +"position index." +msgstr "" + +#: ../Doc/library/collections.rst:768 +msgid "" +"Returns a new tuple subclass named *typename*. The new subclass is used to " +"create tuple-like objects that have fields accessible by attribute lookup as " +"well as being indexable and iterable. Instances of the subclass also have a " +"helpful docstring (with typename and field_names) and a helpful :meth:" +"`__repr__` method which lists the tuple contents in a ``name=value`` format." +msgstr "" + +#: ../Doc/library/collections.rst:774 +msgid "" +"The *field_names* are a single string with each fieldname separated by " +"whitespace and/or commas, for example ``'x y'`` or ``'x, y'``. " +"Alternatively, *field_names* can be a sequence of strings such as ``['x', " +"'y']``." +msgstr "" + +#: ../Doc/library/collections.rst:778 +msgid "" +"Any valid Python identifier may be used for a fieldname except for names " +"starting with an underscore. Valid identifiers consist of letters, digits, " +"and underscores but do not start with a digit or underscore and cannot be a :" +"mod:`keyword` such as *class*, *for*, *return*, *global*, *pass*, or *raise*." +msgstr "" + +#: ../Doc/library/collections.rst:784 +msgid "" +"If *rename* is true, invalid fieldnames are automatically replaced with " +"positional names. For example, ``['abc', 'def', 'ghi', 'abc']`` is " +"converted to ``['abc', '_1', 'ghi', '_3']``, eliminating the keyword ``def`` " +"and the duplicate fieldname ``abc``." +msgstr "" + +#: ../Doc/library/collections.rst:789 +msgid "" +"If *verbose* is true, the class definition is printed after it is built. " +"This option is outdated; instead, it is simpler to print the :attr:`_source` " +"attribute." +msgstr "" + +#: ../Doc/library/collections.rst:793 +msgid "" +"If *module* is defined, the ``__module__`` attribute of the named tuple is " +"set to that value." +msgstr "" + +#: ../Doc/library/collections.rst:796 +msgid "" +"Named tuple instances do not have per-instance dictionaries, so they are " +"lightweight and require no more memory than regular tuples." +msgstr "" + +#: ../Doc/library/collections.rst:799 +msgid "Added support for *rename*." +msgstr "" + +#: ../Doc/library/collections.rst:802 +msgid "" +"The *verbose* and *rename* parameters became :ref:`keyword-only arguments " +"`." +msgstr "" + +#: ../Doc/library/collections.rst:806 +msgid "Added the *module* parameter." +msgstr "" + +#: ../Doc/library/collections.rst:825 +msgid "" +"Named tuples are especially useful for assigning field names to result " +"tuples returned by the :mod:`csv` or :mod:`sqlite3` modules::" +msgstr "" + +#: ../Doc/library/collections.rst:841 +msgid "" +"In addition to the methods inherited from tuples, named tuples support three " +"additional methods and two attributes. To prevent conflicts with field " +"names, the method and attribute names start with an underscore." +msgstr "" + +#: ../Doc/library/collections.rst:847 +msgid "" +"Class method that makes a new instance from an existing sequence or iterable." +msgstr "" + +#: ../Doc/library/collections.rst:857 +msgid "" +"Return a new :class:`OrderedDict` which maps field names to their " +"corresponding values:" +msgstr "" + +#: ../Doc/library/collections.rst:866 +msgid "Returns an :class:`OrderedDict` instead of a regular :class:`dict`." +msgstr "" + +#: ../Doc/library/collections.rst:871 +msgid "" +"Return a new instance of the named tuple replacing specified fields with new " +"values::" +msgstr "" + +#: ../Doc/library/collections.rst:883 +msgid "" +"A string with the pure Python source code used to create the named tuple " +"class. The source makes the named tuple self-documenting. It can be " +"printed, executed using :func:`exec`, or saved to a file and imported." +msgstr "" + +#: ../Doc/library/collections.rst:892 +msgid "" +"Tuple of strings listing the field names. Useful for introspection and for " +"creating new named tuple types from existing named tuples." +msgstr "" + +#: ../Doc/library/collections.rst:905 +msgid "" +"To retrieve a field whose name is stored in a string, use the :func:" +"`getattr` function:" +msgstr "" + +#: ../Doc/library/collections.rst:911 +msgid "" +"To convert a dictionary to a named tuple, use the double-star-operator (as " +"described in :ref:`tut-unpacking-arguments`):" +msgstr "" + +#: ../Doc/library/collections.rst:918 +msgid "" +"Since a named tuple is a regular Python class, it is easy to add or change " +"functionality with a subclass. Here is how to add a calculated field and a " +"fixed-width print format:" +msgstr "" + +#: ../Doc/library/collections.rst:937 +msgid "" +"The subclass shown above sets ``__slots__`` to an empty tuple. This helps " +"keep memory requirements low by preventing the creation of instance " +"dictionaries." +msgstr "" + +#: ../Doc/library/collections.rst:940 +msgid "" +"Subclassing is not useful for adding new, stored fields. Instead, simply " +"create a new named tuple type from the :attr:`_fields` attribute:" +msgstr "" + +#: ../Doc/library/collections.rst:945 +msgid "" +"Docstrings can be customized by making direct assignments to the ``__doc__`` " +"fields:" +msgstr "" + +#: ../Doc/library/collections.rst:954 +msgid "Property docstrings became writeable." +msgstr "" + +#: ../Doc/library/collections.rst:957 +msgid "" +"Default values can be implemented by using :meth:`_replace` to customize a " +"prototype instance:" +msgstr "" + +#: ../Doc/library/collections.rst:968 +msgid "" +"`Recipe for named tuple abstract base class with a metaclass mix-in `_ by Jan Kaliszewski. Besides providing an :term:`abstract base " +"class` for named tuples, it also supports an alternate :term:`metaclass`-" +"based constructor that is convenient for use cases where named tuples are " +"being subclassed." +msgstr "" + +#: ../Doc/library/collections.rst:975 +msgid "" +"See :meth:`types.SimpleNamespace` for a mutable namespace based on an " +"underlying dictionary instead of a tuple." +msgstr "" + +#: ../Doc/library/collections.rst:978 +msgid "" +"See :meth:`typing.NamedTuple` for a way to add type hints for named tuples." +msgstr "" + +#: ../Doc/library/collections.rst:982 +msgid ":class:`OrderedDict` objects" +msgstr "" + +#: ../Doc/library/collections.rst:984 +msgid "" +"Ordered dictionaries are just like regular dictionaries but they remember " +"the order that items were inserted. When iterating over an ordered " +"dictionary, the items are returned in the order their keys were first added." +msgstr "" + +#: ../Doc/library/collections.rst:990 +msgid "" +"Return an instance of a dict subclass, supporting the usual :class:`dict` " +"methods. An *OrderedDict* is a dict that remembers the order that keys were " +"first inserted. If a new entry overwrites an existing entry, the original " +"insertion position is left unchanged. Deleting an entry and reinserting it " +"will move it to the end." +msgstr "" + +#: ../Doc/library/collections.rst:1000 +msgid "" +"The :meth:`popitem` method for ordered dictionaries returns and removes a " +"(key, value) pair. The pairs are returned in :abbr:`LIFO (last-in, first-" +"out)` order if *last* is true or :abbr:`FIFO (first-in, first-out)` order if " +"false." +msgstr "" + +#: ../Doc/library/collections.rst:1007 +msgid "" +"Move an existing *key* to either end of an ordered dictionary. The item is " +"moved to the right end if *last* is true (the default) or to the beginning " +"if *last* is false. Raises :exc:`KeyError` if the *key* does not exist::" +msgstr "" + +#: ../Doc/library/collections.rst:1022 +msgid "" +"In addition to the usual mapping methods, ordered dictionaries also support " +"reverse iteration using :func:`reversed`." +msgstr "" + +#: ../Doc/library/collections.rst:1025 +msgid "" +"Equality tests between :class:`OrderedDict` objects are order-sensitive and " +"are implemented as ``list(od1.items())==list(od2.items())``. Equality tests " +"between :class:`OrderedDict` objects and other :class:`~collections.abc." +"Mapping` objects are order-insensitive like regular dictionaries. This " +"allows :class:`OrderedDict` objects to be substituted anywhere a regular " +"dictionary is used." +msgstr "" + +#: ../Doc/library/collections.rst:1032 +msgid "" +"The :class:`OrderedDict` constructor and :meth:`update` method both accept " +"keyword arguments, but their order is lost because Python's function call " +"semantics pass in keyword arguments using a regular unordered dictionary." +msgstr "" + +#: ../Doc/library/collections.rst:1036 +msgid "" +"The items, keys, and values :term:`views ` of :class:" +"`OrderedDict` now support reverse iteration using :func:`reversed`." +msgstr "" + +#: ../Doc/library/collections.rst:1041 +msgid ":class:`OrderedDict` Examples and Recipes" +msgstr "" + +#: ../Doc/library/collections.rst:1043 +msgid "" +"Since an ordered dictionary remembers its insertion order, it can be used in " +"conjunction with sorting to make a sorted dictionary::" +msgstr "" + +#: ../Doc/library/collections.rst:1061 +msgid "" +"The new sorted dictionaries maintain their sort order when entries are " +"deleted. But when new keys are added, the keys are appended to the end and " +"the sort is not maintained." +msgstr "" + +#: ../Doc/library/collections.rst:1065 +msgid "" +"It is also straight-forward to create an ordered dictionary variant that " +"remembers the order the keys were *last* inserted. If a new entry overwrites " +"an existing entry, the original insertion position is changed and moved to " +"the end::" +msgstr "" + +#: ../Doc/library/collections.rst:1078 +msgid "" +"An ordered dictionary can be combined with the :class:`Counter` class so " +"that the counter remembers the order elements are first encountered::" +msgstr "" + +#: ../Doc/library/collections.rst:1092 +msgid ":class:`UserDict` objects" +msgstr "" + +#: ../Doc/library/collections.rst:1094 +msgid "" +"The class, :class:`UserDict` acts as a wrapper around dictionary objects. " +"The need for this class has been partially supplanted by the ability to " +"subclass directly from :class:`dict`; however, this class can be easier to " +"work with because the underlying dictionary is accessible as an attribute." +msgstr "" + +#: ../Doc/library/collections.rst:1102 +msgid "" +"Class that simulates a dictionary. The instance's contents are kept in a " +"regular dictionary, which is accessible via the :attr:`data` attribute of :" +"class:`UserDict` instances. If *initialdata* is provided, :attr:`data` is " +"initialized with its contents; note that a reference to *initialdata* will " +"not be kept, allowing it be used for other purposes." +msgstr "" + +#: ../Doc/library/collections.rst:1108 +msgid "" +"In addition to supporting the methods and operations of mappings, :class:" +"`UserDict` instances provide the following attribute:" +msgstr "" + +#: ../Doc/library/collections.rst:1113 +msgid "" +"A real dictionary used to store the contents of the :class:`UserDict` class." +msgstr "" + +#: ../Doc/library/collections.rst:1119 +msgid ":class:`UserList` objects" +msgstr "" + +#: ../Doc/library/collections.rst:1121 +msgid "" +"This class acts as a wrapper around list objects. It is a useful base class " +"for your own list-like classes which can inherit from them and override " +"existing methods or add new ones. In this way, one can add new behaviors to " +"lists." +msgstr "" + +#: ../Doc/library/collections.rst:1126 +msgid "" +"The need for this class has been partially supplanted by the ability to " +"subclass directly from :class:`list`; however, this class can be easier to " +"work with because the underlying list is accessible as an attribute." +msgstr "" + +#: ../Doc/library/collections.rst:1132 +msgid "" +"Class that simulates a list. The instance's contents are kept in a regular " +"list, which is accessible via the :attr:`data` attribute of :class:" +"`UserList` instances. The instance's contents are initially set to a copy " +"of *list*, defaulting to the empty list ``[]``. *list* can be any iterable, " +"for example a real Python list or a :class:`UserList` object." +msgstr "" + +#: ../Doc/library/collections.rst:1138 +msgid "" +"In addition to supporting the methods and operations of mutable sequences, :" +"class:`UserList` instances provide the following attribute:" +msgstr "" + +#: ../Doc/library/collections.rst:1143 +msgid "" +"A real :class:`list` object used to store the contents of the :class:" +"`UserList` class." +msgstr "" + +#: ../Doc/library/collections.rst:1146 +msgid "" +"**Subclassing requirements:** Subclasses of :class:`UserList` are expected " +"to offer a constructor which can be called with either no arguments or one " +"argument. List operations which return a new sequence attempt to create an " +"instance of the actual implementation class. To do so, it assumes that the " +"constructor can be called with a single parameter, which is a sequence " +"object used as a data source." +msgstr "" + +#: ../Doc/library/collections.rst:1153 +msgid "" +"If a derived class does not wish to comply with this requirement, all of the " +"special methods supported by this class will need to be overridden; please " +"consult the sources for information about the methods which need to be " +"provided in that case." +msgstr "" + +#: ../Doc/library/collections.rst:1159 +msgid ":class:`UserString` objects" +msgstr "" + +#: ../Doc/library/collections.rst:1161 +msgid "" +"The class, :class:`UserString` acts as a wrapper around string objects. The " +"need for this class has been partially supplanted by the ability to subclass " +"directly from :class:`str`; however, this class can be easier to work with " +"because the underlying string is accessible as an attribute." +msgstr "" + +#: ../Doc/library/collections.rst:1169 +msgid "" +"Class that simulates a string or a Unicode string object. The instance's " +"content is kept in a regular string object, which is accessible via the :" +"attr:`data` attribute of :class:`UserString` instances. The instance's " +"contents are initially set to a copy of *sequence*. The *sequence* can be " +"an instance of :class:`bytes`, :class:`str`, :class:`UserString` (or a " +"subclass) or an arbitrary sequence which can be converted into a string " +"using the built-in :func:`str` function." +msgstr "" + +#: ../Doc/library/collections.rst:1177 +msgid "" +"New methods ``__getnewargs__``, ``__rmod__``, ``casefold``, ``format_map``, " +"``isprintable``, and ``maketrans``." +msgstr "" + +#: ../Doc/library/collections.abc.rst:2 +msgid ":mod:`collections.abc` --- Abstract Base Classes for Containers" +msgstr "" + +#: ../Doc/library/collections.abc.rst:10 +msgid "Formerly, this module was part of the :mod:`collections` module." +msgstr "" + +#: ../Doc/library/collections.abc.rst:13 +msgid "**Source code:** :source:`Lib/_collections_abc.py`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:23 +msgid "" +"This module provides :term:`abstract base classes ` " +"that can be used to test whether a class provides a particular interface; " +"for example, whether it is hashable or whether it is a mapping." +msgstr "" + +#: ../Doc/library/collections.abc.rst:31 +msgid "Collections Abstract Base Classes" +msgstr "" + +#: ../Doc/library/collections.abc.rst:33 +msgid "" +"The collections module offers the following :term:`ABCs `:" +msgstr "" + +#: ../Doc/library/collections.abc.rst:38 ../Doc/library/io.rst:199 +msgid "ABC" +msgstr "" + +#: ../Doc/library/collections.abc.rst:38 +msgid "Inherits from" +msgstr "" + +#: ../Doc/library/collections.abc.rst:38 +msgid "Abstract Methods" +msgstr "" + +#: ../Doc/library/collections.abc.rst:38 +msgid "Mixin Methods" +msgstr "" + +#: ../Doc/library/collections.abc.rst:40 +msgid ":class:`Container`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:40 +msgid "``__contains__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:41 +msgid ":class:`Hashable`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:41 +msgid "``__hash__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:42 ../Doc/library/collections.abc.rst:43 +#: ../Doc/library/collections.abc.rst:44 +msgid ":class:`Iterable`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:42 ../Doc/library/collections.abc.rst:43 +msgid "``__iter__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:43 ../Doc/library/collections.abc.rst:45 +msgid ":class:`Iterator`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:43 +msgid "``__next__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:44 +msgid ":class:`Reversible`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:44 +msgid "``__reversed__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:45 +msgid ":class:`Generator`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:45 ../Doc/library/collections.abc.rst:92 +msgid "``send``, ``throw``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:45 +msgid "``close``, ``__iter__``, ``__next__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:46 ../Doc/library/collections.abc.rst:85 +msgid ":class:`Sized`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:46 ../Doc/library/collections.abc.rst:85 +msgid "``__len__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:47 +msgid ":class:`Callable`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:47 +msgid "``__call__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:48 ../Doc/library/collections.abc.rst:64 +#: ../Doc/library/collections.abc.rst:74 +msgid ":class:`Collection`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:48 +msgid ":class:`Sized`, :class:`Iterable`, :class:`Container`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:48 ../Doc/library/collections.abc.rst:64 +msgid "``__contains__``, ``__iter__``, ``__len__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:52 ../Doc/library/collections.abc.rst:55 +#: ../Doc/library/collections.abc.rst:61 +msgid ":class:`Sequence`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:52 +msgid ":class:`Reversible`, :class:`Collection`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:52 ../Doc/library/collections.abc.rst:61 +msgid "``__getitem__``, ``__len__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:52 +msgid "" +"``__contains__``, ``__iter__``, ``__reversed__``, ``index``, and ``count``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:55 +msgid ":class:`MutableSequence`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:55 +msgid "" +"``__getitem__``, ``__setitem__``, ``__delitem__``, ``__len__``, ``insert``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:55 +msgid "" +"Inherited :class:`Sequence` methods and ``append``, ``reverse``, ``extend``, " +"``pop``, ``remove``, and ``__iadd__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:61 +msgid ":class:`ByteString`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:61 +msgid "Inherited :class:`Sequence` methods" +msgstr "" + +#: ../Doc/library/collections.abc.rst:64 ../Doc/library/collections.abc.rst:68 +msgid ":class:`Set`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:64 +msgid "" +"``__le__``, ``__lt__``, ``__eq__``, ``__ne__``, ``__gt__``, ``__ge__``, " +"``__and__``, ``__or__``, ``__sub__``, ``__xor__``, and ``isdisjoint``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:68 +msgid ":class:`MutableSet`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:68 +msgid "``__contains__``, ``__iter__``, ``__len__``, ``add``, ``discard``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:68 +msgid "" +"Inherited :class:`Set` methods and ``clear``, ``pop``, ``remove``, " +"``__ior__``, ``__iand__``, ``__ixor__``, and ``__isub__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:74 ../Doc/library/collections.abc.rst:78 +msgid ":class:`Mapping`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:74 +msgid "``__getitem__``, ``__iter__``, ``__len__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:74 +msgid "" +"``__contains__``, ``keys``, ``items``, ``values``, ``get``, ``__eq__``, and " +"``__ne__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:78 +msgid ":class:`MutableMapping`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:78 +msgid "" +"``__getitem__``, ``__setitem__``, ``__delitem__``, ``__iter__``, ``__len__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:78 +msgid "" +"Inherited :class:`Mapping` methods and ``pop``, ``popitem``, ``clear``, " +"``update``, and ``setdefault``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:85 ../Doc/library/collections.abc.rst:90 +msgid ":class:`MappingView`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:86 +msgid ":class:`ItemsView`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:86 ../Doc/library/collections.abc.rst:88 +msgid ":class:`MappingView`, :class:`Set`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:86 ../Doc/library/collections.abc.rst:88 +#: ../Doc/library/collections.abc.rst:90 +msgid "``__contains__``, ``__iter__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:88 +msgid ":class:`KeysView`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:90 +msgid ":class:`ValuesView`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:91 ../Doc/library/collections.abc.rst:92 +msgid ":class:`Awaitable`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:91 +msgid "``__await__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:92 +msgid ":class:`Coroutine`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:92 +msgid "``close``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:93 ../Doc/library/collections.abc.rst:94 +msgid ":class:`AsyncIterable`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:93 ../Doc/library/collections.abc.rst:94 +msgid "``__aiter__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:94 +msgid ":class:`AsyncIterator`" +msgstr "" + +#: ../Doc/library/collections.abc.rst:94 +msgid "``__anext__``" +msgstr "" + +#: ../Doc/library/collections.abc.rst:103 +msgid "" +"ABCs for classes that provide respectively the methods :meth:" +"`__contains__`, :meth:`__hash__`, :meth:`__len__`, and :meth:`__call__`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:108 +msgid "" +"ABC for classes that provide the :meth:`__iter__` method. See also the " +"definition of :term:`iterable`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:113 +msgid "ABC for sized iterable container classes." +msgstr "" + +#: ../Doc/library/collections.abc.rst:119 +msgid "" +"ABC for classes that provide the :meth:`~iterator.__iter__` and :meth:" +"`~iterator.__next__` methods. See also the definition of :term:`iterator`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:125 +msgid "" +"ABC for iterable classes that also provide the :meth:`__reversed__` method." +msgstr "" + +#: ../Doc/library/collections.abc.rst:132 +msgid "" +"ABC for generator classes that implement the protocol defined in :pep:`342` " +"that extends iterators with the :meth:`~generator.send`, :meth:`~generator." +"throw` and :meth:`~generator.close` methods. See also the definition of :" +"term:`generator`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:143 +msgid "ABCs for read-only and mutable :term:`sequences `." +msgstr "" + +#: ../Doc/library/collections.abc.rst:145 +msgid "" +"Implementation note: Some of the mixin methods, such as :meth:`__iter__`, :" +"meth:`__reversed__` and :meth:`index`, make repeated calls to the " +"underlying :meth:`__getitem__` method. Consequently, if :meth:`__getitem__` " +"is implemented with constant access speed, the mixin methods will have " +"linear performance; however, if the underlying method is linear (as it would " +"be with a linked list), the mixins will have quadratic performance and will " +"likely need to be overridden." +msgstr "" + +#: ../Doc/library/collections.abc.rst:154 +msgid "The index() method added support for *stop* and *start* arguments." +msgstr "" + +#: ../Doc/library/collections.abc.rst:161 +msgid "ABCs for read-only and mutable sets." +msgstr "" + +#: ../Doc/library/collections.abc.rst:166 +msgid "ABCs for read-only and mutable :term:`mappings `." +msgstr "" + +#: ../Doc/library/collections.abc.rst:173 +msgid "" +"ABCs for mapping, items, keys, and values :term:`views `." +msgstr "" + +#: ../Doc/library/collections.abc.rst:177 +msgid "" +"ABC for :term:`awaitable` objects, which can be used in :keyword:`await` " +"expressions. Custom implementations must provide the :meth:`__await__` " +"method." +msgstr "" + +#: ../Doc/library/collections.abc.rst:181 +msgid "" +":term:`Coroutine` objects and instances of the :class:`~collections.abc." +"Coroutine` ABC are all instances of this ABC." +msgstr "" + +#: ../Doc/library/collections.abc.rst:185 +msgid "" +"In CPython, generator-based coroutines (generators decorated with :func:" +"`types.coroutine` or :func:`asyncio.coroutine`) are *awaitables*, even " +"though they do not have an :meth:`__await__` method. Using " +"``isinstance(gencoro, Awaitable)`` for them will return ``False``. Use :func:" +"`inspect.isawaitable` to detect them." +msgstr "" + +#: ../Doc/library/collections.abc.rst:195 +msgid "" +"ABC for coroutine compatible classes. These implement the following " +"methods, defined in :ref:`coroutine-objects`: :meth:`~coroutine.send`, :meth:" +"`~coroutine.throw`, and :meth:`~coroutine.close`. Custom implementations " +"must also implement :meth:`__await__`. All :class:`Coroutine` instances are " +"also instances of :class:`Awaitable`. See also the definition of :term:" +"`coroutine`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:203 +msgid "" +"In CPython, generator-based coroutines (generators decorated with :func:" +"`types.coroutine` or :func:`asyncio.coroutine`) are *awaitables*, even " +"though they do not have an :meth:`__await__` method. Using " +"``isinstance(gencoro, Coroutine)`` for them will return ``False``. Use :func:" +"`inspect.isawaitable` to detect them." +msgstr "" + +#: ../Doc/library/collections.abc.rst:213 +msgid "" +"ABC for classes that provide ``__aiter__`` method. See also the definition " +"of :term:`asynchronous iterable`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:220 +msgid "" +"ABC for classes that provide ``__aiter__`` and ``__anext__`` methods. See " +"also the definition of :term:`asynchronous iterator`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:226 +msgid "" +"These ABCs allow us to ask classes or instances if they provide particular " +"functionality, for example::" +msgstr "" + +#: ../Doc/library/collections.abc.rst:233 +msgid "" +"Several of the ABCs are also useful as mixins that make it easier to develop " +"classes supporting container APIs. For example, to write a class supporting " +"the full :class:`Set` API, it is only necessary to supply the three " +"underlying abstract methods: :meth:`__contains__`, :meth:`__iter__`, and :" +"meth:`__len__`. The ABC supplies the remaining methods such as :meth:" +"`__and__` and :meth:`isdisjoint`::" +msgstr "" + +#: ../Doc/library/collections.abc.rst:262 +msgid "Notes on using :class:`Set` and :class:`MutableSet` as a mixin:" +msgstr "" + +#: ../Doc/library/collections.abc.rst:265 +msgid "" +"Since some set operations create new sets, the default mixin methods need a " +"way to create new instances from an iterable. The class constructor is " +"assumed to have a signature in the form ``ClassName(iterable)``. That " +"assumption is factored-out to an internal classmethod called :meth:" +"`_from_iterable` which calls ``cls(iterable)`` to produce a new set. If the :" +"class:`Set` mixin is being used in a class with a different constructor " +"signature, you will need to override :meth:`_from_iterable` with a " +"classmethod that can construct new instances from an iterable argument." +msgstr "" + +#: ../Doc/library/collections.abc.rst:276 +msgid "" +"To override the comparisons (presumably for speed, as the semantics are " +"fixed), redefine :meth:`__le__` and :meth:`__ge__`, then the other " +"operations will automatically follow suit." +msgstr "" + +#: ../Doc/library/collections.abc.rst:281 +msgid "" +"The :class:`Set` mixin provides a :meth:`_hash` method to compute a hash " +"value for the set; however, :meth:`__hash__` is not defined because not all " +"sets are hashable or immutable. To add set hashability using mixins, " +"inherit from both :meth:`Set` and :meth:`Hashable`, then define ``__hash__ = " +"Set._hash``." +msgstr "" + +#: ../Doc/library/collections.abc.rst:289 +msgid "" +"`OrderedSet recipe `_ for an " +"example built on :class:`MutableSet`." +msgstr "" + +#: ../Doc/library/collections.abc.rst:292 +msgid "For more about ABCs, see the :mod:`abc` module and :pep:`3119`." +msgstr "" + +#: ../Doc/library/colorsys.rst:2 +msgid ":mod:`colorsys` --- Conversions between color systems" +msgstr "" + +#: ../Doc/library/colorsys.rst:9 +msgid "**Source code:** :source:`Lib/colorsys.py`" +msgstr "" + +#: ../Doc/library/colorsys.rst:13 +msgid "" +"The :mod:`colorsys` module defines bidirectional conversions of color values " +"between colors expressed in the RGB (Red Green Blue) color space used in " +"computer monitors and three other coordinate systems: YIQ, HLS (Hue " +"Lightness Saturation) and HSV (Hue Saturation Value). Coordinates in all of " +"these color spaces are floating point values. In the YIQ space, the Y " +"coordinate is between 0 and 1, but the I and Q coordinates can be positive " +"or negative. In all other spaces, the coordinates are all between 0 and 1." +msgstr "" + +#: ../Doc/library/colorsys.rst:23 +msgid "" +"More information about color spaces can be found at http://www.poynton.com/" +"ColorFAQ.html and https://www.cambridgeincolour.com/tutorials/color-spaces." +"htm." +msgstr "" + +#: ../Doc/library/colorsys.rst:27 +msgid "The :mod:`colorsys` module defines the following functions:" +msgstr "" + +#: ../Doc/library/colorsys.rst:32 +msgid "Convert the color from RGB coordinates to YIQ coordinates." +msgstr "" + +#: ../Doc/library/colorsys.rst:37 +msgid "Convert the color from YIQ coordinates to RGB coordinates." +msgstr "" + +#: ../Doc/library/colorsys.rst:42 +msgid "Convert the color from RGB coordinates to HLS coordinates." +msgstr "" + +#: ../Doc/library/colorsys.rst:47 +msgid "Convert the color from HLS coordinates to RGB coordinates." +msgstr "" + +#: ../Doc/library/colorsys.rst:52 +msgid "Convert the color from RGB coordinates to HSV coordinates." +msgstr "" + +#: ../Doc/library/colorsys.rst:57 +msgid "Convert the color from HSV coordinates to RGB coordinates." +msgstr "" + +#: ../Doc/library/compileall.rst:2 +msgid ":mod:`compileall` --- Byte-compile Python libraries" +msgstr "" + +#: ../Doc/library/compileall.rst:7 +msgid "**Source code:** :source:`Lib/compileall.py`" +msgstr "" + +#: ../Doc/library/compileall.rst:11 +msgid "" +"This module provides some utility functions to support installing Python " +"libraries. These functions compile Python source files in a directory tree. " +"This module can be used to create the cached byte-code files at library " +"installation time, which makes them available for use even by users who " +"don't have write permission to the library directories." +msgstr "" + +#: ../Doc/library/compileall.rst:19 +msgid "Command-line use" +msgstr "" + +#: ../Doc/library/compileall.rst:21 +msgid "" +"This module can work as a script (using :program:`python -m compileall`) to " +"compile Python sources." +msgstr "" + +#: ../Doc/library/compileall.rst:29 +msgid "" +"Positional arguments are files to compile or directories that contain source " +"files, traversed recursively. If no argument is given, behave as if the " +"command line was ``-l ``." +msgstr "" + +#: ../Doc/library/compileall.rst:35 +msgid "" +"Do not recurse into subdirectories, only compile source code files directly " +"contained in the named or implied directories." +msgstr "" + +#: ../Doc/library/compileall.rst:40 +msgid "Force rebuild even if timestamps are up-to-date." +msgstr "" + +#: ../Doc/library/compileall.rst:44 +msgid "" +"Do not print the list of files compiled. If passed once, error messages will " +"still be printed. If passed twice (``-qq``), all output is suppressed." +msgstr "" + +#: ../Doc/library/compileall.rst:49 +msgid "" +"Directory prepended to the path to each file being compiled. This will " +"appear in compilation time tracebacks, and is also compiled in to the byte-" +"code file, where it will be used in tracebacks and other messages in cases " +"where the source file does not exist at the time the byte-code file is " +"executed." +msgstr "" + +#: ../Doc/library/compileall.rst:57 +msgid "" +"regex is used to search the full path to each file considered for " +"compilation, and if the regex produces a match, the file is skipped." +msgstr "" + +#: ../Doc/library/compileall.rst:62 +msgid "" +"Read the file ``list`` and add each line that it contains to the list of " +"files and directories to compile. If ``list`` is ``-``, read lines from " +"``stdin``." +msgstr "" + +#: ../Doc/library/compileall.rst:68 +msgid "" +"Write the byte-code files to their legacy locations and names, which may " +"overwrite byte-code files created by another version of Python. The default " +"is to write files to their :pep:`3147` locations and names, which allows " +"byte-code files from multiple versions of Python to coexist." +msgstr "" + +#: ../Doc/library/compileall.rst:75 +msgid "" +"Control the maximum recursion level for subdirectories. If this is given, " +"then ``-l`` option will not be taken into account. :program:`python -m " +"compileall -r 0` is equivalent to :program:`python -m compileall " +" -l`." +msgstr "" + +#: ../Doc/library/compileall.rst:82 +msgid "" +"Use *N* workers to compile the files within the given directory. If ``0`` is " +"used, then the result of :func:`os.cpu_count()` will be used." +msgstr "" + +#: ../Doc/library/compileall.rst:86 +msgid "Added the ``-i``, ``-b`` and ``-h`` options." +msgstr "" + +#: ../Doc/library/compileall.rst:89 +msgid "" +"Added the ``-j``, ``-r``, and ``-qq`` options. ``-q`` option was changed " +"to a multilevel value. ``-b`` will always produce a byte-code file ending " +"in ``.pyc``, never ``.pyo``." +msgstr "" + +#: ../Doc/library/compileall.rst:95 +msgid "" +"There is no command-line option to control the optimization level used by " +"the :func:`compile` function, because the Python interpreter itself already " +"provides the option: :program:`python -O -m compileall`." +msgstr "" + +#: ../Doc/library/compileall.rst:100 +msgid "Public functions" +msgstr "" + +#: ../Doc/library/compileall.rst:104 +msgid "" +"Recursively descend the directory tree named by *dir*, compiling all :file:`." +"py` files along the way. Return a true value if all the files compiled " +"successfully, and a false value otherwise." +msgstr "" + +#: ../Doc/library/compileall.rst:108 +msgid "" +"The *maxlevels* parameter is used to limit the depth of the recursion; it " +"defaults to ``10``." +msgstr "" + +#: ../Doc/library/compileall.rst:111 +msgid "" +"If *ddir* is given, it is prepended to the path to each file being compiled " +"for use in compilation time tracebacks, and is also compiled in to the byte-" +"code file, where it will be used in tracebacks and other messages in cases " +"where the source file does not exist at the time the byte-code file is " +"executed." +msgstr "" + +#: ../Doc/library/compileall.rst:117 +msgid "" +"If *force* is true, modules are re-compiled even if the timestamps are up to " +"date." +msgstr "" + +#: ../Doc/library/compileall.rst:120 +msgid "" +"If *rx* is given, its search method is called on the complete path to each " +"file considered for compilation, and if it returns a true value, the file is " +"skipped." +msgstr "" + +#: ../Doc/library/compileall.rst:124 ../Doc/library/compileall.rst:174 +msgid "" +"If *quiet* is ``False`` or ``0`` (the default), the filenames and other " +"information are printed to standard out. Set to ``1``, only errors are " +"printed. Set to ``2``, all output is suppressed." +msgstr "" + +#: ../Doc/library/compileall.rst:128 ../Doc/library/compileall.rst:178 +msgid "" +"If *legacy* is true, byte-code files are written to their legacy locations " +"and names, which may overwrite byte-code files created by another version of " +"Python. The default is to write files to their :pep:`3147` locations and " +"names, which allows byte-code files from multiple versions of Python to " +"coexist." +msgstr "" + +#: ../Doc/library/compileall.rst:134 ../Doc/library/compileall.rst:184 +msgid "" +"*optimize* specifies the optimization level for the compiler. It is passed " +"to the built-in :func:`compile` function." +msgstr "" + +#: ../Doc/library/compileall.rst:137 +msgid "" +"The argument *workers* specifies how many workers are used to compile files " +"in parallel. The default is to not use multiple workers. If the platform " +"can't use multiple workers and *workers* argument is given, then sequential " +"compilation will be used as a fallback. If *workers* is lower than ``0``, " +"a :exc:`ValueError` will be raised." +msgstr "" + +#: ../Doc/library/compileall.rst:143 ../Doc/library/compileall.rst:206 +msgid "Added the *legacy* and *optimize* parameter." +msgstr "" + +#: ../Doc/library/compileall.rst:146 +msgid "Added the *workers* parameter." +msgstr "" + +#: ../Doc/library/compileall.rst:149 ../Doc/library/compileall.rst:189 +#: ../Doc/library/compileall.rst:209 +msgid "*quiet* parameter was changed to a multilevel value." +msgstr "" + +#: ../Doc/library/compileall.rst:152 ../Doc/library/compileall.rst:192 +#: ../Doc/library/compileall.rst:212 +msgid "" +"The *legacy* parameter only writes out ``.pyc`` files, not ``.pyo`` files no " +"matter what the value of *optimize* is." +msgstr "" + +#: ../Doc/library/compileall.rst:161 +msgid "" +"Compile the file with path *fullname*. Return a true value if the file " +"compiled successfully, and a false value otherwise." +msgstr "" + +#: ../Doc/library/compileall.rst:164 +msgid "" +"If *ddir* is given, it is prepended to the path to the file being compiled " +"for use in compilation time tracebacks, and is also compiled in to the byte-" +"code file, where it will be used in tracebacks and other messages in cases " +"where the source file does not exist at the time the byte-code file is " +"executed." +msgstr "" + +#: ../Doc/library/compileall.rst:170 +msgid "" +"If *rx* is given, its search method is passed the full path name to the file " +"being compiled, and if it returns a true value, the file is not compiled and " +"``True`` is returned." +msgstr "" + +#: ../Doc/library/compileall.rst:198 +msgid "" +"Byte-compile all the :file:`.py` files found along ``sys.path``. Return a " +"true value if all the files compiled successfully, and a false value " +"otherwise." +msgstr "" + +#: ../Doc/library/compileall.rst:201 +msgid "" +"If *skip_curdir* is true (the default), the current directory is not " +"included in the search. All other parameters are passed to the :func:" +"`compile_dir` function. Note that unlike the other compile functions, " +"``maxlevels`` defaults to ``0``." +msgstr "" + +#: ../Doc/library/compileall.rst:216 +msgid "" +"To force a recompile of all the :file:`.py` files in the :file:`Lib/` " +"subdirectory and all its subdirectories::" +msgstr "" + +#: ../Doc/library/compileall.rst:233 +msgid "Module :mod:`py_compile`" +msgstr "" + +#: ../Doc/library/compileall.rst:234 +msgid "Byte-compile a single source file." +msgstr "" + +#: ../Doc/library/concurrency.rst:5 +msgid "Concurrent Execution" +msgstr "" + +#: ../Doc/library/concurrency.rst:7 +msgid "" +"The modules described in this chapter provide support for concurrent " +"execution of code. The appropriate choice of tool will depend on the task to " +"be executed (CPU bound vs IO bound) and preferred style of development " +"(event driven cooperative multitasking vs preemptive multitasking). Here's " +"an overview:" +msgstr "" + +#: ../Doc/library/concurrency.rst:25 +msgid "The following are support modules for some of the above services:" +msgstr "" + +#: ../Doc/library/concurrent.rst:2 +msgid "The :mod:`concurrent` package" +msgstr "" + +#: ../Doc/library/concurrent.rst:4 +msgid "Currently, there is only one module in this package:" +msgstr "" + +#: ../Doc/library/concurrent.rst:6 +msgid ":mod:`concurrent.futures` -- Launching parallel tasks" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:2 +msgid ":mod:`concurrent.futures` --- Launching parallel tasks" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:9 +msgid "" +"**Source code:** :source:`Lib/concurrent/futures/thread.py` and :source:`Lib/" +"concurrent/futures/process.py`" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:14 +msgid "" +"The :mod:`concurrent.futures` module provides a high-level interface for " +"asynchronously executing callables." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:17 +msgid "" +"The asynchronous execution can be performed with threads, using :class:" +"`ThreadPoolExecutor`, or separate processes, using :class:" +"`ProcessPoolExecutor`. Both implement the same interface, which is defined " +"by the abstract :class:`Executor` class." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:24 +msgid "Executor Objects" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:28 +msgid "" +"An abstract class that provides methods to execute calls asynchronously. It " +"should not be used directly, but through its concrete subclasses." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:33 +msgid "" +"Schedules the callable, *fn*, to be executed as ``fn(*args **kwargs)`` and " +"returns a :class:`Future` object representing the execution of the " +"callable. ::" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:43 +msgid "" +"Equivalent to :func:`map(func, *iterables) ` except *func* is executed " +"asynchronously and several calls to *func* may be made concurrently. The " +"returned iterator raises a :exc:`concurrent.futures.TimeoutError` if :meth:" +"`~iterator.__next__` is called and the result isn't available after " +"*timeout* seconds from the original call to :meth:`Executor.map`. *timeout* " +"can be an int or a float. If *timeout* is not specified or ``None``, there " +"is no limit to the wait time. If a call raises an exception, then that " +"exception will be raised when its value is retrieved from the iterator. When " +"using :class:`ProcessPoolExecutor`, this method chops *iterables* into a " +"number of chunks which it submits to the pool as separate tasks. The " +"(approximate) size of these chunks can be specified by setting *chunksize* " +"to a positive integer. For very long iterables, using a large value for " +"*chunksize* can significantly improve performance compared to the default " +"size of 1. With :class:`ThreadPoolExecutor`, *chunksize* has no effect." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:59 +msgid "Added the *chunksize* argument." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:64 +msgid "" +"Signal the executor that it should free any resources that it is using when " +"the currently pending futures are done executing. Calls to :meth:`Executor." +"submit` and :meth:`Executor.map` made after shutdown will raise :exc:" +"`RuntimeError`." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:69 +msgid "" +"If *wait* is ``True`` then this method will not return until all the pending " +"futures are done executing and the resources associated with the executor " +"have been freed. If *wait* is ``False`` then this method will return " +"immediately and the resources associated with the executor will be freed " +"when all pending futures are done executing. Regardless of the value of " +"*wait*, the entire Python program will not exit until all pending futures " +"are done executing." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:77 +msgid "" +"You can avoid having to call this method explicitly if you use the :keyword:" +"`with` statement, which will shutdown the :class:`Executor` (waiting as if :" +"meth:`Executor.shutdown` were called with *wait* set to ``True``)::" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:91 +msgid "ThreadPoolExecutor" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:93 +msgid "" +":class:`ThreadPoolExecutor` is an :class:`Executor` subclass that uses a " +"pool of threads to execute calls asynchronously." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:96 +msgid "" +"Deadlocks can occur when the callable associated with a :class:`Future` " +"waits on the results of another :class:`Future`. For example::" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:115 +msgid "And::" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:129 +msgid "" +"An :class:`Executor` subclass that uses a pool of at most *max_workers* " +"threads to execute calls asynchronously." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:132 +msgid "" +"If *max_workers* is ``None`` or not given, it will default to the number of " +"processors on the machine, multiplied by ``5``, assuming that :class:" +"`ThreadPoolExecutor` is often used to overlap I/O instead of CPU work and " +"the number of workers should be higher than the number of workers for :class:" +"`ProcessPoolExecutor`." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:140 +msgid "" +"The *thread_name_prefix* argument was added to allow users to control the " +"threading.Thread names for worker threads created by the pool for easier " +"debugging." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:148 +msgid "ThreadPoolExecutor Example" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:180 +msgid "ProcessPoolExecutor" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:182 +msgid "" +"The :class:`ProcessPoolExecutor` class is an :class:`Executor` subclass that " +"uses a pool of processes to execute calls asynchronously. :class:" +"`ProcessPoolExecutor` uses the :mod:`multiprocessing` module, which allows " +"it to side-step the :term:`Global Interpreter Lock` but also means that only " +"picklable objects can be executed and returned." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:188 +msgid "" +"The ``__main__`` module must be importable by worker subprocesses. This " +"means that :class:`ProcessPoolExecutor` will not work in the interactive " +"interpreter." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:191 +msgid "" +"Calling :class:`Executor` or :class:`Future` methods from a callable " +"submitted to a :class:`ProcessPoolExecutor` will result in deadlock." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:196 +msgid "" +"An :class:`Executor` subclass that executes calls asynchronously using a " +"pool of at most *max_workers* processes. If *max_workers* is ``None`` or " +"not given, it will default to the number of processors on the machine. If " +"*max_workers* is lower or equal to ``0``, then a :exc:`ValueError` will be " +"raised." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:202 +msgid "" +"When one of the worker processes terminates abruptly, a :exc:" +"`BrokenProcessPool` error is now raised. Previously, behaviour was " +"undefined but operations on the executor or its futures would often freeze " +"or deadlock." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:212 +msgid "ProcessPoolExecutor Example" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:246 +msgid "Future Objects" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:248 +msgid "" +"The :class:`Future` class encapsulates the asynchronous execution of a " +"callable. :class:`Future` instances are created by :meth:`Executor.submit`." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:253 +msgid "" +"Encapsulates the asynchronous execution of a callable. :class:`Future` " +"instances are created by :meth:`Executor.submit` and should not be created " +"directly except for testing." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:259 +msgid "" +"Attempt to cancel the call. If the call is currently being executed and " +"cannot be cancelled then the method will return ``False``, otherwise the " +"call will be cancelled and the method will return ``True``." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:265 +msgid "Return ``True`` if the call was successfully cancelled." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:269 +msgid "" +"Return ``True`` if the call is currently being executed and cannot be " +"cancelled." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:274 +msgid "" +"Return ``True`` if the call was successfully cancelled or finished running." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:279 +msgid "" +"Return the value returned by the call. If the call hasn't yet completed then " +"this method will wait up to *timeout* seconds. If the call hasn't completed " +"in *timeout* seconds, then a :exc:`concurrent.futures.TimeoutError` will be " +"raised. *timeout* can be an int or float. If *timeout* is not specified or " +"``None``, there is no limit to the wait time." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:286 +#: ../Doc/library/concurrent.futures.rst:300 +msgid "" +"If the future is cancelled before completing then :exc:`.CancelledError` " +"will be raised." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:289 +msgid "If the call raised, this method will raise the same exception." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:293 +msgid "" +"Return the exception raised by the call. If the call hasn't yet completed " +"then this method will wait up to *timeout* seconds. If the call hasn't " +"completed in *timeout* seconds, then a :exc:`concurrent.futures." +"TimeoutError` will be raised. *timeout* can be an int or float. If " +"*timeout* is not specified or ``None``, there is no limit to the wait time." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:303 +msgid "If the call completed without raising, ``None`` is returned." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:307 +msgid "" +"Attaches the callable *fn* to the future. *fn* will be called, with the " +"future as its only argument, when the future is cancelled or finishes " +"running." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:311 +msgid "" +"Added callables are called in the order that they were added and are always " +"called in a thread belonging to the process that added them. If the " +"callable raises an :exc:`Exception` subclass, it will be logged and " +"ignored. If the callable raises a :exc:`BaseException` subclass, the " +"behavior is undefined." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:317 +msgid "" +"If the future has already completed or been cancelled, *fn* will be called " +"immediately." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:320 +msgid "" +"The following :class:`Future` methods are meant for use in unit tests and :" +"class:`Executor` implementations." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:325 +msgid "" +"This method should only be called by :class:`Executor` implementations " +"before executing the work associated with the :class:`Future` and by unit " +"tests." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:329 +msgid "" +"If the method returns ``False`` then the :class:`Future` was cancelled, i." +"e. :meth:`Future.cancel` was called and returned `True`. Any threads " +"waiting on the :class:`Future` completing (i.e. through :func:`as_completed` " +"or :func:`wait`) will be woken up." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:334 +msgid "" +"If the method returns ``True`` then the :class:`Future` was not cancelled " +"and has been put in the running state, i.e. calls to :meth:`Future.running` " +"will return `True`." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:338 +msgid "" +"This method can only be called once and cannot be called after :meth:`Future." +"set_result` or :meth:`Future.set_exception` have been called." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:344 +msgid "" +"Sets the result of the work associated with the :class:`Future` to *result*." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:347 +#: ../Doc/library/concurrent.futures.rst:355 +msgid "" +"This method should only be used by :class:`Executor` implementations and " +"unit tests." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:352 +msgid "" +"Sets the result of the work associated with the :class:`Future` to the :" +"class:`Exception` *exception*." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:360 ../Doc/library/crypt.rst:75 +msgid "Module Functions" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:364 +msgid "" +"Wait for the :class:`Future` instances (possibly created by different :class:" +"`Executor` instances) given by *fs* to complete. Returns a named 2-tuple of " +"sets. The first set, named ``done``, contains the futures that completed " +"(finished or were cancelled) before the wait completed. The second set, " +"named ``not_done``, contains uncompleted futures." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:374 +msgid "" +"*return_when* indicates when this function should return. It must be one of " +"the following constants:" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:397 +msgid "" +"Returns an iterator over the :class:`Future` instances (possibly created by " +"different :class:`Executor` instances) given by *fs* that yields futures as " +"they complete (finished or were cancelled). Any futures given by *fs* that " +"are duplicated will be returned once. Any futures that completed before :" +"func:`as_completed` is called will be yielded first. The returned iterator " +"raises a :exc:`concurrent.futures.TimeoutError` if :meth:`~iterator." +"__next__` is called and the result isn't available after *timeout* seconds " +"from the original call to :func:`as_completed`. *timeout* can be an int or " +"float. If *timeout* is not specified or ``None``, there is no limit to the " +"wait time." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:411 +msgid ":pep:`3148` -- futures - execute computations asynchronously" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:411 ../Doc/library/logging.rst:1243 +msgid "" +"The proposal which described this feature for inclusion in the Python " +"standard library." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:416 +msgid "Exception classes" +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:422 +msgid "Raised when a future is cancelled." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:426 +msgid "Raised when a future operation exceeds the given timeout." +msgstr "" + +#: ../Doc/library/concurrent.futures.rst:432 +msgid "" +"Derived from :exc:`RuntimeError`, this exception class is raised when one of " +"the workers of a :class:`ProcessPoolExecutor` has terminated in a non-clean " +"fashion (for example, if it was killed from the outside)." +msgstr "" + +#: ../Doc/library/configparser.rst:2 +msgid ":mod:`configparser` --- Configuration file parser" +msgstr "" + +#: ../Doc/library/configparser.rst:14 +msgid "**Source code:** :source:`Lib/configparser.py`" +msgstr "" + +#: ../Doc/library/configparser.rst:24 +msgid "" +"This module provides the :class:`ConfigParser` class which implements a " +"basic configuration language which provides a structure similar to what's " +"found in Microsoft Windows INI files. You can use this to write Python " +"programs which can be customized by end users easily." +msgstr "" + +#: ../Doc/library/configparser.rst:31 +msgid "" +"This library does *not* interpret or write the value-type prefixes used in " +"the Windows Registry extended version of INI syntax." +msgstr "" + +#: ../Doc/library/configparser.rst:38 +msgid "Module :mod:`shlex`" +msgstr "" + +#: ../Doc/library/configparser.rst:37 +msgid "" +"Support for a creating Unix shell-like mini-languages which can be used as " +"an alternate format for application configuration files." +msgstr "" + +#: ../Doc/library/configparser.rst:41 +msgid "Module :mod:`json`" +msgstr "" + +#: ../Doc/library/configparser.rst:41 +msgid "" +"The json module implements a subset of JavaScript syntax which can also be " +"used for this purpose." +msgstr "" + +#: ../Doc/library/configparser.rst:46 +msgid "Quick Start" +msgstr "" + +#: ../Doc/library/configparser.rst:48 +msgid "Let's take a very basic configuration file that looks like this:" +msgstr "" + +#: ../Doc/library/configparser.rst:65 +msgid "" +"The structure of INI files is described `in the following section " +"<#supported-ini-file-structure>`_. Essentially, the file consists of " +"sections, each of which contains keys with values. :mod:`configparser` " +"classes can read and write such files. Let's start by creating the above " +"configuration file programmatically." +msgstr "" + +#: ../Doc/library/configparser.rst:89 +msgid "" +"As you can see, we can treat a config parser much like a dictionary. There " +"are differences, `outlined later <#mapping-protocol-access>`_, but the " +"behavior is very close to what you would expect from a dictionary." +msgstr "" + +#: ../Doc/library/configparser.rst:93 +msgid "" +"Now that we have created and saved a configuration file, let's read it back " +"and explore the data it holds." +msgstr "" + +#: ../Doc/library/configparser.rst:129 +msgid "" +"As we can see above, the API is pretty straightforward. The only bit of " +"magic involves the ``DEFAULT`` section which provides default values for all " +"other sections [1]_. Note also that keys in sections are case-insensitive " +"and stored in lowercase [1]_." +msgstr "" + +#: ../Doc/library/configparser.rst:136 +msgid "Supported Datatypes" +msgstr "" + +#: ../Doc/library/configparser.rst:138 +msgid "" +"Config parsers do not guess datatypes of values in configuration files, " +"always storing them internally as strings. This means that if you need " +"other datatypes, you should convert on your own:" +msgstr "" + +#: ../Doc/library/configparser.rst:149 +msgid "" +"Since this task is so common, config parsers provide a range of handy getter " +"methods to handle integers, floats and booleans. The last one is the most " +"interesting because simply passing the value to ``bool()`` would do no good " +"since ``bool('False')`` is still ``True``. This is why config parsers also " +"provide :meth:`~ConfigParser.getboolean`. This method is case-insensitive " +"and recognizes Boolean values from ``'yes'``/``'no'``, ``'on'``/``'off'``, " +"``'true'``/``'false'`` and ``'1'``/``'0'`` [1]_. For example:" +msgstr "" + +#: ../Doc/library/configparser.rst:166 +msgid "" +"Apart from :meth:`~ConfigParser.getboolean`, config parsers also provide " +"equivalent :meth:`~ConfigParser.getint` and :meth:`~ConfigParser.getfloat` " +"methods. You can register your own converters and customize the provided " +"ones. [1]_" +msgstr "" + +#: ../Doc/library/configparser.rst:172 +msgid "Fallback Values" +msgstr "" + +#: ../Doc/library/configparser.rst:174 +msgid "" +"As with a dictionary, you can use a section's :meth:`get` method to provide " +"fallback values:" +msgstr "" + +#: ../Doc/library/configparser.rst:187 +msgid "" +"Please note that default values have precedence over fallback values. For " +"instance, in our example the ``'CompressionLevel'`` key was specified only " +"in the ``'DEFAULT'`` section. If we try to get it from the section " +"``'topsecret.server.com'``, we will always get the default, even if we " +"specify a fallback:" +msgstr "" + +#: ../Doc/library/configparser.rst:198 +msgid "" +"One more thing to be aware of is that the parser-level :meth:`get` method " +"provides a custom, more complex interface, maintained for backwards " +"compatibility. When using this method, a fallback value can be provided via " +"the ``fallback`` keyword-only argument:" +msgstr "" + +#: ../Doc/library/configparser.rst:209 +msgid "" +"The same ``fallback`` argument can be used with the :meth:`~ConfigParser." +"getint`, :meth:`~ConfigParser.getfloat` and :meth:`~ConfigParser.getboolean` " +"methods, for example:" +msgstr "" + +#: ../Doc/library/configparser.rst:225 +msgid "Supported INI File Structure" +msgstr "" + +#: ../Doc/library/configparser.rst:227 +msgid "" +"A configuration file consists of sections, each led by a ``[section]`` " +"header, followed by key/value entries separated by a specific string (``=`` " +"or ``:`` by default [1]_). By default, section names are case sensitive but " +"keys are not [1]_. Leading and trailing whitespace is removed from keys and " +"values. Values can be omitted, in which case the key/value delimiter may " +"also be left out. Values can also span multiple lines, as long as they are " +"indented deeper than the first line of the value. Depending on the parser's " +"mode, blank lines may be treated as parts of multiline values or ignored." +msgstr "" + +#: ../Doc/library/configparser.rst:236 +msgid "" +"Configuration files may include comments, prefixed by specific characters " +"(``#`` and ``;`` by default [1]_). Comments may appear on their own on an " +"otherwise empty line, possibly indented. [1]_" +msgstr "" + +#: ../Doc/library/configparser.rst:240 ../Doc/library/configparser.rst:301 +#: ../Doc/library/inspect.rst:885 ../Doc/library/multiprocessing.rst:1103 +#: ../Doc/library/re.rst:1046 ../Doc/library/time.rst:509 +#: ../Doc/library/turtle.rst:1485 ../Doc/library/unittest.mock.rst:1750 +msgid "For example:" +msgstr "" + +#: ../Doc/library/configparser.rst:288 +msgid "Interpolation of values" +msgstr "" + +#: ../Doc/library/configparser.rst:290 +msgid "" +"On top of the core functionality, :class:`ConfigParser` supports " +"interpolation. This means values can be preprocessed before returning them " +"from ``get()`` calls." +msgstr "" + +#: ../Doc/library/configparser.rst:296 +msgid "" +"The default implementation used by :class:`ConfigParser`. It enables values " +"to contain format strings which refer to other values in the same section, " +"or values in the special default section [1]_. Additional default values " +"can be provided on initialization." +msgstr "" + +#: ../Doc/library/configparser.rst:311 +msgid "" +"In the example above, :class:`ConfigParser` with *interpolation* set to " +"``BasicInterpolation()`` would resolve ``%(home_dir)s`` to the value of " +"``home_dir`` (``/Users`` in this case). ``%(my_dir)s`` in effect would " +"resolve to ``/Users/lumberjack``. All interpolations are done on demand so " +"keys used in the chain of references do not have to be specified in any " +"specific order in the configuration file." +msgstr "" + +#: ../Doc/library/configparser.rst:318 +msgid "" +"With ``interpolation`` set to ``None``, the parser would simply return ``" +"%(my_dir)s/Pictures`` as the value of ``my_pictures`` and ``%(home_dir)s/" +"lumberjack`` as the value of ``my_dir``." +msgstr "" + +#: ../Doc/library/configparser.rst:324 +msgid "" +"An alternative handler for interpolation which implements a more advanced " +"syntax, used for instance in ``zc.buildout``. Extended interpolation is " +"using ``${section:option}`` to denote a value from a foreign section. " +"Interpolation can span multiple levels. For convenience, if the ``section:" +"`` part is omitted, interpolation defaults to the current section (and " +"possibly the default values from the special section)." +msgstr "" + +#: ../Doc/library/configparser.rst:331 +msgid "" +"For example, the configuration specified above with basic interpolation, " +"would look like this with extended interpolation:" +msgstr "" + +#: ../Doc/library/configparser.rst:341 +msgid "Values from other sections can be fetched as well:" +msgstr "" + +#: ../Doc/library/configparser.rst:363 +msgid "Mapping Protocol Access" +msgstr "" + +#: ../Doc/library/configparser.rst:367 +msgid "" +"Mapping protocol access is a generic name for functionality that enables " +"using custom objects as if they were dictionaries. In case of :mod:" +"`configparser`, the mapping interface implementation is using the " +"``parser['section']['option']`` notation." +msgstr "" + +#: ../Doc/library/configparser.rst:372 +msgid "" +"``parser['section']`` in particular returns a proxy for the section's data " +"in the parser. This means that the values are not copied but they are taken " +"from the original parser on demand. What's even more important is that when " +"values are changed on a section proxy, they are actually mutated in the " +"original parser." +msgstr "" + +#: ../Doc/library/configparser.rst:378 +msgid "" +":mod:`configparser` objects behave as close to actual dictionaries as " +"possible. The mapping interface is complete and adheres to the :class:" +"`~collections.abc.MutableMapping` ABC. However, there are a few differences " +"that should be taken into account:" +msgstr "" + +#: ../Doc/library/configparser.rst:383 +msgid "" +"By default, all keys in sections are accessible in a case-insensitive manner " +"[1]_. E.g. ``for option in parser[\"section\"]`` yields only " +"``optionxform``'ed option key names. This means lowercased keys by " +"default. At the same time, for a section that holds the key ``'a'``, both " +"expressions return ``True``::" +msgstr "" + +#: ../Doc/library/configparser.rst:391 +msgid "" +"All sections include ``DEFAULTSECT`` values as well which means that ``." +"clear()`` on a section may not leave the section visibly empty. This is " +"because default values cannot be deleted from the section (because " +"technically they are not there). If they are overridden in the section, " +"deleting causes the default value to be visible again. Trying to delete a " +"default value causes a ``KeyError``." +msgstr "" + +#: ../Doc/library/configparser.rst:398 +msgid "``DEFAULTSECT`` cannot be removed from the parser:" +msgstr "" + +#: ../Doc/library/configparser.rst:400 +msgid "trying to delete it raises ``ValueError``," +msgstr "" + +#: ../Doc/library/configparser.rst:402 +msgid "``parser.clear()`` leaves it intact," +msgstr "" + +#: ../Doc/library/configparser.rst:404 +msgid "``parser.popitem()`` never returns it." +msgstr "" + +#: ../Doc/library/configparser.rst:406 +msgid "" +"``parser.get(section, option, **kwargs)`` - the second argument is **not** a " +"fallback value. Note however that the section-level ``get()`` methods are " +"compatible both with the mapping protocol and the classic configparser API." +msgstr "" + +#: ../Doc/library/configparser.rst:410 +msgid "" +"``parser.items()`` is compatible with the mapping protocol (returns a list " +"of *section_name*, *section_proxy* pairs including the DEFAULTSECT). " +"However, this method can also be invoked with arguments: ``parser." +"items(section, raw, vars)``. The latter call returns a list of *option*, " +"*value* pairs for a specified ``section``, with all interpolations expanded " +"(unless ``raw=True`` is provided)." +msgstr "" + +#: ../Doc/library/configparser.rst:417 +msgid "" +"The mapping protocol is implemented on top of the existing legacy API so " +"that subclasses overriding the original interface still should have mappings " +"working as expected." +msgstr "" + +#: ../Doc/library/configparser.rst:423 +msgid "Customizing Parser Behaviour" +msgstr "" + +#: ../Doc/library/configparser.rst:425 +msgid "" +"There are nearly as many INI format variants as there are applications using " +"it. :mod:`configparser` goes a long way to provide support for the largest " +"sensible set of INI styles available. The default functionality is mainly " +"dictated by historical background and it's very likely that you will want to " +"customize some of the features." +msgstr "" + +#: ../Doc/library/configparser.rst:431 +msgid "" +"The most common way to change the way a specific config parser works is to " +"use the :meth:`__init__` options:" +msgstr "" + +#: ../Doc/library/configparser.rst:434 +msgid "*defaults*, default value: ``None``" +msgstr "" + +#: ../Doc/library/configparser.rst:436 +msgid "" +"This option accepts a dictionary of key-value pairs which will be initially " +"put in the ``DEFAULT`` section. This makes for an elegant way to support " +"concise configuration files that don't specify values which are the same as " +"the documented default." +msgstr "" + +#: ../Doc/library/configparser.rst:441 +msgid "" +"Hint: if you want to specify default values for a specific section, use :" +"meth:`read_dict` before you read the actual file." +msgstr "" + +#: ../Doc/library/configparser.rst:444 +msgid "*dict_type*, default value: :class:`collections.OrderedDict`" +msgstr "" + +#: ../Doc/library/configparser.rst:446 +msgid "" +"This option has a major impact on how the mapping protocol will behave and " +"how the written configuration files look. With the default ordered " +"dictionary, every section is stored in the order they were added to the " +"parser. Same goes for options within sections." +msgstr "" + +#: ../Doc/library/configparser.rst:451 +msgid "" +"An alternative dictionary type can be used for example to sort sections and " +"options on write-back. You can also use a regular dictionary for " +"performance reasons." +msgstr "" + +#: ../Doc/library/configparser.rst:455 +msgid "" +"Please note: there are ways to add a set of key-value pairs in a single " +"operation. When you use a regular dictionary in those operations, the order " +"of the keys may be random. For example:" +msgstr "" + +#: ../Doc/library/configparser.rst:477 +msgid "In these operations you need to use an ordered dictionary as well:" +msgstr "" + +#: ../Doc/library/configparser.rst:508 +msgid "*allow_no_value*, default value: ``False``" +msgstr "" + +#: ../Doc/library/configparser.rst:510 +msgid "" +"Some configuration files are known to include settings without values, but " +"which otherwise conform to the syntax supported by :mod:`configparser`. The " +"*allow_no_value* parameter to the constructor can be used to indicate that " +"such values should be accepted:" +msgstr "" + +#: ../Doc/library/configparser.rst:545 +msgid "*delimiters*, default value: ``('=', ':')``" +msgstr "" + +#: ../Doc/library/configparser.rst:547 +msgid "" +"Delimiters are substrings that delimit keys from values within a section. " +"The first occurrence of a delimiting substring on a line is considered a " +"delimiter. This means values (but not keys) can contain the delimiters." +msgstr "" + +#: ../Doc/library/configparser.rst:551 +msgid "" +"See also the *space_around_delimiters* argument to :meth:`ConfigParser." +"write`." +msgstr "" + +#: ../Doc/library/configparser.rst:554 +msgid "*comment_prefixes*, default value: ``('#', ';')``" +msgstr "" + +#: ../Doc/library/configparser.rst:556 +msgid "*inline_comment_prefixes*, default value: ``None``" +msgstr "" + +#: ../Doc/library/configparser.rst:558 +msgid "" +"Comment prefixes are strings that indicate the start of a valid comment " +"within a config file. *comment_prefixes* are used only on otherwise empty " +"lines (optionally indented) whereas *inline_comment_prefixes* can be used " +"after every valid value (e.g. section names, options and empty lines as " +"well). By default inline comments are disabled and ``'#'`` and ``';'`` are " +"used as prefixes for whole line comments." +msgstr "" + +#: ../Doc/library/configparser.rst:565 +msgid "" +"In previous versions of :mod:`configparser` behaviour matched " +"``comment_prefixes=('#',';')`` and ``inline_comment_prefixes=(';',)``." +msgstr "" + +#: ../Doc/library/configparser.rst:569 +msgid "" +"Please note that config parsers don't support escaping of comment prefixes " +"so using *inline_comment_prefixes* may prevent users from specifying option " +"values with characters used as comment prefixes. When in doubt, avoid " +"setting *inline_comment_prefixes*. In any circumstances, the only way of " +"storing comment prefix characters at the beginning of a line in multiline " +"values is to interpolate the prefix, for example::" +msgstr "" + +#: ../Doc/library/configparser.rst:615 +msgid "*strict*, default value: ``True``" +msgstr "" + +#: ../Doc/library/configparser.rst:617 +msgid "" +"When set to ``True``, the parser will not allow for any section or option " +"duplicates while reading from a single source (using :meth:`read_file`, :" +"meth:`read_string` or :meth:`read_dict`). It is recommended to use strict " +"parsers in new applications." +msgstr "" + +#: ../Doc/library/configparser.rst:622 +msgid "" +"In previous versions of :mod:`configparser` behaviour matched " +"``strict=False``." +msgstr "" + +#: ../Doc/library/configparser.rst:626 +msgid "*empty_lines_in_values*, default value: ``True``" +msgstr "" + +#: ../Doc/library/configparser.rst:628 +msgid "" +"In config parsers, values can span multiple lines as long as they are " +"indented more than the key that holds them. By default parsers also let " +"empty lines to be parts of values. At the same time, keys can be " +"arbitrarily indented themselves to improve readability. In consequence, " +"when configuration files get big and complex, it is easy for the user to " +"lose track of the file structure. Take for instance:" +msgstr "" + +#: ../Doc/library/configparser.rst:643 +msgid "" +"This can be especially problematic for the user to see if she's using a " +"proportional font to edit the file. That is why when your application does " +"not need values with empty lines, you should consider disallowing them. " +"This will make empty lines split keys every time. In the example above, it " +"would produce two keys, ``key`` and ``this``." +msgstr "" + +#: ../Doc/library/configparser.rst:649 +msgid "" +"*default_section*, default value: ``configparser.DEFAULTSECT`` (that is: ``" +"\"DEFAULT\"``)" +msgstr "" + +#: ../Doc/library/configparser.rst:652 +msgid "" +"The convention of allowing a special section of default values for other " +"sections or interpolation purposes is a powerful concept of this library, " +"letting users create complex declarative configurations. This section is " +"normally called ``\"DEFAULT\"`` but this can be customized to point to any " +"other valid section name. Some typical values include: ``\"general\"`` or ``" +"\"common\"``. The name provided is used for recognizing default sections " +"when reading from any source and is used when writing configuration back to " +"a file. Its current value can be retrieved using the ``parser_instance." +"default_section`` attribute and may be modified at runtime (i.e. to convert " +"files from one format to another)." +msgstr "" + +#: ../Doc/library/configparser.rst:663 +msgid "*interpolation*, default value: ``configparser.BasicInterpolation``" +msgstr "" + +#: ../Doc/library/configparser.rst:665 +msgid "" +"Interpolation behaviour may be customized by providing a custom handler " +"through the *interpolation* argument. ``None`` can be used to turn off " +"interpolation completely, ``ExtendedInterpolation()`` provides a more " +"advanced variant inspired by ``zc.buildout``. More on the subject in the " +"`dedicated documentation section <#interpolation-of-values>`_. :class:" +"`RawConfigParser` has a default value of ``None``." +msgstr "" + +#: ../Doc/library/configparser.rst:672 +msgid "*converters*, default value: not set" +msgstr "" + +#: ../Doc/library/configparser.rst:674 +msgid "" +"Config parsers provide option value getters that perform type conversion. " +"By default :meth:`~ConfigParser.getint`, :meth:`~ConfigParser.getfloat`, " +"and :meth:`~ConfigParser.getboolean` are implemented. Should other getters " +"be desirable, users may define them in a subclass or pass a dictionary where " +"each key is a name of the converter and each value is a callable " +"implementing said conversion. For instance, passing ``{'decimal': decimal." +"Decimal}`` would add :meth:`getdecimal` on both the parser object and all " +"section proxies. In other words, it will be possible to write both " +"``parser_instance.getdecimal('section', 'key', fallback=0)`` and " +"``parser_instance['section'].getdecimal('key', 0)``." +msgstr "" + +#: ../Doc/library/configparser.rst:685 +msgid "" +"If the converter needs to access the state of the parser, it can be " +"implemented as a method on a config parser subclass. If the name of this " +"method starts with ``get``, it will be available on all section proxies, in " +"the dict-compatible form (see the ``getdecimal()`` example above)." +msgstr "" + +#: ../Doc/library/configparser.rst:690 +msgid "" +"More advanced customization may be achieved by overriding default values of " +"these parser attributes. The defaults are defined on the classes, so they " +"may be overridden by subclasses or by attribute assignment." +msgstr "" + +#: ../Doc/library/configparser.rst:696 +msgid "" +"By default when using :meth:`~ConfigParser.getboolean`, config parsers " +"consider the following values ``True``: ``'1'``, ``'yes'``, ``'true'``, " +"``'on'`` and the following values ``False``: ``'0'``, ``'no'``, ``'false'``, " +"``'off'``. You can override this by specifying a custom dictionary of " +"strings and their Boolean outcomes. For example:" +msgstr "" + +#: ../Doc/library/configparser.rst:714 +msgid "" +"Other typical Boolean pairs include ``accept``/``reject`` or ``enabled``/" +"``disabled``." +msgstr "" + +#: ../Doc/library/configparser.rst:719 +msgid "" +"This method transforms option names on every read, get, or set operation. " +"The default converts the name to lowercase. This also means that when a " +"configuration file gets written, all keys will be lowercase. Override this " +"method if that's unsuitable. For example:" +msgstr "" + +#: ../Doc/library/configparser.rst:750 +msgid "" +"A compiled regular expression used to parse section headers. The default " +"matches ``[section]`` to the name ``\"section\"``. Whitespace is considered " +"part of the section name, thus ``[ larch ]`` will be read as a section of " +"name ``\" larch \"``. Override this attribute if that's unsuitable. For " +"example:" +msgstr "" + +#: ../Doc/library/configparser.rst:777 +msgid "" +"While ConfigParser objects also use an ``OPTCRE`` attribute for recognizing " +"option lines, it's not recommended to override it because that would " +"interfere with constructor options *allow_no_value* and *delimiters*." +msgstr "" + +#: ../Doc/library/configparser.rst:783 +msgid "Legacy API Examples" +msgstr "" + +#: ../Doc/library/configparser.rst:785 +msgid "" +"Mainly because of backwards compatibility concerns, :mod:`configparser` " +"provides also a legacy API with explicit ``get``/``set`` methods. While " +"there are valid use cases for the methods outlined below, mapping protocol " +"access is preferred for new projects. The legacy API is at times more " +"advanced, low-level and downright counterintuitive." +msgstr "" + +#: ../Doc/library/configparser.rst:791 +msgid "An example of writing to a configuration file::" +msgstr "" + +#: ../Doc/library/configparser.rst:814 +msgid "An example of reading the configuration file again::" +msgstr "" + +#: ../Doc/library/configparser.rst:832 +msgid "To get interpolation, use :class:`ConfigParser`::" +msgstr "" + +#: ../Doc/library/configparser.rst:865 +msgid "" +"Default values are available in both types of ConfigParsers. They are used " +"in interpolation if an option used is not defined elsewhere. ::" +msgstr "" + +#: ../Doc/library/configparser.rst:883 +msgid "ConfigParser Objects" +msgstr "" + +#: ../Doc/library/configparser.rst:887 +msgid "" +"The main configuration parser. When *defaults* is given, it is initialized " +"into the dictionary of intrinsic defaults. When *dict_type* is given, it " +"will be used to create the dictionary objects for the list of sections, for " +"the options within a section, and for the default values." +msgstr "" + +#: ../Doc/library/configparser.rst:892 +msgid "" +"When *delimiters* is given, it is used as the set of substrings that divide " +"keys from values. When *comment_prefixes* is given, it will be used as the " +"set of substrings that prefix comments in otherwise empty lines. Comments " +"can be indented. When *inline_comment_prefixes* is given, it will be used " +"as the set of substrings that prefix comments in non-empty lines." +msgstr "" + +#: ../Doc/library/configparser.rst:898 +msgid "" +"When *strict* is ``True`` (the default), the parser won't allow for any " +"section or option duplicates while reading from a single source (file, " +"string or dictionary), raising :exc:`DuplicateSectionError` or :exc:" +"`DuplicateOptionError`. When *empty_lines_in_values* is ``False`` (default: " +"``True``), each empty line marks the end of an option. Otherwise, internal " +"empty lines of a multiline option are kept as part of the value. When " +"*allow_no_value* is ``True`` (default: ``False``), options without values " +"are accepted; the value held for these is ``None`` and they are serialized " +"without the trailing delimiter." +msgstr "" + +#: ../Doc/library/configparser.rst:908 +msgid "" +"When *default_section* is given, it specifies the name for the special " +"section holding default values for other sections and interpolation purposes " +"(normally named ``\"DEFAULT\"``). This value can be retrieved and changed " +"on runtime using the ``default_section`` instance attribute." +msgstr "" + +#: ../Doc/library/configparser.rst:913 +msgid "" +"Interpolation behaviour may be customized by providing a custom handler " +"through the *interpolation* argument. ``None`` can be used to turn off " +"interpolation completely, ``ExtendedInterpolation()`` provides a more " +"advanced variant inspired by ``zc.buildout``. More on the subject in the " +"`dedicated documentation section <#interpolation-of-values>`_." +msgstr "" + +#: ../Doc/library/configparser.rst:919 +msgid "" +"All option names used in interpolation will be passed through the :meth:" +"`optionxform` method just like any other option name reference. For " +"example, using the default implementation of :meth:`optionxform` (which " +"converts option names to lower case), the values ``foo %(bar)s`` and ``foo " +"%(BAR)s`` are equivalent." +msgstr "" + +#: ../Doc/library/configparser.rst:925 +msgid "" +"When *converters* is given, it should be a dictionary where each key " +"represents the name of a type converter and each value is a callable " +"implementing the conversion from string to the desired datatype. Every " +"converter gets its own corresponding :meth:`get*()` method on the parser " +"object and section proxies." +msgstr "" + +#: ../Doc/library/configparser.rst:931 +msgid "The default *dict_type* is :class:`collections.OrderedDict`." +msgstr "" + +#: ../Doc/library/configparser.rst:934 +msgid "" +"*allow_no_value*, *delimiters*, *comment_prefixes*, *strict*, " +"*empty_lines_in_values*, *default_section* and *interpolation* were added." +msgstr "" + +#: ../Doc/library/configparser.rst:939 +msgid "The *converters* argument was added." +msgstr "" + +#: ../Doc/library/configparser.rst:945 +msgid "Return a dictionary containing the instance-wide defaults." +msgstr "" + +#: ../Doc/library/configparser.rst:950 +msgid "" +"Return a list of the sections available; the *default section* is not " +"included in the list." +msgstr "" + +#: ../Doc/library/configparser.rst:956 +msgid "" +"Add a section named *section* to the instance. If a section by the given " +"name already exists, :exc:`DuplicateSectionError` is raised. If the " +"*default section* name is passed, :exc:`ValueError` is raised. The name of " +"the section must be a string; if not, :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/configparser.rst:961 +msgid "Non-string section names raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/configparser.rst:967 +msgid "" +"Indicates whether the named *section* is present in the configuration. The " +"*default section* is not acknowledged." +msgstr "" + +#: ../Doc/library/configparser.rst:973 +msgid "Return a list of options available in the specified *section*." +msgstr "" + +#: ../Doc/library/configparser.rst:978 +msgid "" +"If the given *section* exists, and contains the given *option*, return :" +"const:`True`; otherwise return :const:`False`. If the specified *section* " +"is :const:`None` or an empty string, DEFAULT is assumed." +msgstr "" + +#: ../Doc/library/configparser.rst:985 +msgid "" +"Attempt to read and parse a list of filenames, returning a list of filenames " +"which were successfully parsed. If *filenames* is a string, it is treated " +"as a single filename. If a file named in *filenames* cannot be opened, that " +"file will be ignored. This is designed so that you can specify a list of " +"potential configuration file locations (for example, the current directory, " +"the user's home directory, and some system-wide directory), and all existing " +"configuration files in the list will be read. If none of the named files " +"exist, the :class:`ConfigParser` instance will contain an empty dataset. An " +"application which requires initial values to be loaded from a file should " +"load the required file or files using :meth:`read_file` before calling :meth:" +"`read` for any optional files::" +msgstr "" + +#: ../Doc/library/configparser.rst:1005 +msgid "" +"The *encoding* parameter. Previously, all files were read using the default " +"encoding for :func:`open`." +msgstr "" + +#: ../Doc/library/configparser.rst:1012 +msgid "" +"Read and parse configuration data from *f* which must be an iterable " +"yielding Unicode strings (for example files opened in text mode)." +msgstr "" + +#: ../Doc/library/configparser.rst:1015 +msgid "" +"Optional argument *source* specifies the name of the file being read. If " +"not given and *f* has a :attr:`name` attribute, that is used for *source*; " +"the default is ``''``." +msgstr "" + +#: ../Doc/library/configparser.rst:1019 +msgid "Replaces :meth:`readfp`." +msgstr "" + +#: ../Doc/library/configparser.rst:1024 +msgid "Parse configuration data from a string." +msgstr "" + +#: ../Doc/library/configparser.rst:1026 +msgid "" +"Optional argument *source* specifies a context-specific name of the string " +"passed. If not given, ``''`` is used. This should commonly be a " +"filesystem path or a URL." +msgstr "" + +#: ../Doc/library/configparser.rst:1035 +msgid "" +"Load configuration from any object that provides a dict-like ``items()`` " +"method. Keys are section names, values are dictionaries with keys and " +"values that should be present in the section. If the used dictionary type " +"preserves order, sections and their keys will be added in order. Values are " +"automatically converted to strings." +msgstr "" + +#: ../Doc/library/configparser.rst:1041 +msgid "" +"Optional argument *source* specifies a context-specific name of the " +"dictionary passed. If not given, ```` is used." +msgstr "" + +#: ../Doc/library/configparser.rst:1044 +msgid "This method can be used to copy state between parsers." +msgstr "" + +#: ../Doc/library/configparser.rst:1051 +msgid "" +"Get an *option* value for the named *section*. If *vars* is provided, it " +"must be a dictionary. The *option* is looked up in *vars* (if provided), " +"*section*, and in *DEFAULTSECT* in that order. If the key is not found and " +"*fallback* is provided, it is used as a fallback value. ``None`` can be " +"provided as a *fallback* value." +msgstr "" + +#: ../Doc/library/configparser.rst:1057 +msgid "" +"All the ``'%'`` interpolations are expanded in the return values, unless the " +"*raw* argument is true. Values for interpolation keys are looked up in the " +"same manner as the option." +msgstr "" + +#: ../Doc/library/configparser.rst:1061 +msgid "" +"Arguments *raw*, *vars* and *fallback* are keyword only to protect users " +"from trying to use the third argument as the *fallback* fallback (especially " +"when using the mapping protocol)." +msgstr "" + +#: ../Doc/library/configparser.rst:1069 +msgid "" +"A convenience method which coerces the *option* in the specified *section* " +"to an integer. See :meth:`get` for explanation of *raw*, *vars* and " +"*fallback*." +msgstr "" + +#: ../Doc/library/configparser.rst:1076 +msgid "" +"A convenience method which coerces the *option* in the specified *section* " +"to a floating point number. See :meth:`get` for explanation of *raw*, " +"*vars* and *fallback*." +msgstr "" + +#: ../Doc/library/configparser.rst:1083 +msgid "" +"A convenience method which coerces the *option* in the specified *section* " +"to a Boolean value. Note that the accepted values for the option are " +"``'1'``, ``'yes'``, ``'true'``, and ``'on'``, which cause this method to " +"return ``True``, and ``'0'``, ``'no'``, ``'false'``, and ``'off'``, which " +"cause it to return ``False``. These string values are checked in a case-" +"insensitive manner. Any other value will cause it to raise :exc:" +"`ValueError`. See :meth:`get` for explanation of *raw*, *vars* and " +"*fallback*." +msgstr "" + +#: ../Doc/library/configparser.rst:1096 +msgid "" +"When *section* is not given, return a list of *section_name*, " +"*section_proxy* pairs, including DEFAULTSECT." +msgstr "" + +#: ../Doc/library/configparser.rst:1099 +msgid "" +"Otherwise, return a list of *name*, *value* pairs for the options in the " +"given *section*. Optional arguments have the same meaning as for the :meth:" +"`get` method." +msgstr "" + +#: ../Doc/library/configparser.rst:1103 +msgid "" +"Items present in *vars* no longer appear in the result. The previous " +"behaviour mixed actual parser options with variables provided for " +"interpolation." +msgstr "" + +#: ../Doc/library/configparser.rst:1110 +msgid "" +"If the given section exists, set the given option to the specified value; " +"otherwise raise :exc:`NoSectionError`. *option* and *value* must be " +"strings; if not, :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/configparser.rst:1117 +msgid "" +"Write a representation of the configuration to the specified :term:`file " +"object`, which must be opened in text mode (accepting strings). This " +"representation can be parsed by a future :meth:`read` call. If " +"*space_around_delimiters* is true, delimiters between keys and values are " +"surrounded by spaces." +msgstr "" + +#: ../Doc/library/configparser.rst:1126 +msgid "" +"Remove the specified *option* from the specified *section*. If the section " +"does not exist, raise :exc:`NoSectionError`. If the option existed to be " +"removed, return :const:`True`; otherwise return :const:`False`." +msgstr "" + +#: ../Doc/library/configparser.rst:1134 +msgid "" +"Remove the specified *section* from the configuration. If the section in " +"fact existed, return ``True``. Otherwise return ``False``." +msgstr "" + +#: ../Doc/library/configparser.rst:1140 +msgid "" +"Transforms the option name *option* as found in an input file or as passed " +"in by client code to the form that should be used in the internal " +"structures. The default implementation returns a lower-case version of " +"*option*; subclasses may override this or client code can set an attribute " +"of this name on instances to affect this behavior." +msgstr "" + +#: ../Doc/library/configparser.rst:1146 +msgid "" +"You don't need to subclass the parser to use this method, you can also set " +"it on an instance, to a function that takes a string argument and returns a " +"string. Setting it to ``str``, for example, would make option names case " +"sensitive::" +msgstr "" + +#: ../Doc/library/configparser.rst:1154 +msgid "" +"Note that when reading configuration files, whitespace around the option " +"names is stripped before :meth:`optionxform` is called." +msgstr "" + +#: ../Doc/library/configparser.rst:1160 +msgid "Use :meth:`read_file` instead." +msgstr "" + +#: ../Doc/library/configparser.rst:1163 +msgid ":meth:`readfp` now iterates on *f* instead of calling ``f.readline()``." +msgstr "" + +#: ../Doc/library/configparser.rst:1166 +msgid "" +"For existing code calling :meth:`readfp` with arguments which don't support " +"iteration, the following generator may be used as a wrapper around the file-" +"like object::" +msgstr "" + +#: ../Doc/library/configparser.rst:1176 +msgid "" +"Instead of ``parser.readfp(f)`` use ``parser." +"read_file(readline_generator(f))``." +msgstr "" + +#: ../Doc/library/configparser.rst:1182 +msgid "" +"The maximum depth for recursive interpolation for :meth:`get` when the *raw* " +"parameter is false. This is relevant only when the default *interpolation* " +"is used." +msgstr "" + +#: ../Doc/library/configparser.rst:1190 +msgid "RawConfigParser Objects" +msgstr "" + +#: ../Doc/library/configparser.rst:1200 +msgid "" +"Legacy variant of the :class:`ConfigParser` with interpolation disabled by " +"default and unsafe ``add_section`` and ``set`` methods." +msgstr "" + +#: ../Doc/library/configparser.rst:1204 +msgid "" +"Consider using :class:`ConfigParser` instead which checks types of the " +"values to be stored internally. If you don't want interpolation, you can " +"use ``ConfigParser(interpolation=None)``." +msgstr "" + +#: ../Doc/library/configparser.rst:1211 +msgid "" +"Add a section named *section* to the instance. If a section by the given " +"name already exists, :exc:`DuplicateSectionError` is raised. If the " +"*default section* name is passed, :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/configparser.rst:1215 +msgid "" +"Type of *section* is not checked which lets users create non-string named " +"sections. This behaviour is unsupported and may cause internal errors." +msgstr "" + +#: ../Doc/library/configparser.rst:1221 +msgid "" +"If the given section exists, set the given option to the specified value; " +"otherwise raise :exc:`NoSectionError`. While it is possible to use :class:" +"`RawConfigParser` (or :class:`ConfigParser` with *raw* parameters set to " +"true) for *internal* storage of non-string values, full functionality " +"(including interpolation and output to files) can only be achieved using " +"string values." +msgstr "" + +#: ../Doc/library/configparser.rst:1228 +msgid "" +"This method lets users assign non-string values to keys internally. This " +"behaviour is unsupported and will cause errors when attempting to write to a " +"file or get it in non-raw mode. **Use the mapping protocol API** which does " +"not allow such assignments to take place." +msgstr "" + +#: ../Doc/library/configparser.rst:1239 +msgid "Base class for all other :mod:`configparser` exceptions." +msgstr "" + +#: ../Doc/library/configparser.rst:1244 +msgid "Exception raised when a specified section is not found." +msgstr "" + +#: ../Doc/library/configparser.rst:1249 +msgid "" +"Exception raised if :meth:`add_section` is called with the name of a section " +"that is already present or in strict parsers when a section if found more " +"than once in a single input file, string or dictionary." +msgstr "" + +#: ../Doc/library/configparser.rst:1253 +msgid "" +"Optional ``source`` and ``lineno`` attributes and arguments to :meth:" +"`__init__` were added." +msgstr "" + +#: ../Doc/library/configparser.rst:1260 +msgid "" +"Exception raised by strict parsers if a single option appears twice during " +"reading from a single file, string or dictionary. This catches misspellings " +"and case sensitivity-related errors, e.g. a dictionary may have two keys " +"representing the same case-insensitive configuration key." +msgstr "" + +#: ../Doc/library/configparser.rst:1268 +msgid "" +"Exception raised when a specified option is not found in the specified " +"section." +msgstr "" + +#: ../Doc/library/configparser.rst:1274 +msgid "" +"Base class for exceptions raised when problems occur performing string " +"interpolation." +msgstr "" + +#: ../Doc/library/configparser.rst:1280 +msgid "" +"Exception raised when string interpolation cannot be completed because the " +"number of iterations exceeds :const:`MAX_INTERPOLATION_DEPTH`. Subclass of :" +"exc:`InterpolationError`." +msgstr "" + +#: ../Doc/library/configparser.rst:1287 +msgid "" +"Exception raised when an option referenced from a value does not exist. " +"Subclass of :exc:`InterpolationError`." +msgstr "" + +#: ../Doc/library/configparser.rst:1293 +msgid "" +"Exception raised when the source text into which substitutions are made does " +"not conform to the required syntax. Subclass of :exc:`InterpolationError`." +msgstr "" + +#: ../Doc/library/configparser.rst:1299 +msgid "" +"Exception raised when attempting to parse a file which has no section " +"headers." +msgstr "" + +#: ../Doc/library/configparser.rst:1305 +msgid "Exception raised when errors occur attempting to parse a file." +msgstr "" + +#: ../Doc/library/configparser.rst:1307 +msgid "" +"The ``filename`` attribute and :meth:`__init__` argument were renamed to " +"``source`` for consistency." +msgstr "" + +#: ../Doc/library/configparser.rst:1314 +msgid "" +"Config parsers allow for heavy customization. If you are interested in " +"changing the behaviour outlined by the footnote reference, consult the " +"`Customizing Parser Behaviour`_ section." +msgstr "" + +#: ../Doc/library/constants.rst:4 +msgid "Built-in Constants" +msgstr "" + +#: ../Doc/library/constants.rst:6 +msgid "A small number of constants live in the built-in namespace. They are:" +msgstr "" + +#: ../Doc/library/constants.rst:10 +msgid "" +"The false value of the :class:`bool` type. Assignments to ``False`` are " +"illegal and raise a :exc:`SyntaxError`." +msgstr "" + +#: ../Doc/library/constants.rst:16 +msgid "" +"The true value of the :class:`bool` type. Assignments to ``True`` are " +"illegal and raise a :exc:`SyntaxError`." +msgstr "" + +#: ../Doc/library/constants.rst:22 +msgid "" +"The sole value of the type ``NoneType``. ``None`` is frequently used to " +"represent the absence of a value, as when default arguments are not passed " +"to a function. Assignments to ``None`` are illegal and raise a :exc:" +"`SyntaxError`." +msgstr "" + +#: ../Doc/library/constants.rst:29 +msgid "" +"Special value which should be returned by the binary special methods (e.g. :" +"meth:`__eq__`, :meth:`__lt__`, :meth:`__add__`, :meth:`__rsub__`, etc.) to " +"indicate that the operation is not implemented with respect to the other " +"type; may be returned by the in-place binary special methods (e.g. :meth:" +"`__imul__`, :meth:`__iand__`, etc.) for the same purpose. Its truth value is " +"true." +msgstr "" + +#: ../Doc/library/constants.rst:38 +msgid "" +"When a binary (or in-place) method returns ``NotImplemented`` the " +"interpreter will try the reflected operation on the other type (or some " +"other fallback, depending on the operator). If all attempts return " +"``NotImplemented``, the interpreter will raise an appropriate exception. " +"Incorrectly returning ``NotImplemented`` will result in a misleading error " +"message or the ``NotImplemented`` value being returned to Python code." +msgstr "" + +#: ../Doc/library/constants.rst:45 +msgid "See :ref:`implementing-the-arithmetic-operations` for examples." +msgstr "" + +#: ../Doc/library/constants.rst:49 +msgid "" +"``NotImplentedError`` and ``NotImplemented`` are not interchangeable, even " +"though they have similar names and purposes. See :exc:`NotImplementedError` " +"for details on when to use it." +msgstr "" + +#: ../Doc/library/constants.rst:56 +msgid "" +"The same as ``...``. Special value used mostly in conjunction with extended " +"slicing syntax for user-defined container data types." +msgstr "" + +#: ../Doc/library/constants.rst:62 +msgid "" +"This constant is true if Python was not started with an :option:`-O` option. " +"See also the :keyword:`assert` statement." +msgstr "" + +#: ../Doc/library/constants.rst:68 +msgid "" +"The names :data:`None`, :data:`False`, :data:`True` and :data:`__debug__` " +"cannot be reassigned (assignments to them, even as an attribute name, raise :" +"exc:`SyntaxError`), so they can be considered \"true\" constants." +msgstr "" + +#: ../Doc/library/constants.rst:74 +msgid "Constants added by the :mod:`site` module" +msgstr "" + +#: ../Doc/library/constants.rst:76 +msgid "" +"The :mod:`site` module (which is imported automatically during startup, " +"except if the :option:`-S` command-line option is given) adds several " +"constants to the built-in namespace. They are useful for the interactive " +"interpreter shell and should not be used in programs." +msgstr "" + +#: ../Doc/library/constants.rst:84 +msgid "" +"Objects that when printed, print a message like \"Use quit() or Ctrl-D (i.e. " +"EOF) to exit\", and when called, raise :exc:`SystemExit` with the specified " +"exit code." +msgstr "" + +#: ../Doc/library/constants.rst:92 +msgid "" +"Objects that when printed, print a message like \"Type license() to see the " +"full license text\", and when called, display the corresponding text in a " +"pager-like fashion (one screen at a time)." +msgstr "" + +#: ../Doc/library/contextlib.rst:2 +msgid "" +":mod:`contextlib` --- Utilities for :keyword:`with`\\ -statement contexts" +msgstr "" + +#: ../Doc/library/contextlib.rst:7 +msgid "**Source code:** :source:`Lib/contextlib.py`" +msgstr "" + +#: ../Doc/library/contextlib.rst:11 +msgid "" +"This module provides utilities for common tasks involving the :keyword:" +"`with` statement. For more information see also :ref:`typecontextmanager` " +"and :ref:`context-managers`." +msgstr "" + +#: ../Doc/library/contextlib.rst:17 +msgid "Utilities" +msgstr "" + +#: ../Doc/library/contextlib.rst:19 +msgid "Functions and classes provided:" +msgstr "" + +#: ../Doc/library/contextlib.rst:23 +msgid "" +"An :term:`abstract base class` for classes that implement :meth:`object." +"__enter__` and :meth:`object.__exit__`. A default implementation for :meth:" +"`object.__enter__` is provided which returns ``self`` while :meth:`object." +"__exit__` is an abstract method which by default returns ``None``. See also " +"the definition of :ref:`typecontextmanager`." +msgstr "" + +#: ../Doc/library/contextlib.rst:35 +msgid "" +"This function is a :term:`decorator` that can be used to define a factory " +"function for :keyword:`with` statement context managers, without needing to " +"create a class or separate :meth:`__enter__` and :meth:`__exit__` methods." +msgstr "" + +#: ../Doc/library/contextlib.rst:39 +msgid "" +"A simple example (this is not recommended as a real way of generating " +"HTML!)::" +msgstr "" + +#: ../Doc/library/contextlib.rst:56 +msgid "" +"The function being decorated must return a :term:`generator`-iterator when " +"called. This iterator must yield exactly one value, which will be bound to " +"the targets in the :keyword:`with` statement's :keyword:`as` clause, if any." +msgstr "" + +#: ../Doc/library/contextlib.rst:60 +msgid "" +"At the point where the generator yields, the block nested in the :keyword:" +"`with` statement is executed. The generator is then resumed after the block " +"is exited. If an unhandled exception occurs in the block, it is reraised " +"inside the generator at the point where the yield occurred. Thus, you can " +"use a :keyword:`try`...\\ :keyword:`except`...\\ :keyword:`finally` " +"statement to trap the error (if any), or ensure that some cleanup takes " +"place. If an exception is trapped merely in order to log it or to perform " +"some action (rather than to suppress it entirely), the generator must " +"reraise that exception. Otherwise the generator context manager will " +"indicate to the :keyword:`with` statement that the exception has been " +"handled, and execution will resume with the statement immediately following " +"the :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:72 +msgid "" +":func:`contextmanager` uses :class:`ContextDecorator` so the context " +"managers it creates can be used as decorators as well as in :keyword:`with` " +"statements. When used as a decorator, a new generator instance is implicitly " +"created on each function call (this allows the otherwise \"one-shot\" " +"context managers created by :func:`contextmanager` to meet the requirement " +"that context managers support multiple invocations in order to be used as " +"decorators)." +msgstr "" + +#: ../Doc/library/contextlib.rst:79 +msgid "Use of :class:`ContextDecorator`." +msgstr "" + +#: ../Doc/library/contextlib.rst:85 +msgid "" +"Return a context manager that closes *thing* upon completion of the block. " +"This is basically equivalent to::" +msgstr "" + +#: ../Doc/library/contextlib.rst:97 +msgid "And lets you write code like this::" +msgstr "" + +#: ../Doc/library/contextlib.rst:106 +msgid "" +"without needing to explicitly close ``page``. Even if an error occurs, " +"``page.close()`` will be called when the :keyword:`with` block is exited." +msgstr "" + +#: ../Doc/library/contextlib.rst:112 +msgid "" +"Return a context manager that suppresses any of the specified exceptions if " +"they occur in the body of a with statement and then resumes execution with " +"the first statement following the end of the with statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:116 +msgid "" +"As with any other mechanism that completely suppresses exceptions, this " +"context manager should be used only to cover very specific errors where " +"silently continuing with program execution is known to be the right thing to " +"do." +msgstr "" + +#: ../Doc/library/contextlib.rst:121 ../Doc/library/difflib.rst:505 +#: ../Doc/library/functools.rst:135 ../Doc/library/multiprocessing.rst:365 +#: ../Doc/library/optparse.rst:330 ../Doc/library/re.rst:1266 +#: ../Doc/library/stdtypes.rst:1847 ../Doc/library/stdtypes.rst:1863 +#: ../Doc/library/stdtypes.rst:1915 ../Doc/library/stdtypes.rst:1983 +#: ../Doc/library/stdtypes.rst:2047 ../Doc/library/stdtypes.rst:2785 +#: ../Doc/library/stdtypes.rst:2801 ../Doc/library/stdtypes.rst:2892 +#: ../Doc/library/stdtypes.rst:2908 ../Doc/library/stdtypes.rst:2923 +#: ../Doc/library/stdtypes.rst:2937 ../Doc/library/stdtypes.rst:2965 +#: ../Doc/library/stdtypes.rst:2979 ../Doc/library/stdtypes.rst:2997 +#: ../Doc/library/stdtypes.rst:3024 ../Doc/library/stdtypes.rst:3047 +#: ../Doc/library/stdtypes.rst:3074 ../Doc/library/stdtypes.rst:3116 +#: ../Doc/library/stdtypes.rst:3140 ../Doc/library/symtable.rst:171 +#: ../Doc/library/textwrap.rst:80 ../Doc/library/textwrap.rst:101 +#: ../Doc/library/threading.rst:844 ../Doc/library/tkinter.rst:273 +#: ../Doc/library/tkinter.rst:535 ../Doc/library/tkinter.rst:709 +#: ../Doc/library/typing.rst:142 ../Doc/library/winsound.rst:77 +msgid "For example::" +msgstr "" + +#: ../Doc/library/contextlib.rst:131 +msgid "This code is equivalent to::" +msgstr "" + +#: ../Doc/library/contextlib.rst:143 ../Doc/library/contextlib.rst:182 +#: ../Doc/library/contextlib.rst:192 +msgid "This context manager is :ref:`reentrant `." +msgstr "" + +#: ../Doc/library/contextlib.rst:150 +msgid "" +"Context manager for temporarily redirecting :data:`sys.stdout` to another " +"file or file-like object." +msgstr "" + +#: ../Doc/library/contextlib.rst:153 +msgid "" +"This tool adds flexibility to existing functions or classes whose output is " +"hardwired to stdout." +msgstr "" + +#: ../Doc/library/contextlib.rst:156 +msgid "" +"For example, the output of :func:`help` normally is sent to *sys.stdout*. " +"You can capture that output in a string by redirecting the output to an :" +"class:`io.StringIO` object::" +msgstr "" + +#: ../Doc/library/contextlib.rst:165 +msgid "" +"To send the output of :func:`help` to a file on disk, redirect the output to " +"a regular file::" +msgstr "" + +#: ../Doc/library/contextlib.rst:172 +msgid "To send the output of :func:`help` to *sys.stderr*::" +msgstr "" + +#: ../Doc/library/contextlib.rst:177 +msgid "" +"Note that the global side effect on :data:`sys.stdout` means that this " +"context manager is not suitable for use in library code and most threaded " +"applications. It also has no effect on the output of subprocesses. However, " +"it is still a useful approach for many utility scripts." +msgstr "" + +#: ../Doc/library/contextlib.rst:189 +msgid "" +"Similar to :func:`~contextlib.redirect_stdout` but redirecting :data:`sys." +"stderr` to another file or file-like object." +msgstr "" + +#: ../Doc/library/contextlib.rst:199 +msgid "" +"A base class that enables a context manager to also be used as a decorator." +msgstr "" + +#: ../Doc/library/contextlib.rst:201 +msgid "" +"Context managers inheriting from ``ContextDecorator`` have to implement " +"``__enter__`` and ``__exit__`` as normal. ``__exit__`` retains its optional " +"exception handling even when used as a decorator." +msgstr "" + +#: ../Doc/library/contextlib.rst:205 +msgid "" +"``ContextDecorator`` is used by :func:`contextmanager`, so you get this " +"functionality automatically." +msgstr "" + +#: ../Doc/library/contextlib.rst:208 +msgid "Example of ``ContextDecorator``::" +msgstr "" + +#: ../Doc/library/contextlib.rst:237 +msgid "" +"This change is just syntactic sugar for any construct of the following form::" +msgstr "" + +#: ../Doc/library/contextlib.rst:243 +msgid "``ContextDecorator`` lets you instead write::" +msgstr "" + +#: ../Doc/library/contextlib.rst:249 +msgid "" +"It makes it clear that the ``cm`` applies to the whole function, rather than " +"just a piece of it (and saving an indentation level is nice, too)." +msgstr "" + +#: ../Doc/library/contextlib.rst:252 +msgid "" +"Existing context managers that already have a base class can be extended by " +"using ``ContextDecorator`` as a mixin class::" +msgstr "" + +#: ../Doc/library/contextlib.rst:265 +msgid "" +"As the decorated function must be able to be called multiple times, the " +"underlying context manager must support use in multiple :keyword:`with` " +"statements. If this is not the case, then the original construct with the " +"explicit :keyword:`with` statement inside the function should be used." +msgstr "" + +#: ../Doc/library/contextlib.rst:275 +msgid "" +"A context manager that is designed to make it easy to programmatically " +"combine other context managers and cleanup functions, especially those that " +"are optional or otherwise driven by input data." +msgstr "" + +#: ../Doc/library/contextlib.rst:279 +msgid "" +"For example, a set of files may easily be handled in a single with statement " +"as follows::" +msgstr "" + +#: ../Doc/library/contextlib.rst:288 +msgid "" +"Each instance maintains a stack of registered callbacks that are called in " +"reverse order when the instance is closed (either explicitly or implicitly " +"at the end of a :keyword:`with` statement). Note that callbacks are *not* " +"invoked implicitly when the context stack instance is garbage collected." +msgstr "" + +#: ../Doc/library/contextlib.rst:293 +msgid "" +"This stack model is used so that context managers that acquire their " +"resources in their ``__init__`` method (such as file objects) can be handled " +"correctly." +msgstr "" + +#: ../Doc/library/contextlib.rst:297 +msgid "" +"Since registered callbacks are invoked in the reverse order of registration, " +"this ends up behaving as if multiple nested :keyword:`with` statements had " +"been used with the registered set of callbacks. This even extends to " +"exception handling - if an inner callback suppresses or replaces an " +"exception, then outer callbacks will be passed arguments based on that " +"updated state." +msgstr "" + +#: ../Doc/library/contextlib.rst:304 +msgid "" +"This is a relatively low level API that takes care of the details of " +"correctly unwinding the stack of exit callbacks. It provides a suitable " +"foundation for higher level context managers that manipulate the exit stack " +"in application specific ways." +msgstr "" + +#: ../Doc/library/contextlib.rst:313 +msgid "" +"Enters a new context manager and adds its :meth:`__exit__` method to the " +"callback stack. The return value is the result of the context manager's own :" +"meth:`__enter__` method." +msgstr "" + +#: ../Doc/library/contextlib.rst:317 +msgid "" +"These context managers may suppress exceptions just as they normally would " +"if used directly as part of a :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:322 +msgid "Adds a context manager's :meth:`__exit__` method to the callback stack." +msgstr "" + +#: ../Doc/library/contextlib.rst:324 +msgid "" +"As ``__enter__`` is *not* invoked, this method can be used to cover part of " +"an :meth:`__enter__` implementation with a context manager's own :meth:" +"`__exit__` method." +msgstr "" + +#: ../Doc/library/contextlib.rst:328 +msgid "" +"If passed an object that is not a context manager, this method assumes it is " +"a callback with the same signature as a context manager's :meth:`__exit__` " +"method and adds it directly to the callback stack." +msgstr "" + +#: ../Doc/library/contextlib.rst:332 +msgid "" +"By returning true values, these callbacks can suppress exceptions the same " +"way context manager :meth:`__exit__` methods can." +msgstr "" + +#: ../Doc/library/contextlib.rst:335 +msgid "" +"The passed in object is returned from the function, allowing this method to " +"be used as a function decorator." +msgstr "" + +#: ../Doc/library/contextlib.rst:340 +msgid "" +"Accepts an arbitrary callback function and arguments and adds it to the " +"callback stack." +msgstr "" + +#: ../Doc/library/contextlib.rst:343 +msgid "" +"Unlike the other methods, callbacks added this way cannot suppress " +"exceptions (as they are never passed the exception details)." +msgstr "" + +#: ../Doc/library/contextlib.rst:346 +msgid "" +"The passed in callback is returned from the function, allowing this method " +"to be used as a function decorator." +msgstr "" + +#: ../Doc/library/contextlib.rst:351 +msgid "" +"Transfers the callback stack to a fresh :class:`ExitStack` instance and " +"returns it. No callbacks are invoked by this operation - instead, they will " +"now be invoked when the new stack is closed (either explicitly or implicitly " +"at the end of a :keyword:`with` statement)." +msgstr "" + +#: ../Doc/library/contextlib.rst:356 +msgid "" +"For example, a group of files can be opened as an \"all or nothing\" " +"operation as follows::" +msgstr "" + +#: ../Doc/library/contextlib.rst:370 +msgid "" +"Immediately unwinds the callback stack, invoking callbacks in the reverse " +"order of registration. For any context managers and exit callbacks " +"registered, the arguments passed in will indicate that no exception occurred." +msgstr "" + +#: ../Doc/library/contextlib.rst:377 ../Doc/library/random.rst:323 +msgid "Examples and Recipes" +msgstr "" + +#: ../Doc/library/contextlib.rst:379 +msgid "" +"This section describes some examples and recipes for making effective use of " +"the tools provided by :mod:`contextlib`." +msgstr "" + +#: ../Doc/library/contextlib.rst:384 +msgid "Supporting a variable number of context managers" +msgstr "" + +#: ../Doc/library/contextlib.rst:386 +msgid "" +"The primary use case for :class:`ExitStack` is the one given in the class " +"documentation: supporting a variable number of context managers and other " +"cleanup operations in a single :keyword:`with` statement. The variability " +"may come from the number of context managers needed being driven by user " +"input (such as opening a user specified collection of files), or from some " +"of the context managers being optional::" +msgstr "" + +#: ../Doc/library/contextlib.rst:401 +msgid "" +"As shown, :class:`ExitStack` also makes it quite easy to use :keyword:`with` " +"statements to manage arbitrary resources that don't natively support the " +"context management protocol." +msgstr "" + +#: ../Doc/library/contextlib.rst:407 +msgid "Simplifying support for single optional context managers" +msgstr "" + +#: ../Doc/library/contextlib.rst:409 +msgid "" +"In the specific case of a single optional context manager, :class:" +"`ExitStack` instances can be used as a \"do nothing\" context manager, " +"allowing a context manager to easily be omitted without affecting the " +"overall structure of the source code::" +msgstr "" + +#: ../Doc/library/contextlib.rst:425 +msgid "Catching exceptions from ``__enter__`` methods" +msgstr "" + +#: ../Doc/library/contextlib.rst:427 +msgid "" +"It is occasionally desirable to catch exceptions from an ``__enter__`` " +"method implementation, *without* inadvertently catching exceptions from the :" +"keyword:`with` statement body or the context manager's ``__exit__`` method. " +"By using :class:`ExitStack` the steps in the context management protocol can " +"be separated slightly in order to allow this::" +msgstr "" + +#: ../Doc/library/contextlib.rst:442 +msgid "" +"Actually needing to do this is likely to indicate that the underlying API " +"should be providing a direct resource management interface for use with :" +"keyword:`try`/:keyword:`except`/:keyword:`finally` statements, but not all " +"APIs are well designed in that regard. When a context manager is the only " +"resource management API provided, then :class:`ExitStack` can make it easier " +"to handle various situations that can't be handled directly in a :keyword:" +"`with` statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:452 +msgid "Cleaning up in an ``__enter__`` implementation" +msgstr "" + +#: ../Doc/library/contextlib.rst:454 +msgid "" +"As noted in the documentation of :meth:`ExitStack.push`, this method can be " +"useful in cleaning up an already allocated resource if later steps in the :" +"meth:`__enter__` implementation fail." +msgstr "" + +#: ../Doc/library/contextlib.rst:458 +msgid "" +"Here's an example of doing this for a context manager that accepts resource " +"acquisition and release functions, along with an optional validation " +"function, and maps them to the context management protocol::" +msgstr "" + +#: ../Doc/library/contextlib.rst:498 +msgid "Replacing any use of ``try-finally`` and flag variables" +msgstr "" + +#: ../Doc/library/contextlib.rst:500 +msgid "" +"A pattern you will sometimes see is a ``try-finally`` statement with a flag " +"variable to indicate whether or not the body of the ``finally`` clause " +"should be executed. In its simplest form (that can't already be handled just " +"by using an ``except`` clause instead), it looks something like this::" +msgstr "" + +#: ../Doc/library/contextlib.rst:514 +msgid "" +"As with any ``try`` statement based code, this can cause problems for " +"development and review, because the setup code and the cleanup code can end " +"up being separated by arbitrarily long sections of code." +msgstr "" + +#: ../Doc/library/contextlib.rst:518 +msgid "" +":class:`ExitStack` makes it possible to instead register a callback for " +"execution at the end of a ``with`` statement, and then later decide to skip " +"executing that callback::" +msgstr "" + +#: ../Doc/library/contextlib.rst:530 +msgid "" +"This allows the intended cleanup up behaviour to be made explicit up front, " +"rather than requiring a separate flag variable." +msgstr "" + +#: ../Doc/library/contextlib.rst:533 +msgid "" +"If a particular application uses this pattern a lot, it can be simplified " +"even further by means of a small helper class::" +msgstr "" + +#: ../Doc/library/contextlib.rst:551 +msgid "" +"If the resource cleanup isn't already neatly bundled into a standalone " +"function, then it is still possible to use the decorator form of :meth:" +"`ExitStack.callback` to declare the resource cleanup in advance::" +msgstr "" + +#: ../Doc/library/contextlib.rst:566 +msgid "" +"Due to the way the decorator protocol works, a callback function declared " +"this way cannot take any parameters. Instead, any resources to be released " +"must be accessed as closure variables." +msgstr "" + +#: ../Doc/library/contextlib.rst:572 +msgid "Using a context manager as a function decorator" +msgstr "" + +#: ../Doc/library/contextlib.rst:574 +msgid "" +":class:`ContextDecorator` makes it possible to use a context manager in both " +"an ordinary ``with`` statement and also as a function decorator." +msgstr "" + +#: ../Doc/library/contextlib.rst:577 +msgid "" +"For example, it is sometimes useful to wrap functions or groups of " +"statements with a logger that can track the time of entry and time of exit. " +"Rather than writing both a function decorator and a context manager for the " +"task, inheriting from :class:`ContextDecorator` provides both capabilities " +"in a single definition::" +msgstr "" + +#: ../Doc/library/contextlib.rst:598 +msgid "Instances of this class can be used as both a context manager::" +msgstr "" + +#: ../Doc/library/contextlib.rst:604 +msgid "And also as a function decorator::" +msgstr "" + +#: ../Doc/library/contextlib.rst:611 +msgid "" +"Note that there is one additional limitation when using context managers as " +"function decorators: there's no way to access the return value of :meth:" +"`__enter__`. If that value is needed, then it is still necessary to use an " +"explicit ``with`` statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:619 +msgid ":pep:`343` - The \"with\" statement" +msgstr "" + +#: ../Doc/library/contextlib.rst:619 +msgid "" +"The specification, background, and examples for the Python :keyword:`with` " +"statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:625 +msgid "Single use, reusable and reentrant context managers" +msgstr "" + +#: ../Doc/library/contextlib.rst:627 +msgid "" +"Most context managers are written in a way that means they can only be used " +"effectively in a :keyword:`with` statement once. These single use context " +"managers must be created afresh each time they're used - attempting to use " +"them a second time will trigger an exception or otherwise not work correctly." +msgstr "" + +#: ../Doc/library/contextlib.rst:633 +msgid "" +"This common limitation means that it is generally advisable to create " +"context managers directly in the header of the :keyword:`with` statement " +"where they are used (as shown in all of the usage examples above)." +msgstr "" + +#: ../Doc/library/contextlib.rst:637 +msgid "" +"Files are an example of effectively single use context managers, since the " +"first :keyword:`with` statement will close the file, preventing any further " +"IO operations using that file object." +msgstr "" + +#: ../Doc/library/contextlib.rst:641 +msgid "" +"Context managers created using :func:`contextmanager` are also single use " +"context managers, and will complain about the underlying generator failing " +"to yield if an attempt is made to use them a second time::" +msgstr "" + +#: ../Doc/library/contextlib.rst:669 +msgid "Reentrant context managers" +msgstr "" + +#: ../Doc/library/contextlib.rst:671 +msgid "" +"More sophisticated context managers may be \"reentrant\". These context " +"managers can not only be used in multiple :keyword:`with` statements, but " +"may also be used *inside* a :keyword:`with` statement that is already using " +"the same context manager." +msgstr "" + +#: ../Doc/library/contextlib.rst:676 +msgid "" +":class:`threading.RLock` is an example of a reentrant context manager, as " +"are :func:`suppress` and :func:`redirect_stdout`. Here's a very simple " +"example of reentrant use::" +msgstr "" + +#: ../Doc/library/contextlib.rst:695 +msgid "" +"Real world examples of reentrancy are more likely to involve multiple " +"functions calling each other and hence be far more complicated than this " +"example." +msgstr "" + +#: ../Doc/library/contextlib.rst:699 +msgid "" +"Note also that being reentrant is *not* the same thing as being thread " +"safe. :func:`redirect_stdout`, for example, is definitely not thread safe, " +"as it makes a global modification to the system state by binding :data:`sys." +"stdout` to a different stream." +msgstr "" + +#: ../Doc/library/contextlib.rst:708 +msgid "Reusable context managers" +msgstr "" + +#: ../Doc/library/contextlib.rst:710 +msgid "" +"Distinct from both single use and reentrant context managers are \"reusable" +"\" context managers (or, to be completely explicit, \"reusable, but not " +"reentrant\" context managers, since reentrant context managers are also " +"reusable). These context managers support being used multiple times, but " +"will fail (or otherwise not work correctly) if the specific context manager " +"instance has already been used in a containing with statement." +msgstr "" + +#: ../Doc/library/contextlib.rst:717 +msgid "" +":class:`threading.Lock` is an example of a reusable, but not reentrant, " +"context manager (for a reentrant lock, it is necessary to use :class:" +"`threading.RLock` instead)." +msgstr "" + +#: ../Doc/library/contextlib.rst:721 +msgid "" +"Another example of a reusable, but not reentrant, context manager is :class:" +"`ExitStack`, as it invokes *all* currently registered callbacks when leaving " +"any with statement, regardless of where those callbacks were added::" +msgstr "" + +#: ../Doc/library/contextlib.rst:752 +msgid "" +"As the output from the example shows, reusing a single stack object across " +"multiple with statements works correctly, but attempting to nest them will " +"cause the stack to be cleared at the end of the innermost with statement, " +"which is unlikely to be desirable behaviour." +msgstr "" + +#: ../Doc/library/contextlib.rst:757 +msgid "" +"Using separate :class:`ExitStack` instances instead of reusing a single " +"instance avoids that problem::" +msgstr "" + +#: ../Doc/library/copy.rst:2 +msgid ":mod:`copy` --- Shallow and deep copy operations" +msgstr "" + +#: ../Doc/library/copy.rst:7 +msgid "**Source code:** :source:`Lib/copy.py`" +msgstr "" + +#: ../Doc/library/copy.rst:11 +msgid "" +"Assignment statements in Python do not copy objects, they create bindings " +"between a target and an object. For collections that are mutable or contain " +"mutable items, a copy is sometimes needed so one can change one copy without " +"changing the other. This module provides generic shallow and deep copy " +"operations (explained below)." +msgstr "" + +#: ../Doc/library/copy.rst:18 +msgid "Interface summary:" +msgstr "" + +#: ../Doc/library/copy.rst:22 +msgid "Return a shallow copy of *x*." +msgstr "" + +#: ../Doc/library/copy.rst:27 +msgid "Return a deep copy of *x*." +msgstr "" + +#: ../Doc/library/copy.rst:32 +msgid "Raised for module specific errors." +msgstr "" + +#: ../Doc/library/copy.rst:35 +msgid "" +"The difference between shallow and deep copying is only relevant for " +"compound objects (objects that contain other objects, like lists or class " +"instances):" +msgstr "" + +#: ../Doc/library/copy.rst:38 +msgid "" +"A *shallow copy* constructs a new compound object and then (to the extent " +"possible) inserts *references* into it to the objects found in the original." +msgstr "" + +#: ../Doc/library/copy.rst:41 +msgid "" +"A *deep copy* constructs a new compound object and then, recursively, " +"inserts *copies* into it of the objects found in the original." +msgstr "" + +#: ../Doc/library/copy.rst:44 +msgid "" +"Two problems often exist with deep copy operations that don't exist with " +"shallow copy operations:" +msgstr "" + +#: ../Doc/library/copy.rst:47 +msgid "" +"Recursive objects (compound objects that, directly or indirectly, contain a " +"reference to themselves) may cause a recursive loop." +msgstr "" + +#: ../Doc/library/copy.rst:50 +msgid "" +"Because deep copy copies *everything* it may copy too much, e.g., even " +"administrative data structures that should be shared even between copies." +msgstr "" + +#: ../Doc/library/copy.rst:53 +msgid "The :func:`deepcopy` function avoids these problems by:" +msgstr "" + +#: ../Doc/library/copy.rst:55 +msgid "" +"keeping a \"memo\" dictionary of objects already copied during the current " +"copying pass; and" +msgstr "" + +#: ../Doc/library/copy.rst:58 +msgid "" +"letting user-defined classes override the copying operation or the set of " +"components copied." +msgstr "" + +#: ../Doc/library/copy.rst:61 +msgid "" +"This module does not copy types like module, method, stack trace, stack " +"frame, file, socket, window, array, or any similar types. It does \"copy\" " +"functions and classes (shallow and deeply), by returning the original object " +"unchanged; this is compatible with the way these are treated by the :mod:" +"`pickle` module." +msgstr "" + +#: ../Doc/library/copy.rst:66 +msgid "" +"Shallow copies of dictionaries can be made using :meth:`dict.copy`, and of " +"lists by assigning a slice of the entire list, for example, ``copied_list = " +"original_list[:]``." +msgstr "" + +#: ../Doc/library/copy.rst:72 +msgid "" +"Classes can use the same interfaces to control copying that they use to " +"control pickling. See the description of module :mod:`pickle` for " +"information on these methods. In fact, the :mod:`copy` module uses the " +"registered pickle functions from the :mod:`copyreg` module." +msgstr "" + +#: ../Doc/library/copy.rst:81 +msgid "" +"In order for a class to define its own copy implementation, it can define " +"special methods :meth:`__copy__` and :meth:`__deepcopy__`. The former is " +"called to implement the shallow copy operation; no additional arguments are " +"passed. The latter is called to implement the deep copy operation; it is " +"passed one argument, the memo dictionary. If the :meth:`__deepcopy__` " +"implementation needs to make a deep copy of a component, it should call the :" +"func:`deepcopy` function with the component as first argument and the memo " +"dictionary as second argument." +msgstr "" + +#: ../Doc/library/copy.rst:93 ../Doc/library/shelve.rst:201 +msgid "Module :mod:`pickle`" +msgstr "" + +#: ../Doc/library/copy.rst:93 +msgid "" +"Discussion of the special methods used to support object state retrieval and " +"restoration." +msgstr "" + +#: ../Doc/library/copyreg.rst:2 +msgid ":mod:`copyreg` --- Register :mod:`pickle` support functions" +msgstr "" + +#: ../Doc/library/copyreg.rst:7 +msgid "**Source code:** :source:`Lib/copyreg.py`" +msgstr "" + +#: ../Doc/library/copyreg.rst:15 +msgid "" +"The :mod:`copyreg` module offers a way to define functions used while " +"pickling specific objects. The :mod:`pickle` and :mod:`copy` modules use " +"those functions when pickling/copying those objects. The module provides " +"configuration information about object constructors which are not classes. " +"Such constructors may be factory functions or class instances." +msgstr "" + +#: ../Doc/library/copyreg.rst:24 +msgid "" +"Declares *object* to be a valid constructor. If *object* is not callable " +"(and hence not valid as a constructor), raises :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/copyreg.rst:30 +msgid "" +"Declares that *function* should be used as a \"reduction\" function for " +"objects of type *type*. *function* should return either a string or a tuple " +"containing two or three elements." +msgstr "" + +#: ../Doc/library/copyreg.rst:34 +msgid "" +"The optional *constructor* parameter, if provided, is a callable object " +"which can be used to reconstruct the object when called with the tuple of " +"arguments returned by *function* at pickling time. :exc:`TypeError` will be " +"raised if *object* is a class or *constructor* is not callable." +msgstr "" + +#: ../Doc/library/copyreg.rst:39 +msgid "" +"See the :mod:`pickle` module for more details on the interface expected of " +"*function* and *constructor*. Note that the :attr:`~pickle.Pickler." +"dispatch_table` attribute of a pickler object or subclass of :class:`pickle." +"Pickler` can also be used for declaring reduction functions." +msgstr "" + +#: ../Doc/library/copyreg.rst:48 +msgid "" +"The example below would like to show how to register a pickle function and " +"how it will be used:" +msgstr "" + +#: ../Doc/library/crypt.rst:2 +msgid ":mod:`crypt` --- Function to check Unix passwords" +msgstr "" + +#: ../Doc/library/crypt.rst:12 +msgid "**Source code:** :source:`Lib/crypt.py`" +msgstr "" + +#: ../Doc/library/crypt.rst:20 +msgid "" +"This module implements an interface to the :manpage:`crypt(3)` routine, " +"which is a one-way hash function based upon a modified DES algorithm; see " +"the Unix man page for further details. Possible uses include storing hashed " +"passwords so you can check passwords without storing the actual password, or " +"attempting to crack Unix passwords with a dictionary." +msgstr "" + +#: ../Doc/library/crypt.rst:28 +msgid "" +"Notice that the behavior of this module depends on the actual " +"implementation of the :manpage:`crypt(3)` routine in the running system. " +"Therefore, any extensions available on the current implementation will also " +"be available on this module." +msgstr "" + +#: ../Doc/library/crypt.rst:34 +msgid "Hashing Methods" +msgstr "" + +#: ../Doc/library/crypt.rst:38 +msgid "" +"The :mod:`crypt` module defines the list of hashing methods (not all methods " +"are available on all platforms):" +msgstr "" + +#: ../Doc/library/crypt.rst:43 +msgid "" +"A Modular Crypt Format method with 16 character salt and 86 character hash. " +"This is the strongest method." +msgstr "" + +#: ../Doc/library/crypt.rst:48 +msgid "" +"Another Modular Crypt Format method with 16 character salt and 43 character " +"hash." +msgstr "" + +#: ../Doc/library/crypt.rst:53 +msgid "" +"Another Modular Crypt Format method with 8 character salt and 22 character " +"hash." +msgstr "" + +#: ../Doc/library/crypt.rst:58 +msgid "" +"The traditional method with a 2 character salt and 13 characters of hash. " +"This is the weakest method." +msgstr "" + +#: ../Doc/library/crypt.rst:63 +msgid "Module Attributes" +msgstr "" + +#: ../Doc/library/crypt.rst:69 +msgid "" +"A list of available password hashing algorithms, as ``crypt.METHOD_*`` " +"objects. This list is sorted from strongest to weakest." +msgstr "" + +#: ../Doc/library/crypt.rst:77 +msgid "The :mod:`crypt` module defines the following functions:" +msgstr "" + +#: ../Doc/library/crypt.rst:81 +msgid "" +"*word* will usually be a user's password as typed at a prompt or in a " +"graphical interface. The optional *salt* is either a string as returned " +"from :func:`mksalt`, one of the ``crypt.METHOD_*`` values (though not all " +"may be available on all platforms), or a full encrypted password including " +"salt, as returned by this function. If *salt* is not provided, the " +"strongest method will be used (as returned by :func:`methods`." +msgstr "" + +#: ../Doc/library/crypt.rst:89 +msgid "" +"Checking a password is usually done by passing the plain-text password as " +"*word* and the full results of a previous :func:`crypt` call, which should " +"be the same as the results of this call." +msgstr "" + +#: ../Doc/library/crypt.rst:93 +msgid "" +"*salt* (either a random 2 or 16 character string, possibly prefixed with ``" +"$digit$`` to indicate the method) which will be used to perturb the " +"encryption algorithm. The characters in *salt* must be in the set ``[./a-zA-" +"Z0-9]``, with the exception of Modular Crypt Format which prefixes a ``$digit" +"$``." +msgstr "" + +#: ../Doc/library/crypt.rst:99 +msgid "" +"Returns the hashed password as a string, which will be composed of " +"characters from the same alphabet as the salt." +msgstr "" + +#: ../Doc/library/crypt.rst:104 +msgid "" +"Since a few :manpage:`crypt(3)` extensions allow different values, with " +"different sizes in the *salt*, it is recommended to use the full crypted " +"password as salt when checking for a password." +msgstr "" + +#: ../Doc/library/crypt.rst:108 +msgid "Accept ``crypt.METHOD_*`` values in addition to strings for *salt*." +msgstr "" + +#: ../Doc/library/crypt.rst:114 +msgid "" +"Return a randomly generated salt of the specified method. If no *method* is " +"given, the strongest method available as returned by :func:`methods` is used." +msgstr "" + +#: ../Doc/library/crypt.rst:118 +msgid "" +"The return value is a string either of 2 characters in length for ``crypt." +"METHOD_CRYPT``, or 19 characters starting with ``$digit$`` and 16 random " +"characters from the set ``[./a-zA-Z0-9]``, suitable for passing as the " +"*salt* argument to :func:`crypt`." +msgstr "" + +#: ../Doc/library/crypt.rst:126 ../Doc/library/csv.rst:475 +#: ../Doc/library/hashlib-blake2.rst:141 ../Doc/library/html.parser.rst:230 +#: ../Doc/library/http.client.rst:467 ../Doc/library/http.cookiejar.rst:729 +#: ../Doc/library/imp.rst:385 ../Doc/library/importlib.rst:1354 +#: ../Doc/library/lzma.rst:385 ../Doc/library/mailbox.rst:1529 +#: ../Doc/library/multiprocessing.rst:2820 ../Doc/library/pickle.rst:863 +#: ../Doc/library/plistlib.rst:218 ../Doc/library/selectors.rst:242 +#: ../Doc/library/socketserver.rst:423 ../Doc/library/ssl.rst:1812 +#: ../Doc/library/struct.rst:330 ../Doc/library/syslog.rst:94 +#: ../Doc/library/tarfile.rst:720 ../Doc/library/tempfile.rst:263 +#: ../Doc/library/timeit.rst:272 ../Doc/library/tokenize.rst:184 +#: ../Doc/library/tracemalloc.rst:34 ../Doc/library/urllib.request.rst:1150 +#: ../Doc/library/wsgiref.rst:757 ../Doc/library/zipapp.rst:166 +#: ../Doc/library/zipimport.rst:147 +msgid "Examples" +msgstr "" + +#: ../Doc/library/crypt.rst:128 +msgid "" +"A simple example illustrating typical use (a constant-time comparison " +"operation is needed to limit exposure to timing attacks. :func:`hmac." +"compare_digest` is suitable for this purpose)::" +msgstr "" + +#: ../Doc/library/crypt.rst:148 +msgid "" +"To generate a hash of a password using the strongest available method and " +"check it against the original::" +msgstr "" + +#: ../Doc/library/crypto.rst:5 +msgid "Cryptographic Services" +msgstr "" + +#: ../Doc/library/crypto.rst:9 +msgid "" +"The modules described in this chapter implement various algorithms of a " +"cryptographic nature. They are available at the discretion of the " +"installation. On Unix systems, the :mod:`crypt` module may also be " +"available. Here's an overview:" +msgstr "" + +#: ../Doc/library/csv.rst:2 +msgid ":mod:`csv` --- CSV File Reading and Writing" +msgstr "" + +#: ../Doc/library/csv.rst:9 +msgid "**Source code:** :source:`Lib/csv.py`" +msgstr "" + +#: ../Doc/library/csv.rst:17 +msgid "" +"The so-called CSV (Comma Separated Values) format is the most common import " +"and export format for spreadsheets and databases. CSV format was used for " +"many years prior to attempts to describe the format in a standardized way " +"in :rfc:`4180`. The lack of a well-defined standard means that subtle " +"differences often exist in the data produced and consumed by different " +"applications. These differences can make it annoying to process CSV files " +"from multiple sources. Still, while the delimiters and quoting characters " +"vary, the overall format is similar enough that it is possible to write a " +"single module which can efficiently manipulate such data, hiding the details " +"of reading and writing the data from the programmer." +msgstr "" + +#: ../Doc/library/csv.rst:28 +msgid "" +"The :mod:`csv` module implements classes to read and write tabular data in " +"CSV format. It allows programmers to say, \"write this data in the format " +"preferred by Excel,\" or \"read data from this file which was generated by " +"Excel,\" without knowing the precise details of the CSV format used by " +"Excel. Programmers can also describe the CSV formats understood by other " +"applications or define their own special-purpose CSV formats." +msgstr "" + +#: ../Doc/library/csv.rst:35 +msgid "" +"The :mod:`csv` module's :class:`reader` and :class:`writer` objects read and " +"write sequences. Programmers can also read and write data in dictionary " +"form using the :class:`DictReader` and :class:`DictWriter` classes." +msgstr "" + +#: ../Doc/library/csv.rst:41 +msgid ":pep:`305` - CSV File API" +msgstr "" + +#: ../Doc/library/csv.rst:42 +msgid "The Python Enhancement Proposal which proposed this addition to Python." +msgstr "" + +#: ../Doc/library/csv.rst:48 ../Doc/library/enum.rst:24 +#: ../Doc/library/re.rst:474 ../Doc/library/xml.dom.rst:81 +msgid "Module Contents" +msgstr "" + +#: ../Doc/library/csv.rst:50 +msgid "The :mod:`csv` module defines the following functions:" +msgstr "" + +#: ../Doc/library/csv.rst:58 +msgid "" +"Return a reader object which will iterate over lines in the given *csvfile*. " +"*csvfile* can be any object which supports the :term:`iterator` protocol and " +"returns a string each time its :meth:`!__next__` method is called --- :term:" +"`file objects ` and list objects are both suitable. If " +"*csvfile* is a file object, it should be opened with ``newline=''``. [1]_ " +"An optional *dialect* parameter can be given which is used to define a set " +"of parameters specific to a particular CSV dialect. It may be an instance " +"of a subclass of the :class:`Dialect` class or one of the strings returned " +"by the :func:`list_dialects` function. The other optional *fmtparams* " +"keyword arguments can be given to override individual formatting parameters " +"in the current dialect. For full details about the dialect and formatting " +"parameters, see section :ref:`csv-fmt-params`." +msgstr "" + +#: ../Doc/library/csv.rst:71 +msgid "" +"Each row read from the csv file is returned as a list of strings. No " +"automatic data type conversion is performed unless the ``QUOTE_NONNUMERIC`` " +"format option is specified (in which case unquoted fields are transformed " +"into floats)." +msgstr "" + +#: ../Doc/library/csv.rst:75 ../Doc/library/csv.rst:105 +#: ../Doc/library/csv.rst:172 ../Doc/library/csv.rst:208 +msgid "A short usage example::" +msgstr "" + +#: ../Doc/library/csv.rst:88 +msgid "" +"Return a writer object responsible for converting the user's data into " +"delimited strings on the given file-like object. *csvfile* can be any " +"object with a :func:`write` method. If *csvfile* is a file object, it " +"should be opened with ``newline=''`` [1]_. An optional *dialect* parameter " +"can be given which is used to define a set of parameters specific to a " +"particular CSV dialect. It may be an instance of a subclass of the :class:" +"`Dialect` class or one of the strings returned by the :func:`list_dialects` " +"function. The other optional *fmtparams* keyword arguments can be given to " +"override individual formatting parameters in the current dialect. For full " +"details about the dialect and formatting parameters, see section :ref:`csv-" +"fmt-params`. To make it as easy as possible to interface with modules which " +"implement the DB API, the value :const:`None` is written as the empty " +"string. While this isn't a reversible transformation, it makes it easier to " +"dump SQL NULL data values to CSV files without preprocessing the data " +"returned from a ``cursor.fetch*`` call. All other non-string data are " +"stringified with :func:`str` before being written." +msgstr "" + +#: ../Doc/library/csv.rst:117 +msgid "" +"Associate *dialect* with *name*. *name* must be a string. The dialect can " +"be specified either by passing a sub-class of :class:`Dialect`, or by " +"*fmtparams* keyword arguments, or both, with keyword arguments overriding " +"parameters of the dialect. For full details about the dialect and formatting " +"parameters, see section :ref:`csv-fmt-params`." +msgstr "" + +#: ../Doc/library/csv.rst:126 +msgid "" +"Delete the dialect associated with *name* from the dialect registry. An :" +"exc:`Error` is raised if *name* is not a registered dialect name." +msgstr "" + +#: ../Doc/library/csv.rst:132 +msgid "" +"Return the dialect associated with *name*. An :exc:`Error` is raised if " +"*name* is not a registered dialect name. This function returns an " +"immutable :class:`Dialect`." +msgstr "" + +#: ../Doc/library/csv.rst:138 +msgid "Return the names of all registered dialects." +msgstr "" + +#: ../Doc/library/csv.rst:143 +msgid "" +"Returns the current maximum field size allowed by the parser. If *new_limit* " +"is given, this becomes the new limit." +msgstr "" + +#: ../Doc/library/csv.rst:147 +msgid "The :mod:`csv` module defines the following classes:" +msgstr "" + +#: ../Doc/library/csv.rst:152 +msgid "" +"Create an object that operates like a regular reader but maps the " +"information in each row to an :mod:`OrderedDict ` " +"whose keys are given by the optional *fieldnames* parameter." +msgstr "" + +#: ../Doc/library/csv.rst:156 +msgid "" +"The *fieldnames* parameter is a :term:`sequence`. If *fieldnames* is " +"omitted, the values in the first row of the *csvfile* will be used as the " +"fieldnames. Regardless of how the fieldnames are determined, the ordered " +"dictionary preserves their original ordering." +msgstr "" + +#: ../Doc/library/csv.rst:161 +msgid "" +"If a row has more fields than fieldnames, the remaining data is put in a " +"list and stored with the fieldname specified by *restkey* (which defaults to " +"``None``). If a non-blank row has fewer fields than fieldnames, the missing " +"values are filled-in with ``None``." +msgstr "" + +#: ../Doc/library/csv.rst:166 +msgid "" +"All other optional or keyword arguments are passed to the underlying :class:" +"`reader` instance." +msgstr "" + +#: ../Doc/library/csv.rst:169 +msgid "Returned rows are now of type :class:`OrderedDict`." +msgstr "" + +#: ../Doc/library/csv.rst:190 +msgid "" +"Create an object which operates like a regular writer but maps dictionaries " +"onto output rows. The *fieldnames* parameter is a :mod:`sequence " +"` of keys that identify the order in which values in the " +"dictionary passed to the :meth:`writerow` method are written to the " +"*csvfile*. The optional *restval* parameter specifies the value to be " +"written if the dictionary is missing a key in *fieldnames*. If the " +"dictionary passed to the :meth:`writerow` method contains a key not found in " +"*fieldnames*, the optional *extrasaction* parameter indicates what action to " +"take. If it is set to ``'raise'`` a :exc:`ValueError` is raised. If it is " +"set to ``'ignore'``, extra values in the dictionary are ignored. Any other " +"optional or keyword arguments are passed to the underlying :class:`writer` " +"instance." +msgstr "" + +#: ../Doc/library/csv.rst:203 +msgid "" +"Note that unlike the :class:`DictReader` class, the *fieldnames* parameter " +"of the :class:`DictWriter` is not optional. Since Python's :class:`dict` " +"objects are not ordered, there is not enough information available to deduce " +"the order in which the row should be written to the *csvfile*." +msgstr "" + +#: ../Doc/library/csv.rst:224 +msgid "" +"The :class:`Dialect` class is a container class relied on primarily for its " +"attributes, which are used to define the parameters for a specific :class:" +"`reader` or :class:`writer` instance." +msgstr "" + +#: ../Doc/library/csv.rst:231 +msgid "" +"The :class:`excel` class defines the usual properties of an Excel-generated " +"CSV file. It is registered with the dialect name ``'excel'``." +msgstr "" + +#: ../Doc/library/csv.rst:237 +msgid "" +"The :class:`excel_tab` class defines the usual properties of an Excel-" +"generated TAB-delimited file. It is registered with the dialect name " +"``'excel-tab'``." +msgstr "" + +#: ../Doc/library/csv.rst:243 +msgid "" +"The :class:`unix_dialect` class defines the usual properties of a CSV file " +"generated on UNIX systems, i.e. using ``'\\n'`` as line terminator and " +"quoting all fields. It is registered with the dialect name ``'unix'``." +msgstr "" + +#: ../Doc/library/csv.rst:252 +msgid "The :class:`Sniffer` class is used to deduce the format of a CSV file." +msgstr "" + +#: ../Doc/library/csv.rst:254 +msgid "The :class:`Sniffer` class provides two methods:" +msgstr "" + +#: ../Doc/library/csv.rst:258 +msgid "" +"Analyze the given *sample* and return a :class:`Dialect` subclass reflecting " +"the parameters found. If the optional *delimiters* parameter is given, it " +"is interpreted as a string containing possible valid delimiter characters." +msgstr "" + +#: ../Doc/library/csv.rst:266 +msgid "" +"Analyze the sample text (presumed to be in CSV format) and return :const:" +"`True` if the first row appears to be a series of column headers." +msgstr "" + +#: ../Doc/library/csv.rst:269 +msgid "An example for :class:`Sniffer` use::" +msgstr "" + +#: ../Doc/library/csv.rst:278 +msgid "The :mod:`csv` module defines the following constants:" +msgstr "" + +#: ../Doc/library/csv.rst:282 +msgid "Instructs :class:`writer` objects to quote all fields." +msgstr "" + +#: ../Doc/library/csv.rst:287 +msgid "" +"Instructs :class:`writer` objects to only quote those fields which contain " +"special characters such as *delimiter*, *quotechar* or any of the characters " +"in *lineterminator*." +msgstr "" + +#: ../Doc/library/csv.rst:294 +msgid "Instructs :class:`writer` objects to quote all non-numeric fields." +msgstr "" + +#: ../Doc/library/csv.rst:296 +msgid "Instructs the reader to convert all non-quoted fields to type *float*." +msgstr "" + +#: ../Doc/library/csv.rst:301 +msgid "" +"Instructs :class:`writer` objects to never quote fields. When the current " +"*delimiter* occurs in output data it is preceded by the current *escapechar* " +"character. If *escapechar* is not set, the writer will raise :exc:`Error` " +"if any characters that require escaping are encountered." +msgstr "" + +#: ../Doc/library/csv.rst:306 +msgid "" +"Instructs :class:`reader` to perform no special processing of quote " +"characters." +msgstr "" + +#: ../Doc/library/csv.rst:308 +msgid "The :mod:`csv` module defines the following exception:" +msgstr "" + +#: ../Doc/library/csv.rst:313 +msgid "Raised by any of the functions when an error is detected." +msgstr "" + +#: ../Doc/library/csv.rst:318 +msgid "Dialects and Formatting Parameters" +msgstr "" + +#: ../Doc/library/csv.rst:320 +msgid "" +"To make it easier to specify the format of input and output records, " +"specific formatting parameters are grouped together into dialects. A " +"dialect is a subclass of the :class:`Dialect` class having a set of specific " +"methods and a single :meth:`validate` method. When creating :class:`reader` " +"or :class:`writer` objects, the programmer can specify a string or a " +"subclass of the :class:`Dialect` class as the dialect parameter. In " +"addition to, or instead of, the *dialect* parameter, the programmer can also " +"specify individual formatting parameters, which have the same names as the " +"attributes defined below for the :class:`Dialect` class." +msgstr "" + +#: ../Doc/library/csv.rst:330 +msgid "Dialects support the following attributes:" +msgstr "" + +#: ../Doc/library/csv.rst:335 +msgid "" +"A one-character string used to separate fields. It defaults to ``','``." +msgstr "" + +#: ../Doc/library/csv.rst:340 +msgid "" +"Controls how instances of *quotechar* appearing inside a field should " +"themselves be quoted. When :const:`True`, the character is doubled. When :" +"const:`False`, the *escapechar* is used as a prefix to the *quotechar*. It " +"defaults to :const:`True`." +msgstr "" + +#: ../Doc/library/csv.rst:345 +msgid "" +"On output, if *doublequote* is :const:`False` and no *escapechar* is set, :" +"exc:`Error` is raised if a *quotechar* is found in a field." +msgstr "" + +#: ../Doc/library/csv.rst:351 +msgid "" +"A one-character string used by the writer to escape the *delimiter* if " +"*quoting* is set to :const:`QUOTE_NONE` and the *quotechar* if *doublequote* " +"is :const:`False`. On reading, the *escapechar* removes any special meaning " +"from the following character. It defaults to :const:`None`, which disables " +"escaping." +msgstr "" + +#: ../Doc/library/csv.rst:359 +msgid "" +"The string used to terminate lines produced by the :class:`writer`. It " +"defaults to ``'\\r\\n'``." +msgstr "" + +#: ../Doc/library/csv.rst:364 +msgid "" +"The :class:`reader` is hard-coded to recognise either ``'\\r'`` or ``'\\n'`` " +"as end-of-line, and ignores *lineterminator*. This behavior may change in " +"the future." +msgstr "" + +#: ../Doc/library/csv.rst:371 +msgid "" +"A one-character string used to quote fields containing special characters, " +"such as the *delimiter* or *quotechar*, or which contain new-line " +"characters. It defaults to ``'\"'``." +msgstr "" + +#: ../Doc/library/csv.rst:378 +msgid "" +"Controls when quotes should be generated by the writer and recognised by the " +"reader. It can take on any of the :const:`QUOTE_\\*` constants (see " +"section :ref:`csv-contents`) and defaults to :const:`QUOTE_MINIMAL`." +msgstr "" + +#: ../Doc/library/csv.rst:385 +msgid "" +"When :const:`True`, whitespace immediately following the *delimiter* is " +"ignored. The default is :const:`False`." +msgstr "" + +#: ../Doc/library/csv.rst:391 +msgid "" +"When ``True``, raise exception :exc:`Error` on bad CSV input. The default is " +"``False``." +msgstr "" + +#: ../Doc/library/csv.rst:395 +msgid "Reader Objects" +msgstr "" + +#: ../Doc/library/csv.rst:397 +msgid "" +"Reader objects (:class:`DictReader` instances and objects returned by the :" +"func:`reader` function) have the following public methods:" +msgstr "" + +#: ../Doc/library/csv.rst:402 +msgid "" +"Return the next row of the reader's iterable object as a list, parsed " +"according to the current dialect. Usually you should call this as " +"``next(reader)``." +msgstr "" + +#: ../Doc/library/csv.rst:406 +msgid "Reader objects have the following public attributes:" +msgstr "" + +#: ../Doc/library/csv.rst:410 +msgid "A read-only description of the dialect in use by the parser." +msgstr "" + +#: ../Doc/library/csv.rst:415 +msgid "" +"The number of lines read from the source iterator. This is not the same as " +"the number of records returned, as records can span multiple lines." +msgstr "" + +#: ../Doc/library/csv.rst:419 +msgid "DictReader objects have the following public attribute:" +msgstr "" + +#: ../Doc/library/csv.rst:423 +msgid "" +"If not passed as a parameter when creating the object, this attribute is " +"initialized upon first access or when the first record is read from the file." +msgstr "" + +#: ../Doc/library/csv.rst:430 +msgid "Writer Objects" +msgstr "" + +#: ../Doc/library/csv.rst:432 +msgid "" +":class:`Writer` objects (:class:`DictWriter` instances and objects returned " +"by the :func:`writer` function) have the following public methods. A *row* " +"must be an iterable of strings or numbers for :class:`Writer` objects and a " +"dictionary mapping fieldnames to strings or numbers (by passing them " +"through :func:`str` first) for :class:`DictWriter` objects. Note that " +"complex numbers are written out surrounded by parens. This may cause some " +"problems for other programs which read CSV files (assuming they support " +"complex numbers at all)." +msgstr "" + +#: ../Doc/library/csv.rst:443 +msgid "" +"Write the *row* parameter to the writer's file object, formatted according " +"to the current dialect." +msgstr "" + +#: ../Doc/library/csv.rst:446 +msgid "Added support of arbitrary iterables." +msgstr "" + +#: ../Doc/library/csv.rst:451 +msgid "" +"Write all the *rows* parameters (a list of *row* objects as described above) " +"to the writer's file object, formatted according to the current dialect." +msgstr "" + +#: ../Doc/library/csv.rst:454 +msgid "Writer objects have the following public attribute:" +msgstr "" + +#: ../Doc/library/csv.rst:459 +msgid "A read-only description of the dialect in use by the writer." +msgstr "" + +#: ../Doc/library/csv.rst:462 +msgid "DictWriter objects have the following public method:" +msgstr "" + +#: ../Doc/library/csv.rst:467 +msgid "Write a row with the field names (as specified in the constructor)." +msgstr "" + +#: ../Doc/library/csv.rst:477 +msgid "The simplest example of reading a CSV file::" +msgstr "" + +#: ../Doc/library/csv.rst:485 +msgid "Reading a file with an alternate format::" +msgstr "" + +#: ../Doc/library/csv.rst:493 +msgid "The corresponding simplest possible writing example is::" +msgstr "" + +#: ../Doc/library/csv.rst:500 +msgid "" +"Since :func:`open` is used to open a CSV file for reading, the file will by " +"default be decoded into unicode using the system default encoding (see :func:" +"`locale.getpreferredencoding`). To decode a file using a different " +"encoding, use the ``encoding`` argument of open::" +msgstr "" + +#: ../Doc/library/csv.rst:511 +msgid "" +"The same applies to writing in something other than the system default " +"encoding: specify the encoding argument when opening the output file." +msgstr "" + +#: ../Doc/library/csv.rst:514 +msgid "Registering a new dialect::" +msgstr "" + +#: ../Doc/library/csv.rst:521 +msgid "" +"A slightly more advanced use of the reader --- catching and reporting " +"errors::" +msgstr "" + +#: ../Doc/library/csv.rst:533 +msgid "" +"And while the module doesn't directly support parsing strings, it can easily " +"be done::" +msgstr "" + +#: ../Doc/library/csv.rst:543 +msgid "" +"If ``newline=''`` is not specified, newlines embedded inside quoted fields " +"will not be interpreted correctly, and on platforms that use ``\\r\\n`` " +"linendings on write an extra ``\\r`` will be added. It should always be " +"safe to specify ``newline=''``, since the csv module does its own (:term:" +"`universal `) newline handling." +msgstr "" + +#: ../Doc/library/ctypes.rst:2 +msgid ":mod:`ctypes` --- A foreign function library for Python" +msgstr "" + +#: ../Doc/library/ctypes.rst:11 +msgid "" +":mod:`ctypes` is a foreign function library for Python. It provides C " +"compatible data types, and allows calling functions in DLLs or shared " +"libraries. It can be used to wrap these libraries in pure Python." +msgstr "" + +#: ../Doc/library/ctypes.rst:19 +msgid "ctypes tutorial" +msgstr "" + +#: ../Doc/library/ctypes.rst:21 +msgid "" +"Note: The code samples in this tutorial use :mod:`doctest` to make sure that " +"they actually work. Since some code samples behave differently under Linux, " +"Windows, or Mac OS X, they contain doctest directives in comments." +msgstr "" + +#: ../Doc/library/ctypes.rst:25 +msgid "" +"Note: Some code samples reference the ctypes :class:`c_int` type. On " +"platforms where ``sizeof(long) == sizeof(int)`` it is an alias to :class:" +"`c_long`. So, you should not be confused if :class:`c_long` is printed if " +"you would expect :class:`c_int` --- they are actually the same type." +msgstr "" + +#: ../Doc/library/ctypes.rst:33 +msgid "Loading dynamic link libraries" +msgstr "" + +#: ../Doc/library/ctypes.rst:35 +msgid "" +":mod:`ctypes` exports the *cdll*, and on Windows *windll* and *oledll* " +"objects, for loading dynamic link libraries." +msgstr "" + +#: ../Doc/library/ctypes.rst:38 +msgid "" +"You load libraries by accessing them as attributes of these objects. *cdll* " +"loads libraries which export functions using the standard ``cdecl`` calling " +"convention, while *windll* libraries call functions using the ``stdcall`` " +"calling convention. *oledll* also uses the ``stdcall`` calling convention, " +"and assumes the functions return a Windows :c:type:`HRESULT` error code. The " +"error code is used to automatically raise an :class:`OSError` exception when " +"the function call fails." +msgstr "" + +#: ../Doc/library/ctypes.rst:46 +msgid "" +"Windows errors used to raise :exc:`WindowsError`, which is now an alias of :" +"exc:`OSError`." +msgstr "" + +#: ../Doc/library/ctypes.rst:51 +msgid "" +"Here are some examples for Windows. Note that ``msvcrt`` is the MS standard " +"C library containing most standard C functions, and uses the cdecl calling " +"convention::" +msgstr "" + +#: ../Doc/library/ctypes.rst:63 +msgid "Windows appends the usual ``.dll`` file suffix automatically." +msgstr "" + +#: ../Doc/library/ctypes.rst:66 +msgid "" +"Accessing the standard C library through ``cdll.msvcrt`` will use an " +"outdated version of the library that may be incompatible with the one being " +"used by Python. Where possible, use native Python functionality, or else " +"import and use the ``msvcrt`` module." +msgstr "" + +#: ../Doc/library/ctypes.rst:71 +msgid "" +"On Linux, it is required to specify the filename *including* the extension " +"to load a library, so attribute access can not be used to load libraries. " +"Either the :meth:`LoadLibrary` method of the dll loaders should be used, or " +"you should load the library by creating an instance of CDLL by calling the " +"constructor::" +msgstr "" + +#: ../Doc/library/ctypes.rst:89 +msgid "Accessing functions from loaded dlls" +msgstr "" + +#: ../Doc/library/ctypes.rst:91 +msgid "Functions are accessed as attributes of dll objects::" +msgstr "" + +#: ../Doc/library/ctypes.rst:106 +msgid "" +"Note that win32 system dlls like ``kernel32`` and ``user32`` often export " +"ANSI as well as UNICODE versions of a function. The UNICODE version is " +"exported with an ``W`` appended to the name, while the ANSI version is " +"exported with an ``A`` appended to the name. The win32 ``GetModuleHandle`` " +"function, which returns a *module handle* for a given module name, has the " +"following C prototype, and a macro is used to expose one of them as " +"``GetModuleHandle`` depending on whether UNICODE is defined or not::" +msgstr "" + +#: ../Doc/library/ctypes.rst:119 +msgid "" +"*windll* does not try to select one of them by magic, you must access the " +"version you need by specifying ``GetModuleHandleA`` or ``GetModuleHandleW`` " +"explicitly, and then call it with bytes or string objects respectively." +msgstr "" + +#: ../Doc/library/ctypes.rst:123 +msgid "" +"Sometimes, dlls export functions with names which aren't valid Python " +"identifiers, like ``\"??2@YAPAXI@Z\"``. In this case you have to use :func:" +"`getattr` to retrieve the function::" +msgstr "" + +#: ../Doc/library/ctypes.rst:131 +msgid "" +"On Windows, some dlls export functions not by name but by ordinal. These " +"functions can be accessed by indexing the dll object with the ordinal " +"number::" +msgstr "" + +#: ../Doc/library/ctypes.rst:148 +msgid "Calling functions" +msgstr "" + +#: ../Doc/library/ctypes.rst:150 +msgid "" +"You can call these functions like any other Python callable. This example " +"uses the ``time()`` function, which returns system time in seconds since the " +"Unix epoch, and the ``GetModuleHandleA()`` function, which returns a win32 " +"module handle." +msgstr "" + +#: ../Doc/library/ctypes.rst:155 +msgid "" +"This example calls both functions with a NULL pointer (``None`` should be " +"used as the NULL pointer)::" +msgstr "" + +#: ../Doc/library/ctypes.rst:164 +msgid "" +":mod:`ctypes` tries to protect you from calling functions with the wrong " +"number of arguments or the wrong calling convention. Unfortunately this " +"only works on Windows. It does this by examining the stack after the " +"function returns, so although an error is raised the function *has* been " +"called::" +msgstr "" + +#: ../Doc/library/ctypes.rst:179 +msgid "" +"The same exception is raised when you call an ``stdcall`` function with the " +"``cdecl`` calling convention, or vice versa::" +msgstr "" + +#: ../Doc/library/ctypes.rst:194 +msgid "" +"To find out the correct calling convention you have to look into the C " +"header file or the documentation for the function you want to call." +msgstr "" + +#: ../Doc/library/ctypes.rst:197 +msgid "" +"On Windows, :mod:`ctypes` uses win32 structured exception handling to " +"prevent crashes from general protection faults when functions are called " +"with invalid argument values::" +msgstr "" + +#: ../Doc/library/ctypes.rst:207 +msgid "" +"There are, however, enough ways to crash Python with :mod:`ctypes`, so you " +"should be careful anyway. The :mod:`faulthandler` module can be helpful in " +"debugging crashes (e.g. from segmentation faults produced by erroneous C " +"library calls)." +msgstr "" + +#: ../Doc/library/ctypes.rst:212 +msgid "" +"``None``, integers, bytes objects and (unicode) strings are the only native " +"Python objects that can directly be used as parameters in these function " +"calls. ``None`` is passed as a C ``NULL`` pointer, bytes objects and strings " +"are passed as pointer to the memory block that contains their data (:c:type:" +"`char *` or :c:type:`wchar_t *`). Python integers are passed as the " +"platforms default C :c:type:`int` type, their value is masked to fit into " +"the C type." +msgstr "" + +#: ../Doc/library/ctypes.rst:219 +msgid "" +"Before we move on calling functions with other parameter types, we have to " +"learn more about :mod:`ctypes` data types." +msgstr "" + +#: ../Doc/library/ctypes.rst:226 ../Doc/library/ctypes.rst:2050 +msgid "Fundamental data types" +msgstr "" + +#: ../Doc/library/ctypes.rst:228 +msgid ":mod:`ctypes` defines a number of primitive C compatible data types:" +msgstr "" + +#: ../Doc/library/ctypes.rst:231 +msgid "ctypes type" +msgstr "" + +#: ../Doc/library/ctypes.rst:231 +msgid "C type" +msgstr "" + +#: ../Doc/library/ctypes.rst:231 ../Doc/library/sqlite3.rst:774 +#: ../Doc/library/sqlite3.rst:791 ../Doc/library/struct.rst:186 +#: ../Doc/library/xmlrpc.client.rst:87 +msgid "Python type" +msgstr "" + +#: ../Doc/library/ctypes.rst:233 +msgid ":class:`c_bool`" +msgstr "" + +#: ../Doc/library/ctypes.rst:233 ../Doc/library/struct.rst:196 +msgid ":c:type:`_Bool`" +msgstr "" + +#: ../Doc/library/ctypes.rst:233 +msgid "bool (1)" +msgstr "" + +#: ../Doc/library/ctypes.rst:235 +msgid ":class:`c_char`" +msgstr "" + +#: ../Doc/library/ctypes.rst:235 ../Doc/library/ctypes.rst:239 +#: ../Doc/library/struct.rst:190 +msgid ":c:type:`char`" +msgstr "" + +#: ../Doc/library/ctypes.rst:235 +msgid "1-character bytes object" +msgstr "" + +#: ../Doc/library/ctypes.rst:237 +msgid ":class:`c_wchar`" +msgstr "" + +#: ../Doc/library/ctypes.rst:237 +msgid ":c:type:`wchar_t`" +msgstr "" + +#: ../Doc/library/ctypes.rst:237 +msgid "1-character string" +msgstr "" + +#: ../Doc/library/ctypes.rst:239 +msgid ":class:`c_byte`" +msgstr "" + +#: ../Doc/library/ctypes.rst:241 +msgid ":class:`c_ubyte`" +msgstr "" + +#: ../Doc/library/ctypes.rst:241 ../Doc/library/struct.rst:194 +msgid ":c:type:`unsigned char`" +msgstr "" + +#: ../Doc/library/ctypes.rst:243 +msgid ":class:`c_short`" +msgstr "" + +#: ../Doc/library/ctypes.rst:243 ../Doc/library/struct.rst:198 +msgid ":c:type:`short`" +msgstr "" + +#: ../Doc/library/ctypes.rst:245 +msgid ":class:`c_ushort`" +msgstr "" + +#: ../Doc/library/ctypes.rst:245 ../Doc/library/struct.rst:200 +msgid ":c:type:`unsigned short`" +msgstr "" + +#: ../Doc/library/ctypes.rst:247 +msgid ":class:`c_int`" +msgstr "" + +#: ../Doc/library/ctypes.rst:247 ../Doc/library/struct.rst:202 +msgid ":c:type:`int`" +msgstr "" + +#: ../Doc/library/ctypes.rst:249 +msgid ":class:`c_uint`" +msgstr "" + +#: ../Doc/library/ctypes.rst:249 ../Doc/library/struct.rst:204 +msgid ":c:type:`unsigned int`" +msgstr "" + +#: ../Doc/library/ctypes.rst:251 +msgid ":class:`c_long`" +msgstr "" + +#: ../Doc/library/ctypes.rst:251 ../Doc/library/struct.rst:206 +msgid ":c:type:`long`" +msgstr "" + +#: ../Doc/library/ctypes.rst:253 +msgid ":class:`c_ulong`" +msgstr "" + +#: ../Doc/library/ctypes.rst:253 ../Doc/library/struct.rst:208 +msgid ":c:type:`unsigned long`" +msgstr "" + +#: ../Doc/library/ctypes.rst:255 +msgid ":class:`c_longlong`" +msgstr "" + +#: ../Doc/library/ctypes.rst:255 +msgid ":c:type:`__int64` or :c:type:`long long`" +msgstr "" + +#: ../Doc/library/ctypes.rst:257 +msgid ":class:`c_ulonglong`" +msgstr "" + +#: ../Doc/library/ctypes.rst:257 +msgid ":c:type:`unsigned __int64` or :c:type:`unsigned long long`" +msgstr "" + +#: ../Doc/library/ctypes.rst:260 +msgid ":class:`c_size_t`" +msgstr "" + +#: ../Doc/library/ctypes.rst:260 ../Doc/library/struct.rst:217 +msgid ":c:type:`size_t`" +msgstr "" + +#: ../Doc/library/ctypes.rst:262 +msgid ":class:`c_ssize_t`" +msgstr "" + +#: ../Doc/library/ctypes.rst:262 +msgid ":c:type:`ssize_t` or :c:type:`Py_ssize_t`" +msgstr "" + +#: ../Doc/library/ctypes.rst:265 +msgid ":class:`c_float`" +msgstr "" + +#: ../Doc/library/ctypes.rst:265 ../Doc/library/struct.rst:221 +msgid ":c:type:`float`" +msgstr "" + +#: ../Doc/library/ctypes.rst:267 +msgid ":class:`c_double`" +msgstr "" + +#: ../Doc/library/ctypes.rst:267 ../Doc/library/struct.rst:223 +msgid ":c:type:`double`" +msgstr "" + +#: ../Doc/library/ctypes.rst:269 +msgid ":class:`c_longdouble`" +msgstr "" + +#: ../Doc/library/ctypes.rst:269 +msgid ":c:type:`long double`" +msgstr "" + +#: ../Doc/library/ctypes.rst:271 +msgid ":class:`c_char_p`" +msgstr "" + +#: ../Doc/library/ctypes.rst:271 +msgid ":c:type:`char *` (NUL terminated)" +msgstr "" + +#: ../Doc/library/ctypes.rst:271 +msgid "bytes object or ``None``" +msgstr "" + +#: ../Doc/library/ctypes.rst:273 +msgid ":class:`c_wchar_p`" +msgstr "" + +#: ../Doc/library/ctypes.rst:273 +msgid ":c:type:`wchar_t *` (NUL terminated)" +msgstr "" + +#: ../Doc/library/ctypes.rst:273 +msgid "string or ``None``" +msgstr "" + +#: ../Doc/library/ctypes.rst:275 +msgid ":class:`c_void_p`" +msgstr "" + +#: ../Doc/library/ctypes.rst:275 +msgid ":c:type:`void *`" +msgstr "" + +#: ../Doc/library/ctypes.rst:275 +msgid "int or ``None``" +msgstr "" + +#: ../Doc/library/ctypes.rst:279 +msgid "The constructor accepts any object with a truth value." +msgstr "" + +#: ../Doc/library/ctypes.rst:281 +msgid "" +"All these types can be created by calling them with an optional initializer " +"of the correct type and value::" +msgstr "" + +#: ../Doc/library/ctypes.rst:292 +msgid "" +"Since these types are mutable, their value can also be changed afterwards::" +msgstr "" + +#: ../Doc/library/ctypes.rst:304 +msgid "" +"Assigning a new value to instances of the pointer types :class:`c_char_p`, :" +"class:`c_wchar_p`, and :class:`c_void_p` changes the *memory location* they " +"point to, *not the contents* of the memory block (of course not, because " +"Python bytes objects are immutable)::" +msgstr "" + +#: ../Doc/library/ctypes.rst:320 +msgid "" +"You should be careful, however, not to pass them to functions expecting " +"pointers to mutable memory. If you need mutable memory blocks, ctypes has a :" +"func:`create_string_buffer` function which creates these in various ways. " +"The current memory block contents can be accessed (or changed) with the " +"``raw`` property; if you want to access it as NUL terminated string, use the " +"``value`` property::" +msgstr "" + +#: ../Doc/library/ctypes.rst:344 +msgid "" +"The :func:`create_string_buffer` function replaces the :func:`c_buffer` " +"function (which is still available as an alias), as well as the :func:" +"`c_string` function from earlier ctypes releases. To create a mutable " +"memory block containing unicode characters of the C type :c:type:`wchar_t` " +"use the :func:`create_unicode_buffer` function." +msgstr "" + +#: ../Doc/library/ctypes.rst:354 +msgid "Calling functions, continued" +msgstr "" + +#: ../Doc/library/ctypes.rst:356 +msgid "" +"Note that printf prints to the real standard output channel, *not* to :data:" +"`sys.stdout`, so these examples will only work at the console prompt, not " +"from within *IDLE* or *PythonWin*::" +msgstr "" + +#: ../Doc/library/ctypes.rst:376 +msgid "" +"As has been mentioned before, all Python types except integers, strings, and " +"bytes objects have to be wrapped in their corresponding :mod:`ctypes` type, " +"so that they can be converted to the required C data type::" +msgstr "" + +#: ../Doc/library/ctypes.rst:389 +msgid "Calling functions with your own custom data types" +msgstr "" + +#: ../Doc/library/ctypes.rst:391 +msgid "" +"You can also customize :mod:`ctypes` argument conversion to allow instances " +"of your own classes be used as function arguments. :mod:`ctypes` looks for " +"an :attr:`_as_parameter_` attribute and uses this as the function argument. " +"Of course, it must be one of integer, string, or bytes::" +msgstr "" + +#: ../Doc/library/ctypes.rst:406 +msgid "" +"If you don't want to store the instance's data in the :attr:`_as_parameter_` " +"instance variable, you could define a :class:`property` which makes the " +"attribute available on request." +msgstr "" + +#: ../Doc/library/ctypes.rst:414 +msgid "Specifying the required argument types (function prototypes)" +msgstr "" + +#: ../Doc/library/ctypes.rst:416 +msgid "" +"It is possible to specify the required argument types of functions exported " +"from DLLs by setting the :attr:`argtypes` attribute." +msgstr "" + +#: ../Doc/library/ctypes.rst:419 +msgid "" +":attr:`argtypes` must be a sequence of C data types (the ``printf`` function " +"is probably not a good example here, because it takes a variable number and " +"different types of parameters depending on the format string, on the other " +"hand this is quite handy to experiment with this feature)::" +msgstr "" + +#: ../Doc/library/ctypes.rst:430 +msgid "" +"Specifying a format protects against incompatible argument types (just as a " +"prototype for a C function), and tries to convert the arguments to valid " +"types::" +msgstr "" + +#: ../Doc/library/ctypes.rst:442 +msgid "" +"If you have defined your own classes which you pass to function calls, you " +"have to implement a :meth:`from_param` class method for them to be able to " +"use them in the :attr:`argtypes` sequence. The :meth:`from_param` class " +"method receives the Python object passed to the function call, it should do " +"a typecheck or whatever is needed to make sure this object is acceptable, " +"and then return the object itself, its :attr:`_as_parameter_` attribute, or " +"whatever you want to pass as the C function argument in this case. Again, " +"the result should be an integer, string, bytes, a :mod:`ctypes` instance, or " +"an object with an :attr:`_as_parameter_` attribute." +msgstr "" + +#: ../Doc/library/ctypes.rst:456 +msgid "Return types" +msgstr "" + +#: ../Doc/library/ctypes.rst:458 +msgid "" +"By default functions are assumed to return the C :c:type:`int` type. Other " +"return types can be specified by setting the :attr:`restype` attribute of " +"the function object." +msgstr "" + +#: ../Doc/library/ctypes.rst:462 +msgid "" +"Here is a more advanced example, it uses the ``strchr`` function, which " +"expects a string pointer and a char, and returns a pointer to a string::" +msgstr "" + +#: ../Doc/library/ctypes.rst:475 +msgid "" +"If you want to avoid the ``ord(\"x\")`` calls above, you can set the :attr:" +"`argtypes` attribute, and the second argument will be converted from a " +"single character Python bytes object into a C char::" +msgstr "" + +#: ../Doc/library/ctypes.rst:493 +msgid "" +"You can also use a callable Python object (a function or a class for " +"example) as the :attr:`restype` attribute, if the foreign function returns " +"an integer. The callable will be called with the *integer* the C function " +"returns, and the result of this call will be used as the result of your " +"function call. This is useful to check for error return values and " +"automatically raise an exception::" +msgstr "" + +#: ../Doc/library/ctypes.rst:516 +msgid "" +"``WinError`` is a function which will call Windows ``FormatMessage()`` api " +"to get the string representation of an error code, and *returns* an " +"exception. ``WinError`` takes an optional error code parameter, if no one is " +"used, it calls :func:`GetLastError` to retrieve it." +msgstr "" + +#: ../Doc/library/ctypes.rst:521 +msgid "" +"Please note that a much more powerful error checking mechanism is available " +"through the :attr:`errcheck` attribute; see the reference manual for details." +msgstr "" + +#: ../Doc/library/ctypes.rst:528 +msgid "Passing pointers (or: passing parameters by reference)" +msgstr "" + +#: ../Doc/library/ctypes.rst:530 +msgid "" +"Sometimes a C api function expects a *pointer* to a data type as parameter, " +"probably to write into the corresponding location, or if the data is too " +"large to be passed by value. This is also known as *passing parameters by " +"reference*." +msgstr "" + +#: ../Doc/library/ctypes.rst:534 +msgid "" +":mod:`ctypes` exports the :func:`byref` function which is used to pass " +"parameters by reference. The same effect can be achieved with the :func:" +"`pointer` function, although :func:`pointer` does a lot more work since it " +"constructs a real pointer object, so it is faster to use :func:`byref` if " +"you don't need the pointer object in Python itself::" +msgstr "" + +#: ../Doc/library/ctypes.rst:556 +msgid "Structures and unions" +msgstr "" + +#: ../Doc/library/ctypes.rst:558 +msgid "" +"Structures and unions must derive from the :class:`Structure` and :class:" +"`Union` base classes which are defined in the :mod:`ctypes` module. Each " +"subclass must define a :attr:`_fields_` attribute. :attr:`_fields_` must be " +"a list of *2-tuples*, containing a *field name* and a *field type*." +msgstr "" + +#: ../Doc/library/ctypes.rst:563 +msgid "" +"The field type must be a :mod:`ctypes` type like :class:`c_int`, or any " +"other derived :mod:`ctypes` type: structure, union, array, pointer." +msgstr "" + +#: ../Doc/library/ctypes.rst:566 +msgid "" +"Here is a simple example of a POINT structure, which contains two integers " +"named *x* and *y*, and also shows how to initialize a structure in the " +"constructor::" +msgstr "" + +#: ../Doc/library/ctypes.rst:586 +msgid "" +"You can, however, build much more complicated structures. A structure can " +"itself contain other structures by using a structure as a field type." +msgstr "" + +#: ../Doc/library/ctypes.rst:589 +msgid "" +"Here is a RECT structure which contains two POINTs named *upperleft* and " +"*lowerright*::" +msgstr "" + +#: ../Doc/library/ctypes.rst:603 +msgid "" +"Nested structures can also be initialized in the constructor in several " +"ways::" +msgstr "" + +#: ../Doc/library/ctypes.rst:608 +msgid "" +"Field :term:`descriptor`\\s can be retrieved from the *class*, they are " +"useful for debugging because they can provide useful information::" +msgstr "" + +#: ../Doc/library/ctypes.rst:622 +msgid "" +":mod:`ctypes` does not support passing unions or structures with bit-fields " +"to functions by value. While this may work on 32-bit x86, it's not " +"guaranteed by the library to work in the general case. Unions and " +"structures with bit-fields should always be passed to functions by pointer." +msgstr "" + +#: ../Doc/library/ctypes.rst:628 +msgid "Structure/union alignment and byte order" +msgstr "" + +#: ../Doc/library/ctypes.rst:630 +msgid "" +"By default, Structure and Union fields are aligned in the same way the C " +"compiler does it. It is possible to override this behavior be specifying a :" +"attr:`_pack_` class attribute in the subclass definition. This must be set " +"to a positive integer and specifies the maximum alignment for the fields. " +"This is what ``#pragma pack(n)`` also does in MSVC." +msgstr "" + +#: ../Doc/library/ctypes.rst:636 +msgid "" +":mod:`ctypes` uses the native byte order for Structures and Unions. To " +"build structures with non-native byte order, you can use one of the :class:" +"`BigEndianStructure`, :class:`LittleEndianStructure`, :class:" +"`BigEndianUnion`, and :class:`LittleEndianUnion` base classes. These " +"classes cannot contain pointer fields." +msgstr "" + +#: ../Doc/library/ctypes.rst:646 +msgid "Bit fields in structures and unions" +msgstr "" + +#: ../Doc/library/ctypes.rst:648 +msgid "" +"It is possible to create structures and unions containing bit fields. Bit " +"fields are only possible for integer fields, the bit width is specified as " +"the third item in the :attr:`_fields_` tuples::" +msgstr "" + +#: ../Doc/library/ctypes.rst:666 +msgid "Arrays" +msgstr "" + +#: ../Doc/library/ctypes.rst:668 +msgid "" +"Arrays are sequences, containing a fixed number of instances of the same " +"type." +msgstr "" + +#: ../Doc/library/ctypes.rst:670 +msgid "" +"The recommended way to create array types is by multiplying a data type with " +"a positive integer::" +msgstr "" + +#: ../Doc/library/ctypes.rst:675 +msgid "" +"Here is an example of a somewhat artificial data type, a structure " +"containing 4 POINTs among other stuff::" +msgstr "" + +#: ../Doc/library/ctypes.rst:691 +msgid "Instances are created in the usual way, by calling the class::" +msgstr "" + +#: ../Doc/library/ctypes.rst:697 +msgid "" +"The above code print a series of ``0 0`` lines, because the array contents " +"is initialized to zeros." +msgstr "" + +#: ../Doc/library/ctypes.rst:700 +msgid "Initializers of the correct type can also be specified::" +msgstr "" + +#: ../Doc/library/ctypes.rst:716 +msgid "Pointers" +msgstr "" + +#: ../Doc/library/ctypes.rst:718 +msgid "" +"Pointer instances are created by calling the :func:`pointer` function on a :" +"mod:`ctypes` type::" +msgstr "" + +#: ../Doc/library/ctypes.rst:726 +msgid "" +"Pointer instances have a :attr:`~_Pointer.contents` attribute which returns " +"the object to which the pointer points, the ``i`` object above::" +msgstr "" + +#: ../Doc/library/ctypes.rst:733 +msgid "" +"Note that :mod:`ctypes` does not have OOR (original object return), it " +"constructs a new, equivalent object each time you retrieve an attribute::" +msgstr "" + +#: ../Doc/library/ctypes.rst:742 +msgid "" +"Assigning another :class:`c_int` instance to the pointer's contents " +"attribute would cause the pointer to point to the memory location where this " +"is stored::" +msgstr "" + +#: ../Doc/library/ctypes.rst:754 +msgid "Pointer instances can also be indexed with integers::" +msgstr "" + +#: ../Doc/library/ctypes.rst:760 +msgid "Assigning to an integer index changes the pointed to value::" +msgstr "" + +#: ../Doc/library/ctypes.rst:769 +msgid "" +"It is also possible to use indexes different from 0, but you must know what " +"you're doing, just as in C: You can access or change arbitrary memory " +"locations. Generally you only use this feature if you receive a pointer from " +"a C function, and you *know* that the pointer actually points to an array " +"instead of a single item." +msgstr "" + +#: ../Doc/library/ctypes.rst:775 +msgid "" +"Behind the scenes, the :func:`pointer` function does more than simply create " +"pointer instances, it has to create pointer *types* first. This is done with " +"the :func:`POINTER` function, which accepts any :mod:`ctypes` type, and " +"returns a new type::" +msgstr "" + +#: ../Doc/library/ctypes.rst:791 +msgid "" +"Calling the pointer type without an argument creates a ``NULL`` pointer. " +"``NULL`` pointers have a ``False`` boolean value::" +msgstr "" + +#: ../Doc/library/ctypes.rst:799 +msgid "" +":mod:`ctypes` checks for ``NULL`` when dereferencing pointers (but " +"dereferencing invalid non-\\ ``NULL`` pointers would crash Python)::" +msgstr "" + +#: ../Doc/library/ctypes.rst:818 +msgid "Type conversions" +msgstr "" + +#: ../Doc/library/ctypes.rst:820 +msgid "" +"Usually, ctypes does strict type checking. This means, if you have " +"``POINTER(c_int)`` in the :attr:`argtypes` list of a function or as the type " +"of a member field in a structure definition, only instances of exactly the " +"same type are accepted. There are some exceptions to this rule, where " +"ctypes accepts other objects. For example, you can pass compatible array " +"instances instead of pointer types. So, for ``POINTER(c_int)``, ctypes " +"accepts an array of c_int::" +msgstr "" + +#: ../Doc/library/ctypes.rst:841 +msgid "" +"In addition, if a function argument is explicitly declared to be a pointer " +"type (such as ``POINTER(c_int)``) in :attr:`argtypes`, an object of the " +"pointed type (``c_int`` in this case) can be passed to the function. ctypes " +"will apply the required :func:`byref` conversion in this case automatically." +msgstr "" + +#: ../Doc/library/ctypes.rst:846 +msgid "To set a POINTER type field to ``NULL``, you can assign ``None``::" +msgstr "" + +#: ../Doc/library/ctypes.rst:853 +msgid "" +"Sometimes you have instances of incompatible types. In C, you can cast one " +"type into another type. :mod:`ctypes` provides a :func:`cast` function " +"which can be used in the same way. The ``Bar`` structure defined above " +"accepts ``POINTER(c_int)`` pointers or :class:`c_int` arrays for its " +"``values`` field, but not instances of other types::" +msgstr "" + +#: ../Doc/library/ctypes.rst:865 +msgid "For these cases, the :func:`cast` function is handy." +msgstr "" + +#: ../Doc/library/ctypes.rst:867 +msgid "" +"The :func:`cast` function can be used to cast a ctypes instance into a " +"pointer to a different ctypes data type. :func:`cast` takes two parameters, " +"a ctypes object that is or can be converted to a pointer of some kind, and a " +"ctypes pointer type. It returns an instance of the second argument, which " +"references the same memory block as the first argument::" +msgstr "" + +#: ../Doc/library/ctypes.rst:878 +msgid "" +"So, :func:`cast` can be used to assign to the ``values`` field of ``Bar`` " +"the structure::" +msgstr "" + +#: ../Doc/library/ctypes.rst:891 +msgid "Incomplete Types" +msgstr "" + +#: ../Doc/library/ctypes.rst:893 +msgid "" +"*Incomplete Types* are structures, unions or arrays whose members are not " +"yet specified. In C, they are specified by forward declarations, which are " +"defined later::" +msgstr "" + +#: ../Doc/library/ctypes.rst:904 +msgid "" +"The straightforward translation into ctypes code would be this, but it does " +"not work::" +msgstr "" + +#: ../Doc/library/ctypes.rst:917 +msgid "" +"because the new ``class cell`` is not available in the class statement " +"itself. In :mod:`ctypes`, we can define the ``cell`` class and set the :attr:" +"`_fields_` attribute later, after the class statement::" +msgstr "" + +#: ../Doc/library/ctypes.rst:929 +msgid "" +"Lets try it. We create two instances of ``cell``, and let them point to each " +"other, and finally follow the pointer chain a few times::" +msgstr "" + +#: ../Doc/library/ctypes.rst:950 +msgid "Callback functions" +msgstr "" + +#: ../Doc/library/ctypes.rst:952 +msgid "" +":mod:`ctypes` allows creating C callable function pointers from Python " +"callables. These are sometimes called *callback functions*." +msgstr "" + +#: ../Doc/library/ctypes.rst:955 +msgid "" +"First, you must create a class for the callback function. The class knows " +"the calling convention, the return type, and the number and types of " +"arguments this function will receive." +msgstr "" + +#: ../Doc/library/ctypes.rst:959 +msgid "" +"The :func:`CFUNCTYPE` factory function creates types for callback functions " +"using the ``cdecl`` calling convention. On Windows, the :func:`WINFUNCTYPE` " +"factory function creates types for callback functions using the ``stdcall`` " +"calling convention." +msgstr "" + +#: ../Doc/library/ctypes.rst:964 +msgid "" +"Both of these factory functions are called with the result type as first " +"argument, and the callback functions expected argument types as the " +"remaining arguments." +msgstr "" + +#: ../Doc/library/ctypes.rst:968 +msgid "" +"I will present an example here which uses the standard C library's :c:func:" +"`qsort` function, that is used to sort items with the help of a callback " +"function. :c:func:`qsort` will be used to sort an array of integers::" +msgstr "" + +#: ../Doc/library/ctypes.rst:978 +msgid "" +":func:`qsort` must be called with a pointer to the data to sort, the number " +"of items in the data array, the size of one item, and a pointer to the " +"comparison function, the callback. The callback will then be called with two " +"pointers to items, and it must return a negative integer if the first item " +"is smaller than the second, a zero if they are equal, and a positive integer " +"otherwise." +msgstr "" + +#: ../Doc/library/ctypes.rst:984 +msgid "" +"So our callback function receives pointers to integers, and must return an " +"integer. First we create the ``type`` for the callback function::" +msgstr "" + +#: ../Doc/library/ctypes.rst:990 +msgid "" +"To get started, here is a simple callback that shows the values it gets " +"passed::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1000 +msgid "The result::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1010 +msgid "Now we can actually compare the two items and return a useful result::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1025 +msgid "As we can easily check, our array is sorted now::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1034 +msgid "" +"Make sure you keep references to :func:`CFUNCTYPE` objects as long as they " +"are used from C code. :mod:`ctypes` doesn't, and if you don't, they may be " +"garbage collected, crashing your program when a callback is made." +msgstr "" + +#: ../Doc/library/ctypes.rst:1038 +msgid "" +"Also, note that if the callback function is called in a thread created " +"outside of Python's control (e.g. by the foreign code that calls the " +"callback), ctypes creates a new dummy Python thread on every invocation. " +"This behavior is correct for most purposes, but it means that values stored " +"with :class:`threading.local` will *not* survive across different callbacks, " +"even when those calls are made from the same C thread." +msgstr "" + +#: ../Doc/library/ctypes.rst:1048 +msgid "Accessing values exported from dlls" +msgstr "" + +#: ../Doc/library/ctypes.rst:1050 +msgid "" +"Some shared libraries not only export functions, they also export variables. " +"An example in the Python library itself is the :c:data:`Py_OptimizeFlag`, an " +"integer set to 0, 1, or 2, depending on the :option:`-O` or :option:`-OO` " +"flag given on startup." +msgstr "" + +#: ../Doc/library/ctypes.rst:1055 +msgid "" +":mod:`ctypes` can access values like this with the :meth:`in_dll` class " +"methods of the type. *pythonapi* is a predefined symbol giving access to " +"the Python C api::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1064 +msgid "" +"If the interpreter would have been started with :option:`-O`, the sample " +"would have printed ``c_long(1)``, or ``c_long(2)`` if :option:`-OO` would " +"have been specified." +msgstr "" + +#: ../Doc/library/ctypes.rst:1068 +msgid "" +"An extended example which also demonstrates the use of pointers accesses " +"the :c:data:`PyImport_FrozenModules` pointer exported by Python." +msgstr "" + +#: ../Doc/library/ctypes.rst:1071 +msgid "Quoting the docs for that value:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1073 +msgid "" +"This pointer is initialized to point to an array of :c:type:`struct _frozen` " +"records, terminated by one whose members are all *NULL* or zero. When a " +"frozen module is imported, it is searched in this table. Third-party code " +"could play tricks with this to provide a dynamically created collection of " +"frozen modules." +msgstr "" + +#: ../Doc/library/ctypes.rst:1078 +msgid "" +"So manipulating this pointer could even prove useful. To restrict the " +"example size, we show only how this table can be read with :mod:`ctypes`::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1090 +msgid "" +"We have defined the :c:type:`struct _frozen` data type, so we can get the " +"pointer to the table::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1097 +msgid "" +"Since ``table`` is a ``pointer`` to the array of ``struct_frozen`` records, " +"we can iterate over it, but we just have to make sure that our loop " +"terminates, because pointers have no size. Sooner or later it would probably " +"crash with an access violation or whatever, so it's better to break out of " +"the loop when we hit the NULL entry::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1115 +msgid "" +"The fact that standard Python has a frozen module and a frozen package " +"(indicated by the negative size member) is not well known, it is only used " +"for testing. Try it out with ``import __hello__`` for example." +msgstr "" + +#: ../Doc/library/ctypes.rst:1123 +msgid "Surprises" +msgstr "" + +#: ../Doc/library/ctypes.rst:1125 +msgid "" +"There are some edges in :mod:`ctypes` where you might expect something other " +"than what actually happens." +msgstr "" + +#: ../Doc/library/ctypes.rst:1128 +msgid "Consider the following example::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1148 +msgid "" +"Hm. We certainly expected the last statement to print ``3 4 1 2``. What " +"happened? Here are the steps of the ``rc.a, rc.b = rc.b, rc.a`` line above::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1156 +msgid "" +"Note that ``temp0`` and ``temp1`` are objects still using the internal " +"buffer of the ``rc`` object above. So executing ``rc.a = temp0`` copies the " +"buffer contents of ``temp0`` into ``rc`` 's buffer. This, in turn, changes " +"the contents of ``temp1``. So, the last assignment ``rc.b = temp1``, doesn't " +"have the expected effect." +msgstr "" + +#: ../Doc/library/ctypes.rst:1162 +msgid "" +"Keep in mind that retrieving sub-objects from Structure, Unions, and Arrays " +"doesn't *copy* the sub-object, instead it retrieves a wrapper object " +"accessing the root-object's underlying buffer." +msgstr "" + +#: ../Doc/library/ctypes.rst:1166 +msgid "" +"Another example that may behave different from what one would expect is " +"this::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1176 +msgid "" +"Why is it printing ``False``? ctypes instances are objects containing a " +"memory block plus some :term:`descriptor`\\s accessing the contents of the " +"memory. Storing a Python object in the memory block does not store the " +"object itself, instead the ``contents`` of the object is stored. Accessing " +"the contents again constructs a new Python object each time!" +msgstr "" + +#: ../Doc/library/ctypes.rst:1186 +msgid "Variable-sized data types" +msgstr "" + +#: ../Doc/library/ctypes.rst:1188 +msgid "" +":mod:`ctypes` provides some support for variable-sized arrays and structures." +msgstr "" + +#: ../Doc/library/ctypes.rst:1190 +msgid "" +"The :func:`resize` function can be used to resize the memory buffer of an " +"existing ctypes object. The function takes the object as first argument, " +"and the requested size in bytes as the second argument. The memory block " +"cannot be made smaller than the natural memory block specified by the " +"objects type, a :exc:`ValueError` is raised if this is tried::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1210 +msgid "" +"This is nice and fine, but how would one access the additional elements " +"contained in this array? Since the type still only knows about 4 elements, " +"we get errors accessing other elements::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1222 +msgid "" +"Another way to use variable-sized data types with :mod:`ctypes` is to use " +"the dynamic nature of Python, and (re-)define the data type after the " +"required size is already known, on a case by case basis." +msgstr "" + +#: ../Doc/library/ctypes.rst:1230 +msgid "ctypes reference" +msgstr "" + +#: ../Doc/library/ctypes.rst:1236 +msgid "Finding shared libraries" +msgstr "" + +#: ../Doc/library/ctypes.rst:1238 +msgid "" +"When programming in a compiled language, shared libraries are accessed when " +"compiling/linking a program, and when the program is run." +msgstr "" + +#: ../Doc/library/ctypes.rst:1241 +msgid "" +"The purpose of the :func:`find_library` function is to locate a library in a " +"way similar to what the compiler or runtime loader does (on platforms with " +"several versions of a shared library the most recent should be loaded), " +"while the ctypes library loaders act like when a program is run, and call " +"the runtime loader directly." +msgstr "" + +#: ../Doc/library/ctypes.rst:1247 +msgid "" +"The :mod:`ctypes.util` module provides a function which can help to " +"determine the library to load." +msgstr "" + +#: ../Doc/library/ctypes.rst:1255 +msgid "" +"Try to find a library and return a pathname. *name* is the library name " +"without any prefix like *lib*, suffix like ``.so``, ``.dylib`` or version " +"number (this is the form used for the posix linker option :option:`-l`). If " +"no library can be found, returns ``None``." +msgstr "" + +#: ../Doc/library/ctypes.rst:1260 ../Doc/library/ctypes.rst:1844 +msgid "The exact functionality is system dependent." +msgstr "" + +#: ../Doc/library/ctypes.rst:1262 +msgid "" +"On Linux, :func:`find_library` tries to run external programs (``/sbin/" +"ldconfig``, ``gcc``, ``objdump`` and ``ld``) to find the library file. It " +"returns the filename of the library file." +msgstr "" + +#: ../Doc/library/ctypes.rst:1266 +msgid "" +"On Linux, the value of the environment variable ``LD_LIBRARY_PATH`` is used " +"when searching for libraries, if a library cannot be found by any other " +"means." +msgstr "" + +#: ../Doc/library/ctypes.rst:1270 +msgid "Here are some examples::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1281 +msgid "" +"On OS X, :func:`find_library` tries several predefined naming schemes and " +"paths to locate the library, and returns a full pathname if successful::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1295 +msgid "" +"On Windows, :func:`find_library` searches along the system search path, and " +"returns the full pathname, but since there is no predefined naming scheme a " +"call like ``find_library(\"c\")`` will fail and return ``None``." +msgstr "" + +#: ../Doc/library/ctypes.rst:1299 +msgid "" +"If wrapping a shared library with :mod:`ctypes`, it *may* be better to " +"determine the shared library name at development time, and hardcode that " +"into the wrapper module instead of using :func:`find_library` to locate the " +"library at runtime." +msgstr "" + +#: ../Doc/library/ctypes.rst:1307 +msgid "Loading shared libraries" +msgstr "" + +#: ../Doc/library/ctypes.rst:1309 +msgid "" +"There are several ways to load shared libraries into the Python process. " +"One way is to instantiate one of the following classes:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1315 +msgid "" +"Instances of this class represent loaded shared libraries. Functions in " +"these libraries use the standard C calling convention, and are assumed to " +"return :c:type:`int`." +msgstr "" + +#: ../Doc/library/ctypes.rst:1322 +msgid "" +"Windows only: Instances of this class represent loaded shared libraries, " +"functions in these libraries use the ``stdcall`` calling convention, and are " +"assumed to return the windows specific :class:`HRESULT` code. :class:" +"`HRESULT` values contain information specifying whether the function call " +"failed or succeeded, together with additional error code. If the return " +"value signals a failure, an :class:`OSError` is automatically raised." +msgstr "" + +#: ../Doc/library/ctypes.rst:1329 +msgid ":exc:`WindowsError` used to be raised." +msgstr "" + +#: ../Doc/library/ctypes.rst:1335 +msgid "" +"Windows only: Instances of this class represent loaded shared libraries, " +"functions in these libraries use the ``stdcall`` calling convention, and are " +"assumed to return :c:type:`int` by default." +msgstr "" + +#: ../Doc/library/ctypes.rst:1339 +msgid "" +"On Windows CE only the standard calling convention is used, for convenience " +"the :class:`WinDLL` and :class:`OleDLL` use the standard calling convention " +"on this platform." +msgstr "" + +#: ../Doc/library/ctypes.rst:1343 +msgid "" +"The Python :term:`global interpreter lock` is released before calling any " +"function exported by these libraries, and reacquired afterwards." +msgstr "" + +#: ../Doc/library/ctypes.rst:1349 +msgid "" +"Instances of this class behave like :class:`CDLL` instances, except that the " +"Python GIL is *not* released during the function call, and after the " +"function execution the Python error flag is checked. If the error flag is " +"set, a Python exception is raised." +msgstr "" + +#: ../Doc/library/ctypes.rst:1354 +msgid "Thus, this is only useful to call Python C api functions directly." +msgstr "" + +#: ../Doc/library/ctypes.rst:1356 +msgid "" +"All these classes can be instantiated by calling them with at least one " +"argument, the pathname of the shared library. If you have an existing " +"handle to an already loaded shared library, it can be passed as the " +"``handle`` named parameter, otherwise the underlying platforms ``dlopen`` or " +"``LoadLibrary`` function is used to load the library into the process, and " +"to get a handle to it." +msgstr "" + +#: ../Doc/library/ctypes.rst:1363 +msgid "" +"The *mode* parameter can be used to specify how the library is loaded. For " +"details, consult the :manpage:`dlopen(3)` manpage. On Windows, *mode* is " +"ignored. On posix systems, RTLD_NOW is always added, and is not " +"configurable." +msgstr "" + +#: ../Doc/library/ctypes.rst:1368 +msgid "" +"The *use_errno* parameter, when set to True, enables a ctypes mechanism that " +"allows accessing the system :data:`errno` error number in a safe way. :mod:" +"`ctypes` maintains a thread-local copy of the systems :data:`errno` " +"variable; if you call foreign functions created with ``use_errno=True`` then " +"the :data:`errno` value before the function call is swapped with the ctypes " +"private copy, the same happens immediately after the function call." +msgstr "" + +#: ../Doc/library/ctypes.rst:1375 +msgid "" +"The function :func:`ctypes.get_errno` returns the value of the ctypes " +"private copy, and the function :func:`ctypes.set_errno` changes the ctypes " +"private copy to a new value and returns the former value." +msgstr "" + +#: ../Doc/library/ctypes.rst:1379 +msgid "" +"The *use_last_error* parameter, when set to True, enables the same mechanism " +"for the Windows error code which is managed by the :func:`GetLastError` and :" +"func:`SetLastError` Windows API functions; :func:`ctypes.get_last_error` " +"and :func:`ctypes.set_last_error` are used to request and change the ctypes " +"private copy of the windows error code." +msgstr "" + +#: ../Doc/library/ctypes.rst:1388 +msgid "" +"Flag to use as *mode* parameter. On platforms where this flag is not " +"available, it is defined as the integer zero." +msgstr "" + +#: ../Doc/library/ctypes.rst:1395 +msgid "" +"Flag to use as *mode* parameter. On platforms where this is not available, " +"it is the same as *RTLD_GLOBAL*." +msgstr "" + +#: ../Doc/library/ctypes.rst:1402 +msgid "" +"The default mode which is used to load shared libraries. On OSX 10.3, this " +"is *RTLD_GLOBAL*, otherwise it is the same as *RTLD_LOCAL*." +msgstr "" + +#: ../Doc/library/ctypes.rst:1405 +msgid "" +"Instances of these classes have no public methods. Functions exported by " +"the shared library can be accessed as attributes or by index. Please note " +"that accessing the function through an attribute caches the result and " +"therefore accessing it repeatedly returns the same object each time. On the " +"other hand, accessing it through an index returns a new object each time:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1416 +msgid "" +"The following public attributes are available, their name starts with an " +"underscore to not clash with exported function names:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1422 +msgid "The system handle used to access the library." +msgstr "" + +#: ../Doc/library/ctypes.rst:1427 +msgid "The name of the library passed in the constructor." +msgstr "" + +#: ../Doc/library/ctypes.rst:1429 +msgid "" +"Shared libraries can also be loaded by using one of the prefabricated " +"objects, which are instances of the :class:`LibraryLoader` class, either by " +"calling the :meth:`LoadLibrary` method, or by retrieving the library as " +"attribute of the loader instance." +msgstr "" + +#: ../Doc/library/ctypes.rst:1437 +msgid "" +"Class which loads shared libraries. *dlltype* should be one of the :class:" +"`CDLL`, :class:`PyDLL`, :class:`WinDLL`, or :class:`OleDLL` types." +msgstr "" + +#: ../Doc/library/ctypes.rst:1440 +msgid "" +":meth:`__getattr__` has special behavior: It allows loading a shared library " +"by accessing it as attribute of a library loader instance. The result is " +"cached, so repeated attribute accesses return the same library each time." +msgstr "" + +#: ../Doc/library/ctypes.rst:1446 +msgid "" +"Load a shared library into the process and return it. This method always " +"returns a new instance of the library." +msgstr "" + +#: ../Doc/library/ctypes.rst:1450 +msgid "These prefabricated library loaders are available:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1455 +msgid "Creates :class:`CDLL` instances." +msgstr "" + +#: ../Doc/library/ctypes.rst:1461 +msgid "Windows only: Creates :class:`WinDLL` instances." +msgstr "" + +#: ../Doc/library/ctypes.rst:1467 +msgid "Windows only: Creates :class:`OleDLL` instances." +msgstr "" + +#: ../Doc/library/ctypes.rst:1473 +msgid "Creates :class:`PyDLL` instances." +msgstr "" + +#: ../Doc/library/ctypes.rst:1476 +msgid "" +"For accessing the C Python api directly, a ready-to-use Python shared " +"library object is available:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1482 +msgid "" +"An instance of :class:`PyDLL` that exposes Python C API functions as " +"attributes. Note that all these functions are assumed to return C :c:type:" +"`int`, which is of course not always the truth, so you have to assign the " +"correct :attr:`restype` attribute to use these functions." +msgstr "" + +#: ../Doc/library/ctypes.rst:1491 +msgid "Foreign functions" +msgstr "" + +#: ../Doc/library/ctypes.rst:1493 +msgid "" +"As explained in the previous section, foreign functions can be accessed as " +"attributes of loaded shared libraries. The function objects created in this " +"way by default accept any number of arguments, accept any ctypes data " +"instances as arguments, and return the default result type specified by the " +"library loader. They are instances of a private class:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1502 +msgid "Base class for C callable foreign functions." +msgstr "" + +#: ../Doc/library/ctypes.rst:1504 +msgid "" +"Instances of foreign functions are also C compatible data types; they " +"represent C function pointers." +msgstr "" + +#: ../Doc/library/ctypes.rst:1507 +msgid "" +"This behavior can be customized by assigning to special attributes of the " +"foreign function object." +msgstr "" + +#: ../Doc/library/ctypes.rst:1512 +msgid "" +"Assign a ctypes type to specify the result type of the foreign function. Use " +"``None`` for :c:type:`void`, a function not returning anything." +msgstr "" + +#: ../Doc/library/ctypes.rst:1515 +msgid "" +"It is possible to assign a callable Python object that is not a ctypes type, " +"in this case the function is assumed to return a C :c:type:`int`, and the " +"callable will be called with this integer, allowing further processing or " +"error checking. Using this is deprecated, for more flexible post processing " +"or error checking use a ctypes data type as :attr:`restype` and assign a " +"callable to the :attr:`errcheck` attribute." +msgstr "" + +#: ../Doc/library/ctypes.rst:1524 +msgid "" +"Assign a tuple of ctypes types to specify the argument types that the " +"function accepts. Functions using the ``stdcall`` calling convention can " +"only be called with the same number of arguments as the length of this " +"tuple; functions using the C calling convention accept additional, " +"unspecified arguments as well." +msgstr "" + +#: ../Doc/library/ctypes.rst:1530 +msgid "" +"When a foreign function is called, each actual argument is passed to the :" +"meth:`from_param` class method of the items in the :attr:`argtypes` tuple, " +"this method allows adapting the actual argument to an object that the " +"foreign function accepts. For example, a :class:`c_char_p` item in the :" +"attr:`argtypes` tuple will convert a string passed as argument into a bytes " +"object using ctypes conversion rules." +msgstr "" + +#: ../Doc/library/ctypes.rst:1537 +msgid "" +"New: It is now possible to put items in argtypes which are not ctypes types, " +"but each item must have a :meth:`from_param` method which returns a value " +"usable as argument (integer, string, ctypes instance). This allows defining " +"adapters that can adapt custom objects as function parameters." +msgstr "" + +#: ../Doc/library/ctypes.rst:1544 +msgid "" +"Assign a Python function or another callable to this attribute. The callable " +"will be called with three or more arguments:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1551 +msgid "" +"*result* is what the foreign function returns, as specified by the :attr:" +"`restype` attribute." +msgstr "" + +#: ../Doc/library/ctypes.rst:1554 +msgid "" +"*func* is the foreign function object itself, this allows reusing the same " +"callable object to check or post process the results of several functions." +msgstr "" + +#: ../Doc/library/ctypes.rst:1558 +msgid "" +"*arguments* is a tuple containing the parameters originally passed to the " +"function call, this allows specializing the behavior on the arguments used." +msgstr "" + +#: ../Doc/library/ctypes.rst:1562 +msgid "" +"The object that this function returns will be returned from the foreign " +"function call, but it can also check the result value and raise an exception " +"if the foreign function call failed." +msgstr "" + +#: ../Doc/library/ctypes.rst:1569 +msgid "" +"This exception is raised when a foreign function call cannot convert one of " +"the passed arguments." +msgstr "" + +#: ../Doc/library/ctypes.rst:1576 +msgid "Function prototypes" +msgstr "" + +#: ../Doc/library/ctypes.rst:1578 +msgid "" +"Foreign functions can also be created by instantiating function prototypes. " +"Function prototypes are similar to function prototypes in C; they describe a " +"function (return type, argument types, calling convention) without defining " +"an implementation. The factory functions must be called with the desired " +"result type and the argument types of the function." +msgstr "" + +#: ../Doc/library/ctypes.rst:1587 +msgid "" +"The returned function prototype creates functions that use the standard C " +"calling convention. The function will release the GIL during the call. If " +"*use_errno* is set to True, the ctypes private copy of the system :data:" +"`errno` variable is exchanged with the real :data:`errno` value before and " +"after the call; *use_last_error* does the same for the Windows error code." +msgstr "" + +#: ../Doc/library/ctypes.rst:1597 +msgid "" +"Windows only: The returned function prototype creates functions that use the " +"``stdcall`` calling convention, except on Windows CE where :func:" +"`WINFUNCTYPE` is the same as :func:`CFUNCTYPE`. The function will release " +"the GIL during the call. *use_errno* and *use_last_error* have the same " +"meaning as above." +msgstr "" + +#: ../Doc/library/ctypes.rst:1606 +msgid "" +"The returned function prototype creates functions that use the Python " +"calling convention. The function will *not* release the GIL during the call." +msgstr "" + +#: ../Doc/library/ctypes.rst:1609 +msgid "" +"Function prototypes created by these factory functions can be instantiated " +"in different ways, depending on the type and number of the parameters in the " +"call:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1617 +msgid "" +"Returns a foreign function at the specified address which must be an integer." +msgstr "" + +#: ../Doc/library/ctypes.rst:1624 +msgid "" +"Create a C callable function (a callback function) from a Python *callable*." +msgstr "" + +#: ../Doc/library/ctypes.rst:1631 +msgid "" +"Returns a foreign function exported by a shared library. *func_spec* must be " +"a 2-tuple ``(name_or_ordinal, library)``. The first item is the name of the " +"exported function as string, or the ordinal of the exported function as " +"small integer. The second item is the shared library instance." +msgstr "" + +#: ../Doc/library/ctypes.rst:1641 +msgid "" +"Returns a foreign function that will call a COM method. *vtbl_index* is the " +"index into the virtual function table, a small non-negative integer. *name* " +"is name of the COM method. *iid* is an optional pointer to the interface " +"identifier which is used in extended error reporting." +msgstr "" + +#: ../Doc/library/ctypes.rst:1646 +msgid "" +"COM methods use a special calling convention: They require a pointer to the " +"COM interface as first argument, in addition to those parameters that are " +"specified in the :attr:`argtypes` tuple." +msgstr "" + +#: ../Doc/library/ctypes.rst:1650 +msgid "" +"The optional *paramflags* parameter creates foreign function wrappers with " +"much more functionality than the features described above." +msgstr "" + +#: ../Doc/library/ctypes.rst:1653 +msgid "*paramflags* must be a tuple of the same length as :attr:`argtypes`." +msgstr "" + +#: ../Doc/library/ctypes.rst:1655 +msgid "" +"Each item in this tuple contains further information about a parameter, it " +"must be a tuple containing one, two, or three items." +msgstr "" + +#: ../Doc/library/ctypes.rst:1658 +msgid "" +"The first item is an integer containing a combination of direction flags for " +"the parameter:" +msgstr "" + +#: ../Doc/library/ctypes.rst:1662 +msgid "Specifies an input parameter to the function." +msgstr "" + +#: ../Doc/library/ctypes.rst:1665 +msgid "Output parameter. The foreign function fills in a value." +msgstr "" + +#: ../Doc/library/ctypes.rst:1668 +msgid "Input parameter which defaults to the integer zero." +msgstr "" + +#: ../Doc/library/ctypes.rst:1670 +msgid "" +"The optional second item is the parameter name as string. If this is " +"specified, the foreign function can be called with named parameters." +msgstr "" + +#: ../Doc/library/ctypes.rst:1673 +msgid "The optional third item is the default value for this parameter." +msgstr "" + +#: ../Doc/library/ctypes.rst:1675 +msgid "" +"This example demonstrates how to wrap the Windows ``MessageBoxW`` function " +"so that it supports default parameters and named arguments. The C " +"declaration from the windows header file is this::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1686 ../Doc/library/ctypes.rst:1709 +msgid "Here is the wrapping with :mod:`ctypes`::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1694 +msgid "The ``MessageBox`` foreign function can now be called in these ways::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1700 +msgid "" +"A second example demonstrates output parameters. The win32 " +"``GetWindowRect`` function retrieves the dimensions of a specified window by " +"copying them into ``RECT`` structure that the caller has to supply. Here is " +"the C declaration::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1718 +msgid "" +"Functions with output parameters will automatically return the output " +"parameter value if there is a single one, or a tuple containing the output " +"parameter values when there are more than one, so the GetWindowRect function " +"now returns a RECT instance, when called." +msgstr "" + +#: ../Doc/library/ctypes.rst:1723 +msgid "" +"Output parameters can be combined with the :attr:`errcheck` protocol to do " +"further output processing and error checking. The win32 ``GetWindowRect`` " +"api function returns a ``BOOL`` to signal success or failure, so this " +"function could do the error checking, and raises an exception when the api " +"call failed::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1736 +msgid "" +"If the :attr:`errcheck` function returns the argument tuple it receives " +"unchanged, :mod:`ctypes` continues the normal processing it does on the " +"output parameters. If you want to return a tuple of window coordinates " +"instead of a ``RECT`` instance, you can retrieve the fields in the function " +"and return them instead, the normal processing will no longer take place::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1755 ../Doc/library/nntplib.rst:550 +msgid "Utility functions" +msgstr "" + +#: ../Doc/library/ctypes.rst:1759 +msgid "" +"Returns the address of the memory buffer as integer. *obj* must be an " +"instance of a ctypes type." +msgstr "" + +#: ../Doc/library/ctypes.rst:1765 +msgid "" +"Returns the alignment requirements of a ctypes type. *obj_or_type* must be a " +"ctypes type or instance." +msgstr "" + +#: ../Doc/library/ctypes.rst:1771 +msgid "" +"Returns a light-weight pointer to *obj*, which must be an instance of a " +"ctypes type. *offset* defaults to zero, and must be an integer that will be " +"added to the internal pointer value." +msgstr "" + +#: ../Doc/library/ctypes.rst:1775 +msgid "``byref(obj, offset)`` corresponds to this C code::" +msgstr "" + +#: ../Doc/library/ctypes.rst:1779 +msgid "" +"The returned object can only be used as a foreign function call parameter. " +"It behaves similar to ``pointer(obj)``, but the construction is a lot faster." +msgstr "" + +#: ../Doc/library/ctypes.rst:1785 +msgid "" +"This function is similar to the cast operator in C. It returns a new " +"instance of *type* which points to the same memory block as *obj*. *type* " +"must be a pointer type, and *obj* must be an object that can be interpreted " +"as a pointer." +msgstr "" + +#: ../Doc/library/ctypes.rst:1793 +msgid "" +"This function creates a mutable character buffer. The returned object is a " +"ctypes array of :class:`c_char`." +msgstr "" + +#: ../Doc/library/ctypes.rst:1796 +msgid "" +"*init_or_size* must be an integer which specifies the size of the array, or " +"a bytes object which will be used to initialize the array items." +msgstr "" + +#: ../Doc/library/ctypes.rst:1799 +msgid "" +"If a bytes object is specified as first argument, the buffer is made one " +"item larger than its length so that the last element in the array is a NUL " +"termination character. An integer can be passed as second argument which " +"allows specifying the size of the array if the length of the bytes should " +"not be used." +msgstr "" + +#: ../Doc/library/ctypes.rst:1808 +msgid "" +"This function creates a mutable unicode character buffer. The returned " +"object is a ctypes array of :class:`c_wchar`." +msgstr "" + +#: ../Doc/library/ctypes.rst:1811 +msgid "" +"*init_or_size* must be an integer which specifies the size of the array, or " +"a string which will be used to initialize the array items." +msgstr "" + +#: ../Doc/library/ctypes.rst:1814 +msgid "" +"If a string is specified as first argument, the buffer is made one item " +"larger than the length of the string so that the last element in the array " +"is a NUL termination character. An integer can be passed as second argument " +"which allows specifying the size of the array if the length of the string " +"should not be used." +msgstr "" + +#: ../Doc/library/ctypes.rst:1824 +msgid "" +"Windows only: This function is a hook which allows implementing in-process " +"COM servers with ctypes. It is called from the DllCanUnloadNow function " +"that the _ctypes extension dll exports." +msgstr "" + +#: ../Doc/library/ctypes.rst:1831 +msgid "" +"Windows only: This function is a hook which allows implementing in-process " +"COM servers with ctypes. It is called from the DllGetClassObject function " +"that the ``_ctypes`` extension dll exports." +msgstr "" + +#: ../Doc/library/ctypes.rst:1839 +msgid "" +"Try to find a library and return a pathname. *name* is the library name " +"without any prefix like ``lib``, suffix like ``.so``, ``.dylib`` or version " +"number (this is the form used for the posix linker option :option:`-l`). If " +"no library can be found, returns ``None``." +msgstr "" + +#: ../Doc/library/ctypes.rst:1850 +msgid "" +"Windows only: return the filename of the VC runtime library used by Python, " +"and by the extension modules. If the name of the library cannot be " +"determined, ``None`` is returned." +msgstr "" + +#: ../Doc/library/ctypes.rst:1854 +msgid "" +"If you need to free memory, for example, allocated by an extension module " +"with a call to the ``free(void *)``, it is important that you use the " +"function in the same library that allocated the memory." +msgstr "" + +#: ../Doc/library/ctypes.rst:1861 +msgid "" +"Windows only: Returns a textual description of the error code *code*. If no " +"error code is specified, the last error code is used by calling the Windows " +"api function GetLastError." +msgstr "" + +#: ../Doc/library/ctypes.rst:1868 +msgid "" +"Windows only: Returns the last error code set by Windows in the calling " +"thread. This function calls the Windows `GetLastError()` function directly, " +"it does not return the ctypes-private copy of the error code." +msgstr "" + +#: ../Doc/library/ctypes.rst:1874 +msgid "" +"Returns the current value of the ctypes-private copy of the system :data:" +"`errno` variable in the calling thread." +msgstr "" + +#: ../Doc/library/ctypes.rst:1879 +msgid "" +"Windows only: returns the current value of the ctypes-private copy of the " +"system :data:`LastError` variable in the calling thread." +msgstr "" + +#: ../Doc/library/ctypes.rst:1884 +msgid "" +"Same as the standard C memmove library function: copies *count* bytes from " +"*src* to *dst*. *dst* and *src* must be integers or ctypes instances that " +"can be converted to pointers." +msgstr "" + +#: ../Doc/library/ctypes.rst:1891 +msgid "" +"Same as the standard C memset library function: fills the memory block at " +"address *dst* with *count* bytes of value *c*. *dst* must be an integer " +"specifying an address, or a ctypes instance." +msgstr "" + +#: ../Doc/library/ctypes.rst:1898 +msgid "" +"This factory function creates and returns a new ctypes pointer type. Pointer " +"types are cached and reused internally, so calling this function repeatedly " +"is cheap. *type* must be a ctypes type." +msgstr "" + +#: ../Doc/library/ctypes.rst:1905 +msgid "" +"This function creates a new pointer instance, pointing to *obj*. The " +"returned object is of the type ``POINTER(type(obj))``." +msgstr "" + +#: ../Doc/library/ctypes.rst:1908 +msgid "" +"Note: If you just want to pass a pointer to an object to a foreign function " +"call, you should use ``byref(obj)`` which is much faster." +msgstr "" + +#: ../Doc/library/ctypes.rst:1914 +msgid "" +"This function resizes the internal memory buffer of *obj*, which must be an " +"instance of a ctypes type. It is not possible to make the buffer smaller " +"than the native size of the objects type, as given by ``sizeof(type(obj))``, " +"but it is possible to enlarge the buffer." +msgstr "" + +#: ../Doc/library/ctypes.rst:1922 +msgid "" +"Set the current value of the ctypes-private copy of the system :data:`errno` " +"variable in the calling thread to *value* and return the previous value." +msgstr "" + +#: ../Doc/library/ctypes.rst:1929 +msgid "" +"Windows only: set the current value of the ctypes-private copy of the " +"system :data:`LastError` variable in the calling thread to *value* and " +"return the previous value." +msgstr "" + +#: ../Doc/library/ctypes.rst:1937 +msgid "" +"Returns the size in bytes of a ctypes type or instance memory buffer. Does " +"the same as the C ``sizeof`` operator." +msgstr "" + +#: ../Doc/library/ctypes.rst:1943 +msgid "" +"This function returns the C string starting at memory address *address* as a " +"bytes object. If size is specified, it is used as size, otherwise the string " +"is assumed to be zero-terminated." +msgstr "" + +#: ../Doc/library/ctypes.rst:1950 +msgid "" +"Windows only: this function is probably the worst-named thing in ctypes. It " +"creates an instance of OSError. If *code* is not specified, " +"``GetLastError`` is called to determine the error code. If *descr* is not " +"specified, :func:`FormatError` is called to get a textual description of the " +"error." +msgstr "" + +#: ../Doc/library/ctypes.rst:1956 +msgid "An instance of :exc:`WindowsError` used to be created." +msgstr "" + +#: ../Doc/library/ctypes.rst:1962 +msgid "" +"This function returns the wide character string starting at memory address " +"*address* as a string. If *size* is specified, it is used as the number of " +"characters of the string, otherwise the string is assumed to be zero-" +"terminated." +msgstr "" + +#: ../Doc/library/ctypes.rst:1971 +msgid "Data types" +msgstr "" + +#: ../Doc/library/ctypes.rst:1976 +msgid "" +"This non-public class is the common base class of all ctypes data types. " +"Among other things, all ctypes type instances contain a memory block that " +"hold C compatible data; the address of the memory block is returned by the :" +"func:`addressof` helper function. Another instance variable is exposed as :" +"attr:`_objects`; this contains other Python objects that need to be kept " +"alive in case the memory block contains pointers." +msgstr "" + +#: ../Doc/library/ctypes.rst:1983 +msgid "" +"Common methods of ctypes data types, these are all class methods (to be " +"exact, they are methods of the :term:`metaclass`):" +msgstr "" + +#: ../Doc/library/ctypes.rst:1988 +msgid "" +"This method returns a ctypes instance that shares the buffer of the *source* " +"object. The *source* object must support the writeable buffer interface. " +"The optional *offset* parameter specifies an offset into the source buffer " +"in bytes; the default is zero. If the source buffer is not large enough a :" +"exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/ctypes.rst:1997 +msgid "" +"This method creates a ctypes instance, copying the buffer from the *source* " +"object buffer which must be readable. The optional *offset* parameter " +"specifies an offset into the source buffer in bytes; the default is zero. " +"If the source buffer is not large enough a :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/ctypes.rst:2005 +msgid "" +"This method returns a ctypes type instance using the memory specified by " +"*address* which must be an integer." +msgstr "" + +#: ../Doc/library/ctypes.rst:2010 +msgid "" +"This method adapts *obj* to a ctypes type. It is called with the actual " +"object used in a foreign function call when the type is present in the " +"foreign function's :attr:`argtypes` tuple; it must return an object that can " +"be used as a function call parameter." +msgstr "" + +#: ../Doc/library/ctypes.rst:2015 +msgid "" +"All ctypes data types have a default implementation of this classmethod that " +"normally returns *obj* if that is an instance of the type. Some types " +"accept other objects as well." +msgstr "" + +#: ../Doc/library/ctypes.rst:2021 +msgid "" +"This method returns a ctypes type instance exported by a shared library. " +"*name* is the name of the symbol that exports the data, *library* is the " +"loaded shared library." +msgstr "" + +#: ../Doc/library/ctypes.rst:2025 +msgid "Common instance variables of ctypes data types:" +msgstr "" + +#: ../Doc/library/ctypes.rst:2029 +msgid "" +"Sometimes ctypes data instances do not own the memory block they contain, " +"instead they share part of the memory block of a base object. The :attr:" +"`_b_base_` read-only member is the root ctypes object that owns the memory " +"block." +msgstr "" + +#: ../Doc/library/ctypes.rst:2036 +msgid "" +"This read-only variable is true when the ctypes data instance has allocated " +"the memory block itself, false otherwise." +msgstr "" + +#: ../Doc/library/ctypes.rst:2041 +msgid "" +"This member is either ``None`` or a dictionary containing Python objects " +"that need to be kept alive so that the memory block contents is kept valid. " +"This object is only exposed for debugging; never modify the contents of this " +"dictionary." +msgstr "" + +#: ../Doc/library/ctypes.rst:2054 +msgid "" +"This non-public class is the base class of all fundamental ctypes data " +"types. It is mentioned here because it contains the common attributes of the " +"fundamental ctypes data types. :class:`_SimpleCData` is a subclass of :" +"class:`_CData`, so it inherits their methods and attributes. ctypes data " +"types that are not and do not contain pointers can now be pickled." +msgstr "" + +#: ../Doc/library/ctypes.rst:2060 +msgid "Instances have a single attribute:" +msgstr "" + +#: ../Doc/library/ctypes.rst:2064 +msgid "" +"This attribute contains the actual value of the instance. For integer and " +"pointer types, it is an integer, for character types, it is a single " +"character bytes object or string, for character pointer types it is a Python " +"bytes object or string." +msgstr "" + +#: ../Doc/library/ctypes.rst:2069 +msgid "" +"When the ``value`` attribute is retrieved from a ctypes instance, usually a " +"new object is returned each time. :mod:`ctypes` does *not* implement " +"original object return, always a new object is constructed. The same is " +"true for all other ctypes object instances." +msgstr "" + +#: ../Doc/library/ctypes.rst:2075 +msgid "" +"Fundamental data types, when returned as foreign function call results, or, " +"for example, by retrieving structure field members or array items, are " +"transparently converted to native Python types. In other words, if a " +"foreign function has a :attr:`restype` of :class:`c_char_p`, you will always " +"receive a Python bytes object, *not* a :class:`c_char_p` instance." +msgstr "" + +#: ../Doc/library/ctypes.rst:2083 +msgid "" +"Subclasses of fundamental data types do *not* inherit this behavior. So, if " +"a foreign functions :attr:`restype` is a subclass of :class:`c_void_p`, you " +"will receive an instance of this subclass from the function call. Of course, " +"you can get the value of the pointer by accessing the ``value`` attribute." +msgstr "" + +#: ../Doc/library/ctypes.rst:2088 +msgid "These are the fundamental ctypes data types:" +msgstr "" + +#: ../Doc/library/ctypes.rst:2092 +msgid "" +"Represents the C :c:type:`signed char` datatype, and interprets the value as " +"small integer. The constructor accepts an optional integer initializer; no " +"overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2099 +msgid "" +"Represents the C :c:type:`char` datatype, and interprets the value as a " +"single character. The constructor accepts an optional string initializer, " +"the length of the string must be exactly one character." +msgstr "" + +#: ../Doc/library/ctypes.rst:2106 +msgid "" +"Represents the C :c:type:`char *` datatype when it points to a zero-" +"terminated string. For a general character pointer that may also point to " +"binary data, ``POINTER(c_char)`` must be used. The constructor accepts an " +"integer address, or a bytes object." +msgstr "" + +#: ../Doc/library/ctypes.rst:2114 +msgid "" +"Represents the C :c:type:`double` datatype. The constructor accepts an " +"optional float initializer." +msgstr "" + +#: ../Doc/library/ctypes.rst:2120 +msgid "" +"Represents the C :c:type:`long double` datatype. The constructor accepts an " +"optional float initializer. On platforms where ``sizeof(long double) == " +"sizeof(double)`` it is an alias to :class:`c_double`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2126 +msgid "" +"Represents the C :c:type:`float` datatype. The constructor accepts an " +"optional float initializer." +msgstr "" + +#: ../Doc/library/ctypes.rst:2132 +msgid "" +"Represents the C :c:type:`signed int` datatype. The constructor accepts an " +"optional integer initializer; no overflow checking is done. On platforms " +"where ``sizeof(int) == sizeof(long)`` it is an alias to :class:`c_long`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2139 +msgid "" +"Represents the C 8-bit :c:type:`signed int` datatype. Usually an alias for :" +"class:`c_byte`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2145 +msgid "" +"Represents the C 16-bit :c:type:`signed int` datatype. Usually an alias " +"for :class:`c_short`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2151 +msgid "" +"Represents the C 32-bit :c:type:`signed int` datatype. Usually an alias " +"for :class:`c_int`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2157 +msgid "" +"Represents the C 64-bit :c:type:`signed int` datatype. Usually an alias " +"for :class:`c_longlong`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2163 +msgid "" +"Represents the C :c:type:`signed long` datatype. The constructor accepts an " +"optional integer initializer; no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2169 +msgid "" +"Represents the C :c:type:`signed long long` datatype. The constructor " +"accepts an optional integer initializer; no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2175 +msgid "" +"Represents the C :c:type:`signed short` datatype. The constructor accepts " +"an optional integer initializer; no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2181 +msgid "Represents the C :c:type:`size_t` datatype." +msgstr "" + +#: ../Doc/library/ctypes.rst:2186 +msgid "Represents the C :c:type:`ssize_t` datatype." +msgstr "" + +#: ../Doc/library/ctypes.rst:2193 +msgid "" +"Represents the C :c:type:`unsigned char` datatype, it interprets the value " +"as small integer. The constructor accepts an optional integer initializer; " +"no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2200 +msgid "" +"Represents the C :c:type:`unsigned int` datatype. The constructor accepts " +"an optional integer initializer; no overflow checking is done. On platforms " +"where ``sizeof(int) == sizeof(long)`` it is an alias for :class:`c_ulong`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2207 +msgid "" +"Represents the C 8-bit :c:type:`unsigned int` datatype. Usually an alias " +"for :class:`c_ubyte`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2213 +msgid "" +"Represents the C 16-bit :c:type:`unsigned int` datatype. Usually an alias " +"for :class:`c_ushort`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2219 +msgid "" +"Represents the C 32-bit :c:type:`unsigned int` datatype. Usually an alias " +"for :class:`c_uint`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2225 +msgid "" +"Represents the C 64-bit :c:type:`unsigned int` datatype. Usually an alias " +"for :class:`c_ulonglong`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2231 +msgid "" +"Represents the C :c:type:`unsigned long` datatype. The constructor accepts " +"an optional integer initializer; no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2237 +msgid "" +"Represents the C :c:type:`unsigned long long` datatype. The constructor " +"accepts an optional integer initializer; no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2243 +msgid "" +"Represents the C :c:type:`unsigned short` datatype. The constructor accepts " +"an optional integer initializer; no overflow checking is done." +msgstr "" + +#: ../Doc/library/ctypes.rst:2249 +msgid "" +"Represents the C :c:type:`void *` type. The value is represented as " +"integer. The constructor accepts an optional integer initializer." +msgstr "" + +#: ../Doc/library/ctypes.rst:2255 +msgid "" +"Represents the C :c:type:`wchar_t` datatype, and interprets the value as a " +"single character unicode string. The constructor accepts an optional string " +"initializer, the length of the string must be exactly one character." +msgstr "" + +#: ../Doc/library/ctypes.rst:2262 +msgid "" +"Represents the C :c:type:`wchar_t *` datatype, which must be a pointer to a " +"zero-terminated wide character string. The constructor accepts an integer " +"address, or a string." +msgstr "" + +#: ../Doc/library/ctypes.rst:2269 +msgid "" +"Represent the C :c:type:`bool` datatype (more accurately, :c:type:`_Bool` " +"from C99). Its value can be ``True`` or ``False``, and the constructor " +"accepts any object that has a truth value." +msgstr "" + +#: ../Doc/library/ctypes.rst:2276 +msgid "" +"Windows only: Represents a :c:type:`HRESULT` value, which contains success " +"or error information for a function or method call." +msgstr "" + +#: ../Doc/library/ctypes.rst:2282 +msgid "" +"Represents the C :c:type:`PyObject *` datatype. Calling this without an " +"argument creates a ``NULL`` :c:type:`PyObject *` pointer." +msgstr "" + +#: ../Doc/library/ctypes.rst:2285 +msgid "" +"The :mod:`ctypes.wintypes` module provides quite some other Windows specific " +"data types, for example :c:type:`HWND`, :c:type:`WPARAM`, or :c:type:" +"`DWORD`. Some useful structures like :c:type:`MSG` or :c:type:`RECT` are " +"also defined." +msgstr "" + +#: ../Doc/library/ctypes.rst:2293 +msgid "Structured data types" +msgstr "" + +#: ../Doc/library/ctypes.rst:2298 +msgid "Abstract base class for unions in native byte order." +msgstr "" + +#: ../Doc/library/ctypes.rst:2303 +msgid "Abstract base class for structures in *big endian* byte order." +msgstr "" + +#: ../Doc/library/ctypes.rst:2308 +msgid "Abstract base class for structures in *little endian* byte order." +msgstr "" + +#: ../Doc/library/ctypes.rst:2310 +msgid "" +"Structures with non-native byte order cannot contain pointer type fields, or " +"any other data types containing pointer type fields." +msgstr "" + +#: ../Doc/library/ctypes.rst:2316 +msgid "Abstract base class for structures in *native* byte order." +msgstr "" + +#: ../Doc/library/ctypes.rst:2318 +msgid "" +"Concrete structure and union types must be created by subclassing one of " +"these types, and at least define a :attr:`_fields_` class variable. :mod:" +"`ctypes` will create :term:`descriptor`\\s which allow reading and writing " +"the fields by direct attribute accesses. These are the" +msgstr "" + +#: ../Doc/library/ctypes.rst:2326 +msgid "" +"A sequence defining the structure fields. The items must be 2-tuples or 3-" +"tuples. The first item is the name of the field, the second item specifies " +"the type of the field; it can be any ctypes data type." +msgstr "" + +#: ../Doc/library/ctypes.rst:2330 +msgid "" +"For integer type fields like :class:`c_int`, a third optional item can be " +"given. It must be a small positive integer defining the bit width of the " +"field." +msgstr "" + +#: ../Doc/library/ctypes.rst:2334 +msgid "" +"Field names must be unique within one structure or union. This is not " +"checked, only one field can be accessed when names are repeated." +msgstr "" + +#: ../Doc/library/ctypes.rst:2337 +msgid "" +"It is possible to define the :attr:`_fields_` class variable *after* the " +"class statement that defines the Structure subclass, this allows creating " +"data types that directly or indirectly reference themselves::" +msgstr "" + +#: ../Doc/library/ctypes.rst:2347 +msgid "" +"The :attr:`_fields_` class variable must, however, be defined before the " +"type is first used (an instance is created, :func:`sizeof` is called on it, " +"and so on). Later assignments to the :attr:`_fields_` class variable will " +"raise an AttributeError." +msgstr "" + +#: ../Doc/library/ctypes.rst:2352 +msgid "" +"It is possible to defined sub-subclasses of structure types, they inherit " +"the fields of the base class plus the :attr:`_fields_` defined in the sub-" +"subclass, if any." +msgstr "" + +#: ../Doc/library/ctypes.rst:2359 +msgid "" +"An optional small integer that allows overriding the alignment of structure " +"fields in the instance. :attr:`_pack_` must already be defined when :attr:" +"`_fields_` is assigned, otherwise it will have no effect." +msgstr "" + +#: ../Doc/library/ctypes.rst:2366 +msgid "" +"An optional sequence that lists the names of unnamed (anonymous) fields. :" +"attr:`_anonymous_` must be already defined when :attr:`_fields_` is " +"assigned, otherwise it will have no effect." +msgstr "" + +#: ../Doc/library/ctypes.rst:2370 +msgid "" +"The fields listed in this variable must be structure or union type fields. :" +"mod:`ctypes` will create descriptors in the structure type that allows " +"accessing the nested fields directly, without the need to create the " +"structure or union field." +msgstr "" + +#: ../Doc/library/ctypes.rst:2375 +msgid "Here is an example type (Windows)::" +msgstr "" + +#: ../Doc/library/ctypes.rst:2388 +msgid "" +"The ``TYPEDESC`` structure describes a COM data type, the ``vt`` field " +"specifies which one of the union fields is valid. Since the ``u`` field is " +"defined as anonymous field, it is now possible to access the members " +"directly off the TYPEDESC instance. ``td.lptdesc`` and ``td.u.lptdesc`` are " +"equivalent, but the former is faster since it does not need to create a " +"temporary union instance::" +msgstr "" + +#: ../Doc/library/ctypes.rst:2400 +msgid "" +"It is possible to defined sub-subclasses of structures, they inherit the " +"fields of the base class. If the subclass definition has a separate :attr:" +"`_fields_` variable, the fields specified in this are appended to the fields " +"of the base class." +msgstr "" + +#: ../Doc/library/ctypes.rst:2405 +msgid "" +"Structure and union constructors accept both positional and keyword " +"arguments. Positional arguments are used to initialize member fields in the " +"same order as they are appear in :attr:`_fields_`. Keyword arguments in the " +"constructor are interpreted as attribute assignments, so they will " +"initialize :attr:`_fields_` with the same name, or create new attributes for " +"names not present in :attr:`_fields_`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2416 +msgid "Arrays and pointers" +msgstr "" + +#: ../Doc/library/ctypes.rst:2420 +msgid "Abstract base class for arrays." +msgstr "" + +#: ../Doc/library/ctypes.rst:2422 +msgid "" +"The recommended way to create concrete array types is by multiplying any :" +"mod:`ctypes` data type with a positive integer. Alternatively, you can " +"subclass this type and define :attr:`_length_` and :attr:`_type_` class " +"variables. Array elements can be read and written using standard subscript " +"and slice accesses; for slice reads, the resulting object is *not* itself " +"an :class:`Array`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2432 +msgid "" +"A positive integer specifying the number of elements in the array. Out-of-" +"range subscripts result in an :exc:`IndexError`. Will be returned by :func:" +"`len`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2439 +msgid "Specifies the type of each element in the array." +msgstr "" + +#: ../Doc/library/ctypes.rst:2442 +msgid "" +"Array subclass constructors accept positional arguments, used to initialize " +"the elements in order." +msgstr "" + +#: ../Doc/library/ctypes.rst:2448 +msgid "Private, abstract base class for pointers." +msgstr "" + +#: ../Doc/library/ctypes.rst:2450 +msgid "" +"Concrete pointer types are created by calling :func:`POINTER` with the type " +"that will be pointed to; this is done automatically by :func:`pointer`." +msgstr "" + +#: ../Doc/library/ctypes.rst:2454 +msgid "" +"If a pointer points to an array, its elements can be read and written using " +"standard subscript and slice accesses. Pointer objects have no size, so :" +"func:`len` will raise :exc:`TypeError`. Negative subscripts will read from " +"the memory *before* the pointer (as in C), and out-of-range subscripts will " +"probably crash with an access violation (if you're lucky)." +msgstr "" + +#: ../Doc/library/ctypes.rst:2464 +msgid "Specifies the type pointed to." +msgstr "" + +#: ../Doc/library/ctypes.rst:2468 +msgid "" +"Returns the object to which to pointer points. Assigning to this attribute " +"changes the pointer to point to the assigned object." +msgstr "" + +#: ../Doc/library/curses.rst:2 +msgid ":mod:`curses` --- Terminal handling for character-cell displays" +msgstr "" + +#: ../Doc/library/curses.rst:14 +msgid "" +"The :mod:`curses` module provides an interface to the curses library, the de-" +"facto standard for portable advanced terminal handling." +msgstr "" + +#: ../Doc/library/curses.rst:17 +msgid "" +"While curses is most widely used in the Unix environment, versions are " +"available for Windows, DOS, and possibly other systems as well. This " +"extension module is designed to match the API of ncurses, an open-source " +"curses library hosted on Linux and the BSD variants of Unix." +msgstr "" + +#: ../Doc/library/curses.rst:24 +msgid "" +"Since version 5.4, the ncurses library decides how to interpret non-ASCII " +"data using the ``nl_langinfo`` function. That means that you have to call :" +"func:`locale.setlocale` in the application and encode Unicode strings using " +"one of the system's available encodings. This example uses the system's " +"default encoding::" +msgstr "" + +#: ../Doc/library/curses.rst:34 +msgid "Then use *code* as the encoding for :meth:`str.encode` calls." +msgstr "" + +#: ../Doc/library/curses.rst:39 +msgid "Module :mod:`curses.ascii`" +msgstr "" + +#: ../Doc/library/curses.rst:39 +msgid "" +"Utilities for working with ASCII characters, regardless of your locale " +"settings." +msgstr "" + +#: ../Doc/library/curses.rst:42 +msgid "Module :mod:`curses.panel`" +msgstr "" + +#: ../Doc/library/curses.rst:42 +msgid "A panel stack extension that adds depth to curses windows." +msgstr "" + +#: ../Doc/library/curses.rst:45 +msgid "Module :mod:`curses.textpad`" +msgstr "" + +#: ../Doc/library/curses.rst:45 +msgid "" +"Editable text widget for curses supporting :program:`Emacs`\\ -like " +"bindings." +msgstr "" + +#: ../Doc/library/curses.rst:49 +msgid ":ref:`curses-howto`" +msgstr "" + +#: ../Doc/library/curses.rst:48 +msgid "" +"Tutorial material on using curses with Python, by Andrew Kuchling and Eric " +"Raymond." +msgstr "" + +#: ../Doc/library/curses.rst:51 +msgid "" +"The :source:`Tools/demo/` directory in the Python source distribution " +"contains some example programs using the curses bindings provided by this " +"module." +msgstr "" + +#: ../Doc/library/curses.rst:60 +msgid "The module :mod:`curses` defines the following exception:" +msgstr "" + +#: ../Doc/library/curses.rst:65 +msgid "Exception raised when a curses library function returns an error." +msgstr "" + +#: ../Doc/library/curses.rst:69 +msgid "" +"Whenever *x* or *y* arguments to a function or a method are optional, they " +"default to the current cursor location. Whenever *attr* is optional, it " +"defaults to :const:`A_NORMAL`." +msgstr "" + +#: ../Doc/library/curses.rst:73 +msgid "The module :mod:`curses` defines the following functions:" +msgstr "" + +#: ../Doc/library/curses.rst:78 +msgid "" +"Return the output speed of the terminal in bits per second. On software " +"terminal emulators it will have a fixed high value. Included for historical " +"reasons; in former times, it was used to write output loops for time delays " +"and occasionally to change interfaces depending on the line speed." +msgstr "" + +#: ../Doc/library/curses.rst:86 +msgid "Emit a short attention sound." +msgstr "" + +#: ../Doc/library/curses.rst:91 +msgid "" +"Return ``True`` or ``False``, depending on whether the programmer can change " +"the colors displayed by the terminal." +msgstr "" + +#: ../Doc/library/curses.rst:97 +msgid "" +"Enter cbreak mode. In cbreak mode (sometimes called \"rare\" mode) normal " +"tty line buffering is turned off and characters are available to be read one " +"by one. However, unlike raw mode, special characters (interrupt, quit, " +"suspend, and flow control) retain their effects on the tty driver and " +"calling program. Calling first :func:`raw` then :func:`cbreak` leaves the " +"terminal in cbreak mode." +msgstr "" + +#: ../Doc/library/curses.rst:106 +msgid "" +"Return the intensity of the red, green, and blue (RGB) components in the " +"color *color_number*, which must be between ``0`` and :const:`COLORS`. A 3-" +"tuple is returned, containing the R,G,B values for the given color, which " +"will be between ``0`` (no component) and ``1000`` (maximum amount of " +"component)." +msgstr "" + +#: ../Doc/library/curses.rst:114 +msgid "" +"Return the attribute value for displaying text in the specified color. This " +"attribute value can be combined with :const:`A_STANDOUT`, :const:" +"`A_REVERSE`, and the other :const:`A_\\*` attributes. :func:`pair_number` " +"is the counterpart to this function." +msgstr "" + +#: ../Doc/library/curses.rst:122 +msgid "" +"Set the cursor state. *visibility* can be set to 0, 1, or 2, for invisible, " +"normal, or very visible. If the terminal supports the visibility requested, " +"the previous cursor state is returned; otherwise, an exception is raised. " +"On many terminals, the \"visible\" mode is an underline cursor and the " +"\"very visible\" mode is a block cursor." +msgstr "" + +#: ../Doc/library/curses.rst:131 +msgid "" +"Save the current terminal mode as the \"program\" mode, the mode when the " +"running program is using curses. (Its counterpart is the \"shell\" mode, " +"for when the program is not in curses.) Subsequent calls to :func:" +"`reset_prog_mode` will restore this mode." +msgstr "" + +#: ../Doc/library/curses.rst:139 +msgid "" +"Save the current terminal mode as the \"shell\" mode, the mode when the " +"running program is not using curses. (Its counterpart is the \"program\" " +"mode, when the program is using curses capabilities.) Subsequent calls to :" +"func:`reset_shell_mode` will restore this mode." +msgstr "" + +#: ../Doc/library/curses.rst:147 +msgid "Insert an *ms* millisecond pause in output." +msgstr "" + +#: ../Doc/library/curses.rst:152 +msgid "" +"Update the physical screen. The curses library keeps two data structures, " +"one representing the current physical screen contents and a virtual screen " +"representing the desired next state. The :func:`doupdate` ground updates " +"the physical screen to match the virtual screen." +msgstr "" + +#: ../Doc/library/curses.rst:157 +msgid "" +"The virtual screen may be updated by a :meth:`noutrefresh` call after write " +"operations such as :meth:`addstr` have been performed on a window. The " +"normal :meth:`refresh` call is simply :meth:`noutrefresh` followed by :func:" +"`doupdate`; if you have to update multiple windows, you can speed " +"performance and perhaps reduce screen flicker by issuing :meth:`noutrefresh` " +"calls on all windows, followed by a single :func:`doupdate`." +msgstr "" + +#: ../Doc/library/curses.rst:167 +msgid "" +"Enter echo mode. In echo mode, each character input is echoed to the screen " +"as it is entered." +msgstr "" + +#: ../Doc/library/curses.rst:173 +msgid "De-initialize the library, and return terminal to normal status." +msgstr "" + +#: ../Doc/library/curses.rst:178 +msgid "" +"Return the user's current erase character. Under Unix operating systems " +"this is a property of the controlling tty of the curses program, and is not " +"set by the curses library itself." +msgstr "" + +#: ../Doc/library/curses.rst:185 +msgid "" +"The :func:`.filter` routine, if used, must be called before :func:`initscr` " +"is called. The effect is that, during those calls, :envvar:`LINES` is set " +"to 1; the capabilities clear, cup, cud, cud1, cuu1, cuu, vpa are disabled; " +"and the home string is set to the value of cr. The effect is that the cursor " +"is confined to the current line, and so are screen updates. This may be " +"used for enabling character-at-a-time line editing without touching the " +"rest of the screen." +msgstr "" + +#: ../Doc/library/curses.rst:195 +msgid "" +"Flash the screen. That is, change it to reverse-video and then change it " +"back in a short interval. Some people prefer such as 'visible bell' to the " +"audible attention signal produced by :func:`beep`." +msgstr "" + +#: ../Doc/library/curses.rst:202 +msgid "" +"Flush all input buffers. This throws away any typeahead that has been " +"typed by the user and has not yet been processed by the program." +msgstr "" + +#: ../Doc/library/curses.rst:208 +msgid "" +"After :meth:`getch` returns :const:`KEY_MOUSE` to signal a mouse event, this " +"method should be call to retrieve the queued mouse event, represented as a 5-" +"tuple ``(id, x, y, z, bstate)``. *id* is an ID value used to distinguish " +"multiple devices, and *x*, *y*, *z* are the event's coordinates. (*z* is " +"currently unused.) *bstate* is an integer value whose bits will be set to " +"indicate the type of event, and will be the bitwise OR of one or more of the " +"following constants, where *n* is the button number from 1 to 4: :const:" +"`BUTTONn_PRESSED`, :const:`BUTTONn_RELEASED`, :const:`BUTTONn_CLICKED`, :" +"const:`BUTTONn_DOUBLE_CLICKED`, :const:`BUTTONn_TRIPLE_CLICKED`, :const:" +"`BUTTON_SHIFT`, :const:`BUTTON_CTRL`, :const:`BUTTON_ALT`." +msgstr "" + +#: ../Doc/library/curses.rst:222 +msgid "" +"Return the current coordinates of the virtual screen cursor in y and x. If " +"leaveok is currently true, then -1,-1 is returned." +msgstr "" + +#: ../Doc/library/curses.rst:228 +msgid "" +"Read window related data stored in the file by an earlier :func:`putwin` " +"call. The routine then creates and initializes a new window using that data, " +"returning the new window object." +msgstr "" + +#: ../Doc/library/curses.rst:235 +msgid "" +"Return ``True`` if the terminal can display colors; otherwise, return " +"``False``." +msgstr "" + +#: ../Doc/library/curses.rst:240 +msgid "" +"Return ``True`` if the terminal has insert- and delete-character " +"capabilities. This function is included for historical reasons only, as all " +"modern software terminal emulators have such capabilities." +msgstr "" + +#: ../Doc/library/curses.rst:247 +msgid "" +"Return ``True`` if the terminal has insert- and delete-line capabilities, or " +"can simulate them using scrolling regions. This function is included for " +"historical reasons only, as all modern software terminal emulators have such " +"capabilities." +msgstr "" + +#: ../Doc/library/curses.rst:255 +msgid "" +"Take a key value *ch*, and return ``True`` if the current terminal type " +"recognizes a key with that value." +msgstr "" + +#: ../Doc/library/curses.rst:261 +msgid "" +"Used for half-delay mode, which is similar to cbreak mode in that characters " +"typed by the user are immediately available to the program. However, after " +"blocking for *tenths* tenths of seconds, an exception is raised if nothing " +"has been typed. The value of *tenths* must be a number between ``1`` and " +"``255``. Use :func:`nocbreak` to leave half-delay mode." +msgstr "" + +#: ../Doc/library/curses.rst:270 +msgid "" +"Change the definition of a color, taking the number of the color to be " +"changed followed by three RGB values (for the amounts of red, green, and " +"blue components). The value of *color_number* must be between ``0`` and :" +"const:`COLORS`. Each of *r*, *g*, *b*, must be a value between ``0`` and " +"``1000``. When :func:`init_color` is used, all occurrences of that color on " +"the screen immediately change to the new definition. This function is a no-" +"op on most terminals; it is active only if :func:`can_change_color` returns " +"``1``." +msgstr "" + +#: ../Doc/library/curses.rst:281 +msgid "" +"Change the definition of a color-pair. It takes three arguments: the number " +"of the color-pair to be changed, the foreground color number, and the " +"background color number. The value of *pair_number* must be between ``1`` " +"and ``COLOR_PAIRS - 1`` (the ``0`` color pair is wired to white on black and " +"cannot be changed). The value of *fg* and *bg* arguments must be between " +"``0`` and :const:`COLORS`. If the color-pair was previously initialized, " +"the screen is refreshed and all occurrences of that color-pair are changed " +"to the new definition." +msgstr "" + +#: ../Doc/library/curses.rst:293 +msgid "" +"Initialize the library. Return a :class:`WindowObject` which represents the " +"whole screen." +msgstr "" + +#: ../Doc/library/curses.rst:298 +msgid "" +"If there is an error opening the terminal, the underlying curses library may " +"cause the interpreter to exit." +msgstr "" + +#: ../Doc/library/curses.rst:304 +msgid "" +"Return ``True`` if :func:`resize_term` would modify the window structure, " +"``False`` otherwise." +msgstr "" + +#: ../Doc/library/curses.rst:310 +msgid "" +"Return ``True`` if :func:`endwin` has been called (that is, the curses " +"library has been deinitialized)." +msgstr "" + +#: ../Doc/library/curses.rst:316 +msgid "" +"Return the name of the key numbered *k*. The name of a key generating " +"printable ASCII character is the key's character. The name of a control-key " +"combination is a two-character string consisting of a caret followed by the " +"corresponding printable ASCII character. The name of an alt-key combination " +"(128-255) is a string consisting of the prefix 'M-' followed by the name of " +"the corresponding ASCII character." +msgstr "" + +#: ../Doc/library/curses.rst:326 +msgid "" +"Return the user's current line kill character. Under Unix operating systems " +"this is a property of the controlling tty of the curses program, and is not " +"set by the curses library itself." +msgstr "" + +#: ../Doc/library/curses.rst:333 +msgid "" +"Return a string containing the terminfo long name field describing the " +"current terminal. The maximum length of a verbose description is 128 " +"characters. It is defined only after the call to :func:`initscr`." +msgstr "" + +#: ../Doc/library/curses.rst:340 +msgid "" +"If *yes* is 1, allow 8-bit characters to be input. If *yes* is 0, allow " +"only 7-bit chars." +msgstr "" + +#: ../Doc/library/curses.rst:346 +msgid "" +"Set the maximum time in milliseconds that can elapse between press and " +"release events in order for them to be recognized as a click, and return the " +"previous interval value. The default value is 200 msec, or one fifth of a " +"second." +msgstr "" + +#: ../Doc/library/curses.rst:353 +msgid "" +"Set the mouse events to be reported, and return a tuple ``(availmask, " +"oldmask)``. *availmask* indicates which of the specified mouse events can " +"be reported; on complete failure it returns 0. *oldmask* is the previous " +"value of the given window's mouse event mask. If this function is never " +"called, no mouse events are ever reported." +msgstr "" + +#: ../Doc/library/curses.rst:362 +msgid "Sleep for *ms* milliseconds." +msgstr "" + +#: ../Doc/library/curses.rst:367 +msgid "" +"Create and return a pointer to a new pad data structure with the given " +"number of lines and columns. A pad is returned as a window object." +msgstr "" + +#: ../Doc/library/curses.rst:370 +msgid "" +"A pad is like a window, except that it is not restricted by the screen size, " +"and is not necessarily associated with a particular part of the screen. " +"Pads can be used when a large window is needed, and only a part of the " +"window will be on the screen at one time. Automatic refreshes of pads (such " +"as from scrolling or echoing of input) do not occur. The :meth:`refresh` " +"and :meth:`noutrefresh` methods of a pad require 6 arguments to specify the " +"part of the pad to be displayed and the location on the screen to be used " +"for the display. The arguments are *pminrow*, *pmincol*, *sminrow*, " +"*smincol*, *smaxrow*, *smaxcol*; the *p* arguments refer to the upper left " +"corner of the pad region to be displayed and the *s* arguments define a " +"clipping box on the screen within which the pad region is to be displayed." +msgstr "" + +#: ../Doc/library/curses.rst:386 +msgid "" +"Return a new window, whose left-upper corner is at ``(begin_y, begin_x)``, " +"and whose height/width is *nlines*/*ncols*." +msgstr "" + +#: ../Doc/library/curses.rst:389 +msgid "" +"By default, the window will extend from the specified position to the lower " +"right corner of the screen." +msgstr "" + +#: ../Doc/library/curses.rst:395 +msgid "" +"Enter newline mode. This mode translates the return key into newline on " +"input, and translates newline into return and line-feed on output. Newline " +"mode is initially on." +msgstr "" + +#: ../Doc/library/curses.rst:402 +msgid "" +"Leave cbreak mode. Return to normal \"cooked\" mode with line buffering." +msgstr "" + +#: ../Doc/library/curses.rst:407 +msgid "Leave echo mode. Echoing of input characters is turned off." +msgstr "" + +#: ../Doc/library/curses.rst:412 +msgid "" +"Leave newline mode. Disable translation of return into newline on input, " +"and disable low-level translation of newline into newline/return on output " +"(but this does not change the behavior of ``addch('\\n')``, which always " +"does the equivalent of return and line feed on the virtual screen). With " +"translation off, curses can sometimes speed up vertical motion a little; " +"also, it will be able to detect the return key on input." +msgstr "" + +#: ../Doc/library/curses.rst:422 +msgid "" +"When the :func:`noqiflush` routine is used, normal flush of input and output " +"queues associated with the INTR, QUIT and SUSP characters will not be done. " +"You may want to call :func:`noqiflush` in a signal handler if you want " +"output to continue as though the interrupt had not occurred, after the " +"handler exits." +msgstr "" + +#: ../Doc/library/curses.rst:430 +msgid "Leave raw mode. Return to normal \"cooked\" mode with line buffering." +msgstr "" + +#: ../Doc/library/curses.rst:435 +msgid "" +"Return a tuple ``(fg, bg)`` containing the colors for the requested color " +"pair. The value of *pair_number* must be between ``1`` and ``COLOR_PAIRS - " +"1``." +msgstr "" + +#: ../Doc/library/curses.rst:441 +msgid "" +"Return the number of the color-pair set by the attribute value *attr*. :func:" +"`color_pair` is the counterpart to this function." +msgstr "" + +#: ../Doc/library/curses.rst:447 +msgid "" +"Equivalent to ``tputs(str, 1, putchar)``; emit the value of a specified " +"terminfo capability for the current terminal. Note that the output of :func:" +"`putp` always goes to standard output." +msgstr "" + +#: ../Doc/library/curses.rst:454 +msgid "" +"If *flag* is ``False``, the effect is the same as calling :func:`noqiflush`. " +"If *flag* is ``True``, or no argument is provided, the queues will be " +"flushed when these control characters are read." +msgstr "" + +#: ../Doc/library/curses.rst:461 +msgid "" +"Enter raw mode. In raw mode, normal line buffering and processing of " +"interrupt, quit, suspend, and flow control keys are turned off; characters " +"are presented to curses input functions one by one." +msgstr "" + +#: ../Doc/library/curses.rst:468 +msgid "" +"Restore the terminal to \"program\" mode, as previously saved by :func:" +"`def_prog_mode`." +msgstr "" + +#: ../Doc/library/curses.rst:474 +msgid "" +"Restore the terminal to \"shell\" mode, as previously saved by :func:" +"`def_shell_mode`." +msgstr "" + +#: ../Doc/library/curses.rst:480 +msgid "" +"Restore the state of the terminal modes to what it was at the last call to :" +"func:`savetty`." +msgstr "" + +#: ../Doc/library/curses.rst:486 +msgid "" +"Backend function used by :func:`resizeterm`, performing most of the work; " +"when resizing the windows, :func:`resize_term` blank-fills the areas that " +"are extended. The calling application should fill in these areas with " +"appropriate data. The :func:`resize_term` function attempts to resize all " +"windows. However, due to the calling convention of pads, it is not possible " +"to resize these without additional interaction with the application." +msgstr "" + +#: ../Doc/library/curses.rst:496 +msgid "" +"Resize the standard and current windows to the specified dimensions, and " +"adjusts other bookkeeping data used by the curses library that record the " +"window dimensions (in particular the SIGWINCH handler)." +msgstr "" + +#: ../Doc/library/curses.rst:503 +msgid "" +"Save the current state of the terminal modes in a buffer, usable by :func:" +"`resetty`." +msgstr "" + +#: ../Doc/library/curses.rst:509 +msgid "" +"Set the virtual screen cursor to *y*, *x*. If *y* and *x* are both -1, then " +"leaveok is set." +msgstr "" + +#: ../Doc/library/curses.rst:515 +msgid "" +"Initialize the terminal. *termstr* is a string giving the terminal name; if " +"omitted, the value of the :envvar:`TERM` environment variable will be used. " +"*fd* is the file descriptor to which any initialization sequences will be " +"sent; if not supplied, the file descriptor for ``sys.stdout`` will be used." +msgstr "" + +#: ../Doc/library/curses.rst:523 +msgid "" +"Must be called if the programmer wants to use colors, and before any other " +"color manipulation routine is called. It is good practice to call this " +"routine right after :func:`initscr`." +msgstr "" + +#: ../Doc/library/curses.rst:527 +msgid "" +":func:`start_color` initializes eight basic colors (black, red, green, " +"yellow, blue, magenta, cyan, and white), and two global variables in the :" +"mod:`curses` module, :const:`COLORS` and :const:`COLOR_PAIRS`, containing " +"the maximum number of colors and color-pairs the terminal can support. It " +"also restores the colors on the terminal to the values they had when the " +"terminal was just turned on." +msgstr "" + +#: ../Doc/library/curses.rst:536 +msgid "" +"Return a logical OR of all video attributes supported by the terminal. This " +"information is useful when a curses program needs complete control over the " +"appearance of the screen." +msgstr "" + +#: ../Doc/library/curses.rst:543 +msgid "" +"Return the value of the environment variable :envvar:`TERM`, truncated to 14 " +"characters." +msgstr "" + +#: ../Doc/library/curses.rst:548 +msgid "" +"Return the value of the Boolean capability corresponding to the terminfo " +"capability name *capname*. The value ``-1`` is returned if *capname* is not " +"a Boolean capability, or ``0`` if it is canceled or absent from the terminal " +"description." +msgstr "" + +#: ../Doc/library/curses.rst:556 +msgid "" +"Return the value of the numeric capability corresponding to the terminfo " +"capability name *capname*. The value ``-2`` is returned if *capname* is not " +"a numeric capability, or ``-1`` if it is canceled or absent from the " +"terminal description." +msgstr "" + +#: ../Doc/library/curses.rst:564 +msgid "" +"Return the value of the string capability corresponding to the terminfo " +"capability name *capname*. ``None`` is returned if *capname* is not a " +"string capability, or is canceled or absent from the terminal description." +msgstr "" + +#: ../Doc/library/curses.rst:571 +msgid "" +"Instantiate the string *str* with the supplied parameters, where *str* " +"should be a parameterized string obtained from the terminfo database. E.g. " +"``tparm(tigetstr(\"cup\"), 5, 3)`` could result in ``b'\\033[6;4H'``, the " +"exact result depending on terminal type." +msgstr "" + +#: ../Doc/library/curses.rst:579 +msgid "" +"Specify that the file descriptor *fd* be used for typeahead checking. If " +"*fd* is ``-1``, then no typeahead checking is done." +msgstr "" + +#: ../Doc/library/curses.rst:582 +msgid "" +"The curses library does \"line-breakout optimization\" by looking for " +"typeahead periodically while updating the screen. If input is found, and it " +"is coming from a tty, the current update is postponed until refresh or " +"doupdate is called again, allowing faster response to commands typed in " +"advance. This function allows specifying a different file descriptor for " +"typeahead checking." +msgstr "" + +#: ../Doc/library/curses.rst:591 +msgid "" +"Return a string which is a printable representation of the character *ch*. " +"Control characters are displayed as a caret followed by the character, for " +"example as ``^C``. Printing characters are left as they are." +msgstr "" + +#: ../Doc/library/curses.rst:598 +msgid "Push *ch* so the next :meth:`getch` will return it." +msgstr "" + +#: ../Doc/library/curses.rst:602 +msgid "Only one *ch* can be pushed before :meth:`getch` is called." +msgstr "" + +#: ../Doc/library/curses.rst:607 +msgid "" +"Update :envvar:`LINES` and :envvar:`COLS`. Useful for detecting manual " +"screen resize." +msgstr "" + +#: ../Doc/library/curses.rst:614 +msgid "Push *ch* so the next :meth:`get_wch` will return it." +msgstr "" + +#: ../Doc/library/curses.rst:618 +msgid "Only one *ch* can be pushed before :meth:`get_wch` is called." +msgstr "" + +#: ../Doc/library/curses.rst:625 +msgid "" +"Push a :const:`KEY_MOUSE` event onto the input queue, associating the given " +"state data with it." +msgstr "" + +#: ../Doc/library/curses.rst:631 +msgid "" +"If used, this function should be called before :func:`initscr` or newterm " +"are called. When *flag* is ``False``, the values of lines and columns " +"specified in the terminfo database will be used, even if environment " +"variables :envvar:`LINES` and :envvar:`COLUMNS` (used by default) are set, " +"or if curses is running in a window (in which case default behavior would be " +"to use the window size if :envvar:`LINES` and :envvar:`COLUMNS` are not set)." +msgstr "" + +#: ../Doc/library/curses.rst:641 +msgid "" +"Allow use of default values for colors on terminals supporting this feature. " +"Use this to support transparency in your application. The default color is " +"assigned to the color number -1. After calling this function, " +"``init_pair(x, curses.COLOR_RED, -1)`` initializes, for instance, color pair " +"*x* to a red foreground color on the default background." +msgstr "" + +#: ../Doc/library/curses.rst:650 +msgid "" +"Initialize curses and call another callable object, *func*, which should be " +"the rest of your curses-using application. If the application raises an " +"exception, this function will restore the terminal to a sane state before re-" +"raising the exception and generating a traceback. The callable object " +"*func* is then passed the main window 'stdscr' as its first argument, " +"followed by any other arguments passed to :func:`wrapper`. Before calling " +"*func*, :func:`wrapper` turns on cbreak mode, turns off echo, enables the " +"terminal keypad, and initializes colors if the terminal has color support. " +"On exit (whether normally or by exception) it restores cooked mode, turns on " +"echo, and disables the terminal keypad." +msgstr "" + +#: ../Doc/library/curses.rst:664 +msgid "Window Objects" +msgstr "" + +#: ../Doc/library/curses.rst:666 +msgid "" +"Window objects, as returned by :func:`initscr` and :func:`newwin` above, " +"have the following methods and attributes:" +msgstr "" + +#: ../Doc/library/curses.rst:675 +msgid "" +"A *character* means a C character (an ASCII code), rather than a Python " +"character (a string of length 1). (This note is true whenever the " +"documentation mentions a character.) The built-in :func:`ord` is handy for " +"conveying strings to codes." +msgstr "" + +#: ../Doc/library/curses.rst:680 +msgid "" +"Paint character *ch* at ``(y, x)`` with attributes *attr*, overwriting any " +"character previously painter at that location. By default, the character " +"position and attributes are the current settings for the window object." +msgstr "" + +#: ../Doc/library/curses.rst:688 +msgid "" +"Paint at most *n* characters of the string *str* at ``(y, x)`` with " +"attributes *attr*, overwriting anything previously on the display." +msgstr "" + +#: ../Doc/library/curses.rst:695 +msgid "" +"Paint the string *str* at ``(y, x)`` with attributes *attr*, overwriting " +"anything previously on the display." +msgstr "" + +#: ../Doc/library/curses.rst:701 +msgid "" +"Remove attribute *attr* from the \"background\" set applied to all writes to " +"the current window." +msgstr "" + +#: ../Doc/library/curses.rst:707 +msgid "" +"Add attribute *attr* from the \"background\" set applied to all writes to " +"the current window." +msgstr "" + +#: ../Doc/library/curses.rst:713 +msgid "" +"Set the \"background\" set of attributes to *attr*. This set is initially 0 " +"(no attributes)." +msgstr "" + +#: ../Doc/library/curses.rst:719 +msgid "" +"Set the background property of the window to the character *ch*, with " +"attributes *attr*. The change is then applied to every character position " +"in that window:" +msgstr "" + +#: ../Doc/library/curses.rst:723 +msgid "" +"The attribute of every character in the window is changed to the new " +"background attribute." +msgstr "" + +#: ../Doc/library/curses.rst:726 +msgid "" +"Wherever the former background character appears, it is changed to the new " +"background character." +msgstr "" + +#: ../Doc/library/curses.rst:732 +msgid "" +"Set the window's background. A window's background consists of a character " +"and any combination of attributes. The attribute part of the background is " +"combined (OR'ed) with all non-blank characters that are written into the " +"window. Both the character and attribute parts of the background are " +"combined with the blank characters. The background becomes a property of " +"the character and moves with the character through any scrolling and insert/" +"delete line/character operations." +msgstr "" + +#: ../Doc/library/curses.rst:742 +msgid "" +"Draw a border around the edges of the window. Each parameter specifies the " +"character to use for a specific part of the border; see the table below for " +"more details. The characters can be specified as integers or as one-" +"character strings." +msgstr "" + +#: ../Doc/library/curses.rst:749 +msgid "" +"A ``0`` value for any parameter will cause the default character to be used " +"for that parameter. Keyword parameters can *not* be used. The defaults are " +"listed in this table:" +msgstr "" + +#: ../Doc/library/curses.rst:754 +msgid "Parameter" +msgstr "" + +#: ../Doc/library/curses.rst:754 +msgid "Default value" +msgstr "" + +#: ../Doc/library/curses.rst:756 +msgid "*ls*" +msgstr "" + +#: ../Doc/library/curses.rst:756 +msgid "Left side" +msgstr "" + +#: ../Doc/library/curses.rst:756 ../Doc/library/curses.rst:758 +msgid ":const:`ACS_VLINE`" +msgstr "" + +#: ../Doc/library/curses.rst:758 +msgid "*rs*" +msgstr "" + +#: ../Doc/library/curses.rst:758 +msgid "Right side" +msgstr "" + +#: ../Doc/library/curses.rst:760 +msgid "*ts*" +msgstr "" + +#: ../Doc/library/curses.rst:760 +msgid "Top" +msgstr "" + +#: ../Doc/library/curses.rst:760 ../Doc/library/curses.rst:762 +msgid ":const:`ACS_HLINE`" +msgstr "" + +#: ../Doc/library/curses.rst:762 +msgid "*bs*" +msgstr "" + +#: ../Doc/library/curses.rst:762 +msgid "Bottom" +msgstr "" + +#: ../Doc/library/curses.rst:764 +msgid "*tl*" +msgstr "" + +#: ../Doc/library/curses.rst:764 +msgid "Upper-left corner" +msgstr "" + +#: ../Doc/library/curses.rst:764 +msgid ":const:`ACS_ULCORNER`" +msgstr "" + +#: ../Doc/library/curses.rst:766 +msgid "*tr*" +msgstr "" + +#: ../Doc/library/curses.rst:766 +msgid "Upper-right corner" +msgstr "" + +#: ../Doc/library/curses.rst:766 +msgid ":const:`ACS_URCORNER`" +msgstr "" + +#: ../Doc/library/curses.rst:768 +msgid "*bl*" +msgstr "" + +#: ../Doc/library/curses.rst:768 +msgid "Bottom-left corner" +msgstr "" + +#: ../Doc/library/curses.rst:768 +msgid ":const:`ACS_LLCORNER`" +msgstr "" + +#: ../Doc/library/curses.rst:770 +msgid "*br*" +msgstr "" + +#: ../Doc/library/curses.rst:770 +msgid "Bottom-right corner" +msgstr "" + +#: ../Doc/library/curses.rst:770 +msgid ":const:`ACS_LRCORNER`" +msgstr "" + +#: ../Doc/library/curses.rst:776 +msgid "" +"Similar to :meth:`border`, but both *ls* and *rs* are *vertch* and both *ts* " +"and *bs* are *horch*. The default corner characters are always used by this " +"function." +msgstr "" + +#: ../Doc/library/curses.rst:785 +msgid "" +"Set the attributes of *num* characters at the current cursor position, or at " +"position ``(y, x)`` if supplied. If no value of *num* is given or *num* = " +"-1, the attribute will be set on all the characters to the end of the " +"line. This function does not move the cursor. The changed line will be " +"touched using the :meth:`touchline` method so that the contents will be " +"redisplayed by the next window refresh." +msgstr "" + +#: ../Doc/library/curses.rst:795 +msgid "" +"Like :meth:`erase`, but also cause the whole window to be repainted upon " +"next call to :meth:`refresh`." +msgstr "" + +#: ../Doc/library/curses.rst:801 +msgid "" +"If *yes* is 1, the next call to :meth:`refresh` will clear the window " +"completely." +msgstr "" + +#: ../Doc/library/curses.rst:807 +msgid "" +"Erase from cursor to the end of the window: all lines below the cursor are " +"deleted, and then the equivalent of :meth:`clrtoeol` is performed." +msgstr "" + +#: ../Doc/library/curses.rst:813 +msgid "Erase from cursor to the end of the line." +msgstr "" + +#: ../Doc/library/curses.rst:818 +msgid "" +"Update the current cursor position of all the ancestors of the window to " +"reflect the current cursor position of the window." +msgstr "" + +#: ../Doc/library/curses.rst:824 +msgid "Delete any character at ``(y, x)``." +msgstr "" + +#: ../Doc/library/curses.rst:829 +msgid "" +"Delete the line under the cursor. All following lines are moved up by one " +"line." +msgstr "" + +#: ../Doc/library/curses.rst:835 +msgid "" +"An abbreviation for \"derive window\", :meth:`derwin` is the same as " +"calling :meth:`subwin`, except that *begin_y* and *begin_x* are relative to " +"the origin of the window, rather than relative to the entire screen. Return " +"a window object for the derived window." +msgstr "" + +#: ../Doc/library/curses.rst:843 +msgid "" +"Add character *ch* with attribute *attr*, and immediately call :meth:" +"`refresh` on the window." +msgstr "" + +#: ../Doc/library/curses.rst:849 +msgid "" +"Test whether the given pair of screen-relative character-cell coordinates " +"are enclosed by the given window, returning ``True`` or ``False``. It is " +"useful for determining what subset of the screen windows enclose the " +"location of a mouse event." +msgstr "" + +#: ../Doc/library/curses.rst:857 +msgid "" +"Encoding used to encode method arguments (Unicode strings and characters). " +"The encoding attribute is inherited from the parent window when a subwindow " +"is created, for example with :meth:`window.subwin`. By default, the locale " +"encoding is used (see :func:`locale.getpreferredencoding`)." +msgstr "" + +#: ../Doc/library/curses.rst:867 +msgid "Clear the window." +msgstr "" + +#: ../Doc/library/curses.rst:872 +msgid "Return a tuple ``(y, x)`` of co-ordinates of upper-left corner." +msgstr "" + +#: ../Doc/library/curses.rst:877 +msgid "Return the given window's current background character/attribute pair." +msgstr "" + +#: ../Doc/library/curses.rst:882 +msgid "" +"Get a character. Note that the integer returned does *not* have to be in " +"ASCII range: function keys, keypad keys and so on return numbers higher than " +"256. In no-delay mode, -1 is returned if there is no input, else :func:" +"`getch` waits until a key is pressed." +msgstr "" + +#: ../Doc/library/curses.rst:890 +msgid "" +"Get a wide character. Return a character for most keys, or an integer for " +"function keys, keypad keys, and other special keys." +msgstr "" + +#: ../Doc/library/curses.rst:898 +msgid "" +"Get a character, returning a string instead of an integer, as :meth:`getch` " +"does. Function keys, keypad keys and other special keys return a multibyte " +"string containing the key name. In no-delay mode, an exception is raised if " +"there is no input." +msgstr "" + +#: ../Doc/library/curses.rst:906 +msgid "Return a tuple ``(y, x)`` of the height and width of the window." +msgstr "" + +#: ../Doc/library/curses.rst:911 +msgid "" +"Return the beginning coordinates of this window relative to its parent " +"window into two integer variables y and x. Return ``-1, -1`` if this window " +"has no parent." +msgstr "" + +#: ../Doc/library/curses.rst:918 +msgid "Read a string from the user, with primitive line editing capacity." +msgstr "" + +#: ../Doc/library/curses.rst:923 +msgid "" +"Return a tuple ``(y, x)`` of current cursor position relative to the " +"window's upper-left corner." +msgstr "" + +#: ../Doc/library/curses.rst:930 +msgid "" +"Display a horizontal line starting at ``(y, x)`` with length *n* consisting " +"of the character *ch*." +msgstr "" + +#: ../Doc/library/curses.rst:936 +msgid "" +"If *flag* is ``False``, curses no longer considers using the hardware insert/" +"delete character feature of the terminal; if *flag* is ``True``, use of " +"character insertion and deletion is enabled. When curses is first " +"initialized, use of character insert/delete is enabled by default." +msgstr "" + +#: ../Doc/library/curses.rst:944 +msgid "" +"If called with *yes* equal to 1, :mod:`curses` will try and use hardware " +"line editing facilities. Otherwise, line insertion/deletion are disabled." +msgstr "" + +#: ../Doc/library/curses.rst:950 +msgid "" +"If *flag* is ``True``, any change in the window image automatically causes " +"the window to be refreshed; you no longer have to call :meth:`refresh` " +"yourself. However, it may degrade performance considerably, due to repeated " +"calls to wrefresh. This option is disabled by default." +msgstr "" + +#: ../Doc/library/curses.rst:958 +msgid "" +"Return the character at the given position in the window. The bottom 8 bits " +"are the character proper, and upper bits are the attributes." +msgstr "" + +#: ../Doc/library/curses.rst:965 +msgid "" +"Paint character *ch* at ``(y, x)`` with attributes *attr*, moving the line " +"from position *x* right by one character." +msgstr "" + +#: ../Doc/library/curses.rst:971 +msgid "" +"Insert *nlines* lines into the specified window above the current line. The " +"*nlines* bottom lines are lost. For negative *nlines*, delete *nlines* " +"lines starting with the one under the cursor, and move the remaining lines " +"up. The bottom *nlines* lines are cleared. The current cursor position " +"remains the same." +msgstr "" + +#: ../Doc/library/curses.rst:980 +msgid "" +"Insert a blank line under the cursor. All following lines are moved down by " +"one line." +msgstr "" + +#: ../Doc/library/curses.rst:987 +msgid "" +"Insert a character string (as many characters as will fit on the line) " +"before the character under the cursor, up to *n* characters. If *n* is " +"zero or negative, the entire string is inserted. All characters to the right " +"of the cursor are shifted right, with the rightmost characters on the line " +"being lost. The cursor position does not change (after moving to *y*, *x*, " +"if specified)." +msgstr "" + +#: ../Doc/library/curses.rst:997 +msgid "" +"Insert a character string (as many characters as will fit on the line) " +"before the character under the cursor. All characters to the right of the " +"cursor are shifted right, with the rightmost characters on the line being " +"lost. The cursor position does not change (after moving to *y*, *x*, if " +"specified)." +msgstr "" + +#: ../Doc/library/curses.rst:1006 +msgid "" +"Return a string of characters, extracted from the window starting at the " +"current cursor position, or at *y*, *x* if specified. Attributes are " +"stripped from the characters. If *n* is specified, :meth:`instr` returns a " +"string at most *n* characters long (exclusive of the trailing NUL)." +msgstr "" + +#: ../Doc/library/curses.rst:1014 +msgid "" +"Return ``True`` if the specified line was modified since the last call to :" +"meth:`refresh`; otherwise return ``False``. Raise a :exc:`curses.error` " +"exception if *line* is not valid for the given window." +msgstr "" + +#: ../Doc/library/curses.rst:1021 +msgid "" +"Return ``True`` if the specified window was modified since the last call to :" +"meth:`refresh`; otherwise return ``False``." +msgstr "" + +#: ../Doc/library/curses.rst:1027 +msgid "" +"If *yes* is 1, escape sequences generated by some keys (keypad, function " +"keys) will be interpreted by :mod:`curses`. If *yes* is 0, escape sequences " +"will be left as is in the input stream." +msgstr "" + +#: ../Doc/library/curses.rst:1034 +msgid "" +"If *yes* is 1, cursor is left where it is on update, instead of being at " +"\"cursor position.\" This reduces cursor movement where possible. If " +"possible the cursor will be made invisible." +msgstr "" + +#: ../Doc/library/curses.rst:1038 +msgid "" +"If *yes* is 0, cursor will always be at \"cursor position\" after an update." +msgstr "" + +#: ../Doc/library/curses.rst:1043 +msgid "Move cursor to ``(new_y, new_x)``." +msgstr "" + +#: ../Doc/library/curses.rst:1048 +msgid "" +"Move the window inside its parent window. The screen-relative parameters of " +"the window are not changed. This routine is used to display different parts " +"of the parent window at the same physical position on the screen." +msgstr "" + +#: ../Doc/library/curses.rst:1055 +msgid "Move the window so its upper-left corner is at ``(new_y, new_x)``." +msgstr "" + +#: ../Doc/library/curses.rst:1060 +msgid "If *yes* is ``1``, :meth:`getch` will be non-blocking." +msgstr "" + +#: ../Doc/library/curses.rst:1065 +msgid "If *yes* is ``1``, escape sequences will not be timed out." +msgstr "" + +#: ../Doc/library/curses.rst:1067 +msgid "" +"If *yes* is ``0``, after a few milliseconds, an escape sequence will not be " +"interpreted, and will be left in the input stream as is." +msgstr "" + +#: ../Doc/library/curses.rst:1073 +msgid "" +"Mark for refresh but wait. This function updates the data structure " +"representing the desired state of the window, but does not force an update " +"of the physical screen. To accomplish that, call :func:`doupdate`." +msgstr "" + +#: ../Doc/library/curses.rst:1080 +msgid "" +"Overlay the window on top of *destwin*. The windows need not be the same " +"size, only the overlapping region is copied. This copy is non-destructive, " +"which means that the current background character does not overwrite the old " +"contents of *destwin*." +msgstr "" + +#: ../Doc/library/curses.rst:1085 +msgid "" +"To get fine-grained control over the copied region, the second form of :meth:" +"`overlay` can be used. *sminrow* and *smincol* are the upper-left " +"coordinates of the source window, and the other variables mark a rectangle " +"in the destination window." +msgstr "" + +#: ../Doc/library/curses.rst:1093 +msgid "" +"Overwrite the window on top of *destwin*. The windows need not be the same " +"size, in which case only the overlapping region is copied. This copy is " +"destructive, which means that the current background character overwrites " +"the old contents of *destwin*." +msgstr "" + +#: ../Doc/library/curses.rst:1098 +msgid "" +"To get fine-grained control over the copied region, the second form of :meth:" +"`overwrite` can be used. *sminrow* and *smincol* are the upper-left " +"coordinates of the source window, the other variables mark a rectangle in " +"the destination window." +msgstr "" + +#: ../Doc/library/curses.rst:1106 +msgid "" +"Write all data associated with the window into the provided file object. " +"This information can be later retrieved using the :func:`getwin` function." +msgstr "" + +#: ../Doc/library/curses.rst:1112 +msgid "" +"Indicate that the *num* screen lines, starting at line *beg*, are corrupted " +"and should be completely redrawn on the next :meth:`refresh` call." +msgstr "" + +#: ../Doc/library/curses.rst:1118 +msgid "" +"Touch the entire window, causing it to be completely redrawn on the next :" +"meth:`refresh` call." +msgstr "" + +#: ../Doc/library/curses.rst:1124 +msgid "" +"Update the display immediately (sync actual screen with previous drawing/" +"deleting methods)." +msgstr "" + +#: ../Doc/library/curses.rst:1127 +msgid "" +"The 6 optional arguments can only be specified when the window is a pad " +"created with :func:`newpad`. The additional parameters are needed to " +"indicate what part of the pad and screen are involved. *pminrow* and " +"*pmincol* specify the upper left-hand corner of the rectangle to be " +"displayed in the pad. *sminrow*, *smincol*, *smaxrow*, and *smaxcol* " +"specify the edges of the rectangle to be displayed on the screen. The lower " +"right-hand corner of the rectangle to be displayed in the pad is calculated " +"from the screen coordinates, since the rectangles must be the same size. " +"Both rectangles must be entirely contained within their respective " +"structures. Negative values of *pminrow*, *pmincol*, *sminrow*, or " +"*smincol* are treated as if they were zero." +msgstr "" + +#: ../Doc/library/curses.rst:1141 +msgid "" +"Reallocate storage for a curses window to adjust its dimensions to the " +"specified values. If either dimension is larger than the current values, " +"the window's data is filled with blanks that have the current background " +"rendition (as set by :meth:`bkgdset`) merged into them." +msgstr "" + +#: ../Doc/library/curses.rst:1149 +msgid "Scroll the screen or scrolling region upward by *lines* lines." +msgstr "" + +#: ../Doc/library/curses.rst:1154 +msgid "" +"Control what happens when the cursor of a window is moved off the edge of " +"the window or scrolling region, either as a result of a newline action on " +"the bottom line, or typing the last character of the last line. If *flag* " +"is false, the cursor is left on the bottom line. If *flag* is true, the " +"window is scrolled up one line. Note that in order to get the physical " +"scrolling effect on the terminal, it is also necessary to call :meth:`idlok`." +msgstr "" + +#: ../Doc/library/curses.rst:1164 +msgid "" +"Set the scrolling region from line *top* to line *bottom*. All scrolling " +"actions will take place in this region." +msgstr "" + +#: ../Doc/library/curses.rst:1170 +msgid "" +"Turn off the standout attribute. On some terminals this has the side effect " +"of turning off all attributes." +msgstr "" + +#: ../Doc/library/curses.rst:1176 +msgid "Turn on attribute *A_STANDOUT*." +msgstr "" + +#: ../Doc/library/curses.rst:1182 ../Doc/library/curses.rst:1189 +msgid "" +"Return a sub-window, whose upper-left corner is at ``(begin_y, begin_x)``, " +"and whose width/height is *ncols*/*nlines*." +msgstr "" + +#: ../Doc/library/curses.rst:1192 +msgid "" +"By default, the sub-window will extend from the specified position to the " +"lower right corner of the window." +msgstr "" + +#: ../Doc/library/curses.rst:1198 +msgid "" +"Touch each location in the window that has been touched in any of its " +"ancestor windows. This routine is called by :meth:`refresh`, so it should " +"almost never be necessary to call it manually." +msgstr "" + +#: ../Doc/library/curses.rst:1205 +msgid "" +"If called with *flag* set to ``True``, then :meth:`syncup` is called " +"automatically whenever there is a change in the window." +msgstr "" + +#: ../Doc/library/curses.rst:1211 +msgid "" +"Touch all locations in ancestors of the window that have been changed in " +"the window." +msgstr "" + +#: ../Doc/library/curses.rst:1217 +msgid "" +"Set blocking or non-blocking read behavior for the window. If *delay* is " +"negative, blocking read is used (which will wait indefinitely for input). " +"If *delay* is zero, then non-blocking read is used, and -1 will be returned " +"by :meth:`getch` if no input is waiting. If *delay* is positive, then :meth:" +"`getch` will block for *delay* milliseconds, and return -1 if there is still " +"no input at the end of that time." +msgstr "" + +#: ../Doc/library/curses.rst:1227 +msgid "" +"Pretend *count* lines have been changed, starting with line *start*. If " +"*changed* is supplied, it specifies whether the affected lines are marked as " +"having been changed (*changed*\\ =1) or unchanged (*changed*\\ =0)." +msgstr "" + +#: ../Doc/library/curses.rst:1234 +msgid "" +"Pretend the whole window has been changed, for purposes of drawing " +"optimizations." +msgstr "" + +#: ../Doc/library/curses.rst:1240 +msgid "" +"Mark all lines in the window as unchanged since the last call to :meth:" +"`refresh`." +msgstr "" + +#: ../Doc/library/curses.rst:1247 +msgid "" +"Display a vertical line starting at ``(y, x)`` with length *n* consisting of " +"the character *ch*." +msgstr "" + +#: ../Doc/library/curses.rst:1254 +msgid "The :mod:`curses` module defines the following data members:" +msgstr "" + +#: ../Doc/library/curses.rst:1259 +msgid "" +"Some curses routines that return an integer, such as :func:`getch`, " +"return :const:`ERR` upon failure." +msgstr "" + +#: ../Doc/library/curses.rst:1265 +msgid "" +"Some curses routines that return an integer, such as :func:`napms`, " +"return :const:`OK` upon success." +msgstr "" + +#: ../Doc/library/curses.rst:1271 +msgid "" +"A string representing the current version of the module. Also available as :" +"const:`__version__`." +msgstr "" + +#: ../Doc/library/curses.rst:1274 +msgid "Several constants are available to specify character cell attributes:" +msgstr "" + +#: ../Doc/library/curses.rst:1277 ../Doc/library/datetime.rst:223 +#: ../Doc/library/grp.rst:18 ../Doc/library/inspect.rst:38 +#: ../Doc/library/pwd.rst:18 ../Doc/library/spwd.rst:21 +#: ../Doc/library/sys.rst:713 ../Doc/library/sys.rst:1224 +#: ../Doc/library/time.rst:536 ../Doc/library/urllib.parse.rst:92 +#: ../Doc/library/urllib.parse.rst:213 ../Doc/library/urllib.parse.rst:298 +msgid "Attribute" +msgstr "" + +#: ../Doc/library/curses.rst:1279 +msgid "``A_ALTCHARSET``" +msgstr "" + +#: ../Doc/library/curses.rst:1279 +msgid "Alternate character set mode." +msgstr "" + +#: ../Doc/library/curses.rst:1281 +msgid "``A_BLINK``" +msgstr "" + +#: ../Doc/library/curses.rst:1281 +msgid "Blink mode." +msgstr "" + +#: ../Doc/library/curses.rst:1283 +msgid "``A_BOLD``" +msgstr "" + +#: ../Doc/library/curses.rst:1283 +msgid "Bold mode." +msgstr "" + +#: ../Doc/library/curses.rst:1285 +msgid "``A_DIM``" +msgstr "" + +#: ../Doc/library/curses.rst:1285 +msgid "Dim mode." +msgstr "" + +#: ../Doc/library/curses.rst:1287 +msgid "``A_NORMAL``" +msgstr "" + +#: ../Doc/library/curses.rst:1287 +msgid "Normal attribute." +msgstr "" + +#: ../Doc/library/curses.rst:1289 +msgid "``A_REVERSE``" +msgstr "" + +#: ../Doc/library/curses.rst:1289 +msgid "Reverse background and foreground colors." +msgstr "" + +#: ../Doc/library/curses.rst:1292 +msgid "``A_STANDOUT``" +msgstr "" + +#: ../Doc/library/curses.rst:1292 +msgid "Standout mode." +msgstr "" + +#: ../Doc/library/curses.rst:1294 +msgid "``A_UNDERLINE``" +msgstr "" + +#: ../Doc/library/curses.rst:1294 +msgid "Underline mode." +msgstr "" + +#: ../Doc/library/curses.rst:1297 +msgid "" +"Keys are referred to by integer constants with names starting with " +"``KEY_``. The exact keycaps available are system dependent." +msgstr "" + +#: ../Doc/library/curses.rst:1303 +msgid "Key constant" +msgstr "" + +#: ../Doc/library/curses.rst:1303 ../Doc/library/locale.rst:65 +msgid "Key" +msgstr "" + +#: ../Doc/library/curses.rst:1305 +msgid "``KEY_MIN``" +msgstr "" + +#: ../Doc/library/curses.rst:1305 +msgid "Minimum key value" +msgstr "" + +#: ../Doc/library/curses.rst:1307 +msgid "``KEY_BREAK``" +msgstr "" + +#: ../Doc/library/curses.rst:1307 +msgid "Break key (unreliable)" +msgstr "" + +#: ../Doc/library/curses.rst:1309 +msgid "``KEY_DOWN``" +msgstr "" + +#: ../Doc/library/curses.rst:1309 +msgid "Down-arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1311 +msgid "``KEY_UP``" +msgstr "" + +#: ../Doc/library/curses.rst:1311 +msgid "Up-arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1313 +msgid "``KEY_LEFT``" +msgstr "" + +#: ../Doc/library/curses.rst:1313 +msgid "Left-arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1315 +msgid "``KEY_RIGHT``" +msgstr "" + +#: ../Doc/library/curses.rst:1315 +msgid "Right-arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1317 +msgid "``KEY_HOME``" +msgstr "" + +#: ../Doc/library/curses.rst:1317 +msgid "Home key (upward+left arrow)" +msgstr "" + +#: ../Doc/library/curses.rst:1319 +msgid "``KEY_BACKSPACE``" +msgstr "" + +#: ../Doc/library/curses.rst:1319 +msgid "Backspace (unreliable)" +msgstr "" + +#: ../Doc/library/curses.rst:1321 +msgid "``KEY_F0``" +msgstr "" + +#: ../Doc/library/curses.rst:1321 +msgid "Function keys. Up to 64 function keys are supported." +msgstr "" + +#: ../Doc/library/curses.rst:1324 +msgid "``KEY_Fn``" +msgstr "" + +#: ../Doc/library/curses.rst:1324 +msgid "Value of function key *n*" +msgstr "" + +#: ../Doc/library/curses.rst:1326 +msgid "``KEY_DL``" +msgstr "" + +#: ../Doc/library/curses.rst:1326 +msgid "Delete line" +msgstr "" + +#: ../Doc/library/curses.rst:1328 +msgid "``KEY_IL``" +msgstr "" + +#: ../Doc/library/curses.rst:1328 +msgid "Insert line" +msgstr "" + +#: ../Doc/library/curses.rst:1330 +msgid "``KEY_DC``" +msgstr "" + +#: ../Doc/library/curses.rst:1330 +msgid "Delete character" +msgstr "" + +#: ../Doc/library/curses.rst:1332 +msgid "``KEY_IC``" +msgstr "" + +#: ../Doc/library/curses.rst:1332 +msgid "Insert char or enter insert mode" +msgstr "" + +#: ../Doc/library/curses.rst:1334 +msgid "``KEY_EIC``" +msgstr "" + +#: ../Doc/library/curses.rst:1334 +msgid "Exit insert char mode" +msgstr "" + +#: ../Doc/library/curses.rst:1336 +msgid "``KEY_CLEAR``" +msgstr "" + +#: ../Doc/library/curses.rst:1336 +msgid "Clear screen" +msgstr "" + +#: ../Doc/library/curses.rst:1338 +msgid "``KEY_EOS``" +msgstr "" + +#: ../Doc/library/curses.rst:1338 +msgid "Clear to end of screen" +msgstr "" + +#: ../Doc/library/curses.rst:1340 +msgid "``KEY_EOL``" +msgstr "" + +#: ../Doc/library/curses.rst:1340 +msgid "Clear to end of line" +msgstr "" + +#: ../Doc/library/curses.rst:1342 +msgid "``KEY_SF``" +msgstr "" + +#: ../Doc/library/curses.rst:1342 +msgid "Scroll 1 line forward" +msgstr "" + +#: ../Doc/library/curses.rst:1344 +msgid "``KEY_SR``" +msgstr "" + +#: ../Doc/library/curses.rst:1344 +msgid "Scroll 1 line backward (reverse)" +msgstr "" + +#: ../Doc/library/curses.rst:1346 +msgid "``KEY_NPAGE``" +msgstr "" + +#: ../Doc/library/curses.rst:1346 +msgid "Next page" +msgstr "" + +#: ../Doc/library/curses.rst:1348 +msgid "``KEY_PPAGE``" +msgstr "" + +#: ../Doc/library/curses.rst:1348 +msgid "Previous page" +msgstr "" + +#: ../Doc/library/curses.rst:1350 +msgid "``KEY_STAB``" +msgstr "" + +#: ../Doc/library/curses.rst:1350 +msgid "Set tab" +msgstr "" + +#: ../Doc/library/curses.rst:1352 +msgid "``KEY_CTAB``" +msgstr "" + +#: ../Doc/library/curses.rst:1352 +msgid "Clear tab" +msgstr "" + +#: ../Doc/library/curses.rst:1354 +msgid "``KEY_CATAB``" +msgstr "" + +#: ../Doc/library/curses.rst:1354 +msgid "Clear all tabs" +msgstr "" + +#: ../Doc/library/curses.rst:1356 +msgid "``KEY_ENTER``" +msgstr "" + +#: ../Doc/library/curses.rst:1356 +msgid "Enter or send (unreliable)" +msgstr "" + +#: ../Doc/library/curses.rst:1358 +msgid "``KEY_SRESET``" +msgstr "" + +#: ../Doc/library/curses.rst:1358 +msgid "Soft (partial) reset (unreliable)" +msgstr "" + +#: ../Doc/library/curses.rst:1360 +msgid "``KEY_RESET``" +msgstr "" + +#: ../Doc/library/curses.rst:1360 +msgid "Reset or hard reset (unreliable)" +msgstr "" + +#: ../Doc/library/curses.rst:1362 +msgid "``KEY_PRINT``" +msgstr "" + +#: ../Doc/library/curses.rst:1362 +msgid "Print" +msgstr "" + +#: ../Doc/library/curses.rst:1364 +msgid "``KEY_LL``" +msgstr "" + +#: ../Doc/library/curses.rst:1364 +msgid "Home down or bottom (lower left)" +msgstr "" + +#: ../Doc/library/curses.rst:1366 +msgid "``KEY_A1``" +msgstr "" + +#: ../Doc/library/curses.rst:1366 +msgid "Upper left of keypad" +msgstr "" + +#: ../Doc/library/curses.rst:1368 +msgid "``KEY_A3``" +msgstr "" + +#: ../Doc/library/curses.rst:1368 +msgid "Upper right of keypad" +msgstr "" + +#: ../Doc/library/curses.rst:1370 +msgid "``KEY_B2``" +msgstr "" + +#: ../Doc/library/curses.rst:1370 +msgid "Center of keypad" +msgstr "" + +#: ../Doc/library/curses.rst:1372 +msgid "``KEY_C1``" +msgstr "" + +#: ../Doc/library/curses.rst:1372 +msgid "Lower left of keypad" +msgstr "" + +#: ../Doc/library/curses.rst:1374 +msgid "``KEY_C3``" +msgstr "" + +#: ../Doc/library/curses.rst:1374 +msgid "Lower right of keypad" +msgstr "" + +#: ../Doc/library/curses.rst:1376 +msgid "``KEY_BTAB``" +msgstr "" + +#: ../Doc/library/curses.rst:1376 +msgid "Back tab" +msgstr "" + +#: ../Doc/library/curses.rst:1378 +msgid "``KEY_BEG``" +msgstr "" + +#: ../Doc/library/curses.rst:1378 +msgid "Beg (beginning)" +msgstr "" + +#: ../Doc/library/curses.rst:1380 +msgid "``KEY_CANCEL``" +msgstr "" + +#: ../Doc/library/curses.rst:1380 ../Doc/library/curses.ascii.rst:71 +msgid "Cancel" +msgstr "" + +#: ../Doc/library/curses.rst:1382 +msgid "``KEY_CLOSE``" +msgstr "" + +#: ../Doc/library/curses.rst:1382 ../Doc/library/idle.rst:96 +msgid "Close" +msgstr "" + +#: ../Doc/library/curses.rst:1384 +msgid "``KEY_COMMAND``" +msgstr "" + +#: ../Doc/library/curses.rst:1384 +msgid "Cmd (command)" +msgstr "" + +#: ../Doc/library/curses.rst:1386 +msgid "``KEY_COPY``" +msgstr "" + +#: ../Doc/library/curses.rst:1386 ../Doc/library/idle.rst:115 +#: ../Doc/library/idle.rst:326 +msgid "Copy" +msgstr "" + +#: ../Doc/library/curses.rst:1388 +msgid "``KEY_CREATE``" +msgstr "" + +#: ../Doc/library/curses.rst:1388 +msgid "Create" +msgstr "" + +#: ../Doc/library/curses.rst:1390 +msgid "``KEY_END``" +msgstr "" + +#: ../Doc/library/curses.rst:1390 +msgid "End" +msgstr "" + +#: ../Doc/library/curses.rst:1392 +msgid "``KEY_EXIT``" +msgstr "" + +#: ../Doc/library/curses.rst:1392 ../Doc/library/idle.rst:99 +msgid "Exit" +msgstr "" + +#: ../Doc/library/curses.rst:1394 +msgid "``KEY_FIND``" +msgstr "" + +#: ../Doc/library/curses.rst:1394 +msgid "Find" +msgstr "" + +#: ../Doc/library/curses.rst:1396 +msgid "``KEY_HELP``" +msgstr "" + +#: ../Doc/library/curses.rst:1396 +msgid "Help" +msgstr "" + +#: ../Doc/library/curses.rst:1398 +msgid "``KEY_MARK``" +msgstr "" + +#: ../Doc/library/curses.rst:1398 +msgid "Mark" +msgstr "" + +#: ../Doc/library/curses.rst:1400 +msgid "``KEY_MESSAGE``" +msgstr "" + +#: ../Doc/library/curses.rst:1400 +msgid "Message" +msgstr "" + +#: ../Doc/library/curses.rst:1402 +msgid "``KEY_MOVE``" +msgstr "" + +#: ../Doc/library/curses.rst:1402 +msgid "Move" +msgstr "" + +#: ../Doc/library/curses.rst:1404 +msgid "``KEY_NEXT``" +msgstr "" + +#: ../Doc/library/curses.rst:1404 +msgid "Next" +msgstr "" + +#: ../Doc/library/curses.rst:1406 +msgid "``KEY_OPEN``" +msgstr "" + +#: ../Doc/library/curses.rst:1406 +msgid "Open" +msgstr "" + +#: ../Doc/library/curses.rst:1408 +msgid "``KEY_OPTIONS``" +msgstr "" + +#: ../Doc/library/curses.rst:1408 ../Doc/library/tkinter.ttk.rst:312 +#: ../Doc/library/tkinter.ttk.rst:393 ../Doc/library/tkinter.ttk.rst:583 +#: ../Doc/library/tkinter.ttk.rst:654 ../Doc/library/tkinter.ttk.rst:722 +msgid "Options" +msgstr "" + +#: ../Doc/library/curses.rst:1410 +msgid "``KEY_PREVIOUS``" +msgstr "" + +#: ../Doc/library/curses.rst:1410 +msgid "Prev (previous)" +msgstr "" + +#: ../Doc/library/curses.rst:1412 +msgid "``KEY_REDO``" +msgstr "" + +#: ../Doc/library/curses.rst:1412 ../Doc/library/idle.rst:109 +msgid "Redo" +msgstr "" + +#: ../Doc/library/curses.rst:1414 +msgid "``KEY_REFERENCE``" +msgstr "" + +#: ../Doc/library/curses.rst:1414 +msgid "Ref (reference)" +msgstr "" + +#: ../Doc/library/curses.rst:1416 +msgid "``KEY_REFRESH``" +msgstr "" + +#: ../Doc/library/curses.rst:1416 +msgid "Refresh" +msgstr "" + +#: ../Doc/library/curses.rst:1418 +msgid "``KEY_REPLACE``" +msgstr "" + +#: ../Doc/library/curses.rst:1418 +msgid "Replace" +msgstr "" + +#: ../Doc/library/curses.rst:1420 +msgid "``KEY_RESTART``" +msgstr "" + +#: ../Doc/library/curses.rst:1420 +msgid "Restart" +msgstr "" + +#: ../Doc/library/curses.rst:1422 +msgid "``KEY_RESUME``" +msgstr "" + +#: ../Doc/library/curses.rst:1422 +msgid "Resume" +msgstr "" + +#: ../Doc/library/curses.rst:1424 +msgid "``KEY_SAVE``" +msgstr "" + +#: ../Doc/library/curses.rst:1424 ../Doc/library/idle.rst:82 +msgid "Save" +msgstr "" + +#: ../Doc/library/curses.rst:1426 +msgid "``KEY_SBEG``" +msgstr "" + +#: ../Doc/library/curses.rst:1426 +msgid "Shifted Beg (beginning)" +msgstr "" + +#: ../Doc/library/curses.rst:1428 +msgid "``KEY_SCANCEL``" +msgstr "" + +#: ../Doc/library/curses.rst:1428 +msgid "Shifted Cancel" +msgstr "" + +#: ../Doc/library/curses.rst:1430 +msgid "``KEY_SCOMMAND``" +msgstr "" + +#: ../Doc/library/curses.rst:1430 +msgid "Shifted Command" +msgstr "" + +#: ../Doc/library/curses.rst:1432 +msgid "``KEY_SCOPY``" +msgstr "" + +#: ../Doc/library/curses.rst:1432 +msgid "Shifted Copy" +msgstr "" + +#: ../Doc/library/curses.rst:1434 +msgid "``KEY_SCREATE``" +msgstr "" + +#: ../Doc/library/curses.rst:1434 +msgid "Shifted Create" +msgstr "" + +#: ../Doc/library/curses.rst:1436 +msgid "``KEY_SDC``" +msgstr "" + +#: ../Doc/library/curses.rst:1436 +msgid "Shifted Delete char" +msgstr "" + +#: ../Doc/library/curses.rst:1438 +msgid "``KEY_SDL``" +msgstr "" + +#: ../Doc/library/curses.rst:1438 +msgid "Shifted Delete line" +msgstr "" + +#: ../Doc/library/curses.rst:1440 +msgid "``KEY_SELECT``" +msgstr "" + +#: ../Doc/library/curses.rst:1440 +msgid "Select" +msgstr "" + +#: ../Doc/library/curses.rst:1442 +msgid "``KEY_SEND``" +msgstr "" + +#: ../Doc/library/curses.rst:1442 +msgid "Shifted End" +msgstr "" + +#: ../Doc/library/curses.rst:1444 +msgid "``KEY_SEOL``" +msgstr "" + +#: ../Doc/library/curses.rst:1444 +msgid "Shifted Clear line" +msgstr "" + +#: ../Doc/library/curses.rst:1446 +msgid "``KEY_SEXIT``" +msgstr "" + +#: ../Doc/library/curses.rst:1446 +msgid "Shifted Dxit" +msgstr "" + +#: ../Doc/library/curses.rst:1448 +msgid "``KEY_SFIND``" +msgstr "" + +#: ../Doc/library/curses.rst:1448 +msgid "Shifted Find" +msgstr "" + +#: ../Doc/library/curses.rst:1450 +msgid "``KEY_SHELP``" +msgstr "" + +#: ../Doc/library/curses.rst:1450 +msgid "Shifted Help" +msgstr "" + +#: ../Doc/library/curses.rst:1452 +msgid "``KEY_SHOME``" +msgstr "" + +#: ../Doc/library/curses.rst:1452 +msgid "Shifted Home" +msgstr "" + +#: ../Doc/library/curses.rst:1454 +msgid "``KEY_SIC``" +msgstr "" + +#: ../Doc/library/curses.rst:1454 +msgid "Shifted Input" +msgstr "" + +#: ../Doc/library/curses.rst:1456 +msgid "``KEY_SLEFT``" +msgstr "" + +#: ../Doc/library/curses.rst:1456 +msgid "Shifted Left arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1458 +msgid "``KEY_SMESSAGE``" +msgstr "" + +#: ../Doc/library/curses.rst:1458 +msgid "Shifted Message" +msgstr "" + +#: ../Doc/library/curses.rst:1460 +msgid "``KEY_SMOVE``" +msgstr "" + +#: ../Doc/library/curses.rst:1460 +msgid "Shifted Move" +msgstr "" + +#: ../Doc/library/curses.rst:1462 +msgid "``KEY_SNEXT``" +msgstr "" + +#: ../Doc/library/curses.rst:1462 +msgid "Shifted Next" +msgstr "" + +#: ../Doc/library/curses.rst:1464 +msgid "``KEY_SOPTIONS``" +msgstr "" + +#: ../Doc/library/curses.rst:1464 +msgid "Shifted Options" +msgstr "" + +#: ../Doc/library/curses.rst:1466 +msgid "``KEY_SPREVIOUS``" +msgstr "" + +#: ../Doc/library/curses.rst:1466 +msgid "Shifted Prev" +msgstr "" + +#: ../Doc/library/curses.rst:1468 +msgid "``KEY_SPRINT``" +msgstr "" + +#: ../Doc/library/curses.rst:1468 +msgid "Shifted Print" +msgstr "" + +#: ../Doc/library/curses.rst:1470 +msgid "``KEY_SREDO``" +msgstr "" + +#: ../Doc/library/curses.rst:1470 +msgid "Shifted Redo" +msgstr "" + +#: ../Doc/library/curses.rst:1472 +msgid "``KEY_SREPLACE``" +msgstr "" + +#: ../Doc/library/curses.rst:1472 +msgid "Shifted Replace" +msgstr "" + +#: ../Doc/library/curses.rst:1474 +msgid "``KEY_SRIGHT``" +msgstr "" + +#: ../Doc/library/curses.rst:1474 +msgid "Shifted Right arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1476 +msgid "``KEY_SRSUME``" +msgstr "" + +#: ../Doc/library/curses.rst:1476 +msgid "Shifted Resume" +msgstr "" + +#: ../Doc/library/curses.rst:1478 +msgid "``KEY_SSAVE``" +msgstr "" + +#: ../Doc/library/curses.rst:1478 +msgid "Shifted Save" +msgstr "" + +#: ../Doc/library/curses.rst:1480 +msgid "``KEY_SSUSPEND``" +msgstr "" + +#: ../Doc/library/curses.rst:1480 +msgid "Shifted Suspend" +msgstr "" + +#: ../Doc/library/curses.rst:1482 +msgid "``KEY_SUNDO``" +msgstr "" + +#: ../Doc/library/curses.rst:1482 +msgid "Shifted Undo" +msgstr "" + +#: ../Doc/library/curses.rst:1484 +msgid "``KEY_SUSPEND``" +msgstr "" + +#: ../Doc/library/curses.rst:1484 +msgid "Suspend" +msgstr "" + +#: ../Doc/library/curses.rst:1486 +msgid "``KEY_UNDO``" +msgstr "" + +#: ../Doc/library/curses.rst:1486 ../Doc/library/idle.rst:106 +msgid "Undo" +msgstr "" + +#: ../Doc/library/curses.rst:1488 +msgid "``KEY_MOUSE``" +msgstr "" + +#: ../Doc/library/curses.rst:1488 +msgid "Mouse event has occurred" +msgstr "" + +#: ../Doc/library/curses.rst:1490 +msgid "``KEY_RESIZE``" +msgstr "" + +#: ../Doc/library/curses.rst:1490 +msgid "Terminal resize event" +msgstr "" + +#: ../Doc/library/curses.rst:1492 +msgid "``KEY_MAX``" +msgstr "" + +#: ../Doc/library/curses.rst:1492 +msgid "Maximum key value" +msgstr "" + +#: ../Doc/library/curses.rst:1495 +msgid "" +"On VT100s and their software emulations, such as X terminal emulators, there " +"are normally at least four function keys (:const:`KEY_F1`, :const:`KEY_F2`, :" +"const:`KEY_F3`, :const:`KEY_F4`) available, and the arrow keys mapped to :" +"const:`KEY_UP`, :const:`KEY_DOWN`, :const:`KEY_LEFT` and :const:`KEY_RIGHT` " +"in the obvious way. If your machine has a PC keyboard, it is safe to expect " +"arrow keys and twelve function keys (older PC keyboards may have only ten " +"function keys); also, the following keypad mappings are standard:" +msgstr "" + +#: ../Doc/library/curses.rst:1504 +msgid "Keycap" +msgstr "" + +#: ../Doc/library/curses.rst:1506 +msgid ":kbd:`Insert`" +msgstr "" + +#: ../Doc/library/curses.rst:1506 +msgid "KEY_IC" +msgstr "" + +#: ../Doc/library/curses.rst:1508 +msgid ":kbd:`Delete`" +msgstr "" + +#: ../Doc/library/curses.rst:1508 +msgid "KEY_DC" +msgstr "" + +#: ../Doc/library/curses.rst:1510 +msgid ":kbd:`Home`" +msgstr "" + +#: ../Doc/library/curses.rst:1510 +msgid "KEY_HOME" +msgstr "" + +#: ../Doc/library/curses.rst:1512 +msgid ":kbd:`End`" +msgstr "" + +#: ../Doc/library/curses.rst:1512 +msgid "KEY_END" +msgstr "" + +#: ../Doc/library/curses.rst:1514 +msgid ":kbd:`Page Up`" +msgstr "" + +#: ../Doc/library/curses.rst:1514 +msgid "KEY_PPAGE" +msgstr "" + +#: ../Doc/library/curses.rst:1516 +msgid ":kbd:`Page Down`" +msgstr "" + +#: ../Doc/library/curses.rst:1516 +msgid "KEY_NPAGE" +msgstr "" + +#: ../Doc/library/curses.rst:1519 +msgid "" +"The following table lists characters from the alternate character set. These " +"are inherited from the VT100 terminal, and will generally be available on " +"software emulations such as X terminals. When there is no graphic " +"available, curses falls back on a crude printable ASCII approximation." +msgstr "" + +#: ../Doc/library/curses.rst:1526 +msgid "These are available only after :func:`initscr` has been called." +msgstr "" + +#: ../Doc/library/curses.rst:1529 +msgid "ACS code" +msgstr "" + +#: ../Doc/library/curses.rst:1531 +msgid "``ACS_BBSS``" +msgstr "" + +#: ../Doc/library/curses.rst:1531 +msgid "alternate name for upper right corner" +msgstr "" + +#: ../Doc/library/curses.rst:1533 +msgid "``ACS_BLOCK``" +msgstr "" + +#: ../Doc/library/curses.rst:1533 +msgid "solid square block" +msgstr "" + +#: ../Doc/library/curses.rst:1535 +msgid "``ACS_BOARD``" +msgstr "" + +#: ../Doc/library/curses.rst:1535 +msgid "board of squares" +msgstr "" + +#: ../Doc/library/curses.rst:1537 +msgid "``ACS_BSBS``" +msgstr "" + +#: ../Doc/library/curses.rst:1537 +msgid "alternate name for horizontal line" +msgstr "" + +#: ../Doc/library/curses.rst:1539 +msgid "``ACS_BSSB``" +msgstr "" + +#: ../Doc/library/curses.rst:1539 +msgid "alternate name for upper left corner" +msgstr "" + +#: ../Doc/library/curses.rst:1541 +msgid "``ACS_BSSS``" +msgstr "" + +#: ../Doc/library/curses.rst:1541 +msgid "alternate name for top tee" +msgstr "" + +#: ../Doc/library/curses.rst:1543 +msgid "``ACS_BTEE``" +msgstr "" + +#: ../Doc/library/curses.rst:1543 +msgid "bottom tee" +msgstr "" + +#: ../Doc/library/curses.rst:1545 +msgid "``ACS_BULLET``" +msgstr "" + +#: ../Doc/library/curses.rst:1545 +msgid "bullet" +msgstr "" + +#: ../Doc/library/curses.rst:1547 +msgid "``ACS_CKBOARD``" +msgstr "" + +#: ../Doc/library/curses.rst:1547 +msgid "checker board (stipple)" +msgstr "" + +#: ../Doc/library/curses.rst:1549 +msgid "``ACS_DARROW``" +msgstr "" + +#: ../Doc/library/curses.rst:1549 +msgid "arrow pointing down" +msgstr "" + +#: ../Doc/library/curses.rst:1551 +msgid "``ACS_DEGREE``" +msgstr "" + +#: ../Doc/library/curses.rst:1551 +msgid "degree symbol" +msgstr "" + +#: ../Doc/library/curses.rst:1553 +msgid "``ACS_DIAMOND``" +msgstr "" + +#: ../Doc/library/curses.rst:1553 +msgid "diamond" +msgstr "" + +#: ../Doc/library/curses.rst:1555 +msgid "``ACS_GEQUAL``" +msgstr "" + +#: ../Doc/library/curses.rst:1555 +msgid "greater-than-or-equal-to" +msgstr "" + +#: ../Doc/library/curses.rst:1557 +msgid "``ACS_HLINE``" +msgstr "" + +#: ../Doc/library/curses.rst:1557 +msgid "horizontal line" +msgstr "" + +#: ../Doc/library/curses.rst:1559 +msgid "``ACS_LANTERN``" +msgstr "" + +#: ../Doc/library/curses.rst:1559 +msgid "lantern symbol" +msgstr "" + +#: ../Doc/library/curses.rst:1561 +msgid "``ACS_LARROW``" +msgstr "" + +#: ../Doc/library/curses.rst:1561 +msgid "left arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1563 +msgid "``ACS_LEQUAL``" +msgstr "" + +#: ../Doc/library/curses.rst:1563 +msgid "less-than-or-equal-to" +msgstr "" + +#: ../Doc/library/curses.rst:1565 +msgid "``ACS_LLCORNER``" +msgstr "" + +#: ../Doc/library/curses.rst:1565 +msgid "lower left-hand corner" +msgstr "" + +#: ../Doc/library/curses.rst:1567 +msgid "``ACS_LRCORNER``" +msgstr "" + +#: ../Doc/library/curses.rst:1567 +msgid "lower right-hand corner" +msgstr "" + +#: ../Doc/library/curses.rst:1569 +msgid "``ACS_LTEE``" +msgstr "" + +#: ../Doc/library/curses.rst:1569 +msgid "left tee" +msgstr "" + +#: ../Doc/library/curses.rst:1571 +msgid "``ACS_NEQUAL``" +msgstr "" + +#: ../Doc/library/curses.rst:1571 +msgid "not-equal sign" +msgstr "" + +#: ../Doc/library/curses.rst:1573 +msgid "``ACS_PI``" +msgstr "" + +#: ../Doc/library/curses.rst:1573 +msgid "letter pi" +msgstr "" + +#: ../Doc/library/curses.rst:1575 +msgid "``ACS_PLMINUS``" +msgstr "" + +#: ../Doc/library/curses.rst:1575 +msgid "plus-or-minus sign" +msgstr "" + +#: ../Doc/library/curses.rst:1577 +msgid "``ACS_PLUS``" +msgstr "" + +#: ../Doc/library/curses.rst:1577 +msgid "big plus sign" +msgstr "" + +#: ../Doc/library/curses.rst:1579 +msgid "``ACS_RARROW``" +msgstr "" + +#: ../Doc/library/curses.rst:1579 +msgid "right arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1581 +msgid "``ACS_RTEE``" +msgstr "" + +#: ../Doc/library/curses.rst:1581 +msgid "right tee" +msgstr "" + +#: ../Doc/library/curses.rst:1583 +msgid "``ACS_S1``" +msgstr "" + +#: ../Doc/library/curses.rst:1583 +msgid "scan line 1" +msgstr "" + +#: ../Doc/library/curses.rst:1585 +msgid "``ACS_S3``" +msgstr "" + +#: ../Doc/library/curses.rst:1585 +msgid "scan line 3" +msgstr "" + +#: ../Doc/library/curses.rst:1587 +msgid "``ACS_S7``" +msgstr "" + +#: ../Doc/library/curses.rst:1587 +msgid "scan line 7" +msgstr "" + +#: ../Doc/library/curses.rst:1589 +msgid "``ACS_S9``" +msgstr "" + +#: ../Doc/library/curses.rst:1589 +msgid "scan line 9" +msgstr "" + +#: ../Doc/library/curses.rst:1591 +msgid "``ACS_SBBS``" +msgstr "" + +#: ../Doc/library/curses.rst:1591 +msgid "alternate name for lower right corner" +msgstr "" + +#: ../Doc/library/curses.rst:1593 +msgid "``ACS_SBSB``" +msgstr "" + +#: ../Doc/library/curses.rst:1593 +msgid "alternate name for vertical line" +msgstr "" + +#: ../Doc/library/curses.rst:1595 +msgid "``ACS_SBSS``" +msgstr "" + +#: ../Doc/library/curses.rst:1595 +msgid "alternate name for right tee" +msgstr "" + +#: ../Doc/library/curses.rst:1597 +msgid "``ACS_SSBB``" +msgstr "" + +#: ../Doc/library/curses.rst:1597 +msgid "alternate name for lower left corner" +msgstr "" + +#: ../Doc/library/curses.rst:1599 +msgid "``ACS_SSBS``" +msgstr "" + +#: ../Doc/library/curses.rst:1599 +msgid "alternate name for bottom tee" +msgstr "" + +#: ../Doc/library/curses.rst:1601 +msgid "``ACS_SSSB``" +msgstr "" + +#: ../Doc/library/curses.rst:1601 +msgid "alternate name for left tee" +msgstr "" + +#: ../Doc/library/curses.rst:1603 +msgid "``ACS_SSSS``" +msgstr "" + +#: ../Doc/library/curses.rst:1603 +msgid "alternate name for crossover or big plus" +msgstr "" + +#: ../Doc/library/curses.rst:1605 +msgid "``ACS_STERLING``" +msgstr "" + +#: ../Doc/library/curses.rst:1605 +msgid "pound sterling" +msgstr "" + +#: ../Doc/library/curses.rst:1607 +msgid "``ACS_TTEE``" +msgstr "" + +#: ../Doc/library/curses.rst:1607 +msgid "top tee" +msgstr "" + +#: ../Doc/library/curses.rst:1609 +msgid "``ACS_UARROW``" +msgstr "" + +#: ../Doc/library/curses.rst:1609 +msgid "up arrow" +msgstr "" + +#: ../Doc/library/curses.rst:1611 +msgid "``ACS_ULCORNER``" +msgstr "" + +#: ../Doc/library/curses.rst:1611 +msgid "upper left corner" +msgstr "" + +#: ../Doc/library/curses.rst:1613 +msgid "``ACS_URCORNER``" +msgstr "" + +#: ../Doc/library/curses.rst:1613 +msgid "upper right corner" +msgstr "" + +#: ../Doc/library/curses.rst:1615 +msgid "``ACS_VLINE``" +msgstr "" + +#: ../Doc/library/curses.rst:1615 +msgid "vertical line" +msgstr "" + +#: ../Doc/library/curses.rst:1618 +msgid "The following table lists the predefined colors:" +msgstr "" + +#: ../Doc/library/curses.rst:1621 +msgid "Color" +msgstr "" + +#: ../Doc/library/curses.rst:1623 +msgid "``COLOR_BLACK``" +msgstr "" + +#: ../Doc/library/curses.rst:1623 +msgid "Black" +msgstr "" + +#: ../Doc/library/curses.rst:1625 +msgid "``COLOR_BLUE``" +msgstr "" + +#: ../Doc/library/curses.rst:1625 +msgid "Blue" +msgstr "" + +#: ../Doc/library/curses.rst:1627 +msgid "``COLOR_CYAN``" +msgstr "" + +#: ../Doc/library/curses.rst:1627 +msgid "Cyan (light greenish blue)" +msgstr "" + +#: ../Doc/library/curses.rst:1629 +msgid "``COLOR_GREEN``" +msgstr "" + +#: ../Doc/library/curses.rst:1629 +msgid "Green" +msgstr "" + +#: ../Doc/library/curses.rst:1631 +msgid "``COLOR_MAGENTA``" +msgstr "" + +#: ../Doc/library/curses.rst:1631 +msgid "Magenta (purplish red)" +msgstr "" + +#: ../Doc/library/curses.rst:1633 +msgid "``COLOR_RED``" +msgstr "" + +#: ../Doc/library/curses.rst:1633 +msgid "Red" +msgstr "" + +#: ../Doc/library/curses.rst:1635 +msgid "``COLOR_WHITE``" +msgstr "" + +#: ../Doc/library/curses.rst:1635 +msgid "White" +msgstr "" + +#: ../Doc/library/curses.rst:1637 +msgid "``COLOR_YELLOW``" +msgstr "" + +#: ../Doc/library/curses.rst:1637 +msgid "Yellow" +msgstr "" + +#: ../Doc/library/curses.rst:1642 +msgid ":mod:`curses.textpad` --- Text input widget for curses programs" +msgstr "" + +#: ../Doc/library/curses.rst:1650 +msgid "" +"The :mod:`curses.textpad` module provides a :class:`Textbox` class that " +"handles elementary text editing in a curses window, supporting a set of " +"keybindings resembling those of Emacs (thus, also of Netscape Navigator, " +"BBedit 6.x, FrameMaker, and many other programs). The module also provides " +"a rectangle-drawing function useful for framing text boxes or for other " +"purposes." +msgstr "" + +#: ../Doc/library/curses.rst:1656 +msgid "The module :mod:`curses.textpad` defines the following function:" +msgstr "" + +#: ../Doc/library/curses.rst:1661 +msgid "" +"Draw a rectangle. The first argument must be a window object; the remaining " +"arguments are coordinates relative to that window. The second and third " +"arguments are the y and x coordinates of the upper left hand corner of the " +"rectangle to be drawn; the fourth and fifth arguments are the y and x " +"coordinates of the lower right hand corner. The rectangle will be drawn " +"using VT100/IBM PC forms characters on terminals that make this possible " +"(including xterm and most other software terminal emulators). Otherwise it " +"will be drawn with ASCII dashes, vertical bars, and plus signs." +msgstr "" + +#: ../Doc/library/curses.rst:1674 +msgid "Textbox objects" +msgstr "" + +#: ../Doc/library/curses.rst:1676 +msgid "You can instantiate a :class:`Textbox` object as follows:" +msgstr "" + +#: ../Doc/library/curses.rst:1681 +msgid "" +"Return a textbox widget object. The *win* argument should be a curses :" +"class:`WindowObject` in which the textbox is to be contained. The edit " +"cursor of the textbox is initially located at the upper left hand corner of " +"the containing window, with coordinates ``(0, 0)``. The instance's :attr:" +"`stripspaces` flag is initially on." +msgstr "" + +#: ../Doc/library/curses.rst:1687 +msgid ":class:`Textbox` objects have the following methods:" +msgstr "" + +#: ../Doc/library/curses.rst:1692 +msgid "" +"This is the entry point you will normally use. It accepts editing " +"keystrokes until one of the termination keystrokes is entered. If " +"*validator* is supplied, it must be a function. It will be called for each " +"keystroke entered with the keystroke as a parameter; command dispatch is " +"done on the result. This method returns the window contents as a string; " +"whether blanks in the window are included is affected by the :attr:" +"`stripspaces` attribute." +msgstr "" + +#: ../Doc/library/curses.rst:1703 +msgid "" +"Process a single command keystroke. Here are the supported special " +"keystrokes:" +msgstr "" + +#: ../Doc/library/curses.rst:1707 ../Doc/library/curses.rst:1745 +msgid "Keystroke" +msgstr "" + +#: ../Doc/library/curses.rst:1707 ../Doc/library/tarfile.rst:117 +msgid "Action" +msgstr "" + +#: ../Doc/library/curses.rst:1709 +msgid ":kbd:`Control-A`" +msgstr "" + +#: ../Doc/library/curses.rst:1709 +msgid "Go to left edge of window." +msgstr "" + +#: ../Doc/library/curses.rst:1711 ../Doc/library/curses.rst:1747 +msgid ":kbd:`Control-B`" +msgstr "" + +#: ../Doc/library/curses.rst:1711 +msgid "Cursor left, wrapping to previous line if appropriate." +msgstr "" + +#: ../Doc/library/curses.rst:1714 +msgid ":kbd:`Control-D`" +msgstr "" + +#: ../Doc/library/curses.rst:1714 +msgid "Delete character under cursor." +msgstr "" + +#: ../Doc/library/curses.rst:1716 +msgid ":kbd:`Control-E`" +msgstr "" + +#: ../Doc/library/curses.rst:1716 +msgid "Go to right edge (stripspaces off) or end of line (stripspaces on)." +msgstr "" + +#: ../Doc/library/curses.rst:1719 ../Doc/library/curses.rst:1749 +msgid ":kbd:`Control-F`" +msgstr "" + +#: ../Doc/library/curses.rst:1719 +msgid "Cursor right, wrapping to next line when appropriate." +msgstr "" + +#: ../Doc/library/curses.rst:1722 +msgid ":kbd:`Control-G`" +msgstr "" + +#: ../Doc/library/curses.rst:1722 +msgid "Terminate, returning the window contents." +msgstr "" + +#: ../Doc/library/curses.rst:1724 +msgid ":kbd:`Control-H`" +msgstr "" + +#: ../Doc/library/curses.rst:1724 +msgid "Delete character backward." +msgstr "" + +#: ../Doc/library/curses.rst:1726 +msgid ":kbd:`Control-J`" +msgstr "" + +#: ../Doc/library/curses.rst:1726 +msgid "Terminate if the window is 1 line, otherwise insert newline." +msgstr "" + +#: ../Doc/library/curses.rst:1729 +msgid ":kbd:`Control-K`" +msgstr "" + +#: ../Doc/library/curses.rst:1729 +msgid "If line is blank, delete it, otherwise clear to end of line." +msgstr "" + +#: ../Doc/library/curses.rst:1732 +msgid ":kbd:`Control-L`" +msgstr "" + +#: ../Doc/library/curses.rst:1732 +msgid "Refresh screen." +msgstr "" + +#: ../Doc/library/curses.rst:1734 ../Doc/library/curses.rst:1753 +msgid ":kbd:`Control-N`" +msgstr "" + +#: ../Doc/library/curses.rst:1734 +msgid "Cursor down; move down one line." +msgstr "" + +#: ../Doc/library/curses.rst:1736 +msgid ":kbd:`Control-O`" +msgstr "" + +#: ../Doc/library/curses.rst:1736 +msgid "Insert a blank line at cursor location." +msgstr "" + +#: ../Doc/library/curses.rst:1738 ../Doc/library/curses.rst:1751 +msgid ":kbd:`Control-P`" +msgstr "" + +#: ../Doc/library/curses.rst:1738 +msgid "Cursor up; move up one line." +msgstr "" + +#: ../Doc/library/curses.rst:1741 +msgid "" +"Move operations do nothing if the cursor is at an edge where the movement is " +"not possible. The following synonyms are supported where possible:" +msgstr "" + +#: ../Doc/library/curses.rst:1747 +msgid ":const:`KEY_LEFT`" +msgstr "" + +#: ../Doc/library/curses.rst:1749 +msgid ":const:`KEY_RIGHT`" +msgstr "" + +#: ../Doc/library/curses.rst:1751 +msgid ":const:`KEY_UP`" +msgstr "" + +#: ../Doc/library/curses.rst:1753 +msgid ":const:`KEY_DOWN`" +msgstr "" + +#: ../Doc/library/curses.rst:1755 +msgid ":const:`KEY_BACKSPACE`" +msgstr "" + +#: ../Doc/library/curses.rst:1755 +msgid ":kbd:`Control-h`" +msgstr "" + +#: ../Doc/library/curses.rst:1758 +msgid "" +"All other keystrokes are treated as a command to insert the given character " +"and move right (with line wrapping)." +msgstr "" + +#: ../Doc/library/curses.rst:1764 +msgid "" +"Return the window contents as a string; whether blanks in the window are " +"included is affected by the :attr:`stripspaces` member." +msgstr "" + +#: ../Doc/library/curses.rst:1770 +msgid "" +"This attribute is a flag which controls the interpretation of blanks in the " +"window. When it is on, trailing blanks on each line are ignored; any cursor " +"motion that would land the cursor on a trailing blank goes to the end of " +"that line instead, and trailing blanks are stripped when the window contents " +"are gathered." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:2 +msgid ":mod:`curses.ascii` --- Utilities for ASCII characters" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:12 +msgid "" +"The :mod:`curses.ascii` module supplies name constants for ASCII characters " +"and functions to test membership in various ASCII character classes. The " +"constants supplied are names for control characters as follows:" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:17 ../Doc/library/inspect.rst:658 +#: ../Doc/library/turtle.rst:2312 +msgid "Name" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:19 +msgid ":const:`NUL`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:21 +msgid ":const:`SOH`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:21 +msgid "Start of heading, console interrupt" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:23 +msgid ":const:`STX`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:23 +msgid "Start of text" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:25 +msgid ":const:`ETX`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:25 +msgid "End of text" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:27 +msgid ":const:`EOT`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:27 +msgid "End of transmission" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:29 +msgid ":const:`ENQ`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:29 +msgid "Enquiry, goes with :const:`ACK` flow control" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:31 +msgid ":const:`ACK`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:31 +msgid "Acknowledgement" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:33 +msgid ":const:`BEL`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:33 +msgid "Bell" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:35 +msgid ":const:`BS`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:35 +msgid "Backspace" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:37 +msgid ":const:`TAB`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:37 +msgid "Tab" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:39 +msgid ":const:`HT`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:39 +msgid "Alias for :const:`TAB`: \"Horizontal tab\"" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:41 +msgid ":const:`LF`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:41 +msgid "Line feed" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:43 +msgid ":const:`NL`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:43 +msgid "Alias for :const:`LF`: \"New line\"" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:45 +msgid ":const:`VT`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:45 +msgid "Vertical tab" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:47 +msgid ":const:`FF`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:47 +msgid "Form feed" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:49 +msgid ":const:`CR`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:49 +msgid "Carriage return" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:51 +msgid ":const:`SO`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:51 +msgid "Shift-out, begin alternate character set" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:53 +msgid ":const:`SI`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:53 +msgid "Shift-in, resume default character set" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:55 +msgid ":const:`DLE`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:55 +msgid "Data-link escape" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:57 +msgid ":const:`DC1`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:57 +msgid "XON, for flow control" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:59 +msgid ":const:`DC2`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:59 +msgid "Device control 2, block-mode flow control" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:61 +msgid ":const:`DC3`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:61 +msgid "XOFF, for flow control" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:63 +msgid ":const:`DC4`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:63 +msgid "Device control 4" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:65 +msgid ":const:`NAK`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:65 +msgid "Negative acknowledgement" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:67 +msgid ":const:`SYN`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:67 +msgid "Synchronous idle" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:69 +msgid ":const:`ETB`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:69 +msgid "End transmission block" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:71 +msgid ":const:`CAN`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:73 +msgid ":const:`EM`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:73 +msgid "End of medium" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:75 +msgid ":const:`SUB`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:75 +msgid "Substitute" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:77 +msgid ":const:`ESC`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:77 +msgid "Escape" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:79 +msgid ":const:`FS`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:79 +msgid "File separator" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:81 +msgid ":const:`GS`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:81 +msgid "Group separator" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:83 +msgid ":const:`RS`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:83 +msgid "Record separator, block-mode terminator" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:85 +msgid ":const:`US`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:85 +msgid "Unit separator" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:87 +msgid ":const:`SP`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:87 +msgid "Space" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:89 +msgid ":const:`DEL`" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:89 +msgid "Delete" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:92 +msgid "" +"Note that many of these have little practical significance in modern usage. " +"The mnemonics derive from teleprinter conventions that predate digital " +"computers." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:95 +msgid "" +"The module supplies the following functions, patterned on those in the " +"standard C library:" +msgstr "" + +#: ../Doc/library/curses.ascii.rst:101 +msgid "" +"Checks for an ASCII alphanumeric character; it is equivalent to ``isalpha(c) " +"or isdigit(c)``." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:107 +msgid "" +"Checks for an ASCII alphabetic character; it is equivalent to ``isupper(c) " +"or islower(c)``." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:113 +msgid "Checks for a character value that fits in the 7-bit ASCII set." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:118 +msgid "Checks for an ASCII whitespace character; space or horizontal tab." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:123 +msgid "" +"Checks for an ASCII control character (in the range 0x00 to 0x1f or 0x7f)." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:128 +msgid "" +"Checks for an ASCII decimal digit, ``'0'`` through ``'9'``. This is " +"equivalent to ``c in string.digits``." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:134 +msgid "Checks for ASCII any printable character except space." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:139 +msgid "Checks for an ASCII lower-case character." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:144 +msgid "Checks for any ASCII printable character including space." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:149 +msgid "" +"Checks for any printable ASCII character which is not a space or an " +"alphanumeric character." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:155 +msgid "" +"Checks for ASCII white-space characters; space, line feed, carriage return, " +"form feed, horizontal tab, vertical tab." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:161 +msgid "Checks for an ASCII uppercase letter." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:166 +msgid "" +"Checks for an ASCII hexadecimal digit. This is equivalent to ``c in string." +"hexdigits``." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:172 +msgid "Checks for an ASCII control character (ordinal values 0 to 31)." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:177 +msgid "Checks for a non-ASCII character (ordinal values 0x80 and above)." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:179 +msgid "" +"These functions accept either integers or strings; when the argument is a " +"string, it is first converted using the built-in function :func:`ord`." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:182 +msgid "" +"Note that all these functions check ordinal bit values derived from the " +"first character of the string you pass in; they do not actually know " +"anything about the host machine's character encoding. For functions that " +"know about the character encoding (and handle internationalization properly) " +"see the :mod:`string` module." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:188 +msgid "" +"The following two functions take either a single-character string or integer " +"byte value; they return a value of the same type." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:194 +msgid "Return the ASCII value corresponding to the low 7 bits of *c*." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:199 +msgid "" +"Return the control character corresponding to the given character (the " +"character bit value is bitwise-anded with 0x1f)." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:205 +msgid "" +"Return the 8-bit character corresponding to the given ASCII character (the " +"character bit value is bitwise-ored with 0x80)." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:208 +msgid "" +"The following function takes either a single-character string or integer " +"value; it returns a string." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:214 +msgid "" +"Return a string representation of the ASCII character *c*. If *c* is " +"printable, this string is the character itself. If the character is a " +"control character (0x00-0x1f) the string consists of a caret (``'^'``) " +"followed by the corresponding uppercase letter. If the character is an ASCII " +"delete (0x7f) the string is ``'^?'``. If the character has its meta bit " +"(0x80) set, the meta bit is stripped, the preceding rules applied, and " +"``'!'`` prepended to the result." +msgstr "" + +#: ../Doc/library/curses.ascii.rst:224 +msgid "" +"A 33-element string array that contains the ASCII mnemonics for the thirty-" +"two ASCII control characters from 0 (NUL) to 0x1f (US), in order, plus the " +"mnemonic ``SP`` for the space character." +msgstr "" + +#: ../Doc/library/curses.panel.rst:2 +msgid ":mod:`curses.panel` --- A panel stack extension for curses" +msgstr "" + +#: ../Doc/library/curses.panel.rst:11 +msgid "" +"Panels are windows with the added feature of depth, so they can be stacked " +"on top of each other, and only the visible portions of each window will be " +"displayed. Panels can be added, moved up or down in the stack, and removed." +msgstr "" + +#: ../Doc/library/curses.panel.rst:21 +msgid "The module :mod:`curses.panel` defines the following functions:" +msgstr "" + +#: ../Doc/library/curses.panel.rst:26 +msgid "Returns the bottom panel in the panel stack." +msgstr "" + +#: ../Doc/library/curses.panel.rst:31 +msgid "" +"Returns a panel object, associating it with the given window *win*. Be aware " +"that you need to keep the returned panel object referenced explicitly. If " +"you don't, the panel object is garbage collected and removed from the panel " +"stack." +msgstr "" + +#: ../Doc/library/curses.panel.rst:38 +msgid "Returns the top panel in the panel stack." +msgstr "" + +#: ../Doc/library/curses.panel.rst:43 +msgid "" +"Updates the virtual screen after changes in the panel stack. This does not " +"call :func:`curses.doupdate`, so you'll have to do this yourself." +msgstr "" + +#: ../Doc/library/curses.panel.rst:50 +msgid "Panel Objects" +msgstr "" + +#: ../Doc/library/curses.panel.rst:52 +msgid "" +"Panel objects, as returned by :func:`new_panel` above, are windows with a " +"stacking order. There's always a window associated with a panel which " +"determines the content, while the panel methods are responsible for the " +"window's depth in the panel stack." +msgstr "" + +#: ../Doc/library/curses.panel.rst:57 +msgid "Panel objects have the following methods:" +msgstr "" + +#: ../Doc/library/curses.panel.rst:62 +msgid "Returns the panel above the current panel." +msgstr "" + +#: ../Doc/library/curses.panel.rst:67 +msgid "Returns the panel below the current panel." +msgstr "" + +#: ../Doc/library/curses.panel.rst:72 +msgid "Push the panel to the bottom of the stack." +msgstr "" + +#: ../Doc/library/curses.panel.rst:77 +msgid "Returns true if the panel is hidden (not visible), false otherwise." +msgstr "" + +#: ../Doc/library/curses.panel.rst:82 +msgid "" +"Hide the panel. This does not delete the object, it just makes the window on " +"screen invisible." +msgstr "" + +#: ../Doc/library/curses.panel.rst:88 +msgid "Move the panel to the screen coordinates ``(y, x)``." +msgstr "" + +#: ../Doc/library/curses.panel.rst:93 +msgid "Change the window associated with the panel to the window *win*." +msgstr "" + +#: ../Doc/library/curses.panel.rst:98 +msgid "" +"Set the panel's user pointer to *obj*. This is used to associate an " +"arbitrary piece of data with the panel, and can be any Python object." +msgstr "" + +#: ../Doc/library/curses.panel.rst:104 +msgid "Display the panel (which might have been hidden)." +msgstr "" + +#: ../Doc/library/curses.panel.rst:109 +msgid "Push panel to the top of the stack." +msgstr "" + +#: ../Doc/library/curses.panel.rst:114 +msgid "" +"Returns the user pointer for the panel. This might be any Python object." +msgstr "" + +#: ../Doc/library/curses.panel.rst:119 +msgid "Returns the window object associated with the panel." +msgstr "" + +#: ../Doc/library/custominterp.rst:5 +msgid "Custom Python Interpreters" +msgstr "" + +#: ../Doc/library/custominterp.rst:7 +msgid "" +"The modules described in this chapter allow writing interfaces similar to " +"Python's interactive interpreter. If you want a Python interpreter that " +"supports some special feature in addition to the Python language, you should " +"look at the :mod:`code` module. (The :mod:`codeop` module is lower-level, " +"used to support compiling a possibly-incomplete chunk of Python code.)" +msgstr "" + +#: ../Doc/library/custominterp.rst:13 ../Doc/library/frameworks.rst:11 +#: ../Doc/library/modules.rst:10 +msgid "The full list of modules described in this chapter is:" +msgstr "" + +#: ../Doc/library/datatypes.rst:5 +msgid "Data Types" +msgstr "" + +#: ../Doc/library/datatypes.rst:7 +msgid "" +"The modules described in this chapter provide a variety of specialized data " +"types such as dates and times, fixed-type arrays, heap queues, synchronized " +"queues, and sets." +msgstr "" + +#: ../Doc/library/datatypes.rst:11 +msgid "" +"Python also provides some built-in data types, in particular, :class:" +"`dict`, :class:`list`, :class:`set` and :class:`frozenset`, and :class:" +"`tuple`. The :class:`str` class is used to hold Unicode strings, and the :" +"class:`bytes` class is used to hold binary data." +msgstr "" + +#: ../Doc/library/datatypes.rst:16 ../Doc/library/functional.rst:8 +#: ../Doc/library/numeric.rst:15 +msgid "The following modules are documented in this chapter:" +msgstr "" + +#: ../Doc/library/datetime.rst:2 +msgid ":mod:`datetime` --- Basic date and time types" +msgstr "" + +#: ../Doc/library/datetime.rst:11 +msgid "**Source code:** :source:`Lib/datetime.py`" +msgstr "" + +#: ../Doc/library/datetime.rst:17 +msgid "" +"The :mod:`datetime` module supplies classes for manipulating dates and times " +"in both simple and complex ways. While date and time arithmetic is " +"supported, the focus of the implementation is on efficient attribute " +"extraction for output formatting and manipulation. For related " +"functionality, see also the :mod:`time` and :mod:`calendar` modules." +msgstr "" + +#: ../Doc/library/datetime.rst:23 +msgid "There are two kinds of date and time objects: \"naive\" and \"aware\"." +msgstr "" + +#: ../Doc/library/datetime.rst:25 +msgid "" +"An aware object has sufficient knowledge of applicable algorithmic and " +"political time adjustments, such as time zone and daylight saving time " +"information, to locate itself relative to other aware objects. An aware " +"object is used to represent a specific moment in time that is not open to " +"interpretation [#]_." +msgstr "" + +#: ../Doc/library/datetime.rst:31 +msgid "" +"A naive object does not contain enough information to unambiguously locate " +"itself relative to other date/time objects. Whether a naive object " +"represents Coordinated Universal Time (UTC), local time, or time in some " +"other timezone is purely up to the program, just like it is up to the " +"program whether a particular number represents metres, miles, or mass. " +"Naive objects are easy to understand and to work with, at the cost of " +"ignoring some aspects of reality." +msgstr "" + +#: ../Doc/library/datetime.rst:38 +msgid "" +"For applications requiring aware objects, :class:`.datetime` and :class:`." +"time` objects have an optional time zone information attribute, :attr:`!" +"tzinfo`, that can be set to an instance of a subclass of the abstract :class:" +"`tzinfo` class. These :class:`tzinfo` objects capture information about the " +"offset from UTC time, the time zone name, and whether Daylight Saving Time " +"is in effect. Note that only one concrete :class:`tzinfo` class, the :class:" +"`timezone` class, is supplied by the :mod:`datetime` module. The :class:" +"`timezone` class can represent simple timezones with fixed offset from UTC, " +"such as UTC itself or North American EST and EDT timezones. Supporting " +"timezones at deeper levels of detail is up to the application. The rules " +"for time adjustment across the world are more political than rational, " +"change frequently, and there is no standard suitable for every application " +"aside from UTC." +msgstr "" + +#: ../Doc/library/datetime.rst:51 +msgid "The :mod:`datetime` module exports the following constants:" +msgstr "" + +#: ../Doc/library/datetime.rst:55 +msgid "" +"The smallest year number allowed in a :class:`date` or :class:`.datetime` " +"object. :const:`MINYEAR` is ``1``." +msgstr "" + +#: ../Doc/library/datetime.rst:61 +msgid "" +"The largest year number allowed in a :class:`date` or :class:`.datetime` " +"object. :const:`MAXYEAR` is ``9999``." +msgstr "" + +#: ../Doc/library/datetime.rst:68 ../Doc/library/time.rst:688 +msgid "Module :mod:`calendar`" +msgstr "" + +#: ../Doc/library/datetime.rst:68 +msgid "General calendar related functions." +msgstr "" + +#: ../Doc/library/datetime.rst:71 +msgid "Time access and conversions." +msgstr "" + +#: ../Doc/library/datetime.rst:75 +msgid "Available Types" +msgstr "" + +#: ../Doc/library/datetime.rst:80 +msgid "" +"An idealized naive date, assuming the current Gregorian calendar always was, " +"and always will be, in effect. Attributes: :attr:`year`, :attr:`month`, and :" +"attr:`day`." +msgstr "" + +#: ../Doc/library/datetime.rst:88 +msgid "" +"An idealized time, independent of any particular day, assuming that every " +"day has exactly 24\\*60\\*60 seconds (there is no notion of \"leap seconds\" " +"here). Attributes: :attr:`hour`, :attr:`minute`, :attr:`second`, :attr:" +"`microsecond`, and :attr:`.tzinfo`." +msgstr "" + +#: ../Doc/library/datetime.rst:97 +msgid "" +"A combination of a date and a time. Attributes: :attr:`year`, :attr:" +"`month`, :attr:`day`, :attr:`hour`, :attr:`minute`, :attr:`second`, :attr:" +"`microsecond`, and :attr:`.tzinfo`." +msgstr "" + +#: ../Doc/library/datetime.rst:105 +msgid "" +"A duration expressing the difference between two :class:`date`, :class:`." +"time`, or :class:`.datetime` instances to microsecond resolution." +msgstr "" + +#: ../Doc/library/datetime.rst:112 +msgid "" +"An abstract base class for time zone information objects. These are used by " +"the :class:`.datetime` and :class:`.time` classes to provide a customizable " +"notion of time adjustment (for example, to account for time zone and/or " +"daylight saving time)." +msgstr "" + +#: ../Doc/library/datetime.rst:120 +msgid "" +"A class that implements the :class:`tzinfo` abstract base class as a fixed " +"offset from the UTC." +msgstr "" + +#: ../Doc/library/datetime.rst:126 +msgid "Objects of these types are immutable." +msgstr "" + +#: ../Doc/library/datetime.rst:128 +msgid "Objects of the :class:`date` type are always naive." +msgstr "" + +#: ../Doc/library/datetime.rst:130 +msgid "" +"An object of type :class:`.time` or :class:`.datetime` may be naive or " +"aware. A :class:`.datetime` object *d* is aware if ``d.tzinfo`` is not " +"``None`` and ``d.tzinfo.utcoffset(d)`` does not return ``None``. If ``d." +"tzinfo`` is ``None``, or if ``d.tzinfo`` is not ``None`` but ``d.tzinfo." +"utcoffset(d)`` returns ``None``, *d* is naive. A :class:`.time` object *t* " +"is aware if ``t.tzinfo`` is not ``None`` and ``t.tzinfo.utcoffset(None)`` " +"does not return ``None``. Otherwise, *t* is naive." +msgstr "" + +#: ../Doc/library/datetime.rst:138 +msgid "" +"The distinction between naive and aware doesn't apply to :class:`timedelta` " +"objects." +msgstr "" + +#: ../Doc/library/datetime.rst:141 +msgid "Subclass relationships::" +msgstr "" + +#: ../Doc/library/datetime.rst:155 +msgid ":class:`timedelta` Objects" +msgstr "" + +#: ../Doc/library/datetime.rst:157 +msgid "" +"A :class:`timedelta` object represents a duration, the difference between " +"two dates or times." +msgstr "" + +#: ../Doc/library/datetime.rst:162 +msgid "" +"All arguments are optional and default to ``0``. Arguments may be integers " +"or floats, and may be positive or negative." +msgstr "" + +#: ../Doc/library/datetime.rst:165 +msgid "" +"Only *days*, *seconds* and *microseconds* are stored internally. Arguments " +"are converted to those units:" +msgstr "" + +#: ../Doc/library/datetime.rst:168 +msgid "A millisecond is converted to 1000 microseconds." +msgstr "" + +#: ../Doc/library/datetime.rst:169 +msgid "A minute is converted to 60 seconds." +msgstr "" + +#: ../Doc/library/datetime.rst:170 +msgid "An hour is converted to 3600 seconds." +msgstr "" + +#: ../Doc/library/datetime.rst:171 +msgid "A week is converted to 7 days." +msgstr "" + +#: ../Doc/library/datetime.rst:173 +msgid "" +"and days, seconds and microseconds are then normalized so that the " +"representation is unique, with" +msgstr "" + +#: ../Doc/library/datetime.rst:176 +msgid "``0 <= microseconds < 1000000``" +msgstr "" + +#: ../Doc/library/datetime.rst:177 +msgid "``0 <= seconds < 3600*24`` (the number of seconds in one day)" +msgstr "" + +#: ../Doc/library/datetime.rst:178 +msgid "``-999999999 <= days <= 999999999``" +msgstr "" + +#: ../Doc/library/datetime.rst:180 +msgid "" +"If any argument is a float and there are fractional microseconds, the " +"fractional microseconds left over from all arguments are combined and their " +"sum is rounded to the nearest microsecond using round-half-to-even " +"tiebreaker. If no argument is a float, the conversion and normalization " +"processes are exact (no information is lost)." +msgstr "" + +#: ../Doc/library/datetime.rst:187 +msgid "" +"If the normalized value of days lies outside the indicated range, :exc:" +"`OverflowError` is raised." +msgstr "" + +#: ../Doc/library/datetime.rst:190 +msgid "" +"Note that normalization of negative values may be surprising at first. For " +"example," +msgstr "" + +#: ../Doc/library/datetime.rst:199 +msgid "Class attributes are:" +msgstr "" + +#: ../Doc/library/datetime.rst:203 +msgid "The most negative :class:`timedelta` object, ``timedelta(-999999999)``." +msgstr "" + +#: ../Doc/library/datetime.rst:208 +msgid "" +"The most positive :class:`timedelta` object, ``timedelta(days=999999999, " +"hours=23, minutes=59, seconds=59, microseconds=999999)``." +msgstr "" + +#: ../Doc/library/datetime.rst:214 +msgid "" +"The smallest possible difference between non-equal :class:`timedelta` " +"objects, ``timedelta(microseconds=1)``." +msgstr "" + +#: ../Doc/library/datetime.rst:217 +msgid "" +"Note that, because of normalization, ``timedelta.max`` > ``-timedelta.min``. " +"``-timedelta.max`` is not representable as a :class:`timedelta` object." +msgstr "" + +#: ../Doc/library/datetime.rst:220 ../Doc/library/datetime.rst:456 +#: ../Doc/library/datetime.rst:852 ../Doc/library/datetime.rst:1412 +msgid "Instance attributes (read-only):" +msgstr "" + +#: ../Doc/library/datetime.rst:225 +msgid "``days``" +msgstr "" + +#: ../Doc/library/datetime.rst:225 +msgid "Between -999999999 and 999999999 inclusive" +msgstr "" + +#: ../Doc/library/datetime.rst:227 +msgid "``seconds``" +msgstr "" + +#: ../Doc/library/datetime.rst:227 +msgid "Between 0 and 86399 inclusive" +msgstr "" + +#: ../Doc/library/datetime.rst:229 +msgid "``microseconds``" +msgstr "" + +#: ../Doc/library/datetime.rst:229 +msgid "Between 0 and 999999 inclusive" +msgstr "" + +#: ../Doc/library/datetime.rst:232 ../Doc/library/datetime.rst:473 +#: ../Doc/library/datetime.rst:905 ../Doc/library/datetime.rst:1451 +msgid "Supported operations:" +msgstr "" + +#: ../Doc/library/datetime.rst:237 ../Doc/library/datetime.rst:476 +#: ../Doc/library/datetime.rst:908 ../Doc/library/operator.rst:364 +#: ../Doc/library/stdtypes.rst:90 ../Doc/library/stdtypes.rst:148 +#: ../Doc/library/stdtypes.rst:276 ../Doc/library/stdtypes.rst:365 +#: ../Doc/library/stdtypes.rst:413 ../Doc/library/stdtypes.rst:849 +#: ../Doc/library/stdtypes.rst:1042 +msgid "Operation" +msgstr "" + +#: ../Doc/library/datetime.rst:237 ../Doc/library/datetime.rst:476 +#: ../Doc/library/datetime.rst:908 ../Doc/library/stdtypes.rst:90 +#: ../Doc/library/stdtypes.rst:276 ../Doc/library/stdtypes.rst:365 +#: ../Doc/library/stdtypes.rst:413 ../Doc/library/stdtypes.rst:849 +#: ../Doc/library/stdtypes.rst:1042 +msgid "Result" +msgstr "" + +#: ../Doc/library/datetime.rst:239 +msgid "``t1 = t2 + t3``" +msgstr "" + +#: ../Doc/library/datetime.rst:239 +msgid "" +"Sum of *t2* and *t3*. Afterwards *t1*-*t2* == *t3* and *t1*-*t3* == *t2* are " +"true. (1)" +msgstr "" + +#: ../Doc/library/datetime.rst:242 +msgid "``t1 = t2 - t3``" +msgstr "" + +#: ../Doc/library/datetime.rst:242 +msgid "" +"Difference of *t2* and *t3*. Afterwards *t1* == *t2* - *t3* and *t2* == *t1* " +"+ *t3* are true. (1)" +msgstr "" + +#: ../Doc/library/datetime.rst:246 +msgid "``t1 = t2 * i or t1 = i * t2``" +msgstr "" + +#: ../Doc/library/datetime.rst:246 +msgid "" +"Delta multiplied by an integer. Afterwards *t1* // i == *t2* is true, " +"provided ``i != 0``." +msgstr "" + +#: ../Doc/library/datetime.rst:250 +msgid "In general, *t1* \\* i == *t1* \\* (i-1) + *t1* is true. (1)" +msgstr "" + +#: ../Doc/library/datetime.rst:253 +msgid "``t1 = t2 * f or t1 = f * t2``" +msgstr "" + +#: ../Doc/library/datetime.rst:253 +msgid "" +"Delta multiplied by a float. The result is rounded to the nearest multiple " +"of timedelta.resolution using round-half-to-even." +msgstr "" + +#: ../Doc/library/datetime.rst:257 +msgid "``f = t2 / t3``" +msgstr "" + +#: ../Doc/library/datetime.rst:257 +msgid "Division (3) of *t2* by *t3*. Returns a :class:`float` object." +msgstr "" + +#: ../Doc/library/datetime.rst:260 +msgid "``t1 = t2 / f or t1 = t2 / i``" +msgstr "" + +#: ../Doc/library/datetime.rst:260 +msgid "" +"Delta divided by a float or an int. The result is rounded to the nearest " +"multiple of timedelta.resolution using round-half-to-even." +msgstr "" + +#: ../Doc/library/datetime.rst:264 +msgid "``t1 = t2 // i`` or ``t1 = t2 // t3``" +msgstr "" + +#: ../Doc/library/datetime.rst:264 +msgid "" +"The floor is computed and the remainder (if any) is thrown away. In the " +"second case, an integer is returned. (3)" +msgstr "" + +#: ../Doc/library/datetime.rst:268 +msgid "``t1 = t2 % t3``" +msgstr "" + +#: ../Doc/library/datetime.rst:268 +msgid "The remainder is computed as a :class:`timedelta` object. (3)" +msgstr "" + +#: ../Doc/library/datetime.rst:271 +msgid "``q, r = divmod(t1, t2)``" +msgstr "" + +#: ../Doc/library/datetime.rst:271 +msgid "" +"Computes the quotient and the remainder: ``q = t1 // t2`` (3) and ``r = t1 % " +"t2``. q is an integer and r is a :class:`timedelta` object." +msgstr "" + +#: ../Doc/library/datetime.rst:276 +msgid "``+t1``" +msgstr "" + +#: ../Doc/library/datetime.rst:276 +msgid "Returns a :class:`timedelta` object with the same value. (2)" +msgstr "" + +#: ../Doc/library/datetime.rst:279 +msgid "``-t1``" +msgstr "" + +#: ../Doc/library/datetime.rst:279 +msgid "" +"equivalent to :class:`timedelta`\\ (-*t1.days*, -*t1.seconds*, -*t1." +"microseconds*), and to *t1*\\* -1. (1)(4)" +msgstr "" + +#: ../Doc/library/datetime.rst:283 +msgid "``abs(t)``" +msgstr "" + +#: ../Doc/library/datetime.rst:283 +msgid "" +"equivalent to +\\ *t* when ``t.days >= 0``, and to -*t* when ``t.days < 0``. " +"(2)" +msgstr "" + +#: ../Doc/library/datetime.rst:286 +msgid "``str(t)``" +msgstr "" + +#: ../Doc/library/datetime.rst:286 +msgid "" +"Returns a string in the form ``[D day[s], ][H]H:MM:SS[.UUUUUU]``, where D is " +"negative for negative ``t``. (5)" +msgstr "" + +#: ../Doc/library/datetime.rst:290 +msgid "``repr(t)``" +msgstr "" + +#: ../Doc/library/datetime.rst:290 +msgid "" +"Returns a string in the form ``datetime.timedelta(D[, S[, U]])``, where D is " +"negative for negative ``t``. (5)" +msgstr "" + +#: ../Doc/library/datetime.rst:298 +msgid "This is exact, but may overflow." +msgstr "" + +#: ../Doc/library/datetime.rst:301 +msgid "This is exact, and cannot overflow." +msgstr "" + +#: ../Doc/library/datetime.rst:304 +msgid "Division by 0 raises :exc:`ZeroDivisionError`." +msgstr "" + +#: ../Doc/library/datetime.rst:307 +msgid "-*timedelta.max* is not representable as a :class:`timedelta` object." +msgstr "" + +#: ../Doc/library/datetime.rst:310 +msgid "" +"String representations of :class:`timedelta` objects are normalized " +"similarly to their internal representation. This leads to somewhat unusual " +"results for negative timedeltas. For example:" +msgstr "" + +#: ../Doc/library/datetime.rst:319 +msgid "" +"In addition to the operations listed above :class:`timedelta` objects " +"support certain additions and subtractions with :class:`date` and :class:`." +"datetime` objects (see below)." +msgstr "" + +#: ../Doc/library/datetime.rst:323 +msgid "" +"Floor division and true division of a :class:`timedelta` object by another :" +"class:`timedelta` object are now supported, as are remainder operations and " +"the :func:`divmod` function. True division and multiplication of a :class:" +"`timedelta` object by a :class:`float` object are now supported." +msgstr "" + +#: ../Doc/library/datetime.rst:330 +msgid "" +"Comparisons of :class:`timedelta` objects are supported with the :class:" +"`timedelta` object representing the smaller duration considered to be the " +"smaller timedelta. In order to stop mixed-type comparisons from falling back " +"to the default comparison by object address, when a :class:`timedelta` " +"object is compared to an object of a different type, :exc:`TypeError` is " +"raised unless the comparison is ``==`` or ``!=``. The latter cases return :" +"const:`False` or :const:`True`, respectively." +msgstr "" + +#: ../Doc/library/datetime.rst:338 +msgid "" +":class:`timedelta` objects are :term:`hashable` (usable as dictionary keys), " +"support efficient pickling, and in Boolean contexts, a :class:`timedelta` " +"object is considered to be true if and only if it isn't equal to " +"``timedelta(0)``." +msgstr "" + +#: ../Doc/library/datetime.rst:342 ../Doc/library/datetime.rst:523 +#: ../Doc/library/datetime.rst:984 ../Doc/library/datetime.rst:1484 +msgid "Instance methods:" +msgstr "" + +#: ../Doc/library/datetime.rst:346 +msgid "" +"Return the total number of seconds contained in the duration. Equivalent to " +"``td / timedelta(seconds=1)``." +msgstr "" + +#: ../Doc/library/datetime.rst:349 +msgid "" +"Note that for very large time intervals (greater than 270 years on most " +"platforms) this method will lose microsecond accuracy." +msgstr "" + +#: ../Doc/library/datetime.rst:355 +msgid "Example usage:" +msgstr "" + +#: ../Doc/library/datetime.rst:381 +msgid ":class:`date` Objects" +msgstr "" + +#: ../Doc/library/datetime.rst:383 +msgid "" +"A :class:`date` object represents a date (year, month and day) in an " +"idealized calendar, the current Gregorian calendar indefinitely extended in " +"both directions. January 1 of year 1 is called day number 1, January 2 of " +"year 1 is called day number 2, and so on. This matches the definition of " +"the \"proleptic Gregorian\" calendar in Dershowitz and Reingold's book " +"Calendrical Calculations, where it's the base calendar for all " +"computations. See the book for algorithms for converting between proleptic " +"Gregorian ordinals and many other calendar systems." +msgstr "" + +#: ../Doc/library/datetime.rst:395 +msgid "" +"All arguments are required. Arguments may be integers, in the following " +"ranges:" +msgstr "" + +#: ../Doc/library/datetime.rst:398 +msgid "``MINYEAR <= year <= MAXYEAR``" +msgstr "" + +#: ../Doc/library/datetime.rst:399 +msgid "``1 <= month <= 12``" +msgstr "" + +#: ../Doc/library/datetime.rst:400 +msgid "``1 <= day <= number of days in the given month and year``" +msgstr "" + +#: ../Doc/library/datetime.rst:402 ../Doc/library/datetime.rst:701 +msgid "" +"If an argument outside those ranges is given, :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/datetime.rst:405 ../Doc/library/datetime.rst:706 +msgid "Other constructors, all class methods:" +msgstr "" + +#: ../Doc/library/datetime.rst:409 +msgid "" +"Return the current local date. This is equivalent to ``date." +"fromtimestamp(time.time())``." +msgstr "" + +#: ../Doc/library/datetime.rst:415 +msgid "" +"Return the local date corresponding to the POSIX timestamp, such as is " +"returned by :func:`time.time`. This may raise :exc:`OverflowError`, if the " +"timestamp is out of the range of values supported by the platform C :c:func:" +"`localtime` function, and :exc:`OSError` on :c:func:`localtime` failure. " +"It's common for this to be restricted to years from 1970 through 2038. Note " +"that on non-POSIX systems that include leap seconds in their notion of a " +"timestamp, leap seconds are ignored by :meth:`fromtimestamp`." +msgstr "" + +#: ../Doc/library/datetime.rst:423 +msgid "" +"Raise :exc:`OverflowError` instead of :exc:`ValueError` if the timestamp is " +"out of the range of values supported by the platform C :c:func:`localtime` " +"function. Raise :exc:`OSError` instead of :exc:`ValueError` on :c:func:" +"`localtime` failure." +msgstr "" + +#: ../Doc/library/datetime.rst:432 +msgid "" +"Return the date corresponding to the proleptic Gregorian ordinal, where " +"January 1 of year 1 has ordinal 1. :exc:`ValueError` is raised unless ``1 " +"<= ordinal <= date.max.toordinal()``. For any date *d*, ``date.fromordinal(d." +"toordinal()) == d``." +msgstr "" + +#: ../Doc/library/datetime.rst:438 ../Doc/library/datetime.rst:832 +#: ../Doc/library/datetime.rst:1392 ../Doc/library/datetime.rst:1924 +msgid "Class attributes:" +msgstr "" + +#: ../Doc/library/datetime.rst:442 +msgid "The earliest representable date, ``date(MINYEAR, 1, 1)``." +msgstr "" + +#: ../Doc/library/datetime.rst:447 +msgid "The latest representable date, ``date(MAXYEAR, 12, 31)``." +msgstr "" + +#: ../Doc/library/datetime.rst:452 +msgid "" +"The smallest possible difference between non-equal date objects, " +"``timedelta(days=1)``." +msgstr "" + +#: ../Doc/library/datetime.rst:460 ../Doc/library/datetime.rst:856 +msgid "Between :const:`MINYEAR` and :const:`MAXYEAR` inclusive." +msgstr "" + +#: ../Doc/library/datetime.rst:465 ../Doc/library/datetime.rst:861 +msgid "Between 1 and 12 inclusive." +msgstr "" + +#: ../Doc/library/datetime.rst:470 ../Doc/library/datetime.rst:866 +msgid "Between 1 and the number of days in the given month of the given year." +msgstr "" + +#: ../Doc/library/datetime.rst:478 +msgid "``date2 = date1 + timedelta``" +msgstr "" + +#: ../Doc/library/datetime.rst:478 +msgid "*date2* is ``timedelta.days`` days removed from *date1*. (1)" +msgstr "" + +#: ../Doc/library/datetime.rst:481 +msgid "``date2 = date1 - timedelta``" +msgstr "" + +#: ../Doc/library/datetime.rst:481 +msgid "Computes *date2* such that ``date2 + timedelta == date1``. (2)" +msgstr "" + +#: ../Doc/library/datetime.rst:484 +msgid "``timedelta = date1 - date2``" +msgstr "" + +#: ../Doc/library/datetime.rst:484 ../Doc/library/datetime.rst:914 +#: ../Doc/library/stdtypes.rst:98 ../Doc/library/stdtypes.rst:863 +#: ../Doc/library/stdtypes.rst:1084 ../Doc/library/stdtypes.rst:2167 +#: ../Doc/library/stdtypes.rst:2169 ../Doc/library/stdtypes.rst:2171 +#: ../Doc/library/stdtypes.rst:2173 ../Doc/library/stdtypes.rst:3267 +#: ../Doc/library/stdtypes.rst:3269 ../Doc/library/stdtypes.rst:3271 +#: ../Doc/library/stdtypes.rst:3273 ../Doc/library/struct.rst:194 +#: ../Doc/library/struct.rst:198 ../Doc/library/struct.rst:200 +#: ../Doc/library/struct.rst:202 ../Doc/library/struct.rst:204 +#: ../Doc/library/struct.rst:206 ../Doc/library/struct.rst:208 +#: ../Doc/library/time.rst:419 ../Doc/library/time.rst:430 +#: ../Doc/library/webbrowser.rst:139 ../Doc/library/webbrowser.rst:141 +msgid "\\(3)" +msgstr "" + +#: ../Doc/library/datetime.rst:486 +msgid "``date1 < date2``" +msgstr "" + +#: ../Doc/library/datetime.rst:486 +msgid "" +"*date1* is considered less than *date2* when *date1* precedes *date2* in " +"time. (4)" +msgstr "" + +#: ../Doc/library/datetime.rst:493 +msgid "" +"*date2* is moved forward in time if ``timedelta.days > 0``, or backward if " +"``timedelta.days < 0``. Afterward ``date2 - date1 == timedelta.days``. " +"``timedelta.seconds`` and ``timedelta.microseconds`` are ignored. :exc:" +"`OverflowError` is raised if ``date2.year`` would be smaller than :const:" +"`MINYEAR` or larger than :const:`MAXYEAR`." +msgstr "" + +#: ../Doc/library/datetime.rst:500 +msgid "" +"This isn't quite equivalent to date1 + (-timedelta), because -timedelta in " +"isolation can overflow in cases where date1 - timedelta does not. " +"``timedelta.seconds`` and ``timedelta.microseconds`` are ignored." +msgstr "" + +#: ../Doc/library/datetime.rst:505 +msgid "" +"This is exact, and cannot overflow. timedelta.seconds and timedelta." +"microseconds are 0, and date2 + timedelta == date1 after." +msgstr "" + +#: ../Doc/library/datetime.rst:509 +msgid "" +"In other words, ``date1 < date2`` if and only if ``date1.toordinal() < date2." +"toordinal()``. In order to stop comparison from falling back to the default " +"scheme of comparing object addresses, date comparison normally raises :exc:" +"`TypeError` if the other comparand isn't also a :class:`date` object. " +"However, ``NotImplemented`` is returned instead if the other comparand has " +"a :meth:`timetuple` attribute. This hook gives other kinds of date objects " +"a chance at implementing mixed-type comparison. If not, when a :class:`date` " +"object is compared to an object of a different type, :exc:`TypeError` is " +"raised unless the comparison is ``==`` or ``!=``. The latter cases return :" +"const:`False` or :const:`True`, respectively." +msgstr "" + +#: ../Doc/library/datetime.rst:520 +msgid "" +"Dates can be used as dictionary keys. In Boolean contexts, all :class:`date` " +"objects are considered to be true." +msgstr "" + +#: ../Doc/library/datetime.rst:527 +msgid "" +"Return a date with the same value, except for those parameters given new " +"values by whichever keyword arguments are specified. For example, if ``d == " +"date(2002, 12, 31)``, then ``d.replace(day=26) == date(2002, 12, 26)``." +msgstr "" + +#: ../Doc/library/datetime.rst:534 +msgid "" +"Return a :class:`time.struct_time` such as returned by :func:`time." +"localtime`. The hours, minutes and seconds are 0, and the DST flag is -1. " +"``d.timetuple()`` is equivalent to ``time.struct_time((d.year, d.month, d." +"day, 0, 0, 0, d.weekday(), yday, -1))``, where ``yday = d.toordinal() - " +"date(d.year, 1, 1).toordinal() + 1`` is the day number within the current " +"year starting with ``1`` for January 1st." +msgstr "" + +#: ../Doc/library/datetime.rst:544 +msgid "" +"Return the proleptic Gregorian ordinal of the date, where January 1 of year " +"1 has ordinal 1. For any :class:`date` object *d*, ``date.fromordinal(d." +"toordinal()) == d``." +msgstr "" + +#: ../Doc/library/datetime.rst:551 +msgid "" +"Return the day of the week as an integer, where Monday is 0 and Sunday is 6. " +"For example, ``date(2002, 12, 4).weekday() == 2``, a Wednesday. See also :" +"meth:`isoweekday`." +msgstr "" + +#: ../Doc/library/datetime.rst:558 +msgid "" +"Return the day of the week as an integer, where Monday is 1 and Sunday is 7. " +"For example, ``date(2002, 12, 4).isoweekday() == 3``, a Wednesday. See also :" +"meth:`weekday`, :meth:`isocalendar`." +msgstr "" + +#: ../Doc/library/datetime.rst:565 +msgid "Return a 3-tuple, (ISO year, ISO week number, ISO weekday)." +msgstr "" + +#: ../Doc/library/datetime.rst:567 +msgid "" +"The ISO calendar is a widely used variant of the Gregorian calendar. See " +"https://www.staff.science.uu.nl/~gent0113/calendar/isocalendar.htm for a " +"good explanation." +msgstr "" + +#: ../Doc/library/datetime.rst:571 +msgid "" +"The ISO year consists of 52 or 53 full weeks, and where a week starts on a " +"Monday and ends on a Sunday. The first week of an ISO year is the first " +"(Gregorian) calendar week of a year containing a Thursday. This is called " +"week number 1, and the ISO year of that Thursday is the same as its " +"Gregorian year." +msgstr "" + +#: ../Doc/library/datetime.rst:576 +msgid "" +"For example, 2004 begins on a Thursday, so the first week of ISO year 2004 " +"begins on Monday, 29 Dec 2003 and ends on Sunday, 4 Jan 2004, so that " +"``date(2003, 12, 29).isocalendar() == (2004, 1, 1)`` and ``date(2004, 1, 4)." +"isocalendar() == (2004, 1, 7)``." +msgstr "" + +#: ../Doc/library/datetime.rst:584 +msgid "" +"Return a string representing the date in ISO 8601 format, 'YYYY-MM-DD'. For " +"example, ``date(2002, 12, 4).isoformat() == '2002-12-04'``." +msgstr "" + +#: ../Doc/library/datetime.rst:590 +msgid "For a date *d*, ``str(d)`` is equivalent to ``d.isoformat()``." +msgstr "" + +#: ../Doc/library/datetime.rst:595 +msgid "" +"Return a string representing the date, for example ``date(2002, 12, 4)." +"ctime() == 'Wed Dec 4 00:00:00 2002'``. ``d.ctime()`` is equivalent to " +"``time.ctime(time.mktime(d.timetuple()))`` on platforms where the native C :" +"c:func:`ctime` function (which :func:`time.ctime` invokes, but which :meth:" +"`date.ctime` does not invoke) conforms to the C standard." +msgstr "" + +#: ../Doc/library/datetime.rst:604 +msgid "" +"Return a string representing the date, controlled by an explicit format " +"string. Format codes referring to hours, minutes or seconds will see 0 " +"values. For a complete list of formatting directives, see :ref:`strftime-" +"strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:612 +msgid "" +"Same as :meth:`.date.strftime`. This makes it possible to specify a format " +"string for a :class:`.date` object in :ref:`formatted string literals ` and when using :meth:`str.format`. For a complete list of " +"formatting directives, see :ref:`strftime-strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:619 +msgid "Example of counting days to an event::" +msgstr "" + +#: ../Doc/library/datetime.rst:637 +msgid "Example of working with :class:`date`:" +msgstr "" + +#: ../Doc/library/datetime.rst:676 +msgid ":class:`.datetime` Objects" +msgstr "" + +#: ../Doc/library/datetime.rst:678 +msgid "" +"A :class:`.datetime` object is a single object containing all the " +"information from a :class:`date` object and a :class:`.time` object. Like " +"a :class:`date` object, :class:`.datetime` assumes the current Gregorian " +"calendar extended in both directions; like a time object, :class:`.datetime` " +"assumes there are exactly 3600\\*24 seconds in every day." +msgstr "" + +#: ../Doc/library/datetime.rst:684 +msgid "Constructor:" +msgstr "" + +#: ../Doc/library/datetime.rst:688 +msgid "" +"The year, month and day arguments are required. *tzinfo* may be ``None``, " +"or an instance of a :class:`tzinfo` subclass. The remaining arguments may " +"be integers, in the following ranges:" +msgstr "" + +#: ../Doc/library/datetime.rst:692 +msgid "``MINYEAR <= year <= MAXYEAR``," +msgstr "" + +#: ../Doc/library/datetime.rst:693 +msgid "``1 <= month <= 12``," +msgstr "" + +#: ../Doc/library/datetime.rst:694 +msgid "``1 <= day <= number of days in the given month and year``," +msgstr "" + +#: ../Doc/library/datetime.rst:695 ../Doc/library/datetime.rst:1383 +msgid "``0 <= hour < 24``," +msgstr "" + +#: ../Doc/library/datetime.rst:696 ../Doc/library/datetime.rst:1384 +msgid "``0 <= minute < 60``," +msgstr "" + +#: ../Doc/library/datetime.rst:697 ../Doc/library/datetime.rst:1385 +msgid "``0 <= second < 60``," +msgstr "" + +#: ../Doc/library/datetime.rst:698 ../Doc/library/datetime.rst:1386 +msgid "``0 <= microsecond < 1000000``," +msgstr "" + +#: ../Doc/library/datetime.rst:699 ../Doc/library/datetime.rst:1387 +msgid "``fold in [0, 1]``." +msgstr "" + +#: ../Doc/library/datetime.rst:703 ../Doc/library/datetime.rst:1018 +#: ../Doc/library/datetime.rst:1494 +msgid "Added the ``fold`` argument." +msgstr "" + +#: ../Doc/library/datetime.rst:710 +msgid "" +"Return the current local datetime, with :attr:`.tzinfo` ``None``. This is " +"equivalent to ``datetime.fromtimestamp(time.time())``. See also :meth:" +"`now`, :meth:`fromtimestamp`." +msgstr "" + +#: ../Doc/library/datetime.rst:717 +msgid "" +"Return the current local date and time. If optional argument *tz* is " +"``None`` or not specified, this is like :meth:`today`, but, if possible, " +"supplies more precision than can be gotten from going through a :func:`time." +"time` timestamp (for example, this may be possible on platforms supplying " +"the C :c:func:`gettimeofday` function)." +msgstr "" + +#: ../Doc/library/datetime.rst:723 +msgid "" +"If *tz* is not ``None``, it must be an instance of a :class:`tzinfo` " +"subclass, and the current date and time are converted to *tz*’s time zone. " +"In this case the result is equivalent to ``tz.fromutc(datetime.utcnow()." +"replace(tzinfo=tz))``. See also :meth:`today`, :meth:`utcnow`." +msgstr "" + +#: ../Doc/library/datetime.rst:731 +msgid "" +"Return the current UTC date and time, with :attr:`.tzinfo` ``None``. This is " +"like :meth:`now`, but returns the current UTC date and time, as a naive :" +"class:`.datetime` object. An aware current UTC datetime can be obtained by " +"calling ``datetime.now(timezone.utc)``. See also :meth:`now`." +msgstr "" + +#: ../Doc/library/datetime.rst:738 +msgid "" +"Return the local date and time corresponding to the POSIX timestamp, such as " +"is returned by :func:`time.time`. If optional argument *tz* is ``None`` or " +"not specified, the timestamp is converted to the platform's local date and " +"time, and the returned :class:`.datetime` object is naive." +msgstr "" + +#: ../Doc/library/datetime.rst:743 +msgid "" +"If *tz* is not ``None``, it must be an instance of a :class:`tzinfo` " +"subclass, and the timestamp is converted to *tz*’s time zone. In this case " +"the result is equivalent to ``tz.fromutc(datetime." +"utcfromtimestamp(timestamp).replace(tzinfo=tz))``." +msgstr "" + +#: ../Doc/library/datetime.rst:748 +msgid "" +":meth:`fromtimestamp` may raise :exc:`OverflowError`, if the timestamp is " +"out of the range of values supported by the platform C :c:func:`localtime` " +"or :c:func:`gmtime` functions, and :exc:`OSError` on :c:func:`localtime` or :" +"c:func:`gmtime` failure. It's common for this to be restricted to years in " +"1970 through 2038. Note that on non-POSIX systems that include leap seconds " +"in their notion of a timestamp, leap seconds are ignored by :meth:" +"`fromtimestamp`, and then it's possible to have two timestamps differing by " +"a second that yield identical :class:`.datetime` objects. See also :meth:" +"`utcfromtimestamp`." +msgstr "" + +#: ../Doc/library/datetime.rst:758 +msgid "" +"Raise :exc:`OverflowError` instead of :exc:`ValueError` if the timestamp is " +"out of the range of values supported by the platform C :c:func:`localtime` " +"or :c:func:`gmtime` functions. Raise :exc:`OSError` instead of :exc:" +"`ValueError` on :c:func:`localtime` or :c:func:`gmtime` failure." +msgstr "" + +#: ../Doc/library/datetime.rst:765 +msgid ":meth:`fromtimestamp` may return instances with :attr:`.fold` set to 1." +msgstr "" + +#: ../Doc/library/datetime.rst:770 +msgid "" +"Return the UTC :class:`.datetime` corresponding to the POSIX timestamp, " +"with :attr:`.tzinfo` ``None``. This may raise :exc:`OverflowError`, if the " +"timestamp is out of the range of values supported by the platform C :c:func:" +"`gmtime` function, and :exc:`OSError` on :c:func:`gmtime` failure. It's " +"common for this to be restricted to years in 1970 through 2038." +msgstr "" + +#: ../Doc/library/datetime.rst:776 +msgid "To get an aware :class:`.datetime` object, call :meth:`fromtimestamp`::" +msgstr "" + +#: ../Doc/library/datetime.rst:780 +msgid "" +"On the POSIX compliant platforms, it is equivalent to the following " +"expression::" +msgstr "" + +#: ../Doc/library/datetime.rst:785 +msgid "" +"except the latter formula always supports the full years range: between :" +"const:`MINYEAR` and :const:`MAXYEAR` inclusive." +msgstr "" + +#: ../Doc/library/datetime.rst:788 +msgid "" +"Raise :exc:`OverflowError` instead of :exc:`ValueError` if the timestamp is " +"out of the range of values supported by the platform C :c:func:`gmtime` " +"function. Raise :exc:`OSError` instead of :exc:`ValueError` on :c:func:" +"`gmtime` failure." +msgstr "" + +#: ../Doc/library/datetime.rst:797 +msgid "" +"Return the :class:`.datetime` corresponding to the proleptic Gregorian " +"ordinal, where January 1 of year 1 has ordinal 1. :exc:`ValueError` is " +"raised unless ``1 <= ordinal <= datetime.max.toordinal()``. The hour, " +"minute, second and microsecond of the result are all 0, and :attr:`.tzinfo` " +"is ``None``." +msgstr "" + +#: ../Doc/library/datetime.rst:805 +msgid "" +"Return a new :class:`.datetime` object whose date components are equal to " +"the given :class:`date` object's, and whose time components are equal to the " +"given :class:`.time` object's. If the *tzinfo* argument is provided, its " +"value is used to set the :attr:`.tzinfo` attribute of the result, otherwise " +"the :attr:`~.time.tzinfo` attribute of the *time* argument is used." +msgstr "" + +#: ../Doc/library/datetime.rst:812 +msgid "" +"For any :class:`.datetime` object *d*, ``d == datetime.combine(d.date(), d." +"time(), d.tzinfo)``. If date is a :class:`.datetime` object, its time " +"components and :attr:`.tzinfo` attributes are ignored." +msgstr "" + +#: ../Doc/library/datetime.rst:817 +msgid "Added the *tzinfo* argument." +msgstr "" + +#: ../Doc/library/datetime.rst:823 +msgid "" +"Return a :class:`.datetime` corresponding to *date_string*, parsed according " +"to *format*. This is equivalent to ``datetime(*(time.strptime(date_string, " +"format)[0:6]))``. :exc:`ValueError` is raised if the date_string and format " +"can't be parsed by :func:`time.strptime` or if it returns a value which " +"isn't a time tuple. For a complete list of formatting directives, see :ref:" +"`strftime-strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:836 +msgid "" +"The earliest representable :class:`.datetime`, ``datetime(MINYEAR, 1, 1, " +"tzinfo=None)``." +msgstr "" + +#: ../Doc/library/datetime.rst:842 +msgid "" +"The latest representable :class:`.datetime`, ``datetime(MAXYEAR, 12, 31, 23, " +"59, 59, 999999, tzinfo=None)``." +msgstr "" + +#: ../Doc/library/datetime.rst:848 +msgid "" +"The smallest possible difference between non-equal :class:`.datetime` " +"objects, ``timedelta(microseconds=1)``." +msgstr "" + +#: ../Doc/library/datetime.rst:871 ../Doc/library/datetime.rst:1416 +msgid "In ``range(24)``." +msgstr "" + +#: ../Doc/library/datetime.rst:876 ../Doc/library/datetime.rst:881 +#: ../Doc/library/datetime.rst:1421 ../Doc/library/datetime.rst:1426 +msgid "In ``range(60)``." +msgstr "" + +#: ../Doc/library/datetime.rst:886 ../Doc/library/datetime.rst:1431 +msgid "In ``range(1000000)``." +msgstr "" + +#: ../Doc/library/datetime.rst:891 +msgid "" +"The object passed as the *tzinfo* argument to the :class:`.datetime` " +"constructor, or ``None`` if none was passed." +msgstr "" + +#: ../Doc/library/datetime.rst:897 ../Doc/library/datetime.rst:1442 +msgid "" +"In ``[0, 1]``. Used to disambiguate wall times during a repeated interval. " +"(A repeated interval occurs when clocks are rolled back at the end of " +"daylight saving time or when the UTC offset for the current zone is " +"decreased for political reasons.) The value 0 (1) represents the earlier " +"(later) of the two moments with the same wall time representation." +msgstr "" + +#: ../Doc/library/datetime.rst:910 +msgid "``datetime2 = datetime1 + timedelta``" +msgstr "" + +#: ../Doc/library/datetime.rst:912 +msgid "``datetime2 = datetime1 - timedelta``" +msgstr "" + +#: ../Doc/library/datetime.rst:914 +msgid "``timedelta = datetime1 - datetime2``" +msgstr "" + +#: ../Doc/library/datetime.rst:916 +msgid "``datetime1 < datetime2``" +msgstr "" + +#: ../Doc/library/datetime.rst:916 +msgid "Compares :class:`.datetime` to :class:`.datetime`. (4)" +msgstr "" + +#: ../Doc/library/datetime.rst:921 +msgid "" +"datetime2 is a duration of timedelta removed from datetime1, moving forward " +"in time if ``timedelta.days`` > 0, or backward if ``timedelta.days`` < 0. " +"The result has the same :attr:`~.datetime.tzinfo` attribute as the input " +"datetime, and datetime2 - datetime1 == timedelta after. :exc:`OverflowError` " +"is raised if datetime2.year would be smaller than :const:`MINYEAR` or larger " +"than :const:`MAXYEAR`. Note that no time zone adjustments are done even if " +"the input is an aware object." +msgstr "" + +#: ../Doc/library/datetime.rst:930 +msgid "" +"Computes the datetime2 such that datetime2 + timedelta == datetime1. As for " +"addition, the result has the same :attr:`~.datetime.tzinfo` attribute as the " +"input datetime, and no time zone adjustments are done even if the input is " +"aware. This isn't quite equivalent to datetime1 + (-timedelta), because -" +"timedelta in isolation can overflow in cases where datetime1 - timedelta " +"does not." +msgstr "" + +#: ../Doc/library/datetime.rst:937 +msgid "" +"Subtraction of a :class:`.datetime` from a :class:`.datetime` is defined " +"only if both operands are naive, or if both are aware. If one is aware and " +"the other is naive, :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/datetime.rst:941 +msgid "" +"If both are naive, or both are aware and have the same :attr:`~.datetime." +"tzinfo` attribute, the :attr:`~.datetime.tzinfo` attributes are ignored, and " +"the result is a :class:`timedelta` object *t* such that ``datetime2 + t == " +"datetime1``. No time zone adjustments are done in this case." +msgstr "" + +#: ../Doc/library/datetime.rst:946 +msgid "" +"If both are aware and have different :attr:`~.datetime.tzinfo` attributes, " +"``a-b`` acts as if *a* and *b* were first converted to naive UTC datetimes " +"first. The result is ``(a.replace(tzinfo=None) - a.utcoffset()) - (b." +"replace(tzinfo=None) - b.utcoffset())`` except that the implementation never " +"overflows." +msgstr "" + +#: ../Doc/library/datetime.rst:952 +msgid "" +"*datetime1* is considered less than *datetime2* when *datetime1* precedes " +"*datetime2* in time." +msgstr "" + +#: ../Doc/library/datetime.rst:955 +msgid "" +"If one comparand is naive and the other is aware, :exc:`TypeError` is raised " +"if an order comparison is attempted. For equality comparisons, naive " +"instances are never equal to aware instances." +msgstr "" + +#: ../Doc/library/datetime.rst:959 +msgid "" +"If both comparands are aware, and have the same :attr:`~.datetime.tzinfo` " +"attribute, the common :attr:`~.datetime.tzinfo` attribute is ignored and the " +"base datetimes are compared. If both comparands are aware and have " +"different :attr:`~.datetime.tzinfo` attributes, the comparands are first " +"adjusted by subtracting their UTC offsets (obtained from ``self." +"utcoffset()``)." +msgstr "" + +#: ../Doc/library/datetime.rst:965 +msgid "" +"Equality comparisons between naive and aware :class:`.datetime` instances " +"don't raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/datetime.rst:971 +msgid "" +"In order to stop comparison from falling back to the default scheme of " +"comparing object addresses, datetime comparison normally raises :exc:" +"`TypeError` if the other comparand isn't also a :class:`.datetime` object. " +"However, ``NotImplemented`` is returned instead if the other comparand has " +"a :meth:`timetuple` attribute. This hook gives other kinds of date objects " +"a chance at implementing mixed-type comparison. If not, when a :class:`." +"datetime` object is compared to an object of a different type, :exc:" +"`TypeError` is raised unless the comparison is ``==`` or ``!=``. The latter " +"cases return :const:`False` or :const:`True`, respectively." +msgstr "" + +#: ../Doc/library/datetime.rst:981 +msgid "" +":class:`.datetime` objects can be used as dictionary keys. In Boolean " +"contexts, all :class:`.datetime` objects are considered to be true." +msgstr "" + +#: ../Doc/library/datetime.rst:988 +msgid "Return :class:`date` object with same year, month and day." +msgstr "" + +#: ../Doc/library/datetime.rst:993 +msgid "" +"Return :class:`.time` object with same hour, minute, second, microsecond and " +"fold. :attr:`.tzinfo` is ``None``. See also method :meth:`timetz`." +msgstr "" + +#: ../Doc/library/datetime.rst:996 ../Doc/library/datetime.rst:1005 +msgid "The fold value is copied to the returned :class:`.time` object." +msgstr "" + +#: ../Doc/library/datetime.rst:1002 +msgid "" +"Return :class:`.time` object with same hour, minute, second, microsecond, " +"fold, and tzinfo attributes. See also method :meth:`time`." +msgstr "" + +#: ../Doc/library/datetime.rst:1013 +msgid "" +"Return a datetime with the same attributes, except for those attributes " +"given new values by whichever keyword arguments are specified. Note that " +"``tzinfo=None`` can be specified to create a naive datetime from an aware " +"datetime with no conversion of date and time data." +msgstr "" + +#: ../Doc/library/datetime.rst:1024 +msgid "" +"Return a :class:`.datetime` object with new :attr:`.tzinfo` attribute *tz*, " +"adjusting the date and time data so the result is the same UTC time as " +"*self*, but in *tz*'s local time." +msgstr "" + +#: ../Doc/library/datetime.rst:1028 +msgid "" +"If provided, *tz* must be an instance of a :class:`tzinfo` subclass, and " +"its :meth:`utcoffset` and :meth:`dst` methods must not return ``None``. If " +"*self* is naive (``self.tzinfo is None``), it is presumed to represent time " +"in the system timezone." +msgstr "" + +#: ../Doc/library/datetime.rst:1033 +msgid "" +"If called without arguments (or with ``tz=None``) the system local timezone " +"is assumed for the target timezone. The ``.tzinfo`` attribute of the " +"converted datetime instance will be set to an instance of :class:`timezone` " +"with the zone name and offset obtained from the OS." +msgstr "" + +#: ../Doc/library/datetime.rst:1038 +msgid "" +"If ``self.tzinfo`` is *tz*, ``self.astimezone(tz)`` is equal to *self*: no " +"adjustment of date or time data is performed. Else the result is local time " +"in the timezone *tz*, representing the same UTC time as *self*: after " +"``astz = dt.astimezone(tz)``, ``astz - astz.utcoffset()`` will have the same " +"date and time data as ``dt - dt.utcoffset()``." +msgstr "" + +#: ../Doc/library/datetime.rst:1044 +msgid "" +"If you merely want to attach a time zone object *tz* to a datetime *dt* " +"without adjustment of date and time data, use ``dt.replace(tzinfo=tz)``. If " +"you merely want to remove the time zone object from an aware datetime *dt* " +"without conversion of date and time data, use ``dt.replace(tzinfo=None)``." +msgstr "" + +#: ../Doc/library/datetime.rst:1049 +msgid "" +"Note that the default :meth:`tzinfo.fromutc` method can be overridden in a :" +"class:`tzinfo` subclass to affect the result returned by :meth:`astimezone`. " +"Ignoring error cases, :meth:`astimezone` acts like::" +msgstr "" + +#: ../Doc/library/datetime.rst:1061 +msgid "*tz* now can be omitted." +msgstr "" + +#: ../Doc/library/datetime.rst:1064 +msgid "" +"The :meth:`astimezone` method can now be called on naive instances that are " +"presumed to represent system local time." +msgstr "" + +#: ../Doc/library/datetime.rst:1071 +msgid "" +"If :attr:`.tzinfo` is ``None``, returns ``None``, else returns ``self.tzinfo." +"utcoffset(self)``, and raises an exception if the latter doesn't return " +"``None``, or a :class:`timedelta` object representing a whole number of " +"minutes with magnitude less than one day." +msgstr "" + +#: ../Doc/library/datetime.rst:1079 +msgid "" +"If :attr:`.tzinfo` is ``None``, returns ``None``, else returns ``self.tzinfo." +"dst(self)``, and raises an exception if the latter doesn't return ``None``, " +"or a :class:`timedelta` object representing a whole number of minutes with " +"magnitude less than one day." +msgstr "" + +#: ../Doc/library/datetime.rst:1087 +msgid "" +"If :attr:`.tzinfo` is ``None``, returns ``None``, else returns ``self.tzinfo." +"tzname(self)``, raises an exception if the latter doesn't return ``None`` or " +"a string object," +msgstr "" + +#: ../Doc/library/datetime.rst:1094 +msgid "" +"Return a :class:`time.struct_time` such as returned by :func:`time." +"localtime`. ``d.timetuple()`` is equivalent to ``time.struct_time((d.year, d." +"month, d.day, d.hour, d.minute, d.second, d.weekday(), yday, dst))``, where " +"``yday = d.toordinal() - date(d.year, 1, 1).toordinal() + 1`` is the day " +"number within the current year starting with ``1`` for January 1st. The :" +"attr:`tm_isdst` flag of the result is set according to the :meth:`dst` " +"method: :attr:`.tzinfo` is ``None`` or :meth:`dst` returns ``None``, :attr:" +"`tm_isdst` is set to ``-1``; else if :meth:`dst` returns a non-zero value, :" +"attr:`tm_isdst` is set to ``1``; else :attr:`tm_isdst` is set to ``0``." +msgstr "" + +#: ../Doc/library/datetime.rst:1107 +msgid "" +"If :class:`.datetime` instance *d* is naive, this is the same as ``d." +"timetuple()`` except that :attr:`tm_isdst` is forced to 0 regardless of what " +"``d.dst()`` returns. DST is never in effect for a UTC time." +msgstr "" + +#: ../Doc/library/datetime.rst:1111 +msgid "" +"If *d* is aware, *d* is normalized to UTC time, by subtracting ``d." +"utcoffset()``, and a :class:`time.struct_time` for the normalized time is " +"returned. :attr:`tm_isdst` is forced to 0. Note that an :exc:" +"`OverflowError` may be raised if *d*.year was ``MINYEAR`` or ``MAXYEAR`` and " +"UTC adjustment spills over a year boundary." +msgstr "" + +#: ../Doc/library/datetime.rst:1121 +msgid "" +"Return the proleptic Gregorian ordinal of the date. The same as ``self." +"date().toordinal()``." +msgstr "" + +#: ../Doc/library/datetime.rst:1126 +msgid "" +"Return POSIX timestamp corresponding to the :class:`.datetime` instance. " +"The return value is a :class:`float` similar to that returned by :func:`time." +"time`." +msgstr "" + +#: ../Doc/library/datetime.rst:1130 +msgid "" +"Naive :class:`.datetime` instances are assumed to represent local time and " +"this method relies on the platform C :c:func:`mktime` function to perform " +"the conversion. Since :class:`.datetime` supports wider range of values " +"than :c:func:`mktime` on many platforms, this method may raise :exc:" +"`OverflowError` for times far in the past or far in the future." +msgstr "" + +#: ../Doc/library/datetime.rst:1137 +msgid "" +"For aware :class:`.datetime` instances, the return value is computed as::" +msgstr "" + +#: ../Doc/library/datetime.rst:1144 +msgid "" +"The :meth:`timestamp` method uses the :attr:`.fold` attribute to " +"disambiguate the times during a repeated interval." +msgstr "" + +#: ../Doc/library/datetime.rst:1150 +msgid "" +"There is no method to obtain the POSIX timestamp directly from a naive :" +"class:`.datetime` instance representing UTC time. If your application uses " +"this convention and your system timezone is not set to UTC, you can obtain " +"the POSIX timestamp by supplying ``tzinfo=timezone.utc``::" +msgstr "" + +#: ../Doc/library/datetime.rst:1158 +msgid "or by calculating the timestamp directly::" +msgstr "" + +#: ../Doc/library/datetime.rst:1164 +msgid "" +"Return the day of the week as an integer, where Monday is 0 and Sunday is 6. " +"The same as ``self.date().weekday()``. See also :meth:`isoweekday`." +msgstr "" + +#: ../Doc/library/datetime.rst:1170 +msgid "" +"Return the day of the week as an integer, where Monday is 1 and Sunday is 7. " +"The same as ``self.date().isoweekday()``. See also :meth:`weekday`, :meth:" +"`isocalendar`." +msgstr "" + +#: ../Doc/library/datetime.rst:1177 +msgid "" +"Return a 3-tuple, (ISO year, ISO week number, ISO weekday). The same as " +"``self.date().isocalendar()``." +msgstr "" + +#: ../Doc/library/datetime.rst:1183 +msgid "" +"Return a string representing the date and time in ISO 8601 format, YYYY-MM-" +"DDTHH:MM:SS.mmmmmm or, if :attr:`microsecond` is 0, YYYY-MM-DDTHH:MM:SS" +msgstr "" + +#: ../Doc/library/datetime.rst:1187 +msgid "" +"If :meth:`utcoffset` does not return ``None``, a 6-character string is " +"appended, giving the UTC offset in (signed) hours and minutes: YYYY-MM-DDTHH:" +"MM:SS.mmmmmm+HH:MM or, if :attr:`microsecond` is 0 YYYY-MM-DDTHH:MM:SS+HH:MM" +msgstr "" + +#: ../Doc/library/datetime.rst:1192 +msgid "" +"The optional argument *sep* (default ``'T'``) is a one-character separator, " +"placed between the date and time portions of the result. For example," +msgstr "" + +#: ../Doc/library/datetime.rst:1202 ../Doc/library/datetime.rst:1505 +msgid "" +"The optional argument *timespec* specifies the number of additional " +"components of the time to include (the default is ``'auto'``). It can be one " +"of the following:" +msgstr "" + +#: ../Doc/library/datetime.rst:1206 ../Doc/library/datetime.rst:1509 +msgid "" +"``'auto'``: Same as ``'seconds'`` if :attr:`microsecond` is 0, same as " +"``'microseconds'`` otherwise." +msgstr "" + +#: ../Doc/library/datetime.rst:1208 ../Doc/library/datetime.rst:1511 +msgid "``'hours'``: Include the :attr:`hour` in the two-digit HH format." +msgstr "" + +#: ../Doc/library/datetime.rst:1209 ../Doc/library/datetime.rst:1512 +msgid "``'minutes'``: Include :attr:`hour` and :attr:`minute` in HH:MM format." +msgstr "" + +#: ../Doc/library/datetime.rst:1210 ../Doc/library/datetime.rst:1513 +msgid "" +"``'seconds'``: Include :attr:`hour`, :attr:`minute`, and :attr:`second` in " +"HH:MM:SS format." +msgstr "" + +#: ../Doc/library/datetime.rst:1212 ../Doc/library/datetime.rst:1515 +msgid "" +"``'milliseconds'``: Include full time, but truncate fractional second part " +"to milliseconds. HH:MM:SS.sss format." +msgstr "" + +#: ../Doc/library/datetime.rst:1214 ../Doc/library/datetime.rst:1517 +msgid "``'microseconds'``: Include full time in HH:MM:SS.mmmmmm format." +msgstr "" + +#: ../Doc/library/datetime.rst:1218 ../Doc/library/datetime.rst:1521 +msgid "Excluded time components are truncated, not rounded." +msgstr "" + +#: ../Doc/library/datetime.rst:1220 ../Doc/library/datetime.rst:1523 +msgid ":exc:`ValueError` will be raised on an invalid *timespec* argument." +msgstr "" + +#: ../Doc/library/datetime.rst:1230 ../Doc/library/datetime.rst:1535 +msgid "Added the *timespec* argument." +msgstr "" + +#: ../Doc/library/datetime.rst:1236 +msgid "" +"For a :class:`.datetime` instance *d*, ``str(d)`` is equivalent to ``d." +"isoformat(' ')``." +msgstr "" + +#: ../Doc/library/datetime.rst:1242 +msgid "" +"Return a string representing the date and time, for example ``datetime(2002, " +"12, 4, 20, 30, 40).ctime() == 'Wed Dec 4 20:30:40 2002'``. ``d.ctime()`` is " +"equivalent to ``time.ctime(time.mktime(d.timetuple()))`` on platforms where " +"the native C :c:func:`ctime` function (which :func:`time.ctime` invokes, but " +"which :meth:`datetime.ctime` does not invoke) conforms to the C standard." +msgstr "" + +#: ../Doc/library/datetime.rst:1251 +msgid "" +"Return a string representing the date and time, controlled by an explicit " +"format string. For a complete list of formatting directives, see :ref:" +"`strftime-strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:1258 +msgid "" +"Same as :meth:`.datetime.strftime`. This makes it possible to specify a " +"format string for a :class:`.datetime` object in :ref:`formatted string " +"literals ` and when using :meth:`str.format`. For a complete " +"list of formatting directives, see :ref:`strftime-strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:1265 +msgid "Examples of working with datetime objects:" +msgstr "" + +#: ../Doc/library/datetime.rst:1312 +msgid "Using datetime with tzinfo:" +msgstr "" + +#: ../Doc/library/datetime.rst:1372 +msgid ":class:`time` Objects" +msgstr "" + +#: ../Doc/library/datetime.rst:1374 +msgid "" +"A time object represents a (local) time of day, independent of any " +"particular day, and subject to adjustment via a :class:`tzinfo` object." +msgstr "" + +#: ../Doc/library/datetime.rst:1379 +msgid "" +"All arguments are optional. *tzinfo* may be ``None``, or an instance of a :" +"class:`tzinfo` subclass. The remaining arguments may be integers, in the " +"following ranges:" +msgstr "" + +#: ../Doc/library/datetime.rst:1389 +msgid "" +"If an argument outside those ranges is given, :exc:`ValueError` is raised. " +"All default to ``0`` except *tzinfo*, which defaults to :const:`None`." +msgstr "" + +#: ../Doc/library/datetime.rst:1397 +msgid "The earliest representable :class:`.time`, ``time(0, 0, 0, 0)``." +msgstr "" + +#: ../Doc/library/datetime.rst:1402 +msgid "The latest representable :class:`.time`, ``time(23, 59, 59, 999999)``." +msgstr "" + +#: ../Doc/library/datetime.rst:1407 +msgid "" +"The smallest possible difference between non-equal :class:`.time` objects, " +"``timedelta(microseconds=1)``, although note that arithmetic on :class:`." +"time` objects is not supported." +msgstr "" + +#: ../Doc/library/datetime.rst:1436 +msgid "" +"The object passed as the tzinfo argument to the :class:`.time` constructor, " +"or ``None`` if none was passed." +msgstr "" + +#: ../Doc/library/datetime.rst:1453 +msgid "" +"comparison of :class:`.time` to :class:`.time`, where *a* is considered less " +"than *b* when *a* precedes *b* in time. If one comparand is naive and the " +"other is aware, :exc:`TypeError` is raised if an order comparison is " +"attempted. For equality comparisons, naive instances are never equal to " +"aware instances." +msgstr "" + +#: ../Doc/library/datetime.rst:1458 +msgid "" +"If both comparands are aware, and have the same :attr:`~time.tzinfo` " +"attribute, the common :attr:`~time.tzinfo` attribute is ignored and the base " +"times are compared. If both comparands are aware and have different :attr:" +"`~time.tzinfo` attributes, the comparands are first adjusted by subtracting " +"their UTC offsets (obtained from ``self.utcoffset()``). In order to stop " +"mixed-type comparisons from falling back to the default comparison by object " +"address, when a :class:`.time` object is compared to an object of a " +"different type, :exc:`TypeError` is raised unless the comparison is ``==`` " +"or ``!=``. The latter cases return :const:`False` or :const:`True`, " +"respectively." +msgstr "" + +#: ../Doc/library/datetime.rst:1468 +msgid "" +"Equality comparisons between naive and aware :class:`time` instances don't " +"raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/datetime.rst:1472 +msgid "hash, use as dict key" +msgstr "" + +#: ../Doc/library/datetime.rst:1474 +msgid "efficient pickling" +msgstr "" + +#: ../Doc/library/datetime.rst:1476 +msgid "" +"In boolean contexts, a :class:`.time` object is always considered to be true." +msgstr "" + +#: ../Doc/library/datetime.rst:1478 +msgid "" +"Before Python 3.5, a :class:`.time` object was considered to be false if it " +"represented midnight in UTC. This behavior was considered obscure and error-" +"prone and has been removed in Python 3.5. See :issue:`13936` for full " +"details." +msgstr "" + +#: ../Doc/library/datetime.rst:1489 +msgid "" +"Return a :class:`.time` with the same value, except for those attributes " +"given new values by whichever keyword arguments are specified. Note that " +"``tzinfo=None`` can be specified to create a naive :class:`.time` from an " +"aware :class:`.time`, without conversion of the time data." +msgstr "" + +#: ../Doc/library/datetime.rst:1500 +msgid "" +"Return a string representing the time in ISO 8601 format, HH:MM:SS.mmmmmm " +"or, if :attr:`microsecond` is 0, HH:MM:SS If :meth:`utcoffset` does not " +"return ``None``, a 6-character string is appended, giving the UTC offset in " +"(signed) hours and minutes: HH:MM:SS.mmmmmm+HH:MM or, if self.microsecond is " +"0, HH:MM:SS+HH:MM" +msgstr "" + +#: ../Doc/library/datetime.rst:1541 +msgid "For a time *t*, ``str(t)`` is equivalent to ``t.isoformat()``." +msgstr "" + +#: ../Doc/library/datetime.rst:1546 +msgid "" +"Return a string representing the time, controlled by an explicit format " +"string. For a complete list of formatting directives, see :ref:`strftime-" +"strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:1553 +msgid "" +"Same as :meth:`.time.strftime`. This makes it possible to specify a format " +"string for a :class:`.time` object in :ref:`formatted string literals ` and when using :meth:`str.format`. For a complete list of " +"formatting directives, see :ref:`strftime-strptime-behavior`." +msgstr "" + +#: ../Doc/library/datetime.rst:1562 +msgid "" +"If :attr:`.tzinfo` is ``None``, returns ``None``, else returns ``self.tzinfo." +"utcoffset(None)``, and raises an exception if the latter doesn't return " +"``None`` or a :class:`timedelta` object representing a whole number of " +"minutes with magnitude less than one day." +msgstr "" + +#: ../Doc/library/datetime.rst:1570 +msgid "" +"If :attr:`.tzinfo` is ``None``, returns ``None``, else returns ``self.tzinfo." +"dst(None)``, and raises an exception if the latter doesn't return ``None``, " +"or a :class:`timedelta` object representing a whole number of minutes with " +"magnitude less than one day." +msgstr "" + +#: ../Doc/library/datetime.rst:1578 +msgid "" +"If :attr:`.tzinfo` is ``None``, returns ``None``, else returns ``self.tzinfo." +"tzname(None)``, or raises an exception if the latter doesn't return ``None`` " +"or a string object." +msgstr "" + +#: ../Doc/library/datetime.rst:1613 +msgid ":class:`tzinfo` Objects" +msgstr "" + +#: ../Doc/library/datetime.rst:1617 +msgid "" +"This is an abstract base class, meaning that this class should not be " +"instantiated directly. You need to derive a concrete subclass, and (at " +"least) supply implementations of the standard :class:`tzinfo` methods needed " +"by the :class:`.datetime` methods you use. The :mod:`datetime` module " +"supplies a simple concrete subclass of :class:`tzinfo`, :class:`timezone`, " +"which can represent timezones with fixed offset from UTC such as UTC itself " +"or North American EST and EDT." +msgstr "" + +#: ../Doc/library/datetime.rst:1625 +msgid "" +"An instance of (a concrete subclass of) :class:`tzinfo` can be passed to the " +"constructors for :class:`.datetime` and :class:`.time` objects. The latter " +"objects view their attributes as being in local time, and the :class:" +"`tzinfo` object supports methods revealing offset of local time from UTC, " +"the name of the time zone, and DST offset, all relative to a date or time " +"object passed to them." +msgstr "" + +#: ../Doc/library/datetime.rst:1631 +msgid "" +"Special requirement for pickling: A :class:`tzinfo` subclass must have an :" +"meth:`__init__` method that can be called with no arguments, else it can be " +"pickled but possibly not unpickled again. This is a technical requirement " +"that may be relaxed in the future." +msgstr "" + +#: ../Doc/library/datetime.rst:1636 +msgid "" +"A concrete subclass of :class:`tzinfo` may need to implement the following " +"methods. Exactly which methods are needed depends on the uses made of " +"aware :mod:`datetime` objects. If in doubt, simply implement all of them." +msgstr "" + +#: ../Doc/library/datetime.rst:1643 +msgid "" +"Return offset of local time from UTC, in minutes east of UTC. If local time " +"is west of UTC, this should be negative. Note that this is intended to be " +"the total offset from UTC; for example, if a :class:`tzinfo` object " +"represents both time zone and DST adjustments, :meth:`utcoffset` should " +"return their sum. If the UTC offset isn't known, return ``None``. Else the " +"value returned must be a :class:`timedelta` object specifying a whole number " +"of minutes in the range -1439 to 1439 inclusive (1440 = 24\\*60; the " +"magnitude of the offset must be less than one day). Most implementations " +"of :meth:`utcoffset` will probably look like one of these two::" +msgstr "" + +#: ../Doc/library/datetime.rst:1656 +msgid "" +"If :meth:`utcoffset` does not return ``None``, :meth:`dst` should not return " +"``None`` either." +msgstr "" + +#: ../Doc/library/datetime.rst:1659 +msgid "" +"The default implementation of :meth:`utcoffset` raises :exc:" +"`NotImplementedError`." +msgstr "" + +#: ../Doc/library/datetime.rst:1665 +msgid "" +"Return the daylight saving time (DST) adjustment, in minutes east of UTC, or " +"``None`` if DST information isn't known. Return ``timedelta(0)`` if DST is " +"not in effect. If DST is in effect, return the offset as a :class:" +"`timedelta` object (see :meth:`utcoffset` for details). Note that DST " +"offset, if applicable, has already been added to the UTC offset returned by :" +"meth:`utcoffset`, so there's no need to consult :meth:`dst` unless you're " +"interested in obtaining DST info separately. For example, :meth:`datetime." +"timetuple` calls its :attr:`~.datetime.tzinfo` attribute's :meth:`dst` " +"method to determine how the :attr:`tm_isdst` flag should be set, and :meth:" +"`tzinfo.fromutc` calls :meth:`dst` to account for DST changes when crossing " +"time zones." +msgstr "" + +#: ../Doc/library/datetime.rst:1676 +msgid "" +"An instance *tz* of a :class:`tzinfo` subclass that models both standard and " +"daylight times must be consistent in this sense:" +msgstr "" + +#: ../Doc/library/datetime.rst:1679 +msgid "``tz.utcoffset(dt) - tz.dst(dt)``" +msgstr "" + +#: ../Doc/library/datetime.rst:1681 +msgid "" +"must return the same result for every :class:`.datetime` *dt* with ``dt." +"tzinfo == tz`` For sane :class:`tzinfo` subclasses, this expression yields " +"the time zone's \"standard offset\", which should not depend on the date or " +"the time, but only on geographic location. The implementation of :meth:" +"`datetime.astimezone` relies on this, but cannot detect violations; it's the " +"programmer's responsibility to ensure it. If a :class:`tzinfo` subclass " +"cannot guarantee this, it may be able to override the default implementation " +"of :meth:`tzinfo.fromutc` to work correctly with :meth:`astimezone` " +"regardless." +msgstr "" + +#: ../Doc/library/datetime.rst:1690 +msgid "" +"Most implementations of :meth:`dst` will probably look like one of these " +"two::" +msgstr "" + +#: ../Doc/library/datetime.rst:1696 +msgid "or ::" +msgstr "" + +#: ../Doc/library/datetime.rst:1708 +msgid "" +"The default implementation of :meth:`dst` raises :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/datetime.rst:1713 +msgid "" +"Return the time zone name corresponding to the :class:`.datetime` object " +"*dt*, as a string. Nothing about string names is defined by the :mod:" +"`datetime` module, and there's no requirement that it mean anything in " +"particular. For example, \"GMT\", \"UTC\", \"-500\", \"-5:00\", \"EDT\", " +"\"US/Eastern\", \"America/New York\" are all valid replies. Return ``None`` " +"if a string name isn't known. Note that this is a method rather than a " +"fixed string primarily because some :class:`tzinfo` subclasses will wish to " +"return different names depending on the specific value of *dt* passed, " +"especially if the :class:`tzinfo` class is accounting for daylight time." +msgstr "" + +#: ../Doc/library/datetime.rst:1723 +msgid "" +"The default implementation of :meth:`tzname` raises :exc:" +"`NotImplementedError`." +msgstr "" + +#: ../Doc/library/datetime.rst:1726 +msgid "" +"These methods are called by a :class:`.datetime` or :class:`.time` object, " +"in response to their methods of the same names. A :class:`.datetime` object " +"passes itself as the argument, and a :class:`.time` object passes ``None`` " +"as the argument. A :class:`tzinfo` subclass's methods should therefore be " +"prepared to accept a *dt* argument of ``None``, or of class :class:`." +"datetime`." +msgstr "" + +#: ../Doc/library/datetime.rst:1732 +msgid "" +"When ``None`` is passed, it's up to the class designer to decide the best " +"response. For example, returning ``None`` is appropriate if the class " +"wishes to say that time objects don't participate in the :class:`tzinfo` " +"protocols. It may be more useful for ``utcoffset(None)`` to return the " +"standard UTC offset, as there is no other convention for discovering the " +"standard offset." +msgstr "" + +#: ../Doc/library/datetime.rst:1738 +msgid "" +"When a :class:`.datetime` object is passed in response to a :class:`." +"datetime` method, ``dt.tzinfo`` is the same object as *self*. :class:" +"`tzinfo` methods can rely on this, unless user code calls :class:`tzinfo` " +"methods directly. The intent is that the :class:`tzinfo` methods interpret " +"*dt* as being in local time, and not need worry about objects in other " +"timezones." +msgstr "" + +#: ../Doc/library/datetime.rst:1744 +msgid "" +"There is one more :class:`tzinfo` method that a subclass may wish to " +"override:" +msgstr "" + +#: ../Doc/library/datetime.rst:1749 +msgid "" +"This is called from the default :class:`datetime.astimezone()` " +"implementation. When called from that, ``dt.tzinfo`` is *self*, and *dt*'s " +"date and time data are to be viewed as expressing a UTC time. The purpose " +"of :meth:`fromutc` is to adjust the date and time data, returning an " +"equivalent datetime in *self*'s local time." +msgstr "" + +#: ../Doc/library/datetime.rst:1755 +msgid "" +"Most :class:`tzinfo` subclasses should be able to inherit the default :meth:" +"`fromutc` implementation without problems. It's strong enough to handle " +"fixed-offset time zones, and time zones accounting for both standard and " +"daylight time, and the latter even if the DST transition times differ in " +"different years. An example of a time zone the default :meth:`fromutc` " +"implementation may not handle correctly in all cases is one where the " +"standard offset (from UTC) depends on the specific date and time passed, " +"which can happen for political reasons. The default implementations of :meth:" +"`astimezone` and :meth:`fromutc` may not produce the result you want if the " +"result is one of the hours straddling the moment the standard offset changes." +msgstr "" + +#: ../Doc/library/datetime.rst:1766 +msgid "" +"Skipping code for error cases, the default :meth:`fromutc` implementation " +"acts like::" +msgstr "" + +#: ../Doc/library/datetime.rst:1784 +msgid "Example :class:`tzinfo` classes:" +msgstr "" + +#: ../Doc/library/datetime.rst:1788 +msgid "" +"Note that there are unavoidable subtleties twice per year in a :class:" +"`tzinfo` subclass accounting for both standard and daylight time, at the DST " +"transition points. For concreteness, consider US Eastern (UTC -0500), where " +"EDT begins the minute after 1:59 (EST) on the second Sunday in March, and " +"ends the minute after 1:59 (EDT) on the first Sunday in November::" +msgstr "" + +#: ../Doc/library/datetime.rst:1802 +msgid "" +"When DST starts (the \"start\" line), the local wall clock leaps from 1:59 " +"to 3:00. A wall time of the form 2:MM doesn't really make sense on that " +"day, so ``astimezone(Eastern)`` won't deliver a result with ``hour == 2`` on " +"the day DST begins. For example, at the Spring forward transition of 2016, " +"we get" +msgstr "" + +#: ../Doc/library/datetime.rst:1819 +msgid "" +"When DST ends (the \"end\" line), there's a potentially worse problem: " +"there's an hour that can't be spelled unambiguously in local wall time: the " +"last hour of daylight time. In Eastern, that's times of the form 5:MM UTC " +"on the day daylight time ends. The local wall clock leaps from 1:59 " +"(daylight time) back to 1:00 (standard time) again. Local times of the form " +"1:MM are ambiguous. :meth:`astimezone` mimics the local clock's behavior by " +"mapping two adjacent UTC hours into the same local hour then. In the " +"Eastern example, UTC times of the form 5:MM and 6:MM both map to 1:MM when " +"converted to Eastern, but earlier times have the :attr:`~datetime.fold` " +"attribute set to 0 and the later times have it set to 1. For example, at the " +"Fall back transition of 2016, we get" +msgstr "" + +#: ../Doc/library/datetime.rst:1841 +msgid "" +"Note that the :class:`datetime` instances that differ only by the value of " +"the :attr:`~datetime.fold` attribute are considered equal in comparisons." +msgstr "" + +#: ../Doc/library/datetime.rst:1844 +msgid "" +"Applications that can't bear wall-time ambiguities should explicitly check " +"the value of the :attr:`~datetime.fold` attribute or avoid using hybrid :" +"class:`tzinfo` subclasses; there are no ambiguities when using :class:" +"`timezone`, or any other fixed-offset :class:`tzinfo` subclass (such as a " +"class representing only EST (fixed offset -5 hours), or only EDT (fixed " +"offset -4 hours))." +msgstr "" + +#: ../Doc/library/datetime.rst:1857 +msgid "`datetuil.tz `_" +msgstr "" + +#: ../Doc/library/datetime.rst:1853 +msgid "" +"The standard library has :class:`timezone` class for handling arbitrary " +"fixed offsets from UTC and :attr:`timezone.utc` as UTC timezone instance." +msgstr "" + +#: ../Doc/library/datetime.rst:1856 +msgid "" +"*datetuil.tz* library brings the *IANA timezone database* (also known as the " +"Olson database) to Python and its usage is recommended." +msgstr "" + +#: ../Doc/library/datetime.rst:1863 +msgid "`IANA timezone database `_" +msgstr "" + +#: ../Doc/library/datetime.rst:1860 +msgid "" +"The Time Zone Database (often called tz, tzdata or zoneinfo) contains code " +"and data that represent the history of local time for many representative " +"locations around the globe. It is updated periodically to reflect changes " +"made by political bodies to time zone boundaries, UTC offsets, and daylight-" +"saving rules." +msgstr "" + +#: ../Doc/library/datetime.rst:1870 +msgid ":class:`timezone` Objects" +msgstr "" + +#: ../Doc/library/datetime.rst:1872 +msgid "" +"The :class:`timezone` class is a subclass of :class:`tzinfo`, each instance " +"of which represents a timezone defined by a fixed offset from UTC. Note " +"that objects of this class cannot be used to represent timezone information " +"in the locations where different offsets are used in different days of the " +"year or where historical changes have been made to civil time." +msgstr "" + +#: ../Doc/library/datetime.rst:1882 +msgid "" +"The *offset* argument must be specified as a :class:`timedelta` object " +"representing the difference between the local time and UTC. It must be " +"strictly between ``-timedelta(hours=24)`` and ``timedelta(hours=24)`` and " +"represent a whole number of minutes, otherwise :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/datetime.rst:1888 +msgid "" +"The *name* argument is optional. If specified it must be a string that will " +"be used as the value returned by the :meth:`datetime.tzname` method." +msgstr "" + +#: ../Doc/library/datetime.rst:1895 +msgid "" +"Return the fixed value specified when the :class:`timezone` instance is " +"constructed. The *dt* argument is ignored. The return value is a :class:" +"`timedelta` instance equal to the difference between the local time and UTC." +msgstr "" + +#: ../Doc/library/datetime.rst:1902 +msgid "" +"Return the fixed value specified when the :class:`timezone` instance is " +"constructed. If *name* is not provided in the constructor, the name " +"returned by ``tzname(dt)`` is generated from the value of the ``offset`` as " +"follows. If *offset* is ``timedelta(0)``, the name is \"UTC\", otherwise it " +"is a string 'UTC±HH:MM', where ± is the sign of ``offset``, HH and MM are " +"two digits of ``offset.hours`` and ``offset.minutes`` respectively." +msgstr "" + +#: ../Doc/library/datetime.rst:1910 +msgid "" +"Name generated from ``offset=timedelta(0)`` is now plain 'UTC', not 'UTC" +"+00:00'." +msgstr "" + +#: ../Doc/library/datetime.rst:1917 +msgid "Always returns ``None``." +msgstr "" + +#: ../Doc/library/datetime.rst:1921 +msgid "" +"Return ``dt + offset``. The *dt* argument must be an aware :class:`." +"datetime` instance, with ``tzinfo`` set to ``self``." +msgstr "" + +#: ../Doc/library/datetime.rst:1928 +msgid "The UTC timezone, ``timezone(timedelta(0))``." +msgstr "" + +#: ../Doc/library/datetime.rst:1934 +msgid ":meth:`strftime` and :meth:`strptime` Behavior" +msgstr "" + +#: ../Doc/library/datetime.rst:1936 +msgid "" +":class:`date`, :class:`.datetime`, and :class:`.time` objects all support a " +"``strftime(format)`` method, to create a string representing the time under " +"the control of an explicit format string. Broadly speaking, ``d." +"strftime(fmt)`` acts like the :mod:`time` module's ``time.strftime(fmt, d." +"timetuple())`` although not all objects support a :meth:`timetuple` method." +msgstr "" + +#: ../Doc/library/datetime.rst:1942 +msgid "" +"Conversely, the :meth:`datetime.strptime` class method creates a :class:`." +"datetime` object from a string representing a date and time and a " +"corresponding format string. ``datetime.strptime(date_string, format)`` is " +"equivalent to ``datetime(*(time.strptime(date_string, format)[0:6]))``." +msgstr "" + +#: ../Doc/library/datetime.rst:1947 +msgid "" +"For :class:`.time` objects, the format codes for year, month, and day should " +"not be used, as time objects have no such values. If they're used anyway, " +"``1900`` is substituted for the year, and ``1`` for the month and day." +msgstr "" + +#: ../Doc/library/datetime.rst:1951 +msgid "" +"For :class:`date` objects, the format codes for hours, minutes, seconds, and " +"microseconds should not be used, as :class:`date` objects have no such " +"values. If they're used anyway, ``0`` is substituted for them." +msgstr "" + +#: ../Doc/library/datetime.rst:1955 +msgid "" +"The full set of format codes supported varies across platforms, because " +"Python calls the platform C library's :func:`strftime` function, and " +"platform variations are common. To see the full set of format codes " +"supported on your platform, consult the :manpage:`strftime(3)` documentation." +msgstr "" + +#: ../Doc/library/datetime.rst:1960 +msgid "" +"The following is a list of all the format codes that the C standard (1989 " +"version) requires, and these work on all platforms with a standard C " +"implementation. Note that the 1999 version of the C standard added " +"additional format codes." +msgstr "" + +#: ../Doc/library/datetime.rst:1966 ../Doc/library/datetime.rst:2072 +#: ../Doc/library/time.rst:380 +msgid "Directive" +msgstr "" + +#: ../Doc/library/datetime.rst:1968 ../Doc/library/time.rst:382 +msgid "``%a``" +msgstr "" + +#: ../Doc/library/datetime.rst:1968 +msgid "Weekday as locale's abbreviated name." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Sun, Mon, ..., Sat (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "So, Mo, ..., Sa (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:1973 ../Doc/library/time.rst:385 +msgid "``%A``" +msgstr "" + +#: ../Doc/library/datetime.rst:1973 +msgid "Weekday as locale's full name." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Sunday, Monday, ..., Saturday (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Sonntag, Montag, ..., Samstag (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:1978 ../Doc/library/time.rst:427 +msgid "``%w``" +msgstr "" + +#: ../Doc/library/datetime.rst:1978 +msgid "Weekday as a decimal number, where 0 is Sunday and 6 is Saturday." +msgstr "" + +#: ../Doc/library/datetime.rst:1978 +msgid "0, 1, ..., 6" +msgstr "" + +#: ../Doc/library/datetime.rst:1982 ../Doc/library/re.rst:1226 +#: ../Doc/library/time.rst:395 +msgid "``%d``" +msgstr "" + +#: ../Doc/library/datetime.rst:1982 +msgid "Day of the month as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:1982 +msgid "01, 02, ..., 31" +msgstr "" + +#: ../Doc/library/datetime.rst:1985 ../Doc/library/time.rst:387 +msgid "``%b``" +msgstr "" + +#: ../Doc/library/datetime.rst:1985 +msgid "Month as locale's abbreviated name." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Jan, Feb, ..., Dec (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Jan, Feb, ..., Dez (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:1990 ../Doc/library/time.rst:390 +msgid "``%B``" +msgstr "" + +#: ../Doc/library/datetime.rst:1990 +msgid "Month as locale's full name." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "January, February, ..., December (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Januar, Februar, ..., Dezember (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:1995 ../Doc/library/time.rst:407 +msgid "``%m``" +msgstr "" + +#: ../Doc/library/datetime.rst:1995 +msgid "Month as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:1995 ../Doc/library/datetime.rst:2007 +msgid "01, 02, ..., 12" +msgstr "" + +#: ../Doc/library/datetime.rst:1998 ../Doc/library/time.rst:444 +msgid "``%y``" +msgstr "" + +#: ../Doc/library/datetime.rst:1998 +msgid "Year without century as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:1998 +msgid "00, 01, ..., 99" +msgstr "" + +#: ../Doc/library/datetime.rst:2001 ../Doc/library/time.rst:447 +msgid "``%Y``" +msgstr "" + +#: ../Doc/library/datetime.rst:2001 ../Doc/library/time.rst:447 +msgid "Year with century as a decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:2001 ../Doc/library/datetime.rst:2074 +msgid "0001, 0002, ..., 2013, 2014, ..., 9998, 9999" +msgstr "" + +#: ../Doc/library/datetime.rst:2004 ../Doc/library/time.rst:398 +msgid "``%H``" +msgstr "" + +#: ../Doc/library/datetime.rst:2004 +msgid "Hour (24-hour clock) as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:2004 +msgid "00, 01, ..., 23" +msgstr "" + +#: ../Doc/library/datetime.rst:2007 ../Doc/library/time.rst:401 +msgid "``%I``" +msgstr "" + +#: ../Doc/library/datetime.rst:2007 +msgid "Hour (12-hour clock) as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:2010 ../Doc/library/time.rst:413 +msgid "``%p``" +msgstr "" + +#: ../Doc/library/datetime.rst:2010 ../Doc/library/time.rst:413 +msgid "Locale's equivalent of either AM or PM." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "AM, PM (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "am, pm (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:2010 +msgid "\\(1), \\(3)" +msgstr "" + +#: ../Doc/library/datetime.rst:2013 ../Doc/library/time.rst:410 +msgid "``%M``" +msgstr "" + +#: ../Doc/library/datetime.rst:2013 +msgid "Minute as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:2013 ../Doc/library/datetime.rst:2016 +msgid "00, 01, ..., 59" +msgstr "" + +#: ../Doc/library/datetime.rst:2016 ../Doc/library/time.rst:416 +msgid "``%S``" +msgstr "" + +#: ../Doc/library/datetime.rst:2016 +msgid "Second as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:2016 ../Doc/library/stdtypes.rst:1087 +#: ../Doc/library/stdtypes.rst:2175 ../Doc/library/stdtypes.rst:2179 +#: ../Doc/library/stdtypes.rst:3275 ../Doc/library/stdtypes.rst:3279 +#: ../Doc/library/struct.rst:215 ../Doc/library/struct.rst:217 +msgid "\\(4)" +msgstr "" + +#: ../Doc/library/datetime.rst:2019 +msgid "``%f``" +msgstr "" + +#: ../Doc/library/datetime.rst:2019 +msgid "Microsecond as a decimal number, zero-padded on the left." +msgstr "" + +#: ../Doc/library/datetime.rst:2019 +msgid "000000, 000001, ..., 999999" +msgstr "" + +#: ../Doc/library/datetime.rst:2019 ../Doc/library/stdtypes.rst:311 +#: ../Doc/library/stdtypes.rst:313 ../Doc/library/stdtypes.rst:1063 +#: ../Doc/library/stdtypes.rst:1066 ../Doc/library/stdtypes.rst:2186 +#: ../Doc/library/stdtypes.rst:2189 ../Doc/library/stdtypes.rst:2192 +#: ../Doc/library/stdtypes.rst:3286 ../Doc/library/stdtypes.rst:3293 +#: ../Doc/library/struct.rst:219 ../Doc/library/struct.rst:221 +#: ../Doc/library/struct.rst:223 +msgid "\\(5)" +msgstr "" + +#: ../Doc/library/datetime.rst:2023 ../Doc/library/datetime.rst:2142 +#: ../Doc/library/time.rst:450 +msgid "``%z``" +msgstr "" + +#: ../Doc/library/datetime.rst:2023 +msgid "" +"UTC offset in the form +HHMM or -HHMM (empty string if the object is naive)." +msgstr "" + +#: ../Doc/library/datetime.rst:2023 +msgid "(empty), +0000, -0400, +1030" +msgstr "" + +#: ../Doc/library/datetime.rst:2023 ../Doc/library/stdtypes.rst:302 +#: ../Doc/library/stdtypes.rst:1074 ../Doc/library/stdtypes.rst:3290 +#: ../Doc/library/struct.rst:229 +msgid "\\(6)" +msgstr "" + +#: ../Doc/library/datetime.rst:2027 ../Doc/library/datetime.rst:2147 +#: ../Doc/library/time.rst:456 +msgid "``%Z``" +msgstr "" + +#: ../Doc/library/datetime.rst:2027 +msgid "Time zone name (empty string if the object is naive)." +msgstr "" + +#: ../Doc/library/datetime.rst:2027 +msgid "(empty), UTC, EST, CST" +msgstr "" + +#: ../Doc/library/datetime.rst:2030 ../Doc/library/time.rst:404 +msgid "``%j``" +msgstr "" + +#: ../Doc/library/datetime.rst:2030 +msgid "Day of the year as a zero-padded decimal number." +msgstr "" + +#: ../Doc/library/datetime.rst:2030 +msgid "001, 002, ..., 366" +msgstr "" + +#: ../Doc/library/datetime.rst:2033 ../Doc/library/time.rst:419 +msgid "``%U``" +msgstr "" + +#: ../Doc/library/datetime.rst:2033 +msgid "" +"Week number of the year (Sunday as the first day of the week) as a zero " +"padded decimal number. All days in a new year preceding the first Sunday are " +"considered to be in week 0." +msgstr "" + +#: ../Doc/library/datetime.rst:2033 ../Doc/library/datetime.rst:2041 +msgid "00, 01, ..., 53" +msgstr "" + +#: ../Doc/library/datetime.rst:2033 ../Doc/library/datetime.rst:2041 +#: ../Doc/library/stdtypes.rst:2161 ../Doc/library/stdtypes.rst:3296 +#: ../Doc/library/struct.rst:219 +msgid "\\(7)" +msgstr "" + +#: ../Doc/library/datetime.rst:2041 ../Doc/library/time.rst:430 +msgid "``%W``" +msgstr "" + +#: ../Doc/library/datetime.rst:2041 +msgid "" +"Week number of the year (Monday as the first day of the week) as a decimal " +"number. All days in a new year preceding the first Monday are considered to " +"be in week 0." +msgstr "" + +#: ../Doc/library/datetime.rst:2049 ../Doc/library/re.rst:1222 +#: ../Doc/library/time.rst:392 +msgid "``%c``" +msgstr "" + +#: ../Doc/library/datetime.rst:2049 ../Doc/library/time.rst:392 +msgid "Locale's appropriate date and time representation." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Tue Aug 16 21:30:00 1988 (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "Di 16 Aug 21:30:00 1988 (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:2054 ../Doc/library/time.rst:438 +msgid "``%x``" +msgstr "" + +#: ../Doc/library/datetime.rst:2054 ../Doc/library/time.rst:438 +msgid "Locale's appropriate date representation." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "08/16/88 (None);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "08/16/1988 (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "16.08.1988 (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:2058 ../Doc/library/time.rst:441 +msgid "``%X``" +msgstr "" + +#: ../Doc/library/datetime.rst:2058 ../Doc/library/time.rst:441 +msgid "Locale's appropriate time representation." +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "21:30:00 (en_US);" +msgstr "" + +#: ../Doc/library/datetime.rst:0 +msgid "21:30:00 (de_DE)" +msgstr "" + +#: ../Doc/library/datetime.rst:2061 ../Doc/library/time.rst:459 +msgid "``%%``" +msgstr "" + +#: ../Doc/library/datetime.rst:2061 ../Doc/library/time.rst:459 +msgid "A literal ``'%'`` character." +msgstr "" + +#: ../Doc/library/datetime.rst:2061 +msgid "%" +msgstr "" + +#: ../Doc/library/datetime.rst:2064 +msgid "" +"Several additional directives not required by the C89 standard are included " +"for convenience. These parameters all correspond to ISO 8601 date values. " +"These may not be available on all platforms when used with the :meth:" +"`strftime` method. The ISO 8601 year and ISO 8601 week directives are not " +"interchangeable with the year and week number directives above. Calling :" +"meth:`strptime` with incomplete or ambiguous ISO 8601 directives will raise " +"a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/datetime.rst:2074 +msgid "``%G``" +msgstr "" + +#: ../Doc/library/datetime.rst:2074 +msgid "" +"ISO 8601 year with century representing the year that contains the greater " +"part of the ISO week (``%V``)." +msgstr "" + +#: ../Doc/library/datetime.rst:2074 ../Doc/library/datetime.rst:2082 +#: ../Doc/library/stdtypes.rst:876 ../Doc/library/stdtypes.rst:3261 +msgid "\\(8)" +msgstr "" + +#: ../Doc/library/datetime.rst:2079 ../Doc/library/re.rst:1236 +msgid "``%u``" +msgstr "" + +#: ../Doc/library/datetime.rst:2079 +msgid "ISO 8601 weekday as a decimal number where 1 is Monday." +msgstr "" + +#: ../Doc/library/datetime.rst:2079 +msgid "1, 2, ..., 7" +msgstr "" + +#: ../Doc/library/datetime.rst:2082 +msgid "``%V``" +msgstr "" + +#: ../Doc/library/datetime.rst:2082 +msgid "" +"ISO 8601 week as a decimal number with Monday as the first day of the week. " +"Week 01 is the week containing Jan 4." +msgstr "" + +#: ../Doc/library/datetime.rst:2082 +msgid "01, 02, ..., 53" +msgstr "" + +#: ../Doc/library/datetime.rst:2089 +msgid "``%G``, ``%u`` and ``%V`` were added." +msgstr "" + +#: ../Doc/library/datetime.rst:2095 +msgid "" +"Because the format depends on the current locale, care should be taken when " +"making assumptions about the output value. Field orderings will vary (for " +"example, \"month/day/year\" versus \"day/month/year\"), and the output may " +"contain Unicode characters encoded using the locale's default encoding (for " +"example, if the current locale is ``ja_JP``, the default encoding could be " +"any one of ``eucJP``, ``SJIS``, or ``utf-8``; use :meth:`locale.getlocale` " +"to determine the current locale's encoding)." +msgstr "" + +#: ../Doc/library/datetime.rst:2104 +msgid "" +"The :meth:`strptime` method can parse years in the full [1, 9999] range, but " +"years < 1000 must be zero-filled to 4-digit width." +msgstr "" + +#: ../Doc/library/datetime.rst:2107 +msgid "" +"In previous versions, :meth:`strftime` method was restricted to years >= " +"1900." +msgstr "" + +#: ../Doc/library/datetime.rst:2111 +msgid "" +"In version 3.2, :meth:`strftime` method was restricted to years >= 1000." +msgstr "" + +#: ../Doc/library/datetime.rst:2116 +msgid "" +"When used with the :meth:`strptime` method, the ``%p`` directive only " +"affects the output hour field if the ``%I`` directive is used to parse the " +"hour." +msgstr "" + +#: ../Doc/library/datetime.rst:2120 +msgid "" +"Unlike the :mod:`time` module, the :mod:`datetime` module does not support " +"leap seconds." +msgstr "" + +#: ../Doc/library/datetime.rst:2124 +msgid "" +"When used with the :meth:`strptime` method, the ``%f`` directive accepts " +"from one to six digits and zero pads on the right. ``%f`` is an extension " +"to the set of format characters in the C standard (but implemented " +"separately in datetime objects, and therefore always available)." +msgstr "" + +#: ../Doc/library/datetime.rst:2131 +msgid "" +"For a naive object, the ``%z`` and ``%Z`` format codes are replaced by empty " +"strings." +msgstr "" + +#: ../Doc/library/datetime.rst:2134 +msgid "For an aware object:" +msgstr "" + +#: ../Doc/library/datetime.rst:2137 +msgid "" +":meth:`utcoffset` is transformed into a 5-character string of the form +HHMM " +"or -HHMM, where HH is a 2-digit string giving the number of UTC offset " +"hours, and MM is a 2-digit string giving the number of UTC offset minutes. " +"For example, if :meth:`utcoffset` returns ``timedelta(hours=-3, " +"minutes=-30)``, ``%z`` is replaced with the string ``'-0330'``." +msgstr "" + +#: ../Doc/library/datetime.rst:2145 +msgid "" +"If :meth:`tzname` returns ``None``, ``%Z`` is replaced by an empty string. " +"Otherwise ``%Z`` is replaced by the returned value, which must be a string." +msgstr "" + +#: ../Doc/library/datetime.rst:2149 +msgid "" +"When the ``%z`` directive is provided to the :meth:`strptime` method, an " +"aware :class:`.datetime` object will be produced. The ``tzinfo`` of the " +"result will be set to a :class:`timezone` instance." +msgstr "" + +#: ../Doc/library/datetime.rst:2155 +msgid "" +"When used with the :meth:`strptime` method, ``%U`` and ``%W`` are only used " +"in calculations when the day of the week and the calendar year (``%Y``) are " +"specified." +msgstr "" + +#: ../Doc/library/datetime.rst:2160 +msgid "" +"Similar to ``%U`` and ``%W``, ``%V`` is only used in calculations when the " +"day of the week and the ISO year (``%G``) are specified in a :meth:" +"`strptime` format string. Also note that ``%G`` and ``%Y`` are not " +"interchangeable." +msgstr "" + +#: ../Doc/library/datetime.rst:2167 +msgid "If, that is, we ignore the effects of Relativity" +msgstr "" + +#: ../Doc/library/dbm.rst:2 +msgid ":mod:`dbm` --- Interfaces to Unix \"databases\"" +msgstr "" + +#: ../Doc/library/dbm.rst:7 +msgid "**Source code:** :source:`Lib/dbm/__init__.py`" +msgstr "" + +#: ../Doc/library/dbm.rst:11 +msgid "" +":mod:`dbm` is a generic interface to variants of the DBM database --- :mod:" +"`dbm.gnu` or :mod:`dbm.ndbm`. If none of these modules is installed, the " +"slow-but-simple implementation in module :mod:`dbm.dumb` will be used. " +"There is a `third party interface `_ to the Oracle Berkeley DB." +msgstr "" + +#: ../Doc/library/dbm.rst:20 +msgid "" +"A tuple containing the exceptions that can be raised by each of the " +"supported modules, with a unique exception also named :exc:`dbm.error` as " +"the first item --- the latter is used when :exc:`dbm.error` is raised." +msgstr "" + +#: ../Doc/library/dbm.rst:27 +msgid "" +"This function attempts to guess which of the several simple database modules " +"available --- :mod:`dbm.gnu`, :mod:`dbm.ndbm` or :mod:`dbm.dumb` --- should " +"be used to open a given file." +msgstr "" + +#: ../Doc/library/dbm.rst:31 +msgid "" +"Returns one of the following values: ``None`` if the file can't be opened " +"because it's unreadable or doesn't exist; the empty string (``''``) if the " +"file's format can't be guessed; or a string containing the required module " +"name, such as ``'dbm.ndbm'`` or ``'dbm.gnu'``." +msgstr "" + +#: ../Doc/library/dbm.rst:39 +msgid "Open the database file *file* and return a corresponding object." +msgstr "" + +#: ../Doc/library/dbm.rst:41 +msgid "" +"If the database file already exists, the :func:`whichdb` function is used to " +"determine its type and the appropriate module is used; if it does not exist, " +"the first module listed above that can be imported is used." +msgstr "" + +#: ../Doc/library/dbm.rst:45 ../Doc/library/dbm.rst:157 +msgid "The optional *flag* argument can be:" +msgstr "" + +#: ../Doc/library/dbm.rst:50 ../Doc/library/dbm.rst:162 +#: ../Doc/library/dbm.rst:277 ../Doc/library/functions.rst:911 +#: ../Doc/library/stdtypes.rst:2186 ../Doc/library/stdtypes.rst:3296 +#: ../Doc/library/sunau.rst:51 +msgid "``'r'``" +msgstr "" + +#: ../Doc/library/dbm.rst:50 ../Doc/library/dbm.rst:162 +#: ../Doc/library/dbm.rst:277 +msgid "Open existing database for reading only (default)" +msgstr "" + +#: ../Doc/library/dbm.rst:53 ../Doc/library/dbm.rst:165 +#: ../Doc/library/dbm.rst:280 ../Doc/library/functions.rst:912 +#: ../Doc/library/sunau.rst:54 +msgid "``'w'``" +msgstr "" + +#: ../Doc/library/dbm.rst:53 ../Doc/library/dbm.rst:165 +#: ../Doc/library/dbm.rst:280 +msgid "Open existing database for reading and writing" +msgstr "" + +#: ../Doc/library/dbm.rst:56 ../Doc/library/dbm.rst:168 +#: ../Doc/library/dbm.rst:283 ../Doc/library/stdtypes.rst:2183 +#: ../Doc/library/stdtypes.rst:3283 ../Doc/library/string.rst:427 +msgid "``'c'``" +msgstr "" + +#: ../Doc/library/dbm.rst:56 ../Doc/library/dbm.rst:168 +#: ../Doc/library/dbm.rst:283 +msgid "Open database for reading and writing, creating it if it doesn't exist" +msgstr "" + +#: ../Doc/library/dbm.rst:59 ../Doc/library/dbm.rst:171 +#: ../Doc/library/dbm.rst:286 ../Doc/library/string.rst:440 +#: ../Doc/library/string.rst:498 +msgid "``'n'``" +msgstr "" + +#: ../Doc/library/dbm.rst:59 ../Doc/library/dbm.rst:171 +#: ../Doc/library/dbm.rst:286 +msgid "Always create a new, empty database, open for reading and writing" +msgstr "" + +#: ../Doc/library/dbm.rst:63 ../Doc/library/dbm.rst:290 +#: ../Doc/library/dbm.rst:346 +msgid "" +"The optional *mode* argument is the Unix mode of the file, used only when " +"the database has to be created. It defaults to octal ``0o666`` (and will be " +"modified by the prevailing umask)." +msgstr "" + +#: ../Doc/library/dbm.rst:68 +msgid "" +"The object returned by :func:`.open` supports the same basic functionality " +"as dictionaries; keys and their corresponding values can be stored, " +"retrieved, and deleted, and the :keyword:`in` operator and the :meth:`keys` " +"method are available, as well as :meth:`get` and :meth:`setdefault`." +msgstr "" + +#: ../Doc/library/dbm.rst:73 +msgid "" +":meth:`get` and :meth:`setdefault` are now available in all database modules." +msgstr "" + +#: ../Doc/library/dbm.rst:76 +msgid "" +"Key and values are always stored as bytes. This means that when strings are " +"used they are implicitly converted to the default encoding before being " +"stored." +msgstr "" + +#: ../Doc/library/dbm.rst:80 +msgid "" +"These objects also support being used in a :keyword:`with` statement, which " +"will automatically close them when done." +msgstr "" + +#: ../Doc/library/dbm.rst:83 +msgid "" +"Added native support for the context management protocol to the objects " +"returned by :func:`.open`." +msgstr "" + +#: ../Doc/library/dbm.rst:87 +msgid "" +"The following example records some hostnames and a corresponding title, and " +"then prints out the contents of the database::" +msgstr "" + +#: ../Doc/library/dbm.rst:117 ../Doc/library/pickle.rst:904 +msgid "Module :mod:`shelve`" +msgstr "" + +#: ../Doc/library/dbm.rst:118 +msgid "Persistence module which stores non-string data." +msgstr "" + +#: ../Doc/library/dbm.rst:121 +msgid "The individual submodules are described in the following sections." +msgstr "" + +#: ../Doc/library/dbm.rst:125 +msgid ":mod:`dbm.gnu` --- GNU's reinterpretation of dbm" +msgstr "" + +#: ../Doc/library/dbm.rst:131 +msgid "**Source code:** :source:`Lib/dbm/gnu.py`" +msgstr "" + +#: ../Doc/library/dbm.rst:135 +msgid "" +"This module is quite similar to the :mod:`dbm` module, but uses the GNU " +"library ``gdbm`` instead to provide some additional functionality. Please " +"note that the file formats created by :mod:`dbm.gnu` and :mod:`dbm.ndbm` are " +"incompatible." +msgstr "" + +#: ../Doc/library/dbm.rst:139 +msgid "" +"The :mod:`dbm.gnu` module provides an interface to the GNU DBM library. " +"``dbm.gnu.gdbm`` objects behave like mappings (dictionaries), except that " +"keys and values are always converted to bytes before storing. Printing a " +"``gdbm`` object doesn't print the keys and values, and the :meth:`items` " +"and :meth:`values` methods are not supported." +msgstr "" + +#: ../Doc/library/dbm.rst:148 +msgid "" +"Raised on :mod:`dbm.gnu`-specific errors, such as I/O errors. :exc:" +"`KeyError` is raised for general mapping errors like specifying an incorrect " +"key." +msgstr "" + +#: ../Doc/library/dbm.rst:154 +msgid "" +"Open a ``gdbm`` database and return a :class:`gdbm` object. The *filename* " +"argument is the name of the database file." +msgstr "" + +#: ../Doc/library/dbm.rst:175 +msgid "" +"The following additional characters may be appended to the flag to control " +"how the database is opened:" +msgstr "" + +#: ../Doc/library/dbm.rst:181 +msgid "" +"Open the database in fast mode. Writes to the database will not be " +"synchronized." +msgstr "" + +#: ../Doc/library/dbm.rst:184 ../Doc/library/stdtypes.rst:2189 +#: ../Doc/library/stdtypes.rst:3290 ../Doc/library/string.rst:414 +msgid "``'s'``" +msgstr "" + +#: ../Doc/library/dbm.rst:184 +msgid "" +"Synchronized mode. This will cause changes to the database to be immediately " +"written to the file." +msgstr "" + +#: ../Doc/library/dbm.rst:188 +msgid "Do not lock database." +msgstr "" + +#: ../Doc/library/dbm.rst:191 +msgid "" +"Not all flags are valid for all versions of ``gdbm``. The module constant :" +"const:`open_flags` is a string of supported flag characters. The exception :" +"exc:`error` is raised if an invalid flag is specified." +msgstr "" + +#: ../Doc/library/dbm.rst:195 +msgid "" +"The optional *mode* argument is the Unix mode of the file, used only when " +"the database has to be created. It defaults to octal ``0o666``." +msgstr "" + +#: ../Doc/library/dbm.rst:198 +msgid "" +"In addition to the dictionary-like methods, ``gdbm`` objects have the " +"following methods:" +msgstr "" + +#: ../Doc/library/dbm.rst:203 +msgid "" +"It's possible to loop over every key in the database using this method and " +"the :meth:`nextkey` method. The traversal is ordered by ``gdbm``'s internal " +"hash values, and won't be sorted by the key values. This method returns the " +"starting key." +msgstr "" + +#: ../Doc/library/dbm.rst:210 +msgid "" +"Returns the key that follows *key* in the traversal. The following code " +"prints every key in the database ``db``, without having to create a list in " +"memory that contains them all::" +msgstr "" + +#: ../Doc/library/dbm.rst:221 +msgid "" +"If you have carried out a lot of deletions and would like to shrink the " +"space used by the ``gdbm`` file, this routine will reorganize the database. " +"``gdbm`` objects will not shorten the length of a database file except by " +"using this reorganization; otherwise, deleted file space will be kept and " +"reused as new (key, value) pairs are added." +msgstr "" + +#: ../Doc/library/dbm.rst:229 +msgid "" +"When the database has been opened in fast mode, this method forces any " +"unwritten data to be written to the disk." +msgstr "" + +#: ../Doc/library/dbm.rst:234 +msgid "Close the ``gdbm`` database." +msgstr "" + +#: ../Doc/library/dbm.rst:237 +msgid ":mod:`dbm.ndbm` --- Interface based on ndbm" +msgstr "" + +#: ../Doc/library/dbm.rst:243 +msgid "**Source code:** :source:`Lib/dbm/ndbm.py`" +msgstr "" + +#: ../Doc/library/dbm.rst:247 +msgid "" +"The :mod:`dbm.ndbm` module provides an interface to the Unix \"(n)dbm\" " +"library. Dbm objects behave like mappings (dictionaries), except that keys " +"and values are always stored as bytes. Printing a ``dbm`` object doesn't " +"print the keys and values, and the :meth:`items` and :meth:`values` methods " +"are not supported." +msgstr "" + +#: ../Doc/library/dbm.rst:252 +msgid "" +"This module can be used with the \"classic\" ndbm interface or the GNU GDBM " +"compatibility interface. On Unix, the :program:`configure` script will " +"attempt to locate the appropriate header file to simplify building this " +"module." +msgstr "" + +#: ../Doc/library/dbm.rst:258 +msgid "" +"Raised on :mod:`dbm.ndbm`-specific errors, such as I/O errors. :exc:" +"`KeyError` is raised for general mapping errors like specifying an incorrect " +"key." +msgstr "" + +#: ../Doc/library/dbm.rst:264 +msgid "Name of the ``ndbm`` implementation library used." +msgstr "" + +#: ../Doc/library/dbm.rst:269 +msgid "" +"Open a dbm database and return a ``ndbm`` object. The *filename* argument " +"is the name of the database file (without the :file:`.dir` or :file:`.pag` " +"extensions)." +msgstr "" + +#: ../Doc/library/dbm.rst:272 +msgid "The optional *flag* argument must be one of these values:" +msgstr "" + +#: ../Doc/library/dbm.rst:294 +msgid "" +"In addition to the dictionary-like methods, ``ndbm`` objects provide the " +"following method:" +msgstr "" + +#: ../Doc/library/dbm.rst:299 +msgid "Close the ``ndbm`` database." +msgstr "" + +#: ../Doc/library/dbm.rst:303 +msgid ":mod:`dbm.dumb` --- Portable DBM implementation" +msgstr "" + +#: ../Doc/library/dbm.rst:308 +msgid "**Source code:** :source:`Lib/dbm/dumb.py`" +msgstr "" + +#: ../Doc/library/dbm.rst:314 +msgid "" +"The :mod:`dbm.dumb` module is intended as a last resort fallback for the :" +"mod:`dbm` module when a more robust module is not available. The :mod:`dbm." +"dumb` module is not written for speed and is not nearly as heavily used as " +"the other database modules." +msgstr "" + +#: ../Doc/library/dbm.rst:321 +msgid "" +"The :mod:`dbm.dumb` module provides a persistent dictionary-like interface " +"which is written entirely in Python. Unlike other modules such as :mod:`dbm." +"gnu` no external library is required. As with other persistent mappings, " +"the keys and values are always stored as bytes." +msgstr "" + +#: ../Doc/library/dbm.rst:326 ../Doc/library/select.rst:26 +msgid "The module defines the following:" +msgstr "" + +#: ../Doc/library/dbm.rst:331 +msgid "" +"Raised on :mod:`dbm.dumb`-specific errors, such as I/O errors. :exc:" +"`KeyError` is raised for general mapping errors like specifying an incorrect " +"key." +msgstr "" + +#: ../Doc/library/dbm.rst:337 +msgid "" +"Open a ``dumbdbm`` database and return a dumbdbm object. The *filename* " +"argument is the basename of the database file (without any specific " +"extensions). When a dumbdbm database is created, files with :file:`.dat` " +"and :file:`.dir` extensions are created." +msgstr "" + +#: ../Doc/library/dbm.rst:342 +msgid "" +"The optional *flag* argument supports only the semantics of ``'c'`` and " +"``'n'`` values. Other values will default to database being always opened " +"for update, and will be created if it does not exist." +msgstr "" + +#: ../Doc/library/dbm.rst:350 +msgid "" +":func:`.open` always creates a new database when the flag has the value " +"``'n'``." +msgstr "" + +#: ../Doc/library/dbm.rst:357 +msgid "" +"Deprecated since version 3.6, will be removed in version 3.8: Creating " +"database in 'r' and 'w' modes. Modifying database in 'r' mode." +msgstr "" + +#: ../Doc/library/dbm.rst:357 +msgid "" +"Creating database in ``'r'`` and ``'w'`` modes. Modifying database in " +"``'r'`` mode." +msgstr "" + +#: ../Doc/library/dbm.rst:358 +msgid "" +"In addition to the methods provided by the :class:`collections.abc." +"MutableMapping` class, :class:`dumbdbm` objects provide the following " +"methods:" +msgstr "" + +#: ../Doc/library/dbm.rst:364 +msgid "" +"Synchronize the on-disk directory and data files. This method is called by " +"the :meth:`Shelve.sync` method." +msgstr "" + +#: ../Doc/library/dbm.rst:369 +msgid "Close the ``dumbdbm`` database." +msgstr "" + +#: ../Doc/library/debug.rst:3 +msgid "Debugging and Profiling" +msgstr "" + +#: ../Doc/library/debug.rst:5 +msgid "" +"These libraries help you with Python development: the debugger enables you " +"to step through code, analyze stack frames and set breakpoints etc., and the " +"profilers run code and give you a detailed breakdown of execution times, " +"allowing you to identify bottlenecks in your programs." +msgstr "" + +#: ../Doc/library/decimal.rst:2 +msgid ":mod:`decimal` --- Decimal fixed point and floating point arithmetic" +msgstr "" + +#: ../Doc/library/decimal.rst:15 +msgid "**Source code:** :source:`Lib/decimal.py`" +msgstr "" + +#: ../Doc/library/decimal.rst:28 +msgid "" +"The :mod:`decimal` module provides support for fast correctly-rounded " +"decimal floating point arithmetic. It offers several advantages over the :" +"class:`float` datatype:" +msgstr "" + +#: ../Doc/library/decimal.rst:32 +msgid "" +"Decimal \"is based on a floating-point model which was designed with people " +"in mind, and necessarily has a paramount guiding principle -- computers must " +"provide an arithmetic that works in the same way as the arithmetic that " +"people learn at school.\" -- excerpt from the decimal arithmetic " +"specification." +msgstr "" + +#: ../Doc/library/decimal.rst:37 +msgid "" +"Decimal numbers can be represented exactly. In contrast, numbers like :" +"const:`1.1` and :const:`2.2` do not have exact representations in binary " +"floating point. End users typically would not expect ``1.1 + 2.2`` to " +"display as :const:`3.3000000000000003` as it does with binary floating point." +msgstr "" + +#: ../Doc/library/decimal.rst:42 +msgid "" +"The exactness carries over into arithmetic. In decimal floating point, " +"``0.1 + 0.1 + 0.1 - 0.3`` is exactly equal to zero. In binary floating " +"point, the result is :const:`5.5511151231257827e-017`. While near to zero, " +"the differences prevent reliable equality testing and differences can " +"accumulate. For this reason, decimal is preferred in accounting applications " +"which have strict equality invariants." +msgstr "" + +#: ../Doc/library/decimal.rst:49 +msgid "" +"The decimal module incorporates a notion of significant places so that " +"``1.30 + 1.20`` is :const:`2.50`. The trailing zero is kept to indicate " +"significance. This is the customary presentation for monetary applications. " +"For multiplication, the \"schoolbook\" approach uses all the figures in the " +"multiplicands. For instance, ``1.3 * 1.2`` gives :const:`1.56` while ``1.30 " +"* 1.20`` gives :const:`1.5600`." +msgstr "" + +#: ../Doc/library/decimal.rst:56 +msgid "" +"Unlike hardware based binary floating point, the decimal module has a user " +"alterable precision (defaulting to 28 places) which can be as large as " +"needed for a given problem:" +msgstr "" + +#: ../Doc/library/decimal.rst:68 +msgid "" +"Both binary and decimal floating point are implemented in terms of published " +"standards. While the built-in float type exposes only a modest portion of " +"its capabilities, the decimal module exposes all required parts of the " +"standard. When needed, the programmer has full control over rounding and " +"signal handling. This includes an option to enforce exact arithmetic by " +"using exceptions to block any inexact operations." +msgstr "" + +#: ../Doc/library/decimal.rst:75 +msgid "" +"The decimal module was designed to support \"without prejudice, both exact " +"unrounded decimal arithmetic (sometimes called fixed-point arithmetic) and " +"rounded floating-point arithmetic.\" -- excerpt from the decimal arithmetic " +"specification." +msgstr "" + +#: ../Doc/library/decimal.rst:80 +msgid "" +"The module design is centered around three concepts: the decimal number, " +"the context for arithmetic, and signals." +msgstr "" + +#: ../Doc/library/decimal.rst:83 +msgid "" +"A decimal number is immutable. It has a sign, coefficient digits, and an " +"exponent. To preserve significance, the coefficient digits do not truncate " +"trailing zeros. Decimals also include special values such as :const:" +"`Infinity`, :const:`-Infinity`, and :const:`NaN`. The standard also " +"differentiates :const:`-0` from :const:`+0`." +msgstr "" + +#: ../Doc/library/decimal.rst:89 +msgid "" +"The context for arithmetic is an environment specifying precision, rounding " +"rules, limits on exponents, flags indicating the results of operations, and " +"trap enablers which determine whether signals are treated as exceptions. " +"Rounding options include :const:`ROUND_CEILING`, :const:`ROUND_DOWN`, :const:" +"`ROUND_FLOOR`, :const:`ROUND_HALF_DOWN`, :const:`ROUND_HALF_EVEN`, :const:" +"`ROUND_HALF_UP`, :const:`ROUND_UP`, and :const:`ROUND_05UP`." +msgstr "" + +#: ../Doc/library/decimal.rst:96 +msgid "" +"Signals are groups of exceptional conditions arising during the course of " +"computation. Depending on the needs of the application, signals may be " +"ignored, considered as informational, or treated as exceptions. The signals " +"in the decimal module are: :const:`Clamped`, :const:`InvalidOperation`, :" +"const:`DivisionByZero`, :const:`Inexact`, :const:`Rounded`, :const:" +"`Subnormal`, :const:`Overflow`, :const:`Underflow` and :const:" +"`FloatOperation`." +msgstr "" + +#: ../Doc/library/decimal.rst:103 +msgid "" +"For each signal there is a flag and a trap enabler. When a signal is " +"encountered, its flag is set to one, then, if the trap enabler is set to " +"one, an exception is raised. Flags are sticky, so the user needs to reset " +"them before monitoring a calculation." +msgstr "" + +#: ../Doc/library/decimal.rst:111 +msgid "" +"IBM's General Decimal Arithmetic Specification, `The General Decimal " +"Arithmetic Specification `_." +msgstr "" + +#: ../Doc/library/decimal.rst:120 +msgid "Quick-start Tutorial" +msgstr "" + +#: ../Doc/library/decimal.rst:122 +msgid "" +"The usual start to using decimals is importing the module, viewing the " +"current context with :func:`getcontext` and, if necessary, setting new " +"values for precision, rounding, or enabled traps::" +msgstr "" + +#: ../Doc/library/decimal.rst:134 +msgid "" +"Decimal instances can be constructed from integers, strings, floats, or " +"tuples. Construction from an integer or a float performs an exact conversion " +"of the value of that integer or float. Decimal numbers include special " +"values such as :const:`NaN` which stands for \"Not a number\", positive and " +"negative :const:`Infinity`, and :const:`-0`::" +msgstr "" + +#: ../Doc/library/decimal.rst:158 +msgid "" +"If the :exc:`FloatOperation` signal is trapped, accidental mixing of " +"decimals and floats in constructors or ordering comparisons raises an " +"exception::" +msgstr "" + +#: ../Doc/library/decimal.rst:177 +msgid "" +"The significance of a new Decimal is determined solely by the number of " +"digits input. Context precision and rounding only come into play during " +"arithmetic operations." +msgstr "" + +#: ../Doc/library/decimal.rst:194 +msgid "" +"If the internal limits of the C version are exceeded, constructing a decimal " +"raises :class:`InvalidOperation`::" +msgstr "" + +#: ../Doc/library/decimal.rst:204 +msgid "" +"Decimals interact well with much of the rest of Python. Here is a small " +"decimal floating point flying circus:" +msgstr "" + +#: ../Doc/library/decimal.rst:236 +msgid "And some mathematical functions are also available to Decimal:" +msgstr "" + +#: ../Doc/library/decimal.rst:248 +msgid "" +"The :meth:`quantize` method rounds a number to a fixed exponent. This " +"method is useful for monetary applications that often round results to a " +"fixed number of places:" +msgstr "" + +#: ../Doc/library/decimal.rst:257 +msgid "" +"As shown above, the :func:`getcontext` function accesses the current context " +"and allows the settings to be changed. This approach meets the needs of " +"most applications." +msgstr "" + +#: ../Doc/library/decimal.rst:261 +msgid "" +"For more advanced work, it may be useful to create alternate contexts using " +"the Context() constructor. To make an alternate active, use the :func:" +"`setcontext` function." +msgstr "" + +#: ../Doc/library/decimal.rst:265 +msgid "" +"In accordance with the standard, the :mod:`decimal` module provides two " +"ready to use standard contexts, :const:`BasicContext` and :const:" +"`ExtendedContext`. The former is especially useful for debugging because " +"many of the traps are enabled:" +msgstr "" + +#: ../Doc/library/decimal.rst:294 +msgid "" +"Contexts also have signal flags for monitoring exceptional conditions " +"encountered during computations. The flags remain set until explicitly " +"cleared, so it is best to clear the flags before each set of monitored " +"computations by using the :meth:`clear_flags` method. ::" +msgstr "" + +#: ../Doc/library/decimal.rst:307 +msgid "" +"The *flags* entry shows that the rational approximation to :const:`Pi` was " +"rounded (digits beyond the context precision were thrown away) and that the " +"result is inexact (some of the discarded digits were non-zero)." +msgstr "" + +#: ../Doc/library/decimal.rst:311 +msgid "" +"Individual traps are set using the dictionary in the :attr:`traps` field of " +"a context:" +msgstr "" + +#: ../Doc/library/decimal.rst:326 +msgid "" +"Most programs adjust the current context only once, at the beginning of the " +"program. And, in many applications, data is converted to :class:`Decimal` " +"with a single cast inside a loop. With context set and decimals created, " +"the bulk of the program manipulates the data no differently than with other " +"Python numeric types." +msgstr "" + +#: ../Doc/library/decimal.rst:338 +msgid "Decimal objects" +msgstr "" + +#: ../Doc/library/decimal.rst:343 +msgid "Construct a new :class:`Decimal` object based from *value*." +msgstr "" + +#: ../Doc/library/decimal.rst:345 +msgid "" +"*value* can be an integer, string, tuple, :class:`float`, or another :class:" +"`Decimal` object. If no *value* is given, returns ``Decimal('0')``. If " +"*value* is a string, it should conform to the decimal numeric string syntax " +"after leading and trailing whitespace characters, as well as underscores " +"throughout, are removed::" +msgstr "" + +#: ../Doc/library/decimal.rst:361 +msgid "" +"Other Unicode decimal digits are also permitted where ``digit`` appears " +"above. These include decimal digits from various other alphabets (for " +"example, Arabic-Indic and Devanāgarī digits) along with the fullwidth digits " +"``'\\uff10'`` through ``'\\uff19'``." +msgstr "" + +#: ../Doc/library/decimal.rst:366 +msgid "" +"If *value* is a :class:`tuple`, it should have three components, a sign (:" +"const:`0` for positive or :const:`1` for negative), a :class:`tuple` of " +"digits, and an integer exponent. For example, ``Decimal((0, (1, 4, 1, 4), " +"-3))`` returns ``Decimal('1.414')``." +msgstr "" + +#: ../Doc/library/decimal.rst:371 +msgid "" +"If *value* is a :class:`float`, the binary floating point value is " +"losslessly converted to its exact decimal equivalent. This conversion can " +"often require 53 or more digits of precision. For example, " +"``Decimal(float('1.1'))`` converts to " +"``Decimal('1.100000000000000088817841970012523233890533447265625')``." +msgstr "" + +#: ../Doc/library/decimal.rst:377 +msgid "" +"The *context* precision does not affect how many digits are stored. That is " +"determined exclusively by the number of digits in *value*. For example, " +"``Decimal('3.00000')`` records all five zeros even if the context precision " +"is only three." +msgstr "" + +#: ../Doc/library/decimal.rst:382 +msgid "" +"The purpose of the *context* argument is determining what to do if *value* " +"is a malformed string. If the context traps :const:`InvalidOperation`, an " +"exception is raised; otherwise, the constructor returns a new Decimal with " +"the value of :const:`NaN`." +msgstr "" + +#: ../Doc/library/decimal.rst:387 +msgid "Once constructed, :class:`Decimal` objects are immutable." +msgstr "" + +#: ../Doc/library/decimal.rst:389 +msgid "" +"The argument to the constructor is now permitted to be a :class:`float` " +"instance." +msgstr "" + +#: ../Doc/library/decimal.rst:393 +msgid "" +":class:`float` arguments raise an exception if the :exc:`FloatOperation` " +"trap is set. By default the trap is off." +msgstr "" + +#: ../Doc/library/decimal.rst:397 +msgid "" +"Underscores are allowed for grouping, as with integral and floating-point " +"literals in code." +msgstr "" + +#: ../Doc/library/decimal.rst:401 +msgid "" +"Decimal floating point objects share many properties with the other built-in " +"numeric types such as :class:`float` and :class:`int`. All of the usual " +"math operations and special methods apply. Likewise, decimal objects can be " +"copied, pickled, printed, used as dictionary keys, used as set elements, " +"compared, sorted, and coerced to another type (such as :class:`float` or :" +"class:`int`)." +msgstr "" + +#: ../Doc/library/decimal.rst:408 +msgid "" +"There are some small differences between arithmetic on Decimal objects and " +"arithmetic on integers and floats. When the remainder operator ``%`` is " +"applied to Decimal objects, the sign of the result is the sign of the " +"*dividend* rather than the sign of the divisor::" +msgstr "" + +#: ../Doc/library/decimal.rst:418 +msgid "" +"The integer division operator ``//`` behaves analogously, returning the " +"integer part of the true quotient (truncating towards zero) rather than its " +"floor, so as to preserve the usual identity ``x == (x // y) * y + x % y``::" +msgstr "" + +#: ../Doc/library/decimal.rst:427 +msgid "" +"The ``%`` and ``//`` operators implement the ``remainder`` and ``divide-" +"integer`` operations (respectively) as described in the specification." +msgstr "" + +#: ../Doc/library/decimal.rst:431 +msgid "" +"Decimal objects cannot generally be combined with floats or instances of :" +"class:`fractions.Fraction` in arithmetic operations: an attempt to add a :" +"class:`Decimal` to a :class:`float`, for example, will raise a :exc:" +"`TypeError`. However, it is possible to use Python's comparison operators " +"to compare a :class:`Decimal` instance ``x`` with another number ``y``. " +"This avoids confusing results when doing equality comparisons between " +"numbers of different types." +msgstr "" + +#: ../Doc/library/decimal.rst:439 +msgid "" +"Mixed-type comparisons between :class:`Decimal` instances and other numeric " +"types are now fully supported." +msgstr "" + +#: ../Doc/library/decimal.rst:443 +msgid "" +"In addition to the standard numeric properties, decimal floating point " +"objects also have a number of specialized methods:" +msgstr "" + +#: ../Doc/library/decimal.rst:449 +msgid "" +"Return the adjusted exponent after shifting out the coefficient's rightmost " +"digits until only the lead digit remains: ``Decimal('321e+5').adjusted()`` " +"returns seven. Used for determining the position of the most significant " +"digit with respect to the decimal point." +msgstr "" + +#: ../Doc/library/decimal.rst:456 +msgid "" +"Return a pair ``(n, d)`` of integers that represent the given :class:" +"`Decimal` instance as a fraction, in lowest terms and with a positive " +"denominator::" +msgstr "" + +#: ../Doc/library/decimal.rst:463 +msgid "" +"The conversion is exact. Raise OverflowError on infinities and ValueError " +"on NaNs." +msgstr "" + +#: ../Doc/library/decimal.rst:470 +msgid "" +"Return a :term:`named tuple` representation of the number: " +"``DecimalTuple(sign, digits, exponent)``." +msgstr "" + +#: ../Doc/library/decimal.rst:476 +msgid "" +"Return the canonical encoding of the argument. Currently, the encoding of " +"a :class:`Decimal` instance is always canonical, so this operation returns " +"its argument unchanged." +msgstr "" + +#: ../Doc/library/decimal.rst:482 +msgid "" +"Compare the values of two Decimal instances. :meth:`compare` returns a " +"Decimal instance, and if either operand is a NaN then the result is a NaN::" +msgstr "" + +#: ../Doc/library/decimal.rst:493 +msgid "" +"This operation is identical to the :meth:`compare` method, except that all " +"NaNs signal. That is, if neither operand is a signaling NaN then any quiet " +"NaN operand is treated as though it were a signaling NaN." +msgstr "" + +#: ../Doc/library/decimal.rst:499 +msgid "" +"Compare two operands using their abstract representation rather than their " +"numerical value. Similar to the :meth:`compare` method, but the result " +"gives a total ordering on :class:`Decimal` instances. Two :class:`Decimal` " +"instances with the same numeric value but different representations compare " +"unequal in this ordering:" +msgstr "" + +#: ../Doc/library/decimal.rst:508 +msgid "" +"Quiet and signaling NaNs are also included in the total ordering. The " +"result of this function is ``Decimal('0')`` if both operands have the same " +"representation, ``Decimal('-1')`` if the first operand is lower in the total " +"order than the second, and ``Decimal('1')`` if the first operand is higher " +"in the total order than the second operand. See the specification for " +"details of the total order." +msgstr "" + +#: ../Doc/library/decimal.rst:515 ../Doc/library/decimal.rst:526 +#: ../Doc/library/decimal.rst:554 ../Doc/library/decimal.rst:829 +msgid "" +"This operation is unaffected by context and is quiet: no flags are changed " +"and no rounding is performed. As an exception, the C version may raise " +"InvalidOperation if the second operand cannot be converted exactly." +msgstr "" + +#: ../Doc/library/decimal.rst:521 +msgid "" +"Compare two operands using their abstract representation rather than their " +"value as in :meth:`compare_total`, but ignoring the sign of each operand. " +"``x.compare_total_mag(y)`` is equivalent to ``x.copy_abs().compare_total(y." +"copy_abs())``." +msgstr "" + +#: ../Doc/library/decimal.rst:532 +msgid "" +"Just returns self, this method is only to comply with the Decimal " +"Specification." +msgstr "" + +#: ../Doc/library/decimal.rst:537 +msgid "" +"Return the absolute value of the argument. This operation is unaffected by " +"the context and is quiet: no flags are changed and no rounding is performed." +msgstr "" + +#: ../Doc/library/decimal.rst:543 +msgid "" +"Return the negation of the argument. This operation is unaffected by the " +"context and is quiet: no flags are changed and no rounding is performed." +msgstr "" + +#: ../Doc/library/decimal.rst:548 +msgid "" +"Return a copy of the first operand with the sign set to be the same as the " +"sign of the second operand. For example:" +msgstr "" + +#: ../Doc/library/decimal.rst:560 +msgid "" +"Return the value of the (natural) exponential function ``e**x`` at the given " +"number. The result is correctly rounded using the :const:`ROUND_HALF_EVEN` " +"rounding mode." +msgstr "" + +#: ../Doc/library/decimal.rst:571 +msgid "Classmethod that converts a float to a decimal number, exactly." +msgstr "" + +#: ../Doc/library/decimal.rst:573 +msgid "" +"Note `Decimal.from_float(0.1)` is not the same as `Decimal('0.1')`. Since " +"0.1 is not exactly representable in binary floating point, the value is " +"stored as the nearest representable value which is `0x1.999999999999ap-4`. " +"That equivalent value in decimal is " +"`0.1000000000000000055511151231257827021181583404541015625`." +msgstr "" + +#: ../Doc/library/decimal.rst:579 +msgid "" +"From Python 3.2 onwards, a :class:`Decimal` instance can also be constructed " +"directly from a :class:`float`." +msgstr "" + +#: ../Doc/library/decimal.rst:597 +msgid "" +"Fused multiply-add. Return self*other+third with no rounding of the " +"intermediate product self*other." +msgstr "" + +#: ../Doc/library/decimal.rst:605 +msgid "" +"Return :const:`True` if the argument is canonical and :const:`False` " +"otherwise. Currently, a :class:`Decimal` instance is always canonical, so " +"this operation always returns :const:`True`." +msgstr "" + +#: ../Doc/library/decimal.rst:611 +msgid "" +"Return :const:`True` if the argument is a finite number, and :const:`False` " +"if the argument is an infinity or a NaN." +msgstr "" + +#: ../Doc/library/decimal.rst:616 +msgid "" +"Return :const:`True` if the argument is either positive or negative infinity " +"and :const:`False` otherwise." +msgstr "" + +#: ../Doc/library/decimal.rst:621 +msgid "" +"Return :const:`True` if the argument is a (quiet or signaling) NaN and :" +"const:`False` otherwise." +msgstr "" + +#: ../Doc/library/decimal.rst:626 +msgid "" +"Return :const:`True` if the argument is a *normal* finite number. Return :" +"const:`False` if the argument is zero, subnormal, infinite or a NaN." +msgstr "" + +#: ../Doc/library/decimal.rst:631 +msgid "" +"Return :const:`True` if the argument is a quiet NaN, and :const:`False` " +"otherwise." +msgstr "" + +#: ../Doc/library/decimal.rst:636 +msgid "" +"Return :const:`True` if the argument has a negative sign and :const:`False` " +"otherwise. Note that zeros and NaNs can both carry signs." +msgstr "" + +#: ../Doc/library/decimal.rst:641 +msgid "" +"Return :const:`True` if the argument is a signaling NaN and :const:`False` " +"otherwise." +msgstr "" + +#: ../Doc/library/decimal.rst:646 +msgid "" +"Return :const:`True` if the argument is subnormal, and :const:`False` " +"otherwise." +msgstr "" + +#: ../Doc/library/decimal.rst:651 +msgid "" +"Return :const:`True` if the argument is a (positive or negative) zero and :" +"const:`False` otherwise." +msgstr "" + +#: ../Doc/library/decimal.rst:656 +msgid "" +"Return the natural (base e) logarithm of the operand. The result is " +"correctly rounded using the :const:`ROUND_HALF_EVEN` rounding mode." +msgstr "" + +#: ../Doc/library/decimal.rst:661 +msgid "" +"Return the base ten logarithm of the operand. The result is correctly " +"rounded using the :const:`ROUND_HALF_EVEN` rounding mode." +msgstr "" + +#: ../Doc/library/decimal.rst:666 +msgid "" +"For a nonzero number, return the adjusted exponent of its operand as a :" +"class:`Decimal` instance. If the operand is a zero then ``Decimal('-" +"Infinity')`` is returned and the :const:`DivisionByZero` flag is raised. If " +"the operand is an infinity then ``Decimal('Infinity')`` is returned." +msgstr "" + +#: ../Doc/library/decimal.rst:674 +msgid "" +":meth:`logical_and` is a logical operation which takes two *logical " +"operands* (see :ref:`logical_operands_label`). The result is the digit-wise " +"``and`` of the two operands." +msgstr "" + +#: ../Doc/library/decimal.rst:680 +msgid "" +":meth:`logical_invert` is a logical operation. The result is the digit-wise " +"inversion of the operand." +msgstr "" + +#: ../Doc/library/decimal.rst:685 +msgid "" +":meth:`logical_or` is a logical operation which takes two *logical operands* " +"(see :ref:`logical_operands_label`). The result is the digit-wise ``or`` of " +"the two operands." +msgstr "" + +#: ../Doc/library/decimal.rst:691 +msgid "" +":meth:`logical_xor` is a logical operation which takes two *logical " +"operands* (see :ref:`logical_operands_label`). The result is the digit-wise " +"exclusive or of the two operands." +msgstr "" + +#: ../Doc/library/decimal.rst:697 +msgid "" +"Like ``max(self, other)`` except that the context rounding rule is applied " +"before returning and that :const:`NaN` values are either signaled or ignored " +"(depending on the context and whether they are signaling or quiet)." +msgstr "" + +#: ../Doc/library/decimal.rst:704 +msgid "" +"Similar to the :meth:`.max` method, but the comparison is done using the " +"absolute values of the operands." +msgstr "" + +#: ../Doc/library/decimal.rst:709 +msgid "" +"Like ``min(self, other)`` except that the context rounding rule is applied " +"before returning and that :const:`NaN` values are either signaled or ignored " +"(depending on the context and whether they are signaling or quiet)." +msgstr "" + +#: ../Doc/library/decimal.rst:716 +msgid "" +"Similar to the :meth:`.min` method, but the comparison is done using the " +"absolute values of the operands." +msgstr "" + +#: ../Doc/library/decimal.rst:721 +msgid "" +"Return the largest number representable in the given context (or in the " +"current thread's context if no context is given) that is smaller than the " +"given operand." +msgstr "" + +#: ../Doc/library/decimal.rst:727 +msgid "" +"Return the smallest number representable in the given context (or in the " +"current thread's context if no context is given) that is larger than the " +"given operand." +msgstr "" + +#: ../Doc/library/decimal.rst:733 +msgid "" +"If the two operands are unequal, return the number closest to the first " +"operand in the direction of the second operand. If both operands are " +"numerically equal, return a copy of the first operand with the sign set to " +"be the same as the sign of the second operand." +msgstr "" + +#: ../Doc/library/decimal.rst:740 +msgid "" +"Normalize the number by stripping the rightmost trailing zeros and " +"converting any result equal to :const:`Decimal('0')` to :const:" +"`Decimal('0e0')`. Used for producing canonical values for attributes of an " +"equivalence class. For example, ``Decimal('32.100')`` and " +"``Decimal('0.321000e+2')`` both normalize to the equivalent value " +"``Decimal('32.1')``." +msgstr "" + +#: ../Doc/library/decimal.rst:749 +msgid "" +"Return a string describing the *class* of the operand. The returned value " +"is one of the following ten strings." +msgstr "" + +#: ../Doc/library/decimal.rst:752 +msgid "``\"-Infinity\"``, indicating that the operand is negative infinity." +msgstr "" + +#: ../Doc/library/decimal.rst:753 +msgid "" +"``\"-Normal\"``, indicating that the operand is a negative normal number." +msgstr "" + +#: ../Doc/library/decimal.rst:754 +msgid "" +"``\"-Subnormal\"``, indicating that the operand is negative and subnormal." +msgstr "" + +#: ../Doc/library/decimal.rst:755 +msgid "``\"-Zero\"``, indicating that the operand is a negative zero." +msgstr "" + +#: ../Doc/library/decimal.rst:756 +msgid "``\"+Zero\"``, indicating that the operand is a positive zero." +msgstr "" + +#: ../Doc/library/decimal.rst:757 +msgid "" +"``\"+Subnormal\"``, indicating that the operand is positive and subnormal." +msgstr "" + +#: ../Doc/library/decimal.rst:758 +msgid "" +"``\"+Normal\"``, indicating that the operand is a positive normal number." +msgstr "" + +#: ../Doc/library/decimal.rst:759 +msgid "``\"+Infinity\"``, indicating that the operand is positive infinity." +msgstr "" + +#: ../Doc/library/decimal.rst:760 +msgid "``\"NaN\"``, indicating that the operand is a quiet NaN (Not a Number)." +msgstr "" + +#: ../Doc/library/decimal.rst:761 +msgid "``\"sNaN\"``, indicating that the operand is a signaling NaN." +msgstr "" + +#: ../Doc/library/decimal.rst:765 +msgid "" +"Return a value equal to the first operand after rounding and having the " +"exponent of the second operand." +msgstr "" + +#: ../Doc/library/decimal.rst:771 +msgid "" +"Unlike other operations, if the length of the coefficient after the quantize " +"operation would be greater than precision, then an :const:`InvalidOperation` " +"is signaled. This guarantees that, unless there is an error condition, the " +"quantized exponent is always equal to that of the right-hand operand." +msgstr "" + +#: ../Doc/library/decimal.rst:777 +msgid "" +"Also unlike other operations, quantize never signals Underflow, even if the " +"result is subnormal and inexact." +msgstr "" + +#: ../Doc/library/decimal.rst:780 +msgid "" +"If the exponent of the second operand is larger than that of the first then " +"rounding may be necessary. In this case, the rounding mode is determined by " +"the ``rounding`` argument if given, else by the given ``context`` argument; " +"if neither argument is given the rounding mode of the current thread's " +"context is used." +msgstr "" + +#: ../Doc/library/decimal.rst:786 +msgid "" +"An error is returned whenever the resulting exponent is greater than :attr:" +"`Emax` or less than :attr:`Etiny`." +msgstr "" + +#: ../Doc/library/decimal.rst:791 +msgid "" +"Return ``Decimal(10)``, the radix (base) in which the :class:`Decimal` class " +"does all its arithmetic. Included for compatibility with the specification." +msgstr "" + +#: ../Doc/library/decimal.rst:797 +msgid "" +"Return the remainder from dividing *self* by *other*. This differs from " +"``self % other`` in that the sign of the remainder is chosen so as to " +"minimize its absolute value. More precisely, the return value is ``self - n " +"* other`` where ``n`` is the integer nearest to the exact value of ``self / " +"other``, and if two integers are equally near then the even one is chosen." +msgstr "" + +#: ../Doc/library/decimal.rst:804 +msgid "If the result is zero then its sign will be the sign of *self*." +msgstr "" + +#: ../Doc/library/decimal.rst:815 +msgid "" +"Return the result of rotating the digits of the first operand by an amount " +"specified by the second operand. The second operand must be an integer in " +"the range -precision through precision. The absolute value of the second " +"operand gives the number of places to rotate. If the second operand is " +"positive then rotation is to the left; otherwise rotation is to the right. " +"The coefficient of the first operand is padded on the left with zeros to " +"length precision if necessary. The sign and exponent of the first operand " +"are unchanged." +msgstr "" + +#: ../Doc/library/decimal.rst:826 +msgid "" +"Test whether self and other have the same exponent or whether both are :" +"const:`NaN`." +msgstr "" + +#: ../Doc/library/decimal.rst:835 +msgid "" +"Return the first operand with exponent adjusted by the second. Equivalently, " +"return the first operand multiplied by ``10**other``. The second operand " +"must be an integer." +msgstr "" + +#: ../Doc/library/decimal.rst:841 +msgid "" +"Return the result of shifting the digits of the first operand by an amount " +"specified by the second operand. The second operand must be an integer in " +"the range -precision through precision. The absolute value of the second " +"operand gives the number of places to shift. If the second operand is " +"positive then the shift is to the left; otherwise the shift is to the " +"right. Digits shifted into the coefficient are zeros. The sign and " +"exponent of the first operand are unchanged." +msgstr "" + +#: ../Doc/library/decimal.rst:851 +msgid "Return the square root of the argument to full precision." +msgstr "" + +#: ../Doc/library/decimal.rst:856 ../Doc/library/decimal.rst:1432 +msgid "" +"Convert to a string, using engineering notation if an exponent is needed." +msgstr "" + +#: ../Doc/library/decimal.rst:858 ../Doc/library/decimal.rst:1434 +msgid "" +"Engineering notation has an exponent which is a multiple of 3. This can " +"leave up to 3 digits to the left of the decimal place and may require the " +"addition of either one or two trailing zeros." +msgstr "" + +#: ../Doc/library/decimal.rst:862 +msgid "" +"For example, this converts ``Decimal('123E+1')`` to ``Decimal('1.23E+3')``." +msgstr "" + +#: ../Doc/library/decimal.rst:866 +msgid "" +"Identical to the :meth:`to_integral_value` method. The ``to_integral`` name " +"has been kept for compatibility with older versions." +msgstr "" + +#: ../Doc/library/decimal.rst:871 +msgid "" +"Round to the nearest integer, signaling :const:`Inexact` or :const:`Rounded` " +"as appropriate if rounding occurs. The rounding mode is determined by the " +"``rounding`` parameter if given, else by the given ``context``. If neither " +"parameter is given then the rounding mode of the current context is used." +msgstr "" + +#: ../Doc/library/decimal.rst:879 +msgid "" +"Round to the nearest integer without signaling :const:`Inexact` or :const:" +"`Rounded`. If given, applies *rounding*; otherwise, uses the rounding " +"method in either the supplied *context* or the current context." +msgstr "" + +#: ../Doc/library/decimal.rst:887 +msgid "Logical operands" +msgstr "" + +#: ../Doc/library/decimal.rst:889 +msgid "" +"The :meth:`logical_and`, :meth:`logical_invert`, :meth:`logical_or`, and :" +"meth:`logical_xor` methods expect their arguments to be *logical operands*. " +"A *logical operand* is a :class:`Decimal` instance whose exponent and sign " +"are both zero, and whose digits are all either :const:`0` or :const:`1`." +msgstr "" + +#: ../Doc/library/decimal.rst:901 +msgid "Context objects" +msgstr "" + +#: ../Doc/library/decimal.rst:903 +msgid "" +"Contexts are environments for arithmetic operations. They govern precision, " +"set rules for rounding, determine which signals are treated as exceptions, " +"and limit the range for exponents." +msgstr "" + +#: ../Doc/library/decimal.rst:907 +msgid "" +"Each thread has its own current context which is accessed or changed using " +"the :func:`getcontext` and :func:`setcontext` functions:" +msgstr "" + +#: ../Doc/library/decimal.rst:913 +msgid "Return the current context for the active thread." +msgstr "" + +#: ../Doc/library/decimal.rst:918 +msgid "Set the current context for the active thread to *c*." +msgstr "" + +#: ../Doc/library/decimal.rst:920 +msgid "" +"You can also use the :keyword:`with` statement and the :func:`localcontext` " +"function to temporarily change the active context." +msgstr "" + +#: ../Doc/library/decimal.rst:925 +msgid "" +"Return a context manager that will set the current context for the active " +"thread to a copy of *ctx* on entry to the with-statement and restore the " +"previous context when exiting the with-statement. If no context is " +"specified, a copy of the current context is used." +msgstr "" + +#: ../Doc/library/decimal.rst:930 +msgid "" +"For example, the following code sets the current decimal precision to 42 " +"places, performs a calculation, and then automatically restores the previous " +"context::" +msgstr "" + +#: ../Doc/library/decimal.rst:940 +msgid "" +"New contexts can also be created using the :class:`Context` constructor " +"described below. In addition, the module provides three pre-made contexts:" +msgstr "" + +#: ../Doc/library/decimal.rst:946 +msgid "" +"This is a standard context defined by the General Decimal Arithmetic " +"Specification. Precision is set to nine. Rounding is set to :const:" +"`ROUND_HALF_UP`. All flags are cleared. All traps are enabled (treated as " +"exceptions) except :const:`Inexact`, :const:`Rounded`, and :const:" +"`Subnormal`." +msgstr "" + +#: ../Doc/library/decimal.rst:952 +msgid "" +"Because many of the traps are enabled, this context is useful for debugging." +msgstr "" + +#: ../Doc/library/decimal.rst:957 +msgid "" +"This is a standard context defined by the General Decimal Arithmetic " +"Specification. Precision is set to nine. Rounding is set to :const:" +"`ROUND_HALF_EVEN`. All flags are cleared. No traps are enabled (so that " +"exceptions are not raised during computations)." +msgstr "" + +#: ../Doc/library/decimal.rst:962 +msgid "" +"Because the traps are disabled, this context is useful for applications that " +"prefer to have result value of :const:`NaN` or :const:`Infinity` instead of " +"raising exceptions. This allows an application to complete a run in the " +"presence of conditions that would otherwise halt the program." +msgstr "" + +#: ../Doc/library/decimal.rst:970 +msgid "" +"This context is used by the :class:`Context` constructor as a prototype for " +"new contexts. Changing a field (such a precision) has the effect of " +"changing the default for new contexts created by the :class:`Context` " +"constructor." +msgstr "" + +#: ../Doc/library/decimal.rst:974 +msgid "" +"This context is most useful in multi-threaded environments. Changing one of " +"the fields before threads are started has the effect of setting system-wide " +"defaults. Changing the fields after threads have started is not recommended " +"as it would require thread synchronization to prevent race conditions." +msgstr "" + +#: ../Doc/library/decimal.rst:979 +msgid "" +"In single threaded environments, it is preferable to not use this context at " +"all. Instead, simply create contexts explicitly as described below." +msgstr "" + +#: ../Doc/library/decimal.rst:982 +msgid "" +"The default values are :attr:`prec`\\ =\\ :const:`28`, :attr:`rounding`\\ =" +"\\ :const:`ROUND_HALF_EVEN`, and enabled traps for :class:`Overflow`, :class:" +"`InvalidOperation`, and :class:`DivisionByZero`." +msgstr "" + +#: ../Doc/library/decimal.rst:987 +msgid "" +"In addition to the three supplied contexts, new contexts can be created with " +"the :class:`Context` constructor." +msgstr "" + +#: ../Doc/library/decimal.rst:993 +msgid "" +"Creates a new context. If a field is not specified or is :const:`None`, the " +"default values are copied from the :const:`DefaultContext`. If the *flags* " +"field is not specified or is :const:`None`, all flags are cleared." +msgstr "" + +#: ../Doc/library/decimal.rst:997 +msgid "" +"*prec* is an integer in the range [:const:`1`, :const:`MAX_PREC`] that sets " +"the precision for arithmetic operations in the context." +msgstr "" + +#: ../Doc/library/decimal.rst:1000 +msgid "" +"The *rounding* option is one of the constants listed in the section " +"`Rounding Modes`_." +msgstr "" + +#: ../Doc/library/decimal.rst:1003 +msgid "" +"The *traps* and *flags* fields list any signals to be set. Generally, new " +"contexts should only set traps and leave the flags clear." +msgstr "" + +#: ../Doc/library/decimal.rst:1006 +msgid "" +"The *Emin* and *Emax* fields are integers specifying the outer limits " +"allowable for exponents. *Emin* must be in the range [:const:`MIN_EMIN`, :" +"const:`0`], *Emax* in the range [:const:`0`, :const:`MAX_EMAX`]." +msgstr "" + +#: ../Doc/library/decimal.rst:1010 +msgid "" +"The *capitals* field is either :const:`0` or :const:`1` (the default). If " +"set to :const:`1`, exponents are printed with a capital :const:`E`; " +"otherwise, a lowercase :const:`e` is used: :const:`Decimal('6.02e+23')`." +msgstr "" + +#: ../Doc/library/decimal.rst:1014 +msgid "" +"The *clamp* field is either :const:`0` (the default) or :const:`1`. If set " +"to :const:`1`, the exponent ``e`` of a :class:`Decimal` instance " +"representable in this context is strictly limited to the range ``Emin - prec " +"+ 1 <= e <= Emax - prec + 1``. If *clamp* is :const:`0` then a weaker " +"condition holds: the adjusted exponent of the :class:`Decimal` instance is " +"at most ``Emax``. When *clamp* is :const:`1`, a large normal number will, " +"where possible, have its exponent reduced and a corresponding number of " +"zeros added to its coefficient, in order to fit the exponent constraints; " +"this preserves the value of the number but loses information about " +"significant trailing zeros. For example::" +msgstr "" + +#: ../Doc/library/decimal.rst:1029 +msgid "" +"A *clamp* value of :const:`1` allows compatibility with the fixed-width " +"decimal interchange formats specified in IEEE 754." +msgstr "" + +#: ../Doc/library/decimal.rst:1032 +msgid "" +"The :class:`Context` class defines several general purpose methods as well " +"as a large number of methods for doing arithmetic directly in a given " +"context. In addition, for each of the :class:`Decimal` methods described " +"above (with the exception of the :meth:`adjusted` and :meth:`as_tuple` " +"methods) there is a corresponding :class:`Context` method. For example, for " +"a :class:`Context` instance ``C`` and :class:`Decimal` instance ``x``, ``C." +"exp(x)`` is equivalent to ``x.exp(context=C)``. Each :class:`Context` " +"method accepts a Python integer (an instance of :class:`int`) anywhere that " +"a Decimal instance is accepted." +msgstr "" + +#: ../Doc/library/decimal.rst:1045 +msgid "Resets all of the flags to :const:`0`." +msgstr "" + +#: ../Doc/library/decimal.rst:1049 +msgid "Resets all of the traps to :const:`0`." +msgstr "" + +#: ../Doc/library/decimal.rst:1055 +msgid "Return a duplicate of the context." +msgstr "" + +#: ../Doc/library/decimal.rst:1059 +msgid "Return a copy of the Decimal instance num." +msgstr "" + +#: ../Doc/library/decimal.rst:1063 +msgid "" +"Creates a new Decimal instance from *num* but using *self* as context. " +"Unlike the :class:`Decimal` constructor, the context precision, rounding " +"method, flags, and traps are applied to the conversion." +msgstr "" + +#: ../Doc/library/decimal.rst:1067 +msgid "" +"This is useful because constants are often given to a greater precision than " +"is needed by the application. Another benefit is that rounding immediately " +"eliminates unintended effects from digits beyond the current precision. In " +"the following example, using unrounded inputs means that adding zero to a " +"sum can change the result:" +msgstr "" + +#: ../Doc/library/decimal.rst:1081 +msgid "" +"This method implements the to-number operation of the IBM specification. If " +"the argument is a string, no leading or trailing whitespace or underscores " +"are permitted." +msgstr "" + +#: ../Doc/library/decimal.rst:1087 +msgid "" +"Creates a new Decimal instance from a float *f* but rounding using *self* as " +"the context. Unlike the :meth:`Decimal.from_float` class method, the " +"context precision, rounding method, flags, and traps are applied to the " +"conversion." +msgstr "" + +#: ../Doc/library/decimal.rst:1107 +msgid "" +"Returns a value equal to ``Emin - prec + 1`` which is the minimum exponent " +"value for subnormal results. When underflow occurs, the exponent is set to :" +"const:`Etiny`." +msgstr "" + +#: ../Doc/library/decimal.rst:1113 +msgid "Returns a value equal to ``Emax - prec + 1``." +msgstr "" + +#: ../Doc/library/decimal.rst:1115 +msgid "" +"The usual approach to working with decimals is to create :class:`Decimal` " +"instances and then apply arithmetic operations which take place within the " +"current context for the active thread. An alternative approach is to use " +"context methods for calculating within a specific context. The methods are " +"similar to those for the :class:`Decimal` class and are only briefly " +"recounted here." +msgstr "" + +#: ../Doc/library/decimal.rst:1125 +msgid "Returns the absolute value of *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1130 +msgid "Return the sum of *x* and *y*." +msgstr "" + +#: ../Doc/library/decimal.rst:1135 +msgid "Returns the same Decimal object *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1140 +msgid "Compares *x* and *y* numerically." +msgstr "" + +#: ../Doc/library/decimal.rst:1145 +msgid "Compares the values of the two operands numerically." +msgstr "" + +#: ../Doc/library/decimal.rst:1150 +msgid "Compares two operands using their abstract representation." +msgstr "" + +#: ../Doc/library/decimal.rst:1155 +msgid "" +"Compares two operands using their abstract representation, ignoring sign." +msgstr "" + +#: ../Doc/library/decimal.rst:1160 +msgid "Returns a copy of *x* with the sign set to 0." +msgstr "" + +#: ../Doc/library/decimal.rst:1165 +msgid "Returns a copy of *x* with the sign inverted." +msgstr "" + +#: ../Doc/library/decimal.rst:1170 +msgid "Copies the sign from *y* to *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1175 +msgid "Return *x* divided by *y*." +msgstr "" + +#: ../Doc/library/decimal.rst:1180 +msgid "Return *x* divided by *y*, truncated to an integer." +msgstr "" + +#: ../Doc/library/decimal.rst:1185 +msgid "Divides two numbers and returns the integer part of the result." +msgstr "" + +#: ../Doc/library/decimal.rst:1190 +msgid "Returns `e ** x`." +msgstr "" + +#: ../Doc/library/decimal.rst:1195 +msgid "Returns *x* multiplied by *y*, plus *z*." +msgstr "" + +#: ../Doc/library/decimal.rst:1200 +msgid "Returns ``True`` if *x* is canonical; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1205 +msgid "Returns ``True`` if *x* is finite; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1210 +msgid "Returns ``True`` if *x* is infinite; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1215 +msgid "Returns ``True`` if *x* is a qNaN or sNaN; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1220 +msgid "" +"Returns ``True`` if *x* is a normal number; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1225 +msgid "Returns ``True`` if *x* is a quiet NaN; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1230 +msgid "Returns ``True`` if *x* is negative; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1235 +msgid "" +"Returns ``True`` if *x* is a signaling NaN; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1240 +msgid "Returns ``True`` if *x* is subnormal; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1245 +msgid "Returns ``True`` if *x* is a zero; otherwise returns ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1250 +msgid "Returns the natural (base e) logarithm of *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1255 +msgid "Returns the base 10 logarithm of *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1260 +msgid "Returns the exponent of the magnitude of the operand's MSD." +msgstr "" + +#: ../Doc/library/decimal.rst:1265 +msgid "Applies the logical operation *and* between each operand's digits." +msgstr "" + +#: ../Doc/library/decimal.rst:1270 +msgid "Invert all the digits in *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1275 +msgid "Applies the logical operation *or* between each operand's digits." +msgstr "" + +#: ../Doc/library/decimal.rst:1280 +msgid "Applies the logical operation *xor* between each operand's digits." +msgstr "" + +#: ../Doc/library/decimal.rst:1285 +msgid "Compares two values numerically and returns the maximum." +msgstr "" + +#: ../Doc/library/decimal.rst:1290 ../Doc/library/decimal.rst:1300 +msgid "Compares the values numerically with their sign ignored." +msgstr "" + +#: ../Doc/library/decimal.rst:1295 +msgid "Compares two values numerically and returns the minimum." +msgstr "" + +#: ../Doc/library/decimal.rst:1305 +msgid "Minus corresponds to the unary prefix minus operator in Python." +msgstr "" + +#: ../Doc/library/decimal.rst:1310 +msgid "Return the product of *x* and *y*." +msgstr "" + +#: ../Doc/library/decimal.rst:1315 +msgid "Returns the largest representable number smaller than *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1320 +msgid "Returns the smallest representable number larger than *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1325 +msgid "Returns the number closest to *x*, in direction towards *y*." +msgstr "" + +#: ../Doc/library/decimal.rst:1330 +msgid "Reduces *x* to its simplest form." +msgstr "" + +#: ../Doc/library/decimal.rst:1335 +msgid "Returns an indication of the class of *x*." +msgstr "" + +#: ../Doc/library/decimal.rst:1340 +msgid "" +"Plus corresponds to the unary prefix plus operator in Python. This " +"operation applies the context precision and rounding, so it is *not* an " +"identity operation." +msgstr "" + +#: ../Doc/library/decimal.rst:1347 +msgid "Return ``x`` to the power of ``y``, reduced modulo ``modulo`` if given." +msgstr "" + +#: ../Doc/library/decimal.rst:1349 +msgid "" +"With two arguments, compute ``x**y``. If ``x`` is negative then ``y`` must " +"be integral. The result will be inexact unless ``y`` is integral and the " +"result is finite and can be expressed exactly in 'precision' digits. The " +"rounding mode of the context is used. Results are always correctly-rounded " +"in the Python version." +msgstr "" + +#: ../Doc/library/decimal.rst:1355 +msgid "" +"The C module computes :meth:`power` in terms of the correctly-rounded :meth:" +"`exp` and :meth:`ln` functions. The result is well-defined but only \"almost " +"always correctly-rounded\"." +msgstr "" + +#: ../Doc/library/decimal.rst:1360 +msgid "" +"With three arguments, compute ``(x**y) % modulo``. For the three argument " +"form, the following restrictions on the arguments hold:" +msgstr "" + +#: ../Doc/library/decimal.rst:1363 +msgid "all three arguments must be integral" +msgstr "" + +#: ../Doc/library/decimal.rst:1364 +msgid "``y`` must be nonnegative" +msgstr "" + +#: ../Doc/library/decimal.rst:1365 +msgid "at least one of ``x`` or ``y`` must be nonzero" +msgstr "" + +#: ../Doc/library/decimal.rst:1366 +msgid "``modulo`` must be nonzero and have at most 'precision' digits" +msgstr "" + +#: ../Doc/library/decimal.rst:1368 +msgid "" +"The value resulting from ``Context.power(x, y, modulo)`` is equal to the " +"value that would be obtained by computing ``(x**y) % modulo`` with unbounded " +"precision, but is computed more efficiently. The exponent of the result is " +"zero, regardless of the exponents of ``x``, ``y`` and ``modulo``. The " +"result is always exact." +msgstr "" + +#: ../Doc/library/decimal.rst:1378 +msgid "Returns a value equal to *x* (rounded), having the exponent of *y*." +msgstr "" + +#: ../Doc/library/decimal.rst:1383 +msgid "Just returns 10, as this is Decimal, :)" +msgstr "" + +#: ../Doc/library/decimal.rst:1388 +msgid "Returns the remainder from integer division." +msgstr "" + +#: ../Doc/library/decimal.rst:1390 +msgid "" +"The sign of the result, if non-zero, is the same as that of the original " +"dividend." +msgstr "" + +#: ../Doc/library/decimal.rst:1396 +msgid "" +"Returns ``x - y * n``, where *n* is the integer nearest the exact value of " +"``x / y`` (if the result is 0 then its sign will be the sign of *x*)." +msgstr "" + +#: ../Doc/library/decimal.rst:1402 +msgid "Returns a rotated copy of *x*, *y* times." +msgstr "" + +#: ../Doc/library/decimal.rst:1407 +msgid "Returns ``True`` if the two operands have the same exponent." +msgstr "" + +#: ../Doc/library/decimal.rst:1412 +msgid "Returns the first operand after adding the second value its exp." +msgstr "" + +#: ../Doc/library/decimal.rst:1417 +msgid "Returns a shifted copy of *x*, *y* times." +msgstr "" + +#: ../Doc/library/decimal.rst:1422 +msgid "Square root of a non-negative number to context precision." +msgstr "" + +#: ../Doc/library/decimal.rst:1427 +msgid "Return the difference between *x* and *y*." +msgstr "" + +#: ../Doc/library/decimal.rst:1441 +msgid "Rounds to an integer." +msgstr "" + +#: ../Doc/library/decimal.rst:1446 +msgid "Converts a number to a string using scientific notation." +msgstr "" + +#: ../Doc/library/decimal.rst:1455 +msgid "" +"The constants in this section are only relevant for the C module. They are " +"also included in the pure Python version for compatibility." +msgstr "" + +#: ../Doc/library/decimal.rst:1459 +msgid "32-bit" +msgstr "" + +#: ../Doc/library/decimal.rst:1459 +msgid "64-bit" +msgstr "" + +#: ../Doc/library/decimal.rst:1461 ../Doc/library/decimal.rst:1463 +msgid ":const:`425000000`" +msgstr "" + +#: ../Doc/library/decimal.rst:1461 ../Doc/library/decimal.rst:1463 +msgid ":const:`999999999999999999`" +msgstr "" + +#: ../Doc/library/decimal.rst:1465 +msgid ":const:`-425000000`" +msgstr "" + +#: ../Doc/library/decimal.rst:1465 +msgid ":const:`-999999999999999999`" +msgstr "" + +#: ../Doc/library/decimal.rst:1467 +msgid ":const:`-849999999`" +msgstr "" + +#: ../Doc/library/decimal.rst:1467 +msgid ":const:`-1999999999999999997`" +msgstr "" + +#: ../Doc/library/decimal.rst:1473 +msgid "" +"The default value is ``True``. If Python is compiled without threads, the C " +"version automatically disables the expensive thread local context machinery. " +"In this case, the value is ``False``." +msgstr "" + +#: ../Doc/library/decimal.rst:1478 +msgid "Rounding modes" +msgstr "" + +#: ../Doc/library/decimal.rst:1482 +msgid "Round towards :const:`Infinity`." +msgstr "" + +#: ../Doc/library/decimal.rst:1486 +msgid "Round towards zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1490 +msgid "Round towards :const:`-Infinity`." +msgstr "" + +#: ../Doc/library/decimal.rst:1494 +msgid "Round to nearest with ties going towards zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1498 +msgid "Round to nearest with ties going to nearest even integer." +msgstr "" + +#: ../Doc/library/decimal.rst:1502 +msgid "Round to nearest with ties going away from zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1506 +msgid "Round away from zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1510 +msgid "" +"Round away from zero if last digit after rounding towards zero would have " +"been 0 or 5; otherwise round towards zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1517 +msgid "Signals" +msgstr "" + +#: ../Doc/library/decimal.rst:1519 +msgid "" +"Signals represent conditions that arise during computation. Each corresponds " +"to one context flag and one context trap enabler." +msgstr "" + +#: ../Doc/library/decimal.rst:1522 +msgid "" +"The context flag is set whenever the condition is encountered. After the " +"computation, flags may be checked for informational purposes (for instance, " +"to determine whether a computation was exact). After checking the flags, be " +"sure to clear all flags before starting the next computation." +msgstr "" + +#: ../Doc/library/decimal.rst:1527 +msgid "" +"If the context's trap enabler is set for the signal, then the condition " +"causes a Python exception to be raised. For example, if the :class:" +"`DivisionByZero` trap is set, then a :exc:`DivisionByZero` exception is " +"raised upon encountering the condition." +msgstr "" + +#: ../Doc/library/decimal.rst:1535 +msgid "Altered an exponent to fit representation constraints." +msgstr "" + +#: ../Doc/library/decimal.rst:1537 +msgid "" +"Typically, clamping occurs when an exponent falls outside the context's :" +"attr:`Emin` and :attr:`Emax` limits. If possible, the exponent is reduced " +"to fit by adding zeros to the coefficient." +msgstr "" + +#: ../Doc/library/decimal.rst:1544 +msgid "Base class for other signals and a subclass of :exc:`ArithmeticError`." +msgstr "" + +#: ../Doc/library/decimal.rst:1549 +msgid "Signals the division of a non-infinite number by zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1551 +msgid "" +"Can occur with division, modulo division, or when raising a number to a " +"negative power. If this signal is not trapped, returns :const:`Infinity` " +"or :const:`-Infinity` with the sign determined by the inputs to the " +"calculation." +msgstr "" + +#: ../Doc/library/decimal.rst:1558 +msgid "Indicates that rounding occurred and the result is not exact." +msgstr "" + +#: ../Doc/library/decimal.rst:1560 +msgid "" +"Signals when non-zero digits were discarded during rounding. The rounded " +"result is returned. The signal flag or trap is used to detect when results " +"are inexact." +msgstr "" + +#: ../Doc/library/decimal.rst:1567 +msgid "An invalid operation was performed." +msgstr "" + +#: ../Doc/library/decimal.rst:1569 +msgid "" +"Indicates that an operation was requested that does not make sense. If not " +"trapped, returns :const:`NaN`. Possible causes include::" +msgstr "" + +#: ../Doc/library/decimal.rst:1585 +msgid "Numerical overflow." +msgstr "" + +#: ../Doc/library/decimal.rst:1587 +msgid "" +"Indicates the exponent is larger than :attr:`Emax` after rounding has " +"occurred. If not trapped, the result depends on the rounding mode, either " +"pulling inward to the largest representable finite number or rounding " +"outward to :const:`Infinity`. In either case, :class:`Inexact` and :class:" +"`Rounded` are also signaled." +msgstr "" + +#: ../Doc/library/decimal.rst:1596 +msgid "Rounding occurred though possibly no information was lost." +msgstr "" + +#: ../Doc/library/decimal.rst:1598 +msgid "" +"Signaled whenever rounding discards digits; even if those digits are zero " +"(such as rounding :const:`5.00` to :const:`5.0`). If not trapped, returns " +"the result unchanged. This signal is used to detect loss of significant " +"digits." +msgstr "" + +#: ../Doc/library/decimal.rst:1606 +msgid "Exponent was lower than :attr:`Emin` prior to rounding." +msgstr "" + +#: ../Doc/library/decimal.rst:1608 +msgid "" +"Occurs when an operation result is subnormal (the exponent is too small). If " +"not trapped, returns the result unchanged." +msgstr "" + +#: ../Doc/library/decimal.rst:1614 +msgid "Numerical underflow with result rounded to zero." +msgstr "" + +#: ../Doc/library/decimal.rst:1616 +msgid "" +"Occurs when a subnormal result is pushed to zero by rounding. :class:" +"`Inexact` and :class:`Subnormal` are also signaled." +msgstr "" + +#: ../Doc/library/decimal.rst:1622 +msgid "Enable stricter semantics for mixing floats and Decimals." +msgstr "" + +#: ../Doc/library/decimal.rst:1624 +msgid "" +"If the signal is not trapped (default), mixing floats and Decimals is " +"permitted in the :class:`~decimal.Decimal` constructor, :meth:`~decimal." +"Context.create_decimal` and all comparison operators. Both conversion and " +"comparisons are exact. Any occurrence of a mixed operation is silently " +"recorded by setting :exc:`FloatOperation` in the context flags. Explicit " +"conversions with :meth:`~decimal.Decimal.from_float` or :meth:`~decimal." +"Context.create_decimal_from_float` do not set the flag." +msgstr "" + +#: ../Doc/library/decimal.rst:1632 +msgid "" +"Otherwise (the signal is trapped), only equality comparisons and explicit " +"conversions are silent. All other mixed operations raise :exc:" +"`FloatOperation`." +msgstr "" + +#: ../Doc/library/decimal.rst:1636 +msgid "The following table summarizes the hierarchy of signals::" +msgstr "" + +#: ../Doc/library/decimal.rst:1657 +msgid "Floating Point Notes" +msgstr "" + +#: ../Doc/library/decimal.rst:1661 +msgid "Mitigating round-off error with increased precision" +msgstr "" + +#: ../Doc/library/decimal.rst:1663 +msgid "" +"The use of decimal floating point eliminates decimal representation error " +"(making it possible to represent :const:`0.1` exactly); however, some " +"operations can still incur round-off error when non-zero digits exceed the " +"fixed precision." +msgstr "" + +#: ../Doc/library/decimal.rst:1667 +msgid "" +"The effects of round-off error can be amplified by the addition or " +"subtraction of nearly offsetting quantities resulting in loss of " +"significance. Knuth provides two instructive examples where rounded " +"floating point arithmetic with insufficient precision causes the breakdown " +"of the associative and distributive properties of addition:" +msgstr "" + +#: ../Doc/library/decimal.rst:1691 +msgid "" +"The :mod:`decimal` module makes it possible to restore the identities by " +"expanding the precision sufficiently to avoid loss of significance:" +msgstr "" + +#: ../Doc/library/decimal.rst:1711 +msgid "Special values" +msgstr "" + +#: ../Doc/library/decimal.rst:1713 +msgid "" +"The number system for the :mod:`decimal` module provides special values " +"including :const:`NaN`, :const:`sNaN`, :const:`-Infinity`, :const:" +"`Infinity`, and two zeros, :const:`+0` and :const:`-0`." +msgstr "" + +#: ../Doc/library/decimal.rst:1717 +msgid "" +"Infinities can be constructed directly with: ``Decimal('Infinity')``. Also, " +"they can arise from dividing by zero when the :exc:`DivisionByZero` signal " +"is not trapped. Likewise, when the :exc:`Overflow` signal is not trapped, " +"infinity can result from rounding beyond the limits of the largest " +"representable number." +msgstr "" + +#: ../Doc/library/decimal.rst:1722 +msgid "" +"The infinities are signed (affine) and can be used in arithmetic operations " +"where they get treated as very large, indeterminate numbers. For instance, " +"adding a constant to infinity gives another infinite result." +msgstr "" + +#: ../Doc/library/decimal.rst:1726 +msgid "" +"Some operations are indeterminate and return :const:`NaN`, or if the :exc:" +"`InvalidOperation` signal is trapped, raise an exception. For example, " +"``0/0`` returns :const:`NaN` which means \"not a number\". This variety of :" +"const:`NaN` is quiet and, once created, will flow through other computations " +"always resulting in another :const:`NaN`. This behavior can be useful for a " +"series of computations that occasionally have missing inputs --- it allows " +"the calculation to proceed while flagging specific results as invalid." +msgstr "" + +#: ../Doc/library/decimal.rst:1734 +msgid "" +"A variant is :const:`sNaN` which signals rather than remaining quiet after " +"every operation. This is a useful return value when an invalid result needs " +"to interrupt a calculation for special handling." +msgstr "" + +#: ../Doc/library/decimal.rst:1738 +msgid "" +"The behavior of Python's comparison operators can be a little surprising " +"where a :const:`NaN` is involved. A test for equality where one of the " +"operands is a quiet or signaling :const:`NaN` always returns :const:`False` " +"(even when doing ``Decimal('NaN')==Decimal('NaN')``), while a test for " +"inequality always returns :const:`True`. An attempt to compare two Decimals " +"using any of the ``<``, ``<=``, ``>`` or ``>=`` operators will raise the :" +"exc:`InvalidOperation` signal if either operand is a :const:`NaN`, and " +"return :const:`False` if this signal is not trapped. Note that the General " +"Decimal Arithmetic specification does not specify the behavior of direct " +"comparisons; these rules for comparisons involving a :const:`NaN` were taken " +"from the IEEE 854 standard (see Table 3 in section 5.7). To ensure strict " +"standards-compliance, use the :meth:`compare` and :meth:`compare-signal` " +"methods instead." +msgstr "" + +#: ../Doc/library/decimal.rst:1751 +msgid "" +"The signed zeros can result from calculations that underflow. They keep the " +"sign that would have resulted if the calculation had been carried out to " +"greater precision. Since their magnitude is zero, both positive and " +"negative zeros are treated as equal and their sign is informational." +msgstr "" + +#: ../Doc/library/decimal.rst:1756 +msgid "" +"In addition to the two signed zeros which are distinct yet equal, there are " +"various representations of zero with differing precisions yet equivalent in " +"value. This takes a bit of getting used to. For an eye accustomed to " +"normalized floating point representations, it is not immediately obvious " +"that the following calculation returns a value equal to zero:" +msgstr "" + +#: ../Doc/library/decimal.rst:1771 +msgid "Working with threads" +msgstr "" + +#: ../Doc/library/decimal.rst:1773 +msgid "" +"The :func:`getcontext` function accesses a different :class:`Context` object " +"for each thread. Having separate thread contexts means that threads may " +"make changes (such as ``getcontext().prec=10``) without interfering with " +"other threads." +msgstr "" + +#: ../Doc/library/decimal.rst:1777 +msgid "" +"Likewise, the :func:`setcontext` function automatically assigns its target " +"to the current thread." +msgstr "" + +#: ../Doc/library/decimal.rst:1780 +msgid "" +"If :func:`setcontext` has not been called before :func:`getcontext`, then :" +"func:`getcontext` will automatically create a new context for use in the " +"current thread." +msgstr "" + +#: ../Doc/library/decimal.rst:1784 +msgid "" +"The new context is copied from a prototype context called *DefaultContext*. " +"To control the defaults so that each thread will use the same values " +"throughout the application, directly modify the *DefaultContext* object. " +"This should be done *before* any threads are started so that there won't be " +"a race condition between threads calling :func:`getcontext`. For example::" +msgstr "" + +#: ../Doc/library/decimal.rst:1809 +msgid "Recipes" +msgstr "" + +#: ../Doc/library/decimal.rst:1811 +msgid "" +"Here are a few recipes that serve as utility functions and that demonstrate " +"ways to work with the :class:`Decimal` class::" +msgstr "" + +#: ../Doc/library/decimal.rst:1966 +msgid "Decimal FAQ" +msgstr "" + +#: ../Doc/library/decimal.rst:1968 +msgid "" +"Q. It is cumbersome to type ``decimal.Decimal('1234.5')``. Is there a way " +"to minimize typing when using the interactive interpreter?" +msgstr "" + +#: ../Doc/library/decimal.rst:1971 +msgid "A. Some users abbreviate the constructor to just a single letter:" +msgstr "" + +#: ../Doc/library/decimal.rst:1977 +msgid "" +"Q. In a fixed-point application with two decimal places, some inputs have " +"many places and need to be rounded. Others are not supposed to have excess " +"digits and need to be validated. What methods should be used?" +msgstr "" + +#: ../Doc/library/decimal.rst:1981 +msgid "" +"A. The :meth:`quantize` method rounds to a fixed number of decimal places. " +"If the :const:`Inexact` trap is set, it is also useful for validation:" +msgstr "" + +#: ../Doc/library/decimal.rst:1999 +msgid "" +"Q. Once I have valid two place inputs, how do I maintain that invariant " +"throughout an application?" +msgstr "" + +#: ../Doc/library/decimal.rst:2002 +msgid "" +"A. Some operations like addition, subtraction, and multiplication by an " +"integer will automatically preserve fixed point. Others operations, like " +"division and non-integer multiplication, will change the number of decimal " +"places and need to be followed-up with a :meth:`quantize` step:" +msgstr "" + +#: ../Doc/library/decimal.rst:2020 +msgid "" +"In developing fixed-point applications, it is convenient to define functions " +"to handle the :meth:`quantize` step:" +msgstr "" + +#: ../Doc/library/decimal.rst:2033 +msgid "" +"Q. There are many ways to express the same value. The numbers :const:" +"`200`, :const:`200.000`, :const:`2E2`, and :const:`.02E+4` all have the same " +"value at various precisions. Is there a way to transform them to a single " +"recognizable canonical value?" +msgstr "" + +#: ../Doc/library/decimal.rst:2038 +msgid "" +"A. The :meth:`normalize` method maps all equivalent values to a single " +"representative:" +msgstr "" + +#: ../Doc/library/decimal.rst:2045 +msgid "" +"Q. Some decimal values always print with exponential notation. Is there a " +"way to get a non-exponential representation?" +msgstr "" + +#: ../Doc/library/decimal.rst:2048 +msgid "" +"A. For some values, exponential notation is the only way to express the " +"number of significant places in the coefficient. For example, expressing :" +"const:`5.0E+3` as :const:`5000` keeps the value constant but cannot show the " +"original's two-place significance." +msgstr "" + +#: ../Doc/library/decimal.rst:2053 +msgid "" +"If an application does not care about tracking significance, it is easy to " +"remove the exponent and trailing zeroes, losing significance, but keeping " +"the value unchanged:" +msgstr "" + +#: ../Doc/library/decimal.rst:2063 +msgid "Q. Is there a way to convert a regular float to a :class:`Decimal`?" +msgstr "" + +#: ../Doc/library/decimal.rst:2065 +msgid "" +"A. Yes, any binary floating point number can be exactly expressed as a " +"Decimal though an exact conversion may take more precision than intuition " +"would suggest:" +msgstr "" + +#: ../Doc/library/decimal.rst:2074 +msgid "" +"Q. Within a complex calculation, how can I make sure that I haven't gotten a " +"spurious result because of insufficient precision or rounding anomalies." +msgstr "" + +#: ../Doc/library/decimal.rst:2077 +msgid "" +"A. The decimal module makes it easy to test results. A best practice is to " +"re-run calculations using greater precision and with various rounding modes. " +"Widely differing results indicate insufficient precision, rounding mode " +"issues, ill-conditioned inputs, or a numerically unstable algorithm." +msgstr "" + +#: ../Doc/library/decimal.rst:2082 +msgid "" +"Q. I noticed that context precision is applied to the results of operations " +"but not to the inputs. Is there anything to watch out for when mixing " +"values of different precisions?" +msgstr "" + +#: ../Doc/library/decimal.rst:2086 +msgid "" +"A. Yes. The principle is that all values are considered to be exact and so " +"is the arithmetic on those values. Only the results are rounded. The " +"advantage for inputs is that \"what you type is what you get\". A " +"disadvantage is that the results can look odd if you forget that the inputs " +"haven't been rounded:" +msgstr "" + +#: ../Doc/library/decimal.rst:2099 +msgid "" +"The solution is either to increase precision or to force rounding of inputs " +"using the unary plus operation:" +msgstr "" + +#: ../Doc/library/decimal.rst:2108 +msgid "" +"Alternatively, inputs can be rounded upon creation using the :meth:`Context." +"create_decimal` method:" +msgstr "" + +#: ../Doc/library/development.rst:5 +msgid "Development Tools" +msgstr "" + +#: ../Doc/library/development.rst:7 +msgid "" +"The modules described in this chapter help you write software. For example, " +"the :mod:`pydoc` module takes a module and generates documentation based on " +"the module's contents. The :mod:`doctest` and :mod:`unittest` modules " +"contains frameworks for writing unit tests that automatically exercise code " +"and verify that the expected output is produced. :program:`2to3` can " +"translate Python 2.x source code into valid Python 3.x code." +msgstr "" + +#: ../Doc/library/development.rst:14 ../Doc/library/i18n.rst:12 +#: ../Doc/library/ipc.rst:14 ../Doc/library/persistence.rst:13 +msgid "The list of modules described in this chapter is:" +msgstr "" + +#: ../Doc/library/difflib.rst:2 +msgid ":mod:`difflib` --- Helpers for computing deltas" +msgstr "" + +#: ../Doc/library/difflib.rst:11 +msgid "**Source code:** :source:`Lib/difflib.py`" +msgstr "" + +#: ../Doc/library/difflib.rst:20 +msgid "" +"This module provides classes and functions for comparing sequences. It can " +"be used for example, for comparing files, and can produce difference " +"information in various formats, including HTML and context and unified " +"diffs. For comparing directories and files, see also, the :mod:`filecmp` " +"module." +msgstr "" + +#: ../Doc/library/difflib.rst:28 +msgid "" +"This is a flexible class for comparing pairs of sequences of any type, so " +"long as the sequence elements are :term:`hashable`. The basic algorithm " +"predates, and is a little fancier than, an algorithm published in the late " +"1980's by Ratcliff and Obershelp under the hyperbolic name \"gestalt pattern " +"matching.\" The idea is to find the longest contiguous matching subsequence " +"that contains no \"junk\" elements; these \"junk\" elements are ones that " +"are uninteresting in some sense, such as blank lines or whitespace. " +"(Handling junk is an extension to the Ratcliff and Obershelp algorithm.) The " +"same idea is then applied recursively to the pieces of the sequences to the " +"left and to the right of the matching subsequence. This does not yield " +"minimal edit sequences, but does tend to yield matches that \"look right\" " +"to people." +msgstr "" + +#: ../Doc/library/difflib.rst:40 +msgid "" +"**Timing:** The basic Ratcliff-Obershelp algorithm is cubic time in the " +"worst case and quadratic time in the expected case. :class:`SequenceMatcher` " +"is quadratic time for the worst case and has expected-case behavior " +"dependent in a complicated way on how many elements the sequences have in " +"common; best case time is linear." +msgstr "" + +#: ../Doc/library/difflib.rst:46 +msgid "" +"**Automatic junk heuristic:** :class:`SequenceMatcher` supports a heuristic " +"that automatically treats certain sequence items as junk. The heuristic " +"counts how many times each individual item appears in the sequence. If an " +"item's duplicates (after the first one) account for more than 1% of the " +"sequence and the sequence is at least 200 items long, this item is marked as " +"\"popular\" and is treated as junk for the purpose of sequence matching. " +"This heuristic can be turned off by setting the ``autojunk`` argument to " +"``False`` when creating the :class:`SequenceMatcher`." +msgstr "" + +#: ../Doc/library/difflib.rst:54 ../Doc/library/difflib.rst:383 +msgid "The *autojunk* parameter." +msgstr "" + +#: ../Doc/library/difflib.rst:60 +msgid "" +"This is a class for comparing sequences of lines of text, and producing " +"human-readable differences or deltas. Differ uses :class:`SequenceMatcher` " +"both to compare sequences of lines, and to compare sequences of characters " +"within similar (near-matching) lines." +msgstr "" + +#: ../Doc/library/difflib.rst:65 +msgid "Each line of a :class:`Differ` delta begins with a two-letter code:" +msgstr "" + +#: ../Doc/library/difflib.rst:68 ../Doc/library/http.rst:60 +msgid "Code" +msgstr "" + +#: ../Doc/library/difflib.rst:70 +msgid "``'- '``" +msgstr "" + +#: ../Doc/library/difflib.rst:70 +msgid "line unique to sequence 1" +msgstr "" + +#: ../Doc/library/difflib.rst:72 +msgid "``'+ '``" +msgstr "" + +#: ../Doc/library/difflib.rst:72 +msgid "line unique to sequence 2" +msgstr "" + +#: ../Doc/library/difflib.rst:74 +msgid "``' '``" +msgstr "" + +#: ../Doc/library/difflib.rst:74 +msgid "line common to both sequences" +msgstr "" + +#: ../Doc/library/difflib.rst:76 +msgid "``'? '``" +msgstr "" + +#: ../Doc/library/difflib.rst:76 +msgid "line not present in either input sequence" +msgstr "" + +#: ../Doc/library/difflib.rst:79 +msgid "" +"Lines beginning with '``?``' attempt to guide the eye to intraline " +"differences, and were not present in either input sequence. These lines can " +"be confusing if the sequences contain tab characters." +msgstr "" + +#: ../Doc/library/difflib.rst:86 +msgid "" +"This class can be used to create an HTML table (or a complete HTML file " +"containing the table) showing a side by side, line by line comparison of " +"text with inter-line and intra-line change highlights. The table can be " +"generated in either full or contextual difference mode." +msgstr "" + +#: ../Doc/library/difflib.rst:91 +msgid "The constructor for this class is:" +msgstr "" + +#: ../Doc/library/difflib.rst:96 +msgid "Initializes instance of :class:`HtmlDiff`." +msgstr "" + +#: ../Doc/library/difflib.rst:98 +msgid "" +"*tabsize* is an optional keyword argument to specify tab stop spacing and " +"defaults to ``8``." +msgstr "" + +#: ../Doc/library/difflib.rst:101 +msgid "" +"*wrapcolumn* is an optional keyword to specify column number where lines are " +"broken and wrapped, defaults to ``None`` where lines are not wrapped." +msgstr "" + +#: ../Doc/library/difflib.rst:104 +msgid "" +"*linejunk* and *charjunk* are optional keyword arguments passed into :func:" +"`ndiff` (used by :class:`HtmlDiff` to generate the side by side HTML " +"differences). See :func:`ndiff` documentation for argument default values " +"and descriptions." +msgstr "" + +#: ../Doc/library/difflib.rst:108 +msgid "The following methods are public:" +msgstr "" + +#: ../Doc/library/difflib.rst:113 +msgid "" +"Compares *fromlines* and *tolines* (lists of strings) and returns a string " +"which is a complete HTML file containing a table showing line by line " +"differences with inter-line and intra-line changes highlighted." +msgstr "" + +#: ../Doc/library/difflib.rst:117 +msgid "" +"*fromdesc* and *todesc* are optional keyword arguments to specify from/to " +"file column header strings (both default to an empty string)." +msgstr "" + +#: ../Doc/library/difflib.rst:120 +msgid "" +"*context* and *numlines* are both optional keyword arguments. Set *context* " +"to ``True`` when contextual differences are to be shown, else the default is " +"``False`` to show the full files. *numlines* defaults to ``5``. When " +"*context* is ``True`` *numlines* controls the number of context lines which " +"surround the difference highlights. When *context* is ``False`` *numlines* " +"controls the number of lines which are shown before a difference highlight " +"when using the \"next\" hyperlinks (setting to zero would cause the \"next\" " +"hyperlinks to place the next difference highlight at the top of the browser " +"without any leading context)." +msgstr "" + +#: ../Doc/library/difflib.rst:130 +msgid "" +"*charset* keyword-only argument was added. The default charset of HTML " +"document changed from ``'ISO-8859-1'`` to ``'utf-8'``." +msgstr "" + +#: ../Doc/library/difflib.rst:136 +msgid "" +"Compares *fromlines* and *tolines* (lists of strings) and returns a string " +"which is a complete HTML table showing line by line differences with inter-" +"line and intra-line changes highlighted." +msgstr "" + +#: ../Doc/library/difflib.rst:140 +msgid "" +"The arguments for this method are the same as those for the :meth:" +"`make_file` method." +msgstr "" + +#: ../Doc/library/difflib.rst:143 +msgid "" +":file:`Tools/scripts/diff.py` is a command-line front-end to this class and " +"contains a good example of its use." +msgstr "" + +#: ../Doc/library/difflib.rst:149 +msgid "" +"Compare *a* and *b* (lists of strings); return a delta (a :term:`generator` " +"generating the delta lines) in context diff format." +msgstr "" + +#: ../Doc/library/difflib.rst:152 +msgid "" +"Context diffs are a compact way of showing just the lines that have changed " +"plus a few lines of context. The changes are shown in a before/after " +"style. The number of context lines is set by *n* which defaults to three." +msgstr "" + +#: ../Doc/library/difflib.rst:156 +msgid "" +"By default, the diff control lines (those with ``***`` or ``---``) are " +"created with a trailing newline. This is helpful so that inputs created " +"from :func:`io.IOBase.readlines` result in diffs that are suitable for use " +"with :func:`io.IOBase.writelines` since both the inputs and outputs have " +"trailing newlines." +msgstr "" + +#: ../Doc/library/difflib.rst:162 ../Doc/library/difflib.rst:293 +msgid "" +"For inputs that do not have trailing newlines, set the *lineterm* argument " +"to ``\"\"`` so that the output will be uniformly newline free." +msgstr "" + +#: ../Doc/library/difflib.rst:165 ../Doc/library/difflib.rst:296 +msgid "" +"The context diff format normally has a header for filenames and modification " +"times. Any or all of these may be specified using strings for *fromfile*, " +"*tofile*, *fromfiledate*, and *tofiledate*. The modification times are " +"normally expressed in the ISO 8601 format. If not specified, the strings " +"default to blanks." +msgstr "" + +#: ../Doc/library/difflib.rst:188 ../Doc/library/difflib.rst:317 +msgid "See :ref:`difflib-interface` for a more detailed example." +msgstr "" + +#: ../Doc/library/difflib.rst:193 +msgid "" +"Return a list of the best \"good enough\" matches. *word* is a sequence for " +"which close matches are desired (typically a string), and *possibilities* is " +"a list of sequences against which to match *word* (typically a list of " +"strings)." +msgstr "" + +#: ../Doc/library/difflib.rst:197 +msgid "" +"Optional argument *n* (default ``3``) is the maximum number of close matches " +"to return; *n* must be greater than ``0``." +msgstr "" + +#: ../Doc/library/difflib.rst:200 +msgid "" +"Optional argument *cutoff* (default ``0.6``) is a float in the range [0, 1]. " +"Possibilities that don't score at least that similar to *word* are ignored." +msgstr "" + +#: ../Doc/library/difflib.rst:203 +msgid "" +"The best (no more than *n*) matches among the possibilities are returned in " +"a list, sorted by similarity score, most similar first." +msgstr "" + +#: ../Doc/library/difflib.rst:219 +msgid "" +"Compare *a* and *b* (lists of strings); return a :class:`Differ`\\ -style " +"delta (a :term:`generator` generating the delta lines)." +msgstr "" + +#: ../Doc/library/difflib.rst:222 +msgid "" +"Optional keyword parameters *linejunk* and *charjunk* are filtering " +"functions (or ``None``):" +msgstr "" + +#: ../Doc/library/difflib.rst:225 +msgid "" +"*linejunk*: A function that accepts a single string argument, and returns " +"true if the string is junk, or false if not. The default is ``None``. There " +"is also a module-level function :func:`IS_LINE_JUNK`, which filters out " +"lines without visible characters, except for at most one pound character " +"(``'#'``) -- however the underlying :class:`SequenceMatcher` class does a " +"dynamic analysis of which lines are so frequent as to constitute noise, and " +"this usually works better than using this function." +msgstr "" + +#: ../Doc/library/difflib.rst:233 +msgid "" +"*charjunk*: A function that accepts a character (a string of length 1), and " +"returns if the character is junk, or false if not. The default is module-" +"level function :func:`IS_CHARACTER_JUNK`, which filters out whitespace " +"characters (a blank or tab; it's a bad idea to include newline in this!)." +msgstr "" + +#: ../Doc/library/difflib.rst:238 +msgid "" +":file:`Tools/scripts/ndiff.py` is a command-line front-end to this function." +msgstr "" + +#: ../Doc/library/difflib.rst:256 +msgid "Return one of the two sequences that generated a delta." +msgstr "" + +#: ../Doc/library/difflib.rst:258 +msgid "" +"Given a *sequence* produced by :meth:`Differ.compare` or :func:`ndiff`, " +"extract lines originating from file 1 or 2 (parameter *which*), stripping " +"off line prefixes." +msgstr "" + +#: ../Doc/library/difflib.rst:279 +msgid "" +"Compare *a* and *b* (lists of strings); return a delta (a :term:`generator` " +"generating the delta lines) in unified diff format." +msgstr "" + +#: ../Doc/library/difflib.rst:282 +msgid "" +"Unified diffs are a compact way of showing just the lines that have changed " +"plus a few lines of context. The changes are shown in an inline style " +"(instead of separate before/after blocks). The number of context lines is " +"set by *n* which defaults to three." +msgstr "" + +#: ../Doc/library/difflib.rst:287 +msgid "" +"By default, the diff control lines (those with ``---``, ``+++``, or ``@@``) " +"are created with a trailing newline. This is helpful so that inputs created " +"from :func:`io.IOBase.readlines` result in diffs that are suitable for use " +"with :func:`io.IOBase.writelines` since both the inputs and outputs have " +"trailing newlines." +msgstr "" + +#: ../Doc/library/difflib.rst:321 +msgid "" +"Compare *a* and *b* (lists of bytes objects) using *dfunc*; yield a sequence " +"of delta lines (also bytes) in the format returned by *dfunc*. *dfunc* must " +"be a callable, typically either :func:`unified_diff` or :func:`context_diff`." +msgstr "" + +#: ../Doc/library/difflib.rst:326 +msgid "" +"Allows you to compare data with unknown or inconsistent encoding. All inputs " +"except *n* must be bytes objects, not str. Works by losslessly converting " +"all inputs (except *n*) to str, and calling ``dfunc(a, b, fromfile, tofile, " +"fromfiledate, tofiledate, n, lineterm)``. The output of *dfunc* is then " +"converted back to bytes, so the delta lines that you receive have the same " +"unknown/inconsistent encodings as *a* and *b*." +msgstr "" + +#: ../Doc/library/difflib.rst:337 +msgid "" +"Return true for ignorable lines. The line *line* is ignorable if *line* is " +"blank or contains a single ``'#'``, otherwise it is not ignorable. Used as " +"a default for parameter *linejunk* in :func:`ndiff` in older versions." +msgstr "" + +#: ../Doc/library/difflib.rst:344 +msgid "" +"Return true for ignorable characters. The character *ch* is ignorable if " +"*ch* is a space or tab, otherwise it is not ignorable. Used as a default " +"for parameter *charjunk* in :func:`ndiff`." +msgstr "" + +#: ../Doc/library/difflib.rst:352 +msgid "" +"`Pattern Matching: The Gestalt Approach `_" +msgstr "" + +#: ../Doc/library/difflib.rst:352 +msgid "" +"Discussion of a similar algorithm by John W. Ratcliff and D. E. Metzener. " +"This was published in `Dr. Dobb's Journal `_ in " +"July, 1988." +msgstr "" + +#: ../Doc/library/difflib.rst:359 +msgid "SequenceMatcher Objects" +msgstr "" + +#: ../Doc/library/difflib.rst:361 +msgid "The :class:`SequenceMatcher` class has this constructor:" +msgstr "" + +#: ../Doc/library/difflib.rst:366 +msgid "" +"Optional argument *isjunk* must be ``None`` (the default) or a one-argument " +"function that takes a sequence element and returns true if and only if the " +"element is \"junk\" and should be ignored. Passing ``None`` for *isjunk* is " +"equivalent to passing ``lambda x: 0``; in other words, no elements are " +"ignored. For example, pass::" +msgstr "" + +#: ../Doc/library/difflib.rst:374 +msgid "" +"if you're comparing lines as sequences of characters, and don't want to " +"synch up on blanks or hard tabs." +msgstr "" + +#: ../Doc/library/difflib.rst:377 +msgid "" +"The optional arguments *a* and *b* are sequences to be compared; both " +"default to empty strings. The elements of both sequences must be :term:" +"`hashable`." +msgstr "" + +#: ../Doc/library/difflib.rst:380 +msgid "" +"The optional argument *autojunk* can be used to disable the automatic junk " +"heuristic." +msgstr "" + +#: ../Doc/library/difflib.rst:386 +msgid "" +"SequenceMatcher objects get three data attributes: *bjunk* is the set of " +"elements of *b* for which *isjunk* is ``True``; *bpopular* is the set of non-" +"junk elements considered popular by the heuristic (if it is not disabled); " +"*b2j* is a dict mapping the remaining elements of *b* to a list of positions " +"where they occur. All three are reset whenever *b* is reset with :meth:" +"`set_seqs` or :meth:`set_seq2`." +msgstr "" + +#: ../Doc/library/difflib.rst:393 +msgid "The *bjunk* and *bpopular* attributes." +msgstr "" + +#: ../Doc/library/difflib.rst:396 +msgid ":class:`SequenceMatcher` objects have the following methods:" +msgstr "" + +#: ../Doc/library/difflib.rst:400 +msgid "Set the two sequences to be compared." +msgstr "" + +#: ../Doc/library/difflib.rst:402 +msgid "" +":class:`SequenceMatcher` computes and caches detailed information about the " +"second sequence, so if you want to compare one sequence against many " +"sequences, use :meth:`set_seq2` to set the commonly used sequence once and " +"call :meth:`set_seq1` repeatedly, once for each of the other sequences." +msgstr "" + +#: ../Doc/library/difflib.rst:410 +msgid "" +"Set the first sequence to be compared. The second sequence to be compared " +"is not changed." +msgstr "" + +#: ../Doc/library/difflib.rst:416 +msgid "" +"Set the second sequence to be compared. The first sequence to be compared " +"is not changed." +msgstr "" + +#: ../Doc/library/difflib.rst:422 +msgid "Find longest matching block in ``a[alo:ahi]`` and ``b[blo:bhi]``." +msgstr "" + +#: ../Doc/library/difflib.rst:424 +msgid "" +"If *isjunk* was omitted or ``None``, :meth:`find_longest_match` returns " +"``(i, j, k)`` such that ``a[i:i+k]`` is equal to ``b[j:j+k]``, where ``alo " +"<= i <= i+k <= ahi`` and ``blo <= j <= j+k <= bhi``. For all ``(i', j', " +"k')`` meeting those conditions, the additional conditions ``k >= k'``, ``i " +"<= i'``, and if ``i == i'``, ``j <= j'`` are also met. In other words, of " +"all maximal matching blocks, return one that starts earliest in *a*, and of " +"all those maximal matching blocks that start earliest in *a*, return the one " +"that starts earliest in *b*." +msgstr "" + +#: ../Doc/library/difflib.rst:437 +msgid "" +"If *isjunk* was provided, first the longest matching block is determined as " +"above, but with the additional restriction that no junk element appears in " +"the block. Then that block is extended as far as possible by matching " +"(only) junk elements on both sides. So the resulting block never matches on " +"junk except as identical junk happens to be adjacent to an interesting match." +msgstr "" + +#: ../Doc/library/difflib.rst:444 +msgid "" +"Here's the same example as before, but considering blanks to be junk. That " +"prevents ``' abcd'`` from matching the ``' abcd'`` at the tail end of the " +"second sequence directly. Instead only the ``'abcd'`` can match, and " +"matches the leftmost ``'abcd'`` in the second sequence:" +msgstr "" + +#: ../Doc/library/difflib.rst:453 +msgid "If no blocks match, this returns ``(alo, blo, 0)``." +msgstr "" + +#: ../Doc/library/difflib.rst:455 +msgid "This method returns a :term:`named tuple` ``Match(a, b, size)``." +msgstr "" + +#: ../Doc/library/difflib.rst:460 +msgid "" +"Return list of triples describing matching subsequences. Each triple is of " +"the form ``(i, j, n)``, and means that ``a[i:i+n] == b[j:j+n]``. The " +"triples are monotonically increasing in *i* and *j*." +msgstr "" + +#: ../Doc/library/difflib.rst:464 +msgid "" +"The last triple is a dummy, and has the value ``(len(a), len(b), 0)``. It " +"is the only triple with ``n == 0``. If ``(i, j, n)`` and ``(i', j', n')`` " +"are adjacent triples in the list, and the second is not the last triple in " +"the list, then ``i+n != i'`` or ``j+n != j'``; in other words, adjacent " +"triples always describe non-adjacent equal blocks." +msgstr "" + +#: ../Doc/library/difflib.rst:481 +msgid "" +"Return list of 5-tuples describing how to turn *a* into *b*. Each tuple is " +"of the form ``(tag, i1, i2, j1, j2)``. The first tuple has ``i1 == j1 == " +"0``, and remaining tuples have *i1* equal to the *i2* from the preceding " +"tuple, and, likewise, *j1* equal to the previous *j2*." +msgstr "" + +#: ../Doc/library/difflib.rst:486 +msgid "The *tag* values are strings, with these meanings:" +msgstr "" + +#: ../Doc/library/difflib.rst:491 +msgid "``a[i1:i2]`` should be replaced by ``b[j1:j2]``." +msgstr "" + +#: ../Doc/library/difflib.rst:494 +msgid "``'delete'``" +msgstr "" + +#: ../Doc/library/difflib.rst:494 +msgid "``a[i1:i2]`` should be deleted. Note that ``j1 == j2`` in this case." +msgstr "" + +#: ../Doc/library/difflib.rst:497 +msgid "``'insert'``" +msgstr "" + +#: ../Doc/library/difflib.rst:497 +msgid "" +"``b[j1:j2]`` should be inserted at ``a[i1:i1]``. Note that ``i1 == i2`` in " +"this case." +msgstr "" + +#: ../Doc/library/difflib.rst:501 +msgid "``'equal'``" +msgstr "" + +#: ../Doc/library/difflib.rst:501 +msgid "``a[i1:i2] == b[j1:j2]`` (the sub-sequences are equal)." +msgstr "" + +#: ../Doc/library/difflib.rst:522 +msgid "Return a :term:`generator` of groups with up to *n* lines of context." +msgstr "" + +#: ../Doc/library/difflib.rst:524 +msgid "" +"Starting with the groups returned by :meth:`get_opcodes`, this method splits " +"out smaller change clusters and eliminates intervening ranges which have no " +"changes." +msgstr "" + +#: ../Doc/library/difflib.rst:528 +msgid "The groups are returned in the same format as :meth:`get_opcodes`." +msgstr "" + +#: ../Doc/library/difflib.rst:533 +msgid "" +"Return a measure of the sequences' similarity as a float in the range [0, 1]." +msgstr "" + +#: ../Doc/library/difflib.rst:536 +msgid "" +"Where T is the total number of elements in both sequences, and M is the " +"number of matches, this is 2.0\\*M / T. Note that this is ``1.0`` if the " +"sequences are identical, and ``0.0`` if they have nothing in common." +msgstr "" + +#: ../Doc/library/difflib.rst:540 +msgid "" +"This is expensive to compute if :meth:`get_matching_blocks` or :meth:" +"`get_opcodes` hasn't already been called, in which case you may want to try :" +"meth:`quick_ratio` or :meth:`real_quick_ratio` first to get an upper bound." +msgstr "" + +#: ../Doc/library/difflib.rst:548 +msgid "Return an upper bound on :meth:`ratio` relatively quickly." +msgstr "" + +#: ../Doc/library/difflib.rst:553 +msgid "Return an upper bound on :meth:`ratio` very quickly." +msgstr "" + +#: ../Doc/library/difflib.rst:556 +msgid "" +"The three methods that return the ratio of matching to total characters can " +"give different results due to differing levels of approximation, although :" +"meth:`quick_ratio` and :meth:`real_quick_ratio` are always at least as large " +"as :meth:`ratio`:" +msgstr "" + +#: ../Doc/library/difflib.rst:573 +msgid "SequenceMatcher Examples" +msgstr "" + +#: ../Doc/library/difflib.rst:575 +msgid "This example compares two strings, considering blanks to be \"junk\":" +msgstr "" + +#: ../Doc/library/difflib.rst:581 +msgid "" +":meth:`ratio` returns a float in [0, 1], measuring the similarity of the " +"sequences. As a rule of thumb, a :meth:`ratio` value over 0.6 means the " +"sequences are close matches:" +msgstr "" + +#: ../Doc/library/difflib.rst:588 +msgid "" +"If you're only interested in where the sequences match, :meth:" +"`get_matching_blocks` is handy:" +msgstr "" + +#: ../Doc/library/difflib.rst:597 +msgid "" +"Note that the last tuple returned by :meth:`get_matching_blocks` is always a " +"dummy, ``(len(a), len(b), 0)``, and this is the only case in which the last " +"tuple element (number of elements matched) is ``0``." +msgstr "" + +#: ../Doc/library/difflib.rst:601 +msgid "" +"If you want to know how to change the first sequence into the second, use :" +"meth:`get_opcodes`:" +msgstr "" + +#: ../Doc/library/difflib.rst:612 +msgid "" +"The :func:`get_close_matches` function in this module which shows how simple " +"code building on :class:`SequenceMatcher` can be used to do useful work." +msgstr "" + +#: ../Doc/library/difflib.rst:616 +msgid "" +"`Simple version control recipe `_ for a small application built with :class:`SequenceMatcher`." +msgstr "" + +#: ../Doc/library/difflib.rst:624 +msgid "Differ Objects" +msgstr "" + +#: ../Doc/library/difflib.rst:626 +msgid "" +"Note that :class:`Differ`\\ -generated deltas make no claim to be " +"**minimal** diffs. To the contrary, minimal diffs are often counter-" +"intuitive, because they synch up anywhere possible, sometimes accidental " +"matches 100 pages apart. Restricting synch points to contiguous matches " +"preserves some notion of locality, at the occasional cost of producing a " +"longer diff." +msgstr "" + +#: ../Doc/library/difflib.rst:632 +msgid "The :class:`Differ` class has this constructor:" +msgstr "" + +#: ../Doc/library/difflib.rst:637 +msgid "" +"Optional keyword parameters *linejunk* and *charjunk* are for filter " +"functions (or ``None``):" +msgstr "" + +#: ../Doc/library/difflib.rst:640 +msgid "" +"*linejunk*: A function that accepts a single string argument, and returns " +"true if the string is junk. The default is ``None``, meaning that no line " +"is considered junk." +msgstr "" + +#: ../Doc/library/difflib.rst:644 +msgid "" +"*charjunk*: A function that accepts a single character argument (a string of " +"length 1), and returns true if the character is junk. The default is " +"``None``, meaning that no character is considered junk." +msgstr "" + +#: ../Doc/library/difflib.rst:648 +msgid "" +"These junk-filtering functions speed up matching to find differences and do " +"not cause any differing lines or characters to be ignored. Read the " +"description of the :meth:`~SequenceMatcher.find_longest_match` method's " +"*isjunk* parameter for an explanation." +msgstr "" + +#: ../Doc/library/difflib.rst:654 +msgid "" +":class:`Differ` objects are used (deltas generated) via a single method:" +msgstr "" + +#: ../Doc/library/difflib.rst:659 +msgid "" +"Compare two sequences of lines, and generate the delta (a sequence of lines)." +msgstr "" + +#: ../Doc/library/difflib.rst:661 +msgid "" +"Each sequence must contain individual single-line strings ending with " +"newlines. Such sequences can be obtained from the :meth:`~io.IOBase." +"readlines` method of file-like objects. The delta generated also consists " +"of newline-terminated strings, ready to be printed as-is via the :meth:`~io." +"IOBase.writelines` method of a file-like object." +msgstr "" + +#: ../Doc/library/difflib.rst:672 +msgid "Differ Example" +msgstr "" + +#: ../Doc/library/difflib.rst:674 +msgid "" +"This example compares two texts. First we set up the texts, sequences of " +"individual single-line strings ending with newlines (such sequences can also " +"be obtained from the :meth:`~io.BaseIO.readlines` method of file-like " +"objects):" +msgstr "" + +#: ../Doc/library/difflib.rst:693 +msgid "Next we instantiate a Differ object:" +msgstr "" + +#: ../Doc/library/difflib.rst:697 +msgid "" +"Note that when instantiating a :class:`Differ` object we may pass functions " +"to filter out line and character \"junk.\" See the :meth:`Differ` " +"constructor for details." +msgstr "" + +#: ../Doc/library/difflib.rst:701 +msgid "Finally, we compare the two:" +msgstr "" + +#: ../Doc/library/difflib.rst:705 +msgid "``result`` is a list of strings, so let's pretty-print it:" +msgstr "" + +#: ../Doc/library/difflib.rst:720 +msgid "As a single multi-line string it looks like this:" +msgstr "" + +#: ../Doc/library/difflib.rst:739 +msgid "A command-line interface to difflib" +msgstr "" + +#: ../Doc/library/difflib.rst:741 +msgid "" +"This example shows how to use difflib to create a ``diff``-like utility. It " +"is also contained in the Python source distribution, as :file:`Tools/scripts/" +"diff.py`." +msgstr "" + +#: ../Doc/library/dis.rst:2 +msgid ":mod:`dis` --- Disassembler for Python bytecode" +msgstr "" + +#: ../Doc/library/dis.rst:7 +msgid "**Source code:** :source:`Lib/dis.py`" +msgstr "" + +#: ../Doc/library/dis.rst:11 +msgid "" +"The :mod:`dis` module supports the analysis of CPython :term:`bytecode` by " +"disassembling it. The CPython bytecode which this module takes as an input " +"is defined in the file :file:`Include/opcode.h` and used by the compiler and " +"the interpreter." +msgstr "" + +#: ../Doc/library/dis.rst:18 +msgid "" +"Bytecode is an implementation detail of the CPython interpreter. No " +"guarantees are made that bytecode will not be added, removed, or changed " +"between versions of Python. Use of this module should not be considered to " +"work across Python VMs or Python releases." +msgstr "" + +#: ../Doc/library/dis.rst:24 +msgid "Example: Given the function :func:`myfunc`::" +msgstr "" + +#: ../Doc/library/dis.rst:29 +msgid "" +"the following command can be used to display the disassembly of :func:" +"`myfunc`::" +msgstr "" + +#: ../Doc/library/dis.rst:38 +msgid "(The \"2\" is a line number)." +msgstr "" + +#: ../Doc/library/dis.rst:41 +msgid "Bytecode analysis" +msgstr "" + +#: ../Doc/library/dis.rst:45 +msgid "" +"The bytecode analysis API allows pieces of Python code to be wrapped in a :" +"class:`Bytecode` object that provides easy access to details of the compiled " +"code." +msgstr "" + +#: ../Doc/library/dis.rst:52 +msgid "" +"Analyse the bytecode corresponding to a function, generator, method, string " +"of source code, or a code object (as returned by :func:`compile`)." +msgstr "" + +#: ../Doc/library/dis.rst:55 +msgid "" +"This is a convenience wrapper around many of the functions listed below, " +"most notably :func:`get_instructions`, as iterating over a :class:`Bytecode` " +"instance yields the bytecode operations as :class:`Instruction` instances." +msgstr "" + +#: ../Doc/library/dis.rst:59 ../Doc/library/dis.rst:200 +msgid "" +"If *first_line* is not None, it indicates the line number that should be " +"reported for the first source line in the disassembled code. Otherwise, the " +"source line information (if any) is taken directly from the disassembled " +"code object." +msgstr "" + +#: ../Doc/library/dis.rst:64 +msgid "" +"If *current_offset* is not None, it refers to an instruction offset in the " +"disassembled code. Setting this means :meth:`.dis` will display a \"current " +"instruction\" marker against the specified opcode." +msgstr "" + +#: ../Doc/library/dis.rst:70 +msgid "" +"Construct a :class:`Bytecode` instance from the given traceback, setting " +"*current_offset* to the instruction responsible for the exception." +msgstr "" + +#: ../Doc/library/dis.rst:75 +msgid "The compiled code object." +msgstr "" + +#: ../Doc/library/dis.rst:79 +msgid "The first source line of the code object (if available)" +msgstr "" + +#: ../Doc/library/dis.rst:83 +msgid "" +"Return a formatted view of the bytecode operations (the same as printed by :" +"func:`dis.dis`, but returned as a multi-line string)." +msgstr "" + +#: ../Doc/library/dis.rst:88 +msgid "" +"Return a formatted multi-line string with detailed information about the " +"code object, like :func:`code_info`." +msgstr "" + +#: ../Doc/library/dis.rst:104 +msgid "Analysis functions" +msgstr "" + +#: ../Doc/library/dis.rst:106 +msgid "" +"The :mod:`dis` module also defines the following analysis functions that " +"convert the input directly to the desired output. They can be useful if only " +"a single operation is being performed, so the intermediate analysis object " +"isn't useful:" +msgstr "" + +#: ../Doc/library/dis.rst:112 +msgid "" +"Return a formatted multi-line string with detailed code object information " +"for the supplied function, generator, method, source code string or code " +"object." +msgstr "" + +#: ../Doc/library/dis.rst:115 +msgid "" +"Note that the exact contents of code info strings are highly implementation " +"dependent and they may change arbitrarily across Python VMs or Python " +"releases." +msgstr "" + +#: ../Doc/library/dis.rst:124 +msgid "" +"Print detailed code object information for the supplied function, method, " +"source code string or code object to *file* (or ``sys.stdout`` if *file* is " +"not specified)." +msgstr "" + +#: ../Doc/library/dis.rst:128 +msgid "" +"This is a convenient shorthand for ``print(code_info(x), file=file)``, " +"intended for interactive exploration at the interpreter prompt." +msgstr "" + +#: ../Doc/library/dis.rst:133 ../Doc/library/dis.rst:151 +#: ../Doc/library/dis.rst:164 ../Doc/library/dis.rst:188 +msgid "Added *file* parameter." +msgstr "" + +#: ../Doc/library/dis.rst:139 +msgid "" +"Disassemble the *x* object. *x* can denote either a module, a class, a " +"method, a function, a generator, a code object, a string of source code or a " +"byte sequence of raw bytecode. For a module, it disassembles all functions. " +"For a class, it disassembles all methods (including class and static " +"methods). For a code object or sequence of raw bytecode, it prints one line " +"per bytecode instruction. Strings are first compiled to code objects with " +"the :func:`compile` built-in function before being disassembled. If no " +"object is provided, this function disassembles the last traceback." +msgstr "" + +#: ../Doc/library/dis.rst:148 ../Doc/library/dis.rst:161 +#: ../Doc/library/dis.rst:185 +msgid "" +"The disassembly is written as text to the supplied *file* argument if " +"provided and to ``sys.stdout`` otherwise." +msgstr "" + +#: ../Doc/library/dis.rst:157 +msgid "" +"Disassemble the top-of-stack function of a traceback, using the last " +"traceback if none was passed. The instruction causing the exception is " +"indicated." +msgstr "" + +#: ../Doc/library/dis.rst:171 +msgid "" +"Disassemble a code object, indicating the last instruction if *lasti* was " +"provided. The output is divided in the following columns:" +msgstr "" + +#: ../Doc/library/dis.rst:174 +msgid "the line number, for the first instruction of each line" +msgstr "" + +#: ../Doc/library/dis.rst:175 +msgid "the current instruction, indicated as ``-->``," +msgstr "" + +#: ../Doc/library/dis.rst:176 +msgid "a labelled instruction, indicated with ``>>``," +msgstr "" + +#: ../Doc/library/dis.rst:177 +msgid "the address of the instruction," +msgstr "" + +#: ../Doc/library/dis.rst:178 +msgid "the operation code name," +msgstr "" + +#: ../Doc/library/dis.rst:179 +msgid "operation parameters, and" +msgstr "" + +#: ../Doc/library/dis.rst:180 +msgid "interpretation of the parameters in parentheses." +msgstr "" + +#: ../Doc/library/dis.rst:182 +msgid "" +"The parameter interpretation recognizes local and global variable names, " +"constant values, branch targets, and compare operators." +msgstr "" + +#: ../Doc/library/dis.rst:194 +msgid "" +"Return an iterator over the instructions in the supplied function, method, " +"source code string or code object." +msgstr "" + +#: ../Doc/library/dis.rst:197 +msgid "" +"The iterator generates a series of :class:`Instruction` named tuples giving " +"the details of each operation in the supplied code." +msgstr "" + +#: ../Doc/library/dis.rst:210 +msgid "" +"This generator function uses the ``co_firstlineno`` and ``co_lnotab`` " +"attributes of the code object *code* to find the offsets which are starts of " +"lines in the source code. They are generated as ``(offset, lineno)`` pairs." +msgstr "" + +#: ../Doc/library/dis.rst:217 +msgid "" +"Detect all offsets in the code object *code* which are jump targets, and " +"return a list of these offsets." +msgstr "" + +#: ../Doc/library/dis.rst:223 +msgid "Compute the stack effect of *opcode* with argument *oparg*." +msgstr "" + +#: ../Doc/library/dis.rst:230 +msgid "Python Bytecode Instructions" +msgstr "" + +#: ../Doc/library/dis.rst:232 +msgid "" +"The :func:`get_instructions` function and :class:`Bytecode` class provide " +"details of bytecode instructions as :class:`Instruction` instances:" +msgstr "" + +#: ../Doc/library/dis.rst:237 +msgid "Details for a bytecode operation" +msgstr "" + +#: ../Doc/library/dis.rst:241 +msgid "" +"numeric code for operation, corresponding to the opcode values listed below " +"and the bytecode values in the :ref:`opcode_collections`." +msgstr "" + +#: ../Doc/library/dis.rst:247 +msgid "human readable name for operation" +msgstr "" + +#: ../Doc/library/dis.rst:252 +msgid "numeric argument to operation (if any), otherwise None" +msgstr "" + +#: ../Doc/library/dis.rst:257 +msgid "resolved arg value (if known), otherwise same as arg" +msgstr "" + +#: ../Doc/library/dis.rst:262 +msgid "human readable description of operation argument" +msgstr "" + +#: ../Doc/library/dis.rst:267 +msgid "start index of operation within bytecode sequence" +msgstr "" + +#: ../Doc/library/dis.rst:272 +msgid "line started by this opcode (if any), otherwise None" +msgstr "" + +#: ../Doc/library/dis.rst:277 +msgid "``True`` if other code jumps to here, otherwise ``False``" +msgstr "" + +#: ../Doc/library/dis.rst:282 +msgid "" +"The Python compiler currently generates the following bytecode instructions." +msgstr "" + +#: ../Doc/library/dis.rst:285 +msgid "**General instructions**" +msgstr "" + +#: ../Doc/library/dis.rst:289 +msgid "Do nothing code. Used as a placeholder by the bytecode optimizer." +msgstr "" + +#: ../Doc/library/dis.rst:294 +msgid "Removes the top-of-stack (TOS) item." +msgstr "" + +#: ../Doc/library/dis.rst:299 +msgid "Swaps the two top-most stack items." +msgstr "" + +#: ../Doc/library/dis.rst:304 +msgid "" +"Lifts second and third stack item one position up, moves top down to " +"position three." +msgstr "" + +#: ../Doc/library/dis.rst:310 +msgid "Duplicates the reference on top of the stack." +msgstr "" + +#: ../Doc/library/dis.rst:315 +msgid "" +"Duplicates the two references on top of the stack, leaving them in the same " +"order." +msgstr "" + +#: ../Doc/library/dis.rst:319 +msgid "**Unary operations**" +msgstr "" + +#: ../Doc/library/dis.rst:321 +msgid "" +"Unary operations take the top of the stack, apply the operation, and push " +"the result back on the stack." +msgstr "" + +#: ../Doc/library/dis.rst:326 +msgid "Implements ``TOS = +TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:331 +msgid "Implements ``TOS = -TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:336 +msgid "Implements ``TOS = not TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:341 +msgid "Implements ``TOS = ~TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:346 +msgid "Implements ``TOS = iter(TOS)``." +msgstr "" + +#: ../Doc/library/dis.rst:351 +msgid "" +"If ``TOS`` is a :term:`generator iterator` or :term:`coroutine` object it is " +"left as is. Otherwise, implements ``TOS = iter(TOS)``." +msgstr "" + +#: ../Doc/library/dis.rst:357 +msgid "**Binary operations**" +msgstr "" + +#: ../Doc/library/dis.rst:359 +msgid "" +"Binary operations remove the top of the stack (TOS) and the second top-most " +"stack item (TOS1) from the stack. They perform the operation, and put the " +"result back on the stack." +msgstr "" + +#: ../Doc/library/dis.rst:365 +msgid "Implements ``TOS = TOS1 ** TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:370 +msgid "Implements ``TOS = TOS1 * TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:375 +msgid "Implements ``TOS = TOS1 @ TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:382 +msgid "Implements ``TOS = TOS1 // TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:387 +msgid "Implements ``TOS = TOS1 / TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:392 +msgid "Implements ``TOS = TOS1 % TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:397 +msgid "Implements ``TOS = TOS1 + TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:402 +msgid "Implements ``TOS = TOS1 - TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:407 +msgid "Implements ``TOS = TOS1[TOS]``." +msgstr "" + +#: ../Doc/library/dis.rst:412 +msgid "Implements ``TOS = TOS1 << TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:417 +msgid "Implements ``TOS = TOS1 >> TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:422 +msgid "Implements ``TOS = TOS1 & TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:427 +msgid "Implements ``TOS = TOS1 ^ TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:432 +msgid "Implements ``TOS = TOS1 | TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:435 +msgid "**In-place operations**" +msgstr "" + +#: ../Doc/library/dis.rst:437 +msgid "" +"In-place operations are like binary operations, in that they remove TOS and " +"TOS1, and push the result back on the stack, but the operation is done in-" +"place when TOS1 supports it, and the resulting TOS may be (but does not have " +"to be) the original TOS1." +msgstr "" + +#: ../Doc/library/dis.rst:444 +msgid "Implements in-place ``TOS = TOS1 ** TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:449 +msgid "Implements in-place ``TOS = TOS1 * TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:454 +msgid "Implements in-place ``TOS = TOS1 @ TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:461 +msgid "Implements in-place ``TOS = TOS1 // TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:466 +msgid "Implements in-place ``TOS = TOS1 / TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:471 +msgid "Implements in-place ``TOS = TOS1 % TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:476 +msgid "Implements in-place ``TOS = TOS1 + TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:481 +msgid "Implements in-place ``TOS = TOS1 - TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:486 +msgid "Implements in-place ``TOS = TOS1 << TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:491 +msgid "Implements in-place ``TOS = TOS1 >> TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:496 +msgid "Implements in-place ``TOS = TOS1 & TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:501 +msgid "Implements in-place ``TOS = TOS1 ^ TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:506 +msgid "Implements in-place ``TOS = TOS1 | TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:511 +msgid "Implements ``TOS1[TOS] = TOS2``." +msgstr "" + +#: ../Doc/library/dis.rst:516 +msgid "Implements ``del TOS1[TOS]``." +msgstr "" + +#: ../Doc/library/dis.rst:519 +msgid "**Coroutine opcodes**" +msgstr "" + +#: ../Doc/library/dis.rst:523 +msgid "" +"Implements ``TOS = get_awaitable(TOS)``, where ``get_awaitable(o)`` returns " +"``o`` if ``o`` is a coroutine object or a generator object with the " +"CO_ITERABLE_COROUTINE flag, or resolves ``o.__await__``." +msgstr "" + +#: ../Doc/library/dis.rst:531 +msgid "" +"Implements ``TOS = get_awaitable(TOS.__aiter__())``. See ``GET_AWAITABLE`` " +"for details about ``get_awaitable``" +msgstr "" + +#: ../Doc/library/dis.rst:537 +msgid "" +"Implements ``PUSH(get_awaitable(TOS.__anext__()))``. See ``GET_AWAITABLE`` " +"for details about ``get_awaitable``" +msgstr "" + +#: ../Doc/library/dis.rst:543 +msgid "" +"Resolves ``__aenter__`` and ``__aexit__`` from the object on top of the " +"stack. Pushes ``__aexit__`` and result of ``__aenter__()`` to the stack." +msgstr "" + +#: ../Doc/library/dis.rst:549 +msgid "Creates a new frame object." +msgstr "" + +#: ../Doc/library/dis.rst:553 +msgid "**Miscellaneous opcodes**" +msgstr "" + +#: ../Doc/library/dis.rst:557 +msgid "" +"Implements the expression statement for the interactive mode. TOS is " +"removed from the stack and printed. In non-interactive mode, an expression " +"statement is terminated with :opcode:`POP_TOP`." +msgstr "" + +#: ../Doc/library/dis.rst:564 +msgid "Terminates a loop due to a :keyword:`break` statement." +msgstr "" + +#: ../Doc/library/dis.rst:569 +msgid "" +"Continues a loop due to a :keyword:`continue` statement. *target* is the " +"address to jump to (which should be a :opcode:`FOR_ITER` instruction)." +msgstr "" + +#: ../Doc/library/dis.rst:575 +msgid "" +"Calls ``set.add(TOS1[-i], TOS)``. Used to implement set comprehensions." +msgstr "" + +#: ../Doc/library/dis.rst:580 +msgid "" +"Calls ``list.append(TOS[-i], TOS)``. Used to implement list comprehensions." +msgstr "" + +#: ../Doc/library/dis.rst:585 +msgid "" +"Calls ``dict.setitem(TOS1[-i], TOS, TOS1)``. Used to implement dict " +"comprehensions." +msgstr "" + +#: ../Doc/library/dis.rst:588 +msgid "" +"For all of the :opcode:`SET_ADD`, :opcode:`LIST_APPEND` and :opcode:" +"`MAP_ADD` instructions, while the added value or key/value pair is popped " +"off, the container object remains on the stack so that it is available for " +"further iterations of the loop." +msgstr "" + +#: ../Doc/library/dis.rst:596 +msgid "Returns with TOS to the caller of the function." +msgstr "" + +#: ../Doc/library/dis.rst:601 +msgid "Pops TOS and yields it from a :term:`generator`." +msgstr "" + +#: ../Doc/library/dis.rst:606 +msgid "Pops TOS and delegates to it as a subiterator from a :term:`generator`." +msgstr "" + +#: ../Doc/library/dis.rst:612 +msgid "" +"Checks whether ``__annotations__`` is defined in ``locals()``, if not it is " +"set up to an empty ``dict``. This opcode is only emitted if a class or " +"module body contains :term:`variable annotations ` " +"statically." +msgstr "" + +#: ../Doc/library/dis.rst:621 +msgid "" +"Loads all symbols not starting with ``'_'`` directly from the module TOS to " +"the local namespace. The module is popped after loading all names. This " +"opcode implements ``from module import *``." +msgstr "" + +#: ../Doc/library/dis.rst:628 +msgid "" +"Removes one block from the block stack. Per frame, there is a stack of " +"blocks, denoting nested loops, try statements, and such." +msgstr "" + +#: ../Doc/library/dis.rst:634 +msgid "" +"Removes one block from the block stack. The popped block must be an " +"exception handler block, as implicitly created when entering an except " +"handler. In addition to popping extraneous values from the frame stack, the " +"last three popped values are used to restore the exception state." +msgstr "" + +#: ../Doc/library/dis.rst:642 +msgid "" +"Terminates a :keyword:`finally` clause. The interpreter recalls whether the " +"exception has to be re-raised, or whether the function returns, and " +"continues with the outer-next block." +msgstr "" + +#: ../Doc/library/dis.rst:649 +msgid "" +"Pushes :func:`builtins.__build_class__` onto the stack. It is later called " +"by :opcode:`CALL_FUNCTION` to construct a class." +msgstr "" + +#: ../Doc/library/dis.rst:655 +msgid "" +"This opcode performs several operations before a with block starts. First, " +"it loads :meth:`~object.__exit__` from the context manager and pushes it " +"onto the stack for later use by :opcode:`WITH_CLEANUP`. Then, :meth:" +"`~object.__enter__` is called, and a finally block pointing to *delta* is " +"pushed. Finally, the result of calling the enter method is pushed onto the " +"stack. The next opcode will either ignore it (:opcode:`POP_TOP`), or store " +"it in (a) variable(s) (:opcode:`STORE_FAST`, :opcode:`STORE_NAME`, or :" +"opcode:`UNPACK_SEQUENCE`)." +msgstr "" + +#: ../Doc/library/dis.rst:667 +msgid "" +"Cleans up the stack when a :keyword:`with` statement block exits. TOS is " +"the context manager's :meth:`__exit__` bound method. Below TOS are 1--3 " +"values indicating how/why the finally clause was entered:" +msgstr "" + +#: ../Doc/library/dis.rst:671 +msgid "SECOND = ``None``" +msgstr "" + +#: ../Doc/library/dis.rst:672 +msgid "(SECOND, THIRD) = (``WHY_{RETURN,CONTINUE}``), retval" +msgstr "" + +#: ../Doc/library/dis.rst:673 +msgid "SECOND = ``WHY_*``; no retval below it" +msgstr "" + +#: ../Doc/library/dis.rst:674 +msgid "(SECOND, THIRD, FOURTH) = exc_info()" +msgstr "" + +#: ../Doc/library/dis.rst:676 +msgid "" +"In the last case, ``TOS(SECOND, THIRD, FOURTH)`` is called, otherwise " +"``TOS(None, None, None)``. Pushes SECOND and result of the call to the " +"stack." +msgstr "" + +#: ../Doc/library/dis.rst:683 +msgid "Pops exception type and result of 'exit' function call from the stack." +msgstr "" + +#: ../Doc/library/dis.rst:685 +msgid "" +"If the stack represents an exception, *and* the function call returns a " +"'true' value, this information is \"zapped\" and replaced with a single " +"``WHY_SILENCED`` to prevent :opcode:`END_FINALLY` from re-raising the " +"exception. (But non-local gotos will still be resumed.)" +msgstr "" + +#: ../Doc/library/dis.rst:693 +msgid "All of the following opcodes use their arguments." +msgstr "" + +#: ../Doc/library/dis.rst:697 +msgid "" +"Implements ``name = TOS``. *namei* is the index of *name* in the attribute :" +"attr:`co_names` of the code object. The compiler tries to use :opcode:" +"`STORE_FAST` or :opcode:`STORE_GLOBAL` if possible." +msgstr "" + +#: ../Doc/library/dis.rst:704 +msgid "" +"Implements ``del name``, where *namei* is the index into :attr:`co_names` " +"attribute of the code object." +msgstr "" + +#: ../Doc/library/dis.rst:710 +msgid "" +"Unpacks TOS into *count* individual values, which are put onto the stack " +"right-to-left." +msgstr "" + +#: ../Doc/library/dis.rst:716 +msgid "" +"Implements assignment with a starred target: Unpacks an iterable in TOS into " +"individual values, where the total number of values can be smaller than the " +"number of items in the iterable: one of the new values will be a list of all " +"leftover items." +msgstr "" + +#: ../Doc/library/dis.rst:721 +msgid "" +"The low byte of *counts* is the number of values before the list value, the " +"high byte of *counts* the number of values after it. The resulting values " +"are put onto the stack right-to-left." +msgstr "" + +#: ../Doc/library/dis.rst:728 +msgid "" +"Implements ``TOS.name = TOS1``, where *namei* is the index of name in :attr:" +"`co_names`." +msgstr "" + +#: ../Doc/library/dis.rst:734 +msgid "" +"Implements ``del TOS.name``, using *namei* as index into :attr:`co_names`." +msgstr "" + +#: ../Doc/library/dis.rst:739 +msgid "Works as :opcode:`STORE_NAME`, but stores the name as a global." +msgstr "" + +#: ../Doc/library/dis.rst:744 +msgid "Works as :opcode:`DELETE_NAME`, but deletes a global name." +msgstr "" + +#: ../Doc/library/dis.rst:749 +msgid "Pushes ``co_consts[consti]`` onto the stack." +msgstr "" + +#: ../Doc/library/dis.rst:754 +msgid "Pushes the value associated with ``co_names[namei]`` onto the stack." +msgstr "" + +#: ../Doc/library/dis.rst:759 +msgid "" +"Creates a tuple consuming *count* items from the stack, and pushes the " +"resulting tuple onto the stack." +msgstr "" + +#: ../Doc/library/dis.rst:765 +msgid "Works as :opcode:`BUILD_TUPLE`, but creates a list." +msgstr "" + +#: ../Doc/library/dis.rst:770 +msgid "Works as :opcode:`BUILD_TUPLE`, but creates a set." +msgstr "" + +#: ../Doc/library/dis.rst:775 +msgid "" +"Pushes a new dictionary object onto the stack. The dictionary is pre-sized " +"to hold *count* entries." +msgstr "" + +#: ../Doc/library/dis.rst:781 +msgid "" +"The version of :opcode:`BUILD_MAP` specialized for constant keys. *count* " +"values are consumed from the stack. The top element on the stack contains a " +"tuple of keys." +msgstr "" + +#: ../Doc/library/dis.rst:790 +msgid "" +"Concatenates *count* strings from the stack and pushes the resulting string " +"onto the stack." +msgstr "" + +#: ../Doc/library/dis.rst:798 +msgid "Replaces TOS with ``getattr(TOS, co_names[namei])``." +msgstr "" + +#: ../Doc/library/dis.rst:803 +msgid "" +"Performs a Boolean operation. The operation name can be found in " +"``cmp_op[opname]``." +msgstr "" + +#: ../Doc/library/dis.rst:809 +msgid "" +"Imports the module ``co_names[namei]``. TOS and TOS1 are popped and provide " +"the *fromlist* and *level* arguments of :func:`__import__`. The module " +"object is pushed onto the stack. The current namespace is not affected: for " +"a proper import statement, a subsequent :opcode:`STORE_FAST` instruction " +"modifies the namespace." +msgstr "" + +#: ../Doc/library/dis.rst:818 +msgid "" +"Loads the attribute ``co_names[namei]`` from the module found in TOS. The " +"resulting object is pushed onto the stack, to be subsequently stored by a :" +"opcode:`STORE_FAST` instruction." +msgstr "" + +#: ../Doc/library/dis.rst:825 +msgid "Increments bytecode counter by *delta*." +msgstr "" + +#: ../Doc/library/dis.rst:830 +msgid "If TOS is true, sets the bytecode counter to *target*. TOS is popped." +msgstr "" + +#: ../Doc/library/dis.rst:835 +msgid "If TOS is false, sets the bytecode counter to *target*. TOS is popped." +msgstr "" + +#: ../Doc/library/dis.rst:840 +msgid "" +"If TOS is true, sets the bytecode counter to *target* and leaves TOS on the " +"stack. Otherwise (TOS is false), TOS is popped." +msgstr "" + +#: ../Doc/library/dis.rst:846 +msgid "" +"If TOS is false, sets the bytecode counter to *target* and leaves TOS on the " +"stack. Otherwise (TOS is true), TOS is popped." +msgstr "" + +#: ../Doc/library/dis.rst:852 +msgid "Set bytecode counter to *target*." +msgstr "" + +#: ../Doc/library/dis.rst:857 +msgid "" +"TOS is an :term:`iterator`. Call its :meth:`~iterator.__next__` method. If " +"this yields a new value, push it on the stack (leaving the iterator below " +"it). If the iterator indicates it is exhausted TOS is popped, and the byte " +"code counter is incremented by *delta*." +msgstr "" + +#: ../Doc/library/dis.rst:865 +msgid "Loads the global named ``co_names[namei]`` onto the stack." +msgstr "" + +#: ../Doc/library/dis.rst:870 +msgid "" +"Pushes a block for a loop onto the block stack. The block spans from the " +"current instruction with a size of *delta* bytes." +msgstr "" + +#: ../Doc/library/dis.rst:876 +msgid "" +"Pushes a try block from a try-except clause onto the block stack. *delta* " +"points to the first except block." +msgstr "" + +#: ../Doc/library/dis.rst:882 +msgid "" +"Pushes a try block from a try-except clause onto the block stack. *delta* " +"points to the finally block." +msgstr "" + +#: ../Doc/library/dis.rst:888 +msgid "" +"Pushes a reference to the local ``co_varnames[var_num]`` onto the stack." +msgstr "" + +#: ../Doc/library/dis.rst:893 +msgid "Stores TOS into the local ``co_varnames[var_num]``." +msgstr "" + +#: ../Doc/library/dis.rst:898 +msgid "Deletes local ``co_varnames[var_num]``." +msgstr "" + +#: ../Doc/library/dis.rst:903 +msgid "Stores TOS as ``locals()['__annotations__'][co_names[namei]] = TOS``." +msgstr "" + +#: ../Doc/library/dis.rst:910 +msgid "" +"Pushes a reference to the cell contained in slot *i* of the cell and free " +"variable storage. The name of the variable is ``co_cellvars[i]`` if *i* is " +"less than the length of *co_cellvars*. Otherwise it is ``co_freevars[i - " +"len(co_cellvars)]``." +msgstr "" + +#: ../Doc/library/dis.rst:918 +msgid "" +"Loads the cell contained in slot *i* of the cell and free variable storage. " +"Pushes a reference to the object the cell contains on the stack." +msgstr "" + +#: ../Doc/library/dis.rst:924 +msgid "" +"Much like :opcode:`LOAD_DEREF` but first checks the locals dictionary before " +"consulting the cell. This is used for loading free variables in class " +"bodies." +msgstr "" + +#: ../Doc/library/dis.rst:931 +msgid "" +"Stores TOS into the cell contained in slot *i* of the cell and free variable " +"storage." +msgstr "" + +#: ../Doc/library/dis.rst:937 +msgid "" +"Empties the cell contained in slot *i* of the cell and free variable " +"storage. Used by the :keyword:`del` statement." +msgstr "" + +#: ../Doc/library/dis.rst:943 +msgid "" +"Raises an exception. *argc* indicates the number of parameters to the raise " +"statement, ranging from 0 to 3. The handler will find the traceback as " +"TOS2, the parameter as TOS1, and the exception as TOS." +msgstr "" + +#: ../Doc/library/dis.rst:950 +msgid "" +"Calls a function. The low byte of *argc* indicates the number of positional " +"parameters, the high byte the number of keyword parameters. On the stack, " +"the opcode finds the keyword parameters first. For each keyword argument, " +"the value is on top of the key. Below the keyword parameters, the " +"positional parameters are on the stack, with the right-most parameter on " +"top. Below the parameters, the function object to call is on the stack. " +"Pops all function arguments, and the function itself off the stack, and " +"pushes the return value." +msgstr "" + +#: ../Doc/library/dis.rst:962 +msgid "" +"Pushes a new function object on the stack. From bottom to top, the consumed " +"stack must consist of values if the argument carries a specified flag value" +msgstr "" + +#: ../Doc/library/dis.rst:965 +msgid "``0x01`` a tuple of default argument objects in positional order" +msgstr "" + +#: ../Doc/library/dis.rst:966 +msgid "``0x02`` a dictionary of keyword-only parameters' default values" +msgstr "" + +#: ../Doc/library/dis.rst:967 +msgid "``0x04`` an annotation dictionary" +msgstr "" + +#: ../Doc/library/dis.rst:968 +msgid "``0x08`` a tuple containing cells for free variables, making a closure" +msgstr "" + +#: ../Doc/library/dis.rst:969 +msgid "the code associated with the function (at TOS1)" +msgstr "" + +#: ../Doc/library/dis.rst:970 +msgid "the :term:`qualified name` of the function (at TOS)" +msgstr "" + +#: ../Doc/library/dis.rst:977 +msgid "" +"Pushes a slice object on the stack. *argc* must be 2 or 3. If it is 2, " +"``slice(TOS1, TOS)`` is pushed; if it is 3, ``slice(TOS2, TOS1, TOS)`` is " +"pushed. See the :func:`slice` built-in function for more information." +msgstr "" + +#: ../Doc/library/dis.rst:984 +msgid "" +"Prefixes any opcode which has an argument too big to fit into the default " +"two bytes. *ext* holds two additional bytes which, taken together with the " +"subsequent opcode's argument, comprise a four-byte argument, *ext* being the " +"two most-significant bytes." +msgstr "" + +#: ../Doc/library/dis.rst:992 +msgid "" +"Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The " +"top element on the stack contains the variable argument list, followed by " +"keyword and positional arguments." +msgstr "" + +#: ../Doc/library/dis.rst:999 +msgid "" +"Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The " +"top element on the stack contains the keyword arguments dictionary, followed " +"by explicit keyword and positional arguments." +msgstr "" + +#: ../Doc/library/dis.rst:1006 +msgid "" +"Calls a function. *argc* is interpreted as in :opcode:`CALL_FUNCTION`. The " +"top element on the stack contains the keyword arguments dictionary, followed " +"by the variable-arguments tuple, followed by explicit keyword and positional " +"arguments." +msgstr "" + +#: ../Doc/library/dis.rst:1014 +msgid "" +"Used for implementing formatted literal strings (f-strings). Pops an " +"optional *fmt_spec* from the stack, then a required *value*. *flags* is " +"interpreted as follows:" +msgstr "" + +#: ../Doc/library/dis.rst:1018 +msgid "``(flags & 0x03) == 0x00``: *value* is formatted as-is." +msgstr "" + +#: ../Doc/library/dis.rst:1019 +msgid "" +"``(flags & 0x03) == 0x01``: call :func:`str` on *value* before formatting it." +msgstr "" + +#: ../Doc/library/dis.rst:1021 +msgid "" +"``(flags & 0x03) == 0x02``: call :func:`repr` on *value* before formatting " +"it." +msgstr "" + +#: ../Doc/library/dis.rst:1023 +msgid "" +"``(flags & 0x03) == 0x03``: call :func:`ascii` on *value* before formatting " +"it." +msgstr "" + +#: ../Doc/library/dis.rst:1025 +msgid "" +"``(flags & 0x04) == 0x04``: pop *fmt_spec* from the stack and use it, else " +"use an empty *fmt_spec*." +msgstr "" + +#: ../Doc/library/dis.rst:1028 +msgid "" +"Formatting is performed using :c:func:`PyObject_Format`. The result is " +"pushed on the stack." +msgstr "" + +#: ../Doc/library/dis.rst:1036 +msgid "" +"This is not really an opcode. It identifies the dividing line between " +"opcodes which don't take arguments ``< HAVE_ARGUMENT`` and those which do " +"``>= HAVE_ARGUMENT``." +msgstr "" + +#: ../Doc/library/dis.rst:1043 +msgid "Opcode collections" +msgstr "" + +#: ../Doc/library/dis.rst:1045 +msgid "" +"These collections are provided for automatic introspection of bytecode " +"instructions:" +msgstr "" + +#: ../Doc/library/dis.rst:1050 +msgid "Sequence of operation names, indexable using the bytecode." +msgstr "" + +#: ../Doc/library/dis.rst:1055 +msgid "Dictionary mapping operation names to bytecodes." +msgstr "" + +#: ../Doc/library/dis.rst:1060 +msgid "Sequence of all compare operation names." +msgstr "" + +#: ../Doc/library/dis.rst:1065 +msgid "Sequence of bytecodes that have a constant parameter." +msgstr "" + +#: ../Doc/library/dis.rst:1070 +msgid "" +"Sequence of bytecodes that access a free variable (note that 'free' in this " +"context refers to names in the current scope that are referenced by inner " +"scopes or names in outer scopes that are referenced from this scope. It " +"does *not* include references to global or builtin scopes)." +msgstr "" + +#: ../Doc/library/dis.rst:1078 +msgid "Sequence of bytecodes that access an attribute by name." +msgstr "" + +#: ../Doc/library/dis.rst:1083 +msgid "Sequence of bytecodes that have a relative jump target." +msgstr "" + +#: ../Doc/library/dis.rst:1088 +msgid "Sequence of bytecodes that have an absolute jump target." +msgstr "" + +#: ../Doc/library/dis.rst:1093 +msgid "Sequence of bytecodes that access a local variable." +msgstr "" + +#: ../Doc/library/dis.rst:1098 +msgid "Sequence of bytecodes of Boolean operations." +msgstr "" + +#: ../Doc/library/distribution.rst:3 +msgid "Software Packaging and Distribution" +msgstr "" + +#: ../Doc/library/distribution.rst:5 +msgid "" +"These libraries help you with publishing and installing Python software. " +"While these modules are designed to work in conjunction with the `Python " +"Package Index `__, they can also be used with " +"a local index server, or without any index server at all." +msgstr "" + +#: ../Doc/library/distutils.rst:2 +msgid ":mod:`distutils` --- Building and installing Python modules" +msgstr "" + +#: ../Doc/library/distutils.rst:12 +msgid "" +"The :mod:`distutils` package provides support for building and installing " +"additional modules into a Python installation. The new modules may be " +"either 100%-pure Python, or may be extension modules written in C, or may be " +"collections of Python packages which include modules coded in both Python " +"and C." +msgstr "" + +#: ../Doc/library/distutils.rst:17 +msgid "" +"Most Python users will *not* want to use this module directly, but instead " +"use the cross-version tools maintained by the Python Packaging Authority. In " +"particular, `setuptools `__ is " +"an enhanced alternative to :mod:`distutils` that provides:" +msgstr "" + +#: ../Doc/library/distutils.rst:23 +msgid "support for declaring project dependencies" +msgstr "" + +#: ../Doc/library/distutils.rst:24 +msgid "" +"additional mechanisms for configuring which files to include in source " +"releases (including plugins for integration with version control systems)" +msgstr "" + +#: ../Doc/library/distutils.rst:26 +msgid "" +"the ability to declare project \"entry points\", which can be used as the " +"basis for application plugin systems" +msgstr "" + +#: ../Doc/library/distutils.rst:28 +msgid "" +"the ability to automatically generate Windows command line executables at " +"installation time rather than needing to prebuild them" +msgstr "" + +#: ../Doc/library/distutils.rst:30 +msgid "consistent behaviour across all supported Python versions" +msgstr "" + +#: ../Doc/library/distutils.rst:32 +msgid "" +"The recommended `pip `__ installer runs all ``setup." +"py`` scripts with ``setuptools``, even if the script itself only imports " +"``distutils``. Refer to the `Python Packaging User Guide `_ for more information." +msgstr "" + +#: ../Doc/library/distutils.rst:38 +msgid "" +"For the benefits of packaging tool authors and users seeking a deeper " +"understanding of the details of the current packaging and distribution " +"system, the legacy :mod:`distutils` based user documentation and API " +"reference remain available:" +msgstr "" + +#: ../Doc/library/distutils.rst:43 +msgid ":ref:`install-index`" +msgstr "" + +#: ../Doc/library/distutils.rst:44 +msgid ":ref:`distutils-index`" +msgstr "" + +#: ../Doc/library/doctest.rst:4 +msgid ":mod:`doctest` --- Test interactive Python examples" +msgstr "" + +#: ../Doc/library/doctest.rst:14 +msgid "**Source code:** :source:`Lib/doctest.py`" +msgstr "" + +#: ../Doc/library/doctest.rst:18 +msgid "" +"The :mod:`doctest` module searches for pieces of text that look like " +"interactive Python sessions, and then executes those sessions to verify that " +"they work exactly as shown. There are several common ways to use doctest:" +msgstr "" + +#: ../Doc/library/doctest.rst:22 +msgid "" +"To check that a module's docstrings are up-to-date by verifying that all " +"interactive examples still work as documented." +msgstr "" + +#: ../Doc/library/doctest.rst:25 +msgid "" +"To perform regression testing by verifying that interactive examples from a " +"test file or a test object work as expected." +msgstr "" + +#: ../Doc/library/doctest.rst:28 +msgid "" +"To write tutorial documentation for a package, liberally illustrated with " +"input-output examples. Depending on whether the examples or the expository " +"text are emphasized, this has the flavor of \"literate testing\" or " +"\"executable documentation\"." +msgstr "" + +#: ../Doc/library/doctest.rst:33 +msgid "Here's a complete but small example module::" +msgstr "" + +#: ../Doc/library/doctest.rst:90 +msgid "" +"If you run :file:`example.py` directly from the command line, :mod:`doctest` " +"works its magic:" +msgstr "" + +#: ../Doc/library/doctest.rst:98 +msgid "" +"There's no output! That's normal, and it means all the examples worked. " +"Pass ``-v`` to the script, and :mod:`doctest` prints a detailed log of what " +"it's trying, and prints a summary at the end:" +msgstr "" + +#: ../Doc/library/doctest.rst:116 +msgid "And so on, eventually ending with:" +msgstr "" + +#: ../Doc/library/doctest.rst:135 +msgid "" +"That's all you need to know to start making productive use of :mod:" +"`doctest`! Jump in. The following sections provide full details. Note that " +"there are many examples of doctests in the standard Python test suite and " +"libraries. Especially useful examples can be found in the standard test " +"file :file:`Lib/test/test_doctest.py`." +msgstr "" + +#: ../Doc/library/doctest.rst:145 +msgid "Simple Usage: Checking Examples in Docstrings" +msgstr "" + +#: ../Doc/library/doctest.rst:147 +msgid "" +"The simplest way to start using doctest (but not necessarily the way you'll " +"continue to do it) is to end each module :mod:`M` with::" +msgstr "" + +#: ../Doc/library/doctest.rst:154 +msgid ":mod:`doctest` then examines docstrings in module :mod:`M`." +msgstr "" + +#: ../Doc/library/doctest.rst:156 +msgid "" +"Running the module as a script causes the examples in the docstrings to get " +"executed and verified::" +msgstr "" + +#: ../Doc/library/doctest.rst:161 +msgid "" +"This won't display anything unless an example fails, in which case the " +"failing example(s) and the cause(s) of the failure(s) are printed to stdout, " +"and the final line of output is ``***Test Failed*** N failures.``, where *N* " +"is the number of examples that failed." +msgstr "" + +#: ../Doc/library/doctest.rst:166 +msgid "Run it with the ``-v`` switch instead::" +msgstr "" + +#: ../Doc/library/doctest.rst:170 +msgid "" +"and a detailed report of all examples tried is printed to standard output, " +"along with assorted summaries at the end." +msgstr "" + +#: ../Doc/library/doctest.rst:173 +msgid "" +"You can force verbose mode by passing ``verbose=True`` to :func:`testmod`, " +"or prohibit it by passing ``verbose=False``. In either of those cases, " +"``sys.argv`` is not examined by :func:`testmod` (so passing ``-v`` or not " +"has no effect)." +msgstr "" + +#: ../Doc/library/doctest.rst:178 +msgid "" +"There is also a command line shortcut for running :func:`testmod`. You can " +"instruct the Python interpreter to run the doctest module directly from the " +"standard library and pass the module name(s) on the command line::" +msgstr "" + +#: ../Doc/library/doctest.rst:184 +msgid "" +"This will import :file:`example.py` as a standalone module and run :func:" +"`testmod` on it. Note that this may not work correctly if the file is part " +"of a package and imports other submodules from that package." +msgstr "" + +#: ../Doc/library/doctest.rst:188 +msgid "" +"For more information on :func:`testmod`, see section :ref:`doctest-basic-" +"api`." +msgstr "" + +#: ../Doc/library/doctest.rst:194 +msgid "Simple Usage: Checking Examples in a Text File" +msgstr "" + +#: ../Doc/library/doctest.rst:196 +msgid "" +"Another simple application of doctest is testing interactive examples in a " +"text file. This can be done with the :func:`testfile` function::" +msgstr "" + +#: ../Doc/library/doctest.rst:202 +msgid "" +"That short script executes and verifies any interactive Python examples " +"contained in the file :file:`example.txt`. The file content is treated as " +"if it were a single giant docstring; the file doesn't need to contain a " +"Python program! For example, perhaps :file:`example.txt` contains this:" +msgstr "" + +#: ../Doc/library/doctest.rst:225 +msgid "" +"Running ``doctest.testfile(\"example.txt\")`` then finds the error in this " +"documentation::" +msgstr "" + +#: ../Doc/library/doctest.rst:236 +msgid "" +"As with :func:`testmod`, :func:`testfile` won't display anything unless an " +"example fails. If an example does fail, then the failing example(s) and the " +"cause(s) of the failure(s) are printed to stdout, using the same format as :" +"func:`testmod`." +msgstr "" + +#: ../Doc/library/doctest.rst:241 +msgid "" +"By default, :func:`testfile` looks for files in the calling module's " +"directory. See section :ref:`doctest-basic-api` for a description of the " +"optional arguments that can be used to tell it to look for files in other " +"locations." +msgstr "" + +#: ../Doc/library/doctest.rst:245 +msgid "" +"Like :func:`testmod`, :func:`testfile`'s verbosity can be set with the ``-" +"v`` command-line switch or with the optional keyword argument *verbose*." +msgstr "" + +#: ../Doc/library/doctest.rst:249 +msgid "" +"There is also a command line shortcut for running :func:`testfile`. You can " +"instruct the Python interpreter to run the doctest module directly from the " +"standard library and pass the file name(s) on the command line::" +msgstr "" + +#: ../Doc/library/doctest.rst:255 +msgid "" +"Because the file name does not end with :file:`.py`, :mod:`doctest` infers " +"that it must be run with :func:`testfile`, not :func:`testmod`." +msgstr "" + +#: ../Doc/library/doctest.rst:258 +msgid "" +"For more information on :func:`testfile`, see section :ref:`doctest-basic-" +"api`." +msgstr "" + +#: ../Doc/library/doctest.rst:264 +msgid "How It Works" +msgstr "" + +#: ../Doc/library/doctest.rst:266 +msgid "" +"This section examines in detail how doctest works: which docstrings it looks " +"at, how it finds interactive examples, what execution context it uses, how " +"it handles exceptions, and how option flags can be used to control its " +"behavior. This is the information that you need to know to write doctest " +"examples; for information about actually running doctest on these examples, " +"see the following sections." +msgstr "" + +#: ../Doc/library/doctest.rst:277 +msgid "Which Docstrings Are Examined?" +msgstr "" + +#: ../Doc/library/doctest.rst:279 +msgid "" +"The module docstring, and all function, class and method docstrings are " +"searched. Objects imported into the module are not searched." +msgstr "" + +#: ../Doc/library/doctest.rst:282 +msgid "" +"In addition, if ``M.__test__`` exists and \"is true\", it must be a dict, " +"and each entry maps a (string) name to a function object, class object, or " +"string. Function and class object docstrings found from ``M.__test__`` are " +"searched, and strings are treated as if they were docstrings. In output, a " +"key ``K`` in ``M.__test__`` appears with name ::" +msgstr "" + +#: ../Doc/library/doctest.rst:290 +msgid "" +"Any classes found are recursively searched similarly, to test docstrings in " +"their contained methods and nested classes." +msgstr "" + +#: ../Doc/library/doctest.rst:301 +msgid "How are Docstring Examples Recognized?" +msgstr "" + +#: ../Doc/library/doctest.rst:303 +msgid "" +"In most cases a copy-and-paste of an interactive console session works fine, " +"but doctest isn't trying to do an exact emulation of any specific Python " +"shell." +msgstr "" + +#: ../Doc/library/doctest.rst:324 +msgid "" +"Any expected output must immediately follow the final ``'>>> '`` or ``'... " +"'`` line containing the code, and the expected output (if any) extends to " +"the next ``'>>> '`` or all-whitespace line." +msgstr "" + +#: ../Doc/library/doctest.rst:328 +msgid "The fine print:" +msgstr "" + +#: ../Doc/library/doctest.rst:330 +msgid "" +"Expected output cannot contain an all-whitespace line, since such a line is " +"taken to signal the end of expected output. If expected output does contain " +"a blank line, put ```` in your doctest example each place a blank " +"line is expected." +msgstr "" + +#: ../Doc/library/doctest.rst:335 +msgid "" +"All hard tab characters are expanded to spaces, using 8-column tab stops. " +"Tabs in output generated by the tested code are not modified. Because any " +"hard tabs in the sample output *are* expanded, this means that if the code " +"output includes hard tabs, the only way the doctest can pass is if the :" +"const:`NORMALIZE_WHITESPACE` option or :ref:`directive ` " +"is in effect. Alternatively, the test can be rewritten to capture the output " +"and compare it to an expected value as part of the test. This handling of " +"tabs in the source was arrived at through trial and error, and has proven to " +"be the least error prone way of handling them. It is possible to use a " +"different algorithm for handling tabs by writing a custom :class:" +"`DocTestParser` class." +msgstr "" + +#: ../Doc/library/doctest.rst:347 +msgid "" +"Output to stdout is captured, but not output to stderr (exception tracebacks " +"are captured via a different means)." +msgstr "" + +#: ../Doc/library/doctest.rst:350 +msgid "" +"If you continue a line via backslashing in an interactive session, or for " +"any other reason use a backslash, you should use a raw docstring, which will " +"preserve your backslashes exactly as you type them::" +msgstr "" + +#: ../Doc/library/doctest.rst:359 +msgid "" +"Otherwise, the backslash will be interpreted as part of the string. For " +"example, the ``\\n`` above would be interpreted as a newline character. " +"Alternatively, you can double each backslash in the doctest version (and not " +"use a raw string)::" +msgstr "" + +#: ../Doc/library/doctest.rst:368 +msgid "The starting column doesn't matter::" +msgstr "" + +#: ../Doc/library/doctest.rst:375 +msgid "" +"and as many leading whitespace characters are stripped from the expected " +"output as appeared in the initial ``'>>> '`` line that started the example." +msgstr "" + +#: ../Doc/library/doctest.rst:382 +msgid "What's the Execution Context?" +msgstr "" + +#: ../Doc/library/doctest.rst:384 +msgid "" +"By default, each time :mod:`doctest` finds a docstring to test, it uses a " +"*shallow copy* of :mod:`M`'s globals, so that running tests doesn't change " +"the module's real globals, and so that one test in :mod:`M` can't leave " +"behind crumbs that accidentally allow another test to work. This means " +"examples can freely use any names defined at top-level in :mod:`M`, and " +"names defined earlier in the docstring being run. Examples cannot see names " +"defined in other docstrings." +msgstr "" + +#: ../Doc/library/doctest.rst:392 +msgid "" +"You can force use of your own dict as the execution context by passing " +"``globs=your_dict`` to :func:`testmod` or :func:`testfile` instead." +msgstr "" + +#: ../Doc/library/doctest.rst:399 +msgid "What About Exceptions?" +msgstr "" + +#: ../Doc/library/doctest.rst:401 +msgid "" +"No problem, provided that the traceback is the only output produced by the " +"example: just paste in the traceback. [#]_ Since tracebacks contain details " +"that are likely to change rapidly (for example, exact file paths and line " +"numbers), this is one case where doctest works hard to be flexible in what " +"it accepts." +msgstr "" + +#: ../Doc/library/doctest.rst:407 +msgid "Simple example::" +msgstr "" + +#: ../Doc/library/doctest.rst:414 +msgid "" +"That doctest succeeds if :exc:`ValueError` is raised, with the ``list." +"remove(x): x not in list`` detail as shown." +msgstr "" + +#: ../Doc/library/doctest.rst:417 +msgid "" +"The expected output for an exception must start with a traceback header, " +"which may be either of the following two lines, indented the same as the " +"first line of the example::" +msgstr "" + +#: ../Doc/library/doctest.rst:424 +msgid "" +"The traceback header is followed by an optional traceback stack, whose " +"contents are ignored by doctest. The traceback stack is typically omitted, " +"or copied verbatim from an interactive session." +msgstr "" + +#: ../Doc/library/doctest.rst:428 +msgid "" +"The traceback stack is followed by the most interesting part: the line(s) " +"containing the exception type and detail. This is usually the last line of " +"a traceback, but can extend across multiple lines if the exception has a " +"multi-line detail::" +msgstr "" + +#: ../Doc/library/doctest.rst:440 +msgid "" +"The last three lines (starting with :exc:`ValueError`) are compared against " +"the exception's type and detail, and the rest are ignored." +msgstr "" + +#: ../Doc/library/doctest.rst:443 +msgid "" +"Best practice is to omit the traceback stack, unless it adds significant " +"documentation value to the example. So the last example is probably better " +"as::" +msgstr "" + +#: ../Doc/library/doctest.rst:453 +msgid "" +"Note that tracebacks are treated very specially. In particular, in the " +"rewritten example, the use of ``...`` is independent of doctest's :const:" +"`ELLIPSIS` option. The ellipsis in that example could be left out, or could " +"just as well be three (or three hundred) commas or digits, or an indented " +"transcript of a Monty Python skit." +msgstr "" + +#: ../Doc/library/doctest.rst:459 +msgid "Some details you should read once, but won't need to remember:" +msgstr "" + +#: ../Doc/library/doctest.rst:461 +msgid "" +"Doctest can't guess whether your expected output came from an exception " +"traceback or from ordinary printing. So, e.g., an example that expects " +"``ValueError: 42 is prime`` will pass whether :exc:`ValueError` is actually " +"raised or if the example merely prints that traceback text. In practice, " +"ordinary output rarely begins with a traceback header line, so this doesn't " +"create real problems." +msgstr "" + +#: ../Doc/library/doctest.rst:468 +msgid "" +"Each line of the traceback stack (if present) must be indented further than " +"the first line of the example, *or* start with a non-alphanumeric character. " +"The first line following the traceback header indented the same and starting " +"with an alphanumeric is taken to be the start of the exception detail. Of " +"course this does the right thing for genuine tracebacks." +msgstr "" + +#: ../Doc/library/doctest.rst:474 +msgid "" +"When the :const:`IGNORE_EXCEPTION_DETAIL` doctest option is specified, " +"everything following the leftmost colon and any module information in the " +"exception name is ignored." +msgstr "" + +#: ../Doc/library/doctest.rst:478 +msgid "" +"The interactive shell omits the traceback header line for some :exc:" +"`SyntaxError`\\ s. But doctest uses the traceback header line to " +"distinguish exceptions from non-exceptions. So in the rare case where you " +"need to test a :exc:`SyntaxError` that omits the traceback header, you will " +"need to manually add the traceback header line to your test example." +msgstr "" + +#: ../Doc/library/doctest.rst:484 +msgid "" +"For some :exc:`SyntaxError`\\ s, Python displays the character position of " +"the syntax error, using a ``^`` marker::" +msgstr "" + +#: ../Doc/library/doctest.rst:493 +msgid "" +"Since the lines showing the position of the error come before the exception " +"type and detail, they are not checked by doctest. For example, the " +"following test would pass, even though it puts the ``^`` marker in the wrong " +"location::" +msgstr "" + +#: ../Doc/library/doctest.rst:509 +msgid "Option Flags" +msgstr "" + +#: ../Doc/library/doctest.rst:511 +msgid "" +"A number of option flags control various aspects of doctest's behavior. " +"Symbolic names for the flags are supplied as module constants, which can be " +"or'ed together and passed to various functions. The names can also be used " +"in :ref:`doctest directives `, and may be passed to the " +"doctest command line interface via the ``-o`` option." +msgstr "" + +#: ../Doc/library/doctest.rst:517 +msgid "The ``-o`` command line option." +msgstr "" + +#: ../Doc/library/doctest.rst:520 +msgid "" +"The first group of options define test semantics, controlling aspects of how " +"doctest decides whether actual output matches an example's expected output:" +msgstr "" + +#: ../Doc/library/doctest.rst:526 +msgid "" +"By default, if an expected output block contains just ``1``, an actual " +"output block containing just ``1`` or just ``True`` is considered to be a " +"match, and similarly for ``0`` versus ``False``. When :const:" +"`DONT_ACCEPT_TRUE_FOR_1` is specified, neither substitution is allowed. The " +"default behavior caters to that Python changed the return type of many " +"functions from integer to boolean; doctests expecting \"little integer\" " +"output still work in these cases. This option will probably go away, but " +"not for several years." +msgstr "" + +#: ../Doc/library/doctest.rst:537 +msgid "" +"By default, if an expected output block contains a line containing only the " +"string ````, then that line will match a blank line in the actual " +"output. Because a genuinely blank line delimits the expected output, this " +"is the only way to communicate that a blank line is expected. When :const:" +"`DONT_ACCEPT_BLANKLINE` is specified, this substitution is not allowed." +msgstr "" + +#: ../Doc/library/doctest.rst:546 +msgid "" +"When specified, all sequences of whitespace (blanks and newlines) are " +"treated as equal. Any sequence of whitespace within the expected output " +"will match any sequence of whitespace within the actual output. By default, " +"whitespace must match exactly. :const:`NORMALIZE_WHITESPACE` is especially " +"useful when a line of expected output is very long, and you want to wrap it " +"across multiple lines in your source." +msgstr "" + +#: ../Doc/library/doctest.rst:556 +msgid "" +"When specified, an ellipsis marker (``...``) in the expected output can " +"match any substring in the actual output. This includes substrings that " +"span line boundaries, and empty substrings, so it's best to keep usage of " +"this simple. Complicated uses can lead to the same kinds of \"oops, it " +"matched too much!\" surprises that ``.*`` is prone to in regular expressions." +msgstr "" + +#: ../Doc/library/doctest.rst:565 +msgid "" +"When specified, an example that expects an exception passes if an exception " +"of the expected type is raised, even if the exception detail does not " +"match. For example, an example expecting ``ValueError: 42`` will pass if " +"the actual exception raised is ``ValueError: 3*14``, but will fail, e.g., " +"if :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/doctest.rst:571 +msgid "" +"It will also ignore the module name used in Python 3 doctest reports. Hence " +"both of these variations will work with the flag specified, regardless of " +"whether the test is run under Python 2.7 or Python 3.2 (or later versions)::" +msgstr "" + +#: ../Doc/library/doctest.rst:583 +msgid "" +"Note that :const:`ELLIPSIS` can also be used to ignore the details of the " +"exception message, but such a test may still fail based on whether or not " +"the module details are printed as part of the exception name. Using :const:" +"`IGNORE_EXCEPTION_DETAIL` and the details from Python 2.3 is also the only " +"clear way to write a doctest that doesn't care about the exception detail " +"yet continues to pass under Python 2.3 or earlier (those releases do not " +"support :ref:`doctest directives ` and ignore them as " +"irrelevant comments). For example::" +msgstr "" + +#: ../Doc/library/doctest.rst:597 +msgid "" +"passes under Python 2.3 and later Python versions with the flag specified, " +"even though the detail changed in Python 2.4 to say \"does not\" instead of " +"\"doesn't\"." +msgstr "" + +#: ../Doc/library/doctest.rst:601 +msgid "" +":const:`IGNORE_EXCEPTION_DETAIL` now also ignores any information relating " +"to the module containing the exception under test." +msgstr "" + +#: ../Doc/library/doctest.rst:608 +msgid "" +"When specified, do not run the example at all. This can be useful in " +"contexts where doctest examples serve as both documentation and test cases, " +"and an example should be included for documentation purposes, but should not " +"be checked. E.g., the example's output might be random; or the example " +"might depend on resources which would be unavailable to the test driver." +msgstr "" + +#: ../Doc/library/doctest.rst:614 +msgid "" +"The SKIP flag can also be used for temporarily \"commenting out\" examples." +msgstr "" + +#: ../Doc/library/doctest.rst:619 +msgid "A bitmask or'ing together all the comparison flags above." +msgstr "" + +#: ../Doc/library/doctest.rst:621 +msgid "The second group of options controls how test failures are reported:" +msgstr "" + +#: ../Doc/library/doctest.rst:626 +msgid "" +"When specified, failures that involve multi-line expected and actual outputs " +"are displayed using a unified diff." +msgstr "" + +#: ../Doc/library/doctest.rst:632 +msgid "" +"When specified, failures that involve multi-line expected and actual outputs " +"will be displayed using a context diff." +msgstr "" + +#: ../Doc/library/doctest.rst:638 +msgid "" +"When specified, differences are computed by ``difflib.Differ``, using the " +"same algorithm as the popular :file:`ndiff.py` utility. This is the only " +"method that marks differences within lines as well as across lines. For " +"example, if a line of expected output contains digit ``1`` where actual " +"output contains letter ``l``, a line is inserted with a caret marking the " +"mismatching column positions." +msgstr "" + +#: ../Doc/library/doctest.rst:647 +msgid "" +"When specified, display the first failing example in each doctest, but " +"suppress output for all remaining examples. This will prevent doctest from " +"reporting correct examples that break because of earlier failures; but it " +"might also hide incorrect examples that fail independently of the first " +"failure. When :const:`REPORT_ONLY_FIRST_FAILURE` is specified, the " +"remaining examples are still run, and still count towards the total number " +"of failures reported; only the output is suppressed." +msgstr "" + +#: ../Doc/library/doctest.rst:658 +msgid "" +"When specified, exit after the first failing example and don't attempt to " +"run the remaining examples. Thus, the number of failures reported will be at " +"most 1. This flag may be useful during debugging, since examples after the " +"first failure won't even produce debugging output." +msgstr "" + +#: ../Doc/library/doctest.rst:663 +msgid "" +"The doctest command line accepts the option ``-f`` as a shorthand for ``-o " +"FAIL_FAST``." +msgstr "" + +#: ../Doc/library/doctest.rst:671 +msgid "A bitmask or'ing together all the reporting flags above." +msgstr "" + +#: ../Doc/library/doctest.rst:674 +msgid "" +"There is also a way to register new option flag names, though this isn't " +"useful unless you intend to extend :mod:`doctest` internals via subclassing:" +msgstr "" + +#: ../Doc/library/doctest.rst:680 +msgid "" +"Create a new option flag with a given name, and return the new flag's " +"integer value. :func:`register_optionflag` can be used when subclassing :" +"class:`OutputChecker` or :class:`DocTestRunner` to create new options that " +"are supported by your subclasses. :func:`register_optionflag` should always " +"be called using the following idiom::" +msgstr "" + +#: ../Doc/library/doctest.rst:692 +msgid "Directives" +msgstr "" + +#: ../Doc/library/doctest.rst:694 +msgid "" +"Doctest directives may be used to modify the :ref:`option flags ` for an individual example. Doctest directives are special Python " +"comments following an example's source code:" +msgstr "" + +#: ../Doc/library/doctest.rst:705 +msgid "" +"Whitespace is not allowed between the ``+`` or ``-`` and the directive " +"option name. The directive option name can be any of the option flag names " +"explained above." +msgstr "" + +#: ../Doc/library/doctest.rst:709 +msgid "" +"An example's doctest directives modify doctest's behavior for that single " +"example. Use ``+`` to enable the named behavior, or ``-`` to disable it." +msgstr "" + +#: ../Doc/library/doctest.rst:712 +msgid "For example, this test passes::" +msgstr "" + +#: ../Doc/library/doctest.rst:718 +msgid "" +"Without the directive it would fail, both because the actual output doesn't " +"have two blanks before the single-digit list elements, and because the " +"actual output is on a single line. This test also passes, and also requires " +"a directive to do so::" +msgstr "" + +#: ../Doc/library/doctest.rst:726 +msgid "" +"Multiple directives can be used on a single physical line, separated by " +"commas::" +msgstr "" + +#: ../Doc/library/doctest.rst:732 +msgid "" +"If multiple directive comments are used for a single example, then they are " +"combined::" +msgstr "" + +#: ../Doc/library/doctest.rst:739 +msgid "" +"As the previous example shows, you can add ``...`` lines to your example " +"containing only directives. This can be useful when an example is too long " +"for a directive to comfortably fit on the same line::" +msgstr "" + +#: ../Doc/library/doctest.rst:747 +msgid "" +"Note that since all options are disabled by default, and directives apply " +"only to the example they appear in, enabling options (via ``+`` in a " +"directive) is usually the only meaningful choice. However, option flags can " +"also be passed to functions that run doctests, establishing different " +"defaults. In such cases, disabling an option via ``-`` in a directive can " +"be useful." +msgstr "" + +#: ../Doc/library/doctest.rst:757 ../Doc/library/exceptions.rst:668 +msgid "Warnings" +msgstr "" + +#: ../Doc/library/doctest.rst:759 +msgid "" +":mod:`doctest` is serious about requiring exact matches in expected output. " +"If even a single character doesn't match, the test fails. This will " +"probably surprise you a few times, as you learn exactly what Python does and " +"doesn't guarantee about output. For example, when printing a dict, Python " +"doesn't guarantee that the key-value pairs will be printed in any particular " +"order, so a test like ::" +msgstr "" + +#: ../Doc/library/doctest.rst:769 +msgid "is vulnerable! One workaround is to do ::" +msgstr "" + +#: ../Doc/library/doctest.rst:774 +msgid "instead. Another is to do ::" +msgstr "" + +#: ../Doc/library/doctest.rst:780 +msgid "There are others, but you get the idea." +msgstr "" + +#: ../Doc/library/doctest.rst:782 +msgid "" +"Another bad idea is to print things that embed an object address, like ::" +msgstr "" + +#: ../Doc/library/doctest.rst:790 +msgid "" +"The :const:`ELLIPSIS` directive gives a nice approach for the last example::" +msgstr "" + +#: ../Doc/library/doctest.rst:795 +msgid "" +"Floating-point numbers are also subject to small output variations across " +"platforms, because Python defers to the platform C library for float " +"formatting, and C libraries vary widely in quality here. ::" +msgstr "" + +#: ../Doc/library/doctest.rst:806 +msgid "" +"Numbers of the form ``I/2.**J`` are safe across all platforms, and I often " +"contrive doctest examples to produce numbers of that form::" +msgstr "" + +#: ../Doc/library/doctest.rst:812 +msgid "" +"Simple fractions are also easier for people to understand, and that makes " +"for better documentation." +msgstr "" + +#: ../Doc/library/doctest.rst:819 +msgid "Basic API" +msgstr "" + +#: ../Doc/library/doctest.rst:821 +msgid "" +"The functions :func:`testmod` and :func:`testfile` provide a simple " +"interface to doctest that should be sufficient for most basic uses. For a " +"less formal introduction to these two functions, see sections :ref:`doctest-" +"simple-testmod` and :ref:`doctest-simple-testfile`." +msgstr "" + +#: ../Doc/library/doctest.rst:829 +msgid "" +"All arguments except *filename* are optional, and should be specified in " +"keyword form." +msgstr "" + +#: ../Doc/library/doctest.rst:832 +msgid "" +"Test examples in the file named *filename*. Return ``(failure_count, " +"test_count)``." +msgstr "" + +#: ../Doc/library/doctest.rst:835 +msgid "" +"Optional argument *module_relative* specifies how the filename should be " +"interpreted:" +msgstr "" + +#: ../Doc/library/doctest.rst:838 +msgid "" +"If *module_relative* is ``True`` (the default), then *filename* specifies an " +"OS-independent module-relative path. By default, this path is relative to " +"the calling module's directory; but if the *package* argument is specified, " +"then it is relative to that package. To ensure OS-independence, *filename* " +"should use ``/`` characters to separate path segments, and may not be an " +"absolute path (i.e., it may not begin with ``/``)." +msgstr "" + +#: ../Doc/library/doctest.rst:845 +msgid "" +"If *module_relative* is ``False``, then *filename* specifies an OS-specific " +"path. The path may be absolute or relative; relative paths are resolved " +"with respect to the current working directory." +msgstr "" + +#: ../Doc/library/doctest.rst:849 +msgid "" +"Optional argument *name* gives the name of the test; by default, or if " +"``None``, ``os.path.basename(filename)`` is used." +msgstr "" + +#: ../Doc/library/doctest.rst:852 +msgid "" +"Optional argument *package* is a Python package or the name of a Python " +"package whose directory should be used as the base directory for a module-" +"relative filename. If no package is specified, then the calling module's " +"directory is used as the base directory for module-relative filenames. It " +"is an error to specify *package* if *module_relative* is ``False``." +msgstr "" + +#: ../Doc/library/doctest.rst:858 +msgid "" +"Optional argument *globs* gives a dict to be used as the globals when " +"executing examples. A new shallow copy of this dict is created for the " +"doctest, so its examples start with a clean slate. By default, or if " +"``None``, a new empty dict is used." +msgstr "" + +#: ../Doc/library/doctest.rst:863 +msgid "" +"Optional argument *extraglobs* gives a dict merged into the globals used to " +"execute examples. This works like :meth:`dict.update`: if *globs* and " +"*extraglobs* have a common key, the associated value in *extraglobs* appears " +"in the combined dict. By default, or if ``None``, no extra globals are " +"used. This is an advanced feature that allows parameterization of " +"doctests. For example, a doctest can be written for a base class, using a " +"generic name for the class, then reused to test any number of subclasses by " +"passing an *extraglobs* dict mapping the generic name to the subclass to be " +"tested." +msgstr "" + +#: ../Doc/library/doctest.rst:872 +msgid "" +"Optional argument *verbose* prints lots of stuff if true, and prints only " +"failures if false; by default, or if ``None``, it's true if and only if ``'-" +"v'`` is in ``sys.argv``." +msgstr "" + +#: ../Doc/library/doctest.rst:876 +msgid "" +"Optional argument *report* prints a summary at the end when true, else " +"prints nothing at the end. In verbose mode, the summary is detailed, else " +"the summary is very brief (in fact, empty if all tests passed)." +msgstr "" + +#: ../Doc/library/doctest.rst:880 +msgid "" +"Optional argument *optionflags* (default value 0) takes the bitwise-or of " +"option flags. See section :ref:`doctest-options`." +msgstr "" + +#: ../Doc/library/doctest.rst:883 +msgid "" +"Optional argument *raise_on_error* defaults to false. If true, an exception " +"is raised upon the first failure or unexpected exception in an example. " +"This allows failures to be post-mortem debugged. Default behavior is to " +"continue running examples." +msgstr "" + +#: ../Doc/library/doctest.rst:888 ../Doc/library/doctest.rst:1028 +msgid "" +"Optional argument *parser* specifies a :class:`DocTestParser` (or subclass) " +"that should be used to extract tests from the files. It defaults to a " +"normal parser (i.e., ``DocTestParser()``)." +msgstr "" + +#: ../Doc/library/doctest.rst:892 ../Doc/library/doctest.rst:1032 +msgid "" +"Optional argument *encoding* specifies an encoding that should be used to " +"convert the file to unicode." +msgstr "" + +#: ../Doc/library/doctest.rst:898 +msgid "" +"All arguments are optional, and all except for *m* should be specified in " +"keyword form." +msgstr "" + +#: ../Doc/library/doctest.rst:901 +msgid "" +"Test examples in docstrings in functions and classes reachable from module " +"*m* (or module :mod:`__main__` if *m* is not supplied or is ``None``), " +"starting with ``m.__doc__``." +msgstr "" + +#: ../Doc/library/doctest.rst:905 +msgid "" +"Also test examples reachable from dict ``m.__test__``, if it exists and is " +"not ``None``. ``m.__test__`` maps names (strings) to functions, classes and " +"strings; function and class docstrings are searched for examples; strings " +"are searched directly, as if they were docstrings." +msgstr "" + +#: ../Doc/library/doctest.rst:910 +msgid "" +"Only docstrings attached to objects belonging to module *m* are searched." +msgstr "" + +#: ../Doc/library/doctest.rst:912 +msgid "Return ``(failure_count, test_count)``." +msgstr "" + +#: ../Doc/library/doctest.rst:914 +msgid "" +"Optional argument *name* gives the name of the module; by default, or if " +"``None``, ``m.__name__`` is used." +msgstr "" + +#: ../Doc/library/doctest.rst:917 +msgid "" +"Optional argument *exclude_empty* defaults to false. If true, objects for " +"which no doctests are found are excluded from consideration. The default is " +"a backward compatibility hack, so that code still using :meth:`doctest." +"master.summarize` in conjunction with :func:`testmod` continues to get " +"output for objects with no tests. The *exclude_empty* argument to the newer :" +"class:`DocTestFinder` constructor defaults to true." +msgstr "" + +#: ../Doc/library/doctest.rst:924 +msgid "" +"Optional arguments *extraglobs*, *verbose*, *report*, *optionflags*, " +"*raise_on_error*, and *globs* are the same as for function :func:`testfile` " +"above, except that *globs* defaults to ``m.__dict__``." +msgstr "" + +#: ../Doc/library/doctest.rst:931 +msgid "" +"Test examples associated with object *f*; for example, *f* may be a string, " +"a module, a function, or a class object." +msgstr "" + +#: ../Doc/library/doctest.rst:934 +msgid "" +"A shallow copy of dictionary argument *globs* is used for the execution " +"context." +msgstr "" + +#: ../Doc/library/doctest.rst:936 +msgid "" +"Optional argument *name* is used in failure messages, and defaults to ``" +"\"NoName\"``." +msgstr "" + +#: ../Doc/library/doctest.rst:939 +msgid "" +"If optional argument *verbose* is true, output is generated even if there " +"are no failures. By default, output is generated only in case of an example " +"failure." +msgstr "" + +#: ../Doc/library/doctest.rst:942 +msgid "" +"Optional argument *compileflags* gives the set of flags that should be used " +"by the Python compiler when running the examples. By default, or if " +"``None``, flags are deduced corresponding to the set of future features " +"found in *globs*." +msgstr "" + +#: ../Doc/library/doctest.rst:946 +msgid "" +"Optional argument *optionflags* works as for function :func:`testfile` above." +msgstr "" + +#: ../Doc/library/doctest.rst:952 +msgid "Unittest API" +msgstr "" + +#: ../Doc/library/doctest.rst:954 +msgid "" +"As your collection of doctest'ed modules grows, you'll want a way to run all " +"their doctests systematically. :mod:`doctest` provides two functions that " +"can be used to create :mod:`unittest` test suites from modules and text " +"files containing doctests. To integrate with :mod:`unittest` test " +"discovery, include a :func:`load_tests` function in your test module::" +msgstr "" + +#: ../Doc/library/doctest.rst:968 +msgid "" +"There are two main functions for creating :class:`unittest.TestSuite` " +"instances from text files and modules with doctests:" +msgstr "" + +#: ../Doc/library/doctest.rst:974 +msgid "" +"Convert doctest tests from one or more text files to a :class:`unittest." +"TestSuite`." +msgstr "" + +#: ../Doc/library/doctest.rst:977 +msgid "" +"The returned :class:`unittest.TestSuite` is to be run by the unittest " +"framework and runs the interactive examples in each file. If an example in " +"any file fails, then the synthesized unit test fails, and a :exc:" +"`failureException` exception is raised showing the name of the file " +"containing the test and a (sometimes approximate) line number." +msgstr "" + +#: ../Doc/library/doctest.rst:983 +msgid "Pass one or more paths (as strings) to text files to be examined." +msgstr "" + +#: ../Doc/library/doctest.rst:985 +msgid "Options may be provided as keyword arguments:" +msgstr "" + +#: ../Doc/library/doctest.rst:987 +msgid "" +"Optional argument *module_relative* specifies how the filenames in *paths* " +"should be interpreted:" +msgstr "" + +#: ../Doc/library/doctest.rst:990 +msgid "" +"If *module_relative* is ``True`` (the default), then each filename in " +"*paths* specifies an OS-independent module-relative path. By default, this " +"path is relative to the calling module's directory; but if the *package* " +"argument is specified, then it is relative to that package. To ensure OS-" +"independence, each filename should use ``/`` characters to separate path " +"segments, and may not be an absolute path (i.e., it may not begin with ``/" +"``)." +msgstr "" + +#: ../Doc/library/doctest.rst:998 +msgid "" +"If *module_relative* is ``False``, then each filename in *paths* specifies " +"an OS-specific path. The path may be absolute or relative; relative paths " +"are resolved with respect to the current working directory." +msgstr "" + +#: ../Doc/library/doctest.rst:1002 +msgid "" +"Optional argument *package* is a Python package or the name of a Python " +"package whose directory should be used as the base directory for module-" +"relative filenames in *paths*. If no package is specified, then the calling " +"module's directory is used as the base directory for module-relative " +"filenames. It is an error to specify *package* if *module_relative* is " +"``False``." +msgstr "" + +#: ../Doc/library/doctest.rst:1009 +msgid "" +"Optional argument *setUp* specifies a set-up function for the test suite. " +"This is called before running the tests in each file. The *setUp* function " +"will be passed a :class:`DocTest` object. The setUp function can access the " +"test globals as the *globs* attribute of the test passed." +msgstr "" + +#: ../Doc/library/doctest.rst:1014 +msgid "" +"Optional argument *tearDown* specifies a tear-down function for the test " +"suite. This is called after running the tests in each file. The *tearDown* " +"function will be passed a :class:`DocTest` object. The setUp function can " +"access the test globals as the *globs* attribute of the test passed." +msgstr "" + +#: ../Doc/library/doctest.rst:1019 ../Doc/library/doctest.rst:1053 +msgid "" +"Optional argument *globs* is a dictionary containing the initial global " +"variables for the tests. A new copy of this dictionary is created for each " +"test. By default, *globs* is a new empty dictionary." +msgstr "" + +#: ../Doc/library/doctest.rst:1023 +msgid "" +"Optional argument *optionflags* specifies the default doctest options for " +"the tests, created by or-ing together individual option flags. See section :" +"ref:`doctest-options`. See function :func:`set_unittest_reportflags` below " +"for a better way to set reporting options." +msgstr "" + +#: ../Doc/library/doctest.rst:1035 +msgid "" +"The global ``__file__`` is added to the globals provided to doctests loaded " +"from a text file using :func:`DocFileSuite`." +msgstr "" + +#: ../Doc/library/doctest.rst:1041 +msgid "Convert doctest tests for a module to a :class:`unittest.TestSuite`." +msgstr "" + +#: ../Doc/library/doctest.rst:1043 +msgid "" +"The returned :class:`unittest.TestSuite` is to be run by the unittest " +"framework and runs each doctest in the module. If any of the doctests fail, " +"then the synthesized unit test fails, and a :exc:`failureException` " +"exception is raised showing the name of the file containing the test and a " +"(sometimes approximate) line number." +msgstr "" + +#: ../Doc/library/doctest.rst:1049 +msgid "" +"Optional argument *module* provides the module to be tested. It can be a " +"module object or a (possibly dotted) module name. If not specified, the " +"module calling this function is used." +msgstr "" + +#: ../Doc/library/doctest.rst:1057 +msgid "" +"Optional argument *extraglobs* specifies an extra set of global variables, " +"which is merged into *globs*. By default, no extra globals are used." +msgstr "" + +#: ../Doc/library/doctest.rst:1060 +msgid "" +"Optional argument *test_finder* is the :class:`DocTestFinder` object (or a " +"drop-in replacement) that is used to extract doctests from the module." +msgstr "" + +#: ../Doc/library/doctest.rst:1063 +msgid "" +"Optional arguments *setUp*, *tearDown*, and *optionflags* are the same as " +"for function :func:`DocFileSuite` above." +msgstr "" + +#: ../Doc/library/doctest.rst:1066 +msgid "This function uses the same search technique as :func:`testmod`." +msgstr "" + +#: ../Doc/library/doctest.rst:1068 +msgid "" +":func:`DocTestSuite` returns an empty :class:`unittest.TestSuite` if " +"*module* contains no docstrings instead of raising :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/doctest.rst:1073 +msgid "" +"Under the covers, :func:`DocTestSuite` creates a :class:`unittest.TestSuite` " +"out of :class:`doctest.DocTestCase` instances, and :class:`DocTestCase` is a " +"subclass of :class:`unittest.TestCase`. :class:`DocTestCase` isn't " +"documented here (it's an internal detail), but studying its code can answer " +"questions about the exact details of :mod:`unittest` integration." +msgstr "" + +#: ../Doc/library/doctest.rst:1079 +msgid "" +"Similarly, :func:`DocFileSuite` creates a :class:`unittest.TestSuite` out " +"of :class:`doctest.DocFileCase` instances, and :class:`DocFileCase` is a " +"subclass of :class:`DocTestCase`." +msgstr "" + +#: ../Doc/library/doctest.rst:1083 +msgid "" +"So both ways of creating a :class:`unittest.TestSuite` run instances of :" +"class:`DocTestCase`. This is important for a subtle reason: when you run :" +"mod:`doctest` functions yourself, you can control the :mod:`doctest` options " +"in use directly, by passing option flags to :mod:`doctest` functions. " +"However, if you're writing a :mod:`unittest` framework, :mod:`unittest` " +"ultimately controls when and how tests get run. The framework author " +"typically wants to control :mod:`doctest` reporting options (perhaps, e.g., " +"specified by command line options), but there's no way to pass options " +"through :mod:`unittest` to :mod:`doctest` test runners." +msgstr "" + +#: ../Doc/library/doctest.rst:1093 +msgid "" +"For this reason, :mod:`doctest` also supports a notion of :mod:`doctest` " +"reporting flags specific to :mod:`unittest` support, via this function:" +msgstr "" + +#: ../Doc/library/doctest.rst:1099 +msgid "Set the :mod:`doctest` reporting flags to use." +msgstr "" + +#: ../Doc/library/doctest.rst:1101 +msgid "" +"Argument *flags* takes the bitwise-or of option flags. See section :ref:" +"`doctest-options`. Only \"reporting flags\" can be used." +msgstr "" + +#: ../Doc/library/doctest.rst:1104 +msgid "" +"This is a module-global setting, and affects all future doctests run by " +"module :mod:`unittest`: the :meth:`runTest` method of :class:`DocTestCase` " +"looks at the option flags specified for the test case when the :class:" +"`DocTestCase` instance was constructed. If no reporting flags were " +"specified (which is the typical and expected case), :mod:`doctest`'s :mod:" +"`unittest` reporting flags are or'ed into the option flags, and the option " +"flags so augmented are passed to the :class:`DocTestRunner` instance created " +"to run the doctest. If any reporting flags were specified when the :class:" +"`DocTestCase` instance was constructed, :mod:`doctest`'s :mod:`unittest` " +"reporting flags are ignored." +msgstr "" + +#: ../Doc/library/doctest.rst:1114 +msgid "" +"The value of the :mod:`unittest` reporting flags in effect before the " +"function was called is returned by the function." +msgstr "" + +#: ../Doc/library/doctest.rst:1121 +msgid "Advanced API" +msgstr "" + +#: ../Doc/library/doctest.rst:1123 +msgid "" +"The basic API is a simple wrapper that's intended to make doctest easy to " +"use. It is fairly flexible, and should meet most users' needs; however, if " +"you require more fine-grained control over testing, or wish to extend " +"doctest's capabilities, then you should use the advanced API." +msgstr "" + +#: ../Doc/library/doctest.rst:1128 +msgid "" +"The advanced API revolves around two container classes, which are used to " +"store the interactive examples extracted from doctest cases:" +msgstr "" + +#: ../Doc/library/doctest.rst:1131 +msgid "" +":class:`Example`: A single Python :term:`statement`, paired with its " +"expected output." +msgstr "" + +#: ../Doc/library/doctest.rst:1134 +msgid "" +":class:`DocTest`: A collection of :class:`Example`\\ s, typically extracted " +"from a single docstring or text file." +msgstr "" + +#: ../Doc/library/doctest.rst:1137 +msgid "" +"Additional processing classes are defined to find, parse, and run, and check " +"doctest examples:" +msgstr "" + +#: ../Doc/library/doctest.rst:1140 +msgid "" +":class:`DocTestFinder`: Finds all docstrings in a given module, and uses a :" +"class:`DocTestParser` to create a :class:`DocTest` from every docstring that " +"contains interactive examples." +msgstr "" + +#: ../Doc/library/doctest.rst:1144 +msgid "" +":class:`DocTestParser`: Creates a :class:`DocTest` object from a string " +"(such as an object's docstring)." +msgstr "" + +#: ../Doc/library/doctest.rst:1147 +msgid "" +":class:`DocTestRunner`: Executes the examples in a :class:`DocTest`, and " +"uses an :class:`OutputChecker` to verify their output." +msgstr "" + +#: ../Doc/library/doctest.rst:1150 +msgid "" +":class:`OutputChecker`: Compares the actual output from a doctest example " +"with the expected output, and decides whether they match." +msgstr "" + +#: ../Doc/library/doctest.rst:1153 +msgid "" +"The relationships among these processing classes are summarized in the " +"following diagram::" +msgstr "" + +#: ../Doc/library/doctest.rst:1169 +msgid "DocTest Objects" +msgstr "" + +#: ../Doc/library/doctest.rst:1174 +msgid "" +"A collection of doctest examples that should be run in a single namespace. " +"The constructor arguments are used to initialize the attributes of the same " +"names." +msgstr "" + +#: ../Doc/library/doctest.rst:1178 +msgid "" +":class:`DocTest` defines the following attributes. They are initialized by " +"the constructor, and should not be modified directly." +msgstr "" + +#: ../Doc/library/doctest.rst:1184 +msgid "" +"A list of :class:`Example` objects encoding the individual interactive " +"Python examples that should be run by this test." +msgstr "" + +#: ../Doc/library/doctest.rst:1190 +msgid "" +"The namespace (aka globals) that the examples should be run in. This is a " +"dictionary mapping names to values. Any changes to the namespace made by " +"the examples (such as binding new variables) will be reflected in :attr:" +"`globs` after the test is run." +msgstr "" + +#: ../Doc/library/doctest.rst:1198 +msgid "" +"A string name identifying the :class:`DocTest`. Typically, this is the name " +"of the object or file that the test was extracted from." +msgstr "" + +#: ../Doc/library/doctest.rst:1204 +msgid "" +"The name of the file that this :class:`DocTest` was extracted from; or " +"``None`` if the filename is unknown, or if the :class:`DocTest` was not " +"extracted from a file." +msgstr "" + +#: ../Doc/library/doctest.rst:1211 +msgid "" +"The line number within :attr:`filename` where this :class:`DocTest` begins, " +"or ``None`` if the line number is unavailable. This line number is zero-" +"based with respect to the beginning of the file." +msgstr "" + +#: ../Doc/library/doctest.rst:1218 +msgid "" +"The string that the test was extracted from, or 'None' if the string is " +"unavailable, or if the test was not extracted from a string." +msgstr "" + +#: ../Doc/library/doctest.rst:1225 +msgid "Example Objects" +msgstr "" + +#: ../Doc/library/doctest.rst:1230 +msgid "" +"A single interactive example, consisting of a Python statement and its " +"expected output. The constructor arguments are used to initialize the " +"attributes of the same names." +msgstr "" + +#: ../Doc/library/doctest.rst:1235 +msgid "" +":class:`Example` defines the following attributes. They are initialized by " +"the constructor, and should not be modified directly." +msgstr "" + +#: ../Doc/library/doctest.rst:1241 +msgid "" +"A string containing the example's source code. This source code consists of " +"a single Python statement, and always ends with a newline; the constructor " +"adds a newline when necessary." +msgstr "" + +#: ../Doc/library/doctest.rst:1248 +msgid "" +"The expected output from running the example's source code (either from " +"stdout, or a traceback in case of exception). :attr:`want` ends with a " +"newline unless no output is expected, in which case it's an empty string. " +"The constructor adds a newline when necessary." +msgstr "" + +#: ../Doc/library/doctest.rst:1256 +msgid "" +"The exception message generated by the example, if the example is expected " +"to generate an exception; or ``None`` if it is not expected to generate an " +"exception. This exception message is compared against the return value of :" +"func:`traceback.format_exception_only`. :attr:`exc_msg` ends with a newline " +"unless it's ``None``. The constructor adds a newline if needed." +msgstr "" + +#: ../Doc/library/doctest.rst:1265 +msgid "" +"The line number within the string containing this example where the example " +"begins. This line number is zero-based with respect to the beginning of the " +"containing string." +msgstr "" + +#: ../Doc/library/doctest.rst:1272 +msgid "" +"The example's indentation in the containing string, i.e., the number of " +"space characters that precede the example's first prompt." +msgstr "" + +#: ../Doc/library/doctest.rst:1278 +msgid "" +"A dictionary mapping from option flags to ``True`` or ``False``, which is " +"used to override default options for this example. Any option flags not " +"contained in this dictionary are left at their default value (as specified " +"by the :class:`DocTestRunner`'s :attr:`optionflags`). By default, no options " +"are set." +msgstr "" + +#: ../Doc/library/doctest.rst:1287 +msgid "DocTestFinder objects" +msgstr "" + +#: ../Doc/library/doctest.rst:1292 +msgid "" +"A processing class used to extract the :class:`DocTest`\\ s that are " +"relevant to a given object, from its docstring and the docstrings of its " +"contained objects. :class:`DocTest`\\ s can be extracted from modules, " +"classes, functions, methods, staticmethods, classmethods, and properties." +msgstr "" + +#: ../Doc/library/doctest.rst:1297 +msgid "" +"The optional argument *verbose* can be used to display the objects searched " +"by the finder. It defaults to ``False`` (no output)." +msgstr "" + +#: ../Doc/library/doctest.rst:1300 +msgid "" +"The optional argument *parser* specifies the :class:`DocTestParser` object " +"(or a drop-in replacement) that is used to extract doctests from docstrings." +msgstr "" + +#: ../Doc/library/doctest.rst:1303 +msgid "" +"If the optional argument *recurse* is false, then :meth:`DocTestFinder.find` " +"will only examine the given object, and not any contained objects." +msgstr "" + +#: ../Doc/library/doctest.rst:1306 +msgid "" +"If the optional argument *exclude_empty* is false, then :meth:`DocTestFinder." +"find` will include tests for objects with empty docstrings." +msgstr "" + +#: ../Doc/library/doctest.rst:1310 +msgid ":class:`DocTestFinder` defines the following method:" +msgstr "" + +#: ../Doc/library/doctest.rst:1315 +msgid "" +"Return a list of the :class:`DocTest`\\ s that are defined by *obj*'s " +"docstring, or by any of its contained objects' docstrings." +msgstr "" + +#: ../Doc/library/doctest.rst:1318 +msgid "" +"The optional argument *name* specifies the object's name; this name will be " +"used to construct names for the returned :class:`DocTest`\\ s. If *name* is " +"not specified, then ``obj.__name__`` is used." +msgstr "" + +#: ../Doc/library/doctest.rst:1322 +msgid "" +"The optional parameter *module* is the module that contains the given " +"object. If the module is not specified or is None, then the test finder will " +"attempt to automatically determine the correct module. The object's module " +"is used:" +msgstr "" + +#: ../Doc/library/doctest.rst:1326 +msgid "As a default namespace, if *globs* is not specified." +msgstr "" + +#: ../Doc/library/doctest.rst:1328 +msgid "" +"To prevent the DocTestFinder from extracting DocTests from objects that are " +"imported from other modules. (Contained objects with modules other than " +"*module* are ignored.)" +msgstr "" + +#: ../Doc/library/doctest.rst:1332 +msgid "To find the name of the file containing the object." +msgstr "" + +#: ../Doc/library/doctest.rst:1334 +msgid "To help find the line number of the object within its file." +msgstr "" + +#: ../Doc/library/doctest.rst:1336 +msgid "" +"If *module* is ``False``, no attempt to find the module will be made. This " +"is obscure, of use mostly in testing doctest itself: if *module* is " +"``False``, or is ``None`` but cannot be found automatically, then all " +"objects are considered to belong to the (non-existent) module, so all " +"contained objects will (recursively) be searched for doctests." +msgstr "" + +#: ../Doc/library/doctest.rst:1342 +msgid "" +"The globals for each :class:`DocTest` is formed by combining *globs* and " +"*extraglobs* (bindings in *extraglobs* override bindings in *globs*). A new " +"shallow copy of the globals dictionary is created for each :class:`DocTest`. " +"If *globs* is not specified, then it defaults to the module's *__dict__*, if " +"specified, or ``{}`` otherwise. If *extraglobs* is not specified, then it " +"defaults to ``{}``." +msgstr "" + +#: ../Doc/library/doctest.rst:1353 +msgid "DocTestParser objects" +msgstr "" + +#: ../Doc/library/doctest.rst:1358 +msgid "" +"A processing class used to extract interactive examples from a string, and " +"use them to create a :class:`DocTest` object." +msgstr "" + +#: ../Doc/library/doctest.rst:1362 ../Doc/library/doctest.rst:1430 +msgid ":class:`DocTestParser` defines the following methods:" +msgstr "" + +#: ../Doc/library/doctest.rst:1367 +msgid "" +"Extract all doctest examples from the given string, and collect them into a :" +"class:`DocTest` object." +msgstr "" + +#: ../Doc/library/doctest.rst:1370 +msgid "" +"*globs*, *name*, *filename*, and *lineno* are attributes for the new :class:" +"`DocTest` object. See the documentation for :class:`DocTest` for more " +"information." +msgstr "" + +#: ../Doc/library/doctest.rst:1377 +msgid "" +"Extract all doctest examples from the given string, and return them as a " +"list of :class:`Example` objects. Line numbers are 0-based. The optional " +"argument *name* is a name identifying this string, and is only used for " +"error messages." +msgstr "" + +#: ../Doc/library/doctest.rst:1384 +msgid "" +"Divide the given string into examples and intervening text, and return them " +"as a list of alternating :class:`Example`\\ s and strings. Line numbers for " +"the :class:`Example`\\ s are 0-based. The optional argument *name* is a " +"name identifying this string, and is only used for error messages." +msgstr "" + +#: ../Doc/library/doctest.rst:1393 +msgid "DocTestRunner objects" +msgstr "" + +#: ../Doc/library/doctest.rst:1398 +msgid "" +"A processing class used to execute and verify the interactive examples in a :" +"class:`DocTest`." +msgstr "" + +#: ../Doc/library/doctest.rst:1401 +msgid "" +"The comparison between expected outputs and actual outputs is done by an :" +"class:`OutputChecker`. This comparison may be customized with a number of " +"option flags; see section :ref:`doctest-options` for more information. If " +"the option flags are insufficient, then the comparison may also be " +"customized by passing a subclass of :class:`OutputChecker` to the " +"constructor." +msgstr "" + +#: ../Doc/library/doctest.rst:1407 +msgid "" +"The test runner's display output can be controlled in two ways. First, an " +"output function can be passed to :meth:`TestRunner.run`; this function will " +"be called with strings that should be displayed. It defaults to ``sys." +"stdout.write``. If capturing the output is not sufficient, then the display " +"output can be also customized by subclassing DocTestRunner, and overriding " +"the methods :meth:`report_start`, :meth:`report_success`, :meth:" +"`report_unexpected_exception`, and :meth:`report_failure`." +msgstr "" + +#: ../Doc/library/doctest.rst:1415 +msgid "" +"The optional keyword argument *checker* specifies the :class:`OutputChecker` " +"object (or drop-in replacement) that should be used to compare the expected " +"outputs to the actual outputs of doctest examples." +msgstr "" + +#: ../Doc/library/doctest.rst:1419 +msgid "" +"The optional keyword argument *verbose* controls the :class:" +"`DocTestRunner`'s verbosity. If *verbose* is ``True``, then information is " +"printed about each example, as it is run. If *verbose* is ``False``, then " +"only failures are printed. If *verbose* is unspecified, or ``None``, then " +"verbose output is used iff the command-line switch ``-v`` is used." +msgstr "" + +#: ../Doc/library/doctest.rst:1425 +msgid "" +"The optional keyword argument *optionflags* can be used to control how the " +"test runner compares expected output to actual output, and how it displays " +"failures. For more information, see section :ref:`doctest-options`." +msgstr "" + +#: ../Doc/library/doctest.rst:1435 +msgid "" +"Report that the test runner is about to process the given example. This " +"method is provided to allow subclasses of :class:`DocTestRunner` to " +"customize their output; it should not be called directly." +msgstr "" + +#: ../Doc/library/doctest.rst:1439 +msgid "" +"*example* is the example about to be processed. *test* is the test " +"*containing example*. *out* is the output function that was passed to :meth:" +"`DocTestRunner.run`." +msgstr "" + +#: ../Doc/library/doctest.rst:1446 +msgid "" +"Report that the given example ran successfully. This method is provided to " +"allow subclasses of :class:`DocTestRunner` to customize their output; it " +"should not be called directly." +msgstr "" + +#: ../Doc/library/doctest.rst:1450 ../Doc/library/doctest.rst:1461 +msgid "" +"*example* is the example about to be processed. *got* is the actual output " +"from the example. *test* is the test containing *example*. *out* is the " +"output function that was passed to :meth:`DocTestRunner.run`." +msgstr "" + +#: ../Doc/library/doctest.rst:1457 +msgid "" +"Report that the given example failed. This method is provided to allow " +"subclasses of :class:`DocTestRunner` to customize their output; it should " +"not be called directly." +msgstr "" + +#: ../Doc/library/doctest.rst:1468 +msgid "" +"Report that the given example raised an unexpected exception. This method is " +"provided to allow subclasses of :class:`DocTestRunner` to customize their " +"output; it should not be called directly." +msgstr "" + +#: ../Doc/library/doctest.rst:1472 +msgid "" +"*example* is the example about to be processed. *exc_info* is a tuple " +"containing information about the unexpected exception (as returned by :func:" +"`sys.exc_info`). *test* is the test containing *example*. *out* is the " +"output function that was passed to :meth:`DocTestRunner.run`." +msgstr "" + +#: ../Doc/library/doctest.rst:1480 +msgid "" +"Run the examples in *test* (a :class:`DocTest` object), and display the " +"results using the writer function *out*." +msgstr "" + +#: ../Doc/library/doctest.rst:1483 +msgid "" +"The examples are run in the namespace ``test.globs``. If *clear_globs* is " +"true (the default), then this namespace will be cleared after the test runs, " +"to help with garbage collection. If you would like to examine the namespace " +"after the test completes, then use *clear_globs=False*." +msgstr "" + +#: ../Doc/library/doctest.rst:1488 +msgid "" +"*compileflags* gives the set of flags that should be used by the Python " +"compiler when running the examples. If not specified, then it will default " +"to the set of future-import flags that apply to *globs*." +msgstr "" + +#: ../Doc/library/doctest.rst:1492 +msgid "" +"The output of each example is checked using the :class:`DocTestRunner`'s " +"output checker, and the results are formatted by the :meth:`DocTestRunner." +"report_\\*` methods." +msgstr "" + +#: ../Doc/library/doctest.rst:1499 +msgid "" +"Print a summary of all the test cases that have been run by this " +"DocTestRunner, and return a :term:`named tuple` ``TestResults(failed, " +"attempted)``." +msgstr "" + +#: ../Doc/library/doctest.rst:1502 +msgid "" +"The optional *verbose* argument controls how detailed the summary is. If " +"the verbosity is not specified, then the :class:`DocTestRunner`'s verbosity " +"is used." +msgstr "" + +#: ../Doc/library/doctest.rst:1509 +msgid "OutputChecker objects" +msgstr "" + +#: ../Doc/library/doctest.rst:1514 +msgid "" +"A class used to check the whether the actual output from a doctest example " +"matches the expected output. :class:`OutputChecker` defines two methods: :" +"meth:`check_output`, which compares a given pair of outputs, and returns " +"true if they match; and :meth:`output_difference`, which returns a string " +"describing the differences between two outputs." +msgstr "" + +#: ../Doc/library/doctest.rst:1521 +msgid ":class:`OutputChecker` defines the following methods:" +msgstr "" + +#: ../Doc/library/doctest.rst:1525 +msgid "" +"Return ``True`` iff the actual output from an example (*got*) matches the " +"expected output (*want*). These strings are always considered to match if " +"they are identical; but depending on what option flags the test runner is " +"using, several non-exact match types are also possible. See section :ref:" +"`doctest-options` for more information about option flags." +msgstr "" + +#: ../Doc/library/doctest.rst:1534 +msgid "" +"Return a string describing the differences between the expected output for a " +"given example (*example*) and the actual output (*got*). *optionflags* is " +"the set of option flags used to compare *want* and *got*." +msgstr "" + +#: ../Doc/library/doctest.rst:1542 +msgid "Debugging" +msgstr "" + +#: ../Doc/library/doctest.rst:1544 +msgid "Doctest provides several mechanisms for debugging doctest examples:" +msgstr "" + +#: ../Doc/library/doctest.rst:1546 +msgid "" +"Several functions convert doctests to executable Python programs, which can " +"be run under the Python debugger, :mod:`pdb`." +msgstr "" + +#: ../Doc/library/doctest.rst:1549 +msgid "" +"The :class:`DebugRunner` class is a subclass of :class:`DocTestRunner` that " +"raises an exception for the first failing example, containing information " +"about that example. This information can be used to perform post-mortem " +"debugging on the example." +msgstr "" + +#: ../Doc/library/doctest.rst:1554 +msgid "" +"The :mod:`unittest` cases generated by :func:`DocTestSuite` support the :" +"meth:`debug` method defined by :class:`unittest.TestCase`." +msgstr "" + +#: ../Doc/library/doctest.rst:1557 +msgid "" +"You can add a call to :func:`pdb.set_trace` in a doctest example, and you'll " +"drop into the Python debugger when that line is executed. Then you can " +"inspect current values of variables, and so on. For example, suppose :file:" +"`a.py` contains just this module docstring::" +msgstr "" + +#: ../Doc/library/doctest.rst:1572 +msgid "Then an interactive Python session may look like this::" +msgstr "" + +#: ../Doc/library/doctest.rst:1605 +msgid "" +"Functions that convert doctests to Python code, and possibly run the " +"synthesized code under the debugger:" +msgstr "" + +#: ../Doc/library/doctest.rst:1611 +msgid "Convert text with examples to a script." +msgstr "" + +#: ../Doc/library/doctest.rst:1613 +msgid "" +"Argument *s* is a string containing doctest examples. The string is " +"converted to a Python script, where doctest examples in *s* are converted to " +"regular code, and everything else is converted to Python comments. The " +"generated script is returned as a string. For example, ::" +msgstr "" + +#: ../Doc/library/doctest.rst:1628 +msgid "displays::" +msgstr "" + +#: ../Doc/library/doctest.rst:1638 +msgid "" +"This function is used internally by other functions (see below), but can " +"also be useful when you want to transform an interactive Python session into " +"a Python script." +msgstr "" + +#: ../Doc/library/doctest.rst:1645 +msgid "Convert the doctest for an object to a script." +msgstr "" + +#: ../Doc/library/doctest.rst:1647 +msgid "" +"Argument *module* is a module object, or dotted name of a module, containing " +"the object whose doctests are of interest. Argument *name* is the name " +"(within the module) of the object with the doctests of interest. The result " +"is a string, containing the object's docstring converted to a Python script, " +"as described for :func:`script_from_examples` above. For example, if " +"module :file:`a.py` contains a top-level function :func:`f`, then ::" +msgstr "" + +#: ../Doc/library/doctest.rst:1657 +msgid "" +"prints a script version of function :func:`f`'s docstring, with doctests " +"converted to code, and the rest placed in comments." +msgstr "" + +#: ../Doc/library/doctest.rst:1663 +msgid "Debug the doctests for an object." +msgstr "" + +#: ../Doc/library/doctest.rst:1665 +msgid "" +"The *module* and *name* arguments are the same as for function :func:" +"`testsource` above. The synthesized Python script for the named object's " +"docstring is written to a temporary file, and then that file is run under " +"the control of the Python debugger, :mod:`pdb`." +msgstr "" + +#: ../Doc/library/doctest.rst:1670 +msgid "" +"A shallow copy of ``module.__dict__`` is used for both local and global " +"execution context." +msgstr "" + +#: ../Doc/library/doctest.rst:1673 +msgid "" +"Optional argument *pm* controls whether post-mortem debugging is used. If " +"*pm* has a true value, the script file is run directly, and the debugger " +"gets involved only if the script terminates via raising an unhandled " +"exception. If it does, then post-mortem debugging is invoked, via :func:" +"`pdb.post_mortem`, passing the traceback object from the unhandled " +"exception. If *pm* is not specified, or is false, the script is run under " +"the debugger from the start, via passing an appropriate :func:`exec` call " +"to :func:`pdb.run`." +msgstr "" + +#: ../Doc/library/doctest.rst:1684 +msgid "Debug the doctests in a string." +msgstr "" + +#: ../Doc/library/doctest.rst:1686 +msgid "" +"This is like function :func:`debug` above, except that a string containing " +"doctest examples is specified directly, via the *src* argument." +msgstr "" + +#: ../Doc/library/doctest.rst:1689 +msgid "" +"Optional argument *pm* has the same meaning as in function :func:`debug` " +"above." +msgstr "" + +#: ../Doc/library/doctest.rst:1691 +msgid "" +"Optional argument *globs* gives a dictionary to use as both local and global " +"execution context. If not specified, or ``None``, an empty dictionary is " +"used. If specified, a shallow copy of the dictionary is used." +msgstr "" + +#: ../Doc/library/doctest.rst:1696 +msgid "" +"The :class:`DebugRunner` class, and the special exceptions it may raise, are " +"of most interest to testing framework authors, and will only be sketched " +"here. See the source code, and especially :class:`DebugRunner`'s docstring " +"(which is a doctest!) for more details:" +msgstr "" + +#: ../Doc/library/doctest.rst:1704 +msgid "" +"A subclass of :class:`DocTestRunner` that raises an exception as soon as a " +"failure is encountered. If an unexpected exception occurs, an :exc:" +"`UnexpectedException` exception is raised, containing the test, the example, " +"and the original exception. If the output doesn't match, then a :exc:" +"`DocTestFailure` exception is raised, containing the test, the example, and " +"the actual output." +msgstr "" + +#: ../Doc/library/doctest.rst:1711 +msgid "" +"For information about the constructor parameters and methods, see the " +"documentation for :class:`DocTestRunner` in section :ref:`doctest-advanced-" +"api`." +msgstr "" + +#: ../Doc/library/doctest.rst:1714 +msgid "" +"There are two exceptions that may be raised by :class:`DebugRunner` " +"instances:" +msgstr "" + +#: ../Doc/library/doctest.rst:1719 +msgid "" +"An exception raised by :class:`DocTestRunner` to signal that a doctest " +"example's actual output did not match its expected output. The constructor " +"arguments are used to initialize the attributes of the same names." +msgstr "" + +#: ../Doc/library/doctest.rst:1723 +msgid ":exc:`DocTestFailure` defines the following attributes:" +msgstr "" + +#: ../Doc/library/doctest.rst:1728 ../Doc/library/doctest.rst:1752 +msgid "The :class:`DocTest` object that was being run when the example failed." +msgstr "" + +#: ../Doc/library/doctest.rst:1733 ../Doc/library/doctest.rst:1757 +msgid "The :class:`Example` that failed." +msgstr "" + +#: ../Doc/library/doctest.rst:1738 +msgid "The example's actual output." +msgstr "" + +#: ../Doc/library/doctest.rst:1743 +msgid "" +"An exception raised by :class:`DocTestRunner` to signal that a doctest " +"example raised an unexpected exception. The constructor arguments are used " +"to initialize the attributes of the same names." +msgstr "" + +#: ../Doc/library/doctest.rst:1747 +msgid ":exc:`UnexpectedException` defines the following attributes:" +msgstr "" + +#: ../Doc/library/doctest.rst:1762 +msgid "" +"A tuple containing information about the unexpected exception, as returned " +"by :func:`sys.exc_info`." +msgstr "" + +#: ../Doc/library/doctest.rst:1769 +msgid "Soapbox" +msgstr "" + +#: ../Doc/library/doctest.rst:1771 +msgid "" +"As mentioned in the introduction, :mod:`doctest` has grown to have three " +"primary uses:" +msgstr "" + +#: ../Doc/library/doctest.rst:1774 +msgid "Checking examples in docstrings." +msgstr "" + +#: ../Doc/library/doctest.rst:1776 +msgid "Regression testing." +msgstr "" + +#: ../Doc/library/doctest.rst:1778 +msgid "Executable documentation / literate testing." +msgstr "" + +#: ../Doc/library/doctest.rst:1780 +msgid "" +"These uses have different requirements, and it is important to distinguish " +"them. In particular, filling your docstrings with obscure test cases makes " +"for bad documentation." +msgstr "" + +#: ../Doc/library/doctest.rst:1784 +msgid "" +"When writing a docstring, choose docstring examples with care. There's an " +"art to this that needs to be learned---it may not be natural at first. " +"Examples should add genuine value to the documentation. A good example can " +"often be worth many words. If done with care, the examples will be " +"invaluable for your users, and will pay back the time it takes to collect " +"them many times over as the years go by and things change. I'm still amazed " +"at how often one of my :mod:`doctest` examples stops working after a " +"\"harmless\" change." +msgstr "" + +#: ../Doc/library/doctest.rst:1792 +msgid "" +"Doctest also makes an excellent tool for regression testing, especially if " +"you don't skimp on explanatory text. By interleaving prose and examples, it " +"becomes much easier to keep track of what's actually being tested, and why. " +"When a test fails, good prose can make it much easier to figure out what the " +"problem is, and how it should be fixed. It's true that you could write " +"extensive comments in code-based testing, but few programmers do. Many have " +"found that using doctest approaches instead leads to much clearer tests. " +"Perhaps this is simply because doctest makes writing prose a little easier " +"than writing code, while writing comments in code is a little harder. I " +"think it goes deeper than just that: the natural attitude when writing a " +"doctest-based test is that you want to explain the fine points of your " +"software, and illustrate them with examples. This in turn naturally leads to " +"test files that start with the simplest features, and logically progress to " +"complications and edge cases. A coherent narrative is the result, instead " +"of a collection of isolated functions that test isolated bits of " +"functionality seemingly at random. It's a different attitude, and produces " +"different results, blurring the distinction between testing and explaining." +msgstr "" + +#: ../Doc/library/doctest.rst:1810 +msgid "" +"Regression testing is best confined to dedicated objects or files. There " +"are several options for organizing tests:" +msgstr "" + +#: ../Doc/library/doctest.rst:1813 +msgid "" +"Write text files containing test cases as interactive examples, and test the " +"files using :func:`testfile` or :func:`DocFileSuite`. This is recommended, " +"although is easiest to do for new projects, designed from the start to use " +"doctest." +msgstr "" + +#: ../Doc/library/doctest.rst:1818 +msgid "" +"Define functions named ``_regrtest_topic`` that consist of single " +"docstrings, containing test cases for the named topics. These functions can " +"be included in the same file as the module, or separated out into a separate " +"test file." +msgstr "" + +#: ../Doc/library/doctest.rst:1822 +msgid "" +"Define a ``__test__`` dictionary mapping from regression test topics to " +"docstrings containing test cases." +msgstr "" + +#: ../Doc/library/doctest.rst:1825 +msgid "" +"When you have placed your tests in a module, the module can itself be the " +"test runner. When a test fails, you can arrange for your test runner to re-" +"run only the failing doctest while you debug the problem. Here is a minimal " +"example of such a test runner::" +msgstr "" + +#: ../Doc/library/doctest.rst:1848 +msgid "" +"Examples containing both expected output and an exception are not supported. " +"Trying to guess where one ends and the other begins is too error-prone, and " +"that also makes for a confusing test." +msgstr "" + +#: ../Doc/library/dummy_threading.rst:2 +msgid "" +":mod:`dummy_threading` --- Drop-in replacement for the :mod:`threading` " +"module" +msgstr "" + +#: ../Doc/library/dummy_threading.rst:7 +msgid "**Source code:** :source:`Lib/dummy_threading.py`" +msgstr "" + +#: ../Doc/library/dummy_threading.rst:11 +msgid "" +"This module provides a duplicate interface to the :mod:`threading` module. " +"It is meant to be imported when the :mod:`_thread` module is not provided on " +"a platform." +msgstr "" + +#: ../Doc/library/email.rst:2 +msgid ":mod:`email` --- An email and MIME handling package" +msgstr "" + +#: ../Doc/library/email.rst:11 +msgid "**Source code:** :source:`Lib/email/__init__.py`" +msgstr "" + +#: ../Doc/library/email.rst:15 +msgid "" +"The :mod:`email` package is a library for managing email messages. It is " +"specifically *not* designed to do any sending of email messages to SMTP (:" +"rfc:`2821`), NNTP, or other servers; those are functions of modules such as :" +"mod:`smtplib` and :mod:`nntplib`. The :mod:`email` package attempts to be " +"as RFC-compliant as possible, supporting :rfc:`5233` and :rfc:`6532`, as " +"well as such MIME-related RFCs as :rfc:`2045`, :rfc:`2046`, :rfc:`2047`, :" +"rfc:`2183`, and :rfc:`2231`." +msgstr "" + +#: ../Doc/library/email.rst:23 +msgid "" +"The overall structure of the email package can be divided into three major " +"components, plus a fourth component that controls the behavior of the other " +"components." +msgstr "" + +#: ../Doc/library/email.rst:27 +msgid "" +"The central component of the package is an \"object model\" that represents " +"email messages. An application interacts with the package primarily through " +"the object model interface defined in the :mod:`~email.message` sub-module. " +"The application can use this API to ask questions about an existing email, " +"to construct a new email, or to add or remove email subcomponents that " +"themselves use the same object model interface. That is, following the " +"nature of email messages and their MIME subcomponents, the email object " +"model is a tree structure of objects that all provide the :class:`~email." +"message.EmailMessage` API." +msgstr "" + +#: ../Doc/library/email.rst:37 +msgid "" +"The other two major components of the package are the :mod:`~email.parser` " +"and the :mod:`~email.generator`. The parser takes the serialized version of " +"an email message (a stream of bytes) and converts it into a tree of :class:" +"`~email.message.EmailMessage` objects. The generator takes an :class:" +"`~email.message.EmailMessage` and turns it back into a serialized byte " +"stream. (The parser and generator also handle streams of text characters, " +"but this usage is discouraged as it is too easy to end up with messages that " +"are not valid in one way or another.)" +msgstr "" + +#: ../Doc/library/email.rst:46 +msgid "" +"The control component is the :mod:`~email.policy` module. Every :class:" +"`~email.message.EmailMessage`, every :mod:`~email.generator`, and every :mod:" +"`~email.parser` has an associated :mod:`~email.policy` object that controls " +"its behavior. Usually an application only needs to specify the policy when " +"an :class:`~email.message.EmailMessage` is created, either by directly " +"instantiating an :class:`~email.message.EmailMessage` to create a new " +"email, or by parsing an input stream using a :mod:`~email.parser`. But the " +"policy can be changed when the message is serialized using a :mod:`~email." +"generator`. This allows, for example, a generic email message to be parsed " +"from disk, but to serialize it using standard SMTP settings when sending it " +"to an email server." +msgstr "" + +#: ../Doc/library/email.rst:58 +msgid "" +"The email package does its best to hide the details of the various governing " +"RFCs from the application. Conceptually the application should be able to " +"treat the email message as a structured tree of unicode text and binary " +"attachments, without having to worry about how these are represented when " +"serialized. In practice, however, it is often necessary to be aware of at " +"least some of the rules governing MIME messages and their structure, " +"specifically the names and nature of the MIME \"content types\" and how they " +"identify multipart documents. For the most part this knowledge should only " +"be required for more complex applications, and even then it should only be " +"the high level structure in question, and not the details of how those " +"structures are represented. Since MIME content types are used widely in " +"modern internet software (not just email), this will be a familiar concept " +"to many programmers." +msgstr "" + +#: ../Doc/library/email.rst:71 +msgid "" +"The following sections describe the functionality of the :mod:`email` " +"package. We start with the :mod:`~email.message` object model, which is the " +"primary interface an application will use, and follow that with the :mod:" +"`~email.parser` and :mod:`~email.generator` components. Then we cover the :" +"mod:`~email.policy` controls, which completes the treatment of the main " +"components of the library." +msgstr "" + +#: ../Doc/library/email.rst:78 +msgid "" +"The next three sections cover the exceptions the package may raise and the " +"defects (non-compliance with the RFCs) that the :mod:`~email.parser` may " +"detect. Then we cover the :mod:`~email.headerregistry` and the :mod:`~email." +"contentmanager` sub-components, which provide tools for doing more detailed " +"manipulation of headers and payloads, respectively. Both of these " +"components contain features relevant to consuming and producing non-trivial " +"messages, but also document their extensibility APIs, which will be of " +"interest to advanced applications." +msgstr "" + +#: ../Doc/library/email.rst:87 +msgid "" +"Following those is a set of examples of using the fundamental parts of the " +"APIs covered in the preceding sections." +msgstr "" + +#: ../Doc/library/email.rst:90 +msgid "" +"The forgoing represent the modern (unicode friendly) API of the email " +"package. The remaining sections, starting with the :class:`~email.message." +"Message` class, cover the legacy :data:`~email.policy.compat32` API that " +"deals much more directly with the details of how email messages are " +"represented. The :data:`~email.policy.compat32` API does *not* hide the " +"details of the RFCs from the application, but for applications that need to " +"operate at that level, they can be useful tools. This documentation is also " +"relevant for applications that are still using the :mod:`~email.policy." +"compat32` API for backward compatibility reasons." +msgstr "" + +#: ../Doc/library/email.rst:100 +msgid "" +"Docs reorganized and rewritten to promote the new :class:`~email.message." +"EmailMessage`/:class:`~email.policy.EmailPolicy` API." +msgstr "" + +#: ../Doc/library/email.rst:105 +msgid "Contents of the :mod:`email` package documentation:" +msgstr "" + +#: ../Doc/library/email.rst:120 +msgid "Legacy API:" +msgstr "" + +#: ../Doc/library/email.rst:136 +msgid "Module :mod:`smtplib`" +msgstr "" + +#: ../Doc/library/email.rst:136 +msgid "SMTP (Simple Mail Transport Protcol) client" +msgstr "" + +#: ../Doc/library/email.rst:139 +msgid "Module :mod:`poplib`" +msgstr "" + +#: ../Doc/library/email.rst:139 +msgid "POP (Post Office Protocol) client" +msgstr "" + +#: ../Doc/library/email.rst:142 ../Doc/library/poplib.rst:85 +msgid "Module :mod:`imaplib`" +msgstr "" + +#: ../Doc/library/email.rst:142 +msgid "IMAP (Internet Message Access Protocol) client" +msgstr "" + +#: ../Doc/library/email.rst:145 +msgid "Module :mod:`nntplib`" +msgstr "" + +#: ../Doc/library/email.rst:145 +msgid "NNTP (Net News Transport Protocol) client" +msgstr "" + +#: ../Doc/library/email.rst:149 +msgid "Module :mod:`mailbox`" +msgstr "" + +#: ../Doc/library/email.rst:148 +msgid "" +"Tools for creating, reading, and managing collections of messages on disk " +"using a variety standard formats." +msgstr "" + +#: ../Doc/library/email.rst:151 +msgid "Module :mod:`smtpd`" +msgstr "" + +#: ../Doc/library/email.rst:152 +msgid "SMTP server framework (primarily useful for testing)" +msgstr "" + +#: ../Doc/library/email.charset.rst:2 +msgid ":mod:`email.charset`: Representing character sets" +msgstr "" + +#: ../Doc/library/email.charset.rst:7 +msgid "**Source code:** :source:`Lib/email/charset.py`" +msgstr "" + +#: ../Doc/library/email.charset.rst:11 +msgid "" +"This module is part of the legacy (``Compat32``) email API. In the new API " +"only the aliases table is used." +msgstr "" + +#: ../Doc/library/email.charset.rst:14 ../Doc/library/email.encoders.rst:15 +#: ../Doc/library/email.header.rst:17 +msgid "" +"The remaining text in this section is the original documentation of the " +"module." +msgstr "" + +#: ../Doc/library/email.charset.rst:16 +msgid "" +"This module provides a class :class:`Charset` for representing character " +"sets and character set conversions in email messages, as well as a character " +"set registry and several convenience methods for manipulating this registry. " +"Instances of :class:`Charset` are used in several other modules within the :" +"mod:`email` package." +msgstr "" + +#: ../Doc/library/email.charset.rst:22 +msgid "Import this class from the :mod:`email.charset` module." +msgstr "" + +#: ../Doc/library/email.charset.rst:27 +msgid "Map character sets to their email properties." +msgstr "" + +#: ../Doc/library/email.charset.rst:29 +msgid "" +"This class provides information about the requirements imposed on email for " +"a specific character set. It also provides convenience routines for " +"converting between character sets, given the availability of the applicable " +"codecs. Given a character set, it will do its best to provide information " +"on how to use that character set in an email message in an RFC-compliant way." +msgstr "" + +#: ../Doc/library/email.charset.rst:35 +msgid "" +"Certain character sets must be encoded with quoted-printable or base64 when " +"used in email headers or bodies. Certain character sets must be converted " +"outright, and are not allowed in email." +msgstr "" + +#: ../Doc/library/email.charset.rst:39 +msgid "" +"Optional *input_charset* is as described below; it is always coerced to " +"lower case. After being alias normalized it is also used as a lookup into " +"the registry of character sets to find out the header encoding, body " +"encoding, and output conversion codec to be used for the character set. For " +"example, if *input_charset* is ``iso-8859-1``, then headers and bodies will " +"be encoded using quoted-printable and no output conversion codec is " +"necessary. If *input_charset* is ``euc-jp``, then headers will be encoded " +"with base64, bodies will not be encoded, but output text will be converted " +"from the ``euc-jp`` character set to the ``iso-2022-jp`` character set." +msgstr "" + +#: ../Doc/library/email.charset.rst:49 +msgid ":class:`Charset` instances have the following data attributes:" +msgstr "" + +#: ../Doc/library/email.charset.rst:53 +msgid "" +"The initial character set specified. Common aliases are converted to their " +"*official* email names (e.g. ``latin_1`` is converted to ``iso-8859-1``). " +"Defaults to 7-bit ``us-ascii``." +msgstr "" + +#: ../Doc/library/email.charset.rst:60 +msgid "" +"If the character set must be encoded before it can be used in an email " +"header, this attribute will be set to ``Charset.QP`` (for quoted-printable), " +"``Charset.BASE64`` (for base64 encoding), or ``Charset.SHORTEST`` for the " +"shortest of QP or BASE64 encoding. Otherwise, it will be ``None``." +msgstr "" + +#: ../Doc/library/email.charset.rst:69 +msgid "" +"Same as *header_encoding*, but describes the encoding for the mail message's " +"body, which indeed may be different than the header encoding. ``Charset." +"SHORTEST`` is not allowed for *body_encoding*." +msgstr "" + +#: ../Doc/library/email.charset.rst:76 +msgid "" +"Some character sets must be converted before they can be used in email " +"headers or bodies. If the *input_charset* is one of them, this attribute " +"will contain the name of the character set output will be converted to. " +"Otherwise, it will be ``None``." +msgstr "" + +#: ../Doc/library/email.charset.rst:84 +msgid "" +"The name of the Python codec used to convert the *input_charset* to " +"Unicode. If no conversion codec is necessary, this attribute will be " +"``None``." +msgstr "" + +#: ../Doc/library/email.charset.rst:91 +msgid "" +"The name of the Python codec used to convert Unicode to the " +"*output_charset*. If no conversion codec is necessary, this attribute will " +"have the same value as the *input_codec*." +msgstr "" + +#: ../Doc/library/email.charset.rst:96 +msgid ":class:`Charset` instances also have the following methods:" +msgstr "" + +#: ../Doc/library/email.charset.rst:100 +msgid "Return the content transfer encoding used for body encoding." +msgstr "" + +#: ../Doc/library/email.charset.rst:102 +msgid "" +"This is either the string ``quoted-printable`` or ``base64`` depending on " +"the encoding used, or it is a function, in which case you should call the " +"function with a single argument, the Message object being encoded. The " +"function should then set the :mailheader:`Content-Transfer-Encoding` header " +"itself to whatever is appropriate." +msgstr "" + +#: ../Doc/library/email.charset.rst:108 +msgid "" +"Returns the string ``quoted-printable`` if *body_encoding* is ``QP``, " +"returns the string ``base64`` if *body_encoding* is ``BASE64``, and returns " +"the string ``7bit`` otherwise." +msgstr "" + +#: ../Doc/library/email.charset.rst:148 +msgid "Return the output character set." +msgstr "" + +#: ../Doc/library/email.charset.rst:150 +msgid "" +"This is the *output_charset* attribute if that is not ``None``, otherwise it " +"is *input_charset*." +msgstr "" + +#: ../Doc/library/email.charset.rst:156 +msgid "Header-encode the string *string*." +msgstr "" + +#: ../Doc/library/email.charset.rst:158 +msgid "" +"The type of encoding (base64 or quoted-printable) will be based on the " +"*header_encoding* attribute." +msgstr "" + +#: ../Doc/library/email.charset.rst:164 +msgid "Header-encode a *string* by converting it first to bytes." +msgstr "" + +#: ../Doc/library/email.charset.rst:166 +msgid "" +"This is similar to :meth:`header_encode` except that the string is fit into " +"maximum line lengths as given by the argument *maxlengths*, which must be an " +"iterator: each element returned from this iterator will provide the next " +"maximum line length." +msgstr "" + +#: ../Doc/library/email.charset.rst:174 +msgid "Body-encode the string *string*." +msgstr "" + +#: ../Doc/library/email.charset.rst:176 +msgid "" +"The type of encoding (base64 or quoted-printable) will be based on the " +"*body_encoding* attribute." +msgstr "" + +#: ../Doc/library/email.charset.rst:179 +msgid "" +"The :class:`Charset` class also provides a number of methods to support " +"standard operations and built-in functions." +msgstr "" + +#: ../Doc/library/email.charset.rst:185 +msgid "" +"Returns *input_charset* as a string coerced to lower case. :meth:`__repr__` " +"is an alias for :meth:`__str__`." +msgstr "" + +#: ../Doc/library/email.charset.rst:191 +msgid "" +"This method allows you to compare two :class:`Charset` instances for " +"equality." +msgstr "" + +#: ../Doc/library/email.charset.rst:197 +msgid "" +"This method allows you to compare two :class:`Charset` instances for " +"inequality." +msgstr "" + +#: ../Doc/library/email.charset.rst:200 +msgid "" +"The :mod:`email.charset` module also provides the following functions for " +"adding new entries to the global character set, alias, and codec registries:" +msgstr "" + +#: ../Doc/library/email.charset.rst:206 +msgid "Add character properties to the global registry." +msgstr "" + +#: ../Doc/library/email.charset.rst:208 +msgid "" +"*charset* is the input character set, and must be the canonical name of a " +"character set." +msgstr "" + +#: ../Doc/library/email.charset.rst:211 +msgid "" +"Optional *header_enc* and *body_enc* is either ``Charset.QP`` for quoted-" +"printable, ``Charset.BASE64`` for base64 encoding, ``Charset.SHORTEST`` for " +"the shortest of quoted-printable or base64 encoding, or ``None`` for no " +"encoding. ``SHORTEST`` is only valid for *header_enc*. The default is " +"``None`` for no encoding." +msgstr "" + +#: ../Doc/library/email.charset.rst:217 +msgid "" +"Optional *output_charset* is the character set that the output should be in. " +"Conversions will proceed from input charset, to Unicode, to the output " +"charset when the method :meth:`Charset.convert` is called. The default is " +"to output in the same character set as the input." +msgstr "" + +#: ../Doc/library/email.charset.rst:222 +msgid "" +"Both *input_charset* and *output_charset* must have Unicode codec entries in " +"the module's character set-to-codec mapping; use :func:`add_codec` to add " +"codecs the module does not know about. See the :mod:`codecs` module's " +"documentation for more information." +msgstr "" + +#: ../Doc/library/email.charset.rst:227 +msgid "" +"The global character set registry is kept in the module global dictionary " +"``CHARSETS``." +msgstr "" + +#: ../Doc/library/email.charset.rst:233 +msgid "" +"Add a character set alias. *alias* is the alias name, e.g. ``latin-1``. " +"*canonical* is the character set's canonical name, e.g. ``iso-8859-1``." +msgstr "" + +#: ../Doc/library/email.charset.rst:236 +msgid "" +"The global charset alias registry is kept in the module global dictionary " +"``ALIASES``." +msgstr "" + +#: ../Doc/library/email.charset.rst:242 +msgid "" +"Add a codec that map characters in the given character set to and from " +"Unicode." +msgstr "" + +#: ../Doc/library/email.charset.rst:244 +msgid "" +"*charset* is the canonical name of a character set. *codecname* is the name " +"of a Python codec, as appropriate for the second argument to the :class:" +"`str`'s :meth:`~str.encode` method." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:4 +msgid "" +":mod:`email.message.Message`: Representing an email message using the :data:" +"`~email.policy.compat32` API" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:11 +msgid "" +"The :class:`Message` class is very similar to the :class:`~email.message." +"EmailMessage` class, without the methods added by that class, and with the " +"default behavior of certain other methods being slightly different. We also " +"document here some methods that, while supported by the :class:`~email." +"message.EmailMessage` class, are not recommended unless you are dealing with " +"legacy code." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:18 +msgid "The philosophy and structure of the two classes is otherwise the same." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:20 +msgid "" +"This document describes the behavior under the default (for :class:" +"`Message`) policy :attr:`~email.policy.Compat32`. If you are going to use " +"another policy, you should be using the :class:`~email.message.EmailMessage` " +"class instead." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:24 +msgid "" +"An email message consists of *headers* and a *payload*. Headers must be :" +"rfc:`5233` style names and values, where the field name and value are " +"separated by a colon. The colon is not part of either the field name or the " +"field value. The payload may be a simple text message, or a binary object, " +"or a structured sequence of sub-messages each with their own set of headers " +"and their own payload. The latter type of payload is indicated by the " +"message having a MIME type such as :mimetype:`multipart/\\*` or :mimetype:" +"`message/rfc822`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:33 +msgid "" +"The conceptual model provided by a :class:`Message` object is that of an " +"ordered dictionary of headers with additional methods for accessing both " +"specialized information from the headers, for accessing the payload, for " +"generating a serialized version of the mssage, and for recursively walking " +"over the object tree. Note that duplicate headers are supported but special " +"methods must be used to access them." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:40 +msgid "" +"The :class:`Message` psuedo-dictionary is indexed by the header names, which " +"must be ASCII values. The values of the dictionary are strings that are " +"supposed to contain only ASCII characters; there is some special handling " +"for non-ASCII input, but it doesn't always produce the correct results. " +"Headers are stored and returned in case-preserving form, but field names are " +"matched case-insensitively. There may also be a single envelope header, " +"also known as the *Unix-From* header or the ``From_`` header. The *payload* " +"is either a string or bytes, in the case of simple message objects, or a " +"list of :class:`Message` objects, for MIME container documents (e.g. :" +"mimetype:`multipart/\\*` and :mimetype:`message/rfc822`)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:51 +msgid "Here are the methods of the :class:`Message` class:" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:56 +msgid "" +"If *policy* is specified (it must be an instance of a :mod:`~email.policy` " +"class) use the rules it specifies to update and serialize the representation " +"of the message. If *policy* is not set, use the :class:`compat32 ` policy, which maintains backward compatibility with the " +"Python 3.2 version of the email package. For more information see the :mod:" +"`~email.policy` documentation." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:63 +msgid "The *policy* keyword argument was added." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:68 +msgid "" +"Return the entire message flattened as a string. When optional *unixfrom* " +"is true, the envelope header is included in the returned string. *unixfrom* " +"defaults to ``False``. For backward compabitility reasons, *maxheaderlen* " +"defaults to ``0``, so if you want a different value you must override it " +"explicitly (the value specified for *max_line_length* in the policy will be " +"ignored by this method). The *policy* argument may be used to override the " +"default policy obtained from the message instance. This can be used to " +"control some of the formatting produced by the method, since the specified " +"*policy* will be passed to the ``Generator``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:78 +#: ../Doc/library/email.compat32-message.rst:120 +msgid "" +"Flattening the message may trigger changes to the :class:`Message` if " +"defaults need to be filled in to complete the transformation to a string " +"(for example, MIME boundaries may be generated or modified)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:82 +msgid "" +"Note that this method is provided as a convenience and may not always format " +"the message the way you want. For example, by default it does not do the " +"mangling of lines that begin with ``From`` that is required by the unix mbox " +"format. For more flexibility, instantiate a :class:`~email.generator." +"Generator` instance and use its :meth:`~email.generator.Generator.flatten` " +"method directly. For example::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:96 +msgid "" +"If the message object contains binary data that is not encoded according to " +"RFC standards, the non-compliant data will be replaced by unicode \"unknown " +"character\" code points. (See also :meth:`.as_bytes` and :class:`~email." +"generator.BytesGenerator`.)" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:101 +msgid "the *policy* keyword argument was added." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:106 +msgid "" +"Equivalent to :meth:`.as_string()`. Allows ``str(msg)`` to produce a string " +"containing the formatted message." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:112 +msgid "" +"Return the entire message flattened as a bytes object. When optional " +"*unixfrom* is true, the envelope header is included in the returned string. " +"*unixfrom* defaults to ``False``. The *policy* argument may be used to " +"override the default policy obtained from the message instance. This can be " +"used to control some of the formatting produced by the method, since the " +"specified *policy* will be passed to the ``BytesGenerator``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:124 +msgid "" +"Note that this method is provided as a convenience and may not always format " +"the message the way you want. For example, by default it does not do the " +"mangling of lines that begin with ``From`` that is required by the unix mbox " +"format. For more flexibility, instantiate a :class:`~email.generator." +"BytesGenerator` instance and use its :meth:`~email.generator.BytesGenerator." +"flatten` method directly. For example::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:144 +msgid "" +"Equivalent to :meth:`.as_bytes()`. Allows ``bytes(msg)`` to produce a bytes " +"object containing the formatted message." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:152 +msgid "" +"Return ``True`` if the message's payload is a list of sub-\\ :class:" +"`Message` objects, otherwise return ``False``. When :meth:`is_multipart` " +"returns ``False``, the payload should be a string object (which might be a " +"CTE encoded binary payload. (Note that :meth:`is_multipart` returning " +"``True`` does not necessarily mean that \"msg.get_content_maintype() == " +"'multipart'\" will return the ``True``. For example, ``is_multipart`` will " +"return ``True`` when the :class:`Message` is of type ``message/rfc822``.)" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:164 +msgid "" +"Set the message's envelope header to *unixfrom*, which should be a string." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:169 +#: ../Doc/library/email.message.rst:152 +msgid "" +"Return the message's envelope header. Defaults to ``None`` if the envelope " +"header was never set." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:175 +msgid "" +"Add the given *payload* to the current payload, which must be ``None`` or a " +"list of :class:`Message` objects before the call. After the call, the " +"payload will always be a list of :class:`Message` objects. If you want to " +"set the payload to a scalar object (e.g. a string), use :meth:`set_payload` " +"instead." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:181 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class its functionality is replaced by :meth:`~email.message.EmailMessage." +"set_content` and the realted ``make`` and ``add`` methods." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:189 +msgid "" +"Return the current payload, which will be a list of :class:`Message` objects " +"when :meth:`is_multipart` is ``True``, or a string when :meth:`is_multipart` " +"is ``False``. If the payload is a list and you mutate the list object, you " +"modify the message's payload in place." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:194 +msgid "" +"With optional argument *i*, :meth:`get_payload` will return the *i*-th " +"element of the payload, counting from zero, if :meth:`is_multipart` is " +"``True``. An :exc:`IndexError` will be raised if *i* is less than 0 or " +"greater than or equal to the number of items in the payload. If the payload " +"is a string (i.e. :meth:`is_multipart` is ``False``) and *i* is given, a :" +"exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:201 +msgid "" +"Optional *decode* is a flag indicating whether the payload should be decoded " +"or not, according to the :mailheader:`Content-Transfer-Encoding` header. " +"When ``True`` and the message is not a multipart, the payload will be " +"decoded if this header's value is ``quoted-printable`` or ``base64``. If " +"some other encoding is used, or :mailheader:`Content-Transfer-Encoding` " +"header is missing, the payload is returned as-is (undecoded). In all cases " +"the returned value is binary data. If the message is a multipart and the " +"*decode* flag is ``True``, then ``None`` is returned. If the payload is " +"base64 and it was not perfectly formed (missing padding, characters outside " +"the base64 alphabet), then an appropriate defect will be added to the " +"message's defect property (:class:`~email.errors.InvalidBase64PaddingDefect` " +"or :class:`~email.errors.InvalidBase64CharactersDefect`, respectively)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:215 +msgid "" +"When *decode* is ``False`` (the default) the body is returned as a string " +"without decoding the :mailheader:`Content-Transfer-Encoding`. However, for " +"a :mailheader:`Content-Transfer-Encoding` of 8bit, an attempt is made to " +"decode the original bytes using the ``charset`` specified by the :mailheader:" +"`Content-Type` header, using the ``replace`` error handler. If no " +"``charset`` is specified, or if the ``charset`` given is not recognized by " +"the email package, the body is decoded using the default ASCII charset." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:224 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class its functionality is replaced by :meth:`~email.message.EmailMessage." +"get_content` and :meth:`~email.message.EmailMessage.iter_parts`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:232 +msgid "" +"Set the entire message object's payload to *payload*. It is the client's " +"responsibility to ensure the payload invariants. Optional *charset* sets " +"the message's default character set; see :meth:`set_charset` for details." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:236 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class its functionality is replaced by :meth:`~email.message.EmailMessage." +"set_content`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:243 +msgid "" +"Set the character set of the payload to *charset*, which can either be a :" +"class:`~email.charset.Charset` instance (see :mod:`email.charset`), a string " +"naming a character set, or ``None``. If it is a string, it will be " +"converted to a :class:`~email.charset.Charset` instance. If *charset* is " +"``None``, the ``charset`` parameter will be removed from the :mailheader:" +"`Content-Type` header (the message will not be otherwise modified). " +"Anything else will generate a :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:251 +msgid "" +"If there is no existing :mailheader:`MIME-Version` header one will be " +"added. If there is no existing :mailheader:`Content-Type` header, one will " +"be added with a value of :mimetype:`text/plain`. Whether the :mailheader:" +"`Content-Type` header already exists or not, its ``charset`` parameter will " +"be set to *charset.output_charset*. If *charset.input_charset* and " +"*charset.output_charset* differ, the payload will be re-encoded to the " +"*output_charset*. If there is no existing :mailheader:`Content-Transfer-" +"Encoding` header, then the payload will be transfer-encoded, if needed, " +"using the specified :class:`~email.charset.Charset`, and a header with the " +"appropriate value will be added. If a :mailheader:`Content-Transfer-" +"Encoding` header already exists, the payload is assumed to already be " +"correctly encoded using that :mailheader:`Content-Transfer-Encoding` and is " +"not modified." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:265 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class its functionality is replaced by the *charset* parameter of the :meth:" +"`email.emailmessage.EmailMessage.set_content` method." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:273 +msgid "" +"Return the :class:`~email.charset.Charset` instance associated with the " +"message's payload." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:276 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class it always returns ``None``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:281 +msgid "" +"The following methods implement a mapping-like interface for accessing the " +"message's :rfc:`2822` headers. Note that there are some semantic " +"differences between these methods and a normal mapping (i.e. dictionary) " +"interface. For example, in a dictionary there are no duplicate keys, but " +"here there may be duplicate message headers. Also, in dictionaries there is " +"no guaranteed order to the keys returned by :meth:`keys`, but in a :class:" +"`Message` object, headers are always returned in the order they appeared in " +"the original message, or were added to the message later. Any header " +"deleted and then re-added are always appended to the end of the header list." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:291 +msgid "" +"These semantic differences are intentional and are biased toward maximal " +"convenience." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:294 +#: ../Doc/library/email.message.rst:170 +msgid "" +"Note that in all cases, any envelope header present in the message is not " +"included in the mapping interface." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:297 +msgid "" +"In a model generated from bytes, any header values that (in contravention of " +"the RFCs) contain non-ASCII bytes will, when retrieved through this " +"interface, be represented as :class:`~email.header.Header` objects with a " +"charset of `unknown-8bit`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:305 +#: ../Doc/library/email.message.rst:176 +msgid "Return the total number of headers, including duplicates." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:310 +msgid "" +"Return true if the message object has a field named *name*. Matching is done " +"case-insensitively and *name* should not include the trailing colon. Used " +"for the ``in`` operator, e.g.::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:320 +msgid "" +"Return the value of the named header field. *name* should not include the " +"colon field separator. If the header is missing, ``None`` is returned; a :" +"exc:`KeyError` is never raised." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:324 +msgid "" +"Note that if the named field appears more than once in the message's " +"headers, exactly which of those field values will be returned is undefined. " +"Use the :meth:`get_all` method to get the values of all the extant named " +"headers." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:332 +msgid "" +"Add a header to the message with field name *name* and value *val*. The " +"field is appended to the end of the message's existing fields." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:335 +#: ../Doc/library/email.message.rst:209 +msgid "" +"Note that this does *not* overwrite or delete any existing header with the " +"same name. If you want to ensure that the new header is the only one " +"present in the message with field name *name*, delete the field first, e.g.::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:345 +#: ../Doc/library/email.message.rst:226 +msgid "" +"Delete all occurrences of the field with name *name* from the message's " +"headers. No exception is raised if the named field isn't present in the " +"headers." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:352 +#: ../Doc/library/email.message.rst:233 +msgid "Return a list of all the message's header field names." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:357 +#: ../Doc/library/email.message.rst:238 +msgid "Return a list of all the message's field values." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:362 +#: ../Doc/library/email.message.rst:243 +msgid "" +"Return a list of 2-tuples containing all the message's field headers and " +"values." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:368 +msgid "" +"Return the value of the named header field. This is identical to :meth:" +"`__getitem__` except that optional *failobj* is returned if the named header " +"is missing (defaults to ``None``)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:372 +msgid "Here are some additional useful methods:" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:377 +#: ../Doc/library/email.message.rst:259 +msgid "" +"Return a list of all the values for the field named *name*. If there are no " +"such named headers in the message, *failobj* is returned (defaults to " +"``None``)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:384 +#: ../Doc/library/email.message.rst:266 +msgid "" +"Extended header setting. This method is similar to :meth:`__setitem__` " +"except that additional header parameters can be provided as keyword " +"arguments. *_name* is the header field to add and *_value* is the *primary* " +"value for the header." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:389 +msgid "" +"For each item in the keyword argument dictionary *_params*, the key is taken " +"as the parameter name, with underscores converted to dashes (since dashes " +"are illegal in Python identifiers). Normally, the parameter will be added " +"as ``key=\"value\"`` unless the value is ``None``, in which case only the " +"key will be added. If the value contains non-ASCII characters, it can be " +"specified as a three tuple in the format ``(CHARSET, LANGUAGE, VALUE)``, " +"where ``CHARSET`` is a string naming the charset to be used to encode the " +"value, ``LANGUAGE`` can usually be set to ``None`` or the empty string (see :" +"rfc:`2231` for other possibilities), and ``VALUE`` is the string value " +"containing non-ASCII code points. If a three tuple is not passed and the " +"value contains non-ASCII characters, it is automatically encoded in :rfc:" +"`2231` format using a ``CHARSET`` of ``utf-8`` and a ``LANGUAGE`` of " +"``None``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:403 +#: ../Doc/library/email.header.rst:186 +msgid "Here's an example::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:407 +#: ../Doc/library/email.message.rst:291 +msgid "This will add a header that looks like ::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:411 +msgid "An example with non-ASCII characters::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:416 +msgid "Which produces ::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:423 +msgid "" +"Replace a header. Replace the first header found in the message that " +"matches *_name*, retaining header order and field name case. If no matching " +"header was found, a :exc:`KeyError` is raised." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:430 +msgid "" +"Return the message's content type. The returned string is coerced to lower " +"case of the form :mimetype:`maintype/subtype`. If there was no :mailheader:" +"`Content-Type` header in the message the default type as given by :meth:" +"`get_default_type` will be returned. Since according to :rfc:`2045`, " +"messages always have a default type, :meth:`get_content_type` will always " +"return a value." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:437 +msgid "" +":rfc:`2045` defines a message's default type to be :mimetype:`text/plain` " +"unless it appears inside a :mimetype:`multipart/digest` container, in which " +"case it would be :mimetype:`message/rfc822`. If the :mailheader:`Content-" +"Type` header has an invalid type specification, :rfc:`2045` mandates that " +"the default type be :mimetype:`text/plain`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:446 +#: ../Doc/library/email.message.rst:328 +msgid "" +"Return the message's main content type. This is the :mimetype:`maintype` " +"part of the string returned by :meth:`get_content_type`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:452 +#: ../Doc/library/email.message.rst:334 +msgid "" +"Return the message's sub-content type. This is the :mimetype:`subtype` part " +"of the string returned by :meth:`get_content_type`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:458 +#: ../Doc/library/email.message.rst:340 +msgid "" +"Return the default content type. Most messages have a default content type " +"of :mimetype:`text/plain`, except for messages that are subparts of :" +"mimetype:`multipart/digest` containers. Such subparts have a default " +"content type of :mimetype:`message/rfc822`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:466 +msgid "" +"Set the default content type. *ctype* should either be :mimetype:`text/" +"plain` or :mimetype:`message/rfc822`, although this is not enforced. The " +"default content type is not stored in the :mailheader:`Content-Type` header." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:474 +msgid "" +"Return the message's :mailheader:`Content-Type` parameters, as a list. The " +"elements of the returned list are 2-tuples of key/value pairs, as split on " +"the ``'='`` sign. The left hand side of the ``'='`` is the key, while the " +"right hand side is the value. If there is no ``'='`` sign in the parameter " +"the value is the empty string, otherwise the value is as described in :meth:" +"`get_param` and is unquoted if optional *unquote* is ``True`` (the default)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:482 +msgid "" +"Optional *failobj* is the object to return if there is no :mailheader:" +"`Content-Type` header. Optional *header* is the header to search instead " +"of :mailheader:`Content-Type`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:486 +#: ../Doc/library/email.compat32-message.rst:524 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class its functionality is replaced by the *params* property of the " +"individual header objects returned by the header access methods." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:494 +msgid "" +"Return the value of the :mailheader:`Content-Type` header's parameter " +"*param* as a string. If the message has no :mailheader:`Content-Type` " +"header or if there is no such parameter, then *failobj* is returned " +"(defaults to ``None``)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:499 +msgid "" +"Optional *header* if given, specifies the message header to use instead of :" +"mailheader:`Content-Type`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:502 +msgid "" +"Parameter keys are always compared case insensitively. The return value can " +"either be a string, or a 3-tuple if the parameter was :rfc:`2231` encoded. " +"When it's a 3-tuple, the elements of the value are of the form ``(CHARSET, " +"LANGUAGE, VALUE)``. Note that both ``CHARSET`` and ``LANGUAGE`` can be " +"``None``, in which case you should consider ``VALUE`` to be encoded in the " +"``us-ascii`` charset. You can usually ignore ``LANGUAGE``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:510 +msgid "" +"If your application doesn't care whether the parameter was encoded as in :" +"rfc:`2231`, you can collapse the parameter value by calling :func:`email." +"utils.collapse_rfc2231_value`, passing in the return value from :meth:" +"`get_param`. This will return a suitably decoded Unicode string when the " +"value is a tuple, or the original string unquoted if it isn't. For example::" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:520 +msgid "" +"In any case, the parameter value (either the returned string, or the " +"``VALUE`` item in the 3-tuple) is always unquoted, unless *unquote* is set " +"to ``False``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:533 +msgid "" +"Set a parameter in the :mailheader:`Content-Type` header. If the parameter " +"already exists in the header, its value will be replaced with *value*. If " +"the :mailheader:`Content-Type` header as not yet been defined for this " +"message, it will be set to :mimetype:`text/plain` and the new parameter " +"value will be appended as per :rfc:`2045`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:539 +msgid "" +"Optional *header* specifies an alternative header to :mailheader:`Content-" +"Type`, and all parameters will be quoted as necessary unless optional " +"*requote* is ``False`` (the default is ``True``)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:543 +msgid "" +"If optional *charset* is specified, the parameter will be encoded according " +"to :rfc:`2231`. Optional *language* specifies the RFC 2231 language, " +"defaulting to the empty string. Both *charset* and *language* should be " +"strings." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:548 +#: ../Doc/library/email.message.rst:373 +msgid "" +"If *replace* is ``False`` (the default) the header is moved to the end of " +"the list of headers. If *replace* is ``True``, the header will be updated " +"in place." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:552 +#: ../Doc/library/email.message.rst:384 +msgid "``replace`` keyword was added." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:557 +msgid "" +"Remove the given parameter completely from the :mailheader:`Content-Type` " +"header. The header will be re-written in place without the parameter or its " +"value. All values will be quoted as necessary unless *requote* is ``False`` " +"(the default is ``True``). Optional *header* specifies an alternative to :" +"mailheader:`Content-Type`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:566 +msgid "" +"Set the main type and subtype for the :mailheader:`Content-Type` header. " +"*type* must be a string in the form :mimetype:`maintype/subtype`, otherwise " +"a :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:570 +msgid "" +"This method replaces the :mailheader:`Content-Type` header, keeping all the " +"parameters in place. If *requote* is ``False``, this leaves the existing " +"header's quoting as is, otherwise the parameters will be quoted (the " +"default)." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:575 +msgid "" +"An alternative header can be specified in the *header* argument. When the :" +"mailheader:`Content-Type` header is set a :mailheader:`MIME-Version` header " +"is also added." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:579 +msgid "" +"This is a legacy method. On the :class:`~email.emailmessage.EmailMessage` " +"class its functionality is replaced by the ``make_`` and ``add_`` methods." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:586 +#: ../Doc/library/email.message.rst:400 +msgid "" +"Return the value of the ``filename`` parameter of the :mailheader:`Content-" +"Disposition` header of the message. If the header does not have a " +"``filename`` parameter, this method falls back to looking for the ``name`` " +"parameter on the :mailheader:`Content-Type` header. If neither is found, or " +"the header is missing, then *failobj* is returned. The returned string will " +"always be unquoted as per :func:`email.utils.unquote`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:597 +#: ../Doc/library/email.message.rst:411 +msgid "" +"Return the value of the ``boundary`` parameter of the :mailheader:`Content-" +"Type` header of the message, or *failobj* if either the header is missing, " +"or has no ``boundary`` parameter. The returned string will always be " +"unquoted as per :func:`email.utils.unquote`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:605 +#: ../Doc/library/email.message.rst:419 +msgid "" +"Set the ``boundary`` parameter of the :mailheader:`Content-Type` header to " +"*boundary*. :meth:`set_boundary` will always quote *boundary* if " +"necessary. A :exc:`~email.errors.HeaderParseError` is raised if the message " +"object has no :mailheader:`Content-Type` header." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:610 +msgid "" +"Note that using this method is subtly different than deleting the old :" +"mailheader:`Content-Type` header and adding a new one with the new boundary " +"via :meth:`add_header`, because :meth:`set_boundary` preserves the order of " +"the :mailheader:`Content-Type` header in the list of headers. However, it " +"does *not* preserve any continuation lines which may have been present in " +"the original :mailheader:`Content-Type` header." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:620 +#: ../Doc/library/email.message.rst:433 +msgid "" +"Return the ``charset`` parameter of the :mailheader:`Content-Type` header, " +"coerced to lower case. If there is no :mailheader:`Content-Type` header, or " +"if that header has no ``charset`` parameter, *failobj* is returned." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:624 +msgid "" +"Note that this method differs from :meth:`get_charset` which returns the :" +"class:`~email.charset.Charset` instance for the default encoding of the " +"message body." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:630 +#: ../Doc/library/email.message.rst:440 +msgid "" +"Return a list containing the character set names in the message. If the " +"message is a :mimetype:`multipart`, then the list will contain one element " +"for each subpart in the payload, otherwise, it will be a list of length 1." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:634 +msgid "" +"Each item in the list will be a string which is the value of the ``charset`` " +"parameter in the :mailheader:`Content-Type` header for the represented " +"subpart. However, if the subpart has no :mailheader:`Content-Type` header, " +"no ``charset`` parameter, or is not of the :mimetype:`text` main MIME type, " +"then that item in the returned list will be *failobj*." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:644 +#: ../Doc/library/email.message.rst:463 +msgid "" +"Return the lowercased value (without parameters) of the message's :" +"mailheader:`Content-Disposition` header if it has one, or ``None``. The " +"possible values for this method are *inline*, *attachment* or ``None`` if " +"the message follows :rfc:`2183`." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:653 +#: ../Doc/library/email.message.rst:477 +msgid "" +"The :meth:`walk` method is an all-purpose generator which can be used to " +"iterate over all the parts and subparts of a message object tree, in depth-" +"first traversal order. You will typically use :meth:`walk` as the iterator " +"in a ``for`` loop; each iteration returns the next subpart." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:658 +#: ../Doc/library/email.message.rst:482 +msgid "" +"Here's an example that prints the MIME type of every part of a multipart " +"message structure:" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:680 +#: ../Doc/library/email.message.rst:504 +msgid "" +"``walk`` iterates over the subparts of any part where :meth:`is_multipart` " +"returns ``True``, even though ``msg.get_content_maintype() == 'multipart'`` " +"may return ``False``. We can see this in our example by making use of the " +"``_structure`` debug helper function:" +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:707 +#: ../Doc/library/email.message.rst:531 +msgid "" +"Here the ``message`` parts are not ``multiparts``, but they do contain " +"subparts. ``is_multipart()`` returns ``True`` and ``walk`` descends into the " +"subparts." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:712 +msgid "" +":class:`Message` objects can also optionally contain two instance " +"attributes, which can be used when generating the plain text of a MIME " +"message." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:718 +#: ../Doc/library/email.message.rst:703 +msgid "" +"The format of a MIME document allows for some text between the blank line " +"following the headers, and the first multipart boundary string. Normally, " +"this text is never visible in a MIME-aware mail reader because it falls " +"outside the standard MIME armor. However, when viewing the raw text of the " +"message, or when viewing the message in a non-MIME aware reader, this text " +"can become visible." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:725 +#: ../Doc/library/email.message.rst:710 +msgid "" +"The *preamble* attribute contains this leading extra-armor text for MIME " +"documents. When the :class:`~email.parser.Parser` discovers some text after " +"the headers but before the first boundary string, it assigns this text to " +"the message's *preamble* attribute. When the :class:`~email.generator." +"Generator` is writing out the plain text representation of a MIME message, " +"and it finds the message has a *preamble* attribute, it will write this text " +"in the area between the headers and the first boundary. See :mod:`email." +"parser` and :mod:`email.generator` for details." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:735 +#: ../Doc/library/email.message.rst:720 +msgid "" +"Note that if the message object has no preamble, the *preamble* attribute " +"will be ``None``." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:741 +msgid "" +"The *epilogue* attribute acts the same way as the *preamble* attribute, " +"except that it contains text that appears between the last boundary and the " +"end of the message." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:745 +msgid "" +"You do not need to set the epilogue to the empty string in order for the :" +"class:`~email.generator.Generator` to print a newline at the end of the file." +msgstr "" + +#: ../Doc/library/email.compat32-message.rst:752 +#: ../Doc/library/email.message.rst:734 +msgid "" +"The *defects* attribute contains a list of all the problems found when " +"parsing this message. See :mod:`email.errors` for a detailed description of " +"the possible parsing defects." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:2 +msgid ":mod:`email.contentmanager`: Managing MIME Content" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:10 +msgid "**Source code:** :source:`Lib/email/contentmanager.py`" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:14 +#: ../Doc/library/email.headerregistry.rst:14 +#: ../Doc/library/email.message.rst:14 ../Doc/library/email.policy.rst:385 +msgid "[1]_" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:19 +msgid "" +"Base class for content managers. Provides the standard registry mechanisms " +"to register converters between MIME content and other representations, as " +"well as the ``get_content`` and ``set_content`` dispatch methods." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:26 +msgid "" +"Look up a handler function based on the ``mimetype`` of *msg* (see next " +"paragraph), call it, passing through all arguments, and return the result of " +"the call. The expectation is that the handler will extract the payload from " +"*msg* and return an object that encodes information about the extracted data." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:32 +msgid "" +"To find the handler, look for the following keys in the registry, stopping " +"with the first one found:" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:35 +msgid "the string representing the full MIME type (``maintype/subtype``)" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:36 +msgid "the string representing the ``maintype``" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:37 +msgid "the empty string" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:39 +msgid "" +"If none of these keys produce a handler, raise a :exc:`KeyError` for the " +"full MIME type." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:45 +msgid "" +"If the ``maintype`` is ``multipart``, raise a :exc:`TypeError`; otherwise " +"look up a handler function based on the type of *obj* (see next paragraph), " +"call :meth:`~email.message.EmailMessage.clear_content` on the *msg*, and " +"call the handler function, passing through all arguments. The expectation " +"is that the handler will transform and store *obj* into *msg*, possibly " +"making other changes to *msg* as well, such as adding various MIME headers " +"to encode information needed to interpret the stored data." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:54 +msgid "" +"To find the handler, obtain the type of *obj* (``typ = type(obj)``), and " +"look for the following keys in the registry, stopping with the first one " +"found:" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:58 +msgid "the type itself (``typ``)" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:59 +msgid "" +"the type's fully qualified name (``typ.__module__ + '.' + typ." +"__qualname__``)." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:61 +msgid "the type's qualname (``typ.__qualname__``)" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:62 +msgid "the type's name (``typ.__name__``)." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:64 +msgid "" +"If none of the above match, repeat all of the checks above for each of the " +"types in the :term:`MRO` (``typ.__mro__``). Finally, if no other key yields " +"a handler, check for a handler for the key ``None``. If there is no handler " +"for ``None``, raise a :exc:`KeyError` for the fully qualified name of the " +"type." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:70 +msgid "" +"Also add a :mailheader:`MIME-Version` header if one is not present (see " +"also :class:`.MIMEPart`)." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:76 +msgid "" +"Record the function *handler* as the handler for *key*. For the possible " +"values of *key*, see :meth:`get_content`." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:82 +msgid "" +"Record *handler* as the function to call when an object of a type matching " +"*typekey* is passed to :meth:`set_content`. For the possible values of " +"*typekey*, see :meth:`set_content`." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:88 +msgid "Content Manager Instances" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:90 +msgid "" +"Currently the email package provides only one concrete content manager, :" +"data:`raw_data_manager`, although more may be added in the future. :data:" +"`raw_data_manager` is the :attr:`~email.policy.EmailPolicy.content_manager` " +"provided by :attr:`~email.policy.EmailPolicy` and its derivatives." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:99 +msgid "" +"This content manager provides only a minimum interface beyond that provided " +"by :class:`~email.message.Message` itself: it deals only with text, raw " +"byte strings, and :class:`~email.message.Message` objects. Nevertheless, it " +"provides significant advantages compared to the base API: ``get_content`` on " +"a text part will return a unicode string without the application needing to " +"manually decode it, ``set_content`` provides a rich set of options for " +"controlling the headers added to a part and controlling the content transfer " +"encoding, and it enables the use of the various ``add_`` methods, thereby " +"simplifying the creation of multipart messages." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:111 +msgid "" +"Return the payload of the part as either a string (for ``text`` parts), an :" +"class:`~email.message.EmailMessage` object (for ``message/rfc822`` parts), " +"or a ``bytes`` object (for all other non-multipart types). Raise a :exc:" +"`KeyError` if called on a ``multipart``. If the part is a ``text`` part and " +"*errors* is specified, use it as the error handler when decoding the payload " +"to unicode. The default error handler is ``replace``." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:133 +msgid "Add headers and payload to *msg*:" +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:135 +msgid "" +"Add a :mailheader:`Content-Type` header with a ``maintype/subtype`` value." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:138 +msgid "" +"For ``str``, set the MIME ``maintype`` to ``text``, and set the subtype to " +"*subtype* if it is specified, or ``plain`` if it is not." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:140 +msgid "" +"For ``bytes``, use the specified *maintype* and *subtype*, or raise a :exc:" +"`TypeError` if they are not specified." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:142 +msgid "" +"For :class:`~email.message.EmailMessage` objects, set the maintype to " +"``message``, and set the subtype to *subtype* if it is specified or " +"``rfc822`` if it is not. If *subtype* is ``partial``, raise an error " +"(``bytes`` objects must be used to construct ``message/partial`` parts)." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:147 +msgid "" +"For *<'list'>*, which should be a list of :class:`~email.message." +"EmailMessage` objects, set the ``maintype`` to ``multipart``, and the " +"``subtype`` to *subtype* if it is specified, and ``mixed`` if it is not. If " +"the message parts in the *<'list'>* have :mailheader:`MIME-Version` headers, " +"remove them." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:154 +msgid "" +"If *charset* is provided (which is valid only for ``str``), encode the " +"string to bytes using the specified character set. The default is " +"``utf-8``. If the specified *charset* is a known alias for a standard MIME " +"charset name, use the standard charset instead." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:159 +msgid "" +"If *cte* is set, encode the payload using the specified content transfer " +"encoding, and set the :mailheader:`Content-Transfer-Endcoding` header to " +"that value. Possible values for *cte* are ``quoted-printable``, ``base64``, " +"``7bit``, ``8bit``, and ``binary``. If the input cannot be encoded in the " +"specified encoding (for example, specifying a *cte* of ``7bit`` for an input " +"that contains non-ASCII values), raise a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:167 +msgid "" +"For ``str`` objects, if *cte* is not set use heuristics to determine the " +"most compact encoding." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:169 +msgid "" +"For :class:`~email.message.EmailMessage`, per :rfc:`2046`, raise an error if " +"a *cte* of ``quoted-printable`` or ``base64`` is requested for *subtype* " +"``rfc822``, and for any *cte* other than ``7bit`` for *subtype* ``external-" +"body``. For ``message/rfc822``, use ``8bit`` if *cte* is not specified. " +"For all other values of *subtype*, use ``7bit``." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:176 +msgid "" +"A *cte* of ``binary`` does not actually work correctly yet. The " +"``EmailMessage`` object as modified by ``set_content`` is correct, but :" +"class:`~email.generator.BytesGenerator` does not serialize it correctly." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:181 +msgid "" +"If *disposition* is set, use it as the value of the :mailheader:`Content-" +"Disposition` header. If not specified, and *filename* is specified, add the " +"header with the value ``attachment``. If *disposition* is not specified and " +"*filename* is also not specified, do not add the header. The only valid " +"values for *disposition* are ``attachment`` and ``inline``." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:188 +msgid "" +"If *filename* is specified, use it as the value of the ``filename`` " +"parameter of the :mailheader:`Content-Disposition` header." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:191 +msgid "" +"If *cid* is specified, add a :mailheader:`Content-ID` header with *cid* as " +"its value." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:194 +msgid "" +"If *params* is specified, iterate its ``items`` method and use the resulting " +"``(key, value)`` pairs to set additional parameters on the :mailheader:" +"`Content-Type` header." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:198 +msgid "" +"If *headers* is specified and is a list of strings of the form ``headername: " +"headervalue`` or a list of ``header`` objects (distinguished from strings by " +"having a ``name`` attribute), add the headers to *msg*." +msgstr "" + +#: ../Doc/library/email.contentmanager.rst:206 +msgid "" +"Oringally added in 3.4 as a :term:`provisional module `" +msgstr "" + +#: ../Doc/library/email.encoders.rst:2 +msgid ":mod:`email.encoders`: Encoders" +msgstr "" + +#: ../Doc/library/email.encoders.rst:7 +msgid "**Source code:** :source:`Lib/email/encoders.py`" +msgstr "" + +#: ../Doc/library/email.encoders.rst:11 +msgid "" +"This module is part of the legacy (``Compat32``) email API. In the new API " +"the functionality is provided by the *cte* parameter of the :meth:`~email." +"message.EmailMessage.set_content` method." +msgstr "" + +#: ../Doc/library/email.encoders.rst:17 +msgid "" +"When creating :class:`~email.message.Message` objects from scratch, you " +"often need to encode the payloads for transport through compliant mail " +"servers. This is especially true for :mimetype:`image/\\*` and :mimetype:" +"`text/\\*` type messages containing binary data." +msgstr "" + +#: ../Doc/library/email.encoders.rst:22 +msgid "" +"The :mod:`email` package provides some convenient encodings in its :mod:" +"`encoders` module. These encoders are actually used by the :class:`~email." +"mime.audio.MIMEAudio` and :class:`~email.mime.image.MIMEImage` class " +"constructors to provide default encodings. All encoder functions take " +"exactly one argument, the message object to encode. They usually extract " +"the payload, encode it, and reset the payload to this newly encoded value. " +"They should also set the :mailheader:`Content-Transfer-Encoding` header as " +"appropriate." +msgstr "" + +#: ../Doc/library/email.encoders.rst:30 +msgid "" +"Note that these functions are not meaningful for a multipart message. They " +"must be applied to individual subparts instead, and will raise a :exc:" +"`TypeError` if passed a message whose type is multipart." +msgstr "" + +#: ../Doc/library/email.encoders.rst:34 +msgid "Here are the encoding functions provided:" +msgstr "" + +#: ../Doc/library/email.encoders.rst:39 +msgid "" +"Encodes the payload into quoted-printable form and sets the :mailheader:" +"`Content-Transfer-Encoding` header to ``quoted-printable`` [#]_. This is a " +"good encoding to use when most of your payload is normal printable data, but " +"contains a few unprintable characters." +msgstr "" + +#: ../Doc/library/email.encoders.rst:47 +msgid "" +"Encodes the payload into base64 form and sets the :mailheader:`Content-" +"Transfer-Encoding` header to ``base64``. This is a good encoding to use " +"when most of your payload is unprintable data since it is a more compact " +"form than quoted-printable. The drawback of base64 encoding is that it " +"renders the text non-human readable." +msgstr "" + +#: ../Doc/library/email.encoders.rst:56 +msgid "" +"This doesn't actually modify the message's payload, but it does set the :" +"mailheader:`Content-Transfer-Encoding` header to either ``7bit`` or ``8bit`` " +"as appropriate, based on the payload data." +msgstr "" + +#: ../Doc/library/email.encoders.rst:63 +msgid "" +"This does nothing; it doesn't even set the :mailheader:`Content-Transfer-" +"Encoding` header." +msgstr "" + +#: ../Doc/library/email.encoders.rst:68 +msgid "" +"Note that encoding with :meth:`encode_quopri` also encodes all tabs and " +"space characters in the data." +msgstr "" + +#: ../Doc/library/email.errors.rst:2 +msgid ":mod:`email.errors`: Exception and Defect classes" +msgstr "" + +#: ../Doc/library/email.errors.rst:7 +msgid "**Source code:** :source:`Lib/email/errors.py`" +msgstr "" + +#: ../Doc/library/email.errors.rst:11 +msgid "" +"The following exception classes are defined in the :mod:`email.errors` " +"module:" +msgstr "" + +#: ../Doc/library/email.errors.rst:16 +msgid "" +"This is the base class for all exceptions that the :mod:`email` package can " +"raise. It is derived from the standard :exc:`Exception` class and defines " +"no additional methods." +msgstr "" + +#: ../Doc/library/email.errors.rst:23 +msgid "" +"This is the base class for exceptions raised by the :class:`~email.parser." +"Parser` class. It is derived from :exc:`MessageError`. This class is also " +"used internally by the parser used by :mod:`~email.headerregistry`." +msgstr "" + +#: ../Doc/library/email.errors.rst:31 +msgid "" +"Raised under some error conditions when parsing the :rfc:`5322` headers of a " +"message, this class is derived from :exc:`MessageParseError`. The :meth:" +"`~email.message.EmailMessage.set_boundary` method will raise this error if " +"the content type is unknown when the method is called. :class:`~email.header." +"Header` may raise this error for certain base64 decoding errors, and when an " +"attempt is made to create a header that appears to contain an embedded " +"header (that is, there is what is supposed to be a continuation line that " +"has no leading whitespace and looks like a header)." +msgstr "" + +#: ../Doc/library/email.errors.rst:43 +msgid "Deprecated and no longer used." +msgstr "" + +#: ../Doc/library/email.errors.rst:48 +msgid "" +"Raised when a payload is added to a :class:`~email.message.Message` object " +"using :meth:`add_payload`, but the payload is already a scalar and the " +"message's :mailheader:`Content-Type` main type is not either :mimetype:" +"`multipart` or missing. :exc:`MultipartConversionError` multiply inherits " +"from :exc:`MessageError` and the built-in :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/email.errors.rst:54 +msgid "" +"Since :meth:`Message.add_payload` is deprecated, this exception is rarely " +"raised in practice. However the exception may also be raised if the :meth:" +"`~email.message.Message.attach` method is called on an instance of a class " +"derived from :class:`~email.mime.nonmultipart.MIMENonMultipart` (e.g. :class:" +"`~email.mime.image.MIMEImage`)." +msgstr "" + +#: ../Doc/library/email.errors.rst:62 +msgid "" +"Here is the list of the defects that the :class:`~email.parser.FeedParser` " +"can find while parsing messages. Note that the defects are added to the " +"message where the problem was found, so for example, if a message nested " +"inside a :mimetype:`multipart/alternative` had a malformed header, that " +"nested message object would have a defect, but the containing messages would " +"not." +msgstr "" + +#: ../Doc/library/email.errors.rst:68 +msgid "" +"All defect classes are subclassed from :class:`email.errors.MessageDefect`." +msgstr "" + +#: ../Doc/library/email.errors.rst:70 +msgid "" +":class:`NoBoundaryInMultipartDefect` -- A message claimed to be a multipart, " +"but had no :mimetype:`boundary` parameter." +msgstr "" + +#: ../Doc/library/email.errors.rst:73 +msgid "" +":class:`StartBoundaryNotFoundDefect` -- The start boundary claimed in the :" +"mailheader:`Content-Type` header was never found." +msgstr "" + +#: ../Doc/library/email.errors.rst:76 +msgid "" +":class:`CloseBoundaryNotFoundDefect` -- A start boundary was found, but no " +"corresponding close boundary was ever found." +msgstr "" + +#: ../Doc/library/email.errors.rst:81 +msgid "" +":class:`FirstHeaderLineIsContinuationDefect` -- The message had a " +"continuation line as its first header line." +msgstr "" + +#: ../Doc/library/email.errors.rst:84 +msgid "" +":class:`MisplacedEnvelopeHeaderDefect` - A \"Unix From\" header was found in " +"the middle of a header block." +msgstr "" + +#: ../Doc/library/email.errors.rst:87 +msgid "" +":class:`MissingHeaderBodySeparatorDefect` - A line was found while parsing " +"headers that had no leading white space but contained no ':'. Parsing " +"continues assuming that the line represents the first line of the body." +msgstr "" + +#: ../Doc/library/email.errors.rst:93 +msgid "" +":class:`MalformedHeaderDefect` -- A header was found that was missing a " +"colon, or was otherwise malformed." +msgstr "" + +#: ../Doc/library/email.errors.rst:96 +msgid "This defect has not been used for several Python versions." +msgstr "" + +#: ../Doc/library/email.errors.rst:99 +msgid "" +":class:`MultipartInvariantViolationDefect` -- A message claimed to be a :" +"mimetype:`multipart`, but no subparts were found. Note that when a message " +"has this defect, its :meth:`~email.message.Message.is_multipart` method may " +"return false even though its content type claims to be :mimetype:`multipart`." +msgstr "" + +#: ../Doc/library/email.errors.rst:104 +msgid "" +":class:`InvalidBase64PaddingDefect` -- When decoding a block of base64 " +"enocded bytes, the padding was not correct. Enough padding is added to " +"perform the decode, but the resulting decoded bytes may be invalid." +msgstr "" + +#: ../Doc/library/email.errors.rst:108 +msgid "" +":class:`InvalidBase64CharactersDefect` -- When decoding a block of base64 " +"enocded bytes, characters outside the base64 alphebet were encountered. The " +"characters are ignored, but the resulting decoded bytes may be invalid." +msgstr "" + +#: ../Doc/library/email.examples.rst:4 +msgid ":mod:`email`: Examples" +msgstr "" + +#: ../Doc/library/email.examples.rst:6 +msgid "" +"Here are a few examples of how to use the :mod:`email` package to read, " +"write, and send simple email messages, as well as more complex MIME messages." +msgstr "" + +#: ../Doc/library/email.examples.rst:9 +msgid "" +"First, let's see how to create and send a simple text message (both the text " +"content and the addresses may contain unicode characters):" +msgstr "" + +#: ../Doc/library/email.examples.rst:15 +msgid "" +"Parsing RFC822 headers can easily be done by the using the classes from the :" +"mod:`~email.parser` module:" +msgstr "" + +#: ../Doc/library/email.examples.rst:21 +msgid "" +"Here's an example of how to send a MIME message containing a bunch of family " +"pictures that may be residing in a directory:" +msgstr "" + +#: ../Doc/library/email.examples.rst:27 +msgid "" +"Here's an example of how to send the entire contents of a directory as an " +"email message: [1]_" +msgstr "" + +#: ../Doc/library/email.examples.rst:33 +msgid "" +"Here's an example of how to unpack a MIME message like the one above, into a " +"directory of files:" +msgstr "" + +#: ../Doc/library/email.examples.rst:39 +msgid "" +"Here's an example of how to create an HTML message with an alternative plain " +"text version. To make things a bit more interesting, we include a related " +"image in the html part, and we save a copy of what we are going to send to " +"disk, as well as sending it." +msgstr "" + +#: ../Doc/library/email.examples.rst:47 +msgid "" +"If we were sent the message from the last example, here is one way we could " +"process it:" +msgstr "" + +#: ../Doc/library/email.examples.rst:52 +msgid "Up to the prompt, the output from the above is:" +msgstr "" + +#: ../Doc/library/email.examples.rst:67 +msgid "" +"Thanks to Matthew Dixon Cowles for the original inspiration and examples." +msgstr "" + +#: ../Doc/library/email.generator.rst:2 +msgid ":mod:`email.generator`: Generating MIME documents" +msgstr "" + +#: ../Doc/library/email.generator.rst:7 +msgid "**Source code:** :source:`Lib/email/generator.py`" +msgstr "" + +#: ../Doc/library/email.generator.rst:11 +msgid "" +"One of the most common tasks is to generate the flat (serialized) version of " +"the email message represented by a message object structure. You will need " +"to do this if you want to send your message via :meth:`smtplib.SMTP." +"sendmail` or the :mod:`nntplib` module, or print the message on the " +"console. Taking a message object structure and producing a serialized " +"representation is the job of the generator classes." +msgstr "" + +#: ../Doc/library/email.generator.rst:18 +msgid "" +"As with the :mod:`email.parser` module, you aren't limited to the " +"functionality of the bundled generator; you could write one from scratch " +"yourself. However the bundled generator knows how to generate most email in " +"a standards-compliant way, should handle MIME and non-MIME email messages " +"just fine, and is designed so that the bytes-oriented parsing and generation " +"operations are inverses, assuming the same non-transforming :mod:`~email." +"policy` is used for both. That is, parsing the serialized byte stream via " +"the :class:`~email.parser.BytesParser` class and then regenerating the " +"serialized byte stream using :class:`BytesGenerator` should produce output " +"identical to the input [#]_. (On the other hand, using the generator on an :" +"class:`~email.message.EmailMessage` constructed by program may result in " +"changes to the :class:`~email.message.EmailMessage` object as defaults are " +"filled in.)" +msgstr "" + +#: ../Doc/library/email.generator.rst:32 +msgid "" +"The :class:`Generator` class can be used to flatten a message into a text " +"(as opposed to binary) serialized representation, but since Unicode cannot " +"represent binary data directly, the message is of necessity transformed into " +"something that contains only ASCII characters, using the standard email RFC " +"Content Transfer Encoding techniques for encoding email messages for " +"transport over channels that are not \"8 bit clean\"." +msgstr "" + +#: ../Doc/library/email.generator.rst:43 +msgid "" +"Return a :class:`BytesGenerator` object that will write any message provided " +"to the :meth:`flatten` method, or any surrogateescape encoded text provided " +"to the :meth:`write` method, to the :term:`file-like object` *outfp*. " +"*outfp* must support a ``write`` method that accepts binary data." +msgstr "" + +#: ../Doc/library/email.generator.rst:48 ../Doc/library/email.generator.rst:149 +msgid "" +"If optional *mangle_from_* is ``True``, put a ``>`` character in front of " +"any line in the body that starts with the exact string ``\"From \"``, that " +"is ``From`` followed by a space at the beginning of a line. *mangle_from_* " +"defaults to the value of the :attr:`~email.policy.Policy.mangle_from_` " +"setting of the *policy* (which is ``True`` for the :data:`~email.policy." +"compat32` policy and ``False`` for all others). *mangle_from_* is intended " +"for use when messages are stored in unix mbox format (see :mod:`mailbox` and " +"`WHY THE CONTENT-LENGTH FORMAT IS BAD `_)." +msgstr "" + +#: ../Doc/library/email.generator.rst:58 ../Doc/library/email.generator.rst:159 +msgid "" +"If *maxheaderlen* is not ``None``, refold any header lines that are longer " +"than *maxheaderlen*, or if ``0``, do not rewrap any headers. If " +"*manheaderlen* is ``None`` (the default), wrap headers and other message " +"lines according to the *policy* settings." +msgstr "" + +#: ../Doc/library/email.generator.rst:63 ../Doc/library/email.generator.rst:164 +msgid "" +"If *policy* is specified, use that policy to control message generation. If " +"*policy* is ``None`` (the default), use the policy associated with the :" +"class:`~email.message.Message` or :class:`~email.message.EmailMessage` " +"object passed to ``flatten`` to control the message generation. See :mod:" +"`email.policy` for details on what *policy* controls." +msgstr "" + +#: ../Doc/library/email.generator.rst:71 ../Doc/library/email.generator.rst:170 +#: ../Doc/library/email.parser.rst:94 ../Doc/library/email.parser.rst:122 +msgid "Added the *policy* keyword." +msgstr "" + +#: ../Doc/library/email.generator.rst:73 ../Doc/library/email.generator.rst:172 +msgid "" +"The default behavior of the *mangle_from_* and *maxheaderlen* parameters is " +"to follow the policy." +msgstr "" + +#: ../Doc/library/email.generator.rst:79 +msgid "" +"Print the textual representation of the message object structure rooted at " +"*msg* to the output file specified when the :class:`BytesGenerator` instance " +"was created." +msgstr "" + +#: ../Doc/library/email.generator.rst:83 +msgid "" +"If the :mod:`~email.policy` option :attr:`~email.policy.Policy.cte_type` is " +"``8bit`` (the default), copy any headers in the original parsed message that " +"have not been modified to the output with any bytes with the high bit set " +"reproduced as in the original, and preserve the non-ASCII :mailheader:" +"`Content-Transfer-Encoding` of any body parts that have them. If " +"``cte_type`` is ``7bit``, convert the bytes with the high bit set as needed " +"using an ASCII-compatible :mailheader:`Content-Transfer-Encoding`. That is, " +"transform parts with non-ASCII :mailheader:`Cotnent-Transfer-Encoding` (:" +"mailheader:`Content-Transfer-Encoding: 8bit`) to an ASCII compatibile :" +"mailheader:`Content-Transfer-Encoding`, and encode RFC-invalid non-ASCII " +"bytes in headers using the MIME ``unknown-8bit`` character set, thus " +"rendering them RFC-compliant." +msgstr "" + +#: ../Doc/library/email.generator.rst:100 +#: ../Doc/library/email.generator.rst:193 +msgid "" +"If *unixfrom* is ``True``, print the envelope header delimiter used by the " +"Unix mailbox format (see :mod:`mailbox`) before the first of the :rfc:`5322` " +"headers of the root message object. If the root object has no envelope " +"header, craft a standard one. The default is ``False``. Note that for " +"subparts, no envelope header is ever printed." +msgstr "" + +#: ../Doc/library/email.generator.rst:106 +#: ../Doc/library/email.generator.rst:199 +msgid "" +"If *linesep* is not ``None``, use it as the separator character between all " +"the lines of the flattened message. If *linesep* is ``None`` (the default), " +"use the value specified in the *policy*." +msgstr "" + +#: ../Doc/library/email.generator.rst:115 +msgid "" +"Return an independent clone of this :class:`BytesGenerator` instance with " +"the exact same option settings, and *fp* as the new *outfp*." +msgstr "" + +#: ../Doc/library/email.generator.rst:121 +msgid "" +"Encode *s* using the ``ASCII`` codec and the ``surrogateescape`` error " +"handler, and pass it to the *write* method of the *outfp* passed to the :" +"class:`BytesGenerator`'s constructor." +msgstr "" + +#: ../Doc/library/email.generator.rst:126 +msgid "" +"As a convenience, :class:`~email.message.EmailMessage` provides the methods :" +"meth:`~email.message.EmailMessage.as_bytes` and ``bytes(aMessage)`` (a.k.a. :" +"meth:`~email.message.EmailMessage.__bytes__`), which simplify the generation " +"of a serialized binary representation of a message object. For more detail, " +"see :mod:`email.message`." +msgstr "" + +#: ../Doc/library/email.generator.rst:133 +msgid "" +"Because strings cannot represent binary data, the :class:`Generator` class " +"must convert any binary data in any message it flattens to an ASCII " +"compatible format, by converting them to an ASCII compatible :mailheader:" +"`Content-Transfer_Encoding`. Using the terminology of the email RFCs, you " +"can think of this as :class:`Generator` serializing to an I/O stream that is " +"not \"8 bit clean\". In other words, most applications will want to be " +"using :class:`BytesGenerator`, and not :class:`Generator`." +msgstr "" + +#: ../Doc/library/email.generator.rst:144 +msgid "" +"Return a :class:`Generator` object that will write any message provided to " +"the :meth:`flatten` method, or any text provided to the :meth:`write` " +"method, to the :term:`file-like object` *outfp*. *outfp* must support a " +"``write`` method that accepts string data." +msgstr "" + +#: ../Doc/library/email.generator.rst:178 +msgid "" +"Print the textual representation of the message object structure rooted at " +"*msg* to the output file specified when the :class:`Generator` instance was " +"created." +msgstr "" + +#: ../Doc/library/email.generator.rst:182 +msgid "" +"If the :mod:`~email.policy` option :attr:`~email.policy.Policy.cte_type` is " +"``8bit``, generate the message as if the option were set to ``7bit``. (This " +"is required because strings cannot represent non-ASCII bytes.) Convert any " +"bytes with the high bit set as needed using an ASCII-compatible :mailheader:" +"`Content-Transfer-Encoding`. That is, transform parts with non-ASCII :" +"mailheader:`Cotnent-Transfer-Encoding` (:mailheader:`Content-Transfer-" +"Encoding: 8bit`) to an ASCII compatibile :mailheader:`Content-Transfer-" +"Encoding`, and encode RFC-invalid non-ASCII bytes in headers using the MIME " +"``unknown-8bit`` character set, thus rendering them RFC-compliant." +msgstr "" + +#: ../Doc/library/email.generator.rst:205 +msgid "" +"Added support for re-encoding ``8bit`` message bodies, and the *linesep* " +"argument." +msgstr "" + +#: ../Doc/library/email.generator.rst:212 +msgid "" +"Return an independent clone of this :class:`Generator` instance with the " +"exact same options, and *fp* as the new *outfp*." +msgstr "" + +#: ../Doc/library/email.generator.rst:218 +msgid "" +"Write *s* to the *write* method of the *outfp* passed to the :class:" +"`Generator`'s constructor. This provides just enough file-like API for :" +"class:`Generator` instances to be used in the :func:`print` function." +msgstr "" + +#: ../Doc/library/email.generator.rst:224 +msgid "" +"As a convenience, :class:`~email.message.EmailMessage` provides the methods :" +"meth:`~email.message.EmailMessage.as_string` and ``str(aMessage)`` (a.k.a. :" +"meth:`~email.message.EmailMessage.__str__`), which simplify the generation " +"of a formatted string representation of a message object. For more detail, " +"see :mod:`email.message`." +msgstr "" + +#: ../Doc/library/email.generator.rst:231 +msgid "" +"The :mod:`email.generator` module also provides a derived class, :class:" +"`DecodedGenerator`, which is like the :class:`Generator` base class, except " +"that non-\\ :mimetype:`text` parts are not serialized, but are instead " +"represented in the output stream by a string derived from a template filled " +"in with information about the part." +msgstr "" + +#: ../Doc/library/email.generator.rst:240 +msgid "" +"Act like :class:`Generator`, except that for any subpart of the message " +"passed to :meth:`Generator.flatten`, if the subpart is of main type :" +"mimetype:`text`, print the decoded payload of the subpart, and if the main " +"type is not :mimetype:`text`, instead of printing it fill in the string " +"*fmt* using information from the part and print the resulting filled-in " +"string." +msgstr "" + +#: ../Doc/library/email.generator.rst:247 +msgid "" +"To fill in *fmt*, execute ``fmt % part_info``, where ``part_info`` is a " +"dictionary composed of the following keys and values:" +msgstr "" + +#: ../Doc/library/email.generator.rst:250 +msgid "``type`` -- Full MIME type of the non-\\ :mimetype:`text` part" +msgstr "" + +#: ../Doc/library/email.generator.rst:252 +msgid "``maintype`` -- Main MIME type of the non-\\ :mimetype:`text` part" +msgstr "" + +#: ../Doc/library/email.generator.rst:254 +msgid "``subtype`` -- Sub-MIME type of the non-\\ :mimetype:`text` part" +msgstr "" + +#: ../Doc/library/email.generator.rst:256 +msgid "``filename`` -- Filename of the non-\\ :mimetype:`text` part" +msgstr "" + +#: ../Doc/library/email.generator.rst:258 +msgid "" +"``description`` -- Description associated with the non-\\ :mimetype:`text` " +"part" +msgstr "" + +#: ../Doc/library/email.generator.rst:260 +msgid "" +"``encoding`` -- Content transfer encoding of the non-\\ :mimetype:`text` part" +msgstr "" + +#: ../Doc/library/email.generator.rst:262 +msgid "If *fmt* is ``None``, use the following default *fmt*:" +msgstr "" + +#: ../Doc/library/email.generator.rst:264 +msgid "" +"\"[Non-text (%(type)s) part of message omitted, filename %(filename)s]\"" +msgstr "" + +#: ../Doc/library/email.generator.rst:266 +msgid "" +"Optional *_mangle_from_* and *maxheaderlen* are as with the :class:" +"`Generator` base class." +msgstr "" + +#: ../Doc/library/email.generator.rst:272 +msgid "" +"This statement assumes that you use the appropriate setting for " +"``unixfrom``, and that there are no :mod:`policy` settings calling for " +"automatic adjustments (for example, :attr:`~email.policy.Policy." +"refold_source` must be ``none``, which is *not* the default). It is also " +"not 100% true, since if the message does not conform to the RFC standards " +"occasionally information about the exact original text is lost during " +"parsing error recovery. It is a goal to fix these latter edge cases when " +"possible." +msgstr "" + +#: ../Doc/library/email.header.rst:2 +msgid ":mod:`email.header`: Internationalized headers" +msgstr "" + +#: ../Doc/library/email.header.rst:7 +msgid "**Source code:** :source:`Lib/email/header.py`" +msgstr "" + +#: ../Doc/library/email.header.rst:11 +msgid "" +"This module is part of the legacy (``Compat32``) email API. In the current " +"API encoding and decoding of headers is handled transparently by the " +"dictionary-like API of the :class:`~email.message.EmailMessage` class. In " +"addition to uses in legacy code, this module can be useful in applications " +"that need to completely control the character sets used when encoding " +"headers." +msgstr "" + +#: ../Doc/library/email.header.rst:19 +msgid "" +":rfc:`2822` is the base standard that describes the format of email " +"messages. It derives from the older :rfc:`822` standard which came into " +"widespread use at a time when most email was composed of ASCII characters " +"only. :rfc:`2822` is a specification written assuming email contains only 7-" +"bit ASCII characters." +msgstr "" + +#: ../Doc/library/email.header.rst:24 +msgid "" +"Of course, as email has been deployed worldwide, it has become " +"internationalized, such that language specific character sets can now be " +"used in email messages. The base standard still requires email messages to " +"be transferred using only 7-bit ASCII characters, so a slew of RFCs have " +"been written describing how to encode email containing non-ASCII characters " +"into :rfc:`2822`\\ -compliant format. These RFCs include :rfc:`2045`, :rfc:" +"`2046`, :rfc:`2047`, and :rfc:`2231`. The :mod:`email` package supports " +"these standards in its :mod:`email.header` and :mod:`email.charset` modules." +msgstr "" + +#: ../Doc/library/email.header.rst:33 +msgid "" +"If you want to include non-ASCII characters in your email headers, say in " +"the :mailheader:`Subject` or :mailheader:`To` fields, you should use the :" +"class:`Header` class and assign the field in the :class:`~email.message." +"Message` object to an instance of :class:`Header` instead of using a string " +"for the header value. Import the :class:`Header` class from the :mod:`email." +"header` module. For example::" +msgstr "" + +#: ../Doc/library/email.header.rst:50 +msgid "" +"Notice here how we wanted the :mailheader:`Subject` field to contain a non-" +"ASCII character? We did this by creating a :class:`Header` instance and " +"passing in the character set that the byte string was encoded in. When the " +"subsequent :class:`~email.message.Message` instance was flattened, the :" +"mailheader:`Subject` field was properly :rfc:`2047` encoded. MIME-aware " +"mail readers would show this header using the embedded ISO-8859-1 character." +msgstr "" + +#: ../Doc/library/email.header.rst:57 +msgid "Here is the :class:`Header` class description:" +msgstr "" + +#: ../Doc/library/email.header.rst:62 +msgid "" +"Create a MIME-compliant header that can contain strings in different " +"character sets." +msgstr "" + +#: ../Doc/library/email.header.rst:65 +msgid "" +"Optional *s* is the initial header value. If ``None`` (the default), the " +"initial header value is not set. You can later append to the header with :" +"meth:`append` method calls. *s* may be an instance of :class:`bytes` or :" +"class:`str`, but see the :meth:`append` documentation for semantics." +msgstr "" + +#: ../Doc/library/email.header.rst:70 +msgid "" +"Optional *charset* serves two purposes: it has the same meaning as the " +"*charset* argument to the :meth:`append` method. It also sets the default " +"character set for all subsequent :meth:`append` calls that omit the " +"*charset* argument. If *charset* is not provided in the constructor (the " +"default), the ``us-ascii`` character set is used both as *s*'s initial " +"charset and as the default for subsequent :meth:`append` calls." +msgstr "" + +#: ../Doc/library/email.header.rst:77 +msgid "" +"The maximum line length can be specified explicitly via *maxlinelen*. For " +"splitting the first line to a shorter value (to account for the field header " +"which isn't included in *s*, e.g. :mailheader:`Subject`) pass in the name of " +"the field in *header_name*. The default *maxlinelen* is 76, and the default " +"value for *header_name* is ``None``, meaning it is not taken into account " +"for the first line of a long, split header." +msgstr "" + +#: ../Doc/library/email.header.rst:84 +msgid "" +"Optional *continuation_ws* must be :rfc:`2822`\\ -compliant folding " +"whitespace, and is usually either a space or a hard tab character. This " +"character will be prepended to continuation lines. *continuation_ws* " +"defaults to a single space character." +msgstr "" + +#: ../Doc/library/email.header.rst:89 +msgid "" +"Optional *errors* is passed straight through to the :meth:`append` method." +msgstr "" + +#: ../Doc/library/email.header.rst:94 +msgid "Append the string *s* to the MIME header." +msgstr "" + +#: ../Doc/library/email.header.rst:96 +msgid "" +"Optional *charset*, if given, should be a :class:`~email.charset.Charset` " +"instance (see :mod:`email.charset`) or the name of a character set, which " +"will be converted to a :class:`~email.charset.Charset` instance. A value of " +"``None`` (the default) means that the *charset* given in the constructor is " +"used." +msgstr "" + +#: ../Doc/library/email.header.rst:102 +msgid "" +"*s* may be an instance of :class:`bytes` or :class:`str`. If it is an " +"instance of :class:`bytes`, then *charset* is the encoding of that byte " +"string, and a :exc:`UnicodeError` will be raised if the string cannot be " +"decoded with that character set." +msgstr "" + +#: ../Doc/library/email.header.rst:107 +msgid "" +"If *s* is an instance of :class:`str`, then *charset* is a hint specifying " +"the character set of the characters in the string." +msgstr "" + +#: ../Doc/library/email.header.rst:110 +msgid "" +"In either case, when producing an :rfc:`2822`\\ -compliant header using :rfc:" +"`2047` rules, the string will be encoded using the output codec of the " +"charset. If the string cannot be encoded using the output codec, a " +"UnicodeError will be raised." +msgstr "" + +#: ../Doc/library/email.header.rst:115 +msgid "" +"Optional *errors* is passed as the errors argument to the decode call if *s* " +"is a byte string." +msgstr "" + +#: ../Doc/library/email.header.rst:121 +msgid "" +"Encode a message header into an RFC-compliant format, possibly wrapping long " +"lines and encapsulating non-ASCII parts in base64 or quoted-printable " +"encodings." +msgstr "" + +#: ../Doc/library/email.header.rst:125 +msgid "" +"Optional *splitchars* is a string containing characters which should be " +"given extra weight by the splitting algorithm during normal header " +"wrapping. This is in very rough support of :RFC:`2822`\\'s 'higher level " +"syntactic breaks': split points preceded by a splitchar are preferred " +"during line splitting, with the characters preferred in the order in which " +"they appear in the string. Space and tab may be included in the string to " +"indicate whether preference should be given to one over the other as a split " +"point when other split chars do not appear in the line being split. " +"Splitchars does not affect :RFC:`2047` encoded lines." +msgstr "" + +#: ../Doc/library/email.header.rst:135 +msgid "" +"*maxlinelen*, if given, overrides the instance's value for the maximum line " +"length." +msgstr "" + +#: ../Doc/library/email.header.rst:138 +msgid "" +"*linesep* specifies the characters used to separate the lines of the folded " +"header. It defaults to the most useful value for Python application code (``" +"\\n``), but ``\\r\\n`` can be specified in order to produce headers with RFC-" +"compliant line separators." +msgstr "" + +#: ../Doc/library/email.header.rst:143 +msgid "Added the *linesep* argument." +msgstr "" + +#: ../Doc/library/email.header.rst:147 +msgid "" +"The :class:`Header` class also provides a number of methods to support " +"standard operators and built-in functions." +msgstr "" + +#: ../Doc/library/email.header.rst:152 +msgid "" +"Returns an approximation of the :class:`Header` as a string, using an " +"unlimited line length. All pieces are converted to unicode using the " +"specified encoding and joined together appropriately. Any pieces with a " +"charset of ``'unknown-8bit'`` are decoded as ASCII using the ``'replace'`` " +"error handler." +msgstr "" + +#: ../Doc/library/email.header.rst:158 +msgid "Added handling for the ``'unknown-8bit'`` charset." +msgstr "" + +#: ../Doc/library/email.header.rst:164 +msgid "" +"This method allows you to compare two :class:`Header` instances for equality." +msgstr "" + +#: ../Doc/library/email.header.rst:170 +msgid "" +"This method allows you to compare two :class:`Header` instances for " +"inequality." +msgstr "" + +#: ../Doc/library/email.header.rst:173 +msgid "" +"The :mod:`email.header` module also provides the following convenient " +"functions." +msgstr "" + +#: ../Doc/library/email.header.rst:178 +msgid "" +"Decode a message header value without converting the character set. The " +"header value is in *header*." +msgstr "" + +#: ../Doc/library/email.header.rst:181 +msgid "" +"This function returns a list of ``(decoded_string, charset)`` pairs " +"containing each of the decoded parts of the header. *charset* is ``None`` " +"for non-encoded parts of the header, otherwise a lower case string " +"containing the name of the character set specified in the encoded string." +msgstr "" + +#: ../Doc/library/email.header.rst:195 +msgid "" +"Create a :class:`Header` instance from a sequence of pairs as returned by :" +"func:`decode_header`." +msgstr "" + +#: ../Doc/library/email.header.rst:198 +msgid "" +":func:`decode_header` takes a header value string and returns a sequence of " +"pairs of the format ``(decoded_string, charset)`` where *charset* is the " +"name of the character set." +msgstr "" + +#: ../Doc/library/email.header.rst:202 +msgid "" +"This function takes one of those sequence of pairs and returns a :class:" +"`Header` instance. Optional *maxlinelen*, *header_name*, and " +"*continuation_ws* are as in the :class:`Header` constructor." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:2 +msgid ":mod:`email.headerregistry`: Custom Header Objects" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:10 +msgid "**Source code:** :source:`Lib/email/headerregistry.py`" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:16 +msgid "" +"Headers are represented by customized subclasses of :class:`str`. The " +"particular class used to represent a given header is determined by the :attr:" +"`~email.policy.EmailPolicy.header_factory` of the :mod:`~email.policy` in " +"effect when the headers are created. This section documents the particular " +"``header_factory`` implemented by the email package for handling :RFC:`5322` " +"compliant email messages, which not only provides customized header objects " +"for various header types, but also provides an extension mechanism for " +"applications to add their own custom header types." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:25 +msgid "" +"When using any of the policy objects derived from :data:`~email.policy." +"EmailPolicy`, all headers are produced by :class:`.HeaderRegistry` and have :" +"class:`.BaseHeader` as their last base class. Each header class has an " +"additional base class that is determined by the type of the header. For " +"example, many headers have the class :class:`.UnstructuredHeader` as their " +"other base class. The specialized second class for a header is determined " +"by the name of the header, using a lookup table stored in the :class:`." +"HeaderRegistry`. All of this is managed transparently for the typical " +"application program, but interfaces are provided for modifying the default " +"behavior for use by more complex applications." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:36 +msgid "" +"The sections below first document the header base classes and their " +"attributes, followed by the API for modifying the behavior of :class:`." +"HeaderRegistry`, and finally the support classes used to represent the data " +"parsed from structured headers." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:44 +msgid "" +"*name* and *value* are passed to ``BaseHeader`` from the :attr:`~email." +"policy.EmailPolicy.header_factory` call. The string value of any header " +"object is the *value* fully decoded to unicode." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:48 +msgid "This base class defines the following read-only properties:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:53 +msgid "" +"The name of the header (the portion of the field before the ':'). This is " +"exactly the value passed in the :attr:`~email.policy.EmailPolicy." +"header_factory` call for *name*; that is, case is preserved." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:61 +msgid "" +"A tuple of :exc:`~email.errors.HeaderDefect` instances reporting any RFC " +"compliance problems found during parsing. The email package tries to be " +"complete about detecting compliance issues. See the :mod:`~email.errors` " +"module for a discussion of the types of defects that may be reported." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:69 +msgid "" +"The maximum number of headers of this type that can have the same ``name``. " +"A value of ``None`` means unlimited. The ``BaseHeader`` value for this " +"attribute is ``None``; it is expected that specialized header classes will " +"override this value as needed." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:74 +msgid "" +"``BaseHeader`` also provides the following method, which is called by the " +"email library code and should not in general be called by application " +"programs:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:80 +msgid "" +"Return a string containing :attr:`~email.policy.Policy.linesep` characters " +"as required to correctly fold the header according to *policy*. A :attr:" +"`~email.policy.Policy.cte_type` of ``8bit`` will be treated as if it were " +"``7bit``, since headers may not contain arbitrary binary data. If :attr:" +"`~email.policy.EmailPolicy.utf8` is ``False``, non-ASCII data will be :rfc:" +"`2047` encoded." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:88 +msgid "" +"``BaseHeader`` by itself cannot be used to create a header object. It " +"defines a protocol that each specialized header cooperates with in order to " +"produce the header object. Specifically, ``BaseHeader`` requires that the " +"specialized class provide a :func:`classmethod` named ``parse``. This " +"method is called as follows::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:96 +msgid "" +"``kwds`` is a dictionary containing one pre-initialized key, ``defects``. " +"``defects`` is an empty list. The parse method should append any detected " +"defects to this list. On return, the ``kwds`` dictionary *must* contain " +"values for at least the keys ``decoded`` and ``defects``. ``decoded`` " +"should be the string value for the header (that is, the header value fully " +"decoded to unicode). The parse method should assume that *string* may " +"contain content-transfer-encoded parts, but should correctly handle all " +"valid unicode characters as well so that it can parse un-encoded header " +"values." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:105 +msgid "" +"``BaseHeader``'s ``__new__`` then creates the header instance, and calls its " +"``init`` method. The specialized class only needs to provide an ``init`` " +"method if it wishes to set additional attributes beyond those provided by " +"``BaseHeader`` itself. Such an ``init`` method should look like this::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:114 +msgid "" +"That is, anything extra that the specialized class puts in to the ``kwds`` " +"dictionary should be removed and handled, and the remaining contents of " +"``kw`` (and ``args``) passed to the ``BaseHeader`` ``init`` method." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:121 +msgid "" +"An \"unstructured\" header is the default type of header in :rfc:`5322`. Any " +"header that does not have a specified syntax is treated as unstructured. " +"The classic example of an unstructured header is the :mailheader:`Subject` " +"header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:126 +msgid "" +"In :rfc:`5322`, an unstructured header is a run of arbitrary text in the " +"ASCII character set. :rfc:`2047`, however, has an :rfc:`5322` compatible " +"mechanism for encoding non-ASCII text as ASCII characters within a header " +"value. When a *value* containing encoded words is passed to the " +"constructor, the ``UnstructuredHeader`` parser converts such encoded words " +"into unicode, following the :rfc:`2047` rules for unstructured text. The " +"parser uses heuristics to attempt to decode certain non-compliant encoded " +"words. Defects are registered in such cases, as well as defects for issues " +"such as invalid characters within the encoded words or the non-encoded text." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:136 +msgid "This header type provides no additional attributes." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:141 +msgid "" +":rfc:`5322` specifies a very specific format for dates within email headers. " +"The ``DateHeader`` parser recognizes that date format, as well as " +"recognizing a number of variant forms that are sometimes found \"in the wild" +"\"." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:146 +#: ../Doc/library/email.headerregistry.rst:188 +msgid "This header type provides the following additional attributes:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:150 +msgid "" +"If the header value can be recognized as a valid date of one form or " +"another, this attribute will contain a :class:`~datetime.datetime` instance " +"representing that date. If the timezone of the input date is specified as " +"``-0000`` (indicating it is in UTC but contains no information about the " +"source timezone), then :attr:`.datetime` will be a naive :class:`~datetime." +"datetime`. If a specific timezone offset is found (including `+0000`), " +"then :attr:`.datetime` will contain an aware ``datetime`` that uses :class:" +"`datetime.timezone` to record the timezone offset." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:160 +msgid "" +"The ``decoded`` value of the header is determined by formatting the " +"``datetime`` according to the :rfc:`5322` rules; that is, it is set to::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:165 +msgid "" +"When creating a ``DateHeader``, *value* may be :class:`~datetime.datetime` " +"instance. This means, for example, that the following code is valid and " +"does what one would expect::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:171 +msgid "" +"Because this is a naive ``datetime`` it will be interpreted as a UTC " +"timestamp, and the resulting value will have a timezone of ``-0000``. Much " +"more useful is to use the :func:`~email.utils.localtime` function from the :" +"mod:`~email.utils` module::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:178 +msgid "" +"This example sets the date header to the current time and date using the " +"current timezone offset." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:184 +msgid "" +"Address headers are one of the most complex structured header types. The " +"``AddressHeader`` class provides a generic interface to any address header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:193 +msgid "" +"A tuple of :class:`.Group` objects encoding the addresses and groups found " +"in the header value. Addresses that are not part of a group are represented " +"in this list as single-address ``Groups`` whose :attr:`~.Group.display_name` " +"is ``None``." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:201 +msgid "" +"A tuple of :class:`.Address` objects encoding all of the individual " +"addresses from the header value. If the header value contains any groups, " +"the individual addresses from the group are included in the list at the " +"point where the group occurs in the value (that is, the list of addresses is " +"\"flattened\" into a one dimensional list)." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:207 +msgid "" +"The ``decoded`` value of the header will have all encoded words decoded to " +"unicode. :class:`~encodings.idna` encoded domain names are also decoded to " +"unicode. The ``decoded`` value is set by :attr:`~str.join`\\ ing the :class:" +"`str` value of the elements of the ``groups`` attribute with ``', '``." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:213 +msgid "" +"A list of :class:`.Address` and :class:`.Group` objects in any combination " +"may be used to set the value of an address header. ``Group`` objects whose " +"``display_name`` is ``None`` will be interpreted as single addresses, which " +"allows an address list to be copied with groups intact by using the list " +"obtained from the ``groups`` attribute of the source header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:222 +msgid "" +"A subclass of :class:`.AddressHeader` that adds one additional attribute:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:228 +msgid "" +"The single address encoded by the header value. If the header value " +"actually contains more than one address (which would be a violation of the " +"RFC under the default :mod:`~email.policy`), accessing this attribute will " +"result in a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:234 +msgid "" +"Many of the above classes also have a ``Unique`` variant (for example, " +"``UniqueUnstructuredHeader``). The only difference is that in the " +"``Unique`` variant, :attr:`~.BaseHeader.max_count` is set to 1." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:241 +msgid "" +"There is really only one valid value for the :mailheader:`MIME-Version` " +"header, and that is ``1.0``. For future proofing, this header class " +"supports other valid version numbers. If a version number has a valid value " +"per :rfc:`2045`, then the header object will have non-``None`` values for " +"the following attributes:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:249 +msgid "" +"The version number as a string, with any whitespace and/or comments removed." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:254 +msgid "The major version number as an integer" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:258 +msgid "The minor version number as an integer" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:263 +msgid "" +"MIME headers all start with the prefix 'Content-'. Each specific header has " +"a certain value, described under the class for that header. Some can also " +"take a list of supplemental parameters, which have a common format. This " +"class serves as a base for all the MIME headers that take parameters." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:270 +msgid "A dictionary mapping parameter names to parameter values." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:275 +msgid "" +"A :class:`ParameterizedMIMEHeader` class that handles the :mailheader:" +"`Content-Type` header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:280 +msgid "The content type string, in the form ``maintype/subtype``." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:289 +msgid "" +"A :class:`ParameterizedMIMEHeader` class that handles the :mailheader:" +"`Content-Disposition` header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:294 +msgid "``inline`` and ``attachment`` are the only valid values in common use." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:299 +msgid "Handles the :mailheader:`Content-Transfer-Encoding` header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:303 +msgid "" +"Valid values are ``7bit``, ``8bit``, ``base64``, and ``quoted-printable``. " +"See :rfc:`2045` for more information." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:312 +msgid "" +"This is the factory used by :class:`~email.policy.EmailPolicy` by default. " +"``HeaderRegistry`` builds the class used to create a header instance " +"dynamically, using *base_class* and a specialized class retrieved from a " +"registry that it holds. When a given header name does not appear in the " +"registry, the class specified by *default_class* is used as the specialized " +"class. When *use_default_map* is ``True`` (the default), the standard " +"mapping of header names to classes is copied in to the registry during " +"initialization. *base_class* is always the last class in the generated " +"class's ``__bases__`` list." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:322 +msgid "The default mappings are:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:324 +msgid "UniqueUnstructuredHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:325 +#: ../Doc/library/email.headerregistry.rst:327 +msgid "UniqueDateHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:326 +msgid "DateHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:328 +msgid "UniqueSingleAddressHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:329 +msgid "SingleAddressHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:330 +#: ../Doc/library/email.headerregistry.rst:332 +#: ../Doc/library/email.headerregistry.rst:334 +#: ../Doc/library/email.headerregistry.rst:336 +msgid "UniqueAddressHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:331 +#: ../Doc/library/email.headerregistry.rst:333 +#: ../Doc/library/email.headerregistry.rst:335 +msgid "AddressHeader" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:338 +msgid "``HeaderRegistry`` has the following methods:" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:343 +msgid "" +"*name* is the name of the header to be mapped. It will be converted to " +"lower case in the registry. *cls* is the specialized class to be used, " +"along with *base_class*, to create the class used to instantiate headers " +"that match *name*." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:351 +msgid "Construct and return a class to handle creating a *name* header." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:356 +msgid "" +"Retrieves the specialized header associated with *name* from the registry " +"(using *default_class* if *name* does not appear in the registry) and " +"composes it with *base_class* to produce a class, calls the constructed " +"class's constructor, passing it the same argument list, and finally returns " +"the class instance created thereby." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:363 +msgid "" +"The following classes are the classes used to represent data parsed from " +"structured headers and can, in general, be used by an application program to " +"construct structured values to assign to specific headers." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:370 +msgid "" +"The class used to represent an email address. The general form of an " +"address is::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:375 ../Doc/library/tokenize.rst:143 +#: ../Doc/library/unittest.rst:968 ../Doc/library/unittest.rst:1036 +msgid "or::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:379 +msgid "" +"where each part must conform to specific syntax rules spelled out in :rfc:" +"`5322`." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:382 +msgid "" +"As a convenience *addr_spec* can be specified instead of *username* and " +"*domain*, in which case *username* and *domain* will be parsed from the " +"*addr_spec*. An *addr_spec* must be a properly RFC quoted string; if it is " +"not ``Address`` will raise an error. Unicode characters are allowed and " +"will be property encoded when serialized. However, per the RFCs, unicode is " +"*not* allowed in the username portion of the address." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:391 +msgid "" +"The display name portion of the address, if any, with all quoting removed. " +"If the address does not have a display name, this attribute will be an empty " +"string." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:397 +msgid "The ``username`` portion of the address, with all quoting removed." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:401 +msgid "The ``domain`` portion of the address." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:405 +msgid "" +"The ``username@domain`` portion of the address, correctly quoted for use as " +"a bare address (the second form shown above). This attribute is not mutable." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:411 +msgid "" +"The ``str`` value of the object is the address quoted according to :rfc:" +"`5322` rules, but with no Content Transfer Encoding of any non-ASCII " +"characters." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:415 +msgid "" +"To support SMTP (:rfc:`5321`), ``Address`` handles one special case: if " +"``username`` and ``domain`` are both the empty string (or ``None``), then " +"the string value of the ``Address`` is ``<>``." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:422 +msgid "" +"The class used to represent an address group. The general form of an " +"address group is::" +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:427 +msgid "" +"As a convenience for processing lists of addresses that consist of a mixture " +"of groups and single addresses, a ``Group`` may also be used to represent " +"single addresses that are not part of a group by setting *display_name* to " +"``None`` and providing a list of the single address as *addresses*." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:434 +msgid "" +"The ``display_name`` of the group. If it is ``None`` and there is exactly " +"one ``Address`` in ``addresses``, then the ``Group`` represents a single " +"address that is not in a group." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:440 +msgid "" +"A possibly empty tuple of :class:`.Address` objects representing the " +"addresses in the group." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:445 +msgid "" +"The ``str`` value of a ``Group`` is formatted according to :rfc:`5322`, but " +"with no Content Transfer Encoding of any non-ASCII characters. If " +"``display_name`` is none and there is a single ``Address`` in the " +"``addresses`` list, the ``str`` value will be the same as the ``str`` of " +"that single ``Address``." +msgstr "" + +#: ../Doc/library/email.headerregistry.rst:454 +msgid "" +"Oringally added in 3.3 as a :term:`provisional module `" +msgstr "" + +#: ../Doc/library/email.iterators.rst:2 +msgid ":mod:`email.iterators`: Iterators" +msgstr "" + +#: ../Doc/library/email.iterators.rst:7 +msgid "**Source code:** :source:`Lib/email/iterators.py`" +msgstr "" + +#: ../Doc/library/email.iterators.rst:11 +msgid "" +"Iterating over a message object tree is fairly easy with the :meth:`Message." +"walk ` method. The :mod:`email.iterators` " +"module provides some useful higher level iterations over message object " +"trees." +msgstr "" + +#: ../Doc/library/email.iterators.rst:19 +msgid "" +"This iterates over all the payloads in all the subparts of *msg*, returning " +"the string payloads line-by-line. It skips over all the subpart headers, " +"and it skips over any subpart with a payload that isn't a Python string. " +"This is somewhat equivalent to reading the flat text representation of the " +"message from a file using :meth:`~io.TextIOBase.readline`, skipping over all " +"the intervening headers." +msgstr "" + +#: ../Doc/library/email.iterators.rst:26 +msgid "" +"Optional *decode* is passed through to :meth:`Message.get_payload `." +msgstr "" + +#: ../Doc/library/email.iterators.rst:32 +msgid "" +"This iterates over all the subparts of *msg*, returning only those subparts " +"that match the MIME type specified by *maintype* and *subtype*." +msgstr "" + +#: ../Doc/library/email.iterators.rst:35 +msgid "" +"Note that *subtype* is optional; if omitted, then subpart MIME type matching " +"is done only with the main type. *maintype* is optional too; it defaults " +"to :mimetype:`text`." +msgstr "" + +#: ../Doc/library/email.iterators.rst:39 +msgid "" +"Thus, by default :func:`typed_subpart_iterator` returns each subpart that " +"has a MIME type of :mimetype:`text/\\*`." +msgstr "" + +#: ../Doc/library/email.iterators.rst:43 +msgid "" +"The following function has been added as a useful debugging tool. It should " +"*not* be considered part of the supported public interface for the package." +msgstr "" + +#: ../Doc/library/email.iterators.rst:48 +msgid "" +"Prints an indented representation of the content types of the message object " +"structure. For example:" +msgstr "" + +#: ../Doc/library/email.iterators.rst:81 +msgid "" +"Optional *fp* is a file-like object to print the output to. It must be " +"suitable for Python's :func:`print` function. *level* is used internally. " +"*include_default*, if true, prints the default type as well." +msgstr "" + +#: ../Doc/library/email.message.rst:2 +msgid ":mod:`email.message`: Representing an email message" +msgstr "" + +#: ../Doc/library/email.message.rst:10 +msgid "**Source code:** :source:`Lib/email/message.py`" +msgstr "" + +#: ../Doc/library/email.message.rst:16 +msgid "" +"The central class in the :mod:`email` package is the :class:`EmailMessage` " +"class, imported from the :mod:`email.message` module. It is the base class " +"for the :mod:`email` object model. :class:`EmailMessage` provides the core " +"functionality for setting and querying header fields, for accessing message " +"bodies, and for creating or modifying structured messages." +msgstr "" + +#: ../Doc/library/email.message.rst:22 +msgid "" +"An email message consists of *headers* and a *payload* (which is also " +"referred to as the *content*). Headers are :rfc:`5322` or :rfc:`6532` style " +"field names and values, where the field name and value are separated by a " +"colon. The colon is not part of either the field name or the field value. " +"The payload may be a simple text message, or a binary object, or a " +"structured sequence of sub-messages each with their own set of headers and " +"their own payload. The latter type of payload is indicated by the message " +"having a MIME type such as :mimetype:`multipart/\\*` or :mimetype:`message/" +"rfc822`." +msgstr "" + +#: ../Doc/library/email.message.rst:31 +msgid "" +"The conceptual model provided by an :class:`EmailMessage` object is that of " +"an ordered dictionary of headers coupled with a *payload* that represents " +"the :rfc:`5322` body of the message, which might be a list of sub-" +"``EmailMessage`` objects. In addition to the normal dictionary methods for " +"accessing the header names and values, there are methods for accessing " +"specialized information from the headers (for example the MIME content " +"type), for operating on the payload, for generating a serialized version of " +"the message, and for recursively walking over the object tree." +msgstr "" + +#: ../Doc/library/email.message.rst:40 +msgid "" +"The :class:`EmailMessage` dictionary-like interface is indexed by the header " +"names, which must be ASCII values. The values of the dictionary are strings " +"with some extra methods. Headers are stored and returned in case-preserving " +"form, but field names are matched case-insensitively. Unlike a real dict, " +"there is an ordering to the keys, and there can be duplicate keys. " +"Additional methods are provided for working with headers that have duplicate " +"keys." +msgstr "" + +#: ../Doc/library/email.message.rst:47 +msgid "" +"The *payload* is either a string or bytes object, in the case of simple " +"message objects, or a list of :class:`EmailMessage` objects, for MIME " +"container documents such as :mimetype:`multipart/\\*` and :mimetype:`message/" +"rfc822` message objects." +msgstr "" + +#: ../Doc/library/email.message.rst:55 +msgid "" +"If *policy* is specified use the rules it specifies to udpate and serialize " +"the representation of the message. If *policy* is not set, use the :class:" +"`~email.policy.default` policy, which follows the rules of the email RFCs " +"except for line endings (instead of the RFC mandated ``\\r\\n``, it uses the " +"Python standard ``\\n`` line endings). For more information see the :mod:" +"`~email.policy` documentation." +msgstr "" + +#: ../Doc/library/email.message.rst:64 +msgid "" +"Return the entire message flattened as a string. When optional *unixfrom* " +"is true, the envelope header is included in the returned string. *unixfrom* " +"defaults to ``False``. For backward compabitility with the base :class:" +"`~email.message.Message` class *maxheaderlen* is accepted, but defaults to " +"``None``, which means that by default the line length is controlled by the :" +"attr:`~email.policy.EmailPolicy.max_line_length` of the policy. The " +"*policy* argument may be used to override the default policy obtained from " +"the message instance. This can be used to control some of the formatting " +"produced by the method, since the specified *policy* will be passed to the :" +"class:`~email.generator.Generator`." +msgstr "" + +#: ../Doc/library/email.message.rst:76 ../Doc/library/email.message.rst:114 +msgid "" +"Flattening the message may trigger changes to the :class:`EmailMessage` if " +"defaults need to be filled in to complete the transformation to a string " +"(for example, MIME boundaries may be generated or modified)." +msgstr "" + +#: ../Doc/library/email.message.rst:80 +msgid "" +"Note that this method is provided as a convenience and may not be the most " +"useful way to serialize messages in your application, especially if you are " +"dealing with multiple messages. See :class:`email.generator.Generator` for " +"a more flexible API for serializing messages. Note also that this method is " +"restricted to producing messages serialized as \"7 bit clean\" when :attr:" +"`~email.policy.EmailPolicy.utf8` is ``False``, which is the default." +msgstr "" + +#: ../Doc/library/email.message.rst:88 +msgid "" +"the default behavior when *maxheaderlen* is not specified was changed from " +"defaulting to 0 to defaulting to the value of *max_line_length* from the " +"policy." +msgstr "" + +#: ../Doc/library/email.message.rst:95 +msgid "" +"Equivalent to `as_string(policy=self.policy.clone(utf8=True)`. Allows " +"``str(msg)`` to produce a string containing the serialized message in a " +"readable format." +msgstr "" + +#: ../Doc/library/email.message.rst:99 +msgid "" +"the method was changed to use ``utf8=True``, thus producing an :rfc:`6531`-" +"like message representation, instead of being a direct alias for :meth:" +"`as_string`." +msgstr "" + +#: ../Doc/library/email.message.rst:106 +msgid "" +"Return the entire message flattened as a bytes object. When optional " +"*unixfrom* is true, the envelope header is included in the returned string. " +"*unixfrom* defaults to ``False``. The *policy* argument may be used to " +"override the default policy obtained from the message instance. This can be " +"used to control some of the formatting produced by the method, since the " +"specified *policy* will be passed to the :class:`~email.generator." +"BytesGenerator`." +msgstr "" + +#: ../Doc/library/email.message.rst:118 +msgid "" +"Note that this method is provided as a convenience and may not be the most " +"useful way to serialize messages in your application, especially if you are " +"dealing with multiple messages. See :class:`email.generator.BytesGenerator` " +"for a more flexible API for serializing messages." +msgstr "" + +#: ../Doc/library/email.message.rst:127 +msgid "" +"Equivalent to :meth:`.as_bytes()`. Allows ``bytes(msg)`` to produce a bytes " +"object containing the serialized message." +msgstr "" + +#: ../Doc/library/email.message.rst:133 +msgid "" +"Return ``True`` if the message's payload is a list of sub-\\ :class:" +"`EmailMessage` objects, otherwise return ``False``. When :meth:" +"`is_multipart` returns ``False``, the payload should be a string object " +"(which might be a CTE encoded binary payload). Note that :meth:" +"`is_multipart` returning ``True`` does not necessarily mean that \"msg." +"get_content_maintype() == 'multipart'\" will return the ``True``. For " +"example, ``is_multipart`` will return ``True`` when the :class:" +"`EmailMessage` is of type ``message/rfc822``." +msgstr "" + +#: ../Doc/library/email.message.rst:145 +msgid "" +"Set the message's envelope header to *unixfrom*, which should be a string. " +"(See :class:`~mailbox.mboxMessage` for a brief description of this header.)" +msgstr "" + +#: ../Doc/library/email.message.rst:156 +msgid "" +"The following methods implement the mapping-like interface for accessing the " +"message's headers. Note that there are some semantic differences between " +"these methods and a normal mapping (i.e. dictionary) interface. For " +"example, in a dictionary there are no duplicate keys, but here there may be " +"duplicate message headers. Also, in dictionaries there is no guaranteed " +"order to the keys returned by :meth:`keys`, but in an :class:`EmailMessage` " +"object, headers are always returned in the order they appeared in the " +"original message, or in which they were added to the message later. Any " +"header deleted and then re-added is always appended to the end of the header " +"list." +msgstr "" + +#: ../Doc/library/email.message.rst:167 +msgid "" +"These semantic differences are intentional and are biased toward convenience " +"in the most common use cases." +msgstr "" + +#: ../Doc/library/email.message.rst:181 +msgid "" +"Return true if the message object has a field named *name*. Matching is done " +"without regard to case and *name* does not include the trailing colon. Used " +"for the ``in`` operator. For example::" +msgstr "" + +#: ../Doc/library/email.message.rst:191 +msgid "" +"Return the value of the named header field. *name* does not include the " +"colon field separator. If the header is missing, ``None`` is returned; a :" +"exc:`KeyError` is never raised." +msgstr "" + +#: ../Doc/library/email.message.rst:195 +msgid "" +"Note that if the named field appears more than once in the message's " +"headers, exactly which of those field values will be returned is undefined. " +"Use the :meth:`get_all` method to get the values of all the extant headers " +"named *name*." +msgstr "" + +#: ../Doc/library/email.message.rst:200 +msgid "" +"Using the standard (non-``compat32``) policies, the returned value is an " +"instance of a subclass of :class:`email.headerregistry.BaseHeader`." +msgstr "" + +#: ../Doc/library/email.message.rst:206 +msgid "" +"Add a header to the message with field name *name* and value *val*. The " +"field is appended to the end of the message's existing headers." +msgstr "" + +#: ../Doc/library/email.message.rst:216 +msgid "" +"If the :mod:`policy` defines certain haders to be unique (as the standard " +"policies do), this method may raise a :exc:`ValueError` when an attempt is " +"made to assign a value to such a header when one already exists. This " +"behavior is intentional for consistency's sake, but do not depend on it as " +"we may choose to make such assignments do an automatic deletion of the " +"existing header in the future." +msgstr "" + +#: ../Doc/library/email.message.rst:249 +msgid "" +"Return the value of the named header field. This is identical to :meth:" +"`__getitem__` except that optional *failobj* is returned if the named header " +"is missing (*failobj* defaults to ``None``)." +msgstr "" + +#: ../Doc/library/email.message.rst:254 +msgid "Here are some additional useful header related methods:" +msgstr "" + +#: ../Doc/library/email.message.rst:271 +msgid "" +"For each item in the keyword argument dictionary *_params*, the key is taken " +"as the parameter name, with underscores converted to dashes (since dashes " +"are illegal in Python identifiers). Normally, the parameter will be added " +"as ``key=\"value\"`` unless the value is ``None``, in which case only the " +"key will be added." +msgstr "" + +#: ../Doc/library/email.message.rst:277 +msgid "" +"If the value contains non-ASCII characters, the charset and language may be " +"explicitly controlled by specifing the value as a three tuple in the format " +"``(CHARSET, LANGUAGE, VALUE)``, where ``CHARSET`` is a string naming the " +"charset to be used to encode the value, ``LANGUAGE`` can usually be set to " +"``None`` or the empty string (see :rfc:`2231` for other possibilities), and " +"``VALUE`` is the string value containing non-ASCII code points. If a three " +"tuple is not passed and the value contains non-ASCII characters, it is " +"automatically encoded in :rfc:`2231` format using a ``CHARSET`` of ``utf-8`` " +"and a ``LANGUAGE`` of ``None``." +msgstr "" + +#: ../Doc/library/email.message.rst:287 ../Doc/library/gettext.rst:380 +msgid "Here is an example::" +msgstr "" + +#: ../Doc/library/email.message.rst:295 +msgid "An example of the extended interface with non-ASCII characters::" +msgstr "" + +#: ../Doc/library/email.message.rst:303 +msgid "" +"Replace a header. Replace the first header found in the message that " +"matches *_name*, retaining header order and field name case of the original " +"header. If no matching header is found, raise a :exc:`KeyError`." +msgstr "" + +#: ../Doc/library/email.message.rst:311 +msgid "" +"Return the message's content type, coerced to lower case of the form :" +"mimetype:`maintype/subtype`. If there is no :mailheader:`Content-Type` " +"header in the message return the value returned by :meth:" +"`get_default_type`. If the :mailheader:`Content-Type` header is invalid, " +"return ``text/plain``." +msgstr "" + +#: ../Doc/library/email.message.rst:317 +msgid "" +"(According to :rfc:`2045`, messages always have a default type, :meth:" +"`get_content_type` will always return a value. :rfc:`2045` defines a " +"message's default type to be :mimetype:`text/plain` unless it appears inside " +"a :mimetype:`multipart/digest` container, in which case it would be :" +"mimetype:`message/rfc822`. If the :mailheader:`Content-Type` header has an " +"invalid type specification, :rfc:`2045` mandates that the default type be :" +"mimetype:`text/plain`.)" +msgstr "" + +#: ../Doc/library/email.message.rst:348 +msgid "" +"Set the default content type. *ctype* should either be :mimetype:`text/" +"plain` or :mimetype:`message/rfc822`, although this is not enforced. The " +"default content type is not stored in the :mailheader:`Content-Type` header, " +"so it only affects the return value of the ``get_content_type`` methods when " +"no :mailheader:`Content-Type` header is present in the message." +msgstr "" + +#: ../Doc/library/email.message.rst:359 +msgid "" +"Set a parameter in the :mailheader:`Content-Type` header. If the parameter " +"already exists in the header, replace its value with *value*. When *header* " +"is ``Content-Type`` (the default) and the header does not yet exist in the " +"message, add it, set its value to :mimetype:`text/plain`, and append the new " +"parameter value. Optional *header* specifies an alternative header to :" +"mailheader:`Content-Type`." +msgstr "" + +#: ../Doc/library/email.message.rst:366 +msgid "" +"If the value contains non-ASCII characters, the charset and language may be " +"explicity specified using the optional *charset* and *language* parameters. " +"Optional *language* specifies the :rfc:`2231` language, defaulting to the " +"empty string. Both *charset* and *language* should be strings. The default " +"is to use the ``utf8`` *charset* and ``None`` for the *language*." +msgstr "" + +#: ../Doc/library/email.message.rst:377 ../Doc/library/email.message.rst:394 +msgid "" +"Use of the *requote* parameter with :class:`EmailMessage` objects is " +"deprecated." +msgstr "" + +#: ../Doc/library/email.message.rst:380 +msgid "" +"Note that existing parameter values of headers may be accessed through the :" +"attr:`~email.headerregistry.BaseHeader.params` attribute of the header value " +"(for example, ``msg['Content-Type'].params['charset']``." +msgstr "" + +#: ../Doc/library/email.message.rst:389 +msgid "" +"Remove the given parameter completely from the :mailheader:`Content-Type` " +"header. The header will be re-written in place without the parameter or its " +"value. Optional *header* specifies an alternative to :mailheader:`Content-" +"Type`." +msgstr "" + +#: ../Doc/library/email.message.rst:424 +msgid "" +"Note that using this method is subtly different from deleting the old :" +"mailheader:`Content-Type` header and adding a new one with the new boundary " +"via :meth:`add_header`, because :meth:`set_boundary` preserves the order of " +"the :mailheader:`Content-Type` header in the list of headers." +msgstr "" + +#: ../Doc/library/email.message.rst:444 +msgid "" +"Each item in the list will be a string which is the value of the ``charset`` " +"parameter in the :mailheader:`Content-Type` header for the represented " +"subpart. If the subpart has no :mailheader:`Content-Type` header, no " +"``charset`` parameter, or is not of the :mimetype:`text` main MIME type, " +"then that item in the returned list will be *failobj*." +msgstr "" + +#: ../Doc/library/email.message.rst:453 +msgid "" +"Return ``True`` if there is a :mailheader:`Content-Disposition` header and " +"its (case insensitive) value is ``attachment``, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/email.message.rst:456 +msgid "" +"is_attachment is now a method instead of a property, for consistency with :" +"meth:`~email.message.Message.is_multipart`." +msgstr "" + +#: ../Doc/library/email.message.rst:471 +msgid "" +"The following methods relate to interrogating and manipulating the content " +"(payload) of the message." +msgstr "" + +#: ../Doc/library/email.message.rst:538 +msgid "" +"Return the MIME part that is the best candidate to be the \"body\" of the " +"message." +msgstr "" + +#: ../Doc/library/email.message.rst:541 +msgid "" +"*preferencelist* must be a sequence of strings from the set ``related``, " +"``html``, and ``plain``, and indicates the order of preference for the " +"content type of the part returned." +msgstr "" + +#: ../Doc/library/email.message.rst:545 +msgid "" +"Start looking for candidate matches with the object on which the " +"``get_body`` method is called." +msgstr "" + +#: ../Doc/library/email.message.rst:548 +msgid "" +"If ``related`` is not included in *preferencelist*, consider the root part " +"(or subpart of the root part) of any related encountered as a candidate if " +"the (sub-)part matches a preference." +msgstr "" + +#: ../Doc/library/email.message.rst:552 +msgid "" +"When encountering a ``multipart/related``, check the ``start`` parameter and " +"if a part with a matching :mailheader:`Content-ID` is found, consider only " +"it when looking for candidate matches. Otherwise consider only the first " +"(default root) part of the ``multipart/related``." +msgstr "" + +#: ../Doc/library/email.message.rst:557 +msgid "" +"If a part has a :mailheader:`Content-Disposition` header, only consider the " +"part a candidate match if the value of the header is ``inline``." +msgstr "" + +#: ../Doc/library/email.message.rst:560 +msgid "" +"If none of the candidates matches any of the preferences in *preferneclist*, " +"return ``None``." +msgstr "" + +#: ../Doc/library/email.message.rst:563 +msgid "" +"Notes: (1) For most applications the only *preferencelist* combinations that " +"really make sense are ``('plain',)``, ``('html', 'plain')``, and the default " +"``('related', 'html', 'plain')``. (2) Because matching starts with the " +"object on which ``get_body`` is called, calling ``get_body`` on a " +"``multipart/related`` will return the object itself unless *preferencelist* " +"has a non-default value. (3) Messages (or message parts) that do not specify " +"a :mailheader:`Content-Type` or whose :mailheader:`Content-Type` header is " +"invalid will be treated as if they are of type ``text/plain``, which may " +"occasionally cause ``get_body`` to return unexpected results." +msgstr "" + +#: ../Doc/library/email.message.rst:577 +msgid "" +"Return an iterator over all of the immediate sub-parts of the message that " +"are not candidate \"body\" parts. That is, skip the first occurrence of " +"each of ``text/plain``, ``text/html``, ``multipart/related``, or ``multipart/" +"alternative`` (unless they are explicitly marked as attachments via :" +"mailheader:`Content-Disposition: attachment`), and return all remaining " +"parts. When applied directly to a ``multipart/related``, return an iterator " +"over the all the related parts except the root part (ie: the part pointed to " +"by the ``start`` parameter, or the first part if there is no ``start`` " +"parameter or the ``start`` parameter doesn't match the :mailheader:`Content-" +"ID` of any of the parts). When applied directly to a ``multipart/" +"alternative`` or a non-``multipart``, return an empty iterator." +msgstr "" + +#: ../Doc/library/email.message.rst:593 +msgid "" +"Return an iterator over all of the immediate sub-parts of the message, which " +"will be empty for a non-``multipart``. (See also :meth:`~email.message." +"EmailMessage.walk`.)" +msgstr "" + +#: ../Doc/library/email.message.rst:600 +msgid "" +"Call the :meth:`~email.contentmanager.ContentManager.get_content` method of " +"the *content_manager*, passing self as the message object, and passing along " +"any other arguments or keywords as additional arguments. If " +"*content_manager* is not specified, use the ``content_manager`` specified by " +"the current :mod:`~email.policy`." +msgstr "" + +#: ../Doc/library/email.message.rst:609 +msgid "" +"Call the :meth:`~email.contentmanager.ContentManager.set_content` method of " +"the *content_manager*, passing self as the message object, and passing along " +"any other arguments or keywords as additional arguments. If " +"*content_manager* is not specified, use the ``content_manager`` specified by " +"the current :mod:`~email.policy`." +msgstr "" + +#: ../Doc/library/email.message.rst:618 +msgid "" +"Convert a non-``multipart`` message into a ``multipart/related`` message, " +"moving any existing :mailheader:`Content-` headers and payload into a (new) " +"first part of the ``multipart``. If *boundary* is specified, use it as the " +"boundary string in the multipart, otherwise leave the boundary to be " +"automatically created when it is needed (for example, when the message is " +"serialized)." +msgstr "" + +#: ../Doc/library/email.message.rst:628 +msgid "" +"Convert a non-``multipart`` or a ``multipart/related`` into a ``multipart/" +"alternative``, moving any existing :mailheader:`Content-` headers and " +"payload into a (new) first part of the ``multipart``. If *boundary* is " +"specified, use it as the boundary string in the multipart, otherwise leave " +"the boundary to be automatically created when it is needed (for example, " +"when the message is serialized)." +msgstr "" + +#: ../Doc/library/email.message.rst:638 +msgid "" +"Convert a non-``multipart``, a ``multipart/related``, or a ``multipart-" +"alternative`` into a ``multipart/mixed``, moving any existing :mailheader:" +"`Content-` headers and payload into a (new) first part of the " +"``multipart``. If *boundary* is specified, use it as the boundary string in " +"the multipart, otherwise leave the boundary to be automatically created when " +"it is needed (for example, when the message is serialized)." +msgstr "" + +#: ../Doc/library/email.message.rst:648 +msgid "" +"If the message is a ``multipart/related``, create a new message object, pass " +"all of the arguments to its :meth:`set_content` method, and :meth:`~email." +"message.Message.attach` it to the ``multipart``. If the message is a non-" +"``multipart``, call :meth:`make_related` and then proceed as above. If the " +"message is any other type of ``multipart``, raise a :exc:`TypeError`. If " +"*content_manager* is not specified, use the ``content_manager`` specified by " +"the current :mod:`~email.policy`. If the added part has no :mailheader:" +"`Content-Disposition` header, add one with the value ``inline``." +msgstr "" + +#: ../Doc/library/email.message.rst:661 +msgid "" +"If the message is a ``multipart/alternative``, create a new message object, " +"pass all of the arguments to its :meth:`set_content` method, and :meth:" +"`~email.message.Message.attach` it to the ``multipart``. If the message is " +"a non-``multipart`` or ``multipart/related``, call :meth:`make_alternative` " +"and then proceed as above. If the message is any other type of " +"``multipart``, raise a :exc:`TypeError`. If *content_manager* is not " +"specified, use the ``content_manager`` specified by the current :mod:`~email." +"policy`." +msgstr "" + +#: ../Doc/library/email.message.rst:673 +msgid "" +"If the message is a ``multipart/mixed``, create a new message object, pass " +"all of the arguments to its :meth:`set_content` method, and :meth:`~email." +"message.Message.attach` it to the ``multipart``. If the message is a non-" +"``multipart``, ``multipart/related``, or ``multipart/alternative``, call :" +"meth:`make_mixed` and then proceed as above. If *content_manager* is not " +"specified, use the ``content_manager`` specified by the current :mod:`~email." +"policy`. If the added part has no :mailheader:`Content-Disposition` header, " +"add one with the value ``attachment``. This method can be used both for " +"explicit attachments (:mailheader:`Content-Disposition: attachment` and " +"``inline`` attachments (:mailheader:`Content-Disposition: inline`), by " +"passing appropriate options to the ``content_manager``." +msgstr "" + +#: ../Doc/library/email.message.rst:689 +msgid "Remove the payload and all of the headers." +msgstr "" + +#: ../Doc/library/email.message.rst:694 +msgid "" +"Remove the payload and all of the :exc:`Content-` headers, leaving all other " +"headers intact and in their original order." +msgstr "" + +#: ../Doc/library/email.message.rst:698 +msgid ":class:`EmailMessage` objects have the following instance attributes:" +msgstr "" + +#: ../Doc/library/email.message.rst:726 +msgid "" +"The *epilogue* attribute acts the same way as the *preamble* attribute, " +"except that it contains text that appears between the last boundary and the " +"end of the message. As with the :attr:`~EmailMessage.preamble`, if there is " +"no epilog text this attribute will be ``None``." +msgstr "" + +#: ../Doc/library/email.message.rst:741 +msgid "" +"This class represents a subpart of a MIME message. It is identical to :" +"class:`EmailMessage`, except that no :mailheader:`MIME-Version` headers are " +"added when :meth:`~EmailMessage.set_content` is called, since sub-parts do " +"not need their own :mailheader:`MIME-Version` headers." +msgstr "" + +#: ../Doc/library/email.message.rst:749 +msgid "" +"Oringally added in 3.4 as a :term:`provisional module `. Docs for legacy message class moved to :ref:`compat32_message`." +msgstr "" + +#: ../Doc/library/email.mime.rst:2 +msgid ":mod:`email.mime`: Creating email and MIME objects from scratch" +msgstr "" + +#: ../Doc/library/email.mime.rst:7 +msgid "**Source code:** :source:`Lib/email/mime/`" +msgstr "" + +#: ../Doc/library/email.mime.rst:11 +msgid "" +"This module is part of the legacy (``Compat32``) email API. Its " +"functionality is partially replaced by the :mod:`~email.contentmanager` in " +"the new API, but in certain applications these classes may still be useful, " +"even in non-legacy code." +msgstr "" + +#: ../Doc/library/email.mime.rst:16 +msgid "" +"Ordinarily, you get a message object structure by passing a file or some " +"text to a parser, which parses the text and returns the root message " +"object. However you can also build a complete message structure from " +"scratch, or even individual :class:`~email.message.Message` objects by " +"hand. In fact, you can also take an existing structure and add new :class:" +"`~email.message.Message` objects, move them around, etc. This makes a very " +"convenient interface for slicing-and-dicing MIME messages." +msgstr "" + +#: ../Doc/library/email.mime.rst:24 +msgid "" +"You can create a new object structure by creating :class:`~email.message." +"Message` instances, adding attachments and all the appropriate headers " +"manually. For MIME messages though, the :mod:`email` package provides some " +"convenient subclasses to make things easier." +msgstr "" + +#: ../Doc/library/email.mime.rst:29 +msgid "Here are the classes:" +msgstr "" + +#: ../Doc/library/email.mime.rst:35 +msgid "Module: :mod:`email.mime.base`" +msgstr "" + +#: ../Doc/library/email.mime.rst:37 +msgid "" +"This is the base class for all the MIME-specific subclasses of :class:" +"`~email.message.Message`. Ordinarily you won't create instances " +"specifically of :class:`MIMEBase`, although you could. :class:`MIMEBase` is " +"provided primarily as a convenient base class for more specific MIME-aware " +"subclasses." +msgstr "" + +#: ../Doc/library/email.mime.rst:43 +msgid "" +"*_maintype* is the :mailheader:`Content-Type` major type (e.g. :mimetype:" +"`text` or :mimetype:`image`), and *_subtype* is the :mailheader:`Content-" +"Type` minor type (e.g. :mimetype:`plain` or :mimetype:`gif`). *_params* is " +"a parameter key/value dictionary and is passed directly to :meth:`Message." +"add_header `." +msgstr "" + +#: ../Doc/library/email.mime.rst:49 +msgid "" +"If *policy* is specified, (defaults to the :class:`compat32 ` policy) it will be passed to :class:`~email.message.Message`." +msgstr "" + +#: ../Doc/library/email.mime.rst:53 +msgid "" +"The :class:`MIMEBase` class always adds a :mailheader:`Content-Type` header " +"(based on *_maintype*, *_subtype*, and *_params*), and a :mailheader:`MIME-" +"Version` header (always set to ``1.0``)." +msgstr "" + +#: ../Doc/library/email.mime.rst:57 ../Doc/library/email.mime.rst:104 +#: ../Doc/library/email.mime.rst:135 ../Doc/library/email.mime.rst:169 +#: ../Doc/library/email.mime.rst:204 ../Doc/library/email.mime.rst:224 +#: ../Doc/library/email.mime.rst:258 +msgid "Added *policy* keyword-only parameter." +msgstr "" + +#: ../Doc/library/email.mime.rst:65 +msgid "Module: :mod:`email.mime.nonmultipart`" +msgstr "" + +#: ../Doc/library/email.mime.rst:67 +msgid "" +"A subclass of :class:`~email.mime.base.MIMEBase`, this is an intermediate " +"base class for MIME messages that are not :mimetype:`multipart`. The " +"primary purpose of this class is to prevent the use of the :meth:`~email." +"message.Message.attach` method, which only makes sense for :mimetype:" +"`multipart` messages. If :meth:`~email.message.Message.attach` is called, " +"a :exc:`~email.errors.MultipartConversionError` exception is raised." +msgstr "" + +#: ../Doc/library/email.mime.rst:80 +msgid "Module: :mod:`email.mime.multipart`" +msgstr "" + +#: ../Doc/library/email.mime.rst:82 +msgid "" +"A subclass of :class:`~email.mime.base.MIMEBase`, this is an intermediate " +"base class for MIME messages that are :mimetype:`multipart`. Optional " +"*_subtype* defaults to :mimetype:`mixed`, but can be used to specify the " +"subtype of the message. A :mailheader:`Content-Type` header of :mimetype:" +"`multipart/_subtype` will be added to the message object. A :mailheader:" +"`MIME-Version` header will also be added." +msgstr "" + +#: ../Doc/library/email.mime.rst:89 +msgid "" +"Optional *boundary* is the multipart boundary string. When ``None`` (the " +"default), the boundary is calculated when needed (for example, when the " +"message is serialized)." +msgstr "" + +#: ../Doc/library/email.mime.rst:93 +msgid "" +"*_subparts* is a sequence of initial subparts for the payload. It must be " +"possible to convert this sequence to a list. You can always attach new " +"subparts to the message by using the :meth:`Message.attach ` method." +msgstr "" + +#: ../Doc/library/email.mime.rst:98 ../Doc/library/email.mime.rst:131 +#: ../Doc/library/email.mime.rst:165 ../Doc/library/email.mime.rst:199 +#: ../Doc/library/email.mime.rst:222 ../Doc/library/email.mime.rst:253 +msgid "" +"Optional *policy* argument defaults to :class:`compat32 `." +msgstr "" + +#: ../Doc/library/email.mime.rst:100 +msgid "" +"Additional parameters for the :mailheader:`Content-Type` header are taken " +"from the keyword arguments, or passed into the *_params* argument, which is " +"a keyword dictionary." +msgstr "" + +#: ../Doc/library/email.mime.rst:113 +msgid "Module: :mod:`email.mime.application`" +msgstr "" + +#: ../Doc/library/email.mime.rst:115 +msgid "" +"A subclass of :class:`~email.mime.nonmultipart.MIMENonMultipart`, the :class:" +"`MIMEApplication` class is used to represent MIME message objects of major " +"type :mimetype:`application`. *_data* is a string containing the raw byte " +"data. Optional *_subtype* specifies the MIME subtype and defaults to :" +"mimetype:`octet-stream`." +msgstr "" + +#: ../Doc/library/email.mime.rst:121 +msgid "" +"Optional *_encoder* is a callable (i.e. function) which will perform the " +"actual encoding of the data for transport. This callable takes one " +"argument, which is the :class:`MIMEApplication` instance. It should use :" +"meth:`~email.message.Message.get_payload` and :meth:`~email.message.Message." +"set_payload` to change the payload to encoded form. It should also add any :" +"mailheader:`Content-Transfer-Encoding` or other headers to the message " +"object as necessary. The default encoding is base64. See the :mod:`email." +"encoders` module for a list of the built-in encoders." +msgstr "" + +#: ../Doc/library/email.mime.rst:133 ../Doc/library/email.mime.rst:167 +msgid "*_params* are passed straight through to the base class constructor." +msgstr "" + +#: ../Doc/library/email.mime.rst:144 +msgid "Module: :mod:`email.mime.audio`" +msgstr "" + +#: ../Doc/library/email.mime.rst:146 +msgid "" +"A subclass of :class:`~email.mime.nonmultipart.MIMENonMultipart`, the :class:" +"`MIMEAudio` class is used to create MIME message objects of major type :" +"mimetype:`audio`. *_audiodata* is a string containing the raw audio data. " +"If this data can be decoded by the standard Python module :mod:`sndhdr`, " +"then the subtype will be automatically included in the :mailheader:`Content-" +"Type` header. Otherwise you can explicitly specify the audio subtype via the " +"*_subtype* argument. If the minor type could not be guessed and *_subtype* " +"was not given, then :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/email.mime.rst:155 +msgid "" +"Optional *_encoder* is a callable (i.e. function) which will perform the " +"actual encoding of the audio data for transport. This callable takes one " +"argument, which is the :class:`MIMEAudio` instance. It should use :meth:" +"`~email.message.Message.get_payload` and :meth:`~email.message.Message." +"set_payload` to change the payload to encoded form. It should also add any :" +"mailheader:`Content-Transfer-Encoding` or other headers to the message " +"object as necessary. The default encoding is base64. See the :mod:`email." +"encoders` module for a list of the built-in encoders." +msgstr "" + +#: ../Doc/library/email.mime.rst:178 +msgid "Module: :mod:`email.mime.image`" +msgstr "" + +#: ../Doc/library/email.mime.rst:180 +msgid "" +"A subclass of :class:`~email.mime.nonmultipart.MIMENonMultipart`, the :class:" +"`MIMEImage` class is used to create MIME message objects of major type :" +"mimetype:`image`. *_imagedata* is a string containing the raw image data. " +"If this data can be decoded by the standard Python module :mod:`imghdr`, " +"then the subtype will be automatically included in the :mailheader:`Content-" +"Type` header. Otherwise you can explicitly specify the image subtype via the " +"*_subtype* argument. If the minor type could not be guessed and *_subtype* " +"was not given, then :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/email.mime.rst:189 +msgid "" +"Optional *_encoder* is a callable (i.e. function) which will perform the " +"actual encoding of the image data for transport. This callable takes one " +"argument, which is the :class:`MIMEImage` instance. It should use :meth:" +"`~email.message.Message.get_payload` and :meth:`~email.message.Message." +"set_payload` to change the payload to encoded form. It should also add any :" +"mailheader:`Content-Transfer-Encoding` or other headers to the message " +"object as necessary. The default encoding is base64. See the :mod:`email." +"encoders` module for a list of the built-in encoders." +msgstr "" + +#: ../Doc/library/email.mime.rst:201 +msgid "" +"*_params* are passed straight through to the :class:`~email.mime.base." +"MIMEBase` constructor." +msgstr "" + +#: ../Doc/library/email.mime.rst:211 +msgid "Module: :mod:`email.mime.message`" +msgstr "" + +#: ../Doc/library/email.mime.rst:213 +msgid "" +"A subclass of :class:`~email.mime.nonmultipart.MIMENonMultipart`, the :class:" +"`MIMEMessage` class is used to create MIME objects of main type :mimetype:" +"`message`. *_msg* is used as the payload, and must be an instance of class :" +"class:`~email.message.Message` (or a subclass thereof), otherwise a :exc:" +"`TypeError` is raised." +msgstr "" + +#: ../Doc/library/email.mime.rst:219 +msgid "" +"Optional *_subtype* sets the subtype of the message; it defaults to :" +"mimetype:`rfc822`." +msgstr "" + +#: ../Doc/library/email.mime.rst:231 +msgid "Module: :mod:`email.mime.text`" +msgstr "" + +#: ../Doc/library/email.mime.rst:233 +msgid "" +"A subclass of :class:`~email.mime.nonmultipart.MIMENonMultipart`, the :class:" +"`MIMEText` class is used to create MIME objects of major type :mimetype:" +"`text`. *_text* is the string for the payload. *_subtype* is the minor type " +"and defaults to :mimetype:`plain`. *_charset* is the character set of the " +"text and is passed as an argument to the :class:`~email.mime.nonmultipart." +"MIMENonMultipart` constructor; it defaults to ``us-ascii`` if the string " +"contains only ``ascii`` code points, and ``utf-8`` otherwise. The " +"*_charset* parameter accepts either a string or a :class:`~email.charset." +"Charset` instance." +msgstr "" + +#: ../Doc/library/email.mime.rst:243 +msgid "" +"Unless the *_charset* argument is explicitly set to ``None``, the MIMEText " +"object created will have both a :mailheader:`Content-Type` header with a " +"``charset`` parameter, and a :mailheader:`Content-Transfer-Endcoding` " +"header. This means that a subsequent ``set_payload`` call will not result " +"in an encoded payload, even if a charset is passed in the ``set_payload`` " +"command. You can \"reset\" this behavior by deleting the ``Content-Transfer-" +"Encoding`` header, after which a ``set_payload`` call will automatically " +"encode the new payload (and add a new :mailheader:`Content-Transfer-" +"Encoding` header)." +msgstr "" + +#: ../Doc/library/email.mime.rst:255 +msgid "*_charset* also accepts :class:`~email.charset.Charset` instances." +msgstr "" + +#: ../Doc/library/email.parser.rst:2 +msgid ":mod:`email.parser`: Parsing email messages" +msgstr "" + +#: ../Doc/library/email.parser.rst:7 +msgid "**Source code:** :source:`Lib/email/parser.py`" +msgstr "" + +#: ../Doc/library/email.parser.rst:11 +msgid "" +"Message object structures can be created in one of two ways: they can be " +"created from whole cloth by creating an :class:`~email.message.EmailMessage` " +"object, adding headers using the dictionary interface, and adding payload(s) " +"using :meth:`~email.message.EmailMessage.set_content` and related methods, " +"or they can be created by parsing a serialized representation of the email " +"message." +msgstr "" + +#: ../Doc/library/email.parser.rst:18 +msgid "" +"The :mod:`email` package provides a standard parser that understands most " +"email document structures, including MIME documents. You can pass the " +"parser a bytes, string or file object, and the parser will return to you the " +"root :class:`~email.message.EmailMessage` instance of the object structure. " +"For simple, non-MIME messages the payload of this root object will likely be " +"a string containing the text of the message. For MIME messages, the root " +"object will return ``True`` from its :meth:`~email.message.EmailMessage." +"is_multipart` method, and the subparts can be accessed via the payload " +"manipulation methods, such as :meth:`~email.message.EmailMessage.get_body`, :" +"meth:`~email.message.EmailMessage.iter_parts`, and :meth:`~email.message." +"EmailMessage.walk`." +msgstr "" + +#: ../Doc/library/email.parser.rst:30 +msgid "" +"There are actually two parser interfaces available for use, the :class:" +"`Parser` API and the incremental :class:`FeedParser` API. The :class:" +"`Parser` API is most useful if you have the entire text of the message in " +"memory, or if the entire message lives in a file on the file system. :class:" +"`FeedParser` is more appropriate when you are reading the message from a " +"stream which might block waiting for more input (such as reading an email " +"message from a socket). The :class:`FeedParser` can consume and parse the " +"message incrementally, and only returns the root object when you close the " +"parser." +msgstr "" + +#: ../Doc/library/email.parser.rst:39 +msgid "" +"Note that the parser can be extended in limited ways, and of course you can " +"implement your own parser completely from scratch. All of the logic that " +"connects the :mod:`email` package's bundled parser and the :class:`~email." +"message.EmailMessage` class is embodied in the :mod:`policy` class, so a " +"custom parser can create message object trees any way it finds necessary by " +"implementing custom versions of the appropriate :mod:`policy` methods." +msgstr "" + +#: ../Doc/library/email.parser.rst:49 +msgid "FeedParser API" +msgstr "" + +#: ../Doc/library/email.parser.rst:51 +msgid "" +"The :class:`BytesFeedParser`, imported from the :mod:`email.feedparser` " +"module, provides an API that is conducive to incremental parsing of email " +"messages, such as would be necessary when reading the text of an email " +"message from a source that can block (such as a socket). The :class:" +"`BytesFeedParser` can of course be used to parse an email message fully " +"contained in a :term:`bytes-like object`, string, or file, but the :class:" +"`BytesParser` API may be more convenient for such use cases. The semantics " +"and results of the two parser APIs are identical." +msgstr "" + +#: ../Doc/library/email.parser.rst:60 +msgid "" +"The :class:`BytesFeedParser`'s API is simple; you create an instance, feed " +"it a bunch of bytes until there's no more to feed it, then close the parser " +"to retrieve the root message object. The :class:`BytesFeedParser` is " +"extremely accurate when parsing standards-compliant messages, and it does a " +"very good job of parsing non-compliant messages, providing information about " +"how a message was deemed broken. It will populate a message object's :attr:" +"`~email.message.EmailMessage.defects` attribute with a list of any problems " +"it found in a message. See the :mod:`email.errors` module for the list of " +"defects that it can find." +msgstr "" + +#: ../Doc/library/email.parser.rst:70 +msgid "Here is the API for the :class:`BytesFeedParser`:" +msgstr "" + +#: ../Doc/library/email.parser.rst:75 +msgid "" +"Create a :class:`BytesFeedParser` instance. Optional *_factory* is a no-" +"argument callable; if not specified use the :attr:`~email.policy.Policy." +"message_factory` from the *policy*. Call *_factory* whenever a new message " +"object is needed." +msgstr "" + +#: ../Doc/library/email.parser.rst:80 +msgid "" +"If *policy* is specified use the rules it specifies to update the " +"representation of the message. If *policy* is not set, use the :class:" +"`compat32 ` policy, which maintains backward " +"compatibility with the Python 3.2 version of the email package and provides :" +"class:`~email.message.Message` as the default factory. All other policies " +"provide :class:`~email.message.EmailMessage` as the default *_factory*. For " +"more information on what else *policy* controls, see the :mod:`~email." +"policy` documentation." +msgstr "" + +#: ../Doc/library/email.parser.rst:89 ../Doc/library/email.parser.rst:145 +msgid "" +"Note: **The policy keyword should always be specified**; The default will " +"change to :data:`email.policy.default` in a future version of Python." +msgstr "" + +#: ../Doc/library/email.parser.rst:95 +msgid "_factory defaults to the policy ``message_factory``." +msgstr "" + +#: ../Doc/library/email.parser.rst:100 +msgid "" +"Feed the parser some more data. *data* should be a :term:`bytes-like " +"object` containing one or more lines. The lines can be partial and the " +"parser will stitch such partial lines together properly. The lines can have " +"any of the three common line endings: carriage return, newline, or carriage " +"return and newline (they can even be mixed)." +msgstr "" + +#: ../Doc/library/email.parser.rst:109 +msgid "" +"Complete the parsing of all previously fed data and return the root message " +"object. It is undefined what happens if :meth:`~feed` is called after this " +"method has been called." +msgstr "" + +#: ../Doc/library/email.parser.rst:116 +msgid "" +"Works like :class:`BytesFeedParser` except that the input to the :meth:" +"`~BytesFeedParser.feed` method must be a string. This is of limited " +"utility, since the only way for such a message to be valid is for it to " +"contain only ASCII text or, if :attr:`~email.policy.Policy.utf8` is " +"``True``, no binary attachments." +msgstr "" + +#: ../Doc/library/email.parser.rst:126 +msgid "Parser API" +msgstr "" + +#: ../Doc/library/email.parser.rst:128 +msgid "" +"The :class:`BytesParser` class, imported from the :mod:`email.parser` " +"module, provides an API that can be used to parse a message when the " +"complete contents of the message are available in a :term:`bytes-like " +"object` or file. The :mod:`email.parser` module also provides :class:" +"`Parser` for parsing strings, and header-only parsers, :class:" +"`BytesHeaderParser` and :class:`HeaderParser`, which can be used if you're " +"only interested in the headers of the message. :class:`BytesHeaderParser` " +"and :class:`HeaderParser` can be much faster in these situations, since they " +"do not attempt to parse the message body, instead setting the payload to the " +"raw body." +msgstr "" + +#: ../Doc/library/email.parser.rst:141 +msgid "" +"Create a :class:`BytesParser` instance. The *_class* and *policy* arguments " +"have the same meaning and sematnics as the *_factory* and *policy* arguments " +"of :class:`BytesFeedParser`." +msgstr "" + +#: ../Doc/library/email.parser.rst:148 +msgid "" +"Removed the *strict* argument that was deprecated in 2.4. Added the " +"*policy* keyword." +msgstr "" + +#: ../Doc/library/email.parser.rst:151 ../Doc/library/email.parser.rst:200 +#: ../Doc/library/email.parser.rst:280 +msgid "_class defaults to the policy ``message_factory``." +msgstr "" + +#: ../Doc/library/email.parser.rst:156 +msgid "" +"Read all the data from the binary file-like object *fp*, parse the resulting " +"bytes, and return the message object. *fp* must support both the :meth:`~io." +"IOBase.readline` and the :meth:`~io.IOBase.read` methods." +msgstr "" + +#: ../Doc/library/email.parser.rst:161 +msgid "" +"The bytes contained in *fp* must be formatted as a block of :rfc:`5322` (or, " +"if :attr:`~email.policy.Policy.utf8` is ``True``, :rfc:`6532`) style headers " +"and header continuation lines, optionally preceded by an envelope header. " +"The header block is terminated either by the end of the data or by a blank " +"line. Following the header block is the body of the message (which may " +"contain MIME-encoded subparts, including subparts with a :mailheader:" +"`Content-Transfer-Encoding` of ``8bit``." +msgstr "" + +#: ../Doc/library/email.parser.rst:169 +msgid "" +"Optional *headersonly* is a flag specifying whether to stop parsing after " +"reading the headers or not. The default is ``False``, meaning it parses the " +"entire contents of the file." +msgstr "" + +#: ../Doc/library/email.parser.rst:176 +msgid "" +"Similar to the :meth:`parse` method, except it takes a :term:`bytes-like " +"object` instead of a file-like object. Calling this method on a :term:" +"`bytes-like object` is equivalent to wrapping *bytes* in a :class:`~io." +"BytesIO` instance first and calling :meth:`parse`." +msgstr "" + +#: ../Doc/library/email.parser.rst:181 ../Doc/library/email.parser.rst:221 +msgid "Optional *headersonly* is as with the :meth:`parse` method." +msgstr "" + +#: ../Doc/library/email.parser.rst:188 +msgid "" +"Exactly like :class:`BytesParser`, except that *headersonly* defaults to " +"``True``." +msgstr "" + +#: ../Doc/library/email.parser.rst:196 +msgid "" +"This class is parallel to :class:`BytesParser`, but handles string input." +msgstr "" + +#: ../Doc/library/email.parser.rst:198 ../Doc/library/email.parser.rst:245 +#: ../Doc/library/email.parser.rst:258 ../Doc/library/email.parser.rst:268 +#: ../Doc/library/email.parser.rst:278 +msgid "Removed the *strict* argument. Added the *policy* keyword." +msgstr "" + +#: ../Doc/library/email.parser.rst:205 +msgid "" +"Read all the data from the text-mode file-like object *fp*, parse the " +"resulting text, and return the root message object. *fp* must support both " +"the :meth:`~io.TextIOBase.readline` and the :meth:`~io.TextIOBase.read` " +"methods on file-like objects." +msgstr "" + +#: ../Doc/library/email.parser.rst:210 +msgid "" +"Other than the text mode requirement, this method operates like :meth:" +"`BytesParser.parse`." +msgstr "" + +#: ../Doc/library/email.parser.rst:216 +msgid "" +"Similar to the :meth:`parse` method, except it takes a string object instead " +"of a file-like object. Calling this method on a string is equivalent to " +"wrapping *text* in a :class:`~io.StringIO` instance first and calling :meth:" +"`parse`." +msgstr "" + +#: ../Doc/library/email.parser.rst:226 +msgid "" +"Exactly like :class:`Parser`, except that *headersonly* defaults to ``True``." +msgstr "" + +#: ../Doc/library/email.parser.rst:230 +msgid "" +"Since creating a message object structure from a string or a file object is " +"such a common task, four functions are provided as a convenience. They are " +"available in the top-level :mod:`email` package namespace." +msgstr "" + +#: ../Doc/library/email.parser.rst:239 +msgid "" +"Return a message object structure from a :term:`bytes-like object`. This is " +"equivalent to ``BytesParser().parsebytes(s)``. Optional *_class* and " +"*strict* are interpreted as with the :class:`~email.parser.BytesParser` " +"class constructor." +msgstr "" + +#: ../Doc/library/email.parser.rst:252 +msgid "" +"Return a message object structure tree from an open binary :term:`file " +"object`. This is equivalent to ``BytesParser().parse(fp)``. *_class* and " +"*policy* are interpreted as with the :class:`~email.parser.BytesParser` " +"class constructor." +msgstr "" + +#: ../Doc/library/email.parser.rst:264 +msgid "" +"Return a message object structure from a string. This is equivalent to " +"``Parser().parsestr(s)``. *_class* and *policy* are interpreted as with " +"the :class:`~email.parser.Parser` class constructor." +msgstr "" + +#: ../Doc/library/email.parser.rst:274 +msgid "" +"Return a message object structure tree from an open :term:`file object`. " +"This is equivalent to ``Parser().parse(fp)``. *_class* and *policy* are " +"interpreted as with the :class:`~email.parser.Parser` class constructor." +msgstr "" + +#: ../Doc/library/email.parser.rst:283 +msgid "" +"Here's an example of how you might use :func:`message_from_bytes` at an " +"interactive Python prompt::" +msgstr "" + +#: ../Doc/library/email.parser.rst:291 +msgid "Additional notes" +msgstr "" + +#: ../Doc/library/email.parser.rst:293 +msgid "Here are some notes on the parsing semantics:" +msgstr "" + +#: ../Doc/library/email.parser.rst:295 +msgid "" +"Most non-\\ :mimetype:`multipart` type messages are parsed as a single " +"message object with a string payload. These objects will return ``False`` " +"for :meth:`~email.message.EmailMessage.is_multipart`, and :meth:`~email." +"message.EmailMessage.iter_parts` will yield an empty list." +msgstr "" + +#: ../Doc/library/email.parser.rst:300 +msgid "" +"All :mimetype:`multipart` type messages will be parsed as a container " +"message object with a list of sub-message objects for their payload. The " +"outer container message will return ``True`` for :meth:`~email.message." +"EmailMessage.is_multipart`, and :meth:`~email.message.EmailMessage." +"iter_parts` will yield a list of subparts." +msgstr "" + +#: ../Doc/library/email.parser.rst:306 +msgid "" +"Most messages with a content type of :mimetype:`message/\\*` (such as :" +"mimetype:`message/delivery-status` and :mimetype:`message/rfc822`) will also " +"be parsed as container object containing a list payload of length 1. Their :" +"meth:`~email.message.EmailMessage.is_multipart` method will return ``True``. " +"The single element yielded by :meth:`~email.message.EmailMessage.iter_parts` " +"will be a sub-message object." +msgstr "" + +#: ../Doc/library/email.parser.rst:313 +msgid "" +"Some non-standards-compliant messages may not be internally consistent about " +"their :mimetype:`multipart`\\ -edness. Such messages may have a :mailheader:" +"`Content-Type` header of type :mimetype:`multipart`, but their :meth:`~email." +"message.EmailMessage.is_multipart` method may return ``False``. If such " +"messages were parsed with the :class:`~email.parser.FeedParser`, they will " +"have an instance of the :class:`~email.errors." +"MultipartInvariantViolationDefect` class in their *defects* attribute list. " +"See :mod:`email.errors` for details." +msgstr "" + +#: ../Doc/library/email.policy.rst:2 +msgid ":mod:`email.policy`: Policy Objects" +msgstr "" + +#: ../Doc/library/email.policy.rst:12 +msgid "**Source code:** :source:`Lib/email/policy.py`" +msgstr "" + +#: ../Doc/library/email.policy.rst:16 +msgid "" +"The :mod:`email` package's prime focus is the handling of email messages as " +"described by the various email and MIME RFCs. However, the general format " +"of email messages (a block of header fields each consisting of a name " +"followed by a colon followed by a value, the whole block followed by a blank " +"line and an arbitrary 'body'), is a format that has found utility outside of " +"the realm of email. Some of these uses conform fairly closely to the main " +"email RFCs, some do not. Even when working with email, there are times when " +"it is desirable to break strict compliance with the RFCs, such as generating " +"emails that interoperate with email servers that do not themselves follow " +"the standards, or that implement extensions you want to use in ways that " +"violate the standards." +msgstr "" + +#: ../Doc/library/email.policy.rst:28 +msgid "" +"Policy objects give the email package the flexibility to handle all these " +"disparate use cases." +msgstr "" + +#: ../Doc/library/email.policy.rst:31 +msgid "" +"A :class:`Policy` object encapsulates a set of attributes and methods that " +"control the behavior of various components of the email package during use. :" +"class:`Policy` instances can be passed to various classes and methods in the " +"email package to alter the default behavior. The settable values and their " +"defaults are described below." +msgstr "" + +#: ../Doc/library/email.policy.rst:37 +msgid "" +"There is a default policy used by all classes in the email package. For all " +"of the :mod:`~email.parser` classes and the related convenience functions, " +"and for the :class:`~email.message.Message` class, this is the :class:" +"`Compat32` policy, via its corresponding pre-defined instance :const:" +"`compat32`. This policy provides for complete backward compatibility (in " +"some cases, including bug compatibility) with the pre-Python3.3 version of " +"the email package." +msgstr "" + +#: ../Doc/library/email.policy.rst:44 +msgid "" +"This default value for the *policy* keyword to :class:`~email.message." +"EmailMessage` is the :class:`EmailPolicy` policy, via its pre-defined " +"instance :data:`~default`." +msgstr "" + +#: ../Doc/library/email.policy.rst:48 +msgid "" +"When a :class:`~email.message.Message` or :class:`~email.message." +"EmailMessage` object is created, it acquires a policy. If the message is " +"created by a :mod:`~email.parser`, a policy passed to the parser will be the " +"policy used by the message it creates. If the message is created by the " +"program, then the policy can be specified when it is created. When a " +"message is passed to a :mod:`~email.generator`, the generator uses the " +"policy from the message by default, but you can also pass a specific policy " +"to the generator that will override the one stored on the message object." +msgstr "" + +#: ../Doc/library/email.policy.rst:57 +msgid "" +"The default value for the *policy* keyword for the :mod:`email.parser` " +"classes and the parser convenience functions **will be changing** in a " +"future version of Python. Therefore you should **always specify explicitly " +"which policy you want to use** when calling any of the classes and functions " +"described in the :mod:`~email.parser` module." +msgstr "" + +#: ../Doc/library/email.policy.rst:63 +msgid "" +"The first part of this documentation covers the features of :class:`Policy`, " +"an :term:`abstract base class` that defines the features that are common to " +"all policy objects, including :const:`compat32`. This includes certain hook " +"methods that are called internally by the email package, which a custom " +"policy could override to obtain different behavior. The second part " +"describes the concrete classes :class:`EmailPolicy` and :class:`Compat32`, " +"which implement the hooks that provide the standard behavior and the " +"backward compatible behavior and features, respectively." +msgstr "" + +#: ../Doc/library/email.policy.rst:72 +msgid "" +":class:`Policy` instances are immutable, but they can be cloned, accepting " +"the same keyword arguments as the class constructor and returning a new :" +"class:`Policy` instance that is a copy of the original but with the " +"specified attributes values changed." +msgstr "" + +#: ../Doc/library/email.policy.rst:77 +msgid "" +"As an example, the following code could be used to read an email message " +"from a file on disk and pass it to the system ``sendmail`` program on a Unix " +"system:" +msgstr "" + +#: ../Doc/library/email.policy.rst:113 +msgid "" +"Here we are telling :class:`~email.generator.BytesGenerator` to use the RFC " +"correct line separator characters when creating the binary string to feed " +"into ``sendmail's`` ``stdin``, where the default policy would use ``\\n`` " +"line separators." +msgstr "" + +#: ../Doc/library/email.policy.rst:118 +msgid "" +"Some email package methods accept a *policy* keyword argument, allowing the " +"policy to be overridden for that method. For example, the following code " +"uses the :meth:`~email.message.Message.as_bytes` method of the *msg* object " +"from the previous example and writes the message to a file using the native " +"line separators for the platform on which it is running::" +msgstr "" + +#: ../Doc/library/email.policy.rst:129 +msgid "" +"Policy objects can also be combined using the addition operator, producing a " +"policy object whose settings are a combination of the non-default values of " +"the summed objects::" +msgstr "" + +#: ../Doc/library/email.policy.rst:137 +msgid "" +"This operation is not commutative; that is, the order in which the objects " +"are added matters. To illustrate::" +msgstr "" + +#: ../Doc/library/email.policy.rst:152 +msgid "" +"This is the :term:`abstract base class` for all policy classes. It provides " +"default implementations for a couple of trivial methods, as well as the " +"implementation of the immutability property, the :meth:`clone` method, and " +"the constructor semantics." +msgstr "" + +#: ../Doc/library/email.policy.rst:157 +msgid "" +"The constructor of a policy class can be passed various keyword arguments. " +"The arguments that may be specified are any non-method properties on this " +"class, plus any additional non-method properties on the concrete class. A " +"value specified in the constructor will override the default value for the " +"corresponding attribute." +msgstr "" + +#: ../Doc/library/email.policy.rst:163 +msgid "" +"This class defines the following properties, and thus values for the " +"following may be passed in the constructor of any policy class:" +msgstr "" + +#: ../Doc/library/email.policy.rst:169 +msgid "" +"The maximum length of any line in the serialized output, not counting the " +"end of line character(s). Default is 78, per :rfc:`5322`. A value of ``0`` " +"or :const:`None` indicates that no line wrapping should be done at all." +msgstr "" + +#: ../Doc/library/email.policy.rst:177 +msgid "" +"The string to be used to terminate lines in serialized output. The default " +"is ``\\n`` because that's the internal end-of-line discipline used by " +"Python, though ``\\r\\n`` is required by the RFCs." +msgstr "" + +#: ../Doc/library/email.policy.rst:184 +msgid "" +"Controls the type of Content Transfer Encodings that may be or are required " +"to be used. The possible values are:" +msgstr "" + +#: ../Doc/library/email.policy.rst:190 +msgid "``7bit``" +msgstr "" + +#: ../Doc/library/email.policy.rst:190 +msgid "" +"all data must be \"7 bit clean\" (ASCII-only). This means that where " +"necessary data will be encoded using either quoted-printable or base64 " +"encoding." +msgstr "" + +#: ../Doc/library/email.policy.rst:194 +msgid "``8bit``" +msgstr "" + +#: ../Doc/library/email.policy.rst:194 +msgid "" +"data is not constrained to be 7 bit clean. Data in headers is still " +"required to be ASCII-only and so will be encoded (see :meth:`fold_binary` " +"and :attr:`~EmailPolicy.utf8` below for exceptions), but body parts may use " +"the ``8bit`` CTE." +msgstr "" + +#: ../Doc/library/email.policy.rst:200 +msgid "" +"A ``cte_type`` value of ``8bit`` only works with ``BytesGenerator``, not " +"``Generator``, because strings cannot contain binary data. If a " +"``Generator`` is operating under a policy that specifies ``cte_type=8bit``, " +"it will act as if ``cte_type`` is ``7bit``." +msgstr "" + +#: ../Doc/library/email.policy.rst:208 +msgid "" +"If :const:`True`, any defects encountered will be raised as errors. If :" +"const:`False` (the default), defects will be passed to the :meth:" +"`register_defect` method." +msgstr "" + +#: ../Doc/library/email.policy.rst:215 +msgid "" +"If :const:`True`, lines starting with *\"From \"* in the body are escaped by " +"putting a ``>`` in front of them. This parameter is used when the message is " +"being serialized by a generator. Default: :const:`False`." +msgstr "" + +#: ../Doc/library/email.policy.rst:220 +msgid "The *mangle_from_* parameter." +msgstr "" + +#: ../Doc/library/email.policy.rst:226 +msgid "" +"A factory function for constructing a new empty message object. Used by the " +"parser when building messages. Defaults to ``None``, in which case :class:" +"`~email.message.Message` is used." +msgstr "" + +#: ../Doc/library/email.policy.rst:232 +msgid "" +"The following :class:`Policy` method is intended to be called by code using " +"the email library to create policy instances with custom settings:" +msgstr "" + +#: ../Doc/library/email.policy.rst:238 +msgid "" +"Return a new :class:`Policy` instance whose attributes have the same values " +"as the current instance, except where those attributes are given new values " +"by the keyword arguments." +msgstr "" + +#: ../Doc/library/email.policy.rst:243 +msgid "" +"The remaining :class:`Policy` methods are called by the email package code, " +"and are not intended to be called by an application using the email package. " +"A custom policy must implement all of these methods." +msgstr "" + +#: ../Doc/library/email.policy.rst:250 +msgid "" +"Handle a *defect* found on *obj*. When the email package calls this method, " +"*defect* will always be a subclass of :class:`~email.errors.Defect`." +msgstr "" + +#: ../Doc/library/email.policy.rst:254 +msgid "" +"The default implementation checks the :attr:`raise_on_defect` flag. If it " +"is ``True``, *defect* is raised as an exception. If it is ``False`` (the " +"default), *obj* and *defect* are passed to :meth:`register_defect`." +msgstr "" + +#: ../Doc/library/email.policy.rst:261 +msgid "" +"Register a *defect* on *obj*. In the email package, *defect* will always be " +"a subclass of :class:`~email.errors.Defect`." +msgstr "" + +#: ../Doc/library/email.policy.rst:264 +msgid "" +"The default implementation calls the ``append`` method of the ``defects`` " +"attribute of *obj*. When the email package calls :attr:`handle_defect`, " +"*obj* will normally have a ``defects`` attribute that has an ``append`` " +"method. Custom object types used with the email package (for example, " +"custom ``Message`` objects) should also provide such an attribute, otherwise " +"defects in parsed messages will raise unexpected errors." +msgstr "" + +#: ../Doc/library/email.policy.rst:274 +msgid "Return the maximum allowed number of headers named *name*." +msgstr "" + +#: ../Doc/library/email.policy.rst:276 +msgid "" +"Called when a header is added to an :class:`~email.message.EmailMessage` or :" +"class:`~email.message.Message` object. If the returned value is not ``0`` " +"or ``None``, and there are already a number of headers with the name *name* " +"greather than or equal to the value returned, a :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/email.policy.rst:282 +msgid "" +"Because the default behavior of ``Message.__setitem__`` is to append the " +"value to the list of headers, it is easy to create duplicate headers without " +"realizing it. This method allows certain headers to be limited in the " +"number of instances of that header that may be added to a ``Message`` " +"programmatically. (The limit is not observed by the parser, which will " +"faithfully produce as many headers as exist in the message being parsed.)" +msgstr "" + +#: ../Doc/library/email.policy.rst:290 +msgid "The default implementation returns ``None`` for all header names." +msgstr "" + +#: ../Doc/library/email.policy.rst:295 +msgid "" +"The email package calls this method with a list of strings, each string " +"ending with the line separation characters found in the source being " +"parsed. The first line includes the field header name and separator. All " +"whitespace in the source is preserved. The method should return the " +"``(name, value)`` tuple that is to be stored in the ``Message`` to represent " +"the parsed header." +msgstr "" + +#: ../Doc/library/email.policy.rst:302 +msgid "" +"If an implementation wishes to retain compatibility with the existing email " +"package policies, *name* should be the case preserved name (all characters " +"up to the '``:``' separator), while *value* should be the unfolded value " +"(all line separator characters removed, but whitespace kept intact), " +"stripped of leading whitespace." +msgstr "" + +#: ../Doc/library/email.policy.rst:308 +msgid "*sourcelines* may contain surrogateescaped binary data." +msgstr "" + +#: ../Doc/library/email.policy.rst:310 ../Doc/library/email.policy.rst:326 +#: ../Doc/library/email.policy.rst:342 +msgid "There is no default implementation" +msgstr "" + +#: ../Doc/library/email.policy.rst:315 +msgid "" +"The email package calls this method with the name and value provided by the " +"application program when the application program is modifying a ``Message`` " +"programmatically (as opposed to a ``Message`` created by a parser). The " +"method should return the ``(name, value)`` tuple that is to be stored in the " +"``Message`` to represent the header." +msgstr "" + +#: ../Doc/library/email.policy.rst:321 +msgid "" +"If an implementation wishes to retain compatibility with the existing email " +"package policies, the *name* and *value* should be strings or string " +"subclasses that do not change the content of the passed in arguments." +msgstr "" + +#: ../Doc/library/email.policy.rst:331 +msgid "" +"The email package calls this method with the *name* and *value* currently " +"stored in the ``Message`` when that header is requested by the application " +"program, and whatever the method returns is what is passed back to the " +"application as the value of the header being retrieved. Note that there may " +"be more than one header with the same name stored in the ``Message``; the " +"method is passed the specific name and value of the header destined to be " +"returned to the application." +msgstr "" + +#: ../Doc/library/email.policy.rst:339 +msgid "" +"*value* may contain surrogateescaped binary data. There should be no " +"surrogateescaped binary data in the value returned by the method." +msgstr "" + +#: ../Doc/library/email.policy.rst:347 +msgid "" +"The email package calls this method with the *name* and *value* currently " +"stored in the ``Message`` for a given header. The method should return a " +"string that represents that header \"folded\" correctly (according to the " +"policy settings) by composing the *name* with the *value* and inserting :" +"attr:`linesep` characters at the appropriate places. See :rfc:`5322` for a " +"discussion of the rules for folding email headers." +msgstr "" + +#: ../Doc/library/email.policy.rst:354 +msgid "" +"*value* may contain surrogateescaped binary data. There should be no " +"surrogateescaped binary data in the string returned by the method." +msgstr "" + +#: ../Doc/library/email.policy.rst:360 +msgid "" +"The same as :meth:`fold`, except that the returned value should be a bytes " +"object rather than a string." +msgstr "" + +#: ../Doc/library/email.policy.rst:363 +msgid "" +"*value* may contain surrogateescaped binary data. These could be converted " +"back into binary data in the returned bytes object." +msgstr "" + +#: ../Doc/library/email.policy.rst:370 +msgid "" +"This concrete :class:`Policy` provides behavior that is intended to be fully " +"compliant with the current email RFCs. These include (but are not limited " +"to) :rfc:`5322`, :rfc:`2047`, and the current MIME RFCs." +msgstr "" + +#: ../Doc/library/email.policy.rst:374 +msgid "" +"This policy adds new header parsing and folding algorithms. Instead of " +"simple strings, headers are ``str`` subclasses with attributes that depend " +"on the type of the field. The parsing and folding algorithm fully " +"implement :rfc:`2047` and :rfc:`5322`." +msgstr "" + +#: ../Doc/library/email.policy.rst:379 +msgid "" +"The default value for the :attr:`~email.policy.Policy.message_factory` " +"attribute is :class:`~email.message.EmailMessage`." +msgstr "" + +#: ../Doc/library/email.policy.rst:382 +msgid "" +"In addition to the settable attributes listed above that apply to all " +"policies, this policy adds the following additional attributes:" +msgstr "" + +#: ../Doc/library/email.policy.rst:390 +msgid "" +"If ``False``, follow :rfc:`5322`, supporting non-ASCII characters in headers " +"by encoding them as \"encoded words\". If ``True``, follow :rfc:`6532` and " +"use ``utf-8`` encoding for headers. Messages formatted in this way may be " +"passed to SMTP servers that support the ``SMTPUTF8`` extension (:rfc:`6531`)." +msgstr "" + +#: ../Doc/library/email.policy.rst:399 +msgid "" +"If the value for a header in the ``Message`` object originated from a :mod:" +"`~email.parser` (as opposed to being set by a program), this attribute " +"indicates whether or not a generator should refold that value when " +"transforming the message back into serialized form. The possible values are:" +msgstr "" + +#: ../Doc/library/email.policy.rst:406 +msgid "``none``" +msgstr "" + +#: ../Doc/library/email.policy.rst:406 +msgid "all source values use original folding" +msgstr "" + +#: ../Doc/library/email.policy.rst:408 +msgid "``long``" +msgstr "" + +#: ../Doc/library/email.policy.rst:408 +msgid "" +"source values that have any line that is longer than ``max_line_length`` " +"will be refolded" +msgstr "" + +#: ../Doc/library/email.policy.rst:411 +msgid "``all``" +msgstr "" + +#: ../Doc/library/email.policy.rst:411 +msgid "all values are refolded." +msgstr "" + +#: ../Doc/library/email.policy.rst:414 +msgid "The default is ``long``." +msgstr "" + +#: ../Doc/library/email.policy.rst:419 +msgid "" +"A callable that takes two arguments, ``name`` and ``value``, where ``name`` " +"is a header field name and ``value`` is an unfolded header field value, and " +"returns a string subclass that represents that header. A default " +"``header_factory`` (see :mod:`~email.headerregistry`) is provided that " +"supports custom parsing for the various address and date :RFC:`5322` header " +"field types, and the major MIME header field stypes. Support for additional " +"custom parsing will be added in the future." +msgstr "" + +#: ../Doc/library/email.policy.rst:430 +msgid "" +"An object with at least two methods: get_content and set_content. When the :" +"meth:`~email.message.EmailMessage.get_content` or :meth:`~email.message." +"EmailMessage.set_content` method of an :class:`~email.message.EmailMessage` " +"object is called, it calls the corresponding method of this object, passing " +"it the message object as its first argument, and any arguments or keywords " +"that were passed to it as additional arguments. By default " +"``content_manager`` is set to :data:`~email.contentmanager.raw_data_manager`." +msgstr "" + +#: ../Doc/library/email.policy.rst:442 ../Doc/library/email.policy.rst:600 +msgid "" +"The class provides the following concrete implementations of the abstract " +"methods of :class:`Policy`:" +msgstr "" + +#: ../Doc/library/email.policy.rst:448 +msgid "" +"Returns the value of the :attr:`~email.headerregistry.BaseHeader.max_count` " +"attribute of the specialized class used to represent the header with the " +"given name." +msgstr "" + +#: ../Doc/library/email.policy.rst:456 ../Doc/library/email.policy.rst:606 +msgid "" +"The name is parsed as everything up to the '``:``' and returned unmodified. " +"The value is determined by stripping leading whitespace off the remainder of " +"the first line, joining all subsequent lines together, and stripping any " +"trailing carriage return or linefeed characters." +msgstr "" + +#: ../Doc/library/email.policy.rst:464 +msgid "" +"The name is returned unchanged. If the input value has a ``name`` attribute " +"and it matches *name* ignoring case, the value is returned unchanged. " +"Otherwise the *name* and *value* are passed to ``header_factory``, and the " +"resulting header object is returned as the value. In this case a " +"``ValueError`` is raised if the input value contains CR or LF characters." +msgstr "" + +#: ../Doc/library/email.policy.rst:474 +msgid "" +"If the value has a ``name`` attribute, it is returned to unmodified. " +"Otherwise the *name*, and the *value* with any CR or LF characters removed, " +"are passed to the ``header_factory``, and the resulting header object is " +"returned. Any surrogateescaped bytes get turned into the unicode unknown-" +"character glyph." +msgstr "" + +#: ../Doc/library/email.policy.rst:483 +msgid "" +"Header folding is controlled by the :attr:`refold_source` policy setting. A " +"value is considered to be a 'source value' if and only if it does not have a " +"``name`` attribute (having a ``name`` attribute means it is a header object " +"of some sort). If a source value needs to be refolded according to the " +"policy, it is converted into a header object by passing the *name* and the " +"*value* with any CR and LF characters removed to the ``header_factory``. " +"Folding of a header object is done by calling its ``fold`` method with the " +"current policy." +msgstr "" + +#: ../Doc/library/email.policy.rst:492 +msgid "" +"Source values are split into lines using :meth:`~str.splitlines`. If the " +"value is not to be refolded, the lines are rejoined using the ``linesep`` " +"from the policy and returned. The exception is lines containing non-ascii " +"binary data. In that case the value is refolded regardless of the " +"``refold_source`` setting, which causes the binary data to be CTE encoded " +"using the ``unknown-8bit`` charset." +msgstr "" + +#: ../Doc/library/email.policy.rst:502 +msgid "" +"The same as :meth:`fold` if :attr:`~Policy.cte_type` is ``7bit``, except " +"that the returned value is bytes." +msgstr "" + +#: ../Doc/library/email.policy.rst:505 +msgid "" +"If :attr:`~Policy.cte_type` is ``8bit``, non-ASCII binary data is converted " +"back into bytes. Headers with binary data are not refolded, regardless of " +"the ``refold_header`` setting, since there is no way to know whether the " +"binary data consists of single byte characters or multibyte characters." +msgstr "" + +#: ../Doc/library/email.policy.rst:512 +msgid "" +"The following instances of :class:`EmailPolicy` provide defaults suitable " +"for specific application domains. Note that in the future the behavior of " +"these instances (in particular the ``HTTP`` instance) may be adjusted to " +"conform even more closely to the RFCs relevant to their domains." +msgstr "" + +#: ../Doc/library/email.policy.rst:520 +msgid "" +"An instance of ``EmailPolicy`` with all defaults unchanged. This policy " +"uses the standard Python ``\\n`` line endings rather than the RFC-correct ``" +"\\r\\n``." +msgstr "" + +#: ../Doc/library/email.policy.rst:527 +msgid "" +"Suitable for serializing messages in conformance with the email RFCs. Like " +"``default``, but with ``linesep`` set to ``\\r\\n``, which is RFC compliant." +msgstr "" + +#: ../Doc/library/email.policy.rst:534 +msgid "" +"The same as ``SMTP`` except that :attr:`~EmailPolicy.utf8` is ``True``. " +"Useful for serializing messages to a message store without using encoded " +"words in the headers. Should only be used for SMTP trasmission if the " +"sender or recipient addresses have non-ASCII characters (the :meth:`smtplib." +"SMTP.send_message` method handles this automatically)." +msgstr "" + +#: ../Doc/library/email.policy.rst:543 +msgid "" +"Suitable for serializing headers with for use in HTTP traffic. Like " +"``SMTP`` except that ``max_line_length`` is set to ``None`` (unlimited)." +msgstr "" + +#: ../Doc/library/email.policy.rst:549 +msgid "" +"Convenience instance. The same as ``default`` except that " +"``raise_on_defect`` is set to ``True``. This allows any policy to be made " +"strict by writing::" +msgstr "" + +#: ../Doc/library/email.policy.rst:556 +msgid "" +"With all of these :class:`EmailPolicies <.EmailPolicy>`, the effective API " +"of the email package is changed from the Python 3.2 API in the following " +"ways:" +msgstr "" + +#: ../Doc/library/email.policy.rst:559 +msgid "" +"Setting a header on a :class:`~email.message.Message` results in that header " +"being parsed and a header object created." +msgstr "" + +#: ../Doc/library/email.policy.rst:562 +msgid "" +"Fetching a header value from a :class:`~email.message.Message` results in " +"that header being parsed and a header object created and returned." +msgstr "" + +#: ../Doc/library/email.policy.rst:566 +msgid "" +"Any header object, or any header that is refolded due to the policy " +"settings, is folded using an algorithm that fully implements the RFC folding " +"algorithms, including knowing where encoded words are required and allowed." +msgstr "" + +#: ../Doc/library/email.policy.rst:571 +msgid "" +"From the application view, this means that any header obtained through the :" +"class:`~email.message.EmailMessage` is a header object with extra " +"attributes, whose string value is the fully decoded unicode value of the " +"header. Likewise, a header may be assigned a new value, or a new header " +"created, using a unicode string, and the policy will take care of converting " +"the unicode string into the correct RFC encoded form." +msgstr "" + +#: ../Doc/library/email.policy.rst:578 +msgid "" +"The header objects and their attributes are described in :mod:`~email." +"headerregistry`." +msgstr "" + +#: ../Doc/library/email.policy.rst:585 +msgid "" +"This concrete :class:`Policy` is the backward compatibility policy. It " +"replicates the behavior of the email package in Python 3.2. The :mod:" +"`~email.policy` module also defines an instance of this class, :const:" +"`compat32`, that is used as the default policy. Thus the default behavior " +"of the email package is to maintain compatibility with Python 3.2." +msgstr "" + +#: ../Doc/library/email.policy.rst:591 +msgid "" +"The following attributes have values that are different from the :class:" +"`Policy` default:" +msgstr "" + +#: ../Doc/library/email.policy.rst:597 +msgid "The default is ``True``." +msgstr "" + +#: ../Doc/library/email.policy.rst:614 +msgid "The name and value are returned unmodified." +msgstr "" + +#: ../Doc/library/email.policy.rst:619 +msgid "" +"If the value contains binary data, it is converted into a :class:`~email." +"header.Header` object using the ``unknown-8bit`` charset. Otherwise it is " +"returned unmodified." +msgstr "" + +#: ../Doc/library/email.policy.rst:626 +msgid "" +"Headers are folded using the :class:`~email.header.Header` folding " +"algorithm, which preserves existing line breaks in the value, and wraps each " +"resulting line to the ``max_line_length``. Non-ASCII binary data are CTE " +"encoded using the ``unknown-8bit`` charset." +msgstr "" + +#: ../Doc/library/email.policy.rst:634 +msgid "" +"Headers are folded using the :class:`~email.header.Header` folding " +"algorithm, which preserves existing line breaks in the value, and wraps each " +"resulting line to the ``max_line_length``. If ``cte_type`` is ``7bit``, non-" +"ascii binary data is CTE encoded using the ``unknown-8bit`` charset. " +"Otherwise the original source header is used, with its existing line breaks " +"and any (RFC invalid) binary data it may contain." +msgstr "" + +#: ../Doc/library/email.policy.rst:644 +msgid "" +"An instance of :class:`Compat32`, providing backward compatibility with the " +"behavior of the email package in Python 3.2." +msgstr "" + +#: ../Doc/library/email.policy.rst:650 +msgid "" +"Oringally added in 3.3 as a :term:`provisional feature `." +msgstr "" + +#: ../Doc/library/email.util.rst:2 +msgid ":mod:`email.utils`: Miscellaneous utilities" +msgstr "" + +#: ../Doc/library/email.util.rst:7 +msgid "**Source code:** :source:`Lib/email/utils.py`" +msgstr "" + +#: ../Doc/library/email.util.rst:11 +msgid "" +"There are a couple of useful utilities provided in the :mod:`email.utils` " +"module:" +msgstr "" + +#: ../Doc/library/email.util.rst:16 +msgid "" +"Return local time as an aware datetime object. If called without arguments, " +"return current time. Otherwise *dt* argument should be a :class:`~datetime." +"datetime` instance, and it is converted to the local time zone according to " +"the system time zone database. If *dt* is naive (that is, ``dt.tzinfo`` is " +"``None``), it is assumed to be in local time. In this case, a positive or " +"zero value for *isdst* causes ``localtime`` to presume initially that summer " +"time (for example, Daylight Saving Time) is or is not (respectively) in " +"effect for the specified time. A negative value for *isdst* causes the " +"``localtime`` to attempt to divine whether summer time is in effect for the " +"specified time." +msgstr "" + +#: ../Doc/library/email.util.rst:32 +msgid "" +"Returns a string suitable for an :rfc:`2822`\\ -compliant :mailheader:" +"`Message-ID` header. Optional *idstring* if given, is a string used to " +"strengthen the uniqueness of the message id. Optional *domain* if given " +"provides the portion of the msgid after the '@'. The default is the local " +"hostname. It is not normally necessary to override this default, but may be " +"useful certain cases, such as a constructing distributed system that uses a " +"consistent domain name across multiple hosts." +msgstr "" + +#: ../Doc/library/email.util.rst:40 +msgid "Added the *domain* keyword." +msgstr "" + +#: ../Doc/library/email.util.rst:44 +msgid "" +"The remaining functions are part of the legacy (``Compat32``) email API. " +"There is no need to directly use these with the new API, since the parsing " +"and formatting they provide is done automatically by the header parsing " +"machinery of the new API." +msgstr "" + +#: ../Doc/library/email.util.rst:52 +msgid "" +"Return a new string with backslashes in *str* replaced by two backslashes, " +"and double quotes replaced by backslash-double quote." +msgstr "" + +#: ../Doc/library/email.util.rst:58 +msgid "" +"Return a new string which is an *unquoted* version of *str*. If *str* ends " +"and begins with double quotes, they are stripped off. Likewise if *str* " +"ends and begins with angle brackets, they are stripped off." +msgstr "" + +#: ../Doc/library/email.util.rst:65 +msgid "" +"Parse address -- which should be the value of some address-containing field " +"such as :mailheader:`To` or :mailheader:`Cc` -- into its constituent " +"*realname* and *email address* parts. Returns a tuple of that information, " +"unless the parse fails, in which case a 2-tuple of ``('', '')`` is returned." +msgstr "" + +#: ../Doc/library/email.util.rst:73 +msgid "" +"The inverse of :meth:`parseaddr`, this takes a 2-tuple of the form " +"``(realname, email_address)`` and returns the string value suitable for a :" +"mailheader:`To` or :mailheader:`Cc` header. If the first element of *pair* " +"is false, then the second element is returned unmodified." +msgstr "" + +#: ../Doc/library/email.util.rst:78 +msgid "" +"Optional *charset* is the character set that will be used in the :rfc:`2047` " +"encoding of the ``realname`` if the ``realname`` contains non-ASCII " +"characters. Can be an instance of :class:`str` or a :class:`~email.charset." +"Charset`. Defaults to ``utf-8``." +msgstr "" + +#: ../Doc/library/email.util.rst:83 +msgid "Added the *charset* option." +msgstr "" + +#: ../Doc/library/email.util.rst:89 +msgid "" +"This method returns a list of 2-tuples of the form returned by " +"``parseaddr()``. *fieldvalues* is a sequence of header field values as might " +"be returned by :meth:`Message.get_all `. " +"Here's a simple example that gets all the recipients of a message::" +msgstr "" + +#: ../Doc/library/email.util.rst:105 +msgid "" +"Attempts to parse a date according to the rules in :rfc:`2822`. however, " +"some mailers don't follow that format as specified, so :func:`parsedate` " +"tries to guess correctly in such cases. *date* is a string containing an :" +"rfc:`2822` date, such as ``\"Mon, 20 Nov 1995 19:12:08 -0500\"``. If it " +"succeeds in parsing the date, :func:`parsedate` returns a 9-tuple that can " +"be passed directly to :func:`time.mktime`; otherwise ``None`` will be " +"returned. Note that indexes 6, 7, and 8 of the result tuple are not usable." +msgstr "" + +#: ../Doc/library/email.util.rst:116 +msgid "" +"Performs the same function as :func:`parsedate`, but returns either ``None`` " +"or a 10-tuple; the first 9 elements make up a tuple that can be passed " +"directly to :func:`time.mktime`, and the tenth is the offset of the date's " +"timezone from UTC (which is the official term for Greenwich Mean Time) " +"[#]_. If the input string has no timezone, the last element of the tuple " +"returned is ``None``. Note that indexes 6, 7, and 8 of the result tuple are " +"not usable." +msgstr "" + +#: ../Doc/library/email.util.rst:126 +msgid "" +"The inverse of :func:`format_datetime`. Performs the same function as :func:" +"`parsedate`, but on success returns a :mod:`~datetime.datetime`. If the " +"input date has a timezone of ``-0000``, the ``datetime`` will be a naive " +"``datetime``, and if the date is conforming to the RFCs it will represent a " +"time in UTC but with no indication of the actual source timezone of the " +"message the date comes from. If the input date has any other valid timezone " +"offset, the ``datetime`` will be an aware ``datetime`` with the " +"corresponding a :class:`~datetime.timezone` :class:`~datetime.tzinfo`." +msgstr "" + +#: ../Doc/library/email.util.rst:140 +msgid "" +"Turn a 10-tuple as returned by :func:`parsedate_tz` into a UTC timestamp " +"(seconds since the Epoch). If the timezone item in the tuple is ``None``, " +"assume local time." +msgstr "" + +#: ../Doc/library/email.util.rst:147 +msgid "Returns a date string as per :rfc:`2822`, e.g.::" +msgstr "" + +#: ../Doc/library/email.util.rst:151 +msgid "" +"Optional *timeval* if given is a floating point time value as accepted by :" +"func:`time.gmtime` and :func:`time.localtime`, otherwise the current time is " +"used." +msgstr "" + +#: ../Doc/library/email.util.rst:155 +msgid "" +"Optional *localtime* is a flag that when ``True``, interprets *timeval*, and " +"returns a date relative to the local timezone instead of UTC, properly " +"taking daylight savings time into account. The default is ``False`` meaning " +"UTC is used." +msgstr "" + +#: ../Doc/library/email.util.rst:160 +msgid "" +"Optional *usegmt* is a flag that when ``True``, outputs a date string with " +"the timezone as an ascii string ``GMT``, rather than a numeric ``-0000``. " +"This is needed for some protocols (such as HTTP). This only applies when " +"*localtime* is ``False``. The default is ``False``." +msgstr "" + +#: ../Doc/library/email.util.rst:168 +msgid "" +"Like ``formatdate``, but the input is a :mod:`datetime` instance. If it is " +"a naive datetime, it is assumed to be \"UTC with no information about the " +"source timezone\", and the conventional ``-0000`` is used for the timezone. " +"If it is an aware ``datetime``, then the numeric timezone offset is used. If " +"it is an aware timezone with offset zero, then *usegmt* may be set to " +"``True``, in which case the string ``GMT`` is used instead of the numeric " +"timezone offset. This provides a way to generate standards conformant HTTP " +"date headers." +msgstr "" + +#: ../Doc/library/email.util.rst:182 +msgid "Decode the string *s* according to :rfc:`2231`." +msgstr "" + +#: ../Doc/library/email.util.rst:187 +msgid "" +"Encode the string *s* according to :rfc:`2231`. Optional *charset* and " +"*language*, if given is the character set name and language name to use. If " +"neither is given, *s* is returned as-is. If *charset* is given but " +"*language* is not, the string is encoded using the empty string for " +"*language*." +msgstr "" + +#: ../Doc/library/email.util.rst:195 +msgid "" +"When a header parameter is encoded in :rfc:`2231` format, :meth:`Message." +"get_param ` may return a 3-tuple containing " +"the character set, language, and value. :func:`collapse_rfc2231_value` " +"turns this into a unicode string. Optional *errors* is passed to the " +"*errors* argument of :class:`str`'s :func:`~str.encode` method; it defaults " +"to ``'replace'``. Optional *fallback_charset* specifies the character set " +"to use if the one in the :rfc:`2231` header is not known by Python; it " +"defaults to ``'us-ascii'``." +msgstr "" + +#: ../Doc/library/email.util.rst:204 +msgid "" +"For convenience, if the *value* passed to :func:`collapse_rfc2231_value` is " +"not a tuple, it should be a string and it is returned unquoted." +msgstr "" + +#: ../Doc/library/email.util.rst:210 +msgid "" +"Decode parameters list according to :rfc:`2231`. *params* is a sequence of " +"2-tuples containing elements of the form ``(content-type, string-value)``." +msgstr "" + +#: ../Doc/library/email.util.rst:216 +msgid "" +"Note that the sign of the timezone offset is the opposite of the sign of the " +"``time.timezone`` variable for the same timezone; the latter variable " +"follows the POSIX standard while this module follows :rfc:`2822`." +msgstr "" + +#: ../Doc/library/ensurepip.rst:2 +msgid ":mod:`ensurepip` --- Bootstrapping the ``pip`` installer" +msgstr "" + +#: ../Doc/library/ensurepip.rst:12 +msgid "" +"The :mod:`ensurepip` package provides support for bootstrapping the ``pip`` " +"installer into an existing Python installation or virtual environment. This " +"bootstrapping approach reflects the fact that ``pip`` is an independent " +"project with its own release cycle, and the latest available stable version " +"is bundled with maintenance and feature releases of the CPython reference " +"interpreter." +msgstr "" + +#: ../Doc/library/ensurepip.rst:19 +msgid "" +"In most cases, end users of Python shouldn't need to invoke this module " +"directly (as ``pip`` should be bootstrapped by default), but it may be " +"needed if installing ``pip`` was skipped when installing Python (or when " +"creating a virtual environment) or after explicitly uninstalling ``pip``." +msgstr "" + +#: ../Doc/library/ensurepip.rst:27 +msgid "" +"This module *does not* access the internet. All of the components needed to " +"bootstrap ``pip`` are included as internal parts of the package." +msgstr "" + +#: ../Doc/library/ensurepip.rst:34 +msgid ":ref:`installing-index`" +msgstr "" + +#: ../Doc/library/ensurepip.rst:34 +msgid "The end user guide for installing Python packages" +msgstr "" + +#: ../Doc/library/ensurepip.rst:36 +msgid ":pep:`453`: Explicit bootstrapping of pip in Python installations" +msgstr "" + +#: ../Doc/library/ensurepip.rst:37 +msgid "The original rationale and specification for this module." +msgstr "" + +#: ../Doc/library/ensurepip.rst:41 +msgid "Command line interface" +msgstr "" + +#: ../Doc/library/ensurepip.rst:43 +msgid "" +"The command line interface is invoked using the interpreter's ``-m`` switch." +msgstr "" + +#: ../Doc/library/ensurepip.rst:45 +msgid "The simplest possible invocation is::" +msgstr "" + +#: ../Doc/library/ensurepip.rst:49 +msgid "" +"This invocation will install ``pip`` if it is not already installed, but " +"otherwise does nothing. To ensure the installed version of ``pip`` is at " +"least as recent as the one bundled with ``ensurepip``, pass the ``--" +"upgrade`` option::" +msgstr "" + +#: ../Doc/library/ensurepip.rst:56 +msgid "" +"By default, ``pip`` is installed into the current virtual environment (if " +"one is active) or into the system site packages (if there is no active " +"virtual environment). The installation location can be controlled through " +"two additional command line options:" +msgstr "" + +#: ../Doc/library/ensurepip.rst:61 +msgid "" +"``--root ``: Installs ``pip`` relative to the given root directory " +"rather than the root of the currently active virtual environment (if any) or " +"the default root for the current Python installation." +msgstr "" + +#: ../Doc/library/ensurepip.rst:64 +msgid "" +"``--user``: Installs ``pip`` into the user site packages directory rather " +"than globally for the current Python installation (this option is not " +"permitted inside an active virtual environment)." +msgstr "" + +#: ../Doc/library/ensurepip.rst:68 +msgid "" +"By default, the scripts ``pipX`` and ``pipX.Y`` will be installed (where X.Y " +"stands for the version of Python used to invoke ``ensurepip``). The scripts " +"installed can be controlled through two additional command line options:" +msgstr "" + +#: ../Doc/library/ensurepip.rst:73 +msgid "" +"``--altinstall``: if an alternate installation is requested, the ``pipX`` " +"script will *not* be installed." +msgstr "" + +#: ../Doc/library/ensurepip.rst:77 +msgid "``--default-pip``: if a \"default pip\" installation is requested, the" +msgstr "" + +#: ../Doc/library/ensurepip.rst:77 +msgid "" +"``pip`` script will be installed in addition to the two regular scripts." +msgstr "" + +#: ../Doc/library/ensurepip.rst:79 +msgid "" +"Providing both of the script selection options will trigger an exception." +msgstr "" + +#: ../Doc/library/ensurepip.rst:83 +msgid "Module API" +msgstr "" + +#: ../Doc/library/ensurepip.rst:85 +msgid ":mod:`ensurepip` exposes two functions for programmatic use:" +msgstr "" + +#: ../Doc/library/ensurepip.rst:89 +msgid "" +"Returns a string specifying the bundled version of pip that will be " +"installed when bootstrapping an environment." +msgstr "" + +#: ../Doc/library/ensurepip.rst:96 +msgid "Bootstraps ``pip`` into the current or designated environment." +msgstr "" + +#: ../Doc/library/ensurepip.rst:98 +msgid "" +"*root* specifies an alternative root directory to install relative to. If " +"*root* is None, then installation uses the default install location for the " +"current environment." +msgstr "" + +#: ../Doc/library/ensurepip.rst:102 +msgid "" +"*upgrade* indicates whether or not to upgrade an existing installation of an " +"earlier version of ``pip`` to the bundled version." +msgstr "" + +#: ../Doc/library/ensurepip.rst:105 +msgid "" +"*user* indicates whether to use the user scheme rather than installing " +"globally." +msgstr "" + +#: ../Doc/library/ensurepip.rst:108 +msgid "" +"By default, the scripts ``pipX`` and ``pipX.Y`` will be installed (where X.Y " +"stands for the current version of Python)." +msgstr "" + +#: ../Doc/library/ensurepip.rst:111 +msgid "If *altinstall* is set, then ``pipX`` will *not* be installed." +msgstr "" + +#: ../Doc/library/ensurepip.rst:113 +msgid "" +"If *default_pip* is set, then ``pip`` will be installed in addition to the " +"two regular scripts." +msgstr "" + +#: ../Doc/library/ensurepip.rst:116 +msgid "" +"Setting both *altinstall* and *default_pip* will trigger :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/ensurepip.rst:119 +msgid "" +"*verbosity* controls the level of output to :data:`sys.stdout` from the " +"bootstrapping operation." +msgstr "" + +#: ../Doc/library/ensurepip.rst:124 +msgid "" +"The bootstrapping process has side effects on both ``sys.path`` and ``os." +"environ``. Invoking the command line interface in a subprocess instead " +"allows these side effects to be avoided." +msgstr "" + +#: ../Doc/library/ensurepip.rst:130 +msgid "" +"The bootstrapping process may install additional modules required by " +"``pip``, but other software should not assume those dependencies will always " +"be present by default (as the dependencies may be removed in a future " +"version of ``pip``)." +msgstr "" + +#: ../Doc/library/enum.rst:2 +msgid ":mod:`enum` --- Support for enumerations" +msgstr "" + +#: ../Doc/library/enum.rst:14 +msgid "**Source code:** :source:`Lib/enum.py`" +msgstr "" + +#: ../Doc/library/enum.rst:18 +msgid "" +"An enumeration is a set of symbolic names (members) bound to unique, " +"constant values. Within an enumeration, the members can be compared by " +"identity, and the enumeration itself can be iterated over." +msgstr "" + +#: ../Doc/library/enum.rst:26 +msgid "" +"This module defines four enumeration classes that can be used to define " +"unique sets of names and values: :class:`Enum`, :class:`IntEnum`, and :class:" +"`IntFlags`. It also defines one decorator, :func:`unique`, and one helper, :" +"class:`auto`." +msgstr "" + +#: ../Doc/library/enum.rst:33 +msgid "" +"Base class for creating enumerated constants. See section `Functional API`_ " +"for an alternate construction syntax." +msgstr "" + +#: ../Doc/library/enum.rst:38 +msgid "" +"Base class for creating enumerated constants that are also subclasses of :" +"class:`int`." +msgstr "" + +#: ../Doc/library/enum.rst:43 +msgid "" +"Base class for creating enumerated constants that can be combined using the " +"bitwise operators without losing their :class:`IntFlag` membership. :class:" +"`IntFlag` members are also subclasses of :class:`int`." +msgstr "" + +#: ../Doc/library/enum.rst:49 +msgid "" +"Base class for creating enumerated constants that can be combined using the " +"bitwise operations without losing their :class:`Flag` membership." +msgstr "" + +#: ../Doc/library/enum.rst:54 +msgid "" +"Enum class decorator that ensures only one name is bound to any one value." +msgstr "" + +#: ../Doc/library/enum.rst:58 +msgid "Instances are replaced with an appropriate value for Enum members." +msgstr "" + +#: ../Doc/library/enum.rst:60 +msgid "``Flag``, ``IntFlag``, ``auto``" +msgstr "" + +#: ../Doc/library/enum.rst:64 +msgid "Creating an Enum" +msgstr "" + +#: ../Doc/library/enum.rst:66 +msgid "" +"Enumerations are created using the :keyword:`class` syntax, which makes them " +"easy to read and write. An alternative creation method is described in " +"`Functional API`_. To define an enumeration, subclass :class:`Enum` as " +"follows::" +msgstr "" + +#: ../Doc/library/enum.rst:78 +msgid "Enum member values" +msgstr "" + +#: ../Doc/library/enum.rst:80 +msgid "" +"Member values can be anything: :class:`int`, :class:`str`, etc.. If the " +"exact value is unimportant you may use :class:`auto` instances and an " +"appropriate value will be chosen for you. Care must be taken if you mix :" +"class:`auto` with other values." +msgstr "" + +#: ../Doc/library/enum.rst:85 +msgid "Nomenclature" +msgstr "" + +#: ../Doc/library/enum.rst:87 +msgid "The class :class:`Color` is an *enumeration* (or *enum*)" +msgstr "" + +#: ../Doc/library/enum.rst:88 +msgid "" +"The attributes :attr:`Color.red`, :attr:`Color.green`, etc., are " +"*enumeration members* (or *enum members*)." +msgstr "" + +#: ../Doc/library/enum.rst:90 +msgid "" +"The enum members have *names* and *values* (the name of :attr:`Color.red` is " +"``red``, the value of :attr:`Color.blue` is ``3``, etc.)" +msgstr "" + +#: ../Doc/library/enum.rst:96 +msgid "" +"Even though we use the :keyword:`class` syntax to create Enums, Enums are " +"not normal Python classes. See `How are Enums different?`_ for more details." +msgstr "" + +#: ../Doc/library/enum.rst:100 +msgid "Enumeration members have human readable string representations::" +msgstr "" + +#: ../Doc/library/enum.rst:105 +msgid "...while their ``repr`` has more information::" +msgstr "" + +#: ../Doc/library/enum.rst:110 +msgid "The *type* of an enumeration member is the enumeration it belongs to::" +msgstr "" + +#: ../Doc/library/enum.rst:118 +msgid "Enum members also have a property that contains just their item name::" +msgstr "" + +#: ../Doc/library/enum.rst:123 +msgid "Enumerations support iteration, in definition order::" +msgstr "" + +#: ../Doc/library/enum.rst:139 +msgid "" +"Enumeration members are hashable, so they can be used in dictionaries and " +"sets::" +msgstr "" + +#: ../Doc/library/enum.rst:149 +msgid "Programmatic access to enumeration members and their attributes" +msgstr "" + +#: ../Doc/library/enum.rst:151 +msgid "" +"Sometimes it's useful to access members in enumerations programmatically (i." +"e. situations where ``Color.red`` won't do because the exact color is not " +"known at program-writing time). ``Enum`` allows such access::" +msgstr "" + +#: ../Doc/library/enum.rst:160 +msgid "If you want to access enum members by *name*, use item access::" +msgstr "" + +#: ../Doc/library/enum.rst:167 +msgid "If you have an enum member and need its :attr:`name` or :attr:`value`::" +msgstr "" + +#: ../Doc/library/enum.rst:177 +msgid "Duplicating enum members and values" +msgstr "" + +#: ../Doc/library/enum.rst:179 +msgid "Having two enum members with the same name is invalid::" +msgstr "" + +#: ../Doc/library/enum.rst:189 +msgid "" +"However, two enum members are allowed to have the same value. Given two " +"members A and B with the same value (and A defined first), B is an alias to " +"A. By-value lookup of the value of A and B will return A. By-name lookup " +"of B will also return A::" +msgstr "" + +#: ../Doc/library/enum.rst:209 +msgid "" +"Attempting to create a member with the same name as an already defined " +"attribute (another member, a method, etc.) or attempting to create an " +"attribute with the same name as a member is not allowed." +msgstr "" + +#: ../Doc/library/enum.rst:215 +msgid "Ensuring unique enumeration values" +msgstr "" + +#: ../Doc/library/enum.rst:217 +msgid "" +"By default, enumerations allow multiple names as aliases for the same value. " +"When this behavior isn't desired, the following decorator can be used to " +"ensure each value is used only once in the enumeration:" +msgstr "" + +#: ../Doc/library/enum.rst:223 +msgid "" +"A :keyword:`class` decorator specifically for enumerations. It searches an " +"enumeration's :attr:`__members__` gathering any aliases it finds; if any are " +"found :exc:`ValueError` is raised with the details::" +msgstr "" + +#: ../Doc/library/enum.rst:241 +msgid "Using automatic values" +msgstr "" + +#: ../Doc/library/enum.rst:243 +msgid "If the exact value is unimportant you can use :class:`auto`::" +msgstr "" + +#: ../Doc/library/enum.rst:254 +msgid "" +"The values are chosen by :func:`_generate_next_value_`, which can be " +"overridden::" +msgstr "" + +#: ../Doc/library/enum.rst:272 +msgid "" +"The goal of the default :meth:`_generate_next_value_` methods is to provide " +"the next :class:`int` in sequence with the last :class:`int` provided, but " +"the way it does this is an implementation detail and may change." +msgstr "" + +#: ../Doc/library/enum.rst:277 ../Doc/library/ipaddress.rst:646 +msgid "Iteration" +msgstr "" + +#: ../Doc/library/enum.rst:279 +msgid "Iterating over the members of an enum does not provide the aliases::" +msgstr "" + +#: ../Doc/library/enum.rst:284 +msgid "" +"The special attribute ``__members__`` is an ordered dictionary mapping names " +"to members. It includes all names defined in the enumeration, including the " +"aliases::" +msgstr "" + +#: ../Doc/library/enum.rst:296 +msgid "" +"The ``__members__`` attribute can be used for detailed programmatic access " +"to the enumeration members. For example, finding all the aliases::" +msgstr "" + +#: ../Doc/library/enum.rst:304 ../Doc/library/stdtypes.rst:125 +msgid "Comparisons" +msgstr "" + +#: ../Doc/library/enum.rst:306 +msgid "Enumeration members are compared by identity::" +msgstr "" + +#: ../Doc/library/enum.rst:315 +msgid "" +"Ordered comparisons between enumeration values are *not* supported. Enum " +"members are not integers (but see `IntEnum`_ below)::" +msgstr "" + +#: ../Doc/library/enum.rst:323 +msgid "Equality comparisons are defined though::" +msgstr "" + +#: ../Doc/library/enum.rst:332 +msgid "" +"Comparisons against non-enumeration values will always compare not equal " +"(again, :class:`IntEnum` was explicitly designed to behave differently, see " +"below)::" +msgstr "" + +#: ../Doc/library/enum.rst:341 +msgid "Allowed members and attributes of enumerations" +msgstr "" + +#: ../Doc/library/enum.rst:343 +msgid "" +"The examples above use integers for enumeration values. Using integers is " +"short and handy (and provided by default by the `Functional API`_), but not " +"strictly enforced. In the vast majority of use-cases, one doesn't care what " +"the actual value of an enumeration is. But if the value *is* important, " +"enumerations can have arbitrary values." +msgstr "" + +#: ../Doc/library/enum.rst:349 +msgid "" +"Enumerations are Python classes, and can have methods and special methods as " +"usual. If we have this enumeration::" +msgstr "" + +#: ../Doc/library/enum.rst:369 +msgid "Then::" +msgstr "" + +#: ../Doc/library/enum.rst:378 +msgid "" +"The rules for what is allowed are as follows: names that start and end with " +"a single underscore are reserved by enum and cannot be used; all other " +"attributes defined within an enumeration will become members of this " +"enumeration, with the exception of special methods (:meth:`__str__`, :meth:" +"`__add__`, etc.) and descriptors (methods are also descriptors)." +msgstr "" + +#: ../Doc/library/enum.rst:384 +msgid "" +"Note: if your enumeration defines :meth:`__new__` and/or :meth:`__init__` " +"then whatever value(s) were given to the enum member will be passed into " +"those methods. See `Planet`_ for an example." +msgstr "" + +#: ../Doc/library/enum.rst:390 +msgid "Restricted subclassing of enumerations" +msgstr "" + +#: ../Doc/library/enum.rst:392 +msgid "" +"Subclassing an enumeration is allowed only if the enumeration does not " +"define any members. So this is forbidden::" +msgstr "" + +#: ../Doc/library/enum.rst:402 +msgid "But this is allowed::" +msgstr "" + +#: ../Doc/library/enum.rst:413 +msgid "" +"Allowing subclassing of enums that define members would lead to a violation " +"of some important invariants of types and instances. On the other hand, it " +"makes sense to allow sharing some common behavior between a group of " +"enumerations. (See `OrderedEnum`_ for an example.)" +msgstr "" + +#: ../Doc/library/enum.rst:420 +msgid "Pickling" +msgstr "" + +#: ../Doc/library/enum.rst:422 +msgid "Enumerations can be pickled and unpickled::" +msgstr "" + +#: ../Doc/library/enum.rst:429 +msgid "" +"The usual restrictions for pickling apply: picklable enums must be defined " +"in the top level of a module, since unpickling requires them to be " +"importable from that module." +msgstr "" + +#: ../Doc/library/enum.rst:435 +msgid "" +"With pickle protocol version 4 it is possible to easily pickle enums nested " +"in other classes." +msgstr "" + +#: ../Doc/library/enum.rst:438 +msgid "" +"It is possible to modify how Enum members are pickled/unpickled by defining :" +"meth:`__reduce_ex__` in the enumeration class." +msgstr "" + +#: ../Doc/library/enum.rst:443 +msgid "Functional API" +msgstr "" + +#: ../Doc/library/enum.rst:445 +msgid "" +"The :class:`Enum` class is callable, providing the following functional API::" +msgstr "" + +#: ../Doc/library/enum.rst:457 +msgid "" +"The semantics of this API resemble :class:`~collections.namedtuple`. The " +"first argument of the call to :class:`Enum` is the name of the enumeration." +msgstr "" + +#: ../Doc/library/enum.rst:460 +msgid "" +"The second argument is the *source* of enumeration member names. It can be " +"a whitespace-separated string of names, a sequence of names, a sequence of 2-" +"tuples with key/value pairs, or a mapping (e.g. dictionary) of names to " +"values. The last two options enable assigning arbitrary values to " +"enumerations; the others auto-assign increasing integers starting with 1 " +"(use the ``start`` parameter to specify a different starting value). A new " +"class derived from :class:`Enum` is returned. In other words, the above " +"assignment to :class:`Animal` is equivalent to::" +msgstr "" + +#: ../Doc/library/enum.rst:476 +msgid "" +"The reason for defaulting to ``1`` as the starting number and not ``0`` is " +"that ``0`` is ``False`` in a boolean sense, but enum members all evaluate to " +"``True``." +msgstr "" + +#: ../Doc/library/enum.rst:480 +msgid "" +"Pickling enums created with the functional API can be tricky as frame stack " +"implementation details are used to try and figure out which module the " +"enumeration is being created in (e.g. it will fail if you use a utility " +"function in separate module, and also may not work on IronPython or Jython). " +"The solution is to specify the module name explicitly as follows::" +msgstr "" + +#: ../Doc/library/enum.rst:490 +msgid "" +"If ``module`` is not supplied, and Enum cannot determine what it is, the new " +"Enum members will not be unpicklable; to keep errors closer to the source, " +"pickling will be disabled." +msgstr "" + +#: ../Doc/library/enum.rst:494 +msgid "" +"The new pickle protocol 4 also, in some circumstances, relies on :attr:" +"`~definition.__qualname__` being set to the location where pickle will be " +"able to find the class. For example, if the class was made available in " +"class SomeData in the global scope::" +msgstr "" + +#: ../Doc/library/enum.rst:501 +msgid "The complete signature is::" +msgstr "" + +#: ../Doc/library/enum.rst:505 +msgid "What the new Enum class will record as its name." +msgstr "" + +#: ../Doc/library/enum.rst:507 +msgid "" +"The Enum members. This can be a whitespace or comma separated string " +"(values will start at 1 unless otherwise specified)::" +msgstr "" + +#: ../Doc/library/enum.rst:512 +msgid "or an iterator of names::" +msgstr "" + +#: ../Doc/library/enum.rst:516 +msgid "or an iterator of (name, value) pairs::" +msgstr "" + +#: ../Doc/library/enum.rst:520 +msgid "or a mapping::" +msgstr "" + +#: ../Doc/library/enum.rst:524 +msgid "name of module where new Enum class can be found." +msgstr "" + +#: ../Doc/library/enum.rst:526 +msgid "where in module new Enum class can be found." +msgstr "" + +#: ../Doc/library/enum.rst:528 +msgid "type to mix in to new Enum class." +msgstr "" + +#: ../Doc/library/enum.rst:530 +msgid "number to start counting at if only names are passed in." +msgstr "" + +#: ../Doc/library/enum.rst:532 +msgid "The *start* parameter was added." +msgstr "" + +#: ../Doc/library/enum.rst:537 +msgid "Derived Enumerations" +msgstr "" + +#: ../Doc/library/enum.rst:540 +msgid "IntEnum" +msgstr "" + +#: ../Doc/library/enum.rst:542 +msgid "" +"The first variation of :class:`Enum` that is provided is also a subclass of :" +"class:`int`. Members of an :class:`IntEnum` can be compared to integers; by " +"extension, integer enumerations of different types can also be compared to " +"each other::" +msgstr "" + +#: ../Doc/library/enum.rst:563 +msgid "" +"However, they still can't be compared to standard :class:`Enum` " +"enumerations::" +msgstr "" + +#: ../Doc/library/enum.rst:576 +msgid "" +":class:`IntEnum` values behave like integers in other ways you'd expect::" +msgstr "" + +#: ../Doc/library/enum.rst:587 +msgid "IntFlag" +msgstr "" + +#: ../Doc/library/enum.rst:589 +msgid "" +"The next variation of :class:`Enum` provided, :class:`IntFlag`, is also " +"based on :class:`int`. The difference being :class:`IntFlag` members can be " +"combined using the bitwise operators (&, \\|, ^, ~) and the result is still " +"an :class:`IntFlag` member. However, as the name implies, :class:`IntFlag` " +"members also subclass :class:`int` and can be used wherever an :class:`int` " +"is used. Any operation on an :class:`IntFlag` member besides the bit-wise " +"operations will lose the :class:`IntFlag` membership." +msgstr "" + +#: ../Doc/library/enum.rst:599 +msgid "Sample :class:`IntFlag` class::" +msgstr "" + +#: ../Doc/library/enum.rst:615 +msgid "It is also possible to name the combinations::" +msgstr "" + +#: ../Doc/library/enum.rst:627 +msgid "" +"Another important difference between :class:`IntFlag` and :class:`Enum` is " +"that if no flags are set (the value is 0), its boolean evaluation is :data:" +"`False`::" +msgstr "" + +#: ../Doc/library/enum.rst:635 +msgid "" +"Because :class:`IntFlag` members are also subclasses of :class:`int` they " +"can be combined with them::" +msgstr "" + +#: ../Doc/library/enum.rst:643 ../Doc/library/mailbox.rst:817 +#: ../Doc/library/mailbox.rst:984 ../Doc/library/mailbox.rst:1354 +#: ../Doc/library/stdtypes.rst:2130 ../Doc/library/stdtypes.rst:3230 +#: ../Doc/library/tkinter.ttk.rst:232 +msgid "Flag" +msgstr "" + +#: ../Doc/library/enum.rst:645 +msgid "" +"The last variation is :class:`Flag`. Like :class:`IntFlag`, :class:`Flag` " +"members can be combined using the bitwise operators (&, \\|, ^, ~). Unlike :" +"class:`IntFlag`, they cannot be combined with, nor compared against, any " +"other :class:`Flag` enumeration, nor :class:`int`. While it is possible to " +"specify the values directly it is recommended to use :class:`auto` as the " +"value and let :class:`Flag` select an appropriate value." +msgstr "" + +#: ../Doc/library/enum.rst:654 +msgid "" +"Like :class:`IntFlag`, if a combination of :class:`Flag` members results in " +"no flags being set, the boolean evaluation is :data:`False`::" +msgstr "" + +#: ../Doc/library/enum.rst:668 +msgid "" +"Individual flags should have values that are powers of two (1, 2, 4, " +"8, ...), while combinations of flags won't::" +msgstr "" + +#: ../Doc/library/enum.rst:680 +msgid "" +"Giving a name to the \"no flags set\" condition does not change its boolean " +"value::" +msgstr "" + +#: ../Doc/library/enum.rst:696 +msgid "" +"For the majority of new code, :class:`Enum` and :class:`Flag` are strongly " +"recommended, since :class:`IntEnum` and :class:`IntFlag` break some semantic " +"promises of an enumeration (by being comparable to integers, and thus by " +"transitivity to other unrelated enumerations). :class:`IntEnum` and :class:" +"`IntFlag` should be used only in cases where :class:`Enum` and :class:`Flag` " +"will not do; for example, when integer constants are replaced with " +"enumerations, or for interoperability with other systems." +msgstr "" + +#: ../Doc/library/enum.rst:706 +msgid "Others" +msgstr "" + +#: ../Doc/library/enum.rst:708 +msgid "" +"While :class:`IntEnum` is part of the :mod:`enum` module, it would be very " +"simple to implement independently::" +msgstr "" + +#: ../Doc/library/enum.rst:714 +msgid "" +"This demonstrates how similar derived enumerations can be defined; for " +"example a :class:`StrEnum` that mixes in :class:`str` instead of :class:" +"`int`." +msgstr "" + +#: ../Doc/library/enum.rst:717 +msgid "Some rules:" +msgstr "" + +#: ../Doc/library/enum.rst:719 +msgid "" +"When subclassing :class:`Enum`, mix-in types must appear before :class:" +"`Enum` itself in the sequence of bases, as in the :class:`IntEnum` example " +"above." +msgstr "" + +#: ../Doc/library/enum.rst:722 +msgid "" +"While :class:`Enum` can have members of any type, once you mix in an " +"additional type, all the members must have values of that type, e.g. :class:" +"`int` above. This restriction does not apply to mix-ins which only add " +"methods and don't specify another data type such as :class:`int` or :class:" +"`str`." +msgstr "" + +#: ../Doc/library/enum.rst:727 +msgid "" +"When another data type is mixed in, the :attr:`value` attribute is *not the " +"same* as the enum member itself, although it is equivalent and will compare " +"equal." +msgstr "" + +#: ../Doc/library/enum.rst:730 +msgid "" +"%-style formatting: `%s` and `%r` call the :class:`Enum` class's :meth:" +"`__str__` and :meth:`__repr__` respectively; other codes (such as `%i` or `" +"%h` for IntEnum) treat the enum member as its mixed-in type." +msgstr "" + +#: ../Doc/library/enum.rst:733 +msgid "" +":ref:`Formatted string literals `, :meth:`str.format`, and :func:" +"`format` will use the mixed-in type's :meth:`__format__`. If the :class:" +"`Enum` class's :func:`str` or :func:`repr` is desired, use the `!s` or `!r` " +"format codes." +msgstr "" + +#: ../Doc/library/enum.rst:740 +msgid "Interesting examples" +msgstr "" + +#: ../Doc/library/enum.rst:742 +msgid "" +"While :class:`Enum`, :class:`IntEnum`, :class:`IntFlag`, and :class:`Flag` " +"are expected to cover the majority of use-cases, they cannot cover them " +"all. Here are recipes for some different types of enumerations that can be " +"used directly, or as examples for creating one's own." +msgstr "" + +#: ../Doc/library/enum.rst:749 +msgid "Omitting values" +msgstr "" + +#: ../Doc/library/enum.rst:751 +msgid "" +"In many use-cases one doesn't care what the actual value of an enumeration " +"is. There are several ways to define this type of simple enumeration:" +msgstr "" + +#: ../Doc/library/enum.rst:754 +msgid "use instances of :class:`auto` for the value" +msgstr "" + +#: ../Doc/library/enum.rst:755 +msgid "use instances of :class:`object` as the value" +msgstr "" + +#: ../Doc/library/enum.rst:756 +msgid "use a descriptive string as the value" +msgstr "" + +#: ../Doc/library/enum.rst:757 +msgid "" +"use a tuple as the value and a custom :meth:`__new__` to replace the tuple " +"with an :class:`int` value" +msgstr "" + +#: ../Doc/library/enum.rst:760 +msgid "" +"Using any of these methods signifies to the user that these values are not " +"important, and also enables one to add, remove, or reorder members without " +"having to renumber the remaining members." +msgstr "" + +#: ../Doc/library/enum.rst:764 +msgid "" +"Whichever method you choose, you should provide a :meth:`repr` that also " +"hides the (unimportant) value::" +msgstr "" + +#: ../Doc/library/enum.rst:774 +msgid "Using :class:`auto`" +msgstr "" + +#: ../Doc/library/enum.rst:776 ../Doc/library/enum.rst:790 +msgid "Using :class:`object` would look like::" +msgstr "" + +#: ../Doc/library/enum.rst:788 +msgid "Using :class:`object`" +msgstr "" + +#: ../Doc/library/enum.rst:802 +msgid "Using a descriptive string" +msgstr "" + +#: ../Doc/library/enum.rst:804 +msgid "Using a string as the value would look like::" +msgstr "" + +#: ../Doc/library/enum.rst:818 +msgid "Using a custom :meth:`__new__`" +msgstr "" + +#: ../Doc/library/enum.rst:820 +msgid "Using an auto-numbering :meth:`__new__` would look like::" +msgstr "" + +#: ../Doc/library/enum.rst:842 +msgid "" +"The :meth:`__new__` method, if defined, is used during creation of the Enum " +"members; it is then replaced by Enum's :meth:`__new__` which is used after " +"class creation for lookup of existing members." +msgstr "" + +#: ../Doc/library/enum.rst:848 +msgid "OrderedEnum" +msgstr "" + +#: ../Doc/library/enum.rst:850 +msgid "" +"An ordered enumeration that is not based on :class:`IntEnum` and so " +"maintains the normal :class:`Enum` invariants (such as not being comparable " +"to other enumerations)::" +msgstr "" + +#: ../Doc/library/enum.rst:884 +msgid "DuplicateFreeEnum" +msgstr "" + +#: ../Doc/library/enum.rst:886 +msgid "" +"Raises an error if a duplicate member name is found instead of creating an " +"alias::" +msgstr "" + +#: ../Doc/library/enum.rst:911 +msgid "" +"This is a useful example for subclassing Enum to add or change other " +"behaviors as well as disallowing aliases. If the only desired change is " +"disallowing aliases, the :func:`unique` decorator can be used instead." +msgstr "" + +#: ../Doc/library/enum.rst:917 +msgid "Planet" +msgstr "" + +#: ../Doc/library/enum.rst:919 +msgid "" +"If :meth:`__new__` or :meth:`__init__` is defined the value of the enum " +"member will be passed to those methods::" +msgstr "" + +#: ../Doc/library/enum.rst:947 +msgid "How are Enums different?" +msgstr "" + +#: ../Doc/library/enum.rst:949 +msgid "" +"Enums have a custom metaclass that affects many aspects of both derived Enum " +"classes and their instances (members)." +msgstr "" + +#: ../Doc/library/enum.rst:954 +msgid "Enum Classes" +msgstr "" + +#: ../Doc/library/enum.rst:956 +msgid "" +"The :class:`EnumMeta` metaclass is responsible for providing the :meth:" +"`__contains__`, :meth:`__dir__`, :meth:`__iter__` and other methods that " +"allow one to do things with an :class:`Enum` class that fail on a typical " +"class, such as `list(Color)` or `some_var in Color`. :class:`EnumMeta` is " +"responsible for ensuring that various other methods on the final :class:" +"`Enum` class are correct (such as :meth:`__new__`, :meth:`__getnewargs__`, :" +"meth:`__str__` and :meth:`__repr__`)." +msgstr "" + +#: ../Doc/library/enum.rst:966 +msgid "Enum Members (aka instances)" +msgstr "" + +#: ../Doc/library/enum.rst:968 +msgid "" +"The most interesting thing about Enum members is that they are singletons. :" +"class:`EnumMeta` creates them all while it is creating the :class:`Enum` " +"class itself, and then puts a custom :meth:`__new__` in place to ensure that " +"no new ones are ever instantiated by returning only the existing member " +"instances." +msgstr "" + +#: ../Doc/library/enum.rst:976 +msgid "Finer Points" +msgstr "" + +#: ../Doc/library/enum.rst:979 +msgid "Supported ``__dunder__`` names" +msgstr "" + +#: ../Doc/library/enum.rst:981 +msgid "" +":attr:`__members__` is an :class:`OrderedDict` of ``member_name``:``member`` " +"items. It is only available on the class." +msgstr "" + +#: ../Doc/library/enum.rst:984 +msgid "" +":meth:`__new__`, if specified, must create and return the enum members; it " +"is also a very good idea to set the member's :attr:`_value_` appropriately. " +"Once all the members are created it is no longer used." +msgstr "" + +#: ../Doc/library/enum.rst:990 +msgid "Supported ``_sunder_`` names" +msgstr "" + +#: ../Doc/library/enum.rst:992 +msgid "``_name_`` -- name of the member" +msgstr "" + +#: ../Doc/library/enum.rst:993 +msgid "" +"``_value_`` -- value of the member; can be set / modified in ``__new__``" +msgstr "" + +#: ../Doc/library/enum.rst:995 +msgid "" +"``_missing_`` -- a lookup function used when a value is not found; may be " +"overridden" +msgstr "" + +#: ../Doc/library/enum.rst:997 +msgid "" +"``_order_`` -- used in Python 2/3 code to ensure member order is consistent " +"(class attribute, removed during class creation)" +msgstr "" + +#: ../Doc/library/enum.rst:999 +msgid "" +"``_generate_next_value_`` -- used by the `Functional API`_ and by :class:" +"`auto` to get an appropriate value for an enum member; may be overridden" +msgstr "" + +#: ../Doc/library/enum.rst:1003 +msgid "``_missing_``, ``_order_``, ``_generate_next_value_``" +msgstr "" + +#: ../Doc/library/enum.rst:1005 +msgid "" +"To help keep Python 2 / Python 3 code in sync an :attr:`_order_` attribute " +"can be provided. It will be checked against the actual order of the " +"enumeration and raise an error if the two do not match::" +msgstr "" + +#: ../Doc/library/enum.rst:1021 +msgid "" +"In Python 2 code the :attr:`_order_` attribute is necessary as definition " +"order is lost before it can be recorded." +msgstr "" + +#: ../Doc/library/enum.rst:1025 +msgid "``Enum`` member type" +msgstr "" + +#: ../Doc/library/enum.rst:1027 +msgid "" +":class:`Enum` members are instances of their :class:`Enum` class, and are " +"normally accessed as ``EnumClass.member``. Under certain circumstances they " +"can also be accessed as ``EnumClass.member.member``, but you should never do " +"this as that lookup may fail or, worse, return something besides the :class:" +"`Enum` member you are looking for::" +msgstr "" + +#: ../Doc/library/enum.rst:1047 +msgid "Boolean value of ``Enum`` classes and members" +msgstr "" + +#: ../Doc/library/enum.rst:1049 +msgid "" +":class:`Enum` members that are mixed with non-:class:`Enum` types (such as :" +"class:`int`, :class:`str`, etc.) are evaluated according to the mixed-in " +"type's rules; otherwise, all members evaluate as :data:`True`. To make your " +"own Enum's boolean evaluation depend on the member's value add the following " +"to your class::" +msgstr "" + +#: ../Doc/library/enum.rst:1058 +msgid ":class:`Enum` classes always evaluate as :data:`True`." +msgstr "" + +#: ../Doc/library/enum.rst:1062 +msgid "``Enum`` classes with methods" +msgstr "" + +#: ../Doc/library/enum.rst:1064 +msgid "" +"If you give your :class:`Enum` subclass extra methods, like the `Planet`_ " +"class above, those methods will show up in a :func:`dir` of the member, but " +"not of the class::" +msgstr "" + +#: ../Doc/library/enum.rst:1075 +msgid "Combining members of ``Flag``" +msgstr "" + +#: ../Doc/library/enum.rst:1077 +msgid "" +"If a combination of Flag members is not named, the :func:`repr` will include " +"all named flags and all named combinations of flags that are in the value::" +msgstr "" + +#: ../Doc/library/errno.rst:2 +msgid ":mod:`errno` --- Standard errno system symbols" +msgstr "" + +#: ../Doc/library/errno.rst:9 +msgid "" +"This module makes available standard ``errno`` system symbols. The value of " +"each symbol is the corresponding integer value. The names and descriptions " +"are borrowed from :file:`linux/include/errno.h`, which should be pretty all-" +"inclusive." +msgstr "" + +#: ../Doc/library/errno.rst:17 +msgid "" +"Dictionary providing a mapping from the errno value to the string name in " +"the underlying system. For instance, ``errno.errorcode[errno.EPERM]`` maps " +"to ``'EPERM'``." +msgstr "" + +#: ../Doc/library/errno.rst:21 +msgid "" +"To translate a numeric error code to an error message, use :func:`os." +"strerror`." +msgstr "" + +#: ../Doc/library/errno.rst:23 +msgid "" +"Of the following list, symbols that are not used on the current platform are " +"not defined by the module. The specific list of defined symbols is " +"available as ``errno.errorcode.keys()``. Symbols available can include:" +msgstr "" + +#: ../Doc/library/errno.rst:30 +msgid "Operation not permitted" +msgstr "" + +#: ../Doc/library/errno.rst:35 +msgid "No such file or directory" +msgstr "" + +#: ../Doc/library/errno.rst:40 +msgid "No such process" +msgstr "" + +#: ../Doc/library/errno.rst:45 +msgid "Interrupted system call." +msgstr "" + +#: ../Doc/library/errno.rst:48 +msgid "This error is mapped to the exception :exc:`InterruptedError`." +msgstr "" + +#: ../Doc/library/errno.rst:53 +msgid "I/O error" +msgstr "" + +#: ../Doc/library/errno.rst:58 +msgid "No such device or address" +msgstr "" + +#: ../Doc/library/errno.rst:63 +msgid "Arg list too long" +msgstr "" + +#: ../Doc/library/errno.rst:68 +msgid "Exec format error" +msgstr "" + +#: ../Doc/library/errno.rst:73 +msgid "Bad file number" +msgstr "" + +#: ../Doc/library/errno.rst:78 +msgid "No child processes" +msgstr "" + +#: ../Doc/library/errno.rst:83 +msgid "Try again" +msgstr "" + +#: ../Doc/library/errno.rst:88 +msgid "Out of memory" +msgstr "" + +#: ../Doc/library/errno.rst:93 +msgid "Permission denied" +msgstr "" + +#: ../Doc/library/errno.rst:98 +msgid "Bad address" +msgstr "" + +#: ../Doc/library/errno.rst:103 +msgid "Block device required" +msgstr "" + +#: ../Doc/library/errno.rst:108 +msgid "Device or resource busy" +msgstr "" + +#: ../Doc/library/errno.rst:113 +msgid "File exists" +msgstr "" + +#: ../Doc/library/errno.rst:118 +msgid "Cross-device link" +msgstr "" + +#: ../Doc/library/errno.rst:123 +msgid "No such device" +msgstr "" + +#: ../Doc/library/errno.rst:128 +msgid "Not a directory" +msgstr "" + +#: ../Doc/library/errno.rst:133 +msgid "Is a directory" +msgstr "" + +#: ../Doc/library/errno.rst:138 +msgid "Invalid argument" +msgstr "" + +#: ../Doc/library/errno.rst:143 +msgid "File table overflow" +msgstr "" + +#: ../Doc/library/errno.rst:148 +msgid "Too many open files" +msgstr "" + +#: ../Doc/library/errno.rst:153 +msgid "Not a typewriter" +msgstr "" + +#: ../Doc/library/errno.rst:158 +msgid "Text file busy" +msgstr "" + +#: ../Doc/library/errno.rst:163 +msgid "File too large" +msgstr "" + +#: ../Doc/library/errno.rst:168 +msgid "No space left on device" +msgstr "" + +#: ../Doc/library/errno.rst:173 +msgid "Illegal seek" +msgstr "" + +#: ../Doc/library/errno.rst:178 +msgid "Read-only file system" +msgstr "" + +#: ../Doc/library/errno.rst:183 +msgid "Too many links" +msgstr "" + +#: ../Doc/library/errno.rst:188 +msgid "Broken pipe" +msgstr "" + +#: ../Doc/library/errno.rst:193 +msgid "Math argument out of domain of func" +msgstr "" + +#: ../Doc/library/errno.rst:198 +msgid "Math result not representable" +msgstr "" + +#: ../Doc/library/errno.rst:203 +msgid "Resource deadlock would occur" +msgstr "" + +#: ../Doc/library/errno.rst:208 +msgid "File name too long" +msgstr "" + +#: ../Doc/library/errno.rst:213 +msgid "No record locks available" +msgstr "" + +#: ../Doc/library/errno.rst:218 +msgid "Function not implemented" +msgstr "" + +#: ../Doc/library/errno.rst:223 +msgid "Directory not empty" +msgstr "" + +#: ../Doc/library/errno.rst:228 +msgid "Too many symbolic links encountered" +msgstr "" + +#: ../Doc/library/errno.rst:233 +msgid "Operation would block" +msgstr "" + +#: ../Doc/library/errno.rst:238 +msgid "No message of desired type" +msgstr "" + +#: ../Doc/library/errno.rst:243 +msgid "Identifier removed" +msgstr "" + +#: ../Doc/library/errno.rst:248 +msgid "Channel number out of range" +msgstr "" + +#: ../Doc/library/errno.rst:253 +msgid "Level 2 not synchronized" +msgstr "" + +#: ../Doc/library/errno.rst:258 +msgid "Level 3 halted" +msgstr "" + +#: ../Doc/library/errno.rst:263 +msgid "Level 3 reset" +msgstr "" + +#: ../Doc/library/errno.rst:268 +msgid "Link number out of range" +msgstr "" + +#: ../Doc/library/errno.rst:273 +msgid "Protocol driver not attached" +msgstr "" + +#: ../Doc/library/errno.rst:278 +msgid "No CSI structure available" +msgstr "" + +#: ../Doc/library/errno.rst:283 +msgid "Level 2 halted" +msgstr "" + +#: ../Doc/library/errno.rst:288 +msgid "Invalid exchange" +msgstr "" + +#: ../Doc/library/errno.rst:293 +msgid "Invalid request descriptor" +msgstr "" + +#: ../Doc/library/errno.rst:298 +msgid "Exchange full" +msgstr "" + +#: ../Doc/library/errno.rst:303 +msgid "No anode" +msgstr "" + +#: ../Doc/library/errno.rst:308 +msgid "Invalid request code" +msgstr "" + +#: ../Doc/library/errno.rst:313 +msgid "Invalid slot" +msgstr "" + +#: ../Doc/library/errno.rst:318 +msgid "File locking deadlock error" +msgstr "" + +#: ../Doc/library/errno.rst:323 +msgid "Bad font file format" +msgstr "" + +#: ../Doc/library/errno.rst:328 +msgid "Device not a stream" +msgstr "" + +#: ../Doc/library/errno.rst:333 +msgid "No data available" +msgstr "" + +#: ../Doc/library/errno.rst:338 +msgid "Timer expired" +msgstr "" + +#: ../Doc/library/errno.rst:343 +msgid "Out of streams resources" +msgstr "" + +#: ../Doc/library/errno.rst:348 +msgid "Machine is not on the network" +msgstr "" + +#: ../Doc/library/errno.rst:353 +msgid "Package not installed" +msgstr "" + +#: ../Doc/library/errno.rst:358 +msgid "Object is remote" +msgstr "" + +#: ../Doc/library/errno.rst:363 +msgid "Link has been severed" +msgstr "" + +#: ../Doc/library/errno.rst:368 +msgid "Advertise error" +msgstr "" + +#: ../Doc/library/errno.rst:373 +msgid "Srmount error" +msgstr "" + +#: ../Doc/library/errno.rst:378 +msgid "Communication error on send" +msgstr "" + +#: ../Doc/library/errno.rst:383 +msgid "Protocol error" +msgstr "" + +#: ../Doc/library/errno.rst:388 +msgid "Multihop attempted" +msgstr "" + +#: ../Doc/library/errno.rst:393 +msgid "RFS specific error" +msgstr "" + +#: ../Doc/library/errno.rst:398 +msgid "Not a data message" +msgstr "" + +#: ../Doc/library/errno.rst:403 +msgid "Value too large for defined data type" +msgstr "" + +#: ../Doc/library/errno.rst:408 +msgid "Name not unique on network" +msgstr "" + +#: ../Doc/library/errno.rst:413 +msgid "File descriptor in bad state" +msgstr "" + +#: ../Doc/library/errno.rst:418 +msgid "Remote address changed" +msgstr "" + +#: ../Doc/library/errno.rst:423 +msgid "Can not access a needed shared library" +msgstr "" + +#: ../Doc/library/errno.rst:428 +msgid "Accessing a corrupted shared library" +msgstr "" + +#: ../Doc/library/errno.rst:433 +msgid ".lib section in a.out corrupted" +msgstr "" + +#: ../Doc/library/errno.rst:438 +msgid "Attempting to link in too many shared libraries" +msgstr "" + +#: ../Doc/library/errno.rst:443 +msgid "Cannot exec a shared library directly" +msgstr "" + +#: ../Doc/library/errno.rst:448 +msgid "Illegal byte sequence" +msgstr "" + +#: ../Doc/library/errno.rst:453 +msgid "Interrupted system call should be restarted" +msgstr "" + +#: ../Doc/library/errno.rst:458 +msgid "Streams pipe error" +msgstr "" + +#: ../Doc/library/errno.rst:463 +msgid "Too many users" +msgstr "" + +#: ../Doc/library/errno.rst:468 +msgid "Socket operation on non-socket" +msgstr "" + +#: ../Doc/library/errno.rst:473 +msgid "Destination address required" +msgstr "" + +#: ../Doc/library/errno.rst:478 +msgid "Message too long" +msgstr "" + +#: ../Doc/library/errno.rst:483 +msgid "Protocol wrong type for socket" +msgstr "" + +#: ../Doc/library/errno.rst:488 +msgid "Protocol not available" +msgstr "" + +#: ../Doc/library/errno.rst:493 +msgid "Protocol not supported" +msgstr "" + +#: ../Doc/library/errno.rst:498 +msgid "Socket type not supported" +msgstr "" + +#: ../Doc/library/errno.rst:503 +msgid "Operation not supported on transport endpoint" +msgstr "" + +#: ../Doc/library/errno.rst:508 +msgid "Protocol family not supported" +msgstr "" + +#: ../Doc/library/errno.rst:513 +msgid "Address family not supported by protocol" +msgstr "" + +#: ../Doc/library/errno.rst:518 +msgid "Address already in use" +msgstr "" + +#: ../Doc/library/errno.rst:523 +msgid "Cannot assign requested address" +msgstr "" + +#: ../Doc/library/errno.rst:528 +msgid "Network is down" +msgstr "" + +#: ../Doc/library/errno.rst:533 +msgid "Network is unreachable" +msgstr "" + +#: ../Doc/library/errno.rst:538 +msgid "Network dropped connection because of reset" +msgstr "" + +#: ../Doc/library/errno.rst:543 +msgid "Software caused connection abort" +msgstr "" + +#: ../Doc/library/errno.rst:548 +msgid "Connection reset by peer" +msgstr "" + +#: ../Doc/library/errno.rst:553 +msgid "No buffer space available" +msgstr "" + +#: ../Doc/library/errno.rst:558 +msgid "Transport endpoint is already connected" +msgstr "" + +#: ../Doc/library/errno.rst:563 +msgid "Transport endpoint is not connected" +msgstr "" + +#: ../Doc/library/errno.rst:568 +msgid "Cannot send after transport endpoint shutdown" +msgstr "" + +#: ../Doc/library/errno.rst:573 +msgid "Too many references: cannot splice" +msgstr "" + +#: ../Doc/library/errno.rst:578 +msgid "Connection timed out" +msgstr "" + +#: ../Doc/library/errno.rst:583 +msgid "Connection refused" +msgstr "" + +#: ../Doc/library/errno.rst:588 +msgid "Host is down" +msgstr "" + +#: ../Doc/library/errno.rst:593 +msgid "No route to host" +msgstr "" + +#: ../Doc/library/errno.rst:598 +msgid "Operation already in progress" +msgstr "" + +#: ../Doc/library/errno.rst:603 +msgid "Operation now in progress" +msgstr "" + +#: ../Doc/library/errno.rst:608 +msgid "Stale NFS file handle" +msgstr "" + +#: ../Doc/library/errno.rst:613 +msgid "Structure needs cleaning" +msgstr "" + +#: ../Doc/library/errno.rst:618 +msgid "Not a XENIX named type file" +msgstr "" + +#: ../Doc/library/errno.rst:623 +msgid "No XENIX semaphores available" +msgstr "" + +#: ../Doc/library/errno.rst:628 +msgid "Is a named type file" +msgstr "" + +#: ../Doc/library/errno.rst:633 +msgid "Remote I/O error" +msgstr "" + +#: ../Doc/library/errno.rst:638 +msgid "Quota exceeded" +msgstr "" + +#: ../Doc/library/exceptions.rst:4 +msgid "Built-in Exceptions" +msgstr "" + +#: ../Doc/library/exceptions.rst:10 +msgid "" +"In Python, all exceptions must be instances of a class that derives from :" +"class:`BaseException`. In a :keyword:`try` statement with an :keyword:" +"`except` clause that mentions a particular class, that clause also handles " +"any exception classes derived from that class (but not exception classes " +"from which *it* is derived). Two exception classes that are not related via " +"subclassing are never equivalent, even if they have the same name." +msgstr "" + +#: ../Doc/library/exceptions.rst:19 +msgid "" +"The built-in exceptions listed below can be generated by the interpreter or " +"built-in functions. Except where mentioned, they have an \"associated value" +"\" indicating the detailed cause of the error. This may be a string or a " +"tuple of several items of information (e.g., an error code and a string " +"explaining the code). The associated value is usually passed as arguments " +"to the exception class's constructor." +msgstr "" + +#: ../Doc/library/exceptions.rst:26 +msgid "" +"User code can raise built-in exceptions. This can be used to test an " +"exception handler or to report an error condition \"just like\" the " +"situation in which the interpreter raises the same exception; but beware " +"that there is nothing to prevent user code from raising an inappropriate " +"error." +msgstr "" + +#: ../Doc/library/exceptions.rst:31 +msgid "" +"The built-in exception classes can be subclassed to define new exceptions; " +"programmers are encouraged to derive new exceptions from the :exc:" +"`Exception` class or one of its subclasses, and not from :exc:" +"`BaseException`. More information on defining exceptions is available in " +"the Python Tutorial under :ref:`tut-userexceptions`." +msgstr "" + +#: ../Doc/library/exceptions.rst:37 +msgid "" +"When raising (or re-raising) an exception in an :keyword:`except` or :" +"keyword:`finally` clause :attr:`__context__` is automatically set to the " +"last exception caught; if the new exception is not handled the traceback " +"that is eventually displayed will include the originating exception(s) and " +"the final exception." +msgstr "" + +#: ../Doc/library/exceptions.rst:43 +msgid "" +"When raising a new exception (rather than using a bare ``raise`` to re-raise " +"the exception currently being handled), the implicit exception context can " +"be supplemented with an explicit cause by using :keyword:`from` with :" +"keyword:`raise`::" +msgstr "" + +#: ../Doc/library/exceptions.rst:50 +msgid "" +"The expression following :keyword:`from` must be an exception or ``None``. " +"It will be set as :attr:`__cause__` on the raised exception. Setting :attr:" +"`__cause__` also implicitly sets the :attr:`__suppress_context__` attribute " +"to ``True``, so that using ``raise new_exc from None`` effectively replaces " +"the old exception with the new one for display purposes (e.g. converting :" +"exc:`KeyError` to :exc:`AttributeError`, while leaving the old exception " +"available in :attr:`__context__` for introspection when debugging." +msgstr "" + +#: ../Doc/library/exceptions.rst:59 +msgid "" +"The default traceback display code shows these chained exceptions in " +"addition to the traceback for the exception itself. An explicitly chained " +"exception in :attr:`__cause__` is always shown when present. An implicitly " +"chained exception in :attr:`__context__` is shown only if :attr:`__cause__` " +"is :const:`None` and :attr:`__suppress_context__` is false." +msgstr "" + +#: ../Doc/library/exceptions.rst:65 +msgid "" +"In either case, the exception itself is always shown after any chained " +"exceptions so that the final line of the traceback always shows the last " +"exception that was raised." +msgstr "" + +#: ../Doc/library/exceptions.rst:71 +msgid "Base classes" +msgstr "" + +#: ../Doc/library/exceptions.rst:73 +msgid "" +"The following exceptions are used mostly as base classes for other " +"exceptions." +msgstr "" + +#: ../Doc/library/exceptions.rst:77 +msgid "" +"The base class for all built-in exceptions. It is not meant to be directly " +"inherited by user-defined classes (for that, use :exc:`Exception`). If :" +"func:`str` is called on an instance of this class, the representation of the " +"argument(s) to the instance are returned, or the empty string when there " +"were no arguments." +msgstr "" + +#: ../Doc/library/exceptions.rst:85 +msgid "" +"The tuple of arguments given to the exception constructor. Some built-in " +"exceptions (like :exc:`OSError`) expect a certain number of arguments and " +"assign a special meaning to the elements of this tuple, while others are " +"usually called only with a single string giving an error message." +msgstr "" + +#: ../Doc/library/exceptions.rst:92 +msgid "" +"This method sets *tb* as the new traceback for the exception and returns the " +"exception object. It is usually used in exception handling code like this::" +msgstr "" + +#: ../Doc/library/exceptions.rst:105 +msgid "" +"All built-in, non-system-exiting exceptions are derived from this class. " +"All user-defined exceptions should also be derived from this class." +msgstr "" + +#: ../Doc/library/exceptions.rst:111 +msgid "" +"The base class for those built-in exceptions that are raised for various " +"arithmetic errors: :exc:`OverflowError`, :exc:`ZeroDivisionError`, :exc:" +"`FloatingPointError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:118 +msgid "" +"Raised when a :ref:`buffer ` related operation cannot be " +"performed." +msgstr "" + +#: ../Doc/library/exceptions.rst:124 +msgid "" +"The base class for the exceptions that are raised when a key or index used " +"on a mapping or sequence is invalid: :exc:`IndexError`, :exc:`KeyError`. " +"This can be raised directly by :func:`codecs.lookup`." +msgstr "" + +#: ../Doc/library/exceptions.rst:130 +msgid "Concrete exceptions" +msgstr "" + +#: ../Doc/library/exceptions.rst:132 +msgid "The following exceptions are the exceptions that are usually raised." +msgstr "" + +#: ../Doc/library/exceptions.rst:138 +msgid "Raised when an :keyword:`assert` statement fails." +msgstr "" + +#: ../Doc/library/exceptions.rst:143 +msgid "" +"Raised when an attribute reference (see :ref:`attribute-references`) or " +"assignment fails. (When an object does not support attribute references or " +"attribute assignments at all, :exc:`TypeError` is raised.)" +msgstr "" + +#: ../Doc/library/exceptions.rst:150 +msgid "" +"Raised when the :func:`input` function hits an end-of-file condition (EOF) " +"without reading any data. (N.B.: the :meth:`io.IOBase.read` and :meth:`io." +"IOBase.readline` methods return an empty string when they hit EOF.)" +msgstr "" + +#: ../Doc/library/exceptions.rst:157 +msgid "" +"Raised when a floating point operation fails. This exception is always " +"defined, but can only be raised when Python is configured with the ``--with-" +"fpectl`` option, or the :const:`WANT_SIGFPE_HANDLER` symbol is defined in " +"the :file:`pyconfig.h` file." +msgstr "" + +#: ../Doc/library/exceptions.rst:165 +msgid "" +"Raised when a :term:`generator` or :term:`coroutine` is closed; see :meth:" +"`generator.close` and :meth:`coroutine.close`. It directly inherits from :" +"exc:`BaseException` instead of :exc:`Exception` since it is technically not " +"an error." +msgstr "" + +#: ../Doc/library/exceptions.rst:173 +msgid "" +"Raised when the :keyword:`import` statement has troubles trying to load a " +"module. Also raised when the \"from list\" in ``from ... import`` has a " +"name that cannot be found." +msgstr "" + +#: ../Doc/library/exceptions.rst:177 +msgid "" +"The :attr:`name` and :attr:`path` attributes can be set using keyword-only " +"arguments to the constructor. When set they represent the name of the module " +"that was attempted to be imported and the path to any file which triggered " +"the exception, respectively." +msgstr "" + +#: ../Doc/library/exceptions.rst:182 +msgid "Added the :attr:`name` and :attr:`path` attributes." +msgstr "" + +#: ../Doc/library/exceptions.rst:187 +msgid "" +"A subclass of :exc:`ImportError` which is raised by :keyword:`import` when a " +"module could not be located. It is also raised when ``None`` is found in :" +"data:`sys.modules`." +msgstr "" + +#: ../Doc/library/exceptions.rst:196 +msgid "" +"Raised when a sequence subscript is out of range. (Slice indices are " +"silently truncated to fall in the allowed range; if an index is not an " +"integer, :exc:`TypeError` is raised.)" +msgstr "" + +#: ../Doc/library/exceptions.rst:205 +msgid "" +"Raised when a mapping (dictionary) key is not found in the set of existing " +"keys." +msgstr "" + +#: ../Doc/library/exceptions.rst:212 +msgid "" +"Raised when the user hits the interrupt key (normally :kbd:`Control-C` or :" +"kbd:`Delete`). During execution, a check for interrupts is made regularly. " +"The exception inherits from :exc:`BaseException` so as to not be " +"accidentally caught by code that catches :exc:`Exception` and thus prevent " +"the interpreter from exiting." +msgstr "" + +#: ../Doc/library/exceptions.rst:221 +msgid "" +"Raised when an operation runs out of memory but the situation may still be " +"rescued (by deleting some objects). The associated value is a string " +"indicating what kind of (internal) operation ran out of memory. Note that " +"because of the underlying memory management architecture (C's :c:func:" +"`malloc` function), the interpreter may not always be able to completely " +"recover from this situation; it nevertheless raises an exception so that a " +"stack traceback can be printed, in case a run-away program was the cause." +msgstr "" + +#: ../Doc/library/exceptions.rst:232 +msgid "" +"Raised when a local or global name is not found. This applies only to " +"unqualified names. The associated value is an error message that includes " +"the name that could not be found." +msgstr "" + +#: ../Doc/library/exceptions.rst:239 +msgid "" +"This exception is derived from :exc:`RuntimeError`. In user defined base " +"classes, abstract methods should raise this exception when they require " +"derived classes to override the method, or while the class is being " +"developed to indicate that the real implementation still needs to be added." +msgstr "" + +#: ../Doc/library/exceptions.rst:246 +msgid "" +"It should not be used to indicate that an operater or method is not meant to " +"be supported at all -- in that case either leave the operator / method " +"undefined or, if a subclass, set it to :data:`None`." +msgstr "" + +#: ../Doc/library/exceptions.rst:252 +msgid "" +"``NotImplementedError`` and ``NotImplemented`` are not interchangeable, even " +"though they have similar names and purposes. See :data:`NotImplemented` for " +"details on when to use it." +msgstr "" + +#: ../Doc/library/exceptions.rst:261 +msgid "" +"This exception is raised when a system function returns a system-related " +"error, including I/O failures such as \"file not found\" or \"disk full" +"\" (not for illegal argument types or other incidental errors)." +msgstr "" + +#: ../Doc/library/exceptions.rst:265 +msgid "" +"The second form of the constructor sets the corresponding attributes, " +"described below. The attributes default to :const:`None` if not specified. " +"For backwards compatibility, if three arguments are passed, the :attr:" +"`~BaseException.args` attribute contains only a 2-tuple of the first two " +"constructor arguments." +msgstr "" + +#: ../Doc/library/exceptions.rst:271 +msgid "" +"The constructor often actually returns a subclass of :exc:`OSError`, as " +"described in `OS exceptions`_ below. The particular subclass depends on the " +"final :attr:`.errno` value. This behaviour only occurs when constructing :" +"exc:`OSError` directly or via an alias, and is not inherited when " +"subclassing." +msgstr "" + +#: ../Doc/library/exceptions.rst:279 +msgid "A numeric error code from the C variable :c:data:`errno`." +msgstr "" + +#: ../Doc/library/exceptions.rst:283 +msgid "" +"Under Windows, this gives you the native Windows error code. The :attr:`." +"errno` attribute is then an approximate translation, in POSIX terms, of that " +"native error code." +msgstr "" + +#: ../Doc/library/exceptions.rst:287 +msgid "" +"Under Windows, if the *winerror* constructor argument is an integer, the :" +"attr:`.errno` attribute is determined from the Windows error code, and the " +"*errno* argument is ignored. On other platforms, the *winerror* argument is " +"ignored, and the :attr:`winerror` attribute does not exist." +msgstr "" + +#: ../Doc/library/exceptions.rst:295 +msgid "" +"The corresponding error message, as provided by the operating system. It is " +"formatted by the C functions :c:func:`perror` under POSIX, and :c:func:" +"`FormatMessage` under Windows." +msgstr "" + +#: ../Doc/library/exceptions.rst:303 +msgid "" +"For exceptions that involve a file system path (such as :func:`open` or :" +"func:`os.unlink`), :attr:`filename` is the file name passed to the function. " +"For functions that involve two file system paths (such as :func:`os." +"rename`), :attr:`filename2` corresponds to the second file name passed to " +"the function." +msgstr "" + +#: ../Doc/library/exceptions.rst:310 +msgid "" +":exc:`EnvironmentError`, :exc:`IOError`, :exc:`WindowsError`, :exc:`socket." +"error`, :exc:`select.error` and :exc:`mmap.error` have been merged into :exc:" +"`OSError`, and the constructor may return a subclass." +msgstr "" + +#: ../Doc/library/exceptions.rst:316 +msgid "" +"The :attr:`filename` attribute is now the original file name passed to the " +"function, instead of the name encoded to or decoded from the filesystem " +"encoding. Also, the *filename2* constructor argument and attribute was " +"added." +msgstr "" + +#: ../Doc/library/exceptions.rst:325 +msgid "" +"Raised when the result of an arithmetic operation is too large to be " +"represented. This cannot occur for integers (which would rather raise :exc:" +"`MemoryError` than give up). However, for historical reasons, OverflowError " +"is sometimes raised for integers that are outside a required range. " +"Because of the lack of standardization of floating point exception handling " +"in C, most floating point operations are not checked." +msgstr "" + +#: ../Doc/library/exceptions.rst:335 +msgid "" +"This exception is derived from :exc:`RuntimeError`. It is raised when the " +"interpreter detects that the maximum recursion depth (see :func:`sys." +"getrecursionlimit`) is exceeded." +msgstr "" + +#: ../Doc/library/exceptions.rst:339 +msgid "Previously, a plain :exc:`RuntimeError` was raised." +msgstr "" + +#: ../Doc/library/exceptions.rst:345 +msgid "" +"This exception is raised when a weak reference proxy, created by the :func:" +"`weakref.proxy` function, is used to access an attribute of the referent " +"after it has been garbage collected. For more information on weak " +"references, see the :mod:`weakref` module." +msgstr "" + +#: ../Doc/library/exceptions.rst:353 +msgid "" +"Raised when an error is detected that doesn't fall in any of the other " +"categories. The associated value is a string indicating what precisely went " +"wrong." +msgstr "" + +#: ../Doc/library/exceptions.rst:360 +msgid "" +"Raised by built-in function :func:`next` and an :term:`iterator`\\'s :meth:" +"`~iterator.__next__` method to signal that there are no further items " +"produced by the iterator." +msgstr "" + +#: ../Doc/library/exceptions.rst:364 +msgid "" +"The exception object has a single attribute :attr:`value`, which is given as " +"an argument when constructing the exception, and defaults to :const:`None`." +msgstr "" + +#: ../Doc/library/exceptions.rst:368 +msgid "" +"When a :term:`generator` or :term:`coroutine` function returns, a new :exc:" +"`StopIteration` instance is raised, and the value returned by the function " +"is used as the :attr:`value` parameter to the constructor of the exception." +msgstr "" + +#: ../Doc/library/exceptions.rst:373 +msgid "" +"If a generator function defined in the presence of a ``from __future__ " +"import generator_stop`` directive raises :exc:`StopIteration`, it will be " +"converted into a :exc:`RuntimeError` (retaining the :exc:`StopIteration` as " +"the new exception's cause)." +msgstr "" + +#: ../Doc/library/exceptions.rst:378 +msgid "" +"Added ``value`` attribute and the ability for generator functions to use it " +"to return a value." +msgstr "" + +#: ../Doc/library/exceptions.rst:382 +msgid "Introduced the RuntimeError transformation." +msgstr "" + +#: ../Doc/library/exceptions.rst:387 +msgid "" +"Must be raised by :meth:`__anext__` method of an :term:`asynchronous " +"iterator` object to stop the iteration." +msgstr "" + +#: ../Doc/library/exceptions.rst:394 +msgid "" +"Raised when the parser encounters a syntax error. This may occur in an :" +"keyword:`import` statement, in a call to the built-in functions :func:`exec` " +"or :func:`eval`, or when reading the initial script or standard input (also " +"interactively)." +msgstr "" + +#: ../Doc/library/exceptions.rst:399 +msgid "" +"Instances of this class have attributes :attr:`filename`, :attr:`lineno`, :" +"attr:`offset` and :attr:`text` for easier access to the details. :func:" +"`str` of the exception instance returns only the message." +msgstr "" + +#: ../Doc/library/exceptions.rst:406 +msgid "" +"Base class for syntax errors related to incorrect indentation. This is a " +"subclass of :exc:`SyntaxError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:412 +msgid "" +"Raised when indentation contains an inconsistent use of tabs and spaces. " +"This is a subclass of :exc:`IndentationError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:418 +msgid "" +"Raised when the interpreter finds an internal error, but the situation does " +"not look so serious to cause it to abandon all hope. The associated value is " +"a string indicating what went wrong (in low-level terms)." +msgstr "" + +#: ../Doc/library/exceptions.rst:422 +msgid "" +"You should report this to the author or maintainer of your Python " +"interpreter. Be sure to report the version of the Python interpreter (``sys." +"version``; it is also printed at the start of an interactive Python " +"session), the exact error message (the exception's associated value) and if " +"possible the source of the program that triggered the error." +msgstr "" + +#: ../Doc/library/exceptions.rst:431 +msgid "" +"This exception is raised by the :func:`sys.exit` function. It inherits " +"from :exc:`BaseException` instead of :exc:`Exception` so that it is not " +"accidentally caught by code that catches :exc:`Exception`. This allows the " +"exception to properly propagate up and cause the interpreter to exit. When " +"it is not handled, the Python interpreter exits; no stack traceback is " +"printed. The constructor accepts the same optional argument passed to :func:" +"`sys.exit`. If the value is an integer, it specifies the system exit status " +"(passed to C's :c:func:`exit` function); if it is ``None``, the exit status " +"is zero; if it has another type (such as a string), the object's value is " +"printed and the exit status is one." +msgstr "" + +#: ../Doc/library/exceptions.rst:442 +msgid "" +"A call to :func:`sys.exit` is translated into an exception so that clean-up " +"handlers (:keyword:`finally` clauses of :keyword:`try` statements) can be " +"executed, and so that a debugger can execute a script without running the " +"risk of losing control. The :func:`os._exit` function can be used if it is " +"absolutely positively necessary to exit immediately (for example, in the " +"child process after a call to :func:`os.fork`)." +msgstr "" + +#: ../Doc/library/exceptions.rst:451 +msgid "" +"The exit status or error message that is passed to the constructor. " +"(Defaults to ``None``.)" +msgstr "" + +#: ../Doc/library/exceptions.rst:457 +msgid "" +"Raised when an operation or function is applied to an object of " +"inappropriate type. The associated value is a string giving details about " +"the type mismatch." +msgstr "" + +#: ../Doc/library/exceptions.rst:460 +msgid "" +"This exception may be raised by user code to indicate that an attempted " +"operation on an object is not supported, and is not meant to be. If an " +"object is meant to support a given operation but has not yet provided an " +"implementation, :exc:`NotImplementedError` is the proper exception to raise." +msgstr "" + +#: ../Doc/library/exceptions.rst:465 +msgid "" +"Passing arguments of the wrong type (e.g. passing a :class:`list` when an :" +"class:`int` is expected) should result in a :exc:`TypeError`, but passing " +"arguments with the wrong value (e.g. a number outside expected boundaries) " +"should result in a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:472 +msgid "" +"Raised when a reference is made to a local variable in a function or method, " +"but no value has been bound to that variable. This is a subclass of :exc:" +"`NameError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:479 +msgid "" +"Raised when a Unicode-related encoding or decoding error occurs. It is a " +"subclass of :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:482 +msgid "" +":exc:`UnicodeError` has attributes that describe the encoding or decoding " +"error. For example, ``err.object[err.start:err.end]`` gives the particular " +"invalid input that the codec failed on." +msgstr "" + +#: ../Doc/library/exceptions.rst:488 +msgid "The name of the encoding that raised the error." +msgstr "" + +#: ../Doc/library/exceptions.rst:492 +msgid "A string describing the specific codec error." +msgstr "" + +#: ../Doc/library/exceptions.rst:496 +msgid "The object the codec was attempting to encode or decode." +msgstr "" + +#: ../Doc/library/exceptions.rst:500 +msgid "The first index of invalid data in :attr:`object`." +msgstr "" + +#: ../Doc/library/exceptions.rst:504 +msgid "The index after the last invalid data in :attr:`object`." +msgstr "" + +#: ../Doc/library/exceptions.rst:509 +msgid "" +"Raised when a Unicode-related error occurs during encoding. It is a " +"subclass of :exc:`UnicodeError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:515 +msgid "" +"Raised when a Unicode-related error occurs during decoding. It is a " +"subclass of :exc:`UnicodeError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:521 +msgid "" +"Raised when a Unicode-related error occurs during translating. It is a " +"subclass of :exc:`UnicodeError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:527 +msgid "" +"Raised when a built-in operation or function receives an argument that has " +"the right type but an inappropriate value, and the situation is not " +"described by a more precise exception such as :exc:`IndexError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:534 +msgid "" +"Raised when the second argument of a division or modulo operation is zero. " +"The associated value is a string indicating the type of the operands and the " +"operation." +msgstr "" + +#: ../Doc/library/exceptions.rst:539 +msgid "" +"The following exceptions are kept for compatibility with previous versions; " +"starting from Python 3.3, they are aliases of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:548 +msgid "Only available on Windows." +msgstr "" + +#: ../Doc/library/exceptions.rst:552 +msgid "OS exceptions" +msgstr "" + +#: ../Doc/library/exceptions.rst:554 +msgid "" +"The following exceptions are subclasses of :exc:`OSError`, they get raised " +"depending on the system error code." +msgstr "" + +#: ../Doc/library/exceptions.rst:559 +msgid "" +"Raised when an operation would block on an object (e.g. socket) set for non-" +"blocking operation. Corresponds to :c:data:`errno` ``EAGAIN``, ``EALREADY``, " +"``EWOULDBLOCK`` and ``EINPROGRESS``." +msgstr "" + +#: ../Doc/library/exceptions.rst:564 +msgid "" +"In addition to those of :exc:`OSError`, :exc:`BlockingIOError` can have one " +"more attribute:" +msgstr "" + +#: ../Doc/library/exceptions.rst:569 +msgid "" +"An integer containing the number of characters written to the stream before " +"it blocked. This attribute is available when using the buffered I/O classes " +"from the :mod:`io` module." +msgstr "" + +#: ../Doc/library/exceptions.rst:575 +msgid "" +"Raised when an operation on a child process failed. Corresponds to :c:data:" +"`errno` ``ECHILD``." +msgstr "" + +#: ../Doc/library/exceptions.rst:580 +msgid "A base class for connection-related issues." +msgstr "" + +#: ../Doc/library/exceptions.rst:582 +msgid "" +"Subclasses are :exc:`BrokenPipeError`, :exc:`ConnectionAbortedError`, :exc:" +"`ConnectionRefusedError` and :exc:`ConnectionResetError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:587 +msgid "" +"A subclass of :exc:`ConnectionError`, raised when trying to write on a pipe " +"while the other end has been closed, or trying to write on a socket which " +"has been shutdown for writing. Corresponds to :c:data:`errno` ``EPIPE`` and " +"``ESHUTDOWN``." +msgstr "" + +#: ../Doc/library/exceptions.rst:594 +msgid "" +"A subclass of :exc:`ConnectionError`, raised when a connection attempt is " +"aborted by the peer. Corresponds to :c:data:`errno` ``ECONNABORTED``." +msgstr "" + +#: ../Doc/library/exceptions.rst:600 +msgid "" +"A subclass of :exc:`ConnectionError`, raised when a connection attempt is " +"refused by the peer. Corresponds to :c:data:`errno` ``ECONNREFUSED``." +msgstr "" + +#: ../Doc/library/exceptions.rst:606 +msgid "" +"A subclass of :exc:`ConnectionError`, raised when a connection is reset by " +"the peer. Corresponds to :c:data:`errno` ``ECONNRESET``." +msgstr "" + +#: ../Doc/library/exceptions.rst:612 +msgid "" +"Raised when trying to create a file or directory which already exists. " +"Corresponds to :c:data:`errno` ``EEXIST``." +msgstr "" + +#: ../Doc/library/exceptions.rst:617 +msgid "" +"Raised when a file or directory is requested but doesn't exist. Corresponds " +"to :c:data:`errno` ``ENOENT``." +msgstr "" + +#: ../Doc/library/exceptions.rst:622 +msgid "" +"Raised when a system call is interrupted by an incoming signal. Corresponds " +"to :c:data:`errno` :py:data:`~errno.EINTR`." +msgstr "" + +#: ../Doc/library/exceptions.rst:625 +msgid "" +"Python now retries system calls when a syscall is interrupted by a signal, " +"except if the signal handler raises an exception (see :pep:`475` for the " +"rationale), instead of raising :exc:`InterruptedError`." +msgstr "" + +#: ../Doc/library/exceptions.rst:632 +msgid "" +"Raised when a file operation (such as :func:`os.remove`) is requested on a " +"directory. Corresponds to :c:data:`errno` ``EISDIR``." +msgstr "" + +#: ../Doc/library/exceptions.rst:638 +msgid "" +"Raised when a directory operation (such as :func:`os.listdir`) is requested " +"on something which is not a directory. Corresponds to :c:data:`errno` " +"``ENOTDIR``." +msgstr "" + +#: ../Doc/library/exceptions.rst:644 +msgid "" +"Raised when trying to run an operation without the adequate access rights - " +"for example filesystem permissions. Corresponds to :c:data:`errno` " +"``EACCES`` and ``EPERM``." +msgstr "" + +#: ../Doc/library/exceptions.rst:650 +msgid "" +"Raised when a given process doesn't exist. Corresponds to :c:data:`errno` " +"``ESRCH``." +msgstr "" + +#: ../Doc/library/exceptions.rst:655 +msgid "" +"Raised when a system function timed out at the system level. Corresponds to :" +"c:data:`errno` ``ETIMEDOUT``." +msgstr "" + +#: ../Doc/library/exceptions.rst:658 +msgid "All the above :exc:`OSError` subclasses were added." +msgstr "" + +#: ../Doc/library/exceptions.rst:664 +msgid ":pep:`3151` - Reworking the OS and IO exception hierarchy" +msgstr "" + +#: ../Doc/library/exceptions.rst:670 +msgid "" +"The following exceptions are used as warning categories; see the :mod:" +"`warnings` module for more information." +msgstr "" + +#: ../Doc/library/exceptions.rst:675 +msgid "Base class for warning categories." +msgstr "" + +#: ../Doc/library/exceptions.rst:680 +msgid "Base class for warnings generated by user code." +msgstr "" + +#: ../Doc/library/exceptions.rst:685 +msgid "Base class for warnings about deprecated features." +msgstr "" + +#: ../Doc/library/exceptions.rst:690 +msgid "" +"Base class for warnings about features which will be deprecated in the " +"future." +msgstr "" + +#: ../Doc/library/exceptions.rst:695 +msgid "Base class for warnings about dubious syntax." +msgstr "" + +#: ../Doc/library/exceptions.rst:700 +msgid "Base class for warnings about dubious runtime behavior." +msgstr "" + +#: ../Doc/library/exceptions.rst:705 +msgid "" +"Base class for warnings about constructs that will change semantically in " +"the future." +msgstr "" + +#: ../Doc/library/exceptions.rst:711 +msgid "Base class for warnings about probable mistakes in module imports." +msgstr "" + +#: ../Doc/library/exceptions.rst:716 +msgid "Base class for warnings related to Unicode." +msgstr "" + +#: ../Doc/library/exceptions.rst:721 +msgid "" +"Base class for warnings related to :class:`bytes` and :class:`bytearray`." +msgstr "" + +#: ../Doc/library/exceptions.rst:726 +msgid "Base class for warnings related to resource usage." +msgstr "" + +#: ../Doc/library/exceptions.rst:733 +msgid "Exception hierarchy" +msgstr "" + +#: ../Doc/library/exceptions.rst:735 +msgid "The class hierarchy for built-in exceptions is:" +msgstr "" + +#: ../Doc/library/faulthandler.rst:2 +msgid ":mod:`faulthandler` --- Dump the Python traceback" +msgstr "" + +#: ../Doc/library/faulthandler.rst:11 +msgid "" +"This module contains functions to dump Python tracebacks explicitly, on a " +"fault, after a timeout, or on a user signal. Call :func:`faulthandler." +"enable` to install fault handlers for the :const:`SIGSEGV`, :const:" +"`SIGFPE`, :const:`SIGABRT`, :const:`SIGBUS`, and :const:`SIGILL` signals. " +"You can also enable them at startup by setting the :envvar:" +"`PYTHONFAULTHANDLER` environment variable or by using the :option:`-X` " +"``faulthandler`` command line option." +msgstr "" + +#: ../Doc/library/faulthandler.rst:18 +msgid "" +"The fault handler is compatible with system fault handlers like Apport or " +"the Windows fault handler. The module uses an alternative stack for signal " +"handlers if the :c:func:`sigaltstack` function is available. This allows it " +"to dump the traceback even on a stack overflow." +msgstr "" + +#: ../Doc/library/faulthandler.rst:23 +msgid "" +"The fault handler is called on catastrophic cases and therefore can only use " +"signal-safe functions (e.g. it cannot allocate memory on the heap). Because " +"of this limitation traceback dumping is minimal compared to normal Python " +"tracebacks:" +msgstr "" + +#: ../Doc/library/faulthandler.rst:28 +msgid "" +"Only ASCII is supported. The ``backslashreplace`` error handler is used on " +"encoding." +msgstr "" + +#: ../Doc/library/faulthandler.rst:30 +msgid "Each string is limited to 500 characters." +msgstr "" + +#: ../Doc/library/faulthandler.rst:31 +msgid "" +"Only the filename, the function name and the line number are displayed. (no " +"source code)" +msgstr "" + +#: ../Doc/library/faulthandler.rst:33 +msgid "It is limited to 100 frames and 100 threads." +msgstr "" + +#: ../Doc/library/faulthandler.rst:34 +msgid "The order is reversed: the most recent call is shown first." +msgstr "" + +#: ../Doc/library/faulthandler.rst:36 +msgid "" +"By default, the Python traceback is written to :data:`sys.stderr`. To see " +"tracebacks, applications must be run in the terminal. A log file can " +"alternatively be passed to :func:`faulthandler.enable`." +msgstr "" + +#: ../Doc/library/faulthandler.rst:40 +msgid "" +"The module is implemented in C, so tracebacks can be dumped on a crash or " +"when Python is deadlocked." +msgstr "" + +#: ../Doc/library/faulthandler.rst:45 +msgid "Dumping the traceback" +msgstr "" + +#: ../Doc/library/faulthandler.rst:49 +msgid "" +"Dump the tracebacks of all threads into *file*. If *all_threads* is " +"``False``, dump only the current thread." +msgstr "" + +#: ../Doc/library/faulthandler.rst:52 ../Doc/library/faulthandler.rst:70 +#: ../Doc/library/faulthandler.rst:106 ../Doc/library/faulthandler.rst:128 +msgid "Added support for passing file descriptor to this function." +msgstr "" + +#: ../Doc/library/faulthandler.rst:57 +msgid "Fault handler state" +msgstr "" + +#: ../Doc/library/faulthandler.rst:61 +msgid "" +"Enable the fault handler: install handlers for the :const:`SIGSEGV`, :const:" +"`SIGFPE`, :const:`SIGABRT`, :const:`SIGBUS` and :const:`SIGILL` signals to " +"dump the Python traceback. If *all_threads* is ``True``, produce tracebacks " +"for every running thread. Otherwise, dump only the current thread." +msgstr "" + +#: ../Doc/library/faulthandler.rst:67 +msgid "" +"The *file* must be kept open until the fault handler is disabled: see :ref:" +"`issue with file descriptors `." +msgstr "" + +#: ../Doc/library/faulthandler.rst:73 +msgid "On Windows, a handler for Windows exception is also installed." +msgstr "" + +#: ../Doc/library/faulthandler.rst:78 +msgid "" +"Disable the fault handler: uninstall the signal handlers installed by :func:" +"`enable`." +msgstr "" + +#: ../Doc/library/faulthandler.rst:83 +msgid "Check if the fault handler is enabled." +msgstr "" + +#: ../Doc/library/faulthandler.rst:87 +msgid "Dumping the tracebacks after a timeout" +msgstr "" + +#: ../Doc/library/faulthandler.rst:91 +msgid "" +"Dump the tracebacks of all threads, after a timeout of *timeout* seconds, or " +"every *timeout* seconds if *repeat* is ``True``. If *exit* is ``True``, " +"call :c:func:`_exit` with status=1 after dumping the tracebacks. (Note :c:" +"func:`_exit` exits the process immediately, which means it doesn't do any " +"cleanup like flushing file buffers.) If the function is called twice, the " +"new call replaces previous parameters and resets the timeout. The timer has " +"a sub-second resolution." +msgstr "" + +#: ../Doc/library/faulthandler.rst:99 +msgid "" +"The *file* must be kept open until the traceback is dumped or :func:" +"`cancel_dump_traceback_later` is called: see :ref:`issue with file " +"descriptors `." +msgstr "" + +#: ../Doc/library/faulthandler.rst:103 +msgid "" +"This function is implemented using a watchdog thread and therefore is not " +"available if Python is compiled with threads disabled." +msgstr "" + +#: ../Doc/library/faulthandler.rst:111 +msgid "Cancel the last call to :func:`dump_traceback_later`." +msgstr "" + +#: ../Doc/library/faulthandler.rst:115 +msgid "Dumping the traceback on a user signal" +msgstr "" + +#: ../Doc/library/faulthandler.rst:119 +msgid "" +"Register a user signal: install a handler for the *signum* signal to dump " +"the traceback of all threads, or of the current thread if *all_threads* is " +"``False``, into *file*. Call the previous handler if chain is ``True``." +msgstr "" + +#: ../Doc/library/faulthandler.rst:123 +msgid "" +"The *file* must be kept open until the signal is unregistered by :func:" +"`unregister`: see :ref:`issue with file descriptors `." +msgstr "" + +#: ../Doc/library/faulthandler.rst:126 ../Doc/library/faulthandler.rst:137 +msgid "Not available on Windows." +msgstr "" + +#: ../Doc/library/faulthandler.rst:133 +msgid "" +"Unregister a user signal: uninstall the handler of the *signum* signal " +"installed by :func:`register`. Return ``True`` if the signal was registered, " +"``False`` otherwise." +msgstr "" + +#: ../Doc/library/faulthandler.rst:143 +msgid "Issue with file descriptors" +msgstr "" + +#: ../Doc/library/faulthandler.rst:145 +msgid "" +":func:`enable`, :func:`dump_traceback_later` and :func:`register` keep the " +"file descriptor of their *file* argument. If the file is closed and its file " +"descriptor is reused by a new file, or if :func:`os.dup2` is used to replace " +"the file descriptor, the traceback will be written into a different file. " +"Call these functions again each time that the file is replaced." +msgstr "" + +#: ../Doc/library/faulthandler.rst:157 +msgid "" +"Example of a segmentation fault on Linux with and without enabling the fault " +"handler::" +msgstr "" + +#: ../Doc/library/fcntl.rst:2 +msgid ":mod:`fcntl` --- The ``fcntl`` and ``ioctl`` system calls" +msgstr "" + +#: ../Doc/library/fcntl.rst:16 +msgid "" +"This module performs file control and I/O control on file descriptors. It is " +"an interface to the :c:func:`fcntl` and :c:func:`ioctl` Unix routines. For " +"a complete description of these calls, see :manpage:`fcntl(2)` and :manpage:" +"`ioctl(2)` Unix manual pages." +msgstr "" + +#: ../Doc/library/fcntl.rst:21 +msgid "" +"All functions in this module take a file descriptor *fd* as their first " +"argument. This can be an integer file descriptor, such as returned by ``sys." +"stdin.fileno()``, or an :class:`io.IOBase` object, such as ``sys.stdin`` " +"itself, which provides a :meth:`~io.IOBase.fileno` that returns a genuine " +"file descriptor." +msgstr "" + +#: ../Doc/library/fcntl.rst:27 +msgid "" +"Operations in this module used to raise an :exc:`IOError` where they now " +"raise an :exc:`OSError`." +msgstr "" + +#: ../Doc/library/fcntl.rst:32 ../Doc/library/syslog.rst:18 +#: ../Doc/library/termios.rst:28 ../Doc/library/traceback.rst:23 +msgid "The module defines the following functions:" +msgstr "" + +#: ../Doc/library/fcntl.rst:37 +msgid "" +"Perform the operation *cmd* on file descriptor *fd* (file objects providing " +"a :meth:`~io.IOBase.fileno` method are accepted as well). The values used " +"for *cmd* are operating system dependent, and are available as constants in " +"the :mod:`fcntl` module, using the same names as used in the relevant C " +"header files. The argument *arg* can either be an integer value, or a :class:" +"`bytes` object. With an integer value, the return value of this function is " +"the integer return value of the C :c:func:`fcntl` call. When the argument " +"is bytes it represents a binary structure, e.g. created by :func:`struct." +"pack`. The binary data is copied to a buffer whose address is passed to the " +"C :c:func:`fcntl` call. The return value after a successful call is the " +"contents of the buffer, converted to a :class:`bytes` object. The length of " +"the returned object will be the same as the length of the *arg* argument. " +"This is limited to 1024 bytes. If the information returned in the buffer by " +"the operating system is larger than 1024 bytes, this is most likely to " +"result in a segmentation violation or a more subtle data corruption." +msgstr "" + +#: ../Doc/library/fcntl.rst:54 +msgid "If the :c:func:`fcntl` fails, an :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/fcntl.rst:59 +msgid "" +"This function is identical to the :func:`~fcntl.fcntl` function, except that " +"the argument handling is even more complicated." +msgstr "" + +#: ../Doc/library/fcntl.rst:62 +msgid "" +"The *request* parameter is limited to values that can fit in 32-bits. " +"Additional constants of interest for use as the *request* argument can be " +"found in the :mod:`termios` module, under the same names as used in the " +"relevant C header files." +msgstr "" + +#: ../Doc/library/fcntl.rst:67 +msgid "" +"The parameter *arg* can be one of an integer, an object supporting the read-" +"only buffer interface (like :class:`bytes`) or an object supporting the read-" +"write buffer interface (like :class:`bytearray`)." +msgstr "" + +#: ../Doc/library/fcntl.rst:71 +msgid "" +"In all but the last case, behaviour is as for the :func:`~fcntl.fcntl` " +"function." +msgstr "" + +#: ../Doc/library/fcntl.rst:74 +msgid "" +"If a mutable buffer is passed, then the behaviour is determined by the value " +"of the *mutate_flag* parameter." +msgstr "" + +#: ../Doc/library/fcntl.rst:77 +msgid "" +"If it is false, the buffer's mutability is ignored and behaviour is as for a " +"read-only buffer, except that the 1024 byte limit mentioned above is avoided " +"-- so long as the buffer you pass is at least as long as what the operating " +"system wants to put there, things should work." +msgstr "" + +#: ../Doc/library/fcntl.rst:82 +msgid "" +"If *mutate_flag* is true (the default), then the buffer is (in effect) " +"passed to the underlying :func:`ioctl` system call, the latter's return code " +"is passed back to the calling Python, and the buffer's new contents reflect " +"the action of the :func:`ioctl`. This is a slight simplification, because " +"if the supplied buffer is less than 1024 bytes long it is first copied into " +"a static buffer 1024 bytes long which is then passed to :func:`ioctl` and " +"copied back into the supplied buffer." +msgstr "" + +#: ../Doc/library/fcntl.rst:90 +msgid "If the :c:func:`ioctl` fails, an :exc:`OSError` exception is raised." +msgstr "" + +#: ../Doc/library/fcntl.rst:92 +msgid "An example::" +msgstr "" + +#: ../Doc/library/fcntl.rst:108 +msgid "" +"Perform the lock operation *operation* on file descriptor *fd* (file objects " +"providing a :meth:`~io.IOBase.fileno` method are accepted as well). See the " +"Unix manual :manpage:`flock(2)` for details. (On some systems, this " +"function is emulated using :c:func:`fcntl`.)" +msgstr "" + +#: ../Doc/library/fcntl.rst:113 +msgid "If the :c:func:`flock` fails, an :exc:`OSError` exception is raised." +msgstr "" + +#: ../Doc/library/fcntl.rst:118 +msgid "" +"This is essentially a wrapper around the :func:`~fcntl.fcntl` locking calls. " +"*fd* is the file descriptor of the file to lock or unlock, and *cmd* is one " +"of the following values:" +msgstr "" + +#: ../Doc/library/fcntl.rst:122 +msgid ":const:`LOCK_UN` -- unlock" +msgstr "" + +#: ../Doc/library/fcntl.rst:123 +msgid ":const:`LOCK_SH` -- acquire a shared lock" +msgstr "" + +#: ../Doc/library/fcntl.rst:124 +msgid ":const:`LOCK_EX` -- acquire an exclusive lock" +msgstr "" + +#: ../Doc/library/fcntl.rst:126 +msgid "" +"When *cmd* is :const:`LOCK_SH` or :const:`LOCK_EX`, it can also be bitwise " +"ORed with :const:`LOCK_NB` to avoid blocking on lock acquisition. If :const:" +"`LOCK_NB` is used and the lock cannot be acquired, an :exc:`OSError` will be " +"raised and the exception will have an *errno* attribute set to :const:" +"`EACCES` or :const:`EAGAIN` (depending on the operating system; for " +"portability, check for both values). On at least some systems, :const:" +"`LOCK_EX` can only be used if the file descriptor refers to a file opened " +"for writing." +msgstr "" + +#: ../Doc/library/fcntl.rst:135 +msgid "" +"*len* is the number of bytes to lock, *start* is the byte offset at which " +"the lock starts, relative to *whence*, and *whence* is as with :func:`io." +"IOBase.seek`, specifically:" +msgstr "" + +#: ../Doc/library/fcntl.rst:139 +msgid ":const:`0` -- relative to the start of the file (:data:`os.SEEK_SET`)" +msgstr "" + +#: ../Doc/library/fcntl.rst:140 +msgid "" +":const:`1` -- relative to the current buffer position (:data:`os.SEEK_CUR`)" +msgstr "" + +#: ../Doc/library/fcntl.rst:141 +msgid ":const:`2` -- relative to the end of the file (:data:`os.SEEK_END`)" +msgstr "" + +#: ../Doc/library/fcntl.rst:143 +msgid "" +"The default for *start* is 0, which means to start at the beginning of the " +"file. The default for *len* is 0 which means to lock to the end of the " +"file. The default for *whence* is also 0." +msgstr "" + +#: ../Doc/library/fcntl.rst:147 +msgid "Examples (all on a SVR4 compliant system)::" +msgstr "" + +#: ../Doc/library/fcntl.rst:157 +msgid "" +"Note that in the first example the return value variable *rv* will hold an " +"integer value; in the second example it will hold a :class:`bytes` object. " +"The structure lay-out for the *lockdata* variable is system dependent --- " +"therefore using the :func:`flock` call may be better." +msgstr "" + +#: ../Doc/library/fcntl.rst:168 ../Doc/library/filesys.rst:32 +msgid "Module :mod:`os`" +msgstr "" + +#: ../Doc/library/fcntl.rst:166 +msgid "" +"If the locking flags :data:`~os.O_SHLOCK` and :data:`~os.O_EXLOCK` are " +"present in the :mod:`os` module (on BSD only), the :func:`os.open` function " +"provides an alternative to the :func:`lockf` and :func:`flock` functions." +msgstr "" + +#: ../Doc/library/filecmp.rst:2 +msgid ":mod:`filecmp` --- File and Directory Comparisons" +msgstr "" + +#: ../Doc/library/filecmp.rst:9 +msgid "**Source code:** :source:`Lib/filecmp.py`" +msgstr "" + +#: ../Doc/library/filecmp.rst:13 +msgid "" +"The :mod:`filecmp` module defines functions to compare files and " +"directories, with various optional time/correctness trade-offs. For " +"comparing files, see also the :mod:`difflib` module." +msgstr "" + +#: ../Doc/library/filecmp.rst:17 +msgid "The :mod:`filecmp` module defines the following functions:" +msgstr "" + +#: ../Doc/library/filecmp.rst:22 +msgid "" +"Compare the files named *f1* and *f2*, returning ``True`` if they seem " +"equal, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/filecmp.rst:25 +msgid "" +"If *shallow* is true, files with identical :func:`os.stat` signatures are " +"taken to be equal. Otherwise, the contents of the files are compared." +msgstr "" + +#: ../Doc/library/filecmp.rst:28 +msgid "" +"Note that no external programs are called from this function, giving it " +"portability and efficiency." +msgstr "" + +#: ../Doc/library/filecmp.rst:31 +msgid "" +"This function uses a cache for past comparisons and the results, with cache " +"entries invalidated if the :func:`os.stat` information for the file " +"changes. The entire cache may be cleared using :func:`clear_cache`." +msgstr "" + +#: ../Doc/library/filecmp.rst:38 +msgid "" +"Compare the files in the two directories *dir1* and *dir2* whose names are " +"given by *common*." +msgstr "" + +#: ../Doc/library/filecmp.rst:41 +msgid "" +"Returns three lists of file names: *match*, *mismatch*, *errors*. *match* " +"contains the list of files that match, *mismatch* contains the names of " +"those that don't, and *errors* lists the names of files which could not be " +"compared. Files are listed in *errors* if they don't exist in one of the " +"directories, the user lacks permission to read them or if the comparison " +"could not be done for some other reason." +msgstr "" + +#: ../Doc/library/filecmp.rst:48 +msgid "" +"The *shallow* parameter has the same meaning and default value as for :func:" +"`filecmp.cmp`." +msgstr "" + +#: ../Doc/library/filecmp.rst:51 +msgid "" +"For example, ``cmpfiles('a', 'b', ['c', 'd/e'])`` will compare ``a/c`` with " +"``b/c`` and ``a/d/e`` with ``b/d/e``. ``'c'`` and ``'d/e'`` will each be in " +"one of the three returned lists." +msgstr "" + +#: ../Doc/library/filecmp.rst:58 +msgid "" +"Clear the filecmp cache. This may be useful if a file is compared so quickly " +"after it is modified that it is within the mtime resolution of the " +"underlying filesystem." +msgstr "" + +#: ../Doc/library/filecmp.rst:68 +msgid "The :class:`dircmp` class" +msgstr "" + +#: ../Doc/library/filecmp.rst:72 +msgid "" +"Construct a new directory comparison object, to compare the directories *a* " +"and *b*. *ignore* is a list of names to ignore, and defaults to :attr:" +"`filecmp.DEFAULT_IGNORES`. *hide* is a list of names to hide, and defaults " +"to ``[os.curdir, os.pardir]``." +msgstr "" + +#: ../Doc/library/filecmp.rst:77 +msgid "" +"The :class:`dircmp` class compares files by doing *shallow* comparisons as " +"described for :func:`filecmp.cmp`." +msgstr "" + +#: ../Doc/library/filecmp.rst:80 +msgid "The :class:`dircmp` class provides the following methods:" +msgstr "" + +#: ../Doc/library/filecmp.rst:84 +msgid "Print (to :data:`sys.stdout`) a comparison between *a* and *b*." +msgstr "" + +#: ../Doc/library/filecmp.rst:88 +msgid "" +"Print a comparison between *a* and *b* and common immediate subdirectories." +msgstr "" + +#: ../Doc/library/filecmp.rst:93 +msgid "" +"Print a comparison between *a* and *b* and common subdirectories " +"(recursively)." +msgstr "" + +#: ../Doc/library/filecmp.rst:96 +msgid "" +"The :class:`dircmp` class offers a number of interesting attributes that may " +"be used to get various bits of information about the directory trees being " +"compared." +msgstr "" + +#: ../Doc/library/filecmp.rst:100 +msgid "" +"Note that via :meth:`__getattr__` hooks, all attributes are computed lazily, " +"so there is no speed penalty if only those attributes which are lightweight " +"to compute are used." +msgstr "" + +#: ../Doc/library/filecmp.rst:107 +msgid "The directory *a*." +msgstr "" + +#: ../Doc/library/filecmp.rst:112 +msgid "The directory *b*." +msgstr "" + +#: ../Doc/library/filecmp.rst:117 +msgid "Files and subdirectories in *a*, filtered by *hide* and *ignore*." +msgstr "" + +#: ../Doc/library/filecmp.rst:122 +msgid "Files and subdirectories in *b*, filtered by *hide* and *ignore*." +msgstr "" + +#: ../Doc/library/filecmp.rst:127 +msgid "Files and subdirectories in both *a* and *b*." +msgstr "" + +#: ../Doc/library/filecmp.rst:132 +msgid "Files and subdirectories only in *a*." +msgstr "" + +#: ../Doc/library/filecmp.rst:137 +msgid "Files and subdirectories only in *b*." +msgstr "" + +#: ../Doc/library/filecmp.rst:142 +msgid "Subdirectories in both *a* and *b*." +msgstr "" + +#: ../Doc/library/filecmp.rst:147 +msgid "Files in both *a* and *b*." +msgstr "" + +#: ../Doc/library/filecmp.rst:152 +msgid "" +"Names in both *a* and *b*, such that the type differs between the " +"directories, or names for which :func:`os.stat` reports an error." +msgstr "" + +#: ../Doc/library/filecmp.rst:158 +msgid "" +"Files which are identical in both *a* and *b*, using the class's file " +"comparison operator." +msgstr "" + +#: ../Doc/library/filecmp.rst:164 +msgid "" +"Files which are in both *a* and *b*, whose contents differ according to the " +"class's file comparison operator." +msgstr "" + +#: ../Doc/library/filecmp.rst:170 +msgid "Files which are in both *a* and *b*, but could not be compared." +msgstr "" + +#: ../Doc/library/filecmp.rst:175 +msgid "" +"A dictionary mapping names in :attr:`common_dirs` to :class:`dircmp` objects." +msgstr "" + +#: ../Doc/library/filecmp.rst:182 +msgid "List of directories ignored by :class:`dircmp` by default." +msgstr "" + +#: ../Doc/library/filecmp.rst:185 +msgid "" +"Here is a simplified example of using the ``subdirs`` attribute to search " +"recursively through two directories to show common different files::" +msgstr "" + +#: ../Doc/library/fileformats.rst:5 +msgid "File Formats" +msgstr "" + +#: ../Doc/library/fileformats.rst:7 +msgid "" +"The modules described in this chapter parse various miscellaneous file " +"formats that aren't markup languages and are not related to e-mail." +msgstr "" + +#: ../Doc/library/fileinput.rst:2 +msgid ":mod:`fileinput` --- Iterate over lines from multiple input streams" +msgstr "" + +#: ../Doc/library/fileinput.rst:10 +msgid "**Source code:** :source:`Lib/fileinput.py`" +msgstr "" + +#: ../Doc/library/fileinput.rst:14 +msgid "" +"This module implements a helper class and functions to quickly write a loop " +"over standard input or a list of files. If you just want to read or write " +"one file see :func:`open`." +msgstr "" + +#: ../Doc/library/fileinput.rst:18 +msgid "The typical use is::" +msgstr "" + +#: ../Doc/library/fileinput.rst:24 +msgid "" +"This iterates over the lines of all files listed in ``sys.argv[1:]``, " +"defaulting to ``sys.stdin`` if the list is empty. If a filename is ``'-'``, " +"it is also replaced by ``sys.stdin``. To specify an alternative list of " +"filenames, pass it as the first argument to :func:`.input`. A single file " +"name is also allowed." +msgstr "" + +#: ../Doc/library/fileinput.rst:29 +msgid "" +"All files are opened in text mode by default, but you can override this by " +"specifying the *mode* parameter in the call to :func:`.input` or :class:" +"`FileInput`. If an I/O error occurs during opening or reading a file, :exc:" +"`OSError` is raised." +msgstr "" + +#: ../Doc/library/fileinput.rst:34 +msgid ":exc:`IOError` used to be raised; it is now an alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/fileinput.rst:37 +msgid "" +"If ``sys.stdin`` is used more than once, the second and further use will " +"return no lines, except perhaps for interactive use, or if it has been " +"explicitly reset (e.g. using ``sys.stdin.seek(0)``)." +msgstr "" + +#: ../Doc/library/fileinput.rst:41 +msgid "" +"Empty files are opened and immediately closed; the only time their presence " +"in the list of filenames is noticeable at all is when the last file opened " +"is empty." +msgstr "" + +#: ../Doc/library/fileinput.rst:45 +msgid "" +"Lines are returned with any newlines intact, which means that the last line " +"in a file may not have one." +msgstr "" + +#: ../Doc/library/fileinput.rst:48 +msgid "" +"You can control how files are opened by providing an opening hook via the " +"*openhook* parameter to :func:`fileinput.input` or :class:`FileInput()`. The " +"hook must be a function that takes two arguments, *filename* and *mode*, and " +"returns an accordingly opened file-like object. Two useful hooks are already " +"provided by this module." +msgstr "" + +#: ../Doc/library/fileinput.rst:54 +msgid "The following function is the primary interface of this module:" +msgstr "" + +#: ../Doc/library/fileinput.rst:59 +msgid "" +"Create an instance of the :class:`FileInput` class. The instance will be " +"used as global state for the functions of this module, and is also returned " +"to use during iteration. The parameters to this function will be passed " +"along to the constructor of the :class:`FileInput` class." +msgstr "" + +#: ../Doc/library/fileinput.rst:64 +msgid "" +"The :class:`FileInput` instance can be used as a context manager in the :" +"keyword:`with` statement. In this example, *input* is closed after the :" +"keyword:`with` statement is exited, even if an exception occurs::" +msgstr "" + +#: ../Doc/library/fileinput.rst:72 ../Doc/library/fileinput.rst:163 +msgid "Can be used as a context manager." +msgstr "" + +#: ../Doc/library/fileinput.rst:76 ../Doc/library/fileinput.rst:170 +msgid "" +"Deprecated since version 3.6, will be removed in version 3.8: The bufsize " +"parameter." +msgstr "" + +#: ../Doc/library/fileinput.rst:76 ../Doc/library/fileinput.rst:170 +msgid "The *bufsize* parameter." +msgstr "" + +#: ../Doc/library/fileinput.rst:78 +msgid "" +"The following functions use the global state created by :func:`fileinput." +"input`; if there is no active state, :exc:`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/fileinput.rst:84 +msgid "" +"Return the name of the file currently being read. Before the first line has " +"been read, returns ``None``." +msgstr "" + +#: ../Doc/library/fileinput.rst:90 +msgid "" +"Return the integer \"file descriptor\" for the current file. When no file is " +"opened (before the first line and between files), returns ``-1``." +msgstr "" + +#: ../Doc/library/fileinput.rst:96 +msgid "" +"Return the cumulative line number of the line that has just been read. " +"Before the first line has been read, returns ``0``. After the last line of " +"the last file has been read, returns the line number of that line." +msgstr "" + +#: ../Doc/library/fileinput.rst:103 +msgid "" +"Return the line number in the current file. Before the first line has been " +"read, returns ``0``. After the last line of the last file has been read, " +"returns the line number of that line within the file." +msgstr "" + +#: ../Doc/library/fileinput.rst:110 +msgid "" +"Returns true if the line just read is the first line of its file, otherwise " +"returns false." +msgstr "" + +#: ../Doc/library/fileinput.rst:116 +msgid "" +"Returns true if the last line was read from ``sys.stdin``, otherwise returns " +"false." +msgstr "" + +#: ../Doc/library/fileinput.rst:122 +msgid "" +"Close the current file so that the next iteration will read the first line " +"from the next file (if any); lines not read from the file will not count " +"towards the cumulative line count. The filename is not changed until after " +"the first line of the next file has been read. Before the first line has " +"been read, this function has no effect; it cannot be used to skip the first " +"file. After the last line of the last file has been read, this function has " +"no effect." +msgstr "" + +#: ../Doc/library/fileinput.rst:132 +msgid "Close the sequence." +msgstr "" + +#: ../Doc/library/fileinput.rst:134 +msgid "" +"The class which implements the sequence behavior provided by the module is " +"available for subclassing as well:" +msgstr "" + +#: ../Doc/library/fileinput.rst:140 +msgid "" +"Class :class:`FileInput` is the implementation; its methods :meth:" +"`filename`, :meth:`fileno`, :meth:`lineno`, :meth:`filelineno`, :meth:" +"`isfirstline`, :meth:`isstdin`, :meth:`nextfile` and :meth:`close` " +"correspond to the functions of the same name in the module. In addition it " +"has a :meth:`~io.TextIOBase.readline` method which returns the next input " +"line, and a :meth:`__getitem__` method which implements the sequence " +"behavior. The sequence must be accessed in strictly sequential order; random " +"access and :meth:`~io.TextIOBase.readline` cannot be mixed." +msgstr "" + +#: ../Doc/library/fileinput.rst:149 +msgid "" +"With *mode* you can specify which file mode will be passed to :func:`open`. " +"It must be one of ``'r'``, ``'rU'``, ``'U'`` and ``'rb'``." +msgstr "" + +#: ../Doc/library/fileinput.rst:152 +msgid "" +"The *openhook*, when given, must be a function that takes two arguments, " +"*filename* and *mode*, and returns an accordingly opened file-like object. " +"You cannot use *inplace* and *openhook* together." +msgstr "" + +#: ../Doc/library/fileinput.rst:156 +msgid "" +"A :class:`FileInput` instance can be used as a context manager in the :" +"keyword:`with` statement. In this example, *input* is closed after the :" +"keyword:`with` statement is exited, even if an exception occurs::" +msgstr "" + +#: ../Doc/library/fileinput.rst:166 +msgid "The ``'rU'`` and ``'U'`` modes." +msgstr "" + +#: ../Doc/library/fileinput.rst:173 +msgid "" +"**Optional in-place filtering:** if the keyword argument ``inplace=True`` is " +"passed to :func:`fileinput.input` or to the :class:`FileInput` constructor, " +"the file is moved to a backup file and standard output is directed to the " +"input file (if a file of the same name as the backup file already exists, it " +"will be replaced silently). This makes it possible to write a filter that " +"rewrites its input file in place. If the *backup* parameter is given " +"(typically as ``backup='.'``), it specifies the extension " +"for the backup file, and the backup file remains around; by default, the " +"extension is ``'.bak'`` and it is deleted when the output file is closed. " +"In-place filtering is disabled when standard input is read." +msgstr "" + +#: ../Doc/library/fileinput.rst:185 +msgid "The two following opening hooks are provided by this module:" +msgstr "" + +#: ../Doc/library/fileinput.rst:189 +msgid "" +"Transparently opens files compressed with gzip and bzip2 (recognized by the " +"extensions ``'.gz'`` and ``'.bz2'``) using the :mod:`gzip` and :mod:`bz2` " +"modules. If the filename extension is not ``'.gz'`` or ``'.bz2'``, the file " +"is opened normally (ie, using :func:`open` without any decompression)." +msgstr "" + +#: ../Doc/library/fileinput.rst:194 +msgid "" +"Usage example: ``fi = fileinput.FileInput(openhook=fileinput." +"hook_compressed)``" +msgstr "" + +#: ../Doc/library/fileinput.rst:199 +msgid "" +"Returns a hook which opens each file with :func:`open`, using the given " +"*encoding* and *errors* to read the file." +msgstr "" + +#: ../Doc/library/fileinput.rst:202 +msgid "" +"Usage example: ``fi = fileinput.FileInput(openhook=fileinput." +"hook_encoded(\"utf-8\", \"surrogateescape\"))``" +msgstr "" + +#: ../Doc/library/fileinput.rst:206 +msgid "Added the optional *errors* parameter." +msgstr "" + +#: ../Doc/library/filesys.rst:5 +msgid "File and Directory Access" +msgstr "" + +#: ../Doc/library/filesys.rst:7 +msgid "" +"The modules described in this chapter deal with disk files and directories. " +"For example, there are modules for reading the properties of files, " +"manipulating paths in a portable way, and creating temporary files. The " +"full list of modules in this chapter is:" +msgstr "" + +#: ../Doc/library/filesys.rst:31 +msgid "" +"Operating system interfaces, including functions to work with files at a " +"lower level than Python :term:`file objects `." +msgstr "" + +#: ../Doc/library/filesys.rst:36 +msgid "Module :mod:`io`" +msgstr "" + +#: ../Doc/library/filesys.rst:35 +msgid "" +"Python's built-in I/O library, including both abstract classes and some " +"concrete classes such as file I/O." +msgstr "" + +#: ../Doc/library/filesys.rst:38 +msgid "Built-in function :func:`open`" +msgstr "" + +#: ../Doc/library/filesys.rst:39 +msgid "The standard way to open files for reading and writing with Python." +msgstr "" + +#: ../Doc/library/fnmatch.rst:2 +msgid ":mod:`fnmatch` --- Unix filename pattern matching" +msgstr "" + +#: ../Doc/library/fnmatch.rst:7 +msgid "**Source code:** :source:`Lib/fnmatch.py`" +msgstr "" + +#: ../Doc/library/fnmatch.rst:15 +msgid "" +"This module provides support for Unix shell-style wildcards, which are *not* " +"the same as regular expressions (which are documented in the :mod:`re` " +"module). The special characters used in shell-style wildcards are:" +msgstr "" + +#: ../Doc/library/fnmatch.rst:20 +msgid "Pattern" +msgstr "" + +#: ../Doc/library/fnmatch.rst:22 ../Doc/library/xml.etree.elementtree.rst:416 +msgid "``*``" +msgstr "" + +#: ../Doc/library/fnmatch.rst:22 +msgid "matches everything" +msgstr "" + +#: ../Doc/library/fnmatch.rst:24 ../Doc/library/struct.rst:196 +msgid "``?``" +msgstr "" + +#: ../Doc/library/fnmatch.rst:24 +msgid "matches any single character" +msgstr "" + +#: ../Doc/library/fnmatch.rst:26 +msgid "``[seq]``" +msgstr "" + +#: ../Doc/library/fnmatch.rst:26 +msgid "matches any character in *seq*" +msgstr "" + +#: ../Doc/library/fnmatch.rst:28 +msgid "``[!seq]``" +msgstr "" + +#: ../Doc/library/fnmatch.rst:28 +msgid "matches any character not in *seq*" +msgstr "" + +#: ../Doc/library/fnmatch.rst:31 ../Doc/library/glob.rst:23 +msgid "" +"For a literal match, wrap the meta-characters in brackets. For example, " +"``'[?]'`` matches the character ``'?'``." +msgstr "" + +#: ../Doc/library/fnmatch.rst:36 +msgid "" +"Note that the filename separator (``'/'`` on Unix) is *not* special to this " +"module. See module :mod:`glob` for pathname expansion (:mod:`glob` uses :" +"func:`fnmatch` to match pathname segments). Similarly, filenames starting " +"with a period are not special for this module, and are matched by the ``*`` " +"and ``?`` patterns." +msgstr "" + +#: ../Doc/library/fnmatch.rst:45 +msgid "" +"Test whether the *filename* string matches the *pattern* string, returning :" +"const:`True` or :const:`False`. If the operating system is case-" +"insensitive, then both parameters will be normalized to all lower- or upper-" +"case before the comparison is performed. :func:`fnmatchcase` can be used to " +"perform a case-sensitive comparison, regardless of whether that's standard " +"for the operating system." +msgstr "" + +#: ../Doc/library/fnmatch.rst:52 +msgid "" +"This example will print all file names in the current directory with the " +"extension ``.txt``::" +msgstr "" + +#: ../Doc/library/fnmatch.rst:65 +msgid "" +"Test whether *filename* matches *pattern*, returning :const:`True` or :const:" +"`False`; the comparison is case-sensitive." +msgstr "" + +#: ../Doc/library/fnmatch.rst:71 +msgid "" +"Return the subset of the list of *names* that match *pattern*. It is the " +"same as ``[n for n in names if fnmatch(n, pattern)]``, but implemented more " +"efficiently." +msgstr "" + +#: ../Doc/library/fnmatch.rst:77 +msgid "Return the shell-style *pattern* converted to a regular expression." +msgstr "" + +#: ../Doc/library/fnmatch.rst:93 +msgid "Module :mod:`glob`" +msgstr "" + +#: ../Doc/library/fnmatch.rst:94 +msgid "Unix shell-style path expansion." +msgstr "" + +#: ../Doc/library/formatter.rst:2 +msgid ":mod:`formatter` --- Generic output formatting" +msgstr "" + +#: ../Doc/library/formatter.rst:8 +msgid "Due to lack of usage, the formatter module has been deprecated." +msgstr "" + +#: ../Doc/library/formatter.rst:13 +msgid "" +"This module supports two interface definitions, each with multiple " +"implementations: The *formatter* interface, and the *writer* interface which " +"is required by the formatter interface." +msgstr "" + +#: ../Doc/library/formatter.rst:17 +msgid "" +"Formatter objects transform an abstract flow of formatting events into " +"specific output events on writer objects. Formatters manage several stack " +"structures to allow various properties of a writer object to be changed and " +"restored; writers need not be able to handle relative changes nor any sort " +"of \"change back\" operation. Specific writer properties which may be " +"controlled via formatter objects are horizontal alignment, font, and left " +"margin indentations. A mechanism is provided which supports providing " +"arbitrary, non-exclusive style settings to a writer as well. Additional " +"interfaces facilitate formatting events which are not reversible, such as " +"paragraph separation." +msgstr "" + +#: ../Doc/library/formatter.rst:27 +msgid "" +"Writer objects encapsulate device interfaces. Abstract devices, such as " +"file formats, are supported as well as physical devices. The provided " +"implementations all work with abstract devices. The interface makes " +"available mechanisms for setting the properties which formatter objects " +"manage and inserting data into the output." +msgstr "" + +#: ../Doc/library/formatter.rst:37 +msgid "The Formatter Interface" +msgstr "" + +#: ../Doc/library/formatter.rst:39 +msgid "" +"Interfaces to create formatters are dependent on the specific formatter " +"class being instantiated. The interfaces described below are the required " +"interfaces which all formatters must support once initialized." +msgstr "" + +#: ../Doc/library/formatter.rst:43 +msgid "One data element is defined at the module level:" +msgstr "" + +#: ../Doc/library/formatter.rst:48 +msgid "" +"Value which can be used in the font specification passed to the " +"``push_font()`` method described below, or as the new value to any other " +"``push_property()`` method. Pushing the ``AS_IS`` value allows the " +"corresponding ``pop_property()`` method to be called without having to track " +"whether the property was changed." +msgstr "" + +#: ../Doc/library/formatter.rst:53 +msgid "The following attributes are defined for formatter instance objects:" +msgstr "" + +#: ../Doc/library/formatter.rst:58 +msgid "The writer instance with which the formatter interacts." +msgstr "" + +#: ../Doc/library/formatter.rst:63 +msgid "" +"Close any open paragraphs and insert at least *blanklines* before the next " +"paragraph." +msgstr "" + +#: ../Doc/library/formatter.rst:69 +msgid "" +"Add a hard line break if one does not already exist. This does not break " +"the logical paragraph." +msgstr "" + +#: ../Doc/library/formatter.rst:75 +msgid "" +"Insert a horizontal rule in the output. A hard break is inserted if there " +"is data in the current paragraph, but the logical paragraph is not broken. " +"The arguments and keywords are passed on to the writer's :meth:" +"`send_line_break` method." +msgstr "" + +#: ../Doc/library/formatter.rst:83 +msgid "" +"Provide data which should be formatted with collapsed whitespace. Whitespace " +"from preceding and successive calls to :meth:`add_flowing_data` is " +"considered as well when the whitespace collapse is performed. The data " +"which is passed to this method is expected to be word-wrapped by the output " +"device. Note that any word-wrapping still must be performed by the writer " +"object due to the need to rely on device and font information." +msgstr "" + +#: ../Doc/library/formatter.rst:93 +msgid "" +"Provide data which should be passed to the writer unchanged. Whitespace, " +"including newline and tab characters, are considered legal in the value of " +"*data*." +msgstr "" + +#: ../Doc/library/formatter.rst:100 +msgid "" +"Insert a label which should be placed to the left of the current left " +"margin. This should be used for constructing bulleted or numbered lists. If " +"the *format* value is a string, it is interpreted as a format specification " +"for *counter*, which should be an integer. The result of this formatting " +"becomes the value of the label; if *format* is not a string it is used as " +"the label value directly. The label value is passed as the only argument to " +"the writer's :meth:`send_label_data` method. Interpretation of non-string " +"label values is dependent on the associated writer." +msgstr "" + +#: ../Doc/library/formatter.rst:109 +msgid "" +"Format specifications are strings which, in combination with a counter " +"value, are used to compute label values. Each character in the format " +"string is copied to the label value, with some characters recognized to " +"indicate a transform on the counter value. Specifically, the character " +"``'1'`` represents the counter value formatter as an Arabic number, the " +"characters ``'A'`` and ``'a'`` represent alphabetic representations of the " +"counter value in upper and lower case, respectively, and ``'I'`` and ``'i'`` " +"represent the counter value in Roman numerals, in upper and lower case. " +"Note that the alphabetic and roman transforms require that the counter value " +"be greater than zero." +msgstr "" + +#: ../Doc/library/formatter.rst:122 +msgid "" +"Send any pending whitespace buffered from a previous call to :meth:" +"`add_flowing_data` to the associated writer object. This should be called " +"before any direct manipulation of the writer object." +msgstr "" + +#: ../Doc/library/formatter.rst:129 +msgid "" +"Push a new alignment setting onto the alignment stack. This may be :const:" +"`AS_IS` if no change is desired. If the alignment value is changed from the " +"previous setting, the writer's :meth:`new_alignment` method is called with " +"the *align* value." +msgstr "" + +#: ../Doc/library/formatter.rst:137 +msgid "Restore the previous alignment." +msgstr "" + +#: ../Doc/library/formatter.rst:142 +msgid "" +"Change some or all font properties of the writer object. Properties which " +"are not set to :const:`AS_IS` are set to the values passed in while others " +"are maintained at their current settings. The writer's :meth:`new_font` " +"method is called with the fully resolved font specification." +msgstr "" + +#: ../Doc/library/formatter.rst:150 +msgid "Restore the previous font." +msgstr "" + +#: ../Doc/library/formatter.rst:155 +msgid "" +"Increase the number of left margin indentations by one, associating the " +"logical tag *margin* with the new indentation. The initial margin level is " +"``0``. Changed values of the logical tag must be true values; false values " +"other than :const:`AS_IS` are not sufficient to change the margin." +msgstr "" + +#: ../Doc/library/formatter.rst:163 +msgid "Restore the previous margin." +msgstr "" + +#: ../Doc/library/formatter.rst:168 +msgid "" +"Push any number of arbitrary style specifications. All styles are pushed " +"onto the styles stack in order. A tuple representing the entire stack, " +"including :const:`AS_IS` values, is passed to the writer's :meth:" +"`new_styles` method." +msgstr "" + +#: ../Doc/library/formatter.rst:175 +msgid "" +"Pop the last *n* style specifications passed to :meth:`push_style`. A tuple " +"representing the revised stack, including :const:`AS_IS` values, is passed " +"to the writer's :meth:`new_styles` method." +msgstr "" + +#: ../Doc/library/formatter.rst:182 +msgid "Set the spacing style for the writer." +msgstr "" + +#: ../Doc/library/formatter.rst:187 +msgid "" +"Inform the formatter that data has been added to the current paragraph out-" +"of-band. This should be used when the writer has been manipulated " +"directly. The optional *flag* argument can be set to false if the writer " +"manipulations produced a hard line break at the end of the output." +msgstr "" + +#: ../Doc/library/formatter.rst:196 +msgid "Formatter Implementations" +msgstr "" + +#: ../Doc/library/formatter.rst:198 +msgid "" +"Two implementations of formatter objects are provided by this module. Most " +"applications may use one of these classes without modification or " +"subclassing." +msgstr "" + +#: ../Doc/library/formatter.rst:204 +msgid "" +"A formatter which does nothing. If *writer* is omitted, a :class:" +"`NullWriter` instance is created. No methods of the writer are called by :" +"class:`NullFormatter` instances. Implementations should inherit from this " +"class if implementing a writer interface but don't need to inherit any " +"implementation." +msgstr "" + +#: ../Doc/library/formatter.rst:213 +msgid "" +"The standard formatter. This implementation has demonstrated wide " +"applicability to many writers, and may be used directly in most " +"circumstances. It has been used to implement a full-featured World Wide Web " +"browser." +msgstr "" + +#: ../Doc/library/formatter.rst:221 +msgid "The Writer Interface" +msgstr "" + +#: ../Doc/library/formatter.rst:223 +msgid "" +"Interfaces to create writers are dependent on the specific writer class " +"being instantiated. The interfaces described below are the required " +"interfaces which all writers must support once initialized. Note that while " +"most applications can use the :class:`AbstractFormatter` class as a " +"formatter, the writer must typically be provided by the application." +msgstr "" + +#: ../Doc/library/formatter.rst:232 +msgid "Flush any buffered output or device control events." +msgstr "" + +#: ../Doc/library/formatter.rst:237 +msgid "" +"Set the alignment style. The *align* value can be any object, but by " +"convention is a string or ``None``, where ``None`` indicates that the " +"writer's \"preferred\" alignment should be used. Conventional *align* values " +"are ``'left'``, ``'center'``, ``'right'``, and ``'justify'``." +msgstr "" + +#: ../Doc/library/formatter.rst:245 +msgid "" +"Set the font style. The value of *font* will be ``None``, indicating that " +"the device's default font should be used, or a tuple of the form ``(size, " +"italic, bold, teletype)``. Size will be a string indicating the size of " +"font that should be used; specific strings and their interpretation must be " +"defined by the application. The *italic*, *bold*, and *teletype* values are " +"Boolean values specifying which of those font attributes should be used." +msgstr "" + +#: ../Doc/library/formatter.rst:255 +msgid "" +"Set the margin level to the integer *level* and the logical tag to *margin*. " +"Interpretation of the logical tag is at the writer's discretion; the only " +"restriction on the value of the logical tag is that it not be a false value " +"for non-zero values of *level*." +msgstr "" + +#: ../Doc/library/formatter.rst:263 +msgid "Set the spacing style to *spacing*." +msgstr "" + +#: ../Doc/library/formatter.rst:268 +msgid "" +"Set additional styles. The *styles* value is a tuple of arbitrary values; " +"the value :const:`AS_IS` should be ignored. The *styles* tuple may be " +"interpreted either as a set or as a stack depending on the requirements of " +"the application and writer implementation." +msgstr "" + +#: ../Doc/library/formatter.rst:276 +msgid "Break the current line." +msgstr "" + +#: ../Doc/library/formatter.rst:281 +msgid "" +"Produce a paragraph separation of at least *blankline* blank lines, or the " +"equivalent. The *blankline* value will be an integer. Note that the " +"implementation will receive a call to :meth:`send_line_break` before this " +"call if a line break is needed; this method should not include ending the " +"last line of the paragraph. It is only responsible for vertical spacing " +"between paragraphs." +msgstr "" + +#: ../Doc/library/formatter.rst:291 +msgid "" +"Display a horizontal rule on the output device. The arguments to this " +"method are entirely application- and writer-specific, and should be " +"interpreted with care. The method implementation may assume that a line " +"break has already been issued via :meth:`send_line_break`." +msgstr "" + +#: ../Doc/library/formatter.rst:299 +msgid "" +"Output character data which may be word-wrapped and re-flowed as needed. " +"Within any sequence of calls to this method, the writer may assume that " +"spans of multiple whitespace characters have been collapsed to single space " +"characters." +msgstr "" + +#: ../Doc/library/formatter.rst:306 +msgid "" +"Output character data which has already been formatted for display. " +"Generally, this should be interpreted to mean that line breaks indicated by " +"newline characters should be preserved and no new line breaks should be " +"introduced. The data may contain embedded newline and tab characters, " +"unlike data provided to the :meth:`send_formatted_data` interface." +msgstr "" + +#: ../Doc/library/formatter.rst:315 +msgid "" +"Set *data* to the left of the current left margin, if possible. The value of " +"*data* is not restricted; treatment of non-string values is entirely " +"application- and writer-dependent. This method will only be called at the " +"beginning of a line." +msgstr "" + +#: ../Doc/library/formatter.rst:324 +msgid "Writer Implementations" +msgstr "" + +#: ../Doc/library/formatter.rst:326 +msgid "" +"Three implementations of the writer object interface are provided as " +"examples by this module. Most applications will need to derive new writer " +"classes from the :class:`NullWriter` class." +msgstr "" + +#: ../Doc/library/formatter.rst:333 +msgid "" +"A writer which only provides the interface definition; no actions are taken " +"on any methods. This should be the base class for all writers which do not " +"need to inherit any implementation methods." +msgstr "" + +#: ../Doc/library/formatter.rst:340 +msgid "" +"A writer which can be used in debugging formatters, but not much else. Each " +"method simply announces itself by printing its name and arguments on " +"standard output." +msgstr "" + +#: ../Doc/library/formatter.rst:347 +msgid "" +"Simple writer class which writes output on the :term:`file object` passed in " +"as *file* or, if *file* is omitted, on standard output. The output is " +"simply word-wrapped to the number of columns specified by *maxcol*. This " +"class is suitable for reflowing a sequence of paragraphs." +msgstr "" + +#: ../Doc/library/fpectl.rst:2 +msgid ":mod:`fpectl` --- Floating point exception control" +msgstr "" + +#: ../Doc/library/fpectl.rst:13 +msgid "" +"The :mod:`fpectl` module is not built by default, and its usage is " +"discouraged and may be dangerous except in the hands of experts. See also " +"the section :ref:`fpectl-limitations` on limitations for more details." +msgstr "" + +#: ../Doc/library/fpectl.rst:21 +msgid "" +"Most computers carry out floating point operations in conformance with the " +"so-called IEEE-754 standard. On any real computer, some floating point " +"operations produce results that cannot be expressed as a normal floating " +"point value. For example, try ::" +msgstr "" + +#: ../Doc/library/fpectl.rst:32 +msgid "" +"(The example above will work on many platforms. DEC Alpha may be one " +"exception.) \"Inf\" is a special, non-numeric value in IEEE-754 that stands " +"for \"infinity\", and \"nan\" means \"not a number.\" Note that, other than " +"the non-numeric results, nothing special happened when you asked Python to " +"carry out those calculations. That is in fact the default behaviour " +"prescribed in the IEEE-754 standard, and if it works for you, stop reading " +"now." +msgstr "" + +#: ../Doc/library/fpectl.rst:39 +msgid "" +"In some circumstances, it would be better to raise an exception and stop " +"processing at the point where the faulty operation was attempted. The :mod:" +"`fpectl` module is for use in that situation. It provides control over " +"floating point units from several hardware manufacturers, allowing the user " +"to turn on the generation of :const:`SIGFPE` whenever any of the IEEE-754 " +"exceptions Division by Zero, Overflow, or Invalid Operation occurs. In " +"tandem with a pair of wrapper macros that are inserted into the C code " +"comprising your python system, :const:`SIGFPE` is trapped and converted into " +"the Python :exc:`FloatingPointError` exception." +msgstr "" + +#: ../Doc/library/fpectl.rst:49 +msgid "" +"The :mod:`fpectl` module defines the following functions and may raise the " +"given exception:" +msgstr "" + +#: ../Doc/library/fpectl.rst:55 +msgid "" +"Turn on the generation of :const:`SIGFPE`, and set up an appropriate signal " +"handler." +msgstr "" + +#: ../Doc/library/fpectl.rst:61 +msgid "Reset default handling of floating point exceptions." +msgstr "" + +#: ../Doc/library/fpectl.rst:66 +msgid "" +"After :func:`turnon_sigfpe` has been executed, a floating point operation " +"that raises one of the IEEE-754 exceptions Division by Zero, Overflow, or " +"Invalid operation will in turn raise this standard Python exception." +msgstr "" + +#: ../Doc/library/fpectl.rst:76 +msgid "" +"The following example demonstrates how to start up and test operation of " +"the :mod:`fpectl` module. ::" +msgstr "" + +#: ../Doc/library/fpectl.rst:99 +msgid "Limitations and other considerations" +msgstr "" + +#: ../Doc/library/fpectl.rst:101 +msgid "" +"Setting up a given processor to trap IEEE-754 floating point errors " +"currently requires custom code on a per-architecture basis. You may have to " +"modify :mod:`fpectl` to control your particular hardware." +msgstr "" + +#: ../Doc/library/fpectl.rst:105 +msgid "" +"Conversion of an IEEE-754 exception to a Python exception requires that the " +"wrapper macros ``PyFPE_START_PROTECT`` and ``PyFPE_END_PROTECT`` be inserted " +"into your code in an appropriate fashion. Python itself has been modified " +"to support the :mod:`fpectl` module, but many other codes of interest to " +"numerical analysts have not." +msgstr "" + +#: ../Doc/library/fpectl.rst:111 +msgid "The :mod:`fpectl` module is not thread-safe." +msgstr "" + +#: ../Doc/library/fpectl.rst:116 +msgid "" +"Some files in the source distribution may be interesting in learning more " +"about how this module operates. The include file :file:`Include/pyfpe.h` " +"discusses the implementation of this module at some length. :file:`Modules/" +"fpetestmodule.c` gives several examples of use. Many additional examples can " +"be found in :file:`Objects/floatobject.c`." +msgstr "" + +#: ../Doc/library/fractions.rst:2 +msgid ":mod:`fractions` --- Rational numbers" +msgstr "" + +#: ../Doc/library/fractions.rst:10 +msgid "**Source code:** :source:`Lib/fractions.py`" +msgstr "" + +#: ../Doc/library/fractions.rst:14 +msgid "" +"The :mod:`fractions` module provides support for rational number arithmetic." +msgstr "" + +#: ../Doc/library/fractions.rst:17 +msgid "" +"A Fraction instance can be constructed from a pair of integers, from another " +"rational number, or from a string." +msgstr "" + +#: ../Doc/library/fractions.rst:26 +msgid "" +"The first version requires that *numerator* and *denominator* are instances " +"of :class:`numbers.Rational` and returns a new :class:`Fraction` instance " +"with value ``numerator/denominator``. If *denominator* is :const:`0`, it " +"raises a :exc:`ZeroDivisionError`. The second version requires that " +"*other_fraction* is an instance of :class:`numbers.Rational` and returns a :" +"class:`Fraction` instance with the same value. The next two versions accept " +"either a :class:`float` or a :class:`decimal.Decimal` instance, and return " +"a :class:`Fraction` instance with exactly the same value. Note that due to " +"the usual issues with binary floating-point (see :ref:`tut-fp-issues`), the " +"argument to ``Fraction(1.1)`` is not exactly equal to 11/10, and so " +"``Fraction(1.1)`` does *not* return ``Fraction(11, 10)`` as one might " +"expect. (But see the documentation for the :meth:`limit_denominator` method " +"below.) The last version of the constructor expects a string or unicode " +"instance. The usual form for this instance is::" +msgstr "" + +#: ../Doc/library/fractions.rst:43 +msgid "" +"where the optional ``sign`` may be either '+' or '-' and ``numerator`` and " +"``denominator`` (if present) are strings of decimal digits. In addition, " +"any string that represents a finite value and is accepted by the :class:" +"`float` constructor is also accepted by the :class:`Fraction` constructor. " +"In either form the input string may also have leading and/or trailing " +"whitespace. Here are some examples::" +msgstr "" + +#: ../Doc/library/fractions.rst:77 +msgid "" +"The :class:`Fraction` class inherits from the abstract base class :class:" +"`numbers.Rational`, and implements all of the methods and operations from " +"that class. :class:`Fraction` instances are hashable, and should be treated " +"as immutable. In addition, :class:`Fraction` has the following properties " +"and methods:" +msgstr "" + +#: ../Doc/library/fractions.rst:83 +msgid "" +"The :class:`Fraction` constructor now accepts :class:`float` and :class:" +"`decimal.Decimal` instances." +msgstr "" + +#: ../Doc/library/fractions.rst:90 +msgid "Numerator of the Fraction in lowest term." +msgstr "" + +#: ../Doc/library/fractions.rst:94 +msgid "Denominator of the Fraction in lowest term." +msgstr "" + +#: ../Doc/library/fractions.rst:99 +msgid "" +"This class method constructs a :class:`Fraction` representing the exact " +"value of *flt*, which must be a :class:`float`. Beware that ``Fraction." +"from_float(0.3)`` is not the same value as ``Fraction(3, 10)``." +msgstr "" + +#: ../Doc/library/fractions.rst:105 +msgid "" +"From Python 3.2 onwards, you can also construct a :class:`Fraction` instance " +"directly from a :class:`float`." +msgstr "" + +#: ../Doc/library/fractions.rst:111 +msgid "" +"This class method constructs a :class:`Fraction` representing the exact " +"value of *dec*, which must be a :class:`decimal.Decimal` instance." +msgstr "" + +#: ../Doc/library/fractions.rst:116 +msgid "" +"From Python 3.2 onwards, you can also construct a :class:`Fraction` instance " +"directly from a :class:`decimal.Decimal` instance." +msgstr "" + +#: ../Doc/library/fractions.rst:123 +msgid "" +"Finds and returns the closest :class:`Fraction` to ``self`` that has " +"denominator at most max_denominator. This method is useful for finding " +"rational approximations to a given floating-point number:" +msgstr "" + +#: ../Doc/library/fractions.rst:131 +msgid "or for recovering a rational number that's represented as a float:" +msgstr "" + +#: ../Doc/library/fractions.rst:144 +msgid "" +"Returns the greatest :class:`int` ``<= self``. This method can also be " +"accessed through the :func:`math.floor` function:" +msgstr "" + +#: ../Doc/library/fractions.rst:154 +msgid "" +"Returns the least :class:`int` ``>= self``. This method can also be " +"accessed through the :func:`math.ceil` function." +msgstr "" + +#: ../Doc/library/fractions.rst:161 +msgid "" +"The first version returns the nearest :class:`int` to ``self``, rounding " +"half to even. The second version rounds ``self`` to the nearest multiple of " +"``Fraction(1, 10**ndigits)`` (logically, if ``ndigits`` is negative), again " +"rounding half toward even. This method can also be accessed through the :" +"func:`round` function." +msgstr "" + +#: ../Doc/library/fractions.rst:170 +msgid "" +"Return the greatest common divisor of the integers *a* and *b*. If either " +"*a* or *b* is nonzero, then the absolute value of ``gcd(a, b)`` is the " +"largest integer that divides both *a* and *b*. ``gcd(a,b)`` has the same " +"sign as *b* if *b* is nonzero; otherwise it takes the sign of *a*. ``gcd(0, " +"0)`` returns ``0``." +msgstr "" + +#: ../Doc/library/fractions.rst:176 +msgid "Use :func:`math.gcd` instead." +msgstr "" + +#: ../Doc/library/fractions.rst:182 +msgid "Module :mod:`numbers`" +msgstr "" + +#: ../Doc/library/fractions.rst:183 +msgid "The abstract base classes making up the numeric tower." +msgstr "" + +#: ../Doc/library/frameworks.rst:5 +msgid "Program Frameworks" +msgstr "" + +#: ../Doc/library/frameworks.rst:7 +msgid "" +"The modules described in this chapter are frameworks that will largely " +"dictate the structure of your program. Currently the modules described " +"here are all oriented toward writing command-line interfaces." +msgstr "" + +#: ../Doc/library/ftplib.rst:2 +msgid ":mod:`ftplib` --- FTP protocol client" +msgstr "" + +#: ../Doc/library/ftplib.rst:7 +msgid "**Source code:** :source:`Lib/ftplib.py`" +msgstr "" + +#: ../Doc/library/ftplib.rst:15 +msgid "" +"This module defines the class :class:`FTP` and a few related items. The :" +"class:`FTP` class implements the client side of the FTP protocol. You can " +"use this to write Python programs that perform a variety of automated FTP " +"jobs, such as mirroring other FTP servers. It is also used by the module :" +"mod:`urllib.request` to handle URLs that use FTP. For more information on " +"FTP (File Transfer Protocol), see Internet :rfc:`959`." +msgstr "" + +#: ../Doc/library/ftplib.rst:22 +msgid "Here's a sample session using the :mod:`ftplib` module::" +msgstr "" + +#: ../Doc/library/ftplib.rst:41 ../Doc/library/gzip.rst:26 +#: ../Doc/library/zipfile.rst:26 +msgid "The module defines the following items:" +msgstr "" + +#: ../Doc/library/ftplib.rst:45 +msgid "" +"Return a new instance of the :class:`FTP` class. When *host* is given, the " +"method call ``connect(host)`` is made. When *user* is given, additionally " +"the method call ``login(user, passwd, acct)`` is made (where *passwd* and " +"*acct* default to the empty string when not given). The optional *timeout* " +"parameter specifies a timeout in seconds for blocking operations like the " +"connection attempt (if is not specified, the global default timeout setting " +"will be used). *source_address* is a 2-tuple ``(host, port)`` for the socket " +"to bind to as its source address before connecting." +msgstr "" + +#: ../Doc/library/ftplib.rst:54 +msgid "The :class:`FTP` class supports the :keyword:`with` statement, e.g.:" +msgstr "" + +#: ../Doc/library/ftplib.rst:71 ../Doc/library/ftplib.rst:92 +#: ../Doc/library/ftplib.rst:193 +msgid "*source_address* parameter was added." +msgstr "" + +#: ../Doc/library/ftplib.rst:77 +msgid "" +"A :class:`FTP` subclass which adds TLS support to FTP as described in :rfc:" +"`4217`. Connect as usual to port 21 implicitly securing the FTP control " +"connection before authenticating. Securing the data connection requires the " +"user to explicitly ask for it by calling the :meth:`prot_p` method. " +"*context* is a :class:`ssl.SSLContext` object which allows bundling SSL " +"configuration options, certificates and private keys into a single " +"(potentially long-lived) structure. Please read :ref:`ssl-security` for " +"best practices." +msgstr "" + +#: ../Doc/library/ftplib.rst:86 +msgid "" +"*keyfile* and *certfile* are a legacy alternative to *context* -- they can " +"point to PEM-formatted private key and certificate chain files " +"(respectively) for the SSL connection." +msgstr "" + +#: ../Doc/library/ftplib.rst:95 ../Doc/library/imaplib.rst:101 +#: ../Doc/library/nntplib.rst:105 ../Doc/library/poplib.rst:60 +#: ../Doc/library/smtplib.rst:93 +msgid "" +"The class now supports hostname check with :attr:`ssl.SSLContext." +"check_hostname` and *Server Name Indication* (see :data:`ssl.HAS_SNI`)." +msgstr "" + +#: ../Doc/library/ftplib.rst:102 ../Doc/library/poplib.rst:67 +#: ../Doc/library/smtplib.rst:100 +msgid "" +"*keyfile* and *certfile* are deprecated in favor of *context*. Please use :" +"meth:`ssl.SSLContext.load_cert_chain` instead, or let :func:`ssl." +"create_default_context` select the system's trusted CA certificates for you." +msgstr "" + +#: ../Doc/library/ftplib.rst:107 +msgid "Here's a sample session using the :class:`FTP_TLS` class::" +msgstr "" + +#: ../Doc/library/ftplib.rst:120 ../Doc/library/nntplib.rst:123 +msgid "Exception raised when an unexpected reply is received from the server." +msgstr "" + +#: ../Doc/library/ftplib.rst:125 +msgid "" +"Exception raised when an error code signifying a temporary error (response " +"codes in the range 400--499) is received." +msgstr "" + +#: ../Doc/library/ftplib.rst:131 +msgid "" +"Exception raised when an error code signifying a permanent error (response " +"codes in the range 500--599) is received." +msgstr "" + +#: ../Doc/library/ftplib.rst:137 +msgid "" +"Exception raised when a reply is received from the server that does not fit " +"the response specifications of the File Transfer Protocol, i.e. begin with a " +"digit in the range 1--5." +msgstr "" + +#: ../Doc/library/ftplib.rst:144 +msgid "" +"The set of all exceptions (as a tuple) that methods of :class:`FTP` " +"instances may raise as a result of problems with the FTP connection (as " +"opposed to programming errors made by the caller). This set includes the " +"four exceptions listed above as well as :exc:`OSError`." +msgstr "" + +#: ../Doc/library/ftplib.rst:154 +msgid "Module :mod:`netrc`" +msgstr "" + +#: ../Doc/library/ftplib.rst:153 +msgid "" +"Parser for the :file:`.netrc` file format. The file :file:`.netrc` is " +"typically used by FTP clients to load user authentication information before " +"prompting the user." +msgstr "" + +#: ../Doc/library/ftplib.rst:161 +msgid "FTP Objects" +msgstr "" + +#: ../Doc/library/ftplib.rst:163 +msgid "" +"Several methods are available in two flavors: one for handling text files " +"and another for binary files. These are named for the command which is used " +"followed by ``lines`` for the text version or ``binary`` for the binary " +"version." +msgstr "" + +#: ../Doc/library/ftplib.rst:167 +msgid ":class:`FTP` instances have the following methods:" +msgstr "" + +#: ../Doc/library/ftplib.rst:172 ../Doc/library/poplib.rst:106 +msgid "" +"Set the instance's debugging level. This controls the amount of debugging " +"output printed. The default, ``0``, produces no debugging output. A value " +"of ``1`` produces a moderate amount of debugging output, generally a single " +"line per request. A value of ``2`` or higher produces the maximum amount of " +"debugging output, logging each line sent and received on the control " +"connection." +msgstr "" + +#: ../Doc/library/ftplib.rst:181 +msgid "" +"Connect to the given host and port. The default port number is ``21``, as " +"specified by the FTP protocol specification. It is rarely needed to specify " +"a different port number. This function should be called only once for each " +"instance; it should not be called at all if a host was given when the " +"instance was created. All other methods can only be used after a connection " +"has been made. The optional *timeout* parameter specifies a timeout in " +"seconds for the connection attempt. If no *timeout* is passed, the global " +"default timeout setting will be used. *source_address* is a 2-tuple ``(host, " +"port)`` for the socket to bind to as its source address before connecting." +msgstr "" + +#: ../Doc/library/ftplib.rst:199 ../Doc/library/nntplib.rst:201 +msgid "" +"Return the welcome message sent by the server in reply to the initial " +"connection. (This message sometimes contains disclaimers or help " +"information that may be relevant to the user.)" +msgstr "" + +#: ../Doc/library/ftplib.rst:206 +msgid "" +"Log in as the given *user*. The *passwd* and *acct* parameters are optional " +"and default to the empty string. If no *user* is specified, it defaults to " +"``'anonymous'``. If *user* is ``'anonymous'``, the default *passwd* is " +"``'anonymous@'``. This function should be called only once for each " +"instance, after a connection has been established; it should not be called " +"at all if a host and user were given when the instance was created. Most " +"FTP commands are only allowed after the client has logged in. The *acct* " +"parameter supplies \"accounting information\"; few systems implement this." +msgstr "" + +#: ../Doc/library/ftplib.rst:218 +msgid "" +"Abort a file transfer that is in progress. Using this does not always work, " +"but it's worth a try." +msgstr "" + +#: ../Doc/library/ftplib.rst:224 +msgid "" +"Send a simple command string to the server and return the response string." +msgstr "" + +#: ../Doc/library/ftplib.rst:229 +msgid "" +"Send a simple command string to the server and handle the response. Return " +"nothing if a response code corresponding to success (codes in the range " +"200--299) is received. Raise :exc:`error_reply` otherwise." +msgstr "" + +#: ../Doc/library/ftplib.rst:236 +msgid "" +"Retrieve a file in binary transfer mode. *cmd* should be an appropriate " +"``RETR`` command: ``'RETR filename'``. The *callback* function is called for " +"each block of data received, with a single string argument giving the data " +"block. The optional *blocksize* argument specifies the maximum chunk size to " +"read on the low-level socket object created to do the actual transfer (which " +"will also be the largest size of the data blocks passed to *callback*). A " +"reasonable default is chosen. *rest* means the same thing as in the :meth:" +"`transfercmd` method." +msgstr "" + +#: ../Doc/library/ftplib.rst:248 +msgid "" +"Retrieve a file or directory listing in ASCII transfer mode. *cmd* should " +"be an appropriate ``RETR`` command (see :meth:`retrbinary`) or a command " +"such as ``LIST`` or ``NLST`` (usually just the string ``'LIST'``). ``LIST`` " +"retrieves a list of files and information about those files. ``NLST`` " +"retrieves a list of file names. The *callback* function is called for each " +"line with a string argument containing the line with the trailing CRLF " +"stripped. The default *callback* prints the line to ``sys.stdout``." +msgstr "" + +#: ../Doc/library/ftplib.rst:260 +msgid "" +"Enable \"passive\" mode if *boolean* is true, other disable passive mode. " +"Passive mode is on by default." +msgstr "" + +#: ../Doc/library/ftplib.rst:266 +msgid "" +"Store a file in binary transfer mode. *cmd* should be an appropriate " +"``STOR`` command: ``\"STOR filename\"``. *fp* is a :term:`file object` " +"(opened in binary mode) which is read until EOF using its :meth:`~io.IOBase." +"read` method in blocks of size *blocksize* to provide the data to be stored. " +"The *blocksize* argument defaults to 8192. *callback* is an optional single " +"parameter callable that is called on each block of data after it is sent. " +"*rest* means the same thing as in the :meth:`transfercmd` method." +msgstr "" + +#: ../Doc/library/ftplib.rst:274 +msgid "*rest* parameter added." +msgstr "" + +#: ../Doc/library/ftplib.rst:280 +msgid "" +"Store a file in ASCII transfer mode. *cmd* should be an appropriate " +"``STOR`` command (see :meth:`storbinary`). Lines are read until EOF from " +"the :term:`file object` *fp* (opened in binary mode) using its :meth:`~io." +"IOBase.readline` method to provide the data to be stored. *callback* is an " +"optional single parameter callable that is called on each line after it is " +"sent." +msgstr "" + +#: ../Doc/library/ftplib.rst:289 +msgid "" +"Initiate a transfer over the data connection. If the transfer is active, " +"send an ``EPRT`` or ``PORT`` command and the transfer command specified by " +"*cmd*, and accept the connection. If the server is passive, send an " +"``EPSV`` or ``PASV`` command, connect to it, and start the transfer " +"command. Either way, return the socket for the connection." +msgstr "" + +#: ../Doc/library/ftplib.rst:295 +msgid "" +"If optional *rest* is given, a ``REST`` command is sent to the server, " +"passing *rest* as an argument. *rest* is usually a byte offset into the " +"requested file, telling the server to restart sending the file's bytes at " +"the requested offset, skipping over the initial bytes. Note however that " +"RFC 959 requires only that *rest* be a string containing characters in the " +"printable range from ASCII code 33 to ASCII code 126. The :meth:" +"`transfercmd` method, therefore, converts *rest* to a string, but no check " +"is performed on the string's contents. If the server does not recognize the " +"``REST`` command, an :exc:`error_reply` exception will be raised. If this " +"happens, simply call :meth:`transfercmd` without a *rest* argument." +msgstr "" + +#: ../Doc/library/ftplib.rst:309 +msgid "" +"Like :meth:`transfercmd`, but returns a tuple of the data connection and the " +"expected size of the data. If the expected size could not be computed, " +"``None`` will be returned as the expected size. *cmd* and *rest* means the " +"same thing as in :meth:`transfercmd`." +msgstr "" + +#: ../Doc/library/ftplib.rst:317 +msgid "" +"List a directory in a standardized format by using ``MLSD`` command (:rfc:" +"`3659`). If *path* is omitted the current directory is assumed. *facts* is " +"a list of strings representing the type of information desired (e.g. " +"``[\"type\", \"size\", \"perm\"]``). Return a generator object yielding a " +"tuple of two elements for every file found in path. First element is the " +"file name, the second one is a dictionary containing facts about the file " +"name. Content of this dictionary might be limited by the *facts* argument " +"but server is not guaranteed to return all requested facts." +msgstr "" + +#: ../Doc/library/ftplib.rst:331 +msgid "" +"Return a list of file names as returned by the ``NLST`` command. The " +"optional *argument* is a directory to list (default is the current server " +"directory). Multiple arguments can be used to pass non-standard options to " +"the ``NLST`` command." +msgstr "" + +#: ../Doc/library/ftplib.rst:336 ../Doc/library/ftplib.rst:348 +msgid "If your server supports the command, :meth:`mlsd` offers a better API." +msgstr "" + +#: ../Doc/library/ftplib.rst:341 +msgid "" +"Produce a directory listing as returned by the ``LIST`` command, printing it " +"to standard output. The optional *argument* is a directory to list (default " +"is the current server directory). Multiple arguments can be used to pass " +"non-standard options to the ``LIST`` command. If the last argument is a " +"function, it is used as a *callback* function as for :meth:`retrlines`; the " +"default prints to ``sys.stdout``. This method returns ``None``." +msgstr "" + +#: ../Doc/library/ftplib.rst:353 +msgid "Rename file *fromname* on the server to *toname*." +msgstr "" + +#: ../Doc/library/ftplib.rst:358 +msgid "" +"Remove the file named *filename* from the server. If successful, returns " +"the text of the response, otherwise raises :exc:`error_perm` on permission " +"errors or :exc:`error_reply` on other errors." +msgstr "" + +#: ../Doc/library/ftplib.rst:365 +msgid "Set the current directory on the server." +msgstr "" + +#: ../Doc/library/ftplib.rst:370 +msgid "Create a new directory on the server." +msgstr "" + +#: ../Doc/library/ftplib.rst:375 +msgid "Return the pathname of the current directory on the server." +msgstr "" + +#: ../Doc/library/ftplib.rst:380 +msgid "Remove the directory named *dirname* on the server." +msgstr "" + +#: ../Doc/library/ftplib.rst:385 +msgid "" +"Request the size of the file named *filename* on the server. On success, " +"the size of the file is returned as an integer, otherwise ``None`` is " +"returned. Note that the ``SIZE`` command is not standardized, but is " +"supported by many common server implementations." +msgstr "" + +#: ../Doc/library/ftplib.rst:393 +msgid "" +"Send a ``QUIT`` command to the server and close the connection. This is the " +"\"polite\" way to close a connection, but it may raise an exception if the " +"server responds with an error to the ``QUIT`` command. This implies a call " +"to the :meth:`close` method which renders the :class:`FTP` instance useless " +"for subsequent calls (see below)." +msgstr "" + +#: ../Doc/library/ftplib.rst:402 +msgid "" +"Close the connection unilaterally. This should not be applied to an already " +"closed connection such as after a successful call to :meth:`~FTP.quit`. " +"After this call the :class:`FTP` instance should not be used any more (after " +"a call to :meth:`close` or :meth:`~FTP.quit` you cannot reopen the " +"connection by issuing another :meth:`login` method)." +msgstr "" + +#: ../Doc/library/ftplib.rst:410 +msgid "FTP_TLS Objects" +msgstr "" + +#: ../Doc/library/ftplib.rst:412 +msgid "" +":class:`FTP_TLS` class inherits from :class:`FTP`, defining these additional " +"objects:" +msgstr "" + +#: ../Doc/library/ftplib.rst:416 +msgid "The SSL version to use (defaults to :attr:`ssl.PROTOCOL_SSLv23`)." +msgstr "" + +#: ../Doc/library/ftplib.rst:420 +msgid "" +"Set up a secure control connection by using TLS or SSL, depending on what is " +"specified in the :attr:`ssl_version` attribute." +msgstr "" + +#: ../Doc/library/ftplib.rst:423 ../Doc/library/imaplib.rst:487 +#: ../Doc/library/nntplib.rst:249 +msgid "" +"The method now supports hostname check with :attr:`ssl.SSLContext." +"check_hostname` and *Server Name Indication* (see :data:`ssl.HAS_SNI`)." +msgstr "" + +#: ../Doc/library/ftplib.rst:430 +msgid "" +"Revert control channel back to plaintext. This can be useful to take " +"advantage of firewalls that know how to handle NAT with non-secure FTP " +"without opening fixed ports." +msgstr "" + +#: ../Doc/library/ftplib.rst:438 +msgid "Set up secure data connection." +msgstr "" + +#: ../Doc/library/ftplib.rst:442 +msgid "Set up clear text data connection." +msgstr "" + +#: ../Doc/library/functional.rst:3 +msgid "Functional Programming Modules" +msgstr "" + +#: ../Doc/library/functional.rst:5 +msgid "" +"The modules described in this chapter provide functions and classes that " +"support a functional programming style, and general operations on callables." +msgstr "" + +#: ../Doc/library/functions.rst:5 ../Doc/library/functions.rst:11 +msgid "Built-in Functions" +msgstr "" + +#: ../Doc/library/functions.rst:7 +msgid "" +"The Python interpreter has a number of functions and types built into it " +"that are always available. They are listed here in alphabetical order." +msgstr "" + +#: ../Doc/library/functions.rst:13 ../Doc/library/stdtypes.rst:295 +msgid ":func:`abs`" +msgstr "" + +#: ../Doc/library/functions.rst:13 +msgid "|func-dict|_" +msgstr "" + +#: ../Doc/library/functions.rst:13 +msgid ":func:`help`" +msgstr "" + +#: ../Doc/library/functions.rst:13 +msgid ":func:`min`" +msgstr "" + +#: ../Doc/library/functions.rst:13 +msgid ":func:`setattr`" +msgstr "" + +#: ../Doc/library/functions.rst:14 +msgid ":func:`all`" +msgstr "" + +#: ../Doc/library/functions.rst:14 +msgid ":func:`dir`" +msgstr "" + +#: ../Doc/library/functions.rst:14 +msgid ":func:`hex`" +msgstr "" + +#: ../Doc/library/functions.rst:14 +msgid ":func:`next`" +msgstr "" + +#: ../Doc/library/functions.rst:14 +msgid ":func:`slice`" +msgstr "" + +#: ../Doc/library/functions.rst:15 +msgid ":func:`any`" +msgstr "" + +#: ../Doc/library/functions.rst:15 ../Doc/library/stdtypes.rst:309 +msgid ":func:`divmod`" +msgstr "" + +#: ../Doc/library/functions.rst:15 +msgid ":func:`id`" +msgstr "" + +#: ../Doc/library/functions.rst:15 +msgid ":func:`object`" +msgstr "" + +#: ../Doc/library/functions.rst:15 +msgid ":func:`sorted`" +msgstr "" + +#: ../Doc/library/functions.rst:16 +msgid ":func:`ascii`" +msgstr "" + +#: ../Doc/library/functions.rst:16 +msgid ":func:`enumerate`" +msgstr "" + +#: ../Doc/library/functions.rst:16 +msgid ":func:`input`" +msgstr "" + +#: ../Doc/library/functions.rst:16 +msgid ":func:`oct`" +msgstr "" + +#: ../Doc/library/functions.rst:16 +msgid ":func:`staticmethod`" +msgstr "" + +#: ../Doc/library/functions.rst:17 +msgid ":func:`bin`" +msgstr "" + +#: ../Doc/library/functions.rst:17 +msgid ":func:`eval`" +msgstr "" + +#: ../Doc/library/functions.rst:17 ../Doc/library/stdtypes.rst:298 +msgid ":func:`int`" +msgstr "" + +#: ../Doc/library/functions.rst:17 +msgid ":func:`open`" +msgstr "" + +#: ../Doc/library/functions.rst:17 +msgid "|func-str|_" +msgstr "" + +#: ../Doc/library/functions.rst:18 +msgid ":func:`bool`" +msgstr "" + +#: ../Doc/library/functions.rst:18 +msgid ":func:`exec`" +msgstr "" + +#: ../Doc/library/functions.rst:18 +msgid ":func:`isinstance`" +msgstr "" + +#: ../Doc/library/functions.rst:18 +msgid ":func:`ord`" +msgstr "" + +#: ../Doc/library/functions.rst:18 +msgid ":func:`sum`" +msgstr "" + +#: ../Doc/library/functions.rst:19 +msgid ":func:`bytearray`" +msgstr "" + +#: ../Doc/library/functions.rst:19 +msgid ":func:`filter`" +msgstr "" + +#: ../Doc/library/functions.rst:19 +msgid ":func:`issubclass`" +msgstr "" + +#: ../Doc/library/functions.rst:19 ../Doc/library/stdtypes.rst:311 +msgid ":func:`pow`" +msgstr "" + +#: ../Doc/library/functions.rst:19 +msgid ":func:`super`" +msgstr "" + +#: ../Doc/library/functions.rst:20 +msgid ":func:`bytes`" +msgstr "" + +#: ../Doc/library/functions.rst:20 ../Doc/library/stdtypes.rst:300 +msgid ":func:`float`" +msgstr "" + +#: ../Doc/library/functions.rst:20 +msgid ":func:`iter`" +msgstr "" + +#: ../Doc/library/functions.rst:20 +msgid ":func:`print`" +msgstr "" + +#: ../Doc/library/functions.rst:20 +msgid "|func-tuple|_" +msgstr "" + +#: ../Doc/library/functions.rst:21 +msgid ":func:`callable`" +msgstr "" + +#: ../Doc/library/functions.rst:21 +msgid ":func:`format`" +msgstr "" + +#: ../Doc/library/functions.rst:21 +msgid ":func:`len`" +msgstr "" + +#: ../Doc/library/functions.rst:21 +msgid ":func:`property`" +msgstr "" + +#: ../Doc/library/functions.rst:21 +msgid ":func:`type`" +msgstr "" + +#: ../Doc/library/functions.rst:22 +msgid ":func:`chr`" +msgstr "" + +#: ../Doc/library/functions.rst:22 +msgid "|func-frozenset|_" +msgstr "" + +#: ../Doc/library/functions.rst:22 +msgid "|func-list|_" +msgstr "" + +#: ../Doc/library/functions.rst:22 +msgid "|func-range|_" +msgstr "" + +#: ../Doc/library/functions.rst:22 +msgid ":func:`vars`" +msgstr "" + +#: ../Doc/library/functions.rst:23 +msgid ":func:`classmethod`" +msgstr "" + +#: ../Doc/library/functions.rst:23 +msgid ":func:`getattr`" +msgstr "" + +#: ../Doc/library/functions.rst:23 +msgid ":func:`locals`" +msgstr "" + +#: ../Doc/library/functions.rst:23 +msgid ":func:`repr`" +msgstr "" + +#: ../Doc/library/functions.rst:23 +msgid ":func:`zip`" +msgstr "" + +#: ../Doc/library/functions.rst:24 +msgid ":func:`compile`" +msgstr "" + +#: ../Doc/library/functions.rst:24 +msgid ":func:`globals`" +msgstr "" + +#: ../Doc/library/functions.rst:24 +msgid ":func:`map`" +msgstr "" + +#: ../Doc/library/functions.rst:24 +msgid ":func:`reversed`" +msgstr "" + +#: ../Doc/library/functions.rst:24 +msgid ":func:`__import__`" +msgstr "" + +#: ../Doc/library/functions.rst:25 ../Doc/library/stdtypes.rst:302 +msgid ":func:`complex`" +msgstr "" + +#: ../Doc/library/functions.rst:25 +msgid ":func:`hasattr`" +msgstr "" + +#: ../Doc/library/functions.rst:25 +msgid ":func:`max`" +msgstr "" + +#: ../Doc/library/functions.rst:25 +msgid ":func:`round`" +msgstr "" + +#: ../Doc/library/functions.rst:26 +msgid ":func:`delattr`" +msgstr "" + +#: ../Doc/library/functions.rst:26 +msgid ":func:`hash`" +msgstr "" + +#: ../Doc/library/functions.rst:26 +msgid "|func-memoryview|_" +msgstr "" + +#: ../Doc/library/functions.rst:26 +msgid "|func-set|_" +msgstr "" + +#: ../Doc/library/functions.rst:44 +msgid "" +"Return the absolute value of a number. The argument may be an integer or a " +"floating point number. If the argument is a complex number, its magnitude " +"is returned." +msgstr "" + +#: ../Doc/library/functions.rst:51 +msgid "" +"Return ``True`` if all elements of the *iterable* are true (or if the " +"iterable is empty). Equivalent to::" +msgstr "" + +#: ../Doc/library/functions.rst:63 +msgid "" +"Return ``True`` if any element of the *iterable* is true. If the iterable " +"is empty, return ``False``. Equivalent to::" +msgstr "" + +#: ../Doc/library/functions.rst:75 +msgid "" +"As :func:`repr`, return a string containing a printable representation of an " +"object, but escape the non-ASCII characters in the string returned by :func:" +"`repr` using ``\\x``, ``\\u`` or ``\\U`` escapes. This generates a string " +"similar to that returned by :func:`repr` in Python 2." +msgstr "" + +#: ../Doc/library/functions.rst:83 +msgid "" +"Convert an integer number to a binary string. The result is a valid Python " +"expression. If *x* is not a Python :class:`int` object, it has to define " +"an :meth:`__index__` method that returns an integer." +msgstr "" + +#: ../Doc/library/functions.rst:90 +msgid "" +"Return a Boolean value, i.e. one of ``True`` or ``False``. *x* is converted " +"using the standard :ref:`truth testing procedure `. If *x* is false " +"or omitted, this returns ``False``; otherwise it returns ``True``. The :" +"class:`bool` class is a subclass of :class:`int` (see :ref:`typesnumeric`). " +"It cannot be subclassed further. Its only instances are ``False`` and " +"``True`` (see :ref:`bltin-boolean-values`)." +msgstr "" + +#: ../Doc/library/functions.rst:103 +msgid "" +"Return a new array of bytes. The :class:`bytearray` class is a mutable " +"sequence of integers in the range 0 <= x < 256. It has most of the usual " +"methods of mutable sequences, described in :ref:`typesseq-mutable`, as well " +"as most methods that the :class:`bytes` type has, see :ref:`bytes-methods`." +msgstr "" + +#: ../Doc/library/functions.rst:108 +msgid "" +"The optional *source* parameter can be used to initialize the array in a few " +"different ways:" +msgstr "" + +#: ../Doc/library/functions.rst:111 +msgid "" +"If it is a *string*, you must also give the *encoding* (and optionally, " +"*errors*) parameters; :func:`bytearray` then converts the string to bytes " +"using :meth:`str.encode`." +msgstr "" + +#: ../Doc/library/functions.rst:115 +msgid "" +"If it is an *integer*, the array will have that size and will be initialized " +"with null bytes." +msgstr "" + +#: ../Doc/library/functions.rst:118 +msgid "" +"If it is an object conforming to the *buffer* interface, a read-only buffer " +"of the object will be used to initialize the bytes array." +msgstr "" + +#: ../Doc/library/functions.rst:121 +msgid "" +"If it is an *iterable*, it must be an iterable of integers in the range ``0 " +"<= x < 256``, which are used as the initial contents of the array." +msgstr "" + +#: ../Doc/library/functions.rst:124 +msgid "Without an argument, an array of size 0 is created." +msgstr "" + +#: ../Doc/library/functions.rst:126 +msgid "See also :ref:`binaryseq` and :ref:`typebytearray`." +msgstr "" + +#: ../Doc/library/functions.rst:132 +msgid "" +"Return a new \"bytes\" object, which is an immutable sequence of integers in " +"the range ``0 <= x < 256``. :class:`bytes` is an immutable version of :" +"class:`bytearray` -- it has the same non-mutating methods and the same " +"indexing and slicing behavior." +msgstr "" + +#: ../Doc/library/functions.rst:137 +msgid "" +"Accordingly, constructor arguments are interpreted as for :func:`bytearray`." +msgstr "" + +#: ../Doc/library/functions.rst:139 +msgid "Bytes objects can also be created with literals, see :ref:`strings`." +msgstr "" + +#: ../Doc/library/functions.rst:141 +msgid "See also :ref:`binaryseq`, :ref:`typebytes`, and :ref:`bytes-methods`." +msgstr "" + +#: ../Doc/library/functions.rst:146 +msgid "" +"Return :const:`True` if the *object* argument appears callable, :const:" +"`False` if not. If this returns true, it is still possible that a call " +"fails, but if it is false, calling *object* will never succeed. Note that " +"classes are callable (calling a class returns a new instance); instances are " +"callable if their class has a :meth:`__call__` method." +msgstr "" + +#: ../Doc/library/functions.rst:152 +msgid "" +"This function was first removed in Python 3.0 and then brought back in " +"Python 3.2." +msgstr "" + +#: ../Doc/library/functions.rst:159 +msgid "" +"Return the string representing a character whose Unicode code point is the " +"integer *i*. For example, ``chr(97)`` returns the string ``'a'``, while " +"``chr(8364)`` returns the string ``'€'``. This is the inverse of :func:`ord`." +msgstr "" + +#: ../Doc/library/functions.rst:163 +msgid "" +"The valid range for the argument is from 0 through 1,114,111 (0x10FFFF in " +"base 16). :exc:`ValueError` will be raised if *i* is outside that range." +msgstr "" + +#: ../Doc/library/functions.rst:169 +msgid "Return a class method for *function*." +msgstr "" + +#: ../Doc/library/functions.rst:171 +msgid "" +"A class method receives the class as implicit first argument, just like an " +"instance method receives the instance. To declare a class method, use this " +"idiom::" +msgstr "" + +#: ../Doc/library/functions.rst:179 +msgid "" +"The ``@classmethod`` form is a function :term:`decorator` -- see the " +"description of function definitions in :ref:`function` for details." +msgstr "" + +#: ../Doc/library/functions.rst:182 +msgid "" +"It can be called either on the class (such as ``C.f()``) or on an instance " +"(such as ``C().f()``). The instance is ignored except for its class. If a " +"class method is called for a derived class, the derived class object is " +"passed as the implied first argument." +msgstr "" + +#: ../Doc/library/functions.rst:187 +msgid "" +"Class methods are different than C++ or Java static methods. If you want " +"those, see :func:`staticmethod` in this section." +msgstr "" + +#: ../Doc/library/functions.rst:190 +msgid "" +"For more information on class methods, consult the documentation on the " +"standard type hierarchy in :ref:`types`." +msgstr "" + +#: ../Doc/library/functions.rst:196 +msgid "" +"Compile the *source* into a code or AST object. Code objects can be " +"executed by :func:`exec` or :func:`eval`. *source* can either be a normal " +"string, a byte string, or an AST object. Refer to the :mod:`ast` module " +"documentation for information on how to work with AST objects." +msgstr "" + +#: ../Doc/library/functions.rst:201 +msgid "" +"The *filename* argument should give the file from which the code was read; " +"pass some recognizable value if it wasn't read from a file (``''`` " +"is commonly used)." +msgstr "" + +#: ../Doc/library/functions.rst:205 +msgid "" +"The *mode* argument specifies what kind of code must be compiled; it can be " +"``'exec'`` if *source* consists of a sequence of statements, ``'eval'`` if " +"it consists of a single expression, or ``'single'`` if it consists of a " +"single interactive statement (in the latter case, expression statements that " +"evaluate to something other than ``None`` will be printed)." +msgstr "" + +#: ../Doc/library/functions.rst:211 +msgid "" +"The optional arguments *flags* and *dont_inherit* control which future " +"statements (see :pep:`236`) affect the compilation of *source*. If neither " +"is present (or both are zero) the code is compiled with those future " +"statements that are in effect in the code that is calling :func:`compile`. " +"If the *flags* argument is given and *dont_inherit* is not (or is zero) then " +"the future statements specified by the *flags* argument are used in addition " +"to those that would be used anyway. If *dont_inherit* is a non-zero integer " +"then the *flags* argument is it -- the future statements in effect around " +"the call to compile are ignored." +msgstr "" + +#: ../Doc/library/functions.rst:221 +msgid "" +"Future statements are specified by bits which can be bitwise ORed together " +"to specify multiple statements. The bitfield required to specify a given " +"feature can be found as the :attr:`~__future__._Feature.compiler_flag` " +"attribute on the :class:`~__future__._Feature` instance in the :mod:" +"`__future__` module." +msgstr "" + +#: ../Doc/library/functions.rst:226 +msgid "" +"The argument *optimize* specifies the optimization level of the compiler; " +"the default value of ``-1`` selects the optimization level of the " +"interpreter as given by :option:`-O` options. Explicit levels are ``0`` (no " +"optimization; ``__debug__`` is true), ``1`` (asserts are removed, " +"``__debug__`` is false) or ``2`` (docstrings are removed too)." +msgstr "" + +#: ../Doc/library/functions.rst:232 +msgid "" +"This function raises :exc:`SyntaxError` if the compiled source is invalid, " +"and :exc:`ValueError` if the source contains null bytes." +msgstr "" + +#: ../Doc/library/functions.rst:235 +msgid "" +"If you want to parse Python code into its AST representation, see :func:`ast." +"parse`." +msgstr "" + +#: ../Doc/library/functions.rst:240 +msgid "" +"When compiling a string with multi-line code in ``'single'`` or ``'eval'`` " +"mode, input must be terminated by at least one newline character. This is " +"to facilitate detection of incomplete and complete statements in the :mod:" +"`code` module." +msgstr "" + +#: ../Doc/library/functions.rst:245 +msgid "" +"Allowed use of Windows and Mac newlines. Also input in ``'exec'`` mode does " +"not have to end in a newline anymore. Added the *optimize* parameter." +msgstr "" + +#: ../Doc/library/functions.rst:249 +msgid "" +"Previously, :exc:`TypeError` was raised when null bytes were encountered in " +"*source*." +msgstr "" + +#: ../Doc/library/functions.rst:256 +msgid "" +"Return a complex number with the value *real* + *imag*\\*1j or convert a " +"string or number to a complex number. If the first parameter is a string, " +"it will be interpreted as a complex number and the function must be called " +"without a second parameter. The second parameter can never be a string. " +"Each argument may be any numeric type (including complex). If *imag* is " +"omitted, it defaults to zero and the constructor serves as a numeric " +"conversion like :class:`int` and :class:`float`. If both arguments are " +"omitted, returns ``0j``." +msgstr "" + +#: ../Doc/library/functions.rst:267 +msgid "" +"When converting from a string, the string must not contain whitespace around " +"the central ``+`` or ``-`` operator. For example, ``complex('1+2j')`` is " +"fine, but ``complex('1 + 2j')`` raises :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/functions.rst:272 +msgid "The complex type is described in :ref:`typesnumeric`." +msgstr "" + +#: ../Doc/library/functions.rst:274 ../Doc/library/functions.rst:537 +#: ../Doc/library/functions.rst:711 +msgid "Grouping digits with underscores as in code literals is allowed." +msgstr "" + +#: ../Doc/library/functions.rst:280 +msgid "" +"This is a relative of :func:`setattr`. The arguments are an object and a " +"string. The string must be the name of one of the object's attributes. The " +"function deletes the named attribute, provided the object allows it. For " +"example, ``delattr(x, 'foobar')`` is equivalent to ``del x.foobar``." +msgstr "" + +#: ../Doc/library/functions.rst:292 +msgid "" +"Create a new dictionary. The :class:`dict` object is the dictionary class. " +"See :class:`dict` and :ref:`typesmapping` for documentation about this class." +msgstr "" + +#: ../Doc/library/functions.rst:295 +msgid "" +"For other containers see the built-in :class:`list`, :class:`set`, and :" +"class:`tuple` classes, as well as the :mod:`collections` module." +msgstr "" + +#: ../Doc/library/functions.rst:301 +msgid "" +"Without arguments, return the list of names in the current local scope. " +"With an argument, attempt to return a list of valid attributes for that " +"object." +msgstr "" + +#: ../Doc/library/functions.rst:304 +msgid "" +"If the object has a method named :meth:`__dir__`, this method will be called " +"and must return the list of attributes. This allows objects that implement a " +"custom :func:`__getattr__` or :func:`__getattribute__` function to customize " +"the way :func:`dir` reports their attributes." +msgstr "" + +#: ../Doc/library/functions.rst:309 +msgid "" +"If the object does not provide :meth:`__dir__`, the function tries its best " +"to gather information from the object's :attr:`~object.__dict__` attribute, " +"if defined, and from its type object. The resulting list is not necessarily " +"complete, and may be inaccurate when the object has a custom :func:" +"`__getattr__`." +msgstr "" + +#: ../Doc/library/functions.rst:314 +msgid "" +"The default :func:`dir` mechanism behaves differently with different types " +"of objects, as it attempts to produce the most relevant, rather than " +"complete, information:" +msgstr "" + +#: ../Doc/library/functions.rst:318 +msgid "" +"If the object is a module object, the list contains the names of the " +"module's attributes." +msgstr "" + +#: ../Doc/library/functions.rst:321 +msgid "" +"If the object is a type or class object, the list contains the names of its " +"attributes, and recursively of the attributes of its bases." +msgstr "" + +#: ../Doc/library/functions.rst:324 +msgid "" +"Otherwise, the list contains the object's attributes' names, the names of " +"its class's attributes, and recursively of the attributes of its class's " +"base classes." +msgstr "" + +#: ../Doc/library/functions.rst:328 +msgid "The resulting list is sorted alphabetically. For example:" +msgstr "" + +#: ../Doc/library/functions.rst:347 +msgid "" +"Because :func:`dir` is supplied primarily as a convenience for use at an " +"interactive prompt, it tries to supply an interesting set of names more than " +"it tries to supply a rigorously or consistently defined set of names, and " +"its detailed behavior may change across releases. For example, metaclass " +"attributes are not in the result list when the argument is a class." +msgstr "" + +#: ../Doc/library/functions.rst:357 +msgid "" +"Take two (non complex) numbers as arguments and return a pair of numbers " +"consisting of their quotient and remainder when using integer division. " +"With mixed operand types, the rules for binary arithmetic operators apply. " +"For integers, the result is the same as ``(a // b, a % b)``. For floating " +"point numbers the result is ``(q, a % b)``, where *q* is usually ``math." +"floor(a / b)`` but may be 1 less than that. In any case ``q * b + a % b`` " +"is very close to *a*, if ``a % b`` is non-zero it has the same sign as *b*, " +"and ``0 <= abs(a % b) < abs(b)``." +msgstr "" + +#: ../Doc/library/functions.rst:369 +msgid "" +"Return an enumerate object. *iterable* must be a sequence, an :term:" +"`iterator`, or some other object which supports iteration. The :meth:" +"`~iterator.__next__` method of the iterator returned by :func:`enumerate` " +"returns a tuple containing a count (from *start* which defaults to 0) and " +"the values obtained from iterating over *iterable*." +msgstr "" + +#: ../Doc/library/functions.rst:381 ../Doc/library/operator.rst:269 +#: ../Doc/library/operator.rst:301 ../Doc/library/operator.rst:347 +#: ../Doc/library/stdtypes.rst:468 +msgid "Equivalent to::" +msgstr "" + +#: ../Doc/library/functions.rst:392 +msgid "" +"The arguments are a string and optional globals and locals. If provided, " +"*globals* must be a dictionary. If provided, *locals* can be any mapping " +"object." +msgstr "" + +#: ../Doc/library/functions.rst:396 +msgid "" +"The *expression* argument is parsed and evaluated as a Python expression " +"(technically speaking, a condition list) using the *globals* and *locals* " +"dictionaries as global and local namespace. If the *globals* dictionary is " +"present and lacks '__builtins__', the current globals are copied into " +"*globals* before *expression* is parsed. This means that *expression* " +"normally has full access to the standard :mod:`builtins` module and " +"restricted environments are propagated. If the *locals* dictionary is " +"omitted it defaults to the *globals* dictionary. If both dictionaries are " +"omitted, the expression is executed in the environment where :func:`eval` is " +"called. The return value is the result of the evaluated expression. Syntax " +"errors are reported as exceptions. Example:" +msgstr "" + +#: ../Doc/library/functions.rst:411 +msgid "" +"This function can also be used to execute arbitrary code objects (such as " +"those created by :func:`compile`). In this case pass a code object instead " +"of a string. If the code object has been compiled with ``'exec'`` as the " +"*mode* argument, :func:`eval`\\'s return value will be ``None``." +msgstr "" + +#: ../Doc/library/functions.rst:416 +msgid "" +"Hints: dynamic execution of statements is supported by the :func:`exec` " +"function. The :func:`globals` and :func:`locals` functions returns the " +"current global and local dictionary, respectively, which may be useful to " +"pass around for use by :func:`eval` or :func:`exec`." +msgstr "" + +#: ../Doc/library/functions.rst:421 +msgid "" +"See :func:`ast.literal_eval` for a function that can safely evaluate strings " +"with expressions containing only literals." +msgstr "" + +#: ../Doc/library/functions.rst:428 +msgid "" +"This function supports dynamic execution of Python code. *object* must be " +"either a string or a code object. If it is a string, the string is parsed " +"as a suite of Python statements which is then executed (unless a syntax " +"error occurs). [#]_ If it is a code object, it is simply executed. In all " +"cases, the code that's executed is expected to be valid as file input (see " +"the section \"File input\" in the Reference Manual). Be aware that the :" +"keyword:`return` and :keyword:`yield` statements may not be used outside of " +"function definitions even within the context of code passed to the :func:" +"`exec` function. The return value is ``None``." +msgstr "" + +#: ../Doc/library/functions.rst:438 +msgid "" +"In all cases, if the optional parts are omitted, the code is executed in the " +"current scope. If only *globals* is provided, it must be a dictionary, " +"which will be used for both the global and the local variables. If " +"*globals* and *locals* are given, they are used for the global and local " +"variables, respectively. If provided, *locals* can be any mapping object. " +"Remember that at module level, globals and locals are the same dictionary. " +"If exec gets two separate objects as *globals* and *locals*, the code will " +"be executed as if it were embedded in a class definition." +msgstr "" + +#: ../Doc/library/functions.rst:447 +msgid "" +"If the *globals* dictionary does not contain a value for the key " +"``__builtins__``, a reference to the dictionary of the built-in module :mod:" +"`builtins` is inserted under that key. That way you can control what " +"builtins are available to the executed code by inserting your own " +"``__builtins__`` dictionary into *globals* before passing it to :func:`exec`." +msgstr "" + +#: ../Doc/library/functions.rst:455 +msgid "" +"The built-in functions :func:`globals` and :func:`locals` return the current " +"global and local dictionary, respectively, which may be useful to pass " +"around for use as the second and third argument to :func:`exec`." +msgstr "" + +#: ../Doc/library/functions.rst:461 +msgid "" +"The default *locals* act as described for function :func:`locals` below: " +"modifications to the default *locals* dictionary should not be attempted. " +"Pass an explicit *locals* dictionary if you need to see effects of the code " +"on *locals* after function :func:`exec` returns." +msgstr "" + +#: ../Doc/library/functions.rst:469 +msgid "" +"Construct an iterator from those elements of *iterable* for which *function* " +"returns true. *iterable* may be either a sequence, a container which " +"supports iteration, or an iterator. If *function* is ``None``, the identity " +"function is assumed, that is, all elements of *iterable* that are false are " +"removed." +msgstr "" + +#: ../Doc/library/functions.rst:475 +msgid "" +"Note that ``filter(function, iterable)`` is equivalent to the generator " +"expression ``(item for item in iterable if function(item))`` if function is " +"not ``None`` and ``(item for item in iterable if item)`` if function is " +"``None``." +msgstr "" + +#: ../Doc/library/functions.rst:480 +msgid "" +"See :func:`itertools.filterfalse` for the complementary function that " +"returns elements of *iterable* for which *function* returns false." +msgstr "" + +#: ../Doc/library/functions.rst:490 +msgid "Return a floating point number constructed from a number or string *x*." +msgstr "" + +#: ../Doc/library/functions.rst:492 +msgid "" +"If the argument is a string, it should contain a decimal number, optionally " +"preceded by a sign, and optionally embedded in whitespace. The optional " +"sign may be ``'+'`` or ``'-'``; a ``'+'`` sign has no effect on the value " +"produced. The argument may also be a string representing a NaN (not-a-" +"number), or a positive or negative infinity. More precisely, the input must " +"conform to the following grammar after leading and trailing whitespace " +"characters are removed:" +msgstr "" + +#: ../Doc/library/functions.rst:507 +msgid "" +"Here ``floatnumber`` is the form of a Python floating-point literal, " +"described in :ref:`floating`. Case is not significant, so, for example, " +"\"inf\", \"Inf\", \"INFINITY\" and \"iNfINity\" are all acceptable spellings " +"for positive infinity." +msgstr "" + +#: ../Doc/library/functions.rst:512 +msgid "" +"Otherwise, if the argument is an integer or a floating point number, a " +"floating point number with the same value (within Python's floating point " +"precision) is returned. If the argument is outside the range of a Python " +"float, an :exc:`OverflowError` will be raised." +msgstr "" + +#: ../Doc/library/functions.rst:517 +msgid "" +"For a general Python object ``x``, ``float(x)`` delegates to ``x." +"__float__()``." +msgstr "" + +#: ../Doc/library/functions.rst:520 +msgid "If no argument is given, ``0.0`` is returned." +msgstr "" + +#: ../Doc/library/functions.rst:522 ../Doc/library/pkgutil.rst:185 +#: ../Doc/library/subprocess.rst:78 +msgid "Examples::" +msgstr "" + +#: ../Doc/library/functions.rst:535 +msgid "The float type is described in :ref:`typesnumeric`." +msgstr "" + +#: ../Doc/library/functions.rst:547 +msgid "" +"Convert a *value* to a \"formatted\" representation, as controlled by " +"*format_spec*. The interpretation of *format_spec* will depend on the type " +"of the *value* argument, however there is a standard formatting syntax that " +"is used by most built-in types: :ref:`formatspec`." +msgstr "" + +#: ../Doc/library/functions.rst:552 +msgid "" +"The default *format_spec* is an empty string which usually gives the same " +"effect as calling :func:`str(value) `." +msgstr "" + +#: ../Doc/library/functions.rst:555 +msgid "" +"A call to ``format(value, format_spec)`` is translated to ``type(value)." +"__format__(value, format_spec)`` which bypasses the instance dictionary when " +"searching for the value's :meth:`__format__` method. A :exc:`TypeError` " +"exception is raised if the method search reaches :mod:`object` and the " +"*format_spec* is non-empty, or if either the *format_spec* or the return " +"value are not strings." +msgstr "" + +#: ../Doc/library/functions.rst:562 +msgid "" +"``object().__format__(format_spec)`` raises :exc:`TypeError` if " +"*format_spec* is not an empty string." +msgstr "" + +#: ../Doc/library/functions.rst:571 +msgid "" +"Return a new :class:`frozenset` object, optionally with elements taken from " +"*iterable*. ``frozenset`` is a built-in class. See :class:`frozenset` and :" +"ref:`types-set` for documentation about this class." +msgstr "" + +#: ../Doc/library/functions.rst:575 +msgid "" +"For other containers see the built-in :class:`set`, :class:`list`, :class:" +"`tuple`, and :class:`dict` classes, as well as the :mod:`collections` module." +msgstr "" + +#: ../Doc/library/functions.rst:582 +msgid "" +"Return the value of the named attribute of *object*. *name* must be a " +"string. If the string is the name of one of the object's attributes, the " +"result is the value of that attribute. For example, ``getattr(x, " +"'foobar')`` is equivalent to ``x.foobar``. If the named attribute does not " +"exist, *default* is returned if provided, otherwise :exc:`AttributeError` is " +"raised." +msgstr "" + +#: ../Doc/library/functions.rst:591 +msgid "" +"Return a dictionary representing the current global symbol table. This is " +"always the dictionary of the current module (inside a function or method, " +"this is the module where it is defined, not the module from which it is " +"called)." +msgstr "" + +#: ../Doc/library/functions.rst:598 +msgid "" +"The arguments are an object and a string. The result is ``True`` if the " +"string is the name of one of the object's attributes, ``False`` if not. " +"(This is implemented by calling ``getattr(object, name)`` and seeing whether " +"it raises an :exc:`AttributeError` or not.)" +msgstr "" + +#: ../Doc/library/functions.rst:606 +msgid "" +"Return the hash value of the object (if it has one). Hash values are " +"integers. They are used to quickly compare dictionary keys during a " +"dictionary lookup. Numeric values that compare equal have the same hash " +"value (even if they are of different types, as is the case for 1 and 1.0)." +msgstr "" + +#: ../Doc/library/functions.rst:613 +msgid "" +"For object's with custom :meth:`__hash__` methods, note that :func:`hash` " +"truncates the return value based on the bit width of the host machine. See :" +"meth:`__hash__` for details." +msgstr "" + +#: ../Doc/library/functions.rst:619 +msgid "" +"Invoke the built-in help system. (This function is intended for interactive " +"use.) If no argument is given, the interactive help system starts on the " +"interpreter console. If the argument is a string, then the string is looked " +"up as the name of a module, function, class, method, keyword, or " +"documentation topic, and a help page is printed on the console. If the " +"argument is any other kind of object, a help page on the object is generated." +msgstr "" + +#: ../Doc/library/functions.rst:626 +msgid "" +"This function is added to the built-in namespace by the :mod:`site` module." +msgstr "" + +#: ../Doc/library/functions.rst:628 +msgid "" +"Changes to :mod:`pydoc` and :mod:`inspect` mean that the reported signatures " +"for callables are now more comprehensive and consistent." +msgstr "" + +#: ../Doc/library/functions.rst:635 +msgid "" +"Convert an integer number to a lowercase hexadecimal string prefixed with " +"\"0x\", for example:" +msgstr "" + +#: ../Doc/library/functions.rst:643 +msgid "" +"If x is not a Python :class:`int` object, it has to define an __index__() " +"method that returns an integer." +msgstr "" + +#: ../Doc/library/functions.rst:646 +msgid "" +"See also :func:`int` for converting a hexadecimal string to an integer using " +"a base of 16." +msgstr "" + +#: ../Doc/library/functions.rst:651 +msgid "" +"To obtain a hexadecimal string representation for a float, use the :meth:" +"`float.hex` method." +msgstr "" + +#: ../Doc/library/functions.rst:657 +msgid "" +"Return the \"identity\" of an object. This is an integer which is " +"guaranteed to be unique and constant for this object during its lifetime. " +"Two objects with non-overlapping lifetimes may have the same :func:`id` " +"value." +msgstr "" + +#: ../Doc/library/functions.rst:667 +msgid "" +"If the *prompt* argument is present, it is written to standard output " +"without a trailing newline. The function then reads a line from input, " +"converts it to a string (stripping a trailing newline), and returns that. " +"When EOF is read, :exc:`EOFError` is raised. Example::" +msgstr "" + +#: ../Doc/library/functions.rst:677 +msgid "" +"If the :mod:`readline` module was loaded, then :func:`input` will use it to " +"provide elaborate line editing and history features." +msgstr "" + +#: ../Doc/library/functions.rst:684 +msgid "" +"Return an integer object constructed from a number or string *x*, or return " +"``0`` if no arguments are given. If *x* is a number, return :meth:`x." +"__int__() `. For floating point numbers, this truncates " +"towards zero." +msgstr "" + +#: ../Doc/library/functions.rst:689 +msgid "" +"If *x* is not a number or if *base* is given, then *x* must be a string, :" +"class:`bytes`, or :class:`bytearray` instance representing an :ref:`integer " +"literal ` in radix *base*. Optionally, the literal can be " +"preceded by ``+`` or ``-`` (with no space in between) and surrounded by " +"whitespace. A base-n literal consists of the digits 0 to n-1, with ``a`` to " +"``z`` (or ``A`` to ``Z``) having values 10 to 35. The default *base* is 10. " +"The allowed values are 0 and 2-36. Base-2, -8, and -16 literals can be " +"optionally prefixed with ``0b``/``0B``, ``0o``/``0O``, or ``0x``/``0X``, as " +"with integer literals in code. Base 0 means to interpret exactly as a code " +"literal, so that the actual base is 2, 8, 10, or 16, and so that " +"``int('010', 0)`` is not legal, while ``int('010')`` is, as well as " +"``int('010', 8)``." +msgstr "" + +#: ../Doc/library/functions.rst:702 +msgid "The integer type is described in :ref:`typesnumeric`." +msgstr "" + +#: ../Doc/library/functions.rst:704 +msgid "" +"If *base* is not an instance of :class:`int` and the *base* object has a :" +"meth:`base.__index__ ` method, that method is called to " +"obtain an integer for the base. Previous versions used :meth:`base.__int__ " +"` instead of :meth:`base.__index__ `." +msgstr "" + +#: ../Doc/library/functions.rst:717 +msgid "" +"Return true if the *object* argument is an instance of the *classinfo* " +"argument, or of a (direct, indirect or :term:`virtual `) subclass thereof. If *object* is not an object of the given type, " +"the function always returns false. If *classinfo* is a tuple of type objects " +"(or recursively, other such tuples), return true if *object* is an instance " +"of any of the types. If *classinfo* is not a type or tuple of types and such " +"tuples, a :exc:`TypeError` exception is raised." +msgstr "" + +#: ../Doc/library/functions.rst:729 +msgid "" +"Return true if *class* is a subclass (direct, indirect or :term:`virtual " +"`) of *classinfo*. A class is considered a subclass of " +"itself. *classinfo* may be a tuple of class objects, in which case every " +"entry in *classinfo* will be checked. In any other case, a :exc:`TypeError` " +"exception is raised." +msgstr "" + +#: ../Doc/library/functions.rst:738 +msgid "" +"Return an :term:`iterator` object. The first argument is interpreted very " +"differently depending on the presence of the second argument. Without a " +"second argument, *object* must be a collection object which supports the " +"iteration protocol (the :meth:`__iter__` method), or it must support the " +"sequence protocol (the :meth:`__getitem__` method with integer arguments " +"starting at ``0``). If it does not support either of those protocols, :exc:" +"`TypeError` is raised. If the second argument, *sentinel*, is given, then " +"*object* must be a callable object. The iterator created in this case will " +"call *object* with no arguments for each call to its :meth:`~iterator." +"__next__` method; if the value returned is equal to *sentinel*, :exc:" +"`StopIteration` will be raised, otherwise the value will be returned." +msgstr "" + +#: ../Doc/library/functions.rst:751 +msgid "See also :ref:`typeiter`." +msgstr "" + +#: ../Doc/library/functions.rst:753 +msgid "" +"One useful application of the second form of :func:`iter` is to read lines " +"of a file until a certain line is reached. The following example reads a " +"file until the :meth:`~io.TextIOBase.readline` method returns an empty " +"string::" +msgstr "" + +#: ../Doc/library/functions.rst:764 +msgid "" +"Return the length (the number of items) of an object. The argument may be a " +"sequence (such as a string, bytes, tuple, list, or range) or a collection " +"(such as a dictionary, set, or frozen set)." +msgstr "" + +#: ../Doc/library/functions.rst:773 +msgid "" +"Rather than being a function, :class:`list` is actually a mutable sequence " +"type, as documented in :ref:`typesseq-list` and :ref:`typesseq`." +msgstr "" + +#: ../Doc/library/functions.rst:779 +msgid "" +"Update and return a dictionary representing the current local symbol table. " +"Free variables are returned by :func:`locals` when it is called in function " +"blocks, but not in class blocks." +msgstr "" + +#: ../Doc/library/functions.rst:784 +msgid "" +"The contents of this dictionary should not be modified; changes may not " +"affect the values of local and free variables used by the interpreter." +msgstr "" + +#: ../Doc/library/functions.rst:789 +msgid "" +"Return an iterator that applies *function* to every item of *iterable*, " +"yielding the results. If additional *iterable* arguments are passed, " +"*function* must take that many arguments and is applied to the items from " +"all iterables in parallel. With multiple iterables, the iterator stops when " +"the shortest iterable is exhausted. For cases where the function inputs are " +"already arranged into argument tuples, see :func:`itertools.starmap`\\." +msgstr "" + +#: ../Doc/library/functions.rst:800 +msgid "" +"Return the largest item in an iterable or the largest of two or more " +"arguments." +msgstr "" + +#: ../Doc/library/functions.rst:803 +msgid "" +"If one positional argument is provided, it should be an :term:`iterable`. " +"The largest item in the iterable is returned. If two or more positional " +"arguments are provided, the largest of the positional arguments is returned." +msgstr "" + +#: ../Doc/library/functions.rst:808 ../Doc/library/functions.rst:842 +msgid "" +"There are two optional keyword-only arguments. The *key* argument specifies " +"a one-argument ordering function like that used for :meth:`list.sort`. The " +"*default* argument specifies an object to return if the provided iterable is " +"empty. If the iterable is empty and *default* is not provided, a :exc:" +"`ValueError` is raised." +msgstr "" + +#: ../Doc/library/functions.rst:814 +msgid "" +"If multiple items are maximal, the function returns the first one " +"encountered. This is consistent with other sort-stability preserving tools " +"such as ``sorted(iterable, key=keyfunc, reverse=True)[0]`` and ``heapq." +"nlargest(1, iterable, key=keyfunc)``." +msgstr "" + +#: ../Doc/library/functions.rst:819 ../Doc/library/functions.rst:853 +msgid "The *default* keyword-only argument." +msgstr "" + +#: ../Doc/library/functions.rst:827 +msgid "" +"Return a \"memory view\" object created from the given argument. See :ref:" +"`typememoryview` for more information." +msgstr "" + +#: ../Doc/library/functions.rst:834 +msgid "" +"Return the smallest item in an iterable or the smallest of two or more " +"arguments." +msgstr "" + +#: ../Doc/library/functions.rst:837 +msgid "" +"If one positional argument is provided, it should be an :term:`iterable`. " +"The smallest item in the iterable is returned. If two or more positional " +"arguments are provided, the smallest of the positional arguments is returned." +msgstr "" + +#: ../Doc/library/functions.rst:848 +msgid "" +"If multiple items are minimal, the function returns the first one " +"encountered. This is consistent with other sort-stability preserving tools " +"such as ``sorted(iterable, key=keyfunc)[0]`` and ``heapq.nsmallest(1, " +"iterable, key=keyfunc)``." +msgstr "" + +#: ../Doc/library/functions.rst:859 +msgid "" +"Retrieve the next item from the *iterator* by calling its :meth:`~iterator." +"__next__` method. If *default* is given, it is returned if the iterator is " +"exhausted, otherwise :exc:`StopIteration` is raised." +msgstr "" + +#: ../Doc/library/functions.rst:866 +msgid "" +"Return a new featureless object. :class:`object` is a base for all classes. " +"It has the methods that are common to all instances of Python classes. This " +"function does not accept any arguments." +msgstr "" + +#: ../Doc/library/functions.rst:872 +msgid "" +":class:`object` does *not* have a :attr:`~object.__dict__`, so you can't " +"assign arbitrary attributes to an instance of the :class:`object` class." +msgstr "" + +#: ../Doc/library/functions.rst:878 +msgid "" +"Convert an integer number to an octal string. The result is a valid Python " +"expression. If *x* is not a Python :class:`int` object, it has to define " +"an :meth:`__index__` method that returns an integer." +msgstr "" + +#: ../Doc/library/functions.rst:888 +msgid "" +"Open *file* and return a corresponding :term:`file object`. If the file " +"cannot be opened, an :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/functions.rst:891 +msgid "" +"*file* is a :term:`path-like object` giving the pathname (absolute or " +"relative to the current working directory) of the file to be opened or an " +"integer file descriptor of the file to be wrapped. (If a file descriptor is " +"given, it is closed when the returned I/O object is closed, unless *closefd* " +"is set to ``False``.)" +msgstr "" + +#: ../Doc/library/functions.rst:897 +msgid "" +"*mode* is an optional string that specifies the mode in which the file is " +"opened. It defaults to ``'r'`` which means open for reading in text mode. " +"Other common values are ``'w'`` for writing (truncating the file if it " +"already exists), ``'x'`` for exclusive creation and ``'a'`` for appending " +"(which on *some* Unix systems, means that *all* writes append to the end of " +"the file regardless of the current seek position). In text mode, if " +"*encoding* is not specified the encoding used is platform dependent: " +"``locale.getpreferredencoding(False)`` is called to get the current locale " +"encoding. (For reading and writing raw bytes use binary mode and leave " +"*encoding* unspecified.) The available modes are:" +msgstr "" + +#: ../Doc/library/functions.rst:909 ../Doc/library/struct.rst:124 +msgid "Character" +msgstr "" + +#: ../Doc/library/functions.rst:911 +msgid "open for reading (default)" +msgstr "" + +#: ../Doc/library/functions.rst:912 +msgid "open for writing, truncating the file first" +msgstr "" + +#: ../Doc/library/functions.rst:913 ../Doc/library/stdtypes.rst:2163 +#: ../Doc/library/stdtypes.rst:3263 ../Doc/library/string.rst:434 +msgid "``'x'``" +msgstr "" + +#: ../Doc/library/functions.rst:913 +msgid "open for exclusive creation, failing if the file already exists" +msgstr "" + +#: ../Doc/library/functions.rst:914 ../Doc/library/stdtypes.rst:2192 +#: ../Doc/library/stdtypes.rst:3293 +msgid "``'a'``" +msgstr "" + +#: ../Doc/library/functions.rst:914 +msgid "open for writing, appending to the end of the file if it exists" +msgstr "" + +#: ../Doc/library/functions.rst:915 +msgid "binary mode" +msgstr "" + +#: ../Doc/library/functions.rst:916 +msgid "``'t'``" +msgstr "" + +#: ../Doc/library/functions.rst:916 +msgid "text mode (default)" +msgstr "" + +#: ../Doc/library/functions.rst:917 ../Doc/library/re.rst:117 +#: ../Doc/library/stdtypes.rst:2143 ../Doc/library/stdtypes.rst:3243 +#: ../Doc/library/string.rst:352 +msgid "``'+'``" +msgstr "" + +#: ../Doc/library/functions.rst:917 +msgid "open a disk file for updating (reading and writing)" +msgstr "" + +#: ../Doc/library/functions.rst:918 +msgid "``'U'``" +msgstr "" + +#: ../Doc/library/functions.rst:918 +msgid ":term:`universal newlines` mode (deprecated)" +msgstr "" + +#: ../Doc/library/functions.rst:921 +msgid "" +"The default mode is ``'r'`` (open for reading text, synonym of ``'rt'``). " +"For binary read-write access, the mode ``'w+b'`` opens and truncates the " +"file to 0 bytes. ``'r+b'`` opens the file without truncation." +msgstr "" + +#: ../Doc/library/functions.rst:925 +msgid "" +"As mentioned in the :ref:`io-overview`, Python distinguishes between binary " +"and text I/O. Files opened in binary mode (including ``'b'`` in the *mode* " +"argument) return contents as :class:`bytes` objects without any decoding. " +"In text mode (the default, or when ``'t'`` is included in the *mode* " +"argument), the contents of the file are returned as :class:`str`, the bytes " +"having been first decoded using a platform-dependent encoding or using the " +"specified *encoding* if given." +msgstr "" + +#: ../Doc/library/functions.rst:935 +msgid "" +"Python doesn't depend on the underlying operating system's notion of text " +"files; all the processing is done by Python itself, and is therefore " +"platform-independent." +msgstr "" + +#: ../Doc/library/functions.rst:939 +msgid "" +"*buffering* is an optional integer used to set the buffering policy. Pass 0 " +"to switch buffering off (only allowed in binary mode), 1 to select line " +"buffering (only usable in text mode), and an integer > 1 to indicate the " +"size in bytes of a fixed-size chunk buffer. When no *buffering* argument is " +"given, the default buffering policy works as follows:" +msgstr "" + +#: ../Doc/library/functions.rst:945 +msgid "" +"Binary files are buffered in fixed-size chunks; the size of the buffer is " +"chosen using a heuristic trying to determine the underlying device's \"block " +"size\" and falling back on :attr:`io.DEFAULT_BUFFER_SIZE`. On many systems, " +"the buffer will typically be 4096 or 8192 bytes long." +msgstr "" + +#: ../Doc/library/functions.rst:950 +msgid "" +"\"Interactive\" text files (files for which :meth:`~io.IOBase.isatty` " +"returns ``True``) use line buffering. Other text files use the policy " +"described above for binary files." +msgstr "" + +#: ../Doc/library/functions.rst:954 +msgid "" +"*encoding* is the name of the encoding used to decode or encode the file. " +"This should only be used in text mode. The default encoding is platform " +"dependent (whatever :func:`locale.getpreferredencoding` returns), but any :" +"term:`text encoding` supported by Python can be used. See the :mod:`codecs` " +"module for the list of supported encodings." +msgstr "" + +#: ../Doc/library/functions.rst:961 +msgid "" +"*errors* is an optional string that specifies how encoding and decoding " +"errors are to be handled--this cannot be used in binary mode. A variety of " +"standard error handlers are available (listed under :ref:`error-handlers`), " +"though any error handling name that has been registered with :func:`codecs." +"register_error` is also valid. The standard names include:" +msgstr "" + +#: ../Doc/library/functions.rst:969 +msgid "" +"``'strict'`` to raise a :exc:`ValueError` exception if there is an encoding " +"error. The default value of ``None`` has the same effect." +msgstr "" + +#: ../Doc/library/functions.rst:973 +msgid "" +"``'ignore'`` ignores errors. Note that ignoring encoding errors can lead to " +"data loss." +msgstr "" + +#: ../Doc/library/functions.rst:976 +msgid "" +"``'replace'`` causes a replacement marker (such as ``'?'``) to be inserted " +"where there is malformed data." +msgstr "" + +#: ../Doc/library/functions.rst:979 +msgid "" +"``'surrogateescape'`` will represent any incorrect bytes as code points in " +"the Unicode Private Use Area ranging from U+DC80 to U+DCFF. These private " +"code points will then be turned back into the same bytes when the " +"``surrogateescape`` error handler is used when writing data. This is useful " +"for processing files in an unknown encoding." +msgstr "" + +#: ../Doc/library/functions.rst:986 +msgid "" +"``'xmlcharrefreplace'`` is only supported when writing to a file. Characters " +"not supported by the encoding are replaced with the appropriate XML " +"character reference ``&#nnn;``." +msgstr "" + +#: ../Doc/library/functions.rst:990 +msgid "" +"``'backslashreplace'`` replaces malformed data by Python's backslashed " +"escape sequences." +msgstr "" + +#: ../Doc/library/functions.rst:993 +msgid "" +"``'namereplace'`` (also only supported when writing) replaces unsupported " +"characters with ``\\N{...}`` escape sequences." +msgstr "" + +#: ../Doc/library/functions.rst:999 +msgid "" +"*newline* controls how :term:`universal newlines` mode works (it only " +"applies to text mode). It can be ``None``, ``''``, ``'\\n'``, ``'\\r'``, " +"and ``'\\r\\n'``. It works as follows:" +msgstr "" + +#: ../Doc/library/functions.rst:1003 +msgid "" +"When reading input from the stream, if *newline* is ``None``, universal " +"newlines mode is enabled. Lines in the input can end in ``'\\n'``, " +"``'\\r'``, or ``'\\r\\n'``, and these are translated into ``'\\n'`` before " +"being returned to the caller. If it is ``''``, universal newlines mode is " +"enabled, but line endings are returned to the caller untranslated. If it " +"has any of the other legal values, input lines are only terminated by the " +"given string, and the line ending is returned to the caller untranslated." +msgstr "" + +#: ../Doc/library/functions.rst:1011 ../Doc/library/io.rst:873 +msgid "" +"When writing output to the stream, if *newline* is ``None``, any ``'\\n'`` " +"characters written are translated to the system default line separator, :" +"data:`os.linesep`. If *newline* is ``''`` or ``'\\n'``, no translation " +"takes place. If *newline* is any of the other legal values, any ``'\\n'`` " +"characters written are translated to the given string." +msgstr "" + +#: ../Doc/library/functions.rst:1017 +msgid "" +"If *closefd* is ``False`` and a file descriptor rather than a filename was " +"given, the underlying file descriptor will be kept open when the file is " +"closed. If a filename is given *closefd* must be ``True`` (the default) " +"otherwise an error will be raised." +msgstr "" + +#: ../Doc/library/functions.rst:1022 +msgid "" +"A custom opener can be used by passing a callable as *opener*. The " +"underlying file descriptor for the file object is then obtained by calling " +"*opener* with (*file*, *flags*). *opener* must return an open file " +"descriptor (passing :mod:`os.open` as *opener* results in functionality " +"similar to passing ``None``)." +msgstr "" + +#: ../Doc/library/functions.rst:1028 ../Doc/library/io.rst:564 +msgid "The newly created file is :ref:`non-inheritable `." +msgstr "" + +#: ../Doc/library/functions.rst:1030 +msgid "" +"The following example uses the :ref:`dir_fd ` parameter of the :func:" +"`os.open` function to open a file relative to a given directory::" +msgstr "" + +#: ../Doc/library/functions.rst:1043 +msgid "" +"The type of :term:`file object` returned by the :func:`open` function " +"depends on the mode. When :func:`open` is used to open a file in a text " +"mode (``'w'``, ``'r'``, ``'wt'``, ``'rt'``, etc.), it returns a subclass of :" +"class:`io.TextIOBase` (specifically :class:`io.TextIOWrapper`). When used " +"to open a file in a binary mode with buffering, the returned class is a " +"subclass of :class:`io.BufferedIOBase`. The exact class varies: in read " +"binary mode, it returns an :class:`io.BufferedReader`; in write binary and " +"append binary modes, it returns an :class:`io.BufferedWriter`, and in read/" +"write mode, it returns an :class:`io.BufferedRandom`. When buffering is " +"disabled, the raw stream, a subclass of :class:`io.RawIOBase`, :class:`io." +"FileIO`, is returned." +msgstr "" + +#: ../Doc/library/functions.rst:1064 +msgid "" +"See also the file handling modules, such as, :mod:`fileinput`, :mod:`io` " +"(where :func:`open` is declared), :mod:`os`, :mod:`os.path`, :mod:" +"`tempfile`, and :mod:`shutil`." +msgstr "" + +#: ../Doc/library/functions.rst:1071 +msgid "The *opener* parameter was added." +msgstr "" + +#: ../Doc/library/functions.rst:1072 +msgid "The ``'x'`` mode was added." +msgstr "" + +#: ../Doc/library/functions.rst:1073 ../Doc/library/http.cookiejar.rst:278 +msgid ":exc:`IOError` used to be raised, it is now an alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/functions.rst:1074 +msgid ":exc:`FileExistsError` is now raised if the file opened in exclusive" +msgstr "" + +#: ../Doc/library/functions.rst:1075 +msgid "creation mode (``'x'``) already exists." +msgstr "" + +#: ../Doc/library/functions.rst:1080 ../Doc/library/io.rst:573 +msgid "The file is now non-inheritable." +msgstr "" + +#: ../Doc/library/functions.rst:None +msgid "" +"Deprecated since version 3.4, will be removed in version 4.0: The 'U' mode." +msgstr "" + +#: ../Doc/library/functions.rst:1084 +msgid "The ``'U'`` mode." +msgstr "" + +#: ../Doc/library/functions.rst:1089 ../Doc/library/os.rst:931 +#: ../Doc/library/os.rst:1114 ../Doc/library/os.rst:1232 +#: ../Doc/library/os.rst:3541 +msgid "" +"If the system call is interrupted and the signal handler does not raise an " +"exception, the function now retries the system call instead of raising an :" +"exc:`InterruptedError` exception (see :pep:`475` for the rationale)." +msgstr "" + +#: ../Doc/library/functions.rst:1092 +msgid "The ``'namereplace'`` error handler was added." +msgstr "" + +#: ../Doc/library/functions.rst:1097 +msgid "Support added to accept objects implementing :class:`os.PathLike`." +msgstr "" + +#: ../Doc/library/functions.rst:1098 +msgid "" +"On Windows, opening a console buffer may return a subclass of :class:`io." +"RawIOBase` other than :class:`io.FileIO`." +msgstr "" + +#: ../Doc/library/functions.rst:1103 +msgid "" +"Given a string representing one Unicode character, return an integer " +"representing the Unicode code point of that character. For example, " +"``ord('a')`` returns the integer ``97`` and ``ord('€')`` (Euro sign) returns " +"``8364``. This is the inverse of :func:`chr`." +msgstr "" + +#: ../Doc/library/functions.rst:1111 +msgid "" +"Return *x* to the power *y*; if *z* is present, return *x* to the power *y*, " +"modulo *z* (computed more efficiently than ``pow(x, y) % z``). The two-" +"argument form ``pow(x, y)`` is equivalent to using the power operator: " +"``x**y``." +msgstr "" + +#: ../Doc/library/functions.rst:1115 +msgid "" +"The arguments must have numeric types. With mixed operand types, the " +"coercion rules for binary arithmetic operators apply. For :class:`int` " +"operands, the result has the same type as the operands (after coercion) " +"unless the second argument is negative; in that case, all arguments are " +"converted to float and a float result is delivered. For example, ``10**2`` " +"returns ``100``, but ``10**-2`` returns ``0.01``. If the second argument is " +"negative, the third argument must be omitted. If *z* is present, *x* and " +"*y* must be of integer types, and *y* must be non-negative." +msgstr "" + +#: ../Doc/library/functions.rst:1127 +msgid "" +"Print *objects* to the text stream *file*, separated by *sep* and followed " +"by *end*. *sep*, *end* and *file*, if present, must be given as keyword " +"arguments." +msgstr "" + +#: ../Doc/library/functions.rst:1131 +msgid "" +"All non-keyword arguments are converted to strings like :func:`str` does and " +"written to the stream, separated by *sep* and followed by *end*. Both *sep* " +"and *end* must be strings; they can also be ``None``, which means to use the " +"default values. If no *objects* are given, :func:`print` will just write " +"*end*." +msgstr "" + +#: ../Doc/library/functions.rst:1137 +msgid "" +"The *file* argument must be an object with a ``write(string)`` method; if it " +"is not present or ``None``, :data:`sys.stdout` will be used. Since printed " +"arguments are converted to text strings, :func:`print` cannot be used with " +"binary mode file objects. For these, use ``file.write(...)`` instead." +msgstr "" + +#: ../Doc/library/functions.rst:1142 +msgid "" +"Whether output is buffered is usually determined by *file*, but if the " +"*flush* keyword argument is true, the stream is forcibly flushed." +msgstr "" + +#: ../Doc/library/functions.rst:1145 +msgid "Added the *flush* keyword argument." +msgstr "" + +#: ../Doc/library/functions.rst:1151 +msgid "Return a property attribute." +msgstr "" + +#: ../Doc/library/functions.rst:1153 +msgid "" +"*fget* is a function for getting an attribute value. *fset* is a function " +"for setting an attribute value. *fdel* is a function for deleting an " +"attribute value. And *doc* creates a docstring for the attribute." +msgstr "" + +#: ../Doc/library/functions.rst:1157 +msgid "A typical use is to define a managed attribute ``x``::" +msgstr "" + +#: ../Doc/library/functions.rst:1174 +msgid "" +"If *c* is an instance of *C*, ``c.x`` will invoke the getter, ``c.x = " +"value`` will invoke the setter and ``del c.x`` the deleter." +msgstr "" + +#: ../Doc/library/functions.rst:1177 +msgid "" +"If given, *doc* will be the docstring of the property attribute. Otherwise, " +"the property will copy *fget*'s docstring (if it exists). This makes it " +"possible to create read-only properties easily using :func:`property` as a :" +"term:`decorator`::" +msgstr "" + +#: ../Doc/library/functions.rst:1190 +msgid "" +"The ``@property`` decorator turns the :meth:`voltage` method into a \"getter" +"\" for a read-only attribute with the same name, and it sets the docstring " +"for *voltage* to \"Get the current voltage.\"" +msgstr "" + +#: ../Doc/library/functions.rst:1194 +msgid "" +"A property object has :attr:`~property.getter`, :attr:`~property.setter`, " +"and :attr:`~property.deleter` methods usable as decorators that create a " +"copy of the property with the corresponding accessor function set to the " +"decorated function. This is best explained with an example::" +msgstr "" + +#: ../Doc/library/functions.rst:1216 +msgid "" +"This code is exactly equivalent to the first example. Be sure to give the " +"additional functions the same name as the original property (``x`` in this " +"case.)" +msgstr "" + +#: ../Doc/library/functions.rst:1220 +msgid "" +"The returned property object also has the attributes ``fget``, ``fset``, and " +"``fdel`` corresponding to the constructor arguments." +msgstr "" + +#: ../Doc/library/functions.rst:1223 +msgid "The docstrings of property objects are now writeable." +msgstr "" + +#: ../Doc/library/functions.rst:1232 +msgid "" +"Rather than being a function, :class:`range` is actually an immutable " +"sequence type, as documented in :ref:`typesseq-range` and :ref:`typesseq`." +msgstr "" + +#: ../Doc/library/functions.rst:1238 +msgid "" +"Return a string containing a printable representation of an object. For " +"many types, this function makes an attempt to return a string that would " +"yield an object with the same value when passed to :func:`eval`, otherwise " +"the representation is a string enclosed in angle brackets that contains the " +"name of the type of the object together with additional information often " +"including the name and address of the object. A class can control what this " +"function returns for its instances by defining a :meth:`__repr__` method." +msgstr "" + +#: ../Doc/library/functions.rst:1249 +msgid "" +"Return a reverse :term:`iterator`. *seq* must be an object which has a :" +"meth:`__reversed__` method or supports the sequence protocol (the :meth:" +"`__len__` method and the :meth:`__getitem__` method with integer arguments " +"starting at ``0``)." +msgstr "" + +#: ../Doc/library/functions.rst:1257 +msgid "" +"Return the floating point value *number* rounded to *ndigits* digits after " +"the decimal point. If *ndigits* is omitted or is ``None``, it returns the " +"nearest integer to its input. Delegates to ``number.__round__(ndigits)``." +msgstr "" + +#: ../Doc/library/functions.rst:1261 +msgid "" +"For the built-in types supporting :func:`round`, values are rounded to the " +"closest multiple of 10 to the power minus *ndigits*; if two multiples are " +"equally close, rounding is done toward the even choice (so, for example, " +"both ``round(0.5)`` and ``round(-0.5)`` are ``0``, and ``round(1.5)`` is " +"``2``). The return value is an integer if called with one argument, " +"otherwise of the same type as *number*." +msgstr "" + +#: ../Doc/library/functions.rst:1270 +msgid "" +"The behavior of :func:`round` for floats can be surprising: for example, " +"``round(2.675, 2)`` gives ``2.67`` instead of the expected ``2.68``. This is " +"not a bug: it's a result of the fact that most decimal fractions can't be " +"represented exactly as a float. See :ref:`tut-fp-issues` for more " +"information." +msgstr "" + +#: ../Doc/library/functions.rst:1281 +msgid "" +"Return a new :class:`set` object, optionally with elements taken from " +"*iterable*. ``set`` is a built-in class. See :class:`set` and :ref:`types-" +"set` for documentation about this class." +msgstr "" + +#: ../Doc/library/functions.rst:1285 +msgid "" +"For other containers see the built-in :class:`frozenset`, :class:`list`, :" +"class:`tuple`, and :class:`dict` classes, as well as the :mod:`collections` " +"module." +msgstr "" + +#: ../Doc/library/functions.rst:1292 +msgid "" +"This is the counterpart of :func:`getattr`. The arguments are an object, a " +"string and an arbitrary value. The string may name an existing attribute or " +"a new attribute. The function assigns the value to the attribute, provided " +"the object allows it. For example, ``setattr(x, 'foobar', 123)`` is " +"equivalent to ``x.foobar = 123``." +msgstr "" + +#: ../Doc/library/functions.rst:1304 +msgid "" +"Return a :term:`slice` object representing the set of indices specified by " +"``range(start, stop, step)``. The *start* and *step* arguments default to " +"``None``. Slice objects have read-only data attributes :attr:`~slice." +"start`, :attr:`~slice.stop` and :attr:`~slice.step` which merely return the " +"argument values (or their default). They have no other explicit " +"functionality; however they are used by Numerical Python and other third " +"party extensions. Slice objects are also generated when extended indexing " +"syntax is used. For example: ``a[start:stop:step]`` or ``a[start:stop, " +"i]``. See :func:`itertools.islice` for an alternate version that returns an " +"iterator." +msgstr "" + +#: ../Doc/library/functions.rst:1317 +msgid "Return a new sorted list from the items in *iterable*." +msgstr "" + +#: ../Doc/library/functions.rst:1319 ../Doc/library/heapq.rst:96 +msgid "" +"Has two optional arguments which must be specified as keyword arguments." +msgstr "" + +#: ../Doc/library/functions.rst:1321 +msgid "" +"*key* specifies a function of one argument that is used to extract a " +"comparison key from each list element: ``key=str.lower``. The default value " +"is ``None`` (compare the elements directly)." +msgstr "" + +#: ../Doc/library/functions.rst:1325 ../Doc/library/stdtypes.rst:1180 +msgid "" +"*reverse* is a boolean value. If set to ``True``, then the list elements " +"are sorted as if each comparison were reversed." +msgstr "" + +#: ../Doc/library/functions.rst:1328 +msgid "" +"Use :func:`functools.cmp_to_key` to convert an old-style *cmp* function to a " +"*key* function." +msgstr "" + +#: ../Doc/library/functions.rst:1331 +msgid "" +"The built-in :func:`sorted` function is guaranteed to be stable. A sort is " +"stable if it guarantees not to change the relative order of elements that " +"compare equal --- this is helpful for sorting in multiple passes (for " +"example, sort by department, then by salary grade)." +msgstr "" + +#: ../Doc/library/functions.rst:1336 ../Doc/library/functools.rst:41 +msgid "" +"For sorting examples and a brief sorting tutorial, see :ref:`sortinghowto`." +msgstr "" + +#: ../Doc/library/functions.rst:1340 +msgid "Return a static method for *function*." +msgstr "" + +#: ../Doc/library/functions.rst:1342 +msgid "" +"A static method does not receive an implicit first argument. To declare a " +"static method, use this idiom::" +msgstr "" + +#: ../Doc/library/functions.rst:1349 +msgid "" +"The ``@staticmethod`` form is a function :term:`decorator` -- see the " +"description of function definitions in :ref:`function` for details." +msgstr "" + +#: ../Doc/library/functions.rst:1352 +msgid "" +"It can be called either on the class (such as ``C.f()``) or on an instance " +"(such as ``C().f()``). The instance is ignored except for its class." +msgstr "" + +#: ../Doc/library/functions.rst:1355 +msgid "" +"Static methods in Python are similar to those found in Java or C++. Also " +"see :func:`classmethod` for a variant that is useful for creating alternate " +"class constructors." +msgstr "" + +#: ../Doc/library/functions.rst:1359 +msgid "" +"For more information on static methods, consult the documentation on the " +"standard type hierarchy in :ref:`types`." +msgstr "" + +#: ../Doc/library/functions.rst:1371 +msgid "" +"Return a :class:`str` version of *object*. See :func:`str` for details." +msgstr "" + +#: ../Doc/library/functions.rst:1373 +msgid "" +"``str`` is the built-in string :term:`class`. For general information about " +"strings, see :ref:`textseq`." +msgstr "" + +#: ../Doc/library/functions.rst:1379 +msgid "" +"Sums *start* and the items of an *iterable* from left to right and returns " +"the total. *start* defaults to ``0``. The *iterable*'s items are normally " +"numbers, and the start value is not allowed to be a string." +msgstr "" + +#: ../Doc/library/functions.rst:1383 +msgid "" +"For some use cases, there are good alternatives to :func:`sum`. The " +"preferred, fast way to concatenate a sequence of strings is by calling ``''." +"join(sequence)``. To add floating point values with extended precision, " +"see :func:`math.fsum`\\. To concatenate a series of iterables, consider " +"using :func:`itertools.chain`." +msgstr "" + +#: ../Doc/library/functions.rst:1391 +msgid "" +"Return a proxy object that delegates method calls to a parent or sibling " +"class of *type*. This is useful for accessing inherited methods that have " +"been overridden in a class. The search order is same as that used by :func:" +"`getattr` except that the *type* itself is skipped." +msgstr "" + +#: ../Doc/library/functions.rst:1396 +msgid "" +"The :attr:`~class.__mro__` attribute of the *type* lists the method " +"resolution search order used by both :func:`getattr` and :func:`super`. The " +"attribute is dynamic and can change whenever the inheritance hierarchy is " +"updated." +msgstr "" + +#: ../Doc/library/functions.rst:1401 +msgid "" +"If the second argument is omitted, the super object returned is unbound. If " +"the second argument is an object, ``isinstance(obj, type)`` must be true. " +"If the second argument is a type, ``issubclass(type2, type)`` must be true " +"(this is useful for classmethods)." +msgstr "" + +#: ../Doc/library/functions.rst:1406 +msgid "" +"There are two typical use cases for *super*. In a class hierarchy with " +"single inheritance, *super* can be used to refer to parent classes without " +"naming them explicitly, thus making the code more maintainable. This use " +"closely parallels the use of *super* in other programming languages." +msgstr "" + +#: ../Doc/library/functions.rst:1411 +msgid "" +"The second use case is to support cooperative multiple inheritance in a " +"dynamic execution environment. This use case is unique to Python and is not " +"found in statically compiled languages or languages that only support single " +"inheritance. This makes it possible to implement \"diamond diagrams\" where " +"multiple base classes implement the same method. Good design dictates that " +"this method have the same calling signature in every case (because the order " +"of calls is determined at runtime, because that order adapts to changes in " +"the class hierarchy, and because that order can include sibling classes that " +"are unknown prior to runtime)." +msgstr "" + +#: ../Doc/library/functions.rst:1421 +msgid "For both use cases, a typical superclass call looks like this::" +msgstr "" + +#: ../Doc/library/functions.rst:1428 +msgid "" +"Note that :func:`super` is implemented as part of the binding process for " +"explicit dotted attribute lookups such as ``super().__getitem__(name)``. It " +"does so by implementing its own :meth:`__getattribute__` method for " +"searching classes in a predictable order that supports cooperative multiple " +"inheritance. Accordingly, :func:`super` is undefined for implicit lookups " +"using statements or operators such as ``super()[name]``." +msgstr "" + +#: ../Doc/library/functions.rst:1435 +msgid "" +"Also note that, aside from the zero argument form, :func:`super` is not " +"limited to use inside methods. The two argument form specifies the " +"arguments exactly and makes the appropriate references. The zero argument " +"form only works inside a class definition, as the compiler fills in the " +"necessary details to correctly retrieve the class being defined, as well as " +"accessing the current instance for ordinary methods." +msgstr "" + +#: ../Doc/library/functions.rst:1442 +msgid "" +"For practical suggestions on how to design cooperative classes using :func:" +"`super`, see `guide to using super() `_." +msgstr "" + +#: ../Doc/library/functions.rst:1451 +msgid "" +"Rather than being a function, :class:`tuple` is actually an immutable " +"sequence type, as documented in :ref:`typesseq-tuple` and :ref:`typesseq`." +msgstr "" + +#: ../Doc/library/functions.rst:1460 +msgid "" +"With one argument, return the type of an *object*. The return value is a " +"type object and generally the same object as returned by :attr:`object." +"__class__ `." +msgstr "" + +#: ../Doc/library/functions.rst:1464 +msgid "" +"The :func:`isinstance` built-in function is recommended for testing the type " +"of an object, because it takes subclasses into account." +msgstr "" + +#: ../Doc/library/functions.rst:1468 +msgid "" +"With three arguments, return a new type object. This is essentially a " +"dynamic form of the :keyword:`class` statement. The *name* string is the " +"class name and becomes the :attr:`~definition.__name__` attribute; the " +"*bases* tuple itemizes the base classes and becomes the :attr:`~class." +"__bases__` attribute; and the *dict* dictionary is the namespace containing " +"definitions for class body and is copied to a standard dictionary to become " +"the :attr:`~object.__dict__` attribute. For example, the following two " +"statements create identical :class:`type` objects:" +msgstr "" + +#: ../Doc/library/functions.rst:1482 +msgid "See also :ref:`bltin-type-objects`." +msgstr "" + +#: ../Doc/library/functions.rst:1484 +msgid "" +"Subclasses of :class:`type` which don't override ``type.__new__`` may no " +"longer use the one-argument form to get the type of an object." +msgstr "" + +#: ../Doc/library/functions.rst:1490 +msgid "" +"Return the :attr:`~object.__dict__` attribute for a module, class, instance, " +"or any other object with a :attr:`~object.__dict__` attribute." +msgstr "" + +#: ../Doc/library/functions.rst:1493 +msgid "" +"Objects such as modules and instances have an updateable :attr:`~object." +"__dict__` attribute; however, other objects may have write restrictions on " +"their :attr:`~object.__dict__` attributes (for example, classes use a :class:" +"`types.MappingProxyType` to prevent direct dictionary updates)." +msgstr "" + +#: ../Doc/library/functions.rst:1498 +msgid "" +"Without an argument, :func:`vars` acts like :func:`locals`. Note, the " +"locals dictionary is only useful for reads since updates to the locals " +"dictionary are ignored." +msgstr "" + +#: ../Doc/library/functions.rst:1505 +msgid "Make an iterator that aggregates elements from each of the iterables." +msgstr "" + +#: ../Doc/library/functions.rst:1507 +msgid "" +"Returns an iterator of tuples, where the *i*-th tuple contains the *i*-th " +"element from each of the argument sequences or iterables. The iterator " +"stops when the shortest input iterable is exhausted. With a single iterable " +"argument, it returns an iterator of 1-tuples. With no arguments, it returns " +"an empty iterator. Equivalent to::" +msgstr "" + +#: ../Doc/library/functions.rst:1526 +msgid "" +"The left-to-right evaluation order of the iterables is guaranteed. This " +"makes possible an idiom for clustering a data series into n-length groups " +"using ``zip(*[iter(s)]*n)``. This repeats the *same* iterator ``n`` times " +"so that each output tuple has the result of ``n`` calls to the iterator. " +"This has the effect of dividing the input into n-length chunks." +msgstr "" + +#: ../Doc/library/functions.rst:1532 +msgid "" +":func:`zip` should only be used with unequal length inputs when you don't " +"care about trailing, unmatched values from the longer iterables. If those " +"values are important, use :func:`itertools.zip_longest` instead." +msgstr "" + +#: ../Doc/library/functions.rst:1536 +msgid "" +":func:`zip` in conjunction with the ``*`` operator can be used to unzip a " +"list::" +msgstr "" + +#: ../Doc/library/functions.rst:1557 +msgid "" +"This is an advanced function that is not needed in everyday Python " +"programming, unlike :func:`importlib.import_module`." +msgstr "" + +#: ../Doc/library/functions.rst:1560 +msgid "" +"This function is invoked by the :keyword:`import` statement. It can be " +"replaced (by importing the :mod:`builtins` module and assigning to " +"``builtins.__import__``) in order to change semantics of the :keyword:" +"`import` statement, but doing so is **strongly** discouraged as it is " +"usually simpler to use import hooks (see :pep:`302`) to attain the same " +"goals and does not cause issues with code which assumes the default import " +"implementation is in use. Direct use of :func:`__import__` is also " +"discouraged in favor of :func:`importlib.import_module`." +msgstr "" + +#: ../Doc/library/functions.rst:1569 +msgid "" +"The function imports the module *name*, potentially using the given " +"*globals* and *locals* to determine how to interpret the name in a package " +"context. The *fromlist* gives the names of objects or submodules that should " +"be imported from the module given by *name*. The standard implementation " +"does not use its *locals* argument at all, and uses its *globals* only to " +"determine the package context of the :keyword:`import` statement." +msgstr "" + +#: ../Doc/library/functions.rst:1576 +msgid "" +"*level* specifies whether to use absolute or relative imports. ``0`` (the " +"default) means only perform absolute imports. Positive values for *level* " +"indicate the number of parent directories to search relative to the " +"directory of the module calling :func:`__import__` (see :pep:`328` for the " +"details)." +msgstr "" + +#: ../Doc/library/functions.rst:1582 +msgid "" +"When the *name* variable is of the form ``package.module``, normally, the " +"top-level package (the name up till the first dot) is returned, *not* the " +"module named by *name*. However, when a non-empty *fromlist* argument is " +"given, the module named by *name* is returned." +msgstr "" + +#: ../Doc/library/functions.rst:1587 +msgid "" +"For example, the statement ``import spam`` results in bytecode resembling " +"the following code::" +msgstr "" + +#: ../Doc/library/functions.rst:1592 +msgid "The statement ``import spam.ham`` results in this call::" +msgstr "" + +#: ../Doc/library/functions.rst:1596 +msgid "" +"Note how :func:`__import__` returns the toplevel module here because this is " +"the object that is bound to a name by the :keyword:`import` statement." +msgstr "" + +#: ../Doc/library/functions.rst:1599 +msgid "" +"On the other hand, the statement ``from spam.ham import eggs, sausage as " +"saus`` results in ::" +msgstr "" + +#: ../Doc/library/functions.rst:1606 +msgid "" +"Here, the ``spam.ham`` module is returned from :func:`__import__`. From " +"this object, the names to import are retrieved and assigned to their " +"respective names." +msgstr "" + +#: ../Doc/library/functions.rst:1610 +msgid "" +"If you simply want to import a module (potentially within a package) by " +"name, use :func:`importlib.import_module`." +msgstr "" + +#: ../Doc/library/functions.rst:1613 +msgid "" +"Negative values for *level* are no longer supported (which also changes the " +"default value to 0)." +msgstr "" + +#: ../Doc/library/functions.rst:1620 +msgid "" +"Note that the parser only accepts the Unix-style end of line convention. If " +"you are reading the code from a file, make sure to use newline conversion " +"mode to convert Windows or Mac-style newlines." +msgstr "" + +#: ../Doc/library/functools.rst:2 +msgid "" +":mod:`functools` --- Higher-order functions and operations on callable " +"objects" +msgstr "" + +#: ../Doc/library/functools.rst:13 +msgid "**Source code:** :source:`Lib/functools.py`" +msgstr "" + +#: ../Doc/library/functools.rst:17 +msgid "" +"The :mod:`functools` module is for higher-order functions: functions that " +"act on or return other functions. In general, any callable object can be " +"treated as a function for the purposes of this module." +msgstr "" + +#: ../Doc/library/functools.rst:21 +msgid "The :mod:`functools` module defines the following functions:" +msgstr "" + +#: ../Doc/library/functools.rst:25 +msgid "" +"Transform an old-style comparison function to a :term:`key function`. Used " +"with tools that accept key functions (such as :func:`sorted`, :func:`min`, :" +"func:`max`, :func:`heapq.nlargest`, :func:`heapq.nsmallest`, :func:" +"`itertools.groupby`). This function is primarily used as a transition tool " +"for programs being converted from Python 2 which supported the use of " +"comparison functions." +msgstr "" + +#: ../Doc/library/functools.rst:32 +msgid "" +"A comparison function is any callable that accept two arguments, compares " +"them, and returns a negative number for less-than, zero for equality, or a " +"positive number for greater-than. A key function is a callable that accepts " +"one argument and returns another value to be used as the sort key." +msgstr "" + +#: ../Doc/library/functools.rst:48 +msgid "" +"Decorator to wrap a function with a memoizing callable that saves up to the " +"*maxsize* most recent calls. It can save time when an expensive or I/O " +"bound function is periodically called with the same arguments." +msgstr "" + +#: ../Doc/library/functools.rst:52 +msgid "" +"Since a dictionary is used to cache results, the positional and keyword " +"arguments to the function must be hashable." +msgstr "" + +#: ../Doc/library/functools.rst:55 +msgid "" +"If *maxsize* is set to None, the LRU feature is disabled and the cache can " +"grow without bound. The LRU feature performs best when *maxsize* is a power-" +"of-two." +msgstr "" + +#: ../Doc/library/functools.rst:59 +msgid "" +"If *typed* is set to True, function arguments of different types will be " +"cached separately. For example, ``f(3)`` and ``f(3.0)`` will be treated as " +"distinct calls with distinct results." +msgstr "" + +#: ../Doc/library/functools.rst:63 +msgid "" +"To help measure the effectiveness of the cache and tune the *maxsize* " +"parameter, the wrapped function is instrumented with a :func:`cache_info` " +"function that returns a :term:`named tuple` showing *hits*, *misses*, " +"*maxsize* and *currsize*. In a multi-threaded environment, the hits and " +"misses are approximate." +msgstr "" + +#: ../Doc/library/functools.rst:69 +msgid "" +"The decorator also provides a :func:`cache_clear` function for clearing or " +"invalidating the cache." +msgstr "" + +#: ../Doc/library/functools.rst:72 +msgid "" +"The original underlying function is accessible through the :attr:" +"`__wrapped__` attribute. This is useful for introspection, for bypassing " +"the cache, or for rewrapping the function with a different cache." +msgstr "" + +#: ../Doc/library/functools.rst:76 +msgid "" +"An `LRU (least recently used) cache `_ works best when the most recent calls are the " +"best predictors of upcoming calls (for example, the most popular articles on " +"a news server tend to change each day). The cache's size limit assures that " +"the cache does not grow without bound on long-running processes such as web " +"servers." +msgstr "" + +#: ../Doc/library/functools.rst:83 +msgid "Example of an LRU cache for static web content::" +msgstr "" + +#: ../Doc/library/functools.rst:102 +msgid "" +"Example of efficiently computing `Fibonacci numbers `_ using a cache to implement a `dynamic " +"programming `_ technique::" +msgstr "" + +#: ../Doc/library/functools.rst:122 +msgid "Added the *typed* option." +msgstr "" + +#: ../Doc/library/functools.rst:127 +msgid "" +"Given a class defining one or more rich comparison ordering methods, this " +"class decorator supplies the rest. This simplifies the effort involved in " +"specifying all of the possible rich comparison operations:" +msgstr "" + +#: ../Doc/library/functools.rst:131 +msgid "" +"The class must define one of :meth:`__lt__`, :meth:`__le__`, :meth:`__gt__`, " +"or :meth:`__ge__`. In addition, the class should supply an :meth:`__eq__` " +"method." +msgstr "" + +#: ../Doc/library/functools.rst:155 +msgid "" +"While this decorator makes it easy to create well behaved totally ordered " +"types, it *does* come at the cost of slower execution and more complex stack " +"traces for the derived comparison methods. If performance benchmarking " +"indicates this is a bottleneck for a given application, implementing all six " +"rich comparison methods instead is likely to provide an easy speed boost." +msgstr "" + +#: ../Doc/library/functools.rst:164 +msgid "" +"Returning NotImplemented from the underlying comparison function for " +"unrecognised types is now supported." +msgstr "" + +#: ../Doc/library/functools.rst:170 +msgid "" +"Return a new :class:`partial` object which when called will behave like " +"*func* called with the positional arguments *args* and keyword arguments " +"*keywords*. If more arguments are supplied to the call, they are appended to " +"*args*. If additional keyword arguments are supplied, they extend and " +"override *keywords*. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/functools.rst:186 +msgid "" +"The :func:`partial` is used for partial function application which \"freezes" +"\" some portion of a function's arguments and/or keywords resulting in a new " +"object with a simplified signature. For example, :func:`partial` can be " +"used to create a callable that behaves like the :func:`int` function where " +"the *base* argument defaults to two:" +msgstr "" + +#: ../Doc/library/functools.rst:201 +msgid "" +"Return a new :class:`partialmethod` descriptor which behaves like :class:" +"`partial` except that it is designed to be used as a method definition " +"rather than being directly callable." +msgstr "" + +#: ../Doc/library/functools.rst:205 +msgid "" +"*func* must be a :term:`descriptor` or a callable (objects which are both, " +"like normal functions, are handled as descriptors)." +msgstr "" + +#: ../Doc/library/functools.rst:208 +msgid "" +"When *func* is a descriptor (such as a normal Python function, :func:" +"`classmethod`, :func:`staticmethod`, :func:`abstractmethod` or another " +"instance of :class:`partialmethod`), calls to ``__get__`` are delegated to " +"the underlying descriptor, and an appropriate :class:`partial` object " +"returned as the result." +msgstr "" + +#: ../Doc/library/functools.rst:214 +msgid "" +"When *func* is a non-descriptor callable, an appropriate bound method is " +"created dynamically. This behaves like a normal Python function when used as " +"a method: the *self* argument will be inserted as the first positional " +"argument, even before the *args* and *keywords* supplied to the :class:" +"`partialmethod` constructor." +msgstr "" + +#: ../Doc/library/functools.rst:245 +msgid "" +"Apply *function* of two arguments cumulatively to the items of *sequence*, " +"from left to right, so as to reduce the sequence to a single value. For " +"example, ``reduce(lambda x, y: x+y, [1, 2, 3, 4, 5])`` calculates " +"``((((1+2)+3)+4)+5)``. The left argument, *x*, is the accumulated value and " +"the right argument, *y*, is the update value from the *sequence*. If the " +"optional *initializer* is present, it is placed before the items of the " +"sequence in the calculation, and serves as a default when the sequence is " +"empty. If *initializer* is not given and *sequence* contains only one item, " +"the first item is returned." +msgstr "" + +#: ../Doc/library/functools.rst:254 ../Doc/library/itertools.rst:101 +#: ../Doc/library/itertools.rst:193 ../Doc/library/itertools.rst:242 +#: ../Doc/library/itertools.rst:468 ../Doc/library/itertools.rst:547 +#: ../Doc/library/itertools.rst:600 +msgid "Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/functools.rst:269 +msgid "" +"Transforms a function into a :term:`single-dispatch ` :term:" +"`generic function`." +msgstr "" + +#: ../Doc/library/functools.rst:272 +msgid "" +"To define a generic function, decorate it with the ``@singledispatch`` " +"decorator. Note that the dispatch happens on the type of the first argument, " +"create your function accordingly::" +msgstr "" + +#: ../Doc/library/functools.rst:283 +msgid "" +"To add overloaded implementations to the function, use the :func:`register` " +"attribute of the generic function. It is a decorator, taking a type " +"parameter and decorating a function implementing the operation for that " +"type::" +msgstr "" + +#: ../Doc/library/functools.rst:301 +msgid "" +"To enable registering lambdas and pre-existing functions, the :func:" +"`register` attribute can be used in a functional form::" +msgstr "" + +#: ../Doc/library/functools.rst:309 +msgid "" +"The :func:`register` attribute returns the undecorated function which " +"enables decorator stacking, pickling, as well as creating unit tests for " +"each variant independently::" +msgstr "" + +#: ../Doc/library/functools.rst:323 +msgid "" +"When called, the generic function dispatches on the type of the first " +"argument::" +msgstr "" + +#: ../Doc/library/functools.rst:343 +msgid "" +"Where there is no registered implementation for a specific type, its method " +"resolution order is used to find a more generic implementation. The original " +"function decorated with ``@singledispatch`` is registered for the base " +"``object`` type, which means it is used if no better implementation is found." +msgstr "" + +#: ../Doc/library/functools.rst:349 +msgid "" +"To check which implementation will the generic function choose for a given " +"type, use the ``dispatch()`` attribute::" +msgstr "" + +#: ../Doc/library/functools.rst:357 +msgid "" +"To access all registered implementations, use the read-only ``registry`` " +"attribute::" +msgstr "" + +#: ../Doc/library/functools.rst:374 +msgid "" +"Update a *wrapper* function to look like the *wrapped* function. The " +"optional arguments are tuples to specify which attributes of the original " +"function are assigned directly to the matching attributes on the wrapper " +"function and which attributes of the wrapper function are updated with the " +"corresponding attributes from the original function. The default values for " +"these arguments are the module level constants ``WRAPPER_ASSIGNMENTS`` " +"(which assigns to the wrapper function's ``__module__``, ``__name__``, " +"``__qualname__``, ``__annotations__`` and ``__doc__``, the documentation " +"string) and ``WRAPPER_UPDATES`` (which updates the wrapper function's " +"``__dict__``, i.e. the instance dictionary)." +msgstr "" + +#: ../Doc/library/functools.rst:384 +msgid "" +"To allow access to the original function for introspection and other " +"purposes (e.g. bypassing a caching decorator such as :func:`lru_cache`), " +"this function automatically adds a ``__wrapped__`` attribute to the wrapper " +"that refers to the function being wrapped." +msgstr "" + +#: ../Doc/library/functools.rst:389 +msgid "" +"The main intended use for this function is in :term:`decorator` functions " +"which wrap the decorated function and return the wrapper. If the wrapper " +"function is not updated, the metadata of the returned function will reflect " +"the wrapper definition rather than the original function definition, which " +"is typically less than helpful." +msgstr "" + +#: ../Doc/library/functools.rst:395 +msgid "" +":func:`update_wrapper` may be used with callables other than functions. Any " +"attributes named in *assigned* or *updated* that are missing from the object " +"being wrapped are ignored (i.e. this function will not attempt to set them " +"on the wrapper function). :exc:`AttributeError` is still raised if the " +"wrapper function itself is missing any attributes named in *updated*." +msgstr "" + +#: ../Doc/library/functools.rst:401 +msgid "Automatic addition of the ``__wrapped__`` attribute." +msgstr "" + +#: ../Doc/library/functools.rst:404 +msgid "Copying of the ``__annotations__`` attribute by default." +msgstr "" + +#: ../Doc/library/functools.rst:407 +msgid "Missing attributes no longer trigger an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/functools.rst:410 +msgid "" +"The ``__wrapped__`` attribute now always refers to the wrapped function, " +"even if that function defined a ``__wrapped__`` attribute. (see :issue:" +"`17482`)" +msgstr "" + +#: ../Doc/library/functools.rst:418 +msgid "" +"This is a convenience function for invoking :func:`update_wrapper` as a " +"function decorator when defining a wrapper function. It is equivalent to " +"``partial(update_wrapper, wrapped=wrapped, assigned=assigned, " +"updated=updated)``. For example::" +msgstr "" + +#: ../Doc/library/functools.rst:444 +msgid "" +"Without the use of this decorator factory, the name of the example function " +"would have been ``'wrapper'``, and the docstring of the original :func:" +"`example` would have been lost." +msgstr "" + +#: ../Doc/library/functools.rst:452 +msgid ":class:`partial` Objects" +msgstr "" + +#: ../Doc/library/functools.rst:454 +msgid "" +":class:`partial` objects are callable objects created by :func:`partial`. " +"They have three read-only attributes:" +msgstr "" + +#: ../Doc/library/functools.rst:460 +msgid "" +"A callable object or function. Calls to the :class:`partial` object will be " +"forwarded to :attr:`func` with new arguments and keywords." +msgstr "" + +#: ../Doc/library/functools.rst:466 +msgid "" +"The leftmost positional arguments that will be prepended to the positional " +"arguments provided to a :class:`partial` object call." +msgstr "" + +#: ../Doc/library/functools.rst:472 +msgid "" +"The keyword arguments that will be supplied when the :class:`partial` object " +"is called." +msgstr "" + +#: ../Doc/library/functools.rst:475 +msgid "" +":class:`partial` objects are like :class:`function` objects in that they are " +"callable, weak referencable, and can have attributes. There are some " +"important differences. For instance, the :attr:`~definition.__name__` and :" +"attr:`__doc__` attributes are not created automatically. Also, :class:" +"`partial` objects defined in classes behave like static methods and do not " +"transform into bound methods during instance attribute look-up." +msgstr "" + +#: ../Doc/library/gc.rst:2 +msgid ":mod:`gc` --- Garbage Collector interface" +msgstr "" + +#: ../Doc/library/gc.rst:12 +msgid "" +"This module provides an interface to the optional garbage collector. It " +"provides the ability to disable the collector, tune the collection " +"frequency, and set debugging options. It also provides access to " +"unreachable objects that the collector found but cannot free. Since the " +"collector supplements the reference counting already used in Python, you can " +"disable the collector if you are sure your program does not create reference " +"cycles. Automatic collection can be disabled by calling ``gc.disable()``. " +"To debug a leaking program call ``gc.set_debug(gc.DEBUG_LEAK)``. Notice that " +"this includes ``gc.DEBUG_SAVEALL``, causing garbage-collected objects to be " +"saved in gc.garbage for inspection." +msgstr "" + +#: ../Doc/library/gc.rst:23 +msgid "The :mod:`gc` module provides the following functions:" +msgstr "" + +#: ../Doc/library/gc.rst:28 +msgid "Enable automatic garbage collection." +msgstr "" + +#: ../Doc/library/gc.rst:33 +msgid "Disable automatic garbage collection." +msgstr "" + +#: ../Doc/library/gc.rst:38 +msgid "Returns true if automatic collection is enabled." +msgstr "" + +#: ../Doc/library/gc.rst:43 +msgid "" +"With no arguments, run a full collection. The optional argument " +"*generation* may be an integer specifying which generation to collect (from " +"0 to 2). A :exc:`ValueError` is raised if the generation number is " +"invalid. The number of unreachable objects found is returned." +msgstr "" + +#: ../Doc/library/gc.rst:48 +msgid "" +"The free lists maintained for a number of built-in types are cleared " +"whenever a full collection or collection of the highest generation (2) is " +"run. Not all items in some free lists may be freed due to the particular " +"implementation, in particular :class:`float`." +msgstr "" + +#: ../Doc/library/gc.rst:56 +msgid "" +"Set the garbage collection debugging flags. Debugging information will be " +"written to ``sys.stderr``. See below for a list of debugging flags which " +"can be combined using bit operations to control debugging." +msgstr "" + +#: ../Doc/library/gc.rst:63 +msgid "Return the debugging flags currently set." +msgstr "" + +#: ../Doc/library/gc.rst:68 +msgid "" +"Returns a list of all objects tracked by the collector, excluding the list " +"returned." +msgstr "" + +#: ../Doc/library/gc.rst:74 +msgid "" +"Return a list of three per-generation dictionaries containing collection " +"statistics since interpreter start. The number of keys may change in the " +"future, but currently each dictionary will contain the following items:" +msgstr "" + +#: ../Doc/library/gc.rst:79 +msgid "``collections`` is the number of times this generation was collected;" +msgstr "" + +#: ../Doc/library/gc.rst:81 +msgid "" +"``collected`` is the total number of objects collected inside this " +"generation;" +msgstr "" + +#: ../Doc/library/gc.rst:84 +msgid "" +"``uncollectable`` is the total number of objects which were found to be " +"uncollectable (and were therefore moved to the :data:`garbage` list) inside " +"this generation." +msgstr "" + +#: ../Doc/library/gc.rst:93 +msgid "" +"Set the garbage collection thresholds (the collection frequency). Setting " +"*threshold0* to zero disables collection." +msgstr "" + +#: ../Doc/library/gc.rst:96 +msgid "" +"The GC classifies objects into three generations depending on how many " +"collection sweeps they have survived. New objects are placed in the " +"youngest generation (generation ``0``). If an object survives a collection " +"it is moved into the next older generation. Since generation ``2`` is the " +"oldest generation, objects in that generation remain there after a " +"collection. In order to decide when to run, the collector keeps track of " +"the number object allocations and deallocations since the last collection. " +"When the number of allocations minus the number of deallocations exceeds " +"*threshold0*, collection starts. Initially only generation ``0`` is " +"examined. If generation ``0`` has been examined more than *threshold1* " +"times since generation ``1`` has been examined, then generation ``1`` is " +"examined as well. Similarly, *threshold2* controls the number of " +"collections of generation ``1`` before collecting generation ``2``." +msgstr "" + +#: ../Doc/library/gc.rst:113 +msgid "" +"Return the current collection counts as a tuple of ``(count0, count1, " +"count2)``." +msgstr "" + +#: ../Doc/library/gc.rst:119 +msgid "" +"Return the current collection thresholds as a tuple of ``(threshold0, " +"threshold1, threshold2)``." +msgstr "" + +#: ../Doc/library/gc.rst:125 +msgid "" +"Return the list of objects that directly refer to any of objs. This function " +"will only locate those containers which support garbage collection; " +"extension types which do refer to other objects but do not support garbage " +"collection will not be found." +msgstr "" + +#: ../Doc/library/gc.rst:130 +msgid "" +"Note that objects which have already been dereferenced, but which live in " +"cycles and have not yet been collected by the garbage collector can be " +"listed among the resulting referrers. To get only currently live objects, " +"call :func:`collect` before calling :func:`get_referrers`." +msgstr "" + +#: ../Doc/library/gc.rst:135 +msgid "" +"Care must be taken when using objects returned by :func:`get_referrers` " +"because some of them could still be under construction and hence in a " +"temporarily invalid state. Avoid using :func:`get_referrers` for any purpose " +"other than debugging." +msgstr "" + +#: ../Doc/library/gc.rst:143 +msgid "" +"Return a list of objects directly referred to by any of the arguments. The " +"referents returned are those objects visited by the arguments' C-level :c:" +"member:`~PyTypeObject.tp_traverse` methods (if any), and may not be all " +"objects actually directly reachable. :c:member:`~PyTypeObject.tp_traverse` " +"methods are supported only by objects that support garbage collection, and " +"are only required to visit objects that may be involved in a cycle. So, for " +"example, if an integer is directly reachable from an argument, that integer " +"object may or may not appear in the result list." +msgstr "" + +#: ../Doc/library/gc.rst:154 +msgid "" +"Returns ``True`` if the object is currently tracked by the garbage " +"collector, ``False`` otherwise. As a general rule, instances of atomic " +"types aren't tracked and instances of non-atomic types (containers, user-" +"defined objects...) are. However, some type-specific optimizations can be " +"present in order to suppress the garbage collector footprint of simple " +"instances (e.g. dicts containing only atomic keys and values)::" +msgstr "" + +#: ../Doc/library/gc.rst:177 +msgid "" +"The following variables are provided for read-only access (you can mutate " +"the values but should not rebind them):" +msgstr "" + +#: ../Doc/library/gc.rst:182 +msgid "" +"A list of objects which the collector found to be unreachable but could not " +"be freed (uncollectable objects). Starting with Python 3.4, this list " +"should be empty most of the time, except when using instances of C extension " +"types with a non-NULL ``tp_del`` slot." +msgstr "" + +#: ../Doc/library/gc.rst:187 +msgid "" +"If :const:`DEBUG_SAVEALL` is set, then all unreachable objects will be added " +"to this list rather than freed." +msgstr "" + +#: ../Doc/library/gc.rst:190 +msgid "" +"If this list is non-empty at :term:`interpreter shutdown`, a :exc:" +"`ResourceWarning` is emitted, which is silent by default. If :const:" +"`DEBUG_UNCOLLECTABLE` is set, in addition all uncollectable objects are " +"printed." +msgstr "" + +#: ../Doc/library/gc.rst:196 +msgid "" +"Following :pep:`442`, objects with a :meth:`__del__` method don't end up in :" +"attr:`gc.garbage` anymore." +msgstr "" + +#: ../Doc/library/gc.rst:202 +msgid "" +"A list of callbacks that will be invoked by the garbage collector before and " +"after collection. The callbacks will be called with two arguments, *phase* " +"and *info*." +msgstr "" + +#: ../Doc/library/gc.rst:206 +msgid "*phase* can be one of two values:" +msgstr "" + +#: ../Doc/library/gc.rst:208 +msgid "\"start\": The garbage collection is about to start." +msgstr "" + +#: ../Doc/library/gc.rst:210 +msgid "\"stop\": The garbage collection has finished." +msgstr "" + +#: ../Doc/library/gc.rst:212 +msgid "" +"*info* is a dict providing more information for the callback. The following " +"keys are currently defined:" +msgstr "" + +#: ../Doc/library/gc.rst:215 +msgid "\"generation\": The oldest generation being collected." +msgstr "" + +#: ../Doc/library/gc.rst:217 +msgid "" +"\"collected\": When *phase* is \"stop\", the number of objects successfully " +"collected." +msgstr "" + +#: ../Doc/library/gc.rst:220 +msgid "" +"\"uncollectable\": When *phase* is \"stop\", the number of objects that " +"could not be collected and were put in :data:`garbage`." +msgstr "" + +#: ../Doc/library/gc.rst:223 +msgid "" +"Applications can add their own callbacks to this list. The primary use " +"cases are:" +msgstr "" + +#: ../Doc/library/gc.rst:226 +msgid "" +"Gathering statistics about garbage collection, such as how often various " +"generations are collected, and how long the collection takes." +msgstr "" + +#: ../Doc/library/gc.rst:230 +msgid "" +"Allowing applications to identify and clear their own uncollectable types " +"when they appear in :data:`garbage`." +msgstr "" + +#: ../Doc/library/gc.rst:236 +msgid "The following constants are provided for use with :func:`set_debug`:" +msgstr "" + +#: ../Doc/library/gc.rst:241 +msgid "" +"Print statistics during collection. This information can be useful when " +"tuning the collection frequency." +msgstr "" + +#: ../Doc/library/gc.rst:247 +msgid "Print information on collectable objects found." +msgstr "" + +#: ../Doc/library/gc.rst:252 +msgid "" +"Print information of uncollectable objects found (objects which are not " +"reachable but cannot be freed by the collector). These objects will be " +"added to the ``garbage`` list." +msgstr "" + +#: ../Doc/library/gc.rst:256 +msgid "" +"Also print the contents of the :data:`garbage` list at :term:`interpreter " +"shutdown`, if it isn't empty." +msgstr "" + +#: ../Doc/library/gc.rst:262 +msgid "" +"When set, all unreachable objects found will be appended to *garbage* rather " +"than being freed. This can be useful for debugging a leaking program." +msgstr "" + +#: ../Doc/library/gc.rst:268 +msgid "" +"The debugging flags necessary for the collector to print information about a " +"leaking program (equal to ``DEBUG_COLLECTABLE | DEBUG_UNCOLLECTABLE | " +"DEBUG_SAVEALL``)." +msgstr "" + +#: ../Doc/library/getopt.rst:2 +msgid ":mod:`getopt` --- C-style parser for command line options" +msgstr "" + +#: ../Doc/library/getopt.rst:8 +msgid "**Source code:** :source:`Lib/getopt.py`" +msgstr "" + +#: ../Doc/library/getopt.rst:12 +msgid "" +"The :mod:`getopt` module is a parser for command line options whose API is " +"designed to be familiar to users of the C :c:func:`getopt` function. Users " +"who are unfamiliar with the C :c:func:`getopt` function or who would like to " +"write less code and get better help and error messages should consider using " +"the :mod:`argparse` module instead." +msgstr "" + +#: ../Doc/library/getopt.rst:20 +msgid "" +"This module helps scripts to parse the command line arguments in ``sys." +"argv``. It supports the same conventions as the Unix :c:func:`getopt` " +"function (including the special meanings of arguments of the form '``-``' " +"and '``--``'). Long options similar to those supported by GNU software may " +"be used as well via an optional third argument." +msgstr "" + +#: ../Doc/library/getopt.rst:26 +msgid "This module provides two functions and an exception:" +msgstr "" + +#: ../Doc/library/getopt.rst:32 +msgid "" +"Parses command line options and parameter list. *args* is the argument list " +"to be parsed, without the leading reference to the running program. " +"Typically, this means ``sys.argv[1:]``. *shortopts* is the string of option " +"letters that the script wants to recognize, with options that require an " +"argument followed by a colon (``':'``; i.e., the same format that Unix :c:" +"func:`getopt` uses)." +msgstr "" + +#: ../Doc/library/getopt.rst:40 +msgid "" +"Unlike GNU :c:func:`getopt`, after a non-option argument, all further " +"arguments are considered also non-options. This is similar to the way non-" +"GNU Unix systems work." +msgstr "" + +#: ../Doc/library/getopt.rst:44 +msgid "" +"*longopts*, if specified, must be a list of strings with the names of the " +"long options which should be supported. The leading ``'--'`` characters " +"should not be included in the option name. Long options which require an " +"argument should be followed by an equal sign (``'='``). Optional arguments " +"are not supported. To accept only long options, *shortopts* should be an " +"empty string. Long options on the command line can be recognized so long as " +"they provide a prefix of the option name that matches exactly one of the " +"accepted options. For example, if *longopts* is ``['foo', 'frob']``, the " +"option ``--fo`` will match as ``--foo``, but ``--f`` will not match " +"uniquely, so :exc:`GetoptError` will be raised." +msgstr "" + +#: ../Doc/library/getopt.rst:55 +msgid "" +"The return value consists of two elements: the first is a list of ``(option, " +"value)`` pairs; the second is the list of program arguments left after the " +"option list was stripped (this is a trailing slice of *args*). Each option-" +"and-value pair returned has the option as its first element, prefixed with a " +"hyphen for short options (e.g., ``'-x'``) or two hyphens for long options (e." +"g., ``'--long-option'``), and the option argument as its second element, or " +"an empty string if the option has no argument. The options occur in the " +"list in the same order in which they were found, thus allowing multiple " +"occurrences. Long and short options may be mixed." +msgstr "" + +#: ../Doc/library/getopt.rst:68 +msgid "" +"This function works like :func:`getopt`, except that GNU style scanning mode " +"is used by default. This means that option and non-option arguments may be " +"intermixed. The :func:`getopt` function stops processing options as soon as " +"a non-option argument is encountered." +msgstr "" + +#: ../Doc/library/getopt.rst:73 +msgid "" +"If the first character of the option string is ``'+'``, or if the " +"environment variable :envvar:`POSIXLY_CORRECT` is set, then option " +"processing stops as soon as a non-option argument is encountered." +msgstr "" + +#: ../Doc/library/getopt.rst:80 +msgid "" +"This is raised when an unrecognized option is found in the argument list or " +"when an option requiring an argument is given none. The argument to the " +"exception is a string indicating the cause of the error. For long options, " +"an argument given to an option which does not require one will also cause " +"this exception to be raised. The attributes :attr:`msg` and :attr:`opt` " +"give the error message and related option; if there is no specific option to " +"which the exception relates, :attr:`opt` is an empty string." +msgstr "" + +#: ../Doc/library/getopt.rst:91 +msgid "Alias for :exc:`GetoptError`; for backward compatibility." +msgstr "" + +#: ../Doc/library/getopt.rst:93 +msgid "An example using only Unix style options:" +msgstr "" + +#: ../Doc/library/getopt.rst:105 +msgid "Using long option names is equally easy:" +msgstr "" + +#: ../Doc/library/getopt.rst:118 +msgid "In a script, typical usage is something like this::" +msgstr "" + +#: ../Doc/library/getopt.rst:147 +msgid "" +"Note that an equivalent command line interface could be produced with less " +"code and more informative help and error messages by using the :mod:" +"`argparse` module::" +msgstr "" + +#: ../Doc/library/getopt.rst:162 +msgid "Module :mod:`argparse`" +msgstr "" + +#: ../Doc/library/getopt.rst:163 +msgid "Alternative command line option and argument parsing library." +msgstr "" + +#: ../Doc/library/getpass.rst:2 +msgid ":mod:`getpass` --- Portable password input" +msgstr "" + +#: ../Doc/library/getpass.rst:11 +msgid "**Source code:** :source:`Lib/getpass.py`" +msgstr "" + +#: ../Doc/library/getpass.rst:15 +msgid "The :mod:`getpass` module provides two functions:" +msgstr "" + +#: ../Doc/library/getpass.rst:20 +msgid "" +"Prompt the user for a password without echoing. The user is prompted using " +"the string *prompt*, which defaults to ``'Password: '``. On Unix, the " +"prompt is written to the file-like object *stream* using the replace error " +"handler if needed. *stream* defaults to the controlling terminal (:file:`/" +"dev/tty`) or if that is unavailable to ``sys.stderr`` (this argument is " +"ignored on Windows)." +msgstr "" + +#: ../Doc/library/getpass.rst:27 +msgid "" +"If echo free input is unavailable getpass() falls back to printing a warning " +"message to *stream* and reading from ``sys.stdin`` and issuing a :exc:" +"`GetPassWarning`." +msgstr "" + +#: ../Doc/library/getpass.rst:32 +msgid "" +"If you call getpass from within IDLE, the input may be done in the terminal " +"you launched IDLE from rather than the idle window itself." +msgstr "" + +#: ../Doc/library/getpass.rst:37 +msgid "A :exc:`UserWarning` subclass issued when password input may be echoed." +msgstr "" + +#: ../Doc/library/getpass.rst:42 +msgid "Return the \"login name\" of the user." +msgstr "" + +#: ../Doc/library/getpass.rst:44 +msgid "" +"This function checks the environment variables :envvar:`LOGNAME`, :envvar:" +"`USER`, :envvar:`LNAME` and :envvar:`USERNAME`, in order, and returns the " +"value of the first one which is set to a non-empty string. If none are set, " +"the login name from the password database is returned on systems which " +"support the :mod:`pwd` module, otherwise, an exception is raised." +msgstr "" + +#: ../Doc/library/gettext.rst:2 +msgid ":mod:`gettext` --- Multilingual internationalization services" +msgstr "" + +#: ../Doc/library/gettext.rst:10 +msgid "**Source code:** :source:`Lib/gettext.py`" +msgstr "" + +#: ../Doc/library/gettext.rst:14 +msgid "" +"The :mod:`gettext` module provides internationalization (I18N) and " +"localization (L10N) services for your Python modules and applications. It " +"supports both the GNU ``gettext`` message catalog API and a higher level, " +"class-based API that may be more appropriate for Python files. The " +"interface described below allows you to write your module and application " +"messages in one natural language, and provide a catalog of translated " +"messages for running under different natural languages." +msgstr "" + +#: ../Doc/library/gettext.rst:22 +msgid "" +"Some hints on localizing your Python modules and applications are also given." +msgstr "" + +#: ../Doc/library/gettext.rst:26 +msgid "GNU :program:`gettext` API" +msgstr "" + +#: ../Doc/library/gettext.rst:28 +msgid "" +"The :mod:`gettext` module defines the following API, which is very similar " +"to the GNU :program:`gettext` API. If you use this API you will affect the " +"translation of your entire application globally. Often this is what you " +"want if your application is monolingual, with the choice of language " +"dependent on the locale of your user. If you are localizing a Python " +"module, or if your application needs to switch languages on the fly, you " +"probably want to use the class-based API instead." +msgstr "" + +#: ../Doc/library/gettext.rst:39 +msgid "" +"Bind the *domain* to the locale directory *localedir*. More concretely, :" +"mod:`gettext` will look for binary :file:`.mo` files for the given domain " +"using the path (on Unix): :file:`localedir/language/LC_MESSAGES/domain.mo`, " +"where *languages* is searched for in the environment variables :envvar:" +"`LANGUAGE`, :envvar:`LC_ALL`, :envvar:`LC_MESSAGES`, and :envvar:`LANG` " +"respectively." +msgstr "" + +#: ../Doc/library/gettext.rst:45 +msgid "" +"If *localedir* is omitted or ``None``, then the current binding for *domain* " +"is returned. [#]_" +msgstr "" + +#: ../Doc/library/gettext.rst:51 +msgid "" +"Bind the *domain* to *codeset*, changing the encoding of strings returned by " +"the :func:`gettext` family of functions. If *codeset* is omitted, then the " +"current binding is returned." +msgstr "" + +#: ../Doc/library/gettext.rst:58 +msgid "" +"Change or query the current global domain. If *domain* is ``None``, then " +"the current global domain is returned, otherwise the global domain is set to " +"*domain*, which is returned." +msgstr "" + +#: ../Doc/library/gettext.rst:65 +msgid "" +"Return the localized translation of *message*, based on the current global " +"domain, language, and locale directory. This function is usually aliased " +"as :func:`_` in the local namespace (see examples below)." +msgstr "" + +#: ../Doc/library/gettext.rst:72 +msgid "" +"Equivalent to :func:`gettext`, but the translation is returned in the " +"preferred system encoding, if no other encoding was explicitly set with :" +"func:`bind_textdomain_codeset`." +msgstr "" + +#: ../Doc/library/gettext.rst:79 +msgid "" +"Like :func:`gettext`, but look the message up in the specified *domain*." +msgstr "" + +#: ../Doc/library/gettext.rst:84 +msgid "" +"Equivalent to :func:`dgettext`, but the translation is returned in the " +"preferred system encoding, if no other encoding was explicitly set with :" +"func:`bind_textdomain_codeset`." +msgstr "" + +#: ../Doc/library/gettext.rst:91 +msgid "" +"Like :func:`gettext`, but consider plural forms. If a translation is found, " +"apply the plural formula to *n*, and return the resulting message (some " +"languages have more than two plural forms). If no translation is found, " +"return *singular* if *n* is 1; return *plural* otherwise." +msgstr "" + +#: ../Doc/library/gettext.rst:96 +msgid "" +"The Plural formula is taken from the catalog header. It is a C or Python " +"expression that has a free variable *n*; the expression evaluates to the " +"index of the plural in the catalog. See `the GNU gettext documentation " +"`__ for the " +"precise syntax to be used in :file:`.po` files and the formulas for a " +"variety of languages." +msgstr "" + +#: ../Doc/library/gettext.rst:106 +msgid "" +"Equivalent to :func:`ngettext`, but the translation is returned in the " +"preferred system encoding, if no other encoding was explicitly set with :" +"func:`bind_textdomain_codeset`." +msgstr "" + +#: ../Doc/library/gettext.rst:113 +msgid "" +"Like :func:`ngettext`, but look the message up in the specified *domain*." +msgstr "" + +#: ../Doc/library/gettext.rst:118 +msgid "" +"Equivalent to :func:`dngettext`, but the translation is returned in the " +"preferred system encoding, if no other encoding was explicitly set with :" +"func:`bind_textdomain_codeset`." +msgstr "" + +#: ../Doc/library/gettext.rst:123 +msgid "" +"Note that GNU :program:`gettext` also defines a :func:`dcgettext` method, " +"but this was deemed not useful and so it is currently unimplemented." +msgstr "" + +#: ../Doc/library/gettext.rst:126 +msgid "Here's an example of typical usage for this API::" +msgstr "" + +#: ../Doc/library/gettext.rst:137 +msgid "Class-based API" +msgstr "" + +#: ../Doc/library/gettext.rst:139 +msgid "" +"The class-based API of the :mod:`gettext` module gives you more flexibility " +"and greater convenience than the GNU :program:`gettext` API. It is the " +"recommended way of localizing your Python applications and modules. :mod:" +"`gettext` defines a \"translations\" class which implements the parsing of " +"GNU :file:`.mo` format files, and has methods for returning strings. " +"Instances of this \"translations\" class can also install themselves in the " +"built-in namespace as the function :func:`_`." +msgstr "" + +#: ../Doc/library/gettext.rst:150 +msgid "" +"This function implements the standard :file:`.mo` file search algorithm. It " +"takes a *domain*, identical to what :func:`textdomain` takes. Optional " +"*localedir* is as in :func:`bindtextdomain` Optional *languages* is a list " +"of strings, where each string is a language code." +msgstr "" + +#: ../Doc/library/gettext.rst:155 +msgid "" +"If *localedir* is not given, then the default system locale directory is " +"used. [#]_ If *languages* is not given, then the following environment " +"variables are searched: :envvar:`LANGUAGE`, :envvar:`LC_ALL`, :envvar:" +"`LC_MESSAGES`, and :envvar:`LANG`. The first one returning a non-empty " +"value is used for the *languages* variable. The environment variables should " +"contain a colon separated list of languages, which will be split on the " +"colon to produce the expected list of language code strings." +msgstr "" + +#: ../Doc/library/gettext.rst:163 +msgid "" +":func:`find` then expands and normalizes the languages, and then iterates " +"through them, searching for an existing file built of these components:" +msgstr "" + +#: ../Doc/library/gettext.rst:166 +msgid ":file:`{localedir}/{language}/LC_MESSAGES/{domain}.mo`" +msgstr "" + +#: ../Doc/library/gettext.rst:168 +msgid "" +"The first such file name that exists is returned by :func:`find`. If no such " +"file is found, then ``None`` is returned. If *all* is given, it returns a " +"list of all file names, in the order in which they appear in the languages " +"list or the environment variables." +msgstr "" + +#: ../Doc/library/gettext.rst:176 +msgid "" +"Return a :class:`Translations` instance based on the *domain*, *localedir*, " +"and *languages*, which are first passed to :func:`find` to get a list of the " +"associated :file:`.mo` file paths. Instances with identical :file:`.mo` " +"file names are cached. The actual class instantiated is either *class_* if " +"provided, otherwise :class:`GNUTranslations`. The class's constructor must " +"take a single :term:`file object` argument. If provided, *codeset* will " +"change the charset used to encode translated strings in the :meth:`lgettext` " +"and :meth:`lngettext` methods." +msgstr "" + +#: ../Doc/library/gettext.rst:185 +msgid "" +"If multiple files are found, later files are used as fallbacks for earlier " +"ones. To allow setting the fallback, :func:`copy.copy` is used to clone each " +"translation object from the cache; the actual instance data is still shared " +"with the cache." +msgstr "" + +#: ../Doc/library/gettext.rst:190 +msgid "" +"If no :file:`.mo` file is found, this function raises :exc:`OSError` if " +"*fallback* is false (which is the default), and returns a :class:" +"`NullTranslations` instance if *fallback* is true." +msgstr "" + +#: ../Doc/library/gettext.rst:194 ../Doc/library/zipimport.rst:93 +msgid ":exc:`IOError` used to be raised instead of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/gettext.rst:200 +msgid "" +"This installs the function :func:`_` in Python's builtins namespace, based " +"on *domain*, *localedir*, and *codeset* which are passed to the function :" +"func:`translation`." +msgstr "" + +#: ../Doc/library/gettext.rst:204 +msgid "" +"For the *names* parameter, please see the description of the translation " +"object's :meth:`~NullTranslations.install` method." +msgstr "" + +#: ../Doc/library/gettext.rst:207 +msgid "" +"As seen below, you usually mark the strings in your application that are " +"candidates for translation, by wrapping them in a call to the :func:`_` " +"function, like this::" +msgstr "" + +#: ../Doc/library/gettext.rst:213 +msgid "" +"For convenience, you want the :func:`_` function to be installed in Python's " +"builtins namespace, so it is easily accessible in all modules of your " +"application." +msgstr "" + +#: ../Doc/library/gettext.rst:219 +msgid "The :class:`NullTranslations` class" +msgstr "" + +#: ../Doc/library/gettext.rst:221 +msgid "" +"Translation classes are what actually implement the translation of original " +"source file message strings to translated message strings. The base class " +"used by all translation classes is :class:`NullTranslations`; this provides " +"the basic interface you can use to write your own specialized translation " +"classes. Here are the methods of :class:`NullTranslations`:" +msgstr "" + +#: ../Doc/library/gettext.rst:230 +msgid "" +"Takes an optional :term:`file object` *fp*, which is ignored by the base " +"class. Initializes \"protected\" instance variables *_info* and *_charset* " +"which are set by derived classes, as well as *_fallback*, which is set " +"through :meth:`add_fallback`. It then calls ``self._parse(fp)`` if *fp* is " +"not ``None``." +msgstr "" + +#: ../Doc/library/gettext.rst:238 +msgid "" +"No-op'd in the base class, this method takes file object *fp*, and reads the " +"data from the file, initializing its message catalog. If you have an " +"unsupported message catalog file format, you should override this method to " +"parse your format." +msgstr "" + +#: ../Doc/library/gettext.rst:246 +msgid "" +"Add *fallback* as the fallback object for the current translation object. A " +"translation object should consult the fallback if it cannot provide a " +"translation for a given message." +msgstr "" + +#: ../Doc/library/gettext.rst:253 +msgid "" +"If a fallback has been set, forward :meth:`gettext` to the fallback. " +"Otherwise, return the translated message. Overridden in derived classes." +msgstr "" + +#: ../Doc/library/gettext.rst:259 +msgid "" +"If a fallback has been set, forward :meth:`lgettext` to the fallback. " +"Otherwise, return the translated message. Overridden in derived classes." +msgstr "" + +#: ../Doc/library/gettext.rst:265 +msgid "" +"If a fallback has been set, forward :meth:`ngettext` to the fallback. " +"Otherwise, return the translated message. Overridden in derived classes." +msgstr "" + +#: ../Doc/library/gettext.rst:271 +msgid "" +"If a fallback has been set, forward :meth:`lngettext` to the fallback. " +"Otherwise, return the translated message. Overridden in derived classes." +msgstr "" + +#: ../Doc/library/gettext.rst:277 +msgid "Return the \"protected\" :attr:`_info` variable." +msgstr "" + +#: ../Doc/library/gettext.rst:282 +msgid "" +"Return the \"protected\" :attr:`_charset` variable, which is the encoding of " +"the message catalog file." +msgstr "" + +#: ../Doc/library/gettext.rst:288 +msgid "" +"Return the \"protected\" :attr:`_output_charset` variable, which defines the " +"encoding used to return translated messages in :meth:`lgettext` and :meth:" +"`lngettext`." +msgstr "" + +#: ../Doc/library/gettext.rst:295 +msgid "" +"Change the \"protected\" :attr:`_output_charset` variable, which defines the " +"encoding used to return translated messages." +msgstr "" + +#: ../Doc/library/gettext.rst:301 +msgid "" +"This method installs :meth:`self.gettext` into the built-in namespace, " +"binding it to ``_``." +msgstr "" + +#: ../Doc/library/gettext.rst:304 +msgid "" +"If the *names* parameter is given, it must be a sequence containing the " +"names of functions you want to install in the builtins namespace in addition " +"to :func:`_`. Supported names are ``'gettext'`` (bound to :meth:`self." +"gettext`), ``'ngettext'`` (bound to :meth:`self.ngettext`), ``'lgettext'`` " +"and ``'lngettext'``." +msgstr "" + +#: ../Doc/library/gettext.rst:310 +msgid "" +"Note that this is only one way, albeit the most convenient way, to make the :" +"func:`_` function available to your application. Because it affects the " +"entire application globally, and specifically the built-in namespace, " +"localized modules should never install :func:`_`. Instead, they should use " +"this code to make :func:`_` available to their module::" +msgstr "" + +#: ../Doc/library/gettext.rst:320 +msgid "" +"This puts :func:`_` only in the module's global namespace and so only " +"affects calls within this module." +msgstr "" + +#: ../Doc/library/gettext.rst:325 +msgid "The :class:`GNUTranslations` class" +msgstr "" + +#: ../Doc/library/gettext.rst:327 +msgid "" +"The :mod:`gettext` module provides one additional class derived from :class:" +"`NullTranslations`: :class:`GNUTranslations`. This class overrides :meth:" +"`_parse` to enable reading GNU :program:`gettext` format :file:`.mo` files " +"in both big-endian and little-endian format." +msgstr "" + +#: ../Doc/library/gettext.rst:332 +msgid "" +":class:`GNUTranslations` parses optional meta-data out of the translation " +"catalog. It is convention with GNU :program:`gettext` to include meta-data " +"as the translation for the empty string. This meta-data is in :rfc:`822`\\ -" +"style ``key: value`` pairs, and should contain the ``Project-Id-Version`` " +"key. If the key ``Content-Type`` is found, then the ``charset`` property is " +"used to initialize the \"protected\" :attr:`_charset` instance variable, " +"defaulting to ``None`` if not found. If the charset encoding is specified, " +"then all message ids and message strings read from the catalog are converted " +"to Unicode using this encoding, else ASCII encoding is assumed." +msgstr "" + +#: ../Doc/library/gettext.rst:342 +msgid "" +"Since message ids are read as Unicode strings too, all :meth:`*gettext` " +"methods will assume message ids as Unicode strings, not byte strings." +msgstr "" + +#: ../Doc/library/gettext.rst:345 +msgid "" +"The entire set of key/value pairs are placed into a dictionary and set as " +"the \"protected\" :attr:`_info` instance variable." +msgstr "" + +#: ../Doc/library/gettext.rst:348 +msgid "" +"If the :file:`.mo` file's magic number is invalid, the major version number " +"is unexpected, or if other problems occur while reading the file, " +"instantiating a :class:`GNUTranslations` class can raise :exc:`OSError`." +msgstr "" + +#: ../Doc/library/gettext.rst:352 +msgid "" +"The following methods are overridden from the base class implementation:" +msgstr "" + +#: ../Doc/library/gettext.rst:357 +msgid "" +"Look up the *message* id in the catalog and return the corresponding message " +"string, as a Unicode string. If there is no entry in the catalog for the " +"*message* id, and a fallback has been set, the look up is forwarded to the " +"fallback's :meth:`gettext` method. Otherwise, the *message* id is returned." +msgstr "" + +#: ../Doc/library/gettext.rst:365 ../Doc/library/gettext.rst:392 +msgid "" +"Equivalent to :meth:`gettext`, but the translation is returned as a " +"bytestring encoded in the selected output charset, or in the preferred " +"system encoding if no encoding was explicitly set with :meth:" +"`set_output_charset`." +msgstr "" + +#: ../Doc/library/gettext.rst:372 +msgid "" +"Do a plural-forms lookup of a message id. *singular* is used as the message " +"id for purposes of lookup in the catalog, while *n* is used to determine " +"which plural form to use. The returned message string is a Unicode string." +msgstr "" + +#: ../Doc/library/gettext.rst:376 +msgid "" +"If the message id is not found in the catalog, and a fallback is specified, " +"the request is forwarded to the fallback's :meth:`ngettext` method. " +"Otherwise, when *n* is 1 *singular* is returned, and *plural* is returned in " +"all other cases." +msgstr "" + +#: ../Doc/library/gettext.rst:398 +msgid "Solaris message catalog support" +msgstr "" + +#: ../Doc/library/gettext.rst:400 +msgid "" +"The Solaris operating system defines its own binary :file:`.mo` file format, " +"but since no documentation can be found on this format, it is not supported " +"at this time." +msgstr "" + +#: ../Doc/library/gettext.rst:406 +msgid "The Catalog constructor" +msgstr "" + +#: ../Doc/library/gettext.rst:410 +msgid "" +"GNOME uses a version of the :mod:`gettext` module by James Henstridge, but " +"this version has a slightly different API. Its documented usage was::" +msgstr "" + +#: ../Doc/library/gettext.rst:418 +msgid "" +"For compatibility with this older module, the function :func:`Catalog` is an " +"alias for the :func:`translation` function described above." +msgstr "" + +#: ../Doc/library/gettext.rst:421 +msgid "" +"One difference between this module and Henstridge's: his catalog objects " +"supported access through a mapping API, but this appears to be unused and so " +"is not currently supported." +msgstr "" + +#: ../Doc/library/gettext.rst:427 +msgid "Internationalizing your programs and modules" +msgstr "" + +#: ../Doc/library/gettext.rst:429 +msgid "" +"Internationalization (I18N) refers to the operation by which a program is " +"made aware of multiple languages. Localization (L10N) refers to the " +"adaptation of your program, once internationalized, to the local language " +"and cultural habits. In order to provide multilingual messages for your " +"Python programs, you need to take the following steps:" +msgstr "" + +#: ../Doc/library/gettext.rst:435 +msgid "" +"prepare your program or module by specially marking translatable strings" +msgstr "" + +#: ../Doc/library/gettext.rst:437 +msgid "" +"run a suite of tools over your marked files to generate raw messages catalogs" +msgstr "" + +#: ../Doc/library/gettext.rst:439 +msgid "create language specific translations of the message catalogs" +msgstr "" + +#: ../Doc/library/gettext.rst:441 +msgid "" +"use the :mod:`gettext` module so that message strings are properly translated" +msgstr "" + +#: ../Doc/library/gettext.rst:443 +msgid "" +"In order to prepare your code for I18N, you need to look at all the strings " +"in your files. Any string that needs to be translated should be marked by " +"wrapping it in ``_('...')`` --- that is, a call to the function :func:`_`. " +"For example::" +msgstr "" + +#: ../Doc/library/gettext.rst:453 +msgid "" +"In this example, the string ``'writing a log message'`` is marked as a " +"candidate for translation, while the strings ``'mylog.txt'`` and ``'w'`` are " +"not." +msgstr "" + +#: ../Doc/library/gettext.rst:456 +msgid "" +"There are a few tools to extract the strings meant for translation. The " +"original GNU :program:`gettext` only supported C or C++ source code but its " +"extended version :program:`xgettext` scans code written in a number of " +"languages, including Python, to find strings marked as translatable. `Babel " +"`__ is a Python internationalization library that " +"includes a :file:`pybabel` script to extract and compile message catalogs. " +"François Pinard's program called :program:`xpot` does a similar job and is " +"available as part of his `po-utils package `__." +msgstr "" + +#: ../Doc/library/gettext.rst:466 +msgid "" +"(Python also includes pure-Python versions of these programs, called :" +"program:`pygettext.py` and :program:`msgfmt.py`; some Python distributions " +"will install them for you. :program:`pygettext.py` is similar to :program:" +"`xgettext`, but only understands Python source code and cannot handle other " +"programming languages such as C or C++. :program:`pygettext.py` supports a " +"command-line interface similar to :program:`xgettext`; for details on its " +"use, run ``pygettext.py --help``. :program:`msgfmt.py` is binary compatible " +"with GNU :program:`msgfmt`. With these two programs, you may not need the " +"GNU :program:`gettext` package to internationalize your Python applications.)" +msgstr "" + +#: ../Doc/library/gettext.rst:478 +msgid "" +":program:`xgettext`, :program:`pygettext`, and similar tools generate :file:" +"`.po` files that are message catalogs. They are structured human-readable " +"files that contain every marked string in the source code, along with a " +"placeholder for the translated versions of these strings." +msgstr "" + +#: ../Doc/library/gettext.rst:484 +msgid "" +"Copies of these :file:`.po` files are then handed over to the individual " +"human translators who write translations for every supported natural " +"language. They send back the completed language-specific versions as a :" +"file:`.po` file that's compiled into a machine-readable :file:" +"`.mo` binary catalog file using the :program:`msgfmt` program. The :file:`." +"mo` files are used by the :mod:`gettext` module for the actual translation " +"processing at run-time." +msgstr "" + +#: ../Doc/library/gettext.rst:493 +msgid "" +"How you use the :mod:`gettext` module in your code depends on whether you " +"are internationalizing a single module or your entire application. The next " +"two sections will discuss each case." +msgstr "" + +#: ../Doc/library/gettext.rst:499 +msgid "Localizing your module" +msgstr "" + +#: ../Doc/library/gettext.rst:501 +msgid "" +"If you are localizing your module, you must take care not to make global " +"changes, e.g. to the built-in namespace. You should not use the GNU " +"``gettext`` API but instead the class-based API." +msgstr "" + +#: ../Doc/library/gettext.rst:505 +msgid "" +"Let's say your module is called \"spam\" and the module's various natural " +"language translation :file:`.mo` files reside in :file:`/usr/share/locale` " +"in GNU :program:`gettext` format. Here's what you would put at the top of " +"your module::" +msgstr "" + +#: ../Doc/library/gettext.rst:516 +msgid "Localizing your application" +msgstr "" + +#: ../Doc/library/gettext.rst:518 +msgid "" +"If you are localizing your application, you can install the :func:`_` " +"function globally into the built-in namespace, usually in the main driver " +"file of your application. This will let all your application-specific files " +"just use ``_('...')`` without having to explicitly install it in each file." +msgstr "" + +#: ../Doc/library/gettext.rst:523 +msgid "" +"In the simple case then, you need only add the following bit of code to the " +"main driver file of your application::" +msgstr "" + +#: ../Doc/library/gettext.rst:529 +msgid "" +"If you need to set the locale directory, you can pass it into the :func:" +"`install` function::" +msgstr "" + +#: ../Doc/library/gettext.rst:537 +msgid "Changing languages on the fly" +msgstr "" + +#: ../Doc/library/gettext.rst:539 +msgid "" +"If your program needs to support many languages at the same time, you may " +"want to create multiple translation instances and then switch between them " +"explicitly, like so::" +msgstr "" + +#: ../Doc/library/gettext.rst:560 +msgid "Deferred translations" +msgstr "" + +#: ../Doc/library/gettext.rst:562 +msgid "" +"In most coding situations, strings are translated where they are coded. " +"Occasionally however, you need to mark strings for translation, but defer " +"actual translation until later. A classic example is::" +msgstr "" + +#: ../Doc/library/gettext.rst:575 +msgid "" +"Here, you want to mark the strings in the ``animals`` list as being " +"translatable, but you don't actually want to translate them until they are " +"printed." +msgstr "" + +#: ../Doc/library/gettext.rst:579 +msgid "Here is one way you can handle this situation::" +msgstr "" + +#: ../Doc/library/gettext.rst:595 +msgid "" +"This works because the dummy definition of :func:`_` simply returns the " +"string unchanged. And this dummy definition will temporarily override any " +"definition of :func:`_` in the built-in namespace (until the :keyword:`del` " +"command). Take care, though if you have a previous definition of :func:`_` " +"in the local namespace." +msgstr "" + +#: ../Doc/library/gettext.rst:601 +msgid "" +"Note that the second use of :func:`_` will not identify \"a\" as being " +"translatable to the :program:`gettext` program, because the parameter is not " +"a string literal." +msgstr "" + +#: ../Doc/library/gettext.rst:605 +msgid "Another way to handle this is with the following example::" +msgstr "" + +#: ../Doc/library/gettext.rst:619 +msgid "" +"In this case, you are marking translatable strings with the function :func:" +"`N_`, which won't conflict with any definition of :func:`_`. However, you " +"will need to teach your message extraction program to look for translatable " +"strings marked with :func:`N_`. :program:`xgettext`, :program:`pygettext`, " +"``pybabel extract``, and :program:`xpot` all support this through the use of " +"the :option:`-k` command-line switch. The choice of :func:`N_` here is " +"totally arbitrary; it could have just as easily been :func:" +"`MarkThisStringForTranslation`." +msgstr "" + +#: ../Doc/library/gettext.rst:630 +msgid "Acknowledgements" +msgstr "" + +#: ../Doc/library/gettext.rst:632 +msgid "" +"The following people contributed code, feedback, design suggestions, " +"previous implementations, and valuable experience to the creation of this " +"module:" +msgstr "" + +#: ../Doc/library/gettext.rst:635 +msgid "Peter Funk" +msgstr "" + +#: ../Doc/library/gettext.rst:637 +msgid "James Henstridge" +msgstr "" + +#: ../Doc/library/gettext.rst:639 +msgid "Juan David Ibáñez Palomar" +msgstr "" + +#: ../Doc/library/gettext.rst:641 +msgid "Marc-André Lemburg" +msgstr "" + +#: ../Doc/library/gettext.rst:643 +msgid "Martin von Löwis" +msgstr "" + +#: ../Doc/library/gettext.rst:645 +msgid "François Pinard" +msgstr "" + +#: ../Doc/library/gettext.rst:647 +msgid "Barry Warsaw" +msgstr "" + +#: ../Doc/library/gettext.rst:649 +msgid "Gustavo Niemeyer" +msgstr "" + +#: ../Doc/library/gettext.rst:653 +msgid "" +"The default locale directory is system dependent; for example, on RedHat " +"Linux it is :file:`/usr/share/locale`, but on Solaris it is :file:`/usr/lib/" +"locale`. The :mod:`gettext` module does not try to support these system " +"dependent defaults; instead its default is :file:`sys.prefix/share/locale`. " +"For this reason, it is always best to call :func:`bindtextdomain` with an " +"explicit absolute path at the start of your application." +msgstr "" + +#: ../Doc/library/gettext.rst:660 +msgid "See the footnote for :func:`bindtextdomain` above." +msgstr "" + +#: ../Doc/library/glob.rst:2 +msgid ":mod:`glob` --- Unix style pathname pattern expansion" +msgstr "" + +#: ../Doc/library/glob.rst:7 +msgid "**Source code:** :source:`Lib/glob.py`" +msgstr "" + +#: ../Doc/library/glob.rst:13 +msgid "" +"The :mod:`glob` module finds all the pathnames matching a specified pattern " +"according to the rules used by the Unix shell, although results are returned " +"in arbitrary order. No tilde expansion is done, but ``*``, ``?``, and " +"character ranges expressed with ``[]`` will be correctly matched. This is " +"done by using the :func:`os.scandir` and :func:`fnmatch.fnmatch` functions " +"in concert, and not by actually invoking a subshell. Note that unlike :func:" +"`fnmatch.fnmatch`, :mod:`glob` treats filenames beginning with a dot (``.``) " +"as special cases. (For tilde and shell variable expansion, use :func:`os." +"path.expanduser` and :func:`os.path.expandvars`.)" +msgstr "" + +#: ../Doc/library/glob.rst:28 ../Doc/library/os.path.rst:33 +msgid "The :mod:`pathlib` module offers high-level path objects." +msgstr "" + +#: ../Doc/library/glob.rst:33 +msgid "" +"Return a possibly-empty list of path names that match *pathname*, which must " +"be a string containing a path specification. *pathname* can be either " +"absolute (like :file:`/usr/src/Python-1.5/Makefile`) or relative (like :file:" +"`../../Tools/\\*/\\*.gif`), and can contain shell-style wildcards. Broken " +"symlinks are included in the results (as in the shell)." +msgstr "" + +#: ../Doc/library/glob.rst:39 +msgid "" +"If *recursive* is true, the pattern \"``**``\" will match any files and zero " +"or more directories and subdirectories. If the pattern is followed by an " +"``os.sep``, only directories and subdirectories match." +msgstr "" + +#: ../Doc/library/glob.rst:44 ../Doc/library/pathlib.rst:730 +msgid "" +"Using the \"``**``\" pattern in large directory trees may consume an " +"inordinate amount of time." +msgstr "" + +#: ../Doc/library/glob.rst:47 +msgid "Support for recursive globs using \"``**``\"." +msgstr "" + +#: ../Doc/library/glob.rst:53 +msgid "" +"Return an :term:`iterator` which yields the same values as :func:`glob` " +"without actually storing them all simultaneously." +msgstr "" + +#: ../Doc/library/glob.rst:59 +msgid "" +"Escape all special characters (``'?'``, ``'*'`` and ``'['``). This is useful " +"if you want to match an arbitrary literal string that may have special " +"characters in it. Special characters in drive/UNC sharepoints are not " +"escaped, e.g. on Windows ``escape('//?/c:/Quo vadis?.txt')`` returns ``'//?/" +"c:/Quo vadis[?].txt'``." +msgstr "" + +#: ../Doc/library/glob.rst:68 +msgid "" +"For example, consider a directory containing the following files: :file:`1." +"gif`, :file:`2.txt`, :file:`card.gif` and a subdirectory :file:`sub` which " +"contains only the file :file:`3.txt`. :func:`glob` will produce the " +"following results. Notice how any leading components of the path are " +"preserved. ::" +msgstr "" + +#: ../Doc/library/glob.rst:86 +msgid "" +"If the directory contains files starting with ``.`` they won't be matched by " +"default. For example, consider a directory containing :file:`card.gif` and :" +"file:`.card.gif`::" +msgstr "" + +#: ../Doc/library/glob.rst:98 +msgid "Module :mod:`fnmatch`" +msgstr "" + +#: ../Doc/library/glob.rst:99 +msgid "Shell-style filename (not path) expansion" +msgstr "" + +#: ../Doc/library/grp.rst:2 +msgid ":mod:`grp` --- The group database" +msgstr "" + +#: ../Doc/library/grp.rst:10 +msgid "" +"This module provides access to the Unix group database. It is available on " +"all Unix versions." +msgstr "" + +#: ../Doc/library/grp.rst:13 +msgid "" +"Group database entries are reported as a tuple-like object, whose attributes " +"correspond to the members of the ``group`` structure (Attribute field below, " +"see ````):" +msgstr "" + +#: ../Doc/library/grp.rst:18 ../Doc/library/pwd.rst:18 +#: ../Doc/library/resource.rst:279 ../Doc/library/spwd.rst:21 +#: ../Doc/library/time.rst:536 ../Doc/library/tkinter.rst:430 +#: ../Doc/library/urllib.parse.rst:92 ../Doc/library/urllib.parse.rst:213 +#: ../Doc/library/urllib.parse.rst:298 ../Doc/library/winreg.rst:210 +#: ../Doc/library/winreg.rst:317 ../Doc/library/winreg.rst:361 +#: ../Doc/library/zipfile.rst:539 +msgid "Index" +msgstr "" + +#: ../Doc/library/grp.rst:20 +msgid "gr_name" +msgstr "" + +#: ../Doc/library/grp.rst:20 +msgid "the name of the group" +msgstr "" + +#: ../Doc/library/grp.rst:22 +msgid "gr_passwd" +msgstr "" + +#: ../Doc/library/grp.rst:22 +msgid "the (encrypted) group password; often empty" +msgstr "" + +#: ../Doc/library/grp.rst:25 +msgid "gr_gid" +msgstr "" + +#: ../Doc/library/grp.rst:25 +msgid "the numerical group ID" +msgstr "" + +#: ../Doc/library/grp.rst:27 ../Doc/library/pwd.rst:26 +#: ../Doc/library/spwd.rst:29 ../Doc/library/time.rst:544 +#: ../Doc/library/tkinter.rst:439 ../Doc/library/urllib.parse.rst:100 +#: ../Doc/library/urllib.parse.rst:221 +msgid "3" +msgstr "" + +#: ../Doc/library/grp.rst:27 +msgid "gr_mem" +msgstr "" + +#: ../Doc/library/grp.rst:27 +msgid "all the group member's user names" +msgstr "" + +#: ../Doc/library/grp.rst:31 +msgid "" +"The gid is an integer, name and password are strings, and the member list is " +"a list of strings. (Note that most users are not explicitly listed as " +"members of the group they are in according to the password database. Check " +"both databases to get complete membership information. Also note that a " +"``gr_name`` that starts with a ``+`` or ``-`` is likely to be a YP/NIS " +"reference and may not be accessible via :func:`getgrnam` or :func:" +"`getgrgid`.)" +msgstr "" + +#: ../Doc/library/grp.rst:38 ../Doc/library/pwd.rst:51 +msgid "It defines the following items:" +msgstr "" + +#: ../Doc/library/grp.rst:43 +msgid "" +"Return the group database entry for the given numeric group ID. :exc:" +"`KeyError` is raised if the entry asked for cannot be found." +msgstr "" + +#: ../Doc/library/grp.rst:46 +msgid "" +"Since Python 3.6 the support of non-integer arguments like floats or strings " +"in :func:`getgrgid` is deprecated." +msgstr "" + +#: ../Doc/library/grp.rst:52 +msgid "" +"Return the group database entry for the given group name. :exc:`KeyError` is " +"raised if the entry asked for cannot be found." +msgstr "" + +#: ../Doc/library/grp.rst:58 +msgid "Return a list of all available group entries, in arbitrary order." +msgstr "" + +#: ../Doc/library/grp.rst:64 ../Doc/library/spwd.rst:73 +msgid "Module :mod:`pwd`" +msgstr "" + +#: ../Doc/library/grp.rst:64 +msgid "An interface to the user database, similar to this." +msgstr "" + +#: ../Doc/library/grp.rst:66 ../Doc/library/pwd.rst:74 +msgid "Module :mod:`spwd`" +msgstr "" + +#: ../Doc/library/grp.rst:67 ../Doc/library/pwd.rst:75 +msgid "An interface to the shadow password database, similar to this." +msgstr "" + +#: ../Doc/library/gzip.rst:2 +msgid ":mod:`gzip` --- Support for :program:`gzip` files" +msgstr "" + +#: ../Doc/library/gzip.rst:7 +msgid "**Source code:** :source:`Lib/gzip.py`" +msgstr "" + +#: ../Doc/library/gzip.rst:11 +msgid "" +"This module provides a simple interface to compress and decompress files " +"just like the GNU programs :program:`gzip` and :program:`gunzip` would." +msgstr "" + +#: ../Doc/library/gzip.rst:14 +msgid "The data compression is provided by the :mod:`zlib` module." +msgstr "" + +#: ../Doc/library/gzip.rst:16 +msgid "" +"The :mod:`gzip` module provides the :class:`GzipFile` class, as well as the :" +"func:`.open`, :func:`compress` and :func:`decompress` convenience functions. " +"The :class:`GzipFile` class reads and writes :program:`gzip`\\ -format " +"files, automatically compressing or decompressing the data so that it looks " +"like an ordinary :term:`file object`." +msgstr "" + +#: ../Doc/library/gzip.rst:22 +msgid "" +"Note that additional file formats which can be decompressed by the :program:" +"`gzip` and :program:`gunzip` programs, such as those produced by :program:" +"`compress` and :program:`pack`, are not supported by this module." +msgstr "" + +#: ../Doc/library/gzip.rst:31 +msgid "" +"Open a gzip-compressed file in binary or text mode, returning a :term:`file " +"object`." +msgstr "" + +#: ../Doc/library/gzip.rst:34 +msgid "" +"The *filename* argument can be an actual filename (a :class:`str` or :class:" +"`bytes` object), or an existing file object to read from or write to." +msgstr "" + +#: ../Doc/library/gzip.rst:37 +msgid "" +"The *mode* argument can be any of ``'r'``, ``'rb'``, ``'a'``, ``'ab'``, " +"``'w'``, ``'wb'``, ``'x'`` or ``'xb'`` for binary mode, or ``'rt'``, " +"``'at'``, ``'wt'``, or ``'xt'`` for text mode. The default is ``'rb'``." +msgstr "" + +#: ../Doc/library/gzip.rst:41 +msgid "" +"The *compresslevel* argument is an integer from 0 to 9, as for the :class:" +"`GzipFile` constructor." +msgstr "" + +#: ../Doc/library/gzip.rst:44 +msgid "" +"For binary mode, this function is equivalent to the :class:`GzipFile` " +"constructor: ``GzipFile(filename, mode, compresslevel)``. In this case, the " +"*encoding*, *errors* and *newline* arguments must not be provided." +msgstr "" + +#: ../Doc/library/gzip.rst:48 +msgid "" +"For text mode, a :class:`GzipFile` object is created, and wrapped in an :" +"class:`io.TextIOWrapper` instance with the specified encoding, error " +"handling behavior, and line ending(s)." +msgstr "" + +#: ../Doc/library/gzip.rst:52 +msgid "" +"Added support for *filename* being a file object, support for text mode, and " +"the *encoding*, *errors* and *newline* arguments." +msgstr "" + +#: ../Doc/library/gzip.rst:56 +msgid "Added support for the ``'x'``, ``'xb'`` and ``'xt'`` modes." +msgstr "" + +#: ../Doc/library/gzip.rst:64 +msgid "" +"Constructor for the :class:`GzipFile` class, which simulates most of the " +"methods of a :term:`file object`, with the exception of the :meth:`truncate` " +"method. At least one of *fileobj* and *filename* must be given a non-" +"trivial value." +msgstr "" + +#: ../Doc/library/gzip.rst:69 +msgid "" +"The new class instance is based on *fileobj*, which can be a regular file, " +"an :class:`io.BytesIO` object, or any other object which simulates a file. " +"It defaults to ``None``, in which case *filename* is opened to provide a " +"file object." +msgstr "" + +#: ../Doc/library/gzip.rst:74 +msgid "" +"When *fileobj* is not ``None``, the *filename* argument is only used to be " +"included in the :program:`gzip` file header, which may include the original " +"filename of the uncompressed file. It defaults to the filename of " +"*fileobj*, if discernible; otherwise, it defaults to the empty string, and " +"in this case the original filename is not included in the header." +msgstr "" + +#: ../Doc/library/gzip.rst:80 +msgid "" +"The *mode* argument can be any of ``'r'``, ``'rb'``, ``'a'``, ``'ab'``, " +"``'w'``, ``'wb'``, ``'x'``, or ``'xb'``, depending on whether the file will " +"be read or written. The default is the mode of *fileobj* if discernible; " +"otherwise, the default is ``'rb'``." +msgstr "" + +#: ../Doc/library/gzip.rst:85 +msgid "" +"Note that the file is always opened in binary mode. To open a compressed " +"file in text mode, use :func:`.open` (or wrap your :class:`GzipFile` with " +"an :class:`io.TextIOWrapper`)." +msgstr "" + +#: ../Doc/library/gzip.rst:89 +msgid "" +"The *compresslevel* argument is an integer from ``0`` to ``9`` controlling " +"the level of compression; ``1`` is fastest and produces the least " +"compression, and ``9`` is slowest and produces the most compression. ``0`` " +"is no compression. The default is ``9``." +msgstr "" + +#: ../Doc/library/gzip.rst:94 +msgid "" +"The *mtime* argument is an optional numeric timestamp to be written to the " +"last modification time field in the stream when compressing. It should only " +"be provided in compression mode. If omitted or ``None``, the current time " +"is used. See the :attr:`mtime` attribute for more details." +msgstr "" + +#: ../Doc/library/gzip.rst:99 +msgid "" +"Calling a :class:`GzipFile` object's :meth:`close` method does not close " +"*fileobj*, since you might wish to append more material after the compressed " +"data. This also allows you to pass an :class:`io.BytesIO` object opened for " +"writing as *fileobj*, and retrieve the resulting memory buffer using the :" +"class:`io.BytesIO` object's :meth:`~io.BytesIO.getvalue` method." +msgstr "" + +#: ../Doc/library/gzip.rst:105 +msgid "" +":class:`GzipFile` supports the :class:`io.BufferedIOBase` interface, " +"including iteration and the :keyword:`with` statement. Only the :meth:" +"`truncate` method isn't implemented." +msgstr "" + +#: ../Doc/library/gzip.rst:109 +msgid ":class:`GzipFile` also provides the following method and attribute:" +msgstr "" + +#: ../Doc/library/gzip.rst:113 +msgid "" +"Read *n* uncompressed bytes without advancing the file position. At most one " +"single read on the compressed stream is done to satisfy the call. The " +"number of bytes returned may be more or less than requested." +msgstr "" + +#: ../Doc/library/gzip.rst:118 +msgid "" +"While calling :meth:`peek` does not change the file position of the :class:" +"`GzipFile`, it may change the position of the underlying file object (e.g. " +"if the :class:`GzipFile` was constructed with the *fileobj* parameter)." +msgstr "" + +#: ../Doc/library/gzip.rst:127 +msgid "" +"When decompressing, the value of the last modification time field in the " +"most recently read header may be read from this attribute, as an integer. " +"The initial value before reading any headers is ``None``." +msgstr "" + +#: ../Doc/library/gzip.rst:131 +msgid "" +"All :program:`gzip` compressed streams are required to contain this " +"timestamp field. Some programs, such as :program:`gunzip`\\ , make use of " +"the timestamp. The format is the same as the return value of :func:`time." +"time` and the :attr:`~os.stat_result.st_mtime` attribute of the object " +"returned by :func:`os.stat`." +msgstr "" + +#: ../Doc/library/gzip.rst:137 +msgid "" +"Support for the :keyword:`with` statement was added, along with the *mtime* " +"constructor argument and :attr:`mtime` attribute." +msgstr "" + +#: ../Doc/library/gzip.rst:141 +msgid "Support for zero-padded and unseekable files was added." +msgstr "" + +#: ../Doc/library/gzip.rst:144 +msgid "The :meth:`io.BufferedIOBase.read1` method is now implemented." +msgstr "" + +#: ../Doc/library/gzip.rst:147 +msgid "Added support for the ``'x'`` and ``'xb'`` modes." +msgstr "" + +#: ../Doc/library/gzip.rst:150 +msgid "" +"Added support for writing arbitrary :term:`bytes-like objects `. The :meth:`~io.BufferedIOBase.read` method now accepts an argument " +"of ``None``." +msgstr "" + +#: ../Doc/library/gzip.rst:162 +msgid "" +"Compress the *data*, returning a :class:`bytes` object containing the " +"compressed data. *compresslevel* has the same meaning as in the :class:" +"`GzipFile` constructor above." +msgstr "" + +#: ../Doc/library/gzip.rst:170 +msgid "" +"Decompress the *data*, returning a :class:`bytes` object containing the " +"uncompressed data." +msgstr "" + +#: ../Doc/library/gzip.rst:179 +msgid "Examples of usage" +msgstr "" + +#: ../Doc/library/gzip.rst:181 +msgid "Example of how to read a compressed file::" +msgstr "" + +#: ../Doc/library/gzip.rst:187 +msgid "Example of how to create a compressed GZIP file::" +msgstr "" + +#: ../Doc/library/gzip.rst:194 +msgid "Example of how to GZIP compress an existing file::" +msgstr "" + +#: ../Doc/library/gzip.rst:202 +msgid "Example of how to GZIP compress a binary string::" +msgstr "" + +#: ../Doc/library/gzip.rst:211 +msgid "Module :mod:`zlib`" +msgstr "" + +#: ../Doc/library/gzip.rst:211 +msgid "" +"The basic data compression module needed to support the :program:`gzip` file " +"format." +msgstr "" + +#: ../Doc/library/hashlib.rst:2 +msgid ":mod:`hashlib` --- Secure hashes and message digests" +msgstr "" + +#: ../Doc/library/hashlib.rst:10 +msgid "**Source code:** :source:`Lib/hashlib.py`" +msgstr "" + +#: ../Doc/library/hashlib.rst:23 +msgid "" +"This module implements a common interface to many different secure hash and " +"message digest algorithms. Included are the FIPS secure hash algorithms " +"SHA1, SHA224, SHA256, SHA384, and SHA512 (defined in FIPS 180-2) as well as " +"RSA's MD5 algorithm (defined in Internet :rfc:`1321`). The terms \"secure " +"hash\" and \"message digest\" are interchangeable. Older algorithms were " +"called message digests. The modern term is secure hash." +msgstr "" + +#: ../Doc/library/hashlib.rst:32 +msgid "" +"If you want the adler32 or crc32 hash functions, they are available in the :" +"mod:`zlib` module." +msgstr "" + +#: ../Doc/library/hashlib.rst:37 +msgid "" +"Some algorithms have known hash collision weaknesses, refer to the \"See also" +"\" section at the end." +msgstr "" + +#: ../Doc/library/hashlib.rst:44 +msgid "Hash algorithms" +msgstr "" + +#: ../Doc/library/hashlib.rst:46 +msgid "" +"There is one constructor method named for each type of :dfn:`hash`. All " +"return a hash object with the same simple interface. For example: use :func:" +"`sha256` to create a SHA-256 hash object. You can now feed this object with :" +"term:`bytes-like objects ` (normally :class:`bytes`) " +"using the :meth:`update` method. At any point you can ask it for the :dfn:" +"`digest` of the concatenation of the data fed to it so far using the :meth:" +"`digest` or :meth:`hexdigest` methods." +msgstr "" + +#: ../Doc/library/hashlib.rst:56 +msgid "" +"For better multithreading performance, the Python :term:`GIL` is released " +"for data larger than 2047 bytes at object creation or on update." +msgstr "" + +#: ../Doc/library/hashlib.rst:61 +msgid "" +"Feeding string objects into :meth:`update` is not supported, as hashes work " +"on bytes, not on characters." +msgstr "" + +#: ../Doc/library/hashlib.rst:66 +msgid "" +"Constructors for hash algorithms that are always present in this module are :" +"func:`sha1`, :func:`sha224`, :func:`sha256`, :func:`sha384`, :func:" +"`sha512`, :func:`blake2b`, and :func:`blake2s`. :func:`md5` is normally " +"available as well, though it may be missing if you are using a rare \"FIPS " +"compliant\" build of Python. Additional algorithms may also be available " +"depending upon the OpenSSL library that Python uses on your platform. On " +"most platforms the :func:`sha3_224`, :func:`sha3_256`, :func:`sha3_384`, :" +"func:`sha3_512`, :func:`shake_128`, :func:`shake_256` are also available." +msgstr "" + +#: ../Doc/library/hashlib.rst:76 +msgid "" +"SHA3 (Keccak) and SHAKE constructors :func:`sha3_224`, :func:`sha3_256`, :" +"func:`sha3_384`, :func:`sha3_512`, :func:`shake_128`, :func:`shake_256`." +msgstr "" + +#: ../Doc/library/hashlib.rst:80 +msgid ":func:`blake2b` and :func:`blake2s` were added." +msgstr "" + +#: ../Doc/library/hashlib.rst:83 +msgid "" +"For example, to obtain the digest of the byte string ``b'Nobody inspects the " +"spammish repetition'``::" +msgstr "" + +#: ../Doc/library/hashlib.rst:97 +msgid "More condensed:" +msgstr "" + +#: ../Doc/library/hashlib.rst:104 +msgid "" +"Is a generic constructor that takes the string name of the desired algorithm " +"as its first parameter. It also exists to allow access to the above listed " +"hashes as well as any other algorithms that your OpenSSL library may offer. " +"The named constructors are much faster than :func:`new` and should be " +"preferred." +msgstr "" + +#: ../Doc/library/hashlib.rst:110 +msgid "Using :func:`new` with an algorithm provided by OpenSSL:" +msgstr "" + +#: ../Doc/library/hashlib.rst:117 +msgid "Hashlib provides the following constant attributes:" +msgstr "" + +#: ../Doc/library/hashlib.rst:121 +msgid "" +"A set containing the names of the hash algorithms guaranteed to be supported " +"by this module on all platforms. Note that 'md5' is in this list despite " +"some upstream vendors offering an odd \"FIPS compliant\" Python build that " +"excludes it." +msgstr "" + +#: ../Doc/library/hashlib.rst:130 +msgid "" +"A set containing the names of the hash algorithms that are available in the " +"running Python interpreter. These names will be recognized when passed to :" +"func:`new`. :attr:`algorithms_guaranteed` will always be a subset. The " +"same algorithm may appear multiple times in this set under different names " +"(thanks to OpenSSL)." +msgstr "" + +#: ../Doc/library/hashlib.rst:138 +msgid "" +"The following values are provided as constant attributes of the hash objects " +"returned by the constructors:" +msgstr "" + +#: ../Doc/library/hashlib.rst:144 +msgid "The size of the resulting hash in bytes." +msgstr "" + +#: ../Doc/library/hashlib.rst:148 ../Doc/library/hmac.rst:89 +msgid "The internal block size of the hash algorithm in bytes." +msgstr "" + +#: ../Doc/library/hashlib.rst:150 ../Doc/library/hmac.rst:81 +msgid "A hash object has the following attributes:" +msgstr "" + +#: ../Doc/library/hashlib.rst:154 +msgid "" +"The canonical name of this hash, always lowercase and always suitable as a " +"parameter to :func:`new` to create another hash of this type." +msgstr "" + +#: ../Doc/library/hashlib.rst:157 +msgid "" +"The name attribute has been present in CPython since its inception, but " +"until Python 3.4 was not formally specified, so may not exist on some " +"platforms." +msgstr "" + +#: ../Doc/library/hashlib.rst:162 +msgid "A hash object has the following methods:" +msgstr "" + +#: ../Doc/library/hashlib.rst:167 +msgid "" +"Update the hash object with the object *arg*, which must be interpretable as " +"a buffer of bytes. Repeated calls are equivalent to a single call with the " +"concatenation of all the arguments: ``m.update(a); m.update(b)`` is " +"equivalent to ``m.update(a+b)``." +msgstr "" + +#: ../Doc/library/hashlib.rst:172 +msgid "" +"The Python GIL is released to allow other threads to run while hash updates " +"on data larger than 2047 bytes is taking place when using hash algorithms " +"supplied by OpenSSL." +msgstr "" + +#: ../Doc/library/hashlib.rst:180 +msgid "" +"Return the digest of the data passed to the :meth:`update` method so far. " +"This is a bytes object of size :attr:`digest_size` which may contain bytes " +"in the whole range from 0 to 255." +msgstr "" + +#: ../Doc/library/hashlib.rst:187 ../Doc/library/hashlib.rst:215 +msgid "" +"Like :meth:`digest` except the digest is returned as a string object of " +"double length, containing only hexadecimal digits. This may be used to " +"exchange the value safely in email or other non-binary environments." +msgstr "" + +#: ../Doc/library/hashlib.rst:194 +msgid "" +"Return a copy (\"clone\") of the hash object. This can be used to " +"efficiently compute the digests of data sharing a common initial substring." +msgstr "" + +#: ../Doc/library/hashlib.rst:199 +msgid "SHAKE variable length digests" +msgstr "" + +#: ../Doc/library/hashlib.rst:201 +msgid "" +"The :func:`shake_128` and :func:`shake_256` algorithms provide variable " +"length digests with length_in_bits//2 up to 128 or 256 bits of security. As " +"such, their digest methods require a length. Maximum length is not limited " +"by the SHAKE algorithm." +msgstr "" + +#: ../Doc/library/hashlib.rst:208 +msgid "" +"Return the digest of the data passed to the :meth:`update` method so far. " +"This is a bytes object of size ``length`` which may contain bytes in the " +"whole range from 0 to 255." +msgstr "" + +#: ../Doc/library/hashlib.rst:221 +msgid "Key derivation" +msgstr "" + +#: ../Doc/library/hashlib.rst:223 +msgid "" +"Key derivation and key stretching algorithms are designed for secure " +"password hashing. Naive algorithms such as ``sha1(password)`` are not " +"resistant against brute-force attacks. A good password hashing function must " +"be tunable, slow, and include a `salt `_." +msgstr "" + +#: ../Doc/library/hashlib.rst:231 +msgid "" +"The function provides PKCS#5 password-based key derivation function 2. It " +"uses HMAC as pseudorandom function." +msgstr "" + +#: ../Doc/library/hashlib.rst:234 +msgid "" +"The string *hash_name* is the desired name of the hash digest algorithm for " +"HMAC, e.g. 'sha1' or 'sha256'. *password* and *salt* are interpreted as " +"buffers of bytes. Applications and libraries should limit *password* to a " +"sensible length (e.g. 1024). *salt* should be about 16 or more bytes from a " +"proper source, e.g. :func:`os.urandom`." +msgstr "" + +#: ../Doc/library/hashlib.rst:240 +msgid "" +"The number of *iterations* should be chosen based on the hash algorithm and " +"computing power. As of 2013, at least 100,000 iterations of SHA-256 are " +"suggested." +msgstr "" + +#: ../Doc/library/hashlib.rst:244 +msgid "" +"*dklen* is the length of the derived key. If *dklen* is ``None`` then the " +"digest size of the hash algorithm *hash_name* is used, e.g. 64 for SHA-512." +msgstr "" + +#: ../Doc/library/hashlib.rst:256 +msgid "" +"A fast implementation of *pbkdf2_hmac* is available with OpenSSL. The " +"Python implementation uses an inline version of :mod:`hmac`. It is about " +"three times slower and doesn't release the GIL." +msgstr "" + +#: ../Doc/library/hashlib.rst:262 +msgid "" +"The function provides scrypt password-based key derivation function as " +"defined in :rfc:`7914`." +msgstr "" + +#: ../Doc/library/hashlib.rst:265 +msgid "" +"*password* and *salt* must be bytes-like objects. Applications and libraries " +"should limit *password* to a sensible length (e.g. 1024). *salt* should be " +"about 16 or more bytes from a proper source, e.g. :func:`os.urandom`." +msgstr "" + +#: ../Doc/library/hashlib.rst:269 +msgid "" +"*n* is the CPU/Memory cost factor, *r* the block size, *p* parallelization " +"factor and *maxmem* limits memory (OpenSSL 1.1.0 defaults to 32 MB). *dklen* " +"is the length of the derived key." +msgstr "" + +#: ../Doc/library/hashlib.rst:273 +msgid "Availability: OpenSSL 1.1+" +msgstr "" + +#: ../Doc/library/hashlib.rst:279 +msgid "BLAKE2" +msgstr "" + +#: ../Doc/library/hashlib.rst:281 +msgid "BLAKE2 takes additional arguments, see :ref:`hashlib-blake2`." +msgstr "" + +#: ../Doc/library/hashlib.rst:287 +msgid "Module :mod:`hmac`" +msgstr "" + +#: ../Doc/library/hashlib.rst:287 +msgid "A module to generate message authentication codes using hashes." +msgstr "" + +#: ../Doc/library/hashlib.rst:290 +msgid "Another way to encode binary hashes for non-binary environments." +msgstr "" + +#: ../Doc/library/hashlib.rst:292 +msgid "See :ref:`hashlib-blake2`." +msgstr "" + +#: ../Doc/library/hashlib.rst:295 +msgid "http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf" +msgstr "" + +#: ../Doc/library/hashlib.rst:295 +msgid "The FIPS 180-2 publication on Secure Hash Algorithms." +msgstr "" + +#: ../Doc/library/hashlib.rst:299 +msgid "" +"https://en.wikipedia.org/wiki/" +"Cryptographic_hash_function#Cryptographic_hash_algorithms" +msgstr "" + +#: ../Doc/library/hashlib.rst:298 +msgid "" +"Wikipedia article with information on which algorithms have known issues and " +"what that means regarding their use." +msgstr "" + +#: ../Doc/library/hashlib.rst:301 +msgid "https://www.ietf.org/rfc/rfc2898.txt" +msgstr "" + +#: ../Doc/library/hashlib.rst:302 +msgid "PKCS #5: Password-Based Cryptography Specification Version 2.0" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:4 +msgid ":mod:`hashlib` --- BLAKE2 hash functions" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:13 +msgid "" +"BLAKE2_ is a cryptographic hash function defined in RFC-7693_ that comes in " +"two flavors:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:16 +msgid "" +"**BLAKE2b**, optimized for 64-bit platforms and produces digests of any size " +"between 1 and 64 bytes," +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:19 +msgid "" +"**BLAKE2s**, optimized for 8- to 32-bit platforms and produces digests of " +"any size between 1 and 32 bytes." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:22 +msgid "" +"BLAKE2 supports **keyed mode** (a faster and simpler replacement for HMAC_), " +"**salted hashing**, **personalization**, and **tree hashing**." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:25 +msgid "" +"Hash objects from this module follow the API of standard library's :mod:" +"`hashlib` objects." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:30 +msgid "Module" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:33 +msgid "Creating hash objects" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:35 +msgid "New hash objects are created by calling constructor functions:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:47 +msgid "" +"These functions return the corresponding hash objects for calculating " +"BLAKE2b or BLAKE2s. They optionally take these general parameters:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:50 +msgid "" +"*data*: initial chunk of data to hash, which must be interpretable as buffer " +"of bytes." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:53 +msgid "*digest_size*: size of output digest in bytes." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:55 +msgid "" +"*key*: key for keyed hashing (up to 64 bytes for BLAKE2b, up to 32 bytes for " +"BLAKE2s)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:58 +msgid "" +"*salt*: salt for randomized hashing (up to 16 bytes for BLAKE2b, up to 8 " +"bytes for BLAKE2s)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:61 +msgid "" +"*person*: personalization string (up to 16 bytes for BLAKE2b, up to 8 bytes " +"for BLAKE2s)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:64 +msgid "The following table shows limits for general parameters (in bytes):" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:67 +msgid "Hash" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:67 +msgid "digest_size" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:67 +msgid "len(key)" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:67 +msgid "len(salt)" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:67 +msgid "len(person)" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:69 +msgid "BLAKE2b" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:69 +msgid "64" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:69 +msgid "16" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:70 +msgid "BLAKE2s" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:70 +msgid "32" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:75 +msgid "" +"BLAKE2 specification defines constant lengths for salt and personalization " +"parameters, however, for convenience, this implementation accepts byte " +"strings of any size up to the specified length. If the length of the " +"parameter is less than specified, it is padded with zeros, thus, for " +"example, ``b'salt'`` and ``b'salt\\x00'`` is the same value. (This is not " +"the case for *key*.)" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:82 +msgid "These sizes are available as module `constants`_ described below." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:84 +msgid "" +"Constructor functions also accept the following tree hashing parameters:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:86 +msgid "*fanout*: fanout (0 to 255, 0 if unlimited, 1 in sequential mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:88 +msgid "" +"*depth*: maximal depth of tree (1 to 255, 255 if unlimited, 1 in sequential " +"mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:91 +msgid "" +"*leaf_size*: maximal byte length of leaf (0 to 2**32-1, 0 if unlimited or in " +"sequential mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:94 +msgid "" +"*node_offset*: node offset (0 to 2**64-1 for BLAKE2b, 0 to 2**48-1 for " +"BLAKE2s, 0 for the first, leftmost, leaf, or in sequential mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:97 +msgid "" +"*node_depth*: node depth (0 to 255, 0 for leaves, or in sequential mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:99 +msgid "" +"*inner_size*: inner digest size (0 to 64 for BLAKE2b, 0 to 32 for BLAKE2s, 0 " +"in sequential mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:102 +msgid "" +"*last_node*: boolean indicating whether the processed node is the last one " +"(`False` for sequential mode)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:108 +msgid "" +"See section 2.10 in `BLAKE2 specification `_ for comprehensive review of tree hashing." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:119 +msgid "Salt length (maximum length accepted by constructors)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:125 +msgid "" +"Personalization string length (maximum length accepted by constructors)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:131 +msgid "Maximum key size." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:137 +msgid "Maximum digest size that the hash function can output." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:144 +msgid "Simple hashing" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:146 +msgid "" +"To calculate hash of some data, you should first construct a hash object by " +"calling the appropriate constructor function (:func:`blake2b` or :func:" +"`blake2s`), then update it with the data by calling :meth:`update` on the " +"object, and, finally, get the digest out of the object by calling :meth:" +"`digest` (or :meth:`hexdigest` for hex-encoded string)." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:159 +msgid "" +"As a shortcut, you can pass the first chunk of data to update directly to " +"the constructor as the first argument (or as *data* keyword argument):" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:166 +msgid "" +"You can call :meth:`hash.update` as many times as you need to iteratively " +"update the hash:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:179 +msgid "Using different digest sizes" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:181 +msgid "" +"BLAKE2 has configurable size of digests up to 64 bytes for BLAKE2b and up to " +"32 bytes for BLAKE2s. For example, to replace SHA-1 with BLAKE2b without " +"changing the size of output, we can tell BLAKE2b to produce 20-byte digests:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:195 +msgid "" +"Hash objects with different digest sizes have completely different outputs " +"(shorter hashes are *not* prefixes of longer hashes); BLAKE2b and BLAKE2s " +"produce different outputs even if the output length is the same:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:211 +msgid "Keyed hashing" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:213 +msgid "" +"Keyed hashing can be used for authentication as a faster and simpler " +"replacement for `Hash-based message authentication code `_ (HMAC). BLAKE2 can be " +"securely used in prefix-MAC mode thanks to the indifferentiability property " +"inherited from BLAKE." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:219 +msgid "" +"This example shows how to get a (hex-encoded) 128-bit authentication code " +"for message ``b'message data'`` with key ``b'pseudorandom key'``::" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:229 +msgid "" +"As a practical example, a web application can symmetrically sign cookies " +"sent to users and later verify them to make sure they weren't tampered with::" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:253 +msgid "" +"Even though there's a native keyed hashing mode, BLAKE2 can, of course, be " +"used in HMAC construction with :mod:`hmac` module::" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:264 +msgid "Randomized hashing" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:266 +msgid "" +"By setting *salt* parameter users can introduce randomization to the hash " +"function. Randomized hashing is useful for protecting against collision " +"attacks on the hash function used in digital signatures." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:270 +msgid "" +"Randomized hashing is designed for situations where one party, the message " +"preparer, generates all or part of a message to be signed by a second party, " +"the message signer. If the message preparer is able to find cryptographic " +"hash function collisions (i.e., two messages producing the same hash value), " +"then she might prepare meaningful versions of the message that would produce " +"the same hash value and digital signature, but with different results (e.g., " +"transferring $1,000,000 to an account, rather than $10). Cryptographic hash " +"functions have been designed with collision resistance as a major goal, but " +"the current concentration on attacking cryptographic hash functions may " +"result in a given cryptographic hash function providing less collision " +"resistance than expected. Randomized hashing offers the signer additional " +"protection by reducing the likelihood that a preparer can generate two or " +"more messages that ultimately yield the same hash value during the digital " +"signature generation process – even if it is practical to find collisions " +"for the hash function. However, the use of randomized hashing may reduce the " +"amount of security provided by a digital signature when all portions of the " +"message are prepared by the signer." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:289 +msgid "" +"(`NIST SP-800-106 \"Randomized Hashing for Digital Signatures\" `_)" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:292 +msgid "" +"In BLAKE2 the salt is processed as a one-time input to the hash function " +"during initialization, rather than as an input to each compression function." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:297 +msgid "" +"*Salted hashing* (or just hashing) with BLAKE2 or any other general-purpose " +"cryptographic hash function, such as SHA-256, is not suitable for hashing " +"passwords. See `BLAKE2 FAQ `_ for more information." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:320 +msgid "Personalization" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:322 +msgid "" +"Sometimes it is useful to force hash function to produce different digests " +"for the same input for different purposes. Quoting the authors of the Skein " +"hash function:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:326 +msgid "" +"We recommend that all application designers seriously consider doing this; " +"we have seen many protocols where a hash that is computed in one part of the " +"protocol can be used in an entirely different part because two hash " +"computations were done on similar or related data, and the attacker can " +"force the application to make the hash inputs the same. Personalizing each " +"hash function used in the protocol summarily stops this type of attack." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:333 +msgid "" +"(`The Skein Hash Function Family `_, p. 21)" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:337 +msgid "BLAKE2 can be personalized by passing bytes to the *person* argument::" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:351 +msgid "" +"Personalization together with the keyed mode can also be used to derive " +"different keys from a single one." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:365 +msgid "Tree mode" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:367 +msgid "Here's an example of hashing a minimal tree with two leaf nodes::" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:373 +msgid "" +"This example uses 64-byte internal digests, and returns the 32-byte final " +"digest::" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:403 +msgid "Credits" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:405 +msgid "" +"BLAKE2_ was designed by *Jean-Philippe Aumasson*, *Samuel Neves*, *Zooko " +"Wilcox-O'Hearn*, and *Christian Winnerlein* based on SHA-3_ finalist BLAKE_ " +"created by *Jean-Philippe Aumasson*, *Luca Henzen*, *Willi Meier*, and " +"*Raphael C.-W. Phan*." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:410 +msgid "" +"It uses core algorithm from ChaCha_ cipher designed by *Daniel J. " +"Bernstein*." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:412 +msgid "" +"The stdlib implementation is based on pyblake2_ module. It was written by " +"*Dmitry Chestnykh* based on C implementation written by *Samuel Neves*. The " +"documentation was copied from pyblake2_ and written by *Dmitry Chestnykh*." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:416 +msgid "The C code was partly rewritten for Python by *Christian Heimes*." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:418 +msgid "" +"The following public domain dedication applies for both C hash function " +"implementation, extension code, and this documentation:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:421 +msgid "" +"To the extent possible under law, the author(s) have dedicated all copyright " +"and related and neighboring rights to this software to the public domain " +"worldwide. This software is distributed without any warranty." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:425 +msgid "" +"You should have received a copy of the CC0 Public Domain Dedication along " +"with this software. If not, see http://creativecommons.org/publicdomain/" +"zero/1.0/." +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:429 +msgid "" +"The following people have helped with development or contributed their " +"changes to the project and the public domain according to the Creative " +"Commons Public Domain Dedication 1.0 Universal:" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:433 +msgid "*Alexandr Sokolovskiy*" +msgstr "" + +#: ../Doc/library/hashlib-blake2.rst:435 +msgid "Official BLAKE2 website: https://blake2.net" +msgstr "" + +#: ../Doc/library/heapq.rst:2 +msgid ":mod:`heapq` --- Heap queue algorithm" +msgstr "" + +#: ../Doc/library/heapq.rst:12 +msgid "**Source code:** :source:`Lib/heapq.py`" +msgstr "" + +#: ../Doc/library/heapq.rst:16 +msgid "" +"This module provides an implementation of the heap queue algorithm, also " +"known as the priority queue algorithm." +msgstr "" + +#: ../Doc/library/heapq.rst:19 +msgid "" +"Heaps are binary trees for which every parent node has a value less than or " +"equal to any of its children. This implementation uses arrays for which " +"``heap[k] <= heap[2*k+1]`` and ``heap[k] <= heap[2*k+2]`` for all *k*, " +"counting elements from zero. For the sake of comparison, non-existing " +"elements are considered to be infinite. The interesting property of a heap " +"is that its smallest element is always the root, ``heap[0]``." +msgstr "" + +#: ../Doc/library/heapq.rst:26 +msgid "" +"The API below differs from textbook heap algorithms in two aspects: (a) We " +"use zero-based indexing. This makes the relationship between the index for " +"a node and the indexes for its children slightly less obvious, but is more " +"suitable since Python uses zero-based indexing. (b) Our pop method returns " +"the smallest item, not the largest (called a \"min heap\" in textbooks; a " +"\"max heap\" is more common in texts because of its suitability for in-place " +"sorting)." +msgstr "" + +#: ../Doc/library/heapq.rst:33 +msgid "" +"These two make it possible to view the heap as a regular Python list without " +"surprises: ``heap[0]`` is the smallest item, and ``heap.sort()`` maintains " +"the heap invariant!" +msgstr "" + +#: ../Doc/library/heapq.rst:37 +msgid "" +"To create a heap, use a list initialized to ``[]``, or you can transform a " +"populated list into a heap via function :func:`heapify`." +msgstr "" + +#: ../Doc/library/heapq.rst:45 +msgid "Push the value *item* onto the *heap*, maintaining the heap invariant." +msgstr "" + +#: ../Doc/library/heapq.rst:50 +msgid "" +"Pop and return the smallest item from the *heap*, maintaining the heap " +"invariant. If the heap is empty, :exc:`IndexError` is raised. To access " +"the smallest item without popping it, use ``heap[0]``." +msgstr "" + +#: ../Doc/library/heapq.rst:57 +msgid "" +"Push *item* on the heap, then pop and return the smallest item from the " +"*heap*. The combined action runs more efficiently than :func:`heappush` " +"followed by a separate call to :func:`heappop`." +msgstr "" + +#: ../Doc/library/heapq.rst:64 +msgid "Transform list *x* into a heap, in-place, in linear time." +msgstr "" + +#: ../Doc/library/heapq.rst:69 +msgid "" +"Pop and return the smallest item from the *heap*, and also push the new " +"*item*. The heap size doesn't change. If the heap is empty, :exc:" +"`IndexError` is raised." +msgstr "" + +#: ../Doc/library/heapq.rst:72 +msgid "" +"This one step operation is more efficient than a :func:`heappop` followed " +"by :func:`heappush` and can be more appropriate when using a fixed-size " +"heap. The pop/push combination always returns an element from the heap and " +"replaces it with *item*." +msgstr "" + +#: ../Doc/library/heapq.rst:77 +msgid "" +"The value returned may be larger than the *item* added. If that isn't " +"desired, consider using :func:`heappushpop` instead. Its push/pop " +"combination returns the smaller of the two values, leaving the larger value " +"on the heap." +msgstr "" + +#: ../Doc/library/heapq.rst:83 +msgid "The module also offers three general purpose functions based on heaps." +msgstr "" + +#: ../Doc/library/heapq.rst:88 +msgid "" +"Merge multiple sorted inputs into a single sorted output (for example, merge " +"timestamped entries from multiple log files). Returns an :term:`iterator` " +"over the sorted values." +msgstr "" + +#: ../Doc/library/heapq.rst:92 +msgid "" +"Similar to ``sorted(itertools.chain(*iterables))`` but returns an iterable, " +"does not pull the data into memory all at once, and assumes that each of the " +"input streams is already sorted (smallest to largest)." +msgstr "" + +#: ../Doc/library/heapq.rst:98 +msgid "" +"*key* specifies a :term:`key function` of one argument that is used to " +"extract a comparison key from each input element. The default value is " +"``None`` (compare the elements directly)." +msgstr "" + +#: ../Doc/library/heapq.rst:102 +msgid "" +"*reverse* is a boolean value. If set to ``True``, then the input elements " +"are merged as if each comparison were reversed." +msgstr "" + +#: ../Doc/library/heapq.rst:105 +msgid "Added the optional *key* and *reverse* parameters." +msgstr "" + +#: ../Doc/library/heapq.rst:111 +msgid "" +"Return a list with the *n* largest elements from the dataset defined by " +"*iterable*. *key*, if provided, specifies a function of one argument that " +"is used to extract a comparison key from each element in the iterable: " +"``key=str.lower`` Equivalent to: ``sorted(iterable, key=key, reverse=True)[:" +"n]``" +msgstr "" + +#: ../Doc/library/heapq.rst:120 +msgid "" +"Return a list with the *n* smallest elements from the dataset defined by " +"*iterable*. *key*, if provided, specifies a function of one argument that " +"is used to extract a comparison key from each element in the iterable: " +"``key=str.lower`` Equivalent to: ``sorted(iterable, key=key)[:n]``" +msgstr "" + +#: ../Doc/library/heapq.rst:126 +msgid "" +"The latter two functions perform best for smaller values of *n*. For larger " +"values, it is more efficient to use the :func:`sorted` function. Also, when " +"``n==1``, it is more efficient to use the built-in :func:`min` and :func:" +"`max` functions. If repeated usage of these functions is required, consider " +"turning the iterable into an actual heap." +msgstr "" + +#: ../Doc/library/heapq.rst:134 ../Doc/library/timeit.rst:23 +msgid "Basic Examples" +msgstr "" + +#: ../Doc/library/heapq.rst:136 +msgid "" +"A `heapsort `_ can be implemented by " +"pushing all values onto a heap and then popping off the smallest values one " +"at a time::" +msgstr "" + +#: ../Doc/library/heapq.rst:149 +msgid "" +"This is similar to ``sorted(iterable)``, but unlike :func:`sorted`, this " +"implementation is not stable." +msgstr "" + +#: ../Doc/library/heapq.rst:152 +msgid "" +"Heap elements can be tuples. This is useful for assigning comparison values " +"(such as task priorities) alongside the main record being tracked::" +msgstr "" + +#: ../Doc/library/heapq.rst:165 +msgid "Priority Queue Implementation Notes" +msgstr "" + +#: ../Doc/library/heapq.rst:167 +msgid "" +"A `priority queue `_ is common " +"use for a heap, and it presents several implementation challenges:" +msgstr "" + +#: ../Doc/library/heapq.rst:170 +msgid "" +"Sort stability: how do you get two tasks with equal priorities to be " +"returned in the order they were originally added?" +msgstr "" + +#: ../Doc/library/heapq.rst:173 +msgid "" +"Tuple comparison breaks for (priority, task) pairs if the priorities are " +"equal and the tasks do not have a default comparison order." +msgstr "" + +#: ../Doc/library/heapq.rst:176 +msgid "" +"If the priority of a task changes, how do you move it to a new position in " +"the heap?" +msgstr "" + +#: ../Doc/library/heapq.rst:179 +msgid "" +"Or if a pending task needs to be deleted, how do you find it and remove it " +"from the queue?" +msgstr "" + +#: ../Doc/library/heapq.rst:182 +msgid "" +"A solution to the first two challenges is to store entries as 3-element list " +"including the priority, an entry count, and the task. The entry count " +"serves as a tie-breaker so that two tasks with the same priority are " +"returned in the order they were added. And since no two entry counts are the " +"same, the tuple comparison will never attempt to directly compare two tasks." +msgstr "" + +#: ../Doc/library/heapq.rst:188 +msgid "" +"The remaining challenges revolve around finding a pending task and making " +"changes to its priority or removing it entirely. Finding a task can be done " +"with a dictionary pointing to an entry in the queue." +msgstr "" + +#: ../Doc/library/heapq.rst:192 +msgid "" +"Removing the entry or changing its priority is more difficult because it " +"would break the heap structure invariants. So, a possible solution is to " +"mark the entry as removed and add a new entry with the revised priority::" +msgstr "" + +#: ../Doc/library/heapq.rst:226 +msgid "Theory" +msgstr "" + +#: ../Doc/library/heapq.rst:228 +msgid "" +"Heaps are arrays for which ``a[k] <= a[2*k+1]`` and ``a[k] <= a[2*k+2]`` for " +"all *k*, counting elements from 0. For the sake of comparison, non-existing " +"elements are considered to be infinite. The interesting property of a heap " +"is that ``a[0]`` is always its smallest element." +msgstr "" + +#: ../Doc/library/heapq.rst:233 +msgid "" +"The strange invariant above is meant to be an efficient memory " +"representation for a tournament. The numbers below are *k*, not ``a[k]``::" +msgstr "" + +#: ../Doc/library/heapq.rst:246 +msgid "" +"In the tree above, each cell *k* is topping ``2*k+1`` and ``2*k+2``. In a " +"usual binary tournament we see in sports, each cell is the winner over the " +"two cells it tops, and we can trace the winner down the tree to see all " +"opponents s/he had. However, in many computer applications of such " +"tournaments, we do not need to trace the history of a winner. To be more " +"memory efficient, when a winner is promoted, we try to replace it by " +"something else at a lower level, and the rule becomes that a cell and the " +"two cells it tops contain three different items, but the top cell \"wins\" " +"over the two topped cells." +msgstr "" + +#: ../Doc/library/heapq.rst:255 +msgid "" +"If this heap invariant is protected at all time, index 0 is clearly the " +"overall winner. The simplest algorithmic way to remove it and find the " +"\"next\" winner is to move some loser (let's say cell 30 in the diagram " +"above) into the 0 position, and then percolate this new 0 down the tree, " +"exchanging values, until the invariant is re-established. This is clearly " +"logarithmic on the total number of items in the tree. By iterating over all " +"items, you get an O(n log n) sort." +msgstr "" + +#: ../Doc/library/heapq.rst:262 +msgid "" +"A nice feature of this sort is that you can efficiently insert new items " +"while the sort is going on, provided that the inserted items are not \"better" +"\" than the last 0'th element you extracted. This is especially useful in " +"simulation contexts, where the tree holds all incoming events, and the \"win" +"\" condition means the smallest scheduled time. When an event schedules " +"other events for execution, they are scheduled into the future, so they can " +"easily go into the heap. So, a heap is a good structure for implementing " +"schedulers (this is what I used for my MIDI sequencer :-)." +msgstr "" + +#: ../Doc/library/heapq.rst:271 +msgid "" +"Various structures for implementing schedulers have been extensively " +"studied, and heaps are good for this, as they are reasonably speedy, the " +"speed is almost constant, and the worst case is not much different than the " +"average case. However, there are other representations which are more " +"efficient overall, yet the worst cases might be terrible." +msgstr "" + +#: ../Doc/library/heapq.rst:277 +msgid "" +"Heaps are also very useful in big disk sorts. You most probably all know " +"that a big sort implies producing \"runs\" (which are pre-sorted sequences, " +"whose size is usually related to the amount of CPU memory), followed by a " +"merging passes for these runs, which merging is often very cleverly " +"organised [#]_. It is very important that the initial sort produces the " +"longest runs possible. Tournaments are a good way to achieve that. If, " +"using all the memory available to hold a tournament, you replace and " +"percolate items that happen to fit the current run, you'll produce runs " +"which are twice the size of the memory for random input, and much better for " +"input fuzzily ordered." +msgstr "" + +#: ../Doc/library/heapq.rst:287 +msgid "" +"Moreover, if you output the 0'th item on disk and get an input which may not " +"fit in the current tournament (because the value \"wins\" over the last " +"output value), it cannot fit in the heap, so the size of the heap " +"decreases. The freed memory could be cleverly reused immediately for " +"progressively building a second heap, which grows at exactly the same rate " +"the first heap is melting. When the first heap completely vanishes, you " +"switch heaps and start a new run. Clever and quite effective!" +msgstr "" + +#: ../Doc/library/heapq.rst:295 +msgid "" +"In a word, heaps are useful memory structures to know. I use them in a few " +"applications, and I think it is good to keep a 'heap' module around. :-)" +msgstr "" + +#: ../Doc/library/heapq.rst:300 +msgid "" +"The disk balancing algorithms which are current, nowadays, are more annoying " +"than clever, and this is a consequence of the seeking capabilities of the " +"disks. On devices which cannot seek, like big tape drives, the story was " +"quite different, and one had to be very clever to ensure (far in advance) " +"that each tape movement will be the most effective possible (that is, will " +"best participate at \"progressing\" the merge). Some tapes were even able " +"to read backwards, and this was also used to avoid the rewinding time. " +"Believe me, real good tape sorts were quite spectacular to watch! From all " +"times, sorting has always been a Great Art! :-)" +msgstr "" + +#: ../Doc/library/hmac.rst:2 +msgid ":mod:`hmac` --- Keyed-Hashing for Message Authentication" +msgstr "" + +#: ../Doc/library/hmac.rst:10 +msgid "**Source code:** :source:`Lib/hmac.py`" +msgstr "" + +#: ../Doc/library/hmac.rst:14 +msgid "This module implements the HMAC algorithm as described by :rfc:`2104`." +msgstr "" + +#: ../Doc/library/hmac.rst:19 +msgid "" +"Return a new hmac object. *key* is a bytes or bytearray object giving the " +"secret key. If *msg* is present, the method call ``update(msg)`` is made. " +"*digestmod* is the digest name, digest constructor or module for the HMAC " +"object to use. It supports any name suitable to :func:`hashlib.new` and " +"defaults to the :data:`hashlib.md5` constructor." +msgstr "" + +#: ../Doc/library/hmac.rst:25 +msgid "" +"Parameter *key* can be a bytes or bytearray object. Parameter *msg* can be " +"of any type supported by :mod:`hashlib`. Parameter *digestmod* can be the " +"name of a hash algorithm." +msgstr "" + +#: ../Doc/library/hmac.rst:30 +msgid "MD5 as implicit default digest for *digestmod* is deprecated." +msgstr "" + +#: ../Doc/library/hmac.rst:34 +msgid "An HMAC object has the following methods:" +msgstr "" + +#: ../Doc/library/hmac.rst:38 +msgid "" +"Update the hmac object with *msg*. Repeated calls are equivalent to a " +"single call with the concatenation of all the arguments: ``m.update(a); m." +"update(b)`` is equivalent to ``m.update(a + b)``." +msgstr "" + +#: ../Doc/library/hmac.rst:42 +msgid "Parameter *msg* can be of any type supported by :mod:`hashlib`." +msgstr "" + +#: ../Doc/library/hmac.rst:48 +msgid "" +"Return the digest of the bytes passed to the :meth:`update` method so far. " +"This bytes object will be the same length as the *digest_size* of the digest " +"given to the constructor. It may contain non-ASCII bytes, including NUL " +"bytes." +msgstr "" + +#: ../Doc/library/hmac.rst:55 +msgid "" +"When comparing the output of :meth:`digest` to an externally-supplied digest " +"during a verification routine, it is recommended to use the :func:" +"`compare_digest` function instead of the ``==`` operator to reduce the " +"vulnerability to timing attacks." +msgstr "" + +#: ../Doc/library/hmac.rst:63 +msgid "" +"Like :meth:`digest` except the digest is returned as a string twice the " +"length containing only hexadecimal digits. This may be used to exchange the " +"value safely in email or other non-binary environments." +msgstr "" + +#: ../Doc/library/hmac.rst:69 +msgid "" +"When comparing the output of :meth:`hexdigest` to an externally-supplied " +"digest during a verification routine, it is recommended to use the :func:" +"`compare_digest` function instead of the ``==`` operator to reduce the " +"vulnerability to timing attacks." +msgstr "" + +#: ../Doc/library/hmac.rst:77 +msgid "" +"Return a copy (\"clone\") of the hmac object. This can be used to " +"efficiently compute the digests of strings that share a common initial " +"substring." +msgstr "" + +#: ../Doc/library/hmac.rst:85 +msgid "The size of the resulting HMAC digest in bytes." +msgstr "" + +#: ../Doc/library/hmac.rst:95 +msgid "The canonical name of this HMAC, always lowercase, e.g. ``hmac-md5``." +msgstr "" + +#: ../Doc/library/hmac.rst:100 +msgid "This module also provides the following helper function:" +msgstr "" + +#: ../Doc/library/hmac.rst:104 +msgid "" +"Return ``a == b``. This function uses an approach designed to prevent " +"timing analysis by avoiding content-based short circuiting behaviour, making " +"it appropriate for cryptography. *a* and *b* must both be of the same type: " +"either :class:`str` (ASCII only, as e.g. returned by :meth:`HMAC." +"hexdigest`), or a :term:`bytes-like object`." +msgstr "" + +#: ../Doc/library/hmac.rst:112 +msgid "" +"If *a* and *b* are of different lengths, or if an error occurs, a timing " +"attack could theoretically reveal information about the types and lengths of " +"*a* and *b*--but not their values." +msgstr "" + +#: ../Doc/library/hmac.rst:122 +msgid "Module :mod:`hashlib`" +msgstr "" + +#: ../Doc/library/hmac.rst:123 +msgid "The Python module providing secure hash functions." +msgstr "" + +#: ../Doc/library/html.rst:2 +msgid ":mod:`html` --- HyperText Markup Language support" +msgstr "" + +#: ../Doc/library/html.rst:7 +msgid "**Source code:** :source:`Lib/html/__init__.py`" +msgstr "" + +#: ../Doc/library/html.rst:11 +msgid "This module defines utilities to manipulate HTML." +msgstr "" + +#: ../Doc/library/html.rst:15 +msgid "" +"Convert the characters ``&``, ``<`` and ``>`` in string *s* to HTML-safe " +"sequences. Use this if you need to display text that might contain such " +"characters in HTML. If the optional flag *quote* is true, the characters (``" +"\"``) and (``'``) are also translated; this helps for inclusion in an HTML " +"attribute value delimited by quotes, as in ````." +msgstr "" + +#: ../Doc/library/html.rst:26 +msgid "" +"Convert all named and numeric character references (e.g. ``>``, ``>" +"``, ``&x3e;``) in the string *s* to the corresponding unicode characters. " +"This function uses the rules defined by the HTML 5 standard for both valid " +"and invalid character references, and the :data:`list of HTML 5 named " +"character references `." +msgstr "" + +#: ../Doc/library/html.rst:36 +msgid "Submodules in the ``html`` package are:" +msgstr "" + +#: ../Doc/library/html.rst:38 +msgid ":mod:`html.parser` -- HTML/XHTML parser with lenient parsing mode" +msgstr "" + +#: ../Doc/library/html.rst:39 +msgid ":mod:`html.entities` -- HTML entity definitions" +msgstr "" + +#: ../Doc/library/html.entities.rst:2 +msgid ":mod:`html.entities` --- Definitions of HTML general entities" +msgstr "" + +#: ../Doc/library/html.entities.rst:9 +msgid "**Source code:** :source:`Lib/html/entities.py`" +msgstr "" + +#: ../Doc/library/html.entities.rst:13 +msgid "" +"This module defines four dictionaries, :data:`html5`, :data:" +"`name2codepoint`, :data:`codepoint2name`, and :data:`entitydefs`." +msgstr "" + +#: ../Doc/library/html.entities.rst:19 +msgid "" +"A dictionary that maps HTML5 named character references [#]_ to the " +"equivalent Unicode character(s), e.g. ``html5['gt;'] == '>'``. Note that the " +"trailing semicolon is included in the name (e.g. ``'gt;'``), however some of " +"the names are accepted by the standard even without the semicolon: in this " +"case the name is present with and without the ``';'``. See also :func:`html." +"unescape`." +msgstr "" + +#: ../Doc/library/html.entities.rst:31 +msgid "" +"A dictionary mapping XHTML 1.0 entity definitions to their replacement text " +"in ISO Latin-1." +msgstr "" + +#: ../Doc/library/html.entities.rst:37 +msgid "A dictionary that maps HTML entity names to the Unicode code points." +msgstr "" + +#: ../Doc/library/html.entities.rst:42 +msgid "A dictionary that maps Unicode code points to HTML entity names." +msgstr "" + +#: ../Doc/library/html.entities.rst:47 +msgid "See https://www.w3.org/TR/html5/syntax.html#named-character-references" +msgstr "" + +#: ../Doc/library/html.parser.rst:2 +msgid ":mod:`html.parser` --- Simple HTML and XHTML parser" +msgstr "" + +#: ../Doc/library/html.parser.rst:7 +msgid "**Source code:** :source:`Lib/html/parser.py`" +msgstr "" + +#: ../Doc/library/html.parser.rst:15 +msgid "" +"This module defines a class :class:`HTMLParser` which serves as the basis " +"for parsing text files formatted in HTML (HyperText Mark-up Language) and " +"XHTML." +msgstr "" + +#: ../Doc/library/html.parser.rst:20 +msgid "Create a parser instance able to parse invalid markup." +msgstr "" + +#: ../Doc/library/html.parser.rst:22 +msgid "" +"If *convert_charrefs* is ``True`` (the default), all character references " +"(except the ones in ``script``/``style`` elements) are automatically " +"converted to the corresponding Unicode characters." +msgstr "" + +#: ../Doc/library/html.parser.rst:26 +msgid "" +"An :class:`.HTMLParser` instance is fed HTML data and calls handler methods " +"when start tags, end tags, text, comments, and other markup elements are " +"encountered. The user should subclass :class:`.HTMLParser` and override its " +"methods to implement the desired behavior." +msgstr "" + +#: ../Doc/library/html.parser.rst:31 +msgid "" +"This parser does not check that end tags match start tags or call the end-" +"tag handler for elements which are closed implicitly by closing an outer " +"element." +msgstr "" + +#: ../Doc/library/html.parser.rst:34 +msgid "*convert_charrefs* keyword argument added." +msgstr "" + +#: ../Doc/library/html.parser.rst:37 +msgid "The default value for argument *convert_charrefs* is now ``True``." +msgstr "" + +#: ../Doc/library/html.parser.rst:42 +msgid "Example HTML Parser Application" +msgstr "" + +#: ../Doc/library/html.parser.rst:44 +msgid "" +"As a basic example, below is a simple HTML parser that uses the :class:" +"`HTMLParser` class to print out start tags, end tags, and data as they are " +"encountered::" +msgstr "" + +#: ../Doc/library/html.parser.rst:64 +msgid "The output will then be:" +msgstr "" + +#: ../Doc/library/html.parser.rst:83 +msgid ":class:`.HTMLParser` Methods" +msgstr "" + +#: ../Doc/library/html.parser.rst:85 +msgid ":class:`HTMLParser` instances have the following methods:" +msgstr "" + +#: ../Doc/library/html.parser.rst:90 +msgid "" +"Feed some text to the parser. It is processed insofar as it consists of " +"complete elements; incomplete data is buffered until more data is fed or :" +"meth:`close` is called. *data* must be :class:`str`." +msgstr "" + +#: ../Doc/library/html.parser.rst:97 +msgid "" +"Force processing of all buffered data as if it were followed by an end-of-" +"file mark. This method may be redefined by a derived class to define " +"additional processing at the end of the input, but the redefined version " +"should always call the :class:`HTMLParser` base class method :meth:`close`." +msgstr "" + +#: ../Doc/library/html.parser.rst:105 +msgid "" +"Reset the instance. Loses all unprocessed data. This is called implicitly " +"at instantiation time." +msgstr "" + +#: ../Doc/library/html.parser.rst:111 +msgid "Return current line number and offset." +msgstr "" + +#: ../Doc/library/html.parser.rst:116 +msgid "" +"Return the text of the most recently opened start tag. This should not " +"normally be needed for structured processing, but may be useful in dealing " +"with HTML \"as deployed\" or for re-generating input with minimal changes " +"(whitespace between attributes can be preserved, etc.)." +msgstr "" + +#: ../Doc/library/html.parser.rst:122 +msgid "" +"The following methods are called when data or markup elements are " +"encountered and they are meant to be overridden in a subclass. The base " +"class implementations do nothing (except for :meth:`~HTMLParser." +"handle_startendtag`):" +msgstr "" + +#: ../Doc/library/html.parser.rst:129 +msgid "" +"This method is called to handle the start of a tag (e.g. ````)." +msgstr "" + +#: ../Doc/library/html.parser.rst:148 +msgid "The *tag* argument is the name of the tag converted to lower case." +msgstr "" + +#: ../Doc/library/html.parser.rst:153 +msgid "" +"Similar to :meth:`handle_starttag`, but called when the parser encounters an " +"XHTML-style empty tag (````). This method may be overridden by " +"subclasses which require this particular lexical information; the default " +"implementation simply calls :meth:`handle_starttag` and :meth:" +"`handle_endtag`." +msgstr "" + +#: ../Doc/library/html.parser.rst:161 +msgid "" +"This method is called to process arbitrary data (e.g. text nodes and the " +"content of ```` and ````)." +msgstr "" + +#: ../Doc/library/html.parser.rst:167 +msgid "" +"This method is called to process a named character reference of the form " +"``&name;`` (e.g. ``>``), where *name* is a general entity reference (e.g. " +"``'gt'``). This method is never called if *convert_charrefs* is ``True``." +msgstr "" + +#: ../Doc/library/html.parser.rst:175 +msgid "" +"This method is called to process decimal and hexadecimal numeric character " +"references of the form ``&#NNN;`` and ``&#xNNN;``. For example, the decimal " +"equivalent for ``>`` is ``>``, whereas the hexadecimal is ``>``; " +"in this case the method will receive ``'62'`` or ``'x3E'``. This method is " +"never called if *convert_charrefs* is ``True``." +msgstr "" + +#: ../Doc/library/html.parser.rst:184 +msgid "" +"This method is called when a comment is encountered (e.g. ```` will cause this method to be " +"called with the argument ``' comment '``." +msgstr "" + +#: ../Doc/library/html.parser.rst:189 +msgid "" +"The content of Internet Explorer conditional comments (condcoms) will also " +"be sent to this method, so, for ````, this method will receive ``'[if IE 9]>IE9-specific content``)." +msgstr "" + +#: ../Doc/library/html.parser.rst:199 +msgid "" +"The *decl* parameter will be the entire contents of the declaration inside " +"the ```` markup (e.g. ``'DOCTYPE html'``)." +msgstr "" + +#: ../Doc/library/html.parser.rst:205 +msgid "" +"Method called when a processing instruction is encountered. The *data* " +"parameter will contain the entire processing instruction. For example, for " +"the processing instruction ````, this method would be " +"called as ``handle_pi(\"proc color='red'\")``. It is intended to be " +"overridden by a derived class; the base class implementation does nothing." +msgstr "" + +#: ../Doc/library/html.parser.rst:213 +msgid "" +"The :class:`HTMLParser` class uses the SGML syntactic rules for processing " +"instructions. An XHTML processing instruction using the trailing ``'?'`` " +"will cause the ``'?'`` to be included in *data*." +msgstr "" + +#: ../Doc/library/html.parser.rst:220 +msgid "" +"This method is called when an unrecognized declaration is read by the parser." +msgstr "" + +#: ../Doc/library/html.parser.rst:222 +msgid "" +"The *data* parameter will be the entire contents of the declaration inside " +"the ```` markup. It is sometimes useful to be overridden by a " +"derived class. The base class implementation does nothing." +msgstr "" + +#: ../Doc/library/html.parser.rst:232 +msgid "" +"The following class implements a parser that will be used to illustrate more " +"examples::" +msgstr "" + +#: ../Doc/library/html.parser.rst:269 +msgid "Parsing a doctype::" +msgstr "" + +#: ../Doc/library/html.parser.rst:275 +msgid "Parsing an element with a few attributes and a title::" +msgstr "" + +#: ../Doc/library/html.parser.rst:287 +msgid "" +"The content of ``script`` and ``style`` elements is returned as is, without " +"further parsing::" +msgstr "" + +#: ../Doc/library/html.parser.rst:303 +msgid "Parsing comments::" +msgstr "" + +#: ../Doc/library/html.parser.rst:310 +msgid "" +"Parsing named and numeric character references and converting them to the " +"correct char (note: these 3 references are all equivalent to ``'>'``)::" +msgstr "" + +#: ../Doc/library/html.parser.rst:318 +msgid "" +"Feeding incomplete chunks to :meth:`~HTMLParser.feed` works, but :meth:" +"`~HTMLParser.handle_data` might be called more than once (unless " +"*convert_charrefs* is set to ``True``)::" +msgstr "" + +#: ../Doc/library/html.parser.rst:331 +msgid "Parsing invalid HTML (e.g. unquoted attributes) also works::" +msgstr "" + +#: ../Doc/library/http.rst:2 +msgid ":mod:`http` --- HTTP modules" +msgstr "" + +#: ../Doc/library/http.rst:7 +msgid "**Source code:** :source:`Lib/http/__init__.py`" +msgstr "" + +#: ../Doc/library/http.rst:15 +msgid "" +":mod:`http` is a package that collects several modules for working with the " +"HyperText Transfer Protocol:" +msgstr "" + +#: ../Doc/library/http.rst:18 +msgid "" +":mod:`http.client` is a low-level HTTP protocol client; for high-level URL " +"opening use :mod:`urllib.request`" +msgstr "" + +#: ../Doc/library/http.rst:20 +msgid "" +":mod:`http.server` contains basic HTTP server classes based on :mod:" +"`socketserver`" +msgstr "" + +#: ../Doc/library/http.rst:21 +msgid "" +":mod:`http.cookies` has utilities for implementing state management with " +"cookies" +msgstr "" + +#: ../Doc/library/http.rst:22 +msgid ":mod:`http.cookiejar` provides persistence of cookies" +msgstr "" + +#: ../Doc/library/http.rst:24 +msgid "" +":mod:`http` is also a module that defines a number of HTTP status codes and " +"associated messages through the :class:`http.HTTPStatus` enum:" +msgstr "" + +#: ../Doc/library/http.rst:31 +msgid "" +"A subclass of :class:`enum.IntEnum` that defines a set of HTTP status codes, " +"reason phrases and long descriptions written in English." +msgstr "" + +#: ../Doc/library/http.rst:53 +msgid "HTTP status codes" +msgstr "" + +#: ../Doc/library/http.rst:55 +msgid "" +"Supported, `IANA-registered `_ status codes available in :class:`http." +"HTTPStatus` are:" +msgstr "" + +#: ../Doc/library/http.rst:60 +msgid "Enum Name" +msgstr "" + +#: ../Doc/library/http.rst:60 +msgid "Details" +msgstr "" + +#: ../Doc/library/http.rst:62 +msgid "``100``" +msgstr "" + +#: ../Doc/library/http.rst:62 +msgid "``CONTINUE``" +msgstr "" + +#: ../Doc/library/http.rst:62 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.2.1" +msgstr "" + +#: ../Doc/library/http.rst:63 +msgid "``101``" +msgstr "" + +#: ../Doc/library/http.rst:63 +msgid "``SWITCHING_PROTOCOLS``" +msgstr "" + +#: ../Doc/library/http.rst:63 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.2.2" +msgstr "" + +#: ../Doc/library/http.rst:64 +msgid "``102``" +msgstr "" + +#: ../Doc/library/http.rst:64 +msgid "``PROCESSING``" +msgstr "" + +#: ../Doc/library/http.rst:64 +msgid "WebDAV :rfc:`2518`, Section 10.1" +msgstr "" + +#: ../Doc/library/http.rst:65 +msgid "``200``" +msgstr "" + +#: ../Doc/library/http.rst:65 +msgid "``OK``" +msgstr "" + +#: ../Doc/library/http.rst:65 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.3.1" +msgstr "" + +#: ../Doc/library/http.rst:66 +msgid "``201``" +msgstr "" + +#: ../Doc/library/http.rst:66 +msgid "``CREATED``" +msgstr "" + +#: ../Doc/library/http.rst:66 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.3.2" +msgstr "" + +#: ../Doc/library/http.rst:67 +msgid "``202``" +msgstr "" + +#: ../Doc/library/http.rst:67 +msgid "``ACCEPTED``" +msgstr "" + +#: ../Doc/library/http.rst:67 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.3.3" +msgstr "" + +#: ../Doc/library/http.rst:68 +msgid "``203``" +msgstr "" + +#: ../Doc/library/http.rst:68 +msgid "``NON_AUTHORITATIVE_INFORMATION``" +msgstr "" + +#: ../Doc/library/http.rst:68 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.3.4" +msgstr "" + +#: ../Doc/library/http.rst:69 +msgid "``204``" +msgstr "" + +#: ../Doc/library/http.rst:69 +msgid "``NO_CONTENT``" +msgstr "" + +#: ../Doc/library/http.rst:69 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.3.5" +msgstr "" + +#: ../Doc/library/http.rst:70 +msgid "``205``" +msgstr "" + +#: ../Doc/library/http.rst:70 +msgid "``RESET_CONTENT``" +msgstr "" + +#: ../Doc/library/http.rst:70 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.3.6" +msgstr "" + +#: ../Doc/library/http.rst:71 +msgid "``206``" +msgstr "" + +#: ../Doc/library/http.rst:71 +msgid "``PARTIAL_CONTENT``" +msgstr "" + +#: ../Doc/library/http.rst:71 +msgid "HTTP/1.1 :rfc:`7233`, Section 4.1" +msgstr "" + +#: ../Doc/library/http.rst:72 +msgid "``207``" +msgstr "" + +#: ../Doc/library/http.rst:72 +msgid "``MULTI_STATUS``" +msgstr "" + +#: ../Doc/library/http.rst:72 +msgid "WebDAV :rfc:`4918`, Section 11.1" +msgstr "" + +#: ../Doc/library/http.rst:73 +msgid "``208``" +msgstr "" + +#: ../Doc/library/http.rst:73 +msgid "``ALREADY_REPORTED``" +msgstr "" + +#: ../Doc/library/http.rst:73 +msgid "WebDAV Binding Extensions :rfc:`5842`, Section 7.1 (Experimental)" +msgstr "" + +#: ../Doc/library/http.rst:74 +msgid "``226``" +msgstr "" + +#: ../Doc/library/http.rst:74 +msgid "``IM_USED``" +msgstr "" + +#: ../Doc/library/http.rst:74 +msgid "Delta Encoding in HTTP :rfc:`3229`, Section 10.4.1" +msgstr "" + +#: ../Doc/library/http.rst:75 +msgid "``300``" +msgstr "" + +#: ../Doc/library/http.rst:75 +msgid "``MULTIPLE_CHOICES``" +msgstr "" + +#: ../Doc/library/http.rst:75 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.4.1" +msgstr "" + +#: ../Doc/library/http.rst:76 +msgid "``301``" +msgstr "" + +#: ../Doc/library/http.rst:76 +msgid "``MOVED_PERMANENTLY``" +msgstr "" + +#: ../Doc/library/http.rst:76 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.4.2" +msgstr "" + +#: ../Doc/library/http.rst:77 +msgid "``302``" +msgstr "" + +#: ../Doc/library/http.rst:77 +msgid "``FOUND``" +msgstr "" + +#: ../Doc/library/http.rst:77 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.4.3" +msgstr "" + +#: ../Doc/library/http.rst:78 +msgid "``303``" +msgstr "" + +#: ../Doc/library/http.rst:78 +msgid "``SEE_OTHER``" +msgstr "" + +#: ../Doc/library/http.rst:78 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.4.4" +msgstr "" + +#: ../Doc/library/http.rst:79 +msgid "``304``" +msgstr "" + +#: ../Doc/library/http.rst:79 +msgid "``NOT_MODIFIED``" +msgstr "" + +#: ../Doc/library/http.rst:79 +msgid "HTTP/1.1 :rfc:`7232`, Section 4.1" +msgstr "" + +#: ../Doc/library/http.rst:80 +msgid "``305``" +msgstr "" + +#: ../Doc/library/http.rst:80 +msgid "``USE_PROXY``" +msgstr "" + +#: ../Doc/library/http.rst:80 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.4.5" +msgstr "" + +#: ../Doc/library/http.rst:81 +msgid "``307``" +msgstr "" + +#: ../Doc/library/http.rst:81 +msgid "``TEMPORARY_REDIRECT``" +msgstr "" + +#: ../Doc/library/http.rst:81 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.4.7" +msgstr "" + +#: ../Doc/library/http.rst:82 +msgid "``308``" +msgstr "" + +#: ../Doc/library/http.rst:82 +msgid "``PERMANENT_REDIRECT``" +msgstr "" + +#: ../Doc/library/http.rst:82 +msgid "Permanent Redirect :rfc:`7238`, Section 3 (Experimental)" +msgstr "" + +#: ../Doc/library/http.rst:83 +msgid "``400``" +msgstr "" + +#: ../Doc/library/http.rst:83 +msgid "``BAD_REQUEST``" +msgstr "" + +#: ../Doc/library/http.rst:83 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.1" +msgstr "" + +#: ../Doc/library/http.rst:84 +msgid "``401``" +msgstr "" + +#: ../Doc/library/http.rst:84 +msgid "``UNAUTHORIZED``" +msgstr "" + +#: ../Doc/library/http.rst:84 +msgid "HTTP/1.1 Authentication :rfc:`7235`, Section 3.1" +msgstr "" + +#: ../Doc/library/http.rst:85 +msgid "``402``" +msgstr "" + +#: ../Doc/library/http.rst:85 +msgid "``PAYMENT_REQUIRED``" +msgstr "" + +#: ../Doc/library/http.rst:85 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.2" +msgstr "" + +#: ../Doc/library/http.rst:86 +msgid "``403``" +msgstr "" + +#: ../Doc/library/http.rst:86 +msgid "``FORBIDDEN``" +msgstr "" + +#: ../Doc/library/http.rst:86 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.3" +msgstr "" + +#: ../Doc/library/http.rst:87 +msgid "``404``" +msgstr "" + +#: ../Doc/library/http.rst:87 +msgid "``NOT_FOUND``" +msgstr "" + +#: ../Doc/library/http.rst:87 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.4" +msgstr "" + +#: ../Doc/library/http.rst:88 +msgid "``405``" +msgstr "" + +#: ../Doc/library/http.rst:88 +msgid "``METHOD_NOT_ALLOWED``" +msgstr "" + +#: ../Doc/library/http.rst:88 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.5" +msgstr "" + +#: ../Doc/library/http.rst:89 +msgid "``406``" +msgstr "" + +#: ../Doc/library/http.rst:89 +msgid "``NOT_ACCEPTABLE``" +msgstr "" + +#: ../Doc/library/http.rst:89 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.6" +msgstr "" + +#: ../Doc/library/http.rst:90 +msgid "``407``" +msgstr "" + +#: ../Doc/library/http.rst:90 +msgid "``PROXY_AUTHENTICATION_REQUIRED``" +msgstr "" + +#: ../Doc/library/http.rst:90 +msgid "HTTP/1.1 Authentication :rfc:`7235`, Section 3.2" +msgstr "" + +#: ../Doc/library/http.rst:91 +msgid "``408``" +msgstr "" + +#: ../Doc/library/http.rst:91 +msgid "``REQUEST_TIMEOUT``" +msgstr "" + +#: ../Doc/library/http.rst:91 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.7" +msgstr "" + +#: ../Doc/library/http.rst:92 +msgid "``409``" +msgstr "" + +#: ../Doc/library/http.rst:92 +msgid "``CONFLICT``" +msgstr "" + +#: ../Doc/library/http.rst:92 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.8" +msgstr "" + +#: ../Doc/library/http.rst:93 +msgid "``410``" +msgstr "" + +#: ../Doc/library/http.rst:93 +msgid "``GONE``" +msgstr "" + +#: ../Doc/library/http.rst:93 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.9" +msgstr "" + +#: ../Doc/library/http.rst:94 +msgid "``411``" +msgstr "" + +#: ../Doc/library/http.rst:94 +msgid "``LENGTH_REQUIRED``" +msgstr "" + +#: ../Doc/library/http.rst:94 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.10" +msgstr "" + +#: ../Doc/library/http.rst:95 +msgid "``412``" +msgstr "" + +#: ../Doc/library/http.rst:95 +msgid "``PRECONDITION_FAILED``" +msgstr "" + +#: ../Doc/library/http.rst:95 +msgid "HTTP/1.1 :rfc:`7232`, Section 4.2" +msgstr "" + +#: ../Doc/library/http.rst:96 +msgid "``413``" +msgstr "" + +#: ../Doc/library/http.rst:96 +msgid "``REQUEST_ENTITY_TOO_LARGE``" +msgstr "" + +#: ../Doc/library/http.rst:96 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.11" +msgstr "" + +#: ../Doc/library/http.rst:97 +msgid "``414``" +msgstr "" + +#: ../Doc/library/http.rst:97 +msgid "``REQUEST_URI_TOO_LONG``" +msgstr "" + +#: ../Doc/library/http.rst:97 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.12" +msgstr "" + +#: ../Doc/library/http.rst:98 +msgid "``415``" +msgstr "" + +#: ../Doc/library/http.rst:98 +msgid "``UNSUPPORTED_MEDIA_TYPE``" +msgstr "" + +#: ../Doc/library/http.rst:98 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.13" +msgstr "" + +#: ../Doc/library/http.rst:99 +msgid "``416``" +msgstr "" + +#: ../Doc/library/http.rst:99 +msgid "``REQUEST_RANGE_NOT_SATISFIABLE``" +msgstr "" + +#: ../Doc/library/http.rst:99 +msgid "HTTP/1.1 Range Requests :rfc:`7233`, Section 4.4" +msgstr "" + +#: ../Doc/library/http.rst:100 +msgid "``417``" +msgstr "" + +#: ../Doc/library/http.rst:100 +msgid "``EXPECTATION_FAILED``" +msgstr "" + +#: ../Doc/library/http.rst:100 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.14" +msgstr "" + +#: ../Doc/library/http.rst:101 +msgid "``422``" +msgstr "" + +#: ../Doc/library/http.rst:101 +msgid "``UNPROCESSABLE_ENTITY``" +msgstr "" + +#: ../Doc/library/http.rst:101 +msgid "WebDAV :rfc:`4918`, Section 11.2" +msgstr "" + +#: ../Doc/library/http.rst:102 +msgid "``423``" +msgstr "" + +#: ../Doc/library/http.rst:102 +msgid "``LOCKED``" +msgstr "" + +#: ../Doc/library/http.rst:102 +msgid "WebDAV :rfc:`4918`, Section 11.3" +msgstr "" + +#: ../Doc/library/http.rst:103 +msgid "``424``" +msgstr "" + +#: ../Doc/library/http.rst:103 +msgid "``FAILED_DEPENDENCY``" +msgstr "" + +#: ../Doc/library/http.rst:103 +msgid "WebDAV :rfc:`4918`, Section 11.4" +msgstr "" + +#: ../Doc/library/http.rst:104 +msgid "``426``" +msgstr "" + +#: ../Doc/library/http.rst:104 +msgid "``UPGRADE_REQUIRED``" +msgstr "" + +#: ../Doc/library/http.rst:104 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.5.15" +msgstr "" + +#: ../Doc/library/http.rst:105 +msgid "``428``" +msgstr "" + +#: ../Doc/library/http.rst:105 +msgid "``PRECONDITION_REQUIRED``" +msgstr "" + +#: ../Doc/library/http.rst:105 ../Doc/library/http.rst:106 +#: ../Doc/library/http.rst:107 +msgid "Additional HTTP Status Codes :rfc:`6585`" +msgstr "" + +#: ../Doc/library/http.rst:106 +msgid "``429``" +msgstr "" + +#: ../Doc/library/http.rst:106 +msgid "``TOO_MANY_REQUESTS``" +msgstr "" + +#: ../Doc/library/http.rst:107 +msgid "``431``" +msgstr "" + +#: ../Doc/library/http.rst:107 +msgid "``REQUEST_HEADER_FIELDS_TOO_LARGE``" +msgstr "" + +#: ../Doc/library/http.rst:108 +msgid "``500``" +msgstr "" + +#: ../Doc/library/http.rst:108 +msgid "``INTERNAL_SERVER_ERROR``" +msgstr "" + +#: ../Doc/library/http.rst:108 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.6.1" +msgstr "" + +#: ../Doc/library/http.rst:109 +msgid "``501``" +msgstr "" + +#: ../Doc/library/http.rst:109 +msgid "``NOT_IMPLEMENTED``" +msgstr "" + +#: ../Doc/library/http.rst:109 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.6.2" +msgstr "" + +#: ../Doc/library/http.rst:110 +msgid "``502``" +msgstr "" + +#: ../Doc/library/http.rst:110 +msgid "``BAD_GATEWAY``" +msgstr "" + +#: ../Doc/library/http.rst:110 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.6.3" +msgstr "" + +#: ../Doc/library/http.rst:111 +msgid "``503``" +msgstr "" + +#: ../Doc/library/http.rst:111 +msgid "``SERVICE_UNAVAILABLE``" +msgstr "" + +#: ../Doc/library/http.rst:111 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.6.4" +msgstr "" + +#: ../Doc/library/http.rst:112 +msgid "``504``" +msgstr "" + +#: ../Doc/library/http.rst:112 +msgid "``GATEWAY_TIMEOUT``" +msgstr "" + +#: ../Doc/library/http.rst:112 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.6.5" +msgstr "" + +#: ../Doc/library/http.rst:113 +msgid "``505``" +msgstr "" + +#: ../Doc/library/http.rst:113 +msgid "``HTTP_VERSION_NOT_SUPPORTED``" +msgstr "" + +#: ../Doc/library/http.rst:113 +msgid "HTTP/1.1 :rfc:`7231`, Section 6.6.6" +msgstr "" + +#: ../Doc/library/http.rst:114 +msgid "``506``" +msgstr "" + +#: ../Doc/library/http.rst:114 +msgid "``VARIANT_ALSO_NEGOTIATES``" +msgstr "" + +#: ../Doc/library/http.rst:114 +msgid "" +"Transparent Content Negotiation in HTTP :rfc:`2295`, Section 8.1 " +"(Experimental)" +msgstr "" + +#: ../Doc/library/http.rst:115 +msgid "``507``" +msgstr "" + +#: ../Doc/library/http.rst:115 +msgid "``INSUFFICIENT_STORAGE``" +msgstr "" + +#: ../Doc/library/http.rst:115 +msgid "WebDAV :rfc:`4918`, Section 11.5" +msgstr "" + +#: ../Doc/library/http.rst:116 +msgid "``508``" +msgstr "" + +#: ../Doc/library/http.rst:116 +msgid "``LOOP_DETECTED``" +msgstr "" + +#: ../Doc/library/http.rst:116 +msgid "WebDAV Binding Extensions :rfc:`5842`, Section 7.2 (Experimental)" +msgstr "" + +#: ../Doc/library/http.rst:117 +msgid "``510``" +msgstr "" + +#: ../Doc/library/http.rst:117 +msgid "``NOT_EXTENDED``" +msgstr "" + +#: ../Doc/library/http.rst:117 +msgid "An HTTP Extension Framework :rfc:`2774`, Section 7 (Experimental)" +msgstr "" + +#: ../Doc/library/http.rst:118 +msgid "``511``" +msgstr "" + +#: ../Doc/library/http.rst:118 +msgid "``NETWORK_AUTHENTICATION_REQUIRED``" +msgstr "" + +#: ../Doc/library/http.rst:118 +msgid "Additional HTTP Status Codes :rfc:`6585`, Section 6" +msgstr "" + +#: ../Doc/library/http.rst:121 +msgid "" +"In order to preserve backwards compatibility, enum values are also present " +"in the :mod:`http.client` module in the form of constants. The enum name is " +"equal to the constant name (i.e. ``http.HTTPStatus.OK`` is also available as " +"``http.client.OK``)." +msgstr "" + +#: ../Doc/library/http.client.rst:2 +msgid ":mod:`http.client` --- HTTP protocol client" +msgstr "" + +#: ../Doc/library/http.client.rst:7 +msgid "**Source code:** :source:`Lib/http/client.py`" +msgstr "" + +#: ../Doc/library/http.client.rst:17 +msgid "" +"This module defines classes which implement the client side of the HTTP and " +"HTTPS protocols. It is normally not used directly --- the module :mod:" +"`urllib.request` uses it to handle URLs that use HTTP and HTTPS." +msgstr "" + +#: ../Doc/library/http.client.rst:23 ../Doc/library/urllib.request.rst:21 +msgid "" +"The `Requests package `_ is recommended " +"for a higher-level HTTP client interface." +msgstr "" + +#: ../Doc/library/http.client.rst:28 +msgid "" +"HTTPS support is only available if Python was compiled with SSL support " +"(through the :mod:`ssl` module)." +msgstr "" + +#: ../Doc/library/http.client.rst:31 +msgid "The module provides the following classes:" +msgstr "" + +#: ../Doc/library/http.client.rst:36 +msgid "" +"An :class:`HTTPConnection` instance represents one transaction with an HTTP " +"server. It should be instantiated passing it a host and optional port " +"number. If no port number is passed, the port is extracted from the host " +"string if it has the form ``host:port``, else the default HTTP port (80) is " +"used. If the optional *timeout* parameter is given, blocking operations " +"(like connection attempts) will timeout after that many seconds (if it is " +"not given, the global default timeout setting is used). The optional " +"*source_address* parameter may be a tuple of a (host, port) to use as the " +"source address the HTTP connection is made from." +msgstr "" + +#: ../Doc/library/http.client.rst:46 +msgid "" +"For example, the following calls all create instances that connect to the " +"server at the same host and port::" +msgstr "" + +#: ../Doc/library/http.client.rst:54 ../Doc/library/socket.rst:485 +msgid "*source_address* was added." +msgstr "" + +#: ../Doc/library/http.client.rst:57 +msgid "" +"The *strict* parameter was removed. HTTP 0.9-style \"Simple Responses\" are " +"not longer supported." +msgstr "" + +#: ../Doc/library/http.client.rst:67 +msgid "" +"A subclass of :class:`HTTPConnection` that uses SSL for communication with " +"secure servers. Default port is ``443``. If *context* is specified, it " +"must be a :class:`ssl.SSLContext` instance describing the various SSL " +"options." +msgstr "" + +#: ../Doc/library/http.client.rst:72 +msgid "Please read :ref:`ssl-security` for more information on best practices." +msgstr "" + +#: ../Doc/library/http.client.rst:74 +msgid "*source_address*, *context* and *check_hostname* were added." +msgstr "" + +#: ../Doc/library/http.client.rst:77 +msgid "" +"This class now supports HTTPS virtual hosts if possible (that is, if :data:" +"`ssl.HAS_SNI` is true)." +msgstr "" + +#: ../Doc/library/http.client.rst:81 +msgid "" +"The *strict* parameter was removed. HTTP 0.9-style \"Simple Responses\" are " +"no longer supported." +msgstr "" + +#: ../Doc/library/http.client.rst:85 +msgid "" +"This class now performs all the necessary certificate and hostname checks by " +"default. To revert to the previous, unverified, behavior :func:`ssl." +"_create_unverified_context` can be passed to the *context* parameter." +msgstr "" + +#: ../Doc/library/http.client.rst:93 +msgid "" +"*key_file* and *cert_file* are deprecated in favor of *context*. Please use :" +"meth:`ssl.SSLContext.load_cert_chain` instead, or let :func:`ssl." +"create_default_context` select the system's trusted CA certificates for you." +msgstr "" + +#: ../Doc/library/http.client.rst:98 +msgid "" +"The *check_hostname* parameter is also deprecated; the :attr:`ssl.SSLContext." +"check_hostname` attribute of *context* should be used instead." +msgstr "" + +#: ../Doc/library/http.client.rst:105 +msgid "" +"Class whose instances are returned upon successful connection. Not " +"instantiated directly by user." +msgstr "" + +#: ../Doc/library/http.client.rst:108 +msgid "" +"The *strict* parameter was removed. HTTP 0.9 style \"Simple Responses\" are " +"no longer supported." +msgstr "" + +#: ../Doc/library/http.client.rst:113 +msgid "The following exceptions are raised as appropriate:" +msgstr "" + +#: ../Doc/library/http.client.rst:118 ../Doc/library/sqlite3.rst:740 +msgid "" +"The base class of the other exceptions in this module. It is a subclass of :" +"exc:`Exception`." +msgstr "" + +#: ../Doc/library/http.client.rst:124 ../Doc/library/http.client.rst:135 +#: ../Doc/library/http.client.rst:140 ../Doc/library/http.client.rst:145 +#: ../Doc/library/http.client.rst:150 ../Doc/library/http.client.rst:155 +msgid "A subclass of :exc:`HTTPException`." +msgstr "" + +#: ../Doc/library/http.client.rst:129 +msgid "" +"A subclass of :exc:`HTTPException`, raised if a port is given and is either " +"non-numeric or empty." +msgstr "" + +#: ../Doc/library/http.client.rst:160 ../Doc/library/http.client.rst:165 +#: ../Doc/library/http.client.rst:170 +msgid "A subclass of :exc:`ImproperConnectionState`." +msgstr "" + +#: ../Doc/library/http.client.rst:175 +msgid "" +"A subclass of :exc:`HTTPException`. Raised if a server responds with a HTTP " +"status code that we don't understand." +msgstr "" + +#: ../Doc/library/http.client.rst:181 +msgid "" +"A subclass of :exc:`HTTPException`. Raised if an excessively long line is " +"received in the HTTP protocol from the server." +msgstr "" + +#: ../Doc/library/http.client.rst:187 +msgid "" +"A subclass of :exc:`ConnectionResetError` and :exc:`BadStatusLine`. Raised " +"by :meth:`HTTPConnection.getresponse` when the attempt to read the response " +"results in no data read from the connection, indicating that the remote end " +"has closed the connection." +msgstr "" + +#: ../Doc/library/http.client.rst:192 +msgid "Previously, :exc:`BadStatusLine`\\ ``('')`` was raised." +msgstr "" + +#: ../Doc/library/http.client.rst:196 ../Doc/library/string.rst:20 +msgid "The constants defined in this module are:" +msgstr "" + +#: ../Doc/library/http.client.rst:200 +msgid "The default port for the HTTP protocol (always ``80``)." +msgstr "" + +#: ../Doc/library/http.client.rst:204 +msgid "The default port for the HTTPS protocol (always ``443``)." +msgstr "" + +#: ../Doc/library/http.client.rst:208 +msgid "This dictionary maps the HTTP 1.1 status codes to the W3C names." +msgstr "" + +#: ../Doc/library/http.client.rst:210 +msgid "" +"Example: ``http.client.responses[http.client.NOT_FOUND]`` is ``'Not Found'``." +msgstr "" + +#: ../Doc/library/http.client.rst:212 +msgid "" +"See :ref:`http-status-codes` for a list of HTTP status codes that are " +"available in this module as constants." +msgstr "" + +#: ../Doc/library/http.client.rst:219 +msgid "HTTPConnection Objects" +msgstr "" + +#: ../Doc/library/http.client.rst:221 +msgid ":class:`HTTPConnection` instances have the following methods:" +msgstr "" + +#: ../Doc/library/http.client.rst:227 +msgid "" +"This will send a request to the server using the HTTP request method " +"*method* and the selector *url*." +msgstr "" + +#: ../Doc/library/http.client.rst:230 +msgid "" +"If *body* is specified, the specified data is sent after the headers are " +"finished. It may be a :class:`str`, a :term:`bytes-like object`, an open :" +"term:`file object`, or an iterable of :class:`bytes`. If *body* is a " +"string, it is encoded as ISO-8859-1, the default for HTTP. If it is a bytes-" +"like object, the bytes are sent as is. If it is a :term:`file object`, the " +"contents of the file is sent; this file object should support at least the " +"``read()`` method. If the file object is an instance of :class:`io." +"TextIOBase`, the data returned by the ``read()`` method will be encoded as " +"ISO-8859-1, otherwise the data returned by ``read()`` is sent as is. If " +"*body* is an iterable, the elements of the iterable are sent as is until the " +"iterable is exhausted." +msgstr "" + +#: ../Doc/library/http.client.rst:242 +msgid "" +"The *headers* argument should be a mapping of extra HTTP headers to send " +"with the request." +msgstr "" + +#: ../Doc/library/http.client.rst:245 +msgid "" +"If *headers* contains neither Content-Length nor Transfer-Encoding, but " +"there is a request body, one of those header fields will be added " +"automatically. If *body* is ``None``, the Content-Length header is set to " +"``0`` for methods that expect a body (``PUT``, ``POST``, and ``PATCH``). If " +"*body* is a string or a bytes-like object that is not also a :term:`file " +"`, the Content-Length header is set to its length. Any other " +"type of *body* (files and iterables in general) will be chunk-encoded, and " +"the Transfer-Encoding header will automatically be set instead of Content-" +"Length." +msgstr "" + +#: ../Doc/library/http.client.rst:257 +msgid "" +"The *encode_chunked* argument is only relevant if Transfer-Encoding is " +"specified in *headers*. If *encode_chunked* is ``False``, the " +"HTTPConnection object assumes that all encoding is handled by the calling " +"code. If it is ``True``, the body will be chunk-encoded." +msgstr "" + +#: ../Doc/library/http.client.rst:263 +msgid "" +"Chunked transfer encoding has been added to the HTTP protocol version 1.1. " +"Unless the HTTP server is known to handle HTTP 1.1, the caller must either " +"specify the Content-Length, or must pass a :class:`str` or bytes-like object " +"that is not also a file as the body representation." +msgstr "" + +#: ../Doc/library/http.client.rst:269 +msgid "*body* can now be an iterable." +msgstr "" + +#: ../Doc/library/http.client.rst:272 +msgid "" +"If neither Content-Length nor Transfer-Encoding are set in *headers*, file " +"and iterable *body* objects are now chunk-encoded. The *encode_chunked* " +"argument was added. No attempt is made to determine the Content-Length for " +"file objects." +msgstr "" + +#: ../Doc/library/http.client.rst:281 +msgid "" +"Should be called after a request is sent to get the response from the " +"server. Returns an :class:`HTTPResponse` instance." +msgstr "" + +#: ../Doc/library/http.client.rst:286 +msgid "" +"Note that you must have read the whole response before you can send a new " +"request to the server." +msgstr "" + +#: ../Doc/library/http.client.rst:289 +msgid "" +"If a :exc:`ConnectionError` or subclass is raised, the :class:" +"`HTTPConnection` object will be ready to reconnect when a new request is " +"sent." +msgstr "" + +#: ../Doc/library/http.client.rst:297 +msgid "" +"Set the debugging level. The default debug level is ``0``, meaning no " +"debugging output is printed. Any value greater than ``0`` will cause all " +"currently defined debug output to be printed to stdout. The ``debuglevel`` " +"is passed to any new :class:`HTTPResponse` objects that are created." +msgstr "" + +#: ../Doc/library/http.client.rst:307 +msgid "" +"Set the host and the port for HTTP Connect Tunnelling. This allows running " +"the connection through a proxy server." +msgstr "" + +#: ../Doc/library/http.client.rst:310 +msgid "" +"The host and port arguments specify the endpoint of the tunneled connection " +"(i.e. the address included in the CONNECT request, *not* the address of the " +"proxy server)." +msgstr "" + +#: ../Doc/library/http.client.rst:314 +msgid "" +"The headers argument should be a mapping of extra HTTP headers to send with " +"the CONNECT request." +msgstr "" + +#: ../Doc/library/http.client.rst:317 +msgid "" +"For example, to tunnel through a HTTPS proxy server running locally on port " +"8080, we would pass the address of the proxy to the :class:`HTTPSConnection` " +"constructor, and the address of the host that we eventually want to reach to " +"the :meth:`~HTTPConnection.set_tunnel` method::" +msgstr "" + +#: ../Doc/library/http.client.rst:332 +msgid "" +"Connect to the server specified when the object was created. By default, " +"this is called automatically when making a request if the client does not " +"already have a connection." +msgstr "" + +#: ../Doc/library/http.client.rst:339 +msgid "Close the connection to the server." +msgstr "" + +#: ../Doc/library/http.client.rst:341 +msgid "" +"As an alternative to using the :meth:`request` method described above, you " +"can also send your request step by step, by using the four functions below." +msgstr "" + +#: ../Doc/library/http.client.rst:348 +msgid "" +"This should be the first call after the connection to the server has been " +"made. It sends a line to the server consisting of the *method* string, the " +"*url* string, and the HTTP version (``HTTP/1.1``). To disable automatic " +"sending of ``Host:`` or ``Accept-Encoding:`` headers (for example to accept " +"additional content encodings), specify *skip_host* or *skip_accept_encoding* " +"with non-False values." +msgstr "" + +#: ../Doc/library/http.client.rst:358 +msgid "" +"Send an :rfc:`822`\\ -style header to the server. It sends a line to the " +"server consisting of the header, a colon and a space, and the first " +"argument. If more arguments are given, continuation lines are sent, each " +"consisting of a tab and an argument." +msgstr "" + +#: ../Doc/library/http.client.rst:366 +msgid "" +"Send a blank line to the server, signalling the end of the headers. The " +"optional *message_body* argument can be used to pass a message body " +"associated with the request." +msgstr "" + +#: ../Doc/library/http.client.rst:370 +msgid "" +"If *encode_chunked* is ``True``, the result of each iteration of " +"*message_body* will be chunk-encoded as specified in :rfc:`7230`, Section " +"3.3.1. How the data is encoded is dependent on the type of *message_body*. " +"If *message_body* implements the :ref:`buffer interface ` the " +"encoding will result in a single chunk. If *message_body* is a :class:" +"`collections.Iterable`, each iteration of *message_body* will result in a " +"chunk. If *message_body* is a :term:`file object`, each call to ``.read()`` " +"will result in a chunk. The method automatically signals the end of the " +"chunk-encoded data immediately after *message_body*." +msgstr "" + +#: ../Doc/library/http.client.rst:381 +msgid "" +"Due to the chunked encoding specification, empty chunks yielded by an " +"iterator body will be ignored by the chunk-encoder. This is to avoid " +"premature termination of the read of the request by the target server due to " +"malformed encoding." +msgstr "" + +#: ../Doc/library/http.client.rst:386 +msgid "Chunked encoding support. The *encode_chunked* parameter was added." +msgstr "" + +#: ../Doc/library/http.client.rst:393 +msgid "" +"Send data to the server. This should be used directly only after the :meth:" +"`endheaders` method has been called and before :meth:`getresponse` is called." +msgstr "" + +#: ../Doc/library/http.client.rst:401 +msgid "HTTPResponse Objects" +msgstr "" + +#: ../Doc/library/http.client.rst:403 +msgid "" +"An :class:`HTTPResponse` instance wraps the HTTP response from the server. " +"It provides access to the request headers and the entity body. The response " +"is an iterable object and can be used in a with statement." +msgstr "" + +#: ../Doc/library/http.client.rst:408 +msgid "" +"The :class:`io.BufferedIOBase` interface is now implemented and all of its " +"reader operations are supported." +msgstr "" + +#: ../Doc/library/http.client.rst:415 +msgid "Reads and returns the response body, or up to the next *amt* bytes." +msgstr "" + +#: ../Doc/library/http.client.rst:419 +msgid "" +"Reads up to the next len(b) bytes of the response body into the buffer *b*. " +"Returns the number of bytes read." +msgstr "" + +#: ../Doc/library/http.client.rst:426 +msgid "" +"Return the value of the header *name*, or *default* if there is no header " +"matching *name*. If there is more than one header with the name *name*, " +"return all of the values joined by ', '. If 'default' is any iterable other " +"than a single string, its elements are similarly returned joined by commas." +msgstr "" + +#: ../Doc/library/http.client.rst:433 +msgid "Return a list of (header, value) tuples." +msgstr "" + +#: ../Doc/library/http.client.rst:437 +msgid "Return the ``fileno`` of the underlying socket." +msgstr "" + +#: ../Doc/library/http.client.rst:441 +msgid "" +"A :class:`http.client.HTTPMessage` instance containing the response " +"headers. :class:`http.client.HTTPMessage` is a subclass of :class:`email." +"message.Message`." +msgstr "" + +#: ../Doc/library/http.client.rst:447 +msgid "" +"HTTP protocol version used by server. 10 for HTTP/1.0, 11 for HTTP/1.1." +msgstr "" + +#: ../Doc/library/http.client.rst:451 +msgid "Status code returned by server." +msgstr "" + +#: ../Doc/library/http.client.rst:455 +msgid "Reason phrase returned by server." +msgstr "" + +#: ../Doc/library/http.client.rst:459 +msgid "" +"A debugging hook. If :attr:`debuglevel` is greater than zero, messages will " +"be printed to stdout as the response is read and parsed." +msgstr "" + +#: ../Doc/library/http.client.rst:464 +msgid "Is ``True`` if the stream is closed." +msgstr "" + +#: ../Doc/library/http.client.rst:469 +msgid "Here is an example session that uses the ``GET`` method::" +msgstr "" + +#: ../Doc/library/http.client.rst:493 +msgid "" +"Here is an example session that uses the ``HEAD`` method. Note that the " +"``HEAD`` method never returns any data. ::" +msgstr "" + +#: ../Doc/library/http.client.rst:508 +msgid "Here is an example session that shows how to ``POST`` requests::" +msgstr "" + +#: ../Doc/library/http.client.rst:524 +msgid "" +"Client side ``HTTP PUT`` requests are very similar to ``POST`` requests. The " +"difference lies only the server side where HTTP server will allow resources " +"to be created via ``PUT`` request. It should be noted that custom HTTP " +"methods +are also handled in :class:`urllib.request.Request` by sending the " +"appropriate +method attribute.Here is an example session that shows how to " +"do ``PUT`` request using http.client::" +msgstr "" + +#: ../Doc/library/http.client.rst:546 +msgid "HTTPMessage Objects" +msgstr "" + +#: ../Doc/library/http.client.rst:548 +msgid "" +"An :class:`http.client.HTTPMessage` instance holds the headers from an HTTP " +"response. It is implemented using the :class:`email.message.Message` class." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:2 +msgid ":mod:`http.cookiejar` --- Cookie handling for HTTP clients" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:10 +msgid "**Source code:** :source:`Lib/http/cookiejar.py`" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:14 +msgid "" +"The :mod:`http.cookiejar` module defines classes for automatic handling of " +"HTTP cookies. It is useful for accessing web sites that require small " +"pieces of data -- :dfn:`cookies` -- to be set on the client machine by an " +"HTTP response from a web server, and then returned to the server in later " +"HTTP requests." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:19 +msgid "" +"Both the regular Netscape cookie protocol and the protocol defined by :rfc:" +"`2965` are handled. RFC 2965 handling is switched off by default. :rfc:" +"`2109` cookies are parsed as Netscape cookies and subsequently treated " +"either as Netscape or RFC 2965 cookies according to the 'policy' in effect. " +"Note that the great majority of cookies on the Internet are Netscape " +"cookies. :mod:`http.cookiejar` attempts to follow the de-facto Netscape " +"cookie protocol (which differs substantially from that set out in the " +"original Netscape specification), including taking note of the ``max-age`` " +"and ``port`` cookie-attributes introduced with RFC 2965." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:31 +msgid "" +"The various named parameters found in :mailheader:`Set-Cookie` and :" +"mailheader:`Set-Cookie2` headers (eg. ``domain`` and ``expires``) are " +"conventionally referred to as :dfn:`attributes`. To distinguish them from " +"Python attributes, the documentation for this module uses the term :dfn:" +"`cookie-attribute` instead." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:38 +msgid "The module defines the following exception:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:43 +msgid "" +"Instances of :class:`FileCookieJar` raise this exception on failure to load " +"cookies from a file. :exc:`LoadError` is a subclass of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:46 +msgid "" +"LoadError was made a subclass of :exc:`OSError` instead of :exc:`IOError`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:51 ../Doc/library/urllib.request.rst:184 +msgid "The following classes are provided:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:56 +msgid "*policy* is an object implementing the :class:`CookiePolicy` interface." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:58 +msgid "" +"The :class:`CookieJar` class stores HTTP cookies. It extracts cookies from " +"HTTP requests, and returns them in HTTP responses. :class:`CookieJar` " +"instances automatically expire contained cookies when necessary. Subclasses " +"are also responsible for storing and retrieving cookies from a file or " +"database." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:66 +msgid "" +"*policy* is an object implementing the :class:`CookiePolicy` interface. For " +"the other arguments, see the documentation for the corresponding attributes." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:69 +msgid "" +"A :class:`CookieJar` which can load cookies from, and perhaps save cookies " +"to, a file on disk. Cookies are **NOT** loaded from the named file until " +"either the :meth:`load` or :meth:`revert` method is called. Subclasses of " +"this class are documented in section :ref:`file-cookie-jar-classes`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:77 +msgid "" +"This class is responsible for deciding whether each cookie should be " +"accepted from / returned to the server." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:83 +msgid "" +"Constructor arguments should be passed as keyword arguments only. " +"*blocked_domains* is a sequence of domain names that we never accept cookies " +"from, nor return cookies to. *allowed_domains* if not :const:`None`, this is " +"a sequence of the only domains for which we accept and return cookies. For " +"all other arguments, see the documentation for :class:`CookiePolicy` and :" +"class:`DefaultCookiePolicy` objects." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:90 +msgid "" +":class:`DefaultCookiePolicy` implements the standard accept / reject rules " +"for Netscape and RFC 2965 cookies. By default, RFC 2109 cookies (ie. " +"cookies received in a :mailheader:`Set-Cookie` header with a version cookie-" +"attribute of 1) are treated according to the RFC 2965 rules. However, if " +"RFC 2965 handling is turned off or :attr:`rfc2109_as_netscape` is ``True``, " +"RFC 2109 cookies are 'downgraded' by the :class:`CookieJar` instance to " +"Netscape cookies, by setting the :attr:`version` attribute of the :class:" +"`Cookie` instance to 0. :class:`DefaultCookiePolicy` also provides some " +"parameters to allow some fine-tuning of policy." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:103 +msgid "" +"This class represents Netscape, RFC 2109 and RFC 2965 cookies. It is not " +"expected that users of :mod:`http.cookiejar` construct their own :class:" +"`Cookie` instances. Instead, if necessary, call :meth:`make_cookies` on a :" +"class:`CookieJar` instance." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:112 +msgid "Module :mod:`urllib.request`" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:112 +msgid "URL opening with automatic cookie handling." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:117 +msgid "Module :mod:`http.cookies`" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:115 +msgid "" +"HTTP cookie classes, principally useful for server-side code. The :mod:" +"`http.cookiejar` and :mod:`http.cookies` modules do not depend on each other." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:123 +msgid "https://curl.haxx.se/rfc/cookie_spec.html" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:120 +msgid "" +"The specification of the original Netscape cookie protocol. Though this is " +"still the dominant protocol, the 'Netscape cookie protocol' implemented by " +"all the major browsers (and :mod:`http.cookiejar`) only bears a passing " +"resemblance to the one sketched out in ``cookie_spec.html``." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:126 ../Doc/library/http.cookies.rst:67 +msgid ":rfc:`2109` - HTTP State Management Mechanism" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:126 +msgid "Obsoleted by RFC 2965. Uses :mailheader:`Set-Cookie` with version=1." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:130 +msgid ":rfc:`2965` - HTTP State Management Mechanism" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:129 +msgid "" +"The Netscape protocol with the bugs fixed. Uses :mailheader:`Set-Cookie2` " +"in place of :mailheader:`Set-Cookie`. Not widely used." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:133 +msgid "http://kristol.org/cookie/errata.html" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:133 +msgid "Unfinished errata to RFC 2965." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:135 +msgid ":rfc:`2964` - Use of HTTP State Management" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:140 +msgid "CookieJar and FileCookieJar Objects" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:142 +msgid "" +":class:`CookieJar` objects support the :term:`iterator` protocol for " +"iterating over contained :class:`Cookie` objects." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:145 +msgid ":class:`CookieJar` has the following methods:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:150 +msgid "Add correct :mailheader:`Cookie` header to *request*." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:152 +msgid "" +"If policy allows (ie. the :attr:`rfc2965` and :attr:`hide_cookie2` " +"attributes of the :class:`CookieJar`'s :class:`CookiePolicy` instance are " +"true and false respectively), the :mailheader:`Cookie2` header is also added " +"when appropriate." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:156 +msgid "" +"The *request* object (usually a :class:`urllib.request..Request` instance) " +"must support the methods :meth:`get_full_url`, :meth:`get_host`, :meth:" +"`get_type`, :meth:`unverifiable`, :meth:`has_header`, :meth:`get_header`, :" +"meth:`header_items`, :meth:`add_unredirected_header` and :attr:" +"`origin_req_host` attribute as documented by :mod:`urllib.request`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:165 ../Doc/library/http.cookiejar.rst:191 +msgid "" +"*request* object needs :attr:`origin_req_host` attribute. Dependency on a " +"deprecated method :meth:`get_origin_req_host` has been removed." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:171 +msgid "" +"Extract cookies from HTTP *response* and store them in the :class:" +"`CookieJar`, where allowed by policy." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:174 +msgid "" +"The :class:`CookieJar` will look for allowable :mailheader:`Set-Cookie` and :" +"mailheader:`Set-Cookie2` headers in the *response* argument, and store " +"cookies as appropriate (subject to the :meth:`CookiePolicy.set_ok` method's " +"approval)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:178 +msgid "" +"The *response* object (usually the result of a call to :meth:`urllib.request." +"urlopen`, or similar) should support an :meth:`info` method, which returns " +"an :class:`email.message.Message` instance." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:182 +msgid "" +"The *request* object (usually a :class:`urllib.request.Request` instance) " +"must support the methods :meth:`get_full_url`, :meth:`get_host`, :meth:" +"`unverifiable`, and :attr:`origin_req_host` attribute, as documented by :mod:" +"`urllib.request`. The request is used to set default values for cookie-" +"attributes as well as for checking that the cookie is allowed to be set." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:196 +msgid "Set the :class:`CookiePolicy` instance to be used." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:201 +msgid "" +"Return sequence of :class:`Cookie` objects extracted from *response* object." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:203 +msgid "" +"See the documentation for :meth:`extract_cookies` for the interfaces " +"required of the *response* and *request* arguments." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:209 +msgid "Set a :class:`Cookie` if policy says it's OK to do so." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:214 +msgid "" +"Set a :class:`Cookie`, without checking with policy to see whether or not it " +"should be set." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:220 +msgid "Clear some cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:222 +msgid "" +"If invoked without arguments, clear all cookies. If given a single " +"argument, only cookies belonging to that *domain* will be removed. If given " +"two arguments, cookies belonging to the specified *domain* and URL *path* " +"are removed. If given three arguments, then the cookie with the specified " +"*domain*, *path* and *name* is removed." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:228 +msgid "Raises :exc:`KeyError` if no matching cookie exists." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:233 +msgid "Discard all session cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:235 +msgid "" +"Discards all contained cookies that have a true :attr:`discard` attribute " +"(usually because they had either no ``max-age`` or ``expires`` cookie-" +"attribute, or an explicit ``discard`` cookie-attribute). For interactive " +"browsers, the end of a session usually corresponds to closing the browser " +"window." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:240 +msgid "" +"Note that the :meth:`save` method won't save session cookies anyway, unless " +"you ask otherwise by passing a true *ignore_discard* argument." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:243 +msgid ":class:`FileCookieJar` implements the following additional methods:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:248 +msgid "Save cookies to a file." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:250 +msgid "" +"This base class raises :exc:`NotImplementedError`. Subclasses may leave " +"this method unimplemented." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:253 +msgid "" +"*filename* is the name of file in which to save cookies. If *filename* is " +"not specified, :attr:`self.filename` is used (whose default is the value " +"passed to the constructor, if any); if :attr:`self.filename` is :const:" +"`None`, :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:258 +msgid "" +"*ignore_discard*: save even cookies set to be discarded. *ignore_expires*: " +"save even cookies that have expired" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:261 +msgid "" +"The file is overwritten if it already exists, thus wiping all the cookies it " +"contains. Saved cookies can be restored later using the :meth:`load` or :" +"meth:`revert` methods." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:268 +msgid "Load cookies from a file." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:270 +msgid "Old cookies are kept unless overwritten by newly loaded ones." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:272 +msgid "Arguments are as for :meth:`save`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:274 +msgid "" +"The named file must be in the format understood by the class, or :exc:" +"`LoadError` will be raised. Also, :exc:`OSError` may be raised, for example " +"if the file does not exist." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:284 +msgid "Clear all cookies and reload cookies from a saved file." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:286 +msgid "" +":meth:`revert` can raise the same exceptions as :meth:`load`. If there is a " +"failure, the object's state will not be altered." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:289 +msgid ":class:`FileCookieJar` instances have the following public attributes:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:294 +msgid "" +"Filename of default file in which to keep cookies. This attribute may be " +"assigned to." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:300 +msgid "" +"If true, load cookies lazily from disk. This attribute should not be " +"assigned to. This is only a hint, since this only affects performance, not " +"behaviour (unless the cookies on disk are changing). A :class:`CookieJar` " +"object may ignore it. None of the :class:`FileCookieJar` classes included " +"in the standard library lazily loads cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:310 +msgid "FileCookieJar subclasses and co-operation with web browsers" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:312 +msgid "" +"The following :class:`CookieJar` subclasses are provided for reading and " +"writing." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:317 +msgid "" +"A :class:`FileCookieJar` that can load from and save cookies to disk in the " +"Mozilla ``cookies.txt`` file format (which is also used by the Lynx and " +"Netscape browsers)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:323 +msgid "" +"This loses information about RFC 2965 cookies, and also about newer or non-" +"standard cookie-attributes such as ``port``." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:328 +msgid "" +"Back up your cookies before saving if you have cookies whose loss / " +"corruption would be inconvenient (there are some subtleties which may lead " +"to slight changes in the file over a load / save round-trip)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:332 +msgid "" +"Also note that cookies saved while Mozilla is running will get clobbered by " +"Mozilla." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:338 +msgid "" +"A :class:`FileCookieJar` that can load from and save cookies to disk in " +"format compatible with the libwww-perl library's ``Set-Cookie3`` file " +"format. This is convenient if you want to store cookies in a human-readable " +"file." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:346 +msgid "CookiePolicy Objects" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:348 +msgid "" +"Objects implementing the :class:`CookiePolicy` interface have the following " +"methods:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:354 +msgid "" +"Return boolean value indicating whether cookie should be accepted from " +"server." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:356 +msgid "" +"*cookie* is a :class:`Cookie` instance. *request* is an object implementing " +"the interface defined by the documentation for :meth:`CookieJar." +"extract_cookies`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:363 +msgid "" +"Return boolean value indicating whether cookie should be returned to server." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:365 +msgid "" +"*cookie* is a :class:`Cookie` instance. *request* is an object implementing " +"the interface defined by the documentation for :meth:`CookieJar." +"add_cookie_header`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:372 +msgid "Return false if cookies should not be returned, given cookie domain." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:374 +msgid "" +"This method is an optimization. It removes the need for checking every " +"cookie with a particular domain (which might involve reading many files). " +"Returning true from :meth:`domain_return_ok` and :meth:`path_return_ok` " +"leaves all the work to :meth:`return_ok`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:379 +msgid "" +"If :meth:`domain_return_ok` returns true for the cookie domain, :meth:" +"`path_return_ok` is called for the cookie path. Otherwise, :meth:" +"`path_return_ok` and :meth:`return_ok` are never called for that cookie " +"domain. If :meth:`path_return_ok` returns true, :meth:`return_ok` is called " +"with the :class:`Cookie` object itself for a full check. Otherwise, :meth:" +"`return_ok` is never called for that cookie path." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:386 +msgid "" +"Note that :meth:`domain_return_ok` is called for every *cookie* domain, not " +"just for the *request* domain. For example, the function might be called " +"with both ``\".example.com\"`` and ``\"www.example.com\"`` if the request " +"domain is ``\"www.example.com\"``. The same goes for :meth:`path_return_ok`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:391 +msgid "The *request* argument is as documented for :meth:`return_ok`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:396 +msgid "Return false if cookies should not be returned, given cookie path." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:398 +msgid "See the documentation for :meth:`domain_return_ok`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:400 +msgid "" +"In addition to implementing the methods above, implementations of the :class:" +"`CookiePolicy` interface must also supply the following attributes, " +"indicating which protocols should be used, and how. All of these attributes " +"may be assigned to." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:408 +msgid "Implement Netscape protocol." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:413 +msgid "Implement RFC 2965 protocol." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:418 +msgid "" +"Don't add :mailheader:`Cookie2` header to requests (the presence of this " +"header indicates to the server that we understand RFC 2965 cookies)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:421 +msgid "" +"The most useful way to define a :class:`CookiePolicy` class is by " +"subclassing from :class:`DefaultCookiePolicy` and overriding some or all of " +"the methods above. :class:`CookiePolicy` itself may be used as a 'null " +"policy' to allow setting and receiving any and all cookies (this is unlikely " +"to be useful)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:430 +msgid "DefaultCookiePolicy Objects" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:432 +msgid "Implements the standard rules for accepting and returning cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:434 +msgid "" +"Both RFC 2965 and Netscape cookies are covered. RFC 2965 handling is " +"switched off by default." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:437 +msgid "" +"The easiest way to provide your own policy is to override this class and " +"call its methods in your overridden implementations before adding your own " +"additional checks::" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:450 +msgid "" +"In addition to the features required to implement the :class:`CookiePolicy` " +"interface, this class allows you to block and allow domains from setting and " +"receiving cookies. There are also some strictness switches that allow you " +"to tighten up the rather loose Netscape protocol rules a little bit (at the " +"cost of blocking some benign cookies)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:456 +msgid "" +"A domain blacklist and whitelist is provided (both off by default). Only " +"domains not in the blacklist and present in the whitelist (if the whitelist " +"is active) participate in cookie setting and returning. Use the " +"*blocked_domains* constructor argument, and :meth:`blocked_domains` and :" +"meth:`set_blocked_domains` methods (and the corresponding argument and " +"methods for *allowed_domains*). If you set a whitelist, you can turn it off " +"again by setting it to :const:`None`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:464 +msgid "" +"Domains in block or allow lists that do not start with a dot must equal the " +"cookie domain to be matched. For example, ``\"example.com\"`` matches a " +"blacklist entry of ``\"example.com\"``, but ``\"www.example.com\"`` does " +"not. Domains that do start with a dot are matched by more specific domains " +"too. For example, both ``\"www.example.com\"`` and ``\"www.coyote.example.com" +"\"`` match ``\".example.com\"`` (but ``\"example.com\"`` itself does not). " +"IP addresses are an exception, and must match exactly. For example, if " +"blocked_domains contains ``\"192.168.1.2\"`` and ``\".168.1.2\"``, " +"192.168.1.2 is blocked, but 193.168.1.2 is not." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:473 +msgid "" +":class:`DefaultCookiePolicy` implements the following additional methods:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:478 +msgid "Return the sequence of blocked domains (as a tuple)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:483 +msgid "Set the sequence of blocked domains." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:488 +msgid "" +"Return whether *domain* is on the blacklist for setting or receiving cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:493 +msgid "Return :const:`None`, or the sequence of allowed domains (as a tuple)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:498 +msgid "Set the sequence of allowed domains, or :const:`None`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:503 +msgid "" +"Return whether *domain* is not on the whitelist for setting or receiving " +"cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:506 +msgid "" +":class:`DefaultCookiePolicy` instances have the following attributes, which " +"are all initialised from the constructor arguments of the same name, and " +"which may all be assigned to." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:513 +msgid "" +"If true, request that the :class:`CookieJar` instance downgrade RFC 2109 " +"cookies (ie. cookies received in a :mailheader:`Set-Cookie` header with a " +"version cookie-attribute of 1) to Netscape cookies by setting the version " +"attribute of the :class:`Cookie` instance to 0. The default value is :const:" +"`None`, in which case RFC 2109 cookies are downgraded if and only if RFC " +"2965 handling is turned off. Therefore, RFC 2109 cookies are downgraded by " +"default." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:521 +msgid "General strictness switches:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:525 +msgid "" +"Don't allow sites to set two-component domains with country-code top-level " +"domains like ``.co.uk``, ``.gov.uk``, ``.co.nz``.etc. This is far from " +"perfect and isn't guaranteed to work!" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:530 +msgid "RFC 2965 protocol strictness switches:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:534 +msgid "" +"Follow RFC 2965 rules on unverifiable transactions (usually, an unverifiable " +"transaction is one resulting from a redirect or a request for an image " +"hosted on another site). If this is false, cookies are *never* blocked on " +"the basis of verifiability" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:540 +msgid "Netscape protocol strictness switches:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:544 +msgid "" +"Apply RFC 2965 rules on unverifiable transactions even to Netscape cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:549 +msgid "" +"Flags indicating how strict to be with domain-matching rules for Netscape " +"cookies. See below for acceptable values." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:555 +msgid "" +"Ignore cookies in Set-Cookie: headers that have names starting with ``'$'``." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:560 +msgid "Don't allow setting cookies whose path doesn't path-match request URI." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:562 +msgid "" +":attr:`strict_ns_domain` is a collection of flags. Its value is constructed " +"by or-ing together (for example, ``DomainStrictNoDots|" +"DomainStrictNonDomain`` means both flags are set)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:569 +msgid "" +"When setting cookies, the 'host prefix' must not contain a dot (eg. ``www." +"foo.bar.com`` can't set a cookie for ``.bar.com``, because ``www.foo`` " +"contains a dot)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:576 +msgid "" +"Cookies that did not explicitly specify a ``domain`` cookie-attribute can " +"only be returned to a domain equal to the domain that set the cookie (eg. " +"``spam.example.com`` won't be returned cookies from ``example.com`` that had " +"no ``domain`` cookie-attribute)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:584 +msgid "When setting cookies, require a full RFC 2965 domain-match." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:586 +msgid "" +"The following attributes are provided for convenience, and are the most " +"useful combinations of the above flags:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:592 +msgid "" +"Equivalent to 0 (ie. all of the above Netscape domain strictness flags " +"switched off)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:598 +msgid "Equivalent to ``DomainStrictNoDots|DomainStrictNonDomain``." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:602 ../Doc/library/http.cookies.rst:74 +msgid "Cookie Objects" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:604 +msgid "" +":class:`Cookie` instances have Python attributes roughly corresponding to " +"the standard cookie-attributes specified in the various cookie standards. " +"The correspondence is not one-to-one, because there are complicated rules " +"for assigning default values, because the ``max-age`` and ``expires`` cookie-" +"attributes contain equivalent information, and because RFC 2109 cookies may " +"be 'downgraded' by :mod:`http.cookiejar` from version 1 to version 0 " +"(Netscape) cookies." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:612 +msgid "" +"Assignment to these attributes should not be necessary other than in rare " +"circumstances in a :class:`CookiePolicy` method. The class does not enforce " +"internal consistency, so you should know what you're doing if you do that." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:619 +msgid "" +"Integer or :const:`None`. Netscape cookies have :attr:`version` 0. RFC 2965 " +"and RFC 2109 cookies have a ``version`` cookie-attribute of 1. However, " +"note that :mod:`http.cookiejar` may 'downgrade' RFC 2109 cookies to Netscape " +"cookies, in which case :attr:`version` is 0." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:627 +msgid "Cookie name (a string)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:632 +msgid "Cookie value (a string), or :const:`None`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:637 +msgid "" +"String representing a port or a set of ports (eg. '80', or '80,8080'), or :" +"const:`None`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:643 +msgid "Cookie path (a string, eg. ``'/acme/rocket_launchers'``)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:648 +msgid "``True`` if cookie should only be returned over a secure connection." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:653 +msgid "" +"Integer expiry date in seconds since epoch, or :const:`None`. See also the :" +"meth:`is_expired` method." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:659 +msgid "``True`` if this is a session cookie." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:664 +msgid "" +"String comment from the server explaining the function of this cookie, or :" +"const:`None`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:670 +msgid "" +"URL linking to a comment from the server explaining the function of this " +"cookie, or :const:`None`." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:676 +msgid "" +"``True`` if this cookie was received as an RFC 2109 cookie (ie. the cookie " +"arrived in a :mailheader:`Set-Cookie` header, and the value of the Version " +"cookie-attribute in that header was 1). This attribute is provided because :" +"mod:`http.cookiejar` may 'downgrade' RFC 2109 cookies to Netscape cookies, " +"in which case :attr:`version` is 0." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:685 +msgid "" +"``True`` if a port or set of ports was explicitly specified by the server " +"(in the :mailheader:`Set-Cookie` / :mailheader:`Set-Cookie2` header)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:691 +msgid "``True`` if a domain was explicitly specified by the server." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:696 +msgid "" +"``True`` if the domain explicitly specified by the server began with a dot " +"(``'.'``)." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:699 +msgid "" +"Cookies may have additional non-standard cookie-attributes. These may be " +"accessed using the following methods:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:705 +msgid "Return true if cookie has the named cookie-attribute." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:710 +msgid "" +"If cookie has the named cookie-attribute, return its value. Otherwise, " +"return *default*." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:716 +msgid "Set the value of the named cookie-attribute." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:718 +msgid "The :class:`Cookie` class also defines the following method:" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:723 +msgid "" +"``True`` if cookie has passed the time at which the server requested it " +"should expire. If *now* is given (in seconds since the epoch), return " +"whether the cookie has expired at the specified time." +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:731 +msgid "" +"The first example shows the most common usage of :mod:`http.cookiejar`::" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:738 +msgid "" +"This example illustrates how to open a URL using your Netscape, Mozilla, or " +"Lynx cookies (assumes Unix/Netscape convention for location of the cookies " +"file)::" +msgstr "" + +#: ../Doc/library/http.cookiejar.rst:747 +msgid "" +"The next example illustrates the use of :class:`DefaultCookiePolicy`. Turn " +"on RFC 2965 cookies, be more strict about domains when setting and returning " +"Netscape cookies, and block some domains from setting cookies or having them " +"returned::" +msgstr "" + +#: ../Doc/library/http.cookies.rst:2 +msgid ":mod:`http.cookies` --- HTTP state management" +msgstr "" + +#: ../Doc/library/http.cookies.rst:10 +msgid "**Source code:** :source:`Lib/http/cookies.py`" +msgstr "" + +#: ../Doc/library/http.cookies.rst:14 +msgid "" +"The :mod:`http.cookies` module defines classes for abstracting the concept " +"of cookies, an HTTP state management mechanism. It supports both simple " +"string-only cookies, and provides an abstraction for having any serializable " +"data-type as cookie value." +msgstr "" + +#: ../Doc/library/http.cookies.rst:19 +msgid "" +"The module formerly strictly applied the parsing rules described in the :rfc:" +"`2109` and :rfc:`2068` specifications. It has since been discovered that " +"MSIE 3.0x doesn't follow the character rules outlined in those specs and " +"also many current day browsers and servers have relaxed parsing rules when " +"comes to Cookie handling. As a result, the parsing rules used are a bit " +"less strict." +msgstr "" + +#: ../Doc/library/http.cookies.rst:25 +msgid "" +"The character set, :data:`string.ascii_letters`, :data:`string.digits` and " +"``!#$%&'*+-.^_`|~:`` denote the set of valid characters allowed by this " +"module in Cookie name (as :attr:`~Morsel.key`)." +msgstr "" + +#: ../Doc/library/http.cookies.rst:29 +msgid "Allowed ':' as a valid Cookie name character." +msgstr "" + +#: ../Doc/library/http.cookies.rst:35 +msgid "" +"On encountering an invalid cookie, :exc:`CookieError` is raised, so if your " +"cookie data comes from a browser you should always prepare for invalid data " +"and catch :exc:`CookieError` on parsing." +msgstr "" + +#: ../Doc/library/http.cookies.rst:42 +msgid "" +"Exception failing because of :rfc:`2109` invalidity: incorrect attributes, " +"incorrect :mailheader:`Set-Cookie` header, etc." +msgstr "" + +#: ../Doc/library/http.cookies.rst:48 +msgid "" +"This class is a dictionary-like object whose keys are strings and whose " +"values are :class:`Morsel` instances. Note that upon setting a key to a " +"value, the value is first converted to a :class:`Morsel` containing the key " +"and the value." +msgstr "" + +#: ../Doc/library/http.cookies.rst:52 +msgid "If *input* is given, it is passed to the :meth:`load` method." +msgstr "" + +#: ../Doc/library/http.cookies.rst:57 +msgid "" +"This class derives from :class:`BaseCookie` and overrides :meth:" +"`value_decode` and :meth:`value_encode` to be the identity and :func:`str` " +"respectively." +msgstr "" + +#: ../Doc/library/http.cookies.rst:65 +msgid "Module :mod:`http.cookiejar`" +msgstr "" + +#: ../Doc/library/http.cookies.rst:64 +msgid "" +"HTTP cookie handling for web *clients*. The :mod:`http.cookiejar` and :mod:" +"`http.cookies` modules do not depend on each other." +msgstr "" + +#: ../Doc/library/http.cookies.rst:68 +msgid "This is the state management specification implemented by this module." +msgstr "" + +#: ../Doc/library/http.cookies.rst:79 +msgid "" +"Return a decoded value from a string representation. Return value can be any " +"type. This method does nothing in :class:`BaseCookie` --- it exists so it " +"can be overridden." +msgstr "" + +#: ../Doc/library/http.cookies.rst:86 +msgid "" +"Return an encoded value. *val* can be any type, but return value must be a " +"string. This method does nothing in :class:`BaseCookie` --- it exists so it " +"can be overridden." +msgstr "" + +#: ../Doc/library/http.cookies.rst:90 +msgid "" +"In general, it should be the case that :meth:`value_encode` and :meth:" +"`value_decode` are inverses on the range of *value_decode*." +msgstr "" + +#: ../Doc/library/http.cookies.rst:96 +msgid "" +"Return a string representation suitable to be sent as HTTP headers. *attrs* " +"and *header* are sent to each :class:`Morsel`'s :meth:`output` method. *sep* " +"is used to join the headers together, and is by default the combination " +"``'\\r\\n'`` (CRLF)." +msgstr "" + +#: ../Doc/library/http.cookies.rst:104 +msgid "" +"Return an embeddable JavaScript snippet, which, if run on a browser which " +"supports JavaScript, will act the same as if the HTTP headers was sent." +msgstr "" + +#: ../Doc/library/http.cookies.rst:107 ../Doc/library/http.cookies.rst:203 +#: ../Doc/library/http.cookies.rst:211 +msgid "The meaning for *attrs* is the same as in :meth:`output`." +msgstr "" + +#: ../Doc/library/http.cookies.rst:112 +msgid "" +"If *rawdata* is a string, parse it as an ``HTTP_COOKIE`` and add the values " +"found there as :class:`Morsel`\\ s. If it is a dictionary, it is equivalent " +"to::" +msgstr "" + +#: ../Doc/library/http.cookies.rst:122 +msgid "Morsel Objects" +msgstr "" + +#: ../Doc/library/http.cookies.rst:127 +msgid "Abstract a key/value pair, which has some :rfc:`2109` attributes." +msgstr "" + +#: ../Doc/library/http.cookies.rst:129 +msgid "" +"Morsels are dictionary-like objects, whose set of keys is constant --- the " +"valid :rfc:`2109` attributes, which are" +msgstr "" + +#: ../Doc/library/http.cookies.rst:132 +msgid "``expires``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:133 +msgid "``path``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:134 +msgid "``comment``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:135 +msgid "``domain``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:136 +msgid "``max-age``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:137 +msgid "``secure``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:138 +msgid "``version``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:139 +msgid "``httponly``" +msgstr "" + +#: ../Doc/library/http.cookies.rst:141 +msgid "" +"The attribute :attr:`httponly` specifies that the cookie is only transferred " +"in HTTP requests, and is not accessible through JavaScript. This is intended " +"to mitigate some forms of cross-site scripting." +msgstr "" + +#: ../Doc/library/http.cookies.rst:145 +msgid "The keys are case-insensitive and their default value is ``''``." +msgstr "" + +#: ../Doc/library/http.cookies.rst:147 +msgid "" +":meth:`~Morsel.__eq__` now takes :attr:`~Morsel.key` and :attr:`~Morsel." +"value` into account." +msgstr "" + +#: ../Doc/library/http.cookies.rst:154 +msgid "The value of the cookie." +msgstr "" + +#: ../Doc/library/http.cookies.rst:156 +msgid "assigning to ``value``; use :meth:`~Morsel.set` instead." +msgstr "" + +#: ../Doc/library/http.cookies.rst:162 +msgid "The encoded value of the cookie --- this is what should be sent." +msgstr "" + +#: ../Doc/library/http.cookies.rst:164 +msgid "assigning to ``coded_value``; use :meth:`~Morsel.set` instead." +msgstr "" + +#: ../Doc/library/http.cookies.rst:170 +msgid "The name of the cookie." +msgstr "" + +#: ../Doc/library/http.cookies.rst:172 +msgid "assigning to ``key``; use :meth:`~Morsel.set` instead." +msgstr "" + +#: ../Doc/library/http.cookies.rst:178 +msgid "Set the *key*, *value* and *coded_value* attributes." +msgstr "" + +#: ../Doc/library/http.cookies.rst:180 +msgid "" +"The undocumented *LegalChars* parameter is ignored and will be removed in a " +"future version." +msgstr "" + +#: ../Doc/library/http.cookies.rst:187 +msgid "Whether *K* is a member of the set of keys of a :class:`Morsel`." +msgstr "" + +#: ../Doc/library/http.cookies.rst:192 +msgid "" +"Return a string representation of the Morsel, suitable to be sent as an HTTP " +"header. By default, all the attributes are included, unless *attrs* is " +"given, in which case it should be a list of attributes to use. *header* is " +"by default ``\"Set-Cookie:\"``." +msgstr "" + +#: ../Doc/library/http.cookies.rst:200 +msgid "" +"Return an embeddable JavaScript snippet, which, if run on a browser which " +"supports JavaScript, will act the same as if the HTTP header was sent." +msgstr "" + +#: ../Doc/library/http.cookies.rst:208 +msgid "" +"Return a string representing the Morsel, without any surrounding HTTP or " +"JavaScript." +msgstr "" + +#: ../Doc/library/http.cookies.rst:216 +msgid "" +"Update the values in the Morsel dictionary with the values in the dictionary " +"*values*. Raise an error if any of the keys in the *values* dict is not a " +"valid :rfc:`2109` attribute." +msgstr "" + +#: ../Doc/library/http.cookies.rst:220 +msgid "an error is raised for invalid keys." +msgstr "" + +#: ../Doc/library/http.cookies.rst:226 +msgid "Return a shallow copy of the Morsel object." +msgstr "" + +#: ../Doc/library/http.cookies.rst:228 +msgid "return a Morsel object instead of a dict." +msgstr "" + +#: ../Doc/library/http.cookies.rst:234 +msgid "" +"Raise an error if key is not a valid :rfc:`2109` attribute, otherwise behave " +"the same as :meth:`dict.setdefault`." +msgstr "" + +#: ../Doc/library/http.cookies.rst:243 +msgid "" +"The following example demonstrates how to use the :mod:`http.cookies` module." +msgstr "" + +#: ../Doc/library/http.server.rst:2 +msgid ":mod:`http.server` --- HTTP servers" +msgstr "" + +#: ../Doc/library/http.server.rst:7 +msgid "**Source code:** :source:`Lib/http/server.py`" +msgstr "" + +#: ../Doc/library/http.server.rst:17 +msgid "" +"This module defines classes for implementing HTTP servers (Web servers)." +msgstr "" + +#: ../Doc/library/http.server.rst:19 +msgid "" +"One class, :class:`HTTPServer`, is a :class:`socketserver.TCPServer` " +"subclass. It creates and listens at the HTTP socket, dispatching the " +"requests to a handler. Code to create and run the server looks like this::" +msgstr "" + +#: ../Doc/library/http.server.rst:31 +msgid "" +"This class builds on the :class:`~socketserver.TCPServer` class by storing " +"the server address as instance variables named :attr:`server_name` and :attr:" +"`server_port`. The server is accessible by the handler, typically through " +"the handler's :attr:`server` instance variable." +msgstr "" + +#: ../Doc/library/http.server.rst:37 +msgid "" +"The :class:`HTTPServer` must be given a *RequestHandlerClass* on " +"instantiation, of which this module provides three different variants:" +msgstr "" + +#: ../Doc/library/http.server.rst:42 +msgid "" +"This class is used to handle the HTTP requests that arrive at the server. " +"By itself, it cannot respond to any actual HTTP requests; it must be " +"subclassed to handle each request method (e.g. GET or POST). :class:" +"`BaseHTTPRequestHandler` provides a number of class and instance variables, " +"and methods for use by subclasses." +msgstr "" + +#: ../Doc/library/http.server.rst:48 +msgid "" +"The handler will parse the request and the headers, then call a method " +"specific to the request type. The method name is constructed from the " +"request. For example, for the request method ``SPAM``, the :meth:`do_SPAM` " +"method will be called with no arguments. All of the relevant information is " +"stored in instance variables of the handler. Subclasses should not need to " +"override or extend the :meth:`__init__` method." +msgstr "" + +#: ../Doc/library/http.server.rst:55 +msgid ":class:`BaseHTTPRequestHandler` has the following instance variables:" +msgstr "" + +#: ../Doc/library/http.server.rst:59 +msgid "" +"Contains a tuple of the form ``(host, port)`` referring to the client's " +"address." +msgstr "" + +#: ../Doc/library/http.server.rst:64 +msgid "Contains the server instance." +msgstr "" + +#: ../Doc/library/http.server.rst:68 +msgid "" +"Boolean that should be set before :meth:`handle_one_request` returns, " +"indicating if another request may be expected, or if the connection should " +"be shut down." +msgstr "" + +#: ../Doc/library/http.server.rst:74 +msgid "" +"Contains the string representation of the HTTP request line. The terminating " +"CRLF is stripped. This attribute should be set by :meth:" +"`handle_one_request`. If no valid request line was processed, it should be " +"set to the empty string." +msgstr "" + +#: ../Doc/library/http.server.rst:81 +msgid "Contains the command (request type). For example, ``'GET'``." +msgstr "" + +#: ../Doc/library/http.server.rst:85 +msgid "Contains the request path." +msgstr "" + +#: ../Doc/library/http.server.rst:89 +msgid "" +"Contains the version string from the request. For example, ``'HTTP/1.0'``." +msgstr "" + +#: ../Doc/library/http.server.rst:93 +msgid "" +"Holds an instance of the class specified by the :attr:`MessageClass` class " +"variable. This instance parses and manages the headers in the HTTP request. " +"The :func:`~http.client.parse_headers` function from :mod:`http.client` is " +"used to parse the headers and it requires that the HTTP request provide a " +"valid :rfc:`2822` style header." +msgstr "" + +#: ../Doc/library/http.server.rst:101 +msgid "" +"An :class:`io.BufferedIOBase` input stream, ready to read from the start of " +"the optional input data." +msgstr "" + +#: ../Doc/library/http.server.rst:106 +msgid "" +"Contains the output stream for writing a response back to the client. Proper " +"adherence to the HTTP protocol must be used when writing to this stream." +msgstr "" + +#: ../Doc/library/http.server.rst:110 +msgid "This is an :class:`io.BufferedIOBase` stream." +msgstr "" + +#: ../Doc/library/http.server.rst:113 +msgid ":class:`BaseHTTPRequestHandler` has the following attributes:" +msgstr "" + +#: ../Doc/library/http.server.rst:117 +msgid "" +"Specifies the server software version. You may want to override this. The " +"format is multiple whitespace-separated strings, where each string is of the " +"form name[/version]. For example, ``'BaseHTTP/0.2'``." +msgstr "" + +#: ../Doc/library/http.server.rst:123 +msgid "" +"Contains the Python system version, in a form usable by the :attr:" +"`version_string` method and the :attr:`server_version` class variable. For " +"example, ``'Python/1.4'``." +msgstr "" + +#: ../Doc/library/http.server.rst:129 +msgid "" +"Specifies a format string that should be used by :meth:`send_error` method " +"for building an error response to the client. The string is filled by " +"default with variables from :attr:`responses` based on the status code that " +"passed to :meth:`send_error`." +msgstr "" + +#: ../Doc/library/http.server.rst:136 +msgid "" +"Specifies the Content-Type HTTP header of error responses sent to the " +"client. The default value is ``'text/html'``." +msgstr "" + +#: ../Doc/library/http.server.rst:141 +msgid "" +"This specifies the HTTP protocol version used in responses. If set to " +"``'HTTP/1.1'``, the server will permit HTTP persistent connections; however, " +"your server *must* then include an accurate ``Content-Length`` header " +"(using :meth:`send_header`) in all of its responses to clients. For " +"backwards compatibility, the setting defaults to ``'HTTP/1.0'``." +msgstr "" + +#: ../Doc/library/http.server.rst:149 +msgid "" +"Specifies an :class:`email.message.Message`\\ -like class to parse HTTP " +"headers. Typically, this is not overridden, and it defaults to :class:`http." +"client.HTTPMessage`." +msgstr "" + +#: ../Doc/library/http.server.rst:155 +msgid "" +"This attribute contains a mapping of error code integers to two-element " +"tuples containing a short and long message. For example, ``{code: " +"(shortmessage, longmessage)}``. The *shortmessage* is usually used as the " +"*message* key in an error response, and *longmessage* as the *explain* key. " +"It is used by :meth:`send_response_only` and :meth:`send_error` methods." +msgstr "" + +#: ../Doc/library/http.server.rst:161 +msgid "A :class:`BaseHTTPRequestHandler` instance has the following methods:" +msgstr "" + +#: ../Doc/library/http.server.rst:165 +msgid "" +"Calls :meth:`handle_one_request` once (or, if persistent connections are " +"enabled, multiple times) to handle incoming HTTP requests. You should never " +"need to override it; instead, implement appropriate :meth:`do_\\*` methods." +msgstr "" + +#: ../Doc/library/http.server.rst:172 +msgid "" +"This method will parse and dispatch the request to the appropriate :meth:`do_" +"\\*` method. You should never need to override it." +msgstr "" + +#: ../Doc/library/http.server.rst:177 +msgid "" +"When a HTTP/1.1 compliant server receives an ``Expect: 100-continue`` " +"request header it responds back with a ``100 Continue`` followed by ``200 " +"OK`` headers. This method can be overridden to raise an error if the server " +"does not want the client to continue. For e.g. server can chose to send " +"``417 Expectation Failed`` as a response header and ``return False``." +msgstr "" + +#: ../Doc/library/http.server.rst:188 +msgid "" +"Sends and logs a complete error reply to the client. The numeric *code* " +"specifies the HTTP error code, with *message* as an optional, short, human " +"readable description of the error. The *explain* argument can be used to " +"provide more detailed information about the error; it will be formatted " +"using the :attr:`error_message_format` attribute and emitted, after a " +"complete set of headers, as the response body. The :attr:`responses` " +"attribute holds the default values for *message* and *explain* that will be " +"used if no value is provided; for unknown codes the default value for both " +"is the string ``???``. The body will be empty if the method is HEAD or the " +"response code is one of the following: ``1xx``, ``204 No Content``, ``205 " +"Reset Content``, ``304 Not Modified``." +msgstr "" + +#: ../Doc/library/http.server.rst:200 +msgid "" +"The error response includes a Content-Length header. Added the *explain* " +"argument." +msgstr "" + +#: ../Doc/library/http.server.rst:206 +msgid "" +"Adds a response header to the headers buffer and logs the accepted request. " +"The HTTP response line is written to the internal buffer, followed by " +"*Server* and *Date* headers. The values for these two headers are picked up " +"from the :meth:`version_string` and :meth:`date_time_string` methods, " +"respectively. If the server does not intend to send any other headers using " +"the :meth:`send_header` method, then :meth:`send_response` should be " +"followed by an :meth:`end_headers` call." +msgstr "" + +#: ../Doc/library/http.server.rst:215 +msgid "" +"Headers are stored to an internal buffer and :meth:`end_headers` needs to be " +"called explicitly." +msgstr "" + +#: ../Doc/library/http.server.rst:221 +msgid "" +"Adds the HTTP header to an internal buffer which will be written to the " +"output stream when either :meth:`end_headers` or :meth:`flush_headers` is " +"invoked. *keyword* should specify the header keyword, with *value* " +"specifying its value. Note that, after the send_header calls are done, :meth:" +"`end_headers` MUST BE called in order to complete the operation." +msgstr "" + +#: ../Doc/library/http.server.rst:227 +msgid "Headers are stored in an internal buffer." +msgstr "" + +#: ../Doc/library/http.server.rst:232 +msgid "" +"Sends the response header only, used for the purposes when ``100 Continue`` " +"response is sent by the server to the client. The headers not buffered and " +"sent directly the output stream.If the *message* is not specified, the HTTP " +"message corresponding the response *code* is sent." +msgstr "" + +#: ../Doc/library/http.server.rst:241 +msgid "" +"Adds a blank line (indicating the end of the HTTP headers in the response) " +"to the headers buffer and calls :meth:`flush_headers()`." +msgstr "" + +#: ../Doc/library/http.server.rst:245 +msgid "The buffered headers are written to the output stream." +msgstr "" + +#: ../Doc/library/http.server.rst:250 +msgid "" +"Finally send the headers to the output stream and flush the internal headers " +"buffer." +msgstr "" + +#: ../Doc/library/http.server.rst:257 +msgid "" +"Logs an accepted (successful) request. *code* should specify the numeric " +"HTTP code associated with the response. If a size of the response is " +"available, then it should be passed as the *size* parameter." +msgstr "" + +#: ../Doc/library/http.server.rst:263 +msgid "" +"Logs an error when a request cannot be fulfilled. By default, it passes the " +"message to :meth:`log_message`, so it takes the same arguments (*format* and " +"additional values)." +msgstr "" + +#: ../Doc/library/http.server.rst:270 +msgid "" +"Logs an arbitrary message to ``sys.stderr``. This is typically overridden to " +"create custom error logging mechanisms. The *format* argument is a standard " +"printf-style format string, where the additional arguments to :meth:" +"`log_message` are applied as inputs to the formatting. The client ip address " +"and current date and time are prefixed to every message logged." +msgstr "" + +#: ../Doc/library/http.server.rst:278 +msgid "" +"Returns the server software's version string. This is a combination of the :" +"attr:`server_version` and :attr:`sys_version` attributes." +msgstr "" + +#: ../Doc/library/http.server.rst:283 +msgid "" +"Returns the date and time given by *timestamp* (which must be None or in the " +"format returned by :func:`time.time`), formatted for a message header. If " +"*timestamp* is omitted, it uses the current date and time." +msgstr "" + +#: ../Doc/library/http.server.rst:287 +msgid "The result looks like ``'Sun, 06 Nov 1994 08:49:37 GMT'``." +msgstr "" + +#: ../Doc/library/http.server.rst:291 +msgid "Returns the current date and time, formatted for logging." +msgstr "" + +#: ../Doc/library/http.server.rst:295 +msgid "Returns the client address." +msgstr "" + +#: ../Doc/library/http.server.rst:297 +msgid "" +"Previously, a name lookup was performed. To avoid name resolution delays, it " +"now always returns the IP address." +msgstr "" + +#: ../Doc/library/http.server.rst:304 +msgid "" +"This class serves files from the current directory and below, directly " +"mapping the directory structure to HTTP requests." +msgstr "" + +#: ../Doc/library/http.server.rst:307 +msgid "" +"A lot of the work, such as parsing the request, is done by the base class :" +"class:`BaseHTTPRequestHandler`. This class implements the :func:`do_GET` " +"and :func:`do_HEAD` functions." +msgstr "" + +#: ../Doc/library/http.server.rst:311 +msgid "" +"The following are defined as class-level attributes of :class:" +"`SimpleHTTPRequestHandler`:" +msgstr "" + +#: ../Doc/library/http.server.rst:316 +msgid "" +"This will be ``\"SimpleHTTP/\" + __version__``, where ``__version__`` is " +"defined at the module level." +msgstr "" + +#: ../Doc/library/http.server.rst:321 +msgid "" +"A dictionary mapping suffixes into MIME types. The default is signified by " +"an empty string, and is considered to be ``application/octet-stream``. The " +"mapping is used case-insensitively, and so should contain only lower-cased " +"keys." +msgstr "" + +#: ../Doc/library/http.server.rst:326 +msgid "" +"The :class:`SimpleHTTPRequestHandler` class defines the following methods:" +msgstr "" + +#: ../Doc/library/http.server.rst:330 +msgid "" +"This method serves the ``'HEAD'`` request type: it sends the headers it " +"would send for the equivalent ``GET`` request. See the :meth:`do_GET` method " +"for a more complete explanation of the possible headers." +msgstr "" + +#: ../Doc/library/http.server.rst:336 +msgid "" +"The request is mapped to a local file by interpreting the request as a path " +"relative to the current working directory." +msgstr "" + +#: ../Doc/library/http.server.rst:339 +msgid "" +"If the request was mapped to a directory, the directory is checked for a " +"file named ``index.html`` or ``index.htm`` (in that order). If found, the " +"file's contents are returned; otherwise a directory listing is generated by " +"calling the :meth:`list_directory` method. This method uses :func:`os." +"listdir` to scan the directory, and returns a ``404`` error response if the :" +"func:`~os.listdir` fails." +msgstr "" + +#: ../Doc/library/http.server.rst:346 +msgid "" +"If the request was mapped to a file, it is opened and the contents are " +"returned. Any :exc:`OSError` exception in opening the requested file is " +"mapped to a ``404``, ``'File not found'`` error. Otherwise, the content type " +"is guessed by calling the :meth:`guess_type` method, which in turn uses the " +"*extensions_map* variable." +msgstr "" + +#: ../Doc/library/http.server.rst:352 +msgid "" +"A ``'Content-type:'`` header with the guessed content type is output, " +"followed by a ``'Content-Length:'`` header with the file's size and a " +"``'Last-Modified:'`` header with the file's modification time." +msgstr "" + +#: ../Doc/library/http.server.rst:356 +msgid "" +"Then follows a blank line signifying the end of the headers, and then the " +"contents of the file are output. If the file's MIME type starts with ``text/" +"`` the file is opened in text mode; otherwise binary mode is used." +msgstr "" + +#: ../Doc/library/http.server.rst:360 +msgid "" +"For example usage, see the implementation of the :func:`test` function " +"invocation in the :mod:`http.server` module." +msgstr "" + +#: ../Doc/library/http.server.rst:364 +msgid "" +"The :class:`SimpleHTTPRequestHandler` class can be used in the following " +"manner in order to create a very basic webserver serving files relative to " +"the current directory::" +msgstr "" + +#: ../Doc/library/http.server.rst:381 +msgid "" +":mod:`http.server` can also be invoked directly using the :option:`-m` " +"switch of the interpreter with a ``port number`` argument. Similar to the " +"previous example, this serves files relative to the current directory::" +msgstr "" + +#: ../Doc/library/http.server.rst:387 +msgid "" +"By default, server binds itself to all interfaces. The option ``-b/--bind`` " +"specifies a specific address to which it should bind. For example, the " +"following command causes the server to bind to localhost only::" +msgstr "" + +#: ../Doc/library/http.server.rst:393 +msgid "``--bind`` argument was introduced." +msgstr "" + +#: ../Doc/library/http.server.rst:399 +msgid "" +"This class is used to serve either files or output of CGI scripts from the " +"current directory and below. Note that mapping HTTP hierarchic structure to " +"local directory structure is exactly as in :class:`SimpleHTTPRequestHandler`." +msgstr "" + +#: ../Doc/library/http.server.rst:405 +msgid "" +"CGI scripts run by the :class:`CGIHTTPRequestHandler` class cannot execute " +"redirects (HTTP code 302), because code 200 (script output follows) is sent " +"prior to execution of the CGI script. This pre-empts the status code." +msgstr "" + +#: ../Doc/library/http.server.rst:410 +msgid "" +"The class will however, run the CGI script, instead of serving it as a file, " +"if it guesses it to be a CGI script. Only directory-based CGI are used --- " +"the other common server configuration is to treat special extensions as " +"denoting CGI scripts." +msgstr "" + +#: ../Doc/library/http.server.rst:415 +msgid "" +"The :func:`do_GET` and :func:`do_HEAD` functions are modified to run CGI " +"scripts and serve the output, instead of serving files, if the request leads " +"to somewhere below the ``cgi_directories`` path." +msgstr "" + +#: ../Doc/library/http.server.rst:419 +msgid "The :class:`CGIHTTPRequestHandler` defines the following data member:" +msgstr "" + +#: ../Doc/library/http.server.rst:423 +msgid "" +"This defaults to ``['/cgi-bin', '/htbin']`` and describes directories to " +"treat as containing CGI scripts." +msgstr "" + +#: ../Doc/library/http.server.rst:426 +msgid "The :class:`CGIHTTPRequestHandler` defines the following method:" +msgstr "" + +#: ../Doc/library/http.server.rst:430 +msgid "" +"This method serves the ``'POST'`` request type, only allowed for CGI " +"scripts. Error 501, \"Can only POST to CGI scripts\", is output when trying " +"to POST to a non-CGI url." +msgstr "" + +#: ../Doc/library/http.server.rst:434 +msgid "" +"Note that CGI scripts will be run with UID of user nobody, for security " +"reasons. Problems with the CGI script will be translated to error 403." +msgstr "" + +#: ../Doc/library/http.server.rst:437 +msgid "" +":class:`CGIHTTPRequestHandler` can be enabled in the command line by passing " +"the ``--cgi`` option::" +msgstr "" + +#: ../Doc/library/i18n.rst:5 +msgid "Internationalization" +msgstr "" + +#: ../Doc/library/i18n.rst:7 +msgid "" +"The modules described in this chapter help you write software that is " +"independent of language and locale by providing mechanisms for selecting a " +"language to be used in program messages or by tailoring output to match " +"local conventions." +msgstr "" + +#: ../Doc/library/idle.rst:4 +msgid "IDLE" +msgstr "" + +#: ../Doc/library/idle.rst:8 +msgid "**Source code:** :source:`Lib/idlelib/`" +msgstr "" + +#: ../Doc/library/idle.rst:17 +msgid "IDLE is Python's Integrated Development and Learning Environment." +msgstr "" + +#: ../Doc/library/idle.rst:19 +msgid "IDLE has the following features:" +msgstr "" + +#: ../Doc/library/idle.rst:21 +msgid "coded in 100% pure Python, using the :mod:`tkinter` GUI toolkit" +msgstr "" + +#: ../Doc/library/idle.rst:23 +msgid "cross-platform: works mostly the same on Windows, Unix, and Mac OS X" +msgstr "" + +#: ../Doc/library/idle.rst:25 +msgid "" +"Python shell window (interactive interpreter) with colorizing of code input, " +"output, and error messages" +msgstr "" + +#: ../Doc/library/idle.rst:28 +msgid "" +"multi-window text editor with multiple undo, Python colorizing, smart " +"indent, call tips, auto completion, and other features" +msgstr "" + +#: ../Doc/library/idle.rst:31 +msgid "" +"search within any window, replace within editor windows, and search through " +"multiple files (grep)" +msgstr "" + +#: ../Doc/library/idle.rst:34 +msgid "" +"debugger with persistent breakpoints, stepping, and viewing of global and " +"local namespaces" +msgstr "" + +#: ../Doc/library/idle.rst:37 +msgid "configuration, browsers, and other dialogs" +msgstr "" + +#: ../Doc/library/idle.rst:40 +msgid "Menus" +msgstr "" + +#: ../Doc/library/idle.rst:42 +msgid "" +"IDLE has two main window types, the Shell window and the Editor window. It " +"is possible to have multiple editor windows simultaneously. Output windows, " +"such as used for Edit / Find in Files, are a subtype of edit window. They " +"currently have the same top menu as Editor windows but a different default " +"title and context menu." +msgstr "" + +#: ../Doc/library/idle.rst:48 +msgid "" +"IDLE's menus dynamically change based on which window is currently selected. " +"Each menu documented below indicates which window type it is associated with." +msgstr "" + +#: ../Doc/library/idle.rst:52 +msgid "File menu (Shell and Editor)" +msgstr "" + +#: ../Doc/library/idle.rst:55 +msgid "New File" +msgstr "" + +#: ../Doc/library/idle.rst:55 +msgid "Create a new file editing window." +msgstr "" + +#: ../Doc/library/idle.rst:58 +msgid "Open..." +msgstr "" + +#: ../Doc/library/idle.rst:58 +msgid "Open an existing file with an Open dialog." +msgstr "" + +#: ../Doc/library/idle.rst:61 +msgid "Recent Files" +msgstr "" + +#: ../Doc/library/idle.rst:61 +msgid "Open a list of recent files. Click one to open it." +msgstr "" + +#: ../Doc/library/idle.rst:64 +msgid "Open Module..." +msgstr "" + +#: ../Doc/library/idle.rst:64 +msgid "Open an existing module (searches sys.path)." +msgstr "" + +#: ../Doc/library/idle.rst:72 +msgid "Class Browser" +msgstr "" + +#: ../Doc/library/idle.rst:71 +msgid "" +"Show functions, classes, and methods in the current Editor file in a tree " +"structure. In the shell, open a module first." +msgstr "" + +#: ../Doc/library/idle.rst:76 +msgid "Path Browser" +msgstr "" + +#: ../Doc/library/idle.rst:75 +msgid "" +"Show sys.path directories, modules, functions, classes and methods in a tree " +"structure." +msgstr "" + +#: ../Doc/library/idle.rst:79 +msgid "" +"Save the current window to the associated file, if there is one. Windows " +"that have been changed since being opened or last saved have a \\* before " +"and after the window title. If there is no associated file, do Save As " +"instead." +msgstr "" + +#: ../Doc/library/idle.rst:86 +msgid "Save As..." +msgstr "" + +#: ../Doc/library/idle.rst:85 +msgid "" +"Save the current window with a Save As dialog. The file saved becomes the " +"new associated file for the window." +msgstr "" + +#: ../Doc/library/idle.rst:90 +msgid "Save Copy As..." +msgstr "" + +#: ../Doc/library/idle.rst:89 +msgid "" +"Save the current window to different file without changing the associated " +"file." +msgstr "" + +#: ../Doc/library/idle.rst:93 +msgid "Print Window" +msgstr "" + +#: ../Doc/library/idle.rst:93 +msgid "Print the current window to the default printer." +msgstr "" + +#: ../Doc/library/idle.rst:96 +msgid "Close the current window (ask to save if unsaved)." +msgstr "" + +#: ../Doc/library/idle.rst:99 +msgid "Close all windows and quit IDLE (ask to save unsaved windows)." +msgstr "" + +#: ../Doc/library/idle.rst:102 +msgid "Edit menu (Shell and Editor)" +msgstr "" + +#: ../Doc/library/idle.rst:105 +msgid "" +"Undo the last change to the current window. A maximum of 1000 changes may " +"be undone." +msgstr "" + +#: ../Doc/library/idle.rst:109 +msgid "Redo the last undone change to the current window." +msgstr "" + +#: ../Doc/library/idle.rst:112 ../Doc/library/idle.rst:323 +msgid "Cut" +msgstr "" + +#: ../Doc/library/idle.rst:112 ../Doc/library/idle.rst:323 +msgid "" +"Copy selection into the system-wide clipboard; then delete the selection." +msgstr "" + +#: ../Doc/library/idle.rst:115 ../Doc/library/idle.rst:326 +msgid "Copy selection into the system-wide clipboard." +msgstr "" + +#: ../Doc/library/idle.rst:118 ../Doc/library/idle.rst:329 +msgid "Paste" +msgstr "" + +#: ../Doc/library/idle.rst:118 ../Doc/library/idle.rst:329 +msgid "Insert contents of the system-wide clipboard into the current window." +msgstr "" + +#: ../Doc/library/idle.rst:120 +msgid "The clipboard functions are also available in context menus." +msgstr "" + +#: ../Doc/library/idle.rst:123 +msgid "Select All" +msgstr "" + +#: ../Doc/library/idle.rst:123 +msgid "Select the entire contents of the current window." +msgstr "" + +#: ../Doc/library/idle.rst:126 +msgid "Find..." +msgstr "" + +#: ../Doc/library/idle.rst:126 +msgid "Open a search dialog with many options" +msgstr "" + +#: ../Doc/library/idle.rst:129 +msgid "Find Again" +msgstr "" + +#: ../Doc/library/idle.rst:129 +msgid "Repeat the last search, if there is one." +msgstr "" + +#: ../Doc/library/idle.rst:132 +msgid "Find Selection" +msgstr "" + +#: ../Doc/library/idle.rst:132 +msgid "Search for the currently selected string, if there is one." +msgstr "" + +#: ../Doc/library/idle.rst:135 +msgid "Find in Files..." +msgstr "" + +#: ../Doc/library/idle.rst:135 +msgid "Open a file search dialog. Put results in a new output window." +msgstr "" + +#: ../Doc/library/idle.rst:138 +msgid "Replace..." +msgstr "" + +#: ../Doc/library/idle.rst:138 +msgid "Open a search-and-replace dialog." +msgstr "" + +#: ../Doc/library/idle.rst:141 +msgid "Go to Line" +msgstr "" + +#: ../Doc/library/idle.rst:141 +msgid "Move cursor to the line number requested and make that line visible." +msgstr "" + +#: ../Doc/library/idle.rst:145 +msgid "Show Completions" +msgstr "" + +#: ../Doc/library/idle.rst:144 +msgid "" +"Open a scrollable list allowing selection of keywords and attributes. See " +"Completions in the Tips sections below." +msgstr "" + +#: ../Doc/library/idle.rst:149 +msgid "Expand Word" +msgstr "" + +#: ../Doc/library/idle.rst:148 +msgid "" +"Expand a prefix you have typed to match a full word in the same window; " +"repeat to get a different expansion." +msgstr "" + +#: ../Doc/library/idle.rst:153 +msgid "Show call tip" +msgstr "" + +#: ../Doc/library/idle.rst:152 +msgid "" +"After an unclosed parenthesis for a function, open a small window with " +"function parameter hints." +msgstr "" + +#: ../Doc/library/idle.rst:156 +msgid "Show surrounding parens" +msgstr "" + +#: ../Doc/library/idle.rst:156 +msgid "Highlight the surrounding parenthesis." +msgstr "" + +#: ../Doc/library/idle.rst:159 +msgid "Format menu (Editor window only)" +msgstr "" + +#: ../Doc/library/idle.rst:162 +msgid "Indent Region" +msgstr "" + +#: ../Doc/library/idle.rst:162 +msgid "Shift selected lines right by the indent width (default 4 spaces)." +msgstr "" + +#: ../Doc/library/idle.rst:165 +msgid "Dedent Region" +msgstr "" + +#: ../Doc/library/idle.rst:165 +msgid "Shift selected lines left by the indent width (default 4 spaces)." +msgstr "" + +#: ../Doc/library/idle.rst:168 +msgid "Comment Out Region" +msgstr "" + +#: ../Doc/library/idle.rst:168 +msgid "Insert ## in front of selected lines." +msgstr "" + +#: ../Doc/library/idle.rst:171 +msgid "Uncomment Region" +msgstr "" + +#: ../Doc/library/idle.rst:171 +msgid "Remove leading # or ## from selected lines." +msgstr "" + +#: ../Doc/library/idle.rst:175 +msgid "Tabify Region" +msgstr "" + +#: ../Doc/library/idle.rst:174 +msgid "" +"Turn *leading* stretches of spaces into tabs. (Note: We recommend using 4 " +"space blocks to indent Python code.)" +msgstr "" + +#: ../Doc/library/idle.rst:178 +msgid "Untabify Region" +msgstr "" + +#: ../Doc/library/idle.rst:178 +msgid "Turn *all* tabs into the correct number of spaces." +msgstr "" + +#: ../Doc/library/idle.rst:181 +msgid "Toggle Tabs" +msgstr "" + +#: ../Doc/library/idle.rst:181 +msgid "Open a dialog to switch between indenting with spaces and tabs." +msgstr "" + +#: ../Doc/library/idle.rst:185 +msgid "New Indent Width" +msgstr "" + +#: ../Doc/library/idle.rst:184 +msgid "" +"Open a dialog to change indent width. The accepted default by the Python " +"community is 4 spaces." +msgstr "" + +#: ../Doc/library/idle.rst:190 +msgid "Format Paragraph" +msgstr "" + +#: ../Doc/library/idle.rst:188 +msgid "" +"Reformat the current blank-line-delimited paragraph in comment block or " +"multiline string or selected line in a string. All lines in the paragraph " +"will be formatted to less than N columns, where N defaults to 72." +msgstr "" + +#: ../Doc/library/idle.rst:193 +msgid "Strip trailing whitespace" +msgstr "" + +#: ../Doc/library/idle.rst:193 +msgid "" +"Remove any space characters after the last non-space character of a line." +msgstr "" + +#: ../Doc/library/idle.rst:199 +msgid "Run menu (Editor window only)" +msgstr "" + +#: ../Doc/library/idle.rst:202 +msgid "Python Shell" +msgstr "" + +#: ../Doc/library/idle.rst:202 +msgid "Open or wake up the Python Shell window." +msgstr "" + +#: ../Doc/library/idle.rst:209 +msgid "Check Module" +msgstr "" + +#: ../Doc/library/idle.rst:205 +msgid "" +"Check the syntax of the module currently open in the Editor window. If the " +"module has not been saved IDLE will either prompt the user to save or " +"autosave, as selected in the General tab of the Idle Settings dialog. If " +"there is a syntax error, the approximate location is indicated in the Editor " +"window." +msgstr "" + +#: ../Doc/library/idle.rst:218 +msgid "Run Module" +msgstr "" + +#: ../Doc/library/idle.rst:212 +msgid "" +"Do Check Module (above). If no error, restart the shell to clean the " +"environment, then execute the module. Output is displayed in the Shell " +"window. Note that output requires use of ``print`` or ``write``. When " +"execution is complete, the Shell retains focus and displays a prompt. At " +"this point, one may interactively explore the result of execution. This is " +"similar to executing a file with ``python -i file`` at a command line." +msgstr "" + +#: ../Doc/library/idle.rst:221 +msgid "Shell menu (Shell window only)" +msgstr "" + +#: ../Doc/library/idle.rst:224 +msgid "View Last Restart" +msgstr "" + +#: ../Doc/library/idle.rst:224 +msgid "Scroll the shell window to the last Shell restart." +msgstr "" + +#: ../Doc/library/idle.rst:227 +msgid "Restart Shell" +msgstr "" + +#: ../Doc/library/idle.rst:227 +msgid "Restart the shell to clean the environment." +msgstr "" + +#: ../Doc/library/idle.rst:230 +msgid "Interrupt Execution" +msgstr "" + +#: ../Doc/library/idle.rst:230 +msgid "Stop a running program." +msgstr "" + +#: ../Doc/library/idle.rst:233 +msgid "Debug menu (Shell window only)" +msgstr "" + +#: ../Doc/library/idle.rst:240 +msgid "Go to File/Line" +msgstr "" + +#: ../Doc/library/idle.rst:236 +msgid "" +"Look on the current line. with the cursor, and the line above for a filename " +"and line number. If found, open the file if not already open, and show the " +"line. Use this to view source lines referenced in an exception traceback " +"and lines found by Find in Files. Also available in the context menu of the " +"Shell window and Output windows." +msgstr "" + +#: ../Doc/library/idle.rst:249 +msgid "Debugger (toggle)" +msgstr "" + +#: ../Doc/library/idle.rst:247 +msgid "" +"When actived, code entered in the Shell or run from an Editor will run under " +"the debugger. In the Editor, breakpoints can be set with the context menu. " +"This feature is still incomplete and somewhat experimental." +msgstr "" + +#: ../Doc/library/idle.rst:253 +msgid "Stack Viewer" +msgstr "" + +#: ../Doc/library/idle.rst:252 +msgid "" +"Show the stack traceback of the last exception in a tree widget, with access " +"to locals and globals." +msgstr "" + +#: ../Doc/library/idle.rst:256 +msgid "Auto-open Stack Viewer" +msgstr "" + +#: ../Doc/library/idle.rst:256 +msgid "" +"Toggle automatically opening the stack viewer on an unhandled exception." +msgstr "" + +#: ../Doc/library/idle.rst:259 +msgid "Options menu (Shell and Editor)" +msgstr "" + +#: ../Doc/library/idle.rst:271 +msgid "Configure IDLE" +msgstr "" + +#: ../Doc/library/idle.rst:262 +msgid "" +"Open a configuration dialog and change preferences for the following: fonts, " +"indentation, keybindings, text color themes, startup windows and size, " +"additional help sources, and extensions (see below). On OS X, open the " +"configuration dialog by selecting Preferences in the application menu. To " +"use a new built-in color theme (IDLE Dark) with older IDLEs, save it as a " +"new custom theme." +msgstr "" + +#: ../Doc/library/idle.rst:269 +msgid "" +"Non-default user settings are saved in a .idlerc directory in the user's " +"home directory. Problems caused by bad user configuration files are solved " +"by editing or deleting one or more of the files in .idlerc." +msgstr "" + +#: ../Doc/library/idle.rst:275 +msgid "Code Context (toggle)(Editor Window only)" +msgstr "" + +#: ../Doc/library/idle.rst:274 +msgid "" +"Open a pane at the top of the edit window which shows the block context of " +"the code which has scrolled above the top of the window." +msgstr "" + +#: ../Doc/library/idle.rst:278 +msgid "Window menu (Shell and Editor)" +msgstr "" + +#: ../Doc/library/idle.rst:283 +msgid "Zoom Height" +msgstr "" + +#: ../Doc/library/idle.rst:281 +msgid "" +"Toggles the window between normal size and maximum height. The initial size " +"defaults to 40 lines by 80 chars unless changed on the General tab of the " +"Configure IDLE dialog." +msgstr "" + +#: ../Doc/library/idle.rst:285 +msgid "" +"The rest of this menu lists the names of all open windows; select one to " +"bring it to the foreground (deiconifying it if necessary)." +msgstr "" + +#: ../Doc/library/idle.rst:289 +msgid "Help menu (Shell and Editor)" +msgstr "" + +#: ../Doc/library/idle.rst:292 +msgid "About IDLE" +msgstr "" + +#: ../Doc/library/idle.rst:292 +msgid "Display version, copyright, license, credits, and more." +msgstr "" + +#: ../Doc/library/idle.rst:296 +msgid "IDLE Help" +msgstr "" + +#: ../Doc/library/idle.rst:295 +msgid "" +"Display a help file for IDLE detailing the menu options, basic editing and " +"navigation, and other tips." +msgstr "" + +#: ../Doc/library/idle.rst:300 +msgid "Python Docs" +msgstr "" + +#: ../Doc/library/idle.rst:299 +msgid "" +"Access local Python documentation, if installed, or start a web browser and " +"open docs.python.org showing the latest Python documentation." +msgstr "" + +#: ../Doc/library/idle.rst:303 +msgid "Turtle Demo" +msgstr "" + +#: ../Doc/library/idle.rst:303 +msgid "Run the turtledemo module with example python code and turtle drawings." +msgstr "" + +#: ../Doc/library/idle.rst:305 +msgid "" +"Additional help sources may be added here with the Configure IDLE dialog " +"under the General tab." +msgstr "" + +#: ../Doc/library/idle.rst:317 +msgid "Context Menus" +msgstr "" + +#: ../Doc/library/idle.rst:319 +msgid "" +"Open a context menu by right-clicking in a window (Control-click on OS X). " +"Context menus have the standard clipboard functions also on the Edit menu." +msgstr "" + +#: ../Doc/library/idle.rst:331 +msgid "" +"Editor windows also have breakpoint functions. Lines with a breakpoint set " +"are specially marked. Breakpoints only have an effect when running under " +"the debugger. Breakpoints for a file are saved in the user's .idlerc " +"directory." +msgstr "" + +#: ../Doc/library/idle.rst:336 +msgid "Set Breakpoint" +msgstr "" + +#: ../Doc/library/idle.rst:336 +msgid "Set a breakpoint on the current line." +msgstr "" + +#: ../Doc/library/idle.rst:339 +msgid "Clear Breakpoint" +msgstr "" + +#: ../Doc/library/idle.rst:339 +msgid "Clear the breakpoint on that line." +msgstr "" + +#: ../Doc/library/idle.rst:341 +msgid "Shell and Output windows have the following." +msgstr "" + +#: ../Doc/library/idle.rst:345 +msgid "Go to file/line" +msgstr "" + +#: ../Doc/library/idle.rst:344 +msgid "Same as in Debug menu." +msgstr "" + +#: ../Doc/library/idle.rst:348 +msgid "Editing and navigation" +msgstr "" + +#: ../Doc/library/idle.rst:350 +msgid "" +"In this section, 'C' refers to the :kbd:`Control` key on Windows and Unix " +"and the :kbd:`Command` key on Mac OSX." +msgstr "" + +#: ../Doc/library/idle.rst:353 +msgid ":kbd:`Backspace` deletes to the left; :kbd:`Del` deletes to the right" +msgstr "" + +#: ../Doc/library/idle.rst:355 +msgid "" +":kbd:`C-Backspace` delete word left; :kbd:`C-Del` delete word to the right" +msgstr "" + +#: ../Doc/library/idle.rst:357 +msgid "Arrow keys and :kbd:`Page Up`/:kbd:`Page Down` to move around" +msgstr "" + +#: ../Doc/library/idle.rst:359 +msgid ":kbd:`C-LeftArrow` and :kbd:`C-RightArrow` moves by words" +msgstr "" + +#: ../Doc/library/idle.rst:361 +msgid ":kbd:`Home`/:kbd:`End` go to begin/end of line" +msgstr "" + +#: ../Doc/library/idle.rst:363 +msgid ":kbd:`C-Home`/:kbd:`C-End` go to begin/end of file" +msgstr "" + +#: ../Doc/library/idle.rst:365 +msgid "Some useful Emacs bindings are inherited from Tcl/Tk:" +msgstr "" + +#: ../Doc/library/idle.rst:367 +msgid ":kbd:`C-a` beginning of line" +msgstr "" + +#: ../Doc/library/idle.rst:369 +msgid ":kbd:`C-e` end of line" +msgstr "" + +#: ../Doc/library/idle.rst:371 +msgid ":kbd:`C-k` kill line (but doesn't put it in clipboard)" +msgstr "" + +#: ../Doc/library/idle.rst:373 +msgid ":kbd:`C-l` center window around the insertion point" +msgstr "" + +#: ../Doc/library/idle.rst:375 +msgid "" +":kbd:`C-b` go backwards one character without deleting (usually you can also " +"use the cursor key for this)" +msgstr "" + +#: ../Doc/library/idle.rst:378 +msgid "" +":kbd:`C-f` go forward one character without deleting (usually you can also " +"use the cursor key for this)" +msgstr "" + +#: ../Doc/library/idle.rst:381 +msgid "" +":kbd:`C-p` go up one line (usually you can also use the cursor key for this)" +msgstr "" + +#: ../Doc/library/idle.rst:384 +msgid ":kbd:`C-d` delete next character" +msgstr "" + +#: ../Doc/library/idle.rst:386 +msgid "" +"Standard keybindings (like :kbd:`C-c` to copy and :kbd:`C-v` to paste) may " +"work. Keybindings are selected in the Configure IDLE dialog." +msgstr "" + +#: ../Doc/library/idle.rst:391 +msgid "Automatic indentation" +msgstr "" + +#: ../Doc/library/idle.rst:393 +msgid "" +"After a block-opening statement, the next line is indented by 4 spaces (in " +"the Python Shell window by one tab). After certain keywords (break, return " +"etc.) the next line is dedented. In leading indentation, :kbd:`Backspace` " +"deletes up to 4 spaces if they are there. :kbd:`Tab` inserts spaces (in the " +"Python Shell window one tab), number depends on Indent width. Currently tabs " +"are restricted to four spaces due to Tcl/Tk limitations." +msgstr "" + +#: ../Doc/library/idle.rst:400 +msgid "See also the indent/dedent region commands in the edit menu." +msgstr "" + +#: ../Doc/library/idle.rst:403 +msgid "Completions" +msgstr "" + +#: ../Doc/library/idle.rst:405 +msgid "" +"Completions are supplied for functions, classes, and attributes of classes, " +"both built-in and user-defined. Completions are also provided for filenames." +msgstr "" + +#: ../Doc/library/idle.rst:409 +msgid "" +"The AutoCompleteWindow (ACW) will open after a predefined delay (default is " +"two seconds) after a '.' or (in a string) an os.sep is typed. If after one " +"of those characters (plus zero or more other characters) a tab is typed the " +"ACW will open immediately if a possible continuation is found." +msgstr "" + +#: ../Doc/library/idle.rst:414 +msgid "" +"If there is only one possible completion for the characters entered, a :kbd:" +"`Tab` will supply that completion without opening the ACW." +msgstr "" + +#: ../Doc/library/idle.rst:417 +msgid "" +"'Show Completions' will force open a completions window, by default the :kbd:" +"`C-space` will open a completions window. In an empty string, this will " +"contain the files in the current directory. On a blank line, it will contain " +"the built-in and user-defined functions and classes in the current name " +"spaces, plus any modules imported. If some characters have been entered, the " +"ACW will attempt to be more specific." +msgstr "" + +#: ../Doc/library/idle.rst:424 +msgid "" +"If a string of characters is typed, the ACW selection will jump to the entry " +"most closely matching those characters. Entering a :kbd:`tab` will cause " +"the longest non-ambiguous match to be entered in the Editor window or " +"Shell. Two :kbd:`tab` in a row will supply the current ACW selection, as " +"will return or a double click. Cursor keys, Page Up/Down, mouse selection, " +"and the scroll wheel all operate on the ACW." +msgstr "" + +#: ../Doc/library/idle.rst:431 +msgid "" +"\"Hidden\" attributes can be accessed by typing the beginning of hidden name " +"after a '.', e.g. '_'. This allows access to modules with ``__all__`` set, " +"or to class-private attributes." +msgstr "" + +#: ../Doc/library/idle.rst:435 +msgid "Completions and the 'Expand Word' facility can save a lot of typing!" +msgstr "" + +#: ../Doc/library/idle.rst:437 +msgid "" +"Completions are currently limited to those in the namespaces. Names in an " +"Editor window which are not via ``__main__`` and :data:`sys.modules` will " +"not be found. Run the module once with your imports to correct this " +"situation. Note that IDLE itself places quite a few modules in sys.modules, " +"so much can be found by default, e.g. the re module." +msgstr "" + +#: ../Doc/library/idle.rst:443 +msgid "" +"If you don't like the ACW popping up unbidden, simply make the delay longer " +"or disable the extension." +msgstr "" + +#: ../Doc/library/idle.rst:447 +msgid "Calltips" +msgstr "" + +#: ../Doc/library/idle.rst:449 +msgid "" +"A calltip is shown when one types :kbd:`(` after the name of an " +"*acccessible* function. A name expression may include dots and subscripts. " +"A calltip remains until it is clicked, the cursor is moved out of the " +"argument area, or :kbd:`)` is typed. When the cursor is in the argument " +"part of a definition, the menu or shortcut display a calltip." +msgstr "" + +#: ../Doc/library/idle.rst:455 +msgid "" +"A calltip consists of the function signature and the first line of the " +"docstring. For builtins without an accessible signature, the calltip " +"consists of all lines up the fifth line or the first blank line. These " +"details may change." +msgstr "" + +#: ../Doc/library/idle.rst:460 +msgid "" +"The set of *accessible* functions depends on what modules have been imported " +"into the user process, including those imported by Idle itself, and what " +"definitions have been run, all since the last restart." +msgstr "" + +#: ../Doc/library/idle.rst:464 +msgid "" +"For example, restart the Shell and enter ``itertools.count(``. A calltip " +"appears because Idle imports itertools into the user process for its own " +"use. (This could change.) Enter ``turtle.write(`` and nothing appears. " +"Idle does not import turtle. The menu or shortcut do nothing either. Enter " +"``import turtle`` and then ``turtle.write(`` will work." +msgstr "" + +#: ../Doc/library/idle.rst:470 +msgid "" +"In an editor, import statements have no effect until one runs the file. One " +"might want to run a file after writing the import statements at the top, or " +"immediately run an existing file before editing." +msgstr "" + +#: ../Doc/library/idle.rst:475 +msgid "Python Shell window" +msgstr "" + +#: ../Doc/library/idle.rst:477 +msgid ":kbd:`C-c` interrupts executing command" +msgstr "" + +#: ../Doc/library/idle.rst:479 +msgid "" +":kbd:`C-d` sends end-of-file; closes window if typed at a ``>>>`` prompt" +msgstr "" + +#: ../Doc/library/idle.rst:481 +msgid ":kbd:`Alt-/` (Expand word) is also useful to reduce typing" +msgstr "" + +#: ../Doc/library/idle.rst:483 +msgid "Command history" +msgstr "" + +#: ../Doc/library/idle.rst:485 +msgid "" +":kbd:`Alt-p` retrieves previous command matching what you have typed. On OS " +"X use :kbd:`C-p`." +msgstr "" + +#: ../Doc/library/idle.rst:488 +msgid ":kbd:`Alt-n` retrieves next. On OS X use :kbd:`C-n`." +msgstr "" + +#: ../Doc/library/idle.rst:490 +msgid ":kbd:`Return` while on any previous command retrieves that command" +msgstr "" + +#: ../Doc/library/idle.rst:494 +msgid "Text colors" +msgstr "" + +#: ../Doc/library/idle.rst:496 +msgid "" +"Idle defaults to black on white text, but colors text with special meanings. " +"For the shell, these are shell output, shell error, user output, and user " +"error. For Python code, at the shell prompt or in an editor, these are " +"keywords, builtin class and function names, names following ``class`` and " +"``def``, strings, and comments. For any text window, these are the cursor " +"(when present), found text (when possible), and selected text." +msgstr "" + +#: ../Doc/library/idle.rst:503 +msgid "" +"Text coloring is done in the background, so uncolorized text is occasionally " +"visible. To change the color scheme, use the Configure IDLE dialog " +"Highlighting tab. The marking of debugger breakpoint lines in the editor " +"and text in popups and dialogs is not user-configurable." +msgstr "" + +#: ../Doc/library/idle.rst:510 +msgid "Startup and code execution" +msgstr "" + +#: ../Doc/library/idle.rst:512 +msgid "" +"Upon startup with the ``-s`` option, IDLE will execute the file referenced " +"by the environment variables :envvar:`IDLESTARTUP` or :envvar:" +"`PYTHONSTARTUP`. IDLE first checks for ``IDLESTARTUP``; if ``IDLESTARTUP`` " +"is present the file referenced is run. If ``IDLESTARTUP`` is not present, " +"IDLE checks for ``PYTHONSTARTUP``. Files referenced by these environment " +"variables are convenient places to store functions that are used frequently " +"from the IDLE shell, or for executing import statements to import common " +"modules." +msgstr "" + +#: ../Doc/library/idle.rst:520 +msgid "" +"In addition, ``Tk`` also loads a startup file if it is present. Note that " +"the Tk file is loaded unconditionally. This additional file is ``.Idle.py`` " +"and is looked for in the user's home directory. Statements in this file " +"will be executed in the Tk namespace, so this file is not useful for " +"importing functions to be used from IDLE's Python shell." +msgstr "" + +#: ../Doc/library/idle.rst:528 ../Doc/library/pickletools.rst:21 +msgid "Command line usage" +msgstr "" + +#: ../Doc/library/idle.rst:544 +msgid "If there are arguments:" +msgstr "" + +#: ../Doc/library/idle.rst:546 +msgid "" +"If ``-``, ``-c``, or ``r`` is used, all arguments are placed in ``sys." +"argv[1:...]`` and ``sys.argv[0]`` is set to ``''``, ``'-c'``, or ``'-r'``. " +"No editor window is opened, even if that is the default set in the Options " +"dialog." +msgstr "" + +#: ../Doc/library/idle.rst:551 +msgid "" +"Otherwise, arguments are files opened for editing and ``sys.argv`` reflects " +"the arguments passed to IDLE itself." +msgstr "" + +#: ../Doc/library/idle.rst:556 +msgid "IDLE-console differences" +msgstr "" + +#: ../Doc/library/idle.rst:558 +msgid "" +"As much as possible, the result of executing Python code with IDLE is the " +"same as executing the same code in a console window. However, the different " +"interface and operation occasionally affects visible results. For instance, " +"``sys.modules`` starts with more entries." +msgstr "" + +#: ../Doc/library/idle.rst:563 +msgid "" +"IDLE also replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` with " +"objects that get input from and send output to the Shell window. When this " +"window has the focus, it controls the keyboard and screen. This is normally " +"transparent, but functions that directly access the keyboard and screen will " +"not work. If ``sys`` is reset with ``importlib.reload(sys)``, IDLE's " +"changes are lost and things like ``input``, ``raw_input``, and ``print`` " +"will not work correctly." +msgstr "" + +#: ../Doc/library/idle.rst:571 +msgid "" +"With IDLE's Shell, one enters, edits, and recalls complete statements. Some " +"consoles only work with a single physical line at a time. IDLE uses " +"``exec`` to run each statement. As a result, ``'__builtins__'`` is always " +"defined for each statement." +msgstr "" + +#: ../Doc/library/idle.rst:577 +msgid "Running without a subprocess" +msgstr "" + +#: ../Doc/library/idle.rst:579 +msgid "" +"By default, IDLE executes user code in a separate subprocess via a socket, " +"which uses the internal loopback interface. This connection is not " +"externally visible and no data is sent to or received from the Internet. If " +"firewall software complains anyway, you can ignore it." +msgstr "" + +#: ../Doc/library/idle.rst:584 +msgid "" +"If the attempt to make the socket connection fails, Idle will notify you. " +"Such failures are sometimes transient, but if persistent, the problem may be " +"either a firewall blocking the connecton or misconfiguration of a particular " +"system. Until the problem is fixed, one can run Idle with the -n command " +"line switch." +msgstr "" + +#: ../Doc/library/idle.rst:590 +msgid "" +"If IDLE is started with the -n command line switch it will run in a single " +"process and will not create the subprocess which runs the RPC Python " +"execution server. This can be useful if Python cannot create the subprocess " +"or the RPC socket interface on your platform. However, in this mode user " +"code is not isolated from IDLE itself. Also, the environment is not " +"restarted when Run/Run Module (F5) is selected. If your code has been " +"modified, you must reload() the affected modules and re-import any specific " +"items (e.g. from foo import baz) if the changes are to take effect. For " +"these reasons, it is preferable to run IDLE with the default subprocess if " +"at all possible." +msgstr "" + +#: ../Doc/library/idle.rst:605 +msgid "Help and preferences" +msgstr "" + +#: ../Doc/library/idle.rst:608 +msgid "Additional help sources" +msgstr "" + +#: ../Doc/library/idle.rst:610 +msgid "" +"IDLE includes a help menu entry called \"Python Docs\" that will open the " +"extensive sources of help, including tutorials, available at docs.python." +"org. Selected URLs can be added or removed from the help menu at any time " +"using the Configure IDLE dialog. See the IDLE help option in the help menu " +"of IDLE for more information." +msgstr "" + +#: ../Doc/library/idle.rst:618 +msgid "Setting preferences" +msgstr "" + +#: ../Doc/library/idle.rst:620 +msgid "" +"The font preferences, highlighting, keys, and general preferences can be " +"changed via Configure IDLE on the Option menu. Keys can be user defined; " +"IDLE ships with four built in key sets. In addition a user can create a " +"custom key set in the Configure IDLE dialog under the keys tab." +msgstr "" + +#: ../Doc/library/idle.rst:627 +msgid "Extensions" +msgstr "" + +#: ../Doc/library/idle.rst:629 +msgid "" +"IDLE contains an extension facility. Peferences for extensions can be " +"changed with Configure Extensions. See the beginning of config-extensions." +"def in the idlelib directory for further information. The default " +"extensions are currently:" +msgstr "" + +#: ../Doc/library/idle.rst:634 +msgid "FormatParagraph" +msgstr "" + +#: ../Doc/library/idle.rst:636 +msgid "AutoExpand" +msgstr "" + +#: ../Doc/library/idle.rst:638 +msgid "ZoomHeight" +msgstr "" + +#: ../Doc/library/idle.rst:640 +msgid "ScriptBinding" +msgstr "" + +#: ../Doc/library/idle.rst:642 +msgid "CallTips" +msgstr "" + +#: ../Doc/library/idle.rst:644 +msgid "ParenMatch" +msgstr "" + +#: ../Doc/library/idle.rst:646 +msgid "AutoComplete" +msgstr "" + +#: ../Doc/library/idle.rst:648 +msgid "CodeContext" +msgstr "" + +#: ../Doc/library/idle.rst:650 +msgid "RstripExtension" +msgstr "" + +#: ../Doc/library/imaplib.rst:2 +msgid ":mod:`imaplib` --- IMAP4 protocol client" +msgstr "" + +#: ../Doc/library/imaplib.rst:14 +msgid "**Source code:** :source:`Lib/imaplib.py`" +msgstr "" + +#: ../Doc/library/imaplib.rst:23 +msgid "" +"This module defines three classes, :class:`IMAP4`, :class:`IMAP4_SSL` and :" +"class:`IMAP4_stream`, which encapsulate a connection to an IMAP4 server and " +"implement a large subset of the IMAP4rev1 client protocol as defined in :rfc:" +"`2060`. It is backward compatible with IMAP4 (:rfc:`1730`) servers, but note " +"that the ``STATUS`` command is not supported in IMAP4." +msgstr "" + +#: ../Doc/library/imaplib.rst:29 +msgid "" +"Three classes are provided by the :mod:`imaplib` module, :class:`IMAP4` is " +"the base class:" +msgstr "" + +#: ../Doc/library/imaplib.rst:35 +msgid "" +"This class implements the actual IMAP4 protocol. The connection is created " +"and protocol version (IMAP4 or IMAP4rev1) is determined when the instance is " +"initialized. If *host* is not specified, ``''`` (the local host) is used. If " +"*port* is omitted, the standard IMAP4 port (143) is used." +msgstr "" + +#: ../Doc/library/imaplib.rst:40 +msgid "" +"The :class:`IMAP4` class supports the :keyword:`with` statement. When used " +"like this, the IMAP4 ``LOGOUT`` command is issued automatically when the :" +"keyword:`with` statement exits. E.g.::" +msgstr "" + +#: ../Doc/library/imaplib.rst:53 +msgid "Three exceptions are defined as attributes of the :class:`IMAP4` class:" +msgstr "" + +#: ../Doc/library/imaplib.rst:58 +msgid "" +"Exception raised on any errors. The reason for the exception is passed to " +"the constructor as a string." +msgstr "" + +#: ../Doc/library/imaplib.rst:64 +msgid "" +"IMAP4 server errors cause this exception to be raised. This is a sub-class " +"of :exc:`IMAP4.error`. Note that closing the instance and instantiating a " +"new one will usually allow recovery from this exception." +msgstr "" + +#: ../Doc/library/imaplib.rst:71 +msgid "" +"This exception is raised when a writable mailbox has its status changed by " +"the server. This is a sub-class of :exc:`IMAP4.error`. Some other client " +"now has write permission, and the mailbox will need to be re-opened to re-" +"obtain write permission." +msgstr "" + +#: ../Doc/library/imaplib.rst:77 +msgid "There's also a subclass for secure connections:" +msgstr "" + +#: ../Doc/library/imaplib.rst:83 +msgid "" +"This is a subclass derived from :class:`IMAP4` that connects over an SSL " +"encrypted socket (to use this class you need a socket module that was " +"compiled with SSL support). If *host* is not specified, ``''`` (the local " +"host) is used. If *port* is omitted, the standard IMAP4-over-SSL port (993) " +"is used. *ssl_context* is a :class:`ssl.SSLContext` object which allows " +"bundling SSL configuration options, certificates and private keys into a " +"single (potentially long-lived) structure. Please read :ref:`ssl-security` " +"for best practices." +msgstr "" + +#: ../Doc/library/imaplib.rst:92 +msgid "" +"*keyfile* and *certfile* are a legacy alternative to *ssl_context* - they " +"can point to PEM-formatted private key and certificate chain files for the " +"SSL connection. Note that the *keyfile*/*certfile* parameters are mutually " +"exclusive with *ssl_context*, a :class:`ValueError` is raised if *keyfile*/" +"*certfile* is provided along with *ssl_context*." +msgstr "" + +#: ../Doc/library/imaplib.rst:98 +msgid "*ssl_context* parameter added." +msgstr "" + +#: ../Doc/library/imaplib.rst:108 +msgid "" +"*keyfile* and *certfile* are deprecated in favor of *ssl_context*. Please " +"use :meth:`ssl.SSLContext.load_cert_chain` instead, or let :func:`ssl." +"create_default_context` select the system's trusted CA certificates for you." +msgstr "" + +#: ../Doc/library/imaplib.rst:114 +msgid "The second subclass allows for connections created by a child process:" +msgstr "" + +#: ../Doc/library/imaplib.rst:119 +msgid "" +"This is a subclass derived from :class:`IMAP4` that connects to the ``stdin/" +"stdout`` file descriptors created by passing *command* to ``subprocess." +"Popen()``." +msgstr "" + +#: ../Doc/library/imaplib.rst:124 +msgid "The following utility functions are defined:" +msgstr "" + +#: ../Doc/library/imaplib.rst:129 +msgid "" +"Parse an IMAP4 ``INTERNALDATE`` string and return corresponding local time. " +"The return value is a :class:`time.struct_time` tuple or None if the string " +"has wrong format." +msgstr "" + +#: ../Doc/library/imaplib.rst:135 +msgid "" +"Converts an integer into a string representation using characters from the " +"set [``A`` .. ``P``]." +msgstr "" + +#: ../Doc/library/imaplib.rst:141 +msgid "Converts an IMAP4 ``FLAGS`` response to a tuple of individual flags." +msgstr "" + +#: ../Doc/library/imaplib.rst:146 +msgid "" +"Convert *date_time* to an IMAP4 ``INTERNALDATE`` representation. The return " +"value is a string in the form: ``\"DD-Mmm-YYYY HH:MM:SS +HHMM\"`` (including " +"double-quotes). The *date_time* argument can be a number (int or float) " +"representing seconds since epoch (as returned by :func:`time.time`), a 9-" +"tuple representing local time an instance of :class:`time.struct_time` (as " +"returned by :func:`time.localtime`), an aware instance of :class:`datetime." +"datetime`, or a double-quoted string. In the last case, it is assumed to " +"already be in the correct format." +msgstr "" + +#: ../Doc/library/imaplib.rst:156 +msgid "" +"Note that IMAP4 message numbers change as the mailbox changes; in " +"particular, after an ``EXPUNGE`` command performs deletions the remaining " +"messages are renumbered. So it is highly advisable to use UIDs instead, with " +"the UID command." +msgstr "" + +#: ../Doc/library/imaplib.rst:160 ../Doc/library/poplib.rst:253 +msgid "" +"At the end of the module, there is a test section that contains a more " +"extensive example of usage." +msgstr "" + +#: ../Doc/library/imaplib.rst:166 +msgid "" +"Documents describing the protocol, and sources and binaries for servers " +"implementing it, can all be found at the University of Washington's *IMAP " +"Information Center* (https://www.washington.edu/imap/)." +msgstr "" + +#: ../Doc/library/imaplib.rst:174 +msgid "IMAP4 Objects" +msgstr "" + +#: ../Doc/library/imaplib.rst:176 +msgid "" +"All IMAP4rev1 commands are represented by methods of the same name, either " +"upper-case or lower-case." +msgstr "" + +#: ../Doc/library/imaplib.rst:179 +msgid "" +"All arguments to commands are converted to strings, except for " +"``AUTHENTICATE``, and the last argument to ``APPEND`` which is passed as an " +"IMAP4 literal. If necessary (the string contains IMAP4 protocol-sensitive " +"characters and isn't enclosed with either parentheses or double quotes) each " +"string is quoted. However, the *password* argument to the ``LOGIN`` command " +"is always quoted. If you want to avoid having an argument string quoted (eg: " +"the *flags* argument to ``STORE``) then enclose the string in parentheses " +"(eg: ``r'(\\Deleted)'``)." +msgstr "" + +#: ../Doc/library/imaplib.rst:187 +msgid "" +"Each command returns a tuple: ``(type, [data, ...])`` where *type* is " +"usually ``'OK'`` or ``'NO'``, and *data* is either the text from the command " +"response, or mandated results from the command. Each *data* is either a " +"string, or a tuple. If a tuple, then the first part is the header of the " +"response, and the second part contains the data (ie: 'literal' value)." +msgstr "" + +#: ../Doc/library/imaplib.rst:193 +msgid "" +"The *message_set* options to commands below is a string specifying one or " +"more messages to be acted upon. It may be a simple message number " +"(``'1'``), a range of message numbers (``'2:4'``), or a group of non-" +"contiguous ranges separated by commas (``'1:3,6:9'``). A range can contain " +"an asterisk to indicate an infinite upper bound (``'3:*'``)." +msgstr "" + +#: ../Doc/library/imaplib.rst:199 +msgid "An :class:`IMAP4` instance has the following methods:" +msgstr "" + +#: ../Doc/library/imaplib.rst:204 +msgid "Append *message* to named mailbox." +msgstr "" + +#: ../Doc/library/imaplib.rst:209 +msgid "Authenticate command --- requires response processing." +msgstr "" + +#: ../Doc/library/imaplib.rst:211 +msgid "" +"*mechanism* specifies which authentication mechanism is to be used - it " +"should appear in the instance variable ``capabilities`` in the form " +"``AUTH=mechanism``." +msgstr "" + +#: ../Doc/library/imaplib.rst:214 +msgid "*authobject* must be a callable object::" +msgstr "" + +#: ../Doc/library/imaplib.rst:218 +msgid "" +"It will be called to process server continuation responses; the *response* " +"argument it is passed will be ``bytes``. It should return ``bytes`` *data* " +"that will be base64 encoded and sent to the server. It should return " +"``None`` if the client abort response ``*`` should be sent instead." +msgstr "" + +#: ../Doc/library/imaplib.rst:223 +msgid "" +"string usernames and passwords are now encoded to ``utf-8`` instead of being " +"limited to ASCII." +msgstr "" + +#: ../Doc/library/imaplib.rst:230 +msgid "Checkpoint mailbox on server." +msgstr "" + +#: ../Doc/library/imaplib.rst:235 +msgid "" +"Close currently selected mailbox. Deleted messages are removed from writable " +"mailbox. This is the recommended command before ``LOGOUT``." +msgstr "" + +#: ../Doc/library/imaplib.rst:241 +msgid "Copy *message_set* messages onto end of *new_mailbox*." +msgstr "" + +#: ../Doc/library/imaplib.rst:246 +msgid "Create new mailbox named *mailbox*." +msgstr "" + +#: ../Doc/library/imaplib.rst:251 +msgid "Delete old mailbox named *mailbox*." +msgstr "" + +#: ../Doc/library/imaplib.rst:256 +msgid "Delete the ACLs (remove any rights) set for who on mailbox." +msgstr "" + +#: ../Doc/library/imaplib.rst:261 +msgid "" +"Enable *capability* (see :rfc:`5161`). Most capabilities do not need to be " +"enabled. Currently only the ``UTF8=ACCEPT`` capability is supported (see :" +"RFC:`6855`)." +msgstr "" + +#: ../Doc/library/imaplib.rst:265 +msgid "The :meth:`enable` method itself, and :RFC:`6855` support." +msgstr "" + +#: ../Doc/library/imaplib.rst:271 +msgid "" +"Permanently remove deleted items from selected mailbox. Generates an " +"``EXPUNGE`` response for each deleted message. Returned data contains a list " +"of ``EXPUNGE`` message numbers in order received." +msgstr "" + +#: ../Doc/library/imaplib.rst:278 +msgid "" +"Fetch (parts of) messages. *message_parts* should be a string of message " +"part names enclosed within parentheses, eg: ``\"(UID BODY[TEXT])\"``. " +"Returned data are tuples of message part envelope and data." +msgstr "" + +#: ../Doc/library/imaplib.rst:285 +msgid "" +"Get the ``ACL``\\ s for *mailbox*. The method is non-standard, but is " +"supported by the ``Cyrus`` server." +msgstr "" + +#: ../Doc/library/imaplib.rst:291 +msgid "" +"Retrieve the specified ``ANNOTATION``\\ s for *mailbox*. The method is non-" +"standard, but is supported by the ``Cyrus`` server." +msgstr "" + +#: ../Doc/library/imaplib.rst:297 +msgid "" +"Get the ``quota`` *root*'s resource usage and limits. This method is part of " +"the IMAP4 QUOTA extension defined in rfc2087." +msgstr "" + +#: ../Doc/library/imaplib.rst:303 +msgid "" +"Get the list of ``quota`` ``roots`` for the named *mailbox*. This method is " +"part of the IMAP4 QUOTA extension defined in rfc2087." +msgstr "" + +#: ../Doc/library/imaplib.rst:309 +msgid "" +"List mailbox names in *directory* matching *pattern*. *directory* defaults " +"to the top-level mail folder, and *pattern* defaults to match anything. " +"Returned data contains a list of ``LIST`` responses." +msgstr "" + +#: ../Doc/library/imaplib.rst:316 +msgid "" +"Identify the client using a plaintext password. The *password* will be " +"quoted." +msgstr "" + +#: ../Doc/library/imaplib.rst:321 +msgid "" +"Force use of ``CRAM-MD5`` authentication when identifying the client to " +"protect the password. Will only work if the server ``CAPABILITY`` response " +"includes the phrase ``AUTH=CRAM-MD5``." +msgstr "" + +#: ../Doc/library/imaplib.rst:328 +msgid "Shutdown connection to server. Returns server ``BYE`` response." +msgstr "" + +#: ../Doc/library/imaplib.rst:333 +msgid "" +"List subscribed mailbox names in directory matching pattern. *directory* " +"defaults to the top level directory and *pattern* defaults to match any " +"mailbox. Returned data are tuples of message part envelope and data." +msgstr "" + +#: ../Doc/library/imaplib.rst:340 +msgid "Show my ACLs for a mailbox (i.e. the rights that I have on mailbox)." +msgstr "" + +#: ../Doc/library/imaplib.rst:345 +msgid "Returns IMAP namespaces as defined in RFC2342." +msgstr "" + +#: ../Doc/library/imaplib.rst:350 +msgid "Send ``NOOP`` to server." +msgstr "" + +#: ../Doc/library/imaplib.rst:355 +msgid "" +"Opens socket to *port* at *host*. This method is implicitly called by the :" +"class:`IMAP4` constructor. The connection objects established by this " +"method will be used in the :meth:`IMAP4.read`, :meth:`IMAP4.readline`, :meth:" +"`IMAP4.send`, and :meth:`IMAP4.shutdown` methods. You may override this " +"method." +msgstr "" + +#: ../Doc/library/imaplib.rst:364 +msgid "" +"Fetch truncated part of a message. Returned data is a tuple of message part " +"envelope and data." +msgstr "" + +#: ../Doc/library/imaplib.rst:370 +msgid "" +"Assume authentication as *user*. Allows an authorised administrator to proxy " +"into any user's mailbox." +msgstr "" + +#: ../Doc/library/imaplib.rst:376 +msgid "" +"Reads *size* bytes from the remote server. You may override this method." +msgstr "" + +#: ../Doc/library/imaplib.rst:381 +msgid "Reads one line from the remote server. You may override this method." +msgstr "" + +#: ../Doc/library/imaplib.rst:386 +msgid "" +"Prompt server for an update. Returned data is ``None`` if no new messages, " +"else value of ``RECENT`` response." +msgstr "" + +#: ../Doc/library/imaplib.rst:392 +msgid "Rename mailbox named *oldmailbox* to *newmailbox*." +msgstr "" + +#: ../Doc/library/imaplib.rst:397 +msgid "" +"Return data for response *code* if received, or ``None``. Returns the given " +"code, instead of the usual type." +msgstr "" + +#: ../Doc/library/imaplib.rst:403 +msgid "" +"Search mailbox for matching messages. *charset* may be ``None``, in which " +"case no ``CHARSET`` will be specified in the request to the server. The " +"IMAP protocol requires that at least one criterion be specified; an " +"exception will be raised when the server returns an error. *charset* must " +"be ``None`` if the ``UTF8=ACCEPT`` capability was enabled using the :meth:" +"`enable` command." +msgstr "" + +#: ../Doc/library/imaplib.rst:421 +msgid "" +"Select a mailbox. Returned data is the count of messages in *mailbox* " +"(``EXISTS`` response). The default *mailbox* is ``'INBOX'``. If the " +"*readonly* flag is set, modifications to the mailbox are not allowed." +msgstr "" + +#: ../Doc/library/imaplib.rst:428 +msgid "Sends ``data`` to the remote server. You may override this method." +msgstr "" + +#: ../Doc/library/imaplib.rst:433 +msgid "" +"Set an ``ACL`` for *mailbox*. The method is non-standard, but is supported " +"by the ``Cyrus`` server." +msgstr "" + +#: ../Doc/library/imaplib.rst:439 +msgid "" +"Set ``ANNOTATION``\\ s for *mailbox*. The method is non-standard, but is " +"supported by the ``Cyrus`` server." +msgstr "" + +#: ../Doc/library/imaplib.rst:445 +msgid "" +"Set the ``quota`` *root*'s resource *limits*. This method is part of the " +"IMAP4 QUOTA extension defined in rfc2087." +msgstr "" + +#: ../Doc/library/imaplib.rst:451 +msgid "" +"Close connection established in ``open``. This method is implicitly called " +"by :meth:`IMAP4.logout`. You may override this method." +msgstr "" + +#: ../Doc/library/imaplib.rst:457 +msgid "Returns socket instance used to connect to server." +msgstr "" + +#: ../Doc/library/imaplib.rst:462 +msgid "" +"The ``sort`` command is a variant of ``search`` with sorting semantics for " +"the results. Returned data contains a space separated list of matching " +"message numbers." +msgstr "" + +#: ../Doc/library/imaplib.rst:466 +msgid "" +"Sort has two arguments before the *search_criterion* argument(s); a " +"parenthesized list of *sort_criteria*, and the searching *charset*. Note " +"that unlike ``search``, the searching *charset* argument is mandatory. " +"There is also a ``uid sort`` command which corresponds to ``sort`` the way " +"that ``uid search`` corresponds to ``search``. The ``sort`` command first " +"searches the mailbox for messages that match the given searching criteria " +"using the charset argument for the interpretation of strings in the " +"searching criteria. It then returns the numbers of matching messages." +msgstr "" + +#: ../Doc/library/imaplib.rst:475 ../Doc/library/imaplib.rst:546 +msgid "This is an ``IMAP4rev1`` extension command." +msgstr "" + +#: ../Doc/library/imaplib.rst:480 +msgid "" +"Send a ``STARTTLS`` command. The *ssl_context* argument is optional and " +"should be a :class:`ssl.SSLContext` object. This will enable encryption on " +"the IMAP connection. Please read :ref:`ssl-security` for best practices." +msgstr "" + +#: ../Doc/library/imaplib.rst:495 +msgid "Request named status conditions for *mailbox*." +msgstr "" + +#: ../Doc/library/imaplib.rst:500 +msgid "" +"Alters flag dispositions for messages in mailbox. *command* is specified by " +"section 6.4.6 of :rfc:`2060` as being one of \"FLAGS\", \"+FLAGS\", or \"-" +"FLAGS\", optionally with a suffix of \".SILENT\"." +msgstr "" + +#: ../Doc/library/imaplib.rst:504 +msgid "For example, to set the delete flag on all messages::" +msgstr "" + +#: ../Doc/library/imaplib.rst:513 +msgid "" +"Creating flags containing ']' (for example: \"[test]\") violates :rfc:`3501` " +"(the IMAP protocol). However, imaplib has historically allowed creation of " +"such tags, and popular IMAP servers, such as Gmail, accept and produce such " +"flags. There are non-Python programs which also create such tags. Although " +"it is an RFC violation and IMAP clients and servers are supposed to be " +"strict, imaplib nonetheless continues to allow such tags to be created for " +"backward compatibility reasons, and as of python 3.6, handles them if they " +"are sent from the server, since this improves real-world compatibility." +msgstr "" + +#: ../Doc/library/imaplib.rst:525 +msgid "Subscribe to new mailbox." +msgstr "" + +#: ../Doc/library/imaplib.rst:530 +msgid "" +"The ``thread`` command is a variant of ``search`` with threading semantics " +"for the results. Returned data contains a space separated list of thread " +"members." +msgstr "" + +#: ../Doc/library/imaplib.rst:533 +msgid "" +"Thread members consist of zero or more messages numbers, delimited by " +"spaces, indicating successive parent and child." +msgstr "" + +#: ../Doc/library/imaplib.rst:536 +msgid "" +"Thread has two arguments before the *search_criterion* argument(s); a " +"*threading_algorithm*, and the searching *charset*. Note that unlike " +"``search``, the searching *charset* argument is mandatory. There is also a " +"``uid thread`` command which corresponds to ``thread`` the way that ``uid " +"search`` corresponds to ``search``. The ``thread`` command first searches " +"the mailbox for messages that match the given searching criteria using the " +"charset argument for the interpretation of strings in the searching " +"criteria. It then returns the matching messages threaded according to the " +"specified threading algorithm." +msgstr "" + +#: ../Doc/library/imaplib.rst:551 +msgid "" +"Execute command args with messages identified by UID, rather than message " +"number. Returns response appropriate to command. At least one argument " +"must be supplied; if none are provided, the server will return an error and " +"an exception will be raised." +msgstr "" + +#: ../Doc/library/imaplib.rst:559 +msgid "Unsubscribe from old mailbox." +msgstr "" + +#: ../Doc/library/imaplib.rst:564 +msgid "" +"Allow simple extension commands notified by server in ``CAPABILITY`` " +"response." +msgstr "" + +#: ../Doc/library/imaplib.rst:567 +msgid "The following attributes are defined on instances of :class:`IMAP4`:" +msgstr "" + +#: ../Doc/library/imaplib.rst:571 +msgid "" +"The most recent supported protocol in the ``CAPABILITY`` response from the " +"server." +msgstr "" + +#: ../Doc/library/imaplib.rst:577 +msgid "" +"Integer value to control debugging output. The initialize value is taken " +"from the module variable ``Debug``. Values greater than three trace each " +"command." +msgstr "" + +#: ../Doc/library/imaplib.rst:583 +msgid "" +"Boolean value that is normally ``False``, but is set to ``True`` if an :meth:" +"`enable` command is successfully issued for the ``UTF8=ACCEPT`` capability." +msgstr "" + +#: ../Doc/library/imaplib.rst:593 +msgid "IMAP4 Example" +msgstr "" + +#: ../Doc/library/imaplib.rst:595 ../Doc/library/poplib.rst:240 +msgid "" +"Here is a minimal example (without error checking) that opens a mailbox and " +"retrieves and prints all messages::" +msgstr "" + +#: ../Doc/library/imghdr.rst:2 +msgid ":mod:`imghdr` --- Determine the type of an image" +msgstr "" + +#: ../Doc/library/imghdr.rst:7 +msgid "**Source code:** :source:`Lib/imghdr.py`" +msgstr "" + +#: ../Doc/library/imghdr.rst:11 +msgid "" +"The :mod:`imghdr` module determines the type of image contained in a file or " +"byte stream." +msgstr "" + +#: ../Doc/library/imghdr.rst:14 +msgid "The :mod:`imghdr` module defines the following function:" +msgstr "" + +#: ../Doc/library/imghdr.rst:19 +msgid "" +"Tests the image data contained in the file named by *filename*, and returns " +"a string describing the image type. If optional *h* is provided, the " +"*filename* is ignored and *h* is assumed to contain the byte stream to test." +msgstr "" + +#: ../Doc/library/imghdr.rst:26 +msgid "" +"The following image types are recognized, as listed below with the return " +"value from :func:`what`:" +msgstr "" + +#: ../Doc/library/imghdr.rst:30 +msgid "Image format" +msgstr "" + +#: ../Doc/library/imghdr.rst:32 +msgid "``'rgb'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:32 +msgid "SGI ImgLib Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:34 +msgid "``'gif'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:34 +msgid "GIF 87a and 89a Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:36 +msgid "``'pbm'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:36 +msgid "Portable Bitmap Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:38 +msgid "``'pgm'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:38 +msgid "Portable Graymap Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:40 +msgid "``'ppm'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:40 +msgid "Portable Pixmap Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:42 +msgid "``'tiff'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:42 +msgid "TIFF Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:44 +msgid "``'rast'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:44 +msgid "Sun Raster Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:46 +msgid "``'xbm'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:46 +msgid "X Bitmap Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:48 +msgid "``'jpeg'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:48 +msgid "JPEG data in JFIF or Exif formats" +msgstr "" + +#: ../Doc/library/imghdr.rst:50 +msgid "``'bmp'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:50 +msgid "BMP files" +msgstr "" + +#: ../Doc/library/imghdr.rst:52 +msgid "``'png'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:52 +msgid "Portable Network Graphics" +msgstr "" + +#: ../Doc/library/imghdr.rst:54 +msgid "``'webp'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:54 +msgid "WebP files" +msgstr "" + +#: ../Doc/library/imghdr.rst:56 +msgid "``'exr'``" +msgstr "" + +#: ../Doc/library/imghdr.rst:56 +msgid "OpenEXR Files" +msgstr "" + +#: ../Doc/library/imghdr.rst:59 +msgid "The *exr* and *webp* formats were added." +msgstr "" + +#: ../Doc/library/imghdr.rst:63 +msgid "" +"You can extend the list of file types :mod:`imghdr` can recognize by " +"appending to this variable:" +msgstr "" + +#: ../Doc/library/imghdr.rst:69 +msgid "" +"A list of functions performing the individual tests. Each function takes " +"two arguments: the byte-stream and an open file-like object. When :func:" +"`what` is called with a byte-stream, the file-like object will be ``None``." +msgstr "" + +#: ../Doc/library/imghdr.rst:73 +msgid "" +"The test function should return a string describing the image type if the " +"test succeeded, or ``None`` if it failed." +msgstr "" + +#: ../Doc/library/imp.rst:2 +msgid ":mod:`imp` --- Access the :ref:`import ` internals" +msgstr "" + +#: ../Doc/library/imp.rst:8 +msgid "**Source code:** :source:`Lib/imp.py`" +msgstr "" + +#: ../Doc/library/imp.rst:10 +msgid "" +"The :mod:`imp` package is pending deprecation in favor of :mod:`importlib`." +msgstr "" + +#: ../Doc/library/imp.rst:17 +msgid "" +"This module provides an interface to the mechanisms used to implement the :" +"keyword:`import` statement. It defines the following constants and " +"functions:" +msgstr "" + +#: ../Doc/library/imp.rst:25 +msgid "" +"Return the magic string value used to recognize byte-compiled code files (:" +"file:`.pyc` files). (This value may be different for each Python version.)" +msgstr "" + +#: ../Doc/library/imp.rst:28 +msgid "Use :attr:`importlib.util.MAGIC_NUMBER` instead." +msgstr "" + +#: ../Doc/library/imp.rst:34 +msgid "" +"Return a list of 3-element tuples, each describing a particular type of " +"module. Each triple has the form ``(suffix, mode, type)``, where *suffix* is " +"a string to be appended to the module name to form the filename to search " +"for, *mode* is the mode string to pass to the built-in :func:`open` function " +"to open the file (this can be ``'r'`` for text files or ``'rb'`` for binary " +"files), and *type* is the file type, which has one of the values :const:" +"`PY_SOURCE`, :const:`PY_COMPILED`, or :const:`C_EXTENSION`, described below." +msgstr "" + +#: ../Doc/library/imp.rst:43 +msgid "Use the constants defined on :mod:`importlib.machinery` instead." +msgstr "" + +#: ../Doc/library/imp.rst:49 +msgid "" +"Try to find the module *name*. If *path* is omitted or ``None``, the list " +"of directory names given by ``sys.path`` is searched, but first a few " +"special places are searched: the function tries to find a built-in module " +"with the given name (:const:`C_BUILTIN`), then a frozen module (:const:" +"`PY_FROZEN`), and on some systems some other places are looked in as well " +"(on Windows, it looks in the registry which may point to a specific file)." +msgstr "" + +#: ../Doc/library/imp.rst:56 +msgid "" +"Otherwise, *path* must be a list of directory names; each directory is " +"searched for files with any of the suffixes returned by :func:`get_suffixes` " +"above. Invalid names in the list are silently ignored (but all list items " +"must be strings)." +msgstr "" + +#: ../Doc/library/imp.rst:61 +msgid "" +"If search is successful, the return value is a 3-element tuple ``(file, " +"pathname, description)``:" +msgstr "" + +#: ../Doc/library/imp.rst:64 +msgid "" +"*file* is an open :term:`file object` positioned at the beginning, " +"*pathname* is the pathname of the file found, and *description* is a 3-" +"element tuple as contained in the list returned by :func:`get_suffixes` " +"describing the kind of module found." +msgstr "" + +#: ../Doc/library/imp.rst:69 +msgid "" +"If the module does not live in a file, the returned *file* is ``None``, " +"*pathname* is the empty string, and the *description* tuple contains empty " +"strings for its suffix and mode; the module type is indicated as given in " +"parentheses above. If the search is unsuccessful, :exc:`ImportError` is " +"raised. Other exceptions indicate problems with the arguments or " +"environment." +msgstr "" + +#: ../Doc/library/imp.rst:76 +msgid "" +"If the module is a package, *file* is ``None``, *pathname* is the package " +"path and the last item in the *description* tuple is :const:`PKG_DIRECTORY`." +msgstr "" + +#: ../Doc/library/imp.rst:79 +msgid "" +"This function does not handle hierarchical module names (names containing " +"dots). In order to find *P.M*, that is, submodule *M* of package *P*, use :" +"func:`find_module` and :func:`load_module` to find and load package *P*, and " +"then use :func:`find_module` with the *path* argument set to ``P.__path__``. " +"When *P* itself has a dotted name, apply this recipe recursively." +msgstr "" + +#: ../Doc/library/imp.rst:85 +msgid "" +"Use :func:`importlib.util.find_spec` instead unless Python 3.3 compatibility " +"is required, in which case use :func:`importlib.find_loader`. For example " +"usage of the former case, see the :ref:`importlib-examples` section of the :" +"mod:`importlib` documentation." +msgstr "" + +#: ../Doc/library/imp.rst:95 +msgid "" +"Load a module that was previously found by :func:`find_module` (or by an " +"otherwise conducted search yielding compatible results). This function does " +"more than importing the module: if the module was already imported, it will " +"reload the module! The *name* argument indicates the full module name " +"(including the package name, if this is a submodule of a package). The " +"*file* argument is an open file, and *pathname* is the corresponding file " +"name; these can be ``None`` and ``''``, respectively, when the module is a " +"package or not being loaded from a file. The *description* argument is a " +"tuple, as would be returned by :func:`get_suffixes`, describing what kind of " +"module must be loaded." +msgstr "" + +#: ../Doc/library/imp.rst:106 +msgid "" +"If the load is successful, the return value is the module object; otherwise, " +"an exception (usually :exc:`ImportError`) is raised." +msgstr "" + +#: ../Doc/library/imp.rst:109 +msgid "" +"**Important:** the caller is responsible for closing the *file* argument, if " +"it was not ``None``, even when an exception is raised. This is best done " +"using a :keyword:`try` ... :keyword:`finally` statement." +msgstr "" + +#: ../Doc/library/imp.rst:113 +msgid "" +"If previously used in conjunction with :func:`imp.find_module` then consider " +"using :func:`importlib.import_module`, otherwise use the loader returned by " +"the replacement you chose for :func:`imp.find_module`. If you called :func:" +"`imp.load_module` and related functions directly with file path arguments " +"then use a combination of :func:`importlib.util.spec_from_file_location` " +"and :func:`importlib.util.module_from_spec`. See the :ref:`importlib-" +"examples` section of the :mod:`importlib` documentation for details of the " +"various approaches." +msgstr "" + +#: ../Doc/library/imp.rst:127 +msgid "" +"Return a new empty module object called *name*. This object is *not* " +"inserted in ``sys.modules``." +msgstr "" + +#: ../Doc/library/imp.rst:130 +msgid "Use :func:`importlib.util.module_from_spec` instead." +msgstr "" + +#: ../Doc/library/imp.rst:136 +msgid "" +"Reload a previously imported *module*. The argument must be a module " +"object, so it must have been successfully imported before. This is useful " +"if you have edited the module source file using an external editor and want " +"to try out the new version without leaving the Python interpreter. The " +"return value is the module object (the same as the *module* argument)." +msgstr "" + +#: ../Doc/library/imp.rst:142 +msgid "When ``reload(module)`` is executed:" +msgstr "" + +#: ../Doc/library/imp.rst:144 +msgid "" +"Python modules' code is recompiled and the module-level code reexecuted, " +"defining a new set of objects which are bound to names in the module's " +"dictionary. The ``init`` function of extension modules is not called a " +"second time." +msgstr "" + +#: ../Doc/library/imp.rst:149 ../Doc/library/importlib.rst:162 +msgid "" +"As with all other objects in Python the old objects are only reclaimed after " +"their reference counts drop to zero." +msgstr "" + +#: ../Doc/library/imp.rst:152 ../Doc/library/importlib.rst:165 +msgid "" +"The names in the module namespace are updated to point to any new or changed " +"objects." +msgstr "" + +#: ../Doc/library/imp.rst:155 ../Doc/library/importlib.rst:168 +msgid "" +"Other references to the old objects (such as names external to the module) " +"are not rebound to refer to the new objects and must be updated in each " +"namespace where they occur if that is desired." +msgstr "" + +#: ../Doc/library/imp.rst:159 ../Doc/library/importlib.rst:172 +msgid "There are a number of other caveats:" +msgstr "" + +#: ../Doc/library/imp.rst:161 ../Doc/library/importlib.rst:174 +msgid "" +"When a module is reloaded, its dictionary (containing the module's global " +"variables) is retained. Redefinitions of names will override the old " +"definitions, so this is generally not a problem. If the new version of a " +"module does not define a name that was defined by the old version, the old " +"definition remains. This feature can be used to the module's advantage if " +"it maintains a global table or cache of objects --- with a :keyword:`try` " +"statement it can test for the table's presence and skip its initialization " +"if desired::" +msgstr "" + +#: ../Doc/library/imp.rst:174 +msgid "" +"It is legal though generally not very useful to reload built-in or " +"dynamically loaded modules, except for :mod:`sys`, :mod:`__main__` and :mod:" +"`builtins`. In many cases, however, extension modules are not designed to be " +"initialized more than once, and may fail in arbitrary ways when reloaded." +msgstr "" + +#: ../Doc/library/imp.rst:179 +msgid "" +"If a module imports objects from another module using :keyword:`from` ... :" +"keyword:`import` ..., calling :func:`reload` for the other module does not " +"redefine the objects imported from it --- one way around this is to re-" +"execute the :keyword:`from` statement, another is to use :keyword:`import` " +"and qualified names (*module*.*name*) instead." +msgstr "" + +#: ../Doc/library/imp.rst:185 ../Doc/library/importlib.rst:200 +msgid "" +"If a module instantiates instances of a class, reloading the module that " +"defines the class does not affect the method definitions of the instances " +"--- they continue to use the old class definition. The same is true for " +"derived classes." +msgstr "" + +#: ../Doc/library/imp.rst:189 +msgid "" +"Relies on both ``__name__`` and ``__loader__`` being defined on the module " +"being reloaded instead of just ``__name__``." +msgstr "" + +#: ../Doc/library/imp.rst:193 +msgid "Use :func:`importlib.reload` instead." +msgstr "" + +#: ../Doc/library/imp.rst:197 +msgid "" +"The following functions are conveniences for handling :pep:`3147` byte-" +"compiled file paths." +msgstr "" + +#: ../Doc/library/imp.rst:204 +msgid "" +"Return the :pep:`3147` path to the byte-compiled file associated with the " +"source *path*. For example, if *path* is ``/foo/bar/baz.py`` the return " +"value would be ``/foo/bar/__pycache__/baz.cpython-32.pyc`` for Python 3.2. " +"The ``cpython-32`` string comes from the current magic tag (see :func:" +"`get_tag`; if :attr:`sys.implementation.cache_tag` is not defined then :exc:" +"`NotImplementedError` will be raised). By passing in ``True`` or ``False`` " +"for *debug_override* you can override the system's value for ``__debug__``, " +"leading to optimized bytecode." +msgstr "" + +#: ../Doc/library/imp.rst:213 +msgid "*path* need not exist." +msgstr "" + +#: ../Doc/library/imp.rst:215 +msgid "" +"If :attr:`sys.implementation.cache_tag` is ``None``, then :exc:" +"`NotImplementedError` is raised." +msgstr "" + +#: ../Doc/library/imp.rst:219 +msgid "Use :func:`importlib.util.cache_from_source` instead." +msgstr "" + +#: ../Doc/library/imp.rst:222 +msgid "The *debug_override* parameter no longer creates a ``.pyo`` file." +msgstr "" + +#: ../Doc/library/imp.rst:228 +msgid "" +"Given the *path* to a :pep:`3147` file name, return the associated source " +"code file path. For example, if *path* is ``/foo/bar/__pycache__/baz." +"cpython-32.pyc`` the returned path would be ``/foo/bar/baz.py``. *path* " +"need not exist, however if it does not conform to :pep:`3147` format, a " +"``ValueError`` is raised. If :attr:`sys.implementation.cache_tag` is not " +"defined, :exc:`NotImplementedError` is raised." +msgstr "" + +#: ../Doc/library/imp.rst:236 +msgid "" +"Raise :exc:`NotImplementedError` when :attr:`sys.implementation.cache_tag` " +"is not defined." +msgstr "" + +#: ../Doc/library/imp.rst:240 +msgid "Use :func:`importlib.util.source_from_cache` instead." +msgstr "" + +#: ../Doc/library/imp.rst:246 +msgid "" +"Return the :pep:`3147` magic tag string matching this version of Python's " +"magic number, as returned by :func:`get_magic`." +msgstr "" + +#: ../Doc/library/imp.rst:249 +msgid "" +"Use :attr:`sys.implementation.cache_tag` directly starting in Python 3.3." +msgstr "" + +#: ../Doc/library/imp.rst:254 +msgid "" +"The following functions help interact with the import system's internal " +"locking mechanism. Locking semantics of imports are an implementation " +"detail which may vary from release to release. However, Python ensures that " +"circular imports work without any deadlocks." +msgstr "" + +#: ../Doc/library/imp.rst:262 +msgid "" +"Return ``True`` if the global import lock is currently held, else ``False``. " +"On platforms without threads, always return ``False``." +msgstr "" + +#: ../Doc/library/imp.rst:265 +msgid "" +"On platforms with threads, a thread executing an import first holds a global " +"import lock, then sets up a per-module lock for the rest of the import. " +"This blocks other threads from importing the same module until the original " +"import completes, preventing other threads from seeing incomplete module " +"objects constructed by the original thread. An exception is made for " +"circular imports, which by construction have to expose an incomplete module " +"object at some point." +msgstr "" + +#: ../Doc/library/imp.rst:273 ../Doc/library/imp.rst:293 +#: ../Doc/library/imp.rst:306 +msgid "" +"The locking scheme has changed to per-module locks for the most part. A " +"global import lock is kept for some critical tasks, such as initializing the " +"per-module locks." +msgstr "" + +#: ../Doc/library/imp.rst:283 +msgid "" +"Acquire the interpreter's global import lock for the current thread. This " +"lock should be used by import hooks to ensure thread-safety when importing " +"modules." +msgstr "" + +#: ../Doc/library/imp.rst:287 +msgid "" +"Once a thread has acquired the import lock, the same thread may acquire it " +"again without blocking; the thread must release it once for each time it has " +"acquired it." +msgstr "" + +#: ../Doc/library/imp.rst:291 +msgid "On platforms without threads, this function does nothing." +msgstr "" + +#: ../Doc/library/imp.rst:303 +msgid "" +"Release the interpreter's global import lock. On platforms without threads, " +"this function does nothing." +msgstr "" + +#: ../Doc/library/imp.rst:314 +msgid "" +"The following constants with integer values, defined in this module, are " +"used to indicate the search result of :func:`find_module`." +msgstr "" + +#: ../Doc/library/imp.rst:320 +msgid "The module was found as a source file." +msgstr "" + +#: ../Doc/library/imp.rst:327 +msgid "The module was found as a compiled code object file." +msgstr "" + +#: ../Doc/library/imp.rst:334 +msgid "The module was found as dynamically loadable shared library." +msgstr "" + +#: ../Doc/library/imp.rst:341 +msgid "The module was found as a package directory." +msgstr "" + +#: ../Doc/library/imp.rst:348 +msgid "The module was found as a built-in module." +msgstr "" + +#: ../Doc/library/imp.rst:355 +msgid "The module was found as a frozen module." +msgstr "" + +#: ../Doc/library/imp.rst:362 +msgid "" +"The :class:`NullImporter` type is a :pep:`302` import hook that handles non-" +"directory path strings by failing to find any modules. Calling this type " +"with an existing directory or empty string raises :exc:`ImportError`. " +"Otherwise, a :class:`NullImporter` instance is returned." +msgstr "" + +#: ../Doc/library/imp.rst:367 +msgid "Instances have only one method:" +msgstr "" + +#: ../Doc/library/imp.rst:371 +msgid "" +"This method always returns ``None``, indicating that the requested module " +"could not be found." +msgstr "" + +#: ../Doc/library/imp.rst:374 +msgid "" +"``None`` is inserted into ``sys.path_importer_cache`` instead of an instance " +"of :class:`NullImporter`." +msgstr "" + +#: ../Doc/library/imp.rst:378 +msgid "Insert ``None`` into ``sys.path_importer_cache`` instead." +msgstr "" + +#: ../Doc/library/imp.rst:387 +msgid "" +"The following function emulates what was the standard import statement up to " +"Python 1.4 (no hierarchical module names). (This *implementation* wouldn't " +"work in that version, since :func:`find_module` has been extended and :func:" +"`load_module` has been added in 1.4.) ::" +msgstr "" + +#: ../Doc/library/importlib.rst:2 +msgid ":mod:`importlib` -- The implementation of :keyword:`import`" +msgstr "" + +#: ../Doc/library/importlib.rst:12 +msgid "**Source code:** :source:`Lib/importlib/__init__.py`" +msgstr "" + +#: ../Doc/library/importlib.rst:19 +msgid "" +"The purpose of the :mod:`importlib` package is two-fold. One is to provide " +"the implementation of the :keyword:`import` statement (and thus, by " +"extension, the :func:`__import__` function) in Python source code. This " +"provides an implementation of :keyword:`import` which is portable to any " +"Python interpreter. This also provides an implementation which is easier to " +"comprehend than one implemented in a programming language other than Python." +msgstr "" + +#: ../Doc/library/importlib.rst:26 +msgid "" +"Two, the components to implement :keyword:`import` are exposed in this " +"package, making it easier for users to create their own custom objects " +"(known generically as an :term:`importer`) to participate in the import " +"process." +msgstr "" + +#: ../Doc/library/importlib.rst:33 +msgid ":ref:`import`" +msgstr "" + +#: ../Doc/library/importlib.rst:33 +msgid "The language reference for the :keyword:`import` statement." +msgstr "" + +#: ../Doc/library/importlib.rst:38 +msgid "" +"`Packages specification `__" +msgstr "" + +#: ../Doc/library/importlib.rst:36 +msgid "" +"Original specification of packages. Some semantics have changed since the " +"writing of this document (e.g. redirecting based on ``None`` in :data:`sys." +"modules`)." +msgstr "" + +#: ../Doc/library/importlib.rst:41 +msgid "The :func:`.__import__` function" +msgstr "" + +#: ../Doc/library/importlib.rst:41 +msgid "The :keyword:`import` statement is syntactic sugar for this function." +msgstr "" + +#: ../Doc/library/importlib.rst:44 +msgid ":pep:`235`" +msgstr "" + +#: ../Doc/library/importlib.rst:44 +msgid "Import on Case-Insensitive Platforms" +msgstr "" + +#: ../Doc/library/importlib.rst:47 +msgid ":pep:`263`" +msgstr "" + +#: ../Doc/library/importlib.rst:47 +msgid "Defining Python Source Code Encodings" +msgstr "" + +#: ../Doc/library/importlib.rst:50 +msgid ":pep:`302`" +msgstr "" + +#: ../Doc/library/importlib.rst:50 +msgid "New Import Hooks" +msgstr "" + +#: ../Doc/library/importlib.rst:53 +msgid ":pep:`328`" +msgstr "" + +#: ../Doc/library/importlib.rst:53 +msgid "Imports: Multi-Line and Absolute/Relative" +msgstr "" + +#: ../Doc/library/importlib.rst:56 +msgid ":pep:`366`" +msgstr "" + +#: ../Doc/library/importlib.rst:56 +msgid "Main module explicit relative imports" +msgstr "" + +#: ../Doc/library/importlib.rst:59 +msgid ":pep:`420`" +msgstr "" + +#: ../Doc/library/importlib.rst:59 +msgid "Implicit namespace packages" +msgstr "" + +#: ../Doc/library/importlib.rst:62 +msgid ":pep:`451`" +msgstr "" + +#: ../Doc/library/importlib.rst:62 +msgid "A ModuleSpec Type for the Import System" +msgstr "" + +#: ../Doc/library/importlib.rst:65 +msgid ":pep:`488`" +msgstr "" + +#: ../Doc/library/importlib.rst:65 +msgid "Elimination of PYO files" +msgstr "" + +#: ../Doc/library/importlib.rst:68 +msgid ":pep:`489`" +msgstr "" + +#: ../Doc/library/importlib.rst:68 +msgid "Multi-phase extension module initialization" +msgstr "" + +#: ../Doc/library/importlib.rst:71 +msgid ":pep:`3120`" +msgstr "" + +#: ../Doc/library/importlib.rst:71 +msgid "Using UTF-8 as the Default Source Encoding" +msgstr "" + +#: ../Doc/library/importlib.rst:73 +msgid ":pep:`3147`" +msgstr "" + +#: ../Doc/library/importlib.rst:74 +msgid "PYC Repository Directories" +msgstr "" + +#: ../Doc/library/importlib.rst:82 +msgid "An implementation of the built-in :func:`__import__` function." +msgstr "" + +#: ../Doc/library/importlib.rst:85 +msgid "" +"Programmatic importing of modules should use :func:`import_module` instead " +"of this function." +msgstr "" + +#: ../Doc/library/importlib.rst:90 +msgid "" +"Import a module. The *name* argument specifies what module to import in " +"absolute or relative terms (e.g. either ``pkg.mod`` or ``..mod``). If the " +"name is specified in relative terms, then the *package* argument must be set " +"to the name of the package which is to act as the anchor for resolving the " +"package name (e.g. ``import_module('..mod', 'pkg.subpkg')`` will import " +"``pkg.mod``)." +msgstr "" + +#: ../Doc/library/importlib.rst:98 +msgid "" +"The :func:`import_module` function acts as a simplifying wrapper around :" +"func:`importlib.__import__`. This means all semantics of the function are " +"derived from :func:`importlib.__import__`. The most important difference " +"between these two functions is that :func:`import_module` returns the " +"specified package or module (e.g. ``pkg.mod``), while :func:`__import__` " +"returns the top-level package or module (e.g. ``pkg``)." +msgstr "" + +#: ../Doc/library/importlib.rst:105 +msgid "" +"If you are dynamically importing a module that was created since the " +"interpreter began execution (e.g., created a Python source file), you may " +"need to call :func:`invalidate_caches` in order for the new module to be " +"noticed by the import system." +msgstr "" + +#: ../Doc/library/importlib.rst:110 +msgid "Parent packages are automatically imported." +msgstr "" + +#: ../Doc/library/importlib.rst:115 +msgid "" +"Find the loader for a module, optionally within the specified *path*. If the " +"module is in :attr:`sys.modules`, then ``sys.modules[name].__loader__`` is " +"returned (unless the loader would be ``None`` or is not set, in which case :" +"exc:`ValueError` is raised). Otherwise a search using :attr:`sys.meta_path` " +"is done. ``None`` is returned if no loader is found." +msgstr "" + +#: ../Doc/library/importlib.rst:121 +msgid "" +"A dotted name does not have its parents implicitly imported as that requires " +"loading them and that may not be desired. To properly import a submodule you " +"will need to import all parent packages of the submodule and use the correct " +"argument to *path*." +msgstr "" + +#: ../Doc/library/importlib.rst:128 +msgid "" +"If ``__loader__`` is not set, raise :exc:`ValueError`, just like when the " +"attribute is set to ``None``." +msgstr "" + +#: ../Doc/library/importlib.rst:132 +msgid "Use :func:`importlib.util.find_spec` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:137 +msgid "" +"Invalidate the internal caches of finders stored at :data:`sys.meta_path`. " +"If a finder implements ``invalidate_caches()`` then it will be called to " +"perform the invalidation. This function should be called if any modules are " +"created/installed while your program is running to guarantee all finders " +"will notice the new module's existence." +msgstr "" + +#: ../Doc/library/importlib.rst:147 +msgid "" +"Reload a previously imported *module*. The argument must be a module " +"object, so it must have been successfully imported before. This is useful " +"if you have edited the module source file using an external editor and want " +"to try out the new version without leaving the Python interpreter. The " +"return value is the module object (which can be different if re-importing " +"causes a different object to be placed in :data:`sys.modules`)." +msgstr "" + +#: ../Doc/library/importlib.rst:154 +msgid "When :func:`reload` is executed:" +msgstr "" + +#: ../Doc/library/importlib.rst:156 +msgid "" +"Python module's code is recompiled and the module-level code re-executed, " +"defining a new set of objects which are bound to names in the module's " +"dictionary by reusing the :term:`loader` which originally loaded the " +"module. The ``init`` function of extension modules is not called a second " +"time." +msgstr "" + +#: ../Doc/library/importlib.rst:188 +msgid "" +"It is generally not very useful to reload built-in or dynamically loaded " +"modules. Reloading :mod:`sys`, :mod:`__main__`, :mod:`builtins` and other " +"key modules is not recommended. In many cases extension modules are not " +"designed to be initialized more than once, and may fail in arbitrary ways " +"when reloaded." +msgstr "" + +#: ../Doc/library/importlib.rst:194 +msgid "" +"If a module imports objects from another module using :keyword:`from` ... :" +"keyword:`import` ..., calling :func:`reload` for the other module does not " +"redefine the objects imported from it --- one way around this is to re-" +"execute the :keyword:`from` statement, another is to use :keyword:`import` " +"and qualified names (*module.name*) instead." +msgstr "" + +#: ../Doc/library/importlib.rst:209 +msgid ":mod:`importlib.abc` -- Abstract base classes related to import" +msgstr "" + +#: ../Doc/library/importlib.rst:214 +msgid "**Source code:** :source:`Lib/importlib/abc.py`" +msgstr "" + +#: ../Doc/library/importlib.rst:219 +msgid "" +"The :mod:`importlib.abc` module contains all of the core abstract base " +"classes used by :keyword:`import`. Some subclasses of the core abstract base " +"classes are also provided to help in implementing the core ABCs." +msgstr "" + +#: ../Doc/library/importlib.rst:223 +msgid "ABC hierarchy::" +msgstr "" + +#: ../Doc/library/importlib.rst:239 +msgid "An abstract base class representing a :term:`finder`." +msgstr "" + +#: ../Doc/library/importlib.rst:241 +msgid "Use :class:`MetaPathFinder` or :class:`PathEntryFinder` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:246 +msgid "" +"An abstact method for finding a :term:`loader` for the specified module. " +"Originally specified in :pep:`302`, this method was meant for use in :data:" +"`sys.meta_path` and in the path-based import subsystem." +msgstr "" + +#: ../Doc/library/importlib.rst:250 +msgid "" +"Returns ``None`` when called instead of raising :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/importlib.rst:257 +msgid "" +"An abstract base class representing a :term:`meta path finder`. For " +"compatibility, this is a subclass of :class:`Finder`." +msgstr "" + +#: ../Doc/library/importlib.rst:264 +msgid "" +"An abstract method for finding a :term:`spec ` for the " +"specified module. If this is a top-level import, *path* will be ``None``. " +"Otherwise, this is a search for a subpackage or module and *path* will be " +"the value of :attr:`__path__` from the parent package. If a spec cannot be " +"found, ``None`` is returned. When passed in, ``target`` is a module object " +"that the finder may use to make a more educated guess about what spec to " +"return." +msgstr "" + +#: ../Doc/library/importlib.rst:276 +msgid "" +"A legacy method for finding a :term:`loader` for the specified module. If " +"this is a top-level import, *path* will be ``None``. Otherwise, this is a " +"search for a subpackage or module and *path* will be the value of :attr:" +"`__path__` from the parent package. If a loader cannot be found, ``None`` is " +"returned." +msgstr "" + +#: ../Doc/library/importlib.rst:282 +msgid "" +"If :meth:`find_spec` is defined, backwards-compatible functionality is " +"provided." +msgstr "" + +#: ../Doc/library/importlib.rst:285 +msgid "" +"Returns ``None`` when called instead of raising :exc:`NotImplementedError`. " +"Can use :meth:`find_spec` to provide functionality." +msgstr "" + +#: ../Doc/library/importlib.rst:290 ../Doc/library/importlib.rst:343 +#: ../Doc/library/importlib.rst:351 ../Doc/library/importlib.rst:843 +msgid "Use :meth:`find_spec` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:295 +msgid "" +"An optional method which, when called, should invalidate any internal cache " +"used by the finder. Used by :func:`importlib.invalidate_caches` when " +"invalidating the caches of all finders on :data:`sys.meta_path`." +msgstr "" + +#: ../Doc/library/importlib.rst:299 +msgid "Returns ``None`` when called instead of ``NotImplemented``." +msgstr "" + +#: ../Doc/library/importlib.rst:305 +msgid "" +"An abstract base class representing a :term:`path entry finder`. Though it " +"bears some similarities to :class:`MetaPathFinder`, ``PathEntryFinder`` is " +"meant for use only within the path-based import subsystem provided by :class:" +"`PathFinder`. This ABC is a subclass of :class:`Finder` for compatibility " +"reasons only." +msgstr "" + +#: ../Doc/library/importlib.rst:315 +msgid "" +"An abstract method for finding a :term:`spec ` for the " +"specified module. The finder will search for the module only within the :" +"term:`path entry` to which it is assigned. If a spec cannot be found, " +"``None`` is returned. When passed in, ``target`` is a module object that " +"the finder may use to make a more educated guess about what spec to return." +msgstr "" + +#: ../Doc/library/importlib.rst:326 +msgid "" +"A legacy method for finding a :term:`loader` for the specified module. " +"Returns a 2-tuple of ``(loader, portion)`` where ``portion`` is a sequence " +"of file system locations contributing to part of a namespace package. The " +"loader may be ``None`` while specifying ``portion`` to signify the " +"contribution of the file system locations to a namespace package. An empty " +"list can be used for ``portion`` to signify the loader is not part of a " +"namespace package. If ``loader`` is ``None`` and ``portion`` is the empty " +"list then no loader or location for a namespace package were found (i.e. " +"failure to find anything for the module)." +msgstr "" + +#: ../Doc/library/importlib.rst:336 +msgid "" +"If :meth:`find_spec` is defined then backwards-compatible functionality is " +"provided." +msgstr "" + +#: ../Doc/library/importlib.rst:339 +msgid "" +"Returns ``(None, [])`` instead of raising :exc:`NotImplementedError`. Uses :" +"meth:`find_spec` when available to provide functionality." +msgstr "" + +#: ../Doc/library/importlib.rst:348 +msgid "" +"A concrete implementation of :meth:`Finder.find_module` which is equivalent " +"to ``self.find_loader(fullname)[0]``." +msgstr "" + +#: ../Doc/library/importlib.rst:356 +msgid "" +"An optional method which, when called, should invalidate any internal cache " +"used by the finder. Used by :meth:`PathFinder.invalidate_caches` when " +"invalidating the caches of all cached finders." +msgstr "" + +#: ../Doc/library/importlib.rst:363 +msgid "" +"An abstract base class for a :term:`loader`. See :pep:`302` for the exact " +"definition for a loader." +msgstr "" + +#: ../Doc/library/importlib.rst:368 +msgid "" +"A method that returns the module object to use when importing a module. " +"This method may return ``None``, indicating that default module creation " +"semantics should take place." +msgstr "" + +#: ../Doc/library/importlib.rst:374 +msgid "" +"Starting in Python 3.6, this method will not be optional when :meth:" +"`exec_module` is defined." +msgstr "" + +#: ../Doc/library/importlib.rst:380 +msgid "" +"An abstract method that executes the module in its own namespace when a " +"module is imported or reloaded. The module should already be initialized " +"when ``exec_module()`` is called. When this method exists, :meth:`~importlib." +"abc.Loader.create_module` must be defined." +msgstr "" + +#: ../Doc/library/importlib.rst:387 +msgid ":meth:`~importlib.abc.Loader.create_module` must also be defined." +msgstr "" + +#: ../Doc/library/importlib.rst:392 +msgid "" +"A legacy method for loading a module. If the module cannot be loaded, :exc:" +"`ImportError` is raised, otherwise the loaded module is returned." +msgstr "" + +#: ../Doc/library/importlib.rst:396 +msgid "" +"If the requested module already exists in :data:`sys.modules`, that module " +"should be used and reloaded. Otherwise the loader should create a new module " +"and insert it into :data:`sys.modules` before any loading begins, to prevent " +"recursion from the import. If the loader inserted a module and the load " +"fails, it must be removed by the loader from :data:`sys.modules`; modules " +"already in :data:`sys.modules` before the loader began execution should be " +"left alone (see :func:`importlib.util.module_for_loader`)." +msgstr "" + +#: ../Doc/library/importlib.rst:405 +msgid "" +"The loader should set several attributes on the module. (Note that some of " +"these attributes can change when a module is reloaded):" +msgstr "" + +#: ../Doc/library/importlib.rst:410 +msgid ":attr:`__name__`" +msgstr "" + +#: ../Doc/library/importlib.rst:410 ../Doc/library/types.rst:149 +msgid "The name of the module." +msgstr "" + +#: ../Doc/library/importlib.rst:414 +msgid ":attr:`__file__`" +msgstr "" + +#: ../Doc/library/importlib.rst:413 +msgid "" +"The path to where the module data is stored (not set for built-in modules)." +msgstr "" + +#: ../Doc/library/importlib.rst:418 +msgid ":attr:`__cached__`" +msgstr "" + +#: ../Doc/library/importlib.rst:417 +msgid "" +"The path to where a compiled version of the module is/should be stored (not " +"set when the attribute would be inappropriate)." +msgstr "" + +#: ../Doc/library/importlib.rst:422 +msgid ":attr:`__path__`" +msgstr "" + +#: ../Doc/library/importlib.rst:421 +msgid "" +"A list of strings specifying the search path within a package. This " +"attribute is not set on modules." +msgstr "" + +#: ../Doc/library/importlib.rst:428 +msgid ":attr:`__package__`" +msgstr "" + +#: ../Doc/library/importlib.rst:425 +msgid "" +"The parent package for the module/package. If the module is top-level then " +"it has a value of the empty string. The :func:`importlib.util." +"module_for_loader` decorator can handle the details for :attr:`__package__`." +msgstr "" + +#: ../Doc/library/importlib.rst:433 +msgid ":attr:`__loader__`" +msgstr "" + +#: ../Doc/library/importlib.rst:431 +msgid "" +"The loader used to load the module. The :func:`importlib.util." +"module_for_loader` decorator can handle the details for :attr:`__package__`." +msgstr "" + +#: ../Doc/library/importlib.rst:435 +msgid "" +"When :meth:`exec_module` is available then backwards-compatible " +"functionality is provided." +msgstr "" + +#: ../Doc/library/importlib.rst:438 +msgid "" +"Raise :exc:`ImportError` when called instead of :exc:`NotImplementedError`. " +"Functionality provided when :meth:`exec_module` is available." +msgstr "" + +#: ../Doc/library/importlib.rst:443 +msgid "" +"The recommended API for loading a module is :meth:`exec_module` (and :meth:" +"`create_module`). Loaders should implement it instead of load_module(). " +"The import machinery takes care of all the other responsibilities of " +"load_module() when exec_module() is implemented." +msgstr "" + +#: ../Doc/library/importlib.rst:452 +msgid "" +"A legacy method which when implemented calculates and returns the given " +"module's repr, as a string. The module type's default repr() will use the " +"result of this method as appropriate." +msgstr "" + +#: ../Doc/library/importlib.rst:458 +msgid "Made optional instead of an abstractmethod." +msgstr "" + +#: ../Doc/library/importlib.rst:461 +msgid "The import machinery now takes care of this automatically." +msgstr "" + +#: ../Doc/library/importlib.rst:467 +msgid "" +"An abstract base class for a :term:`loader` which implements the optional :" +"pep:`302` protocol for loading arbitrary resources from the storage back-end." +msgstr "" + +#: ../Doc/library/importlib.rst:473 +msgid "" +"An abstract method to return the bytes for the data located at *path*. " +"Loaders that have a file-like storage back-end that allows storing arbitrary " +"data can implement this abstract method to give direct access to the data " +"stored. :exc:`OSError` is to be raised if the *path* cannot be found. The " +"*path* is expected to be constructed using a module's :attr:`__file__` " +"attribute or an item from a package's :attr:`__path__`." +msgstr "" + +#: ../Doc/library/importlib.rst:481 +msgid "Raises :exc:`OSError` instead of :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/importlib.rst:487 +msgid "" +"An abstract base class for a :term:`loader` which implements the optional :" +"pep:`302` protocol for loaders that inspect modules." +msgstr "" + +#: ../Doc/library/importlib.rst:492 +msgid "" +"Return the code object for a module, or ``None`` if the module does not have " +"a code object (as would be the case, for example, for a built-in module). " +"Raise an :exc:`ImportError` if loader cannot find the requested module." +msgstr "" + +#: ../Doc/library/importlib.rst:498 +msgid "" +"While the method has a default implementation, it is suggested that it be " +"overridden if possible for performance." +msgstr "" + +#: ../Doc/library/importlib.rst:504 +msgid "No longer abstract and a concrete implementation is provided." +msgstr "" + +#: ../Doc/library/importlib.rst:509 +msgid "" +"An abstract method to return the source of a module. It is returned as a " +"text string using :term:`universal newlines`, translating all recognized " +"line separators into ``'\\n'`` characters. Returns ``None`` if no source is " +"available (e.g. a built-in module). Raises :exc:`ImportError` if the loader " +"cannot find the module specified." +msgstr "" + +#: ../Doc/library/importlib.rst:515 ../Doc/library/importlib.rst:524 +#: ../Doc/library/importlib.rst:574 +msgid "Raises :exc:`ImportError` instead of :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/importlib.rst:520 +msgid "" +"An abstract method to return a true value if the module is a package, a " +"false value otherwise. :exc:`ImportError` is raised if the :term:`loader` " +"cannot find the module." +msgstr "" + +#: ../Doc/library/importlib.rst:529 +msgid "Create a code object from Python source." +msgstr "" + +#: ../Doc/library/importlib.rst:531 +msgid "" +"The *data* argument can be whatever the :func:`compile` function supports (i." +"e. string or bytes). The *path* argument should be the \"path\" to where the " +"source code originated from, which can be an abstract concept (e.g. location " +"in a zip file)." +msgstr "" + +#: ../Doc/library/importlib.rst:536 +msgid "" +"With the subsequent code object one can execute it in a module by running " +"``exec(code, module.__dict__)``." +msgstr "" + +#: ../Doc/library/importlib.rst:541 +msgid "Made the method static." +msgstr "" + +#: ../Doc/library/importlib.rst:546 +msgid "Implementation of :meth:`Loader.exec_module`." +msgstr "" + +#: ../Doc/library/importlib.rst:552 +msgid "Implementation of :meth:`Loader.load_module`." +msgstr "" + +#: ../Doc/library/importlib.rst:554 +msgid "use :meth:`exec_module` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:560 +msgid "" +"An abstract base class which inherits from :class:`InspectLoader` that, when " +"implemented, helps a module to be executed as a script. The ABC represents " +"an optional :pep:`302` protocol." +msgstr "" + +#: ../Doc/library/importlib.rst:566 +msgid "" +"An abstract method that is to return the value of :attr:`__file__` for the " +"specified module. If no path is available, :exc:`ImportError` is raised." +msgstr "" + +#: ../Doc/library/importlib.rst:570 +msgid "" +"If source code is available, then the method should return the path to the " +"source file, regardless of whether a bytecode was used to load the module." +msgstr "" + +#: ../Doc/library/importlib.rst:580 +msgid "" +"An abstract base class which inherits from :class:`ResourceLoader` and :" +"class:`ExecutionLoader`, providing concrete implementations of :meth:" +"`ResourceLoader.get_data` and :meth:`ExecutionLoader.get_filename`." +msgstr "" + +#: ../Doc/library/importlib.rst:584 +msgid "" +"The *fullname* argument is a fully resolved name of the module the loader is " +"to handle. The *path* argument is the path to the file for the module." +msgstr "" + +#: ../Doc/library/importlib.rst:591 +msgid "The name of the module the loader can handle." +msgstr "" + +#: ../Doc/library/importlib.rst:595 +msgid "Path to the file of the module." +msgstr "" + +#: ../Doc/library/importlib.rst:599 +msgid "Calls super's ``load_module()``." +msgstr "" + +#: ../Doc/library/importlib.rst:601 +msgid "Use :meth:`Loader.exec_module` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:606 ../Doc/library/importlib.rst:1037 +msgid "Returns :attr:`path`." +msgstr "" + +#: ../Doc/library/importlib.rst:610 +msgid "Reads *path* as a binary file and returns the bytes from it." +msgstr "" + +#: ../Doc/library/importlib.rst:615 +msgid "" +"An abstract base class for implementing source (and optionally bytecode) " +"file loading. The class inherits from both :class:`ResourceLoader` and :" +"class:`ExecutionLoader`, requiring the implementation of:" +msgstr "" + +#: ../Doc/library/importlib.rst:619 +msgid ":meth:`ResourceLoader.get_data`" +msgstr "" + +#: ../Doc/library/importlib.rst:622 +msgid ":meth:`ExecutionLoader.get_filename`" +msgstr "" + +#: ../Doc/library/importlib.rst:621 +msgid "" +"Should only return the path to the source file; sourceless loading is not " +"supported." +msgstr "" + +#: ../Doc/library/importlib.rst:624 +msgid "" +"The abstract methods defined by this class are to add optional bytecode file " +"support. Not implementing these optional methods (or causing them to raise :" +"exc:`NotImplementedError`) causes the loader to only work with source code. " +"Implementing the methods allows the loader to work with source *and* " +"bytecode files; it does not allow for *sourceless* loading where only " +"bytecode is provided. Bytecode files are an optimization to speed up " +"loading by removing the parsing step of Python's compiler, and so no " +"bytecode-specific API is exposed." +msgstr "" + +#: ../Doc/library/importlib.rst:635 +msgid "" +"Optional abstract method which returns a :class:`dict` containing metadata " +"about the specified path. Supported dictionary keys are:" +msgstr "" + +#: ../Doc/library/importlib.rst:638 +msgid "" +"``'mtime'`` (mandatory): an integer or floating-point number representing " +"the modification time of the source code;" +msgstr "" + +#: ../Doc/library/importlib.rst:640 +msgid "``'size'`` (optional): the size in bytes of the source code." +msgstr "" + +#: ../Doc/library/importlib.rst:642 +msgid "" +"Any other keys in the dictionary are ignored, to allow for future " +"extensions. If the path cannot be handled, :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/importlib.rst:647 ../Doc/library/importlib.rst:660 +msgid "Raise :exc:`OSError` instead of :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/importlib.rst:652 +msgid "" +"Optional abstract method which returns the modification time for the " +"specified path." +msgstr "" + +#: ../Doc/library/importlib.rst:655 +msgid "" +"This method is deprecated in favour of :meth:`path_stats`. You don't have " +"to implement it, but it is still available for compatibility purposes. " +"Raise :exc:`OSError` if the path cannot be handled." +msgstr "" + +#: ../Doc/library/importlib.rst:665 +msgid "" +"Optional abstract method which writes the specified bytes to a file path. " +"Any intermediate directories which do not exist are to be created " +"automatically." +msgstr "" + +#: ../Doc/library/importlib.rst:669 +msgid "" +"When writing to the path fails because the path is read-only (:attr:`errno." +"EACCES`/:exc:`PermissionError`), do not propagate the exception." +msgstr "" + +#: ../Doc/library/importlib.rst:673 +msgid "No longer raises :exc:`NotImplementedError` when called." +msgstr "" + +#: ../Doc/library/importlib.rst:678 +msgid "Concrete implementation of :meth:`InspectLoader.get_code`." +msgstr "" + +#: ../Doc/library/importlib.rst:682 +msgid "Concrete implementation of :meth:`Loader.exec_module`." +msgstr "" + +#: ../Doc/library/importlib.rst:688 +msgid "Concrete implementation of :meth:`Loader.load_module`." +msgstr "" + +#: ../Doc/library/importlib.rst:690 +msgid "Use :meth:`exec_module` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:695 +msgid "Concrete implementation of :meth:`InspectLoader.get_source`." +msgstr "" + +#: ../Doc/library/importlib.rst:699 +msgid "" +"Concrete implementation of :meth:`InspectLoader.is_package`. A module is " +"determined to be a package if its file path (as provided by :meth:" +"`ExecutionLoader.get_filename`) is a file named ``__init__`` when the file " +"extension is removed **and** the module name itself does not end in " +"``__init__``." +msgstr "" + +#: ../Doc/library/importlib.rst:707 +msgid ":mod:`importlib.machinery` -- Importers and path hooks" +msgstr "" + +#: ../Doc/library/importlib.rst:712 +msgid "**Source code:** :source:`Lib/importlib/machinery.py`" +msgstr "" + +#: ../Doc/library/importlib.rst:716 +msgid "" +"This module contains the various objects that help :keyword:`import` find " +"and load modules." +msgstr "" + +#: ../Doc/library/importlib.rst:721 +msgid "" +"A list of strings representing the recognized file suffixes for source " +"modules." +msgstr "" + +#: ../Doc/library/importlib.rst:728 +msgid "" +"A list of strings representing the file suffixes for non-optimized bytecode " +"modules." +msgstr "" + +#: ../Doc/library/importlib.rst:733 ../Doc/library/importlib.rst:743 +msgid "Use :attr:`BYTECODE_SUFFIXES` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:738 +msgid "" +"A list of strings representing the file suffixes for optimized bytecode " +"modules." +msgstr "" + +#: ../Doc/library/importlib.rst:748 +msgid "" +"A list of strings representing the recognized file suffixes for bytecode " +"modules (including the leading dot)." +msgstr "" + +#: ../Doc/library/importlib.rst:753 +msgid "The value is no longer dependent on ``__debug__``." +msgstr "" + +#: ../Doc/library/importlib.rst:758 +msgid "" +"A list of strings representing the recognized file suffixes for extension " +"modules." +msgstr "" + +#: ../Doc/library/importlib.rst:765 +msgid "" +"Returns a combined list of strings representing all file suffixes for " +"modules recognized by the standard import machinery. This is a helper for " +"code which simply needs to know if a filesystem path potentially refers to a " +"module without needing any details on the kind of module (for example, :func:" +"`inspect.getmodulename`)." +msgstr "" + +#: ../Doc/library/importlib.rst:776 +msgid "" +"An :term:`importer` for built-in modules. All known built-in modules are " +"listed in :data:`sys.builtin_module_names`. This class implements the :class:" +"`importlib.abc.MetaPathFinder` and :class:`importlib.abc.InspectLoader` ABCs." +msgstr "" + +#: ../Doc/library/importlib.rst:781 ../Doc/library/importlib.rst:795 +#: ../Doc/library/importlib.rst:804 ../Doc/library/importlib.rst:815 +msgid "" +"Only class methods are defined by this class to alleviate the need for " +"instantiation." +msgstr "" + +#: ../Doc/library/importlib.rst:784 +msgid "" +"As part of :pep:`489`, the builtin importer now implements :meth:`Loader." +"create_module` and :meth:`Loader.exec_module`" +msgstr "" + +#: ../Doc/library/importlib.rst:791 +msgid "" +"An :term:`importer` for frozen modules. This class implements the :class:" +"`importlib.abc.MetaPathFinder` and :class:`importlib.abc.InspectLoader` ABCs." +msgstr "" + +#: ../Doc/library/importlib.rst:801 +msgid "" +":term:`Finder` for modules declared in the Windows registry. This class " +"implements the :class:`importlib.abc.Finder` ABC." +msgstr "" + +#: ../Doc/library/importlib.rst:812 +msgid "" +"A :term:`Finder` for :data:`sys.path` and package ``__path__`` attributes. " +"This class implements the :class:`importlib.abc.MetaPathFinder` ABC." +msgstr "" + +#: ../Doc/library/importlib.rst:820 +msgid "" +"Class method that attempts to find a :term:`spec ` for the " +"module specified by *fullname* on :data:`sys.path` or, if defined, on " +"*path*. For each path entry that is searched, :data:`sys." +"path_importer_cache` is checked. If a non-false object is found then it is " +"used as the :term:`path entry finder` to look for the module being searched " +"for. If no entry is found in :data:`sys.path_importer_cache`, then :data:" +"`sys.path_hooks` is searched for a finder for the path entry and, if found, " +"is stored in :data:`sys.path_importer_cache` along with being queried about " +"the module. If no finder is ever found then ``None`` is both stored in the " +"cache and returned." +msgstr "" + +#: ../Doc/library/importlib.rst:834 +msgid "" +"If the current working directory -- represented by an empty string -- is no " +"longer valid then ``None`` is returned but no value is cached in :data:`sys." +"path_importer_cache`." +msgstr "" + +#: ../Doc/library/importlib.rst:841 +msgid "A legacy wrapper around :meth:`find_spec`." +msgstr "" + +#: ../Doc/library/importlib.rst:848 +msgid "" +"Calls :meth:`importlib.abc.PathEntryFinder.invalidate_caches` on all finders " +"stored in :attr:`sys.path_importer_cache`." +msgstr "" + +#: ../Doc/library/importlib.rst:851 +msgid "" +"Calls objects in :data:`sys.path_hooks` with the current working directory " +"for ``''`` (i.e. the empty string)." +msgstr "" + +#: ../Doc/library/importlib.rst:858 +msgid "" +"A concrete implementation of :class:`importlib.abc.PathEntryFinder` which " +"caches results from the file system." +msgstr "" + +#: ../Doc/library/importlib.rst:861 +msgid "" +"The *path* argument is the directory for which the finder is in charge of " +"searching." +msgstr "" + +#: ../Doc/library/importlib.rst:864 +msgid "" +"The *loader_details* argument is a variable number of 2-item tuples each " +"containing a loader and a sequence of file suffixes the loader recognizes. " +"The loaders are expected to be callables which accept two arguments of the " +"module's name and the path to the file found." +msgstr "" + +#: ../Doc/library/importlib.rst:869 +msgid "" +"The finder will cache the directory contents as necessary, making stat calls " +"for each module search to verify the cache is not outdated. Because cache " +"staleness relies upon the granularity of the operating system's state " +"information of the file system, there is a potential race condition of " +"searching for a module, creating a new file, and then searching for the " +"module the new file represents. If the operations happen fast enough to fit " +"within the granularity of stat calls, then the module search will fail. To " +"prevent this from happening, when you create a module dynamically, make sure " +"to call :func:`importlib.invalidate_caches`." +msgstr "" + +#: ../Doc/library/importlib.rst:883 +msgid "The path the finder will search in." +msgstr "" + +#: ../Doc/library/importlib.rst:887 +msgid "Attempt to find the spec to handle *fullname* within :attr:`path`." +msgstr "" + +#: ../Doc/library/importlib.rst:893 +msgid "Attempt to find the loader to handle *fullname* within :attr:`path`." +msgstr "" + +#: ../Doc/library/importlib.rst:897 +msgid "Clear out the internal cache." +msgstr "" + +#: ../Doc/library/importlib.rst:901 +msgid "" +"A class method which returns a closure for use on :attr:`sys.path_hooks`. An " +"instance of :class:`FileFinder` is returned by the closure using the path " +"argument given to the closure directly and *loader_details* indirectly." +msgstr "" + +#: ../Doc/library/importlib.rst:906 +msgid "" +"If the argument to the closure is not an existing directory, :exc:" +"`ImportError` is raised." +msgstr "" + +#: ../Doc/library/importlib.rst:912 +msgid "" +"A concrete implementation of :class:`importlib.abc.SourceLoader` by " +"subclassing :class:`importlib.abc.FileLoader` and providing some concrete " +"implementations of other methods." +msgstr "" + +#: ../Doc/library/importlib.rst:920 +msgid "The name of the module that this loader will handle." +msgstr "" + +#: ../Doc/library/importlib.rst:924 +msgid "The path to the source file." +msgstr "" + +#: ../Doc/library/importlib.rst:928 +msgid "Return true if :attr:`path` appears to be for a package." +msgstr "" + +#: ../Doc/library/importlib.rst:932 +msgid "" +"Concrete implementation of :meth:`importlib.abc.SourceLoader.path_stats`." +msgstr "" + +#: ../Doc/library/importlib.rst:936 +msgid "Concrete implementation of :meth:`importlib.abc.SourceLoader.set_data`." +msgstr "" + +#: ../Doc/library/importlib.rst:940 ../Doc/library/importlib.rst:983 +msgid "" +"Concrete implementation of :meth:`importlib.abc.Loader.load_module` where " +"specifying the name of the module to load is optional." +msgstr "" + +#: ../Doc/library/importlib.rst:945 ../Doc/library/importlib.rst:988 +msgid "Use :meth:`importlib.abc.Loader.exec_module` instead." +msgstr "" + +#: ../Doc/library/importlib.rst:950 +msgid "" +"A concrete implementation of :class:`importlib.abc.FileLoader` which can " +"import bytecode files (i.e. no source code files exist)." +msgstr "" + +#: ../Doc/library/importlib.rst:953 +msgid "" +"Please note that direct use of bytecode files (and thus not source code " +"files) inhibits your modules from being usable by all Python implementations " +"or new versions of Python which change the bytecode format." +msgstr "" + +#: ../Doc/library/importlib.rst:962 +msgid "The name of the module the loader will handle." +msgstr "" + +#: ../Doc/library/importlib.rst:966 +msgid "The path to the bytecode file." +msgstr "" + +#: ../Doc/library/importlib.rst:970 +msgid "Determines if the module is a package based on :attr:`path`." +msgstr "" + +#: ../Doc/library/importlib.rst:974 +msgid "Returns the code object for :attr:`name` created from :attr:`path`." +msgstr "" + +#: ../Doc/library/importlib.rst:978 +msgid "" +"Returns ``None`` as bytecode files have no source when this loader is used." +msgstr "" + +#: ../Doc/library/importlib.rst:993 +msgid "" +"A concrete implementation of :class:`importlib.abc.ExecutionLoader` for " +"extension modules." +msgstr "" + +#: ../Doc/library/importlib.rst:996 +msgid "" +"The *fullname* argument specifies the name of the module the loader is to " +"support. The *path* argument is the path to the extension module's file." +msgstr "" + +#: ../Doc/library/importlib.rst:1003 +msgid "Name of the module the loader supports." +msgstr "" + +#: ../Doc/library/importlib.rst:1007 +msgid "Path to the extension module." +msgstr "" + +#: ../Doc/library/importlib.rst:1011 +msgid "" +"Creates the module object from the given specification in accordance with :" +"pep:`489`." +msgstr "" + +#: ../Doc/library/importlib.rst:1018 +msgid "Initializes the given module object in accordance with :pep:`489`." +msgstr "" + +#: ../Doc/library/importlib.rst:1024 +msgid "" +"Returns ``True`` if the file path points to a package's ``__init__`` module " +"based on :attr:`EXTENSION_SUFFIXES`." +msgstr "" + +#: ../Doc/library/importlib.rst:1029 +msgid "Returns ``None`` as extension modules lack a code object." +msgstr "" + +#: ../Doc/library/importlib.rst:1033 +msgid "Returns ``None`` as extension modules do not have source code." +msgstr "" + +#: ../Doc/library/importlib.rst:1044 +msgid "A specification for a module's import-system-related state." +msgstr "" + +#: ../Doc/library/importlib.rst:1050 +msgid "(``__name__``)" +msgstr "" + +#: ../Doc/library/importlib.rst:1052 +msgid "A string for the fully-qualified name of the module." +msgstr "" + +#: ../Doc/library/importlib.rst:1056 +msgid "(``__loader__``)" +msgstr "" + +#: ../Doc/library/importlib.rst:1058 +msgid "" +"The loader to use for loading. For namespace packages this should be set to " +"None." +msgstr "" + +#: ../Doc/library/importlib.rst:1063 +msgid "(``__file__``)" +msgstr "" + +#: ../Doc/library/importlib.rst:1065 +msgid "" +"Name of the place from which the module is loaded, e.g. \"builtin\" for " +"built-in modules and the filename for modules loaded from source. Normally " +"\"origin\" should be set, but it may be None (the default) which indicates " +"it is unspecified." +msgstr "" + +#: ../Doc/library/importlib.rst:1072 +msgid "(``__path__``)" +msgstr "" + +#: ../Doc/library/importlib.rst:1074 +msgid "" +"List of strings for where to find submodules, if a package (None otherwise)." +msgstr "" + +#: ../Doc/library/importlib.rst:1079 +msgid "" +"Container of extra module-specific data for use during loading (or None)." +msgstr "" + +#: ../Doc/library/importlib.rst:1084 +msgid "(``__cached__``)" +msgstr "" + +#: ../Doc/library/importlib.rst:1086 +msgid "String for where the compiled module should be stored (or None)." +msgstr "" + +#: ../Doc/library/importlib.rst:1090 +msgid "(``__package__``)" +msgstr "" + +#: ../Doc/library/importlib.rst:1092 +msgid "" +"(Read-only) Fully-qualified name of the package to which the module belongs " +"as a submodule (or None)." +msgstr "" + +#: ../Doc/library/importlib.rst:1097 +msgid "" +"Boolean indicating whether or not the module's \"origin\" attribute refers " +"to a loadable location." +msgstr "" + +#: ../Doc/library/importlib.rst:1101 +msgid ":mod:`importlib.util` -- Utility code for importers" +msgstr "" + +#: ../Doc/library/importlib.rst:1107 +msgid "**Source code:** :source:`Lib/importlib/util.py`" +msgstr "" + +#: ../Doc/library/importlib.rst:1111 +msgid "" +"This module contains the various objects that help in the construction of " +"an :term:`importer`." +msgstr "" + +#: ../Doc/library/importlib.rst:1116 +msgid "" +"The bytes which represent the bytecode version number. If you need help with " +"loading/writing bytecode then consider :class:`importlib.abc.SourceLoader`." +msgstr "" + +#: ../Doc/library/importlib.rst:1123 +msgid "" +"Return the :pep:`3147`/:pep:`488` path to the byte-compiled file associated " +"with the source *path*. For example, if *path* is ``/foo/bar/baz.py`` the " +"return value would be ``/foo/bar/__pycache__/baz.cpython-32.pyc`` for Python " +"3.2. The ``cpython-32`` string comes from the current magic tag (see :func:" +"`get_tag`; if :attr:`sys.implementation.cache_tag` is not defined then :exc:" +"`NotImplementedError` will be raised)." +msgstr "" + +#: ../Doc/library/importlib.rst:1130 +msgid "" +"The *optimization* parameter is used to specify the optimization level of " +"the bytecode file. An empty string represents no optimization, so ``/foo/bar/" +"baz.py`` with an *optimization* of ``''`` will result in a bytecode path of " +"``/foo/bar/__pycache__/baz.cpython-32.pyc``. ``None`` causes the interpter's " +"optimization level to be used. Any other value's string representation being " +"used, so ``/foo/bar/baz.py`` with an *optimization* of ``2`` will lead to " +"the bytecode path of ``/foo/bar/__pycache__/baz.cpython-32.opt-2.pyc``. The " +"string representation of *optimization* can only be alphanumeric, else :exc:" +"`ValueError` is raised." +msgstr "" + +#: ../Doc/library/importlib.rst:1140 +msgid "" +"The *debug_override* parameter is deprecated and can be used to override the " +"system's value for ``__debug__``. A ``True`` value is the equivalent of " +"setting *optimization* to the empty string. A ``False`` value is the same as " +"setting *optimization* to ``1``. If both *debug_override* an *optimization* " +"are not ``None`` then :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/importlib.rst:1148 +msgid "" +"The *optimization* parameter was added and the *debug_override* parameter " +"was deprecated." +msgstr "" + +#: ../Doc/library/importlib.rst:1158 +msgid "" +"Given the *path* to a :pep:`3147` file name, return the associated source " +"code file path. For example, if *path* is ``/foo/bar/__pycache__/baz." +"cpython-32.pyc`` the returned path would be ``/foo/bar/baz.py``. *path* " +"need not exist, however if it does not conform to :pep:`3147` or :pep:`488` " +"format, a ``ValueError`` is raised. If :attr:`sys.implementation.cache_tag` " +"is not defined, :exc:`NotImplementedError` is raised." +msgstr "" + +#: ../Doc/library/importlib.rst:1173 +msgid "" +"Decode the given bytes representing source code and return it as a string " +"with universal newlines (as required by :meth:`importlib.abc.InspectLoader." +"get_source`)." +msgstr "" + +#: ../Doc/library/importlib.rst:1181 +msgid "Resolve a relative module name to an absolute one." +msgstr "" + +#: ../Doc/library/importlib.rst:1183 +msgid "" +"If **name** has no leading dots, then **name** is simply returned. This " +"allows for usage such as ``importlib.util.resolve_name('sys', __package__)`` " +"without doing a check to see if the **package** argument is needed." +msgstr "" + +#: ../Doc/library/importlib.rst:1188 +msgid "" +":exc:`ValueError` is raised if **name** is a relative module name but " +"package is a false value (e.g. ``None`` or the empty string). :exc:" +"`ValueError` is also raised a relative name would escape its containing " +"package (e.g. requesting ``..bacon`` from within the ``spam`` package)." +msgstr "" + +#: ../Doc/library/importlib.rst:1197 +msgid "" +"Find the :term:`spec ` for a module, optionally relative to the " +"specified **package** name. If the module is in :attr:`sys.modules`, then " +"``sys.modules[name].__spec__`` is returned (unless the spec would be " +"``None`` or is not set, in which case :exc:`ValueError` is raised). " +"Otherwise a search using :attr:`sys.meta_path` is done. ``None`` is returned " +"if no spec is found." +msgstr "" + +#: ../Doc/library/importlib.rst:1204 +msgid "" +"If **name** is for a submodule (contains a dot), the parent module is " +"automatically imported." +msgstr "" + +#: ../Doc/library/importlib.rst:1207 +msgid "**name** and **package** work the same as for :func:`import_module`." +msgstr "" + +#: ../Doc/library/importlib.rst:1213 +msgid "" +"Create a new module based on **spec** and :meth:`spec.loader.create_module " +"`." +msgstr "" + +#: ../Doc/library/importlib.rst:1216 +msgid "" +"If :meth:`spec.loader.create_module ` " +"does not return ``None``, then any pre-existing attributes will not be " +"reset. Also, no :exc:`AttributeError` will be raised if triggered while " +"accessing **spec** or setting an attribute on the module." +msgstr "" + +#: ../Doc/library/importlib.rst:1221 +msgid "" +"This function is preferred over using :class:`types.ModuleType` to create a " +"new module as **spec** is used to set as many import-controlled attributes " +"on the module as possible." +msgstr "" + +#: ../Doc/library/importlib.rst:1229 +msgid "" +"A :term:`decorator` for :meth:`importlib.abc.Loader.load_module` to handle " +"selecting the proper module object to load with. The decorated method is " +"expected to have a call signature taking two positional arguments (e.g. " +"``load_module(self, module)``) for which the second argument will be the " +"module **object** to be used by the loader. Note that the decorator will not " +"work on static methods because of the assumption of two arguments." +msgstr "" + +#: ../Doc/library/importlib.rst:1238 +msgid "" +"The decorated method will take in the **name** of the module to be loaded as " +"expected for a :term:`loader`. If the module is not found in :data:`sys." +"modules` then a new one is constructed. Regardless of where the module came " +"from, :attr:`__loader__` set to **self** and :attr:`__package__` is set " +"based on what :meth:`importlib.abc.InspectLoader.is_package` returns (if " +"available). These attributes are set unconditionally to support reloading." +msgstr "" + +#: ../Doc/library/importlib.rst:1246 +msgid "" +"If an exception is raised by the decorated method and a module was added to :" +"data:`sys.modules`, then the module will be removed to prevent a partially " +"initialized module from being in left in :data:`sys.modules`. If the module " +"was already in :data:`sys.modules` then it is left alone." +msgstr "" + +#: ../Doc/library/importlib.rst:1251 +msgid "" +":attr:`__loader__` and :attr:`__package__` are automatically set (when " +"possible)." +msgstr "" + +#: ../Doc/library/importlib.rst:1255 +msgid "" +"Set :attr:`__name__`, :attr:`__loader__` :attr:`__package__` unconditionally " +"to support reloading." +msgstr "" + +#: ../Doc/library/importlib.rst:1259 +msgid "" +"The import machinery now directly performs all the functionality provided by " +"this function." +msgstr "" + +#: ../Doc/library/importlib.rst:1265 +msgid "" +"A :term:`decorator` for :meth:`importlib.abc.Loader.load_module` to set the :" +"attr:`__loader__` attribute on the returned module. If the attribute is " +"already set the decorator does nothing. It is assumed that the first " +"positional argument to the wrapped method (i.e. ``self``) is what :attr:" +"`__loader__` should be set to." +msgstr "" + +#: ../Doc/library/importlib.rst:1272 +msgid "" +"Set ``__loader__`` if set to ``None``, as if the attribute does not exist." +msgstr "" + +#: ../Doc/library/importlib.rst:1276 ../Doc/library/importlib.rst:1285 +msgid "The import machinery takes care of this automatically." +msgstr "" + +#: ../Doc/library/importlib.rst:1281 +msgid "" +"A :term:`decorator` for :meth:`importlib.abc.Loader.load_module` to set the :" +"attr:`__package__` attribute on the returned module. If :attr:`__package__` " +"is set and has a value other than ``None`` it will not be changed." +msgstr "" + +#: ../Doc/library/importlib.rst:1290 +msgid "" +"A factory function for creating a :class:`ModuleSpec` instance based on a " +"loader. The parameters have the same meaning as they do for ModuleSpec. " +"The function uses available :term:`loader` APIs, such as :meth:" +"`InspectLoader.is_package`, to fill in any missing information on the spec." +msgstr "" + +#: ../Doc/library/importlib.rst:1300 +msgid "" +"A factory function for creating a :class:`ModuleSpec` instance based on the " +"path to a file. Missing information will be filled in on the spec by making " +"use of loader APIs and by the implication that the module will be file-based." +msgstr "" + +#: ../Doc/library/importlib.rst:1312 +msgid "" +"A class which postpones the execution of the loader of a module until the " +"module has an attribute accessed." +msgstr "" + +#: ../Doc/library/importlib.rst:1315 +msgid "" +"This class **only** works with loaders that define :meth:`~importlib.abc." +"Loader.exec_module` as control over what module type is used for the module " +"is required. For those same reasons, the loader's :meth:`~importlib.abc." +"Loader.create_module` method must return ``None`` or a type for which its " +"``__class__`` attribute can be mutated along with not using :term:`slots " +"<__slots__>`. Finally, modules which substitute the object placed into :attr:" +"`sys.modules` will not work as there is no way to properly replace the " +"module references throughout the interpreter safely; :exc:`ValueError` is " +"raised if such a substitution is detected." +msgstr "" + +#: ../Doc/library/importlib.rst:1326 +msgid "" +"For projects where startup time is critical, this class allows for " +"potentially minimizing the cost of loading a module if it is never used. For " +"projects where startup time is not essential then use of this class is " +"**heavily** discouraged due to error messages created during loading being " +"postponed and thus occurring out of context." +msgstr "" + +#: ../Doc/library/importlib.rst:1334 +msgid "" +"Began calling :meth:`~importlib.abc.Loader.create_module`, removing the " +"compatibility warning for :class:`importlib.machinery.BuiltinImporter` and :" +"class:`importlib.machinery.ExtensionFileLoader`." +msgstr "" + +#: ../Doc/library/importlib.rst:1341 +msgid "" +"A static method which returns a callable that creates a lazy loader. This is " +"meant to be used in situations where the loader is passed by class instead " +"of by instance. ::" +msgstr "" + +#: ../Doc/library/importlib.rst:1357 +msgid "Importing programmatically" +msgstr "" + +#: ../Doc/library/importlib.rst:1359 +msgid "" +"To programmatically import a module, use :func:`importlib.import_module`. ::" +msgstr "" + +#: ../Doc/library/importlib.rst:1368 +msgid "Checking if a module can be imported" +msgstr "" + +#: ../Doc/library/importlib.rst:1370 +msgid "" +"If you need to find out if a module can be imported without actually doing " +"the import, then you should use :func:`importlib.util.find_spec`. ::" +msgstr "" + +#: ../Doc/library/importlib.rst:1392 +msgid "Importing a source file directly" +msgstr "" + +#: ../Doc/library/importlib.rst:1394 +msgid "" +"To import a Python source file directly, use the following recipe (Python " +"3.4 and newer only)::" +msgstr "" + +#: ../Doc/library/importlib.rst:1414 +msgid "Setting up an importer" +msgstr "" + +#: ../Doc/library/importlib.rst:1416 +msgid "" +"For deep customizations of import, you typically want to implement an :term:" +"`importer`. This means managing both the :term:`finder` and :term:`loader` " +"side of things. For finders there are two flavours to choose from depending " +"on your needs: a :term:`meta path finder` or a :term:`path entry finder`. " +"The former is what you would put on :attr:`sys.meta_path` while the latter " +"is what you create using a :term:`path entry hook` on :attr:`sys.path_hooks` " +"which works with :attr:`sys.path` entries to potentially create a finder. " +"This example will show you how to register your own importers so that import " +"will use them (for creating an importer for yourself, read the documentation " +"for the appropriate classes defined within this package)::" +msgstr "" + +#: ../Doc/library/importlib.rst:1448 +msgid "Approximating :func:`importlib.import_module`" +msgstr "" + +#: ../Doc/library/importlib.rst:1450 +msgid "" +"Import itself is implemented in Python code, making it possible to expose " +"most of the import machinery through importlib. The following helps " +"illustrate the various APIs that importlib exposes by providing an " +"approximate implementation of :func:`importlib.import_module` (Python 3.4 " +"and newer for the importlib usage, Python 3.6 and newer for other parts of " +"the code). ::" +msgstr "" + +#: ../Doc/library/index.rst:5 +msgid "The Python Standard Library" +msgstr "" + +#: ../Doc/library/index.rst:7 +msgid "" +"While :ref:`reference-index` describes the exact syntax and semantics of the " +"Python language, this library reference manual describes the standard " +"library that is distributed with Python. It also describes some of the " +"optional components that are commonly included in Python distributions." +msgstr "" + +#: ../Doc/library/index.rst:13 +msgid "" +"Python's standard library is very extensive, offering a wide range of " +"facilities as indicated by the long table of contents listed below. The " +"library contains built-in modules (written in C) that provide access to " +"system functionality such as file I/O that would otherwise be inaccessible " +"to Python programmers, as well as modules written in Python that provide " +"standardized solutions for many problems that occur in everyday programming. " +"Some of these modules are explicitly designed to encourage and enhance the " +"portability of Python programs by abstracting away platform-specifics into " +"platform-neutral APIs." +msgstr "" + +#: ../Doc/library/index.rst:23 +msgid "" +"The Python installers for the Windows platform usually include the entire " +"standard library and often also include many additional components. For Unix-" +"like operating systems Python is normally provided as a collection of " +"packages, so it may be necessary to use the packaging tools provided with " +"the operating system to obtain some or all of the optional components." +msgstr "" + +#: ../Doc/library/index.rst:30 +msgid "" +"In addition to the standard library, there is a growing collection of " +"several thousand components (from individual programs and modules to " +"packages and entire application development frameworks), available from the " +"`Python Package Index `_." +msgstr "" + +#: ../Doc/library/inspect.rst:2 +msgid ":mod:`inspect` --- Inspect live objects" +msgstr "" + +#: ../Doc/library/inspect.rst:10 +msgid "**Source code:** :source:`Lib/inspect.py`" +msgstr "" + +#: ../Doc/library/inspect.rst:14 +msgid "" +"The :mod:`inspect` module provides several useful functions to help get " +"information about live objects such as modules, classes, methods, functions, " +"tracebacks, frame objects, and code objects. For example, it can help you " +"examine the contents of a class, retrieve the source code of a method, " +"extract and format the argument list for a function, or get all the " +"information you need to display a detailed traceback." +msgstr "" + +#: ../Doc/library/inspect.rst:21 +msgid "" +"There are four main kinds of services provided by this module: type " +"checking, getting source code, inspecting classes and functions, and " +"examining the interpreter stack." +msgstr "" + +#: ../Doc/library/inspect.rst:29 +msgid "Types and members" +msgstr "" + +#: ../Doc/library/inspect.rst:31 +msgid "" +"The :func:`getmembers` function retrieves the members of an object such as a " +"class or module. The functions whose names begin with \"is\" are mainly " +"provided as convenient choices for the second argument to :func:" +"`getmembers`. They also help you determine when you can expect to find the " +"following special attributes:" +msgstr "" + +#: ../Doc/library/inspect.rst:38 ../Doc/library/string.rst:412 +#: ../Doc/library/string.rst:423 ../Doc/library/string.rst:455 +msgid "Type" +msgstr "" + +#: ../Doc/library/inspect.rst:40 ../Doc/library/logging.rst:775 +msgid "module" +msgstr "" + +#: ../Doc/library/inspect.rst:40 ../Doc/library/inspect.rst:45 +#: ../Doc/library/inspect.rst:55 ../Doc/library/inspect.rst:70 +#: ../Doc/library/inspect.rst:205 +msgid "__doc__" +msgstr "" + +#: ../Doc/library/inspect.rst:40 ../Doc/library/inspect.rst:45 +#: ../Doc/library/inspect.rst:55 ../Doc/library/inspect.rst:70 +#: ../Doc/library/inspect.rst:205 +msgid "documentation string" +msgstr "" + +#: ../Doc/library/inspect.rst:42 +msgid "__file__" +msgstr "" + +#: ../Doc/library/inspect.rst:42 +msgid "filename (missing for built-in modules)" +msgstr "" + +#: ../Doc/library/inspect.rst:45 ../Doc/library/tkinter.ttk.rst:114 +msgid "class" +msgstr "" + +#: ../Doc/library/inspect.rst:47 ../Doc/library/inspect.rst:57 +#: ../Doc/library/inspect.rst:72 ../Doc/library/inspect.rst:178 +#: ../Doc/library/inspect.rst:192 ../Doc/library/inspect.rst:207 +msgid "__name__" +msgstr "" + +#: ../Doc/library/inspect.rst:47 +msgid "name with which this class was defined" +msgstr "" + +#: ../Doc/library/inspect.rst:50 ../Doc/library/inspect.rst:60 +#: ../Doc/library/inspect.rst:75 ../Doc/library/inspect.rst:180 +#: ../Doc/library/inspect.rst:194 ../Doc/library/inspect.rst:210 +msgid "__qualname__" +msgstr "" + +#: ../Doc/library/inspect.rst:50 ../Doc/library/inspect.rst:60 +#: ../Doc/library/inspect.rst:75 ../Doc/library/inspect.rst:180 +#: ../Doc/library/inspect.rst:194 ../Doc/library/inspect.rst:210 +msgid "qualified name" +msgstr "" + +#: ../Doc/library/inspect.rst:52 +msgid "__module__" +msgstr "" + +#: ../Doc/library/inspect.rst:52 +msgid "name of module in which this class was defined" +msgstr "" + +#: ../Doc/library/inspect.rst:55 +msgid "method" +msgstr "" + +#: ../Doc/library/inspect.rst:57 +msgid "name with which this method was defined" +msgstr "" + +#: ../Doc/library/inspect.rst:62 +msgid "__func__" +msgstr "" + +#: ../Doc/library/inspect.rst:62 +msgid "function object containing implementation of method" +msgstr "" + +#: ../Doc/library/inspect.rst:66 ../Doc/library/inspect.rst:212 +msgid "__self__" +msgstr "" + +#: ../Doc/library/inspect.rst:66 +msgid "instance to which this method is bound, or ``None``" +msgstr "" + +#: ../Doc/library/inspect.rst:70 +msgid "function" +msgstr "" + +#: ../Doc/library/inspect.rst:72 +msgid "name with which this function was defined" +msgstr "" + +#: ../Doc/library/inspect.rst:77 +msgid "__code__" +msgstr "" + +#: ../Doc/library/inspect.rst:77 +msgid "code object containing compiled function :term:`bytecode`" +msgstr "" + +#: ../Doc/library/inspect.rst:81 +msgid "__defaults__" +msgstr "" + +#: ../Doc/library/inspect.rst:81 +msgid "tuple of any default values for positional or keyword parameters" +msgstr "" + +#: ../Doc/library/inspect.rst:85 +msgid "__kwdefaults__" +msgstr "" + +#: ../Doc/library/inspect.rst:85 +msgid "mapping of any default values for keyword-only parameters" +msgstr "" + +#: ../Doc/library/inspect.rst:89 +msgid "__globals__" +msgstr "" + +#: ../Doc/library/inspect.rst:89 +msgid "global namespace in which this function was defined" +msgstr "" + +#: ../Doc/library/inspect.rst:92 +msgid "__annotations__" +msgstr "" + +#: ../Doc/library/inspect.rst:92 +msgid "" +"mapping of parameters names to annotations; ``\"return\"`` key is reserved " +"for return annotations." +msgstr "" + +#: ../Doc/library/inspect.rst:98 ../Doc/library/tracemalloc.rst:524 +msgid "traceback" +msgstr "" + +#: ../Doc/library/inspect.rst:98 +msgid "tb_frame" +msgstr "" + +#: ../Doc/library/inspect.rst:98 +msgid "frame object at this level" +msgstr "" + +#: ../Doc/library/inspect.rst:101 +msgid "tb_lasti" +msgstr "" + +#: ../Doc/library/inspect.rst:101 ../Doc/library/inspect.rst:123 +msgid "index of last attempted instruction in bytecode" +msgstr "" + +#: ../Doc/library/inspect.rst:104 +msgid "tb_lineno" +msgstr "" + +#: ../Doc/library/inspect.rst:104 ../Doc/library/inspect.rst:126 +msgid "current line number in Python source code" +msgstr "" + +#: ../Doc/library/inspect.rst:107 +msgid "tb_next" +msgstr "" + +#: ../Doc/library/inspect.rst:107 +msgid "next inner traceback object (called by this level)" +msgstr "" + +#: ../Doc/library/inspect.rst:111 ../Doc/library/inspect.rst:182 +#: ../Doc/library/inspect.rst:199 +msgid "frame" +msgstr "" + +#: ../Doc/library/inspect.rst:111 +msgid "f_back" +msgstr "" + +#: ../Doc/library/inspect.rst:111 +msgid "next outer frame object (this frame's caller)" +msgstr "" + +#: ../Doc/library/inspect.rst:114 +msgid "f_builtins" +msgstr "" + +#: ../Doc/library/inspect.rst:114 +msgid "builtins namespace seen by this frame" +msgstr "" + +#: ../Doc/library/inspect.rst:117 +msgid "f_code" +msgstr "" + +#: ../Doc/library/inspect.rst:117 +msgid "code object being executed in this frame" +msgstr "" + +#: ../Doc/library/inspect.rst:120 +msgid "f_globals" +msgstr "" + +#: ../Doc/library/inspect.rst:120 +msgid "global namespace seen by this frame" +msgstr "" + +#: ../Doc/library/inspect.rst:123 +msgid "f_lasti" +msgstr "" + +#: ../Doc/library/inspect.rst:126 +msgid "f_lineno" +msgstr "" + +#: ../Doc/library/inspect.rst:129 +msgid "f_locals" +msgstr "" + +#: ../Doc/library/inspect.rst:129 +msgid "local namespace seen by this frame" +msgstr "" + +#: ../Doc/library/inspect.rst:132 +msgid "f_restricted" +msgstr "" + +#: ../Doc/library/inspect.rst:132 +msgid "0 or 1 if frame is in restricted execution mode" +msgstr "" + +#: ../Doc/library/inspect.rst:135 +msgid "f_trace" +msgstr "" + +#: ../Doc/library/inspect.rst:135 +msgid "tracing function for this frame, or ``None``" +msgstr "" + +#: ../Doc/library/inspect.rst:138 ../Doc/library/inspect.rst:186 +#: ../Doc/library/inspect.rst:203 +msgid "code" +msgstr "" + +#: ../Doc/library/inspect.rst:138 +msgid "co_argcount" +msgstr "" + +#: ../Doc/library/inspect.rst:138 +msgid "number of arguments (not including \\* or \\*\\* args)" +msgstr "" + +#: ../Doc/library/inspect.rst:142 +msgid "co_code" +msgstr "" + +#: ../Doc/library/inspect.rst:142 +msgid "string of raw compiled bytecode" +msgstr "" + +#: ../Doc/library/inspect.rst:145 +msgid "co_consts" +msgstr "" + +#: ../Doc/library/inspect.rst:145 +msgid "tuple of constants used in the bytecode" +msgstr "" + +#: ../Doc/library/inspect.rst:148 +msgid "co_filename" +msgstr "" + +#: ../Doc/library/inspect.rst:148 +msgid "name of file in which this code object was created" +msgstr "" + +#: ../Doc/library/inspect.rst:152 +msgid "co_firstlineno" +msgstr "" + +#: ../Doc/library/inspect.rst:152 +msgid "number of first line in Python source code" +msgstr "" + +#: ../Doc/library/inspect.rst:155 +msgid "co_flags" +msgstr "" + +#: ../Doc/library/inspect.rst:155 +msgid "bitmap: 1=optimized ``|`` 2=newlocals ``|`` 4=\\*arg ``|`` 8=\\*\\*arg" +msgstr "" + +#: ../Doc/library/inspect.rst:159 +msgid "co_lnotab" +msgstr "" + +#: ../Doc/library/inspect.rst:159 +msgid "encoded mapping of line numbers to bytecode indices" +msgstr "" + +#: ../Doc/library/inspect.rst:163 +msgid "co_name" +msgstr "" + +#: ../Doc/library/inspect.rst:163 +msgid "name with which this code object was defined" +msgstr "" + +#: ../Doc/library/inspect.rst:166 +msgid "co_names" +msgstr "" + +#: ../Doc/library/inspect.rst:166 +msgid "tuple of names of local variables" +msgstr "" + +#: ../Doc/library/inspect.rst:169 +msgid "co_nlocals" +msgstr "" + +#: ../Doc/library/inspect.rst:169 +msgid "number of local variables" +msgstr "" + +#: ../Doc/library/inspect.rst:171 +msgid "co_stacksize" +msgstr "" + +#: ../Doc/library/inspect.rst:171 +msgid "virtual machine stack space required" +msgstr "" + +#: ../Doc/library/inspect.rst:174 +msgid "co_varnames" +msgstr "" + +#: ../Doc/library/inspect.rst:174 +msgid "tuple of names of arguments and local variables" +msgstr "" + +#: ../Doc/library/inspect.rst:178 +msgid "generator" +msgstr "" + +#: ../Doc/library/inspect.rst:178 ../Doc/library/inspect.rst:192 +#: ../Doc/library/logging.rst:789 +msgid "name" +msgstr "" + +#: ../Doc/library/inspect.rst:182 +msgid "gi_frame" +msgstr "" + +#: ../Doc/library/inspect.rst:184 +msgid "gi_running" +msgstr "" + +#: ../Doc/library/inspect.rst:184 +msgid "is the generator running?" +msgstr "" + +#: ../Doc/library/inspect.rst:186 +msgid "gi_code" +msgstr "" + +#: ../Doc/library/inspect.rst:188 +msgid "gi_yieldfrom" +msgstr "" + +#: ../Doc/library/inspect.rst:188 +msgid "object being iterated by ``yield from``, or ``None``" +msgstr "" + +#: ../Doc/library/inspect.rst:192 +msgid "coroutine" +msgstr "" + +#: ../Doc/library/inspect.rst:196 +msgid "cr_await" +msgstr "" + +#: ../Doc/library/inspect.rst:196 +msgid "object being awaited on, or ``None``" +msgstr "" + +#: ../Doc/library/inspect.rst:199 +msgid "cr_frame" +msgstr "" + +#: ../Doc/library/inspect.rst:201 +msgid "cr_running" +msgstr "" + +#: ../Doc/library/inspect.rst:201 +msgid "is the coroutine running?" +msgstr "" + +#: ../Doc/library/inspect.rst:203 +msgid "cr_code" +msgstr "" + +#: ../Doc/library/inspect.rst:205 +msgid "builtin" +msgstr "" + +#: ../Doc/library/inspect.rst:207 +msgid "original name of this function or method" +msgstr "" + +#: ../Doc/library/inspect.rst:212 +msgid "instance to which a method is bound, or ``None``" +msgstr "" + +#: ../Doc/library/inspect.rst:219 +msgid "Add ``__qualname__`` and ``gi_yieldfrom`` attributes to generators." +msgstr "" + +#: ../Doc/library/inspect.rst:221 +msgid "" +"The ``__name__`` attribute of generators is now set from the function name, " +"instead of the code name, and it can now be modified." +msgstr "" + +#: ../Doc/library/inspect.rst:227 +msgid "" +"Return all the members of an object in a list of (name, value) pairs sorted " +"by name. If the optional *predicate* argument is supplied, only members for " +"which the predicate returns a true value are included." +msgstr "" + +#: ../Doc/library/inspect.rst:233 +msgid "" +":func:`getmembers` will only return class attributes defined in the " +"metaclass when the argument is a class and those attributes have been listed " +"in the metaclass' custom :meth:`__dir__`." +msgstr "" + +#: ../Doc/library/inspect.rst:240 +msgid "" +"Return the name of the module named by the file *path*, without including " +"the names of enclosing packages. The file extension is checked against all " +"of the entries in :func:`importlib.machinery.all_suffixes`. If it matches, " +"the final path component is returned with the extension removed. Otherwise, " +"``None`` is returned." +msgstr "" + +#: ../Doc/library/inspect.rst:246 +msgid "" +"Note that this function *only* returns a meaningful name for actual Python " +"modules - paths that potentially refer to Python packages will still return " +"``None``." +msgstr "" + +#: ../Doc/library/inspect.rst:250 +msgid "The function is based directly on :mod:`importlib`." +msgstr "" + +#: ../Doc/library/inspect.rst:256 +msgid "Return true if the object is a module." +msgstr "" + +#: ../Doc/library/inspect.rst:261 +msgid "" +"Return true if the object is a class, whether built-in or created in Python " +"code." +msgstr "" + +#: ../Doc/library/inspect.rst:267 +msgid "Return true if the object is a bound method written in Python." +msgstr "" + +#: ../Doc/library/inspect.rst:272 +msgid "" +"Return true if the object is a Python function, which includes functions " +"created by a :term:`lambda` expression." +msgstr "" + +#: ../Doc/library/inspect.rst:278 +msgid "Return true if the object is a Python generator function." +msgstr "" + +#: ../Doc/library/inspect.rst:283 +msgid "Return true if the object is a generator." +msgstr "" + +#: ../Doc/library/inspect.rst:288 +msgid "" +"Return true if the object is a :term:`coroutine function` (a function " +"defined with an :keyword:`async def` syntax)." +msgstr "" + +#: ../Doc/library/inspect.rst:296 +msgid "" +"Return true if the object is a :term:`coroutine` created by an :keyword:" +"`async def` function." +msgstr "" + +#: ../Doc/library/inspect.rst:304 +msgid "Return true if the object can be used in :keyword:`await` expression." +msgstr "" + +#: ../Doc/library/inspect.rst:306 +msgid "" +"Can also be used to distinguish generator-based coroutines from regular " +"generators::" +msgstr "" + +#: ../Doc/library/inspect.rst:323 +msgid "Return true if the object is a traceback." +msgstr "" + +#: ../Doc/library/inspect.rst:328 +msgid "Return true if the object is a frame." +msgstr "" + +#: ../Doc/library/inspect.rst:333 +msgid "Return true if the object is a code." +msgstr "" + +#: ../Doc/library/inspect.rst:338 +msgid "" +"Return true if the object is a built-in function or a bound built-in method." +msgstr "" + +#: ../Doc/library/inspect.rst:343 +msgid "" +"Return true if the object is a user-defined or built-in function or method." +msgstr "" + +#: ../Doc/library/inspect.rst:348 +msgid "Return true if the object is an abstract base class." +msgstr "" + +#: ../Doc/library/inspect.rst:353 +msgid "" +"Return true if the object is a method descriptor, but not if :func:" +"`ismethod`, :func:`isclass`, :func:`isfunction` or :func:`isbuiltin` are " +"true." +msgstr "" + +#: ../Doc/library/inspect.rst:357 +msgid "" +"This, for example, is true of ``int.__add__``. An object passing this test " +"has a :meth:`~object.__get__` method but not a :meth:`~object.__set__` " +"method, but beyond that the set of attributes varies. A :attr:`~definition." +"__name__` attribute is usually sensible, and :attr:`__doc__` often is." +msgstr "" + +#: ../Doc/library/inspect.rst:363 +msgid "" +"Methods implemented via descriptors that also pass one of the other tests " +"return false from the :func:`ismethoddescriptor` test, simply because the " +"other tests promise more -- you can, e.g., count on having the :attr:" +"`__func__` attribute (etc) when an object passes :func:`ismethod`." +msgstr "" + +#: ../Doc/library/inspect.rst:371 +msgid "Return true if the object is a data descriptor." +msgstr "" + +#: ../Doc/library/inspect.rst:373 +msgid "" +"Data descriptors have both a :attr:`~object.__get__` and a :attr:`~object." +"__set__` method. Examples are properties (defined in Python), getsets, and " +"members. The latter two are defined in C and there are more specific tests " +"available for those types, which is robust across Python implementations. " +"Typically, data descriptors will also have :attr:`~definition.__name__` and :" +"attr:`__doc__` attributes (properties, getsets, and members have both of " +"these attributes), but this is not guaranteed." +msgstr "" + +#: ../Doc/library/inspect.rst:384 +msgid "Return true if the object is a getset descriptor." +msgstr "" + +#: ../Doc/library/inspect.rst:388 +msgid "" +"getsets are attributes defined in extension modules via :c:type:" +"`PyGetSetDef` structures. For Python implementations without such types, " +"this method will always return ``False``." +msgstr "" + +#: ../Doc/library/inspect.rst:395 +msgid "Return true if the object is a member descriptor." +msgstr "" + +#: ../Doc/library/inspect.rst:399 +msgid "" +"Member descriptors are attributes defined in extension modules via :c:type:" +"`PyMemberDef` structures. For Python implementations without such types, " +"this method will always return ``False``." +msgstr "" + +#: ../Doc/library/inspect.rst:407 +msgid "Retrieving source code" +msgstr "" + +#: ../Doc/library/inspect.rst:411 +msgid "" +"Get the documentation string for an object, cleaned up with :func:" +"`cleandoc`. If the documentation string for an object is not provided and " +"the object is a class, a method, a property or a descriptor, retrieve the " +"documentation string from the inheritance hierarchy." +msgstr "" + +#: ../Doc/library/inspect.rst:416 +msgid "Documentation strings are now inherited if not overridden." +msgstr "" + +#: ../Doc/library/inspect.rst:422 +msgid "" +"Return in a single string any lines of comments immediately preceding the " +"object's source code (for a class, function, or method), or at the top of " +"the Python source file (if the object is a module)." +msgstr "" + +#: ../Doc/library/inspect.rst:429 +msgid "" +"Return the name of the (text or binary) file in which an object was defined. " +"This will fail with a :exc:`TypeError` if the object is a built-in module, " +"class, or function." +msgstr "" + +#: ../Doc/library/inspect.rst:436 +msgid "Try to guess which module an object was defined in." +msgstr "" + +#: ../Doc/library/inspect.rst:441 +msgid "" +"Return the name of the Python source file in which an object was defined. " +"This will fail with a :exc:`TypeError` if the object is a built-in module, " +"class, or function." +msgstr "" + +#: ../Doc/library/inspect.rst:448 +msgid "" +"Return a list of source lines and starting line number for an object. The " +"argument may be a module, class, method, function, traceback, frame, or code " +"object. The source code is returned as a list of the lines corresponding to " +"the object and the line number indicates where in the original source file " +"the first line of code was found. An :exc:`OSError` is raised if the source " +"code cannot be retrieved." +msgstr "" + +#: ../Doc/library/inspect.rst:455 ../Doc/library/inspect.rst:467 +msgid "" +":exc:`OSError` is raised instead of :exc:`IOError`, now an alias of the " +"former." +msgstr "" + +#: ../Doc/library/inspect.rst:462 +msgid "" +"Return the text of the source code for an object. The argument may be a " +"module, class, method, function, traceback, frame, or code object. The " +"source code is returned as a single string. An :exc:`OSError` is raised if " +"the source code cannot be retrieved." +msgstr "" + +#: ../Doc/library/inspect.rst:474 +msgid "" +"Clean up indentation from docstrings that are indented to line up with " +"blocks of code." +msgstr "" + +#: ../Doc/library/inspect.rst:477 +msgid "" +"All leading whitespace is removed from the first line. Any leading " +"whitespace that can be uniformly removed from the second line onwards is " +"removed. Empty lines at the beginning and end are subsequently removed. " +"Also, all tabs are expanded to spaces." +msgstr "" + +#: ../Doc/library/inspect.rst:486 +msgid "Introspecting callables with the Signature object" +msgstr "" + +#: ../Doc/library/inspect.rst:490 +msgid "" +"The Signature object represents the call signature of a callable object and " +"its return annotation. To retrieve a Signature object, use the :func:" +"`signature` function." +msgstr "" + +#: ../Doc/library/inspect.rst:496 +msgid "Return a :class:`Signature` object for the given ``callable``::" +msgstr "" + +#: ../Doc/library/inspect.rst:513 +msgid "" +"Accepts a wide range of python callables, from plain functions and classes " +"to :func:`functools.partial` objects." +msgstr "" + +#: ../Doc/library/inspect.rst:516 +msgid "" +"Raises :exc:`ValueError` if no signature can be provided, and :exc:" +"`TypeError` if that type of object is not supported." +msgstr "" + +#: ../Doc/library/inspect.rst:519 +msgid "" +"``follow_wrapped`` parameter. Pass ``False`` to get a signature of " +"``callable`` specifically (``callable.__wrapped__`` will not be used to " +"unwrap decorated callables.)" +msgstr "" + +#: ../Doc/library/inspect.rst:526 +msgid "" +"Some callables may not be introspectable in certain implementations of " +"Python. For example, in CPython, some built-in functions defined in C " +"provide no metadata about their arguments." +msgstr "" + +#: ../Doc/library/inspect.rst:533 +msgid "" +"A Signature object represents the call signature of a function and its " +"return annotation. For each parameter accepted by the function it stores a :" +"class:`Parameter` object in its :attr:`parameters` collection." +msgstr "" + +#: ../Doc/library/inspect.rst:537 +msgid "" +"The optional *parameters* argument is a sequence of :class:`Parameter` " +"objects, which is validated to check that there are no parameters with " +"duplicate names, and that the parameters are in the right order, i.e. " +"positional-only first, then positional-or-keyword, and that parameters with " +"defaults follow parameters without defaults." +msgstr "" + +#: ../Doc/library/inspect.rst:543 +msgid "" +"The optional *return_annotation* argument, can be an arbitrary Python " +"object, is the \"return\" annotation of the callable." +msgstr "" + +#: ../Doc/library/inspect.rst:546 +msgid "" +"Signature objects are *immutable*. Use :meth:`Signature.replace` to make a " +"modified copy." +msgstr "" + +#: ../Doc/library/inspect.rst:549 +msgid "Signature objects are picklable and hashable." +msgstr "" + +#: ../Doc/library/inspect.rst:554 +msgid "A special class-level marker to specify absence of a return annotation." +msgstr "" + +#: ../Doc/library/inspect.rst:558 +msgid "" +"An ordered mapping of parameters' names to the corresponding :class:" +"`Parameter` objects." +msgstr "" + +#: ../Doc/library/inspect.rst:563 +msgid "" +"The \"return\" annotation for the callable. If the callable has no \"return" +"\" annotation, this attribute is set to :attr:`Signature.empty`." +msgstr "" + +#: ../Doc/library/inspect.rst:568 +msgid "" +"Create a mapping from positional and keyword arguments to parameters. " +"Returns :class:`BoundArguments` if ``*args`` and ``**kwargs`` match the " +"signature, or raises a :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/inspect.rst:574 +msgid "" +"Works the same way as :meth:`Signature.bind`, but allows the omission of " +"some required arguments (mimics :func:`functools.partial` behavior.) " +"Returns :class:`BoundArguments`, or raises a :exc:`TypeError` if the passed " +"arguments do not match the signature." +msgstr "" + +#: ../Doc/library/inspect.rst:581 +msgid "" +"Create a new Signature instance based on the instance replace was invoked " +"on. It is possible to pass different ``parameters`` and/or " +"``return_annotation`` to override the corresponding properties of the base " +"signature. To remove return_annotation from the copied Signature, pass in :" +"attr:`Signature.empty`." +msgstr "" + +#: ../Doc/library/inspect.rst:598 +msgid "" +"Return a :class:`Signature` (or its subclass) object for a given callable " +"``obj``. Pass ``follow_wrapped=False`` to get a signature of ``obj`` " +"without unwrapping its ``__wrapped__`` chain." +msgstr "" + +#: ../Doc/library/inspect.rst:602 +msgid "This method simplifies subclassing of :class:`Signature`::" +msgstr "" + +#: ../Doc/library/inspect.rst:614 +msgid "" +"Parameter objects are *immutable*. Instead of modifying a Parameter object, " +"you can use :meth:`Parameter.replace` to create a modified copy." +msgstr "" + +#: ../Doc/library/inspect.rst:617 +msgid "Parameter objects are picklable and hashable." +msgstr "" + +#: ../Doc/library/inspect.rst:622 +msgid "" +"A special class-level marker to specify absence of default values and " +"annotations." +msgstr "" + +#: ../Doc/library/inspect.rst:627 +msgid "" +"The name of the parameter as a string. The name must be a valid Python " +"identifier." +msgstr "" + +#: ../Doc/library/inspect.rst:632 +msgid "" +"CPython generates implicit parameter names of the form ``.0`` on the code " +"objects used to implement comprehensions and generator expressions." +msgstr "" + +#: ../Doc/library/inspect.rst:636 +msgid "" +"These parameter names are exposed by this module as names like ``implicit0``." +msgstr "" + +#: ../Doc/library/inspect.rst:642 +msgid "" +"The default value for the parameter. If the parameter has no default value, " +"this attribute is set to :attr:`Parameter.empty`." +msgstr "" + +#: ../Doc/library/inspect.rst:647 +msgid "" +"The annotation for the parameter. If the parameter has no annotation, this " +"attribute is set to :attr:`Parameter.empty`." +msgstr "" + +#: ../Doc/library/inspect.rst:652 +msgid "" +"Describes how argument values are bound to the parameter. Possible values " +"(accessible via :class:`Parameter`, like ``Parameter.KEYWORD_ONLY``):" +msgstr "" + +#: ../Doc/library/inspect.rst:660 +msgid "*POSITIONAL_ONLY*" +msgstr "" + +#: ../Doc/library/inspect.rst:660 +msgid "Value must be supplied as a positional argument." +msgstr "" + +#: ../Doc/library/inspect.rst:663 +msgid "" +"Python has no explicit syntax for defining positional-only parameters, but " +"many built-in and extension module functions (especially those that accept " +"only one or two parameters) accept them." +msgstr "" + +#: ../Doc/library/inspect.rst:669 +msgid "*POSITIONAL_OR_KEYWORD*" +msgstr "" + +#: ../Doc/library/inspect.rst:669 +msgid "" +"Value may be supplied as either a keyword or positional argument (this is " +"the standard binding behaviour for functions implemented in Python.)" +msgstr "" + +#: ../Doc/library/inspect.rst:674 +msgid "*VAR_POSITIONAL*" +msgstr "" + +#: ../Doc/library/inspect.rst:674 +msgid "" +"A tuple of positional arguments that aren't bound to any other parameter. " +"This corresponds to a ``*args`` parameter in a Python function definition." +msgstr "" + +#: ../Doc/library/inspect.rst:679 +msgid "*KEYWORD_ONLY*" +msgstr "" + +#: ../Doc/library/inspect.rst:679 +msgid "" +"Value must be supplied as a keyword argument. Keyword only parameters are " +"those which appear after a ``*`` or ``*args`` entry in a Python function " +"definition." +msgstr "" + +#: ../Doc/library/inspect.rst:684 +msgid "*VAR_KEYWORD*" +msgstr "" + +#: ../Doc/library/inspect.rst:684 +msgid "" +"A dict of keyword arguments that aren't bound to any other parameter. This " +"corresponds to a ``**kwargs`` parameter in a Python function definition." +msgstr "" + +#: ../Doc/library/inspect.rst:690 +msgid "Example: print all keyword-only arguments without default values::" +msgstr "" + +#: ../Doc/library/inspect.rst:704 +msgid "" +"Create a new Parameter instance based on the instance replaced was invoked " +"on. To override a :class:`Parameter` attribute, pass the corresponding " +"argument. To remove a default value or/and an annotation from a Parameter, " +"pass :attr:`Parameter.empty`." +msgstr "" + +#: ../Doc/library/inspect.rst:722 +msgid "" +"In Python 3.3 Parameter objects were allowed to have ``name`` set to " +"``None`` if their ``kind`` was set to ``POSITIONAL_ONLY``. This is no longer " +"permitted." +msgstr "" + +#: ../Doc/library/inspect.rst:729 +msgid "" +"Result of a :meth:`Signature.bind` or :meth:`Signature.bind_partial` call. " +"Holds the mapping of arguments to the function's parameters." +msgstr "" + +#: ../Doc/library/inspect.rst:734 +msgid "" +"An ordered, mutable mapping (:class:`collections.OrderedDict`) of " +"parameters' names to arguments' values. Contains only explicitly bound " +"arguments. Changes in :attr:`arguments` will reflect in :attr:`args` and :" +"attr:`kwargs`." +msgstr "" + +#: ../Doc/library/inspect.rst:739 +msgid "" +"Should be used in conjunction with :attr:`Signature.parameters` for any " +"argument processing purposes." +msgstr "" + +#: ../Doc/library/inspect.rst:744 +msgid "" +"Arguments for which :meth:`Signature.bind` or :meth:`Signature.bind_partial` " +"relied on a default value are skipped. However, if needed, use :meth:" +"`BoundArguments.apply_defaults` to add them." +msgstr "" + +#: ../Doc/library/inspect.rst:751 +msgid "" +"A tuple of positional arguments values. Dynamically computed from the :attr:" +"`arguments` attribute." +msgstr "" + +#: ../Doc/library/inspect.rst:756 +msgid "" +"A dict of keyword arguments values. Dynamically computed from the :attr:" +"`arguments` attribute." +msgstr "" + +#: ../Doc/library/inspect.rst:761 +msgid "A reference to the parent :class:`Signature` object." +msgstr "" + +#: ../Doc/library/inspect.rst:765 +msgid "Set default values for missing arguments." +msgstr "" + +#: ../Doc/library/inspect.rst:767 +msgid "" +"For variable-positional arguments (``*args``) the default is an empty tuple." +msgstr "" + +#: ../Doc/library/inspect.rst:770 +msgid "" +"For variable-keyword arguments (``**kwargs``) the default is an empty dict." +msgstr "" + +#: ../Doc/library/inspect.rst:783 +msgid "" +"The :attr:`args` and :attr:`kwargs` properties can be used to invoke " +"functions::" +msgstr "" + +#: ../Doc/library/inspect.rst:796 +msgid ":pep:`362` - Function Signature Object." +msgstr "" + +#: ../Doc/library/inspect.rst:797 +msgid "The detailed specification, implementation details and examples." +msgstr "" + +#: ../Doc/library/inspect.rst:803 ../Doc/library/unittest.rst:639 +msgid "Classes and functions" +msgstr "" + +#: ../Doc/library/inspect.rst:807 +msgid "" +"Arrange the given list of classes into a hierarchy of nested lists. Where a " +"nested list appears, it contains classes derived from the class whose entry " +"immediately precedes the list. Each entry is a 2-tuple containing a class " +"and a tuple of its base classes. If the *unique* argument is true, exactly " +"one entry appears in the returned structure for each class in the given " +"list. Otherwise, classes using multiple inheritance and their descendants " +"will appear multiple times." +msgstr "" + +#: ../Doc/library/inspect.rst:818 +msgid "" +"Get the names and default values of a Python function's arguments. A :term:" +"`named tuple` ``ArgSpec(args, varargs, keywords, defaults)`` is returned. " +"*args* is a list of the argument names. *varargs* and *keywords* are the " +"names of the ``*`` and ``**`` arguments or ``None``. *defaults* is a tuple " +"of default argument values or ``None`` if there are no default arguments; if " +"this tuple has *n* elements, they correspond to the last *n* elements listed " +"in *args*." +msgstr "" + +#: ../Doc/library/inspect.rst:826 ../Doc/library/inspect.rst:853 +#: ../Doc/library/inspect.rst:867 ../Doc/library/inspect.rst:894 +#: ../Doc/library/inspect.rst:906 +msgid "" +"Use :func:`signature` and :ref:`Signature Object `, which provide a better introspecting API for callables." +msgstr "" + +#: ../Doc/library/inspect.rst:834 +msgid "" +"Get the names and default values of a Python function's arguments. A :term:" +"`named tuple` is returned:" +msgstr "" + +#: ../Doc/library/inspect.rst:837 +msgid "" +"``FullArgSpec(args, varargs, varkw, defaults, kwonlyargs, kwonlydefaults, " +"annotations)``" +msgstr "" + +#: ../Doc/library/inspect.rst:840 +msgid "" +"*args* is a list of the argument names. *varargs* and *varkw* are the names " +"of the ``*`` and ``**`` arguments or ``None``. *defaults* is an *n*-tuple " +"of the default values of the last *n* arguments, or ``None`` if there are no " +"default arguments. *kwonlyargs* is a list of keyword-only argument names. " +"*kwonlydefaults* is a dictionary mapping names from kwonlyargs to defaults. " +"*annotations* is a dictionary mapping argument names to annotations." +msgstr "" + +#: ../Doc/library/inspect.rst:848 +msgid "" +"This function is now based on :func:`signature`, but still ignores " +"``__wrapped__`` attributes and includes the already bound first parameter in " +"the signature output for bound methods." +msgstr "" + +#: ../Doc/library/inspect.rst:861 +msgid "" +"Get information about arguments passed into a particular frame. A :term:" +"`named tuple` ``ArgInfo(args, varargs, keywords, locals)`` is returned. " +"*args* is a list of the argument names. *varargs* and *keywords* are the " +"names of the ``*`` and ``**`` arguments or ``None``. *locals* is the locals " +"dictionary of the given frame." +msgstr "" + +#: ../Doc/library/inspect.rst:875 +msgid "" +"Format a pretty argument spec from the values returned by :func:" +"`getfullargspec`." +msgstr "" + +#: ../Doc/library/inspect.rst:878 +msgid "" +"The first seven arguments are (``args``, ``varargs``, ``varkw``, " +"``defaults``, ``kwonlyargs``, ``kwonlydefaults``, ``annotations``)." +msgstr "" + +#: ../Doc/library/inspect.rst:881 +msgid "" +"The other six arguments are functions that are called to turn argument " +"names, ``*`` argument name, ``**`` argument name, default values, return " +"annotation and individual annotations into strings, respectively." +msgstr "" + +#: ../Doc/library/inspect.rst:902 +msgid "" +"Format a pretty argument spec from the four values returned by :func:" +"`getargvalues`. The format\\* arguments are the corresponding optional " +"formatting functions that are called to turn names and values into strings." +msgstr "" + +#: ../Doc/library/inspect.rst:914 +msgid "" +"Return a tuple of class cls's base classes, including cls, in method " +"resolution order. No class appears more than once in this tuple. Note that " +"the method resolution order depends on cls's type. Unless a very peculiar " +"user-defined metatype is in use, cls will be the first element of the tuple." +msgstr "" + +#: ../Doc/library/inspect.rst:922 +msgid "" +"Bind the *args* and *kwds* to the argument names of the Python function or " +"method *func*, as if it was called with them. For bound methods, bind also " +"the first argument (typically named ``self``) to the associated instance. A " +"dict is returned, mapping the argument names (including the names of the " +"``*`` and ``**`` arguments, if any) to their values from *args* and *kwds*. " +"In case of invoking *func* incorrectly, i.e. whenever ``func(*args, " +"**kwds)`` would raise an exception because of incompatible signature, an " +"exception of the same type and the same or similar message is raised. For " +"example::" +msgstr "" + +#: ../Doc/library/inspect.rst:945 +msgid "Use :meth:`Signature.bind` and :meth:`Signature.bind_partial` instead." +msgstr "" + +#: ../Doc/library/inspect.rst:951 +msgid "" +"Get the mapping of external name references in a Python function or method " +"*func* to their current values. A :term:`named tuple` " +"``ClosureVars(nonlocals, globals, builtins, unbound)`` is returned. " +"*nonlocals* maps referenced names to lexical closure variables, *globals* to " +"the function's module globals and *builtins* to the builtins visible from " +"the function body. *unbound* is the set of names referenced in the function " +"that could not be resolved at all given the current module globals and " +"builtins." +msgstr "" + +#: ../Doc/library/inspect.rst:960 +msgid "" +":exc:`TypeError` is raised if *func* is not a Python function or method." +msgstr "" + +#: ../Doc/library/inspect.rst:967 +msgid "" +"Get the object wrapped by *func*. It follows the chain of :attr:" +"`__wrapped__` attributes returning the last object in the chain." +msgstr "" + +#: ../Doc/library/inspect.rst:970 +msgid "" +"*stop* is an optional callback accepting an object in the wrapper chain as " +"its sole argument that allows the unwrapping to be terminated early if the " +"callback returns a true value. If the callback never returns a true value, " +"the last object in the chain is returned as usual. For example, :func:" +"`signature` uses this to stop unwrapping if any object in the chain has a " +"``__signature__`` attribute defined." +msgstr "" + +#: ../Doc/library/inspect.rst:977 +msgid ":exc:`ValueError` is raised if a cycle is encountered." +msgstr "" + +#: ../Doc/library/inspect.rst:985 +msgid "The interpreter stack" +msgstr "" + +#: ../Doc/library/inspect.rst:987 +msgid "" +"When the following functions return \"frame records,\" each record is a :" +"term:`named tuple` ``FrameInfo(frame, filename, lineno, function, " +"code_context, index)``. The tuple contains the frame object, the filename, " +"the line number of the current line, the function name, a list of lines of " +"context from the source code, and the index of the current line within that " +"list." +msgstr "" + +#: ../Doc/library/inspect.rst:995 +msgid "Return a named tuple instead of a tuple." +msgstr "" + +#: ../Doc/library/inspect.rst:1000 +msgid "" +"Keeping references to frame objects, as found in the first element of the " +"frame records these functions return, can cause your program to create " +"reference cycles. Once a reference cycle has been created, the lifespan of " +"all objects which can be accessed from the objects which form the cycle can " +"become much longer even if Python's optional cycle detector is enabled. If " +"such cycles must be created, it is important to ensure they are explicitly " +"broken to avoid the delayed destruction of objects and increased memory " +"consumption which occurs." +msgstr "" + +#: ../Doc/library/inspect.rst:1008 +msgid "" +"Though the cycle detector will catch these, destruction of the frames (and " +"local variables) can be made deterministic by removing the cycle in a :" +"keyword:`finally` clause. This is also important if the cycle detector was " +"disabled when Python was compiled or using :func:`gc.disable`. For example::" +msgstr "" + +#: ../Doc/library/inspect.rst:1020 +msgid "" +"If you want to keep the frame around (for example to print a traceback " +"later), you can also break reference cycles by using the :meth:`frame.clear` " +"method." +msgstr "" + +#: ../Doc/library/inspect.rst:1024 +msgid "" +"The optional *context* argument supported by most of these functions " +"specifies the number of lines of context to return, which are centered " +"around the current line." +msgstr "" + +#: ../Doc/library/inspect.rst:1031 +msgid "" +"Get information about a frame or traceback object. A :term:`named tuple` " +"``Traceback(filename, lineno, function, code_context, index)`` is returned." +msgstr "" + +#: ../Doc/library/inspect.rst:1037 +msgid "" +"Get a list of frame records for a frame and all outer frames. These frames " +"represent the calls that lead to the creation of *frame*. The first entry in " +"the returned list represents *frame*; the last entry represents the " +"outermost call on *frame*'s stack." +msgstr "" + +#: ../Doc/library/inspect.rst:1042 ../Doc/library/inspect.rst:1055 +#: ../Doc/library/inspect.rst:1079 ../Doc/library/inspect.rst:1092 +msgid "" +"A list of :term:`named tuples ` ``FrameInfo(frame, filename, " +"lineno, function, code_context, index)`` is returned." +msgstr "" + +#: ../Doc/library/inspect.rst:1050 +msgid "" +"Get a list of frame records for a traceback's frame and all inner frames. " +"These frames represent calls made as a consequence of *frame*. The first " +"entry in the list represents *traceback*; the last entry represents where " +"the exception was raised." +msgstr "" + +#: ../Doc/library/inspect.rst:1063 +msgid "Return the frame object for the caller's stack frame." +msgstr "" + +#: ../Doc/library/inspect.rst:1067 +msgid "" +"This function relies on Python stack frame support in the interpreter, which " +"isn't guaranteed to exist in all implementations of Python. If running in " +"an implementation without Python stack frame support this function returns " +"``None``." +msgstr "" + +#: ../Doc/library/inspect.rst:1075 +msgid "" +"Return a list of frame records for the caller's stack. The first entry in " +"the returned list represents the caller; the last entry represents the " +"outermost call on the stack." +msgstr "" + +#: ../Doc/library/inspect.rst:1087 +msgid "" +"Return a list of frame records for the stack between the current frame and " +"the frame in which an exception currently being handled was raised in. The " +"first entry in the list represents the caller; the last entry represents " +"where the exception was raised." +msgstr "" + +#: ../Doc/library/inspect.rst:1099 +msgid "Fetching attributes statically" +msgstr "" + +#: ../Doc/library/inspect.rst:1101 +msgid "" +"Both :func:`getattr` and :func:`hasattr` can trigger code execution when " +"fetching or checking for the existence of attributes. Descriptors, like " +"properties, will be invoked and :meth:`__getattr__` and :meth:" +"`__getattribute__` may be called." +msgstr "" + +#: ../Doc/library/inspect.rst:1106 +msgid "" +"For cases where you want passive introspection, like documentation tools, " +"this can be inconvenient. :func:`getattr_static` has the same signature as :" +"func:`getattr` but avoids executing code when it fetches attributes." +msgstr "" + +#: ../Doc/library/inspect.rst:1112 +msgid "" +"Retrieve attributes without triggering dynamic lookup via the descriptor " +"protocol, :meth:`__getattr__` or :meth:`__getattribute__`." +msgstr "" + +#: ../Doc/library/inspect.rst:1115 +msgid "" +"Note: this function may not be able to retrieve all attributes that getattr " +"can fetch (like dynamically created attributes) and may find attributes that " +"getattr can't (like descriptors that raise AttributeError). It can also " +"return descriptors objects instead of instance members." +msgstr "" + +#: ../Doc/library/inspect.rst:1121 +msgid "" +"If the instance :attr:`~object.__dict__` is shadowed by another member (for " +"example a property) then this function will be unable to find instance " +"members." +msgstr "" + +#: ../Doc/library/inspect.rst:1127 +msgid "" +":func:`getattr_static` does not resolve descriptors, for example slot " +"descriptors or getset descriptors on objects implemented in C. The " +"descriptor object is returned instead of the underlying attribute." +msgstr "" + +#: ../Doc/library/inspect.rst:1131 +msgid "" +"You can handle these with code like the following. Note that for arbitrary " +"getset descriptors invoking these may trigger code execution::" +msgstr "" + +#: ../Doc/library/inspect.rst:1157 +msgid "Current State of Generators and Coroutines" +msgstr "" + +#: ../Doc/library/inspect.rst:1159 +msgid "" +"When implementing coroutine schedulers and for other advanced uses of " +"generators, it is useful to determine whether a generator is currently " +"executing, is waiting to start or resume or execution, or has already " +"terminated. :func:`getgeneratorstate` allows the current state of a " +"generator to be determined easily." +msgstr "" + +#: ../Doc/library/inspect.rst:1167 +msgid "Get current state of a generator-iterator." +msgstr "" + +#: ../Doc/library/inspect.rst:1173 ../Doc/library/inspect.rst:1188 +msgid "Possible states are:" +msgstr "" + +#: ../Doc/library/inspect.rst:1170 +msgid "GEN_CREATED: Waiting to start execution." +msgstr "" + +#: ../Doc/library/inspect.rst:1171 +msgid "GEN_RUNNING: Currently being executed by the interpreter." +msgstr "" + +#: ../Doc/library/inspect.rst:1172 +msgid "GEN_SUSPENDED: Currently suspended at a yield expression." +msgstr "" + +#: ../Doc/library/inspect.rst:1173 +msgid "GEN_CLOSED: Execution has completed." +msgstr "" + +#: ../Doc/library/inspect.rst:1179 +msgid "" +"Get current state of a coroutine object. The function is intended to be " +"used with coroutine objects created by :keyword:`async def` functions, but " +"will accept any coroutine-like object that has ``cr_running`` and " +"``cr_frame`` attributes." +msgstr "" + +#: ../Doc/library/inspect.rst:1185 +msgid "CORO_CREATED: Waiting to start execution." +msgstr "" + +#: ../Doc/library/inspect.rst:1186 +msgid "CORO_RUNNING: Currently being executed by the interpreter." +msgstr "" + +#: ../Doc/library/inspect.rst:1187 +msgid "CORO_SUSPENDED: Currently suspended at an await expression." +msgstr "" + +#: ../Doc/library/inspect.rst:1188 +msgid "CORO_CLOSED: Execution has completed." +msgstr "" + +#: ../Doc/library/inspect.rst:1192 +msgid "" +"The current internal state of the generator can also be queried. This is " +"mostly useful for testing purposes, to ensure that internal state is being " +"updated as expected:" +msgstr "" + +#: ../Doc/library/inspect.rst:1198 +msgid "" +"Get the mapping of live local variables in *generator* to their current " +"values. A dictionary is returned that maps from variable names to values. " +"This is the equivalent of calling :func:`locals` in the body of the " +"generator, and all the same caveats apply." +msgstr "" + +#: ../Doc/library/inspect.rst:1203 +msgid "" +"If *generator* is a :term:`generator` with no currently associated frame, " +"then an empty dictionary is returned. :exc:`TypeError` is raised if " +"*generator* is not a Python generator object." +msgstr "" + +#: ../Doc/library/inspect.rst:1209 +msgid "" +"This function relies on the generator exposing a Python stack frame for " +"introspection, which isn't guaranteed to be the case in all implementations " +"of Python. In such cases, this function will always return an empty " +"dictionary." +msgstr "" + +#: ../Doc/library/inspect.rst:1218 +msgid "" +"This function is analogous to :func:`~inspect.getgeneratorlocals`, but works " +"for coroutine objects created by :keyword:`async def` functions." +msgstr "" + +#: ../Doc/library/inspect.rst:1227 ../Doc/library/json.rst:653 +#: ../Doc/library/tarfile.rst:649 +msgid "Command Line Interface" +msgstr "" + +#: ../Doc/library/inspect.rst:1229 +msgid "" +"The :mod:`inspect` module also provides a basic introspection capability " +"from the command line." +msgstr "" + +#: ../Doc/library/inspect.rst:1234 +msgid "" +"By default, accepts the name of a module and prints the source of that " +"module. A class or function within the module can be printed instead by " +"appended a colon and the qualified name of the target object." +msgstr "" + +#: ../Doc/library/inspect.rst:1240 +msgid "" +"Print information about the specified object rather than the source code" +msgstr "" + +#: ../Doc/library/internet.rst:5 +msgid "Internet Protocols and Support" +msgstr "" + +#: ../Doc/library/internet.rst:14 +msgid "" +"The modules described in this chapter implement Internet protocols and " +"support for related technology. They are all implemented in Python. Most of " +"these modules require the presence of the system-dependent module :mod:" +"`socket`, which is currently supported on most popular platforms. Here is " +"an overview:" +msgstr "" + +#: ../Doc/library/intro.rst:7 +msgid "The \"Python library\" contains several different kinds of components." +msgstr "" + +#: ../Doc/library/intro.rst:9 +msgid "" +"It contains data types that would normally be considered part of the \"core" +"\" of a language, such as numbers and lists. For these types, the Python " +"language core defines the form of literals and places some constraints on " +"their semantics, but does not fully define the semantics. (On the other " +"hand, the language core does define syntactic properties like the spelling " +"and priorities of operators.)" +msgstr "" + +#: ../Doc/library/intro.rst:15 +msgid "" +"The library also contains built-in functions and exceptions --- objects that " +"can be used by all Python code without the need of an :keyword:`import` " +"statement. Some of these are defined by the core language, but many are not " +"essential for the core semantics and are only described here." +msgstr "" + +#: ../Doc/library/intro.rst:20 +msgid "" +"The bulk of the library, however, consists of a collection of modules. There " +"are many ways to dissect this collection. Some modules are written in C and " +"built in to the Python interpreter; others are written in Python and " +"imported in source form. Some modules provide interfaces that are highly " +"specific to Python, like printing a stack trace; some provide interfaces " +"that are specific to particular operating systems, such as access to " +"specific hardware; others provide interfaces that are specific to a " +"particular application domain, like the World Wide Web. Some modules are " +"available in all versions and ports of Python; others are only available " +"when the underlying system supports or requires them; yet others are " +"available only when a particular configuration option was chosen at the time " +"when Python was compiled and installed." +msgstr "" + +#: ../Doc/library/intro.rst:32 +msgid "" +"This manual is organized \"from the inside out:\" it first describes the " +"built-in functions, data types and exceptions, and finally the modules, " +"grouped in chapters of related modules." +msgstr "" + +#: ../Doc/library/intro.rst:36 +msgid "" +"This means that if you start reading this manual from the start, and skip to " +"the next chapter when you get bored, you will get a reasonable overview of " +"the available modules and application areas that are supported by the Python " +"library. Of course, you don't *have* to read it like a novel --- you can " +"also browse the table of contents (in front of the manual), or look for a " +"specific function, module or term in the index (in the back). And finally, " +"if you enjoy learning about random subjects, you choose a random page number " +"(see module :mod:`random`) and read a section or two. Regardless of the " +"order in which you read the sections of this manual, it helps to start with " +"chapter :ref:`built-in-funcs`, as the remainder of the manual assumes " +"familiarity with this material." +msgstr "" + +#: ../Doc/library/intro.rst:48 +msgid "Let the show begin!" +msgstr "" + +#: ../Doc/library/io.rst:2 +msgid ":mod:`io` --- Core tools for working with streams" +msgstr "" + +#: ../Doc/library/io.rst:15 +msgid "**Source code:** :source:`Lib/io.py`" +msgstr "" + +#: ../Doc/library/io.rst:22 +msgid "Overview" +msgstr "" + +#: ../Doc/library/io.rst:27 +msgid "" +"The :mod:`io` module provides Python's main facilities for dealing with " +"various types of I/O. There are three main types of I/O: *text I/O*, " +"*binary I/O* and *raw I/O*. These are generic categories, and various " +"backing stores can be used for each of them. A concrete object belonging to " +"any of these categories is called a :term:`file object`. Other common terms " +"are *stream* and *file-like object*." +msgstr "" + +#: ../Doc/library/io.rst:34 +msgid "" +"Independently of its category, each concrete stream object will also have " +"various capabilities: it can be read-only, write-only, or read-write. It can " +"also allow arbitrary random access (seeking forwards or backwards to any " +"location), or only sequential access (for example in the case of a socket or " +"pipe)." +msgstr "" + +#: ../Doc/library/io.rst:40 +msgid "" +"All streams are careful about the type of data you give to them. For " +"example giving a :class:`str` object to the ``write()`` method of a binary " +"stream will raise a ``TypeError``. So will giving a :class:`bytes` object " +"to the ``write()`` method of a text stream." +msgstr "" + +#: ../Doc/library/io.rst:45 +msgid "" +"Operations that used to raise :exc:`IOError` now raise :exc:`OSError`, " +"since :exc:`IOError` is now an alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/io.rst:51 ../Doc/library/io.rst:743 ../Doc/library/io.rst:973 +msgid "Text I/O" +msgstr "" + +#: ../Doc/library/io.rst:53 +msgid "" +"Text I/O expects and produces :class:`str` objects. This means that " +"whenever the backing store is natively made of bytes (such as in the case of " +"a file), encoding and decoding of data is made transparently as well as " +"optional translation of platform-specific newline characters." +msgstr "" + +#: ../Doc/library/io.rst:58 +msgid "" +"The easiest way to create a text stream is with :meth:`open()`, optionally " +"specifying an encoding::" +msgstr "" + +#: ../Doc/library/io.rst:63 +msgid "" +"In-memory text streams are also available as :class:`StringIO` objects::" +msgstr "" + +#: ../Doc/library/io.rst:67 +msgid "" +"The text stream API is described in detail in the documentation of :class:" +"`TextIOBase`." +msgstr "" + +#: ../Doc/library/io.rst:72 ../Doc/library/io.rst:961 +msgid "Binary I/O" +msgstr "" + +#: ../Doc/library/io.rst:74 +msgid "" +"Binary I/O (also called *buffered I/O*) expects :term:`bytes-like objects " +"` and produces :class:`bytes` objects. No encoding, " +"decoding, or newline translation is performed. This category of streams can " +"be used for all kinds of non-text data, and also when manual control over " +"the handling of text data is desired." +msgstr "" + +#: ../Doc/library/io.rst:80 +msgid "" +"The easiest way to create a binary stream is with :meth:`open()` with " +"``'b'`` in the mode string::" +msgstr "" + +#: ../Doc/library/io.rst:85 +msgid "" +"In-memory binary streams are also available as :class:`BytesIO` objects::" +msgstr "" + +#: ../Doc/library/io.rst:89 +msgid "" +"The binary stream API is described in detail in the docs of :class:" +"`BufferedIOBase`." +msgstr "" + +#: ../Doc/library/io.rst:92 +msgid "" +"Other library modules may provide additional ways to create text or binary " +"streams. See :meth:`socket.socket.makefile` for example." +msgstr "" + +#: ../Doc/library/io.rst:97 +msgid "Raw I/O" +msgstr "" + +#: ../Doc/library/io.rst:99 +msgid "" +"Raw I/O (also called *unbuffered I/O*) is generally used as a low-level " +"building-block for binary and text streams; it is rarely useful to directly " +"manipulate a raw stream from user code. Nevertheless, you can create a raw " +"stream by opening a file in binary mode with buffering disabled::" +msgstr "" + +#: ../Doc/library/io.rst:106 +msgid "" +"The raw stream API is described in detail in the docs of :class:`RawIOBase`." +msgstr "" + +#: ../Doc/library/io.rst:110 +msgid "High-level Module Interface" +msgstr "" + +#: ../Doc/library/io.rst:114 +msgid "" +"An int containing the default buffer size used by the module's buffered I/O " +"classes. :func:`open` uses the file's blksize (as obtained by :func:`os." +"stat`) if possible." +msgstr "" + +#: ../Doc/library/io.rst:121 +msgid "This is an alias for the builtin :func:`open` function." +msgstr "" + +#: ../Doc/library/io.rst:126 +msgid "" +"This is a compatibility alias for the builtin :exc:`BlockingIOError` " +"exception." +msgstr "" + +#: ../Doc/library/io.rst:132 +msgid "" +"An exception inheriting :exc:`OSError` and :exc:`ValueError` that is raised " +"when an unsupported operation is called on a stream." +msgstr "" + +#: ../Doc/library/io.rst:137 +msgid "In-memory streams" +msgstr "" + +#: ../Doc/library/io.rst:139 +msgid "" +"It is also possible to use a :class:`str` or :term:`bytes-like object` as a " +"file for both reading and writing. For strings :class:`StringIO` can be " +"used like a file opened in text mode. :class:`BytesIO` can be used like a " +"file opened in binary mode. Both provide full read-write capabilities with " +"random access." +msgstr "" + +#: ../Doc/library/io.rst:149 +msgid ":mod:`sys`" +msgstr "" + +#: ../Doc/library/io.rst:149 +msgid "" +"contains the standard IO streams: :data:`sys.stdin`, :data:`sys.stdout`, " +"and :data:`sys.stderr`." +msgstr "" + +#: ../Doc/library/io.rst:154 +msgid "Class hierarchy" +msgstr "" + +#: ../Doc/library/io.rst:156 +msgid "" +"The implementation of I/O streams is organized as a hierarchy of classes. " +"First :term:`abstract base classes ` (ABCs), which are " +"used to specify the various categories of streams, then concrete classes " +"providing the standard stream implementations." +msgstr "" + +#: ../Doc/library/io.rst:163 +msgid "" +"The abstract base classes also provide default implementations of some " +"methods in order to help implementation of concrete stream classes. For " +"example, :class:`BufferedIOBase` provides unoptimized implementations of :" +"meth:`~IOBase.readinto` and :meth:`~IOBase.readline`." +msgstr "" + +#: ../Doc/library/io.rst:168 +msgid "" +"At the top of the I/O hierarchy is the abstract base class :class:`IOBase`. " +"It defines the basic interface to a stream. Note, however, that there is no " +"separation between reading and writing to streams; implementations are " +"allowed to raise :exc:`UnsupportedOperation` if they do not support a given " +"operation." +msgstr "" + +#: ../Doc/library/io.rst:173 +msgid "" +"The :class:`RawIOBase` ABC extends :class:`IOBase`. It deals with the " +"reading and writing of bytes to a stream. :class:`FileIO` subclasses :class:" +"`RawIOBase` to provide an interface to files in the machine's file system." +msgstr "" + +#: ../Doc/library/io.rst:177 +msgid "" +"The :class:`BufferedIOBase` ABC deals with buffering on a raw byte stream (:" +"class:`RawIOBase`). Its subclasses, :class:`BufferedWriter`, :class:" +"`BufferedReader`, and :class:`BufferedRWPair` buffer streams that are " +"readable, writable, and both readable and writable. :class:`BufferedRandom` " +"provides a buffered interface to random access streams. Another :class:" +"`BufferedIOBase` subclass, :class:`BytesIO`, is a stream of in-memory bytes." +msgstr "" + +#: ../Doc/library/io.rst:185 +msgid "" +"The :class:`TextIOBase` ABC, another subclass of :class:`IOBase`, deals with " +"streams whose bytes represent text, and handles encoding and decoding to and " +"from strings. :class:`TextIOWrapper`, which extends it, is a buffered text " +"interface to a buffered raw stream (:class:`BufferedIOBase`). Finally, :" +"class:`StringIO` is an in-memory stream for text." +msgstr "" + +#: ../Doc/library/io.rst:191 +msgid "" +"Argument names are not part of the specification, and only the arguments of :" +"func:`open` are intended to be used as keyword arguments." +msgstr "" + +#: ../Doc/library/io.rst:194 +msgid "" +"The following table summarizes the ABCs provided by the :mod:`io` module:" +msgstr "" + +#: ../Doc/library/io.rst:199 +msgid "Inherits" +msgstr "" + +#: ../Doc/library/io.rst:199 +msgid "Stub Methods" +msgstr "" + +#: ../Doc/library/io.rst:199 +msgid "Mixin Methods and Properties" +msgstr "" + +#: ../Doc/library/io.rst:201 ../Doc/library/io.rst:206 +#: ../Doc/library/io.rst:208 ../Doc/library/io.rst:210 +msgid ":class:`IOBase`" +msgstr "" + +#: ../Doc/library/io.rst:201 +msgid "``fileno``, ``seek``, and ``truncate``" +msgstr "" + +#: ../Doc/library/io.rst:201 +msgid "" +"``close``, ``closed``, ``__enter__``, ``__exit__``, ``flush``, ``isatty``, " +"``__iter__``, ``__next__``, ``readable``, ``readline``, ``readlines``, " +"``seekable``, ``tell``, ``writable``, and ``writelines``" +msgstr "" + +#: ../Doc/library/io.rst:206 +msgid ":class:`RawIOBase`" +msgstr "" + +#: ../Doc/library/io.rst:206 +msgid "``readinto`` and ``write``" +msgstr "" + +#: ../Doc/library/io.rst:206 +msgid "Inherited :class:`IOBase` methods, ``read``, and ``readall``" +msgstr "" + +#: ../Doc/library/io.rst:208 +msgid ":class:`BufferedIOBase`" +msgstr "" + +#: ../Doc/library/io.rst:208 +msgid "``detach``, ``read``, ``read1``, and ``write``" +msgstr "" + +#: ../Doc/library/io.rst:208 +msgid "Inherited :class:`IOBase` methods, ``readinto``" +msgstr "" + +#: ../Doc/library/io.rst:210 +msgid ":class:`TextIOBase`" +msgstr "" + +#: ../Doc/library/io.rst:210 +msgid "``detach``, ``read``, ``readline``, and ``write``" +msgstr "" + +#: ../Doc/library/io.rst:210 +msgid "" +"Inherited :class:`IOBase` methods, ``encoding``, ``errors``, and ``newlines``" +msgstr "" + +#: ../Doc/library/io.rst:217 +msgid "I/O Base Classes" +msgstr "" + +#: ../Doc/library/io.rst:221 +msgid "" +"The abstract base class for all I/O classes, acting on streams of bytes. " +"There is no public constructor." +msgstr "" + +#: ../Doc/library/io.rst:224 +msgid "" +"This class provides empty abstract implementations for many methods that " +"derived classes can override selectively; the default implementations " +"represent a file that cannot be read, written or seeked." +msgstr "" + +#: ../Doc/library/io.rst:229 +msgid "" +"Even though :class:`IOBase` does not declare :meth:`read`, :meth:`readinto`, " +"or :meth:`write` because their signatures will vary, implementations and " +"clients should consider those methods part of the interface. Also, " +"implementations may raise a :exc:`ValueError` (or :exc:" +"`UnsupportedOperation`) when operations they do not support are called." +msgstr "" + +#: ../Doc/library/io.rst:235 +msgid "" +"The basic type used for binary data read from or written to a file is :class:" +"`bytes`. Other :term:`bytes-like objects ` are accepted " +"as method arguments too. In some cases, such as :meth:`~RawIOBase." +"readinto`, a writable object such as :class:`bytearray` is required. Text I/" +"O classes work with :class:`str` data." +msgstr "" + +#: ../Doc/library/io.rst:241 +msgid "" +"Note that calling any method (even inquiries) on a closed stream is " +"undefined. Implementations may raise :exc:`ValueError` in this case." +msgstr "" + +#: ../Doc/library/io.rst:244 +msgid "" +":class:`IOBase` (and its subclasses) supports the iterator protocol, meaning " +"that an :class:`IOBase` object can be iterated over yielding the lines in a " +"stream. Lines are defined slightly differently depending on whether the " +"stream is a binary stream (yielding bytes), or a text stream (yielding " +"character strings). See :meth:`~IOBase.readline` below." +msgstr "" + +#: ../Doc/library/io.rst:250 +msgid "" +":class:`IOBase` is also a context manager and therefore supports the :" +"keyword:`with` statement. In this example, *file* is closed after the :" +"keyword:`with` statement's suite is finished---even if an exception occurs::" +msgstr "" + +#: ../Doc/library/io.rst:257 +msgid ":class:`IOBase` provides these data attributes and methods:" +msgstr "" + +#: ../Doc/library/io.rst:261 +msgid "" +"Flush and close this stream. This method has no effect if the file is " +"already closed. Once the file is closed, any operation on the file (e.g. " +"reading or writing) will raise a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/io.rst:265 +msgid "" +"As a convenience, it is allowed to call this method more than once; only the " +"first call, however, will have an effect." +msgstr "" + +#: ../Doc/library/io.rst:270 +msgid "``True`` if the stream is closed." +msgstr "" + +#: ../Doc/library/io.rst:274 +msgid "" +"Return the underlying file descriptor (an integer) of the stream if it " +"exists. An :exc:`OSError` is raised if the IO object does not use a file " +"descriptor." +msgstr "" + +#: ../Doc/library/io.rst:280 +msgid "" +"Flush the write buffers of the stream if applicable. This does nothing for " +"read-only and non-blocking streams." +msgstr "" + +#: ../Doc/library/io.rst:285 +msgid "" +"Return ``True`` if the stream is interactive (i.e., connected to a terminal/" +"tty device)." +msgstr "" + +#: ../Doc/library/io.rst:290 +msgid "" +"Return ``True`` if the stream can be read from. If ``False``, :meth:`read` " +"will raise :exc:`OSError`." +msgstr "" + +#: ../Doc/library/io.rst:295 +msgid "" +"Read and return one line from the stream. If *size* is specified, at most " +"*size* bytes will be read." +msgstr "" + +#: ../Doc/library/io.rst:298 +msgid "" +"The line terminator is always ``b'\\n'`` for binary files; for text files, " +"the *newline* argument to :func:`open` can be used to select the line " +"terminator(s) recognized." +msgstr "" + +#: ../Doc/library/io.rst:304 +msgid "" +"Read and return a list of lines from the stream. *hint* can be specified to " +"control the number of lines read: no more lines will be read if the total " +"size (in bytes/characters) of all lines so far exceeds *hint*." +msgstr "" + +#: ../Doc/library/io.rst:308 +msgid "" +"Note that it's already possible to iterate on file objects using ``for line " +"in file: ...`` without calling ``file.readlines()``." +msgstr "" + +#: ../Doc/library/io.rst:313 +msgid "" +"Change the stream position to the given byte *offset*. *offset* is " +"interpreted relative to the position indicated by *whence*. The default " +"value for *whence* is :data:`SEEK_SET`. Values for *whence* are:" +msgstr "" + +#: ../Doc/library/io.rst:317 +msgid "" +":data:`SEEK_SET` or ``0`` -- start of the stream (the default); *offset* " +"should be zero or positive" +msgstr "" + +#: ../Doc/library/io.rst:319 +msgid "" +":data:`SEEK_CUR` or ``1`` -- current stream position; *offset* may be " +"negative" +msgstr "" + +#: ../Doc/library/io.rst:321 +msgid "" +":data:`SEEK_END` or ``2`` -- end of the stream; *offset* is usually negative" +msgstr "" + +#: ../Doc/library/io.rst:324 +msgid "Return the new absolute position." +msgstr "" + +#: ../Doc/library/io.rst:326 ../Doc/library/io.rst:820 +msgid "The ``SEEK_*`` constants." +msgstr "" + +#: ../Doc/library/io.rst:329 +msgid "" +"Some operating systems could support additional values, like :data:`os." +"SEEK_HOLE` or :data:`os.SEEK_DATA`. The valid values for a file could depend " +"on it being open in text or binary mode." +msgstr "" + +#: ../Doc/library/io.rst:336 +msgid "" +"Return ``True`` if the stream supports random access. If ``False``, :meth:" +"`seek`, :meth:`tell` and :meth:`truncate` will raise :exc:`OSError`." +msgstr "" + +#: ../Doc/library/io.rst:341 +msgid "Return the current stream position." +msgstr "" + +#: ../Doc/library/io.rst:345 +msgid "" +"Resize the stream to the given *size* in bytes (or the current position if " +"*size* is not specified). The current stream position isn't changed. This " +"resizing can extend or reduce the current file size. In case of extension, " +"the contents of the new file area depend on the platform (on most systems, " +"additional bytes are zero-filled). The new file size is returned." +msgstr "" + +#: ../Doc/library/io.rst:352 +msgid "Windows will now zero-fill files when extending." +msgstr "" + +#: ../Doc/library/io.rst:357 +msgid "" +"Return ``True`` if the stream supports writing. If ``False``, :meth:`write` " +"and :meth:`truncate` will raise :exc:`OSError`." +msgstr "" + +#: ../Doc/library/io.rst:362 +msgid "" +"Write a list of lines to the stream. Line separators are not added, so it " +"is usual for each of the lines provided to have a line separator at the end." +msgstr "" + +#: ../Doc/library/io.rst:368 +msgid "" +"Prepare for object destruction. :class:`IOBase` provides a default " +"implementation of this method that calls the instance's :meth:`~IOBase." +"close` method." +msgstr "" + +#: ../Doc/library/io.rst:375 +msgid "" +"Base class for raw binary I/O. It inherits :class:`IOBase`. There is no " +"public constructor." +msgstr "" + +#: ../Doc/library/io.rst:378 +msgid "" +"Raw binary I/O typically provides low-level access to an underlying OS " +"device or API, and does not try to encapsulate it in high-level primitives " +"(this is left to Buffered I/O and Text I/O, described later in this page)." +msgstr "" + +#: ../Doc/library/io.rst:382 +msgid "" +"In addition to the attributes and methods from :class:`IOBase`, :class:" +"`RawIOBase` provides the following methods:" +msgstr "" + +#: ../Doc/library/io.rst:387 +msgid "" +"Read up to *size* bytes from the object and return them. As a convenience, " +"if *size* is unspecified or -1, :meth:`readall` is called. Otherwise, only " +"one system call is ever made. Fewer than *size* bytes may be returned if " +"the operating system call returns fewer than *size* bytes." +msgstr "" + +#: ../Doc/library/io.rst:392 +msgid "" +"If 0 bytes are returned, and *size* was not 0, this indicates end of file. " +"If the object is in non-blocking mode and no bytes are available, ``None`` " +"is returned." +msgstr "" + +#: ../Doc/library/io.rst:398 +msgid "" +"Read and return all the bytes from the stream until EOF, using multiple " +"calls to the stream if necessary." +msgstr "" + +#: ../Doc/library/io.rst:403 +msgid "" +"Read bytes into a pre-allocated, writable :term:`bytes-like object` *b*, and " +"return the number of bytes read. If the object is in non-blocking mode and " +"no bytes are available, ``None`` is returned." +msgstr "" + +#: ../Doc/library/io.rst:410 +msgid "" +"Write the given :term:`bytes-like object`, *b*, to the underlying raw " +"stream, and return the number of bytes written. This can be less than the " +"length of *b* in bytes, depending on specifics of the underlying raw stream, " +"and especially if it is in non-blocking mode. ``None`` is returned if the " +"raw stream is set not to block and no single byte could be readily written " +"to it. The caller may release or mutate *b* after this method returns, so " +"the implementation should only access *b* during the method call." +msgstr "" + +#: ../Doc/library/io.rst:423 +msgid "" +"Base class for binary streams that support some kind of buffering. It " +"inherits :class:`IOBase`. There is no public constructor." +msgstr "" + +#: ../Doc/library/io.rst:426 +msgid "" +"The main difference with :class:`RawIOBase` is that methods :meth:`read`, :" +"meth:`readinto` and :meth:`write` will try (respectively) to read as much " +"input as requested or to consume all given output, at the expense of making " +"perhaps more than one system call." +msgstr "" + +#: ../Doc/library/io.rst:431 +msgid "" +"In addition, those methods can raise :exc:`BlockingIOError` if the " +"underlying raw stream is in non-blocking mode and cannot take or give enough " +"data; unlike their :class:`RawIOBase` counterparts, they will never return " +"``None``." +msgstr "" + +#: ../Doc/library/io.rst:436 +msgid "" +"Besides, the :meth:`read` method does not have a default implementation that " +"defers to :meth:`readinto`." +msgstr "" + +#: ../Doc/library/io.rst:439 +msgid "" +"A typical :class:`BufferedIOBase` implementation should not inherit from a :" +"class:`RawIOBase` implementation, but wrap one, like :class:`BufferedWriter` " +"and :class:`BufferedReader` do." +msgstr "" + +#: ../Doc/library/io.rst:443 +msgid "" +":class:`BufferedIOBase` provides or overrides these methods and attribute in " +"addition to those from :class:`IOBase`:" +msgstr "" + +#: ../Doc/library/io.rst:448 +msgid "" +"The underlying raw stream (a :class:`RawIOBase` instance) that :class:" +"`BufferedIOBase` deals with. This is not part of the :class:" +"`BufferedIOBase` API and may not exist on some implementations." +msgstr "" + +#: ../Doc/library/io.rst:454 +msgid "Separate the underlying raw stream from the buffer and return it." +msgstr "" + +#: ../Doc/library/io.rst:456 +msgid "" +"After the raw stream has been detached, the buffer is in an unusable state." +msgstr "" + +#: ../Doc/library/io.rst:459 +msgid "" +"Some buffers, like :class:`BytesIO`, do not have the concept of a single raw " +"stream to return from this method. They raise :exc:`UnsupportedOperation`." +msgstr "" + +#: ../Doc/library/io.rst:467 +msgid "" +"Read and return up to *size* bytes. If the argument is omitted, ``None``, " +"or negative, data is read and returned until EOF is reached. An empty :" +"class:`bytes` object is returned if the stream is already at EOF." +msgstr "" + +#: ../Doc/library/io.rst:471 +msgid "" +"If the argument is positive, and the underlying raw stream is not " +"interactive, multiple raw reads may be issued to satisfy the byte count " +"(unless EOF is reached first). But for interactive raw streams, at most one " +"raw read will be issued, and a short result does not imply that EOF is " +"imminent." +msgstr "" + +#: ../Doc/library/io.rst:477 ../Doc/library/io.rst:496 +#: ../Doc/library/io.rst:506 +msgid "" +"A :exc:`BlockingIOError` is raised if the underlying raw stream is in non " +"blocking-mode, and has no data available at the moment." +msgstr "" + +#: ../Doc/library/io.rst:482 +msgid "" +"Read and return up to *size* bytes, with at most one call to the underlying " +"raw stream's :meth:`~RawIOBase.read` (or :meth:`~RawIOBase.readinto`) " +"method. This can be useful if you are implementing your own buffering on " +"top of a :class:`BufferedIOBase` object." +msgstr "" + +#: ../Doc/library/io.rst:490 +msgid "" +"Read bytes into a pre-allocated, writable :term:`bytes-like object` *b* and " +"return the number of bytes read." +msgstr "" + +#: ../Doc/library/io.rst:493 +msgid "" +"Like :meth:`read`, multiple reads may be issued to the underlying raw " +"stream, unless the latter is interactive." +msgstr "" + +#: ../Doc/library/io.rst:501 +msgid "" +"Read bytes into a pre-allocated, writable :term:`bytes-like object` *b*, " +"using at most one call to the underlying raw stream's :meth:`~RawIOBase." +"read` (or :meth:`~RawIOBase.readinto`) method. Return the number of bytes " +"read." +msgstr "" + +#: ../Doc/library/io.rst:513 +msgid "" +"Write the given :term:`bytes-like object`, *b*, and return the number of " +"bytes written (always equal to the length of *b* in bytes, since if the " +"write fails an :exc:`OSError` will be raised). Depending on the actual " +"implementation, these bytes may be readily written to the underlying stream, " +"or held in a buffer for performance and latency reasons." +msgstr "" + +#: ../Doc/library/io.rst:520 +msgid "" +"When in non-blocking mode, a :exc:`BlockingIOError` is raised if the data " +"needed to be written to the raw stream but it couldn't accept all the data " +"without blocking." +msgstr "" + +#: ../Doc/library/io.rst:524 +msgid "" +"The caller may release or mutate *b* after this method returns, so the " +"implementation should only access *b* during the method call." +msgstr "" + +#: ../Doc/library/io.rst:529 +msgid "Raw File I/O" +msgstr "" + +#: ../Doc/library/io.rst:533 +msgid "" +":class:`FileIO` represents an OS-level file containing bytes data. It " +"implements the :class:`RawIOBase` interface (and therefore the :class:" +"`IOBase` interface, too)." +msgstr "" + +#: ../Doc/library/io.rst:537 +msgid "The *name* can be one of two things:" +msgstr "" + +#: ../Doc/library/io.rst:539 +msgid "" +"a character string or :class:`bytes` object representing the path to the " +"file which will be opened. In this case closefd must be True (the default) " +"otherwise an error will be raised." +msgstr "" + +#: ../Doc/library/io.rst:542 +msgid "" +"an integer representing the number of an existing OS-level file descriptor " +"to which the resulting :class:`FileIO` object will give access. When the " +"FileIO object is closed this fd will be closed as well, unless *closefd* is " +"set to ``False``." +msgstr "" + +#: ../Doc/library/io.rst:547 +msgid "" +"The *mode* can be ``'r'``, ``'w'``, ``'x'`` or ``'a'`` for reading " +"(default), writing, exclusive creation or appending. The file will be " +"created if it doesn't exist when opened for writing or appending; it will be " +"truncated when opened for writing. :exc:`FileExistsError` will be raised if " +"it already exists when opened for creating. Opening a file for creating " +"implies writing, so this mode behaves in a similar way to ``'w'``. Add a " +"``'+'`` to the mode to allow simultaneous reading and writing." +msgstr "" + +#: ../Doc/library/io.rst:555 +msgid "" +"The :meth:`read` (when called with a positive argument), :meth:`readinto` " +"and :meth:`write` methods on this class will only make one system call." +msgstr "" + +#: ../Doc/library/io.rst:558 +msgid "" +"A custom opener can be used by passing a callable as *opener*. The " +"underlying file descriptor for the file object is then obtained by calling " +"*opener* with (*name*, *flags*). *opener* must return an open file " +"descriptor (passing :mod:`os.open` as *opener* results in functionality " +"similar to passing ``None``)." +msgstr "" + +#: ../Doc/library/io.rst:566 +msgid "" +"See the :func:`open` built-in function for examples on using the *opener* " +"parameter." +msgstr "" + +#: ../Doc/library/io.rst:569 +msgid "The *opener* parameter was added. The ``'x'`` mode was added." +msgstr "" + +#: ../Doc/library/io.rst:576 +msgid "" +"In addition to the attributes and methods from :class:`IOBase` and :class:" +"`RawIOBase`, :class:`FileIO` provides the following data attributes:" +msgstr "" + +#: ../Doc/library/io.rst:582 +msgid "The mode as given in the constructor." +msgstr "" + +#: ../Doc/library/io.rst:586 +msgid "" +"The file name. This is the file descriptor of the file when no name is " +"given in the constructor." +msgstr "" + +#: ../Doc/library/io.rst:591 +msgid "Buffered Streams" +msgstr "" + +#: ../Doc/library/io.rst:593 +msgid "" +"Buffered I/O streams provide a higher-level interface to an I/O device than " +"raw I/O does." +msgstr "" + +#: ../Doc/library/io.rst:598 +msgid "" +"A stream implementation using an in-memory bytes buffer. It inherits :class:" +"`BufferedIOBase`. The buffer is discarded when the :meth:`~IOBase.close` " +"method is called." +msgstr "" + +#: ../Doc/library/io.rst:602 +msgid "" +"The optional argument *initial_bytes* is a :term:`bytes-like object` that " +"contains initial data." +msgstr "" + +#: ../Doc/library/io.rst:605 +msgid "" +":class:`BytesIO` provides or overrides these methods in addition to those " +"from :class:`BufferedIOBase` and :class:`IOBase`:" +msgstr "" + +#: ../Doc/library/io.rst:610 +msgid "" +"Return a readable and writable view over the contents of the buffer without " +"copying them. Also, mutating the view will transparently update the " +"contents of the buffer::" +msgstr "" + +#: ../Doc/library/io.rst:621 +msgid "" +"As long as the view exists, the :class:`BytesIO` object cannot be resized or " +"closed." +msgstr "" + +#: ../Doc/library/io.rst:628 +msgid "Return :class:`bytes` containing the entire contents of the buffer." +msgstr "" + +#: ../Doc/library/io.rst:633 +msgid "In :class:`BytesIO`, this is the same as :meth:`read`." +msgstr "" + +#: ../Doc/library/io.rst:637 +msgid "In :class:`BytesIO`, this is the same as :meth:`readinto`." +msgstr "" + +#: ../Doc/library/io.rst:643 +msgid "" +"A buffer providing higher-level access to a readable, sequential :class:" +"`RawIOBase` object. It inherits :class:`BufferedIOBase`. When reading data " +"from this object, a larger amount of data may be requested from the " +"underlying raw stream, and kept in an internal buffer. The buffered data can " +"then be returned directly on subsequent reads." +msgstr "" + +#: ../Doc/library/io.rst:649 +msgid "" +"The constructor creates a :class:`BufferedReader` for the given readable " +"*raw* stream and *buffer_size*. If *buffer_size* is omitted, :data:" +"`DEFAULT_BUFFER_SIZE` is used." +msgstr "" + +#: ../Doc/library/io.rst:653 +msgid "" +":class:`BufferedReader` provides or overrides these methods in addition to " +"those from :class:`BufferedIOBase` and :class:`IOBase`:" +msgstr "" + +#: ../Doc/library/io.rst:658 +msgid "" +"Return bytes from the stream without advancing the position. At most one " +"single read on the raw stream is done to satisfy the call. The number of " +"bytes returned may be less or more than requested." +msgstr "" + +#: ../Doc/library/io.rst:664 +msgid "" +"Read and return *size* bytes, or if *size* is not given or negative, until " +"EOF or if the read call would block in non-blocking mode." +msgstr "" + +#: ../Doc/library/io.rst:669 +msgid "" +"Read and return up to *size* bytes with only one call on the raw stream. If " +"at least one byte is buffered, only buffered bytes are returned. Otherwise, " +"one raw stream read call is made." +msgstr "" + +#: ../Doc/library/io.rst:676 +msgid "" +"A buffer providing higher-level access to a writeable, sequential :class:" +"`RawIOBase` object. It inherits :class:`BufferedIOBase`. When writing to " +"this object, data is normally placed into an internal buffer. The buffer " +"will be written out to the underlying :class:`RawIOBase` object under " +"various conditions, including:" +msgstr "" + +#: ../Doc/library/io.rst:682 +msgid "when the buffer gets too small for all pending data;" +msgstr "" + +#: ../Doc/library/io.rst:683 +msgid "when :meth:`flush()` is called;" +msgstr "" + +#: ../Doc/library/io.rst:684 +msgid "" +"when a :meth:`seek()` is requested (for :class:`BufferedRandom` objects);" +msgstr "" + +#: ../Doc/library/io.rst:685 +msgid "when the :class:`BufferedWriter` object is closed or destroyed." +msgstr "" + +#: ../Doc/library/io.rst:687 +msgid "" +"The constructor creates a :class:`BufferedWriter` for the given writeable " +"*raw* stream. If the *buffer_size* is not given, it defaults to :data:" +"`DEFAULT_BUFFER_SIZE`." +msgstr "" + +#: ../Doc/library/io.rst:691 +msgid "" +":class:`BufferedWriter` provides or overrides these methods in addition to " +"those from :class:`BufferedIOBase` and :class:`IOBase`:" +msgstr "" + +#: ../Doc/library/io.rst:696 +msgid "" +"Force bytes held in the buffer into the raw stream. A :exc:" +"`BlockingIOError` should be raised if the raw stream blocks." +msgstr "" + +#: ../Doc/library/io.rst:701 +msgid "" +"Write the :term:`bytes-like object`, *b*, and return the number of bytes " +"written. When in non-blocking mode, a :exc:`BlockingIOError` is raised if " +"the buffer needs to be written out but the raw stream blocks." +msgstr "" + +#: ../Doc/library/io.rst:709 +msgid "" +"A buffered interface to random access streams. It inherits :class:" +"`BufferedReader` and :class:`BufferedWriter`, and further supports :meth:" +"`seek` and :meth:`tell` functionality." +msgstr "" + +#: ../Doc/library/io.rst:713 +msgid "" +"The constructor creates a reader and writer for a seekable raw stream, given " +"in the first argument. If the *buffer_size* is omitted it defaults to :data:" +"`DEFAULT_BUFFER_SIZE`." +msgstr "" + +#: ../Doc/library/io.rst:717 +msgid "" +":class:`BufferedRandom` is capable of anything :class:`BufferedReader` or :" +"class:`BufferedWriter` can do." +msgstr "" + +#: ../Doc/library/io.rst:723 +msgid "" +"A buffered I/O object combining two unidirectional :class:`RawIOBase` " +"objects -- one readable, the other writeable -- into a single bidirectional " +"endpoint. It inherits :class:`BufferedIOBase`." +msgstr "" + +#: ../Doc/library/io.rst:727 +msgid "" +"*reader* and *writer* are :class:`RawIOBase` objects that are readable and " +"writeable respectively. If the *buffer_size* is omitted it defaults to :" +"data:`DEFAULT_BUFFER_SIZE`." +msgstr "" + +#: ../Doc/library/io.rst:731 +msgid "" +":class:`BufferedRWPair` implements all of :class:`BufferedIOBase`\\'s " +"methods except for :meth:`~BufferedIOBase.detach`, which raises :exc:" +"`UnsupportedOperation`." +msgstr "" + +#: ../Doc/library/io.rst:737 +msgid "" +":class:`BufferedRWPair` does not attempt to synchronize accesses to its " +"underlying raw streams. You should not pass it the same object as reader " +"and writer; use :class:`BufferedRandom` instead." +msgstr "" + +#: ../Doc/library/io.rst:747 +msgid "" +"Base class for text streams. This class provides a character and line based " +"interface to stream I/O. There is no :meth:`readinto` method because " +"Python's character strings are immutable. It inherits :class:`IOBase`. " +"There is no public constructor." +msgstr "" + +#: ../Doc/library/io.rst:752 +msgid "" +":class:`TextIOBase` provides or overrides these data attributes and methods " +"in addition to those from :class:`IOBase`:" +msgstr "" + +#: ../Doc/library/io.rst:757 +msgid "" +"The name of the encoding used to decode the stream's bytes into strings, and " +"to encode strings into bytes." +msgstr "" + +#: ../Doc/library/io.rst:762 +msgid "The error setting of the decoder or encoder." +msgstr "" + +#: ../Doc/library/io.rst:766 +msgid "" +"A string, a tuple of strings, or ``None``, indicating the newlines " +"translated so far. Depending on the implementation and the initial " +"constructor flags, this may not be available." +msgstr "" + +#: ../Doc/library/io.rst:772 +msgid "" +"The underlying binary buffer (a :class:`BufferedIOBase` instance) that :" +"class:`TextIOBase` deals with. This is not part of the :class:`TextIOBase` " +"API and may not exist in some implementations." +msgstr "" + +#: ../Doc/library/io.rst:778 +msgid "" +"Separate the underlying binary buffer from the :class:`TextIOBase` and " +"return it." +msgstr "" + +#: ../Doc/library/io.rst:781 +msgid "" +"After the underlying buffer has been detached, the :class:`TextIOBase` is in " +"an unusable state." +msgstr "" + +#: ../Doc/library/io.rst:784 +msgid "" +"Some :class:`TextIOBase` implementations, like :class:`StringIO`, may not " +"have the concept of an underlying buffer and calling this method will raise :" +"exc:`UnsupportedOperation`." +msgstr "" + +#: ../Doc/library/io.rst:792 +msgid "" +"Read and return at most *size* characters from the stream as a single :class:" +"`str`. If *size* is negative or ``None``, reads until EOF." +msgstr "" + +#: ../Doc/library/io.rst:797 +msgid "" +"Read until newline or EOF and return a single ``str``. If the stream is " +"already at EOF, an empty string is returned." +msgstr "" + +#: ../Doc/library/io.rst:800 +msgid "If *size* is specified, at most *size* characters will be read." +msgstr "" + +#: ../Doc/library/io.rst:804 +msgid "" +"Change the stream position to the given *offset*. Behaviour depends on the " +"*whence* parameter. The default value for *whence* is :data:`SEEK_SET`." +msgstr "" + +#: ../Doc/library/io.rst:808 +msgid "" +":data:`SEEK_SET` or ``0``: seek from the start of the stream (the default); " +"*offset* must either be a number returned by :meth:`TextIOBase.tell`, or " +"zero. Any other *offset* value produces undefined behaviour." +msgstr "" + +#: ../Doc/library/io.rst:812 +msgid "" +":data:`SEEK_CUR` or ``1``: \"seek\" to the current position; *offset* must " +"be zero, which is a no-operation (all other values are unsupported)." +msgstr "" + +#: ../Doc/library/io.rst:815 +msgid "" +":data:`SEEK_END` or ``2``: seek to the end of the stream; *offset* must be " +"zero (all other values are unsupported)." +msgstr "" + +#: ../Doc/library/io.rst:818 +msgid "Return the new absolute position as an opaque number." +msgstr "" + +#: ../Doc/library/io.rst:825 +msgid "" +"Return the current stream position as an opaque number. The number does not " +"usually represent a number of bytes in the underlying binary storage." +msgstr "" + +#: ../Doc/library/io.rst:831 +msgid "" +"Write the string *s* to the stream and return the number of characters " +"written." +msgstr "" + +#: ../Doc/library/io.rst:838 +msgid "" +"A buffered text stream over a :class:`BufferedIOBase` binary stream. It " +"inherits :class:`TextIOBase`." +msgstr "" + +#: ../Doc/library/io.rst:841 +msgid "" +"*encoding* gives the name of the encoding that the stream will be decoded or " +"encoded with. It defaults to :func:`locale.getpreferredencoding(False) " +"`." +msgstr "" + +#: ../Doc/library/io.rst:845 +msgid "" +"*errors* is an optional string that specifies how encoding and decoding " +"errors are to be handled. Pass ``'strict'`` to raise a :exc:`ValueError` " +"exception if there is an encoding error (the default of ``None`` has the " +"same effect), or pass ``'ignore'`` to ignore errors. (Note that ignoring " +"encoding errors can lead to data loss.) ``'replace'`` causes a replacement " +"marker (such as ``'?'``) to be inserted where there is malformed data. " +"``'backslashreplace'`` causes malformed data to be replaced by a backslashed " +"escape sequence. When writing, ``'xmlcharrefreplace'`` (replace with the " +"appropriate XML character reference) or ``'namereplace'`` (replace with ``" +"\\N{...}`` escape sequences) can be used. Any other error handling name " +"that has been registered with :func:`codecs.register_error` is also valid." +msgstr "" + +#: ../Doc/library/io.rst:861 +msgid "" +"*newline* controls how line endings are handled. It can be ``None``, " +"``''``, ``'\\n'``, ``'\\r'``, and ``'\\r\\n'``. It works as follows:" +msgstr "" + +#: ../Doc/library/io.rst:864 +msgid "" +"When reading input from the stream, if *newline* is ``None``, :term:" +"`universal newlines` mode is enabled. Lines in the input can end in " +"``'\\n'``, ``'\\r'``, or ``'\\r\\n'``, and these are translated into " +"``'\\n'`` before being returned to the caller. If it is ``''``, universal " +"newlines mode is enabled, but line endings are returned to the caller " +"untranslated. If it has any of the other legal values, input lines are only " +"terminated by the given string, and the line ending is returned to the " +"caller untranslated." +msgstr "" + +#: ../Doc/library/io.rst:879 +msgid "" +"If *line_buffering* is ``True``, :meth:`flush` is implied when a call to " +"write contains a newline character." +msgstr "" + +#: ../Doc/library/io.rst:882 +msgid "" +"If *write_through* is ``True``, calls to :meth:`write` are guaranteed not to " +"be buffered: any data written on the :class:`TextIOWrapper` object is " +"immediately handled to its underlying binary *buffer*." +msgstr "" + +#: ../Doc/library/io.rst:886 +msgid "The *write_through* argument has been added." +msgstr "" + +#: ../Doc/library/io.rst:889 +msgid "" +"The default *encoding* is now ``locale.getpreferredencoding(False)`` instead " +"of ``locale.getpreferredencoding()``. Don't change temporary the locale " +"encoding using :func:`locale.setlocale`, use the current locale encoding " +"instead of the user preferred encoding." +msgstr "" + +#: ../Doc/library/io.rst:895 +msgid "" +":class:`TextIOWrapper` provides one attribute in addition to those of :class:" +"`TextIOBase` and its parents:" +msgstr "" + +#: ../Doc/library/io.rst:900 +msgid "Whether line buffering is enabled." +msgstr "" + +#: ../Doc/library/io.rst:905 +msgid "" +"An in-memory stream for text I/O. The text buffer is discarded when the :" +"meth:`~IOBase.close` method is called." +msgstr "" + +#: ../Doc/library/io.rst:908 +msgid "" +"The initial value of the buffer can be set by providing *initial_value*. If " +"newline translation is enabled, newlines will be encoded as if by :meth:" +"`~TextIOBase.write`. The stream is positioned at the start of the buffer." +msgstr "" + +#: ../Doc/library/io.rst:913 +msgid "" +"The *newline* argument works like that of :class:`TextIOWrapper`. The " +"default is to consider only ``\\n`` characters as ends of lines and to do no " +"newline translation. If *newline* is set to ``None``, newlines are written " +"as ``\\n`` on all platforms, but universal newline decoding is still " +"performed when reading." +msgstr "" + +#: ../Doc/library/io.rst:919 +msgid "" +":class:`StringIO` provides this method in addition to those from :class:" +"`TextIOBase` and its parents:" +msgstr "" + +#: ../Doc/library/io.rst:924 +msgid "" +"Return a ``str`` containing the entire contents of the buffer. Newlines are " +"decoded as if by :meth:`~TextIOBase.read`, although the stream position is " +"not changed." +msgstr "" + +#: ../Doc/library/io.rst:928 ../Doc/library/wsgiref.rst:117 +#: ../Doc/library/wsgiref.rst:164 ../Doc/library/wsgiref.rst:284 +#: ../Doc/library/wsgiref.rst:416 +msgid "Example usage::" +msgstr "" + +#: ../Doc/library/io.rst:950 +msgid "" +"A helper codec that decodes newlines for :term:`universal newlines` mode. It " +"inherits :class:`codecs.IncrementalDecoder`." +msgstr "" + +#: ../Doc/library/io.rst:955 ../Doc/library/pickle.rst:853 +msgid "Performance" +msgstr "" + +#: ../Doc/library/io.rst:957 +msgid "" +"This section discusses the performance of the provided concrete I/O " +"implementations." +msgstr "" + +#: ../Doc/library/io.rst:963 +msgid "" +"By reading and writing only large chunks of data even when the user asks for " +"a single byte, buffered I/O hides any inefficiency in calling and executing " +"the operating system's unbuffered I/O routines. The gain depends on the OS " +"and the kind of I/O which is performed. For example, on some modern OSes " +"such as Linux, unbuffered disk I/O can be as fast as buffered I/O. The " +"bottom line, however, is that buffered I/O offers predictable performance " +"regardless of the platform and the backing device. Therefore, it is almost " +"always preferable to use buffered I/O rather than unbuffered I/O for binary " +"data." +msgstr "" + +#: ../Doc/library/io.rst:975 +msgid "" +"Text I/O over a binary storage (such as a file) is significantly slower than " +"binary I/O over the same storage, because it requires conversions between " +"unicode and binary data using a character codec. This can become noticeable " +"handling huge amounts of text data like large log files. Also, :meth:" +"`TextIOWrapper.tell` and :meth:`TextIOWrapper.seek` are both quite slow due " +"to the reconstruction algorithm used." +msgstr "" + +#: ../Doc/library/io.rst:982 +msgid "" +":class:`StringIO`, however, is a native in-memory unicode container and will " +"exhibit similar speed to :class:`BytesIO`." +msgstr "" + +#: ../Doc/library/io.rst:986 +msgid "Multi-threading" +msgstr "" + +#: ../Doc/library/io.rst:988 +msgid "" +":class:`FileIO` objects are thread-safe to the extent that the operating " +"system calls (such as ``read(2)`` under Unix) they wrap are thread-safe too." +msgstr "" + +#: ../Doc/library/io.rst:991 +msgid "" +"Binary buffered objects (instances of :class:`BufferedReader`, :class:" +"`BufferedWriter`, :class:`BufferedRandom` and :class:`BufferedRWPair`) " +"protect their internal structures using a lock; it is therefore safe to call " +"them from multiple threads at once." +msgstr "" + +#: ../Doc/library/io.rst:996 +msgid ":class:`TextIOWrapper` objects are not thread-safe." +msgstr "" + +#: ../Doc/library/io.rst:999 +msgid "Reentrancy" +msgstr "" + +#: ../Doc/library/io.rst:1001 +msgid "" +"Binary buffered objects (instances of :class:`BufferedReader`, :class:" +"`BufferedWriter`, :class:`BufferedRandom` and :class:`BufferedRWPair`) are " +"not reentrant. While reentrant calls will not happen in normal situations, " +"they can arise from doing I/O in a :mod:`signal` handler. If a thread tries " +"to re-enter a buffered object which it is already accessing, a :exc:" +"`RuntimeError` is raised. Note this doesn't prohibit a different thread " +"from entering the buffered object." +msgstr "" + +#: ../Doc/library/io.rst:1009 +msgid "" +"The above implicitly extends to text files, since the :func:`open()` " +"function will wrap a buffered object inside a :class:`TextIOWrapper`. This " +"includes standard streams and therefore affects the built-in function :func:" +"`print()` as well." +msgstr "" + +#: ../Doc/library/ipaddress.rst:2 +msgid ":mod:`ipaddress` --- IPv4/IPv6 manipulation library" +msgstr "" + +#: ../Doc/library/ipaddress.rst:9 +msgid "**Source code:** :source:`Lib/ipaddress.py`" +msgstr "" + +#: ../Doc/library/ipaddress.rst:13 +msgid "" +":mod:`ipaddress` provides the capabilities to create, manipulate and operate " +"on IPv4 and IPv6 addresses and networks." +msgstr "" + +#: ../Doc/library/ipaddress.rst:16 +msgid "" +"The functions and classes in this module make it straightforward to handle " +"various tasks related to IP addresses, including checking whether or not two " +"hosts are on the same subnet, iterating over all hosts in a particular " +"subnet, checking whether or not a string represents a valid IP address or " +"network definition, and so on." +msgstr "" + +#: ../Doc/library/ipaddress.rst:22 +msgid "" +"This is the full module API reference—for an overview and introduction, see :" +"ref:`ipaddress-howto`." +msgstr "" + +#: ../Doc/library/ipaddress.rst:33 +msgid "Convenience factory functions" +msgstr "" + +#: ../Doc/library/ipaddress.rst:35 +msgid "" +"The :mod:`ipaddress` module provides factory functions to conveniently " +"create IP addresses, networks and interfaces:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:40 +msgid "" +"Return an :class:`IPv4Address` or :class:`IPv6Address` object depending on " +"the IP address passed as argument. Either IPv4 or IPv6 addresses may be " +"supplied; integers less than 2**32 will be considered to be IPv4 by default. " +"A :exc:`ValueError` is raised if *address* does not represent a valid IPv4 " +"or IPv6 address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:54 +msgid "" +"Return an :class:`IPv4Network` or :class:`IPv6Network` object depending on " +"the IP address passed as argument. *address* is a string or integer " +"representing the IP network. Either IPv4 or IPv6 networks may be supplied; " +"integers less than 2**32 will be considered to be IPv4 by default. *strict* " +"is passed to :class:`IPv4Network` or :class:`IPv6Network` constructor. A :" +"exc:`ValueError` is raised if *address* does not represent a valid IPv4 or " +"IPv6 address, or if the network has host bits set." +msgstr "" + +#: ../Doc/library/ipaddress.rst:68 +msgid "" +"Return an :class:`IPv4Interface` or :class:`IPv6Interface` object depending " +"on the IP address passed as argument. *address* is a string or integer " +"representing the IP address. Either IPv4 or IPv6 addresses may be supplied; " +"integers less than 2**32 will be considered to be IPv4 by default. A :exc:" +"`ValueError` is raised if *address* does not represent a valid IPv4 or IPv6 " +"address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:75 +msgid "" +"One downside of these convenience functions is that the need to handle both " +"IPv4 and IPv6 formats means that error messages provide minimal information " +"on the precise error, as the functions don't know whether the IPv4 or IPv6 " +"format was intended. More detailed error reporting can be obtained by " +"calling the appropriate version specific class constructors directly." +msgstr "" + +#: ../Doc/library/ipaddress.rst:84 +msgid "IP Addresses" +msgstr "" + +#: ../Doc/library/ipaddress.rst:87 +msgid "Address objects" +msgstr "" + +#: ../Doc/library/ipaddress.rst:89 +msgid "" +"The :class:`IPv4Address` and :class:`IPv6Address` objects share a lot of " +"common attributes. Some attributes that are only meaningful for IPv6 " +"addresses are also implemented by :class:`IPv4Address` objects, in order to " +"make it easier to write code that handles both IP versions correctly." +msgstr "" + +#: ../Doc/library/ipaddress.rst:96 +msgid "" +"Construct an IPv4 address. An :exc:`AddressValueError` is raised if " +"*address* is not a valid IPv4 address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:99 +msgid "The following constitutes a valid IPv4 address:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:101 +msgid "" +"A string in decimal-dot notation, consisting of four decimal integers in the " +"inclusive range 0-255, separated by dots (e.g. ``192.168.0.1``). Each " +"integer represents an octet (byte) in the address. Leading zeroes are " +"tolerated only for values less than 8 (as there is no ambiguity between the " +"decimal and octal interpretations of such strings)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:106 +msgid "An integer that fits into 32 bits." +msgstr "" + +#: ../Doc/library/ipaddress.rst:107 +msgid "" +"An integer packed into a :class:`bytes` object of length 4 (most significant " +"octet first)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:119 +msgid "The appropriate version number: ``4`` for IPv4, ``6`` for IPv6." +msgstr "" + +#: ../Doc/library/ipaddress.rst:123 +msgid "" +"The total number of bits in the address representation for this version: " +"``32`` for IPv4, ``128`` for IPv6." +msgstr "" + +#: ../Doc/library/ipaddress.rst:126 +msgid "" +"The prefix defines the number of leading bits in an address that are " +"compared to determine whether or not an address is part of a network." +msgstr "" + +#: ../Doc/library/ipaddress.rst:133 +msgid "" +"The string representation in dotted decimal notation. Leading zeroes are " +"never included in the representation." +msgstr "" + +#: ../Doc/library/ipaddress.rst:136 +msgid "" +"As IPv4 does not define a shorthand notation for addresses with octets set " +"to zero, these two attributes are always the same as ``str(addr)`` for IPv4 " +"addresses. Exposing these attributes makes it easier to write display code " +"that can handle both IPv4 and IPv6 addresses." +msgstr "" + +#: ../Doc/library/ipaddress.rst:143 +msgid "" +"The binary representation of this address - a :class:`bytes` object of the " +"appropriate length (most significant octet first). This is 4 bytes for IPv4 " +"and 16 bytes for IPv6." +msgstr "" + +#: ../Doc/library/ipaddress.rst:149 +msgid "The name of the reverse DNS PTR record for the IP address, e.g.::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:156 +msgid "" +"This is the name that could be used for performing a PTR lookup, not the " +"resolved hostname itself." +msgstr "" + +#: ../Doc/library/ipaddress.rst:163 +msgid "" +"``True`` if the address is reserved for multicast use. See :RFC:`3171` (for " +"IPv4) or :RFC:`2373` (for IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:168 +msgid "" +"``True`` if the address is allocated for private networks. See iana-ipv4-" +"special-registry_ (for IPv4) or iana-ipv6-special-registry_ (for IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:174 +msgid "" +"``True`` if the address is allocated for public networks. See iana-ipv4-" +"special-registry_ (for IPv4) or iana-ipv6-special-registry_ (for IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:182 +msgid "" +"``True`` if the address is unspecified. See :RFC:`5735` (for IPv4) or :RFC:" +"`2373` (for IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:187 +msgid "``True`` if the address is otherwise IETF reserved." +msgstr "" + +#: ../Doc/library/ipaddress.rst:191 +msgid "" +"``True`` if this is a loopback address. See :RFC:`3330` (for IPv4) or :RFC:" +"`2373` (for IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:196 +msgid "" +"``True`` if the address is reserved for link-local usage. See :RFC:`3927`." +msgstr "" + +#: ../Doc/library/ipaddress.rst:205 +msgid "" +"Construct an IPv6 address. An :exc:`AddressValueError` is raised if " +"*address* is not a valid IPv6 address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:208 +msgid "The following constitutes a valid IPv6 address:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:210 +msgid "" +"A string consisting of eight groups of four hexadecimal digits, each group " +"representing 16 bits. The groups are separated by colons. This describes an " +"*exploded* (longhand) notation. The string can also be *compressed* " +"(shorthand notation) by various means. See :RFC:`4291` for details. For " +"example, ``\"0000:0000:0000:0000:0000:0abc:0007:0def\"`` can be compressed " +"to ``\"::abc:7:def\"``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:217 +msgid "An integer that fits into 128 bits." +msgstr "" + +#: ../Doc/library/ipaddress.rst:218 +msgid "" +"An integer packed into a :class:`bytes` object of length 16, big-endian." +msgstr "" + +#: ../Doc/library/ipaddress.rst:225 +msgid "" +"The short form of the address representation, with leading zeroes in groups " +"omitted and the longest sequence of groups consisting entirely of zeroes " +"collapsed to a single empty group." +msgstr "" + +#: ../Doc/library/ipaddress.rst:229 +msgid "This is also the value returned by ``str(addr)`` for IPv6 addresses." +msgstr "" + +#: ../Doc/library/ipaddress.rst:233 +msgid "" +"The long form of the address representation, with all leading zeroes and " +"groups consisting entirely of zeroes included." +msgstr "" + +#: ../Doc/library/ipaddress.rst:237 +msgid "" +"For the following attributes, see the corresponding documention of the :" +"class:`IPv4Address` class:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:252 +msgid "is_global" +msgstr "" + +#: ../Doc/library/ipaddress.rst:257 +msgid "" +"``True`` if the address is reserved for site-local usage. Note that the " +"site-local address space has been deprecated by :RFC:`3879`. Use :attr:" +"`~IPv4Address.is_private` to test if this address is in the space of unique " +"local addresses as defined by :RFC:`4193`." +msgstr "" + +#: ../Doc/library/ipaddress.rst:264 +msgid "" +"For addresses that appear to be IPv4 mapped addresses (starting with ``::" +"FFFF/96``), this property will report the embedded IPv4 address. For any " +"other address, this property will be ``None``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:270 +msgid "" +"For addresses that appear to be 6to4 addresses (starting with " +"``2002::/16``) as defined by :RFC:`3056`, this property will report the " +"embedded IPv4 address. For any other address, this property will be " +"``None``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:277 +msgid "" +"For addresses that appear to be Teredo addresses (starting with " +"``2001::/32``) as defined by :RFC:`4380`, this property will report the " +"embedded ``(server, client)`` IP address pair. For any other address, this " +"property will be ``None``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:284 +msgid "Conversion to Strings and Integers" +msgstr "" + +#: ../Doc/library/ipaddress.rst:286 +msgid "" +"To interoperate with networking interfaces such as the socket module, " +"addresses must be converted to strings or integers. This is handled using " +"the :func:`str` and :func:`int` builtin functions::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:301 ../Doc/library/ipaddress.rst:631 +#: ../Doc/library/pathlib.rst:207 +msgid "Operators" +msgstr "" + +#: ../Doc/library/ipaddress.rst:303 +msgid "" +"Address objects support some operators. Unless stated otherwise, operators " +"can only be applied between compatible objects (i.e. IPv4 with IPv4, IPv6 " +"with IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:309 +msgid "Comparison operators" +msgstr "" + +#: ../Doc/library/ipaddress.rst:311 +msgid "" +"Address objects can be compared with the usual set of comparison operators. " +"Some examples::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:323 +msgid "Arithmetic operators" +msgstr "" + +#: ../Doc/library/ipaddress.rst:325 +msgid "" +"Integers can be added to or subtracted from address objects. Some examples::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:338 +msgid "IP Network definitions" +msgstr "" + +#: ../Doc/library/ipaddress.rst:340 +msgid "" +"The :class:`IPv4Network` and :class:`IPv6Network` objects provide a " +"mechanism for defining and inspecting IP network definitions. A network " +"definition consists of a *mask* and a *network address*, and as such defines " +"a range of IP addresses that equal the network address when masked (binary " +"AND) with the mask. For example, a network definition with the mask " +"``255.255.255.0`` and the network address ``192.168.1.0`` consists of IP " +"addresses in the inclusive range ``192.168.1.0`` to ``192.168.1.255``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:350 +msgid "Prefix, net mask and host mask" +msgstr "" + +#: ../Doc/library/ipaddress.rst:352 +msgid "" +"There are several equivalent ways to specify IP network masks. A *prefix* " +"``/`` is a notation that denotes how many high-order bits are set in " +"the network mask. A *net mask* is an IP address with some number of high-" +"order bits set. Thus the prefix ``/24`` is equivalent to the net mask " +"``255.255.255.0`` in IPv4, or ``ffff:ff00::`` in IPv6. In addition, a *host " +"mask* is the logical inverse of a *net mask*, and is sometimes used (for " +"example in Cisco access control lists) to denote a network mask. The host " +"mask equivalent to ``/24`` in IPv4 is ``0.0.0.255``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:363 +msgid "Network objects" +msgstr "" + +#: ../Doc/library/ipaddress.rst:365 +msgid "" +"All attributes implemented by address objects are implemented by network " +"objects as well. In addition, network objects implement additional " +"attributes. All of these are common between :class:`IPv4Network` and :class:" +"`IPv6Network`, so to avoid duplication they are only documented for :class:" +"`IPv4Network`." +msgstr "" + +#: ../Doc/library/ipaddress.rst:372 +msgid "" +"Construct an IPv4 network definition. *address* can be one of the following:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:374 +msgid "" +"A string consisting of an IP address and an optional mask, separated by a " +"slash (``/``). The IP address is the network address, and the mask can be " +"either a single number, which means it's a *prefix*, or a string " +"representation of an IPv4 address. If it's the latter, the mask is " +"interpreted as a *net mask* if it starts with a non-zero field, or as a " +"*host mask* if it starts with a zero field. If no mask is provided, it's " +"considered to be ``/32``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:382 +msgid "" +"For example, the following *address* specifications are equivalent: " +"``192.168.1.0/24``, ``192.168.1.0/255.255.255.0`` and " +"``192.168.1.0/0.0.0.255``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:386 +msgid "" +"An integer that fits into 32 bits. This is equivalent to a single-address " +"network, with the network address being *address* and the mask being ``/32``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:390 +msgid "" +"An integer packed into a :class:`bytes` object of length 4, big-endian. The " +"interpretation is similar to an integer *address*." +msgstr "" + +#: ../Doc/library/ipaddress.rst:393 +msgid "" +"A two-tuple of an address description and a netmask, where the address " +"description is either a string, a 32-bits integer, a 4-bytes packed integer, " +"or an existing IPv4Address object; and the netmask is either an integer " +"representing the prefix length (e.g. ``24``) or a string representing the " +"prefix mask (e.g. ``255.255.255.0``)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:399 +msgid "" +"An :exc:`AddressValueError` is raised if *address* is not a valid IPv4 " +"address. A :exc:`NetmaskValueError` is raised if the mask is not valid for " +"an IPv4 address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:403 ../Doc/library/ipaddress.rst:588 +msgid "" +"If *strict* is ``True`` and host bits are set in the supplied address, then :" +"exc:`ValueError` is raised. Otherwise, the host bits are masked out to " +"determine the appropriate network address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:407 +msgid "" +"Unless stated otherwise, all network methods accepting other network/address " +"objects will raise :exc:`TypeError` if the argument's IP version is " +"incompatible to ``self``" +msgstr "" + +#: ../Doc/library/ipaddress.rst:413 ../Doc/library/ipaddress.rst:594 +msgid "Added the two-tuple form for the *address* constructor parameter." +msgstr "" + +#: ../Doc/library/ipaddress.rst:418 +msgid "" +"Refer to the corresponding attribute documentation in :class:`IPv4Address`" +msgstr "" + +#: ../Doc/library/ipaddress.rst:428 +msgid "" +"These attributes are true for the network as a whole if they are true for " +"both the network address and the broadcast address" +msgstr "" + +#: ../Doc/library/ipaddress.rst:433 +msgid "" +"The network address for the network. The network address and the prefix " +"length together uniquely define a network." +msgstr "" + +#: ../Doc/library/ipaddress.rst:438 +msgid "" +"The broadcast address for the network. Packets sent to the broadcast address " +"should be received by every host on the network." +msgstr "" + +#: ../Doc/library/ipaddress.rst:443 +msgid "The host mask, as a string." +msgstr "" + +#: ../Doc/library/ipaddress.rst:449 +msgid "" +"A string representation of the network, with the mask in prefix notation." +msgstr "" + +#: ../Doc/library/ipaddress.rst:452 +msgid "" +"``with_prefixlen`` and ``compressed`` are always the same as " +"``str(network)``. ``exploded`` uses the exploded form the network address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:458 +msgid "" +"A string representation of the network, with the mask in net mask notation." +msgstr "" + +#: ../Doc/library/ipaddress.rst:463 +msgid "" +"A string representation of the network, with the mask in host mask notation." +msgstr "" + +#: ../Doc/library/ipaddress.rst:468 +msgid "The total number of addresses in the network." +msgstr "" + +#: ../Doc/library/ipaddress.rst:472 +msgid "Length of the network prefix, in bits." +msgstr "" + +#: ../Doc/library/ipaddress.rst:476 +msgid "" +"Returns an iterator over the usable hosts in the network. The usable hosts " +"are all the IP addresses that belong to the network, except the network " +"address itself and the network broadcast address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:487 +msgid "" +"``True`` if this network is partly or wholly contained in *other* or *other* " +"is wholly contained in this network." +msgstr "" + +#: ../Doc/library/ipaddress.rst:492 +msgid "" +"Computes the network definitions resulting from removing the given *network* " +"from this one. Returns an iterator of network objects. Raises :exc:" +"`ValueError` if *network* is not completely contained in this network." +msgstr "" + +#: ../Doc/library/ipaddress.rst:505 +msgid "" +"The subnets that join to make the current network definition, depending on " +"the argument values. *prefixlen_diff* is the amount our prefix length " +"should be increased by. *new_prefix* is the desired new prefix of the " +"subnets; it must be larger than our prefix. One and only one of " +"*prefixlen_diff* and *new_prefix* must be set. Returns an iterator of " +"network objects." +msgstr "" + +#: ../Doc/library/ipaddress.rst:530 +msgid "" +"The supernet containing this network definition, depending on the argument " +"values. *prefixlen_diff* is the amount our prefix length should be " +"decreased by. *new_prefix* is the desired new prefix of the supernet; it " +"must be smaller than our prefix. One and only one of *prefixlen_diff* and " +"*new_prefix* must be set. Returns a single network object." +msgstr "" + +#: ../Doc/library/ipaddress.rst:546 +msgid "" +"Compare this network to *other*. In this comparison only the network " +"addresses are considered; host bits aren't. Returns either ``-1``, ``0`` or " +"``1``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:560 +msgid "" +"Construct an IPv6 network definition. *address* can be one of the following:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:562 +msgid "" +"A string consisting of an IP address and an optional mask, separated by a " +"slash (``/``). The IP address is the network address, and the mask can be " +"either a single number, which means it's a *prefix*, or a string " +"representation of an IPv6 address. If it's the latter, the mask is " +"interpreted as a *net mask*. If no mask is provided, it's considered to be " +"``/128``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:569 +msgid "" +"For example, the following *address* specifications are equivalent: ``2001:" +"db00::0/24`` and ``2001:db00::0/ffff:ff00::``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:572 +msgid "" +"An integer that fits into 128 bits. This is equivalent to a single-address " +"network, with the network address being *address* and the mask being " +"``/128``." +msgstr "" + +#: ../Doc/library/ipaddress.rst:576 +msgid "" +"An integer packed into a :class:`bytes` object of length 16, big-endian. The " +"interpretation is similar to an integer *address*." +msgstr "" + +#: ../Doc/library/ipaddress.rst:579 +msgid "" +"A two-tuple of an address description and a netmask, where the address " +"description is either a string, a 128-bits integer, a 16-bytes packed " +"integer, or an existing IPv6Address object; and the netmask is an integer " +"representing the prefix length." +msgstr "" + +#: ../Doc/library/ipaddress.rst:584 +msgid "" +"An :exc:`AddressValueError` is raised if *address* is not a valid IPv6 " +"address. A :exc:`NetmaskValueError` is raised if the mask is not valid for " +"an IPv6 address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:621 +msgid "" +"Refer to the corresponding attribute documentation in :class:`IPv4Network`" +msgstr "" + +#: ../Doc/library/ipaddress.rst:626 +msgid "" +"These attribute is true for the network as a whole if it is true for both " +"the network address and the broadcast address" +msgstr "" + +#: ../Doc/library/ipaddress.rst:633 +msgid "" +"Network objects support some operators. Unless stated otherwise, operators " +"can only be applied between compatible objects (i.e. IPv4 with IPv4, IPv6 " +"with IPv6)." +msgstr "" + +#: ../Doc/library/ipaddress.rst:639 +msgid "Logical operators" +msgstr "" + +#: ../Doc/library/ipaddress.rst:641 +msgid "" +"Network objects can be compared with the usual set of logical operators, " +"similarly to address objects." +msgstr "" + +#: ../Doc/library/ipaddress.rst:648 +msgid "" +"Network objects can be iterated to list all the addresses belonging to the " +"network. For iteration, *all* hosts are returned, including unusable hosts " +"(for usable hosts, use the :meth:`~IPv4Network.hosts` method). An example::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:675 +msgid "Networks as containers of addresses" +msgstr "" + +#: ../Doc/library/ipaddress.rst:677 +msgid "Network objects can act as containers of addresses. Some examples::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:690 +msgid "Interface objects" +msgstr "" + +#: ../Doc/library/ipaddress.rst:694 +msgid "" +"Construct an IPv4 interface. The meaning of *address* is as in the " +"constructor of :class:`IPv4Network`, except that arbitrary host addresses " +"are always accepted." +msgstr "" + +#: ../Doc/library/ipaddress.rst:698 +msgid "" +":class:`IPv4Interface` is a subclass of :class:`IPv4Address`, so it inherits " +"all the attributes from that class. In addition, the following attributes " +"are available:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:704 +msgid "The address (:class:`IPv4Address`) without network information." +msgstr "" + +#: ../Doc/library/ipaddress.rst:712 +msgid "The network (:class:`IPv4Network`) this interface belongs to." +msgstr "" + +#: ../Doc/library/ipaddress.rst:720 +msgid "" +"A string representation of the interface with the mask in prefix notation." +msgstr "" + +#: ../Doc/library/ipaddress.rst:728 +msgid "" +"A string representation of the interface with the network as a net mask." +msgstr "" + +#: ../Doc/library/ipaddress.rst:736 +msgid "" +"A string representation of the interface with the network as a host mask." +msgstr "" + +#: ../Doc/library/ipaddress.rst:745 +msgid "" +"Construct an IPv6 interface. The meaning of *address* is as in the " +"constructor of :class:`IPv6Network`, except that arbitrary host addresses " +"are always accepted." +msgstr "" + +#: ../Doc/library/ipaddress.rst:749 +msgid "" +":class:`IPv6Interface` is a subclass of :class:`IPv6Address`, so it inherits " +"all the attributes from that class. In addition, the following attributes " +"are available:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:759 +msgid "" +"Refer to the corresponding attribute documentation in :class:`IPv4Interface`." +msgstr "" + +#: ../Doc/library/ipaddress.rst:764 +msgid "Other Module Level Functions" +msgstr "" + +#: ../Doc/library/ipaddress.rst:766 +msgid "The module also provides the following module level functions:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:770 +msgid "" +"Represent an address as 4 packed bytes in network (big-endian) order. " +"*address* is an integer representation of an IPv4 IP address. A :exc:" +"`ValueError` is raised if the integer is negative or too large to be an IPv4 " +"IP address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:783 +msgid "" +"Represent an address as 16 packed bytes in network (big-endian) order. " +"*address* is an integer representation of an IPv6 IP address. A :exc:" +"`ValueError` is raised if the integer is negative or too large to be an IPv6 " +"IP address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:791 +msgid "" +"Return an iterator of the summarized network range given the first and last " +"IP addresses. *first* is the first :class:`IPv4Address` or :class:" +"`IPv6Address` in the range and *last* is the last :class:`IPv4Address` or :" +"class:`IPv6Address` in the range. A :exc:`TypeError` is raised if *first* " +"or *last* are not IP addresses or are not of the same version. A :exc:" +"`ValueError` is raised if *last* is not greater than *first* or if *first* " +"address version is not 4 or 6." +msgstr "" + +#: ../Doc/library/ipaddress.rst:807 +msgid "" +"Return an iterator of the collapsed :class:`IPv4Network` or :class:" +"`IPv6Network` objects. *addresses* is an iterator of :class:`IPv4Network` " +"or :class:`IPv6Network` objects. A :exc:`TypeError` is raised if " +"*addresses* contains mixed version objects." +msgstr "" + +#: ../Doc/library/ipaddress.rst:820 +msgid "" +"Return a key suitable for sorting between networks and addresses. Address " +"and Network objects are not sortable by default; they're fundamentally " +"different, so the expression::" +msgstr "" + +#: ../Doc/library/ipaddress.rst:826 +msgid "" +"doesn't make sense. There are some times however, where you may wish to " +"have :mod:`ipaddress` sort these anyway. If you need to do this, you can " +"use this function as the ``key`` argument to :func:`sorted()`." +msgstr "" + +#: ../Doc/library/ipaddress.rst:830 +msgid "*obj* is either a network or address object." +msgstr "" + +#: ../Doc/library/ipaddress.rst:834 +msgid "Custom Exceptions" +msgstr "" + +#: ../Doc/library/ipaddress.rst:836 +msgid "" +"To support more specific error reporting from class constructors, the module " +"defines the following exceptions:" +msgstr "" + +#: ../Doc/library/ipaddress.rst:841 +msgid "Any value error related to the address." +msgstr "" + +#: ../Doc/library/ipaddress.rst:846 +msgid "Any value error related to the netmask." +msgstr "" + +#: ../Doc/library/ipc.rst:5 +msgid "Interprocess Communication and Networking" +msgstr "" + +#: ../Doc/library/ipc.rst:7 +msgid "" +"The modules described in this chapter provide mechanisms for different " +"processes to communicate." +msgstr "" + +#: ../Doc/library/ipc.rst:10 +msgid "" +"Some modules only work for two processes that are on the same machine, e.g. :" +"mod:`signal` and :mod:`mmap`. Other modules support networking protocols " +"that two or more processes can use to communicate across machines." +msgstr "" + +#: ../Doc/library/itertools.rst:2 +msgid ":mod:`itertools` --- Functions creating iterators for efficient looping" +msgstr "" + +#: ../Doc/library/itertools.rst:16 +msgid "" +"This module implements a number of :term:`iterator` building blocks inspired " +"by constructs from APL, Haskell, and SML. Each has been recast in a form " +"suitable for Python." +msgstr "" + +#: ../Doc/library/itertools.rst:20 +msgid "" +"The module standardizes a core set of fast, memory efficient tools that are " +"useful by themselves or in combination. Together, they form an \"iterator " +"algebra\" making it possible to construct specialized tools succinctly and " +"efficiently in pure Python." +msgstr "" + +#: ../Doc/library/itertools.rst:25 +msgid "" +"For instance, SML provides a tabulation tool: ``tabulate(f)`` which produces " +"a sequence ``f(0), f(1), ...``. The same effect can be achieved in Python " +"by combining :func:`map` and :func:`count` to form ``map(f, count())``." +msgstr "" + +#: ../Doc/library/itertools.rst:29 +msgid "" +"These tools and their built-in counterparts also work well with the high-" +"speed functions in the :mod:`operator` module. For example, the " +"multiplication operator can be mapped across two vectors to form an " +"efficient dot-product: ``sum(map(operator.mul, vector1, vector2))``." +msgstr "" + +#: ../Doc/library/itertools.rst:35 +msgid "**Infinite Iterators:**" +msgstr "" + +#: ../Doc/library/itertools.rst:38 ../Doc/library/itertools.rst:48 +#: ../Doc/library/itertools.rst:67 +msgid "Iterator" +msgstr "" + +#: ../Doc/library/itertools.rst:38 ../Doc/library/itertools.rst:48 +#: ../Doc/library/itertools.rst:67 +msgid "Arguments" +msgstr "" + +#: ../Doc/library/itertools.rst:38 ../Doc/library/itertools.rst:48 +#: ../Doc/library/itertools.rst:67 +msgid "Results" +msgstr "" + +#: ../Doc/library/itertools.rst:40 +msgid ":func:`count`" +msgstr "" + +#: ../Doc/library/itertools.rst:40 +msgid "start, [step]" +msgstr "" + +#: ../Doc/library/itertools.rst:40 +msgid "start, start+step, start+2*step, ..." +msgstr "" + +#: ../Doc/library/itertools.rst:40 +msgid "``count(10) --> 10 11 12 13 14 ...``" +msgstr "" + +#: ../Doc/library/itertools.rst:41 +msgid ":func:`cycle`" +msgstr "" + +#: ../Doc/library/itertools.rst:41 +msgid "p" +msgstr "" + +#: ../Doc/library/itertools.rst:41 +msgid "p0, p1, ... plast, p0, p1, ..." +msgstr "" + +#: ../Doc/library/itertools.rst:41 +msgid "``cycle('ABCD') --> A B C D A B C D ...``" +msgstr "" + +#: ../Doc/library/itertools.rst:42 +msgid ":func:`repeat`" +msgstr "" + +#: ../Doc/library/itertools.rst:42 +msgid "elem [,n]" +msgstr "" + +#: ../Doc/library/itertools.rst:42 +msgid "elem, elem, elem, ... endlessly or up to n times" +msgstr "" + +#: ../Doc/library/itertools.rst:42 +msgid "``repeat(10, 3) --> 10 10 10``" +msgstr "" + +#: ../Doc/library/itertools.rst:45 +msgid "**Iterators terminating on the shortest input sequence:**" +msgstr "" + +#: ../Doc/library/itertools.rst:50 +msgid ":func:`accumulate`" +msgstr "" + +#: ../Doc/library/itertools.rst:50 +msgid "p [,func]" +msgstr "" + +#: ../Doc/library/itertools.rst:50 +msgid "p0, p0+p1, p0+p1+p2, ..." +msgstr "" + +#: ../Doc/library/itertools.rst:50 +msgid "``accumulate([1,2,3,4,5]) --> 1 3 6 10 15``" +msgstr "" + +#: ../Doc/library/itertools.rst:51 +msgid ":func:`chain`" +msgstr "" + +#: ../Doc/library/itertools.rst:51 ../Doc/library/itertools.rst:61 +msgid "p, q, ..." +msgstr "" + +#: ../Doc/library/itertools.rst:51 ../Doc/library/itertools.rst:52 +msgid "p0, p1, ... plast, q0, q1, ..." +msgstr "" + +#: ../Doc/library/itertools.rst:51 +msgid "``chain('ABC', 'DEF') --> A B C D E F``" +msgstr "" + +#: ../Doc/library/itertools.rst:52 +msgid ":func:`chain.from_iterable`" +msgstr "" + +#: ../Doc/library/itertools.rst:52 +msgid "iterable" +msgstr "" + +#: ../Doc/library/itertools.rst:52 +msgid "``chain.from_iterable(['ABC', 'DEF']) --> A B C D E F``" +msgstr "" + +#: ../Doc/library/itertools.rst:53 +msgid ":func:`compress`" +msgstr "" + +#: ../Doc/library/itertools.rst:53 +msgid "data, selectors" +msgstr "" + +#: ../Doc/library/itertools.rst:53 +msgid "(d[0] if s[0]), (d[1] if s[1]), ..." +msgstr "" + +#: ../Doc/library/itertools.rst:53 +msgid "``compress('ABCDEF', [1,0,1,0,1,1]) --> A C E F``" +msgstr "" + +#: ../Doc/library/itertools.rst:54 +msgid ":func:`dropwhile`" +msgstr "" + +#: ../Doc/library/itertools.rst:54 ../Doc/library/itertools.rst:55 +#: ../Doc/library/itertools.rst:59 +msgid "pred, seq" +msgstr "" + +#: ../Doc/library/itertools.rst:54 +msgid "seq[n], seq[n+1], starting when pred fails" +msgstr "" + +#: ../Doc/library/itertools.rst:54 +msgid "``dropwhile(lambda x: x<5, [1,4,6,4,1]) --> 6 4 1``" +msgstr "" + +#: ../Doc/library/itertools.rst:55 +msgid ":func:`filterfalse`" +msgstr "" + +#: ../Doc/library/itertools.rst:55 +msgid "elements of seq where pred(elem) is false" +msgstr "" + +#: ../Doc/library/itertools.rst:55 +msgid "``filterfalse(lambda x: x%2, range(10)) --> 0 2 4 6 8``" +msgstr "" + +#: ../Doc/library/itertools.rst:56 +msgid ":func:`groupby`" +msgstr "" + +#: ../Doc/library/itertools.rst:56 +msgid "iterable[, keyfunc]" +msgstr "" + +#: ../Doc/library/itertools.rst:56 +msgid "sub-iterators grouped by value of keyfunc(v)" +msgstr "" + +#: ../Doc/library/itertools.rst:57 +msgid ":func:`islice`" +msgstr "" + +#: ../Doc/library/itertools.rst:57 +msgid "seq, [start,] stop [, step]" +msgstr "" + +#: ../Doc/library/itertools.rst:57 +msgid "elements from seq[start:stop:step]" +msgstr "" + +#: ../Doc/library/itertools.rst:57 +msgid "``islice('ABCDEFG', 2, None) --> C D E F G``" +msgstr "" + +#: ../Doc/library/itertools.rst:58 +msgid ":func:`starmap`" +msgstr "" + +#: ../Doc/library/itertools.rst:58 +msgid "func, seq" +msgstr "" + +#: ../Doc/library/itertools.rst:58 +msgid "func(\\*seq[0]), func(\\*seq[1]), ..." +msgstr "" + +#: ../Doc/library/itertools.rst:58 +msgid "``starmap(pow, [(2,5), (3,2), (10,3)]) --> 32 9 1000``" +msgstr "" + +#: ../Doc/library/itertools.rst:59 +msgid ":func:`takewhile`" +msgstr "" + +#: ../Doc/library/itertools.rst:59 +msgid "seq[0], seq[1], until pred fails" +msgstr "" + +#: ../Doc/library/itertools.rst:59 +msgid "``takewhile(lambda x: x<5, [1,4,6,4,1]) --> 1 4``" +msgstr "" + +#: ../Doc/library/itertools.rst:60 +msgid ":func:`tee`" +msgstr "" + +#: ../Doc/library/itertools.rst:60 +msgid "it, n" +msgstr "" + +#: ../Doc/library/itertools.rst:60 +msgid "it1, it2, ... itn splits one iterator into n" +msgstr "" + +#: ../Doc/library/itertools.rst:61 +msgid ":func:`zip_longest`" +msgstr "" + +#: ../Doc/library/itertools.rst:61 +msgid "(p[0], q[0]), (p[1], q[1]), ..." +msgstr "" + +#: ../Doc/library/itertools.rst:61 +msgid "``zip_longest('ABCD', 'xy', fillvalue='-') --> Ax By C- D-``" +msgstr "" + +#: ../Doc/library/itertools.rst:64 +msgid "**Combinatoric generators:**" +msgstr "" + +#: ../Doc/library/itertools.rst:69 +msgid ":func:`product`" +msgstr "" + +#: ../Doc/library/itertools.rst:69 +msgid "p, q, ... [repeat=1]" +msgstr "" + +#: ../Doc/library/itertools.rst:69 +msgid "cartesian product, equivalent to a nested for-loop" +msgstr "" + +#: ../Doc/library/itertools.rst:70 +msgid ":func:`permutations`" +msgstr "" + +#: ../Doc/library/itertools.rst:70 +msgid "p[, r]" +msgstr "" + +#: ../Doc/library/itertools.rst:70 +msgid "r-length tuples, all possible orderings, no repeated elements" +msgstr "" + +#: ../Doc/library/itertools.rst:71 +msgid ":func:`combinations`" +msgstr "" + +#: ../Doc/library/itertools.rst:71 ../Doc/library/itertools.rst:72 +msgid "p, r" +msgstr "" + +#: ../Doc/library/itertools.rst:71 +msgid "r-length tuples, in sorted order, no repeated elements" +msgstr "" + +#: ../Doc/library/itertools.rst:72 +msgid ":func:`combinations_with_replacement`" +msgstr "" + +#: ../Doc/library/itertools.rst:72 +msgid "r-length tuples, in sorted order, with repeated elements" +msgstr "" + +#: ../Doc/library/itertools.rst:73 +msgid "``product('ABCD', repeat=2)``" +msgstr "" + +#: ../Doc/library/itertools.rst:73 +msgid "``AA AB AC AD BA BB BC BD CA CB CC CD DA DB DC DD``" +msgstr "" + +#: ../Doc/library/itertools.rst:74 +msgid "``permutations('ABCD', 2)``" +msgstr "" + +#: ../Doc/library/itertools.rst:74 +msgid "``AB AC AD BA BC BD CA CB CD DA DB DC``" +msgstr "" + +#: ../Doc/library/itertools.rst:75 +msgid "``combinations('ABCD', 2)``" +msgstr "" + +#: ../Doc/library/itertools.rst:75 +msgid "``AB AC AD BC BD CD``" +msgstr "" + +#: ../Doc/library/itertools.rst:76 +msgid "``combinations_with_replacement('ABCD', 2)``" +msgstr "" + +#: ../Doc/library/itertools.rst:76 +msgid "``AA AB AC AD BB BC BD CC CD DD``" +msgstr "" + +#: ../Doc/library/itertools.rst:83 +msgid "Itertool functions" +msgstr "" + +#: ../Doc/library/itertools.rst:85 +msgid "" +"The following module functions all construct and return iterators. Some " +"provide streams of infinite length, so they should only be accessed by " +"functions or loops that truncate the stream." +msgstr "" + +#: ../Doc/library/itertools.rst:91 +msgid "" +"Make an iterator that returns accumulated sums, or accumulated results of " +"other binary functions (specified via the optional *func* argument). If " +"*func* is supplied, it should be a function of two arguments. Elements of " +"the input *iterable* may be any type that can be accepted as arguments to " +"*func*. (For example, with the default operation of addition, elements may " +"be any addable type including :class:`~decimal.Decimal` or :class:" +"`~fractions.Fraction`.) If the input iterable is empty, the output iterable " +"will also be empty." +msgstr "" + +#: ../Doc/library/itertools.rst:117 +msgid "" +"There are a number of uses for the *func* argument. It can be set to :func:" +"`min` for a running minimum, :func:`max` for a running maximum, or :func:" +"`operator.mul` for a running product. Amortization tables can be built by " +"accumulating interest and applying payments. First-order `recurrence " +"relations `_ can be " +"modeled by supplying the initial value in the iterable and using only the " +"accumulated total in *func* argument::" +msgstr "" + +#: ../Doc/library/itertools.rst:147 +msgid "" +"See :func:`functools.reduce` for a similar function that returns only the " +"final accumulated value." +msgstr "" + +#: ../Doc/library/itertools.rst:152 +msgid "Added the optional *func* parameter." +msgstr "" + +#: ../Doc/library/itertools.rst:157 +msgid "" +"Make an iterator that returns elements from the first iterable until it is " +"exhausted, then proceeds to the next iterable, until all of the iterables " +"are exhausted. Used for treating consecutive sequences as a single " +"sequence. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:171 +msgid "" +"Alternate constructor for :func:`chain`. Gets chained inputs from a single " +"iterable argument that is evaluated lazily. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:183 +msgid "Return *r* length subsequences of elements from the input *iterable*." +msgstr "" + +#: ../Doc/library/itertools.rst:185 ../Doc/library/itertools.rst:234 +msgid "" +"Combinations are emitted in lexicographic sort order. So, if the input " +"*iterable* is sorted, the combination tuples will be produced in sorted " +"order." +msgstr "" + +#: ../Doc/library/itertools.rst:189 +msgid "" +"Elements are treated as unique based on their position, not on their value. " +"So if the input elements are unique, there will be no repeat values in each " +"combination." +msgstr "" + +#: ../Doc/library/itertools.rst:215 +msgid "" +"The code for :func:`combinations` can be also expressed as a subsequence of :" +"func:`permutations` after filtering entries where the elements are not in " +"sorted order (according to their position in the input pool)::" +msgstr "" + +#: ../Doc/library/itertools.rst:226 +msgid "" +"The number of items returned is ``n! / r! / (n-r)!`` when ``0 <= r <= n`` or " +"zero when ``r > n``." +msgstr "" + +#: ../Doc/library/itertools.rst:231 +msgid "" +"Return *r* length subsequences of elements from the input *iterable* " +"allowing individual elements to be repeated more than once." +msgstr "" + +#: ../Doc/library/itertools.rst:238 +msgid "" +"Elements are treated as unique based on their position, not on their value. " +"So if the input elements are unique, the generated combinations will also be " +"unique." +msgstr "" + +#: ../Doc/library/itertools.rst:261 +msgid "" +"The code for :func:`combinations_with_replacement` can be also expressed as " +"a subsequence of :func:`product` after filtering entries where the elements " +"are not in sorted order (according to their position in the input pool)::" +msgstr "" + +#: ../Doc/library/itertools.rst:272 +msgid "" +"The number of items returned is ``(n+r-1)! / r! / (n-1)!`` when ``n > 0``." +msgstr "" + +#: ../Doc/library/itertools.rst:279 +msgid "" +"Make an iterator that filters elements from *data* returning only those that " +"have a corresponding element in *selectors* that evaluates to ``True``. " +"Stops when either the *data* or *selectors* iterables has been exhausted. " +"Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:293 +msgid "" +"Make an iterator that returns evenly spaced values starting with number " +"*start*. Often used as an argument to :func:`map` to generate consecutive " +"data points. Also, used with :func:`zip` to add sequence numbers. Roughly " +"equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:305 +msgid "" +"When counting with floating point numbers, better accuracy can sometimes be " +"achieved by substituting multiplicative code such as: ``(start + step * i " +"for i in count())``." +msgstr "" + +#: ../Doc/library/itertools.rst:309 +msgid "Added *step* argument and allowed non-integer arguments." +msgstr "" + +#: ../Doc/library/itertools.rst:314 +msgid "" +"Make an iterator returning elements from the iterable and saving a copy of " +"each. When the iterable is exhausted, return elements from the saved copy. " +"Repeats indefinitely. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:328 +msgid "" +"Note, this member of the toolkit may require significant auxiliary storage " +"(depending on the length of the iterable)." +msgstr "" + +#: ../Doc/library/itertools.rst:334 +msgid "" +"Make an iterator that drops elements from the iterable as long as the " +"predicate is true; afterwards, returns every element. Note, the iterator " +"does not produce *any* output until the predicate first becomes false, so it " +"may have a lengthy start-up time. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:351 +msgid "" +"Make an iterator that filters elements from iterable returning only those " +"for which the predicate is ``False``. If *predicate* is ``None``, return the " +"items that are false. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:366 +msgid "" +"Make an iterator that returns consecutive keys and groups from the " +"*iterable*. The *key* is a function computing a key value for each element. " +"If not specified or is ``None``, *key* defaults to an identity function and " +"returns the element unchanged. Generally, the iterable needs to already be " +"sorted on the same key function." +msgstr "" + +#: ../Doc/library/itertools.rst:372 +msgid "" +"The operation of :func:`groupby` is similar to the ``uniq`` filter in Unix. " +"It generates a break or new group every time the value of the key function " +"changes (which is why it is usually necessary to have sorted the data using " +"the same key function). That behavior differs from SQL's GROUP BY which " +"aggregates common elements regardless of their input order." +msgstr "" + +#: ../Doc/library/itertools.rst:378 +msgid "" +"The returned group is itself an iterator that shares the underlying iterable " +"with :func:`groupby`. Because the source is shared, when the :func:" +"`groupby` object is advanced, the previous group is no longer visible. So, " +"if that data is needed later, it should be stored as a list::" +msgstr "" + +#: ../Doc/library/itertools.rst:390 +msgid ":func:`groupby` is roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:422 +msgid "" +"Make an iterator that returns selected elements from the iterable. If " +"*start* is non-zero, then elements from the iterable are skipped until start " +"is reached. Afterward, elements are returned consecutively unless *step* is " +"set higher than one which results in items being skipped. If *stop* is " +"``None``, then iteration continues until the iterator is exhausted, if at " +"all; otherwise, it stops at the specified position. Unlike regular " +"slicing, :func:`islice` does not support negative values for *start*, " +"*stop*, or *step*. Can be used to extract related fields from data where " +"the internal structure has been flattened (for example, a multi-line report " +"may list a name field on every third line). Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:448 +msgid "" +"If *start* is ``None``, then iteration starts at zero. If *step* is " +"``None``, then the step defaults to one." +msgstr "" + +#: ../Doc/library/itertools.rst:454 +msgid "" +"Return successive *r* length permutations of elements in the *iterable*." +msgstr "" + +#: ../Doc/library/itertools.rst:456 +msgid "" +"If *r* is not specified or is ``None``, then *r* defaults to the length of " +"the *iterable* and all possible full-length permutations are generated." +msgstr "" + +#: ../Doc/library/itertools.rst:460 +msgid "" +"Permutations are emitted in lexicographic sort order. So, if the input " +"*iterable* is sorted, the permutation tuples will be produced in sorted " +"order." +msgstr "" + +#: ../Doc/library/itertools.rst:464 +msgid "" +"Elements are treated as unique based on their position, not on their value. " +"So if the input elements are unique, there will be no repeat values in each " +"permutation." +msgstr "" + +#: ../Doc/library/itertools.rst:495 +msgid "" +"The code for :func:`permutations` can be also expressed as a subsequence of :" +"func:`product`, filtered to exclude entries with repeated elements (those " +"from the same position in the input pool)::" +msgstr "" + +#: ../Doc/library/itertools.rst:507 +msgid "" +"The number of items returned is ``n! / (n-r)!`` when ``0 <= r <= n`` or zero " +"when ``r > n``." +msgstr "" + +#: ../Doc/library/itertools.rst:512 +msgid "Cartesian product of input iterables." +msgstr "" + +#: ../Doc/library/itertools.rst:514 +msgid "" +"Roughly equivalent to nested for-loops in a generator expression. For " +"example, ``product(A, B)`` returns the same as ``((x,y) for x in A for y in " +"B)``." +msgstr "" + +#: ../Doc/library/itertools.rst:517 +msgid "" +"The nested loops cycle like an odometer with the rightmost element advancing " +"on every iteration. This pattern creates a lexicographic ordering so that " +"if the input's iterables are sorted, the product tuples are emitted in " +"sorted order." +msgstr "" + +#: ../Doc/library/itertools.rst:522 +msgid "" +"To compute the product of an iterable with itself, specify the number of " +"repetitions with the optional *repeat* keyword argument. For example, " +"``product(A, repeat=4)`` means the same as ``product(A, A, A, A)``." +msgstr "" + +#: ../Doc/library/itertools.rst:526 +msgid "" +"This function is roughly equivalent to the following code, except that the " +"actual implementation does not build up intermediate results in memory::" +msgstr "" + +#: ../Doc/library/itertools.rst:542 +msgid "" +"Make an iterator that returns *object* over and over again. Runs " +"indefinitely unless the *times* argument is specified. Used as argument to :" +"func:`map` for invariant parameters to the called function. Also used with :" +"func:`zip` to create an invariant part of a tuple record." +msgstr "" + +#: ../Doc/library/itertools.rst:558 +msgid "" +"A common use for *repeat* is to supply a stream of constant values to *map* " +"or *zip*::" +msgstr "" + +#: ../Doc/library/itertools.rst:566 +msgid "" +"Make an iterator that computes the function using arguments obtained from " +"the iterable. Used instead of :func:`map` when argument parameters are " +"already grouped in tuples from a single iterable (the data has been \"pre-" +"zipped\"). The difference between :func:`map` and :func:`starmap` parallels " +"the distinction between ``function(a,b)`` and ``function(*c)``. Roughly " +"equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:580 +msgid "" +"Make an iterator that returns elements from the iterable as long as the " +"predicate is true. Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:594 +msgid "Return *n* independent iterators from a single iterable." +msgstr "" + +#: ../Doc/library/itertools.rst:596 +msgid "" +"The following Python code helps explain what *tee* does (although the actual " +"implementation is more complex and uses only a single underlying :abbr:`FIFO " +"(first-in, first-out)` queue)." +msgstr "" + +#: ../Doc/library/itertools.rst:617 +msgid "" +"Once :func:`tee` has made a split, the original *iterable* should not be " +"used anywhere else; otherwise, the *iterable* could get advanced without the " +"tee objects being informed." +msgstr "" + +#: ../Doc/library/itertools.rst:621 +msgid "" +"This itertool may require significant auxiliary storage (depending on how " +"much temporary data needs to be stored). In general, if one iterator uses " +"most or all of the data before another iterator starts, it is faster to use :" +"func:`list` instead of :func:`tee`." +msgstr "" + +#: ../Doc/library/itertools.rst:629 +msgid "" +"Make an iterator that aggregates elements from each of the iterables. If the " +"iterables are of uneven length, missing values are filled-in with " +"*fillvalue*. Iteration continues until the longest iterable is exhausted. " +"Roughly equivalent to::" +msgstr "" + +#: ../Doc/library/itertools.rst:654 +msgid "" +"If one of the iterables is potentially infinite, then the :func:" +"`zip_longest` function should be wrapped with something that limits the " +"number of calls (for example :func:`islice` or :func:`takewhile`). If not " +"specified, *fillvalue* defaults to ``None``." +msgstr "" + +#: ../Doc/library/itertools.rst:663 +msgid "Itertools Recipes" +msgstr "" + +#: ../Doc/library/itertools.rst:665 +msgid "" +"This section shows recipes for creating an extended toolset using the " +"existing itertools as building blocks." +msgstr "" + +#: ../Doc/library/itertools.rst:668 +msgid "" +"The extended tools offer the same high performance as the underlying " +"toolset. The superior memory performance is kept by processing elements one " +"at a time rather than bringing the whole iterable into memory all at once. " +"Code volume is kept small by linking the tools together in a functional " +"style which helps eliminate temporary variables. High speed is retained by " +"preferring \"vectorized\" building blocks over the use of for-loops and :" +"term:`generator`\\s which incur interpreter overhead." +msgstr "" + +#: ../Doc/library/itertools.rst:861 +msgid "" +"Note, many of the above recipes can be optimized by replacing global lookups " +"with local variables defined as default values. For example, the " +"*dotproduct* recipe can be written as::" +msgstr "" + +#: ../Doc/library/json.rst:2 +msgid ":mod:`json` --- JSON encoder and decoder" +msgstr "" + +#: ../Doc/library/json.rst:10 +msgid "**Source code:** :source:`Lib/json/__init__.py`" +msgstr "" + +#: ../Doc/library/json.rst:14 +msgid "" +"`JSON (JavaScript Object Notation) `_, specified by :rfc:" +"`7159` (which obsoletes :rfc:`4627`) and by `ECMA-404 `_, is a lightweight " +"data interchange format inspired by `JavaScript `_ object literal syntax (although it is not a strict subset " +"of JavaScript [#rfc-errata]_ )." +msgstr "" + +#: ../Doc/library/json.rst:21 +msgid "" +":mod:`json` exposes an API familiar to users of the standard library :mod:" +"`marshal` and :mod:`pickle` modules." +msgstr "" + +#: ../Doc/library/json.rst:24 +msgid "Encoding basic Python object hierarchies::" +msgstr "" + +#: ../Doc/library/json.rst:43 +msgid "Compact encoding::" +msgstr "" + +#: ../Doc/library/json.rst:49 +msgid "Pretty printing::" +msgstr "" + +#: ../Doc/library/json.rst:58 +msgid "Decoding JSON::" +msgstr "" + +#: ../Doc/library/json.rst:70 +msgid "Specializing JSON object decoding::" +msgstr "" + +#: ../Doc/library/json.rst:85 +msgid "Extending :class:`JSONEncoder`::" +msgstr "" + +#: ../Doc/library/json.rst:105 +msgid "Using :mod:`json.tool` from the shell to validate and pretty-print::" +msgstr "" + +#: ../Doc/library/json.rst:114 +msgid "See :ref:`json-commandline` for detailed documentation." +msgstr "" + +#: ../Doc/library/json.rst:120 +msgid "" +"JSON is a subset of `YAML `_ 1.2. The JSON produced by " +"this module's default settings (in particular, the default *separators* " +"value) is also a subset of YAML 1.0 and 1.1. This module can thus also be " +"used as a YAML serializer." +msgstr "" + +#: ../Doc/library/json.rst:127 +msgid "Basic Usage" +msgstr "" + +#: ../Doc/library/json.rst:134 +msgid "" +"Serialize *obj* as a JSON formatted stream to *fp* (a ``.write()``-" +"supporting :term:`file-like object`) using this :ref:`conversion table `." +msgstr "" + +#: ../Doc/library/json.rst:138 +msgid "" +"If *skipkeys* is true (default: ``False``), then dict keys that are not of a " +"basic type (:class:`str`, :class:`int`, :class:`float`, :class:`bool`, " +"``None``) will be skipped instead of raising a :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/json.rst:142 +msgid "" +"The :mod:`json` module always produces :class:`str` objects, not :class:" +"`bytes` objects. Therefore, ``fp.write()`` must support :class:`str` input." +msgstr "" + +#: ../Doc/library/json.rst:146 ../Doc/library/json.rst:413 +msgid "" +"If *ensure_ascii* is true (the default), the output is guaranteed to have " +"all incoming non-ASCII characters escaped. If *ensure_ascii* is false, " +"these characters will be output as-is." +msgstr "" + +#: ../Doc/library/json.rst:150 +msgid "" +"If *check_circular* is false (default: ``True``), then the circular " +"reference check for container types will be skipped and a circular reference " +"will result in an :exc:`OverflowError` (or worse)." +msgstr "" + +#: ../Doc/library/json.rst:154 +msgid "" +"If *allow_nan* is false (default: ``True``), then it will be a :exc:" +"`ValueError` to serialize out of range :class:`float` values (``nan``, " +"``inf``, ``-inf``) in strict compliance of the JSON specification. If " +"*allow_nan* is true, their JavaScript equivalents (``NaN``, ``Infinity``, ``-" +"Infinity``) will be used." +msgstr "" + +#: ../Doc/library/json.rst:160 ../Doc/library/json.rst:432 +msgid "" +"If *indent* is a non-negative integer or string, then JSON array elements " +"and object members will be pretty-printed with that indent level. An indent " +"level of 0, negative, or ``\"\"`` will only insert newlines. ``None`` (the " +"default) selects the most compact representation. Using a positive integer " +"indent indents that many spaces per level. If *indent* is a string (such as " +"``\"\\t\"``), that string is used to indent each level." +msgstr "" + +#: ../Doc/library/json.rst:167 ../Doc/library/json.rst:439 +msgid "Allow strings for *indent* in addition to integers." +msgstr "" + +#: ../Doc/library/json.rst:170 ../Doc/library/json.rst:442 +msgid "" +"If specified, *separators* should be an ``(item_separator, key_separator)`` " +"tuple. The default is ``(', ', ': ')`` if *indent* is ``None`` and ``(',', " +"': ')`` otherwise. To get the most compact JSON representation, you should " +"specify ``(',', ':')`` to eliminate whitespace." +msgstr "" + +#: ../Doc/library/json.rst:175 ../Doc/library/json.rst:447 +msgid "Use ``(',', ': ')`` as default if *indent* is not ``None``." +msgstr "" + +#: ../Doc/library/json.rst:178 ../Doc/library/json.rst:450 +msgid "" +"If specified, *default* should be a function that gets called for objects " +"that can't otherwise be serialized. It should return a JSON encodable " +"version of the object or raise a :exc:`TypeError`. If not specified, :exc:" +"`TypeError` is raised." +msgstr "" + +#: ../Doc/library/json.rst:183 +msgid "" +"If *sort_keys* is true (default: ``False``), then the output of dictionaries " +"will be sorted by key." +msgstr "" + +#: ../Doc/library/json.rst:186 +msgid "" +"To use a custom :class:`JSONEncoder` subclass (e.g. one that overrides the :" +"meth:`default` method to serialize additional types), specify it with the " +"*cls* kwarg; otherwise :class:`JSONEncoder` is used." +msgstr "" + +#: ../Doc/library/json.rst:190 ../Doc/library/json.rst:266 +msgid "" +"All optional parameters are now :ref:`keyword-only `." +msgstr "" + +#: ../Doc/library/json.rst:199 +msgid "" +"Serialize *obj* to a JSON formatted :class:`str` using this :ref:`conversion " +"table `. The arguments have the same meaning as in :func:" +"`dump`." +msgstr "" + +#: ../Doc/library/json.rst:205 +msgid "" +"Unlike :mod:`pickle` and :mod:`marshal`, JSON is not a framed protocol, so " +"trying to serialize multiple objects with repeated calls to :func:`dump` " +"using the same *fp* will result in an invalid JSON file." +msgstr "" + +#: ../Doc/library/json.rst:211 +msgid "" +"Keys in key/value pairs of JSON are always of the type :class:`str`. When a " +"dictionary is converted into JSON, all the keys of the dictionary are " +"coerced to strings. As a result of this, if a dictionary is converted into " +"JSON and then back into a dictionary, the dictionary may not equal the " +"original one. That is, ``loads(dumps(x)) != x`` if x has non-string keys." +msgstr "" + +#: ../Doc/library/json.rst:220 +msgid "" +"Deserialize *fp* (a ``.read()``-supporting :term:`file-like object` " +"containing a JSON document) to a Python object using this :ref:`conversion " +"table `." +msgstr "" + +#: ../Doc/library/json.rst:224 +msgid "" +"*object_hook* is an optional function that will be called with the result of " +"any object literal decoded (a :class:`dict`). The return value of " +"*object_hook* will be used instead of the :class:`dict`. This feature can " +"be used to implement custom decoders (e.g. `JSON-RPC `_ class hinting)." +msgstr "" + +#: ../Doc/library/json.rst:230 +msgid "" +"*object_pairs_hook* is an optional function that will be called with the " +"result of any object literal decoded with an ordered list of pairs. The " +"return value of *object_pairs_hook* will be used instead of the :class:" +"`dict`. This feature can be used to implement custom decoders that rely on " +"the order that the key and value pairs are decoded (for example, :func:" +"`collections.OrderedDict` will remember the order of insertion). If " +"*object_hook* is also defined, the *object_pairs_hook* takes priority." +msgstr "" + +#: ../Doc/library/json.rst:238 ../Doc/library/json.rst:328 +msgid "Added support for *object_pairs_hook*." +msgstr "" + +#: ../Doc/library/json.rst:241 ../Doc/library/json.rst:331 +msgid "" +"*parse_float*, if specified, will be called with the string of every JSON " +"float to be decoded. By default, this is equivalent to ``float(num_str)``. " +"This can be used to use another datatype or parser for JSON floats (e.g. :" +"class:`decimal.Decimal`)." +msgstr "" + +#: ../Doc/library/json.rst:246 ../Doc/library/json.rst:336 +msgid "" +"*parse_int*, if specified, will be called with the string of every JSON int " +"to be decoded. By default, this is equivalent to ``int(num_str)``. This " +"can be used to use another datatype or parser for JSON integers (e.g. :class:" +"`float`)." +msgstr "" + +#: ../Doc/library/json.rst:251 +msgid "" +"*parse_constant*, if specified, will be called with one of the following " +"strings: ``'-Infinity'``, ``'Infinity'``, ``'NaN'``. This can be used to " +"raise an exception if invalid JSON numbers are encountered." +msgstr "" + +#: ../Doc/library/json.rst:256 +msgid "*parse_constant* doesn't get called on 'null', 'true', 'false' anymore." +msgstr "" + +#: ../Doc/library/json.rst:259 +msgid "" +"To use a custom :class:`JSONDecoder` subclass, specify it with the ``cls`` " +"kwarg; otherwise :class:`JSONDecoder` is used. Additional keyword arguments " +"will be passed to the constructor of the class." +msgstr "" + +#: ../Doc/library/json.rst:263 ../Doc/library/json.rst:278 +#: ../Doc/library/json.rst:351 +msgid "" +"If the data being deserialized is not a valid JSON document, a :exc:" +"`JSONDecodeError` will be raised." +msgstr "" + +#: ../Doc/library/json.rst:271 +msgid "" +"Deserialize *s* (a :class:`str`, :class:`bytes` or :class:`bytearray` " +"instance containing a JSON document) to a Python object using this :ref:" +"`conversion table `." +msgstr "" + +#: ../Doc/library/json.rst:275 +msgid "" +"The other arguments have the same meaning as in :func:`load`, except " +"*encoding* which is ignored and deprecated." +msgstr "" + +#: ../Doc/library/json.rst:282 +msgid "Encoders and Decoders" +msgstr "" + +#: ../Doc/library/json.rst:286 +msgid "Simple JSON decoder." +msgstr "" + +#: ../Doc/library/json.rst:288 +msgid "Performs the following translations in decoding by default:" +msgstr "" + +#: ../Doc/library/json.rst:293 ../Doc/library/json.rst:384 +msgid "JSON" +msgstr "" + +#: ../Doc/library/json.rst:293 ../Doc/library/json.rst:384 +msgid "Python" +msgstr "" + +#: ../Doc/library/json.rst:295 ../Doc/library/json.rst:386 +msgid "object" +msgstr "" + +#: ../Doc/library/json.rst:295 ../Doc/library/json.rst:386 +msgid "dict" +msgstr "" + +#: ../Doc/library/json.rst:297 ../Doc/library/json.rst:388 +msgid "array" +msgstr "" + +#: ../Doc/library/json.rst:297 +msgid "list" +msgstr "" + +#: ../Doc/library/json.rst:299 ../Doc/library/json.rst:390 +#: ../Doc/library/turtle.rst:1796 ../Doc/library/turtle.rst:1797 +#: ../Doc/library/turtle.rst:1809 ../Doc/library/turtle.rst:1810 +msgid "string" +msgstr "" + +#: ../Doc/library/json.rst:299 ../Doc/library/json.rst:390 +msgid "str" +msgstr "" + +#: ../Doc/library/json.rst:301 +msgid "number (int)" +msgstr "" + +#: ../Doc/library/json.rst:303 +msgid "number (real)" +msgstr "" + +#: ../Doc/library/json.rst:305 ../Doc/library/json.rst:394 +msgid "true" +msgstr "" + +#: ../Doc/library/json.rst:305 ../Doc/library/json.rst:394 +msgid "True" +msgstr "" + +#: ../Doc/library/json.rst:307 ../Doc/library/json.rst:396 +msgid "false" +msgstr "" + +#: ../Doc/library/json.rst:307 ../Doc/library/json.rst:396 +msgid "False" +msgstr "" + +#: ../Doc/library/json.rst:309 ../Doc/library/json.rst:398 +msgid "null" +msgstr "" + +#: ../Doc/library/json.rst:309 ../Doc/library/json.rst:398 +#: ../Doc/library/string.rst:417 ../Doc/library/string.rst:444 +#: ../Doc/library/string.rst:505 +msgid "None" +msgstr "" + +#: ../Doc/library/json.rst:312 +msgid "" +"It also understands ``NaN``, ``Infinity``, and ``-Infinity`` as their " +"corresponding ``float`` values, which is outside the JSON spec." +msgstr "" + +#: ../Doc/library/json.rst:315 +msgid "" +"*object_hook*, if specified, will be called with the result of every JSON " +"object decoded and its return value will be used in place of the given :" +"class:`dict`. This can be used to provide custom deserializations (e.g. to " +"support JSON-RPC class hinting)." +msgstr "" + +#: ../Doc/library/json.rst:320 +msgid "" +"*object_pairs_hook*, if specified will be called with the result of every " +"JSON object decoded with an ordered list of pairs. The return value of " +"*object_pairs_hook* will be used instead of the :class:`dict`. This feature " +"can be used to implement custom decoders that rely on the order that the key " +"and value pairs are decoded (for example, :func:`collections.OrderedDict` " +"will remember the order of insertion). If *object_hook* is also defined, the " +"*object_pairs_hook* takes priority." +msgstr "" + +#: ../Doc/library/json.rst:341 +msgid "" +"*parse_constant*, if specified, will be called with one of the following " +"strings: ``'-Infinity'``, ``'Infinity'``, ``'NaN'``, ``'null'``, ``'true'``, " +"``'false'``. This can be used to raise an exception if invalid JSON numbers " +"are encountered." +msgstr "" + +#: ../Doc/library/json.rst:346 +msgid "" +"If *strict* is false (``True`` is the default), then control characters will " +"be allowed inside strings. Control characters in this context are those " +"with character codes in the 0-31 range, including ``'\\t'`` (tab), " +"``'\\n'``, ``'\\r'`` and ``'\\0'``." +msgstr "" + +#: ../Doc/library/json.rst:354 ../Doc/library/json.rst:455 +msgid "All parameters are now :ref:`keyword-only `." +msgstr "" + +#: ../Doc/library/json.rst:359 +msgid "" +"Return the Python representation of *s* (a :class:`str` instance containing " +"a JSON document)." +msgstr "" + +#: ../Doc/library/json.rst:362 +msgid "" +":exc:`JSONDecodeError` will be raised if the given JSON document is not " +"valid." +msgstr "" + +#: ../Doc/library/json.rst:367 +msgid "" +"Decode a JSON document from *s* (a :class:`str` beginning with a JSON " +"document) and return a 2-tuple of the Python representation and the index in " +"*s* where the document ended." +msgstr "" + +#: ../Doc/library/json.rst:371 +msgid "" +"This can be used to decode a JSON document from a string that may have " +"extraneous data at the end." +msgstr "" + +#: ../Doc/library/json.rst:377 +msgid "Extensible JSON encoder for Python data structures." +msgstr "" + +#: ../Doc/library/json.rst:379 +msgid "Supports the following objects and types by default:" +msgstr "" + +#: ../Doc/library/json.rst:388 +msgid "list, tuple" +msgstr "" + +#: ../Doc/library/json.rst:392 +msgid "int, float, int- & float-derived Enums" +msgstr "" + +#: ../Doc/library/json.rst:392 +msgid "number" +msgstr "" + +#: ../Doc/library/json.rst:401 +msgid "Added support for int- and float-derived Enum classes." +msgstr "" + +#: ../Doc/library/json.rst:404 +msgid "" +"To extend this to recognize other objects, subclass and implement a :meth:" +"`default` method with another method that returns a serializable object for " +"``o`` if possible, otherwise it should call the superclass implementation " +"(to raise :exc:`TypeError`)." +msgstr "" + +#: ../Doc/library/json.rst:409 +msgid "" +"If *skipkeys* is false (the default), then it is a :exc:`TypeError` to " +"attempt encoding of keys that are not str, int, float or None. If " +"*skipkeys* is true, such items are simply skipped." +msgstr "" + +#: ../Doc/library/json.rst:417 +msgid "" +"If *check_circular* is true (the default), then lists, dicts, and custom " +"encoded objects will be checked for circular references during encoding to " +"prevent an infinite recursion (which would cause an :exc:`OverflowError`). " +"Otherwise, no such check takes place." +msgstr "" + +#: ../Doc/library/json.rst:422 +msgid "" +"If *allow_nan* is true (the default), then ``NaN``, ``Infinity``, and ``-" +"Infinity`` will be encoded as such. This behavior is not JSON specification " +"compliant, but is consistent with most JavaScript based encoders and " +"decoders. Otherwise, it will be a :exc:`ValueError` to encode such floats." +msgstr "" + +#: ../Doc/library/json.rst:428 +msgid "" +"If *sort_keys* is true (default: ``False``), then the output of dictionaries " +"will be sorted by key; this is useful for regression tests to ensure that " +"JSON serializations can be compared on a day-to-day basis." +msgstr "" + +#: ../Doc/library/json.rst:461 +msgid "" +"Implement this method in a subclass such that it returns a serializable " +"object for *o*, or calls the base implementation (to raise a :exc:" +"`TypeError`)." +msgstr "" + +#: ../Doc/library/json.rst:465 +msgid "" +"For example, to support arbitrary iterators, you could implement default " +"like this::" +msgstr "" + +#: ../Doc/library/json.rst:481 +msgid "" +"Return a JSON string representation of a Python data structure, *o*. For " +"example::" +msgstr "" + +#: ../Doc/library/json.rst:490 +msgid "" +"Encode the given object, *o*, and yield each string representation as " +"available. For example::" +msgstr "" + +#: ../Doc/library/json.rst:502 +msgid "Subclass of :exc:`ValueError` with the following additional attributes:" +msgstr "" + +#: ../Doc/library/json.rst:506 ../Doc/library/re.rst:798 +msgid "The unformatted error message." +msgstr "" + +#: ../Doc/library/json.rst:510 +msgid "The JSON document being parsed." +msgstr "" + +#: ../Doc/library/json.rst:514 +msgid "The start index of *doc* where parsing failed." +msgstr "" + +#: ../Doc/library/json.rst:518 ../Doc/library/re.rst:810 +msgid "The line corresponding to *pos*." +msgstr "" + +#: ../Doc/library/json.rst:522 ../Doc/library/re.rst:814 +msgid "The column corresponding to *pos*." +msgstr "" + +#: ../Doc/library/json.rst:528 +msgid "Standard Compliance and Interoperability" +msgstr "" + +#: ../Doc/library/json.rst:530 +msgid "" +"The JSON format is specified by :rfc:`7159` and by `ECMA-404 `_. This section " +"details this module's level of compliance with the RFC. For simplicity, :" +"class:`JSONEncoder` and :class:`JSONDecoder` subclasses, and parameters " +"other than those explicitly mentioned, are not considered." +msgstr "" + +#: ../Doc/library/json.rst:536 +msgid "" +"This module does not comply with the RFC in a strict fashion, implementing " +"some extensions that are valid JavaScript but not valid JSON. In particular:" +msgstr "" + +#: ../Doc/library/json.rst:539 +msgid "Infinite and NaN number values are accepted and output;" +msgstr "" + +#: ../Doc/library/json.rst:540 +msgid "" +"Repeated names within an object are accepted, and only the value of the last " +"name-value pair is used." +msgstr "" + +#: ../Doc/library/json.rst:543 +msgid "" +"Since the RFC permits RFC-compliant parsers to accept input texts that are " +"not RFC-compliant, this module's deserializer is technically RFC-compliant " +"under default settings." +msgstr "" + +#: ../Doc/library/json.rst:548 +msgid "Character Encodings" +msgstr "" + +#: ../Doc/library/json.rst:550 +msgid "" +"The RFC requires that JSON be represented using either UTF-8, UTF-16, or " +"UTF-32, with UTF-8 being the recommended default for maximum " +"interoperability." +msgstr "" + +#: ../Doc/library/json.rst:553 +msgid "" +"As permitted, though not required, by the RFC, this module's serializer sets " +"*ensure_ascii=True* by default, thus escaping the output so that the " +"resulting strings only contain ASCII characters." +msgstr "" + +#: ../Doc/library/json.rst:557 +msgid "" +"Other than the *ensure_ascii* parameter, this module is defined strictly in " +"terms of conversion between Python objects and :class:`Unicode strings " +"`, and thus does not otherwise directly address the issue of character " +"encodings." +msgstr "" + +#: ../Doc/library/json.rst:562 +msgid "" +"The RFC prohibits adding a byte order mark (BOM) to the start of a JSON " +"text, and this module's serializer does not add a BOM to its output. The RFC " +"permits, but does not require, JSON deserializers to ignore an initial BOM " +"in their input. This module's deserializer raises a :exc:`ValueError` when " +"an initial BOM is present." +msgstr "" + +#: ../Doc/library/json.rst:568 +msgid "" +"The RFC does not explicitly forbid JSON strings which contain byte sequences " +"that don't correspond to valid Unicode characters (e.g. unpaired UTF-16 " +"surrogates), but it does note that they may cause interoperability problems. " +"By default, this module accepts and outputs (when present in the original :" +"class:`str`) code points for such sequences." +msgstr "" + +#: ../Doc/library/json.rst:576 +msgid "Infinite and NaN Number Values" +msgstr "" + +#: ../Doc/library/json.rst:578 +msgid "" +"The RFC does not permit the representation of infinite or NaN number values. " +"Despite that, by default, this module accepts and outputs ``Infinity``, ``-" +"Infinity``, and ``NaN`` as if they were valid JSON number literal values::" +msgstr "" + +#: ../Doc/library/json.rst:593 +msgid "" +"In the serializer, the *allow_nan* parameter can be used to alter this " +"behavior. In the deserializer, the *parse_constant* parameter can be used " +"to alter this behavior." +msgstr "" + +#: ../Doc/library/json.rst:599 +msgid "Repeated Names Within an Object" +msgstr "" + +#: ../Doc/library/json.rst:601 +msgid "" +"The RFC specifies that the names within a JSON object should be unique, but " +"does not mandate how repeated names in JSON objects should be handled. By " +"default, this module does not raise an exception; instead, it ignores all " +"but the last name-value pair for a given name::" +msgstr "" + +#: ../Doc/library/json.rst:610 +msgid "The *object_pairs_hook* parameter can be used to alter this behavior." +msgstr "" + +#: ../Doc/library/json.rst:614 +msgid "Top-level Non-Object, Non-Array Values" +msgstr "" + +#: ../Doc/library/json.rst:616 +msgid "" +"The old version of JSON specified by the obsolete :rfc:`4627` required that " +"the top-level value of a JSON text must be either a JSON object or array " +"(Python :class:`dict` or :class:`list`), and could not be a JSON null, " +"boolean, number, or string value. :rfc:`7159` removed that restriction, and " +"this module does not and has never implemented that restriction in either " +"its serializer or its deserializer." +msgstr "" + +#: ../Doc/library/json.rst:623 +msgid "" +"Regardless, for maximum interoperability, you may wish to voluntarily adhere " +"to the restriction yourself." +msgstr "" + +#: ../Doc/library/json.rst:628 +msgid "Implementation Limitations" +msgstr "" + +#: ../Doc/library/json.rst:630 +msgid "Some JSON deserializer implementations may set limits on:" +msgstr "" + +#: ../Doc/library/json.rst:632 +msgid "the size of accepted JSON texts" +msgstr "" + +#: ../Doc/library/json.rst:633 +msgid "the maximum level of nesting of JSON objects and arrays" +msgstr "" + +#: ../Doc/library/json.rst:634 +msgid "the range and precision of JSON numbers" +msgstr "" + +#: ../Doc/library/json.rst:635 +msgid "the content and maximum length of JSON strings" +msgstr "" + +#: ../Doc/library/json.rst:637 +msgid "" +"This module does not impose any such limits beyond those of the relevant " +"Python datatypes themselves or the Python interpreter itself." +msgstr "" + +#: ../Doc/library/json.rst:640 +msgid "" +"When serializing to JSON, beware any such limitations in applications that " +"may consume your JSON. In particular, it is common for JSON numbers to be " +"deserialized into IEEE 754 double precision numbers and thus subject to that " +"representation's range and precision limitations. This is especially " +"relevant when serializing Python :class:`int` values of extremely large " +"magnitude, or when serializing instances of \"exotic\" numerical types such " +"as :class:`decimal.Decimal`." +msgstr "" + +#: ../Doc/library/json.rst:658 +msgid "**Source code:** :source:`Lib/json/tool.py`" +msgstr "" + +#: ../Doc/library/json.rst:662 +msgid "" +"The :mod:`json.tool` module provides a simple command line interface to " +"validate and pretty-print JSON objects." +msgstr "" + +#: ../Doc/library/json.rst:665 +msgid "" +"If the optional ``infile`` and ``outfile`` arguments are not specified, :" +"attr:`sys.stdin` and :attr:`sys.stdout` will be used respectively::" +msgstr "" + +#: ../Doc/library/json.rst:675 +msgid "" +"The output is now in the same order as the input. Use the :option:`--sort-" +"keys` option to sort the output of dictionaries alphabetically by key." +msgstr "" + +#: ../Doc/library/json.rst:681 ../Doc/library/pickletools.rst:50 +#: ../Doc/library/tarfile.rst:691 +msgid "Command line options" +msgstr "" + +#: ../Doc/library/json.rst:685 +msgid "The JSON file to be validated or pretty-printed::" +msgstr "" + +#: ../Doc/library/json.rst:699 +msgid "If *infile* is not specified, read from :attr:`sys.stdin`." +msgstr "" + +#: ../Doc/library/json.rst:703 +msgid "" +"Write the output of the *infile* to the given *outfile*. Otherwise, write it " +"to :attr:`sys.stdout`." +msgstr "" + +#: ../Doc/library/json.rst:708 +msgid "Sort the output of dictionaries alphabetically by key." +msgstr "" + +#: ../Doc/library/json.rst:714 +msgid "Show the help message." +msgstr "" + +#: ../Doc/library/json.rst:719 +msgid "" +"As noted in `the errata for RFC 7159 `_, JSON permits literal U+2028 (LINE SEPARATOR) " +"and U+2029 (PARAGRAPH SEPARATOR) characters in strings, whereas JavaScript " +"(as of ECMAScript Edition 5.1) does not." +msgstr "" + +#: ../Doc/library/keyword.rst:2 +msgid ":mod:`keyword` --- Testing for Python keywords" +msgstr "" + +#: ../Doc/library/keyword.rst:7 +msgid "**Source code:** :source:`Lib/keyword.py`" +msgstr "" + +#: ../Doc/library/keyword.rst:11 +msgid "" +"This module allows a Python program to determine if a string is a keyword." +msgstr "" + +#: ../Doc/library/keyword.rst:16 +msgid "Return true if *s* is a Python keyword." +msgstr "" + +#: ../Doc/library/keyword.rst:21 +msgid "" +"Sequence containing all the keywords defined for the interpreter. If any " +"keywords are defined to only be active when particular :mod:`__future__` " +"statements are in effect, these will be included as well." +msgstr "" + +#: ../Doc/library/language.rst:5 +msgid "Python Language Services" +msgstr "" + +#: ../Doc/library/language.rst:7 +msgid "" +"Python provides a number of modules to assist in working with the Python " +"language. These modules support tokenizing, parsing, syntax analysis, " +"bytecode disassembly, and various other facilities." +msgstr "" + +#: ../Doc/library/language.rst:11 +msgid "These modules include:" +msgstr "" + +#: ../Doc/library/linecache.rst:2 +msgid ":mod:`linecache` --- Random access to text lines" +msgstr "" + +#: ../Doc/library/linecache.rst:9 +msgid "**Source code:** :source:`Lib/linecache.py`" +msgstr "" + +#: ../Doc/library/linecache.rst:13 +msgid "" +"The :mod:`linecache` module allows one to get any line from a Python source " +"file, while attempting to optimize internally, using a cache, the common " +"case where many lines are read from a single file. This is used by the :mod:" +"`traceback` module to retrieve source lines for inclusion in the formatted " +"traceback." +msgstr "" + +#: ../Doc/library/linecache.rst:18 +msgid "" +"The :func:`tokenize.open` function is used to open files. This function " +"uses :func:`tokenize.detect_encoding` to get the encoding of the file; in " +"the absence of an encoding token, the file encoding defaults to UTF-8." +msgstr "" + +#: ../Doc/library/linecache.rst:22 +msgid "The :mod:`linecache` module defines the following functions:" +msgstr "" + +#: ../Doc/library/linecache.rst:27 +msgid "" +"Get line *lineno* from file named *filename*. This function will never raise " +"an exception --- it will return ``''`` on errors (the terminating newline " +"character will be included for lines that are found)." +msgstr "" + +#: ../Doc/library/linecache.rst:33 +msgid "" +"If a file named *filename* is not found, the function will look for it in " +"the module search path, ``sys.path``, after first checking for a :pep:`302` " +"``__loader__`` in *module_globals*, in case the module was imported from a " +"zipfile or other non-filesystem import source." +msgstr "" + +#: ../Doc/library/linecache.rst:41 +msgid "" +"Clear the cache. Use this function if you no longer need lines from files " +"previously read using :func:`getline`." +msgstr "" + +#: ../Doc/library/linecache.rst:47 +msgid "" +"Check the cache for validity. Use this function if files in the cache may " +"have changed on disk, and you require the updated version. If *filename* is " +"omitted, it will check all the entries in the cache." +msgstr "" + +#: ../Doc/library/linecache.rst:53 +msgid "" +"Capture enough detail about a non-file-based module to permit getting its " +"lines later via :func:`getline` even if *module_globals* is None in the " +"later call. This avoids doing I/O until a line is actually needed, without " +"having to carry the module globals around indefinitely." +msgstr "" + +#: ../Doc/library/locale.rst:2 +msgid ":mod:`locale` --- Internationalization services" +msgstr "" + +#: ../Doc/library/locale.rst:10 +msgid "**Source code:** :source:`Lib/locale.py`" +msgstr "" + +#: ../Doc/library/locale.rst:14 +msgid "" +"The :mod:`locale` module opens access to the POSIX locale database and " +"functionality. The POSIX locale mechanism allows programmers to deal with " +"certain cultural issues in an application, without requiring the programmer " +"to know all the specifics of each country where the software is executed." +msgstr "" + +#: ../Doc/library/locale.rst:21 +msgid "" +"The :mod:`locale` module is implemented on top of the :mod:`_locale` module, " +"which in turn uses an ANSI C locale implementation if available." +msgstr "" + +#: ../Doc/library/locale.rst:24 +msgid "The :mod:`locale` module defines the following exception and functions:" +msgstr "" + +#: ../Doc/library/locale.rst:29 +msgid "" +"Exception raised when the locale passed to :func:`setlocale` is not " +"recognized." +msgstr "" + +#: ../Doc/library/locale.rst:35 +msgid "" +"If *locale* is given and not ``None``, :func:`setlocale` modifies the locale " +"setting for the *category*. The available categories are listed in the data " +"description below. *locale* may be a string, or an iterable of two strings " +"(language code and encoding). If it's an iterable, it's converted to a " +"locale name using the locale aliasing engine. An empty string specifies the " +"user's default settings. If the modification of the locale fails, the " +"exception :exc:`Error` is raised. If successful, the new locale setting is " +"returned." +msgstr "" + +#: ../Doc/library/locale.rst:43 +msgid "" +"If *locale* is omitted or ``None``, the current setting for *category* is " +"returned." +msgstr "" + +#: ../Doc/library/locale.rst:46 +msgid "" +":func:`setlocale` is not thread-safe on most systems. Applications typically " +"start with a call of ::" +msgstr "" + +#: ../Doc/library/locale.rst:52 +msgid "" +"This sets the locale for all categories to the user's default setting " +"(typically specified in the :envvar:`LANG` environment variable). If the " +"locale is not changed thereafter, using multithreading should not cause " +"problems." +msgstr "" + +#: ../Doc/library/locale.rst:59 +msgid "" +"Returns the database of the local conventions as a dictionary. This " +"dictionary has the following strings as keys:" +msgstr "" + +#: ../Doc/library/locale.rst:65 +msgid "Category" +msgstr "" + +#: ../Doc/library/locale.rst:67 +msgid ":const:`LC_NUMERIC`" +msgstr "" + +#: ../Doc/library/locale.rst:67 +msgid "``'decimal_point'``" +msgstr "" + +#: ../Doc/library/locale.rst:67 +msgid "Decimal point character." +msgstr "" + +#: ../Doc/library/locale.rst:69 +msgid "``'grouping'``" +msgstr "" + +#: ../Doc/library/locale.rst:69 +msgid "" +"Sequence of numbers specifying which relative positions the " +"``'thousands_sep'`` is expected. If the sequence is terminated with :const:" +"`CHAR_MAX`, no further grouping is performed. If the sequence terminates " +"with a ``0``, the last group size is repeatedly used." +msgstr "" + +#: ../Doc/library/locale.rst:80 +msgid "``'thousands_sep'``" +msgstr "" + +#: ../Doc/library/locale.rst:80 +msgid "Character used between groups." +msgstr "" + +#: ../Doc/library/locale.rst:82 +msgid ":const:`LC_MONETARY`" +msgstr "" + +#: ../Doc/library/locale.rst:82 +msgid "``'int_curr_symbol'``" +msgstr "" + +#: ../Doc/library/locale.rst:82 +msgid "International currency symbol." +msgstr "" + +#: ../Doc/library/locale.rst:84 +msgid "``'currency_symbol'``" +msgstr "" + +#: ../Doc/library/locale.rst:84 +msgid "Local currency symbol." +msgstr "" + +#: ../Doc/library/locale.rst:86 +msgid "``'p_cs_precedes/n_cs_precedes'``" +msgstr "" + +#: ../Doc/library/locale.rst:86 +msgid "" +"Whether the currency symbol precedes the value (for positive resp. negative " +"values)." +msgstr "" + +#: ../Doc/library/locale.rst:91 +msgid "``'p_sep_by_space/n_sep_by_space'``" +msgstr "" + +#: ../Doc/library/locale.rst:91 +msgid "" +"Whether the currency symbol is separated from the value by a space (for " +"positive resp. negative values)." +msgstr "" + +#: ../Doc/library/locale.rst:96 +msgid "``'mon_decimal_point'``" +msgstr "" + +#: ../Doc/library/locale.rst:96 +msgid "Decimal point used for monetary values." +msgstr "" + +#: ../Doc/library/locale.rst:99 +msgid "``'frac_digits'``" +msgstr "" + +#: ../Doc/library/locale.rst:99 +msgid "" +"Number of fractional digits used in local formatting of monetary values." +msgstr "" + +#: ../Doc/library/locale.rst:103 +msgid "``'int_frac_digits'``" +msgstr "" + +#: ../Doc/library/locale.rst:103 +msgid "" +"Number of fractional digits used in international formatting of monetary " +"values." +msgstr "" + +#: ../Doc/library/locale.rst:107 +msgid "``'mon_thousands_sep'``" +msgstr "" + +#: ../Doc/library/locale.rst:107 +msgid "Group separator used for monetary values." +msgstr "" + +#: ../Doc/library/locale.rst:110 +msgid "``'mon_grouping'``" +msgstr "" + +#: ../Doc/library/locale.rst:110 +msgid "Equivalent to ``'grouping'``, used for monetary values." +msgstr "" + +#: ../Doc/library/locale.rst:113 +msgid "``'positive_sign'``" +msgstr "" + +#: ../Doc/library/locale.rst:113 +msgid "Symbol used to annotate a positive monetary value." +msgstr "" + +#: ../Doc/library/locale.rst:116 +msgid "``'negative_sign'``" +msgstr "" + +#: ../Doc/library/locale.rst:116 +msgid "Symbol used to annotate a negative monetary value." +msgstr "" + +#: ../Doc/library/locale.rst:119 +msgid "``'p_sign_posn/n_sign_posn'``" +msgstr "" + +#: ../Doc/library/locale.rst:119 +msgid "" +"The position of the sign (for positive resp. negative values), see below." +msgstr "" + +#: ../Doc/library/locale.rst:124 +msgid "" +"All numeric values can be set to :const:`CHAR_MAX` to indicate that there is " +"no value specified in this locale." +msgstr "" + +#: ../Doc/library/locale.rst:127 +msgid "" +"The possible values for ``'p_sign_posn'`` and ``'n_sign_posn'`` are given " +"below." +msgstr "" + +#: ../Doc/library/locale.rst:130 ../Doc/library/mailbox.rst:817 +#: ../Doc/library/mailbox.rst:984 ../Doc/library/mailbox.rst:1134 +#: ../Doc/library/mailbox.rst:1221 ../Doc/library/mailbox.rst:1354 +#: ../Doc/library/sys.rst:713 ../Doc/library/sys.rst:1224 +msgid "Explanation" +msgstr "" + +#: ../Doc/library/locale.rst:132 ../Doc/library/resource.rst:281 +#: ../Doc/library/winreg.rst:212 ../Doc/library/winreg.rst:319 +#: ../Doc/library/winreg.rst:363 ../Doc/library/zipfile.rst:541 +msgid "``0``" +msgstr "" + +#: ../Doc/library/locale.rst:132 +msgid "Currency and value are surrounded by parentheses." +msgstr "" + +#: ../Doc/library/locale.rst:135 ../Doc/library/resource.rst:283 +#: ../Doc/library/winreg.rst:214 ../Doc/library/winreg.rst:322 +#: ../Doc/library/winreg.rst:365 ../Doc/library/zipfile.rst:543 +msgid "``1``" +msgstr "" + +#: ../Doc/library/locale.rst:135 +msgid "The sign should precede the value and currency symbol." +msgstr "" + +#: ../Doc/library/locale.rst:138 ../Doc/library/resource.rst:285 +#: ../Doc/library/winreg.rst:218 ../Doc/library/winreg.rst:325 +#: ../Doc/library/zipfile.rst:545 +msgid "``2``" +msgstr "" + +#: ../Doc/library/locale.rst:138 +msgid "The sign should follow the value and currency symbol." +msgstr "" + +#: ../Doc/library/locale.rst:141 ../Doc/library/resource.rst:287 +#: ../Doc/library/zipfile.rst:547 +msgid "``3``" +msgstr "" + +#: ../Doc/library/locale.rst:141 +msgid "The sign should immediately precede the value." +msgstr "" + +#: ../Doc/library/locale.rst:144 ../Doc/library/resource.rst:289 +#: ../Doc/library/zipfile.rst:549 +msgid "``4``" +msgstr "" + +#: ../Doc/library/locale.rst:144 +msgid "The sign should immediately follow the value." +msgstr "" + +#: ../Doc/library/locale.rst:147 +msgid "``CHAR_MAX``" +msgstr "" + +#: ../Doc/library/locale.rst:147 +msgid "Nothing is specified in this locale." +msgstr "" + +#: ../Doc/library/locale.rst:153 +msgid "" +"Return some locale-specific information as a string. This function is not " +"available on all systems, and the set of possible options might also vary " +"across platforms. The possible argument values are numbers, for which " +"symbolic constants are available in the locale module." +msgstr "" + +#: ../Doc/library/locale.rst:158 +msgid "" +"The :func:`nl_langinfo` function accepts one of the following keys. Most " +"descriptions are taken from the corresponding description in the GNU C " +"library." +msgstr "" + +#: ../Doc/library/locale.rst:164 +msgid "" +"Get a string with the name of the character encoding used in the selected " +"locale." +msgstr "" + +#: ../Doc/library/locale.rst:169 +msgid "" +"Get a string that can be used as a format string for :func:`time.strftime` " +"to represent date and time in a locale-specific way." +msgstr "" + +#: ../Doc/library/locale.rst:174 +msgid "" +"Get a string that can be used as a format string for :func:`time.strftime` " +"to represent a date in a locale-specific way." +msgstr "" + +#: ../Doc/library/locale.rst:179 +msgid "" +"Get a string that can be used as a format string for :func:`time.strftime` " +"to represent a time in a locale-specific way." +msgstr "" + +#: ../Doc/library/locale.rst:184 +msgid "" +"Get a format string for :func:`time.strftime` to represent time in the am/pm " +"format." +msgstr "" + +#: ../Doc/library/locale.rst:189 +msgid "Get the name of the n-th day of the week." +msgstr "" + +#: ../Doc/library/locale.rst:193 +msgid "" +"This follows the US convention of :const:`DAY_1` being Sunday, not the " +"international convention (ISO 8601) that Monday is the first day of the week." +msgstr "" + +#: ../Doc/library/locale.rst:199 +msgid "Get the abbreviated name of the n-th day of the week." +msgstr "" + +#: ../Doc/library/locale.rst:203 +msgid "Get the name of the n-th month." +msgstr "" + +#: ../Doc/library/locale.rst:207 +msgid "Get the abbreviated name of the n-th month." +msgstr "" + +#: ../Doc/library/locale.rst:211 +msgid "Get the radix character (decimal dot, decimal comma, etc.)." +msgstr "" + +#: ../Doc/library/locale.rst:215 +msgid "Get the separator character for thousands (groups of three digits)." +msgstr "" + +#: ../Doc/library/locale.rst:219 +msgid "" +"Get a regular expression that can be used with the regex function to " +"recognize a positive response to a yes/no question." +msgstr "" + +#: ../Doc/library/locale.rst:224 +msgid "" +"The expression is in the syntax suitable for the :c:func:`regex` function " +"from the C library, which might differ from the syntax used in :mod:`re`." +msgstr "" + +#: ../Doc/library/locale.rst:229 +msgid "" +"Get a regular expression that can be used with the regex(3) function to " +"recognize a negative response to a yes/no question." +msgstr "" + +#: ../Doc/library/locale.rst:234 +msgid "" +"Get the currency symbol, preceded by \"-\" if the symbol should appear " +"before the value, \"+\" if the symbol should appear after the value, or \"." +"\" if the symbol should replace the radix character." +msgstr "" + +#: ../Doc/library/locale.rst:240 +msgid "Get a string that represents the era used in the current locale." +msgstr "" + +#: ../Doc/library/locale.rst:242 +msgid "" +"Most locales do not define this value. An example of a locale which does " +"define this value is the Japanese one. In Japan, the traditional " +"representation of dates includes the name of the era corresponding to the " +"then-emperor's reign." +msgstr "" + +#: ../Doc/library/locale.rst:247 +msgid "" +"Normally it should not be necessary to use this value directly. Specifying " +"the ``E`` modifier in their format strings causes the :func:`time.strftime` " +"function to use this information. The format of the returned string is not " +"specified, and therefore you should not assume knowledge of it on different " +"systems." +msgstr "" + +#: ../Doc/library/locale.rst:255 +msgid "" +"Get a format string for :func:`time.strftime` to represent date and time in " +"a locale-specific era-based way." +msgstr "" + +#: ../Doc/library/locale.rst:260 +msgid "" +"Get a format string for :func:`time.strftime` to represent a date in a " +"locale-specific era-based way." +msgstr "" + +#: ../Doc/library/locale.rst:265 +msgid "" +"Get a format string for :func:`time.strftime` to represent a time in a " +"locale-specific era-based way." +msgstr "" + +#: ../Doc/library/locale.rst:270 +msgid "" +"Get a representation of up to 100 values used to represent the values 0 to " +"99." +msgstr "" + +#: ../Doc/library/locale.rst:276 +msgid "" +"Tries to determine the default locale settings and returns them as a tuple " +"of the form ``(language code, encoding)``." +msgstr "" + +#: ../Doc/library/locale.rst:279 +msgid "" +"According to POSIX, a program which has not called ``setlocale(LC_ALL, '')`` " +"runs using the portable ``'C'`` locale. Calling ``setlocale(LC_ALL, '')`` " +"lets it use the default locale as defined by the :envvar:`LANG` variable. " +"Since we do not want to interfere with the current locale setting we thus " +"emulate the behavior in the way described above." +msgstr "" + +#: ../Doc/library/locale.rst:285 +msgid "" +"To maintain compatibility with other platforms, not only the :envvar:`LANG` " +"variable is tested, but a list of variables given as envvars parameter. The " +"first found to be defined will be used. *envvars* defaults to the search " +"path used in GNU gettext; it must always contain the variable name " +"``'LANG'``. The GNU gettext search path contains ``'LC_ALL'``, " +"``'LC_CTYPE'``, ``'LANG'`` and ``'LANGUAGE'``, in that order." +msgstr "" + +#: ../Doc/library/locale.rst:292 ../Doc/library/locale.rst:303 +msgid "" +"Except for the code ``'C'``, the language code corresponds to :rfc:`1766`. " +"*language code* and *encoding* may be ``None`` if their values cannot be " +"determined." +msgstr "" + +#: ../Doc/library/locale.rst:299 +msgid "" +"Returns the current setting for the given locale category as sequence " +"containing *language code*, *encoding*. *category* may be one of the :const:" +"`LC_\\*` values except :const:`LC_ALL`. It defaults to :const:`LC_CTYPE`." +msgstr "" + +#: ../Doc/library/locale.rst:310 +msgid "" +"Return the encoding used for text data, according to user preferences. User " +"preferences are expressed differently on different systems, and might not be " +"available programmatically on some systems, so this function only returns a " +"guess." +msgstr "" + +#: ../Doc/library/locale.rst:315 +msgid "" +"On some systems, it is necessary to invoke :func:`setlocale` to obtain the " +"user preferences, so this function is not thread-safe. If invoking setlocale " +"is not necessary or desired, *do_setlocale* should be set to ``False``." +msgstr "" + +#: ../Doc/library/locale.rst:322 +msgid "" +"Returns a normalized locale code for the given locale name. The returned " +"locale code is formatted for use with :func:`setlocale`. If normalization " +"fails, the original name is returned unchanged." +msgstr "" + +#: ../Doc/library/locale.rst:326 +msgid "" +"If the given encoding is not known, the function defaults to the default " +"encoding for the locale code just like :func:`setlocale`." +msgstr "" + +#: ../Doc/library/locale.rst:332 +msgid "Sets the locale for *category* to the default setting." +msgstr "" + +#: ../Doc/library/locale.rst:334 +msgid "" +"The default setting is determined by calling :func:`getdefaultlocale`. " +"*category* defaults to :const:`LC_ALL`." +msgstr "" + +#: ../Doc/library/locale.rst:340 +msgid "" +"Compares two strings according to the current :const:`LC_COLLATE` setting. " +"As any other compare function, returns a negative, or a positive value, or " +"``0``, depending on whether *string1* collates before or after *string2* or " +"is equal to it." +msgstr "" + +#: ../Doc/library/locale.rst:348 +msgid "" +"Transforms a string to one that can be used in locale-aware comparisons. " +"For example, ``strxfrm(s1) < strxfrm(s2)`` is equivalent to ``strcoll(s1, " +"s2) < 0``. This function can be used when the same string is compared " +"repeatedly, e.g. when collating a sequence of strings." +msgstr "" + +#: ../Doc/library/locale.rst:357 +msgid "" +"Formats a number *val* according to the current :const:`LC_NUMERIC` setting. " +"The format follows the conventions of the ``%`` operator. For floating " +"point values, the decimal point is modified if appropriate. If *grouping* " +"is true, also takes the grouping into account." +msgstr "" + +#: ../Doc/library/locale.rst:362 +msgid "" +"If *monetary* is true, the conversion uses monetary thousands separator and " +"grouping strings." +msgstr "" + +#: ../Doc/library/locale.rst:365 +msgid "" +"Please note that this function will only work for exactly one %char " +"specifier. For whole format strings, use :func:`format_string`." +msgstr "" + +#: ../Doc/library/locale.rst:371 +msgid "" +"Processes formatting specifiers as in ``format % val``, but takes the " +"current locale settings into account." +msgstr "" + +#: ../Doc/library/locale.rst:377 +msgid "" +"Formats a number *val* according to the current :const:`LC_MONETARY` " +"settings." +msgstr "" + +#: ../Doc/library/locale.rst:379 +msgid "" +"The returned string includes the currency symbol if *symbol* is true, which " +"is the default. If *grouping* is true (which is not the default), grouping " +"is done with the value. If *international* is true (which is not the " +"default), the international currency symbol is used." +msgstr "" + +#: ../Doc/library/locale.rst:384 +msgid "" +"Note that this function will not work with the 'C' locale, so you have to " +"set a locale via :func:`setlocale` first." +msgstr "" + +#: ../Doc/library/locale.rst:390 +msgid "" +"Formats a floating point number using the same format as the built-in " +"function ``str(float)``, but takes the decimal point into account." +msgstr "" + +#: ../Doc/library/locale.rst:396 +msgid "" +"Converts a string into a normalized number string, following the :const:" +"`LC_NUMERIC` settings." +msgstr "" + +#: ../Doc/library/locale.rst:404 +msgid "" +"Converts a string to a floating point number, following the :const:" +"`LC_NUMERIC` settings." +msgstr "" + +#: ../Doc/library/locale.rst:410 +msgid "" +"Converts a string to an integer, following the :const:`LC_NUMERIC` " +"conventions." +msgstr "" + +#: ../Doc/library/locale.rst:417 +msgid "" +"Locale category for the character type functions. Depending on the settings " +"of this category, the functions of module :mod:`string` dealing with case " +"change their behaviour." +msgstr "" + +#: ../Doc/library/locale.rst:424 +msgid "" +"Locale category for sorting strings. The functions :func:`strcoll` and :" +"func:`strxfrm` of the :mod:`locale` module are affected." +msgstr "" + +#: ../Doc/library/locale.rst:430 +msgid "" +"Locale category for the formatting of time. The function :func:`time." +"strftime` follows these conventions." +msgstr "" + +#: ../Doc/library/locale.rst:436 +msgid "" +"Locale category for formatting of monetary values. The available options " +"are available from the :func:`localeconv` function." +msgstr "" + +#: ../Doc/library/locale.rst:442 +msgid "" +"Locale category for message display. Python currently does not support " +"application specific locale-aware messages. Messages displayed by the " +"operating system, like those returned by :func:`os.strerror` might be " +"affected by this category." +msgstr "" + +#: ../Doc/library/locale.rst:450 +msgid "" +"Locale category for formatting numbers. The functions :func:`.format`, :" +"func:`atoi`, :func:`atof` and :func:`.str` of the :mod:`locale` module are " +"affected by that category. All other numeric formatting operations are not " +"affected." +msgstr "" + +#: ../Doc/library/locale.rst:458 +msgid "" +"Combination of all locale settings. If this flag is used when the locale is " +"changed, setting the locale for all categories is attempted. If that fails " +"for any category, no category is changed at all. When the locale is " +"retrieved using this flag, a string indicating the setting for all " +"categories is returned. This string can be later used to restore the " +"settings." +msgstr "" + +#: ../Doc/library/locale.rst:467 +msgid "" +"This is a symbolic constant used for different values returned by :func:" +"`localeconv`." +msgstr "" + +#: ../Doc/library/locale.rst:484 +msgid "Background, details, hints, tips and caveats" +msgstr "" + +#: ../Doc/library/locale.rst:486 +msgid "" +"The C standard defines the locale as a program-wide property that may be " +"relatively expensive to change. On top of that, some implementation are " +"broken in such a way that frequent locale changes may cause core dumps. " +"This makes the locale somewhat painful to use correctly." +msgstr "" + +#: ../Doc/library/locale.rst:491 +msgid "" +"Initially, when a program is started, the locale is the ``C`` locale, no " +"matter what the user's preferred locale is. There is one exception: the :" +"data:`LC_CTYPE` category is changed at startup to set the current locale " +"encoding to the user's preferred locale encoding. The program must " +"explicitly say that it wants the user's preferred locale settings for other " +"categories by calling ``setlocale(LC_ALL, '')``." +msgstr "" + +#: ../Doc/library/locale.rst:498 +msgid "" +"It is generally a bad idea to call :func:`setlocale` in some library " +"routine, since as a side effect it affects the entire program. Saving and " +"restoring it is almost as bad: it is expensive and affects other threads " +"that happen to run before the settings have been restored." +msgstr "" + +#: ../Doc/library/locale.rst:503 +msgid "" +"If, when coding a module for general use, you need a locale independent " +"version of an operation that is affected by the locale (such as certain " +"formats used with :func:`time.strftime`), you will have to find a way to do " +"it without using the standard library routine. Even better is convincing " +"yourself that using locale settings is okay. Only as a last resort should " +"you document that your module is not compatible with non-\\ ``C`` locale " +"settings." +msgstr "" + +#: ../Doc/library/locale.rst:510 +msgid "" +"The only way to perform numeric operations according to the locale is to use " +"the special functions defined by this module: :func:`atof`, :func:`atoi`, :" +"func:`.format`, :func:`.str`." +msgstr "" + +#: ../Doc/library/locale.rst:514 +msgid "" +"There is no way to perform case conversions and character classifications " +"according to the locale. For (Unicode) text strings these are done " +"according to the character value only, while for byte strings, the " +"conversions and classifications are done according to the ASCII value of the " +"byte, and bytes whose high bit is set (i.e., non-ASCII bytes) are never " +"converted or considered part of a character class such as letter or " +"whitespace." +msgstr "" + +#: ../Doc/library/locale.rst:525 +msgid "For extension writers and programs that embed Python" +msgstr "" + +#: ../Doc/library/locale.rst:527 +msgid "" +"Extension modules should never call :func:`setlocale`, except to find out " +"what the current locale is. But since the return value can only be used " +"portably to restore it, that is not very useful (except perhaps to find out " +"whether or not the locale is ``C``)." +msgstr "" + +#: ../Doc/library/locale.rst:532 +msgid "" +"When Python code uses the :mod:`locale` module to change the locale, this " +"also affects the embedding application. If the embedding application " +"doesn't want this to happen, it should remove the :mod:`_locale` extension " +"module (which does all the work) from the table of built-in modules in the :" +"file:`config.c` file, and make sure that the :mod:`_locale` module is not " +"accessible as a shared library." +msgstr "" + +#: ../Doc/library/locale.rst:543 +msgid "Access to message catalogs" +msgstr "" + +#: ../Doc/library/locale.rst:545 +msgid "" +"The locale module exposes the C library's gettext interface on systems that " +"provide this interface. It consists of the functions :func:`gettext`, :func:" +"`dgettext`, :func:`dcgettext`, :func:`textdomain`, :func:`bindtextdomain`, " +"and :func:`bind_textdomain_codeset`. These are similar to the same " +"functions in the :mod:`gettext` module, but use the C library's binary " +"format for message catalogs, and the C library's search algorithms for " +"locating message catalogs." +msgstr "" + +#: ../Doc/library/locale.rst:552 +msgid "" +"Python applications should normally find no need to invoke these functions, " +"and should use :mod:`gettext` instead. A known exception to this rule are " +"applications that link with additional C libraries which internally invoke :" +"c:func:`gettext` or :func:`dcgettext`. For these applications, it may be " +"necessary to bind the text domain, so that the libraries can properly locate " +"their message catalogs." +msgstr "" + +#: ../Doc/library/logging.rst:2 +msgid ":mod:`logging` --- Logging facility for Python" +msgstr "" + +#: ../Doc/library/logging.rst:10 +msgid "**Source code:** :source:`Lib/logging/__init__.py`" +msgstr "" + +#: ../Doc/library/logging.rst:0 ../Doc/library/logging.config.rst:0 +#: ../Doc/library/logging.handlers.rst:0 +msgid "Important" +msgstr "" + +#: ../Doc/library/logging.rst:16 +msgid "" +"This page contains the API reference information. For tutorial information " +"and discussion of more advanced topics, see" +msgstr "" + +#: ../Doc/library/logging.rst:19 ../Doc/library/logging.config.rst:17 +#: ../Doc/library/logging.handlers.rst:17 +msgid ":ref:`Basic Tutorial `" +msgstr "" + +#: ../Doc/library/logging.rst:20 ../Doc/library/logging.config.rst:18 +#: ../Doc/library/logging.handlers.rst:18 +msgid ":ref:`Advanced Tutorial `" +msgstr "" + +#: ../Doc/library/logging.rst:21 ../Doc/library/logging.config.rst:19 +#: ../Doc/library/logging.handlers.rst:19 +msgid ":ref:`Logging Cookbook `" +msgstr "" + +#: ../Doc/library/logging.rst:25 +msgid "" +"This module defines functions and classes which implement a flexible event " +"logging system for applications and libraries." +msgstr "" + +#: ../Doc/library/logging.rst:28 +msgid "" +"The key benefit of having the logging API provided by a standard library " +"module is that all Python modules can participate in logging, so your " +"application log can include your own messages integrated with messages from " +"third-party modules." +msgstr "" + +#: ../Doc/library/logging.rst:33 +msgid "" +"The module provides a lot of functionality and flexibility. If you are " +"unfamiliar with logging, the best way to get to grips with it is to see the " +"tutorials (see the links on the right)." +msgstr "" + +#: ../Doc/library/logging.rst:37 +msgid "" +"The basic classes defined by the module, together with their functions, are " +"listed below." +msgstr "" + +#: ../Doc/library/logging.rst:40 +msgid "Loggers expose the interface that application code directly uses." +msgstr "" + +#: ../Doc/library/logging.rst:41 +msgid "" +"Handlers send the log records (created by loggers) to the appropriate " +"destination." +msgstr "" + +#: ../Doc/library/logging.rst:43 +msgid "" +"Filters provide a finer grained facility for determining which log records " +"to output." +msgstr "" + +#: ../Doc/library/logging.rst:45 +msgid "Formatters specify the layout of log records in the final output." +msgstr "" + +#: ../Doc/library/logging.rst:51 +msgid "Logger Objects" +msgstr "" + +#: ../Doc/library/logging.rst:53 +msgid "" +"Loggers have the following attributes and methods. Note that Loggers are " +"never instantiated directly, but always through the module-level function " +"``logging.getLogger(name)``. Multiple calls to :func:`getLogger` with the " +"same name will always return a reference to the same Logger object." +msgstr "" + +#: ../Doc/library/logging.rst:58 +msgid "" +"The ``name`` is potentially a period-separated hierarchical value, like " +"``foo.bar.baz`` (though it could also be just plain ``foo``, for example). " +"Loggers that are further down in the hierarchical list are children of " +"loggers higher up in the list. For example, given a logger with a name of " +"``foo``, loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` " +"are all descendants of ``foo``. The logger name hierarchy is analogous to " +"the Python package hierarchy, and identical to it if you organise your " +"loggers on a per-module basis using the recommended construction ``logging." +"getLogger(__name__)``. That's because in a module, ``__name__`` is the " +"module's name in the Python package namespace." +msgstr "" + +#: ../Doc/library/logging.rst:74 +msgid "" +"If this evaluates to true, events logged to this logger will be passed to " +"the handlers of higher level (ancestor) loggers, in addition to any handlers " +"attached to this logger. Messages are passed directly to the ancestor " +"loggers' handlers - neither the level nor filters of the ancestor loggers in " +"question are considered." +msgstr "" + +#: ../Doc/library/logging.rst:80 +msgid "" +"If this evaluates to false, logging messages are not passed to the handlers " +"of ancestor loggers." +msgstr "" + +#: ../Doc/library/logging.rst:83 +msgid "The constructor sets this attribute to ``True``." +msgstr "" + +#: ../Doc/library/logging.rst:85 +msgid "" +"If you attach a handler to a logger *and* one or more of its ancestors, it " +"may emit the same record multiple times. In general, you should not need to " +"attach a handler to more than one logger - if you just attach it to the " +"appropriate logger which is highest in the logger hierarchy, then it will " +"see all events logged by all descendant loggers, provided that their " +"propagate setting is left set to ``True``. A common scenario is to attach " +"handlers only to the root logger, and to let propagation take care of the " +"rest." +msgstr "" + +#: ../Doc/library/logging.rst:96 +msgid "" +"Sets the threshold for this logger to *lvl*. Logging messages which are less " +"severe than *lvl* will be ignored. When a logger is created, the level is " +"set to :const:`NOTSET` (which causes all messages to be processed when the " +"logger is the root logger, or delegation to the parent when the logger is a " +"non-root logger). Note that the root logger is created with level :const:" +"`WARNING`." +msgstr "" + +#: ../Doc/library/logging.rst:102 +msgid "" +"The term 'delegation to the parent' means that if a logger has a level of " +"NOTSET, its chain of ancestor loggers is traversed until either an ancestor " +"with a level other than NOTSET is found, or the root is reached." +msgstr "" + +#: ../Doc/library/logging.rst:106 +msgid "" +"If an ancestor is found with a level other than NOTSET, then that ancestor's " +"level is treated as the effective level of the logger where the ancestor " +"search began, and is used to determine how a logging event is handled." +msgstr "" + +#: ../Doc/library/logging.rst:110 +msgid "" +"If the root is reached, and it has a level of NOTSET, then all messages will " +"be processed. Otherwise, the root's level will be used as the effective " +"level." +msgstr "" + +#: ../Doc/library/logging.rst:113 ../Doc/library/logging.rst:395 +msgid "See :ref:`levels` for a list of levels." +msgstr "" + +#: ../Doc/library/logging.rst:115 +msgid "" +"The *lvl* parameter now accepts a string representation of the level such as " +"'INFO' as an alternative to the integer constants such as :const:`INFO`. " +"Note, however, that levels are internally stored as integers, and methods " +"such as e.g. :meth:`getEffectiveLevel` and :meth:`isEnabledFor` will return/" +"expect to be passed integers." +msgstr "" + +#: ../Doc/library/logging.rst:125 +msgid "" +"Indicates if a message of severity *lvl* would be processed by this logger. " +"This method checks first the module-level level set by ``logging." +"disable(lvl)`` and then the logger's effective level as determined by :meth:" +"`getEffectiveLevel`." +msgstr "" + +#: ../Doc/library/logging.rst:133 +msgid "" +"Indicates the effective level for this logger. If a value other than :const:" +"`NOTSET` has been set using :meth:`setLevel`, it is returned. Otherwise, the " +"hierarchy is traversed towards the root until a value other than :const:" +"`NOTSET` is found, and that value is returned. The value returned is an " +"integer, typically one of :const:`logging.DEBUG`, :const:`logging.INFO` etc." +msgstr "" + +#: ../Doc/library/logging.rst:143 +msgid "" +"Returns a logger which is a descendant to this logger, as determined by the " +"suffix. Thus, ``logging.getLogger('abc').getChild('def.ghi')`` would return " +"the same logger as would be returned by ``logging.getLogger('abc.def." +"ghi')``. This is a convenience method, useful when the parent logger is " +"named using e.g. ``__name__`` rather than a literal string." +msgstr "" + +#: ../Doc/library/logging.rst:154 +msgid "" +"Logs a message with level :const:`DEBUG` on this logger. The *msg* is the " +"message format string, and the *args* are the arguments which are merged " +"into *msg* using the string formatting operator. (Note that this means that " +"you can use keywords in the format string, together with a single dictionary " +"argument.)" +msgstr "" + +#: ../Doc/library/logging.rst:159 +msgid "" +"There are three keyword arguments in *kwargs* which are inspected: " +"*exc_info*, *stack_info*, and *extra*." +msgstr "" + +#: ../Doc/library/logging.rst:162 +msgid "" +"If *exc_info* does not evaluate as false, it causes exception information to " +"be added to the logging message. If an exception tuple (in the format " +"returned by :func:`sys.exc_info`) or an exception instance is provided, it " +"is used; otherwise, :func:`sys.exc_info` is called to get the exception " +"information." +msgstr "" + +#: ../Doc/library/logging.rst:167 ../Doc/library/logging.rst:923 +msgid "" +"The second optional keyword argument is *stack_info*, which defaults to " +"``False``. If true, stack information is added to the logging message, " +"including the actual logging call. Note that this is not the same stack " +"information as that displayed through specifying *exc_info*: The former is " +"stack frames from the bottom of the stack up to the logging call in the " +"current thread, whereas the latter is information about stack frames which " +"have been unwound, following an exception, while searching for exception " +"handlers." +msgstr "" + +#: ../Doc/library/logging.rst:176 ../Doc/library/logging.rst:932 +msgid "" +"You can specify *stack_info* independently of *exc_info*, e.g. to just show " +"how you got to a certain point in your code, even when no exceptions were " +"raised. The stack frames are printed following a header line which says::" +msgstr "" + +#: ../Doc/library/logging.rst:182 ../Doc/library/logging.rst:938 +msgid "" +"This mimics the ``Traceback (most recent call last):`` which is used when " +"displaying exception frames." +msgstr "" + +#: ../Doc/library/logging.rst:185 +msgid "" +"The third keyword argument is *extra* which can be used to pass a dictionary " +"which is used to populate the __dict__ of the LogRecord created for the " +"logging event with user-defined attributes. These custom attributes can then " +"be used as you like. For example, they could be incorporated into logged " +"messages. For example::" +msgstr "" + +#: ../Doc/library/logging.rst:197 +msgid "would print something like ::" +msgstr "" + +#: ../Doc/library/logging.rst:201 ../Doc/library/logging.rst:956 +msgid "" +"The keys in the dictionary passed in *extra* should not clash with the keys " +"used by the logging system. (See the :class:`Formatter` documentation for " +"more information on which keys are used by the logging system.)" +msgstr "" + +#: ../Doc/library/logging.rst:205 ../Doc/library/logging.rst:960 +msgid "" +"If you choose to use these attributes in logged messages, you need to " +"exercise some care. In the above example, for instance, the :class:" +"`Formatter` has been set up with a format string which expects 'clientip' " +"and 'user' in the attribute dictionary of the LogRecord. If these are " +"missing, the message will not be logged because a string formatting " +"exception will occur. So in this case, you always need to pass the *extra* " +"dictionary with these keys." +msgstr "" + +#: ../Doc/library/logging.rst:212 ../Doc/library/logging.rst:967 +msgid "" +"While this might be annoying, this feature is intended for use in " +"specialized circumstances, such as multi-threaded servers where the same " +"code executes in many contexts, and interesting conditions which arise are " +"dependent on this context (such as remote client IP address and " +"authenticated user name, in the above example). In such circumstances, it is " +"likely that specialized :class:`Formatter`\\ s would be used with " +"particular :class:`Handler`\\ s." +msgstr "" + +#: ../Doc/library/logging.rst:219 ../Doc/library/logging.rst:974 +msgid "The *stack_info* parameter was added." +msgstr "" + +#: ../Doc/library/logging.rst:222 +msgid "The *exc_info* parameter can now accept exception instances." +msgstr "" + +#: ../Doc/library/logging.rst:228 +msgid "" +"Logs a message with level :const:`INFO` on this logger. The arguments are " +"interpreted as for :meth:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:234 +msgid "" +"Logs a message with level :const:`WARNING` on this logger. The arguments are " +"interpreted as for :meth:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:237 +msgid "" +"There is an obsolete method ``warn`` which is functionally identical to " +"``warning``. As ``warn`` is deprecated, please do not use it - use " +"``warning`` instead." +msgstr "" + +#: ../Doc/library/logging.rst:243 +msgid "" +"Logs a message with level :const:`ERROR` on this logger. The arguments are " +"interpreted as for :meth:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:249 +msgid "" +"Logs a message with level :const:`CRITICAL` on this logger. The arguments " +"are interpreted as for :meth:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:255 +msgid "" +"Logs a message with integer level *lvl* on this logger. The other arguments " +"are interpreted as for :meth:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:261 +msgid "" +"Logs a message with level :const:`ERROR` on this logger. The arguments are " +"interpreted as for :meth:`debug`. Exception info is added to the logging " +"message. This method should only be called from an exception handler." +msgstr "" + +#: ../Doc/library/logging.rst:268 +msgid "Adds the specified filter *filt* to this logger." +msgstr "" + +#: ../Doc/library/logging.rst:273 +msgid "Removes the specified filter *filt* from this logger." +msgstr "" + +#: ../Doc/library/logging.rst:278 +msgid "" +"Applies this logger's filters to the record and returns a true value if the " +"record is to be processed. The filters are consulted in turn, until one of " +"them returns a false value. If none of them return a false value, the record " +"will be processed (passed to handlers). If one returns a false value, no " +"further processing of the record occurs." +msgstr "" + +#: ../Doc/library/logging.rst:287 +msgid "Adds the specified handler *hdlr* to this logger." +msgstr "" + +#: ../Doc/library/logging.rst:292 +msgid "Removes the specified handler *hdlr* from this logger." +msgstr "" + +#: ../Doc/library/logging.rst:297 +msgid "" +"Finds the caller's source filename and line number. Returns the filename, " +"line number, function name and stack information as a 4-element tuple. The " +"stack information is returned as *None* unless *stack_info* is *True*." +msgstr "" + +#: ../Doc/library/logging.rst:304 +msgid "" +"Handles a record by passing it to all handlers associated with this logger " +"and its ancestors (until a false value of *propagate* is found). This method " +"is used for unpickled records received from a socket, as well as those " +"created locally. Logger-level filtering is applied using :meth:`~Logger." +"filter`." +msgstr "" + +#: ../Doc/library/logging.rst:312 +msgid "" +"This is a factory method which can be overridden in subclasses to create " +"specialized :class:`LogRecord` instances." +msgstr "" + +#: ../Doc/library/logging.rst:317 +msgid "" +"Checks to see if this logger has any handlers configured. This is done by " +"looking for handlers in this logger and its parents in the logger hierarchy. " +"Returns ``True`` if a handler was found, else ``False``. The method stops " +"searching up the hierarchy whenever a logger with the 'propagate' attribute " +"set to False is found - that will be the last logger which is checked for " +"the existence of handlers." +msgstr "" + +#: ../Doc/library/logging.rst:330 +msgid "Logging Levels" +msgstr "" + +#: ../Doc/library/logging.rst:332 +msgid "" +"The numeric values of logging levels are given in the following table. These " +"are primarily of interest if you want to define your own levels, and need " +"them to have specific values relative to the predefined levels. If you " +"define a level with the same numeric value, it overwrites the predefined " +"value; the predefined name is lost." +msgstr "" + +#: ../Doc/library/logging.rst:339 +msgid "Level" +msgstr "" + +#: ../Doc/library/logging.rst:339 +msgid "Numeric value" +msgstr "" + +#: ../Doc/library/logging.rst:341 +msgid "``CRITICAL``" +msgstr "" + +#: ../Doc/library/logging.rst:341 +msgid "50" +msgstr "" + +#: ../Doc/library/logging.rst:343 +msgid "``ERROR``" +msgstr "" + +#: ../Doc/library/logging.rst:343 +msgid "40" +msgstr "" + +#: ../Doc/library/logging.rst:345 +msgid "``WARNING``" +msgstr "" + +#: ../Doc/library/logging.rst:345 +msgid "30" +msgstr "" + +#: ../Doc/library/logging.rst:347 +msgid "``INFO``" +msgstr "" + +#: ../Doc/library/logging.rst:347 +msgid "20" +msgstr "" + +#: ../Doc/library/logging.rst:349 +msgid "``DEBUG``" +msgstr "" + +#: ../Doc/library/logging.rst:349 +msgid "10" +msgstr "" + +#: ../Doc/library/logging.rst:351 +msgid "``NOTSET``" +msgstr "" + +#: ../Doc/library/logging.rst:358 +msgid "Handler Objects" +msgstr "" + +#: ../Doc/library/logging.rst:360 +msgid "" +"Handlers have the following attributes and methods. Note that :class:" +"`Handler` is never instantiated directly; this class acts as a base for more " +"useful subclasses. However, the :meth:`__init__` method in subclasses needs " +"to call :meth:`Handler.__init__`." +msgstr "" + +#: ../Doc/library/logging.rst:368 +msgid "" +"Initializes the :class:`Handler` instance by setting its level, setting the " +"list of filters to the empty list and creating a lock (using :meth:" +"`createLock`) for serializing access to an I/O mechanism." +msgstr "" + +#: ../Doc/library/logging.rst:375 +msgid "" +"Initializes a thread lock which can be used to serialize access to " +"underlying I/O functionality which may not be threadsafe." +msgstr "" + +#: ../Doc/library/logging.rst:381 +msgid "Acquires the thread lock created with :meth:`createLock`." +msgstr "" + +#: ../Doc/library/logging.rst:386 +msgid "Releases the thread lock acquired with :meth:`acquire`." +msgstr "" + +#: ../Doc/library/logging.rst:391 +msgid "" +"Sets the threshold for this handler to *lvl*. Logging messages which are " +"less severe than *lvl* will be ignored. When a handler is created, the level " +"is set to :const:`NOTSET` (which causes all messages to be processed)." +msgstr "" + +#: ../Doc/library/logging.rst:397 +msgid "" +"The *lvl* parameter now accepts a string representation of the level such as " +"'INFO' as an alternative to the integer constants such as :const:`INFO`." +msgstr "" + +#: ../Doc/library/logging.rst:405 +msgid "Sets the :class:`Formatter` for this handler to *form*." +msgstr "" + +#: ../Doc/library/logging.rst:410 +msgid "Adds the specified filter *filt* to this handler." +msgstr "" + +#: ../Doc/library/logging.rst:415 +msgid "Removes the specified filter *filt* from this handler." +msgstr "" + +#: ../Doc/library/logging.rst:420 +msgid "" +"Applies this handler's filters to the record and returns a true value if the " +"record is to be processed. The filters are consulted in turn, until one of " +"them returns a false value. If none of them return a false value, the record " +"will be emitted. If one returns a false value, the handler will not emit the " +"record." +msgstr "" + +#: ../Doc/library/logging.rst:429 +msgid "" +"Ensure all logging output has been flushed. This version does nothing and is " +"intended to be implemented by subclasses." +msgstr "" + +#: ../Doc/library/logging.rst:435 +msgid "" +"Tidy up any resources used by the handler. This version does no output but " +"removes the handler from an internal list of handlers which is closed when :" +"func:`shutdown` is called. Subclasses should ensure that this gets called " +"from overridden :meth:`close` methods." +msgstr "" + +#: ../Doc/library/logging.rst:443 +msgid "" +"Conditionally emits the specified logging record, depending on filters which " +"may have been added to the handler. Wraps the actual emission of the record " +"with acquisition/release of the I/O thread lock." +msgstr "" + +#: ../Doc/library/logging.rst:450 +msgid "" +"This method should be called from handlers when an exception is encountered " +"during an :meth:`emit` call. If the module-level attribute " +"``raiseExceptions`` is ``False``, exceptions get silently ignored. This is " +"what is mostly wanted for a logging system - most users will not care about " +"errors in the logging system, they are more interested in application " +"errors. You could, however, replace this with a custom handler if you wish. " +"The specified record is the one which was being processed when the exception " +"occurred. (The default value of ``raiseExceptions`` is ``True``, as that is " +"more useful during development)." +msgstr "" + +#: ../Doc/library/logging.rst:463 +msgid "" +"Do formatting for a record - if a formatter is set, use it. Otherwise, use " +"the default formatter for the module." +msgstr "" + +#: ../Doc/library/logging.rst:469 +msgid "" +"Do whatever it takes to actually log the specified logging record. This " +"version is intended to be implemented by subclasses and so raises a :exc:" +"`NotImplementedError`." +msgstr "" + +#: ../Doc/library/logging.rst:473 +msgid "" +"For a list of handlers included as standard, see :mod:`logging.handlers`." +msgstr "" + +#: ../Doc/library/logging.rst:478 +msgid "Formatter Objects" +msgstr "" + +#: ../Doc/library/logging.rst:482 +msgid "" +":class:`Formatter` objects have the following attributes and methods. They " +"are responsible for converting a :class:`LogRecord` to (usually) a string " +"which can be interpreted by either a human or an external system. The base :" +"class:`Formatter` allows a formatting string to be specified. If none is " +"supplied, the default value of ``'%(message)s'`` is used, which just " +"includes the message in the logging call. To have additional items of " +"information in the formatted output (such as a timestamp), keep reading." +msgstr "" + +#: ../Doc/library/logging.rst:490 +msgid "" +"A Formatter can be initialized with a format string which makes use of " +"knowledge of the :class:`LogRecord` attributes - such as the default value " +"mentioned above making use of the fact that the user's message and arguments " +"are pre-formatted into a :class:`LogRecord`'s *message* attribute. This " +"format string contains standard Python %-style mapping keys. See section :" +"ref:`old-string-formatting` for more information on string formatting." +msgstr "" + +#: ../Doc/library/logging.rst:497 +msgid "" +"The useful mapping keys in a :class:`LogRecord` are given in the section on :" +"ref:`logrecord-attributes`." +msgstr "" + +#: ../Doc/library/logging.rst:503 +msgid "" +"Returns a new instance of the :class:`Formatter` class. The instance is " +"initialized with a format string for the message as a whole, as well as a " +"format string for the date/time portion of a message. If no *fmt* is " +"specified, ``'%(message)s'`` is used. If no *datefmt* is specified, the " +"ISO8601 date format is used." +msgstr "" + +#: ../Doc/library/logging.rst:509 +msgid "" +"The *style* parameter can be one of '%', '{' or '$' and determines how the " +"format string will be merged with its data: using one of %-formatting, :meth:" +"`str.format` or :class:`string.Template`. See :ref:`formatting-styles` for " +"more information on using {- and $-formatting for log messages." +msgstr "" + +#: ../Doc/library/logging.rst:514 +msgid "The *style* parameter was added." +msgstr "" + +#: ../Doc/library/logging.rst:520 +msgid "" +"The record's attribute dictionary is used as the operand to a string " +"formatting operation. Returns the resulting string. Before formatting the " +"dictionary, a couple of preparatory steps are carried out. The *message* " +"attribute of the record is computed using *msg* % *args*. If the formatting " +"string contains ``'(asctime)'``, :meth:`formatTime` is called to format the " +"event time. If there is exception information, it is formatted using :meth:" +"`formatException` and appended to the message. Note that the formatted " +"exception information is cached in attribute *exc_text*. This is useful " +"because the exception information can be pickled and sent across the wire, " +"but you should be careful if you have more than one :class:`Formatter` " +"subclass which customizes the formatting of exception information. In this " +"case, you will have to clear the cached value after a formatter has done its " +"formatting, so that the next formatter to handle the event doesn't use the " +"cached value but recalculates it afresh." +msgstr "" + +#: ../Doc/library/logging.rst:536 +msgid "" +"If stack information is available, it's appended after the exception " +"information, using :meth:`formatStack` to transform it if necessary." +msgstr "" + +#: ../Doc/library/logging.rst:542 +msgid "" +"This method should be called from :meth:`format` by a formatter which wants " +"to make use of a formatted time. This method can be overridden in formatters " +"to provide for any specific requirement, but the basic behavior is as " +"follows: if *datefmt* (a string) is specified, it is used with :func:`time." +"strftime` to format the creation time of the record. Otherwise, the ISO8601 " +"format is used. The resulting string is returned." +msgstr "" + +#: ../Doc/library/logging.rst:550 +msgid "" +"This function uses a user-configurable function to convert the creation time " +"to a tuple. By default, :func:`time.localtime` is used; to change this for a " +"particular formatter instance, set the ``converter`` attribute to a function " +"with the same signature as :func:`time.localtime` or :func:`time.gmtime`. To " +"change it for all formatters, for example if you want all logging times to " +"be shown in GMT, set the ``converter`` attribute in the ``Formatter`` class." +msgstr "" + +#: ../Doc/library/logging.rst:558 +msgid "" +"Previously, the default ISO 8601 format was hard-coded as in this example: " +"``2010-09-06 22:38:15,292`` where the part before the comma is handled by a " +"strptime format string (``'%Y-%m-%d %H:%M:%S'``), and the part after the " +"comma is a millisecond value. Because strptime does not have a format " +"placeholder for milliseconds, the millisecond value is appended using " +"another format string, ``'%s,%03d'`` – and both of these format strings have " +"been hardcoded into this method. With the change, these strings are defined " +"as class-level attributes which can be overridden at the instance level when " +"desired. The names of the attributes are ``default_time_format`` (for the " +"strptime format string) and ``default_msec_format`` (for appending the " +"millisecond value)." +msgstr "" + +#: ../Doc/library/logging.rst:573 +msgid "" +"Formats the specified exception information (a standard exception tuple as " +"returned by :func:`sys.exc_info`) as a string. This default implementation " +"just uses :func:`traceback.print_exception`. The resulting string is " +"returned." +msgstr "" + +#: ../Doc/library/logging.rst:580 +msgid "" +"Formats the specified stack information (a string as returned by :func:" +"`traceback.print_stack`, but with the last newline removed) as a string. " +"This default implementation just returns the input value." +msgstr "" + +#: ../Doc/library/logging.rst:587 +msgid "Filter Objects" +msgstr "" + +#: ../Doc/library/logging.rst:589 +msgid "" +"``Filters`` can be used by ``Handlers`` and ``Loggers`` for more " +"sophisticated filtering than is provided by levels. The base filter class " +"only allows events which are below a certain point in the logger hierarchy. " +"For example, a filter initialized with 'A.B' will allow events logged by " +"loggers 'A.B', 'A.B.C', 'A.B.C.D', 'A.B.D' etc. but not 'A.BB', 'B.A.B' etc. " +"If initialized with the empty string, all events are passed." +msgstr "" + +#: ../Doc/library/logging.rst:599 +msgid "" +"Returns an instance of the :class:`Filter` class. If *name* is specified, it " +"names a logger which, together with its children, will have its events " +"allowed through the filter. If *name* is the empty string, allows every " +"event." +msgstr "" + +#: ../Doc/library/logging.rst:606 +msgid "" +"Is the specified record to be logged? Returns zero for no, nonzero for yes. " +"If deemed appropriate, the record may be modified in-place by this method." +msgstr "" + +#: ../Doc/library/logging.rst:610 +msgid "" +"Note that filters attached to handlers are consulted before an event is " +"emitted by the handler, whereas filters attached to loggers are consulted " +"whenever an event is logged (using :meth:`debug`, :meth:`info`, etc.), " +"before sending an event to handlers. This means that events which have been " +"generated by descendant loggers will not be filtered by a logger's filter " +"setting, unless the filter has also been applied to those descendant loggers." +msgstr "" + +#: ../Doc/library/logging.rst:617 +msgid "" +"You don't actually need to subclass ``Filter``: you can pass any instance " +"which has a ``filter`` method with the same semantics." +msgstr "" + +#: ../Doc/library/logging.rst:620 +msgid "" +"You don't need to create specialized ``Filter`` classes, or use other " +"classes with a ``filter`` method: you can use a function (or other callable) " +"as a filter. The filtering logic will check to see if the filter object has " +"a ``filter`` attribute: if it does, it's assumed to be a ``Filter`` and its :" +"meth:`~Filter.filter` method is called. Otherwise, it's assumed to be a " +"callable and called with the record as the single parameter. The returned " +"value should conform to that returned by :meth:`~Filter.filter`." +msgstr "" + +#: ../Doc/library/logging.rst:630 +msgid "" +"Although filters are used primarily to filter records based on more " +"sophisticated criteria than levels, they get to see every record which is " +"processed by the handler or logger they're attached to: this can be useful " +"if you want to do things like counting how many records were processed by a " +"particular logger or handler, or adding, changing or removing attributes in " +"the LogRecord being processed. Obviously changing the LogRecord needs to be " +"done with some care, but it does allow the injection of contextual " +"information into logs (see :ref:`filters-contextual`)." +msgstr "" + +#: ../Doc/library/logging.rst:642 +msgid "LogRecord Objects" +msgstr "" + +#: ../Doc/library/logging.rst:644 +msgid "" +":class:`LogRecord` instances are created automatically by the :class:" +"`Logger` every time something is logged, and can be created manually via :" +"func:`makeLogRecord` (for example, from a pickled event received over the " +"wire)." +msgstr "" + +#: ../Doc/library/logging.rst:652 +msgid "Contains all the information pertinent to the event being logged." +msgstr "" + +#: ../Doc/library/logging.rst:654 +msgid "" +"The primary information is passed in :attr:`msg` and :attr:`args`, which are " +"combined using ``msg % args`` to create the :attr:`message` field of the " +"record." +msgstr "" + +#: ../Doc/library/logging.rst:658 +msgid "" +"The name of the logger used to log the event represented by this LogRecord. " +"Note that this name will always have this value, even though it may be " +"emitted by a handler attached to a different (ancestor) logger." +msgstr "" + +#: ../Doc/library/logging.rst:662 +msgid "" +"The numeric level of the logging event (one of DEBUG, INFO etc.) Note that " +"this is converted to *two* attributes of the LogRecord: ``levelno`` for the " +"numeric value and ``levelname`` for the corresponding level name." +msgstr "" + +#: ../Doc/library/logging.rst:666 +msgid "The full pathname of the source file where the logging call was made." +msgstr "" + +#: ../Doc/library/logging.rst:668 +msgid "The line number in the source file where the logging call was made." +msgstr "" + +#: ../Doc/library/logging.rst:670 +msgid "" +"The event description message, possibly a format string with placeholders " +"for variable data." +msgstr "" + +#: ../Doc/library/logging.rst:672 +msgid "" +"Variable data to merge into the *msg* argument to obtain the event " +"description." +msgstr "" + +#: ../Doc/library/logging.rst:674 +msgid "" +"An exception tuple with the current exception information, or *None* if no " +"exception information is available." +msgstr "" + +#: ../Doc/library/logging.rst:676 +msgid "" +"The name of the function or method from which the logging call was invoked." +msgstr "" + +#: ../Doc/library/logging.rst:678 +msgid "" +"A text string representing stack information from the base of the stack in " +"the current thread, up to the logging call." +msgstr "" + +#: ../Doc/library/logging.rst:683 +msgid "" +"Returns the message for this :class:`LogRecord` instance after merging any " +"user-supplied arguments with the message. If the user-supplied message " +"argument to the logging call is not a string, :func:`str` is called on it to " +"convert it to a string. This allows use of user-defined classes as messages, " +"whose ``__str__`` method can return the actual format string to be used." +msgstr "" + +#: ../Doc/library/logging.rst:690 +msgid "" +"The creation of a ``LogRecord`` has been made more configurable by providing " +"a factory which is used to create the record. The factory can be set using :" +"func:`getLogRecordFactory` and :func:`setLogRecordFactory` (see this for the " +"factory's signature)." +msgstr "" + +#: ../Doc/library/logging.rst:696 +msgid "" +"This functionality can be used to inject your own values into a LogRecord at " +"creation time. You can use the following pattern::" +msgstr "" + +#: ../Doc/library/logging.rst:708 +msgid "" +"With this pattern, multiple factories could be chained, and as long as they " +"don't overwrite each other's attributes or unintentionally overwrite the " +"standard attributes listed above, there should be no surprises." +msgstr "" + +#: ../Doc/library/logging.rst:717 +msgid "LogRecord attributes" +msgstr "" + +#: ../Doc/library/logging.rst:719 +msgid "" +"The LogRecord has a number of attributes, most of which are derived from the " +"parameters to the constructor. (Note that the names do not always correspond " +"exactly between the LogRecord constructor parameters and the LogRecord " +"attributes.) These attributes can be used to merge data from the record into " +"the format string. The following table lists (in alphabetical order) the " +"attribute names, their meanings and the corresponding placeholder in a %-" +"style format string." +msgstr "" + +#: ../Doc/library/logging.rst:727 +msgid "" +"If you are using {}-formatting (:func:`str.format`), you can use ``{attrname}" +"`` as the placeholder in the format string. If you are using $-formatting (:" +"class:`string.Template`), use the form ``${attrname}``. In both cases, of " +"course, replace ``attrname`` with the actual attribute name you want to use." +msgstr "" + +#: ../Doc/library/logging.rst:733 +msgid "" +"In the case of {}-formatting, you can specify formatting flags by placing " +"them after the attribute name, separated from it with a colon. For example: " +"a placeholder of ``{msecs:03d}`` would format a millisecond value of ``4`` " +"as ``004``. Refer to the :meth:`str.format` documentation for full details " +"on the options available to you." +msgstr "" + +#: ../Doc/library/logging.rst:740 +msgid "Attribute name" +msgstr "" + +#: ../Doc/library/logging.rst:740 ../Doc/library/logging.rst:1104 +#: ../Doc/library/ossaudiodev.rst:201 ../Doc/library/struct.rst:186 +msgid "Format" +msgstr "" + +#: ../Doc/library/logging.rst:742 +msgid "args" +msgstr "" + +#: ../Doc/library/logging.rst:742 ../Doc/library/logging.rst:756 +#: ../Doc/library/logging.rst:784 ../Doc/library/logging.rst:802 +msgid "You shouldn't need to format this yourself." +msgstr "" + +#: ../Doc/library/logging.rst:742 +msgid "" +"The tuple of arguments merged into ``msg`` to produce ``message``, or a dict " +"whose values are used for the merge (when there is only one argument, and it " +"is a dictionary)." +msgstr "" + +#: ../Doc/library/logging.rst:747 +msgid "asctime" +msgstr "" + +#: ../Doc/library/logging.rst:747 +msgid "``%(asctime)s``" +msgstr "" + +#: ../Doc/library/logging.rst:747 +msgid "" +"Human-readable time when the :class:`LogRecord` was created. By default " +"this is of the form '2003-07-08 16:49:45,896' (the numbers after the comma " +"are millisecond portion of the time)." +msgstr "" + +#: ../Doc/library/logging.rst:753 +msgid "created" +msgstr "" + +#: ../Doc/library/logging.rst:753 +msgid "``%(created)f``" +msgstr "" + +#: ../Doc/library/logging.rst:753 +msgid "" +"Time when the :class:`LogRecord` was created (as returned by :func:`time." +"time`)." +msgstr "" + +#: ../Doc/library/logging.rst:756 +msgid "exc_info" +msgstr "" + +#: ../Doc/library/logging.rst:756 +msgid "" +"Exception tuple (à la ``sys.exc_info``) or, if no exception has occurred, " +"*None*." +msgstr "" + +#: ../Doc/library/logging.rst:759 ../Doc/library/tracemalloc.rst:522 +msgid "filename" +msgstr "" + +#: ../Doc/library/logging.rst:759 +msgid "``%(filename)s``" +msgstr "" + +#: ../Doc/library/logging.rst:759 +msgid "Filename portion of ``pathname``." +msgstr "" + +#: ../Doc/library/logging.rst:761 +msgid "funcName" +msgstr "" + +#: ../Doc/library/logging.rst:761 +msgid "``%(funcName)s``" +msgstr "" + +#: ../Doc/library/logging.rst:761 +msgid "Name of function containing the logging call." +msgstr "" + +#: ../Doc/library/logging.rst:763 +msgid "levelname" +msgstr "" + +#: ../Doc/library/logging.rst:763 +msgid "``%(levelname)s``" +msgstr "" + +#: ../Doc/library/logging.rst:763 +msgid "" +"Text logging level for the message (``'DEBUG'``, ``'INFO'``, ``'WARNING'``, " +"``'ERROR'``, ``'CRITICAL'``)." +msgstr "" + +#: ../Doc/library/logging.rst:767 +msgid "levelno" +msgstr "" + +#: ../Doc/library/logging.rst:767 +msgid "``%(levelno)s``" +msgstr "" + +#: ../Doc/library/logging.rst:767 +msgid "" +"Numeric logging level for the message (:const:`DEBUG`, :const:`INFO`, :const:" +"`WARNING`, :const:`ERROR`, :const:`CRITICAL`)." +msgstr "" + +#: ../Doc/library/logging.rst:772 +msgid "lineno" +msgstr "" + +#: ../Doc/library/logging.rst:772 +msgid "``%(lineno)d``" +msgstr "" + +#: ../Doc/library/logging.rst:772 +msgid "Source line number where the logging call was issued (if available)." +msgstr "" + +#: ../Doc/library/logging.rst:775 +msgid "``%(module)s``" +msgstr "" + +#: ../Doc/library/logging.rst:775 +msgid "Module (name portion of ``filename``)." +msgstr "" + +#: ../Doc/library/logging.rst:777 +msgid "msecs" +msgstr "" + +#: ../Doc/library/logging.rst:777 +msgid "``%(msecs)d``" +msgstr "" + +#: ../Doc/library/logging.rst:777 +msgid "" +"Millisecond portion of the time when the :class:`LogRecord` was created." +msgstr "" + +#: ../Doc/library/logging.rst:780 +msgid "message" +msgstr "" + +#: ../Doc/library/logging.rst:780 +msgid "``%(message)s``" +msgstr "" + +#: ../Doc/library/logging.rst:780 +msgid "" +"The logged message, computed as ``msg % args``. This is set when :meth:" +"`Formatter.format` is invoked." +msgstr "" + +#: ../Doc/library/logging.rst:784 +msgid "msg" +msgstr "" + +#: ../Doc/library/logging.rst:784 +msgid "" +"The format string passed in the original logging call. Merged with ``args`` " +"to produce ``message``, or an arbitrary object (see :ref:`arbitrary-object-" +"messages`)." +msgstr "" + +#: ../Doc/library/logging.rst:789 +msgid "``%(name)s``" +msgstr "" + +#: ../Doc/library/logging.rst:789 +msgid "Name of the logger used to log the call." +msgstr "" + +#: ../Doc/library/logging.rst:791 +msgid "pathname" +msgstr "" + +#: ../Doc/library/logging.rst:791 +msgid "``%(pathname)s``" +msgstr "" + +#: ../Doc/library/logging.rst:791 +msgid "" +"Full pathname of the source file where the logging call was issued (if " +"available)." +msgstr "" + +#: ../Doc/library/logging.rst:794 +msgid "process" +msgstr "" + +#: ../Doc/library/logging.rst:794 +msgid "``%(process)d``" +msgstr "" + +#: ../Doc/library/logging.rst:794 +msgid "Process ID (if available)." +msgstr "" + +#: ../Doc/library/logging.rst:796 +msgid "processName" +msgstr "" + +#: ../Doc/library/logging.rst:796 +msgid "``%(processName)s``" +msgstr "" + +#: ../Doc/library/logging.rst:796 +msgid "Process name (if available)." +msgstr "" + +#: ../Doc/library/logging.rst:798 +msgid "relativeCreated" +msgstr "" + +#: ../Doc/library/logging.rst:798 +msgid "``%(relativeCreated)d``" +msgstr "" + +#: ../Doc/library/logging.rst:798 +msgid "" +"Time in milliseconds when the LogRecord was created, relative to the time " +"the logging module was loaded." +msgstr "" + +#: ../Doc/library/logging.rst:802 +msgid "stack_info" +msgstr "" + +#: ../Doc/library/logging.rst:802 +msgid "" +"Stack frame information (where available) from the bottom of the stack in " +"the current thread, up to and including the stack frame of the logging call " +"which resulted in the creation of this record." +msgstr "" + +#: ../Doc/library/logging.rst:808 +msgid "thread" +msgstr "" + +#: ../Doc/library/logging.rst:808 +msgid "``%(thread)d``" +msgstr "" + +#: ../Doc/library/logging.rst:808 +msgid "Thread ID (if available)." +msgstr "" + +#: ../Doc/library/logging.rst:810 +msgid "threadName" +msgstr "" + +#: ../Doc/library/logging.rst:810 +msgid "``%(threadName)s``" +msgstr "" + +#: ../Doc/library/logging.rst:810 +msgid "Thread name (if available)." +msgstr "" + +#: ../Doc/library/logging.rst:813 +msgid "*processName* was added." +msgstr "" + +#: ../Doc/library/logging.rst:820 +msgid "LoggerAdapter Objects" +msgstr "" + +#: ../Doc/library/logging.rst:822 +msgid "" +":class:`LoggerAdapter` instances are used to conveniently pass contextual " +"information into logging calls. For a usage example, see the section on :ref:" +"`adding contextual information to your logging output `." +msgstr "" + +#: ../Doc/library/logging.rst:828 +msgid "" +"Returns an instance of :class:`LoggerAdapter` initialized with an " +"underlying :class:`Logger` instance and a dict-like object." +msgstr "" + +#: ../Doc/library/logging.rst:833 +msgid "" +"Modifies the message and/or keyword arguments passed to a logging call in " +"order to insert contextual information. This implementation takes the object " +"passed as *extra* to the constructor and adds it to *kwargs* using key " +"'extra'. The return value is a (*msg*, *kwargs*) tuple which has the " +"(possibly modified) versions of the arguments passed in." +msgstr "" + +#: ../Doc/library/logging.rst:839 +msgid "" +"In addition to the above, :class:`LoggerAdapter` supports the following " +"methods of :class:`Logger`: :meth:`~Logger.debug`, :meth:`~Logger.info`, :" +"meth:`~Logger.warning`, :meth:`~Logger.error`, :meth:`~Logger.exception`, :" +"meth:`~Logger.critical`, :meth:`~Logger.log`, :meth:`~Logger.isEnabledFor`, :" +"meth:`~Logger.getEffectiveLevel`, :meth:`~Logger.setLevel` and :meth:" +"`~Logger.hasHandlers`. These methods have the same signatures as their " +"counterparts in :class:`Logger`, so you can use the two types of instances " +"interchangeably." +msgstr "" + +#: ../Doc/library/logging.rst:848 +msgid "" +"The :meth:`~Logger.isEnabledFor`, :meth:`~Logger.getEffectiveLevel`, :meth:" +"`~Logger.setLevel` and :meth:`~Logger.hasHandlers` methods were added to :" +"class:`LoggerAdapter`. These methods delegate to the underlying logger." +msgstr "" + +#: ../Doc/library/logging.rst:855 +msgid "Thread Safety" +msgstr "" + +#: ../Doc/library/logging.rst:857 +msgid "" +"The logging module is intended to be thread-safe without any special work " +"needing to be done by its clients. It achieves this though using threading " +"locks; there is one lock to serialize access to the module's shared data, " +"and each handler also creates a lock to serialize access to its underlying I/" +"O." +msgstr "" + +#: ../Doc/library/logging.rst:862 +msgid "" +"If you are implementing asynchronous signal handlers using the :mod:`signal` " +"module, you may not be able to use logging from within such handlers. This " +"is because lock implementations in the :mod:`threading` module are not " +"always re-entrant, and so cannot be invoked from such signal handlers." +msgstr "" + +#: ../Doc/library/logging.rst:869 +msgid "Module-Level Functions" +msgstr "" + +#: ../Doc/library/logging.rst:871 +msgid "" +"In addition to the classes described above, there are a number of module- " +"level functions." +msgstr "" + +#: ../Doc/library/logging.rst:877 +msgid "" +"Return a logger with the specified name or, if name is ``None``, return a " +"logger which is the root logger of the hierarchy. If specified, the name is " +"typically a dot-separated hierarchical name like *'a'*, *'a.b'* or *'a.b.c." +"d'*. Choice of these names is entirely up to the developer who is using " +"logging." +msgstr "" + +#: ../Doc/library/logging.rst:882 +msgid "" +"All calls to this function with a given name return the same logger " +"instance. This means that logger instances never need to be passed between " +"different parts of an application." +msgstr "" + +#: ../Doc/library/logging.rst:889 +msgid "" +"Return either the standard :class:`Logger` class, or the last class passed " +"to :func:`setLoggerClass`. This function may be called from within a new " +"class definition, to ensure that installing a customized :class:`Logger` " +"class will not undo customizations already applied by other code. For " +"example::" +msgstr "" + +#: ../Doc/library/logging.rst:900 +msgid "Return a callable which is used to create a :class:`LogRecord`." +msgstr "" + +#: ../Doc/library/logging.rst:902 +msgid "" +"This function has been provided, along with :func:`setLogRecordFactory`, to " +"allow developers more control over how the :class:`LogRecord` representing a " +"logging event is constructed." +msgstr "" + +#: ../Doc/library/logging.rst:907 +msgid "" +"See :func:`setLogRecordFactory` for more information about the how the " +"factory is called." +msgstr "" + +#: ../Doc/library/logging.rst:912 +msgid "" +"Logs a message with level :const:`DEBUG` on the root logger. The *msg* is " +"the message format string, and the *args* are the arguments which are merged " +"into *msg* using the string formatting operator. (Note that this means that " +"you can use keywords in the format string, together with a single dictionary " +"argument.)" +msgstr "" + +#: ../Doc/library/logging.rst:917 +msgid "" +"There are three keyword arguments in *kwargs* which are inspected: " +"*exc_info* which, if it does not evaluate as false, causes exception " +"information to be added to the logging message. If an exception tuple (in " +"the format returned by :func:`sys.exc_info`) is provided, it is used; " +"otherwise, :func:`sys.exc_info` is called to get the exception information." +msgstr "" + +#: ../Doc/library/logging.rst:941 +msgid "" +"The third optional keyword argument is *extra* which can be used to pass a " +"dictionary which is used to populate the __dict__ of the LogRecord created " +"for the logging event with user-defined attributes. These custom attributes " +"can then be used as you like. For example, they could be incorporated into " +"logged messages. For example::" +msgstr "" + +#: ../Doc/library/logging.rst:952 +msgid "would print something like::" +msgstr "" + +#: ../Doc/library/logging.rst:979 +msgid "" +"Logs a message with level :const:`INFO` on the root logger. The arguments " +"are interpreted as for :func:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:985 +msgid "" +"Logs a message with level :const:`WARNING` on the root logger. The arguments " +"are interpreted as for :func:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:988 +msgid "" +"There is an obsolete function ``warn`` which is functionally identical to " +"``warning``. As ``warn`` is deprecated, please do not use it - use " +"``warning`` instead." +msgstr "" + +#: ../Doc/library/logging.rst:995 +msgid "" +"Logs a message with level :const:`ERROR` on the root logger. The arguments " +"are interpreted as for :func:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:1001 +msgid "" +"Logs a message with level :const:`CRITICAL` on the root logger. The " +"arguments are interpreted as for :func:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:1007 +msgid "" +"Logs a message with level :const:`ERROR` on the root logger. The arguments " +"are interpreted as for :func:`debug`. Exception info is added to the logging " +"message. This function should only be called from an exception handler." +msgstr "" + +#: ../Doc/library/logging.rst:1013 +msgid "" +"Logs a message with level *level* on the root logger. The other arguments " +"are interpreted as for :func:`debug`." +msgstr "" + +#: ../Doc/library/logging.rst:1016 +msgid "" +"The above module-level convenience functions, which delegate to the root " +"logger, call :func:`basicConfig` to ensure that at least one handler is " +"available. Because of this, they should *not* be used in threads, in " +"versions of Python earlier than 2.7.1 and 3.2, unless at least one handler " +"has been added to the root logger *before* the threads are started. In " +"earlier versions of Python, due to a thread safety shortcoming in :func:" +"`basicConfig`, this can (under rare circumstances) lead to handlers being " +"added multiple times to the root logger, which can in turn lead to multiple " +"messages for the same event." +msgstr "" + +#: ../Doc/library/logging.rst:1028 +msgid "" +"Provides an overriding level *lvl* for all loggers which takes precedence " +"over the logger's own level. When the need arises to temporarily throttle " +"logging output down across the whole application, this function can be " +"useful. Its effect is to disable all logging calls of severity *lvl* and " +"below, so that if you call it with a value of INFO, then all INFO and DEBUG " +"events would be discarded, whereas those of severity WARNING and above would " +"be processed according to the logger's effective level. If ``logging." +"disable(logging.NOTSET)`` is called, it effectively removes this overriding " +"level, so that logging output again depends on the effective levels of " +"individual loggers." +msgstr "" + +#: ../Doc/library/logging.rst:1042 +msgid "" +"Associates level *lvl* with text *levelName* in an internal dictionary, " +"which is used to map numeric levels to a textual representation, for example " +"when a :class:`Formatter` formats a message. This function can also be used " +"to define your own levels. The only constraints are that all levels used " +"must be registered using this function, levels should be positive integers " +"and they should increase in increasing order of severity." +msgstr "" + +#: ../Doc/library/logging.rst:1049 +msgid "" +"If you are thinking of defining your own levels, please see the section on :" +"ref:`custom-levels`." +msgstr "" + +#: ../Doc/library/logging.rst:1054 +msgid "" +"Returns the textual representation of logging level *lvl*. If the level is " +"one of the predefined levels :const:`CRITICAL`, :const:`ERROR`, :const:" +"`WARNING`, :const:`INFO` or :const:`DEBUG` then you get the corresponding " +"string. If you have associated levels with names using :func:`addLevelName` " +"then the name you have associated with *lvl* is returned. If a numeric value " +"corresponding to one of the defined levels is passed in, the corresponding " +"string representation is returned. Otherwise, the string 'Level %s' % lvl is " +"returned." +msgstr "" + +#: ../Doc/library/logging.rst:1062 +msgid "" +"Levels are internally integers (as they need to be compared in the logging " +"logic). This function is used to convert between an integer level and the " +"level name displayed in the formatted log output by means of the ``" +"%(levelname)s`` format specifier (see :ref:`logrecord-attributes`)." +msgstr "" + +#: ../Doc/library/logging.rst:1067 +msgid "" +"In Python versions earlier than 3.4, this function could also be passed a " +"text level, and would return the corresponding numeric value of the level. " +"This undocumented behaviour was considered a mistake, and was removed in " +"Python 3.4, but reinstated in 3.4.2 due to retain backward compatibility." +msgstr "" + +#: ../Doc/library/logging.rst:1075 +msgid "" +"Creates and returns a new :class:`LogRecord` instance whose attributes are " +"defined by *attrdict*. This function is useful for taking a pickled :class:" +"`LogRecord` attribute dictionary, sent over a socket, and reconstituting it " +"as a :class:`LogRecord` instance at the receiving end." +msgstr "" + +#: ../Doc/library/logging.rst:1083 +msgid "" +"Does basic configuration for the logging system by creating a :class:" +"`StreamHandler` with a default :class:`Formatter` and adding it to the root " +"logger. The functions :func:`debug`, :func:`info`, :func:`warning`, :func:" +"`error` and :func:`critical` will call :func:`basicConfig` automatically if " +"no handlers are defined for the root logger." +msgstr "" + +#: ../Doc/library/logging.rst:1089 +msgid "" +"This function does nothing if the root logger already has handlers " +"configured for it." +msgstr "" + +#: ../Doc/library/logging.rst:1092 +msgid "" +"This function should be called from the main thread before other threads are " +"started. In versions of Python prior to 2.7.1 and 3.2, if this function is " +"called from multiple threads, it is possible (in rare circumstances) that a " +"handler will be added to the root logger more than once, leading to " +"unexpected results such as messages being duplicated in the log." +msgstr "" + +#: ../Doc/library/logging.rst:1099 +msgid "The following keyword arguments are supported." +msgstr "" + +#: ../Doc/library/logging.rst:1106 +msgid "``filename``" +msgstr "" + +#: ../Doc/library/logging.rst:1106 +msgid "" +"Specifies that a FileHandler be created, using the specified filename, " +"rather than a StreamHandler." +msgstr "" + +#: ../Doc/library/logging.rst:1110 +msgid "``filemode``" +msgstr "" + +#: ../Doc/library/logging.rst:1110 +msgid "" +"Specifies the mode to open the file, if filename is specified (if filemode " +"is unspecified, it defaults to 'a')." +msgstr "" + +#: ../Doc/library/logging.rst:1114 +msgid "``format``" +msgstr "" + +#: ../Doc/library/logging.rst:1114 +msgid "Use the specified format string for the handler." +msgstr "" + +#: ../Doc/library/logging.rst:1117 +msgid "``datefmt``" +msgstr "" + +#: ../Doc/library/logging.rst:1117 +msgid "Use the specified date/time format." +msgstr "" + +#: ../Doc/library/logging.rst:1119 +msgid "``style``" +msgstr "" + +#: ../Doc/library/logging.rst:1119 +msgid "" +"If ``format`` is specified, use this style for the format string. One of " +"'%', '{' or '$' for %-formatting, :meth:`str.format` or :class:`string." +"Template` respectively, and defaulting to '%' if not specified." +msgstr "" + +#: ../Doc/library/logging.rst:1125 +msgid "``level``" +msgstr "" + +#: ../Doc/library/logging.rst:1125 +msgid "Set the root logger level to the specified level." +msgstr "" + +#: ../Doc/library/logging.rst:1128 +msgid "``stream``" +msgstr "" + +#: ../Doc/library/logging.rst:1128 +msgid "" +"Use the specified stream to initialize the StreamHandler. Note that this " +"argument is incompatible with 'filename' - if both are present, a " +"``ValueError`` is raised." +msgstr "" + +#: ../Doc/library/logging.rst:1133 +msgid "``handlers``" +msgstr "" + +#: ../Doc/library/logging.rst:1133 +msgid "" +"If specified, this should be an iterable of already created handlers to add " +"to the root logger. Any handlers which don't already have a formatter set " +"will be assigned the default formatter created in this function. Note that " +"this argument is incompatible with 'filename' or 'stream' - if both are " +"present, a ``ValueError`` is raised." +msgstr "" + +#: ../Doc/library/logging.rst:1143 +msgid "The ``style`` argument was added." +msgstr "" + +#: ../Doc/library/logging.rst:1146 +msgid "" +"The ``handlers`` argument was added. Additional checks were added to catch " +"situations where incompatible arguments are specified (e.g. ``handlers`` " +"together with ``stream`` or ``filename``, or ``stream`` together with " +"``filename``)." +msgstr "" + +#: ../Doc/library/logging.rst:1155 +msgid "" +"Informs the logging system to perform an orderly shutdown by flushing and " +"closing all handlers. This should be called at application exit and no " +"further use of the logging system should be made after this call." +msgstr "" + +#: ../Doc/library/logging.rst:1162 +msgid "" +"Tells the logging system to use the class *klass* when instantiating a " +"logger. The class should define :meth:`__init__` such that only a name " +"argument is required, and the :meth:`__init__` should call :meth:`Logger." +"__init__`. This function is typically called before any loggers are " +"instantiated by applications which need to use custom logger behavior." +msgstr "" + +#: ../Doc/library/logging.rst:1171 +msgid "Set a callable which is used to create a :class:`LogRecord`." +msgstr "" + +#: ../Doc/library/logging.rst:1173 +msgid "The factory callable to be used to instantiate a log record." +msgstr "" + +#: ../Doc/library/logging.rst:1175 +msgid "" +"This function has been provided, along with :func:`getLogRecordFactory`, to " +"allow developers more control over how the :class:`LogRecord` representing a " +"logging event is constructed." +msgstr "" + +#: ../Doc/library/logging.rst:1180 +msgid "The factory has the following signature:" +msgstr "" + +#: ../Doc/library/logging.rst:1182 +msgid "" +"``factory(name, level, fn, lno, msg, args, exc_info, func=None, sinfo=None, " +"**kwargs)``" +msgstr "" + +#: ../Doc/library/logging.rst:1184 +msgid "The logger name." +msgstr "" + +#: ../Doc/library/logging.rst:1185 +msgid "The logging level (numeric)." +msgstr "" + +#: ../Doc/library/logging.rst:1186 +msgid "The full pathname of the file where the logging call was made." +msgstr "" + +#: ../Doc/library/logging.rst:1187 +msgid "The line number in the file where the logging call was made." +msgstr "" + +#: ../Doc/library/logging.rst:1188 +msgid "The logging message." +msgstr "" + +#: ../Doc/library/logging.rst:1189 +msgid "The arguments for the logging message." +msgstr "" + +#: ../Doc/library/logging.rst:1190 +msgid "An exception tuple, or None." +msgstr "" + +#: ../Doc/library/logging.rst:1191 +msgid "The name of the function or method which invoked the logging call." +msgstr "" + +#: ../Doc/library/logging.rst:1193 +msgid "" +"A stack traceback such as is provided by :func:`traceback.print_stack`, " +"showing the call hierarchy." +msgstr "" + +#: ../Doc/library/logging.rst:1195 +msgid "Additional keyword arguments." +msgstr "" + +#: ../Doc/library/logging.rst:1199 +msgid "Module-Level Attributes" +msgstr "" + +#: ../Doc/library/logging.rst:1203 +msgid "" +"A \"handler of last resort\" is available through this attribute. This is a :" +"class:`StreamHandler` writing to ``sys.stderr`` with a level of ``WARNING``, " +"and is used to handle logging events in the absence of any logging " +"configuration. The end result is to just print the message to ``sys." +"stderr``. This replaces the earlier error message saying that \"no handlers " +"could be found for logger XYZ\". If you need the earlier behaviour for some " +"reason, ``lastResort`` can be set to ``None``." +msgstr "" + +#: ../Doc/library/logging.rst:1214 +msgid "Integration with the warnings module" +msgstr "" + +#: ../Doc/library/logging.rst:1216 +msgid "" +"The :func:`captureWarnings` function can be used to integrate :mod:`logging` " +"with the :mod:`warnings` module." +msgstr "" + +#: ../Doc/library/logging.rst:1221 +msgid "" +"This function is used to turn the capture of warnings by logging on and off." +msgstr "" + +#: ../Doc/library/logging.rst:1224 +msgid "" +"If *capture* is ``True``, warnings issued by the :mod:`warnings` module will " +"be redirected to the logging system. Specifically, a warning will be " +"formatted using :func:`warnings.formatwarning` and the resulting string " +"logged to a logger named ``'py.warnings'`` with a severity of :const:" +"`WARNING`." +msgstr "" + +#: ../Doc/library/logging.rst:1229 +msgid "" +"If *capture* is ``False``, the redirection of warnings to the logging system " +"will stop, and warnings will be redirected to their original destinations (i." +"e. those in effect before ``captureWarnings(True)`` was called)." +msgstr "" + +#: ../Doc/library/logging.rst:1237 ../Doc/library/logging.handlers.rst:1069 +msgid "Module :mod:`logging.config`" +msgstr "" + +#: ../Doc/library/logging.rst:1237 ../Doc/library/logging.handlers.rst:1070 +msgid "Configuration API for the logging module." +msgstr "" + +#: ../Doc/library/logging.rst:1240 ../Doc/library/logging.config.rst:807 +msgid "Module :mod:`logging.handlers`" +msgstr "" + +#: ../Doc/library/logging.rst:1240 ../Doc/library/logging.config.rst:808 +msgid "Useful handlers included with the logging module." +msgstr "" + +#: ../Doc/library/logging.rst:1244 +msgid ":pep:`282` - A Logging System" +msgstr "" + +#: ../Doc/library/logging.rst:1249 +msgid "" +"`Original Python logging package `_" +msgstr "" + +#: ../Doc/library/logging.rst:1247 +msgid "" +"This is the original source for the :mod:`logging` package. The version of " +"the package available from this site is suitable for use with Python 1.5.2, " +"2.1.x and 2.2.x, which do not include the :mod:`logging` package in the " +"standard library." +msgstr "" + +#: ../Doc/library/logging.config.rst:2 +msgid ":mod:`logging.config` --- Logging configuration" +msgstr "" + +#: ../Doc/library/logging.config.rst:10 +msgid "**Source code:** :source:`Lib/logging/config.py`" +msgstr "" + +#: ../Doc/library/logging.config.rst:14 ../Doc/library/logging.handlers.rst:14 +msgid "" +"This page contains only reference information. For tutorials, please see" +msgstr "" + +#: ../Doc/library/logging.config.rst:23 +msgid "This section describes the API for configuring the logging module." +msgstr "" + +#: ../Doc/library/logging.config.rst:28 +msgid "Configuration functions" +msgstr "" + +#: ../Doc/library/logging.config.rst:30 +msgid "" +"The following functions configure the logging module. They are located in " +"the :mod:`logging.config` module. Their use is optional --- you can " +"configure the logging module using these functions or by making calls to the " +"main API (defined in :mod:`logging` itself) and defining handlers which are " +"declared either in :mod:`logging` or :mod:`logging.handlers`." +msgstr "" + +#: ../Doc/library/logging.config.rst:38 +msgid "" +"Takes the logging configuration from a dictionary. The contents of this " +"dictionary are described in :ref:`logging-config-dictschema` below." +msgstr "" + +#: ../Doc/library/logging.config.rst:42 +msgid "" +"If an error is encountered during configuration, this function will raise a :" +"exc:`ValueError`, :exc:`TypeError`, :exc:`AttributeError` or :exc:" +"`ImportError` with a suitably descriptive message. The following is a " +"(possibly incomplete) list of conditions which will raise an error:" +msgstr "" + +#: ../Doc/library/logging.config.rst:48 +msgid "" +"A ``level`` which is not a string or which is a string not corresponding to " +"an actual logging level." +msgstr "" + +#: ../Doc/library/logging.config.rst:50 +msgid "A ``propagate`` value which is not a boolean." +msgstr "" + +#: ../Doc/library/logging.config.rst:51 +msgid "An id which does not have a corresponding destination." +msgstr "" + +#: ../Doc/library/logging.config.rst:52 +msgid "A non-existent handler id found during an incremental call." +msgstr "" + +#: ../Doc/library/logging.config.rst:53 +msgid "An invalid logger name." +msgstr "" + +#: ../Doc/library/logging.config.rst:54 +msgid "Inability to resolve to an internal or external object." +msgstr "" + +#: ../Doc/library/logging.config.rst:56 +msgid "" +"Parsing is performed by the :class:`DictConfigurator` class, whose " +"constructor is passed the dictionary used for configuration, and has a :meth:" +"`configure` method. The :mod:`logging.config` module has a callable " +"attribute :attr:`dictConfigClass` which is initially set to :class:" +"`DictConfigurator`. You can replace the value of :attr:`dictConfigClass` " +"with a suitable implementation of your own." +msgstr "" + +#: ../Doc/library/logging.config.rst:64 +msgid "" +":func:`dictConfig` calls :attr:`dictConfigClass` passing the specified " +"dictionary, and then calls the :meth:`configure` method on the returned " +"object to put the configuration into effect::" +msgstr "" + +#: ../Doc/library/logging.config.rst:71 +msgid "" +"For example, a subclass of :class:`DictConfigurator` could call " +"``DictConfigurator.__init__()`` in its own :meth:`__init__()`, then set up " +"custom prefixes which would be usable in the subsequent :meth:`configure` " +"call. :attr:`dictConfigClass` would be bound to this new subclass, and then :" +"func:`dictConfig` could be called exactly as in the default, uncustomized " +"state." +msgstr "" + +#: ../Doc/library/logging.config.rst:82 +msgid "" +"Reads the logging configuration from a :mod:`configparser`\\-format file. " +"The format of the file should be as described in :ref:`logging-config-" +"fileformat`. This function can be called several times from an application, " +"allowing an end user to select from various pre-canned configurations (if " +"the developer provides a mechanism to present the choices and load the " +"chosen configuration)." +msgstr "" + +#: ../Doc/library/logging.config.rst:90 +msgid "" +"A filename, or a file-like object, or an instance derived from :class:" +"`~configparser.RawConfigParser`. If a ``RawConfigParser``-derived instance " +"is passed, it is used as is. Otherwise, a :class:`~configparser." +"Configparser` is instantiated, and the configuration read by it from the " +"object passed in ``fname``. If that has a :meth:`readline` method, it is " +"assumed to be a file-like object and read using :meth:`~configparser." +"ConfigParser.read_file`; otherwise, it is assumed to be a filename and " +"passed to :meth:`~configparser.ConfigParser.read`." +msgstr "" + +#: ../Doc/library/logging.config.rst:102 +msgid "" +"Defaults to be passed to the ConfigParser can be specified in this argument." +msgstr "" + +#: ../Doc/library/logging.config.rst:105 +msgid "" +"If specified as ``False``, loggers which exist when this call is made are " +"left enabled. The default is ``True`` because this enables old behaviour in " +"a backward- compatible way. This behaviour is to disable any existing " +"loggers unless they or their ancestors are explicitly named in the logging " +"configuration." +msgstr "" + +#: ../Doc/library/logging.config.rst:114 +msgid "" +"An instance of a subclass of :class:`~configparser.RawConfigParser` is now " +"accepted as a value for ``fname``. This facilitates:" +msgstr "" + +#: ../Doc/library/logging.config.rst:118 +msgid "" +"Use of a configuration file where logging configuration is just part of the " +"overall application configuration." +msgstr "" + +#: ../Doc/library/logging.config.rst:120 +msgid "" +"Use of a configuration read from a file, and then modified by the using " +"application (e.g. based on command-line parameters or other aspects of the " +"runtime environment) before being passed to ``fileConfig``." +msgstr "" + +#: ../Doc/library/logging.config.rst:126 +msgid "" +"Starts up a socket server on the specified port, and listens for new " +"configurations. If no port is specified, the module's default :const:" +"`DEFAULT_LOGGING_CONFIG_PORT` is used. Logging configurations will be sent " +"as a file suitable for processing by :func:`dictConfig` or :func:" +"`fileConfig`. Returns a :class:`~threading.Thread` instance on which you can " +"call :meth:`~threading.Thread.start` to start the server, and which you can :" +"meth:`~threading.Thread.join` when appropriate. To stop the server, call :" +"func:`stopListening`." +msgstr "" + +#: ../Doc/library/logging.config.rst:135 +msgid "" +"The ``verify`` argument, if specified, should be a callable which should " +"verify whether bytes received across the socket are valid and should be " +"processed. This could be done by encrypting and/or signing what is sent " +"across the socket, such that the ``verify`` callable can perform signature " +"verification and/or decryption. The ``verify`` callable is called with a " +"single argument - the bytes received across the socket - and should return " +"the bytes to be processed, or None to indicate that the bytes should be " +"discarded. The returned bytes could be the same as the passed in bytes (e.g. " +"when only verification is done), or they could be completely different " +"(perhaps if decryption were performed)." +msgstr "" + +#: ../Doc/library/logging.config.rst:146 +msgid "" +"To send a configuration to the socket, read in the configuration file and " +"send it to the socket as a sequence of bytes preceded by a four-byte length " +"string packed in binary using ``struct.pack('>L', n)``." +msgstr "" + +#: ../Doc/library/logging.config.rst:152 +msgid "" +"Because portions of the configuration are passed through :func:`eval`, use " +"of this function may open its users to a security risk. While the function " +"only binds to a socket on ``localhost``, and so does not accept connections " +"from remote machines, there are scenarios where untrusted code could be run " +"under the account of the process which calls :func:`listen`. Specifically, " +"if the process calling :func:`listen` runs on a multi-user machine where " +"users cannot trust each other, then a malicious user could arrange to run " +"essentially arbitrary code in a victim user's process, simply by connecting " +"to the victim's :func:`listen` socket and sending a configuration which runs " +"whatever code the attacker wants to have executed in the victim's process. " +"This is especially easy to do if the default port is used, but not hard even " +"if a different port is used). To avoid the risk of this happening, use the " +"``verify`` argument to :func:`listen` to prevent unrecognised configurations " +"from being applied." +msgstr "" + +#: ../Doc/library/logging.config.rst:168 +msgid "The ``verify`` argument was added." +msgstr "" + +#: ../Doc/library/logging.config.rst:173 +msgid "" +"If you want to send configurations to the listener which don't disable " +"existing loggers, you will need to use a JSON format for the configuration, " +"which will use :func:`dictConfig` for configuration. This method allows you " +"to specify ``disable_existing_loggers`` as ``False`` in the configuration " +"you send." +msgstr "" + +#: ../Doc/library/logging.config.rst:182 +msgid "" +"Stops the listening server which was created with a call to :func:`listen`. " +"This is typically called before calling :meth:`join` on the return value " +"from :func:`listen`." +msgstr "" + +#: ../Doc/library/logging.config.rst:190 +msgid "Configuration dictionary schema" +msgstr "" + +#: ../Doc/library/logging.config.rst:192 +msgid "" +"Describing a logging configuration requires listing the various objects to " +"create and the connections between them; for example, you may create a " +"handler named 'console' and then say that the logger named 'startup' will " +"send its messages to the 'console' handler. These objects aren't limited to " +"those provided by the :mod:`logging` module because you might write your own " +"formatter or handler class. The parameters to these classes may also need to " +"include external objects such as ``sys.stderr``. The syntax for describing " +"these objects and connections is defined in :ref:`logging-config-dict-" +"connections` below." +msgstr "" + +#: ../Doc/library/logging.config.rst:204 +msgid "Dictionary Schema Details" +msgstr "" + +#: ../Doc/library/logging.config.rst:206 +msgid "" +"The dictionary passed to :func:`dictConfig` must contain the following keys:" +msgstr "" + +#: ../Doc/library/logging.config.rst:209 +msgid "" +"*version* - to be set to an integer value representing the schema version. " +"The only valid value at present is 1, but having this key allows the schema " +"to evolve while still preserving backwards compatibility." +msgstr "" + +#: ../Doc/library/logging.config.rst:214 +msgid "" +"All other keys are optional, but if present they will be interpreted as " +"described below. In all cases below where a 'configuring dict' is " +"mentioned, it will be checked for the special ``'()'`` key to see if a " +"custom instantiation is required. If so, the mechanism described in :ref:" +"`logging-config-dict-userdef` below is used to create an instance; " +"otherwise, the context is used to determine what to instantiate." +msgstr "" + +#: ../Doc/library/logging.config.rst:221 +msgid "" +"*formatters* - the corresponding value will be a dict in which each key is a " +"formatter id and each value is a dict describing how to configure the " +"corresponding :class:`~logging.Formatter` instance." +msgstr "" + +#: ../Doc/library/logging.config.rst:225 +msgid "" +"The configuring dict is searched for keys ``format`` and ``datefmt`` (with " +"defaults of ``None``) and these are used to construct a :class:`~logging." +"Formatter` instance." +msgstr "" + +#: ../Doc/library/logging.config.rst:229 +msgid "" +"*filters* - the corresponding value will be a dict in which each key is a " +"filter id and each value is a dict describing how to configure the " +"corresponding Filter instance." +msgstr "" + +#: ../Doc/library/logging.config.rst:233 +msgid "" +"The configuring dict is searched for the key ``name`` (defaulting to the " +"empty string) and this is used to construct a :class:`logging.Filter` " +"instance." +msgstr "" + +#: ../Doc/library/logging.config.rst:237 +msgid "" +"*handlers* - the corresponding value will be a dict in which each key is a " +"handler id and each value is a dict describing how to configure the " +"corresponding Handler instance." +msgstr "" + +#: ../Doc/library/logging.config.rst:241 ../Doc/library/logging.config.rst:283 +msgid "The configuring dict is searched for the following keys:" +msgstr "" + +#: ../Doc/library/logging.config.rst:243 +msgid "" +"``class`` (mandatory). This is the fully qualified name of the handler " +"class." +msgstr "" + +#: ../Doc/library/logging.config.rst:246 +msgid "``level`` (optional). The level of the handler." +msgstr "" + +#: ../Doc/library/logging.config.rst:248 +msgid "``formatter`` (optional). The id of the formatter for this handler." +msgstr "" + +#: ../Doc/library/logging.config.rst:251 +msgid "``filters`` (optional). A list of ids of the filters for this handler." +msgstr "" + +#: ../Doc/library/logging.config.rst:254 +msgid "" +"All *other* keys are passed through as keyword arguments to the handler's " +"constructor. For example, given the snippet:" +msgstr "" + +#: ../Doc/library/logging.config.rst:273 +msgid "" +"the handler with id ``console`` is instantiated as a :class:`logging." +"StreamHandler`, using ``sys.stdout`` as the underlying stream. The handler " +"with id ``file`` is instantiated as a :class:`logging.handlers." +"RotatingFileHandler` with the keyword arguments ``filename='logconfig.log', " +"maxBytes=1024, backupCount=3``." +msgstr "" + +#: ../Doc/library/logging.config.rst:279 +msgid "" +"*loggers* - the corresponding value will be a dict in which each key is a " +"logger name and each value is a dict describing how to configure the " +"corresponding Logger instance." +msgstr "" + +#: ../Doc/library/logging.config.rst:285 +msgid "``level`` (optional). The level of the logger." +msgstr "" + +#: ../Doc/library/logging.config.rst:287 +msgid "``propagate`` (optional). The propagation setting of the logger." +msgstr "" + +#: ../Doc/library/logging.config.rst:289 +msgid "``filters`` (optional). A list of ids of the filters for this logger." +msgstr "" + +#: ../Doc/library/logging.config.rst:292 +msgid "" +"``handlers`` (optional). A list of ids of the handlers for this logger." +msgstr "" + +#: ../Doc/library/logging.config.rst:295 +msgid "" +"The specified loggers will be configured according to the level, " +"propagation, filters and handlers specified." +msgstr "" + +#: ../Doc/library/logging.config.rst:298 +msgid "" +"*root* - this will be the configuration for the root logger. Processing of " +"the configuration will be as for any logger, except that the ``propagate`` " +"setting will not be applicable." +msgstr "" + +#: ../Doc/library/logging.config.rst:302 +msgid "" +"*incremental* - whether the configuration is to be interpreted as " +"incremental to the existing configuration. This value defaults to " +"``False``, which means that the specified configuration replaces the " +"existing configuration with the same semantics as used by the existing :func:" +"`fileConfig` API." +msgstr "" + +#: ../Doc/library/logging.config.rst:308 +msgid "" +"If the specified value is ``True``, the configuration is processed as " +"described in the section on :ref:`logging-config-dict-incremental`." +msgstr "" + +#: ../Doc/library/logging.config.rst:311 +msgid "" +"*disable_existing_loggers* - whether any existing loggers are to be " +"disabled. This setting mirrors the parameter of the same name in :func:" +"`fileConfig`. If absent, this parameter defaults to ``True``. This value is " +"ignored if *incremental* is ``True``." +msgstr "" + +#: ../Doc/library/logging.config.rst:319 +msgid "Incremental Configuration" +msgstr "" + +#: ../Doc/library/logging.config.rst:321 +msgid "" +"It is difficult to provide complete flexibility for incremental " +"configuration. For example, because objects such as filters and formatters " +"are anonymous, once a configuration is set up, it is not possible to refer " +"to such anonymous objects when augmenting a configuration." +msgstr "" + +#: ../Doc/library/logging.config.rst:327 +msgid "" +"Furthermore, there is not a compelling case for arbitrarily altering the " +"object graph of loggers, handlers, filters, formatters at run-time, once a " +"configuration is set up; the verbosity of loggers and handlers can be " +"controlled just by setting levels (and, in the case of loggers, propagation " +"flags). Changing the object graph arbitrarily in a safe way is problematic " +"in a multi-threaded environment; while not impossible, the benefits are not " +"worth the complexity it adds to the implementation." +msgstr "" + +#: ../Doc/library/logging.config.rst:336 +msgid "" +"Thus, when the ``incremental`` key of a configuration dict is present and is " +"``True``, the system will completely ignore any ``formatters`` and " +"``filters`` entries, and process only the ``level`` settings in the " +"``handlers`` entries, and the ``level`` and ``propagate`` settings in the " +"``loggers`` and ``root`` entries." +msgstr "" + +#: ../Doc/library/logging.config.rst:342 +msgid "" +"Using a value in the configuration dict lets configurations to be sent over " +"the wire as pickled dicts to a socket listener. Thus, the logging verbosity " +"of a long-running application can be altered over time with no need to stop " +"and restart the application." +msgstr "" + +#: ../Doc/library/logging.config.rst:350 +msgid "Object connections" +msgstr "" + +#: ../Doc/library/logging.config.rst:352 +msgid "" +"The schema describes a set of logging objects - loggers, handlers, " +"formatters, filters - which are connected to each other in an object graph. " +"Thus, the schema needs to represent connections between the objects. For " +"example, say that, once configured, a particular logger has attached to it a " +"particular handler. For the purposes of this discussion, we can say that " +"the logger represents the source, and the handler the destination, of a " +"connection between the two. Of course in the configured objects this is " +"represented by the logger holding a reference to the handler. In the " +"configuration dict, this is done by giving each destination object an id " +"which identifies it unambiguously, and then using the id in the source " +"object's configuration to indicate that a connection exists between the " +"source and the destination object with that id." +msgstr "" + +#: ../Doc/library/logging.config.rst:366 +msgid "So, for example, consider the following YAML snippet:" +msgstr "" + +#: ../Doc/library/logging.config.rst:387 +msgid "" +"(Note: YAML used here because it's a little more readable than the " +"equivalent Python source form for the dictionary.)" +msgstr "" + +#: ../Doc/library/logging.config.rst:390 +msgid "" +"The ids for loggers are the logger names which would be used " +"programmatically to obtain a reference to those loggers, e.g. ``foo.bar." +"baz``. The ids for Formatters and Filters can be any string value (such as " +"``brief``, ``precise`` above) and they are transient, in that they are only " +"meaningful for processing the configuration dictionary and used to determine " +"connections between objects, and are not persisted anywhere when the " +"configuration call is complete." +msgstr "" + +#: ../Doc/library/logging.config.rst:398 +msgid "" +"The above snippet indicates that logger named ``foo.bar.baz`` should have " +"two handlers attached to it, which are described by the handler ids ``h1`` " +"and ``h2``. The formatter for ``h1`` is that described by id ``brief``, and " +"the formatter for ``h2`` is that described by id ``precise``." +msgstr "" + +#: ../Doc/library/logging.config.rst:408 +msgid "User-defined objects" +msgstr "" + +#: ../Doc/library/logging.config.rst:410 +msgid "" +"The schema supports user-defined objects for handlers, filters and " +"formatters. (Loggers do not need to have different types for different " +"instances, so there is no support in this configuration schema for user-" +"defined logger classes.)" +msgstr "" + +#: ../Doc/library/logging.config.rst:415 +msgid "" +"Objects to be configured are described by dictionaries which detail their " +"configuration. In some places, the logging system will be able to infer " +"from the context how an object is to be instantiated, but when a user-" +"defined object is to be instantiated, the system will not know how to do " +"this. In order to provide complete flexibility for user-defined object " +"instantiation, the user needs to provide a 'factory' - a callable which is " +"called with a configuration dictionary and which returns the instantiated " +"object. This is signalled by an absolute import path to the factory being " +"made available under the special key ``'()'``. Here's a concrete example:" +msgstr "" + +#: ../Doc/library/logging.config.rst:441 +msgid "" +"The above YAML snippet defines three formatters. The first, with id " +"``brief``, is a standard :class:`logging.Formatter` instance with the " +"specified format string. The second, with id ``default``, has a longer " +"format and also defines the time format explicitly, and will result in a :" +"class:`logging.Formatter` initialized with those two format strings. Shown " +"in Python source form, the ``brief`` and ``default`` formatters have " +"configuration sub-dictionaries::" +msgstr "" + +#: ../Doc/library/logging.config.rst:453 ../Doc/library/stdtypes.rst:2439 +msgid "and::" +msgstr "" + +#: ../Doc/library/logging.config.rst:460 +msgid "" +"respectively, and as these dictionaries do not contain the special key " +"``'()'``, the instantiation is inferred from the context: as a result, " +"standard :class:`logging.Formatter` instances are created. The " +"configuration sub-dictionary for the third formatter, with id ``custom``, " +"is::" +msgstr "" + +#: ../Doc/library/logging.config.rst:473 +msgid "" +"and this contains the special key ``'()'``, which means that user-defined " +"instantiation is wanted. In this case, the specified factory callable will " +"be used. If it is an actual callable it will be used directly - otherwise, " +"if you specify a string (as in the example) the actual callable will be " +"located using normal import mechanisms. The callable will be called with the " +"**remaining** items in the configuration sub-dictionary as keyword " +"arguments. In the above example, the formatter with id ``custom`` will be " +"assumed to be returned by the call::" +msgstr "" + +#: ../Doc/library/logging.config.rst:485 +msgid "" +"The key ``'()'`` has been used as the special key because it is not a valid " +"keyword parameter name, and so will not clash with the names of the keyword " +"arguments used in the call. The ``'()'`` also serves as a mnemonic that the " +"corresponding value is a callable." +msgstr "" + +#: ../Doc/library/logging.config.rst:494 +msgid "Access to external objects" +msgstr "" + +#: ../Doc/library/logging.config.rst:496 +msgid "" +"There are times where a configuration needs to refer to objects external to " +"the configuration, for example ``sys.stderr``. If the configuration dict is " +"constructed using Python code, this is straightforward, but a problem arises " +"when the configuration is provided via a text file (e.g. JSON, YAML). In a " +"text file, there is no standard way to distinguish ``sys.stderr`` from the " +"literal string ``'sys.stderr'``. To facilitate this distinction, the " +"configuration system looks for certain special prefixes in string values and " +"treat them specially. For example, if the literal string ``'ext://sys." +"stderr'`` is provided as a value in the configuration, then the ``ext://`` " +"will be stripped off and the remainder of the value processed using normal " +"import mechanisms." +msgstr "" + +#: ../Doc/library/logging.config.rst:509 +msgid "" +"The handling of such prefixes is done in a way analogous to protocol " +"handling: there is a generic mechanism to look for prefixes which match the " +"regular expression ``^(?P[a-z]+)://(?P.*)$`` whereby, if the " +"``prefix`` is recognised, the ``suffix`` is processed in a prefix-dependent " +"manner and the result of the processing replaces the string value. If the " +"prefix is not recognised, then the string value will be left as-is." +msgstr "" + +#: ../Doc/library/logging.config.rst:521 +msgid "Access to internal objects" +msgstr "" + +#: ../Doc/library/logging.config.rst:523 +msgid "" +"As well as external objects, there is sometimes also a need to refer to " +"objects in the configuration. This will be done implicitly by the " +"configuration system for things that it knows about. For example, the " +"string value ``'DEBUG'`` for a ``level`` in a logger or handler will " +"automatically be converted to the value ``logging.DEBUG``, and the " +"``handlers``, ``filters`` and ``formatter`` entries will take an object id " +"and resolve to the appropriate destination object." +msgstr "" + +#: ../Doc/library/logging.config.rst:531 +msgid "" +"However, a more generic mechanism is needed for user-defined objects which " +"are not known to the :mod:`logging` module. For example, consider :class:" +"`logging.handlers.MemoryHandler`, which takes a ``target`` argument which is " +"another handler to delegate to. Since the system already knows about this " +"class, then in the configuration, the given ``target`` just needs to be the " +"object id of the relevant target handler, and the system will resolve to the " +"handler from the id. If, however, a user defines a ``my.package.MyHandler`` " +"which has an ``alternate`` handler, the configuration system would not know " +"that the ``alternate`` referred to a handler. To cater for this, a generic " +"resolution system allows the user to specify::" +msgstr "" + +#: ../Doc/library/logging.config.rst:551 +msgid "" +"The literal string ``'cfg://handlers.file'`` will be resolved in an " +"analogous way to strings with the ``ext://`` prefix, but looking in the " +"configuration itself rather than the import namespace. The mechanism allows " +"access by dot or by index, in a similar way to that provided by ``str." +"format``. Thus, given the following snippet::" +msgstr "" + +#: ../Doc/library/logging.config.rst:567 +msgid "" +"in the configuration, the string ``'cfg://handlers'`` would resolve to the " +"dict with key ``handlers``, the string ``'cfg://handlers.email`` would " +"resolve to the dict with key ``email`` in the ``handlers`` dict, and so on. " +"The string ``'cfg://handlers.email.toaddrs[1]`` would resolve to ``'dev_team." +"domain.tld'`` and the string ``'cfg://handlers.email.toaddrs[0]'`` would " +"resolve to the value ``'support_team@domain.tld'``. The ``subject`` value " +"could be accessed using either ``'cfg://handlers.email.subject'`` or, " +"equivalently, ``'cfg://handlers.email[subject]'``. The latter form only " +"needs to be used if the key contains spaces or non-alphanumeric characters. " +"If an index value consists only of decimal digits, access will be attempted " +"using the corresponding integer value, falling back to the string value if " +"needed." +msgstr "" + +#: ../Doc/library/logging.config.rst:581 +msgid "" +"Given a string ``cfg://handlers.myhandler.mykey.123``, this will resolve to " +"``config_dict['handlers']['myhandler']['mykey']['123']``. If the string is " +"specified as ``cfg://handlers.myhandler.mykey[123]``, the system will " +"attempt to retrieve the value from ``config_dict['handlers']['myhandler']" +"['mykey'][123]``, and fall back to ``config_dict['handlers']['myhandler']" +"['mykey']['123']`` if that fails." +msgstr "" + +#: ../Doc/library/logging.config.rst:593 +msgid "Import resolution and custom importers" +msgstr "" + +#: ../Doc/library/logging.config.rst:595 +msgid "" +"Import resolution, by default, uses the builtin :func:`__import__` function " +"to do its importing. You may want to replace this with your own importing " +"mechanism: if so, you can replace the :attr:`importer` attribute of the :" +"class:`DictConfigurator` or its superclass, the :class:`BaseConfigurator` " +"class. However, you need to be careful because of the way functions are " +"accessed from classes via descriptors. If you are using a Python callable to " +"do your imports, and you want to define it at class level rather than " +"instance level, you need to wrap it with :func:`staticmethod`. For example::" +msgstr "" + +#: ../Doc/library/logging.config.rst:610 +msgid "" +"You don't need to wrap with :func:`staticmethod` if you're setting the " +"import callable on a configurator *instance*." +msgstr "" + +#: ../Doc/library/logging.config.rst:617 +msgid "Configuration file format" +msgstr "" + +#: ../Doc/library/logging.config.rst:619 +msgid "" +"The configuration file format understood by :func:`fileConfig` is based on :" +"mod:`configparser` functionality. The file must contain sections called " +"``[loggers]``, ``[handlers]`` and ``[formatters]`` which identify by name " +"the entities of each type which are defined in the file. For each such " +"entity, there is a separate section which identifies how that entity is " +"configured. Thus, for a logger named ``log01`` in the ``[loggers]`` " +"section, the relevant configuration details are held in a section " +"``[logger_log01]``. Similarly, a handler called ``hand01`` in the " +"``[handlers]`` section will have its configuration held in a section called " +"``[handler_hand01]``, while a formatter called ``form01`` in the " +"``[formatters]`` section will have its configuration specified in a section " +"called ``[formatter_form01]``. The root logger configuration must be " +"specified in a section called ``[logger_root]``." +msgstr "" + +#: ../Doc/library/logging.config.rst:634 +msgid "" +"The :func:`fileConfig` API is older than the :func:`dictConfig` API and does " +"not provide functionality to cover certain aspects of logging. For example, " +"you cannot configure :class:`~logging.Filter` objects, which provide for " +"filtering of messages beyond simple integer levels, using :func:" +"`fileConfig`. If you need to have instances of :class:`~logging.Filter` in " +"your logging configuration, you will need to use :func:`dictConfig`. Note " +"that future enhancements to configuration functionality will be added to :" +"func:`dictConfig`, so it's worth considering transitioning to this newer API " +"when it's convenient to do so." +msgstr "" + +#: ../Doc/library/logging.config.rst:644 +msgid "Examples of these sections in the file are given below." +msgstr "" + +#: ../Doc/library/logging.config.rst:657 +msgid "" +"The root logger must specify a level and a list of handlers. An example of a " +"root logger section is given below." +msgstr "" + +#: ../Doc/library/logging.config.rst:666 +msgid "" +"The ``level`` entry can be one of ``DEBUG, INFO, WARNING, ERROR, CRITICAL`` " +"or ``NOTSET``. For the root logger only, ``NOTSET`` means that all messages " +"will be logged. Level values are :func:`eval`\\ uated in the context of the " +"``logging`` package's namespace." +msgstr "" + +#: ../Doc/library/logging.config.rst:671 +msgid "" +"The ``handlers`` entry is a comma-separated list of handler names, which " +"must appear in the ``[handlers]`` section. These names must appear in the " +"``[handlers]`` section and have corresponding sections in the configuration " +"file." +msgstr "" + +#: ../Doc/library/logging.config.rst:676 +msgid "" +"For loggers other than the root logger, some additional information is " +"required. This is illustrated by the following example." +msgstr "" + +#: ../Doc/library/logging.config.rst:687 +msgid "" +"The ``level`` and ``handlers`` entries are interpreted as for the root " +"logger, except that if a non-root logger's level is specified as ``NOTSET``, " +"the system consults loggers higher up the hierarchy to determine the " +"effective level of the logger. The ``propagate`` entry is set to 1 to " +"indicate that messages must propagate to handlers higher up the logger " +"hierarchy from this logger, or 0 to indicate that messages are **not** " +"propagated to handlers up the hierarchy. The ``qualname`` entry is the " +"hierarchical channel name of the logger, that is to say the name used by the " +"application to get the logger." +msgstr "" + +#: ../Doc/library/logging.config.rst:696 +msgid "" +"Sections which specify handler configuration are exemplified by the " +"following." +msgstr "" + +#: ../Doc/library/logging.config.rst:706 +msgid "" +"The ``class`` entry indicates the handler's class (as determined by :func:" +"`eval` in the ``logging`` package's namespace). The ``level`` is interpreted " +"as for loggers, and ``NOTSET`` is taken to mean 'log everything'." +msgstr "" + +#: ../Doc/library/logging.config.rst:710 +msgid "" +"The ``formatter`` entry indicates the key name of the formatter for this " +"handler. If blank, a default formatter (``logging._defaultFormatter``) is " +"used. If a name is specified, it must appear in the ``[formatters]`` section " +"and have a corresponding section in the configuration file." +msgstr "" + +#: ../Doc/library/logging.config.rst:715 +msgid "" +"The ``args`` entry, when :func:`eval`\\ uated in the context of the " +"``logging`` package's namespace, is the list of arguments to the constructor " +"for the handler class. Refer to the constructors for the relevant handlers, " +"or to the examples below, to see how typical entries are constructed." +msgstr "" + +#: ../Doc/library/logging.config.rst:771 +msgid "" +"Sections which specify formatter configuration are typified by the following." +msgstr "" + +#: ../Doc/library/logging.config.rst:780 +msgid "" +"The ``format`` entry is the overall format string, and the ``datefmt`` entry " +"is the :func:`strftime`\\ -compatible date/time format string. If empty, " +"the package substitutes ISO8601 format date/times, which is almost " +"equivalent to specifying the date format string ``'%Y-%m-%d %H:%M:%S'``. " +"The ISO8601 format also specifies milliseconds, which are appended to the " +"result of using the above format string, with a comma separator. An example " +"time in ISO8601 format is ``2003-01-23 00:29:50,411``." +msgstr "" + +#: ../Doc/library/logging.config.rst:788 +msgid "" +"The ``class`` entry is optional. It indicates the name of the formatter's " +"class (as a dotted module and class name.) This option is useful for " +"instantiating a :class:`~logging.Formatter` subclass. Subclasses of :class:" +"`~logging.Formatter` can present exception tracebacks in an expanded or " +"condensed format." +msgstr "" + +#: ../Doc/library/logging.config.rst:796 +msgid "" +"Due to the use of :func:`eval` as described above, there are potential " +"security risks which result from using the :func:`listen` to send and " +"receive configurations via sockets. The risks are limited to where multiple " +"users with no mutual trust run code on the same machine; see the :func:" +"`listen` documentation for more information." +msgstr "" + +#: ../Doc/library/logging.config.rst:805 +#: ../Doc/library/logging.handlers.rst:1067 +msgid "Module :mod:`logging`" +msgstr "" + +#: ../Doc/library/logging.config.rst:805 +#: ../Doc/library/logging.handlers.rst:1067 +msgid "API reference for the logging module." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:2 +msgid ":mod:`logging.handlers` --- Logging handlers" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:10 +msgid "**Source code:** :source:`Lib/logging/handlers.py`" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:25 +msgid "" +"The following useful handlers are provided in the package. Note that three " +"of the handlers (:class:`StreamHandler`, :class:`FileHandler` and :class:" +"`NullHandler`) are actually defined in the :mod:`logging` module itself, but " +"have been documented here along with the other handlers." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:33 +msgid "StreamHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:35 +msgid "" +"The :class:`StreamHandler` class, located in the core :mod:`logging` " +"package, sends logging output to streams such as *sys.stdout*, *sys.stderr* " +"or any file-like object (or, more precisely, any object which supports :meth:" +"`write` and :meth:`flush` methods)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:43 +msgid "" +"Returns a new instance of the :class:`StreamHandler` class. If *stream* is " +"specified, the instance will use it for logging output; otherwise, *sys." +"stderr* will be used." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:50 +msgid "" +"If a formatter is specified, it is used to format the record. The record is " +"then written to the stream with a terminator. If exception information is " +"present, it is formatted using :func:`traceback.print_exception` and " +"appended to the stream." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:58 +msgid "" +"Flushes the stream by calling its :meth:`flush` method. Note that the :meth:" +"`close` method is inherited from :class:`~logging.Handler` and so does no " +"output, so an explicit :meth:`flush` call may be needed at times." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:62 +msgid "" +"The ``StreamHandler`` class now has a ``terminator`` attribute, default " +"value ``'\\n'``, which is used as the terminator when writing a formatted " +"record to a stream. If you don't want this newline termination, you can set " +"the handler instance's ``terminator`` attribute to the empty string. In " +"earlier versions, the terminator was hardcoded as ``'\\n'``." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:72 +msgid "FileHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:74 +msgid "" +"The :class:`FileHandler` class, located in the core :mod:`logging` package, " +"sends logging output to a disk file. It inherits the output functionality " +"from :class:`StreamHandler`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:81 +msgid "" +"Returns a new instance of the :class:`FileHandler` class. The specified file " +"is opened and used as the stream for logging. If *mode* is not specified, :" +"const:`'a'` is used. If *encoding* is not *None*, it is used to open the " +"file with that encoding. If *delay* is true, then file opening is deferred " +"until the first call to :meth:`emit`. By default, the file grows " +"indefinitely." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:87 +#: ../Doc/library/logging.handlers.rst:166 +#: ../Doc/library/logging.handlers.rst:296 +#: ../Doc/library/logging.handlers.rst:396 +msgid "" +"As well as string values, :class:`~pathlib.Path` objects are also accepted " +"for the *filename* argument." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:93 +msgid "Closes the file." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:98 +msgid "Outputs the record to the file." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:104 +msgid "NullHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:108 +msgid "" +"The :class:`NullHandler` class, located in the core :mod:`logging` package, " +"does not do any formatting or output. It is essentially a 'no-op' handler " +"for use by library developers." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:114 +msgid "Returns a new instance of the :class:`NullHandler` class." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:118 +#: ../Doc/library/logging.handlers.rst:122 +msgid "This method does nothing." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:126 +msgid "" +"This method returns ``None`` for the lock, since there is no underlying I/O " +"to which access needs to be serialized." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:130 +msgid "" +"See :ref:`library-config` for more information on how to use :class:" +"`NullHandler`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:136 +msgid "WatchedFileHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:140 +msgid "" +"The :class:`WatchedFileHandler` class, located in the :mod:`logging." +"handlers` module, is a :class:`FileHandler` which watches the file it is " +"logging to. If the file changes, it is closed and reopened using the file " +"name." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:144 +msgid "" +"A file change can happen because of usage of programs such as *newsyslog* " +"and *logrotate* which perform log file rotation. This handler, intended for " +"use under Unix/Linux, watches the file to see if it has changed since the " +"last emit. (A file is deemed to have changed if its device or inode have " +"changed.) If the file has changed, the old file stream is closed, and the " +"file opened to get a new stream." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:151 +msgid "" +"This handler is not appropriate for use under Windows, because under Windows " +"open log files cannot be moved or renamed - logging opens the files with " +"exclusive locks - and so there is no need for such a handler. Furthermore, " +"*ST_INO* is not supported under Windows; :func:`~os.stat` always returns " +"zero for this value." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:160 +msgid "" +"Returns a new instance of the :class:`WatchedFileHandler` class. The " +"specified file is opened and used as the stream for logging. If *mode* is " +"not specified, :const:`'a'` is used. If *encoding* is not *None*, it is " +"used to open the file with that encoding. If *delay* is true, then file " +"opening is deferred until the first call to :meth:`emit`. By default, the " +"file grows indefinitely." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:172 +msgid "" +"Checks to see if the file has changed. If it has, the existing stream is " +"flushed and closed and the file opened again, typically as a precursor to " +"outputting the record to the file." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:181 +msgid "" +"Outputs the record to the file, but first calls :meth:`reopenIfNeeded` to " +"reopen the file if it has changed." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:187 +msgid "BaseRotatingHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:189 +msgid "" +"The :class:`BaseRotatingHandler` class, located in the :mod:`logging." +"handlers` module, is the base class for the rotating file handlers, :class:" +"`RotatingFileHandler` and :class:`TimedRotatingFileHandler`. You should not " +"need to instantiate this class, but it has attributes and methods you may " +"need to override." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:197 +msgid "The parameters are as for :class:`FileHandler`. The attributes are:" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:201 +msgid "" +"If this attribute is set to a callable, the :meth:`rotation_filename` method " +"delegates to this callable. The parameters passed to the callable are those " +"passed to :meth:`rotation_filename`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:205 +msgid "" +"The namer function is called quite a few times during rollover, so it should " +"be as simple and as fast as possible. It should also return the same output " +"every time for a given input, otherwise the rollover behaviour may not work " +"as expected." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:215 +msgid "" +"If this attribute is set to a callable, the :meth:`rotate` method delegates " +"to this callable. The parameters passed to the callable are those passed " +"to :meth:`rotate`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:223 +msgid "Modify the filename of a log file when rotating." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:225 +msgid "This is provided so that a custom filename can be provided." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:227 +msgid "" +"The default implementation calls the 'namer' attribute of the handler, if " +"it's callable, passing the default name to it. If the attribute isn't " +"callable (the default is ``None``), the name is returned unchanged." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:231 +msgid "The default name for the log file." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:238 +msgid "When rotating, rotate the current log." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:240 +msgid "" +"The default implementation calls the 'rotator' attribute of the handler, if " +"it's callable, passing the source and dest arguments to it. If the attribute " +"isn't callable (the default is ``None``), the source is simply renamed to " +"the destination." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:245 +msgid "" +"The source filename. This is normally the base filename, e.g. 'test.log'." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:247 +msgid "" +"The destination filename. This is normally what the source is rotated to, e." +"g. 'test.log.1'." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:252 +msgid "" +"The reason the attributes exist is to save you having to subclass - you can " +"use the same callables for instances of :class:`RotatingFileHandler` and :" +"class:`TimedRotatingFileHandler`. If either the namer or rotator callable " +"raises an exception, this will be handled in the same way as any other " +"exception during an :meth:`emit` call, i.e. via the :meth:`handleError` " +"method of the handler." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:259 +msgid "" +"If you need to make more significant changes to rotation processing, you can " +"override the methods." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:262 +msgid "For an example, see :ref:`cookbook-rotator-namer`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:268 +msgid "RotatingFileHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:270 +msgid "" +"The :class:`RotatingFileHandler` class, located in the :mod:`logging." +"handlers` module, supports rotation of disk log files." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:276 +msgid "" +"Returns a new instance of the :class:`RotatingFileHandler` class. The " +"specified file is opened and used as the stream for logging. If *mode* is " +"not specified, ``'a'`` is used. If *encoding* is not *None*, it is used to " +"open the file with that encoding. If *delay* is true, then file opening is " +"deferred until the first call to :meth:`emit`. By default, the file grows " +"indefinitely." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:282 +msgid "" +"You can use the *maxBytes* and *backupCount* values to allow the file to :" +"dfn:`rollover` at a predetermined size. When the size is about to be " +"exceeded, the file is closed and a new file is silently opened for output. " +"Rollover occurs whenever the current log file is nearly *maxBytes* in " +"length; if either of *maxBytes* or *backupCount* is zero, rollover never " +"occurs. If *backupCount* is non-zero, the system will save old log files by " +"appending the extensions '.1', '.2' etc., to the filename. For example, with " +"a *backupCount* of 5 and a base file name of :file:`app.log`, you would get :" +"file:`app.log`, :file:`app.log.1`, :file:`app.log.2`, up to :file:`app." +"log.5`. The file being written to is always :file:`app.log`. When this file " +"is filled, it is closed and renamed to :file:`app.log.1`, and if files :file:" +"`app.log.1`, :file:`app.log.2`, etc. exist, then they are renamed to :file:" +"`app.log.2`, :file:`app.log.3` etc. respectively." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:302 +#: ../Doc/library/logging.handlers.rst:402 +msgid "Does a rollover, as described above." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:307 +msgid "" +"Outputs the record to the file, catering for rollover as described " +"previously." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:313 +msgid "TimedRotatingFileHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:315 +msgid "" +"The :class:`TimedRotatingFileHandler` class, located in the :mod:`logging." +"handlers` module, supports rotation of disk log files at certain timed " +"intervals." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:322 +msgid "" +"Returns a new instance of the :class:`TimedRotatingFileHandler` class. The " +"specified file is opened and used as the stream for logging. On rotating it " +"also sets the filename suffix. Rotating happens based on the product of " +"*when* and *interval*." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:327 +msgid "" +"You can use the *when* to specify the type of *interval*. The list of " +"possible values is below. Note that they are not case sensitive." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:331 +msgid "Type of interval" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:331 +msgid "If/how *atTime* is used" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:333 +msgid "``'S'``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:333 +msgid "Seconds" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:333 +#: ../Doc/library/logging.handlers.rst:335 +#: ../Doc/library/logging.handlers.rst:337 +#: ../Doc/library/logging.handlers.rst:339 +msgid "Ignored" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:335 +msgid "``'M'``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:335 +msgid "Minutes" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:337 +msgid "Hours" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:339 +msgid "``'D'``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:339 +msgid "Days" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:341 +msgid "``'W0'-'W6'``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:341 +msgid "Weekday (0=Monday)" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:341 +#: ../Doc/library/logging.handlers.rst:344 +msgid "Used to compute initial rollover time" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:344 +msgid "``'midnight'``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:344 +msgid "Roll over at midnight, if *atTime* not specified, else at time *atTime*" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:349 +msgid "" +"When using weekday-based rotation, specify 'W0' for Monday, 'W1' for " +"Tuesday, and so on up to 'W6' for Sunday. In this case, the value passed for " +"*interval* isn't used." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:353 +msgid "" +"The system will save old log files by appending extensions to the filename. " +"The extensions are date-and-time based, using the strftime format ``%Y-%m-%d_" +"%H-%M-%S`` or a leading portion thereof, depending on the rollover interval." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:358 +msgid "" +"When computing the next rollover time for the first time (when the handler " +"is created), the last modification time of an existing log file, or else the " +"current time, is used to compute when the next rotation will occur." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:362 +msgid "" +"If the *utc* argument is true, times in UTC will be used; otherwise local " +"time is used." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:365 +msgid "" +"If *backupCount* is nonzero, at most *backupCount* files will be kept, and " +"if more would be created when rollover occurs, the oldest one is deleted. " +"The deletion logic uses the interval to determine which files to delete, so " +"changing the interval may leave old files lying around." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:370 +msgid "" +"If *delay* is true, then file opening is deferred until the first call to :" +"meth:`emit`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:373 +msgid "" +"If *atTime* is not ``None``, it must be a ``datetime.time`` instance which " +"specifies the time of day when rollover occurs, for the cases where rollover " +"is set to happen \"at midnight\" or \"on a particular weekday\". Note that " +"in these cases, the *atTime* value is effectively used to compute the " +"*initial* rollover, and subsequent rollovers would be calculated via the " +"normal interval calculation." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:380 +msgid "" +"Calculation of the initial rollover time is done when the handler is " +"initialised. Calculation of subsequent rollover times is done only when " +"rollover occurs, and rollover occurs only when emitting output. If this is " +"not kept in mind, it might lead to some confusion. For example, if an " +"interval of \"every minute\" is set, that does not mean you will always see " +"log files with times (in the filename) separated by a minute; if, during " +"application execution, logging output is generated more frequently than once " +"a minute, *then* you can expect to see log files with times separated by a " +"minute. If, on the other hand, logging messages are only output once every " +"five minutes (say), then there will be gaps in the file times corresponding " +"to the minutes where no output (and hence no rollover) occurred." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:393 +msgid "*atTime* parameter was added." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:406 +msgid "" +"Outputs the record to the file, catering for rollover as described above." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:412 +msgid "SocketHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:414 +msgid "" +"The :class:`SocketHandler` class, located in the :mod:`logging.handlers` " +"module, sends logging output to a network socket. The base class uses a TCP " +"socket." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:420 +msgid "" +"Returns a new instance of the :class:`SocketHandler` class intended to " +"communicate with a remote machine whose address is given by *host* and " +"*port*." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:423 +#: ../Doc/library/logging.handlers.rst:511 +msgid "" +"If ``port`` is specified as ``None``, a Unix domain socket is created using " +"the value in ``host`` - otherwise, a TCP socket is created." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:429 +msgid "Closes the socket." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:434 +msgid "" +"Pickles the record's attribute dictionary and writes it to the socket in " +"binary format. If there is an error with the socket, silently drops the " +"packet. If the connection was previously lost, re-establishes the " +"connection. To unpickle the record at the receiving end into a :class:" +"`~logging.LogRecord`, use the :func:`~logging.makeLogRecord` function." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:444 +msgid "" +"Handles an error which has occurred during :meth:`emit`. The most likely " +"cause is a lost connection. Closes the socket so that we can retry on the " +"next event." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:451 +msgid "" +"This is a factory method which allows subclasses to define the precise type " +"of socket they want. The default implementation creates a TCP socket (:const:" +"`socket.SOCK_STREAM`)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:458 +msgid "" +"Pickles the record's attribute dictionary in binary format with a length " +"prefix, and returns it ready for transmission across the socket." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:461 +msgid "" +"Note that pickles aren't completely secure. If you are concerned about " +"security, you may want to override this method to implement a more secure " +"mechanism. For example, you can sign pickles using HMAC and then verify them " +"on the receiving end, or alternatively you can disable unpickling of global " +"objects on the receiving end." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:470 +msgid "" +"Send a pickled string *packet* to the socket. This function allows for " +"partial sends which can happen when the network is busy." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:476 +msgid "" +"Tries to create a socket; on failure, uses an exponential back-off " +"algorithm. On initial failure, the handler will drop the message it was " +"trying to send. When subsequent messages are handled by the same instance, " +"it will not try connecting until some time has passed. The default " +"parameters are such that the initial delay is one second, and if after that " +"delay the connection still can't be made, the handler will double the delay " +"each time up to a maximum of 30 seconds." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:484 +msgid "This behaviour is controlled by the following handler attributes:" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:486 +msgid "``retryStart`` (initial delay, defaulting to 1.0 seconds)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:487 +msgid "``retryFactor`` (multiplier, defaulting to 2.0)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:488 +msgid "``retryMax`` (maximum delay, defaulting to 30.0 seconds)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:490 +msgid "" +"This means that if the remote listener starts up *after* the handler has " +"been used, you could lose messages (since the handler won't even attempt a " +"connection until the delay has elapsed, but just silently drop messages " +"during the delay period)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:499 +msgid "DatagramHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:501 +msgid "" +"The :class:`DatagramHandler` class, located in the :mod:`logging.handlers` " +"module, inherits from :class:`SocketHandler` to support sending logging " +"messages over UDP sockets." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:508 +msgid "" +"Returns a new instance of the :class:`DatagramHandler` class intended to " +"communicate with a remote machine whose address is given by *host* and " +"*port*." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:517 +msgid "" +"Pickles the record's attribute dictionary and writes it to the socket in " +"binary format. If there is an error with the socket, silently drops the " +"packet. To unpickle the record at the receiving end into a :class:`~logging." +"LogRecord`, use the :func:`~logging.makeLogRecord` function." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:526 +msgid "" +"The factory method of :class:`SocketHandler` is here overridden to create a " +"UDP socket (:const:`socket.SOCK_DGRAM`)." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:532 +msgid "Send a pickled string to a socket." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:538 +msgid "SysLogHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:540 +msgid "" +"The :class:`SysLogHandler` class, located in the :mod:`logging.handlers` " +"module, supports sending logging messages to a remote or local Unix syslog." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:546 +msgid "" +"Returns a new instance of the :class:`SysLogHandler` class intended to " +"communicate with a remote Unix machine whose address is given by *address* " +"in the form of a ``(host, port)`` tuple. If *address* is not specified, " +"``('localhost', 514)`` is used. The address is used to open a socket. An " +"alternative to providing a ``(host, port)`` tuple is providing an address as " +"a string, for example '/dev/log'. In this case, a Unix domain socket is used " +"to send the message to the syslog. If *facility* is not specified, :const:" +"`LOG_USER` is used. The type of socket opened depends on the *socktype* " +"argument, which defaults to :const:`socket.SOCK_DGRAM` and thus opens a UDP " +"socket. To open a TCP socket (for use with the newer syslog daemons such as " +"rsyslog), specify a value of :const:`socket.SOCK_STREAM`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:558 +msgid "" +"Note that if your server is not listening on UDP port 514, :class:" +"`SysLogHandler` may appear not to work. In that case, check what address you " +"should be using for a domain socket - it's system dependent. For example, on " +"Linux it's usually '/dev/log' but on OS/X it's '/var/run/syslog'. You'll " +"need to check your platform and use the appropriate address (you may need to " +"do this check at runtime if your application needs to run on several " +"platforms). On Windows, you pretty much have to use the UDP option." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:567 +msgid "*socktype* was added." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:573 +msgid "Closes the socket to the remote host." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:578 +msgid "" +"The record is formatted, and then sent to the syslog server. If exception " +"information is present, it is *not* sent to the server." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:581 +msgid "" +"(See: :issue:`12168`.) In earlier versions, the message sent to the syslog " +"daemons was always terminated with a NUL byte, because early versions of " +"these daemons expected a NUL terminated message - even though it's not in " +"the relevant specification (RFC 5424). More recent versions of these daemons " +"don't expect the NUL byte but strip it off if it's there, and even more " +"recent daemons (which adhere more closely to RFC 5424) pass the NUL byte on " +"as part of the message." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:590 +msgid "" +"To enable easier handling of syslog messages in the face of all these " +"differing daemon behaviours, the appending of the NUL byte has been made " +"configurable, through the use of a class-level attribute, ``append_nul``. " +"This defaults to ``True`` (preserving the existing behaviour) but can be set " +"to ``False`` on a ``SysLogHandler`` instance in order for that instance to " +"*not* append the NUL terminator." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:597 +msgid "" +"(See: :issue:`12419`.) In earlier versions, there was no facility for an " +"\"ident\" or \"tag\" prefix to identify the source of the message. This can " +"now be specified using a class-level attribute, defaulting to ``\"\"`` to " +"preserve existing behaviour, but which can be overridden on a " +"``SysLogHandler`` instance in order for that instance to prepend the ident " +"to every message handled. Note that the provided ident must be text, not " +"bytes, and is prepended to the message exactly as is." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:608 +msgid "" +"Encodes the facility and priority into an integer. You can pass in strings " +"or integers - if strings are passed, internal mapping dictionaries are used " +"to convert them to integers." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:612 +msgid "" +"The symbolic ``LOG_`` values are defined in :class:`SysLogHandler` and " +"mirror the values defined in the ``sys/syslog.h`` header file." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:615 +msgid "**Priorities**" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:618 +#: ../Doc/library/logging.handlers.rst:640 +msgid "Name (string)" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:618 +#: ../Doc/library/logging.handlers.rst:640 +msgid "Symbolic value" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:620 +msgid "``alert``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:620 +msgid "LOG_ALERT" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:622 +msgid "``crit`` or ``critical``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:622 +msgid "LOG_CRIT" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:624 +msgid "``debug``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:624 +msgid "LOG_DEBUG" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:626 +msgid "``emerg`` or ``panic``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:626 +msgid "LOG_EMERG" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:628 +msgid "``err`` or ``error``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:628 +msgid "LOG_ERR" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:630 +msgid "``info``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:630 +msgid "LOG_INFO" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:632 +msgid "``notice``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:632 +msgid "LOG_NOTICE" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:634 +msgid "``warn`` or ``warning``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:634 +msgid "LOG_WARNING" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:637 +msgid "**Facilities**" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:642 +msgid "``auth``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:642 +msgid "LOG_AUTH" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:644 +msgid "``authpriv``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:644 +msgid "LOG_AUTHPRIV" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:646 +msgid "``cron``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:646 +msgid "LOG_CRON" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:648 +msgid "``daemon``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:648 +msgid "LOG_DAEMON" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:650 +msgid "``ftp``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:650 +msgid "LOG_FTP" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:652 +msgid "``kern``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:652 +msgid "LOG_KERN" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:654 +msgid "``lpr``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:654 +msgid "LOG_LPR" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:656 +msgid "``mail``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:656 +msgid "LOG_MAIL" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:658 +msgid "``news``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:658 +msgid "LOG_NEWS" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:660 +msgid "``syslog``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:660 +msgid "LOG_SYSLOG" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:662 +msgid "``user``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:662 +msgid "LOG_USER" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:664 +msgid "``uucp``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:664 +msgid "LOG_UUCP" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:666 +msgid "``local0``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:666 +msgid "LOG_LOCAL0" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:668 +msgid "``local1``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:668 +msgid "LOG_LOCAL1" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:670 +msgid "``local2``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:670 +msgid "LOG_LOCAL2" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:672 +msgid "``local3``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:672 +msgid "LOG_LOCAL3" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:674 +msgid "``local4``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:674 +msgid "LOG_LOCAL4" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:676 +msgid "``local5``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:676 +msgid "LOG_LOCAL5" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:678 +msgid "``local6``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:678 +msgid "LOG_LOCAL6" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:680 +msgid "``local7``" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:680 +msgid "LOG_LOCAL7" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:685 +msgid "" +"Maps a logging level name to a syslog priority name. You may need to " +"override this if you are using custom levels, or if the default algorithm is " +"not suitable for your needs. The default algorithm maps ``DEBUG``, ``INFO``, " +"``WARNING``, ``ERROR`` and ``CRITICAL`` to the equivalent syslog names, and " +"all other level names to 'warning'." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:695 +msgid "NTEventLogHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:697 +msgid "" +"The :class:`NTEventLogHandler` class, located in the :mod:`logging.handlers` " +"module, supports sending logging messages to a local Windows NT, Windows " +"2000 or Windows XP event log. Before you can use it, you need Mark Hammond's " +"Win32 extensions for Python installed." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:705 +msgid "" +"Returns a new instance of the :class:`NTEventLogHandler` class. The " +"*appname* is used to define the application name as it appears in the event " +"log. An appropriate registry entry is created using this name. The *dllname* " +"should give the fully qualified pathname of a .dll or .exe which contains " +"message definitions to hold in the log (if not specified, ``'win32service." +"pyd'`` is used - this is installed with the Win32 extensions and contains " +"some basic placeholder message definitions. Note that use of these " +"placeholders will make your event logs big, as the entire message source is " +"held in the log. If you want slimmer logs, you have to pass in the name of " +"your own .dll or .exe which contains the message definitions you want to use " +"in the event log). The *logtype* is one of ``'Application'``, ``'System'`` " +"or ``'Security'``, and defaults to ``'Application'``." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:721 +msgid "" +"At this point, you can remove the application name from the registry as a " +"source of event log entries. However, if you do this, you will not be able " +"to see the events as you intended in the Event Log Viewer - it needs to be " +"able to access the registry to get the .dll name. The current version does " +"not do this." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:730 +msgid "" +"Determines the message ID, event category and event type, and then logs the " +"message in the NT event log." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:736 +msgid "" +"Returns the event category for the record. Override this if you want to " +"specify your own categories. This version returns 0." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:742 +msgid "" +"Returns the event type for the record. Override this if you want to specify " +"your own types. This version does a mapping using the handler's typemap " +"attribute, which is set up in :meth:`__init__` to a dictionary which " +"contains mappings for :const:`DEBUG`, :const:`INFO`, :const:`WARNING`, :" +"const:`ERROR` and :const:`CRITICAL`. If you are using your own levels, you " +"will either need to override this method or place a suitable dictionary in " +"the handler's *typemap* attribute." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:753 +msgid "" +"Returns the message ID for the record. If you are using your own messages, " +"you could do this by having the *msg* passed to the logger being an ID " +"rather than a format string. Then, in here, you could use a dictionary " +"lookup to get the message ID. This version returns 1, which is the base " +"message ID in :file:`win32service.pyd`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:762 +msgid "SMTPHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:764 +msgid "" +"The :class:`SMTPHandler` class, located in the :mod:`logging.handlers` " +"module, supports sending logging messages to an email address via SMTP." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:770 +msgid "" +"Returns a new instance of the :class:`SMTPHandler` class. The instance is " +"initialized with the from and to addresses and subject line of the email. " +"The *toaddrs* should be a list of strings. To specify a non-standard SMTP " +"port, use the (host, port) tuple format for the *mailhost* argument. If you " +"use a string, the standard SMTP port is used. If your SMTP server requires " +"authentication, you can specify a (username, password) tuple for the " +"*credentials* argument." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:777 +msgid "" +"To specify the use of a secure protocol (TLS), pass in a tuple to the " +"*secure* argument. This will only be used when authentication credentials " +"are supplied. The tuple should be either an empty tuple, or a single-value " +"tuple with the name of a keyfile, or a 2-value tuple with the names of the " +"keyfile and certificate file. (This tuple is passed to the :meth:`smtplib." +"SMTP.starttls` method.)" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:784 +msgid "" +"A timeout can be specified for communication with the SMTP server using the " +"*timeout* argument." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:787 +msgid "The *timeout* argument was added." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:792 +msgid "Formats the record and sends it to the specified addressees." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:797 +msgid "" +"If you want to specify a subject line which is record-dependent, override " +"this method." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:803 +msgid "MemoryHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:805 +msgid "" +"The :class:`MemoryHandler` class, located in the :mod:`logging.handlers` " +"module, supports buffering of logging records in memory, periodically " +"flushing them to a :dfn:`target` handler. Flushing occurs whenever the " +"buffer is full, or when an event of a certain severity or greater is seen." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:810 +msgid "" +":class:`MemoryHandler` is a subclass of the more general :class:" +"`BufferingHandler`, which is an abstract class. This buffers logging records " +"in memory. Whenever each record is added to the buffer, a check is made by " +"calling :meth:`shouldFlush` to see if the buffer should be flushed. If it " +"should, then :meth:`flush` is expected to do the flushing." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:819 +msgid "Initializes the handler with a buffer of the specified capacity." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:824 +msgid "" +"Appends the record to the buffer. If :meth:`shouldFlush` returns true, " +"calls :meth:`flush` to process the buffer." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:830 +msgid "" +"You can override this to implement custom flushing behavior. This version " +"just zaps the buffer to empty." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:836 +msgid "" +"Returns true if the buffer is up to capacity. This method can be overridden " +"to implement custom flushing strategies." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:842 +msgid "" +"Returns a new instance of the :class:`MemoryHandler` class. The instance is " +"initialized with a buffer size of *capacity*. If *flushLevel* is not " +"specified, :const:`ERROR` is used. If no *target* is specified, the target " +"will need to be set using :meth:`setTarget` before this handler does " +"anything useful. If *flushOnClose* is specified as ``False``, then the " +"buffer is *not* flushed when the handler is closed. If not specified or " +"specified as ``True``, the previous behaviour of flushing the buffer will " +"occur when the handler is closed." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:850 +msgid "The *flushOnClose* parameter was added." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:856 +msgid "Calls :meth:`flush`, sets the target to ``None`` and clears the buffer." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:862 +msgid "" +"For a :class:`MemoryHandler`, flushing means just sending the buffered " +"records to the target, if there is one. The buffer is also cleared when this " +"happens. Override if you want different behavior." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:869 +msgid "Sets the target handler for this handler." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:874 +msgid "Checks for buffer full or a record at the *flushLevel* or higher." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:880 +msgid "HTTPHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:882 +msgid "" +"The :class:`HTTPHandler` class, located in the :mod:`logging.handlers` " +"module, supports sending logging messages to a Web server, using either " +"``GET`` or ``POST`` semantics." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:889 +msgid "" +"Returns a new instance of the :class:`HTTPHandler` class. The *host* can be " +"of the form ``host:port``, should you need to use a specific port number. " +"If no *method* is specified, ``GET`` is used. If *secure* is true, a HTTPS " +"connection will be used. The *context* parameter may be set to a :class:`ssl." +"SSLContext` instance to configure the SSL settings used for the HTTPS " +"connection. If *credentials* is specified, it should be a 2-tuple consisting " +"of userid and password, which will be placed in a HTTP 'Authorization' " +"header using Basic authentication. If you specify credentials, you should " +"also specify secure=True so that your userid and password are not passed in " +"cleartext across the wire." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:900 +msgid "The *context* parameter was added." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:905 +msgid "" +"Provides a dictionary, based on ``record``, which is to be URL-encoded and " +"sent to the web server. The default implementation just returns ``record." +"__dict__``. This method can be overridden if e.g. only a subset of :class:" +"`~logging.LogRecord` is to be sent to the web server, or if more specific " +"customization of what's sent to the server is required." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:913 +msgid "" +"Sends the record to the Web server as a URL-encoded dictionary. The :meth:" +"`mapLogRecord` method is used to convert the record to the dictionary to be " +"sent." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:917 +msgid "" +"Since preparing a record for sending it to a Web server is not the same as a " +"generic formatting operation, using :meth:`~logging.Handler.setFormatter` to " +"specify a :class:`~logging.Formatter` for a :class:`HTTPHandler` has no " +"effect. Instead of calling :meth:`~logging.Handler.format`, this handler " +"calls :meth:`mapLogRecord` and then :func:`urllib.parse.urlencode` to encode " +"the dictionary in a form suitable for sending to a Web server." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:930 +msgid "QueueHandler" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:934 +msgid "" +"The :class:`QueueHandler` class, located in the :mod:`logging.handlers` " +"module, supports sending logging messages to a queue, such as those " +"implemented in the :mod:`queue` or :mod:`multiprocessing` modules." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:938 +msgid "" +"Along with the :class:`QueueListener` class, :class:`QueueHandler` can be " +"used to let handlers do their work on a separate thread from the one which " +"does the logging. This is important in Web applications and also other " +"service applications where threads servicing clients need to respond as " +"quickly as possible, while any potentially slow operations (such as sending " +"an email via :class:`SMTPHandler`) are done on a separate thread." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:947 +msgid "" +"Returns a new instance of the :class:`QueueHandler` class. The instance is " +"initialized with the queue to send messages to. The queue can be any queue- " +"like object; it's used as-is by the :meth:`enqueue` method, which needs to " +"know how to send messages to it." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:955 +msgid "Enqueues the result of preparing the LogRecord." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:959 +msgid "" +"Prepares a record for queuing. The object returned by this method is " +"enqueued." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:962 +msgid "" +"The base implementation formats the record to merge the message and " +"arguments, and removes unpickleable items from the record in-place." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:966 +msgid "" +"You might want to override this method if you want to convert the record to " +"a dict or JSON string, or send a modified copy of the record while leaving " +"the original intact." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:972 +msgid "" +"Enqueues the record on the queue using ``put_nowait()``; you may want to " +"override this if you want to use blocking behaviour, or a timeout, or a " +"customized queue implementation." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:981 +msgid "QueueListener" +msgstr "" + +#: ../Doc/library/logging.handlers.rst:985 +msgid "" +"The :class:`QueueListener` class, located in the :mod:`logging.handlers` " +"module, supports receiving logging messages from a queue, such as those " +"implemented in the :mod:`queue` or :mod:`multiprocessing` modules. The " +"messages are received from a queue in an internal thread and passed, on the " +"same thread, to one or more handlers for processing. While :class:" +"`QueueListener` is not itself a handler, it is documented here because it " +"works hand-in-hand with :class:`QueueHandler`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:993 +msgid "" +"Along with the :class:`QueueHandler` class, :class:`QueueListener` can be " +"used to let handlers do their work on a separate thread from the one which " +"does the logging. This is important in Web applications and also other " +"service applications where threads servicing clients need to respond as " +"quickly as possible, while any potentially slow operations (such as sending " +"an email via :class:`SMTPHandler`) are done on a separate thread." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1002 +msgid "" +"Returns a new instance of the :class:`QueueListener` class. The instance is " +"initialized with the queue to send messages to and a list of handlers which " +"will handle entries placed on the queue. The queue can be any queue- like " +"object; it's passed as-is to the :meth:`dequeue` method, which needs to know " +"how to get messages from it. If ``respect_handler_level`` is ``True``, a " +"handler's level is respected (compared with the level for the message) when " +"deciding whether to pass messages to that handler; otherwise, the behaviour " +"is as in previous Python versions - to always pass each message to each " +"handler." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1012 +msgid "The ``respect_handler_levels`` argument was added." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1017 +msgid "Dequeues a record and return it, optionally blocking." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1019 +msgid "" +"The base implementation uses ``get()``. You may want to override this method " +"if you want to use timeouts or work with custom queue implementations." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1025 +msgid "Prepare a record for handling." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1027 +msgid "" +"This implementation just returns the passed-in record. You may want to " +"override this method if you need to do any custom marshalling or " +"manipulation of the record before passing it to the handlers." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1033 +msgid "Handle a record." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1035 +msgid "" +"This just loops through the handlers offering them the record to handle. The " +"actual object passed to the handlers is that which is returned from :meth:" +"`prepare`." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1041 +msgid "Starts the listener." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1043 +msgid "" +"This starts up a background thread to monitor the queue for LogRecords to " +"process." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1048 +msgid "Stops the listener." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1050 +msgid "" +"This asks the thread to terminate, and then waits for it to do so. Note that " +"if you don't call this before your application exits, there may be some " +"records still left on the queue, which won't be processed." +msgstr "" + +#: ../Doc/library/logging.handlers.rst:1056 +msgid "" +"Writes a sentinel to the queue to tell the listener to quit. This " +"implementation uses ``put_nowait()``. You may want to override this method " +"if you want to use timeouts or work with custom queue implementations." +msgstr "" + +#: ../Doc/library/lzma.rst:2 +msgid ":mod:`lzma` --- Compression using the LZMA algorithm" +msgstr "" + +#: ../Doc/library/lzma.rst:12 +msgid "**Source code:** :source:`Lib/lzma.py`" +msgstr "" + +#: ../Doc/library/lzma.rst:16 +msgid "" +"This module provides classes and convenience functions for compressing and " +"decompressing data using the LZMA compression algorithm. Also included is a " +"file interface supporting the ``.xz`` and legacy ``.lzma`` file formats used " +"by the :program:`xz` utility, as well as raw compressed streams." +msgstr "" + +#: ../Doc/library/lzma.rst:21 +msgid "" +"The interface provided by this module is very similar to that of the :mod:" +"`bz2` module. However, note that :class:`LZMAFile` is *not* thread-safe, " +"unlike :class:`bz2.BZ2File`, so if you need to use a single :class:" +"`LZMAFile` instance from multiple threads, it is necessary to protect it " +"with a lock." +msgstr "" + +#: ../Doc/library/lzma.rst:29 +msgid "" +"This exception is raised when an error occurs during compression or " +"decompression, or while initializing the compressor/decompressor state." +msgstr "" + +#: ../Doc/library/lzma.rst:34 +msgid "Reading and writing compressed files" +msgstr "" + +#: ../Doc/library/lzma.rst:38 +msgid "" +"Open an LZMA-compressed file in binary or text mode, returning a :term:`file " +"object`." +msgstr "" + +#: ../Doc/library/lzma.rst:41 +msgid "" +"The *filename* argument can be either an actual file name (given as a :class:" +"`str`, :class:`bytes` or :term:`path-like object` object), in which case the " +"named file is opened, or it can be an existing file object to read from or " +"write to." +msgstr "" + +#: ../Doc/library/lzma.rst:46 +msgid "" +"The *mode* argument can be any of ``\"r\"``, ``\"rb\"``, ``\"w\"``, ``\"wb" +"\"``, ``\"x\"``, ``\"xb\"``, ``\"a\"`` or ``\"ab\"`` for binary mode, or ``" +"\"rt\"``, ``\"wt\"``, ``\"xt\"``, or ``\"at\"`` for text mode. The default " +"is ``\"rb\"``." +msgstr "" + +#: ../Doc/library/lzma.rst:50 ../Doc/library/lzma.rst:95 +msgid "" +"When opening a file for reading, the *format* and *filters* arguments have " +"the same meanings as for :class:`LZMADecompressor`. In this case, the " +"*check* and *preset* arguments should not be used." +msgstr "" + +#: ../Doc/library/lzma.rst:54 ../Doc/library/lzma.rst:99 +msgid "" +"When opening a file for writing, the *format*, *check*, *preset* and " +"*filters* arguments have the same meanings as for :class:`LZMACompressor`." +msgstr "" + +#: ../Doc/library/lzma.rst:57 +msgid "" +"For binary mode, this function is equivalent to the :class:`LZMAFile` " +"constructor: ``LZMAFile(filename, mode, ...)``. In this case, the " +"*encoding*, *errors* and *newline* arguments must not be provided." +msgstr "" + +#: ../Doc/library/lzma.rst:61 +msgid "" +"For text mode, a :class:`LZMAFile` object is created, and wrapped in an :" +"class:`io.TextIOWrapper` instance with the specified encoding, error " +"handling behavior, and line ending(s)." +msgstr "" + +#: ../Doc/library/lzma.rst:65 +msgid "Added support for the ``\"x\"``, ``\"xb\"`` and ``\"xt\"`` modes." +msgstr "" + +#: ../Doc/library/lzma.rst:74 +msgid "Open an LZMA-compressed file in binary mode." +msgstr "" + +#: ../Doc/library/lzma.rst:76 +msgid "" +"An :class:`LZMAFile` can wrap an already-open :term:`file object`, or " +"operate directly on a named file. The *filename* argument specifies either " +"the file object to wrap, or the name of the file to open (as a :class:" +"`str`, :class:`bytes` or :term:`path-like object` object). When wrapping an " +"existing file object, the wrapped file will not be closed when the :class:" +"`LZMAFile` is closed." +msgstr "" + +#: ../Doc/library/lzma.rst:83 +msgid "" +"The *mode* argument can be either ``\"r\"`` for reading (default), ``\"w\"`` " +"for overwriting, ``\"x\"`` for exclusive creation, or ``\"a\"`` for " +"appending. These can equivalently be given as ``\"rb\"``, ``\"wb\"``, ``\"xb" +"\"`` and ``\"ab\"`` respectively." +msgstr "" + +#: ../Doc/library/lzma.rst:88 +msgid "" +"If *filename* is a file object (rather than an actual file name), a mode of " +"``\"w\"`` does not truncate the file, and is instead equivalent to ``\"a\"``." +msgstr "" + +#: ../Doc/library/lzma.rst:91 +msgid "" +"When opening a file for reading, the input file may be the concatenation of " +"multiple separate compressed streams. These are transparently decoded as a " +"single logical stream." +msgstr "" + +#: ../Doc/library/lzma.rst:102 +msgid "" +":class:`LZMAFile` supports all the members specified by :class:`io." +"BufferedIOBase`, except for :meth:`detach` and :meth:`truncate`. Iteration " +"and the :keyword:`with` statement are supported." +msgstr "" + +#: ../Doc/library/lzma.rst:106 +msgid "The following method is also provided:" +msgstr "" + +#: ../Doc/library/lzma.rst:110 +msgid "" +"Return buffered data without advancing the file position. At least one byte " +"of data will be returned, unless EOF has been reached. The exact number of " +"bytes returned is unspecified (the *size* argument is ignored)." +msgstr "" + +#: ../Doc/library/lzma.rst:114 +msgid "" +"While calling :meth:`peek` does not change the file position of the :class:" +"`LZMAFile`, it may change the position of the underlying file object (e.g. " +"if the :class:`LZMAFile` was constructed by passing a file object for " +"*filename*)." +msgstr "" + +#: ../Doc/library/lzma.rst:119 +msgid "Added support for the ``\"x\"`` and ``\"xb\"`` modes." +msgstr "" + +#: ../Doc/library/lzma.rst:131 +msgid "Compressing and decompressing data in memory" +msgstr "" + +#: ../Doc/library/lzma.rst:135 +msgid "" +"Create a compressor object, which can be used to compress data incrementally." +msgstr "" + +#: ../Doc/library/lzma.rst:137 +msgid "" +"For a more convenient way of compressing a single chunk of data, see :func:" +"`compress`." +msgstr "" + +#: ../Doc/library/lzma.rst:140 +msgid "" +"The *format* argument specifies what container format should be used. " +"Possible values are:" +msgstr "" + +#: ../Doc/library/lzma.rst:144 +msgid ":const:`FORMAT_XZ`: The ``.xz`` container format." +msgstr "" + +#: ../Doc/library/lzma.rst:144 +msgid "This is the default format." +msgstr "" + +#: ../Doc/library/lzma.rst:148 +msgid ":const:`FORMAT_ALONE`: The legacy ``.lzma`` container format." +msgstr "" + +#: ../Doc/library/lzma.rst:147 +msgid "" +"This format is more limited than ``.xz`` -- it does not support integrity " +"checks or multiple filters." +msgstr "" + +#: ../Doc/library/lzma.rst:154 +msgid ":const:`FORMAT_RAW`: A raw data stream, not using any container format." +msgstr "" + +#: ../Doc/library/lzma.rst:151 +msgid "" +"This format specifier does not support integrity checks, and requires that " +"you always specify a custom filter chain (for both compression and " +"decompression). Additionally, data compressed in this manner cannot be " +"decompressed using :const:`FORMAT_AUTO` (see :class:`LZMADecompressor`)." +msgstr "" + +#: ../Doc/library/lzma.rst:156 +msgid "" +"The *check* argument specifies the type of integrity check to include in the " +"compressed data. This check is used when decompressing, to ensure that the " +"data has not been corrupted. Possible values are:" +msgstr "" + +#: ../Doc/library/lzma.rst:160 +msgid "" +":const:`CHECK_NONE`: No integrity check. This is the default (and the only " +"acceptable value) for :const:`FORMAT_ALONE` and :const:`FORMAT_RAW`." +msgstr "" + +#: ../Doc/library/lzma.rst:164 +msgid ":const:`CHECK_CRC32`: 32-bit Cyclic Redundancy Check." +msgstr "" + +#: ../Doc/library/lzma.rst:166 +msgid "" +":const:`CHECK_CRC64`: 64-bit Cyclic Redundancy Check. This is the default " +"for :const:`FORMAT_XZ`." +msgstr "" + +#: ../Doc/library/lzma.rst:169 +msgid ":const:`CHECK_SHA256`: 256-bit Secure Hash Algorithm." +msgstr "" + +#: ../Doc/library/lzma.rst:171 +msgid "" +"If the specified check is not supported, an :class:`LZMAError` is raised." +msgstr "" + +#: ../Doc/library/lzma.rst:173 +msgid "" +"The compression settings can be specified either as a preset compression " +"level (with the *preset* argument), or in detail as a custom filter chain " +"(with the *filters* argument)." +msgstr "" + +#: ../Doc/library/lzma.rst:177 +msgid "" +"The *preset* argument (if provided) should be an integer between ``0`` and " +"``9`` (inclusive), optionally OR-ed with the constant :const:" +"`PRESET_EXTREME`. If neither *preset* nor *filters* are given, the default " +"behavior is to use :const:`PRESET_DEFAULT` (preset level ``6``). Higher " +"presets produce smaller output, but make the compression process slower." +msgstr "" + +#: ../Doc/library/lzma.rst:186 +msgid "" +"In addition to being more CPU-intensive, compression with higher presets " +"also requires much more memory (and produces output that needs more memory " +"to decompress). With preset ``9`` for example, the overhead for an :class:" +"`LZMACompressor` object can be as high as 800 MiB. For this reason, it is " +"generally best to stick with the default preset." +msgstr "" + +#: ../Doc/library/lzma.rst:192 +msgid "" +"The *filters* argument (if provided) should be a filter chain specifier. " +"See :ref:`filter-chain-specs` for details." +msgstr "" + +#: ../Doc/library/lzma.rst:197 +msgid "" +"Compress *data* (a :class:`bytes` object), returning a :class:`bytes` object " +"containing compressed data for at least part of the input. Some of *data* " +"may be buffered internally, for use in later calls to :meth:`compress` and :" +"meth:`flush`. The returned data should be concatenated with the output of " +"any previous calls to :meth:`compress`." +msgstr "" + +#: ../Doc/library/lzma.rst:205 +msgid "" +"Finish the compression process, returning a :class:`bytes` object containing " +"any data stored in the compressor's internal buffers." +msgstr "" + +#: ../Doc/library/lzma.rst:208 +msgid "The compressor cannot be used after this method has been called." +msgstr "" + +#: ../Doc/library/lzma.rst:213 +msgid "" +"Create a decompressor object, which can be used to decompress data " +"incrementally." +msgstr "" + +#: ../Doc/library/lzma.rst:216 +msgid "" +"For a more convenient way of decompressing an entire compressed stream at " +"once, see :func:`decompress`." +msgstr "" + +#: ../Doc/library/lzma.rst:219 +msgid "" +"The *format* argument specifies the container format that should be used. " +"The default is :const:`FORMAT_AUTO`, which can decompress both ``.xz`` and " +"``.lzma`` files. Other possible values are :const:`FORMAT_XZ`, :const:" +"`FORMAT_ALONE`, and :const:`FORMAT_RAW`." +msgstr "" + +#: ../Doc/library/lzma.rst:224 +msgid "" +"The *memlimit* argument specifies a limit (in bytes) on the amount of memory " +"that the decompressor can use. When this argument is used, decompression " +"will fail with an :class:`LZMAError` if it is not possible to decompress the " +"input within the given memory limit." +msgstr "" + +#: ../Doc/library/lzma.rst:229 +msgid "" +"The *filters* argument specifies the filter chain that was used to create " +"the stream being decompressed. This argument is required if *format* is :" +"const:`FORMAT_RAW`, but should not be used for other formats. See :ref:" +"`filter-chain-specs` for more information about filter chains." +msgstr "" + +#: ../Doc/library/lzma.rst:235 +msgid "" +"This class does not transparently handle inputs containing multiple " +"compressed streams, unlike :func:`decompress` and :class:`LZMAFile`. To " +"decompress a multi-stream input with :class:`LZMADecompressor`, you must " +"create a new decompressor for each stream." +msgstr "" + +#: ../Doc/library/lzma.rst:269 +msgid "" +"The ID of the integrity check used by the input stream. This may be :const:" +"`CHECK_UNKNOWN` until enough of the input has been decoded to determine what " +"integrity check it uses." +msgstr "" + +#: ../Doc/library/lzma.rst:281 +msgid "Before the end of the stream is reached, this will be ``b\"\"``." +msgstr "" + +#: ../Doc/library/lzma.rst:292 +msgid "" +"Compress *data* (a :class:`bytes` object), returning the compressed data as " +"a :class:`bytes` object." +msgstr "" + +#: ../Doc/library/lzma.rst:295 +msgid "" +"See :class:`LZMACompressor` above for a description of the *format*, " +"*check*, *preset* and *filters* arguments." +msgstr "" + +#: ../Doc/library/lzma.rst:301 +msgid "" +"Decompress *data* (a :class:`bytes` object), returning the uncompressed data " +"as a :class:`bytes` object." +msgstr "" + +#: ../Doc/library/lzma.rst:304 +msgid "" +"If *data* is the concatenation of multiple distinct compressed streams, " +"decompress all of these streams, and return the concatenation of the results." +msgstr "" + +#: ../Doc/library/lzma.rst:307 +msgid "" +"See :class:`LZMADecompressor` above for a description of the *format*, " +"*memlimit* and *filters* arguments." +msgstr "" + +#: ../Doc/library/lzma.rst:312 ../Doc/library/multiprocessing.rst:882 +msgid "Miscellaneous" +msgstr "" + +#: ../Doc/library/lzma.rst:316 +msgid "Returns true if the given integrity check is supported on this system." +msgstr "" + +#: ../Doc/library/lzma.rst:318 +msgid "" +":const:`CHECK_NONE` and :const:`CHECK_CRC32` are always supported. :const:" +"`CHECK_CRC64` and :const:`CHECK_SHA256` may be unavailable if you are using " +"a version of :program:`liblzma` that was compiled with a limited feature set." +msgstr "" + +#: ../Doc/library/lzma.rst:327 +msgid "Specifying custom filter chains" +msgstr "" + +#: ../Doc/library/lzma.rst:329 +msgid "" +"A filter chain specifier is a sequence of dictionaries, where each " +"dictionary contains the ID and options for a single filter. Each dictionary " +"must contain the key ``\"id\"``, and may contain additional keys to specify " +"filter-dependent options. Valid filter IDs are as follows:" +msgstr "" + +#: ../Doc/library/lzma.rst:336 +msgid "Compression filters:" +msgstr "" + +#: ../Doc/library/lzma.rst:335 +msgid ":const:`FILTER_LZMA1` (for use with :const:`FORMAT_ALONE`)" +msgstr "" + +#: ../Doc/library/lzma.rst:336 +msgid "" +":const:`FILTER_LZMA2` (for use with :const:`FORMAT_XZ` and :const:" +"`FORMAT_RAW`)" +msgstr "" + +#: ../Doc/library/lzma.rst:339 +msgid "Delta filter:" +msgstr "" + +#: ../Doc/library/lzma.rst:339 +msgid ":const:`FILTER_DELTA`" +msgstr "" + +#: ../Doc/library/lzma.rst:347 +msgid "Branch-Call-Jump (BCJ) filters:" +msgstr "" + +#: ../Doc/library/lzma.rst:342 +msgid ":const:`FILTER_X86`" +msgstr "" + +#: ../Doc/library/lzma.rst:343 +msgid ":const:`FILTER_IA64`" +msgstr "" + +#: ../Doc/library/lzma.rst:344 +msgid ":const:`FILTER_ARM`" +msgstr "" + +#: ../Doc/library/lzma.rst:345 +msgid ":const:`FILTER_ARMTHUMB`" +msgstr "" + +#: ../Doc/library/lzma.rst:346 +msgid ":const:`FILTER_POWERPC`" +msgstr "" + +#: ../Doc/library/lzma.rst:347 +msgid ":const:`FILTER_SPARC`" +msgstr "" + +#: ../Doc/library/lzma.rst:349 +msgid "" +"A filter chain can consist of up to 4 filters, and cannot be empty. The last " +"filter in the chain must be a compression filter, and any other filters must " +"be delta or BCJ filters." +msgstr "" + +#: ../Doc/library/lzma.rst:353 +msgid "" +"Compression filters support the following options (specified as additional " +"entries in the dictionary representing the filter):" +msgstr "" + +#: ../Doc/library/lzma.rst:356 +msgid "" +"``preset``: A compression preset to use as a source of default values for " +"options that are not specified explicitly." +msgstr "" + +#: ../Doc/library/lzma.rst:358 +msgid "" +"``dict_size``: Dictionary size in bytes. This should be between 4 KiB and " +"1.5 GiB (inclusive)." +msgstr "" + +#: ../Doc/library/lzma.rst:360 +msgid "``lc``: Number of literal context bits." +msgstr "" + +#: ../Doc/library/lzma.rst:361 +msgid "" +"``lp``: Number of literal position bits. The sum ``lc + lp`` must be at most " +"4." +msgstr "" + +#: ../Doc/library/lzma.rst:363 +msgid "``pb``: Number of position bits; must be at most 4." +msgstr "" + +#: ../Doc/library/lzma.rst:364 +msgid "``mode``: :const:`MODE_FAST` or :const:`MODE_NORMAL`." +msgstr "" + +#: ../Doc/library/lzma.rst:365 +msgid "" +"``nice_len``: What should be considered a \"nice length\" for a match. This " +"should be 273 or less." +msgstr "" + +#: ../Doc/library/lzma.rst:367 +msgid "" +"``mf``: What match finder to use -- :const:`MF_HC3`, :const:`MF_HC4`, :const:" +"`MF_BT2`, :const:`MF_BT3`, or :const:`MF_BT4`." +msgstr "" + +#: ../Doc/library/lzma.rst:369 +msgid "" +"``depth``: Maximum search depth used by match finder. 0 (default) means to " +"select automatically based on other filter options." +msgstr "" + +#: ../Doc/library/lzma.rst:372 +msgid "" +"The delta filter stores the differences between bytes, producing more " +"repetitive input for the compressor in certain circumstances. It supports " +"one option, ``dist``. This indicates the distance between bytes to be " +"subtracted. The default is 1, i.e. take the differences between adjacent " +"bytes." +msgstr "" + +#: ../Doc/library/lzma.rst:377 +msgid "" +"The BCJ filters are intended to be applied to machine code. They convert " +"relative branches, calls and jumps in the code to use absolute addressing, " +"with the aim of increasing the redundancy that can be exploited by the " +"compressor. These filters support one option, ``start_offset``. This " +"specifies the address that should be mapped to the beginning of the input " +"data. The default is 0." +msgstr "" + +#: ../Doc/library/lzma.rst:387 +msgid "Reading in a compressed file::" +msgstr "" + +#: ../Doc/library/lzma.rst:393 +msgid "Creating a compressed file::" +msgstr "" + +#: ../Doc/library/lzma.rst:400 +msgid "Compressing data in memory::" +msgstr "" + +#: ../Doc/library/lzma.rst:406 +msgid "Incremental compression::" +msgstr "" + +#: ../Doc/library/lzma.rst:417 +msgid "Writing compressed data to an already-open file::" +msgstr "" + +#: ../Doc/library/lzma.rst:426 +msgid "Creating a compressed file using a custom filter chain::" +msgstr "" + +#: ../Doc/library/macpath.rst:2 +msgid ":mod:`macpath` --- Mac OS 9 path manipulation functions" +msgstr "" + +#: ../Doc/library/macpath.rst:7 +msgid "**Source code:** :source:`Lib/macpath.py`" +msgstr "" + +#: ../Doc/library/macpath.rst:11 +msgid "" +"This module is the Mac OS 9 (and earlier) implementation of the :mod:`os." +"path` module. It can be used to manipulate old-style Macintosh pathnames on " +"Mac OS X (or any other platform)." +msgstr "" + +#: ../Doc/library/macpath.rst:15 +msgid "" +"The following functions are available in this module: :func:`normcase`, :" +"func:`normpath`, :func:`isabs`, :func:`join`, :func:`split`, :func:`isdir`, :" +"func:`isfile`, :func:`walk`, :func:`exists`. For other functions available " +"in :mod:`os.path` dummy counterparts are available." +msgstr "" + +#: ../Doc/library/mailbox.rst:2 +msgid ":mod:`mailbox` --- Manipulate mailboxes in various formats" +msgstr "" + +#: ../Doc/library/mailbox.rst:10 +msgid "**Source code:** :source:`Lib/mailbox.py`" +msgstr "" + +#: ../Doc/library/mailbox.rst:14 +msgid "" +"This module defines two classes, :class:`Mailbox` and :class:`Message`, for " +"accessing and manipulating on-disk mailboxes and the messages they contain. :" +"class:`Mailbox` offers a dictionary-like mapping from keys to messages. :" +"class:`Message` extends the :mod:`email.message` module's :class:`~email." +"message.Message` class with format-specific state and behavior. Supported " +"mailbox formats are Maildir, mbox, MH, Babyl, and MMDF." +msgstr "" + +#: ../Doc/library/mailbox.rst:24 +msgid "Module :mod:`email`" +msgstr "" + +#: ../Doc/library/mailbox.rst:25 +msgid "Represent and manipulate messages." +msgstr "" + +#: ../Doc/library/mailbox.rst:31 +msgid ":class:`Mailbox` objects" +msgstr "" + +#: ../Doc/library/mailbox.rst:35 +msgid "A mailbox, which may be inspected and modified." +msgstr "" + +#: ../Doc/library/mailbox.rst:37 +msgid "" +"The :class:`Mailbox` class defines an interface and is not intended to be " +"instantiated. Instead, format-specific subclasses should inherit from :" +"class:`Mailbox` and your code should instantiate a particular subclass." +msgstr "" + +#: ../Doc/library/mailbox.rst:41 +msgid "" +"The :class:`Mailbox` interface is dictionary-like, with small keys " +"corresponding to messages. Keys are issued by the :class:`Mailbox` instance " +"with which they will be used and are only meaningful to that :class:" +"`Mailbox` instance. A key continues to identify a message even if the " +"corresponding message is modified, such as by replacing it with another " +"message." +msgstr "" + +#: ../Doc/library/mailbox.rst:47 +msgid "" +"Messages may be added to a :class:`Mailbox` instance using the set-like " +"method :meth:`add` and removed using a ``del`` statement or the set-like " +"methods :meth:`remove` and :meth:`discard`." +msgstr "" + +#: ../Doc/library/mailbox.rst:51 +msgid "" +":class:`Mailbox` interface semantics differ from dictionary semantics in " +"some noteworthy ways. Each time a message is requested, a new representation " +"(typically a :class:`Message` instance) is generated based upon the current " +"state of the mailbox. Similarly, when a message is added to a :class:" +"`Mailbox` instance, the provided message representation's contents are " +"copied. In neither case is a reference to the message representation kept by " +"the :class:`Mailbox` instance." +msgstr "" + +#: ../Doc/library/mailbox.rst:59 +msgid "" +"The default :class:`Mailbox` iterator iterates over message representations, " +"not keys as the default dictionary iterator does. Moreover, modification of " +"a mailbox during iteration is safe and well-defined. Messages added to the " +"mailbox after an iterator is created will not be seen by the iterator. " +"Messages removed from the mailbox before the iterator yields them will be " +"silently skipped, though using a key from an iterator may result in a :exc:" +"`KeyError` exception if the corresponding message is subsequently removed." +msgstr "" + +#: ../Doc/library/mailbox.rst:70 +msgid "" +"Be very cautious when modifying mailboxes that might be simultaneously " +"changed by some other process. The safest mailbox format to use for such " +"tasks is Maildir; try to avoid using single-file formats such as mbox for " +"concurrent writing. If you're modifying a mailbox, you *must* lock it by " +"calling the :meth:`lock` and :meth:`unlock` methods *before* reading any " +"messages in the file or making any changes by adding or deleting a message. " +"Failing to lock the mailbox runs the risk of losing messages or corrupting " +"the entire mailbox." +msgstr "" + +#: ../Doc/library/mailbox.rst:79 +msgid ":class:`Mailbox` instances have the following methods:" +msgstr "" + +#: ../Doc/library/mailbox.rst:84 +msgid "" +"Add *message* to the mailbox and return the key that has been assigned to it." +msgstr "" + +#: ../Doc/library/mailbox.rst:87 +msgid "" +"Parameter *message* may be a :class:`Message` instance, an :class:`email." +"message.Message` instance, a string, a byte string, or a file-like object " +"(which should be open in binary mode). If *message* is an instance of the " +"appropriate format-specific :class:`Message` subclass (e.g., if it's an :" +"class:`mboxMessage` instance and this is an :class:`mbox` instance), its " +"format-specific information is used. Otherwise, reasonable defaults for " +"format-specific information are used." +msgstr "" + +#: ../Doc/library/mailbox.rst:96 +msgid "Support for binary input was added." +msgstr "" + +#: ../Doc/library/mailbox.rst:104 +msgid "Delete the message corresponding to *key* from the mailbox." +msgstr "" + +#: ../Doc/library/mailbox.rst:106 +msgid "" +"If no such message exists, a :exc:`KeyError` exception is raised if the " +"method was called as :meth:`remove` or :meth:`__delitem__` but no exception " +"is raised if the method was called as :meth:`discard`. The behavior of :meth:" +"`discard` may be preferred if the underlying mailbox format supports " +"concurrent modification by other processes." +msgstr "" + +#: ../Doc/library/mailbox.rst:115 +msgid "" +"Replace the message corresponding to *key* with *message*. Raise a :exc:" +"`KeyError` exception if no message already corresponds to *key*." +msgstr "" + +#: ../Doc/library/mailbox.rst:118 +msgid "" +"As with :meth:`add`, parameter *message* may be a :class:`Message` instance, " +"an :class:`email.message.Message` instance, a string, a byte string, or a " +"file-like object (which should be open in binary mode). If *message* is an " +"instance of the appropriate format-specific :class:`Message` subclass (e.g., " +"if it's an :class:`mboxMessage` instance and this is an :class:`mbox` " +"instance), its format-specific information is used. Otherwise, the format-" +"specific information of the message that currently corresponds to *key* is " +"left unchanged." +msgstr "" + +#: ../Doc/library/mailbox.rst:132 +msgid "" +"Return an iterator over all keys if called as :meth:`iterkeys` or return a " +"list of keys if called as :meth:`keys`." +msgstr "" + +#: ../Doc/library/mailbox.rst:140 +msgid "" +"Return an iterator over representations of all messages if called as :meth:" +"`itervalues` or :meth:`__iter__` or return a list of such representations if " +"called as :meth:`values`. The messages are represented as instances of the " +"appropriate format-specific :class:`Message` subclass unless a custom " +"message factory was specified when the :class:`Mailbox` instance was " +"initialized." +msgstr "" + +#: ../Doc/library/mailbox.rst:149 +msgid "" +"The behavior of :meth:`__iter__` is unlike that of dictionaries, which " +"iterate over keys." +msgstr "" + +#: ../Doc/library/mailbox.rst:156 +msgid "" +"Return an iterator over (*key*, *message*) pairs, where *key* is a key and " +"*message* is a message representation, if called as :meth:`iteritems` or " +"return a list of such pairs if called as :meth:`items`. The messages are " +"represented as instances of the appropriate format-specific :class:`Message` " +"subclass unless a custom message factory was specified when the :class:" +"`Mailbox` instance was initialized." +msgstr "" + +#: ../Doc/library/mailbox.rst:167 +msgid "" +"Return a representation of the message corresponding to *key*. If no such " +"message exists, *default* is returned if the method was called as :meth:" +"`get` and a :exc:`KeyError` exception is raised if the method was called as :" +"meth:`__getitem__`. The message is represented as an instance of the " +"appropriate format-specific :class:`Message` subclass unless a custom " +"message factory was specified when the :class:`Mailbox` instance was " +"initialized." +msgstr "" + +#: ../Doc/library/mailbox.rst:178 +msgid "" +"Return a representation of the message corresponding to *key* as an instance " +"of the appropriate format-specific :class:`Message` subclass, or raise a :" +"exc:`KeyError` exception if no such message exists." +msgstr "" + +#: ../Doc/library/mailbox.rst:185 +msgid "" +"Return a byte representation of the message corresponding to *key*, or raise " +"a :exc:`KeyError` exception if no such message exists." +msgstr "" + +#: ../Doc/library/mailbox.rst:193 +msgid "" +"Return a string representation of the message corresponding to *key*, or " +"raise a :exc:`KeyError` exception if no such message exists. The message is " +"processed through :class:`email.message.Message` to convert it to a 7bit " +"clean representation." +msgstr "" + +#: ../Doc/library/mailbox.rst:201 +msgid "" +"Return a file-like representation of the message corresponding to *key*, or " +"raise a :exc:`KeyError` exception if no such message exists. The file-like " +"object behaves as if open in binary mode. This file should be closed once " +"it is no longer needed." +msgstr "" + +#: ../Doc/library/mailbox.rst:206 +msgid "" +"The file object really is a binary file; previously it was incorrectly " +"returned in text mode. Also, the file-like object now supports the context " +"management protocol: you can use a :keyword:`with` statement to " +"automatically close it." +msgstr "" + +#: ../Doc/library/mailbox.rst:214 +msgid "" +"Unlike other representations of messages, file-like representations are not " +"necessarily independent of the :class:`Mailbox` instance that created them " +"or of the underlying mailbox. More specific documentation is provided by " +"each subclass." +msgstr "" + +#: ../Doc/library/mailbox.rst:222 +msgid "Return ``True`` if *key* corresponds to a message, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/mailbox.rst:227 +msgid "Return a count of messages in the mailbox." +msgstr "" + +#: ../Doc/library/mailbox.rst:232 +msgid "Delete all messages from the mailbox." +msgstr "" + +#: ../Doc/library/mailbox.rst:237 +msgid "" +"Return a representation of the message corresponding to *key* and delete the " +"message. If no such message exists, return *default*. The message is " +"represented as an instance of the appropriate format-specific :class:" +"`Message` subclass unless a custom message factory was specified when the :" +"class:`Mailbox` instance was initialized." +msgstr "" + +#: ../Doc/library/mailbox.rst:246 +msgid "" +"Return an arbitrary (*key*, *message*) pair, where *key* is a key and " +"*message* is a message representation, and delete the corresponding message. " +"If the mailbox is empty, raise a :exc:`KeyError` exception. The message is " +"represented as an instance of the appropriate format-specific :class:" +"`Message` subclass unless a custom message factory was specified when the :" +"class:`Mailbox` instance was initialized." +msgstr "" + +#: ../Doc/library/mailbox.rst:256 +msgid "" +"Parameter *arg* should be a *key*-to-*message* mapping or an iterable of " +"(*key*, *message*) pairs. Updates the mailbox so that, for each given *key* " +"and *message*, the message corresponding to *key* is set to *message* as if " +"by using :meth:`__setitem__`. As with :meth:`__setitem__`, each *key* must " +"already correspond to a message in the mailbox or else a :exc:`KeyError` " +"exception will be raised, so in general it is incorrect for *arg* to be a :" +"class:`Mailbox` instance." +msgstr "" + +#: ../Doc/library/mailbox.rst:266 +msgid "Unlike with dictionaries, keyword arguments are not supported." +msgstr "" + +#: ../Doc/library/mailbox.rst:271 +msgid "" +"Write any pending changes to the filesystem. For some :class:`Mailbox` " +"subclasses, changes are always written immediately and :meth:`flush` does " +"nothing, but you should still make a habit of calling this method." +msgstr "" + +#: ../Doc/library/mailbox.rst:278 +msgid "" +"Acquire an exclusive advisory lock on the mailbox so that other processes " +"know not to modify it. An :exc:`ExternalClashError` is raised if the lock is " +"not available. The particular locking mechanisms used depend upon the " +"mailbox format. You should *always* lock the mailbox before making any " +"modifications to its contents." +msgstr "" + +#: ../Doc/library/mailbox.rst:287 +msgid "Release the lock on the mailbox, if any." +msgstr "" + +#: ../Doc/library/mailbox.rst:292 +msgid "" +"Flush the mailbox, unlock it if necessary, and close any open files. For " +"some :class:`Mailbox` subclasses, this method does nothing." +msgstr "" + +#: ../Doc/library/mailbox.rst:299 +msgid ":class:`Maildir`" +msgstr "" + +#: ../Doc/library/mailbox.rst:304 +msgid "" +"A subclass of :class:`Mailbox` for mailboxes in Maildir format. Parameter " +"*factory* is a callable object that accepts a file-like message " +"representation (which behaves as if opened in binary mode) and returns a " +"custom representation. If *factory* is ``None``, :class:`MaildirMessage` is " +"used as the default message representation. If *create* is ``True``, the " +"mailbox is created if it does not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:311 +msgid "" +"It is for historical reasons that *dirname* is named as such rather than " +"*path*." +msgstr "" + +#: ../Doc/library/mailbox.rst:313 +msgid "" +"Maildir is a directory-based mailbox format invented for the qmail mail " +"transfer agent and now widely supported by other programs. Messages in a " +"Maildir mailbox are stored in separate files within a common directory " +"structure. This design allows Maildir mailboxes to be accessed and modified " +"by multiple unrelated programs without data corruption, so file locking is " +"unnecessary." +msgstr "" + +#: ../Doc/library/mailbox.rst:320 +msgid "" +"Maildir mailboxes contain three subdirectories, namely: :file:`tmp`, :file:" +"`new`, and :file:`cur`. Messages are created momentarily in the :file:`tmp` " +"subdirectory and then moved to the :file:`new` subdirectory to finalize " +"delivery. A mail user agent may subsequently move the message to the :file:" +"`cur` subdirectory and store information about the state of the message in a " +"special \"info\" section appended to its file name." +msgstr "" + +#: ../Doc/library/mailbox.rst:327 +msgid "" +"Folders of the style introduced by the Courier mail transfer agent are also " +"supported. Any subdirectory of the main mailbox is considered a folder if " +"``'.'`` is the first character in its name. Folder names are represented by :" +"class:`Maildir` without the leading ``'.'``. Each folder is itself a Maildir " +"mailbox but should not contain other folders. Instead, a logical nesting is " +"indicated using ``'.'`` to delimit levels, e.g., \"Archived.2005.07\"." +msgstr "" + +#: ../Doc/library/mailbox.rst:336 +msgid "" +"The Maildir specification requires the use of a colon (``':'``) in certain " +"message file names. However, some operating systems do not permit this " +"character in file names, If you wish to use a Maildir-like format on such an " +"operating system, you should specify another character to use instead. The " +"exclamation point (``'!'``) is a popular choice. For example::" +msgstr "" + +#: ../Doc/library/mailbox.rst:346 +msgid "The :attr:`colon` attribute may also be set on a per-instance basis." +msgstr "" + +#: ../Doc/library/mailbox.rst:348 +msgid "" +":class:`Maildir` instances have all of the methods of :class:`Mailbox` in " +"addition to the following:" +msgstr "" + +#: ../Doc/library/mailbox.rst:354 ../Doc/library/mailbox.rst:532 +msgid "Return a list of the names of all folders." +msgstr "" + +#: ../Doc/library/mailbox.rst:359 +msgid "" +"Return a :class:`Maildir` instance representing the folder whose name is " +"*folder*. A :exc:`NoSuchMailboxError` exception is raised if the folder does " +"not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:366 +msgid "" +"Create a folder whose name is *folder* and return a :class:`Maildir` " +"instance representing it." +msgstr "" + +#: ../Doc/library/mailbox.rst:372 ../Doc/library/mailbox.rst:550 +msgid "" +"Delete the folder whose name is *folder*. If the folder contains any " +"messages, a :exc:`NotEmptyError` exception will be raised and the folder " +"will not be deleted." +msgstr "" + +#: ../Doc/library/mailbox.rst:379 +msgid "" +"Delete temporary files from the mailbox that have not been accessed in the " +"last 36 hours. The Maildir specification says that mail-reading programs " +"should do this occasionally." +msgstr "" + +#: ../Doc/library/mailbox.rst:383 +msgid "" +"Some :class:`Mailbox` methods implemented by :class:`Maildir` deserve " +"special remarks:" +msgstr "" + +#: ../Doc/library/mailbox.rst:393 +msgid "" +"These methods generate unique file names based upon the current process ID. " +"When using multiple threads, undetected name clashes may occur and cause " +"corruption of the mailbox unless threads are coordinated to avoid using " +"these methods to manipulate the same mailbox simultaneously." +msgstr "" + +#: ../Doc/library/mailbox.rst:401 +msgid "" +"All changes to Maildir mailboxes are immediately applied, so this method " +"does nothing." +msgstr "" + +#: ../Doc/library/mailbox.rst:408 +msgid "" +"Maildir mailboxes do not support (or require) locking, so these methods do " +"nothing." +msgstr "" + +#: ../Doc/library/mailbox.rst:414 +msgid "" +":class:`Maildir` instances do not keep any open files and the underlying " +"mailboxes do not support locking, so this method does nothing." +msgstr "" + +#: ../Doc/library/mailbox.rst:420 +msgid "" +"Depending upon the host platform, it may not be possible to modify or remove " +"the underlying message while the returned file remains open." +msgstr "" + +#: ../Doc/library/mailbox.rst:427 +msgid "" +"`maildir man page from qmail `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:427 +msgid "The original specification of the format." +msgstr "" + +#: ../Doc/library/mailbox.rst:431 +msgid "`Using maildir format `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:430 +msgid "" +"Notes on Maildir by its inventor. Includes an updated name-creation scheme " +"and details on \"info\" semantics." +msgstr "" + +#: ../Doc/library/mailbox.rst:434 +msgid "" +"`maildir man page from Courier `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:434 +msgid "" +"Another specification of the format. Describes a common extension for " +"supporting folders." +msgstr "" + +#: ../Doc/library/mailbox.rst:441 +msgid ":class:`mbox`" +msgstr "" + +#: ../Doc/library/mailbox.rst:446 +msgid "" +"A subclass of :class:`Mailbox` for mailboxes in mbox format. Parameter " +"*factory* is a callable object that accepts a file-like message " +"representation (which behaves as if opened in binary mode) and returns a " +"custom representation. If *factory* is ``None``, :class:`mboxMessage` is " +"used as the default message representation. If *create* is ``True``, the " +"mailbox is created if it does not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:453 +msgid "" +"The mbox format is the classic format for storing mail on Unix systems. All " +"messages in an mbox mailbox are stored in a single file with the beginning " +"of each message indicated by a line whose first five characters are \"From " +"\"." +msgstr "" + +#: ../Doc/library/mailbox.rst:457 +msgid "" +"Several variations of the mbox format exist to address perceived " +"shortcomings in the original. In the interest of compatibility, :class:" +"`mbox` implements the original format, which is sometimes referred to as :" +"dfn:`mboxo`. This means that the :mailheader:`Content-Length` header, if " +"present, is ignored and that any occurrences of \"From \" at the beginning " +"of a line in a message body are transformed to \">From \" when storing the " +"message, although occurrences of \">From \" are not transformed to \"From \" " +"when reading the message." +msgstr "" + +#: ../Doc/library/mailbox.rst:465 +msgid "" +"Some :class:`Mailbox` methods implemented by :class:`mbox` deserve special " +"remarks:" +msgstr "" + +#: ../Doc/library/mailbox.rst:471 +msgid "" +"Using the file after calling :meth:`flush` or :meth:`close` on the :class:" +"`mbox` instance may yield unpredictable results or raise an exception." +msgstr "" + +#: ../Doc/library/mailbox.rst:479 ../Doc/library/mailbox.rst:691 +#: ../Doc/library/mailbox.rst:742 +msgid "" +"Three locking mechanisms are used---dot locking and, if available, the :c:" +"func:`flock` and :c:func:`lockf` system calls." +msgstr "" + +#: ../Doc/library/mailbox.rst:486 +msgid "`mbox man page from qmail `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:486 +msgid "A specification of the format and its variations." +msgstr "" + +#: ../Doc/library/mailbox.rst:489 +msgid "" +"`mbox man page from tin `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:489 +msgid "Another specification of the format, with details on locking." +msgstr "" + +#: ../Doc/library/mailbox.rst:492 +msgid "" +"`Configuring Netscape Mail on Unix: Why The Content-Length Format is Bad " +"`_" +msgstr "" + +#: ../Doc/library/mailbox.rst:492 +msgid "An argument for using the original mbox format rather than a variation." +msgstr "" + +#: ../Doc/library/mailbox.rst:494 +msgid "" +"`\"mbox\" is a family of several mutually incompatible mailbox formats " +"`_" +msgstr "" + +#: ../Doc/library/mailbox.rst:495 +msgid "A history of mbox variations." +msgstr "" + +#: ../Doc/library/mailbox.rst:501 +msgid ":class:`MH`" +msgstr "" + +#: ../Doc/library/mailbox.rst:506 +msgid "" +"A subclass of :class:`Mailbox` for mailboxes in MH format. Parameter " +"*factory* is a callable object that accepts a file-like message " +"representation (which behaves as if opened in binary mode) and returns a " +"custom representation. If *factory* is ``None``, :class:`MHMessage` is used " +"as the default message representation. If *create* is ``True``, the mailbox " +"is created if it does not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:513 +msgid "" +"MH is a directory-based mailbox format invented for the MH Message Handling " +"System, a mail user agent. Each message in an MH mailbox resides in its own " +"file. An MH mailbox may contain other MH mailboxes (called :dfn:`folders`) " +"in addition to messages. Folders may be nested indefinitely. MH mailboxes " +"also support :dfn:`sequences`, which are named lists used to logically group " +"messages without moving them to sub-folders. Sequences are defined in a file " +"called :file:`.mh_sequences` in each folder." +msgstr "" + +#: ../Doc/library/mailbox.rst:521 +msgid "" +"The :class:`MH` class manipulates MH mailboxes, but it does not attempt to " +"emulate all of :program:`mh`'s behaviors. In particular, it does not modify " +"and is not affected by the :file:`context` or :file:`.mh_profile` files that " +"are used by :program:`mh` to store its state and configuration." +msgstr "" + +#: ../Doc/library/mailbox.rst:526 +msgid "" +":class:`MH` instances have all of the methods of :class:`Mailbox` in " +"addition to the following:" +msgstr "" + +#: ../Doc/library/mailbox.rst:537 +msgid "" +"Return an :class:`MH` instance representing the folder whose name is " +"*folder*. A :exc:`NoSuchMailboxError` exception is raised if the folder does " +"not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:544 +msgid "" +"Create a folder whose name is *folder* and return an :class:`MH` instance " +"representing it." +msgstr "" + +#: ../Doc/library/mailbox.rst:557 +msgid "" +"Return a dictionary of sequence names mapped to key lists. If there are no " +"sequences, the empty dictionary is returned." +msgstr "" + +#: ../Doc/library/mailbox.rst:563 +msgid "" +"Re-define the sequences that exist in the mailbox based upon *sequences*, a " +"dictionary of names mapped to key lists, like returned by :meth:" +"`get_sequences`." +msgstr "" + +#: ../Doc/library/mailbox.rst:570 +msgid "" +"Rename messages in the mailbox as necessary to eliminate gaps in numbering. " +"Entries in the sequences list are updated correspondingly." +msgstr "" + +#: ../Doc/library/mailbox.rst:575 +msgid "" +"Already-issued keys are invalidated by this operation and should not be " +"subsequently used." +msgstr "" + +#: ../Doc/library/mailbox.rst:578 +msgid "" +"Some :class:`Mailbox` methods implemented by :class:`MH` deserve special " +"remarks:" +msgstr "" + +#: ../Doc/library/mailbox.rst:586 +msgid "" +"These methods immediately delete the message. The MH convention of marking a " +"message for deletion by prepending a comma to its name is not used." +msgstr "" + +#: ../Doc/library/mailbox.rst:593 +msgid "" +"Three locking mechanisms are used---dot locking and, if available, the :c:" +"func:`flock` and :c:func:`lockf` system calls. For MH mailboxes, locking the " +"mailbox means locking the :file:`.mh_sequences` file and, only for the " +"duration of any operations that affect them, locking individual message " +"files." +msgstr "" + +#: ../Doc/library/mailbox.rst:602 +msgid "" +"Depending upon the host platform, it may not be possible to remove the " +"underlying message while the returned file remains open." +msgstr "" + +#: ../Doc/library/mailbox.rst:608 +msgid "" +"All changes to MH mailboxes are immediately applied, so this method does " +"nothing." +msgstr "" + +#: ../Doc/library/mailbox.rst:614 +msgid "" +":class:`MH` instances do not keep any open files, so this method is " +"equivalent to :meth:`unlock`." +msgstr "" + +#: ../Doc/library/mailbox.rst:621 +msgid "`nmh - Message Handling System `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:621 +msgid "" +"Home page of :program:`nmh`, an updated version of the original :program:" +"`mh`." +msgstr "" + +#: ../Doc/library/mailbox.rst:624 +msgid "" +"`MH & nmh: Email for Users & Programmers `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:624 +msgid "" +"A GPL-licensed book on :program:`mh` and :program:`nmh`, with some " +"information on the mailbox format." +msgstr "" + +#: ../Doc/library/mailbox.rst:631 +msgid ":class:`Babyl`" +msgstr "" + +#: ../Doc/library/mailbox.rst:636 +msgid "" +"A subclass of :class:`Mailbox` for mailboxes in Babyl format. Parameter " +"*factory* is a callable object that accepts a file-like message " +"representation (which behaves as if opened in binary mode) and returns a " +"custom representation. If *factory* is ``None``, :class:`BabylMessage` is " +"used as the default message representation. If *create* is ``True``, the " +"mailbox is created if it does not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:643 +msgid "" +"Babyl is a single-file mailbox format used by the Rmail mail user agent " +"included with Emacs. The beginning of a message is indicated by a line " +"containing the two characters Control-Underscore (``'\\037'``) and Control-L " +"(``'\\014'``). The end of a message is indicated by the start of the next " +"message or, in the case of the last message, a line containing a Control-" +"Underscore (``'\\037'``) character." +msgstr "" + +#: ../Doc/library/mailbox.rst:650 +msgid "" +"Messages in a Babyl mailbox have two sets of headers, original headers and " +"so-called visible headers. Visible headers are typically a subset of the " +"original headers that have been reformatted or abridged to be more " +"attractive. Each message in a Babyl mailbox also has an accompanying list " +"of :dfn:`labels`, or short strings that record extra information about the " +"message, and a list of all user-defined labels found in the mailbox is kept " +"in the Babyl options section." +msgstr "" + +#: ../Doc/library/mailbox.rst:658 +msgid "" +":class:`Babyl` instances have all of the methods of :class:`Mailbox` in " +"addition to the following:" +msgstr "" + +#: ../Doc/library/mailbox.rst:664 +msgid "" +"Return a list of the names of all user-defined labels used in the mailbox." +msgstr "" + +#: ../Doc/library/mailbox.rst:668 +msgid "" +"The actual messages are inspected to determine which labels exist in the " +"mailbox rather than consulting the list of labels in the Babyl options " +"section, but the Babyl section is updated whenever the mailbox is modified." +msgstr "" + +#: ../Doc/library/mailbox.rst:673 +msgid "" +"Some :class:`Mailbox` methods implemented by :class:`Babyl` deserve special " +"remarks:" +msgstr "" + +#: ../Doc/library/mailbox.rst:679 +msgid "" +"In Babyl mailboxes, the headers of a message are not stored contiguously " +"with the body of the message. To generate a file-like representation, the " +"headers and body are copied together into an :class:`io.BytesIO` instance, " +"which has an API identical to that of a file. As a result, the file-like " +"object is truly independent of the underlying mailbox but does not save " +"memory compared to a string representation." +msgstr "" + +#: ../Doc/library/mailbox.rst:698 +msgid "" +"`Format of Version 5 Babyl Files `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:698 +msgid "A specification of the Babyl format." +msgstr "" + +#: ../Doc/library/mailbox.rst:700 +msgid "" +"`Reading Mail with Rmail `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:701 +msgid "The Rmail manual, with some information on Babyl semantics." +msgstr "" + +#: ../Doc/library/mailbox.rst:707 +msgid ":class:`MMDF`" +msgstr "" + +#: ../Doc/library/mailbox.rst:712 +msgid "" +"A subclass of :class:`Mailbox` for mailboxes in MMDF format. Parameter " +"*factory* is a callable object that accepts a file-like message " +"representation (which behaves as if opened in binary mode) and returns a " +"custom representation. If *factory* is ``None``, :class:`MMDFMessage` is " +"used as the default message representation. If *create* is ``True``, the " +"mailbox is created if it does not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:719 +msgid "" +"MMDF is a single-file mailbox format invented for the Multichannel " +"Memorandum Distribution Facility, a mail transfer agent. Each message is in " +"the same form as an mbox message but is bracketed before and after by lines " +"containing four Control-A (``'\\001'``) characters. As with the mbox format, " +"the beginning of each message is indicated by a line whose first five " +"characters are \"From \", but additional occurrences of \"From \" are not " +"transformed to \">From \" when storing messages because the extra message " +"separator lines prevent mistaking such occurrences for the starts of " +"subsequent messages." +msgstr "" + +#: ../Doc/library/mailbox.rst:728 +msgid "" +"Some :class:`Mailbox` methods implemented by :class:`MMDF` deserve special " +"remarks:" +msgstr "" + +#: ../Doc/library/mailbox.rst:734 +msgid "" +"Using the file after calling :meth:`flush` or :meth:`close` on the :class:" +"`MMDF` instance may yield unpredictable results or raise an exception." +msgstr "" + +#: ../Doc/library/mailbox.rst:749 +msgid "" +"`mmdf man page from tin `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:749 +msgid "" +"A specification of MMDF format from the documentation of tin, a newsreader." +msgstr "" + +#: ../Doc/library/mailbox.rst:752 +msgid "`MMDF `_" +msgstr "" + +#: ../Doc/library/mailbox.rst:752 +msgid "" +"A Wikipedia article describing the Multichannel Memorandum Distribution " +"Facility." +msgstr "" + +#: ../Doc/library/mailbox.rst:759 +msgid ":class:`Message` objects" +msgstr "" + +#: ../Doc/library/mailbox.rst:764 +msgid "" +"A subclass of the :mod:`email.message` module's :class:`~email.message." +"Message`. Subclasses of :class:`mailbox.Message` add mailbox-format-specific " +"state and behavior." +msgstr "" + +#: ../Doc/library/mailbox.rst:768 +msgid "" +"If *message* is omitted, the new instance is created in a default, empty " +"state. If *message* is an :class:`email.message.Message` instance, its " +"contents are copied; furthermore, any format-specific information is " +"converted insofar as possible if *message* is a :class:`Message` instance. " +"If *message* is a string, a byte string, or a file, it should contain an :" +"rfc:`2822`\\ -compliant message, which is read and parsed. Files should be " +"open in binary mode, but text mode files are accepted for backward " +"compatibility." +msgstr "" + +#: ../Doc/library/mailbox.rst:777 +msgid "" +"The format-specific state and behaviors offered by subclasses vary, but in " +"general it is only the properties that are not specific to a particular " +"mailbox that are supported (although presumably the properties are specific " +"to a particular mailbox format). For example, file offsets for single-file " +"mailbox formats and file names for directory-based mailbox formats are not " +"retained, because they are only applicable to the original mailbox. But " +"state such as whether a message has been read by the user or marked as " +"important is retained, because it applies to the message itself." +msgstr "" + +#: ../Doc/library/mailbox.rst:786 +msgid "" +"There is no requirement that :class:`Message` instances be used to represent " +"messages retrieved using :class:`Mailbox` instances. In some situations, the " +"time and memory required to generate :class:`Message` representations might " +"not be acceptable. For such situations, :class:`Mailbox` instances also " +"offer string and file-like representations, and a custom message factory may " +"be specified when a :class:`Mailbox` instance is initialized." +msgstr "" + +#: ../Doc/library/mailbox.rst:797 +msgid ":class:`MaildirMessage`" +msgstr "" + +#: ../Doc/library/mailbox.rst:802 +msgid "" +"A message with Maildir-specific behaviors. Parameter *message* has the same " +"meaning as with the :class:`Message` constructor." +msgstr "" + +#: ../Doc/library/mailbox.rst:805 +msgid "" +"Typically, a mail user agent application moves all of the messages in the :" +"file:`new` subdirectory to the :file:`cur` subdirectory after the first time " +"the user opens and closes the mailbox, recording that the messages are old " +"whether or not they've actually been read. Each message in :file:`cur` has " +"an \"info\" section added to its file name to store information about its " +"state. (Some mail readers may also add an \"info\" section to messages in :" +"file:`new`.) The \"info\" section may take one of two forms: it may contain " +"\"2,\" followed by a list of standardized flags (e.g., \"2,FR\") or it may " +"contain \"1,\" followed by so-called experimental information. Standard " +"flags for Maildir messages are as follows:" +msgstr "" + +#: ../Doc/library/mailbox.rst:819 ../Doc/library/mailbox.rst:990 +#: ../Doc/library/mailbox.rst:1360 +msgid "D" +msgstr "" + +#: ../Doc/library/mailbox.rst:819 +msgid "Draft" +msgstr "" + +#: ../Doc/library/mailbox.rst:819 +msgid "Under composition" +msgstr "" + +#: ../Doc/library/mailbox.rst:821 ../Doc/library/mailbox.rst:992 +#: ../Doc/library/mailbox.rst:1362 +msgid "F" +msgstr "" + +#: ../Doc/library/mailbox.rst:821 ../Doc/library/mailbox.rst:992 +#: ../Doc/library/mailbox.rst:1362 +msgid "Flagged" +msgstr "" + +#: ../Doc/library/mailbox.rst:821 ../Doc/library/mailbox.rst:992 +#: ../Doc/library/mailbox.rst:1140 ../Doc/library/mailbox.rst:1362 +msgid "Marked as important" +msgstr "" + +#: ../Doc/library/mailbox.rst:823 +msgid "P" +msgstr "" + +#: ../Doc/library/mailbox.rst:823 +msgid "Passed" +msgstr "" + +#: ../Doc/library/mailbox.rst:823 +msgid "Forwarded, resent, or bounced" +msgstr "" + +#: ../Doc/library/mailbox.rst:825 ../Doc/library/mailbox.rst:986 +#: ../Doc/library/mailbox.rst:1356 +msgid "R" +msgstr "" + +#: ../Doc/library/mailbox.rst:825 +msgid "Replied" +msgstr "" + +#: ../Doc/library/mailbox.rst:825 ../Doc/library/mailbox.rst:994 +#: ../Doc/library/mailbox.rst:1138 ../Doc/library/mailbox.rst:1229 +#: ../Doc/library/mailbox.rst:1364 +msgid "Replied to" +msgstr "" + +#: ../Doc/library/mailbox.rst:827 +msgid "S" +msgstr "" + +#: ../Doc/library/mailbox.rst:827 +msgid "Seen" +msgstr "" + +#: ../Doc/library/mailbox.rst:827 ../Doc/library/mailbox.rst:986 +#: ../Doc/library/mailbox.rst:1356 +msgid "Read" +msgstr "" + +#: ../Doc/library/mailbox.rst:829 +msgid "T" +msgstr "" + +#: ../Doc/library/mailbox.rst:829 +msgid "Trashed" +msgstr "" + +#: ../Doc/library/mailbox.rst:829 ../Doc/library/mailbox.rst:990 +#: ../Doc/library/mailbox.rst:1225 ../Doc/library/mailbox.rst:1360 +msgid "Marked for subsequent deletion" +msgstr "" + +#: ../Doc/library/mailbox.rst:832 +msgid ":class:`MaildirMessage` instances offer the following methods:" +msgstr "" + +#: ../Doc/library/mailbox.rst:837 +msgid "" +"Return either \"new\" (if the message should be stored in the :file:`new` " +"subdirectory) or \"cur\" (if the message should be stored in the :file:`cur` " +"subdirectory)." +msgstr "" + +#: ../Doc/library/mailbox.rst:843 +msgid "" +"A message is typically moved from :file:`new` to :file:`cur` after its " +"mailbox has been accessed, whether or not the message is has been read. A " +"message ``msg`` has been read if ``\"S\" in msg.get_flags()`` is ``True``." +msgstr "" + +#: ../Doc/library/mailbox.rst:851 +msgid "" +"Set the subdirectory the message should be stored in. Parameter *subdir* " +"must be either \"new\" or \"cur\"." +msgstr "" + +#: ../Doc/library/mailbox.rst:857 +msgid "" +"Return a string specifying the flags that are currently set. If the message " +"complies with the standard Maildir format, the result is the concatenation " +"in alphabetical order of zero or one occurrence of each of ``'D'``, ``'F'``, " +"``'P'``, ``'R'``, ``'S'``, and ``'T'``. The empty string is returned if no " +"flags are set or if \"info\" contains experimental semantics." +msgstr "" + +#: ../Doc/library/mailbox.rst:867 +msgid "Set the flags specified by *flags* and unset all others." +msgstr "" + +#: ../Doc/library/mailbox.rst:872 +msgid "" +"Set the flag(s) specified by *flag* without changing other flags. To add " +"more than one flag at a time, *flag* may be a string of more than one " +"character. The current \"info\" is overwritten whether or not it contains " +"experimental information rather than flags." +msgstr "" + +#: ../Doc/library/mailbox.rst:880 +msgid "" +"Unset the flag(s) specified by *flag* without changing other flags. To " +"remove more than one flag at a time, *flag* maybe a string of more than one " +"character. If \"info\" contains experimental information rather than flags, " +"the current \"info\" is not modified." +msgstr "" + +#: ../Doc/library/mailbox.rst:888 +msgid "" +"Return the delivery date of the message as a floating-point number " +"representing seconds since the epoch." +msgstr "" + +#: ../Doc/library/mailbox.rst:894 +msgid "" +"Set the delivery date of the message to *date*, a floating-point number " +"representing seconds since the epoch." +msgstr "" + +#: ../Doc/library/mailbox.rst:900 +msgid "" +"Return a string containing the \"info\" for a message. This is useful for " +"accessing and modifying \"info\" that is experimental (i.e., not a list of " +"flags)." +msgstr "" + +#: ../Doc/library/mailbox.rst:907 +msgid "Set \"info\" to *info*, which should be a string." +msgstr "" + +#: ../Doc/library/mailbox.rst:909 +msgid "" +"When a :class:`MaildirMessage` instance is created based upon an :class:" +"`mboxMessage` or :class:`MMDFMessage` instance, the :mailheader:`Status` " +"and :mailheader:`X-Status` headers are omitted and the following conversions " +"take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:915 ../Doc/library/mailbox.rst:933 +#: ../Doc/library/mailbox.rst:948 ../Doc/library/mailbox.rst:1055 +#: ../Doc/library/mailbox.rst:1072 ../Doc/library/mailbox.rst:1087 +#: ../Doc/library/mailbox.rst:1102 ../Doc/library/mailbox.rst:1169 +#: ../Doc/library/mailbox.rst:1184 ../Doc/library/mailbox.rst:1198 +#: ../Doc/library/mailbox.rst:1295 ../Doc/library/mailbox.rst:1312 +#: ../Doc/library/mailbox.rst:1326 ../Doc/library/mailbox.rst:1426 +#: ../Doc/library/mailbox.rst:1443 ../Doc/library/mailbox.rst:1458 +#: ../Doc/library/mailbox.rst:1474 +msgid "Resulting state" +msgstr "" + +#: ../Doc/library/mailbox.rst:915 ../Doc/library/mailbox.rst:1184 +#: ../Doc/library/mailbox.rst:1312 +msgid ":class:`mboxMessage` or :class:`MMDFMessage` state" +msgstr "" + +#: ../Doc/library/mailbox.rst:918 ../Doc/library/mailbox.rst:935 +#: ../Doc/library/mailbox.rst:950 ../Doc/library/mailbox.rst:1059 +#: ../Doc/library/mailbox.rst:1430 +msgid "\"cur\" subdirectory" +msgstr "" + +#: ../Doc/library/mailbox.rst:918 ../Doc/library/mailbox.rst:1059 +#: ../Doc/library/mailbox.rst:1076 ../Doc/library/mailbox.rst:1091 +#: ../Doc/library/mailbox.rst:1106 ../Doc/library/mailbox.rst:1430 +#: ../Doc/library/mailbox.rst:1447 ../Doc/library/mailbox.rst:1462 +#: ../Doc/library/mailbox.rst:1478 +msgid "O flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:920 ../Doc/library/mailbox.rst:939 +#: ../Doc/library/mailbox.rst:1063 ../Doc/library/mailbox.rst:1078 +#: ../Doc/library/mailbox.rst:1110 ../Doc/library/mailbox.rst:1175 +#: ../Doc/library/mailbox.rst:1191 ../Doc/library/mailbox.rst:1434 +#: ../Doc/library/mailbox.rst:1449 ../Doc/library/mailbox.rst:1482 +msgid "F flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:922 ../Doc/library/mailbox.rst:924 +#: ../Doc/library/mailbox.rst:941 ../Doc/library/mailbox.rst:956 +#: ../Doc/library/mailbox.rst:1057 ../Doc/library/mailbox.rst:1065 +#: ../Doc/library/mailbox.rst:1104 ../Doc/library/mailbox.rst:1173 +#: ../Doc/library/mailbox.rst:1301 ../Doc/library/mailbox.rst:1428 +#: ../Doc/library/mailbox.rst:1436 ../Doc/library/mailbox.rst:1476 +msgid "R flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:922 ../Doc/library/mailbox.rst:1065 +#: ../Doc/library/mailbox.rst:1080 ../Doc/library/mailbox.rst:1095 +#: ../Doc/library/mailbox.rst:1112 ../Doc/library/mailbox.rst:1189 +#: ../Doc/library/mailbox.rst:1319 ../Doc/library/mailbox.rst:1436 +#: ../Doc/library/mailbox.rst:1451 ../Doc/library/mailbox.rst:1466 +#: ../Doc/library/mailbox.rst:1484 +msgid "A flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:924 ../Doc/library/mailbox.rst:1057 +#: ../Doc/library/mailbox.rst:1428 +msgid "S flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:926 ../Doc/library/mailbox.rst:958 +#: ../Doc/library/mailbox.rst:1061 ../Doc/library/mailbox.rst:1299 +#: ../Doc/library/mailbox.rst:1432 +msgid "T flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:926 ../Doc/library/mailbox.rst:1061 +#: ../Doc/library/mailbox.rst:1093 ../Doc/library/mailbox.rst:1108 +#: ../Doc/library/mailbox.rst:1317 ../Doc/library/mailbox.rst:1432 +#: ../Doc/library/mailbox.rst:1464 ../Doc/library/mailbox.rst:1480 +msgid "D flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:929 +msgid "" +"When a :class:`MaildirMessage` instance is created based upon an :class:" +"`MHMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:933 ../Doc/library/mailbox.rst:1072 +#: ../Doc/library/mailbox.rst:1326 ../Doc/library/mailbox.rst:1443 +msgid ":class:`MHMessage` state" +msgstr "" + +#: ../Doc/library/mailbox.rst:935 ../Doc/library/mailbox.rst:1076 +#: ../Doc/library/mailbox.rst:1171 ../Doc/library/mailbox.rst:1187 +#: ../Doc/library/mailbox.rst:1200 ../Doc/library/mailbox.rst:1328 +#: ../Doc/library/mailbox.rst:1447 +msgid "\"unseen\" sequence" +msgstr "" + +#: ../Doc/library/mailbox.rst:937 ../Doc/library/mailbox.rst:952 +msgid "\"cur\" subdirectory and S flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:937 ../Doc/library/mailbox.rst:1074 +#: ../Doc/library/mailbox.rst:1445 +msgid "no \"unseen\" sequence" +msgstr "" + +#: ../Doc/library/mailbox.rst:939 ../Doc/library/mailbox.rst:1078 +#: ../Doc/library/mailbox.rst:1175 ../Doc/library/mailbox.rst:1191 +#: ../Doc/library/mailbox.rst:1449 +msgid "\"flagged\" sequence" +msgstr "" + +#: ../Doc/library/mailbox.rst:941 ../Doc/library/mailbox.rst:1080 +#: ../Doc/library/mailbox.rst:1173 ../Doc/library/mailbox.rst:1189 +#: ../Doc/library/mailbox.rst:1202 ../Doc/library/mailbox.rst:1330 +#: ../Doc/library/mailbox.rst:1451 +msgid "\"replied\" sequence" +msgstr "" + +#: ../Doc/library/mailbox.rst:944 +msgid "" +"When a :class:`MaildirMessage` instance is created based upon a :class:" +"`BabylMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:948 ../Doc/library/mailbox.rst:1087 +#: ../Doc/library/mailbox.rst:1198 ../Doc/library/mailbox.rst:1458 +msgid ":class:`BabylMessage` state" +msgstr "" + +#: ../Doc/library/mailbox.rst:950 ../Doc/library/mailbox.rst:1091 +#: ../Doc/library/mailbox.rst:1200 ../Doc/library/mailbox.rst:1297 +#: ../Doc/library/mailbox.rst:1315 ../Doc/library/mailbox.rst:1328 +#: ../Doc/library/mailbox.rst:1462 +msgid "\"unseen\" label" +msgstr "" + +#: ../Doc/library/mailbox.rst:952 ../Doc/library/mailbox.rst:1089 +#: ../Doc/library/mailbox.rst:1460 +msgid "no \"unseen\" label" +msgstr "" + +#: ../Doc/library/mailbox.rst:954 ../Doc/library/mailbox.rst:1303 +msgid "P flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:954 +msgid "\"forwarded\" or \"resent\" label" +msgstr "" + +#: ../Doc/library/mailbox.rst:956 ../Doc/library/mailbox.rst:1095 +#: ../Doc/library/mailbox.rst:1202 ../Doc/library/mailbox.rst:1301 +#: ../Doc/library/mailbox.rst:1319 ../Doc/library/mailbox.rst:1330 +#: ../Doc/library/mailbox.rst:1466 +msgid "\"answered\" label" +msgstr "" + +#: ../Doc/library/mailbox.rst:958 ../Doc/library/mailbox.rst:1093 +#: ../Doc/library/mailbox.rst:1299 ../Doc/library/mailbox.rst:1317 +#: ../Doc/library/mailbox.rst:1464 +msgid "\"deleted\" label" +msgstr "" + +#: ../Doc/library/mailbox.rst:965 +msgid ":class:`mboxMessage`" +msgstr "" + +#: ../Doc/library/mailbox.rst:970 +msgid "" +"A message with mbox-specific behaviors. Parameter *message* has the same " +"meaning as with the :class:`Message` constructor." +msgstr "" + +#: ../Doc/library/mailbox.rst:973 +msgid "" +"Messages in an mbox mailbox are stored together in a single file. The " +"sender's envelope address and the time of delivery are typically stored in a " +"line beginning with \"From \" that is used to indicate the start of a " +"message, though there is considerable variation in the exact format of this " +"data among mbox implementations. Flags that indicate the state of the " +"message, such as whether it has been read or marked as important, are " +"typically stored in :mailheader:`Status` and :mailheader:`X-Status` headers." +msgstr "" + +#: ../Doc/library/mailbox.rst:981 +msgid "Conventional flags for mbox messages are as follows:" +msgstr "" + +#: ../Doc/library/mailbox.rst:988 ../Doc/library/mailbox.rst:1358 +msgid "O" +msgstr "" + +#: ../Doc/library/mailbox.rst:988 ../Doc/library/mailbox.rst:1358 +msgid "Old" +msgstr "" + +#: ../Doc/library/mailbox.rst:988 ../Doc/library/mailbox.rst:1358 +msgid "Previously detected by MUA" +msgstr "" + +#: ../Doc/library/mailbox.rst:990 ../Doc/library/mailbox.rst:1360 +msgid "Deleted" +msgstr "" + +#: ../Doc/library/mailbox.rst:994 ../Doc/library/mailbox.rst:1364 +msgid "A" +msgstr "" + +#: ../Doc/library/mailbox.rst:994 ../Doc/library/mailbox.rst:1364 +msgid "Answered" +msgstr "" + +#: ../Doc/library/mailbox.rst:997 ../Doc/library/mailbox.rst:1367 +msgid "" +"The \"R\" and \"O\" flags are stored in the :mailheader:`Status` header, and " +"the \"D\", \"F\", and \"A\" flags are stored in the :mailheader:`X-Status` " +"header. The flags and headers typically appear in the order mentioned." +msgstr "" + +#: ../Doc/library/mailbox.rst:1001 +msgid ":class:`mboxMessage` instances offer the following methods:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1006 ../Doc/library/mailbox.rst:1377 +msgid "" +"Return a string representing the \"From \" line that marks the start of the " +"message in an mbox mailbox. The leading \"From \" and the trailing newline " +"are excluded." +msgstr "" + +#: ../Doc/library/mailbox.rst:1013 ../Doc/library/mailbox.rst:1384 +msgid "" +"Set the \"From \" line to *from_*, which should be specified without a " +"leading \"From \" or trailing newline. For convenience, *time_* may be " +"specified and will be formatted appropriately and appended to *from_*. If " +"*time_* is specified, it should be a :class:`time.struct_time` instance, a " +"tuple suitable for passing to :meth:`time.strftime`, or ``True`` (to use :" +"meth:`time.gmtime`)." +msgstr "" + +#: ../Doc/library/mailbox.rst:1023 ../Doc/library/mailbox.rst:1394 +msgid "" +"Return a string specifying the flags that are currently set. If the message " +"complies with the conventional format, the result is the concatenation in " +"the following order of zero or one occurrence of each of ``'R'``, ``'O'``, " +"``'D'``, ``'F'``, and ``'A'``." +msgstr "" + +#: ../Doc/library/mailbox.rst:1031 ../Doc/library/mailbox.rst:1402 +msgid "" +"Set the flags specified by *flags* and unset all others. Parameter *flags* " +"should be the concatenation in any order of zero or more occurrences of each " +"of ``'R'``, ``'O'``, ``'D'``, ``'F'``, and ``'A'``." +msgstr "" + +#: ../Doc/library/mailbox.rst:1038 ../Doc/library/mailbox.rst:1409 +msgid "" +"Set the flag(s) specified by *flag* without changing other flags. To add " +"more than one flag at a time, *flag* may be a string of more than one " +"character." +msgstr "" + +#: ../Doc/library/mailbox.rst:1045 ../Doc/library/mailbox.rst:1416 +msgid "" +"Unset the flag(s) specified by *flag* without changing other flags. To " +"remove more than one flag at a time, *flag* maybe a string of more than one " +"character." +msgstr "" + +#: ../Doc/library/mailbox.rst:1049 +msgid "" +"When an :class:`mboxMessage` instance is created based upon a :class:" +"`MaildirMessage` instance, a \"From \" line is generated based upon the :" +"class:`MaildirMessage` instance's delivery date, and the following " +"conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1055 ../Doc/library/mailbox.rst:1169 +#: ../Doc/library/mailbox.rst:1295 ../Doc/library/mailbox.rst:1426 +msgid ":class:`MaildirMessage` state" +msgstr "" + +#: ../Doc/library/mailbox.rst:1068 +msgid "" +"When an :class:`mboxMessage` instance is created based upon an :class:" +"`MHMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1074 ../Doc/library/mailbox.rst:1089 +#: ../Doc/library/mailbox.rst:1445 ../Doc/library/mailbox.rst:1460 +msgid "R flag and O flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:1083 +msgid "" +"When an :class:`mboxMessage` instance is created based upon a :class:" +"`BabylMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1098 +msgid "" +"When a :class:`Message` instance is created based upon an :class:" +"`MMDFMessage` instance, the \"From \" line is copied and all flags directly " +"correspond:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1102 +msgid ":class:`MMDFMessage` state" +msgstr "" + +#: ../Doc/library/mailbox.rst:1119 +msgid ":class:`MHMessage`" +msgstr "" + +#: ../Doc/library/mailbox.rst:1124 +msgid "" +"A message with MH-specific behaviors. Parameter *message* has the same " +"meaning as with the :class:`Message` constructor." +msgstr "" + +#: ../Doc/library/mailbox.rst:1127 +msgid "" +"MH messages do not support marks or flags in the traditional sense, but they " +"do support sequences, which are logical groupings of arbitrary messages. " +"Some mail reading programs (although not the standard :program:`mh` and :" +"program:`nmh`) use sequences in much the same way flags are used with other " +"formats, as follows:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1134 +msgid "Sequence" +msgstr "" + +#: ../Doc/library/mailbox.rst:1136 ../Doc/library/mailbox.rst:1223 +msgid "unseen" +msgstr "" + +#: ../Doc/library/mailbox.rst:1136 ../Doc/library/mailbox.rst:1223 +msgid "Not read, but previously detected by MUA" +msgstr "" + +#: ../Doc/library/mailbox.rst:1138 +msgid "replied" +msgstr "" + +#: ../Doc/library/mailbox.rst:1140 +msgid "flagged" +msgstr "" + +#: ../Doc/library/mailbox.rst:1143 +msgid ":class:`MHMessage` instances offer the following methods:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1148 +msgid "Return a list of the names of sequences that include this message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1153 +msgid "Set the list of sequences that include this message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1158 +msgid "Add *sequence* to the list of sequences that include this message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1163 +msgid "Remove *sequence* from the list of sequences that include this message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1165 +msgid "" +"When an :class:`MHMessage` instance is created based upon a :class:" +"`MaildirMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1171 ../Doc/library/mailbox.rst:1297 +msgid "no S flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:1178 +msgid "" +"When an :class:`MHMessage` instance is created based upon an :class:" +"`mboxMessage` or :class:`MMDFMessage` instance, the :mailheader:`Status` " +"and :mailheader:`X-Status` headers are omitted and the following conversions " +"take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1187 ../Doc/library/mailbox.rst:1315 +msgid "no R flag" +msgstr "" + +#: ../Doc/library/mailbox.rst:1194 +msgid "" +"When an :class:`MHMessage` instance is created based upon a :class:" +"`BabylMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1209 +msgid ":class:`BabylMessage`" +msgstr "" + +#: ../Doc/library/mailbox.rst:1214 +msgid "" +"A message with Babyl-specific behaviors. Parameter *message* has the same " +"meaning as with the :class:`Message` constructor." +msgstr "" + +#: ../Doc/library/mailbox.rst:1217 +msgid "" +"Certain message labels, called :dfn:`attributes`, are defined by convention " +"to have special meanings. The attributes are as follows:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1221 +msgid "Label" +msgstr "" + +#: ../Doc/library/mailbox.rst:1225 +msgid "deleted" +msgstr "" + +#: ../Doc/library/mailbox.rst:1227 +msgid "filed" +msgstr "" + +#: ../Doc/library/mailbox.rst:1227 +msgid "Copied to another file or mailbox" +msgstr "" + +#: ../Doc/library/mailbox.rst:1229 +msgid "answered" +msgstr "" + +#: ../Doc/library/mailbox.rst:1231 +msgid "forwarded" +msgstr "" + +#: ../Doc/library/mailbox.rst:1231 +msgid "Forwarded" +msgstr "" + +#: ../Doc/library/mailbox.rst:1233 +msgid "edited" +msgstr "" + +#: ../Doc/library/mailbox.rst:1233 +msgid "Modified by the user" +msgstr "" + +#: ../Doc/library/mailbox.rst:1235 +msgid "resent" +msgstr "" + +#: ../Doc/library/mailbox.rst:1235 +msgid "Resent" +msgstr "" + +#: ../Doc/library/mailbox.rst:1238 +msgid "" +"By default, Rmail displays only visible headers. The :class:`BabylMessage` " +"class, though, uses the original headers because they are more complete. " +"Visible headers may be accessed explicitly if desired." +msgstr "" + +#: ../Doc/library/mailbox.rst:1242 +msgid ":class:`BabylMessage` instances offer the following methods:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1247 +msgid "Return a list of labels on the message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1252 +msgid "Set the list of labels on the message to *labels*." +msgstr "" + +#: ../Doc/library/mailbox.rst:1257 +msgid "Add *label* to the list of labels on the message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1262 +msgid "Remove *label* from the list of labels on the message." +msgstr "" + +#: ../Doc/library/mailbox.rst:1267 +msgid "" +"Return an :class:`Message` instance whose headers are the message's visible " +"headers and whose body is empty." +msgstr "" + +#: ../Doc/library/mailbox.rst:1273 +msgid "" +"Set the message's visible headers to be the same as the headers in " +"*message*. Parameter *visible* should be a :class:`Message` instance, an :" +"class:`email.message.Message` instance, a string, or a file-like object " +"(which should be open in text mode)." +msgstr "" + +#: ../Doc/library/mailbox.rst:1281 +msgid "" +"When a :class:`BabylMessage` instance's original headers are modified, the " +"visible headers are not automatically modified to correspond. This method " +"updates the visible headers as follows: each visible header with a " +"corresponding original header is set to the value of the original header, " +"each visible header without a corresponding original header is removed, and " +"any of :mailheader:`Date`, :mailheader:`From`, :mailheader:`Reply-To`, :" +"mailheader:`To`, :mailheader:`CC`, and :mailheader:`Subject` that are " +"present in the original headers but not the visible headers are added to the " +"visible headers." +msgstr "" + +#: ../Doc/library/mailbox.rst:1291 +msgid "" +"When a :class:`BabylMessage` instance is created based upon a :class:" +"`MaildirMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1303 +msgid "\"forwarded\" label" +msgstr "" + +#: ../Doc/library/mailbox.rst:1306 +msgid "" +"When a :class:`BabylMessage` instance is created based upon an :class:" +"`mboxMessage` or :class:`MMDFMessage` instance, the :mailheader:`Status` " +"and :mailheader:`X-Status` headers are omitted and the following conversions " +"take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1322 +msgid "" +"When a :class:`BabylMessage` instance is created based upon an :class:" +"`MHMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1337 +msgid ":class:`MMDFMessage`" +msgstr "" + +#: ../Doc/library/mailbox.rst:1342 +msgid "" +"A message with MMDF-specific behaviors. Parameter *message* has the same " +"meaning as with the :class:`Message` constructor." +msgstr "" + +#: ../Doc/library/mailbox.rst:1345 +msgid "" +"As with message in an mbox mailbox, MMDF messages are stored with the " +"sender's address and the delivery date in an initial line beginning with " +"\"From \". Likewise, flags that indicate the state of the message are " +"typically stored in :mailheader:`Status` and :mailheader:`X-Status` headers." +msgstr "" + +#: ../Doc/library/mailbox.rst:1350 +msgid "" +"Conventional flags for MMDF messages are identical to those of mbox message " +"and are as follows:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1371 +msgid "" +":class:`MMDFMessage` instances offer the following methods, which are " +"identical to those offered by :class:`mboxMessage`:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1420 +msgid "" +"When an :class:`MMDFMessage` instance is created based upon a :class:" +"`MaildirMessage` instance, a \"From \" line is generated based upon the :" +"class:`MaildirMessage` instance's delivery date, and the following " +"conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1439 +msgid "" +"When an :class:`MMDFMessage` instance is created based upon an :class:" +"`MHMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1454 +msgid "" +"When an :class:`MMDFMessage` instance is created based upon a :class:" +"`BabylMessage` instance, the following conversions take place:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1469 +msgid "" +"When an :class:`MMDFMessage` instance is created based upon an :class:" +"`mboxMessage` instance, the \"From \" line is copied and all flags directly " +"correspond:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1474 +msgid ":class:`mboxMessage` state" +msgstr "" + +#: ../Doc/library/mailbox.rst:1491 +msgid "" +"The following exception classes are defined in the :mod:`mailbox` module:" +msgstr "" + +#: ../Doc/library/mailbox.rst:1496 +msgid "The based class for all other module-specific exceptions." +msgstr "" + +#: ../Doc/library/mailbox.rst:1501 +msgid "" +"Raised when a mailbox is expected but is not found, such as when " +"instantiating a :class:`Mailbox` subclass with a path that does not exist " +"(and with the *create* parameter set to ``False``), or when opening a folder " +"that does not exist." +msgstr "" + +#: ../Doc/library/mailbox.rst:1508 +msgid "" +"Raised when a mailbox is not empty but is expected to be, such as when " +"deleting a folder that contains messages." +msgstr "" + +#: ../Doc/library/mailbox.rst:1514 +msgid "" +"Raised when some mailbox-related condition beyond the control of the program " +"causes it to be unable to proceed, such as when failing to acquire a lock " +"that another program already holds a lock, or when a uniquely-generated file " +"name already exists." +msgstr "" + +#: ../Doc/library/mailbox.rst:1522 +msgid "" +"Raised when the data in a file cannot be parsed, such as when an :class:`MH` " +"instance attempts to read a corrupted :file:`.mh_sequences` file." +msgstr "" + +#: ../Doc/library/mailbox.rst:1531 +msgid "" +"A simple example of printing the subjects of all messages in a mailbox that " +"seem interesting::" +msgstr "" + +#: ../Doc/library/mailbox.rst:1540 +msgid "" +"To copy all mail from a Babyl mailbox to an MH mailbox, converting all of " +"the format-specific information that can be converted::" +msgstr "" + +#: ../Doc/library/mailbox.rst:1551 +msgid "" +"This example sorts mail from several mailing lists into different mailboxes, " +"being careful to avoid mail corruption due to concurrent modification by " +"other programs, mail loss due to interruption of the program, or premature " +"termination due to malformed messages in the mailbox::" +msgstr "" + +#: ../Doc/library/mailcap.rst:2 +msgid ":mod:`mailcap` --- Mailcap file handling" +msgstr "" + +#: ../Doc/library/mailcap.rst:7 +msgid "**Source code:** :source:`Lib/mailcap.py`" +msgstr "" + +#: ../Doc/library/mailcap.rst:11 +msgid "" +"Mailcap files are used to configure how MIME-aware applications such as mail " +"readers and Web browsers react to files with different MIME types. (The name " +"\"mailcap\" is derived from the phrase \"mail capability\".) For example, a " +"mailcap file might contain a line like ``video/mpeg; xmpeg %s``. Then, if " +"the user encounters an email message or Web document with the MIME type :" +"mimetype:`video/mpeg`, ``%s`` will be replaced by a filename (usually one " +"belonging to a temporary file) and the :program:`xmpeg` program can be " +"automatically started to view the file." +msgstr "" + +#: ../Doc/library/mailcap.rst:20 +msgid "" +"The mailcap format is documented in :rfc:`1524`, \"A User Agent " +"Configuration Mechanism For Multimedia Mail Format Information,\" but is not " +"an Internet standard. However, mailcap files are supported on most Unix " +"systems." +msgstr "" + +#: ../Doc/library/mailcap.rst:27 +msgid "" +"Return a 2-tuple; the first element is a string containing the command line " +"to be executed (which can be passed to :func:`os.system`), and the second " +"element is the mailcap entry for a given MIME type. If no matching MIME " +"type can be found, ``(None, None)`` is returned." +msgstr "" + +#: ../Doc/library/mailcap.rst:32 +msgid "" +"*key* is the name of the field desired, which represents the type of " +"activity to be performed; the default value is 'view', since in the most " +"common case you simply want to view the body of the MIME-typed data. Other " +"possible values might be 'compose' and 'edit', if you wanted to create a new " +"body of the given MIME type or alter the existing body data. See :rfc:" +"`1524` for a complete list of these fields." +msgstr "" + +#: ../Doc/library/mailcap.rst:39 +msgid "" +"*filename* is the filename to be substituted for ``%s`` in the command line; " +"the default value is ``'/dev/null'`` which is almost certainly not what you " +"want, so usually you'll override it by specifying a filename." +msgstr "" + +#: ../Doc/library/mailcap.rst:43 +msgid "" +"*plist* can be a list containing named parameters; the default value is " +"simply an empty list. Each entry in the list must be a string containing " +"the parameter name, an equals sign (``'='``), and the parameter's value. " +"Mailcap entries can contain named parameters like ``%{foo}``, which will be " +"replaced by the value of the parameter named 'foo'. For example, if the " +"command line ``showpartial %{id} %{number} %{total}`` was in a mailcap file, " +"and *plist* was set to ``['id=1', 'number=2', 'total=3']``, the resulting " +"command line would be ``'showpartial 1 2 3'``." +msgstr "" + +#: ../Doc/library/mailcap.rst:52 +msgid "" +"In a mailcap file, the \"test\" field can optionally be specified to test " +"some external condition (such as the machine architecture, or the window " +"system in use) to determine whether or not the mailcap line applies. :func:" +"`findmatch` will automatically check such conditions and skip the entry if " +"the check fails." +msgstr "" + +#: ../Doc/library/mailcap.rst:60 +msgid "" +"Returns a dictionary mapping MIME types to a list of mailcap file entries. " +"This dictionary must be passed to the :func:`findmatch` function. An entry " +"is stored as a list of dictionaries, but it shouldn't be necessary to know " +"the details of this representation." +msgstr "" + +#: ../Doc/library/mailcap.rst:65 +msgid "" +"The information is derived from all of the mailcap files found on the " +"system. Settings in the user's mailcap file :file:`$HOME/.mailcap` will " +"override settings in the system mailcap files :file:`/etc/mailcap`, :file:`/" +"usr/etc/mailcap`, and :file:`/usr/local/etc/mailcap`." +msgstr "" + +#: ../Doc/library/mailcap.rst:70 +msgid "An example usage::" +msgstr "" + +#: ../Doc/library/markup.rst:5 +msgid "Structured Markup Processing Tools" +msgstr "" + +#: ../Doc/library/markup.rst:7 +msgid "" +"Python supports a variety of modules to work with various forms of " +"structured data markup. This includes modules to work with the Standard " +"Generalized Markup Language (SGML) and the Hypertext Markup Language (HTML), " +"and several interfaces for working with the Extensible Markup Language (XML)." +msgstr "" + +#: ../Doc/library/marshal.rst:2 +msgid ":mod:`marshal` --- Internal Python object serialization" +msgstr "" + +#: ../Doc/library/marshal.rst:10 +msgid "" +"This module contains functions that can read and write Python values in a " +"binary format. The format is specific to Python, but independent of machine " +"architecture issues (e.g., you can write a Python value to a file on a PC, " +"transport the file to a Sun, and read it back there). Details of the format " +"are undocumented on purpose; it may change between Python versions (although " +"it rarely does). [#]_" +msgstr "" + +#: ../Doc/library/marshal.rst:21 +msgid "" +"This is not a general \"persistence\" module. For general persistence and " +"transfer of Python objects through RPC calls, see the modules :mod:`pickle` " +"and :mod:`shelve`. The :mod:`marshal` module exists mainly to support " +"reading and writing the \"pseudo-compiled\" code for Python modules of :file:" +"`.pyc` files. Therefore, the Python maintainers reserve the right to modify " +"the marshal format in backward incompatible ways should the need arise. If " +"you're serializing and de-serializing Python objects, use the :mod:`pickle` " +"module instead -- the performance is comparable, version independence is " +"guaranteed, and pickle supports a substantially wider range of objects than " +"marshal." +msgstr "" + +#: ../Doc/library/marshal.rst:33 +msgid "" +"The :mod:`marshal` module is not intended to be secure against erroneous or " +"maliciously constructed data. Never unmarshal data received from an " +"untrusted or unauthenticated source." +msgstr "" + +#: ../Doc/library/marshal.rst:39 +msgid "" +"Not all Python object types are supported; in general, only objects whose " +"value is independent from a particular invocation of Python can be written " +"and read by this module. The following types are supported: booleans, " +"integers, floating point numbers, complex numbers, strings, bytes, " +"bytearrays, tuples, lists, sets, frozensets, dictionaries, and code objects, " +"where it should be understood that tuples, lists, sets, frozensets and " +"dictionaries are only supported as long as the values contained therein are " +"themselves supported. The singletons :const:`None`, :const:`Ellipsis` and :" +"exc:`StopIteration` can also be marshalled and unmarshalled. For format " +"*version* lower than 3, recursive lists, sets and dictionaries cannot be " +"written (see below)." +msgstr "" + +#: ../Doc/library/marshal.rst:51 +msgid "" +"There are functions that read/write files as well as functions operating on " +"strings." +msgstr "" + +#: ../Doc/library/marshal.rst:54 +msgid "The module defines these functions:" +msgstr "" + +#: ../Doc/library/marshal.rst:59 +msgid "" +"Write the value on the open file. The value must be a supported type. The " +"file must be an open file object such as ``sys.stdout`` or returned by :func:" +"`open` or :func:`os.popen`. It must be opened in binary mode (``'wb'`` or " +"``'w+b'``)." +msgstr "" + +#: ../Doc/library/marshal.rst:64 +msgid "" +"If the value has (or contains an object that has) an unsupported type, a :" +"exc:`ValueError` exception is raised --- but garbage data will also be " +"written to the file. The object will not be properly read back by :func:" +"`load`." +msgstr "" + +#: ../Doc/library/marshal.rst:68 +msgid "" +"The *version* argument indicates the data format that ``dump`` should use " +"(see below)." +msgstr "" + +#: ../Doc/library/marshal.rst:74 +msgid "" +"Read one value from the open file and return it. If no valid value is read " +"(e.g. because the data has a different Python version's incompatible marshal " +"format), raise :exc:`EOFError`, :exc:`ValueError` or :exc:`TypeError`. The " +"file must be an open file object opened in binary mode (``'rb'`` or ``'r" +"+b'``)." +msgstr "" + +#: ../Doc/library/marshal.rst:82 +msgid "" +"If an object containing an unsupported type was marshalled with :func:" +"`dump`, :func:`load` will substitute ``None`` for the unmarshallable type." +msgstr "" + +#: ../Doc/library/marshal.rst:88 +msgid "" +"Return the string that would be written to a file by ``dump(value, file)``. " +"The value must be a supported type. Raise a :exc:`ValueError` exception if " +"value has (or contains an object that has) an unsupported type." +msgstr "" + +#: ../Doc/library/marshal.rst:92 +msgid "" +"The *version* argument indicates the data format that ``dumps`` should use " +"(see below)." +msgstr "" + +#: ../Doc/library/marshal.rst:98 +msgid "" +"Convert the string to a value. If no valid value is found, raise :exc:" +"`EOFError`, :exc:`ValueError` or :exc:`TypeError`. Extra characters in the " +"string are ignored." +msgstr "" + +#: ../Doc/library/marshal.rst:103 +msgid "In addition, the following constants are defined:" +msgstr "" + +#: ../Doc/library/marshal.rst:107 +msgid "" +"Indicates the format that the module uses. Version 0 is the historical " +"format, version 1 shares interned strings and version 2 uses a binary format " +"for floating point numbers. Version 3 adds support for object instancing and " +"recursion. The current version is 4." +msgstr "" + +#: ../Doc/library/marshal.rst:116 +msgid "" +"The name of this module stems from a bit of terminology used by the " +"designers of Modula-3 (amongst others), who use the term \"marshalling\" for " +"shipping of data around in a self-contained form. Strictly speaking, \"to " +"marshal\" means to convert some data from internal to external form (in an " +"RPC buffer for instance) and \"unmarshalling\" for the reverse process." +msgstr "" + +#: ../Doc/library/math.rst:2 +msgid ":mod:`math` --- Mathematical functions" +msgstr "" + +#: ../Doc/library/math.rst:13 +msgid "" +"This module is always available. It provides access to the mathematical " +"functions defined by the C standard." +msgstr "" + +#: ../Doc/library/math.rst:16 +msgid "" +"These functions cannot be used with complex numbers; use the functions of " +"the same name from the :mod:`cmath` module if you require support for " +"complex numbers. The distinction between functions which support complex " +"numbers and those which don't is made since most users do not want to learn " +"quite as much mathematics as required to understand complex numbers. " +"Receiving an exception instead of a complex result allows earlier detection " +"of the unexpected complex number used as a parameter, so that the programmer " +"can determine how and why it was generated in the first place." +msgstr "" + +#: ../Doc/library/math.rst:25 +msgid "" +"The following functions are provided by this module. Except when explicitly " +"noted otherwise, all return values are floats." +msgstr "" + +#: ../Doc/library/math.rst:30 +msgid "Number-theoretic and representation functions" +msgstr "" + +#: ../Doc/library/math.rst:34 +msgid "" +"Return the ceiling of *x*, the smallest integer greater than or equal to " +"*x*. If *x* is not a float, delegates to ``x.__ceil__()``, which should " +"return an :class:`~numbers.Integral` value." +msgstr "" + +#: ../Doc/library/math.rst:41 +msgid "" +"Return a float with the magnitude (absolute value) of *x* but the sign of " +"*y*. On platforms that support signed zeros, ``copysign(1.0, -0.0)`` " +"returns *-1.0*." +msgstr "" + +#: ../Doc/library/math.rst:47 +msgid "Return the absolute value of *x*." +msgstr "" + +#: ../Doc/library/math.rst:51 +msgid "" +"Return *x* factorial. Raises :exc:`ValueError` if *x* is not integral or is " +"negative." +msgstr "" + +#: ../Doc/library/math.rst:56 +msgid "" +"Return the floor of *x*, the largest integer less than or equal to *x*. If " +"*x* is not a float, delegates to ``x.__floor__()``, which should return an :" +"class:`~numbers.Integral` value." +msgstr "" + +#: ../Doc/library/math.rst:63 +msgid "" +"Return ``fmod(x, y)``, as defined by the platform C library. Note that the " +"Python expression ``x % y`` may not return the same result. The intent of " +"the C standard is that ``fmod(x, y)`` be exactly (mathematically; to " +"infinite precision) equal to ``x - n*y`` for some integer *n* such that the " +"result has the same sign as *x* and magnitude less than ``abs(y)``. " +"Python's ``x % y`` returns a result with the sign of *y* instead, and may " +"not be exactly computable for float arguments. For example, ``fmod(-1e-100, " +"1e100)`` is ``-1e-100``, but the result of Python's ``-1e-100 % 1e100`` is " +"``1e100-1e-100``, which cannot be represented exactly as a float, and rounds " +"to the surprising ``1e100``. For this reason, function :func:`fmod` is " +"generally preferred when working with floats, while Python's ``x % y`` is " +"preferred when working with integers." +msgstr "" + +#: ../Doc/library/math.rst:78 +msgid "" +"Return the mantissa and exponent of *x* as the pair ``(m, e)``. *m* is a " +"float and *e* is an integer such that ``x == m * 2**e`` exactly. If *x* is " +"zero, returns ``(0.0, 0)``, otherwise ``0.5 <= abs(m) < 1``. This is used " +"to \"pick apart\" the internal representation of a float in a portable way." +msgstr "" + +#: ../Doc/library/math.rst:86 +msgid "" +"Return an accurate floating point sum of values in the iterable. Avoids " +"loss of precision by tracking multiple intermediate partial sums::" +msgstr "" + +#: ../Doc/library/math.rst:94 +msgid "" +"The algorithm's accuracy depends on IEEE-754 arithmetic guarantees and the " +"typical case where the rounding mode is half-even. On some non-Windows " +"builds, the underlying C library uses extended precision addition and may " +"occasionally double-round an intermediate sum causing it to be off in its " +"least significant bit." +msgstr "" + +#: ../Doc/library/math.rst:100 +msgid "" +"For further discussion and two alternative approaches, see the `ASPN " +"cookbook recipes for accurate floating point summation `_\\." +msgstr "" + +#: ../Doc/library/math.rst:107 +msgid "" +"Return the greatest common divisor of the integers *a* and *b*. If either " +"*a* or *b* is nonzero, then the value of ``gcd(a, b)`` is the largest " +"positive integer that divides both *a* and *b*. ``gcd(0, 0)`` returns ``0``." +msgstr "" + +#: ../Doc/library/math.rst:149 +msgid "" +"Return ``True`` if *x* is neither an infinity nor a NaN, and ``False`` " +"otherwise. (Note that ``0.0`` *is* considered finite.)" +msgstr "" + +#: ../Doc/library/math.rst:157 +msgid "" +"Return ``True`` if *x* is a positive or negative infinity, and ``False`` " +"otherwise." +msgstr "" + +#: ../Doc/library/math.rst:163 +msgid "" +"Return ``True`` if *x* is a NaN (not a number), and ``False`` otherwise." +msgstr "" + +#: ../Doc/library/math.rst:168 +msgid "" +"Return ``x * (2**i)``. This is essentially the inverse of function :func:" +"`frexp`." +msgstr "" + +#: ../Doc/library/math.rst:174 +msgid "" +"Return the fractional and integer parts of *x*. Both results carry the sign " +"of *x* and are floats." +msgstr "" + +#: ../Doc/library/math.rst:180 +msgid "" +"Return the :class:`~numbers.Real` value *x* truncated to an :class:`~numbers." +"Integral` (usually an integer). Delegates to ``x.__trunc__()``." +msgstr "" + +#: ../Doc/library/math.rst:185 +msgid "" +"Note that :func:`frexp` and :func:`modf` have a different call/return " +"pattern than their C equivalents: they take a single argument and return a " +"pair of values, rather than returning their second return value through an " +"'output parameter' (there is no such thing in Python)." +msgstr "" + +#: ../Doc/library/math.rst:190 +msgid "" +"For the :func:`ceil`, :func:`floor`, and :func:`modf` functions, note that " +"*all* floating-point numbers of sufficiently large magnitude are exact " +"integers. Python floats typically carry no more than 53 bits of precision " +"(the same as the platform C double type), in which case any float *x* with " +"``abs(x) >= 2**52`` necessarily has no fractional bits." +msgstr "" + +#: ../Doc/library/math.rst:202 +msgid "Return ``e**x``." +msgstr "" + +#: ../Doc/library/math.rst:207 +msgid "" +"Return ``e**x - 1``. For small floats *x*, the subtraction in ``exp(x) - " +"1`` can result in a `significant loss of precision `_\\; the :func:`expm1` function provides a way to " +"compute this quantity to full precision::" +msgstr "" + +#: ../Doc/library/math.rst:223 +msgid "With one argument, return the natural logarithm of *x* (to base *e*)." +msgstr "" + +#: ../Doc/library/math.rst:225 +msgid "" +"With two arguments, return the logarithm of *x* to the given *base*, " +"calculated as ``log(x)/log(base)``." +msgstr "" + +#: ../Doc/library/math.rst:231 +msgid "" +"Return the natural logarithm of *1+x* (base *e*). The result is calculated " +"in a way which is accurate for *x* near zero." +msgstr "" + +#: ../Doc/library/math.rst:237 +msgid "" +"Return the base-2 logarithm of *x*. This is usually more accurate than " +"``log(x, 2)``." +msgstr "" + +#: ../Doc/library/math.rst:244 +msgid "" +":meth:`int.bit_length` returns the number of bits necessary to represent an " +"integer in binary, excluding the sign and leading zeros." +msgstr "" + +#: ../Doc/library/math.rst:250 +msgid "" +"Return the base-10 logarithm of *x*. This is usually more accurate than " +"``log(x, 10)``." +msgstr "" + +#: ../Doc/library/math.rst:256 +msgid "" +"Return ``x`` raised to the power ``y``. Exceptional cases follow Annex 'F' " +"of the C99 standard as far as possible. In particular, ``pow(1.0, x)`` and " +"``pow(x, 0.0)`` always return ``1.0``, even when ``x`` is a zero or a NaN. " +"If both ``x`` and ``y`` are finite, ``x`` is negative, and ``y`` is not an " +"integer then ``pow(x, y)`` is undefined, and raises :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/math.rst:263 +msgid "" +"Unlike the built-in ``**`` operator, :func:`math.pow` converts both its " +"arguments to type :class:`float`. Use ``**`` or the built-in :func:`pow` " +"function for computing exact integer powers." +msgstr "" + +#: ../Doc/library/math.rst:270 +msgid "Return the square root of *x*." +msgstr "" + +#: ../Doc/library/math.rst:278 +msgid "Return the arc cosine of *x*, in radians." +msgstr "" + +#: ../Doc/library/math.rst:283 +msgid "Return the arc sine of *x*, in radians." +msgstr "" + +#: ../Doc/library/math.rst:288 +msgid "Return the arc tangent of *x*, in radians." +msgstr "" + +#: ../Doc/library/math.rst:293 +msgid "" +"Return ``atan(y / x)``, in radians. The result is between ``-pi`` and " +"``pi``. The vector in the plane from the origin to point ``(x, y)`` makes " +"this angle with the positive X axis. The point of :func:`atan2` is that the " +"signs of both inputs are known to it, so it can compute the correct quadrant " +"for the angle. For example, ``atan(1)`` and ``atan2(1, 1)`` are both " +"``pi/4``, but ``atan2(-1, -1)`` is ``-3*pi/4``." +msgstr "" + +#: ../Doc/library/math.rst:303 +msgid "Return the cosine of *x* radians." +msgstr "" + +#: ../Doc/library/math.rst:308 +msgid "" +"Return the Euclidean norm, ``sqrt(x*x + y*y)``. This is the length of the " +"vector from the origin to point ``(x, y)``." +msgstr "" + +#: ../Doc/library/math.rst:314 +msgid "Return the sine of *x* radians." +msgstr "" + +#: ../Doc/library/math.rst:319 +msgid "Return the tangent of *x* radians." +msgstr "" + +#: ../Doc/library/math.rst:322 +msgid "Angular conversion" +msgstr "" + +#: ../Doc/library/math.rst:327 +msgid "Convert angle *x* from radians to degrees." +msgstr "" + +#: ../Doc/library/math.rst:332 +msgid "Convert angle *x* from degrees to radians." +msgstr "" + +#: ../Doc/library/math.rst:337 +msgid "" +"`Hyperbolic functions `_ " +"are analogs of trigonometric functions that are based on hyperbolas instead " +"of circles." +msgstr "" + +#: ../Doc/library/math.rst:343 +msgid "Return the inverse hyperbolic cosine of *x*." +msgstr "" + +#: ../Doc/library/math.rst:348 +msgid "Return the inverse hyperbolic sine of *x*." +msgstr "" + +#: ../Doc/library/math.rst:353 +msgid "Return the inverse hyperbolic tangent of *x*." +msgstr "" + +#: ../Doc/library/math.rst:372 +msgid "Special functions" +msgstr "" + +#: ../Doc/library/math.rst:376 +msgid "" +"Return the `error function `_ " +"at *x*." +msgstr "" + +#: ../Doc/library/math.rst:379 +msgid "" +"The :func:`erf` function can be used to compute traditional statistical " +"functions such as the `cumulative standard normal distribution `_::" +msgstr "" + +#: ../Doc/library/math.rst:392 +msgid "" +"Return the complementary error function at *x*. The `complementary error " +"function `_ is defined as " +"``1.0 - erf(x)``. It is used for large values of *x* where a subtraction " +"from one would cause a `loss of significance `_\\." +msgstr "" + +#: ../Doc/library/math.rst:403 +msgid "" +"Return the `Gamma function `_ " +"at *x*." +msgstr "" + +#: ../Doc/library/math.rst:411 +msgid "" +"Return the natural logarithm of the absolute value of the Gamma function at " +"*x*." +msgstr "" + +#: ../Doc/library/math.rst:422 +msgid "The mathematical constant π = 3.141592..., to available precision." +msgstr "" + +#: ../Doc/library/math.rst:427 +msgid "The mathematical constant e = 2.718281..., to available precision." +msgstr "" + +#: ../Doc/library/math.rst:431 +msgid "" +"The mathematical constant τ = 6.283185..., to available precision. Tau is a " +"circle constant equal to 2π, the ratio of a circle's circumference to its " +"radius. To learn more about Tau, check out Vi Hart's video `Pi is (still) " +"Wrong `_, and start celebrating " +"`Tau day `_ by eating twice as much pie!" +msgstr "" + +#: ../Doc/library/math.rst:441 +msgid "" +"A floating-point positive infinity. (For negative infinity, use ``-math." +"inf``.) Equivalent to the output of ``float('inf')``." +msgstr "" + +#: ../Doc/library/math.rst:449 +msgid "" +"A floating-point \"not a number\" (NaN) value. Equivalent to the output of " +"``float('nan')``." +msgstr "" + +#: ../Doc/library/math.rst:457 +msgid "" +"The :mod:`math` module consists mostly of thin wrappers around the platform " +"C math library functions. Behavior in exceptional cases follows Annex F of " +"the C99 standard where appropriate. The current implementation will raise :" +"exc:`ValueError` for invalid operations like ``sqrt(-1.0)`` or ``log(0.0)`` " +"(where C99 Annex F recommends signaling invalid operation or divide-by-" +"zero), and :exc:`OverflowError` for results that overflow (for example, " +"``exp(1000.0)``). A NaN will not be returned from any of the functions " +"above unless one or more of the input arguments was a NaN; in that case, " +"most functions will return a NaN, but (again following C99 Annex F) there " +"are some exceptions to this rule, for example ``pow(float('nan'), 0.0)`` or " +"``hypot(float('nan'), float('inf'))``." +msgstr "" + +#: ../Doc/library/math.rst:469 +msgid "" +"Note that Python makes no effort to distinguish signaling NaNs from quiet " +"NaNs, and behavior for signaling NaNs remains unspecified. Typical behavior " +"is to treat all NaNs as though they were quiet." +msgstr "" + +#: ../Doc/library/math.rst:476 +msgid "Module :mod:`cmath`" +msgstr "" + +#: ../Doc/library/math.rst:477 +msgid "Complex number versions of many of these functions." +msgstr "" + +#: ../Doc/library/mimetypes.rst:2 +msgid ":mod:`mimetypes` --- Map filenames to MIME types" +msgstr "" + +#: ../Doc/library/mimetypes.rst:9 +msgid "**Source code:** :source:`Lib/mimetypes.py`" +msgstr "" + +#: ../Doc/library/mimetypes.rst:15 +msgid "" +"The :mod:`mimetypes` module converts between a filename or URL and the MIME " +"type associated with the filename extension. Conversions are provided from " +"filename to MIME type and from MIME type to filename extension; encodings " +"are not supported for the latter conversion." +msgstr "" + +#: ../Doc/library/mimetypes.rst:20 +msgid "" +"The module provides one class and a number of convenience functions. The " +"functions are the normal interface to this module, but some applications may " +"be interested in the class as well." +msgstr "" + +#: ../Doc/library/mimetypes.rst:24 +msgid "" +"The functions described below provide the primary interface for this " +"module. If the module has not been initialized, they will call :func:`init` " +"if they rely on the information :func:`init` sets up." +msgstr "" + +#: ../Doc/library/mimetypes.rst:33 +msgid "" +"Guess the type of a file based on its filename or URL, given by *url*. The " +"return value is a tuple ``(type, encoding)`` where *type* is ``None`` if the " +"type can't be guessed (missing or unknown suffix) or a string of the form " +"``'type/subtype'``, usable for a MIME :mailheader:`content-type` header." +msgstr "" + +#: ../Doc/library/mimetypes.rst:38 +msgid "" +"*encoding* is ``None`` for no encoding or the name of the program used to " +"encode (e.g. :program:`compress` or :program:`gzip`). The encoding is " +"suitable for use as a :mailheader:`Content-Encoding` header, **not** as a :" +"mailheader:`Content-Transfer-Encoding` header. The mappings are table " +"driven. Encoding suffixes are case sensitive; type suffixes are first tried " +"case sensitively, then case insensitively." +msgstr "" + +#: ../Doc/library/mimetypes.rst:45 +msgid "" +"The optional *strict* argument is a flag specifying whether the list of " +"known MIME types is limited to only the official types `registered with IANA " +"`_. When " +"*strict* is ``True`` (the default), only the IANA types are supported; when " +"*strict* is ``False``, some additional non-standard but commonly used MIME " +"types are also recognized." +msgstr "" + +#: ../Doc/library/mimetypes.rst:55 +msgid "" +"Guess the extensions for a file based on its MIME type, given by *type*. The " +"return value is a list of strings giving all possible filename extensions, " +"including the leading dot (``'.'``). The extensions are not guaranteed to " +"have been associated with any particular data stream, but would be mapped to " +"the MIME type *type* by :func:`guess_type`." +msgstr "" + +#: ../Doc/library/mimetypes.rst:61 ../Doc/library/mimetypes.rst:73 +msgid "" +"The optional *strict* argument has the same meaning as with the :func:" +"`guess_type` function." +msgstr "" + +#: ../Doc/library/mimetypes.rst:66 +msgid "" +"Guess the extension for a file based on its MIME type, given by *type*. The " +"return value is a string giving a filename extension, including the leading " +"dot (``'.'``). The extension is not guaranteed to have been associated with " +"any particular data stream, but would be mapped to the MIME type *type* by :" +"func:`guess_type`. If no extension can be guessed for *type*, ``None`` is " +"returned." +msgstr "" + +#: ../Doc/library/mimetypes.rst:75 +msgid "" +"Some additional functions and data items are available for controlling the " +"behavior of the module." +msgstr "" + +#: ../Doc/library/mimetypes.rst:81 +msgid "" +"Initialize the internal data structures. If given, *files* must be a " +"sequence of file names which should be used to augment the default type " +"map. If omitted, the file names to use are taken from :const:`knownfiles`; " +"on Windows, the current registry settings are loaded. Each file named in " +"*files* or :const:`knownfiles` takes precedence over those named before it. " +"Calling :func:`init` repeatedly is allowed." +msgstr "" + +#: ../Doc/library/mimetypes.rst:88 +msgid "" +"Specifying an empty list for *files* will prevent the system defaults from " +"being applied: only the well-known values will be present from a built-in " +"list." +msgstr "" + +#: ../Doc/library/mimetypes.rst:91 +msgid "Previously, Windows registry settings were ignored." +msgstr "" + +#: ../Doc/library/mimetypes.rst:97 +msgid "" +"Load the type map given in the file *filename*, if it exists. The type map " +"is returned as a dictionary mapping filename extensions, including the " +"leading dot (``'.'``), to strings of the form ``'type/subtype'``. If the " +"file *filename* does not exist or cannot be read, ``None`` is returned." +msgstr "" + +#: ../Doc/library/mimetypes.rst:105 +msgid "" +"Add a mapping from the MIME type *type* to the extension *ext*. When the " +"extension is already known, the new type will replace the old one. When the " +"type is already known the extension will be added to the list of known " +"extensions." +msgstr "" + +#: ../Doc/library/mimetypes.rst:109 +msgid "" +"When *strict* is ``True`` (the default), the mapping will be added to the " +"official MIME types, otherwise to the non-standard ones." +msgstr "" + +#: ../Doc/library/mimetypes.rst:115 +msgid "" +"Flag indicating whether or not the global data structures have been " +"initialized. This is set to ``True`` by :func:`init`." +msgstr "" + +#: ../Doc/library/mimetypes.rst:123 +msgid "" +"List of type map file names commonly installed. These files are typically " +"named :file:`mime.types` and are installed in different locations by " +"different packages." +msgstr "" + +#: ../Doc/library/mimetypes.rst:130 +msgid "" +"Dictionary mapping suffixes to suffixes. This is used to allow recognition " +"of encoded files for which the encoding and the type are indicated by the " +"same extension. For example, the :file:`.tgz` extension is mapped to :file:" +"`.tar.gz` to allow the encoding and type to be recognized separately." +msgstr "" + +#: ../Doc/library/mimetypes.rst:138 +msgid "Dictionary mapping filename extensions to encoding types." +msgstr "" + +#: ../Doc/library/mimetypes.rst:143 +msgid "Dictionary mapping filename extensions to MIME types." +msgstr "" + +#: ../Doc/library/mimetypes.rst:148 +msgid "" +"Dictionary mapping filename extensions to non-standard, but commonly found " +"MIME types." +msgstr "" + +#: ../Doc/library/mimetypes.rst:152 +msgid "An example usage of the module::" +msgstr "" + +#: ../Doc/library/mimetypes.rst:169 +msgid "MimeTypes Objects" +msgstr "" + +#: ../Doc/library/mimetypes.rst:171 +msgid "" +"The :class:`MimeTypes` class may be useful for applications which may want " +"more than one MIME-type database; it provides an interface similar to the " +"one of the :mod:`mimetypes` module." +msgstr "" + +#: ../Doc/library/mimetypes.rst:178 +msgid "" +"This class represents a MIME-types database. By default, it provides access " +"to the same database as the rest of this module. The initial database is a " +"copy of that provided by the module, and may be extended by loading " +"additional :file:`mime.types`\\ -style files into the database using the :" +"meth:`read` or :meth:`readfp` methods. The mapping dictionaries may also be " +"cleared before loading additional data if the default data is not desired." +msgstr "" + +#: ../Doc/library/mimetypes.rst:185 +msgid "" +"The optional *filenames* parameter can be used to cause additional files to " +"be loaded \"on top\" of the default database." +msgstr "" + +#: ../Doc/library/mimetypes.rst:191 +msgid "" +"Dictionary mapping suffixes to suffixes. This is used to allow recognition " +"of encoded files for which the encoding and the type are indicated by the " +"same extension. For example, the :file:`.tgz` extension is mapped to :file:" +"`.tar.gz` to allow the encoding and type to be recognized separately. This " +"is initially a copy of the global :data:`suffix_map` defined in the module." +msgstr "" + +#: ../Doc/library/mimetypes.rst:200 +msgid "" +"Dictionary mapping filename extensions to encoding types. This is initially " +"a copy of the global :data:`encodings_map` defined in the module." +msgstr "" + +#: ../Doc/library/mimetypes.rst:206 +msgid "" +"Tuple containing two dictionaries, mapping filename extensions to MIME " +"types: the first dictionary is for the non-standards types and the second " +"one is for the standard types. They are initialized by :data:`common_types` " +"and :data:`types_map`." +msgstr "" + +#: ../Doc/library/mimetypes.rst:214 +msgid "" +"Tuple containing two dictionaries, mapping MIME types to a list of filename " +"extensions: the first dictionary is for the non-standards types and the " +"second one is for the standard types. They are initialized by :data:" +"`common_types` and :data:`types_map`." +msgstr "" + +#: ../Doc/library/mimetypes.rst:222 +msgid "" +"Similar to the :func:`guess_extension` function, using the tables stored as " +"part of the object." +msgstr "" + +#: ../Doc/library/mimetypes.rst:228 +msgid "" +"Similar to the :func:`guess_type` function, using the tables stored as part " +"of the object." +msgstr "" + +#: ../Doc/library/mimetypes.rst:234 +msgid "" +"Similar to the :func:`guess_all_extensions` function, using the tables " +"stored as part of the object." +msgstr "" + +#: ../Doc/library/mimetypes.rst:240 +msgid "" +"Load MIME information from a file named *filename*. This uses :meth:" +"`readfp` to parse the file." +msgstr "" + +#: ../Doc/library/mimetypes.rst:243 +msgid "" +"If *strict* is ``True``, information will be added to list of standard " +"types, else to the list of non-standard types." +msgstr "" + +#: ../Doc/library/mimetypes.rst:249 +msgid "" +"Load MIME type information from an open file *fp*. The file must have the " +"format of the standard :file:`mime.types` files." +msgstr "" + +#: ../Doc/library/mimetypes.rst:252 ../Doc/library/mimetypes.rst:260 +msgid "" +"If *strict* is ``True``, information will be added to the list of standard " +"types, else to the list of non-standard types." +msgstr "" + +#: ../Doc/library/mimetypes.rst:258 +msgid "" +"Load MIME type information from the Windows registry. Availability: Windows." +msgstr "" + +#: ../Doc/library/misc.rst:5 +msgid "Miscellaneous Services" +msgstr "" + +#: ../Doc/library/misc.rst:7 +msgid "" +"The modules described in this chapter provide miscellaneous services that " +"are available in all Python versions. Here's an overview:" +msgstr "" + +#: ../Doc/library/mm.rst:5 +msgid "Multimedia Services" +msgstr "" + +#: ../Doc/library/mm.rst:7 +msgid "" +"The modules described in this chapter implement various algorithms or " +"interfaces that are mainly useful for multimedia applications. They are " +"available at the discretion of the installation. Here's an overview:" +msgstr "" + +#: ../Doc/library/mmap.rst:2 +msgid ":mod:`mmap` --- Memory-mapped file support" +msgstr "" + +#: ../Doc/library/mmap.rst:9 +msgid "" +"Memory-mapped file objects behave like both :class:`bytearray` and like :" +"term:`file objects `. You can use mmap objects in most places " +"where :class:`bytearray` are expected; for example, you can use the :mod:" +"`re` module to search through a memory-mapped file. You can also change a " +"single byte by doing ``obj[index] = 97``, or change a subsequence by " +"assigning to a slice: ``obj[i1:i2] = b'...'``. You can also read and write " +"data starting at the current file position, and :meth:`seek` through the " +"file to different positions." +msgstr "" + +#: ../Doc/library/mmap.rst:17 +msgid "" +"A memory-mapped file is created by the :class:`mmap` constructor, which is " +"different on Unix and on Windows. In either case you must provide a file " +"descriptor for a file opened for update. If you wish to map an existing " +"Python file object, use its :meth:`fileno` method to obtain the correct " +"value for the *fileno* parameter. Otherwise, you can open the file using " +"the :func:`os.open` function, which returns a file descriptor directly (the " +"file still needs to be closed when done)." +msgstr "" + +#: ../Doc/library/mmap.rst:26 +msgid "" +"If you want to create a memory-mapping for a writable, buffered file, you " +"should :func:`~io.IOBase.flush` the file first. This is necessary to ensure " +"that local modifications to the buffers are actually available to the " +"mapping." +msgstr "" + +#: ../Doc/library/mmap.rst:31 +msgid "" +"For both the Unix and Windows versions of the constructor, *access* may be " +"specified as an optional keyword parameter. *access* accepts one of three " +"values: :const:`ACCESS_READ`, :const:`ACCESS_WRITE`, or :const:`ACCESS_COPY` " +"to specify read-only, write-through or copy-on-write memory respectively. " +"*access* can be used on both Unix and Windows. If *access* is not " +"specified, Windows mmap returns a write-through mapping. The initial memory " +"values for all three access types are taken from the specified file. " +"Assignment to an :const:`ACCESS_READ` memory map raises a :exc:`TypeError` " +"exception. Assignment to an :const:`ACCESS_WRITE` memory map affects both " +"memory and the underlying file. Assignment to an :const:`ACCESS_COPY` " +"memory map affects memory but does not update the underlying file." +msgstr "" + +#: ../Doc/library/mmap.rst:43 +msgid "" +"To map anonymous memory, -1 should be passed as the fileno along with the " +"length." +msgstr "" + +#: ../Doc/library/mmap.rst:47 +msgid "" +"**(Windows version)** Maps *length* bytes from the file specified by the " +"file handle *fileno*, and creates a mmap object. If *length* is larger than " +"the current size of the file, the file is extended to contain *length* " +"bytes. If *length* is ``0``, the maximum length of the map is the current " +"size of the file, except that if the file is empty Windows raises an " +"exception (you cannot create an empty mapping on Windows)." +msgstr "" + +#: ../Doc/library/mmap.rst:54 +msgid "" +"*tagname*, if specified and not ``None``, is a string giving a tag name for " +"the mapping. Windows allows you to have many different mappings against the " +"same file. If you specify the name of an existing tag, that tag is opened, " +"otherwise a new tag of this name is created. If this parameter is omitted " +"or ``None``, the mapping is created without a name. Avoiding the use of the " +"tag parameter will assist in keeping your code portable between Unix and " +"Windows." +msgstr "" + +#: ../Doc/library/mmap.rst:62 +msgid "" +"*offset* may be specified as a non-negative integer offset. mmap references " +"will be relative to the offset from the beginning of the file. *offset* " +"defaults to 0. *offset* must be a multiple of the ALLOCATIONGRANULARITY." +msgstr "" + +#: ../Doc/library/mmap.rst:70 +msgid "" +"**(Unix version)** Maps *length* bytes from the file specified by the file " +"descriptor *fileno*, and returns a mmap object. If *length* is ``0``, the " +"maximum length of the map will be the current size of the file when :class:" +"`mmap` is called." +msgstr "" + +#: ../Doc/library/mmap.rst:75 +msgid "" +"*flags* specifies the nature of the mapping. :const:`MAP_PRIVATE` creates a " +"private copy-on-write mapping, so changes to the contents of the mmap object " +"will be private to this process, and :const:`MAP_SHARED` creates a mapping " +"that's shared with all other processes mapping the same areas of the file. " +"The default value is :const:`MAP_SHARED`." +msgstr "" + +#: ../Doc/library/mmap.rst:81 +msgid "" +"*prot*, if specified, gives the desired memory protection; the two most " +"useful values are :const:`PROT_READ` and :const:`PROT_WRITE`, to specify " +"that the pages may be read or written. *prot* defaults to :const:`PROT_READ " +"\\| PROT_WRITE`." +msgstr "" + +#: ../Doc/library/mmap.rst:86 +msgid "" +"*access* may be specified in lieu of *flags* and *prot* as an optional " +"keyword parameter. It is an error to specify both *flags*, *prot* and " +"*access*. See the description of *access* above for information on how to " +"use this parameter." +msgstr "" + +#: ../Doc/library/mmap.rst:91 +msgid "" +"*offset* may be specified as a non-negative integer offset. mmap references " +"will be relative to the offset from the beginning of the file. *offset* " +"defaults to 0. *offset* must be a multiple of the PAGESIZE or " +"ALLOCATIONGRANULARITY." +msgstr "" + +#: ../Doc/library/mmap.rst:96 +msgid "" +"To ensure validity of the created memory mapping the file specified by the " +"descriptor *fileno* is internally automatically synchronized with physical " +"backing store on Mac OS X and OpenVMS." +msgstr "" + +#: ../Doc/library/mmap.rst:100 +msgid "This example shows a simple way of using :class:`mmap`::" +msgstr "" + +#: ../Doc/library/mmap.rst:125 +msgid "" +":class:`mmap` can also be used as a context manager in a :keyword:`with` " +"statement.::" +msgstr "" + +#: ../Doc/library/mmap.rst:133 +msgid "Context manager support." +msgstr "" + +#: ../Doc/library/mmap.rst:137 +msgid "" +"The next example demonstrates how to create an anonymous map and exchange " +"data between the parent and child processes::" +msgstr "" + +#: ../Doc/library/mmap.rst:155 +msgid "Memory-mapped file objects support the following methods:" +msgstr "" + +#: ../Doc/library/mmap.rst:159 +msgid "" +"Closes the mmap. Subsequent calls to other methods of the object will result " +"in a ValueError exception being raised. This will not close the open file." +msgstr "" + +#: ../Doc/library/mmap.rst:166 +msgid "``True`` if the file is closed." +msgstr "" + +#: ../Doc/library/mmap.rst:173 +msgid "" +"Returns the lowest index in the object where the subsequence *sub* is found, " +"such that *sub* is contained in the range [*start*, *end*]. Optional " +"arguments *start* and *end* are interpreted as in slice notation. Returns " +"``-1`` on failure." +msgstr "" + +#: ../Doc/library/mmap.rst:178 ../Doc/library/mmap.rst:241 +#: ../Doc/library/mmap.rst:273 ../Doc/library/ossaudiodev.rst:159 +#: ../Doc/library/ossaudiodev.rst:173 ../Doc/library/socket.rst:63 +#: ../Doc/library/socket.rst:715 ../Doc/library/socket.rst:757 +#: ../Doc/library/socket.rst:1399 ../Doc/library/ssl.rst:366 +msgid "Writable :term:`bytes-like object` is now accepted." +msgstr "" + +#: ../Doc/library/mmap.rst:184 +msgid "" +"Flushes changes made to the in-memory copy of a file back to disk. Without " +"use of this call there is no guarantee that changes are written back before " +"the object is destroyed. If *offset* and *size* are specified, only changes " +"to the given range of bytes will be flushed to disk; otherwise, the whole " +"extent of the mapping is flushed." +msgstr "" + +#: ../Doc/library/mmap.rst:190 +msgid "" +"**(Windows version)** A nonzero value returned indicates success; zero " +"indicates failure." +msgstr "" + +#: ../Doc/library/mmap.rst:193 +msgid "" +"**(Unix version)** A zero value is returned to indicate success. An " +"exception is raised when the call failed." +msgstr "" + +#: ../Doc/library/mmap.rst:199 +msgid "" +"Copy the *count* bytes starting at offset *src* to the destination index " +"*dest*. If the mmap was created with :const:`ACCESS_READ`, then calls to " +"move will raise a :exc:`TypeError` exception." +msgstr "" + +#: ../Doc/library/mmap.rst:206 +msgid "" +"Return a :class:`bytes` containing up to *n* bytes starting from the current " +"file position. If the argument is omitted, *None* or negative, return all " +"bytes from the current file position to the end of the mapping. The file " +"position is updated to point after the bytes that were returned." +msgstr "" + +#: ../Doc/library/mmap.rst:212 +msgid "Argument can be omitted or *None*." +msgstr "" + +#: ../Doc/library/mmap.rst:217 +msgid "" +"Returns a byte at the current file position as an integer, and advances the " +"file position by 1." +msgstr "" + +#: ../Doc/library/mmap.rst:223 +msgid "" +"Returns a single line, starting at the current file position and up to the " +"next newline." +msgstr "" + +#: ../Doc/library/mmap.rst:229 +msgid "" +"Resizes the map and the underlying file, if any. If the mmap was created " +"with :const:`ACCESS_READ` or :const:`ACCESS_COPY`, resizing the map will " +"raise a :exc:`TypeError` exception." +msgstr "" + +#: ../Doc/library/mmap.rst:236 +msgid "" +"Returns the highest index in the object where the subsequence *sub* is " +"found, such that *sub* is contained in the range [*start*, *end*]. Optional " +"arguments *start* and *end* are interpreted as in slice notation. Returns " +"``-1`` on failure." +msgstr "" + +#: ../Doc/library/mmap.rst:247 +msgid "" +"Set the file's current position. *whence* argument is optional and defaults " +"to ``os.SEEK_SET`` or ``0`` (absolute file positioning); other values are " +"``os.SEEK_CUR`` or ``1`` (seek relative to the current position) and ``os." +"SEEK_END`` or ``2`` (seek relative to the file's end)." +msgstr "" + +#: ../Doc/library/mmap.rst:255 +msgid "" +"Return the length of the file, which can be larger than the size of the " +"memory-mapped area." +msgstr "" + +#: ../Doc/library/mmap.rst:261 +msgid "Returns the current position of the file pointer." +msgstr "" + +#: ../Doc/library/mmap.rst:266 +msgid "" +"Write the bytes in *bytes* into memory at the current position of the file " +"pointer and return the number of bytes written (never less than " +"``len(bytes)``, since if the write fails, a :exc:`ValueError` will be " +"raised). The file position is updated to point after the bytes that were " +"written. If the mmap was created with :const:`ACCESS_READ`, then writing to " +"it will raise a :exc:`TypeError` exception." +msgstr "" + +#: ../Doc/library/mmap.rst:276 +msgid "The number of bytes written is now returned." +msgstr "" + +#: ../Doc/library/mmap.rst:282 +msgid "" +"Write the integer *byte* into memory at the current position of the file " +"pointer; the file position is advanced by ``1``. If the mmap was created " +"with :const:`ACCESS_READ`, then writing to it will raise a :exc:`TypeError` " +"exception." +msgstr "" + +#: ../Doc/library/modulefinder.rst:2 +msgid ":mod:`modulefinder` --- Find modules used by a script" +msgstr "" + +#: ../Doc/library/modulefinder.rst:9 +msgid "**Source code:** :source:`Lib/modulefinder.py`" +msgstr "" + +#: ../Doc/library/modulefinder.rst:13 +msgid "" +"This module provides a :class:`ModuleFinder` class that can be used to " +"determine the set of modules imported by a script. ``modulefinder.py`` can " +"also be run as a script, giving the filename of a Python script as its " +"argument, after which a report of the imported modules will be printed." +msgstr "" + +#: ../Doc/library/modulefinder.rst:21 +msgid "" +"Record that the package named *pkg_name* can be found in the specified " +"*path*." +msgstr "" + +#: ../Doc/library/modulefinder.rst:26 +msgid "" +"Allows specifying that the module named *oldname* is in fact the package " +"named *newname*." +msgstr "" + +#: ../Doc/library/modulefinder.rst:32 +msgid "" +"This class provides :meth:`run_script` and :meth:`report` methods to " +"determine the set of modules imported by a script. *path* can be a list of " +"directories to search for modules; if not specified, ``sys.path`` is used. " +"*debug* sets the debugging level; higher values make the class print " +"debugging messages about what it's doing. *excludes* is a list of module " +"names to exclude from the analysis. *replace_paths* is a list of ``(oldpath, " +"newpath)`` tuples that will be replaced in module paths." +msgstr "" + +#: ../Doc/library/modulefinder.rst:43 +msgid "" +"Print a report to standard output that lists the modules imported by the " +"script and their paths, as well as modules that are missing or seem to be " +"missing." +msgstr "" + +#: ../Doc/library/modulefinder.rst:49 +msgid "" +"Analyze the contents of the *pathname* file, which must contain Python code." +msgstr "" + +#: ../Doc/library/modulefinder.rst:54 +msgid "" +"A dictionary mapping module names to modules. See :ref:`modulefinder-" +"example`." +msgstr "" + +#: ../Doc/library/modulefinder.rst:61 +msgid "Example usage of :class:`ModuleFinder`" +msgstr "" + +#: ../Doc/library/modulefinder.rst:63 +msgid "The script that is going to get analyzed later on (bacon.py)::" +msgstr "" + +#: ../Doc/library/modulefinder.rst:78 +msgid "The script that will output the report of bacon.py::" +msgstr "" + +#: ../Doc/library/modulefinder.rst:94 +msgid "Sample output (may vary depending on the architecture)::" +msgstr "" + +#: ../Doc/library/modules.rst:5 +msgid "Importing Modules" +msgstr "" + +#: ../Doc/library/modules.rst:7 +msgid "" +"The modules described in this chapter provide new ways to import other " +"Python modules and hooks for customizing the import process." +msgstr "" + +#: ../Doc/library/msilib.rst:2 +msgid ":mod:`msilib` --- Read and write Microsoft Installer files" +msgstr "" + +#: ../Doc/library/msilib.rst:11 +msgid "**Source code:** :source:`Lib/msilib/__init__.py`" +msgstr "" + +#: ../Doc/library/msilib.rst:17 +msgid "" +"The :mod:`msilib` supports the creation of Microsoft Installer (``.msi``) " +"files. Because these files often contain an embedded \"cabinet\" file (``." +"cab``), it also exposes an API to create CAB files. Support for reading ``." +"cab`` files is currently not implemented; read support for the ``.msi`` " +"database is possible." +msgstr "" + +#: ../Doc/library/msilib.rst:22 +msgid "" +"This package aims to provide complete access to all tables in an ``.msi`` " +"file, therefore, it is a fairly low-level API. Two primary applications of " +"this package are the :mod:`distutils` command ``bdist_msi``, and the " +"creation of Python installer package itself (although that currently uses a " +"different version of ``msilib``)." +msgstr "" + +#: ../Doc/library/msilib.rst:28 +msgid "" +"The package contents can be roughly split into four parts: low-level CAB " +"routines, low-level MSI routines, higher-level MSI routines, and standard " +"table structures." +msgstr "" + +#: ../Doc/library/msilib.rst:35 +msgid "" +"Create a new CAB file named *cabname*. *files* must be a list of tuples, " +"each containing the name of the file on disk, and the name of the file " +"inside the CAB file." +msgstr "" + +#: ../Doc/library/msilib.rst:39 +msgid "" +"The files are added to the CAB file in the order they appear in the list. " +"All files are added into a single CAB file, using the MSZIP compression " +"algorithm." +msgstr "" + +#: ../Doc/library/msilib.rst:42 +msgid "" +"Callbacks to Python for the various steps of MSI creation are currently not " +"exposed." +msgstr "" + +#: ../Doc/library/msilib.rst:48 +msgid "" +"Return the string representation of a new unique identifier. This wraps the " +"Windows API functions :c:func:`UuidCreate` and :c:func:`UuidToString`." +msgstr "" + +#: ../Doc/library/msilib.rst:54 +msgid "" +"Return a new database object by calling MsiOpenDatabase. *path* is the " +"file name of the MSI file; *persist* can be one of the constants " +"``MSIDBOPEN_CREATEDIRECT``, ``MSIDBOPEN_CREATE``, ``MSIDBOPEN_DIRECT``, " +"``MSIDBOPEN_READONLY``, or ``MSIDBOPEN_TRANSACT``, and may include the flag " +"``MSIDBOPEN_PATCHFILE``. See the Microsoft documentation for the meaning of " +"these flags; depending on the flags, an existing database is opened, or a " +"new one created." +msgstr "" + +#: ../Doc/library/msilib.rst:65 +msgid "" +"Return a new record object by calling :c:func:`MSICreateRecord`. *count* is " +"the number of fields of the record." +msgstr "" + +#: ../Doc/library/msilib.rst:71 +msgid "" +"Create and return a new database *name*, initialize it with *schema*, and " +"set the properties *ProductName*, *ProductCode*, *ProductVersion*, and " +"*Manufacturer*." +msgstr "" + +#: ../Doc/library/msilib.rst:75 +msgid "" +"*schema* must be a module object containing ``tables`` and " +"``_Validation_records`` attributes; typically, :mod:`msilib.schema` should " +"be used." +msgstr "" + +#: ../Doc/library/msilib.rst:79 +msgid "" +"The database will contain just the schema and the validation records when " +"this function returns." +msgstr "" + +#: ../Doc/library/msilib.rst:85 +msgid "Add all *records* to the table named *table* in *database*." +msgstr "" + +#: ../Doc/library/msilib.rst:87 +msgid "" +"The *table* argument must be one of the predefined tables in the MSI schema, " +"e.g. ``'Feature'``, ``'File'``, ``'Component'``, ``'Dialog'``, " +"``'Control'``, etc." +msgstr "" + +#: ../Doc/library/msilib.rst:91 +msgid "" +"*records* should be a list of tuples, each one containing all fields of a " +"record according to the schema of the table. For optional fields, ``None`` " +"can be passed." +msgstr "" + +#: ../Doc/library/msilib.rst:95 +msgid "Field values can be ints, strings, or instances of the Binary class." +msgstr "" + +#: ../Doc/library/msilib.rst:100 +msgid "" +"Represents entries in the Binary table; inserting such an object using :func:" +"`add_data` reads the file named *filename* into the table." +msgstr "" + +#: ../Doc/library/msilib.rst:106 +msgid "" +"Add all table content from *module* to *database*. *module* must contain an " +"attribute *tables* listing all tables for which content should be added, and " +"one attribute per table that has the actual content." +msgstr "" + +#: ../Doc/library/msilib.rst:110 +msgid "This is typically used to install the sequence tables." +msgstr "" + +#: ../Doc/library/msilib.rst:115 +msgid "" +"Add the file *path* into the ``_Stream`` table of *database*, with the " +"stream name *name*." +msgstr "" + +#: ../Doc/library/msilib.rst:121 +msgid "" +"Return a new UUID, in the format that MSI typically requires (i.e. in curly " +"braces, and with all hexdigits in upper-case)." +msgstr "" + +#: ../Doc/library/msilib.rst:127 +msgid "" +"`FCICreateFile `_ `UuidCreate `_ `UuidToString `_" +msgstr "" + +#: ../Doc/library/msilib.rst:134 +msgid "Database Objects" +msgstr "" + +#: ../Doc/library/msilib.rst:139 +msgid "" +"Return a view object, by calling :c:func:`MSIDatabaseOpenView`. *sql* is the " +"SQL statement to execute." +msgstr "" + +#: ../Doc/library/msilib.rst:145 +msgid "" +"Commit the changes pending in the current transaction, by calling :c:func:" +"`MSIDatabaseCommit`." +msgstr "" + +#: ../Doc/library/msilib.rst:151 +msgid "" +"Return a new summary information object, by calling :c:func:" +"`MsiGetSummaryInformation`. *count* is the maximum number of updated values." +msgstr "" + +#: ../Doc/library/msilib.rst:158 +msgid "" +"`MSIDatabaseOpenView `_ `MSIDatabaseCommit `_ " +"`MSIGetSummaryInformation `_" +msgstr "" + +#: ../Doc/library/msilib.rst:165 +msgid "View Objects" +msgstr "" + +#: ../Doc/library/msilib.rst:170 +msgid "" +"Execute the SQL query of the view, through :c:func:`MSIViewExecute`. If " +"*params* is not ``None``, it is a record describing actual values of the " +"parameter tokens in the query." +msgstr "" + +#: ../Doc/library/msilib.rst:177 +msgid "" +"Return a record describing the columns of the view, through calling :c:func:" +"`MsiViewGetColumnInfo`. *kind* can be either ``MSICOLINFO_NAMES`` or " +"``MSICOLINFO_TYPES``." +msgstr "" + +#: ../Doc/library/msilib.rst:184 +msgid "" +"Return a result record of the query, through calling :c:func:`MsiViewFetch`." +msgstr "" + +#: ../Doc/library/msilib.rst:189 +msgid "" +"Modify the view, by calling :c:func:`MsiViewModify`. *kind* can be one of " +"``MSIMODIFY_SEEK``, ``MSIMODIFY_REFRESH``, ``MSIMODIFY_INSERT``, " +"``MSIMODIFY_UPDATE``, ``MSIMODIFY_ASSIGN``, ``MSIMODIFY_REPLACE``, " +"``MSIMODIFY_MERGE``, ``MSIMODIFY_DELETE``, ``MSIMODIFY_INSERT_TEMPORARY``, " +"``MSIMODIFY_VALIDATE``, ``MSIMODIFY_VALIDATE_NEW``, " +"``MSIMODIFY_VALIDATE_FIELD``, or ``MSIMODIFY_VALIDATE_DELETE``." +msgstr "" + +#: ../Doc/library/msilib.rst:196 +msgid "*data* must be a record describing the new data." +msgstr "" + +#: ../Doc/library/msilib.rst:201 +msgid "Close the view, through :c:func:`MsiViewClose`." +msgstr "" + +#: ../Doc/library/msilib.rst:206 +msgid "" +"`MsiViewExecute `_ `MSIViewGetColumnInfo `_ " +"`MsiViewFetch `_ `MsiViewModify `_ `MsiViewClose `_" +msgstr "" + +#: ../Doc/library/msilib.rst:215 +msgid "Summary Information Objects" +msgstr "" + +#: ../Doc/library/msilib.rst:220 +msgid "" +"Return a property of the summary, through :c:func:" +"`MsiSummaryInfoGetProperty`. *field* is the name of the property, and can be " +"one of the constants ``PID_CODEPAGE``, ``PID_TITLE``, ``PID_SUBJECT``, " +"``PID_AUTHOR``, ``PID_KEYWORDS``, ``PID_COMMENTS``, ``PID_TEMPLATE``, " +"``PID_LASTAUTHOR``, ``PID_REVNUMBER``, ``PID_LASTPRINTED``, " +"``PID_CREATE_DTM``, ``PID_LASTSAVE_DTM``, ``PID_PAGECOUNT``, " +"``PID_WORDCOUNT``, ``PID_CHARCOUNT``, ``PID_APPNAME``, or ``PID_SECURITY``." +msgstr "" + +#: ../Doc/library/msilib.rst:231 +msgid "" +"Return the number of summary properties, through :c:func:" +"`MsiSummaryInfoGetPropertyCount`." +msgstr "" + +#: ../Doc/library/msilib.rst:237 +msgid "" +"Set a property through :c:func:`MsiSummaryInfoSetProperty`. *field* can have " +"the same values as in :meth:`GetProperty`, *value* is the new value of the " +"property. Possible value types are integer and string." +msgstr "" + +#: ../Doc/library/msilib.rst:244 +msgid "" +"Write the modified properties to the summary information stream, using :c:" +"func:`MsiSummaryInfoPersist`." +msgstr "" + +#: ../Doc/library/msilib.rst:250 +msgid "" +"`MsiSummaryInfoGetProperty `_ " +"`MsiSummaryInfoGetPropertyCount `_ " +"`MsiSummaryInfoSetProperty `_ `MsiSummaryInfoPersist " +"`_" +msgstr "" + +#: ../Doc/library/msilib.rst:258 +msgid "Record Objects" +msgstr "" + +#: ../Doc/library/msilib.rst:263 +msgid "" +"Return the number of fields of the record, through :c:func:" +"`MsiRecordGetFieldCount`." +msgstr "" + +#: ../Doc/library/msilib.rst:269 +msgid "" +"Return the value of *field* as an integer where possible. *field* must be " +"an integer." +msgstr "" + +#: ../Doc/library/msilib.rst:275 +msgid "" +"Return the value of *field* as a string where possible. *field* must be an " +"integer." +msgstr "" + +#: ../Doc/library/msilib.rst:281 +msgid "" +"Set *field* to *value* through :c:func:`MsiRecordSetString`. *field* must be " +"an integer; *value* a string." +msgstr "" + +#: ../Doc/library/msilib.rst:287 +msgid "" +"Set *field* to the contents of the file named *value*, through :c:func:" +"`MsiRecordSetStream`. *field* must be an integer; *value* a string." +msgstr "" + +#: ../Doc/library/msilib.rst:293 +msgid "" +"Set *field* to *value* through :c:func:`MsiRecordSetInteger`. Both *field* " +"and *value* must be an integer." +msgstr "" + +#: ../Doc/library/msilib.rst:299 +msgid "" +"Set all fields of the record to 0, through :c:func:`MsiRecordClearData`." +msgstr "" + +#: ../Doc/library/msilib.rst:304 +msgid "" +"`MsiRecordGetFieldCount `_ `MsiRecordSetString `_ " +"`MsiRecordSetStream `_ `MsiRecordSetInteger `_ `MsiRecordClear `_" +msgstr "" + +#: ../Doc/library/msilib.rst:313 +msgid "Errors" +msgstr "" + +#: ../Doc/library/msilib.rst:315 +msgid "" +"All wrappers around MSI functions raise :exc:`MsiError`; the string inside " +"the exception will contain more detail." +msgstr "" + +#: ../Doc/library/msilib.rst:322 +msgid "CAB Objects" +msgstr "" + +#: ../Doc/library/msilib.rst:327 +msgid "" +"The class :class:`CAB` represents a CAB file. During MSI construction, files " +"will be added simultaneously to the ``Files`` table, and to a CAB file. " +"Then, when all files have been added, the CAB file can be written, then " +"added to the MSI file." +msgstr "" + +#: ../Doc/library/msilib.rst:332 +msgid "*name* is the name of the CAB file in the MSI file." +msgstr "" + +#: ../Doc/library/msilib.rst:337 +msgid "" +"Add the file with the pathname *full* to the CAB file, under the name " +"*logical*. If there is already a file named *logical*, a new file name is " +"created." +msgstr "" + +#: ../Doc/library/msilib.rst:341 +msgid "" +"Return the index of the file in the CAB file, and the new name of the file " +"inside the CAB file." +msgstr "" + +#: ../Doc/library/msilib.rst:347 +msgid "" +"Generate a CAB file, add it as a stream to the MSI file, put it into the " +"``Media`` table, and remove the generated file from the disk." +msgstr "" + +#: ../Doc/library/msilib.rst:354 +msgid "Directory Objects" +msgstr "" + +#: ../Doc/library/msilib.rst:359 +msgid "" +"Create a new directory in the Directory table. There is a current component " +"at each point in time for the directory, which is either explicitly created " +"through :meth:`start_component`, or implicitly when files are added for the " +"first time. Files are added into the current component, and into the cab " +"file. To create a directory, a base directory object needs to be specified " +"(can be ``None``), the path to the physical directory, and a logical " +"directory name. *default* specifies the DefaultDir slot in the directory " +"table. *componentflags* specifies the default flags that new components get." +msgstr "" + +#: ../Doc/library/msilib.rst:371 +msgid "" +"Add an entry to the Component table, and make this component the current " +"component for this directory. If no component name is given, the directory " +"name is used. If no *feature* is given, the current feature is used. If no " +"*flags* are given, the directory's default flags are used. If no *keyfile* " +"is given, the KeyPath is left null in the Component table." +msgstr "" + +#: ../Doc/library/msilib.rst:380 +msgid "" +"Add a file to the current component of the directory, starting a new one if " +"there is no current component. By default, the file name in the source and " +"the file table will be identical. If the *src* file is specified, it is " +"interpreted relative to the current directory. Optionally, a *version* and a " +"*language* can be specified for the entry in the File table." +msgstr "" + +#: ../Doc/library/msilib.rst:389 +msgid "" +"Add a list of files to the current component as specified in the glob " +"pattern. Individual files can be excluded in the *exclude* list." +msgstr "" + +#: ../Doc/library/msilib.rst:395 +msgid "Remove ``.pyc``/``.pyo`` files on uninstall." +msgstr "" + +#: ../Doc/library/msilib.rst:400 +msgid "" +"`Directory Table `_ `File Table `_ `Component Table `_ `FeatureComponents Table `_" +msgstr "" + +#: ../Doc/library/msilib.rst:408 ../Doc/library/turtle.rst:2312 +msgid "Features" +msgstr "" + +#: ../Doc/library/msilib.rst:413 +msgid "" +"Add a new record to the ``Feature`` table, using the values *id*, *parent." +"id*, *title*, *desc*, *display*, *level*, *directory*, and *attributes*. The " +"resulting feature object can be passed to the :meth:`start_component` method " +"of :class:`Directory`." +msgstr "" + +#: ../Doc/library/msilib.rst:421 +msgid "" +"Make this feature the current feature of :mod:`msilib`. New components are " +"automatically added to the default feature, unless a feature is explicitly " +"specified." +msgstr "" + +#: ../Doc/library/msilib.rst:428 +msgid "" +"`Feature Table `_" +msgstr "" + +#: ../Doc/library/msilib.rst:433 +msgid "GUI classes" +msgstr "" + +#: ../Doc/library/msilib.rst:435 +msgid "" +":mod:`msilib` provides several classes that wrap the GUI tables in an MSI " +"database. However, no standard user interface is provided; use :mod:" +"`~distutils.command.bdist_msi` to create MSI files with a user-interface for " +"installing Python packages." +msgstr "" + +#: ../Doc/library/msilib.rst:443 +msgid "" +"Base class of the dialog controls. *dlg* is the dialog object the control " +"belongs to, and *name* is the control's name." +msgstr "" + +#: ../Doc/library/msilib.rst:449 +msgid "Make an entry into the ``ControlEvent`` table for this control." +msgstr "" + +#: ../Doc/library/msilib.rst:454 +msgid "Make an entry into the ``EventMapping`` table for this control." +msgstr "" + +#: ../Doc/library/msilib.rst:459 +msgid "Make an entry into the ``ControlCondition`` table for this control." +msgstr "" + +#: ../Doc/library/msilib.rst:464 +msgid "" +"Create a radio button control named *name*. *property* is the installer " +"property that gets set when a radio button is selected." +msgstr "" + +#: ../Doc/library/msilib.rst:470 +msgid "" +"Add a radio button named *name* to the group, at the coordinates *x*, *y*, " +"*width*, *height*, and with the label *text*. If *value* is ``None``, it " +"defaults to *name*." +msgstr "" + +#: ../Doc/library/msilib.rst:477 +msgid "" +"Return a new :class:`Dialog` object. An entry in the ``Dialog`` table is " +"made, with the specified coordinates, dialog attributes, title, name of the " +"first, default, and cancel controls." +msgstr "" + +#: ../Doc/library/msilib.rst:484 +msgid "" +"Return a new :class:`Control` object. An entry in the ``Control`` table is " +"made with the specified parameters." +msgstr "" + +#: ../Doc/library/msilib.rst:487 +msgid "" +"This is a generic method; for specific types, specialized methods are " +"provided." +msgstr "" + +#: ../Doc/library/msilib.rst:493 +msgid "Add and return a ``Text`` control." +msgstr "" + +#: ../Doc/library/msilib.rst:498 +msgid "Add and return a ``Bitmap`` control." +msgstr "" + +#: ../Doc/library/msilib.rst:503 +msgid "Add and return a ``Line`` control." +msgstr "" + +#: ../Doc/library/msilib.rst:508 +msgid "Add and return a ``PushButton`` control." +msgstr "" + +#: ../Doc/library/msilib.rst:513 +msgid "Add and return a ``RadioButtonGroup`` control." +msgstr "" + +#: ../Doc/library/msilib.rst:518 +msgid "Add and return a ``CheckBox`` control." +msgstr "" + +#: ../Doc/library/msilib.rst:523 +msgid "" +"`Dialog Table `_ `Control Table `_ `Control Types `_ " +"`ControlCondition Table `_ `ControlEvent Table `_ " +"`EventMapping Table `_ `RadioButton Table `_" +msgstr "" + +#: ../Doc/library/msilib.rst:534 +msgid "Precomputed tables" +msgstr "" + +#: ../Doc/library/msilib.rst:536 +msgid "" +":mod:`msilib` provides a few subpackages that contain only schema and table " +"definitions. Currently, these definitions are based on MSI version 2.0." +msgstr "" + +#: ../Doc/library/msilib.rst:542 +msgid "" +"This is the standard MSI schema for MSI 2.0, with the *tables* variable " +"providing a list of table definitions, and *_Validation_records* providing " +"the data for MSI validation." +msgstr "" + +#: ../Doc/library/msilib.rst:549 +msgid "" +"This module contains table contents for the standard sequence tables: " +"*AdminExecuteSequence*, *AdminUISequence*, *AdvtExecuteSequence*, " +"*InstallExecuteSequence*, and *InstallUISequence*." +msgstr "" + +#: ../Doc/library/msilib.rst:556 +msgid "" +"This module contains definitions for the UIText and ActionText tables, for " +"the standard installer actions." +msgstr "" + +#: ../Doc/library/msvcrt.rst:2 +msgid ":mod:`msvcrt` -- Useful routines from the MS VC++ runtime" +msgstr "" + +#: ../Doc/library/msvcrt.rst:12 +msgid "" +"These functions provide access to some useful capabilities on Windows " +"platforms. Some higher-level modules use these functions to build the " +"Windows implementations of their services. For example, the :mod:`getpass` " +"module uses this in the implementation of the :func:`getpass` function." +msgstr "" + +#: ../Doc/library/msvcrt.rst:17 +msgid "" +"Further documentation on these functions can be found in the Platform API " +"documentation." +msgstr "" + +#: ../Doc/library/msvcrt.rst:20 +msgid "" +"The module implements both the normal and wide char variants of the console " +"I/O api. The normal API deals only with ASCII characters and is of limited " +"use for internationalized applications. The wide char API should be used " +"where ever possible." +msgstr "" + +#: ../Doc/library/msvcrt.rst:25 ../Doc/library/ossaudiodev.rst:42 +msgid "" +"Operations in this module now raise :exc:`OSError` where :exc:`IOError` was " +"raised." +msgstr "" + +#: ../Doc/library/msvcrt.rst:33 +msgid "File Operations" +msgstr "" + +#: ../Doc/library/msvcrt.rst:38 +msgid "" +"Lock part of a file based on file descriptor *fd* from the C runtime. " +"Raises :exc:`OSError` on failure. The locked region of the file extends " +"from the current file position for *nbytes* bytes, and may continue beyond " +"the end of the file. *mode* must be one of the :const:`LK_\\*` constants " +"listed below. Multiple regions in a file may be locked at the same time, but " +"may not overlap. Adjacent regions are not merged; they must be unlocked " +"individually." +msgstr "" + +#: ../Doc/library/msvcrt.rst:49 +msgid "" +"Locks the specified bytes. If the bytes cannot be locked, the program " +"immediately tries again after 1 second. If, after 10 attempts, the bytes " +"cannot be locked, :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/msvcrt.rst:57 +msgid "" +"Locks the specified bytes. If the bytes cannot be locked, :exc:`OSError` is " +"raised." +msgstr "" + +#: ../Doc/library/msvcrt.rst:63 +msgid "Unlocks the specified bytes, which must have been previously locked." +msgstr "" + +#: ../Doc/library/msvcrt.rst:68 +msgid "" +"Set the line-end translation mode for the file descriptor *fd*. To set it to " +"text mode, *flags* should be :const:`os.O_TEXT`; for binary, it should be :" +"const:`os.O_BINARY`." +msgstr "" + +#: ../Doc/library/msvcrt.rst:75 +msgid "" +"Create a C runtime file descriptor from the file handle *handle*. The " +"*flags* parameter should be a bitwise OR of :const:`os.O_APPEND`, :const:`os." +"O_RDONLY`, and :const:`os.O_TEXT`. The returned file descriptor may be used " +"as a parameter to :func:`os.fdopen` to create a file object." +msgstr "" + +#: ../Doc/library/msvcrt.rst:83 +msgid "" +"Return the file handle for the file descriptor *fd*. Raises :exc:`OSError` " +"if *fd* is not recognized." +msgstr "" + +#: ../Doc/library/msvcrt.rst:90 +msgid "Console I/O" +msgstr "" + +#: ../Doc/library/msvcrt.rst:95 +msgid "Return true if a keypress is waiting to be read." +msgstr "" + +#: ../Doc/library/msvcrt.rst:100 +msgid "" +"Read a keypress and return the resulting character as a byte string. Nothing " +"is echoed to the console. This call will block if a keypress is not already " +"available, but will not wait for :kbd:`Enter` to be pressed. If the pressed " +"key was a special function key, this will return ``'\\000'`` or ``'\\xe0'``; " +"the next call will return the keycode. The :kbd:`Control-C` keypress cannot " +"be read with this function." +msgstr "" + +#: ../Doc/library/msvcrt.rst:110 +msgid "Wide char variant of :func:`getch`, returning a Unicode value." +msgstr "" + +#: ../Doc/library/msvcrt.rst:115 +msgid "" +"Similar to :func:`getch`, but the keypress will be echoed if it represents " +"a printable character." +msgstr "" + +#: ../Doc/library/msvcrt.rst:121 +msgid "Wide char variant of :func:`getche`, returning a Unicode value." +msgstr "" + +#: ../Doc/library/msvcrt.rst:126 +msgid "Print the byte string *char* to the console without buffering." +msgstr "" + +#: ../Doc/library/msvcrt.rst:131 +msgid "Wide char variant of :func:`putch`, accepting a Unicode value." +msgstr "" + +#: ../Doc/library/msvcrt.rst:136 +msgid "" +"Cause the byte string *char* to be \"pushed back\" into the console buffer; " +"it will be the next character read by :func:`getch` or :func:`getche`." +msgstr "" + +#: ../Doc/library/msvcrt.rst:142 +msgid "Wide char variant of :func:`ungetch`, accepting a Unicode value." +msgstr "" + +#: ../Doc/library/msvcrt.rst:148 +msgid "Other Functions" +msgstr "" + +#: ../Doc/library/msvcrt.rst:153 +msgid "" +"Force the :c:func:`malloc` heap to clean itself up and return unused blocks " +"to the operating system. On failure, this raises :exc:`OSError`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2 +msgid ":mod:`multiprocessing` --- Process-based parallelism" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:7 +msgid "**Source code:** :source:`Lib/multiprocessing/`" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:14 +msgid "" +":mod:`multiprocessing` is a package that supports spawning processes using " +"an API similar to the :mod:`threading` module. The :mod:`multiprocessing` " +"package offers both local and remote concurrency, effectively side-stepping " +"the :term:`Global Interpreter Lock` by using subprocesses instead of " +"threads. Due to this, the :mod:`multiprocessing` module allows the " +"programmer to fully leverage multiple processors on a given machine. It " +"runs on both Unix and Windows." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:22 +msgid "" +"The :mod:`multiprocessing` module also introduces APIs which do not have " +"analogs in the :mod:`threading` module. A prime example of this is the :" +"class:`~multiprocessing.pool.Pool` object which offers a convenient means of " +"parallelizing the execution of a function across multiple input values, " +"distributing the input data across processes (data parallelism). The " +"following example demonstrates the common practice of defining such " +"functions in a module so that child processes can successfully import that " +"module. This basic example of data parallelism using :class:" +"`~multiprocessing.pool.Pool`, ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:40 +msgid "will print to standard output ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:46 +msgid "The :class:`Process` class" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:48 +msgid "" +"In :mod:`multiprocessing`, processes are spawned by creating a :class:" +"`Process` object and then calling its :meth:`~Process.start` method. :class:" +"`Process` follows the API of :class:`threading.Thread`. A trivial example " +"of a multiprocess program is ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:63 +msgid "" +"To show the individual process IDs involved, here is an expanded example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:84 +msgid "" +"For an explanation of why the ``if __name__ == '__main__'`` part is " +"necessary, see :ref:`multiprocessing-programming`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:90 +msgid "Contexts and start methods" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:94 +msgid "" +"Depending on the platform, :mod:`multiprocessing` supports three ways to " +"start a process. These *start methods* are" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:105 +msgid "*spawn*" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:98 +msgid "" +"The parent process starts a fresh python interpreter process. The child " +"process will only inherit those resources necessary to run the process " +"objects :meth:`~Process.run` method. In particular, unnecessary file " +"descriptors and handles from the parent process will not be inherited. " +"Starting a process using this method is rather slow compared to using *fork* " +"or *forkserver*." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:105 +msgid "Available on Unix and Windows. The default on Windows." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:114 +msgid "*fork*" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:108 +msgid "" +"The parent process uses :func:`os.fork` to fork the Python interpreter. The " +"child process, when it begins, is effectively identical to the parent " +"process. All resources of the parent are inherited by the child process. " +"Note that safely forking a multithreaded process is problematic." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:114 +msgid "Available on Unix only. The default on Unix." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:125 +msgid "*forkserver*" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:117 +msgid "" +"When the program starts and selects the *forkserver* start method, a server " +"process is started. From then on, whenever a new process is needed, the " +"parent process connects to the server and requests that it fork a new " +"process. The fork server process is single threaded so it is safe for it to " +"use :func:`os.fork`. No unnecessary resources are inherited." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:124 +msgid "" +"Available on Unix platforms which support passing file descriptors over Unix " +"pipes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:127 +msgid "" +"*spawn* added on all unix platforms, and *forkserver* added for some unix " +"platforms. Child processes no longer inherit all of the parents inheritable " +"handles on Windows." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:133 +msgid "" +"On Unix using the *spawn* or *forkserver* start methods will also start a " +"*semaphore tracker* process which tracks the unlinked named semaphores " +"created by processes of the program. When all processes have exited the " +"semaphore tracker unlinks any remaining semaphores. Usually there should be " +"none, but if a process was killed by a signal there may some \"leaked\" " +"semaphores. (Unlinking the named semaphores is a serious matter since the " +"system allows only a limited number, and they will not be automatically " +"unlinked until the next reboot.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:142 +msgid "" +"To select a start method you use the :func:`set_start_method` in the ``if " +"__name__ == '__main__'`` clause of the main module. For example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:159 +msgid "" +":func:`set_start_method` should not be used more than once in the program." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:162 +msgid "" +"Alternatively, you can use :func:`get_context` to obtain a context object. " +"Context objects have the same API as the multiprocessing module, and allow " +"one to use multiple start methods in the same program. ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:180 +msgid "" +"Note that objects related to one context may not be compatible with " +"processes for a different context. In particular, locks created using the " +"*fork* context cannot be passed to a processes started using the *spawn* or " +"*forkserver* start methods." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:185 +msgid "" +"A library which wants to use a particular start method should probably use :" +"func:`get_context` to avoid interfering with the choice of the library user." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:191 +msgid "Exchanging objects between processes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:193 +msgid "" +":mod:`multiprocessing` supports two types of communication channel between " +"processes:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:196 +msgid "**Queues**" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:198 +msgid "" +"The :class:`Queue` class is a near clone of :class:`queue.Queue`. For " +"example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:213 +msgid "Queues are thread and process safe." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:215 +msgid "**Pipes**" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:217 +msgid "" +"The :func:`Pipe` function returns a pair of connection objects connected by " +"a pipe which by default is duplex (two-way). For example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:233 +msgid "" +"The two connection objects returned by :func:`Pipe` represent the two ends " +"of the pipe. Each connection object has :meth:`~Connection.send` and :meth:" +"`~Connection.recv` methods (among others). Note that data in a pipe may " +"become corrupted if two processes (or threads) try to read from or write to " +"the *same* end of the pipe at the same time. Of course there is no risk of " +"corruption from processes using different ends of the pipe at the same time." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:243 +msgid "Synchronization between processes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:245 +msgid "" +":mod:`multiprocessing` contains equivalents of all the synchronization " +"primitives from :mod:`threading`. For instance one can use a lock to ensure " +"that only one process prints to standard output at a time::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:264 +msgid "" +"Without using the lock output from the different processes is liable to get " +"all mixed up." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:269 +msgid "Sharing state between processes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:271 +msgid "" +"As mentioned above, when doing concurrent programming it is usually best to " +"avoid using shared state as far as possible. This is particularly true when " +"using multiple processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:275 +msgid "" +"However, if you really do need to use some shared data then :mod:" +"`multiprocessing` provides a couple of ways of doing so." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:278 +msgid "**Shared memory**" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:280 +msgid "" +"Data can be stored in a shared memory map using :class:`Value` or :class:" +"`Array`. For example, the following code ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:301 +#: ../Doc/library/multiprocessing.rst:347 +msgid "will print ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:306 +msgid "" +"The ``'d'`` and ``'i'`` arguments used when creating ``num`` and ``arr`` are " +"typecodes of the kind used by the :mod:`array` module: ``'d'`` indicates a " +"double precision float and ``'i'`` indicates a signed integer. These shared " +"objects will be process and thread-safe." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:311 +msgid "" +"For more flexibility in using shared memory one can use the :mod:" +"`multiprocessing.sharedctypes` module which supports the creation of " +"arbitrary ctypes objects allocated from shared memory." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:315 +msgid "**Server process**" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:317 +msgid "" +"A manager object returned by :func:`Manager` controls a server process which " +"holds Python objects and allows other processes to manipulate them using " +"proxies." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:321 +msgid "" +"A manager returned by :func:`Manager` will support types :class:`list`, :" +"class:`dict`, :class:`~managers.Namespace`, :class:`Lock`, :class:`RLock`, :" +"class:`Semaphore`, :class:`BoundedSemaphore`, :class:`Condition`, :class:" +"`Event`, :class:`Barrier`, :class:`Queue`, :class:`Value` and :class:" +"`Array`. For example, ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:352 +msgid "" +"Server process managers are more flexible than using shared memory objects " +"because they can be made to support arbitrary object types. Also, a single " +"manager can be shared by processes on different computers over a network. " +"They are, however, slower than using shared memory." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:359 +msgid "Using a pool of workers" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:361 +msgid "" +"The :class:`~multiprocessing.pool.Pool` class represents a pool of worker " +"processes. It has methods which allows tasks to be offloaded to the worker " +"processes in a few different ways." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:409 +msgid "" +"Note that the methods of a pool should only ever be used by the process " +"which created it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:414 +msgid "" +"Functionality within this package requires that the ``__main__`` module be " +"importable by the children. This is covered in :ref:`multiprocessing-" +"programming` however it is worth pointing out here. This means that some " +"examples, such as the :class:`multiprocessing.pool.Pool` examples will not " +"work in the interactive interpreter. For example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:436 +msgid "" +"(If you try this it will actually output three full tracebacks interleaved " +"in a semi-random fashion, and then you may have to stop the master process " +"somehow.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:442 +#: ../Doc/library/xml.etree.elementtree.rst:456 +msgid "Reference" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:444 +msgid "" +"The :mod:`multiprocessing` package mostly replicates the API of the :mod:" +"`threading` module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:449 +msgid ":class:`Process` and exceptions" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:454 +msgid "" +"Process objects represent activity that is run in a separate process. The :" +"class:`Process` class has equivalents of all the methods of :class:" +"`threading.Thread`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:458 +msgid "" +"The constructor should always be called with keyword arguments. *group* " +"should always be ``None``; it exists solely for compatibility with :class:" +"`threading.Thread`. *target* is the callable object to be invoked by the :" +"meth:`run()` method. It defaults to ``None``, meaning nothing is called. " +"*name* is the process name (see :attr:`name` for more details). *args* is " +"the argument tuple for the target invocation. *kwargs* is a dictionary of " +"keyword arguments for the target invocation. If provided, the keyword-only " +"*daemon* argument sets the process :attr:`daemon` flag to ``True`` or " +"``False``. If ``None`` (the default), this flag will be inherited from the " +"creating process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:469 +msgid "By default, no arguments are passed to *target*." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:471 +msgid "" +"If a subclass overrides the constructor, it must make sure it invokes the " +"base class constructor (:meth:`Process.__init__`) before doing anything else " +"to the process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:475 ../Doc/library/threading.rst:232 +msgid "Added the *daemon* argument." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:480 +msgid "Method representing the process's activity." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:482 +msgid "" +"You may override this method in a subclass. The standard :meth:`run` method " +"invokes the callable object passed to the object's constructor as the target " +"argument, if any, with sequential and keyword arguments taken from the " +"*args* and *kwargs* arguments, respectively." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:489 +msgid "Start the process's activity." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:491 +msgid "" +"This must be called at most once per process object. It arranges for the " +"object's :meth:`run` method to be invoked in a separate process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:496 +msgid "" +"If the optional argument *timeout* is ``None`` (the default), the method " +"blocks until the process whose :meth:`join` method is called terminates. If " +"*timeout* is a positive number, it blocks at most *timeout* seconds. Note " +"that the method returns ``None`` if its process terminates or if the method " +"times out. Check the process's :attr:`exitcode` to determine if it " +"terminated." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:503 +msgid "A process can be joined many times." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:505 +msgid "" +"A process cannot join itself because this would cause a deadlock. It is an " +"error to attempt to join a process before it has been started." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:510 +msgid "" +"The process's name. The name is a string used for identification purposes " +"only. It has no semantics. Multiple processes may be given the same name." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:514 +msgid "" +"The initial name is set by the constructor. If no explicit name is provided " +"to the constructor, a name of the form 'Process-N\\ :sub:`1`:N\\ :sub:" +"`2`:...:N\\ :sub:`k`' is constructed, where each N\\ :sub:`k` is the N-th " +"child of its parent." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:521 +msgid "Return whether the process is alive." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:523 +msgid "" +"Roughly, a process object is alive from the moment the :meth:`start` method " +"returns until the child process terminates." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:528 +msgid "" +"The process's daemon flag, a Boolean value. This must be set before :meth:" +"`start` is called." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:531 +msgid "The initial value is inherited from the creating process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:533 +msgid "" +"When a process exits, it attempts to terminate all of its daemonic child " +"processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:536 +msgid "" +"Note that a daemonic process is not allowed to create child processes. " +"Otherwise a daemonic process would leave its children orphaned if it gets " +"terminated when its parent process exits. Additionally, these are **not** " +"Unix daemons or services, they are normal processes that will be terminated " +"(and not joined) if non-daemonic processes have exited." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:542 +msgid "" +"In addition to the :class:`threading.Thread` API, :class:`Process` objects " +"also support the following attributes and methods:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:547 +msgid "" +"Return the process ID. Before the process is spawned, this will be ``None``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:552 +msgid "" +"The child's exit code. This will be ``None`` if the process has not yet " +"terminated. A negative value *-N* indicates that the child was terminated " +"by signal *N*." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:558 +msgid "The process's authentication key (a byte string)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:560 +msgid "" +"When :mod:`multiprocessing` is initialized the main process is assigned a " +"random string using :func:`os.urandom`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:563 +msgid "" +"When a :class:`Process` object is created, it will inherit the " +"authentication key of its parent process, although this may be changed by " +"setting :attr:`authkey` to another byte string." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:567 +msgid "See :ref:`multiprocessing-auth-keys`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:571 +msgid "" +"A numeric handle of a system object which will become \"ready\" when the " +"process ends." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:574 +msgid "" +"You can use this value if you want to wait on several events at once using :" +"func:`multiprocessing.connection.wait`. Otherwise calling :meth:`join()` is " +"simpler." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:578 +msgid "" +"On Windows, this is an OS handle usable with the ``WaitForSingleObject`` and " +"``WaitForMultipleObjects`` family of API calls. On Unix, this is a file " +"descriptor usable with primitives from the :mod:`select` module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:586 +msgid "" +"Terminate the process. On Unix this is done using the ``SIGTERM`` signal; " +"on Windows :c:func:`TerminateProcess` is used. Note that exit handlers and " +"finally clauses, etc., will not be executed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:590 +msgid "" +"Note that descendant processes of the process will *not* be terminated -- " +"they will simply become orphaned." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:595 +msgid "" +"If this method is used when the associated process is using a pipe or queue " +"then the pipe or queue is liable to become corrupted and may become unusable " +"by other process. Similarly, if the process has acquired a lock or " +"semaphore etc. then terminating it is liable to cause other processes to " +"deadlock." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:601 +msgid "" +"Note that the :meth:`start`, :meth:`join`, :meth:`is_alive`, :meth:" +"`terminate` and :attr:`exitcode` methods should only be called by the " +"process that created the process object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:605 +msgid "Example usage of some of the methods of :class:`Process`:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:625 +msgid "The base class of all :mod:`multiprocessing` exceptions." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:629 +msgid "" +"Exception raised by :meth:`Connection.recv_bytes_into()` when the supplied " +"buffer object is too small for the message read." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:632 +msgid "" +"If ``e`` is an instance of :exc:`BufferTooShort` then ``e.args[0]`` will " +"give the message as a byte string." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:637 +msgid "Raised when there is an authentication error." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:641 +msgid "Raised by methods with a timeout when the timeout expires." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:644 +msgid "Pipes and Queues" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:646 +msgid "" +"When using multiple processes, one generally uses message passing for " +"communication between processes and avoids having to use any synchronization " +"primitives like locks." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:650 +msgid "" +"For passing messages one can use :func:`Pipe` (for a connection between two " +"processes) or a queue (which allows multiple producers and consumers)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:653 +msgid "" +"The :class:`Queue`, :class:`SimpleQueue` and :class:`JoinableQueue` types " +"are multi-producer, multi-consumer :abbr:`FIFO (first-in, first-out)` queues " +"modelled on the :class:`queue.Queue` class in the standard library. They " +"differ in that :class:`Queue` lacks the :meth:`~queue.Queue.task_done` and :" +"meth:`~queue.Queue.join` methods introduced into Python 2.5's :class:`queue." +"Queue` class." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:660 +msgid "" +"If you use :class:`JoinableQueue` then you **must** call :meth:" +"`JoinableQueue.task_done` for each task removed from the queue or else the " +"semaphore used to count the number of unfinished tasks may eventually " +"overflow, raising an exception." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:665 +msgid "" +"Note that one can also create a shared queue by using a manager object -- " +"see :ref:`multiprocessing-managers`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:670 +msgid "" +":mod:`multiprocessing` uses the usual :exc:`queue.Empty` and :exc:`queue." +"Full` exceptions to signal a timeout. They are not available in the :mod:" +"`multiprocessing` namespace so you need to import them from :mod:`queue`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:677 +msgid "" +"When an object is put on a queue, the object is pickled and a background " +"thread later flushes the pickled data to an underlying pipe. This has some " +"consequences which are a little surprising, but should not cause any " +"practical difficulties -- if they really bother you then you can instead use " +"a queue created with a :ref:`manager `." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:684 +msgid "" +"After putting an object on an empty queue there may be an infinitesimal " +"delay before the queue's :meth:`~Queue.empty` method returns :const:`False` " +"and :meth:`~Queue.get_nowait` can return without raising :exc:`queue.Empty`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:689 +msgid "" +"If multiple processes are enqueuing objects, it is possible for the objects " +"to be received at the other end out-of-order. However, objects enqueued by " +"the same process will always be in the expected order with respect to each " +"other." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:696 +msgid "" +"If a process is killed using :meth:`Process.terminate` or :func:`os.kill` " +"while it is trying to use a :class:`Queue`, then the data in the queue is " +"likely to become corrupted. This may cause any other process to get an " +"exception when it tries to use the queue later on." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:703 +msgid "" +"As mentioned above, if a child process has put items on a queue (and it has " +"not used :meth:`JoinableQueue.cancel_join_thread `), then that process will not terminate until all " +"buffered items have been flushed to the pipe." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:708 +msgid "" +"This means that if you try joining that process you may get a deadlock " +"unless you are sure that all items which have been put on the queue have " +"been consumed. Similarly, if the child process is non-daemonic then the " +"parent process may hang on exit when it tries to join all its non-daemonic " +"children." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:713 +msgid "" +"Note that a queue created using a manager does not have this issue. See :" +"ref:`multiprocessing-programming`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:716 +msgid "" +"For an example of the usage of queues for interprocess communication see :" +"ref:`multiprocessing-examples`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:722 +msgid "" +"Returns a pair ``(conn1, conn2)`` of :class:`Connection` objects " +"representing the ends of a pipe." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:725 +msgid "" +"If *duplex* is ``True`` (the default) then the pipe is bidirectional. If " +"*duplex* is ``False`` then the pipe is unidirectional: ``conn1`` can only be " +"used for receiving messages and ``conn2`` can only be used for sending " +"messages." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:733 +msgid "" +"Returns a process shared queue implemented using a pipe and a few locks/" +"semaphores. When a process first puts an item on the queue a feeder thread " +"is started which transfers objects from a buffer into the pipe." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:737 +msgid "" +"The usual :exc:`queue.Empty` and :exc:`queue.Full` exceptions from the " +"standard library's :mod:`queue` module are raised to signal timeouts." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:740 +msgid "" +":class:`Queue` implements all the methods of :class:`queue.Queue` except " +"for :meth:`~queue.Queue.task_done` and :meth:`~queue.Queue.join`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:745 +msgid "" +"Return the approximate size of the queue. Because of multithreading/" +"multiprocessing semantics, this number is not reliable." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:748 +msgid "" +"Note that this may raise :exc:`NotImplementedError` on Unix platforms like " +"Mac OS X where ``sem_getvalue()`` is not implemented." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:753 +msgid "" +"Return ``True`` if the queue is empty, ``False`` otherwise. Because of " +"multithreading/multiprocessing semantics, this is not reliable." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:758 +msgid "" +"Return ``True`` if the queue is full, ``False`` otherwise. Because of " +"multithreading/multiprocessing semantics, this is not reliable." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:763 +msgid "" +"Put obj into the queue. If the optional argument *block* is ``True`` (the " +"default) and *timeout* is ``None`` (the default), block if necessary until a " +"free slot is available. If *timeout* is a positive number, it blocks at " +"most *timeout* seconds and raises the :exc:`queue.Full` exception if no free " +"slot was available within that time. Otherwise (*block* is ``False``), put " +"an item on the queue if a free slot is immediately available, else raise " +"the :exc:`queue.Full` exception (*timeout* is ignored in that case)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:774 +msgid "Equivalent to ``put(obj, False)``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:778 +msgid "" +"Remove and return an item from the queue. If optional args *block* is " +"``True`` (the default) and *timeout* is ``None`` (the default), block if " +"necessary until an item is available. If *timeout* is a positive number, it " +"blocks at most *timeout* seconds and raises the :exc:`queue.Empty` exception " +"if no item was available within that time. Otherwise (block is ``False``), " +"return an item if one is immediately available, else raise the :exc:`queue." +"Empty` exception (*timeout* is ignored in that case)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:788 ../Doc/library/queue.rst:134 +msgid "Equivalent to ``get(False)``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:790 +msgid "" +":class:`multiprocessing.Queue` has a few additional methods not found in :" +"class:`queue.Queue`. These methods are usually unnecessary for most code:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:796 +msgid "" +"Indicate that no more data will be put on this queue by the current " +"process. The background thread will quit once it has flushed all buffered " +"data to the pipe. This is called automatically when the queue is garbage " +"collected." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:803 +msgid "" +"Join the background thread. This can only be used after :meth:`close` has " +"been called. It blocks until the background thread exits, ensuring that all " +"data in the buffer has been flushed to the pipe." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:807 +msgid "" +"By default if a process is not the creator of the queue then on exit it will " +"attempt to join the queue's background thread. The process can call :meth:" +"`cancel_join_thread` to make :meth:`join_thread` do nothing." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:813 +msgid "" +"Prevent :meth:`join_thread` from blocking. In particular, this prevents the " +"background thread from being joined automatically when the process exits -- " +"see :meth:`join_thread`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:817 +msgid "" +"A better name for this method might be ``allow_exit_without_flush()``. It " +"is likely to cause enqueued data to lost, and you almost certainly will not " +"need to use it. It is really only there if you need the current process to " +"exit immediately without waiting to flush enqueued data to the underlying " +"pipe, and you don't care about lost data." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:826 +msgid "" +"This class's functionality requires a functioning shared semaphore " +"implementation on the host operating system. Without one, the functionality " +"in this class will be disabled, and attempts to instantiate a :class:`Queue` " +"will result in an :exc:`ImportError`. See :issue:`3770` for additional " +"information. The same holds true for any of the specialized queue types " +"listed below." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:835 +msgid "" +"It is a simplified :class:`Queue` type, very close to a locked :class:`Pipe`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:847 +msgid "Put *item* into the queue." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:852 +msgid "" +":class:`JoinableQueue`, a :class:`Queue` subclass, is a queue which " +"additionally has :meth:`task_done` and :meth:`join` methods." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:857 +msgid "" +"Indicate that a formerly enqueued task is complete. Used by queue " +"consumers. For each :meth:`~Queue.get` used to fetch a task, a subsequent " +"call to :meth:`task_done` tells the queue that the processing on the task is " +"complete." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:862 +msgid "" +"If a :meth:`~queue.Queue.join` is currently blocking, it will resume when " +"all items have been processed (meaning that a :meth:`task_done` call was " +"received for every item that had been :meth:`~Queue.put` into the queue)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:866 ../Doc/library/queue.rst:150 +msgid "" +"Raises a :exc:`ValueError` if called more times than there were items placed " +"in the queue." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:874 +msgid "" +"The count of unfinished tasks goes up whenever an item is added to the " +"queue. The count goes down whenever a consumer calls :meth:`task_done` to " +"indicate that the item was retrieved and all work on it is complete. When " +"the count of unfinished tasks drops to zero, :meth:`~queue.Queue.join` " +"unblocks." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:886 +msgid "Return list of all live children of the current process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:888 +msgid "" +"Calling this has the side effect of \"joining\" any processes which have " +"already finished." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:893 +msgid "Return the number of CPUs in the system." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:895 ../Doc/library/os.rst:3819 +msgid "" +"This number is not equivalent to the number of CPUs the current process can " +"use. The number of usable CPUs can be obtained with ``len(os." +"sched_getaffinity(0))``" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:899 +msgid "May raise :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:902 +msgid ":func:`os.cpu_count`" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:906 +msgid "" +"Return the :class:`Process` object corresponding to the current process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:908 +msgid "An analogue of :func:`threading.current_thread`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:912 +msgid "" +"Add support for when a program which uses :mod:`multiprocessing` has been " +"frozen to produce a Windows executable. (Has been tested with **py2exe**, " +"**PyInstaller** and **cx_Freeze**.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:916 +msgid "" +"One needs to call this function straight after the ``if __name__ == " +"'__main__'`` line of the main module. For example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:928 +msgid "" +"If the ``freeze_support()`` line is omitted then trying to run the frozen " +"executable will raise :exc:`RuntimeError`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:931 +msgid "" +"Calling ``freeze_support()`` has no effect when invoked on any operating " +"system other than Windows. In addition, if the module is being run normally " +"by the Python interpreter on Windows (the program has not been frozen), then " +"``freeze_support()`` has no effect." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:938 +msgid "" +"Returns a list of the supported start methods, the first of which is the " +"default. The possible start methods are ``'fork'``, ``'spawn'`` and " +"``'forkserver'``. On Windows only ``'spawn'`` is available. On Unix " +"``'fork'`` and ``'spawn'`` are always supported, with ``'fork'`` being the " +"default." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:948 +msgid "" +"Return a context object which has the same attributes as the :mod:" +"`multiprocessing` module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:951 +msgid "" +"If *method* is *None* then the default context is returned. Otherwise " +"*method* should be ``'fork'``, ``'spawn'``, ``'forkserver'``. :exc:" +"`ValueError` is raised if the specified start method is not available." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:960 +msgid "Return the name of start method used for starting processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:962 +msgid "" +"If the start method has not been fixed and *allow_none* is false, then the " +"start method is fixed to the default and the name is returned. If the start " +"method has not been fixed and *allow_none* is true then *None* is returned." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:967 +msgid "" +"The return value can be ``'fork'``, ``'spawn'``, ``'forkserver'`` or " +"*None*. ``'fork'`` is the default on Unix, while ``'spawn'`` is the default " +"on Windows." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:975 +msgid "" +"Sets the path of the Python interpreter to use when starting a child " +"process. (By default :data:`sys.executable` is used). Embedders will " +"probably need to do some thing like ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:981 +msgid "before they can create child processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:983 +msgid "Now supported on Unix when the ``'spawn'`` start method is used." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:988 +msgid "" +"Set the method which should be used to start child processes. *method* can " +"be ``'fork'``, ``'spawn'`` or ``'forkserver'``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:991 +msgid "" +"Note that this should be called at most once, and it should be protected " +"inside the ``if __name__ == '__main__'`` clause of the main module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:999 +msgid "" +":mod:`multiprocessing` contains no analogues of :func:`threading." +"active_count`, :func:`threading.enumerate`, :func:`threading.settrace`, :" +"func:`threading.setprofile`, :class:`threading.Timer`, or :class:`threading." +"local`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1006 ../Doc/library/sqlite3.rst:269 +msgid "Connection Objects" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1008 +msgid "" +"Connection objects allow the sending and receiving of picklable objects or " +"strings. They can be thought of as message oriented connected sockets." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1011 +msgid "" +"Connection objects are usually created using :func:`Pipe` -- see also :ref:" +"`multiprocessing-listeners-clients`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1018 +msgid "" +"Send an object to the other end of the connection which should be read " +"using :meth:`recv`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1021 +msgid "" +"The object must be picklable. Very large pickles (approximately 32 MB+, " +"though it depends on the OS) may raise a :exc:`ValueError` exception." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1026 +msgid "" +"Return an object sent from the other end of the connection using :meth:" +"`send`. Blocks until there its something to receive. Raises :exc:" +"`EOFError` if there is nothing left to receive and the other end was closed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1033 +msgid "Return the file descriptor or handle used by the connection." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1037 ../Doc/library/telnetlib.rst:160 +msgid "Close the connection." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1039 +msgid "This is called automatically when the connection is garbage collected." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1043 +msgid "Return whether there is any data available to be read." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1045 +msgid "" +"If *timeout* is not specified then it will return immediately. If *timeout* " +"is a number then this specifies the maximum time in seconds to block. If " +"*timeout* is ``None`` then an infinite timeout is used." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1049 +msgid "" +"Note that multiple connection objects may be polled at once by using :func:" +"`multiprocessing.connection.wait`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1054 +msgid "Send byte data from a :term:`bytes-like object` as a complete message." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1056 +msgid "" +"If *offset* is given then data is read from that position in *buffer*. If " +"*size* is given then that many bytes will be read from buffer. Very large " +"buffers (approximately 32 MB+, though it depends on the OS) may raise a :exc:" +"`ValueError` exception" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1063 +msgid "" +"Return a complete message of byte data sent from the other end of the " +"connection as a string. Blocks until there is something to receive. Raises :" +"exc:`EOFError` if there is nothing left to receive and the other end has " +"closed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1068 +msgid "" +"If *maxlength* is specified and the message is longer than *maxlength* then :" +"exc:`OSError` is raised and the connection will no longer be readable." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1072 +msgid "" +"This function used to raise :exc:`IOError`, which is now an alias of :exc:" +"`OSError`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1079 +msgid "" +"Read into *buffer* a complete message of byte data sent from the other end " +"of the connection and return the number of bytes in the message. Blocks " +"until there is something to receive. Raises :exc:`EOFError` if there is " +"nothing left to receive and the other end was closed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1085 +msgid "" +"*buffer* must be a writable :term:`bytes-like object`. If *offset* is given " +"then the message will be written into the buffer from that position. Offset " +"must be a non-negative integer less than the length of *buffer* (in bytes)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1090 +msgid "" +"If the buffer is too short then a :exc:`BufferTooShort` exception is raised " +"and the complete message is available as ``e.args[0]`` where ``e`` is the " +"exception instance." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1094 +msgid "" +"Connection objects themselves can now be transferred between processes " +"using :meth:`Connection.send` and :meth:`Connection.recv`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1098 +msgid "" +"Connection objects now support the context management protocol -- see :ref:" +"`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the " +"connection object, and :meth:`~contextmanager.__exit__` calls :meth:`close`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1127 +msgid "" +"The :meth:`Connection.recv` method automatically unpickles the data it " +"receives, which can be a security risk unless you can trust the process " +"which sent the message." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1131 +msgid "" +"Therefore, unless the connection object was produced using :func:`Pipe` you " +"should only use the :meth:`~Connection.recv` and :meth:`~Connection.send` " +"methods after performing some sort of authentication. See :ref:" +"`multiprocessing-auth-keys`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1138 +msgid "" +"If a process is killed while it is trying to read or write to a pipe then " +"the data in the pipe is likely to become corrupted, because it may become " +"impossible to be sure where the message boundaries lie." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1146 +msgid "" +"Generally synchronization primitives are not as necessary in a multiprocess " +"program as they are in a multithreaded program. See the documentation for :" +"mod:`threading` module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1150 +msgid "" +"Note that one can also create synchronization primitives by using a manager " +"object -- see :ref:`multiprocessing-managers`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1155 +msgid "A barrier object: a clone of :class:`threading.Barrier`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1161 +msgid "" +"A bounded semaphore object: a close analog of :class:`threading." +"BoundedSemaphore`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1164 +#: ../Doc/library/multiprocessing.rst:1302 +msgid "" +"A solitary difference from its close analog exists: its ``acquire`` method's " +"first argument is named *block*, as is consistent with :meth:`Lock.acquire`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1168 +msgid "" +"On Mac OS X, this is indistinguishable from :class:`Semaphore` because " +"``sem_getvalue()`` is not implemented on that platform." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1173 +msgid "A condition variable: an alias for :class:`threading.Condition`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1175 +msgid "" +"If *lock* is specified then it should be a :class:`Lock` or :class:`RLock` " +"object from :mod:`multiprocessing`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1178 +#: ../Doc/library/multiprocessing.rst:1712 +msgid "The :meth:`~threading.Condition.wait_for` method was added." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1183 +msgid "A clone of :class:`threading.Event`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1188 +msgid "" +"A non-recursive lock object: a close analog of :class:`threading.Lock`. Once " +"a process or thread has acquired a lock, subsequent attempts to acquire it " +"from any process or thread will block until it is released; any process or " +"thread may release it. The concepts and behaviors of :class:`threading." +"Lock` as it applies to threads are replicated here in :class:" +"`multiprocessing.Lock` as it applies to either processes or threads, except " +"as noted." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1196 +msgid "" +"Note that :class:`Lock` is actually a factory function which returns an " +"instance of ``multiprocessing.synchronize.Lock`` initialized with a default " +"context." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1200 +msgid "" +":class:`Lock` supports the :term:`context manager` protocol and thus may be " +"used in :keyword:`with` statements." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1205 +#: ../Doc/library/multiprocessing.rst:1256 ../Doc/library/threading.rst:380 +#: ../Doc/library/threading.rst:454 +msgid "Acquire a lock, blocking or non-blocking." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1207 +msgid "" +"With the *block* argument set to ``True`` (the default), the method call " +"will block until the lock is in an unlocked state, then set it to locked and " +"return ``True``. Note that the name of this first argument differs from " +"that in :meth:`threading.Lock.acquire`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1212 +msgid "" +"With the *block* argument set to ``False``, the method call does not block. " +"If the lock is currently in a locked state, return ``False``; otherwise set " +"the lock to a locked state and return ``True``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1216 +msgid "" +"When invoked with a positive, floating-point value for *timeout*, block for " +"at most the number of seconds specified by *timeout* as long as the lock can " +"not be acquired. Invocations with a negative value for *timeout* are " +"equivalent to a *timeout* of zero. Invocations with a *timeout* value of " +"``None`` (the default) set the timeout period to infinite. Note that the " +"treatment of negative or ``None`` values for *timeout* differs from the " +"implemented behavior in :meth:`threading.Lock.acquire`. The *timeout* " +"argument has no practical implications if the *block* argument is set to " +"``False`` and is thus ignored. Returns ``True`` if the lock has been " +"acquired or ``False`` if the timeout period has elapsed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1231 +msgid "" +"Release a lock. This can be called from any process or thread, not only the " +"process or thread which originally acquired the lock." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1234 +msgid "" +"Behavior is the same as in :meth:`threading.Lock.release` except that when " +"invoked on an unlocked lock, a :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1240 +msgid "" +"A recursive lock object: a close analog of :class:`threading.RLock`. A " +"recursive lock must be released by the process or thread that acquired it. " +"Once a process or thread has acquired a recursive lock, the same process or " +"thread may acquire it again without blocking; that process or thread must " +"release it once for each time it has been acquired." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1246 +msgid "" +"Note that :class:`RLock` is actually a factory function which returns an " +"instance of ``multiprocessing.synchronize.RLock`` initialized with a default " +"context." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1250 +msgid "" +":class:`RLock` supports the :term:`context manager` protocol and thus may be " +"used in :keyword:`with` statements." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1258 +msgid "" +"When invoked with the *block* argument set to ``True``, block until the lock " +"is in an unlocked state (not owned by any process or thread) unless the lock " +"is already owned by the current process or thread. The current process or " +"thread then takes ownership of the lock (if it does not already have " +"ownership) and the recursion level inside the lock increments by one, " +"resulting in a return value of ``True``. Note that there are several " +"differences in this first argument's behavior compared to the implementation " +"of :meth:`threading.RLock.acquire`, starting with the name of the argument " +"itself." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1268 +msgid "" +"When invoked with the *block* argument set to ``False``, do not block. If " +"the lock has already been acquired (and thus is owned) by another process or " +"thread, the current process or thread does not take ownership and the " +"recursion level within the lock is not changed, resulting in a return value " +"of ``False``. If the lock is in an unlocked state, the current process or " +"thread takes ownership and the recursion level is incremented, resulting in " +"a return value of ``True``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1276 +msgid "" +"Use and behaviors of the *timeout* argument are the same as in :meth:`Lock." +"acquire`. Note that some of these behaviors of *timeout* differ from the " +"implemented behaviors in :meth:`threading.RLock.acquire`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1283 +msgid "" +"Release a lock, decrementing the recursion level. If after the decrement " +"the recursion level is zero, reset the lock to unlocked (not owned by any " +"process or thread) and if any other processes or threads are blocked waiting " +"for the lock to become unlocked, allow exactly one of them to proceed. If " +"after the decrement the recursion level is still nonzero, the lock remains " +"locked and owned by the calling process or thread." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1291 +msgid "" +"Only call this method when the calling process or thread owns the lock. An :" +"exc:`AssertionError` is raised if this method is called by a process or " +"thread other than the owner or if the lock is in an unlocked (unowned) " +"state. Note that the type of exception raised in this situation differs " +"from the implemented behavior in :meth:`threading.RLock.release`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1300 +msgid "A semaphore object: a close analog of :class:`threading.Semaphore`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1307 +msgid "" +"On Mac OS X, ``sem_timedwait`` is unsupported, so calling ``acquire()`` with " +"a timeout will emulate that function's behavior using a sleeping loop." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1312 +msgid "" +"If the SIGINT signal generated by :kbd:`Ctrl-C` arrives while the main " +"thread is blocked by a call to :meth:`BoundedSemaphore.acquire`, :meth:`Lock." +"acquire`, :meth:`RLock.acquire`, :meth:`Semaphore.acquire`, :meth:`Condition." +"acquire` or :meth:`Condition.wait` then the call will be immediately " +"interrupted and :exc:`KeyboardInterrupt` will be raised." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1318 +msgid "" +"This differs from the behaviour of :mod:`threading` where SIGINT will be " +"ignored while the equivalent blocking calls are in progress." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1323 +msgid "" +"Some of this package's functionality requires a functioning shared semaphore " +"implementation on the host operating system. Without one, the :mod:" +"`multiprocessing.synchronize` module will be disabled, and attempts to " +"import it will result in an :exc:`ImportError`. See :issue:`3770` for " +"additional information." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1331 +msgid "Shared :mod:`ctypes` Objects" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1333 +msgid "" +"It is possible to create shared objects using shared memory which can be " +"inherited by child processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1338 +msgid "" +"Return a :mod:`ctypes` object allocated from shared memory. By default the " +"return value is actually a synchronized wrapper for the object. The object " +"itself can be accessed via the *value* attribute of a :class:`Value`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1342 +#: ../Doc/library/multiprocessing.rst:1429 +msgid "" +"*typecode_or_type* determines the type of the returned object: it is either " +"a ctypes type or a one character typecode of the kind used by the :mod:" +"`array` module. *\\*args* is passed on to the constructor for the type." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1346 +msgid "" +"If *lock* is ``True`` (the default) then a new recursive lock object is " +"created to synchronize access to the value. If *lock* is a :class:`Lock` " +"or :class:`RLock` object then that will be used to synchronize access to the " +"value. If *lock* is ``False`` then access to the returned object will not " +"be automatically protected by a lock, so it will not necessarily be " +"\"process-safe\"." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1353 +msgid "" +"Operations like ``+=`` which involve a read and write are not atomic. So " +"if, for instance, you want to atomically increment a shared value it is " +"insufficient to just do ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1359 +msgid "" +"Assuming the associated lock is recursive (which it is by default) you can " +"instead do ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1365 +#: ../Doc/library/multiprocessing.rst:1455 +#: ../Doc/library/multiprocessing.rst:1470 +msgid "Note that *lock* is a keyword-only argument." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1369 +msgid "" +"Return a ctypes array allocated from shared memory. By default the return " +"value is actually a synchronized wrapper for the array." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1372 +msgid "" +"*typecode_or_type* determines the type of the elements of the returned " +"array: it is either a ctypes type or a one character typecode of the kind " +"used by the :mod:`array` module. If *size_or_initializer* is an integer, " +"then it determines the length of the array, and the array will be initially " +"zeroed. Otherwise, *size_or_initializer* is a sequence which is used to " +"initialize the array and whose length determines the length of the array." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1379 +msgid "" +"If *lock* is ``True`` (the default) then a new lock object is created to " +"synchronize access to the value. If *lock* is a :class:`Lock` or :class:" +"`RLock` object then that will be used to synchronize access to the value. " +"If *lock* is ``False`` then access to the returned object will not be " +"automatically protected by a lock, so it will not necessarily be \"process-" +"safe\"." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1386 +msgid "Note that *lock* is a keyword only argument." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1388 +msgid "" +"Note that an array of :data:`ctypes.c_char` has *value* and *raw* attributes " +"which allow one to use it to store and retrieve strings." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1393 +msgid "The :mod:`multiprocessing.sharedctypes` module" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1398 +msgid "" +"The :mod:`multiprocessing.sharedctypes` module provides functions for " +"allocating :mod:`ctypes` objects from shared memory which can be inherited " +"by child processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1404 +msgid "" +"Although it is possible to store a pointer in shared memory remember that " +"this will refer to a location in the address space of a specific process. " +"However, the pointer is quite likely to be invalid in the context of a " +"second process and trying to dereference the pointer from the second process " +"may cause a crash." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1412 +msgid "Return a ctypes array allocated from shared memory." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1414 +msgid "" +"*typecode_or_type* determines the type of the elements of the returned " +"array: it is either a ctypes type or a one character typecode of the kind " +"used by the :mod:`array` module. If *size_or_initializer* is an integer " +"then it determines the length of the array, and the array will be initially " +"zeroed. Otherwise *size_or_initializer* is a sequence which is used to " +"initialize the array and whose length determines the length of the array." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1421 +msgid "" +"Note that setting and getting an element is potentially non-atomic -- use :" +"func:`Array` instead to make sure that access is automatically synchronized " +"using a lock." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1427 +msgid "Return a ctypes object allocated from shared memory." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1433 +msgid "" +"Note that setting and getting the value is potentially non-atomic -- use :" +"func:`Value` instead to make sure that access is automatically synchronized " +"using a lock." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1437 +msgid "" +"Note that an array of :data:`ctypes.c_char` has ``value`` and ``raw`` " +"attributes which allow one to use it to store and retrieve strings -- see " +"documentation for :mod:`ctypes`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1443 +msgid "" +"The same as :func:`RawArray` except that depending on the value of *lock* a " +"process-safe synchronization wrapper may be returned instead of a raw ctypes " +"array." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1447 +#: ../Doc/library/multiprocessing.rst:1463 +msgid "" +"If *lock* is ``True`` (the default) then a new lock object is created to " +"synchronize access to the value. If *lock* is a :class:`~multiprocessing." +"Lock` or :class:`~multiprocessing.RLock` object then that will be used to " +"synchronize access to the value. If *lock* is ``False`` then access to the " +"returned object will not be automatically protected by a lock, so it will " +"not necessarily be \"process-safe\"." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1459 +msgid "" +"The same as :func:`RawValue` except that depending on the value of *lock* a " +"process-safe synchronization wrapper may be returned instead of a raw ctypes " +"object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1474 +msgid "" +"Return a ctypes object allocated from shared memory which is a copy of the " +"ctypes object *obj*." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1479 +msgid "" +"Return a process-safe wrapper object for a ctypes object which uses *lock* " +"to synchronize access. If *lock* is ``None`` (the default) then a :class:" +"`multiprocessing.RLock` object is created automatically." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1483 +msgid "" +"A synchronized wrapper will have two methods in addition to those of the " +"object it wraps: :meth:`get_obj` returns the wrapped object and :meth:" +"`get_lock` returns the lock object used for synchronization." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1487 +msgid "" +"Note that accessing the ctypes object through the wrapper can be a lot " +"slower than accessing the raw ctypes object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1490 +msgid "Synchronized objects support the :term:`context manager` protocol." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1494 +msgid "" +"The table below compares the syntax for creating shared ctypes objects from " +"shared memory with the normal ctypes syntax. (In the table ``MyStruct`` is " +"some subclass of :class:`ctypes.Structure`.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1499 +msgid "ctypes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1499 +msgid "sharedctypes using type" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1499 +msgid "sharedctypes using typecode" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1501 +msgid "c_double(2.4)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1501 +msgid "RawValue(c_double, 2.4)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1501 +msgid "RawValue('d', 2.4)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1502 +msgid "MyStruct(4, 6)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1502 +msgid "RawValue(MyStruct, 4, 6)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1503 +msgid "(c_short * 7)()" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1503 +msgid "RawArray(c_short, 7)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1503 +msgid "RawArray('h', 7)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1504 +msgid "(c_int * 3)(9, 2, 8)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1504 +msgid "RawArray(c_int, (9, 2, 8))" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1504 +msgid "RawArray('i', (9, 2, 8))" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1508 +msgid "" +"Below is an example where a number of ctypes objects are modified by a child " +"process::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1546 +msgid "The results printed are ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1559 +msgid "Managers" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1561 +msgid "" +"Managers provide a way to create data which can be shared between different " +"processes, including sharing over a network between processes running on " +"different machines. A manager object controls a server process which manages " +"*shared objects*. Other processes can access the shared objects by using " +"proxies." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1569 +msgid "" +"Returns a started :class:`~multiprocessing.managers.SyncManager` object " +"which can be used for sharing objects between processes. The returned " +"manager object corresponds to a spawned child process and has methods which " +"will create shared objects and return corresponding proxies." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1577 +msgid "" +"Manager processes will be shutdown as soon as they are garbage collected or " +"their parent process exits. The manager classes are defined in the :mod:" +"`multiprocessing.managers` module:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1583 +msgid "Create a BaseManager object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1585 +msgid "" +"Once created one should call :meth:`start` or ``get_server()." +"serve_forever()`` to ensure that the manager object refers to a started " +"manager process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1588 +msgid "" +"*address* is the address on which the manager process listens for new " +"connections. If *address* is ``None`` then an arbitrary one is chosen." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1591 +msgid "" +"*authkey* is the authentication key which will be used to check the validity " +"of incoming connections to the server process. If *authkey* is ``None`` " +"then ``current_process().authkey`` is used. Otherwise *authkey* is used and " +"it must be a byte string." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1598 +msgid "" +"Start a subprocess to start the manager. If *initializer* is not ``None`` " +"then the subprocess will call ``initializer(*initargs)`` when it starts." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1603 +msgid "" +"Returns a :class:`Server` object which represents the actual server under " +"the control of the Manager. The :class:`Server` object supports the :meth:" +"`serve_forever` method::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1612 +msgid ":class:`Server` additionally has an :attr:`address` attribute." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1616 +msgid "Connect a local manager object to a remote manager process::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1624 +msgid "" +"Stop the process used by the manager. This is only available if :meth:" +"`start` has been used to start the server process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1627 +msgid "This can be called multiple times." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1631 +msgid "" +"A classmethod which can be used for registering a type or callable with the " +"manager class." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1634 +msgid "" +"*typeid* is a \"type identifier\" which is used to identify a particular " +"type of shared object. This must be a string." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1637 +msgid "" +"*callable* is a callable used for creating objects for this type " +"identifier. If a manager instance will be connected to the server using " +"the :meth:`connect` method, or if the *create_method* argument is ``False`` " +"then this can be left as ``None``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1643 +msgid "" +"*proxytype* is a subclass of :class:`BaseProxy` which is used to create " +"proxies for shared objects with this *typeid*. If ``None`` then a proxy " +"class is created automatically." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1647 +msgid "" +"*exposed* is used to specify a sequence of method names which proxies for " +"this typeid should be allowed to access using :meth:`BaseProxy." +"_callmethod`. (If *exposed* is ``None`` then :attr:`proxytype._exposed_` is " +"used instead if it exists.) In the case where no exposed list is specified, " +"all \"public methods\" of the shared object will be accessible. (Here a " +"\"public method\" means any attribute which has a :meth:`~object.__call__` " +"method and whose name does not begin with ``'_'``.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1656 +msgid "" +"*method_to_typeid* is a mapping used to specify the return type of those " +"exposed methods which should return a proxy. It maps method names to typeid " +"strings. (If *method_to_typeid* is ``None`` then :attr:`proxytype." +"_method_to_typeid_` is used instead if it exists.) If a method's name is " +"not a key of this mapping or if the mapping is ``None`` then the object " +"returned by the method will be copied by value." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1663 +msgid "" +"*create_method* determines whether a method should be created with name " +"*typeid* which can be used to tell the server process to create a new shared " +"object and return a proxy for it. By default it is ``True``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1667 +msgid ":class:`BaseManager` instances also have one read-only property:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1671 +msgid "The address used by the manager." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1673 +msgid "" +"Manager objects support the context management protocol -- see :ref:" +"`typecontextmanager`. :meth:`~contextmanager.__enter__` starts the server " +"process (if it has not already started) and then returns the manager " +"object. :meth:`~contextmanager.__exit__` calls :meth:`shutdown`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1679 +msgid "" +"In previous versions :meth:`~contextmanager.__enter__` did not start the " +"manager's server process if it was not already started." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1684 +msgid "" +"A subclass of :class:`BaseManager` which can be used for the synchronization " +"of processes. Objects of this type are returned by :func:`multiprocessing." +"Manager`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1688 +msgid "" +"Its methods create and return :ref:`multiprocessing-proxy_objects` for a " +"number of commonly used data types to be synchronized across processes. This " +"notably includes shared lists and dictionaries." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1694 +msgid "" +"Create a shared :class:`threading.Barrier` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1701 +msgid "" +"Create a shared :class:`threading.BoundedSemaphore` object and return a " +"proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1706 +msgid "" +"Create a shared :class:`threading.Condition` object and return a proxy for " +"it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1709 +msgid "" +"If *lock* is supplied then it should be a proxy for a :class:`threading." +"Lock` or :class:`threading.RLock` object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1717 +msgid "" +"Create a shared :class:`threading.Event` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1721 +msgid "" +"Create a shared :class:`threading.Lock` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1725 +msgid "Create a shared :class:`Namespace` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1729 +msgid "Create a shared :class:`queue.Queue` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1733 +msgid "" +"Create a shared :class:`threading.RLock` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1737 +msgid "" +"Create a shared :class:`threading.Semaphore` object and return a proxy for " +"it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1742 +msgid "Create an array and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1746 +msgid "" +"Create an object with a writable ``value`` attribute and return a proxy for " +"it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1753 +msgid "Create a shared :class:`dict` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1758 +msgid "Create a shared :class:`list` object and return a proxy for it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1760 +msgid "" +"Shared objects are capable of being nested. For example, a shared container " +"object such as a shared list can contain other shared objects which will all " +"be managed and synchronized by the :class:`SyncManager`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1767 +msgid "A type that can register with :class:`SyncManager`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1769 +msgid "" +"A namespace object has no public methods, but does have writable attributes. " +"Its representation shows the values of its attributes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1772 +msgid "" +"However, when using a proxy for a namespace object, an attribute beginning " +"with ``'_'`` will be an attribute of the proxy and not an attribute of the " +"referent:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1788 +msgid "Customized managers" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1790 +msgid "" +"To create one's own manager, one creates a subclass of :class:`BaseManager` " +"and uses the :meth:`~BaseManager.register` classmethod to register new types " +"or callables with the manager class. For example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1815 +msgid "Using a remote manager" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1817 +msgid "" +"It is possible to run a manager server on one machine and have clients use " +"it from other machines (assuming that the firewalls involved allow it)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1820 +msgid "" +"Running the following commands creates a server for a single shared queue " +"which remote clients can access::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1832 +msgid "One client can access the server as follows::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1842 +msgid "Another client can also use it::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1853 +msgid "" +"Local processes can also access that queue, using the code from above on the " +"client to access it remotely::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1878 +msgid "Proxy Objects" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1880 +msgid "" +"A proxy is an object which *refers* to a shared object which lives " +"(presumably) in a different process. The shared object is said to be the " +"*referent* of the proxy. Multiple proxy objects may have the same referent." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1884 +msgid "" +"A proxy object has methods which invoke corresponding methods of its " +"referent (although not every method of the referent will necessarily be " +"available through the proxy). In this way, a proxy can be used just like " +"its referent can:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1902 +msgid "" +"Notice that applying :func:`str` to a proxy will return the representation " +"of the referent, whereas applying :func:`repr` will return the " +"representation of the proxy." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1906 +msgid "" +"An important feature of proxy objects is that they are picklable so they can " +"be passed between processes. As such, a referent can contain :ref:" +"`multiprocessing-proxy_objects`. This permits nesting of these managed " +"lists, dicts, and other :ref:`multiprocessing-proxy_objects`:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1922 +msgid "Similarly, dict and list proxies may be nested inside one another::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1935 +msgid "" +"If standard (non-proxy) :class:`list` or :class:`dict` objects are contained " +"in a referent, modifications to those mutable values will not be propagated " +"through the manager because the proxy has no way of knowing when the values " +"contained within are modified. However, storing a value in a container " +"proxy (which triggers a ``__setitem__`` on the proxy object) does propagate " +"through the manager and so to effectively modify such an item, one could re-" +"assign the modified value to the container proxy::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1954 +msgid "" +"This approach is perhaps less convenient than employing nested :ref:" +"`multiprocessing-proxy_objects` for most use cases but also demonstrates a " +"level of control over the synchronization." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1960 +msgid "" +"The proxy types in :mod:`multiprocessing` do nothing to support comparisons " +"by value. So, for instance, we have:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1968 +msgid "" +"One should just use a copy of the referent instead when making comparisons." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1972 +msgid "Proxy objects are instances of subclasses of :class:`BaseProxy`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1976 +msgid "Call and return the result of a method of the proxy's referent." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1978 +msgid "" +"If ``proxy`` is a proxy whose referent is ``obj`` then the expression ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1982 +msgid "will evaluate the expression ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1986 +msgid "in the manager's process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1988 +msgid "" +"The returned value will be a copy of the result of the call or a proxy to a " +"new shared object -- see documentation for the *method_to_typeid* argument " +"of :meth:`BaseManager.register`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1992 +msgid "" +"If an exception is raised by the call, then is re-raised by :meth:" +"`_callmethod`. If some other exception is raised in the manager's process " +"then this is converted into a :exc:`RemoteError` exception and is raised by :" +"meth:`_callmethod`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:1997 +msgid "" +"Note in particular that an exception will be raised if *methodname* has not " +"been *exposed*." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2000 +msgid "An example of the usage of :meth:`_callmethod`:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2016 +msgid "Return a copy of the referent." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2018 +msgid "If the referent is unpicklable then this will raise an exception." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2022 +msgid "Return a representation of the proxy object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2026 +msgid "Return the representation of the referent." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2030 ../Doc/library/optparse.rst:1483 +msgid "Cleanup" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2032 +msgid "" +"A proxy object uses a weakref callback so that when it gets garbage " +"collected it deregisters itself from the manager which owns its referent." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2035 +msgid "" +"A shared object gets deleted from the manager process when there are no " +"longer any proxies referring to it." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2040 +msgid "Process Pools" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2045 +msgid "" +"One can create a pool of processes which will carry out tasks submitted to " +"it with the :class:`Pool` class." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2050 +msgid "" +"A process pool object which controls a pool of worker processes to which " +"jobs can be submitted. It supports asynchronous results with timeouts and " +"callbacks and has a parallel map implementation." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2054 +msgid "" +"*processes* is the number of worker processes to use. If *processes* is " +"``None`` then the number returned by :func:`os.cpu_count` is used." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2057 +msgid "" +"If *initializer* is not ``None`` then each worker process will call " +"``initializer(*initargs)`` when it starts." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2060 +msgid "" +"*maxtasksperchild* is the number of tasks a worker process can complete " +"before it will exit and be replaced with a fresh worker process, to enable " +"unused resources to be freed. The default *maxtasksperchild* is None, which " +"means worker processes will live as long as the pool." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2065 +msgid "" +"*context* can be used to specify the context used for starting the worker " +"processes. Usually a pool is created using the function :func:" +"`multiprocessing.Pool` or the :meth:`Pool` method of a context object. In " +"both cases *context* is set appropriately." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2071 +msgid "" +"Note that the methods of the pool object should only be called by the " +"process which created the pool." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2074 +msgid "*maxtasksperchild*" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2077 +msgid "*context*" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2082 +msgid "" +"Worker processes within a :class:`Pool` typically live for the complete " +"duration of the Pool's work queue. A frequent pattern found in other systems " +"(such as Apache, mod_wsgi, etc) to free resources held by workers is to " +"allow a worker within a pool to complete only a set amount of work before " +"being exiting, being cleaned up and a new process spawned to replace the old " +"one. The *maxtasksperchild* argument to the :class:`Pool` exposes this " +"ability to the end user." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2092 +msgid "" +"Call *func* with arguments *args* and keyword arguments *kwds*. It blocks " +"until the result is ready. Given this blocks, :meth:`apply_async` is better " +"suited for performing work in parallel. Additionally, *func* is only " +"executed in one of the workers of the pool." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2099 +msgid "A variant of the :meth:`apply` method which returns a result object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2101 +#: ../Doc/library/multiprocessing.rst:2126 +msgid "" +"If *callback* is specified then it should be a callable which accepts a " +"single argument. When the result becomes ready *callback* is applied to it, " +"that is unless the call failed, in which case the *error_callback* is " +"applied instead." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2106 +#: ../Doc/library/multiprocessing.rst:2131 +msgid "" +"If *error_callback* is specified then it should be a callable which accepts " +"a single argument. If the target function fails, then the *error_callback* " +"is called with the exception instance." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2110 +#: ../Doc/library/multiprocessing.rst:2135 +msgid "" +"Callbacks should complete immediately since otherwise the thread which " +"handles the results will get blocked." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2115 +msgid "" +"A parallel equivalent of the :func:`map` built-in function (it supports only " +"one *iterable* argument though). It blocks until the result is ready." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2118 +msgid "" +"This method chops the iterable into a number of chunks which it submits to " +"the process pool as separate tasks. The (approximate) size of these chunks " +"can be specified by setting *chunksize* to a positive integer." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2124 +msgid "A variant of the :meth:`.map` method which returns a result object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2140 +msgid "A lazier version of :meth:`map`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2142 +msgid "" +"The *chunksize* argument is the same as the one used by the :meth:`.map` " +"method. For very long iterables using a large value for *chunksize* can " +"make the job complete **much** faster than using the default value of ``1``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2147 +msgid "" +"Also if *chunksize* is ``1`` then the :meth:`!next` method of the iterator " +"returned by the :meth:`imap` method has an optional *timeout* parameter: " +"``next(timeout)`` will raise :exc:`multiprocessing.TimeoutError` if the " +"result cannot be returned within *timeout* seconds." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2154 +msgid "" +"The same as :meth:`imap` except that the ordering of the results from the " +"returned iterator should be considered arbitrary. (Only when there is only " +"one worker process is the order guaranteed to be \"correct\".)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2160 +msgid "" +"Like :meth:`map` except that the elements of the *iterable* are expected to " +"be iterables that are unpacked as arguments." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2163 +msgid "" +"Hence an *iterable* of ``[(1,2), (3, 4)]`` results in ``[func(1,2), " +"func(3,4)]``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2170 +msgid "" +"A combination of :meth:`starmap` and :meth:`map_async` that iterates over " +"*iterable* of iterables and calls *func* with the iterables unpacked. " +"Returns a result object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2178 +msgid "" +"Prevents any more tasks from being submitted to the pool. Once all the " +"tasks have been completed the worker processes will exit." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2183 +msgid "" +"Stops the worker processes immediately without completing outstanding work. " +"When the pool object is garbage collected :meth:`terminate` will be called " +"immediately." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2189 +msgid "" +"Wait for the worker processes to exit. One must call :meth:`close` or :meth:" +"`terminate` before using :meth:`join`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2192 +msgid "" +"Pool objects now support the context management protocol -- see :ref:" +"`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the pool " +"object, and :meth:`~contextmanager.__exit__` calls :meth:`terminate`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2200 +msgid "" +"The class of the result returned by :meth:`Pool.apply_async` and :meth:`Pool." +"map_async`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2205 +msgid "" +"Return the result when it arrives. If *timeout* is not ``None`` and the " +"result does not arrive within *timeout* seconds then :exc:`multiprocessing." +"TimeoutError` is raised. If the remote call raised an exception then that " +"exception will be reraised by :meth:`get`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2212 +msgid "Wait until the result is available or until *timeout* seconds pass." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2216 +msgid "Return whether the call has completed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2220 +msgid "" +"Return whether the call completed without raising an exception. Will raise :" +"exc:`AssertionError` if the result is not ready." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2223 +msgid "The following example demonstrates the use of a pool::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2250 +msgid "Listeners and Clients" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2255 +msgid "" +"Usually message passing between processes is done using queues or by using :" +"class:`~multiprocessing.Connection` objects returned by :func:" +"`~multiprocessing.Pipe`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2259 +msgid "" +"However, the :mod:`multiprocessing.connection` module allows some extra " +"flexibility. It basically gives a high level message oriented API for " +"dealing with sockets or Windows named pipes. It also has support for " +"*digest authentication* using the :mod:`hmac` module, and for polling " +"multiple connections at the same time." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2268 +msgid "" +"Send a randomly generated message to the other end of the connection and " +"wait for a reply." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2271 +msgid "" +"If the reply matches the digest of the message using *authkey* as the key " +"then a welcome message is sent to the other end of the connection. " +"Otherwise :exc:`~multiprocessing.AuthenticationError` is raised." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2277 +msgid "" +"Receive a message, calculate the digest of the message using *authkey* as " +"the key, and then send the digest back." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2280 +msgid "" +"If a welcome message is not received, then :exc:`~multiprocessing." +"AuthenticationError` is raised." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2285 +msgid "" +"Attempt to set up a connection to the listener which is using address " +"*address*, returning a :class:`~multiprocessing.Connection`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2288 +msgid "" +"The type of the connection is determined by *family* argument, but this can " +"generally be omitted since it can usually be inferred from the format of " +"*address*. (See :ref:`multiprocessing-address-formats`)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2292 +msgid "" +"If *authenticate* is ``True`` or *authkey* is a byte string then digest " +"authentication is used. The key used for authentication will be either " +"*authkey* or ``current_process().authkey`` if *authkey* is ``None``. If " +"authentication fails then :exc:`~multiprocessing.AuthenticationError` is " +"raised. See :ref:`multiprocessing-auth-keys`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2301 +msgid "" +"A wrapper for a bound socket or Windows named pipe which is 'listening' for " +"connections." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2304 +msgid "" +"*address* is the address to be used by the bound socket or named pipe of the " +"listener object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2309 +msgid "" +"If an address of '0.0.0.0' is used, the address will not be a connectable " +"end point on Windows. If you require a connectable end-point, you should use " +"'127.0.0.1'." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2313 +msgid "" +"*family* is the type of socket (or named pipe) to use. This can be one of " +"the strings ``'AF_INET'`` (for a TCP socket), ``'AF_UNIX'`` (for a Unix " +"domain socket) or ``'AF_PIPE'`` (for a Windows named pipe). Of these only " +"the first is guaranteed to be available. If *family* is ``None`` then the " +"family is inferred from the format of *address*. If *address* is also " +"``None`` then a default is chosen. This default is the family which is " +"assumed to be the fastest available. See :ref:`multiprocessing-address-" +"formats`. Note that if *family* is ``'AF_UNIX'`` and address is ``None`` " +"then the socket will be created in a private temporary directory created " +"using :func:`tempfile.mkstemp`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2324 +msgid "" +"If the listener object uses a socket then *backlog* (1 by default) is passed " +"to the :meth:`~socket.socket.listen` method of the socket once it has been " +"bound." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2328 +msgid "" +"If *authenticate* is ``True`` (``False`` by default) or *authkey* is not " +"``None`` then digest authentication is used." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2331 +msgid "" +"If *authkey* is a byte string then it will be used as the authentication " +"key; otherwise it must be *None*." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2334 +msgid "" +"If *authkey* is ``None`` and *authenticate* is ``True`` then " +"``current_process().authkey`` is used as the authentication key. If " +"*authkey* is ``None`` and *authenticate* is ``False`` then no authentication " +"is done. If authentication fails then :exc:`~multiprocessing." +"AuthenticationError` is raised. See :ref:`multiprocessing-auth-keys`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2343 +msgid "" +"Accept a connection on the bound socket or named pipe of the listener object " +"and return a :class:`~multiprocessing.Connection` object. If authentication " +"is attempted and fails, then :exc:`~multiprocessing.AuthenticationError` is " +"raised." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2350 +msgid "" +"Close the bound socket or named pipe of the listener object. This is called " +"automatically when the listener is garbage collected. However it is " +"advisable to call it explicitly." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2354 +msgid "Listener objects have the following read-only properties:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2358 +msgid "The address which is being used by the Listener object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2362 +msgid "" +"The address from which the last accepted connection came. If this is " +"unavailable then it is ``None``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2365 +msgid "" +"Listener objects now support the context management protocol -- see :ref:" +"`typecontextmanager`. :meth:`~contextmanager.__enter__` returns the " +"listener object, and :meth:`~contextmanager.__exit__` calls :meth:`close`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2372 +msgid "" +"Wait till an object in *object_list* is ready. Returns the list of those " +"objects in *object_list* which are ready. If *timeout* is a float then the " +"call blocks for at most that many seconds. If *timeout* is ``None`` then it " +"will block for an unlimited period. A negative timeout is equivalent to a " +"zero timeout." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2378 +msgid "" +"For both Unix and Windows, an object can appear in *object_list* if it is" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2381 +msgid "a readable :class:`~multiprocessing.Connection` object;" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2382 +msgid "a connected and readable :class:`socket.socket` object; or" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2383 +msgid "" +"the :attr:`~multiprocessing.Process.sentinel` attribute of a :class:" +"`~multiprocessing.Process` object." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2386 +msgid "" +"A connection or socket object is ready when there is data available to be " +"read from it, or the other end has been closed." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2389 +msgid "" +"**Unix**: ``wait(object_list, timeout)`` almost equivalent ``select." +"select(object_list, [], [], timeout)``. The difference is that, if :func:" +"`select.select` is interrupted by a signal, it can raise :exc:`OSError` with " +"an error number of ``EINTR``, whereas :func:`wait` will not." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2395 +msgid "" +"**Windows**: An item in *object_list* must either be an integer handle which " +"is waitable (according to the definition used by the documentation of the " +"Win32 function ``WaitForMultipleObjects()``) or it can be an object with a :" +"meth:`fileno` method which returns a socket handle or pipe handle. (Note " +"that pipe handles and socket handles are **not** waitable handles.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2405 +msgid "**Examples**" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2407 +msgid "" +"The following server code creates a listener which uses ``'secret " +"password'`` as an authentication key. It then waits for a connection and " +"sends some data to the client::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2426 +msgid "" +"The following code connects to the server and receives some data from the " +"server::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2443 +msgid "" +"The following code uses :func:`~multiprocessing.connection.wait` to wait for " +"messages from multiple processes at once::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2482 +msgid "Address Formats" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2484 +msgid "" +"An ``'AF_INET'`` address is a tuple of the form ``(hostname, port)`` where " +"*hostname* is a string and *port* is an integer." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2487 +msgid "" +"An ``'AF_UNIX'`` address is a string representing a filename on the " +"filesystem." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2493 +msgid "An ``'AF_PIPE'`` address is a string of the form" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2491 +msgid "" +":samp:`r'\\\\\\\\.\\\\pipe\\\\{PipeName}'`. To use :func:`Client` to " +"connect to a named pipe on a remote computer called *ServerName* one should " +"use an address of the form :samp:`r'\\\\\\\\{ServerName}\\\\pipe\\" +"\\{PipeName}'` instead." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2495 +msgid "" +"Note that any string beginning with two backslashes is assumed by default to " +"be an ``'AF_PIPE'`` address rather than an ``'AF_UNIX'`` address." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2502 +msgid "Authentication keys" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2504 +msgid "" +"When one uses :meth:`Connection.recv `, the " +"data received is automatically unpickled. Unfortunately unpickling data " +"from an untrusted source is a security risk. Therefore :class:`Listener` " +"and :func:`Client` use the :mod:`hmac` module to provide digest " +"authentication." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2510 +msgid "" +"An authentication key is a byte string which can be thought of as a " +"password: once a connection is established both ends will demand proof that " +"the other knows the authentication key. (Demonstrating that both ends are " +"using the same key does **not** involve sending the key over the connection.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2516 +msgid "" +"If authentication is requested but no authentication key is specified then " +"the return value of ``current_process().authkey`` is used (see :class:" +"`~multiprocessing.Process`). This value will be automatically inherited by " +"any :class:`~multiprocessing.Process` object that the current process " +"creates. This means that (by default) all processes of a multi-process " +"program will share a single authentication key which can be used when " +"setting up connections between themselves." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2524 +msgid "" +"Suitable authentication keys can also be generated by using :func:`os." +"urandom`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2530 +msgid "" +"Some support for logging is available. Note, however, that the :mod:" +"`logging` package does not use process shared locks so it is possible " +"(depending on the handler type) for messages from different processes to get " +"mixed up." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2537 +msgid "" +"Returns the logger used by :mod:`multiprocessing`. If necessary, a new one " +"will be created." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2540 +msgid "" +"When first created the logger has level :data:`logging.NOTSET` and no " +"default handler. Messages sent to this logger will not by default propagate " +"to the root logger." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2544 +msgid "" +"Note that on Windows child processes will only inherit the level of the " +"parent process's logger -- any other customization of the logger will not be " +"inherited." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2551 +msgid "" +"This function performs a call to :func:`get_logger` but in addition to " +"returning the logger created by get_logger, it adds a handler which sends " +"output to :data:`sys.stderr` using format ``'[%(levelname)s/%(processName)s] " +"%(message)s'``." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2556 +msgid "Below is an example session with logging turned on::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2571 +msgid "For a full table of logging levels, see the :mod:`logging` module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2575 +msgid "The :mod:`multiprocessing.dummy` module" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2580 +msgid "" +":mod:`multiprocessing.dummy` replicates the API of :mod:`multiprocessing` " +"but is no more than a wrapper around the :mod:`threading` module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2587 +msgid "Programming guidelines" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2589 +msgid "" +"There are certain guidelines and idioms which should be adhered to when " +"using :mod:`multiprocessing`." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2594 +msgid "All start methods" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2596 +msgid "The following applies to all start methods." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2598 +msgid "Avoid shared state" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2600 +msgid "" +"As far as possible one should try to avoid shifting large amounts of data " +"between processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2603 +msgid "" +"It is probably best to stick to using queues or pipes for communication " +"between processes rather than using the lower level synchronization " +"primitives." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2607 +msgid "Picklability" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2609 +msgid "Ensure that the arguments to the methods of proxies are picklable." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2611 +msgid "Thread safety of proxies" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2613 +msgid "" +"Do not use a proxy object from more than one thread unless you protect it " +"with a lock." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2616 +msgid "" +"(There is never a problem with different processes using the *same* proxy.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2618 +msgid "Joining zombie processes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2620 +msgid "" +"On Unix when a process finishes but has not been joined it becomes a zombie. " +"There should never be very many because each time a new process starts (or :" +"func:`~multiprocessing.active_children` is called) all completed processes " +"which have not yet been joined will be joined. Also calling a finished " +"process's :meth:`Process.is_alive ` will " +"join the process. Even so it is probably good practice to explicitly join " +"all the processes that you start." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2628 +msgid "Better to inherit than pickle/unpickle" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2630 +msgid "" +"When using the *spawn* or *forkserver* start methods many types from :mod:" +"`multiprocessing` need to be picklable so that child processes can use " +"them. However, one should generally avoid sending shared objects to other " +"processes using pipes or queues. Instead you should arrange the program so " +"that a process which needs access to a shared resource created elsewhere can " +"inherit it from an ancestor process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2638 +msgid "Avoid terminating processes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2640 +msgid "" +"Using the :meth:`Process.terminate ` " +"method to stop a process is liable to cause any shared resources (such as " +"locks, semaphores, pipes and queues) currently being used by the process to " +"become broken or unavailable to other processes." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2646 +msgid "" +"Therefore it is probably best to only consider using :meth:`Process." +"terminate ` on processes which never use " +"any shared resources." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2650 +msgid "Joining processes that use queues" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2652 +msgid "" +"Bear in mind that a process that has put items in a queue will wait before " +"terminating until all the buffered items are fed by the \"feeder\" thread to " +"the underlying pipe. (The child process can call the :meth:`Queue." +"cancel_join_thread ` method of the " +"queue to avoid this behaviour.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2658 +msgid "" +"This means that whenever you use a queue you need to make sure that all " +"items which have been put on the queue will eventually be removed before the " +"process is joined. Otherwise you cannot be sure that processes which have " +"put items on the queue will terminate. Remember also that non-daemonic " +"processes will be joined automatically." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2664 +msgid "An example which will deadlock is the following::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2678 +msgid "" +"A fix here would be to swap the last two lines (or simply remove the ``p." +"join()`` line)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2681 +msgid "Explicitly pass resources to child processes" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2683 +msgid "" +"On Unix using the *fork* start method, a child process can make use of a " +"shared resource created in a parent process using a global resource. " +"However, it is better to pass the object as an argument to the constructor " +"for the child process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2688 +msgid "" +"Apart from making the code (potentially) compatible with Windows and the " +"other start methods this also ensures that as long as the child process is " +"still alive the object will not be garbage collected in the parent process. " +"This might be important if some resource is freed when the object is garbage " +"collected in the parent process." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2695 +msgid "So for instance ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2707 +msgid "should be rewritten as ::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2719 +msgid "Beware of replacing :data:`sys.stdin` with a \"file like object\"" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2721 +msgid ":mod:`multiprocessing` originally unconditionally called::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2725 +msgid "" +"in the :meth:`multiprocessing.Process._bootstrap` method --- this resulted " +"in issues with processes-in-processes. This has been changed to::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2731 +msgid "" +"Which solves the fundamental issue of processes colliding with each other " +"resulting in a bad file descriptor error, but introduces a potential danger " +"to applications which replace :func:`sys.stdin` with a \"file-like object\" " +"with output buffering. This danger is that if multiple processes call :meth:" +"`~io.IOBase.close()` on this file-like object, it could result in the same " +"data being flushed to the object multiple times, resulting in corruption." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2738 +msgid "" +"If you write a file-like object and implement your own caching, you can make " +"it fork-safe by storing the pid whenever you append to the cache, and " +"discarding the cache when the pid changes. For example::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2750 +msgid "" +"For more information, see :issue:`5155`, :issue:`5313` and :issue:`5331`" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2753 +msgid "The *spawn* and *forkserver* start methods" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2755 +msgid "" +"There are a few extra restriction which don't apply to the *fork* start " +"method." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2758 +msgid "More picklability" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2760 +msgid "" +"Ensure that all arguments to :meth:`Process.__init__` are picklable. Also, " +"if you subclass :class:`~multiprocessing.Process` then make sure that " +"instances will be picklable when the :meth:`Process.start ` method is called." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2765 +msgid "Global variables" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2767 +msgid "" +"Bear in mind that if code run in a child process tries to access a global " +"variable, then the value it sees (if any) may not be the same as the value " +"in the parent process at the time that :meth:`Process.start ` was called." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2772 +msgid "" +"However, global variables which are just module level constants cause no " +"problems." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2775 +msgid "Safe importing of main module" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2777 +msgid "" +"Make sure that the main module can be safely imported by a new Python " +"interpreter without causing unintended side effects (such a starting a new " +"process)." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2781 +msgid "" +"For example, using the *spawn* or *forkserver* start method running the " +"following module would fail with a :exc:`RuntimeError`::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2793 +msgid "" +"Instead one should protect the \"entry point\" of the program by using ``if " +"__name__ == '__main__':`` as follows::" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2807 +msgid "" +"(The ``freeze_support()`` line can be omitted if the program will be run " +"normally instead of frozen.)" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2810 +msgid "" +"This allows the newly spawned Python interpreter to safely import the module " +"and then run the module's ``foo()`` function." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2813 +msgid "" +"Similar restrictions apply if a pool or manager is created in the main " +"module." +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2822 +msgid "Demonstration of how to create and use customized managers and proxies:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2828 +msgid "Using :class:`~multiprocessing.pool.Pool`:" +msgstr "" + +#: ../Doc/library/multiprocessing.rst:2834 +msgid "" +"An example showing how to use queues to feed tasks to a collection of worker " +"processes and collect the results:" +msgstr "" + +#: ../Doc/library/netdata.rst:6 +msgid "Internet Data Handling" +msgstr "" + +#: ../Doc/library/netdata.rst:8 +msgid "" +"This chapter describes modules which support handling data formats commonly " +"used on the Internet." +msgstr "" + +#: ../Doc/library/netrc.rst:3 +msgid ":mod:`netrc` --- netrc file processing" +msgstr "" + +#: ../Doc/library/netrc.rst:11 +msgid "**Source code:** :source:`Lib/netrc.py`" +msgstr "" + +#: ../Doc/library/netrc.rst:15 +msgid "" +"The :class:`netrc` class parses and encapsulates the netrc file format used " +"by the Unix :program:`ftp` program and other FTP clients." +msgstr "" + +#: ../Doc/library/netrc.rst:21 +msgid "" +"A :class:`netrc` instance or subclass instance encapsulates data from a " +"netrc file. The initialization argument, if present, specifies the file to " +"parse. If no argument is given, the file :file:`.netrc` in the user's home " +"directory will be read. Parse errors will raise :exc:`NetrcParseError` with " +"diagnostic information including the file name, line number, and terminating " +"token. If no argument is specified on a POSIX system, the presence of " +"passwords in the :file:`.netrc` file will raise a :exc:`NetrcParseError` if " +"the file ownership or permissions are insecure (owned by a user other than " +"the user running the process, or accessible for read or write by any other " +"user). This implements security behavior equivalent to that of ftp and other " +"programs that use :file:`.netrc`." +msgstr "" + +#: ../Doc/library/netrc.rst:33 +msgid "Added the POSIX permission check." +msgstr "" + +#: ../Doc/library/netrc.rst:38 +msgid "" +"Exception raised by the :class:`netrc` class when syntactical errors are " +"encountered in source text. Instances of this exception provide three " +"interesting attributes: :attr:`msg` is a textual explanation of the error, :" +"attr:`filename` is the name of the source file, and :attr:`lineno` gives the " +"line number on which the error was found." +msgstr "" + +#: ../Doc/library/netrc.rst:48 +msgid "netrc Objects" +msgstr "" + +#: ../Doc/library/netrc.rst:50 +msgid "A :class:`netrc` instance has the following methods:" +msgstr "" + +#: ../Doc/library/netrc.rst:55 +msgid "" +"Return a 3-tuple ``(login, account, password)`` of authenticators for " +"*host*. If the netrc file did not contain an entry for the given host, " +"return the tuple associated with the 'default' entry. If neither matching " +"host nor default entry is available, return ``None``." +msgstr "" + +#: ../Doc/library/netrc.rst:63 +msgid "" +"Dump the class data as a string in the format of a netrc file. (This " +"discards comments and may reorder the entries.)" +msgstr "" + +#: ../Doc/library/netrc.rst:66 +msgid "Instances of :class:`netrc` have public instance variables:" +msgstr "" + +#: ../Doc/library/netrc.rst:71 +msgid "" +"Dictionary mapping host names to ``(login, account, password)`` tuples. The " +"'default' entry, if any, is represented as a pseudo-host by that name." +msgstr "" + +#: ../Doc/library/netrc.rst:77 +msgid "Dictionary mapping macro names to string lists." +msgstr "" + +#: ../Doc/library/netrc.rst:81 +msgid "" +"Passwords are limited to a subset of the ASCII character set. All ASCII " +"punctuation is allowed in passwords, however, note that whitespace and non-" +"printable characters are not allowed in passwords. This is a limitation of " +"the way the .netrc file is parsed and may be removed in the future." +msgstr "" + +#: ../Doc/library/nis.rst:3 +msgid ":mod:`nis` --- Interface to Sun's NIS (Yellow Pages)" +msgstr "" + +#: ../Doc/library/nis.rst:14 +msgid "" +"The :mod:`nis` module gives a thin wrapper around the NIS library, useful " +"for central administration of several hosts." +msgstr "" + +#: ../Doc/library/nis.rst:17 +msgid "" +"Because NIS exists only on Unix systems, this module is only available for " +"Unix." +msgstr "" + +#: ../Doc/library/nis.rst:19 +msgid "The :mod:`nis` module defines the following functions:" +msgstr "" + +#: ../Doc/library/nis.rst:24 +msgid "" +"Return the match for *key* in map *mapname*, or raise an error (:exc:`nis." +"error`) if there is none. Both should be strings, *key* is 8-bit clean. " +"Return value is an arbitrary array of bytes (may contain ``NULL`` and other " +"joys)." +msgstr "" + +#: ../Doc/library/nis.rst:29 ../Doc/library/nis.rst:41 +msgid "Note that *mapname* is first checked if it is an alias to another name." +msgstr "" + +#: ../Doc/library/nis.rst:31 ../Doc/library/nis.rst:43 +#: ../Doc/library/nis.rst:51 +msgid "" +"The *domain* argument allows overriding the NIS domain used for the lookup. " +"If unspecified, lookup is in the default NIS domain." +msgstr "" + +#: ../Doc/library/nis.rst:37 +msgid "" +"Return a dictionary mapping *key* to *value* such that ``match(key, " +"mapname)==value``. Note that both keys and values of the dictionary are " +"arbitrary arrays of bytes." +msgstr "" + +#: ../Doc/library/nis.rst:49 +msgid "Return a list of all valid maps." +msgstr "" + +#: ../Doc/library/nis.rst:57 +msgid "Return the system default NIS domain." +msgstr "" + +#: ../Doc/library/nis.rst:60 +msgid "The :mod:`nis` module defines the following exception:" +msgstr "" + +#: ../Doc/library/nis.rst:64 +msgid "An error raised when a NIS function returns an error code." +msgstr "" + +#: ../Doc/library/nntplib.rst:2 +msgid ":mod:`nntplib` --- NNTP protocol client" +msgstr "" + +#: ../Doc/library/nntplib.rst:7 +msgid "**Source code:** :source:`Lib/nntplib.py`" +msgstr "" + +#: ../Doc/library/nntplib.rst:15 +msgid "" +"This module defines the class :class:`NNTP` which implements the client side " +"of the Network News Transfer Protocol. It can be used to implement a news " +"reader or poster, or automated news processors. It is compatible with :rfc:" +"`3977` as well as the older :rfc:`977` and :rfc:`2980`." +msgstr "" + +#: ../Doc/library/nntplib.rst:20 +msgid "" +"Here are two small examples of how it can be used. To list some statistics " +"about a newsgroup and print the subjects of the last 10 articles::" +msgstr "" + +#: ../Doc/library/nntplib.rst:44 +msgid "" +"To post an article from a binary file (this assumes that the article has " +"valid headers, and that you have right to post on the particular newsgroup)::" +msgstr "" + +#: ../Doc/library/nntplib.rst:54 +msgid "The module itself defines the following classes:" +msgstr "" + +#: ../Doc/library/nntplib.rst:59 +msgid "" +"Return a new :class:`NNTP` object, representing a connection to the NNTP " +"server running on host *host*, listening at port *port*. An optional " +"*timeout* can be specified for the socket connection. If the optional *user* " +"and *password* are provided, or if suitable credentials are present in :file:" +"`/.netrc` and the optional flag *usenetrc* is true, the ``AUTHINFO USER`` " +"and ``AUTHINFO PASS`` commands are used to identify and authenticate the " +"user to the server. If the optional flag *readermode* is true, then a " +"``mode reader`` command is sent before authentication is performed. Reader " +"mode is sometimes necessary if you are connecting to an NNTP server on the " +"local machine and intend to call reader-specific commands, such as " +"``group``. If you get unexpected :exc:`NNTPPermanentError`\\ s, you might " +"need to set *readermode*. The :class:`NNTP` class supports the :keyword:" +"`with` statement to unconditionally consume :exc:`OSError` exceptions and to " +"close the NNTP connection when done, e.g.:" +msgstr "" + +#: ../Doc/library/nntplib.rst:83 +msgid "*usenetrc* is now ``False`` by default." +msgstr "" + +#: ../Doc/library/nntplib.rst:91 +msgid "" +"Return a new :class:`NNTP_SSL` object, representing an encrypted connection " +"to the NNTP server running on host *host*, listening at port *port*. :class:" +"`NNTP_SSL` objects have the same methods as :class:`NNTP` objects. If " +"*port* is omitted, port 563 (NNTPS) is used. *ssl_context* is also optional, " +"and is a :class:`~ssl.SSLContext` object. Please read :ref:`ssl-security` " +"for best practices. All other parameters behave the same as for :class:" +"`NNTP`." +msgstr "" + +#: ../Doc/library/nntplib.rst:99 +msgid "" +"Note that SSL-on-563 is discouraged per :rfc:`4642`, in favor of STARTTLS as " +"described below. However, some servers only support the former." +msgstr "" + +#: ../Doc/library/nntplib.rst:112 +msgid "" +"Derived from the standard exception :exc:`Exception`, this is the base class " +"for all exceptions raised by the :mod:`nntplib` module. Instances of this " +"class have the following attribute:" +msgstr "" + +#: ../Doc/library/nntplib.rst:118 +msgid "The response of the server if available, as a :class:`str` object." +msgstr "" + +#: ../Doc/library/nntplib.rst:128 +msgid "" +"Exception raised when a response code in the range 400--499 is received." +msgstr "" + +#: ../Doc/library/nntplib.rst:133 +msgid "" +"Exception raised when a response code in the range 500--599 is received." +msgstr "" + +#: ../Doc/library/nntplib.rst:138 +msgid "" +"Exception raised when a reply is received from the server that does not " +"begin with a digit in the range 1--5." +msgstr "" + +#: ../Doc/library/nntplib.rst:144 +msgid "Exception raised when there is some error in the response data." +msgstr "" + +#: ../Doc/library/nntplib.rst:150 +msgid "NNTP Objects" +msgstr "" + +#: ../Doc/library/nntplib.rst:152 +msgid "" +"When connected, :class:`NNTP` and :class:`NNTP_SSL` objects support the " +"following methods and attributes." +msgstr "" + +#: ../Doc/library/nntplib.rst:156 +msgid "Attributes" +msgstr "" + +#: ../Doc/library/nntplib.rst:160 +msgid "" +"An integer representing the version of the NNTP protocol supported by the " +"server. In practice, this should be ``2`` for servers advertising :rfc:" +"`3977` compliance and ``1`` for others." +msgstr "" + +#: ../Doc/library/nntplib.rst:168 +msgid "" +"A string describing the software name and version of the NNTP server, or :" +"const:`None` if not advertised by the server." +msgstr "" + +#: ../Doc/library/nntplib.rst:174 ../Doc/library/pathlib.rst:629 +#: ../Doc/library/stdtypes.rst:4408 +msgid "Methods" +msgstr "" + +#: ../Doc/library/nntplib.rst:176 +msgid "" +"The *response* that is returned as the first item in the return tuple of " +"almost all methods is the server's response: a string beginning with a three-" +"digit code. If the server's response indicates an error, the method raises " +"one of the above exceptions." +msgstr "" + +#: ../Doc/library/nntplib.rst:181 +msgid "" +"Many of the following methods take an optional keyword-only argument *file*. " +"When the *file* argument is supplied, it must be either a :term:`file " +"object` opened for binary writing, or the name of an on-disk file to be " +"written to. The method will then write any data returned by the server " +"(except for the response line and the terminating dot) to the file; any list " +"of lines, tuples or objects that the method normally returns will be empty." +msgstr "" + +#: ../Doc/library/nntplib.rst:188 +msgid "" +"Many of the following methods have been reworked and fixed, which makes them " +"incompatible with their 3.1 counterparts." +msgstr "" + +#: ../Doc/library/nntplib.rst:195 +msgid "" +"Send a ``QUIT`` command and close the connection. Once this method has been " +"called, no other methods of the NNTP object should be called." +msgstr "" + +#: ../Doc/library/nntplib.rst:208 +msgid "" +"Return the :rfc:`3977` capabilities advertised by the server, as a :class:" +"`dict` instance mapping capability names to (possibly empty) lists of " +"values. On legacy servers which don't understand the ``CAPABILITIES`` " +"command, an empty dictionary is returned instead." +msgstr "" + +#: ../Doc/library/nntplib.rst:222 +msgid "" +"Send ``AUTHINFO`` commands with the user name and password. If *user* and " +"*password* are None and *usenetrc* is true, credentials from ``~/.netrc`` " +"will be used if possible." +msgstr "" + +#: ../Doc/library/nntplib.rst:226 +msgid "" +"Unless intentionally delayed, login is normally performed during the :class:" +"`NNTP` object initialization and separately calling this function is " +"unnecessary. To force authentication to be delayed, you must not set *user* " +"or *password* when creating the object, and must set *usenetrc* to False." +msgstr "" + +#: ../Doc/library/nntplib.rst:237 +msgid "" +"Send a ``STARTTLS`` command. This will enable encryption on the NNTP " +"connection. The *ssl_context* argument is optional and should be a :class:" +"`ssl.SSLContext` object. Please read :ref:`ssl-security` for best practices." +msgstr "" + +#: ../Doc/library/nntplib.rst:242 +msgid "" +"Note that this may not be done after authentication information has been " +"transmitted, and authentication occurs by default if possible during a :" +"class:`NNTP` object initialization. See :meth:`NNTP.login` for information " +"on suppressing this behavior." +msgstr "" + +#: ../Doc/library/nntplib.rst:256 +msgid "" +"Send a ``NEWGROUPS`` command. The *date* argument should be a :class:" +"`datetime.date` or :class:`datetime.datetime` object. Return a pair " +"``(response, groups)`` where *groups* is a list representing the groups that " +"are new since the given *date*. If *file* is supplied, though, then *groups* " +"will be empty." +msgstr "" + +#: ../Doc/library/nntplib.rst:272 +msgid "" +"Send a ``NEWNEWS`` command. Here, *group* is a group name or ``'*'``, and " +"*date* has the same meaning as for :meth:`newgroups`. Return a pair " +"``(response, articles)`` where *articles* is a list of message ids." +msgstr "" + +#: ../Doc/library/nntplib.rst:276 +msgid "This command is frequently disabled by NNTP server administrators." +msgstr "" + +#: ../Doc/library/nntplib.rst:281 +msgid "" +"Send a ``LIST`` or ``LIST ACTIVE`` command. Return a pair ``(response, " +"list)`` where *list* is a list of tuples representing all the groups " +"available from this NNTP server, optionally matching the pattern string " +"*group_pattern*. Each tuple has the form ``(group, last, first, flag)``, " +"where *group* is a group name, *last* and *first* are the last and first " +"article numbers, and *flag* usually takes one of these values:" +msgstr "" + +#: ../Doc/library/nntplib.rst:289 +msgid "``y``: Local postings and articles from peers are allowed." +msgstr "" + +#: ../Doc/library/nntplib.rst:290 +msgid "``m``: The group is moderated and all postings must be approved." +msgstr "" + +#: ../Doc/library/nntplib.rst:291 +msgid "``n``: No local postings are allowed, only articles from peers." +msgstr "" + +#: ../Doc/library/nntplib.rst:292 +msgid "``j``: Articles from peers are filed in the junk group instead." +msgstr "" + +#: ../Doc/library/nntplib.rst:293 +msgid "``x``: No local postings, and articles from peers are ignored." +msgstr "" + +#: ../Doc/library/nntplib.rst:294 +msgid "``=foo.bar``: Articles are filed in the ``foo.bar`` group instead." +msgstr "" + +#: ../Doc/library/nntplib.rst:296 +msgid "" +"If *flag* has another value, then the status of the newsgroup should be " +"considered unknown." +msgstr "" + +#: ../Doc/library/nntplib.rst:299 +msgid "" +"This command can return very large results, especially if *group_pattern* is " +"not specified. It is best to cache the results offline unless you really " +"need to refresh them." +msgstr "" + +#: ../Doc/library/nntplib.rst:303 +msgid "*group_pattern* was added." +msgstr "" + +#: ../Doc/library/nntplib.rst:309 +msgid "" +"Send a ``LIST NEWSGROUPS`` command, where *grouppattern* is a wildmat string " +"as specified in :rfc:`3977` (it's essentially the same as DOS or UNIX shell " +"wildcard strings). Return a pair ``(response, descriptions)``, where " +"*descriptions* is a dictionary mapping group names to textual descriptions." +msgstr "" + +#: ../Doc/library/nntplib.rst:323 +msgid "" +"Get a description for a single group *group*. If more than one group " +"matches (if 'group' is a real wildmat string), return the first match. If " +"no group matches, return an empty string." +msgstr "" + +#: ../Doc/library/nntplib.rst:327 +msgid "" +"This elides the response code from the server. If the response code is " +"needed, use :meth:`descriptions`." +msgstr "" + +#: ../Doc/library/nntplib.rst:333 +msgid "" +"Send a ``GROUP`` command, where *name* is the group name. The group is " +"selected as the current group, if it exists. Return a tuple ``(response, " +"count, first, last, name)`` where *count* is the (estimated) number of " +"articles in the group, *first* is the first article number in the group, " +"*last* is the last article number in the group, and *name* is the group name." +msgstr "" + +#: ../Doc/library/nntplib.rst:343 +msgid "" +"Send an ``OVER`` command, or an ``XOVER`` command on legacy servers. " +"*message_spec* can be either a string representing a message id, or a " +"``(first, last)`` tuple of numbers indicating a range of articles in the " +"current group, or a ``(first, None)`` tuple indicating a range of articles " +"starting from *first* to the last article in the current group, or :const:" +"`None` to select the current article in the current group." +msgstr "" + +#: ../Doc/library/nntplib.rst:350 +msgid "" +"Return a pair ``(response, overviews)``. *overviews* is a list of " +"``(article_number, overview)`` tuples, one for each article selected by " +"*message_spec*. Each *overview* is a dictionary with the same number of " +"items, but this number depends on the server. These items are either " +"message headers (the key is then the lower-cased header name) or metadata " +"items (the key is then the metadata name prepended with ``\":\"``). The " +"following items are guaranteed to be present by the NNTP specification:" +msgstr "" + +#: ../Doc/library/nntplib.rst:358 +msgid "" +"the ``subject``, ``from``, ``date``, ``message-id`` and ``references`` " +"headers" +msgstr "" + +#: ../Doc/library/nntplib.rst:360 +msgid "" +"the ``:bytes`` metadata: the number of bytes in the entire raw article " +"(including headers and body)" +msgstr "" + +#: ../Doc/library/nntplib.rst:362 +msgid "the ``:lines`` metadata: the number of lines in the article body" +msgstr "" + +#: ../Doc/library/nntplib.rst:364 +msgid "" +"The value of each item is either a string, or :const:`None` if not present." +msgstr "" + +#: ../Doc/library/nntplib.rst:366 +msgid "" +"It is advisable to use the :func:`decode_header` function on header values " +"when they may contain non-ASCII characters::" +msgstr "" + +#: ../Doc/library/nntplib.rst:386 +msgid "" +"Send a ``HELP`` command. Return a pair ``(response, list)`` where *list* is " +"a list of help strings." +msgstr "" + +#: ../Doc/library/nntplib.rst:392 +msgid "" +"Send a ``STAT`` command, where *message_spec* is either a message id " +"(enclosed in ``'<'`` and ``'>'``) or an article number in the current group. " +"If *message_spec* is omitted or :const:`None`, the current article in the " +"current group is considered. Return a triple ``(response, number, id)`` " +"where *number* is the article number and *id* is the message id." +msgstr "" + +#: ../Doc/library/nntplib.rst:406 +msgid "Send a ``NEXT`` command. Return as for :meth:`.stat`." +msgstr "" + +#: ../Doc/library/nntplib.rst:411 +msgid "Send a ``LAST`` command. Return as for :meth:`.stat`." +msgstr "" + +#: ../Doc/library/nntplib.rst:416 +msgid "" +"Send an ``ARTICLE`` command, where *message_spec* has the same meaning as " +"for :meth:`.stat`. Return a tuple ``(response, info)`` where *info* is a :" +"class:`~collections.namedtuple` with three attributes *number*, *message_id* " +"and *lines* (in that order). *number* is the article number in the group " +"(or 0 if the information is not available), *message_id* the message id as a " +"string, and *lines* a list of lines (without terminating newlines) " +"comprising the raw message including headers and body." +msgstr "" + +#: ../Doc/library/nntplib.rst:441 +msgid "" +"Same as :meth:`article()`, but sends a ``HEAD`` command. The *lines* " +"returned (or written to *file*) will only contain the message headers, not " +"the body." +msgstr "" + +#: ../Doc/library/nntplib.rst:448 +msgid "" +"Same as :meth:`article()`, but sends a ``BODY`` command. The *lines* " +"returned (or written to *file*) will only contain the message body, not the " +"headers." +msgstr "" + +#: ../Doc/library/nntplib.rst:455 +msgid "" +"Post an article using the ``POST`` command. The *data* argument is either " +"a :term:`file object` opened for binary reading, or any iterable of bytes " +"objects (representing raw lines of the article to be posted). It should " +"represent a well-formed news article, including the required headers. The :" +"meth:`post` method automatically escapes lines beginning with ``.`` and " +"appends the termination line." +msgstr "" + +#: ../Doc/library/nntplib.rst:462 +msgid "" +"If the method succeeds, the server's response is returned. If the server " +"refuses posting, a :class:`NNTPReplyError` is raised." +msgstr "" + +#: ../Doc/library/nntplib.rst:468 +msgid "" +"Send an ``IHAVE`` command. *message_id* is the id of the message to send to " +"the server (enclosed in ``'<'`` and ``'>'``). The *data* parameter and the " +"return value are the same as for :meth:`post()`." +msgstr "" + +#: ../Doc/library/nntplib.rst:475 +msgid "" +"Return a pair ``(response, date)``. *date* is a :class:`~datetime.datetime` " +"object containing the current date and time of the server." +msgstr "" + +#: ../Doc/library/nntplib.rst:481 +msgid "Send a ``SLAVE`` command. Return the server's *response*." +msgstr "" + +#: ../Doc/library/nntplib.rst:486 +msgid "" +"Set the instance's debugging level. This controls the amount of debugging " +"output printed. The default, ``0``, produces no debugging output. A value " +"of ``1`` produces a moderate amount of debugging output, generally a single " +"line per request or response. A value of ``2`` or higher produces the " +"maximum amount of debugging output, logging each line sent and received on " +"the connection (including message text)." +msgstr "" + +#: ../Doc/library/nntplib.rst:494 +msgid "" +"The following are optional NNTP extensions defined in :rfc:`2980`. Some of " +"them have been superseded by newer commands in :rfc:`3977`." +msgstr "" + +#: ../Doc/library/nntplib.rst:500 +msgid "" +"Send an ``XHDR`` command. The *hdr* argument is a header keyword, e.g. " +"``'subject'``. The *str* argument should have the form ``'first-last'`` " +"where *first* and *last* are the first and last article numbers to search. " +"Return a pair ``(response, list)``, where *list* is a list of pairs ``(id, " +"text)``, where *id* is an article number (as a string) and *text* is the " +"text of the requested header for that article. If the *file* parameter is " +"supplied, then the output of the ``XHDR`` command is stored in a file. If " +"*file* is a string, then the method will open a file with that name, write " +"to it then close it. If *file* is a :term:`file object`, then it will start " +"calling :meth:`write` on it to store the lines of the command output. If " +"*file* is supplied, then the returned *list* is an empty list." +msgstr "" + +#: ../Doc/library/nntplib.rst:515 +msgid "" +"Send an ``XOVER`` command. *start* and *end* are article numbers delimiting " +"the range of articles to select. The return value is the same of for :meth:" +"`over()`. It is recommended to use :meth:`over()` instead, since it will " +"automatically use the newer ``OVER`` command if available." +msgstr "" + +#: ../Doc/library/nntplib.rst:524 +msgid "" +"Return a pair ``(resp, path)``, where *path* is the directory path to the " +"article with message ID *id*. Most of the time, this extension is not " +"enabled by NNTP server administrators." +msgstr "" + +#: ../Doc/library/nntplib.rst:528 +msgid "The XPATH extension is not actively used." +msgstr "" + +#: ../Doc/library/nntplib.rst:552 +msgid "The module also defines the following utility function:" +msgstr "" + +#: ../Doc/library/nntplib.rst:557 +msgid "" +"Decode a header value, un-escaping any escaped non-ASCII characters. " +"*header_str* must be a :class:`str` object. The unescaped value is " +"returned. Using this function is recommended to display some headers in a " +"human readable form::" +msgstr "" + +#: ../Doc/library/numbers.rst:2 +msgid ":mod:`numbers` --- Numeric abstract base classes" +msgstr "" + +#: ../Doc/library/numbers.rst:7 +msgid "**Source code:** :source:`Lib/numbers.py`" +msgstr "" + +#: ../Doc/library/numbers.rst:11 +msgid "" +"The :mod:`numbers` module (:pep:`3141`) defines a hierarchy of numeric :term:" +"`abstract base classes ` which progressively define " +"more operations. None of the types defined in this module can be " +"instantiated." +msgstr "" + +#: ../Doc/library/numbers.rst:18 +msgid "" +"The root of the numeric hierarchy. If you just want to check if an argument " +"*x* is a number, without caring what kind, use ``isinstance(x, Number)``." +msgstr "" + +#: ../Doc/library/numbers.rst:23 +msgid "The numeric tower" +msgstr "" + +#: ../Doc/library/numbers.rst:27 +msgid "" +"Subclasses of this type describe complex numbers and include the operations " +"that work on the built-in :class:`complex` type. These are: conversions to :" +"class:`complex` and :class:`bool`, :attr:`.real`, :attr:`.imag`, ``+``, ``-" +"``, ``*``, ``/``, :func:`abs`, :meth:`conjugate`, ``==``, and ``!=``. All " +"except ``-`` and ``!=`` are abstract." +msgstr "" + +#: ../Doc/library/numbers.rst:35 +msgid "Abstract. Retrieves the real component of this number." +msgstr "" + +#: ../Doc/library/numbers.rst:39 +msgid "Abstract. Retrieves the imaginary component of this number." +msgstr "" + +#: ../Doc/library/numbers.rst:43 +msgid "" +"Abstract. Returns the complex conjugate. For example, ``(1+3j).conjugate() " +"== (1-3j)``." +msgstr "" + +#: ../Doc/library/numbers.rst:48 +msgid "" +"To :class:`Complex`, :class:`Real` adds the operations that work on real " +"numbers." +msgstr "" + +#: ../Doc/library/numbers.rst:51 +msgid "" +"In short, those are: a conversion to :class:`float`, :func:`math.trunc`, :" +"func:`round`, :func:`math.floor`, :func:`math.ceil`, :func:`divmod`, ``//``, " +"``%``, ``<``, ``<=``, ``>``, and ``>=``." +msgstr "" + +#: ../Doc/library/numbers.rst:55 +msgid "" +"Real also provides defaults for :func:`complex`, :attr:`~Complex.real`, :" +"attr:`~Complex.imag`, and :meth:`~Complex.conjugate`." +msgstr "" + +#: ../Doc/library/numbers.rst:61 +msgid "" +"Subtypes :class:`Real` and adds :attr:`~Rational.numerator` and :attr:" +"`~Rational.denominator` properties, which should be in lowest terms. With " +"these, it provides a default for :func:`float`." +msgstr "" + +#: ../Doc/library/numbers.rst:68 ../Doc/library/numbers.rst:72 +msgid "Abstract." +msgstr "" + +#: ../Doc/library/numbers.rst:77 +msgid "" +"Subtypes :class:`Rational` and adds a conversion to :class:`int`. Provides " +"defaults for :func:`float`, :attr:`~Rational.numerator`, and :attr:" +"`~Rational.denominator`. Adds abstract methods for ``**`` and bit-string " +"operations: ``<<``, ``>>``, ``&``, ``^``, ``|``, ``~``." +msgstr "" + +#: ../Doc/library/numbers.rst:84 +msgid "Notes for type implementors" +msgstr "" + +#: ../Doc/library/numbers.rst:86 +msgid "" +"Implementors should be careful to make equal numbers equal and hash them to " +"the same values. This may be subtle if there are two different extensions of " +"the real numbers. For example, :class:`fractions.Fraction` implements :func:" +"`hash` as follows::" +msgstr "" + +#: ../Doc/library/numbers.rst:105 +msgid "Adding More Numeric ABCs" +msgstr "" + +#: ../Doc/library/numbers.rst:107 +msgid "" +"There are, of course, more possible ABCs for numbers, and this would be a " +"poor hierarchy if it precluded the possibility of adding those. You can add " +"``MyFoo`` between :class:`Complex` and :class:`Real` with::" +msgstr "" + +#: ../Doc/library/numbers.rst:119 +msgid "Implementing the arithmetic operations" +msgstr "" + +#: ../Doc/library/numbers.rst:121 +msgid "" +"We want to implement the arithmetic operations so that mixed-mode operations " +"either call an implementation whose author knew about the types of both " +"arguments, or convert both to the nearest built in type and do the operation " +"there. For subtypes of :class:`Integral`, this means that :meth:`__add__` " +"and :meth:`__radd__` should be defined as::" +msgstr "" + +#: ../Doc/library/numbers.rst:152 +msgid "" +"There are 5 different cases for a mixed-type operation on subclasses of :" +"class:`Complex`. I'll refer to all of the above code that doesn't refer to " +"``MyIntegral`` and ``OtherTypeIKnowAbout`` as \"boilerplate\". ``a`` will be " +"an instance of ``A``, which is a subtype of :class:`Complex` (``a : A <: " +"Complex``), and ``b : B <: Complex``. I'll consider ``a + b``:" +msgstr "" + +#: ../Doc/library/numbers.rst:159 +msgid "If ``A`` defines an :meth:`__add__` which accepts ``b``, all is well." +msgstr "" + +#: ../Doc/library/numbers.rst:161 +msgid "" +"If ``A`` falls back to the boilerplate code, and it were to return a value " +"from :meth:`__add__`, we'd miss the possibility that ``B`` defines a more " +"intelligent :meth:`__radd__`, so the boilerplate should return :const:" +"`NotImplemented` from :meth:`__add__`. (Or ``A`` may not implement :meth:" +"`__add__` at all.)" +msgstr "" + +#: ../Doc/library/numbers.rst:167 +msgid "" +"Then ``B``'s :meth:`__radd__` gets a chance. If it accepts ``a``, all is " +"well." +msgstr "" + +#: ../Doc/library/numbers.rst:169 +msgid "" +"If it falls back to the boilerplate, there are no more possible methods to " +"try, so this is where the default implementation should live." +msgstr "" + +#: ../Doc/library/numbers.rst:172 +msgid "" +"If ``B <: A``, Python tries ``B.__radd__`` before ``A.__add__``. This is ok, " +"because it was implemented with knowledge of ``A``, so it can handle those " +"instances before delegating to :class:`Complex`." +msgstr "" + +#: ../Doc/library/numbers.rst:177 +msgid "" +"If ``A <: Complex`` and ``B <: Real`` without sharing any other knowledge, " +"then the appropriate shared operation is the one involving the built in :" +"class:`complex`, and both :meth:`__radd__` s land there, so ``a+b == b+a``." +msgstr "" + +#: ../Doc/library/numbers.rst:182 +msgid "" +"Because most of the operations on any given type will be very similar, it " +"can be useful to define a helper function which generates the forward and " +"reverse instances of any given operator. For example, :class:`fractions." +"Fraction` uses::" +msgstr "" + +#: ../Doc/library/numeric.rst:6 +msgid "Numeric and Mathematical Modules" +msgstr "" + +#: ../Doc/library/numeric.rst:8 +msgid "" +"The modules described in this chapter provide numeric and math-related " +"functions and data types. The :mod:`numbers` module defines an abstract " +"hierarchy of numeric types. The :mod:`math` and :mod:`cmath` modules contain " +"various mathematical functions for floating-point and complex numbers. The :" +"mod:`decimal` module supports exact representations of decimal numbers, " +"using arbitrary precision arithmetic." +msgstr "" + +#: ../Doc/library/operator.rst:2 +msgid ":mod:`operator` --- Standard operators as functions" +msgstr "" + +#: ../Doc/library/operator.rst:9 +msgid "**Source code:** :source:`Lib/operator.py`" +msgstr "" + +#: ../Doc/library/operator.rst:18 +msgid "" +"The :mod:`operator` module exports a set of efficient functions " +"corresponding to the intrinsic operators of Python. For example, ``operator." +"add(x, y)`` is equivalent to the expression ``x+y``. The function names are " +"those used for special class methods; variants without leading and trailing " +"``__`` are also provided for convenience." +msgstr "" + +#: ../Doc/library/operator.rst:24 +msgid "" +"The functions fall into categories that perform object comparisons, logical " +"operations, mathematical operations and sequence operations." +msgstr "" + +#: ../Doc/library/operator.rst:27 +msgid "" +"The object comparison functions are useful for all objects, and are named " +"after the rich comparison operators they support:" +msgstr "" + +#: ../Doc/library/operator.rst:44 +msgid "" +"Perform \"rich comparisons\" between *a* and *b*. Specifically, ``lt(a, b)`` " +"is equivalent to ``a < b``, ``le(a, b)`` is equivalent to ``a <= b``, " +"``eq(a, b)`` is equivalent to ``a == b``, ``ne(a, b)`` is equivalent to ``a !" +"= b``, ``gt(a, b)`` is equivalent to ``a > b`` and ``ge(a, b)`` is " +"equivalent to ``a >= b``. Note that these functions can return any value, " +"which may or may not be interpretable as a Boolean value. See :ref:" +"`comparisons` for more information about rich comparisons." +msgstr "" + +#: ../Doc/library/operator.rst:53 +msgid "" +"The logical operations are also generally applicable to all objects, and " +"support truth tests, identity tests, and boolean operations:" +msgstr "" + +#: ../Doc/library/operator.rst:60 +msgid "" +"Return the outcome of :keyword:`not` *obj*. (Note that there is no :meth:" +"`__not__` method for object instances; only the interpreter core defines " +"this operation. The result is affected by the :meth:`__bool__` and :meth:" +"`__len__` methods.)" +msgstr "" + +#: ../Doc/library/operator.rst:68 +msgid "" +"Return :const:`True` if *obj* is true, and :const:`False` otherwise. This " +"is equivalent to using the :class:`bool` constructor." +msgstr "" + +#: ../Doc/library/operator.rst:74 +msgid "Return ``a is b``. Tests object identity." +msgstr "" + +#: ../Doc/library/operator.rst:79 +msgid "Return ``a is not b``. Tests object identity." +msgstr "" + +#: ../Doc/library/operator.rst:82 +msgid "The mathematical and bitwise operations are the most numerous:" +msgstr "" + +#: ../Doc/library/operator.rst:88 +msgid "Return the absolute value of *obj*." +msgstr "" + +#: ../Doc/library/operator.rst:94 +msgid "Return ``a + b``, for *a* and *b* numbers." +msgstr "" + +#: ../Doc/library/operator.rst:100 +msgid "Return the bitwise and of *a* and *b*." +msgstr "" + +#: ../Doc/library/operator.rst:106 +msgid "Return ``a // b``." +msgstr "" + +#: ../Doc/library/operator.rst:112 +msgid "Return *a* converted to an integer. Equivalent to ``a.__index__()``." +msgstr "" + +#: ../Doc/library/operator.rst:120 +msgid "" +"Return the bitwise inverse of the number *obj*. This is equivalent to " +"``~obj``." +msgstr "" + +#: ../Doc/library/operator.rst:126 +msgid "Return *a* shifted left by *b*." +msgstr "" + +#: ../Doc/library/operator.rst:132 +msgid "Return ``a % b``." +msgstr "" + +#: ../Doc/library/operator.rst:138 +msgid "Return ``a * b``, for *a* and *b* numbers." +msgstr "" + +#: ../Doc/library/operator.rst:144 +msgid "Return ``a @ b``." +msgstr "" + +#: ../Doc/library/operator.rst:152 +msgid "Return *obj* negated (``-obj``)." +msgstr "" + +#: ../Doc/library/operator.rst:158 +msgid "Return the bitwise or of *a* and *b*." +msgstr "" + +#: ../Doc/library/operator.rst:164 +msgid "Return *obj* positive (``+obj``)." +msgstr "" + +#: ../Doc/library/operator.rst:170 +msgid "Return ``a ** b``, for *a* and *b* numbers." +msgstr "" + +#: ../Doc/library/operator.rst:176 +msgid "Return *a* shifted right by *b*." +msgstr "" + +#: ../Doc/library/operator.rst:182 +msgid "Return ``a - b``." +msgstr "" + +#: ../Doc/library/operator.rst:188 +msgid "" +"Return ``a / b`` where 2/3 is .66 rather than 0. This is also known as " +"\"true\" division." +msgstr "" + +#: ../Doc/library/operator.rst:195 +msgid "Return the bitwise exclusive or of *a* and *b*." +msgstr "" + +#: ../Doc/library/operator.rst:198 +msgid "" +"Operations which work with sequences (some of them with mappings too) " +"include:" +msgstr "" + +#: ../Doc/library/operator.rst:203 +msgid "Return ``a + b`` for *a* and *b* sequences." +msgstr "" + +#: ../Doc/library/operator.rst:209 +msgid "Return the outcome of the test ``b in a``. Note the reversed operands." +msgstr "" + +#: ../Doc/library/operator.rst:214 +msgid "Return the number of occurrences of *b* in *a*." +msgstr "" + +#: ../Doc/library/operator.rst:220 +msgid "Remove the value of *a* at index *b*." +msgstr "" + +#: ../Doc/library/operator.rst:226 +msgid "Return the value of *a* at index *b*." +msgstr "" + +#: ../Doc/library/operator.rst:231 +msgid "Return the index of the first of occurrence of *b* in *a*." +msgstr "" + +#: ../Doc/library/operator.rst:237 +msgid "Set the value of *a* at index *b* to *c*." +msgstr "" + +#: ../Doc/library/operator.rst:242 +msgid "" +"Return an estimated length for the object *o*. First try to return its " +"actual length, then an estimate using :meth:`object.__length_hint__`, and " +"finally return the default value." +msgstr "" + +#: ../Doc/library/operator.rst:248 +msgid "" +"The :mod:`operator` module also defines tools for generalized attribute and " +"item lookups. These are useful for making fast field extractors as " +"arguments for :func:`map`, :func:`sorted`, :meth:`itertools.groupby`, or " +"other functions that expect a function argument." +msgstr "" + +#: ../Doc/library/operator.rst:257 +msgid "" +"Return a callable object that fetches *attr* from its operand. If more than " +"one attribute is requested, returns a tuple of attributes. The attribute " +"names can also contain dots. For example:" +msgstr "" + +#: ../Doc/library/operator.rst:261 +msgid "After ``f = attrgetter('name')``, the call ``f(b)`` returns ``b.name``." +msgstr "" + +#: ../Doc/library/operator.rst:263 +msgid "" +"After ``f = attrgetter('name', 'date')``, the call ``f(b)`` returns ``(b." +"name, b.date)``." +msgstr "" + +#: ../Doc/library/operator.rst:266 +msgid "" +"After ``f = attrgetter('name.first', 'name.last')``, the call ``f(b)`` " +"returns ``(b.name.first, b.name.last)``." +msgstr "" + +#: ../Doc/library/operator.rst:292 +msgid "" +"Return a callable object that fetches *item* from its operand using the " +"operand's :meth:`__getitem__` method. If multiple items are specified, " +"returns a tuple of lookup values. For example:" +msgstr "" + +#: ../Doc/library/operator.rst:296 +msgid "After ``f = itemgetter(2)``, the call ``f(r)`` returns ``r[2]``." +msgstr "" + +#: ../Doc/library/operator.rst:298 +msgid "" +"After ``g = itemgetter(2, 5, 3)``, the call ``g(r)`` returns ``(r[2], r[5], " +"r[3])``." +msgstr "" + +#: ../Doc/library/operator.rst:313 +msgid "" +"The items can be any type accepted by the operand's :meth:`__getitem__` " +"method. Dictionaries accept any hashable value. Lists, tuples, and strings " +"accept an index or a slice:" +msgstr "" + +#: ../Doc/library/operator.rst:325 +msgid "" +"Example of using :func:`itemgetter` to retrieve specific fields from a tuple " +"record:" +msgstr "" + +#: ../Doc/library/operator.rst:338 +msgid "" +"Return a callable object that calls the method *name* on its operand. If " +"additional arguments and/or keyword arguments are given, they will be given " +"to the method as well. For example:" +msgstr "" + +#: ../Doc/library/operator.rst:342 +msgid "" +"After ``f = methodcaller('name')``, the call ``f(b)`` returns ``b.name()``." +msgstr "" + +#: ../Doc/library/operator.rst:344 +msgid "" +"After ``f = methodcaller('name', 'foo', bar=1)``, the call ``f(b)`` returns " +"``b.name('foo', bar=1)``." +msgstr "" + +#: ../Doc/library/operator.rst:358 +msgid "Mapping Operators to Functions" +msgstr "" + +#: ../Doc/library/operator.rst:360 +msgid "" +"This table shows how abstract operations correspond to operator symbols in " +"the Python syntax and the functions in the :mod:`operator` module." +msgstr "" + +#: ../Doc/library/operator.rst:364 ../Doc/library/xml.etree.elementtree.rst:408 +msgid "Syntax" +msgstr "" + +#: ../Doc/library/operator.rst:364 +msgid "Function" +msgstr "" + +#: ../Doc/library/operator.rst:366 +msgid "Addition" +msgstr "" + +#: ../Doc/library/operator.rst:366 +msgid "``a + b``" +msgstr "" + +#: ../Doc/library/operator.rst:366 +msgid "``add(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:368 +msgid "Concatenation" +msgstr "" + +#: ../Doc/library/operator.rst:368 +msgid "``seq1 + seq2``" +msgstr "" + +#: ../Doc/library/operator.rst:368 +msgid "``concat(seq1, seq2)``" +msgstr "" + +#: ../Doc/library/operator.rst:370 +msgid "Containment Test" +msgstr "" + +#: ../Doc/library/operator.rst:370 +msgid "``obj in seq``" +msgstr "" + +#: ../Doc/library/operator.rst:370 +msgid "``contains(seq, obj)``" +msgstr "" + +#: ../Doc/library/operator.rst:372 ../Doc/library/operator.rst:374 +msgid "Division" +msgstr "" + +#: ../Doc/library/operator.rst:372 +msgid "``a / b``" +msgstr "" + +#: ../Doc/library/operator.rst:372 +msgid "``truediv(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:374 +msgid "``a // b``" +msgstr "" + +#: ../Doc/library/operator.rst:374 +msgid "``floordiv(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:376 +msgid "Bitwise And" +msgstr "" + +#: ../Doc/library/operator.rst:376 +msgid "``a & b``" +msgstr "" + +#: ../Doc/library/operator.rst:376 +msgid "``and_(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:378 +msgid "Bitwise Exclusive Or" +msgstr "" + +#: ../Doc/library/operator.rst:378 +msgid "``a ^ b``" +msgstr "" + +#: ../Doc/library/operator.rst:378 +msgid "``xor(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:380 +msgid "Bitwise Inversion" +msgstr "" + +#: ../Doc/library/operator.rst:380 +msgid "``~ a``" +msgstr "" + +#: ../Doc/library/operator.rst:380 +msgid "``invert(a)``" +msgstr "" + +#: ../Doc/library/operator.rst:382 +msgid "Bitwise Or" +msgstr "" + +#: ../Doc/library/operator.rst:382 +msgid "``a | b``" +msgstr "" + +#: ../Doc/library/operator.rst:382 +msgid "``or_(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:384 +msgid "Exponentiation" +msgstr "" + +#: ../Doc/library/operator.rst:384 +msgid "``a ** b``" +msgstr "" + +#: ../Doc/library/operator.rst:384 +msgid "``pow(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:386 ../Doc/library/operator.rst:388 +msgid "Identity" +msgstr "" + +#: ../Doc/library/operator.rst:386 ../Doc/library/unittest.rst:791 +msgid "``a is b``" +msgstr "" + +#: ../Doc/library/operator.rst:386 +msgid "``is_(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:388 ../Doc/library/unittest.rst:794 +msgid "``a is not b``" +msgstr "" + +#: ../Doc/library/operator.rst:388 +msgid "``is_not(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:390 +msgid "Indexed Assignment" +msgstr "" + +#: ../Doc/library/operator.rst:390 +msgid "``obj[k] = v``" +msgstr "" + +#: ../Doc/library/operator.rst:390 +msgid "``setitem(obj, k, v)``" +msgstr "" + +#: ../Doc/library/operator.rst:392 +msgid "Indexed Deletion" +msgstr "" + +#: ../Doc/library/operator.rst:392 +msgid "``del obj[k]``" +msgstr "" + +#: ../Doc/library/operator.rst:392 +msgid "``delitem(obj, k)``" +msgstr "" + +#: ../Doc/library/operator.rst:394 +msgid "Indexing" +msgstr "" + +#: ../Doc/library/operator.rst:394 +msgid "``obj[k]``" +msgstr "" + +#: ../Doc/library/operator.rst:394 +msgid "``getitem(obj, k)``" +msgstr "" + +#: ../Doc/library/operator.rst:396 +msgid "Left Shift" +msgstr "" + +#: ../Doc/library/operator.rst:396 +msgid "``a << b``" +msgstr "" + +#: ../Doc/library/operator.rst:396 +msgid "``lshift(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:398 +msgid "Modulo" +msgstr "" + +#: ../Doc/library/operator.rst:398 +msgid "``a % b``" +msgstr "" + +#: ../Doc/library/operator.rst:398 +msgid "``mod(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:400 +msgid "Multiplication" +msgstr "" + +#: ../Doc/library/operator.rst:400 +msgid "``a * b``" +msgstr "" + +#: ../Doc/library/operator.rst:400 +msgid "``mul(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:402 +msgid "Matrix Multiplication" +msgstr "" + +#: ../Doc/library/operator.rst:402 +msgid "``a @ b``" +msgstr "" + +#: ../Doc/library/operator.rst:402 +msgid "``matmul(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:404 +msgid "Negation (Arithmetic)" +msgstr "" + +#: ../Doc/library/operator.rst:404 +msgid "``- a``" +msgstr "" + +#: ../Doc/library/operator.rst:404 +msgid "``neg(a)``" +msgstr "" + +#: ../Doc/library/operator.rst:406 +msgid "Negation (Logical)" +msgstr "" + +#: ../Doc/library/operator.rst:406 +msgid "``not a``" +msgstr "" + +#: ../Doc/library/operator.rst:406 +msgid "``not_(a)``" +msgstr "" + +#: ../Doc/library/operator.rst:408 +msgid "Positive" +msgstr "" + +#: ../Doc/library/operator.rst:408 +msgid "``+ a``" +msgstr "" + +#: ../Doc/library/operator.rst:408 +msgid "``pos(a)``" +msgstr "" + +#: ../Doc/library/operator.rst:410 +msgid "Right Shift" +msgstr "" + +#: ../Doc/library/operator.rst:410 +msgid "``a >> b``" +msgstr "" + +#: ../Doc/library/operator.rst:410 +msgid "``rshift(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:412 +msgid "Slice Assignment" +msgstr "" + +#: ../Doc/library/operator.rst:412 +msgid "``seq[i:j] = values``" +msgstr "" + +#: ../Doc/library/operator.rst:412 +msgid "``setitem(seq, slice(i, j), values)``" +msgstr "" + +#: ../Doc/library/operator.rst:414 +msgid "Slice Deletion" +msgstr "" + +#: ../Doc/library/operator.rst:414 +msgid "``del seq[i:j]``" +msgstr "" + +#: ../Doc/library/operator.rst:414 +msgid "``delitem(seq, slice(i, j))``" +msgstr "" + +#: ../Doc/library/operator.rst:416 +msgid "Slicing" +msgstr "" + +#: ../Doc/library/operator.rst:416 +msgid "``seq[i:j]``" +msgstr "" + +#: ../Doc/library/operator.rst:416 +msgid "``getitem(seq, slice(i, j))``" +msgstr "" + +#: ../Doc/library/operator.rst:418 +msgid "String Formatting" +msgstr "" + +#: ../Doc/library/operator.rst:418 +msgid "``s % obj``" +msgstr "" + +#: ../Doc/library/operator.rst:418 +msgid "``mod(s, obj)``" +msgstr "" + +#: ../Doc/library/operator.rst:420 +msgid "Subtraction" +msgstr "" + +#: ../Doc/library/operator.rst:420 +msgid "``a - b``" +msgstr "" + +#: ../Doc/library/operator.rst:420 +msgid "``sub(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:422 +msgid "Truth Test" +msgstr "" + +#: ../Doc/library/operator.rst:422 +msgid "``obj``" +msgstr "" + +#: ../Doc/library/operator.rst:422 +msgid "``truth(obj)``" +msgstr "" + +#: ../Doc/library/operator.rst:424 ../Doc/library/operator.rst:426 +#: ../Doc/library/operator.rst:432 ../Doc/library/operator.rst:434 +msgid "Ordering" +msgstr "" + +#: ../Doc/library/operator.rst:424 ../Doc/library/unittest.rst:1105 +msgid "``a < b``" +msgstr "" + +#: ../Doc/library/operator.rst:424 +msgid "``lt(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:426 ../Doc/library/unittest.rst:1108 +msgid "``a <= b``" +msgstr "" + +#: ../Doc/library/operator.rst:426 +msgid "``le(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:428 +msgid "Equality" +msgstr "" + +#: ../Doc/library/operator.rst:428 ../Doc/library/unittest.rst:779 +msgid "``a == b``" +msgstr "" + +#: ../Doc/library/operator.rst:428 +msgid "``eq(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:430 +msgid "Difference" +msgstr "" + +#: ../Doc/library/operator.rst:430 ../Doc/library/unittest.rst:782 +msgid "``a != b``" +msgstr "" + +#: ../Doc/library/operator.rst:430 +msgid "``ne(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:432 ../Doc/library/unittest.rst:1102 +msgid "``a >= b``" +msgstr "" + +#: ../Doc/library/operator.rst:432 +msgid "``ge(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:434 ../Doc/library/unittest.rst:1099 +msgid "``a > b``" +msgstr "" + +#: ../Doc/library/operator.rst:434 +msgid "``gt(a, b)``" +msgstr "" + +#: ../Doc/library/operator.rst:438 +msgid "Inplace Operators" +msgstr "" + +#: ../Doc/library/operator.rst:440 +msgid "" +"Many operations have an \"in-place\" version. Listed below are functions " +"providing a more primitive access to in-place operators than the usual " +"syntax does; for example, the :term:`statement` ``x += y`` is equivalent to " +"``x = operator.iadd(x, y)``. Another way to put it is to say that ``z = " +"operator.iadd(x, y)`` is equivalent to the compound statement ``z = x; z += " +"y``." +msgstr "" + +#: ../Doc/library/operator.rst:447 +msgid "" +"In those examples, note that when an in-place method is called, the " +"computation and assignment are performed in two separate steps. The in-" +"place functions listed below only do the first step, calling the in-place " +"method. The second step, assignment, is not handled." +msgstr "" + +#: ../Doc/library/operator.rst:452 +msgid "" +"For immutable targets such as strings, numbers, and tuples, the updated " +"value is computed, but not assigned back to the input variable:" +msgstr "" + +#: ../Doc/library/operator.rst:461 +msgid "" +"For mutable targets such as lists and dictionaries, the inplace method will " +"perform the update, so no subsequent assignment is necessary:" +msgstr "" + +#: ../Doc/library/operator.rst:473 +msgid "``a = iadd(a, b)`` is equivalent to ``a += b``." +msgstr "" + +#: ../Doc/library/operator.rst:479 +msgid "``a = iand(a, b)`` is equivalent to ``a &= b``." +msgstr "" + +#: ../Doc/library/operator.rst:485 +msgid "" +"``a = iconcat(a, b)`` is equivalent to ``a += b`` for *a* and *b* sequences." +msgstr "" + +#: ../Doc/library/operator.rst:491 +msgid "``a = ifloordiv(a, b)`` is equivalent to ``a //= b``." +msgstr "" + +#: ../Doc/library/operator.rst:497 +msgid "``a = ilshift(a, b)`` is equivalent to ``a <<= b``." +msgstr "" + +#: ../Doc/library/operator.rst:503 +msgid "``a = imod(a, b)`` is equivalent to ``a %= b``." +msgstr "" + +#: ../Doc/library/operator.rst:509 +msgid "``a = imul(a, b)`` is equivalent to ``a *= b``." +msgstr "" + +#: ../Doc/library/operator.rst:515 +msgid "``a = imatmul(a, b)`` is equivalent to ``a @= b``." +msgstr "" + +#: ../Doc/library/operator.rst:523 +msgid "``a = ior(a, b)`` is equivalent to ``a |= b``." +msgstr "" + +#: ../Doc/library/operator.rst:529 +msgid "``a = ipow(a, b)`` is equivalent to ``a **= b``." +msgstr "" + +#: ../Doc/library/operator.rst:535 +msgid "``a = irshift(a, b)`` is equivalent to ``a >>= b``." +msgstr "" + +#: ../Doc/library/operator.rst:541 +msgid "``a = isub(a, b)`` is equivalent to ``a -= b``." +msgstr "" + +#: ../Doc/library/operator.rst:547 +msgid "``a = itruediv(a, b)`` is equivalent to ``a /= b``." +msgstr "" + +#: ../Doc/library/operator.rst:553 +msgid "``a = ixor(a, b)`` is equivalent to ``a ^= b``." +msgstr "" + +#: ../Doc/library/optparse.rst:2 +msgid ":mod:`optparse` --- Parser for command line options" +msgstr "" + +#: ../Doc/library/optparse.rst:11 +msgid "**Source code:** :source:`Lib/optparse.py`" +msgstr "" + +#: ../Doc/library/optparse.rst:13 +msgid "" +"The :mod:`optparse` module is deprecated and will not be developed further; " +"development will continue with the :mod:`argparse` module." +msgstr "" + +#: ../Doc/library/optparse.rst:19 +msgid "" +":mod:`optparse` is a more convenient, flexible, and powerful library for " +"parsing command-line options than the old :mod:`getopt` module. :mod:" +"`optparse` uses a more declarative style of command-line parsing: you create " +"an instance of :class:`OptionParser`, populate it with options, and parse " +"the command line. :mod:`optparse` allows users to specify options in the " +"conventional GNU/POSIX syntax, and additionally generates usage and help " +"messages for you." +msgstr "" + +#: ../Doc/library/optparse.rst:26 +msgid "Here's an example of using :mod:`optparse` in a simple script::" +msgstr "" + +#: ../Doc/library/optparse.rst:39 +msgid "" +"With these few lines of code, users of your script can now do the \"usual " +"thing\" on the command-line, for example::" +msgstr "" + +#: ../Doc/library/optparse.rst:44 +msgid "" +"As it parses the command line, :mod:`optparse` sets attributes of the " +"``options`` object returned by :meth:`parse_args` based on user-supplied " +"command-line values. When :meth:`parse_args` returns from parsing this " +"command line, ``options.filename`` will be ``\"outfile\"`` and ``options." +"verbose`` will be ``False``. :mod:`optparse` supports both long and short " +"options, allows short options to be merged together, and allows options to " +"be associated with their arguments in a variety of ways. Thus, the " +"following command lines are all equivalent to the above example::" +msgstr "" + +#: ../Doc/library/optparse.rst:58 +msgid "Additionally, users can run one of ::" +msgstr "" + +#: ../Doc/library/optparse.rst:63 +msgid "" +"and :mod:`optparse` will print out a brief summary of your script's options:" +msgstr "" + +#: ../Doc/library/optparse.rst:74 +msgid "" +"where the value of *yourscript* is determined at runtime (normally from " +"``sys.argv[0]``)." +msgstr "" + +#: ../Doc/library/optparse.rst:81 +msgid "Background" +msgstr "" + +#: ../Doc/library/optparse.rst:83 +msgid "" +":mod:`optparse` was explicitly designed to encourage the creation of " +"programs with straightforward, conventional command-line interfaces. To " +"that end, it supports only the most common command-line syntax and semantics " +"conventionally used under Unix. If you are unfamiliar with these " +"conventions, read this section to acquaint yourself with them." +msgstr "" + +#: ../Doc/library/optparse.rst:93 +msgid "Terminology" +msgstr "" + +#: ../Doc/library/optparse.rst:104 +msgid "argument" +msgstr "" + +#: ../Doc/library/optparse.rst:96 +msgid "" +"a string entered on the command-line, and passed by the shell to ``execl()`` " +"or ``execv()``. In Python, arguments are elements of ``sys.argv[1:]`` " +"(``sys.argv[0]`` is the name of the program being executed). Unix shells " +"also use the term \"word\"." +msgstr "" + +#: ../Doc/library/optparse.rst:101 +msgid "" +"It is occasionally desirable to substitute an argument list other than ``sys." +"argv[1:]``, so you should read \"argument\" as \"an element of ``sys." +"argv[1:]``, or of some other list provided as a substitute for ``sys." +"argv[1:]``\"." +msgstr "" + +#: ../Doc/library/optparse.rst:134 +msgid "option" +msgstr "" + +#: ../Doc/library/optparse.rst:107 +msgid "" +"an argument used to supply extra information to guide or customize the " +"execution of a program. There are many different syntaxes for options; the " +"traditional Unix syntax is a hyphen (\"-\") followed by a single letter, e." +"g. ``-x`` or ``-F``. Also, traditional Unix syntax allows multiple options " +"to be merged into a single argument, e.g. ``-x -F`` is equivalent to ``-" +"xF``. The GNU project introduced ``--`` followed by a series of hyphen-" +"separated words, e.g. ``--file`` or ``--dry-run``. These are the only two " +"option syntaxes provided by :mod:`optparse`." +msgstr "" + +#: ../Doc/library/optparse.rst:116 +msgid "Some other option syntaxes that the world has seen include:" +msgstr "" + +#: ../Doc/library/optparse.rst:118 +msgid "" +"a hyphen followed by a few letters, e.g. ``-pf`` (this is *not* the same as " +"multiple options merged into a single argument)" +msgstr "" + +#: ../Doc/library/optparse.rst:121 +msgid "" +"a hyphen followed by a whole word, e.g. ``-file`` (this is technically " +"equivalent to the previous syntax, but they aren't usually seen in the same " +"program)" +msgstr "" + +#: ../Doc/library/optparse.rst:125 +msgid "" +"a plus sign followed by a single letter, or a few letters, or a word, e.g. ``" +"+f``, ``+rgb``" +msgstr "" + +#: ../Doc/library/optparse.rst:128 +msgid "" +"a slash followed by a letter, or a few letters, or a word, e.g. ``/f``, ``/" +"file``" +msgstr "" + +#: ../Doc/library/optparse.rst:131 +msgid "" +"These option syntaxes are not supported by :mod:`optparse`, and they never " +"will be. This is deliberate: the first three are non-standard on any " +"environment, and the last only makes sense if you're exclusively targeting " +"VMS, MS-DOS, and/or Windows." +msgstr "" + +#: ../Doc/library/optparse.rst:160 +msgid "option argument" +msgstr "" + +#: ../Doc/library/optparse.rst:137 +msgid "" +"an argument that follows an option, is closely associated with that option, " +"and is consumed from the argument list when that option is. With :mod:" +"`optparse`, option arguments may either be in a separate argument from their " +"option:" +msgstr "" + +#: ../Doc/library/optparse.rst:147 +msgid "or included in the same argument:" +msgstr "" + +#: ../Doc/library/optparse.rst:154 +msgid "" +"Typically, a given option either takes an argument or it doesn't. Lots of " +"people want an \"optional option arguments\" feature, meaning that some " +"options will take an argument if they see it, and won't if they don't. This " +"is somewhat controversial, because it makes parsing ambiguous: if ``-a`` " +"takes an optional argument and ``-b`` is another option entirely, how do we " +"interpret ``-ab``? Because of this ambiguity, :mod:`optparse` does not " +"support this feature." +msgstr "" + +#: ../Doc/library/optparse.rst:165 +msgid "positional argument" +msgstr "" + +#: ../Doc/library/optparse.rst:163 +msgid "" +"something leftover in the argument list after options have been parsed, i.e. " +"after options and their arguments have been parsed and removed from the " +"argument list." +msgstr "" + +#: ../Doc/library/optparse.rst:171 +msgid "required option" +msgstr "" + +#: ../Doc/library/optparse.rst:168 +msgid "" +"an option that must be supplied on the command-line; note that the phrase " +"\"required option\" is self-contradictory in English. :mod:`optparse` " +"doesn't prevent you from implementing required options, but doesn't give you " +"much help at it either." +msgstr "" + +#: ../Doc/library/optparse.rst:173 +msgid "For example, consider this hypothetical command-line::" +msgstr "" + +#: ../Doc/library/optparse.rst:177 +msgid "" +"``-v`` and ``--report`` are both options. Assuming that ``--report`` takes " +"one argument, ``report.txt`` is an option argument. ``foo`` and ``bar`` are " +"positional arguments." +msgstr "" + +#: ../Doc/library/optparse.rst:185 +msgid "What are options for?" +msgstr "" + +#: ../Doc/library/optparse.rst:187 +msgid "" +"Options are used to provide extra information to tune or customize the " +"execution of a program. In case it wasn't clear, options are usually " +"*optional*. A program should be able to run just fine with no options " +"whatsoever. (Pick a random program from the Unix or GNU toolsets. Can it " +"run without any options at all and still make sense? The main exceptions " +"are ``find``, ``tar``, and ``dd``\\ ---all of which are mutant oddballs that " +"have been rightly criticized for their non-standard syntax and confusing " +"interfaces.)" +msgstr "" + +#: ../Doc/library/optparse.rst:195 +msgid "" +"Lots of people want their programs to have \"required options\". Think " +"about it. If it's required, then it's *not optional*! If there is a piece " +"of information that your program absolutely requires in order to run " +"successfully, that's what positional arguments are for." +msgstr "" + +#: ../Doc/library/optparse.rst:200 +msgid "" +"As an example of good command-line interface design, consider the humble " +"``cp`` utility, for copying files. It doesn't make much sense to try to " +"copy files without supplying a destination and at least one source. Hence, " +"``cp`` fails if you run it with no arguments. However, it has a flexible, " +"useful syntax that does not require any options at all::" +msgstr "" + +#: ../Doc/library/optparse.rst:209 +msgid "" +"You can get pretty far with just that. Most ``cp`` implementations provide " +"a bunch of options to tweak exactly how the files are copied: you can " +"preserve mode and modification time, avoid following symlinks, ask before " +"clobbering existing files, etc. But none of this distracts from the core " +"mission of ``cp``, which is to copy either one file to another, or several " +"files to another directory." +msgstr "" + +#: ../Doc/library/optparse.rst:220 +msgid "What are positional arguments for?" +msgstr "" + +#: ../Doc/library/optparse.rst:222 +msgid "" +"Positional arguments are for those pieces of information that your program " +"absolutely, positively requires to run." +msgstr "" + +#: ../Doc/library/optparse.rst:225 +msgid "" +"A good user interface should have as few absolute requirements as possible. " +"If your program requires 17 distinct pieces of information in order to run " +"successfully, it doesn't much matter *how* you get that information from the " +"user---most people will give up and walk away before they successfully run " +"the program. This applies whether the user interface is a command-line, a " +"configuration file, or a GUI: if you make that many demands on your users, " +"most of them will simply give up." +msgstr "" + +#: ../Doc/library/optparse.rst:233 +msgid "" +"In short, try to minimize the amount of information that users are " +"absolutely required to supply---use sensible defaults whenever possible. Of " +"course, you also want to make your programs reasonably flexible. That's " +"what options are for. Again, it doesn't matter if they are entries in a " +"config file, widgets in the \"Preferences\" dialog of a GUI, or command-line " +"options---the more options you implement, the more flexible your program is, " +"and the more complicated its implementation becomes. Too much flexibility " +"has drawbacks as well, of course; too many options can overwhelm users and " +"make your code much harder to maintain." +msgstr "" + +#: ../Doc/library/optparse.rst:248 +msgid "" +"While :mod:`optparse` is quite flexible and powerful, it's also " +"straightforward to use in most cases. This section covers the code patterns " +"that are common to any :mod:`optparse`\\ -based program." +msgstr "" + +#: ../Doc/library/optparse.rst:252 +msgid "" +"First, you need to import the OptionParser class; then, early in the main " +"program, create an OptionParser instance::" +msgstr "" + +#: ../Doc/library/optparse.rst:259 +msgid "Then you can start defining options. The basic syntax is::" +msgstr "" + +#: ../Doc/library/optparse.rst:264 +msgid "" +"Each option has one or more option strings, such as ``-f`` or ``--file``, " +"and several option attributes that tell :mod:`optparse` what to expect and " +"what to do when it encounters that option on the command line." +msgstr "" + +#: ../Doc/library/optparse.rst:268 +msgid "" +"Typically, each option will have one short option string and one long option " +"string, e.g.::" +msgstr "" + +#: ../Doc/library/optparse.rst:273 +msgid "" +"You're free to define as many short option strings and as many long option " +"strings as you like (including zero), as long as there is at least one " +"option string overall." +msgstr "" + +#: ../Doc/library/optparse.rst:277 +msgid "" +"The option strings passed to :meth:`OptionParser.add_option` are effectively " +"labels for the option defined by that call. For brevity, we will frequently " +"refer to *encountering an option* on the command line; in reality, :mod:" +"`optparse` encounters *option strings* and looks up options from them." +msgstr "" + +#: ../Doc/library/optparse.rst:283 +msgid "" +"Once all of your options are defined, instruct :mod:`optparse` to parse your " +"program's command line::" +msgstr "" + +#: ../Doc/library/optparse.rst:288 +msgid "" +"(If you like, you can pass a custom argument list to :meth:`parse_args`, but " +"that's rarely necessary: by default it uses ``sys.argv[1:]``.)" +msgstr "" + +#: ../Doc/library/optparse.rst:291 +msgid ":meth:`parse_args` returns two values:" +msgstr "" + +#: ../Doc/library/optparse.rst:293 +msgid "" +"``options``, an object containing values for all of your options---e.g. if " +"``--file`` takes a single string argument, then ``options.file`` will be the " +"filename supplied by the user, or ``None`` if the user did not supply that " +"option" +msgstr "" + +#: ../Doc/library/optparse.rst:298 +msgid "" +"``args``, the list of positional arguments leftover after parsing options" +msgstr "" + +#: ../Doc/library/optparse.rst:300 +msgid "" +"This tutorial section only covers the four most important option " +"attributes: :attr:`~Option.action`, :attr:`~Option.type`, :attr:`~Option." +"dest` (destination), and :attr:`~Option.help`. Of these, :attr:`~Option." +"action` is the most fundamental." +msgstr "" + +#: ../Doc/library/optparse.rst:309 +msgid "Understanding option actions" +msgstr "" + +#: ../Doc/library/optparse.rst:311 +msgid "" +"Actions tell :mod:`optparse` what to do when it encounters an option on the " +"command line. There is a fixed set of actions hard-coded into :mod:" +"`optparse`; adding new actions is an advanced topic covered in section :ref:" +"`optparse-extending-optparse`. Most actions tell :mod:`optparse` to store a " +"value in some variable---for example, take a string from the command line " +"and store it in an attribute of ``options``." +msgstr "" + +#: ../Doc/library/optparse.rst:318 +msgid "" +"If you don't specify an option action, :mod:`optparse` defaults to ``store``." +msgstr "" + +#: ../Doc/library/optparse.rst:324 +msgid "The store action" +msgstr "" + +#: ../Doc/library/optparse.rst:326 +msgid "" +"The most common option action is ``store``, which tells :mod:`optparse` to " +"take the next argument (or the remainder of the current argument), ensure " +"that it is of the correct type, and store it to your chosen destination." +msgstr "" + +#: ../Doc/library/optparse.rst:335 +msgid "" +"Now let's make up a fake command line and ask :mod:`optparse` to parse it::" +msgstr "" + +#: ../Doc/library/optparse.rst:340 +msgid "" +"When :mod:`optparse` sees the option string ``-f``, it consumes the next " +"argument, ``foo.txt``, and stores it in ``options.filename``. So, after " +"this call to :meth:`parse_args`, ``options.filename`` is ``\"foo.txt\"``." +msgstr "" + +#: ../Doc/library/optparse.rst:344 +msgid "" +"Some other option types supported by :mod:`optparse` are ``int`` and " +"``float``. Here's an option that expects an integer argument::" +msgstr "" + +#: ../Doc/library/optparse.rst:349 +msgid "" +"Note that this option has no long option string, which is perfectly " +"acceptable. Also, there's no explicit action, since the default is ``store``." +msgstr "" + +#: ../Doc/library/optparse.rst:352 +msgid "" +"Let's parse another fake command-line. This time, we'll jam the option " +"argument right up against the option: since ``-n42`` (one argument) is " +"equivalent to ``-n 42`` (two arguments), the code ::" +msgstr "" + +#: ../Doc/library/optparse.rst:359 +msgid "will print ``42``." +msgstr "" + +#: ../Doc/library/optparse.rst:361 +msgid "" +"If you don't specify a type, :mod:`optparse` assumes ``string``. Combined " +"with the fact that the default action is ``store``, that means our first " +"example can be a lot shorter::" +msgstr "" + +#: ../Doc/library/optparse.rst:367 +msgid "" +"If you don't supply a destination, :mod:`optparse` figures out a sensible " +"default from the option strings: if the first long option string is ``--foo-" +"bar``, then the default destination is ``foo_bar``. If there are no long " +"option strings, :mod:`optparse` looks at the first short option string: the " +"default destination for ``-f`` is ``f``." +msgstr "" + +#: ../Doc/library/optparse.rst:373 +msgid "" +":mod:`optparse` also includes the built-in ``complex`` type. Adding types " +"is covered in section :ref:`optparse-extending-optparse`." +msgstr "" + +#: ../Doc/library/optparse.rst:380 +msgid "Handling boolean (flag) options" +msgstr "" + +#: ../Doc/library/optparse.rst:382 +msgid "" +"Flag options---set a variable to true or false when a particular option is " +"seen ---are quite common. :mod:`optparse` supports them with two separate " +"actions, ``store_true`` and ``store_false``. For example, you might have a " +"``verbose`` flag that is turned on with ``-v`` and off with ``-q``::" +msgstr "" + +#: ../Doc/library/optparse.rst:390 +msgid "" +"Here we have two different options with the same destination, which is " +"perfectly OK. (It just means you have to be a bit careful when setting " +"default values--- see below.)" +msgstr "" + +#: ../Doc/library/optparse.rst:394 +msgid "" +"When :mod:`optparse` encounters ``-v`` on the command line, it sets " +"``options.verbose`` to ``True``; when it encounters ``-q``, ``options." +"verbose`` is set to ``False``." +msgstr "" + +#: ../Doc/library/optparse.rst:402 +msgid "Other actions" +msgstr "" + +#: ../Doc/library/optparse.rst:404 +msgid "Some other actions supported by :mod:`optparse` are:" +msgstr "" + +#: ../Doc/library/optparse.rst:407 ../Doc/library/optparse.rst:928 +msgid "``\"store_const\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:407 ../Doc/library/optparse.rst:928 +msgid "store a constant value" +msgstr "" + +#: ../Doc/library/optparse.rst:410 ../Doc/library/optparse.rst:937 +msgid "``\"append\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:410 ../Doc/library/optparse.rst:937 +msgid "append this option's argument to a list" +msgstr "" + +#: ../Doc/library/optparse.rst:413 ../Doc/library/optparse.rst:943 +msgid "``\"count\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:413 ../Doc/library/optparse.rst:943 +msgid "increment a counter by one" +msgstr "" + +#: ../Doc/library/optparse.rst:416 ../Doc/library/optparse.rst:946 +msgid "``\"callback\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:416 ../Doc/library/optparse.rst:946 +msgid "call a specified function" +msgstr "" + +#: ../Doc/library/optparse.rst:418 +msgid "" +"These are covered in section :ref:`optparse-reference-guide`, Reference " +"Guide and section :ref:`optparse-option-callbacks`." +msgstr "" + +#: ../Doc/library/optparse.rst:425 +msgid "Default values" +msgstr "" + +#: ../Doc/library/optparse.rst:427 +msgid "" +"All of the above examples involve setting some variable (the \"destination" +"\") when certain command-line options are seen. What happens if those " +"options are never seen? Since we didn't supply any defaults, they are all " +"set to ``None``. This is usually fine, but sometimes you want more " +"control. :mod:`optparse` lets you supply a default value for each " +"destination, which is assigned before the command line is parsed." +msgstr "" + +#: ../Doc/library/optparse.rst:434 +msgid "" +"First, consider the verbose/quiet example. If we want :mod:`optparse` to " +"set ``verbose`` to ``True`` unless ``-q`` is seen, then we can do this::" +msgstr "" + +#: ../Doc/library/optparse.rst:440 +msgid "" +"Since default values apply to the *destination* rather than to any " +"particular option, and these two options happen to have the same " +"destination, this is exactly equivalent::" +msgstr "" + +#: ../Doc/library/optparse.rst:447 +msgid "Consider this::" +msgstr "" + +#: ../Doc/library/optparse.rst:452 +msgid "" +"Again, the default value for ``verbose`` will be ``True``: the last default " +"value supplied for any particular destination is the one that counts." +msgstr "" + +#: ../Doc/library/optparse.rst:455 +msgid "" +"A clearer way to specify default values is the :meth:`set_defaults` method " +"of OptionParser, which you can call at any time before calling :meth:" +"`parse_args`::" +msgstr "" + +#: ../Doc/library/optparse.rst:462 +msgid "" +"As before, the last value specified for a given option destination is the " +"one that counts. For clarity, try to use one method or the other of setting " +"default values, not both." +msgstr "" + +#: ../Doc/library/optparse.rst:470 +msgid "Generating help" +msgstr "" + +#: ../Doc/library/optparse.rst:472 +msgid "" +":mod:`optparse`'s ability to generate help and usage text automatically is " +"useful for creating user-friendly command-line interfaces. All you have to " +"do is supply a :attr:`~Option.help` value for each option, and optionally a " +"short usage message for your whole program. Here's an OptionParser " +"populated with user-friendly (documented) options::" +msgstr "" + +#: ../Doc/library/optparse.rst:493 +msgid "" +"If :mod:`optparse` encounters either ``-h`` or ``--help`` on the command-" +"line, or if you just call :meth:`parser.print_help`, it prints the following " +"to standard output:" +msgstr "" + +#: ../Doc/library/optparse.rst:510 +msgid "" +"(If the help output is triggered by a help option, :mod:`optparse` exits " +"after printing the help text.)" +msgstr "" + +#: ../Doc/library/optparse.rst:513 +msgid "" +"There's a lot going on here to help :mod:`optparse` generate the best " +"possible help message:" +msgstr "" + +#: ../Doc/library/optparse.rst:516 +msgid "the script defines its own usage message::" +msgstr "" + +#: ../Doc/library/optparse.rst:520 +msgid "" +":mod:`optparse` expands ``%prog`` in the usage string to the name of the " +"current program, i.e. ``os.path.basename(sys.argv[0])``. The expanded " +"string is then printed before the detailed option help." +msgstr "" + +#: ../Doc/library/optparse.rst:524 +msgid "" +"If you don't supply a usage string, :mod:`optparse` uses a bland but " +"sensible default: ``\"Usage: %prog [options]\"``, which is fine if your " +"script doesn't take any positional arguments." +msgstr "" + +#: ../Doc/library/optparse.rst:528 +msgid "" +"every option defines a help string, and doesn't worry about line-" +"wrapping--- :mod:`optparse` takes care of wrapping lines and making the help " +"output look good." +msgstr "" + +#: ../Doc/library/optparse.rst:532 +msgid "" +"options that take a value indicate this fact in their automatically-" +"generated help message, e.g. for the \"mode\" option::" +msgstr "" + +#: ../Doc/library/optparse.rst:537 +msgid "" +"Here, \"MODE\" is called the meta-variable: it stands for the argument that " +"the user is expected to supply to ``-m``/``--mode``. By default, :mod:" +"`optparse` converts the destination variable name to uppercase and uses that " +"for the meta-variable. Sometimes, that's not what you want---for example, " +"the ``--filename`` option explicitly sets ``metavar=\"FILE\"``, resulting in " +"this automatically-generated option description::" +msgstr "" + +#: ../Doc/library/optparse.rst:546 +msgid "" +"This is important for more than just saving space, though: the manually " +"written help text uses the meta-variable ``FILE`` to clue the user in that " +"there's a connection between the semi-formal syntax ``-f FILE`` and the " +"informal semantic description \"write output to FILE\". This is a simple but " +"effective way to make your help text a lot clearer and more useful for end " +"users." +msgstr "" + +#: ../Doc/library/optparse.rst:552 +msgid "" +"options that have a default value can include ``%default`` in the help " +"string---\\ :mod:`optparse` will replace it with :func:`str` of the option's " +"default value. If an option has no default value (or the default value is " +"``None``), ``%default`` expands to ``none``." +msgstr "" + +#: ../Doc/library/optparse.rst:558 +msgid "Grouping Options" +msgstr "" + +#: ../Doc/library/optparse.rst:560 +msgid "" +"When dealing with many options, it is convenient to group these options for " +"better help output. An :class:`OptionParser` can contain several option " +"groups, each of which can contain several options." +msgstr "" + +#: ../Doc/library/optparse.rst:564 +msgid "An option group is obtained using the class :class:`OptionGroup`:" +msgstr "" + +#: ../Doc/library/optparse.rst:568 ../Doc/library/optparse.rst:1620 +msgid "where" +msgstr "" + +#: ../Doc/library/optparse.rst:570 +msgid "" +"parser is the :class:`OptionParser` instance the group will be insterted in " +"to" +msgstr "" + +#: ../Doc/library/optparse.rst:572 +msgid "title is the group title" +msgstr "" + +#: ../Doc/library/optparse.rst:573 +msgid "description, optional, is a long description of the group" +msgstr "" + +#: ../Doc/library/optparse.rst:575 +msgid "" +":class:`OptionGroup` inherits from :class:`OptionContainer` (like :class:" +"`OptionParser`) and so the :meth:`add_option` method can be used to add an " +"option to the group." +msgstr "" + +#: ../Doc/library/optparse.rst:579 +msgid "" +"Once all the options are declared, using the :class:`OptionParser` method :" +"meth:`add_option_group` the group is added to the previously defined parser." +msgstr "" + +#: ../Doc/library/optparse.rst:582 +msgid "" +"Continuing with the parser defined in the previous section, adding an :class:" +"`OptionGroup` to a parser is easy::" +msgstr "" + +#: ../Doc/library/optparse.rst:591 +msgid "This would result in the following help output:" +msgstr "" + +#: ../Doc/library/optparse.rst:612 +msgid "" +"A bit more complete example might involve using more than one group: still " +"extending the previous example::" +msgstr "" + +#: ../Doc/library/optparse.rst:629 +msgid "that results in the following output:" +msgstr "" + +#: ../Doc/library/optparse.rst:655 +msgid "" +"Another interesting method, in particular when working programmatically with " +"option groups is:" +msgstr "" + +#: ../Doc/library/optparse.rst:660 +msgid "" +"Return the :class:`OptionGroup` to which the short or long option string " +"*opt_str* (e.g. ``'-o'`` or ``'--option'``) belongs. If there's no such :" +"class:`OptionGroup`, return ``None``." +msgstr "" + +#: ../Doc/library/optparse.rst:667 +msgid "Printing a version string" +msgstr "" + +#: ../Doc/library/optparse.rst:669 +msgid "" +"Similar to the brief usage string, :mod:`optparse` can also print a version " +"string for your program. You have to supply the string as the ``version`` " +"argument to OptionParser::" +msgstr "" + +#: ../Doc/library/optparse.rst:675 +msgid "" +"``%prog`` is expanded just like it is in ``usage``. Apart from that, " +"``version`` can contain anything you like. When you supply it, :mod:" +"`optparse` automatically adds a ``--version`` option to your parser. If it " +"encounters this option on the command line, it expands your ``version`` " +"string (by replacing ``%prog``), prints it to stdout, and exits." +msgstr "" + +#: ../Doc/library/optparse.rst:681 +msgid "For example, if your script is called ``/usr/bin/foo``:" +msgstr "" + +#: ../Doc/library/optparse.rst:688 +msgid "" +"The following two methods can be used to print and get the ``version`` " +"string:" +msgstr "" + +#: ../Doc/library/optparse.rst:692 +msgid "" +"Print the version message for the current program (``self.version``) to " +"*file* (default stdout). As with :meth:`print_usage`, any occurrence of ``" +"%prog`` in ``self.version`` is replaced with the name of the current " +"program. Does nothing if ``self.version`` is empty or undefined." +msgstr "" + +#: ../Doc/library/optparse.rst:699 +msgid "" +"Same as :meth:`print_version` but returns the version string instead of " +"printing it." +msgstr "" + +#: ../Doc/library/optparse.rst:706 +msgid "How :mod:`optparse` handles errors" +msgstr "" + +#: ../Doc/library/optparse.rst:708 +msgid "" +"There are two broad classes of errors that :mod:`optparse` has to worry " +"about: programmer errors and user errors. Programmer errors are usually " +"erroneous calls to :func:`OptionParser.add_option`, e.g. invalid option " +"strings, unknown option attributes, missing option attributes, etc. These " +"are dealt with in the usual way: raise an exception (either :exc:`optparse." +"OptionError` or :exc:`TypeError`) and let the program crash." +msgstr "" + +#: ../Doc/library/optparse.rst:715 +msgid "" +"Handling user errors is much more important, since they are guaranteed to " +"happen no matter how stable your code is. :mod:`optparse` can automatically " +"detect some user errors, such as bad option arguments (passing ``-n 4x`` " +"where ``-n`` takes an integer argument), missing arguments (``-n`` at the " +"end of the command line, where ``-n`` takes an argument of any type). Also, " +"you can call :func:`OptionParser.error` to signal an application-defined " +"error condition::" +msgstr "" + +#: ../Doc/library/optparse.rst:728 +msgid "" +"In either case, :mod:`optparse` handles the error the same way: it prints " +"the program's usage message and an error message to standard error and exits " +"with error status 2." +msgstr "" + +#: ../Doc/library/optparse.rst:732 +msgid "" +"Consider the first example above, where the user passes ``4x`` to an option " +"that takes an integer:" +msgstr "" + +#: ../Doc/library/optparse.rst:742 +msgid "Or, where the user fails to pass a value at all:" +msgstr "" + +#: ../Doc/library/optparse.rst:751 +msgid "" +":mod:`optparse`\\ -generated error messages take care always to mention the " +"option involved in the error; be sure to do the same when calling :func:" +"`OptionParser.error` from your application code." +msgstr "" + +#: ../Doc/library/optparse.rst:755 +msgid "" +"If :mod:`optparse`'s default error-handling behaviour does not suit your " +"needs, you'll need to subclass OptionParser and override its :meth:" +"`~OptionParser.exit` and/or :meth:`~OptionParser.error` methods." +msgstr "" + +#: ../Doc/library/optparse.rst:763 +msgid "Putting it all together" +msgstr "" + +#: ../Doc/library/optparse.rst:765 +msgid "Here's what :mod:`optparse`\\ -based scripts usually look like::" +msgstr "" + +#: ../Doc/library/optparse.rst:793 +msgid "Reference Guide" +msgstr "" + +#: ../Doc/library/optparse.rst:799 +msgid "Creating the parser" +msgstr "" + +#: ../Doc/library/optparse.rst:801 +msgid "" +"The first step in using :mod:`optparse` is to create an OptionParser " +"instance." +msgstr "" + +#: ../Doc/library/optparse.rst:805 +msgid "" +"The OptionParser constructor has no required arguments, but a number of " +"optional keyword arguments. You should always pass them as keyword " +"arguments, i.e. do not rely on the order in which the arguments are declared." +msgstr "" + +#: ../Doc/library/optparse.rst:814 +msgid "``usage`` (default: ``\"%prog [options]\"``)" +msgstr "" + +#: ../Doc/library/optparse.rst:810 +msgid "" +"The usage summary to print when your program is run incorrectly or with a " +"help option. When :mod:`optparse` prints the usage string, it expands ``" +"%prog`` to ``os.path.basename(sys.argv[0])`` (or to ``prog`` if you passed " +"that keyword argument). To suppress a usage message, pass the special " +"value :data:`optparse.SUPPRESS_USAGE`." +msgstr "" + +#: ../Doc/library/optparse.rst:821 +msgid "``option_list`` (default: ``[]``)" +msgstr "" + +#: ../Doc/library/optparse.rst:817 +msgid "" +"A list of Option objects to populate the parser with. The options in " +"``option_list`` are added after any options in ``standard_option_list`` (a " +"class attribute that may be set by OptionParser subclasses), but before any " +"version or help options. Deprecated; use :meth:`add_option` after creating " +"the parser instead." +msgstr "" + +#: ../Doc/library/optparse.rst:824 +msgid "``option_class`` (default: optparse.Option)" +msgstr "" + +#: ../Doc/library/optparse.rst:824 +msgid "Class to use when adding options to the parser in :meth:`add_option`." +msgstr "" + +#: ../Doc/library/optparse.rst:830 +msgid "``version`` (default: ``None``)" +msgstr "" + +#: ../Doc/library/optparse.rst:827 +msgid "" +"A version string to print when the user supplies a version option. If you " +"supply a true value for ``version``, :mod:`optparse` automatically adds a " +"version option with the single option string ``--version``. The substring ``" +"%prog`` is expanded the same as for ``usage``." +msgstr "" + +#: ../Doc/library/optparse.rst:835 +msgid "``conflict_handler`` (default: ``\"error\"``)" +msgstr "" + +#: ../Doc/library/optparse.rst:833 +msgid "" +"Specifies what to do when options with conflicting option strings are added " +"to the parser; see section :ref:`optparse-conflicts-between-options`." +msgstr "" + +#: ../Doc/library/optparse.rst:841 +msgid "``description`` (default: ``None``)" +msgstr "" + +#: ../Doc/library/optparse.rst:838 +msgid "" +"A paragraph of text giving a brief overview of your program. :mod:`optparse` " +"reformats this paragraph to fit the current terminal width and prints it " +"when the user requests help (after ``usage``, but before the list of " +"options)." +msgstr "" + +#: ../Doc/library/optparse.rst:846 +msgid "``formatter`` (default: a new :class:`IndentedHelpFormatter`)" +msgstr "" + +#: ../Doc/library/optparse.rst:844 +msgid "" +"An instance of optparse.HelpFormatter that will be used for printing help " +"text. :mod:`optparse` provides two concrete classes for this purpose: " +"IndentedHelpFormatter and TitledHelpFormatter." +msgstr "" + +#: ../Doc/library/optparse.rst:850 +msgid "``add_help_option`` (default: ``True``)" +msgstr "" + +#: ../Doc/library/optparse.rst:849 +msgid "" +"If true, :mod:`optparse` will add a help option (with option strings ``-h`` " +"and ``--help``) to the parser." +msgstr "" + +#: ../Doc/library/optparse.rst:854 +msgid "``prog``" +msgstr "" + +#: ../Doc/library/optparse.rst:853 +msgid "" +"The string to use when expanding ``%prog`` in ``usage`` and ``version`` " +"instead of ``os.path.basename(sys.argv[0])``." +msgstr "" + +#: ../Doc/library/optparse.rst:856 +msgid "``epilog`` (default: ``None``)" +msgstr "" + +#: ../Doc/library/optparse.rst:857 +msgid "A paragraph of help text to print after the option help." +msgstr "" + +#: ../Doc/library/optparse.rst:862 +msgid "Populating the parser" +msgstr "" + +#: ../Doc/library/optparse.rst:864 +msgid "" +"There are several ways to populate the parser with options. The preferred " +"way is by using :meth:`OptionParser.add_option`, as shown in section :ref:" +"`optparse-tutorial`. :meth:`add_option` can be called in one of two ways:" +msgstr "" + +#: ../Doc/library/optparse.rst:868 +msgid "pass it an Option instance (as returned by :func:`make_option`)" +msgstr "" + +#: ../Doc/library/optparse.rst:870 +msgid "" +"pass it any combination of positional and keyword arguments that are " +"acceptable to :func:`make_option` (i.e., to the Option constructor), and it " +"will create the Option instance for you" +msgstr "" + +#: ../Doc/library/optparse.rst:874 +msgid "" +"The other alternative is to pass a list of pre-constructed Option instances " +"to the OptionParser constructor, as in::" +msgstr "" + +#: ../Doc/library/optparse.rst:885 +msgid "" +"(:func:`make_option` is a factory function for creating Option instances; " +"currently it is an alias for the Option constructor. A future version of :" +"mod:`optparse` may split Option into several classes, and :func:" +"`make_option` will pick the right class to instantiate. Do not instantiate " +"Option directly.)" +msgstr "" + +#: ../Doc/library/optparse.rst:894 +msgid "Defining options" +msgstr "" + +#: ../Doc/library/optparse.rst:896 +msgid "" +"Each Option instance represents a set of synonymous command-line option " +"strings, e.g. ``-f`` and ``--file``. You can specify any number of short or " +"long option strings, but you must specify at least one overall option string." +msgstr "" + +#: ../Doc/library/optparse.rst:900 +msgid "" +"The canonical way to create an :class:`Option` instance is with the :meth:" +"`add_option` method of :class:`OptionParser`." +msgstr "" + +#: ../Doc/library/optparse.rst:906 +msgid "To define an option with only a short option string::" +msgstr "" + +#: ../Doc/library/optparse.rst:910 +msgid "And to define an option with only a long option string::" +msgstr "" + +#: ../Doc/library/optparse.rst:914 +msgid "" +"The keyword arguments define attributes of the new Option object. The most " +"important option attribute is :attr:`~Option.action`, and it largely " +"determines which other attributes are relevant or required. If you pass " +"irrelevant option attributes, or fail to pass required ones, :mod:`optparse` " +"raises an :exc:`OptionError` exception explaining your mistake." +msgstr "" + +#: ../Doc/library/optparse.rst:920 +msgid "" +"An option's *action* determines what :mod:`optparse` does when it encounters " +"this option on the command-line. The standard option actions hard-coded " +"into :mod:`optparse` are:" +msgstr "" + +#: ../Doc/library/optparse.rst:925 +msgid "``\"store\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:925 +msgid "store this option's argument (default)" +msgstr "" + +#: ../Doc/library/optparse.rst:931 +msgid "``\"store_true\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:931 +msgid "store a true value" +msgstr "" + +#: ../Doc/library/optparse.rst:934 +msgid "``\"store_false\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:934 +msgid "store a false value" +msgstr "" + +#: ../Doc/library/optparse.rst:940 +msgid "``\"append_const\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:940 +msgid "append a constant value to a list" +msgstr "" + +#: ../Doc/library/optparse.rst:949 ../Doc/library/optparse.rst:1226 +msgid "``\"help\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:949 +msgid "" +"print a usage message including all options and the documentation for them" +msgstr "" + +#: ../Doc/library/optparse.rst:951 +msgid "" +"(If you don't supply an action, the default is ``\"store\"``. For this " +"action, you may also supply :attr:`~Option.type` and :attr:`~Option.dest` " +"option attributes; see :ref:`optparse-standard-option-actions`.)" +msgstr "" + +#: ../Doc/library/optparse.rst:955 +msgid "" +"As you can see, most actions involve storing or updating a value somewhere. :" +"mod:`optparse` always creates a special object for this, conventionally " +"called ``options`` (it happens to be an instance of :class:`optparse." +"Values`). Option arguments (and various other values) are stored as " +"attributes of this object, according to the :attr:`~Option.dest` " +"(destination) option attribute." +msgstr "" + +#: ../Doc/library/optparse.rst:961 +msgid "For example, when you call ::" +msgstr "" + +#: ../Doc/library/optparse.rst:965 +msgid "" +"one of the first things :mod:`optparse` does is create the ``options`` " +"object::" +msgstr "" + +#: ../Doc/library/optparse.rst:969 +msgid "If one of the options in this parser is defined with ::" +msgstr "" + +#: ../Doc/library/optparse.rst:973 +msgid "and the command-line being parsed includes any of the following::" +msgstr "" + +#: ../Doc/library/optparse.rst:980 +msgid "" +"then :mod:`optparse`, on seeing this option, will do the equivalent of ::" +msgstr "" + +#: ../Doc/library/optparse.rst:984 +msgid "" +"The :attr:`~Option.type` and :attr:`~Option.dest` option attributes are " +"almost as important as :attr:`~Option.action`, but :attr:`~Option.action` is " +"the only one that makes sense for *all* options." +msgstr "" + +#: ../Doc/library/optparse.rst:992 +msgid "Option attributes" +msgstr "" + +#: ../Doc/library/optparse.rst:994 +msgid "" +"The following option attributes may be passed as keyword arguments to :meth:" +"`OptionParser.add_option`. If you pass an option attribute that is not " +"relevant to a particular option, or fail to pass a required option " +"attribute, :mod:`optparse` raises :exc:`OptionError`." +msgstr "" + +#: ../Doc/library/optparse.rst:1001 +msgid "(default: ``\"store\"``)" +msgstr "" + +#: ../Doc/library/optparse.rst:1003 +msgid "" +"Determines :mod:`optparse`'s behaviour when this option is seen on the " +"command line; the available options are documented :ref:`here `." +msgstr "" + +#: ../Doc/library/optparse.rst:1009 +msgid "(default: ``\"string\"``)" +msgstr "" + +#: ../Doc/library/optparse.rst:1011 +msgid "" +"The argument type expected by this option (e.g., ``\"string\"`` or ``\"int" +"\"``); the available option types are documented :ref:`here `." +msgstr "" + +#: ../Doc/library/optparse.rst:1017 ../Doc/library/optparse.rst:1067 +msgid "(default: derived from option strings)" +msgstr "" + +#: ../Doc/library/optparse.rst:1019 +msgid "" +"If the option's action implies writing or modifying a value somewhere, this " +"tells :mod:`optparse` where to write it: :attr:`~Option.dest` names an " +"attribute of the ``options`` object that :mod:`optparse` builds as it parses " +"the command line." +msgstr "" + +#: ../Doc/library/optparse.rst:1026 +msgid "" +"The value to use for this option's destination if the option is not seen on " +"the command line. See also :meth:`OptionParser.set_defaults`." +msgstr "" + +#: ../Doc/library/optparse.rst:1031 +msgid "(default: 1)" +msgstr "" + +#: ../Doc/library/optparse.rst:1033 +msgid "" +"How many arguments of type :attr:`~Option.type` should be consumed when this " +"option is seen. If > 1, :mod:`optparse` will store a tuple of values to :" +"attr:`~Option.dest`." +msgstr "" + +#: ../Doc/library/optparse.rst:1039 +msgid "For actions that store a constant value, the constant value to store." +msgstr "" + +#: ../Doc/library/optparse.rst:1043 +msgid "" +"For options of type ``\"choice\"``, the list of strings the user may choose " +"from." +msgstr "" + +#: ../Doc/library/optparse.rst:1048 +msgid "" +"For options with action ``\"callback\"``, the callable to call when this " +"option is seen. See section :ref:`optparse-option-callbacks` for detail on " +"the arguments passed to the callable." +msgstr "" + +#: ../Doc/library/optparse.rst:1055 +msgid "" +"Additional positional and keyword arguments to pass to ``callback`` after " +"the four standard callback arguments." +msgstr "" + +#: ../Doc/library/optparse.rst:1060 +msgid "" +"Help text to print for this option when listing all available options after " +"the user supplies a :attr:`~Option.help` option (such as ``--help``). If no " +"help text is supplied, the option will be listed without help text. To hide " +"this option, use the special value :data:`optparse.SUPPRESS_HELP`." +msgstr "" + +#: ../Doc/library/optparse.rst:1069 +msgid "" +"Stand-in for the option argument(s) to use when printing help text. See " +"section :ref:`optparse-tutorial` for an example." +msgstr "" + +#: ../Doc/library/optparse.rst:1076 +msgid "Standard option actions" +msgstr "" + +#: ../Doc/library/optparse.rst:1078 +msgid "" +"The various option actions all have slightly different requirements and " +"effects. Most actions have several relevant option attributes which you may " +"specify to guide :mod:`optparse`'s behaviour; a few have required " +"attributes, which you must specify for any option using that action." +msgstr "" + +#: ../Doc/library/optparse.rst:1083 +msgid "" +"``\"store\"`` [relevant: :attr:`~Option.type`, :attr:`~Option.dest`, :attr:" +"`~Option.nargs`, :attr:`~Option.choices`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1086 +msgid "" +"The option must be followed by an argument, which is converted to a value " +"according to :attr:`~Option.type` and stored in :attr:`~Option.dest`. If :" +"attr:`~Option.nargs` > 1, multiple arguments will be consumed from the " +"command line; all will be converted according to :attr:`~Option.type` and " +"stored to :attr:`~Option.dest` as a tuple. See the :ref:`optparse-standard-" +"option-types` section." +msgstr "" + +#: ../Doc/library/optparse.rst:1093 +msgid "" +"If :attr:`~Option.choices` is supplied (a list or tuple of strings), the " +"type defaults to ``\"choice\"``." +msgstr "" + +#: ../Doc/library/optparse.rst:1096 +msgid "If :attr:`~Option.type` is not supplied, it defaults to ``\"string\"``." +msgstr "" + +#: ../Doc/library/optparse.rst:1098 +msgid "" +"If :attr:`~Option.dest` is not supplied, :mod:`optparse` derives a " +"destination from the first long option string (e.g., ``--foo-bar`` implies " +"``foo_bar``). If there are no long option strings, :mod:`optparse` derives a " +"destination from the first short option string (e.g., ``-f`` implies ``f``)." +msgstr "" + +#: ../Doc/library/optparse.rst:1108 +msgid "As it parses the command line ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1112 +msgid ":mod:`optparse` will set ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1118 +msgid "" +"``\"store_const\"`` [required: :attr:`~Option.const`; relevant: :attr:" +"`~Option.dest`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1121 +msgid "The value :attr:`~Option.const` is stored in :attr:`~Option.dest`." +msgstr "" + +#: ../Doc/library/optparse.rst:1132 +msgid "If ``--noisy`` is seen, :mod:`optparse` will set ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1136 +msgid "``\"store_true\"`` [relevant: :attr:`~Option.dest`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1138 +msgid "" +"A special case of ``\"store_const\"`` that stores a true value to :attr:" +"`~Option.dest`." +msgstr "" + +#: ../Doc/library/optparse.rst:1141 +msgid "``\"store_false\"`` [relevant: :attr:`~Option.dest`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1143 +msgid "Like ``\"store_true\"``, but stores a false value." +msgstr "" + +#: ../Doc/library/optparse.rst:1150 +msgid "" +"``\"append\"`` [relevant: :attr:`~Option.type`, :attr:`~Option.dest`, :attr:" +"`~Option.nargs`, :attr:`~Option.choices`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1153 +msgid "" +"The option must be followed by an argument, which is appended to the list " +"in :attr:`~Option.dest`. If no default value for :attr:`~Option.dest` is " +"supplied, an empty list is automatically created when :mod:`optparse` first " +"encounters this option on the command-line. If :attr:`~Option.nargs` > 1, " +"multiple arguments are consumed, and a tuple of length :attr:`~Option.nargs` " +"is appended to :attr:`~Option.dest`." +msgstr "" + +#: ../Doc/library/optparse.rst:1160 +msgid "" +"The defaults for :attr:`~Option.type` and :attr:`~Option.dest` are the same " +"as for the ``\"store\"`` action." +msgstr "" + +#: ../Doc/library/optparse.rst:1167 +msgid "" +"If ``-t3`` is seen on the command-line, :mod:`optparse` does the equivalent " +"of::" +msgstr "" + +#: ../Doc/library/optparse.rst:1173 +msgid "If, a little later on, ``--tracks=4`` is seen, it does::" +msgstr "" + +#: ../Doc/library/optparse.rst:1177 +msgid "" +"The ``append`` action calls the ``append`` method on the current value of " +"the option. This means that any default value specified must have an " +"``append`` method. It also means that if the default value is non-empty, " +"the default elements will be present in the parsed value for the option, " +"with any values from the command line appended after those default values::" +msgstr "" + +#: ../Doc/library/optparse.rst:1188 +msgid "" +"``\"append_const\"`` [required: :attr:`~Option.const`; relevant: :attr:" +"`~Option.dest`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1191 +msgid "" +"Like ``\"store_const\"``, but the value :attr:`~Option.const` is appended " +"to :attr:`~Option.dest`; as with ``\"append\"``, :attr:`~Option.dest` " +"defaults to ``None``, and an empty list is automatically created the first " +"time the option is encountered." +msgstr "" + +#: ../Doc/library/optparse.rst:1196 +msgid "``\"count\"`` [relevant: :attr:`~Option.dest`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1198 +msgid "" +"Increment the integer stored at :attr:`~Option.dest`. If no default value " +"is supplied, :attr:`~Option.dest` is set to zero before being incremented " +"the first time." +msgstr "" + +#: ../Doc/library/optparse.rst:1206 +msgid "" +"The first time ``-v`` is seen on the command line, :mod:`optparse` does the " +"equivalent of::" +msgstr "" + +#: ../Doc/library/optparse.rst:1212 +msgid "Every subsequent occurrence of ``-v`` results in ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1216 +msgid "" +"``\"callback\"`` [required: :attr:`~Option.callback`; relevant: :attr:" +"`~Option.type`, :attr:`~Option.nargs`, :attr:`~Option.callback_args`, :attr:" +"`~Option.callback_kwargs`]" +msgstr "" + +#: ../Doc/library/optparse.rst:1220 +msgid "" +"Call the function specified by :attr:`~Option.callback`, which is called " +"as ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1224 +msgid "See section :ref:`optparse-option-callbacks` for more detail." +msgstr "" + +#: ../Doc/library/optparse.rst:1228 +msgid "" +"Prints a complete help message for all the options in the current option " +"parser. The help message is constructed from the ``usage`` string passed to " +"OptionParser's constructor and the :attr:`~Option.help` string passed to " +"every option." +msgstr "" + +#: ../Doc/library/optparse.rst:1233 +msgid "" +"If no :attr:`~Option.help` string is supplied for an option, it will still " +"be listed in the help message. To omit an option entirely, use the special " +"value :data:`optparse.SUPPRESS_HELP`." +msgstr "" + +#: ../Doc/library/optparse.rst:1237 +msgid "" +":mod:`optparse` automatically adds a :attr:`~Option.help` option to all " +"OptionParsers, so you do not normally need to create one." +msgstr "" + +#: ../Doc/library/optparse.rst:1255 +msgid "" +"If :mod:`optparse` sees either ``-h`` or ``--help`` on the command line, it " +"will print something like the following help message to stdout (assuming " +"``sys.argv[0]`` is ``\"foo.py\"``):" +msgstr "" + +#: ../Doc/library/optparse.rst:1268 +msgid "" +"After printing the help message, :mod:`optparse` terminates your process " +"with ``sys.exit(0)``." +msgstr "" + +#: ../Doc/library/optparse.rst:1271 +msgid "``\"version\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:1273 +msgid "" +"Prints the version number supplied to the OptionParser to stdout and exits. " +"The version number is actually formatted and printed by the " +"``print_version()`` method of OptionParser. Generally only relevant if the " +"``version`` argument is supplied to the OptionParser constructor. As with :" +"attr:`~Option.help` options, you will rarely create ``version`` options, " +"since :mod:`optparse` automatically adds them when needed." +msgstr "" + +#: ../Doc/library/optparse.rst:1284 +msgid "Standard option types" +msgstr "" + +#: ../Doc/library/optparse.rst:1286 +msgid "" +":mod:`optparse` has five built-in option types: ``\"string\"``, ``\"int\"``, " +"``\"choice\"``, ``\"float\"`` and ``\"complex\"``. If you need to add new " +"option types, see section :ref:`optparse-extending-optparse`." +msgstr "" + +#: ../Doc/library/optparse.rst:1290 +msgid "" +"Arguments to string options are not checked or converted in any way: the " +"text on the command line is stored in the destination (or passed to the " +"callback) as-is." +msgstr "" + +#: ../Doc/library/optparse.rst:1293 +msgid "Integer arguments (type ``\"int\"``) are parsed as follows:" +msgstr "" + +#: ../Doc/library/optparse.rst:1295 +msgid "if the number starts with ``0x``, it is parsed as a hexadecimal number" +msgstr "" + +#: ../Doc/library/optparse.rst:1297 +msgid "if the number starts with ``0``, it is parsed as an octal number" +msgstr "" + +#: ../Doc/library/optparse.rst:1299 +msgid "if the number starts with ``0b``, it is parsed as a binary number" +msgstr "" + +#: ../Doc/library/optparse.rst:1301 +msgid "otherwise, the number is parsed as a decimal number" +msgstr "" + +#: ../Doc/library/optparse.rst:1304 +msgid "" +"The conversion is done by calling :func:`int` with the appropriate base (2, " +"8, 10, or 16). If this fails, so will :mod:`optparse`, although with a more " +"useful error message." +msgstr "" + +#: ../Doc/library/optparse.rst:1308 +msgid "" +"``\"float\"`` and ``\"complex\"`` option arguments are converted directly " +"with :func:`float` and :func:`complex`, with similar error-handling." +msgstr "" + +#: ../Doc/library/optparse.rst:1311 +msgid "" +"``\"choice\"`` options are a subtype of ``\"string\"`` options. The :attr:" +"`~Option.choices` option attribute (a sequence of strings) defines the set " +"of allowed option arguments. :func:`optparse.check_choice` compares user-" +"supplied option arguments against this master list and raises :exc:" +"`OptionValueError` if an invalid string is given." +msgstr "" + +#: ../Doc/library/optparse.rst:1323 +msgid "" +"The whole point of creating and populating an OptionParser is to call its :" +"meth:`parse_args` method::" +msgstr "" + +#: ../Doc/library/optparse.rst:1328 +msgid "where the input parameters are" +msgstr "" + +#: ../Doc/library/optparse.rst:1331 ../Doc/library/optparse.rst:1345 +#: ../Doc/library/optparse.rst:1664 +msgid "``args``" +msgstr "" + +#: ../Doc/library/optparse.rst:1331 +msgid "the list of arguments to process (default: ``sys.argv[1:]``)" +msgstr "" + +#: ../Doc/library/optparse.rst:1336 +msgid "``values``" +msgstr "" + +#: ../Doc/library/optparse.rst:1334 +msgid "" +"an :class:`optparse.Values` object to store option arguments in (default: a " +"new instance of :class:`Values`) -- if you give an existing object, the " +"option defaults will not be initialized on it" +msgstr "" + +#: ../Doc/library/optparse.rst:1338 +msgid "and the return values are" +msgstr "" + +#: ../Doc/library/optparse.rst:1342 +msgid "``options``" +msgstr "" + +#: ../Doc/library/optparse.rst:1341 +msgid "" +"the same object that was passed in as ``values``, or the optparse.Values " +"instance created by :mod:`optparse`" +msgstr "" + +#: ../Doc/library/optparse.rst:1345 +msgid "the leftover positional arguments after all options have been processed" +msgstr "" + +#: ../Doc/library/optparse.rst:1347 +msgid "" +"The most common usage is to supply neither keyword argument. If you supply " +"``values``, it will be modified with repeated :func:`setattr` calls (roughly " +"one for every option argument stored to an option destination) and returned " +"by :meth:`parse_args`." +msgstr "" + +#: ../Doc/library/optparse.rst:1352 +msgid "" +"If :meth:`parse_args` encounters any errors in the argument list, it calls " +"the OptionParser's :meth:`error` method with an appropriate end-user error " +"message. This ultimately terminates your process with an exit status of 2 " +"(the traditional Unix exit status for command-line errors)." +msgstr "" + +#: ../Doc/library/optparse.rst:1361 +msgid "Querying and manipulating your option parser" +msgstr "" + +#: ../Doc/library/optparse.rst:1363 +msgid "" +"The default behavior of the option parser can be customized slightly, and " +"you can also poke around your option parser and see what's there. " +"OptionParser provides several methods to help you out:" +msgstr "" + +#: ../Doc/library/optparse.rst:1369 +msgid "" +"Set parsing to stop on the first non-option. For example, if ``-a`` and ``-" +"b`` are both simple options that take no arguments, :mod:`optparse` normally " +"accepts this syntax::" +msgstr "" + +#: ../Doc/library/optparse.rst:1375 +msgid "and treats it as equivalent to ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1379 +msgid "" +"To disable this feature, call :meth:`disable_interspersed_args`. This " +"restores traditional Unix syntax, where option parsing stops with the first " +"non-option argument." +msgstr "" + +#: ../Doc/library/optparse.rst:1383 +msgid "" +"Use this if you have a command processor which runs another command which " +"has options of its own and you want to make sure these options don't get " +"confused. For example, each command might have a different set of options." +msgstr "" + +#: ../Doc/library/optparse.rst:1389 +msgid "" +"Set parsing to not stop on the first non-option, allowing interspersing " +"switches with command arguments. This is the default behavior." +msgstr "" + +#: ../Doc/library/optparse.rst:1394 +msgid "" +"Returns the Option instance with the option string *opt_str*, or ``None`` if " +"no options have that option string." +msgstr "" + +#: ../Doc/library/optparse.rst:1399 +msgid "" +"Return true if the OptionParser has an option with option string *opt_str* " +"(e.g., ``-q`` or ``--verbose``)." +msgstr "" + +#: ../Doc/library/optparse.rst:1404 +msgid "" +"If the :class:`OptionParser` has an option corresponding to *opt_str*, that " +"option is removed. If that option provided any other option strings, all of " +"those option strings become invalid. If *opt_str* does not occur in any " +"option belonging to this :class:`OptionParser`, raises :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/optparse.rst:1413 +msgid "Conflicts between options" +msgstr "" + +#: ../Doc/library/optparse.rst:1415 +msgid "" +"If you're not careful, it's easy to define options with conflicting option " +"strings::" +msgstr "" + +#: ../Doc/library/optparse.rst:1422 +msgid "" +"(This is particularly true if you've defined your own OptionParser subclass " +"with some standard options.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1425 +msgid "" +"Every time you add an option, :mod:`optparse` checks for conflicts with " +"existing options. If it finds any, it invokes the current conflict-handling " +"mechanism. You can set the conflict-handling mechanism either in the " +"constructor::" +msgstr "" + +#: ../Doc/library/optparse.rst:1431 +msgid "or with a separate call::" +msgstr "" + +#: ../Doc/library/optparse.rst:1435 +msgid "The available conflict handlers are:" +msgstr "" + +#: ../Doc/library/optparse.rst:1439 +msgid "``\"error\"`` (default)" +msgstr "" + +#: ../Doc/library/optparse.rst:1438 +msgid "" +"assume option conflicts are a programming error and raise :exc:" +"`OptionConflictError`" +msgstr "" + +#: ../Doc/library/optparse.rst:1443 +msgid "``\"resolve\"``" +msgstr "" + +#: ../Doc/library/optparse.rst:1442 +msgid "resolve option conflicts intelligently (see below)" +msgstr "" + +#: ../Doc/library/optparse.rst:1445 +msgid "" +"As an example, let's define an :class:`OptionParser` that resolves conflicts " +"intelligently and add conflicting options to it::" +msgstr "" + +#: ../Doc/library/optparse.rst:1452 +msgid "" +"At this point, :mod:`optparse` detects that a previously-added option is " +"already using the ``-n`` option string. Since ``conflict_handler`` is ``" +"\"resolve\"``, it resolves the situation by removing ``-n`` from the earlier " +"option's list of option strings. Now ``--dry-run`` is the only way for the " +"user to activate that option. If the user asks for help, the help message " +"will reflect that::" +msgstr "" + +#: ../Doc/library/optparse.rst:1463 +msgid "" +"It's possible to whittle away the option strings for a previously-added " +"option until there are none left, and the user has no way of invoking that " +"option from the command-line. In that case, :mod:`optparse` removes that " +"option completely, so it doesn't show up in help text or anywhere else. " +"Carrying on with our existing OptionParser::" +msgstr "" + +#: ../Doc/library/optparse.rst:1471 +msgid "" +"At this point, the original ``-n``/``--dry-run`` option is no longer " +"accessible, so :mod:`optparse` removes it, leaving this help text::" +msgstr "" + +#: ../Doc/library/optparse.rst:1485 +msgid "" +"OptionParser instances have several cyclic references. This should not be a " +"problem for Python's garbage collector, but you may wish to break the cyclic " +"references explicitly by calling :meth:`~OptionParser.destroy` on your " +"OptionParser once you are done with it. This is particularly useful in long-" +"running applications where large object graphs are reachable from your " +"OptionParser." +msgstr "" + +#: ../Doc/library/optparse.rst:1496 +msgid "Other methods" +msgstr "" + +#: ../Doc/library/optparse.rst:1498 +msgid "OptionParser supports several other public methods:" +msgstr "" + +#: ../Doc/library/optparse.rst:1502 +msgid "" +"Set the usage string according to the rules described above for the " +"``usage`` constructor keyword argument. Passing ``None`` sets the default " +"usage string; use :data:`optparse.SUPPRESS_USAGE` to suppress a usage " +"message." +msgstr "" + +#: ../Doc/library/optparse.rst:1508 +msgid "" +"Print the usage message for the current program (``self.usage``) to *file* " +"(default stdout). Any occurrence of the string ``%prog`` in ``self.usage`` " +"is replaced with the name of the current program. Does nothing if ``self." +"usage`` is empty or not defined." +msgstr "" + +#: ../Doc/library/optparse.rst:1515 +msgid "" +"Same as :meth:`print_usage` but returns the usage string instead of printing " +"it." +msgstr "" + +#: ../Doc/library/optparse.rst:1520 +msgid "" +"Set default values for several option destinations at once. Using :meth:" +"`set_defaults` is the preferred way to set default values for options, since " +"multiple options can share the same destination. For example, if several " +"\"mode\" options all set the same destination, any one of them can set the " +"default, and the last one wins::" +msgstr "" + +#: ../Doc/library/optparse.rst:1533 +msgid "To avoid this confusion, use :meth:`set_defaults`::" +msgstr "" + +#: ../Doc/library/optparse.rst:1545 +msgid "Option Callbacks" +msgstr "" + +#: ../Doc/library/optparse.rst:1547 +msgid "" +"When :mod:`optparse`'s built-in actions and types aren't quite enough for " +"your needs, you have two choices: extend :mod:`optparse` or define a " +"callback option. Extending :mod:`optparse` is more general, but overkill for " +"a lot of simple cases. Quite often a simple callback is all you need." +msgstr "" + +#: ../Doc/library/optparse.rst:1552 +msgid "There are two steps to defining a callback option:" +msgstr "" + +#: ../Doc/library/optparse.rst:1554 +msgid "define the option itself using the ``\"callback\"`` action" +msgstr "" + +#: ../Doc/library/optparse.rst:1556 +msgid "" +"write the callback; this is a function (or method) that takes at least four " +"arguments, as described below" +msgstr "" + +#: ../Doc/library/optparse.rst:1563 +msgid "Defining a callback option" +msgstr "" + +#: ../Doc/library/optparse.rst:1565 +msgid "" +"As always, the easiest way to define a callback option is by using the :meth:" +"`OptionParser.add_option` method. Apart from :attr:`~Option.action`, the " +"only option attribute you must specify is ``callback``, the function to " +"call::" +msgstr "" + +#: ../Doc/library/optparse.rst:1571 +msgid "" +"``callback`` is a function (or other callable object), so you must have " +"already defined ``my_callback()`` when you create this callback option. In " +"this simple case, :mod:`optparse` doesn't even know if ``-c`` takes any " +"arguments, which usually means that the option takes no arguments---the mere " +"presence of ``-c`` on the command-line is all it needs to know. In some " +"circumstances, though, you might want your callback to consume an arbitrary " +"number of command-line arguments. This is where writing callbacks gets " +"tricky; it's covered later in this section." +msgstr "" + +#: ../Doc/library/optparse.rst:1580 +msgid "" +":mod:`optparse` always passes four particular arguments to your callback, " +"and it will only pass additional arguments if you specify them via :attr:" +"`~Option.callback_args` and :attr:`~Option.callback_kwargs`. Thus, the " +"minimal callback function signature is::" +msgstr "" + +#: ../Doc/library/optparse.rst:1587 +msgid "The four arguments to a callback are described below." +msgstr "" + +#: ../Doc/library/optparse.rst:1589 +msgid "" +"There are several other option attributes that you can supply when you " +"define a callback option:" +msgstr "" + +#: ../Doc/library/optparse.rst:1596 +msgid ":attr:`~Option.type`" +msgstr "" + +#: ../Doc/library/optparse.rst:1593 +msgid "" +"has its usual meaning: as with the ``\"store\"`` or ``\"append\"`` actions, " +"it instructs :mod:`optparse` to consume one argument and convert it to :attr:" +"`~Option.type`. Rather than storing the converted value(s) anywhere, " +"though, :mod:`optparse` passes it to your callback function." +msgstr "" + +#: ../Doc/library/optparse.rst:1602 +msgid ":attr:`~Option.nargs`" +msgstr "" + +#: ../Doc/library/optparse.rst:1599 +msgid "" +"also has its usual meaning: if it is supplied and > 1, :mod:`optparse` will " +"consume :attr:`~Option.nargs` arguments, each of which must be convertible " +"to :attr:`~Option.type`. It then passes a tuple of converted values to your " +"callback." +msgstr "" + +#: ../Doc/library/optparse.rst:1605 +msgid ":attr:`~Option.callback_args`" +msgstr "" + +#: ../Doc/library/optparse.rst:1605 +msgid "a tuple of extra positional arguments to pass to the callback" +msgstr "" + +#: ../Doc/library/optparse.rst:1609 +msgid ":attr:`~Option.callback_kwargs`" +msgstr "" + +#: ../Doc/library/optparse.rst:1608 +msgid "a dictionary of extra keyword arguments to pass to the callback" +msgstr "" + +#: ../Doc/library/optparse.rst:1614 +msgid "How callbacks are called" +msgstr "" + +#: ../Doc/library/optparse.rst:1616 +msgid "All callbacks are called as follows::" +msgstr "" + +#: ../Doc/library/optparse.rst:1623 +msgid "``option``" +msgstr "" + +#: ../Doc/library/optparse.rst:1623 +msgid "is the Option instance that's calling the callback" +msgstr "" + +#: ../Doc/library/optparse.rst:1630 +msgid "``opt_str``" +msgstr "" + +#: ../Doc/library/optparse.rst:1626 +msgid "" +"is the option string seen on the command-line that's triggering the " +"callback. (If an abbreviated long option was used, ``opt_str`` will be the " +"full, canonical option string---e.g. if the user puts ``--foo`` on the " +"command-line as an abbreviation for ``--foobar``, then ``opt_str`` will be ``" +"\"--foobar\"``.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1637 +msgid "``value``" +msgstr "" + +#: ../Doc/library/optparse.rst:1633 +msgid "" +"is the argument to this option seen on the command-line. :mod:`optparse` " +"will only expect an argument if :attr:`~Option.type` is set; the type of " +"``value`` will be the type implied by the option's type. If :attr:`~Option." +"type` for this option is ``None`` (no argument expected), then ``value`` " +"will be ``None``. If :attr:`~Option.nargs` > 1, ``value`` will be a tuple " +"of values of the appropriate type." +msgstr "" + +#: ../Doc/library/optparse.rst:1660 +msgid "``parser``" +msgstr "" + +#: ../Doc/library/optparse.rst:1640 +msgid "" +"is the OptionParser instance driving the whole thing, mainly useful because " +"you can access some other interesting data through its instance attributes:" +msgstr "" + +#: ../Doc/library/optparse.rst:1647 +msgid "``parser.largs``" +msgstr "" + +#: ../Doc/library/optparse.rst:1644 +msgid "" +"the current list of leftover arguments, ie. arguments that have been " +"consumed but are neither options nor option arguments. Feel free to modify " +"``parser.largs``, e.g. by adding more arguments to it. (This list will " +"become ``args``, the second return value of :meth:`parse_args`.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1653 +msgid "``parser.rargs``" +msgstr "" + +#: ../Doc/library/optparse.rst:1650 +msgid "" +"the current list of remaining arguments, ie. with ``opt_str`` and ``value`` " +"(if applicable) removed, and only the arguments following them still there. " +"Feel free to modify ``parser.rargs``, e.g. by consuming more arguments." +msgstr "" + +#: ../Doc/library/optparse.rst:1660 +msgid "``parser.values``" +msgstr "" + +#: ../Doc/library/optparse.rst:1656 +msgid "" +"the object where option values are by default stored (an instance of " +"optparse.OptionValues). This lets callbacks use the same mechanism as the " +"rest of :mod:`optparse` for storing option values; you don't need to mess " +"around with globals or closures. You can also access or modify the value(s) " +"of any options already encountered on the command-line." +msgstr "" + +#: ../Doc/library/optparse.rst:1663 +msgid "" +"is a tuple of arbitrary positional arguments supplied via the :attr:`~Option." +"callback_args` option attribute." +msgstr "" + +#: ../Doc/library/optparse.rst:1669 +msgid "``kwargs``" +msgstr "" + +#: ../Doc/library/optparse.rst:1667 +msgid "" +"is a dictionary of arbitrary keyword arguments supplied via :attr:`~Option." +"callback_kwargs`." +msgstr "" + +#: ../Doc/library/optparse.rst:1674 +msgid "Raising errors in a callback" +msgstr "" + +#: ../Doc/library/optparse.rst:1676 +msgid "" +"The callback function should raise :exc:`OptionValueError` if there are any " +"problems with the option or its argument(s). :mod:`optparse` catches this " +"and terminates the program, printing the error message you supply to " +"stderr. Your message should be clear, concise, accurate, and mention the " +"option at fault. Otherwise, the user will have a hard time figuring out what " +"he did wrong." +msgstr "" + +#: ../Doc/library/optparse.rst:1686 +msgid "Callback example 1: trivial callback" +msgstr "" + +#: ../Doc/library/optparse.rst:1688 +msgid "" +"Here's an example of a callback option that takes no arguments, and simply " +"records that the option was seen::" +msgstr "" + +#: ../Doc/library/optparse.rst:1696 +msgid "Of course, you could do that with the ``\"store_true\"`` action." +msgstr "" + +#: ../Doc/library/optparse.rst:1702 +msgid "Callback example 2: check option order" +msgstr "" + +#: ../Doc/library/optparse.rst:1704 +msgid "" +"Here's a slightly more interesting example: record the fact that ``-a`` is " +"seen, but blow up if it comes after ``-b`` in the command-line. ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1719 +msgid "Callback example 3: check option order (generalized)" +msgstr "" + +#: ../Doc/library/optparse.rst:1721 +msgid "" +"If you want to re-use this callback for several similar options (set a flag, " +"but blow up if ``-b`` has already been seen), it needs a bit of work: the " +"error message and the flag that it sets must be generalized. ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1738 +msgid "Callback example 4: check arbitrary condition" +msgstr "" + +#: ../Doc/library/optparse.rst:1740 +msgid "" +"Of course, you could put any condition in there---you're not limited to " +"checking the values of already-defined options. For example, if you have " +"options that should not be called when the moon is full, all you have to do " +"is this::" +msgstr "" + +#: ../Doc/library/optparse.rst:1753 +msgid "" +"(The definition of ``is_moon_full()`` is left as an exercise for the reader.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1759 +msgid "Callback example 5: fixed arguments" +msgstr "" + +#: ../Doc/library/optparse.rst:1761 +msgid "" +"Things get slightly more interesting when you define callback options that " +"take a fixed number of arguments. Specifying that a callback option takes " +"arguments is similar to defining a ``\"store\"`` or ``\"append\"`` option: " +"if you define :attr:`~Option.type`, then the option takes one argument that " +"must be convertible to that type; if you further define :attr:`~Option." +"nargs`, then the option takes :attr:`~Option.nargs` arguments." +msgstr "" + +#: ../Doc/library/optparse.rst:1768 +msgid "" +"Here's an example that just emulates the standard ``\"store\"`` action::" +msgstr "" + +#: ../Doc/library/optparse.rst:1777 +msgid "" +"Note that :mod:`optparse` takes care of consuming 3 arguments and converting " +"them to integers for you; all you have to do is store them. (Or whatever; " +"obviously you don't need a callback for this example.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1785 +msgid "Callback example 6: variable arguments" +msgstr "" + +#: ../Doc/library/optparse.rst:1787 +msgid "" +"Things get hairy when you want an option to take a variable number of " +"arguments. For this case, you must write a callback, as :mod:`optparse` " +"doesn't provide any built-in capabilities for it. And you have to deal with " +"certain intricacies of conventional Unix command-line parsing that :mod:" +"`optparse` normally handles for you. In particular, callbacks should " +"implement the conventional rules for bare ``--`` and ``-`` arguments:" +msgstr "" + +#: ../Doc/library/optparse.rst:1794 +msgid "either ``--`` or ``-`` can be option arguments" +msgstr "" + +#: ../Doc/library/optparse.rst:1796 +msgid "" +"bare ``--`` (if not the argument to some option): halt command-line " +"processing and discard the ``--``" +msgstr "" + +#: ../Doc/library/optparse.rst:1799 +msgid "" +"bare ``-`` (if not the argument to some option): halt command-line " +"processing but keep the ``-`` (append it to ``parser.largs``)" +msgstr "" + +#: ../Doc/library/optparse.rst:1802 +msgid "" +"If you want an option that takes a variable number of arguments, there are " +"several subtle, tricky issues to worry about. The exact implementation you " +"choose will be based on which trade-offs you're willing to make for your " +"application (which is why :mod:`optparse` doesn't support this sort of thing " +"directly)." +msgstr "" + +#: ../Doc/library/optparse.rst:1808 +msgid "" +"Nevertheless, here's a stab at a callback for an option with variable " +"arguments::" +msgstr "" + +#: ../Doc/library/optparse.rst:1842 +msgid "Extending :mod:`optparse`" +msgstr "" + +#: ../Doc/library/optparse.rst:1844 +msgid "" +"Since the two major controlling factors in how :mod:`optparse` interprets " +"command-line options are the action and type of each option, the most likely " +"direction of extension is to add new actions and new types." +msgstr "" + +#: ../Doc/library/optparse.rst:1852 +msgid "Adding new types" +msgstr "" + +#: ../Doc/library/optparse.rst:1854 +msgid "" +"To add new types, you need to define your own subclass of :mod:`optparse`'s :" +"class:`Option` class. This class has a couple of attributes that define :" +"mod:`optparse`'s types: :attr:`~Option.TYPES` and :attr:`~Option." +"TYPE_CHECKER`." +msgstr "" + +#: ../Doc/library/optparse.rst:1860 +msgid "" +"A tuple of type names; in your subclass, simply define a new tuple :attr:" +"`TYPES` that builds on the standard one." +msgstr "" + +#: ../Doc/library/optparse.rst:1865 +msgid "" +"A dictionary mapping type names to type-checking functions. A type-checking " +"function has the following signature::" +msgstr "" + +#: ../Doc/library/optparse.rst:1870 +msgid "" +"where ``option`` is an :class:`Option` instance, ``opt`` is an option string " +"(e.g., ``-f``), and ``value`` is the string from the command line that must " +"be checked and converted to your desired type. ``check_mytype()`` should " +"return an object of the hypothetical type ``mytype``. The value returned by " +"a type-checking function will wind up in the OptionValues instance returned " +"by :meth:`OptionParser.parse_args`, or be passed to a callback as the " +"``value`` parameter." +msgstr "" + +#: ../Doc/library/optparse.rst:1878 +msgid "" +"Your type-checking function should raise :exc:`OptionValueError` if it " +"encounters any problems. :exc:`OptionValueError` takes a single string " +"argument, which is passed as-is to :class:`OptionParser`'s :meth:`error` " +"method, which in turn prepends the program name and the string ``\"error:" +"\"`` and prints everything to stderr before terminating the process." +msgstr "" + +#: ../Doc/library/optparse.rst:1884 +msgid "" +"Here's a silly example that demonstrates adding a ``\"complex\"`` option " +"type to parse Python-style complex numbers on the command line. (This is " +"even sillier than it used to be, because :mod:`optparse` 1.3 added built-in " +"support for complex numbers, but never mind.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1889 +msgid "First, the necessary imports::" +msgstr "" + +#: ../Doc/library/optparse.rst:1894 +msgid "" +"You need to define your type-checker first, since it's referred to later (in " +"the :attr:`~Option.TYPE_CHECKER` class attribute of your Option subclass)::" +msgstr "" + +#: ../Doc/library/optparse.rst:1904 +msgid "Finally, the Option subclass::" +msgstr "" + +#: ../Doc/library/optparse.rst:1911 +msgid "" +"(If we didn't make a :func:`copy` of :attr:`Option.TYPE_CHECKER`, we would " +"end up modifying the :attr:`~Option.TYPE_CHECKER` attribute of :mod:" +"`optparse`'s Option class. This being Python, nothing stops you from doing " +"that except good manners and common sense.)" +msgstr "" + +#: ../Doc/library/optparse.rst:1916 +msgid "" +"That's it! Now you can write a script that uses the new option type just " +"like any other :mod:`optparse`\\ -based script, except you have to instruct " +"your OptionParser to use MyOption instead of Option::" +msgstr "" + +#: ../Doc/library/optparse.rst:1923 +msgid "" +"Alternately, you can build your own option list and pass it to OptionParser; " +"if you don't use :meth:`add_option` in the above way, you don't need to tell " +"OptionParser which option class to use::" +msgstr "" + +#: ../Doc/library/optparse.rst:1934 +msgid "Adding new actions" +msgstr "" + +#: ../Doc/library/optparse.rst:1936 +msgid "" +"Adding new actions is a bit trickier, because you have to understand that :" +"mod:`optparse` has a couple of classifications for actions:" +msgstr "" + +#: ../Doc/library/optparse.rst:1942 +msgid "\"store\" actions" +msgstr "" + +#: ../Doc/library/optparse.rst:1940 +msgid "" +"actions that result in :mod:`optparse` storing a value to an attribute of " +"the current OptionValues instance; these options require a :attr:`~Option." +"dest` attribute to be supplied to the Option constructor." +msgstr "" + +#: ../Doc/library/optparse.rst:1948 +msgid "\"typed\" actions" +msgstr "" + +#: ../Doc/library/optparse.rst:1945 +msgid "" +"actions that take a value from the command line and expect it to be of a " +"certain type; or rather, a string that can be converted to a certain type. " +"These options require a :attr:`~Option.type` attribute to the Option " +"constructor." +msgstr "" + +#: ../Doc/library/optparse.rst:1950 +msgid "" +"These are overlapping sets: some default \"store\" actions are ``\"store" +"\"``, ``\"store_const\"``, ``\"append\"``, and ``\"count\"``, while the " +"default \"typed\" actions are ``\"store\"``, ``\"append\"``, and ``\"callback" +"\"``." +msgstr "" + +#: ../Doc/library/optparse.rst:1954 +msgid "" +"When you add an action, you need to categorize it by listing it in at least " +"one of the following class attributes of Option (all are lists of strings):" +msgstr "" + +#: ../Doc/library/optparse.rst:1959 +msgid "All actions must be listed in ACTIONS." +msgstr "" + +#: ../Doc/library/optparse.rst:1963 +msgid "\"store\" actions are additionally listed here." +msgstr "" + +#: ../Doc/library/optparse.rst:1967 +msgid "\"typed\" actions are additionally listed here." +msgstr "" + +#: ../Doc/library/optparse.rst:1971 +msgid "" +"Actions that always take a type (i.e. whose options always take a value) are " +"additionally listed here. The only effect of this is that :mod:`optparse` " +"assigns the default type, ``\"string\"``, to options with no explicit type " +"whose action is listed in :attr:`ALWAYS_TYPED_ACTIONS`." +msgstr "" + +#: ../Doc/library/optparse.rst:1976 +msgid "" +"In order to actually implement your new action, you must override Option's :" +"meth:`take_action` method and add a case that recognizes your action." +msgstr "" + +#: ../Doc/library/optparse.rst:1979 +msgid "" +"For example, let's add an ``\"extend\"`` action. This is similar to the " +"standard ``\"append\"`` action, but instead of taking a single value from " +"the command-line and appending it to an existing list, ``\"extend\"`` will " +"take multiple values in a single comma-delimited string, and extend an " +"existing list with them. That is, if ``--names`` is an ``\"extend\"`` " +"option of type ``\"string\"``, the command line ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1988 +msgid "would result in a list ::" +msgstr "" + +#: ../Doc/library/optparse.rst:1992 +msgid "Again we define a subclass of Option::" +msgstr "" + +#: ../Doc/library/optparse.rst:2009 +msgid "Features of note:" +msgstr "" + +#: ../Doc/library/optparse.rst:2011 +msgid "" +"``\"extend\"`` both expects a value on the command-line and stores that " +"value somewhere, so it goes in both :attr:`~Option.STORE_ACTIONS` and :attr:" +"`~Option.TYPED_ACTIONS`." +msgstr "" + +#: ../Doc/library/optparse.rst:2015 +msgid "" +"to ensure that :mod:`optparse` assigns the default type of ``\"string\"`` to " +"``\"extend\"`` actions, we put the ``\"extend\"`` action in :attr:`~Option." +"ALWAYS_TYPED_ACTIONS` as well." +msgstr "" + +#: ../Doc/library/optparse.rst:2019 +msgid "" +":meth:`MyOption.take_action` implements just this one new action, and passes " +"control back to :meth:`Option.take_action` for the standard :mod:`optparse` " +"actions." +msgstr "" + +#: ../Doc/library/optparse.rst:2023 +msgid "" +"``values`` is an instance of the optparse_parser.Values class, which " +"provides the very useful :meth:`ensure_value` method. :meth:`ensure_value` " +"is essentially :func:`getattr` with a safety valve; it is called as ::" +msgstr "" + +#: ../Doc/library/optparse.rst:2029 +msgid "" +"If the ``attr`` attribute of ``values`` doesn't exist or is None, then " +"ensure_value() first sets it to ``value``, and then returns 'value. This is " +"very handy for actions like ``\"extend\"``, ``\"append\"``, and ``\"count" +"\"``, all of which accumulate data in a variable and expect that variable to " +"be of a certain type (a list for the first two, an integer for the latter). " +"Using :meth:`ensure_value` means that scripts using your action don't have " +"to worry about setting a default value for the option destinations in " +"question; they can just leave the default as None and :meth:`ensure_value` " +"will take care of getting it right when it's needed." +msgstr "" + +#: ../Doc/library/os.rst:2 +msgid ":mod:`os` --- Miscellaneous operating system interfaces" +msgstr "" + +#: ../Doc/library/os.rst:7 +msgid "**Source code:** :source:`Lib/os.py`" +msgstr "" + +#: ../Doc/library/os.rst:11 +msgid "" +"This module provides a portable way of using operating system dependent " +"functionality. If you just want to read or write a file see :func:`open`, " +"if you want to manipulate paths, see the :mod:`os.path` module, and if you " +"want to read all the lines in all the files on the command line see the :mod:" +"`fileinput` module. For creating temporary files and directories see the :" +"mod:`tempfile` module, and for high-level file and directory handling see " +"the :mod:`shutil` module." +msgstr "" + +#: ../Doc/library/os.rst:19 +msgid "Notes on the availability of these functions:" +msgstr "" + +#: ../Doc/library/os.rst:21 +msgid "" +"The design of all built-in operating system dependent modules of Python is " +"such that as long as the same functionality is available, it uses the same " +"interface; for example, the function ``os.stat(path)`` returns stat " +"information about *path* in the same format (which happens to have " +"originated with the POSIX interface)." +msgstr "" + +#: ../Doc/library/os.rst:27 +msgid "" +"Extensions peculiar to a particular operating system are also available " +"through the :mod:`os` module, but using them is of course a threat to " +"portability." +msgstr "" + +#: ../Doc/library/os.rst:31 +msgid "" +"All functions accepting path or file names accept both bytes and string " +"objects, and result in an object of the same type, if a path or file name is " +"returned." +msgstr "" + +#: ../Doc/library/os.rst:35 +msgid "" +"An \"Availability: Unix\" note means that this function is commonly found on " +"Unix systems. It does not make any claims about its existence on a specific " +"operating system." +msgstr "" + +#: ../Doc/library/os.rst:39 +msgid "" +"If not separately noted, all functions that claim \"Availability: Unix\" are " +"supported on Mac OS X, which builds on a Unix core." +msgstr "" + +#: ../Doc/library/os.rst:47 +msgid "" +"All functions in this module raise :exc:`OSError` in the case of invalid or " +"inaccessible file names and paths, or other arguments that have the correct " +"type, but are not accepted by the operating system." +msgstr "" + +#: ../Doc/library/os.rst:53 +msgid "An alias for the built-in :exc:`OSError` exception." +msgstr "" + +#: ../Doc/library/os.rst:58 +msgid "" +"The name of the operating system dependent module imported. The following " +"names have currently been registered: ``'posix'``, ``'nt'``, ``'java'``." +msgstr "" + +#: ../Doc/library/os.rst:63 +msgid "" +":attr:`sys.platform` has a finer granularity. :func:`os.uname` gives system-" +"dependent version information." +msgstr "" + +#: ../Doc/library/os.rst:66 ../Doc/library/sys.rst:918 +msgid "" +"The :mod:`platform` module provides detailed checks for the system's " +"identity." +msgstr "" + +#: ../Doc/library/os.rst:74 +msgid "File Names, Command Line Arguments, and Environment Variables" +msgstr "" + +#: ../Doc/library/os.rst:76 +msgid "" +"In Python, file names, command line arguments, and environment variables are " +"represented using the string type. On some systems, decoding these strings " +"to and from bytes is necessary before passing them to the operating system. " +"Python uses the file system encoding to perform this conversion (see :func:" +"`sys.getfilesystemencoding`)." +msgstr "" + +#: ../Doc/library/os.rst:82 +msgid "" +"On some systems, conversion using the file system encoding may fail. In this " +"case, Python uses the :ref:`surrogateescape encoding error handler " +"`, which means that undecodable bytes are replaced by a " +"Unicode character U+DCxx on decoding, and these are again translated to the " +"original byte on encoding." +msgstr "" + +#: ../Doc/library/os.rst:90 +msgid "" +"The file system encoding must guarantee to successfully decode all bytes " +"below 128. If the file system encoding fails to provide this guarantee, API " +"functions may raise UnicodeErrors." +msgstr "" + +#: ../Doc/library/os.rst:98 +msgid "Process Parameters" +msgstr "" + +#: ../Doc/library/os.rst:100 +msgid "" +"These functions and data items provide information and operate on the " +"current process and user." +msgstr "" + +#: ../Doc/library/os.rst:106 +msgid "" +"Return the filename corresponding to the controlling terminal of the process." +msgstr "" + +#: ../Doc/library/os.rst:108 ../Doc/library/os.rst:270 +#: ../Doc/library/os.rst:279 ../Doc/library/os.rst:288 +#: ../Doc/library/os.rst:297 ../Doc/library/os.rst:306 +#: ../Doc/library/os.rst:341 ../Doc/library/os.rst:349 +#: ../Doc/library/os.rst:385 ../Doc/library/os.rst:396 +#: ../Doc/library/os.rst:406 ../Doc/library/os.rst:416 +#: ../Doc/library/os.rst:427 ../Doc/library/os.rst:436 +#: ../Doc/library/os.rst:466 ../Doc/library/os.rst:473 +#: ../Doc/library/os.rst:480 ../Doc/library/os.rst:489 +#: ../Doc/library/os.rst:501 ../Doc/library/os.rst:510 +#: ../Doc/library/os.rst:536 ../Doc/library/os.rst:543 +#: ../Doc/library/os.rst:552 ../Doc/library/os.rst:561 +#: ../Doc/library/os.rst:568 ../Doc/library/os.rst:575 +#: ../Doc/library/os.rst:584 ../Doc/library/os.rst:752 +#: ../Doc/library/os.rst:762 ../Doc/library/os.rst:770 +#: ../Doc/library/os.rst:793 ../Doc/library/os.rst:814 +#: ../Doc/library/os.rst:847 ../Doc/library/os.rst:865 +#: ../Doc/library/os.rst:877 ../Doc/library/os.rst:1045 +#: ../Doc/library/os.rst:1060 ../Doc/library/os.rst:1075 +#: ../Doc/library/os.rst:1085 ../Doc/library/os.rst:1095 +#: ../Doc/library/os.rst:1146 ../Doc/library/os.rst:1163 +#: ../Doc/library/os.rst:1175 ../Doc/library/os.rst:1189 +#: ../Doc/library/os.rst:1199 ../Doc/library/os.rst:1207 +#: ../Doc/library/os.rst:1216 ../Doc/library/os.rst:1249 +#: ../Doc/library/os.rst:1486 ../Doc/library/os.rst:1551 +#: ../Doc/library/os.rst:1565 ../Doc/library/os.rst:1577 +#: ../Doc/library/os.rst:1596 ../Doc/library/os.rst:1609 +#: ../Doc/library/os.rst:1620 ../Doc/library/os.rst:1785 +#: ../Doc/library/os.rst:1807 ../Doc/library/os.rst:1851 +#: ../Doc/library/os.rst:1863 ../Doc/library/os.rst:2472 +#: ../Doc/library/os.rst:2616 ../Doc/library/os.rst:2837 +#: ../Doc/library/os.rst:3045 ../Doc/library/os.rst:3053 +#: ../Doc/library/os.rst:3060 ../Doc/library/os.rst:3067 +#: ../Doc/library/os.rst:3074 ../Doc/library/os.rst:3081 +#: ../Doc/library/os.rst:3088 ../Doc/library/os.rst:3095 +#: ../Doc/library/os.rst:3103 ../Doc/library/os.rst:3111 +#: ../Doc/library/os.rst:3118 ../Doc/library/os.rst:3125 +#: ../Doc/library/os.rst:3134 ../Doc/library/os.rst:3142 +#: ../Doc/library/os.rst:3150 ../Doc/library/os.rst:3157 +#: ../Doc/library/os.rst:3164 ../Doc/library/os.rst:3179 +#: ../Doc/library/os.rst:3224 ../Doc/library/os.rst:3231 +#: ../Doc/library/os.rst:3239 ../Doc/library/os.rst:3459 +#: ../Doc/library/os.rst:3474 ../Doc/library/os.rst:3485 +#: ../Doc/library/os.rst:3496 ../Doc/library/os.rst:3509 +#: ../Doc/library/os.rst:3556 ../Doc/library/os.rst:3567 +#: ../Doc/library/os.rst:3575 ../Doc/library/os.rst:3591 +#: ../Doc/library/os.rst:3603 ../Doc/library/os.rst:3611 +#: ../Doc/library/os.rst:3619 ../Doc/library/os.rst:3627 +#: ../Doc/library/os.rst:3635 ../Doc/library/os.rst:3643 +#: ../Doc/library/os.rst:3650 ../Doc/library/os.rst:3657 +#: ../Doc/library/os.rst:3803 ../Doc/library/os.rst:3812 +#: ../Doc/library/os.rst:3833 ../Doc/library/os.rst:3843 +#: ../Doc/library/os.rst:3852 ../Doc/library/shutil.rst:336 +#: ../Doc/library/socket.rst:824 ../Doc/library/socket.rst:835 +#: ../Doc/library/socket.rst:846 ../Doc/library/socket.rst:857 +#: ../Doc/library/sys.rst:979 ../Doc/library/time.rst:158 +#: ../Doc/library/time.rst:167 ../Doc/library/time.rst:176 +#: ../Doc/library/time.rst:197 ../Doc/library/time.rst:216 +#: ../Doc/library/time.rst:226 ../Doc/library/time.rst:235 +#: ../Doc/library/time.rst:600 +msgid "Availability: Unix." +msgstr "" + +#: ../Doc/library/os.rst:113 +msgid "" +"A :term:`mapping` object representing the string environment. For example, " +"``environ['HOME']`` is the pathname of your home directory (on some " +"platforms), and is equivalent to ``getenv(\"HOME\")`` in C." +msgstr "" + +#: ../Doc/library/os.rst:117 +msgid "" +"This mapping is captured the first time the :mod:`os` module is imported, " +"typically during Python startup as part of processing :file:`site.py`. " +"Changes to the environment made after this time are not reflected in ``os." +"environ``, except for changes made by modifying ``os.environ`` directly." +msgstr "" + +#: ../Doc/library/os.rst:122 +msgid "" +"If the platform supports the :func:`putenv` function, this mapping may be " +"used to modify the environment as well as query the environment. :func:" +"`putenv` will be called automatically when the mapping is modified." +msgstr "" + +#: ../Doc/library/os.rst:126 +msgid "" +"On Unix, keys and values use :func:`sys.getfilesystemencoding` and " +"``'surrogateescape'`` error handler. Use :data:`environb` if you would like " +"to use a different encoding." +msgstr "" + +#: ../Doc/library/os.rst:132 +msgid "" +"Calling :func:`putenv` directly does not change ``os.environ``, so it's " +"better to modify ``os.environ``." +msgstr "" + +#: ../Doc/library/os.rst:137 +msgid "" +"On some platforms, including FreeBSD and Mac OS X, setting ``environ`` may " +"cause memory leaks. Refer to the system documentation for :c:func:`putenv`." +msgstr "" + +#: ../Doc/library/os.rst:141 +msgid "" +"If :func:`putenv` is not provided, a modified copy of this mapping may be " +"passed to the appropriate process-creation functions to cause child " +"processes to use a modified environment." +msgstr "" + +#: ../Doc/library/os.rst:145 +msgid "" +"If the platform supports the :func:`unsetenv` function, you can delete items " +"in this mapping to unset environment variables. :func:`unsetenv` will be " +"called automatically when an item is deleted from ``os.environ``, and when " +"one of the :meth:`pop` or :meth:`clear` methods is called." +msgstr "" + +#: ../Doc/library/os.rst:153 +msgid "" +"Bytes version of :data:`environ`: a :term:`mapping` object representing the " +"environment as byte strings. :data:`environ` and :data:`environb` are " +"synchronized (modify :data:`environb` updates :data:`environ`, and vice " +"versa)." +msgstr "" + +#: ../Doc/library/os.rst:158 +msgid "" +":data:`environb` is only available if :data:`supports_bytes_environ` is True." +msgstr "" + +#: ../Doc/library/os.rst:169 +msgid "These functions are described in :ref:`os-file-dir`." +msgstr "" + +#: ../Doc/library/os.rst:174 +msgid "" +"Encode :term:`path-like ` *filename* to the filesystem " +"encoding with ``'surrogateescape'`` error handler, or ``'strict'`` on " +"Windows; return :class:`bytes` unchanged." +msgstr "" + +#: ../Doc/library/os.rst:178 +msgid ":func:`fsdecode` is the reverse function." +msgstr "" + +#: ../Doc/library/os.rst:182 ../Doc/library/os.rst:197 +msgid "" +"Support added to accept objects implementing the :class:`os.PathLike` " +"interface." +msgstr "" + +#: ../Doc/library/os.rst:189 +msgid "" +"Decode the :term:`path-like ` *filename* from the " +"filesystem encoding with ``'surrogateescape'`` error handler, or " +"``'strict'`` on Windows; return :class:`str` unchanged." +msgstr "" + +#: ../Doc/library/os.rst:193 +msgid ":func:`fsencode` is the reverse function." +msgstr "" + +#: ../Doc/library/os.rst:204 +msgid "Return the file system representation of the path." +msgstr "" + +#: ../Doc/library/os.rst:206 +msgid "" +"If :class:`str` or :class:`bytes` is passed in, it is returned unchanged. " +"Otherwise :meth:`~os.PathLike.__fspath__` is called and its value is " +"returned as long as it is a :class:`str` or :class:`bytes` object. In all " +"other cases, :exc:`TypeError` is raised." +msgstr "" + +#: ../Doc/library/os.rst:216 +msgid "" +"An :term:`abstract base class` for objects representing a file system path, " +"e.g. :class:`pathlib.PurePath`." +msgstr "" + +#: ../Doc/library/os.rst:223 +msgid "Return the file system path representation of the object." +msgstr "" + +#: ../Doc/library/os.rst:225 +msgid "" +"The method should only return a :class:`str` or :class:`bytes` object, with " +"the preference being for :class:`str`." +msgstr "" + +#: ../Doc/library/os.rst:231 +msgid "" +"Return the value of the environment variable *key* if it exists, or " +"*default* if it doesn't. *key*, *default* and the result are str." +msgstr "" + +#: ../Doc/library/os.rst:234 +msgid "" +"On Unix, keys and values are decoded with :func:`sys.getfilesystemencoding` " +"and ``'surrogateescape'`` error handler. Use :func:`os.getenvb` if you would " +"like to use a different encoding." +msgstr "" + +#: ../Doc/library/os.rst:238 ../Doc/library/os.rst:449 +#: ../Doc/library/os.rst:653 +msgid "Availability: most flavors of Unix, Windows." +msgstr "" + +#: ../Doc/library/os.rst:243 +msgid "" +"Return the value of the environment variable *key* if it exists, or " +"*default* if it doesn't. *key*, *default* and the result are bytes." +msgstr "" + +#: ../Doc/library/os.rst:246 +msgid "" +":func:`getenvb` is only available if :data:`supports_bytes_environ` is True." +msgstr "" + +#: ../Doc/library/os.rst:249 +msgid "Availability: most flavors of Unix." +msgstr "" + +#: ../Doc/library/os.rst:256 +msgid "" +"Returns the list of directories that will be searched for a named " +"executable, similar to a shell, when launching a process. *env*, when " +"specified, should be an environment variable dictionary to lookup the PATH " +"in. By default, when *env* is None, :data:`environ` is used." +msgstr "" + +#: ../Doc/library/os.rst:267 +msgid "" +"Return the effective group id of the current process. This corresponds to " +"the \"set id\" bit on the file being executed in the current process." +msgstr "" + +#: ../Doc/library/os.rst:277 +msgid "Return the current process's effective user id." +msgstr "" + +#: ../Doc/library/os.rst:286 +msgid "Return the real group id of the current process." +msgstr "" + +#: ../Doc/library/os.rst:293 +msgid "" +"Return list of group ids that *user* belongs to. If *group* is not in the " +"list, it is included; typically, *group* is specified as the group ID field " +"from the password record for *user*." +msgstr "" + +#: ../Doc/library/os.rst:304 +msgid "" +"Return list of supplemental group ids associated with the current process." +msgstr "" + +#: ../Doc/library/os.rst:310 +msgid "" +"On Mac OS X, :func:`getgroups` behavior differs somewhat from other Unix " +"platforms. If the Python interpreter was built with a deployment target of :" +"const:`10.5` or earlier, :func:`getgroups` returns the list of effective " +"group ids associated with the current user process; this list is limited to " +"a system-defined number of entries, typically 16, and may be modified by " +"calls to :func:`setgroups` if suitably privileged. If built with a " +"deployment target greater than :const:`10.5`, :func:`getgroups` returns the " +"current group access list for the user associated with the effective user id " +"of the process; the group access list may change over the lifetime of the " +"process, it is not affected by calls to :func:`setgroups`, and its length is " +"not limited to 16. The deployment target value, :const:" +"`MACOSX_DEPLOYMENT_TARGET`, can be obtained with :func:`sysconfig." +"get_config_var`." +msgstr "" + +#: ../Doc/library/os.rst:327 +msgid "" +"Return the name of the user logged in on the controlling terminal of the " +"process. For most purposes, it is more useful to use the environment " +"variables :envvar:`LOGNAME` or :envvar:`USERNAME` to find out who the user " +"is, or ``pwd.getpwuid(os.getuid())[0]`` to get the login name of the current " +"real user id." +msgstr "" + +#: ../Doc/library/os.rst:333 ../Doc/library/os.rst:367 +#: ../Doc/library/os.rst:826 ../Doc/library/os.rst:835 +#: ../Doc/library/os.rst:1021 ../Doc/library/os.rst:1276 +#: ../Doc/library/os.rst:1634 ../Doc/library/os.rst:2599 +#: ../Doc/library/os.rst:2628 ../Doc/library/os.rst:3011 +#: ../Doc/library/os.rst:3342 ../Doc/library/os.rst:3353 +#: ../Doc/library/os.rst:3421 ../Doc/library/os.rst:3444 +#: ../Doc/library/os.path.rst:355 ../Doc/library/os.path.rst:367 +#: ../Doc/library/os.path.rst:383 ../Doc/library/os.path.rst:399 +#: ../Doc/library/shutil.rst:325 +msgid "Availability: Unix, Windows." +msgstr "" + +#: ../Doc/library/os.rst:338 +msgid "" +"Return the process group id of the process with process id *pid*. If *pid* " +"is 0, the process group id of the current process is returned." +msgstr "" + +#: ../Doc/library/os.rst:347 +msgid "Return the id of the current process group." +msgstr "" + +#: ../Doc/library/os.rst:356 +msgid "Return the current process id." +msgstr "" + +#: ../Doc/library/os.rst:363 +msgid "" +"Return the parent's process id. When the parent process has exited, on Unix " +"the id returned is the one of the init process (1), on Windows it is still " +"the same id, which may be already reused by another process." +msgstr "" + +#: ../Doc/library/os.rst:369 +msgid "Added support for Windows." +msgstr "" + +#: ../Doc/library/os.rst:377 +msgid "" +"Get program scheduling priority. The value *which* is one of :const:" +"`PRIO_PROCESS`, :const:`PRIO_PGRP`, or :const:`PRIO_USER`, and *who* is " +"interpreted relative to *which* (a process identifier for :const:" +"`PRIO_PROCESS`, process group identifier for :const:`PRIO_PGRP`, and a user " +"ID for :const:`PRIO_USER`). A zero value for *who* denotes (respectively) " +"the calling process, the process group of the calling process, or the real " +"user ID of the calling process." +msgstr "" + +#: ../Doc/library/os.rst:394 +msgid "" +"Parameters for the :func:`getpriority` and :func:`setpriority` functions." +msgstr "" + +#: ../Doc/library/os.rst:403 +msgid "" +"Return a tuple (ruid, euid, suid) denoting the current process's real, " +"effective, and saved user ids." +msgstr "" + +#: ../Doc/library/os.rst:413 +msgid "" +"Return a tuple (rgid, egid, sgid) denoting the current process's real, " +"effective, and saved group ids." +msgstr "" + +#: ../Doc/library/os.rst:425 +msgid "Return the current process's real user id." +msgstr "" + +#: ../Doc/library/os.rst:432 +msgid "" +"Call the system initgroups() to initialize the group access list with all of " +"the groups of which the specified username is a member, plus the specified " +"group id." +msgstr "" + +#: ../Doc/library/os.rst:445 +msgid "" +"Set the environment variable named *key* to the string *value*. Such " +"changes to the environment affect subprocesses started with :func:`os." +"system`, :func:`popen` or :func:`fork` and :func:`execv`." +msgstr "" + +#: ../Doc/library/os.rst:453 +msgid "" +"On some platforms, including FreeBSD and Mac OS X, setting ``environ`` may " +"cause memory leaks. Refer to the system documentation for putenv." +msgstr "" + +#: ../Doc/library/os.rst:456 +msgid "" +"When :func:`putenv` is supported, assignments to items in ``os.environ`` are " +"automatically translated into corresponding calls to :func:`putenv`; " +"however, calls to :func:`putenv` don't update ``os.environ``, so it is " +"actually preferable to assign to items of ``os.environ``." +msgstr "" + +#: ../Doc/library/os.rst:464 +msgid "Set the current process's effective group id." +msgstr "" + +#: ../Doc/library/os.rst:471 +msgid "Set the current process's effective user id." +msgstr "" + +#: ../Doc/library/os.rst:478 +msgid "Set the current process' group id." +msgstr "" + +#: ../Doc/library/os.rst:485 +msgid "" +"Set the list of supplemental group ids associated with the current process " +"to *groups*. *groups* must be a sequence, and each element must be an " +"integer identifying a group. This operation is typically available only to " +"the superuser." +msgstr "" + +#: ../Doc/library/os.rst:491 +msgid "" +"On Mac OS X, the length of *groups* may not exceed the system-defined " +"maximum number of effective group ids, typically 16. See the documentation " +"for :func:`getgroups` for cases where it may not return the same group list " +"set by calling setgroups()." +msgstr "" + +#: ../Doc/library/os.rst:498 +msgid "" +"Call the system call :c:func:`setpgrp` or ``setpgrp(0, 0)`` depending on " +"which version is implemented (if any). See the Unix manual for the " +"semantics." +msgstr "" + +#: ../Doc/library/os.rst:506 +msgid "" +"Call the system call :c:func:`setpgid` to set the process group id of the " +"process with id *pid* to the process group with id *pgrp*. See the Unix " +"manual for the semantics." +msgstr "" + +#: ../Doc/library/os.rst:517 +msgid "" +"Set program scheduling priority. The value *which* is one of :const:" +"`PRIO_PROCESS`, :const:`PRIO_PGRP`, or :const:`PRIO_USER`, and *who* is " +"interpreted relative to *which* (a process identifier for :const:" +"`PRIO_PROCESS`, process group identifier for :const:`PRIO_PGRP`, and a user " +"ID for :const:`PRIO_USER`). A zero value for *who* denotes (respectively) " +"the calling process, the process group of the calling process, or the real " +"user ID of the calling process. *priority* is a value in the range -20 to " +"19. The default priority is 0; lower priorities cause more favorable " +"scheduling." +msgstr "" + +#: ../Doc/library/os.rst:527 +msgid "Availability: Unix" +msgstr "" + +#: ../Doc/library/os.rst:534 +msgid "Set the current process's real and effective group ids." +msgstr "" + +#: ../Doc/library/os.rst:541 +msgid "Set the current process's real, effective, and saved group ids." +msgstr "" + +#: ../Doc/library/os.rst:550 +msgid "Set the current process's real, effective, and saved user ids." +msgstr "" + +#: ../Doc/library/os.rst:559 +msgid "Set the current process's real and effective user ids." +msgstr "" + +#: ../Doc/library/os.rst:566 +msgid "" +"Call the system call :c:func:`getsid`. See the Unix manual for the " +"semantics." +msgstr "" + +#: ../Doc/library/os.rst:573 +msgid "" +"Call the system call :c:func:`setsid`. See the Unix manual for the " +"semantics." +msgstr "" + +#: ../Doc/library/os.rst:582 +msgid "Set the current process's user id." +msgstr "" + +#: ../Doc/library/os.rst:590 +msgid "" +"Return the error message corresponding to the error code in *code*. On " +"platforms where :c:func:`strerror` returns ``NULL`` when given an unknown " +"error number, :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/os.rst:597 +msgid "" +"``True`` if the native OS type of the environment is bytes (eg. ``False`` on " +"Windows)." +msgstr "" + +#: ../Doc/library/os.rst:605 +msgid "Set the current numeric umask and return the previous umask." +msgstr "" + +#: ../Doc/library/os.rst:614 +msgid "" +"Returns information identifying the current operating system. The return " +"value is an object with five attributes:" +msgstr "" + +#: ../Doc/library/os.rst:617 +msgid ":attr:`sysname` - operating system name" +msgstr "" + +#: ../Doc/library/os.rst:618 +msgid ":attr:`nodename` - name of machine on network (implementation-defined)" +msgstr "" + +#: ../Doc/library/os.rst:619 +msgid ":attr:`release` - operating system release" +msgstr "" + +#: ../Doc/library/os.rst:620 +msgid ":attr:`version` - operating system version" +msgstr "" + +#: ../Doc/library/os.rst:621 +msgid ":attr:`machine` - hardware identifier" +msgstr "" + +#: ../Doc/library/os.rst:623 +msgid "" +"For backwards compatibility, this object is also iterable, behaving like a " +"five-tuple containing :attr:`sysname`, :attr:`nodename`, :attr:`release`, :" +"attr:`version`, and :attr:`machine` in that order." +msgstr "" + +#: ../Doc/library/os.rst:628 +msgid "" +"Some systems truncate :attr:`nodename` to 8 characters or to the leading " +"component; a better way to get the hostname is :func:`socket.gethostname` " +"or even ``socket.gethostbyaddr(socket.gethostname())``." +msgstr "" + +#: ../Doc/library/os.rst:633 +msgid "Availability: recent flavors of Unix." +msgstr "" + +#: ../Doc/library/os.rst:635 ../Doc/library/os.rst:3446 +msgid "" +"Return type changed from a tuple to a tuple-like object with named " +"attributes." +msgstr "" + +#: ../Doc/library/os.rst:644 +msgid "" +"Unset (delete) the environment variable named *key*. Such changes to the " +"environment affect subprocesses started with :func:`os.system`, :func:" +"`popen` or :func:`fork` and :func:`execv`." +msgstr "" + +#: ../Doc/library/os.rst:648 +msgid "" +"When :func:`unsetenv` is supported, deletion of items in ``os.environ`` is " +"automatically translated into a corresponding call to :func:`unsetenv`; " +"however, calls to :func:`unsetenv` don't update ``os.environ``, so it is " +"actually preferable to delete items of ``os.environ``." +msgstr "" + +#: ../Doc/library/os.rst:659 +msgid "File Object Creation" +msgstr "" + +#: ../Doc/library/os.rst:661 +msgid "" +"This function creates new :term:`file objects `. (See also :" +"func:`~os.open` for opening file descriptors.)" +msgstr "" + +#: ../Doc/library/os.rst:667 +msgid "" +"Return an open file object connected to the file descriptor *fd*. This is " +"an alias of the :func:`open` built-in function and accepts the same " +"arguments. The only difference is that the first argument of :func:`fdopen` " +"must always be an integer." +msgstr "" + +#: ../Doc/library/os.rst:676 +msgid "File Descriptor Operations" +msgstr "" + +#: ../Doc/library/os.rst:678 +msgid "" +"These functions operate on I/O streams referenced using file descriptors." +msgstr "" + +#: ../Doc/library/os.rst:680 +msgid "" +"File descriptors are small integers corresponding to a file that has been " +"opened by the current process. For example, standard input is usually file " +"descriptor 0, standard output is 1, and standard error is 2. Further files " +"opened by a process will then be assigned 3, 4, 5, and so forth. The name " +"\"file descriptor\" is slightly deceptive; on Unix platforms, sockets and " +"pipes are also referenced by file descriptors." +msgstr "" + +#: ../Doc/library/os.rst:687 +msgid "" +"The :meth:`~io.IOBase.fileno` method can be used to obtain the file " +"descriptor associated with a :term:`file object` when required. Note that " +"using the file descriptor directly will bypass the file object methods, " +"ignoring aspects such as internal buffering of data." +msgstr "" + +#: ../Doc/library/os.rst:695 +msgid "Close file descriptor *fd*." +msgstr "" + +#: ../Doc/library/os.rst:699 +msgid "" +"This function is intended for low-level I/O and must be applied to a file " +"descriptor as returned by :func:`os.open` or :func:`pipe`. To close a " +"\"file object\" returned by the built-in function :func:`open` or by :func:" +"`popen` or :func:`fdopen`, use its :meth:`~io.IOBase.close` method." +msgstr "" + +#: ../Doc/library/os.rst:707 +msgid "" +"Close all file descriptors from *fd_low* (inclusive) to *fd_high* " +"(exclusive), ignoring errors. Equivalent to (but much faster than)::" +msgstr "" + +#: ../Doc/library/os.rst:719 +msgid "" +"Return a string describing the encoding of the device associated with *fd* " +"if it is connected to a terminal; else return :const:`None`." +msgstr "" + +#: ../Doc/library/os.rst:725 +msgid "" +"Return a duplicate of file descriptor *fd*. The new file descriptor is :ref:" +"`non-inheritable `." +msgstr "" + +#: ../Doc/library/os.rst:728 +msgid "" +"On Windows, when duplicating a standard stream (0: stdin, 1: stdout, 2: " +"stderr), the new file descriptor is :ref:`inheritable `." +msgstr "" + +#: ../Doc/library/os.rst:732 ../Doc/library/os.rst:918 +#: ../Doc/library/select.rst:53 ../Doc/library/select.rst:98 +msgid "The new file descriptor is now non-inheritable." +msgstr "" + +#: ../Doc/library/os.rst:738 +msgid "" +"Duplicate file descriptor *fd* to *fd2*, closing the latter first if " +"necessary. The file descriptor *fd2* is :ref:`inheritable ` " +"by default, or non-inheritable if *inheritable* is ``False``." +msgstr "" + +#: ../Doc/library/os.rst:742 +msgid "Add the optional *inheritable* parameter." +msgstr "" + +#: ../Doc/library/os.rst:748 +msgid "" +"Change the mode of the file given by *fd* to the numeric *mode*. See the " +"docs for :func:`chmod` for possible values of *mode*. As of Python 3.3, " +"this is equivalent to ``os.chmod(fd, mode)``." +msgstr "" + +#: ../Doc/library/os.rst:757 +msgid "" +"Change the owner and group id of the file given by *fd* to the numeric *uid* " +"and *gid*. To leave one of the ids unchanged, set it to -1. See :func:" +"`chown`. As of Python 3.3, this is equivalent to ``os.chown(fd, uid, gid)``." +msgstr "" + +#: ../Doc/library/os.rst:767 +msgid "" +"Force write of file with filedescriptor *fd* to disk. Does not force update " +"of metadata." +msgstr "" + +#: ../Doc/library/os.rst:773 +msgid "This function is not available on MacOS." +msgstr "" + +#: ../Doc/library/os.rst:778 +msgid "" +"Return system configuration information relevant to an open file. *name* " +"specifies the configuration value to retrieve; it may be a string which is " +"the name of a defined system value; these names are specified in a number of " +"standards (POSIX.1, Unix 95, Unix 98, and others). Some platforms define " +"additional names as well. The names known to the host operating system are " +"given in the ``pathconf_names`` dictionary. For configuration variables not " +"included in that mapping, passing an integer for *name* is also accepted." +msgstr "" + +#: ../Doc/library/os.rst:786 ../Doc/library/os.rst:1843 +msgid "" +"If *name* is a string and is not known, :exc:`ValueError` is raised. If a " +"specific value for *name* is not supported by the host system, even if it is " +"included in ``pathconf_names``, an :exc:`OSError` is raised with :const:" +"`errno.EINVAL` for the error number." +msgstr "" + +#: ../Doc/library/os.rst:791 +msgid "As of Python 3.3, this is equivalent to ``os.pathconf(fd, name)``." +msgstr "" + +#: ../Doc/library/os.rst:798 +msgid "" +"Get the status of the file descriptor *fd*. Return a :class:`stat_result` " +"object." +msgstr "" + +#: ../Doc/library/os.rst:801 +msgid "As of Python 3.3, this is equivalent to ``os.stat(fd)``." +msgstr "" + +#: ../Doc/library/os.rst:805 ../Doc/library/os.rst:1696 +msgid "The :func:`.stat` function." +msgstr "" + +#: ../Doc/library/os.rst:810 +msgid "" +"Return information about the filesystem containing the file associated with " +"file descriptor *fd*, like :func:`statvfs`. As of Python 3.3, this is " +"equivalent to ``os.statvfs(fd)``." +msgstr "" + +#: ../Doc/library/os.rst:819 +msgid "" +"Force write of file with filedescriptor *fd* to disk. On Unix, this calls " +"the native :c:func:`fsync` function; on Windows, the MS :c:func:`_commit` " +"function." +msgstr "" + +#: ../Doc/library/os.rst:822 +msgid "" +"If you're starting with a buffered Python :term:`file object` *f*, first do " +"``f.flush()``, and then do ``os.fsync(f.fileno())``, to ensure that all " +"internal buffers associated with *f* are written to disk." +msgstr "" + +#: ../Doc/library/os.rst:831 +msgid "" +"Truncate the file corresponding to file descriptor *fd*, so that it is at " +"most *length* bytes in size. As of Python 3.3, this is equivalent to ``os." +"truncate(fd, length)``." +msgstr "" + +#: ../Doc/library/os.rst:837 ../Doc/library/os.rst:2632 +msgid "Added support for Windows" +msgstr "" + +#: ../Doc/library/os.rst:842 +msgid "" +"Get the blocking mode of the file descriptor: ``False`` if the :data:" +"`O_NONBLOCK` flag is set, ``True`` if the flag is cleared." +msgstr "" + +#: ../Doc/library/os.rst:845 +msgid "See also :func:`set_blocking` and :meth:`socket.socket.setblocking`." +msgstr "" + +#: ../Doc/library/os.rst:853 +msgid "" +"Return ``True`` if the file descriptor *fd* is open and connected to a tty(-" +"like) device, else ``False``." +msgstr "" + +#: ../Doc/library/os.rst:859 +msgid "" +"Apply, test or remove a POSIX lock on an open file descriptor. *fd* is an " +"open file descriptor. *cmd* specifies the command to use - one of :data:" +"`F_LOCK`, :data:`F_TLOCK`, :data:`F_ULOCK` or :data:`F_TEST`. *len* " +"specifies the section of the file to lock." +msgstr "" + +#: ../Doc/library/os.rst:875 +msgid "Flags that specify what action :func:`lockf` will take." +msgstr "" + +#: ../Doc/library/os.rst:884 +msgid "" +"Set the current position of file descriptor *fd* to position *pos*, modified " +"by *how*: :const:`SEEK_SET` or ``0`` to set the position relative to the " +"beginning of the file; :const:`SEEK_CUR` or ``1`` to set it relative to the " +"current position; :const:`SEEK_END` or ``2`` to set it relative to the end " +"of the file. Return the new cursor position in bytes, starting from the " +"beginning." +msgstr "" + +#: ../Doc/library/os.rst:895 +msgid "" +"Parameters to the :func:`lseek` function. Their values are 0, 1, and 2, " +"respectively." +msgstr "" + +#: ../Doc/library/os.rst:898 +msgid "" +"Some operating systems could support additional values, like :data:`os." +"SEEK_HOLE` or :data:`os.SEEK_DATA`." +msgstr "" + +#: ../Doc/library/os.rst:905 +msgid "" +"Open the file *path* and set various flags according to *flags* and possibly " +"its mode according to *mode*. When computing *mode*, the current umask " +"value is first masked out. Return the file descriptor for the newly opened " +"file. The new file descriptor is :ref:`non-inheritable `." +msgstr "" + +#: ../Doc/library/os.rst:910 +msgid "" +"For a description of the flag and mode values, see the C run-time " +"documentation; flag constants (like :const:`O_RDONLY` and :const:`O_WRONLY`) " +"are defined in the :mod:`os` module. In particular, on Windows adding :" +"const:`O_BINARY` is needed to open files in binary mode." +msgstr "" + +#: ../Doc/library/os.rst:915 +msgid "" +"This function can support :ref:`paths relative to directory descriptors " +"` with the *dir_fd* parameter." +msgstr "" + +#: ../Doc/library/os.rst:923 +msgid "" +"This function is intended for low-level I/O. For normal usage, use the " +"built-in function :func:`open`, which returns a :term:`file object` with :" +"meth:`~file.read` and :meth:`~file.write` methods (and many more). To wrap " +"a file descriptor in a file object, use :func:`fdopen`." +msgstr "" + +#: ../Doc/library/os.rst:928 ../Doc/library/os.rst:1728 +#: ../Doc/library/os.rst:1787 ../Doc/library/os.rst:1809 +#: ../Doc/library/os.rst:1886 ../Doc/library/os.rst:1907 +msgid "The *dir_fd* argument." +msgstr "" + +#: ../Doc/library/os.rst:939 +msgid "" +"The following constants are options for the *flags* parameter to the :func:" +"`~os.open` function. They can be combined using the bitwise OR operator ``|" +"``. Some of them are not available on all platforms. For descriptions of " +"their availability and use, consult the :manpage:`open(2)` manual page on " +"Unix or `the MSDN `_ " +"on Windows." +msgstr "" + +#: ../Doc/library/os.rst:954 +msgid "The above constants are available on Unix and Windows." +msgstr "" + +#: ../Doc/library/os.rst:965 +msgid "The above constants are only available on Unix." +msgstr "" + +#: ../Doc/library/os.rst:967 +msgid "Add :data:`O_CLOEXEC` constant." +msgstr "" + +#: ../Doc/library/os.rst:978 +msgid "The above constants are only available on Windows." +msgstr "" + +#: ../Doc/library/os.rst:991 +msgid "" +"The above constants are extensions and not present if they are not defined " +"by the C library." +msgstr "" + +#: ../Doc/library/os.rst:994 +msgid "" +"Add :data:`O_PATH` on systems that support it. Add :data:`O_TMPFILE`, only " +"available on Linux Kernel 3.11 or newer." +msgstr "" + +#: ../Doc/library/os.rst:1004 +msgid "" +"Open a new pseudo-terminal pair. Return a pair of file descriptors " +"``(master, slave)`` for the pty and the tty, respectively. The new file " +"descriptors are :ref:`non-inheritable `. For a (slightly) " +"more portable approach, use the :mod:`pty` module." +msgstr "" + +#: ../Doc/library/os.rst:1009 ../Doc/library/os.rst:1035 +#: ../Doc/library/os.rst:3190 +msgid "Availability: some flavors of Unix." +msgstr "" + +#: ../Doc/library/os.rst:1011 ../Doc/library/os.rst:1023 +msgid "The new file descriptors are now non-inheritable." +msgstr "" + +#: ../Doc/library/os.rst:1017 +msgid "" +"Create a pipe. Return a pair of file descriptors ``(r, w)`` usable for " +"reading and writing, respectively. The new file descriptor is :ref:`non-" +"inheritable `." +msgstr "" + +#: ../Doc/library/os.rst:1029 +msgid "" +"Create a pipe with *flags* set atomically. *flags* can be constructed by " +"ORing together one or more of these values: :data:`O_NONBLOCK`, :data:" +"`O_CLOEXEC`. Return a pair of file descriptors ``(r, w)`` usable for reading " +"and writing, respectively." +msgstr "" + +#: ../Doc/library/os.rst:1042 +msgid "" +"Ensures that enough disk space is allocated for the file specified by *fd* " +"starting from *offset* and continuing for *len* bytes." +msgstr "" + +#: ../Doc/library/os.rst:1052 +msgid "" +"Announces an intention to access data in a specific pattern thus allowing " +"the kernel to make optimizations. The advice applies to the region of the " +"file specified by *fd* starting at *offset* and continuing for *len* bytes. " +"*advice* is one of :data:`POSIX_FADV_NORMAL`, :data:" +"`POSIX_FADV_SEQUENTIAL`, :data:`POSIX_FADV_RANDOM`, :data:" +"`POSIX_FADV_NOREUSE`, :data:`POSIX_FADV_WILLNEED` or :data:" +"`POSIX_FADV_DONTNEED`." +msgstr "" + +#: ../Doc/library/os.rst:1072 +msgid "" +"Flags that can be used in *advice* in :func:`posix_fadvise` that specify the " +"access pattern that is likely to be used." +msgstr "" + +#: ../Doc/library/os.rst:1082 +msgid "" +"Read from a file descriptor, *fd*, at a position of *offset*. It will read " +"up to *buffersize* number of bytes. The file offset remains unchanged." +msgstr "" + +#: ../Doc/library/os.rst:1092 +msgid "" +"Write *bytestring* to a file descriptor, *fd*, from *offset*, leaving the " +"file offset unchanged." +msgstr "" + +#: ../Doc/library/os.rst:1102 +msgid "" +"Read at most *n* bytes from file descriptor *fd*. Return a bytestring " +"containing the bytes read. If the end of the file referred to by *fd* has " +"been reached, an empty bytes object is returned." +msgstr "" + +#: ../Doc/library/os.rst:1108 +msgid "" +"This function is intended for low-level I/O and must be applied to a file " +"descriptor as returned by :func:`os.open` or :func:`pipe`. To read a \"file " +"object\" returned by the built-in function :func:`open` or by :func:`popen` " +"or :func:`fdopen`, or :data:`sys.stdin`, use its :meth:`~file.read` or :meth:" +"`~file.readline` methods." +msgstr "" + +#: ../Doc/library/os.rst:1123 +msgid "" +"Copy *count* bytes from file descriptor *in* to file descriptor *out* " +"starting at *offset*. Return the number of bytes sent. When EOF is reached " +"return 0." +msgstr "" + +#: ../Doc/library/os.rst:1127 +msgid "" +"The first function notation is supported by all platforms that define :func:" +"`sendfile`." +msgstr "" + +#: ../Doc/library/os.rst:1130 +msgid "" +"On Linux, if *offset* is given as ``None``, the bytes are read from the " +"current position of *in* and the position of *in* is updated." +msgstr "" + +#: ../Doc/library/os.rst:1133 +msgid "" +"The second case may be used on Mac OS X and FreeBSD where *headers* and " +"*trailers* are arbitrary sequences of buffers that are written before and " +"after the data from *in* is written. It returns the same as the first case." +msgstr "" + +#: ../Doc/library/os.rst:1137 +msgid "" +"On Mac OS X and FreeBSD, a value of 0 for *count* specifies to send until " +"the end of *in* is reached." +msgstr "" + +#: ../Doc/library/os.rst:1140 +msgid "" +"All platforms support sockets as *out* file descriptor, and some platforms " +"allow other types (e.g. regular file, pipe) as well." +msgstr "" + +#: ../Doc/library/os.rst:1143 +msgid "" +"Cross-platform applications should not use *headers*, *trailers* and *flags* " +"arguments." +msgstr "" + +#: ../Doc/library/os.rst:1150 +msgid "" +"For a higher-level wrapper of :func:`sendfile`, see :meth:`socket.socket." +"sendfile`." +msgstr "" + +#: ../Doc/library/os.rst:1158 +msgid "" +"Set the blocking mode of the specified file descriptor. Set the :data:" +"`O_NONBLOCK` flag if blocking is ``False``, clear the flag otherwise." +msgstr "" + +#: ../Doc/library/os.rst:1161 +msgid "See also :func:`get_blocking` and :meth:`socket.socket.setblocking`." +msgstr "" + +#: ../Doc/library/os.rst:1172 +msgid "" +"Parameters to the :func:`sendfile` function, if the implementation supports " +"them." +msgstr "" + +#: ../Doc/library/os.rst:1182 +msgid "" +"Read from a file descriptor *fd* into a number of mutable :term:`bytes-like " +"objects ` *buffers*. :func:`~os.readv` will transfer data " +"into each buffer until it is full and then move on to the next buffer in the " +"sequence to hold the rest of the data. :func:`~os.readv` returns the total " +"number of bytes read (which may be less than the total capacity of all the " +"objects)." +msgstr "" + +#: ../Doc/library/os.rst:1196 +msgid "" +"Return the process group associated with the terminal given by *fd* (an open " +"file descriptor as returned by :func:`os.open`)." +msgstr "" + +#: ../Doc/library/os.rst:1204 +msgid "" +"Set the process group associated with the terminal given by *fd* (an open " +"file descriptor as returned by :func:`os.open`) to *pg*." +msgstr "" + +#: ../Doc/library/os.rst:1212 +msgid "" +"Return a string which specifies the terminal device associated with file " +"descriptor *fd*. If *fd* is not associated with a terminal device, an " +"exception is raised." +msgstr "" + +#: ../Doc/library/os.rst:1221 +msgid "" +"Write the bytestring in *str* to file descriptor *fd*. Return the number of " +"bytes actually written." +msgstr "" + +#: ../Doc/library/os.rst:1226 +msgid "" +"This function is intended for low-level I/O and must be applied to a file " +"descriptor as returned by :func:`os.open` or :func:`pipe`. To write a " +"\"file object\" returned by the built-in function :func:`open` or by :func:" +"`popen` or :func:`fdopen`, or :data:`sys.stdout` or :data:`sys.stderr`, use " +"its :meth:`~file.write` method." +msgstr "" + +#: ../Doc/library/os.rst:1240 +msgid "" +"Write the contents of *buffers* to file descriptor *fd*. *buffers* must be a " +"sequence of :term:`bytes-like objects `. Buffers are " +"processed in array order. Entire contents of first buffer is written before " +"proceeding to second, and so on. The operating system may set a limit " +"(sysconf() value SC_IOV_MAX) on the number of buffers that can be used." +msgstr "" + +#: ../Doc/library/os.rst:1246 +msgid "" +":func:`~os.writev` writes the contents of each object to the file descriptor " +"and returns the total number of bytes written." +msgstr "" + +#: ../Doc/library/os.rst:1257 +msgid "Querying the size of a terminal" +msgstr "" + +#: ../Doc/library/os.rst:1263 +msgid "" +"Return the size of the terminal window as ``(columns, lines)``, tuple of " +"type :class:`terminal_size`." +msgstr "" + +#: ../Doc/library/os.rst:1266 +msgid "" +"The optional argument ``fd`` (default ``STDOUT_FILENO``, or standard output) " +"specifies which file descriptor should be queried." +msgstr "" + +#: ../Doc/library/os.rst:1269 +msgid "" +"If the file descriptor is not connected to a terminal, an :exc:`OSError` is " +"raised." +msgstr "" + +#: ../Doc/library/os.rst:1272 +msgid "" +":func:`shutil.get_terminal_size` is the high-level function which should " +"normally be used, ``os.get_terminal_size`` is the low-level implementation." +msgstr "" + +#: ../Doc/library/os.rst:1280 +msgid "" +"A subclass of tuple, holding ``(columns, lines)`` of the terminal window " +"size." +msgstr "" + +#: ../Doc/library/os.rst:1284 +msgid "Width of the terminal window in characters." +msgstr "" + +#: ../Doc/library/os.rst:1288 +msgid "Height of the terminal window in characters." +msgstr "" + +#: ../Doc/library/os.rst:1294 +msgid "Inheritance of File Descriptors" +msgstr "" + +#: ../Doc/library/os.rst:1298 +msgid "" +"A file descriptor has an \"inheritable\" flag which indicates if the file " +"descriptor can be inherited by child processes. Since Python 3.4, file " +"descriptors created by Python are non-inheritable by default." +msgstr "" + +#: ../Doc/library/os.rst:1302 +msgid "" +"On UNIX, non-inheritable file descriptors are closed in child processes at " +"the execution of a new program, other file descriptors are inherited." +msgstr "" + +#: ../Doc/library/os.rst:1305 +msgid "" +"On Windows, non-inheritable handles and file descriptors are closed in child " +"processes, except for standard streams (file descriptors 0, 1 and 2: stdin, " +"stdout and stderr), which are always inherited. Using :func:`spawn\\* " +"` functions, all inheritable handles and all inheritable file " +"descriptors are inherited. Using the :mod:`subprocess` module, all file " +"descriptors except standard streams are closed, and inheritable handles are " +"only inherited if the *close_fds* parameter is ``False``." +msgstr "" + +#: ../Doc/library/os.rst:1315 +msgid "" +"Get the \"inheritable\" flag of the specified file descriptor (a boolean)." +msgstr "" + +#: ../Doc/library/os.rst:1319 +msgid "Set the \"inheritable\" flag of the specified file descriptor." +msgstr "" + +#: ../Doc/library/os.rst:1323 +msgid "Get the \"inheritable\" flag of the specified handle (a boolean)." +msgstr "" + +#: ../Doc/library/os.rst:1329 +msgid "Set the \"inheritable\" flag of the specified handle." +msgstr "" + +#: ../Doc/library/os.rst:1337 +msgid "Files and Directories" +msgstr "" + +#: ../Doc/library/os.rst:1339 +msgid "" +"On some Unix platforms, many of these functions support one or more of these " +"features:" +msgstr "" + +#: ../Doc/library/os.rst:1344 +msgid "" +"**specifying a file descriptor:** For some functions, the *path* argument " +"can be not only a string giving a path name, but also a file descriptor. " +"The function will then operate on the file referred to by the descriptor. " +"(For POSIX systems, Python will call the ``f...`` version of the function.)" +msgstr "" + +#: ../Doc/library/os.rst:1350 +msgid "" +"You can check whether or not *path* can be specified as a file descriptor on " +"your platform using :data:`os.supports_fd`. If it is unavailable, using it " +"will raise a :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/os.rst:1354 +msgid "" +"If the function also supports *dir_fd* or *follow_symlinks* arguments, it is " +"an error to specify one of those when supplying *path* as a file descriptor." +msgstr "" + +#: ../Doc/library/os.rst:1359 +msgid "" +"**paths relative to directory descriptors:** If *dir_fd* is not ``None``, it " +"should be a file descriptor referring to a directory, and the path to " +"operate on should be relative; path will then be relative to that " +"directory. If the path is absolute, *dir_fd* is ignored. (For POSIX " +"systems, Python will call the ``...at`` or ``f...at`` version of the " +"function.)" +msgstr "" + +#: ../Doc/library/os.rst:1365 +msgid "" +"You can check whether or not *dir_fd* is supported on your platform using :" +"data:`os.supports_dir_fd`. If it is unavailable, using it will raise a :exc:" +"`NotImplementedError`." +msgstr "" + +#: ../Doc/library/os.rst:1371 +msgid "" +"**not following symlinks:** If *follow_symlinks* is ``False``, and the last " +"element of the path to operate on is a symbolic link, the function will " +"operate on the symbolic link itself instead of the file the link points to. " +"(For POSIX systems, Python will call the ``l...`` version of the function.)" +msgstr "" + +#: ../Doc/library/os.rst:1377 +msgid "" +"You can check whether or not *follow_symlinks* is supported on your platform " +"using :data:`os.supports_follow_symlinks`. If it is unavailable, using it " +"will raise a :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/os.rst:1385 +msgid "" +"Use the real uid/gid to test for access to *path*. Note that most " +"operations will use the effective uid/gid, therefore this routine can be " +"used in a suid/sgid environment to test if the invoking user has the " +"specified access to *path*. *mode* should be :const:`F_OK` to test the " +"existence of *path*, or it can be the inclusive OR of one or more of :const:" +"`R_OK`, :const:`W_OK`, and :const:`X_OK` to test permissions. Return :const:" +"`True` if access is allowed, :const:`False` if not. See the Unix man page :" +"manpage:`access(2)` for more information." +msgstr "" + +#: ../Doc/library/os.rst:1394 +msgid "" +"This function can support specifying :ref:`paths relative to directory " +"descriptors ` and :ref:`not following symlinks `." +msgstr "" + +#: ../Doc/library/os.rst:1397 +msgid "" +"If *effective_ids* is ``True``, :func:`access` will perform its access " +"checks using the effective uid/gid instead of the real uid/gid. " +"*effective_ids* may not be supported on your platform; you can check whether " +"or not it is available using :data:`os.supports_effective_ids`. If it is " +"unavailable, using it will raise a :exc:`NotImplementedError`." +msgstr "" + +#: ../Doc/library/os.rst:1405 +msgid "" +"Using :func:`access` to check if a user is authorized to e.g. open a file " +"before actually doing so using :func:`open` creates a security hole, because " +"the user might exploit the short time interval between checking and opening " +"the file to manipulate it. It's preferable to use :term:`EAFP` techniques. " +"For example::" +msgstr "" + +#: ../Doc/library/os.rst:1416 +msgid "is better written as::" +msgstr "" + +#: ../Doc/library/os.rst:1428 +msgid "" +"I/O operations may fail even when :func:`access` indicates that they would " +"succeed, particularly for operations on network filesystems which may have " +"permissions semantics beyond the usual POSIX permission-bit model." +msgstr "" + +#: ../Doc/library/os.rst:1432 +msgid "Added the *dir_fd*, *effective_ids*, and *follow_symlinks* parameters." +msgstr "" + +#: ../Doc/library/os.rst:1444 +msgid "" +"Values to pass as the *mode* parameter of :func:`access` to test the " +"existence, readability, writability and executability of *path*, " +"respectively." +msgstr "" + +#: ../Doc/library/os.rst:1453 +msgid "Change the current working directory to *path*." +msgstr "" + +#: ../Doc/library/os.rst:1455 +msgid "" +"This function can support :ref:`specifying a file descriptor `. " +"The descriptor must refer to an opened directory, not an open file." +msgstr "" + +#: ../Doc/library/os.rst:1458 +msgid "" +"Added support for specifying *path* as a file descriptor on some platforms." +msgstr "" + +#: ../Doc/library/os.rst:1468 +msgid "" +"Set the flags of *path* to the numeric *flags*. *flags* may take a " +"combination (bitwise OR) of the following values (as defined in the :mod:" +"`stat` module):" +msgstr "" + +#: ../Doc/library/os.rst:1471 +msgid ":data:`stat.UF_NODUMP`" +msgstr "" + +#: ../Doc/library/os.rst:1472 +msgid ":data:`stat.UF_IMMUTABLE`" +msgstr "" + +#: ../Doc/library/os.rst:1473 +msgid ":data:`stat.UF_APPEND`" +msgstr "" + +#: ../Doc/library/os.rst:1474 +msgid ":data:`stat.UF_OPAQUE`" +msgstr "" + +#: ../Doc/library/os.rst:1475 +msgid ":data:`stat.UF_NOUNLINK`" +msgstr "" + +#: ../Doc/library/os.rst:1476 +msgid ":data:`stat.UF_COMPRESSED`" +msgstr "" + +#: ../Doc/library/os.rst:1477 +msgid ":data:`stat.UF_HIDDEN`" +msgstr "" + +#: ../Doc/library/os.rst:1478 +msgid ":data:`stat.SF_ARCHIVED`" +msgstr "" + +#: ../Doc/library/os.rst:1479 +msgid ":data:`stat.SF_IMMUTABLE`" +msgstr "" + +#: ../Doc/library/os.rst:1480 +msgid ":data:`stat.SF_APPEND`" +msgstr "" + +#: ../Doc/library/os.rst:1481 +msgid ":data:`stat.SF_NOUNLINK`" +msgstr "" + +#: ../Doc/library/os.rst:1482 +msgid ":data:`stat.SF_SNAPSHOT`" +msgstr "" + +#: ../Doc/library/os.rst:1484 +msgid "" +"This function can support :ref:`not following symlinks `." +msgstr "" + +#: ../Doc/library/os.rst:1488 +msgid "The *follow_symlinks* argument." +msgstr "" + +#: ../Doc/library/os.rst:1497 +msgid "" +"Change the mode of *path* to the numeric *mode*. *mode* may take one of the " +"following values (as defined in the :mod:`stat` module) or bitwise ORed " +"combinations of them:" +msgstr "" + +#: ../Doc/library/os.rst:1501 +msgid ":data:`stat.S_ISUID`" +msgstr "" + +#: ../Doc/library/os.rst:1502 +msgid ":data:`stat.S_ISGID`" +msgstr "" + +#: ../Doc/library/os.rst:1503 +msgid ":data:`stat.S_ENFMT`" +msgstr "" + +#: ../Doc/library/os.rst:1504 +msgid ":data:`stat.S_ISVTX`" +msgstr "" + +#: ../Doc/library/os.rst:1505 +msgid ":data:`stat.S_IREAD`" +msgstr "" + +#: ../Doc/library/os.rst:1506 +msgid ":data:`stat.S_IWRITE`" +msgstr "" + +#: ../Doc/library/os.rst:1507 +msgid ":data:`stat.S_IEXEC`" +msgstr "" + +#: ../Doc/library/os.rst:1508 +msgid ":data:`stat.S_IRWXU`" +msgstr "" + +#: ../Doc/library/os.rst:1509 +msgid ":data:`stat.S_IRUSR`" +msgstr "" + +#: ../Doc/library/os.rst:1510 +msgid ":data:`stat.S_IWUSR`" +msgstr "" + +#: ../Doc/library/os.rst:1511 +msgid ":data:`stat.S_IXUSR`" +msgstr "" + +#: ../Doc/library/os.rst:1512 +msgid ":data:`stat.S_IRWXG`" +msgstr "" + +#: ../Doc/library/os.rst:1513 +msgid ":data:`stat.S_IRGRP`" +msgstr "" + +#: ../Doc/library/os.rst:1514 +msgid ":data:`stat.S_IWGRP`" +msgstr "" + +#: ../Doc/library/os.rst:1515 +msgid ":data:`stat.S_IXGRP`" +msgstr "" + +#: ../Doc/library/os.rst:1516 +msgid ":data:`stat.S_IRWXO`" +msgstr "" + +#: ../Doc/library/os.rst:1517 +msgid ":data:`stat.S_IROTH`" +msgstr "" + +#: ../Doc/library/os.rst:1518 +msgid ":data:`stat.S_IWOTH`" +msgstr "" + +#: ../Doc/library/os.rst:1519 +msgid ":data:`stat.S_IXOTH`" +msgstr "" + +#: ../Doc/library/os.rst:1521 ../Doc/library/os.rst:1544 +#: ../Doc/library/os.rst:2681 +msgid "" +"This function can support :ref:`specifying a file descriptor `, :" +"ref:`paths relative to directory descriptors ` and :ref:`not " +"following symlinks `." +msgstr "" + +#: ../Doc/library/os.rst:1527 +msgid "" +"Although Windows supports :func:`chmod`, you can only set the file's read-" +"only flag with it (via the ``stat.S_IWRITE`` and ``stat.S_IREAD`` constants " +"or a corresponding integer value). All other bits are ignored." +msgstr "" + +#: ../Doc/library/os.rst:1531 +msgid "" +"Added support for specifying *path* as an open file descriptor, and the " +"*dir_fd* and *follow_symlinks* arguments." +msgstr "" + +#: ../Doc/library/os.rst:1541 +msgid "" +"Change the owner and group id of *path* to the numeric *uid* and *gid*. To " +"leave one of the ids unchanged, set it to -1." +msgstr "" + +#: ../Doc/library/os.rst:1548 +msgid "" +"See :func:`shutil.chown` for a higher-level function that accepts names in " +"addition to numeric ids." +msgstr "" + +#: ../Doc/library/os.rst:1553 +msgid "" +"Added support for specifying an open file descriptor for *path*, and the " +"*dir_fd* and *follow_symlinks* arguments." +msgstr "" + +#: ../Doc/library/os.rst:1557 +msgid "Supports a :term:`path-like object`." +msgstr "" + +#: ../Doc/library/os.rst:1563 +msgid "Change the root directory of the current process to *path*." +msgstr "" + +#: ../Doc/library/os.rst:1573 +msgid "" +"Change the current working directory to the directory represented by the " +"file descriptor *fd*. The descriptor must refer to an opened directory, not " +"an open file. As of Python 3.3, this is equivalent to ``os.chdir(fd)``." +msgstr "" + +#: ../Doc/library/os.rst:1582 +msgid "Return a string representing the current working directory." +msgstr "" + +#: ../Doc/library/os.rst:1587 +msgid "Return a bytestring representing the current working directory." +msgstr "" + +#: ../Doc/library/os.rst:1592 +msgid "" +"Set the flags of *path* to the numeric *flags*, like :func:`chflags`, but do " +"not follow symbolic links. As of Python 3.3, this is equivalent to ``os." +"chflags(path, flags, follow_symlinks=False)``." +msgstr "" + +#: ../Doc/library/os.rst:1604 +msgid "" +"Change the mode of *path* to the numeric *mode*. If path is a symlink, this " +"affects the symlink rather than the target. See the docs for :func:`chmod` " +"for possible values of *mode*. As of Python 3.3, this is equivalent to ``os." +"chmod(path, mode, follow_symlinks=False)``." +msgstr "" + +#: ../Doc/library/os.rst:1616 +msgid "" +"Change the owner and group id of *path* to the numeric *uid* and *gid*. " +"This function will not follow symbolic links. As of Python 3.3, this is " +"equivalent to ``os.chown(path, uid, gid, follow_symlinks=False)``." +msgstr "" + +#: ../Doc/library/os.rst:1628 +msgid "Create a hard link pointing to *src* named *dst*." +msgstr "" + +#: ../Doc/library/os.rst:1630 +msgid "" +"This function can support specifying *src_dir_fd* and/or *dst_dir_fd* to " +"supply :ref:`paths relative to directory descriptors `, and :ref:" +"`not following symlinks `." +msgstr "" + +#: ../Doc/library/os.rst:1636 ../Doc/library/os.path.rst:369 +#: ../Doc/library/os.path.rst:385 ../Doc/library/os.path.rst:401 +msgid "Added Windows support." +msgstr "" + +#: ../Doc/library/os.rst:1639 +msgid "Added the *src_dir_fd*, *dst_dir_fd*, and *follow_symlinks* arguments." +msgstr "" + +#: ../Doc/library/os.rst:1642 ../Doc/library/os.rst:1704 +#: ../Doc/library/os.rst:1949 ../Doc/library/os.rst:1982 +#: ../Doc/library/os.rst:2608 +msgid "Accepts a :term:`path-like object` for *src* and *dst*." +msgstr "" + +#: ../Doc/library/os.rst:1648 +msgid "" +"Return a list containing the names of the entries in the directory given by " +"*path*. The list is in arbitrary order, and does not include the special " +"entries ``'.'`` and ``'..'`` even if they are present in the directory." +msgstr "" + +#: ../Doc/library/os.rst:1652 +msgid "" +"*path* may be a :term:`path-like object`. If *path* is of type ``bytes`` " +"(directly or indirectly through the :class:`PathLike` interface), the " +"filenames returned will also be of type ``bytes``; in all other " +"circumstances, they will be of type ``str``." +msgstr "" + +#: ../Doc/library/os.rst:1657 +msgid "" +"This function can also support :ref:`specifying a file descriptor " +"`; the file descriptor must refer to a directory." +msgstr "" + +#: ../Doc/library/os.rst:1661 +msgid "To encode ``str`` filenames to ``bytes``, use :func:`~os.fsencode`." +msgstr "" + +#: ../Doc/library/os.rst:1665 +msgid "" +"The :func:`scandir` function returns directory entries along with file " +"attribute information, giving better performance for many common use cases." +msgstr "" + +#: ../Doc/library/os.rst:1669 +msgid "The *path* parameter became optional." +msgstr "" + +#: ../Doc/library/os.rst:1672 ../Doc/library/os.rst:2477 +msgid "Added support for specifying an open file descriptor for *path*." +msgstr "" + +#: ../Doc/library/os.rst:1681 +msgid "" +"Perform the equivalent of an :c:func:`lstat` system call on the given path. " +"Similar to :func:`~os.stat`, but does not follow symbolic links. Return a :" +"class:`stat_result` object." +msgstr "" + +#: ../Doc/library/os.rst:1685 +msgid "" +"On platforms that do not support symbolic links, this is an alias for :func:" +"`~os.stat`." +msgstr "" + +#: ../Doc/library/os.rst:1688 +msgid "" +"As of Python 3.3, this is equivalent to ``os.stat(path, dir_fd=dir_fd, " +"follow_symlinks=False)``." +msgstr "" + +#: ../Doc/library/os.rst:1691 ../Doc/library/os.rst:1722 +#: ../Doc/library/os.rst:1776 ../Doc/library/os.rst:1804 +#: ../Doc/library/os.rst:1878 +msgid "" +"This function can also support :ref:`paths relative to directory descriptors " +"`." +msgstr "" + +#: ../Doc/library/os.rst:1698 ../Doc/library/os.rst:1883 +#: ../Doc/library/os.rst:2601 +msgid "Added support for Windows 6.0 (Vista) symbolic links." +msgstr "" + +#: ../Doc/library/os.rst:1701 +msgid "Added the *dir_fd* parameter." +msgstr "" + +#: ../Doc/library/os.rst:1710 +msgid "Create a directory named *path* with numeric mode *mode*." +msgstr "" + +#: ../Doc/library/os.rst:1712 +msgid "If the directory already exists, :exc:`FileExistsError` is raised." +msgstr "" + +#: ../Doc/library/os.rst:1716 +msgid "" +"On some systems, *mode* is ignored. Where it is used, the current umask " +"value is first masked out. If bits other than the last 9 (i.e. the last 3 " +"digits of the octal representation of the *mode*) are set, their meaning is " +"platform-dependent. On some platforms, they are ignored and you should " +"call :func:`chmod` explicitly to set them." +msgstr "" + +#: ../Doc/library/os.rst:1725 +msgid "" +"It is also possible to create temporary directories; see the :mod:`tempfile` " +"module's :func:`tempfile.mkdtemp` function." +msgstr "" + +#: ../Doc/library/os.rst:1741 +msgid "" +"Recursive directory creation function. Like :func:`mkdir`, but makes all " +"intermediate-level directories needed to contain the leaf directory." +msgstr "" + +#: ../Doc/library/os.rst:1744 +msgid "" +"The *mode* parameter is passed to :func:`mkdir`; see :ref:`the mkdir() " +"description ` for how it is interpreted." +msgstr "" + +#: ../Doc/library/os.rst:1747 +msgid "" +"If *exist_ok* is ``False`` (the default), an :exc:`OSError` is raised if the " +"target directory already exists." +msgstr "" + +#: ../Doc/library/os.rst:1752 +msgid "" +":func:`makedirs` will become confused if the path elements to create " +"include :data:`pardir` (eg. \"..\" on UNIX systems)." +msgstr "" + +#: ../Doc/library/os.rst:1755 +msgid "This function handles UNC paths correctly." +msgstr "" + +#: ../Doc/library/os.rst:1757 +msgid "The *exist_ok* parameter." +msgstr "" + +#: ../Doc/library/os.rst:1762 +msgid "" +"Before Python 3.4.1, if *exist_ok* was ``True`` and the directory existed, :" +"func:`makedirs` would still raise an error if *mode* did not match the mode " +"of the existing directory. Since this behavior was impossible to implement " +"safely, it was removed in Python 3.4.1. See :issue:`21082`." +msgstr "" + +#: ../Doc/library/os.rst:1773 +msgid "" +"Create a FIFO (a named pipe) named *path* with numeric mode *mode*. The " +"current umask value is first masked out from the mode." +msgstr "" + +#: ../Doc/library/os.rst:1779 +msgid "" +"FIFOs are pipes that can be accessed like regular files. FIFOs exist until " +"they are deleted (for example with :func:`os.unlink`). Generally, FIFOs are " +"used as rendezvous between \"client\" and \"server\" type processes: the " +"server opens the FIFO for reading, and the client opens it for writing. " +"Note that :func:`mkfifo` doesn't open the FIFO --- it just creates the " +"rendezvous point." +msgstr "" + +#: ../Doc/library/os.rst:1796 +msgid "" +"Create a filesystem node (file, device special file or named pipe) named " +"*path*. *mode* specifies both the permissions to use and the type of node to " +"be created, being combined (bitwise OR) with one of ``stat.S_IFREG``, ``stat." +"S_IFCHR``, ``stat.S_IFBLK``, and ``stat.S_IFIFO`` (those constants are " +"available in :mod:`stat`). For ``stat.S_IFCHR`` and ``stat.S_IFBLK``, " +"*device* defines the newly created device special file (probably using :func:" +"`os.makedev`), otherwise it is ignored." +msgstr "" + +#: ../Doc/library/os.rst:1818 +msgid "" +"Extract the device major number from a raw device number (usually the :attr:" +"`st_dev` or :attr:`st_rdev` field from :c:type:`stat`)." +msgstr "" + +#: ../Doc/library/os.rst:1824 +msgid "" +"Extract the device minor number from a raw device number (usually the :attr:" +"`st_dev` or :attr:`st_rdev` field from :c:type:`stat`)." +msgstr "" + +#: ../Doc/library/os.rst:1830 +msgid "Compose a raw device number from the major and minor device numbers." +msgstr "" + +#: ../Doc/library/os.rst:1835 +msgid "" +"Return system configuration information relevant to a named file. *name* " +"specifies the configuration value to retrieve; it may be a string which is " +"the name of a defined system value; these names are specified in a number of " +"standards (POSIX.1, Unix 95, Unix 98, and others). Some platforms define " +"additional names as well. The names known to the host operating system are " +"given in the ``pathconf_names`` dictionary. For configuration variables not " +"included in that mapping, passing an integer for *name* is also accepted." +msgstr "" + +#: ../Doc/library/os.rst:1848 ../Doc/library/os.rst:2470 +#: ../Doc/library/os.rst:2626 +msgid "" +"This function can support :ref:`specifying a file descriptor `." +msgstr "" + +#: ../Doc/library/os.rst:1859 +msgid "" +"Dictionary mapping names accepted by :func:`pathconf` and :func:`fpathconf` " +"to the integer values defined for those names by the host operating system. " +"This can be used to determine the set of names known to the system." +msgstr "" + +#: ../Doc/library/os.rst:1868 +msgid "" +"Return a string representing the path to which the symbolic link points. " +"The result may be either an absolute or relative pathname; if it is " +"relative, it may be converted to an absolute pathname using ``os.path." +"join(os.path.dirname(path), result)``." +msgstr "" + +#: ../Doc/library/os.rst:1873 +msgid "" +"If the *path* is a string object (directly or indirectly through a :class:" +"`PathLike` interface), the result will also be a string object, and the call " +"may raise a UnicodeDecodeError. If the *path* is a bytes object (direct or " +"indirectly), the result will be a bytes object." +msgstr "" + +#: ../Doc/library/os.rst:1881 ../Doc/library/os.path.rst:88 +msgid "Availability: Unix, Windows" +msgstr "" + +#: ../Doc/library/os.rst:1895 +msgid "" +"Remove (delete) the file *path*. If *path* is a directory, :exc:`OSError` " +"is raised. Use :func:`rmdir` to remove directories." +msgstr "" + +#: ../Doc/library/os.rst:1898 ../Doc/library/os.rst:1992 +#: ../Doc/library/os.rst:2584 +msgid "" +"This function can support :ref:`paths relative to directory descriptors " +"`." +msgstr "" + +#: ../Doc/library/os.rst:1901 +msgid "" +"On Windows, attempting to remove a file that is in use causes an exception " +"to be raised; on Unix, the directory entry is removed but the storage " +"allocated to the file is not made available until the original file is no " +"longer in use." +msgstr "" + +#: ../Doc/library/os.rst:1905 +msgid "This function is semantically identical to :func:`unlink`." +msgstr "" + +#: ../Doc/library/os.rst:1918 +msgid "" +"Remove directories recursively. Works like :func:`rmdir` except that, if " +"the leaf directory is successfully removed, :func:`removedirs` tries to " +"successively remove every parent directory mentioned in *path* until an " +"error is raised (which is ignored, because it generally means that a parent " +"directory is not empty). For example, ``os.removedirs('foo/bar/baz')`` will " +"first remove the directory ``'foo/bar/baz'``, and then remove ``'foo/bar'`` " +"and ``'foo'`` if they are empty. Raises :exc:`OSError` if the leaf directory " +"could not be successfully removed." +msgstr "" + +#: ../Doc/library/os.rst:1933 +msgid "" +"Rename the file or directory *src* to *dst*. If *dst* is a directory, :exc:" +"`OSError` will be raised. On Unix, if *dst* exists and is a file, it will " +"be replaced silently if the user has permission. The operation may fail on " +"some Unix flavors if *src* and *dst* are on different filesystems. If " +"successful, the renaming will be an atomic operation (this is a POSIX " +"requirement). On Windows, if *dst* already exists, :exc:`OSError` will be " +"raised even if it is a file." +msgstr "" + +#: ../Doc/library/os.rst:1941 ../Doc/library/os.rst:1977 +msgid "" +"This function can support specifying *src_dir_fd* and/or *dst_dir_fd* to " +"supply :ref:`paths relative to directory descriptors `." +msgstr "" + +#: ../Doc/library/os.rst:1944 +msgid "" +"If you want cross-platform overwriting of the destination, use :func:" +"`replace`." +msgstr "" + +#: ../Doc/library/os.rst:1946 +msgid "The *src_dir_fd* and *dst_dir_fd* arguments." +msgstr "" + +#: ../Doc/library/os.rst:1955 +msgid "" +"Recursive directory or file renaming function. Works like :func:`rename`, " +"except creation of any intermediate directories needed to make the new " +"pathname good is attempted first. After the rename, directories " +"corresponding to rightmost path segments of the old name will be pruned away " +"using :func:`removedirs`." +msgstr "" + +#: ../Doc/library/os.rst:1962 +msgid "" +"This function can fail with the new directory structure made if you lack " +"permissions needed to remove the leaf directory or file." +msgstr "" + +#: ../Doc/library/os.rst:1965 +msgid "Accepts a :term:`path-like object` for *old* and *new*." +msgstr "" + +#: ../Doc/library/os.rst:1971 +msgid "" +"Rename the file or directory *src* to *dst*. If *dst* is a directory, :exc:" +"`OSError` will be raised. If *dst* exists and is a file, it will be " +"replaced silently if the user has permission. The operation may fail if " +"*src* and *dst* are on different filesystems. If successful, the renaming " +"will be an atomic operation (this is a POSIX requirement)." +msgstr "" + +#: ../Doc/library/os.rst:1988 +msgid "" +"Remove (delete) the directory *path*. Only works when the directory is " +"empty, otherwise, :exc:`OSError` is raised. In order to remove whole " +"directory trees, :func:`shutil.rmtree` can be used." +msgstr "" + +#: ../Doc/library/os.rst:1995 ../Doc/library/os.rst:2646 +msgid "The *dir_fd* parameter." +msgstr "" + +#: ../Doc/library/os.rst:2004 +msgid "" +"Return an iterator of :class:`os.DirEntry` objects corresponding to the " +"entries in the directory given by *path*. The entries are yielded in " +"arbitrary order, and the special entries ``'.'`` and ``'..'`` are not " +"included." +msgstr "" + +#: ../Doc/library/os.rst:2009 +msgid "" +"Using :func:`scandir` instead of :func:`listdir` can significantly increase " +"the performance of code that also needs file type or file attribute " +"information, because :class:`os.DirEntry` objects expose this information if " +"the operating system provides it when scanning a directory. All :class:`os." +"DirEntry` methods may perform a system call, but :func:`~os.DirEntry.is_dir` " +"and :func:`~os.DirEntry.is_file` usually only require a system call for " +"symbolic links; :func:`os.DirEntry.stat` always requires a system call on " +"Unix but only requires one for symbolic links on Windows." +msgstr "" + +#: ../Doc/library/os.rst:2019 +msgid "" +"On Unix, *path* can be of type :class:`str` or :class:`bytes` (either " +"directly or indirectly through the :class:`PathLike` interface; use :func:" +"`~os.fsencode` and :func:`~os.fsdecode` to encode and decode :class:`bytes` " +"paths). On Windows, *path* must be of type :class:`str`. On both systems, " +"the type of the :attr:`~os.DirEntry.name` and :attr:`~os.DirEntry.path` " +"attributes of each :class:`os.DirEntry` will be of the same type as *path*." +msgstr "" + +#: ../Doc/library/os.rst:2027 +msgid "" +"The :func:`scandir` iterator supports the :term:`context manager` protocol " +"and has the following method:" +msgstr "" + +#: ../Doc/library/os.rst:2032 +msgid "Close the iterator and free acquired resources." +msgstr "" + +#: ../Doc/library/os.rst:2034 +msgid "" +"This is called automatically when the iterator is exhausted or garbage " +"collected, or when an error happens during iterating. However it is " +"advisable to call it explicitly or use the :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/os.rst:2041 +msgid "" +"The following example shows a simple use of :func:`scandir` to display all " +"the files (excluding directories) in the given *path* that don't start with " +"``'.'``. The ``entry.is_file()`` call will generally not make an additional " +"system call::" +msgstr "" + +#: ../Doc/library/os.rst:2053 +msgid "" +"On Unix-based systems, :func:`scandir` uses the system's `opendir() `_ and " +"`readdir() `_ functions. On Windows, it uses the Win32 `FindFirstFileW " +"`_ and `FindNextFileW `_ functions." +msgstr "" + +#: ../Doc/library/os.rst:2065 +msgid "" +"Added support for the :term:`context manager` protocol and the :func:" +"`~scandir.close()` method. If a :func:`scandir` iterator is neither " +"exhausted nor explicitly closed a :exc:`ResourceWarning` will be emitted in " +"its destructor." +msgstr "" + +#: ../Doc/library/os.rst:2071 +msgid "The function accepts a :term:`path-like object`." +msgstr "" + +#: ../Doc/library/os.rst:2076 +msgid "" +"Object yielded by :func:`scandir` to expose the file path and other file " +"attributes of a directory entry." +msgstr "" + +#: ../Doc/library/os.rst:2079 +msgid "" +":func:`scandir` will provide as much of this information as possible without " +"making additional system calls. When a ``stat()`` or ``lstat()`` system call " +"is made, the ``os.DirEntry`` object will cache the result." +msgstr "" + +#: ../Doc/library/os.rst:2083 +msgid "" +"``os.DirEntry`` instances are not intended to be stored in long-lived data " +"structures; if you know the file metadata has changed or if a long time has " +"elapsed since calling :func:`scandir`, call ``os.stat(entry.path)`` to fetch " +"up-to-date information." +msgstr "" + +#: ../Doc/library/os.rst:2088 +msgid "" +"Because the ``os.DirEntry`` methods can make operating system calls, they " +"may also raise :exc:`OSError`. If you need very fine-grained control over " +"errors, you can catch :exc:`OSError` when calling one of the ``os.DirEntry`` " +"methods and handle as appropriate." +msgstr "" + +#: ../Doc/library/os.rst:2093 +msgid "" +"To be directly usable as a :term:`path-like object`, ``os.DirEntry`` " +"implements the :class:`PathLike` interface." +msgstr "" + +#: ../Doc/library/os.rst:2096 +msgid "Attributes and methods on a ``os.DirEntry`` instance are as follows:" +msgstr "" + +#: ../Doc/library/os.rst:2100 +msgid "" +"The entry's base filename, relative to the :func:`scandir` *path* argument." +msgstr "" + +#: ../Doc/library/os.rst:2103 +msgid "" +"The :attr:`name` attribute will be of the same type (``str`` or ``bytes``) " +"as the :func:`scandir` *path* argument. Use :func:`~os.fsdecode` to decode " +"byte filenames." +msgstr "" + +#: ../Doc/library/os.rst:2109 +msgid "" +"The entry's full path name: equivalent to ``os.path.join(scandir_path, entry." +"name)`` where *scandir_path* is the :func:`scandir` *path* argument. The " +"path is only absolute if the :func:`scandir` *path* argument was absolute." +msgstr "" + +#: ../Doc/library/os.rst:2114 +msgid "" +"The :attr:`path` attribute will be of the same type (``str`` or ``bytes``) " +"as the :func:`scandir` *path* argument. Use :func:`~os.fsdecode` to decode " +"byte filenames." +msgstr "" + +#: ../Doc/library/os.rst:2120 +msgid "Return the inode number of the entry." +msgstr "" + +#: ../Doc/library/os.rst:2122 +msgid "" +"The result is cached on the ``os.DirEntry`` object. Use ``os.stat(entry." +"path, follow_symlinks=False).st_ino`` to fetch up-to-date information." +msgstr "" + +#: ../Doc/library/os.rst:2126 +msgid "" +"On the first, uncached call, a system call is required on Windows but not on " +"Unix." +msgstr "" + +#: ../Doc/library/os.rst:2131 +msgid "" +"Return ``True`` if this entry is a directory or a symbolic link pointing to " +"a directory; return ``False`` if the entry is or points to any other kind of " +"file, or if it doesn't exist anymore." +msgstr "" + +#: ../Doc/library/os.rst:2135 +msgid "" +"If *follow_symlinks* is ``False``, return ``True`` only if this entry is a " +"directory (without following symlinks); return ``False`` if the entry is any " +"other kind of file or if it doesn't exist anymore." +msgstr "" + +#: ../Doc/library/os.rst:2139 +msgid "" +"The result is cached on the ``os.DirEntry`` object, with a separate cache " +"for *follow_symlinks* ``True`` and ``False``. Call :func:`os.stat` along " +"with :func:`stat.S_ISDIR` to fetch up-to-date information." +msgstr "" + +#: ../Doc/library/os.rst:2143 +msgid "" +"On the first, uncached call, no system call is required in most cases. " +"Specifically, for non-symlinks, neither Windows or Unix require a system " +"call, except on certain Unix file systems, such as network file systems, " +"that return ``dirent.d_type == DT_UNKNOWN``. If the entry is a symlink, a " +"system call will be required to follow the symlink unless *follow_symlinks* " +"is ``False``." +msgstr "" + +#: ../Doc/library/os.rst:2150 ../Doc/library/os.rst:2180 +msgid "" +"This method can raise :exc:`OSError`, such as :exc:`PermissionError`, but :" +"exc:`FileNotFoundError` is caught and not raised." +msgstr "" + +#: ../Doc/library/os.rst:2155 +msgid "" +"Return ``True`` if this entry is a file or a symbolic link pointing to a " +"file; return ``False`` if the entry is or points to a directory or other non-" +"file entry, or if it doesn't exist anymore." +msgstr "" + +#: ../Doc/library/os.rst:2159 +msgid "" +"If *follow_symlinks* is ``False``, return ``True`` only if this entry is a " +"file (without following symlinks); return ``False`` if the entry is a " +"directory or other non-file entry, or if it doesn't exist anymore." +msgstr "" + +#: ../Doc/library/os.rst:2163 +msgid "" +"The result is cached on the ``os.DirEntry`` object. Caching, system calls " +"made, and exceptions raised are as per :func:`~os.DirEntry.is_dir`." +msgstr "" + +#: ../Doc/library/os.rst:2168 +msgid "" +"Return ``True`` if this entry is a symbolic link (even if broken); return " +"``False`` if the entry points to a directory or any kind of file, or if it " +"doesn't exist anymore." +msgstr "" + +#: ../Doc/library/os.rst:2172 +msgid "" +"The result is cached on the ``os.DirEntry`` object. Call :func:`os.path." +"islink` to fetch up-to-date information." +msgstr "" + +#: ../Doc/library/os.rst:2175 +msgid "" +"On the first, uncached call, no system call is required in most cases. " +"Specifically, neither Windows or Unix require a system call, except on " +"certain Unix file systems, such as network file systems, that return " +"``dirent.d_type == DT_UNKNOWN``." +msgstr "" + +#: ../Doc/library/os.rst:2185 +msgid "" +"Return a :class:`stat_result` object for this entry. This method follows " +"symbolic links by default; to stat a symbolic link add the " +"``follow_symlinks=False`` argument." +msgstr "" + +#: ../Doc/library/os.rst:2189 +msgid "" +"On Unix, this method always requires a system call. On Windows, it only " +"requires a system call if *follow_symlinks* is ``True`` and the entry is a " +"symbolic link." +msgstr "" + +#: ../Doc/library/os.rst:2193 +msgid "" +"On Windows, the ``st_ino``, ``st_dev`` and ``st_nlink`` attributes of the :" +"class:`stat_result` are always set to zero. Call :func:`os.stat` to get " +"these attributes." +msgstr "" + +#: ../Doc/library/os.rst:2197 +msgid "" +"The result is cached on the ``os.DirEntry`` object, with a separate cache " +"for *follow_symlinks* ``True`` and ``False``. Call :func:`os.stat` to fetch " +"up-to-date information." +msgstr "" + +#: ../Doc/library/os.rst:2201 +msgid "" +"Note that there is a nice correspondence between several attributes and " +"methods of ``os.DirEntry`` and of :class:`pathlib.Path`. In particular, the " +"``name`` attribute has the same meaning, as do the ``is_dir()``, " +"``is_file()``, ``is_symlink()`` and ``stat()`` methods." +msgstr "" + +#: ../Doc/library/os.rst:2209 +msgid "Added support for the :class:`~os.PathLike` interface." +msgstr "" + +#: ../Doc/library/os.rst:2215 +msgid "" +"Get the status of a file or a file descriptor. Perform the equivalent of a :" +"c:func:`stat` system call on the given path. *path* may be specified as " +"either a string -- directly or indirectly through the :class:`PathLike` " +"interface -- or as an open file descriptor. Return a :class:`stat_result` " +"object." +msgstr "" + +#: ../Doc/library/os.rst:2221 +msgid "" +"This function normally follows symlinks; to stat a symlink add the argument " +"``follow_symlinks=False``, or use :func:`lstat`." +msgstr "" + +#: ../Doc/library/os.rst:2224 ../Doc/library/os.rst:2859 +#: ../Doc/library/os.rst:2873 ../Doc/library/os.rst:2887 +#: ../Doc/library/os.rst:2905 +msgid "" +"This function can support :ref:`specifying a file descriptor ` and :" +"ref:`not following symlinks `." +msgstr "" + +#: ../Doc/library/os.rst:2242 +msgid ":func:`fstat` and :func:`lstat` functions." +msgstr "" + +#: ../Doc/library/os.rst:2244 +msgid "" +"Added the *dir_fd* and *follow_symlinks* arguments, specifying a file " +"descriptor instead of a path." +msgstr "" + +#: ../Doc/library/os.rst:2254 +msgid "" +"Object whose attributes correspond roughly to the members of the :c:type:" +"`stat` structure. It is used for the result of :func:`os.stat`, :func:`os." +"fstat` and :func:`os.lstat`." +msgstr "" + +#: ../Doc/library/os.rst:2258 +msgid "Attributes:" +msgstr "" + +#: ../Doc/library/os.rst:2262 +msgid "File mode: file type and file mode bits (permissions)." +msgstr "" + +#: ../Doc/library/os.rst:2266 ../Doc/library/stat.rst:154 +msgid "Inode number." +msgstr "" + +#: ../Doc/library/os.rst:2270 +msgid "Identifier of the device on which this file resides." +msgstr "" + +#: ../Doc/library/os.rst:2274 +msgid "Number of hard links." +msgstr "" + +#: ../Doc/library/os.rst:2278 +msgid "User identifier of the file owner." +msgstr "" + +#: ../Doc/library/os.rst:2282 +msgid "Group identifier of the file owner." +msgstr "" + +#: ../Doc/library/os.rst:2286 +msgid "" +"Size of the file in bytes, if it is a regular file or a symbolic link. The " +"size of a symbolic link is the length of the pathname it contains, without a " +"terminating null byte." +msgstr "" + +#: ../Doc/library/os.rst:2290 +msgid "Timestamps:" +msgstr "" + +#: ../Doc/library/os.rst:2294 +msgid "Time of most recent access expressed in seconds." +msgstr "" + +#: ../Doc/library/os.rst:2298 +msgid "Time of most recent content modification expressed in seconds." +msgstr "" + +#: ../Doc/library/os.rst:2302 ../Doc/library/os.rst:2318 +msgid "Platform dependent:" +msgstr "" + +#: ../Doc/library/os.rst:2304 ../Doc/library/os.rst:2320 +msgid "the time of most recent metadata change on Unix," +msgstr "" + +#: ../Doc/library/os.rst:2305 +msgid "the time of creation on Windows, expressed in seconds." +msgstr "" + +#: ../Doc/library/os.rst:2309 +msgid "Time of most recent access expressed in nanoseconds as an integer." +msgstr "" + +#: ../Doc/library/os.rst:2313 +msgid "" +"Time of most recent content modification expressed in nanoseconds as an " +"integer." +msgstr "" + +#: ../Doc/library/os.rst:2321 +msgid "" +"the time of creation on Windows, expressed in nanoseconds as an integer." +msgstr "" + +#: ../Doc/library/os.rst:2324 +msgid "See also the :func:`stat_float_times` function." +msgstr "" + +#: ../Doc/library/os.rst:2328 +msgid "" +"The exact meaning and resolution of the :attr:`st_atime`, :attr:`st_mtime`, " +"and :attr:`st_ctime` attributes depend on the operating system and the file " +"system. For example, on Windows systems using the FAT or FAT32 file " +"systems, :attr:`st_mtime` has 2-second resolution, and :attr:`st_atime` has " +"only 1-day resolution. See your operating system documentation for details." +msgstr "" + +#: ../Doc/library/os.rst:2335 +msgid "" +"Similarly, although :attr:`st_atime_ns`, :attr:`st_mtime_ns`, and :attr:" +"`st_ctime_ns` are always expressed in nanoseconds, many systems do not " +"provide nanosecond precision. On systems that do provide nanosecond " +"precision, the floating-point object used to store :attr:`st_atime`, :attr:" +"`st_mtime`, and :attr:`st_ctime` cannot preserve all of it, and as such will " +"be slightly inexact. If you need the exact timestamps you should always use :" +"attr:`st_atime_ns`, :attr:`st_mtime_ns`, and :attr:`st_ctime_ns`." +msgstr "" + +#: ../Doc/library/os.rst:2344 +msgid "" +"On some Unix systems (such as Linux), the following attributes may also be " +"available:" +msgstr "" + +#: ../Doc/library/os.rst:2349 +msgid "" +"Number of 512-byte blocks allocated for file. This may be smaller than :attr:" +"`st_size`/512 when the file has holes." +msgstr "" + +#: ../Doc/library/os.rst:2354 +msgid "" +"\"Preferred\" blocksize for efficient file system I/O. Writing to a file in " +"smaller chunks may cause an inefficient read-modify-rewrite." +msgstr "" + +#: ../Doc/library/os.rst:2359 +msgid "Type of device if an inode device." +msgstr "" + +#: ../Doc/library/os.rst:2363 +msgid "User defined flags for file." +msgstr "" + +#: ../Doc/library/os.rst:2365 +msgid "" +"On other Unix systems (such as FreeBSD), the following attributes may be " +"available (but may be only filled out if root tries to use them):" +msgstr "" + +#: ../Doc/library/os.rst:2370 +msgid "File generation number." +msgstr "" + +#: ../Doc/library/os.rst:2374 +msgid "Time of file creation." +msgstr "" + +#: ../Doc/library/os.rst:2376 +msgid "On Mac OS systems, the following attributes may also be available:" +msgstr "" + +#: ../Doc/library/os.rst:2380 +msgid "Real size of the file." +msgstr "" + +#: ../Doc/library/os.rst:2384 +msgid "Creator of the file." +msgstr "" + +#: ../Doc/library/os.rst:2388 +msgid "File type." +msgstr "" + +#: ../Doc/library/os.rst:2390 +msgid "On Windows systems, the following attribute is also available:" +msgstr "" + +#: ../Doc/library/os.rst:2394 +msgid "" +"Windows file attributes: ``dwFileAttributes`` member of the " +"``BY_HANDLE_FILE_INFORMATION`` structure returned by :c:func:" +"`GetFileInformationByHandle`. See the ``FILE_ATTRIBUTE_*`` constants in the :" +"mod:`stat` module." +msgstr "" + +#: ../Doc/library/os.rst:2399 +msgid "" +"The standard module :mod:`stat` defines functions and constants that are " +"useful for extracting information from a :c:type:`stat` structure. (On " +"Windows, some items are filled with dummy values.)" +msgstr "" + +#: ../Doc/library/os.rst:2403 +msgid "" +"For backward compatibility, a :class:`stat_result` instance is also " +"accessible as a tuple of at least 10 integers giving the most important (and " +"portable) members of the :c:type:`stat` structure, in the order :attr:" +"`st_mode`, :attr:`st_ino`, :attr:`st_dev`, :attr:`st_nlink`, :attr:" +"`st_uid`, :attr:`st_gid`, :attr:`st_size`, :attr:`st_atime`, :attr:" +"`st_mtime`, :attr:`st_ctime`. More items may be added at the end by some " +"implementations. For compatibility with older Python versions, accessing :" +"class:`stat_result` as a tuple always returns integers." +msgstr "" + +#: ../Doc/library/os.rst:2412 +msgid "" +"Added the :attr:`st_atime_ns`, :attr:`st_mtime_ns`, and :attr:`st_ctime_ns` " +"members." +msgstr "" + +#: ../Doc/library/os.rst:2416 +msgid "Added the :attr:`st_file_attributes` member on Windows." +msgstr "" + +#: ../Doc/library/os.rst:2422 +msgid "" +"Determine whether :class:`stat_result` represents time stamps as float " +"objects. If *newvalue* is ``True``, future calls to :func:`~os.stat` return " +"floats, if it is ``False``, future calls return ints. If *newvalue* is " +"omitted, return the current setting." +msgstr "" + +#: ../Doc/library/os.rst:2427 +msgid "" +"For compatibility with older Python versions, accessing :class:`stat_result` " +"as a tuple always returns integers." +msgstr "" + +#: ../Doc/library/os.rst:2430 +msgid "" +"Python now returns float values by default. Applications which do not work " +"correctly with floating point time stamps can use this function to restore " +"the old behaviour." +msgstr "" + +#: ../Doc/library/os.rst:2434 +msgid "" +"The resolution of the timestamps (that is the smallest possible fraction) " +"depends on the system. Some systems only support second resolution; on these " +"systems, the fraction will always be zero." +msgstr "" + +#: ../Doc/library/os.rst:2438 +msgid "" +"It is recommended that this setting is only changed at program startup time " +"in the *__main__* module; libraries should never change this setting. If an " +"application uses a library that works incorrectly if floating point time " +"stamps are processed, this application should turn the feature off until the " +"library has been corrected." +msgstr "" + +#: ../Doc/library/os.rst:2449 +msgid "" +"Perform a :c:func:`statvfs` system call on the given path. The return value " +"is an object whose attributes describe the filesystem on the given path, and " +"correspond to the members of the :c:type:`statvfs` structure, namely: :attr:" +"`f_bsize`, :attr:`f_frsize`, :attr:`f_blocks`, :attr:`f_bfree`, :attr:" +"`f_bavail`, :attr:`f_files`, :attr:`f_ffree`, :attr:`f_favail`, :attr:" +"`f_flag`, :attr:`f_namemax`." +msgstr "" + +#: ../Doc/library/os.rst:2456 +msgid "" +"Two module-level constants are defined for the :attr:`f_flag` attribute's " +"bit-flags: if :const:`ST_RDONLY` is set, the filesystem is mounted read-" +"only, and if :const:`ST_NOSUID` is set, the semantics of setuid/setgid bits " +"are disabled or not supported." +msgstr "" + +#: ../Doc/library/os.rst:2461 +msgid "" +"Additional module-level constants are defined for GNU/glibc based systems. " +"These are :const:`ST_NODEV` (disallow access to device special files), :" +"const:`ST_NOEXEC` (disallow program execution), :const:`ST_SYNCHRONOUS` " +"(writes are synced at once), :const:`ST_MANDLOCK` (allow mandatory locks on " +"an FS), :const:`ST_WRITE` (write on file/directory/symlink), :const:" +"`ST_APPEND` (append-only file), :const:`ST_IMMUTABLE` (immutable file), :" +"const:`ST_NOATIME` (do not update access times), :const:`ST_NODIRATIME` (do " +"not update directory access times), :const:`ST_RELATIME` (update atime " +"relative to mtime/ctime)." +msgstr "" + +#: ../Doc/library/os.rst:2474 +msgid "The :const:`ST_RDONLY` and :const:`ST_NOSUID` constants were added." +msgstr "" + +#: ../Doc/library/os.rst:2480 +msgid "" +"The :const:`ST_NODEV`, :const:`ST_NOEXEC`, :const:`ST_SYNCHRONOUS`, :const:" +"`ST_MANDLOCK`, :const:`ST_WRITE`, :const:`ST_APPEND`, :const:" +"`ST_IMMUTABLE`, :const:`ST_NOATIME`, :const:`ST_NODIRATIME`, and :const:" +"`ST_RELATIME` constants were added." +msgstr "" + +#: ../Doc/library/os.rst:2492 +msgid "" +"A :class:`~collections.abc.Set` object indicating which functions in the :" +"mod:`os` module permit use of their *dir_fd* parameter. Different platforms " +"provide different functionality, and an option that might work on one might " +"be unsupported on another. For consistency's sakes, functions that support " +"*dir_fd* always allow specifying the parameter, but will raise an exception " +"if the functionality is not actually available." +msgstr "" + +#: ../Doc/library/os.rst:2499 +msgid "" +"To check whether a particular function permits use of its *dir_fd* " +"parameter, use the ``in`` operator on ``supports_dir_fd``. As an example, " +"this expression determines whether the *dir_fd* parameter of :func:`os.stat` " +"is locally available::" +msgstr "" + +#: ../Doc/library/os.rst:2506 +msgid "" +"Currently *dir_fd* parameters only work on Unix platforms; none of them work " +"on Windows." +msgstr "" + +#: ../Doc/library/os.rst:2514 +msgid "" +"A :class:`~collections.abc.Set` object indicating which functions in the :" +"mod:`os` module permit use of the *effective_ids* parameter for :func:`os." +"access`. If the local platform supports it, the collection will contain :" +"func:`os.access`, otherwise it will be empty." +msgstr "" + +#: ../Doc/library/os.rst:2519 +msgid "" +"To check whether you can use the *effective_ids* parameter for :func:`os." +"access`, use the ``in`` operator on ``supports_effective_ids``, like so::" +msgstr "" + +#: ../Doc/library/os.rst:2525 +msgid "" +"Currently *effective_ids* only works on Unix platforms; it does not work on " +"Windows." +msgstr "" + +#: ../Doc/library/os.rst:2533 +msgid "" +"A :class:`~collections.abc.Set` object indicating which functions in the :" +"mod:`os` module permit specifying their *path* parameter as an open file " +"descriptor. Different platforms provide different functionality, and an " +"option that might work on one might be unsupported on another. For " +"consistency's sakes, functions that support *fd* always allow specifying the " +"parameter, but will raise an exception if the functionality is not actually " +"available." +msgstr "" + +#: ../Doc/library/os.rst:2541 +msgid "" +"To check whether a particular function permits specifying an open file " +"descriptor for its *path* parameter, use the ``in`` operator on " +"``supports_fd``. As an example, this expression determines whether :func:`os." +"chdir` accepts open file descriptors when called on your local platform::" +msgstr "" + +#: ../Doc/library/os.rst:2554 +msgid "" +"A :class:`~collections.abc.Set` object indicating which functions in the :" +"mod:`os` module permit use of their *follow_symlinks* parameter. Different " +"platforms provide different functionality, and an option that might work on " +"one might be unsupported on another. For consistency's sakes, functions " +"that support *follow_symlinks* always allow specifying the parameter, but " +"will raise an exception if the functionality is not actually available." +msgstr "" + +#: ../Doc/library/os.rst:2561 +msgid "" +"To check whether a particular function permits use of its *follow_symlinks* " +"parameter, use the ``in`` operator on ``supports_follow_symlinks``. As an " +"example, this expression determines whether the *follow_symlinks* parameter " +"of :func:`os.stat` is locally available::" +msgstr "" + +#: ../Doc/library/os.rst:2573 +msgid "Create a symbolic link pointing to *src* named *dst*." +msgstr "" + +#: ../Doc/library/os.rst:2575 +msgid "" +"On Windows, a symlink represents either a file or a directory, and does not " +"morph to the target dynamically. If the target is present, the type of the " +"symlink will be created to match. Otherwise, the symlink will be created as " +"a directory if *target_is_directory* is ``True`` or a file symlink (the " +"default) otherwise. On non-Window platforms, *target_is_directory* is " +"ignored." +msgstr "" + +#: ../Doc/library/os.rst:2581 +msgid "" +"Symbolic link support was introduced in Windows 6.0 (Vista). :func:" +"`symlink` will raise a :exc:`NotImplementedError` on Windows versions " +"earlier than 6.0." +msgstr "" + +#: ../Doc/library/os.rst:2589 +msgid "" +"On Windows, the *SeCreateSymbolicLinkPrivilege* is required in order to " +"successfully create symlinks. This privilege is not typically granted to " +"regular users but is available to accounts which can escalate privileges to " +"the administrator level. Either obtaining the privilege or running your " +"application as an administrator are ways to successfully create symlinks." +msgstr "" + +#: ../Doc/library/os.rst:2596 +msgid "" +":exc:`OSError` is raised when the function is called by an unprivileged user." +msgstr "" + +#: ../Doc/library/os.rst:2604 +msgid "" +"Added the *dir_fd* argument, and now allow *target_is_directory* on non-" +"Windows platforms." +msgstr "" + +#: ../Doc/library/os.rst:2614 +msgid "Force write of everything to disk." +msgstr "" + +#: ../Doc/library/os.rst:2623 +msgid "" +"Truncate the file corresponding to *path*, so that it is at most *length* " +"bytes in size." +msgstr "" + +#: ../Doc/library/os.rst:2641 +msgid "" +"Remove (delete) the file *path*. This function is semantically identical " +"to :func:`remove`; the ``unlink`` name is its traditional Unix name. Please " +"see the documentation for :func:`remove` for further information." +msgstr "" + +#: ../Doc/library/os.rst:2655 +msgid "Set the access and modified times of the file specified by *path*." +msgstr "" + +#: ../Doc/library/os.rst:2657 +msgid "" +":func:`utime` takes two optional parameters, *times* and *ns*. These specify " +"the times set on *path* and are used as follows:" +msgstr "" + +#: ../Doc/library/os.rst:2660 +msgid "" +"If *ns* is specified, it must be a 2-tuple of the form ``(atime_ns, " +"mtime_ns)`` where each member is an int expressing nanoseconds." +msgstr "" + +#: ../Doc/library/os.rst:2663 +msgid "" +"If *times* is not ``None``, it must be a 2-tuple of the form ``(atime, " +"mtime)`` where each member is an int or float expressing seconds." +msgstr "" + +#: ../Doc/library/os.rst:2666 +msgid "" +"If *times* is ``None`` and *ns* is unspecified, this is equivalent to " +"specifying ``ns=(atime_ns, mtime_ns)`` where both times are the current time." +msgstr "" + +#: ../Doc/library/os.rst:2670 +msgid "It is an error to specify tuples for both *times* and *ns*." +msgstr "" + +#: ../Doc/library/os.rst:2672 +msgid "" +"Whether a directory can be given for *path* depends on whether the operating " +"system implements directories as files (for example, Windows does not). " +"Note that the exact times you set here may not be returned by a subsequent :" +"func:`~os.stat` call, depending on the resolution with which your operating " +"system records access and modification times; see :func:`~os.stat`. The " +"best way to preserve exact times is to use the *st_atime_ns* and " +"*st_mtime_ns* fields from the :func:`os.stat` result object with the *ns* " +"parameter to `utime`." +msgstr "" + +#: ../Doc/library/os.rst:2685 +msgid "" +"Added support for specifying an open file descriptor for *path*, and the " +"*dir_fd*, *follow_symlinks*, and *ns* parameters." +msgstr "" + +#: ../Doc/library/os.rst:2699 +msgid "" +"Generate the file names in a directory tree by walking the tree either top-" +"down or bottom-up. For each directory in the tree rooted at directory *top* " +"(including *top* itself), it yields a 3-tuple ``(dirpath, dirnames, " +"filenames)``." +msgstr "" + +#: ../Doc/library/os.rst:2704 +msgid "" +"*dirpath* is a string, the path to the directory. *dirnames* is a list of " +"the names of the subdirectories in *dirpath* (excluding ``'.'`` and " +"``'..'``). *filenames* is a list of the names of the non-directory files in " +"*dirpath*. Note that the names in the lists contain no path components. To " +"get a full path (which begins with *top*) to a file or directory in " +"*dirpath*, do ``os.path.join(dirpath, name)``." +msgstr "" + +#: ../Doc/library/os.rst:2711 +msgid "" +"If optional argument *topdown* is ``True`` or not specified, the triple for " +"a directory is generated before the triples for any of its subdirectories " +"(directories are generated top-down). If *topdown* is ``False``, the triple " +"for a directory is generated after the triples for all of its subdirectories " +"(directories are generated bottom-up). No matter the value of *topdown*, the " +"list of subdirectories is retrieved before the tuples for the directory and " +"its subdirectories are generated." +msgstr "" + +#: ../Doc/library/os.rst:2719 +msgid "" +"When *topdown* is ``True``, the caller can modify the *dirnames* list in-" +"place (perhaps using :keyword:`del` or slice assignment), and :func:`walk` " +"will only recurse into the subdirectories whose names remain in *dirnames*; " +"this can be used to prune the search, impose a specific order of visiting, " +"or even to inform :func:`walk` about directories the caller creates or " +"renames before it resumes :func:`walk` again. Modifying *dirnames* when " +"*topdown* is ``False`` has no effect on the behavior of the walk, because in " +"bottom-up mode the directories in *dirnames* are generated before *dirpath* " +"itself is generated." +msgstr "" + +#: ../Doc/library/os.rst:2728 +msgid "" +"By default, errors from the :func:`listdir` call are ignored. If optional " +"argument *onerror* is specified, it should be a function; it will be called " +"with one argument, an :exc:`OSError` instance. It can report the error to " +"continue with the walk, or raise the exception to abort the walk. Note that " +"the filename is available as the ``filename`` attribute of the exception " +"object." +msgstr "" + +#: ../Doc/library/os.rst:2734 +msgid "" +"By default, :func:`walk` will not walk down into symbolic links that resolve " +"to directories. Set *followlinks* to ``True`` to visit directories pointed " +"to by symlinks, on systems that support them." +msgstr "" + +#: ../Doc/library/os.rst:2740 +msgid "" +"Be aware that setting *followlinks* to ``True`` can lead to infinite " +"recursion if a link points to a parent directory of itself. :func:`walk` " +"does not keep track of the directories it visited already." +msgstr "" + +#: ../Doc/library/os.rst:2746 +msgid "" +"If you pass a relative pathname, don't change the current working directory " +"between resumptions of :func:`walk`. :func:`walk` never changes the current " +"directory, and assumes that its caller doesn't either." +msgstr "" + +#: ../Doc/library/os.rst:2750 ../Doc/library/os.rst:2809 +msgid "" +"This example displays the number of bytes taken by non-directory files in " +"each directory under the starting directory, except that it doesn't look " +"under any CVS subdirectory::" +msgstr "" + +#: ../Doc/library/os.rst:2763 +msgid "" +"In the next example (simple implementation of :func:`shutil.rmtree`), " +"walking the tree bottom-up is essential, :func:`rmdir` doesn't allow " +"deleting a directory before the directory is empty::" +msgstr "" + +#: ../Doc/library/os.rst:2778 +msgid "" +"This function now calls :func:`os.scandir` instead of :func:`os.listdir`, " +"making it faster by reducing the number of calls to :func:`os.stat`." +msgstr "" + +#: ../Doc/library/os.rst:2792 +msgid "" +"This behaves exactly like :func:`walk`, except that it yields a 4-tuple " +"``(dirpath, dirnames, filenames, dirfd)``, and it supports ``dir_fd``." +msgstr "" + +#: ../Doc/library/os.rst:2795 +msgid "" +"*dirpath*, *dirnames* and *filenames* are identical to :func:`walk` output, " +"and *dirfd* is a file descriptor referring to the directory *dirpath*." +msgstr "" + +#: ../Doc/library/os.rst:2798 +msgid "" +"This function always supports :ref:`paths relative to directory descriptors " +"` and :ref:`not following symlinks `. Note however " +"that, unlike other functions, the :func:`fwalk` default value for " +"*follow_symlinks* is ``False``." +msgstr "" + +#: ../Doc/library/os.rst:2805 +msgid "" +"Since :func:`fwalk` yields file descriptors, those are only valid until the " +"next iteration step, so you should duplicate them (e.g. with :func:`dup`) if " +"you want to keep them longer." +msgstr "" + +#: ../Doc/library/os.rst:2822 +msgid "" +"In the next example, walking the tree bottom-up is essential: :func:`rmdir` " +"doesn't allow deleting a directory before the directory is empty::" +msgstr "" + +#: ../Doc/library/os.rst:2846 +msgid "Linux extended attributes" +msgstr "" + +#: ../Doc/library/os.rst:2850 +msgid "These functions are all available on Linux only." +msgstr "" + +#: ../Doc/library/os.rst:2854 +msgid "" +"Return the value of the extended filesystem attribute *attribute* for " +"*path*. *attribute* can be bytes or str (directly or indirectly through the :" +"class:`PathLike` interface). If it is str, it is encoded with the filesystem " +"encoding." +msgstr "" + +#: ../Doc/library/os.rst:2862 +msgid "Accepts a :term:`path-like object` fpr *path* and *attribute*." +msgstr "" + +#: ../Doc/library/os.rst:2868 +msgid "" +"Return a list of the extended filesystem attributes on *path*. The " +"attributes in the list are represented as strings decoded with the " +"filesystem encoding. If *path* is ``None``, :func:`listxattr` will examine " +"the current directory." +msgstr "" + +#: ../Doc/library/os.rst:2882 +msgid "" +"Removes the extended filesystem attribute *attribute* from *path*. " +"*attribute* should be bytes or str (directly or indirectly through the :" +"class:`PathLike` interface). If it is a string, it is encoded with the " +"filesystem encoding." +msgstr "" + +#: ../Doc/library/os.rst:2890 ../Doc/library/os.rst:2913 +msgid "Accepts a :term:`path-like object` for *path* and *attribute*." +msgstr "" + +#: ../Doc/library/os.rst:2896 +msgid "" +"Set the extended filesystem attribute *attribute* on *path* to *value*. " +"*attribute* must be a bytes or str with no embedded NULs (directly or " +"indirectly through the :class:`PathLike` interface). If it is a str, it is " +"encoded with the filesystem encoding. *flags* may be :data:`XATTR_REPLACE` " +"or :data:`XATTR_CREATE`. If :data:`XATTR_REPLACE` is given and the attribute " +"does not exist, ``EEXISTS`` will be raised. If :data:`XATTR_CREATE` is given " +"and the attribute already exists, the attribute will not be created and " +"``ENODATA`` will be raised." +msgstr "" + +#: ../Doc/library/os.rst:2910 +msgid "" +"A bug in Linux kernel versions less than 2.6.39 caused the flags argument to " +"be ignored on some filesystems." +msgstr "" + +#: ../Doc/library/os.rst:2919 +msgid "" +"The maximum size the value of an extended attribute can be. Currently, this " +"is 64 KiB on Linux." +msgstr "" + +#: ../Doc/library/os.rst:2925 +msgid "" +"This is a possible value for the flags argument in :func:`setxattr`. It " +"indicates the operation must create an attribute." +msgstr "" + +#: ../Doc/library/os.rst:2931 +msgid "" +"This is a possible value for the flags argument in :func:`setxattr`. It " +"indicates the operation must replace an existing attribute." +msgstr "" + +#: ../Doc/library/os.rst:2938 +msgid "Process Management" +msgstr "" + +#: ../Doc/library/os.rst:2940 +msgid "These functions may be used to create and manage processes." +msgstr "" + +#: ../Doc/library/os.rst:2942 +msgid "" +"The various :func:`exec\\* ` functions take a list of arguments for " +"the new program loaded into the process. In each case, the first of these " +"arguments is passed to the new program as its own name rather than as an " +"argument a user may have typed on a command line. For the C programmer, " +"this is the ``argv[0]`` passed to a program's :c:func:`main`. For example, " +"``os.execv('/bin/echo', ['foo', 'bar'])`` will only print ``bar`` on " +"standard output; ``foo`` will seem to be ignored." +msgstr "" + +#: ../Doc/library/os.rst:2953 +msgid "" +"Generate a :const:`SIGABRT` signal to the current process. On Unix, the " +"default behavior is to produce a core dump; on Windows, the process " +"immediately returns an exit code of ``3``. Be aware that calling this " +"function will not call the Python signal handler registered for :const:" +"`SIGABRT` with :func:`signal.signal`." +msgstr "" + +#: ../Doc/library/os.rst:2969 +msgid "" +"These functions all execute a new program, replacing the current process; " +"they do not return. On Unix, the new executable is loaded into the current " +"process, and will have the same process id as the caller. Errors will be " +"reported as :exc:`OSError` exceptions." +msgstr "" + +#: ../Doc/library/os.rst:2974 +msgid "" +"The current process is replaced immediately. Open file objects and " +"descriptors are not flushed, so if there may be data buffered on these open " +"files, you should flush them using :func:`sys.stdout.flush` or :func:`os." +"fsync` before calling an :func:`exec\\* ` function." +msgstr "" + +#: ../Doc/library/os.rst:2980 +msgid "" +"The \"l\" and \"v\" variants of the :func:`exec\\* ` functions differ " +"in how command-line arguments are passed. The \"l\" variants are perhaps " +"the easiest to work with if the number of parameters is fixed when the code " +"is written; the individual parameters simply become additional parameters to " +"the :func:`execl\\*` functions. The \"v\" variants are good when the number " +"of parameters is variable, with the arguments being passed in a list or " +"tuple as the *args* parameter. In either case, the arguments to the child " +"process should start with the name of the command being run, but this is not " +"enforced." +msgstr "" + +#: ../Doc/library/os.rst:2989 +msgid "" +"The variants which include a \"p\" near the end (:func:`execlp`, :func:" +"`execlpe`, :func:`execvp`, and :func:`execvpe`) will use the :envvar:`PATH` " +"environment variable to locate the program *file*. When the environment is " +"being replaced (using one of the :func:`exec\\*e ` variants, " +"discussed in the next paragraph), the new environment is used as the source " +"of the :envvar:`PATH` variable. The other variants, :func:`execl`, :func:" +"`execle`, :func:`execv`, and :func:`execve`, will not use the :envvar:`PATH` " +"variable to locate the executable; *path* must contain an appropriate " +"absolute or relative path." +msgstr "" + +#: ../Doc/library/os.rst:2999 +msgid "" +"For :func:`execle`, :func:`execlpe`, :func:`execve`, and :func:`execvpe` " +"(note that these all end in \"e\"), the *env* parameter must be a mapping " +"which is used to define the environment variables for the new process (these " +"are used instead of the current process' environment); the functions :func:" +"`execl`, :func:`execlp`, :func:`execv`, and :func:`execvp` all cause the new " +"process to inherit the environment of the current process." +msgstr "" + +#: ../Doc/library/os.rst:3006 +msgid "" +"For :func:`execve` on some platforms, *path* may also be specified as an " +"open file descriptor. This functionality may not be supported on your " +"platform; you can check whether or not it is available using :data:`os." +"supports_fd`. If it is unavailable, using it will raise a :exc:" +"`NotImplementedError`." +msgstr "" + +#: ../Doc/library/os.rst:3013 +msgid "" +"Added support for specifying an open file descriptor for *path* for :func:" +"`execve`." +msgstr "" + +#: ../Doc/library/os.rst:3022 +msgid "" +"Exit the process with status *n*, without calling cleanup handlers, flushing " +"stdio buffers, etc." +msgstr "" + +#: ../Doc/library/os.rst:3027 +msgid "" +"The standard way to exit is ``sys.exit(n)``. :func:`_exit` should normally " +"only be used in the child process after a :func:`fork`." +msgstr "" + +#: ../Doc/library/os.rst:3030 +msgid "" +"The following exit codes are defined and can be used with :func:`_exit`, " +"although they are not required. These are typically used for system " +"programs written in Python, such as a mail server's external command " +"delivery program." +msgstr "" + +#: ../Doc/library/os.rst:3036 +msgid "" +"Some of these may not be available on all Unix platforms, since there is " +"some variation. These constants are defined where they are defined by the " +"underlying platform." +msgstr "" + +#: ../Doc/library/os.rst:3043 +msgid "Exit code that means no error occurred." +msgstr "" + +#: ../Doc/library/os.rst:3050 +msgid "" +"Exit code that means the command was used incorrectly, such as when the " +"wrong number of arguments are given." +msgstr "" + +#: ../Doc/library/os.rst:3058 +msgid "Exit code that means the input data was incorrect." +msgstr "" + +#: ../Doc/library/os.rst:3065 +msgid "Exit code that means an input file did not exist or was not readable." +msgstr "" + +#: ../Doc/library/os.rst:3072 +msgid "Exit code that means a specified user did not exist." +msgstr "" + +#: ../Doc/library/os.rst:3079 +msgid "Exit code that means a specified host did not exist." +msgstr "" + +#: ../Doc/library/os.rst:3086 +msgid "Exit code that means that a required service is unavailable." +msgstr "" + +#: ../Doc/library/os.rst:3093 +msgid "Exit code that means an internal software error was detected." +msgstr "" + +#: ../Doc/library/os.rst:3100 +msgid "" +"Exit code that means an operating system error was detected, such as the " +"inability to fork or create a pipe." +msgstr "" + +#: ../Doc/library/os.rst:3108 +msgid "" +"Exit code that means some system file did not exist, could not be opened, or " +"had some other kind of error." +msgstr "" + +#: ../Doc/library/os.rst:3116 +msgid "Exit code that means a user specified output file could not be created." +msgstr "" + +#: ../Doc/library/os.rst:3123 +msgid "" +"Exit code that means that an error occurred while doing I/O on some file." +msgstr "" + +#: ../Doc/library/os.rst:3130 +msgid "" +"Exit code that means a temporary failure occurred. This indicates something " +"that may not really be an error, such as a network connection that couldn't " +"be made during a retryable operation." +msgstr "" + +#: ../Doc/library/os.rst:3139 +msgid "" +"Exit code that means that a protocol exchange was illegal, invalid, or not " +"understood." +msgstr "" + +#: ../Doc/library/os.rst:3147 +msgid "" +"Exit code that means that there were insufficient permissions to perform the " +"operation (but not intended for file system problems)." +msgstr "" + +#: ../Doc/library/os.rst:3155 +msgid "Exit code that means that some kind of configuration error occurred." +msgstr "" + +#: ../Doc/library/os.rst:3162 +msgid "Exit code that means something like \"an entry was not found\"." +msgstr "" + +#: ../Doc/library/os.rst:3169 +msgid "" +"Fork a child process. Return ``0`` in the child and the child's process id " +"in the parent. If an error occurs :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/os.rst:3172 +msgid "" +"Note that some platforms including FreeBSD <= 6.3 and Cygwin have known " +"issues when using fork() from a thread." +msgstr "" + +#: ../Doc/library/os.rst:3177 +msgid "See :mod:`ssl` for applications that use the SSL module with fork()." +msgstr "" + +#: ../Doc/library/os.rst:3184 +msgid "" +"Fork a child process, using a new pseudo-terminal as the child's controlling " +"terminal. Return a pair of ``(pid, fd)``, where *pid* is ``0`` in the child, " +"the new child's process id in the parent, and *fd* is the file descriptor of " +"the master end of the pseudo-terminal. For a more portable approach, use " +"the :mod:`pty` module. If an error occurs :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/os.rst:3199 +msgid "" +"Send signal *sig* to the process *pid*. Constants for the specific signals " +"available on the host platform are defined in the :mod:`signal` module." +msgstr "" + +#: ../Doc/library/os.rst:3202 +msgid "" +"Windows: The :data:`signal.CTRL_C_EVENT` and :data:`signal.CTRL_BREAK_EVENT` " +"signals are special signals which can only be sent to console processes " +"which share a common console window, e.g., some subprocesses. Any other " +"value for *sig* will cause the process to be unconditionally killed by the " +"TerminateProcess API, and the exit code will be set to *sig*. The Windows " +"version of :func:`kill` additionally takes process handles to be killed." +msgstr "" + +#: ../Doc/library/os.rst:3210 +msgid "See also :func:`signal.pthread_kill`." +msgstr "" + +#: ../Doc/library/os.rst:3212 +msgid "Windows support." +msgstr "" + +#: ../Doc/library/os.rst:3222 +msgid "Send the signal *sig* to the process group *pgid*." +msgstr "" + +#: ../Doc/library/os.rst:3229 +msgid "" +"Add *increment* to the process's \"niceness\". Return the new niceness." +msgstr "" + +#: ../Doc/library/os.rst:3236 +msgid "" +"Lock program segments into memory. The value of *op* (defined in ````) determines which segments are locked." +msgstr "" + +#: ../Doc/library/os.rst:3244 +msgid "" +"Open a pipe to or from command *cmd*. The return value is an open file " +"object connected to the pipe, which can be read or written depending on " +"whether *mode* is ``'r'`` (default) or ``'w'``. The *buffering* argument has " +"the same meaning as the corresponding argument to the built-in :func:`open` " +"function. The returned file object reads or writes text strings rather than " +"bytes." +msgstr "" + +#: ../Doc/library/os.rst:3251 +msgid "" +"The ``close`` method returns :const:`None` if the subprocess exited " +"successfully, or the subprocess's return code if there was an error. On " +"POSIX systems, if the return code is positive it represents the return value " +"of the process left-shifted by one byte. If the return code is negative, " +"the process was terminated by the signal given by the negated value of the " +"return code. (For example, the return value might be ``- signal.SIGKILL`` " +"if the subprocess was killed.) On Windows systems, the return value " +"contains the signed integer return code from the child process." +msgstr "" + +#: ../Doc/library/os.rst:3261 +msgid "" +"This is implemented using :class:`subprocess.Popen`; see that class's " +"documentation for more powerful ways to manage and communicate with " +"subprocesses." +msgstr "" + +#: ../Doc/library/os.rst:3275 +msgid "Execute the program *path* in a new process." +msgstr "" + +#: ../Doc/library/os.rst:3277 +msgid "" +"(Note that the :mod:`subprocess` module provides more powerful facilities " +"for spawning new processes and retrieving their results; using that module " +"is preferable to using these functions. Check especially the :ref:" +"`subprocess-replacements` section.)" +msgstr "" + +#: ../Doc/library/os.rst:3282 +msgid "" +"If *mode* is :const:`P_NOWAIT`, this function returns the process id of the " +"new process; if *mode* is :const:`P_WAIT`, returns the process's exit code " +"if it exits normally, or ``-signal``, where *signal* is the signal that " +"killed the process. On Windows, the process id will actually be the process " +"handle, so can be used with the :func:`waitpid` function." +msgstr "" + +#: ../Doc/library/os.rst:3288 +msgid "" +"The \"l\" and \"v\" variants of the :func:`spawn\\* ` functions " +"differ in how command-line arguments are passed. The \"l\" variants are " +"perhaps the easiest to work with if the number of parameters is fixed when " +"the code is written; the individual parameters simply become additional " +"parameters to the :func:`spawnl\\*` functions. The \"v\" variants are good " +"when the number of parameters is variable, with the arguments being passed " +"in a list or tuple as the *args* parameter. In either case, the arguments " +"to the child process must start with the name of the command being run." +msgstr "" + +#: ../Doc/library/os.rst:3297 +msgid "" +"The variants which include a second \"p\" near the end (:func:`spawnlp`, :" +"func:`spawnlpe`, :func:`spawnvp`, and :func:`spawnvpe`) will use the :envvar:" +"`PATH` environment variable to locate the program *file*. When the " +"environment is being replaced (using one of the :func:`spawn\\*e ` " +"variants, discussed in the next paragraph), the new environment is used as " +"the source of the :envvar:`PATH` variable. The other variants, :func:" +"`spawnl`, :func:`spawnle`, :func:`spawnv`, and :func:`spawnve`, will not use " +"the :envvar:`PATH` variable to locate the executable; *path* must contain an " +"appropriate absolute or relative path." +msgstr "" + +#: ../Doc/library/os.rst:3307 +msgid "" +"For :func:`spawnle`, :func:`spawnlpe`, :func:`spawnve`, and :func:`spawnvpe` " +"(note that these all end in \"e\"), the *env* parameter must be a mapping " +"which is used to define the environment variables for the new process (they " +"are used instead of the current process' environment); the functions :func:" +"`spawnl`, :func:`spawnlp`, :func:`spawnv`, and :func:`spawnvp` all cause the " +"new process to inherit the environment of the current process. Note that " +"keys and values in the *env* dictionary must be strings; invalid keys or " +"values will cause the function to fail, with a return value of ``127``." +msgstr "" + +#: ../Doc/library/os.rst:3316 +msgid "" +"As an example, the following calls to :func:`spawnlp` and :func:`spawnvpe` " +"are equivalent::" +msgstr "" + +#: ../Doc/library/os.rst:3325 +msgid "" +"Availability: Unix, Windows. :func:`spawnlp`, :func:`spawnlpe`, :func:" +"`spawnvp` and :func:`spawnvpe` are not available on Windows. :func:" +"`spawnle` and :func:`spawnve` are not thread-safe on Windows; we advise you " +"to use the :mod:`subprocess` module instead." +msgstr "" + +#: ../Doc/library/os.rst:3337 +msgid "" +"Possible values for the *mode* parameter to the :func:`spawn\\* ` " +"family of functions. If either of these values is given, the :func:`spawn" +"\\*` functions will return as soon as the new process has been created, with " +"the process id as the return value." +msgstr "" + +#: ../Doc/library/os.rst:3347 +msgid "" +"Possible value for the *mode* parameter to the :func:`spawn\\* ` " +"family of functions. If this is given as *mode*, the :func:`spawn\\*` " +"functions will not return until the new process has run to completion and " +"will return the exit code of the process the run is successful, or ``-" +"signal`` if a signal kills the process." +msgstr "" + +#: ../Doc/library/os.rst:3359 +msgid "" +"Possible values for the *mode* parameter to the :func:`spawn\\* ` " +"family of functions. These are less portable than those listed above. :" +"const:`P_DETACH` is similar to :const:`P_NOWAIT`, but the new process is " +"detached from the console of the calling process. If :const:`P_OVERLAY` is " +"used, the current process will be replaced; the :func:`spawn\\* ` " +"function will not return." +msgstr "" + +#: ../Doc/library/os.rst:3370 +msgid "Start a file with its associated application." +msgstr "" + +#: ../Doc/library/os.rst:3372 +msgid "" +"When *operation* is not specified or ``'open'``, this acts like double-" +"clicking the file in Windows Explorer, or giving the file name as an " +"argument to the :program:`start` command from the interactive command shell: " +"the file is opened with whatever application (if any) its extension is " +"associated." +msgstr "" + +#: ../Doc/library/os.rst:3377 +msgid "" +"When another *operation* is given, it must be a \"command verb\" that " +"specifies what should be done with the file. Common verbs documented by " +"Microsoft are ``'print'`` and ``'edit'`` (to be used on files) as well as " +"``'explore'`` and ``'find'`` (to be used on directories)." +msgstr "" + +#: ../Doc/library/os.rst:3382 +msgid "" +":func:`startfile` returns as soon as the associated application is launched. " +"There is no option to wait for the application to close, and no way to " +"retrieve the application's exit status. The *path* parameter is relative to " +"the current directory. If you want to use an absolute path, make sure the " +"first character is not a slash (``'/'``); the underlying Win32 :c:func:" +"`ShellExecute` function doesn't work if it is. Use the :func:`os.path." +"normpath` function to ensure that the path is properly encoded for Win32." +msgstr "" + +#: ../Doc/library/os.rst:3390 +msgid "" +"To reduce interpreter startup overhead, the Win32 :c:func:`ShellExecute` " +"function is not resolved until this function is first called. If the " +"function cannot be resolved, :exc:`NotImplementedError` will be raised." +msgstr "" + +#: ../Doc/library/os.rst:3399 +msgid "" +"Execute the command (a string) in a subshell. This is implemented by " +"calling the Standard C function :c:func:`system`, and has the same " +"limitations. Changes to :data:`sys.stdin`, etc. are not reflected in the " +"environment of the executed command. If *command* generates any output, it " +"will be sent to the interpreter standard output stream." +msgstr "" + +#: ../Doc/library/os.rst:3405 +msgid "" +"On Unix, the return value is the exit status of the process encoded in the " +"format specified for :func:`wait`. Note that POSIX does not specify the " +"meaning of the return value of the C :c:func:`system` function, so the " +"return value of the Python function is system-dependent." +msgstr "" + +#: ../Doc/library/os.rst:3410 +msgid "" +"On Windows, the return value is that returned by the system shell after " +"running *command*. The shell is given by the Windows environment variable :" +"envvar:`COMSPEC`: it is usually :program:`cmd.exe`, which returns the exit " +"status of the command run; on systems using a non-native shell, consult your " +"shell documentation." +msgstr "" + +#: ../Doc/library/os.rst:3416 +msgid "" +"The :mod:`subprocess` module provides more powerful facilities for spawning " +"new processes and retrieving their results; using that module is preferable " +"to using this function. See the :ref:`subprocess-replacements` section in " +"the :mod:`subprocess` documentation for some helpful recipes." +msgstr "" + +#: ../Doc/library/os.rst:3426 +msgid "" +"Returns the current global process times. The return value is an object with " +"five attributes:" +msgstr "" + +#: ../Doc/library/os.rst:3429 +msgid ":attr:`user` - user time" +msgstr "" + +#: ../Doc/library/os.rst:3430 +msgid ":attr:`system` - system time" +msgstr "" + +#: ../Doc/library/os.rst:3431 +msgid ":attr:`children_user` - user time of all child processes" +msgstr "" + +#: ../Doc/library/os.rst:3432 +msgid ":attr:`children_system` - system time of all child processes" +msgstr "" + +#: ../Doc/library/os.rst:3433 +msgid ":attr:`elapsed` - elapsed real time since a fixed point in the past" +msgstr "" + +#: ../Doc/library/os.rst:3435 +msgid "" +"For backwards compatibility, this object also behaves like a five-tuple " +"containing :attr:`user`, :attr:`system`, :attr:`children_user`, :attr:" +"`children_system`, and :attr:`elapsed` in that order." +msgstr "" + +#: ../Doc/library/os.rst:3439 +msgid "" +"See the Unix manual page :manpage:`times(2)` or the corresponding Windows " +"Platform API documentation. On Windows, only :attr:`user` and :attr:`system` " +"are known; the other attributes are zero." +msgstr "" + +#: ../Doc/library/os.rst:3453 +msgid "" +"Wait for completion of a child process, and return a tuple containing its " +"pid and exit status indication: a 16-bit number, whose low byte is the " +"signal number that killed the process, and whose high byte is the exit " +"status (if the signal number is zero); the high bit of the low byte is set " +"if a core file was produced." +msgstr "" + +#: ../Doc/library/os.rst:3463 +msgid "" +"Wait for the completion of one or more child processes. *idtype* can be :" +"data:`P_PID`, :data:`P_PGID` or :data:`P_ALL`. *id* specifies the pid to " +"wait on. *options* is constructed from the ORing of one or more of :data:" +"`WEXITED`, :data:`WSTOPPED` or :data:`WCONTINUED` and additionally may be " +"ORed with :data:`WNOHANG` or :data:`WNOWAIT`. The return value is an object " +"representing the data contained in the :c:type:`siginfo_t` structure, " +"namely: :attr:`si_pid`, :attr:`si_uid`, :attr:`si_signo`, :attr:" +"`si_status`, :attr:`si_code` or ``None`` if :data:`WNOHANG` is specified and " +"there are no children in a waitable state." +msgstr "" + +#: ../Doc/library/os.rst:3482 +msgid "" +"These are the possible values for *idtype* in :func:`waitid`. They affect " +"how *id* is interpreted." +msgstr "" + +#: ../Doc/library/os.rst:3493 +msgid "" +"Flags that can be used in *options* in :func:`waitid` that specify what " +"child signal to wait for." +msgstr "" + +#: ../Doc/library/os.rst:3506 +msgid "" +"These are the possible values for :attr:`si_code` in the result returned by :" +"func:`waitid`." +msgstr "" + +#: ../Doc/library/os.rst:3516 +msgid "The details of this function differ on Unix and Windows." +msgstr "" + +#: ../Doc/library/os.rst:3518 +msgid "" +"On Unix: Wait for completion of a child process given by process id *pid*, " +"and return a tuple containing its process id and exit status indication " +"(encoded as for :func:`wait`). The semantics of the call are affected by " +"the value of the integer *options*, which should be ``0`` for normal " +"operation." +msgstr "" + +#: ../Doc/library/os.rst:3523 +msgid "" +"If *pid* is greater than ``0``, :func:`waitpid` requests status information " +"for that specific process. If *pid* is ``0``, the request is for the status " +"of any child in the process group of the current process. If *pid* is " +"``-1``, the request pertains to any child of the current process. If *pid* " +"is less than ``-1``, status is requested for any process in the process " +"group ``-pid`` (the absolute value of *pid*)." +msgstr "" + +#: ../Doc/library/os.rst:3530 +msgid "" +"An :exc:`OSError` is raised with the value of errno when the syscall returns " +"-1." +msgstr "" + +#: ../Doc/library/os.rst:3533 +msgid "" +"On Windows: Wait for completion of a process given by process handle *pid*, " +"and return a tuple containing *pid*, and its exit status shifted left by 8 " +"bits (shifting makes cross-platform use of the function easier). A *pid* " +"less than or equal to ``0`` has no special meaning on Windows, and raises an " +"exception. The value of integer *options* has no effect. *pid* can refer to " +"any process whose id is known, not necessarily a child process. The :func:" +"`spawn\\* ` functions called with :const:`P_NOWAIT` return suitable " +"process handles." +msgstr "" + +#: ../Doc/library/os.rst:3549 +msgid "" +"Similar to :func:`waitpid`, except no process id argument is given and a 3-" +"element tuple containing the child's process id, exit status indication, and " +"resource usage information is returned. Refer to :mod:`resource`.\\ :func:" +"`~resource.getrusage` for details on resource usage information. The option " +"argument is the same as that provided to :func:`waitpid` and :func:`wait4`." +msgstr "" + +#: ../Doc/library/os.rst:3561 +msgid "" +"Similar to :func:`waitpid`, except a 3-element tuple, containing the child's " +"process id, exit status indication, and resource usage information is " +"returned. Refer to :mod:`resource`.\\ :func:`~resource.getrusage` for " +"details on resource usage information. The arguments to :func:`wait4` are " +"the same as those provided to :func:`waitpid`." +msgstr "" + +#: ../Doc/library/os.rst:3572 +msgid "" +"The option for :func:`waitpid` to return immediately if no child process " +"status is available immediately. The function returns ``(0, 0)`` in this " +"case." +msgstr "" + +#: ../Doc/library/os.rst:3580 +msgid "" +"This option causes child processes to be reported if they have been " +"continued from a job control stop since their status was last reported." +msgstr "" + +#: ../Doc/library/os.rst:3583 +msgid "Availability: some Unix systems." +msgstr "" + +#: ../Doc/library/os.rst:3588 +msgid "" +"This option causes child processes to be reported if they have been stopped " +"but their current state has not been reported since they were stopped." +msgstr "" + +#: ../Doc/library/os.rst:3594 +msgid "" +"The following functions take a process status code as returned by :func:" +"`system`, :func:`wait`, or :func:`waitpid` as a parameter. They may be used " +"to determine the disposition of a process." +msgstr "" + +#: ../Doc/library/os.rst:3600 +msgid "" +"Return ``True`` if a core dump was generated for the process, otherwise " +"return ``False``." +msgstr "" + +#: ../Doc/library/os.rst:3608 +msgid "" +"Return ``True`` if the process has been continued from a job control stop, " +"otherwise return ``False``." +msgstr "" + +#: ../Doc/library/os.rst:3616 +msgid "" +"Return ``True`` if the process has been stopped, otherwise return ``False``." +msgstr "" + +#: ../Doc/library/os.rst:3624 +msgid "" +"Return ``True`` if the process exited due to a signal, otherwise return " +"``False``." +msgstr "" + +#: ../Doc/library/os.rst:3632 +msgid "" +"Return ``True`` if the process exited using the :manpage:`exit(2)` system " +"call, otherwise return ``False``." +msgstr "" + +#: ../Doc/library/os.rst:3640 +msgid "" +"If ``WIFEXITED(status)`` is true, return the integer parameter to the :" +"manpage:`exit(2)` system call. Otherwise, the return value is meaningless." +msgstr "" + +#: ../Doc/library/os.rst:3648 +msgid "Return the signal which caused the process to stop." +msgstr "" + +#: ../Doc/library/os.rst:3655 +msgid "Return the signal which caused the process to exit." +msgstr "" + +#: ../Doc/library/os.rst:3661 +msgid "Interface to the scheduler" +msgstr "" + +#: ../Doc/library/os.rst:3663 +msgid "" +"These functions control how a process is allocated CPU time by the operating " +"system. They are only available on some Unix platforms. For more detailed " +"information, consult your Unix manpages." +msgstr "" + +#: ../Doc/library/os.rst:3669 +msgid "" +"The following scheduling policies are exposed if they are supported by the " +"operating system." +msgstr "" + +#: ../Doc/library/os.rst:3674 +msgid "The default scheduling policy." +msgstr "" + +#: ../Doc/library/os.rst:3678 +msgid "" +"Scheduling policy for CPU-intensive processes that tries to preserve " +"interactivity on the rest of the computer." +msgstr "" + +#: ../Doc/library/os.rst:3683 +msgid "Scheduling policy for extremely low priority background tasks." +msgstr "" + +#: ../Doc/library/os.rst:3687 +msgid "Scheduling policy for sporadic server programs." +msgstr "" + +#: ../Doc/library/os.rst:3691 +msgid "A First In First Out scheduling policy." +msgstr "" + +#: ../Doc/library/os.rst:3695 +msgid "A round-robin scheduling policy." +msgstr "" + +#: ../Doc/library/os.rst:3699 +msgid "" +"This flag can be OR'ed with any other scheduling policy. When a process with " +"this flag set forks, its child's scheduling policy and priority are reset to " +"the default." +msgstr "" + +#: ../Doc/library/os.rst:3706 +msgid "" +"This class represents tunable scheduling parameters used in :func:" +"`sched_setparam`, :func:`sched_setscheduler`, and :func:`sched_getparam`. It " +"is immutable." +msgstr "" + +#: ../Doc/library/os.rst:3710 +msgid "At the moment, there is only one possible parameter:" +msgstr "" + +#: ../Doc/library/os.rst:3714 +msgid "The scheduling priority for a scheduling policy." +msgstr "" + +#: ../Doc/library/os.rst:3719 +msgid "" +"Get the minimum priority value for *policy*. *policy* is one of the " +"scheduling policy constants above." +msgstr "" + +#: ../Doc/library/os.rst:3725 +msgid "" +"Get the maximum priority value for *policy*. *policy* is one of the " +"scheduling policy constants above." +msgstr "" + +#: ../Doc/library/os.rst:3731 +msgid "" +"Set the scheduling policy for the process with PID *pid*. A *pid* of 0 means " +"the calling process. *policy* is one of the scheduling policy constants " +"above. *param* is a :class:`sched_param` instance." +msgstr "" + +#: ../Doc/library/os.rst:3738 +msgid "" +"Return the scheduling policy for the process with PID *pid*. A *pid* of 0 " +"means the calling process. The result is one of the scheduling policy " +"constants above." +msgstr "" + +#: ../Doc/library/os.rst:3745 +msgid "" +"Set a scheduling parameters for the process with PID *pid*. A *pid* of 0 " +"means the calling process. *param* is a :class:`sched_param` instance." +msgstr "" + +#: ../Doc/library/os.rst:3751 +msgid "" +"Return the scheduling parameters as a :class:`sched_param` instance for the " +"process with PID *pid*. A *pid* of 0 means the calling process." +msgstr "" + +#: ../Doc/library/os.rst:3757 +msgid "" +"Return the round-robin quantum in seconds for the process with PID *pid*. A " +"*pid* of 0 means the calling process." +msgstr "" + +#: ../Doc/library/os.rst:3763 +msgid "Voluntarily relinquish the CPU." +msgstr "" + +#: ../Doc/library/os.rst:3768 +msgid "" +"Restrict the process with PID *pid* (or the current process if zero) to a " +"set of CPUs. *mask* is an iterable of integers representing the set of CPUs " +"to which the process should be restricted." +msgstr "" + +#: ../Doc/library/os.rst:3775 +msgid "" +"Return the set of CPUs the process with PID *pid* (or the current process if " +"zero) is restricted to." +msgstr "" + +#: ../Doc/library/os.rst:3782 +msgid "Miscellaneous System Information" +msgstr "" + +#: ../Doc/library/os.rst:3787 +msgid "" +"Return string-valued system configuration values. *name* specifies the " +"configuration value to retrieve; it may be a string which is the name of a " +"defined system value; these names are specified in a number of standards " +"(POSIX, Unix 95, Unix 98, and others). Some platforms define additional " +"names as well. The names known to the host operating system are given as the " +"keys of the ``confstr_names`` dictionary. For configuration variables not " +"included in that mapping, passing an integer for *name* is also accepted." +msgstr "" + +#: ../Doc/library/os.rst:3795 +msgid "" +"If the configuration value specified by *name* isn't defined, ``None`` is " +"returned." +msgstr "" + +#: ../Doc/library/os.rst:3798 +msgid "" +"If *name* is a string and is not known, :exc:`ValueError` is raised. If a " +"specific value for *name* is not supported by the host system, even if it is " +"included in ``confstr_names``, an :exc:`OSError` is raised with :const:" +"`errno.EINVAL` for the error number." +msgstr "" + +#: ../Doc/library/os.rst:3808 +msgid "" +"Dictionary mapping names accepted by :func:`confstr` to the integer values " +"defined for those names by the host operating system. This can be used to " +"determine the set of names known to the system." +msgstr "" + +#: ../Doc/library/os.rst:3817 +msgid "Return the number of CPUs in the system. Returns None if undetermined." +msgstr "" + +#: ../Doc/library/os.rst:3829 +msgid "" +"Return the number of processes in the system run queue averaged over the " +"last 1, 5, and 15 minutes or raises :exc:`OSError` if the load average was " +"unobtainable." +msgstr "" + +#: ../Doc/library/os.rst:3838 +msgid "" +"Return integer-valued system configuration values. If the configuration " +"value specified by *name* isn't defined, ``-1`` is returned. The comments " +"regarding the *name* parameter for :func:`confstr` apply here as well; the " +"dictionary that provides information on the known names is given by " +"``sysconf_names``." +msgstr "" + +#: ../Doc/library/os.rst:3848 +msgid "" +"Dictionary mapping names accepted by :func:`sysconf` to the integer values " +"defined for those names by the host operating system. This can be used to " +"determine the set of names known to the system." +msgstr "" + +#: ../Doc/library/os.rst:3854 +msgid "" +"The following data values are used to support path manipulation operations. " +"These are defined for all platforms." +msgstr "" + +#: ../Doc/library/os.rst:3857 +msgid "" +"Higher-level operations on pathnames are defined in the :mod:`os.path` " +"module." +msgstr "" + +#: ../Doc/library/os.rst:3862 +msgid "" +"The constant string used by the operating system to refer to the current " +"directory. This is ``'.'`` for Windows and POSIX. Also available via :mod:" +"`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3869 +msgid "" +"The constant string used by the operating system to refer to the parent " +"directory. This is ``'..'`` for Windows and POSIX. Also available via :mod:" +"`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3876 +msgid "" +"The character used by the operating system to separate pathname components. " +"This is ``'/'`` for POSIX and ``'\\\\'`` for Windows. Note that knowing " +"this is not sufficient to be able to parse or concatenate pathnames --- use :" +"func:`os.path.split` and :func:`os.path.join` --- but it is occasionally " +"useful. Also available via :mod:`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3885 +msgid "" +"An alternative character used by the operating system to separate pathname " +"components, or ``None`` if only one separator character exists. This is set " +"to ``'/'`` on Windows systems where ``sep`` is a backslash. Also available " +"via :mod:`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3893 +msgid "" +"The character which separates the base filename from the extension; for " +"example, the ``'.'`` in :file:`os.py`. Also available via :mod:`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3899 +msgid "" +"The character conventionally used by the operating system to separate search " +"path components (as in :envvar:`PATH`), such as ``':'`` for POSIX or ``';'`` " +"for Windows. Also available via :mod:`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3906 +msgid "" +"The default search path used by :func:`exec\\*p\\* ` and :func:`spawn" +"\\*p\\* ` if the environment doesn't have a ``'PATH'`` key. Also " +"available via :mod:`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3913 +msgid "" +"The string used to separate (or, rather, terminate) lines on the current " +"platform. This may be a single character, such as ``'\\n'`` for POSIX, or " +"multiple characters, for example, ``'\\r\\n'`` for Windows. Do not use *os." +"linesep* as a line terminator when writing files opened in text mode (the " +"default); use a single ``'\\n'`` instead, on all platforms." +msgstr "" + +#: ../Doc/library/os.rst:3922 +msgid "" +"The file path of the null device. For example: ``'/dev/null'`` for POSIX, " +"``'nul'`` for Windows. Also available via :mod:`os.path`." +msgstr "" + +#: ../Doc/library/os.rst:3933 +msgid "" +"Flags for use with the :func:`~sys.setdlopenflags` and :func:`~sys." +"getdlopenflags` functions. See the Unix manual page :manpage:`dlopen(3)` " +"for what the different flags mean." +msgstr "" + +#: ../Doc/library/os.rst:3941 ../Doc/library/secrets.rst:34 +msgid "Random numbers" +msgstr "" + +#: ../Doc/library/os.rst:3946 +msgid "" +"Get up to *size* random bytes. The function can return less bytes than " +"requested." +msgstr "" + +#: ../Doc/library/os.rst:3949 +msgid "" +"These bytes can be used to seed user-space random number generators or for " +"cryptographic purposes." +msgstr "" + +#: ../Doc/library/os.rst:3952 +msgid "" +"``getrandom()`` relies on entropy gathered from device drivers and other " +"sources of environmental noise. Unnecessarily reading large quantities of " +"data will have a negative impact on other users of the ``/dev/random`` and " +"``/dev/urandom`` devices." +msgstr "" + +#: ../Doc/library/os.rst:3957 +msgid "" +"The flags argument is a bit mask that can contain zero or more of the " +"following values ORed together: :py:data:`os.GRND_RANDOM` and :py:data:" +"`GRND_NONBLOCK`." +msgstr "" + +#: ../Doc/library/os.rst:3961 +msgid "" +"See also the `Linux getrandom() manual page `_." +msgstr "" + +#: ../Doc/library/os.rst:3964 +msgid "Availability: Linux 3.17 and newer." +msgstr "" + +#: ../Doc/library/os.rst:3970 +msgid "Return a string of *size* random bytes suitable for cryptographic use." +msgstr "" + +#: ../Doc/library/os.rst:3972 +msgid "" +"This function returns random bytes from an OS-specific randomness source. " +"The returned data should be unpredictable enough for cryptographic " +"applications, though its exact quality depends on the OS implementation." +msgstr "" + +#: ../Doc/library/os.rst:3976 +msgid "" +"On Linux, if the ``getrandom()`` syscall is available, it is used in " +"blocking mode: block until the system urandom entropy pool is initialized " +"(128 bits of entropy are collected by the kernel). See the :pep:`524` for " +"the rationale. On Linux, the :func:`getrandom` function can be used to get " +"random bytes in non-blocking mode (using the :data:`GRND_NONBLOCK` flag) or " +"to poll until the system urandom entropy pool is initialized." +msgstr "" + +#: ../Doc/library/os.rst:3983 +msgid "" +"On a Unix-like system, random bytes are read from the ``/dev/urandom`` " +"device. If the ``/dev/urandom`` device is not available or not readable, " +"the :exc:`NotImplementedError` exception is raised." +msgstr "" + +#: ../Doc/library/os.rst:3987 +msgid "On Windows, it will use ``CryptGenRandom()``." +msgstr "" + +#: ../Doc/library/os.rst:3990 +msgid "" +"The :mod:`secrets` module provides higher level functions. For an easy-to-" +"use interface to the random number generator provided by your platform, " +"please see :class:`random.SystemRandom`." +msgstr "" + +#: ../Doc/library/os.rst:3994 +msgid "" +"On Linux, ``getrandom()`` is now used in blocking mode to increase the " +"security." +msgstr "" + +#: ../Doc/library/os.rst:3998 +msgid "" +"On Linux, if the ``getrandom()`` syscall blocks (the urandom entropy pool is " +"not initialized yet), fall back on reading ``/dev/urandom``." +msgstr "" + +#: ../Doc/library/os.rst:4002 +msgid "" +"On Linux 3.17 and newer, the ``getrandom()`` syscall is now used when " +"available. On OpenBSD 5.6 and newer, the C ``getentropy()`` function is now " +"used. These functions avoid the usage of an internal file descriptor." +msgstr "" + +#: ../Doc/library/os.rst:4010 +msgid "" +"By default, when reading from ``/dev/random``, :func:`getrandom` blocks if " +"no random bytes are available, and when reading from ``/dev/urandom``, it " +"blocks if the entropy pool has not yet been initialized." +msgstr "" + +#: ../Doc/library/os.rst:4014 +msgid "" +"If the :py:data:`GRND_NONBLOCK` flag is set, then :func:`getrandom` does not " +"block in these cases, but instead immediately raises :exc:`BlockingIOError`." +msgstr "" + +#: ../Doc/library/os.rst:4021 +msgid "" +"If this bit is set, then random bytes are drawn from the ``/dev/" +"random`` pool instead of the ``/dev/urandom`` pool." +msgstr "" + +#: ../Doc/library/os.path.rst:2 +msgid ":mod:`os.path` --- Common pathname manipulations" +msgstr "" + +#: ../Doc/library/os.path.rst:7 +msgid "" +"**Source code:** :source:`Lib/posixpath.py` (for POSIX), :source:`Lib/ntpath." +"py` (for Windows NT), and :source:`Lib/macpath.py` (for Macintosh)" +msgstr "" + +#: ../Doc/library/os.path.rst:15 +msgid "" +"This module implements some useful functions on pathnames. To read or write " +"files see :func:`open`, and for accessing the filesystem see the :mod:`os` " +"module. The path parameters can be passed as either strings, or bytes. " +"Applications are encouraged to represent file names as (Unicode) character " +"strings. Unfortunately, some file names may not be representable as strings " +"on Unix, so applications that need to support arbitrary file names on Unix " +"should use bytes objects to represent path names. Vice versa, using bytes " +"objects cannot represent all file names on Windows (in the standard ``mbcs`` " +"encoding), hence Windows applications should use string objects to access " +"all files." +msgstr "" + +#: ../Doc/library/os.path.rst:26 +msgid "" +"Unlike a unix shell, Python does not do any *automatic* path expansions. " +"Functions such as :func:`expanduser` and :func:`expandvars` can be invoked " +"explicitly when an application desires shell-like path expansion. (See also " +"the :mod:`glob` module.)" +msgstr "" + +#: ../Doc/library/os.path.rst:38 +msgid "" +"All of these functions accept either only bytes or only string objects as " +"their parameters. The result is an object of the same type, if a path or " +"file name is returned." +msgstr "" + +#: ../Doc/library/os.path.rst:45 +msgid "" +"Since different operating systems have different path name conventions, " +"there are several versions of this module in the standard library. The :mod:" +"`os.path` module is always the path module suitable for the operating system " +"Python is running on, and therefore usable for local paths. However, you " +"can also import and use the individual modules if you want to manipulate a " +"path that is *always* in one of the different formats. They all have the " +"same interface:" +msgstr "" + +#: ../Doc/library/os.path.rst:53 +msgid ":mod:`posixpath` for UNIX-style paths" +msgstr "" + +#: ../Doc/library/os.path.rst:54 +msgid ":mod:`ntpath` for Windows paths" +msgstr "" + +#: ../Doc/library/os.path.rst:55 +msgid ":mod:`macpath` for old-style MacOS paths" +msgstr "" + +#: ../Doc/library/os.path.rst:60 +msgid "" +"Return a normalized absolutized version of the pathname *path*. On most " +"platforms, this is equivalent to calling the function :func:`normpath` as " +"follows: ``normpath(join(os.getcwd(), path))``." +msgstr "" + +#: ../Doc/library/os.path.rst:70 +msgid "" +"Return the base name of pathname *path*. This is the second element of the " +"pair returned by passing *path* to the function :func:`split`. Note that " +"the result of this function is different from the Unix :program:`basename` " +"program; where :program:`basename` for ``'/foo/bar/'`` returns ``'bar'``, " +"the :func:`basename` function returns an empty string (``''``)." +msgstr "" + +#: ../Doc/library/os.path.rst:83 +msgid "" +"Return the longest common sub-path of each pathname in the sequence " +"*paths*. Raise ValueError if *paths* contains both absolute and relative " +"pathnames, or if *paths* is empty. Unlike :func:`commonprefix`, this " +"returns a valid path." +msgstr "" + +#: ../Doc/library/os.path.rst:92 +msgid "Accepts a sequence of :term:`path-like objects `." +msgstr "" + +#: ../Doc/library/os.path.rst:98 +msgid "" +"Return the longest path prefix (taken character-by-character) that is a " +"prefix of all paths in *list*. If *list* is empty, return the empty string " +"(``''``)." +msgstr "" + +#: ../Doc/library/os.path.rst:104 +msgid "" +"This function may return invalid paths because it works a character at a " +"time. To obtain a valid path, see :func:`commonpath`." +msgstr "" + +#: ../Doc/library/os.path.rst:122 +msgid "" +"Return the directory name of pathname *path*. This is the first element of " +"the pair returned by passing *path* to the function :func:`split`." +msgstr "" + +#: ../Doc/library/os.path.rst:131 +msgid "" +"Return ``True`` if *path* refers to an existing path or an open file " +"descriptor. Returns ``False`` for broken symbolic links. On some " +"platforms, this function may return ``False`` if permission is not granted " +"to execute :func:`os.stat` on the requested file, even if the *path* " +"physically exists." +msgstr "" + +#: ../Doc/library/os.path.rst:137 +msgid "" +"*path* can now be an integer: ``True`` is returned if it is an open file " +"descriptor, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/os.path.rst:147 +msgid "" +"Return ``True`` if *path* refers to an existing path. Returns ``True`` for " +"broken symbolic links. Equivalent to :func:`exists` on platforms lacking :" +"func:`os.lstat`." +msgstr "" + +#: ../Doc/library/os.path.rst:157 +msgid "" +"On Unix and Windows, return the argument with an initial component of ``~`` " +"or ``~user`` replaced by that *user*'s home directory." +msgstr "" + +#: ../Doc/library/os.path.rst:162 +msgid "" +"On Unix, an initial ``~`` is replaced by the environment variable :envvar:" +"`HOME` if it is set; otherwise the current user's home directory is looked " +"up in the password directory through the built-in module :mod:`pwd`. An " +"initial ``~user`` is looked up directly in the password directory." +msgstr "" + +#: ../Doc/library/os.path.rst:167 +msgid "" +"On Windows, :envvar:`HOME` and :envvar:`USERPROFILE` will be used if set, " +"otherwise a combination of :envvar:`HOMEPATH` and :envvar:`HOMEDRIVE` will " +"be used. An initial ``~user`` is handled by stripping the last directory " +"component from the created user path derived above." +msgstr "" + +#: ../Doc/library/os.path.rst:172 +msgid "" +"If the expansion fails or if the path does not begin with a tilde, the path " +"is returned unchanged." +msgstr "" + +#: ../Doc/library/os.path.rst:181 +msgid "" +"Return the argument with environment variables expanded. Substrings of the " +"form ``$name`` or ``${name}`` are replaced by the value of environment " +"variable *name*. Malformed variable names and references to non-existing " +"variables are left unchanged." +msgstr "" + +#: ../Doc/library/os.path.rst:186 +msgid "" +"On Windows, ``%name%`` expansions are supported in addition to ``$name`` and " +"``${name}``." +msgstr "" + +#: ../Doc/library/os.path.rst:195 +msgid "" +"Return the time of last access of *path*. The return value is a number " +"giving the number of seconds since the epoch (see the :mod:`time` module). " +"Raise :exc:`OSError` if the file does not exist or is inaccessible." +msgstr "" + +#: ../Doc/library/os.path.rst:199 ../Doc/library/os.path.rst:209 +msgid "" +"If :func:`os.stat_float_times` returns ``True``, the result is a floating " +"point number." +msgstr "" + +#: ../Doc/library/os.path.rst:205 +msgid "" +"Return the time of last modification of *path*. The return value is a " +"number giving the number of seconds since the epoch (see the :mod:`time` " +"module). Raise :exc:`OSError` if the file does not exist or is inaccessible." +msgstr "" + +#: ../Doc/library/os.path.rst:218 +msgid "" +"Return the system's ctime which, on some systems (like Unix) is the time of " +"the last metadata change, and, on others (like Windows), is the creation " +"time for *path*. The return value is a number giving the number of seconds " +"since the epoch (see the :mod:`time` module). Raise :exc:`OSError` if the " +"file does not exist or is inaccessible." +msgstr "" + +#: ../Doc/library/os.path.rst:230 +msgid "" +"Return the size, in bytes, of *path*. Raise :exc:`OSError` if the file does " +"not exist or is inaccessible." +msgstr "" + +#: ../Doc/library/os.path.rst:239 +msgid "" +"Return ``True`` if *path* is an absolute pathname. On Unix, that means it " +"begins with a slash, on Windows that it begins with a (back)slash after " +"chopping off a potential drive letter." +msgstr "" + +#: ../Doc/library/os.path.rst:249 +msgid "" +"Return ``True`` if *path* is an existing regular file. This follows " +"symbolic links, so both :func:`islink` and :func:`isfile` can be true for " +"the same path." +msgstr "" + +#: ../Doc/library/os.path.rst:258 +msgid "" +"Return ``True`` if *path* is an existing directory. This follows symbolic " +"links, so both :func:`islink` and :func:`isdir` can be true for the same " +"path." +msgstr "" + +#: ../Doc/library/os.path.rst:267 +msgid "" +"Return ``True`` if *path* refers to a directory entry that is a symbolic " +"link. Always ``False`` if symbolic links are not supported by the Python " +"runtime." +msgstr "" + +#: ../Doc/library/os.path.rst:276 +msgid "" +"Return ``True`` if pathname *path* is a :dfn:`mount point`: a point in a " +"file system where a different file system has been mounted. On POSIX, the " +"function checks whether *path*'s parent, :file:`path/..`, is on a different " +"device than *path*, or whether :file:`path/..` and *path* point to the same " +"i-node on the same device --- this should detect mount points for all Unix " +"and POSIX variants. On Windows, a drive letter root and a share UNC are " +"always mount points, and for any other path ``GetVolumePathName`` is called " +"to see if it is different from the input path." +msgstr "" + +#: ../Doc/library/os.path.rst:285 +msgid "Support for detecting non-root mount points on Windows." +msgstr "" + +#: ../Doc/library/os.path.rst:294 +msgid "" +"Join one or more path components intelligently. The return value is the " +"concatenation of *path* and any members of *\\*paths* with exactly one " +"directory separator (``os.sep``) following each non-empty part except the " +"last, meaning that the result will only end in a separator if the last part " +"is empty. If a component is an absolute path, all previous components are " +"thrown away and joining continues from the absolute path component." +msgstr "" + +#: ../Doc/library/os.path.rst:302 +msgid "" +"On Windows, the drive letter is not reset when an absolute path component (e." +"g., ``r'\\foo'``) is encountered. If a component contains a drive letter, " +"all previous components are thrown away and the drive letter is reset. Note " +"that since there is a current directory for each drive, ``os.path.join(\"c:" +"\", \"foo\")`` represents a path relative to the current directory on drive :" +"file:`C:` (:file:`c:foo`), not :file:`c:\\\\foo`." +msgstr "" + +#: ../Doc/library/os.path.rst:309 +msgid "Accepts a :term:`path-like object` for *path* and *paths*." +msgstr "" + +#: ../Doc/library/os.path.rst:315 +msgid "" +"Normalize the case of a pathname. On Unix and Mac OS X, this returns the " +"path unchanged; on case-insensitive filesystems, it converts the path to " +"lowercase. On Windows, it also converts forward slashes to backward " +"slashes. Raise a TypeError if the type of *path* is not ``str`` or ``bytes`` " +"(directly or indirectly through the :class:`os.PathLike` interface)." +msgstr "" + +#: ../Doc/library/os.path.rst:327 +msgid "" +"Normalize a pathname by collapsing redundant separators and up-level " +"references so that ``A//B``, ``A/B/``, ``A/./B`` and ``A/foo/../B`` all " +"become ``A/B``. This string manipulation may change the meaning of a path " +"that contains symbolic links. On Windows, it converts forward slashes to " +"backward slashes. To normalize case, use :func:`normcase`." +msgstr "" + +#: ../Doc/library/os.path.rst:339 +msgid "" +"Return the canonical path of the specified filename, eliminating any " +"symbolic links encountered in the path (if they are supported by the " +"operating system)." +msgstr "" + +#: ../Doc/library/os.path.rst:348 +msgid "" +"Return a relative filepath to *path* either from the current directory or " +"from an optional *start* directory. This is a path computation: the " +"filesystem is not accessed to confirm the existence or nature of *path* or " +"*start*." +msgstr "" + +#: ../Doc/library/os.path.rst:353 +msgid "*start* defaults to :attr:`os.curdir`." +msgstr "" + +#: ../Doc/library/os.path.rst:363 +msgid "" +"Return ``True`` if both pathname arguments refer to the same file or " +"directory. This is determined by the device number and i-node number and " +"raises an exception if an :func:`os.stat` call on either pathname fails." +msgstr "" + +#: ../Doc/library/os.path.rst:372 +msgid "Windows now uses the same implementation as all other platforms." +msgstr "" + +#: ../Doc/library/os.path.rst:381 +msgid "" +"Return ``True`` if the file descriptors *fp1* and *fp2* refer to the same " +"file." +msgstr "" + +#: ../Doc/library/os.path.rst:394 +msgid "" +"Return ``True`` if the stat tuples *stat1* and *stat2* refer to the same " +"file. These structures may have been returned by :func:`os.fstat`, :func:`os." +"lstat`, or :func:`os.stat`. This function implements the underlying " +"comparison used by :func:`samefile` and :func:`sameopenfile`." +msgstr "" + +#: ../Doc/library/os.path.rst:410 +msgid "" +"Split the pathname *path* into a pair, ``(head, tail)`` where *tail* is the " +"last pathname component and *head* is everything leading up to that. The " +"*tail* part will never contain a slash; if *path* ends in a slash, *tail* " +"will be empty. If there is no slash in *path*, *head* will be empty. If " +"*path* is empty, both *head* and *tail* are empty. Trailing slashes are " +"stripped from *head* unless it is the root (one or more slashes only). In " +"all cases, ``join(head, tail)`` returns a path to the same location as " +"*path* (but the strings may differ). Also see the functions :func:`dirname` " +"and :func:`basename`." +msgstr "" + +#: ../Doc/library/os.path.rst:426 +msgid "" +"Split the pathname *path* into a pair ``(drive, tail)`` where *drive* is " +"either a mount point or the empty string. On systems which do not use drive " +"specifications, *drive* will always be the empty string. In all cases, " +"``drive + tail`` will be the same as *path*." +msgstr "" + +#: ../Doc/library/os.path.rst:431 +msgid "" +"On Windows, splits a pathname into drive/UNC sharepoint and relative path." +msgstr "" + +#: ../Doc/library/os.path.rst:433 +msgid "" +"If the path contains a drive letter, drive will contain everything up to and " +"including the colon. e.g. ``splitdrive(\"c:/dir\")`` returns ``(\"c:\", \"/" +"dir\")``" +msgstr "" + +#: ../Doc/library/os.path.rst:437 +msgid "" +"If the path contains a UNC path, drive will contain the host name and share, " +"up to but not including the fourth separator. e.g. ``splitdrive(\"//host/" +"computer/dir\")`` returns ``(\"//host/computer\", \"/dir\")``" +msgstr "" + +#: ../Doc/library/os.path.rst:447 +msgid "" +"Split the pathname *path* into a pair ``(root, ext)`` such that ``root + " +"ext == path``, and *ext* is empty or begins with a period and contains at " +"most one period. Leading periods on the basename are ignored; ``splitext('." +"cshrc')`` returns ``('.cshrc', '')``." +msgstr "" + +#: ../Doc/library/os.path.rst:458 +msgid "Use *splitdrive* instead." +msgstr "" + +#: ../Doc/library/os.path.rst:461 +msgid "" +"Split the pathname *path* into a pair ``(unc, rest)`` so that *unc* is the " +"UNC mount point (such as ``r'\\\\host\\mount'``), if present, and *rest* the " +"rest of the path (such as ``r'\\path\\file.ext'``). For paths containing " +"drive letters, *unc* will always be the empty string." +msgstr "" + +#: ../Doc/library/os.path.rst:466 +msgid "Availability: Windows." +msgstr "" + +#: ../Doc/library/os.path.rst:471 +msgid "" +"``True`` if arbitrary Unicode strings can be used as file names (within " +"limitations imposed by the file system)." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:2 +msgid ":mod:`ossaudiodev` --- Access to OSS-compatible audio devices" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:10 +msgid "" +"This module allows you to access the OSS (Open Sound System) audio " +"interface. OSS is available for a wide range of open-source and commercial " +"Unices, and is the standard audio interface for Linux and recent versions of " +"FreeBSD." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:50 +msgid "" +"`Open Sound System Programmer's Guide `_" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:50 +msgid "the official documentation for the OSS C API" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:52 +msgid "" +"The module defines a large number of constants supplied by the OSS device " +"driver; see ```` on either Linux or FreeBSD for a listing." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:55 +msgid ":mod:`ossaudiodev` defines the following variables and functions:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:60 +msgid "" +"This exception is raised on certain errors. The argument is a string " +"describing what went wrong." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:63 +msgid "" +"(If :mod:`ossaudiodev` receives an error from a system call such as :c:func:" +"`open`, :c:func:`write`, or :c:func:`ioctl`, it raises :exc:`OSError`. " +"Errors detected directly by :mod:`ossaudiodev` result in :exc:" +"`OSSAudioError`.)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:67 +msgid "" +"(For backwards compatibility, the exception class is also available as " +"``ossaudiodev.error``.)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:74 +msgid "" +"Open an audio device and return an OSS audio device object. This object " +"supports many file-like methods, such as :meth:`read`, :meth:`write`, and :" +"meth:`fileno` (although there are subtle differences between conventional " +"Unix read/write semantics and those of OSS audio devices). It also supports " +"a number of audio-specific methods; see below for the complete list of " +"methods." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:80 +msgid "" +"*device* is the audio device filename to use. If it is not specified, this " +"module first looks in the environment variable :envvar:`AUDIODEV` for a " +"device to use. If not found, it falls back to :file:`/dev/dsp`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:84 +msgid "" +"*mode* is one of ``'r'`` for read-only (record) access, ``'w'`` for write-" +"only (playback) access and ``'rw'`` for both. Since many sound cards only " +"allow one process to have the recorder or player open at a time, it is a " +"good idea to open the device only for the activity needed. Further, some " +"sound cards are half-duplex: they can be opened for reading or writing, but " +"not both at once." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:91 +msgid "" +"Note the unusual calling syntax: the *first* argument is optional, and the " +"second is required. This is a historical artifact for compatibility with " +"the older :mod:`linuxaudiodev` module which :mod:`ossaudiodev` supersedes." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:102 +msgid "" +"Open a mixer device and return an OSS mixer device object. *device* is the " +"mixer device filename to use. If it is not specified, this module first " +"looks in the environment variable :envvar:`MIXERDEV` for a device to use. " +"If not found, it falls back to :file:`/dev/mixer`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:111 +msgid "Audio Device Objects" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:113 +msgid "" +"Before you can write to or read from an audio device, you must call three " +"methods in the correct order:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:116 +msgid ":meth:`setfmt` to set the output format" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:118 +msgid ":meth:`channels` to set the number of channels" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:120 +msgid ":meth:`speed` to set the sample rate" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:122 +msgid "" +"Alternately, you can use the :meth:`setparameters` method to set all three " +"audio parameters at once. This is more convenient, but may not be as " +"flexible in all cases." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:126 +msgid "" +"The audio device objects returned by :func:`.open` define the following " +"methods and (read-only) attributes:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:132 +msgid "" +"Explicitly close the audio device. When you are done writing to or reading " +"from an audio device, you should explicitly close it. A closed device " +"cannot be used again." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:139 +msgid "Return the file descriptor associated with the device." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:144 +msgid "" +"Read *size* bytes from the audio input and return them as a Python string. " +"Unlike most Unix device drivers, OSS audio devices in blocking mode (the " +"default) will block :func:`read` until the entire requested amount of data " +"is available." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:152 +msgid "" +"Write a :term:`bytes-like object` *data* to the audio device and return the " +"number of bytes written. If the audio device is in blocking mode (the " +"default), the entire data is always written (again, this is different from " +"usual Unix device semantics). If the device is in non-blocking mode, some " +"data may not be written ---see :meth:`writeall`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:165 +msgid "" +"Write a :term:`bytes-like object` *data* to the audio device: waits until " +"the audio device is able to accept data, writes as much data as it will " +"accept, and repeats until *data* has been completely written. If the device " +"is in blocking mode (the default), this has the same effect as :meth:" +"`write`; :meth:`writeall` is only useful in non-blocking mode. Has no " +"return value, since the amount of data written is always equal to the amount " +"of data supplied." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:177 +msgid "" +"Audio device objects also support the context management protocol, i.e. they " +"can be used in a :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:182 +msgid "" +"The following methods each map to exactly one :c:func:`ioctl` system call. " +"The correspondence is obvious: for example, :meth:`setfmt` corresponds to " +"the ``SNDCTL_DSP_SETFMT`` ioctl, and :meth:`sync` to ``SNDCTL_DSP_SYNC`` " +"(this can be useful when consulting the OSS documentation). If the " +"underlying :c:func:`ioctl` fails, they all raise :exc:`OSError`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:191 +msgid "" +"Put the device into non-blocking mode. Once in non-blocking mode, there is " +"no way to return it to blocking mode." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:197 +msgid "" +"Return a bitmask of the audio output formats supported by the soundcard. " +"Some of the formats supported by OSS are:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:203 +msgid ":const:`AFMT_MU_LAW`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:203 +msgid "" +"a logarithmic encoding (used by Sun ``.au`` files and :file:`/dev/audio`)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:206 +msgid ":const:`AFMT_A_LAW`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:206 +msgid "a logarithmic encoding" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:208 +msgid ":const:`AFMT_IMA_ADPCM`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:208 +msgid "" +"a 4:1 compressed format defined by the Interactive Multimedia Association" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:211 +msgid ":const:`AFMT_U8`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:211 +msgid "Unsigned, 8-bit audio" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:213 +msgid ":const:`AFMT_S16_LE`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:213 +msgid "" +"Signed, 16-bit audio, little-endian byte order (as used by Intel processors)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:216 +msgid ":const:`AFMT_S16_BE`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:216 +msgid "" +"Signed, 16-bit audio, big-endian byte order (as used by 68k, PowerPC, Sparc)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:219 +msgid ":const:`AFMT_S8`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:219 +msgid "Signed, 8 bit audio" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:221 +msgid ":const:`AFMT_U16_LE`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:221 +msgid "Unsigned, 16-bit little-endian audio" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:223 +msgid ":const:`AFMT_U16_BE`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:223 +msgid "Unsigned, 16-bit big-endian audio" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:226 +msgid "" +"Consult the OSS documentation for a full list of audio formats, and note " +"that most devices support only a subset of these formats. Some older " +"devices only support :const:`AFMT_U8`; the most common format used today is :" +"const:`AFMT_S16_LE`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:234 +msgid "" +"Try to set the current audio format to *format*---see :meth:`getfmts` for a " +"list. Returns the audio format that the device was set to, which may not be " +"the requested format. May also be used to return the current audio format---" +"do this by passing an \"audio format\" of :const:`AFMT_QUERY`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:242 +msgid "" +"Set the number of output channels to *nchannels*. A value of 1 indicates " +"monophonic sound, 2 stereophonic. Some devices may have more than 2 " +"channels, and some high-end devices may not support mono. Returns the number " +"of channels the device was set to." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:250 +msgid "" +"Try to set the audio sampling rate to *samplerate* samples per second. " +"Returns the rate actually set. Most sound devices don't support arbitrary " +"sampling rates. Common rates are:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:255 +msgid "Rate" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:257 +msgid "8000" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:257 +msgid "default rate for :file:`/dev/audio`" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:259 +msgid "11025" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:259 +msgid "speech recording" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:261 +msgid "22050" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:263 +msgid "44100" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:263 +msgid "CD quality audio (at 16 bits/sample and 2 channels)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:266 +msgid "96000" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:266 +msgid "DVD quality audio (at 24 bits/sample)" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:272 +msgid "" +"Wait until the sound device has played every byte in its buffer. (This " +"happens implicitly when the device is closed.) The OSS documentation " +"recommends closing and re-opening the device rather than using :meth:`sync`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:279 +msgid "" +"Immediately stop playing or recording and return the device to a state where " +"it can accept commands. The OSS documentation recommends closing and re-" +"opening the device after calling :meth:`reset`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:286 +msgid "" +"Tell the driver that there is likely to be a pause in the output, making it " +"possible for the device to handle the pause more intelligently. You might " +"use this after playing a spot sound effect, before waiting for user input, " +"or before doing disk I/O." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:291 +msgid "" +"The following convenience methods combine several ioctls, or one ioctl and " +"some simple calculations." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:297 +msgid "" +"Set the key audio sampling parameters---sample format, number of channels, " +"and sampling rate---in one method call. *format*, *nchannels*, and " +"*samplerate* should be as specified in the :meth:`setfmt`, :meth:`channels`, " +"and :meth:`speed` methods. If *strict* is true, :meth:`setparameters` " +"checks to see if each parameter was actually set to the requested value, and " +"raises :exc:`OSSAudioError` if not. Returns a tuple (*format*, *nchannels*, " +"*samplerate*) indicating the parameter values that were actually set by the " +"device driver (i.e., the same as the return values of :meth:`setfmt`, :meth:" +"`channels`, and :meth:`speed`)." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:307 +msgid "For example, ::" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:311 +msgid "is equivalent to ::" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:320 +msgid "Returns the size of the hardware buffer, in samples." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:325 +msgid "" +"Returns the number of samples that are in the hardware buffer yet to be " +"played." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:330 +msgid "" +"Returns the number of samples that could be queued into the hardware buffer " +"to be played without blocking." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:333 +msgid "Audio device objects also support several read-only attributes:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:338 +msgid "Boolean indicating whether the device has been closed." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:343 +msgid "String containing the name of the device file." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:348 +msgid "The I/O mode for the file, either ``\"r\"``, ``\"rw\"``, or ``\"w\"``." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:354 +msgid "Mixer Device Objects" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:356 +msgid "The mixer object provides two file-like methods:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:361 +msgid "" +"This method closes the open mixer device file. Any further attempts to use " +"the mixer after this file is closed will raise an :exc:`OSError`." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:367 +msgid "Returns the file handle number of the open mixer device file." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:369 +msgid "Mixer objects also support the context management protocol." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:373 +msgid "The remaining methods are specific to audio mixing:" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:378 +msgid "" +"This method returns a bitmask specifying the available mixer controls " +"(\"Control\" being a specific mixable \"channel\", such as :const:" +"`SOUND_MIXER_PCM` or :const:`SOUND_MIXER_SYNTH`). This bitmask indicates a " +"subset of all available mixer controls---the :const:`SOUND_MIXER_\\*` " +"constants defined at module level. To determine if, for example, the current " +"mixer object supports a PCM mixer, use the following Python code::" +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:390 +msgid "" +"For most purposes, the :const:`SOUND_MIXER_VOLUME` (master volume) and :" +"const:`SOUND_MIXER_PCM` controls should suffice---but code that uses the " +"mixer should be flexible when it comes to choosing mixer controls. On the " +"Gravis Ultrasound, for example, :const:`SOUND_MIXER_VOLUME` does not exist." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:398 +msgid "" +"Returns a bitmask indicating stereo mixer controls. If a bit is set, the " +"corresponding control is stereo; if it is unset, the control is either " +"monophonic or not supported by the mixer (use in combination with :meth:" +"`controls` to determine which)." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:403 +msgid "" +"See the code example for the :meth:`controls` function for an example of " +"getting data from a bitmask." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:409 +msgid "" +"Returns a bitmask specifying the mixer controls that may be used to record. " +"See the code example for :meth:`controls` for an example of reading from a " +"bitmask." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:415 +msgid "" +"Returns the volume of a given mixer control. The returned volume is a 2-" +"tuple ``(left_volume,right_volume)``. Volumes are specified as numbers from " +"0 (silent) to 100 (full volume). If the control is monophonic, a 2-tuple is " +"still returned, but both volumes are the same." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:420 +msgid "" +"Raises :exc:`OSSAudioError` if an invalid control is specified, or :exc:" +"`OSError` if an unsupported control is specified." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:426 +msgid "" +"Sets the volume for a given mixer control to ``(left,right)``. ``left`` and " +"``right`` must be ints and between 0 (silent) and 100 (full volume). On " +"success, the new volume is returned as a 2-tuple. Note that this may not be " +"exactly the same as the volume specified, because of the limited resolution " +"of some soundcard's mixers." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:432 +msgid "" +"Raises :exc:`OSSAudioError` if an invalid mixer control was specified, or if " +"the specified volumes were out-of-range." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:438 +msgid "" +"This method returns a bitmask indicating which control(s) are currently " +"being used as a recording source." +msgstr "" + +#: ../Doc/library/ossaudiodev.rst:444 +msgid "" +"Call this function to specify a recording source. Returns a bitmask " +"indicating the new recording source (or sources) if successful; raises :exc:" +"`OSError` if an invalid source was specified. To set the current recording " +"source to the microphone input::" +msgstr "" + +#: ../Doc/library/othergui.rst:4 +msgid "Other Graphical User Interface Packages" +msgstr "" + +#: ../Doc/library/othergui.rst:6 +msgid "" +"Major cross-platform (Windows, Mac OS X, Unix-like) GUI toolkits are " +"available for Python:" +msgstr "" + +#: ../Doc/library/othergui.rst:23 +msgid "`PyGObject `_" +msgstr "" + +#: ../Doc/library/othergui.rst:12 +msgid "" +"provides introspection bindings for C libraries using `GObject `_. One of these libraries is the `GTK+ " +"3 `_ widget set. GTK+ comes with many more widgets than " +"Tkinter provides. An online `Python GTK+ 3 Tutorial `_ is available." +msgstr "" + +#: ../Doc/library/othergui.rst:19 +msgid "" +"`PyGTK `_ provides bindings for an older version of " +"the library, GTK+ 2. It provides an object oriented interface that is " +"slightly higher level than the C one. There are also bindings to `GNOME " +"`_. An online `tutorial `_ is available." +msgstr "" + +#: ../Doc/library/othergui.rst:35 +msgid "`PyQt `_" +msgstr "" + +#: ../Doc/library/othergui.rst:26 +msgid "" +"PyQt is a :program:`sip`\\ -wrapped binding to the Qt toolkit. Qt is an " +"extensive C++ GUI application development framework that is available for " +"Unix, Windows and Mac OS X. :program:`sip` is a tool for generating bindings " +"for C++ libraries as Python classes, and is specifically designed for " +"Python. The *PyQt3* bindings have a book, `GUI Programming with Python: QT " +"Edition `_ by Boudewijn " +"Rempt. The *PyQt4* bindings also have a book, `Rapid GUI Programming with " +"Python and Qt `_, by Mark Summerfield." +msgstr "" + +#: ../Doc/library/othergui.rst:40 +msgid "`PySide `_" +msgstr "" + +#: ../Doc/library/othergui.rst:38 +msgid "" +"is a newer binding to the Qt toolkit, provided by Nokia. Compared to PyQt, " +"its licensing scheme is friendlier to non-open source applications." +msgstr "" + +#: ../Doc/library/othergui.rst:53 +msgid "`wxPython `_" +msgstr "" + +#: ../Doc/library/othergui.rst:43 +msgid "" +"wxPython is a cross-platform GUI toolkit for Python that is built around the " +"popular `wxWidgets `_ (formerly wxWindows) C++ " +"toolkit. It provides a native look and feel for applications on Windows, " +"Mac OS X, and Unix systems by using each platform's native widgets where " +"ever possible, (GTK+ on Unix-like systems). In addition to an extensive set " +"of widgets, wxPython provides classes for online documentation and context " +"sensitive help, printing, HTML viewing, low-level device context drawing, " +"drag and drop, system clipboard access, an XML-based resource format and " +"more, including an ever growing library of user-contributed modules. " +"wxPython has a book, `wxPython in Action `_, by Noel Rappin and Robin Dunn." +msgstr "" + +#: ../Doc/library/othergui.rst:56 +msgid "" +"PyGTK, PyQt, and wxPython, all have a modern look and feel and more widgets " +"than Tkinter. In addition, there are many other GUI toolkits for Python, " +"both cross-platform, and platform-specific. See the `GUI Programming " +"`_ page in the Python Wiki for " +"a much more complete list, and also for links to documents where the " +"different GUI toolkits are compared." +msgstr "" + +#: ../Doc/library/parser.rst:2 +msgid ":mod:`parser` --- Access Python parse trees" +msgstr "" + +#: ../Doc/library/parser.rst:21 +msgid "" +"The :mod:`parser` module provides an interface to Python's internal parser " +"and byte-code compiler. The primary purpose for this interface is to allow " +"Python code to edit the parse tree of a Python expression and create " +"executable code from this. This is better than trying to parse and modify " +"an arbitrary Python code fragment as a string because parsing is performed " +"in a manner identical to the code forming the application. It is also " +"faster." +msgstr "" + +#: ../Doc/library/parser.rst:30 +msgid "" +"From Python 2.5 onward, it's much more convenient to cut in at the Abstract " +"Syntax Tree (AST) generation and compilation stage, using the :mod:`ast` " +"module." +msgstr "" + +#: ../Doc/library/parser.rst:34 +msgid "" +"There are a few things to note about this module which are important to " +"making use of the data structures created. This is not a tutorial on " +"editing the parse trees for Python code, but some examples of using the :mod:" +"`parser` module are presented." +msgstr "" + +#: ../Doc/library/parser.rst:39 +msgid "" +"Most importantly, a good understanding of the Python grammar processed by " +"the internal parser is required. For full information on the language " +"syntax, refer to :ref:`reference-index`. The parser itself is created from " +"a grammar specification defined in the file :file:`Grammar/Grammar` in the " +"standard Python distribution. The parse trees stored in the ST objects " +"created by this module are the actual output from the internal parser when " +"created by the :func:`expr` or :func:`suite` functions, described below. " +"The ST objects created by :func:`sequence2st` faithfully simulate those " +"structures. Be aware that the values of the sequences which are considered " +"\"correct\" will vary from one version of Python to another as the formal " +"grammar for the language is revised. However, transporting code from one " +"Python version to another as source text will always allow correct parse " +"trees to be created in the target version, with the only restriction being " +"that migrating to an older version of the interpreter will not support more " +"recent language constructs. The parse trees are not typically compatible " +"from one version to another, whereas source code has always been forward-" +"compatible." +msgstr "" + +#: ../Doc/library/parser.rst:56 +msgid "" +"Each element of the sequences returned by :func:`st2list` or :func:" +"`st2tuple` has a simple form. Sequences representing non-terminal elements " +"in the grammar always have a length greater than one. The first element is " +"an integer which identifies a production in the grammar. These integers are " +"given symbolic names in the C header file :file:`Include/graminit.h` and the " +"Python module :mod:`symbol`. Each additional element of the sequence " +"represents a component of the production as recognized in the input string: " +"these are always sequences which have the same form as the parent. An " +"important aspect of this structure which should be noted is that keywords " +"used to identify the parent node type, such as the keyword :keyword:`if` in " +"an :const:`if_stmt`, are included in the node tree without any special " +"treatment. For example, the :keyword:`if` keyword is represented by the " +"tuple ``(1, 'if')``, where ``1`` is the numeric value associated with all :" +"const:`NAME` tokens, including variable and function names defined by the " +"user. In an alternate form returned when line number information is " +"requested, the same token might be represented as ``(1, 'if', 12)``, where " +"the ``12`` represents the line number at which the terminal symbol was found." +msgstr "" + +#: ../Doc/library/parser.rst:73 +msgid "" +"Terminal elements are represented in much the same way, but without any " +"child elements and the addition of the source text which was identified. " +"The example of the :keyword:`if` keyword above is representative. The " +"various types of terminal symbols are defined in the C header file :file:" +"`Include/token.h` and the Python module :mod:`token`." +msgstr "" + +#: ../Doc/library/parser.rst:79 +msgid "" +"The ST objects are not required to support the functionality of this module, " +"but are provided for three purposes: to allow an application to amortize the " +"cost of processing complex parse trees, to provide a parse tree " +"representation which conserves memory space when compared to the Python list " +"or tuple representation, and to ease the creation of additional modules in C " +"which manipulate parse trees. A simple \"wrapper\" class may be created in " +"Python to hide the use of ST objects." +msgstr "" + +#: ../Doc/library/parser.rst:87 +msgid "" +"The :mod:`parser` module defines functions for a few distinct purposes. The " +"most important purposes are to create ST objects and to convert ST objects " +"to other representations such as parse trees and compiled code objects, but " +"there are also functions which serve to query the type of parse tree " +"represented by an ST object." +msgstr "" + +#: ../Doc/library/parser.rst:97 +msgid "Module :mod:`symbol`" +msgstr "" + +#: ../Doc/library/parser.rst:97 +msgid "Useful constants representing internal nodes of the parse tree." +msgstr "" + +#: ../Doc/library/parser.rst:100 +msgid "Module :mod:`token`" +msgstr "" + +#: ../Doc/library/parser.rst:100 +msgid "" +"Useful constants representing leaf nodes of the parse tree and functions for " +"testing node values." +msgstr "" + +#: ../Doc/library/parser.rst:107 +msgid "Creating ST Objects" +msgstr "" + +#: ../Doc/library/parser.rst:109 +msgid "" +"ST objects may be created from source code or from a parse tree. When " +"creating an ST object from source, different functions are used to create " +"the ``'eval'`` and ``'exec'`` forms." +msgstr "" + +#: ../Doc/library/parser.rst:116 +msgid "" +"The :func:`expr` function parses the parameter *source* as if it were an " +"input to ``compile(source, 'file.py', 'eval')``. If the parse succeeds, an " +"ST object is created to hold the internal parse tree representation, " +"otherwise an appropriate exception is raised." +msgstr "" + +#: ../Doc/library/parser.rst:124 +msgid "" +"The :func:`suite` function parses the parameter *source* as if it were an " +"input to ``compile(source, 'file.py', 'exec')``. If the parse succeeds, an " +"ST object is created to hold the internal parse tree representation, " +"otherwise an appropriate exception is raised." +msgstr "" + +#: ../Doc/library/parser.rst:132 +msgid "" +"This function accepts a parse tree represented as a sequence and builds an " +"internal representation if possible. If it can validate that the tree " +"conforms to the Python grammar and all nodes are valid node types in the " +"host version of Python, an ST object is created from the internal " +"representation and returned to the called. If there is a problem creating " +"the internal representation, or if the tree cannot be validated, a :exc:" +"`ParserError` exception is raised. An ST object created this way should not " +"be assumed to compile correctly; normal exceptions raised by compilation may " +"still be initiated when the ST object is passed to :func:`compilest`. This " +"may indicate problems not related to syntax (such as a :exc:`MemoryError` " +"exception), but may also be due to constructs such as the result of parsing " +"``del f(0)``, which escapes the Python parser but is checked by the bytecode " +"compiler." +msgstr "" + +#: ../Doc/library/parser.rst:145 +msgid "" +"Sequences representing terminal tokens may be represented as either two-" +"element lists of the form ``(1, 'name')`` or as three-element lists of the " +"form ``(1, 'name', 56)``. If the third element is present, it is assumed to " +"be a valid line number. The line number may be specified for any subset of " +"the terminal symbols in the input tree." +msgstr "" + +#: ../Doc/library/parser.rst:154 +msgid "" +"This is the same function as :func:`sequence2st`. This entry point is " +"maintained for backward compatibility." +msgstr "" + +#: ../Doc/library/parser.rst:161 +msgid "Converting ST Objects" +msgstr "" + +#: ../Doc/library/parser.rst:163 +msgid "" +"ST objects, regardless of the input used to create them, may be converted to " +"parse trees represented as list- or tuple- trees, or may be compiled into " +"executable code objects. Parse trees may be extracted with or without line " +"numbering information." +msgstr "" + +#: ../Doc/library/parser.rst:171 +msgid "" +"This function accepts an ST object from the caller in *st* and returns a " +"Python list representing the equivalent parse tree. The resulting list " +"representation can be used for inspection or the creation of a new parse " +"tree in list form. This function does not fail so long as memory is " +"available to build the list representation. If the parse tree will only be " +"used for inspection, :func:`st2tuple` should be used instead to reduce " +"memory consumption and fragmentation. When the list representation is " +"required, this function is significantly faster than retrieving a tuple " +"representation and converting that to nested lists." +msgstr "" + +#: ../Doc/library/parser.rst:181 +msgid "" +"If *line_info* is true, line number information will be included for all " +"terminal tokens as a third element of the list representing the token. Note " +"that the line number provided specifies the line on which the token *ends*. " +"This information is omitted if the flag is false or omitted." +msgstr "" + +#: ../Doc/library/parser.rst:189 +msgid "" +"This function accepts an ST object from the caller in *st* and returns a " +"Python tuple representing the equivalent parse tree. Other than returning a " +"tuple instead of a list, this function is identical to :func:`st2list`." +msgstr "" + +#: ../Doc/library/parser.rst:193 +msgid "" +"If *line_info* is true, line number information will be included for all " +"terminal tokens as a third element of the list representing the token. This " +"information is omitted if the flag is false or omitted." +msgstr "" + +#: ../Doc/library/parser.rst:204 +msgid "" +"The Python byte compiler can be invoked on an ST object to produce code " +"objects which can be used as part of a call to the built-in :func:`exec` or :" +"func:`eval` functions. This function provides the interface to the compiler, " +"passing the internal parse tree from *st* to the parser, using the source " +"file name specified by the *filename* parameter. The default value supplied " +"for *filename* indicates that the source was an ST object." +msgstr "" + +#: ../Doc/library/parser.rst:211 +msgid "" +"Compiling an ST object may result in exceptions related to compilation; an " +"example would be a :exc:`SyntaxError` caused by the parse tree for ``del " +"f(0)``: this statement is considered legal within the formal grammar for " +"Python but is not a legal language construct. The :exc:`SyntaxError` raised " +"for this condition is actually generated by the Python byte-compiler " +"normally, which is why it can be raised at this point by the :mod:`parser` " +"module. Most causes of compilation failure can be diagnosed " +"programmatically by inspection of the parse tree." +msgstr "" + +#: ../Doc/library/parser.rst:224 +msgid "Queries on ST Objects" +msgstr "" + +#: ../Doc/library/parser.rst:226 +msgid "" +"Two functions are provided which allow an application to determine if an ST " +"was created as an expression or a suite. Neither of these functions can be " +"used to determine if an ST was created from source code via :func:`expr` or :" +"func:`suite` or from a parse tree via :func:`sequence2st`." +msgstr "" + +#: ../Doc/library/parser.rst:236 +msgid "" +"When *st* represents an ``'eval'`` form, this function returns true, " +"otherwise it returns false. This is useful, since code objects normally " +"cannot be queried for this information using existing built-in functions. " +"Note that the code objects created by :func:`compilest` cannot be queried " +"like this either, and are identical to those created by the built-in :func:" +"`compile` function." +msgstr "" + +#: ../Doc/library/parser.rst:245 +msgid "" +"This function mirrors :func:`isexpr` in that it reports whether an ST object " +"represents an ``'exec'`` form, commonly known as a \"suite.\" It is not " +"safe to assume that this function is equivalent to ``not isexpr(st)``, as " +"additional syntactic fragments may be supported in the future." +msgstr "" + +#: ../Doc/library/parser.rst:254 +msgid "Exceptions and Error Handling" +msgstr "" + +#: ../Doc/library/parser.rst:256 +msgid "" +"The parser module defines a single exception, but may also pass other built-" +"in exceptions from other portions of the Python runtime environment. See " +"each function for information about the exceptions it can raise." +msgstr "" + +#: ../Doc/library/parser.rst:263 +msgid "" +"Exception raised when a failure occurs within the parser module. This is " +"generally produced for validation failures rather than the built-in :exc:" +"`SyntaxError` raised during normal parsing. The exception argument is either " +"a string describing the reason of the failure or a tuple containing a " +"sequence causing the failure from a parse tree passed to :func:`sequence2st` " +"and an explanatory string. Calls to :func:`sequence2st` need to be able to " +"handle either type of exception, while calls to other functions in the " +"module will only need to be aware of the simple string values." +msgstr "" + +#: ../Doc/library/parser.rst:272 +msgid "" +"Note that the functions :func:`compilest`, :func:`expr`, and :func:`suite` " +"may raise exceptions which are normally raised by the parsing and " +"compilation process. These include the built in exceptions :exc:" +"`MemoryError`, :exc:`OverflowError`, :exc:`SyntaxError`, and :exc:" +"`SystemError`. In these cases, these exceptions carry all the meaning " +"normally associated with them. Refer to the descriptions of each function " +"for detailed information." +msgstr "" + +#: ../Doc/library/parser.rst:283 +msgid "ST Objects" +msgstr "" + +#: ../Doc/library/parser.rst:285 +msgid "" +"Ordered and equality comparisons are supported between ST objects. Pickling " +"of ST objects (using the :mod:`pickle` module) is also supported." +msgstr "" + +#: ../Doc/library/parser.rst:291 +msgid "" +"The type of the objects returned by :func:`expr`, :func:`suite` and :func:" +"`sequence2st`." +msgstr "" + +#: ../Doc/library/parser.rst:294 +msgid "ST objects have the following methods:" +msgstr "" + +#: ../Doc/library/parser.rst:299 +msgid "Same as ``compilest(st, filename)``." +msgstr "" + +#: ../Doc/library/parser.rst:304 +msgid "Same as ``isexpr(st)``." +msgstr "" + +#: ../Doc/library/parser.rst:309 +msgid "Same as ``issuite(st)``." +msgstr "" + +#: ../Doc/library/parser.rst:314 +msgid "Same as ``st2list(st, line_info, col_info)``." +msgstr "" + +#: ../Doc/library/parser.rst:319 +msgid "Same as ``st2tuple(st, line_info, col_info)``." +msgstr "" + +#: ../Doc/library/parser.rst:323 +msgid "Example: Emulation of :func:`compile`" +msgstr "" + +#: ../Doc/library/parser.rst:325 +msgid "" +"While many useful operations may take place between parsing and bytecode " +"generation, the simplest operation is to do nothing. For this purpose, " +"using the :mod:`parser` module to produce an intermediate data structure is " +"equivalent to the code ::" +msgstr "" + +#: ../Doc/library/parser.rst:335 +msgid "" +"The equivalent operation using the :mod:`parser` module is somewhat longer, " +"and allows the intermediate internal parse tree to be retained as an ST " +"object::" +msgstr "" + +#: ../Doc/library/parser.rst:345 +msgid "" +"An application which needs both ST and code objects can package this code " +"into readily available functions::" +msgstr "" + +#: ../Doc/library/pathlib.rst:3 +msgid ":mod:`pathlib` --- Object-oriented filesystem paths" +msgstr "" + +#: ../Doc/library/pathlib.rst:10 +msgid "**Source code:** :source:`Lib/pathlib.py`" +msgstr "" + +#: ../Doc/library/pathlib.rst:16 +msgid "" +"This module offers classes representing filesystem paths with semantics " +"appropriate for different operating systems. Path classes are divided " +"between :ref:`pure paths `, which provide purely computational " +"operations without I/O, and :ref:`concrete paths `, which " +"inherit from pure paths but also provide I/O operations." +msgstr "" + +#: ../Doc/library/pathlib.rst:25 +msgid "" +"If you've never used this module before or just aren't sure which class is " +"right for your task, :class:`Path` is most likely what you need. It " +"instantiates a :ref:`concrete path ` for the platform the " +"code is running on." +msgstr "" + +#: ../Doc/library/pathlib.rst:29 +msgid "Pure paths are useful in some special cases; for example:" +msgstr "" + +#: ../Doc/library/pathlib.rst:31 +msgid "" +"If you want to manipulate Windows paths on a Unix machine (or vice versa). " +"You cannot instantiate a :class:`WindowsPath` when running on Unix, but you " +"can instantiate :class:`PureWindowsPath`." +msgstr "" + +#: ../Doc/library/pathlib.rst:34 +msgid "" +"You want to make sure that your code only manipulates paths without actually " +"accessing the OS. In this case, instantiating one of the pure classes may be " +"useful since those simply don't have any OS-accessing operations." +msgstr "" + +#: ../Doc/library/pathlib.rst:39 +msgid ":pep:`428`: The pathlib module -- object-oriented filesystem paths." +msgstr "" + +#: ../Doc/library/pathlib.rst:42 +msgid "" +"For low-level path manipulation on strings, you can also use the :mod:`os." +"path` module." +msgstr "" + +#: ../Doc/library/pathlib.rst:47 +msgid "Basic use" +msgstr "" + +#: ../Doc/library/pathlib.rst:49 +msgid "Importing the main class::" +msgstr "" + +#: ../Doc/library/pathlib.rst:53 +msgid "Listing subdirectories::" +msgstr "" + +#: ../Doc/library/pathlib.rst:60 +msgid "Listing Python source files in this directory tree::" +msgstr "" + +#: ../Doc/library/pathlib.rst:67 +msgid "Navigating inside a directory tree::" +msgstr "" + +#: ../Doc/library/pathlib.rst:76 +msgid "Querying path properties::" +msgstr "" + +#: ../Doc/library/pathlib.rst:83 +msgid "Opening a file::" +msgstr "" + +#: ../Doc/library/pathlib.rst:93 +msgid "Pure paths" +msgstr "" + +#: ../Doc/library/pathlib.rst:95 +msgid "" +"Pure path objects provide path-handling operations which don't actually " +"access a filesystem. There are three ways to access these classes, which we " +"also call *flavours*:" +msgstr "" + +#: ../Doc/library/pathlib.rst:101 +msgid "" +"A generic class that represents the system's path flavour (instantiating it " +"creates either a :class:`PurePosixPath` or a :class:`PureWindowsPath`)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:107 +msgid "" +"Each element of *pathsegments* can be either a string representing a path " +"segment, an object implementing the :class:`os.PathLike` interface which " +"returns a string, or another path object::" +msgstr "" + +#: ../Doc/library/pathlib.rst:116 +msgid "When *pathsegments* is empty, the current directory is assumed::" +msgstr "" + +#: ../Doc/library/pathlib.rst:121 +msgid "" +"When several absolute paths are given, the last is taken as an anchor " +"(mimicking :func:`os.path.join`'s behaviour)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:129 +msgid "" +"However, in a Windows path, changing the local root doesn't discard the " +"previous drive setting::" +msgstr "" + +#: ../Doc/library/pathlib.rst:135 +msgid "" +"Spurious slashes and single dots are collapsed, but double dots (``'..'``) " +"are not, since this would change the meaning of a path in the face of " +"symbolic links::" +msgstr "" + +#: ../Doc/library/pathlib.rst:146 +msgid "" +"(a naïve approach would make ``PurePosixPath('foo/../bar')`` equivalent to " +"``PurePosixPath('bar')``, which is wrong if ``foo`` is a symbolic link to " +"another directory)" +msgstr "" + +#: ../Doc/library/pathlib.rst:150 +msgid "" +"Pure path objects implement the :class:`os.PathLike` interface, allowing " +"them to be used anywhere the interface is accepted." +msgstr "" + +#: ../Doc/library/pathlib.rst:153 +msgid "Added support for the :class:`os.PathLike` interface." +msgstr "" + +#: ../Doc/library/pathlib.rst:158 +msgid "" +"A subclass of :class:`PurePath`, this path flavour represents non-Windows " +"filesystem paths::" +msgstr "" + +#: ../Doc/library/pathlib.rst:164 ../Doc/library/pathlib.rst:174 +#: ../Doc/library/pathlib.rst:587 ../Doc/library/pathlib.rst:597 +#: ../Doc/library/pathlib.rst:607 +msgid "*pathsegments* is specified similarly to :class:`PurePath`." +msgstr "" + +#: ../Doc/library/pathlib.rst:168 +msgid "" +"A subclass of :class:`PurePath`, this path flavour represents Windows " +"filesystem paths::" +msgstr "" + +#: ../Doc/library/pathlib.rst:176 +msgid "" +"Regardless of the system you're running on, you can instantiate all of these " +"classes, since they don't provide any operation that does system calls." +msgstr "" + +#: ../Doc/library/pathlib.rst:181 +msgid "General properties" +msgstr "" + +#: ../Doc/library/pathlib.rst:183 +msgid "" +"Paths are immutable and hashable. Paths of a same flavour are comparable " +"and orderable. These properties respect the flavour's case-folding " +"semantics::" +msgstr "" + +#: ../Doc/library/pathlib.rst:196 +msgid "Paths of a different flavour compare unequal and cannot be ordered::" +msgstr "" + +#: ../Doc/library/pathlib.rst:209 +msgid "" +"The slash operator helps create child paths, similarly to :func:`os.path." +"join`::" +msgstr "" + +#: ../Doc/library/pathlib.rst:220 +msgid "" +"A path object can be used anywhere an object implementing :class:`os." +"PathLike` is accepted::" +msgstr "" + +#: ../Doc/library/pathlib.rst:228 +msgid "" +"The string representation of a path is the raw filesystem path itself (in " +"native form, e.g. with backslashes under Windows), which you can pass to any " +"function taking a file path as a string::" +msgstr "" + +#: ../Doc/library/pathlib.rst:239 +msgid "" +"Similarly, calling :class:`bytes` on a path gives the raw filesystem path as " +"a bytes object, as encoded by :func:`os.fsencode`::" +msgstr "" + +#: ../Doc/library/pathlib.rst:246 +msgid "" +"Calling :class:`bytes` is only recommended under Unix. Under Windows, the " +"unicode form is the canonical representation of filesystem paths." +msgstr "" + +#: ../Doc/library/pathlib.rst:251 +msgid "Accessing individual parts" +msgstr "" + +#: ../Doc/library/pathlib.rst:253 +msgid "" +"To access the individual \"parts\" (components) of a path, use the following " +"property:" +msgstr "" + +#: ../Doc/library/pathlib.rst:258 +msgid "A tuple giving access to the path's various components::" +msgstr "" + +#: ../Doc/library/pathlib.rst:268 +msgid "(note how the drive and local root are regrouped in a single part)" +msgstr "" + +#: ../Doc/library/pathlib.rst:272 +msgid "Methods and properties" +msgstr "" + +#: ../Doc/library/pathlib.rst:274 +msgid "Pure paths provide the following methods and properties:" +msgstr "" + +#: ../Doc/library/pathlib.rst:278 +msgid "A string representing the drive letter or name, if any::" +msgstr "" + +#: ../Doc/library/pathlib.rst:287 +msgid "UNC shares are also considered drives::" +msgstr "" + +#: ../Doc/library/pathlib.rst:294 +msgid "A string representing the (local or global) root, if any::" +msgstr "" + +#: ../Doc/library/pathlib.rst:303 +msgid "UNC shares always have a root::" +msgstr "" + +#: ../Doc/library/pathlib.rst:310 +msgid "The concatenation of the drive and root::" +msgstr "" + +#: ../Doc/library/pathlib.rst:324 +msgid "" +"An immutable sequence providing access to the logical ancestors of the path::" +msgstr "" + +#: ../Doc/library/pathlib.rst:338 +msgid "The logical parent of the path::" +msgstr "" + +#: ../Doc/library/pathlib.rst:344 +msgid "You cannot go past an anchor, or empty path::" +msgstr "" + +#: ../Doc/library/pathlib.rst:354 +msgid "This is a purely lexical operation, hence the following behaviour::" +msgstr "" + +#: ../Doc/library/pathlib.rst:360 +msgid "" +"If you want to walk an arbitrary filesystem path upwards, it is recommended " +"to first call :meth:`Path.resolve` so as to resolve symlinks and eliminate `" +"\"..\"` components." +msgstr "" + +#: ../Doc/library/pathlib.rst:367 +msgid "" +"A string representing the final path component, excluding the drive and " +"root, if any::" +msgstr "" + +#: ../Doc/library/pathlib.rst:373 +msgid "UNC drive names are not considered::" +msgstr "" + +#: ../Doc/library/pathlib.rst:383 +msgid "The file extension of the final component, if any::" +msgstr "" + +#: ../Doc/library/pathlib.rst:395 +msgid "A list of the path's file extensions::" +msgstr "" + +#: ../Doc/library/pathlib.rst:407 +msgid "The final path component, without its suffix::" +msgstr "" + +#: ../Doc/library/pathlib.rst:419 +msgid "" +"Return a string representation of the path with forward slashes (``/``)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:430 +msgid "" +"Represent the path as a ``file`` URI. :exc:`ValueError` is raised if the " +"path isn't absolute." +msgstr "" + +#: ../Doc/library/pathlib.rst:443 +msgid "" +"Return whether the path is absolute or not. A path is considered absolute " +"if it has both a root and (if the flavour allows) a drive::" +msgstr "" + +#: ../Doc/library/pathlib.rst:463 +msgid "" +"With :class:`PureWindowsPath`, return ``True`` if the path is considered " +"reserved under Windows, ``False`` otherwise. With :class:`PurePosixPath`, " +"``False`` is always returned." +msgstr "" + +#: ../Doc/library/pathlib.rst:472 +msgid "" +"File system calls on reserved paths can fail mysteriously or have unintended " +"effects." +msgstr "" + +#: ../Doc/library/pathlib.rst:478 +msgid "" +"Calling this method is equivalent to combining the path with each of the " +"*other* arguments in turn::" +msgstr "" + +#: ../Doc/library/pathlib.rst:493 +msgid "" +"Match this path against the provided glob-style pattern. Return ``True`` if " +"matching is successful, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/pathlib.rst:496 +msgid "" +"If *pattern* is relative, the path can be either relative or absolute, and " +"matching is done from the right::" +msgstr "" + +#: ../Doc/library/pathlib.rst:506 +msgid "" +"If *pattern* is absolute, the path must be absolute, and the whole path must " +"match::" +msgstr "" + +#: ../Doc/library/pathlib.rst:514 +msgid "As with other methods, case-sensitivity is observed::" +msgstr "" + +#: ../Doc/library/pathlib.rst:522 +msgid "" +"Compute a version of this path relative to the path represented by *other*. " +"If it's impossible, ValueError is raised::" +msgstr "" + +#: ../Doc/library/pathlib.rst:540 +msgid "" +"Return a new path with the :attr:`name` changed. If the original path " +"doesn't have a name, ValueError is raised::" +msgstr "" + +#: ../Doc/library/pathlib.rst:557 +msgid "" +"Return a new path with the :attr:`suffix` changed. If the original path " +"doesn't have a suffix, the new *suffix* is appended instead::" +msgstr "" + +#: ../Doc/library/pathlib.rst:572 +msgid "Concrete paths" +msgstr "" + +#: ../Doc/library/pathlib.rst:574 +msgid "" +"Concrete paths are subclasses of the pure path classes. In addition to " +"operations provided by the latter, they also provide methods to do system " +"calls on path objects. There are three ways to instantiate concrete paths:" +msgstr "" + +#: ../Doc/library/pathlib.rst:580 +msgid "" +"A subclass of :class:`PurePath`, this class represents concrete paths of the " +"system's path flavour (instantiating it creates either a :class:`PosixPath` " +"or a :class:`WindowsPath`)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:591 +msgid "" +"A subclass of :class:`Path` and :class:`PurePosixPath`, this class " +"represents concrete non-Windows filesystem paths::" +msgstr "" + +#: ../Doc/library/pathlib.rst:601 +msgid "" +"A subclass of :class:`Path` and :class:`PureWindowsPath`, this class " +"represents concrete Windows filesystem paths::" +msgstr "" + +#: ../Doc/library/pathlib.rst:609 +msgid "" +"You can only instantiate the class flavour that corresponds to your system " +"(allowing system calls on non-compatible path flavours could lead to bugs or " +"failures in your application)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:631 +msgid "" +"Concrete paths provide the following methods in addition to pure paths " +"methods. Many of these methods can raise an :exc:`OSError` if a system call " +"fails (for example because the path doesn't exist):" +msgstr "" + +#: ../Doc/library/pathlib.rst:637 +msgid "" +"Return a new path object representing the current directory (as returned by :" +"func:`os.getcwd`)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:646 +msgid "" +"Return a new path object representing the user's home directory (as returned " +"by :func:`os.path.expanduser` with ``~`` construct)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:657 +msgid "" +"Return information about this path (similarly to :func:`os.stat`). The " +"result is looked up at each call to this method." +msgstr "" + +#: ../Doc/library/pathlib.rst:669 +msgid "Change the file mode and permissions, like :func:`os.chmod`::" +msgstr "" + +#: ../Doc/library/pathlib.rst:681 +msgid "Whether the path points to an existing file or directory::" +msgstr "" + +#: ../Doc/library/pathlib.rst:693 +msgid "" +"If the path points to a symlink, :meth:`exists` returns whether the symlink " +"*points to* an existing file or directory." +msgstr "" + +#: ../Doc/library/pathlib.rst:699 +msgid "" +"Return a new path with expanded ``~`` and ``~user`` constructs, as returned " +"by :meth:`os.path.expanduser`::" +msgstr "" + +#: ../Doc/library/pathlib.rst:711 +msgid "" +"Glob the given *pattern* in the directory represented by this path, yielding " +"all matching files (of any kind)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:719 +msgid "" +"The \"``**``\" pattern means \"this directory and all subdirectories, " +"recursively\". In other words, it enables recursive globbing::" +msgstr "" + +#: ../Doc/library/pathlib.rst:736 +msgid "" +"Return the name of the group owning the file. :exc:`KeyError` is raised if " +"the file's gid isn't found in the system database." +msgstr "" + +#: ../Doc/library/pathlib.rst:742 +msgid "" +"Return ``True`` if the path points to a directory (or a symbolic link " +"pointing to a directory), ``False`` if it points to another kind of file." +msgstr "" + +#: ../Doc/library/pathlib.rst:745 ../Doc/library/pathlib.rst:754 +#: ../Doc/library/pathlib.rst:771 ../Doc/library/pathlib.rst:780 +#: ../Doc/library/pathlib.rst:789 ../Doc/library/pathlib.rst:798 +msgid "" +"``False`` is also returned if the path doesn't exist or is a broken symlink; " +"other errors (such as permission errors) are propagated." +msgstr "" + +#: ../Doc/library/pathlib.rst:751 +msgid "" +"Return ``True`` if the path points to a regular file (or a symbolic link " +"pointing to a regular file), ``False`` if it points to another kind of file." +msgstr "" + +#: ../Doc/library/pathlib.rst:760 +msgid "" +"Return ``True`` if the path points to a symbolic link, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/pathlib.rst:762 +msgid "" +"``False`` is also returned if the path doesn't exist; other errors (such as " +"permission errors) are propagated." +msgstr "" + +#: ../Doc/library/pathlib.rst:768 +msgid "" +"Return ``True`` if the path points to a Unix socket (or a symbolic link " +"pointing to a Unix socket), ``False`` if it points to another kind of file." +msgstr "" + +#: ../Doc/library/pathlib.rst:777 +msgid "" +"Return ``True`` if the path points to a FIFO (or a symbolic link pointing to " +"a FIFO), ``False`` if it points to another kind of file." +msgstr "" + +#: ../Doc/library/pathlib.rst:786 +msgid "" +"Return ``True`` if the path points to a block device (or a symbolic link " +"pointing to a block device), ``False`` if it points to another kind of file." +msgstr "" + +#: ../Doc/library/pathlib.rst:795 +msgid "" +"Return ``True`` if the path points to a character device (or a symbolic link " +"pointing to a character device), ``False`` if it points to another kind of " +"file." +msgstr "" + +#: ../Doc/library/pathlib.rst:804 +msgid "" +"When the path points to a directory, yield path objects of the directory " +"contents::" +msgstr "" + +#: ../Doc/library/pathlib.rst:820 +msgid "" +"Like :meth:`Path.chmod` but, if the path points to a symbolic link, the " +"symbolic link's mode is changed rather than its target's." +msgstr "" + +#: ../Doc/library/pathlib.rst:826 +msgid "" +"Like :meth:`Path.stat` but, if the path points to a symbolic link, return " +"the symbolic link's information rather than its target's." +msgstr "" + +#: ../Doc/library/pathlib.rst:832 +msgid "" +"Create a new directory at this given path. If *mode* is given, it is " +"combined with the process' ``umask`` value to determine the file mode and " +"access flags. If the path already exists, :exc:`FileExistsError` is raised." +msgstr "" + +#: ../Doc/library/pathlib.rst:837 +msgid "" +"If *parents* is true, any missing parents of this path are created as " +"needed; they are created with the default permissions without taking *mode* " +"into account (mimicking the POSIX ``mkdir -p`` command)." +msgstr "" + +#: ../Doc/library/pathlib.rst:841 +msgid "" +"If *parents* is false (the default), a missing parent raises :exc:" +"`FileNotFoundError`." +msgstr "" + +#: ../Doc/library/pathlib.rst:844 +msgid "" +"If *exist_ok* is false (the default), :exc:`FileExistsError` is raised if " +"the target directory already exists." +msgstr "" + +#: ../Doc/library/pathlib.rst:847 +msgid "" +"If *exist_ok* is true, :exc:`FileExistsError` exceptions will be ignored " +"(same behavior as the POSIX ``mkdir -p`` command), but only if the last path " +"component is not an existing non-directory file." +msgstr "" + +#: ../Doc/library/pathlib.rst:851 +msgid "The *exist_ok* parameter was added." +msgstr "" + +#: ../Doc/library/pathlib.rst:857 +msgid "" +"Open the file pointed to by the path, like the built-in :func:`open` " +"function does::" +msgstr "" + +#: ../Doc/library/pathlib.rst:869 +msgid "" +"Return the name of the user owning the file. :exc:`KeyError` is raised if " +"the file's uid isn't found in the system database." +msgstr "" + +#: ../Doc/library/pathlib.rst:875 +msgid "Return the binary contents of the pointed-to file as a bytes object::" +msgstr "" + +#: ../Doc/library/pathlib.rst:888 +msgid "Return the decoded contents of the pointed-to file as a string::" +msgstr "" + +#: ../Doc/library/pathlib.rst:896 +msgid "The optional parameters have the same meaning as in :func:`open`." +msgstr "" + +#: ../Doc/library/pathlib.rst:903 +msgid "" +"Rename this file or directory to the given *target*. On Unix, if *target* " +"exists and is a file, it will be replaced silently if the user has " +"permission. *target* can be either a string or another path object::" +msgstr "" + +#: ../Doc/library/pathlib.rst:918 +msgid "" +"Rename this file or directory to the given *target*. If *target* points to " +"an existing file or directory, it will be unconditionally replaced." +msgstr "" + +#: ../Doc/library/pathlib.rst:924 +msgid "" +"Make the path absolute, resolving any symlinks. A new path object is " +"returned::" +msgstr "" + +#: ../Doc/library/pathlib.rst:933 +msgid "" +"\"``..``\" components are also eliminated (this is the only method to do " +"so)::" +msgstr "" + +#: ../Doc/library/pathlib.rst:939 +msgid "" +"If the path doesn't exist, :exc:`FileNotFoundError` is raised. If an " +"infinite loop is encountered along the resolution path, :exc:`RuntimeError` " +"is raised." +msgstr "" + +#: ../Doc/library/pathlib.rst:946 +msgid "" +"This is like calling :meth:`Path.glob` with \"``**``\" added in front of the " +"given *pattern*:" +msgstr "" + +#: ../Doc/library/pathlib.rst:959 +msgid "Remove this directory. The directory must be empty." +msgstr "" + +#: ../Doc/library/pathlib.rst:964 +msgid "" +"Return whether this path points to the same file as *other_path*, which can " +"be either a Path object, or a string. The semantics are similar to :func:" +"`os.path.samefile` and :func:`os.path.samestat`." +msgstr "" + +#: ../Doc/library/pathlib.rst:968 +msgid "" +"An :exc:`OSError` can be raised if either file cannot be accessed for some " +"reason." +msgstr "" + +#: ../Doc/library/pathlib.rst:983 +msgid "" +"Make this path a symbolic link to *target*. Under Windows, " +"*target_is_directory* must be true (default ``False``) if the link's target " +"is a directory. Under POSIX, *target_is_directory*'s value is ignored." +msgstr "" + +#: ../Doc/library/pathlib.rst:997 +msgid "" +"The order of arguments (link, target) is the reverse of :func:`os.symlink`'s." +msgstr "" + +#: ../Doc/library/pathlib.rst:1003 +msgid "" +"Create a file at this given path. If *mode* is given, it is combined with " +"the process' ``umask`` value to determine the file mode and access flags. " +"If the file already exists, the function succeeds if *exist_ok* is true (and " +"its modification time is updated to the current time), otherwise :exc:" +"`FileExistsError` is raised." +msgstr "" + +#: ../Doc/library/pathlib.rst:1012 +msgid "" +"Remove this file or symbolic link. If the path points to a directory, use :" +"func:`Path.rmdir` instead." +msgstr "" + +#: ../Doc/library/pathlib.rst:1018 +msgid "" +"Open the file pointed to in bytes mode, write *data* to it, and close the " +"file::" +msgstr "" + +#: ../Doc/library/pathlib.rst:1027 +msgid "An existing file of the same name is overwritten." +msgstr "" + +#: ../Doc/library/pathlib.rst:1034 +msgid "" +"Open the file pointed to in text mode, write *data* to it, and close the " +"file::" +msgstr "" + +#: ../Doc/library/pdb.rst:4 +msgid ":mod:`pdb` --- The Python Debugger" +msgstr "" + +#: ../Doc/library/pdb.rst:9 +msgid "**Source code:** :source:`Lib/pdb.py`" +msgstr "" + +#: ../Doc/library/pdb.rst:15 +msgid "" +"The module :mod:`pdb` defines an interactive source code debugger for Python " +"programs. It supports setting (conditional) breakpoints and single stepping " +"at the source line level, inspection of stack frames, source code listing, " +"and evaluation of arbitrary Python code in the context of any stack frame. " +"It also supports post-mortem debugging and can be called under program " +"control." +msgstr "" + +#: ../Doc/library/pdb.rst:26 +msgid "" +"The debugger is extensible -- it is actually defined as the class :class:" +"`Pdb`. This is currently undocumented but easily understood by reading the " +"source. The extension interface uses the modules :mod:`bdb` and :mod:`cmd`." +msgstr "" + +#: ../Doc/library/pdb.rst:30 +msgid "" +"The debugger's prompt is ``(Pdb)``. Typical usage to run a program under " +"control of the debugger is::" +msgstr "" + +#: ../Doc/library/pdb.rst:44 +msgid "" +"Tab-completion via the :mod:`readline` module is available for commands and " +"command arguments, e.g. the current global and local names are offered as " +"arguments of the ``p`` command." +msgstr "" + +#: ../Doc/library/pdb.rst:49 +msgid "" +":file:`pdb.py` can also be invoked as a script to debug other scripts. For " +"example::" +msgstr "" + +#: ../Doc/library/pdb.rst:54 +msgid "" +"When invoked as a script, pdb will automatically enter post-mortem debugging " +"if the program being debugged exits abnormally. After post-mortem debugging " +"(or after normal exit of the program), pdb will restart the program. " +"Automatic restarting preserves pdb's state (such as breakpoints) and in most " +"cases is more useful than quitting the debugger upon program's exit." +msgstr "" + +#: ../Doc/library/pdb.rst:60 +msgid "" +":file:`pdb.py` now accepts a ``-c`` option that executes commands as if " +"given in a :file:`.pdbrc` file, see :ref:`debugger-commands`." +msgstr "" + +#: ../Doc/library/pdb.rst:64 +msgid "" +"The typical usage to break into the debugger from a running program is to " +"insert ::" +msgstr "" + +#: ../Doc/library/pdb.rst:69 +msgid "" +"at the location you want to break into the debugger. You can then step " +"through the code following this statement, and continue running without the " +"debugger using the :pdbcmd:`continue` command." +msgstr "" + +#: ../Doc/library/pdb.rst:73 +msgid "The typical usage to inspect a crashed program is::" +msgstr "" + +#: ../Doc/library/pdb.rst:91 +msgid "" +"The module defines the following functions; each enters the debugger in a " +"slightly different way:" +msgstr "" + +#: ../Doc/library/pdb.rst:96 +msgid "" +"Execute the *statement* (given as a string or a code object) under debugger " +"control. The debugger prompt appears before any code is executed; you can " +"set breakpoints and type :pdbcmd:`continue`, or you can step through the " +"statement using :pdbcmd:`step` or :pdbcmd:`next` (all these commands are " +"explained below). The optional *globals* and *locals* arguments specify the " +"environment in which the code is executed; by default the dictionary of the " +"module :mod:`__main__` is used. (See the explanation of the built-in :func:" +"`exec` or :func:`eval` functions.)" +msgstr "" + +#: ../Doc/library/pdb.rst:108 +msgid "" +"Evaluate the *expression* (given as a string or a code object) under " +"debugger control. When :func:`runeval` returns, it returns the value of the " +"expression. Otherwise this function is similar to :func:`run`." +msgstr "" + +#: ../Doc/library/pdb.rst:115 +msgid "" +"Call the *function* (a function or method object, not a string) with the " +"given arguments. When :func:`runcall` returns, it returns whatever the " +"function call returned. The debugger prompt appears as soon as the function " +"is entered." +msgstr "" + +#: ../Doc/library/pdb.rst:123 +msgid "" +"Enter the debugger at the calling stack frame. This is useful to hard-code " +"a breakpoint at a given point in a program, even if the code is not " +"otherwise being debugged (e.g. when an assertion fails)." +msgstr "" + +#: ../Doc/library/pdb.rst:130 +msgid "" +"Enter post-mortem debugging of the given *traceback* object. If no " +"*traceback* is given, it uses the one of the exception that is currently " +"being handled (an exception must be being handled if the default is to be " +"used)." +msgstr "" + +#: ../Doc/library/pdb.rst:138 +msgid "" +"Enter post-mortem debugging of the traceback found in :data:`sys." +"last_traceback`." +msgstr "" + +#: ../Doc/library/pdb.rst:142 +msgid "" +"The ``run*`` functions and :func:`set_trace` are aliases for instantiating " +"the :class:`Pdb` class and calling the method of the same name. If you want " +"to access further features, you have to do this yourself:" +msgstr "" + +#: ../Doc/library/pdb.rst:149 +msgid ":class:`Pdb` is the debugger class." +msgstr "" + +#: ../Doc/library/pdb.rst:151 +msgid "" +"The *completekey*, *stdin* and *stdout* arguments are passed to the " +"underlying :class:`cmd.Cmd` class; see the description there." +msgstr "" + +#: ../Doc/library/pdb.rst:154 +msgid "" +"The *skip* argument, if given, must be an iterable of glob-style module name " +"patterns. The debugger will not step into frames that originate in a module " +"that matches one of these patterns. [1]_" +msgstr "" + +#: ../Doc/library/pdb.rst:158 +msgid "" +"By default, Pdb sets a handler for the SIGINT signal (which is sent when the " +"user presses :kbd:`Ctrl-C` on the console) when you give a ``continue`` " +"command. This allows you to break into the debugger again by pressing :kbd:" +"`Ctrl-C`. If you want Pdb not to touch the SIGINT handler, set *nosigint* " +"to true." +msgstr "" + +#: ../Doc/library/pdb.rst:163 +msgid "" +"The *readrc* argument defaults to true and controls whether Pdb will load ." +"pdbrc files from the filesystem." +msgstr "" + +#: ../Doc/library/pdb.rst:166 +msgid "Example call to enable tracing with *skip*::" +msgstr "" + +#: ../Doc/library/pdb.rst:173 +msgid "" +"The *nosigint* argument. Previously, a SIGINT handler was never set by Pdb." +msgstr "" + +#: ../Doc/library/pdb.rst:177 +msgid "The *readrc* argument." +msgstr "" + +#: ../Doc/library/pdb.rst:185 +msgid "See the documentation for the functions explained above." +msgstr "" + +#: ../Doc/library/pdb.rst:191 +msgid "Debugger Commands" +msgstr "" + +#: ../Doc/library/pdb.rst:193 +msgid "" +"The commands recognized by the debugger are listed below. Most commands can " +"be abbreviated to one or two letters as indicated; e.g. ``h(elp)`` means " +"that either ``h`` or ``help`` can be used to enter the help command (but not " +"``he`` or ``hel``, nor ``H`` or ``Help`` or ``HELP``). Arguments to " +"commands must be separated by whitespace (spaces or tabs). Optional " +"arguments are enclosed in square brackets (``[]``) in the command syntax; " +"the square brackets must not be typed. Alternatives in the command syntax " +"are separated by a vertical bar (``|``)." +msgstr "" + +#: ../Doc/library/pdb.rst:202 +msgid "" +"Entering a blank line repeats the last command entered. Exception: if the " +"last command was a :pdbcmd:`list` command, the next 11 lines are listed." +msgstr "" + +#: ../Doc/library/pdb.rst:205 +msgid "" +"Commands that the debugger doesn't recognize are assumed to be Python " +"statements and are executed in the context of the program being debugged. " +"Python statements can also be prefixed with an exclamation point (``!``). " +"This is a powerful way to inspect the program being debugged; it is even " +"possible to change a variable or call a function. When an exception occurs " +"in such a statement, the exception name is printed but the debugger's state " +"is not changed." +msgstr "" + +#: ../Doc/library/pdb.rst:213 +msgid "" +"The debugger supports :ref:`aliases `. Aliases can have " +"parameters which allows one a certain level of adaptability to the context " +"under examination." +msgstr "" + +#: ../Doc/library/pdb.rst:217 +msgid "" +"Multiple commands may be entered on a single line, separated by ``;;``. (A " +"single ``;`` is not used as it is the separator for multiple commands in a " +"line that is passed to the Python parser.) No intelligence is applied to " +"separating the commands; the input is split at the first ``;;`` pair, even " +"if it is in the middle of a quoted string." +msgstr "" + +#: ../Doc/library/pdb.rst:227 +msgid "" +"If a file :file:`.pdbrc` exists in the user's home directory or in the " +"current directory, it is read in and executed as if it had been typed at the " +"debugger prompt. This is particularly useful for aliases. If both files " +"exist, the one in the home directory is read first and aliases defined there " +"can be overridden by the local file." +msgstr "" + +#: ../Doc/library/pdb.rst:233 +msgid "" +":file:`.pdbrc` can now contain commands that continue debugging, such as :" +"pdbcmd:`continue` or :pdbcmd:`next`. Previously, these commands had no " +"effect." +msgstr "" + +#: ../Doc/library/pdb.rst:241 +msgid "" +"Without argument, print the list of available commands. With a *command* as " +"argument, print help about that command. ``help pdb`` displays the full " +"documentation (the docstring of the :mod:`pdb` module). Since the *command* " +"argument must be an identifier, ``help exec`` must be entered to get help on " +"the ``!`` command." +msgstr "" + +#: ../Doc/library/pdb.rst:249 +msgid "" +"Print a stack trace, with the most recent frame at the bottom. An arrow " +"indicates the current frame, which determines the context of most commands." +msgstr "" + +#: ../Doc/library/pdb.rst:254 +msgid "" +"Move the current frame *count* (default one) levels down in the stack trace " +"(to a newer frame)." +msgstr "" + +#: ../Doc/library/pdb.rst:259 +msgid "" +"Move the current frame *count* (default one) levels up in the stack trace " +"(to an older frame)." +msgstr "" + +#: ../Doc/library/pdb.rst:264 +msgid "" +"With a *lineno* argument, set a break there in the current file. With a " +"*function* argument, set a break at the first executable statement within " +"that function. The line number may be prefixed with a filename and a colon, " +"to specify a breakpoint in another file (probably one that hasn't been " +"loaded yet). The file is searched on :data:`sys.path`. Note that each " +"breakpoint is assigned a number to which all the other breakpoint commands " +"refer." +msgstr "" + +#: ../Doc/library/pdb.rst:271 +msgid "" +"If a second argument is present, it is an expression which must evaluate to " +"true before the breakpoint is honored." +msgstr "" + +#: ../Doc/library/pdb.rst:274 +msgid "" +"Without argument, list all breaks, including for each breakpoint, the number " +"of times that breakpoint has been hit, the current ignore count, and the " +"associated condition if any." +msgstr "" + +#: ../Doc/library/pdb.rst:280 +msgid "" +"Temporary breakpoint, which is removed automatically when it is first hit. " +"The arguments are the same as for :pdbcmd:`break`." +msgstr "" + +#: ../Doc/library/pdb.rst:285 +msgid "" +"With a *filename:lineno* argument, clear all the breakpoints at this line. " +"With a space separated list of breakpoint numbers, clear those breakpoints. " +"Without argument, clear all breaks (but first ask confirmation)." +msgstr "" + +#: ../Doc/library/pdb.rst:291 +msgid "" +"Disable the breakpoints given as a space separated list of breakpoint " +"numbers. Disabling a breakpoint means it cannot cause the program to stop " +"execution, but unlike clearing a breakpoint, it remains in the list of " +"breakpoints and can be (re-)enabled." +msgstr "" + +#: ../Doc/library/pdb.rst:298 +msgid "Enable the breakpoints specified." +msgstr "" + +#: ../Doc/library/pdb.rst:302 +msgid "" +"Set the ignore count for the given breakpoint number. If count is omitted, " +"the ignore count is set to 0. A breakpoint becomes active when the ignore " +"count is zero. When non-zero, the count is decremented each time the " +"breakpoint is reached and the breakpoint is not disabled and any associated " +"condition evaluates to true." +msgstr "" + +#: ../Doc/library/pdb.rst:310 +msgid "" +"Set a new *condition* for the breakpoint, an expression which must evaluate " +"to true before the breakpoint is honored. If *condition* is absent, any " +"existing condition is removed; i.e., the breakpoint is made unconditional." +msgstr "" + +#: ../Doc/library/pdb.rst:316 +msgid "" +"Specify a list of commands for breakpoint number *bpnumber*. The commands " +"themselves appear on the following lines. Type a line containing just " +"``end`` to terminate the commands. An example::" +msgstr "" + +#: ../Doc/library/pdb.rst:325 +msgid "" +"To remove all commands from a breakpoint, type commands and follow it " +"immediately with ``end``; that is, give no commands." +msgstr "" + +#: ../Doc/library/pdb.rst:328 +msgid "" +"With no *bpnumber* argument, commands refers to the last breakpoint set." +msgstr "" + +#: ../Doc/library/pdb.rst:330 +msgid "" +"You can use breakpoint commands to start your program up again. Simply use " +"the continue command, or step, or any other command that resumes execution." +msgstr "" + +#: ../Doc/library/pdb.rst:333 +msgid "" +"Specifying any command resuming execution (currently continue, step, next, " +"return, jump, quit and their abbreviations) terminates the command list (as " +"if that command was immediately followed by end). This is because any time " +"you resume execution (even with a simple next or step), you may encounter " +"another breakpoint--which could have its own command list, leading to " +"ambiguities about which list to execute." +msgstr "" + +#: ../Doc/library/pdb.rst:340 +msgid "" +"If you use the 'silent' command in the command list, the usual message about " +"stopping at a breakpoint is not printed. This may be desirable for " +"breakpoints that are to print a specific message and then continue. If none " +"of the other commands print anything, you see no sign that the breakpoint " +"was reached." +msgstr "" + +#: ../Doc/library/pdb.rst:347 +msgid "" +"Execute the current line, stop at the first possible occasion (either in a " +"function that is called or on the next line in the current function)." +msgstr "" + +#: ../Doc/library/pdb.rst:352 +msgid "" +"Continue execution until the next line in the current function is reached or " +"it returns. (The difference between :pdbcmd:`next` and :pdbcmd:`step` is " +"that :pdbcmd:`step` stops inside a called function, while :pdbcmd:`next` " +"executes called functions at (nearly) full speed, only stopping at the next " +"line in the current function.)" +msgstr "" + +#: ../Doc/library/pdb.rst:360 +msgid "" +"Without argument, continue execution until the line with a number greater " +"than the current one is reached." +msgstr "" + +#: ../Doc/library/pdb.rst:363 +msgid "" +"With a line number, continue execution until a line with a number greater or " +"equal to that is reached. In both cases, also stop when the current frame " +"returns." +msgstr "" + +#: ../Doc/library/pdb.rst:367 +msgid "Allow giving an explicit line number." +msgstr "" + +#: ../Doc/library/pdb.rst:372 +msgid "Continue execution until the current function returns." +msgstr "" + +#: ../Doc/library/pdb.rst:376 +msgid "Continue execution, only stop when a breakpoint is encountered." +msgstr "" + +#: ../Doc/library/pdb.rst:380 +msgid "" +"Set the next line that will be executed. Only available in the bottom-most " +"frame. This lets you jump back and execute code again, or jump forward to " +"skip code that you don't want to run." +msgstr "" + +#: ../Doc/library/pdb.rst:384 +msgid "" +"It should be noted that not all jumps are allowed -- for instance it is not " +"possible to jump into the middle of a :keyword:`for` loop or out of a :" +"keyword:`finally` clause." +msgstr "" + +#: ../Doc/library/pdb.rst:390 +msgid "" +"List source code for the current file. Without arguments, list 11 lines " +"around the current line or continue the previous listing. With ``.`` as " +"argument, list 11 lines around the current line. With one argument, list 11 " +"lines around at that line. With two arguments, list the given range; if the " +"second argument is less than the first, it is interpreted as a count." +msgstr "" + +#: ../Doc/library/pdb.rst:396 +msgid "" +"The current line in the current frame is indicated by ``->``. If an " +"exception is being debugged, the line where the exception was originally " +"raised or propagated is indicated by ``>>``, if it differs from the current " +"line." +msgstr "" + +#: ../Doc/library/pdb.rst:401 +msgid "The ``>>`` marker." +msgstr "" + +#: ../Doc/library/pdb.rst:406 +msgid "" +"List all source code for the current function or frame. Interesting lines " +"are marked as for :pdbcmd:`list`." +msgstr "" + +#: ../Doc/library/pdb.rst:413 +msgid "Print the argument list of the current function." +msgstr "" + +#: ../Doc/library/pdb.rst:417 +msgid "Evaluate the *expression* in the current context and print its value." +msgstr "" + +#: ../Doc/library/pdb.rst:421 +msgid "" +"``print()`` can also be used, but is not a debugger command --- this " +"executes the Python :func:`print` function." +msgstr "" + +#: ../Doc/library/pdb.rst:427 +msgid "" +"Like the :pdbcmd:`p` command, except the value of the expression is pretty-" +"printed using the :mod:`pprint` module." +msgstr "" + +#: ../Doc/library/pdb.rst:432 +msgid "Print the type of the *expression*." +msgstr "" + +#: ../Doc/library/pdb.rst:436 +msgid "Try to get source code for the given object and display it." +msgstr "" + +#: ../Doc/library/pdb.rst:442 +msgid "" +"Display the value of the expression if it changed, each time execution stops " +"in the current frame." +msgstr "" + +#: ../Doc/library/pdb.rst:445 +msgid "Without expression, list all display expressions for the current frame." +msgstr "" + +#: ../Doc/library/pdb.rst:451 +msgid "" +"Do not display the expression any more in the current frame. Without " +"expression, clear all display expressions for the current frame." +msgstr "" + +#: ../Doc/library/pdb.rst:458 +msgid "" +"Start an interactive interpreter (using the :mod:`code` module) whose global " +"namespace contains all the (global and local) names found in the current " +"scope." +msgstr "" + +#: ../Doc/library/pdb.rst:468 +msgid "" +"Create an alias called *name* that executes *command*. The command must " +"*not* be enclosed in quotes. Replaceable parameters can be indicated by ``" +"%1``, ``%2``, and so on, while ``%*`` is replaced by all the parameters. If " +"no command is given, the current alias for *name* is shown. If no arguments " +"are given, all aliases are listed." +msgstr "" + +#: ../Doc/library/pdb.rst:474 +msgid "" +"Aliases may be nested and can contain anything that can be legally typed at " +"the pdb prompt. Note that internal pdb commands *can* be overridden by " +"aliases. Such a command is then hidden until the alias is removed. " +"Aliasing is recursively applied to the first word of the command line; all " +"other words in the line are left alone." +msgstr "" + +#: ../Doc/library/pdb.rst:480 +msgid "" +"As an example, here are two useful aliases (especially when placed in the :" +"file:`.pdbrc` file)::" +msgstr "" + +#: ../Doc/library/pdb.rst:490 +msgid "Delete the specified alias." +msgstr "" + +#: ../Doc/library/pdb.rst:494 +msgid "" +"Execute the (one-line) *statement* in the context of the current stack " +"frame. The exclamation point can be omitted unless the first word of the " +"statement resembles a debugger command. To set a global variable, you can " +"prefix the assignment command with a :keyword:`global` statement on the same " +"line, e.g.::" +msgstr "" + +#: ../Doc/library/pdb.rst:506 +msgid "" +"Restart the debugged Python program. If an argument is supplied, it is " +"split with :mod:`shlex` and the result is used as the new :data:`sys.argv`. " +"History, breakpoints, actions and debugger options are preserved. :pdbcmd:" +"`restart` is an alias for :pdbcmd:`run`." +msgstr "" + +#: ../Doc/library/pdb.rst:513 +msgid "Quit from the debugger. The program being executed is aborted." +msgstr "" + +#: ../Doc/library/pdb.rst:518 +msgid "" +"Whether a frame is considered to originate in a certain module is determined " +"by the ``__name__`` in the frame globals." +msgstr "" + +#: ../Doc/library/persistence.rst:5 +msgid "Data Persistence" +msgstr "" + +#: ../Doc/library/persistence.rst:7 +msgid "" +"The modules described in this chapter support storing Python data in a " +"persistent form on disk. The :mod:`pickle` and :mod:`marshal` modules can " +"turn many Python data types into a stream of bytes and then recreate the " +"objects from the bytes. The various DBM-related modules support a family of " +"hash-based file formats that store a mapping of strings to other strings." +msgstr "" + +#: ../Doc/library/pickle.rst:2 +msgid ":mod:`pickle` --- Python object serialization" +msgstr "" + +#: ../Doc/library/pickle.rst:10 +msgid "**Source code:** :source:`Lib/pickle.py`" +msgstr "" + +#: ../Doc/library/pickle.rst:22 +msgid "" +"The :mod:`pickle` module implements binary protocols for serializing and de-" +"serializing a Python object structure. *\"Pickling\"* is the process " +"whereby a Python object hierarchy is converted into a byte stream, and *" +"\"unpickling\"* is the inverse operation, whereby a byte stream (from a :" +"term:`binary file` or :term:`bytes-like object`) is converted back into an " +"object hierarchy. Pickling (and unpickling) is alternatively known as " +"\"serialization\", \"marshalling,\" [#]_ or \"flattening\"; however, to " +"avoid confusion, the terms used here are \"pickling\" and \"unpickling\"." +msgstr "" + +#: ../Doc/library/pickle.rst:33 +msgid "" +"The :mod:`pickle` module is not secure against erroneous or maliciously " +"constructed data. Never unpickle data received from an untrusted or " +"unauthenticated source." +msgstr "" + +#: ../Doc/library/pickle.rst:39 +msgid "Relationship to other Python modules" +msgstr "" + +#: ../Doc/library/pickle.rst:42 +msgid "Comparison with ``marshal``" +msgstr "" + +#: ../Doc/library/pickle.rst:44 +msgid "" +"Python has a more primitive serialization module called :mod:`marshal`, but " +"in general :mod:`pickle` should always be the preferred way to serialize " +"Python objects. :mod:`marshal` exists primarily to support Python's :file:`." +"pyc` files." +msgstr "" + +#: ../Doc/library/pickle.rst:49 +msgid "" +"The :mod:`pickle` module differs from :mod:`marshal` in several significant " +"ways:" +msgstr "" + +#: ../Doc/library/pickle.rst:51 +msgid "" +"The :mod:`pickle` module keeps track of the objects it has already " +"serialized, so that later references to the same object won't be serialized " +"again. :mod:`marshal` doesn't do this." +msgstr "" + +#: ../Doc/library/pickle.rst:55 +msgid "" +"This has implications both for recursive objects and object sharing. " +"Recursive objects are objects that contain references to themselves. These " +"are not handled by marshal, and in fact, attempting to marshal recursive " +"objects will crash your Python interpreter. Object sharing happens when " +"there are multiple references to the same object in different places in the " +"object hierarchy being serialized. :mod:`pickle` stores such objects only " +"once, and ensures that all other references point to the master copy. " +"Shared objects remain shared, which can be very important for mutable " +"objects." +msgstr "" + +#: ../Doc/library/pickle.rst:64 +msgid "" +":mod:`marshal` cannot be used to serialize user-defined classes and their " +"instances. :mod:`pickle` can save and restore class instances " +"transparently, however the class definition must be importable and live in " +"the same module as when the object was stored." +msgstr "" + +#: ../Doc/library/pickle.rst:69 +msgid "" +"The :mod:`marshal` serialization format is not guaranteed to be portable " +"across Python versions. Because its primary job in life is to support :file:" +"`.pyc` files, the Python implementers reserve the right to change the " +"serialization format in non-backwards compatible ways should the need arise. " +"The :mod:`pickle` serialization format is guaranteed to be backwards " +"compatible across Python releases." +msgstr "" + +#: ../Doc/library/pickle.rst:77 +msgid "Comparison with ``json``" +msgstr "" + +#: ../Doc/library/pickle.rst:79 +msgid "" +"There are fundamental differences between the pickle protocols and `JSON " +"(JavaScript Object Notation) `_:" +msgstr "" + +#: ../Doc/library/pickle.rst:82 +msgid "" +"JSON is a text serialization format (it outputs unicode text, although most " +"of the time it is then encoded to ``utf-8``), while pickle is a binary " +"serialization format;" +msgstr "" + +#: ../Doc/library/pickle.rst:86 +msgid "JSON is human-readable, while pickle is not;" +msgstr "" + +#: ../Doc/library/pickle.rst:88 +msgid "" +"JSON is interoperable and widely used outside of the Python ecosystem, while " +"pickle is Python-specific;" +msgstr "" + +#: ../Doc/library/pickle.rst:91 +msgid "" +"JSON, by default, can only represent a subset of the Python built-in types, " +"and no custom classes; pickle can represent an extremely large number of " +"Python types (many of them automatically, by clever usage of Python's " +"introspection facilities; complex cases can be tackled by implementing :ref:" +"`specific object APIs `)." +msgstr "" + +#: ../Doc/library/pickle.rst:98 +msgid "" +"The :mod:`json` module: a standard library module allowing JSON " +"serialization and deserialization." +msgstr "" + +#: ../Doc/library/pickle.rst:105 +msgid "Data stream format" +msgstr "" + +#: ../Doc/library/pickle.rst:110 +msgid "" +"The data format used by :mod:`pickle` is Python-specific. This has the " +"advantage that there are no restrictions imposed by external standards such " +"as JSON or XDR (which can't represent pointer sharing); however it means " +"that non-Python programs may not be able to reconstruct pickled Python " +"objects." +msgstr "" + +#: ../Doc/library/pickle.rst:115 +msgid "" +"By default, the :mod:`pickle` data format uses a relatively compact binary " +"representation. If you need optimal size characteristics, you can " +"efficiently :doc:`compress ` pickled data." +msgstr "" + +#: ../Doc/library/pickle.rst:119 +msgid "" +"The module :mod:`pickletools` contains tools for analyzing data streams " +"generated by :mod:`pickle`. :mod:`pickletools` source code has extensive " +"comments about opcodes used by pickle protocols." +msgstr "" + +#: ../Doc/library/pickle.rst:123 +msgid "" +"There are currently 5 different protocols which can be used for pickling. " +"The higher the protocol used, the more recent the version of Python needed " +"to read the pickle produced." +msgstr "" + +#: ../Doc/library/pickle.rst:127 +msgid "" +"Protocol version 0 is the original \"human-readable\" protocol and is " +"backwards compatible with earlier versions of Python." +msgstr "" + +#: ../Doc/library/pickle.rst:130 +msgid "" +"Protocol version 1 is an old binary format which is also compatible with " +"earlier versions of Python." +msgstr "" + +#: ../Doc/library/pickle.rst:133 +msgid "" +"Protocol version 2 was introduced in Python 2.3. It provides much more " +"efficient pickling of :term:`new-style class`\\es. Refer to :pep:`307` for " +"information about improvements brought by protocol 2." +msgstr "" + +#: ../Doc/library/pickle.rst:137 +msgid "" +"Protocol version 3 was added in Python 3.0. It has explicit support for :" +"class:`bytes` objects and cannot be unpickled by Python 2.x. This is the " +"default protocol, and the recommended protocol when compatibility with other " +"Python 3 versions is required." +msgstr "" + +#: ../Doc/library/pickle.rst:142 +msgid "" +"Protocol version 4 was added in Python 3.4. It adds support for very large " +"objects, pickling more kinds of objects, and some data format " +"optimizations. Refer to :pep:`3154` for information about improvements " +"brought by protocol 4." +msgstr "" + +#: ../Doc/library/pickle.rst:148 +msgid "" +"Serialization is a more primitive notion than persistence; although :mod:" +"`pickle` reads and writes file objects, it does not handle the issue of " +"naming persistent objects, nor the (even more complicated) issue of " +"concurrent access to persistent objects. The :mod:`pickle` module can " +"transform a complex object into a byte stream and it can transform the byte " +"stream into an object with the same internal structure. Perhaps the most " +"obvious thing to do with these byte streams is to write them onto a file, " +"but it is also conceivable to send them across a network or store them in a " +"database. The :mod:`shelve` module provides a simple interface to pickle " +"and unpickle objects on DBM-style database files." +msgstr "" + +#: ../Doc/library/pickle.rst:161 +msgid "Module Interface" +msgstr "" + +#: ../Doc/library/pickle.rst:163 +msgid "" +"To serialize an object hierarchy, you simply call the :func:`dumps` " +"function. Similarly, to de-serialize a data stream, you call the :func:" +"`loads` function. However, if you want more control over serialization and " +"de-serialization, you can create a :class:`Pickler` or an :class:`Unpickler` " +"object, respectively." +msgstr "" + +#: ../Doc/library/pickle.rst:168 +msgid "The :mod:`pickle` module provides the following constants:" +msgstr "" + +#: ../Doc/library/pickle.rst:173 +msgid "" +"An integer, the highest :ref:`protocol version ` " +"available. This value can be passed as a *protocol* value to functions :" +"func:`dump` and :func:`dumps` as well as the :class:`Pickler` constructor." +msgstr "" + +#: ../Doc/library/pickle.rst:180 +msgid "" +"An integer, the default :ref:`protocol version ` used for " +"pickling. May be less than :data:`HIGHEST_PROTOCOL`. Currently the default " +"protocol is 3, a new protocol designed for Python 3." +msgstr "" + +#: ../Doc/library/pickle.rst:185 +msgid "" +"The :mod:`pickle` module provides the following functions to make the " +"pickling process more convenient:" +msgstr "" + +#: ../Doc/library/pickle.rst:190 +msgid "" +"Write a pickled representation of *obj* to the open :term:`file object` " +"*file*. This is equivalent to ``Pickler(file, protocol).dump(obj)``." +msgstr "" + +#: ../Doc/library/pickle.rst:193 ../Doc/library/pickle.rst:289 +msgid "" +"The optional *protocol* argument, an integer, tells the pickler to use the " +"given protocol; supported protocols are 0 to :data:`HIGHEST_PROTOCOL`. If " +"not specified, the default is :data:`DEFAULT_PROTOCOL`. If a negative " +"number is specified, :data:`HIGHEST_PROTOCOL` is selected." +msgstr "" + +#: ../Doc/library/pickle.rst:198 ../Doc/library/pickle.rst:294 +msgid "" +"The *file* argument must have a write() method that accepts a single bytes " +"argument. It can thus be an on-disk file opened for binary writing, an :" +"class:`io.BytesIO` instance, or any other custom object that meets this " +"interface." +msgstr "" + +#: ../Doc/library/pickle.rst:203 ../Doc/library/pickle.rst:299 +msgid "" +"If *fix_imports* is true and *protocol* is less than 3, pickle will try to " +"map the new Python 3 names to the old module names used in Python 2, so that " +"the pickle data stream is readable with Python 2." +msgstr "" + +#: ../Doc/library/pickle.rst:209 +msgid "" +"Return the pickled representation of the object as a :class:`bytes` object, " +"instead of writing it to a file." +msgstr "" + +#: ../Doc/library/pickle.rst:212 +msgid "" +"Arguments *protocol* and *fix_imports* have the same meaning as in :func:" +"`dump`." +msgstr "" + +#: ../Doc/library/pickle.rst:217 +msgid "" +"Read a pickled object representation from the open :term:`file object` " +"*file* and return the reconstituted object hierarchy specified therein. This " +"is equivalent to ``Unpickler(file).load()``." +msgstr "" + +#: ../Doc/library/pickle.rst:221 ../Doc/library/pickle.rst:244 +msgid "" +"The protocol version of the pickle is detected automatically, so no protocol " +"argument is needed. Bytes past the pickled object's representation are " +"ignored." +msgstr "" + +#: ../Doc/library/pickle.rst:225 +msgid "" +"The argument *file* must have two methods, a read() method that takes an " +"integer argument, and a readline() method that requires no arguments. Both " +"methods should return bytes. Thus *file* can be an on-disk file opened for " +"binary reading, an :class:`io.BytesIO` object, or any other custom object " +"that meets this interface." +msgstr "" + +#: ../Doc/library/pickle.rst:231 ../Doc/library/pickle.rst:248 +msgid "" +"Optional keyword arguments are *fix_imports*, *encoding* and *errors*, which " +"are used to control compatibility support for pickle stream generated by " +"Python 2. If *fix_imports* is true, pickle will try to map the old Python 2 " +"names to the new names used in Python 3. The *encoding* and *errors* tell " +"pickle how to decode 8-bit string instances pickled by Python 2; these " +"default to 'ASCII' and 'strict', respectively. The *encoding* can be " +"'bytes' to read these 8-bit string instances as bytes objects." +msgstr "" + +#: ../Doc/library/pickle.rst:241 +msgid "" +"Read a pickled object hierarchy from a :class:`bytes` object and return the " +"reconstituted object hierarchy specified therein." +msgstr "" + +#: ../Doc/library/pickle.rst:257 +msgid "The :mod:`pickle` module defines three exceptions:" +msgstr "" + +#: ../Doc/library/pickle.rst:261 +msgid "" +"Common base class for the other pickling exceptions. It inherits :exc:" +"`Exception`." +msgstr "" + +#: ../Doc/library/pickle.rst:266 +msgid "" +"Error raised when an unpicklable object is encountered by :class:`Pickler`. " +"It inherits :exc:`PickleError`." +msgstr "" + +#: ../Doc/library/pickle.rst:269 +msgid "" +"Refer to :ref:`pickle-picklable` to learn what kinds of objects can be " +"pickled." +msgstr "" + +#: ../Doc/library/pickle.rst:274 +msgid "" +"Error raised when there is a problem unpickling an object, such as a data " +"corruption or a security violation. It inherits :exc:`PickleError`." +msgstr "" + +#: ../Doc/library/pickle.rst:277 +msgid "" +"Note that other exceptions may also be raised during unpickling, including " +"(but not necessarily limited to) AttributeError, EOFError, ImportError, and " +"IndexError." +msgstr "" + +#: ../Doc/library/pickle.rst:282 +msgid "" +"The :mod:`pickle` module exports two classes, :class:`Pickler` and :class:" +"`Unpickler`:" +msgstr "" + +#: ../Doc/library/pickle.rst:287 +msgid "This takes a binary file for writing a pickle data stream." +msgstr "" + +#: ../Doc/library/pickle.rst:305 +msgid "" +"Write a pickled representation of *obj* to the open file object given in the " +"constructor." +msgstr "" + +#: ../Doc/library/pickle.rst:310 +msgid "Do nothing by default. This exists so a subclass can override it." +msgstr "" + +#: ../Doc/library/pickle.rst:312 +msgid "" +"If :meth:`persistent_id` returns ``None``, *obj* is pickled as usual. Any " +"other value causes :class:`Pickler` to emit the returned value as a " +"persistent ID for *obj*. The meaning of this persistent ID should be " +"defined by :meth:`Unpickler.persistent_load`. Note that the value returned " +"by :meth:`persistent_id` cannot itself have a persistent ID." +msgstr "" + +#: ../Doc/library/pickle.rst:318 ../Doc/library/pickle.rst:389 +msgid "See :ref:`pickle-persistent` for details and examples of uses." +msgstr "" + +#: ../Doc/library/pickle.rst:322 +msgid "" +"A pickler object's dispatch table is a registry of *reduction functions* of " +"the kind which can be declared using :func:`copyreg.pickle`. It is a " +"mapping whose keys are classes and whose values are reduction functions. A " +"reduction function takes a single argument of the associated class and " +"should conform to the same interface as a :meth:`__reduce__` method." +msgstr "" + +#: ../Doc/library/pickle.rst:330 +msgid "" +"By default, a pickler object will not have a :attr:`dispatch_table` " +"attribute, and it will instead use the global dispatch table managed by the :" +"mod:`copyreg` module. However, to customize the pickling for a specific " +"pickler object one can set the :attr:`dispatch_table` attribute to a dict-" +"like object. Alternatively, if a subclass of :class:`Pickler` has a :attr:" +"`dispatch_table` attribute then this will be used as the default dispatch " +"table for instances of that class." +msgstr "" + +#: ../Doc/library/pickle.rst:339 +msgid "See :ref:`pickle-dispatch` for usage examples." +msgstr "" + +#: ../Doc/library/pickle.rst:345 +msgid "" +"Deprecated. Enable fast mode if set to a true value. The fast mode disables " +"the usage of memo, therefore speeding the pickling process by not generating " +"superfluous PUT opcodes. It should not be used with self-referential " +"objects, doing otherwise will cause :class:`Pickler` to recurse infinitely." +msgstr "" + +#: ../Doc/library/pickle.rst:351 +msgid "Use :func:`pickletools.optimize` if you need more compact pickles." +msgstr "" + +#: ../Doc/library/pickle.rst:356 +msgid "This takes a binary file for reading a pickle data stream." +msgstr "" + +#: ../Doc/library/pickle.rst:358 +msgid "" +"The protocol version of the pickle is detected automatically, so no protocol " +"argument is needed." +msgstr "" + +#: ../Doc/library/pickle.rst:361 +msgid "" +"The argument *file* must have two methods, a read() method that takes an " +"integer argument, and a readline() method that requires no arguments. Both " +"methods should return bytes. Thus *file* can be an on-disk file object " +"opened for binary reading, an :class:`io.BytesIO` object, or any other " +"custom object that meets this interface." +msgstr "" + +#: ../Doc/library/pickle.rst:367 +msgid "" +"Optional keyword arguments are *fix_imports*, *encoding* and *errors*, which " +"are used to control compatibility support for pickle stream generated by " +"Python 2. If *fix_imports* is true, pickle will try to map the old Python 2 " +"names to the new names used in Python 3. The *encoding* and *errors* tell " +"pickle how to decode 8-bit string instances pickled by Python 2; these " +"default to 'ASCII' and 'strict', respectively. The *encoding* can be " +"'bytes' to read these ß8-bit string instances as bytes objects." +msgstr "" + +#: ../Doc/library/pickle.rst:377 +msgid "" +"Read a pickled object representation from the open file object given in the " +"constructor, and return the reconstituted object hierarchy specified " +"therein. Bytes past the pickled object's representation are ignored." +msgstr "" + +#: ../Doc/library/pickle.rst:383 +msgid "Raise an :exc:`UnpicklingError` by default." +msgstr "" + +#: ../Doc/library/pickle.rst:385 +msgid "" +"If defined, :meth:`persistent_load` should return the object specified by " +"the persistent ID *pid*. If an invalid persistent ID is encountered, an :" +"exc:`UnpicklingError` should be raised." +msgstr "" + +#: ../Doc/library/pickle.rst:393 +msgid "" +"Import *module* if necessary and return the object called *name* from it, " +"where the *module* and *name* arguments are :class:`str` objects. Note, " +"unlike its name suggests, :meth:`find_class` is also used for finding " +"functions." +msgstr "" + +#: ../Doc/library/pickle.rst:398 +msgid "" +"Subclasses may override this to gain control over what type of objects and " +"how they can be loaded, potentially reducing security risks. Refer to :ref:" +"`pickle-restrict` for details." +msgstr "" + +#: ../Doc/library/pickle.rst:406 +msgid "What can be pickled and unpickled?" +msgstr "" + +#: ../Doc/library/pickle.rst:408 +msgid "The following types can be pickled:" +msgstr "" + +#: ../Doc/library/pickle.rst:410 +msgid "``None``, ``True``, and ``False``" +msgstr "" + +#: ../Doc/library/pickle.rst:412 +msgid "integers, floating point numbers, complex numbers" +msgstr "" + +#: ../Doc/library/pickle.rst:414 +msgid "strings, bytes, bytearrays" +msgstr "" + +#: ../Doc/library/pickle.rst:416 +msgid "tuples, lists, sets, and dictionaries containing only picklable objects" +msgstr "" + +#: ../Doc/library/pickle.rst:418 +msgid "" +"functions defined at the top level of a module (using :keyword:`def`, not :" +"keyword:`lambda`)" +msgstr "" + +#: ../Doc/library/pickle.rst:421 +msgid "built-in functions defined at the top level of a module" +msgstr "" + +#: ../Doc/library/pickle.rst:423 +msgid "classes that are defined at the top level of a module" +msgstr "" + +#: ../Doc/library/pickle.rst:425 +msgid "" +"instances of such classes whose :attr:`~object.__dict__` or the result of " +"calling :meth:`__getstate__` is picklable (see section :ref:`pickle-inst` " +"for details)." +msgstr "" + +#: ../Doc/library/pickle.rst:429 +msgid "" +"Attempts to pickle unpicklable objects will raise the :exc:`PicklingError` " +"exception; when this happens, an unspecified number of bytes may have " +"already been written to the underlying file. Trying to pickle a highly " +"recursive data structure may exceed the maximum recursion depth, a :exc:" +"`RecursionError` will be raised in this case. You can carefully raise this " +"limit with :func:`sys.setrecursionlimit`." +msgstr "" + +#: ../Doc/library/pickle.rst:436 +msgid "" +"Note that functions (built-in and user-defined) are pickled by \"fully " +"qualified\" name reference, not by value. [#]_ This means that only the " +"function name is pickled, along with the name of the module the function is " +"defined in. Neither the function's code, nor any of its function attributes " +"are pickled. Thus the defining module must be importable in the unpickling " +"environment, and the module must contain the named object, otherwise an " +"exception will be raised. [#]_" +msgstr "" + +#: ../Doc/library/pickle.rst:443 +msgid "" +"Similarly, classes are pickled by named reference, so the same restrictions " +"in the unpickling environment apply. Note that none of the class's code or " +"data is pickled, so in the following example the class attribute ``attr`` is " +"not restored in the unpickling environment::" +msgstr "" + +#: ../Doc/library/pickle.rst:453 +msgid "" +"These restrictions are why picklable functions and classes must be defined " +"in the top level of a module." +msgstr "" + +#: ../Doc/library/pickle.rst:456 +msgid "" +"Similarly, when class instances are pickled, their class's code and data are " +"not pickled along with them. Only the instance data are pickled. This is " +"done on purpose, so you can fix bugs in a class or add methods to the class " +"and still load objects that were created with an earlier version of the " +"class. If you plan to have long-lived objects that will see many versions " +"of a class, it may be worthwhile to put a version number in the objects so " +"that suitable conversions can be made by the class's :meth:`__setstate__` " +"method." +msgstr "" + +#: ../Doc/library/pickle.rst:468 +msgid "Pickling Class Instances" +msgstr "" + +#: ../Doc/library/pickle.rst:472 +msgid "" +"In this section, we describe the general mechanisms available to you to " +"define, customize, and control how class instances are pickled and unpickled." +msgstr "" + +#: ../Doc/library/pickle.rst:475 +msgid "" +"In most cases, no additional code is needed to make instances picklable. By " +"default, pickle will retrieve the class and the attributes of an instance " +"via introspection. When a class instance is unpickled, its :meth:`__init__` " +"method is usually *not* invoked. The default behaviour first creates an " +"uninitialized instance and then restores the saved attributes. The " +"following code shows an implementation of this behaviour::" +msgstr "" + +#: ../Doc/library/pickle.rst:490 +msgid "" +"Classes can alter the default behaviour by providing one or several special " +"methods:" +msgstr "" + +#: ../Doc/library/pickle.rst:495 +msgid "" +"In protocols 2 and newer, classes that implements the :meth:" +"`__getnewargs_ex__` method can dictate the values passed to the :meth:" +"`__new__` method upon unpickling. The method must return a pair ``(args, " +"kwargs)`` where *args* is a tuple of positional arguments and *kwargs* a " +"dictionary of named arguments for constructing the object. Those will be " +"passed to the :meth:`__new__` method upon unpickling." +msgstr "" + +#: ../Doc/library/pickle.rst:503 +msgid "" +"You should implement this method if the :meth:`__new__` method of your class " +"requires keyword-only arguments. Otherwise, it is recommended for " +"compatibility to implement :meth:`__getnewargs__`." +msgstr "" + +#: ../Doc/library/pickle.rst:507 +msgid ":meth:`__getnewargs_ex__` is now used in protocols 2 and 3." +msgstr "" + +#: ../Doc/library/pickle.rst:513 +msgid "" +"This method serve a similar purpose as :meth:`__getnewargs_ex__`, but " +"supports only positional arguments. It must return a tuple of arguments " +"``args`` which will be passed to the :meth:`__new__` method upon unpickling." +msgstr "" + +#: ../Doc/library/pickle.rst:517 +msgid "" +":meth:`__getnewargs__` will not be called if :meth:`__getnewargs_ex__` is " +"defined." +msgstr "" + +#: ../Doc/library/pickle.rst:520 +msgid "" +"Before Python 3.6, :meth:`__getnewargs__` was called instead of :meth:" +"`__getnewargs_ex__` in protocols 2 and 3." +msgstr "" + +#: ../Doc/library/pickle.rst:527 +msgid "" +"Classes can further influence how their instances are pickled; if the class " +"defines the method :meth:`__getstate__`, it is called and the returned " +"object is pickled as the contents for the instance, instead of the contents " +"of the instance's dictionary. If the :meth:`__getstate__` method is absent, " +"the instance's :attr:`~object.__dict__` is pickled as usual." +msgstr "" + +#: ../Doc/library/pickle.rst:536 +msgid "" +"Upon unpickling, if the class defines :meth:`__setstate__`, it is called " +"with the unpickled state. In that case, there is no requirement for the " +"state object to be a dictionary. Otherwise, the pickled state must be a " +"dictionary and its items are assigned to the new instance's dictionary." +msgstr "" + +#: ../Doc/library/pickle.rst:543 +msgid "" +"If :meth:`__getstate__` returns a false value, the :meth:`__setstate__` " +"method will not be called upon unpickling." +msgstr "" + +#: ../Doc/library/pickle.rst:547 +msgid "" +"Refer to the section :ref:`pickle-state` for more information about how to " +"use the methods :meth:`__getstate__` and :meth:`__setstate__`." +msgstr "" + +#: ../Doc/library/pickle.rst:552 +msgid "" +"At unpickling time, some methods like :meth:`__getattr__`, :meth:" +"`__getattribute__`, or :meth:`__setattr__` may be called upon the instance. " +"In case those methods rely on some internal invariant being true, the type " +"should implement :meth:`__getnewargs__` or :meth:`__getnewargs_ex__` to " +"establish such an invariant; otherwise, neither :meth:`__new__` nor :meth:" +"`__init__` will be called." +msgstr "" + +#: ../Doc/library/pickle.rst:561 +msgid "" +"As we shall see, pickle does not use directly the methods described above. " +"In fact, these methods are part of the copy protocol which implements the :" +"meth:`__reduce__` special method. The copy protocol provides a unified " +"interface for retrieving the data necessary for pickling and copying " +"objects. [#]_" +msgstr "" + +#: ../Doc/library/pickle.rst:567 +msgid "" +"Although powerful, implementing :meth:`__reduce__` directly in your classes " +"is error prone. For this reason, class designers should use the high-level " +"interface (i.e., :meth:`__getnewargs_ex__`, :meth:`__getstate__` and :meth:" +"`__setstate__`) whenever possible. We will show, however, cases where " +"using :meth:`__reduce__` is the only option or leads to more efficient " +"pickling or both." +msgstr "" + +#: ../Doc/library/pickle.rst:576 +msgid "" +"The interface is currently defined as follows. The :meth:`__reduce__` " +"method takes no argument and shall return either a string or preferably a " +"tuple (the returned object is often referred to as the \"reduce value\")." +msgstr "" + +#: ../Doc/library/pickle.rst:580 +msgid "" +"If a string is returned, the string should be interpreted as the name of a " +"global variable. It should be the object's local name relative to its " +"module; the pickle module searches the module namespace to determine the " +"object's module. This behaviour is typically useful for singletons." +msgstr "" + +#: ../Doc/library/pickle.rst:585 +msgid "" +"When a tuple is returned, it must be between two and five items long. " +"Optional items can either be omitted, or ``None`` can be provided as their " +"value. The semantics of each item are in order:" +msgstr "" + +#: ../Doc/library/pickle.rst:591 +msgid "" +"A callable object that will be called to create the initial version of the " +"object." +msgstr "" + +#: ../Doc/library/pickle.rst:594 +msgid "" +"A tuple of arguments for the callable object. An empty tuple must be given " +"if the callable does not accept any argument." +msgstr "" + +#: ../Doc/library/pickle.rst:597 +msgid "" +"Optionally, the object's state, which will be passed to the object's :meth:" +"`__setstate__` method as previously described. If the object has no such " +"method then, the value must be a dictionary and it will be added to the " +"object's :attr:`~object.__dict__` attribute." +msgstr "" + +#: ../Doc/library/pickle.rst:602 +msgid "" +"Optionally, an iterator (and not a sequence) yielding successive items. " +"These items will be appended to the object either using ``obj.append(item)`` " +"or, in batch, using ``obj.extend(list_of_items)``. This is primarily used " +"for list subclasses, but may be used by other classes as long as they have :" +"meth:`append` and :meth:`extend` methods with the appropriate signature. " +"(Whether :meth:`append` or :meth:`extend` is used depends on which pickle " +"protocol version is used as well as the number of items to append, so both " +"must be supported.)" +msgstr "" + +#: ../Doc/library/pickle.rst:611 +msgid "" +"Optionally, an iterator (not a sequence) yielding successive key-value " +"pairs. These items will be stored to the object using ``obj[key] = " +"value``. This is primarily used for dictionary subclasses, but may be used " +"by other classes as long as they implement :meth:`__setitem__`." +msgstr "" + +#: ../Doc/library/pickle.rst:619 +msgid "" +"Alternatively, a :meth:`__reduce_ex__` method may be defined. The only " +"difference is this method should take a single integer argument, the " +"protocol version. When defined, pickle will prefer it over the :meth:" +"`__reduce__` method. In addition, :meth:`__reduce__` automatically becomes " +"a synonym for the extended version. The main use for this method is to " +"provide backwards-compatible reduce values for older Python releases." +msgstr "" + +#: ../Doc/library/pickle.rst:631 +msgid "Persistence of External Objects" +msgstr "" + +#: ../Doc/library/pickle.rst:637 +msgid "" +"For the benefit of object persistence, the :mod:`pickle` module supports the " +"notion of a reference to an object outside the pickled data stream. Such " +"objects are referenced by a persistent ID, which should be either a string " +"of alphanumeric characters (for protocol 0) [#]_ or just an arbitrary object " +"(for any newer protocol)." +msgstr "" + +#: ../Doc/library/pickle.rst:643 +msgid "" +"The resolution of such persistent IDs is not defined by the :mod:`pickle` " +"module; it will delegate this resolution to the user defined methods on the " +"pickler and unpickler, :meth:`~Pickler.persistent_id` and :meth:`~Unpickler." +"persistent_load` respectively." +msgstr "" + +#: ../Doc/library/pickle.rst:648 +msgid "" +"To pickle objects that have an external persistent id, the pickler must have " +"a custom :meth:`~Pickler.persistent_id` method that takes an object as an " +"argument and returns either ``None`` or the persistent id for that object. " +"When ``None`` is returned, the pickler simply pickles the object as normal. " +"When a persistent ID string is returned, the pickler will pickle that " +"object, along with a marker so that the unpickler will recognize it as a " +"persistent ID." +msgstr "" + +#: ../Doc/library/pickle.rst:655 +msgid "" +"To unpickle external objects, the unpickler must have a custom :meth:" +"`~Unpickler.persistent_load` method that takes a persistent ID object and " +"returns the referenced object." +msgstr "" + +#: ../Doc/library/pickle.rst:659 +msgid "" +"Here is a comprehensive example presenting how persistent ID can be used to " +"pickle external objects by reference." +msgstr "" + +#: ../Doc/library/pickle.rst:667 +msgid "Dispatch Tables" +msgstr "" + +#: ../Doc/library/pickle.rst:669 +msgid "" +"If one wants to customize pickling of some classes without disturbing any " +"other code which depends on pickling, then one can create a pickler with a " +"private dispatch table." +msgstr "" + +#: ../Doc/library/pickle.rst:673 +msgid "" +"The global dispatch table managed by the :mod:`copyreg` module is available " +"as :data:`copyreg.dispatch_table`. Therefore, one may choose to use a " +"modified copy of :data:`copyreg.dispatch_table` as a private dispatch table." +msgstr "" + +#: ../Doc/library/pickle.rst:678 +msgid "For example ::" +msgstr "" + +#: ../Doc/library/pickle.rst:685 +msgid "" +"creates an instance of :class:`pickle.Pickler` with a private dispatch table " +"which handles the ``SomeClass`` class specially. Alternatively, the code ::" +msgstr "" + +#: ../Doc/library/pickle.rst:695 +msgid "" +"does the same, but all instances of ``MyPickler`` will by default share the " +"same dispatch table. The equivalent code using the :mod:`copyreg` module " +"is ::" +msgstr "" + +#: ../Doc/library/pickle.rst:706 +msgid "Handling Stateful Objects" +msgstr "" + +#: ../Doc/library/pickle.rst:712 +msgid "" +"Here's an example that shows how to modify pickling behavior for a class. " +"The :class:`TextReader` class opens a text file, and returns the line number " +"and line contents each time its :meth:`!readline` method is called. If a :" +"class:`TextReader` instance is pickled, all attributes *except* the file " +"object member are saved. When the instance is unpickled, the file is " +"reopened, and reading resumes from the last location. The :meth:" +"`__setstate__` and :meth:`__getstate__` methods are used to implement this " +"behavior. ::" +msgstr "" + +#: ../Doc/library/pickle.rst:758 +msgid "A sample usage might be something like this::" +msgstr "" + +#: ../Doc/library/pickle.rst:773 +msgid "Restricting Globals" +msgstr "" + +#: ../Doc/library/pickle.rst:778 +msgid "" +"By default, unpickling will import any class or function that it finds in " +"the pickle data. For many applications, this behaviour is unacceptable as " +"it permits the unpickler to import and invoke arbitrary code. Just consider " +"what this hand-crafted pickle data stream does when loaded::" +msgstr "" + +#: ../Doc/library/pickle.rst:788 +msgid "" +"In this example, the unpickler imports the :func:`os.system` function and " +"then apply the string argument \"echo hello world\". Although this example " +"is inoffensive, it is not difficult to imagine one that could damage your " +"system." +msgstr "" + +#: ../Doc/library/pickle.rst:792 +msgid "" +"For this reason, you may want to control what gets unpickled by customizing :" +"meth:`Unpickler.find_class`. Unlike its name suggests, :meth:`Unpickler." +"find_class` is called whenever a global (i.e., a class or a function) is " +"requested. Thus it is possible to either completely forbid globals or " +"restrict them to a safe subset." +msgstr "" + +#: ../Doc/library/pickle.rst:798 +msgid "" +"Here is an example of an unpickler allowing only few safe classes from the :" +"mod:`builtins` module to be loaded::" +msgstr "" + +#: ../Doc/library/pickle.rst:827 +msgid "A sample usage of our unpickler working has intended::" +msgstr "" + +#: ../Doc/library/pickle.rst:846 +msgid "" +"As our examples shows, you have to be careful with what you allow to be " +"unpickled. Therefore if security is a concern, you may want to consider " +"alternatives such as the marshalling API in :mod:`xmlrpc.client` or third-" +"party solutions." +msgstr "" + +#: ../Doc/library/pickle.rst:855 +msgid "" +"Recent versions of the pickle protocol (from protocol 2 and upwards) feature " +"efficient binary encodings for several common features and built-in types. " +"Also, the :mod:`pickle` module has a transparent optimizer written in C." +msgstr "" + +#: ../Doc/library/pickle.rst:865 +msgid "" +"For the simplest code, use the :func:`dump` and :func:`load` functions. ::" +msgstr "" + +#: ../Doc/library/pickle.rst:881 +msgid "The following example reads the resulting pickled data. ::" +msgstr "" + +#: ../Doc/library/pickle.rst:898 +msgid "Module :mod:`copyreg`" +msgstr "" + +#: ../Doc/library/pickle.rst:898 +msgid "Pickle interface constructor registration for extension types." +msgstr "" + +#: ../Doc/library/pickle.rst:901 +msgid "Module :mod:`pickletools`" +msgstr "" + +#: ../Doc/library/pickle.rst:901 +msgid "Tools for working with and analyzing pickled data." +msgstr "" + +#: ../Doc/library/pickle.rst:904 +msgid "Indexed databases of objects; uses :mod:`pickle`." +msgstr "" + +#: ../Doc/library/pickle.rst:907 +msgid "Module :mod:`copy`" +msgstr "" + +#: ../Doc/library/pickle.rst:907 +msgid "Shallow and deep object copying." +msgstr "" + +#: ../Doc/library/pickle.rst:909 +msgid "Module :mod:`marshal`" +msgstr "" + +#: ../Doc/library/pickle.rst:910 +msgid "High-performance serialization of built-in types." +msgstr "" + +#: ../Doc/library/pickle.rst:915 +msgid "Don't confuse this with the :mod:`marshal` module" +msgstr "" + +#: ../Doc/library/pickle.rst:917 +msgid "" +"This is why :keyword:`lambda` functions cannot be pickled: all :keyword:" +"`lambda` functions share the same name: ````." +msgstr "" + +#: ../Doc/library/pickle.rst:920 +msgid "" +"The exception raised will likely be an :exc:`ImportError` or an :exc:" +"`AttributeError` but it could be something else." +msgstr "" + +#: ../Doc/library/pickle.rst:923 +msgid "" +"The :mod:`copy` module uses this protocol for shallow and deep copying " +"operations." +msgstr "" + +#: ../Doc/library/pickle.rst:926 +msgid "" +"The limitation on alphanumeric characters is due to the fact the persistent " +"IDs, in protocol 0, are delimited by the newline character. Therefore if " +"any kind of newline characters occurs in persistent IDs, the resulting " +"pickle will become unreadable." +msgstr "" + +#: ../Doc/library/pickletools.rst:2 +msgid ":mod:`pickletools` --- Tools for pickle developers" +msgstr "" + +#: ../Doc/library/pickletools.rst:8 +msgid "**Source code:** :source:`Lib/pickletools.py`" +msgstr "" + +#: ../Doc/library/pickletools.rst:13 +msgid "" +"This module contains various constants relating to the intimate details of " +"the :mod:`pickle` module, some lengthy comments about the implementation, " +"and a few useful functions for analyzing pickled data. The contents of this " +"module are useful for Python core developers who are working on the :mod:" +"`pickle`; ordinary users of the :mod:`pickle` module probably won't find " +"the :mod:`pickletools` module relevant." +msgstr "" + +#: ../Doc/library/pickletools.rst:25 +msgid "" +"When invoked from the command line, ``python -m pickletools`` will " +"disassemble the contents of one or more pickle files. Note that if you want " +"to see the Python object stored in the pickle rather than the details of " +"pickle format, you may want to use ``-m pickle`` instead. However, when the " +"pickle file that you want to examine comes from an untrusted source, ``-m " +"pickletools`` is a safer option because it does not execute pickle bytecode." +msgstr "" + +#: ../Doc/library/pickletools.rst:33 +msgid "For example, with a tuple ``(1, 2)`` pickled in file ``x.pickle``:" +msgstr "" + +#: ../Doc/library/pickletools.rst:56 +msgid "Annotate each line with a short opcode description." +msgstr "" + +#: ../Doc/library/pickletools.rst:60 +msgid "Name of a file where the output should be written." +msgstr "" + +#: ../Doc/library/pickletools.rst:64 +msgid "The number of blanks by which to indent a new MARK level." +msgstr "" + +#: ../Doc/library/pickletools.rst:68 +msgid "" +"When multiple objects are disassembled, preserve memo between disassemblies." +msgstr "" + +#: ../Doc/library/pickletools.rst:73 +msgid "" +"When more than one pickle file are specified, print given preamble before " +"each disassembly." +msgstr "" + +#: ../Doc/library/pickletools.rst:79 ../Doc/library/trace.rst:131 +msgid "Programmatic Interface" +msgstr "" + +#: ../Doc/library/pickletools.rst:84 +msgid "" +"Outputs a symbolic disassembly of the pickle to the file-like object *out*, " +"defaulting to ``sys.stdout``. *pickle* can be a string or a file-like " +"object. *memo* can be a Python dictionary that will be used as the pickle's " +"memo; it can be used to perform disassemblies across multiple pickles " +"created by the same pickler. Successive levels, indicated by ``MARK`` " +"opcodes in the stream, are indented by *indentlevel* spaces. If a nonzero " +"value is given to *annotate*, each opcode in the output is annotated with a " +"short description. The value of *annotate* is used as a hint for the column " +"where annotation should start." +msgstr "" + +#: ../Doc/library/pickletools.rst:95 +msgid "The *annotate* argument." +msgstr "" + +#: ../Doc/library/pickletools.rst:100 +msgid "" +"Provides an :term:`iterator` over all of the opcodes in a pickle, returning " +"a sequence of ``(opcode, arg, pos)`` triples. *opcode* is an instance of " +"an :class:`OpcodeInfo` class; *arg* is the decoded value, as a Python " +"object, of the opcode's argument; *pos* is the position at which this opcode " +"is located. *pickle* can be a string or a file-like object." +msgstr "" + +#: ../Doc/library/pickletools.rst:108 +msgid "" +"Returns a new equivalent pickle string after eliminating unused ``PUT`` " +"opcodes. The optimized pickle is shorter, takes less transmission time, " +"requires less storage space, and unpickles more efficiently." +msgstr "" + +#: ../Doc/library/pipes.rst:2 +msgid ":mod:`pipes` --- Interface to shell pipelines" +msgstr "" + +#: ../Doc/library/pipes.rst:10 +msgid "**Source code:** :source:`Lib/pipes.py`" +msgstr "" + +#: ../Doc/library/pipes.rst:14 +msgid "" +"The :mod:`pipes` module defines a class to abstract the concept of a " +"*pipeline* --- a sequence of converters from one file to another." +msgstr "" + +#: ../Doc/library/pipes.rst:17 +msgid "" +"Because the module uses :program:`/bin/sh` command lines, a POSIX or " +"compatible shell for :func:`os.system` and :func:`os.popen` is required." +msgstr "" + +#: ../Doc/library/pipes.rst:20 +msgid "The :mod:`pipes` module defines the following class:" +msgstr "" + +#: ../Doc/library/pipes.rst:25 +msgid "An abstraction of a pipeline." +msgstr "" + +#: ../Doc/library/pipes.rst:42 +msgid "Template Objects" +msgstr "" + +#: ../Doc/library/pipes.rst:44 +msgid "Template objects following methods:" +msgstr "" + +#: ../Doc/library/pipes.rst:49 +msgid "Restore a pipeline template to its initial state." +msgstr "" + +#: ../Doc/library/pipes.rst:54 +msgid "Return a new, equivalent, pipeline template." +msgstr "" + +#: ../Doc/library/pipes.rst:59 +msgid "" +"If *flag* is true, turn debugging on. Otherwise, turn debugging off. When " +"debugging is on, commands to be executed are printed, and the shell is given " +"``set -x`` command to be more verbose." +msgstr "" + +#: ../Doc/library/pipes.rst:66 +msgid "" +"Append a new action at the end. The *cmd* variable must be a valid bourne " +"shell command. The *kind* variable consists of two letters." +msgstr "" + +#: ../Doc/library/pipes.rst:69 +msgid "" +"The first letter can be either of ``'-'`` (which means the command reads its " +"standard input), ``'f'`` (which means the commands reads a given file on the " +"command line) or ``'.'`` (which means the commands reads no input, and hence " +"must be first.)" +msgstr "" + +#: ../Doc/library/pipes.rst:74 +msgid "" +"Similarly, the second letter can be either of ``'-'`` (which means the " +"command writes to standard output), ``'f'`` (which means the command writes " +"a file on the command line) or ``'.'`` (which means the command does not " +"write anything, and hence must be last.)" +msgstr "" + +#: ../Doc/library/pipes.rst:82 +msgid "" +"Add a new action at the beginning. See :meth:`append` for explanations of " +"the arguments." +msgstr "" + +#: ../Doc/library/pipes.rst:88 +msgid "" +"Return a file-like object, open to *file*, but read from or written to by " +"the pipeline. Note that only one of ``'r'``, ``'w'`` may be given." +msgstr "" + +#: ../Doc/library/pipes.rst:94 +msgid "Copy *infile* to *outfile* through the pipe." +msgstr "" + +#: ../Doc/library/pkgutil.rst:2 +msgid ":mod:`pkgutil` --- Package extension utility" +msgstr "" + +#: ../Doc/library/pkgutil.rst:7 +msgid "**Source code:** :source:`Lib/pkgutil.py`" +msgstr "" + +#: ../Doc/library/pkgutil.rst:11 +msgid "" +"This module provides utilities for the import system, in particular package " +"support." +msgstr "" + +#: ../Doc/library/pkgutil.rst:16 +msgid "A namedtuple that holds a brief summary of a module's info." +msgstr "" + +#: ../Doc/library/pkgutil.rst:22 +msgid "" +"Extend the search path for the modules which comprise a package. Intended " +"use is to place the following code in a package's :file:`__init__.py`::" +msgstr "" + +#: ../Doc/library/pkgutil.rst:28 +msgid "" +"This will add to the package's ``__path__`` all subdirectories of " +"directories on ``sys.path`` named after the package. This is useful if one " +"wants to distribute different parts of a single logical package as multiple " +"directories." +msgstr "" + +#: ../Doc/library/pkgutil.rst:33 +msgid "" +"It also looks for :file:`\\*.pkg` files beginning where ``*`` matches the " +"*name* argument. This feature is similar to :file:`\\*.pth` files (see the :" +"mod:`site` module for more information), except that it doesn't special-case " +"lines starting with ``import``. A :file:`\\*.pkg` file is trusted at face " +"value: apart from checking for duplicates, all entries found in a :file:`\\*." +"pkg` file are added to the path, regardless of whether they exist on the " +"filesystem. (This is a feature.)" +msgstr "" + +#: ../Doc/library/pkgutil.rst:41 +msgid "" +"If the input path is not a list (as is the case for frozen packages) it is " +"returned unchanged. The input path is not modified; an extended copy is " +"returned. Items are only appended to the copy at the end." +msgstr "" + +#: ../Doc/library/pkgutil.rst:45 +msgid "" +"It is assumed that :data:`sys.path` is a sequence. Items of :data:`sys." +"path` that are not strings referring to existing directories are ignored. " +"Unicode items on :data:`sys.path` that cause errors when used as filenames " +"may cause this function to raise an exception (in line with :func:`os.path." +"isdir` behavior)." +msgstr "" + +#: ../Doc/library/pkgutil.rst:54 +msgid ":pep:`302` Finder that wraps Python's \"classic\" import algorithm." +msgstr "" + +#: ../Doc/library/pkgutil.rst:56 +msgid "" +"If *dirname* is a string, a :pep:`302` finder is created that searches that " +"directory. If *dirname* is ``None``, a :pep:`302` finder is created that " +"searches the current :data:`sys.path`, plus any modules that are frozen or " +"built-in." +msgstr "" + +#: ../Doc/library/pkgutil.rst:61 +msgid "" +"Note that :class:`ImpImporter` does not currently support being used by " +"placement on :data:`sys.meta_path`." +msgstr "" + +#: ../Doc/library/pkgutil.rst:64 ../Doc/library/pkgutil.rst:73 +msgid "" +"This emulation is no longer needed, as the standard import mechanism is now " +"fully PEP 302 compliant and available in :mod:`importlib`." +msgstr "" + +#: ../Doc/library/pkgutil.rst:71 +msgid ":term:`Loader` that wraps Python's \"classic\" import algorithm." +msgstr "" + +#: ../Doc/library/pkgutil.rst:80 +msgid "Retrieve a module :term:`loader` for the given *fullname*." +msgstr "" + +#: ../Doc/library/pkgutil.rst:82 +msgid "" +"This is a backwards compatibility wrapper around :func:`importlib.util." +"find_spec` that converts most failures to :exc:`ImportError` and only " +"returns the loader rather than the full :class:`ModuleSpec`." +msgstr "" + +#: ../Doc/library/pkgutil.rst:87 ../Doc/library/pkgutil.rst:104 +#: ../Doc/library/pkgutil.rst:119 ../Doc/library/pkgutil.rst:140 +#: ../Doc/library/pkgutil.rst:161 ../Doc/library/pkgutil.rst:200 +msgid "" +"Updated to be based directly on :mod:`importlib` rather than relying on the " +"package internal PEP 302 import emulation." +msgstr "" + +#: ../Doc/library/pkgutil.rst:91 ../Doc/library/pkgutil.rst:123 +msgid "Updated to be based on :pep:`451`" +msgstr "" + +#: ../Doc/library/pkgutil.rst:96 +msgid "Retrieve a :term:`finder` for the given *path_item*." +msgstr "" + +#: ../Doc/library/pkgutil.rst:98 +msgid "" +"The returned finder is cached in :data:`sys.path_importer_cache` if it was " +"newly created by a path hook." +msgstr "" + +#: ../Doc/library/pkgutil.rst:101 +msgid "" +"The cache (or part of it) can be cleared manually if a rescan of :data:`sys." +"path_hooks` is necessary." +msgstr "" + +#: ../Doc/library/pkgutil.rst:111 +msgid "Get a :term:`loader` object for *module_or_name*." +msgstr "" + +#: ../Doc/library/pkgutil.rst:113 +msgid "" +"If the module or package is accessible via the normal import mechanism, a " +"wrapper around the relevant part of that machinery is returned. Returns " +"``None`` if the module cannot be found or imported. If the named module is " +"not already imported, its containing package (if any) is imported, in order " +"to establish the package ``__path__``." +msgstr "" + +#: ../Doc/library/pkgutil.rst:129 +msgid "Yield :term:`finder` objects for the given module name." +msgstr "" + +#: ../Doc/library/pkgutil.rst:131 +msgid "" +"If fullname contains a '.', the finders will be for the package containing " +"fullname, otherwise they will be all registered top level finders (i.e. " +"those on both sys.meta_path and sys.path_hooks)." +msgstr "" + +#: ../Doc/library/pkgutil.rst:135 +msgid "" +"If the named module is in a package, that package is imported as a side " +"effect of invoking this function." +msgstr "" + +#: ../Doc/library/pkgutil.rst:138 +msgid "If no module name is specified, all top level finders are produced." +msgstr "" + +#: ../Doc/library/pkgutil.rst:147 +msgid "" +"Yields :class:`ModuleInfo` for all submodules on *path*, or, if *path* is " +"``None``, all top-level modules on ``sys.path``." +msgstr "" + +#: ../Doc/library/pkgutil.rst:150 ../Doc/library/pkgutil.rst:171 +msgid "" +"*path* should be either ``None`` or a list of paths to look for modules in." +msgstr "" + +#: ../Doc/library/pkgutil.rst:152 ../Doc/library/pkgutil.rst:173 +msgid "" +"*prefix* is a string to output on the front of every module name on output." +msgstr "" + +#: ../Doc/library/pkgutil.rst:156 ../Doc/library/pkgutil.rst:195 +msgid "" +"Only works for a :term:`finder` which defines an ``iter_modules()`` method. " +"This interface is non-standard, so the module also provides implementations " +"for :class:`importlib.machinery.FileFinder` and :class:`zipimport." +"zipimporter`." +msgstr "" + +#: ../Doc/library/pkgutil.rst:168 +msgid "" +"Yields :class:`ModuleInfo` for all modules recursively on *path*, or, if " +"*path* is ``None``, all accessible modules." +msgstr "" + +#: ../Doc/library/pkgutil.rst:175 +msgid "" +"Note that this function must import all *packages* (*not* all modules!) on " +"the given *path*, in order to access the ``__path__`` attribute to find " +"submodules." +msgstr "" + +#: ../Doc/library/pkgutil.rst:179 +msgid "" +"*onerror* is a function which gets called with one argument (the name of the " +"package which was being imported) if any exception occurs while trying to " +"import a package. If no *onerror* function is supplied, :exc:`ImportError`" +"\\s are caught and ignored, while all other exceptions are propagated, " +"terminating the search." +msgstr "" + +#: ../Doc/library/pkgutil.rst:207 +msgid "Get a resource from a package." +msgstr "" + +#: ../Doc/library/pkgutil.rst:209 +msgid "" +"This is a wrapper for the :term:`loader` :meth:`get_data ` API. The *package* argument should be the name of " +"a package, in standard module format (``foo.bar``). The *resource* argument " +"should be in the form of a relative filename, using ``/`` as the path " +"separator. The parent directory name ``..`` is not allowed, and nor is a " +"rooted name (starting with a ``/``)." +msgstr "" + +#: ../Doc/library/pkgutil.rst:216 +msgid "" +"The function returns a binary string that is the contents of the specified " +"resource." +msgstr "" + +#: ../Doc/library/pkgutil.rst:219 +msgid "" +"For packages located in the filesystem, which have already been imported, " +"this is the rough equivalent of::" +msgstr "" + +#: ../Doc/library/pkgutil.rst:225 +msgid "" +"If the package cannot be located or loaded, or it uses a :term:`loader` " +"which does not support :meth:`get_data `, then ``None`` is returned." +msgstr "" + +#: ../Doc/library/platform.rst:2 +msgid ":mod:`platform` --- Access to underlying platform's identifying data" +msgstr "" + +#: ../Doc/library/platform.rst:10 +msgid "**Source code:** :source:`Lib/platform.py`" +msgstr "" + +#: ../Doc/library/platform.rst:16 +msgid "" +"Specific platforms listed alphabetically, with Linux included in the Unix " +"section." +msgstr "" + +#: ../Doc/library/platform.rst:21 +msgid "Cross Platform" +msgstr "" + +#: ../Doc/library/platform.rst:26 +msgid "" +"Queries the given executable (defaults to the Python interpreter binary) for " +"various architecture information." +msgstr "" + +#: ../Doc/library/platform.rst:29 +msgid "" +"Returns a tuple ``(bits, linkage)`` which contain information about the bit " +"architecture and the linkage format used for the executable. Both values are " +"returned as strings." +msgstr "" + +#: ../Doc/library/platform.rst:33 +msgid "" +"Values that cannot be determined are returned as given by the parameter " +"presets. If bits is given as ``''``, the ``sizeof(pointer)`` (or " +"``sizeof(long)`` on Python version < 1.5.2) is used as indicator for the " +"supported pointer size." +msgstr "" + +#: ../Doc/library/platform.rst:38 +msgid "" +"The function relies on the system's :file:`file` command to do the actual " +"work. This is available on most if not all Unix platforms and some non-Unix " +"platforms and then only if the executable points to the Python interpreter. " +"Reasonable defaults are used when the above needs are not met." +msgstr "" + +#: ../Doc/library/platform.rst:45 +msgid "" +"On Mac OS X (and perhaps other platforms), executable files may be universal " +"files containing multiple architectures." +msgstr "" + +#: ../Doc/library/platform.rst:48 +msgid "" +"To get at the \"64-bitness\" of the current interpreter, it is more reliable " +"to query the :attr:`sys.maxsize` attribute::" +msgstr "" + +#: ../Doc/library/platform.rst:56 +msgid "" +"Returns the machine type, e.g. ``'i386'``. An empty string is returned if " +"the value cannot be determined." +msgstr "" + +#: ../Doc/library/platform.rst:62 +msgid "" +"Returns the computer's network name (may not be fully qualified!). An empty " +"string is returned if the value cannot be determined." +msgstr "" + +#: ../Doc/library/platform.rst:68 +msgid "" +"Returns a single string identifying the underlying platform with as much " +"useful information as possible." +msgstr "" + +#: ../Doc/library/platform.rst:71 +msgid "" +"The output is intended to be *human readable* rather than machine parseable. " +"It may look different on different platforms and this is intended." +msgstr "" + +#: ../Doc/library/platform.rst:74 +msgid "" +"If *aliased* is true, the function will use aliases for various platforms " +"that report system names which differ from their common names, for example " +"SunOS will be reported as Solaris. The :func:`system_alias` function is " +"used to implement this." +msgstr "" + +#: ../Doc/library/platform.rst:79 +msgid "" +"Setting *terse* to true causes the function to return only the absolute " +"minimum information needed to identify the platform." +msgstr "" + +#: ../Doc/library/platform.rst:85 +msgid "Returns the (real) processor name, e.g. ``'amdk6'``." +msgstr "" + +#: ../Doc/library/platform.rst:87 +msgid "" +"An empty string is returned if the value cannot be determined. Note that " +"many platforms do not provide this information or simply return the same " +"value as for :func:`machine`. NetBSD does this." +msgstr "" + +#: ../Doc/library/platform.rst:94 +msgid "" +"Returns a tuple ``(buildno, builddate)`` stating the Python build number and " +"date as strings." +msgstr "" + +#: ../Doc/library/platform.rst:100 +msgid "Returns a string identifying the compiler used for compiling Python." +msgstr "" + +#: ../Doc/library/platform.rst:105 +msgid "Returns a string identifying the Python implementation SCM branch." +msgstr "" + +#: ../Doc/library/platform.rst:110 +msgid "" +"Returns a string identifying the Python implementation. Possible return " +"values are: 'CPython', 'IronPython', 'Jython', 'PyPy'." +msgstr "" + +#: ../Doc/library/platform.rst:116 +msgid "Returns a string identifying the Python implementation SCM revision." +msgstr "" + +#: ../Doc/library/platform.rst:121 +msgid "Returns the Python version as string ``'major.minor.patchlevel'``." +msgstr "" + +#: ../Doc/library/platform.rst:123 +msgid "" +"Note that unlike the Python ``sys.version``, the returned value will always " +"include the patchlevel (it defaults to 0)." +msgstr "" + +#: ../Doc/library/platform.rst:129 +msgid "" +"Returns the Python version as tuple ``(major, minor, patchlevel)`` of " +"strings." +msgstr "" + +#: ../Doc/library/platform.rst:131 +msgid "" +"Note that unlike the Python ``sys.version``, the returned value will always " +"include the patchlevel (it defaults to ``'0'``)." +msgstr "" + +#: ../Doc/library/platform.rst:137 +msgid "" +"Returns the system's release, e.g. ``'2.2.0'`` or ``'NT'`` An empty string " +"is returned if the value cannot be determined." +msgstr "" + +#: ../Doc/library/platform.rst:143 +msgid "" +"Returns the system/OS name, e.g. ``'Linux'``, ``'Windows'``, or ``'Java'``. " +"An empty string is returned if the value cannot be determined." +msgstr "" + +#: ../Doc/library/platform.rst:149 +msgid "" +"Returns ``(system, release, version)`` aliased to common marketing names " +"used for some systems. It also does some reordering of the information in " +"some cases where it would otherwise cause confusion." +msgstr "" + +#: ../Doc/library/platform.rst:156 +msgid "" +"Returns the system's release version, e.g. ``'#3 on degas'``. An empty " +"string is returned if the value cannot be determined." +msgstr "" + +#: ../Doc/library/platform.rst:162 +msgid "" +"Fairly portable uname interface. Returns a :func:`~collections.namedtuple` " +"containing six attributes: :attr:`system`, :attr:`node`, :attr:`release`, :" +"attr:`version`, :attr:`machine`, and :attr:`processor`." +msgstr "" + +#: ../Doc/library/platform.rst:166 +msgid "" +"Note that this adds a sixth attribute (:attr:`processor`) not present in " +"the :func:`os.uname` result. Also, the attribute names are different for " +"the first two attributes; :func:`os.uname` names them :attr:`sysname` and :" +"attr:`nodename`." +msgstr "" + +#: ../Doc/library/platform.rst:171 +msgid "Entries which cannot be determined are set to ``''``." +msgstr "" + +#: ../Doc/library/platform.rst:173 ../Doc/library/sndhdr.rst:39 +#: ../Doc/library/sndhdr.rst:49 +msgid "Result changed from a tuple to a namedtuple." +msgstr "" + +#: ../Doc/library/platform.rst:178 +msgid "Java Platform" +msgstr "" + +#: ../Doc/library/platform.rst:183 +msgid "Version interface for Jython." +msgstr "" + +#: ../Doc/library/platform.rst:185 +msgid "" +"Returns a tuple ``(release, vendor, vminfo, osinfo)`` with *vminfo* being a " +"tuple ``(vm_name, vm_release, vm_vendor)`` and *osinfo* being a tuple " +"``(os_name, os_version, os_arch)``. Values which cannot be determined are " +"set to the defaults given as parameters (which all default to ``''``)." +msgstr "" + +#: ../Doc/library/platform.rst:192 +msgid "Windows Platform" +msgstr "" + +#: ../Doc/library/platform.rst:197 +msgid "" +"Get additional version information from the Windows Registry and return a " +"tuple ``(release, version, csd, ptype)`` referring to OS release, version " +"number, CSD level (service pack) and OS type (multi/single processor)." +msgstr "" + +#: ../Doc/library/platform.rst:201 +msgid "" +"As a hint: *ptype* is ``'Uniprocessor Free'`` on single processor NT " +"machines and ``'Multiprocessor Free'`` on multi processor machines. The " +"*'Free'* refers to the OS version being free of debugging code. It could " +"also state *'Checked'* which means the OS version uses debugging code, i.e. " +"code that checks arguments, ranges, etc." +msgstr "" + +#: ../Doc/library/platform.rst:209 +msgid "" +"This function works best with Mark Hammond's :mod:`win32all` package " +"installed, but also on Python 2.3 and later (support for this was added in " +"Python 2.6). It obviously only runs on Win32 compatible platforms." +msgstr "" + +#: ../Doc/library/platform.rst:216 +msgid "Win95/98 specific" +msgstr "" + +#: ../Doc/library/platform.rst:220 +msgid "" +"Portable :func:`popen` interface. Find a working popen implementation " +"preferring :func:`win32pipe.popen`. On Windows NT, :func:`win32pipe.popen` " +"should work; on Windows 9x it hangs due to bugs in the MS C library." +msgstr "" + +#: ../Doc/library/platform.rst:224 +msgid "" +"This function is obsolete. Use the :mod:`subprocess` module. Check " +"especially the :ref:`subprocess-replacements` section." +msgstr "" + +#: ../Doc/library/platform.rst:230 +msgid "Mac OS Platform" +msgstr "" + +#: ../Doc/library/platform.rst:235 +msgid "" +"Get Mac OS version information and return it as tuple ``(release, " +"versioninfo, machine)`` with *versioninfo* being a tuple ``(version, " +"dev_stage, non_release_version)``." +msgstr "" + +#: ../Doc/library/platform.rst:239 +msgid "" +"Entries which cannot be determined are set to ``''``. All tuple entries are " +"strings." +msgstr "" + +#: ../Doc/library/platform.rst:244 +msgid "Unix Platforms" +msgstr "" + +#: ../Doc/library/platform.rst:249 +msgid "This is another name for :func:`linux_distribution`." +msgstr "" + +#: ../Doc/library/platform.rst:251 ../Doc/library/platform.rst:269 +msgid "Deprecated since version 3.5, will be removed in version 3.7." +msgstr "" + +#: ../Doc/library/platform.rst:255 +msgid "Tries to determine the name of the Linux OS distribution name." +msgstr "" + +#: ../Doc/library/platform.rst:257 +msgid "" +"``supported_dists`` may be given to define the set of Linux distributions to " +"look for. It defaults to a list of currently supported Linux distributions " +"identified by their release file name." +msgstr "" + +#: ../Doc/library/platform.rst:261 +msgid "" +"If ``full_distribution_name`` is true (default), the full distribution read " +"from the OS is returned. Otherwise the short name taken from " +"``supported_dists`` is used." +msgstr "" + +#: ../Doc/library/platform.rst:265 +msgid "" +"Returns a tuple ``(distname,version,id)`` which defaults to the args given " +"as parameters. ``id`` is the item in parentheses after the version number. " +"It is usually the version codename." +msgstr "" + +#: ../Doc/library/platform.rst:273 +msgid "" +"Tries to determine the libc version against which the file executable " +"(defaults to the Python interpreter) is linked. Returns a tuple of strings " +"``(lib, version)`` which default to the given parameters in case the lookup " +"fails." +msgstr "" + +#: ../Doc/library/platform.rst:277 +msgid "" +"Note that this function has intimate knowledge of how different libc " +"versions add symbols to the executable is probably only usable for " +"executables compiled using :program:`gcc`." +msgstr "" + +#: ../Doc/library/platform.rst:281 +msgid "The file is read and scanned in chunks of *chunksize* bytes." +msgstr "" + +#: ../Doc/library/plistlib.rst:2 +msgid ":mod:`plistlib` --- Generate and parse Mac OS X ``.plist`` files" +msgstr "" + +#: ../Doc/library/plistlib.rst:11 +msgid "**Source code:** :source:`Lib/plistlib.py`" +msgstr "" + +#: ../Doc/library/plistlib.rst:19 +msgid "" +"This module provides an interface for reading and writing the \"property list" +"\" files used mainly by Mac OS X and supports both binary and XML plist " +"files." +msgstr "" + +#: ../Doc/library/plistlib.rst:22 +msgid "" +"The property list (``.plist``) file format is a simple serialization " +"supporting basic object types, like dictionaries, lists, numbers and " +"strings. Usually the top level object is a dictionary." +msgstr "" + +#: ../Doc/library/plistlib.rst:26 +msgid "" +"To write out and to parse a plist file, use the :func:`dump` and :func:" +"`load` functions." +msgstr "" + +#: ../Doc/library/plistlib.rst:29 +msgid "" +"To work with plist data in bytes objects, use :func:`dumps` and :func:" +"`loads`." +msgstr "" + +#: ../Doc/library/plistlib.rst:32 +msgid "" +"Values can be strings, integers, floats, booleans, tuples, lists, " +"dictionaries (but only with string keys), :class:`Data`, :class:`bytes`, :" +"class:`bytesarray` or :class:`datetime.datetime` objects." +msgstr "" + +#: ../Doc/library/plistlib.rst:36 +msgid "New API, old API deprecated. Support for binary format plists added." +msgstr "" + +#: ../Doc/library/plistlib.rst:41 +msgid "" +"`PList manual page `_" +msgstr "" + +#: ../Doc/library/plistlib.rst:42 +msgid "Apple's documentation of the file format." +msgstr "" + +#: ../Doc/library/plistlib.rst:45 ../Doc/library/threading.rst:24 +msgid "This module defines the following functions:" +msgstr "" + +#: ../Doc/library/plistlib.rst:49 +msgid "" +"Read a plist file. *fp* should be a readable and binary file object. Return " +"the unpacked root object (which usually is a dictionary)." +msgstr "" + +#: ../Doc/library/plistlib.rst:53 +msgid "The *fmt* is the format of the file and the following values are valid:" +msgstr "" + +#: ../Doc/library/plistlib.rst:55 +msgid ":data:`None`: Autodetect the file format" +msgstr "" + +#: ../Doc/library/plistlib.rst:57 +msgid ":data:`FMT_XML`: XML file format" +msgstr "" + +#: ../Doc/library/plistlib.rst:59 +msgid ":data:`FMT_BINARY`: Binary plist format" +msgstr "" + +#: ../Doc/library/plistlib.rst:61 +msgid "" +"If *use_builtin_types* is true (the default) binary data will be returned as " +"instances of :class:`bytes`, otherwise it is returned as instances of :class:" +"`Data`." +msgstr "" + +#: ../Doc/library/plistlib.rst:65 +msgid "" +"The *dict_type* is the type used for dictionaries that are read from the " +"plist file. The exact structure of the plist can be recovered by using :" +"class:`collections.OrderedDict` (although the order of keys shouldn't be " +"important in plist files)." +msgstr "" + +#: ../Doc/library/plistlib.rst:70 +msgid "" +"XML data for the :data:`FMT_XML` format is parsed using the Expat parser " +"from :mod:`xml.parsers.expat` -- see its documentation for possible " +"exceptions on ill-formed XML. Unknown elements will simply be ignored by " +"the plist parser." +msgstr "" + +#: ../Doc/library/plistlib.rst:75 +msgid "" +"The parser for the binary format raises :exc:`InvalidFileException` when the " +"file cannot be parsed." +msgstr "" + +#: ../Doc/library/plistlib.rst:83 +msgid "" +"Load a plist from a bytes object. See :func:`load` for an explanation of the " +"keyword arguments." +msgstr "" + +#: ../Doc/library/plistlib.rst:91 +msgid "" +"Write *value* to a plist file. *Fp* should be a writable, binary file object." +msgstr "" + +#: ../Doc/library/plistlib.rst:94 +msgid "" +"The *fmt* argument specifies the format of the plist file and can be one of " +"the following values:" +msgstr "" + +#: ../Doc/library/plistlib.rst:97 +msgid ":data:`FMT_XML`: XML formatted plist file" +msgstr "" + +#: ../Doc/library/plistlib.rst:99 +msgid ":data:`FMT_BINARY`: Binary formatted plist file" +msgstr "" + +#: ../Doc/library/plistlib.rst:101 +msgid "" +"When *sort_keys* is true (the default) the keys for dictionaries will be " +"written to the plist in sorted order, otherwise they will be written in the " +"iteration order of the dictionary." +msgstr "" + +#: ../Doc/library/plistlib.rst:105 +msgid "" +"When *skipkeys* is false (the default) the function raises :exc:`TypeError` " +"when a key of a dictionary is not a string, otherwise such keys are skipped." +msgstr "" + +#: ../Doc/library/plistlib.rst:108 +msgid "" +"A :exc:`TypeError` will be raised if the object is of an unsupported type or " +"a container that contains objects of unsupported types." +msgstr "" + +#: ../Doc/library/plistlib.rst:111 +msgid "" +"An :exc:`OverflowError` will be raised for integer values that cannot be " +"represented in (binary) plist files." +msgstr "" + +#: ../Doc/library/plistlib.rst:119 +msgid "" +"Return *value* as a plist-formatted bytes object. See the documentation for :" +"func:`dump` for an explanation of the keyword arguments of this function." +msgstr "" + +#: ../Doc/library/plistlib.rst:125 +msgid "The following functions are deprecated:" +msgstr "" + +#: ../Doc/library/plistlib.rst:129 +msgid "" +"Read a plist file. *pathOrFile* may be either a file name or a (readable and " +"binary) file object. Returns the unpacked root object (which usually is a " +"dictionary)." +msgstr "" + +#: ../Doc/library/plistlib.rst:133 +msgid "" +"This function calls :func:`load` to do the actual work, see the " +"documentation of :func:`that function ` for an explanation of the " +"keyword arguments." +msgstr "" + +#: ../Doc/library/plistlib.rst:138 ../Doc/library/plistlib.rst:161 +msgid "" +"Dict values in the result have a ``__getattr__`` method that defers to " +"``__getitem_``. This means that you can use attribute access to access items " +"of these dictionaries." +msgstr "" + +#: ../Doc/library/plistlib.rst:142 +msgid "Use :func:`load` instead." +msgstr "" + +#: ../Doc/library/plistlib.rst:147 +msgid "" +"Write *rootObject* to an XML plist file. *pathOrFile* may be either a file " +"name or a (writable and binary) file object" +msgstr "" + +#: ../Doc/library/plistlib.rst:150 +msgid "Use :func:`dump` instead." +msgstr "" + +#: ../Doc/library/plistlib.rst:155 +msgid "Read a plist data from a bytes object. Return the root object." +msgstr "" + +#: ../Doc/library/plistlib.rst:157 +msgid "See :func:`load` for a description of the keyword arguments." +msgstr "" + +#: ../Doc/library/plistlib.rst:165 +msgid "Use :func:`loads` instead." +msgstr "" + +#: ../Doc/library/plistlib.rst:170 +msgid "Return *rootObject* as an XML plist-formatted bytes object." +msgstr "" + +#: ../Doc/library/plistlib.rst:172 +msgid "Use :func:`dumps` instead." +msgstr "" + +#: ../Doc/library/plistlib.rst:175 +msgid "The following classes are available:" +msgstr "" + +#: ../Doc/library/plistlib.rst:179 +msgid "" +"Return an extended mapping object with the same value as dictionary *dict*." +msgstr "" + +#: ../Doc/library/plistlib.rst:182 +msgid "" +"This class is a subclass of :class:`dict` where attribute access can be used " +"to access items. That is, ``aDict.key`` is the same as ``aDict['key']`` for " +"getting, setting and deleting items in the mapping." +msgstr "" + +#: ../Doc/library/plistlib.rst:191 +msgid "" +"Return a \"data\" wrapper object around the bytes object *data*. This is " +"used in functions converting from/to plists to represent the ```` type " +"available in plists." +msgstr "" + +#: ../Doc/library/plistlib.rst:195 +msgid "" +"It has one attribute, :attr:`data`, that can be used to retrieve the Python " +"bytes object stored in it." +msgstr "" + +#: ../Doc/library/plistlib.rst:198 +msgid "Use a :class:`bytes` object instead." +msgstr "" + +#: ../Doc/library/plistlib.rst:201 +msgid "The following constants are available:" +msgstr "" + +#: ../Doc/library/plistlib.rst:205 +msgid "The XML format for plist files." +msgstr "" + +#: ../Doc/library/plistlib.rst:212 +msgid "The binary format for plist files" +msgstr "" + +#: ../Doc/library/plistlib.rst:220 +msgid "Generating a plist::" +msgstr "" + +#: ../Doc/library/plistlib.rst:240 +msgid "Parsing a plist::" +msgstr "" + +#: ../Doc/library/poplib.rst:2 +msgid ":mod:`poplib` --- POP3 protocol client" +msgstr "" + +#: ../Doc/library/poplib.rst:10 +msgid "**Source code:** :source:`Lib/poplib.py`" +msgstr "" + +#: ../Doc/library/poplib.rst:16 +msgid "" +"This module defines a class, :class:`POP3`, which encapsulates a connection " +"to a POP3 server and implements the protocol as defined in :rfc:`1939`. The :" +"class:`POP3` class supports both the minimal and optional command sets from :" +"rfc:`1939`. The :class:`POP3` class also supports the ``STLS`` command " +"introduced in :rfc:`2595` to enable encrypted communication on an already " +"established connection." +msgstr "" + +#: ../Doc/library/poplib.rst:22 +msgid "" +"Additionally, this module provides a class :class:`POP3_SSL`, which provides " +"support for connecting to POP3 servers that use SSL as an underlying " +"protocol layer." +msgstr "" + +#: ../Doc/library/poplib.rst:26 +msgid "" +"Note that POP3, though widely supported, is obsolescent. The implementation " +"quality of POP3 servers varies widely, and too many are quite poor. If your " +"mailserver supports IMAP, you would be better off using the :class:`imaplib." +"IMAP4` class, as IMAP servers tend to be better implemented." +msgstr "" + +#: ../Doc/library/poplib.rst:31 +msgid "The :mod:`poplib` module provides two classes:" +msgstr "" + +#: ../Doc/library/poplib.rst:36 +msgid "" +"This class implements the actual POP3 protocol. The connection is created " +"when the instance is initialized. If *port* is omitted, the standard POP3 " +"port (110) is used. The optional *timeout* parameter specifies a timeout in " +"seconds for the connection attempt (if not specified, the global default " +"timeout setting will be used)." +msgstr "" + +#: ../Doc/library/poplib.rst:45 +msgid "" +"This is a subclass of :class:`POP3` that connects to the server over an SSL " +"encrypted socket. If *port* is not specified, 995, the standard POP3-over-" +"SSL port is used. *timeout* works as in the :class:`POP3` constructor. " +"*context* is an optional :class:`ssl.SSLContext` object which allows " +"bundling SSL configuration options, certificates and private keys into a " +"single (potentially long-lived) structure. Please read :ref:`ssl-security` " +"for best practices." +msgstr "" + +#: ../Doc/library/poplib.rst:53 +msgid "" +"*keyfile* and *certfile* are a legacy alternative to *context* - they can " +"point to PEM-formatted private key and certificate chain files, " +"respectively, for the SSL connection." +msgstr "" + +#: ../Doc/library/poplib.rst:57 +msgid "*context* parameter added." +msgstr "" + +#: ../Doc/library/poplib.rst:72 +msgid "One exception is defined as an attribute of the :mod:`poplib` module:" +msgstr "" + +#: ../Doc/library/poplib.rst:77 +msgid "" +"Exception raised on any errors from this module (errors from :mod:`socket` " +"module are not caught). The reason for the exception is passed to the " +"constructor as a string." +msgstr "" + +#: ../Doc/library/poplib.rst:85 +msgid "The standard Python IMAP module." +msgstr "" + +#: ../Doc/library/poplib.rst:89 +msgid "" +"`Frequently Asked Questions About Fetchmail `_" +msgstr "" + +#: ../Doc/library/poplib.rst:88 +msgid "" +"The FAQ for the :program:`fetchmail` POP/IMAP client collects information on " +"POP3 server variations and RFC noncompliance that may be useful if you need " +"to write an application based on the POP protocol." +msgstr "" + +#: ../Doc/library/poplib.rst:96 +msgid "POP3 Objects" +msgstr "" + +#: ../Doc/library/poplib.rst:98 +msgid "" +"All POP3 commands are represented by methods of the same name, in lower-" +"case; most return the response text sent by the server." +msgstr "" + +#: ../Doc/library/poplib.rst:101 +msgid "An :class:`POP3` instance has the following methods:" +msgstr "" + +#: ../Doc/library/poplib.rst:115 +msgid "Returns the greeting string sent by the POP3 server." +msgstr "" + +#: ../Doc/library/poplib.rst:120 +msgid "" +"Query the server's capabilities as specified in :rfc:`2449`. Returns a " +"dictionary in the form ``{'name': ['param'...]}``." +msgstr "" + +#: ../Doc/library/poplib.rst:128 +msgid "" +"Send user command, response should indicate that a password is required." +msgstr "" + +#: ../Doc/library/poplib.rst:133 +msgid "" +"Send password, response includes message count and mailbox size. Note: the " +"mailbox on the server is locked until :meth:`~poplib.quit` is called." +msgstr "" + +#: ../Doc/library/poplib.rst:139 +msgid "Use the more secure APOP authentication to log into the POP3 server." +msgstr "" + +#: ../Doc/library/poplib.rst:144 +msgid "" +"Use RPOP authentication (similar to UNIX r-commands) to log into POP3 server." +msgstr "" + +#: ../Doc/library/poplib.rst:149 +msgid "" +"Get mailbox status. The result is a tuple of 2 integers: ``(message count, " +"mailbox size)``." +msgstr "" + +#: ../Doc/library/poplib.rst:155 +msgid "" +"Request message list, result is in the form ``(response, ['mesg_num " +"octets', ...], octets)``. If *which* is set, it is the message to list." +msgstr "" + +#: ../Doc/library/poplib.rst:161 +msgid "" +"Retrieve whole message number *which*, and set its seen flag. Result is in " +"form ``(response, ['line', ...], octets)``." +msgstr "" + +#: ../Doc/library/poplib.rst:167 +msgid "" +"Flag message number *which* for deletion. On most servers deletions are not " +"actually performed until QUIT (the major exception is Eudora QPOP, which " +"deliberately violates the RFCs by doing pending deletes on any disconnect)." +msgstr "" + +#: ../Doc/library/poplib.rst:174 +msgid "Remove any deletion marks for the mailbox." +msgstr "" + +#: ../Doc/library/poplib.rst:179 +msgid "Do nothing. Might be used as a keep-alive." +msgstr "" + +#: ../Doc/library/poplib.rst:184 +msgid "Signoff: commit changes, unlock mailbox, drop connection." +msgstr "" + +#: ../Doc/library/poplib.rst:189 +msgid "" +"Retrieves the message header plus *howmuch* lines of the message after the " +"header of message number *which*. Result is in form ``(response, " +"['line', ...], octets)``." +msgstr "" + +#: ../Doc/library/poplib.rst:193 +msgid "" +"The POP3 TOP command this method uses, unlike the RETR command, doesn't set " +"the message's seen flag; unfortunately, TOP is poorly specified in the RFCs " +"and is frequently broken in off-brand servers. Test this method by hand " +"against the POP3 servers you will use before trusting it." +msgstr "" + +#: ../Doc/library/poplib.rst:201 +msgid "" +"Return message digest (unique id) list. If *which* is specified, result " +"contains the unique id for that message in the form ``'response mesgnum " +"uid``, otherwise result is list ``(response, ['mesgnum uid', ...], octets)``." +msgstr "" + +#: ../Doc/library/poplib.rst:208 +msgid "" +"Try to switch to UTF-8 mode. Returns the server response if successful, " +"raises :class:`error_proto` if not. Specified in :RFC:`6856`." +msgstr "" + +#: ../Doc/library/poplib.rst:216 +msgid "" +"Start a TLS session on the active connection as specified in :rfc:`2595`. " +"This is only allowed before user authentication" +msgstr "" + +#: ../Doc/library/poplib.rst:219 +msgid "" +"*context* parameter is a :class:`ssl.SSLContext` object which allows " +"bundling SSL configuration options, certificates and private keys into a " +"single (potentially long-lived) structure. Please read :ref:`ssl-security` " +"for best practices." +msgstr "" + +#: ../Doc/library/poplib.rst:224 +msgid "" +"This method supports hostname checking via :attr:`ssl.SSLContext." +"check_hostname` and *Server Name Indication* (see :data:`ssl.HAS_SNI`)." +msgstr "" + +#: ../Doc/library/poplib.rst:231 +msgid "" +"Instances of :class:`POP3_SSL` have no additional methods. The interface of " +"this subclass is identical to its parent." +msgstr "" + +#: ../Doc/library/poplib.rst:238 +msgid "POP3 Example" +msgstr "" + +#: ../Doc/library/posix.rst:2 +msgid ":mod:`posix` --- The most common POSIX system calls" +msgstr "" + +#: ../Doc/library/posix.rst:10 +msgid "" +"This module provides access to operating system functionality that is " +"standardized by the C Standard and the POSIX standard (a thinly disguised " +"Unix interface)." +msgstr "" + +#: ../Doc/library/posix.rst:16 +msgid "" +"**Do not import this module directly.** Instead, import the module :mod:" +"`os`, which provides a *portable* version of this interface. On Unix, the :" +"mod:`os` module provides a superset of the :mod:`posix` interface. On non-" +"Unix operating systems the :mod:`posix` module is not available, but a " +"subset is always available through the :mod:`os` interface. Once :mod:`os` " +"is imported, there is *no* performance penalty in using it instead of :mod:" +"`posix`. In addition, :mod:`os` provides some additional functionality, " +"such as automatically calling :func:`~os.putenv` when an entry in ``os." +"environ`` is changed." +msgstr "" + +#: ../Doc/library/posix.rst:25 +msgid "" +"Errors are reported as exceptions; the usual exceptions are given for type " +"errors, while errors reported by the system calls raise :exc:`OSError`." +msgstr "" + +#: ../Doc/library/posix.rst:32 +msgid "Large File Support" +msgstr "" + +#: ../Doc/library/posix.rst:40 +msgid "" +"Several operating systems (including AIX, HP-UX, Irix and Solaris) provide " +"support for files that are larger than 2 GiB from a C programming model " +"where :c:type:`int` and :c:type:`long` are 32-bit values. This is typically " +"accomplished by defining the relevant size and offset types as 64-bit " +"values. Such files are sometimes referred to as :dfn:`large files`." +msgstr "" + +#: ../Doc/library/posix.rst:46 +msgid "" +"Large file support is enabled in Python when the size of an :c:type:`off_t` " +"is larger than a :c:type:`long` and the :c:type:`long long` type is " +"available and is at least as large as an :c:type:`off_t`. It may be " +"necessary to configure and compile Python with certain compiler flags to " +"enable this mode. For example, it is enabled by default with recent versions " +"of Irix, but with Solaris 2.6 and 2.7 you need to do something like::" +msgstr "" + +#: ../Doc/library/posix.rst:56 +msgid "On large-file-capable Linux systems, this might work::" +msgstr "" + +#: ../Doc/library/posix.rst:65 +msgid "Notable Module Contents" +msgstr "" + +#: ../Doc/library/posix.rst:67 +msgid "" +"In addition to many functions described in the :mod:`os` module " +"documentation, :mod:`posix` defines the following data item:" +msgstr "" + +#: ../Doc/library/posix.rst:72 +msgid "" +"A dictionary representing the string environment at the time the interpreter " +"was started. Keys and values are bytes on Unix and str on Windows. For " +"example, ``environ[b'HOME']`` (``environ['HOME']`` on Windows) is the " +"pathname of your home directory, equivalent to ``getenv(\"HOME\")`` in C." +msgstr "" + +#: ../Doc/library/posix.rst:77 +msgid "" +"Modifying this dictionary does not affect the string environment passed on " +"by :func:`~os.execv`, :func:`~os.popen` or :func:`~os.system`; if you need " +"to change the environment, pass ``environ`` to :func:`~os.execve` or add " +"variable assignments and export statements to the command string for :func:" +"`~os.system` or :func:`~os.popen`." +msgstr "" + +#: ../Doc/library/posix.rst:83 +msgid "On Unix, keys and values are bytes." +msgstr "" + +#: ../Doc/library/posix.rst:88 +msgid "" +"The :mod:`os` module provides an alternate implementation of ``environ`` " +"which updates the environment on modification. Note also that updating :data:" +"`os.environ` will render this dictionary obsolete. Use of the :mod:`os` " +"module version of this is recommended over direct access to the :mod:`posix` " +"module." +msgstr "" + +#: ../Doc/library/pprint.rst:2 +msgid ":mod:`pprint` --- Data pretty printer" +msgstr "" + +#: ../Doc/library/pprint.rst:10 +msgid "**Source code:** :source:`Lib/pprint.py`" +msgstr "" + +#: ../Doc/library/pprint.rst:14 +msgid "" +"The :mod:`pprint` module provides a capability to \"pretty-print\" arbitrary " +"Python data structures in a form which can be used as input to the " +"interpreter. If the formatted structures include objects which are not " +"fundamental Python types, the representation may not be loadable. This may " +"be the case if objects such as files, sockets or classes are included, as " +"well as many other objects which are not representable as Python literals." +msgstr "" + +#: ../Doc/library/pprint.rst:21 +msgid "" +"The formatted representation keeps objects on a single line if it can, and " +"breaks them onto multiple lines if they don't fit within the allowed width. " +"Construct :class:`PrettyPrinter` objects explicitly if you need to adjust " +"the width constraint." +msgstr "" + +#: ../Doc/library/pprint.rst:26 +msgid "Dictionaries are sorted by key before the display is computed." +msgstr "" + +#: ../Doc/library/pprint.rst:28 +msgid "The :mod:`pprint` module defines one class:" +msgstr "" + +#: ../Doc/library/pprint.rst:36 +msgid "" +"Construct a :class:`PrettyPrinter` instance. This constructor understands " +"several keyword parameters. An output stream may be set using the *stream* " +"keyword; the only method used on the stream object is the file protocol's :" +"meth:`write` method. If not specified, the :class:`PrettyPrinter` adopts " +"``sys.stdout``. The amount of indentation added for each recursive level is " +"specified by *indent*; the default is one. Other values can cause output to " +"look a little odd, but can make nesting easier to spot. The number of " +"levels which may be printed is controlled by *depth*; if the data structure " +"being printed is too deep, the next contained level is replaced by ``...``. " +"By default, there is no constraint on the depth of the objects being " +"formatted. The desired output width is constrained using the *width* " +"parameter; the default is 80 characters. If a structure cannot be formatted " +"within the constrained width, a best effort will be made. If *compact* is " +"false (the default) each item of a long sequence will be formatted on a " +"separate line. If *compact* is true, as many items as will fit within the " +"*width* will be formatted on each output line." +msgstr "" + +#: ../Doc/library/pprint.rst:53 ../Doc/library/pprint.rst:88 +#: ../Doc/library/pprint.rst:102 +msgid "Added the *compact* parameter." +msgstr "" + +#: ../Doc/library/pprint.rst:80 +msgid "The :mod:`pprint` module also provides several shortcut functions:" +msgstr "" + +#: ../Doc/library/pprint.rst:84 +msgid "" +"Return the formatted representation of *object* as a string. *indent*, " +"*width*, *depth* and *compact* will be passed to the :class:`PrettyPrinter` " +"constructor as formatting parameters." +msgstr "" + +#: ../Doc/library/pprint.rst:95 +msgid "" +"Prints the formatted representation of *object* on *stream*, followed by a " +"newline. If *stream* is ``None``, ``sys.stdout`` is used. This may be used " +"in the interactive interpreter instead of the :func:`print` function for " +"inspecting values (you can even reassign ``print = pprint.pprint`` for use " +"within a scope). *indent*, *width*, *depth* and *compact* will be passed to " +"the :class:`PrettyPrinter` constructor as formatting parameters." +msgstr "" + +#: ../Doc/library/pprint.rst:121 +msgid "" +"Determine if the formatted representation of *object* is \"readable,\" or " +"can be used to reconstruct the value using :func:`eval`. This always " +"returns ``False`` for recursive objects." +msgstr "" + +#: ../Doc/library/pprint.rst:131 +msgid "Determine if *object* requires a recursive representation." +msgstr "" + +#: ../Doc/library/pprint.rst:134 +msgid "One more support function is also defined:" +msgstr "" + +#: ../Doc/library/pprint.rst:138 +msgid "" +"Return a string representation of *object*, protected against recursive data " +"structures. If the representation of *object* exposes a recursive entry, " +"the recursive reference will be represented as ````. The representation is not otherwise formatted." +msgstr "" + +#: ../Doc/library/pprint.rst:150 +msgid "PrettyPrinter Objects" +msgstr "" + +#: ../Doc/library/pprint.rst:152 +msgid ":class:`PrettyPrinter` instances have the following methods:" +msgstr "" + +#: ../Doc/library/pprint.rst:157 +msgid "" +"Return the formatted representation of *object*. This takes into account " +"the options passed to the :class:`PrettyPrinter` constructor." +msgstr "" + +#: ../Doc/library/pprint.rst:163 +msgid "" +"Print the formatted representation of *object* on the configured stream, " +"followed by a newline." +msgstr "" + +#: ../Doc/library/pprint.rst:166 +msgid "" +"The following methods provide the implementations for the corresponding " +"functions of the same names. Using these methods on an instance is slightly " +"more efficient since new :class:`PrettyPrinter` objects don't need to be " +"created." +msgstr "" + +#: ../Doc/library/pprint.rst:176 +msgid "" +"Determine if the formatted representation of the object is \"readable,\" or " +"can be used to reconstruct the value using :func:`eval`. Note that this " +"returns ``False`` for recursive objects. If the *depth* parameter of the :" +"class:`PrettyPrinter` is set and the object is deeper than allowed, this " +"returns ``False``." +msgstr "" + +#: ../Doc/library/pprint.rst:185 +msgid "Determine if the object requires a recursive representation." +msgstr "" + +#: ../Doc/library/pprint.rst:187 +msgid "" +"This method is provided as a hook to allow subclasses to modify the way " +"objects are converted to strings. The default implementation uses the " +"internals of the :func:`saferepr` implementation." +msgstr "" + +#: ../Doc/library/pprint.rst:194 +msgid "" +"Returns three values: the formatted version of *object* as a string, a flag " +"indicating whether the result is readable, and a flag indicating whether " +"recursion was detected. The first argument is the object to be presented. " +"The second is a dictionary which contains the :func:`id` of objects that are " +"part of the current presentation context (direct and indirect containers for " +"*object* that are affecting the presentation) as the keys; if an object " +"needs to be presented which is already represented in *context*, the third " +"return value should be ``True``. Recursive calls to the :meth:`.format` " +"method should add additional entries for containers to this dictionary. The " +"third argument, *maxlevels*, gives the requested limit to recursion; this " +"will be ``0`` if there is no requested limit. This argument should be " +"passed unmodified to recursive calls. The fourth argument, *level*, gives " +"the current level; recursive calls should be passed a value less than that " +"of the current call." +msgstr "" + +#: ../Doc/library/pprint.rst:214 +msgid "" +"To demonstrate several uses of the :func:`pprint` function and its " +"parameters, let's fetch information about a project from `PyPI `_::" +msgstr "" + +#: ../Doc/library/pprint.rst:225 +msgid "In its basic form, :func:`pprint` shows the whole object::" +msgstr "" + +#: ../Doc/library/pprint.rst:279 +msgid "" +"The result can be limited to a certain *depth* (ellipsis is used for deeper " +"contents)::" +msgstr "" + +#: ../Doc/library/pprint.rst:313 +msgid "" +"Additionally, maximum character *width* can be suggested. If a long object " +"cannot be split, the specified width will be exceeded::" +msgstr "" + +#: ../Doc/library/profile.rst:5 +msgid "The Python Profilers" +msgstr "" + +#: ../Doc/library/profile.rst:7 +msgid "**Source code:** :source:`Lib/profile.py` and :source:`Lib/pstats.py`" +msgstr "" + +#: ../Doc/library/profile.rst:14 +msgid "Introduction to the profilers" +msgstr "" + +#: ../Doc/library/profile.rst:20 +msgid "" +":mod:`cProfile` and :mod:`profile` provide :dfn:`deterministic profiling` of " +"Python programs. A :dfn:`profile` is a set of statistics that describes how " +"often and for how long various parts of the program executed. These " +"statistics can be formatted into reports via the :mod:`pstats` module." +msgstr "" + +#: ../Doc/library/profile.rst:25 +msgid "" +"The Python standard library provides two different implementations of the " +"same profiling interface:" +msgstr "" + +#: ../Doc/library/profile.rst:28 +msgid "" +":mod:`cProfile` is recommended for most users; it's a C extension with " +"reasonable overhead that makes it suitable for profiling long-running " +"programs. Based on :mod:`lsprof`, contributed by Brett Rosen and Ted " +"Czotter." +msgstr "" + +#: ../Doc/library/profile.rst:33 +msgid "" +":mod:`profile`, a pure Python module whose interface is imitated by :mod:" +"`cProfile`, but which adds significant overhead to profiled programs. If " +"you're trying to extend the profiler in some way, the task might be easier " +"with this module. Originally designed and written by Jim Roskind." +msgstr "" + +#: ../Doc/library/profile.rst:40 +msgid "" +"The profiler modules are designed to provide an execution profile for a " +"given program, not for benchmarking purposes (for that, there is :mod:" +"`timeit` for reasonably accurate results). This particularly applies to " +"benchmarking Python code against C code: the profilers introduce overhead " +"for Python code, but not for C-level functions, and so the C code would seem " +"faster than any Python one." +msgstr "" + +#: ../Doc/library/profile.rst:51 +msgid "Instant User's Manual" +msgstr "" + +#: ../Doc/library/profile.rst:53 +msgid "" +"This section is provided for users that \"don't want to read the manual.\" " +"It provides a very brief overview, and allows a user to rapidly perform " +"profiling on an existing application." +msgstr "" + +#: ../Doc/library/profile.rst:57 +msgid "To profile a function that takes a single argument, you can do::" +msgstr "" + +#: ../Doc/library/profile.rst:63 +msgid "" +"(Use :mod:`profile` instead of :mod:`cProfile` if the latter is not " +"available on your system.)" +msgstr "" + +#: ../Doc/library/profile.rst:66 +msgid "" +"The above action would run :func:`re.compile` and print profile results like " +"the following::" +msgstr "" + +#: ../Doc/library/profile.rst:82 +msgid "" +"The first line indicates that 197 calls were monitored. Of those calls, 192 " +"were :dfn:`primitive`, meaning that the call was not induced via recursion. " +"The next line: ``Ordered by: standard name``, indicates that the text string " +"in the far right column was used to sort the output. The column headings " +"include:" +msgstr "" + +#: ../Doc/library/profile.rst:88 +msgid "ncalls" +msgstr "" + +#: ../Doc/library/profile.rst:88 +msgid "for the number of calls," +msgstr "" + +#: ../Doc/library/profile.rst:92 +msgid "tottime" +msgstr "" + +#: ../Doc/library/profile.rst:91 +msgid "" +"for the total time spent in the given function (and excluding time made in " +"calls to sub-functions)" +msgstr "" + +#: ../Doc/library/profile.rst:95 ../Doc/library/profile.rst:102 +msgid "percall" +msgstr "" + +#: ../Doc/library/profile.rst:95 +msgid "is the quotient of ``tottime`` divided by ``ncalls``" +msgstr "" + +#: ../Doc/library/profile.rst:99 +msgid "cumtime" +msgstr "" + +#: ../Doc/library/profile.rst:98 +msgid "" +"is the cumulative time spent in this and all subfunctions (from invocation " +"till exit). This figure is accurate *even* for recursive functions." +msgstr "" + +#: ../Doc/library/profile.rst:102 +msgid "is the quotient of ``cumtime`` divided by primitive calls" +msgstr "" + +#: ../Doc/library/profile.rst:105 +msgid "filename:lineno(function)" +msgstr "" + +#: ../Doc/library/profile.rst:105 +msgid "provides the respective data of each function" +msgstr "" + +#: ../Doc/library/profile.rst:107 +msgid "" +"When there are two numbers in the first column (for example ``3/1``), it " +"means that the function recursed. The second value is the number of " +"primitive calls and the former is the total number of calls. Note that when " +"the function does not recurse, these two values are the same, and only the " +"single figure is printed." +msgstr "" + +#: ../Doc/library/profile.rst:113 +msgid "" +"Instead of printing the output at the end of the profile run, you can save " +"the results to a file by specifying a filename to the :func:`run` function::" +msgstr "" + +#: ../Doc/library/profile.rst:120 +msgid "" +"The :class:`pstats.Stats` class reads profile results from a file and " +"formats them in various ways." +msgstr "" + +#: ../Doc/library/profile.rst:123 +msgid "" +"The file :mod:`cProfile` can also be invoked as a script to profile another " +"script. For example::" +msgstr "" + +#: ../Doc/library/profile.rst:128 +msgid "``-o`` writes the profile results to a file instead of to stdout" +msgstr "" + +#: ../Doc/library/profile.rst:130 +msgid "" +"``-s`` specifies one of the :func:`~pstats.Stats.sort_stats` sort values to " +"sort the output by. This only applies when ``-o`` is not supplied." +msgstr "" + +#: ../Doc/library/profile.rst:133 +msgid "" +"The :mod:`pstats` module's :class:`~pstats.Stats` class has a variety of " +"methods for manipulating and printing the data saved into a profile results " +"file::" +msgstr "" + +#: ../Doc/library/profile.rst:140 +msgid "" +"The :meth:`~pstats.Stats.strip_dirs` method removed the extraneous path from " +"all the module names. The :meth:`~pstats.Stats.sort_stats` method sorted all " +"the entries according to the standard module/line/name string that is " +"printed. The :meth:`~pstats.Stats.print_stats` method printed out all the " +"statistics. You might try the following sort calls::" +msgstr "" + +#: ../Doc/library/profile.rst:149 +msgid "" +"The first call will actually sort the list by function name, and the second " +"call will print out the statistics. The following are some interesting " +"calls to experiment with::" +msgstr "" + +#: ../Doc/library/profile.rst:155 +msgid "" +"This sorts the profile by cumulative time in a function, and then only " +"prints the ten most significant lines. If you want to understand what " +"algorithms are taking time, the above line is what you would use." +msgstr "" + +#: ../Doc/library/profile.rst:159 +msgid "" +"If you were looking to see what functions were looping a lot, and taking a " +"lot of time, you would do::" +msgstr "" + +#: ../Doc/library/profile.rst:164 +msgid "" +"to sort according to time spent within each function, and then print the " +"statistics for the top ten functions." +msgstr "" + +#: ../Doc/library/profile.rst:167 +msgid "You might also try::" +msgstr "" + +#: ../Doc/library/profile.rst:171 +msgid "" +"This will sort all the statistics by file name, and then print out " +"statistics for only the class init methods (since they are spelled with " +"``__init__`` in them). As one final example, you could try::" +msgstr "" + +#: ../Doc/library/profile.rst:177 +msgid "" +"This line sorts statistics with a primary key of time, and a secondary key " +"of cumulative time, and then prints out some of the statistics. To be " +"specific, the list is first culled down to 50% (re: ``.5``) of its original " +"size, then only lines containing ``init`` are maintained, and that sub-sub-" +"list is printed." +msgstr "" + +#: ../Doc/library/profile.rst:182 +msgid "" +"If you wondered what functions called the above functions, you could now " +"(``p`` is still sorted according to the last criteria) do::" +msgstr "" + +#: ../Doc/library/profile.rst:187 +msgid "and you would get a list of callers for each of the listed functions." +msgstr "" + +#: ../Doc/library/profile.rst:189 +msgid "" +"If you want more functionality, you're going to have to read the manual, or " +"guess what the following functions do::" +msgstr "" + +#: ../Doc/library/profile.rst:195 +msgid "" +"Invoked as a script, the :mod:`pstats` module is a statistics browser for " +"reading and examining profile dumps. It has a simple line-oriented " +"interface (implemented using :mod:`cmd`) and interactive help." +msgstr "" + +#: ../Doc/library/profile.rst:200 +msgid ":mod:`profile` and :mod:`cProfile` Module Reference" +msgstr "" + +#: ../Doc/library/profile.rst:206 +msgid "" +"Both the :mod:`profile` and :mod:`cProfile` modules provide the following " +"functions:" +msgstr "" + +#: ../Doc/library/profile.rst:211 +msgid "" +"This function takes a single argument that can be passed to the :func:`exec` " +"function, and an optional file name. In all cases this routine executes::" +msgstr "" + +#: ../Doc/library/profile.rst:216 +msgid "" +"and gathers profiling statistics from the execution. If no file name is " +"present, then this function automatically creates a :class:`~pstats.Stats` " +"instance and prints a simple profiling report. If the sort value is " +"specified it is passed to this :class:`~pstats.Stats` instance to control " +"how the results are sorted." +msgstr "" + +#: ../Doc/library/profile.rst:224 +msgid "" +"This function is similar to :func:`run`, with added arguments to supply the " +"globals and locals dictionaries for the *command* string. This routine " +"executes::" +msgstr "" + +#: ../Doc/library/profile.rst:230 +msgid "and gathers profiling statistics as in the :func:`run` function above." +msgstr "" + +#: ../Doc/library/profile.rst:234 +msgid "" +"This class is normally only used if more precise control over profiling is " +"needed than what the :func:`cProfile.run` function provides." +msgstr "" + +#: ../Doc/library/profile.rst:237 +msgid "" +"A custom timer can be supplied for measuring how long code takes to run via " +"the *timer* argument. This must be a function that returns a single number " +"representing the current time. If the number is an integer, the *timeunit* " +"specifies a multiplier that specifies the duration of each unit of time. For " +"example, if the timer returns times measured in thousands of seconds, the " +"time unit would be ``.001``." +msgstr "" + +#: ../Doc/library/profile.rst:244 +msgid "" +"Directly using the :class:`Profile` class allows formatting profile results " +"without writing the profile data to a file::" +msgstr "" + +#: ../Doc/library/profile.rst:260 +msgid "Start collecting profiling data." +msgstr "" + +#: ../Doc/library/profile.rst:264 +msgid "Stop collecting profiling data." +msgstr "" + +#: ../Doc/library/profile.rst:268 +msgid "" +"Stop collecting profiling data and record the results internally as the " +"current profile." +msgstr "" + +#: ../Doc/library/profile.rst:273 +msgid "" +"Create a :class:`~pstats.Stats` object based on the current profile and " +"print the results to stdout." +msgstr "" + +#: ../Doc/library/profile.rst:278 +msgid "Write the results of the current profile to *filename*." +msgstr "" + +#: ../Doc/library/profile.rst:282 +msgid "Profile the cmd via :func:`exec`." +msgstr "" + +#: ../Doc/library/profile.rst:286 +msgid "" +"Profile the cmd via :func:`exec` with the specified global and local " +"environment." +msgstr "" + +#: ../Doc/library/profile.rst:291 +msgid "Profile ``func(*args, **kwargs)``" +msgstr "" + +#: ../Doc/library/profile.rst:296 +msgid "The :class:`Stats` Class" +msgstr "" + +#: ../Doc/library/profile.rst:298 +msgid "" +"Analysis of the profiler data is done using the :class:`~pstats.Stats` class." +msgstr "" + +#: ../Doc/library/profile.rst:305 +msgid "" +"This class constructor creates an instance of a \"statistics object\" from a " +"*filename* (or list of filenames) or from a :class:`Profile` instance. " +"Output will be printed to the stream specified by *stream*." +msgstr "" + +#: ../Doc/library/profile.rst:309 +msgid "" +"The file selected by the above constructor must have been created by the " +"corresponding version of :mod:`profile` or :mod:`cProfile`. To be specific, " +"there is *no* file compatibility guaranteed with future versions of this " +"profiler, and there is no compatibility with files produced by other " +"profilers. If several files are provided, all the statistics for identical " +"functions will be coalesced, so that an overall view of several processes " +"can be considered in a single report. If additional files need to be " +"combined with data in an existing :class:`~pstats.Stats` object, the :meth:" +"`~pstats.Stats.add` method can be used." +msgstr "" + +#: ../Doc/library/profile.rst:319 +msgid "" +"Instead of reading the profile data from a file, a :class:`cProfile.Profile` " +"or :class:`profile.Profile` object can be used as the profile data source." +msgstr "" + +#: ../Doc/library/profile.rst:322 +msgid ":class:`Stats` objects have the following methods:" +msgstr "" + +#: ../Doc/library/profile.rst:326 +msgid "" +"This method for the :class:`Stats` class removes all leading path " +"information from file names. It is very useful in reducing the size of the " +"printout to fit within (close to) 80 columns. This method modifies the " +"object, and the stripped information is lost. After performing a strip " +"operation, the object is considered to have its entries in a \"random\" " +"order, as it was just after object initialization and loading. If :meth:" +"`~pstats.Stats.strip_dirs` causes two function names to be indistinguishable " +"(they are on the same line of the same filename, and have the same function " +"name), then the statistics for these two entries are accumulated into a " +"single entry." +msgstr "" + +#: ../Doc/library/profile.rst:340 +msgid "" +"This method of the :class:`Stats` class accumulates additional profiling " +"information into the current profiling object. Its arguments should refer " +"to filenames created by the corresponding version of :func:`profile.run` or :" +"func:`cProfile.run`. Statistics for identically named (re: file, line, name) " +"functions are automatically accumulated into single function statistics." +msgstr "" + +#: ../Doc/library/profile.rst:350 +msgid "" +"Save the data loaded into the :class:`Stats` object to a file named " +"*filename*. The file is created if it does not exist, and is overwritten if " +"it already exists. This is equivalent to the method of the same name on " +"the :class:`profile.Profile` and :class:`cProfile.Profile` classes." +msgstr "" + +#: ../Doc/library/profile.rst:358 +msgid "" +"This method modifies the :class:`Stats` object by sorting it according to " +"the supplied criteria. The argument is typically a string identifying the " +"basis of a sort (example: ``'time'`` or ``'name'``)." +msgstr "" + +#: ../Doc/library/profile.rst:362 +msgid "" +"When more than one key is provided, then additional keys are used as " +"secondary criteria when there is equality in all keys selected before them. " +"For example, ``sort_stats('name', 'file')`` will sort all the entries " +"according to their function name, and resolve all ties (identical function " +"names) by sorting by file name." +msgstr "" + +#: ../Doc/library/profile.rst:368 +msgid "" +"Abbreviations can be used for any key names, as long as the abbreviation is " +"unambiguous. The following are the keys currently defined:" +msgstr "" + +#: ../Doc/library/profile.rst:372 +msgid "Valid Arg" +msgstr "" + +#: ../Doc/library/profile.rst:374 +msgid "``'calls'``" +msgstr "" + +#: ../Doc/library/profile.rst:374 ../Doc/library/profile.rst:386 +msgid "call count" +msgstr "" + +#: ../Doc/library/profile.rst:376 +msgid "``'cumulative'``" +msgstr "" + +#: ../Doc/library/profile.rst:376 ../Doc/library/profile.rst:378 +msgid "cumulative time" +msgstr "" + +#: ../Doc/library/profile.rst:378 +msgid "``'cumtime'``" +msgstr "" + +#: ../Doc/library/profile.rst:380 +msgid "``'file'``" +msgstr "" + +#: ../Doc/library/profile.rst:380 ../Doc/library/profile.rst:382 +#: ../Doc/library/profile.rst:384 +msgid "file name" +msgstr "" + +#: ../Doc/library/profile.rst:382 ../Doc/library/tracemalloc.rst:522 +msgid "``'filename'``" +msgstr "" + +#: ../Doc/library/profile.rst:384 +msgid "``'module'``" +msgstr "" + +#: ../Doc/library/profile.rst:386 +msgid "``'ncalls'``" +msgstr "" + +#: ../Doc/library/profile.rst:388 +msgid "``'pcalls'``" +msgstr "" + +#: ../Doc/library/profile.rst:388 +msgid "primitive call count" +msgstr "" + +#: ../Doc/library/profile.rst:390 ../Doc/library/sys.rst:1066 +msgid "``'line'``" +msgstr "" + +#: ../Doc/library/profile.rst:390 +msgid "line number" +msgstr "" + +#: ../Doc/library/profile.rst:392 +msgid "``'name'``" +msgstr "" + +#: ../Doc/library/profile.rst:392 +msgid "function name" +msgstr "" + +#: ../Doc/library/profile.rst:394 +msgid "``'nfl'``" +msgstr "" + +#: ../Doc/library/profile.rst:394 +msgid "name/file/line" +msgstr "" + +#: ../Doc/library/profile.rst:396 +msgid "``'stdname'``" +msgstr "" + +#: ../Doc/library/profile.rst:396 +msgid "standard name" +msgstr "" + +#: ../Doc/library/profile.rst:398 +msgid "``'time'``" +msgstr "" + +#: ../Doc/library/profile.rst:398 ../Doc/library/profile.rst:400 +msgid "internal time" +msgstr "" + +#: ../Doc/library/profile.rst:400 +msgid "``'tottime'``" +msgstr "" + +#: ../Doc/library/profile.rst:403 +msgid "" +"Note that all sorts on statistics are in descending order (placing most time " +"consuming items first), where as name, file, and line number searches are in " +"ascending order (alphabetical). The subtle distinction between ``'nfl'`` and " +"``'stdname'`` is that the standard name is a sort of the name as printed, " +"which means that the embedded line numbers get compared in an odd way. For " +"example, lines 3, 20, and 40 would (if the file names were the same) appear " +"in the string order 20, 3 and 40. In contrast, ``'nfl'`` does a numeric " +"compare of the line numbers. In fact, ``sort_stats('nfl')`` is the same as " +"``sort_stats('name', 'file', 'line')``." +msgstr "" + +#: ../Doc/library/profile.rst:414 +msgid "" +"For backward-compatibility reasons, the numeric arguments ``-1``, ``0``, " +"``1``, and ``2`` are permitted. They are interpreted as ``'stdname'``, " +"``'calls'``, ``'time'``, and ``'cumulative'`` respectively. If this old " +"style format (numeric) is used, only one sort key (the numeric key) will be " +"used, and additional arguments will be silently ignored." +msgstr "" + +#: ../Doc/library/profile.rst:425 +msgid "" +"This method for the :class:`Stats` class reverses the ordering of the basic " +"list within the object. Note that by default ascending vs descending order " +"is properly selected based on the sort key of choice." +msgstr "" + +#: ../Doc/library/profile.rst:435 +msgid "" +"This method for the :class:`Stats` class prints out a report as described in " +"the :func:`profile.run` definition." +msgstr "" + +#: ../Doc/library/profile.rst:438 +msgid "" +"The order of the printing is based on the last :meth:`~pstats.Stats." +"sort_stats` operation done on the object (subject to caveats in :meth:" +"`~pstats.Stats.add` and :meth:`~pstats.Stats.strip_dirs`)." +msgstr "" + +#: ../Doc/library/profile.rst:443 +msgid "" +"The arguments provided (if any) can be used to limit the list down to the " +"significant entries. Initially, the list is taken to be the complete set of " +"profiled functions. Each restriction is either an integer (to select a " +"count of lines), or a decimal fraction between 0.0 and 1.0 inclusive (to " +"select a percentage of lines), or a regular expression (to pattern match the " +"standard name that is printed. If several restrictions are provided, then " +"they are applied sequentially. For example::" +msgstr "" + +#: ../Doc/library/profile.rst:453 +msgid "" +"would first limit the printing to first 10% of list, and then only print " +"functions that were part of filename :file:`.\\*foo:`. In contrast, the " +"command::" +msgstr "" + +#: ../Doc/library/profile.rst:459 +msgid "" +"would limit the list to all functions having file names :file:`.\\*foo:`, " +"and then proceed to only print the first 10% of them." +msgstr "" + +#: ../Doc/library/profile.rst:465 +msgid "" +"This method for the :class:`Stats` class prints a list of all functions that " +"called each function in the profiled database. The ordering is identical to " +"that provided by :meth:`~pstats.Stats.print_stats`, and the definition of " +"the restricting argument is also identical. Each caller is reported on its " +"own line. The format differs slightly depending on the profiler that " +"produced the stats:" +msgstr "" + +#: ../Doc/library/profile.rst:472 +msgid "" +"With :mod:`profile`, a number is shown in parentheses after each caller to " +"show how many times this specific call was made. For convenience, a second " +"non-parenthesized number repeats the cumulative time spent in the function " +"at the right." +msgstr "" + +#: ../Doc/library/profile.rst:477 +msgid "" +"With :mod:`cProfile`, each caller is preceded by three numbers: the number " +"of times this specific call was made, and the total and cumulative times " +"spent in the current function while it was invoked by this specific caller." +msgstr "" + +#: ../Doc/library/profile.rst:485 +msgid "" +"This method for the :class:`Stats` class prints a list of all function that " +"were called by the indicated function. Aside from this reversal of " +"direction of calls (re: called vs was called by), the arguments and ordering " +"are identical to the :meth:`~pstats.Stats.print_callers` method." +msgstr "" + +#: ../Doc/library/profile.rst:494 +msgid "What Is Deterministic Profiling?" +msgstr "" + +#: ../Doc/library/profile.rst:496 +msgid "" +":dfn:`Deterministic profiling` is meant to reflect the fact that all " +"*function call*, *function return*, and *exception* events are monitored, " +"and precise timings are made for the intervals between these events (during " +"which time the user's code is executing). In contrast, :dfn:`statistical " +"profiling` (which is not done by this module) randomly samples the effective " +"instruction pointer, and deduces where time is being spent. The latter " +"technique traditionally involves less overhead (as the code does not need to " +"be instrumented), but provides only relative indications of where time is " +"being spent." +msgstr "" + +#: ../Doc/library/profile.rst:505 +msgid "" +"In Python, since there is an interpreter active during execution, the " +"presence of instrumented code is not required to do deterministic " +"profiling. Python automatically provides a :dfn:`hook` (optional callback) " +"for each event. In addition, the interpreted nature of Python tends to add " +"so much overhead to execution, that deterministic profiling tends to only " +"add small processing overhead in typical applications. The result is that " +"deterministic profiling is not that expensive, yet provides extensive run " +"time statistics about the execution of a Python program." +msgstr "" + +#: ../Doc/library/profile.rst:514 +msgid "" +"Call count statistics can be used to identify bugs in code (surprising " +"counts), and to identify possible inline-expansion points (high call " +"counts). Internal time statistics can be used to identify \"hot loops\" " +"that should be carefully optimized. Cumulative time statistics should be " +"used to identify high level errors in the selection of algorithms. Note " +"that the unusual handling of cumulative times in this profiler allows " +"statistics for recursive implementations of algorithms to be directly " +"compared to iterative implementations." +msgstr "" + +#: ../Doc/library/profile.rst:527 +msgid "Limitations" +msgstr "" + +#: ../Doc/library/profile.rst:529 +msgid "" +"One limitation has to do with accuracy of timing information. There is a " +"fundamental problem with deterministic profilers involving accuracy. The " +"most obvious restriction is that the underlying \"clock\" is only ticking at " +"a rate (typically) of about .001 seconds. Hence no measurements will be " +"more accurate than the underlying clock. If enough measurements are taken, " +"then the \"error\" will tend to average out. Unfortunately, removing this " +"first error induces a second source of error." +msgstr "" + +#: ../Doc/library/profile.rst:537 +msgid "" +"The second problem is that it \"takes a while\" from when an event is " +"dispatched until the profiler's call to get the time actually *gets* the " +"state of the clock. Similarly, there is a certain lag when exiting the " +"profiler event handler from the time that the clock's value was obtained " +"(and then squirreled away), until the user's code is once again executing. " +"As a result, functions that are called many times, or call many functions, " +"will typically accumulate this error. The error that accumulates in this " +"fashion is typically less than the accuracy of the clock (less than one " +"clock tick), but it *can* accumulate and become very significant." +msgstr "" + +#: ../Doc/library/profile.rst:547 +msgid "" +"The problem is more important with :mod:`profile` than with the lower-" +"overhead :mod:`cProfile`. For this reason, :mod:`profile` provides a means " +"of calibrating itself for a given platform so that this error can be " +"probabilistically (on the average) removed. After the profiler is " +"calibrated, it will be more accurate (in a least square sense), but it will " +"sometimes produce negative numbers (when call counts are exceptionally low, " +"and the gods of probability work against you :-). ) Do *not* be alarmed by " +"negative numbers in the profile. They should *only* appear if you have " +"calibrated your profiler, and the results are actually better than without " +"calibration." +msgstr "" + +#: ../Doc/library/profile.rst:561 +msgid "Calibration" +msgstr "" + +#: ../Doc/library/profile.rst:563 +msgid "" +"The profiler of the :mod:`profile` module subtracts a constant from each " +"event handling time to compensate for the overhead of calling the time " +"function, and socking away the results. By default, the constant is 0. The " +"following procedure can be used to obtain a better constant for a given " +"platform (see :ref:`profile-limitations`). ::" +msgstr "" + +#: ../Doc/library/profile.rst:574 +msgid "" +"The method executes the number of Python calls given by the argument, " +"directly and again under the profiler, measuring the time for both. It then " +"computes the hidden overhead per profiler event, and returns that as a " +"float. For example, on a 1.8Ghz Intel Core i5 running Mac OS X, and using " +"Python's time.clock() as the timer, the magical number is about 4.04e-6." +msgstr "" + +#: ../Doc/library/profile.rst:580 +msgid "" +"The object of this exercise is to get a fairly consistent result. If your " +"computer is *very* fast, or your timer function has poor resolution, you " +"might have to pass 100000, or even 1000000, to get consistent results." +msgstr "" + +#: ../Doc/library/profile.rst:584 +msgid "" +"When you have a consistent answer, there are three ways you can use it::" +msgstr "" + +#: ../Doc/library/profile.rst:598 +msgid "" +"If you have a choice, you are better off choosing a smaller constant, and " +"then your results will \"less often\" show up as negative in profile " +"statistics." +msgstr "" + +#: ../Doc/library/profile.rst:604 +msgid "Using a custom timer" +msgstr "" + +#: ../Doc/library/profile.rst:606 +msgid "" +"If you want to change how current time is determined (for example, to force " +"use of wall-clock time or elapsed process time), pass the timing function " +"you want to the :class:`Profile` class constructor::" +msgstr "" + +#: ../Doc/library/profile.rst:612 +msgid "" +"The resulting profiler will then call ``your_time_func``. Depending on " +"whether you are using :class:`profile.Profile` or :class:`cProfile.Profile`, " +"``your_time_func``'s return value will be interpreted differently:" +msgstr "" + +#: ../Doc/library/profile.rst:630 +msgid ":class:`profile.Profile`" +msgstr "" + +#: ../Doc/library/profile.rst:617 +msgid "" +"``your_time_func`` should return a single number, or a list of numbers whose " +"sum is the current time (like what :func:`os.times` returns). If the " +"function returns a single time number, or the list of returned numbers has " +"length 2, then you will get an especially fast version of the dispatch " +"routine." +msgstr "" + +#: ../Doc/library/profile.rst:623 +msgid "" +"Be warned that you should calibrate the profiler class for the timer " +"function that you choose (see :ref:`profile-calibration`). For most " +"machines, a timer that returns a lone integer value will provide the best " +"results in terms of low overhead during profiling. (:func:`os.times` is " +"*pretty* bad, as it returns a tuple of floating point values). If you want " +"to substitute a better timer in the cleanest fashion, derive a class and " +"hardwire a replacement dispatch method that best handles your timer call, " +"along with the appropriate calibration constant." +msgstr "" + +#: ../Doc/library/profile.rst:644 +msgid ":class:`cProfile.Profile`" +msgstr "" + +#: ../Doc/library/profile.rst:633 +msgid "" +"``your_time_func`` should return a single number. If it returns integers, " +"you can also invoke the class constructor with a second argument specifying " +"the real duration of one unit of time. For example, if " +"``your_integer_time_func`` returns times measured in thousands of seconds, " +"you would construct the :class:`Profile` instance as follows::" +msgstr "" + +#: ../Doc/library/profile.rst:641 +msgid "" +"As the :class:`cProfile.Profile` class cannot be calibrated, custom timer " +"functions should be used with care and should be as fast as possible. For " +"the best results with a custom timer, it might be necessary to hard-code it " +"in the C source of the internal :mod:`_lsprof` module." +msgstr "" + +#: ../Doc/library/profile.rst:646 +msgid "" +"Python 3.3 adds several new functions in :mod:`time` that can be used to " +"make precise measurements of process or wall-clock time. For example, see :" +"func:`time.perf_counter`." +msgstr "" + +#: ../Doc/library/pty.rst:2 +msgid ":mod:`pty` --- Pseudo-terminal utilities" +msgstr "" + +#: ../Doc/library/pty.rst:11 +msgid "**Source code:** :source:`Lib/pty.py`" +msgstr "" + +#: ../Doc/library/pty.rst:15 +msgid "" +"The :mod:`pty` module defines operations for handling the pseudo-terminal " +"concept: starting another process and being able to write to and read from " +"its controlling terminal programmatically." +msgstr "" + +#: ../Doc/library/pty.rst:19 +msgid "" +"Because pseudo-terminal handling is highly platform dependent, there is code " +"to do it only for Linux. (The Linux code is supposed to work on other " +"platforms, but hasn't been tested yet.)" +msgstr "" + +#: ../Doc/library/pty.rst:23 +msgid "The :mod:`pty` module defines the following functions:" +msgstr "" + +#: ../Doc/library/pty.rst:28 +msgid "" +"Fork. Connect the child's controlling terminal to a pseudo-terminal. Return " +"value is ``(pid, fd)``. Note that the child gets *pid* 0, and the *fd* is " +"*invalid*. The parent's return value is the *pid* of the child, and *fd* is " +"a file descriptor connected to the child's controlling terminal (and also to " +"the child's standard input and output)." +msgstr "" + +#: ../Doc/library/pty.rst:37 +msgid "" +"Open a new pseudo-terminal pair, using :func:`os.openpty` if possible, or " +"emulation code for generic Unix systems. Return a pair of file descriptors " +"``(master, slave)``, for the master and the slave end, respectively." +msgstr "" + +#: ../Doc/library/pty.rst:44 +msgid "" +"Spawn a process, and connect its controlling terminal with the current " +"process's standard io. This is often used to baffle programs which insist on " +"reading from the controlling terminal." +msgstr "" + +#: ../Doc/library/pty.rst:48 +msgid "" +"The functions *master_read* and *stdin_read* should be functions which read " +"from a file descriptor. The defaults try to read 1024 bytes each time they " +"are called." +msgstr "" + +#: ../Doc/library/pty.rst:52 +msgid "" +":func:`spawn` now returns the status value from :func:`os.waitpid` on the " +"child process." +msgstr "" + +#: ../Doc/library/pty.rst:61 +msgid "" +"The following program acts like the Unix command :manpage:`script(1)`, using " +"a pseudo-terminal to record all input and output of a terminal session in a " +"\"typescript\". ::" +msgstr "" + +#: ../Doc/library/pwd.rst:2 +msgid ":mod:`pwd` --- The password database" +msgstr "" + +#: ../Doc/library/pwd.rst:10 +msgid "" +"This module provides access to the Unix user account and password database. " +"It is available on all Unix versions." +msgstr "" + +#: ../Doc/library/pwd.rst:13 +msgid "" +"Password database entries are reported as a tuple-like object, whose " +"attributes correspond to the members of the ``passwd`` structure (Attribute " +"field below, see ````):" +msgstr "" + +#: ../Doc/library/pwd.rst:20 +msgid "``pw_name``" +msgstr "" + +#: ../Doc/library/pwd.rst:20 ../Doc/library/spwd.rst:23 +msgid "Login name" +msgstr "" + +#: ../Doc/library/pwd.rst:22 +msgid "``pw_passwd``" +msgstr "" + +#: ../Doc/library/pwd.rst:22 +msgid "Optional encrypted password" +msgstr "" + +#: ../Doc/library/pwd.rst:24 +msgid "``pw_uid``" +msgstr "" + +#: ../Doc/library/pwd.rst:24 +msgid "Numerical user ID" +msgstr "" + +#: ../Doc/library/pwd.rst:26 +msgid "``pw_gid``" +msgstr "" + +#: ../Doc/library/pwd.rst:26 +msgid "Numerical group ID" +msgstr "" + +#: ../Doc/library/pwd.rst:28 +msgid "``pw_gecos``" +msgstr "" + +#: ../Doc/library/pwd.rst:28 +msgid "User name or comment field" +msgstr "" + +#: ../Doc/library/pwd.rst:30 ../Doc/library/spwd.rst:35 +#: ../Doc/library/time.rst:548 ../Doc/library/urllib.parse.rst:105 +msgid "5" +msgstr "" + +#: ../Doc/library/pwd.rst:30 +msgid "``pw_dir``" +msgstr "" + +#: ../Doc/library/pwd.rst:30 +msgid "User home directory" +msgstr "" + +#: ../Doc/library/pwd.rst:32 ../Doc/library/spwd.rst:38 +#: ../Doc/library/time.rst:551 +msgid "6" +msgstr "" + +#: ../Doc/library/pwd.rst:32 +msgid "``pw_shell``" +msgstr "" + +#: ../Doc/library/pwd.rst:32 +msgid "User command interpreter" +msgstr "" + +#: ../Doc/library/pwd.rst:35 +msgid "" +"The uid and gid items are integers, all others are strings. :exc:`KeyError` " +"is raised if the entry asked for cannot be found." +msgstr "" + +#: ../Doc/library/pwd.rst:42 +msgid "" +"In traditional Unix the field ``pw_passwd`` usually contains a password " +"encrypted with a DES derived algorithm (see module :mod:`crypt`). However " +"most modern unices use a so-called *shadow password* system. On those " +"unices the *pw_passwd* field only contains an asterisk (``'*'``) or the " +"letter ``'x'`` where the encrypted password is stored in a file :file:`/etc/" +"shadow` which is not world readable. Whether the *pw_passwd* field contains " +"anything useful is system-dependent. If available, the :mod:`spwd` module " +"should be used where access to the encrypted password is required." +msgstr "" + +#: ../Doc/library/pwd.rst:56 +msgid "Return the password database entry for the given numeric user ID." +msgstr "" + +#: ../Doc/library/pwd.rst:61 +msgid "Return the password database entry for the given user name." +msgstr "" + +#: ../Doc/library/pwd.rst:66 +msgid "" +"Return a list of all available password database entries, in arbitrary order." +msgstr "" + +#: ../Doc/library/pwd.rst:72 ../Doc/library/spwd.rst:71 +msgid "Module :mod:`grp`" +msgstr "" + +#: ../Doc/library/pwd.rst:72 ../Doc/library/spwd.rst:71 +msgid "An interface to the group database, similar to this." +msgstr "" + +#: ../Doc/library/py_compile.rst:2 +msgid ":mod:`py_compile` --- Compile Python source files" +msgstr "" + +#: ../Doc/library/py_compile.rst:10 +msgid "**Source code:** :source:`Lib/py_compile.py`" +msgstr "" + +#: ../Doc/library/py_compile.rst:16 +msgid "" +"The :mod:`py_compile` module provides a function to generate a byte-code " +"file from a source file, and another function used when the module source " +"file is invoked as a script." +msgstr "" + +#: ../Doc/library/py_compile.rst:20 +msgid "" +"Though not often needed, this function can be useful when installing modules " +"for shared use, especially if some of the users may not have permission to " +"write the byte-code cache files in the directory containing the source code." +msgstr "" + +#: ../Doc/library/py_compile.rst:27 +msgid "" +"Exception raised when an error occurs while attempting to compile the file." +msgstr "" + +#: ../Doc/library/py_compile.rst:32 +msgid "" +"Compile a source file to byte-code and write out the byte-code cache file. " +"The source code is loaded from the file named *file*. The byte-code is " +"written to *cfile*, which defaults to the :pep:`3147`/:pep:`488` path, " +"ending in ``.pyc``. For example, if *file* is ``/foo/bar/baz.py`` *cfile* " +"will default to ``/foo/bar/__pycache__/baz.cpython-32.pyc`` for Python 3.2. " +"If *dfile* is specified, it is used as the name of the source file in error " +"messages when instead of *file*. If *doraise* is true, a :exc:" +"`PyCompileError` is raised when an error is encountered while compiling " +"*file*. If *doraise* is false (the default), an error string is written to " +"``sys.stderr``, but no exception is raised. This function returns the path " +"to byte-compiled file, i.e. whatever *cfile* value was used." +msgstr "" + +#: ../Doc/library/py_compile.rst:45 +msgid "" +"If the path that *cfile* becomes (either explicitly specified or computed) " +"is a symlink or non-regular file, :exc:`FileExistsError` will be raised. " +"This is to act as a warning that import will turn those paths into regular " +"files if it is allowed to write byte-compiled files to those paths. This is " +"a side-effect of import using file renaming to place the final byte-compiled " +"file into place to prevent concurrent file writing issues." +msgstr "" + +#: ../Doc/library/py_compile.rst:52 +msgid "" +"*optimize* controls the optimization level and is passed to the built-in :" +"func:`compile` function. The default of ``-1`` selects the optimization " +"level of the current interpreter." +msgstr "" + +#: ../Doc/library/py_compile.rst:56 +msgid "" +"Changed default value of *cfile* to be :PEP:`3147`-compliant. Previous " +"default was *file* + ``'c'`` (``'o'`` if optimization was enabled). Also " +"added the *optimize* parameter." +msgstr "" + +#: ../Doc/library/py_compile.rst:61 +msgid "" +"Changed code to use :mod:`importlib` for the byte-code cache file writing. " +"This means file creation/writing semantics now match what :mod:`importlib` " +"does, e.g. permissions, write-and-move semantics, etc. Also added the caveat " +"that :exc:`FileExistsError` is raised if *cfile* is a symlink or non-regular " +"file." +msgstr "" + +#: ../Doc/library/py_compile.rst:71 +msgid "" +"Compile several source files. The files named in *args* (or on the command " +"line, if *args* is ``None``) are compiled and the resulting byte-code is " +"cached in the normal manner. This function does not search a directory " +"structure to locate source files; it only compiles files named explicitly. " +"If ``'-'`` is the only parameter in args, the list of files is taken from " +"standard input." +msgstr "" + +#: ../Doc/library/py_compile.rst:78 +msgid "Added support for ``'-'``." +msgstr "" + +#: ../Doc/library/py_compile.rst:81 +msgid "" +"When this module is run as a script, the :func:`main` is used to compile all " +"the files named on the command line. The exit status is nonzero if one of " +"the files could not be compiled." +msgstr "" + +#: ../Doc/library/py_compile.rst:88 +msgid "Module :mod:`compileall`" +msgstr "" + +#: ../Doc/library/py_compile.rst:89 +msgid "Utilities to compile all Python source files in a directory tree." +msgstr "" + +#: ../Doc/library/pyclbr.rst:2 +msgid ":mod:`pyclbr` --- Python class browser support" +msgstr "" + +#: ../Doc/library/pyclbr.rst:9 +msgid "**Source code:** :source:`Lib/pyclbr.py`" +msgstr "" + +#: ../Doc/library/pyclbr.rst:13 +msgid "" +"The :mod:`pyclbr` module can be used to determine some limited information " +"about the classes, methods and top-level functions defined in a module. The " +"information provided is sufficient to implement a traditional three-pane " +"class browser. The information is extracted from the source code rather " +"than by importing the module, so this module is safe to use with untrusted " +"code. This restriction makes it impossible to use this module with modules " +"not implemented in Python, including all standard and optional extension " +"modules." +msgstr "" + +#: ../Doc/library/pyclbr.rst:25 +msgid "" +"Read a module and return a dictionary mapping class names to class " +"descriptor objects. The parameter *module* should be the name of a module " +"as a string; it may be the name of a module within a package. The *path* " +"parameter should be a sequence, and is used to augment the value of ``sys." +"path``, which is used to locate module source code." +msgstr "" + +#: ../Doc/library/pyclbr.rst:34 +msgid "" +"Like :func:`readmodule`, but the returned dictionary, in addition to mapping " +"class names to class descriptor objects, also maps top-level function names " +"to function descriptor objects. Moreover, if the module being read is a " +"package, the key ``'__path__'`` in the returned dictionary has as its value " +"a list which contains the package search path." +msgstr "" + +#: ../Doc/library/pyclbr.rst:45 +msgid "Class Objects" +msgstr "" + +#: ../Doc/library/pyclbr.rst:47 +msgid "" +"The :class:`Class` objects used as values in the dictionary returned by :" +"func:`readmodule` and :func:`readmodule_ex` provide the following data " +"attributes:" +msgstr "" + +#: ../Doc/library/pyclbr.rst:54 +msgid "" +"The name of the module defining the class described by the class descriptor." +msgstr "" + +#: ../Doc/library/pyclbr.rst:59 +msgid "The name of the class." +msgstr "" + +#: ../Doc/library/pyclbr.rst:64 +msgid "" +"A list of :class:`Class` objects which describe the immediate base classes " +"of the class being described. Classes which are named as superclasses but " +"which are not discoverable by :func:`readmodule` are listed as a string with " +"the class name instead of as :class:`Class` objects." +msgstr "" + +#: ../Doc/library/pyclbr.rst:73 +msgid "A dictionary mapping method names to line numbers." +msgstr "" + +#: ../Doc/library/pyclbr.rst:78 +msgid "Name of the file containing the ``class`` statement defining the class." +msgstr "" + +#: ../Doc/library/pyclbr.rst:83 +msgid "" +"The line number of the ``class`` statement within the file named by :attr:" +"`~Class.file`." +msgstr "" + +#: ../Doc/library/pyclbr.rst:90 +msgid "Function Objects" +msgstr "" + +#: ../Doc/library/pyclbr.rst:92 +msgid "" +"The :class:`Function` objects used as values in the dictionary returned by :" +"func:`readmodule_ex` provide the following attributes:" +msgstr "" + +#: ../Doc/library/pyclbr.rst:98 +msgid "" +"The name of the module defining the function described by the function " +"descriptor." +msgstr "" + +#: ../Doc/library/pyclbr.rst:104 +msgid "The name of the function." +msgstr "" + +#: ../Doc/library/pyclbr.rst:109 +msgid "" +"Name of the file containing the ``def`` statement defining the function." +msgstr "" + +#: ../Doc/library/pyclbr.rst:114 +msgid "" +"The line number of the ``def`` statement within the file named by :attr:" +"`~Function.file`." +msgstr "" + +#: ../Doc/library/pydoc.rst:2 +msgid ":mod:`pydoc` --- Documentation generator and online help system" +msgstr "" + +#: ../Doc/library/pydoc.rst:10 +msgid "**Source code:** :source:`Lib/pydoc.py`" +msgstr "" + +#: ../Doc/library/pydoc.rst:19 +msgid "" +"The :mod:`pydoc` module automatically generates documentation from Python " +"modules. The documentation can be presented as pages of text on the " +"console, served to a Web browser, or saved to HTML files." +msgstr "" + +#: ../Doc/library/pydoc.rst:23 +msgid "" +"For modules, classes, functions and methods, the displayed documentation is " +"derived from the docstring (i.e. the :attr:`__doc__` attribute) of the " +"object, and recursively of its documentable members. If there is no " +"docstring, :mod:`pydoc` tries to obtain a description from the block of " +"comment lines just above the definition of the class, function or method in " +"the source file, or at the top of the module (see :func:`inspect." +"getcomments`)." +msgstr "" + +#: ../Doc/library/pydoc.rst:30 +msgid "" +"The built-in function :func:`help` invokes the online help system in the " +"interactive interpreter, which uses :mod:`pydoc` to generate its " +"documentation as text on the console. The same text documentation can also " +"be viewed from outside the Python interpreter by running :program:`pydoc` as " +"a script at the operating system's command prompt. For example, running ::" +msgstr "" + +#: ../Doc/library/pydoc.rst:38 +msgid "" +"at a shell prompt will display documentation on the :mod:`sys` module, in a " +"style similar to the manual pages shown by the Unix :program:`man` command. " +"The argument to :program:`pydoc` can be the name of a function, module, or " +"package, or a dotted reference to a class, method, or function within a " +"module or module in a package. If the argument to :program:`pydoc` looks " +"like a path (that is, it contains the path separator for your operating " +"system, such as a slash in Unix), and refers to an existing Python source " +"file, then documentation is produced for that file." +msgstr "" + +#: ../Doc/library/pydoc.rst:49 +msgid "" +"In order to find objects and their documentation, :mod:`pydoc` imports the " +"module(s) to be documented. Therefore, any code on module level will be " +"executed on that occasion. Use an ``if __name__ == '__main__':`` guard to " +"only execute code when a file is invoked as a script and not just imported." +msgstr "" + +#: ../Doc/library/pydoc.rst:54 +msgid "" +"When printing output to the console, :program:`pydoc` attempts to paginate " +"the output for easier reading. If the :envvar:`PAGER` environment variable " +"is set, :program:`pydoc` will use its value as a pagination program." +msgstr "" + +#: ../Doc/library/pydoc.rst:58 +msgid "" +"Specifying a ``-w`` flag before the argument will cause HTML documentation " +"to be written out to a file in the current directory, instead of displaying " +"text on the console." +msgstr "" + +#: ../Doc/library/pydoc.rst:62 +msgid "" +"Specifying a ``-k`` flag before the argument will search the synopsis lines " +"of all available modules for the keyword given as the argument, again in a " +"manner similar to the Unix :program:`man` command. The synopsis line of a " +"module is the first line of its documentation string." +msgstr "" + +#: ../Doc/library/pydoc.rst:67 +msgid "" +"You can also use :program:`pydoc` to start an HTTP server on the local " +"machine that will serve documentation to visiting Web browsers. :program:" +"`pydoc -p 1234` will start a HTTP server on port 1234, allowing you to " +"browse the documentation at ``http://localhost:1234/`` in your preferred Web " +"browser. Specifying ``0`` as the port number will select an arbitrary unused " +"port." +msgstr "" + +#: ../Doc/library/pydoc.rst:73 +msgid "" +":program:`pydoc -b` will start the server and additionally open a web " +"browser to a module index page. Each served page has a navigation bar at " +"the top where you can *Get* help on an individual item, *Search* all modules " +"with a keyword in their synopsis line, and go to the *Module index*, " +"*Topics* and *Keywords* pages." +msgstr "" + +#: ../Doc/library/pydoc.rst:79 +msgid "" +"When :program:`pydoc` generates documentation, it uses the current " +"environment and path to locate modules. Thus, invoking :program:`pydoc " +"spam` documents precisely the version of the module you would get if you " +"started the Python interpreter and typed ``import spam``." +msgstr "" + +#: ../Doc/library/pydoc.rst:84 +msgid "" +"Module docs for core modules are assumed to reside in ``https://docs.python." +"org/X.Y/library/`` where ``X`` and ``Y`` are the major and minor version " +"numbers of the Python interpreter. This can be overridden by setting the :" +"envvar:`PYTHONDOCS` environment variable to a different URL or to a local " +"directory containing the Library Reference Manual pages." +msgstr "" + +#: ../Doc/library/pydoc.rst:91 +msgid "Added the ``-b`` option." +msgstr "" + +#: ../Doc/library/pydoc.rst:94 +msgid "The ``-g`` command line option was removed." +msgstr "" + +#: ../Doc/library/pydoc.rst:97 +msgid "" +":mod:`pydoc` now uses :func:`inspect.signature` rather than :func:`inspect." +"getfullargspec` to extract signature information from callables." +msgstr "" + +#: ../Doc/library/pyexpat.rst:2 +msgid ":mod:`xml.parsers.expat` --- Fast XML parsing using Expat" +msgstr "" + +#: ../Doc/library/pyexpat.rst:21 +msgid "" +"The :mod:`pyexpat` module is not secure against maliciously constructed " +"data. If you need to parse untrusted or unauthenticated data see :ref:`xml-" +"vulnerabilities`." +msgstr "" + +#: ../Doc/library/pyexpat.rst:28 +msgid "" +"The :mod:`xml.parsers.expat` module is a Python interface to the Expat non-" +"validating XML parser. The module provides a single extension type, :class:" +"`xmlparser`, that represents the current state of an XML parser. After an :" +"class:`xmlparser` object has been created, various attributes of the object " +"can be set to handler functions. When an XML document is then fed to the " +"parser, the handler functions are called for the character data and markup " +"in the XML document." +msgstr "" + +#: ../Doc/library/pyexpat.rst:38 +msgid "" +"This module uses the :mod:`pyexpat` module to provide access to the Expat " +"parser. Direct use of the :mod:`pyexpat` module is deprecated." +msgstr "" + +#: ../Doc/library/pyexpat.rst:41 +msgid "This module provides one exception and one type object:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:46 +msgid "" +"The exception raised when Expat reports an error. See section :ref:" +"`expaterror-objects` for more information on interpreting Expat errors." +msgstr "" + +#: ../Doc/library/pyexpat.rst:52 +msgid "Alias for :exc:`ExpatError`." +msgstr "" + +#: ../Doc/library/pyexpat.rst:57 +msgid "The type of the return values from the :func:`ParserCreate` function." +msgstr "" + +#: ../Doc/library/pyexpat.rst:59 +msgid "The :mod:`xml.parsers.expat` module contains two functions:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:64 +msgid "Returns an explanatory string for a given error number *errno*." +msgstr "" + +#: ../Doc/library/pyexpat.rst:69 +msgid "" +"Creates and returns a new :class:`xmlparser` object. *encoding*, if " +"specified, must be a string naming the encoding used by the XML data. " +"Expat doesn't support as many encodings as Python does, and its repertoire " +"of encodings can't be extended; it supports UTF-8, UTF-16, ISO-8859-1 " +"(Latin1), and ASCII. If *encoding* [1]_ is given it will override the " +"implicit or explicit encoding of the document." +msgstr "" + +#: ../Doc/library/pyexpat.rst:76 +msgid "" +"Expat can optionally do XML namespace processing for you, enabled by " +"providing a value for *namespace_separator*. The value must be a one-" +"character string; a :exc:`ValueError` will be raised if the string has an " +"illegal length (``None`` is considered the same as omission). When " +"namespace processing is enabled, element type names and attribute names that " +"belong to a namespace will be expanded. The element name passed to the " +"element handlers :attr:`StartElementHandler` and :attr:`EndElementHandler` " +"will be the concatenation of the namespace URI, the namespace separator " +"character, and the local part of the name. If the namespace separator is a " +"zero byte (``chr(0)``) then the namespace URI and the local part will be " +"concatenated without any separator." +msgstr "" + +#: ../Doc/library/pyexpat.rst:88 +msgid "" +"For example, if *namespace_separator* is set to a space character (``' '``) " +"and the following document is parsed:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:100 +msgid "" +":attr:`StartElementHandler` will receive the following strings for each " +"element::" +msgstr "" + +#: ../Doc/library/pyexpat.rst:107 +msgid "" +"Due to limitations in the ``Expat`` library used by :mod:`pyexpat`, the :" +"class:`xmlparser` instance returned can only be used to parse a single XML " +"document. Call ``ParserCreate`` for each document to provide unique parser " +"instances." +msgstr "" + +#: ../Doc/library/pyexpat.rst:115 +msgid "`The Expat XML Parser `_" +msgstr "" + +#: ../Doc/library/pyexpat.rst:116 +msgid "Home page of the Expat project." +msgstr "" + +#: ../Doc/library/pyexpat.rst:122 ../Doc/library/xml.etree.elementtree.rst:1045 +msgid "XMLParser Objects" +msgstr "" + +#: ../Doc/library/pyexpat.rst:124 +msgid ":class:`xmlparser` objects have the following methods:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:129 +msgid "" +"Parses the contents of the string *data*, calling the appropriate handler " +"functions to process the parsed data. *isfinal* must be true on the final " +"call to this method; it allows the parsing of a single file in fragments, " +"not the submission of multiple files. *data* can be the empty string at any " +"time." +msgstr "" + +#: ../Doc/library/pyexpat.rst:138 +msgid "" +"Parse XML data reading from the object *file*. *file* only needs to provide " +"the ``read(nbytes)`` method, returning the empty string when there's no more " +"data." +msgstr "" + +#: ../Doc/library/pyexpat.rst:145 +msgid "" +"Sets the base to be used for resolving relative URIs in system identifiers " +"in declarations. Resolving relative identifiers is left to the application: " +"this value will be passed through as the *base* argument to the :func:" +"`ExternalEntityRefHandler`, :func:`NotationDeclHandler`, and :func:" +"`UnparsedEntityDeclHandler` functions." +msgstr "" + +#: ../Doc/library/pyexpat.rst:154 +msgid "" +"Returns a string containing the base set by a previous call to :meth:" +"`SetBase`, or ``None`` if :meth:`SetBase` hasn't been called." +msgstr "" + +#: ../Doc/library/pyexpat.rst:160 +msgid "" +"Returns the input data that generated the current event as a string. The " +"data is in the encoding of the entity which contains the text. When called " +"while an event handler is not active, the return value is ``None``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:167 +msgid "" +"Create a \"child\" parser which can be used to parse an external parsed " +"entity referred to by content parsed by the parent parser. The *context* " +"parameter should be the string passed to the :meth:" +"`ExternalEntityRefHandler` handler function, described below. The child " +"parser is created with the :attr:`ordered_attributes` and :attr:" +"`specified_attributes` set to the values of this parser." +msgstr "" + +#: ../Doc/library/pyexpat.rst:176 +msgid "" +"Control parsing of parameter entities (including the external DTD subset). " +"Possible *flag* values are :const:`XML_PARAM_ENTITY_PARSING_NEVER`, :const:" +"`XML_PARAM_ENTITY_PARSING_UNLESS_STANDALONE` and :const:" +"`XML_PARAM_ENTITY_PARSING_ALWAYS`. Return true if setting the flag was " +"successful." +msgstr "" + +#: ../Doc/library/pyexpat.rst:184 +msgid "" +"Calling this with a true value for *flag* (the default) will cause Expat to " +"call the :attr:`ExternalEntityRefHandler` with :const:`None` for all " +"arguments to allow an alternate DTD to be loaded. If the document does not " +"contain a document type declaration, the :attr:`ExternalEntityRefHandler` " +"will still be called, but the :attr:`StartDoctypeDeclHandler` and :attr:" +"`EndDoctypeDeclHandler` will not be called." +msgstr "" + +#: ../Doc/library/pyexpat.rst:191 +msgid "" +"Passing a false value for *flag* will cancel a previous call that passed a " +"true value, but otherwise has no effect." +msgstr "" + +#: ../Doc/library/pyexpat.rst:194 +msgid "" +"This method can only be called before the :meth:`Parse` or :meth:`ParseFile` " +"methods are called; calling it after either of those have been called " +"causes :exc:`ExpatError` to be raised with the :attr:`code` attribute set to " +"``errors.codes[errors.XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING]``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:199 +msgid ":class:`xmlparser` objects have the following attributes:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:204 +msgid "" +"The size of the buffer used when :attr:`buffer_text` is true. A new buffer " +"size can be set by assigning a new integer value to this attribute. When the " +"size is changed, the buffer will be flushed." +msgstr "" + +#: ../Doc/library/pyexpat.rst:212 +msgid "" +"Setting this to true causes the :class:`xmlparser` object to buffer textual " +"content returned by Expat to avoid multiple calls to the :meth:" +"`CharacterDataHandler` callback whenever possible. This can improve " +"performance substantially since Expat normally breaks character data into " +"chunks at every line ending. This attribute is false by default, and may be " +"changed at any time." +msgstr "" + +#: ../Doc/library/pyexpat.rst:222 +msgid "" +"If :attr:`buffer_text` is enabled, the number of bytes stored in the buffer. " +"These bytes represent UTF-8 encoded text. This attribute has no meaningful " +"interpretation when :attr:`buffer_text` is false." +msgstr "" + +#: ../Doc/library/pyexpat.rst:229 +msgid "" +"Setting this attribute to a non-zero integer causes the attributes to be " +"reported as a list rather than a dictionary. The attributes are presented " +"in the order found in the document text. For each attribute, two list " +"entries are presented: the attribute name and the attribute value. (Older " +"versions of this module also used this format.) By default, this attribute " +"is false; it may be changed at any time." +msgstr "" + +#: ../Doc/library/pyexpat.rst:239 +msgid "" +"If set to a non-zero integer, the parser will report only those attributes " +"which were specified in the document instance and not those which were " +"derived from attribute declarations. Applications which set this need to be " +"especially careful to use what additional information is available from the " +"declarations as needed to comply with the standards for the behavior of XML " +"processors. By default, this attribute is false; it may be changed at any " +"time." +msgstr "" + +#: ../Doc/library/pyexpat.rst:247 +msgid "" +"The following attributes contain values relating to the most recent error " +"encountered by an :class:`xmlparser` object, and will only have correct " +"values once a call to :meth:`Parse` or :meth:`ParseFile` has raised an :exc:" +"`xml.parsers.expat.ExpatError` exception." +msgstr "" + +#: ../Doc/library/pyexpat.rst:255 +msgid "Byte index at which an error occurred." +msgstr "" + +#: ../Doc/library/pyexpat.rst:260 +msgid "" +"Numeric code specifying the problem. This value can be passed to the :func:" +"`ErrorString` function, or compared to one of the constants defined in the " +"``errors`` object." +msgstr "" + +#: ../Doc/library/pyexpat.rst:267 +msgid "Column number at which an error occurred." +msgstr "" + +#: ../Doc/library/pyexpat.rst:272 +msgid "Line number at which an error occurred." +msgstr "" + +#: ../Doc/library/pyexpat.rst:274 +msgid "" +"The following attributes contain values relating to the current parse " +"location in an :class:`xmlparser` object. During a callback reporting a " +"parse event they indicate the location of the first of the sequence of " +"characters that generated the event. When called outside of a callback, the " +"position indicated will be just past the last parse event (regardless of " +"whether there was an associated callback)." +msgstr "" + +#: ../Doc/library/pyexpat.rst:284 +msgid "Current byte index in the parser input." +msgstr "" + +#: ../Doc/library/pyexpat.rst:289 +msgid "Current column number in the parser input." +msgstr "" + +#: ../Doc/library/pyexpat.rst:294 +msgid "Current line number in the parser input." +msgstr "" + +#: ../Doc/library/pyexpat.rst:296 +msgid "" +"Here is the list of handlers that can be set. To set a handler on an :class:" +"`xmlparser` object *o*, use ``o.handlername = func``. *handlername* must be " +"taken from the following list, and *func* must be a callable object " +"accepting the correct number of arguments. The arguments are all strings, " +"unless otherwise stated." +msgstr "" + +#: ../Doc/library/pyexpat.rst:305 +msgid "" +"Called when the XML declaration is parsed. The XML declaration is the " +"(optional) declaration of the applicable version of the XML recommendation, " +"the encoding of the document text, and an optional \"standalone\" " +"declaration. *version* and *encoding* will be strings, and *standalone* will " +"be ``1`` if the document is declared standalone, ``0`` if it is declared not " +"to be standalone, or ``-1`` if the standalone clause was omitted. This is " +"only available with Expat version 1.95.0 or newer." +msgstr "" + +#: ../Doc/library/pyexpat.rst:316 +msgid "" +"Called when Expat begins parsing the document type declaration (``'``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:430 +msgid "" +"Called at the start of a CDATA section. This and :attr:" +"`EndCdataSectionHandler` are needed to be able to identify the syntactical " +"start and end for CDATA sections." +msgstr "" + +#: ../Doc/library/pyexpat.rst:437 +msgid "Called at the end of a CDATA section." +msgstr "" + +#: ../Doc/library/pyexpat.rst:442 +msgid "" +"Called for any characters in the XML document for which no applicable " +"handler has been specified. This means characters that are part of a " +"construct which could be reported, but for which no handler has been " +"supplied." +msgstr "" + +#: ../Doc/library/pyexpat.rst:449 +msgid "" +"This is the same as the :func:`DefaultHandler`, but doesn't inhibit " +"expansion of internal entities. The entity reference will not be passed to " +"the default handler." +msgstr "" + +#: ../Doc/library/pyexpat.rst:456 +msgid "" +"Called if the XML document hasn't been declared as being a standalone " +"document. This happens when there is an external subset or a reference to a " +"parameter entity, but the XML declaration does not set standalone to ``yes`` " +"in an XML declaration. If this handler returns ``0``, then the parser will " +"raise an :const:`XML_ERROR_NOT_STANDALONE` error. If this handler is not " +"set, no exception is raised by the parser for this condition." +msgstr "" + +#: ../Doc/library/pyexpat.rst:466 +msgid "" +"Called for references to external entities. *base* is the current base, as " +"set by a previous call to :meth:`SetBase`. The public and system " +"identifiers, *systemId* and *publicId*, are strings if given; if the public " +"identifier is not given, *publicId* will be ``None``. The *context* value " +"is opaque and should only be used as described below." +msgstr "" + +#: ../Doc/library/pyexpat.rst:472 +msgid "" +"For external entities to be parsed, this handler must be implemented. It is " +"responsible for creating the sub-parser using " +"``ExternalEntityParserCreate(context)``, initializing it with the " +"appropriate callbacks, and parsing the entity. This handler should return " +"an integer; if it returns ``0``, the parser will raise an :const:" +"`XML_ERROR_EXTERNAL_ENTITY_HANDLING` error, otherwise parsing will continue." +msgstr "" + +#: ../Doc/library/pyexpat.rst:480 +msgid "" +"If this handler is not provided, external entities are reported by the :attr:" +"`DefaultHandler` callback, if provided." +msgstr "" + +#: ../Doc/library/pyexpat.rst:487 +msgid "ExpatError Exceptions" +msgstr "" + +#: ../Doc/library/pyexpat.rst:492 +msgid ":exc:`ExpatError` exceptions have a number of interesting attributes:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:497 +msgid "" +"Expat's internal error number for the specific error. The :data:`errors." +"messages ` dictionary maps these error " +"numbers to Expat's error messages. For example::" +msgstr "" + +#: ../Doc/library/pyexpat.rst:509 +msgid "" +"The :mod:`~xml.parsers.expat.errors` module also provides error message " +"constants and a dictionary :data:`~xml.parsers.expat.errors.codes` mapping " +"these messages back to the error codes, see below." +msgstr "" + +#: ../Doc/library/pyexpat.rst:516 +msgid "" +"Line number on which the error was detected. The first line is numbered " +"``1``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:521 +msgid "" +"Character offset into the line where the error occurred. The first column " +"is numbered ``0``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:530 +msgid "" +"The following program defines three handlers that just print out their " +"arguments. ::" +msgstr "" + +#: ../Doc/library/pyexpat.rst:554 +msgid "The output from this program is::" +msgstr "" + +#: ../Doc/library/pyexpat.rst:571 +msgid "Content Model Descriptions" +msgstr "" + +#: ../Doc/library/pyexpat.rst:577 +msgid "" +"Content models are described using nested tuples. Each tuple contains four " +"values: the type, the quantifier, the name, and a tuple of children. " +"Children are simply additional content model descriptions." +msgstr "" + +#: ../Doc/library/pyexpat.rst:581 +msgid "" +"The values of the first two fields are constants defined in the :mod:`xml." +"parsers.expat.model` module. These constants can be collected in two " +"groups: the model type group and the quantifier group." +msgstr "" + +#: ../Doc/library/pyexpat.rst:585 +msgid "The constants in the model type group are:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:591 +msgid "" +"The element named by the model name was declared to have a content model of " +"``ANY``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:598 +msgid "" +"The named element allows a choice from a number of options; this is used for " +"content models such as ``(A | B | C)``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:605 +msgid "Elements which are declared to be ``EMPTY`` have this model type." +msgstr "" + +#: ../Doc/library/pyexpat.rst:619 +msgid "" +"Models which represent a series of models which follow one after the other " +"are indicated with this model type. This is used for models such as ``(A, " +"B, C)``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:622 +msgid "The constants in the quantifier group are:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:628 +msgid "No modifier is given, so it can appear exactly once, as for ``A``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:634 +msgid "The model is optional: it can appear once or not at all, as for ``A?``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:640 +msgid "The model must occur one or more times (like ``A+``)." +msgstr "" + +#: ../Doc/library/pyexpat.rst:646 +msgid "The model must occur zero or more times, as for ``A*``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:652 +msgid "Expat error constants" +msgstr "" + +#: ../Doc/library/pyexpat.rst:656 +msgid "" +"The following constants are provided in the :mod:`xml.parsers.expat.errors` " +"module. These constants are useful in interpreting some of the attributes " +"of the :exc:`ExpatError` exception objects raised when an error has " +"occurred. Since for backwards compatibility reasons, the constants' value is " +"the error *message* and not the numeric error *code*, you do this by " +"comparing its :attr:`code` attribute with :samp:`errors.codes[errors." +"XML_ERROR_{CONSTANT_NAME}]`." +msgstr "" + +#: ../Doc/library/pyexpat.rst:664 +msgid "The ``errors`` module has the following attributes:" +msgstr "" + +#: ../Doc/library/pyexpat.rst:668 +msgid "A dictionary mapping numeric error codes to their string descriptions." +msgstr "" + +#: ../Doc/library/pyexpat.rst:675 +msgid "A dictionary mapping string descriptions to their error codes." +msgstr "" + +#: ../Doc/library/pyexpat.rst:685 +msgid "" +"An entity reference in an attribute value referred to an external entity " +"instead of an internal entity." +msgstr "" + +#: ../Doc/library/pyexpat.rst:691 +msgid "" +"A character reference referred to a character which is illegal in XML (for " +"example, character ``0``, or '``�``')." +msgstr "" + +#: ../Doc/library/pyexpat.rst:697 +msgid "" +"An entity reference referred to an entity which was declared with a " +"notation, so cannot be parsed." +msgstr "" + +#: ../Doc/library/pyexpat.rst:703 +msgid "An attribute was used more than once in a start tag." +msgstr "" + +#: ../Doc/library/pyexpat.rst:711 +msgid "" +"Raised when an input byte could not properly be assigned to a character; for " +"example, a NUL byte (value ``0``) in a UTF-8 input stream." +msgstr "" + +#: ../Doc/library/pyexpat.rst:717 +msgid "Something other than whitespace occurred after the document element." +msgstr "" + +#: ../Doc/library/pyexpat.rst:722 +msgid "" +"An XML declaration was found somewhere other than the start of the input " +"data." +msgstr "" + +#: ../Doc/library/pyexpat.rst:727 +msgid "" +"The document contains no elements (XML requires all documents to contain " +"exactly one top-level element).." +msgstr "" + +#: ../Doc/library/pyexpat.rst:733 +msgid "Expat was not able to allocate memory internally." +msgstr "" + +#: ../Doc/library/pyexpat.rst:738 +msgid "A parameter entity reference was found where it was not allowed." +msgstr "" + +#: ../Doc/library/pyexpat.rst:743 +msgid "An incomplete character was found in the input." +msgstr "" + +#: ../Doc/library/pyexpat.rst:748 +msgid "" +"An entity reference contained another reference to the same entity; possibly " +"via a different name, and possibly indirectly." +msgstr "" + +#: ../Doc/library/pyexpat.rst:754 +msgid "Some unspecified syntax error was encountered." +msgstr "" + +#: ../Doc/library/pyexpat.rst:759 +msgid "An end tag did not match the innermost open start tag." +msgstr "" + +#: ../Doc/library/pyexpat.rst:764 +msgid "" +"Some token (such as a start tag) was not closed before the end of the stream " +"or the next token was encountered." +msgstr "" + +#: ../Doc/library/pyexpat.rst:770 +msgid "A reference was made to an entity which was not defined." +msgstr "" + +#: ../Doc/library/pyexpat.rst:775 +msgid "The document encoding is not supported by Expat." +msgstr "" + +#: ../Doc/library/pyexpat.rst:780 +msgid "A CDATA marked section was not closed." +msgstr "" + +#: ../Doc/library/pyexpat.rst:788 +msgid "" +"The parser determined that the document was not \"standalone\" though it " +"declared itself to be in the XML declaration, and the :attr:" +"`NotStandaloneHandler` was set and returned ``0``." +msgstr "" + +#: ../Doc/library/pyexpat.rst:801 +msgid "" +"An operation was requested that requires DTD support to be compiled in, but " +"Expat was configured without DTD support. This should never be reported by " +"a standard build of the :mod:`xml.parsers.expat` module." +msgstr "" + +#: ../Doc/library/pyexpat.rst:808 +msgid "" +"A behavioral change was requested after parsing started that can only be " +"changed before parsing has started. This is (currently) only raised by :" +"meth:`UseForeignDTD`." +msgstr "" + +#: ../Doc/library/pyexpat.rst:815 +msgid "An undeclared prefix was found when namespace processing was enabled." +msgstr "" + +#: ../Doc/library/pyexpat.rst:820 +msgid "" +"The document attempted to remove the namespace declaration associated with a " +"prefix." +msgstr "" + +#: ../Doc/library/pyexpat.rst:826 +msgid "A parameter entity contained incomplete markup." +msgstr "" + +#: ../Doc/library/pyexpat.rst:831 +msgid "The document contained no document element at all." +msgstr "" + +#: ../Doc/library/pyexpat.rst:836 +msgid "There was an error parsing a text declaration in an external entity." +msgstr "" + +#: ../Doc/library/pyexpat.rst:841 +msgid "Characters were found in the public id that are not allowed." +msgstr "" + +#: ../Doc/library/pyexpat.rst:846 +msgid "" +"The requested operation was made on a suspended parser, but isn't allowed. " +"This includes attempts to provide additional input or to stop the parser." +msgstr "" + +#: ../Doc/library/pyexpat.rst:852 +msgid "" +"An attempt to resume the parser was made when the parser had not been " +"suspended." +msgstr "" + +#: ../Doc/library/pyexpat.rst:857 +msgid "This should not be reported to Python applications." +msgstr "" + +#: ../Doc/library/pyexpat.rst:862 +msgid "" +"The requested operation was made on a parser which was finished parsing " +"input, but isn't allowed. This includes attempts to provide additional " +"input or to stop the parser." +msgstr "" + +#: ../Doc/library/pyexpat.rst:872 +msgid "" +"The encoding string included in XML output should conform to the appropriate " +"standards. For example, \"UTF-8\" is valid, but \"UTF8\" is not. See https://" +"www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl and https://www.iana." +"org/assignments/character-sets/character-sets.xhtml." +msgstr "" + +#: ../Doc/library/python.rst:5 +msgid "Python Runtime Services" +msgstr "" + +#: ../Doc/library/python.rst:7 +msgid "" +"The modules described in this chapter provide a wide range of services " +"related to the Python interpreter and its interaction with its environment. " +"Here's an overview:" +msgstr "" + +#: ../Doc/library/queue.rst:2 +msgid ":mod:`queue` --- A synchronized queue class" +msgstr "" + +#: ../Doc/library/queue.rst:7 +msgid "**Source code:** :source:`Lib/queue.py`" +msgstr "" + +#: ../Doc/library/queue.rst:11 +msgid "" +"The :mod:`queue` module implements multi-producer, multi-consumer queues. It " +"is especially useful in threaded programming when information must be " +"exchanged safely between multiple threads. The :class:`Queue` class in this " +"module implements all the required locking semantics. It depends on the " +"availability of thread support in Python; see the :mod:`threading` module." +msgstr "" + +#: ../Doc/library/queue.rst:18 +msgid "" +"The module implements three types of queue, which differ only in the order " +"in which the entries are retrieved. In a :abbr:`FIFO (first-in, first-out)` " +"queue, the first tasks added are the first retrieved. In a :abbr:`LIFO (last-" +"in, first-out)` queue, the most recently added entry is the first retrieved " +"(operating like a stack). With a priority queue, the entries are kept " +"sorted (using the :mod:`heapq` module) and the lowest valued entry is " +"retrieved first." +msgstr "" + +#: ../Doc/library/queue.rst:26 +msgid "" +"Internally, the module uses locks to temporarily block competing threads; " +"however, it is not designed to handle reentrancy within a thread." +msgstr "" + +#: ../Doc/library/queue.rst:29 +msgid "The :mod:`queue` module defines the following classes and exceptions:" +msgstr "" + +#: ../Doc/library/queue.rst:33 +msgid "" +"Constructor for a :abbr:`FIFO (first-in, first-out)` queue. *maxsize* is an " +"integer that sets the upperbound limit on the number of items that can be " +"placed in the queue. Insertion will block once this size has been reached, " +"until queue items are consumed. If *maxsize* is less than or equal to zero, " +"the queue size is infinite." +msgstr "" + +#: ../Doc/library/queue.rst:41 +msgid "" +"Constructor for a :abbr:`LIFO (last-in, first-out)` queue. *maxsize* is an " +"integer that sets the upperbound limit on the number of items that can be " +"placed in the queue. Insertion will block once this size has been reached, " +"until queue items are consumed. If *maxsize* is less than or equal to zero, " +"the queue size is infinite." +msgstr "" + +#: ../Doc/library/queue.rst:50 +msgid "" +"Constructor for a priority queue. *maxsize* is an integer that sets the " +"upperbound limit on the number of items that can be placed in the queue. " +"Insertion will block once this size has been reached, until queue items are " +"consumed. If *maxsize* is less than or equal to zero, the queue size is " +"infinite." +msgstr "" + +#: ../Doc/library/queue.rst:55 +msgid "" +"The lowest valued entries are retrieved first (the lowest valued entry is " +"the one returned by ``sorted(list(entries))[0]``). A typical pattern for " +"entries is a tuple in the form: ``(priority_number, data)``." +msgstr "" + +#: ../Doc/library/queue.rst:62 +msgid "" +"Exception raised when non-blocking :meth:`~Queue.get` (or :meth:`~Queue." +"get_nowait`) is called on a :class:`Queue` object which is empty." +msgstr "" + +#: ../Doc/library/queue.rst:69 +msgid "" +"Exception raised when non-blocking :meth:`~Queue.put` (or :meth:`~Queue." +"put_nowait`) is called on a :class:`Queue` object which is full." +msgstr "" + +#: ../Doc/library/queue.rst:77 +msgid "Queue Objects" +msgstr "" + +#: ../Doc/library/queue.rst:79 +msgid "" +"Queue objects (:class:`Queue`, :class:`LifoQueue`, or :class:" +"`PriorityQueue`) provide the public methods described below." +msgstr "" + +#: ../Doc/library/queue.rst:85 +msgid "" +"Return the approximate size of the queue. Note, qsize() > 0 doesn't " +"guarantee that a subsequent get() will not block, nor will qsize() < maxsize " +"guarantee that put() will not block." +msgstr "" + +#: ../Doc/library/queue.rst:92 +msgid "" +"Return ``True`` if the queue is empty, ``False`` otherwise. If empty() " +"returns ``True`` it doesn't guarantee that a subsequent call to put() will " +"not block. Similarly, if empty() returns ``False`` it doesn't guarantee " +"that a subsequent call to get() will not block." +msgstr "" + +#: ../Doc/library/queue.rst:100 +msgid "" +"Return ``True`` if the queue is full, ``False`` otherwise. If full() " +"returns ``True`` it doesn't guarantee that a subsequent call to get() will " +"not block. Similarly, if full() returns ``False`` it doesn't guarantee that " +"a subsequent call to put() will not block." +msgstr "" + +#: ../Doc/library/queue.rst:108 +msgid "" +"Put *item* into the queue. If optional args *block* is true and *timeout* is " +"None (the default), block if necessary until a free slot is available. If " +"*timeout* is a positive number, it blocks at most *timeout* seconds and " +"raises the :exc:`Full` exception if no free slot was available within that " +"time. Otherwise (*block* is false), put an item on the queue if a free slot " +"is immediately available, else raise the :exc:`Full` exception (*timeout* is " +"ignored in that case)." +msgstr "" + +#: ../Doc/library/queue.rst:119 +msgid "Equivalent to ``put(item, False)``." +msgstr "" + +#: ../Doc/library/queue.rst:124 +msgid "" +"Remove and return an item from the queue. If optional args *block* is true " +"and *timeout* is None (the default), block if necessary until an item is " +"available. If *timeout* is a positive number, it blocks at most *timeout* " +"seconds and raises the :exc:`Empty` exception if no item was available " +"within that time. Otherwise (*block* is false), return an item if one is " +"immediately available, else raise the :exc:`Empty` exception (*timeout* is " +"ignored in that case)." +msgstr "" + +#: ../Doc/library/queue.rst:136 +msgid "" +"Two methods are offered to support tracking whether enqueued tasks have been " +"fully processed by daemon consumer threads." +msgstr "" + +#: ../Doc/library/queue.rst:142 +msgid "" +"Indicate that a formerly enqueued task is complete. Used by queue consumer " +"threads. For each :meth:`get` used to fetch a task, a subsequent call to :" +"meth:`task_done` tells the queue that the processing on the task is complete." +msgstr "" + +#: ../Doc/library/queue.rst:146 +msgid "" +"If a :meth:`join` is currently blocking, it will resume when all items have " +"been processed (meaning that a :meth:`task_done` call was received for every " +"item that had been :meth:`put` into the queue)." +msgstr "" + +#: ../Doc/library/queue.rst:156 +msgid "Blocks until all items in the queue have been gotten and processed." +msgstr "" + +#: ../Doc/library/queue.rst:158 +msgid "" +"The count of unfinished tasks goes up whenever an item is added to the " +"queue. The count goes down whenever a consumer thread calls :meth:" +"`task_done` to indicate that the item was retrieved and all work on it is " +"complete. When the count of unfinished tasks drops to zero, :meth:`join` " +"unblocks." +msgstr "" + +#: ../Doc/library/queue.rst:164 +msgid "Example of how to wait for enqueued tasks to be completed::" +msgstr "" + +#: ../Doc/library/queue.rst:198 +msgid "Class :class:`multiprocessing.Queue`" +msgstr "" + +#: ../Doc/library/queue.rst:197 +msgid "" +"A queue class for use in a multi-processing (rather than multi-threading) " +"context." +msgstr "" + +#: ../Doc/library/queue.rst:200 +msgid "" +":class:`collections.deque` is an alternative implementation of unbounded " +"queues with fast atomic :meth:`~collections.deque.append` and :meth:" +"`~collections.deque.popleft` operations that do not require locking." +msgstr "" + +#: ../Doc/library/quopri.rst:2 +msgid ":mod:`quopri` --- Encode and decode MIME quoted-printable data" +msgstr "" + +#: ../Doc/library/quopri.rst:7 +msgid "**Source code:** :source:`Lib/quopri.py`" +msgstr "" + +#: ../Doc/library/quopri.rst:15 +msgid "" +"This module performs quoted-printable transport encoding and decoding, as " +"defined in :rfc:`1521`: \"MIME (Multipurpose Internet Mail Extensions) Part " +"One: Mechanisms for Specifying and Describing the Format of Internet Message " +"Bodies\". The quoted-printable encoding is designed for data where there are " +"relatively few nonprintable characters; the base64 encoding scheme available " +"via the :mod:`base64` module is more compact if there are many such " +"characters, as when sending a graphics file." +msgstr "" + +#: ../Doc/library/quopri.rst:25 +msgid "" +"Decode the contents of the *input* file and write the resulting decoded " +"binary data to the *output* file. *input* and *output* must be :term:`binary " +"file objects `. If the optional argument *header* is present " +"and true, underscore will be decoded as space. This is used to decode \"Q\"-" +"encoded headers as described in :rfc:`1522`: \"MIME (Multipurpose Internet " +"Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text\"." +msgstr "" + +#: ../Doc/library/quopri.rst:35 +msgid "" +"Encode the contents of the *input* file and write the resulting quoted- " +"printable data to the *output* file. *input* and *output* must be :term:" +"`binary file objects `. *quotetabs*, a flag which controls " +"whether to encode embedded spaces and tabs must be provideda and when true " +"it encodes such embedded whitespace, and when false it leaves them " +"unencoded. Note that spaces and tabs appearing at the end of lines are " +"always encoded, as per :rfc:`1521`. *header* is a flag which controls if " +"spaces are encoded as underscores as per :rfc:`1522`." +msgstr "" + +#: ../Doc/library/quopri.rst:47 +msgid "" +"Like :func:`decode`, except that it accepts a source :class:`bytes` and " +"returns the corresponding decoded :class:`bytes`." +msgstr "" + +#: ../Doc/library/quopri.rst:53 +msgid "" +"Like :func:`encode`, except that it accepts a source :class:`bytes` and " +"returns the corresponding encoded :class:`bytes`. By default, it sends a " +"False value to *quotetabs* parameter of the :func:`encode` function." +msgstr "" + +#: ../Doc/library/quopri.rst:62 +msgid "Encode and decode MIME base64 data" +msgstr "" + +#: ../Doc/library/random.rst:2 +msgid ":mod:`random` --- Generate pseudo-random numbers" +msgstr "" + +#: ../Doc/library/random.rst:7 +msgid "**Source code:** :source:`Lib/random.py`" +msgstr "" + +#: ../Doc/library/random.rst:11 +msgid "" +"This module implements pseudo-random number generators for various " +"distributions." +msgstr "" + +#: ../Doc/library/random.rst:14 +msgid "" +"For integers, there is uniform selection from a range. For sequences, there " +"is uniform selection of a random element, a function to generate a random " +"permutation of a list in-place, and a function for random sampling without " +"replacement." +msgstr "" + +#: ../Doc/library/random.rst:19 +msgid "" +"On the real line, there are functions to compute uniform, normal (Gaussian), " +"lognormal, negative exponential, gamma, and beta distributions. For " +"generating distributions of angles, the von Mises distribution is available." +msgstr "" + +#: ../Doc/library/random.rst:23 +msgid "" +"Almost all module functions depend on the basic function :func:`.random`, " +"which generates a random float uniformly in the semi-open range [0.0, 1.0). " +"Python uses the Mersenne Twister as the core generator. It produces 53-bit " +"precision floats and has a period of 2\\*\\*19937-1. The underlying " +"implementation in C is both fast and threadsafe. The Mersenne Twister is " +"one of the most extensively tested random number generators in existence. " +"However, being completely deterministic, it is not suitable for all " +"purposes, and is completely unsuitable for cryptographic purposes." +msgstr "" + +#: ../Doc/library/random.rst:32 +msgid "" +"The functions supplied by this module are actually bound methods of a hidden " +"instance of the :class:`random.Random` class. You can instantiate your own " +"instances of :class:`Random` to get generators that don't share state." +msgstr "" + +#: ../Doc/library/random.rst:36 +msgid "" +"Class :class:`Random` can also be subclassed if you want to use a different " +"basic generator of your own devising: in that case, override the :meth:" +"`~Random.random`, :meth:`~Random.seed`, :meth:`~Random.getstate`, and :meth:" +"`~Random.setstate` methods. Optionally, a new generator can supply a :meth:" +"`~Random.getrandbits` method --- this allows :meth:`randrange` to produce " +"selections over an arbitrarily large range." +msgstr "" + +#: ../Doc/library/random.rst:42 +msgid "" +"The :mod:`random` module also provides the :class:`SystemRandom` class which " +"uses the system function :func:`os.urandom` to generate random numbers from " +"sources provided by the operating system." +msgstr "" + +#: ../Doc/library/random.rst:48 +msgid "" +"The pseudo-random generators of this module should not be used for security " +"purposes. For security or cryptographic uses, see the :mod:`secrets` module." +msgstr "" + +#: ../Doc/library/random.rst:53 +msgid "Bookkeeping functions:" +msgstr "" + +#: ../Doc/library/random.rst:57 +msgid "Initialize the random number generator." +msgstr "" + +#: ../Doc/library/random.rst:59 +msgid "" +"If *a* is omitted or ``None``, the current system time is used. If " +"randomness sources are provided by the operating system, they are used " +"instead of the system time (see the :func:`os.urandom` function for details " +"on availability)." +msgstr "" + +#: ../Doc/library/random.rst:64 +msgid "If *a* is an int, it is used directly." +msgstr "" + +#: ../Doc/library/random.rst:66 +msgid "" +"With version 2 (the default), a :class:`str`, :class:`bytes`, or :class:" +"`bytearray` object gets converted to an :class:`int` and all of its bits are " +"used." +msgstr "" + +#: ../Doc/library/random.rst:69 +msgid "" +"With version 1 (provided for reproducing random sequences from older " +"versions of Python), the algorithm for :class:`str` and :class:`bytes` " +"generates a narrower range of seeds." +msgstr "" + +#: ../Doc/library/random.rst:73 +msgid "" +"Moved to the version 2 scheme which uses all of the bits in a string seed." +msgstr "" + +#: ../Doc/library/random.rst:78 +msgid "" +"Return an object capturing the current internal state of the generator. " +"This object can be passed to :func:`setstate` to restore the state." +msgstr "" + +#: ../Doc/library/random.rst:84 +msgid "" +"*state* should have been obtained from a previous call to :func:`getstate`, " +"and :func:`setstate` restores the internal state of the generator to what it " +"was at the time :func:`getstate` was called." +msgstr "" + +#: ../Doc/library/random.rst:91 +msgid "" +"Returns a Python integer with *k* random bits. This method is supplied with " +"the MersenneTwister generator and some other generators may also provide it " +"as an optional part of the API. When available, :meth:`getrandbits` enables :" +"meth:`randrange` to handle arbitrarily large ranges." +msgstr "" + +#: ../Doc/library/random.rst:97 +msgid "Functions for integers:" +msgstr "" + +#: ../Doc/library/random.rst:102 +msgid "" +"Return a randomly selected element from ``range(start, stop, step)``. This " +"is equivalent to ``choice(range(start, stop, step))``, but doesn't actually " +"build a range object." +msgstr "" + +#: ../Doc/library/random.rst:106 +msgid "" +"The positional argument pattern matches that of :func:`range`. Keyword " +"arguments should not be used because the function may use them in unexpected " +"ways." +msgstr "" + +#: ../Doc/library/random.rst:109 +msgid "" +":meth:`randrange` is more sophisticated about producing equally distributed " +"values. Formerly it used a style like ``int(random()*n)`` which could " +"produce slightly uneven distributions." +msgstr "" + +#: ../Doc/library/random.rst:116 +msgid "" +"Return a random integer *N* such that ``a <= N <= b``. Alias for " +"``randrange(a, b+1)``." +msgstr "" + +#: ../Doc/library/random.rst:120 +msgid "Functions for sequences:" +msgstr "" + +#: ../Doc/library/random.rst:124 +msgid "" +"Return a random element from the non-empty sequence *seq*. If *seq* is " +"empty, raises :exc:`IndexError`." +msgstr "" + +#: ../Doc/library/random.rst:129 +msgid "" +"Return a *k* sized list of elements chosen from the *population* with " +"replacement. If the *population* is empty, raises :exc:`IndexError`." +msgstr "" + +#: ../Doc/library/random.rst:132 +msgid "" +"If a *weights* sequence is specified, selections are made according to the " +"relative weights. Alternatively, if a *cum_weights* sequence is given, the " +"selections are made according to the cumulative weights (perhaps computed " +"using :func:`itertools.accumulate`). For example, the relative weights " +"``[10, 5, 30, 5]`` are equivalent to the cumulative weights ``[10, 15, 45, " +"50]``. Internally, the relative weights are converted to cumulative weights " +"before making selections, so supplying the cumulative weights saves work." +msgstr "" + +#: ../Doc/library/random.rst:141 +msgid "" +"If neither *weights* nor *cum_weights* are specified, selections are made " +"with equal probability. If a weights sequence is supplied, it must be the " +"same length as the *population* sequence. It is a :exc:`TypeError` to " +"specify both *weights* and *cum_weights*." +msgstr "" + +#: ../Doc/library/random.rst:146 +msgid "" +"The *weights* or *cum_weights* can use any numeric type that interoperates " +"with the :class:`float` values returned by :func:`random` (that includes " +"integers, floats, and fractions but excludes decimals)." +msgstr "" + +#: ../Doc/library/random.rst:155 +msgid "" +"Shuffle the sequence *x* in place. The optional argument *random* is a 0-" +"argument function returning a random float in [0.0, 1.0); by default, this " +"is the function :func:`.random`." +msgstr "" + +#: ../Doc/library/random.rst:159 +msgid "" +"Note that for even rather small ``len(x)``, the total number of permutations " +"of *x* is larger than the period of most random number generators; this " +"implies that most permutations of a long sequence can never be generated." +msgstr "" + +#: ../Doc/library/random.rst:166 +msgid "" +"Return a *k* length list of unique elements chosen from the population " +"sequence or set. Used for random sampling without replacement." +msgstr "" + +#: ../Doc/library/random.rst:169 +msgid "" +"Returns a new list containing elements from the population while leaving the " +"original population unchanged. The resulting list is in selection order so " +"that all sub-slices will also be valid random samples. This allows raffle " +"winners (the sample) to be partitioned into grand prize and second place " +"winners (the subslices)." +msgstr "" + +#: ../Doc/library/random.rst:175 +msgid "" +"Members of the population need not be :term:`hashable` or unique. If the " +"population contains repeats, then each occurrence is a possible selection in " +"the sample." +msgstr "" + +#: ../Doc/library/random.rst:178 +msgid "" +"To choose a sample from a range of integers, use an :func:`range` object as " +"an argument. This is especially fast and space efficient for sampling from " +"a large population: ``sample(range(10000000), 60)``." +msgstr "" + +#: ../Doc/library/random.rst:182 +msgid "" +"If the sample size is larger than the population size, a :exc:`ValueError` " +"is raised." +msgstr "" + +#: ../Doc/library/random.rst:185 +msgid "" +"The following functions generate specific real-valued distributions. " +"Function parameters are named after the corresponding variables in the " +"distribution's equation, as used in common mathematical practice; most of " +"these equations can be found in any statistics text." +msgstr "" + +#: ../Doc/library/random.rst:193 +msgid "Return the next random floating point number in the range [0.0, 1.0)." +msgstr "" + +#: ../Doc/library/random.rst:198 +msgid "" +"Return a random floating point number *N* such that ``a <= N <= b`` for ``a " +"<= b`` and ``b <= N <= a`` for ``b < a``." +msgstr "" + +#: ../Doc/library/random.rst:201 +msgid "" +"The end-point value ``b`` may or may not be included in the range depending " +"on floating-point rounding in the equation ``a + (b-a) * random()``." +msgstr "" + +#: ../Doc/library/random.rst:207 +msgid "" +"Return a random floating point number *N* such that ``low <= N <= high`` and " +"with the specified *mode* between those bounds. The *low* and *high* bounds " +"default to zero and one. The *mode* argument defaults to the midpoint " +"between the bounds, giving a symmetric distribution." +msgstr "" + +#: ../Doc/library/random.rst:215 +msgid "" +"Beta distribution. Conditions on the parameters are ``alpha > 0`` and " +"``beta > 0``. Returned values range between 0 and 1." +msgstr "" + +#: ../Doc/library/random.rst:221 +msgid "" +"Exponential distribution. *lambd* is 1.0 divided by the desired mean. It " +"should be nonzero. (The parameter would be called \"lambda\", but that is a " +"reserved word in Python.) Returned values range from 0 to positive infinity " +"if *lambd* is positive, and from negative infinity to 0 if *lambd* is " +"negative." +msgstr "" + +#: ../Doc/library/random.rst:230 +msgid "" +"Gamma distribution. (*Not* the gamma function!) Conditions on the " +"parameters are ``alpha > 0`` and ``beta > 0``." +msgstr "" + +#: ../Doc/library/random.rst:233 +msgid "The probability distribution function is::" +msgstr "" + +#: ../Doc/library/random.rst:242 +msgid "" +"Gaussian distribution. *mu* is the mean, and *sigma* is the standard " +"deviation. This is slightly faster than the :func:`normalvariate` function " +"defined below." +msgstr "" + +#: ../Doc/library/random.rst:249 +msgid "" +"Log normal distribution. If you take the natural logarithm of this " +"distribution, you'll get a normal distribution with mean *mu* and standard " +"deviation *sigma*. *mu* can have any value, and *sigma* must be greater " +"than zero." +msgstr "" + +#: ../Doc/library/random.rst:257 +msgid "" +"Normal distribution. *mu* is the mean, and *sigma* is the standard " +"deviation." +msgstr "" + +#: ../Doc/library/random.rst:262 +msgid "" +"*mu* is the mean angle, expressed in radians between 0 and 2\\*\\ *pi*, and " +"*kappa* is the concentration parameter, which must be greater than or equal " +"to zero. If *kappa* is equal to zero, this distribution reduces to a " +"uniform random angle over the range 0 to 2\\*\\ *pi*." +msgstr "" + +#: ../Doc/library/random.rst:270 +msgid "Pareto distribution. *alpha* is the shape parameter." +msgstr "" + +#: ../Doc/library/random.rst:275 +msgid "" +"Weibull distribution. *alpha* is the scale parameter and *beta* is the " +"shape parameter." +msgstr "" + +#: ../Doc/library/random.rst:279 +msgid "Alternative Generator:" +msgstr "" + +#: ../Doc/library/random.rst:283 +msgid "" +"Class that uses the :func:`os.urandom` function for generating random " +"numbers from sources provided by the operating system. Not available on all " +"systems. Does not rely on software state, and sequences are not " +"reproducible. Accordingly, the :meth:`seed` method has no effect and is " +"ignored. The :meth:`getstate` and :meth:`setstate` methods raise :exc:" +"`NotImplementedError` if called." +msgstr "" + +#: ../Doc/library/random.rst:293 +msgid "" +"M. Matsumoto and T. Nishimura, \"Mersenne Twister: A 623-dimensionally " +"equidistributed uniform pseudorandom number generator\", ACM Transactions on " +"Modeling and Computer Simulation Vol. 8, No. 1, January pp.3-30 1998." +msgstr "" + +#: ../Doc/library/random.rst:298 +msgid "" +"`Complementary-Multiply-with-Carry recipe `_ for a compatible alternative random number generator with " +"a long period and comparatively simple update operations." +msgstr "" + +#: ../Doc/library/random.rst:305 +msgid "Notes on Reproducibility" +msgstr "" + +#: ../Doc/library/random.rst:307 +msgid "" +"Sometimes it is useful to be able to reproduce the sequences given by a " +"pseudo random number generator. By re-using a seed value, the same sequence " +"should be reproducible from run to run as long as multiple threads are not " +"running." +msgstr "" + +#: ../Doc/library/random.rst:311 +msgid "" +"Most of the random module's algorithms and seeding functions are subject to " +"change across Python versions, but two aspects are guaranteed not to change:" +msgstr "" + +#: ../Doc/library/random.rst:314 +msgid "" +"If a new seeding method is added, then a backward compatible seeder will be " +"offered." +msgstr "" + +#: ../Doc/library/random.rst:317 +msgid "" +"The generator's :meth:`~Random.random` method will continue to produce the " +"same sequence when the compatible seeder is given the same seed." +msgstr "" + +#: ../Doc/library/random.rst:325 +msgid "Basic usage::" +msgstr "" + +#: ../Doc/library/random.rst:354 +msgid "" +"Example of `statistical bootstrapping `_ using resampling with replacement to estimate " +"a confidence interval for the mean of a small sample of size five::" +msgstr "" + +#: ../Doc/library/re.rst:2 +msgid ":mod:`re` --- Regular expression operations" +msgstr "" + +#: ../Doc/library/re.rst:10 +msgid "**Source code:** :source:`Lib/re.py`" +msgstr "" + +#: ../Doc/library/re.rst:14 +msgid "" +"This module provides regular expression matching operations similar to those " +"found in Perl." +msgstr "" + +#: ../Doc/library/re.rst:17 +msgid "" +"Both patterns and strings to be searched can be Unicode strings as well as 8-" +"bit strings. However, Unicode strings and 8-bit strings cannot be mixed: " +"that is, you cannot match a Unicode string with a byte pattern or vice-" +"versa; similarly, when asking for a substitution, the replacement string " +"must be of the same type as both the pattern and the search string." +msgstr "" + +#: ../Doc/library/re.rst:23 +msgid "" +"Regular expressions use the backslash character (``'\\'``) to indicate " +"special forms or to allow special characters to be used without invoking " +"their special meaning. This collides with Python's usage of the same " +"character for the same purpose in string literals; for example, to match a " +"literal backslash, one might have to write ``'\\\\\\\\'`` as the pattern " +"string, because the regular expression must be ``\\\\``, and each backslash " +"must be expressed as ``\\\\`` inside a regular Python string literal." +msgstr "" + +#: ../Doc/library/re.rst:32 +msgid "" +"The solution is to use Python's raw string notation for regular expression " +"patterns; backslashes are not handled in any special way in a string literal " +"prefixed with ``'r'``. So ``r\"\\n\"`` is a two-character string containing " +"``'\\'`` and ``'n'``, while ``\"\\n\"`` is a one-character string containing " +"a newline. Usually patterns will be expressed in Python code using this raw " +"string notation." +msgstr "" + +#: ../Doc/library/re.rst:39 +msgid "" +"It is important to note that most regular expression operations are " +"available as module-level functions and methods on :ref:`compiled regular " +"expressions `. The functions are shortcuts that don't require " +"you to compile a regex object first, but miss some fine-tuning parameters." +msgstr "" + +#: ../Doc/library/re.rst:49 +msgid "Regular Expression Syntax" +msgstr "" + +#: ../Doc/library/re.rst:51 +msgid "" +"A regular expression (or RE) specifies a set of strings that matches it; the " +"functions in this module let you check if a particular string matches a " +"given regular expression (or if a given regular expression matches a " +"particular string, which comes down to the same thing)." +msgstr "" + +#: ../Doc/library/re.rst:56 +msgid "" +"Regular expressions can be concatenated to form new regular expressions; if " +"*A* and *B* are both regular expressions, then *AB* is also a regular " +"expression. In general, if a string *p* matches *A* and another string *q* " +"matches *B*, the string *pq* will match AB. This holds unless *A* or *B* " +"contain low precedence operations; boundary conditions between *A* and *B*; " +"or have numbered group references. Thus, complex expressions can easily be " +"constructed from simpler primitive expressions like the ones described " +"here. For details of the theory and implementation of regular expressions, " +"consult the Friedl book referenced above, or almost any textbook about " +"compiler construction." +msgstr "" + +#: ../Doc/library/re.rst:66 +msgid "" +"A brief explanation of the format of regular expressions follows. For " +"further information and a gentler presentation, consult the :ref:`regex-" +"howto`." +msgstr "" + +#: ../Doc/library/re.rst:69 +msgid "" +"Regular expressions can contain both special and ordinary characters. Most " +"ordinary characters, like ``'A'``, ``'a'``, or ``'0'``, are the simplest " +"regular expressions; they simply match themselves. You can concatenate " +"ordinary characters, so ``last`` matches the string ``'last'``. (In the " +"rest of this section, we'll write RE's in ``this special style``, usually " +"without quotes, and strings to be matched ``'in single quotes'``.)" +msgstr "" + +#: ../Doc/library/re.rst:76 +msgid "" +"Some characters, like ``'|'`` or ``'('``, are special. Special characters " +"either stand for classes of ordinary characters, or affect how the regular " +"expressions around them are interpreted. Regular expression pattern strings " +"may not contain null bytes, but can specify the null byte using a ``" +"\\number`` notation such as ``'\\x00'``." +msgstr "" + +#: ../Doc/library/re.rst:82 +msgid "" +"Repetition qualifiers (``*``, ``+``, ``?``, ``{m,n}``, etc) cannot be " +"directly nested. This avoids ambiguity with the non-greedy modifier suffix " +"``?``, and with other modifiers in other implementations. To apply a second " +"repetition to an inner repetition, parentheses may be used. For example, the " +"expression ``(?:a{6})*`` matches any multiple of six ``'a'`` characters." +msgstr "" + +#: ../Doc/library/re.rst:89 +msgid "The special characters are:" +msgstr "" + +#: ../Doc/library/re.rst:94 +msgid "``'.'``" +msgstr "" + +#: ../Doc/library/re.rst:92 +msgid "" +"(Dot.) In the default mode, this matches any character except a newline. " +"If the :const:`DOTALL` flag has been specified, this matches any character " +"including a newline." +msgstr "" + +#: ../Doc/library/re.rst:98 ../Doc/library/string.rst:338 +msgid "``'^'``" +msgstr "" + +#: ../Doc/library/re.rst:97 +msgid "" +"(Caret.) Matches the start of the string, and in :const:`MULTILINE` mode " +"also matches immediately after each newline." +msgstr "" + +#: ../Doc/library/re.rst:107 +msgid "``'$'``" +msgstr "" + +#: ../Doc/library/re.rst:101 +msgid "" +"Matches the end of the string or just before the newline at the end of the " +"string, and in :const:`MULTILINE` mode also matches before a newline. " +"``foo`` matches both 'foo' and 'foobar', while the regular expression ``foo" +"$`` matches only 'foo'. More interestingly, searching for ``foo.$`` in " +"``'foo1\\nfoo2\\n'`` matches 'foo2' normally, but 'foo1' in :const:" +"`MULTILINE` mode; searching for a single ``$`` in ``'foo\\n'`` will find two " +"(empty) matches: one just before the newline, and one at the end of the " +"string." +msgstr "" + +#: ../Doc/library/re.rst:112 +msgid "``'*'``" +msgstr "" + +#: ../Doc/library/re.rst:110 +msgid "" +"Causes the resulting RE to match 0 or more repetitions of the preceding RE, " +"as many repetitions as are possible. ``ab*`` will match 'a', 'ab', or 'a' " +"followed by any number of 'b's." +msgstr "" + +#: ../Doc/library/re.rst:115 +msgid "" +"Causes the resulting RE to match 1 or more repetitions of the preceding RE. " +"``ab+`` will match 'a' followed by any non-zero number of 'b's; it will not " +"match just 'a'." +msgstr "" + +#: ../Doc/library/re.rst:121 +msgid "``'?'``" +msgstr "" + +#: ../Doc/library/re.rst:120 +msgid "" +"Causes the resulting RE to match 0 or 1 repetitions of the preceding RE. " +"``ab?`` will match either 'a' or 'ab'." +msgstr "" + +#: ../Doc/library/re.rst:130 +msgid "``*?``, ``+?``, ``??``" +msgstr "" + +#: ../Doc/library/re.rst:124 +msgid "" +"The ``'*'``, ``'+'``, and ``'?'`` qualifiers are all :dfn:`greedy`; they " +"match as much text as possible. Sometimes this behaviour isn't desired; if " +"the RE ``<.*>`` is matched against `` b ``, it will match the entire " +"string, and not just ````. Adding ``?`` after the qualifier makes it " +"perform the match in :dfn:`non-greedy` or :dfn:`minimal` fashion; as *few* " +"characters as possible will be matched. Using the RE ``<.*?>`` will match " +"only ````." +msgstr "" + +#: ../Doc/library/re.rst:135 +msgid "``{m}``" +msgstr "" + +#: ../Doc/library/re.rst:133 +msgid "" +"Specifies that exactly *m* copies of the previous RE should be matched; " +"fewer matches cause the entire RE not to match. For example, ``a{6}`` will " +"match exactly six ``'a'`` characters, but not five." +msgstr "" + +#: ../Doc/library/re.rst:144 +msgid "``{m,n}``" +msgstr "" + +#: ../Doc/library/re.rst:138 +msgid "" +"Causes the resulting RE to match from *m* to *n* repetitions of the " +"preceding RE, attempting to match as many repetitions as possible. For " +"example, ``a{3,5}`` will match from 3 to 5 ``'a'`` characters. Omitting *m* " +"specifies a lower bound of zero, and omitting *n* specifies an infinite " +"upper bound. As an example, ``a{4,}b`` will match ``aaaab`` or a thousand " +"``'a'`` characters followed by a ``b``, but not ``aaab``. The comma may not " +"be omitted or the modifier would be confused with the previously described " +"form." +msgstr "" + +#: ../Doc/library/re.rst:151 +msgid "``{m,n}?``" +msgstr "" + +#: ../Doc/library/re.rst:147 +msgid "" +"Causes the resulting RE to match from *m* to *n* repetitions of the " +"preceding RE, attempting to match as *few* repetitions as possible. This is " +"the non-greedy version of the previous qualifier. For example, on the 6-" +"character string ``'aaaaaa'``, ``a{3,5}`` will match 5 ``'a'`` characters, " +"while ``a{3,5}?`` will only match 3 characters." +msgstr "" + +#: ../Doc/library/re.rst:164 +msgid "``'\\'``" +msgstr "" + +#: ../Doc/library/re.rst:154 +msgid "" +"Either escapes special characters (permitting you to match characters like " +"``'*'``, ``'?'``, and so forth), or signals a special sequence; special " +"sequences are discussed below." +msgstr "" + +#: ../Doc/library/re.rst:158 +msgid "" +"If you're not using a raw string to express the pattern, remember that " +"Python also uses the backslash as an escape sequence in string literals; if " +"the escape sequence isn't recognized by Python's parser, the backslash and " +"subsequent character are included in the resulting string. However, if " +"Python would recognize the resulting sequence, the backslash should be " +"repeated twice. This is complicated and hard to understand, so it's highly " +"recommended that you use raw strings for all but the simplest expressions." +msgstr "" + +#: ../Doc/library/re.rst:196 +msgid "``[]``" +msgstr "" + +#: ../Doc/library/re.rst:167 +msgid "Used to indicate a set of characters. In a set:" +msgstr "" + +#: ../Doc/library/re.rst:169 +msgid "" +"Characters can be listed individually, e.g. ``[amk]`` will match ``'a'``, " +"``'m'``, or ``'k'``." +msgstr "" + +#: ../Doc/library/re.rst:172 +msgid "" +"Ranges of characters can be indicated by giving two characters and " +"separating them by a ``'-'``, for example ``[a-z]`` will match any lowercase " +"ASCII letter, ``[0-5][0-9]`` will match all the two-digits numbers from " +"``00`` to ``59``, and ``[0-9A-Fa-f]`` will match any hexadecimal digit. If " +"``-`` is escaped (e.g. ``[a\\-z]``) or if it's placed as the first or last " +"character (e.g. ``[a-]``), it will match a literal ``'-'``." +msgstr "" + +#: ../Doc/library/re.rst:179 +msgid "" +"Special characters lose their special meaning inside sets. For example, " +"``[(+*)]`` will match any of the literal characters ``'('``, ``'+'``, " +"``'*'``, or ``')'``." +msgstr "" + +#: ../Doc/library/re.rst:183 +msgid "" +"Character classes such as ``\\w`` or ``\\S`` (defined below) are also " +"accepted inside a set, although the characters they match depends on " +"whether :const:`ASCII` or :const:`LOCALE` mode is in force." +msgstr "" + +#: ../Doc/library/re.rst:187 +msgid "" +"Characters that are not within a range can be matched by :dfn:" +"`complementing` the set. If the first character of the set is ``'^'``, all " +"the characters that are *not* in the set will be matched. For example, " +"``[^5]`` will match any character except ``'5'``, and ``[^^]`` will match " +"any character except ``'^'``. ``^`` has no special meaning if it's not the " +"first character in the set." +msgstr "" + +#: ../Doc/library/re.rst:194 +msgid "" +"To match a literal ``']'`` inside a set, precede it with a backslash, or " +"place it at the beginning of the set. For example, both ``[()[\\]{}]`` and " +"``[]()[{}]`` will both match a parenthesis." +msgstr "" + +#: ../Doc/library/re.rst:207 +msgid "``'|'``" +msgstr "" + +#: ../Doc/library/re.rst:199 +msgid "" +"``A|B``, where A and B can be arbitrary REs, creates a regular expression " +"that will match either A or B. An arbitrary number of REs can be separated " +"by the ``'|'`` in this way. This can be used inside groups (see below) as " +"well. As the target string is scanned, REs separated by ``'|'`` are tried " +"from left to right. When one pattern completely matches, that branch is " +"accepted. This means that once ``A`` matches, ``B`` will not be tested " +"further, even if it would produce a longer overall match. In other words, " +"the ``'|'`` operator is never greedy. To match a literal ``'|'``, use ``\\|" +"``, or enclose it inside a character class, as in ``[|]``." +msgstr "" + +#: ../Doc/library/re.rst:214 +msgid "``(...)``" +msgstr "" + +#: ../Doc/library/re.rst:210 +msgid "" +"Matches whatever regular expression is inside the parentheses, and indicates " +"the start and end of a group; the contents of a group can be retrieved after " +"a match has been performed, and can be matched later in the string with the " +"``\\number`` special sequence, described below. To match the literals " +"``'('`` or ``')'``, use ``\\(`` or ``\\)``, or enclose them inside a " +"character class: ``[(] [)]``." +msgstr "" + +#: ../Doc/library/re.rst:221 +msgid "``(?...)``" +msgstr "" + +#: ../Doc/library/re.rst:217 +msgid "" +"This is an extension notation (a ``'?'`` following a ``'('`` is not " +"meaningful otherwise). The first character after the ``'?'`` determines " +"what the meaning and further syntax of the construct is. Extensions usually " +"do not create a new group; ``(?P...)`` is the only exception to this " +"rule. Following are the currently supported extensions." +msgstr "" + +#: ../Doc/library/re.rst:234 +msgid "``(?aiLmsux)``" +msgstr "" + +#: ../Doc/library/re.rst:224 +msgid "" +"(One or more letters from the set ``'a'``, ``'i'``, ``'L'``, ``'m'``, " +"``'s'``, ``'u'``, ``'x'``.) The group matches the empty string; the letters " +"set the corresponding flags: :const:`re.A` (ASCII-only matching), :const:`re." +"I` (ignore case), :const:`re.L` (locale dependent), :const:`re.M` (multi-" +"line), :const:`re.S` (dot matches all), and :const:`re.X` (verbose), for the " +"entire regular expression. (The flags are described in :ref:`contents-of-" +"module-re`.) This is useful if you wish to include the flags as part of the " +"regular expression, instead of passing a *flag* argument to the :func:`re." +"compile` function. Flags should be used first in the expression string." +msgstr "" + +#: ../Doc/library/re.rst:240 +msgid "``(?:...)``" +msgstr "" + +#: ../Doc/library/re.rst:237 +msgid "" +"A non-capturing version of regular parentheses. Matches whatever regular " +"expression is inside the parentheses, but the substring matched by the group " +"*cannot* be retrieved after performing a match or referenced later in the " +"pattern." +msgstr "" + +#: ../Doc/library/re.rst:250 +msgid "``(?imsx-imsx:...)``" +msgstr "" + +#: ../Doc/library/re.rst:243 +msgid "" +"(Zero or more letters from the set ``'i'``, ``'m'``, ``'s'``, ``'x'``, " +"optionally followed by ``'-'`` followed by one or more letters from the same " +"set.) The letters set or removes the corresponding flags: :const:`re.I` " +"(ignore case), :const:`re.M` (multi-line), :const:`re.S` (dot matches all), " +"and :const:`re.X` (verbose), for the part of the expression. (The flags are " +"described in :ref:`contents-of-module-re`.)" +msgstr "" + +#: ../Doc/library/re.rst:275 +msgid "``(?P...)``" +msgstr "" + +#: ../Doc/library/re.rst:253 +msgid "" +"Similar to regular parentheses, but the substring matched by the group is " +"accessible via the symbolic group name *name*. Group names must be valid " +"Python identifiers, and each group name must be defined only once within a " +"regular expression. A symbolic group is also a numbered group, just as if " +"the group were not named." +msgstr "" + +#: ../Doc/library/re.rst:259 +msgid "" +"Named groups can be referenced in three contexts. If the pattern is ``(?" +"P['\"]).*?(?P=quote)`` (i.e. matching a string quoted with either " +"single or double quotes):" +msgstr "" + +#: ../Doc/library/re.rst:264 +msgid "Context of reference to group \"quote\"" +msgstr "" + +#: ../Doc/library/re.rst:264 +msgid "Ways to reference it" +msgstr "" + +#: ../Doc/library/re.rst:266 +msgid "in the same pattern itself" +msgstr "" + +#: ../Doc/library/re.rst:266 +msgid "``(?P=quote)`` (as shown)" +msgstr "" + +#: ../Doc/library/re.rst:267 ../Doc/library/re.rst:274 +msgid "``\\1``" +msgstr "" + +#: ../Doc/library/re.rst:269 +msgid "when processing match object ``m``" +msgstr "" + +#: ../Doc/library/re.rst:269 +msgid "``m.group('quote')``" +msgstr "" + +#: ../Doc/library/re.rst:270 +msgid "``m.end('quote')`` (etc.)" +msgstr "" + +#: ../Doc/library/re.rst:272 +msgid "in a string passed to the ``repl`` argument of ``re.sub()``" +msgstr "" + +#: ../Doc/library/re.rst:272 +msgid "``\\g``" +msgstr "" + +#: ../Doc/library/re.rst:273 +msgid "``\\g<1>``" +msgstr "" + +#: ../Doc/library/re.rst:279 +msgid "``(?P=name)``" +msgstr "" + +#: ../Doc/library/re.rst:278 +msgid "" +"A backreference to a named group; it matches whatever text was matched by " +"the earlier group named *name*." +msgstr "" + +#: ../Doc/library/re.rst:282 +msgid "``(?#...)``" +msgstr "" + +#: ../Doc/library/re.rst:282 +msgid "A comment; the contents of the parentheses are simply ignored." +msgstr "" + +#: ../Doc/library/re.rst:287 +msgid "``(?=...)``" +msgstr "" + +#: ../Doc/library/re.rst:285 +msgid "" +"Matches if ``...`` matches next, but doesn't consume any of the string. " +"This is called a lookahead assertion. For example, ``Isaac (?=Asimov)`` " +"will match ``'Isaac '`` only if it's followed by ``'Asimov'``." +msgstr "" + +#: ../Doc/library/re.rst:292 +msgid "``(?!...)``" +msgstr "" + +#: ../Doc/library/re.rst:290 +msgid "" +"Matches if ``...`` doesn't match next. This is a negative lookahead " +"assertion. For example, ``Isaac (?!Asimov)`` will match ``'Isaac '`` only if " +"it's *not* followed by ``'Asimov'``." +msgstr "" + +#: ../Doc/library/re.rst:317 +msgid "``(?<=...)``" +msgstr "" + +#: ../Doc/library/re.rst:295 +msgid "" +"Matches if the current position in the string is preceded by a match for " +"``...`` that ends at the current position. This is called a :dfn:`positive " +"lookbehind assertion`. ``(?<=abc)def`` will find a match in ``abcdef``, " +"since the lookbehind will back up 3 characters and check if the contained " +"pattern matches. The contained pattern must only match strings of some fixed " +"length, meaning that ``abc`` or ``a|b`` are allowed, but ``a*`` and ``a{3,4}" +"`` are not. Note that patterns which start with positive lookbehind " +"assertions will not match at the beginning of the string being searched; you " +"will most likely want to use the :func:`search` function rather than the :" +"func:`match` function:" +msgstr "" + +#: ../Doc/library/re.rst:310 +msgid "This example looks for a word following a hyphen:" +msgstr "" + +#: ../Doc/library/re.rst:316 +msgid "Added support for group references of fixed length." +msgstr "" + +#: ../Doc/library/re.rst:324 +msgid "``(?|$)`` is a poor email matching pattern, which will match with " +"``''`` as well as ``'user@host.com'``, but not with " +"``''``." +msgstr "" + +#: ../Doc/library/re.rst:335 +msgid "" +"The special sequences consist of ``'\\'`` and a character from the list " +"below. If the ordinary character is not an ASCII digit or an ASCII letter, " +"then the resulting RE will match the second character. For example, ``\\$`` " +"matches the character ``'$'``." +msgstr "" + +#: ../Doc/library/re.rst:348 +msgid "``\\number``" +msgstr "" + +#: ../Doc/library/re.rst:341 +msgid "" +"Matches the contents of the group of the same number. Groups are numbered " +"starting from 1. For example, ``(.+) \\1`` matches ``'the the'`` or ``'55 " +"55'``, but not ``'thethe'`` (note the space after the group). This special " +"sequence can only be used to match one of the first 99 groups. If the first " +"digit of *number* is 0, or *number* is 3 octal digits long, it will not be " +"interpreted as a group match, but as the character with octal value " +"*number*. Inside the ``'['`` and ``']'`` of a character class, all numeric " +"escapes are treated as characters." +msgstr "" + +#: ../Doc/library/re.rst:351 +msgid "``\\A``" +msgstr "" + +#: ../Doc/library/re.rst:351 +msgid "Matches only at the start of the string." +msgstr "" + +#: ../Doc/library/re.rst:366 +msgid "``\\b``" +msgstr "" + +#: ../Doc/library/re.rst:354 +msgid "" +"Matches the empty string, but only at the beginning or end of a word. A word " +"is defined as a sequence of Unicode alphanumeric or underscore characters, " +"so the end of a word is indicated by whitespace or a non-alphanumeric, non-" +"underscore Unicode character. Note that formally, ``\\b`` is defined as the " +"boundary between a ``\\w`` and a ``\\W`` character (or vice versa), or " +"between ``\\w`` and the beginning/end of the string. This means that " +"``r'\\bfoo\\b'`` matches ``'foo'``, ``'foo.'``, ``'(foo)'``, ``'bar foo " +"baz'`` but not ``'foobar'`` or ``'foo3'``." +msgstr "" + +#: ../Doc/library/re.rst:363 +msgid "" +"By default Unicode alphanumerics are the ones used, but this can be changed " +"by using the :const:`ASCII` flag. Inside a character range, ``\\b`` " +"represents the backspace character, for compatibility with Python's string " +"literals." +msgstr "" + +#: ../Doc/library/re.rst:374 +msgid "``\\B``" +msgstr "" + +#: ../Doc/library/re.rst:369 +msgid "" +"Matches the empty string, but only when it is *not* at the beginning or end " +"of a word. This means that ``r'py\\B'`` matches ``'python'``, ``'py3'``, " +"``'py2'``, but not ``'py'``, ``'py.'``, or ``'py!'``. ``\\B`` is just the " +"opposite of ``\\b``, so word characters are Unicode alphanumerics or the " +"underscore, although this can be changed by using the :const:`ASCII` flag." +msgstr "" + +#: ../Doc/library/re.rst:385 +msgid "``\\d``" +msgstr "" + +#: ../Doc/library/re.rst:382 ../Doc/library/re.rst:402 +#: ../Doc/library/re.rst:421 +msgid "For Unicode (str) patterns:" +msgstr "" + +#: ../Doc/library/re.rst:378 +msgid "" +"Matches any Unicode decimal digit (that is, any character in Unicode " +"character category [Nd]). This includes ``[0-9]``, and also many other " +"digit characters. If the :const:`ASCII` flag is used only ``[0-9]`` is " +"matched (but the flag affects the entire regular expression, so in such " +"cases using an explicit ``[0-9]`` may be a better choice)." +msgstr "" + +#: ../Doc/library/re.rst:385 ../Doc/library/re.rst:406 +#: ../Doc/library/re.rst:425 +msgid "For 8-bit (bytes) patterns:" +msgstr "" + +#: ../Doc/library/re.rst:385 +msgid "Matches any decimal digit; this is equivalent to ``[0-9]``." +msgstr "" + +#: ../Doc/library/re.rst:392 +msgid "``\\D``" +msgstr "" + +#: ../Doc/library/re.rst:388 +msgid "" +"Matches any character which is not a Unicode decimal digit. This is the " +"opposite of ``\\d``. If the :const:`ASCII` flag is used this becomes the " +"equivalent of ``[^0-9]`` (but the flag affects the entire regular " +"expression, so in such cases using an explicit ``[^0-9]`` may be a better " +"choice)." +msgstr "" + +#: ../Doc/library/re.rst:406 +msgid "``\\s``" +msgstr "" + +#: ../Doc/library/re.rst:396 +msgid "" +"Matches Unicode whitespace characters (which includes ``[ \\t\\n\\r\\f" +"\\v]``, and also many other characters, for example the non-breaking spaces " +"mandated by typography rules in many languages). If the :const:`ASCII` flag " +"is used, only ``[ \\t\\n\\r\\f\\v]`` is matched (but the flag affects the " +"entire regular expression, so in such cases using an explicit ``[ \\t\\n\\r" +"\\f\\v]`` may be a better choice)." +msgstr "" + +#: ../Doc/library/re.rst:405 +msgid "" +"Matches characters considered whitespace in the ASCII character set; this is " +"equivalent to ``[ \\t\\n\\r\\f\\v]``." +msgstr "" + +#: ../Doc/library/re.rst:413 +msgid "``\\S``" +msgstr "" + +#: ../Doc/library/re.rst:409 +msgid "" +"Matches any character which is not a Unicode whitespace character. This is " +"the opposite of ``\\s``. If the :const:`ASCII` flag is used this becomes the " +"equivalent of ``[^ \\t\\n\\r\\f\\v]`` (but the flag affects the entire " +"regular expression, so in such cases using an explicit ``[^ \\t\\n\\r\\f" +"\\v]`` may be a better choice)." +msgstr "" + +#: ../Doc/library/re.rst:425 +msgid "``\\w``" +msgstr "" + +#: ../Doc/library/re.rst:417 +msgid "" +"Matches Unicode word characters; this includes most characters that can be " +"part of a word in any language, as well as numbers and the underscore. If " +"the :const:`ASCII` flag is used, only ``[a-zA-Z0-9_]`` is matched (but the " +"flag affects the entire regular expression, so in such cases using an " +"explicit ``[a-zA-Z0-9_]`` may be a better choice)." +msgstr "" + +#: ../Doc/library/re.rst:424 +msgid "" +"Matches characters considered alphanumeric in the ASCII character set; this " +"is equivalent to ``[a-zA-Z0-9_]``." +msgstr "" + +#: ../Doc/library/re.rst:432 +msgid "``\\W``" +msgstr "" + +#: ../Doc/library/re.rst:428 +msgid "" +"Matches any character which is not a Unicode word character. This is the " +"opposite of ``\\w``. If the :const:`ASCII` flag is used this becomes the " +"equivalent of ``[^a-zA-Z0-9_]`` (but the flag affects the entire regular " +"expression, so in such cases using an explicit ``[^a-zA-Z0-9_]`` may be a " +"better choice)." +msgstr "" + +#: ../Doc/library/re.rst:435 +msgid "``\\Z``" +msgstr "" + +#: ../Doc/library/re.rst:435 +msgid "Matches only at the end of the string." +msgstr "" + +#: ../Doc/library/re.rst:437 +msgid "" +"Most of the standard escapes supported by Python string literals are also " +"accepted by the regular expression parser::" +msgstr "" + +#: ../Doc/library/re.rst:444 +msgid "" +"(Note that ``\\b`` is used to represent word boundaries, and means " +"\"backspace\" only inside character classes.)" +msgstr "" + +#: ../Doc/library/re.rst:447 +msgid "" +"``'\\u'`` and ``'\\U'`` escape sequences are only recognized in Unicode " +"patterns. In bytes patterns they are not treated specially." +msgstr "" + +#: ../Doc/library/re.rst:450 +msgid "" +"Octal escapes are included in a limited form. If the first digit is a 0, or " +"if there are three octal digits, it is considered an octal escape. " +"Otherwise, it is a group reference. As for string literals, octal escapes " +"are always at most three digits in length." +msgstr "" + +#: ../Doc/library/re.rst:455 +msgid "The ``'\\u'`` and ``'\\U'`` escape sequences have been added." +msgstr "" + +#: ../Doc/library/re.rst:458 ../Doc/library/re.rst:757 +msgid "" +"Unknown escapes consisting of ``'\\'`` and an ASCII letter now are errors." +msgstr "" + +#: ../Doc/library/re.rst:466 +msgid "Mastering Regular Expressions" +msgstr "" + +#: ../Doc/library/re.rst:465 +msgid "" +"Book on regular expressions by Jeffrey Friedl, published by O'Reilly. The " +"second edition of the book no longer covers Python at all, but the first " +"edition covered writing good regular expression patterns in great detail." +msgstr "" + +#: ../Doc/library/re.rst:476 +msgid "" +"The module defines several functions, constants, and an exception. Some of " +"the functions are simplified versions of the full featured methods for " +"compiled regular expressions. Most non-trivial applications always use the " +"compiled form." +msgstr "" + +#: ../Doc/library/re.rst:484 +msgid "" +"Compile a regular expression pattern into a regular expression object, which " +"can be used for matching using its :func:`~regex.match` and :func:`~regex." +"search` methods, described below." +msgstr "" + +#: ../Doc/library/re.rst:488 +msgid "" +"The expression's behaviour can be modified by specifying a *flags* value. " +"Values can be any of the following variables, combined using bitwise OR (the " +"``|`` operator)." +msgstr "" + +#: ../Doc/library/re.rst:492 +msgid "The sequence ::" +msgstr "" + +#: ../Doc/library/re.rst:497 +msgid "is equivalent to ::" +msgstr "" + +#: ../Doc/library/re.rst:501 +msgid "" +"but using :func:`re.compile` and saving the resulting regular expression " +"object for reuse is more efficient when the expression will be used several " +"times in a single program." +msgstr "" + +#: ../Doc/library/re.rst:507 +msgid "" +"The compiled versions of the most recent patterns passed to :func:`re." +"compile` and the module-level matching functions are cached, so programs " +"that use only a few regular expressions at a time needn't worry about " +"compiling regular expressions." +msgstr "" + +#: ../Doc/library/re.rst:516 +msgid "" +"Make ``\\w``, ``\\W``, ``\\b``, ``\\B``, ``\\d``, ``\\D``, ``\\s`` and ``" +"\\S`` perform ASCII-only matching instead of full Unicode matching. This is " +"only meaningful for Unicode patterns, and is ignored for byte patterns." +msgstr "" + +#: ../Doc/library/re.rst:520 +msgid "" +"Note that for backward compatibility, the :const:`re.U` flag still exists " +"(as well as its synonym :const:`re.UNICODE` and its embedded counterpart ``(?" +"u)``), but these are redundant in Python 3 since matches are Unicode by " +"default for strings (and Unicode matching isn't allowed for bytes)." +msgstr "" + +#: ../Doc/library/re.rst:529 +msgid "Display debug information about compiled expression." +msgstr "" + +#: ../Doc/library/re.rst:535 +msgid "" +"Perform case-insensitive matching; expressions like ``[A-Z]`` will match " +"lowercase letters, too. This is not affected by the current locale and " +"works for Unicode characters as expected." +msgstr "" + +#: ../Doc/library/re.rst:543 +msgid "" +"Make ``\\w``, ``\\W``, ``\\b``, ``\\B``, ``\\s`` and ``\\S`` dependent on " +"the current locale. The use of this flag is discouraged as the locale " +"mechanism is very unreliable, and it only handles one \"culture\" at a time " +"anyway; you should use Unicode matching instead, which is the default in " +"Python 3 for Unicode (str) patterns. This flag can be used only with bytes " +"patterns." +msgstr "" + +#: ../Doc/library/re.rst:549 +msgid "" +":const:`re.LOCALE` can be used only with bytes patterns and is not " +"compatible with :const:`re.ASCII`." +msgstr "" + +#: ../Doc/library/re.rst:557 +msgid "" +"When specified, the pattern character ``'^'`` matches at the beginning of " +"the string and at the beginning of each line (immediately following each " +"newline); and the pattern character ``'$'`` matches at the end of the string " +"and at the end of each line (immediately preceding each newline). By " +"default, ``'^'`` matches only at the beginning of the string, and ``'$'`` " +"only at the end of the string and immediately before the newline (if any) at " +"the end of the string." +msgstr "" + +#: ../Doc/library/re.rst:568 +msgid "" +"Make the ``'.'`` special character match any character at all, including a " +"newline; without this flag, ``'.'`` will match anything *except* a newline." +msgstr "" + +#: ../Doc/library/re.rst:575 +msgid "" +"This flag allows you to write regular expressions that look nicer and are " +"more readable by allowing you to visually separate logical sections of the " +"pattern and add comments. Whitespace within the pattern is ignored, except " +"when in a character class or when preceded by an unescaped backslash. When a " +"line contains a ``#`` that is not in a character class and is not preceded " +"by an unescaped backslash, all characters from the leftmost such ``#`` " +"through the end of the line are ignored." +msgstr "" + +#: ../Doc/library/re.rst:583 +msgid "" +"This means that the two following regular expression objects that match a " +"decimal number are functionally equal::" +msgstr "" + +#: ../Doc/library/re.rst:596 +msgid "" +"Scan through *string* looking for the first location where the regular " +"expression *pattern* produces a match, and return a corresponding :ref:" +"`match object `. Return ``None`` if no position in the " +"string matches the pattern; note that this is different from finding a zero-" +"length match at some point in the string." +msgstr "" + +#: ../Doc/library/re.rst:605 +msgid "" +"If zero or more characters at the beginning of *string* match the regular " +"expression *pattern*, return a corresponding :ref:`match object `. Return ``None`` if the string does not match the pattern; note " +"that this is different from a zero-length match." +msgstr "" + +#: ../Doc/library/re.rst:610 +msgid "" +"Note that even in :const:`MULTILINE` mode, :func:`re.match` will only match " +"at the beginning of the string and not at the beginning of each line." +msgstr "" + +#: ../Doc/library/re.rst:613 +msgid "" +"If you want to locate a match anywhere in *string*, use :func:`search` " +"instead (see also :ref:`search-vs-match`)." +msgstr "" + +#: ../Doc/library/re.rst:619 +msgid "" +"If the whole *string* matches the regular expression *pattern*, return a " +"corresponding :ref:`match object `. Return ``None`` if the " +"string does not match the pattern; note that this is different from a zero-" +"length match." +msgstr "" + +#: ../Doc/library/re.rst:629 +msgid "" +"Split *string* by the occurrences of *pattern*. If capturing parentheses " +"are used in *pattern*, then the text of all groups in the pattern are also " +"returned as part of the resulting list. If *maxsplit* is nonzero, at most " +"*maxsplit* splits occur, and the remainder of the string is returned as the " +"final element of the list. ::" +msgstr "" + +#: ../Doc/library/re.rst:644 +msgid "" +"If there are capturing groups in the separator and it matches at the start " +"of the string, the result will start with an empty string. The same holds " +"for the end of the string:" +msgstr "" + +#: ../Doc/library/re.rst:651 +msgid "" +"That way, separator components are always found at the same relative indices " +"within the result list." +msgstr "" + +#: ../Doc/library/re.rst:656 +msgid "" +":func:`split` doesn't currently split a string on an empty pattern match. " +"For example:" +msgstr "" + +#: ../Doc/library/re.rst:662 +msgid "" +"Even though ``'x*'`` also matches 0 'x' before 'a', between 'b' and 'c', and " +"after 'c', currently these matches are ignored. The correct behavior (i.e. " +"splitting on empty matches too and returning ``['', 'a', 'b', 'c', '']``) " +"will be implemented in future versions of Python, but since this is a " +"backward incompatible change, a :exc:`FutureWarning` will be raised in the " +"meanwhile." +msgstr "" + +#: ../Doc/library/re.rst:669 +msgid "" +"Patterns that can only match empty strings currently never split the " +"string. Since this doesn't match the expected behavior, a :exc:`ValueError` " +"will be raised starting from Python 3.5::" +msgstr "" + +#: ../Doc/library/re.rst:679 ../Doc/library/re.rst:751 +#: ../Doc/library/re.rst:766 +msgid "Added the optional flags argument." +msgstr "" + +#: ../Doc/library/re.rst:682 +msgid "" +"Splitting on a pattern that could match an empty string now raises a " +"warning. Patterns that can only match empty strings are now rejected." +msgstr "" + +#: ../Doc/library/re.rst:688 +msgid "" +"Return all non-overlapping matches of *pattern* in *string*, as a list of " +"strings. The *string* is scanned left-to-right, and matches are returned in " +"the order found. If one or more groups are present in the pattern, return a " +"list of groups; this will be a list of tuples if the pattern has more than " +"one group. Empty matches are included in the result unless they touch the " +"beginning of another match." +msgstr "" + +#: ../Doc/library/re.rst:698 +msgid "" +"Return an :term:`iterator` yielding :ref:`match objects ` " +"over all non-overlapping matches for the RE *pattern* in *string*. The " +"*string* is scanned left-to-right, and matches are returned in the order " +"found. Empty matches are included in the result unless they touch the " +"beginning of another match." +msgstr "" + +#: ../Doc/library/re.rst:707 +msgid "" +"Return the string obtained by replacing the leftmost non-overlapping " +"occurrences of *pattern* in *string* by the replacement *repl*. If the " +"pattern isn't found, *string* is returned unchanged. *repl* can be a string " +"or a function; if it is a string, any backslash escapes in it are " +"processed. That is, ``\\n`` is converted to a single newline character, ``" +"\\r`` is converted to a carriage return, and so forth. Unknown escapes such " +"as ``\\&`` are left alone. Backreferences, such as ``\\6``, are replaced " +"with the substring matched by group 6 in the pattern. For example:" +msgstr "" + +#: ../Doc/library/re.rst:721 +msgid "" +"If *repl* is a function, it is called for every non-overlapping occurrence " +"of *pattern*. The function takes a single match object argument, and " +"returns the replacement string. For example:" +msgstr "" + +#: ../Doc/library/re.rst:733 +msgid "The pattern may be a string or an RE object." +msgstr "" + +#: ../Doc/library/re.rst:735 +msgid "" +"The optional argument *count* is the maximum number of pattern occurrences " +"to be replaced; *count* must be a non-negative integer. If omitted or zero, " +"all occurrences will be replaced. Empty matches for the pattern are replaced " +"only when not adjacent to a previous match, so ``sub('x*', '-', 'abc')`` " +"returns ``'-a-b-c-'``." +msgstr "" + +#: ../Doc/library/re.rst:741 +msgid "" +"In string-type *repl* arguments, in addition to the character escapes and " +"backreferences described above, ``\\g`` will use the substring matched " +"by the group named ``name``, as defined by the ``(?P...)`` syntax. ``" +"\\g`` uses the corresponding group number; ``\\g<2>`` is therefore " +"equivalent to ``\\2``, but isn't ambiguous in a replacement such as ``" +"\\g<2>0``. ``\\20`` would be interpreted as a reference to group 20, not a " +"reference to group 2 followed by the literal character ``'0'``. The " +"backreference ``\\g<0>`` substitutes in the entire substring matched by the " +"RE." +msgstr "" + +#: ../Doc/library/re.rst:754 ../Doc/library/re.rst:769 +#: ../Doc/library/re.rst:970 +msgid "Unmatched groups are replaced with an empty string." +msgstr "" + +#: ../Doc/library/re.rst:763 +msgid "" +"Perform the same operation as :func:`sub`, but return a tuple ``(new_string, " +"number_of_subs_made)``." +msgstr "" + +#: ../Doc/library/re.rst:775 +msgid "" +"Escape all the characters in pattern except ASCII letters, numbers and " +"``'_'``. This is useful if you want to match an arbitrary literal string " +"that may have regular expression metacharacters in it." +msgstr "" + +#: ../Doc/library/re.rst:779 +msgid "The ``'_'`` character is no longer escaped." +msgstr "" + +#: ../Doc/library/re.rst:785 +msgid "Clear the regular expression cache." +msgstr "" + +#: ../Doc/library/re.rst:790 +msgid "" +"Exception raised when a string passed to one of the functions here is not a " +"valid regular expression (for example, it might contain unmatched " +"parentheses) or when some other error occurs during compilation or " +"matching. It is never an error if a string contains no match for a " +"pattern. The error instance has the following additional attributes:" +msgstr "" + +#: ../Doc/library/re.rst:802 +msgid "The regular expression pattern." +msgstr "" + +#: ../Doc/library/re.rst:806 +msgid "The index of *pattern* where compilation failed." +msgstr "" + +#: ../Doc/library/re.rst:816 +msgid "Added additional attributes." +msgstr "" + +#: ../Doc/library/re.rst:822 +msgid "Regular Expression Objects" +msgstr "" + +#: ../Doc/library/re.rst:824 +msgid "" +"Compiled regular expression objects support the following methods and " +"attributes:" +msgstr "" + +#: ../Doc/library/re.rst:829 +msgid "" +"Scan through *string* looking for the first location where this regular " +"expression produces a match, and return a corresponding :ref:`match object " +"`. Return ``None`` if no position in the string matches the " +"pattern; note that this is different from finding a zero-length match at " +"some point in the string." +msgstr "" + +#: ../Doc/library/re.rst:835 +msgid "" +"The optional second parameter *pos* gives an index in the string where the " +"search is to start; it defaults to ``0``. This is not completely equivalent " +"to slicing the string; the ``'^'`` pattern character matches at the real " +"beginning of the string and at positions just after a newline, but not " +"necessarily at the index where the search is to start." +msgstr "" + +#: ../Doc/library/re.rst:841 +msgid "" +"The optional parameter *endpos* limits how far the string will be searched; " +"it will be as if the string is *endpos* characters long, so only the " +"characters from *pos* to ``endpos - 1`` will be searched for a match. If " +"*endpos* is less than *pos*, no match will be found; otherwise, if *rx* is a " +"compiled regular expression object, ``rx.search(string, 0, 50)`` is " +"equivalent to ``rx.search(string[:50], 0)``." +msgstr "" + +#: ../Doc/library/re.rst:856 +msgid "" +"If zero or more characters at the *beginning* of *string* match this regular " +"expression, return a corresponding :ref:`match object `. " +"Return ``None`` if the string does not match the pattern; note that this is " +"different from a zero-length match." +msgstr "" + +#: ../Doc/library/re.rst:861 ../Doc/library/re.rst:879 +msgid "" +"The optional *pos* and *endpos* parameters have the same meaning as for the :" +"meth:`~regex.search` method." +msgstr "" + +#: ../Doc/library/re.rst:869 +msgid "" +"If you want to locate a match anywhere in *string*, use :meth:`~regex." +"search` instead (see also :ref:`search-vs-match`)." +msgstr "" + +#: ../Doc/library/re.rst:875 +msgid "" +"If the whole *string* matches this regular expression, return a " +"corresponding :ref:`match object `. Return ``None`` if the " +"string does not match the pattern; note that this is different from a zero-" +"length match." +msgstr "" + +#: ../Doc/library/re.rst:893 +msgid "Identical to the :func:`split` function, using the compiled pattern." +msgstr "" + +#: ../Doc/library/re.rst:898 +msgid "" +"Similar to the :func:`findall` function, using the compiled pattern, but " +"also accepts optional *pos* and *endpos* parameters that limit the search " +"region like for :meth:`match`." +msgstr "" + +#: ../Doc/library/re.rst:905 +msgid "" +"Similar to the :func:`finditer` function, using the compiled pattern, but " +"also accepts optional *pos* and *endpos* parameters that limit the search " +"region like for :meth:`match`." +msgstr "" + +#: ../Doc/library/re.rst:912 +msgid "Identical to the :func:`sub` function, using the compiled pattern." +msgstr "" + +#: ../Doc/library/re.rst:917 +msgid "Identical to the :func:`subn` function, using the compiled pattern." +msgstr "" + +#: ../Doc/library/re.rst:922 +msgid "" +"The regex matching flags. This is a combination of the flags given to :func:" +"`.compile`, any ``(?...)`` inline flags in the pattern, and implicit flags " +"such as :data:`UNICODE` if the pattern is a Unicode string." +msgstr "" + +#: ../Doc/library/re.rst:929 +msgid "The number of capturing groups in the pattern." +msgstr "" + +#: ../Doc/library/re.rst:934 +msgid "" +"A dictionary mapping any symbolic group names defined by ``(?P)`` to " +"group numbers. The dictionary is empty if no symbolic groups were used in " +"the pattern." +msgstr "" + +#: ../Doc/library/re.rst:941 +msgid "The pattern string from which the RE object was compiled." +msgstr "" + +#: ../Doc/library/re.rst:947 +msgid "Match Objects" +msgstr "" + +#: ../Doc/library/re.rst:949 +msgid "" +"Match objects always have a boolean value of ``True``. Since :meth:`~regex." +"match` and :meth:`~regex.search` return ``None`` when there is no match, you " +"can test whether there was a match with a simple ``if`` statement::" +msgstr "" + +#: ../Doc/library/re.rst:958 +msgid "Match objects support the following methods and attributes:" +msgstr "" + +#: ../Doc/library/re.rst:963 +msgid "" +"Return the string obtained by doing backslash substitution on the template " +"string *template*, as done by the :meth:`~regex.sub` method. Escapes such as " +"``\\n`` are converted to the appropriate characters, and numeric " +"backreferences (``\\1``, ``\\2``) and named backreferences (``\\g<1>``, ``" +"\\g``) are replaced by the contents of the corresponding group." +msgstr "" + +#: ../Doc/library/re.rst:975 +msgid "" +"Returns one or more subgroups of the match. If there is a single argument, " +"the result is a single string; if there are multiple arguments, the result " +"is a tuple with one item per argument. Without arguments, *group1* defaults " +"to zero (the whole match is returned). If a *groupN* argument is zero, the " +"corresponding return value is the entire matching string; if it is in the " +"inclusive range [1..99], it is the string matching the corresponding " +"parenthesized group. If a group number is negative or larger than the " +"number of groups defined in the pattern, an :exc:`IndexError` exception is " +"raised. If a group is contained in a part of the pattern that did not match, " +"the corresponding result is ``None``. If a group is contained in a part of " +"the pattern that matched multiple times, the last match is returned." +msgstr "" + +#: ../Doc/library/re.rst:997 +msgid "" +"If the regular expression uses the ``(?P...)`` syntax, the *groupN* " +"arguments may also be strings identifying groups by their group name. If a " +"string argument is not used as a group name in the pattern, an :exc:" +"`IndexError` exception is raised." +msgstr "" + +#: ../Doc/library/re.rst:1002 +msgid "A moderately complicated example:" +msgstr "" + +#: ../Doc/library/re.rst:1010 +msgid "Named groups can also be referred to by their index:" +msgstr "" + +#: ../Doc/library/re.rst:1017 +msgid "If a group matches multiple times, only the last match is accessible:" +msgstr "" + +#: ../Doc/library/re.rst:1026 +msgid "" +"This is identical to ``m.group(g)``. This allows easier access to an " +"individual group from a match:" +msgstr "" + +#: ../Doc/library/re.rst:1042 +msgid "" +"Return a tuple containing all the subgroups of the match, from 1 up to " +"however many groups are in the pattern. The *default* argument is used for " +"groups that did not participate in the match; it defaults to ``None``." +msgstr "" + +#: ../Doc/library/re.rst:1052 +msgid "" +"If we make the decimal place and everything after it optional, not all " +"groups might participate in the match. These groups will default to " +"``None`` unless the *default* argument is given:" +msgstr "" + +#: ../Doc/library/re.rst:1065 +msgid "" +"Return a dictionary containing all the *named* subgroups of the match, keyed " +"by the subgroup name. The *default* argument is used for groups that did " +"not participate in the match; it defaults to ``None``. For example:" +msgstr "" + +#: ../Doc/library/re.rst:1077 +msgid "" +"Return the indices of the start and end of the substring matched by *group*; " +"*group* defaults to zero (meaning the whole matched substring). Return " +"``-1`` if *group* exists but did not contribute to the match. For a match " +"object *m*, and a group *g* that did contribute to the match, the substring " +"matched by group *g* (equivalent to ``m.group(g)``) is ::" +msgstr "" + +#: ../Doc/library/re.rst:1085 +msgid "" +"Note that ``m.start(group)`` will equal ``m.end(group)`` if *group* matched " +"a null string. For example, after ``m = re.search('b(c?)', 'cba')``, ``m." +"start(0)`` is 1, ``m.end(0)`` is 2, ``m.start(1)`` and ``m.end(1)`` are both " +"2, and ``m.start(2)`` raises an :exc:`IndexError` exception." +msgstr "" + +#: ../Doc/library/re.rst:1090 +msgid "An example that will remove *remove_this* from email addresses:" +msgstr "" + +#: ../Doc/library/re.rst:1100 +msgid "" +"For a match *m*, return the 2-tuple ``(m.start(group), m.end(group))``. Note " +"that if *group* did not contribute to the match, this is ``(-1, -1)``. " +"*group* defaults to zero, the entire match." +msgstr "" + +#: ../Doc/library/re.rst:1107 +msgid "" +"The value of *pos* which was passed to the :meth:`~regex.search` or :meth:" +"`~regex.match` method of a :ref:`regex object `. This is the " +"index into the string at which the RE engine started looking for a match." +msgstr "" + +#: ../Doc/library/re.rst:1114 +msgid "" +"The value of *endpos* which was passed to the :meth:`~regex.search` or :meth:" +"`~regex.match` method of a :ref:`regex object `. This is the " +"index into the string beyond which the RE engine will not go." +msgstr "" + +#: ../Doc/library/re.rst:1121 +msgid "" +"The integer index of the last matched capturing group, or ``None`` if no " +"group was matched at all. For example, the expressions ``(a)b``, ``((a)" +"(b))``, and ``((ab))`` will have ``lastindex == 1`` if applied to the string " +"``'ab'``, while the expression ``(a)(b)`` will have ``lastindex == 2``, if " +"applied to the same string." +msgstr "" + +#: ../Doc/library/re.rst:1130 +msgid "" +"The name of the last matched capturing group, or ``None`` if the group " +"didn't have a name, or if no group was matched at all." +msgstr "" + +#: ../Doc/library/re.rst:1136 +msgid "" +"The regular expression object whose :meth:`~regex.match` or :meth:`~regex." +"search` method produced this match instance." +msgstr "" + +#: ../Doc/library/re.rst:1142 +msgid "The string passed to :meth:`~regex.match` or :meth:`~regex.search`." +msgstr "" + +#: ../Doc/library/re.rst:1148 +msgid "Regular Expression Examples" +msgstr "" + +#: ../Doc/library/re.rst:1152 +msgid "Checking for a Pair" +msgstr "" + +#: ../Doc/library/re.rst:1154 +msgid "" +"In this example, we'll use the following helper function to display match " +"objects a little more gracefully:" +msgstr "" + +#: ../Doc/library/re.rst:1164 +msgid "" +"Suppose you are writing a poker program where a player's hand is represented " +"as a 5-character string with each character representing a card, \"a\" for " +"ace, \"k\" for king, \"q\" for queen, \"j\" for jack, \"t\" for 10, and " +"\"2\" through \"9\" representing the card with that value." +msgstr "" + +#: ../Doc/library/re.rst:1169 +msgid "To see if a given string is a valid hand, one could do the following:" +msgstr "" + +#: ../Doc/library/re.rst:1179 +msgid "" +"That last hand, ``\"727ak\"``, contained a pair, or two of the same valued " +"cards. To match this with a regular expression, one could use backreferences " +"as such:" +msgstr "" + +#: ../Doc/library/re.rst:1189 +msgid "" +"To find out what card the pair consists of, one could use the :meth:`~match." +"group` method of the match object in the following manner:" +msgstr "" + +#: ../Doc/library/re.rst:1209 +msgid "Simulating scanf()" +msgstr "" + +#: ../Doc/library/re.rst:1213 +msgid "" +"Python does not currently have an equivalent to :c:func:`scanf`. Regular " +"expressions are generally more powerful, though also more verbose, than :c:" +"func:`scanf` format strings. The table below offers some more-or-less " +"equivalent mappings between :c:func:`scanf` format tokens and regular " +"expressions." +msgstr "" + +#: ../Doc/library/re.rst:1220 +msgid ":c:func:`scanf` Token" +msgstr "" + +#: ../Doc/library/re.rst:1220 +msgid "Regular Expression" +msgstr "" + +#: ../Doc/library/re.rst:1222 ../Doc/library/xml.etree.elementtree.rst:419 +msgid "``.``" +msgstr "" + +#: ../Doc/library/re.rst:1224 +msgid "``%5c``" +msgstr "" + +#: ../Doc/library/re.rst:1224 +msgid "``.{5}``" +msgstr "" + +#: ../Doc/library/re.rst:1226 +msgid "``[-+]?\\d+``" +msgstr "" + +#: ../Doc/library/re.rst:1228 +msgid "``%e``, ``%E``, ``%f``, ``%g``" +msgstr "" + +#: ../Doc/library/re.rst:1228 +msgid "``[-+]?(\\d+(\\.\\d*)?|\\.\\d+)([eE][-+]?\\d+)?``" +msgstr "" + +#: ../Doc/library/re.rst:1230 +msgid "``%i``" +msgstr "" + +#: ../Doc/library/re.rst:1230 +msgid "``[-+]?(0[xX][\\dA-Fa-f]+|0[0-7]*|\\d+)``" +msgstr "" + +#: ../Doc/library/re.rst:1232 +msgid "``%o``" +msgstr "" + +#: ../Doc/library/re.rst:1232 +msgid "``[-+]?[0-7]+``" +msgstr "" + +#: ../Doc/library/re.rst:1234 +msgid "``%s``" +msgstr "" + +#: ../Doc/library/re.rst:1234 +msgid "``\\S+``" +msgstr "" + +#: ../Doc/library/re.rst:1236 +msgid "``\\d+``" +msgstr "" + +#: ../Doc/library/re.rst:1238 +msgid "``%x``, ``%X``" +msgstr "" + +#: ../Doc/library/re.rst:1238 +msgid "``[-+]?(0[xX])?[\\dA-Fa-f]+``" +msgstr "" + +#: ../Doc/library/re.rst:1241 +msgid "To extract the filename and numbers from a string like ::" +msgstr "" + +#: ../Doc/library/re.rst:1245 +msgid "you would use a :c:func:`scanf` format like ::" +msgstr "" + +#: ../Doc/library/re.rst:1249 +msgid "The equivalent regular expression would be ::" +msgstr "" + +#: ../Doc/library/re.rst:1257 +msgid "search() vs. match()" +msgstr "" + +#: ../Doc/library/re.rst:1261 +msgid "" +"Python offers two different primitive operations based on regular " +"expressions: :func:`re.match` checks for a match only at the beginning of " +"the string, while :func:`re.search` checks for a match anywhere in the " +"string (this is what Perl does by default)." +msgstr "" + +#: ../Doc/library/re.rst:1272 +msgid "" +"Regular expressions beginning with ``'^'`` can be used with :func:`search` " +"to restrict the match at the beginning of the string::" +msgstr "" + +#: ../Doc/library/re.rst:1280 +msgid "" +"Note however that in :const:`MULTILINE` mode :func:`match` only matches at " +"the beginning of the string, whereas using :func:`search` with a regular " +"expression beginning with ``'^'`` will match at the beginning of each line." +msgstr "" + +#: ../Doc/library/re.rst:1290 +msgid "Making a Phonebook" +msgstr "" + +#: ../Doc/library/re.rst:1292 +msgid "" +":func:`split` splits a string into a list delimited by the passed pattern. " +"The method is invaluable for converting textual data into data structures " +"that can be easily read and modified by Python as demonstrated in the " +"following example that creates a phonebook." +msgstr "" + +#: ../Doc/library/re.rst:1297 +msgid "" +"First, here is the input. Normally it may come from a file, here we are " +"using triple-quoted string syntax:" +msgstr "" + +#: ../Doc/library/re.rst:1308 +msgid "" +"The entries are separated by one or more newlines. Now we convert the string " +"into a list with each nonempty line having its own entry:" +msgstr "" + +#: ../Doc/library/re.rst:1321 +msgid "" +"Finally, split each entry into a list with first name, last name, telephone " +"number, and address. We use the ``maxsplit`` parameter of :func:`split` " +"because the address has spaces, our splitting pattern, in it:" +msgstr "" + +#: ../Doc/library/re.rst:1334 +msgid "" +"The ``:?`` pattern matches the colon after the last name, so that it does " +"not occur in the result list. With a ``maxsplit`` of ``4``, we could " +"separate the house number from the street name:" +msgstr "" + +#: ../Doc/library/re.rst:1349 +msgid "Text Munging" +msgstr "" + +#: ../Doc/library/re.rst:1351 +msgid "" +":func:`sub` replaces every occurrence of a pattern with a string or the " +"result of a function. This example demonstrates using :func:`sub` with a " +"function to \"munge\" text, or randomize the order of all the characters in " +"each word of a sentence except for the first and last characters::" +msgstr "" + +#: ../Doc/library/re.rst:1368 +msgid "Finding all Adverbs" +msgstr "" + +#: ../Doc/library/re.rst:1370 +msgid "" +":func:`findall` matches *all* occurrences of a pattern, not just the first " +"one as :func:`search` does. For example, if one was a writer and wanted to " +"find all of the adverbs in some text, he or she might use :func:`findall` in " +"the following manner:" +msgstr "" + +#: ../Doc/library/re.rst:1381 +msgid "Finding all Adverbs and their Positions" +msgstr "" + +#: ../Doc/library/re.rst:1383 +msgid "" +"If one wants more information about all matches of a pattern than the " +"matched text, :func:`finditer` is useful as it provides :ref:`match objects " +"` instead of strings. Continuing with the previous example, " +"if one was a writer who wanted to find all of the adverbs *and their " +"positions* in some text, he or she would use :func:`finditer` in the " +"following manner:" +msgstr "" + +#: ../Doc/library/re.rst:1397 +msgid "Raw String Notation" +msgstr "" + +#: ../Doc/library/re.rst:1399 +msgid "" +"Raw string notation (``r\"text\"``) keeps regular expressions sane. Without " +"it, every backslash (``'\\'``) in a regular expression would have to be " +"prefixed with another one to escape it. For example, the two following " +"lines of code are functionally identical:" +msgstr "" + +#: ../Doc/library/re.rst:1409 +msgid "" +"When one wants to match a literal backslash, it must be escaped in the " +"regular expression. With raw string notation, this means ``r\"\\\\\"``. " +"Without raw string notation, one must use ``\"\\\\\\\\\"``, making the " +"following lines of code functionally identical:" +msgstr "" + +#: ../Doc/library/re.rst:1421 +msgid "Writing a Tokenizer" +msgstr "" + +#: ../Doc/library/re.rst:1423 +msgid "" +"A `tokenizer or scanner `_ " +"analyzes a string to categorize groups of characters. This is a useful " +"first step in writing a compiler or interpreter." +msgstr "" + +#: ../Doc/library/re.rst:1427 +msgid "" +"The text categories are specified with regular expressions. The technique " +"is to combine those into a single master regular expression and to loop over " +"successive matches::" +msgstr "" + +#: ../Doc/library/re.rst:1477 +msgid "The tokenizer produces the following output::" +msgstr "" + +#: ../Doc/library/readline.rst:2 +msgid ":mod:`readline` --- GNU readline interface" +msgstr "" + +#: ../Doc/library/readline.rst:12 +msgid "" +"The :mod:`readline` module defines a number of functions to facilitate " +"completion and reading/writing of history files from the Python interpreter. " +"This module can be used directly, or via the :mod:`rlcompleter` module, " +"which supports completion of Python identifiers at the interactive prompt. " +"Settings made using this module affect the behaviour of both the " +"interpreter's interactive prompt and the prompts offered by the built-in :" +"func:`input` function." +msgstr "" + +#: ../Doc/library/readline.rst:22 +msgid "" +"The underlying Readline library API may be implemented by the ``libedit`` " +"library instead of GNU readline. On MacOS X the :mod:`readline` module " +"detects which library is being used at run time." +msgstr "" + +#: ../Doc/library/readline.rst:27 +msgid "" +"The configuration file for ``libedit`` is different from that of GNU " +"readline. If you programmatically load configuration strings you can check " +"for the text \"libedit\" in :const:`readline.__doc__` to differentiate " +"between GNU readline and libedit." +msgstr "" + +#: ../Doc/library/readline.rst:32 +msgid "" +"Readline keybindings may be configured via an initialization file, typically " +"``.inputrc`` in your home directory. See `Readline Init File `_ in the GNU " +"Readline manual for information about the format and allowable constructs of " +"that file, and the capabilities of the Readline library in general." +msgstr "" + +#: ../Doc/library/readline.rst:41 +msgid "Init file" +msgstr "" + +#: ../Doc/library/readline.rst:43 +msgid "The following functions relate to the init file and user configuration:" +msgstr "" + +#: ../Doc/library/readline.rst:48 +msgid "" +"Execute the init line provided in the *string* argument. This calls :c:func:" +"`rl_parse_and_bind` in the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:54 +msgid "" +"Execute a readline initialization file. The default filename is the last " +"filename used. This calls :c:func:`rl_read_init_file` in the underlying " +"library." +msgstr "" + +#: ../Doc/library/readline.rst:59 +msgid "Line buffer" +msgstr "" + +#: ../Doc/library/readline.rst:61 +msgid "The following functions operate on the line buffer:" +msgstr "" + +#: ../Doc/library/readline.rst:66 +msgid "" +"Return the current contents of the line buffer (:c:data:`rl_line_buffer` in " +"the underlying library)." +msgstr "" + +#: ../Doc/library/readline.rst:72 +msgid "" +"Insert text into the line buffer at the cursor position. This calls :c:func:" +"`rl_insert_text` in the underlying library, but ignores the return value." +msgstr "" + +#: ../Doc/library/readline.rst:79 +msgid "" +"Change what's displayed on the screen to reflect the current contents of the " +"line buffer. This calls :c:func:`rl_redisplay` in the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:84 +msgid "History file" +msgstr "" + +#: ../Doc/library/readline.rst:86 +msgid "The following functions operate on a history file:" +msgstr "" + +#: ../Doc/library/readline.rst:91 +msgid "" +"Load a readline history file, and append it to the history list. The default " +"filename is :file:`~/.history`. This calls :c:func:`read_history` in the " +"underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:98 +msgid "" +"Save the history list to a readline history file, overwriting any existing " +"file. The default filename is :file:`~/.history`. This calls :c:func:" +"`write_history` in the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:105 +msgid "" +"Append the last *nelements* items of history to a file. The default " +"filename is :file:`~/.history`. The file must already exist. This calls :c:" +"func:`append_history` in the underlying library. This function only exists " +"if Python was compiled for a version of the library that supports it." +msgstr "" + +#: ../Doc/library/readline.rst:117 +msgid "" +"Set or return the desired number of lines to save in the history file. The :" +"func:`write_history_file` function uses this value to truncate the history " +"file, by calling :c:func:`history_truncate_file` in the underlying library. " +"Negative values imply unlimited history file size." +msgstr "" + +#: ../Doc/library/readline.rst:125 +msgid "History list" +msgstr "" + +#: ../Doc/library/readline.rst:127 +msgid "The following functions operate on a global history list:" +msgstr "" + +#: ../Doc/library/readline.rst:132 +msgid "" +"Clear the current history. This calls :c:func:`clear_history` in the " +"underlying library. The Python function only exists if Python was compiled " +"for a version of the library that supports it." +msgstr "" + +#: ../Doc/library/readline.rst:139 +msgid "" +"Return the number of items currently in the history. (This is different " +"from :func:`get_history_length`, which returns the maximum number of lines " +"that will be written to a history file.)" +msgstr "" + +#: ../Doc/library/readline.rst:146 +msgid "" +"Return the current contents of history item at *index*. The item index is " +"one-based. This calls :c:func:`history_get` in the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:152 +msgid "" +"Remove history item specified by its position from the history. The position " +"is zero-based. This calls :c:func:`remove_history` in the underlying " +"library." +msgstr "" + +#: ../Doc/library/readline.rst:159 +msgid "" +"Replace history item specified by its position with *line*. The position is " +"zero-based. This calls :c:func:`replace_history_entry` in the underlying " +"library." +msgstr "" + +#: ../Doc/library/readline.rst:166 +msgid "" +"Append *line* to the history buffer, as if it was the last line typed. This " +"calls :c:func:`add_history` in the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:172 +msgid "" +"Enable or disable automatic calls to :c:func:`add_history` when reading " +"input via readline. The *enabled* argument should be a Boolean value that " +"when true, enables auto history, and that when False, disables auto history." +msgstr "" + +#: ../Doc/library/readline.rst:185 +msgid "Startup hooks" +msgstr "" + +#: ../Doc/library/readline.rst:190 +msgid "" +"Set or remove the function invoked by the :c:data:`rl_startup_hook` callback " +"of the underlying library. If *function* is specified, it will be used as " +"the new hook function; if omitted or ``None``, any function already " +"installed is removed. The hook is called with no arguments just before " +"readline prints the first prompt." +msgstr "" + +#: ../Doc/library/readline.rst:199 +msgid "" +"Set or remove the function invoked by the :c:data:`rl_pre_input_hook` " +"callback of the underlying library. If *function* is specified, it will be " +"used as the new hook function; if omitted or ``None``, any function already " +"installed is removed. The hook is called with no arguments after the first " +"prompt has been printed and just before readline starts reading input " +"characters. This function only exists if Python was compiled for a version " +"of the library that supports it." +msgstr "" + +#: ../Doc/library/readline.rst:209 +msgid "Completion" +msgstr "" + +#: ../Doc/library/readline.rst:211 +msgid "" +"The following functions relate to implementing a custom word completion " +"function. This is typically operated by the Tab key, and can suggest and " +"automatically complete a word being typed. By default, Readline is set up " +"to be used by :mod:`rlcompleter` to complete Python identifiers for the " +"interactive interpreter. If the :mod:`readline` module is to be used with a " +"custom completer, a different set of word delimiters should be set." +msgstr "" + +#: ../Doc/library/readline.rst:221 +msgid "" +"Set or remove the completer function. If *function* is specified, it will " +"be used as the new completer function; if omitted or ``None``, any completer " +"function already installed is removed. The completer function is called as " +"``function(text, state)``, for *state* in ``0``, ``1``, ``2``, ..., until it " +"returns a non-string value. It should return the next possible completion " +"starting with *text*." +msgstr "" + +#: ../Doc/library/readline.rst:228 +msgid "" +"The installed completer function is invoked by the *entry_func* callback " +"passed to :c:func:`rl_completion_matches` in the underlying library. The " +"*text* string comes from the first parameter to the :c:data:" +"`rl_attempted_completion_function` callback of the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:237 +msgid "" +"Get the completer function, or ``None`` if no completer function has been " +"set." +msgstr "" + +#: ../Doc/library/readline.rst:242 +msgid "" +"Get the type of completion being attempted. This returns the :c:data:" +"`rl_completion_type` variable in the underlying library as an integer." +msgstr "" + +#: ../Doc/library/readline.rst:250 +msgid "" +"Get the beginning or ending index of the completion scope. These indexes are " +"the *start* and *end* arguments passed to the :c:data:" +"`rl_attempted_completion_function` callback of the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:259 +msgid "" +"Set or get the word delimiters for completion. These determine the start of " +"the word to be considered for completion (the completion scope). These " +"functions access the :c:data:`rl_completer_word_break_characters` variable " +"in the underlying library." +msgstr "" + +#: ../Doc/library/readline.rst:267 +msgid "" +"Set or remove the completion display function. If *function* is specified, " +"it will be used as the new completion display function; if omitted or " +"``None``, any completion display function already installed is removed. " +"This sets or clears the :c:data:`rl_completion_display_matches_hook` " +"callback in the underlying library. The completion display function is " +"called as ``function(substitution, [matches], longest_match_length)`` once " +"each time matches need to be displayed." +msgstr "" + +#: ../Doc/library/readline.rst:282 +msgid "" +"The following example demonstrates how to use the :mod:`readline` module's " +"history reading and writing functions to automatically load and save a " +"history file named :file:`.python_history` from the user's home directory. " +"The code below would normally be executed automatically during interactive " +"sessions from the user's :envvar:`PYTHONSTARTUP` file. ::" +msgstr "" + +#: ../Doc/library/readline.rst:302 +msgid "" +"This code is actually automatically run when Python is run in :ref:" +"`interactive mode ` (see :ref:`rlcompleter-config`)." +msgstr "" + +#: ../Doc/library/readline.rst:305 +msgid "" +"The following example achieves the same goal but supports concurrent " +"interactive sessions, by only appending the new history. ::" +msgstr "" + +#: ../Doc/library/readline.rst:326 +msgid "" +"The following example extends the :class:`code.InteractiveConsole` class to " +"support history save/restore. ::" +msgstr "" + +#: ../Doc/library/reprlib.rst:2 +msgid ":mod:`reprlib` --- Alternate :func:`repr` implementation" +msgstr "" + +#: ../Doc/library/reprlib.rst:9 +msgid "**Source code:** :source:`Lib/reprlib.py`" +msgstr "" + +#: ../Doc/library/reprlib.rst:13 +msgid "" +"The :mod:`reprlib` module provides a means for producing object " +"representations with limits on the size of the resulting strings. This is " +"used in the Python debugger and may be useful in other contexts as well." +msgstr "" + +#: ../Doc/library/reprlib.rst:17 +msgid "This module provides a class, an instance, and a function:" +msgstr "" + +#: ../Doc/library/reprlib.rst:22 +msgid "" +"Class which provides formatting services useful in implementing functions " +"similar to the built-in :func:`repr`; size limits for different object " +"types are added to avoid the generation of representations which are " +"excessively long." +msgstr "" + +#: ../Doc/library/reprlib.rst:29 +msgid "" +"This is an instance of :class:`Repr` which is used to provide the :func:`." +"repr` function described below. Changing the attributes of this object will " +"affect the size limits used by :func:`.repr` and the Python debugger." +msgstr "" + +#: ../Doc/library/reprlib.rst:37 +msgid "" +"This is the :meth:`~Repr.repr` method of ``aRepr``. It returns a string " +"similar to that returned by the built-in function of the same name, but with " +"limits on most sizes." +msgstr "" + +#: ../Doc/library/reprlib.rst:41 +msgid "" +"In addition to size-limiting tools, the module also provides a decorator for " +"detecting recursive calls to :meth:`__repr__` and substituting a placeholder " +"string instead." +msgstr "" + +#: ../Doc/library/reprlib.rst:47 +msgid "" +"Decorator for :meth:`__repr__` methods to detect recursive calls within the " +"same thread. If a recursive call is made, the *fillvalue* is returned, " +"otherwise, the usual :meth:`__repr__` call is made. For example:" +msgstr "" + +#: ../Doc/library/reprlib.rst:68 +msgid "Repr Objects" +msgstr "" + +#: ../Doc/library/reprlib.rst:70 +msgid "" +":class:`Repr` instances provide several attributes which can be used to " +"provide size limits for the representations of different object types, and " +"methods which format specific object types." +msgstr "" + +#: ../Doc/library/reprlib.rst:77 +msgid "" +"Depth limit on the creation of recursive representations. The default is " +"``6``." +msgstr "" + +#: ../Doc/library/reprlib.rst:88 +msgid "" +"Limits on the number of entries represented for the named object type. The " +"default is ``4`` for :attr:`maxdict`, ``5`` for :attr:`maxarray`, and ``6`` " +"for the others." +msgstr "" + +#: ../Doc/library/reprlib.rst:95 +msgid "" +"Maximum number of characters in the representation for an integer. Digits " +"are dropped from the middle. The default is ``40``." +msgstr "" + +#: ../Doc/library/reprlib.rst:101 +msgid "" +"Limit on the number of characters in the representation of the string. Note " +"that the \"normal\" representation of the string is used as the character " +"source: if escape sequences are needed in the representation, these may be " +"mangled when the representation is shortened. The default is ``30``." +msgstr "" + +#: ../Doc/library/reprlib.rst:109 +msgid "" +"This limit is used to control the size of object types for which no specific " +"formatting method is available on the :class:`Repr` object. It is applied in " +"a similar manner as :attr:`maxstring`. The default is ``20``." +msgstr "" + +#: ../Doc/library/reprlib.rst:116 +msgid "" +"The equivalent to the built-in :func:`repr` that uses the formatting imposed " +"by the instance." +msgstr "" + +#: ../Doc/library/reprlib.rst:122 +msgid "" +"Recursive implementation used by :meth:`.repr`. This uses the type of *obj* " +"to determine which formatting method to call, passing it *obj* and *level*. " +"The type-specific methods should call :meth:`repr1` to perform recursive " +"formatting, with ``level - 1`` for the value of *level* in the recursive " +"call." +msgstr "" + +#: ../Doc/library/reprlib.rst:131 +msgid "" +"Formatting methods for specific types are implemented as methods with a name " +"based on the type name. In the method name, **TYPE** is replaced by ``'_'." +"join(type(obj).__name__.split())``. Dispatch to these methods is handled by :" +"meth:`repr1`. Type-specific methods which need to recursively format a value " +"should call ``self.repr1(subobj, level - 1)``." +msgstr "" + +#: ../Doc/library/reprlib.rst:141 +msgid "Subclassing Repr Objects" +msgstr "" + +#: ../Doc/library/reprlib.rst:143 +msgid "" +"The use of dynamic dispatching by :meth:`Repr.repr1` allows subclasses of :" +"class:`Repr` to add support for additional built-in object types or to " +"modify the handling of types already supported. This example shows how " +"special support for file objects could be added::" +msgstr "" + +#: ../Doc/library/resource.rst:2 +msgid ":mod:`resource` --- Resource usage information" +msgstr "" + +#: ../Doc/library/resource.rst:13 +msgid "" +"This module provides basic mechanisms for measuring and controlling system " +"resources utilized by a program." +msgstr "" + +#: ../Doc/library/resource.rst:16 +msgid "" +"Symbolic constants are used to specify particular system resources and to " +"request usage information about either the current process or its children." +msgstr "" + +#: ../Doc/library/resource.rst:19 +msgid "An :exc:`OSError` is raised on syscall failure." +msgstr "" + +#: ../Doc/library/resource.rst:24 ../Doc/library/select.rst:31 +#: ../Doc/library/socket.rst:191 +msgid "A deprecated alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/resource.rst:26 ../Doc/library/select.rst:33 +#: ../Doc/library/socket.rst:193 +msgid "Following :pep:`3151`, this class was made an alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/resource.rst:31 +msgid "Resource Limits" +msgstr "" + +#: ../Doc/library/resource.rst:33 +msgid "" +"Resources usage can be limited using the :func:`setrlimit` function " +"described below. Each resource is controlled by a pair of limits: a soft " +"limit and a hard limit. The soft limit is the current limit, and may be " +"lowered or raised by a process over time. The soft limit can never exceed " +"the hard limit. The hard limit can be lowered to any value greater than the " +"soft limit, but not raised. (Only processes with the effective UID of the " +"super-user can raise a hard limit.)" +msgstr "" + +#: ../Doc/library/resource.rst:41 +msgid "" +"The specific resources that can be limited are system dependent. They are " +"described in the :manpage:`getrlimit(2)` man page. The resources listed " +"below are supported when the underlying operating system supports them; " +"resources which cannot be checked or controlled by the operating system are " +"not defined in this module for those platforms." +msgstr "" + +#: ../Doc/library/resource.rst:50 +msgid "Constant used to represent the limit for an unlimited resource." +msgstr "" + +#: ../Doc/library/resource.rst:55 +msgid "" +"Returns a tuple ``(soft, hard)`` with the current soft and hard limits of " +"*resource*. Raises :exc:`ValueError` if an invalid resource is specified, " +"or :exc:`error` if the underlying system call fails unexpectedly." +msgstr "" + +#: ../Doc/library/resource.rst:62 +msgid "" +"Sets new limits of consumption of *resource*. The *limits* argument must be " +"a tuple ``(soft, hard)`` of two integers describing the new limits. A value " +"of :data:`~resource.RLIM_INFINITY` can be used to request a limit that is " +"unlimited." +msgstr "" + +#: ../Doc/library/resource.rst:67 +msgid "" +"Raises :exc:`ValueError` if an invalid resource is specified, if the new " +"soft limit exceeds the hard limit, or if a process tries to raise its hard " +"limit. Specifying a limit of :data:`~resource.RLIM_INFINITY` when the hard " +"or system limit for that resource is not unlimited will result in a :exc:" +"`ValueError`. A process with the effective UID of super-user can request " +"any valid limit value, including unlimited, but :exc:`ValueError` will still " +"be raised if the requested limit exceeds the system imposed limit." +msgstr "" + +#: ../Doc/library/resource.rst:76 +msgid "" +"``setrlimit`` may also raise :exc:`error` if the underlying system call " +"fails." +msgstr "" + +#: ../Doc/library/resource.rst:81 +msgid "" +"Combines :func:`setrlimit` and :func:`getrlimit` in one function and " +"supports to get and set the resources limits of an arbitrary process. If " +"*pid* is 0, then the call applies to the current process. *resource* and " +"*limits* have the same meaning as in :func:`setrlimit`, except that *limits* " +"is optional." +msgstr "" + +#: ../Doc/library/resource.rst:87 +msgid "" +"When *limits* is not given the function returns the *resource* limit of the " +"process *pid*. When *limits* is given the *resource* limit of the process is " +"set and the former resource limit is returned." +msgstr "" + +#: ../Doc/library/resource.rst:91 +msgid "" +"Raises :exc:`ProcessLookupError` when *pid* can't be found and :exc:" +"`PermissionError` when the user doesn't have ``CAP_SYS_RESOURCE`` for the " +"process." +msgstr "" + +#: ../Doc/library/resource.rst:95 +msgid "Availability: Linux 2.6.36 or later with glibc 2.13 or later" +msgstr "" + +#: ../Doc/library/resource.rst:100 +msgid "" +"These symbols define resources whose consumption can be controlled using " +"the :func:`setrlimit` and :func:`getrlimit` functions described below. The " +"values of these symbols are exactly the constants used by C programs." +msgstr "" + +#: ../Doc/library/resource.rst:104 +msgid "" +"The Unix man page for :manpage:`getrlimit(2)` lists the available resources. " +"Note that not all systems use the same symbol or same value to denote the " +"same resource. This module does not attempt to mask platform differences " +"--- symbols not defined for a platform will not be available from this " +"module on that platform." +msgstr "" + +#: ../Doc/library/resource.rst:113 +msgid "" +"The maximum size (in bytes) of a core file that the current process can " +"create. This may result in the creation of a partial core file if a larger " +"core would be required to contain the entire process image." +msgstr "" + +#: ../Doc/library/resource.rst:120 +msgid "" +"The maximum amount of processor time (in seconds) that a process can use. If " +"this limit is exceeded, a :const:`SIGXCPU` signal is sent to the process. " +"(See the :mod:`signal` module documentation for information about how to " +"catch this signal and do something useful, e.g. flush open files to disk.)" +msgstr "" + +#: ../Doc/library/resource.rst:128 +msgid "The maximum size of a file which the process may create." +msgstr "" + +#: ../Doc/library/resource.rst:133 +msgid "The maximum size (in bytes) of the process's heap." +msgstr "" + +#: ../Doc/library/resource.rst:138 +msgid "" +"The maximum size (in bytes) of the call stack for the current process. This " +"only affects the stack of the main thread in a multi-threaded process." +msgstr "" + +#: ../Doc/library/resource.rst:144 +msgid "" +"The maximum resident set size that should be made available to the process." +msgstr "" + +#: ../Doc/library/resource.rst:149 +msgid "The maximum number of processes the current process may create." +msgstr "" + +#: ../Doc/library/resource.rst:154 +msgid "The maximum number of open file descriptors for the current process." +msgstr "" + +#: ../Doc/library/resource.rst:159 +msgid "The BSD name for :const:`RLIMIT_NOFILE`." +msgstr "" + +#: ../Doc/library/resource.rst:164 +msgid "The maximum address space which may be locked in memory." +msgstr "" + +#: ../Doc/library/resource.rst:169 +msgid "The largest area of mapped memory which the process may occupy." +msgstr "" + +#: ../Doc/library/resource.rst:174 +msgid "" +"The maximum area (in bytes) of address space which may be taken by the " +"process." +msgstr "" + +#: ../Doc/library/resource.rst:179 +msgid "The number of bytes that can be allocated for POSIX message queues." +msgstr "" + +#: ../Doc/library/resource.rst:181 ../Doc/library/resource.rst:218 +msgid "Availability: Linux 2.6.8 or later." +msgstr "" + +#: ../Doc/library/resource.rst:188 +msgid "The ceiling for the process's nice level (calculated as 20 - rlim_cur)." +msgstr "" + +#: ../Doc/library/resource.rst:190 ../Doc/library/resource.rst:199 +msgid "Availability: Linux 2.6.12 or later." +msgstr "" + +#: ../Doc/library/resource.rst:197 +msgid "The ceiling of the real-time priority." +msgstr "" + +#: ../Doc/library/resource.rst:206 +msgid "" +"The time limit (in microseconds) on CPU time that a process can spend under " +"real-time scheduling without making a blocking syscall." +msgstr "" + +#: ../Doc/library/resource.rst:209 +msgid "Availability: Linux 2.6.25 or later." +msgstr "" + +#: ../Doc/library/resource.rst:216 +msgid "The number of signals which the process may queue." +msgstr "" + +#: ../Doc/library/resource.rst:224 +msgid "" +"The maximum size (in bytes) of socket buffer usage for this user. This " +"limits the amount of network memory, and hence the amount of mbufs, that " +"this user may hold at any time." +msgstr "" + +#: ../Doc/library/resource.rst:228 ../Doc/library/resource.rst:239 +#: ../Doc/library/resource.rst:247 +msgid "Availability: FreeBSD 9 or later." +msgstr "" + +#: ../Doc/library/resource.rst:234 +msgid "" +"The maximum size (in bytes) of the swap space that may be reserved or used " +"by all of this user id's processes. This limit is enforced only if bit 1 of " +"the vm.overcommit sysctl is set. Please see :manpage:`tuning(7)` for a " +"complete description of this sysctl." +msgstr "" + +#: ../Doc/library/resource.rst:245 +msgid "The maximum number of pseudo-terminals created by this user id." +msgstr "" + +#: ../Doc/library/resource.rst:252 +msgid "Resource Usage" +msgstr "" + +#: ../Doc/library/resource.rst:254 +msgid "These functions are used to retrieve resource usage information:" +msgstr "" + +#: ../Doc/library/resource.rst:259 +msgid "" +"This function returns an object that describes the resources consumed by " +"either the current process or its children, as specified by the *who* " +"parameter. The *who* parameter should be specified using one of the :const:" +"`RUSAGE_\\*` constants described below." +msgstr "" + +#: ../Doc/library/resource.rst:264 +msgid "" +"The fields of the return value each describe how a particular system " +"resource has been used, e.g. amount of time spent running is user mode or " +"number of times the process was swapped out of main memory. Some values are " +"dependent on the clock tick internal, e.g. the amount of memory the process " +"is using." +msgstr "" + +#: ../Doc/library/resource.rst:269 +msgid "" +"For backward compatibility, the return value is also accessible as a tuple " +"of 16 elements." +msgstr "" + +#: ../Doc/library/resource.rst:272 +msgid "" +"The fields :attr:`ru_utime` and :attr:`ru_stime` of the return value are " +"floating point values representing the amount of time spent executing in " +"user mode and the amount of time spent executing in system mode, " +"respectively. The remaining values are integers. Consult the :manpage:" +"`getrusage(2)` man page for detailed information about these values. A brief " +"summary is presented here:" +msgstr "" + +#: ../Doc/library/resource.rst:279 ../Doc/library/sunau.rst:21 +#: ../Doc/library/uuid.rst:69 +msgid "Field" +msgstr "" + +#: ../Doc/library/resource.rst:279 +msgid "Resource" +msgstr "" + +#: ../Doc/library/resource.rst:281 +msgid ":attr:`ru_utime`" +msgstr "" + +#: ../Doc/library/resource.rst:281 +msgid "time in user mode (float)" +msgstr "" + +#: ../Doc/library/resource.rst:283 +msgid ":attr:`ru_stime`" +msgstr "" + +#: ../Doc/library/resource.rst:283 +msgid "time in system mode (float)" +msgstr "" + +#: ../Doc/library/resource.rst:285 +msgid ":attr:`ru_maxrss`" +msgstr "" + +#: ../Doc/library/resource.rst:285 +msgid "maximum resident set size" +msgstr "" + +#: ../Doc/library/resource.rst:287 +msgid ":attr:`ru_ixrss`" +msgstr "" + +#: ../Doc/library/resource.rst:287 +msgid "shared memory size" +msgstr "" + +#: ../Doc/library/resource.rst:289 +msgid ":attr:`ru_idrss`" +msgstr "" + +#: ../Doc/library/resource.rst:289 +msgid "unshared memory size" +msgstr "" + +#: ../Doc/library/resource.rst:291 ../Doc/library/zipfile.rst:551 +msgid "``5``" +msgstr "" + +#: ../Doc/library/resource.rst:291 +msgid ":attr:`ru_isrss`" +msgstr "" + +#: ../Doc/library/resource.rst:291 +msgid "unshared stack size" +msgstr "" + +#: ../Doc/library/resource.rst:293 +msgid "``6``" +msgstr "" + +#: ../Doc/library/resource.rst:293 +msgid ":attr:`ru_minflt`" +msgstr "" + +#: ../Doc/library/resource.rst:293 +msgid "page faults not requiring I/O" +msgstr "" + +#: ../Doc/library/resource.rst:295 +msgid "``7``" +msgstr "" + +#: ../Doc/library/resource.rst:295 +msgid ":attr:`ru_majflt`" +msgstr "" + +#: ../Doc/library/resource.rst:295 +msgid "page faults requiring I/O" +msgstr "" + +#: ../Doc/library/resource.rst:297 +msgid "``8``" +msgstr "" + +#: ../Doc/library/resource.rst:297 +msgid ":attr:`ru_nswap`" +msgstr "" + +#: ../Doc/library/resource.rst:297 +msgid "number of swap outs" +msgstr "" + +#: ../Doc/library/resource.rst:299 +msgid "``9``" +msgstr "" + +#: ../Doc/library/resource.rst:299 +msgid ":attr:`ru_inblock`" +msgstr "" + +#: ../Doc/library/resource.rst:299 +msgid "block input operations" +msgstr "" + +#: ../Doc/library/resource.rst:301 +msgid "``10``" +msgstr "" + +#: ../Doc/library/resource.rst:301 +msgid ":attr:`ru_oublock`" +msgstr "" + +#: ../Doc/library/resource.rst:301 +msgid "block output operations" +msgstr "" + +#: ../Doc/library/resource.rst:303 +msgid "``11``" +msgstr "" + +#: ../Doc/library/resource.rst:303 +msgid ":attr:`ru_msgsnd`" +msgstr "" + +#: ../Doc/library/resource.rst:303 +msgid "messages sent" +msgstr "" + +#: ../Doc/library/resource.rst:305 +msgid "``12``" +msgstr "" + +#: ../Doc/library/resource.rst:305 +msgid ":attr:`ru_msgrcv`" +msgstr "" + +#: ../Doc/library/resource.rst:305 +msgid "messages received" +msgstr "" + +#: ../Doc/library/resource.rst:307 +msgid "``13``" +msgstr "" + +#: ../Doc/library/resource.rst:307 +msgid ":attr:`ru_nsignals`" +msgstr "" + +#: ../Doc/library/resource.rst:307 +msgid "signals received" +msgstr "" + +#: ../Doc/library/resource.rst:309 +msgid "``14``" +msgstr "" + +#: ../Doc/library/resource.rst:309 +msgid ":attr:`ru_nvcsw`" +msgstr "" + +#: ../Doc/library/resource.rst:309 +msgid "voluntary context switches" +msgstr "" + +#: ../Doc/library/resource.rst:311 +msgid "``15``" +msgstr "" + +#: ../Doc/library/resource.rst:311 +msgid ":attr:`ru_nivcsw`" +msgstr "" + +#: ../Doc/library/resource.rst:311 +msgid "involuntary context switches" +msgstr "" + +#: ../Doc/library/resource.rst:314 +msgid "" +"This function will raise a :exc:`ValueError` if an invalid *who* parameter " +"is specified. It may also raise :exc:`error` exception in unusual " +"circumstances." +msgstr "" + +#: ../Doc/library/resource.rst:320 +msgid "" +"Returns the number of bytes in a system page. (This need not be the same as " +"the hardware page size.)" +msgstr "" + +#: ../Doc/library/resource.rst:323 +msgid "" +"The following :const:`RUSAGE_\\*` symbols are passed to the :func:" +"`getrusage` function to specify which processes information should be " +"provided for." +msgstr "" + +#: ../Doc/library/resource.rst:329 +msgid "" +"Pass to :func:`getrusage` to request resources consumed by the calling " +"process, which is the sum of resources used by all threads in the process." +msgstr "" + +#: ../Doc/library/resource.rst:335 +msgid "" +"Pass to :func:`getrusage` to request resources consumed by child processes " +"of the calling process which have been terminated and waited for." +msgstr "" + +#: ../Doc/library/resource.rst:341 +msgid "" +"Pass to :func:`getrusage` to request resources consumed by both the current " +"process and child processes. May not be available on all systems." +msgstr "" + +#: ../Doc/library/resource.rst:347 +msgid "" +"Pass to :func:`getrusage` to request resources consumed by the current " +"thread. May not be available on all systems." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:2 +msgid ":mod:`rlcompleter` --- Completion function for GNU readline" +msgstr "" + +#: ../Doc/library/rlcompleter.rst:9 +msgid "**Source code:** :source:`Lib/rlcompleter.py`" +msgstr "" + +#: ../Doc/library/rlcompleter.rst:13 +msgid "" +"The :mod:`rlcompleter` module defines a completion function suitable for " +"the :mod:`readline` module by completing valid Python identifiers and " +"keywords." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:16 +msgid "" +"When this module is imported on a Unix platform with the :mod:`readline` " +"module available, an instance of the :class:`Completer` class is " +"automatically created and its :meth:`complete` method is set as the :mod:" +"`readline` completer." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:31 +msgid "" +"The :mod:`rlcompleter` module is designed for use with Python's :ref:" +"`interactive mode `. Unless Python is run with the :option:" +"`-S` option, the module is automatically imported and configured (see :ref:" +"`rlcompleter-config`)." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:36 +msgid "" +"On platforms without :mod:`readline`, the :class:`Completer` class defined " +"by this module can still be used for custom purposes." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:43 +msgid "Completer Objects" +msgstr "" + +#: ../Doc/library/rlcompleter.rst:45 +msgid "Completer objects have the following method:" +msgstr "" + +#: ../Doc/library/rlcompleter.rst:50 +msgid "Return the *state*\\ th completion for *text*." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:52 +msgid "" +"If called for *text* that doesn't include a period character (``'.'``), it " +"will complete from names currently defined in :mod:`__main__`, :mod:" +"`builtins` and keywords (as defined by the :mod:`keyword` module)." +msgstr "" + +#: ../Doc/library/rlcompleter.rst:56 +msgid "" +"If called for a dotted name, it will try to evaluate anything without " +"obvious side-effects (functions will not be evaluated, but it can generate " +"calls to :meth:`__getattr__`) up to the last part, and find matches for the " +"rest via the :func:`dir` function. Any exception raised during the " +"evaluation of the expression is caught, silenced and :const:`None` is " +"returned." +msgstr "" + +#: ../Doc/library/runpy.rst:2 +msgid ":mod:`runpy` --- Locating and executing Python modules" +msgstr "" + +#: ../Doc/library/runpy.rst:9 +msgid "**Source code:** :source:`Lib/runpy.py`" +msgstr "" + +#: ../Doc/library/runpy.rst:13 +msgid "" +"The :mod:`runpy` module is used to locate and run Python modules without " +"importing them first. Its main use is to implement the :option:`-m` command " +"line switch that allows scripts to be located using the Python module " +"namespace rather than the filesystem." +msgstr "" + +#: ../Doc/library/runpy.rst:18 +msgid "" +"Note that this is *not* a sandbox module - all code is executed in the " +"current process, and any side effects (such as cached imports of other " +"modules) will remain in place after the functions have returned." +msgstr "" + +#: ../Doc/library/runpy.rst:22 +msgid "" +"Furthermore, any functions and classes defined by the executed code are not " +"guaranteed to work correctly after a :mod:`runpy` function has returned. If " +"that limitation is not acceptable for a given use case, :mod:`importlib` is " +"likely to be a more suitable choice than this module." +msgstr "" + +#: ../Doc/library/runpy.rst:27 +msgid "The :mod:`runpy` module provides two functions:" +msgstr "" + +#: ../Doc/library/runpy.rst:35 +msgid "" +"Execute the code of the specified module and return the resulting module " +"globals dictionary. The module's code is first located using the standard " +"import mechanism (refer to :pep:`302` for details) and then executed in a " +"fresh module namespace." +msgstr "" + +#: ../Doc/library/runpy.rst:40 +msgid "" +"The *mod_name* argument should be an absolute module name. If the module " +"name refers to a package rather than a normal module, then that package is " +"imported and the ``__main__`` submodule within that package is then executed " +"and the resulting module globals dictionary returned." +msgstr "" + +#: ../Doc/library/runpy.rst:46 +msgid "" +"The optional dictionary argument *init_globals* may be used to pre-populate " +"the module's globals dictionary before the code is executed. The supplied " +"dictionary will not be modified. If any of the special global variables " +"below are defined in the supplied dictionary, those definitions are " +"overridden by :func:`run_module`." +msgstr "" + +#: ../Doc/library/runpy.rst:52 ../Doc/library/runpy.rst:121 +msgid "" +"The special global variables ``__name__``, ``__spec__``, ``__file__``, " +"``__cached__``, ``__loader__`` and ``__package__`` are set in the globals " +"dictionary before the module code is executed (Note that this is a minimal " +"set of variables - other variables may be set implicitly as an interpreter " +"implementation detail)." +msgstr "" + +#: ../Doc/library/runpy.rst:58 +msgid "" +"``__name__`` is set to *run_name* if this optional argument is not :const:" +"`None`, to ``mod_name + '.__main__'`` if the named module is a package and " +"to the *mod_name* argument otherwise." +msgstr "" + +#: ../Doc/library/runpy.rst:62 +msgid "" +"``__spec__`` will be set appropriately for the *actually* imported module " +"(that is, ``__spec__.name`` will always be *mod_name* or ``mod_name + '." +"__main__``, never *run_name*)." +msgstr "" + +#: ../Doc/library/runpy.rst:66 +msgid "" +"``__file__``, ``__cached__``, ``__loader__`` and ``__package__`` are :ref:" +"`set as normal ` based on the module spec." +msgstr "" + +#: ../Doc/library/runpy.rst:69 +msgid "" +"If the argument *alter_sys* is supplied and evaluates to :const:`True`, then " +"``sys.argv[0]`` is updated with the value of ``__file__`` and ``sys." +"modules[__name__]`` is updated with a temporary module object for the module " +"being executed. Both ``sys.argv[0]`` and ``sys.modules[__name__]`` are " +"restored to their original values before the function returns." +msgstr "" + +#: ../Doc/library/runpy.rst:75 +msgid "" +"Note that this manipulation of :mod:`sys` is not thread-safe. Other threads " +"may see the partially initialised module, as well as the altered list of " +"arguments. It is recommended that the :mod:`sys` module be left alone when " +"invoking this function from threaded code." +msgstr "" + +#: ../Doc/library/runpy.rst:81 +msgid "" +"The :option:`-m` option offering equivalent functionality from the command " +"line." +msgstr "" + +#: ../Doc/library/runpy.rst:84 +msgid "" +"Added ability to execute packages by looking for a ``__main__`` submodule." +msgstr "" + +#: ../Doc/library/runpy.rst:87 +msgid "Added ``__cached__`` global variable (see :pep:`3147`)." +msgstr "" + +#: ../Doc/library/runpy.rst:90 +msgid "" +"Updated to take advantage of the module spec feature added by :pep:`451`. " +"This allows ``__cached__`` to be set correctly for modules run this way, as " +"well as ensuring the real module name is always accessible as ``__spec__." +"name``." +msgstr "" + +#: ../Doc/library/runpy.rst:101 +msgid "" +"Execute the code at the named filesystem location and return the resulting " +"module globals dictionary. As with a script name supplied to the CPython " +"command line, the supplied path may refer to a Python source file, a " +"compiled bytecode file or a valid sys.path entry containing a ``__main__`` " +"module (e.g. a zipfile containing a top-level ``__main__.py`` file)." +msgstr "" + +#: ../Doc/library/runpy.rst:107 +msgid "" +"For a simple script, the specified code is simply executed in a fresh module " +"namespace. For a valid sys.path entry (typically a zipfile or directory), " +"the entry is first added to the beginning of ``sys.path``. The function then " +"looks for and executes a :mod:`__main__` module using the updated path. Note " +"that there is no special protection against invoking an existing :mod:" +"`__main__` entry located elsewhere on ``sys.path`` if there is no such " +"module at the specified location." +msgstr "" + +#: ../Doc/library/runpy.rst:115 +msgid "" +"The optional dictionary argument *init_globals* may be used to pre-populate " +"the module's globals dictionary before the code is executed. The supplied " +"dictionary will not be modified. If any of the special global variables " +"below are defined in the supplied dictionary, those definitions are " +"overridden by :func:`run_path`." +msgstr "" + +#: ../Doc/library/runpy.rst:127 +msgid "" +"``__name__`` is set to *run_name* if this optional argument is not :const:" +"`None` and to ``''`` otherwise." +msgstr "" + +#: ../Doc/library/runpy.rst:130 +msgid "" +"If the supplied path directly references a script file (whether as source or " +"as precompiled byte code), then ``__file__`` will be set to the supplied " +"path, and ``__spec__``, ``__cached__``, ``__loader__`` and ``__package__`` " +"will all be set to :const:`None`." +msgstr "" + +#: ../Doc/library/runpy.rst:135 +msgid "" +"If the supplied path is a reference to a valid sys.path entry, then " +"``__spec__`` will be set appropriately for the imported ``__main__`` module " +"(that is, ``__spec__.name`` will always be ``__main__``). ``__file__``, " +"``__cached__``, ``__loader__`` and ``__package__`` will be :ref:`set as " +"normal ` based on the module spec." +msgstr "" + +#: ../Doc/library/runpy.rst:141 +msgid "" +"A number of alterations are also made to the :mod:`sys` module. Firstly, " +"``sys.path`` may be altered as described above. ``sys.argv[0]`` is updated " +"with the value of ``file_path`` and ``sys.modules[__name__]`` is updated " +"with a temporary module object for the module being executed. All " +"modifications to items in :mod:`sys` are reverted before the function " +"returns." +msgstr "" + +#: ../Doc/library/runpy.rst:148 +msgid "" +"Note that, unlike :func:`run_module`, the alterations made to :mod:`sys` are " +"not optional in this function as these adjustments are essential to allowing " +"the execution of sys.path entries. As the thread-safety limitations still " +"apply, use of this function in threaded code should be either serialised " +"with the import lock or delegated to a separate process." +msgstr "" + +#: ../Doc/library/runpy.rst:155 +msgid "" +":ref:`using-on-interface-options` for equivalent functionality on the " +"command line (``python path/to/script``)." +msgstr "" + +#: ../Doc/library/runpy.rst:160 +msgid "" +"Updated to take advantage of the module spec feature added by :pep:`451`. " +"This allows ``__cached__`` to be set correctly in the case where " +"``__main__`` is imported from a valid sys.path entry rather than being " +"executed directly." +msgstr "" + +#: ../Doc/library/runpy.rst:169 +msgid ":pep:`338` -- Executing modules as scripts" +msgstr "" + +#: ../Doc/library/runpy.rst:169 ../Doc/library/runpy.rst:172 +msgid "PEP written and implemented by Nick Coghlan." +msgstr "" + +#: ../Doc/library/runpy.rst:172 +msgid ":pep:`366` -- Main module explicit relative imports" +msgstr "" + +#: ../Doc/library/runpy.rst:175 +msgid ":pep:`451` -- A ModuleSpec Type for the Import System" +msgstr "" + +#: ../Doc/library/runpy.rst:175 +msgid "PEP written and implemented by Eric Snow" +msgstr "" + +#: ../Doc/library/runpy.rst:177 +msgid ":ref:`using-on-general` - CPython command line details" +msgstr "" + +#: ../Doc/library/runpy.rst:179 +msgid "The :func:`importlib.import_module` function" +msgstr "" + +#: ../Doc/library/sched.rst:2 +msgid ":mod:`sched` --- Event scheduler" +msgstr "" + +#: ../Doc/library/sched.rst:9 +msgid "**Source code:** :source:`Lib/sched.py`" +msgstr "" + +#: ../Doc/library/sched.rst:15 +msgid "" +"The :mod:`sched` module defines a class which implements a general purpose " +"event scheduler:" +msgstr "" + +#: ../Doc/library/sched.rst:20 +msgid "" +"The :class:`scheduler` class defines a generic interface to scheduling " +"events. It needs two functions to actually deal with the \"outside world\" " +"--- *timefunc* should be callable without arguments, and return a number " +"(the \"time\", in any units whatsoever). If time.monotonic is not available, " +"the *timefunc* default is time.time instead. The *delayfunc* function should " +"be callable with one argument, compatible with the output of *timefunc*, and " +"should delay that many time units. *delayfunc* will also be called with the " +"argument ``0`` after each event is run to allow other threads an opportunity " +"to run in multi-threaded applications." +msgstr "" + +#: ../Doc/library/sched.rst:30 +msgid "*timefunc* and *delayfunc* parameters are optional." +msgstr "" + +#: ../Doc/library/sched.rst:33 +msgid "" +":class:`scheduler` class can be safely used in multi-threaded environments." +msgstr "" + +#: ../Doc/library/sched.rst:62 +msgid "Scheduler Objects" +msgstr "" + +#: ../Doc/library/sched.rst:64 +msgid ":class:`scheduler` instances have the following methods and attributes:" +msgstr "" + +#: ../Doc/library/sched.rst:69 +msgid "" +"Schedule a new event. The *time* argument should be a numeric type " +"compatible with the return value of the *timefunc* function passed to the " +"constructor. Events scheduled for the same *time* will be executed in the " +"order of their *priority*." +msgstr "" + +#: ../Doc/library/sched.rst:74 +msgid "" +"Executing the event means executing ``action(*argument, **kwargs)``. " +"*argument* is a sequence holding the positional arguments for *action*. " +"*kwargs* is a dictionary holding the keyword arguments for *action*." +msgstr "" + +#: ../Doc/library/sched.rst:78 +msgid "" +"Return value is an event which may be used for later cancellation of the " +"event (see :meth:`cancel`)." +msgstr "" + +#: ../Doc/library/sched.rst:81 ../Doc/library/sched.rst:94 +msgid "*argument* parameter is optional." +msgstr "" + +#: ../Doc/library/sched.rst:84 ../Doc/library/sched.rst:97 +msgid "*kwargs* parameter was added." +msgstr "" + +#: ../Doc/library/sched.rst:90 +msgid "" +"Schedule an event for *delay* more time units. Other than the relative time, " +"the other arguments, the effect and the return value are the same as those " +"for :meth:`enterabs`." +msgstr "" + +#: ../Doc/library/sched.rst:102 +msgid "" +"Remove the event from the queue. If *event* is not an event currently in the " +"queue, this method will raise a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/sched.rst:108 +msgid "Return true if the event queue is empty." +msgstr "" + +#: ../Doc/library/sched.rst:113 +msgid "" +"Run all scheduled events. This method will wait (using the :func:" +"`delayfunc` function passed to the constructor) for the next event, then " +"execute it and so on until there are no more scheduled events." +msgstr "" + +#: ../Doc/library/sched.rst:117 +msgid "" +"If *blocking* is false executes the scheduled events due to expire soonest " +"(if any) and then return the deadline of the next scheduled call in the " +"scheduler (if any)." +msgstr "" + +#: ../Doc/library/sched.rst:121 +msgid "" +"Either *action* or *delayfunc* can raise an exception. In either case, the " +"scheduler will maintain a consistent state and propagate the exception. If " +"an exception is raised by *action*, the event will not be attempted in " +"future calls to :meth:`run`." +msgstr "" + +#: ../Doc/library/sched.rst:126 +msgid "" +"If a sequence of events takes longer to run than the time available before " +"the next event, the scheduler will simply fall behind. No events will be " +"dropped; the calling code is responsible for canceling events which are no " +"longer pertinent." +msgstr "" + +#: ../Doc/library/sched.rst:131 +msgid "*blocking* parameter was added." +msgstr "" + +#: ../Doc/library/sched.rst:136 +msgid "" +"Read-only attribute returning a list of upcoming events in the order they " +"will be run. Each event is shown as a :term:`named tuple` with the " +"following fields: time, priority, action, argument, kwargs." +msgstr "" + +#: ../Doc/library/secrets.rst:2 +msgid ":mod:`secrets` --- Generate secure random numbers for managing secrets" +msgstr "" + +#: ../Doc/library/secrets.rst:16 +msgid "**Source code:** :source:`Lib/secrets.py`" +msgstr "" + +#: ../Doc/library/secrets.rst:20 +msgid "" +"The :mod:`secrets` module is used for generating cryptographically strong " +"random numbers suitable for managing data such as passwords, account " +"authentication, security tokens, and related secrets." +msgstr "" + +#: ../Doc/library/secrets.rst:24 +msgid "" +"In particularly, :mod:`secrets` should be used in preference to the default " +"pseudo-random number generator in the :mod:`random` module, which is " +"designed for modelling and simulation, not security or cryptography." +msgstr "" + +#: ../Doc/library/secrets.rst:30 +msgid ":pep:`506`" +msgstr "" + +#: ../Doc/library/secrets.rst:36 +msgid "" +"The :mod:`secrets` module provides access to the most secure source of " +"randomness that your operating system provides." +msgstr "" + +#: ../Doc/library/secrets.rst:41 +msgid "" +"A class for generating random numbers using the highest-quality sources " +"provided by the operating system. See :class:`random.SystemRandom` for " +"additional details." +msgstr "" + +#: ../Doc/library/secrets.rst:47 +msgid "Return a randomly-chosen element from a non-empty sequence." +msgstr "" + +#: ../Doc/library/secrets.rst:51 +msgid "Return a random int in the range [0, *n*)." +msgstr "" + +#: ../Doc/library/secrets.rst:55 +msgid "Return an int with *k* random bits." +msgstr "" + +#: ../Doc/library/secrets.rst:59 +msgid "Generating tokens" +msgstr "" + +#: ../Doc/library/secrets.rst:61 +msgid "" +"The :mod:`secrets` module provides functions for generating secure tokens, " +"suitable for applications such as password resets, hard-to-guess URLs, and " +"similar." +msgstr "" + +#: ../Doc/library/secrets.rst:67 +msgid "" +"Return a random byte string containing *nbytes* number of bytes. If *nbytes* " +"is ``None`` or not supplied, a reasonable default is used." +msgstr "" + +#: ../Doc/library/secrets.rst:79 +msgid "" +"Return a random text string, in hexadecimal. The string has *nbytes* random " +"bytes, each byte converted to two hex digits. If *nbytes* is ``None`` or " +"not supplied, a reasonable default is used." +msgstr "" + +#: ../Doc/library/secrets.rst:90 +msgid "" +"Return a random URL-safe text string, containing *nbytes* random bytes. The " +"text is Base64 encoded, so on average each byte results in approximately 1.3 " +"characters. If *nbytes* is ``None`` or not supplied, a reasonable default " +"is used." +msgstr "" + +#: ../Doc/library/secrets.rst:102 +msgid "How many bytes should tokens use?" +msgstr "" + +#: ../Doc/library/secrets.rst:104 +msgid "" +"To be secure against `brute-force attacks `_, tokens need to have sufficient randomness. " +"Unfortunately, what is considered sufficient will necessarily increase as " +"computers get more powerful and able to make more guesses in a shorter " +"period. As of 2015, it is believed that 32 bytes (256 bits) of randomness " +"is sufficient for the typical use-case expected for the :mod:`secrets` " +"module." +msgstr "" + +#: ../Doc/library/secrets.rst:112 +msgid "" +"For those who want to manage their own token length, you can explicitly " +"specify how much randomness is used for tokens by giving an :class:`int` " +"argument to the various ``token_*`` functions. That argument is taken as " +"the number of bytes of randomness to use." +msgstr "" + +#: ../Doc/library/secrets.rst:117 +msgid "" +"Otherwise, if no argument is provided, or if the argument is ``None``, the " +"``token_*`` functions will use a reasonable default instead." +msgstr "" + +#: ../Doc/library/secrets.rst:122 +msgid "" +"That default is subject to change at any time, including during maintenance " +"releases." +msgstr "" + +#: ../Doc/library/secrets.rst:127 ../Doc/library/socket.rst:523 +#: ../Doc/library/sysconfig.rst:162 +msgid "Other functions" +msgstr "" + +#: ../Doc/library/secrets.rst:131 +msgid "" +"Return ``True`` if strings *a* and *b* are equal, otherwise ``False``, in " +"such a way as to reduce the risk of `timing attacks `_. See :func:`hmac.compare_digest` for additional " +"details." +msgstr "" + +#: ../Doc/library/secrets.rst:138 +msgid "Recipes and best practices" +msgstr "" + +#: ../Doc/library/secrets.rst:140 +msgid "" +"This section shows recipes and best practices for using :mod:`secrets` to " +"manage a basic level of security." +msgstr "" + +#: ../Doc/library/secrets.rst:143 +msgid "Generate an eight-character alphanumeric password:" +msgstr "" + +#: ../Doc/library/secrets.rst:154 +msgid "" +"Applications should not `store passwords in a recoverable format `_, whether plain text or encrypted. " +"They should be salted and hashed using a cryptographically-strong one-way " +"(irreversible) hash function." +msgstr "" + +#: ../Doc/library/secrets.rst:160 +msgid "" +"Generate a ten-character alphanumeric password with at least one lowercase " +"character, at least one uppercase character, and at least three digits:" +msgstr "" + +#: ../Doc/library/secrets.rst:176 +msgid "Generate an `XKCD-style passphrase `_:" +msgstr "" + +#: ../Doc/library/secrets.rst:187 +msgid "" +"Generate a hard-to-guess temporary URL containing a security token suitable " +"for password recovery applications:" +msgstr "" + +#: ../Doc/library/select.rst:2 +msgid ":mod:`select` --- Waiting for I/O completion" +msgstr "" + +#: ../Doc/library/select.rst:9 +msgid "" +"This module provides access to the :c:func:`select` and :c:func:`poll` " +"functions available in most operating systems, :c:func:`devpoll` available " +"on Solaris and derivatives, :c:func:`epoll` available on Linux 2.5+ and :c:" +"func:`kqueue` available on most BSD. Note that on Windows, it only works for " +"sockets; on other operating systems, it also works for other file types (in " +"particular, on Unix, it works on pipes). It cannot be used on regular files " +"to determine whether a file has grown since it was last read." +msgstr "" + +#: ../Doc/library/select.rst:20 +msgid "" +"The :mod:`selectors` module allows high-level and efficient I/O " +"multiplexing, built upon the :mod:`select` module primitives. Users are " +"encouraged to use the :mod:`selectors` module instead, unless they want " +"precise control over the OS-level primitives used." +msgstr "" + +#: ../Doc/library/select.rst:39 +msgid "" +"(Only supported on Solaris and derivatives.) Returns a ``/dev/poll`` " +"polling object; see section :ref:`devpoll-objects` below for the methods " +"supported by devpoll objects." +msgstr "" + +#: ../Doc/library/select.rst:43 +msgid "" +":c:func:`devpoll` objects are linked to the number of file descriptors " +"allowed at the time of instantiation. If your program reduces this value, :c:" +"func:`devpoll` will fail. If your program increases this value, :c:func:" +"`devpoll` may return an incomplete list of active file descriptors." +msgstr "" + +#: ../Doc/library/select.rst:49 ../Doc/library/select.rst:69 +#: ../Doc/library/select.rst:96 +msgid "The new file descriptor is :ref:`non-inheritable `." +msgstr "" + +#: ../Doc/library/select.rst:58 +msgid "" +"(Only supported on Linux 2.5.44 and newer.) Return an edge polling object, " +"which can be used as Edge or Level Triggered interface for I/O events. " +"*sizehint* and *flags* are deprecated and completely ignored." +msgstr "" + +#: ../Doc/library/select.rst:62 +msgid "" +"See the :ref:`epoll-objects` section below for the methods supported by " +"epolling objects." +msgstr "" + +#: ../Doc/library/select.rst:65 +msgid "" +"``epoll`` objects support the context management protocol: when used in a :" +"keyword:`with` statement, the new file descriptor is automatically closed at " +"the end of the block." +msgstr "" + +#: ../Doc/library/select.rst:71 +msgid "Added the *flags* parameter." +msgstr "" + +#: ../Doc/library/select.rst:74 +msgid "" +"Support for the :keyword:`with` statement was added. The new file descriptor " +"is now non-inheritable." +msgstr "" + +#: ../Doc/library/select.rst:78 +msgid "" +"The *flags* parameter. ``select.EPOLL_CLOEXEC`` is used by default now. " +"Use :func:`os.set_inheritable` to make the file descriptor inheritable." +msgstr "" + +#: ../Doc/library/select.rst:85 +msgid "" +"(Not supported by all operating systems.) Returns a polling object, which " +"supports registering and unregistering file descriptors, and then polling " +"them for I/O events; see section :ref:`poll-objects` below for the methods " +"supported by polling objects." +msgstr "" + +#: ../Doc/library/select.rst:93 +msgid "" +"(Only supported on BSD.) Returns a kernel queue object; see section :ref:" +"`kqueue-objects` below for the methods supported by kqueue objects." +msgstr "" + +#: ../Doc/library/select.rst:104 +msgid "" +"(Only supported on BSD.) Returns a kernel event object; see section :ref:" +"`kevent-objects` below for the methods supported by kevent objects." +msgstr "" + +#: ../Doc/library/select.rst:110 +msgid "" +"This is a straightforward interface to the Unix :c:func:`select` system " +"call. The first three arguments are sequences of 'waitable objects': either " +"integers representing file descriptors or objects with a parameterless " +"method named :meth:`~io.IOBase.fileno` returning such an integer:" +msgstr "" + +#: ../Doc/library/select.rst:115 +msgid "*rlist*: wait until ready for reading" +msgstr "" + +#: ../Doc/library/select.rst:116 +msgid "*wlist*: wait until ready for writing" +msgstr "" + +#: ../Doc/library/select.rst:117 +msgid "" +"*xlist*: wait for an \"exceptional condition\" (see the manual page for what " +"your system considers such a condition)" +msgstr "" + +#: ../Doc/library/select.rst:120 +msgid "" +"Empty sequences are allowed, but acceptance of three empty sequences is " +"platform-dependent. (It is known to work on Unix but not on Windows.) The " +"optional *timeout* argument specifies a time-out as a floating point number " +"in seconds. When the *timeout* argument is omitted the function blocks " +"until at least one file descriptor is ready. A time-out value of zero " +"specifies a poll and never blocks." +msgstr "" + +#: ../Doc/library/select.rst:127 +msgid "" +"The return value is a triple of lists of objects that are ready: subsets of " +"the first three arguments. When the time-out is reached without a file " +"descriptor becoming ready, three empty lists are returned." +msgstr "" + +#: ../Doc/library/select.rst:135 +msgid "" +"Among the acceptable object types in the sequences are Python :term:`file " +"objects ` (e.g. ``sys.stdin``, or objects returned by :func:" +"`open` or :func:`os.popen`), socket objects returned by :func:`socket." +"socket`. You may also define a :dfn:`wrapper` class yourself, as long as it " +"has an appropriate :meth:`~io.IOBase.fileno` method (that really returns a " +"file descriptor, not just a random integer)." +msgstr "" + +#: ../Doc/library/select.rst:146 +msgid "" +"File objects on Windows are not acceptable, but sockets are. On Windows, " +"the underlying :c:func:`select` function is provided by the WinSock library, " +"and does not handle file descriptors that don't originate from WinSock." +msgstr "" + +#: ../Doc/library/select.rst:151 ../Doc/library/select.rst:255 +#: ../Doc/library/select.rst:349 ../Doc/library/select.rst:437 +#: ../Doc/library/select.rst:477 +msgid "" +"The function is now retried with a recomputed timeout when interrupted by a " +"signal, except if the signal handler raises an exception (see :pep:`475` for " +"the rationale), instead of raising :exc:`InterruptedError`." +msgstr "" + +#: ../Doc/library/select.rst:160 +msgid "" +"The minimum number of bytes which can be written without blocking to a pipe " +"when the pipe has been reported as ready for writing by :func:`~select." +"select`, :func:`poll` or another interface in this module. This doesn't " +"apply to other kind of file-like objects such as sockets." +msgstr "" + +#: ../Doc/library/select.rst:165 +msgid "" +"This value is guaranteed by POSIX to be at least 512. Availability: Unix." +msgstr "" + +#: ../Doc/library/select.rst:173 +msgid "``/dev/poll`` Polling Objects" +msgstr "" + +#: ../Doc/library/select.rst:175 +msgid "" +"Solaris and derivatives have ``/dev/poll``. While :c:func:`select` is " +"O(highest file descriptor) and :c:func:`poll` is O(number of file " +"descriptors), ``/dev/poll`` is O(active file descriptors)." +msgstr "" + +#: ../Doc/library/select.rst:179 +msgid "" +"``/dev/poll`` behaviour is very close to the standard :c:func:`poll` object." +msgstr "" + +#: ../Doc/library/select.rst:185 +msgid "Close the file descriptor of the polling object." +msgstr "" + +#: ../Doc/library/select.rst:192 +msgid "``True`` if the polling object is closed." +msgstr "" + +#: ../Doc/library/select.rst:199 +msgid "Return the file descriptor number of the polling object." +msgstr "" + +#: ../Doc/library/select.rst:206 ../Doc/library/select.rst:372 +msgid "" +"Register a file descriptor with the polling object. Future calls to the :" +"meth:`poll` method will then check whether the file descriptor has any " +"pending I/O events. *fd* can be either an integer, or an object with a :" +"meth:`~io.IOBase.fileno` method that returns an integer. File objects " +"implement :meth:`!fileno`, so they can also be used as the argument." +msgstr "" + +#: ../Doc/library/select.rst:212 +msgid "" +"*eventmask* is an optional bitmask describing the type of events you want to " +"check for. The constants are the same that with :c:func:`poll` object. The " +"default value is a combination of the constants :const:`POLLIN`, :const:" +"`POLLPRI`, and :const:`POLLOUT`." +msgstr "" + +#: ../Doc/library/select.rst:219 +msgid "" +"Registering a file descriptor that's already registered is not an error, but " +"the result is undefined. The appropriate action is to unregister or modify " +"it first. This is an important difference compared with :c:func:`poll`." +msgstr "" + +#: ../Doc/library/select.rst:227 +msgid "" +"This method does an :meth:`unregister` followed by a :meth:`register`. It is " +"(a bit) more efficient that doing the same explicitly." +msgstr "" + +#: ../Doc/library/select.rst:234 ../Doc/library/select.rst:416 +msgid "" +"Remove a file descriptor being tracked by a polling object. Just like the :" +"meth:`register` method, *fd* can be an integer or an object with a :meth:" +"`~io.IOBase.fileno` method that returns an integer." +msgstr "" + +#: ../Doc/library/select.rst:238 +msgid "" +"Attempting to remove a file descriptor that was never registered is safely " +"ignored." +msgstr "" + +#: ../Doc/library/select.rst:244 +msgid "" +"Polls the set of registered file descriptors, and returns a possibly-empty " +"list containing ``(fd, event)`` 2-tuples for the descriptors that have " +"events or errors to report. *fd* is the file descriptor, and *event* is a " +"bitmask with bits set for the reported events for that descriptor --- :const:" +"`POLLIN` for waiting input, :const:`POLLOUT` to indicate that the descriptor " +"can be written to, and so forth. An empty list indicates that the call timed " +"out and no file descriptors had any events to report. If *timeout* is given, " +"it specifies the length of time in milliseconds which the system will wait " +"for events before returning. If *timeout* is omitted, -1, or :const:`None`, " +"the call will block until there is an event for this poll object." +msgstr "" + +#: ../Doc/library/select.rst:265 +msgid "Edge and Level Trigger Polling (epoll) Objects" +msgstr "" + +#: ../Doc/library/select.rst:267 +msgid "http://linux.die.net/man/4/epoll" +msgstr "" + +#: ../Doc/library/select.rst:269 +msgid "*eventmask*" +msgstr "" + +#: ../Doc/library/select.rst:274 +msgid ":const:`EPOLLIN`" +msgstr "" + +#: ../Doc/library/select.rst:274 ../Doc/library/selectors.rst:62 +msgid "Available for read" +msgstr "" + +#: ../Doc/library/select.rst:276 +msgid ":const:`EPOLLOUT`" +msgstr "" + +#: ../Doc/library/select.rst:276 ../Doc/library/selectors.rst:64 +msgid "Available for write" +msgstr "" + +#: ../Doc/library/select.rst:278 +msgid ":const:`EPOLLPRI`" +msgstr "" + +#: ../Doc/library/select.rst:278 +msgid "Urgent data for read" +msgstr "" + +#: ../Doc/library/select.rst:280 +msgid ":const:`EPOLLERR`" +msgstr "" + +#: ../Doc/library/select.rst:280 +msgid "Error condition happened on the assoc. fd" +msgstr "" + +#: ../Doc/library/select.rst:282 +msgid ":const:`EPOLLHUP`" +msgstr "" + +#: ../Doc/library/select.rst:282 +msgid "Hang up happened on the assoc. fd" +msgstr "" + +#: ../Doc/library/select.rst:284 +msgid ":const:`EPOLLET`" +msgstr "" + +#: ../Doc/library/select.rst:284 +msgid "Set Edge Trigger behavior, the default is Level Trigger behavior" +msgstr "" + +#: ../Doc/library/select.rst:287 +msgid ":const:`EPOLLONESHOT`" +msgstr "" + +#: ../Doc/library/select.rst:287 +msgid "" +"Set one-shot behavior. After one event is pulled out, the fd is internally " +"disabled" +msgstr "" + +#: ../Doc/library/select.rst:290 +msgid ":const:`EPOLLEXCLUSIVE`" +msgstr "" + +#: ../Doc/library/select.rst:290 +msgid "" +"Wake only one epoll object when the associated fd has an event. The default " +"(if this flag is not set) is to wake all epoll objects polling on on a fd." +msgstr "" + +#: ../Doc/library/select.rst:295 +msgid ":const:`EPOLLRDHUP`" +msgstr "" + +#: ../Doc/library/select.rst:295 +msgid "" +"Stream socket peer closed connection or shut down writing half of connection." +msgstr "" + +#: ../Doc/library/select.rst:298 +msgid ":const:`EPOLLRDNORM`" +msgstr "" + +#: ../Doc/library/select.rst:298 +msgid "Equivalent to :const:`EPOLLIN`" +msgstr "" + +#: ../Doc/library/select.rst:300 +msgid ":const:`EPOLLRDBAND`" +msgstr "" + +#: ../Doc/library/select.rst:300 +msgid "Priority data band can be read." +msgstr "" + +#: ../Doc/library/select.rst:302 +msgid ":const:`EPOLLWRNORM`" +msgstr "" + +#: ../Doc/library/select.rst:302 +msgid "Equivalent to :const:`EPOLLOUT`" +msgstr "" + +#: ../Doc/library/select.rst:304 +msgid ":const:`EPOLLWRBAND`" +msgstr "" + +#: ../Doc/library/select.rst:304 +msgid "Priority data may be written." +msgstr "" + +#: ../Doc/library/select.rst:306 +msgid ":const:`EPOLLMSG`" +msgstr "" + +#: ../Doc/library/select.rst:306 +msgid "Ignored." +msgstr "" + +#: ../Doc/library/select.rst:312 +msgid "Close the control file descriptor of the epoll object." +msgstr "" + +#: ../Doc/library/select.rst:317 +msgid "``True`` if the epoll object is closed." +msgstr "" + +#: ../Doc/library/select.rst:322 ../Doc/library/select.rst:461 +msgid "Return the file descriptor number of the control fd." +msgstr "" + +#: ../Doc/library/select.rst:327 +msgid "Create an epoll object from a given file descriptor." +msgstr "" + +#: ../Doc/library/select.rst:332 +msgid "Register a fd descriptor with the epoll object." +msgstr "" + +#: ../Doc/library/select.rst:337 +msgid "Modify a registered file descriptor." +msgstr "" + +#: ../Doc/library/select.rst:342 +msgid "Remove a registered file descriptor from the epoll object." +msgstr "" + +#: ../Doc/library/select.rst:347 +msgid "Wait for events. timeout in seconds (float)" +msgstr "" + +#: ../Doc/library/select.rst:359 +msgid "Polling Objects" +msgstr "" + +#: ../Doc/library/select.rst:361 +msgid "" +"The :c:func:`poll` system call, supported on most Unix systems, provides " +"better scalability for network servers that service many, many clients at " +"the same time. :c:func:`poll` scales better because the system call only " +"requires listing the file descriptors of interest, while :c:func:`select` " +"builds a bitmap, turns on bits for the fds of interest, and then afterward " +"the whole bitmap has to be linearly scanned again. :c:func:`select` is " +"O(highest file descriptor), while :c:func:`poll` is O(number of file " +"descriptors)." +msgstr "" + +#: ../Doc/library/select.rst:378 +msgid "" +"*eventmask* is an optional bitmask describing the type of events you want to " +"check for, and can be a combination of the constants :const:`POLLIN`, :const:" +"`POLLPRI`, and :const:`POLLOUT`, described in the table below. If not " +"specified, the default value used will check for all 3 types of events." +msgstr "" + +#: ../Doc/library/select.rst:386 +msgid ":const:`POLLIN`" +msgstr "" + +#: ../Doc/library/select.rst:386 +msgid "There is data to read" +msgstr "" + +#: ../Doc/library/select.rst:388 +msgid ":const:`POLLPRI`" +msgstr "" + +#: ../Doc/library/select.rst:388 +msgid "There is urgent data to read" +msgstr "" + +#: ../Doc/library/select.rst:390 +msgid ":const:`POLLOUT`" +msgstr "" + +#: ../Doc/library/select.rst:390 +msgid "Ready for output: writing will not block" +msgstr "" + +#: ../Doc/library/select.rst:392 +msgid ":const:`POLLERR`" +msgstr "" + +#: ../Doc/library/select.rst:392 +msgid "Error condition of some sort" +msgstr "" + +#: ../Doc/library/select.rst:394 +msgid ":const:`POLLHUP`" +msgstr "" + +#: ../Doc/library/select.rst:394 +msgid "Hung up" +msgstr "" + +#: ../Doc/library/select.rst:396 +msgid ":const:`POLLRDHUP`" +msgstr "" + +#: ../Doc/library/select.rst:396 +msgid "" +"Stream socket peer closed connection, or shut down writing half of connection" +msgstr "" + +#: ../Doc/library/select.rst:399 +msgid ":const:`POLLNVAL`" +msgstr "" + +#: ../Doc/library/select.rst:399 +msgid "Invalid request: descriptor not open" +msgstr "" + +#: ../Doc/library/select.rst:402 +msgid "" +"Registering a file descriptor that's already registered is not an error, and " +"has the same effect as registering the descriptor exactly once." +msgstr "" + +#: ../Doc/library/select.rst:408 +msgid "" +"Modifies an already registered fd. This has the same effect as " +"``register(fd, eventmask)``. Attempting to modify a file descriptor that " +"was never registered causes an :exc:`OSError` exception with errno :const:" +"`ENOENT` to be raised." +msgstr "" + +#: ../Doc/library/select.rst:420 +msgid "" +"Attempting to remove a file descriptor that was never registered causes a :" +"exc:`KeyError` exception to be raised." +msgstr "" + +#: ../Doc/library/select.rst:426 +msgid "" +"Polls the set of registered file descriptors, and returns a possibly-empty " +"list containing ``(fd, event)`` 2-tuples for the descriptors that have " +"events or errors to report. *fd* is the file descriptor, and *event* is a " +"bitmask with bits set for the reported events for that descriptor --- :const:" +"`POLLIN` for waiting input, :const:`POLLOUT` to indicate that the descriptor " +"can be written to, and so forth. An empty list indicates that the call timed " +"out and no file descriptors had any events to report. If *timeout* is given, " +"it specifies the length of time in milliseconds which the system will wait " +"for events before returning. If *timeout* is omitted, negative, or :const:" +"`None`, the call will block until there is an event for this poll object." +msgstr "" + +#: ../Doc/library/select.rst:447 +msgid "Kqueue Objects" +msgstr "" + +#: ../Doc/library/select.rst:451 +msgid "Close the control file descriptor of the kqueue object." +msgstr "" + +#: ../Doc/library/select.rst:456 +msgid "``True`` if the kqueue object is closed." +msgstr "" + +#: ../Doc/library/select.rst:466 +msgid "Create a kqueue object from a given file descriptor." +msgstr "" + +#: ../Doc/library/select.rst:471 +msgid "Low level interface to kevent" +msgstr "" + +#: ../Doc/library/select.rst:473 +msgid "changelist must be an iterable of kevent object or None" +msgstr "" + +#: ../Doc/library/select.rst:474 +msgid "max_events must be 0 or a positive integer" +msgstr "" + +#: ../Doc/library/select.rst:475 +msgid "timeout in seconds (floats possible)" +msgstr "" + +#: ../Doc/library/select.rst:487 +msgid "Kevent Objects" +msgstr "" + +#: ../Doc/library/select.rst:489 +msgid "https://www.freebsd.org/cgi/man.cgi?query=kqueue&sektion=2" +msgstr "" + +#: ../Doc/library/select.rst:493 +msgid "" +"Value used to identify the event. The interpretation depends on the filter " +"but it's usually the file descriptor. In the constructor ident can either be " +"an int or an object with a :meth:`~io.IOBase.fileno` method. kevent stores " +"the integer internally." +msgstr "" + +#: ../Doc/library/select.rst:500 +msgid "Name of the kernel filter." +msgstr "" + +#: ../Doc/library/select.rst:505 +msgid ":const:`KQ_FILTER_READ`" +msgstr "" + +#: ../Doc/library/select.rst:505 +msgid "Takes a descriptor and returns whenever there is data available to read" +msgstr "" + +#: ../Doc/library/select.rst:508 +msgid ":const:`KQ_FILTER_WRITE`" +msgstr "" + +#: ../Doc/library/select.rst:508 +msgid "" +"Takes a descriptor and returns whenever there is data available to write" +msgstr "" + +#: ../Doc/library/select.rst:511 +msgid ":const:`KQ_FILTER_AIO`" +msgstr "" + +#: ../Doc/library/select.rst:511 +msgid "AIO requests" +msgstr "" + +#: ../Doc/library/select.rst:513 +msgid ":const:`KQ_FILTER_VNODE`" +msgstr "" + +#: ../Doc/library/select.rst:513 +msgid "" +"Returns when one or more of the requested events watched in *fflag* occurs" +msgstr "" + +#: ../Doc/library/select.rst:516 +msgid ":const:`KQ_FILTER_PROC`" +msgstr "" + +#: ../Doc/library/select.rst:516 +msgid "Watch for events on a process id" +msgstr "" + +#: ../Doc/library/select.rst:518 +msgid ":const:`KQ_FILTER_NETDEV`" +msgstr "" + +#: ../Doc/library/select.rst:518 +msgid "Watch for events on a network device [not available on Mac OS X]" +msgstr "" + +#: ../Doc/library/select.rst:521 +msgid ":const:`KQ_FILTER_SIGNAL`" +msgstr "" + +#: ../Doc/library/select.rst:521 +msgid "Returns whenever the watched signal is delivered to the process" +msgstr "" + +#: ../Doc/library/select.rst:524 +msgid ":const:`KQ_FILTER_TIMER`" +msgstr "" + +#: ../Doc/library/select.rst:524 +msgid "Establishes an arbitrary timer" +msgstr "" + +#: ../Doc/library/select.rst:529 +msgid "Filter action." +msgstr "" + +#: ../Doc/library/select.rst:534 +msgid ":const:`KQ_EV_ADD`" +msgstr "" + +#: ../Doc/library/select.rst:534 +msgid "Adds or modifies an event" +msgstr "" + +#: ../Doc/library/select.rst:536 +msgid ":const:`KQ_EV_DELETE`" +msgstr "" + +#: ../Doc/library/select.rst:536 +msgid "Removes an event from the queue" +msgstr "" + +#: ../Doc/library/select.rst:538 +msgid ":const:`KQ_EV_ENABLE`" +msgstr "" + +#: ../Doc/library/select.rst:538 +msgid "Permitscontrol() to returns the event" +msgstr "" + +#: ../Doc/library/select.rst:540 +msgid ":const:`KQ_EV_DISABLE`" +msgstr "" + +#: ../Doc/library/select.rst:540 +msgid "Disablesevent" +msgstr "" + +#: ../Doc/library/select.rst:542 +msgid ":const:`KQ_EV_ONESHOT`" +msgstr "" + +#: ../Doc/library/select.rst:542 +msgid "Removes event after first occurrence" +msgstr "" + +#: ../Doc/library/select.rst:544 +msgid ":const:`KQ_EV_CLEAR`" +msgstr "" + +#: ../Doc/library/select.rst:544 +msgid "Reset the state after an event is retrieved" +msgstr "" + +#: ../Doc/library/select.rst:546 +msgid ":const:`KQ_EV_SYSFLAGS`" +msgstr "" + +#: ../Doc/library/select.rst:546 ../Doc/library/select.rst:548 +msgid "internal event" +msgstr "" + +#: ../Doc/library/select.rst:548 +msgid ":const:`KQ_EV_FLAG1`" +msgstr "" + +#: ../Doc/library/select.rst:550 +msgid ":const:`KQ_EV_EOF`" +msgstr "" + +#: ../Doc/library/select.rst:550 +msgid "Filter specific EOF condition" +msgstr "" + +#: ../Doc/library/select.rst:552 +msgid ":const:`KQ_EV_ERROR`" +msgstr "" + +#: ../Doc/library/select.rst:552 +msgid "See return values" +msgstr "" + +#: ../Doc/library/select.rst:558 +msgid "Filter specific flags." +msgstr "" + +#: ../Doc/library/select.rst:560 +msgid ":const:`KQ_FILTER_READ` and :const:`KQ_FILTER_WRITE` filter flags:" +msgstr "" + +#: ../Doc/library/select.rst:565 +msgid ":const:`KQ_NOTE_LOWAT`" +msgstr "" + +#: ../Doc/library/select.rst:565 +msgid "low water mark of a socket buffer" +msgstr "" + +#: ../Doc/library/select.rst:568 +msgid ":const:`KQ_FILTER_VNODE` filter flags:" +msgstr "" + +#: ../Doc/library/select.rst:573 +msgid ":const:`KQ_NOTE_DELETE`" +msgstr "" + +#: ../Doc/library/select.rst:573 +msgid "*unlink()* was called" +msgstr "" + +#: ../Doc/library/select.rst:575 +msgid ":const:`KQ_NOTE_WRITE`" +msgstr "" + +#: ../Doc/library/select.rst:575 +msgid "a write occurred" +msgstr "" + +#: ../Doc/library/select.rst:577 +msgid ":const:`KQ_NOTE_EXTEND`" +msgstr "" + +#: ../Doc/library/select.rst:577 +msgid "the file was extended" +msgstr "" + +#: ../Doc/library/select.rst:579 +msgid ":const:`KQ_NOTE_ATTRIB`" +msgstr "" + +#: ../Doc/library/select.rst:579 +msgid "an attribute was changed" +msgstr "" + +#: ../Doc/library/select.rst:581 +msgid ":const:`KQ_NOTE_LINK`" +msgstr "" + +#: ../Doc/library/select.rst:581 +msgid "the link count has changed" +msgstr "" + +#: ../Doc/library/select.rst:583 +msgid ":const:`KQ_NOTE_RENAME`" +msgstr "" + +#: ../Doc/library/select.rst:583 +msgid "the file was renamed" +msgstr "" + +#: ../Doc/library/select.rst:585 +msgid ":const:`KQ_NOTE_REVOKE`" +msgstr "" + +#: ../Doc/library/select.rst:585 +msgid "access to the file was revoked" +msgstr "" + +#: ../Doc/library/select.rst:588 +msgid ":const:`KQ_FILTER_PROC` filter flags:" +msgstr "" + +#: ../Doc/library/select.rst:593 +msgid ":const:`KQ_NOTE_EXIT`" +msgstr "" + +#: ../Doc/library/select.rst:593 +msgid "the process has exited" +msgstr "" + +#: ../Doc/library/select.rst:595 +msgid ":const:`KQ_NOTE_FORK`" +msgstr "" + +#: ../Doc/library/select.rst:595 +msgid "the process has called *fork()*" +msgstr "" + +#: ../Doc/library/select.rst:597 +msgid ":const:`KQ_NOTE_EXEC`" +msgstr "" + +#: ../Doc/library/select.rst:597 +msgid "the process has executed a new process" +msgstr "" + +#: ../Doc/library/select.rst:599 +msgid ":const:`KQ_NOTE_PCTRLMASK`" +msgstr "" + +#: ../Doc/library/select.rst:599 ../Doc/library/select.rst:601 +msgid "internal filter flag" +msgstr "" + +#: ../Doc/library/select.rst:601 +msgid ":const:`KQ_NOTE_PDATAMASK`" +msgstr "" + +#: ../Doc/library/select.rst:603 +msgid ":const:`KQ_NOTE_TRACK`" +msgstr "" + +#: ../Doc/library/select.rst:603 +msgid "follow a process across *fork()*" +msgstr "" + +#: ../Doc/library/select.rst:605 +msgid ":const:`KQ_NOTE_CHILD`" +msgstr "" + +#: ../Doc/library/select.rst:605 +msgid "returned on the child process for *NOTE_TRACK*" +msgstr "" + +#: ../Doc/library/select.rst:608 +msgid ":const:`KQ_NOTE_TRACKERR`" +msgstr "" + +#: ../Doc/library/select.rst:608 +msgid "unable to attach to a child" +msgstr "" + +#: ../Doc/library/select.rst:611 +msgid ":const:`KQ_FILTER_NETDEV` filter flags (not available on Mac OS X):" +msgstr "" + +#: ../Doc/library/select.rst:616 +msgid ":const:`KQ_NOTE_LINKUP`" +msgstr "" + +#: ../Doc/library/select.rst:616 +msgid "link is up" +msgstr "" + +#: ../Doc/library/select.rst:618 +msgid ":const:`KQ_NOTE_LINKDOWN`" +msgstr "" + +#: ../Doc/library/select.rst:618 +msgid "link is down" +msgstr "" + +#: ../Doc/library/select.rst:620 +msgid ":const:`KQ_NOTE_LINKINV`" +msgstr "" + +#: ../Doc/library/select.rst:620 +msgid "link state is invalid" +msgstr "" + +#: ../Doc/library/select.rst:626 +msgid "Filter specific data." +msgstr "" + +#: ../Doc/library/select.rst:631 +msgid "User defined value." +msgstr "" + +#: ../Doc/library/selectors.rst:2 +msgid ":mod:`selectors` -- High-level I/O multiplexing" +msgstr "" + +#: ../Doc/library/selectors.rst:9 +msgid "**Source code:** :source:`Lib/selectors.py`" +msgstr "" + +#: ../Doc/library/selectors.rst:16 +msgid "" +"This module allows high-level and efficient I/O multiplexing, built upon " +"the :mod:`select` module primitives. Users are encouraged to use this module " +"instead, unless they want precise control over the OS-level primitives used." +msgstr "" + +#: ../Doc/library/selectors.rst:20 +msgid "" +"It defines a :class:`BaseSelector` abstract base class, along with several " +"concrete implementations (:class:`KqueueSelector`, :class:" +"`EpollSelector`...), that can be used to wait for I/O readiness notification " +"on multiple file objects. In the following, \"file object\" refers to any " +"object with a :meth:`fileno()` method, or a raw file descriptor. See :term:" +"`file object`." +msgstr "" + +#: ../Doc/library/selectors.rst:26 +msgid "" +":class:`DefaultSelector` is an alias to the most efficient implementation " +"available on the current platform: this should be the default choice for " +"most users." +msgstr "" + +#: ../Doc/library/selectors.rst:31 +msgid "" +"The type of file objects supported depends on the platform: on Windows, " +"sockets are supported, but not pipes, whereas on Unix, both are supported " +"(some other types may be supported as well, such as fifos or special file " +"devices)." +msgstr "" + +#: ../Doc/library/selectors.rst:38 +msgid ":mod:`select`" +msgstr "" + +#: ../Doc/library/selectors.rst:39 +msgid "Low-level I/O multiplexing module." +msgstr "" + +#: ../Doc/library/selectors.rst:43 ../Doc/library/struct.rst:391 +msgid "Classes" +msgstr "" + +#: ../Doc/library/selectors.rst:45 +msgid "Classes hierarchy::" +msgstr "" + +#: ../Doc/library/selectors.rst:55 +msgid "" +"In the following, *events* is a bitwise mask indicating which I/O events " +"should be waited for on a given file object. It can be a combination of the " +"modules constants below:" +msgstr "" + +#: ../Doc/library/selectors.rst:62 +msgid ":const:`EVENT_READ`" +msgstr "" + +#: ../Doc/library/selectors.rst:64 +msgid ":const:`EVENT_WRITE`" +msgstr "" + +#: ../Doc/library/selectors.rst:70 +msgid "" +"A :class:`SelectorKey` is a :class:`~collections.namedtuple` used to " +"associate a file object to its underlying file decriptor, selected event " +"mask and attached data. It is returned by several :class:`BaseSelector` " +"methods." +msgstr "" + +#: ../Doc/library/selectors.rst:77 +msgid "File object registered." +msgstr "" + +#: ../Doc/library/selectors.rst:81 +msgid "Underlying file descriptor." +msgstr "" + +#: ../Doc/library/selectors.rst:85 +msgid "Events that must be waited for on this file object." +msgstr "" + +#: ../Doc/library/selectors.rst:89 +msgid "" +"Optional opaque data associated to this file object: for example, this could " +"be used to store a per-client session ID." +msgstr "" + +#: ../Doc/library/selectors.rst:95 +msgid "" +"A :class:`BaseSelector` is used to wait for I/O event readiness on multiple " +"file objects. It supports file stream registration, unregistration, and a " +"method to wait for I/O events on those streams, with an optional timeout. " +"It's an abstract base class, so cannot be instantiated. Use :class:" +"`DefaultSelector` instead, or one of :class:`SelectSelector`, :class:" +"`KqueueSelector` etc. if you want to specifically use an implementation, and " +"your platform supports it. :class:`BaseSelector` and its concrete " +"implementations support the :term:`context manager` protocol." +msgstr "" + +#: ../Doc/library/selectors.rst:107 +msgid "Register a file object for selection, monitoring it for I/O events." +msgstr "" + +#: ../Doc/library/selectors.rst:109 +msgid "" +"*fileobj* is the file object to monitor. It may either be an integer file " +"descriptor or an object with a ``fileno()`` method. *events* is a bitwise " +"mask of events to monitor. *data* is an opaque object." +msgstr "" + +#: ../Doc/library/selectors.rst:114 +msgid "" +"This returns a new :class:`SelectorKey` instance, or raises a :exc:" +"`ValueError` in case of invalid event mask or file descriptor, or :exc:" +"`KeyError` if the file object is already registered." +msgstr "" + +#: ../Doc/library/selectors.rst:120 +msgid "" +"Unregister a file object from selection, removing it from monitoring. A file " +"object shall be unregistered prior to being closed." +msgstr "" + +#: ../Doc/library/selectors.rst:123 +msgid "*fileobj* must be a file object previously registered." +msgstr "" + +#: ../Doc/library/selectors.rst:125 +msgid "" +"This returns the associated :class:`SelectorKey` instance, or raises a :exc:" +"`KeyError` if *fileobj* is not registered. It will raise :exc:`ValueError` " +"if *fileobj* is invalid (e.g. it has no ``fileno()`` method or its " +"``fileno()`` method has an invalid return value)." +msgstr "" + +#: ../Doc/library/selectors.rst:132 +msgid "Change a registered file object's monitored events or attached data." +msgstr "" + +#: ../Doc/library/selectors.rst:134 +msgid "" +"This is equivalent to :meth:`BaseSelector.unregister(fileobj)` followed by :" +"meth:`BaseSelector.register(fileobj, events, data)`, except that it can be " +"implemented more efficiently." +msgstr "" + +#: ../Doc/library/selectors.rst:138 +msgid "" +"This returns a new :class:`SelectorKey` instance, or raises a :exc:" +"`ValueError` in case of invalid event mask or file descriptor, or :exc:" +"`KeyError` if the file object is not registered." +msgstr "" + +#: ../Doc/library/selectors.rst:144 +msgid "" +"Wait until some registered file objects become ready, or the timeout expires." +msgstr "" + +#: ../Doc/library/selectors.rst:147 +msgid "" +"If ``timeout > 0``, this specifies the maximum wait time, in seconds. If " +"``timeout <= 0``, the call won't block, and will report the currently ready " +"file objects. If *timeout* is ``None``, the call will block until a " +"monitored file object becomes ready." +msgstr "" + +#: ../Doc/library/selectors.rst:153 +msgid "" +"This returns a list of ``(key, events)`` tuples, one for each ready file " +"object." +msgstr "" + +#: ../Doc/library/selectors.rst:156 +msgid "" +"*key* is the :class:`SelectorKey` instance corresponding to a ready file " +"object. *events* is a bitmask of events ready on this file object." +msgstr "" + +#: ../Doc/library/selectors.rst:161 +msgid "" +"This method can return before any file object becomes ready or the timeout " +"has elapsed if the current process receives a signal: in this case, an empty " +"list will be returned." +msgstr "" + +#: ../Doc/library/selectors.rst:165 +msgid "" +"The selector is now retried with a recomputed timeout when interrupted by a " +"signal if the signal handler did not raise an exception (see :pep:`475` for " +"the rationale), instead of returning an empty list of events before the " +"timeout." +msgstr "" + +#: ../Doc/library/selectors.rst:173 +msgid "Close the selector." +msgstr "" + +#: ../Doc/library/selectors.rst:175 +msgid "" +"This must be called to make sure that any underlying resource is freed. The " +"selector shall not be used once it has been closed." +msgstr "" + +#: ../Doc/library/selectors.rst:180 +msgid "Return the key associated with a registered file object." +msgstr "" + +#: ../Doc/library/selectors.rst:182 +msgid "" +"This returns the :class:`SelectorKey` instance associated to this file " +"object, or raises :exc:`KeyError` if the file object is not registered." +msgstr "" + +#: ../Doc/library/selectors.rst:187 +msgid "Return a mapping of file objects to selector keys." +msgstr "" + +#: ../Doc/library/selectors.rst:189 +msgid "" +"This returns a :class:`~collections.abc.Mapping` instance mapping registered " +"file objects to their associated :class:`SelectorKey` instance." +msgstr "" + +#: ../Doc/library/selectors.rst:196 +msgid "" +"The default selector class, using the most efficient implementation " +"available on the current platform. This should be the default choice for " +"most users." +msgstr "" + +#: ../Doc/library/selectors.rst:203 +msgid ":func:`select.select`-based selector." +msgstr "" + +#: ../Doc/library/selectors.rst:208 +msgid ":func:`select.poll`-based selector." +msgstr "" + +#: ../Doc/library/selectors.rst:213 +msgid ":func:`select.epoll`-based selector." +msgstr "" + +#: ../Doc/library/selectors.rst:217 +msgid "" +"This returns the file descriptor used by the underlying :func:`select.epoll` " +"object." +msgstr "" + +#: ../Doc/library/selectors.rst:222 +msgid ":func:`select.devpoll`-based selector." +msgstr "" + +#: ../Doc/library/selectors.rst:226 +msgid "" +"This returns the file descriptor used by the underlying :func:`select." +"devpoll` object." +msgstr "" + +#: ../Doc/library/selectors.rst:233 +msgid ":func:`select.kqueue`-based selector." +msgstr "" + +#: ../Doc/library/selectors.rst:237 +msgid "" +"This returns the file descriptor used by the underlying :func:`select." +"kqueue` object." +msgstr "" + +#: ../Doc/library/selectors.rst:244 +msgid "Here is a simple echo server implementation::" +msgstr "" + +#: ../Doc/library/shelve.rst:2 +msgid ":mod:`shelve` --- Python object persistence" +msgstr "" + +#: ../Doc/library/shelve.rst:7 +msgid "**Source code:** :source:`Lib/shelve.py`" +msgstr "" + +#: ../Doc/library/shelve.rst:13 +msgid "" +"A \"shelf\" is a persistent, dictionary-like object. The difference with " +"\"dbm\" databases is that the values (not the keys!) in a shelf can be " +"essentially arbitrary Python objects --- anything that the :mod:`pickle` " +"module can handle. This includes most class instances, recursive data types, " +"and objects containing lots of shared sub-objects. The keys are ordinary " +"strings." +msgstr "" + +#: ../Doc/library/shelve.rst:22 +msgid "" +"Open a persistent dictionary. The filename specified is the base filename " +"for the underlying database. As a side-effect, an extension may be added to " +"the filename and more than one file may be created. By default, the " +"underlying database file is opened for reading and writing. The optional " +"*flag* parameter has the same interpretation as the *flag* parameter of :" +"func:`dbm.open`." +msgstr "" + +#: ../Doc/library/shelve.rst:28 +msgid "" +"By default, version 3 pickles are used to serialize values. The version of " +"the pickle protocol can be specified with the *protocol* parameter." +msgstr "" + +#: ../Doc/library/shelve.rst:31 +msgid "" +"Because of Python semantics, a shelf cannot know when a mutable persistent-" +"dictionary entry is modified. By default modified objects are written " +"*only* when assigned to the shelf (see :ref:`shelve-example`). If the " +"optional *writeback* parameter is set to *True*, all entries accessed are " +"also cached in memory, and written back on :meth:`~Shelf.sync` and :meth:" +"`~Shelf.close`; this can make it handier to mutate mutable entries in the " +"persistent dictionary, but, if many entries are accessed, it can consume " +"vast amounts of memory for the cache, and it can make the close operation " +"very slow since all accessed entries are written back (there is no way to " +"determine which accessed entries are mutable, nor which ones were actually " +"mutated)." +msgstr "" + +#: ../Doc/library/shelve.rst:45 +msgid "" +"Do not rely on the shelf being closed automatically; always call :meth:" +"`~Shelf.close` explicitly when you don't need it any more, or use :func:" +"`shelve.open` as a context manager::" +msgstr "" + +#: ../Doc/library/shelve.rst:54 +msgid "" +"Because the :mod:`shelve` module is backed by :mod:`pickle`, it is insecure " +"to load a shelf from an untrusted source. Like with pickle, loading a shelf " +"can execute arbitrary code." +msgstr "" + +#: ../Doc/library/shelve.rst:58 +msgid "" +"Shelf objects support all methods supported by dictionaries. This eases the " +"transition from dictionary based scripts to those requiring persistent " +"storage." +msgstr "" + +#: ../Doc/library/shelve.rst:61 +msgid "Two additional methods are supported:" +msgstr "" + +#: ../Doc/library/shelve.rst:65 +msgid "" +"Write back all entries in the cache if the shelf was opened with *writeback* " +"set to :const:`True`. Also empty the cache and synchronize the persistent " +"dictionary on disk, if feasible. This is called automatically when the " +"shelf is closed with :meth:`close`." +msgstr "" + +#: ../Doc/library/shelve.rst:72 +msgid "" +"Synchronize and close the persistent *dict* object. Operations on a closed " +"shelf will fail with a :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/shelve.rst:78 +msgid "" +"`Persistent dictionary recipe `_ with widely supported storage formats and having the speed of native " +"dictionaries." +msgstr "" + +#: ../Doc/library/shelve.rst:84 +msgid "Restrictions" +msgstr "" + +#: ../Doc/library/shelve.rst:90 +msgid "" +"The choice of which database package will be used (such as :mod:`dbm.ndbm` " +"or :mod:`dbm.gnu`) depends on which interface is available. Therefore it is " +"not safe to open the database directly using :mod:`dbm`. The database is " +"also (unfortunately) subject to the limitations of :mod:`dbm`, if it is used " +"--- this means that (the pickled representation of) the objects stored in " +"the database should be fairly small, and in rare cases key collisions may " +"cause the database to refuse updates." +msgstr "" + +#: ../Doc/library/shelve.rst:98 +msgid "" +"The :mod:`shelve` module does not support *concurrent* read/write access to " +"shelved objects. (Multiple simultaneous read accesses are safe.) When a " +"program has a shelf open for writing, no other program should have it open " +"for reading or writing. Unix file locking can be used to solve this, but " +"this differs across Unix versions and requires knowledge about the database " +"implementation used." +msgstr "" + +#: ../Doc/library/shelve.rst:108 +msgid "" +"A subclass of :class:`collections.abc.MutableMapping` which stores pickled " +"values in the *dict* object." +msgstr "" + +#: ../Doc/library/shelve.rst:111 +msgid "" +"By default, version 3 pickles are used to serialize values. The version of " +"the pickle protocol can be specified with the *protocol* parameter. See the :" +"mod:`pickle` documentation for a discussion of the pickle protocols." +msgstr "" + +#: ../Doc/library/shelve.rst:115 +msgid "" +"If the *writeback* parameter is ``True``, the object will hold a cache of " +"all entries accessed and write them back to the *dict* at sync and close " +"times. This allows natural operations on mutable entries, but can consume " +"much more memory and make sync and close take a long time." +msgstr "" + +#: ../Doc/library/shelve.rst:120 +msgid "" +"The *keyencoding* parameter is the encoding used to encode keys before they " +"are used with the underlying dict." +msgstr "" + +#: ../Doc/library/shelve.rst:123 +msgid "" +"A :class:`Shelf` object can also be used as a context manager, in which case " +"it will be automatically closed when the :keyword:`with` block ends." +msgstr "" + +#: ../Doc/library/shelve.rst:126 +msgid "" +"Added the *keyencoding* parameter; previously, keys were always encoded in " +"UTF-8." +msgstr "" + +#: ../Doc/library/shelve.rst:130 ../Doc/library/subprocess.rst:520 +msgid "Added context manager support." +msgstr "" + +#: ../Doc/library/shelve.rst:136 +msgid "" +"A subclass of :class:`Shelf` which exposes :meth:`first`, :meth:`!next`, :" +"meth:`previous`, :meth:`last` and :meth:`set_location` which are available " +"in the third-party :mod:`bsddb` module from `pybsddb `_ but not in other database modules. The *dict* " +"object passed to the constructor must support those methods. This is " +"generally accomplished by calling one of :func:`bsddb.hashopen`, :func:" +"`bsddb.btopen` or :func:`bsddb.rnopen`. The optional *protocol*, " +"*writeback*, and *keyencoding* parameters have the same interpretation as " +"for the :class:`Shelf` class." +msgstr "" + +#: ../Doc/library/shelve.rst:149 +msgid "" +"A subclass of :class:`Shelf` which accepts a *filename* instead of a dict-" +"like object. The underlying file will be opened using :func:`dbm.open`. By " +"default, the file will be created and opened for both read and write. The " +"optional *flag* parameter has the same interpretation as for the :func:`." +"open` function. The optional *protocol* and *writeback* parameters have the " +"same interpretation as for the :class:`Shelf` class." +msgstr "" + +#: ../Doc/library/shelve.rst:162 +msgid "" +"To summarize the interface (``key`` is a string, ``data`` is an arbitrary " +"object)::" +msgstr "" + +#: ../Doc/library/shelve.rst:199 +msgid "Module :mod:`dbm`" +msgstr "" + +#: ../Doc/library/shelve.rst:199 +msgid "Generic interface to ``dbm``-style databases." +msgstr "" + +#: ../Doc/library/shelve.rst:202 +msgid "Object serialization used by :mod:`shelve`." +msgstr "" + +#: ../Doc/library/shlex.rst:2 +msgid ":mod:`shlex` --- Simple lexical analysis" +msgstr "" + +#: ../Doc/library/shlex.rst:12 +msgid "**Source code:** :source:`Lib/shlex.py`" +msgstr "" + +#: ../Doc/library/shlex.rst:16 +msgid "" +"The :class:`~shlex.shlex` class makes it easy to write lexical analyzers for " +"simple syntaxes resembling that of the Unix shell. This will often be " +"useful for writing minilanguages, (for example, in run control files for " +"Python applications) or for parsing quoted strings." +msgstr "" + +#: ../Doc/library/shlex.rst:21 +msgid "The :mod:`shlex` module defines the following functions:" +msgstr "" + +#: ../Doc/library/shlex.rst:26 +msgid "" +"Split the string *s* using shell-like syntax. If *comments* is :const:" +"`False` (the default), the parsing of comments in the given string will be " +"disabled (setting the :attr:`~shlex.commenters` attribute of the :class:" +"`~shlex.shlex` instance to the empty string). This function operates in " +"POSIX mode by default, but uses non-POSIX mode if the *posix* argument is " +"false." +msgstr "" + +#: ../Doc/library/shlex.rst:35 +msgid "" +"Since the :func:`split` function instantiates a :class:`~shlex.shlex` " +"instance, passing ``None`` for *s* will read the string to split from " +"standard input." +msgstr "" + +#: ../Doc/library/shlex.rst:42 +msgid "" +"Return a shell-escaped version of the string *s*. The returned value is a " +"string that can safely be used as one token in a shell command line, for " +"cases where you cannot use a list." +msgstr "" + +#: ../Doc/library/shlex.rst:46 +msgid "This idiom would be unsafe::" +msgstr "" + +#: ../Doc/library/shlex.rst:53 +msgid ":func:`quote` lets you plug the security hole::" +msgstr "" + +#: ../Doc/library/shlex.rst:62 +msgid "The quoting is compatible with UNIX shells and with :func:`split`:" +msgstr "" + +#: ../Doc/library/shlex.rst:73 +msgid "The :mod:`shlex` module defines the following class:" +msgstr "" + +#: ../Doc/library/shlex.rst:78 +msgid "" +"A :class:`~shlex.shlex` instance or subclass instance is a lexical analyzer " +"object. The initialization argument, if present, specifies where to read " +"characters from. It must be a file-/stream-like object with :meth:`~io." +"TextIOBase.read` and :meth:`~io.TextIOBase.readline` methods, or a string. " +"If no argument is given, input will be taken from ``sys.stdin``. The second " +"optional argument is a filename string, which sets the initial value of the :" +"attr:`~shlex.infile` attribute. If the *instream* argument is omitted or " +"equal to ``sys.stdin``, this second argument defaults to \"stdin\". The " +"*posix* argument defines the operational mode: when *posix* is not true " +"(default), the :class:`~shlex.shlex` instance will operate in compatibility " +"mode. When operating in POSIX mode, :class:`~shlex.shlex` will try to be as " +"close as possible to the POSIX shell parsing rules. The *punctuation_chars* " +"argument provides a way to make the behaviour even closer to how real shells " +"parse. This can take a number of values: the default value, ``False``, " +"preserves the behaviour seen under Python 3.5 and earlier. If set to " +"``True``, then parsing of the characters ``();<>|&`` is changed: any run of " +"these characters (considered punctuation characters) is returned as a single " +"token. If set to a non-empty string of characters, those characters will be " +"used as the punctuation characters. Any characters in the :attr:`wordchars` " +"attribute that appear in *punctuation_chars* will be removed from :attr:" +"`wordchars`. See :ref:`improved-shell-compatibility` for more information." +msgstr "" + +#: ../Doc/library/shlex.rst:101 +msgid "The *punctuation_chars* parameter was added." +msgstr "" + +#: ../Doc/library/shlex.rst:106 +msgid "Module :mod:`configparser`" +msgstr "" + +#: ../Doc/library/shlex.rst:107 +msgid "" +"Parser for configuration files similar to the Windows :file:`.ini` files." +msgstr "" + +#: ../Doc/library/shlex.rst:113 +msgid "shlex Objects" +msgstr "" + +#: ../Doc/library/shlex.rst:115 +msgid "A :class:`~shlex.shlex` instance has the following methods:" +msgstr "" + +#: ../Doc/library/shlex.rst:120 +msgid "" +"Return a token. If tokens have been stacked using :meth:`push_token`, pop a " +"token off the stack. Otherwise, read one from the input stream. If reading " +"encounters an immediate end-of-file, :attr:`eof` is returned (the empty " +"string (``''``) in non-POSIX mode, and ``None`` in POSIX mode)." +msgstr "" + +#: ../Doc/library/shlex.rst:128 +msgid "Push the argument onto the token stack." +msgstr "" + +#: ../Doc/library/shlex.rst:133 +msgid "" +"Read a raw token. Ignore the pushback stack, and do not interpret source " +"requests. (This is not ordinarily a useful entry point, and is documented " +"here only for the sake of completeness.)" +msgstr "" + +#: ../Doc/library/shlex.rst:140 +msgid "" +"When :class:`~shlex.shlex` detects a source request (see :attr:`source` " +"below) this method is given the following token as argument, and expected to " +"return a tuple consisting of a filename and an open file-like object." +msgstr "" + +#: ../Doc/library/shlex.rst:144 +msgid "" +"Normally, this method first strips any quotes off the argument. If the " +"result is an absolute pathname, or there was no previous source request in " +"effect, or the previous source was a stream (such as ``sys.stdin``), the " +"result is left alone. Otherwise, if the result is a relative pathname, the " +"directory part of the name of the file immediately before it on the source " +"inclusion stack is prepended (this behavior is like the way the C " +"preprocessor handles ``#include \"file.h\"``)." +msgstr "" + +#: ../Doc/library/shlex.rst:152 +msgid "" +"The result of the manipulations is treated as a filename, and returned as " +"the first component of the tuple, with :func:`open` called on it to yield " +"the second component. (Note: this is the reverse of the order of arguments " +"in instance initialization!)" +msgstr "" + +#: ../Doc/library/shlex.rst:157 +msgid "" +"This hook is exposed so that you can use it to implement directory search " +"paths, addition of file extensions, and other namespace hacks. There is no " +"corresponding 'close' hook, but a shlex instance will call the :meth:`~io." +"IOBase.close` method of the sourced input stream when it returns EOF." +msgstr "" + +#: ../Doc/library/shlex.rst:163 +msgid "" +"For more explicit control of source stacking, use the :meth:`push_source` " +"and :meth:`pop_source` methods." +msgstr "" + +#: ../Doc/library/shlex.rst:169 +msgid "" +"Push an input source stream onto the input stack. If the filename argument " +"is specified it will later be available for use in error messages. This is " +"the same method used internally by the :meth:`sourcehook` method." +msgstr "" + +#: ../Doc/library/shlex.rst:176 +msgid "" +"Pop the last-pushed input source from the input stack. This is the same " +"method used internally when the lexer reaches EOF on a stacked input stream." +msgstr "" + +#: ../Doc/library/shlex.rst:182 +msgid "" +"This method generates an error message leader in the format of a Unix C " +"compiler error label; the format is ``'\"%s\", line %d: '``, where the ``" +"%s`` is replaced with the name of the current source file and the ``%d`` " +"with the current input line number (the optional arguments can be used to " +"override these)." +msgstr "" + +#: ../Doc/library/shlex.rst:187 +msgid "" +"This convenience is provided to encourage :mod:`shlex` users to generate " +"error messages in the standard, parseable format understood by Emacs and " +"other Unix tools." +msgstr "" + +#: ../Doc/library/shlex.rst:191 +msgid "" +"Instances of :class:`~shlex.shlex` subclasses have some public instance " +"variables which either control lexical analysis or can be used for debugging:" +msgstr "" + +#: ../Doc/library/shlex.rst:197 +msgid "" +"The string of characters that are recognized as comment beginners. All " +"characters from the comment beginner to end of line are ignored. Includes " +"just ``'#'`` by default." +msgstr "" + +#: ../Doc/library/shlex.rst:204 +msgid "" +"The string of characters that will accumulate into multi-character tokens. " +"By default, includes all ASCII alphanumerics and underscore. In POSIX mode, " +"the accented characters in the Latin-1 set are also included. If :attr:" +"`punctuation_chars` is not empty, the characters ``~-./*?=``, which can " +"appear in filename specifications and command line parameters, will also be " +"included in this attribute, and any characters which appear in " +"``punctuation_chars`` will be removed from ``wordchars`` if they are present " +"there." +msgstr "" + +#: ../Doc/library/shlex.rst:216 +msgid "" +"Characters that will be considered whitespace and skipped. Whitespace " +"bounds tokens. By default, includes space, tab, linefeed and carriage-" +"return." +msgstr "" + +#: ../Doc/library/shlex.rst:222 +msgid "" +"Characters that will be considered as escape. This will be only used in " +"POSIX mode, and includes just ``'\\'`` by default." +msgstr "" + +#: ../Doc/library/shlex.rst:228 +msgid "" +"Characters that will be considered string quotes. The token accumulates " +"until the same quote is encountered again (thus, different quote types " +"protect each other as in the shell.) By default, includes ASCII single and " +"double quotes." +msgstr "" + +#: ../Doc/library/shlex.rst:235 +msgid "" +"Characters in :attr:`quotes` that will interpret escape characters defined " +"in :attr:`escape`. This is only used in POSIX mode, and includes just " +"``'\"'`` by default." +msgstr "" + +#: ../Doc/library/shlex.rst:242 +msgid "" +"If ``True``, tokens will only be split in whitespaces. This is useful, for " +"example, for parsing command lines with :class:`~shlex.shlex`, getting " +"tokens in a similar way to shell arguments. If this attribute is ``True``, :" +"attr:`punctuation_chars` will have no effect, and splitting will happen only " +"on whitespaces. When using :attr:`punctuation_chars`, which is intended to " +"provide parsing closer to that implemented by shells, it is advisable to " +"leave ``whitespace_split`` as ``False`` (the default value)." +msgstr "" + +#: ../Doc/library/shlex.rst:253 +msgid "" +"The name of the current input file, as initially set at class instantiation " +"time or stacked by later source requests. It may be useful to examine this " +"when constructing error messages." +msgstr "" + +#: ../Doc/library/shlex.rst:260 +msgid "" +"The input stream from which this :class:`~shlex.shlex` instance is reading " +"characters." +msgstr "" + +#: ../Doc/library/shlex.rst:266 +msgid "" +"This attribute is ``None`` by default. If you assign a string to it, that " +"string will be recognized as a lexical-level inclusion request similar to " +"the ``source`` keyword in various shells. That is, the immediately " +"following token will be opened as a filename and input will be taken from " +"that stream until EOF, at which point the :meth:`~io.IOBase.close` method of " +"that stream will be called and the input source will again become the " +"original input stream. Source requests may be stacked any number of levels " +"deep." +msgstr "" + +#: ../Doc/library/shlex.rst:277 +msgid "" +"If this attribute is numeric and ``1`` or more, a :class:`~shlex.shlex` " +"instance will print verbose progress output on its behavior. If you need to " +"use this, you can read the module source code to learn the details." +msgstr "" + +#: ../Doc/library/shlex.rst:284 +msgid "Source line number (count of newlines seen so far plus one)." +msgstr "" + +#: ../Doc/library/shlex.rst:289 +msgid "" +"The token buffer. It may be useful to examine this when catching exceptions." +msgstr "" + +#: ../Doc/library/shlex.rst:294 +msgid "" +"Token used to determine end of file. This will be set to the empty string " +"(``''``), in non-POSIX mode, and to ``None`` in POSIX mode." +msgstr "" + +#: ../Doc/library/shlex.rst:300 +msgid "" +"Characters that will be considered punctuation. Runs of punctuation " +"characters will be returned as a single token. However, note that no " +"semantic validity checking will be performed: for example, '>>>' could be " +"returned as a token, even though it may not be recognised as such by shells." +msgstr "" + +#: ../Doc/library/shlex.rst:311 +msgid "Parsing Rules" +msgstr "" + +#: ../Doc/library/shlex.rst:313 +msgid "" +"When operating in non-POSIX mode, :class:`~shlex.shlex` will try to obey to " +"the following rules." +msgstr "" + +#: ../Doc/library/shlex.rst:316 +msgid "" +"Quote characters are not recognized within words (``Do\"Not\"Separate`` is " +"parsed as the single word ``Do\"Not\"Separate``);" +msgstr "" + +#: ../Doc/library/shlex.rst:319 +msgid "Escape characters are not recognized;" +msgstr "" + +#: ../Doc/library/shlex.rst:321 +msgid "" +"Enclosing characters in quotes preserve the literal value of all characters " +"within the quotes;" +msgstr "" + +#: ../Doc/library/shlex.rst:324 +msgid "" +"Closing quotes separate words (``\"Do\"Separate`` is parsed as ``\"Do\"`` " +"and ``Separate``);" +msgstr "" + +#: ../Doc/library/shlex.rst:327 +msgid "" +"If :attr:`~shlex.whitespace_split` is ``False``, any character not declared " +"to be a word character, whitespace, or a quote will be returned as a single-" +"character token. If it is ``True``, :class:`~shlex.shlex` will only split " +"words in whitespaces;" +msgstr "" + +#: ../Doc/library/shlex.rst:332 +msgid "EOF is signaled with an empty string (``''``);" +msgstr "" + +#: ../Doc/library/shlex.rst:334 +msgid "It's not possible to parse empty strings, even if quoted." +msgstr "" + +#: ../Doc/library/shlex.rst:336 +msgid "" +"When operating in POSIX mode, :class:`~shlex.shlex` will try to obey to the " +"following parsing rules." +msgstr "" + +#: ../Doc/library/shlex.rst:339 +msgid "" +"Quotes are stripped out, and do not separate words (``\"Do\"Not\"Separate" +"\"`` is parsed as the single word ``DoNotSeparate``);" +msgstr "" + +#: ../Doc/library/shlex.rst:342 +msgid "" +"Non-quoted escape characters (e.g. ``'\\'``) preserve the literal value of " +"the next character that follows;" +msgstr "" + +#: ../Doc/library/shlex.rst:345 +msgid "" +"Enclosing characters in quotes which are not part of :attr:`~shlex." +"escapedquotes` (e.g. ``\"'\"``) preserve the literal value of all characters " +"within the quotes;" +msgstr "" + +#: ../Doc/library/shlex.rst:349 +msgid "" +"Enclosing characters in quotes which are part of :attr:`~shlex." +"escapedquotes` (e.g. ``'\"'``) preserves the literal value of all characters " +"within the quotes, with the exception of the characters mentioned in :attr:" +"`~shlex.escape`. The escape characters retain its special meaning only when " +"followed by the quote in use, or the escape character itself. Otherwise the " +"escape character will be considered a normal character." +msgstr "" + +#: ../Doc/library/shlex.rst:357 +msgid "EOF is signaled with a :const:`None` value;" +msgstr "" + +#: ../Doc/library/shlex.rst:359 +msgid "Quoted empty strings (``''``) are allowed." +msgstr "" + +#: ../Doc/library/shlex.rst:364 +msgid "Improved Compatibility with Shells" +msgstr "" + +#: ../Doc/library/shlex.rst:368 +msgid "" +"The :class:`shlex` class provides compatibility with the parsing performed " +"by common Unix shells like ``bash``, ``dash``, and ``sh``. To take " +"advantage of this compatibility, specify the ``punctuation_chars`` argument " +"in the constructor. This defaults to ``False``, which preserves pre-3.6 " +"behaviour. However, if it is set to ``True``, then parsing of the characters " +"``();<>|&`` is changed: any run of these characters is returned as a single " +"token. While this is short of a full parser for shells (which would be out " +"of scope for the standard library, given the multiplicity of shells out " +"there), it does allow you to perform processing of command lines more easily " +"than you could otherwise. To illustrate, you can see the difference in the " +"following snippet::" +msgstr "" + +#: ../Doc/library/shlex.rst:390 +msgid "which prints out::" +msgstr "" + +#: ../Doc/library/shlex.rst:395 +msgid "" +"Of course, tokens will be returned which are not valid for shells, and " +"you'll need to implement your own error checks on the returned tokens." +msgstr "" + +#: ../Doc/library/shlex.rst:398 +msgid "" +"Instead of passing ``True`` as the value for the punctuation_chars " +"parameter, you can pass a string with specific characters, which will be " +"used to determine which characters constitute punctuation. For example::" +msgstr "" + +#: ../Doc/library/shlex.rst:407 +msgid "" +"When ``punctuation_chars`` is specified, the :attr:`~shlex.wordchars` " +"attribute is augmented with the characters ``~-./*?=``. That is because " +"these characters can appear in file names (including wildcards) and command-" +"line arguments (e.g. ``--color=auto``). Hence::" +msgstr "" + +#: ../Doc/library/shutil.rst:2 +msgid ":mod:`shutil` --- High-level file operations" +msgstr "" + +#: ../Doc/library/shutil.rst:10 +msgid "**Source code:** :source:`Lib/shutil.py`" +msgstr "" + +#: ../Doc/library/shutil.rst:18 +msgid "" +"The :mod:`shutil` module offers a number of high-level operations on files " +"and collections of files. In particular, functions are provided which " +"support file copying and removal. For operations on individual files, see " +"also the :mod:`os` module." +msgstr "" + +#: ../Doc/library/shutil.rst:25 +msgid "" +"Even the higher-level file copying functions (:func:`shutil.copy`, :func:" +"`shutil.copy2`) cannot copy all file metadata." +msgstr "" + +#: ../Doc/library/shutil.rst:28 +msgid "" +"On POSIX platforms, this means that file owner and group are lost as well as " +"ACLs. On Mac OS, the resource fork and other metadata are not used. This " +"means that resources will be lost and file type and creator codes will not " +"be correct. On Windows, file owners, ACLs and alternate data streams are not " +"copied." +msgstr "" + +#: ../Doc/library/shutil.rst:38 +msgid "Directory and files operations" +msgstr "" + +#: ../Doc/library/shutil.rst:42 +msgid "" +"Copy the contents of the file-like object *fsrc* to the file-like object " +"*fdst*. The integer *length*, if given, is the buffer size. In particular, a " +"negative *length* value means to copy the data without looping over the " +"source data in chunks; by default the data is read in chunks to avoid " +"uncontrolled memory consumption. Note that if the current file position of " +"the *fsrc* object is not 0, only the contents from the current file position " +"to the end of the file will be copied." +msgstr "" + +#: ../Doc/library/shutil.rst:53 +msgid "" +"Copy the contents (no metadata) of the file named *src* to a file named " +"*dst* and return *dst*. *src* and *dst* are path names given as strings. " +"*dst* must be the complete target file name; look at :func:`shutil.copy` for " +"a copy that accepts a target directory path. If *src* and *dst* specify the " +"same file, :exc:`SameFileError` is raised." +msgstr "" + +#: ../Doc/library/shutil.rst:59 +msgid "" +"The destination location must be writable; otherwise, an :exc:`OSError` " +"exception will be raised. If *dst* already exists, it will be replaced. " +"Special files such as character or block devices and pipes cannot be copied " +"with this function." +msgstr "" + +#: ../Doc/library/shutil.rst:64 +msgid "" +"If *follow_symlinks* is false and *src* is a symbolic link, a new symbolic " +"link will be created instead of copying the file *src* points to." +msgstr "" + +#: ../Doc/library/shutil.rst:68 +msgid "" +":exc:`IOError` used to be raised instead of :exc:`OSError`. Added " +"*follow_symlinks* argument. Now returns *dst*." +msgstr "" + +#: ../Doc/library/shutil.rst:73 +msgid "" +"Raise :exc:`SameFileError` instead of :exc:`Error`. Since the former is a " +"subclass of the latter, this change is backward compatible." +msgstr "" + +#: ../Doc/library/shutil.rst:80 +msgid "" +"This exception is raised if source and destination in :func:`copyfile` are " +"the same file." +msgstr "" + +#: ../Doc/library/shutil.rst:88 +msgid "" +"Copy the permission bits from *src* to *dst*. The file contents, owner, and " +"group are unaffected. *src* and *dst* are path names given as strings. If " +"*follow_symlinks* is false, and both *src* and *dst* are symbolic links, :" +"func:`copymode` will attempt to modify the mode of *dst* itself (rather than " +"the file it points to). This functionality is not available on every " +"platform; please see :func:`copystat` for more information. If :func:" +"`copymode` cannot modify symbolic links on the local platform, and it is " +"asked to do so, it will do nothing and return." +msgstr "" + +#: ../Doc/library/shutil.rst:97 +msgid "Added *follow_symlinks* argument." +msgstr "" + +#: ../Doc/library/shutil.rst:102 +msgid "" +"Copy the permission bits, last access time, last modification time, and " +"flags from *src* to *dst*. On Linux, :func:`copystat` also copies the " +"\"extended attributes\" where possible. The file contents, owner, and group " +"are unaffected. *src* and *dst* are path names given as strings." +msgstr "" + +#: ../Doc/library/shutil.rst:107 +msgid "" +"If *follow_symlinks* is false, and *src* and *dst* both refer to symbolic " +"links, :func:`copystat` will operate on the symbolic links themselves rather " +"than the files the symbolic links refer to--reading the information from the " +"*src* symbolic link, and writing the information to the *dst* symbolic link." +msgstr "" + +#: ../Doc/library/shutil.rst:116 +msgid "" +"Not all platforms provide the ability to examine and modify symbolic links. " +"Python itself can tell you what functionality is locally available." +msgstr "" + +#: ../Doc/library/shutil.rst:120 +msgid "" +"If ``os.chmod in os.supports_follow_symlinks`` is ``True``, :func:`copystat` " +"can modify the permission bits of a symbolic link." +msgstr "" + +#: ../Doc/library/shutil.rst:124 +msgid "" +"If ``os.utime in os.supports_follow_symlinks`` is ``True``, :func:`copystat` " +"can modify the last access and modification times of a symbolic link." +msgstr "" + +#: ../Doc/library/shutil.rst:128 +msgid "" +"If ``os.chflags in os.supports_follow_symlinks`` is ``True``, :func:" +"`copystat` can modify the flags of a symbolic link. (``os.chflags`` is not " +"available on all platforms.)" +msgstr "" + +#: ../Doc/library/shutil.rst:133 +msgid "" +"On platforms where some or all of this functionality is unavailable, when " +"asked to modify a symbolic link, :func:`copystat` will copy everything it " +"can. :func:`copystat` never returns failure." +msgstr "" + +#: ../Doc/library/shutil.rst:138 +msgid "Please see :data:`os.supports_follow_symlinks` for more information." +msgstr "" + +#: ../Doc/library/shutil.rst:141 +msgid "" +"Added *follow_symlinks* argument and support for Linux extended attributes." +msgstr "" + +#: ../Doc/library/shutil.rst:146 +msgid "" +"Copies the file *src* to the file or directory *dst*. *src* and *dst* " +"should be strings. If *dst* specifies a directory, the file will be copied " +"into *dst* using the base filename from *src*. Returns the path to the " +"newly created file." +msgstr "" + +#: ../Doc/library/shutil.rst:151 +msgid "" +"If *follow_symlinks* is false, and *src* is a symbolic link, *dst* will be " +"created as a symbolic link. If *follow_symlinks* is true and *src* is a " +"symbolic link, *dst* will be a copy of the file *src* refers to." +msgstr "" + +#: ../Doc/library/shutil.rst:156 +msgid "" +":func:`copy` copies the file data and the file's permission mode (see :func:" +"`os.chmod`). Other metadata, like the file's creation and modification " +"times, is not preserved. To preserve all file metadata from the original, " +"use :func:`~shutil.copy2` instead." +msgstr "" + +#: ../Doc/library/shutil.rst:162 +msgid "" +"Added *follow_symlinks* argument. Now returns path to the newly created file." +msgstr "" + +#: ../Doc/library/shutil.rst:168 +msgid "" +"Identical to :func:`~shutil.copy` except that :func:`copy2` also attempts to " +"preserve all file metadata." +msgstr "" + +#: ../Doc/library/shutil.rst:171 +msgid "" +"When *follow_symlinks* is false, and *src* is a symbolic link, :func:`copy2` " +"attempts to copy all metadata from the *src* symbolic link to the newly-" +"created *dst* symbolic link. However, this functionality is not available on " +"all platforms. On platforms where some or all of this functionality is " +"unavailable, :func:`copy2` will preserve all the metadata it can; :func:" +"`copy2` never returns failure." +msgstr "" + +#: ../Doc/library/shutil.rst:179 +msgid "" +":func:`copy2` uses :func:`copystat` to copy the file metadata. Please see :" +"func:`copystat` for more information about platform support for modifying " +"symbolic link metadata." +msgstr "" + +#: ../Doc/library/shutil.rst:183 +msgid "" +"Added *follow_symlinks* argument, try to copy extended file system " +"attributes too (currently Linux only). Now returns path to the newly created " +"file." +msgstr "" + +#: ../Doc/library/shutil.rst:190 +msgid "" +"This factory function creates a function that can be used as a callable for :" +"func:`copytree`\\'s *ignore* argument, ignoring files and directories that " +"match one of the glob-style *patterns* provided. See the example below." +msgstr "" + +#: ../Doc/library/shutil.rst:198 +msgid "" +"Recursively copy an entire directory tree rooted at *src*, returning the " +"destination directory. The destination directory, named by *dst*, must not " +"already exist; it will be created as well as missing parent directories. " +"Permissions and times of directories are copied with :func:`copystat`, " +"individual files are copied using :func:`shutil.copy2`." +msgstr "" + +#: ../Doc/library/shutil.rst:205 +msgid "" +"If *symlinks* is true, symbolic links in the source tree are represented as " +"symbolic links in the new tree and the metadata of the original links will " +"be copied as far as the platform allows; if false or omitted, the contents " +"and metadata of the linked files are copied to the new tree." +msgstr "" + +#: ../Doc/library/shutil.rst:210 +msgid "" +"When *symlinks* is false, if the file pointed by the symlink doesn't exist, " +"an exception will be added in the list of errors raised in an :exc:`Error` " +"exception at the end of the copy process. You can set the optional " +"*ignore_dangling_symlinks* flag to true if you want to silence this " +"exception. Notice that this option has no effect on platforms that don't " +"support :func:`os.symlink`." +msgstr "" + +#: ../Doc/library/shutil.rst:217 +msgid "" +"If *ignore* is given, it must be a callable that will receive as its " +"arguments the directory being visited by :func:`copytree`, and a list of its " +"contents, as returned by :func:`os.listdir`. Since :func:`copytree` is " +"called recursively, the *ignore* callable will be called once for each " +"directory that is copied. The callable must return a sequence of directory " +"and file names relative to the current directory (i.e. a subset of the items " +"in its second argument); these names will then be ignored in the copy " +"process. :func:`ignore_patterns` can be used to create such a callable that " +"ignores names based on glob-style patterns." +msgstr "" + +#: ../Doc/library/shutil.rst:227 +msgid "" +"If exception(s) occur, an :exc:`Error` is raised with a list of reasons." +msgstr "" + +#: ../Doc/library/shutil.rst:229 +msgid "" +"If *copy_function* is given, it must be a callable that will be used to copy " +"each file. It will be called with the source path and the destination path " +"as arguments. By default, :func:`shutil.copy2` is used, but any function " +"that supports the same signature (like :func:`shutil.copy`) can be used." +msgstr "" + +#: ../Doc/library/shutil.rst:234 +msgid "Copy metadata when *symlinks* is false. Now returns *dst*." +msgstr "" + +#: ../Doc/library/shutil.rst:238 +msgid "" +"Added the *copy_function* argument to be able to provide a custom copy " +"function. Added the *ignore_dangling_symlinks* argument to silent dangling " +"symlinks errors when *symlinks* is false." +msgstr "" + +#: ../Doc/library/shutil.rst:249 +msgid "" +"Delete an entire directory tree; *path* must point to a directory (but not a " +"symbolic link to a directory). If *ignore_errors* is true, errors resulting " +"from failed removals will be ignored; if false or omitted, such errors are " +"handled by calling a handler specified by *onerror* or, if that is omitted, " +"they raise an exception." +msgstr "" + +#: ../Doc/library/shutil.rst:257 +msgid "" +"On platforms that support the necessary fd-based functions a symlink attack " +"resistant version of :func:`rmtree` is used by default. On other platforms, " +"the :func:`rmtree` implementation is susceptible to a symlink attack: given " +"proper timing and circumstances, attackers can manipulate symlinks on the " +"filesystem to delete files they wouldn't be able to access otherwise. " +"Applications can use the :data:`rmtree.avoids_symlink_attacks` function " +"attribute to determine which case applies." +msgstr "" + +#: ../Doc/library/shutil.rst:265 +msgid "" +"If *onerror* is provided, it must be a callable that accepts three " +"parameters: *function*, *path*, and *excinfo*." +msgstr "" + +#: ../Doc/library/shutil.rst:268 +msgid "" +"The first parameter, *function*, is the function which raised the exception; " +"it depends on the platform and implementation. The second parameter, " +"*path*, will be the path name passed to *function*. The third parameter, " +"*excinfo*, will be the exception information returned by :func:`sys." +"exc_info`. Exceptions raised by *onerror* will not be caught." +msgstr "" + +#: ../Doc/library/shutil.rst:274 +msgid "" +"Added a symlink attack resistant version that is used automatically if " +"platform supports fd-based functions." +msgstr "" + +#: ../Doc/library/shutil.rst:280 +msgid "" +"Indicates whether the current platform and implementation provides a symlink " +"attack resistant version of :func:`rmtree`. Currently this is only true for " +"platforms supporting fd-based directory access functions." +msgstr "" + +#: ../Doc/library/shutil.rst:289 +msgid "" +"Recursively move a file or directory (*src*) to another location (*dst*) and " +"return the destination." +msgstr "" + +#: ../Doc/library/shutil.rst:292 +msgid "" +"If the destination is an existing directory, then *src* is moved inside that " +"directory. If the destination already exists but is not a directory, it may " +"be overwritten depending on :func:`os.rename` semantics." +msgstr "" + +#: ../Doc/library/shutil.rst:296 +msgid "" +"If the destination is on the current filesystem, then :func:`os.rename` is " +"used. Otherwise, *src* is copied to *dst* using *copy_function* and then " +"removed. In case of symlinks, a new symlink pointing to the target of *src* " +"will be created in or as *dst* and *src* will be removed." +msgstr "" + +#: ../Doc/library/shutil.rst:301 +msgid "" +"If *copy_function* is given, it must be a callable that takes two arguments " +"*src* and *dst*, and will be used to copy *src* to *dest* if :func:`os." +"rename` cannot be used. If the source is a directory, :func:`copytree` is " +"called, passing it the :func:`copy_function`. The default *copy_function* " +"is :func:`copy2`. Using :func:`copy` as the *copy_function* allows the move " +"to succeed when it is not possible to also copy the metadata, at the expense " +"of not copying any of the metadata." +msgstr "" + +#: ../Doc/library/shutil.rst:309 +msgid "" +"Added explicit symlink handling for foreign filesystems, thus adapting it to " +"the behavior of GNU's :program:`mv`. Now returns *dst*." +msgstr "" + +#: ../Doc/library/shutil.rst:314 +msgid "Added the *copy_function* keyword argument." +msgstr "" + +#: ../Doc/library/shutil.rst:319 +msgid "" +"Return disk usage statistics about the given path as a :term:`named tuple` " +"with the attributes *total*, *used* and *free*, which are the amount of " +"total, used and free space, in bytes." +msgstr "" + +#: ../Doc/library/shutil.rst:329 +msgid "Change owner *user* and/or *group* of the given *path*." +msgstr "" + +#: ../Doc/library/shutil.rst:331 +msgid "" +"*user* can be a system user name or a uid; the same applies to *group*. At " +"least one argument is required." +msgstr "" + +#: ../Doc/library/shutil.rst:334 +msgid "See also :func:`os.chown`, the underlying function." +msgstr "" + +#: ../Doc/library/shutil.rst:343 +msgid "" +"Return the path to an executable which would be run if the given *cmd* was " +"called. If no *cmd* would be called, return ``None``." +msgstr "" + +#: ../Doc/library/shutil.rst:346 +msgid "" +"*mode* is a permission mask passed to :func:`os.access`, by default " +"determining if the file exists and executable." +msgstr "" + +#: ../Doc/library/shutil.rst:349 +msgid "" +"When no *path* is specified, the results of :func:`os.environ` are used, " +"returning either the \"PATH\" value or a fallback of :attr:`os.defpath`." +msgstr "" + +#: ../Doc/library/shutil.rst:352 +msgid "" +"On Windows, the current directory is always prepended to the *path* whether " +"or not you use the default or provide your own, which is the behavior the " +"command shell uses when finding executables. Additionally, when finding the " +"*cmd* in the *path*, the ``PATHEXT`` environment variable is checked. For " +"example, if you call ``shutil.which(\"python\")``, :func:`which` will search " +"``PATHEXT`` to know that it should look for ``python.exe`` within the *path* " +"directories. For example, on Windows::" +msgstr "" + +#: ../Doc/library/shutil.rst:368 +msgid "" +"This exception collects exceptions that are raised during a multi-file " +"operation. For :func:`copytree`, the exception argument is a list of 3-" +"tuples (*srcname*, *dstname*, *exception*)." +msgstr "" + +#: ../Doc/library/shutil.rst:376 +msgid "copytree example" +msgstr "" + +#: ../Doc/library/shutil.rst:378 +msgid "" +"This example is the implementation of the :func:`copytree` function, " +"described above, with the docstring omitted. It demonstrates many of the " +"other functions provided by this module. ::" +msgstr "" + +#: ../Doc/library/shutil.rst:413 +msgid "Another example that uses the :func:`ignore_patterns` helper::" +msgstr "" + +#: ../Doc/library/shutil.rst:419 +msgid "" +"This will copy everything except ``.pyc`` files and files or directories " +"whose name starts with ``tmp``." +msgstr "" + +#: ../Doc/library/shutil.rst:422 +msgid "Another example that uses the *ignore* argument to add a logging call::" +msgstr "" + +#: ../Doc/library/shutil.rst:437 +msgid "rmtree example" +msgstr "" + +#: ../Doc/library/shutil.rst:439 +msgid "" +"This example shows how to remove a directory tree on Windows where some of " +"the files have their read-only bit set. It uses the onerror callback to " +"clear the readonly bit and reattempt the remove. Any subsequent failure will " +"propagate. ::" +msgstr "" + +#: ../Doc/library/shutil.rst:457 +msgid "Archiving operations" +msgstr "" + +#: ../Doc/library/shutil.rst:461 +msgid "" +"High-level utilities to create and read compressed and archived files are " +"also provided. They rely on the :mod:`zipfile` and :mod:`tarfile` modules." +msgstr "" + +#: ../Doc/library/shutil.rst:466 +msgid "Create an archive file (such as zip or tar) and return its name." +msgstr "" + +#: ../Doc/library/shutil.rst:468 +msgid "" +"*base_name* is the name of the file to create, including the path, minus any " +"format-specific extension. *format* is the archive format: one of \"zip\", " +"\"tar\", \"bztar\" (if the :mod:`bz2` module is available), \"xztar\" (if " +"the :mod:`lzma` module is available) or \"gztar\"." +msgstr "" + +#: ../Doc/library/shutil.rst:473 +msgid "" +"*root_dir* is a directory that will be the root directory of the archive; " +"for example, we typically chdir into *root_dir* before creating the archive." +msgstr "" + +#: ../Doc/library/shutil.rst:477 +msgid "" +"*base_dir* is the directory where we start archiving from; i.e. *base_dir* " +"will be the common prefix of all files and directories in the archive." +msgstr "" + +#: ../Doc/library/shutil.rst:481 +msgid "*root_dir* and *base_dir* both default to the current directory." +msgstr "" + +#: ../Doc/library/shutil.rst:483 +msgid "" +"If *dry_run* is true, no archive is created, but the operations that would " +"be executed are logged to *logger*." +msgstr "" + +#: ../Doc/library/shutil.rst:486 +msgid "" +"*owner* and *group* are used when creating a tar archive. By default, uses " +"the current owner and group." +msgstr "" + +#: ../Doc/library/shutil.rst:489 +msgid "" +"*logger* must be an object compatible with :pep:`282`, usually an instance " +"of :class:`logging.Logger`." +msgstr "" + +#: ../Doc/library/shutil.rst:492 +msgid "The *verbose* argument is unused and deprecated." +msgstr "" + +#: ../Doc/library/shutil.rst:494 +msgid "Added support for the *xztar* format." +msgstr "" + +#: ../Doc/library/shutil.rst:500 +msgid "" +"Return a list of supported formats for archiving. Each element of the " +"returned sequence is a tuple ``(name, description)``." +msgstr "" + +#: ../Doc/library/shutil.rst:503 ../Doc/library/shutil.rst:579 +msgid "By default :mod:`shutil` provides these formats:" +msgstr "" + +#: ../Doc/library/shutil.rst:505 ../Doc/library/shutil.rst:581 +msgid "*gztar*: gzip'ed tar-file" +msgstr "" + +#: ../Doc/library/shutil.rst:506 ../Doc/library/shutil.rst:582 +msgid "*bztar*: bzip2'ed tar-file (if the :mod:`bz2` module is available.)" +msgstr "" + +#: ../Doc/library/shutil.rst:507 ../Doc/library/shutil.rst:583 +msgid "*xztar*: xz'ed tar-file (if the :mod:`lzma` module is available.)" +msgstr "" + +#: ../Doc/library/shutil.rst:508 ../Doc/library/shutil.rst:584 +msgid "*tar*: uncompressed tar file" +msgstr "" + +#: ../Doc/library/shutil.rst:509 ../Doc/library/shutil.rst:585 +msgid "*zip*: ZIP file" +msgstr "" + +#: ../Doc/library/shutil.rst:511 +msgid "" +"You can register new formats or provide your own archiver for any existing " +"formats, by using :func:`register_archive_format`." +msgstr "" + +#: ../Doc/library/shutil.rst:517 +msgid "Register an archiver for the format *name*." +msgstr "" + +#: ../Doc/library/shutil.rst:519 +msgid "" +"*function* is the callable that will be used to unpack archives. The " +"callable will receive the *base_name* of the file to create, followed by the " +"*base_dir* (which defaults to :data:`os.curdir`) to start archiving from. " +"Further arguments are passed as keyword arguments: *owner*, *group*, " +"*dry_run* and *logger* (as passed in :func:`make_archive`)." +msgstr "" + +#: ../Doc/library/shutil.rst:525 +msgid "" +"If given, *extra_args* is a sequence of ``(name, value)`` pairs that will be " +"used as extra keywords arguments when the archiver callable is used." +msgstr "" + +#: ../Doc/library/shutil.rst:528 +msgid "" +"*description* is used by :func:`get_archive_formats` which returns the list " +"of archivers. Defaults to an empty string." +msgstr "" + +#: ../Doc/library/shutil.rst:534 +msgid "Remove the archive format *name* from the list of supported formats." +msgstr "" + +#: ../Doc/library/shutil.rst:539 +msgid "Unpack an archive. *filename* is the full path of the archive." +msgstr "" + +#: ../Doc/library/shutil.rst:541 +msgid "" +"*extract_dir* is the name of the target directory where the archive is " +"unpacked. If not provided, the current working directory is used." +msgstr "" + +#: ../Doc/library/shutil.rst:544 +msgid "" +"*format* is the archive format: one of \"zip\", \"tar\", or \"gztar\". Or " +"any other format registered with :func:`register_unpack_format`. If not " +"provided, :func:`unpack_archive` will use the archive file name extension " +"and see if an unpacker was registered for that extension. In case none is " +"found, a :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/shutil.rst:553 +msgid "" +"Registers an unpack format. *name* is the name of the format and " +"*extensions* is a list of extensions corresponding to the format, like ``." +"zip`` for Zip files." +msgstr "" + +#: ../Doc/library/shutil.rst:557 +msgid "" +"*function* is the callable that will be used to unpack archives. The " +"callable will receive the path of the archive, followed by the directory the " +"archive must be extracted to." +msgstr "" + +#: ../Doc/library/shutil.rst:561 +msgid "" +"When provided, *extra_args* is a sequence of ``(name, value)`` tuples that " +"will be passed as keywords arguments to the callable." +msgstr "" + +#: ../Doc/library/shutil.rst:564 +msgid "" +"*description* can be provided to describe the format, and will be returned " +"by the :func:`get_unpack_formats` function." +msgstr "" + +#: ../Doc/library/shutil.rst:570 +msgid "Unregister an unpack format. *name* is the name of the format." +msgstr "" + +#: ../Doc/library/shutil.rst:575 +msgid "" +"Return a list of all registered formats for unpacking. Each element of the " +"returned sequence is a tuple ``(name, extensions, description)``." +msgstr "" + +#: ../Doc/library/shutil.rst:587 +msgid "" +"You can register new formats or provide your own unpacker for any existing " +"formats, by using :func:`register_unpack_format`." +msgstr "" + +#: ../Doc/library/shutil.rst:594 +msgid "Archiving example" +msgstr "" + +#: ../Doc/library/shutil.rst:596 +msgid "" +"In this example, we create a gzip'ed tar-file archive containing all files " +"found in the :file:`.ssh` directory of the user::" +msgstr "" + +#: ../Doc/library/shutil.rst:606 +msgid "The resulting archive contains:" +msgstr "" + +#: ../Doc/library/shutil.rst:622 +msgid "Querying the size of the output terminal" +msgstr "" + +#: ../Doc/library/shutil.rst:628 +msgid "Get the size of the terminal window." +msgstr "" + +#: ../Doc/library/shutil.rst:630 +msgid "" +"For each of the two dimensions, the environment variable, ``COLUMNS`` and " +"``LINES`` respectively, is checked. If the variable is defined and the value " +"is a positive integer, it is used." +msgstr "" + +#: ../Doc/library/shutil.rst:634 +msgid "" +"When ``COLUMNS`` or ``LINES`` is not defined, which is the common case, the " +"terminal connected to :data:`sys.__stdout__` is queried by invoking :func:" +"`os.get_terminal_size`." +msgstr "" + +#: ../Doc/library/shutil.rst:638 +msgid "" +"If the terminal size cannot be successfully queried, either because the " +"system doesn't support querying, or because we are not connected to a " +"terminal, the value given in ``fallback`` parameter is used. ``fallback`` " +"defaults to ``(80, 24)`` which is the default size used by many terminal " +"emulators." +msgstr "" + +#: ../Doc/library/shutil.rst:644 +msgid "The value returned is a named tuple of type :class:`os.terminal_size`." +msgstr "" + +#: ../Doc/library/shutil.rst:646 +msgid "" +"See also: The Single UNIX Specification, Version 2, `Other Environment " +"Variables`_." +msgstr "" + +#: ../Doc/library/signal.rst:2 +msgid ":mod:`signal` --- Set handlers for asynchronous events" +msgstr "" + +#: ../Doc/library/signal.rst:9 +msgid "This module provides mechanisms to use signal handlers in Python." +msgstr "" + +#: ../Doc/library/signal.rst:13 +msgid "General rules" +msgstr "" + +#: ../Doc/library/signal.rst:15 +msgid "" +"The :func:`signal.signal` function allows defining custom handlers to be " +"executed when a signal is received. A small number of default handlers are " +"installed: :const:`SIGPIPE` is ignored (so write errors on pipes and sockets " +"can be reported as ordinary Python exceptions) and :const:`SIGINT` is " +"translated into a :exc:`KeyboardInterrupt` exception." +msgstr "" + +#: ../Doc/library/signal.rst:21 +msgid "" +"A handler for a particular signal, once set, remains installed until it is " +"explicitly reset (Python emulates the BSD style interface regardless of the " +"underlying implementation), with the exception of the handler for :const:" +"`SIGCHLD`, which follows the underlying implementation." +msgstr "" + +#: ../Doc/library/signal.rst:28 +msgid "Execution of Python signal handlers" +msgstr "" + +#: ../Doc/library/signal.rst:30 +msgid "" +"A Python signal handler does not get executed inside the low-level (C) " +"signal handler. Instead, the low-level signal handler sets a flag which " +"tells the :term:`virtual machine` to execute the corresponding Python signal " +"handler at a later point(for example at the next :term:`bytecode` " +"instruction). This has consequences:" +msgstr "" + +#: ../Doc/library/signal.rst:36 +msgid "" +"It makes little sense to catch synchronous errors like :const:`SIGFPE` or :" +"const:`SIGSEGV` that are caused by an invalid operation in C code. Python " +"will return from the signal handler to the C code, which is likely to raise " +"the same signal again, causing Python to apparently hang. From Python 3.3 " +"onwards, you can use the :mod:`faulthandler` module to report on synchronous " +"errors." +msgstr "" + +#: ../Doc/library/signal.rst:43 +msgid "" +"A long-running calculation implemented purely in C (such as regular " +"expression matching on a large body of text) may run uninterrupted for an " +"arbitrary amount of time, regardless of any signals received. The Python " +"signal handlers will be called when the calculation finishes." +msgstr "" + +#: ../Doc/library/signal.rst:53 +msgid "Signals and threads" +msgstr "" + +#: ../Doc/library/signal.rst:55 +msgid "" +"Python signal handlers are always executed in the main Python thread, even " +"if the signal was received in another thread. This means that signals can't " +"be used as a means of inter-thread communication. You can use the " +"synchronization primitives from the :mod:`threading` module instead." +msgstr "" + +#: ../Doc/library/signal.rst:60 +msgid "Besides, only the main thread is allowed to set a new signal handler." +msgstr "" + +#: ../Doc/library/signal.rst:64 ../Doc/library/site.rst:139 +#: ../Doc/library/socket.rst:181 +msgid "Module contents" +msgstr "" + +#: ../Doc/library/signal.rst:66 +msgid "" +"signal (SIG*), handler (:const:`SIG_DFL`, :const:`SIG_IGN`) and sigmask (:" +"const:`SIG_BLOCK`, :const:`SIG_UNBLOCK`, :const:`SIG_SETMASK`) related " +"constants listed below were turned into :class:`enums `. :func:" +"`getsignal`, :func:`pthread_sigmask`, :func:`sigpending` and :func:`sigwait` " +"functions return human-readable :class:`enums `." +msgstr "" + +#: ../Doc/library/signal.rst:76 +msgid "The variables defined in the :mod:`signal` module are:" +msgstr "" + +#: ../Doc/library/signal.rst:81 +msgid "" +"This is one of two standard signal handling options; it will simply perform " +"the default function for the signal. For example, on most systems the " +"default action for :const:`SIGQUIT` is to dump core and exit, while the " +"default action for :const:`SIGCHLD` is to simply ignore it." +msgstr "" + +#: ../Doc/library/signal.rst:89 +msgid "" +"This is another standard signal handler, which will simply ignore the given " +"signal." +msgstr "" + +#: ../Doc/library/signal.rst:95 +msgid "" +"All the signal numbers are defined symbolically. For example, the hangup " +"signal is defined as :const:`signal.SIGHUP`; the variable names are " +"identical to the names used in C programs, as found in ````. The " +"Unix man page for ':c:func:`signal`' lists the existing signals (on some " +"systems this is :manpage:`signal(2)`, on others the list is in :manpage:" +"`signal(7)`). Note that not all systems define the same set of signal names; " +"only those names defined by the system are defined by this module." +msgstr "" + +#: ../Doc/library/signal.rst:106 +msgid "" +"The signal corresponding to the :kbd:`Ctrl+C` keystroke event. This signal " +"can only be used with :func:`os.kill`." +msgstr "" + +#: ../Doc/library/signal.rst:116 +msgid "" +"The signal corresponding to the :kbd:`Ctrl+Break` keystroke event. This " +"signal can only be used with :func:`os.kill`." +msgstr "" + +#: ../Doc/library/signal.rst:126 +msgid "One more than the number of the highest signal number." +msgstr "" + +#: ../Doc/library/signal.rst:131 +msgid "" +"Decrements interval timer in real time, and delivers :const:`SIGALRM` upon " +"expiration." +msgstr "" + +#: ../Doc/library/signal.rst:137 +msgid "" +"Decrements interval timer only when the process is executing, and delivers " +"SIGVTALRM upon expiration." +msgstr "" + +#: ../Doc/library/signal.rst:143 +msgid "" +"Decrements interval timer both when the process executes and when the system " +"is executing on behalf of the process. Coupled with ITIMER_VIRTUAL, this " +"timer is usually used to profile the time spent by the application in user " +"and kernel space. SIGPROF is delivered upon expiration." +msgstr "" + +#: ../Doc/library/signal.rst:151 +msgid "" +"A possible value for the *how* parameter to :func:`pthread_sigmask` " +"indicating that signals are to be blocked." +msgstr "" + +#: ../Doc/library/signal.rst:158 +msgid "" +"A possible value for the *how* parameter to :func:`pthread_sigmask` " +"indicating that signals are to be unblocked." +msgstr "" + +#: ../Doc/library/signal.rst:165 +msgid "" +"A possible value for the *how* parameter to :func:`pthread_sigmask` " +"indicating that the signal mask is to be replaced." +msgstr "" + +#: ../Doc/library/signal.rst:171 +msgid "The :mod:`signal` module defines one exception:" +msgstr "" + +#: ../Doc/library/signal.rst:175 +msgid "" +"Raised to signal an error from the underlying :func:`setitimer` or :func:" +"`getitimer` implementation. Expect this error if an invalid interval timer " +"or a negative time is passed to :func:`setitimer`. This error is a subtype " +"of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/signal.rst:180 +msgid "" +"This error used to be a subtype of :exc:`IOError`, which is now an alias of :" +"exc:`OSError`." +msgstr "" + +#: ../Doc/library/signal.rst:185 +msgid "The :mod:`signal` module defines the following functions:" +msgstr "" + +#: ../Doc/library/signal.rst:190 +msgid "" +"If *time* is non-zero, this function requests that a :const:`SIGALRM` signal " +"be sent to the process in *time* seconds. Any previously scheduled alarm is " +"canceled (only one alarm can be scheduled at any time). The returned value " +"is then the number of seconds before any previously set alarm was to have " +"been delivered. If *time* is zero, no alarm is scheduled, and any scheduled " +"alarm is canceled. If the return value is zero, no alarm is currently " +"scheduled. (See the Unix man page :manpage:`alarm(2)`.) Availability: Unix." +msgstr "" + +#: ../Doc/library/signal.rst:201 +msgid "" +"Return the current signal handler for the signal *signalnum*. The returned " +"value may be a callable Python object, or one of the special values :const:" +"`signal.SIG_IGN`, :const:`signal.SIG_DFL` or :const:`None`. Here, :const:" +"`signal.SIG_IGN` means that the signal was previously ignored, :const:" +"`signal.SIG_DFL` means that the default way of handling the signal was " +"previously in use, and ``None`` means that the previous signal handler was " +"not installed from Python." +msgstr "" + +#: ../Doc/library/signal.rst:212 +msgid "" +"Cause the process to sleep until a signal is received; the appropriate " +"handler will then be called. Returns nothing. Not on Windows. (See the " +"Unix man page :manpage:`signal(2)`.)" +msgstr "" + +#: ../Doc/library/signal.rst:216 +msgid "" +"See also :func:`sigwait`, :func:`sigwaitinfo`, :func:`sigtimedwait` and :" +"func:`sigpending`." +msgstr "" + +#: ../Doc/library/signal.rst:222 +msgid "" +"Send the signal *signalnum* to the thread *thread_id*, another thread in the " +"same process as the caller. The target thread can be executing any code " +"(Python or not). However, if the target thread is executing the Python " +"interpreter, the Python signal handlers will be :ref:`executed by the main " +"thread `. Therefore, the only point of sending a " +"signal to a particular Python thread would be to force a running system call " +"to fail with :exc:`InterruptedError`." +msgstr "" + +#: ../Doc/library/signal.rst:230 +msgid "" +"Use :func:`threading.get_ident()` or the :attr:`~threading.Thread.ident` " +"attribute of :class:`threading.Thread` objects to get a suitable value for " +"*thread_id*." +msgstr "" + +#: ../Doc/library/signal.rst:234 +msgid "" +"If *signalnum* is 0, then no signal is sent, but error checking is still " +"performed; this can be used to check if the target thread is still running." +msgstr "" + +#: ../Doc/library/signal.rst:237 +msgid "" +"Availability: Unix (see the man page :manpage:`pthread_kill(3)` for further " +"information)." +msgstr "" + +#: ../Doc/library/signal.rst:240 +msgid "See also :func:`os.kill`." +msgstr "" + +#: ../Doc/library/signal.rst:247 +msgid "" +"Fetch and/or change the signal mask of the calling thread. The signal mask " +"is the set of signals whose delivery is currently blocked for the caller. " +"Return the old signal mask as a set of signals." +msgstr "" + +#: ../Doc/library/signal.rst:251 +msgid "" +"The behavior of the call is dependent on the value of *how*, as follows." +msgstr "" + +#: ../Doc/library/signal.rst:253 +msgid "" +":data:`SIG_BLOCK`: The set of blocked signals is the union of the current " +"set and the *mask* argument." +msgstr "" + +#: ../Doc/library/signal.rst:255 +msgid "" +":data:`SIG_UNBLOCK`: The signals in *mask* are removed from the current set " +"of blocked signals. It is permissible to attempt to unblock a signal which " +"is not blocked." +msgstr "" + +#: ../Doc/library/signal.rst:258 +msgid "" +":data:`SIG_SETMASK`: The set of blocked signals is set to the *mask* " +"argument." +msgstr "" + +#: ../Doc/library/signal.rst:261 +msgid "" +"*mask* is a set of signal numbers (e.g. {:const:`signal.SIGINT`, :const:" +"`signal.SIGTERM`}). Use ``range(1, signal.NSIG)`` for a full mask including " +"all signals." +msgstr "" + +#: ../Doc/library/signal.rst:265 +msgid "" +"For example, ``signal.pthread_sigmask(signal.SIG_BLOCK, [])`` reads the " +"signal mask of the calling thread." +msgstr "" + +#: ../Doc/library/signal.rst:268 +msgid "" +"Availability: Unix. See the man page :manpage:`sigprocmask(3)` and :manpage:" +"`pthread_sigmask(3)` for further information." +msgstr "" + +#: ../Doc/library/signal.rst:271 +msgid "See also :func:`pause`, :func:`sigpending` and :func:`sigwait`." +msgstr "" + +#: ../Doc/library/signal.rst:278 +msgid "" +"Sets given interval timer (one of :const:`signal.ITIMER_REAL`, :const:" +"`signal.ITIMER_VIRTUAL` or :const:`signal.ITIMER_PROF`) specified by *which* " +"to fire after *seconds* (float is accepted, different from :func:`alarm`) " +"and after that every *interval* seconds. The interval timer specified by " +"*which* can be cleared by setting seconds to zero." +msgstr "" + +#: ../Doc/library/signal.rst:284 +msgid "" +"When an interval timer fires, a signal is sent to the process. The signal " +"sent is dependent on the timer being used; :const:`signal.ITIMER_REAL` will " +"deliver :const:`SIGALRM`, :const:`signal.ITIMER_VIRTUAL` sends :const:" +"`SIGVTALRM`, and :const:`signal.ITIMER_PROF` will deliver :const:`SIGPROF`." +msgstr "" + +#: ../Doc/library/signal.rst:290 +msgid "The old values are returned as a tuple: (delay, interval)." +msgstr "" + +#: ../Doc/library/signal.rst:292 +msgid "" +"Attempting to pass an invalid interval timer will cause an :exc:" +"`ItimerError`. Availability: Unix." +msgstr "" + +#: ../Doc/library/signal.rst:298 +msgid "" +"Returns current value of a given interval timer specified by *which*. " +"Availability: Unix." +msgstr "" + +#: ../Doc/library/signal.rst:304 +msgid "" +"Set the wakeup file descriptor to *fd*. When a signal is received, the " +"signal number is written as a single byte into the fd. This can be used by " +"a library to wakeup a poll or select call, allowing the signal to be fully " +"processed." +msgstr "" + +#: ../Doc/library/signal.rst:309 +msgid "" +"The old wakeup fd is returned. *fd* must be non-blocking. It is up to the " +"library to remove any bytes before calling poll or select again." +msgstr "" + +#: ../Doc/library/signal.rst:312 +msgid "" +"Use for example ``struct.unpack('%uB' % len(data), data)`` to decode the " +"signal numbers list." +msgstr "" + +#: ../Doc/library/signal.rst:315 ../Doc/library/signal.rst:343 +msgid "" +"When threads are enabled, this function can only be called from the main " +"thread; attempting to call it from other threads will cause a :exc:" +"`ValueError` exception to be raised." +msgstr "" + +#: ../Doc/library/signal.rst:319 +msgid "On Windows, the function now also supports socket handles." +msgstr "" + +#: ../Doc/library/signal.rst:325 +msgid "" +"Change system call restart behaviour: if *flag* is :const:`False`, system " +"calls will be restarted when interrupted by signal *signalnum*, otherwise " +"system calls will be interrupted. Returns nothing. Availability: Unix (see " +"the man page :manpage:`siginterrupt(3)` for further information)." +msgstr "" + +#: ../Doc/library/signal.rst:330 +msgid "" +"Note that installing a signal handler with :func:`signal` will reset the " +"restart behaviour to interruptible by implicitly calling :c:func:" +"`siginterrupt` with a true *flag* value for the given signal." +msgstr "" + +#: ../Doc/library/signal.rst:337 +msgid "" +"Set the handler for signal *signalnum* to the function *handler*. *handler* " +"can be a callable Python object taking two arguments (see below), or one of " +"the special values :const:`signal.SIG_IGN` or :const:`signal.SIG_DFL`. The " +"previous signal handler will be returned (see the description of :func:" +"`getsignal` above). (See the Unix man page :manpage:`signal(2)`.)" +msgstr "" + +#: ../Doc/library/signal.rst:347 +msgid "" +"The *handler* is called with two arguments: the signal number and the " +"current stack frame (``None`` or a frame object; for a description of frame " +"objects, see the :ref:`description in the type hierarchy ` or " +"see the attribute descriptions in the :mod:`inspect` module)." +msgstr "" + +#: ../Doc/library/signal.rst:352 +msgid "" +"On Windows, :func:`signal` can only be called with :const:`SIGABRT`, :const:" +"`SIGFPE`, :const:`SIGILL`, :const:`SIGINT`, :const:`SIGSEGV`, or :const:" +"`SIGTERM`. A :exc:`ValueError` will be raised in any other case. Note that " +"not all systems define the same set of signal names; an :exc:" +"`AttributeError` will be raised if a signal name is not defined as ``SIG*`` " +"module level constant." +msgstr "" + +#: ../Doc/library/signal.rst:362 +msgid "" +"Examine the set of signals that are pending for delivery to the calling " +"thread (i.e., the signals which have been raised while blocked). Return the " +"set of the pending signals." +msgstr "" + +#: ../Doc/library/signal.rst:366 +msgid "" +"Availability: Unix (see the man page :manpage:`sigpending(2)` for further " +"information)." +msgstr "" + +#: ../Doc/library/signal.rst:369 +msgid "See also :func:`pause`, :func:`pthread_sigmask` and :func:`sigwait`." +msgstr "" + +#: ../Doc/library/signal.rst:376 +msgid "" +"Suspend execution of the calling thread until the delivery of one of the " +"signals specified in the signal set *sigset*. The function accepts the " +"signal (removes it from the pending list of signals), and returns the signal " +"number." +msgstr "" + +#: ../Doc/library/signal.rst:380 +msgid "" +"Availability: Unix (see the man page :manpage:`sigwait(3)` for further " +"information)." +msgstr "" + +#: ../Doc/library/signal.rst:383 +msgid "" +"See also :func:`pause`, :func:`pthread_sigmask`, :func:`sigpending`, :func:" +"`sigwaitinfo` and :func:`sigtimedwait`." +msgstr "" + +#: ../Doc/library/signal.rst:391 +msgid "" +"Suspend execution of the calling thread until the delivery of one of the " +"signals specified in the signal set *sigset*. The function accepts the " +"signal and removes it from the pending list of signals. If one of the " +"signals in *sigset* is already pending for the calling thread, the function " +"will return immediately with information about that signal. The signal " +"handler is not called for the delivered signal. The function raises an :exc:" +"`InterruptedError` if it is interrupted by a signal that is not in *sigset*." +msgstr "" + +#: ../Doc/library/signal.rst:400 +msgid "" +"The return value is an object representing the data contained in the :c:type:" +"`siginfo_t` structure, namely: :attr:`si_signo`, :attr:`si_code`, :attr:" +"`si_errno`, :attr:`si_pid`, :attr:`si_uid`, :attr:`si_status`, :attr:" +"`si_band`." +msgstr "" + +#: ../Doc/library/signal.rst:405 +msgid "" +"Availability: Unix (see the man page :manpage:`sigwaitinfo(2)` for further " +"information)." +msgstr "" + +#: ../Doc/library/signal.rst:408 +msgid "See also :func:`pause`, :func:`sigwait` and :func:`sigtimedwait`." +msgstr "" + +#: ../Doc/library/signal.rst:412 +msgid "" +"The function is now retried if interrupted by a signal not in *sigset* and " +"the signal handler does not raise an exception (see :pep:`475` for the " +"rationale)." +msgstr "" + +#: ../Doc/library/signal.rst:420 +msgid "" +"Like :func:`sigwaitinfo`, but takes an additional *timeout* argument " +"specifying a timeout. If *timeout* is specified as :const:`0`, a poll is " +"performed. Returns :const:`None` if a timeout occurs." +msgstr "" + +#: ../Doc/library/signal.rst:424 +msgid "" +"Availability: Unix (see the man page :manpage:`sigtimedwait(2)` for further " +"information)." +msgstr "" + +#: ../Doc/library/signal.rst:427 +msgid "See also :func:`pause`, :func:`sigwait` and :func:`sigwaitinfo`." +msgstr "" + +#: ../Doc/library/signal.rst:431 +msgid "" +"The function is now retried with the recomputed *timeout* if interrupted by " +"a signal not in *sigset* and the signal handler does not raise an exception " +"(see :pep:`475` for the rationale)." +msgstr "" + +#: ../Doc/library/signal.rst:442 +msgid "" +"Here is a minimal example program. It uses the :func:`alarm` function to " +"limit the time spent waiting to open a file; this is useful if the file is " +"for a serial device that may not be turned on, which would normally cause " +"the :func:`os.open` to hang indefinitely. The solution is to set a 5-second " +"alarm before opening the file; if the operation takes too long, the alarm " +"signal will be sent, and the handler raises an exception. ::" +msgstr "" + +#: ../Doc/library/site.rst:2 +msgid ":mod:`site` --- Site-specific configuration hook" +msgstr "" + +#: ../Doc/library/site.rst:7 +msgid "**Source code:** :source:`Lib/site.py`" +msgstr "" + +#: ../Doc/library/site.rst:13 +msgid "" +"**This module is automatically imported during initialization.** The " +"automatic import can be suppressed using the interpreter's :option:`-S` " +"option." +msgstr "" + +#: ../Doc/library/site.rst:18 +msgid "" +"Importing this module will append site-specific paths to the module search " +"path and add a few builtins, unless :option:`-S` was used. In that case, " +"this module can be safely imported with no automatic modifications to the " +"module search path or additions to the builtins. To explicitly trigger the " +"usual site-specific additions, call the :func:`site.main` function." +msgstr "" + +#: ../Doc/library/site.rst:24 +msgid "" +"Importing the module used to trigger paths manipulation even when using :" +"option:`-S`." +msgstr "" + +#: ../Doc/library/site.rst:31 +msgid "" +"It starts by constructing up to four directories from a head and a tail " +"part. For the head part, it uses ``sys.prefix`` and ``sys.exec_prefix``; " +"empty heads are skipped. For the tail part, it uses the empty string and " +"then :file:`lib/site-packages` (on Windows) or :file:`lib/python{X.Y}/site-" +"packages` (on Unix and Macintosh). For each of the distinct head-tail " +"combinations, it sees if it refers to an existing directory, and if so, adds " +"it to ``sys.path`` and also inspects the newly added path for configuration " +"files." +msgstr "" + +#: ../Doc/library/site.rst:40 +msgid "Support for the \"site-python\" directory has been removed." +msgstr "" + +#: ../Doc/library/site.rst:43 +msgid "" +"If a file named \"pyvenv.cfg\" exists one directory above sys.executable, " +"sys.prefix and sys.exec_prefix are set to that directory and it is also " +"checked for site-packages (sys.base_prefix and sys.base_exec_prefix will " +"always be the \"real\" prefixes of the Python installation). If \"pyvenv.cfg" +"\" (a bootstrap configuration file) contains the key \"include-system-site-" +"packages\" set to anything other than \"false\" (case-insensitive), the " +"system-level prefixes will still also be searched for site-packages; " +"otherwise they won't." +msgstr "" + +#: ../Doc/library/site.rst:52 +msgid "" +"A path configuration file is a file whose name has the form :file:`{name}." +"pth` and exists in one of the four directories mentioned above; its contents " +"are additional items (one per line) to be added to ``sys.path``. Non-" +"existing items are never added to ``sys.path``, and no check is made that " +"the item refers to a directory rather than a file. No item is added to " +"``sys.path`` more than once. Blank lines and lines beginning with ``#`` are " +"skipped. Lines starting with ``import`` (followed by space or tab) are " +"executed." +msgstr "" + +#: ../Doc/library/site.rst:64 +msgid "" +"For example, suppose ``sys.prefix`` and ``sys.exec_prefix`` are set to :file:" +"`/usr/local`. The Python X.Y library is then installed in :file:`/usr/local/" +"lib/python{X.Y}`. Suppose this has a subdirectory :file:`/usr/local/lib/" +"python{X.Y}/site-packages` with three subsubdirectories, :file:`foo`, :file:" +"`bar` and :file:`spam`, and two path configuration files, :file:`foo.pth` " +"and :file:`bar.pth`. Assume :file:`foo.pth` contains the following::" +msgstr "" + +#: ../Doc/library/site.rst:78 +msgid "and :file:`bar.pth` contains::" +msgstr "" + +#: ../Doc/library/site.rst:84 +msgid "" +"Then the following version-specific directories are added to ``sys.path``, " +"in this order::" +msgstr "" + +#: ../Doc/library/site.rst:90 +msgid "" +"Note that :file:`bletch` is omitted because it doesn't exist; the :file:" +"`bar` directory precedes the :file:`foo` directory because :file:`bar.pth` " +"comes alphabetically before :file:`foo.pth`; and :file:`spam` is omitted " +"because it is not mentioned in either path configuration file." +msgstr "" + +#: ../Doc/library/site.rst:97 +msgid "" +"After these path manipulations, an attempt is made to import a module named :" +"mod:`sitecustomize`, which can perform arbitrary site-specific " +"customizations. It is typically created by a system administrator in the " +"site-packages directory. If this import fails with an :exc:`ImportError` " +"exception, it is silently ignored. If Python is started without output " +"streams available, as with :file:`pythonw.exe` on Windows (which is used by " +"default to start IDLE), attempted output from :mod:`sitecustomize` is " +"ignored. Any exception other than :exc:`ImportError` causes a silent and " +"perhaps mysterious failure of the process." +msgstr "" + +#: ../Doc/library/site.rst:109 +msgid "" +"After this, an attempt is made to import a module named :mod:" +"`usercustomize`, which can perform arbitrary user-specific customizations, " +"if :data:`ENABLE_USER_SITE` is true. This file is intended to be created in " +"the user site-packages directory (see below), which is part of ``sys.path`` " +"unless disabled by :option:`-s`. An :exc:`ImportError` will be silently " +"ignored." +msgstr "" + +#: ../Doc/library/site.rst:115 +msgid "" +"Note that for some non-Unix systems, ``sys.prefix`` and ``sys.exec_prefix`` " +"are empty, and the path manipulations are skipped; however the import of :" +"mod:`sitecustomize` and :mod:`usercustomize` is still attempted." +msgstr "" + +#: ../Doc/library/site.rst:123 +msgid "Readline configuration" +msgstr "" + +#: ../Doc/library/site.rst:125 +msgid "" +"On systems that support :mod:`readline`, this module will also import and " +"configure the :mod:`rlcompleter` module, if Python is started in :ref:" +"`interactive mode ` and without the :option:`-S` option. " +"The default behavior is enable tab-completion and to use :file:`~/." +"python_history` as the history save file. To disable it, delete (or " +"override) the :data:`sys.__interactivehook__` attribute in your :mod:" +"`sitecustomize` or :mod:`usercustomize` module or your :envvar:" +"`PYTHONSTARTUP` file." +msgstr "" + +#: ../Doc/library/site.rst:134 +msgid "Activation of rlcompleter and history was made automatic." +msgstr "" + +#: ../Doc/library/site.rst:143 +msgid "A list of prefixes for site-packages directories." +msgstr "" + +#: ../Doc/library/site.rst:148 +msgid "" +"Flag showing the status of the user site-packages directory. ``True`` means " +"that it is enabled and was added to ``sys.path``. ``False`` means that it " +"was disabled by user request (with :option:`-s` or :envvar:" +"`PYTHONNOUSERSITE`). ``None`` means it was disabled for security reasons " +"(mismatch between user or group id and effective id) or by an administrator." +msgstr "" + +#: ../Doc/library/site.rst:158 +msgid "" +"Path to the user site-packages for the running Python. Can be ``None`` if :" +"func:`getusersitepackages` hasn't been called yet. Default value is :file:" +"`~/.local/lib/python{X.Y}/site-packages` for UNIX and non-framework Mac OS X " +"builds, :file:`~/Library/Python/{X.Y}/lib/python/site-packages` for Mac " +"framework builds, and :file:`{%APPDATA%}\\\\Python\\\\Python{XY}\\\\site-" +"packages` on Windows. This directory is a site directory, which means that :" +"file:`.pth` files in it will be processed." +msgstr "" + +#: ../Doc/library/site.rst:169 +msgid "" +"Path to the base directory for the user site-packages. Can be ``None`` if :" +"func:`getuserbase` hasn't been called yet. Default value is :file:`~/." +"local` for UNIX and Mac OS X non-framework builds, :file:`~/Library/Python/" +"{X.Y}` for Mac framework builds, and :file:`{%APPDATA%}\\\\Python` for " +"Windows. This value is used by Distutils to compute the installation " +"directories for scripts, data files, Python modules, etc. for the :ref:`user " +"installation scheme `. See also :envvar:" +"`PYTHONUSERBASE`." +msgstr "" + +#: ../Doc/library/site.rst:181 +msgid "" +"Adds all the standard site-specific directories to the module search path. " +"This function is called automatically when this module is imported, unless " +"the Python interpreter was started with the :option:`-S` flag." +msgstr "" + +#: ../Doc/library/site.rst:185 +msgid "This function used to be called unconditionally." +msgstr "" + +#: ../Doc/library/site.rst:191 +msgid "" +"Add a directory to sys.path and process its :file:`.pth` files. Typically " +"used in :mod:`sitecustomize` or :mod:`usercustomize` (see above)." +msgstr "" + +#: ../Doc/library/site.rst:197 +msgid "Return a list containing all global site-packages directories." +msgstr "" + +#: ../Doc/library/site.rst:204 +msgid "" +"Return the path of the user base directory, :data:`USER_BASE`. If it is not " +"initialized yet, this function will also set it, respecting :envvar:" +"`PYTHONUSERBASE`." +msgstr "" + +#: ../Doc/library/site.rst:213 +msgid "" +"Return the path of the user-specific site-packages directory, :data:" +"`USER_SITE`. If it is not initialized yet, this function will also set it, " +"respecting :envvar:`PYTHONNOUSERSITE` and :data:`USER_BASE`." +msgstr "" + +#: ../Doc/library/site.rst:220 +msgid "" +"The :mod:`site` module also provides a way to get the user directories from " +"the command line:" +msgstr "" + +#: ../Doc/library/site.rst:230 +msgid "" +"If it is called without arguments, it will print the contents of :data:`sys." +"path` on the standard output, followed by the value of :data:`USER_BASE` and " +"whether the directory exists, then the same thing for :data:`USER_SITE`, and " +"finally the value of :data:`ENABLE_USER_SITE`." +msgstr "" + +#: ../Doc/library/site.rst:237 +msgid "Print the path to the user base directory." +msgstr "" + +#: ../Doc/library/site.rst:241 +msgid "Print the path to the user site-packages directory." +msgstr "" + +#: ../Doc/library/site.rst:243 +msgid "" +"If both options are given, user base and user site will be printed (always " +"in this order), separated by :data:`os.pathsep`." +msgstr "" + +#: ../Doc/library/site.rst:246 +msgid "" +"If any option is given, the script will exit with one of these values: ``O`` " +"if the user site-packages directory is enabled, ``1`` if it was disabled by " +"the user, ``2`` if it is disabled for security reasons or by an " +"administrator, and a value greater than 2 if there is an error." +msgstr "" + +#: ../Doc/library/site.rst:253 +msgid ":pep:`370` -- Per user site-packages directory" +msgstr "" + +#: ../Doc/library/smtpd.rst:2 +msgid ":mod:`smtpd` --- SMTP Server" +msgstr "" + +#: ../Doc/library/smtpd.rst:10 +msgid "**Source code:** :source:`Lib/smtpd.py`" +msgstr "" + +#: ../Doc/library/smtpd.rst:14 +msgid "This module offers several classes to implement SMTP (email) servers." +msgstr "" + +#: ../Doc/library/smtpd.rst:16 +msgid "" +"Several server implementations are present; one is a generic do-nothing " +"implementation, which can be overridden, while the other two offer specific " +"mail-sending strategies." +msgstr "" + +#: ../Doc/library/smtpd.rst:20 +msgid "" +"Additionally the SMTPChannel may be extended to implement very specific " +"interaction behaviour with SMTP clients." +msgstr "" + +#: ../Doc/library/smtpd.rst:23 +msgid "" +"The code supports :RFC:`5321`, plus the :rfc:`1870` SIZE and :rfc:`6531` " +"SMTPUTF8 extensions." +msgstr "" + +#: ../Doc/library/smtpd.rst:28 +msgid "SMTPServer Objects" +msgstr "" + +#: ../Doc/library/smtpd.rst:34 +msgid "" +"Create a new :class:`SMTPServer` object, which binds to local address " +"*localaddr*. It will treat *remoteaddr* as an upstream SMTP relayer. Both " +"*localaddr* and *remoteaddr* should be a :ref:`(host, port) ` " +"tuple. The object inherits from :class:`asyncore.dispatcher`, and so will " +"insert itself into :mod:`asyncore`'s event loop on instantiation." +msgstr "" + +#: ../Doc/library/smtpd.rst:40 ../Doc/library/smtpd.rst:162 +msgid "" +"*data_size_limit* specifies the maximum number of bytes that will be " +"accepted in a ``DATA`` command. A value of ``None`` or ``0`` means no limit." +msgstr "" + +#: ../Doc/library/smtpd.rst:44 +msgid "" +"*map* is the socket map to use for connections (an initially empty " +"dictionary is a suitable value). If not specified the :mod:`asyncore` " +"global socket map is used." +msgstr "" + +#: ../Doc/library/smtpd.rst:48 +msgid "" +"*enable_SMTPUTF8* determines whether the ``SMTPUTF8`` extension (as defined " +"in :RFC:`6531`) should be enabled. The default is ``False``. When ``True``, " +"``SMTPUTF8`` is accepted as a parameter to the ``MAIL`` command and when " +"present is passed to :meth:`process_message` in the " +"``kwargs['mail_options']`` list. *decode_data* and *enable_SMTPUTF8* cannot " +"be set to ``True`` at the same time." +msgstr "" + +#: ../Doc/library/smtpd.rst:55 +msgid "" +"*decode_data* specifies whether the data portion of the SMTP transaction " +"should be decoded using UTF-8. When *decode_data* is ``False`` (the " +"default), the server advertises the ``8BITMIME`` extension (:rfc:`6152`), " +"accepts the ``BODY=8BITMIME`` parameter to the ``MAIL`` command, and when " +"present passes it to :meth:`process_message` in the " +"``kwargs['mail_options']`` list. *decode_data* and *enable_SMTPUTF8* cannot " +"be set to ``True`` at the same time." +msgstr "" + +#: ../Doc/library/smtpd.rst:65 +msgid "" +"Raise a :exc:`NotImplementedError` exception. Override this in subclasses to " +"do something useful with this message. Whatever was passed in the " +"constructor as *remoteaddr* will be available as the :attr:`_remoteaddr` " +"attribute. *peer* is the remote host's address, *mailfrom* is the envelope " +"originator, *rcpttos* are the envelope recipients and *data* is a string " +"containing the contents of the e-mail (which should be in :rfc:`5321` " +"format)." +msgstr "" + +#: ../Doc/library/smtpd.rst:73 +msgid "" +"If the *decode_data* constructor keyword is set to ``True``, the *data* " +"argument will be a unicode string. If it is set to ``False``, it will be a " +"bytes object." +msgstr "" + +#: ../Doc/library/smtpd.rst:77 +msgid "" +"*kwargs* is a dictionary containing additional information. It is empty if " +"``decode_data=True`` was given as an init argument, otherwise it contains " +"the following keys:" +msgstr "" + +#: ../Doc/library/smtpd.rst:84 +msgid "*mail_options*:" +msgstr "" + +#: ../Doc/library/smtpd.rst:82 +msgid "" +"a list of all received parameters to the ``MAIL`` command (the elements are " +"uppercase strings; example: ``['BODY=8BITMIME', 'SMTPUTF8']``)." +msgstr "" + +#: ../Doc/library/smtpd.rst:89 +msgid "*rcpt_options*:" +msgstr "" + +#: ../Doc/library/smtpd.rst:87 +msgid "" +"same as *mail_options* but for the ``RCPT`` command. Currently no ``RCPT " +"TO`` options are supported, so for now this will always be an empty list." +msgstr "" + +#: ../Doc/library/smtpd.rst:91 +msgid "" +"Implementations of ``process_message`` should use the ``**kwargs`` signature " +"to accept arbitrary keyword arguments, since future feature enhancements may " +"add keys to the kwargs dictionary." +msgstr "" + +#: ../Doc/library/smtpd.rst:95 +msgid "" +"Return ``None`` to request a normal ``250 Ok`` response; otherwise return " +"the desired response string in :RFC:`5321` format." +msgstr "" + +#: ../Doc/library/smtpd.rst:100 +msgid "" +"Override this in subclasses to use a custom :class:`SMTPChannel` for " +"managing SMTP clients." +msgstr "" + +#: ../Doc/library/smtpd.rst:103 +msgid "The *map* constructor argument." +msgstr "" + +#: ../Doc/library/smtpd.rst:106 +msgid "*localaddr* and *remoteaddr* may now contain IPv6 addresses." +msgstr "" + +#: ../Doc/library/smtpd.rst:109 +msgid "" +"The *decode_data* and *enable_SMTPUTF8* constructor parameters, and the " +"*kwargs* parameter to :meth:`process_message` when *decode_data* is " +"``False``." +msgstr "" + +#: ../Doc/library/smtpd.rst:114 ../Doc/library/smtpd.rst:184 +msgid "*decode_data* is now ``False`` by default." +msgstr "" + +#: ../Doc/library/smtpd.rst:119 +msgid "DebuggingServer Objects" +msgstr "" + +#: ../Doc/library/smtpd.rst:124 +msgid "" +"Create a new debugging server. Arguments are as per :class:`SMTPServer`. " +"Messages will be discarded, and printed on stdout." +msgstr "" + +#: ../Doc/library/smtpd.rst:129 +msgid "PureProxy Objects" +msgstr "" + +#: ../Doc/library/smtpd.rst:134 +msgid "" +"Create a new pure proxy server. Arguments are as per :class:`SMTPServer`. " +"Everything will be relayed to *remoteaddr*. Note that running this has a " +"good chance to make you into an open relay, so please be careful." +msgstr "" + +#: ../Doc/library/smtpd.rst:140 +msgid "MailmanProxy Objects" +msgstr "" + +#: ../Doc/library/smtpd.rst:145 +msgid "" +"Create a new pure proxy server. Arguments are as per :class:`SMTPServer`. " +"Everything will be relayed to *remoteaddr*, unless local mailman " +"configurations knows about an address, in which case it will be handled via " +"mailman. Note that running this has a good chance to make you into an open " +"relay, so please be careful." +msgstr "" + +#: ../Doc/library/smtpd.rst:152 +msgid "SMTPChannel Objects" +msgstr "" + +#: ../Doc/library/smtpd.rst:157 +msgid "" +"Create a new :class:`SMTPChannel` object which manages the communication " +"between the server and a single SMTP client." +msgstr "" + +#: ../Doc/library/smtpd.rst:160 +msgid "*conn* and *addr* are as per the instance variables described below." +msgstr "" + +#: ../Doc/library/smtpd.rst:166 +msgid "" +"*enable_SMTPUTF8* determines whether the ``SMTPUTF8`` extension (as defined " +"in :RFC:`6531`) should be enabled. The default is ``False``. *decode_data* " +"and *enable_SMTPUTF8* cannot be set to ``True`` at the same time." +msgstr "" + +#: ../Doc/library/smtpd.rst:171 +msgid "" +"A dictionary can be specified in *map* to avoid using a global socket map." +msgstr "" + +#: ../Doc/library/smtpd.rst:173 +msgid "" +"*decode_data* specifies whether the data portion of the SMTP transaction " +"should be decoded using UTF-8. The default is ``False``. *decode_data* and " +"*enable_SMTPUTF8* cannot be set to ``True`` at the same time." +msgstr "" + +#: ../Doc/library/smtpd.rst:178 +msgid "" +"To use a custom SMTPChannel implementation you need to override the :attr:" +"`SMTPServer.channel_class` of your :class:`SMTPServer`." +msgstr "" + +#: ../Doc/library/smtpd.rst:181 +msgid "The *decode_data* and *enable_SMTPUTF8* parameters were added." +msgstr "" + +#: ../Doc/library/smtpd.rst:187 +msgid "The :class:`SMTPChannel` has the following instance variables:" +msgstr "" + +#: ../Doc/library/smtpd.rst:191 +msgid "Holds the :class:`SMTPServer` that spawned this channel." +msgstr "" + +#: ../Doc/library/smtpd.rst:195 +msgid "Holds the socket object connecting to the client." +msgstr "" + +#: ../Doc/library/smtpd.rst:199 +msgid "" +"Holds the address of the client, the second value returned by :func:`socket." +"accept `" +msgstr "" + +#: ../Doc/library/smtpd.rst:204 +msgid "" +"Holds a list of the line strings (decoded using UTF-8) received from the " +"client. The lines have their ``\"\\r\\n\"`` line ending translated to ``\"\\n" +"\"``." +msgstr "" + +#: ../Doc/library/smtpd.rst:210 +msgid "" +"Holds the current state of the channel. This will be either :attr:`COMMAND` " +"initially and then :attr:`DATA` after the client sends a \"DATA\" line." +msgstr "" + +#: ../Doc/library/smtpd.rst:216 +msgid "" +"Holds a string containing the greeting sent by the client in its \"HELO\"." +msgstr "" + +#: ../Doc/library/smtpd.rst:220 +msgid "" +"Holds a string containing the address identified in the \"MAIL FROM:\" line " +"from the client." +msgstr "" + +#: ../Doc/library/smtpd.rst:225 +msgid "" +"Holds a list of strings containing the addresses identified in the \"RCPT TO:" +"\" lines from the client." +msgstr "" + +#: ../Doc/library/smtpd.rst:230 +msgid "" +"Holds a string containing all of the data sent by the client during the DATA " +"state, up to but not including the terminating ``\"\\r\\n.\\r\\n\"``." +msgstr "" + +#: ../Doc/library/smtpd.rst:235 +msgid "" +"Holds the fully-qualified domain name of the server as returned by :func:" +"`socket.getfqdn`." +msgstr "" + +#: ../Doc/library/smtpd.rst:240 +msgid "" +"Holds the name of the client peer as returned by ``conn.getpeername()`` " +"where ``conn`` is :attr:`conn`." +msgstr "" + +#: ../Doc/library/smtpd.rst:243 +msgid "" +"The :class:`SMTPChannel` operates by invoking methods named " +"``smtp_`` upon reception of a command line from the client. Built " +"into the base :class:`SMTPChannel` class are methods for handling the " +"following commands (and responding to them appropriately):" +msgstr "" + +#: ../Doc/library/smtpd.rst:249 +msgid "Command" +msgstr "" + +#: ../Doc/library/smtpd.rst:249 +msgid "Action taken" +msgstr "" + +#: ../Doc/library/smtpd.rst:251 +msgid "HELO" +msgstr "" + +#: ../Doc/library/smtpd.rst:251 +msgid "" +"Accepts the greeting from the client and stores it in :attr:" +"`seen_greeting`. Sets server to base command mode." +msgstr "" + +#: ../Doc/library/smtpd.rst:253 +msgid "EHLO" +msgstr "" + +#: ../Doc/library/smtpd.rst:253 +msgid "" +"Accepts the greeting from the client and stores it in :attr:" +"`seen_greeting`. Sets server to extended command mode." +msgstr "" + +#: ../Doc/library/smtpd.rst:255 +msgid "NOOP" +msgstr "" + +#: ../Doc/library/smtpd.rst:255 +msgid "Takes no action." +msgstr "" + +#: ../Doc/library/smtpd.rst:256 +msgid "QUIT" +msgstr "" + +#: ../Doc/library/smtpd.rst:256 +msgid "Closes the connection cleanly." +msgstr "" + +#: ../Doc/library/smtpd.rst:257 +msgid "MAIL" +msgstr "" + +#: ../Doc/library/smtpd.rst:257 +msgid "" +"Accepts the \"MAIL FROM:\" syntax and stores the supplied address as :attr:" +"`mailfrom`. In extended command mode, accepts the :rfc:`1870` SIZE " +"attribute and responds appropriately based on the value of *data_size_limit*." +msgstr "" + +#: ../Doc/library/smtpd.rst:261 +msgid "RCPT" +msgstr "" + +#: ../Doc/library/smtpd.rst:261 +msgid "" +"Accepts the \"RCPT TO:\" syntax and stores the supplied addresses in the :" +"attr:`rcpttos` list." +msgstr "" + +#: ../Doc/library/smtpd.rst:263 +msgid "RSET" +msgstr "" + +#: ../Doc/library/smtpd.rst:263 +msgid "" +"Resets the :attr:`mailfrom`, :attr:`rcpttos`, and :attr:`received_data`, but " +"not the greeting." +msgstr "" + +#: ../Doc/library/smtpd.rst:265 +msgid "DATA" +msgstr "" + +#: ../Doc/library/smtpd.rst:265 +msgid "" +"Sets the internal state to :attr:`DATA` and stores remaining lines from the " +"client in :attr:`received_data` until the terminator ``\"\\r\\n.\\r\\n\"`` " +"is received." +msgstr "" + +#: ../Doc/library/smtpd.rst:268 +msgid "HELP" +msgstr "" + +#: ../Doc/library/smtpd.rst:268 +msgid "Returns minimal information on command syntax" +msgstr "" + +#: ../Doc/library/smtpd.rst:269 +msgid "VRFY" +msgstr "" + +#: ../Doc/library/smtpd.rst:269 +msgid "Returns code 252 (the server doesn't know if the address is valid)" +msgstr "" + +#: ../Doc/library/smtpd.rst:270 +msgid "EXPN" +msgstr "" + +#: ../Doc/library/smtpd.rst:270 +msgid "Reports that the command is not implemented." +msgstr "" + +#: ../Doc/library/smtplib.rst:2 +msgid ":mod:`smtplib` --- SMTP protocol client" +msgstr "" + +#: ../Doc/library/smtplib.rst:9 +msgid "**Source code:** :source:`Lib/smtplib.py`" +msgstr "" + +#: ../Doc/library/smtplib.rst:17 +msgid "" +"The :mod:`smtplib` module defines an SMTP client session object that can be " +"used to send mail to any Internet machine with an SMTP or ESMTP listener " +"daemon. For details of SMTP and ESMTP operation, consult :rfc:`821` (Simple " +"Mail Transfer Protocol) and :rfc:`1869` (SMTP Service Extensions)." +msgstr "" + +#: ../Doc/library/smtplib.rst:25 +msgid "" +"An :class:`SMTP` instance encapsulates an SMTP connection. It has methods " +"that support a full repertoire of SMTP and ESMTP operations. If the optional " +"host and port parameters are given, the SMTP :meth:`connect` method is " +"called with those parameters during initialization. If specified, " +"*local_hostname* is used as the FQDN of the local host in the HELO/EHLO " +"command. Otherwise, the local hostname is found using :func:`socket." +"getfqdn`. If the :meth:`connect` call returns anything other than a success " +"code, an :exc:`SMTPConnectError` is raised. The optional *timeout* parameter " +"specifies a timeout in seconds for blocking operations like the connection " +"attempt (if not specified, the global default timeout setting will be " +"used). If the timeout expires, :exc:`socket.timeout` is raised. The " +"optional source_address parameter allows binding to some specific source " +"address in a machine with multiple network interfaces, and/or to some " +"specific source TCP port. It takes a 2-tuple (host, port), for the socket to " +"bind to as its source address before connecting. If omitted (or if host or " +"port are ``''`` and/or 0 respectively) the OS default behavior will be used." +msgstr "" + +#: ../Doc/library/smtplib.rst:43 +msgid "" +"For normal use, you should only require the initialization/connect, :meth:" +"`sendmail`, and :meth:`~smtplib.quit` methods. An example is included below." +msgstr "" + +#: ../Doc/library/smtplib.rst:47 +msgid "" +"The :class:`SMTP` class supports the :keyword:`with` statement. When used " +"like this, the SMTP ``QUIT`` command is issued automatically when the :" +"keyword:`with` statement exits. E.g.::" +msgstr "" + +#: ../Doc/library/smtplib.rst:61 ../Doc/library/smtplib.rst:90 +msgid "source_address argument was added." +msgstr "" + +#: ../Doc/library/smtplib.rst:64 +msgid "The SMTPUTF8 extension (:rfc:`6531`) is now supported." +msgstr "" + +#: ../Doc/library/smtplib.rst:72 +msgid "" +"An :class:`SMTP_SSL` instance behaves exactly the same as instances of :" +"class:`SMTP`. :class:`SMTP_SSL` should be used for situations where SSL is " +"required from the beginning of the connection and using :meth:`starttls` is " +"not appropriate. If *host* is not specified, the local host is used. If " +"*port* is zero, the standard SMTP-over-SSL port (465) is used. The optional " +"arguments *local_hostname*, *timeout* and *source_address* have the same " +"meaning as they do in the :class:`SMTP` class. *context*, also optional, " +"can contain a :class:`~ssl.SSLContext` and allows configuring various " +"aspects of the secure connection. Please read :ref:`ssl-security` for best " +"practices." +msgstr "" + +#: ../Doc/library/smtplib.rst:83 +msgid "" +"*keyfile* and *certfile* are a legacy alternative to *context*, and can " +"point to a PEM formatted private key and certificate chain file for the SSL " +"connection." +msgstr "" + +#: ../Doc/library/smtplib.rst:87 ../Doc/library/smtplib.rst:400 +#: ../Doc/library/urllib.request.rst:111 +msgid "*context* was added." +msgstr "" + +#: ../Doc/library/smtplib.rst:108 +msgid "" +"The LMTP protocol, which is very similar to ESMTP, is heavily based on the " +"standard SMTP client. It's common to use Unix sockets for LMTP, so our :meth:" +"`connect` method must support that as well as a regular host:port server. " +"The optional arguments local_hostname and source_address have the same " +"meaning as they do in the :class:`SMTP` class. To specify a Unix socket, you " +"must use an absolute path for *host*, starting with a '/'." +msgstr "" + +#: ../Doc/library/smtplib.rst:115 +msgid "" +"Authentication is supported, using the regular SMTP mechanism. When using a " +"Unix socket, LMTP generally don't support or require any authentication, but " +"your mileage might vary." +msgstr "" + +#: ../Doc/library/smtplib.rst:120 +msgid "A nice selection of exceptions is defined as well:" +msgstr "" + +#: ../Doc/library/smtplib.rst:125 +msgid "" +"Subclass of :exc:`OSError` that is the base exception class for all the " +"other exceptions provided by this module." +msgstr "" + +#: ../Doc/library/smtplib.rst:128 +msgid "SMTPException became subclass of :exc:`OSError`" +msgstr "" + +#: ../Doc/library/smtplib.rst:134 +msgid "" +"This exception is raised when the server unexpectedly disconnects, or when " +"an attempt is made to use the :class:`SMTP` instance before connecting it to " +"a server." +msgstr "" + +#: ../Doc/library/smtplib.rst:141 +msgid "" +"Base class for all exceptions that include an SMTP error code. These " +"exceptions are generated in some instances when the SMTP server returns an " +"error code. The error code is stored in the :attr:`smtp_code` attribute of " +"the error, and the :attr:`smtp_error` attribute is set to the error message." +msgstr "" + +#: ../Doc/library/smtplib.rst:149 +msgid "" +"Sender address refused. In addition to the attributes set by on all :exc:" +"`SMTPResponseException` exceptions, this sets 'sender' to the string that " +"the SMTP server refused." +msgstr "" + +#: ../Doc/library/smtplib.rst:156 +msgid "" +"All recipient addresses refused. The errors for each recipient are " +"accessible through the attribute :attr:`recipients`, which is a dictionary " +"of exactly the same sort as :meth:`SMTP.sendmail` returns." +msgstr "" + +#: ../Doc/library/smtplib.rst:163 +msgid "The SMTP server refused to accept the message data." +msgstr "" + +#: ../Doc/library/smtplib.rst:168 +msgid "Error occurred during establishment of a connection with the server." +msgstr "" + +#: ../Doc/library/smtplib.rst:173 +msgid "The server refused our ``HELO`` message." +msgstr "" + +#: ../Doc/library/smtplib.rst:178 +msgid "The command or option attempted is not supported by the server." +msgstr "" + +#: ../Doc/library/smtplib.rst:185 +msgid "" +"SMTP authentication went wrong. Most probably the server didn't accept the " +"username/password combination provided." +msgstr "" + +#: ../Doc/library/smtplib.rst:193 +msgid ":rfc:`821` - Simple Mail Transfer Protocol" +msgstr "" + +#: ../Doc/library/smtplib.rst:192 +msgid "" +"Protocol definition for SMTP. This document covers the model, operating " +"procedure, and protocol details for SMTP." +msgstr "" + +#: ../Doc/library/smtplib.rst:197 +msgid ":rfc:`1869` - SMTP Service Extensions" +msgstr "" + +#: ../Doc/library/smtplib.rst:196 +msgid "" +"Definition of the ESMTP extensions for SMTP. This describes a framework for " +"extending SMTP with new commands, supporting dynamic discovery of the " +"commands provided by the server, and defines a few additional commands." +msgstr "" + +#: ../Doc/library/smtplib.rst:204 +msgid "SMTP Objects" +msgstr "" + +#: ../Doc/library/smtplib.rst:206 +msgid "An :class:`SMTP` instance has the following methods:" +msgstr "" + +#: ../Doc/library/smtplib.rst:211 +msgid "" +"Set the debug output level. A value of 1 or ``True`` for *level* results in " +"debug messages for connection and for all messages sent to and received from " +"the server. A value of 2 for *level* results in these messages being " +"timestamped." +msgstr "" + +#: ../Doc/library/smtplib.rst:216 +msgid "Added debuglevel 2." +msgstr "" + +#: ../Doc/library/smtplib.rst:221 +msgid "" +"Send a command *cmd* to the server. The optional argument *args* is simply " +"concatenated to the command, separated by a space." +msgstr "" + +#: ../Doc/library/smtplib.rst:224 +msgid "" +"This returns a 2-tuple composed of a numeric response code and the actual " +"response line (multiline responses are joined into one long line.)" +msgstr "" + +#: ../Doc/library/smtplib.rst:227 +msgid "" +"In normal operation it should not be necessary to call this method " +"explicitly. It is used to implement other methods and may be useful for " +"testing private extensions." +msgstr "" + +#: ../Doc/library/smtplib.rst:231 +msgid "" +"If the connection to the server is lost while waiting for the reply, :exc:" +"`SMTPServerDisconnected` will be raised." +msgstr "" + +#: ../Doc/library/smtplib.rst:237 +msgid "" +"Connect to a host on a given port. The defaults are to connect to the local " +"host at the standard SMTP port (25). If the hostname ends with a colon " +"(``':'``) followed by a number, that suffix will be stripped off and the " +"number interpreted as the port number to use. This method is automatically " +"invoked by the constructor if a host is specified during instantiation. " +"Returns a 2-tuple of the response code and message sent by the server in its " +"connection response." +msgstr "" + +#: ../Doc/library/smtplib.rst:248 +msgid "" +"Identify yourself to the SMTP server using ``HELO``. The hostname argument " +"defaults to the fully qualified domain name of the local host. The message " +"returned by the server is stored as the :attr:`helo_resp` attribute of the " +"object." +msgstr "" + +#: ../Doc/library/smtplib.rst:253 +msgid "" +"In normal operation it should not be necessary to call this method " +"explicitly. It will be implicitly called by the :meth:`sendmail` when " +"necessary." +msgstr "" + +#: ../Doc/library/smtplib.rst:259 +msgid "" +"Identify yourself to an ESMTP server using ``EHLO``. The hostname argument " +"defaults to the fully qualified domain name of the local host. Examine the " +"response for ESMTP option and store them for use by :meth:`has_extn`. Also " +"sets several informational attributes: the message returned by the server is " +"stored as the :attr:`ehlo_resp` attribute, :attr:`does_esmtp` is set to true " +"or false depending on whether the server supports ESMTP, and :attr:" +"`esmtp_features` will be a dictionary containing the names of the SMTP " +"service extensions this server supports, and their parameters (if any)." +msgstr "" + +#: ../Doc/library/smtplib.rst:268 +msgid "" +"Unless you wish to use :meth:`has_extn` before sending mail, it should not " +"be necessary to call this method explicitly. It will be implicitly called " +"by :meth:`sendmail` when necessary." +msgstr "" + +#: ../Doc/library/smtplib.rst:274 +msgid "" +"This method call :meth:`ehlo` and or :meth:`helo` if there has been no " +"previous ``EHLO`` or ``HELO`` command this session. It tries ESMTP ``EHLO`` " +"first." +msgstr "" + +#: ../Doc/library/smtplib.rst:278 ../Doc/library/smtplib.rst:308 +#: ../Doc/library/smtplib.rst:392 ../Doc/library/smtplib.rst:461 +msgid ":exc:`SMTPHeloError`" +msgstr "" + +#: ../Doc/library/smtplib.rst:279 ../Doc/library/smtplib.rst:308 +#: ../Doc/library/smtplib.rst:392 ../Doc/library/smtplib.rst:461 +msgid "The server didn't reply properly to the ``HELO`` greeting." +msgstr "" + +#: ../Doc/library/smtplib.rst:283 +msgid "" +"Return :const:`True` if *name* is in the set of SMTP service extensions " +"returned by the server, :const:`False` otherwise. Case is ignored." +msgstr "" + +#: ../Doc/library/smtplib.rst:289 +msgid "" +"Check the validity of an address on this server using SMTP ``VRFY``. Returns " +"a tuple consisting of code 250 and a full :rfc:`822` address (including " +"human name) if the user address is valid. Otherwise returns an SMTP error " +"code of 400 or greater and an error string." +msgstr "" + +#: ../Doc/library/smtplib.rst:296 +msgid "Many sites disable SMTP ``VRFY`` in order to foil spammers." +msgstr "" + +#: ../Doc/library/smtplib.rst:301 +msgid "" +"Log in on an SMTP server that requires authentication. The arguments are the " +"username and the password to authenticate with. If there has been no " +"previous ``EHLO`` or ``HELO`` command this session, this method tries ESMTP " +"``EHLO`` first. This method will return normally if the authentication was " +"successful, or may raise the following exceptions:" +msgstr "" + +#: ../Doc/library/smtplib.rst:311 +msgid ":exc:`SMTPAuthenticationError`" +msgstr "" + +#: ../Doc/library/smtplib.rst:311 +msgid "The server didn't accept the username/password combination." +msgstr "" + +#: ../Doc/library/smtplib.rst:314 ../Doc/library/smtplib.rst:395 +#: ../Doc/library/smtplib.rst:472 +msgid ":exc:`SMTPNotSupportedError`" +msgstr "" + +#: ../Doc/library/smtplib.rst:314 +msgid "The ``AUTH`` command is not supported by the server." +msgstr "" + +#: ../Doc/library/smtplib.rst:317 +msgid ":exc:`SMTPException`" +msgstr "" + +#: ../Doc/library/smtplib.rst:317 +msgid "No suitable authentication method was found." +msgstr "" + +#: ../Doc/library/smtplib.rst:319 +msgid "" +"Each of the authentication methods supported by :mod:`smtplib` are tried in " +"turn if they are advertised as supported by the server. See :meth:`auth` " +"for a list of supported authentication methods. *initial_response_ok* is " +"passed through to :meth:`auth`." +msgstr "" + +#: ../Doc/library/smtplib.rst:324 +msgid "" +"Optional keyword argument *initial_response_ok* specifies whether, for " +"authentication methods that support it, an \"initial response\" as specified " +"in :rfc:`4954` can be sent along with the ``AUTH`` command, rather than " +"requiring a challenge/response." +msgstr "" + +#: ../Doc/library/smtplib.rst:329 +msgid "" +":exc:`SMTPNotSupportedError` may be raised, and the *initial_response_ok* " +"parameter was added." +msgstr "" + +#: ../Doc/library/smtplib.rst:336 +msgid "" +"Issue an ``SMTP`` ``AUTH`` command for the specified authentication " +"*mechanism*, and handle the challenge response via *authobject*." +msgstr "" + +#: ../Doc/library/smtplib.rst:339 +msgid "" +"*mechanism* specifies which authentication mechanism is to be used as " +"argument to the ``AUTH`` command; the valid values are those listed in the " +"``auth`` element of :attr:`esmtp_features`." +msgstr "" + +#: ../Doc/library/smtplib.rst:343 +msgid "" +"*authobject* must be a callable object taking an optional single argument:" +msgstr "" + +#: ../Doc/library/smtplib.rst:345 +msgid "data = authobject(challenge=None)" +msgstr "" + +#: ../Doc/library/smtplib.rst:347 +msgid "" +"If optional keyword argument *initial_response_ok* is true, ``authobject()`` " +"will be called first with no argument. It can return the :rfc:`4954` " +"\"initial response\" bytes which will be encoded and sent with the ``AUTH`` " +"command as below. If the ``authobject()`` does not support an initial " +"response (e.g. because it requires a challenge), it should return None when " +"called with ``challenge=None``. If *initial_response_ok* is false, then " +"``authobject()`` will not be called first with None." +msgstr "" + +#: ../Doc/library/smtplib.rst:355 +msgid "" +"If the initial response check returns None, or if *initial_response_ok* is " +"false, ``authobject()`` will be called to process the server's challenge " +"response; the *challenge* argument it is passed will be a ``bytes``. It " +"should return ``bytes`` *data* that will be base64 encoded and sent to the " +"server." +msgstr "" + +#: ../Doc/library/smtplib.rst:361 +msgid "" +"The ``SMTP`` class provides ``authobjects`` for the ``CRAM-MD5``, ``PLAIN``, " +"and ``LOGIN`` mechanisms; they are named ``SMTP.auth_cram_md5``, ``SMTP." +"auth_plain``, and ``SMTP.auth_login`` respectively. They all require that " +"the ``user`` and ``password`` properties of the ``SMTP`` instance are set to " +"appropriate values." +msgstr "" + +#: ../Doc/library/smtplib.rst:367 +msgid "" +"User code does not normally need to call ``auth`` directly, but can instead " +"call the :meth:`login` method, which will try each of the above mechanisms " +"in turn, in the order listed. ``auth`` is exposed to facilitate the " +"implementation of authentication methods not (or not yet) supported directly " +"by :mod:`smtplib`." +msgstr "" + +#: ../Doc/library/smtplib.rst:378 +msgid "" +"Put the SMTP connection in TLS (Transport Layer Security) mode. All SMTP " +"commands that follow will be encrypted. You should then call :meth:`ehlo` " +"again." +msgstr "" + +#: ../Doc/library/smtplib.rst:382 +msgid "" +"If *keyfile* and *certfile* are provided, these are passed to the :mod:" +"`socket` module's :func:`ssl` function." +msgstr "" + +#: ../Doc/library/smtplib.rst:385 +msgid "" +"Optional *context* parameter is a :class:`ssl.SSLContext` object; This is an " +"alternative to using a keyfile and a certfile and if specified both " +"*keyfile* and *certfile* should be None." +msgstr "" + +#: ../Doc/library/smtplib.rst:388 +msgid "" +"If there has been no previous ``EHLO`` or ``HELO`` command this session, " +"this method tries ESMTP ``EHLO`` first." +msgstr "" + +#: ../Doc/library/smtplib.rst:395 +msgid "The server does not support the STARTTLS extension." +msgstr "" + +#: ../Doc/library/smtplib.rst:398 +msgid ":exc:`RuntimeError`" +msgstr "" + +#: ../Doc/library/smtplib.rst:398 +msgid "SSL/TLS support is not available to your Python interpreter." +msgstr "" + +#: ../Doc/library/smtplib.rst:403 +msgid "" +"The method now supports hostname check with :attr:`SSLContext." +"check_hostname` and *Server Name Indicator* (see :data:`~ssl.HAS_SNI`)." +msgstr "" + +#: ../Doc/library/smtplib.rst:408 +msgid "" +"The error raised for lack of STARTTLS support is now the :exc:" +"`SMTPNotSupportedError` subclass instead of the base :exc:`SMTPException`." +msgstr "" + +#: ../Doc/library/smtplib.rst:416 +msgid "" +"Send mail. The required arguments are an :rfc:`822` from-address string, a " +"list of :rfc:`822` to-address strings (a bare string will be treated as a " +"list with 1 address), and a message string. The caller may pass a list of " +"ESMTP options (such as ``8bitmime``) to be used in ``MAIL FROM`` commands as " +"*mail_options*. ESMTP options (such as ``DSN`` commands) that should be used " +"with all ``RCPT`` commands can be passed as *rcpt_options*. (If you need to " +"use different ESMTP options to different recipients you have to use the low-" +"level methods such as :meth:`mail`, :meth:`rcpt` and :meth:`data` to send " +"the message.)" +msgstr "" + +#: ../Doc/library/smtplib.rst:427 +msgid "" +"The *from_addr* and *to_addrs* parameters are used to construct the message " +"envelope used by the transport agents. ``sendmail`` does not modify the " +"message headers in any way." +msgstr "" + +#: ../Doc/library/smtplib.rst:431 +msgid "" +"*msg* may be a string containing characters in the ASCII range, or a byte " +"string. A string is encoded to bytes using the ascii codec, and lone ``" +"\\r`` and ``\\n`` characters are converted to ``\\r\\n`` characters. A byte " +"string is not modified." +msgstr "" + +#: ../Doc/library/smtplib.rst:436 +msgid "" +"If there has been no previous ``EHLO`` or ``HELO`` command this session, " +"this method tries ESMTP ``EHLO`` first. If the server does ESMTP, message " +"size and each of the specified options will be passed to it (if the option " +"is in the feature set the server advertises). If ``EHLO`` fails, ``HELO`` " +"will be tried and ESMTP options suppressed." +msgstr "" + +#: ../Doc/library/smtplib.rst:442 +msgid "" +"This method will return normally if the mail is accepted for at least one " +"recipient. Otherwise it will raise an exception. That is, if this method " +"does not raise an exception, then someone should get your mail. If this " +"method does not raise an exception, it returns a dictionary, with one entry " +"for each recipient that was refused. Each entry contains a tuple of the " +"SMTP error code and the accompanying error message sent by the server." +msgstr "" + +#: ../Doc/library/smtplib.rst:449 +msgid "" +"If ``SMTPUTF8`` is included in *mail_options*, and the server supports it, " +"*from_addr* and *to_addrs* may contain non-ASCII characters." +msgstr "" + +#: ../Doc/library/smtplib.rst:452 +msgid "This method may raise the following exceptions:" +msgstr "" + +#: ../Doc/library/smtplib.rst:458 +msgid ":exc:`SMTPRecipientsRefused`" +msgstr "" + +#: ../Doc/library/smtplib.rst:455 +msgid "" +"All recipients were refused. Nobody got the mail. The :attr:`recipients` " +"attribute of the exception object is a dictionary with information about the " +"refused recipients (like the one returned when at least one recipient was " +"accepted)." +msgstr "" + +#: ../Doc/library/smtplib.rst:464 +msgid ":exc:`SMTPSenderRefused`" +msgstr "" + +#: ../Doc/library/smtplib.rst:464 +msgid "The server didn't accept the *from_addr*." +msgstr "" + +#: ../Doc/library/smtplib.rst:468 +msgid ":exc:`SMTPDataError`" +msgstr "" + +#: ../Doc/library/smtplib.rst:467 +msgid "" +"The server replied with an unexpected error code (other than a refusal of a " +"recipient)." +msgstr "" + +#: ../Doc/library/smtplib.rst:471 +msgid "" +"``SMTPUTF8`` was given in the *mail_options* but is not supported by the " +"server." +msgstr "" + +#: ../Doc/library/smtplib.rst:474 +msgid "" +"Unless otherwise noted, the connection will be open even after an exception " +"is raised." +msgstr "" + +#: ../Doc/library/smtplib.rst:477 +msgid "*msg* may be a byte string." +msgstr "" + +#: ../Doc/library/smtplib.rst:480 +msgid "" +"``SMTPUTF8`` support added, and :exc:`SMTPNotSupportedError` may be raised " +"if ``SMTPUTF8`` is specified but the server does not support it." +msgstr "" + +#: ../Doc/library/smtplib.rst:488 +msgid "" +"This is a convenience method for calling :meth:`sendmail` with the message " +"represented by an :class:`email.message.Message` object. The arguments have " +"the same meaning as for :meth:`sendmail`, except that *msg* is a ``Message`` " +"object." +msgstr "" + +#: ../Doc/library/smtplib.rst:493 +msgid "" +"If *from_addr* is ``None`` or *to_addrs* is ``None``, ``send_message`` fills " +"those arguments with addresses extracted from the headers of *msg* as " +"specified in :rfc:`5322`\\: *from_addr* is set to the :mailheader:`Sender` " +"field if it is present, and otherwise to the :mailheader:`From` field. " +"*to_addrs* combines the values (if any) of the :mailheader:`To`, :mailheader:" +"`Cc`, and :mailheader:`Bcc` fields from *msg*. If exactly one set of :" +"mailheader:`Resent-*` headers appear in the message, the regular headers are " +"ignored and the :mailheader:`Resent-*` headers are used instead. If the " +"message contains more than one set of :mailheader:`Resent-*` headers, a :exc:" +"`ValueError` is raised, since there is no way to unambiguously detect the " +"most recent set of :mailheader:`Resent-` headers." +msgstr "" + +#: ../Doc/library/smtplib.rst:505 +msgid "" +"``send_message`` serializes *msg* using :class:`~email.generator." +"BytesGenerator` with ``\\r\\n`` as the *linesep*, and calls :meth:`sendmail` " +"to transmit the resulting message. Regardless of the values of *from_addr* " +"and *to_addrs*, ``send_message`` does not transmit any :mailheader:`Bcc` or :" +"mailheader:`Resent-Bcc` headers that may appear in *msg*. If any of the " +"addresses in *from_addr* and *to_addrs* contain non-ASCII characters and the " +"server does not advertise ``SMTPUTF8`` support, an :exc:`SMTPNotSupported` " +"error is raised. Otherwise the ``Message`` is serialized with a clone of " +"its :mod:`~email.policy` with the :attr:`~email.policy.EmailPolicy.utf8` " +"attribute set to ``True``, and ``SMTPUTF8`` and ``BODY=8BITMIME`` are added " +"to *mail_options*." +msgstr "" + +#: ../Doc/library/smtplib.rst:519 +msgid "Support for internationalized addresses (``SMTPUTF8``)." +msgstr "" + +#: ../Doc/library/smtplib.rst:525 +msgid "" +"Terminate the SMTP session and close the connection. Return the result of " +"the SMTP ``QUIT`` command." +msgstr "" + +#: ../Doc/library/smtplib.rst:529 +msgid "" +"Low-level methods corresponding to the standard SMTP/ESMTP commands " +"``HELP``, ``RSET``, ``NOOP``, ``MAIL``, ``RCPT``, and ``DATA`` are also " +"supported. Normally these do not need to be called directly, so they are not " +"documented here. For details, consult the module code." +msgstr "" + +#: ../Doc/library/smtplib.rst:538 +msgid "SMTP Example" +msgstr "" + +#: ../Doc/library/smtplib.rst:540 +msgid "" +"This example prompts the user for addresses needed in the message envelope " +"('To' and 'From' addresses), and the message to be delivered. Note that the " +"headers to be included with the message must be included in the message as " +"entered; this example doesn't do any processing of the :rfc:`822` headers. " +"In particular, the 'To' and 'From' addresses must be included in the message " +"headers explicitly. ::" +msgstr "" + +#: ../Doc/library/smtplib.rst:576 +msgid "" +"In general, you will want to use the :mod:`email` package's features to " +"construct an email message, which you can then send via :meth:`~smtplib.SMTP." +"send_message`; see :ref:`email-examples`." +msgstr "" + +#: ../Doc/library/sndhdr.rst:2 +msgid ":mod:`sndhdr` --- Determine type of sound file" +msgstr "" + +#: ../Doc/library/sndhdr.rst:10 +msgid "**Source code:** :source:`Lib/sndhdr.py`" +msgstr "" + +#: ../Doc/library/sndhdr.rst:18 +msgid "" +"The :mod:`sndhdr` provides utility functions which attempt to determine the " +"type of sound data which is in a file. When these functions are able to " +"determine what type of sound data is stored in a file, they return a :func:" +"`~collections.namedtuple`, containing five attributes: (``filetype``, " +"``framerate``, ``nchannels``, ``nframes``, ``sampwidth``). The value for " +"*type* indicates the data type and will be one of the strings ``'aifc'``, " +"``'aiff'``, ``'au'``, ``'hcom'``, ``'sndr'``, ``'sndt'``, ``'voc'``, " +"``'wav'``, ``'8svx'``, ``'sb'``, ``'ub'``, or ``'ul'``. The *sampling_rate* " +"will be either the actual value or ``0`` if unknown or difficult to decode. " +"Similarly, *channels* will be either the number of channels or ``0`` if it " +"cannot be determined or if the value is difficult to decode. The value for " +"*frames* will be either the number of frames or ``-1``. The last item in " +"the tuple, *bits_per_sample*, will either be the sample size in bits or " +"``'A'`` for A-LAW or ``'U'`` for u-LAW." +msgstr "" + +#: ../Doc/library/sndhdr.rst:35 +msgid "" +"Determines the type of sound data stored in the file *filename* using :func:" +"`whathdr`. If it succeeds, returns a namedtuple as described above, " +"otherwise ``None`` is returned." +msgstr "" + +#: ../Doc/library/sndhdr.rst:45 +msgid "" +"Determines the type of sound data stored in a file based on the file " +"header. The name of the file is given by *filename*. This function returns " +"a namedtuple as described above on success, or ``None``." +msgstr "" + +#: ../Doc/library/socket.rst:2 +msgid ":mod:`socket` --- Low-level networking interface" +msgstr "" + +#: ../Doc/library/socket.rst:7 +msgid "**Source code:** :source:`Lib/socket.py`" +msgstr "" + +#: ../Doc/library/socket.rst:11 +msgid "" +"This module provides access to the BSD *socket* interface. It is available " +"on all modern Unix systems, Windows, MacOS, and probably additional " +"platforms." +msgstr "" + +#: ../Doc/library/socket.rst:16 +msgid "" +"Some behavior may be platform dependent, since calls are made to the " +"operating system socket APIs." +msgstr "" + +#: ../Doc/library/socket.rst:21 +msgid "" +"The Python interface is a straightforward transliteration of the Unix system " +"call and library interface for sockets to Python's object-oriented style: " +"the :func:`.socket` function returns a :dfn:`socket object` whose methods " +"implement the various socket system calls. Parameter types are somewhat " +"higher-level than in the C interface: as with :meth:`read` and :meth:`write` " +"operations on Python files, buffer allocation on receive operations is " +"automatic, and buffer length is implicit on send operations." +msgstr "" + +#: ../Doc/library/socket.rst:33 +msgid "Module :mod:`socketserver`" +msgstr "" + +#: ../Doc/library/socket.rst:33 +msgid "Classes that simplify writing network servers." +msgstr "" + +#: ../Doc/library/socket.rst:35 +msgid "Module :mod:`ssl`" +msgstr "" + +#: ../Doc/library/socket.rst:36 +msgid "A TLS/SSL wrapper for socket objects." +msgstr "" + +#: ../Doc/library/socket.rst:40 +msgid "Socket families" +msgstr "" + +#: ../Doc/library/socket.rst:42 +msgid "" +"Depending on the system and the build options, various socket families are " +"supported by this module." +msgstr "" + +#: ../Doc/library/socket.rst:45 +msgid "" +"The address format required by a particular socket object is automatically " +"selected based on the address family specified when the socket object was " +"created. Socket addresses are represented as follows:" +msgstr "" + +#: ../Doc/library/socket.rst:49 +msgid "" +"The address of an :const:`AF_UNIX` socket bound to a file system node is " +"represented as a string, using the file system encoding and the " +"``'surrogateescape'`` error handler (see :pep:`383`). An address in Linux's " +"abstract namespace is returned as a :term:`bytes-like object` with an " +"initial null byte; note that sockets in this namespace can communicate with " +"normal file system sockets, so programs intended to run on Linux may need to " +"deal with both types of address. A string or bytes-like object can be used " +"for either type of address when passing it as an argument." +msgstr "" + +#: ../Doc/library/socket.rst:59 +msgid "" +"Previously, :const:`AF_UNIX` socket paths were assumed to use UTF-8 encoding." +msgstr "" + +#: ../Doc/library/socket.rst:68 +msgid "" +"A pair ``(host, port)`` is used for the :const:`AF_INET` address family, " +"where *host* is a string representing either a hostname in Internet domain " +"notation like ``'daring.cwi.nl'`` or an IPv4 address like " +"``'100.50.200.5'``, and *port* is an integer." +msgstr "" + +#: ../Doc/library/socket.rst:73 +msgid "" +"For :const:`AF_INET6` address family, a four-tuple ``(host, port, flowinfo, " +"scopeid)`` is used, where *flowinfo* and *scopeid* represent the " +"``sin6_flowinfo`` and ``sin6_scope_id`` members in :const:`struct " +"sockaddr_in6` in C. For :mod:`socket` module methods, *flowinfo* and " +"*scopeid* can be omitted just for backward compatibility. Note, however, " +"omission of *scopeid* can cause problems in manipulating scoped IPv6 " +"addresses." +msgstr "" + +#: ../Doc/library/socket.rst:80 +msgid ":const:`AF_NETLINK` sockets are represented as pairs ``(pid, groups)``." +msgstr "" + +#: ../Doc/library/socket.rst:82 +msgid "" +"Linux-only support for TIPC is available using the :const:`AF_TIPC` address " +"family. TIPC is an open, non-IP based networked protocol designed for use " +"in clustered computer environments. Addresses are represented by a tuple, " +"and the fields depend on the address type. The general tuple form is " +"``(addr_type, v1, v2, v3 [, scope])``, where:" +msgstr "" + +#: ../Doc/library/socket.rst:88 +msgid "" +"*addr_type* is one of :const:`TIPC_ADDR_NAMESEQ`, :const:`TIPC_ADDR_NAME`, " +"or :const:`TIPC_ADDR_ID`." +msgstr "" + +#: ../Doc/library/socket.rst:90 +msgid "" +"*scope* is one of :const:`TIPC_ZONE_SCOPE`, :const:`TIPC_CLUSTER_SCOPE`, " +"and :const:`TIPC_NODE_SCOPE`." +msgstr "" + +#: ../Doc/library/socket.rst:92 +msgid "" +"If *addr_type* is :const:`TIPC_ADDR_NAME`, then *v1* is the server type, " +"*v2* is the port identifier, and *v3* should be 0." +msgstr "" + +#: ../Doc/library/socket.rst:95 +msgid "" +"If *addr_type* is :const:`TIPC_ADDR_NAMESEQ`, then *v1* is the server type, " +"*v2* is the lower port number, and *v3* is the upper port number." +msgstr "" + +#: ../Doc/library/socket.rst:98 +msgid "" +"If *addr_type* is :const:`TIPC_ADDR_ID`, then *v1* is the node, *v2* is the " +"reference, and *v3* should be set to 0." +msgstr "" + +#: ../Doc/library/socket.rst:101 +msgid "" +"A tuple ``(interface, )`` is used for the :const:`AF_CAN` address family, " +"where *interface* is a string representing a network interface name like " +"``'can0'``. The network interface name ``''`` can be used to receive packets " +"from all network interfaces of this family." +msgstr "" + +#: ../Doc/library/socket.rst:106 +msgid "" +"A string or a tuple ``(id, unit)`` is used for the :const:`SYSPROTO_CONTROL` " +"protocol of the :const:`PF_SYSTEM` family. The string is the name of a " +"kernel control using a dynamically-assigned ID. The tuple can be used if ID " +"and unit number of the kernel control are known or if a registered ID is " +"used." +msgstr "" + +#: ../Doc/library/socket.rst:114 +msgid "" +":const:`AF_BLUETOOTH` supports the following protocols and address formats:" +msgstr "" + +#: ../Doc/library/socket.rst:117 +msgid "" +":const:`BTPROTO_L2CAP` accepts ``(bdaddr, psm)`` where ``bdaddr`` is the " +"Bluetooth address as a string and ``psm`` is an integer." +msgstr "" + +#: ../Doc/library/socket.rst:120 +msgid "" +":const:`BTPROTO_RFCOMM` accepts ``(bdaddr, channel)`` where ``bdaddr`` is " +"the Bluetooth address as a string and ``channel`` is an integer." +msgstr "" + +#: ../Doc/library/socket.rst:123 +msgid "" +":const:`BTPROTO_HCI` accepts ``(device_id,)`` where ``device_id`` is either " +"an integer or a string with the Bluetooth address of the interface. (This " +"depends on your OS; NetBSD and DragonFlyBSD expect a Bluetooth address while " +"everything else expects an integer.)" +msgstr "" + +#: ../Doc/library/socket.rst:128 +msgid "NetBSD and DragonFlyBSD support added." +msgstr "" + +#: ../Doc/library/socket.rst:131 +msgid "" +":const:`BTPROTO_SCO` accepts ``bdaddr`` where ``bdaddr`` is a :class:`bytes` " +"object containing the Bluetooth address in a string format. (ex. " +"``b'12:23:34:45:56:67'``) This protocol is not supported under FreeBSD." +msgstr "" + +#: ../Doc/library/socket.rst:136 +msgid "" +":const:`AF_ALG` is a Linux-only socket based interface to Kernel " +"cryptography. An algorithm socket is configured with a tuple of two to four " +"elements ``(type, name [, feat [, mask]])``, where:" +msgstr "" + +#: ../Doc/library/socket.rst:140 +msgid "" +"*type* is the algorithm type as string, e.g. ``aead``, ``hash``, " +"``skcipher`` or ``rng``." +msgstr "" + +#: ../Doc/library/socket.rst:143 +msgid "" +"*name* is the algorithm name and operation mode as string, e.g. ``sha256``, " +"``hmac(sha256)``, ``cbc(aes)`` or ``drbg_nopr_ctr_aes256``." +msgstr "" + +#: ../Doc/library/socket.rst:146 +msgid "*feat* and *mask* are unsigned 32bit integers." +msgstr "" + +#: ../Doc/library/socket.rst:148 +msgid "" +"Availability Linux 2.6.38, some algorithm types require more recent Kernels." +msgstr "" + +#: ../Doc/library/socket.rst:152 +msgid "" +"Certain other address families (:const:`AF_PACKET`, :const:`AF_CAN`) support " +"specific representations." +msgstr "" + +#: ../Doc/library/socket.rst:157 +msgid "" +"For IPv4 addresses, two special forms are accepted instead of a host " +"address: the empty string represents :const:`INADDR_ANY`, and the string " +"``''`` represents :const:`INADDR_BROADCAST`. This behavior is " +"not compatible with IPv6, therefore, you may want to avoid these if you " +"intend to support IPv6 with your Python programs." +msgstr "" + +#: ../Doc/library/socket.rst:163 +msgid "" +"If you use a hostname in the *host* portion of IPv4/v6 socket address, the " +"program may show a nondeterministic behavior, as Python uses the first " +"address returned from the DNS resolution. The socket address will be " +"resolved differently into an actual IPv4/v6 address, depending on the " +"results from DNS resolution and/or the host configuration. For " +"deterministic behavior use a numeric address in *host* portion." +msgstr "" + +#: ../Doc/library/socket.rst:170 +msgid "" +"All errors raise exceptions. The normal exceptions for invalid argument " +"types and out-of-memory conditions can be raised; starting from Python 3.3, " +"errors related to socket or address semantics raise :exc:`OSError` or one of " +"its subclasses (they used to raise :exc:`socket.error`)." +msgstr "" + +#: ../Doc/library/socket.rst:175 +msgid "" +"Non-blocking mode is supported through :meth:`~socket.setblocking`. A " +"generalization of this based on timeouts is supported through :meth:`~socket." +"settimeout`." +msgstr "" + +#: ../Doc/library/socket.rst:183 +msgid "The module :mod:`socket` exports the following elements." +msgstr "" + +#: ../Doc/library/socket.rst:199 +msgid "" +"A subclass of :exc:`OSError`, this exception is raised for address-related " +"errors, i.e. for functions that use *h_errno* in the POSIX C API, including :" +"func:`gethostbyname_ex` and :func:`gethostbyaddr`. The accompanying value is " +"a pair ``(h_errno, string)`` representing an error returned by a library " +"call. *h_errno* is a numeric value, while *string* represents the " +"description of *h_errno*, as returned by the :c:func:`hstrerror` C function." +msgstr "" + +#: ../Doc/library/socket.rst:207 ../Doc/library/socket.rst:220 +#: ../Doc/library/socket.rst:231 +msgid "This class was made a subclass of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/socket.rst:212 +msgid "" +"A subclass of :exc:`OSError`, this exception is raised for address-related " +"errors by :func:`getaddrinfo` and :func:`getnameinfo`. The accompanying " +"value is a pair ``(error, string)`` representing an error returned by a " +"library call. *string* represents the description of *error*, as returned " +"by the :c:func:`gai_strerror` C function. The numeric *error* value will " +"match one of the :const:`EAI_\\*` constants defined in this module." +msgstr "" + +#: ../Doc/library/socket.rst:225 +msgid "" +"A subclass of :exc:`OSError`, this exception is raised when a timeout occurs " +"on a socket which has had timeouts enabled via a prior call to :meth:" +"`~socket.settimeout` (or implicitly through :func:`~socket." +"setdefaulttimeout`). The accompanying value is a string whose value is " +"currently always \"timed out\"." +msgstr "" + +#: ../Doc/library/socket.rst:238 +msgid "" +"The AF_* and SOCK_* constants are now :class:`AddressFamily` and :class:" +"`SocketKind` :class:`.IntEnum` collections." +msgstr "" + +#: ../Doc/library/socket.rst:247 +msgid "" +"These constants represent the address (and protocol) families, used for the " +"first argument to :func:`.socket`. If the :const:`AF_UNIX` constant is not " +"defined then this protocol is unsupported. More constants may be available " +"depending on the system." +msgstr "" + +#: ../Doc/library/socket.rst:259 +msgid "" +"These constants represent the socket types, used for the second argument to :" +"func:`.socket`. More constants may be available depending on the system. " +"(Only :const:`SOCK_STREAM` and :const:`SOCK_DGRAM` appear to be generally " +"useful.)" +msgstr "" + +#: ../Doc/library/socket.rst:267 +msgid "" +"These two constants, if defined, can be combined with the socket types and " +"allow you to set some flags atomically (thus avoiding possible race " +"conditions and the need for separate calls)." +msgstr "" + +#: ../Doc/library/socket.rst:273 +msgid "" +"`Secure File Descriptor Handling `_ for a more thorough explanation." +msgstr "" + +#: ../Doc/library/socket.rst:276 +msgid "Availability: Linux >= 2.6.27." +msgstr "" + +#: ../Doc/library/socket.rst:295 +msgid "" +"Many constants of these forms, documented in the Unix documentation on " +"sockets and/or the IP protocol, are also defined in the socket module. They " +"are generally used in arguments to the :meth:`setsockopt` and :meth:" +"`getsockopt` methods of socket objects. In most cases, only those symbols " +"that are defined in the Unix header files are defined; for a few symbols, " +"default values are provided." +msgstr "" + +#: ../Doc/library/socket.rst:302 +msgid "" +"``SO_DOMAIN``, ``SO_PROTOCOL``, ``SO_PEERSEC``, ``SO_PASSSEC`` were added." +msgstr "" + +#: ../Doc/library/socket.rst:311 ../Doc/library/socket.rst:346 +msgid "" +"Many constants of these forms, documented in the Linux documentation, are " +"also defined in the socket module." +msgstr "" + +#: ../Doc/library/socket.rst:314 ../Doc/library/socket.rst:325 +msgid "Availability: Linux >= 2.6.25." +msgstr "" + +#: ../Doc/library/socket.rst:321 +msgid "" +"CAN_BCM, in the CAN protocol family, is the broadcast manager (BCM) " +"protocol. Broadcast manager constants, documented in the Linux " +"documentation, are also defined in the socket module." +msgstr "" + +#: ../Doc/library/socket.rst:331 +msgid "" +"Enables CAN FD support in a CAN_RAW socket. This is disabled by default. " +"This allows your application to send both CAN and CAN FD frames; however, " +"you one must accept both CAN and CAN FD frames when reading from the socket." +msgstr "" + +#: ../Doc/library/socket.rst:335 +msgid "This constant is documented in the Linux documentation." +msgstr "" + +#: ../Doc/library/socket.rst:337 +msgid "Availability: Linux >= 3.6." +msgstr "" + +#: ../Doc/library/socket.rst:349 +msgid "Availability: Linux >= 2.6.30." +msgstr "" + +#: ../Doc/library/socket.rst:359 +msgid "" +"Constants for Windows' WSAIoctl(). The constants are used as arguments to " +"the :meth:`~socket.socket.ioctl` method of socket objects." +msgstr "" + +#: ../Doc/library/socket.rst:362 ../Doc/library/socket.rst:1039 +msgid "``SIO_LOOPBACK_FAST_PATH`` was added." +msgstr "" + +#: ../Doc/library/socket.rst:368 +msgid "" +"TIPC related constants, matching the ones exported by the C socket API. See " +"the TIPC documentation for more information." +msgstr "" + +#: ../Doc/library/socket.rst:375 +msgid "Constants for Linux Kernel cryptography." +msgstr "" + +#: ../Doc/library/socket.rst:377 +msgid "Availability: Linux >= 2.6.38." +msgstr "" + +#: ../Doc/library/socket.rst:383 +msgid "Availability: BSD, OSX." +msgstr "" + +#: ../Doc/library/socket.rst:389 +msgid "" +"This constant contains a boolean value which indicates if IPv6 is supported " +"on this platform." +msgstr "" + +#: ../Doc/library/socket.rst:395 +msgid "" +"These are string constants containing Bluetooth addresses with special " +"meanings. For example, :const:`BDADDR_ANY` can be used to indicate any " +"address when specifying the binding socket with :const:`BTPROTO_RFCOMM`." +msgstr "" + +#: ../Doc/library/socket.rst:404 +msgid "" +"For use with :const:`BTPROTO_HCI`. :const:`HCI_FILTER` is not available for " +"NetBSD or DragonFlyBSD. :const:`HCI_TIME_STAMP` and :const:`HCI_DATA_DIR` " +"are not available for FreeBSD, NetBSD, or DragonFlyBSD." +msgstr "" + +#: ../Doc/library/socket.rst:413 +msgid "Creating sockets" +msgstr "" + +#: ../Doc/library/socket.rst:415 +msgid "" +"The following functions all create :ref:`socket objects `." +msgstr "" + +#: ../Doc/library/socket.rst:420 +msgid "" +"Create a new socket using the given address family, socket type and protocol " +"number. The address family should be :const:`AF_INET` (the default), :const:" +"`AF_INET6`, :const:`AF_UNIX`, :const:`AF_CAN` or :const:`AF_RDS`. The socket " +"type should be :const:`SOCK_STREAM` (the default), :const:`SOCK_DGRAM`, :" +"const:`SOCK_RAW` or perhaps one of the other ``SOCK_`` constants. The " +"protocol number is usually zero and may be omitted or in the case where the " +"address family is :const:`AF_CAN` the protocol should be one of :const:" +"`CAN_RAW` or :const:`CAN_BCM`. If *fileno* is specified, the other " +"arguments are ignored, causing the socket with the specified file descriptor " +"to return. Unlike :func:`socket.fromfd`, *fileno* will return the same " +"socket and not a duplicate. This may help close a detached socket using :" +"meth:`socket.close()`." +msgstr "" + +#: ../Doc/library/socket.rst:433 ../Doc/library/socket.rst:500 +#: ../Doc/library/socket.rst:883 ../Doc/library/socket.rst:966 +msgid "The newly created socket is :ref:`non-inheritable `." +msgstr "" + +#: ../Doc/library/socket.rst:435 +msgid "The AF_CAN family was added. The AF_RDS family was added." +msgstr "" + +#: ../Doc/library/socket.rst:439 +msgid "The CAN_BCM protocol was added." +msgstr "" + +#: ../Doc/library/socket.rst:442 ../Doc/library/socket.rst:502 +msgid "The returned socket is now non-inheritable." +msgstr "" + +#: ../Doc/library/socket.rst:448 +msgid "" +"Build a pair of connected socket objects using the given address family, " +"socket type, and protocol number. Address family, socket type, and protocol " +"number are as for the :func:`.socket` function above. The default family is :" +"const:`AF_UNIX` if defined on the platform; otherwise, the default is :const:" +"`AF_INET`." +msgstr "" + +#: ../Doc/library/socket.rst:453 +msgid "The newly created sockets are :ref:`non-inheritable `." +msgstr "" + +#: ../Doc/library/socket.rst:455 +msgid "" +"The returned socket objects now support the whole socket API, rather than a " +"subset." +msgstr "" + +#: ../Doc/library/socket.rst:459 +msgid "The returned sockets are now non-inheritable." +msgstr "" + +#: ../Doc/library/socket.rst:462 +msgid "Windows support added." +msgstr "" + +#: ../Doc/library/socket.rst:468 +msgid "" +"Connect to a TCP service listening on the Internet *address* (a 2-tuple " +"``(host, port)``), and return the socket object. This is a higher-level " +"function than :meth:`socket.connect`: if *host* is a non-numeric hostname, " +"it will try to resolve it for both :data:`AF_INET` and :data:`AF_INET6`, and " +"then try to connect to all possible addresses in turn until a connection " +"succeeds. This makes it easy to write clients that are compatible to both " +"IPv4 and IPv6." +msgstr "" + +#: ../Doc/library/socket.rst:476 +msgid "" +"Passing the optional *timeout* parameter will set the timeout on the socket " +"instance before attempting to connect. If no *timeout* is supplied, the " +"global default timeout setting returned by :func:`getdefaulttimeout` is used." +msgstr "" + +#: ../Doc/library/socket.rst:481 +msgid "" +"If supplied, *source_address* must be a 2-tuple ``(host, port)`` for the " +"socket to bind to as its source address before connecting. If host or port " +"are '' or 0 respectively the OS default behavior will be used." +msgstr "" + +#: ../Doc/library/socket.rst:491 +msgid "" +"Duplicate the file descriptor *fd* (an integer as returned by a file " +"object's :meth:`fileno` method) and build a socket object from the result. " +"Address family, socket type and protocol number are as for the :func:`." +"socket` function above. The file descriptor should refer to a socket, but " +"this is not checked --- subsequent operations on the object may fail if the " +"file descriptor is invalid. This function is rarely needed, but can be used " +"to get or set socket options on a socket passed to a program as standard " +"input or output (such as a server started by the Unix inet daemon). The " +"socket is assumed to be in blocking mode." +msgstr "" + +#: ../Doc/library/socket.rst:508 +msgid "" +"Instantiate a socket from data obtained from the :meth:`socket.share` " +"method. The socket is assumed to be in blocking mode." +msgstr "" + +#: ../Doc/library/socket.rst:518 +msgid "" +"This is a Python type object that represents the socket object type. It is " +"the same as ``type(socket(...))``." +msgstr "" + +#: ../Doc/library/socket.rst:525 +msgid "The :mod:`socket` module also offers various network-related services:" +msgstr "" + +#: ../Doc/library/socket.rst:530 +msgid "" +"Translate the *host*/*port* argument into a sequence of 5-tuples that " +"contain all the necessary arguments for creating a socket connected to that " +"service. *host* is a domain name, a string representation of an IPv4/v6 " +"address or ``None``. *port* is a string service name such as ``'http'``, a " +"numeric port number or ``None``. By passing ``None`` as the value of *host* " +"and *port*, you can pass ``NULL`` to the underlying C API." +msgstr "" + +#: ../Doc/library/socket.rst:537 +msgid "" +"The *family*, *type* and *proto* arguments can be optionally specified in " +"order to narrow the list of addresses returned. Passing zero as a value for " +"each of these arguments selects the full range of results. The *flags* " +"argument can be one or several of the ``AI_*`` constants, and will influence " +"how results are computed and returned. For example, :const:`AI_NUMERICHOST` " +"will disable domain name resolution and will raise an error if *host* is a " +"domain name." +msgstr "" + +#: ../Doc/library/socket.rst:545 +msgid "The function returns a list of 5-tuples with the following structure:" +msgstr "" + +#: ../Doc/library/socket.rst:547 +msgid "``(family, type, proto, canonname, sockaddr)``" +msgstr "" + +#: ../Doc/library/socket.rst:549 +msgid "" +"In these tuples, *family*, *type*, *proto* are all integers and are meant to " +"be passed to the :func:`.socket` function. *canonname* will be a string " +"representing the canonical name of the *host* if :const:`AI_CANONNAME` is " +"part of the *flags* argument; else *canonname* will be empty. *sockaddr* is " +"a tuple describing a socket address, whose format depends on the returned " +"*family* (a ``(address, port)`` 2-tuple for :const:`AF_INET`, a ``(address, " +"port, flow info, scope id)`` 4-tuple for :const:`AF_INET6`), and is meant to " +"be passed to the :meth:`socket.connect` method." +msgstr "" + +#: ../Doc/library/socket.rst:559 +msgid "" +"The following example fetches address information for a hypothetical TCP " +"connection to ``example.org`` on port 80 (results may differ on your system " +"if IPv6 isn't enabled)::" +msgstr "" + +#: ../Doc/library/socket.rst:569 +msgid "parameters can now be passed using keyword arguments." +msgstr "" + +#: ../Doc/library/socket.rst:574 +msgid "" +"Return a fully qualified domain name for *name*. If *name* is omitted or " +"empty, it is interpreted as the local host. To find the fully qualified " +"name, the hostname returned by :func:`gethostbyaddr` is checked, followed by " +"aliases for the host, if available. The first name which includes a period " +"is selected. In case no fully qualified domain name is available, the " +"hostname as returned by :func:`gethostname` is returned." +msgstr "" + +#: ../Doc/library/socket.rst:584 +msgid "" +"Translate a host name to IPv4 address format. The IPv4 address is returned " +"as a string, such as ``'100.50.200.5'``. If the host name is an IPv4 " +"address itself it is returned unchanged. See :func:`gethostbyname_ex` for a " +"more complete interface. :func:`gethostbyname` does not support IPv6 name " +"resolution, and :func:`getaddrinfo` should be used instead for IPv4/v6 dual " +"stack support." +msgstr "" + +#: ../Doc/library/socket.rst:593 +msgid "" +"Translate a host name to IPv4 address format, extended interface. Return a " +"triple ``(hostname, aliaslist, ipaddrlist)`` where *hostname* is the primary " +"host name responding to the given *ip_address*, *aliaslist* is a (possibly " +"empty) list of alternative host names for the same address, and *ipaddrlist* " +"is a list of IPv4 addresses for the same interface on the same host (often " +"but not always a single address). :func:`gethostbyname_ex` does not support " +"IPv6 name resolution, and :func:`getaddrinfo` should be used instead for " +"IPv4/v6 dual stack support." +msgstr "" + +#: ../Doc/library/socket.rst:605 +msgid "" +"Return a string containing the hostname of the machine where the Python " +"interpreter is currently executing." +msgstr "" + +#: ../Doc/library/socket.rst:608 +msgid "" +"Note: :func:`gethostname` doesn't always return the fully qualified domain " +"name; use :func:`getfqdn` for that." +msgstr "" + +#: ../Doc/library/socket.rst:614 +msgid "" +"Return a triple ``(hostname, aliaslist, ipaddrlist)`` where *hostname* is " +"the primary host name responding to the given *ip_address*, *aliaslist* is a " +"(possibly empty) list of alternative host names for the same address, and " +"*ipaddrlist* is a list of IPv4/v6 addresses for the same interface on the " +"same host (most likely containing only a single address). To find the fully " +"qualified domain name, use the function :func:`getfqdn`. :func:" +"`gethostbyaddr` supports both IPv4 and IPv6." +msgstr "" + +#: ../Doc/library/socket.rst:625 +msgid "" +"Translate a socket address *sockaddr* into a 2-tuple ``(host, port)``. " +"Depending on the settings of *flags*, the result can contain a fully-" +"qualified domain name or numeric address representation in *host*. " +"Similarly, *port* can contain a string port name or a numeric port number." +msgstr "" + +#: ../Doc/library/socket.rst:633 +msgid "" +"Translate an Internet protocol name (for example, ``'icmp'``) to a constant " +"suitable for passing as the (optional) third argument to the :func:`.socket` " +"function. This is usually only needed for sockets opened in \"raw\" mode (:" +"const:`SOCK_RAW`); for the normal socket modes, the correct protocol is " +"chosen automatically if the protocol is omitted or zero." +msgstr "" + +#: ../Doc/library/socket.rst:642 +msgid "" +"Translate an Internet service name and protocol name to a port number for " +"that service. The optional protocol name, if given, should be ``'tcp'`` or " +"``'udp'``, otherwise any protocol will match." +msgstr "" + +#: ../Doc/library/socket.rst:649 +msgid "" +"Translate an Internet port number and protocol name to a service name for " +"that service. The optional protocol name, if given, should be ``'tcp'`` or " +"``'udp'``, otherwise any protocol will match." +msgstr "" + +#: ../Doc/library/socket.rst:656 +msgid "" +"Convert 32-bit positive integers from network to host byte order. On " +"machines where the host byte order is the same as network byte order, this " +"is a no-op; otherwise, it performs a 4-byte swap operation." +msgstr "" + +#: ../Doc/library/socket.rst:663 +msgid "" +"Convert 16-bit positive integers from network to host byte order. On " +"machines where the host byte order is the same as network byte order, this " +"is a no-op; otherwise, it performs a 2-byte swap operation." +msgstr "" + +#: ../Doc/library/socket.rst:670 +msgid "" +"Convert 32-bit positive integers from host to network byte order. On " +"machines where the host byte order is the same as network byte order, this " +"is a no-op; otherwise, it performs a 4-byte swap operation." +msgstr "" + +#: ../Doc/library/socket.rst:677 +msgid "" +"Convert 16-bit positive integers from host to network byte order. On " +"machines where the host byte order is the same as network byte order, this " +"is a no-op; otherwise, it performs a 2-byte swap operation." +msgstr "" + +#: ../Doc/library/socket.rst:684 +msgid "" +"Convert an IPv4 address from dotted-quad string format (for example, " +"'123.45.67.89') to 32-bit packed binary format, as a bytes object four " +"characters in length. This is useful when conversing with a program that " +"uses the standard C library and needs objects of type :c:type:`struct " +"in_addr`, which is the C type for the 32-bit packed binary this function " +"returns." +msgstr "" + +#: ../Doc/library/socket.rst:690 +msgid "" +":func:`inet_aton` also accepts strings with less than three dots; see the " +"Unix manual page :manpage:`inet(3)` for details." +msgstr "" + +#: ../Doc/library/socket.rst:693 +msgid "" +"If the IPv4 address string passed to this function is invalid, :exc:" +"`OSError` will be raised. Note that exactly what is valid depends on the " +"underlying C implementation of :c:func:`inet_aton`." +msgstr "" + +#: ../Doc/library/socket.rst:697 +msgid "" +":func:`inet_aton` does not support IPv6, and :func:`inet_pton` should be " +"used instead for IPv4/v6 dual stack support." +msgstr "" + +#: ../Doc/library/socket.rst:703 +msgid "" +"Convert a 32-bit packed IPv4 address (a :term:`bytes-like object` four bytes " +"in length) to its standard dotted-quad string representation (for example, " +"'123.45.67.89'). This is useful when conversing with a program that uses " +"the standard C library and needs objects of type :c:type:`struct in_addr`, " +"which is the C type for the 32-bit packed binary data this function takes as " +"an argument." +msgstr "" + +#: ../Doc/library/socket.rst:710 +msgid "" +"If the byte sequence passed to this function is not exactly 4 bytes in " +"length, :exc:`OSError` will be raised. :func:`inet_ntoa` does not support " +"IPv6, and :func:`inet_ntop` should be used instead for IPv4/v6 dual stack " +"support." +msgstr "" + +#: ../Doc/library/socket.rst:721 +msgid "" +"Convert an IP address from its family-specific string format to a packed, " +"binary format. :func:`inet_pton` is useful when a library or network " +"protocol calls for an object of type :c:type:`struct in_addr` (similar to :" +"func:`inet_aton`) or :c:type:`struct in6_addr`." +msgstr "" + +#: ../Doc/library/socket.rst:726 +msgid "" +"Supported values for *address_family* are currently :const:`AF_INET` and :" +"const:`AF_INET6`. If the IP address string *ip_string* is invalid, :exc:" +"`OSError` will be raised. Note that exactly what is valid depends on both " +"the value of *address_family* and the underlying implementation of :c:func:" +"`inet_pton`." +msgstr "" + +#: ../Doc/library/socket.rst:732 ../Doc/library/socket.rst:752 +msgid "Availability: Unix (maybe not all platforms), Windows." +msgstr "" + +#: ../Doc/library/socket.rst:734 ../Doc/library/socket.rst:754 +#: ../Doc/library/subprocess.rst:1184 ../Doc/library/subprocess.rst:1200 +msgid "Windows support added" +msgstr "" + +#: ../Doc/library/socket.rst:740 +msgid "" +"Convert a packed IP address (a :term:`bytes-like object` of some number of " +"bytes) to its standard, family-specific string representation (for example, " +"``'7.10.0.5'`` or ``'5aef:2b::8'``). :func:`inet_ntop` is useful when a " +"library or network protocol returns an object of type :c:type:`struct " +"in_addr` (similar to :func:`inet_ntoa`) or :c:type:`struct in6_addr`." +msgstr "" + +#: ../Doc/library/socket.rst:747 +msgid "" +"Supported values for *address_family* are currently :const:`AF_INET` and :" +"const:`AF_INET6`. If the bytes object *packed_ip* is not the correct length " +"for the specified address family, :exc:`ValueError` will be raised. :exc:" +"`OSError` is raised for errors from the call to :func:`inet_ntop`." +msgstr "" + +#: ../Doc/library/socket.rst:769 +msgid "" +"Return the total length, without trailing padding, of an ancillary data item " +"with associated data of the given *length*. This value can often be used as " +"the buffer size for :meth:`~socket.recvmsg` to receive a single item of " +"ancillary data, but :rfc:`3542` requires portable applications to use :func:" +"`CMSG_SPACE` and thus include space for padding, even when the item will be " +"the last in the buffer. Raises :exc:`OverflowError` if *length* is outside " +"the permissible range of values." +msgstr "" + +#: ../Doc/library/socket.rst:778 ../Doc/library/socket.rst:799 +#: ../Doc/library/socket.rst:1170 ../Doc/library/socket.rst:1212 +#: ../Doc/library/socket.rst:1316 +msgid "Availability: most Unix platforms, possibly others." +msgstr "" + +#: ../Doc/library/socket.rst:785 +msgid "" +"Return the buffer size needed for :meth:`~socket.recvmsg` to receive an " +"ancillary data item with associated data of the given *length*, along with " +"any trailing padding. The buffer space needed to receive multiple items is " +"the sum of the :func:`CMSG_SPACE` values for their associated data lengths. " +"Raises :exc:`OverflowError` if *length* is outside the permissible range of " +"values." +msgstr "" + +#: ../Doc/library/socket.rst:793 +msgid "" +"Note that some systems might support ancillary data without providing this " +"function. Also note that setting the buffer size using the results of this " +"function may not precisely limit the amount of ancillary data that can be " +"received, since additional data may be able to fit into the padding area." +msgstr "" + +#: ../Doc/library/socket.rst:806 +msgid "" +"Return the default timeout in seconds (float) for new socket objects. A " +"value of ``None`` indicates that new socket objects have no timeout. When " +"the socket module is first imported, the default is ``None``." +msgstr "" + +#: ../Doc/library/socket.rst:813 +msgid "" +"Set the default timeout in seconds (float) for new socket objects. When the " +"socket module is first imported, the default is ``None``. See :meth:" +"`~socket.settimeout` for possible values and their respective meanings." +msgstr "" + +#: ../Doc/library/socket.rst:821 +msgid "" +"Set the machine's hostname to *name*. This will raise an :exc:`OSError` if " +"you don't have enough rights." +msgstr "" + +#: ../Doc/library/socket.rst:831 +msgid "" +"Return a list of network interface information (index int, name string) " +"tuples. :exc:`OSError` if the system call fails." +msgstr "" + +#: ../Doc/library/socket.rst:842 +msgid "" +"Return a network interface index number corresponding to an interface name. :" +"exc:`OSError` if no interface with the given name exists." +msgstr "" + +#: ../Doc/library/socket.rst:853 +msgid "" +"Return a network interface name corresponding to an interface index number. :" +"exc:`OSError` if no interface with the given index exists." +msgstr "" + +#: ../Doc/library/socket.rst:865 +msgid "Socket Objects" +msgstr "" + +#: ../Doc/library/socket.rst:867 +msgid "" +"Socket objects have the following methods. Except for :meth:`~socket." +"makefile`, these correspond to Unix system calls applicable to sockets." +msgstr "" + +#: ../Doc/library/socket.rst:871 +msgid "" +"Support for the :term:`context manager` protocol was added. Exiting the " +"context manager is equivalent to calling :meth:`~socket.close`." +msgstr "" + +#: ../Doc/library/socket.rst:878 +msgid "" +"Accept a connection. The socket must be bound to an address and listening " +"for connections. The return value is a pair ``(conn, address)`` where *conn* " +"is a *new* socket object usable to send and receive data on the connection, " +"and *address* is the address bound to the socket on the other end of the " +"connection." +msgstr "" + +#: ../Doc/library/socket.rst:885 ../Doc/library/socket.rst:968 +msgid "The socket is now non-inheritable." +msgstr "" + +#: ../Doc/library/socket.rst:888 ../Doc/library/socket.rst:1089 +#: ../Doc/library/socket.rst:1103 ../Doc/library/socket.rst:1174 +#: ../Doc/library/socket.rst:1245 ../Doc/library/socket.rst:1264 +#: ../Doc/library/socket.rst:1279 ../Doc/library/socket.rst:1320 +msgid "" +"If the system call is interrupted and the signal handler does not raise an " +"exception, the method now retries the system call instead of raising an :exc:" +"`InterruptedError` exception (see :pep:`475` for the rationale)." +msgstr "" + +#: ../Doc/library/socket.rst:896 +msgid "" +"Bind the socket to *address*. The socket must not already be bound. (The " +"format of *address* depends on the address family --- see above.)" +msgstr "" + +#: ../Doc/library/socket.rst:902 +msgid "" +"Mark the socket closed. The underlying system resource (e.g. a file " +"descriptor) is also closed when all file objects from :meth:`makefile()` are " +"closed. Once that happens, all future operations on the socket object will " +"fail. The remote end will receive no more data (after queued data is " +"flushed)." +msgstr "" + +#: ../Doc/library/socket.rst:908 +msgid "" +"Sockets are automatically closed when they are garbage-collected, but it is " +"recommended to :meth:`close` them explicitly, or to use a :keyword:`with` " +"statement around them." +msgstr "" + +#: ../Doc/library/socket.rst:912 +msgid "" +":exc:`OSError` is now raised if an error occurs when the underlying :c:func:" +"`close` call is made." +msgstr "" + +#: ../Doc/library/socket.rst:918 +msgid "" +":meth:`close()` releases the resource associated with a connection but does " +"not necessarily close the connection immediately. If you want to close the " +"connection in a timely fashion, call :meth:`shutdown()` before :meth:" +"`close()`." +msgstr "" + +#: ../Doc/library/socket.rst:926 +msgid "" +"Connect to a remote socket at *address*. (The format of *address* depends on " +"the address family --- see above.)" +msgstr "" + +#: ../Doc/library/socket.rst:929 +msgid "" +"If the connection is interrupted by a signal, the method waits until the " +"connection completes, or raise a :exc:`socket.timeout` on timeout, if the " +"signal handler doesn't raise an exception and the socket is blocking or has " +"a timeout. For non-blocking sockets, the method raises an :exc:" +"`InterruptedError` exception if the connection is interrupted by a signal " +"(or the exception raised by the signal handler)." +msgstr "" + +#: ../Doc/library/socket.rst:936 +msgid "" +"The method now waits until the connection completes instead of raising an :" +"exc:`InterruptedError` exception if the connection is interrupted by a " +"signal, the signal handler doesn't raise an exception and the socket is " +"blocking or has a timeout (see the :pep:`475` for the rationale)." +msgstr "" + +#: ../Doc/library/socket.rst:945 +msgid "" +"Like ``connect(address)``, but return an error indicator instead of raising " +"an exception for errors returned by the C-level :c:func:`connect` call " +"(other problems, such as \"host not found,\" can still raise exceptions). " +"The error indicator is ``0`` if the operation succeeded, otherwise the value " +"of the :c:data:`errno` variable. This is useful to support, for example, " +"asynchronous connects." +msgstr "" + +#: ../Doc/library/socket.rst:955 +msgid "" +"Put the socket object into closed state without actually closing the " +"underlying file descriptor. The file descriptor is returned, and can be " +"reused for other purposes." +msgstr "" + +#: ../Doc/library/socket.rst:964 +msgid "Duplicate the socket." +msgstr "" + +#: ../Doc/library/socket.rst:974 +msgid "" +"Return the socket's file descriptor (a small integer), or -1 on failure. " +"This is useful with :func:`select.select`." +msgstr "" + +#: ../Doc/library/socket.rst:977 +msgid "" +"Under Windows the small integer returned by this method cannot be used where " +"a file descriptor can be used (such as :func:`os.fdopen`). Unix does not " +"have this limitation." +msgstr "" + +#: ../Doc/library/socket.rst:983 +msgid "" +"Get the :ref:`inheritable flag ` of the socket's file " +"descriptor or socket's handle: ``True`` if the socket can be inherited in " +"child processes, ``False`` if it cannot." +msgstr "" + +#: ../Doc/library/socket.rst:992 +msgid "" +"Return the remote address to which the socket is connected. This is useful " +"to find out the port number of a remote IPv4/v6 socket, for instance. (The " +"format of the address returned depends on the address family --- see " +"above.) On some systems this function is not supported." +msgstr "" + +#: ../Doc/library/socket.rst:1000 +msgid "" +"Return the socket's own address. This is useful to find out the port number " +"of an IPv4/v6 socket, for instance. (The format of the address returned " +"depends on the address family --- see above.)" +msgstr "" + +#: ../Doc/library/socket.rst:1007 +msgid "" +"Return the value of the given socket option (see the Unix man page :manpage:" +"`getsockopt(2)`). The needed symbolic constants (:const:`SO_\\*` etc.) are " +"defined in this module. If *buflen* is absent, an integer option is assumed " +"and its integer value is returned by the function. If *buflen* is present, " +"it specifies the maximum length of the buffer used to receive the option in, " +"and this buffer is returned as a bytes object. It is up to the caller to " +"decode the contents of the buffer (see the optional built-in module :mod:" +"`struct` for a way to decode C structures encoded as byte strings)." +msgstr "" + +#: ../Doc/library/socket.rst:1019 +msgid "" +"Return the timeout in seconds (float) associated with socket operations, or " +"``None`` if no timeout is set. This reflects the last call to :meth:" +"`setblocking` or :meth:`settimeout`." +msgstr "" + +#: ../Doc/library/socket.rst:1028 +msgid "" +"The :meth:`ioctl` method is a limited interface to the WSAIoctl system " +"interface. Please refer to the `Win32 documentation `_ for more information." +msgstr "" + +#: ../Doc/library/socket.rst:1033 +msgid "" +"On other platforms, the generic :func:`fcntl.fcntl` and :func:`fcntl.ioctl` " +"functions may be used; they accept a socket object as their first argument." +msgstr "" + +#: ../Doc/library/socket.rst:1036 +msgid "" +"Currently only the following control codes are supported: ``SIO_RCVALL``, " +"``SIO_KEEPALIVE_VALS``, and ``SIO_LOOPBACK_FAST_PATH``." +msgstr "" + +#: ../Doc/library/socket.rst:1044 +msgid "" +"Enable a server to accept connections. If *backlog* is specified, it must " +"be at least 0 (if it is lower, it is set to 0); it specifies the number of " +"unaccepted connections that the system will allow before refusing new " +"connections. If not specified, a default reasonable value is chosen." +msgstr "" + +#: ../Doc/library/socket.rst:1049 +msgid "The *backlog* parameter is now optional." +msgstr "" + +#: ../Doc/library/socket.rst:1057 +msgid "" +"Return a :term:`file object` associated with the socket. The exact returned " +"type depends on the arguments given to :meth:`makefile`. These arguments " +"are interpreted the same way as by the built-in :func:`open` function, " +"except the only supported *mode* values are ``'r'`` (default), ``'w'`` and " +"``'b'``." +msgstr "" + +#: ../Doc/library/socket.rst:1062 +msgid "" +"The socket must be in blocking mode; it can have a timeout, but the file " +"object's internal buffer may end up in an inconsistent state if a timeout " +"occurs." +msgstr "" + +#: ../Doc/library/socket.rst:1066 +msgid "" +"Closing the file object returned by :meth:`makefile` won't close the " +"original socket unless all other file objects have been closed and :meth:" +"`socket.close` has been called on the socket object." +msgstr "" + +#: ../Doc/library/socket.rst:1072 +msgid "" +"On Windows, the file-like object created by :meth:`makefile` cannot be used " +"where a file object with a file descriptor is expected, such as the stream " +"arguments of :meth:`subprocess.Popen`." +msgstr "" + +#: ../Doc/library/socket.rst:1079 +msgid "" +"Receive data from the socket. The return value is a bytes object " +"representing the data received. The maximum amount of data to be received " +"at once is specified by *bufsize*. See the Unix manual page :manpage:" +"`recv(2)` for the meaning of the optional argument *flags*; it defaults to " +"zero." +msgstr "" + +#: ../Doc/library/socket.rst:1086 +msgid "" +"For best match with hardware and network realities, the value of *bufsize* " +"should be a relatively small power of 2, for example, 4096." +msgstr "" + +#: ../Doc/library/socket.rst:1097 +msgid "" +"Receive data from the socket. The return value is a pair ``(bytes, " +"address)`` where *bytes* is a bytes object representing the data received " +"and *address* is the address of the socket sending the data. See the Unix " +"manual page :manpage:`recv(2)` for the meaning of the optional argument " +"*flags*; it defaults to zero. (The format of *address* depends on the " +"address family --- see above.)" +msgstr "" + +#: ../Doc/library/socket.rst:1111 +msgid "" +"Receive normal data (up to *bufsize* bytes) and ancillary data from the " +"socket. The *ancbufsize* argument sets the size in bytes of the internal " +"buffer used to receive the ancillary data; it defaults to 0, meaning that no " +"ancillary data will be received. Appropriate buffer sizes for ancillary " +"data can be calculated using :func:`CMSG_SPACE` or :func:`CMSG_LEN`, and " +"items which do not fit into the buffer might be truncated or discarded. The " +"*flags* argument defaults to 0 and has the same meaning as for :meth:`recv`." +msgstr "" + +#: ../Doc/library/socket.rst:1121 +msgid "" +"The return value is a 4-tuple: ``(data, ancdata, msg_flags, address)``. The " +"*data* item is a :class:`bytes` object holding the non-ancillary data " +"received. The *ancdata* item is a list of zero or more tuples " +"``(cmsg_level, cmsg_type, cmsg_data)`` representing the ancillary data " +"(control messages) received: *cmsg_level* and *cmsg_type* are integers " +"specifying the protocol level and protocol-specific type respectively, and " +"*cmsg_data* is a :class:`bytes` object holding the associated data. The " +"*msg_flags* item is the bitwise OR of various flags indicating conditions on " +"the received message; see your system documentation for details. If the " +"receiving socket is unconnected, *address* is the address of the sending " +"socket, if available; otherwise, its value is unspecified." +msgstr "" + +#: ../Doc/library/socket.rst:1135 +msgid "" +"On some systems, :meth:`sendmsg` and :meth:`recvmsg` can be used to pass " +"file descriptors between processes over an :const:`AF_UNIX` socket. When " +"this facility is used (it is often restricted to :const:`SOCK_STREAM` " +"sockets), :meth:`recvmsg` will return, in its ancillary data, items of the " +"form ``(socket.SOL_SOCKET, socket.SCM_RIGHTS, fds)``, where *fds* is a :" +"class:`bytes` object representing the new file descriptors as a binary array " +"of the native C :c:type:`int` type. If :meth:`recvmsg` raises an exception " +"after the system call returns, it will first attempt to close any file " +"descriptors received via this mechanism." +msgstr "" + +#: ../Doc/library/socket.rst:1146 +msgid "" +"Some systems do not indicate the truncated length of ancillary data items " +"which have been only partially received. If an item appears to extend " +"beyond the end of the buffer, :meth:`recvmsg` will issue a :exc:" +"`RuntimeWarning`, and will return the part of it which is inside the buffer " +"provided it has not been truncated before the start of its associated data." +msgstr "" + +#: ../Doc/library/socket.rst:1153 +msgid "" +"On systems which support the :const:`SCM_RIGHTS` mechanism, the following " +"function will receive up to *maxfds* file descriptors, returning the message " +"data and a list containing the descriptors (while ignoring unexpected " +"conditions such as unrelated control messages being received). See also :" +"meth:`sendmsg`. ::" +msgstr "" + +#: ../Doc/library/socket.rst:1182 +msgid "" +"Receive normal data and ancillary data from the socket, behaving as :meth:" +"`recvmsg` would, but scatter the non-ancillary data into a series of buffers " +"instead of returning a new bytes object. The *buffers* argument must be an " +"iterable of objects that export writable buffers (e.g. :class:`bytearray` " +"objects); these will be filled with successive chunks of the non-ancillary " +"data until it has all been written or there are no more buffers. The " +"operating system may set a limit (:func:`~os.sysconf` value ``SC_IOV_MAX``) " +"on the number of buffers that can be used. The *ancbufsize* and *flags* " +"arguments have the same meaning as for :meth:`recvmsg`." +msgstr "" + +#: ../Doc/library/socket.rst:1193 +msgid "" +"The return value is a 4-tuple: ``(nbytes, ancdata, msg_flags, address)``, " +"where *nbytes* is the total number of bytes of non-ancillary data written " +"into the buffers, and *ancdata*, *msg_flags* and *address* are the same as " +"for :meth:`recvmsg`." +msgstr "" + +#: ../Doc/library/socket.rst:1219 +msgid "" +"Receive data from the socket, writing it into *buffer* instead of creating a " +"new bytestring. The return value is a pair ``(nbytes, address)`` where " +"*nbytes* is the number of bytes received and *address* is the address of the " +"socket sending the data. See the Unix manual page :manpage:`recv(2)` for " +"the meaning of the optional argument *flags*; it defaults to zero. (The " +"format of *address* depends on the address family --- see above.)" +msgstr "" + +#: ../Doc/library/socket.rst:1229 +msgid "" +"Receive up to *nbytes* bytes from the socket, storing the data into a buffer " +"rather than creating a new bytestring. If *nbytes* is not specified (or 0), " +"receive up to the size available in the given buffer. Returns the number of " +"bytes received. See the Unix manual page :manpage:`recv(2)` for the meaning " +"of the optional argument *flags*; it defaults to zero." +msgstr "" + +#: ../Doc/library/socket.rst:1238 +msgid "" +"Send data to the socket. The socket must be connected to a remote socket. " +"The optional *flags* argument has the same meaning as for :meth:`recv` " +"above. Returns the number of bytes sent. Applications are responsible for " +"checking that all data has been sent; if only some of the data was " +"transmitted, the application needs to attempt delivery of the remaining " +"data. For further information on this topic, consult the :ref:`socket-howto`." +msgstr "" + +#: ../Doc/library/socket.rst:1253 +msgid "" +"Send data to the socket. The socket must be connected to a remote socket. " +"The optional *flags* argument has the same meaning as for :meth:`recv` " +"above. Unlike :meth:`send`, this method continues to send data from *bytes* " +"until either all data has been sent or an error occurs. ``None`` is " +"returned on success. On error, an exception is raised, and there is no way " +"to determine how much data, if any, was successfully sent." +msgstr "" + +#: ../Doc/library/socket.rst:1260 +msgid "" +"The socket timeout is no more reset each time data is sent successfully. The " +"socket timeout is now the maximum total duration to send all data." +msgstr "" + +#: ../Doc/library/socket.rst:1273 +msgid "" +"Send data to the socket. The socket should not be connected to a remote " +"socket, since the destination socket is specified by *address*. The " +"optional *flags* argument has the same meaning as for :meth:`recv` above. " +"Return the number of bytes sent. (The format of *address* depends on the " +"address family --- see above.)" +msgstr "" + +#: ../Doc/library/socket.rst:1287 +msgid "" +"Send normal and ancillary data to the socket, gathering the non-ancillary " +"data from a series of buffers and concatenating it into a single message. " +"The *buffers* argument specifies the non-ancillary data as an iterable of :" +"term:`bytes-like objects ` (e.g. :class:`bytes` objects); " +"the operating system may set a limit (:func:`~os.sysconf` value " +"``SC_IOV_MAX``) on the number of buffers that can be used. The *ancdata* " +"argument specifies the ancillary data (control messages) as an iterable of " +"zero or more tuples ``(cmsg_level, cmsg_type, cmsg_data)``, where " +"*cmsg_level* and *cmsg_type* are integers specifying the protocol level and " +"protocol-specific type respectively, and *cmsg_data* is a bytes-like object " +"holding the associated data. Note that some systems (in particular, systems " +"without :func:`CMSG_SPACE`) might support sending only one control message " +"per call. The *flags* argument defaults to 0 and has the same meaning as " +"for :meth:`send`. If *address* is supplied and not ``None``, it sets a " +"destination address for the message. The return value is the number of " +"bytes of non-ancillary data sent." +msgstr "" + +#: ../Doc/library/socket.rst:1307 +msgid "" +"The following function sends the list of file descriptors *fds* over an :" +"const:`AF_UNIX` socket, on systems which support the :const:`SCM_RIGHTS` " +"mechanism. See also :meth:`recvmsg`. ::" +msgstr "" + +#: ../Doc/library/socket.rst:1327 +msgid "" +"Specialized version of :meth:`~socket.sendmsg` for :const:`AF_ALG` socket. " +"Set mode, IV, AEAD associated data length and flags for :const:`AF_ALG` " +"socket." +msgstr "" + +#: ../Doc/library/socket.rst:1330 +msgid "Availability: Linux >= 2.6.38" +msgstr "" + +#: ../Doc/library/socket.rst:1336 +msgid "" +"Send a file until EOF is reached by using high-performance :mod:`os." +"sendfile` and return the total number of bytes which were sent. *file* must " +"be a regular file object opened in binary mode. If :mod:`os.sendfile` is not " +"available (e.g. Windows) or *file* is not a regular file :meth:`send` will " +"be used instead. *offset* tells from where to start reading the file. If " +"specified, *count* is the total number of bytes to transmit as opposed to " +"sending the file until EOF is reached. File position is updated on return or " +"also in case of error in which case :meth:`file.tell() ` can " +"be used to figure out the number of bytes which were sent. The socket must " +"be of :const:`SOCK_STREAM` type. Non- blocking sockets are not supported." +msgstr "" + +#: ../Doc/library/socket.rst:1352 +msgid "" +"Set the :ref:`inheritable flag ` of the socket's file " +"descriptor or socket's handle." +msgstr "" + +#: ../Doc/library/socket.rst:1360 +msgid "" +"Set blocking or non-blocking mode of the socket: if *flag* is false, the " +"socket is set to non-blocking, else to blocking mode." +msgstr "" + +#: ../Doc/library/socket.rst:1363 +msgid "" +"This method is a shorthand for certain :meth:`~socket.settimeout` calls:" +msgstr "" + +#: ../Doc/library/socket.rst:1365 +msgid "``sock.setblocking(True)`` is equivalent to ``sock.settimeout(None)``" +msgstr "" + +#: ../Doc/library/socket.rst:1367 +msgid "``sock.setblocking(False)`` is equivalent to ``sock.settimeout(0.0)``" +msgstr "" + +#: ../Doc/library/socket.rst:1372 +msgid "" +"Set a timeout on blocking socket operations. The *value* argument can be a " +"nonnegative floating point number expressing seconds, or ``None``. If a non-" +"zero value is given, subsequent socket operations will raise a :exc:" +"`timeout` exception if the timeout period *value* has elapsed before the " +"operation has completed. If zero is given, the socket is put in non-" +"blocking mode. If ``None`` is given, the socket is put in blocking mode." +msgstr "" + +#: ../Doc/library/socket.rst:1379 +msgid "" +"For further information, please consult the :ref:`notes on socket timeouts " +"`." +msgstr "" + +#: ../Doc/library/socket.rst:1388 +msgid "" +"Set the value of the given socket option (see the Unix manual page :manpage:" +"`setsockopt(2)`). The needed symbolic constants are defined in the :mod:" +"`socket` module (:const:`SO_\\*` etc.). The value can be an integer, None " +"or a :term:`bytes-like object` representing a buffer. In the later case it " +"is up to the caller to ensure that the bytestring contains the proper bits " +"(see the optional built-in module :mod:`struct` for a way to encode C " +"structures as bytestrings). When value is set to None, optlen argument is " +"required. It's equivalent to call setsockopt C function with optval=NULL and " +"optlen=optlen." +msgstr "" + +#: ../Doc/library/socket.rst:1402 +msgid "setsockopt(level, optname, None, optlen: int) form added." +msgstr "" + +#: ../Doc/library/socket.rst:1408 +msgid "" +"Shut down one or both halves of the connection. If *how* is :const:" +"`SHUT_RD`, further receives are disallowed. If *how* is :const:`SHUT_WR`, " +"further sends are disallowed. If *how* is :const:`SHUT_RDWR`, further sends " +"and receives are disallowed." +msgstr "" + +#: ../Doc/library/socket.rst:1416 +msgid "" +"Duplicate a socket and prepare it for sharing with a target process. The " +"target process must be provided with *process_id*. The resulting bytes " +"object can then be passed to the target process using some form of " +"interprocess communication and the socket can be recreated there using :func:" +"`fromshare`. Once this method has been called, it is safe to close the " +"socket since the operating system has already duplicated it for the target " +"process." +msgstr "" + +#: ../Doc/library/socket.rst:1428 +msgid "" +"Note that there are no methods :meth:`read` or :meth:`write`; use :meth:" +"`~socket.recv` and :meth:`~socket.send` without *flags* argument instead." +msgstr "" + +#: ../Doc/library/socket.rst:1431 +msgid "" +"Socket objects also have these (read-only) attributes that correspond to the " +"values given to the :class:`socket` constructor." +msgstr "" + +#: ../Doc/library/socket.rst:1437 +msgid "The socket family." +msgstr "" + +#: ../Doc/library/socket.rst:1442 +msgid "The socket type." +msgstr "" + +#: ../Doc/library/socket.rst:1447 +msgid "The socket protocol." +msgstr "" + +#: ../Doc/library/socket.rst:1454 +msgid "Notes on socket timeouts" +msgstr "" + +#: ../Doc/library/socket.rst:1456 +msgid "" +"A socket object can be in one of three modes: blocking, non-blocking, or " +"timeout. Sockets are by default always created in blocking mode, but this " +"can be changed by calling :func:`setdefaulttimeout`." +msgstr "" + +#: ../Doc/library/socket.rst:1460 +msgid "" +"In *blocking mode*, operations block until complete or the system returns an " +"error (such as connection timed out)." +msgstr "" + +#: ../Doc/library/socket.rst:1463 +msgid "" +"In *non-blocking mode*, operations fail (with an error that is unfortunately " +"system-dependent) if they cannot be completed immediately: functions from " +"the :mod:`select` can be used to know when and whether a socket is available " +"for reading or writing." +msgstr "" + +#: ../Doc/library/socket.rst:1468 +msgid "" +"In *timeout mode*, operations fail if they cannot be completed within the " +"timeout specified for the socket (they raise a :exc:`timeout` exception) or " +"if the system returns an error." +msgstr "" + +#: ../Doc/library/socket.rst:1473 +msgid "" +"At the operating system level, sockets in *timeout mode* are internally set " +"in non-blocking mode. Also, the blocking and timeout modes are shared " +"between file descriptors and socket objects that refer to the same network " +"endpoint. This implementation detail can have visible consequences if e.g. " +"you decide to use the :meth:`~socket.fileno()` of a socket." +msgstr "" + +#: ../Doc/library/socket.rst:1480 +msgid "Timeouts and the ``connect`` method" +msgstr "" + +#: ../Doc/library/socket.rst:1482 +msgid "" +"The :meth:`~socket.connect` operation is also subject to the timeout " +"setting, and in general it is recommended to call :meth:`~socket.settimeout` " +"before calling :meth:`~socket.connect` or pass a timeout parameter to :meth:" +"`create_connection`. However, the system network stack may also return a " +"connection timeout error of its own regardless of any Python socket timeout " +"setting." +msgstr "" + +#: ../Doc/library/socket.rst:1490 +msgid "Timeouts and the ``accept`` method" +msgstr "" + +#: ../Doc/library/socket.rst:1492 +msgid "" +"If :func:`getdefaulttimeout` is not :const:`None`, sockets returned by the :" +"meth:`~socket.accept` method inherit that timeout. Otherwise, the behaviour " +"depends on settings of the listening socket:" +msgstr "" + +#: ../Doc/library/socket.rst:1496 +msgid "" +"if the listening socket is in *blocking mode* or in *timeout mode*, the " +"socket returned by :meth:`~socket.accept` is in *blocking mode*;" +msgstr "" + +#: ../Doc/library/socket.rst:1499 +msgid "" +"if the listening socket is in *non-blocking mode*, whether the socket " +"returned by :meth:`~socket.accept` is in blocking or non-blocking mode is " +"operating system-dependent. If you want to ensure cross-platform behaviour, " +"it is recommended you manually override this setting." +msgstr "" + +#: ../Doc/library/socket.rst:1510 +msgid "" +"Here are four minimal example programs using the TCP/IP protocol: a server " +"that echoes all data that it receives back (servicing only one client), and " +"a client using it. Note that a server must perform the sequence :func:`." +"socket`, :meth:`~socket.bind`, :meth:`~socket.listen`, :meth:`~socket." +"accept` (possibly repeating the :meth:`~socket.accept` to service more than " +"one client), while a client only needs the sequence :func:`.socket`, :meth:" +"`~socket.connect`. Also note that the server does not :meth:`~socket." +"sendall`/:meth:`~socket.recv` on the socket it is listening on but on the " +"new socket returned by :meth:`~socket.accept`." +msgstr "" + +#: ../Doc/library/socket.rst:1520 +msgid "The first two examples support IPv4 only. ::" +msgstr "" + +#: ../Doc/library/socket.rst:1551 +msgid "" +"The next two examples are identical to the above two, but support both IPv4 " +"and IPv6. The server side will listen to the first address family available " +"(it should listen to both instead). On most of IPv6-ready systems, IPv6 will " +"take precedence and the server may not accept IPv4 traffic. The client side " +"will try to connect to the all addresses returned as a result of the name " +"resolution, and sends traffic to the first one connected successfully. ::" +msgstr "" + +#: ../Doc/library/socket.rst:1624 +msgid "" +"The next example shows how to write a very simple network sniffer with raw " +"sockets on Windows. The example requires administrator privileges to modify " +"the interface::" +msgstr "" + +#: ../Doc/library/socket.rst:1649 +msgid "" +"The last example shows how to use the socket interface to communicate to a " +"CAN network using the raw socket protocol. To use CAN with the broadcast " +"manager protocol instead, open a socket with::" +msgstr "" + +#: ../Doc/library/socket.rst:1655 +msgid "" +"After binding (:const:`CAN_RAW`) or connecting (:const:`CAN_BCM`) the " +"socket, you can use the :meth:`socket.send`, and the :meth:`socket.recv` " +"operations (and their counterparts) on the socket object as usual." +msgstr "" + +#: ../Doc/library/socket.rst:1659 +msgid "This example might require special privileges::" +msgstr "" + +#: ../Doc/library/socket.rst:1699 +msgid "" +"Running an example several times with too small delay between executions, " +"could lead to this error::" +msgstr "" + +#: ../Doc/library/socket.rst:1704 +msgid "" +"This is because the previous execution has left the socket in a " +"``TIME_WAIT`` state, and can't be immediately reused." +msgstr "" + +#: ../Doc/library/socket.rst:1707 +msgid "" +"There is a :mod:`socket` flag to set, in order to prevent this, :data:" +"`socket.SO_REUSEADDR`::" +msgstr "" + +#: ../Doc/library/socket.rst:1714 +msgid "" +"the :data:`SO_REUSEADDR` flag tells the kernel to reuse a local socket in " +"``TIME_WAIT`` state, without waiting for its natural timeout to expire." +msgstr "" + +#: ../Doc/library/socket.rst:1720 +msgid "" +"For an introduction to socket programming (in C), see the following papers:" +msgstr "" + +#: ../Doc/library/socket.rst:1722 +msgid "" +"*An Introductory 4.3BSD Interprocess Communication Tutorial*, by Stuart " +"Sechrest" +msgstr "" + +#: ../Doc/library/socket.rst:1724 +msgid "" +"*An Advanced 4.3BSD Interprocess Communication Tutorial*, by Samuel J. " +"Leffler et al," +msgstr "" + +#: ../Doc/library/socket.rst:1727 +msgid "" +"both in the UNIX Programmer's Manual, Supplementary Documents 1 (sections " +"PS1:7 and PS1:8). The platform-specific reference material for the various " +"socket-related system calls are also a valuable source of information on the " +"details of socket semantics. For Unix, refer to the manual pages; for " +"Windows, see the WinSock (or Winsock 2) specification. For IPv6-ready APIs, " +"readers may want to refer to :rfc:`3493` titled Basic Socket Interface " +"Extensions for IPv6." +msgstr "" + +#: ../Doc/library/socketserver.rst:2 +msgid ":mod:`socketserver` --- A framework for network servers" +msgstr "" + +#: ../Doc/library/socketserver.rst:7 +msgid "**Source code:** :source:`Lib/socketserver.py`" +msgstr "" + +#: ../Doc/library/socketserver.rst:11 +msgid "" +"The :mod:`socketserver` module simplifies the task of writing network " +"servers." +msgstr "" + +#: ../Doc/library/socketserver.rst:13 +msgid "There are four basic concrete server classes:" +msgstr "" + +#: ../Doc/library/socketserver.rst:18 +msgid "" +"This uses the Internet TCP protocol, which provides for continuous streams " +"of data between the client and server. If *bind_and_activate* is true, the " +"constructor automatically attempts to invoke :meth:`~BaseServer.server_bind` " +"and :meth:`~BaseServer.server_activate`. The other parameters are passed to " +"the :class:`BaseServer` base class." +msgstr "" + +#: ../Doc/library/socketserver.rst:28 +msgid "" +"This uses datagrams, which are discrete packets of information that may " +"arrive out of order or be lost while in transit. The parameters are the " +"same as for :class:`TCPServer`." +msgstr "" + +#: ../Doc/library/socketserver.rst:36 +msgid "" +"These more infrequently used classes are similar to the TCP and UDP classes, " +"but use Unix domain sockets; they're not available on non-Unix platforms. " +"The parameters are the same as for :class:`TCPServer`." +msgstr "" + +#: ../Doc/library/socketserver.rst:42 +msgid "" +"These four classes process requests :dfn:`synchronously`; each request must " +"be completed before the next request can be started. This isn't suitable if " +"each request takes a long time to complete, because it requires a lot of " +"computation, or because it returns a lot of data which the client is slow to " +"process. The solution is to create a separate process or thread to handle " +"each request; the :class:`ForkingMixIn` and :class:`ThreadingMixIn` mix-in " +"classes can be used to support asynchronous behaviour." +msgstr "" + +#: ../Doc/library/socketserver.rst:50 +msgid "" +"Creating a server requires several steps. First, you must create a request " +"handler class by subclassing the :class:`BaseRequestHandler` class and " +"overriding its :meth:`~BaseRequestHandler.handle` method; this method will " +"process incoming requests. Second, you must instantiate one of the server " +"classes, passing it the server's address and the request handler class. It " +"is recommended to use the server in a :keyword:`with` statement. Then call " +"the :meth:`~BaseServer.handle_request` or :meth:`~BaseServer.serve_forever` " +"method of the server object to process one or many requests. Finally, call :" +"meth:`~BaseServer.server_close` to close the socket (unless you used a :" +"keyword:`with` statement)." +msgstr "" + +#: ../Doc/library/socketserver.rst:62 +msgid "" +"When inheriting from :class:`ThreadingMixIn` for threaded connection " +"behavior, you should explicitly declare how you want your threads to behave " +"on an abrupt shutdown. The :class:`ThreadingMixIn` class defines an " +"attribute *daemon_threads*, which indicates whether or not the server should " +"wait for thread termination. You should set the flag explicitly if you " +"would like threads to behave autonomously; the default is :const:`False`, " +"meaning that Python will not exit until all threads created by :class:" +"`ThreadingMixIn` have exited." +msgstr "" + +#: ../Doc/library/socketserver.rst:71 +msgid "" +"Server classes have the same external methods and attributes, no matter what " +"network protocol they use." +msgstr "" + +#: ../Doc/library/socketserver.rst:76 +msgid "Server Creation Notes" +msgstr "" + +#: ../Doc/library/socketserver.rst:78 +msgid "" +"There are five classes in an inheritance diagram, four of which represent " +"synchronous servers of four types::" +msgstr "" + +#: ../Doc/library/socketserver.rst:95 +msgid "" +"Note that :class:`UnixDatagramServer` derives from :class:`UDPServer`, not " +"from :class:`UnixStreamServer` --- the only difference between an IP and a " +"Unix stream server is the address family, which is simply repeated in both " +"Unix server classes." +msgstr "" + +#: ../Doc/library/socketserver.rst:104 +msgid "" +"Forking and threading versions of each type of server can be created using " +"these mix-in classes. For instance, :class:`ThreadingUDPServer` is created " +"as follows::" +msgstr "" + +#: ../Doc/library/socketserver.rst:111 +msgid "" +"The mix-in class comes first, since it overrides a method defined in :class:" +"`UDPServer`. Setting the various attributes also changes the behavior of " +"the underlying server mechanism." +msgstr "" + +#: ../Doc/library/socketserver.rst:115 +msgid "" +":class:`ForkingMixIn` and the Forking classes mentioned below are only " +"available on POSIX platforms that support :func:`~os.fork`." +msgstr "" + +#: ../Doc/library/socketserver.rst:123 +msgid "These classes are pre-defined using the mix-in classes." +msgstr "" + +#: ../Doc/library/socketserver.rst:126 +msgid "" +"To implement a service, you must derive a class from :class:" +"`BaseRequestHandler` and redefine its :meth:`~BaseRequestHandler.handle` " +"method. You can then run various versions of the service by combining one of " +"the server classes with your request handler class. The request handler " +"class must be different for datagram or stream services. This can be hidden " +"by using the handler subclasses :class:`StreamRequestHandler` or :class:" +"`DatagramRequestHandler`." +msgstr "" + +#: ../Doc/library/socketserver.rst:134 +msgid "" +"Of course, you still have to use your head! For instance, it makes no sense " +"to use a forking server if the service contains state in memory that can be " +"modified by different requests, since the modifications in the child process " +"would never reach the initial state kept in the parent process and passed to " +"each child. In this case, you can use a threading server, but you will " +"probably have to use locks to protect the integrity of the shared data." +msgstr "" + +#: ../Doc/library/socketserver.rst:141 +msgid "" +"On the other hand, if you are building an HTTP server where all data is " +"stored externally (for instance, in the file system), a synchronous class " +"will essentially render the service \"deaf\" while one request is being " +"handled -- which may be for a very long time if a client is slow to receive " +"all the data it has requested. Here a threading or forking server is " +"appropriate." +msgstr "" + +#: ../Doc/library/socketserver.rst:147 +msgid "" +"In some cases, it may be appropriate to process part of a request " +"synchronously, but to finish processing in a forked child depending on the " +"request data. This can be implemented by using a synchronous server and " +"doing an explicit fork in the request handler class :meth:" +"`~BaseRequestHandler.handle` method." +msgstr "" + +#: ../Doc/library/socketserver.rst:152 +msgid "" +"Another approach to handling multiple simultaneous requests in an " +"environment that supports neither threads nor :func:`~os.fork` (or where " +"these are too expensive or inappropriate for the service) is to maintain an " +"explicit table of partially finished requests and to use :mod:`selectors` to " +"decide which request to work on next (or whether to handle a new incoming " +"request). This is particularly important for stream services where each " +"client can potentially be connected for a long time (if threads or " +"subprocesses cannot be used). See :mod:`asyncore` for another way to manage " +"this." +msgstr "" + +#: ../Doc/library/socketserver.rst:166 +msgid "Server Objects" +msgstr "" + +#: ../Doc/library/socketserver.rst:170 +msgid "" +"This is the superclass of all Server objects in the module. It defines the " +"interface, given below, but does not implement most of the methods, which is " +"done in subclasses. The two parameters are stored in the respective :attr:" +"`server_address` and :attr:`RequestHandlerClass` attributes." +msgstr "" + +#: ../Doc/library/socketserver.rst:178 +msgid "" +"Return an integer file descriptor for the socket on which the server is " +"listening. This function is most commonly passed to :mod:`selectors`, to " +"allow monitoring multiple servers in the same process." +msgstr "" + +#: ../Doc/library/socketserver.rst:185 +msgid "" +"Process a single request. This function calls the following methods in " +"order: :meth:`get_request`, :meth:`verify_request`, and :meth:" +"`process_request`. If the user-provided :meth:`~BaseRequestHandler.handle` " +"method of the handler class raises an exception, the server's :meth:" +"`handle_error` method will be called. If no request is received within :" +"attr:`timeout` seconds, :meth:`handle_timeout` will be called and :meth:" +"`handle_request` will return." +msgstr "" + +#: ../Doc/library/socketserver.rst:197 +msgid "" +"Handle requests until an explicit :meth:`shutdown` request. Poll for " +"shutdown every *poll_interval* seconds. Ignores the :attr:`timeout` " +"attribute. It also calls :meth:`service_actions`, which may be used by a " +"subclass or mixin to provide actions specific to a given service. For " +"example, the :class:`ForkingMixIn` class uses :meth:`service_actions` to " +"clean up zombie child processes." +msgstr "" + +#: ../Doc/library/socketserver.rst:205 +msgid "Added ``service_actions`` call to the ``serve_forever`` method." +msgstr "" + +#: ../Doc/library/socketserver.rst:211 +msgid "" +"This is called in the :meth:`serve_forever` loop. This method can be " +"overridden by subclasses or mixin classes to perform actions specific to a " +"given service, such as cleanup actions." +msgstr "" + +#: ../Doc/library/socketserver.rst:219 +msgid "Tell the :meth:`serve_forever` loop to stop and wait until it does." +msgstr "" + +#: ../Doc/library/socketserver.rst:224 +msgid "Clean up the server. May be overridden." +msgstr "" + +#: ../Doc/library/socketserver.rst:229 +msgid "" +"The family of protocols to which the server's socket belongs. Common " +"examples are :const:`socket.AF_INET` and :const:`socket.AF_UNIX`." +msgstr "" + +#: ../Doc/library/socketserver.rst:235 +msgid "" +"The user-provided request handler class; an instance of this class is " +"created for each request." +msgstr "" + +#: ../Doc/library/socketserver.rst:241 +msgid "" +"The address on which the server is listening. The format of addresses " +"varies depending on the protocol family; see the documentation for the :mod:" +"`socket` module for details. For Internet protocols, this is a tuple " +"containing a string giving the address, and an integer port number: " +"``('127.0.0.1', 80)``, for example." +msgstr "" + +#: ../Doc/library/socketserver.rst:250 +msgid "" +"The socket object on which the server will listen for incoming requests." +msgstr "" + +#: ../Doc/library/socketserver.rst:253 +msgid "The server classes support the following class variables:" +msgstr "" + +#: ../Doc/library/socketserver.rst:259 +msgid "" +"Whether the server will allow the reuse of an address. This defaults to :" +"const:`False`, and can be set in subclasses to change the policy." +msgstr "" + +#: ../Doc/library/socketserver.rst:265 +msgid "" +"The size of the request queue. If it takes a long time to process a single " +"request, any requests that arrive while the server is busy are placed into a " +"queue, up to :attr:`request_queue_size` requests. Once the queue is full, " +"further requests from clients will get a \"Connection denied\" error. The " +"default value is usually 5, but this can be overridden by subclasses." +msgstr "" + +#: ../Doc/library/socketserver.rst:274 +msgid "" +"The type of socket used by the server; :const:`socket.SOCK_STREAM` and :" +"const:`socket.SOCK_DGRAM` are two common values." +msgstr "" + +#: ../Doc/library/socketserver.rst:280 +msgid "" +"Timeout duration, measured in seconds, or :const:`None` if no timeout is " +"desired. If :meth:`handle_request` receives no incoming requests within the " +"timeout period, the :meth:`handle_timeout` method is called." +msgstr "" + +#: ../Doc/library/socketserver.rst:285 +msgid "" +"There are various server methods that can be overridden by subclasses of " +"base server classes like :class:`TCPServer`; these methods aren't useful to " +"external users of the server object." +msgstr "" + +#: ../Doc/library/socketserver.rst:294 +msgid "" +"Actually processes the request by instantiating :attr:`RequestHandlerClass` " +"and calling its :meth:`~BaseRequestHandler.handle` method." +msgstr "" + +#: ../Doc/library/socketserver.rst:300 +msgid "" +"Must accept a request from the socket, and return a 2-tuple containing the " +"*new* socket object to be used to communicate with the client, and the " +"client's address." +msgstr "" + +#: ../Doc/library/socketserver.rst:307 +msgid "" +"This function is called if the :meth:`~BaseRequestHandler.handle` method of " +"a :attr:`RequestHandlerClass` instance raises an exception. The default " +"action is to print the traceback to standard error and continue handling " +"further requests." +msgstr "" + +#: ../Doc/library/socketserver.rst:312 +msgid "Now only called for exceptions derived from the :exc:`Exception` class." +msgstr "" + +#: ../Doc/library/socketserver.rst:319 +msgid "" +"This function is called when the :attr:`timeout` attribute has been set to a " +"value other than :const:`None` and the timeout period has passed with no " +"requests being received. The default action for forking servers is to " +"collect the status of any child processes that have exited, while in " +"threading servers this method does nothing." +msgstr "" + +#: ../Doc/library/socketserver.rst:328 +msgid "" +"Calls :meth:`finish_request` to create an instance of the :attr:" +"`RequestHandlerClass`. If desired, this function can create a new process " +"or thread to handle the request; the :class:`ForkingMixIn` and :class:" +"`ThreadingMixIn` classes do this." +msgstr "" + +#: ../Doc/library/socketserver.rst:340 +msgid "" +"Called by the server's constructor to activate the server. The default " +"behavior for a TCP server just invokes :meth:`~socket.socket.listen` on the " +"server's socket. May be overridden." +msgstr "" + +#: ../Doc/library/socketserver.rst:347 +msgid "" +"Called by the server's constructor to bind the socket to the desired " +"address. May be overridden." +msgstr "" + +#: ../Doc/library/socketserver.rst:353 +msgid "" +"Must return a Boolean value; if the value is :const:`True`, the request will " +"be processed, and if it's :const:`False`, the request will be denied. This " +"function can be overridden to implement access controls for a server. The " +"default implementation always returns :const:`True`." +msgstr "" + +#: ../Doc/library/socketserver.rst:359 +msgid "" +"Support for the :term:`context manager` protocol was added. Exiting the " +"context manager is equivalent to calling :meth:`server_close`." +msgstr "" + +#: ../Doc/library/socketserver.rst:365 +msgid "Request Handler Objects" +msgstr "" + +#: ../Doc/library/socketserver.rst:369 +msgid "" +"This is the superclass of all request handler objects. It defines the " +"interface, given below. A concrete request handler subclass must define a " +"new :meth:`handle` method, and can override any of the other methods. A new " +"instance of the subclass is created for each request." +msgstr "" + +#: ../Doc/library/socketserver.rst:378 +msgid "" +"Called before the :meth:`handle` method to perform any initialization " +"actions required. The default implementation does nothing." +msgstr "" + +#: ../Doc/library/socketserver.rst:384 +msgid "" +"This function must do all the work required to service a request. The " +"default implementation does nothing. Several instance attributes are " +"available to it; the request is available as :attr:`self.request`; the " +"client address as :attr:`self.client_address`; and the server instance as :" +"attr:`self.server`, in case it needs access to per-server information." +msgstr "" + +#: ../Doc/library/socketserver.rst:390 +msgid "" +"The type of :attr:`self.request` is different for datagram or stream " +"services. For stream services, :attr:`self.request` is a socket object; for " +"datagram services, :attr:`self.request` is a pair of string and socket." +msgstr "" + +#: ../Doc/library/socketserver.rst:397 +msgid "" +"Called after the :meth:`handle` method to perform any clean-up actions " +"required. The default implementation does nothing. If :meth:`setup` raises " +"an exception, this function will not be called." +msgstr "" + +#: ../Doc/library/socketserver.rst:405 +msgid "" +"These :class:`BaseRequestHandler` subclasses override the :meth:" +"`~BaseRequestHandler.setup` and :meth:`~BaseRequestHandler.finish` methods, " +"and provide :attr:`self.rfile` and :attr:`self.wfile` attributes. The :attr:" +"`self.rfile` and :attr:`self.wfile` attributes can be read or written, " +"respectively, to get the request data or return data to the client." +msgstr "" + +#: ../Doc/library/socketserver.rst:412 +msgid "" +"The :attr:`rfile` attributes of both classes support the :class:`io." +"BufferedIOBase` readable interface, and :attr:`DatagramRequestHandler.wfile` " +"supports the :class:`io.BufferedIOBase` writable interface." +msgstr "" + +#: ../Doc/library/socketserver.rst:417 +msgid "" +":attr:`StreamRequestHandler.wfile` also supports the :class:`io." +"BufferedIOBase` writable interface." +msgstr "" + +#: ../Doc/library/socketserver.rst:426 +msgid ":class:`socketserver.TCPServer` Example" +msgstr "" + +#: ../Doc/library/socketserver.rst:428 ../Doc/library/socketserver.rst:527 +msgid "This is the server side::" +msgstr "" + +#: ../Doc/library/socketserver.rst:458 +msgid "" +"An alternative request handler class that makes use of streams (file-like " +"objects that simplify communication by providing the standard file " +"interface)::" +msgstr "" + +#: ../Doc/library/socketserver.rst:473 +msgid "" +"The difference is that the ``readline()`` call in the second handler will " +"call ``recv()`` multiple times until it encounters a newline character, " +"while the single ``recv()`` call in the first handler will just return what " +"has been sent from the client in one ``sendall()`` call." +msgstr "" + +#: ../Doc/library/socketserver.rst:479 ../Doc/library/socketserver.rst:551 +msgid "This is the client side::" +msgstr "" + +#: ../Doc/library/socketserver.rst:500 ../Doc/library/socketserver.rst:626 +msgid "The output of the example should look something like this:" +msgstr "" + +#: ../Doc/library/socketserver.rst:502 +msgid "Server:" +msgstr "" + +#: ../Doc/library/socketserver.rst:512 +msgid "Client:" +msgstr "" + +#: ../Doc/library/socketserver.rst:525 +msgid ":class:`socketserver.UDPServer` Example" +msgstr "" + +#: ../Doc/library/socketserver.rst:570 +msgid "" +"The output of the example should look exactly like for the TCP server " +"example." +msgstr "" + +#: ../Doc/library/socketserver.rst:574 +msgid "Asynchronous Mixins" +msgstr "" + +#: ../Doc/library/socketserver.rst:576 +msgid "" +"To build asynchronous handlers, use the :class:`ThreadingMixIn` and :class:" +"`ForkingMixIn` classes." +msgstr "" + +#: ../Doc/library/socketserver.rst:579 +msgid "An example for the :class:`ThreadingMixIn` class::" +msgstr "" + +#: ../Doc/library/socketserver.rst:637 +msgid "" +"The :class:`ForkingMixIn` class is used in the same way, except that the " +"server will spawn a new process for each request. Available only on POSIX " +"platforms that support :func:`~os.fork`." +msgstr "" + +#: ../Doc/library/spwd.rst:2 +msgid ":mod:`spwd` --- The shadow password database" +msgstr "" + +#: ../Doc/library/spwd.rst:10 +msgid "" +"This module provides access to the Unix shadow password database. It is " +"available on various Unix versions." +msgstr "" + +#: ../Doc/library/spwd.rst:13 +msgid "" +"You must have enough privileges to access the shadow password database (this " +"usually means you have to be root)." +msgstr "" + +#: ../Doc/library/spwd.rst:16 +msgid "" +"Shadow password database entries are reported as a tuple-like object, whose " +"attributes correspond to the members of the ``spwd`` structure (Attribute " +"field below, see ````):" +msgstr "" + +#: ../Doc/library/spwd.rst:23 +msgid "``sp_namp``" +msgstr "" + +#: ../Doc/library/spwd.rst:25 +msgid "``sp_pwdp``" +msgstr "" + +#: ../Doc/library/spwd.rst:25 +msgid "Encrypted password" +msgstr "" + +#: ../Doc/library/spwd.rst:27 +msgid "``sp_lstchg``" +msgstr "" + +#: ../Doc/library/spwd.rst:27 +msgid "Date of last change" +msgstr "" + +#: ../Doc/library/spwd.rst:29 +msgid "``sp_min``" +msgstr "" + +#: ../Doc/library/spwd.rst:29 +msgid "Minimal number of days between changes" +msgstr "" + +#: ../Doc/library/spwd.rst:32 +msgid "``sp_max``" +msgstr "" + +#: ../Doc/library/spwd.rst:32 +msgid "Maximum number of days between changes" +msgstr "" + +#: ../Doc/library/spwd.rst:35 +msgid "``sp_warn``" +msgstr "" + +#: ../Doc/library/spwd.rst:35 +msgid "Number of days before password expires to warn user about it" +msgstr "" + +#: ../Doc/library/spwd.rst:38 +msgid "``sp_inact``" +msgstr "" + +#: ../Doc/library/spwd.rst:38 +msgid "Number of days after password expires until account is disabled" +msgstr "" + +#: ../Doc/library/spwd.rst:42 ../Doc/library/time.rst:553 +msgid "7" +msgstr "" + +#: ../Doc/library/spwd.rst:42 +msgid "``sp_expire``" +msgstr "" + +#: ../Doc/library/spwd.rst:42 +msgid "Number of days since 1970-01-01 when account expires" +msgstr "" + +#: ../Doc/library/spwd.rst:45 +msgid "``sp_flag``" +msgstr "" + +#: ../Doc/library/spwd.rst:45 +msgid "Reserved" +msgstr "" + +#: ../Doc/library/spwd.rst:48 +msgid "" +"The sp_namp and sp_pwdp items are strings, all others are integers. :exc:" +"`KeyError` is raised if the entry asked for cannot be found." +msgstr "" + +#: ../Doc/library/spwd.rst:51 ../Doc/library/webbrowser.rst:51 +msgid "The following functions are defined:" +msgstr "" + +#: ../Doc/library/spwd.rst:56 +msgid "Return the shadow password database entry for the given user name." +msgstr "" + +#: ../Doc/library/spwd.rst:58 +msgid "" +"Raises a :exc:`PermissionError` instead of :exc:`KeyError` if the user " +"doesn't have privileges." +msgstr "" + +#: ../Doc/library/spwd.rst:64 +msgid "" +"Return a list of all available shadow password database entries, in " +"arbitrary order." +msgstr "" + +#: ../Doc/library/spwd.rst:74 +msgid "An interface to the normal password database, similar to this." +msgstr "" + +#: ../Doc/library/sqlite3.rst:2 +msgid ":mod:`sqlite3` --- DB-API 2.0 interface for SQLite databases" +msgstr "" + +#: ../Doc/library/sqlite3.rst:9 +msgid "**Source code:** :source:`Lib/sqlite3/`" +msgstr "" + +#: ../Doc/library/sqlite3.rst:13 +msgid "" +"SQLite is a C library that provides a lightweight disk-based database that " +"doesn't require a separate server process and allows accessing the database " +"using a nonstandard variant of the SQL query language. Some applications can " +"use SQLite for internal data storage. It's also possible to prototype an " +"application using SQLite and then port the code to a larger database such as " +"PostgreSQL or Oracle." +msgstr "" + +#: ../Doc/library/sqlite3.rst:20 +msgid "" +"The sqlite3 module was written by Gerhard Häring. It provides a SQL " +"interface compliant with the DB-API 2.0 specification described by :pep:" +"`249`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:23 +msgid "" +"To use the module, you must first create a :class:`Connection` object that " +"represents the database. Here the data will be stored in the :file:`example." +"db` file::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:30 +msgid "" +"You can also supply the special name ``:memory:`` to create a database in " +"RAM." +msgstr "" + +#: ../Doc/library/sqlite3.rst:32 +msgid "" +"Once you have a :class:`Connection`, you can create a :class:`Cursor` " +"object and call its :meth:`~Cursor.execute` method to perform SQL commands::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:51 +msgid "" +"The data you've saved is persistent and is available in subsequent sessions::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:57 +msgid "" +"Usually your SQL operations will need to use values from Python variables. " +"You shouldn't assemble your query using Python's string operations because " +"doing so is insecure; it makes your program vulnerable to an SQL injection " +"attack (see https://xkcd.com/327/ for humorous example of what can go wrong)." +msgstr "" + +#: ../Doc/library/sqlite3.rst:62 +msgid "" +"Instead, use the DB-API's parameter substitution. Put ``?`` as a " +"placeholder wherever you want to use a value, and then provide a tuple of " +"values as the second argument to the cursor's :meth:`~Cursor.execute` " +"method. (Other database modules may use a different placeholder, such as ``" +"%s`` or ``:1``.) For example::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:84 +msgid "" +"To retrieve data after executing a SELECT statement, you can either treat " +"the cursor as an :term:`iterator`, call the cursor's :meth:`~Cursor." +"fetchone` method to retrieve a single matching row, or call :meth:`~Cursor." +"fetchall` to get a list of the matching rows." +msgstr "" + +#: ../Doc/library/sqlite3.rst:89 +msgid "This example uses the iterator form::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:104 +msgid "https://github.com/ghaering/pysqlite" +msgstr "" + +#: ../Doc/library/sqlite3.rst:103 +msgid "" +"The pysqlite web page -- sqlite3 is developed externally under the name " +"\"pysqlite\"." +msgstr "" + +#: ../Doc/library/sqlite3.rst:108 +msgid "https://www.sqlite.org" +msgstr "" + +#: ../Doc/library/sqlite3.rst:107 +msgid "" +"The SQLite web page; the documentation describes the syntax and the " +"available data types for the supported SQL dialect." +msgstr "" + +#: ../Doc/library/sqlite3.rst:111 +msgid "http://www.w3schools.com/sql/" +msgstr "" + +#: ../Doc/library/sqlite3.rst:111 +msgid "Tutorial, reference and examples for learning SQL syntax." +msgstr "" + +#: ../Doc/library/sqlite3.rst:113 +msgid ":pep:`249` - Database API Specification 2.0" +msgstr "" + +#: ../Doc/library/sqlite3.rst:114 +msgid "PEP written by Marc-André Lemburg." +msgstr "" + +#: ../Doc/library/sqlite3.rst:120 +msgid "Module functions and constants" +msgstr "" + +#: ../Doc/library/sqlite3.rst:125 +msgid "" +"The version number of this module, as a string. This is not the version of " +"the SQLite library." +msgstr "" + +#: ../Doc/library/sqlite3.rst:131 +msgid "" +"The version number of this module, as a tuple of integers. This is not the " +"version of the SQLite library." +msgstr "" + +#: ../Doc/library/sqlite3.rst:137 +msgid "The version number of the run-time SQLite library, as a string." +msgstr "" + +#: ../Doc/library/sqlite3.rst:142 +msgid "" +"The version number of the run-time SQLite library, as a tuple of integers." +msgstr "" + +#: ../Doc/library/sqlite3.rst:147 ../Doc/library/sqlite3.rst:160 +msgid "" +"This constant is meant to be used with the *detect_types* parameter of the :" +"func:`connect` function." +msgstr "" + +#: ../Doc/library/sqlite3.rst:150 +msgid "" +"Setting it makes the :mod:`sqlite3` module parse the declared type for each " +"column it returns. It will parse out the first word of the declared type, " +"i. e. for \"integer primary key\", it will parse out \"integer\", or for " +"\"number(10)\" it will parse out \"number\". Then for that column, it will " +"look into the converters dictionary and use the converter function " +"registered for that type there." +msgstr "" + +#: ../Doc/library/sqlite3.rst:163 +msgid "" +"Setting this makes the SQLite interface parse the column name for each " +"column it returns. It will look for a string formed [mytype] in there, and " +"then decide that 'mytype' is the type of the column. It will try to find an " +"entry of 'mytype' in the converters dictionary and then use the converter " +"function found there to return the value. The column name found in :attr:" +"`Cursor.description` is only the first word of the column name, i. e. if " +"you use something like ``'as \"x [datetime]\"'`` in your SQL, then we will " +"parse out everything until the first blank for the column name: the column " +"name would simply be \"x\"." +msgstr "" + +#: ../Doc/library/sqlite3.rst:175 +msgid "" +"Opens a connection to the SQLite database file *database*. You can use ``\":" +"memory:\"`` to open a database connection to a database that resides in RAM " +"instead of on disk." +msgstr "" + +#: ../Doc/library/sqlite3.rst:179 +msgid "" +"When a database is accessed by multiple connections, and one of the " +"processes modifies the database, the SQLite database is locked until that " +"transaction is committed. The *timeout* parameter specifies how long the " +"connection should wait for the lock to go away until raising an exception. " +"The default for the timeout parameter is 5.0 (five seconds)." +msgstr "" + +#: ../Doc/library/sqlite3.rst:185 +msgid "" +"For the *isolation_level* parameter, please see the :attr:`~Connection." +"isolation_level` property of :class:`Connection` objects." +msgstr "" + +#: ../Doc/library/sqlite3.rst:188 +msgid "" +"SQLite natively supports only the types TEXT, INTEGER, REAL, BLOB and NULL. " +"If you want to use other types you must add support for them yourself. The " +"*detect_types* parameter and the using custom **converters** registered with " +"the module-level :func:`register_converter` function allow you to easily do " +"that." +msgstr "" + +#: ../Doc/library/sqlite3.rst:193 +msgid "" +"*detect_types* defaults to 0 (i. e. off, no type detection), you can set it " +"to any combination of :const:`PARSE_DECLTYPES` and :const:`PARSE_COLNAMES` " +"to turn type detection on." +msgstr "" + +#: ../Doc/library/sqlite3.rst:197 +msgid "" +"By default, *check_same_thread* is :const:`True` and only the creating " +"thread may use the connection. If set :const:`False`, the returned " +"connection may be shared across multiple threads. When using multiple " +"threads with the same connection writing operations should be serialized by " +"the user to avoid data corruption." +msgstr "" + +#: ../Doc/library/sqlite3.rst:202 +msgid "" +"By default, the :mod:`sqlite3` module uses its :class:`Connection` class for " +"the connect call. You can, however, subclass the :class:`Connection` class " +"and make :func:`connect` use your class instead by providing your class for " +"the *factory* parameter." +msgstr "" + +#: ../Doc/library/sqlite3.rst:207 +msgid "Consult the section :ref:`sqlite3-types` of this manual for details." +msgstr "" + +#: ../Doc/library/sqlite3.rst:209 +msgid "" +"The :mod:`sqlite3` module internally uses a statement cache to avoid SQL " +"parsing overhead. If you want to explicitly set the number of statements " +"that are cached for the connection, you can set the *cached_statements* " +"parameter. The currently implemented default is to cache 100 statements." +msgstr "" + +#: ../Doc/library/sqlite3.rst:214 +msgid "" +"If *uri* is true, *database* is interpreted as a URI. This allows you to " +"specify options. For example, to open a database in read-only mode you can " +"use::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:220 +msgid "" +"More information about this feature, including a list of recognized options, " +"can be found in the `SQLite URI documentation `_." +msgstr "" + +#: ../Doc/library/sqlite3.rst:223 +msgid "Added the *uri* parameter." +msgstr "" + +#: ../Doc/library/sqlite3.rst:229 +msgid "" +"Registers a callable to convert a bytestring from the database into a custom " +"Python type. The callable will be invoked for all database values that are " +"of the type *typename*. Confer the parameter *detect_types* of the :func:" +"`connect` function for how the type detection works. Note that the case of " +"*typename* and the name of the type in your query must match!" +msgstr "" + +#: ../Doc/library/sqlite3.rst:238 +msgid "" +"Registers a callable to convert the custom Python type *type* into one of " +"SQLite's supported types. The callable *callable* accepts as single " +"parameter the Python value, and must return a value of the following types: " +"int, float, str or bytes." +msgstr "" + +#: ../Doc/library/sqlite3.rst:246 +msgid "" +"Returns :const:`True` if the string *sql* contains one or more complete SQL " +"statements terminated by semicolons. It does not verify that the SQL is " +"syntactically correct, only that there are no unclosed string literals and " +"the statement is terminated by a semicolon." +msgstr "" + +#: ../Doc/library/sqlite3.rst:251 +msgid "" +"This can be used to build a shell for SQLite, as in the following example:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:259 +msgid "" +"By default you will not get any tracebacks in user-defined functions, " +"aggregates, converters, authorizer callbacks etc. If you want to debug them, " +"you can call this function with *flag* set to ``True``. Afterwards, you will " +"get tracebacks from callbacks on ``sys.stderr``. Use :const:`False` to " +"disable the feature again." +msgstr "" + +#: ../Doc/library/sqlite3.rst:273 +msgid "A SQLite database connection has the following attributes and methods:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:277 +msgid "" +"Get or set the current isolation level. :const:`None` for autocommit mode or " +"one of \"DEFERRED\", \"IMMEDIATE\" or \"EXCLUSIVE\". See section :ref:" +"`sqlite3-controlling-transactions` for a more detailed explanation." +msgstr "" + +#: ../Doc/library/sqlite3.rst:283 +msgid "" +":const:`True` if a transaction is active (there are uncommitted changes), :" +"const:`False` otherwise. Read-only attribute." +msgstr "" + +#: ../Doc/library/sqlite3.rst:290 +msgid "" +"The cursor method accepts a single optional parameter *factory*. If " +"supplied, this must be a callable returning an instance of :class:`Cursor` " +"or its subclasses." +msgstr "" + +#: ../Doc/library/sqlite3.rst:296 +msgid "" +"This method commits the current transaction. If you don't call this method, " +"anything you did since the last call to ``commit()`` is not visible from " +"other database connections. If you wonder why you don't see the data you've " +"written to the database, please check you didn't forget to call this method." +msgstr "" + +#: ../Doc/library/sqlite3.rst:303 +msgid "" +"This method rolls back any changes to the database since the last call to :" +"meth:`commit`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:308 +msgid "" +"This closes the database connection. Note that this does not automatically " +"call :meth:`commit`. If you just close your database connection without " +"calling :meth:`commit` first, your changes will be lost!" +msgstr "" + +#: ../Doc/library/sqlite3.rst:314 +msgid "" +"This is a nonstandard shortcut that creates a cursor object by calling the :" +"meth:`~Connection.cursor` method, calls the cursor's :meth:`~Cursor.execute` " +"method with the *parameters* given, and returns the cursor." +msgstr "" + +#: ../Doc/library/sqlite3.rst:321 +msgid "" +"This is a nonstandard shortcut that creates a cursor object by calling the :" +"meth:`~Connection.cursor` method, calls the cursor's :meth:`~Cursor." +"executemany` method with the *parameters* given, and returns the cursor." +msgstr "" + +#: ../Doc/library/sqlite3.rst:328 +msgid "" +"This is a nonstandard shortcut that creates a cursor object by calling the :" +"meth:`~Connection.cursor` method, calls the cursor's :meth:`~Cursor." +"executescript` method with the given *sql_script*, and returns the cursor." +msgstr "" + +#: ../Doc/library/sqlite3.rst:335 +msgid "" +"Creates a user-defined function that you can later use from within SQL " +"statements under the function name *name*. *num_params* is the number of " +"parameters the function accepts (if *num_params* is -1, the function may " +"take any number of arguments), and *func* is a Python callable that is " +"called as the SQL function." +msgstr "" + +#: ../Doc/library/sqlite3.rst:341 +msgid "" +"The function can return any of the types supported by SQLite: bytes, str, " +"int, float and None." +msgstr "" + +#: ../Doc/library/sqlite3.rst:351 +msgid "Creates a user-defined aggregate function." +msgstr "" + +#: ../Doc/library/sqlite3.rst:353 +msgid "" +"The aggregate class must implement a ``step`` method, which accepts the " +"number of parameters *num_params* (if *num_params* is -1, the function may " +"take any number of arguments), and a ``finalize`` method which will return " +"the final result of the aggregate." +msgstr "" + +#: ../Doc/library/sqlite3.rst:358 +msgid "" +"The ``finalize`` method can return any of the types supported by SQLite: " +"bytes, str, int, float and None." +msgstr "" + +#: ../Doc/library/sqlite3.rst:368 +msgid "" +"Creates a collation with the specified *name* and *callable*. The callable " +"will be passed two string arguments. It should return -1 if the first is " +"ordered lower than the second, 0 if they are ordered equal and 1 if the " +"first is ordered higher than the second. Note that this controls sorting " +"(ORDER BY in SQL) so your comparisons don't affect other SQL operations." +msgstr "" + +#: ../Doc/library/sqlite3.rst:374 +msgid "" +"Note that the callable will get its parameters as Python bytestrings, which " +"will normally be encoded in UTF-8." +msgstr "" + +#: ../Doc/library/sqlite3.rst:377 +msgid "" +"The following example shows a custom collation that sorts \"the wrong way\":" +msgstr "" + +#: ../Doc/library/sqlite3.rst:381 +msgid "" +"To remove a collation, call ``create_collation`` with None as callable::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:388 +msgid "" +"You can call this method from a different thread to abort any queries that " +"might be executing on the connection. The query will then abort and the " +"caller will get an exception." +msgstr "" + +#: ../Doc/library/sqlite3.rst:395 +msgid "" +"This routine registers a callback. The callback is invoked for each attempt " +"to access a column of a table in the database. The callback should return :" +"const:`SQLITE_OK` if access is allowed, :const:`SQLITE_DENY` if the entire " +"SQL statement should be aborted with an error and :const:`SQLITE_IGNORE` if " +"the column should be treated as a NULL value. These constants are available " +"in the :mod:`sqlite3` module." +msgstr "" + +#: ../Doc/library/sqlite3.rst:402 +msgid "" +"The first argument to the callback signifies what kind of operation is to be " +"authorized. The second and third argument will be arguments or :const:`None` " +"depending on the first argument. The 4th argument is the name of the " +"database (\"main\", \"temp\", etc.) if applicable. The 5th argument is the " +"name of the inner-most trigger or view that is responsible for the access " +"attempt or :const:`None` if this access attempt is directly from input SQL " +"code." +msgstr "" + +#: ../Doc/library/sqlite3.rst:409 +msgid "" +"Please consult the SQLite documentation about the possible values for the " +"first argument and the meaning of the second and third argument depending on " +"the first one. All necessary constants are available in the :mod:`sqlite3` " +"module." +msgstr "" + +#: ../Doc/library/sqlite3.rst:416 +msgid "" +"This routine registers a callback. The callback is invoked for every *n* " +"instructions of the SQLite virtual machine. This is useful if you want to " +"get called from SQLite during long-running operations, for example to update " +"a GUI." +msgstr "" + +#: ../Doc/library/sqlite3.rst:421 +msgid "" +"If you want to clear any previously installed progress handler, call the " +"method with :const:`None` for *handler*." +msgstr "" + +#: ../Doc/library/sqlite3.rst:427 +msgid "" +"Registers *trace_callback* to be called for each SQL statement that is " +"actually executed by the SQLite backend." +msgstr "" + +#: ../Doc/library/sqlite3.rst:430 +msgid "" +"The only argument passed to the callback is the statement (as string) that " +"is being executed. The return value of the callback is ignored. Note that " +"the backend does not only run statements passed to the :meth:`Cursor." +"execute` methods. Other sources include the transaction management of the " +"Python module and the execution of triggers defined in the current database." +msgstr "" + +#: ../Doc/library/sqlite3.rst:436 +msgid "" +"Passing :const:`None` as *trace_callback* will disable the trace callback." +msgstr "" + +#: ../Doc/library/sqlite3.rst:443 +msgid "" +"This routine allows/disallows the SQLite engine to load SQLite extensions " +"from shared libraries. SQLite extensions can define new functions, " +"aggregates or whole new virtual table implementations. One well-known " +"extension is the fulltext-search extension distributed with SQLite." +msgstr "" + +#: ../Doc/library/sqlite3.rst:448 ../Doc/library/sqlite3.rst:460 +msgid "Loadable extensions are disabled by default. See [#f1]_." +msgstr "" + +#: ../Doc/library/sqlite3.rst:456 +msgid "" +"This routine loads a SQLite extension from a shared library. You have to " +"enable extension loading with :meth:`enable_load_extension` before you can " +"use this routine." +msgstr "" + +#: ../Doc/library/sqlite3.rst:466 +msgid "" +"You can change this attribute to a callable that accepts the cursor and the " +"original row as a tuple and will return the real result row. This way, you " +"can implement more advanced ways of returning results, such as returning an " +"object that can also access columns by name." +msgstr "" + +#: ../Doc/library/sqlite3.rst:475 +msgid "" +"If returning a tuple doesn't suffice and you want name-based access to " +"columns, you should consider setting :attr:`row_factory` to the highly-" +"optimized :class:`sqlite3.Row` type. :class:`Row` provides both index-based " +"and case-insensitive name-based access to columns with almost no memory " +"overhead. It will probably be better than your own custom dictionary-based " +"approach or even a db_row based solution." +msgstr "" + +#: ../Doc/library/sqlite3.rst:487 +msgid "" +"Using this attribute you can control what objects are returned for the " +"``TEXT`` data type. By default, this attribute is set to :class:`str` and " +"the :mod:`sqlite3` module will return Unicode objects for ``TEXT``. If you " +"want to return bytestrings instead, you can set it to :class:`bytes`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:492 +msgid "" +"You can also set it to any other callable that accepts a single bytestring " +"parameter and returns the resulting object." +msgstr "" + +#: ../Doc/library/sqlite3.rst:495 +msgid "See the following example code for illustration:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:502 +msgid "" +"Returns the total number of database rows that have been modified, inserted, " +"or deleted since the database connection was opened." +msgstr "" + +#: ../Doc/library/sqlite3.rst:508 +msgid "" +"Returns an iterator to dump the database in an SQL text format. Useful when " +"saving an in-memory database for later restoration. This function provides " +"the same capabilities as the :kbd:`.dump` command in the :program:`sqlite3` " +"shell." +msgstr "" + +#: ../Doc/library/sqlite3.rst:527 +msgid "Cursor Objects" +msgstr "" + +#: ../Doc/library/sqlite3.rst:531 +msgid "A :class:`Cursor` instance has the following attributes and methods." +msgstr "" + +#: ../Doc/library/sqlite3.rst:535 +msgid "" +"Executes an SQL statement. The SQL statement may be parameterized (i. e. " +"placeholders instead of SQL literals). The :mod:`sqlite3` module supports " +"two kinds of placeholders: question marks (qmark style) and named " +"placeholders (named style)." +msgstr "" + +#: ../Doc/library/sqlite3.rst:540 +msgid "Here's an example of both styles:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:544 +msgid "" +":meth:`execute` will only execute a single SQL statement. If you try to " +"execute more than one statement with it, it will raise a :exc:`.Warning`. " +"Use :meth:`executescript` if you want to execute multiple SQL statements " +"with one call." +msgstr "" + +#: ../Doc/library/sqlite3.rst:552 +msgid "" +"Executes an SQL command against all parameter sequences or mappings found in " +"the sequence *seq_of_parameters*. The :mod:`sqlite3` module also allows " +"using an :term:`iterator` yielding parameters instead of a sequence." +msgstr "" + +#: ../Doc/library/sqlite3.rst:558 +msgid "Here's a shorter example using a :term:`generator`:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:565 +msgid "" +"This is a nonstandard convenience method for executing multiple SQL " +"statements at once. It issues a ``COMMIT`` statement first, then executes " +"the SQL script it gets as a parameter." +msgstr "" + +#: ../Doc/library/sqlite3.rst:569 +msgid "*sql_script* can be an instance of :class:`str`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:578 +msgid "" +"Fetches the next row of a query result set, returning a single sequence, or :" +"const:`None` when no more data is available." +msgstr "" + +#: ../Doc/library/sqlite3.rst:584 +msgid "" +"Fetches the next set of rows of a query result, returning a list. An empty " +"list is returned when no more rows are available." +msgstr "" + +#: ../Doc/library/sqlite3.rst:587 +msgid "" +"The number of rows to fetch per call is specified by the *size* parameter. " +"If it is not given, the cursor's arraysize determines the number of rows to " +"be fetched. The method should try to fetch as many rows as indicated by the " +"size parameter. If this is not possible due to the specified number of rows " +"not being available, fewer rows may be returned." +msgstr "" + +#: ../Doc/library/sqlite3.rst:593 +msgid "" +"Note there are performance considerations involved with the *size* " +"parameter. For optimal performance, it is usually best to use the arraysize " +"attribute. If the *size* parameter is used, then it is best for it to retain " +"the same value from one :meth:`fetchmany` call to the next." +msgstr "" + +#: ../Doc/library/sqlite3.rst:600 +msgid "" +"Fetches all (remaining) rows of a query result, returning a list. Note that " +"the cursor's arraysize attribute can affect the performance of this " +"operation. An empty list is returned when no rows are available." +msgstr "" + +#: ../Doc/library/sqlite3.rst:606 +msgid "Close the cursor now (rather than whenever ``__del__`` is called)." +msgstr "" + +#: ../Doc/library/sqlite3.rst:608 +msgid "" +"The cursor will be unusable from this point forward; a :exc:" +"`ProgrammingError` exception will be raised if any operation is attempted " +"with the cursor." +msgstr "" + +#: ../Doc/library/sqlite3.rst:613 +msgid "" +"Although the :class:`Cursor` class of the :mod:`sqlite3` module implements " +"this attribute, the database engine's own support for the determination of " +"\"rows affected\"/\"rows selected\" is quirky." +msgstr "" + +#: ../Doc/library/sqlite3.rst:617 +msgid "" +"For :meth:`executemany` statements, the number of modifications are summed " +"up into :attr:`rowcount`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:620 +msgid "" +"As required by the Python DB API Spec, the :attr:`rowcount` attribute \"is " +"-1 in case no ``executeXX()`` has been performed on the cursor or the " +"rowcount of the last operation is not determinable by the interface\". This " +"includes ``SELECT`` statements because we cannot determine the number of " +"rows a query produced until all rows were fetched." +msgstr "" + +#: ../Doc/library/sqlite3.rst:626 +msgid "" +"With SQLite versions before 3.6.5, :attr:`rowcount` is set to 0 if you make " +"a ``DELETE FROM table`` without any condition." +msgstr "" + +#: ../Doc/library/sqlite3.rst:631 +msgid "" +"This read-only attribute provides the rowid of the last modified row. It is " +"only set if you issued an ``INSERT`` or a ``REPLACE`` statement using the :" +"meth:`execute` method. For operations other than ``INSERT`` or ``REPLACE`` " +"or when :meth:`executemany` is called, :attr:`lastrowid` is set to :const:" +"`None`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:637 +msgid "" +"If the ``INSERT`` or ``REPLACE`` statement failed to insert the previous " +"successful rowid is returned." +msgstr "" + +#: ../Doc/library/sqlite3.rst:640 +msgid "Added support for the ``REPLACE`` statement." +msgstr "" + +#: ../Doc/library/sqlite3.rst:645 +msgid "" +"This read-only attribute provides the column names of the last query. To " +"remain compatible with the Python DB API, it returns a 7-tuple for each " +"column where the last six items of each tuple are :const:`None`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:649 +msgid "It is set for ``SELECT`` statements without any matching rows as well." +msgstr "" + +#: ../Doc/library/sqlite3.rst:653 +msgid "" +"This read-only attribute provides the SQLite database :class:`Connection` " +"used by the :class:`Cursor` object. A :class:`Cursor` object created by " +"calling :meth:`con.cursor() ` will have a :attr:" +"`connection` attribute that refers to *con*::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:666 +msgid "Row Objects" +msgstr "" + +#: ../Doc/library/sqlite3.rst:670 +msgid "" +"A :class:`Row` instance serves as a highly optimized :attr:`~Connection." +"row_factory` for :class:`Connection` objects. It tries to mimic a tuple in " +"most of its features." +msgstr "" + +#: ../Doc/library/sqlite3.rst:674 +msgid "" +"It supports mapping access by column name and index, iteration, " +"representation, equality testing and :func:`len`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:677 +msgid "" +"If two :class:`Row` objects have exactly the same columns and their members " +"are equal, they compare equal." +msgstr "" + +#: ../Doc/library/sqlite3.rst:682 +msgid "" +"This method returns a list of column names. Immediately after a query, it is " +"the first member of each tuple in :attr:`Cursor.description`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:685 +msgid "Added support of slicing." +msgstr "" + +#: ../Doc/library/sqlite3.rst:688 +msgid "Let's assume we initialize a table as in the example given above::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:700 +msgid "Now we plug :class:`Row` in::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:736 +msgid "A subclass of :exc:`Exception`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:745 +msgid "Exception raised for errors that are related to the database." +msgstr "" + +#: ../Doc/library/sqlite3.rst:749 +msgid "" +"Exception raised when the relational integrity of the database is affected, " +"e.g. a foreign key check fails. It is a subclass of :exc:`DatabaseError`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:754 +msgid "" +"Exception raised for programming errors, e.g. table not found or already " +"exists, syntax error in the SQL statement, wrong number of parameters " +"specified, etc. It is a subclass of :exc:`DatabaseError`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:762 +msgid "SQLite and Python types" +msgstr "" + +#: ../Doc/library/sqlite3.rst:768 +msgid "" +"SQLite natively supports the following types: ``NULL``, ``INTEGER``, " +"``REAL``, ``TEXT``, ``BLOB``." +msgstr "" + +#: ../Doc/library/sqlite3.rst:771 +msgid "" +"The following Python types can thus be sent to SQLite without any problem:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:774 ../Doc/library/sqlite3.rst:791 +msgid "SQLite type" +msgstr "" + +#: ../Doc/library/sqlite3.rst:776 ../Doc/library/sqlite3.rst:793 +#: ../Doc/library/urllib.parse.rst:107 ../Doc/library/urllib.parse.rst:109 +#: ../Doc/library/urllib.parse.rst:111 ../Doc/library/urllib.parse.rst:113 +#: ../Doc/library/urllib.parse.rst:225 ../Doc/library/urllib.parse.rst:227 +#: ../Doc/library/urllib.parse.rst:229 ../Doc/library/urllib.parse.rst:231 +msgid ":const:`None`" +msgstr "" + +#: ../Doc/library/sqlite3.rst:776 ../Doc/library/sqlite3.rst:793 +msgid "``NULL``" +msgstr "" + +#: ../Doc/library/sqlite3.rst:778 ../Doc/library/sqlite3.rst:795 +msgid ":class:`int`" +msgstr "" + +#: ../Doc/library/sqlite3.rst:778 ../Doc/library/sqlite3.rst:795 +msgid "``INTEGER``" +msgstr "" + +#: ../Doc/library/sqlite3.rst:780 ../Doc/library/sqlite3.rst:797 +msgid ":class:`float`" +msgstr "" + +#: ../Doc/library/sqlite3.rst:780 ../Doc/library/sqlite3.rst:797 +msgid "``REAL``" +msgstr "" + +#: ../Doc/library/sqlite3.rst:782 ../Doc/library/xmlrpc.client.rst:99 +msgid ":class:`str`" +msgstr "" + +#: ../Doc/library/sqlite3.rst:782 ../Doc/library/sqlite3.rst:799 +msgid "``TEXT``" +msgstr "" + +#: ../Doc/library/sqlite3.rst:784 ../Doc/library/sqlite3.rst:802 +msgid ":class:`bytes`" +msgstr "" + +#: ../Doc/library/sqlite3.rst:784 ../Doc/library/sqlite3.rst:802 +msgid "``BLOB``" +msgstr "" + +#: ../Doc/library/sqlite3.rst:788 +msgid "This is how SQLite types are converted to Python types by default:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:799 +msgid "depends on :attr:`~Connection.text_factory`, :class:`str` by default" +msgstr "" + +#: ../Doc/library/sqlite3.rst:805 +msgid "" +"The type system of the :mod:`sqlite3` module is extensible in two ways: you " +"can store additional Python types in a SQLite database via object " +"adaptation, and you can let the :mod:`sqlite3` module convert SQLite types " +"to different Python types via converters." +msgstr "" + +#: ../Doc/library/sqlite3.rst:812 +msgid "Using adapters to store additional Python types in SQLite databases" +msgstr "" + +#: ../Doc/library/sqlite3.rst:814 +msgid "" +"As described before, SQLite supports only a limited set of types natively. " +"To use other Python types with SQLite, you must **adapt** them to one of the " +"sqlite3 module's supported types for SQLite: one of NoneType, int, float, " +"str, bytes." +msgstr "" + +#: ../Doc/library/sqlite3.rst:819 +msgid "" +"There are two ways to enable the :mod:`sqlite3` module to adapt a custom " +"Python type to one of the supported ones." +msgstr "" + +#: ../Doc/library/sqlite3.rst:824 +msgid "Letting your object adapt itself" +msgstr "" + +#: ../Doc/library/sqlite3.rst:826 +msgid "" +"This is a good approach if you write the class yourself. Let's suppose you " +"have a class like this::" +msgstr "" + +#: ../Doc/library/sqlite3.rst:833 +msgid "" +"Now you want to store the point in a single SQLite column. First you'll " +"have to choose one of the supported types first to be used for representing " +"the point. Let's just use str and separate the coordinates using a " +"semicolon. Then you need to give your class a method ``__conform__(self, " +"protocol)`` which must return the converted value. The parameter *protocol* " +"will be :class:`PrepareProtocol`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:843 +msgid "Registering an adapter callable" +msgstr "" + +#: ../Doc/library/sqlite3.rst:845 +msgid "" +"The other possibility is to create a function that converts the type to the " +"string representation and register the function with :meth:" +"`register_adapter`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:850 +msgid "" +"The :mod:`sqlite3` module has two default adapters for Python's built-in :" +"class:`datetime.date` and :class:`datetime.datetime` types. Now let's " +"suppose we want to store :class:`datetime.datetime` objects not in ISO " +"representation, but as a Unix timestamp." +msgstr "" + +#: ../Doc/library/sqlite3.rst:859 +msgid "Converting SQLite values to custom Python types" +msgstr "" + +#: ../Doc/library/sqlite3.rst:861 +msgid "" +"Writing an adapter lets you send custom Python types to SQLite. But to make " +"it really useful we need to make the Python to SQLite to Python roundtrip " +"work." +msgstr "" + +#: ../Doc/library/sqlite3.rst:864 +msgid "Enter converters." +msgstr "" + +#: ../Doc/library/sqlite3.rst:866 +msgid "" +"Let's go back to the :class:`Point` class. We stored the x and y coordinates " +"separated via semicolons as strings in SQLite." +msgstr "" + +#: ../Doc/library/sqlite3.rst:869 +msgid "" +"First, we'll define a converter function that accepts the string as a " +"parameter and constructs a :class:`Point` object from it." +msgstr "" + +#: ../Doc/library/sqlite3.rst:874 +msgid "" +"Converter functions **always** get called with a :class:`bytes` object, no " +"matter under which data type you sent the value to SQLite." +msgstr "" + +#: ../Doc/library/sqlite3.rst:883 +msgid "" +"Now you need to make the :mod:`sqlite3` module know that what you select " +"from the database is actually a point. There are two ways of doing this:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:886 +msgid "Implicitly via the declared type" +msgstr "" + +#: ../Doc/library/sqlite3.rst:888 +msgid "Explicitly via the column name" +msgstr "" + +#: ../Doc/library/sqlite3.rst:890 +msgid "" +"Both ways are described in section :ref:`sqlite3-module-contents`, in the " +"entries for the constants :const:`PARSE_DECLTYPES` and :const:" +"`PARSE_COLNAMES`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:893 +msgid "The following example illustrates both approaches." +msgstr "" + +#: ../Doc/library/sqlite3.rst:899 +msgid "Default adapters and converters" +msgstr "" + +#: ../Doc/library/sqlite3.rst:901 +msgid "" +"There are default adapters for the date and datetime types in the datetime " +"module. They will be sent as ISO dates/ISO timestamps to SQLite." +msgstr "" + +#: ../Doc/library/sqlite3.rst:904 +msgid "" +"The default converters are registered under the name \"date\" for :class:" +"`datetime.date` and under the name \"timestamp\" for :class:`datetime." +"datetime`." +msgstr "" + +#: ../Doc/library/sqlite3.rst:908 +msgid "" +"This way, you can use date/timestamps from Python without any additional " +"fiddling in most cases. The format of the adapters is also compatible with " +"the experimental SQLite date/time functions." +msgstr "" + +#: ../Doc/library/sqlite3.rst:912 +msgid "The following example demonstrates this." +msgstr "" + +#: ../Doc/library/sqlite3.rst:916 +msgid "" +"If a timestamp stored in SQLite has a fractional part longer than 6 numbers, " +"its value will be truncated to microsecond precision by the timestamp " +"converter." +msgstr "" + +#: ../Doc/library/sqlite3.rst:924 +msgid "Controlling Transactions" +msgstr "" + +#: ../Doc/library/sqlite3.rst:926 +msgid "" +"By default, the :mod:`sqlite3` module opens transactions implicitly before a " +"Data Modification Language (DML) statement (i.e. ``INSERT``/``UPDATE``/" +"``DELETE``/``REPLACE``)." +msgstr "" + +#: ../Doc/library/sqlite3.rst:930 +msgid "" +"So if you are within a transaction and issue a command like ``CREATE " +"TABLE ...``, ``VACUUM``, ``PRAGMA``, the :mod:`sqlite3` module will commit " +"implicitly before executing that command. There are two reasons for doing " +"that. The first is that some of these commands don't work within " +"transactions. The other reason is that sqlite3 needs to keep track of the " +"transaction state (if a transaction is active or not). The current " +"transaction state is exposed through the :attr:`Connection.in_transaction` " +"attribute of the connection object." +msgstr "" + +#: ../Doc/library/sqlite3.rst:938 +msgid "" +"You can control which kind of ``BEGIN`` statements sqlite3 implicitly " +"executes (or none at all) via the *isolation_level* parameter to the :func:" +"`connect` call, or via the :attr:`isolation_level` property of connections." +msgstr "" + +#: ../Doc/library/sqlite3.rst:942 +msgid "" +"If you want **autocommit mode**, then set :attr:`isolation_level` to None." +msgstr "" + +#: ../Doc/library/sqlite3.rst:944 +msgid "" +"Otherwise leave it at its default, which will result in a plain \"BEGIN\" " +"statement, or set it to one of SQLite's supported isolation levels: " +"\"DEFERRED\", \"IMMEDIATE\" or \"EXCLUSIVE\"." +msgstr "" + +#: ../Doc/library/sqlite3.rst:948 +msgid "" +":mod:`sqlite3` used to implicitly commit an open transaction before DDL " +"statements. This is no longer the case." +msgstr "" + +#: ../Doc/library/sqlite3.rst:954 +msgid "Using :mod:`sqlite3` efficiently" +msgstr "" + +#: ../Doc/library/sqlite3.rst:958 +msgid "Using shortcut methods" +msgstr "" + +#: ../Doc/library/sqlite3.rst:960 +msgid "" +"Using the nonstandard :meth:`execute`, :meth:`executemany` and :meth:" +"`executescript` methods of the :class:`Connection` object, your code can be " +"written more concisely because you don't have to create the (often " +"superfluous) :class:`Cursor` objects explicitly. Instead, the :class:" +"`Cursor` objects are created implicitly and these shortcut methods return " +"the cursor objects. This way, you can execute a ``SELECT`` statement and " +"iterate over it directly using only a single call on the :class:`Connection` " +"object." +msgstr "" + +#: ../Doc/library/sqlite3.rst:972 +msgid "Accessing columns by name instead of by index" +msgstr "" + +#: ../Doc/library/sqlite3.rst:974 +msgid "" +"One useful feature of the :mod:`sqlite3` module is the built-in :class:" +"`sqlite3.Row` class designed to be used as a row factory." +msgstr "" + +#: ../Doc/library/sqlite3.rst:977 +msgid "" +"Rows wrapped with this class can be accessed both by index (like tuples) and " +"case-insensitively by name:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:984 +msgid "Using the connection as a context manager" +msgstr "" + +#: ../Doc/library/sqlite3.rst:986 +msgid "" +"Connection objects can be used as context managers that automatically commit " +"or rollback transactions. In the event of an exception, the transaction is " +"rolled back; otherwise, the transaction is committed:" +msgstr "" + +#: ../Doc/library/sqlite3.rst:995 +msgid "Common issues" +msgstr "" + +#: ../Doc/library/sqlite3.rst:998 +msgid "Multithreading" +msgstr "" + +#: ../Doc/library/sqlite3.rst:1000 +msgid "" +"Older SQLite versions had issues with sharing connections between threads. " +"That's why the Python module disallows sharing connections and cursors " +"between threads. If you still try to do so, you will get an exception at " +"runtime." +msgstr "" + +#: ../Doc/library/sqlite3.rst:1004 +msgid "" +"The only exception is calling the :meth:`~Connection.interrupt` method, " +"which only makes sense to call from a different thread." +msgstr "" + +#: ../Doc/library/sqlite3.rst:1009 +msgid "" +"The sqlite3 module is not built with loadable extension support by default, " +"because some platforms (notably Mac OS X) have SQLite libraries which are " +"compiled without this feature. To get loadable extension support, you must " +"pass --enable-loadable-sqlite-extensions to configure." +msgstr "" + +#: ../Doc/library/ssl.rst:2 +msgid ":mod:`ssl` --- TLS/SSL wrapper for socket objects" +msgstr "" + +#: ../Doc/library/ssl.rst:10 +msgid "**Source code:** :source:`Lib/ssl.py`" +msgstr "" + +#: ../Doc/library/ssl.rst:18 +msgid "" +"This module provides access to Transport Layer Security (often known as " +"\"Secure Sockets Layer\") encryption and peer authentication facilities for " +"network sockets, both client-side and server-side. This module uses the " +"OpenSSL library. It is available on all modern Unix systems, Windows, Mac OS " +"X, and probably additional platforms, as long as OpenSSL is installed on " +"that platform." +msgstr "" + +#: ../Doc/library/ssl.rst:26 +msgid "" +"Some behavior may be platform dependent, since calls are made to the " +"operating system socket APIs. The installed version of OpenSSL may also " +"cause variations in behavior. For example, TLSv1.1 and TLSv1.2 come with " +"openssl version 1.0.1." +msgstr "" + +#: ../Doc/library/ssl.rst:32 +msgid "" +"Don't use this module without reading the :ref:`ssl-security`. Doing so may " +"lead to a false sense of security, as the default settings of the ssl module " +"are not necessarily appropriate for your application." +msgstr "" + +#: ../Doc/library/ssl.rst:37 +msgid "" +"This section documents the objects and functions in the ``ssl`` module; for " +"more general information about TLS, SSL, and certificates, the reader is " +"referred to the documents in the \"See Also\" section at the bottom." +msgstr "" + +#: ../Doc/library/ssl.rst:41 +msgid "" +"This module provides a class, :class:`ssl.SSLSocket`, which is derived from " +"the :class:`socket.socket` type, and provides a socket-like wrapper that " +"also encrypts and decrypts the data going over the socket with SSL. It " +"supports additional methods such as :meth:`getpeercert`, which retrieves the " +"certificate of the other side of the connection, and :meth:`cipher`,which " +"retrieves the cipher being used for the secure connection." +msgstr "" + +#: ../Doc/library/ssl.rst:48 +msgid "" +"For more sophisticated applications, the :class:`ssl.SSLContext` class helps " +"manage settings and certificates, which can then be inherited by SSL sockets " +"created through the :meth:`SSLContext.wrap_socket` method." +msgstr "" + +#: ../Doc/library/ssl.rst:54 +msgid "" +"OpenSSL 0.9.8, 1.0.0 and 1.0.1 are deprecated and no longer supported. In " +"the future the ssl module will require at least OpenSSL 1.0.2 or 1.1.0." +msgstr "" + +#: ../Doc/library/ssl.rst:60 +msgid "Functions, Constants, and Exceptions" +msgstr "" + +#: ../Doc/library/ssl.rst:64 +msgid "" +"Raised to signal an error from the underlying SSL implementation (currently " +"provided by the OpenSSL library). This signifies some problem in the higher-" +"level encryption and authentication layer that's superimposed on the " +"underlying network connection. This error is a subtype of :exc:`OSError`. " +"The error code and message of :exc:`SSLError` instances are provided by the " +"OpenSSL library." +msgstr "" + +#: ../Doc/library/ssl.rst:71 +msgid ":exc:`SSLError` used to be a subtype of :exc:`socket.error`." +msgstr "" + +#: ../Doc/library/ssl.rst:76 +msgid "" +"A string mnemonic designating the OpenSSL submodule in which the error " +"occurred, such as ``SSL``, ``PEM`` or ``X509``. The range of possible " +"values depends on the OpenSSL version." +msgstr "" + +#: ../Doc/library/ssl.rst:84 +msgid "" +"A string mnemonic designating the reason this error occurred, for example " +"``CERTIFICATE_VERIFY_FAILED``. The range of possible values depends on the " +"OpenSSL version." +msgstr "" + +#: ../Doc/library/ssl.rst:92 +msgid "" +"A subclass of :exc:`SSLError` raised when trying to read or write and the " +"SSL connection has been closed cleanly. Note that this doesn't mean that " +"the underlying transport (read TCP) has been closed." +msgstr "" + +#: ../Doc/library/ssl.rst:100 +msgid "" +"A subclass of :exc:`SSLError` raised by a :ref:`non-blocking SSL socket ` when trying to read or write data, but more data needs to be " +"received on the underlying TCP transport before the request can be fulfilled." +msgstr "" + +#: ../Doc/library/ssl.rst:109 +msgid "" +"A subclass of :exc:`SSLError` raised by a :ref:`non-blocking SSL socket ` when trying to read or write data, but more data needs to be " +"sent on the underlying TCP transport before the request can be fulfilled." +msgstr "" + +#: ../Doc/library/ssl.rst:118 +msgid "" +"A subclass of :exc:`SSLError` raised when a system error was encountered " +"while trying to fulfill an operation on a SSL socket. Unfortunately, there " +"is no easy way to inspect the original errno number." +msgstr "" + +#: ../Doc/library/ssl.rst:126 +msgid "" +"A subclass of :exc:`SSLError` raised when the SSL connection has been " +"terminated abruptly. Generally, you shouldn't try to reuse the underlying " +"transport when this error is encountered." +msgstr "" + +#: ../Doc/library/ssl.rst:134 +msgid "" +"Raised to signal an error with a certificate (such as mismatching " +"hostname). Certificate errors detected by OpenSSL, though, raise an :exc:" +"`SSLError`." +msgstr "" + +#: ../Doc/library/ssl.rst:140 +msgid "Socket creation" +msgstr "" + +#: ../Doc/library/ssl.rst:142 +msgid "" +"The following function allows for standalone socket creation. Starting from " +"Python 3.2, it can be more flexible to use :meth:`SSLContext.wrap_socket` " +"instead." +msgstr "" + +#: ../Doc/library/ssl.rst:148 +msgid "" +"Takes an instance ``sock`` of :class:`socket.socket`, and returns an " +"instance of :class:`ssl.SSLSocket`, a subtype of :class:`socket.socket`, " +"which wraps the underlying socket in an SSL context. ``sock`` must be a :" +"data:`~socket.SOCK_STREAM` socket; other socket types are unsupported." +msgstr "" + +#: ../Doc/library/ssl.rst:153 +msgid "" +"For client-side sockets, the context construction is lazy; if the underlying " +"socket isn't connected yet, the context construction will be performed " +"after :meth:`connect` is called on the socket. For server-side sockets, if " +"the socket has no remote peer, it is assumed to be a listening socket, and " +"the server-side SSL wrapping is automatically performed on client " +"connections accepted via the :meth:`accept` method. :func:`wrap_socket` may " +"raise :exc:`SSLError`." +msgstr "" + +#: ../Doc/library/ssl.rst:161 +msgid "" +"The ``keyfile`` and ``certfile`` parameters specify optional files which " +"contain a certificate to be used to identify the local side of the " +"connection. See the discussion of :ref:`ssl-certificates` for more " +"information on how the certificate is stored in the ``certfile``." +msgstr "" + +#: ../Doc/library/ssl.rst:166 +msgid "" +"The parameter ``server_side`` is a boolean which identifies whether server-" +"side or client-side behavior is desired from this socket." +msgstr "" + +#: ../Doc/library/ssl.rst:169 +msgid "" +"The parameter ``cert_reqs`` specifies whether a certificate is required from " +"the other side of the connection, and whether it will be validated if " +"provided. It must be one of the three values :const:`CERT_NONE` " +"(certificates ignored), :const:`CERT_OPTIONAL` (not required, but validated " +"if provided), or :const:`CERT_REQUIRED` (required and validated). If the " +"value of this parameter is not :const:`CERT_NONE`, then the ``ca_certs`` " +"parameter must point to a file of CA certificates." +msgstr "" + +#: ../Doc/library/ssl.rst:177 +msgid "" +"The ``ca_certs`` file contains a set of concatenated \"certification " +"authority\" certificates, which are used to validate certificates passed " +"from the other end of the connection. See the discussion of :ref:`ssl-" +"certificates` for more information about how to arrange the certificates in " +"this file." +msgstr "" + +#: ../Doc/library/ssl.rst:183 +msgid "" +"The parameter ``ssl_version`` specifies which version of the SSL protocol to " +"use. Typically, the server chooses a particular protocol version, and the " +"client must adapt to the server's choice. Most of the versions are not " +"interoperable with the other versions. If not specified, the default is :" +"data:`PROTOCOL_TLS`; it provides the most compatibility with other versions." +msgstr "" + +#: ../Doc/library/ssl.rst:190 +msgid "" +"Here's a table showing which versions in a client (down the side) can " +"connect to which versions in a server (along the top):" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "*client* / **server**" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "**SSLv2**" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "**SSLv3**" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "**TLS**" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "**TLSv1**" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "**TLSv1.1**" +msgstr "" + +#: ../Doc/library/ssl.rst:196 +msgid "**TLSv1.2**" +msgstr "" + +#: ../Doc/library/ssl.rst:198 +msgid "*SSLv2*" +msgstr "" + +#: ../Doc/library/ssl.rst:198 ../Doc/library/ssl.rst:199 +#: ../Doc/library/ssl.rst:200 ../Doc/library/ssl.rst:201 +#: ../Doc/library/ssl.rst:202 ../Doc/library/ssl.rst:203 +msgid "yes" +msgstr "" + +#: ../Doc/library/ssl.rst:198 ../Doc/library/ssl.rst:199 +#: ../Doc/library/ssl.rst:201 ../Doc/library/ssl.rst:202 +#: ../Doc/library/ssl.rst:203 +msgid "no" +msgstr "" + +#: ../Doc/library/ssl.rst:198 ../Doc/library/ssl.rst:200 +msgid "no [1]_" +msgstr "" + +#: ../Doc/library/ssl.rst:199 +msgid "*SSLv3*" +msgstr "" + +#: ../Doc/library/ssl.rst:199 ../Doc/library/ssl.rst:200 +msgid "no [2]_" +msgstr "" + +#: ../Doc/library/ssl.rst:200 +msgid "*TLS* (*SSLv23*)" +msgstr "" + +#: ../Doc/library/ssl.rst:201 +msgid "*TLSv1*" +msgstr "" + +#: ../Doc/library/ssl.rst:202 +msgid "*TLSv1.1*" +msgstr "" + +#: ../Doc/library/ssl.rst:203 +msgid "*TLSv1.2*" +msgstr "" + +#: ../Doc/library/ssl.rst:207 +msgid ":class:`SSLContext` disables SSLv2 with :data:`OP_NO_SSLv2` by default." +msgstr "" + +#: ../Doc/library/ssl.rst:208 +msgid ":class:`SSLContext` disables SSLv3 with :data:`OP_NO_SSLv3` by default." +msgstr "" + +#: ../Doc/library/ssl.rst:212 +msgid "" +"Which connections succeed will vary depending on the version of OpenSSL. " +"For example, before OpenSSL 1.0.0, an SSLv23 client would always attempt " +"SSLv2 connections." +msgstr "" + +#: ../Doc/library/ssl.rst:216 +msgid "" +"The *ciphers* parameter sets the available ciphers for this SSL object. It " +"should be a string in the `OpenSSL cipher list format `_." +msgstr "" + +#: ../Doc/library/ssl.rst:220 +msgid "" +"The parameter ``do_handshake_on_connect`` specifies whether to do the SSL " +"handshake automatically after doing a :meth:`socket.connect`, or whether the " +"application program will call it explicitly, by invoking the :meth:" +"`SSLSocket.do_handshake` method. Calling :meth:`SSLSocket.do_handshake` " +"explicitly gives the program control over the blocking behavior of the " +"socket I/O involved in the handshake." +msgstr "" + +#: ../Doc/library/ssl.rst:227 +msgid "" +"The parameter ``suppress_ragged_eofs`` specifies how the :meth:`SSLSocket." +"recv` method should signal unexpected EOF from the other end of the " +"connection. If specified as :const:`True` (the default), it returns a " +"normal EOF (an empty bytes object) in response to unexpected EOF errors " +"raised from the underlying socket; if :const:`False`, it will raise the " +"exceptions back to the caller." +msgstr "" + +#: ../Doc/library/ssl.rst:234 +msgid "New optional argument *ciphers*." +msgstr "" + +#: ../Doc/library/ssl.rst:238 +msgid "Context creation" +msgstr "" + +#: ../Doc/library/ssl.rst:240 +msgid "" +"A convenience function helps create :class:`SSLContext` objects for common " +"purposes." +msgstr "" + +#: ../Doc/library/ssl.rst:245 +msgid "" +"Return a new :class:`SSLContext` object with default settings for the given " +"*purpose*. The settings are chosen by the :mod:`ssl` module, and usually " +"represent a higher security level than when calling the :class:`SSLContext` " +"constructor directly." +msgstr "" + +#: ../Doc/library/ssl.rst:250 +msgid "" +"*cafile*, *capath*, *cadata* represent optional CA certificates to trust for " +"certificate verification, as in :meth:`SSLContext.load_verify_locations`. " +"If all three are :const:`None`, this function can choose to trust the " +"system's default CA certificates instead." +msgstr "" + +#: ../Doc/library/ssl.rst:256 +msgid "" +"The settings are: :data:`PROTOCOL_TLS`, :data:`OP_NO_SSLv2`, and :data:" +"`OP_NO_SSLv3` with high encryption cipher suites without RC4 and without " +"unauthenticated cipher suites. Passing :data:`~Purpose.SERVER_AUTH` as " +"*purpose* sets :data:`~SSLContext.verify_mode` to :data:`CERT_REQUIRED` and " +"either loads CA certificates (when at least one of *cafile*, *capath* or " +"*cadata* is given) or uses :meth:`SSLContext.load_default_certs` to load " +"default CA certificates." +msgstr "" + +#: ../Doc/library/ssl.rst:265 +msgid "" +"The protocol, options, cipher and other settings may change to more " +"restrictive values anytime without prior deprecation. The values represent " +"a fair balance between compatibility and security." +msgstr "" + +#: ../Doc/library/ssl.rst:269 +msgid "" +"If your application needs specific settings, you should create a :class:" +"`SSLContext` and apply the settings yourself." +msgstr "" + +#: ../Doc/library/ssl.rst:273 +msgid "" +"If you find that when certain older clients or servers attempt to connect " +"with a :class:`SSLContext` created by this function that they get an error " +"stating \"Protocol or cipher suite mismatch\", it may be that they only " +"support SSL3.0 which this function excludes using the :data:`OP_NO_SSLv3`. " +"SSL3.0 is widely considered to be `completely broken `_. If you still wish to continue to use this function but " +"still allow SSL 3.0 connections you can re-enable them using::" +msgstr "" + +#: ../Doc/library/ssl.rst:289 +msgid "RC4 was dropped from the default cipher string." +msgstr "" + +#: ../Doc/library/ssl.rst:293 +msgid "ChaCha20/Poly1305 was added to the default cipher string." +msgstr "" + +#: ../Doc/library/ssl.rst:295 +msgid "3DES was dropped from the default cipher string." +msgstr "" + +#: ../Doc/library/ssl.rst:299 +msgid "Random generation" +msgstr "" + +#: ../Doc/library/ssl.rst:303 +msgid "" +"Return *num* cryptographically strong pseudo-random bytes. Raises an :class:" +"`SSLError` if the PRNG has not been seeded with enough data or if the " +"operation is not supported by the current RAND method. :func:`RAND_status` " +"can be used to check the status of the PRNG and :func:`RAND_add` can be used " +"to seed the PRNG." +msgstr "" + +#: ../Doc/library/ssl.rst:309 ../Doc/library/ssl.rst:330 +msgid "For almost all applications :func:`os.urandom` is preferable." +msgstr "" + +#: ../Doc/library/ssl.rst:311 +msgid "" +"Read the Wikipedia article, `Cryptographically secure pseudorandom number " +"generator (CSPRNG) `_, to get the " +"requirements of a cryptographically generator." +msgstr "" + +#: ../Doc/library/ssl.rst:320 +msgid "" +"Return (bytes, is_cryptographic): bytes are *num* pseudo-random bytes, " +"is_cryptographic is ``True`` if the bytes generated are cryptographically " +"strong. Raises an :class:`SSLError` if the operation is not supported by the " +"current RAND method." +msgstr "" + +#: ../Doc/library/ssl.rst:325 +msgid "" +"Generated pseudo-random byte sequences will be unique if they are of " +"sufficient length, but are not necessarily unpredictable. They can be used " +"for non-cryptographic purposes and for certain purposes in cryptographic " +"protocols, but usually not for key generation etc." +msgstr "" + +#: ../Doc/library/ssl.rst:336 +msgid "" +"OpenSSL has deprecated :func:`ssl.RAND_pseudo_bytes`, use :func:`ssl." +"RAND_bytes` instead." +msgstr "" + +#: ../Doc/library/ssl.rst:341 +msgid "" +"Return ``True`` if the SSL pseudo-random number generator has been seeded " +"with 'enough' randomness, and ``False`` otherwise. You can use :func:`ssl." +"RAND_egd` and :func:`ssl.RAND_add` to increase the randomness of the pseudo-" +"random number generator." +msgstr "" + +#: ../Doc/library/ssl.rst:348 +msgid "" +"If you are running an entropy-gathering daemon (EGD) somewhere, and *path* " +"is the pathname of a socket connection open to it, this will read 256 bytes " +"of randomness from the socket, and add it to the SSL pseudo-random number " +"generator to increase the security of generated secret keys. This is " +"typically only necessary on systems without better sources of randomness." +msgstr "" + +#: ../Doc/library/ssl.rst:354 +msgid "" +"See http://egd.sourceforge.net/ or http://prngd.sourceforge.net/ for sources " +"of entropy-gathering daemons." +msgstr "" + +#: ../Doc/library/ssl.rst:357 +msgid "Availability: not available with LibreSSL and OpenSSL > 1.1.0" +msgstr "" + +#: ../Doc/library/ssl.rst:361 +msgid "" +"Mix the given *bytes* into the SSL pseudo-random number generator. The " +"parameter *entropy* (a float) is a lower bound on the entropy contained in " +"string (so you can always use :const:`0.0`). See :rfc:`1750` for more " +"information on sources of entropy." +msgstr "" + +#: ../Doc/library/ssl.rst:370 +msgid "Certificate handling" +msgstr "" + +#: ../Doc/library/ssl.rst:374 +msgid "" +"Verify that *cert* (in decoded format as returned by :meth:`SSLSocket." +"getpeercert`) matches the given *hostname*. The rules applied are those for " +"checking the identity of HTTPS servers as outlined in :rfc:`2818` and :rfc:" +"`6125`. In addition to HTTPS, this function should be suitable for checking " +"the identity of servers in various SSL-based protocols such as FTPS, IMAPS, " +"POPS and others." +msgstr "" + +#: ../Doc/library/ssl.rst:381 +msgid "" +":exc:`CertificateError` is raised on failure. On success, the function " +"returns nothing::" +msgstr "" + +#: ../Doc/library/ssl.rst:394 +msgid "" +"The function now follows :rfc:`6125`, section 6.4.3 and does neither match " +"multiple wildcards (e.g. ``*.*.com`` or ``*a*.example.org``) nor a wildcard " +"inside an internationalized domain names (IDN) fragment. IDN A-labels such " +"as ``www*.xn--pthon-kva.org`` are still supported, but ``x*.python.org`` no " +"longer matches ``xn--tda.python.org``." +msgstr "" + +#: ../Doc/library/ssl.rst:401 +msgid "" +"Matching of IP addresses, when present in the subjectAltName field of the " +"certificate, is now supported." +msgstr "" + +#: ../Doc/library/ssl.rst:407 +msgid "" +"Return the time in seconds since the Epoch, given the ``cert_time`` string " +"representing the \"notBefore\" or \"notAfter\" date from a certificate in ``" +"\"%b %d %H:%M:%S %Y %Z\"`` strptime format (C locale)." +msgstr "" + +#: ../Doc/library/ssl.rst:412 +msgid "Here's an example:" +msgstr "" + +#: ../Doc/library/ssl.rst:424 +msgid "\"notBefore\" or \"notAfter\" dates must use GMT (:rfc:`5280`)." +msgstr "" + +#: ../Doc/library/ssl.rst:426 +msgid "" +"Interpret the input time as a time in UTC as specified by 'GMT' timezone in " +"the input string. Local timezone was used previously. Return an integer (no " +"fractions of a second in the input format)" +msgstr "" + +#: ../Doc/library/ssl.rst:434 +msgid "" +"Given the address ``addr`` of an SSL-protected server, as a (*hostname*, " +"*port-number*) pair, fetches the server's certificate, and returns it as a " +"PEM-encoded string. If ``ssl_version`` is specified, uses that version of " +"the SSL protocol to attempt to connect to the server. If ``ca_certs`` is " +"specified, it should be a file containing a list of root certificates, the " +"same format as used for the same parameter in :func:`wrap_socket`. The call " +"will attempt to validate the server certificate against that set of root " +"certificates, and will fail if the validation attempt fails." +msgstr "" + +#: ../Doc/library/ssl.rst:443 +msgid "This function is now IPv6-compatible." +msgstr "" + +#: ../Doc/library/ssl.rst:446 +msgid "" +"The default *ssl_version* is changed from :data:`PROTOCOL_SSLv3` to :data:" +"`PROTOCOL_TLS` for maximum compatibility with modern servers." +msgstr "" + +#: ../Doc/library/ssl.rst:452 +msgid "" +"Given a certificate as a DER-encoded blob of bytes, returns a PEM-encoded " +"string version of the same certificate." +msgstr "" + +#: ../Doc/library/ssl.rst:457 +msgid "" +"Given a certificate as an ASCII PEM string, returns a DER-encoded sequence " +"of bytes for that same certificate." +msgstr "" + +#: ../Doc/library/ssl.rst:462 +msgid "" +"Returns a named tuple with paths to OpenSSL's default cafile and capath. The " +"paths are the same as used by :meth:`SSLContext.set_default_verify_paths`. " +"The return value is a :term:`named tuple` ``DefaultVerifyPaths``:" +msgstr "" + +#: ../Doc/library/ssl.rst:467 +msgid "" +":attr:`cafile` - resolved path to cafile or None if the file doesn't exist," +msgstr "" + +#: ../Doc/library/ssl.rst:468 +msgid "" +":attr:`capath` - resolved path to capath or None if the directory doesn't " +"exist," +msgstr "" + +#: ../Doc/library/ssl.rst:469 +msgid "" +":attr:`openssl_cafile_env` - OpenSSL's environment key that points to a " +"cafile," +msgstr "" + +#: ../Doc/library/ssl.rst:470 +msgid ":attr:`openssl_cafile` - hard coded path to a cafile," +msgstr "" + +#: ../Doc/library/ssl.rst:471 +msgid "" +":attr:`openssl_capath_env` - OpenSSL's environment key that points to a " +"capath," +msgstr "" + +#: ../Doc/library/ssl.rst:472 +msgid ":attr:`openssl_capath` - hard coded path to a capath directory" +msgstr "" + +#: ../Doc/library/ssl.rst:474 +msgid "" +"Availability: LibreSSL ignores the environment vars :attr:" +"`openssl_cafile_env` and :attr:`openssl_capath_env`" +msgstr "" + +#: ../Doc/library/ssl.rst:481 +msgid "" +"Retrieve certificates from Windows' system cert store. *store_name* may be " +"one of ``CA``, ``ROOT`` or ``MY``. Windows may provide additional cert " +"stores, too." +msgstr "" + +#: ../Doc/library/ssl.rst:485 +msgid "" +"The function returns a list of (cert_bytes, encoding_type, trust) tuples. " +"The encoding_type specifies the encoding of cert_bytes. It is either :const:" +"`x509_asn` for X.509 ASN.1 data or :const:`pkcs_7_asn` for PKCS#7 ASN.1 " +"data. Trust specifies the purpose of the certificate as a set of OIDS or " +"exactly ``True`` if the certificate is trustworthy for all purposes." +msgstr "" + +#: ../Doc/library/ssl.rst:504 +msgid "" +"Retrieve CRLs from Windows' system cert store. *store_name* may be one of " +"``CA``, ``ROOT`` or ``MY``. Windows may provide additional cert stores, too." +msgstr "" + +#: ../Doc/library/ssl.rst:508 +msgid "" +"The function returns a list of (cert_bytes, encoding_type, trust) tuples. " +"The encoding_type specifies the encoding of cert_bytes. It is either :const:" +"`x509_asn` for X.509 ASN.1 data or :const:`pkcs_7_asn` for PKCS#7 ASN.1 data." +msgstr "" + +#: ../Doc/library/ssl.rst:521 +msgid "" +"All constants are now :class:`enum.IntEnum` or :class:`enum.IntFlag` " +"collections." +msgstr "" + +#: ../Doc/library/ssl.rst:527 +msgid "" +"Possible value for :attr:`SSLContext.verify_mode`, or the ``cert_reqs`` " +"parameter to :func:`wrap_socket`. In this mode (the default), no " +"certificates will be required from the other side of the socket connection. " +"If a certificate is received from the other end, no attempt to validate it " +"is made." +msgstr "" + +#: ../Doc/library/ssl.rst:533 ../Doc/library/ssl.rst:1927 +msgid "See the discussion of :ref:`ssl-security` below." +msgstr "" + +#: ../Doc/library/ssl.rst:537 +msgid "" +"Possible value for :attr:`SSLContext.verify_mode`, or the ``cert_reqs`` " +"parameter to :func:`wrap_socket`. In this mode no certificates will be " +"required from the other side of the socket connection; but if they are " +"provided, validation will be attempted and an :class:`SSLError` will be " +"raised on failure." +msgstr "" + +#: ../Doc/library/ssl.rst:543 ../Doc/library/ssl.rst:554 +msgid "" +"Use of this setting requires a valid set of CA certificates to be passed, " +"either to :meth:`SSLContext.load_verify_locations` or as a value of the " +"``ca_certs`` parameter to :func:`wrap_socket`." +msgstr "" + +#: ../Doc/library/ssl.rst:549 +msgid "" +"Possible value for :attr:`SSLContext.verify_mode`, or the ``cert_reqs`` " +"parameter to :func:`wrap_socket`. In this mode, certificates are required " +"from the other side of the socket connection; an :class:`SSLError` will be " +"raised if no certificate is provided, or if its validation fails." +msgstr "" + +#: ../Doc/library/ssl.rst:560 +msgid ":class:`enum.IntEnum` collection of CERT_* constants." +msgstr "" + +#: ../Doc/library/ssl.rst:566 +msgid "" +"Possible value for :attr:`SSLContext.verify_flags`. In this mode, " +"certificate revocation lists (CRLs) are not checked. By default OpenSSL does " +"neither require nor verify CRLs." +msgstr "" + +#: ../Doc/library/ssl.rst:574 +msgid "" +"Possible value for :attr:`SSLContext.verify_flags`. In this mode, only the " +"peer cert is check but non of the intermediate CA certificates. The mode " +"requires a valid CRL that is signed by the peer cert's issuer (its direct " +"ancestor CA). If no proper has been loaded :attr:`SSLContext." +"load_verify_locations`, validation will fail." +msgstr "" + +#: ../Doc/library/ssl.rst:584 +msgid "" +"Possible value for :attr:`SSLContext.verify_flags`. In this mode, CRLs of " +"all certificates in the peer cert chain are checked." +msgstr "" + +#: ../Doc/library/ssl.rst:591 +msgid "" +"Possible value for :attr:`SSLContext.verify_flags` to disable workarounds " +"for broken X.509 certificates." +msgstr "" + +#: ../Doc/library/ssl.rst:598 +msgid "" +"Possible value for :attr:`SSLContext.verify_flags`. It instructs OpenSSL to " +"prefer trusted certificates when building the trust chain to validate a " +"certificate. This flag is enabled by default." +msgstr "" + +#: ../Doc/library/ssl.rst:606 +msgid ":class:`enum.IntFlag` collection of VERIFY_* constants." +msgstr "" + +#: ../Doc/library/ssl.rst:612 +msgid "" +"Selects the highest protocol version that both the client and server " +"support. Despite the name, this option can select \"TLS\" protocols as well " +"as \"SSL\"." +msgstr "" + +#: ../Doc/library/ssl.rst:619 +msgid "" +"Auto-negotiate the the highest protocol version like :data:" +"`PROTOCOL_SSLv23`, but only support client-side :class:`SSLSocket` " +"connections. The protocol enables :data:`CERT_REQUIRED` and :attr:" +"`~SSLContext.check_hostname` by default." +msgstr "" + +#: ../Doc/library/ssl.rst:628 +msgid "" +"Auto-negotiate the the highest protocol version like :data:" +"`PROTOCOL_SSLv23`, but only support server-side :class:`SSLSocket` " +"connections." +msgstr "" + +#: ../Doc/library/ssl.rst:635 +msgid "Alias for data:`PROTOCOL_TLS`." +msgstr "" + +#: ../Doc/library/ssl.rst:639 +msgid "Use data:`PROTOCOL_TLS` instead." +msgstr "" + +#: ../Doc/library/ssl.rst:643 +msgid "Selects SSL version 2 as the channel encryption protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:645 +msgid "" +"This protocol is not available if OpenSSL is compiled with the " +"``OPENSSL_NO_SSL2`` flag." +msgstr "" + +#: ../Doc/library/ssl.rst:650 +msgid "SSL version 2 is insecure. Its use is highly discouraged." +msgstr "" + +#: ../Doc/library/ssl.rst:654 +msgid "OpenSSL has removed support for SSLv2." +msgstr "" + +#: ../Doc/library/ssl.rst:658 +msgid "Selects SSL version 3 as the channel encryption protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:660 +msgid "" +"This protocol is not be available if OpenSSL is compiled with the " +"``OPENSSL_NO_SSLv3`` flag." +msgstr "" + +#: ../Doc/library/ssl.rst:665 +msgid "SSL version 3 is insecure. Its use is highly discouraged." +msgstr "" + +#: ../Doc/library/ssl.rst:669 ../Doc/library/ssl.rst:678 +#: ../Doc/library/ssl.rst:690 ../Doc/library/ssl.rst:703 +msgid "" +"OpenSSL has deprecated all version specific protocols. Use the default " +"protocol data:`PROTOCOL_TLS` with flags like data:`OP_NO_SSLv3` instead." +msgstr "" + +#: ../Doc/library/ssl.rst:674 +msgid "Selects TLS version 1.0 as the channel encryption protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:683 +msgid "" +"Selects TLS version 1.1 as the channel encryption protocol. Available only " +"with openssl version 1.0.1+." +msgstr "" + +#: ../Doc/library/ssl.rst:695 +msgid "" +"Selects TLS version 1.2 as the channel encryption protocol. This is the most " +"modern version, and probably the best choice for maximum protection, if both " +"sides can speak it. Available only with openssl version 1.0.1+." +msgstr "" + +#: ../Doc/library/ssl.rst:708 +msgid "" +"Enables workarounds for various bugs present in other SSL implementations. " +"This option is set by default. It does not necessarily set the same flags " +"as OpenSSL's ``SSL_OP_ALL`` constant." +msgstr "" + +#: ../Doc/library/ssl.rst:716 +msgid "" +"Prevents an SSLv2 connection. This option is only applicable in conjunction " +"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing SSLv2 as " +"the protocol version." +msgstr "" + +#: ../Doc/library/ssl.rst:724 +msgid "SSLv2 is deprecated" +msgstr "" + +#: ../Doc/library/ssl.rst:729 +msgid "" +"Prevents an SSLv3 connection. This option is only applicable in conjunction " +"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing SSLv3 as " +"the protocol version." +msgstr "" + +#: ../Doc/library/ssl.rst:737 +msgid "SSLv3 is deprecated" +msgstr "" + +#: ../Doc/library/ssl.rst:741 +msgid "" +"Prevents a TLSv1 connection. This option is only applicable in conjunction " +"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing TLSv1 as " +"the protocol version." +msgstr "" + +#: ../Doc/library/ssl.rst:749 +msgid "" +"Prevents a TLSv1.1 connection. This option is only applicable in conjunction " +"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing TLSv1.1 as " +"the protocol version. Available only with openssl version 1.0.1+." +msgstr "" + +#: ../Doc/library/ssl.rst:757 +msgid "" +"Prevents a TLSv1.2 connection. This option is only applicable in conjunction " +"with :const:`PROTOCOL_TLS`. It prevents the peers from choosing TLSv1.2 as " +"the protocol version. Available only with openssl version 1.0.1+." +msgstr "" + +#: ../Doc/library/ssl.rst:765 +msgid "" +"Use the server's cipher ordering preference, rather than the client's. This " +"option has no effect on client sockets and SSLv2 server sockets." +msgstr "" + +#: ../Doc/library/ssl.rst:772 +msgid "" +"Prevents re-use of the same DH key for distinct SSL sessions. This improves " +"forward secrecy but requires more computational resources. This option only " +"applies to server sockets." +msgstr "" + +#: ../Doc/library/ssl.rst:780 +msgid "" +"Prevents re-use of the same ECDH key for distinct SSL sessions. This " +"improves forward secrecy but requires more computational resources. This " +"option only applies to server sockets." +msgstr "" + +#: ../Doc/library/ssl.rst:788 +msgid "" +"Disable compression on the SSL channel. This is useful if the application " +"protocol supports its own compression scheme." +msgstr "" + +#: ../Doc/library/ssl.rst:791 +msgid "This option is only available with OpenSSL 1.0.0 and later." +msgstr "" + +#: ../Doc/library/ssl.rst:797 +msgid ":class:`enum.IntFlag` collection of OP_* constants." +msgstr "" + +#: ../Doc/library/ssl.rst:801 +msgid "Prevent client side from requesting a session ticket." +msgstr "" + +#: ../Doc/library/ssl.rst:807 +msgid "" +"Whether the OpenSSL library has built-in support for the *Application-Layer " +"Protocol Negotiation* TLS extension as described in :rfc:`7301`." +msgstr "" + +#: ../Doc/library/ssl.rst:814 +msgid "" +"Whether the OpenSSL library has built-in support for Elliptic Curve-based " +"Diffie-Hellman key exchange. This should be true unless the feature was " +"explicitly disabled by the distributor." +msgstr "" + +#: ../Doc/library/ssl.rst:822 +msgid "" +"Whether the OpenSSL library has built-in support for the *Server Name " +"Indication* extension (as defined in :rfc:`4366`)." +msgstr "" + +#: ../Doc/library/ssl.rst:829 +msgid "" +"Whether the OpenSSL library has built-in support for *Next Protocol " +"Negotiation* as described in the `NPN draft specification `_. When true, you can use the :" +"meth:`SSLContext.set_npn_protocols` method to advertise which protocols you " +"want to support." +msgstr "" + +#: ../Doc/library/ssl.rst:839 +msgid "" +"List of supported TLS channel binding types. Strings in this list can be " +"used as arguments to :meth:`SSLSocket.get_channel_binding`." +msgstr "" + +#: ../Doc/library/ssl.rst:846 +msgid "The version string of the OpenSSL library loaded by the interpreter::" +msgstr "" + +#: ../Doc/library/ssl.rst:855 +msgid "" +"A tuple of five integers representing version information about the OpenSSL " +"library::" +msgstr "" + +#: ../Doc/library/ssl.rst:865 +msgid "The raw version number of the OpenSSL library, as a single integer::" +msgstr "" + +#: ../Doc/library/ssl.rst:878 +msgid "" +"Alert Descriptions from :rfc:`5246` and others. The `IANA TLS Alert Registry " +"`_ contains this list and references to the RFCs where their " +"meaning is defined." +msgstr "" + +#: ../Doc/library/ssl.rst:882 +msgid "" +"Used as the return value of the callback function in :meth:`SSLContext." +"set_servername_callback`." +msgstr "" + +#: ../Doc/library/ssl.rst:889 +msgid ":class:`enum.IntEnum` collection of ALERT_DESCRIPTION_* constants." +msgstr "" + +#: ../Doc/library/ssl.rst:895 +msgid "" +"Option for :func:`create_default_context` and :meth:`SSLContext." +"load_default_certs`. This value indicates that the context may be used to " +"authenticate Web servers (therefore, it will be used to create client-side " +"sockets)." +msgstr "" + +#: ../Doc/library/ssl.rst:904 +msgid "" +"Option for :func:`create_default_context` and :meth:`SSLContext." +"load_default_certs`. This value indicates that the context may be used to " +"authenticate Web clients (therefore, it will be used to create server-side " +"sockets)." +msgstr "" + +#: ../Doc/library/ssl.rst:913 +msgid ":class:`enum.IntEnum` collection of SSL_ERROR_* constants." +msgstr "" + +#: ../Doc/library/ssl.rst:919 +msgid "SSL Sockets" +msgstr "" + +#: ../Doc/library/ssl.rst:923 +msgid "SSL sockets provide the following methods of :ref:`socket-objects`:" +msgstr "" + +#: ../Doc/library/ssl.rst:925 +msgid ":meth:`~socket.socket.accept()`" +msgstr "" + +#: ../Doc/library/ssl.rst:926 +msgid ":meth:`~socket.socket.bind()`" +msgstr "" + +#: ../Doc/library/ssl.rst:927 +msgid ":meth:`~socket.socket.close()`" +msgstr "" + +#: ../Doc/library/ssl.rst:928 +msgid ":meth:`~socket.socket.connect()`" +msgstr "" + +#: ../Doc/library/ssl.rst:929 +msgid ":meth:`~socket.socket.detach()`" +msgstr "" + +#: ../Doc/library/ssl.rst:930 +msgid ":meth:`~socket.socket.fileno()`" +msgstr "" + +#: ../Doc/library/ssl.rst:931 +msgid "" +":meth:`~socket.socket.getpeername()`, :meth:`~socket.socket.getsockname()`" +msgstr "" + +#: ../Doc/library/ssl.rst:932 +msgid "" +":meth:`~socket.socket.getsockopt()`, :meth:`~socket.socket.setsockopt()`" +msgstr "" + +#: ../Doc/library/ssl.rst:933 +msgid "" +":meth:`~socket.socket.gettimeout()`, :meth:`~socket.socket.settimeout()`, :" +"meth:`~socket.socket.setblocking()`" +msgstr "" + +#: ../Doc/library/ssl.rst:935 +msgid ":meth:`~socket.socket.listen()`" +msgstr "" + +#: ../Doc/library/ssl.rst:936 +msgid ":meth:`~socket.socket.makefile()`" +msgstr "" + +#: ../Doc/library/ssl.rst:937 +msgid "" +":meth:`~socket.socket.recv()`, :meth:`~socket.socket.recv_into()` (but " +"passing a non-zero ``flags`` argument is not allowed)" +msgstr "" + +#: ../Doc/library/ssl.rst:939 +msgid "" +":meth:`~socket.socket.send()`, :meth:`~socket.socket.sendall()` (with the " +"same limitation)" +msgstr "" + +#: ../Doc/library/ssl.rst:941 +msgid "" +":meth:`~socket.socket.sendfile()` (but :mod:`os.sendfile` will be used for " +"plain-text sockets only, else :meth:`~socket.socket.send()` will be used)" +msgstr "" + +#: ../Doc/library/ssl.rst:943 +msgid ":meth:`~socket.socket.shutdown()`" +msgstr "" + +#: ../Doc/library/ssl.rst:945 +msgid "" +"However, since the SSL (and TLS) protocol has its own framing atop of TCP, " +"the SSL sockets abstraction can, in certain respects, diverge from the " +"specification of normal, OS-level sockets. See especially the :ref:`notes " +"on non-blocking sockets `." +msgstr "" + +#: ../Doc/library/ssl.rst:950 +msgid "" +"Usually, :class:`SSLSocket` are not created directly, but using the the :" +"meth:`SSLContext.wrap_socket` method." +msgstr "" + +#: ../Doc/library/ssl.rst:953 +msgid "The :meth:`sendfile` method was added." +msgstr "" + +#: ../Doc/library/ssl.rst:956 +msgid "" +"The :meth:`shutdown` does not reset the socket timeout each time bytes are " +"received or sent. The socket timeout is now to maximum total duration of the " +"shutdown." +msgstr "" + +#: ../Doc/library/ssl.rst:961 +msgid "" +"It is deprecated to create a :class:`SSLSocket` instance directly, use :meth:" +"`SSLContext.wrap_socket` to wrap a socket." +msgstr "" + +#: ../Doc/library/ssl.rst:966 +msgid "SSL sockets also have the following additional methods and attributes:" +msgstr "" + +#: ../Doc/library/ssl.rst:970 +msgid "" +"Read up to *len* bytes of data from the SSL socket and return the result as " +"a ``bytes`` instance. If *buffer* is specified, then read into the buffer " +"instead, and return the number of bytes read." +msgstr "" + +#: ../Doc/library/ssl.rst:974 +msgid "" +"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket is :" +"ref:`non-blocking ` and the read would block." +msgstr "" + +#: ../Doc/library/ssl.rst:977 +msgid "" +"As at any time a re-negotiation is possible, a call to :meth:`read` can also " +"cause write operations." +msgstr "" + +#: ../Doc/library/ssl.rst:980 +msgid "" +"The socket timeout is no more reset each time bytes are received or sent. " +"The socket timeout is now to maximum total duration to read up to *len* " +"bytes." +msgstr "" + +#: ../Doc/library/ssl.rst:985 +msgid "Use :meth:`~SSLSocket.recv` instead of :meth:`~SSLSocket.read`." +msgstr "" + +#: ../Doc/library/ssl.rst:990 +msgid "" +"Write *buf* to the SSL socket and return the number of bytes written. The " +"*buf* argument must be an object supporting the buffer interface." +msgstr "" + +#: ../Doc/library/ssl.rst:993 +msgid "" +"Raise :exc:`SSLWantReadError` or :exc:`SSLWantWriteError` if the socket is :" +"ref:`non-blocking ` and the write would block." +msgstr "" + +#: ../Doc/library/ssl.rst:996 +msgid "" +"As at any time a re-negotiation is possible, a call to :meth:`write` can " +"also cause read operations." +msgstr "" + +#: ../Doc/library/ssl.rst:999 +msgid "" +"The socket timeout is no more reset each time bytes are received or sent. " +"The socket timeout is now to maximum total duration to write *buf*." +msgstr "" + +#: ../Doc/library/ssl.rst:1003 +msgid "Use :meth:`~SSLSocket.send` instead of :meth:`~SSLSocket.write`." +msgstr "" + +#: ../Doc/library/ssl.rst:1008 +msgid "" +"The :meth:`~SSLSocket.read` and :meth:`~SSLSocket.write` methods are the low-" +"level methods that read and write unencrypted, application-level data and " +"decrypt/encrypt it to encrypted, wire-level data. These methods require an " +"active SSL connection, i.e. the handshake was completed and :meth:`SSLSocket." +"unwrap` was not called." +msgstr "" + +#: ../Doc/library/ssl.rst:1014 +msgid "" +"Normally you should use the socket API methods like :meth:`~socket.socket." +"recv` and :meth:`~socket.socket.send` instead of these methods." +msgstr "" + +#: ../Doc/library/ssl.rst:1020 +msgid "Perform the SSL setup handshake." +msgstr "" + +#: ../Doc/library/ssl.rst:1022 +msgid "" +"The handshake method also performs :func:`match_hostname` when the :attr:" +"`~SSLContext.check_hostname` attribute of the socket's :attr:`~SSLSocket." +"context` is true." +msgstr "" + +#: ../Doc/library/ssl.rst:1027 +msgid "" +"The socket timeout is no more reset each time bytes are received or sent. " +"The socket timeout is now to maximum total duration of the handshake." +msgstr "" + +#: ../Doc/library/ssl.rst:1033 +msgid "" +"If there is no certificate for the peer on the other end of the connection, " +"return ``None``. If the SSL handshake hasn't been done yet, raise :exc:" +"`ValueError`." +msgstr "" + +#: ../Doc/library/ssl.rst:1037 +msgid "" +"If the ``binary_form`` parameter is :const:`False`, and a certificate was " +"received from the peer, this method returns a :class:`dict` instance. If " +"the certificate was not validated, the dict is empty. If the certificate " +"was validated, it returns a dict with several keys, amongst them ``subject`` " +"(the principal for which the certificate was issued) and ``issuer`` (the " +"principal issuing the certificate). If a certificate contains an instance " +"of the *Subject Alternative Name* extension (see :rfc:`3280`), there will " +"also be a ``subjectAltName`` key in the dictionary." +msgstr "" + +#: ../Doc/library/ssl.rst:1046 +msgid "" +"The ``subject`` and ``issuer`` fields are tuples containing the sequence of " +"relative distinguished names (RDNs) given in the certificate's data " +"structure for the respective fields, and each RDN is a sequence of name-" +"value pairs. Here is a real-world example::" +msgstr "" + +#: ../Doc/library/ssl.rst:1072 +msgid "" +"To validate a certificate for a particular service, you can use the :func:" +"`match_hostname` function." +msgstr "" + +#: ../Doc/library/ssl.rst:1075 +msgid "" +"If the ``binary_form`` parameter is :const:`True`, and a certificate was " +"provided, this method returns the DER-encoded form of the entire certificate " +"as a sequence of bytes, or :const:`None` if the peer did not provide a " +"certificate. Whether the peer provides a certificate depends on the SSL " +"socket's role:" +msgstr "" + +#: ../Doc/library/ssl.rst:1081 +msgid "" +"for a client SSL socket, the server will always provide a certificate, " +"regardless of whether validation was required;" +msgstr "" + +#: ../Doc/library/ssl.rst:1084 +msgid "" +"for a server SSL socket, the client will only provide a certificate when " +"requested by the server; therefore :meth:`getpeercert` will return :const:" +"`None` if you used :const:`CERT_NONE` (rather than :const:`CERT_OPTIONAL` " +"or :const:`CERT_REQUIRED`)." +msgstr "" + +#: ../Doc/library/ssl.rst:1089 +msgid "" +"The returned dictionary includes additional items such as ``issuer`` and " +"``notBefore``." +msgstr "" + +#: ../Doc/library/ssl.rst:1093 +msgid "" +":exc:`ValueError` is raised when the handshake isn't done. The returned " +"dictionary includes additional X509v3 extension items such as " +"``crlDistributionPoints``, ``caIssuers`` and ``OCSP`` URIs." +msgstr "" + +#: ../Doc/library/ssl.rst:1100 +msgid "" +"Returns a three-value tuple containing the name of the cipher being used, " +"the version of the SSL protocol that defines its use, and the number of " +"secret bits being used. If no connection has been established, returns " +"``None``." +msgstr "" + +#: ../Doc/library/ssl.rst:1106 +msgid "" +"Return the list of ciphers shared by the client during the handshake. Each " +"entry of the returned list is a three-value tuple containing the name of the " +"cipher, the version of the SSL protocol that defines its use, and the number " +"of secret bits the cipher uses. :meth:`~SSLSocket.shared_ciphers` returns " +"``None`` if no connection has been established or the socket is a client " +"socket." +msgstr "" + +#: ../Doc/library/ssl.rst:1117 +msgid "" +"Return the compression algorithm being used as a string, or ``None`` if the " +"connection isn't compressed." +msgstr "" + +#: ../Doc/library/ssl.rst:1120 +msgid "" +"If the higher-level protocol supports its own compression mechanism, you can " +"use :data:`OP_NO_COMPRESSION` to disable SSL-level compression." +msgstr "" + +#: ../Doc/library/ssl.rst:1127 +msgid "" +"Get channel binding data for current connection, as a bytes object. Returns " +"``None`` if not connected or the handshake has not been completed." +msgstr "" + +#: ../Doc/library/ssl.rst:1130 +msgid "" +"The *cb_type* parameter allow selection of the desired channel binding type. " +"Valid channel binding types are listed in the :data:`CHANNEL_BINDING_TYPES` " +"list. Currently only the 'tls-unique' channel binding, defined by :rfc:" +"`5929`, is supported. :exc:`ValueError` will be raised if an unsupported " +"channel binding type is requested." +msgstr "" + +#: ../Doc/library/ssl.rst:1140 +msgid "" +"Return the protocol that was selected during the TLS handshake. If :meth:" +"`SSLContext.set_alpn_protocols` was not called, if the other party does not " +"support ALPN, if this socket does not support any of the client's proposed " +"protocols, or if the handshake has not happened yet, ``None`` is returned." +msgstr "" + +#: ../Doc/library/ssl.rst:1150 +msgid "" +"Return the higher-level protocol that was selected during the TLS/SSL " +"handshake. If :meth:`SSLContext.set_npn_protocols` was not called, or if the " +"other party does not support NPN, or if the handshake has not yet happened, " +"this will return ``None``." +msgstr "" + +#: ../Doc/library/ssl.rst:1159 +msgid "" +"Performs the SSL shutdown handshake, which removes the TLS layer from the " +"underlying socket, and returns the underlying socket object. This can be " +"used to go from encrypted operation over a connection to unencrypted. The " +"returned socket should always be used for further communication with the " +"other side of the connection, rather than the original socket." +msgstr "" + +#: ../Doc/library/ssl.rst:1167 +msgid "" +"Return the actual SSL protocol version negotiated by the connection as a " +"string, or ``None`` is no secure connection is established. As of this " +"writing, possible return values include ``\"SSLv2\"``, ``\"SSLv3\"``, ``" +"\"TLSv1\"``, ``\"TLSv1.1\"`` and ``\"TLSv1.2\"``. Recent OpenSSL versions " +"may define more return values." +msgstr "" + +#: ../Doc/library/ssl.rst:1177 +msgid "" +"Returns the number of already decrypted bytes available for read, pending on " +"the connection." +msgstr "" + +#: ../Doc/library/ssl.rst:1182 +msgid "" +"The :class:`SSLContext` object this SSL socket is tied to. If the SSL " +"socket was created using the top-level :func:`wrap_socket` function (rather " +"than :meth:`SSLContext.wrap_socket`), this is a custom context object " +"created for this SSL socket." +msgstr "" + +#: ../Doc/library/ssl.rst:1191 +msgid "" +"A boolean which is ``True`` for server-side sockets and ``False`` for client-" +"side sockets." +msgstr "" + +#: ../Doc/library/ssl.rst:1198 +msgid "" +"Hostname of the server: :class:`str` type, or ``None`` for server-side " +"socket or if the hostname was not specified in the constructor." +msgstr "" + +#: ../Doc/library/ssl.rst:1205 +msgid "" +"The :class:`SSLSession` for this SSL connection. The session is available " +"for client and server side sockets after the TLS handshake has been " +"performed. For client sockets the session can be set before :meth:" +"`~SSLSocket.do_handshake` has been called to reuse a session." +msgstr "" + +#: ../Doc/library/ssl.rst:1218 +msgid "SSL Contexts" +msgstr "" + +#: ../Doc/library/ssl.rst:1222 +msgid "" +"An SSL context holds various data longer-lived than single SSL connections, " +"such as SSL configuration options, certificate(s) and private key(s). It " +"also manages a cache of SSL sessions for server-side sockets, in order to " +"speed up repeated connections from the same clients." +msgstr "" + +#: ../Doc/library/ssl.rst:1229 +msgid "" +"Create a new SSL context. You may pass *protocol* which must be one of the " +"``PROTOCOL_*`` constants defined in this module. :data:`PROTOCOL_TLS` is " +"currently recommended for maximum interoperability and default value." +msgstr "" + +#: ../Doc/library/ssl.rst:1235 +msgid "" +":func:`create_default_context` lets the :mod:`ssl` module choose security " +"settings for a given purpose." +msgstr "" + +#: ../Doc/library/ssl.rst:1240 +msgid "" +"The context is created with secure default values. The options :data:" +"`OP_NO_COMPRESSION`, :data:`OP_CIPHER_SERVER_PREFERENCE`, :data:" +"`OP_SINGLE_DH_USE`, :data:`OP_SINGLE_ECDH_USE`, :data:`OP_NO_SSLv2` (except " +"for :data:`PROTOCOL_SSLv2`), and :data:`OP_NO_SSLv3` (except for :data:" +"`PROTOCOL_SSLv3`) are set by default. The initial cipher suite list contains " +"only ``HIGH`` ciphers, no ``NULL`` ciphers and no ``MD5`` ciphers (except " +"for :data:`PROTOCOL_SSLv2`)." +msgstr "" + +#: ../Doc/library/ssl.rst:1250 +msgid ":class:`SSLContext` objects have the following methods and attributes:" +msgstr "" + +#: ../Doc/library/ssl.rst:1254 +msgid "" +"Get statistics about quantities of loaded X.509 certificates, count of X.509 " +"certificates flagged as CA certificates and certificate revocation lists as " +"dictionary." +msgstr "" + +#: ../Doc/library/ssl.rst:1258 +msgid "Example for a context with one CA cert and one other cert::" +msgstr "" + +#: ../Doc/library/ssl.rst:1268 +msgid "" +"Load a private key and the corresponding certificate. The *certfile* string " +"must be the path to a single file in PEM format containing the certificate " +"as well as any number of CA certificates needed to establish the " +"certificate's authenticity. The *keyfile* string, if present, must point to " +"a file containing the private key in. Otherwise the private key will be " +"taken from *certfile* as well. See the discussion of :ref:`ssl-" +"certificates` for more information on how the certificate is stored in the " +"*certfile*." +msgstr "" + +#: ../Doc/library/ssl.rst:1277 +msgid "" +"The *password* argument may be a function to call to get the password for " +"decrypting the private key. It will only be called if the private key is " +"encrypted and a password is necessary. It will be called with no arguments, " +"and it should return a string, bytes, or bytearray. If the return value is " +"a string it will be encoded as UTF-8 before using it to decrypt the key. " +"Alternatively a string, bytes, or bytearray value may be supplied directly " +"as the *password* argument. It will be ignored if the private key is not " +"encrypted and no password is needed." +msgstr "" + +#: ../Doc/library/ssl.rst:1286 +msgid "" +"If the *password* argument is not specified and a password is required, " +"OpenSSL's built-in password prompting mechanism will be used to " +"interactively prompt the user for a password." +msgstr "" + +#: ../Doc/library/ssl.rst:1290 +msgid "" +"An :class:`SSLError` is raised if the private key doesn't match with the " +"certificate." +msgstr "" + +#: ../Doc/library/ssl.rst:1293 +msgid "New optional argument *password*." +msgstr "" + +#: ../Doc/library/ssl.rst:1298 +msgid "" +"Load a set of default \"certification authority\" (CA) certificates from " +"default locations. On Windows it loads CA certs from the ``CA`` and ``ROOT`` " +"system stores. On other systems it calls :meth:`SSLContext." +"set_default_verify_paths`. In the future the method may load CA certificates " +"from other locations, too." +msgstr "" + +#: ../Doc/library/ssl.rst:1304 +msgid "" +"The *purpose* flag specifies what kind of CA certificates are loaded. The " +"default settings :data:`Purpose.SERVER_AUTH` loads certificates, that are " +"flagged and trusted for TLS web server authentication (client side " +"sockets). :data:`Purpose.CLIENT_AUTH` loads CA certificates for client " +"certificate verification on the server side." +msgstr "" + +#: ../Doc/library/ssl.rst:1314 +msgid "" +"Load a set of \"certification authority\" (CA) certificates used to validate " +"other peers' certificates when :data:`verify_mode` is other than :data:" +"`CERT_NONE`. At least one of *cafile* or *capath* must be specified." +msgstr "" + +#: ../Doc/library/ssl.rst:1318 +msgid "" +"This method can also load certification revocation lists (CRLs) in PEM or " +"DER format. In order to make use of CRLs, :attr:`SSLContext.verify_flags` " +"must be configured properly." +msgstr "" + +#: ../Doc/library/ssl.rst:1322 +msgid "" +"The *cafile* string, if present, is the path to a file of concatenated CA " +"certificates in PEM format. See the discussion of :ref:`ssl-certificates` " +"for more information about how to arrange the certificates in this file." +msgstr "" + +#: ../Doc/library/ssl.rst:1327 +msgid "" +"The *capath* string, if present, is the path to a directory containing " +"several CA certificates in PEM format, following an `OpenSSL specific layout " +"`_." +msgstr "" + +#: ../Doc/library/ssl.rst:1332 +msgid "" +"The *cadata* object, if present, is either an ASCII string of one or more " +"PEM-encoded certificates or a :term:`bytes-like object` of DER-encoded " +"certificates. Like with *capath* extra lines around PEM-encoded certificates " +"are ignored but at least one certificate must be present." +msgstr "" + +#: ../Doc/library/ssl.rst:1337 +msgid "New optional argument *cadata*" +msgstr "" + +#: ../Doc/library/ssl.rst:1342 +msgid "" +"Get a list of loaded \"certification authority\" (CA) certificates. If the " +"``binary_form`` parameter is :const:`False` each list entry is a dict like " +"the output of :meth:`SSLSocket.getpeercert`. Otherwise the method returns a " +"list of DER-encoded certificates. The returned list does not contain " +"certificates from *capath* unless a certificate was requested and loaded by " +"a SSL connection." +msgstr "" + +#: ../Doc/library/ssl.rst:1350 +msgid "" +"Certificates in a capath directory aren't loaded unless they have been used " +"at least once." +msgstr "" + +#: ../Doc/library/ssl.rst:1357 +msgid "" +"Get a list of enabled ciphers. The list is in order of cipher priority. See :" +"meth:`SSLContext.set_ciphers`." +msgstr "" + +#: ../Doc/library/ssl.rst:1405 +msgid "On OpenSSL 1.1 and newer the cipher dict contains additional fields::" +msgstr "" + +#: ../Doc/library/ssl.rst:1407 +msgid "Availability: OpenSSL 1.0.2+" +msgstr "" + +#: ../Doc/library/ssl.rst:1413 +msgid "" +"Load a set of default \"certification authority\" (CA) certificates from a " +"filesystem path defined when building the OpenSSL library. Unfortunately, " +"there's no easy way to know whether this method succeeds: no error is " +"returned if no certificates are to be found. When the OpenSSL library is " +"provided as part of the operating system, though, it is likely to be " +"configured properly." +msgstr "" + +#: ../Doc/library/ssl.rst:1422 +msgid "" +"Set the available ciphers for sockets created with this context. It should " +"be a string in the `OpenSSL cipher list format `_. If no cipher can be selected " +"(because compile-time options or other configuration forbids use of all the " +"specified ciphers), an :class:`SSLError` will be raised." +msgstr "" + +#: ../Doc/library/ssl.rst:1430 +msgid "" +"when connected, the :meth:`SSLSocket.cipher` method of SSL sockets will give " +"the currently selected cipher." +msgstr "" + +#: ../Doc/library/ssl.rst:1435 +msgid "" +"Specify which protocols the socket should advertise during the SSL/TLS " +"handshake. It should be a list of ASCII strings, like ``['http/1.1', " +"'spdy/2']``, ordered by preference. The selection of a protocol will happen " +"during the handshake, and will play out according to :rfc:`7301`. After a " +"successful handshake, the :meth:`SSLSocket.selected_alpn_protocol` method " +"will return the agreed-upon protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:1442 +msgid "" +"This method will raise :exc:`NotImplementedError` if :data:`HAS_ALPN` is " +"False." +msgstr "" + +#: ../Doc/library/ssl.rst:1445 +msgid "" +"OpenSSL 1.1.0+ will abort the handshake and raise :exc:`SSLError` when both " +"sides support ALPN but cannot agree on a protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:1452 +msgid "" +"Specify which protocols the socket should advertise during the SSL/TLS " +"handshake. It should be a list of strings, like ``['http/1.1', 'spdy/2']``, " +"ordered by preference. The selection of a protocol will happen during the " +"handshake, and will play out according to the `NPN draft specification " +"`_. After a " +"successful handshake, the :meth:`SSLSocket.selected_npn_protocol` method " +"will return the agreed-upon protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:1460 +msgid "" +"This method will raise :exc:`NotImplementedError` if :data:`HAS_NPN` is " +"False." +msgstr "" + +#: ../Doc/library/ssl.rst:1467 +msgid "" +"Register a callback function that will be called after the TLS Client Hello " +"handshake message has been received by the SSL/TLS server when the TLS " +"client specifies a server name indication. The server name indication " +"mechanism is specified in :rfc:`6066` section 3 - Server Name Indication." +msgstr "" + +#: ../Doc/library/ssl.rst:1472 +msgid "" +"Only one callback can be set per ``SSLContext``. If *server_name_callback* " +"is ``None`` then the callback is disabled. Calling this function a " +"subsequent time will disable the previously registered callback." +msgstr "" + +#: ../Doc/library/ssl.rst:1476 +msgid "" +"The callback function, *server_name_callback*, will be called with three " +"arguments; the first being the :class:`ssl.SSLSocket`, the second is a " +"string that represents the server name that the client is intending to " +"communicate (or :const:`None` if the TLS Client Hello does not contain a " +"server name) and the third argument is the original :class:`SSLContext`. The " +"server name argument is the IDNA decoded server name." +msgstr "" + +#: ../Doc/library/ssl.rst:1483 +msgid "" +"A typical use of this callback is to change the :class:`ssl.SSLSocket`'s :" +"attr:`SSLSocket.context` attribute to a new object of type :class:" +"`SSLContext` representing a certificate chain that matches the server name." +msgstr "" + +#: ../Doc/library/ssl.rst:1488 +msgid "" +"Due to the early negotiation phase of the TLS connection, only limited " +"methods and attributes are usable like :meth:`SSLSocket." +"selected_alpn_protocol` and :attr:`SSLSocket.context`. :meth:`SSLSocket." +"getpeercert`, :meth:`SSLSocket.getpeercert`, :meth:`SSLSocket.cipher` and :" +"meth:`SSLSocket.compress` methods require that the TLS connection has " +"progressed beyond the TLS Client Hello and therefore will not contain return " +"meaningful values nor can they be called safely." +msgstr "" + +#: ../Doc/library/ssl.rst:1496 +msgid "" +"The *server_name_callback* function must return ``None`` to allow the TLS " +"negotiation to continue. If a TLS failure is required, a constant :const:" +"`ALERT_DESCRIPTION_* ` can be returned. " +"Other return values will result in a TLS fatal error with :const:" +"`ALERT_DESCRIPTION_INTERNAL_ERROR`." +msgstr "" + +#: ../Doc/library/ssl.rst:1502 +msgid "" +"If there is an IDNA decoding error on the server name, the TLS connection " +"will terminate with an :const:`ALERT_DESCRIPTION_INTERNAL_ERROR` fatal TLS " +"alert message to the client." +msgstr "" + +#: ../Doc/library/ssl.rst:1506 +msgid "" +"If an exception is raised from the *server_name_callback* function the TLS " +"connection will terminate with a fatal TLS alert message :const:" +"`ALERT_DESCRIPTION_HANDSHAKE_FAILURE`." +msgstr "" + +#: ../Doc/library/ssl.rst:1510 +msgid "" +"This method will raise :exc:`NotImplementedError` if the OpenSSL library had " +"OPENSSL_NO_TLSEXT defined when it was built." +msgstr "" + +#: ../Doc/library/ssl.rst:1517 +msgid "" +"Load the key generation parameters for Diffie-Helman (DH) key exchange. " +"Using DH key exchange improves forward secrecy at the expense of " +"computational resources (both on the server and on the client). The *dhfile* " +"parameter should be the path to a file containing DH parameters in PEM " +"format." +msgstr "" + +#: ../Doc/library/ssl.rst:1523 +msgid "" +"This setting doesn't apply to client sockets. You can also use the :data:" +"`OP_SINGLE_DH_USE` option to further improve security." +msgstr "" + +#: ../Doc/library/ssl.rst:1530 +msgid "" +"Set the curve name for Elliptic Curve-based Diffie-Hellman (ECDH) key " +"exchange. ECDH is significantly faster than regular DH while arguably as " +"secure. The *curve_name* parameter should be a string describing a well-" +"known elliptic curve, for example ``prime256v1`` for a widely supported " +"curve." +msgstr "" + +#: ../Doc/library/ssl.rst:1536 +msgid "" +"This setting doesn't apply to client sockets. You can also use the :data:" +"`OP_SINGLE_ECDH_USE` option to further improve security." +msgstr "" + +#: ../Doc/library/ssl.rst:1539 +msgid "This method is not available if :data:`HAS_ECDH` is False." +msgstr "" + +#: ../Doc/library/ssl.rst:1544 +msgid "" +"`SSL/TLS & Perfect Forward Secrecy `_" +msgstr "" + +#: ../Doc/library/ssl.rst:1545 +msgid "Vincent Bernat." +msgstr "" + +#: ../Doc/library/ssl.rst:1551 +msgid "" +"Wrap an existing Python socket *sock* and return an :class:`SSLSocket` " +"object. *sock* must be a :data:`~socket.SOCK_STREAM` socket; other socket " +"types are unsupported." +msgstr "" + +#: ../Doc/library/ssl.rst:1555 +msgid "" +"The returned SSL socket is tied to the context, its settings and " +"certificates. The parameters *server_side*, *do_handshake_on_connect* and " +"*suppress_ragged_eofs* have the same meaning as in the top-level :func:" +"`wrap_socket` function." +msgstr "" + +#: ../Doc/library/ssl.rst:1560 +msgid "" +"On client connections, the optional parameter *server_hostname* specifies " +"the hostname of the service which we are connecting to. This allows a " +"single server to host multiple SSL-based services with distinct " +"certificates, quite similarly to HTTP virtual hosts. Specifying " +"*server_hostname* will raise a :exc:`ValueError` if *server_side* is true." +msgstr "" + +#: ../Doc/library/ssl.rst:1566 +msgid "*session*, see :attr:`~SSLSocket.session`." +msgstr "" + +#: ../Doc/library/ssl.rst:1568 +msgid "" +"Always allow a server_hostname to be passed, even if OpenSSL does not have " +"SNI." +msgstr "" + +#: ../Doc/library/ssl.rst:1572 ../Doc/library/ssl.rst:1585 +msgid "*session* argument was added." +msgstr "" + +#: ../Doc/library/ssl.rst:1578 +msgid "" +"Create a new :class:`SSLObject` instance by wrapping the BIO objects " +"*incoming* and *outgoing*. The SSL routines will read input data from the " +"incoming BIO and write data to the outgoing BIO." +msgstr "" + +#: ../Doc/library/ssl.rst:1582 +msgid "" +"The *server_side*, *server_hostname* and *session* parameters have the same " +"meaning as in :meth:`SSLContext.wrap_socket`." +msgstr "" + +#: ../Doc/library/ssl.rst:1590 +msgid "" +"Get statistics about the SSL sessions created or managed by this context. A " +"dictionary is returned which maps the names of each `piece of information " +"`_ to their " +"numeric values. For example, here is the total number of hits and misses in " +"the session cache since the context was created::" +msgstr "" + +#: ../Doc/library/ssl.rst:1602 +msgid "" +"Whether to match the peer cert's hostname with :func:`match_hostname` in :" +"meth:`SSLSocket.do_handshake`. The context's :attr:`~SSLContext.verify_mode` " +"must be set to :data:`CERT_OPTIONAL` or :data:`CERT_REQUIRED`, and you must " +"pass *server_hostname* to :meth:`~SSLContext.wrap_socket` in order to match " +"the hostname." +msgstr "" + +#: ../Doc/library/ssl.rst:1625 +msgid "This features requires OpenSSL 0.9.8f or newer." +msgstr "" + +#: ../Doc/library/ssl.rst:1629 +msgid "" +"An integer representing the set of SSL options enabled on this context. The " +"default value is :data:`OP_ALL`, but you can specify other options such as :" +"data:`OP_NO_SSLv2` by ORing them together." +msgstr "" + +#: ../Doc/library/ssl.rst:1634 +msgid "" +"With versions of OpenSSL older than 0.9.8m, it is only possible to set " +"options, not to clear them. Attempting to clear an option (by resetting the " +"corresponding bits) will raise a ``ValueError``." +msgstr "" + +#: ../Doc/library/ssl.rst:1638 +msgid ":attr:`SSLContext.options` returns :class:`Options` flags:" +msgstr "" + +#: ../Doc/library/ssl.rst:1646 +msgid "" +"The protocol version chosen when constructing the context. This attribute " +"is read-only." +msgstr "" + +#: ../Doc/library/ssl.rst:1651 +msgid "" +"The flags for certificate verification operations. You can set flags like :" +"data:`VERIFY_CRL_CHECK_LEAF` by ORing them together. By default OpenSSL does " +"neither require nor verify certificate revocation lists (CRLs). Available " +"only with openssl version 0.9.8+." +msgstr "" + +#: ../Doc/library/ssl.rst:1658 +msgid ":attr:`SSLContext.verify_flags` returns :class:`VerifyFlags` flags:" +msgstr "" + +#: ../Doc/library/ssl.rst:1666 +msgid "" +"Whether to try to verify other peers' certificates and how to behave if " +"verification fails. This attribute must be one of :data:`CERT_NONE`, :data:" +"`CERT_OPTIONAL` or :data:`CERT_REQUIRED`." +msgstr "" + +#: ../Doc/library/ssl.rst:1670 +msgid ":attr:`SSLContext.verify_mode` returns :class:`VerifyMode` enum:" +msgstr "" + +#: ../Doc/library/ssl.rst:1683 +msgid "Certificates" +msgstr "" + +#: ../Doc/library/ssl.rst:1685 +msgid "" +"Certificates in general are part of a public-key / private-key system. In " +"this system, each *principal*, (which may be a machine, or a person, or an " +"organization) is assigned a unique two-part encryption key. One part of the " +"key is public, and is called the *public key*; the other part is kept " +"secret, and is called the *private key*. The two parts are related, in that " +"if you encrypt a message with one of the parts, you can decrypt it with the " +"other part, and **only** with the other part." +msgstr "" + +#: ../Doc/library/ssl.rst:1693 +msgid "" +"A certificate contains information about two principals. It contains the " +"name of a *subject*, and the subject's public key. It also contains a " +"statement by a second principal, the *issuer*, that the subject is who he " +"claims to be, and that this is indeed the subject's public key. The " +"issuer's statement is signed with the issuer's private key, which only the " +"issuer knows. However, anyone can verify the issuer's statement by finding " +"the issuer's public key, decrypting the statement with it, and comparing it " +"to the other information in the certificate. The certificate also contains " +"information about the time period over which it is valid. This is expressed " +"as two fields, called \"notBefore\" and \"notAfter\"." +msgstr "" + +#: ../Doc/library/ssl.rst:1703 +msgid "" +"In the Python use of certificates, a client or server can use a certificate " +"to prove who they are. The other side of a network connection can also be " +"required to produce a certificate, and that certificate can be validated to " +"the satisfaction of the client or server that requires such validation. The " +"connection attempt can be set to raise an exception if the validation fails. " +"Validation is done automatically, by the underlying OpenSSL framework; the " +"application need not concern itself with its mechanics. But the application " +"does usually need to provide sets of certificates to allow this process to " +"take place." +msgstr "" + +#: ../Doc/library/ssl.rst:1713 +msgid "" +"Python uses files to contain certificates. They should be formatted as \"PEM" +"\" (see :rfc:`1422`), which is a base-64 encoded form wrapped with a header " +"line and a footer line::" +msgstr "" + +#: ../Doc/library/ssl.rst:1722 +msgid "Certificate chains" +msgstr "" + +#: ../Doc/library/ssl.rst:1724 +msgid "" +"The Python files which contain certificates can contain a sequence of " +"certificates, sometimes called a *certificate chain*. This chain should " +"start with the specific certificate for the principal who \"is\" the client " +"or server, and then the certificate for the issuer of that certificate, and " +"then the certificate for the issuer of *that* certificate, and so on up the " +"chain till you get to a certificate which is *self-signed*, that is, a " +"certificate which has the same subject and issuer, sometimes called a *root " +"certificate*. The certificates should just be concatenated together in the " +"certificate file. For example, suppose we had a three certificate chain, " +"from our server certificate to the certificate of the certification " +"authority that signed our server certificate, to the root certificate of the " +"agency which issued the certification authority's certificate::" +msgstr "" + +#: ../Doc/library/ssl.rst:1748 +msgid "CA certificates" +msgstr "" + +#: ../Doc/library/ssl.rst:1750 +msgid "" +"If you are going to require validation of the other side of the connection's " +"certificate, you need to provide a \"CA certs\" file, filled with the " +"certificate chains for each issuer you are willing to trust. Again, this " +"file just contains these chains concatenated together. For validation, " +"Python will use the first chain it finds in the file which matches. The " +"platform's certificates file can be used by calling :meth:`SSLContext." +"load_default_certs`, this is done automatically with :func:`." +"create_default_context`." +msgstr "" + +#: ../Doc/library/ssl.rst:1759 +msgid "Combined key and certificate" +msgstr "" + +#: ../Doc/library/ssl.rst:1761 +msgid "" +"Often the private key is stored in the same file as the certificate; in this " +"case, only the ``certfile`` parameter to :meth:`SSLContext.load_cert_chain` " +"and :func:`wrap_socket` needs to be passed. If the private key is stored " +"with the certificate, it should come before the first certificate in the " +"certificate chain::" +msgstr "" + +#: ../Doc/library/ssl.rst:1775 +msgid "Self-signed certificates" +msgstr "" + +#: ../Doc/library/ssl.rst:1777 +msgid "" +"If you are going to create a server that provides SSL-encrypted connection " +"services, you will need to acquire a certificate for that service. There " +"are many ways of acquiring appropriate certificates, such as buying one from " +"a certification authority. Another common practice is to generate a self-" +"signed certificate. The simplest way to do this is with the OpenSSL " +"package, using something like the following::" +msgstr "" + +#: ../Doc/library/ssl.rst:1806 +msgid "" +"The disadvantage of a self-signed certificate is that it is its own root " +"certificate, and no one else will have it in their cache of known (and " +"trusted) root certificates." +msgstr "" + +#: ../Doc/library/ssl.rst:1815 +msgid "Testing for SSL support" +msgstr "" + +#: ../Doc/library/ssl.rst:1817 +msgid "" +"To test for the presence of SSL support in a Python installation, user code " +"should use the following idiom::" +msgstr "" + +#: ../Doc/library/ssl.rst:1828 +msgid "Client-side operation" +msgstr "" + +#: ../Doc/library/ssl.rst:1830 +msgid "" +"This example creates a SSL context with the recommended security settings " +"for client sockets, including automatic certificate verification::" +msgstr "" + +#: ../Doc/library/ssl.rst:1835 +msgid "" +"If you prefer to tune security settings yourself, you might create a context " +"from scratch (but beware that you might not get the settings right)::" +msgstr "" + +#: ../Doc/library/ssl.rst:1844 +msgid "" +"(this snippet assumes your operating system places a bundle of all CA " +"certificates in ``/etc/ssl/certs/ca-bundle.crt``; if not, you'll get an " +"error and have to adjust the location)" +msgstr "" + +#: ../Doc/library/ssl.rst:1848 +msgid "" +"When you use the context to connect to a server, :const:`CERT_REQUIRED` " +"validates the server certificate: it ensures that the server certificate was " +"signed with one of the CA certificates, and checks the signature for " +"correctness::" +msgstr "" + +#: ../Doc/library/ssl.rst:1857 +msgid "You may then fetch the certificate::" +msgstr "" + +#: ../Doc/library/ssl.rst:1861 +msgid "" +"Visual inspection shows that the certificate does identify the desired " +"service (that is, the HTTPS host ``www.python.org``)::" +msgstr "" + +#: ../Doc/library/ssl.rst:1904 +msgid "" +"Now the SSL channel is established and the certificate verified, you can " +"proceed to talk with the server::" +msgstr "" + +#: ../Doc/library/ssl.rst:1931 +msgid "Server-side operation" +msgstr "" + +#: ../Doc/library/ssl.rst:1933 +msgid "" +"For server operation, typically you'll need to have a server certificate, " +"and private key, each in a file. You'll first create a context holding the " +"key and the certificate, so that clients can check your authenticity. Then " +"you'll open a socket, bind it to a port, call :meth:`listen` on it, and " +"start waiting for clients to connect::" +msgstr "" + +#: ../Doc/library/ssl.rst:1948 +msgid "" +"When a client connects, you'll call :meth:`accept` on the socket to get the " +"new socket from the other end, and use the context's :meth:`SSLContext." +"wrap_socket` method to create a server-side SSL socket for the connection::" +msgstr "" + +#: ../Doc/library/ssl.rst:1961 +msgid "" +"Then you'll read data from the ``connstream`` and do something with it till " +"you are finished with the client (or the client is finished with you)::" +msgstr "" + +#: ../Doc/library/ssl.rst:1975 +msgid "" +"And go back to listening for new client connections (of course, a real " +"server would probably handle each client connection in a separate thread, or " +"put the sockets in :ref:`non-blocking mode ` and use an " +"event loop)." +msgstr "" + +#: ../Doc/library/ssl.rst:1983 +msgid "Notes on non-blocking sockets" +msgstr "" + +#: ../Doc/library/ssl.rst:1985 +msgid "" +"SSL sockets behave slightly different than regular sockets in non-blocking " +"mode. When working with non-blocking sockets, there are thus several things " +"you need to be aware of:" +msgstr "" + +#: ../Doc/library/ssl.rst:1989 +msgid "" +"Most :class:`SSLSocket` methods will raise either :exc:`SSLWantWriteError` " +"or :exc:`SSLWantReadError` instead of :exc:`BlockingIOError` if an I/O " +"operation would block. :exc:`SSLWantReadError` will be raised if a read " +"operation on the underlying socket is necessary, and :exc:" +"`SSLWantWriteError` for a write operation on the underlying socket. Note " +"that attempts to *write* to an SSL socket may require *reading* from the " +"underlying socket first, and attempts to *read* from the SSL socket may " +"require a prior *write* to the underlying socket." +msgstr "" + +#: ../Doc/library/ssl.rst:2001 +msgid "" +"In earlier Python versions, the :meth:`!SSLSocket.send` method returned zero " +"instead of raising :exc:`SSLWantWriteError` or :exc:`SSLWantReadError`." +msgstr "" + +#: ../Doc/library/ssl.rst:2005 +msgid "" +"Calling :func:`~select.select` tells you that the OS-level socket can be " +"read from (or written to), but it does not imply that there is sufficient " +"data at the upper SSL layer. For example, only part of an SSL frame might " +"have arrived. Therefore, you must be ready to handle :meth:`SSLSocket.recv` " +"and :meth:`SSLSocket.send` failures, and retry after another call to :func:" +"`~select.select`." +msgstr "" + +#: ../Doc/library/ssl.rst:2012 +msgid "" +"Conversely, since the SSL layer has its own framing, a SSL socket may still " +"have data available for reading without :func:`~select.select` being aware " +"of it. Therefore, you should first call :meth:`SSLSocket.recv` to drain any " +"potentially available data, and then only block on a :func:`~select.select` " +"call if still necessary." +msgstr "" + +#: ../Doc/library/ssl.rst:2018 +msgid "" +"(of course, similar provisions apply when using other primitives such as :" +"func:`~select.poll`, or those in the :mod:`selectors` module)" +msgstr "" + +#: ../Doc/library/ssl.rst:2021 +msgid "" +"The SSL handshake itself will be non-blocking: the :meth:`SSLSocket." +"do_handshake` method has to be retried until it returns successfully. Here " +"is a synopsis using :func:`~select.select` to wait for the socket's " +"readiness::" +msgstr "" + +#: ../Doc/library/ssl.rst:2037 +msgid "" +"The :mod:`asyncio` module supports :ref:`non-blocking SSL sockets ` and provides a higher level API. It polls for events using " +"the :mod:`selectors` module and handles :exc:`SSLWantWriteError`, :exc:" +"`SSLWantReadError` and :exc:`BlockingIOError` exceptions. It runs the SSL " +"handshake asynchronously as well." +msgstr "" + +#: ../Doc/library/ssl.rst:2046 +msgid "Memory BIO Support" +msgstr "" + +#: ../Doc/library/ssl.rst:2050 +msgid "" +"Ever since the SSL module was introduced in Python 2.6, the :class:" +"`SSLSocket` class has provided two related but distinct areas of " +"functionality:" +msgstr "" + +#: ../Doc/library/ssl.rst:2053 +msgid "SSL protocol handling" +msgstr "" + +#: ../Doc/library/ssl.rst:2054 +msgid "Network IO" +msgstr "" + +#: ../Doc/library/ssl.rst:2056 +msgid "" +"The network IO API is identical to that provided by :class:`socket.socket`, " +"from which :class:`SSLSocket` also inherits. This allows an SSL socket to be " +"used as a drop-in replacement for a regular socket, making it very easy to " +"add SSL support to an existing application." +msgstr "" + +#: ../Doc/library/ssl.rst:2061 +msgid "" +"Combining SSL protocol handling and network IO usually works well, but there " +"are some cases where it doesn't. An example is async IO frameworks that want " +"to use a different IO multiplexing model than the \"select/poll on a file " +"descriptor\" (readiness based) model that is assumed by :class:`socket." +"socket` and by the internal OpenSSL socket IO routines. This is mostly " +"relevant for platforms like Windows where this model is not efficient. For " +"this purpose, a reduced scope variant of :class:`SSLSocket` called :class:" +"`SSLObject` is provided." +msgstr "" + +#: ../Doc/library/ssl.rst:2072 +msgid "" +"A reduced-scope variant of :class:`SSLSocket` representing an SSL protocol " +"instance that does not contain any network IO methods. This class is " +"typically used by framework authors that want to implement asynchronous IO " +"for SSL through memory buffers." +msgstr "" + +#: ../Doc/library/ssl.rst:2077 +msgid "" +"This class implements an interface on top of a low-level SSL object as " +"implemented by OpenSSL. This object captures the state of an SSL connection " +"but does not provide any network IO itself. IO needs to be performed through " +"separate \"BIO\" objects which are OpenSSL's IO abstraction layer." +msgstr "" + +#: ../Doc/library/ssl.rst:2082 +msgid "" +"An :class:`SSLObject` instance can be created using the :meth:`~SSLContext." +"wrap_bio` method. This method will create the :class:`SSLObject` instance " +"and bind it to a pair of BIOs. The *incoming* BIO is used to pass data from " +"Python to the SSL protocol instance, while the *outgoing* BIO is used to " +"pass data the other way around." +msgstr "" + +#: ../Doc/library/ssl.rst:2088 +msgid "The following methods are available:" +msgstr "" + +#: ../Doc/library/ssl.rst:2090 +msgid ":attr:`~SSLSocket.context`" +msgstr "" + +#: ../Doc/library/ssl.rst:2091 +msgid ":attr:`~SSLSocket.server_side`" +msgstr "" + +#: ../Doc/library/ssl.rst:2092 +msgid ":attr:`~SSLSocket.server_hostname`" +msgstr "" + +#: ../Doc/library/ssl.rst:2093 +msgid ":attr:`~SSLSocket.session`" +msgstr "" + +#: ../Doc/library/ssl.rst:2094 +msgid ":attr:`~SSLSocket.session_reused`" +msgstr "" + +#: ../Doc/library/ssl.rst:2095 +msgid ":meth:`~SSLSocket.read`" +msgstr "" + +#: ../Doc/library/ssl.rst:2096 +msgid ":meth:`~SSLSocket.write`" +msgstr "" + +#: ../Doc/library/ssl.rst:2097 +msgid ":meth:`~SSLSocket.getpeercert`" +msgstr "" + +#: ../Doc/library/ssl.rst:2098 +msgid ":meth:`~SSLSocket.selected_npn_protocol`" +msgstr "" + +#: ../Doc/library/ssl.rst:2099 +msgid ":meth:`~SSLSocket.cipher`" +msgstr "" + +#: ../Doc/library/ssl.rst:2100 +msgid ":meth:`~SSLSocket.shared_ciphers`" +msgstr "" + +#: ../Doc/library/ssl.rst:2101 +msgid ":meth:`~SSLSocket.compression`" +msgstr "" + +#: ../Doc/library/ssl.rst:2102 +msgid ":meth:`~SSLSocket.pending`" +msgstr "" + +#: ../Doc/library/ssl.rst:2103 +msgid ":meth:`~SSLSocket.do_handshake`" +msgstr "" + +#: ../Doc/library/ssl.rst:2104 +msgid ":meth:`~SSLSocket.unwrap`" +msgstr "" + +#: ../Doc/library/ssl.rst:2105 +msgid ":meth:`~SSLSocket.get_channel_binding`" +msgstr "" + +#: ../Doc/library/ssl.rst:2107 +msgid "" +"When compared to :class:`SSLSocket`, this object lacks the following " +"features:" +msgstr "" + +#: ../Doc/library/ssl.rst:2110 +msgid "" +"Any form of network IO incluging methods such as ``recv()`` and ``send()``." +msgstr "" + +#: ../Doc/library/ssl.rst:2113 +msgid "" +"There is no *do_handshake_on_connect* machinery. You must always manually " +"call :meth:`~SSLSocket.do_handshake` to start the handshake." +msgstr "" + +#: ../Doc/library/ssl.rst:2116 +msgid "" +"There is no handling of *suppress_ragged_eofs*. All end-of-file conditions " +"that are in violation of the protocol are reported via the :exc:" +"`SSLEOFError` exception." +msgstr "" + +#: ../Doc/library/ssl.rst:2120 +msgid "" +"The method :meth:`~SSLSocket.unwrap` call does not return anything, unlike " +"for an SSL socket where it returns the underlying socket." +msgstr "" + +#: ../Doc/library/ssl.rst:2123 +msgid "" +"The *server_name_callback* callback passed to :meth:`SSLContext." +"set_servername_callback` will get an :class:`SSLObject` instance instead of " +"a :class:`SSLSocket` instance as its first parameter." +msgstr "" + +#: ../Doc/library/ssl.rst:2127 +msgid "Some notes related to the use of :class:`SSLObject`:" +msgstr "" + +#: ../Doc/library/ssl.rst:2129 +msgid "" +"All IO on an :class:`SSLObject` is :ref:`non-blocking `. " +"This means that for example :meth:`~SSLSocket.read` will raise an :exc:" +"`SSLWantReadError` if it needs more data than the incoming BIO has available." +msgstr "" + +#: ../Doc/library/ssl.rst:2134 +msgid "" +"There is no module-level ``wrap_bio()`` call like there is for :meth:" +"`~SSLContext.wrap_socket`. An :class:`SSLObject` is always created via an :" +"class:`SSLContext`." +msgstr "" + +#: ../Doc/library/ssl.rst:2138 +msgid "" +"An SSLObject communicates with the outside world using memory buffers. The " +"class :class:`MemoryBIO` provides a memory buffer that can be used for this " +"purpose. It wraps an OpenSSL memory BIO (Basic IO) object:" +msgstr "" + +#: ../Doc/library/ssl.rst:2144 +msgid "" +"A memory buffer that can be used to pass data between Python and an SSL " +"protocol instance." +msgstr "" + +#: ../Doc/library/ssl.rst:2149 +msgid "Return the number of bytes currently in the memory buffer." +msgstr "" + +#: ../Doc/library/ssl.rst:2153 +msgid "" +"A boolean indicating whether the memory BIO is current at the end-of-file " +"position." +msgstr "" + +#: ../Doc/library/ssl.rst:2158 +msgid "" +"Read up to *n* bytes from the memory buffer. If *n* is not specified or " +"negative, all bytes are returned." +msgstr "" + +#: ../Doc/library/ssl.rst:2163 +msgid "" +"Write the bytes from *buf* to the memory BIO. The *buf* argument must be an " +"object supporting the buffer protocol." +msgstr "" + +#: ../Doc/library/ssl.rst:2166 +msgid "" +"The return value is the number of bytes written, which is always equal to " +"the length of *buf*." +msgstr "" + +#: ../Doc/library/ssl.rst:2171 +msgid "" +"Write an EOF marker to the memory BIO. After this method has been called, it " +"is illegal to call :meth:`~MemoryBIO.write`. The attribute :attr:`eof` will " +"become true after all data currently in the buffer has been read." +msgstr "" + +#: ../Doc/library/ssl.rst:2177 +msgid "SSL session" +msgstr "" + +#: ../Doc/library/ssl.rst:2183 +msgid "Session object used by :attr:`~SSLSocket.session`." +msgstr "" + +#: ../Doc/library/ssl.rst:2195 +msgid "Security considerations" +msgstr "" + +#: ../Doc/library/ssl.rst:2198 +msgid "Best defaults" +msgstr "" + +#: ../Doc/library/ssl.rst:2200 +msgid "" +"For **client use**, if you don't have any special requirements for your " +"security policy, it is highly recommended that you use the :func:" +"`create_default_context` function to create your SSL context. It will load " +"the system's trusted CA certificates, enable certificate validation and " +"hostname checking, and try to choose reasonably secure protocol and cipher " +"settings." +msgstr "" + +#: ../Doc/library/ssl.rst:2207 +msgid "" +"For example, here is how you would use the :class:`smtplib.SMTP` class to " +"create a trusted, secure connection to a SMTP server::" +msgstr "" + +#: ../Doc/library/ssl.rst:2216 +msgid "" +"If a client certificate is needed for the connection, it can be added with :" +"meth:`SSLContext.load_cert_chain`." +msgstr "" + +#: ../Doc/library/ssl.rst:2219 +msgid "" +"By contrast, if you create the SSL context by calling the :class:" +"`SSLContext` constructor yourself, it will not have certificate validation " +"nor hostname checking enabled by default. If you do so, please read the " +"paragraphs below to achieve a good security level." +msgstr "" + +#: ../Doc/library/ssl.rst:2225 +msgid "Manual settings" +msgstr "" + +#: ../Doc/library/ssl.rst:2228 +msgid "Verifying certificates" +msgstr "" + +#: ../Doc/library/ssl.rst:2230 +msgid "" +"When calling the :class:`SSLContext` constructor directly, :const:" +"`CERT_NONE` is the default. Since it does not authenticate the other peer, " +"it can be insecure, especially in client mode where most of time you would " +"like to ensure the authenticity of the server you're talking to. Therefore, " +"when in client mode, it is highly recommended to use :const:" +"`CERT_REQUIRED`. However, it is in itself not sufficient; you also have to " +"check that the server certificate, which can be obtained by calling :meth:" +"`SSLSocket.getpeercert`, matches the desired service. For many protocols " +"and applications, the service can be identified by the hostname; in this " +"case, the :func:`match_hostname` function can be used. This common check is " +"automatically performed when :attr:`SSLContext.check_hostname` is enabled." +msgstr "" + +#: ../Doc/library/ssl.rst:2243 +msgid "" +"In server mode, if you want to authenticate your clients using the SSL layer " +"(rather than using a higher-level authentication mechanism), you'll also " +"have to specify :const:`CERT_REQUIRED` and similarly check the client " +"certificate." +msgstr "" + +#: ../Doc/library/ssl.rst:2249 +msgid "" +"In client mode, :const:`CERT_OPTIONAL` and :const:`CERT_REQUIRED` are " +"equivalent unless anonymous ciphers are enabled (they are disabled by " +"default)." +msgstr "" + +#: ../Doc/library/ssl.rst:2254 +msgid "Protocol versions" +msgstr "" + +#: ../Doc/library/ssl.rst:2256 +msgid "" +"SSL versions 2 and 3 are considered insecure and are therefore dangerous to " +"use. If you want maximum compatibility between clients and servers, it is " +"recommended to use :const:`PROTOCOL_TLS_CLIENT` or :const:" +"`PROTOCOL_TLS_SERVER` as the protocol version. SSLv2 and SSLv3 are disabled " +"by default." +msgstr "" + +#: ../Doc/library/ssl.rst:2267 +msgid "" +"The SSL context created above will only allow TLSv1.2 and later (if " +"supported by your system) connections to a server. :const:" +"`PROTOCOL_TLS_CLIENT` implies certificate validation and hostname checks by " +"default. You have to load certificates into the context." +msgstr "" + +#: ../Doc/library/ssl.rst:2274 +msgid "Cipher selection" +msgstr "" + +#: ../Doc/library/ssl.rst:2276 +msgid "" +"If you have advanced security requirements, fine-tuning of the ciphers " +"enabled when negotiating a SSL session is possible through the :meth:" +"`SSLContext.set_ciphers` method. Starting from Python 3.2.3, the ssl module " +"disables certain weak ciphers by default, but you may want to further " +"restrict the cipher choice. Be sure to read OpenSSL's documentation about " +"the `cipher list format `_. If you want to check which ciphers are enabled " +"by a given cipher list, use :meth:`SSLContext.get_ciphers` or the ``openssl " +"ciphers`` command on your system." +msgstr "" + +#: ../Doc/library/ssl.rst:2287 +msgid "Multi-processing" +msgstr "" + +#: ../Doc/library/ssl.rst:2289 +msgid "" +"If using this module as part of a multi-processed application (using, for " +"example the :mod:`multiprocessing` or :mod:`concurrent.futures` modules), be " +"aware that OpenSSL's internal random number generator does not properly " +"handle forked processes. Applications must change the PRNG state of the " +"parent process if they use any SSL feature with :func:`os.fork`. Any " +"successful call of :func:`~ssl.RAND_add`, :func:`~ssl.RAND_bytes` or :func:" +"`~ssl.RAND_pseudo_bytes` is sufficient." +msgstr "" + +#: ../Doc/library/ssl.rst:2301 +msgid "Class :class:`socket.socket`" +msgstr "" + +#: ../Doc/library/ssl.rst:2301 +msgid "Documentation of underlying :mod:`socket` class" +msgstr "" + +#: ../Doc/library/ssl.rst:2304 +msgid "" +"`SSL/TLS Strong Encryption: An Introduction `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2304 +msgid "Intro from the Apache webserver documentation" +msgstr "" + +#: ../Doc/library/ssl.rst:2307 +msgid "" +"`RFC 1422: Privacy Enhancement for Internet Electronic Mail: Part II: " +"Certificate-Based Key Management `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2307 +msgid "Steve Kent" +msgstr "" + +#: ../Doc/library/ssl.rst:2310 +msgid "" +"`RFC 1750: Randomness Recommendations for Security `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2310 +msgid "D. Eastlake et. al." +msgstr "" + +#: ../Doc/library/ssl.rst:2313 +msgid "" +"`RFC 3280: Internet X.509 Public Key Infrastructure Certificate and CRL " +"Profile `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2313 +msgid "Housley et. al." +msgstr "" + +#: ../Doc/library/ssl.rst:2316 +msgid "" +"`RFC 4366: Transport Layer Security (TLS) Extensions `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2316 +msgid "Blake-Wilson et. al." +msgstr "" + +#: ../Doc/library/ssl.rst:2319 +msgid "" +"`RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2319 +msgid "T. Dierks et. al." +msgstr "" + +#: ../Doc/library/ssl.rst:2322 +msgid "" +"`RFC 6066: Transport Layer Security (TLS) Extensions `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2322 +msgid "D. Eastlake" +msgstr "" + +#: ../Doc/library/ssl.rst:2324 +msgid "" +"`IANA TLS: Transport Layer Security (TLS) Parameters `_" +msgstr "" + +#: ../Doc/library/ssl.rst:2325 +msgid "IANA" +msgstr "" + +#: ../Doc/library/stat.rst:2 +msgid ":mod:`stat` --- Interpreting :func:`~os.stat` results" +msgstr "" + +#: ../Doc/library/stat.rst:10 +msgid "**Source code:** :source:`Lib/stat.py`" +msgstr "" + +#: ../Doc/library/stat.rst:14 +msgid "" +"The :mod:`stat` module defines constants and functions for interpreting the " +"results of :func:`os.stat`, :func:`os.fstat` and :func:`os.lstat` (if they " +"exist). For complete details about the :c:func:`stat`, :c:func:`fstat` and :" +"c:func:`lstat` calls, consult the documentation for your system." +msgstr "" + +#: ../Doc/library/stat.rst:19 +msgid "The stat module is backed by a C implementation." +msgstr "" + +#: ../Doc/library/stat.rst:22 +msgid "" +"The :mod:`stat` module defines the following functions to test for specific " +"file types:" +msgstr "" + +#: ../Doc/library/stat.rst:28 +msgid "Return non-zero if the mode is from a directory." +msgstr "" + +#: ../Doc/library/stat.rst:33 +msgid "Return non-zero if the mode is from a character special device file." +msgstr "" + +#: ../Doc/library/stat.rst:38 +msgid "Return non-zero if the mode is from a block special device file." +msgstr "" + +#: ../Doc/library/stat.rst:43 +msgid "Return non-zero if the mode is from a regular file." +msgstr "" + +#: ../Doc/library/stat.rst:48 +msgid "Return non-zero if the mode is from a FIFO (named pipe)." +msgstr "" + +#: ../Doc/library/stat.rst:53 +msgid "Return non-zero if the mode is from a symbolic link." +msgstr "" + +#: ../Doc/library/stat.rst:58 +msgid "Return non-zero if the mode is from a socket." +msgstr "" + +#: ../Doc/library/stat.rst:62 +msgid "Return non-zero if the mode is from a door." +msgstr "" + +#: ../Doc/library/stat.rst:68 +msgid "Return non-zero if the mode is from an event port." +msgstr "" + +#: ../Doc/library/stat.rst:74 +msgid "Return non-zero if the mode is from a whiteout." +msgstr "" + +#: ../Doc/library/stat.rst:78 +msgid "" +"Two additional functions are defined for more general manipulation of the " +"file's mode:" +msgstr "" + +#: ../Doc/library/stat.rst:84 +msgid "" +"Return the portion of the file's mode that can be set by :func:`os.chmod`\\ " +"---that is, the file's permission bits, plus the sticky bit, set-group-id, " +"and set-user-id bits (on systems that support them)." +msgstr "" + +#: ../Doc/library/stat.rst:91 +msgid "" +"Return the portion of the file's mode that describes the file type (used by " +"the :func:`S_IS\\*` functions above)." +msgstr "" + +#: ../Doc/library/stat.rst:94 +msgid "" +"Normally, you would use the :func:`os.path.is\\*` functions for testing the " +"type of a file; the functions here are useful when you are doing multiple " +"tests of the same file and wish to avoid the overhead of the :c:func:`stat` " +"system call for each test. These are also useful when checking for " +"information about a file that isn't handled by :mod:`os.path`, like the " +"tests for block and character devices." +msgstr "" + +#: ../Doc/library/stat.rst:129 +msgid "" +"An additional utility function is provided to convert a file's mode in a " +"human readable string:" +msgstr "" + +#: ../Doc/library/stat.rst:134 +msgid "Convert a file's mode to a string of the form '-rwxrwxrwx'." +msgstr "" + +#: ../Doc/library/stat.rst:138 +msgid "" +"The function supports :data:`S_IFDOOR`, :data:`S_IFPORT` and :data:`S_IFWHT`." +msgstr "" + +#: ../Doc/library/stat.rst:143 +msgid "" +"All the variables below are simply symbolic indexes into the 10-tuple " +"returned by :func:`os.stat`, :func:`os.fstat` or :func:`os.lstat`." +msgstr "" + +#: ../Doc/library/stat.rst:149 +msgid "Inode protection mode." +msgstr "" + +#: ../Doc/library/stat.rst:159 +msgid "Device inode resides on." +msgstr "" + +#: ../Doc/library/stat.rst:164 +msgid "Number of links to the inode." +msgstr "" + +#: ../Doc/library/stat.rst:169 +msgid "User id of the owner." +msgstr "" + +#: ../Doc/library/stat.rst:174 +msgid "Group id of the owner." +msgstr "" + +#: ../Doc/library/stat.rst:179 +msgid "" +"Size in bytes of a plain file; amount of data waiting on some special files." +msgstr "" + +#: ../Doc/library/stat.rst:184 +msgid "Time of last access." +msgstr "" + +#: ../Doc/library/stat.rst:189 ../Doc/library/tarfile.rst:550 +msgid "Time of last modification." +msgstr "" + +#: ../Doc/library/stat.rst:194 +msgid "" +"The \"ctime\" as reported by the operating system. On some systems (like " +"Unix) is the time of the last metadata change, and, on others (like " +"Windows), is the creation time (see platform documentation for details)." +msgstr "" + +#: ../Doc/library/stat.rst:198 +msgid "" +"The interpretation of \"file size\" changes according to the file type. For " +"plain files this is the size of the file in bytes. For FIFOs and sockets " +"under most flavors of Unix (including Linux in particular), the \"size\" is " +"the number of bytes waiting to be read at the time of the call to :func:`os." +"stat`, :func:`os.fstat`, or :func:`os.lstat`; this can sometimes be useful, " +"especially for polling one of these special files after a non-blocking " +"open. The meaning of the size field for other character and block devices " +"varies more, depending on the implementation of the underlying system call." +msgstr "" + +#: ../Doc/library/stat.rst:207 +msgid "The variables below define the flags used in the :data:`ST_MODE` field." +msgstr "" + +#: ../Doc/library/stat.rst:209 +msgid "" +"Use of the functions above is more portable than use of the first set of " +"flags:" +msgstr "" + +#: ../Doc/library/stat.rst:213 +msgid "Socket." +msgstr "" + +#: ../Doc/library/stat.rst:217 +msgid "Symbolic link." +msgstr "" + +#: ../Doc/library/stat.rst:221 +msgid "Regular file." +msgstr "" + +#: ../Doc/library/stat.rst:225 +msgid "Block device." +msgstr "" + +#: ../Doc/library/stat.rst:229 +msgid "Directory." +msgstr "" + +#: ../Doc/library/stat.rst:233 +msgid "Character device." +msgstr "" + +#: ../Doc/library/stat.rst:237 +msgid "FIFO." +msgstr "" + +#: ../Doc/library/stat.rst:241 +msgid "Door." +msgstr "" + +#: ../Doc/library/stat.rst:247 +msgid "Event port." +msgstr "" + +#: ../Doc/library/stat.rst:253 +msgid "Whiteout." +msgstr "" + +#: ../Doc/library/stat.rst:259 +msgid "" +":data:`S_IFDOOR`, :data:`S_IFPORT` or :data:`S_IFWHT` are defined as 0 when " +"the platform does not have support for the file types." +msgstr "" + +#: ../Doc/library/stat.rst:262 +msgid "" +"The following flags can also be used in the *mode* argument of :func:`os." +"chmod`:" +msgstr "" + +#: ../Doc/library/stat.rst:266 +msgid "Set UID bit." +msgstr "" + +#: ../Doc/library/stat.rst:270 +msgid "" +"Set-group-ID bit. This bit has several special uses. For a directory it " +"indicates that BSD semantics is to be used for that directory: files created " +"there inherit their group ID from the directory, not from the effective " +"group ID of the creating process, and directories created there will also " +"get the :data:`S_ISGID` bit set. For a file that does not have the group " +"execution bit (:data:`S_IXGRP`) set, the set-group-ID bit indicates " +"mandatory file/record locking (see also :data:`S_ENFMT`)." +msgstr "" + +#: ../Doc/library/stat.rst:281 +msgid "" +"Sticky bit. When this bit is set on a directory it means that a file in " +"that directory can be renamed or deleted only by the owner of the file, by " +"the owner of the directory, or by a privileged process." +msgstr "" + +#: ../Doc/library/stat.rst:287 +msgid "Mask for file owner permissions." +msgstr "" + +#: ../Doc/library/stat.rst:291 +msgid "Owner has read permission." +msgstr "" + +#: ../Doc/library/stat.rst:295 +msgid "Owner has write permission." +msgstr "" + +#: ../Doc/library/stat.rst:299 +msgid "Owner has execute permission." +msgstr "" + +#: ../Doc/library/stat.rst:303 +msgid "Mask for group permissions." +msgstr "" + +#: ../Doc/library/stat.rst:307 +msgid "Group has read permission." +msgstr "" + +#: ../Doc/library/stat.rst:311 +msgid "Group has write permission." +msgstr "" + +#: ../Doc/library/stat.rst:315 +msgid "Group has execute permission." +msgstr "" + +#: ../Doc/library/stat.rst:319 +msgid "Mask for permissions for others (not in group)." +msgstr "" + +#: ../Doc/library/stat.rst:323 +msgid "Others have read permission." +msgstr "" + +#: ../Doc/library/stat.rst:327 +msgid "Others have write permission." +msgstr "" + +#: ../Doc/library/stat.rst:331 +msgid "Others have execute permission." +msgstr "" + +#: ../Doc/library/stat.rst:335 +msgid "" +"System V file locking enforcement. This flag is shared with :data:" +"`S_ISGID`: file/record locking is enforced on files that do not have the " +"group execution bit (:data:`S_IXGRP`) set." +msgstr "" + +#: ../Doc/library/stat.rst:341 +msgid "Unix V7 synonym for :data:`S_IRUSR`." +msgstr "" + +#: ../Doc/library/stat.rst:345 +msgid "Unix V7 synonym for :data:`S_IWUSR`." +msgstr "" + +#: ../Doc/library/stat.rst:349 +msgid "Unix V7 synonym for :data:`S_IXUSR`." +msgstr "" + +#: ../Doc/library/stat.rst:351 +msgid "" +"The following flags can be used in the *flags* argument of :func:`os." +"chflags`:" +msgstr "" + +#: ../Doc/library/stat.rst:355 +msgid "Do not dump the file." +msgstr "" + +#: ../Doc/library/stat.rst:359 ../Doc/library/stat.rst:387 +msgid "The file may not be changed." +msgstr "" + +#: ../Doc/library/stat.rst:363 ../Doc/library/stat.rst:391 +msgid "The file may only be appended to." +msgstr "" + +#: ../Doc/library/stat.rst:367 +msgid "The directory is opaque when viewed through a union stack." +msgstr "" + +#: ../Doc/library/stat.rst:371 ../Doc/library/stat.rst:395 +msgid "The file may not be renamed or deleted." +msgstr "" + +#: ../Doc/library/stat.rst:375 +msgid "The file is stored compressed (Mac OS X 10.6+)." +msgstr "" + +#: ../Doc/library/stat.rst:379 +msgid "The file should not be displayed in a GUI (Mac OS X 10.5+)." +msgstr "" + +#: ../Doc/library/stat.rst:383 +msgid "The file may be archived." +msgstr "" + +#: ../Doc/library/stat.rst:399 +msgid "The file is a snapshot file." +msgstr "" + +#: ../Doc/library/stat.rst:401 +msgid "" +"See the \\*BSD or Mac OS systems man page :manpage:`chflags(2)` for more " +"information." +msgstr "" + +#: ../Doc/library/stat.rst:403 +msgid "" +"On Windows, the following file attribute constants are available for use " +"when testing bits in the ``st_file_attributes`` member returned by :func:`os." +"stat`. See the `Windows API documentation `_ for more detail on the meaning of " +"these constants." +msgstr "" + +#: ../Doc/library/statistics.rst:2 +msgid ":mod:`statistics` --- Mathematical statistics functions" +msgstr "" + +#: ../Doc/library/statistics.rst:12 +msgid "**Source code:** :source:`Lib/statistics.py`" +msgstr "" + +#: ../Doc/library/statistics.rst:21 +msgid "" +"This module provides functions for calculating mathematical statistics of " +"numeric (:class:`Real`-valued) data." +msgstr "" + +#: ../Doc/library/statistics.rst:26 +msgid "" +"Unless explicitly noted otherwise, these functions support :class:`int`, :" +"class:`float`, :class:`decimal.Decimal` and :class:`fractions.Fraction`. " +"Behaviour with other types (whether in the numeric tower or not) is " +"currently unsupported. Mixed types are also undefined and implementation-" +"dependent. If your input data consists of mixed types, you may be able to " +"use :func:`map` to ensure a consistent result, e.g. ``map(float, " +"input_data)``." +msgstr "" + +#: ../Doc/library/statistics.rst:35 +msgid "Averages and measures of central location" +msgstr "" + +#: ../Doc/library/statistics.rst:37 +msgid "" +"These functions calculate an average or typical value from a population or " +"sample." +msgstr "" + +#: ../Doc/library/statistics.rst:41 +msgid ":func:`mean`" +msgstr "" + +#: ../Doc/library/statistics.rst:41 +msgid "Arithmetic mean (\"average\") of data." +msgstr "" + +#: ../Doc/library/statistics.rst:42 +msgid ":func:`harmonic_mean`" +msgstr "" + +#: ../Doc/library/statistics.rst:42 +msgid "Harmonic mean of data." +msgstr "" + +#: ../Doc/library/statistics.rst:43 +msgid ":func:`median`" +msgstr "" + +#: ../Doc/library/statistics.rst:43 +msgid "Median (middle value) of data." +msgstr "" + +#: ../Doc/library/statistics.rst:44 +msgid ":func:`median_low`" +msgstr "" + +#: ../Doc/library/statistics.rst:44 +msgid "Low median of data." +msgstr "" + +#: ../Doc/library/statistics.rst:45 +msgid ":func:`median_high`" +msgstr "" + +#: ../Doc/library/statistics.rst:45 +msgid "High median of data." +msgstr "" + +#: ../Doc/library/statistics.rst:46 +msgid ":func:`median_grouped`" +msgstr "" + +#: ../Doc/library/statistics.rst:46 +msgid "Median, or 50th percentile, of grouped data." +msgstr "" + +#: ../Doc/library/statistics.rst:47 ../Doc/library/turtle.rst:0 +msgid ":func:`mode`" +msgstr "" + +#: ../Doc/library/statistics.rst:47 +msgid "Mode (most common value) of discrete data." +msgstr "" + +#: ../Doc/library/statistics.rst:51 +msgid "Measures of spread" +msgstr "" + +#: ../Doc/library/statistics.rst:53 +msgid "" +"These functions calculate a measure of how much the population or sample " +"tends to deviate from the typical or average values." +msgstr "" + +#: ../Doc/library/statistics.rst:57 +msgid ":func:`pstdev`" +msgstr "" + +#: ../Doc/library/statistics.rst:57 +msgid "Population standard deviation of data." +msgstr "" + +#: ../Doc/library/statistics.rst:58 +msgid ":func:`pvariance`" +msgstr "" + +#: ../Doc/library/statistics.rst:58 +msgid "Population variance of data." +msgstr "" + +#: ../Doc/library/statistics.rst:59 +msgid ":func:`stdev`" +msgstr "" + +#: ../Doc/library/statistics.rst:59 +msgid "Sample standard deviation of data." +msgstr "" + +#: ../Doc/library/statistics.rst:60 +msgid ":func:`variance`" +msgstr "" + +#: ../Doc/library/statistics.rst:60 +msgid "Sample variance of data." +msgstr "" + +#: ../Doc/library/statistics.rst:65 +msgid "Function details" +msgstr "" + +#: ../Doc/library/statistics.rst:67 +msgid "" +"Note: The functions do not require the data given to them to be sorted. " +"However, for reading convenience, most of the examples show sorted sequences." +msgstr "" + +#: ../Doc/library/statistics.rst:72 +msgid "" +"Return the sample arithmetic mean of *data*, a sequence or iterator of real-" +"valued numbers." +msgstr "" + +#: ../Doc/library/statistics.rst:75 +msgid "" +"The arithmetic mean is the sum of the data divided by the number of data " +"points. It is commonly called \"the average\", although it is only one of " +"many different mathematical averages. It is a measure of the central " +"location of the data." +msgstr "" + +#: ../Doc/library/statistics.rst:80 +msgid "If *data* is empty, :exc:`StatisticsError` will be raised." +msgstr "" + +#: ../Doc/library/statistics.rst:82 +msgid "Some examples of use:" +msgstr "" + +#: ../Doc/library/statistics.rst:101 +msgid "" +"The mean is strongly affected by outliers and is not a robust estimator for " +"central location: the mean is not necessarily a typical example of the data " +"points. For more robust, although less efficient, measures of central " +"location, see :func:`median` and :func:`mode`. (In this case, \"efficient\" " +"refers to statistical efficiency rather than computational efficiency.)" +msgstr "" + +#: ../Doc/library/statistics.rst:108 +msgid "" +"The sample mean gives an unbiased estimate of the true population mean, " +"which means that, taken on average over all the possible samples, " +"``mean(sample)`` converges on the true mean of the entire population. If " +"*data* represents the entire population rather than a sample, then " +"``mean(data)`` is equivalent to calculating the true population mean μ." +msgstr "" + +#: ../Doc/library/statistics.rst:117 +msgid "" +"Return the harmonic mean of *data*, a sequence or iterator of real-valued " +"numbers." +msgstr "" + +#: ../Doc/library/statistics.rst:120 +msgid "" +"The harmonic mean, sometimes called the subcontrary mean, is the reciprocal " +"of the arithmetic :func:`mean` of the reciprocals of the data. For example, " +"the harmonic mean of three values *a*, *b* and *c* will be equivalent to ``3/" +"(1/a + 1/b + 1/c)``." +msgstr "" + +#: ../Doc/library/statistics.rst:125 +msgid "" +"The harmonic mean is a type of average, a measure of the central location of " +"the data. It is often appropriate when averaging quantities which are rates " +"or ratios, for example speeds. For example:" +msgstr "" + +#: ../Doc/library/statistics.rst:129 +msgid "" +"Suppose an investor purchases an equal value of shares in each of three " +"companies, with P/E (price/earning) ratios of 2.5, 3 and 10. What is the " +"average P/E ratio for the investor's portfolio?" +msgstr "" + +#: ../Doc/library/statistics.rst:138 +msgid "" +"Using the arithmetic mean would give an average of about 5.167, which is too " +"high." +msgstr "" + +#: ../Doc/library/statistics.rst:141 +msgid "" +":exc:`StatisticsError` is raised if *data* is empty, or any element is less " +"than zero." +msgstr "" + +#: ../Doc/library/statistics.rst:149 +msgid "" +"Return the median (middle value) of numeric data, using the common \"mean of " +"middle two\" method. If *data* is empty, :exc:`StatisticsError` is raised." +msgstr "" + +#: ../Doc/library/statistics.rst:152 +msgid "" +"The median is a robust measure of central location, and is less affected by " +"the presence of outliers in your data. When the number of data points is " +"odd, the middle data point is returned:" +msgstr "" + +#: ../Doc/library/statistics.rst:161 +msgid "" +"When the number of data points is even, the median is interpolated by taking " +"the average of the two middle values:" +msgstr "" + +#: ../Doc/library/statistics.rst:169 +msgid "" +"This is suited for when your data is discrete, and you don't mind that the " +"median may not be an actual data point." +msgstr "" + +#: ../Doc/library/statistics.rst:172 +msgid ":func:`median_low`, :func:`median_high`, :func:`median_grouped`" +msgstr "" + +#: ../Doc/library/statistics.rst:177 +msgid "" +"Return the low median of numeric data. If *data* is empty, :exc:" +"`StatisticsError` is raised." +msgstr "" + +#: ../Doc/library/statistics.rst:180 +msgid "" +"The low median is always a member of the data set. When the number of data " +"points is odd, the middle value is returned. When it is even, the smaller " +"of the two middle values is returned." +msgstr "" + +#: ../Doc/library/statistics.rst:191 +msgid "" +"Use the low median when your data are discrete and you prefer the median to " +"be an actual data point rather than interpolated." +msgstr "" + +#: ../Doc/library/statistics.rst:197 +msgid "" +"Return the high median of data. If *data* is empty, :exc:`StatisticsError` " +"is raised." +msgstr "" + +#: ../Doc/library/statistics.rst:200 +msgid "" +"The high median is always a member of the data set. When the number of data " +"points is odd, the middle value is returned. When it is even, the larger of " +"the two middle values is returned." +msgstr "" + +#: ../Doc/library/statistics.rst:211 +msgid "" +"Use the high median when your data are discrete and you prefer the median to " +"be an actual data point rather than interpolated." +msgstr "" + +#: ../Doc/library/statistics.rst:217 +msgid "" +"Return the median of grouped continuous data, calculated as the 50th " +"percentile, using interpolation. If *data* is empty, :exc:`StatisticsError` " +"is raised." +msgstr "" + +#: ../Doc/library/statistics.rst:226 +msgid "" +"In the following example, the data are rounded, so that each value " +"represents the midpoint of data classes, e.g. 1 is the midpoint of the class " +"0.5-1.5, 2 is the midpoint of 1.5-2.5, 3 is the midpoint of 2.5-3.5, etc. " +"With the data given, the middle value falls somewhere in the class 3.5-4.5, " +"and interpolation is used to estimate it:" +msgstr "" + +#: ../Doc/library/statistics.rst:237 +msgid "" +"Optional argument *interval* represents the class interval, and defaults to " +"1. Changing the class interval naturally will change the interpolation:" +msgstr "" + +#: ../Doc/library/statistics.rst:247 +msgid "" +"This function does not check whether the data points are at least *interval* " +"apart." +msgstr "" + +#: ../Doc/library/statistics.rst:252 +msgid "" +"Under some circumstances, :func:`median_grouped` may coerce data points to " +"floats. This behaviour is likely to change in the future." +msgstr "" + +#: ../Doc/library/statistics.rst:257 +msgid "" +"\"Statistics for the Behavioral Sciences\", Frederick J Gravetter and Larry " +"B Wallnau (8th Edition)." +msgstr "" + +#: ../Doc/library/statistics.rst:260 +msgid "" +"Calculating the `median `_." +msgstr "" + +#: ../Doc/library/statistics.rst:262 +msgid "" +"The `SSMEDIAN `_ function in the Gnome Gnumeric " +"spreadsheet, including `this discussion `_." +msgstr "" + +#: ../Doc/library/statistics.rst:270 +msgid "" +"Return the most common data point from discrete or nominal *data*. The mode " +"(when it exists) is the most typical value, and is a robust measure of " +"central location." +msgstr "" + +#: ../Doc/library/statistics.rst:274 +msgid "" +"If *data* is empty, or if there is not exactly one most common value, :exc:" +"`StatisticsError` is raised." +msgstr "" + +#: ../Doc/library/statistics.rst:277 +msgid "" +"``mode`` assumes discrete data, and returns a single value. This is the " +"standard treatment of the mode as commonly taught in schools:" +msgstr "" + +#: ../Doc/library/statistics.rst:285 +msgid "" +"The mode is unique in that it is the only statistic which also applies to " +"nominal (non-numeric) data:" +msgstr "" + +#: ../Doc/library/statistics.rst:296 +msgid "" +"Return the population standard deviation (the square root of the population " +"variance). See :func:`pvariance` for arguments and other details." +msgstr "" + +#: ../Doc/library/statistics.rst:307 +msgid "" +"Return the population variance of *data*, a non-empty iterable of real-" +"valued numbers. Variance, or second moment about the mean, is a measure of " +"the variability (spread or dispersion) of data. A large variance indicates " +"that the data is spread out; a small variance indicates it is clustered " +"closely around the mean." +msgstr "" + +#: ../Doc/library/statistics.rst:313 +msgid "" +"If the optional second argument *mu* is given, it should be the mean of " +"*data*. If it is missing or ``None`` (the default), the mean is " +"automatically calculated." +msgstr "" + +#: ../Doc/library/statistics.rst:317 +msgid "" +"Use this function to calculate the variance from the entire population. To " +"estimate the variance from a sample, the :func:`variance` function is " +"usually a better choice." +msgstr "" + +#: ../Doc/library/statistics.rst:321 +msgid "Raises :exc:`StatisticsError` if *data* is empty." +msgstr "" + +#: ../Doc/library/statistics.rst:323 ../Doc/library/statistics.rst:397 +#: ../Doc/library/tracemalloc.rst:395 ../Doc/library/unicodedata.rst:150 +msgid "Examples:" +msgstr "" + +#: ../Doc/library/statistics.rst:331 +msgid "" +"If you have already calculated the mean of your data, you can pass it as the " +"optional second argument *mu* to avoid recalculation:" +msgstr "" + +#: ../Doc/library/statistics.rst:340 +msgid "" +"This function does not attempt to verify that you have passed the actual " +"mean as *mu*. Using arbitrary values for *mu* may lead to invalid or " +"impossible results." +msgstr "" + +#: ../Doc/library/statistics.rst:344 +msgid "Decimals and Fractions are supported:" +msgstr "" + +#: ../Doc/library/statistics.rst:358 +msgid "" +"When called with the entire population, this gives the population variance " +"σ². When called on a sample instead, this is the biased sample variance s², " +"also known as variance with N degrees of freedom." +msgstr "" + +#: ../Doc/library/statistics.rst:362 +msgid "" +"If you somehow know the true population mean μ, you may use this function to " +"calculate the variance of a sample, giving the known population mean as the " +"second argument. Provided the data points are representative (e.g. " +"independent and identically distributed), the result will be an unbiased " +"estimate of the population variance." +msgstr "" + +#: ../Doc/library/statistics.rst:371 +msgid "" +"Return the sample standard deviation (the square root of the sample " +"variance). See :func:`variance` for arguments and other details." +msgstr "" + +#: ../Doc/library/statistics.rst:382 +msgid "" +"Return the sample variance of *data*, an iterable of at least two real-" +"valued numbers. Variance, or second moment about the mean, is a measure of " +"the variability (spread or dispersion) of data. A large variance indicates " +"that the data is spread out; a small variance indicates it is clustered " +"closely around the mean." +msgstr "" + +#: ../Doc/library/statistics.rst:388 +msgid "" +"If the optional second argument *xbar* is given, it should be the mean of " +"*data*. If it is missing or ``None`` (the default), the mean is " +"automatically calculated." +msgstr "" + +#: ../Doc/library/statistics.rst:392 +msgid "" +"Use this function when your data is a sample from a population. To calculate " +"the variance from the entire population, see :func:`pvariance`." +msgstr "" + +#: ../Doc/library/statistics.rst:395 +msgid "Raises :exc:`StatisticsError` if *data* has fewer than two values." +msgstr "" + +#: ../Doc/library/statistics.rst:405 +msgid "" +"If you have already calculated the mean of your data, you can pass it as the " +"optional second argument *xbar* to avoid recalculation:" +msgstr "" + +#: ../Doc/library/statistics.rst:414 +msgid "" +"This function does not attempt to verify that you have passed the actual " +"mean as *xbar*. Using arbitrary values for *xbar* can lead to invalid or " +"impossible results." +msgstr "" + +#: ../Doc/library/statistics.rst:418 +msgid "Decimal and Fraction values are supported:" +msgstr "" + +#: ../Doc/library/statistics.rst:432 +msgid "" +"This is the sample variance s² with Bessel's correction, also known as " +"variance with N-1 degrees of freedom. Provided that the data points are " +"representative (e.g. independent and identically distributed), the result " +"should be an unbiased estimate of the true population variance." +msgstr "" + +#: ../Doc/library/statistics.rst:437 +msgid "" +"If you somehow know the actual population mean μ you should pass it to the :" +"func:`pvariance` function as the *mu* parameter to get the variance of a " +"sample." +msgstr "" + +#: ../Doc/library/statistics.rst:444 +msgid "A single exception is defined:" +msgstr "" + +#: ../Doc/library/statistics.rst:448 +msgid "Subclass of :exc:`ValueError` for statistics-related exceptions." +msgstr "" + +#: ../Doc/library/stdtypes.rst:8 +msgid "Built-in Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:10 +msgid "" +"The following sections describe the standard types that are built into the " +"interpreter." +msgstr "" + +#: ../Doc/library/stdtypes.rst:15 +msgid "" +"The principal built-in types are numerics, sequences, mappings, classes, " +"instances and exceptions." +msgstr "" + +#: ../Doc/library/stdtypes.rst:18 +msgid "" +"Some collection classes are mutable. The methods that add, subtract, or " +"rearrange their members in place, and don't return a specific item, never " +"return the collection instance itself but ``None``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:22 +msgid "" +"Some operations are supported by several object types; in particular, " +"practically all objects can be compared, tested for truth value, and " +"converted to a string (with the :func:`repr` function or the slightly " +"different :func:`str` function). The latter function is implicitly used " +"when an object is written by the :func:`print` function." +msgstr "" + +#: ../Doc/library/stdtypes.rst:32 +msgid "Truth Value Testing" +msgstr "" + +#: ../Doc/library/stdtypes.rst:41 +msgid "" +"Any object can be tested for truth value, for use in an :keyword:`if` or :" +"keyword:`while` condition or as operand of the Boolean operations below. The " +"following values are considered false:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:51 +msgid "``False``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:53 +msgid "zero of any numeric type, for example, ``0``, ``0.0``, ``0j``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:55 +msgid "any empty sequence, for example, ``''``, ``()``, ``[]``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:57 +msgid "any empty mapping, for example, ``{}``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:59 +msgid "" +"instances of user-defined classes, if the class defines a :meth:`__bool__` " +"or :meth:`__len__` method, when that method returns the integer zero or :" +"class:`bool` value ``False``. [1]_" +msgstr "" + +#: ../Doc/library/stdtypes.rst:65 +msgid "" +"All other values are considered true --- so objects of many types are always " +"true." +msgstr "" + +#: ../Doc/library/stdtypes.rst:74 +msgid "" +"Operations and built-in functions that have a Boolean result always return " +"``0`` or ``False`` for false and ``1`` or ``True`` for true, unless " +"otherwise stated. (Important exception: the Boolean operations ``or`` and " +"``and`` always return one of their operands.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:83 +msgid "Boolean Operations --- :keyword:`and`, :keyword:`or`, :keyword:`not`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:87 +msgid "These are the Boolean operations, ordered by ascending priority:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:92 +msgid "``x or y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:92 +msgid "if *x* is false, then *y*, else *x*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:95 +msgid "``x and y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:95 +msgid "if *x* is false, then *x*, else *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:98 +msgid "``not x``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:98 +msgid "if *x* is false, then ``True``, else ``False``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:110 +msgid "" +"This is a short-circuit operator, so it only evaluates the second argument " +"if the first one is :const:`False`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:114 +msgid "" +"This is a short-circuit operator, so it only evaluates the second argument " +"if the first one is :const:`True`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:118 +msgid "" +"``not`` has a lower priority than non-Boolean operators, so ``not a == b`` " +"is interpreted as ``not (a == b)``, and ``a == not b`` is a syntax error." +msgstr "" + +#: ../Doc/library/stdtypes.rst:139 +msgid "" +"There are eight comparison operations in Python. They all have the same " +"priority (which is higher than that of the Boolean operations). Comparisons " +"can be chained arbitrarily; for example, ``x < y <= z`` is equivalent to ``x " +"< y and y <= z``, except that *y* is evaluated only once (but in both cases " +"*z* is not evaluated at all when ``x < y`` is found to be false)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:145 +msgid "This table summarizes the comparison operations:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:150 ../Doc/library/struct.rst:130 +msgid "``<``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:150 +msgid "strictly less than" +msgstr "" + +#: ../Doc/library/stdtypes.rst:152 +msgid "``<=``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:152 +msgid "less than or equal" +msgstr "" + +#: ../Doc/library/stdtypes.rst:154 ../Doc/library/struct.rst:132 +msgid "``>``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:154 +msgid "strictly greater than" +msgstr "" + +#: ../Doc/library/stdtypes.rst:156 +msgid "``>=``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:156 +msgid "greater than or equal" +msgstr "" + +#: ../Doc/library/stdtypes.rst:158 +msgid "``==``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:158 +msgid "equal" +msgstr "" + +#: ../Doc/library/stdtypes.rst:160 +msgid "``!=``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:160 +msgid "not equal" +msgstr "" + +#: ../Doc/library/stdtypes.rst:162 +msgid "``is``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:162 +msgid "object identity" +msgstr "" + +#: ../Doc/library/stdtypes.rst:164 +msgid "``is not``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:164 +msgid "negated object identity" +msgstr "" + +#: ../Doc/library/stdtypes.rst:171 +msgid "" +"Objects of different types, except different numeric types, never compare " +"equal. Furthermore, some types (for example, function objects) support only " +"a degenerate notion of comparison where any two objects of that type are " +"unequal. The ``<``, ``<=``, ``>`` and ``>=`` operators will raise a :exc:" +"`TypeError` exception when comparing a complex number with another built-in " +"numeric type, when the objects are of different types that cannot be " +"compared, or in other cases where there is no defined ordering." +msgstr "" + +#: ../Doc/library/stdtypes.rst:187 +msgid "" +"Non-identical instances of a class normally compare as non-equal unless the " +"class defines the :meth:`__eq__` method." +msgstr "" + +#: ../Doc/library/stdtypes.rst:190 +msgid "" +"Instances of a class cannot be ordered with respect to other instances of " +"the same class, or other types of object, unless the class defines enough of " +"the methods :meth:`__lt__`, :meth:`__le__`, :meth:`__gt__`, and :meth:" +"`__ge__` (in general, :meth:`__lt__` and :meth:`__eq__` are sufficient, if " +"you want the conventional meanings of the comparison operators)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:196 +msgid "" +"The behavior of the :keyword:`is` and :keyword:`is not` operators cannot be " +"customized; also they can be applied to any two objects and never raise an " +"exception." +msgstr "" + +#: ../Doc/library/stdtypes.rst:204 +msgid "" +"Two more operations with the same syntactic priority, :keyword:`in` and :" +"keyword:`not in`, are supported only by sequence types (below)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:211 +msgid "Numeric Types --- :class:`int`, :class:`float`, :class:`complex`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:221 +msgid "" +"There are three distinct numeric types: :dfn:`integers`, :dfn:`floating " +"point numbers`, and :dfn:`complex numbers`. In addition, Booleans are a " +"subtype of integers. Integers have unlimited precision. Floating point " +"numbers are usually implemented using :c:type:`double` in C; information " +"about the precision and internal representation of floating point numbers " +"for the machine on which your program is running is available in :data:`sys." +"float_info`. Complex numbers have a real and imaginary part, which are each " +"a floating point number. To extract these parts from a complex number *z*, " +"use ``z.real`` and ``z.imag``. (The standard library includes additional " +"numeric types, :mod:`fractions` that hold rationals, and :mod:`decimal` that " +"hold floating-point numbers with user-definable precision.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:243 +msgid "" +"Numbers are created by numeric literals or as the result of built-in " +"functions and operators. Unadorned integer literals (including hex, octal " +"and binary numbers) yield integers. Numeric literals containing a decimal " +"point or an exponent sign yield floating point numbers. Appending ``'j'`` " +"or ``'J'`` to a numeric literal yields an imaginary number (a complex number " +"with a zero real part) which you can add to an integer or float to get a " +"complex number with real and imaginary parts." +msgstr "" + +#: ../Doc/library/stdtypes.rst:264 +msgid "" +"Python fully supports mixed arithmetic: when a binary arithmetic operator " +"has operands of different numeric types, the operand with the \"narrower\" " +"type is widened to that of the other, where integer is narrower than " +"floating point, which is narrower than complex. Comparisons between numbers " +"of mixed type use the same rule. [2]_ The constructors :func:`int`, :func:" +"`float`, and :func:`complex` can be used to produce numbers of a specific " +"type." +msgstr "" + +#: ../Doc/library/stdtypes.rst:271 +msgid "" +"All numeric types (except complex) support the following operations, sorted " +"by ascending priority (all numeric operations have a higher priority than " +"comparison operations):" +msgstr "" + +#: ../Doc/library/stdtypes.rst:276 +msgid "Full documentation" +msgstr "" + +#: ../Doc/library/stdtypes.rst:278 +msgid "``x + y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:278 +msgid "sum of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:280 +msgid "``x - y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:280 +msgid "difference of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:282 +msgid "``x * y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:282 +msgid "product of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:284 +msgid "``x / y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:284 +msgid "quotient of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:286 +msgid "``x // y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:286 +msgid "floored quotient of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:289 +msgid "``x % y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:289 +msgid "remainder of ``x / y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:291 +msgid "``-x``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:291 +msgid "*x* negated" +msgstr "" + +#: ../Doc/library/stdtypes.rst:293 +msgid "``+x``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:293 +msgid "*x* unchanged" +msgstr "" + +#: ../Doc/library/stdtypes.rst:295 +msgid "``abs(x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:295 +msgid "absolute value or magnitude of *x*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:298 +msgid "``int(x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:298 +msgid "*x* converted to integer" +msgstr "" + +#: ../Doc/library/stdtypes.rst:298 +msgid "\\(3)\\(6)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:300 +msgid "``float(x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:300 +msgid "*x* converted to floating point" +msgstr "" + +#: ../Doc/library/stdtypes.rst:300 +msgid "\\(4)\\(6)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:302 +msgid "``complex(re, im)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:302 +msgid "" +"a complex number with real part *re*, imaginary part *im*. *im* defaults to " +"zero." +msgstr "" + +#: ../Doc/library/stdtypes.rst:306 +msgid "``c.conjugate()``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:306 +msgid "conjugate of the complex number *c*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:309 +msgid "``divmod(x, y)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:309 +msgid "the pair ``(x // y, x % y)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:311 +msgid "``pow(x, y)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:311 ../Doc/library/stdtypes.rst:313 +msgid "*x* to the power *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:313 +msgid "``x ** y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:323 +msgid "" +"Also referred to as integer division. The resultant value is a whole " +"integer, though the result's type is not necessarily int. The result is " +"always rounded towards minus infinity: ``1//2`` is ``0``, ``(-1)//2`` is " +"``-1``, ``1//(-2)`` is ``-1``, and ``(-1)//(-2)`` is ``0``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:329 +msgid "" +"Not for complex numbers. Instead convert to floats using :func:`abs` if " +"appropriate." +msgstr "" + +#: ../Doc/library/stdtypes.rst:341 +msgid "" +"Conversion from floating point to integer may round or truncate as in C; see " +"functions :func:`math.floor` and :func:`math.ceil` for well-defined " +"conversions." +msgstr "" + +#: ../Doc/library/stdtypes.rst:346 +msgid "" +"float also accepts the strings \"nan\" and \"inf\" with an optional prefix " +"\"+\" or \"-\" for Not a Number (NaN) and positive or negative infinity." +msgstr "" + +#: ../Doc/library/stdtypes.rst:350 +msgid "" +"Python defines ``pow(0, 0)`` and ``0 ** 0`` to be ``1``, as is common for " +"programming languages." +msgstr "" + +#: ../Doc/library/stdtypes.rst:354 +msgid "" +"The numeric literals accepted include the digits ``0`` to ``9`` or any " +"Unicode equivalent (code points with the ``Nd`` property)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:357 +msgid "" +"See http://www.unicode.org/Public/8.0.0/ucd/extracted/DerivedNumericType.txt " +"for a complete list of code points with the ``Nd`` property." +msgstr "" + +#: ../Doc/library/stdtypes.rst:361 +msgid "" +"All :class:`numbers.Real` types (:class:`int` and :class:`float`) also " +"include the following operations:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:367 +msgid ":func:`math.trunc(\\ x) `" +msgstr "" + +#: ../Doc/library/stdtypes.rst:367 +msgid "*x* truncated to :class:`~numbers.Integral`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:370 +msgid ":func:`round(x[, n]) `" +msgstr "" + +#: ../Doc/library/stdtypes.rst:370 +msgid "" +"*x* rounded to *n* digits, rounding half to even. If *n* is omitted, it " +"defaults to 0." +msgstr "" + +#: ../Doc/library/stdtypes.rst:374 +msgid ":func:`math.floor(\\ x) `" +msgstr "" + +#: ../Doc/library/stdtypes.rst:374 +msgid "the greatest :class:`~numbers.Integral` <= *x*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:377 +msgid ":func:`math.ceil(x) `" +msgstr "" + +#: ../Doc/library/stdtypes.rst:377 +msgid "the least :class:`~numbers.Integral` >= *x*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:381 +msgid "" +"For additional numeric operations see the :mod:`math` and :mod:`cmath` " +"modules." +msgstr "" + +#: ../Doc/library/stdtypes.rst:390 +msgid "Bitwise Operations on Integer Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:402 +msgid "" +"Bitwise operations only make sense for integers. Negative numbers are " +"treated as their 2's complement value (this assumes that there are enough " +"bits so that no overflow occurs during the operation)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:406 +msgid "" +"The priorities of the binary bitwise operations are all lower than the " +"numeric operations and higher than the comparisons; the unary operation " +"``~`` has the same priority as the other unary numeric operations (``+`` and " +"``-``)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:410 +msgid "This table lists the bitwise operations sorted in ascending priority:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:415 +msgid "``x | y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:415 +msgid "bitwise :dfn:`or` of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:418 +msgid "``x ^ y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:418 +msgid "bitwise :dfn:`exclusive or` of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:421 +msgid "``x & y``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:421 +msgid "bitwise :dfn:`and` of *x* and *y*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:424 +msgid "``x << n``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:424 +msgid "*x* shifted left by *n* bits" +msgstr "" + +#: ../Doc/library/stdtypes.rst:424 +msgid "(1)(2)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:426 +msgid "``x >> n``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:426 +msgid "*x* shifted right by *n* bits" +msgstr "" + +#: ../Doc/library/stdtypes.rst:426 +msgid "(1)(3)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:428 +msgid "``~x``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:428 +msgid "the bits of *x* inverted" +msgstr "" + +#: ../Doc/library/stdtypes.rst:434 +msgid "" +"Negative shift counts are illegal and cause a :exc:`ValueError` to be raised." +msgstr "" + +#: ../Doc/library/stdtypes.rst:437 +msgid "" +"A left shift by *n* bits is equivalent to multiplication by ``pow(2, n)`` " +"without overflow check." +msgstr "" + +#: ../Doc/library/stdtypes.rst:441 +msgid "" +"A right shift by *n* bits is equivalent to division by ``pow(2, n)`` without " +"overflow check." +msgstr "" + +#: ../Doc/library/stdtypes.rst:446 +msgid "Additional Methods on Integer Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:448 +msgid "" +"The int type implements the :class:`numbers.Integral` :term:`abstract base " +"class`. In addition, it provides a few more methods:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:453 +msgid "" +"Return the number of bits necessary to represent an integer in binary, " +"excluding the sign and leading zeros::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:462 +msgid "" +"More precisely, if ``x`` is nonzero, then ``x.bit_length()`` is the unique " +"positive integer ``k`` such that ``2**(k-1) <= abs(x) < 2**k``. " +"Equivalently, when ``abs(x)`` is small enough to have a correctly rounded " +"logarithm, then ``k = 1 + int(log(abs(x), 2))``. If ``x`` is zero, then ``x." +"bit_length()`` returns ``0``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:479 +msgid "Return an array of bytes representing an integer." +msgstr "" + +#: ../Doc/library/stdtypes.rst:491 +msgid "" +"The integer is represented using *length* bytes. An :exc:`OverflowError` is " +"raised if the integer is not representable with the given number of bytes." +msgstr "" + +#: ../Doc/library/stdtypes.rst:495 ../Doc/library/stdtypes.rst:527 +msgid "" +"The *byteorder* argument determines the byte order used to represent the " +"integer. If *byteorder* is ``\"big\"``, the most significant byte is at the " +"beginning of the byte array. If *byteorder* is ``\"little\"``, the most " +"significant byte is at the end of the byte array. To request the native " +"byte order of the host system, use :data:`sys.byteorder` as the byte order " +"value." +msgstr "" + +#: ../Doc/library/stdtypes.rst:502 +msgid "" +"The *signed* argument determines whether two's complement is used to " +"represent the integer. If *signed* is ``False`` and a negative integer is " +"given, an :exc:`OverflowError` is raised. The default value for *signed* is " +"``False``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:511 +msgid "Return the integer represented by the given array of bytes." +msgstr "" + +#: ../Doc/library/stdtypes.rst:524 +msgid "" +"The argument *bytes* must either be a :term:`bytes-like object` or an " +"iterable producing bytes." +msgstr "" + +#: ../Doc/library/stdtypes.rst:534 +msgid "" +"The *signed* argument indicates whether two's complement is used to " +"represent the integer." +msgstr "" + +#: ../Doc/library/stdtypes.rst:541 +msgid "Additional Methods on Float" +msgstr "" + +#: ../Doc/library/stdtypes.rst:543 +msgid "" +"The float type implements the :class:`numbers.Real` :term:`abstract base " +"class`. float also has the following additional methods." +msgstr "" + +#: ../Doc/library/stdtypes.rst:548 +msgid "" +"Return a pair of integers whose ratio is exactly equal to the original float " +"and with a positive denominator. Raises :exc:`OverflowError` on infinities " +"and a :exc:`ValueError` on NaNs." +msgstr "" + +#: ../Doc/library/stdtypes.rst:555 +msgid "" +"Return ``True`` if the float instance is finite with integral value, and " +"``False`` otherwise::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:563 +msgid "" +"Two methods support conversion to and from hexadecimal strings. Since " +"Python's floats are stored internally as binary numbers, converting a float " +"to or from a *decimal* string usually involves a small rounding error. In " +"contrast, hexadecimal strings allow exact representation and specification " +"of floating-point numbers. This can be useful when debugging, and in " +"numerical work." +msgstr "" + +#: ../Doc/library/stdtypes.rst:574 +msgid "" +"Return a representation of a floating-point number as a hexadecimal string. " +"For finite floating-point numbers, this representation will always include a " +"leading ``0x`` and a trailing ``p`` and exponent." +msgstr "" + +#: ../Doc/library/stdtypes.rst:582 +msgid "" +"Class method to return the float represented by a hexadecimal string *s*. " +"The string *s* may have leading and trailing whitespace." +msgstr "" + +#: ../Doc/library/stdtypes.rst:587 +msgid "" +"Note that :meth:`float.hex` is an instance method, while :meth:`float." +"fromhex` is a class method." +msgstr "" + +#: ../Doc/library/stdtypes.rst:590 +msgid "A hexadecimal string takes the form::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:594 +msgid "" +"where the optional ``sign`` may by either ``+`` or ``-``, ``integer`` and " +"``fraction`` are strings of hexadecimal digits, and ``exponent`` is a " +"decimal integer with an optional leading sign. Case is not significant, and " +"there must be at least one hexadecimal digit in either the integer or the " +"fraction. This syntax is similar to the syntax specified in section 6.4.4.2 " +"of the C99 standard, and also to the syntax used in Java 1.5 onwards. In " +"particular, the output of :meth:`float.hex` is usable as a hexadecimal " +"floating-point literal in C or Java code, and hexadecimal strings produced " +"by C's ``%a`` format character or Java's ``Double.toHexString`` are accepted " +"by :meth:`float.fromhex`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:607 +msgid "" +"Note that the exponent is written in decimal rather than hexadecimal, and " +"that it gives the power of 2 by which to multiply the coefficient. For " +"example, the hexadecimal string ``0x3.a7p10`` represents the floating-point " +"number ``(3 + 10./16 + 7./16**2) * 2.0**10``, or ``3740.0``::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:617 +msgid "" +"Applying the reverse conversion to ``3740.0`` gives a different hexadecimal " +"string representing the same number::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:627 +msgid "Hashing of numeric types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:629 +msgid "" +"For numbers ``x`` and ``y``, possibly of different types, it's a requirement " +"that ``hash(x) == hash(y)`` whenever ``x == y`` (see the :meth:`__hash__` " +"method documentation for more details). For ease of implementation and " +"efficiency across a variety of numeric types (including :class:`int`, :class:" +"`float`, :class:`decimal.Decimal` and :class:`fractions.Fraction`) Python's " +"hash for numeric types is based on a single mathematical function that's " +"defined for any rational number, and hence applies to all instances of :" +"class:`int` and :class:`fractions.Fraction`, and all finite instances of :" +"class:`float` and :class:`decimal.Decimal`. Essentially, this function is " +"given by reduction modulo ``P`` for a fixed prime ``P``. The value of ``P`` " +"is made available to Python as the :attr:`modulus` attribute of :data:`sys." +"hash_info`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:644 +msgid "" +"Currently, the prime used is ``P = 2**31 - 1`` on machines with 32-bit C " +"longs and ``P = 2**61 - 1`` on machines with 64-bit C longs." +msgstr "" + +#: ../Doc/library/stdtypes.rst:647 +msgid "Here are the rules in detail:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:649 +msgid "" +"If ``x = m / n`` is a nonnegative rational number and ``n`` is not divisible " +"by ``P``, define ``hash(x)`` as ``m * invmod(n, P) % P``, where ``invmod(n, " +"P)`` gives the inverse of ``n`` modulo ``P``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:653 +msgid "" +"If ``x = m / n`` is a nonnegative rational number and ``n`` is divisible by " +"``P`` (but ``m`` is not) then ``n`` has no inverse modulo ``P`` and the rule " +"above doesn't apply; in this case define ``hash(x)`` to be the constant " +"value ``sys.hash_info.inf``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:658 +msgid "" +"If ``x = m / n`` is a negative rational number define ``hash(x)`` as ``-" +"hash(-x)``. If the resulting hash is ``-1``, replace it with ``-2``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:662 +msgid "" +"The particular values ``sys.hash_info.inf``, ``-sys.hash_info.inf`` and " +"``sys.hash_info.nan`` are used as hash values for positive infinity, " +"negative infinity, or nans (respectively). (All hashable nans have the same " +"hash value.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:667 +msgid "" +"For a :class:`complex` number ``z``, the hash values of the real and " +"imaginary parts are combined by computing ``hash(z.real) + sys.hash_info." +"imag * hash(z.imag)``, reduced modulo ``2**sys.hash_info.width`` so that it " +"lies in ``range(-2**(sys.hash_info.width - 1), 2**(sys.hash_info.width - " +"1))``. Again, if the result is ``-1``, it's replaced with ``-2``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:675 +msgid "" +"To clarify the above rules, here's some example Python code, equivalent to " +"the built-in hash, for computing the hash of a rational number, :class:" +"`float`, or :class:`complex`::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:730 +msgid "Iterator Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:738 +msgid "" +"Python supports a concept of iteration over containers. This is implemented " +"using two distinct methods; these are used to allow user-defined classes to " +"support iteration. Sequences, described below in more detail, always " +"support the iteration methods." +msgstr "" + +#: ../Doc/library/stdtypes.rst:743 +msgid "" +"One method needs to be defined for container objects to provide iteration " +"support:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:750 +msgid "" +"Return an iterator object. The object is required to support the iterator " +"protocol described below. If a container supports different types of " +"iteration, additional methods can be provided to specifically request " +"iterators for those iteration types. (An example of an object supporting " +"multiple forms of iteration would be a tree structure which supports both " +"breadth-first and depth-first traversal.) This method corresponds to the :c:" +"member:`~PyTypeObject.tp_iter` slot of the type structure for Python objects " +"in the Python/C API." +msgstr "" + +#: ../Doc/library/stdtypes.rst:759 +msgid "" +"The iterator objects themselves are required to support the following two " +"methods, which together form the :dfn:`iterator protocol`:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:765 +msgid "" +"Return the iterator object itself. This is required to allow both " +"containers and iterators to be used with the :keyword:`for` and :keyword:" +"`in` statements. This method corresponds to the :c:member:`~PyTypeObject." +"tp_iter` slot of the type structure for Python objects in the Python/C API." +msgstr "" + +#: ../Doc/library/stdtypes.rst:773 +msgid "" +"Return the next item from the container. If there are no further items, " +"raise the :exc:`StopIteration` exception. This method corresponds to the :c:" +"member:`~PyTypeObject.tp_iternext` slot of the type structure for Python " +"objects in the Python/C API." +msgstr "" + +#: ../Doc/library/stdtypes.rst:778 +msgid "" +"Python defines several iterator objects to support iteration over general " +"and specific sequence types, dictionaries, and other more specialized " +"forms. The specific types are not important beyond their implementation of " +"the iterator protocol." +msgstr "" + +#: ../Doc/library/stdtypes.rst:783 +msgid "" +"Once an iterator's :meth:`~iterator.__next__` method raises :exc:" +"`StopIteration`, it must continue to do so on subsequent calls. " +"Implementations that do not obey this property are deemed broken." +msgstr "" + +#: ../Doc/library/stdtypes.rst:791 +msgid "Generator Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:793 +msgid "" +"Python's :term:`generator`\\s provide a convenient way to implement the " +"iterator protocol. If a container object's :meth:`__iter__` method is " +"implemented as a generator, it will automatically return an iterator object " +"(technically, a generator object) supplying the :meth:`__iter__` and :meth:" +"`~generator.__next__` methods. More information about generators can be " +"found in :ref:`the documentation for the yield expression `." +msgstr "" + +#: ../Doc/library/stdtypes.rst:805 +msgid "Sequence Types --- :class:`list`, :class:`tuple`, :class:`range`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:807 +msgid "" +"There are three basic sequence types: lists, tuples, and range objects. " +"Additional sequence types tailored for processing of :ref:`binary data " +"` and :ref:`text strings ` are described in dedicated " +"sections." +msgstr "" + +#: ../Doc/library/stdtypes.rst:816 +msgid "Common Sequence Operations" +msgstr "" + +#: ../Doc/library/stdtypes.rst:820 +msgid "" +"The operations in the following table are supported by most sequence types, " +"both mutable and immutable. The :class:`collections.abc.Sequence` ABC is " +"provided to make it easier to correctly implement these operations on custom " +"sequence types." +msgstr "" + +#: ../Doc/library/stdtypes.rst:825 +msgid "" +"This table lists the sequence operations sorted in ascending priority. In " +"the table, *s* and *t* are sequences of the same type, *n*, *i*, *j* and *k* " +"are integers and *x* is an arbitrary object that meets any type and value " +"restrictions imposed by *s*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:830 +msgid "" +"The ``in`` and ``not in`` operations have the same priorities as the " +"comparison operations. The ``+`` (concatenation) and ``*`` (repetition) " +"operations have the same priority as the corresponding numeric operations." +msgstr "" + +#: ../Doc/library/stdtypes.rst:851 +msgid "``x in s``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:851 +msgid "``True`` if an item of *s* is equal to *x*, else ``False``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:854 +msgid "``x not in s``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:854 +msgid "``False`` if an item of *s* is equal to *x*, else ``True``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:857 +msgid "``s + t``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:857 +msgid "the concatenation of *s* and *t*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:857 +msgid "(6)(7)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:860 +msgid "``s * n`` or ``n * s``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:860 +msgid "equivalent to adding *s* to itself *n* times" +msgstr "" + +#: ../Doc/library/stdtypes.rst:860 +msgid "(2)(7)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:863 +msgid "``s[i]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:863 +msgid "*i*\\ th item of *s*, origin 0" +msgstr "" + +#: ../Doc/library/stdtypes.rst:865 +msgid "``s[i:j]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:865 +msgid "slice of *s* from *i* to *j*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:865 +msgid "(3)(4)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:867 +msgid "``s[i:j:k]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:867 +msgid "slice of *s* from *i* to *j* with step *k*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:867 +msgid "(3)(5)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:870 +msgid "``len(s)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:870 +msgid "length of *s*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:872 +msgid "``min(s)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:872 +msgid "smallest item of *s*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:874 +msgid "``max(s)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:874 +msgid "largest item of *s*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:876 +msgid "``s.index(x[, i[, j]])``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:876 +msgid "" +"index of the first occurrence of *x* in *s* (at or after index *i* and " +"before index *j*)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:880 +msgid "``s.count(x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:880 +msgid "total number of occurrences of *x* in *s*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:884 +msgid "" +"Sequences of the same type also support comparisons. In particular, tuples " +"and lists are compared lexicographically by comparing corresponding " +"elements. This means that to compare equal, every element must compare equal " +"and the two sequences must be of the same type and have the same length. " +"(For full details see :ref:`comparisons` in the language reference.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:893 +msgid "" +"While the ``in`` and ``not in`` operations are used only for simple " +"containment testing in the general case, some specialised sequences (such " +"as :class:`str`, :class:`bytes` and :class:`bytearray`) also use them for " +"subsequence testing::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:902 +msgid "" +"Values of *n* less than ``0`` are treated as ``0`` (which yields an empty " +"sequence of the same type as *s*). Note that items in the sequence *s* are " +"not copied; they are referenced multiple times. This often haunts new " +"Python programmers; consider::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:914 +msgid "" +"What has happened is that ``[[]]`` is a one-element list containing an empty " +"list, so all three elements of ``[[]] * 3`` are references to this single " +"empty list. Modifying any of the elements of ``lists`` modifies this single " +"list. You can create a list of different lists this way::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:926 +msgid "" +"Further explanation is available in the FAQ entry :ref:`faq-multidimensional-" +"list`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:930 +msgid "" +"If *i* or *j* is negative, the index is relative to the end of the string: " +"``len(s) + i`` or ``len(s) + j`` is substituted. But note that ``-0`` is " +"still ``0``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:935 +msgid "" +"The slice of *s* from *i* to *j* is defined as the sequence of items with " +"index *k* such that ``i <= k < j``. If *i* or *j* is greater than " +"``len(s)``, use ``len(s)``. If *i* is omitted or ``None``, use ``0``. If " +"*j* is omitted or ``None``, use ``len(s)``. If *i* is greater than or equal " +"to *j*, the slice is empty." +msgstr "" + +#: ../Doc/library/stdtypes.rst:942 +msgid "" +"The slice of *s* from *i* to *j* with step *k* is defined as the sequence of " +"items with index ``x = i + n*k`` such that ``0 <= n < (j-i)/k``. In other " +"words, the indices are ``i``, ``i+k``, ``i+2*k``, ``i+3*k`` and so on, " +"stopping when *j* is reached (but never including *j*). If *i* or *j* is " +"greater than ``len(s)``, use ``len(s)``. If *i* or *j* are omitted or " +"``None``, they become \"end\" values (which end depends on the sign of " +"*k*). Note, *k* cannot be zero. If *k* is ``None``, it is treated like " +"``1``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:951 +msgid "" +"Concatenating immutable sequences always results in a new object. This " +"means that building up a sequence by repeated concatenation will have a " +"quadratic runtime cost in the total sequence length. To get a linear " +"runtime cost, you must switch to one of the alternatives below:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:956 +msgid "" +"if concatenating :class:`str` objects, you can build a list and use :meth:" +"`str.join` at the end or else write to an :class:`io.StringIO` instance and " +"retrieve its value when complete" +msgstr "" + +#: ../Doc/library/stdtypes.rst:960 +msgid "" +"if concatenating :class:`bytes` objects, you can similarly use :meth:`bytes." +"join` or :class:`io.BytesIO`, or you can do in-place concatenation with a :" +"class:`bytearray` object. :class:`bytearray` objects are mutable and have " +"an efficient overallocation mechanism" +msgstr "" + +#: ../Doc/library/stdtypes.rst:965 +msgid "if concatenating :class:`tuple` objects, extend a :class:`list` instead" +msgstr "" + +#: ../Doc/library/stdtypes.rst:967 +msgid "for other types, investigate the relevant class documentation" +msgstr "" + +#: ../Doc/library/stdtypes.rst:971 +msgid "" +"Some sequence types (such as :class:`range`) only support item sequences " +"that follow specific patterns, and hence don't support sequence " +"concatenation or repetition." +msgstr "" + +#: ../Doc/library/stdtypes.rst:976 +msgid "" +"``index`` raises :exc:`ValueError` when *x* is not found in *s*. When " +"supported, the additional arguments to the index method allow efficient " +"searching of subsections of the sequence. Passing the extra arguments is " +"roughly equivalent to using ``s[i:j].index(x)``, only without copying any " +"data and with the returned index being relative to the start of the sequence " +"rather than the start of the slice." +msgstr "" + +#: ../Doc/library/stdtypes.rst:987 +msgid "Immutable Sequence Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:994 +msgid "" +"The only operation that immutable sequence types generally implement that is " +"not also implemented by mutable sequence types is support for the :func:" +"`hash` built-in." +msgstr "" + +#: ../Doc/library/stdtypes.rst:998 +msgid "" +"This support allows immutable sequences, such as :class:`tuple` instances, " +"to be used as :class:`dict` keys and stored in :class:`set` and :class:" +"`frozenset` instances." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1002 +msgid "" +"Attempting to hash an immutable sequence that contains unhashable values " +"will result in :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1009 +msgid "Mutable Sequence Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1016 +msgid "" +"The operations in the following table are defined on mutable sequence types. " +"The :class:`collections.abc.MutableSequence` ABC is provided to make it " +"easier to correctly implement these operations on custom sequence types." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1020 +msgid "" +"In the table *s* is an instance of a mutable sequence type, *t* is any " +"iterable object and *x* is an arbitrary object that meets any type and value " +"restrictions imposed by *s* (for example, :class:`bytearray` only accepts " +"integers that meet the value restriction ``0 <= x <= 255``)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1044 +msgid "``s[i] = x``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1044 +msgid "item *i* of *s* is replaced by *x*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1047 +msgid "``s[i:j] = t``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1047 +msgid "" +"slice of *s* from *i* to *j* is replaced by the contents of the iterable *t*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1051 +msgid "``del s[i:j]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1051 +msgid "same as ``s[i:j] = []``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1053 +msgid "``s[i:j:k] = t``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1053 +msgid "the elements of ``s[i:j:k]`` are replaced by those of *t*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1056 +msgid "``del s[i:j:k]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1056 +msgid "removes the elements of ``s[i:j:k]`` from the list" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1059 +msgid "``s.append(x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1059 +msgid "" +"appends *x* to the end of the sequence (same as ``s[len(s):len(s)] = [x]``)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1063 +msgid "``s.clear()``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1063 +msgid "removes all items from ``s`` (same as ``del s[:]``)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1066 +msgid "``s.copy()``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1066 +msgid "creates a shallow copy of ``s`` (same as ``s[:]``)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1069 +msgid "``s.extend(t)`` or ``s += t``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1069 +msgid "" +"extends *s* with the contents of *t* (for the most part the same as " +"``s[len(s):len(s)] = t``)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1074 +msgid "``s *= n``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1074 +msgid "updates *s* with its contents repeated *n* times" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1077 +msgid "``s.insert(i, x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1077 +msgid "" +"inserts *x* into *s* at the index given by *i* (same as ``s[i:i] = [x]``)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1081 +msgid "``s.pop([i])``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1081 +msgid "retrieves the item at *i* and also removes it from *s*" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1084 +msgid "``s.remove(x)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1084 +msgid "remove the first item from *s* where ``s[i] == x``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1087 +msgid "``s.reverse()``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1087 +msgid "reverses the items of *s* in place" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1095 +msgid "*t* must have the same length as the slice it is replacing." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1098 +msgid "" +"The optional argument *i* defaults to ``-1``, so that by default the last " +"item is removed and returned." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1102 +msgid "``remove`` raises :exc:`ValueError` when *x* is not found in *s*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1105 +msgid "" +"The :meth:`reverse` method modifies the sequence in place for economy of " +"space when reversing a large sequence. To remind users that it operates by " +"side effect, it does not return the reversed sequence." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1110 +msgid "" +":meth:`clear` and :meth:`!copy` are included for consistency with the " +"interfaces of mutable containers that don't support slicing operations (such " +"as :class:`dict` and :class:`set`)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1114 +msgid ":meth:`clear` and :meth:`!copy` methods." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1118 +msgid "" +"The value *n* is an integer, or an object implementing :meth:`~object." +"__index__`. Zero and negative values of *n* clear the sequence. Items in " +"the sequence are not copied; they are referenced multiple times, as " +"explained for ``s * n`` under :ref:`typesseq-common`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1127 +msgid "Lists" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1131 +msgid "" +"Lists are mutable sequences, typically used to store collections of " +"homogeneous items (where the precise degree of similarity will vary by " +"application)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1137 +msgid "Lists may be constructed in several ways:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1139 +msgid "Using a pair of square brackets to denote the empty list: ``[]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1140 +msgid "" +"Using square brackets, separating items with commas: ``[a]``, ``[a, b, c]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1141 +msgid "Using a list comprehension: ``[x for x in iterable]``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1142 +msgid "Using the type constructor: ``list()`` or ``list(iterable)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1144 +msgid "" +"The constructor builds a list whose items are the same and in the same order " +"as *iterable*'s items. *iterable* may be either a sequence, a container " +"that supports iteration, or an iterator object. If *iterable* is already a " +"list, a copy is made and returned, similar to ``iterable[:]``. For example, " +"``list('abc')`` returns ``['a', 'b', 'c']`` and ``list( (1, 2, 3) )`` " +"returns ``[1, 2, 3]``. If no argument is given, the constructor creates a " +"new empty list, ``[]``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1153 +msgid "" +"Many other operations also produce lists, including the :func:`sorted` built-" +"in." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1156 +msgid "" +"Lists implement all of the :ref:`common ` and :ref:`mutable " +"` sequence operations. Lists also provide the following " +"additional method:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1162 +msgid "" +"This method sorts the list in place, using only ``<`` comparisons between " +"items. Exceptions are not suppressed - if any comparison operations fail, " +"the entire sort operation will fail (and the list will likely be left in a " +"partially modified state)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1167 +msgid "" +":meth:`sort` accepts two arguments that can only be passed by keyword (:ref:" +"`keyword-only arguments `):" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1170 +msgid "" +"*key* specifies a function of one argument that is used to extract a " +"comparison key from each list element (for example, ``key=str.lower``). The " +"key corresponding to each item in the list is calculated once and then used " +"for the entire sorting process. The default value of ``None`` means that " +"list items are sorted directly without calculating a separate key value." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1177 +msgid "" +"The :func:`functools.cmp_to_key` utility is available to convert a 2.x style " +"*cmp* function to a *key* function." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1183 +msgid "" +"This method modifies the sequence in place for economy of space when sorting " +"a large sequence. To remind users that it operates by side effect, it does " +"not return the sorted sequence (use :func:`sorted` to explicitly request a " +"new sorted list instance)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1188 +msgid "" +"The :meth:`sort` method is guaranteed to be stable. A sort is stable if it " +"guarantees not to change the relative order of elements that compare equal " +"--- this is helpful for sorting in multiple passes (for example, sort by " +"department, then by salary grade)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1195 +msgid "" +"While a list is being sorted, the effect of attempting to mutate, or even " +"inspect, the list is undefined. The C implementation of Python makes the " +"list appear empty for the duration, and raises :exc:`ValueError` if it can " +"detect that the list has been mutated during a sort." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1204 +msgid "Tuples" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1208 +msgid "" +"Tuples are immutable sequences, typically used to store collections of " +"heterogeneous data (such as the 2-tuples produced by the :func:`enumerate` " +"built-in). Tuples are also used for cases where an immutable sequence of " +"homogeneous data is needed (such as allowing storage in a :class:`set` or :" +"class:`dict` instance)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1216 +msgid "Tuples may be constructed in a number of ways:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1218 +msgid "Using a pair of parentheses to denote the empty tuple: ``()``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1219 +msgid "Using a trailing comma for a singleton tuple: ``a,`` or ``(a,)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1220 +msgid "Separating items with commas: ``a, b, c`` or ``(a, b, c)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1221 +msgid "Using the :func:`tuple` built-in: ``tuple()`` or ``tuple(iterable)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1223 +msgid "" +"The constructor builds a tuple whose items are the same and in the same " +"order as *iterable*'s items. *iterable* may be either a sequence, a " +"container that supports iteration, or an iterator object. If *iterable* is " +"already a tuple, it is returned unchanged. For example, ``tuple('abc')`` " +"returns ``('a', 'b', 'c')`` and ``tuple( [1, 2, 3] )`` returns ``(1, 2, " +"3)``. If no argument is given, the constructor creates a new empty tuple, " +"``()``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1231 +msgid "" +"Note that it is actually the comma which makes a tuple, not the parentheses. " +"The parentheses are optional, except in the empty tuple case, or when they " +"are needed to avoid syntactic ambiguity. For example, ``f(a, b, c)`` is a " +"function call with three arguments, while ``f((a, b, c))`` is a function " +"call with a 3-tuple as the sole argument." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1237 +msgid "" +"Tuples implement all of the :ref:`common ` sequence " +"operations." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1240 +msgid "" +"For heterogeneous collections of data where access by name is clearer than " +"access by index, :func:`collections.namedtuple` may be a more appropriate " +"choice than a simple tuple object." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1248 +msgid "Ranges" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1252 +msgid "" +"The :class:`range` type represents an immutable sequence of numbers and is " +"commonly used for looping a specific number of times in :keyword:`for` loops." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1259 +msgid "" +"The arguments to the range constructor must be integers (either built-in :" +"class:`int` or any object that implements the ``__index__`` special " +"method). If the *step* argument is omitted, it defaults to ``1``. If the " +"*start* argument is omitted, it defaults to ``0``. If *step* is zero, :exc:" +"`ValueError` is raised." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1265 +msgid "" +"For a positive *step*, the contents of a range ``r`` are determined by the " +"formula ``r[i] = start + step*i`` where ``i >= 0`` and ``r[i] < stop``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1269 +msgid "" +"For a negative *step*, the contents of the range are still determined by the " +"formula ``r[i] = start + step*i``, but the constraints are ``i >= 0`` and " +"``r[i] > stop``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1273 +msgid "" +"A range object will be empty if ``r[0]`` does not meet the value constraint. " +"Ranges do support negative indices, but these are interpreted as indexing " +"from the end of the sequence determined by the positive indices." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1278 +msgid "" +"Ranges containing absolute values larger than :data:`sys.maxsize` are " +"permitted but some features (such as :func:`len`) may raise :exc:" +"`OverflowError`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1282 +msgid "Range examples::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1299 +msgid "" +"Ranges implement all of the :ref:`common ` sequence " +"operations except concatenation and repetition (due to the fact that range " +"objects can only represent sequences that follow a strict pattern and " +"repetition and concatenation will usually violate that pattern)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1306 +msgid "" +"The value of the *start* parameter (or ``0`` if the parameter was not " +"supplied)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1311 +msgid "The value of the *stop* parameter" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1315 +msgid "" +"The value of the *step* parameter (or ``1`` if the parameter was not " +"supplied)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1318 +msgid "" +"The advantage of the :class:`range` type over a regular :class:`list` or :" +"class:`tuple` is that a :class:`range` object will always take the same " +"(small) amount of memory, no matter the size of the range it represents (as " +"it only stores the ``start``, ``stop`` and ``step`` values, calculating " +"individual items and subranges as needed)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1324 +msgid "" +"Range objects implement the :class:`collections.abc.Sequence` ABC, and " +"provide features such as containment tests, element index lookup, slicing " +"and support for negative indices (see :ref:`typesseq`):" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1344 +msgid "" +"Testing range objects for equality with ``==`` and ``!=`` compares them as " +"sequences. That is, two range objects are considered equal if they " +"represent the same sequence of values. (Note that two range objects that " +"compare equal might have different :attr:`~range.start`, :attr:`~range.stop` " +"and :attr:`~range.step` attributes, for example ``range(0) == range(2, 1, " +"3)`` or ``range(0, 3, 2) == range(0, 4, 2)``.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1351 +msgid "" +"Implement the Sequence ABC. Support slicing and negative indices. Test :" +"class:`int` objects for membership in constant time instead of iterating " +"through all items." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1357 +msgid "" +"Define '==' and '!=' to compare range objects based on the sequence of " +"values they define (instead of comparing based on object identity)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1362 +msgid "" +"The :attr:`~range.start`, :attr:`~range.stop` and :attr:`~range.step` " +"attributes." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1368 +msgid "" +"The `linspace recipe `_ shows " +"how to implement a lazy version of range that suitable for floating point " +"applications." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1380 +msgid "Text Sequence Type --- :class:`str`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1382 +msgid "" +"Textual data in Python is handled with :class:`str` objects, or :dfn:" +"`strings`. Strings are immutable :ref:`sequences ` of Unicode code " +"points. String literals are written in a variety of ways:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1387 +msgid "Single quotes: ``'allows embedded \"double\" quotes'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1388 +msgid "Double quotes: ``\"allows embedded 'single' quotes\"``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1389 +msgid "" +"Triple quoted: ``'''Three single quotes'''``, ``\"\"\"Three double quotes" +"\"\"\"``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1391 +msgid "" +"Triple quoted strings may span multiple lines - all associated whitespace " +"will be included in the string literal." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1394 +msgid "" +"String literals that are part of a single expression and have only " +"whitespace between them will be implicitly converted to a single string " +"literal. That is, ``(\"spam \" \"eggs\") == \"spam eggs\"``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1398 +msgid "" +"See :ref:`strings` for more about the various forms of string literal, " +"including supported escape sequences, and the ``r`` (\"raw\") prefix that " +"disables most escape sequence processing." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1402 +msgid "" +"Strings may also be created from other objects using the :class:`str` " +"constructor." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1405 +msgid "" +"Since there is no separate \"character\" type, indexing a string produces " +"strings of length 1. That is, for a non-empty string *s*, ``s[0] == s[0:1]``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1411 +msgid "" +"There is also no mutable string type, but :meth:`str.join` or :class:`io." +"StringIO` can be used to efficiently construct strings from multiple " +"fragments." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1415 +msgid "" +"For backwards compatibility with the Python 2 series, the ``u`` prefix is " +"once again permitted on string literals. It has no effect on the meaning of " +"string literals and cannot be combined with the ``r`` prefix." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1427 +msgid "" +"Return a :ref:`string ` version of *object*. If *object* is not " +"provided, returns the empty string. Otherwise, the behavior of ``str()`` " +"depends on whether *encoding* or *errors* is given, as follows." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1431 +msgid "" +"If neither *encoding* nor *errors* is given, ``str(object)`` returns :meth:" +"`object.__str__() `, which is the \"informal\" or nicely " +"printable string representation of *object*. For string objects, this is " +"the string itself. If *object* does not have a :meth:`~object.__str__` " +"method, then :func:`str` falls back to returning :meth:`repr(object) `." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1442 +msgid "" +"If at least one of *encoding* or *errors* is given, *object* should be a :" +"term:`bytes-like object` (e.g. :class:`bytes` or :class:`bytearray`). In " +"this case, if *object* is a :class:`bytes` (or :class:`bytearray`) object, " +"then ``str(bytes, encoding, errors)`` is equivalent to :meth:`bytes." +"decode(encoding, errors) `. Otherwise, the bytes object " +"underlying the buffer object is obtained before calling :meth:`bytes." +"decode`. See :ref:`binaryseq` and :ref:`bufferobjects` for information on " +"buffer objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1451 +msgid "" +"Passing a :class:`bytes` object to :func:`str` without the *encoding* or " +"*errors* arguments falls under the first case of returning the informal " +"string representation (see also the :option:`-b` command-line option to " +"Python). For example::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1459 +msgid "" +"For more information on the ``str`` class and its methods, see :ref:" +"`textseq` and the :ref:`string-methods` section below. To output formatted " +"strings, see the :ref:`f-strings` and :ref:`formatstrings` sections. In " +"addition, see the :ref:`stringservices` section." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1471 +msgid "String Methods" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1476 +msgid "" +"Strings implement all of the :ref:`common ` sequence " +"operations, along with the additional methods described below." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1479 +msgid "" +"Strings also support two styles of string formatting, one providing a large " +"degree of flexibility and customization (see :meth:`str.format`, :ref:" +"`formatstrings` and :ref:`string-formatting`) and the other based on C " +"``printf`` style formatting that handles a narrower range of types and is " +"slightly harder to use correctly, but is often faster for the cases it can " +"handle (:ref:`old-string-formatting`)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1486 +msgid "" +"The :ref:`textservices` section of the standard library covers a number of " +"other modules that provide various text related utilities (including regular " +"expression support in the :mod:`re` module)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1492 +msgid "" +"Return a copy of the string with its first character capitalized and the " +"rest lowercased." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1498 +msgid "" +"Return a casefolded copy of the string. Casefolded strings may be used for " +"caseless matching." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1501 +msgid "" +"Casefolding is similar to lowercasing but more aggressive because it is " +"intended to remove all case distinctions in a string. For example, the " +"German lowercase letter ``'ß'`` is equivalent to ``\"ss\"``. Since it is " +"already lowercase, :meth:`lower` would do nothing to ``'ß'``; :meth:" +"`casefold` converts it to ``\"ss\"``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1507 +msgid "" +"The casefolding algorithm is described in section 3.13 of the Unicode " +"Standard." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1515 +msgid "" +"Return centered in a string of length *width*. Padding is done using the " +"specified *fillchar* (default is an ASCII space). The original string is " +"returned if *width* is less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1523 +msgid "" +"Return the number of non-overlapping occurrences of substring *sub* in the " +"range [*start*, *end*]. Optional arguments *start* and *end* are " +"interpreted as in slice notation." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1530 +msgid "" +"Return an encoded version of the string as a bytes object. Default encoding " +"is ``'utf-8'``. *errors* may be given to set a different error handling " +"scheme. The default for *errors* is ``'strict'``, meaning that encoding " +"errors raise a :exc:`UnicodeError`. Other possible values are ``'ignore'``, " +"``'replace'``, ``'xmlcharrefreplace'``, ``'backslashreplace'`` and any other " +"name registered via :func:`codecs.register_error`, see section :ref:`error-" +"handlers`. For a list of possible encodings, see section :ref:`standard-" +"encodings`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1539 +msgid "Support for keyword arguments added." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1545 +msgid "" +"Return ``True`` if the string ends with the specified *suffix*, otherwise " +"return ``False``. *suffix* can also be a tuple of suffixes to look for. " +"With optional *start*, test beginning at that position. With optional " +"*end*, stop comparing at that position." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1553 +msgid "" +"Return a copy of the string where all tab characters are replaced by one or " +"more spaces, depending on the current column and the given tab size. Tab " +"positions occur every *tabsize* characters (default is 8, giving tab " +"positions at columns 0, 8, 16 and so on). To expand the string, the current " +"column is set to zero and the string is examined character by character. If " +"the character is a tab (``\\t``), one or more space characters are inserted " +"in the result until the current column is equal to the next tab position. " +"(The tab character itself is not copied.) If the character is a newline (``" +"\\n``) or return (``\\r``), it is copied and the current column is reset to " +"zero. Any other character is copied unchanged and the current column is " +"incremented by one regardless of how the character is represented when " +"printed." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1574 +msgid "" +"Return the lowest index in the string where substring *sub* is found within " +"the slice ``s[start:end]``. Optional arguments *start* and *end* are " +"interpreted as in slice notation. Return ``-1`` if *sub* is not found." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1580 +msgid "" +"The :meth:`~str.find` method should be used only if you need to know the " +"position of *sub*. To check if *sub* is a substring or not, use the :" +"keyword:`in` operator::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1590 +msgid "" +"Perform a string formatting operation. The string on which this method is " +"called can contain literal text or replacement fields delimited by braces " +"``{}``. Each replacement field contains either the numeric index of a " +"positional argument, or the name of a keyword argument. Returns a copy of " +"the string where each replacement field is replaced with the string value of " +"the corresponding argument." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1600 +msgid "" +"See :ref:`formatstrings` for a description of the various formatting options " +"that can be specified in format strings." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1606 +msgid "" +"Similar to ``str.format(**mapping)``, except that ``mapping`` is used " +"directly and not copied to a :class:`dict`. This is useful if for example " +"``mapping`` is a dict subclass:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1622 +msgid "" +"Like :meth:`~str.find`, but raise :exc:`ValueError` when the substring is " +"not found." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1628 +msgid "" +"Return true if all characters in the string are alphanumeric and there is at " +"least one character, false otherwise. A character ``c`` is alphanumeric if " +"one of the following returns ``True``: ``c.isalpha()``, ``c.isdecimal()``, " +"``c.isdigit()``, or ``c.isnumeric()``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1636 +msgid "" +"Return true if all characters in the string are alphabetic and there is at " +"least one character, false otherwise. Alphabetic characters are those " +"characters defined in the Unicode character database as \"Letter\", i.e., " +"those with general category property being one of \"Lm\", \"Lt\", \"Lu\", " +"\"Ll\", or \"Lo\". Note that this is different from the \"Alphabetic\" " +"property defined in the Unicode Standard." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1645 +msgid "" +"Return true if all characters in the string are decimal characters and there " +"is at least one character, false otherwise. Decimal characters are those " +"from general category \"Nd\". This category includes digit characters, and " +"all characters that can be used to form decimal-radix numbers, e.g. U+0660, " +"ARABIC-INDIC DIGIT ZERO." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1655 +msgid "" +"Return true if all characters in the string are digits and there is at least " +"one character, false otherwise. Digits include decimal characters and " +"digits that need special handling, such as the compatibility superscript " +"digits. Formally, a digit is a character that has the property value " +"Numeric_Type=Digit or Numeric_Type=Decimal." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1663 +msgid "" +"Return true if the string is a valid identifier according to the language " +"definition, section :ref:`identifiers`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1666 +msgid "" +"Use :func:`keyword.iskeyword` to test for reserved identifiers such as :" +"keyword:`def` and :keyword:`class`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1671 +msgid "" +"Return true if all cased characters [4]_ in the string are lowercase and " +"there is at least one cased character, false otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1677 +msgid "" +"Return true if all characters in the string are numeric characters, and " +"there is at least one character, false otherwise. Numeric characters include " +"digit characters, and all characters that have the Unicode numeric value " +"property, e.g. U+2155, VULGAR FRACTION ONE FIFTH. Formally, numeric " +"characters are those with the property value Numeric_Type=Digit, " +"Numeric_Type=Decimal or Numeric_Type=Numeric." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1687 +msgid "" +"Return true if all characters in the string are printable or the string is " +"empty, false otherwise. Nonprintable characters are those characters " +"defined in the Unicode character database as \"Other\" or \"Separator\", " +"excepting the ASCII space (0x20) which is considered printable. (Note that " +"printable characters in this context are those which should not be escaped " +"when :func:`repr` is invoked on a string. It has no bearing on the handling " +"of strings written to :data:`sys.stdout` or :data:`sys.stderr`.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1698 +msgid "" +"Return true if there are only whitespace characters in the string and there " +"is at least one character, false otherwise. Whitespace characters are " +"those characters defined in the Unicode character database as \"Other\" or " +"\"Separator\" and those with bidirectional property being one of \"WS\", \"B" +"\", or \"S\"." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1705 +msgid "" +"Return true if the string is a titlecased string and there is at least one " +"character, for example uppercase characters may only follow uncased " +"characters and lowercase characters only cased ones. Return false otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1712 +msgid "" +"Return true if all cased characters [4]_ in the string are uppercase and " +"there is at least one cased character, false otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1718 +msgid "" +"Return a string which is the concatenation of the strings in the :term:" +"`iterable` *iterable*. A :exc:`TypeError` will be raised if there are any " +"non-string values in *iterable*, including :class:`bytes` objects. The " +"separator between elements is the string providing this method." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1726 +msgid "" +"Return the string left justified in a string of length *width*. Padding is " +"done using the specified *fillchar* (default is an ASCII space). The " +"original string is returned if *width* is less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1733 +msgid "" +"Return a copy of the string with all the cased characters [4]_ converted to " +"lowercase." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1736 +msgid "" +"The lowercasing algorithm used is described in section 3.13 of the Unicode " +"Standard." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1742 +msgid "" +"Return a copy of the string with leading characters removed. The *chars* " +"argument is a string specifying the set of characters to be removed. If " +"omitted or ``None``, the *chars* argument defaults to removing whitespace. " +"The *chars* argument is not a prefix; rather, all combinations of its values " +"are stripped::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1755 +msgid "" +"This static method returns a translation table usable for :meth:`str." +"translate`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1757 +msgid "" +"If there is only one argument, it must be a dictionary mapping Unicode " +"ordinals (integers) or characters (strings of length 1) to Unicode ordinals, " +"strings (of arbitrary lengths) or None. Character keys will then be " +"converted to ordinals." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1762 +msgid "" +"If there are two arguments, they must be strings of equal length, and in the " +"resulting dictionary, each character in x will be mapped to the character at " +"the same position in y. If there is a third argument, it must be a string, " +"whose characters will be mapped to None in the result." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1770 +msgid "" +"Split the string at the first occurrence of *sep*, and return a 3-tuple " +"containing the part before the separator, the separator itself, and the part " +"after the separator. If the separator is not found, return a 3-tuple " +"containing the string itself, followed by two empty strings." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1778 +msgid "" +"Return a copy of the string with all occurrences of substring *old* replaced " +"by *new*. If the optional argument *count* is given, only the first *count* " +"occurrences are replaced." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1785 +msgid "" +"Return the highest index in the string where substring *sub* is found, such " +"that *sub* is contained within ``s[start:end]``. Optional arguments *start* " +"and *end* are interpreted as in slice notation. Return ``-1`` on failure." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1792 +msgid "" +"Like :meth:`rfind` but raises :exc:`ValueError` when the substring *sub* is " +"not found." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1798 +msgid "" +"Return the string right justified in a string of length *width*. Padding is " +"done using the specified *fillchar* (default is an ASCII space). The " +"original string is returned if *width* is less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1805 +msgid "" +"Split the string at the last occurrence of *sep*, and return a 3-tuple " +"containing the part before the separator, the separator itself, and the part " +"after the separator. If the separator is not found, return a 3-tuple " +"containing two empty strings, followed by the string itself." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1813 +msgid "" +"Return a list of the words in the string, using *sep* as the delimiter " +"string. If *maxsplit* is given, at most *maxsplit* splits are done, the " +"*rightmost* ones. If *sep* is not specified or ``None``, any whitespace " +"string is a separator. Except for splitting from the right, :meth:`rsplit` " +"behaves like :meth:`split` which is described in detail below." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1822 +msgid "" +"Return a copy of the string with trailing characters removed. The *chars* " +"argument is a string specifying the set of characters to be removed. If " +"omitted or ``None``, the *chars* argument defaults to removing whitespace. " +"The *chars* argument is not a suffix; rather, all combinations of its values " +"are stripped::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1835 +msgid "" +"Return a list of the words in the string, using *sep* as the delimiter " +"string. If *maxsplit* is given, at most *maxsplit* splits are done (thus, " +"the list will have at most ``maxsplit+1`` elements). If *maxsplit* is not " +"specified or ``-1``, then there is no limit on the number of splits (all " +"possible splits are made)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1841 +msgid "" +"If *sep* is given, consecutive delimiters are not grouped together and are " +"deemed to delimit empty strings (for example, ``'1,,2'.split(',')`` returns " +"``['1', '', '2']``). The *sep* argument may consist of multiple characters " +"(for example, ``'1<>2<>3'.split('<>')`` returns ``['1', '2', '3']``). " +"Splitting an empty string with a specified separator returns ``['']``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1856 +msgid "" +"If *sep* is not specified or is ``None``, a different splitting algorithm is " +"applied: runs of consecutive whitespace are regarded as a single separator, " +"and the result will contain no empty strings at the start or end if the " +"string has leading or trailing whitespace. Consequently, splitting an empty " +"string or a string consisting of just whitespace with a ``None`` separator " +"returns ``[]``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1878 +msgid "" +"Return a list of the lines in the string, breaking at line boundaries. Line " +"breaks are not included in the resulting list unless *keepends* is given and " +"true." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1882 +msgid "" +"This method splits on the following line boundaries. In particular, the " +"boundaries are a superset of :term:`universal newlines`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1886 +msgid "Representation" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1888 +msgid "``\\n``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1888 +msgid "Line Feed" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1890 +msgid "``\\r``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1890 +msgid "Carriage Return" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1892 +msgid "``\\r\\n``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1892 +msgid "Carriage Return + Line Feed" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1894 +msgid "``\\v`` or ``\\x0b``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1894 +msgid "Line Tabulation" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1896 +msgid "``\\f`` or ``\\x0c``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1896 +msgid "Form Feed" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1898 +msgid "``\\x1c``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1898 +msgid "File Separator" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1900 +msgid "``\\x1d``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1900 +msgid "Group Separator" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1902 +msgid "``\\x1e``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1902 +msgid "Record Separator" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1904 +msgid "``\\x85``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1904 +msgid "Next Line (C1 Control Code)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1906 +msgid "``\\u2028``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1906 +msgid "Line Separator" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1908 +msgid "``\\u2029``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1908 +msgid "Paragraph Separator" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1913 +msgid "``\\v`` and ``\\f`` added to list of line boundaries." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1922 +msgid "" +"Unlike :meth:`~str.split` when a delimiter string *sep* is given, this " +"method returns an empty list for the empty string, and a terminal line break " +"does not result in an extra line::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1931 +msgid "For comparison, ``split('\\n')`` gives::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1941 +msgid "" +"Return ``True`` if string starts with the *prefix*, otherwise return " +"``False``. *prefix* can also be a tuple of prefixes to look for. With " +"optional *start*, test string beginning at that position. With optional " +"*end*, stop comparing string at that position." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1949 +msgid "" +"Return a copy of the string with the leading and trailing characters " +"removed. The *chars* argument is a string specifying the set of characters " +"to be removed. If omitted or ``None``, the *chars* argument defaults to " +"removing whitespace. The *chars* argument is not a prefix or suffix; rather, " +"all combinations of its values are stripped::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1960 +msgid "" +"The outermost leading and trailing *chars* argument values are stripped from " +"the string. Characters are removed from the leading end until reaching a " +"string character that is not contained in the set of characters in *chars*. " +"A similar action takes place on the trailing end. For example::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1973 +msgid "" +"Return a copy of the string with uppercase characters converted to lowercase " +"and vice versa. Note that it is not necessarily true that ``s.swapcase()." +"swapcase() == s``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1980 +msgid "" +"Return a titlecased version of the string where words start with an " +"uppercase character and the remaining characters are lowercase." +msgstr "" + +#: ../Doc/library/stdtypes.rst:1988 ../Doc/library/stdtypes.rst:3084 +msgid "" +"The algorithm uses a simple language-independent definition of a word as " +"groups of consecutive letters. The definition works in many contexts but it " +"means that apostrophes in contractions and possessives form word boundaries, " +"which may not be the desired result::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:1996 ../Doc/library/stdtypes.rst:3092 +msgid "" +"A workaround for apostrophes can be constructed using regular expressions::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2011 +msgid "" +"Return a copy of the string in which each character has been mapped through " +"the given translation table. The table must be an object that implements " +"indexing via :meth:`__getitem__`, typically a :term:`mapping` or :term:" +"`sequence`. When indexed by a Unicode ordinal (an integer), the table " +"object can do any of the following: return a Unicode ordinal or a string, to " +"map the character to one or more other characters; return ``None``, to " +"delete the character from the return string; or raise a :exc:`LookupError` " +"exception, to map the character to itself." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2020 +msgid "" +"You can use :meth:`str.maketrans` to create a translation map from character-" +"to-character mappings in different formats." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2023 +msgid "" +"See also the :mod:`codecs` module for a more flexible approach to custom " +"character mappings." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2029 +msgid "" +"Return a copy of the string with all the cased characters [4]_ converted to " +"uppercase. Note that ``str.upper().isupper()`` might be ``False`` if ``s`` " +"contains uncased characters or if the Unicode category of the resulting " +"character(s) is not \"Lu\" (Letter, uppercase), but e.g. \"Lt\" (Letter, " +"titlecase)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2035 +msgid "" +"The uppercasing algorithm used is described in section 3.13 of the Unicode " +"Standard." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2041 +msgid "" +"Return a copy of the string left filled with ASCII ``'0'`` digits to make a " +"string of length *width*. A leading sign prefix (``'+'``/``'-'``) is handled " +"by inserting the padding *after* the sign character rather than before. The " +"original string is returned if *width* is less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2059 +msgid "``printf``-style String Formatting" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2073 +msgid "" +"The formatting operations described here exhibit a variety of quirks that " +"lead to a number of common errors (such as failing to display tuples and " +"dictionaries correctly). Using the newer :ref:`formatted string literals ` or the :meth:`str.format` interface helps avoid these errors. " +"These alternatives also provide more powerful, flexible and extensible " +"approaches to formatting text." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2080 +msgid "" +"String objects have one unique built-in operation: the ``%`` operator " +"(modulo). This is also known as the string *formatting* or *interpolation* " +"operator. Given ``format % values`` (where *format* is a string), ``%`` " +"conversion specifications in *format* are replaced with zero or more " +"elements of *values*. The effect is similar to using the :c:func:`sprintf` " +"in the C language." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2086 +msgid "" +"If *format* requires a single argument, *values* may be a single non-tuple " +"object. [5]_ Otherwise, *values* must be a tuple with exactly the number of " +"items specified by the format string, or a single mapping object (for " +"example, a dictionary)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2091 ../Doc/library/stdtypes.rst:3191 +msgid "" +"A conversion specifier contains two or more characters and has the following " +"components, which must occur in this order:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2094 ../Doc/library/stdtypes.rst:3194 +msgid "The ``'%'`` character, which marks the start of the specifier." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2096 ../Doc/library/stdtypes.rst:3196 +msgid "" +"Mapping key (optional), consisting of a parenthesised sequence of characters " +"(for example, ``(somename)``)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2099 ../Doc/library/stdtypes.rst:3199 +msgid "" +"Conversion flags (optional), which affect the result of some conversion " +"types." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2102 ../Doc/library/stdtypes.rst:3202 +msgid "" +"Minimum field width (optional). If specified as an ``'*'`` (asterisk), the " +"actual width is read from the next element of the tuple in *values*, and the " +"object to convert comes after the minimum field width and optional precision." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2106 ../Doc/library/stdtypes.rst:3206 +msgid "" +"Precision (optional), given as a ``'.'`` (dot) followed by the precision. " +"If specified as ``'*'`` (an asterisk), the actual precision is read from the " +"next element of the tuple in *values*, and the value to convert comes after " +"the precision." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2111 ../Doc/library/stdtypes.rst:3211 +msgid "Length modifier (optional)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2113 ../Doc/library/stdtypes.rst:3213 +msgid "Conversion type." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2115 +msgid "" +"When the right argument is a dictionary (or other mapping type), then the " +"formats in the string *must* include a parenthesised mapping key into that " +"dictionary inserted immediately after the ``'%'`` character. The mapping key " +"selects the value to be formatted from the mapping. For example:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2124 ../Doc/library/stdtypes.rst:3224 +msgid "" +"In this case no ``*`` specifiers may occur in a format (since they require a " +"sequential parameter list)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2127 ../Doc/library/stdtypes.rst:3227 +msgid "The conversion flag characters are:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2132 ../Doc/library/stdtypes.rst:3232 +msgid "``'#'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2132 ../Doc/library/stdtypes.rst:3232 +msgid "" +"The value conversion will use the \"alternate form\" (where defined below)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2135 ../Doc/library/stdtypes.rst:3235 +msgid "``'0'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2135 ../Doc/library/stdtypes.rst:3235 +msgid "The conversion will be zero padded for numeric values." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2137 ../Doc/library/stdtypes.rst:3237 +#: ../Doc/library/string.rst:355 +msgid "``'-'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2137 ../Doc/library/stdtypes.rst:3237 +msgid "" +"The converted value is left adjusted (overrides the ``'0'`` conversion if " +"both are given)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2140 ../Doc/library/stdtypes.rst:3240 +msgid "``' '``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2140 ../Doc/library/stdtypes.rst:3240 +msgid "" +"(a space) A blank should be left before a positive number (or empty string) " +"produced by a signed conversion." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2143 ../Doc/library/stdtypes.rst:3243 +msgid "" +"A sign character (``'+'`` or ``'-'``) will precede the conversion (overrides " +"a \"space\" flag)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2147 ../Doc/library/stdtypes.rst:3247 +msgid "" +"A length modifier (``h``, ``l``, or ``L``) may be present, but is ignored as " +"it is not necessary for Python -- so e.g. ``%ld`` is identical to ``%d``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2150 ../Doc/library/stdtypes.rst:3250 +msgid "The conversion types are:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2153 ../Doc/library/stdtypes.rst:3253 +msgid "Conversion" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2155 ../Doc/library/stdtypes.rst:2157 +#: ../Doc/library/stdtypes.rst:3255 ../Doc/library/stdtypes.rst:3257 +msgid "Signed integer decimal." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2159 ../Doc/library/stdtypes.rst:3259 +#: ../Doc/library/string.rst:432 +msgid "``'o'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2159 ../Doc/library/stdtypes.rst:3259 +msgid "Signed octal value." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2161 ../Doc/library/stdtypes.rst:3261 +msgid "Obsolete type -- it is identical to ``'d'``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2163 ../Doc/library/stdtypes.rst:3263 +msgid "Signed hexadecimal (lowercase)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2165 ../Doc/library/stdtypes.rst:3265 +#: ../Doc/library/string.rst:437 +msgid "``'X'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2165 ../Doc/library/stdtypes.rst:3265 +msgid "Signed hexadecimal (uppercase)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2167 ../Doc/library/stdtypes.rst:3267 +#: ../Doc/library/string.rst:457 +msgid "``'e'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2167 ../Doc/library/stdtypes.rst:3267 +msgid "Floating point exponential format (lowercase)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2169 ../Doc/library/stdtypes.rst:3269 +#: ../Doc/library/string.rst:461 +msgid "``'E'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2169 ../Doc/library/stdtypes.rst:3269 +msgid "Floating point exponential format (uppercase)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2171 ../Doc/library/stdtypes.rst:2173 +#: ../Doc/library/stdtypes.rst:3271 ../Doc/library/stdtypes.rst:3273 +msgid "Floating point decimal format." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2173 ../Doc/library/stdtypes.rst:3273 +#: ../Doc/library/string.rst:467 +msgid "``'F'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2175 ../Doc/library/stdtypes.rst:3275 +#: ../Doc/library/string.rst:470 +msgid "``'g'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2175 ../Doc/library/stdtypes.rst:3275 +msgid "" +"Floating point format. Uses lowercase exponential format if exponent is less " +"than -4 or not less than precision, decimal format otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2179 ../Doc/library/stdtypes.rst:3279 +#: ../Doc/library/string.rst:494 +msgid "``'G'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2179 ../Doc/library/stdtypes.rst:3279 +msgid "" +"Floating point format. Uses uppercase exponential format if exponent is less " +"than -4 or not less than precision, decimal format otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2183 +msgid "Single character (accepts integer or single character string)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2186 +msgid "String (converts any Python object using :func:`repr`)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2189 +msgid "String (converts any Python object using :func:`str`)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2192 +msgid "String (converts any Python object using :func:`ascii`)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2195 ../Doc/library/stdtypes.rst:3299 +#: ../Doc/library/string.rst:502 +msgid "``'%'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2195 ../Doc/library/stdtypes.rst:3299 +msgid "No argument is converted, results in a ``'%'`` character in the result." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2202 ../Doc/library/stdtypes.rst:3306 +msgid "" +"The alternate form causes a leading zero (``'0'``) to be inserted between " +"left-hand padding and the formatting of the number if the leading character " +"of the result is not already a zero." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2207 ../Doc/library/stdtypes.rst:3311 +msgid "" +"The alternate form causes a leading ``'0x'`` or ``'0X'`` (depending on " +"whether the ``'x'`` or ``'X'`` format was used) to be inserted between left-" +"hand padding and the formatting of the number if the leading character of " +"the result is not already a zero." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2213 ../Doc/library/stdtypes.rst:3317 +msgid "" +"The alternate form causes the result to always contain a decimal point, even " +"if no digits follow it." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2216 ../Doc/library/stdtypes.rst:3320 +msgid "" +"The precision determines the number of digits after the decimal point and " +"defaults to 6." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2220 ../Doc/library/stdtypes.rst:3324 +msgid "" +"The alternate form causes the result to always contain a decimal point, and " +"trailing zeroes are not removed as they would otherwise be." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2223 ../Doc/library/stdtypes.rst:3327 +msgid "" +"The precision determines the number of significant digits before and after " +"the decimal point and defaults to 6." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2227 ../Doc/library/stdtypes.rst:3331 +msgid "If precision is ``N``, the output is truncated to ``N`` characters." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2231 ../Doc/library/stdtypes.rst:3340 +msgid "See :pep:`237`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2233 +msgid "" +"Since Python strings have an explicit length, ``%s`` conversions do not " +"assume that ``'\\0'`` is the end of the string." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2238 +msgid "" +"``%f`` conversions for numbers whose absolute value is over 1e50 are no " +"longer replaced by ``%g`` conversions." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2249 +msgid "" +"Binary Sequence Types --- :class:`bytes`, :class:`bytearray`, :class:" +"`memoryview`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2257 +msgid "" +"The core built-in types for manipulating binary data are :class:`bytes` and :" +"class:`bytearray`. They are supported by :class:`memoryview` which uses the :" +"ref:`buffer protocol ` to access the memory of other binary " +"objects without needing to make a copy." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2262 +msgid "" +"The :mod:`array` module supports efficient storage of basic data types like " +"32-bit integers and IEEE754 double-precision floating values." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2268 +msgid "Bytes" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2272 +msgid "" +"Bytes objects are immutable sequences of single bytes. Since many major " +"binary protocols are based on the ASCII text encoding, bytes objects offer " +"several methods that are only valid when working with ASCII compatible data " +"and are closely related to string objects in a variety of other ways." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2277 +msgid "" +"Firstly, the syntax for bytes literals is largely the same as that for " +"string literals, except that a ``b`` prefix is added:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2280 +msgid "Single quotes: ``b'still allows embedded \"double\" quotes'``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2281 +msgid "Double quotes: ``b\"still allows embedded 'single' quotes\"``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2282 +msgid "" +"Triple quoted: ``b'''3 single quotes'''``, ``b\"\"\"3 double quotes\"\"\"``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2284 +msgid "" +"Only ASCII characters are permitted in bytes literals (regardless of the " +"declared source code encoding). Any binary values over 127 must be entered " +"into bytes literals using the appropriate escape sequence." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2288 +msgid "" +"As with string literals, bytes literals may also use a ``r`` prefix to " +"disable processing of escape sequences. See :ref:`strings` for more about " +"the various forms of bytes literal, including supported escape sequences." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2292 +msgid "" +"While bytes literals and representations are based on ASCII text, bytes " +"objects actually behave like immutable sequences of integers, with each " +"value in the sequence restricted such that ``0 <= x < 256`` (attempts to " +"violate this restriction will trigger :exc:`ValueError`. This is done " +"deliberately to emphasise that while many binary formats include ASCII based " +"elements and can be usefully manipulated with some text-oriented algorithms, " +"this is not generally the case for arbitrary binary data (blindly applying " +"text processing algorithms to binary data formats that are not ASCII " +"compatible will usually lead to data corruption)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2302 +msgid "" +"In addition to the literal forms, bytes objects can be created in a number " +"of other ways:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2305 +msgid "A zero-filled bytes object of a specified length: ``bytes(10)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2306 +msgid "From an iterable of integers: ``bytes(range(20))``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2307 +msgid "Copying existing binary data via the buffer protocol: ``bytes(obj)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2309 +msgid "Also see the :ref:`bytes ` built-in." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2311 +msgid "" +"Since 2 hexadecimal digits correspond precisely to a single byte, " +"hexadecimal numbers are a commonly used format for describing binary data. " +"Accordingly, the bytes type has an additional class method to read data in " +"that format:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2317 +msgid "" +"This :class:`bytes` class method returns a bytes object, decoding the given " +"string object. The string must contain two hexadecimal digits per byte, " +"with ASCII spaces being ignored." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2324 +msgid "" +"A reverse conversion function exists to transform a bytes object into its " +"hexadecimal representation." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2329 ../Doc/library/stdtypes.rst:2397 +msgid "" +"Return a string object containing two hexadecimal digits for each byte in " +"the instance." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2337 +msgid "" +"Since bytes objects are sequences of integers (akin to a tuple), for a bytes " +"object *b*, ``b[0]`` will be an integer, while ``b[0:1]`` will be a bytes " +"object of length 1. (This contrasts with text strings, where both indexing " +"and slicing will produce a string of length 1)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2342 +msgid "" +"The representation of bytes objects uses the literal format (``b'...'``) " +"since it is often more useful than e.g. ``bytes([46, 46, 46])``. You can " +"always convert a bytes object into a list of integers using ``list(b)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2347 +msgid "" +"For Python 2.x users: In the Python 2.x series, a variety of implicit " +"conversions between 8-bit strings (the closest thing 2.x offers to a built-" +"in binary data type) and Unicode strings were permitted. This was a " +"backwards compatibility workaround to account for the fact that Python " +"originally only supported 8-bit text, and Unicode text was a later addition. " +"In Python 3.x, those implicit conversions are gone - conversions between 8-" +"bit binary data and Unicode text must be explicit, and bytes and string " +"objects will always compare unequal." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2360 +msgid "Bytearray Objects" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2364 +msgid "" +":class:`bytearray` objects are a mutable counterpart to :class:`bytes` " +"objects. There is no dedicated literal syntax for bytearray objects, instead " +"they are always created by calling the constructor:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2368 +msgid "Creating an empty instance: ``bytearray()``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2369 +msgid "Creating a zero-filled instance with a given length: ``bytearray(10)``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2370 +msgid "From an iterable of integers: ``bytearray(range(20))``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2371 +msgid "" +"Copying existing binary data via the buffer protocol: ``bytearray(b'Hi!')``" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2373 +msgid "" +"As bytearray objects are mutable, they support the :ref:`mutable ` sequence operations in addition to the common bytes and bytearray " +"operations described in :ref:`bytes-methods`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2377 +msgid "Also see the :ref:`bytearray ` built-in." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2379 +msgid "" +"Since 2 hexadecimal digits correspond precisely to a single byte, " +"hexadecimal numbers are a commonly used format for describing binary data. " +"Accordingly, the bytearray type has an additional class method to read data " +"in that format:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2385 +msgid "" +"This :class:`bytearray` class method returns bytearray object, decoding the " +"given string object. The string must contain two hexadecimal digits per " +"byte, with ASCII spaces being ignored." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2392 +msgid "" +"A reverse conversion function exists to transform a bytearray object into " +"its hexadecimal representation." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2405 +msgid "" +"Since bytearray objects are sequences of integers (akin to a list), for a " +"bytearray object *b*, ``b[0]`` will be an integer, while ``b[0:1]`` will be " +"a bytearray object of length 1. (This contrasts with text strings, where " +"both indexing and slicing will produce a string of length 1)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2410 +msgid "" +"The representation of bytearray objects uses the bytes literal format " +"(``bytearray(b'...')``) since it is often more useful than e.g. " +"``bytearray([46, 46, 46])``. You can always convert a bytearray object into " +"a list of integers using ``list(b)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2419 +msgid "Bytes and Bytearray Operations" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2424 +msgid "" +"Both bytes and bytearray objects support the :ref:`common ` " +"sequence operations. They interoperate not just with operands of the same " +"type, but with any :term:`bytes-like object`. Due to this flexibility, they " +"can be freely mixed in operations without causing errors. However, the " +"return type of the result may depend on the order of operands." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2432 +msgid "" +"The methods on bytes and bytearray objects don't accept strings as their " +"arguments, just as the methods on strings don't accept bytes as their " +"arguments. For example, you have to write::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2444 +msgid "" +"Some bytes and bytearray operations assume the use of ASCII compatible " +"binary formats, and hence should be avoided when working with arbitrary " +"binary data. These restrictions are covered below." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2449 +msgid "" +"Using these ASCII based operations to manipulate binary data that is not " +"stored in an ASCII based format may lead to data corruption." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2452 +msgid "" +"The following methods on bytes and bytearray objects can be used with " +"arbitrary binary data." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2458 +msgid "" +"Return the number of non-overlapping occurrences of subsequence *sub* in the " +"range [*start*, *end*]. Optional arguments *start* and *end* are " +"interpreted as in slice notation." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2462 ../Doc/library/stdtypes.rst:2509 +#: ../Doc/library/stdtypes.rst:2531 ../Doc/library/stdtypes.rst:2596 +#: ../Doc/library/stdtypes.rst:2609 +msgid "" +"The subsequence to search for may be any :term:`bytes-like object` or an " +"integer in the range 0 to 255." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2465 ../Doc/library/stdtypes.rst:2521 +#: ../Doc/library/stdtypes.rst:2534 ../Doc/library/stdtypes.rst:2599 +#: ../Doc/library/stdtypes.rst:2612 +msgid "Also accept an integer in the range 0 to 255 as the subsequence." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2472 +msgid "" +"Return a string decoded from the given bytes. Default encoding is " +"``'utf-8'``. *errors* may be given to set a different error handling " +"scheme. The default for *errors* is ``'strict'``, meaning that encoding " +"errors raise a :exc:`UnicodeError`. Other possible values are ``'ignore'``, " +"``'replace'`` and any other name registered via :func:`codecs." +"register_error`, see section :ref:`error-handlers`. For a list of possible " +"encodings, see section :ref:`standard-encodings`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2482 +msgid "" +"Passing the *encoding* argument to :class:`str` allows decoding any :term:" +"`bytes-like object` directly, without needing to make a temporary bytes or " +"bytearray object." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2486 +msgid "Added support for keyword arguments." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2493 +msgid "" +"Return ``True`` if the binary data ends with the specified *suffix*, " +"otherwise return ``False``. *suffix* can also be a tuple of suffixes to " +"look for. With optional *start*, test beginning at that position. With " +"optional *end*, stop comparing at that position." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2498 +msgid "The suffix(es) to search for may be any :term:`bytes-like object`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2504 +msgid "" +"Return the lowest index in the data where the subsequence *sub* is found, " +"such that *sub* is contained in the slice ``s[start:end]``. Optional " +"arguments *start* and *end* are interpreted as in slice notation. Return " +"``-1`` if *sub* is not found." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2514 +msgid "" +"The :meth:`~bytes.find` method should be used only if you need to know the " +"position of *sub*. To check if *sub* is a substring or not, use the :" +"keyword:`in` operator::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2528 +msgid "" +"Like :meth:`~bytes.find`, but raise :exc:`ValueError` when the subsequence " +"is not found." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2541 +msgid "" +"Return a bytes or bytearray object which is the concatenation of the binary " +"data sequences in the :term:`iterable` *iterable*. A :exc:`TypeError` will " +"be raised if there are any values in *iterable* that are not :term:`bytes-" +"like objects `, including :class:`str` objects. The " +"separator between elements is the contents of the bytes or bytearray object " +"providing this method." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2552 +msgid "" +"This static method returns a translation table usable for :meth:`bytes." +"translate` that will map each character in *from* into the character at the " +"same position in *to*; *from* and *to* must both be :term:`bytes-like " +"objects ` and have the same length." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2563 +msgid "" +"Split the sequence at the first occurrence of *sep*, and return a 3-tuple " +"containing the part before the separator, the separator, and the part after " +"the separator. If the separator is not found, return a 3-tuple containing a " +"copy of the original sequence, followed by two empty bytes or bytearray " +"objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2569 ../Doc/library/stdtypes.rst:2625 +msgid "The separator to search for may be any :term:`bytes-like object`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2575 +msgid "" +"Return a copy of the sequence with all occurrences of subsequence *old* " +"replaced by *new*. If the optional argument *count* is given, only the " +"first *count* occurrences are replaced." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2579 +msgid "" +"The subsequence to search for and its replacement may be any :term:`bytes-" +"like object`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2584 ../Doc/library/stdtypes.rst:2676 +#: ../Doc/library/stdtypes.rst:2690 ../Doc/library/stdtypes.rst:2714 +#: ../Doc/library/stdtypes.rst:2728 ../Doc/library/stdtypes.rst:2763 +#: ../Doc/library/stdtypes.rst:2833 ../Doc/library/stdtypes.rst:2851 +#: ../Doc/library/stdtypes.rst:2879 ../Doc/library/stdtypes.rst:3008 +#: ../Doc/library/stdtypes.rst:3063 ../Doc/library/stdtypes.rst:3106 +#: ../Doc/library/stdtypes.rst:3127 ../Doc/library/stdtypes.rst:3149 +#: ../Doc/library/stdtypes.rst:3344 +msgid "" +"The bytearray version of this method does *not* operate in place - it always " +"produces a new object, even if no changes were made." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2591 +msgid "" +"Return the highest index in the sequence where the subsequence *sub* is " +"found, such that *sub* is contained within ``s[start:end]``. Optional " +"arguments *start* and *end* are interpreted as in slice notation. Return " +"``-1`` on failure." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2606 +msgid "" +"Like :meth:`~bytes.rfind` but raises :exc:`ValueError` when the subsequence " +"*sub* is not found." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2619 +msgid "" +"Split the sequence at the last occurrence of *sep*, and return a 3-tuple " +"containing the part before the separator, the separator, and the part after " +"the separator. If the separator is not found, return a 3-tuple containing a " +"copy of the original sequence, followed by two empty bytes or bytearray " +"objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2631 +msgid "" +"Return ``True`` if the binary data starts with the specified *prefix*, " +"otherwise return ``False``. *prefix* can also be a tuple of prefixes to " +"look for. With optional *start*, test beginning at that position. With " +"optional *end*, stop comparing at that position." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2636 +msgid "The prefix(es) to search for may be any :term:`bytes-like object`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2642 +msgid "" +"Return a copy of the bytes or bytearray object where all bytes occurring in " +"the optional argument *delete* are removed, and the remaining bytes have " +"been mapped through the given translation table, which must be a bytes " +"object of length 256." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2647 +msgid "" +"You can use the :func:`bytes.maketrans` method to create a translation table." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2650 +msgid "" +"Set the *table* argument to ``None`` for translations that only delete " +"characters::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2656 +msgid "*delete* is now supported as a keyword argument." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2660 +msgid "" +"The following methods on bytes and bytearray objects have default behaviours " +"that assume the use of ASCII compatible binary formats, but can still be " +"used with arbitrary binary data by passing appropriate arguments. Note that " +"all of the bytearray methods in this section do *not* operate in place, and " +"instead produce new objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2669 +msgid "" +"Return a copy of the object centered in a sequence of length *width*. " +"Padding is done using the specified *fillbyte* (default is an ASCII space). " +"For :class:`bytes` objects, the original sequence is returned if *width* is " +"less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2683 +msgid "" +"Return a copy of the object left justified in a sequence of length *width*. " +"Padding is done using the specified *fillbyte* (default is an ASCII space). " +"For :class:`bytes` objects, the original sequence is returned if *width* is " +"less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2697 +msgid "" +"Return a copy of the sequence with specified leading bytes removed. The " +"*chars* argument is a binary sequence specifying the set of byte values to " +"be removed - the name refers to the fact this method is usually used with " +"ASCII characters. If omitted or ``None``, the *chars* argument defaults to " +"removing ASCII whitespace. The *chars* argument is not a prefix; rather, " +"all combinations of its values are stripped::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2709 ../Doc/library/stdtypes.rst:2758 +#: ../Doc/library/stdtypes.rst:2828 +msgid "" +"The binary sequence of byte values to remove may be any :term:`bytes-like " +"object`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2721 +msgid "" +"Return a copy of the object right justified in a sequence of length *width*. " +"Padding is done using the specified *fillbyte* (default is an ASCII space). " +"For :class:`bytes` objects, the original sequence is returned if *width* is " +"less than or equal to ``len(s)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2735 +msgid "" +"Split the binary sequence into subsequences of the same type, using *sep* as " +"the delimiter string. If *maxsplit* is given, at most *maxsplit* splits are " +"done, the *rightmost* ones. If *sep* is not specified or ``None``, any " +"subsequence consisting solely of ASCII whitespace is a separator. Except for " +"splitting from the right, :meth:`rsplit` behaves like :meth:`split` which is " +"described in detail below." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2746 +msgid "" +"Return a copy of the sequence with specified trailing bytes removed. The " +"*chars* argument is a binary sequence specifying the set of byte values to " +"be removed - the name refers to the fact this method is usually used with " +"ASCII characters. If omitted or ``None``, the *chars* argument defaults to " +"removing ASCII whitespace. The *chars* argument is not a suffix; rather, " +"all combinations of its values are stripped::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2770 +msgid "" +"Split the binary sequence into subsequences of the same type, using *sep* as " +"the delimiter string. If *maxsplit* is given and non-negative, at most " +"*maxsplit* splits are done (thus, the list will have at most ``maxsplit+1`` " +"elements). If *maxsplit* is not specified or is ``-1``, then there is no " +"limit on the number of splits (all possible splits are made)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2776 +msgid "" +"If *sep* is given, consecutive delimiters are not grouped together and are " +"deemed to delimit empty subsequences (for example, ``b'1,,2'.split(b',')`` " +"returns ``[b'1', b'', b'2']``). The *sep* argument may consist of a " +"multibyte sequence (for example, ``b'1<>2<>3'.split(b'<>')`` returns " +"``[b'1', b'2', b'3']``). Splitting an empty sequence with a specified " +"separator returns ``[b'']`` or ``[bytearray(b'')]`` depending on the type of " +"object being split. The *sep* argument may be any :term:`bytes-like object`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2794 +msgid "" +"If *sep* is not specified or is ``None``, a different splitting algorithm is " +"applied: runs of consecutive ASCII whitespace are regarded as a single " +"separator, and the result will contain no empty strings at the start or end " +"if the sequence has leading or trailing whitespace. Consequently, splitting " +"an empty sequence or a sequence consisting solely of ASCII whitespace " +"without a specified separator returns ``[]``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2815 +msgid "" +"Return a copy of the sequence with specified leading and trailing bytes " +"removed. The *chars* argument is a binary sequence specifying the set of " +"byte values to be removed - the name refers to the fact this method is " +"usually used with ASCII characters. If omitted or ``None``, the *chars* " +"argument defaults to removing ASCII whitespace. The *chars* argument is not " +"a prefix or suffix; rather, all combinations of its values are stripped::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2837 +msgid "" +"The following methods on bytes and bytearray objects assume the use of ASCII " +"compatible binary formats and should not be applied to arbitrary binary " +"data. Note that all of the bytearray methods in this section do *not* " +"operate in place, and instead produce new objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2845 +msgid "" +"Return a copy of the sequence with each byte interpreted as an ASCII " +"character, and the first byte capitalized and the rest lowercased. Non-ASCII " +"byte values are passed through unchanged." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2858 +msgid "" +"Return a copy of the sequence where all ASCII tab characters are replaced by " +"one or more ASCII spaces, depending on the current column and the given tab " +"size. Tab positions occur every *tabsize* bytes (default is 8, giving tab " +"positions at columns 0, 8, 16 and so on). To expand the sequence, the " +"current column is set to zero and the sequence is examined byte by byte. If " +"the byte is an ASCII tab character (``b'\\t'``), one or more space " +"characters are inserted in the result until the current column is equal to " +"the next tab position. (The tab character itself is not copied.) If the " +"current byte is an ASCII newline (``b'\\n'``) or carriage return " +"(``b'\\r'``), it is copied and the current column is reset to zero. Any " +"other byte value is copied unchanged and the current column is incremented " +"by one regardless of how the byte value is represented when printed::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:2886 +msgid "" +"Return true if all bytes in the sequence are alphabetical ASCII characters " +"or ASCII decimal digits and the sequence is not empty, false otherwise. " +"Alphabetic ASCII characters are those byte values in the sequence " +"``b'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ'``. ASCII decimal " +"digits are those byte values in the sequence ``b'0123456789'``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2903 +msgid "" +"Return true if all bytes in the sequence are alphabetic ASCII characters and " +"the sequence is not empty, false otherwise. Alphabetic ASCII characters are " +"those byte values in the sequence " +"``b'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ'``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2919 +msgid "" +"Return true if all bytes in the sequence are ASCII decimal digits and the " +"sequence is not empty, false otherwise. ASCII decimal digits are those byte " +"values in the sequence ``b'0123456789'``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2934 +msgid "" +"Return true if there is at least one lowercase ASCII character in the " +"sequence and no uppercase ASCII characters, false otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2944 ../Doc/library/stdtypes.rst:2986 +#: ../Doc/library/stdtypes.rst:3002 ../Doc/library/stdtypes.rst:3052 +#: ../Doc/library/stdtypes.rst:3121 +msgid "" +"Lowercase ASCII characters are those byte values in the sequence " +"``b'abcdefghijklmnopqrstuvwxyz'``. Uppercase ASCII characters are those byte " +"values in the sequence ``b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2952 +msgid "" +"Return true if all bytes in the sequence are ASCII whitespace and the " +"sequence is not empty, false otherwise. ASCII whitespace characters are " +"those byte values in the sequence ``b' \\t\\n\\r\\x0b\\f'`` (space, tab, " +"newline, carriage return, vertical tab, form feed)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2961 +msgid "" +"Return true if the sequence is ASCII titlecase and the sequence is not " +"empty, false otherwise. See :meth:`bytes.title` for more details on the " +"definition of \"titlecase\"." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2976 +msgid "" +"Return true if there is at least one uppercase alphabetic ASCII character in " +"the sequence and no lowercase ASCII characters, false otherwise." +msgstr "" + +#: ../Doc/library/stdtypes.rst:2994 +msgid "" +"Return a copy of the sequence with all the uppercase ASCII characters " +"converted to their corresponding lowercase counterpart." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3019 +msgid "" +"Return a list of the lines in the binary sequence, breaking at ASCII line " +"boundaries. This method uses the :term:`universal newlines` approach to " +"splitting lines. Line breaks are not included in the resulting list unless " +"*keepends* is given and true." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3031 +msgid "" +"Unlike :meth:`~bytes.split` when a delimiter string *sep* is given, this " +"method returns an empty list for the empty string, and a terminal line break " +"does not result in an extra line::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3044 +msgid "" +"Return a copy of the sequence with all the lowercase ASCII characters " +"converted to their corresponding uppercase counterpart and vice-versa." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3056 +msgid "" +"Unlike :func:`str.swapcase()`, it is always the case that ``bin.swapcase()." +"swapcase() == bin`` for the binary versions. Case conversions are " +"symmetrical in ASCII, even though that is not generally true for arbitrary " +"Unicode code points." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3070 +msgid "" +"Return a titlecased version of the binary sequence where words start with an " +"uppercase ASCII character and the remaining characters are lowercase. " +"Uncased byte values are left unmodified." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3079 +msgid "" +"Lowercase ASCII characters are those byte values in the sequence " +"``b'abcdefghijklmnopqrstuvwxyz'``. Uppercase ASCII characters are those byte " +"values in the sequence ``b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'``. All other byte " +"values are uncased." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3113 +msgid "" +"Return a copy of the sequence with all the lowercase ASCII characters " +"converted to their corresponding uppercase counterpart." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3134 +msgid "" +"Return a copy of the sequence left filled with ASCII ``b'0'`` digits to make " +"a sequence of length *width*. A leading sign prefix (``b'+'``/ ``b'-'`` is " +"handled by inserting the padding *after* the sign character rather than " +"before. For :class:`bytes` objects, the original sequence is returned if " +"*width* is less than or equal to ``len(seq)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3156 +msgid "``printf``-style Bytes Formatting" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3174 +msgid "" +"The formatting operations described here exhibit a variety of quirks that " +"lead to a number of common errors (such as failing to display tuples and " +"dictionaries correctly). If the value being printed may be a tuple or " +"dictionary, wrap it in a tuple." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3179 +msgid "" +"Bytes objects (``bytes``/``bytearray``) have one unique built-in operation: " +"the ``%`` operator (modulo). This is also known as the bytes *formatting* or " +"*interpolation* operator. Given ``format % values`` (where *format* is a " +"bytes object), ``%`` conversion specifications in *format* are replaced with " +"zero or more elements of *values*. The effect is similar to using the :c:" +"func:`sprintf` in the C language." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3186 +msgid "" +"If *format* requires a single argument, *values* may be a single non-tuple " +"object. [5]_ Otherwise, *values* must be a tuple with exactly the number of " +"items specified by the format bytes object, or a single mapping object (for " +"example, a dictionary)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3215 +msgid "" +"When the right argument is a dictionary (or other mapping type), then the " +"formats in the bytes object *must* include a parenthesised mapping key into " +"that dictionary inserted immediately after the ``'%'`` character. The " +"mapping key selects the value to be formatted from the mapping. For example:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3283 +msgid "Single byte (accepts integer or single byte objects)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3286 +msgid "" +"Bytes (any object that follows the :ref:`buffer protocol ` or " +"has :meth:`__bytes__`)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3290 +msgid "" +"``'s'`` is an alias for ``'b'`` and should only be used for Python2/3 code " +"bases." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3293 +msgid "" +"Bytes (converts any Python object using ``repr(obj)." +"encode('ascii','backslashreplace)``)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3296 +msgid "" +"``'r'`` is an alias for ``'a'`` and should only be used for Python2/3 code " +"bases." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3334 +msgid "``b'%s'`` is deprecated, but will not be removed during the 3.x series." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3337 +msgid "``b'%r'`` is deprecated, but will not be removed during the 3.x series." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3347 +msgid ":pep:`461`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3353 +msgid "Memory Views" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3355 +msgid "" +":class:`memoryview` objects allow Python code to access the internal data of " +"an object that supports the :ref:`buffer protocol ` without " +"copying." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3361 +msgid "" +"Create a :class:`memoryview` that references *obj*. *obj* must support the " +"buffer protocol. Built-in objects that support the buffer protocol include :" +"class:`bytes` and :class:`bytearray`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3365 +msgid "" +"A :class:`memoryview` has the notion of an *element*, which is the atomic " +"memory unit handled by the originating object *obj*. For many simple types " +"such as :class:`bytes` and :class:`bytearray`, an element is a single byte, " +"but other types such as :class:`array.array` may have bigger elements." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3371 +msgid "" +"``len(view)`` is equal to the length of :class:`~memoryview.tolist`. If " +"``view.ndim = 0``, the length is 1. If ``view.ndim = 1``, the length is " +"equal to the number of elements in the view. For higher dimensions, the " +"length is equal to the length of the nested list representation of the view. " +"The :class:`~memoryview.itemsize` attribute will give you the number of " +"bytes in a single element." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3378 +msgid "" +"A :class:`memoryview` supports slicing and indexing to expose its data. One-" +"dimensional slicing will result in a subview::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3391 +msgid "" +"If :class:`~memoryview.format` is one of the native format specifiers from " +"the :mod:`struct` module, indexing with an integer or a tuple of integers is " +"also supported and returns a single *element* with the correct type. One-" +"dimensional memoryviews can be indexed with an integer or a one-integer " +"tuple. Multi-dimensional memoryviews can be indexed with tuples of exactly " +"*ndim* integers where *ndim* is the number of dimensions. Zero-dimensional " +"memoryviews can be indexed with the empty tuple." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3400 +msgid "Here is an example with a non-byte format::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3412 +msgid "" +"If the underlying object is writable, the memoryview supports one-" +"dimensional slice assignment. Resizing is not allowed::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3433 +msgid "" +"One-dimensional memoryviews of hashable (read-only) types with formats 'B', " +"'b' or 'c' are also hashable. The hash is defined as ``hash(m) == hash(m." +"tobytes())``::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3445 +msgid "" +"One-dimensional memoryviews can now be sliced. One-dimensional memoryviews " +"with formats 'B', 'b' or 'c' are now hashable." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3449 +msgid "" +"memoryview is now registered automatically with :class:`collections.abc." +"Sequence`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3453 +msgid "memoryviews can now be indexed with tuple of integers." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3456 +msgid ":class:`memoryview` has several methods:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3460 +msgid "" +"A memoryview and a :pep:`3118` exporter are equal if their shapes are " +"equivalent and if all corresponding values are equal when the operands' " +"respective format codes are interpreted using :mod:`struct` syntax." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3464 +msgid "" +"For the subset of :mod:`struct` format strings currently supported by :meth:" +"`tolist`, ``v`` and ``w`` are equal if ``v.tolist() == w.tolist()``::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3483 +msgid "" +"If either format string is not supported by the :mod:`struct` module, then " +"the objects will always compare as unequal (even if the format strings and " +"buffer contents are identical)::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3499 +msgid "" +"Note that, as with floating point numbers, ``v is w`` does *not* imply ``v " +"== w`` for memoryview objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3502 +msgid "" +"Previous versions compared the raw memory disregarding the item format and " +"the logical array structure." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3508 +msgid "" +"Return the data in the buffer as a bytestring. This is equivalent to " +"calling the :class:`bytes` constructor on the memoryview. ::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3517 +msgid "" +"For non-contiguous arrays the result is equal to the flattened list " +"representation with all elements converted to bytes. :meth:`tobytes` " +"supports all format strings, including those that are not in :mod:`struct` " +"module syntax." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3524 +msgid "" +"Return a string object containing two hexadecimal digits for each byte in " +"the buffer. ::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3535 +msgid "Return the data in the buffer as a list of elements. ::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3545 +msgid "" +":meth:`tolist` now supports all single character native formats in :mod:" +"`struct` module syntax as well as multi-dimensional representations." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3552 +msgid "" +"Release the underlying buffer exposed by the memoryview object. Many " +"objects take special actions when a view is held on them (for example, a :" +"class:`bytearray` would temporarily forbid resizing); therefore, calling " +"release() is handy to remove these restrictions (and free any dangling " +"resources) as soon as possible." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3558 +msgid "" +"After this method has been called, any further operation on the view raises " +"a :class:`ValueError` (except :meth:`release()` itself which can be called " +"multiple times)::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3569 +msgid "" +"The context management protocol can be used for a similar effect, using the " +"``with`` statement::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3585 +msgid "" +"Cast a memoryview to a new format or shape. *shape* defaults to " +"``[byte_length//new_itemsize]``, which means that the result view will be " +"one-dimensional. The return value is a new memoryview, but the buffer itself " +"is not copied. Supported casts are 1D -> C-:term:`contiguous` and C-" +"contiguous -> 1D." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3591 +msgid "" +"The destination format is restricted to a single element native format in :" +"mod:`struct` syntax. One of the formats must be a byte format ('B', 'b' or " +"'c'). The byte length of the result must be the same as the original length." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3596 +msgid "Cast 1D/long to 1D/unsigned bytes::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3619 +msgid "Cast 1D/unsigned bytes to 1D/char::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3632 +msgid "Cast 1D/bytes to 3D/ints to 1D/signed char::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3658 +msgid "Cast 1D/unsigned char to 2D/unsigned long::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3672 +msgid "The source format is no longer restricted when casting to a byte view." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3675 +msgid "There are also several readonly attributes available:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3679 +msgid "The underlying object of the memoryview::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3690 +msgid "" +"``nbytes == product(shape) * itemsize == len(m.tobytes())``. This is the " +"amount of space in bytes that the array would use in a contiguous " +"representation. It is not necessarily equal to len(m)::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3709 +msgid "Multi-dimensional arrays::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3726 +msgid "A bool indicating whether the memory is read only." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3730 +msgid "" +"A string containing the format (in :mod:`struct` module style) for each " +"element in the view. A memoryview can be created from exporters with " +"arbitrary format strings, but some methods (e.g. :meth:`tolist`) are " +"restricted to native single element formats." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3735 +msgid "" +"format ``'B'`` is now handled according to the struct module syntax. This " +"means that ``memoryview(b'abc')[0] == b'abc'[0] == 97``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3741 +msgid "The size in bytes of each element of the memoryview::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3754 +msgid "" +"An integer indicating how many dimensions of a multi-dimensional array the " +"memory represents." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3759 +msgid "" +"A tuple of integers the length of :attr:`ndim` giving the shape of the " +"memory as an N-dimensional array." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3762 ../Doc/library/stdtypes.rst:3770 +msgid "An empty tuple instead of None when ndim = 0." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3767 +msgid "" +"A tuple of integers the length of :attr:`ndim` giving the size in bytes to " +"access each element for each dimension of the array." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3775 +msgid "Used internally for PIL-style arrays. The value is informational only." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3779 +msgid "A bool indicating whether the memory is C-:term:`contiguous`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3785 +msgid "A bool indicating whether the memory is Fortran :term:`contiguous`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3791 +msgid "A bool indicating whether the memory is :term:`contiguous`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3799 +msgid "Set Types --- :class:`set`, :class:`frozenset`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3803 +msgid "" +"A :dfn:`set` object is an unordered collection of distinct :term:`hashable` " +"objects. Common uses include membership testing, removing duplicates from a " +"sequence, and computing mathematical operations such as intersection, union, " +"difference, and symmetric difference. (For other containers see the built-" +"in :class:`dict`, :class:`list`, and :class:`tuple` classes, and the :mod:" +"`collections` module.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3810 +msgid "" +"Like other collections, sets support ``x in set``, ``len(set)``, and ``for x " +"in set``. Being an unordered collection, sets do not record element " +"position or order of insertion. Accordingly, sets do not support indexing, " +"slicing, or other sequence-like behavior." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3815 +msgid "" +"There are currently two built-in set types, :class:`set` and :class:" +"`frozenset`. The :class:`set` type is mutable --- the contents can be " +"changed using methods like :meth:`~set.add` and :meth:`~set.remove`. Since " +"it is mutable, it has no hash value and cannot be used as either a " +"dictionary key or as an element of another set. The :class:`frozenset` type " +"is immutable and :term:`hashable` --- its contents cannot be altered after " +"it is created; it can therefore be used as a dictionary key or as an element " +"of another set." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3823 +msgid "" +"Non-empty sets (not frozensets) can be created by placing a comma-separated " +"list of elements within braces, for example: ``{'jack', 'sjoerd'}``, in " +"addition to the :class:`set` constructor." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3827 +msgid "The constructors for both classes work the same:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3832 +msgid "" +"Return a new set or frozenset object whose elements are taken from " +"*iterable*. The elements of a set must be :term:`hashable`. To represent " +"sets of sets, the inner sets must be :class:`frozenset` objects. If " +"*iterable* is not specified, a new empty set is returned." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3838 +msgid "" +"Instances of :class:`set` and :class:`frozenset` provide the following " +"operations:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3843 +msgid "Return the number of elements in set *s* (cardinality of *s*)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3847 +msgid "Test *x* for membership in *s*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3851 +msgid "Test *x* for non-membership in *s*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3855 +msgid "" +"Return ``True`` if the set has no elements in common with *other*. Sets are " +"disjoint if and only if their intersection is the empty set." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3861 +msgid "Test whether every element in the set is in *other*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3865 +msgid "" +"Test whether the set is a proper subset of *other*, that is, ``set <= other " +"and set != other``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3871 +msgid "Test whether every element in *other* is in the set." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3875 +msgid "" +"Test whether the set is a proper superset of *other*, that is, ``set >= " +"other and set != other``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3881 +msgid "Return a new set with elements from the set and all others." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3886 +msgid "Return a new set with elements common to the set and all others." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3891 +msgid "Return a new set with elements in the set that are not in the others." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3896 +msgid "" +"Return a new set with elements in either the set or *other* but not both." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3900 +msgid "Return a new set with a shallow copy of *s*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3903 +msgid "" +"Note, the non-operator versions of :meth:`union`, :meth:`intersection`, :" +"meth:`difference`, and :meth:`symmetric_difference`, :meth:`issubset`, and :" +"meth:`issuperset` methods will accept any iterable as an argument. In " +"contrast, their operator based counterparts require their arguments to be " +"sets. This precludes error-prone constructions like ``set('abc') & 'cbs'`` " +"in favor of the more readable ``set('abc').intersection('cbs')``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3910 +msgid "" +"Both :class:`set` and :class:`frozenset` support set to set comparisons. Two " +"sets are equal if and only if every element of each set is contained in the " +"other (each is a subset of the other). A set is less than another set if and " +"only if the first set is a proper subset of the second set (is a subset, but " +"is not equal). A set is greater than another set if and only if the first " +"set is a proper superset of the second set (is a superset, but is not equal)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3917 +msgid "" +"Instances of :class:`set` are compared to instances of :class:`frozenset` " +"based on their members. For example, ``set('abc') == frozenset('abc')`` " +"returns ``True`` and so does ``set('abc') in set([frozenset('abc')])``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3921 +msgid "" +"The subset and equality comparisons do not generalize to a total ordering " +"function. For example, any two nonempty disjoint sets are not equal and are " +"not subsets of each other, so *all* of the following return ``False``: " +"``ab``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3926 +msgid "" +"Since sets only define partial ordering (subset relationships), the output " +"of the :meth:`list.sort` method is undefined for lists of sets." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3929 +msgid "Set elements, like dictionary keys, must be :term:`hashable`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3931 +msgid "" +"Binary operations that mix :class:`set` instances with :class:`frozenset` " +"return the type of the first operand. For example: ``frozenset('ab') | " +"set('bc')`` returns an instance of :class:`frozenset`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3935 +msgid "" +"The following table lists operations available for :class:`set` that do not " +"apply to immutable instances of :class:`frozenset`:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:3941 +msgid "Update the set, adding elements from all others." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3946 +msgid "Update the set, keeping only elements found in it and all others." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3951 +msgid "Update the set, removing elements found in others." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3956 +msgid "" +"Update the set, keeping only elements found in either set, but not in both." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3960 +msgid "Add element *elem* to the set." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3964 +msgid "" +"Remove element *elem* from the set. Raises :exc:`KeyError` if *elem* is not " +"contained in the set." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3969 +msgid "Remove element *elem* from the set if it is present." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3973 +msgid "" +"Remove and return an arbitrary element from the set. Raises :exc:`KeyError` " +"if the set is empty." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3978 +msgid "Remove all elements from the set." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3981 +msgid "" +"Note, the non-operator versions of the :meth:`update`, :meth:" +"`intersection_update`, :meth:`difference_update`, and :meth:" +"`symmetric_difference_update` methods will accept any iterable as an " +"argument." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3986 +msgid "" +"Note, the *elem* argument to the :meth:`__contains__`, :meth:`remove`, and :" +"meth:`discard` methods may be a set. To support searching for an equivalent " +"frozenset, the *elem* set is temporarily mutated during the search and then " +"restored. During the search, the *elem* set should not be read or mutated " +"since it does not have a meaningful value." +msgstr "" + +#: ../Doc/library/stdtypes.rst:3996 +msgid "Mapping Types --- :class:`dict`" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4006 +msgid "" +"A :term:`mapping` object maps :term:`hashable` values to arbitrary objects. " +"Mappings are mutable objects. There is currently only one standard mapping " +"type, the :dfn:`dictionary`. (For other containers see the built-in :class:" +"`list`, :class:`set`, and :class:`tuple` classes, and the :mod:`collections` " +"module.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4012 +msgid "" +"A dictionary's keys are *almost* arbitrary values. Values that are not :" +"term:`hashable`, that is, values containing lists, dictionaries or other " +"mutable types (that are compared by value rather than by object identity) " +"may not be used as keys. Numeric types used for keys obey the normal rules " +"for numeric comparison: if two numbers compare equal (such as ``1`` and " +"``1.0``) then they can be used interchangeably to index the same dictionary " +"entry. (Note however, that since computers store floating-point numbers as " +"approximations it is usually unwise to use them as dictionary keys.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4021 +msgid "" +"Dictionaries can be created by placing a comma-separated list of ``key: " +"value`` pairs within braces, for example: ``{'jack': 4098, 'sjoerd': 4127}`` " +"or ``{4098: 'jack', 4127: 'sjoerd'}``, or by the :class:`dict` constructor." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4029 +msgid "" +"Return a new dictionary initialized from an optional positional argument and " +"a possibly empty set of keyword arguments." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4032 +msgid "" +"If no positional argument is given, an empty dictionary is created. If a " +"positional argument is given and it is a mapping object, a dictionary is " +"created with the same key-value pairs as the mapping object. Otherwise, the " +"positional argument must be an :term:`iterable` object. Each item in the " +"iterable must itself be an iterable with exactly two objects. The first " +"object of each item becomes a key in the new dictionary, and the second " +"object the corresponding value. If a key occurs more than once, the last " +"value for that key becomes the corresponding value in the new dictionary." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4042 +msgid "" +"If keyword arguments are given, the keyword arguments and their values are " +"added to the dictionary created from the positional argument. If a key " +"being added is already present, the value from the keyword argument replaces " +"the value from the positional argument." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4047 +msgid "" +"To illustrate, the following examples all return a dictionary equal to " +"``{\"one\": 1, \"two\": 2, \"three\": 3}``::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4058 +msgid "" +"Providing keyword arguments as in the first example only works for keys that " +"are valid Python identifiers. Otherwise, any valid keys can be used." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4062 +msgid "" +"These are the operations that dictionaries support (and therefore, custom " +"mapping types should support too):" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4067 +msgid "Return the number of items in the dictionary *d*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4071 +msgid "" +"Return the item of *d* with key *key*. Raises a :exc:`KeyError` if *key* is " +"not in the map." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4076 +msgid "" +"If a subclass of dict defines a method :meth:`__missing__` and *key* is not " +"present, the ``d[key]`` operation calls that method with the key *key* as " +"argument. The ``d[key]`` operation then returns or raises whatever is " +"returned or raised by the ``__missing__(key)`` call. No other operations or " +"methods invoke :meth:`__missing__`. If :meth:`__missing__` is not defined, :" +"exc:`KeyError` is raised. :meth:`__missing__` must be a method; it cannot be " +"an instance variable::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4094 +msgid "" +"The example above shows part of the implementation of :class:`collections." +"Counter`. A different ``__missing__`` method is used by :class:`collections." +"defaultdict`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4100 +msgid "Set ``d[key]`` to *value*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4104 +msgid "" +"Remove ``d[key]`` from *d*. Raises a :exc:`KeyError` if *key* is not in the " +"map." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4109 +msgid "Return ``True`` if *d* has a key *key*, else ``False``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4113 +msgid "Equivalent to ``not key in d``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4117 +msgid "" +"Return an iterator over the keys of the dictionary. This is a shortcut for " +"``iter(d.keys())``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4122 +msgid "Remove all items from the dictionary." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4126 +msgid "Return a shallow copy of the dictionary." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4130 +msgid "Create a new dictionary with keys from *seq* and values set to *value*." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4132 +msgid "" +":meth:`fromkeys` is a class method that returns a new dictionary. *value* " +"defaults to ``None``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4137 +msgid "" +"Return the value for *key* if *key* is in the dictionary, else *default*. If " +"*default* is not given, it defaults to ``None``, so that this method never " +"raises a :exc:`KeyError`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4143 +msgid "" +"Return a new view of the dictionary's items (``(key, value)`` pairs). See " +"the :ref:`documentation of view objects `." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4148 +msgid "" +"Return a new view of the dictionary's keys. See the :ref:`documentation of " +"view objects `." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4153 +msgid "" +"If *key* is in the dictionary, remove it and return its value, else return " +"*default*. If *default* is not given and *key* is not in the dictionary, a :" +"exc:`KeyError` is raised." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4159 +msgid "" +"Remove and return an arbitrary ``(key, value)`` pair from the dictionary." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4161 +msgid "" +":meth:`popitem` is useful to destructively iterate over a dictionary, as " +"often used in set algorithms. If the dictionary is empty, calling :meth:" +"`popitem` raises a :exc:`KeyError`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4167 +msgid "" +"If *key* is in the dictionary, return its value. If not, insert *key* with " +"a value of *default* and return *default*. *default* defaults to ``None``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4173 +msgid "" +"Update the dictionary with the key/value pairs from *other*, overwriting " +"existing keys. Return ``None``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4176 +msgid "" +":meth:`update` accepts either another dictionary object or an iterable of " +"key/value pairs (as tuples or other iterables of length two). If keyword " +"arguments are specified, the dictionary is then updated with those key/value " +"pairs: ``d.update(red=1, blue=2)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4183 +msgid "" +"Return a new view of the dictionary's values. See the :ref:`documentation " +"of view objects `." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4186 +msgid "" +"Dictionaries compare equal if and only if they have the same ``(key, " +"value)`` pairs. Order comparisons ('<', '<=', '>=', '>') raise :exc:" +"`TypeError`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4191 +msgid "" +":class:`types.MappingProxyType` can be used to create a read-only view of a :" +"class:`dict`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4198 +msgid "Dictionary view objects" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4200 +msgid "" +"The objects returned by :meth:`dict.keys`, :meth:`dict.values` and :meth:" +"`dict.items` are *view objects*. They provide a dynamic view on the " +"dictionary's entries, which means that when the dictionary changes, the view " +"reflects these changes." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4205 +msgid "" +"Dictionary views can be iterated over to yield their respective data, and " +"support membership tests:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4210 +msgid "Return the number of entries in the dictionary." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4214 +msgid "" +"Return an iterator over the keys, values or items (represented as tuples of " +"``(key, value)``) in the dictionary." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4217 +msgid "" +"Keys and values are iterated over in an arbitrary order which is non-random, " +"varies across Python implementations, and depends on the dictionary's " +"history of insertions and deletions. If keys, values and items views are " +"iterated over with no intervening modifications to the dictionary, the order " +"of items will directly correspond. This allows the creation of ``(value, " +"key)`` pairs using :func:`zip`: ``pairs = zip(d.values(), d.keys())``. " +"Another way to create the same list is ``pairs = [(v, k) for (k, v) in d." +"items()]``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4225 +msgid "" +"Iterating views while adding or deleting entries in the dictionary may raise " +"a :exc:`RuntimeError` or fail to iterate over all entries." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4230 +msgid "" +"Return ``True`` if *x* is in the underlying dictionary's keys, values or " +"items (in the latter case, *x* should be a ``(key, value)`` tuple)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4234 +msgid "" +"Keys views are set-like since their entries are unique and hashable. If all " +"values are hashable, so that ``(key, value)`` pairs are unique and hashable, " +"then the items view is also set-like. (Values views are not treated as set-" +"like since the entries are generally not unique.) For set-like views, all " +"of the operations defined for the abstract base class :class:`collections." +"abc.Set` are available (for example, ``==``, ``<``, or ``^``)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4241 +msgid "An example of dictionary view usage::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4276 +msgid "Context Manager Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4283 +msgid "" +"Python's :keyword:`with` statement supports the concept of a runtime context " +"defined by a context manager. This is implemented using a pair of methods " +"that allow user-defined classes to define a runtime context that is entered " +"before the statement body is executed and exited when the statement ends:" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4291 +msgid "" +"Enter the runtime context and return either this object or another object " +"related to the runtime context. The value returned by this method is bound " +"to the identifier in the :keyword:`as` clause of :keyword:`with` statements " +"using this context manager." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4296 +msgid "" +"An example of a context manager that returns itself is a :term:`file " +"object`. File objects return themselves from __enter__() to allow :func:" +"`open` to be used as the context expression in a :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4300 +msgid "" +"An example of a context manager that returns a related object is the one " +"returned by :func:`decimal.localcontext`. These managers set the active " +"decimal context to a copy of the original decimal context and then return " +"the copy. This allows changes to be made to the current decimal context in " +"the body of the :keyword:`with` statement without affecting code outside " +"the :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4310 +msgid "" +"Exit the runtime context and return a Boolean flag indicating if any " +"exception that occurred should be suppressed. If an exception occurred while " +"executing the body of the :keyword:`with` statement, the arguments contain " +"the exception type, value and traceback information. Otherwise, all three " +"arguments are ``None``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4315 +msgid "" +"Returning a true value from this method will cause the :keyword:`with` " +"statement to suppress the exception and continue execution with the " +"statement immediately following the :keyword:`with` statement. Otherwise the " +"exception continues propagating after this method has finished executing. " +"Exceptions that occur during execution of this method will replace any " +"exception that occurred in the body of the :keyword:`with` statement." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4322 +msgid "" +"The exception passed in should never be reraised explicitly - instead, this " +"method should return a false value to indicate that the method completed " +"successfully and does not want to suppress the raised exception. This allows " +"context management code to easily detect whether or not an :meth:`__exit__` " +"method has actually failed." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4328 +msgid "" +"Python defines several context managers to support easy thread " +"synchronisation, prompt closure of files or other objects, and simpler " +"manipulation of the active decimal arithmetic context. The specific types " +"are not treated specially beyond their implementation of the context " +"management protocol. See the :mod:`contextlib` module for some examples." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4334 +msgid "" +"Python's :term:`generator`\\s and the :class:`contextlib.contextmanager` " +"decorator provide a convenient way to implement these protocols. If a " +"generator function is decorated with the :class:`contextlib.contextmanager` " +"decorator, it will return a context manager implementing the necessary :meth:" +"`__enter__` and :meth:`__exit__` methods, rather than the iterator produced " +"by an undecorated generator function." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4341 +msgid "" +"Note that there is no specific slot for any of these methods in the type " +"structure for Python objects in the Python/C API. Extension types wanting to " +"define these methods must provide them as a normal Python accessible method. " +"Compared to the overhead of setting up the runtime context, the overhead of " +"a single class dictionary lookup is negligible." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4351 +msgid "Other Built-in Types" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4353 +msgid "" +"The interpreter supports several other kinds of objects. Most of these " +"support only one or two operations." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4360 +msgid "Modules" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4362 +msgid "" +"The only special operation on a module is attribute access: ``m.name``, " +"where *m* is a module and *name* accesses a name defined in *m*'s symbol " +"table. Module attributes can be assigned to. (Note that the :keyword:" +"`import` statement is not, strictly speaking, an operation on a module " +"object; ``import foo`` does not require a module object named *foo* to " +"exist, rather it requires an (external) *definition* for a module named " +"*foo* somewhere.)" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4369 +msgid "" +"A special attribute of every module is :attr:`~object.__dict__`. This is the " +"dictionary containing the module's symbol table. Modifying this dictionary " +"will actually change the module's symbol table, but direct assignment to " +"the :attr:`~object.__dict__` attribute is not possible (you can write ``m." +"__dict__['a'] = 1``, which defines ``m.a`` to be ``1``, but you can't write " +"``m.__dict__ = {}``). Modifying :attr:`~object.__dict__` directly is not " +"recommended." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4377 +msgid "" +"Modules built into the interpreter are written like this: ````. If loaded from a file, they are written as ````." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4385 +msgid "Classes and Class Instances" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4387 +msgid "See :ref:`objects` and :ref:`class` for these." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4395 +msgid "" +"Function objects are created by function definitions. The only operation on " +"a function object is to call it: ``func(argument-list)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4398 +msgid "" +"There are really two flavors of function objects: built-in functions and " +"user-defined functions. Both support the same operation (to call the " +"function), but the implementation is different, hence the different object " +"types." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4402 +msgid "See :ref:`function` for more information." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4412 +msgid "" +"Methods are functions that are called using the attribute notation. There " +"are two flavors: built-in methods (such as :meth:`append` on lists) and " +"class instance methods. Built-in methods are described with the types that " +"support them." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4417 +msgid "" +"If you access a method (a function defined in a class namespace) through an " +"instance, you get a special object: a :dfn:`bound method` (also called :dfn:" +"`instance method`) object. When called, it will add the ``self`` argument to " +"the argument list. Bound methods have two special read-only attributes: ``m." +"__self__`` is the object on which the method operates, and ``m.__func__`` is " +"the function implementing the method. Calling ``m(arg-1, arg-2, ..., arg-" +"n)`` is completely equivalent to calling ``m.__func__(m.__self__, arg-1, " +"arg-2, ..., arg-n)``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4426 +msgid "" +"Like function objects, bound method objects support getting arbitrary " +"attributes. However, since method attributes are actually stored on the " +"underlying function object (``meth.__func__``), setting method attributes on " +"bound methods is disallowed. Attempting to set an attribute on a method " +"results in an :exc:`AttributeError` being raised. In order to set a method " +"attribute, you need to explicitly set it on the underlying function object::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4446 ../Doc/library/stdtypes.rst:4474 +msgid "See :ref:`types` for more information." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4454 +msgid "Code Objects" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4460 +msgid "" +"Code objects are used by the implementation to represent \"pseudo-compiled\" " +"executable Python code such as a function body. They differ from function " +"objects because they don't contain a reference to their global execution " +"environment. Code objects are returned by the built-in :func:`compile` " +"function and can be extracted from function objects through their :attr:" +"`__code__` attribute. See also the :mod:`code` module." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4471 +msgid "" +"A code object can be executed or evaluated by passing it (instead of a " +"source string) to the :func:`exec` or :func:`eval` built-in functions." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4480 +msgid "Type Objects" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4486 +msgid "" +"Type objects represent the various object types. An object's type is " +"accessed by the built-in function :func:`type`. There are no special " +"operations on types. The standard module :mod:`types` defines names for all " +"standard built-in types." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4491 +msgid "Types are written like this: ````." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4497 +msgid "The Null Object" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4499 +msgid "" +"This object is returned by functions that don't explicitly return a value. " +"It supports no special operations. There is exactly one null object, named " +"``None`` (a built-in name). ``type(None)()`` produces the same singleton." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4503 +msgid "It is written as ``None``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4509 +msgid "The Ellipsis Object" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4511 +msgid "" +"This object is commonly used by slicing (see :ref:`slicings`). It supports " +"no special operations. There is exactly one ellipsis object, named :const:" +"`Ellipsis` (a built-in name). ``type(Ellipsis)()`` produces the :const:" +"`Ellipsis` singleton." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4516 +msgid "It is written as ``Ellipsis`` or ``...``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4522 +msgid "The NotImplemented Object" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4524 +msgid "" +"This object is returned from comparisons and binary operations when they are " +"asked to operate on types they don't support. See :ref:`comparisons` for " +"more information. There is exactly one ``NotImplemented`` object. " +"``type(NotImplemented)()`` produces the singleton instance." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4529 +msgid "It is written as ``NotImplemented``." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4535 +msgid "Boolean Values" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4537 +msgid "" +"Boolean values are the two constant objects ``False`` and ``True``. They " +"are used to represent truth values (although other values can also be " +"considered false or true). In numeric contexts (for example when used as " +"the argument to an arithmetic operator), they behave like the integers 0 and " +"1, respectively. The built-in function :func:`bool` can be used to convert " +"any value to a Boolean, if the value can be interpreted as a truth value " +"(see section :ref:`truth` above)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4550 +msgid "They are written as ``False`` and ``True``, respectively." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4556 +msgid "Internal Objects" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4558 +msgid "" +"See :ref:`types` for this information. It describes stack frame objects, " +"traceback objects, and slice objects." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4565 +msgid "Special Attributes" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4567 +msgid "" +"The implementation adds a few special read-only attributes to several object " +"types, where they are relevant. Some of these are not reported by the :func:" +"`dir` built-in function." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4574 +msgid "" +"A dictionary or other mapping object used to store an object's (writable) " +"attributes." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4580 +msgid "The class to which a class instance belongs." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4585 +msgid "The tuple of base classes of a class object." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4590 +msgid "" +"The name of the class, function, method, descriptor, or generator instance." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4596 +msgid "" +"The :term:`qualified name` of the class, function, method, descriptor, or " +"generator instance." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4604 +msgid "" +"This attribute is a tuple of classes that are considered when looking for " +"base classes during method resolution." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4610 +msgid "" +"This method can be overridden by a metaclass to customize the method " +"resolution order for its instances. It is called at class instantiation, " +"and its result is stored in :attr:`~class.__mro__`." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4617 +msgid "" +"Each class keeps a list of weak references to its immediate subclasses. " +"This method returns a list of all those references still alive. Example::" +msgstr "" + +#: ../Doc/library/stdtypes.rst:4627 +msgid "" +"Additional information on these special methods may be found in the Python " +"Reference Manual (:ref:`customization`)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4630 +msgid "" +"As a consequence, the list ``[1, 2]`` is considered equal to ``[1.0, 2.0]``, " +"and similarly for tuples." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4633 +msgid "They must have since the parser can't tell the type of the operands." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4635 +msgid "" +"Cased characters are those with general category property being one of \"Lu" +"\" (Letter, uppercase), \"Ll\" (Letter, lowercase), or \"Lt\" (Letter, " +"titlecase)." +msgstr "" + +#: ../Doc/library/stdtypes.rst:4638 +msgid "" +"To format only a tuple you should therefore provide a singleton tuple whose " +"only element is the tuple to be formatted." +msgstr "" + +#: ../Doc/library/string.rst:2 +msgid ":mod:`string` --- Common string operations" +msgstr "" + +#: ../Doc/library/string.rst:7 +msgid "**Source code:** :source:`Lib/string.py`" +msgstr "" + +#: ../Doc/library/string.rst:13 +msgid ":ref:`textseq`" +msgstr "" + +#: ../Doc/library/string.rst:15 +msgid ":ref:`string-methods`" +msgstr "" + +#: ../Doc/library/string.rst:18 +msgid "String constants" +msgstr "" + +#: ../Doc/library/string.rst:25 +msgid "" +"The concatenation of the :const:`ascii_lowercase` and :const:" +"`ascii_uppercase` constants described below. This value is not locale-" +"dependent." +msgstr "" + +#: ../Doc/library/string.rst:31 +msgid "" +"The lowercase letters ``'abcdefghijklmnopqrstuvwxyz'``. This value is not " +"locale-dependent and will not change." +msgstr "" + +#: ../Doc/library/string.rst:37 +msgid "" +"The uppercase letters ``'ABCDEFGHIJKLMNOPQRSTUVWXYZ'``. This value is not " +"locale-dependent and will not change." +msgstr "" + +#: ../Doc/library/string.rst:43 +msgid "The string ``'0123456789'``." +msgstr "" + +#: ../Doc/library/string.rst:48 +msgid "The string ``'0123456789abcdefABCDEF'``." +msgstr "" + +#: ../Doc/library/string.rst:53 +msgid "The string ``'01234567'``." +msgstr "" + +#: ../Doc/library/string.rst:58 +msgid "" +"String of ASCII characters which are considered punctuation characters in " +"the ``C`` locale." +msgstr "" + +#: ../Doc/library/string.rst:64 +msgid "" +"String of ASCII characters which are considered printable. This is a " +"combination of :const:`digits`, :const:`ascii_letters`, :const:" +"`punctuation`, and :const:`whitespace`." +msgstr "" + +#: ../Doc/library/string.rst:71 +msgid "" +"A string containing all ASCII characters that are considered whitespace. " +"This includes the characters space, tab, linefeed, return, formfeed, and " +"vertical tab." +msgstr "" + +#: ../Doc/library/string.rst:79 +msgid "Custom String Formatting" +msgstr "" + +#: ../Doc/library/string.rst:81 +msgid "" +"The built-in string class provides the ability to do complex variable " +"substitutions and value formatting via the :meth:`~str.format` method " +"described in :pep:`3101`. The :class:`Formatter` class in the :mod:`string` " +"module allows you to create and customize your own string formatting " +"behaviors using the same implementation as the built-in :meth:`~str.format` " +"method." +msgstr "" + +#: ../Doc/library/string.rst:90 +msgid "The :class:`Formatter` class has the following public methods:" +msgstr "" + +#: ../Doc/library/string.rst:94 +msgid "" +"The primary API method. It takes a format string and an arbitrary set of " +"positional and keyword arguments. It is just a wrapper that calls :meth:" +"`vformat`." +msgstr "" + +#: ../Doc/library/string.rst:98 +msgid "" +"Passing a format string as keyword argument *format_string* has been " +"deprecated." +msgstr "" + +#: ../Doc/library/string.rst:104 +msgid "" +"This function does the actual work of formatting. It is exposed as a " +"separate function for cases where you want to pass in a predefined " +"dictionary of arguments, rather than unpacking and repacking the dictionary " +"as individual arguments using the ``*args`` and ``**kwargs`` syntax. :meth:" +"`vformat` does the work of breaking up the format string into character data " +"and replacement fields. It calls the various methods described below." +msgstr "" + +#: ../Doc/library/string.rst:112 +msgid "" +"In addition, the :class:`Formatter` defines a number of methods that are " +"intended to be replaced by subclasses:" +msgstr "" + +#: ../Doc/library/string.rst:117 +msgid "" +"Loop over the format_string and return an iterable of tuples " +"(*literal_text*, *field_name*, *format_spec*, *conversion*). This is used " +"by :meth:`vformat` to break the string into either literal text, or " +"replacement fields." +msgstr "" + +#: ../Doc/library/string.rst:122 +msgid "" +"The values in the tuple conceptually represent a span of literal text " +"followed by a single replacement field. If there is no literal text (which " +"can happen if two replacement fields occur consecutively), then " +"*literal_text* will be a zero-length string. If there is no replacement " +"field, then the values of *field_name*, *format_spec* and *conversion* will " +"be ``None``." +msgstr "" + +#: ../Doc/library/string.rst:131 +msgid "" +"Given *field_name* as returned by :meth:`parse` (see above), convert it to " +"an object to be formatted. Returns a tuple (obj, used_key). The default " +"version takes strings of the form defined in :pep:`3101`, such as " +"\"0[name]\" or \"label.title\". *args* and *kwargs* are as passed in to :" +"meth:`vformat`. The return value *used_key* has the same meaning as the " +"*key* parameter to :meth:`get_value`." +msgstr "" + +#: ../Doc/library/string.rst:140 +msgid "" +"Retrieve a given field value. The *key* argument will be either an integer " +"or a string. If it is an integer, it represents the index of the positional " +"argument in *args*; if it is a string, then it represents a named argument " +"in *kwargs*." +msgstr "" + +#: ../Doc/library/string.rst:145 +msgid "" +"The *args* parameter is set to the list of positional arguments to :meth:" +"`vformat`, and the *kwargs* parameter is set to the dictionary of keyword " +"arguments." +msgstr "" + +#: ../Doc/library/string.rst:149 +msgid "" +"For compound field names, these functions are only called for the first " +"component of the field name; Subsequent components are handled through " +"normal attribute and indexing operations." +msgstr "" + +#: ../Doc/library/string.rst:153 +msgid "" +"So for example, the field expression '0.name' would cause :meth:`get_value` " +"to be called with a *key* argument of 0. The ``name`` attribute will be " +"looked up after :meth:`get_value` returns by calling the built-in :func:" +"`getattr` function." +msgstr "" + +#: ../Doc/library/string.rst:158 +msgid "" +"If the index or keyword refers to an item that does not exist, then an :exc:" +"`IndexError` or :exc:`KeyError` should be raised." +msgstr "" + +#: ../Doc/library/string.rst:163 +msgid "" +"Implement checking for unused arguments if desired. The arguments to this " +"function is the set of all argument keys that were actually referred to in " +"the format string (integers for positional arguments, and strings for named " +"arguments), and a reference to the *args* and *kwargs* that was passed to " +"vformat. The set of unused args can be calculated from these parameters. :" +"meth:`check_unused_args` is assumed to raise an exception if the check fails." +msgstr "" + +#: ../Doc/library/string.rst:173 +msgid "" +":meth:`format_field` simply calls the global :func:`format` built-in. The " +"method is provided so that subclasses can override it." +msgstr "" + +#: ../Doc/library/string.rst:178 +msgid "" +"Converts the value (returned by :meth:`get_field`) given a conversion type " +"(as in the tuple returned by the :meth:`parse` method). The default version " +"understands 's' (str), 'r' (repr) and 'a' (ascii) conversion types." +msgstr "" + +#: ../Doc/library/string.rst:187 +msgid "Format String Syntax" +msgstr "" + +#: ../Doc/library/string.rst:189 +msgid "" +"The :meth:`str.format` method and the :class:`Formatter` class share the " +"same syntax for format strings (although in the case of :class:`Formatter`, " +"subclasses can define their own format string syntax). The syntax is " +"related to that of :ref:`formatted string literals `, but there " +"are differences." +msgstr "" + +#: ../Doc/library/string.rst:195 +msgid "" +"Format strings contain \"replacement fields\" surrounded by curly braces ``{}" +"``. Anything that is not contained in braces is considered literal text, " +"which is copied unchanged to the output. If you need to include a brace " +"character in the literal text, it can be escaped by doubling: ``{{`` and ``}}" +"``." +msgstr "" + +#: ../Doc/library/string.rst:200 +msgid "The grammar for a replacement field is as follows:" +msgstr "" + +#: ../Doc/library/string.rst:212 +msgid "" +"In less formal terms, the replacement field can start with a *field_name* " +"that specifies the object whose value is to be formatted and inserted into " +"the output instead of the replacement field. The *field_name* is optionally " +"followed by a *conversion* field, which is preceded by an exclamation point " +"``'!'``, and a *format_spec*, which is preceded by a colon ``':'``. These " +"specify a non-default format for the replacement value." +msgstr "" + +#: ../Doc/library/string.rst:219 +msgid "See also the :ref:`formatspec` section." +msgstr "" + +#: ../Doc/library/string.rst:221 +msgid "" +"The *field_name* itself begins with an *arg_name* that is either a number or " +"a keyword. If it's a number, it refers to a positional argument, and if " +"it's a keyword, it refers to a named keyword argument. If the numerical " +"arg_names in a format string are 0, 1, 2, ... in sequence, they can all be " +"omitted (not just some) and the numbers 0, 1, 2, ... will be automatically " +"inserted in that order. Because *arg_name* is not quote-delimited, it is not " +"possible to specify arbitrary dictionary keys (e.g., the strings ``'10'`` or " +"``':-]'``) within a format string. The *arg_name* can be followed by any " +"number of index or attribute expressions. An expression of the form ``'." +"name'`` selects the named attribute using :func:`getattr`, while an " +"expression of the form ``'[index]'`` does an index lookup using :func:" +"`__getitem__`." +msgstr "" + +#: ../Doc/library/string.rst:233 +msgid "" +"The positional argument specifiers can be omitted, so ``'{} {}'`` is " +"equivalent to ``'{0} {1}'``." +msgstr "" + +#: ../Doc/library/string.rst:237 +msgid "Some simple format string examples::" +msgstr "" + +#: ../Doc/library/string.rst:246 +msgid "" +"The *conversion* field causes a type coercion before formatting. Normally, " +"the job of formatting a value is done by the :meth:`__format__` method of " +"the value itself. However, in some cases it is desirable to force a type to " +"be formatted as a string, overriding its own definition of formatting. By " +"converting the value to a string before calling :meth:`__format__`, the " +"normal formatting logic is bypassed." +msgstr "" + +#: ../Doc/library/string.rst:253 +msgid "" +"Three conversion flags are currently supported: ``'!s'`` which calls :func:" +"`str` on the value, ``'!r'`` which calls :func:`repr` and ``'!a'`` which " +"calls :func:`ascii`." +msgstr "" + +#: ../Doc/library/string.rst:257 +msgid "Some examples::" +msgstr "" + +#: ../Doc/library/string.rst:263 +msgid "" +"The *format_spec* field contains a specification of how the value should be " +"presented, including such details as field width, alignment, padding, " +"decimal precision and so on. Each value type can define its own " +"\"formatting mini-language\" or interpretation of the *format_spec*." +msgstr "" + +#: ../Doc/library/string.rst:268 +msgid "" +"Most built-in types support a common formatting mini-language, which is " +"described in the next section." +msgstr "" + +#: ../Doc/library/string.rst:271 +msgid "" +"A *format_spec* field can also include nested replacement fields within it. " +"These nested replacement fields may contain a field name, conversion flag " +"and format specification, but deeper nesting is not allowed. The " +"replacement fields within the format_spec are substituted before the " +"*format_spec* string is interpreted. This allows the formatting of a value " +"to be dynamically specified." +msgstr "" + +#: ../Doc/library/string.rst:278 +msgid "See the :ref:`formatexamples` section for some examples." +msgstr "" + +#: ../Doc/library/string.rst:284 +msgid "Format Specification Mini-Language" +msgstr "" + +#: ../Doc/library/string.rst:286 +msgid "" +"\"Format specifications\" are used within replacement fields contained " +"within a format string to define how individual values are presented (see :" +"ref:`formatstrings` and :ref:`f-strings`). They can also be passed directly " +"to the built-in :func:`format` function. Each formattable type may define " +"how the format specification is to be interpreted." +msgstr "" + +#: ../Doc/library/string.rst:293 +msgid "" +"Most built-in types implement the following options for format " +"specifications, although some of the formatting options are only supported " +"by the numeric types." +msgstr "" + +#: ../Doc/library/string.rst:296 +msgid "" +"A general convention is that an empty format string (``\"\"``) produces the " +"same result as if you had called :func:`str` on the value. A non-empty " +"format string typically modifies the result." +msgstr "" + +#: ../Doc/library/string.rst:300 +msgid "The general form of a *standard format specifier* is:" +msgstr "" + +#: ../Doc/library/string.rst:312 +msgid "" +"If a valid *align* value is specified, it can be preceded by a *fill* " +"character that can be any character and defaults to a space if omitted. It " +"is not possible to use a literal curly brace (\"``{``\" or \"``}``\") as the " +"*fill* character in a :ref:`formatted string literal ` or when " +"using the :meth:`str.format` method. However, it is possible to insert a " +"curly brace with a nested replacement field. This limitation doesn't affect " +"the :func:`format` function." +msgstr "" + +#: ../Doc/library/string.rst:321 +msgid "The meaning of the various alignment options is as follows:" +msgstr "" + +#: ../Doc/library/string.rst:324 ../Doc/library/string.rst:350 +#: ../Doc/library/tkinter.ttk.rst:112 ../Doc/library/tkinter.ttk.rst:147 +#: ../Doc/library/tkinter.ttk.rst:173 ../Doc/library/tkinter.ttk.rst:216 +#: ../Doc/library/tkinter.ttk.rst:319 ../Doc/library/tkinter.ttk.rst:400 +#: ../Doc/library/tkinter.ttk.rst:426 ../Doc/library/tkinter.ttk.rst:590 +#: ../Doc/library/tkinter.ttk.rst:661 ../Doc/library/tkinter.ttk.rst:729 +#: ../Doc/library/tkinter.ttk.rst:780 ../Doc/library/tkinter.ttk.rst:808 +msgid "Option" +msgstr "" + +#: ../Doc/library/string.rst:326 +msgid "``'<'``" +msgstr "" + +#: ../Doc/library/string.rst:326 +msgid "" +"Forces the field to be left-aligned within the available space (this is the " +"default for most objects)." +msgstr "" + +#: ../Doc/library/string.rst:329 +msgid "``'>'``" +msgstr "" + +#: ../Doc/library/string.rst:329 +msgid "" +"Forces the field to be right-aligned within the available space (this is the " +"default for numbers)." +msgstr "" + +#: ../Doc/library/string.rst:332 +msgid "``'='``" +msgstr "" + +#: ../Doc/library/string.rst:332 +msgid "" +"Forces the padding to be placed after the sign (if any) but before the " +"digits. This is used for printing fields in the form '+000000120'. This " +"alignment option is only valid for numeric types. It becomes the default " +"when '0' immediately precedes the field width." +msgstr "" + +#: ../Doc/library/string.rst:338 +msgid "Forces the field to be centered within the available space." +msgstr "" + +#: ../Doc/library/string.rst:342 +msgid "" +"Note that unless a minimum field width is defined, the field width will " +"always be the same size as the data to fill it, so that the alignment option " +"has no meaning in this case." +msgstr "" + +#: ../Doc/library/string.rst:346 +msgid "" +"The *sign* option is only valid for number types, and can be one of the " +"following:" +msgstr "" + +#: ../Doc/library/string.rst:352 +msgid "" +"indicates that a sign should be used for both positive as well as negative " +"numbers." +msgstr "" + +#: ../Doc/library/string.rst:355 +msgid "" +"indicates that a sign should be used only for negative numbers (this is the " +"default behavior)." +msgstr "" + +#: ../Doc/library/string.rst:358 +msgid "space" +msgstr "" + +#: ../Doc/library/string.rst:358 +msgid "" +"indicates that a leading space should be used on positive numbers, and a " +"minus sign on negative numbers." +msgstr "" + +#: ../Doc/library/string.rst:363 +msgid "" +"The ``'#'`` option causes the \"alternate form\" to be used for the " +"conversion. The alternate form is defined differently for different types. " +"This option is only valid for integer, float, complex and Decimal types. For " +"integers, when binary, octal, or hexadecimal output is used, this option " +"adds the prefix respective ``'0b'``, ``'0o'``, or ``'0x'`` to the output " +"value. For floats, complex and Decimal the alternate form causes the result " +"of the conversion to always contain a decimal-point character, even if no " +"digits follow it. Normally, a decimal-point character appears in the result " +"of these conversions only if a digit follows it. In addition, for ``'g'`` " +"and ``'G'`` conversions, trailing zeros are not removed from the result." +msgstr "" + +#: ../Doc/library/string.rst:375 +msgid "" +"The ``','`` option signals the use of a comma for a thousands separator. For " +"a locale aware separator, use the ``'n'`` integer presentation type instead." +msgstr "" + +#: ../Doc/library/string.rst:379 +msgid "Added the ``','`` option (see also :pep:`378`)." +msgstr "" + +#: ../Doc/library/string.rst:382 +msgid "" +"The ``'_'`` option signals the use of an underscore for a thousands " +"separator for floating point presentation types and for integer presentation " +"type ``'d'``. For integer presentation types ``'b'``, ``'o'``, ``'x'``, and " +"``'X'``, underscores will be inserted every 4 digits. For other " +"presentation types, specifying this option is an error." +msgstr "" + +#: ../Doc/library/string.rst:389 +msgid "Added the ``'_'`` option (see also :pep:`515`)." +msgstr "" + +#: ../Doc/library/string.rst:392 +msgid "" +"*width* is a decimal integer defining the minimum field width. If not " +"specified, then the field width will be determined by the content." +msgstr "" + +#: ../Doc/library/string.rst:395 +msgid "" +"When no explicit alignment is given, preceding the *width* field by a zero " +"(``'0'``) character enables sign-aware zero-padding for numeric types. This " +"is equivalent to a *fill* character of ``'0'`` with an *alignment* type of " +"``'='``." +msgstr "" + +#: ../Doc/library/string.rst:400 +msgid "" +"The *precision* is a decimal number indicating how many digits should be " +"displayed after the decimal point for a floating point value formatted with " +"``'f'`` and ``'F'``, or before and after the decimal point for a floating " +"point value formatted with ``'g'`` or ``'G'``. For non-number types the " +"field indicates the maximum field size - in other words, how many characters " +"will be used from the field content. The *precision* is not allowed for " +"integer values." +msgstr "" + +#: ../Doc/library/string.rst:407 +msgid "Finally, the *type* determines how the data should be presented." +msgstr "" + +#: ../Doc/library/string.rst:409 +msgid "The available string presentation types are:" +msgstr "" + +#: ../Doc/library/string.rst:414 +msgid "String format. This is the default type for strings and may be omitted." +msgstr "" + +#: ../Doc/library/string.rst:417 +msgid "The same as ``'s'``." +msgstr "" + +#: ../Doc/library/string.rst:420 +msgid "The available integer presentation types are:" +msgstr "" + +#: ../Doc/library/string.rst:425 +msgid "Binary format. Outputs the number in base 2." +msgstr "" + +#: ../Doc/library/string.rst:427 +msgid "" +"Character. Converts the integer to the corresponding unicode character " +"before printing." +msgstr "" + +#: ../Doc/library/string.rst:430 +msgid "Decimal Integer. Outputs the number in base 10." +msgstr "" + +#: ../Doc/library/string.rst:432 +msgid "Octal format. Outputs the number in base 8." +msgstr "" + +#: ../Doc/library/string.rst:434 +msgid "" +"Hex format. Outputs the number in base 16, using lower- case letters for the " +"digits above 9." +msgstr "" + +#: ../Doc/library/string.rst:437 +msgid "" +"Hex format. Outputs the number in base 16, using upper- case letters for the " +"digits above 9." +msgstr "" + +#: ../Doc/library/string.rst:440 +msgid "" +"Number. This is the same as ``'d'``, except that it uses the current locale " +"setting to insert the appropriate number separator characters." +msgstr "" + +#: ../Doc/library/string.rst:444 +msgid "The same as ``'d'``." +msgstr "" + +#: ../Doc/library/string.rst:447 +msgid "" +"In addition to the above presentation types, integers can be formatted with " +"the floating point presentation types listed below (except ``'n'`` and " +"None). When doing so, :func:`float` is used to convert the integer to a " +"floating point number before formatting." +msgstr "" + +#: ../Doc/library/string.rst:452 +msgid "" +"The available presentation types for floating point and decimal values are:" +msgstr "" + +#: ../Doc/library/string.rst:457 +msgid "" +"Exponent notation. Prints the number in scientific notation using the letter " +"'e' to indicate the exponent. The default precision is ``6``." +msgstr "" + +#: ../Doc/library/string.rst:461 +msgid "" +"Exponent notation. Same as ``'e'`` except it uses an upper case 'E' as the " +"separator character." +msgstr "" + +#: ../Doc/library/string.rst:464 +msgid "" +"Fixed point. Displays the number as a fixed-point number. The default " +"precision is ``6``." +msgstr "" + +#: ../Doc/library/string.rst:467 +msgid "" +"Fixed point. Same as ``'f'``, but converts ``nan`` to ``NAN`` and ``inf`` to " +"``INF``." +msgstr "" + +#: ../Doc/library/string.rst:470 +msgid "" +"General format. For a given precision ``p >= 1``, this rounds the number to " +"``p`` significant digits and then formats the result in either fixed-point " +"format or in scientific notation, depending on its magnitude." +msgstr "" + +#: ../Doc/library/string.rst:475 +msgid "" +"The precise rules are as follows: suppose that the result formatted with " +"presentation type ``'e'`` and precision ``p-1`` would have exponent " +"``exp``. Then if ``-4 <= exp < p``, the number is formatted with " +"presentation type ``'f'`` and precision ``p-1-exp``. Otherwise, the number " +"is formatted with presentation type ``'e'`` and precision ``p-1``. In both " +"cases insignificant trailing zeros are removed from the significand, and the " +"decimal point is also removed if there are no remaining digits following it." +msgstr "" + +#: ../Doc/library/string.rst:486 +msgid "" +"Positive and negative infinity, positive and negative zero, and nans, are " +"formatted as ``inf``, ``-inf``, ``0``, ``-0`` and ``nan`` respectively, " +"regardless of the precision." +msgstr "" + +#: ../Doc/library/string.rst:491 +msgid "" +"A precision of ``0`` is treated as equivalent to a precision of ``1``. The " +"default precision is ``6``." +msgstr "" + +#: ../Doc/library/string.rst:494 +msgid "" +"General format. Same as ``'g'`` except switches to ``'E'`` if the number " +"gets too large. The representations of infinity and NaN are uppercased, too." +msgstr "" + +#: ../Doc/library/string.rst:498 +msgid "" +"Number. This is the same as ``'g'``, except that it uses the current locale " +"setting to insert the appropriate number separator characters." +msgstr "" + +#: ../Doc/library/string.rst:502 +msgid "" +"Percentage. Multiplies the number by 100 and displays in fixed (``'f'``) " +"format, followed by a percent sign." +msgstr "" + +#: ../Doc/library/string.rst:505 +msgid "" +"Similar to ``'g'``, except that fixed-point notation, when used, has at " +"least one digit past the decimal point. The default precision is as high as " +"needed to represent the particular value. The overall effect is to match the " +"output of :func:`str` as altered by the other format modifiers." +msgstr "" + +#: ../Doc/library/string.rst:517 +msgid "Format examples" +msgstr "" + +#: ../Doc/library/string.rst:519 +msgid "" +"This section contains examples of the :meth:`str.format` syntax and " +"comparison with the old ``%``-formatting." +msgstr "" + +#: ../Doc/library/string.rst:522 +msgid "" +"In most of the cases the syntax is similar to the old ``%``-formatting, with " +"the addition of the ``{}`` and with ``:`` used instead of ``%``. For " +"example, ``'%03.2f'`` can be translated to ``'{:03.2f}'``." +msgstr "" + +#: ../Doc/library/string.rst:526 +msgid "" +"The new format syntax also supports new and different options, shown in the " +"follow examples." +msgstr "" + +#: ../Doc/library/string.rst:529 +msgid "Accessing arguments by position::" +msgstr "" + +#: ../Doc/library/string.rst:542 +msgid "Accessing arguments by name::" +msgstr "" + +#: ../Doc/library/string.rst:550 +msgid "Accessing arguments' attributes::" +msgstr "" + +#: ../Doc/library/string.rst:565 +msgid "Accessing arguments' items::" +msgstr "" + +#: ../Doc/library/string.rst:571 +msgid "Replacing ``%s`` and ``%r``::" +msgstr "" + +#: ../Doc/library/string.rst:576 +msgid "Aligning the text and specifying a width::" +msgstr "" + +#: ../Doc/library/string.rst:587 +msgid "Replacing ``%+f``, ``%-f``, and ``% f`` and specifying a sign::" +msgstr "" + +#: ../Doc/library/string.rst:596 +msgid "" +"Replacing ``%x`` and ``%o`` and converting the value to different bases::" +msgstr "" + +#: ../Doc/library/string.rst:605 +msgid "Using the comma as a thousands separator::" +msgstr "" + +#: ../Doc/library/string.rst:610 +msgid "Expressing a percentage::" +msgstr "" + +#: ../Doc/library/string.rst:617 +msgid "Using type-specific formatting::" +msgstr "" + +#: ../Doc/library/string.rst:624 +msgid "Nesting arguments and more complex examples::" +msgstr "" + +#: ../Doc/library/string.rst:658 +msgid "Template strings" +msgstr "" + +#: ../Doc/library/string.rst:660 +msgid "" +"Templates provide simpler string substitutions as described in :pep:`292`. " +"Instead of the normal ``%``\\ -based substitutions, Templates support ``$``" +"\\ -based substitutions, using the following rules:" +msgstr "" + +#: ../Doc/library/string.rst:664 +msgid "``$$`` is an escape; it is replaced with a single ``$``." +msgstr "" + +#: ../Doc/library/string.rst:666 +msgid "" +"``$identifier`` names a substitution placeholder matching a mapping key of ``" +"\"identifier\"``. By default, ``\"identifier\"`` is restricted to any case-" +"insensitive ASCII alphanumeric string (including underscores) that starts " +"with an underscore or ASCII letter. The first non-identifier character " +"after the ``$`` character terminates this placeholder specification." +msgstr "" + +#: ../Doc/library/string.rst:673 +msgid "" +"``${identifier}`` is equivalent to ``$identifier``. It is required when " +"valid identifier characters follow the placeholder but are not part of the " +"placeholder, such as ``\"${noun}ification\"``." +msgstr "" + +#: ../Doc/library/string.rst:677 +msgid "" +"Any other appearance of ``$`` in the string will result in a :exc:" +"`ValueError` being raised." +msgstr "" + +#: ../Doc/library/string.rst:680 +msgid "" +"The :mod:`string` module provides a :class:`Template` class that implements " +"these rules. The methods of :class:`Template` are:" +msgstr "" + +#: ../Doc/library/string.rst:686 +msgid "The constructor takes a single argument which is the template string." +msgstr "" + +#: ../Doc/library/string.rst:691 +msgid "" +"Performs the template substitution, returning a new string. *mapping* is " +"any dictionary-like object with keys that match the placeholders in the " +"template. Alternatively, you can provide keyword arguments, where the " +"keywords are the placeholders. When both *mapping* and *kwds* are given and " +"there are duplicates, the placeholders from *kwds* take precedence." +msgstr "" + +#: ../Doc/library/string.rst:700 +msgid "" +"Like :meth:`substitute`, except that if placeholders are missing from " +"*mapping* and *kwds*, instead of raising a :exc:`KeyError` exception, the " +"original placeholder will appear in the resulting string intact. Also, " +"unlike with :meth:`substitute`, any other appearances of the ``$`` will " +"simply return ``$`` instead of raising :exc:`ValueError`." +msgstr "" + +#: ../Doc/library/string.rst:706 +msgid "" +"While other exceptions may still occur, this method is called \"safe\" " +"because substitutions always tries to return a usable string instead of " +"raising an exception. In another sense, :meth:`safe_substitute` may be " +"anything other than safe, since it will silently ignore malformed templates " +"containing dangling delimiters, unmatched braces, or placeholders that are " +"not valid Python identifiers." +msgstr "" + +#: ../Doc/library/string.rst:713 +msgid ":class:`Template` instances also provide one public data attribute:" +msgstr "" + +#: ../Doc/library/string.rst:717 +msgid "" +"This is the object passed to the constructor's *template* argument. In " +"general, you shouldn't change it, but read-only access is not enforced." +msgstr "" + +#: ../Doc/library/string.rst:720 +msgid "Here is an example of how to use a Template::" +msgstr "" + +#: ../Doc/library/string.rst:738 +msgid "" +"Advanced usage: you can derive subclasses of :class:`Template` to customize " +"the placeholder syntax, delimiter character, or the entire regular " +"expression used to parse template strings. To do this, you can override " +"these class attributes:" +msgstr "" + +#: ../Doc/library/string.rst:742 +msgid "" +"*delimiter* -- This is the literal string describing a placeholder " +"introducing delimiter. The default value is ``$``. Note that this should " +"*not* be a regular expression, as the implementation will call :meth:`re." +"escape` on this string as needed." +msgstr "" + +#: ../Doc/library/string.rst:747 +msgid "" +"*idpattern* -- This is the regular expression describing the pattern for non-" +"braced placeholders (the braces will be added automatically as " +"appropriate). The default value is the regular expression ``[_a-z][_a-" +"z0-9]*``." +msgstr "" + +#: ../Doc/library/string.rst:752 +msgid "" +"*flags* -- The regular expression flags that will be applied when compiling " +"the regular expression used for recognizing substitutions. The default " +"value is ``re.IGNORECASE``. Note that ``re.VERBOSE`` will always be added " +"to the flags, so custom *idpattern*\\ s must follow conventions for verbose " +"regular expressions." +msgstr "" + +#: ../Doc/library/string.rst:760 +msgid "" +"Alternatively, you can provide the entire regular expression pattern by " +"overriding the class attribute *pattern*. If you do this, the value must be " +"a regular expression object with four named capturing groups. The capturing " +"groups correspond to the rules given above, along with the invalid " +"placeholder rule:" +msgstr "" + +#: ../Doc/library/string.rst:766 +msgid "" +"*escaped* -- This group matches the escape sequence, e.g. ``$$``, in the " +"default pattern." +msgstr "" + +#: ../Doc/library/string.rst:769 +msgid "" +"*named* -- This group matches the unbraced placeholder name; it should not " +"include the delimiter in capturing group." +msgstr "" + +#: ../Doc/library/string.rst:772 +msgid "" +"*braced* -- This group matches the brace enclosed placeholder name; it " +"should not include either the delimiter or braces in the capturing group." +msgstr "" + +#: ../Doc/library/string.rst:775 +msgid "" +"*invalid* -- This group matches any other delimiter pattern (usually a " +"single delimiter), and it should appear last in the regular expression." +msgstr "" + +#: ../Doc/library/string.rst:780 +msgid "Helper functions" +msgstr "" + +#: ../Doc/library/string.rst:784 +msgid "" +"Split the argument into words using :meth:`str.split`, capitalize each word " +"using :meth:`str.capitalize`, and join the capitalized words using :meth:" +"`str.join`. If the optional second argument *sep* is absent or ``None``, " +"runs of whitespace characters are replaced by a single space and leading and " +"trailing whitespace are removed, otherwise *sep* is used to split and join " +"the words." +msgstr "" + +#: ../Doc/library/stringprep.rst:2 +msgid ":mod:`stringprep` --- Internet String Preparation" +msgstr "" + +#: ../Doc/library/stringprep.rst:10 +msgid "**Source code:** :source:`Lib/stringprep.py`" +msgstr "" + +#: ../Doc/library/stringprep.rst:14 +msgid "" +"When identifying things (such as host names) in the internet, it is often " +"necessary to compare such identifications for \"equality\". Exactly how this " +"comparison is executed may depend on the application domain, e.g. whether it " +"should be case-insensitive or not. It may be also necessary to restrict the " +"possible identifications, to allow only identifications consisting of " +"\"printable\" characters." +msgstr "" + +#: ../Doc/library/stringprep.rst:21 +msgid "" +":rfc:`3454` defines a procedure for \"preparing\" Unicode strings in " +"internet protocols. Before passing strings onto the wire, they are processed " +"with the preparation procedure, after which they have a certain normalized " +"form. The RFC defines a set of tables, which can be combined into profiles. " +"Each profile must define which tables it uses, and what other optional parts " +"of the ``stringprep`` procedure are part of the profile. One example of a " +"``stringprep`` profile is ``nameprep``, which is used for internationalized " +"domain names." +msgstr "" + +#: ../Doc/library/stringprep.rst:29 +msgid "" +"The module :mod:`stringprep` only exposes the tables from RFC 3454. As these " +"tables would be very large to represent them as dictionaries or lists, the " +"module uses the Unicode character database internally. The module source " +"code itself was generated using the ``mkstringprep.py`` utility." +msgstr "" + +#: ../Doc/library/stringprep.rst:34 +msgid "" +"As a result, these tables are exposed as functions, not as data structures. " +"There are two kinds of tables in the RFC: sets and mappings. For a set, :mod:" +"`stringprep` provides the \"characteristic function\", i.e. a function that " +"returns true if the parameter is part of the set. For mappings, it provides " +"the mapping function: given the key, it returns the associated value. Below " +"is a list of all functions available in the module." +msgstr "" + +#: ../Doc/library/stringprep.rst:44 +msgid "" +"Determine whether *code* is in tableA.1 (Unassigned code points in Unicode " +"3.2)." +msgstr "" + +#: ../Doc/library/stringprep.rst:49 +msgid "Determine whether *code* is in tableB.1 (Commonly mapped to nothing)." +msgstr "" + +#: ../Doc/library/stringprep.rst:54 +msgid "" +"Return the mapped value for *code* according to tableB.2 (Mapping for case-" +"folding used with NFKC)." +msgstr "" + +#: ../Doc/library/stringprep.rst:60 +msgid "" +"Return the mapped value for *code* according to tableB.3 (Mapping for case-" +"folding used with no normalization)." +msgstr "" + +#: ../Doc/library/stringprep.rst:66 +msgid "Determine whether *code* is in tableC.1.1 (ASCII space characters)." +msgstr "" + +#: ../Doc/library/stringprep.rst:71 +msgid "" +"Determine whether *code* is in tableC.1.2 (Non-ASCII space characters)." +msgstr "" + +#: ../Doc/library/stringprep.rst:76 +msgid "" +"Determine whether *code* is in tableC.1 (Space characters, union of C.1.1 " +"and C.1.2)." +msgstr "" + +#: ../Doc/library/stringprep.rst:82 +msgid "Determine whether *code* is in tableC.2.1 (ASCII control characters)." +msgstr "" + +#: ../Doc/library/stringprep.rst:87 +msgid "" +"Determine whether *code* is in tableC.2.2 (Non-ASCII control characters)." +msgstr "" + +#: ../Doc/library/stringprep.rst:92 +msgid "" +"Determine whether *code* is in tableC.2 (Control characters, union of C.2.1 " +"and C.2.2)." +msgstr "" + +#: ../Doc/library/stringprep.rst:98 +msgid "Determine whether *code* is in tableC.3 (Private use)." +msgstr "" + +#: ../Doc/library/stringprep.rst:103 +msgid "Determine whether *code* is in tableC.4 (Non-character code points)." +msgstr "" + +#: ../Doc/library/stringprep.rst:108 +msgid "Determine whether *code* is in tableC.5 (Surrogate codes)." +msgstr "" + +#: ../Doc/library/stringprep.rst:113 +msgid "" +"Determine whether *code* is in tableC.6 (Inappropriate for plain text)." +msgstr "" + +#: ../Doc/library/stringprep.rst:118 +msgid "" +"Determine whether *code* is in tableC.7 (Inappropriate for canonical " +"representation)." +msgstr "" + +#: ../Doc/library/stringprep.rst:124 +msgid "" +"Determine whether *code* is in tableC.8 (Change display properties or are " +"deprecated)." +msgstr "" + +#: ../Doc/library/stringprep.rst:130 +msgid "Determine whether *code* is in tableC.9 (Tagging characters)." +msgstr "" + +#: ../Doc/library/stringprep.rst:135 +msgid "" +"Determine whether *code* is in tableD.1 (Characters with bidirectional " +"property \"R\" or \"AL\")." +msgstr "" + +#: ../Doc/library/stringprep.rst:141 +msgid "" +"Determine whether *code* is in tableD.2 (Characters with bidirectional " +"property \"L\")." +msgstr "" + +#: ../Doc/library/struct.rst:2 +msgid ":mod:`struct` --- Interpret bytes as packed binary data" +msgstr "" + +#: ../Doc/library/struct.rst:7 +msgid "**Source code:** :source:`Lib/struct.py`" +msgstr "" + +#: ../Doc/library/struct.rst:15 +msgid "" +"This module performs conversions between Python values and C structs " +"represented as Python :class:`bytes` objects. This can be used in handling " +"binary data stored in files or from network connections, among other " +"sources. It uses :ref:`struct-format-strings` as compact descriptions of " +"the layout of the C structs and the intended conversion to/from Python " +"values." +msgstr "" + +#: ../Doc/library/struct.rst:23 +msgid "" +"By default, the result of packing a given C struct includes pad bytes in " +"order to maintain proper alignment for the C types involved; similarly, " +"alignment is taken into account when unpacking. This behavior is chosen so " +"that the bytes of a packed struct correspond exactly to the layout in memory " +"of the corresponding C struct. To handle platform-independent data formats " +"or omit implicit pad bytes, use ``standard`` size and alignment instead of " +"``native`` size and alignment: see :ref:`struct-alignment` for details." +msgstr "" + +#: ../Doc/library/struct.rst:31 +msgid "" +"Several :mod:`struct` functions (and methods of :class:`Struct`) take a " +"*buffer* argument. This refers to objects that implement the :ref:" +"`bufferobjects` and provide either a readable or read-writable buffer. The " +"most common types used for that purpose are :class:`bytes` and :class:" +"`bytearray`, but many other types that can be viewed as an array of bytes " +"implement the buffer protocol, so that they can be read/filled without " +"additional copying from a :class:`bytes` object." +msgstr "" + +#: ../Doc/library/struct.rst:40 +msgid "Functions and Exceptions" +msgstr "" + +#: ../Doc/library/struct.rst:42 +msgid "The module defines the following exception and functions:" +msgstr "" + +#: ../Doc/library/struct.rst:47 +msgid "" +"Exception raised on various occasions; argument is a string describing what " +"is wrong." +msgstr "" + +#: ../Doc/library/struct.rst:53 +msgid "" +"Return a bytes object containing the values *v1*, *v2*, ... packed according " +"to the format string *fmt*. The arguments must match the values required by " +"the format exactly." +msgstr "" + +#: ../Doc/library/struct.rst:60 +msgid "" +"Pack the values *v1*, *v2*, ... according to the format string *fmt* and " +"write the packed bytes into the writable buffer *buffer* starting at " +"position *offset*. Note that *offset* is a required argument." +msgstr "" + +#: ../Doc/library/struct.rst:67 +msgid "" +"Unpack from the buffer *buffer* (presumably packed by ``pack(fmt, ...)``) " +"according to the format string *fmt*. The result is a tuple even if it " +"contains exactly one item. The buffer's size in bytes must match the size " +"required by the format, as reflected by :func:`calcsize`." +msgstr "" + +#: ../Doc/library/struct.rst:75 +msgid "" +"Unpack from *buffer* starting at position *offset*, according to the format " +"string *fmt*. The result is a tuple even if it contains exactly one item. " +"The buffer's size in bytes, minus *offset*, must be at least the size " +"required by the format, as reflected by :func:`calcsize`." +msgstr "" + +#: ../Doc/library/struct.rst:83 +msgid "" +"Iteratively unpack from the buffer *buffer* according to the format string " +"*fmt*. This function returns an iterator which will read equally-sized " +"chunks from the buffer until all its contents have been consumed. The " +"buffer's size in bytes must be a multiple of the size required by the " +"format, as reflected by :func:`calcsize`." +msgstr "" + +#: ../Doc/library/struct.rst:89 +msgid "Each iteration yields a tuple as specified by the format string." +msgstr "" + +#: ../Doc/library/struct.rst:96 +msgid "" +"Return the size of the struct (and hence of the bytes object produced by " +"``pack(fmt, ...)``) corresponding to the format string *fmt*." +msgstr "" + +#: ../Doc/library/struct.rst:102 +msgid "Format Strings" +msgstr "" + +#: ../Doc/library/struct.rst:104 +msgid "" +"Format strings are the mechanism used to specify the expected layout when " +"packing and unpacking data. They are built up from :ref:`format-" +"characters`, which specify the type of data being packed/unpacked. In " +"addition, there are special characters for controlling the :ref:`struct-" +"alignment`." +msgstr "" + +#: ../Doc/library/struct.rst:113 +msgid "Byte Order, Size, and Alignment" +msgstr "" + +#: ../Doc/library/struct.rst:115 +msgid "" +"By default, C types are represented in the machine's native format and byte " +"order, and properly aligned by skipping pad bytes if necessary (according to " +"the rules used by the C compiler)." +msgstr "" + +#: ../Doc/library/struct.rst:119 +msgid "" +"Alternatively, the first character of the format string can be used to " +"indicate the byte order, size and alignment of the packed data, according to " +"the following table:" +msgstr "" + +#: ../Doc/library/struct.rst:124 +msgid "Byte order" +msgstr "" + +#: ../Doc/library/struct.rst:124 +msgid "Size" +msgstr "" + +#: ../Doc/library/struct.rst:124 +msgid "Alignment" +msgstr "" + +#: ../Doc/library/struct.rst:126 +msgid "``@``" +msgstr "" + +#: ../Doc/library/struct.rst:126 ../Doc/library/struct.rst:128 +msgid "native" +msgstr "" + +#: ../Doc/library/struct.rst:128 +msgid "``=``" +msgstr "" + +#: ../Doc/library/struct.rst:128 ../Doc/library/struct.rst:130 +#: ../Doc/library/struct.rst:132 ../Doc/library/struct.rst:134 +msgid "standard" +msgstr "" + +#: ../Doc/library/struct.rst:128 ../Doc/library/struct.rst:130 +#: ../Doc/library/struct.rst:132 ../Doc/library/struct.rst:134 +msgid "none" +msgstr "" + +#: ../Doc/library/struct.rst:130 +msgid "little-endian" +msgstr "" + +#: ../Doc/library/struct.rst:132 +msgid "big-endian" +msgstr "" + +#: ../Doc/library/struct.rst:134 +msgid "``!``" +msgstr "" + +#: ../Doc/library/struct.rst:134 +msgid "network (= big-endian)" +msgstr "" + +#: ../Doc/library/struct.rst:137 +msgid "If the first character is not one of these, ``'@'`` is assumed." +msgstr "" + +#: ../Doc/library/struct.rst:139 +msgid "" +"Native byte order is big-endian or little-endian, depending on the host " +"system. For example, Intel x86 and AMD64 (x86-64) are little-endian; " +"Motorola 68000 and PowerPC G5 are big-endian; ARM and Intel Itanium feature " +"switchable endianness (bi-endian). Use ``sys.byteorder`` to check the " +"endianness of your system." +msgstr "" + +#: ../Doc/library/struct.rst:145 +msgid "" +"Native size and alignment are determined using the C compiler's ``sizeof`` " +"expression. This is always combined with native byte order." +msgstr "" + +#: ../Doc/library/struct.rst:148 +msgid "" +"Standard size depends only on the format character; see the table in the :" +"ref:`format-characters` section." +msgstr "" + +#: ../Doc/library/struct.rst:151 +msgid "" +"Note the difference between ``'@'`` and ``'='``: both use native byte order, " +"but the size and alignment of the latter is standardized." +msgstr "" + +#: ../Doc/library/struct.rst:154 +msgid "" +"The form ``'!'`` is available for those poor souls who claim they can't " +"remember whether network byte order is big-endian or little-endian." +msgstr "" + +#: ../Doc/library/struct.rst:157 +msgid "" +"There is no way to indicate non-native byte order (force byte-swapping); use " +"the appropriate choice of ``'<'`` or ``'>'``." +msgstr "" + +#: ../Doc/library/struct.rst:162 +msgid "" +"Padding is only automatically added between successive structure members. No " +"padding is added at the beginning or the end of the encoded struct." +msgstr "" + +#: ../Doc/library/struct.rst:165 +msgid "" +"No padding is added when using non-native size and alignment, e.g. with '<', " +"'>', '=', and '!'." +msgstr "" + +#: ../Doc/library/struct.rst:168 +msgid "" +"To align the end of a structure to the alignment requirement of a particular " +"type, end the format with the code for that type with a repeat count of " +"zero. See :ref:`struct-examples`." +msgstr "" + +#: ../Doc/library/struct.rst:176 +msgid "Format Characters" +msgstr "" + +#: ../Doc/library/struct.rst:178 +msgid "" +"Format characters have the following meaning; the conversion between C and " +"Python values should be obvious given their types. The 'Standard size' " +"column refers to the size of the packed value in bytes when using standard " +"size; that is, when the format string starts with one of ``'<'``, ``'>'``, " +"``'!'`` or ``'='``. When using native size, the size of the packed value is " +"platform-dependent." +msgstr "" + +#: ../Doc/library/struct.rst:186 +msgid "Standard size" +msgstr "" + +#: ../Doc/library/struct.rst:188 +msgid "``x``" +msgstr "" + +#: ../Doc/library/struct.rst:188 +msgid "pad byte" +msgstr "" + +#: ../Doc/library/struct.rst:188 +msgid "no value" +msgstr "" + +#: ../Doc/library/struct.rst:190 +msgid "``c``" +msgstr "" + +#: ../Doc/library/struct.rst:190 +msgid "bytes of length 1" +msgstr "" + +#: ../Doc/library/struct.rst:192 +msgid "``b``" +msgstr "" + +#: ../Doc/library/struct.rst:192 +msgid ":c:type:`signed char`" +msgstr "" + +#: ../Doc/library/struct.rst:192 ../Doc/library/struct.rst:194 +#: ../Doc/library/struct.rst:198 ../Doc/library/struct.rst:200 +#: ../Doc/library/struct.rst:202 ../Doc/library/struct.rst:204 +#: ../Doc/library/struct.rst:206 ../Doc/library/struct.rst:208 +#: ../Doc/library/struct.rst:210 ../Doc/library/struct.rst:212 +#: ../Doc/library/struct.rst:215 ../Doc/library/struct.rst:217 +#: ../Doc/library/struct.rst:229 +msgid "integer" +msgstr "" + +#: ../Doc/library/struct.rst:192 +msgid "\\(1),\\(3)" +msgstr "" + +#: ../Doc/library/struct.rst:194 +msgid "``B``" +msgstr "" + +#: ../Doc/library/struct.rst:196 +msgid "bool" +msgstr "" + +#: ../Doc/library/struct.rst:198 +msgid "``h``" +msgstr "" + +#: ../Doc/library/struct.rst:200 +msgid "``H``" +msgstr "" + +#: ../Doc/library/struct.rst:202 +msgid "``i``" +msgstr "" + +#: ../Doc/library/struct.rst:204 +msgid "``I``" +msgstr "" + +#: ../Doc/library/struct.rst:206 +msgid "``l``" +msgstr "" + +#: ../Doc/library/struct.rst:208 +msgid "``L``" +msgstr "" + +#: ../Doc/library/struct.rst:210 +msgid "``q``" +msgstr "" + +#: ../Doc/library/struct.rst:210 +msgid ":c:type:`long long`" +msgstr "" + +#: ../Doc/library/struct.rst:210 ../Doc/library/struct.rst:212 +msgid "\\(2), \\(3)" +msgstr "" + +#: ../Doc/library/struct.rst:212 +msgid "``Q``" +msgstr "" + +#: ../Doc/library/struct.rst:212 +msgid ":c:type:`unsigned long long`" +msgstr "" + +#: ../Doc/library/struct.rst:215 +msgid "``n``" +msgstr "" + +#: ../Doc/library/struct.rst:215 +msgid ":c:type:`ssize_t`" +msgstr "" + +#: ../Doc/library/struct.rst:217 +msgid "``N``" +msgstr "" + +#: ../Doc/library/struct.rst:219 +msgid "``e``" +msgstr "" + +#: ../Doc/library/struct.rst:221 +msgid "``f``" +msgstr "" + +#: ../Doc/library/struct.rst:223 +msgid "``d``" +msgstr "" + +#: ../Doc/library/struct.rst:225 +msgid "``s``" +msgstr "" + +#: ../Doc/library/struct.rst:225 ../Doc/library/struct.rst:227 +msgid ":c:type:`char[]`" +msgstr "" + +#: ../Doc/library/struct.rst:225 ../Doc/library/struct.rst:227 +msgid "bytes" +msgstr "" + +#: ../Doc/library/struct.rst:227 +msgid "``p``" +msgstr "" + +#: ../Doc/library/struct.rst:229 +msgid "``P``" +msgstr "" + +#: ../Doc/library/struct.rst:229 +msgid ":c:type:`void \\*`" +msgstr "" + +#: ../Doc/library/struct.rst:232 +msgid "Added support for the ``'n'`` and ``'N'`` formats." +msgstr "" + +#: ../Doc/library/struct.rst:238 +msgid "" +"The ``'?'`` conversion code corresponds to the :c:type:`_Bool` type defined " +"by C99. If this type is not available, it is simulated using a :c:type:" +"`char`. In standard mode, it is always represented by one byte." +msgstr "" + +#: ../Doc/library/struct.rst:243 +msgid "" +"The ``'q'`` and ``'Q'`` conversion codes are available in native mode only " +"if the platform C compiler supports C :c:type:`long long`, or, on Windows, :" +"c:type:`__int64`. They are always available in standard modes." +msgstr "" + +#: ../Doc/library/struct.rst:248 +msgid "" +"When attempting to pack a non-integer using any of the integer conversion " +"codes, if the non-integer has a :meth:`__index__` method then that method is " +"called to convert the argument to an integer before packing." +msgstr "" + +#: ../Doc/library/struct.rst:252 +msgid "Use of the :meth:`__index__` method for non-integers is new in 3.2." +msgstr "" + +#: ../Doc/library/struct.rst:256 +msgid "" +"The ``'n'`` and ``'N'`` conversion codes are only available for the native " +"size (selected as the default or with the ``'@'`` byte order character). For " +"the standard size, you can use whichever of the other integer formats fits " +"your application." +msgstr "" + +#: ../Doc/library/struct.rst:262 +msgid "" +"For the ``'f'``, ``'d'`` and ``'e'`` conversion codes, the packed " +"representation uses the IEEE 754 binary32, binary64 or binary16 format (for " +"``'f'``, ``'d'`` or ``'e'`` respectively), regardless of the floating-point " +"format used by the platform." +msgstr "" + +#: ../Doc/library/struct.rst:268 +msgid "" +"The ``'P'`` format character is only available for the native byte ordering " +"(selected as the default or with the ``'@'`` byte order character). The byte " +"order character ``'='`` chooses to use little- or big-endian ordering based " +"on the host system. The struct module does not interpret this as native " +"ordering, so the ``'P'`` format is not available." +msgstr "" + +#: ../Doc/library/struct.rst:275 +msgid "" +"The IEEE 754 binary16 \"half precision\" type was introduced in the 2008 " +"revision of the `IEEE 754 standard `_. It has a sign " +"bit, a 5-bit exponent and 11-bit precision (with 10 bits explicitly stored), " +"and can represent numbers between approximately ``6.1e-05`` and ``6.5e+04`` " +"at full precision. This type is not widely supported by C compilers: on a " +"typical machine, an unsigned short can be used for storage, but not for math " +"operations. See the Wikipedia page on the `half-precision floating-point " +"format `_ for more information." +msgstr "" + +#: ../Doc/library/struct.rst:285 +msgid "" +"A format character may be preceded by an integral repeat count. For " +"example, the format string ``'4h'`` means exactly the same as ``'hhhh'``." +msgstr "" + +#: ../Doc/library/struct.rst:288 +msgid "" +"Whitespace characters between formats are ignored; a count and its format " +"must not contain whitespace though." +msgstr "" + +#: ../Doc/library/struct.rst:291 +msgid "" +"For the ``'s'`` format character, the count is interpreted as the length of " +"the bytes, not a repeat count like for the other format characters; for " +"example, ``'10s'`` means a single 10-byte string, while ``'10c'`` means 10 " +"characters. If a count is not given, it defaults to 1. For packing, the " +"string is truncated or padded with null bytes as appropriate to make it fit. " +"For unpacking, the resulting bytes object always has exactly the specified " +"number of bytes. As a special case, ``'0s'`` means a single, empty string " +"(while ``'0c'`` means 0 characters)." +msgstr "" + +#: ../Doc/library/struct.rst:300 +msgid "" +"When packing a value ``x`` using one of the integer formats (``'b'``, " +"``'B'``, ``'h'``, ``'H'``, ``'i'``, ``'I'``, ``'l'``, ``'L'``, ``'q'``, " +"``'Q'``), if ``x`` is outside the valid range for that format then :exc:" +"`struct.error` is raised." +msgstr "" + +#: ../Doc/library/struct.rst:305 +msgid "" +"In 3.0, some of the integer formats wrapped out-of-range values and raised :" +"exc:`DeprecationWarning` instead of :exc:`struct.error`." +msgstr "" + +#: ../Doc/library/struct.rst:309 +msgid "" +"The ``'p'`` format character encodes a \"Pascal string\", meaning a short " +"variable-length string stored in a *fixed number of bytes*, given by the " +"count. The first byte stored is the length of the string, or 255, whichever " +"is smaller. The bytes of the string follow. If the string passed in to :" +"func:`pack` is too long (longer than the count minus 1), only the leading " +"``count-1`` bytes of the string are stored. If the string is shorter than " +"``count-1``, it is padded with null bytes so that exactly count bytes in all " +"are used. Note that for :func:`unpack`, the ``'p'`` format character " +"consumes ``count`` bytes, but that the string returned can never contain " +"more than 255 bytes." +msgstr "" + +#: ../Doc/library/struct.rst:320 +msgid "" +"For the ``'?'`` format character, the return value is either :const:`True` " +"or :const:`False`. When packing, the truth value of the argument object is " +"used. Either 0 or 1 in the native or standard bool representation will be " +"packed, and any non-zero value will be ``True`` when unpacking." +msgstr "" + +#: ../Doc/library/struct.rst:333 +msgid "" +"All examples assume a native byte order, size, and alignment with a big-" +"endian machine." +msgstr "" + +#: ../Doc/library/struct.rst:336 +msgid "A basic example of packing/unpacking three integers::" +msgstr "" + +#: ../Doc/library/struct.rst:346 +msgid "" +"Unpacked fields can be named by assigning them to variables or by wrapping " +"the result in a named tuple::" +msgstr "" + +#: ../Doc/library/struct.rst:357 +msgid "" +"The ordering of format characters may have an impact on size since the " +"padding needed to satisfy alignment requirements is different::" +msgstr "" + +#: ../Doc/library/struct.rst:369 +msgid "" +"The following format ``'llh0l'`` specifies two pad bytes at the end, " +"assuming longs are aligned on 4-byte boundaries::" +msgstr "" + +#: ../Doc/library/struct.rst:375 +msgid "" +"This only works when native size and alignment are in effect; standard size " +"and alignment does not enforce any alignment." +msgstr "" + +#: ../Doc/library/struct.rst:382 +msgid "Module :mod:`array`" +msgstr "" + +#: ../Doc/library/struct.rst:382 +msgid "Packed binary storage of homogeneous data." +msgstr "" + +#: ../Doc/library/struct.rst:385 +msgid "Packing and unpacking of XDR data." +msgstr "" + +#: ../Doc/library/struct.rst:393 +msgid "The :mod:`struct` module also defines the following type:" +msgstr "" + +#: ../Doc/library/struct.rst:398 +msgid "" +"Return a new Struct object which writes and reads binary data according to " +"the format string *format*. Creating a Struct object once and calling its " +"methods is more efficient than calling the :mod:`struct` functions with the " +"same format since the format string only needs to be compiled once." +msgstr "" + +#: ../Doc/library/struct.rst:404 +msgid "Compiled Struct objects support the following methods and attributes:" +msgstr "" + +#: ../Doc/library/struct.rst:408 +msgid "" +"Identical to the :func:`pack` function, using the compiled format. " +"(``len(result)`` will equal :attr:`size`.)" +msgstr "" + +#: ../Doc/library/struct.rst:414 +msgid "Identical to the :func:`pack_into` function, using the compiled format." +msgstr "" + +#: ../Doc/library/struct.rst:419 +msgid "" +"Identical to the :func:`unpack` function, using the compiled format. The " +"buffer's size in bytes must equal :attr:`size`." +msgstr "" + +#: ../Doc/library/struct.rst:425 +msgid "" +"Identical to the :func:`unpack_from` function, using the compiled format. " +"The buffer's size in bytes, minus *offset*, must be at least :attr:`size`." +msgstr "" + +#: ../Doc/library/struct.rst:432 +msgid "" +"Identical to the :func:`iter_unpack` function, using the compiled format. " +"The buffer's size in bytes must be a multiple of :attr:`size`." +msgstr "" + +#: ../Doc/library/struct.rst:439 +msgid "The format string used to construct this Struct object." +msgstr "" + +#: ../Doc/library/struct.rst:443 +msgid "" +"The calculated size of the struct (and hence of the bytes object produced by " +"the :meth:`pack` method) corresponding to :attr:`format`." +msgstr "" + +#: ../Doc/library/subprocess.rst:2 +msgid ":mod:`subprocess` --- Subprocess management" +msgstr "" + +#: ../Doc/library/subprocess.rst:10 +msgid "**Source code:** :source:`Lib/subprocess.py`" +msgstr "" + +#: ../Doc/library/subprocess.rst:14 +msgid "" +"The :mod:`subprocess` module allows you to spawn new processes, connect to " +"their input/output/error pipes, and obtain their return codes. This module " +"intends to replace several older modules and functions::" +msgstr "" + +#: ../Doc/library/subprocess.rst:21 +msgid "" +"Information about how the :mod:`subprocess` module can be used to replace " +"these modules and functions can be found in the following sections." +msgstr "" + +#: ../Doc/library/subprocess.rst:26 +msgid ":pep:`324` -- PEP proposing the subprocess module" +msgstr "" + +#: ../Doc/library/subprocess.rst:30 +msgid "Using the :mod:`subprocess` Module" +msgstr "" + +#: ../Doc/library/subprocess.rst:32 +msgid "" +"The recommended approach to invoking subprocesses is to use the :func:`run` " +"function for all use cases it can handle. For more advanced use cases, the " +"underlying :class:`Popen` interface can be used directly." +msgstr "" + +#: ../Doc/library/subprocess.rst:36 +msgid "" +"The :func:`run` function was added in Python 3.5; if you need to retain " +"compatibility with older versions, see the :ref:`call-function-trio` section." +msgstr "" + +#: ../Doc/library/subprocess.rst:44 +msgid "" +"Run the command described by *args*. Wait for command to complete, then " +"return a :class:`CompletedProcess` instance." +msgstr "" + +#: ../Doc/library/subprocess.rst:47 +msgid "" +"The arguments shown above are merely the most common ones, described below " +"in :ref:`frequently-used-arguments` (hence the use of keyword-only notation " +"in the abbreviated signature). The full function signature is largely the " +"same as that of the :class:`Popen` constructor - apart from *timeout*, " +"*input* and *check*, all the arguments to this function are passed through " +"to that interface." +msgstr "" + +#: ../Doc/library/subprocess.rst:54 +msgid "" +"This does not capture stdout or stderr by default. To do so, pass :data:" +"`PIPE` for the *stdout* and/or *stderr* arguments." +msgstr "" + +#: ../Doc/library/subprocess.rst:57 +msgid "" +"The *timeout* argument is passed to :meth:`Popen.communicate`. If the " +"timeout expires, the child process will be killed and waited for. The :exc:" +"`TimeoutExpired` exception will be re-raised after the child process has " +"terminated." +msgstr "" + +#: ../Doc/library/subprocess.rst:62 +msgid "" +"The *input* argument is passed to :meth:`Popen.communicate` and thus to the " +"subprocess's stdin. If used it must be a byte sequence, or a string if " +"*encoding* or *errors* is specified or *universal_newlines* is True. When " +"used, the internal :class:`Popen` object is automatically created with " +"``stdin=PIPE``, and the *stdin* argument may not be used as well." +msgstr "" + +#: ../Doc/library/subprocess.rst:68 +msgid "" +"If *check* is True, and the process exits with a non-zero exit code, a :exc:" +"`CalledProcessError` exception will be raised. Attributes of that exception " +"hold the arguments, the exit code, and stdout and stderr if they were " +"captured." +msgstr "" + +#: ../Doc/library/subprocess.rst:73 +msgid "" +"If *encoding* or *errors* are specified, or *universal_newlines* is True, " +"file objects for stdin, stdout and stderr are opened in text mode using the " +"specified *encoding* and *errors* or the :class:`io.TextIOWrapper` default. " +"Otherwise, file objects are opened in binary mode." +msgstr "" + +#: ../Doc/library/subprocess.rst:96 +msgid "Added *encoding* and *errors* parameters" +msgstr "" + +#: ../Doc/library/subprocess.rst:100 +msgid "" +"The return value from :func:`run`, representing a process that has finished." +msgstr "" + +#: ../Doc/library/subprocess.rst:104 +msgid "" +"The arguments used to launch the process. This may be a list or a string." +msgstr "" + +#: ../Doc/library/subprocess.rst:108 +msgid "" +"Exit status of the child process. Typically, an exit status of 0 indicates " +"that it ran successfully." +msgstr "" + +#: ../Doc/library/subprocess.rst:111 ../Doc/library/subprocess.rst:741 +msgid "" +"A negative value ``-N`` indicates that the child was terminated by signal " +"``N`` (POSIX only)." +msgstr "" + +#: ../Doc/library/subprocess.rst:116 +msgid "" +"Captured stdout from the child process. A bytes sequence, or a string if :" +"func:`run` was called with an encoding or errors. None if stdout was not " +"captured." +msgstr "" + +#: ../Doc/library/subprocess.rst:120 +msgid "" +"If you ran the process with ``stderr=subprocess.STDOUT``, stdout and stderr " +"will be combined in this attribute, and :attr:`stderr` will be None." +msgstr "" + +#: ../Doc/library/subprocess.rst:126 +msgid "" +"Captured stderr from the child process. A bytes sequence, or a string if :" +"func:`run` was called with an encoding or errors. None if stderr was not " +"captured." +msgstr "" + +#: ../Doc/library/subprocess.rst:132 +msgid "If :attr:`returncode` is non-zero, raise a :exc:`CalledProcessError`." +msgstr "" + +#: ../Doc/library/subprocess.rst:138 +msgid "" +"Special value that can be used as the *stdin*, *stdout* or *stderr* argument " +"to :class:`Popen` and indicates that the special file :data:`os.devnull` " +"will be used." +msgstr "" + +#: ../Doc/library/subprocess.rst:147 +msgid "" +"Special value that can be used as the *stdin*, *stdout* or *stderr* argument " +"to :class:`Popen` and indicates that a pipe to the standard stream should be " +"opened. Most useful with :meth:`Popen.communicate`." +msgstr "" + +#: ../Doc/library/subprocess.rst:154 +msgid "" +"Special value that can be used as the *stderr* argument to :class:`Popen` " +"and indicates that standard error should go into the same handle as standard " +"output." +msgstr "" + +#: ../Doc/library/subprocess.rst:161 +msgid "Base class for all other exceptions from this module." +msgstr "" + +#: ../Doc/library/subprocess.rst:168 +msgid "" +"Subclass of :exc:`SubprocessError`, raised when a timeout expires while " +"waiting for a child process." +msgstr "" + +#: ../Doc/library/subprocess.rst:173 ../Doc/library/subprocess.rst:210 +msgid "Command that was used to spawn the child process." +msgstr "" + +#: ../Doc/library/subprocess.rst:177 +msgid "Timeout in seconds." +msgstr "" + +#: ../Doc/library/subprocess.rst:181 ../Doc/library/subprocess.rst:214 +msgid "" +"Output of the child process if it was captured by :func:`run` or :func:" +"`check_output`. Otherwise, ``None``." +msgstr "" + +#: ../Doc/library/subprocess.rst:186 ../Doc/library/subprocess.rst:219 +msgid "Alias for output, for symmetry with :attr:`stderr`." +msgstr "" + +#: ../Doc/library/subprocess.rst:190 ../Doc/library/subprocess.rst:223 +msgid "" +"Stderr output of the child process if it was captured by :func:`run`. " +"Otherwise, ``None``." +msgstr "" + +#: ../Doc/library/subprocess.rst:195 ../Doc/library/subprocess.rst:226 +msgid "*stdout* and *stderr* attributes added" +msgstr "" + +#: ../Doc/library/subprocess.rst:200 +msgid "" +"Subclass of :exc:`SubprocessError`, raised when a process run by :func:" +"`check_call` or :func:`check_output` returns a non-zero exit status." +msgstr "" + +#: ../Doc/library/subprocess.rst:205 +msgid "" +"Exit status of the child process. If the process exited due to a signal, " +"this will be the negative signal number." +msgstr "" + +#: ../Doc/library/subprocess.rst:233 +msgid "Frequently Used Arguments" +msgstr "" + +#: ../Doc/library/subprocess.rst:235 +msgid "" +"To support a wide variety of use cases, the :class:`Popen` constructor (and " +"the convenience functions) accept a large number of optional arguments. For " +"most typical use cases, many of these arguments can be safely left at their " +"default values. The arguments that are most commonly needed are:" +msgstr "" + +#: ../Doc/library/subprocess.rst:240 +msgid "" +"*args* is required for all calls and should be a string, or a sequence of " +"program arguments. Providing a sequence of arguments is generally preferred, " +"as it allows the module to take care of any required escaping and quoting of " +"arguments (e.g. to permit spaces in file names). If passing a single string, " +"either *shell* must be :const:`True` (see below) or else the string must " +"simply name the program to be executed without specifying any arguments." +msgstr "" + +#: ../Doc/library/subprocess.rst:248 +msgid "" +"*stdin*, *stdout* and *stderr* specify the executed program's standard " +"input, standard output and standard error file handles, respectively. Valid " +"values are :data:`PIPE`, :data:`DEVNULL`, an existing file descriptor (a " +"positive integer), an existing file object, and ``None``. :data:`PIPE` " +"indicates that a new pipe to the child should be created. :data:`DEVNULL` " +"indicates that the special file :data:`os.devnull` will be used. With the " +"default settings of ``None``, no redirection will occur; the child's file " +"handles will be inherited from the parent. Additionally, *stderr* can be :" +"data:`STDOUT`, which indicates that the stderr data from the child process " +"should be captured into the same file handle as for *stdout*." +msgstr "" + +#: ../Doc/library/subprocess.rst:262 +msgid "" +"If *encoding* or *errors* are specified, or *universal_newlines* is True, " +"the file objects *stdin*, *stdout* and *stderr* will be opened in text mode " +"using the *encoding* and *errors* specified in the call or the defaults for :" +"class:`io.TextIOWrapper`." +msgstr "" + +#: ../Doc/library/subprocess.rst:267 +msgid "" +"For *stdin*, line ending characters ``'\\n'`` in the input will be converted " +"to the default line separator :data:`os.linesep`. For *stdout* and *stderr*, " +"all line endings in the output will be converted to ``'\\n'``. For more " +"information see the documentation of the :class:`io.TextIOWrapper` class " +"when the *newline* argument to its constructor is ``None``." +msgstr "" + +#: ../Doc/library/subprocess.rst:273 +msgid "" +"If text mode is not used, *stdin*, *stdout* and *stderr* will be opened as " +"binary streams. No encoding or line ending conversion is performed." +msgstr "" + +#: ../Doc/library/subprocess.rst:276 +msgid "Added *encoding* and *errors* parameters." +msgstr "" + +#: ../Doc/library/subprocess.rst:281 +msgid "" +"The newlines attribute of the file objects :attr:`Popen.stdin`, :attr:`Popen." +"stdout` and :attr:`Popen.stderr` are not updated by the :meth:`Popen." +"communicate` method." +msgstr "" + +#: ../Doc/library/subprocess.rst:285 +msgid "" +"If *shell* is ``True``, the specified command will be executed through the " +"shell. This can be useful if you are using Python primarily for the " +"enhanced control flow it offers over most system shells and still want " +"convenient access to other shell features such as shell pipes, filename " +"wildcards, environment variable expansion, and expansion of ``~`` to a " +"user's home directory. However, note that Python itself offers " +"implementations of many shell-like features (in particular, :mod:`glob`, :" +"mod:`fnmatch`, :func:`os.walk`, :func:`os.path.expandvars`, :func:`os.path." +"expanduser`, and :mod:`shutil`)." +msgstr "" + +#: ../Doc/library/subprocess.rst:295 +msgid "" +"When *universal_newlines* is ``True``, the class uses the encoding :func:" +"`locale.getpreferredencoding(False) ` instead " +"of ``locale.getpreferredencoding()``. See the :class:`io.TextIOWrapper` " +"class for more information on this change." +msgstr "" + +#: ../Doc/library/subprocess.rst:303 ../Doc/library/subprocess.rst:387 +msgid "" +"Read the `Security Considerations`_ section before using ``shell=True``." +msgstr "" + +#: ../Doc/library/subprocess.rst:305 +msgid "" +"These options, along with all of the other options, are described in more " +"detail in the :class:`Popen` constructor documentation." +msgstr "" + +#: ../Doc/library/subprocess.rst:310 +msgid "Popen Constructor" +msgstr "" + +#: ../Doc/library/subprocess.rst:312 +msgid "" +"The underlying process creation and management in this module is handled by " +"the :class:`Popen` class. It offers a lot of flexibility so that developers " +"are able to handle the less common cases not covered by the convenience " +"functions." +msgstr "" + +#: ../Doc/library/subprocess.rst:325 +msgid "" +"Execute a child program in a new process. On POSIX, the class uses :meth:" +"`os.execvp`-like behavior to execute the child program. On Windows, the " +"class uses the Windows ``CreateProcess()`` function. The arguments to :" +"class:`Popen` are as follows." +msgstr "" + +#: ../Doc/library/subprocess.rst:330 +msgid "" +"*args* should be a sequence of program arguments or else a single string. By " +"default, the program to execute is the first item in *args* if *args* is a " +"sequence. If *args* is a string, the interpretation is platform-dependent " +"and described below. See the *shell* and *executable* arguments for " +"additional differences from the default behavior. Unless otherwise stated, " +"it is recommended to pass *args* as a sequence." +msgstr "" + +#: ../Doc/library/subprocess.rst:337 +msgid "" +"On POSIX, if *args* is a string, the string is interpreted as the name or " +"path of the program to execute. However, this can only be done if not " +"passing arguments to the program." +msgstr "" + +#: ../Doc/library/subprocess.rst:343 +msgid "" +":meth:`shlex.split` can be useful when determining the correct tokenization " +"for *args*, especially in complex cases::" +msgstr "" + +#: ../Doc/library/subprocess.rst:354 +msgid "" +"Note in particular that options (such as *-input*) and arguments (such as " +"*eggs.txt*) that are separated by whitespace in the shell go in separate " +"list elements, while arguments that need quoting or backslash escaping when " +"used in the shell (such as filenames containing spaces or the *echo* command " +"shown above) are single list elements." +msgstr "" + +#: ../Doc/library/subprocess.rst:360 +msgid "" +"On Windows, if *args* is a sequence, it will be converted to a string in a " +"manner described in :ref:`converting-argument-sequence`. This is because " +"the underlying ``CreateProcess()`` operates on strings." +msgstr "" + +#: ../Doc/library/subprocess.rst:364 +msgid "" +"The *shell* argument (which defaults to *False*) specifies whether to use " +"the shell as the program to execute. If *shell* is *True*, it is " +"recommended to pass *args* as a string rather than as a sequence." +msgstr "" + +#: ../Doc/library/subprocess.rst:368 +msgid "" +"On POSIX with ``shell=True``, the shell defaults to :file:`/bin/sh`. If " +"*args* is a string, the string specifies the command to execute through the " +"shell. This means that the string must be formatted exactly as it would be " +"when typed at the shell prompt. This includes, for example, quoting or " +"backslash escaping filenames with spaces in them. If *args* is a sequence, " +"the first item specifies the command string, and any additional items will " +"be treated as additional arguments to the shell itself. That is to say, :" +"class:`Popen` does the equivalent of::" +msgstr "" + +#: ../Doc/library/subprocess.rst:379 +msgid "" +"On Windows with ``shell=True``, the :envvar:`COMSPEC` environment variable " +"specifies the default shell. The only time you need to specify " +"``shell=True`` on Windows is when the command you wish to execute is built " +"into the shell (e.g. :command:`dir` or :command:`copy`). You do not need " +"``shell=True`` to run a batch file or console-based executable." +msgstr "" + +#: ../Doc/library/subprocess.rst:389 +msgid "" +"*bufsize* will be supplied as the corresponding argument to the :func:`open` " +"function when creating the stdin/stdout/stderr pipe file objects:" +msgstr "" + +#: ../Doc/library/subprocess.rst:393 +msgid "" +":const:`0` means unbuffered (read and write are one system call and can " +"return short)" +msgstr "" + +#: ../Doc/library/subprocess.rst:395 +msgid "" +":const:`1` means line buffered (only usable if ``universal_newlines=True`` i." +"e., in a text mode)" +msgstr "" + +#: ../Doc/library/subprocess.rst:397 +msgid "any other positive value means use a buffer of approximately that size" +msgstr "" + +#: ../Doc/library/subprocess.rst:399 +msgid "" +"negative bufsize (the default) means the system default of io." +"DEFAULT_BUFFER_SIZE will be used." +msgstr "" + +#: ../Doc/library/subprocess.rst:402 +msgid "" +"*bufsize* now defaults to -1 to enable buffering by default to match the " +"behavior that most code expects. In versions prior to Python 3.2.4 and " +"3.3.1 it incorrectly defaulted to :const:`0` which was unbuffered and " +"allowed short reads. This was unintentional and did not match the behavior " +"of Python 2 as most code expected." +msgstr "" + +#: ../Doc/library/subprocess.rst:409 +msgid "" +"The *executable* argument specifies a replacement program to execute. It " +"is very seldom needed. When ``shell=False``, *executable* replaces the " +"program to execute specified by *args*. However, the original *args* is " +"still passed to the program. Most programs treat the program specified by " +"*args* as the command name, which can then be different from the program " +"actually executed. On POSIX, the *args* name becomes the display name for " +"the executable in utilities such as :program:`ps`. If ``shell=True``, on " +"POSIX the *executable* argument specifies a replacement shell for the " +"default :file:`/bin/sh`." +msgstr "" + +#: ../Doc/library/subprocess.rst:419 +msgid "" +"*stdin*, *stdout* and *stderr* specify the executed program's standard " +"input, standard output and standard error file handles, respectively. Valid " +"values are :data:`PIPE`, :data:`DEVNULL`, an existing file descriptor (a " +"positive integer), an existing :term:`file object`, and ``None``. :data:" +"`PIPE` indicates that a new pipe to the child should be created. :data:" +"`DEVNULL` indicates that the special file :data:`os.devnull` will be used. " +"With the default settings of ``None``, no redirection will occur; the " +"child's file handles will be inherited from the parent. Additionally, " +"*stderr* can be :data:`STDOUT`, which indicates that the stderr data from " +"the applications should be captured into the same file handle as for stdout." +msgstr "" + +#: ../Doc/library/subprocess.rst:430 +msgid "" +"If *preexec_fn* is set to a callable object, this object will be called in " +"the child process just before the child is executed. (POSIX only)" +msgstr "" + +#: ../Doc/library/subprocess.rst:436 +msgid "" +"The *preexec_fn* parameter is not safe to use in the presence of threads in " +"your application. The child process could deadlock before exec is called. " +"If you must use it, keep it trivial! Minimize the number of libraries you " +"call into." +msgstr "" + +#: ../Doc/library/subprocess.rst:444 +msgid "" +"If you need to modify the environment for the child use the *env* parameter " +"rather than doing it in a *preexec_fn*. The *start_new_session* parameter " +"can take the place of a previously common use of *preexec_fn* to call os." +"setsid() in the child." +msgstr "" + +#: ../Doc/library/subprocess.rst:449 +msgid "" +"If *close_fds* is true, all file descriptors except :const:`0`, :const:`1` " +"and :const:`2` will be closed before the child process is executed. (POSIX " +"only). The default varies by platform: Always true on POSIX. On Windows it " +"is true when *stdin*/*stdout*/*stderr* are :const:`None`, false otherwise. " +"On Windows, if *close_fds* is true then no handles will be inherited by the " +"child process. Note that on Windows, you cannot set *close_fds* to true and " +"also redirect the standard handles by setting *stdin*, *stdout* or *stderr*." +msgstr "" + +#: ../Doc/library/subprocess.rst:457 +msgid "" +"The default for *close_fds* was changed from :const:`False` to what is " +"described above." +msgstr "" + +#: ../Doc/library/subprocess.rst:461 +msgid "" +"*pass_fds* is an optional sequence of file descriptors to keep open between " +"the parent and child. Providing any *pass_fds* forces *close_fds* to be :" +"const:`True`. (POSIX only)" +msgstr "" + +#: ../Doc/library/subprocess.rst:465 +msgid "The *pass_fds* parameter was added." +msgstr "" + +#: ../Doc/library/subprocess.rst:468 +msgid "" +"If *cwd* is not ``None``, the function changes the working directory to " +"*cwd* before executing the child. In particular, the function looks for " +"*executable* (or for the first item in *args*) relative to *cwd* if the " +"executable path is a relative path." +msgstr "" + +#: ../Doc/library/subprocess.rst:473 +msgid "" +"If *restore_signals* is true (the default) all signals that Python has set " +"to SIG_IGN are restored to SIG_DFL in the child process before the exec. " +"Currently this includes the SIGPIPE, SIGXFZ and SIGXFSZ signals. (POSIX only)" +msgstr "" + +#: ../Doc/library/subprocess.rst:478 +msgid "*restore_signals* was added." +msgstr "" + +#: ../Doc/library/subprocess.rst:481 +msgid "" +"If *start_new_session* is true the setsid() system call will be made in the " +"child process prior to the execution of the subprocess. (POSIX only)" +msgstr "" + +#: ../Doc/library/subprocess.rst:484 +msgid "*start_new_session* was added." +msgstr "" + +#: ../Doc/library/subprocess.rst:487 +msgid "" +"If *env* is not ``None``, it must be a mapping that defines the environment " +"variables for the new process; these are used instead of the default " +"behavior of inheriting the current process' environment." +msgstr "" + +#: ../Doc/library/subprocess.rst:493 +msgid "" +"If specified, *env* must provide any variables required for the program to " +"execute. On Windows, in order to run a `side-by-side assembly`_ the " +"specified *env* **must** include a valid :envvar:`SystemRoot`." +msgstr "" + +#: ../Doc/library/subprocess.rst:499 +msgid "" +"If *encoding* or *errors* are specified, the file objects *stdin*, *stdout* " +"and *stderr* are opened in text mode with the specified encoding and " +"*errors*, as described above in :ref:`frequently-used-arguments`. If " +"*universal_newlines* is ``True``, they are opened in text mode with default " +"encoding. Otherwise, they are opened as binary streams." +msgstr "" + +#: ../Doc/library/subprocess.rst:505 +msgid "*encoding* and *errors* were added." +msgstr "" + +#: ../Doc/library/subprocess.rst:508 +msgid "" +"If given, *startupinfo* will be a :class:`STARTUPINFO` object, which is " +"passed to the underlying ``CreateProcess`` function. *creationflags*, if " +"given, can be :data:`CREATE_NEW_CONSOLE` or :data:" +"`CREATE_NEW_PROCESS_GROUP`. (Windows only)" +msgstr "" + +#: ../Doc/library/subprocess.rst:513 +msgid "" +"Popen objects are supported as context managers via the :keyword:`with` " +"statement: on exit, standard file descriptors are closed, and the process is " +"waited for. ::" +msgstr "" + +#: ../Doc/library/subprocess.rst:523 +msgid "" +"Popen destructor now emits a :exc:`ResourceWarning` warning if the child " +"process is still running." +msgstr "" + +#: ../Doc/library/subprocess.rst:531 +msgid "" +"Exceptions raised in the child process, before the new program has started " +"to execute, will be re-raised in the parent. Additionally, the exception " +"object will have one extra attribute called :attr:`child_traceback`, which " +"is a string containing traceback information from the child's point of view." +msgstr "" + +#: ../Doc/library/subprocess.rst:536 +msgid "" +"The most common exception raised is :exc:`OSError`. This occurs, for " +"example, when trying to execute a non-existent file. Applications should " +"prepare for :exc:`OSError` exceptions." +msgstr "" + +#: ../Doc/library/subprocess.rst:540 +msgid "" +"A :exc:`ValueError` will be raised if :class:`Popen` is called with invalid " +"arguments." +msgstr "" + +#: ../Doc/library/subprocess.rst:543 +msgid "" +":func:`check_call` and :func:`check_output` will raise :exc:" +"`CalledProcessError` if the called process returns a non-zero return code." +msgstr "" + +#: ../Doc/library/subprocess.rst:547 +msgid "" +"All of the functions and methods that accept a *timeout* parameter, such as :" +"func:`call` and :meth:`Popen.communicate` will raise :exc:`TimeoutExpired` " +"if the timeout expires before the process exits." +msgstr "" + +#: ../Doc/library/subprocess.rst:551 +msgid "" +"Exceptions defined in this module all inherit from :exc:`SubprocessError`." +msgstr "" + +#: ../Doc/library/subprocess.rst:553 +msgid "The :exc:`SubprocessError` base class was added." +msgstr "" + +#: ../Doc/library/subprocess.rst:558 +msgid "Security Considerations" +msgstr "" + +#: ../Doc/library/subprocess.rst:560 +msgid "" +"Unlike some other popen functions, this implementation will never implicitly " +"call a system shell. This means that all characters, including shell " +"metacharacters, can safely be passed to child processes. If the shell is " +"invoked explicitly, via ``shell=True``, it is the application's " +"responsibility to ensure that all whitespace and metacharacters are quoted " +"appropriately to avoid `shell injection `_ vulnerabilities." +msgstr "" + +#: ../Doc/library/subprocess.rst:569 +msgid "" +"When using ``shell=True``, the :func:`shlex.quote` function can be used to " +"properly escape whitespace and shell metacharacters in strings that are " +"going to be used to construct shell commands." +msgstr "" + +#: ../Doc/library/subprocess.rst:575 +msgid "Popen Objects" +msgstr "" + +#: ../Doc/library/subprocess.rst:577 +msgid "Instances of the :class:`Popen` class have the following methods:" +msgstr "" + +#: ../Doc/library/subprocess.rst:582 +msgid "" +"Check if child process has terminated. Set and return :attr:`~Popen." +"returncode` attribute." +msgstr "" + +#: ../Doc/library/subprocess.rst:588 +msgid "" +"Wait for child process to terminate. Set and return :attr:`~Popen." +"returncode` attribute." +msgstr "" + +#: ../Doc/library/subprocess.rst:591 +msgid "" +"If the process does not terminate after *timeout* seconds, raise a :exc:" +"`TimeoutExpired` exception. It is safe to catch this exception and retry " +"the wait." +msgstr "" + +#: ../Doc/library/subprocess.rst:597 +msgid "" +"This will deadlock when using ``stdout=PIPE`` or ``stderr=PIPE`` and the " +"child process generates enough output to a pipe such that it blocks waiting " +"for the OS pipe buffer to accept more data. Use :meth:`Popen.communicate` " +"when using pipes to avoid that." +msgstr "" + +#: ../Doc/library/subprocess.rst:604 +msgid "" +"The function is implemented using a busy loop (non-blocking call and short " +"sleeps). Use the :mod:`asyncio` module for an asynchronous wait: see :class:" +"`asyncio.create_subprocess_exec`." +msgstr "" + +#: ../Doc/library/subprocess.rst:608 ../Doc/library/subprocess.rst:654 +#: ../Doc/library/subprocess.rst:878 ../Doc/library/subprocess.rst:906 +#: ../Doc/library/subprocess.rst:949 +msgid "*timeout* was added." +msgstr "" + +#: ../Doc/library/subprocess.rst:613 +msgid "" +"Do not use the *endtime* parameter. It is was unintentionally exposed in " +"3.3 but was left undocumented as it was intended to be private for internal " +"use. Use *timeout* instead." +msgstr "" + +#: ../Doc/library/subprocess.rst:619 +msgid "" +"Interact with process: Send data to stdin. Read data from stdout and " +"stderr, until end-of-file is reached. Wait for process to terminate. The " +"optional *input* argument should be data to be sent to the child process, or " +"``None``, if no data should be sent to the child. If streams were opened in " +"text mode, *input* must be a string. Otherwise, it must be bytes." +msgstr "" + +#: ../Doc/library/subprocess.rst:625 +msgid "" +":meth:`communicate` returns a tuple ``(stdout_data, stderr_data)``. The data " +"will be strings if streams were opened in text mode; otherwise, bytes." +msgstr "" + +#: ../Doc/library/subprocess.rst:629 +msgid "" +"Note that if you want to send data to the process's stdin, you need to " +"create the Popen object with ``stdin=PIPE``. Similarly, to get anything " +"other than ``None`` in the result tuple, you need to give ``stdout=PIPE`` " +"and/or ``stderr=PIPE`` too." +msgstr "" + +#: ../Doc/library/subprocess.rst:634 +msgid "" +"If the process does not terminate after *timeout* seconds, a :exc:" +"`TimeoutExpired` exception will be raised. Catching this exception and " +"retrying communication will not lose any output." +msgstr "" + +#: ../Doc/library/subprocess.rst:638 +msgid "" +"The child process is not killed if the timeout expires, so in order to " +"cleanup properly a well-behaved application should kill the child process " +"and finish communication::" +msgstr "" + +#: ../Doc/library/subprocess.rst:660 +msgid "Sends the signal *signal* to the child." +msgstr "" + +#: ../Doc/library/subprocess.rst:664 +msgid "" +"On Windows, SIGTERM is an alias for :meth:`terminate`. CTRL_C_EVENT and " +"CTRL_BREAK_EVENT can be sent to processes started with a *creationflags* " +"parameter which includes `CREATE_NEW_PROCESS_GROUP`." +msgstr "" + +#: ../Doc/library/subprocess.rst:671 +msgid "" +"Stop the child. On Posix OSs the method sends SIGTERM to the child. On " +"Windows the Win32 API function :c:func:`TerminateProcess` is called to stop " +"the child." +msgstr "" + +#: ../Doc/library/subprocess.rst:678 +msgid "" +"Kills the child. On Posix OSs the function sends SIGKILL to the child. On " +"Windows :meth:`kill` is an alias for :meth:`terminate`." +msgstr "" + +#: ../Doc/library/subprocess.rst:682 +msgid "The following attributes are also available:" +msgstr "" + +#: ../Doc/library/subprocess.rst:686 +msgid "" +"The *args* argument as it was passed to :class:`Popen` -- a sequence of " +"program arguments or else a single string." +msgstr "" + +#: ../Doc/library/subprocess.rst:693 +msgid "" +"If the *stdin* argument was :data:`PIPE`, this attribute is a writeable " +"stream object as returned by :func:`open`. If the *encoding* or *errors* " +"arguments were specified or the *universal_newlines* argument was ``True``, " +"the stream is a text stream, otherwise it is a byte stream. If the *stdin* " +"argument was not :data:`PIPE`, this attribute is ``None``." +msgstr "" + +#: ../Doc/library/subprocess.rst:702 +msgid "" +"If the *stdout* argument was :data:`PIPE`, this attribute is a readable " +"stream object as returned by :func:`open`. Reading from the stream provides " +"output from the child process. If the *encoding* or *errors* arguments were " +"specified or the *universal_newlines* argument was ``True``, the stream is a " +"text stream, otherwise it is a byte stream. If the *stdout* argument was " +"not :data:`PIPE`, this attribute is ``None``." +msgstr "" + +#: ../Doc/library/subprocess.rst:712 +msgid "" +"If the *stderr* argument was :data:`PIPE`, this attribute is a readable " +"stream object as returned by :func:`open`. Reading from the stream provides " +"error output from the child process. If the *encoding* or *errors* arguments " +"were specified or the *universal_newlines* argument was ``True``, the stream " +"is a text stream, otherwise it is a byte stream. If the *stderr* argument " +"was not :data:`PIPE`, this attribute is ``None``." +msgstr "" + +#: ../Doc/library/subprocess.rst:721 +msgid "" +"Use :meth:`~Popen.communicate` rather than :attr:`.stdin.write `, :attr:`.stdout.read ` or :attr:`.stderr.read ` to avoid deadlocks due to any of the other OS pipe buffers filling " +"up and blocking the child process." +msgstr "" + +#: ../Doc/library/subprocess.rst:729 +msgid "The process ID of the child process." +msgstr "" + +#: ../Doc/library/subprocess.rst:731 +msgid "" +"Note that if you set the *shell* argument to ``True``, this is the process " +"ID of the spawned shell." +msgstr "" + +#: ../Doc/library/subprocess.rst:737 +msgid "" +"The child return code, set by :meth:`poll` and :meth:`wait` (and indirectly " +"by :meth:`communicate`). A ``None`` value indicates that the process hasn't " +"terminated yet." +msgstr "" + +#: ../Doc/library/subprocess.rst:746 +msgid "Windows Popen Helpers" +msgstr "" + +#: ../Doc/library/subprocess.rst:748 +msgid "" +"The :class:`STARTUPINFO` class and following constants are only available on " +"Windows." +msgstr "" + +#: ../Doc/library/subprocess.rst:753 +msgid "" +"Partial support of the Windows `STARTUPINFO `__ structure is used for :class:`Popen` " +"creation." +msgstr "" + +#: ../Doc/library/subprocess.rst:759 +msgid "" +"A bit field that determines whether certain :class:`STARTUPINFO` attributes " +"are used when the process creates a window. ::" +msgstr "" + +#: ../Doc/library/subprocess.rst:767 +msgid "" +"If :attr:`dwFlags` specifies :data:`STARTF_USESTDHANDLES`, this attribute is " +"the standard input handle for the process. If :data:`STARTF_USESTDHANDLES` " +"is not specified, the default for standard input is the keyboard buffer." +msgstr "" + +#: ../Doc/library/subprocess.rst:774 +msgid "" +"If :attr:`dwFlags` specifies :data:`STARTF_USESTDHANDLES`, this attribute is " +"the standard output handle for the process. Otherwise, this attribute is " +"ignored and the default for standard output is the console window's buffer." +msgstr "" + +#: ../Doc/library/subprocess.rst:781 +msgid "" +"If :attr:`dwFlags` specifies :data:`STARTF_USESTDHANDLES`, this attribute is " +"the standard error handle for the process. Otherwise, this attribute is " +"ignored and the default for standard error is the console window's buffer." +msgstr "" + +#: ../Doc/library/subprocess.rst:787 +msgid "" +"If :attr:`dwFlags` specifies :data:`STARTF_USESHOWWINDOW`, this attribute " +"can be any of the values that can be specified in the ``nCmdShow`` parameter " +"for the `ShowWindow `__ function, except for ``SW_SHOWDEFAULT``. " +"Otherwise, this attribute is ignored." +msgstr "" + +#: ../Doc/library/subprocess.rst:794 +msgid "" +":data:`SW_HIDE` is provided for this attribute. It is used when :class:" +"`Popen` is called with ``shell=True``." +msgstr "" + +#: ../Doc/library/subprocess.rst:801 +msgid "The :mod:`subprocess` module exposes the following constants." +msgstr "" + +#: ../Doc/library/subprocess.rst:805 +msgid "" +"The standard input device. Initially, this is the console input buffer, " +"``CONIN$``." +msgstr "" + +#: ../Doc/library/subprocess.rst:810 +msgid "" +"The standard output device. Initially, this is the active console screen " +"buffer, ``CONOUT$``." +msgstr "" + +#: ../Doc/library/subprocess.rst:815 +msgid "" +"The standard error device. Initially, this is the active console screen " +"buffer, ``CONOUT$``." +msgstr "" + +#: ../Doc/library/subprocess.rst:820 +msgid "Hides the window. Another window will be activated." +msgstr "" + +#: ../Doc/library/subprocess.rst:824 +msgid "" +"Specifies that the :attr:`STARTUPINFO.hStdInput`, :attr:`STARTUPINFO." +"hStdOutput`, and :attr:`STARTUPINFO.hStdError` attributes contain additional " +"information." +msgstr "" + +#: ../Doc/library/subprocess.rst:830 +msgid "" +"Specifies that the :attr:`STARTUPINFO.wShowWindow` attribute contains " +"additional information." +msgstr "" + +#: ../Doc/library/subprocess.rst:835 +msgid "" +"The new process has a new console, instead of inheriting its parent's " +"console (the default)." +msgstr "" + +#: ../Doc/library/subprocess.rst:840 +msgid "" +"A :class:`Popen` ``creationflags`` parameter to specify that a new process " +"group will be created. This flag is necessary for using :func:`os.kill` on " +"the subprocess." +msgstr "" + +#: ../Doc/library/subprocess.rst:844 +msgid "This flag is ignored if :data:`CREATE_NEW_CONSOLE` is specified." +msgstr "" + +#: ../Doc/library/subprocess.rst:849 +msgid "Older high-level API" +msgstr "" + +#: ../Doc/library/subprocess.rst:851 +msgid "" +"Prior to Python 3.5, these three functions comprised the high level API to " +"subprocess. You can now use :func:`run` in many cases, but lots of existing " +"code calls these functions." +msgstr "" + +#: ../Doc/library/subprocess.rst:857 +msgid "" +"Run the command described by *args*. Wait for command to complete, then " +"return the :attr:`~Popen.returncode` attribute." +msgstr "" + +#: ../Doc/library/subprocess.rst:860 ../Doc/library/subprocess.rst:888 +#: ../Doc/library/subprocess.rst:921 ../Doc/library/typing.rst:688 +msgid "This is equivalent to::" +msgstr "" + +#: ../Doc/library/subprocess.rst:864 +msgid "(except that the *input* and *check* parameters are not supported)" +msgstr "" + +#: ../Doc/library/subprocess.rst:866 ../Doc/library/subprocess.rst:894 +msgid "" +"The arguments shown above are merely the most common ones. The full function " +"signature is largely the same as that of the :class:`Popen` constructor - " +"this function passes all supplied arguments other than *timeout* directly " +"through to that interface." +msgstr "" + +#: ../Doc/library/subprocess.rst:873 ../Doc/library/subprocess.rst:901 +msgid "" +"Do not use ``stdout=PIPE`` or ``stderr=PIPE`` with this function. The child " +"process will block if it generates enough output to a pipe to fill up the OS " +"pipe buffer as the pipes are not being read from." +msgstr "" + +#: ../Doc/library/subprocess.rst:883 +msgid "" +"Run command with arguments. Wait for command to complete. If the return " +"code was zero then return, otherwise raise :exc:`CalledProcessError`. The :" +"exc:`CalledProcessError` object will have the return code in the :attr:" +"`~CalledProcessError.returncode` attribute." +msgstr "" + +#: ../Doc/library/subprocess.rst:892 +msgid "(except that the *input* parameter is not supported)" +msgstr "" + +#: ../Doc/library/subprocess.rst:914 +msgid "Run command with arguments and return its output." +msgstr "" + +#: ../Doc/library/subprocess.rst:916 +msgid "" +"If the return code was non-zero it raises a :exc:`CalledProcessError`. The :" +"exc:`CalledProcessError` object will have the return code in the :attr:" +"`~CalledProcessError.returncode` attribute and any output in the :attr:" +"`~CalledProcessError.output` attribute." +msgstr "" + +#: ../Doc/library/subprocess.rst:925 +msgid "" +"The arguments shown above are merely the most common ones. The full function " +"signature is largely the same as that of :func:`run` - most arguments are " +"passed directly through to that interface. However, explicitly passing " +"``input=None`` to inherit the parent's standard input file handle is not " +"supported." +msgstr "" + +#: ../Doc/library/subprocess.rst:931 +msgid "" +"By default, this function will return the data as encoded bytes. The actual " +"encoding of the output data may depend on the command being invoked, so the " +"decoding to text will often need to be handled at the application level." +msgstr "" + +#: ../Doc/library/subprocess.rst:935 +msgid "" +"This behaviour may be overridden by setting *universal_newlines* to ``True`` " +"as described above in :ref:`frequently-used-arguments`." +msgstr "" + +#: ../Doc/library/subprocess.rst:938 +msgid "" +"To also capture standard error in the result, use ``stderr=subprocess." +"STDOUT``::" +msgstr "" + +#: ../Doc/library/subprocess.rst:952 +msgid "Support for the *input* keyword argument was added." +msgstr "" + +#: ../Doc/library/subprocess.rst:958 +msgid "Replacing Older Functions with the :mod:`subprocess` Module" +msgstr "" + +#: ../Doc/library/subprocess.rst:960 +msgid "" +"In this section, \"a becomes b\" means that b can be used as a replacement " +"for a." +msgstr "" + +#: ../Doc/library/subprocess.rst:964 +msgid "" +"All \"a\" functions in this section fail (more or less) silently if the " +"executed program cannot be found; the \"b\" replacements raise :exc:" +"`OSError` instead." +msgstr "" + +#: ../Doc/library/subprocess.rst:968 +msgid "" +"In addition, the replacements using :func:`check_output` will fail with a :" +"exc:`CalledProcessError` if the requested operation produces a non-zero " +"return code. The output is still available as the :attr:`~CalledProcessError." +"output` attribute of the raised exception." +msgstr "" + +#: ../Doc/library/subprocess.rst:973 +msgid "" +"In the following examples, we assume that the relevant functions have " +"already been imported from the :mod:`subprocess` module." +msgstr "" + +#: ../Doc/library/subprocess.rst:978 +msgid "Replacing /bin/sh shell backquote" +msgstr "" + +#: ../Doc/library/subprocess.rst:984 ../Doc/library/subprocess.rst:995 +#: ../Doc/library/subprocess.rst:1012 +msgid "becomes::" +msgstr "" + +#: ../Doc/library/subprocess.rst:989 +msgid "Replacing shell pipeline" +msgstr "" + +#: ../Doc/library/subprocess.rst:1002 +msgid "" +"The p1.stdout.close() call after starting the p2 is important in order for " +"p1 to receive a SIGPIPE if p2 exits before p1." +msgstr "" + +#: ../Doc/library/subprocess.rst:1005 +msgid "" +"Alternatively, for trusted input, the shell's own pipeline support may still " +"be used directly:" +msgstr "" + +#: ../Doc/library/subprocess.rst:1018 +msgid "Replacing :func:`os.system`" +msgstr "" + +#: ../Doc/library/subprocess.rst:1028 +msgid "Calling the program through the shell is usually not required." +msgstr "" + +#: ../Doc/library/subprocess.rst:1030 +msgid "A more realistic example would look like this::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1043 +msgid "Replacing the :func:`os.spawn ` family" +msgstr "" + +#: ../Doc/library/subprocess.rst:1045 +msgid "P_NOWAIT example::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1051 +msgid "P_WAIT example::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1057 +msgid "Vector example::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1063 +msgid "Environment example::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1072 +msgid "Replacing :func:`os.popen`, :func:`os.popen2`, :func:`os.popen3`" +msgstr "" + +#: ../Doc/library/subprocess.rst:1102 +msgid "Return code handling translates as follows::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1118 +msgid "Replacing functions from the :mod:`popen2` module" +msgstr "" + +#: ../Doc/library/subprocess.rst:1122 +msgid "" +"If the cmd argument to popen2 functions is a string, the command is executed " +"through /bin/sh. If it is a list, the command is directly executed." +msgstr "" + +#: ../Doc/library/subprocess.rst:1141 +msgid "" +":class:`popen2.Popen3` and :class:`popen2.Popen4` basically work as :class:" +"`subprocess.Popen`, except that:" +msgstr "" + +#: ../Doc/library/subprocess.rst:1144 +msgid ":class:`Popen` raises an exception if the execution fails." +msgstr "" + +#: ../Doc/library/subprocess.rst:1146 +msgid "the *capturestderr* argument is replaced with the *stderr* argument." +msgstr "" + +#: ../Doc/library/subprocess.rst:1148 +msgid "``stdin=PIPE`` and ``stdout=PIPE`` must be specified." +msgstr "" + +#: ../Doc/library/subprocess.rst:1150 +msgid "" +"popen2 closes all file descriptors by default, but you have to specify " +"``close_fds=True`` with :class:`Popen` to guarantee this behavior on all " +"platforms or past Python versions." +msgstr "" + +#: ../Doc/library/subprocess.rst:1156 +msgid "Legacy Shell Invocation Functions" +msgstr "" + +#: ../Doc/library/subprocess.rst:1158 +msgid "" +"This module also provides the following legacy functions from the 2.x " +"``commands`` module. These operations implicitly invoke the system shell and " +"none of the guarantees described above regarding security and exception " +"handling consistency are valid for these functions." +msgstr "" + +#: ../Doc/library/subprocess.rst:1165 +msgid "Return ``(status, output)`` of executing *cmd* in a shell." +msgstr "" + +#: ../Doc/library/subprocess.rst:1167 +msgid "" +"Execute the string *cmd* in a shell with :meth:`Popen.check_output` and " +"return a 2-tuple ``(status, output)``. The locale encoding is used; see the " +"notes on :ref:`frequently-used-arguments` for more details." +msgstr "" + +#: ../Doc/library/subprocess.rst:1171 +msgid "" +"A trailing newline is stripped from the output. The exit status for the " +"command can be interpreted according to the rules for the C function :c:func:" +"`wait`. Example::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1182 ../Doc/library/subprocess.rst:1198 +msgid "Availability: POSIX & Windows" +msgstr "" + +#: ../Doc/library/subprocess.rst:1190 +msgid "Return output (stdout and stderr) of executing *cmd* in a shell." +msgstr "" + +#: ../Doc/library/subprocess.rst:1192 +msgid "" +"Like :func:`getstatusoutput`, except the exit status is ignored and the " +"return value is a string containing the command's output. Example::" +msgstr "" + +#: ../Doc/library/subprocess.rst:1210 +msgid "Converting an argument sequence to a string on Windows" +msgstr "" + +#: ../Doc/library/subprocess.rst:1212 +msgid "" +"On Windows, an *args* sequence is converted to a string that can be parsed " +"using the following rules (which correspond to the rules used by the MS C " +"runtime):" +msgstr "" + +#: ../Doc/library/subprocess.rst:1216 +msgid "" +"Arguments are delimited by white space, which is either a space or a tab." +msgstr "" + +#: ../Doc/library/subprocess.rst:1219 +msgid "" +"A string surrounded by double quotation marks is interpreted as a single " +"argument, regardless of white space contained within. A quoted string can " +"be embedded in an argument." +msgstr "" + +#: ../Doc/library/subprocess.rst:1224 +msgid "" +"A double quotation mark preceded by a backslash is interpreted as a literal " +"double quotation mark." +msgstr "" + +#: ../Doc/library/subprocess.rst:1227 +msgid "" +"Backslashes are interpreted literally, unless they immediately precede a " +"double quotation mark." +msgstr "" + +#: ../Doc/library/subprocess.rst:1230 +msgid "" +"If backslashes immediately precede a double quotation mark, every pair of " +"backslashes is interpreted as a literal backslash. If the number of " +"backslashes is odd, the last backslash escapes the next double quotation " +"mark as described in rule 3." +msgstr "" + +#: ../Doc/library/subprocess.rst:1239 +msgid ":mod:`shlex`" +msgstr "" + +#: ../Doc/library/subprocess.rst:1240 +msgid "Module which provides function to parse and escape command lines." +msgstr "" + +#: ../Doc/library/sunau.rst:2 +msgid ":mod:`sunau` --- Read and write Sun AU files" +msgstr "" + +#: ../Doc/library/sunau.rst:9 +msgid "**Source code:** :source:`Lib/sunau.py`" +msgstr "" + +#: ../Doc/library/sunau.rst:13 +msgid "" +"The :mod:`sunau` module provides a convenient interface to the Sun AU sound " +"format. Note that this module is interface-compatible with the modules :mod:" +"`aifc` and :mod:`wave`." +msgstr "" + +#: ../Doc/library/sunau.rst:17 +msgid "" +"An audio file consists of a header followed by the data. The fields of the " +"header are:" +msgstr "" + +#: ../Doc/library/sunau.rst:23 +msgid "magic word" +msgstr "" + +#: ../Doc/library/sunau.rst:23 +msgid "The four bytes ``.snd``." +msgstr "" + +#: ../Doc/library/sunau.rst:25 +msgid "header size" +msgstr "" + +#: ../Doc/library/sunau.rst:25 +msgid "Size of the header, including info, in bytes." +msgstr "" + +#: ../Doc/library/sunau.rst:27 +msgid "data size" +msgstr "" + +#: ../Doc/library/sunau.rst:27 +msgid "Physical size of the data, in bytes." +msgstr "" + +#: ../Doc/library/sunau.rst:29 +msgid "encoding" +msgstr "" + +#: ../Doc/library/sunau.rst:29 +msgid "Indicates how the audio samples are encoded." +msgstr "" + +#: ../Doc/library/sunau.rst:31 +msgid "sample rate" +msgstr "" + +#: ../Doc/library/sunau.rst:31 +msgid "The sampling rate." +msgstr "" + +#: ../Doc/library/sunau.rst:33 +msgid "# of channels" +msgstr "" + +#: ../Doc/library/sunau.rst:33 +msgid "The number of channels in the samples." +msgstr "" + +#: ../Doc/library/sunau.rst:35 +msgid "info" +msgstr "" + +#: ../Doc/library/sunau.rst:35 +msgid "" +"ASCII string giving a description of the audio file (padded with null bytes)." +msgstr "" + +#: ../Doc/library/sunau.rst:39 +msgid "" +"Apart from the info field, all header fields are 4 bytes in size. They are " +"all 32-bit unsigned integers encoded in big-endian byte order." +msgstr "" + +#: ../Doc/library/sunau.rst:42 +msgid "The :mod:`sunau` module defines the following functions:" +msgstr "" + +#: ../Doc/library/sunau.rst:47 +msgid "" +"If *file* is a string, open the file by that name, otherwise treat it as a " +"seekable file-like object. *mode* can be any of" +msgstr "" + +#: ../Doc/library/sunau.rst:51 ../Doc/library/wave.rst:26 +msgid "Read only mode." +msgstr "" + +#: ../Doc/library/sunau.rst:54 ../Doc/library/wave.rst:29 +msgid "Write only mode." +msgstr "" + +#: ../Doc/library/sunau.rst:56 +msgid "Note that it does not allow read/write files." +msgstr "" + +#: ../Doc/library/sunau.rst:58 +msgid "" +"A *mode* of ``'r'`` returns an :class:`AU_read` object, while a *mode* of " +"``'w'`` or ``'wb'`` returns an :class:`AU_write` object." +msgstr "" + +#: ../Doc/library/sunau.rst:64 ../Doc/library/wave.rst:52 +msgid "A synonym for :func:`.open`, maintained for backwards compatibility." +msgstr "" + +#: ../Doc/library/sunau.rst:67 +msgid "The :mod:`sunau` module defines the following exception:" +msgstr "" + +#: ../Doc/library/sunau.rst:71 +msgid "" +"An error raised when something is impossible because of Sun AU specs or " +"implementation deficiency." +msgstr "" + +#: ../Doc/library/sunau.rst:75 +msgid "The :mod:`sunau` module defines the following data items:" +msgstr "" + +#: ../Doc/library/sunau.rst:79 +msgid "" +"An integer every valid Sun AU file begins with, stored in big-endian form. " +"This is the string ``.snd`` interpreted as an integer." +msgstr "" + +#: ../Doc/library/sunau.rst:90 +msgid "" +"Values of the encoding field from the AU header which are supported by this " +"module." +msgstr "" + +#: ../Doc/library/sunau.rst:101 +msgid "" +"Additional known values of the encoding field from the AU header, but which " +"are not supported by this module." +msgstr "" + +#: ../Doc/library/sunau.rst:108 +msgid "AU_read Objects" +msgstr "" + +#: ../Doc/library/sunau.rst:110 +msgid "" +"AU_read objects, as returned by :func:`.open` above, have the following " +"methods:" +msgstr "" + +#: ../Doc/library/sunau.rst:115 +msgid "" +"Close the stream, and make the instance unusable. (This is called " +"automatically on deletion.)" +msgstr "" + +#: ../Doc/library/sunau.rst:121 +msgid "Returns number of audio channels (1 for mone, 2 for stereo)." +msgstr "" + +#: ../Doc/library/sunau.rst:126 ../Doc/library/wave.rst:82 +msgid "Returns sample width in bytes." +msgstr "" + +#: ../Doc/library/sunau.rst:131 ../Doc/library/wave.rst:87 +msgid "Returns sampling frequency." +msgstr "" + +#: ../Doc/library/sunau.rst:136 ../Doc/library/wave.rst:92 +msgid "Returns number of audio frames." +msgstr "" + +#: ../Doc/library/sunau.rst:141 +msgid "" +"Returns compression type. Supported compression types are ``'ULAW'``, " +"``'ALAW'`` and ``'NONE'``." +msgstr "" + +#: ../Doc/library/sunau.rst:147 +msgid "" +"Human-readable version of :meth:`getcomptype`. The supported types have the " +"respective names ``'CCITT G.711 u-law'``, ``'CCITT G.711 A-law'`` and ``'not " +"compressed'``." +msgstr "" + +#: ../Doc/library/sunau.rst:161 +msgid "" +"Reads and returns at most *n* frames of audio, as a :class:`bytes` object. " +"The data will be returned in linear format. If the original data is in u-" +"LAW format, it will be converted." +msgstr "" + +#: ../Doc/library/sunau.rst:168 ../Doc/library/wave.rst:120 +msgid "Rewind the file pointer to the beginning of the audio stream." +msgstr "" + +#: ../Doc/library/sunau.rst:170 ../Doc/library/wave.rst:135 +msgid "" +"The following two methods define a term \"position\" which is compatible " +"between them, and is otherwise implementation dependent." +msgstr "" + +#: ../Doc/library/sunau.rst:176 +msgid "" +"Set the file pointer to the specified position. Only values returned from :" +"meth:`tell` should be used for *pos*." +msgstr "" + +#: ../Doc/library/sunau.rst:182 +msgid "" +"Return current file pointer position. Note that the returned value has " +"nothing to do with the actual position in the file." +msgstr "" + +#: ../Doc/library/sunau.rst:185 +msgid "" +"The following two functions are defined for compatibility with the :mod:" +"`aifc`, and don't do anything interesting." +msgstr "" + +#: ../Doc/library/sunau.rst:191 ../Doc/library/wave.rst:128 +msgid "Returns ``None``." +msgstr "" + +#: ../Doc/library/sunau.rst:196 ../Doc/library/wave.rst:133 +msgid "Raise an error." +msgstr "" + +#: ../Doc/library/sunau.rst:202 +msgid "AU_write Objects" +msgstr "" + +#: ../Doc/library/sunau.rst:204 +msgid "" +"AU_write objects, as returned by :func:`.open` above, have the following " +"methods:" +msgstr "" + +#: ../Doc/library/sunau.rst:209 ../Doc/library/wave.rst:182 +msgid "Set the number of channels." +msgstr "" + +#: ../Doc/library/sunau.rst:214 +msgid "Set the sample width (in bytes.)" +msgstr "" + +#: ../Doc/library/sunau.rst:216 +msgid "Added support for 24-bit samples." +msgstr "" + +#: ../Doc/library/sunau.rst:222 +msgid "Set the frame rate." +msgstr "" + +#: ../Doc/library/sunau.rst:227 +msgid "" +"Set the number of frames. This can be later changed, when and if more " +"frames are written." +msgstr "" + +#: ../Doc/library/sunau.rst:233 +msgid "" +"Set the compression type and description. Only ``'NONE'`` and ``'ULAW'`` are " +"supported on output." +msgstr "" + +#: ../Doc/library/sunau.rst:239 +msgid "" +"The *tuple* should be ``(nchannels, sampwidth, framerate, nframes, comptype, " +"compname)``, with values valid for the :meth:`set\\*` methods. Set all " +"parameters." +msgstr "" + +#: ../Doc/library/sunau.rst:246 +msgid "" +"Return current position in the file, with the same disclaimer for the :meth:" +"`AU_read.tell` and :meth:`AU_read.setpos` methods." +msgstr "" + +#: ../Doc/library/sunau.rst:252 ../Doc/library/wave.rst:227 +msgid "Write audio frames, without correcting *nframes*." +msgstr "" + +#: ../Doc/library/sunau.rst:260 +msgid "Write audio frames and make sure *nframes* is correct." +msgstr "" + +#: ../Doc/library/sunau.rst:268 +msgid "Make sure *nframes* is correct, and close the file." +msgstr "" + +#: ../Doc/library/sunau.rst:270 +msgid "This method is called upon deletion." +msgstr "" + +#: ../Doc/library/sunau.rst:272 +msgid "" +"Note that it is invalid to set any parameters after calling :meth:" +"`writeframes` or :meth:`writeframesraw`." +msgstr "" + +#: ../Doc/library/superseded.rst:5 +msgid "Superseded Modules" +msgstr "" + +#: ../Doc/library/superseded.rst:7 +msgid "" +"The modules described in this chapter are deprecated and only kept for " +"backwards compatibility. They have been superseded by other modules." +msgstr "" + +#: ../Doc/library/symbol.rst:2 +msgid ":mod:`symbol` --- Constants used with Python parse trees" +msgstr "" + +#: ../Doc/library/symbol.rst:9 +msgid "**Source code:** :source:`Lib/symbol.py`" +msgstr "" + +#: ../Doc/library/symbol.rst:13 +msgid "" +"This module provides constants which represent the numeric values of " +"internal nodes of the parse tree. Unlike most Python constants, these use " +"lower-case names. Refer to the file :file:`Grammar/Grammar` in the Python " +"distribution for the definitions of the names in the context of the language " +"grammar. The specific numeric values which the names map to may change " +"between Python versions." +msgstr "" + +#: ../Doc/library/symbol.rst:20 +msgid "This module also provides one additional data object:" +msgstr "" + +#: ../Doc/library/symbol.rst:25 ../Doc/library/token.rst:25 +msgid "" +"Dictionary mapping the numeric values of the constants defined in this " +"module back to name strings, allowing more human-readable representation of " +"parse trees to be generated." +msgstr "" + +#: ../Doc/library/symtable.rst:2 +msgid ":mod:`symtable` --- Access to the compiler's symbol tables" +msgstr "" + +#: ../Doc/library/symtable.rst:7 +msgid "**Source code:** :source:`Lib/symtable.py`" +msgstr "" + +#: ../Doc/library/symtable.rst:15 +msgid "" +"Symbol tables are generated by the compiler from AST just before bytecode is " +"generated. The symbol table is responsible for calculating the scope of " +"every identifier in the code. :mod:`symtable` provides an interface to " +"examine these tables." +msgstr "" + +#: ../Doc/library/symtable.rst:22 +msgid "Generating Symbol Tables" +msgstr "" + +#: ../Doc/library/symtable.rst:26 +msgid "" +"Return the toplevel :class:`SymbolTable` for the Python source *code*. " +"*filename* is the name of the file containing the code. *compile_type* is " +"like the *mode* argument to :func:`compile`." +msgstr "" + +#: ../Doc/library/symtable.rst:32 +msgid "Examining Symbol Tables" +msgstr "" + +#: ../Doc/library/symtable.rst:36 +msgid "A namespace table for a block. The constructor is not public." +msgstr "" + +#: ../Doc/library/symtable.rst:40 +msgid "" +"Return the type of the symbol table. Possible values are ``'class'``, " +"``'module'``, and ``'function'``." +msgstr "" + +#: ../Doc/library/symtable.rst:45 +msgid "Return the table's identifier." +msgstr "" + +#: ../Doc/library/symtable.rst:49 +msgid "" +"Return the table's name. This is the name of the class if the table is for " +"a class, the name of the function if the table is for a function, or " +"``'top'`` if the table is global (:meth:`get_type` returns ``'module'``)." +msgstr "" + +#: ../Doc/library/symtable.rst:55 +msgid "Return the number of the first line in the block this table represents." +msgstr "" + +#: ../Doc/library/symtable.rst:59 +msgid "Return ``True`` if the locals in this table can be optimized." +msgstr "" + +#: ../Doc/library/symtable.rst:63 +msgid "Return ``True`` if the block is a nested class or function." +msgstr "" + +#: ../Doc/library/symtable.rst:67 +msgid "" +"Return ``True`` if the block has nested namespaces within it. These can be " +"obtained with :meth:`get_children`." +msgstr "" + +#: ../Doc/library/symtable.rst:72 +msgid "Return ``True`` if the block uses ``exec``." +msgstr "" + +#: ../Doc/library/symtable.rst:76 +msgid "Return a list of names of symbols in this table." +msgstr "" + +#: ../Doc/library/symtable.rst:80 +msgid "Lookup *name* in the table and return a :class:`Symbol` instance." +msgstr "" + +#: ../Doc/library/symtable.rst:84 +msgid "Return a list of :class:`Symbol` instances for names in the table." +msgstr "" + +#: ../Doc/library/symtable.rst:88 +msgid "Return a list of the nested symbol tables." +msgstr "" + +#: ../Doc/library/symtable.rst:93 +msgid "" +"A namespace for a function or method. This class inherits :class:" +"`SymbolTable`." +msgstr "" + +#: ../Doc/library/symtable.rst:98 +msgid "Return a tuple containing names of parameters to this function." +msgstr "" + +#: ../Doc/library/symtable.rst:102 +msgid "Return a tuple containing names of locals in this function." +msgstr "" + +#: ../Doc/library/symtable.rst:106 +msgid "Return a tuple containing names of globals in this function." +msgstr "" + +#: ../Doc/library/symtable.rst:110 +msgid "Return a tuple containing names of free variables in this function." +msgstr "" + +#: ../Doc/library/symtable.rst:115 +msgid "A namespace of a class. This class inherits :class:`SymbolTable`." +msgstr "" + +#: ../Doc/library/symtable.rst:119 +msgid "Return a tuple containing the names of methods declared in the class." +msgstr "" + +#: ../Doc/library/symtable.rst:124 +msgid "" +"An entry in a :class:`SymbolTable` corresponding to an identifier in the " +"source. The constructor is not public." +msgstr "" + +#: ../Doc/library/symtable.rst:129 +msgid "Return the symbol's name." +msgstr "" + +#: ../Doc/library/symtable.rst:133 +msgid "Return ``True`` if the symbol is used in its block." +msgstr "" + +#: ../Doc/library/symtable.rst:137 +msgid "Return ``True`` if the symbol is created from an import statement." +msgstr "" + +#: ../Doc/library/symtable.rst:141 +msgid "Return ``True`` if the symbol is a parameter." +msgstr "" + +#: ../Doc/library/symtable.rst:145 +msgid "Return ``True`` if the symbol is global." +msgstr "" + +#: ../Doc/library/symtable.rst:149 +msgid "" +"Return ``True`` if the symbol is declared global with a global statement." +msgstr "" + +#: ../Doc/library/symtable.rst:153 +msgid "Return ``True`` if the symbol is local to its block." +msgstr "" + +#: ../Doc/library/symtable.rst:157 +msgid "" +"Return ``True`` if the symbol is referenced in its block, but not assigned " +"to." +msgstr "" + +#: ../Doc/library/symtable.rst:162 +msgid "Return ``True`` if the symbol is assigned to in its block." +msgstr "" + +#: ../Doc/library/symtable.rst:166 +msgid "Return ``True`` if name binding introduces new namespace." +msgstr "" + +#: ../Doc/library/symtable.rst:168 +msgid "" +"If the name is used as the target of a function or class statement, this " +"will be true." +msgstr "" + +#: ../Doc/library/symtable.rst:177 +msgid "" +"Note that a single name can be bound to multiple objects. If the result is " +"``True``, the name may also be bound to other objects, like an int or list, " +"that does not introduce a new namespace." +msgstr "" + +#: ../Doc/library/symtable.rst:183 +msgid "Return a list of namespaces bound to this name." +msgstr "" + +#: ../Doc/library/symtable.rst:187 +msgid "" +"Return the namespace bound to this name. If more than one namespace is " +"bound, :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/sys.rst:2 +msgid ":mod:`sys` --- System-specific parameters and functions" +msgstr "" + +#: ../Doc/library/sys.rst:9 +msgid "" +"This module provides access to some variables used or maintained by the " +"interpreter and to functions that interact strongly with the interpreter. It " +"is always available." +msgstr "" + +#: ../Doc/library/sys.rst:16 +msgid "" +"On POSIX systems where Python was built with the standard ``configure`` " +"script, this contains the ABI flags as specified by :pep:`3149`." +msgstr "" + +#: ../Doc/library/sys.rst:24 +msgid "" +"The list of command line arguments passed to a Python script. ``argv[0]`` is " +"the script name (it is operating system dependent whether this is a full " +"pathname or not). If the command was executed using the :option:`-c` " +"command line option to the interpreter, ``argv[0]`` is set to the string ``'-" +"c'``. If no script name was passed to the Python interpreter, ``argv[0]`` " +"is the empty string." +msgstr "" + +#: ../Doc/library/sys.rst:30 +msgid "" +"To loop over the standard input, or the list of files given on the command " +"line, see the :mod:`fileinput` module." +msgstr "" + +#: ../Doc/library/sys.rst:36 +msgid "" +"Set during Python startup, before ``site.py`` is run, to the same value as :" +"data:`exec_prefix`. If not running in a :ref:`virtual environment `, the values will stay the same; if ``site.py`` finds that a virtual " +"environment is in use, the values of :data:`prefix` and :data:`exec_prefix` " +"will be changed to point to the virtual environment, whereas :data:" +"`base_prefix` and :data:`base_exec_prefix` will remain pointing to the base " +"Python installation (the one which the virtual environment was created from)." +msgstr "" + +#: ../Doc/library/sys.rst:50 +msgid "" +"Set during Python startup, before ``site.py`` is run, to the same value as :" +"data:`prefix`. If not running in a :ref:`virtual environment `, " +"the values will stay the same; if ``site.py`` finds that a virtual " +"environment is in use, the values of :data:`prefix` and :data:`exec_prefix` " +"will be changed to point to the virtual environment, whereas :data:" +"`base_prefix` and :data:`base_exec_prefix` will remain pointing to the base " +"Python installation (the one which the virtual environment was created from)." +msgstr "" + +#: ../Doc/library/sys.rst:63 +msgid "" +"An indicator of the native byte order. This will have the value ``'big'`` " +"on big-endian (most-significant byte first) platforms, and ``'little'`` on " +"little-endian (least-significant byte first) platforms." +msgstr "" + +#: ../Doc/library/sys.rst:70 +msgid "" +"A tuple of strings giving the names of all modules that are compiled into " +"this Python interpreter. (This information is not available in any other " +"way --- ``modules.keys()`` only lists the imported modules.)" +msgstr "" + +#: ../Doc/library/sys.rst:77 +msgid "" +"Call ``func(*args)``, while tracing is enabled. The tracing state is saved, " +"and restored afterwards. This is intended to be called from a debugger from " +"a checkpoint, to recursively debug some other code." +msgstr "" + +#: ../Doc/library/sys.rst:84 +msgid "A string containing the copyright pertaining to the Python interpreter." +msgstr "" + +#: ../Doc/library/sys.rst:89 +msgid "" +"Clear the internal type cache. The type cache is used to speed up attribute " +"and method lookups. Use the function *only* to drop unnecessary references " +"during reference leak debugging." +msgstr "" + +#: ../Doc/library/sys.rst:93 ../Doc/library/sys.rst:109 +msgid "" +"This function should be used for internal and specialized purposes only." +msgstr "" + +#: ../Doc/library/sys.rst:98 +msgid "" +"Return a dictionary mapping each thread's identifier to the topmost stack " +"frame currently active in that thread at the time the function is called. " +"Note that functions in the :mod:`traceback` module can build the call stack " +"given such a frame." +msgstr "" + +#: ../Doc/library/sys.rst:103 +msgid "" +"This is most useful for debugging deadlock: this function does not require " +"the deadlocked threads' cooperation, and such threads' call stacks are " +"frozen for as long as they remain deadlocked. The frame returned for a non-" +"deadlocked thread may bear no relationship to that thread's current activity " +"by the time calling code examines the frame." +msgstr "" + +#: ../Doc/library/sys.rst:114 +msgid "" +"Print low-level information to stderr about the state of CPython's memory " +"allocator." +msgstr "" + +#: ../Doc/library/sys.rst:117 +msgid "" +"If Python is configured --with-pydebug, it also performs some expensive " +"internal consistency checks." +msgstr "" + +#: ../Doc/library/sys.rst:124 +msgid "" +"This function is specific to CPython. The exact output format is not " +"defined here, and may change." +msgstr "" + +#: ../Doc/library/sys.rst:130 +msgid "Integer specifying the handle of the Python DLL. Availability: Windows." +msgstr "" + +#: ../Doc/library/sys.rst:135 +msgid "" +"If *value* is not ``None``, this function prints ``repr(value)`` to ``sys." +"stdout``, and saves *value* in ``builtins._``. If ``repr(value)`` is not " +"encodable to ``sys.stdout.encoding`` with ``sys.stdout.errors`` error " +"handler (which is probably ``'strict'``), encode it to ``sys.stdout." +"encoding`` with ``'backslashreplace'`` error handler." +msgstr "" + +#: ../Doc/library/sys.rst:141 +msgid "" +"``sys.displayhook`` is called on the result of evaluating an :term:" +"`expression` entered in an interactive Python session. The display of these " +"values can be customized by assigning another one-argument function to ``sys." +"displayhook``." +msgstr "" + +#: ../Doc/library/sys.rst:145 +msgid "Pseudo-code::" +msgstr "" + +#: ../Doc/library/sys.rst:165 +msgid "Use ``'backslashreplace'`` error handler on :exc:`UnicodeEncodeError`." +msgstr "" + +#: ../Doc/library/sys.rst:171 +msgid "" +"If this is true, Python won't try to write ``.pyc`` files on the import of " +"source modules. This value is initially set to ``True`` or ``False`` " +"depending on the :option:`-B` command line option and the :envvar:" +"`PYTHONDONTWRITEBYTECODE` environment variable, but you can set it yourself " +"to control bytecode file generation." +msgstr "" + +#: ../Doc/library/sys.rst:180 +msgid "" +"This function prints out a given traceback and exception to ``sys.stderr``." +msgstr "" + +#: ../Doc/library/sys.rst:182 +msgid "" +"When an exception is raised and uncaught, the interpreter calls ``sys." +"excepthook`` with three arguments, the exception class, exception instance, " +"and a traceback object. In an interactive session this happens just before " +"control is returned to the prompt; in a Python program this happens just " +"before the program exits. The handling of such top-level exceptions can be " +"customized by assigning another three-argument function to ``sys." +"excepthook``." +msgstr "" + +#: ../Doc/library/sys.rst:193 +msgid "" +"These objects contain the original values of ``displayhook`` and " +"``excepthook`` at the start of the program. They are saved so that " +"``displayhook`` and ``excepthook`` can be restored in case they happen to " +"get replaced with broken objects." +msgstr "" + +#: ../Doc/library/sys.rst:201 +msgid "" +"This function returns a tuple of three values that give information about " +"the exception that is currently being handled. The information returned is " +"specific both to the current thread and to the current stack frame. If the " +"current stack frame is not handling an exception, the information is taken " +"from the calling stack frame, or its caller, and so on until a stack frame " +"is found that is handling an exception. Here, \"handling an exception\" is " +"defined as \"executing an except clause.\" For any stack frame, only " +"information about the exception being currently handled is accessible." +msgstr "" + +#: ../Doc/library/sys.rst:212 +msgid "" +"If no exception is being handled anywhere on the stack, a tuple containing " +"three ``None`` values is returned. Otherwise, the values returned are " +"``(type, value, traceback)``. Their meaning is: *type* gets the type of the " +"exception being handled (a subclass of :exc:`BaseException`); *value* gets " +"the exception instance (an instance of the exception type); *traceback* gets " +"a traceback object (see the Reference Manual) which encapsulates the call " +"stack at the point where the exception originally occurred." +msgstr "" + +#: ../Doc/library/sys.rst:223 +msgid "" +"A string giving the site-specific directory prefix where the platform-" +"dependent Python files are installed; by default, this is also ``'/usr/" +"local'``. This can be set at build time with the ``--exec-prefix`` argument " +"to the :program:`configure` script. Specifically, all configuration files " +"(e.g. the :file:`pyconfig.h` header file) are installed in the directory :" +"file:`{exec_prefix}/lib/python{X.Y}/config`, and shared library modules are " +"installed in :file:`{exec_prefix}/lib/python{X.Y}/lib-dynload`, where *X.Y* " +"is the version number of Python, for example ``3.2``." +msgstr "" + +#: ../Doc/library/sys.rst:234 +msgid "" +"If a :ref:`virtual environment ` is in effect, this value will be " +"changed in ``site.py`` to point to the virtual environment. The value for " +"the Python installation will still be available, via :data:" +"`base_exec_prefix`." +msgstr "" + +#: ../Doc/library/sys.rst:242 +msgid "" +"A string giving the absolute path of the executable binary for the Python " +"interpreter, on systems where this makes sense. If Python is unable to " +"retrieve the real path to its executable, :data:`sys.executable` will be an " +"empty string or ``None``." +msgstr "" + +#: ../Doc/library/sys.rst:250 +msgid "" +"Exit from Python. This is implemented by raising the :exc:`SystemExit` " +"exception, so cleanup actions specified by finally clauses of :keyword:`try` " +"statements are honored, and it is possible to intercept the exit attempt at " +"an outer level." +msgstr "" + +#: ../Doc/library/sys.rst:255 +msgid "" +"The optional argument *arg* can be an integer giving the exit status " +"(defaulting to zero), or another type of object. If it is an integer, zero " +"is considered \"successful termination\" and any nonzero value is considered " +"\"abnormal termination\" by shells and the like. Most systems require it to " +"be in the range 0--127, and produce undefined results otherwise. Some " +"systems have a convention for assigning specific meanings to specific exit " +"codes, but these are generally underdeveloped; Unix programs generally use 2 " +"for command line syntax errors and 1 for all other kind of errors. If " +"another type of object is passed, ``None`` is equivalent to passing zero, " +"and any other object is printed to :data:`stderr` and results in an exit " +"code of 1. In particular, ``sys.exit(\"some error message\")`` is a quick " +"way to exit a program when an error occurs." +msgstr "" + +#: ../Doc/library/sys.rst:268 +msgid "" +"Since :func:`exit` ultimately \"only\" raises an exception, it will only " +"exit the process when called from the main thread, and the exception is not " +"intercepted." +msgstr "" + +#: ../Doc/library/sys.rst:272 +msgid "" +"If an error occurs in the cleanup after the Python interpreter has caught :" +"exc:`SystemExit` (such as an error flushing buffered data in the standard " +"streams), the exit status is changed to 120." +msgstr "" + +#: ../Doc/library/sys.rst:280 +msgid "" +"The :term:`struct sequence` *flags* exposes the status of command line " +"flags. The attributes are read only." +msgstr "" + +#: ../Doc/library/sys.rst:284 ../Doc/library/sys.rst:322 +#: ../Doc/library/sys.rst:616 +msgid "attribute" +msgstr "" + +#: ../Doc/library/sys.rst:284 +msgid "flag" +msgstr "" + +#: ../Doc/library/sys.rst:286 +msgid ":const:`debug`" +msgstr "" + +#: ../Doc/library/sys.rst:286 +msgid ":option:`-d`" +msgstr "" + +#: ../Doc/library/sys.rst:287 +msgid ":const:`inspect`" +msgstr "" + +#: ../Doc/library/sys.rst:287 ../Doc/library/sys.rst:288 +msgid ":option:`-i`" +msgstr "" + +#: ../Doc/library/sys.rst:288 +msgid ":const:`interactive`" +msgstr "" + +#: ../Doc/library/sys.rst:289 +msgid ":const:`optimize`" +msgstr "" + +#: ../Doc/library/sys.rst:289 +msgid ":option:`-O` or :option:`-OO`" +msgstr "" + +#: ../Doc/library/sys.rst:290 +msgid ":const:`dont_write_bytecode`" +msgstr "" + +#: ../Doc/library/sys.rst:290 +msgid ":option:`-B`" +msgstr "" + +#: ../Doc/library/sys.rst:291 +msgid ":const:`no_user_site`" +msgstr "" + +#: ../Doc/library/sys.rst:291 +msgid ":option:`-s`" +msgstr "" + +#: ../Doc/library/sys.rst:292 +msgid ":const:`no_site`" +msgstr "" + +#: ../Doc/library/sys.rst:292 +msgid ":option:`-S`" +msgstr "" + +#: ../Doc/library/sys.rst:293 +msgid ":const:`ignore_environment`" +msgstr "" + +#: ../Doc/library/sys.rst:293 +msgid ":option:`-E`" +msgstr "" + +#: ../Doc/library/sys.rst:294 +msgid ":const:`verbose`" +msgstr "" + +#: ../Doc/library/sys.rst:294 +msgid ":option:`-v`" +msgstr "" + +#: ../Doc/library/sys.rst:295 +msgid ":const:`bytes_warning`" +msgstr "" + +#: ../Doc/library/sys.rst:295 +msgid ":option:`-b`" +msgstr "" + +#: ../Doc/library/sys.rst:296 +msgid ":const:`quiet`" +msgstr "" + +#: ../Doc/library/sys.rst:296 +msgid ":option:`-q`" +msgstr "" + +#: ../Doc/library/sys.rst:297 +msgid ":const:`hash_randomization`" +msgstr "" + +#: ../Doc/library/sys.rst:297 +msgid ":option:`-R`" +msgstr "" + +#: ../Doc/library/sys.rst:300 +msgid "Added ``quiet`` attribute for the new :option:`-q` flag." +msgstr "" + +#: ../Doc/library/sys.rst:303 +msgid "The ``hash_randomization`` attribute." +msgstr "" + +#: ../Doc/library/sys.rst:306 +msgid "Removed obsolete ``division_warning`` attribute." +msgstr "" + +#: ../Doc/library/sys.rst:312 +msgid "" +"A :term:`struct sequence` holding information about the float type. It " +"contains low level information about the precision and internal " +"representation. The values correspond to the various floating-point " +"constants defined in the standard header file :file:`float.h` for the 'C' " +"programming language; see section 5.2.4.2.2 of the 1999 ISO/IEC C standard " +"[C99]_, 'Characteristics of floating types', for details." +msgstr "" + +#: ../Doc/library/sys.rst:322 +msgid "float.h macro" +msgstr "" + +#: ../Doc/library/sys.rst:322 ../Doc/library/sys.rst:616 +msgid "explanation" +msgstr "" + +#: ../Doc/library/sys.rst:324 +msgid ":const:`epsilon`" +msgstr "" + +#: ../Doc/library/sys.rst:324 +msgid "DBL_EPSILON" +msgstr "" + +#: ../Doc/library/sys.rst:324 +msgid "" +"difference between 1 and the least value greater than 1 that is " +"representable as a float" +msgstr "" + +#: ../Doc/library/sys.rst:327 +msgid ":const:`dig`" +msgstr "" + +#: ../Doc/library/sys.rst:327 +msgid "DBL_DIG" +msgstr "" + +#: ../Doc/library/sys.rst:327 +msgid "" +"maximum number of decimal digits that can be faithfully represented in a " +"float; see below" +msgstr "" + +#: ../Doc/library/sys.rst:330 +msgid ":const:`mant_dig`" +msgstr "" + +#: ../Doc/library/sys.rst:330 +msgid "DBL_MANT_DIG" +msgstr "" + +#: ../Doc/library/sys.rst:330 +msgid "" +"float precision: the number of base-``radix`` digits in the significand of a " +"float" +msgstr "" + +#: ../Doc/library/sys.rst:333 +msgid ":const:`max`" +msgstr "" + +#: ../Doc/library/sys.rst:333 +msgid "DBL_MAX" +msgstr "" + +#: ../Doc/library/sys.rst:333 +msgid "maximum representable finite float" +msgstr "" + +#: ../Doc/library/sys.rst:335 +msgid ":const:`max_exp`" +msgstr "" + +#: ../Doc/library/sys.rst:335 +msgid "DBL_MAX_EXP" +msgstr "" + +#: ../Doc/library/sys.rst:335 +msgid "" +"maximum integer e such that ``radix**(e-1)`` is a representable finite float" +msgstr "" + +#: ../Doc/library/sys.rst:338 +msgid ":const:`max_10_exp`" +msgstr "" + +#: ../Doc/library/sys.rst:338 +msgid "DBL_MAX_10_EXP" +msgstr "" + +#: ../Doc/library/sys.rst:338 +msgid "" +"maximum integer e such that ``10**e`` is in the range of representable " +"finite floats" +msgstr "" + +#: ../Doc/library/sys.rst:341 +msgid ":const:`min`" +msgstr "" + +#: ../Doc/library/sys.rst:341 +msgid "DBL_MIN" +msgstr "" + +#: ../Doc/library/sys.rst:341 +msgid "minimum positive normalized float" +msgstr "" + +#: ../Doc/library/sys.rst:343 +msgid ":const:`min_exp`" +msgstr "" + +#: ../Doc/library/sys.rst:343 +msgid "DBL_MIN_EXP" +msgstr "" + +#: ../Doc/library/sys.rst:343 +msgid "minimum integer e such that ``radix**(e-1)`` is a normalized float" +msgstr "" + +#: ../Doc/library/sys.rst:346 +msgid ":const:`min_10_exp`" +msgstr "" + +#: ../Doc/library/sys.rst:346 +msgid "DBL_MIN_10_EXP" +msgstr "" + +#: ../Doc/library/sys.rst:346 +msgid "minimum integer e such that ``10**e`` is a normalized float" +msgstr "" + +#: ../Doc/library/sys.rst:349 +msgid ":const:`radix`" +msgstr "" + +#: ../Doc/library/sys.rst:349 +msgid "FLT_RADIX" +msgstr "" + +#: ../Doc/library/sys.rst:349 +msgid "radix of exponent representation" +msgstr "" + +#: ../Doc/library/sys.rst:351 +msgid ":const:`rounds`" +msgstr "" + +#: ../Doc/library/sys.rst:351 +msgid "FLT_ROUNDS" +msgstr "" + +#: ../Doc/library/sys.rst:351 +msgid "" +"integer constant representing the rounding mode used for arithmetic " +"operations. This reflects the value of the system FLT_ROUNDS macro at " +"interpreter startup time. See section 5.2.4.2.2 of the C99 standard for an " +"explanation of the possible values and their meanings." +msgstr "" + +#: ../Doc/library/sys.rst:359 +msgid "" +"The attribute :attr:`sys.float_info.dig` needs further explanation. If " +"``s`` is any string representing a decimal number with at most :attr:`sys." +"float_info.dig` significant digits, then converting ``s`` to a float and " +"back again will recover a string representing the same decimal value::" +msgstr "" + +#: ../Doc/library/sys.rst:372 +msgid "" +"But for strings with more than :attr:`sys.float_info.dig` significant " +"digits, this isn't always true::" +msgstr "" + +#: ../Doc/library/sys.rst:381 +msgid "" +"A string indicating how the :func:`repr` function behaves for floats. If " +"the string has value ``'short'`` then for a finite float ``x``, ``repr(x)`` " +"aims to produce a short string with the property that ``float(repr(x)) == " +"x``. This is the usual behaviour in Python 3.1 and later. Otherwise, " +"``float_repr_style`` has value ``'legacy'`` and ``repr(x)`` behaves in the " +"same way as it did in versions of Python prior to 3.1." +msgstr "" + +#: ../Doc/library/sys.rst:394 +msgid "" +"Return the number of memory blocks currently allocated by the interpreter, " +"regardless of their size. This function is mainly useful for tracking and " +"debugging memory leaks. Because of the interpreter's internal caches, the " +"result can vary from call to call; you may have to call :func:" +"`_clear_type_cache()` and :func:`gc.collect()` to get more predictable " +"results." +msgstr "" + +#: ../Doc/library/sys.rst:401 +msgid "" +"If a Python build or implementation cannot reasonably compute this " +"information, :func:`getallocatedblocks()` is allowed to return 0 instead." +msgstr "" + +#: ../Doc/library/sys.rst:409 +msgid "" +"Return the interpreter's \"check interval\"; see :func:`setcheckinterval`." +msgstr "" + +#: ../Doc/library/sys.rst:411 +msgid "Use :func:`getswitchinterval` instead." +msgstr "" + +#: ../Doc/library/sys.rst:417 +msgid "" +"Return the name of the current default string encoding used by the Unicode " +"implementation." +msgstr "" + +#: ../Doc/library/sys.rst:423 +msgid "" +"Return the current value of the flags that are used for :c:func:`dlopen` " +"calls. Symbolic names for the flag values can be found in the :mod:`os` " +"module (``RTLD_xxx`` constants, e.g. :data:`os.RTLD_LAZY`). Availability: " +"Unix." +msgstr "" + +#: ../Doc/library/sys.rst:431 +msgid "" +"Return the name of the encoding used to convert between Unicode filenames " +"and bytes filenames. For best compatibility, str should be used for " +"filenames in all cases, although representing filenames as bytes is also " +"supported. Functions accepting or returning filenames should support either " +"str or bytes and internally convert to the system's preferred representation." +msgstr "" + +#: ../Doc/library/sys.rst:438 +msgid "This encoding is always ASCII-compatible." +msgstr "" + +#: ../Doc/library/sys.rst:440 ../Doc/library/sys.rst:463 +msgid "" +":func:`os.fsencode` and :func:`os.fsdecode` should be used to ensure that " +"the correct encoding and errors mode are used." +msgstr "" + +#: ../Doc/library/sys.rst:443 +msgid "On Mac OS X, the encoding is ``'utf-8'``." +msgstr "" + +#: ../Doc/library/sys.rst:445 +msgid "On Unix, the encoding is the locale encoding." +msgstr "" + +#: ../Doc/library/sys.rst:447 +msgid "" +"On Windows, the encoding may be ``'utf-8'`` or ``'mbcs'``, depending on user " +"configuration." +msgstr "" + +#: ../Doc/library/sys.rst:450 +msgid ":func:`getfilesystemencoding` result cannot be ``None`` anymore." +msgstr "" + +#: ../Doc/library/sys.rst:453 +msgid "" +"Windows is no longer guaranteed to return ``'mbcs'``. See :pep:`529` and :" +"func:`_enablelegacywindowsfsencoding` for more information." +msgstr "" + +#: ../Doc/library/sys.rst:459 +msgid "" +"Return the name of the error mode used to convert between Unicode filenames " +"and bytes filenames. The encoding name is returned from :func:" +"`getfilesystemencoding`." +msgstr "" + +#: ../Doc/library/sys.rst:470 +msgid "" +"Return the reference count of the *object*. The count returned is generally " +"one higher than you might expect, because it includes the (temporary) " +"reference as an argument to :func:`getrefcount`." +msgstr "" + +#: ../Doc/library/sys.rst:477 +msgid "" +"Return the current value of the recursion limit, the maximum depth of the " +"Python interpreter stack. This limit prevents infinite recursion from " +"causing an overflow of the C stack and crashing Python. It can be set by :" +"func:`setrecursionlimit`." +msgstr "" + +#: ../Doc/library/sys.rst:485 +msgid "" +"Return the size of an object in bytes. The object can be any type of object. " +"All built-in objects will return correct results, but this does not have to " +"hold true for third-party extensions as it is implementation specific." +msgstr "" + +#: ../Doc/library/sys.rst:490 +msgid "" +"Only the memory consumption directly attributed to the object is accounted " +"for, not the memory consumption of objects it refers to." +msgstr "" + +#: ../Doc/library/sys.rst:493 +msgid "" +"If given, *default* will be returned if the object does not provide means to " +"retrieve the size. Otherwise a :exc:`TypeError` will be raised." +msgstr "" + +#: ../Doc/library/sys.rst:496 +msgid "" +":func:`getsizeof` calls the object's ``__sizeof__`` method and adds an " +"additional garbage collector overhead if the object is managed by the " +"garbage collector." +msgstr "" + +#: ../Doc/library/sys.rst:500 +msgid "" +"See `recursive sizeof recipe `_ " +"for an example of using :func:`getsizeof` recursively to find the size of " +"containers and all their contents." +msgstr "" + +#: ../Doc/library/sys.rst:506 +msgid "" +"Return the interpreter's \"thread switch interval\"; see :func:" +"`setswitchinterval`." +msgstr "" + +#: ../Doc/library/sys.rst:514 +msgid "" +"Return a frame object from the call stack. If optional integer *depth* is " +"given, return the frame object that many calls below the top of the stack. " +"If that is deeper than the call stack, :exc:`ValueError` is raised. The " +"default for *depth* is zero, returning the frame at the top of the call " +"stack." +msgstr "" + +#: ../Doc/library/sys.rst:521 +msgid "" +"This function should be used for internal and specialized purposes only. It " +"is not guaranteed to exist in all implementations of Python." +msgstr "" + +#: ../Doc/library/sys.rst:531 +msgid "Get the profiler function as set by :func:`setprofile`." +msgstr "" + +#: ../Doc/library/sys.rst:540 +msgid "Get the trace function as set by :func:`settrace`." +msgstr "" + +#: ../Doc/library/sys.rst:544 +msgid "" +"The :func:`gettrace` function is intended only for implementing debuggers, " +"profilers, coverage tools and the like. Its behavior is part of the " +"implementation platform, rather than part of the language definition, and " +"thus may not be available in all Python implementations." +msgstr "" + +#: ../Doc/library/sys.rst:552 +msgid "" +"Return a named tuple describing the Windows version currently running. The " +"named elements are *major*, *minor*, *build*, *platform*, *service_pack*, " +"*service_pack_minor*, *service_pack_major*, *suite_mask*, *product_type* and " +"*platform_version*. *service_pack* contains a string, *platform_version* a 3-" +"tuple and all other values are integers. The components can also be accessed " +"by name, so ``sys.getwindowsversion()[0]`` is equivalent to ``sys." +"getwindowsversion().major``. For compatibility with prior versions, only the " +"first 5 elements are retrievable by indexing." +msgstr "" + +#: ../Doc/library/sys.rst:563 +msgid "*platform* will be :const:`2 (VER_PLATFORM_WIN32_NT)`." +msgstr "" + +#: ../Doc/library/sys.rst:565 +msgid "*product_type* may be one of the following values:" +msgstr "" + +#: ../Doc/library/sys.rst:570 +msgid ":const:`1 (VER_NT_WORKSTATION)`" +msgstr "" + +#: ../Doc/library/sys.rst:570 +msgid "The system is a workstation." +msgstr "" + +#: ../Doc/library/sys.rst:572 +msgid ":const:`2 (VER_NT_DOMAIN_CONTROLLER)`" +msgstr "" + +#: ../Doc/library/sys.rst:572 +msgid "The system is a domain controller." +msgstr "" + +#: ../Doc/library/sys.rst:575 +msgid ":const:`3 (VER_NT_SERVER)`" +msgstr "" + +#: ../Doc/library/sys.rst:575 +msgid "The system is a server, but not a domain controller." +msgstr "" + +#: ../Doc/library/sys.rst:579 +msgid "" +"This function wraps the Win32 :c:func:`GetVersionEx` function; see the " +"Microsoft documentation on :c:func:`OSVERSIONINFOEX` for more information " +"about these fields." +msgstr "" + +#: ../Doc/library/sys.rst:583 +msgid "" +"*platform_version* returns the accurate major version, minor version and " +"build number of the current operating system, rather than the version that " +"is being emulated for the process. It is intended for use in logging rather " +"than for feature detection." +msgstr "" + +#: ../Doc/library/sys.rst:590 +msgid "" +"Changed to a named tuple and added *service_pack_minor*, " +"*service_pack_major*, *suite_mask*, and *product_type*." +msgstr "" + +#: ../Doc/library/sys.rst:594 +msgid "Added *platform_version*" +msgstr "" + +#: ../Doc/library/sys.rst:599 +msgid "Returns ``None``, or a wrapper set by :func:`set_coroutine_wrapper`." +msgstr "" + +#: ../Doc/library/sys.rst:601 ../Doc/library/sys.rst:1134 +msgid "See :pep:`492` for more details." +msgstr "" + +#: ../Doc/library/sys.rst:605 ../Doc/library/sys.rst:1138 +msgid "" +"This function has been added on a provisional basis (see :pep:`411` for " +"details.) Use it only for debugging purposes." +msgstr "" + +#: ../Doc/library/sys.rst:611 +msgid "" +"A :term:`struct sequence` giving parameters of the numeric hash " +"implementation. For more details about hashing of numeric types, see :ref:" +"`numeric-hash`." +msgstr "" + +#: ../Doc/library/sys.rst:618 +msgid ":const:`width`" +msgstr "" + +#: ../Doc/library/sys.rst:618 +msgid "width in bits used for hash values" +msgstr "" + +#: ../Doc/library/sys.rst:620 +msgid ":const:`modulus`" +msgstr "" + +#: ../Doc/library/sys.rst:620 +msgid "prime modulus P used for numeric hash scheme" +msgstr "" + +#: ../Doc/library/sys.rst:622 +msgid ":const:`inf`" +msgstr "" + +#: ../Doc/library/sys.rst:622 +msgid "hash value returned for a positive infinity" +msgstr "" + +#: ../Doc/library/sys.rst:624 +msgid ":const:`nan`" +msgstr "" + +#: ../Doc/library/sys.rst:624 +msgid "hash value returned for a nan" +msgstr "" + +#: ../Doc/library/sys.rst:626 +msgid ":const:`imag`" +msgstr "" + +#: ../Doc/library/sys.rst:626 +msgid "multiplier used for the imaginary part of a complex number" +msgstr "" + +#: ../Doc/library/sys.rst:629 +msgid ":const:`algorithm`" +msgstr "" + +#: ../Doc/library/sys.rst:629 +msgid "name of the algorithm for hashing of str, bytes, and memoryview" +msgstr "" + +#: ../Doc/library/sys.rst:632 +msgid ":const:`hash_bits`" +msgstr "" + +#: ../Doc/library/sys.rst:632 +msgid "internal output size of the hash algorithm" +msgstr "" + +#: ../Doc/library/sys.rst:634 +msgid ":const:`seed_bits`" +msgstr "" + +#: ../Doc/library/sys.rst:634 +msgid "size of the seed key of the hash algorithm" +msgstr "" + +#: ../Doc/library/sys.rst:640 +msgid "Added *algorithm*, *hash_bits* and *seed_bits*" +msgstr "" + +#: ../Doc/library/sys.rst:646 +msgid "" +"The version number encoded as a single integer. This is guaranteed to " +"increase with each version, including proper support for non-production " +"releases. For example, to test that the Python interpreter is at least " +"version 1.5.2, use::" +msgstr "" + +#: ../Doc/library/sys.rst:657 +msgid "" +"This is called ``hexversion`` since it only really looks meaningful when " +"viewed as the result of passing it to the built-in :func:`hex` function. " +"The :term:`struct sequence` :data:`sys.version_info` may be used for a more " +"human-friendly encoding of the same information." +msgstr "" + +#: ../Doc/library/sys.rst:662 +msgid "More details of ``hexversion`` can be found at :ref:`apiabiversion`." +msgstr "" + +#: ../Doc/library/sys.rst:667 +msgid "" +"An object containing information about the implementation of the currently " +"running Python interpreter. The following attributes are required to exist " +"in all Python implementations." +msgstr "" + +#: ../Doc/library/sys.rst:671 +msgid "" +"*name* is the implementation's identifier, e.g. ``'cpython'``. The actual " +"string is defined by the Python implementation, but it is guaranteed to be " +"lower case." +msgstr "" + +#: ../Doc/library/sys.rst:675 +msgid "" +"*version* is a named tuple, in the same format as :data:`sys.version_info`. " +"It represents the version of the Python *implementation*. This has a " +"distinct meaning from the specific version of the Python *language* to which " +"the currently running interpreter conforms, which ``sys.version_info`` " +"represents. For example, for PyPy 1.8 ``sys.implementation.version`` might " +"be ``sys.version_info(1, 8, 0, 'final', 0)``, whereas ``sys.version_info`` " +"would be ``sys.version_info(2, 7, 2, 'final', 0)``. For CPython they are " +"the same value, since it is the reference implementation." +msgstr "" + +#: ../Doc/library/sys.rst:685 +msgid "" +"*hexversion* is the implementation version in hexadecimal format, like :data:" +"`sys.hexversion`." +msgstr "" + +#: ../Doc/library/sys.rst:688 +msgid "" +"*cache_tag* is the tag used by the import machinery in the filenames of " +"cached modules. By convention, it would be a composite of the " +"implementation's name and version, like ``'cpython-33'``. However, a Python " +"implementation may use some other value if appropriate. If ``cache_tag`` is " +"set to ``None``, it indicates that module caching should be disabled." +msgstr "" + +#: ../Doc/library/sys.rst:695 +msgid "" +":data:`sys.implementation` may contain additional attributes specific to the " +"Python implementation. These non-standard attributes must start with an " +"underscore, and are not described here. Regardless of its contents, :data:" +"`sys.implementation` will not change during a run of the interpreter, nor " +"between implementation versions. (It may change between Python language " +"versions, however.) See :pep:`421` for more information." +msgstr "" + +#: ../Doc/library/sys.rst:707 +msgid "" +"A :term:`struct sequence` that holds information about Python's internal " +"representation of integers. The attributes are read only." +msgstr "" + +#: ../Doc/library/sys.rst:715 +msgid ":const:`bits_per_digit`" +msgstr "" + +#: ../Doc/library/sys.rst:715 +msgid "" +"number of bits held in each digit. Python integers are stored internally in " +"base ``2**int_info.bits_per_digit``" +msgstr "" + +#: ../Doc/library/sys.rst:719 +msgid ":const:`sizeof_digit`" +msgstr "" + +#: ../Doc/library/sys.rst:719 +msgid "size in bytes of the C type used to represent a digit" +msgstr "" + +#: ../Doc/library/sys.rst:728 +msgid "" +"When this attribute exists, its value is automatically called (with no " +"arguments) when the interpreter is launched in :ref:`interactive mode `. This is done after the :envvar:`PYTHONSTARTUP` file is read, " +"so that you can set this hook there. The :mod:`site` module :ref:`sets this " +"`." +msgstr "" + +#: ../Doc/library/sys.rst:739 +msgid "" +"Enter *string* in the table of \"interned\" strings and return the interned " +"string -- which is *string* itself or a copy. Interning strings is useful to " +"gain a little performance on dictionary lookup -- if the keys in a " +"dictionary are interned, and the lookup key is interned, the key comparisons " +"(after hashing) can be done by a pointer compare instead of a string " +"compare. Normally, the names used in Python programs are automatically " +"interned, and the dictionaries used to hold module, class or instance " +"attributes have interned keys." +msgstr "" + +#: ../Doc/library/sys.rst:747 +msgid "" +"Interned strings are not immortal; you must keep a reference to the return " +"value of :func:`intern` around to benefit from it." +msgstr "" + +#: ../Doc/library/sys.rst:753 +msgid "" +"Return :const:`True` if the Python interpreter is :term:`shutting down " +"`, :const:`False` otherwise." +msgstr "" + +#: ../Doc/library/sys.rst:763 +msgid "" +"These three variables are not always defined; they are set when an exception " +"is not handled and the interpreter prints an error message and a stack " +"traceback. Their intended use is to allow an interactive user to import a " +"debugger module and engage in post-mortem debugging without having to re-" +"execute the command that caused the error. (Typical use is ``import pdb; " +"pdb.pm()`` to enter the post-mortem debugger; see :mod:`pdb` module for more " +"information.)" +msgstr "" + +#: ../Doc/library/sys.rst:771 +msgid "" +"The meaning of the variables is the same as that of the return values from :" +"func:`exc_info` above." +msgstr "" + +#: ../Doc/library/sys.rst:777 +msgid "" +"An integer giving the maximum value a variable of type :c:type:`Py_ssize_t` " +"can take. It's usually ``2**31 - 1`` on a 32-bit platform and ``2**63 - 1`` " +"on a 64-bit platform." +msgstr "" + +#: ../Doc/library/sys.rst:784 +msgid "" +"An integer giving the value of the largest Unicode code point, i.e. " +"``1114111`` (``0x10FFFF`` in hexadecimal)." +msgstr "" + +#: ../Doc/library/sys.rst:787 +msgid "" +"Before :pep:`393`, ``sys.maxunicode`` used to be either ``0xFFFF`` or " +"``0x10FFFF``, depending on the configuration option that specified whether " +"Unicode characters were stored as UCS-2 or UCS-4." +msgstr "" + +#: ../Doc/library/sys.rst:795 +msgid "" +"A list of :term:`meta path finder` objects that have their :meth:`~importlib." +"abc.MetaPathFinder.find_spec` methods called to see if one of the objects " +"can find the module to be imported. The :meth:`~importlib.abc.MetaPathFinder." +"find_spec` method is called with at least the absolute name of the module " +"being imported. If the module to be imported is contained in a package, then " +"the parent package's :attr:`__path__` attribute is passed in as a second " +"argument. The method returns a :term:`module spec`, or ``None`` if the " +"module cannot be found." +msgstr "" + +#: ../Doc/library/sys.rst:807 +msgid ":class:`importlib.abc.MetaPathFinder`" +msgstr "" + +#: ../Doc/library/sys.rst:807 +msgid "" +"The abstract base class defining the interface of finder objects on :data:" +"`meta_path`." +msgstr "" + +#: ../Doc/library/sys.rst:811 +msgid ":class:`importlib.machinery.ModuleSpec`" +msgstr "" + +#: ../Doc/library/sys.rst:810 +msgid "" +"The concrete class which :meth:`~importlib.abc.MetaPathFinder.find_spec` " +"should return instances of." +msgstr "" + +#: ../Doc/library/sys.rst:816 +msgid "" +":term:`Module specs ` were introduced in Python 3.4, by :pep:" +"`451`. Earlier versions of Python looked for a method called :meth:" +"`~importlib.abc.MetaPathFinder.find_module`. This is still called as a " +"fallback if a :data:`meta_path` entry doesn't have a :meth:`~importlib.abc." +"MetaPathFinder.find_spec` method." +msgstr "" + +#: ../Doc/library/sys.rst:824 +msgid "" +"This is a dictionary that maps module names to modules which have already " +"been loaded. This can be manipulated to force reloading of modules and " +"other tricks. However, replacing the dictionary will not necessarily work as " +"expected and deleting essential items from the dictionary may cause Python " +"to fail." +msgstr "" + +#: ../Doc/library/sys.rst:834 +msgid "" +"A list of strings that specifies the search path for modules. Initialized " +"from the environment variable :envvar:`PYTHONPATH`, plus an installation-" +"dependent default." +msgstr "" + +#: ../Doc/library/sys.rst:838 +msgid "" +"As initialized upon program startup, the first item of this list, " +"``path[0]``, is the directory containing the script that was used to invoke " +"the Python interpreter. If the script directory is not available (e.g. if " +"the interpreter is invoked interactively or if the script is read from " +"standard input), ``path[0]`` is the empty string, which directs Python to " +"search modules in the current directory first. Notice that the script " +"directory is inserted *before* the entries inserted as a result of :envvar:" +"`PYTHONPATH`." +msgstr "" + +#: ../Doc/library/sys.rst:846 +msgid "" +"A program is free to modify this list for its own purposes. Only strings " +"and bytes should be added to :data:`sys.path`; all other data types are " +"ignored during import." +msgstr "" + +#: ../Doc/library/sys.rst:852 +msgid "" +"Module :mod:`site` This describes how to use .pth files to extend :data:`sys." +"path`." +msgstr "" + +#: ../Doc/library/sys.rst:858 +msgid "" +"A list of callables that take a path argument to try to create a :term:" +"`finder` for the path. If a finder can be created, it is to be returned by " +"the callable, else raise :exc:`ImportError`." +msgstr "" + +#: ../Doc/library/sys.rst:862 ../Doc/library/sys.rst:873 +msgid "Originally specified in :pep:`302`." +msgstr "" + +#: ../Doc/library/sys.rst:867 +msgid "" +"A dictionary acting as a cache for :term:`finder` objects. The keys are " +"paths that have been passed to :data:`sys.path_hooks` and the values are the " +"finders that are found. If a path is a valid file system path but no finder " +"is found on :data:`sys.path_hooks` then ``None`` is stored." +msgstr "" + +#: ../Doc/library/sys.rst:875 +msgid "" +"``None`` is stored instead of :class:`imp.NullImporter` when no finder is " +"found." +msgstr "" + +#: ../Doc/library/sys.rst:882 +msgid "" +"This string contains a platform identifier that can be used to append " +"platform-specific components to :data:`sys.path`, for instance." +msgstr "" + +#: ../Doc/library/sys.rst:885 +msgid "" +"For Unix systems, except on Linux, this is the lowercased OS name as " +"returned by ``uname -s`` with the first part of the version as returned by " +"``uname -r`` appended, e.g. ``'sunos5'`` or ``'freebsd8'``, *at the time " +"when Python was built*. Unless you want to test for a specific system " +"version, it is therefore recommended to use the following idiom::" +msgstr "" + +#: ../Doc/library/sys.rst:896 +msgid "For other systems, the values are:" +msgstr "" + +#: ../Doc/library/sys.rst:899 +msgid "System" +msgstr "" + +#: ../Doc/library/sys.rst:899 +msgid "``platform`` value" +msgstr "" + +#: ../Doc/library/sys.rst:901 +msgid "Linux" +msgstr "" + +#: ../Doc/library/sys.rst:901 +msgid "``'linux'``" +msgstr "" + +#: ../Doc/library/sys.rst:902 +msgid "``'win32'``" +msgstr "" + +#: ../Doc/library/sys.rst:903 +msgid "Windows/Cygwin" +msgstr "" + +#: ../Doc/library/sys.rst:903 +msgid "``'cygwin'``" +msgstr "" + +#: ../Doc/library/sys.rst:904 +msgid "``'darwin'``" +msgstr "" + +#: ../Doc/library/sys.rst:907 +msgid "" +"On Linux, :attr:`sys.platform` doesn't contain the major version anymore. It " +"is always ``'linux'``, instead of ``'linux2'`` or ``'linux3'``. Since older " +"Python versions include the version number, it is recommended to always use " +"the ``startswith`` idiom presented above." +msgstr "" + +#: ../Doc/library/sys.rst:915 +msgid "" +":attr:`os.name` has a coarser granularity. :func:`os.uname` gives system-" +"dependent version information." +msgstr "" + +#: ../Doc/library/sys.rst:924 +msgid "" +"A string giving the site-specific directory prefix where the platform " +"independent Python files are installed; by default, this is the string ``'/" +"usr/local'``. This can be set at build time with the ``--prefix`` argument " +"to the :program:`configure` script. The main collection of Python library " +"modules is installed in the directory :file:`{prefix}/lib/python{X.Y}` while " +"the platform independent header files (all except :file:`pyconfig.h`) are " +"stored in :file:`{prefix}/include/python{X.Y}`, where *X.Y* is the version " +"number of Python, for example ``3.2``." +msgstr "" + +#: ../Doc/library/sys.rst:933 +msgid "" +"If a :ref:`virtual environment ` is in effect, this value will be " +"changed in ``site.py`` to point to the virtual environment. The value for " +"the Python installation will still be available, via :data:`base_prefix`." +msgstr "" + +#: ../Doc/library/sys.rst:946 +msgid "" +"Strings specifying the primary and secondary prompt of the interpreter. " +"These are only defined if the interpreter is in interactive mode. Their " +"initial values in this case are ``'>>> '`` and ``'... '``. If a non-string " +"object is assigned to either variable, its :func:`str` is re-evaluated each " +"time the interpreter prepares to read a new interactive command; this can be " +"used to implement a dynamic prompt." +msgstr "" + +#: ../Doc/library/sys.rst:956 +msgid "" +"Set the interpreter's \"check interval\". This integer value determines how " +"often the interpreter checks for periodic things such as thread switches and " +"signal handlers. The default is ``100``, meaning the check is performed " +"every 100 Python virtual instructions. Setting it to a larger value may " +"increase performance for programs using threads. Setting it to a value " +"``<=`` 0 checks every virtual instruction, maximizing responsiveness as well " +"as overhead." +msgstr "" + +#: ../Doc/library/sys.rst:963 +msgid "" +"This function doesn't have an effect anymore, as the internal logic for " +"thread switching and asynchronous tasks has been rewritten. Use :func:" +"`setswitchinterval` instead." +msgstr "" + +#: ../Doc/library/sys.rst:971 +msgid "" +"Set the flags used by the interpreter for :c:func:`dlopen` calls, such as " +"when the interpreter loads extension modules. Among other things, this will " +"enable a lazy resolving of symbols when importing a module, if called as " +"``sys.setdlopenflags(0)``. To share symbols across extension modules, call " +"as ``sys.setdlopenflags(os.RTLD_GLOBAL)``. Symbolic names for the flag " +"values can be found in the :mod:`os` module (``RTLD_xxx`` constants, e.g. :" +"data:`os.RTLD_LAZY`)." +msgstr "" + +#: ../Doc/library/sys.rst:987 +msgid "" +"Set the system's profile function, which allows you to implement a Python " +"source code profiler in Python. See chapter :ref:`profile` for more " +"information on the Python profiler. The system's profile function is called " +"similarly to the system's trace function (see :func:`settrace`), but it " +"isn't called for each executed line of code (only on call and return, but " +"the return event is reported even when an exception has been set). The " +"function is thread-specific, but there is no way for the profiler to know " +"about context switches between threads, so it does not make sense to use " +"this in the presence of multiple threads. Also, its return value is not " +"used, so it can simply return ``None``." +msgstr "" + +#: ../Doc/library/sys.rst:1000 +msgid "" +"Set the maximum depth of the Python interpreter stack to *limit*. This " +"limit prevents infinite recursion from causing an overflow of the C stack " +"and crashing Python." +msgstr "" + +#: ../Doc/library/sys.rst:1004 +msgid "" +"The highest possible limit is platform-dependent. A user may need to set " +"the limit higher when they have a program that requires deep recursion and a " +"platform that supports a higher limit. This should be done with care, " +"because a too-high limit can lead to a crash." +msgstr "" + +#: ../Doc/library/sys.rst:1009 +msgid "" +"If the new limit is too low at the current recursion depth, a :exc:" +"`RecursionError` exception is raised." +msgstr "" + +#: ../Doc/library/sys.rst:1012 +msgid "" +"A :exc:`RecursionError` exception is now raised if the new limit is too low " +"at the current recursion depth." +msgstr "" + +#: ../Doc/library/sys.rst:1019 +msgid "" +"Set the interpreter's thread switch interval (in seconds). This floating-" +"point value determines the ideal duration of the \"timeslices\" allocated to " +"concurrently running Python threads. Please note that the actual value can " +"be higher, especially if long-running internal functions or methods are " +"used. Also, which thread becomes scheduled at the end of the interval is " +"the operating system's decision. The interpreter doesn't have its own " +"scheduler." +msgstr "" + +#: ../Doc/library/sys.rst:1036 +msgid "" +"Set the system's trace function, which allows you to implement a Python " +"source code debugger in Python. The function is thread-specific; for a " +"debugger to support multiple threads, it must be registered using :func:" +"`settrace` for each thread being debugged." +msgstr "" + +#: ../Doc/library/sys.rst:1041 +msgid "" +"Trace functions should have three arguments: *frame*, *event*, and *arg*. " +"*frame* is the current stack frame. *event* is a string: ``'call'``, " +"``'line'``, ``'return'``, ``'exception'``, ``'c_call'``, ``'c_return'``, or " +"``'c_exception'``. *arg* depends on the event type." +msgstr "" + +#: ../Doc/library/sys.rst:1046 +msgid "" +"The trace function is invoked (with *event* set to ``'call'``) whenever a " +"new local scope is entered; it should return a reference to a local trace " +"function to be used that scope, or ``None`` if the scope shouldn't be traced." +msgstr "" + +#: ../Doc/library/sys.rst:1050 +msgid "" +"The local trace function should return a reference to itself (or to another " +"function for further tracing in that scope), or ``None`` to turn off tracing " +"in that scope." +msgstr "" + +#: ../Doc/library/sys.rst:1054 +msgid "The events have the following meaning:" +msgstr "" + +#: ../Doc/library/sys.rst:1059 +msgid "``'call'``" +msgstr "" + +#: ../Doc/library/sys.rst:1057 +msgid "" +"A function is called (or some other code block entered). The global trace " +"function is called; *arg* is ``None``; the return value specifies the local " +"trace function." +msgstr "" + +#: ../Doc/library/sys.rst:1062 +msgid "" +"The interpreter is about to execute a new line of code or re-execute the " +"condition of a loop. The local trace function is called; *arg* is ``None``; " +"the return value specifies the new local trace function. See :file:`Objects/" +"lnotab_notes.txt` for a detailed explanation of how this works." +msgstr "" + +#: ../Doc/library/sys.rst:1072 +msgid "``'return'``" +msgstr "" + +#: ../Doc/library/sys.rst:1069 +msgid "" +"A function (or other code block) is about to return. The local trace " +"function is called; *arg* is the value that will be returned, or ``None`` if " +"the event is caused by an exception being raised. The trace function's " +"return value is ignored." +msgstr "" + +#: ../Doc/library/sys.rst:1077 +msgid "``'exception'``" +msgstr "" + +#: ../Doc/library/sys.rst:1075 +msgid "" +"An exception has occurred. The local trace function is called; *arg* is a " +"tuple ``(exception, value, traceback)``; the return value specifies the new " +"local trace function." +msgstr "" + +#: ../Doc/library/sys.rst:1081 +msgid "``'c_call'``" +msgstr "" + +#: ../Doc/library/sys.rst:1080 +msgid "" +"A C function is about to be called. This may be an extension function or a " +"built-in. *arg* is the C function object." +msgstr "" + +#: ../Doc/library/sys.rst:1084 +msgid "``'c_return'``" +msgstr "" + +#: ../Doc/library/sys.rst:1084 +msgid "A C function has returned. *arg* is the C function object." +msgstr "" + +#: ../Doc/library/sys.rst:1087 +msgid "``'c_exception'``" +msgstr "" + +#: ../Doc/library/sys.rst:1087 +msgid "A C function has raised an exception. *arg* is the C function object." +msgstr "" + +#: ../Doc/library/sys.rst:1089 +msgid "" +"Note that as an exception is propagated down the chain of callers, an " +"``'exception'`` event is generated at each level." +msgstr "" + +#: ../Doc/library/sys.rst:1092 +msgid "For more information on code and frame objects, refer to :ref:`types`." +msgstr "" + +#: ../Doc/library/sys.rst:1096 +msgid "" +"The :func:`settrace` function is intended only for implementing debuggers, " +"profilers, coverage tools and the like. Its behavior is part of the " +"implementation platform, rather than part of the language definition, and " +"thus may not be available in all Python implementations." +msgstr "" + +#: ../Doc/library/sys.rst:1104 +msgid "" +"Allows intercepting creation of :term:`coroutine` objects (only ones that " +"are created by an :keyword:`async def` function; generators decorated with :" +"func:`types.coroutine` or :func:`asyncio.coroutine` will not be intercepted)." +msgstr "" + +#: ../Doc/library/sys.rst:1109 +msgid "The *wrapper* argument must be either:" +msgstr "" + +#: ../Doc/library/sys.rst:1111 +msgid "a callable that accepts one argument (a coroutine object);" +msgstr "" + +#: ../Doc/library/sys.rst:1112 +msgid "``None``, to reset the wrapper." +msgstr "" + +#: ../Doc/library/sys.rst:1114 +msgid "" +"If called twice, the new wrapper replaces the previous one. The function is " +"thread-specific." +msgstr "" + +#: ../Doc/library/sys.rst:1117 +msgid "" +"The *wrapper* callable cannot define new coroutines directly or indirectly::" +msgstr "" + +#: ../Doc/library/sys.rst:1132 +msgid "See also :func:`get_coroutine_wrapper`." +msgstr "" + +#: ../Doc/library/sys.rst:1143 +msgid "" +"Changes the default filesystem encoding and errors mode to 'mbcs' and " +"'replace' respectively, for consistency with versions of Python prior to 3.6." +msgstr "" + +#: ../Doc/library/sys.rst:1146 +msgid "" +"This is equivalent to defining the :envvar:`PYTHONLEGACYWINDOWSFSENCODING` " +"environment variable before launching Python." +msgstr "" + +#: ../Doc/library/sys.rst:1149 +msgid "Availability: Windows" +msgstr "" + +#: ../Doc/library/sys.rst:1151 +msgid "See :pep:`529` for more details." +msgstr "" + +#: ../Doc/library/sys.rst:1158 +msgid "" +":term:`File objects ` used by the interpreter for standard " +"input, output and errors:" +msgstr "" + +#: ../Doc/library/sys.rst:1161 +msgid "" +"``stdin`` is used for all interactive input (including calls to :func:" +"`input`);" +msgstr "" + +#: ../Doc/library/sys.rst:1163 +msgid "" +"``stdout`` is used for the output of :func:`print` and :term:`expression` " +"statements and for the prompts of :func:`input`;" +msgstr "" + +#: ../Doc/library/sys.rst:1165 +msgid "The interpreter's own prompts and its error messages go to ``stderr``." +msgstr "" + +#: ../Doc/library/sys.rst:1167 +msgid "" +"These streams are regular :term:`text files ` like those returned " +"by the :func:`open` function. Their parameters are chosen as follows:" +msgstr "" + +#: ../Doc/library/sys.rst:1171 +msgid "" +"The character encoding is platform-dependent. Under Windows, if the stream " +"is interactive (that is, if its :meth:`isatty` method returns ``True``), the " +"console codepage is used, otherwise the ANSI code page. Under other " +"platforms, the locale encoding is used (see :meth:`locale." +"getpreferredencoding`)." +msgstr "" + +#: ../Doc/library/sys.rst:1176 +msgid "" +"Under all platforms though, you can override this value by setting the :" +"envvar:`PYTHONIOENCODING` environment variable before starting Python." +msgstr "" + +#: ../Doc/library/sys.rst:1179 +msgid "" +"When interactive, standard streams are line-buffered. Otherwise, they are " +"block-buffered like regular text files. You can override this value with " +"the :option:`-u` command-line option." +msgstr "" + +#: ../Doc/library/sys.rst:1185 +msgid "" +"To write or read binary data from/to the standard streams, use the " +"underlying binary :data:`~io.TextIOBase.buffer` object. For example, to " +"write bytes to :data:`stdout`, use ``sys.stdout.buffer.write(b'abc')``." +msgstr "" + +#: ../Doc/library/sys.rst:1189 +msgid "" +"However, if you are writing a library (and do not control in which context " +"its code will be executed), be aware that the standard streams may be " +"replaced with file-like objects like :class:`io.StringIO` which do not " +"support the :attr:`~io.BufferedIOBase.buffer` attribute." +msgstr "" + +#: ../Doc/library/sys.rst:1199 +msgid "" +"These objects contain the original values of ``stdin``, ``stderr`` and " +"``stdout`` at the start of the program. They are used during finalization, " +"and could be useful to print to the actual standard stream no matter if the " +"``sys.std*`` object has been redirected." +msgstr "" + +#: ../Doc/library/sys.rst:1204 +msgid "" +"It can also be used to restore the actual files to known working file " +"objects in case they have been overwritten with a broken object. However, " +"the preferred way to do this is to explicitly save the previous stream " +"before replacing it, and restore the saved object." +msgstr "" + +#: ../Doc/library/sys.rst:1210 +msgid "" +"Under some conditions ``stdin``, ``stdout`` and ``stderr`` as well as the " +"original values ``__stdin__``, ``__stdout__`` and ``__stderr__`` can be " +"None. It is usually the case for Windows GUI apps that aren't connected to a " +"console and Python apps started with :program:`pythonw`." +msgstr "" + +#: ../Doc/library/sys.rst:1218 +msgid "" +"A :term:`struct sequence` holding information about the thread " +"implementation." +msgstr "" + +#: ../Doc/library/sys.rst:1226 +msgid ":const:`name`" +msgstr "" + +#: ../Doc/library/sys.rst:1226 +msgid "Name of the thread implementation:" +msgstr "" + +#: ../Doc/library/sys.rst:1228 +msgid "``'nt'``: Windows threads" +msgstr "" + +#: ../Doc/library/sys.rst:1229 +msgid "``'pthread'``: POSIX threads" +msgstr "" + +#: ../Doc/library/sys.rst:1230 +msgid "``'solaris'``: Solaris threads" +msgstr "" + +#: ../Doc/library/sys.rst:1232 +msgid ":const:`lock`" +msgstr "" + +#: ../Doc/library/sys.rst:1232 +msgid "Name of the lock implementation:" +msgstr "" + +#: ../Doc/library/sys.rst:1234 +msgid "``'semaphore'``: a lock uses a semaphore" +msgstr "" + +#: ../Doc/library/sys.rst:1235 +msgid "``'mutex+cond'``: a lock uses a mutex and a condition variable" +msgstr "" + +#: ../Doc/library/sys.rst:1237 +msgid "``None`` if this information is unknown" +msgstr "" + +#: ../Doc/library/sys.rst:1239 +msgid ":const:`version`" +msgstr "" + +#: ../Doc/library/sys.rst:1239 +msgid "" +"Name and version of the thread library. It is a string, or ``None`` if these " +"informations are unknown." +msgstr "" + +#: ../Doc/library/sys.rst:1248 +msgid "" +"When this variable is set to an integer value, it determines the maximum " +"number of levels of traceback information printed when an unhandled " +"exception occurs. The default is ``1000``. When set to ``0`` or less, all " +"traceback information is suppressed and only the exception type and value " +"are printed." +msgstr "" + +#: ../Doc/library/sys.rst:1256 +msgid "" +"A string containing the version number of the Python interpreter plus " +"additional information on the build number and compiler used. This string " +"is displayed when the interactive interpreter is started. Do not extract " +"version information out of it, rather, use :data:`version_info` and the " +"functions provided by the :mod:`platform` module." +msgstr "" + +#: ../Doc/library/sys.rst:1265 +msgid "" +"The C API version for this interpreter. Programmers may find this useful " +"when debugging version conflicts between Python and extension modules." +msgstr "" + +#: ../Doc/library/sys.rst:1271 +msgid "" +"A tuple containing the five components of the version number: *major*, " +"*minor*, *micro*, *releaselevel*, and *serial*. All values except " +"*releaselevel* are integers; the release level is ``'alpha'``, ``'beta'``, " +"``'candidate'``, or ``'final'``. The ``version_info`` value corresponding " +"to the Python version 2.0 is ``(2, 0, 0, 'final', 0)``. The components can " +"also be accessed by name, so ``sys.version_info[0]`` is equivalent to ``sys." +"version_info.major`` and so on." +msgstr "" + +#: ../Doc/library/sys.rst:1279 +msgid "Added named component attributes." +msgstr "" + +#: ../Doc/library/sys.rst:1284 +msgid "" +"This is an implementation detail of the warnings framework; do not modify " +"this value. Refer to the :mod:`warnings` module for more information on the " +"warnings framework." +msgstr "" + +#: ../Doc/library/sys.rst:1291 +msgid "" +"The version number used to form registry keys on Windows platforms. This is " +"stored as string resource 1000 in the Python DLL. The value is normally the " +"first three characters of :const:`version`. It is provided in the :mod:" +"`sys` module for informational purposes; modifying this value has no effect " +"on the registry keys used by Python. Availability: Windows." +msgstr "" + +#: ../Doc/library/sys.rst:1300 +msgid "" +"A dictionary of the various implementation-specific flags passed through " +"the :option:`-X` command-line option. Option names are either mapped to " +"their values, if given explicitly, or to :const:`True`. Example:" +msgstr "" + +#: ../Doc/library/sys.rst:1316 +msgid "" +"This is a CPython-specific way of accessing options passed through :option:`-" +"X`. Other implementations may export them through other means, or not at " +"all." +msgstr "" + +#: ../Doc/library/sys.rst:1324 +msgid "Citations" +msgstr "" + +#: ../Doc/library/sys.rst:1325 +msgid "" +"ISO/IEC 9899:1999. \"Programming languages -- C.\" A public draft of this " +"standard is available at http://www.open-std.org/jtc1/sc22/wg14/www/docs/" +"n1256.pdf\\ ." +msgstr "" + +#: ../Doc/library/sysconfig.rst:2 +msgid "" +":mod:`sysconfig` --- Provide access to Python's configuration information" +msgstr "" + +#: ../Doc/library/sysconfig.rst:12 +msgid "**Source code:** :source:`Lib/sysconfig.py`" +msgstr "" + +#: ../Doc/library/sysconfig.rst:19 +msgid "" +"The :mod:`sysconfig` module provides access to Python's configuration " +"information like the list of installation paths and the configuration " +"variables relevant for the current platform." +msgstr "" + +#: ../Doc/library/sysconfig.rst:24 +msgid "Configuration variables" +msgstr "" + +#: ../Doc/library/sysconfig.rst:26 +msgid "" +"A Python distribution contains a :file:`Makefile` and a :file:`pyconfig.h` " +"header file that are necessary to build both the Python binary itself and " +"third-party C extensions compiled using :mod:`distutils`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:30 +msgid "" +":mod:`sysconfig` puts all variables found in these files in a dictionary " +"that can be accessed using :func:`get_config_vars` or :func:`get_config_var`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:33 +msgid "Notice that on Windows, it's a much smaller set." +msgstr "" + +#: ../Doc/library/sysconfig.rst:37 +msgid "" +"With no arguments, return a dictionary of all configuration variables " +"relevant for the current platform." +msgstr "" + +#: ../Doc/library/sysconfig.rst:40 +msgid "" +"With arguments, return a list of values that result from looking up each " +"argument in the configuration variable dictionary." +msgstr "" + +#: ../Doc/library/sysconfig.rst:43 +msgid "For each argument, if the value is not found, return ``None``." +msgstr "" + +#: ../Doc/library/sysconfig.rst:48 +msgid "" +"Return the value of a single variable *name*. Equivalent to " +"``get_config_vars().get(name)``." +msgstr "" + +#: ../Doc/library/sysconfig.rst:51 ../Doc/library/sysconfig.rst:141 +msgid "If *name* is not found, return ``None``." +msgstr "" + +#: ../Doc/library/sysconfig.rst:53 +msgid "Example of usage::" +msgstr "" + +#: ../Doc/library/sysconfig.rst:65 +msgid "Installation paths" +msgstr "" + +#: ../Doc/library/sysconfig.rst:67 +msgid "" +"Python uses an installation scheme that differs depending on the platform " +"and on the installation options. These schemes are stored in :mod:" +"`sysconfig` under unique identifiers based on the value returned by :const:" +"`os.name`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:71 +msgid "" +"Every new component that is installed using :mod:`distutils` or a Distutils-" +"based system will follow the same scheme to copy its file in the right " +"places." +msgstr "" + +#: ../Doc/library/sysconfig.rst:75 +msgid "Python currently supports seven schemes:" +msgstr "" + +#: ../Doc/library/sysconfig.rst:77 +msgid "" +"*posix_prefix*: scheme for Posix platforms like Linux or Mac OS X. This is " +"the default scheme used when Python or a component is installed." +msgstr "" + +#: ../Doc/library/sysconfig.rst:79 +msgid "" +"*posix_home*: scheme for Posix platforms used when a *home* option is used " +"upon installation. This scheme is used when a component is installed " +"through Distutils with a specific home prefix." +msgstr "" + +#: ../Doc/library/sysconfig.rst:82 +msgid "" +"*posix_user*: scheme for Posix platforms used when a component is installed " +"through Distutils and the *user* option is used. This scheme defines paths " +"located under the user home directory." +msgstr "" + +#: ../Doc/library/sysconfig.rst:85 +msgid "*nt*: scheme for NT platforms like Windows." +msgstr "" + +#: ../Doc/library/sysconfig.rst:86 +msgid "*nt_user*: scheme for NT platforms, when the *user* option is used." +msgstr "" + +#: ../Doc/library/sysconfig.rst:88 +msgid "" +"Each scheme is itself composed of a series of paths and each path has a " +"unique identifier. Python currently uses eight paths:" +msgstr "" + +#: ../Doc/library/sysconfig.rst:91 +msgid "" +"*stdlib*: directory containing the standard Python library files that are " +"not platform-specific." +msgstr "" + +#: ../Doc/library/sysconfig.rst:93 +msgid "" +"*platstdlib*: directory containing the standard Python library files that " +"are platform-specific." +msgstr "" + +#: ../Doc/library/sysconfig.rst:95 +msgid "*platlib*: directory for site-specific, platform-specific files." +msgstr "" + +#: ../Doc/library/sysconfig.rst:96 +msgid "*purelib*: directory for site-specific, non-platform-specific files." +msgstr "" + +#: ../Doc/library/sysconfig.rst:97 +msgid "*include*: directory for non-platform-specific header files." +msgstr "" + +#: ../Doc/library/sysconfig.rst:98 +msgid "*platinclude*: directory for platform-specific header files." +msgstr "" + +#: ../Doc/library/sysconfig.rst:99 +msgid "*scripts*: directory for script files." +msgstr "" + +#: ../Doc/library/sysconfig.rst:100 +msgid "*data*: directory for data files." +msgstr "" + +#: ../Doc/library/sysconfig.rst:102 +msgid ":mod:`sysconfig` provides some functions to determine these paths." +msgstr "" + +#: ../Doc/library/sysconfig.rst:106 +msgid "" +"Return a tuple containing all schemes currently supported in :mod:" +"`sysconfig`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:112 +msgid "" +"Return a tuple containing all path names currently supported in :mod:" +"`sysconfig`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:118 +msgid "" +"Return an installation path corresponding to the path *name*, from the " +"install scheme named *scheme*." +msgstr "" + +#: ../Doc/library/sysconfig.rst:121 +msgid "" +"*name* has to be a value from the list returned by :func:`get_path_names`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:123 +msgid "" +":mod:`sysconfig` stores installation paths corresponding to each path name, " +"for each platform, with variables to be expanded. For instance the *stdlib* " +"path for the *nt* scheme is: ``{base}/Lib``." +msgstr "" + +#: ../Doc/library/sysconfig.rst:127 +msgid "" +":func:`get_path` will use the variables returned by :func:`get_config_vars` " +"to expand the path. All variables have default values for each platform so " +"one may call this function and get the default value." +msgstr "" + +#: ../Doc/library/sysconfig.rst:131 +msgid "" +"If *scheme* is provided, it must be a value from the list returned by :func:" +"`get_scheme_names`. Otherwise, the default scheme for the current platform " +"is used." +msgstr "" + +#: ../Doc/library/sysconfig.rst:135 +msgid "" +"If *vars* is provided, it must be a dictionary of variables that will update " +"the dictionary return by :func:`get_config_vars`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:138 +msgid "" +"If *expand* is set to ``False``, the path will not be expanded using the " +"variables." +msgstr "" + +#: ../Doc/library/sysconfig.rst:146 +msgid "" +"Return a dictionary containing all installation paths corresponding to an " +"installation scheme. See :func:`get_path` for more information." +msgstr "" + +#: ../Doc/library/sysconfig.rst:149 +msgid "" +"If *scheme* is not provided, will use the default scheme for the current " +"platform." +msgstr "" + +#: ../Doc/library/sysconfig.rst:152 +msgid "" +"If *vars* is provided, it must be a dictionary of variables that will update " +"the dictionary used to expand the paths." +msgstr "" + +#: ../Doc/library/sysconfig.rst:155 +msgid "If *expand* is set to False, the paths will not be expanded." +msgstr "" + +#: ../Doc/library/sysconfig.rst:157 +msgid "" +"If *scheme* is not an existing scheme, :func:`get_paths` will raise a :exc:" +"`KeyError`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:166 +msgid "" +"Return the ``MAJOR.MINOR`` Python version number as a string. Similar to " +"``'%d.%d' % sys.version_info[:2]``." +msgstr "" + +#: ../Doc/library/sysconfig.rst:172 +msgid "Return a string that identifies the current platform." +msgstr "" + +#: ../Doc/library/sysconfig.rst:174 +msgid "" +"This is used mainly to distinguish platform-specific build directories and " +"platform-specific built distributions. Typically includes the OS name and " +"version and the architecture (as supplied by :func:`os.uname`), although the " +"exact information included depends on the OS; e.g. for IRIX the architecture " +"isn't particularly important (IRIX only runs on SGI hardware), but for Linux " +"the kernel version isn't particularly important." +msgstr "" + +#: ../Doc/library/sysconfig.rst:181 +msgid "Examples of returned values:" +msgstr "" + +#: ../Doc/library/sysconfig.rst:183 +msgid "linux-i586" +msgstr "" + +#: ../Doc/library/sysconfig.rst:184 +msgid "linux-alpha (?)" +msgstr "" + +#: ../Doc/library/sysconfig.rst:185 +msgid "solaris-2.6-sun4u" +msgstr "" + +#: ../Doc/library/sysconfig.rst:186 +msgid "irix-5.3" +msgstr "" + +#: ../Doc/library/sysconfig.rst:187 +msgid "irix64-6.2" +msgstr "" + +#: ../Doc/library/sysconfig.rst:189 +msgid "Windows will return one of:" +msgstr "" + +#: ../Doc/library/sysconfig.rst:191 +msgid "win-amd64 (64bit Windows on AMD64 (aka x86_64, Intel64, EM64T, etc)" +msgstr "" + +#: ../Doc/library/sysconfig.rst:192 +msgid "win-ia64 (64bit Windows on Itanium)" +msgstr "" + +#: ../Doc/library/sysconfig.rst:193 +msgid "win32 (all others - specifically, sys.platform is returned)" +msgstr "" + +#: ../Doc/library/sysconfig.rst:195 +msgid "Mac OS X can return:" +msgstr "" + +#: ../Doc/library/sysconfig.rst:197 +msgid "macosx-10.6-ppc" +msgstr "" + +#: ../Doc/library/sysconfig.rst:198 +msgid "macosx-10.4-ppc64" +msgstr "" + +#: ../Doc/library/sysconfig.rst:199 +msgid "macosx-10.3-i386" +msgstr "" + +#: ../Doc/library/sysconfig.rst:200 +msgid "macosx-10.4-fat" +msgstr "" + +#: ../Doc/library/sysconfig.rst:202 +msgid "" +"For other non-POSIX platforms, currently just returns :data:`sys.platform`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:207 +msgid "" +"Return ``True`` if the running Python interpreter was built from source and " +"is being run from its built location, and not from a location resulting from " +"e.g. running ``make install`` or installing via a binary installer." +msgstr "" + +#: ../Doc/library/sysconfig.rst:214 +msgid "Parse a :file:`config.h`\\-style file." +msgstr "" + +#: ../Doc/library/sysconfig.rst:216 +msgid "" +"*fp* is a file-like object pointing to the :file:`config.h`\\-like file." +msgstr "" + +#: ../Doc/library/sysconfig.rst:218 +msgid "" +"A dictionary containing name/value pairs is returned. If an optional " +"dictionary is passed in as the second argument, it is used instead of a new " +"dictionary, and updated with the values read in the file." +msgstr "" + +#: ../Doc/library/sysconfig.rst:225 +msgid "Return the path of :file:`pyconfig.h`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:229 +msgid "Return the path of :file:`Makefile`." +msgstr "" + +#: ../Doc/library/sysconfig.rst:232 +msgid "Using :mod:`sysconfig` as a script" +msgstr "" + +#: ../Doc/library/sysconfig.rst:234 +msgid "You can use :mod:`sysconfig` as a script with Python's *-m* option:" +msgstr "" + +#: ../Doc/library/sysconfig.rst:261 +msgid "" +"This call will print in the standard output the information returned by :" +"func:`get_platform`, :func:`get_python_version`, :func:`get_path` and :func:" +"`get_config_vars`." +msgstr "" + +#: ../Doc/library/syslog.rst:2 +msgid ":mod:`syslog` --- Unix syslog library routines" +msgstr "" + +#: ../Doc/library/syslog.rst:10 +msgid "" +"This module provides an interface to the Unix ``syslog`` library routines. " +"Refer to the Unix manual pages for a detailed description of the ``syslog`` " +"facility." +msgstr "" + +#: ../Doc/library/syslog.rst:14 +msgid "" +"This module wraps the system ``syslog`` family of routines. A pure Python " +"library that can speak to a syslog server is available in the :mod:`logging." +"handlers` module as :class:`SysLogHandler`." +msgstr "" + +#: ../Doc/library/syslog.rst:24 +msgid "" +"Send the string *message* to the system logger. A trailing newline is added " +"if necessary. Each message is tagged with a priority composed of a " +"*facility* and a *level*. The optional *priority* argument, which defaults " +"to :const:`LOG_INFO`, determines the message priority. If the facility is " +"not encoded in *priority* using logical-or (``LOG_INFO | LOG_USER``), the " +"value given in the :func:`openlog` call is used." +msgstr "" + +#: ../Doc/library/syslog.rst:31 +msgid "" +"If :func:`openlog` has not been called prior to the call to :func:`syslog`, " +"``openlog()`` will be called with no arguments." +msgstr "" + +#: ../Doc/library/syslog.rst:37 +msgid "" +"Logging options of subsequent :func:`syslog` calls can be set by calling :" +"func:`openlog`. :func:`syslog` will call :func:`openlog` with no arguments " +"if the log is not currently open." +msgstr "" + +#: ../Doc/library/syslog.rst:41 +msgid "" +"The optional *ident* keyword argument is a string which is prepended to " +"every message, and defaults to ``sys.argv[0]`` with leading path components " +"stripped. The optional *logoption* keyword argument (default is 0) is a bit " +"field -- see below for possible values to combine. The optional *facility* " +"keyword argument (default is :const:`LOG_USER`) sets the default facility " +"for messages which do not have a facility explicitly encoded." +msgstr "" + +#: ../Doc/library/syslog.rst:48 +msgid "" +"In previous versions, keyword arguments were not allowed, and *ident* was " +"required. The default for *ident* was dependent on the system libraries, " +"and often was ``python`` instead of the name of the python program file." +msgstr "" + +#: ../Doc/library/syslog.rst:56 +msgid "" +"Reset the syslog module values and call the system library ``closelog()``." +msgstr "" + +#: ../Doc/library/syslog.rst:58 +msgid "" +"This causes the module to behave as it does when initially imported. For " +"example, :func:`openlog` will be called on the first :func:`syslog` call " +"(if :func:`openlog` hasn't already been called), and *ident* and other :func:" +"`openlog` parameters are reset to defaults." +msgstr "" + +#: ../Doc/library/syslog.rst:66 +msgid "" +"Set the priority mask to *maskpri* and return the previous mask value. " +"Calls to :func:`syslog` with a priority level not set in *maskpri* are " +"ignored. The default is to log all priorities. The function " +"``LOG_MASK(pri)`` calculates the mask for the individual priority *pri*. " +"The function ``LOG_UPTO(pri)`` calculates the mask for all priorities up to " +"and including *pri*." +msgstr "" + +#: ../Doc/library/syslog.rst:73 +msgid "The module defines the following constants:" +msgstr "" + +#: ../Doc/library/syslog.rst:78 +msgid "Priority levels (high to low):" +msgstr "" + +#: ../Doc/library/syslog.rst:76 +msgid "" +":const:`LOG_EMERG`, :const:`LOG_ALERT`, :const:`LOG_CRIT`, :const:" +"`LOG_ERR`, :const:`LOG_WARNING`, :const:`LOG_NOTICE`, :const:`LOG_INFO`, :" +"const:`LOG_DEBUG`." +msgstr "" + +#: ../Doc/library/syslog.rst:85 +msgid "Facilities:" +msgstr "" + +#: ../Doc/library/syslog.rst:81 +msgid "" +":const:`LOG_KERN`, :const:`LOG_USER`, :const:`LOG_MAIL`, :const:" +"`LOG_DAEMON`, :const:`LOG_AUTH`, :const:`LOG_LPR`, :const:`LOG_NEWS`, :const:" +"`LOG_UUCP`, :const:`LOG_CRON`, :const:`LOG_SYSLOG`, :const:`LOG_LOCAL0` to :" +"const:`LOG_LOCAL7`, and, if defined in ````, :const:`LOG_AUTHPRIV`." +msgstr "" + +#: ../Doc/library/syslog.rst:91 +msgid "Log options:" +msgstr "" + +#: ../Doc/library/syslog.rst:88 +msgid "" +":const:`LOG_PID`, :const:`LOG_CONS`, :const:`LOG_NDELAY`, and, if defined in " +"````, :const:`LOG_ODELAY`, :const:`LOG_NOWAIT`, and :const:" +"`LOG_PERROR`." +msgstr "" + +#: ../Doc/library/syslog.rst:97 +msgid "Simple example" +msgstr "" + +#: ../Doc/library/syslog.rst:99 +msgid "A simple set of examples::" +msgstr "" + +#: ../Doc/library/syslog.rst:107 +msgid "" +"An example of setting some log options, these would include the process ID " +"in logged messages, and write the messages to the destination facility used " +"for mail logging::" +msgstr "" + +#: ../Doc/library/tabnanny.rst:2 +msgid ":mod:`tabnanny` --- Detection of ambiguous indentation" +msgstr "" + +#: ../Doc/library/tabnanny.rst:13 +msgid "**Source code:** :source:`Lib/tabnanny.py`" +msgstr "" + +#: ../Doc/library/tabnanny.rst:17 +msgid "" +"For the time being this module is intended to be called as a script. However " +"it is possible to import it into an IDE and use the function :func:`check` " +"described below." +msgstr "" + +#: ../Doc/library/tabnanny.rst:23 +msgid "" +"The API provided by this module is likely to change in future releases; such " +"changes may not be backward compatible." +msgstr "" + +#: ../Doc/library/tabnanny.rst:29 +msgid "" +"If *file_or_dir* is a directory and not a symbolic link, then recursively " +"descend the directory tree named by *file_or_dir*, checking all :file:`.py` " +"files along the way. If *file_or_dir* is an ordinary Python source file, it " +"is checked for whitespace related problems. The diagnostic messages are " +"written to standard output using the :func:`print` function." +msgstr "" + +#: ../Doc/library/tabnanny.rst:38 +msgid "" +"Flag indicating whether to print verbose messages. This is incremented by " +"the ``-v`` option if called as a script." +msgstr "" + +#: ../Doc/library/tabnanny.rst:44 +msgid "" +"Flag indicating whether to print only the filenames of files containing " +"whitespace related problems. This is set to true by the ``-q`` option if " +"called as a script." +msgstr "" + +#: ../Doc/library/tabnanny.rst:51 +msgid "" +"Raised by :func:`tokeneater` if detecting an ambiguous indent. Captured and " +"handled in :func:`check`." +msgstr "" + +#: ../Doc/library/tabnanny.rst:57 +msgid "" +"This function is used by :func:`check` as a callback parameter to the " +"function :func:`tokenize.tokenize`." +msgstr "" + +#: ../Doc/library/tabnanny.rst:66 +msgid "Module :mod:`tokenize`" +msgstr "" + +#: ../Doc/library/tabnanny.rst:67 +msgid "Lexical scanner for Python source code." +msgstr "" + +#: ../Doc/library/tarfile.rst:2 +msgid ":mod:`tarfile` --- Read and write tar archive files" +msgstr "" + +#: ../Doc/library/tarfile.rst:10 +msgid "**Source code:** :source:`Lib/tarfile.py`" +msgstr "" + +#: ../Doc/library/tarfile.rst:14 +msgid "" +"The :mod:`tarfile` module makes it possible to read and write tar archives, " +"including those using gzip, bz2 and lzma compression. Use the :mod:`zipfile` " +"module to read or write :file:`.zip` files, or the higher-level functions " +"in :ref:`shutil `." +msgstr "" + +#: ../Doc/library/tarfile.rst:19 +msgid "Some facts and figures:" +msgstr "" + +#: ../Doc/library/tarfile.rst:21 +msgid "" +"reads and writes :mod:`gzip`, :mod:`bz2` and :mod:`lzma` compressed archives " +"if the respective modules are available." +msgstr "" + +#: ../Doc/library/tarfile.rst:24 +msgid "read/write support for the POSIX.1-1988 (ustar) format." +msgstr "" + +#: ../Doc/library/tarfile.rst:26 +msgid "" +"read/write support for the GNU tar format including *longname* and " +"*longlink* extensions, read-only support for all variants of the *sparse* " +"extension including restoration of sparse files." +msgstr "" + +#: ../Doc/library/tarfile.rst:30 +msgid "read/write support for the POSIX.1-2001 (pax) format." +msgstr "" + +#: ../Doc/library/tarfile.rst:32 +msgid "" +"handles directories, regular files, hardlinks, symbolic links, fifos, " +"character devices and block devices and is able to acquire and restore file " +"information like timestamp, access permissions and owner." +msgstr "" + +#: ../Doc/library/tarfile.rst:36 +msgid "Added support for :mod:`lzma` compression." +msgstr "" + +#: ../Doc/library/tarfile.rst:42 +msgid "" +"Return a :class:`TarFile` object for the pathname *name*. For detailed " +"information on :class:`TarFile` objects and the keyword arguments that are " +"allowed, see :ref:`tarfile-objects`." +msgstr "" + +#: ../Doc/library/tarfile.rst:46 +msgid "" +"*mode* has to be a string of the form ``'filemode[:compression]'``, it " +"defaults to ``'r'``. Here is a full list of mode combinations:" +msgstr "" + +#: ../Doc/library/tarfile.rst:50 ../Doc/library/tkinter.ttk.rst:598 +msgid "mode" +msgstr "" + +#: ../Doc/library/tarfile.rst:52 +msgid "``'r' or 'r:*'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:52 +msgid "Open for reading with transparent compression (recommended)." +msgstr "" + +#: ../Doc/library/tarfile.rst:55 +msgid "``'r:'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:55 +msgid "Open for reading exclusively without compression." +msgstr "" + +#: ../Doc/library/tarfile.rst:58 +msgid "``'r:gz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:58 +msgid "Open for reading with gzip compression." +msgstr "" + +#: ../Doc/library/tarfile.rst:60 +msgid "``'r:bz2'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:60 +msgid "Open for reading with bzip2 compression." +msgstr "" + +#: ../Doc/library/tarfile.rst:62 +msgid "``'r:xz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:62 +msgid "Open for reading with lzma compression." +msgstr "" + +#: ../Doc/library/tarfile.rst:64 +msgid "``'x'`` or ``'x:'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:64 +msgid "" +"Create a tarfile exclusively without compression. Raise an :exc:" +"`FileExistsError` exception if it already exists." +msgstr "" + +#: ../Doc/library/tarfile.rst:69 +msgid "``'x:gz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:69 +msgid "" +"Create a tarfile with gzip compression. Raise an :exc:`FileExistsError` " +"exception if it already exists." +msgstr "" + +#: ../Doc/library/tarfile.rst:73 +msgid "``'x:bz2'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:73 +msgid "" +"Create a tarfile with bzip2 compression. Raise an :exc:`FileExistsError` " +"exception if it already exists." +msgstr "" + +#: ../Doc/library/tarfile.rst:77 +msgid "``'x:xz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:77 +msgid "" +"Create a tarfile with lzma compression. Raise an :exc:`FileExistsError` " +"exception if it already exists." +msgstr "" + +#: ../Doc/library/tarfile.rst:81 +msgid "``'a' or 'a:'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:81 +msgid "" +"Open for appending with no compression. The file is created if it does not " +"exist." +msgstr "" + +#: ../Doc/library/tarfile.rst:84 +msgid "``'w' or 'w:'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:84 +msgid "Open for uncompressed writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:86 +msgid "``'w:gz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:86 +msgid "Open for gzip compressed writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:88 +msgid "``'w:bz2'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:88 +msgid "Open for bzip2 compressed writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:90 +msgid "``'w:xz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:90 +msgid "Open for lzma compressed writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:93 +msgid "" +"Note that ``'a:gz'``, ``'a:bz2'`` or ``'a:xz'`` is not possible. If *mode* " +"is not suitable to open a certain (compressed) file for reading, :exc:" +"`ReadError` is raised. Use *mode* ``'r'`` to avoid this. If a compression " +"method is not supported, :exc:`CompressionError` is raised." +msgstr "" + +#: ../Doc/library/tarfile.rst:98 +msgid "" +"If *fileobj* is specified, it is used as an alternative to a :term:`file " +"object` opened in binary mode for *name*. It is supposed to be at position 0." +msgstr "" + +#: ../Doc/library/tarfile.rst:101 +msgid "" +"For modes ``'w:gz'``, ``'r:gz'``, ``'w:bz2'``, ``'r:bz2'``, ``'x:gz'``, ``'x:" +"bz2'``, :func:`tarfile.open` accepts the keyword argument *compresslevel* " +"(default ``9``) to specify the compression level of the file." +msgstr "" + +#: ../Doc/library/tarfile.rst:105 +msgid "" +"For special purposes, there is a second format for *mode*: ``'filemode|" +"[compression]'``. :func:`tarfile.open` will return a :class:`TarFile` " +"object that processes its data as a stream of blocks. No random seeking " +"will be done on the file. If given, *fileobj* may be any object that has a :" +"meth:`read` or :meth:`write` method (depending on the *mode*). *bufsize* " +"specifies the blocksize and defaults to ``20 * 512`` bytes. Use this variant " +"in combination with e.g. ``sys.stdin``, a socket :term:`file object` or a " +"tape device. However, such a :class:`TarFile` object is limited in that it " +"does not allow random access, see :ref:`tar-examples`. The currently " +"possible modes:" +msgstr "" + +#: ../Doc/library/tarfile.rst:117 ../Doc/library/turtle.rst:1843 +msgid "Mode" +msgstr "" + +#: ../Doc/library/tarfile.rst:119 +msgid "``'r|*'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:119 +msgid "Open a *stream* of tar blocks for reading with transparent compression." +msgstr "" + +#: ../Doc/library/tarfile.rst:122 +msgid "``'r|'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:122 +msgid "Open a *stream* of uncompressed tar blocks for reading." +msgstr "" + +#: ../Doc/library/tarfile.rst:125 +msgid "``'r|gz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:125 +msgid "Open a gzip compressed *stream* for reading." +msgstr "" + +#: ../Doc/library/tarfile.rst:128 +msgid "``'r|bz2'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:128 +msgid "Open a bzip2 compressed *stream* for reading." +msgstr "" + +#: ../Doc/library/tarfile.rst:131 +msgid "``'r|xz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:131 +msgid "Open an lzma compressed *stream* for reading." +msgstr "" + +#: ../Doc/library/tarfile.rst:134 +msgid "``'w|'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:134 +msgid "Open an uncompressed *stream* for writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:136 +msgid "``'w|gz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:136 +msgid "Open a gzip compressed *stream* for writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:139 +msgid "``'w|bz2'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:139 +msgid "Open a bzip2 compressed *stream* for writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:142 +msgid "``'w|xz'``" +msgstr "" + +#: ../Doc/library/tarfile.rst:142 +msgid "Open an lzma compressed *stream* for writing." +msgstr "" + +#: ../Doc/library/tarfile.rst:151 +msgid "" +"Class for reading and writing tar archives. Do not use this class directly: " +"use :func:`tarfile.open` instead. See :ref:`tarfile-objects`." +msgstr "" + +#: ../Doc/library/tarfile.rst:157 +msgid "" +"Return :const:`True` if *name* is a tar archive file, that the :mod:" +"`tarfile` module can read." +msgstr "" + +#: ../Doc/library/tarfile.rst:161 +msgid "The :mod:`tarfile` module defines the following exceptions:" +msgstr "" + +#: ../Doc/library/tarfile.rst:166 +msgid "Base class for all :mod:`tarfile` exceptions." +msgstr "" + +#: ../Doc/library/tarfile.rst:171 +msgid "" +"Is raised when a tar archive is opened, that either cannot be handled by " +"the :mod:`tarfile` module or is somehow invalid." +msgstr "" + +#: ../Doc/library/tarfile.rst:177 +msgid "" +"Is raised when a compression method is not supported or when the data cannot " +"be decoded properly." +msgstr "" + +#: ../Doc/library/tarfile.rst:183 +msgid "" +"Is raised for the limitations that are typical for stream-like :class:" +"`TarFile` objects." +msgstr "" + +#: ../Doc/library/tarfile.rst:189 +msgid "" +"Is raised for *non-fatal* errors when using :meth:`TarFile.extract`, but " +"only if :attr:`TarFile.errorlevel`\\ ``== 2``." +msgstr "" + +#: ../Doc/library/tarfile.rst:195 +msgid "Is raised by :meth:`TarInfo.frombuf` if the buffer it gets is invalid." +msgstr "" + +#: ../Doc/library/tarfile.rst:198 +msgid "The following constants are available at the module level:" +msgstr "" + +#: ../Doc/library/tarfile.rst:202 +msgid "" +"The default character encoding: ``'utf-8'`` on Windows, the value returned " +"by :func:`sys.getfilesystemencoding` otherwise." +msgstr "" + +#: ../Doc/library/tarfile.rst:206 +msgid "" +"Each of the following constants defines a tar archive format that the :mod:" +"`tarfile` module is able to create. See section :ref:`tar-formats` for " +"details." +msgstr "" + +#: ../Doc/library/tarfile.rst:213 +msgid "POSIX.1-1988 (ustar) format." +msgstr "" + +#: ../Doc/library/tarfile.rst:218 +msgid "GNU tar format." +msgstr "" + +#: ../Doc/library/tarfile.rst:223 +msgid "POSIX.1-2001 (pax) format." +msgstr "" + +#: ../Doc/library/tarfile.rst:228 +msgid "" +"The default format for creating archives. This is currently :const:" +"`GNU_FORMAT`." +msgstr "" + +#: ../Doc/library/tarfile.rst:234 +msgid "Module :mod:`zipfile`" +msgstr "" + +#: ../Doc/library/tarfile.rst:234 +msgid "Documentation of the :mod:`zipfile` standard module." +msgstr "" + +#: ../Doc/library/tarfile.rst:238 +msgid ":ref:`archiving-operations`" +msgstr "" + +#: ../Doc/library/tarfile.rst:237 +msgid "" +"Documentation of the higher-level archiving facilities provided by the " +"standard :mod:`shutil` module." +msgstr "" + +#: ../Doc/library/tarfile.rst:240 +msgid "" +"`GNU tar manual, Basic Tar Format `_" +msgstr "" + +#: ../Doc/library/tarfile.rst:241 +msgid "Documentation for tar archive files, including GNU tar extensions." +msgstr "" + +#: ../Doc/library/tarfile.rst:247 +msgid "TarFile Objects" +msgstr "" + +#: ../Doc/library/tarfile.rst:249 +msgid "" +"The :class:`TarFile` object provides an interface to a tar archive. A tar " +"archive is a sequence of blocks. An archive member (a stored file) is made " +"up of a header block followed by data blocks. It is possible to store a file " +"in a tar archive several times. Each archive member is represented by a :" +"class:`TarInfo` object, see :ref:`tarinfo-objects` for details." +msgstr "" + +#: ../Doc/library/tarfile.rst:255 +msgid "" +"A :class:`TarFile` object can be used as a context manager in a :keyword:" +"`with` statement. It will automatically be closed when the block is " +"completed. Please note that in the event of an exception an archive opened " +"for writing will not be finalized; only the internally used file object will " +"be closed. See the :ref:`tar-examples` section for a use case." +msgstr "" + +#: ../Doc/library/tarfile.rst:261 +msgid "Added support for the context management protocol." +msgstr "" + +#: ../Doc/library/tarfile.rst:266 +msgid "" +"All following arguments are optional and can be accessed as instance " +"attributes as well." +msgstr "" + +#: ../Doc/library/tarfile.rst:269 +msgid "" +"*name* is the pathname of the archive. It can be omitted if *fileobj* is " +"given. In this case, the file object's :attr:`name` attribute is used if it " +"exists." +msgstr "" + +#: ../Doc/library/tarfile.rst:272 +msgid "" +"*mode* is either ``'r'`` to read from an existing archive, ``'a'`` to append " +"data to an existing file, ``'w'`` to create a new file overwriting an " +"existing one, or ``'x'`` to create a new file only if it does not already " +"exist." +msgstr "" + +#: ../Doc/library/tarfile.rst:276 +msgid "" +"If *fileobj* is given, it is used for reading or writing data. If it can be " +"determined, *mode* is overridden by *fileobj*'s mode. *fileobj* will be used " +"from position 0." +msgstr "" + +#: ../Doc/library/tarfile.rst:282 +msgid "*fileobj* is not closed, when :class:`TarFile` is closed." +msgstr "" + +#: ../Doc/library/tarfile.rst:284 +msgid "" +"*format* controls the archive format. It must be one of the constants :const:" +"`USTAR_FORMAT`, :const:`GNU_FORMAT` or :const:`PAX_FORMAT` that are defined " +"at module level." +msgstr "" + +#: ../Doc/library/tarfile.rst:288 +msgid "" +"The *tarinfo* argument can be used to replace the default :class:`TarInfo` " +"class with a different one." +msgstr "" + +#: ../Doc/library/tarfile.rst:291 +msgid "" +"If *dereference* is :const:`False`, add symbolic and hard links to the " +"archive. If it is :const:`True`, add the content of the target files to the " +"archive. This has no effect on systems that do not support symbolic links." +msgstr "" + +#: ../Doc/library/tarfile.rst:295 +msgid "" +"If *ignore_zeros* is :const:`False`, treat an empty block as the end of the " +"archive. If it is :const:`True`, skip empty (and invalid) blocks and try to " +"get as many members as possible. This is only useful for reading " +"concatenated or damaged archives." +msgstr "" + +#: ../Doc/library/tarfile.rst:299 +msgid "" +"*debug* can be set from ``0`` (no debug messages) up to ``3`` (all debug " +"messages). The messages are written to ``sys.stderr``." +msgstr "" + +#: ../Doc/library/tarfile.rst:302 +msgid "" +"If *errorlevel* is ``0``, all errors are ignored when using :meth:`TarFile." +"extract`. Nevertheless, they appear as error messages in the debug output, " +"when debugging is enabled. If ``1``, all *fatal* errors are raised as :exc:" +"`OSError` exceptions. If ``2``, all *non-fatal* errors are raised as :exc:" +"`TarError` exceptions as well." +msgstr "" + +#: ../Doc/library/tarfile.rst:308 +msgid "" +"The *encoding* and *errors* arguments define the character encoding to be " +"used for reading or writing the archive and how conversion errors are going " +"to be handled. The default settings will work for most users. See section :" +"ref:`tar-unicode` for in-depth information." +msgstr "" + +#: ../Doc/library/tarfile.rst:313 +msgid "" +"The *pax_headers* argument is an optional dictionary of strings which will " +"be added as a pax global header if *format* is :const:`PAX_FORMAT`." +msgstr "" + +#: ../Doc/library/tarfile.rst:316 ../Doc/library/tarfile.rst:531 +msgid "Use ``'surrogateescape'`` as the default for the *errors* argument." +msgstr "" + +#: ../Doc/library/tarfile.rst:324 +msgid "" +"Alternative constructor. The :func:`tarfile.open` function is actually a " +"shortcut to this classmethod." +msgstr "" + +#: ../Doc/library/tarfile.rst:330 +msgid "" +"Return a :class:`TarInfo` object for member *name*. If *name* can not be " +"found in the archive, :exc:`KeyError` is raised." +msgstr "" + +#: ../Doc/library/tarfile.rst:335 +msgid "" +"If a member occurs more than once in the archive, its last occurrence is " +"assumed to be the most up-to-date version." +msgstr "" + +#: ../Doc/library/tarfile.rst:341 +msgid "" +"Return the members of the archive as a list of :class:`TarInfo` objects. The " +"list has the same order as the members in the archive." +msgstr "" + +#: ../Doc/library/tarfile.rst:347 +msgid "" +"Return the members as a list of their names. It has the same order as the " +"list returned by :meth:`getmembers`." +msgstr "" + +#: ../Doc/library/tarfile.rst:353 +msgid "" +"Print a table of contents to ``sys.stdout``. If *verbose* is :const:`False`, " +"only the names of the members are printed. If it is :const:`True`, output " +"similar to that of :program:`ls -l` is produced. If optional *members* is " +"given, it must be a subset of the list returned by :meth:`getmembers`." +msgstr "" + +#: ../Doc/library/tarfile.rst:358 +msgid "Added the *members* parameter." +msgstr "" + +#: ../Doc/library/tarfile.rst:364 +msgid "" +"Return the next member of the archive as a :class:`TarInfo` object, when :" +"class:`TarFile` is opened for reading. Return :const:`None` if there is no " +"more available." +msgstr "" + +#: ../Doc/library/tarfile.rst:371 +msgid "" +"Extract all members from the archive to the current working directory or " +"directory *path*. If optional *members* is given, it must be a subset of the " +"list returned by :meth:`getmembers`. Directory information like owner, " +"modification time and permissions are set after all members have been " +"extracted. This is done to work around two problems: A directory's " +"modification time is reset each time a file is created in it. And, if a " +"directory's permissions do not allow writing, extracting files to it will " +"fail." +msgstr "" + +#: ../Doc/library/tarfile.rst:379 ../Doc/library/tarfile.rst:402 +msgid "" +"If *numeric_owner* is :const:`True`, the uid and gid numbers from the " +"tarfile are used to set the owner/group for the extracted files. Otherwise, " +"the named values from the tarfile are used." +msgstr "" + +#: ../Doc/library/tarfile.rst:385 +msgid "" +"Never extract archives from untrusted sources without prior inspection. It " +"is possible that files are created outside of *path*, e.g. members that have " +"absolute filenames starting with ``\"/\"`` or filenames with two dots ``\".." +"\"``." +msgstr "" + +#: ../Doc/library/tarfile.rst:390 ../Doc/library/tarfile.rst:418 +msgid "Added the *numeric_only* parameter." +msgstr "" + +#: ../Doc/library/tarfile.rst:396 +msgid "" +"Extract a member from the archive to the current working directory, using " +"its full name. Its file information is extracted as accurately as possible. " +"*member* may be a filename or a :class:`TarInfo` object. You can specify a " +"different directory using *path*. File attributes (owner, mtime, mode) are " +"set unless *set_attrs* is false." +msgstr "" + +#: ../Doc/library/tarfile.rst:408 +msgid "" +"The :meth:`extract` method does not take care of several extraction issues. " +"In most cases you should consider using the :meth:`extractall` method." +msgstr "" + +#: ../Doc/library/tarfile.rst:413 +msgid "See the warning for :meth:`extractall`." +msgstr "" + +#: ../Doc/library/tarfile.rst:415 +msgid "Added the *set_attrs* parameter." +msgstr "" + +#: ../Doc/library/tarfile.rst:423 +msgid "" +"Extract a member from the archive as a file object. *member* may be a " +"filename or a :class:`TarInfo` object. If *member* is a regular file or a " +"link, an :class:`io.BufferedReader` object is returned. Otherwise, :const:" +"`None` is returned." +msgstr "" + +#: ../Doc/library/tarfile.rst:428 +msgid "Return an :class:`io.BufferedReader` object." +msgstr "" + +#: ../Doc/library/tarfile.rst:434 +msgid "" +"Add the file *name* to the archive. *name* may be any type of file " +"(directory, fifo, symbolic link, etc.). If given, *arcname* specifies an " +"alternative name for the file in the archive. Directories are added " +"recursively by default. This can be avoided by setting *recursive* to :const:" +"`False`. If *exclude* is given, it must be a function that takes one " +"filename argument and returns a boolean value. Depending on this value the " +"respective file is either excluded (:const:`True`) or added (:const:" +"`False`). If *filter* is specified it must be a keyword argument. It should " +"be a function that takes a :class:`TarInfo` object argument and returns the " +"changed :class:`TarInfo` object. If it instead returns :const:`None` the :" +"class:`TarInfo` object will be excluded from the archive. See :ref:`tar-" +"examples` for an example." +msgstr "" + +#: ../Doc/library/tarfile.rst:447 +msgid "Added the *filter* parameter." +msgstr "" + +#: ../Doc/library/tarfile.rst:450 +msgid "" +"The *exclude* parameter is deprecated, please use the *filter* parameter " +"instead." +msgstr "" + +#: ../Doc/library/tarfile.rst:457 +msgid "" +"Add the :class:`TarInfo` object *tarinfo* to the archive. If *fileobj* is " +"given, it should be a :term:`binary file`, and ``tarinfo.size`` bytes are " +"read from it and added to the archive. You can create :class:`TarInfo` " +"objects directly, or by using :meth:`gettarinfo`." +msgstr "" + +#: ../Doc/library/tarfile.rst:465 +msgid "" +"Create a :class:`TarInfo` object from the result of :func:`os.stat` or " +"equivalent on an existing file. The file is either named by *name*, or " +"specified as a :term:`file object` *fileobj* with a file descriptor. If " +"given, *arcname* specifies an alternative name for the file in the archive, " +"otherwise, the name is taken from *fileobj*’s :attr:`~io.FileIO.name` " +"attribute, or the *name* argument. The name should be a text string." +msgstr "" + +#: ../Doc/library/tarfile.rst:473 +msgid "" +"You can modify some of the :class:`TarInfo`’s attributes before you add it " +"using :meth:`addfile`. If the file object is not an ordinary file object " +"positioned at the beginning of the file, attributes such as :attr:`~TarInfo." +"size` may need modifying. This is the case for objects such as :class:" +"`~gzip.GzipFile`. The :attr:`~TarInfo.name` may also be modified, in which " +"case *arcname* could be a dummy string." +msgstr "" + +#: ../Doc/library/tarfile.rst:484 +msgid "" +"Close the :class:`TarFile`. In write mode, two finishing zero blocks are " +"appended to the archive." +msgstr "" + +#: ../Doc/library/tarfile.rst:490 +msgid "A dictionary containing key-value pairs of pax global headers." +msgstr "" + +#: ../Doc/library/tarfile.rst:497 +msgid "TarInfo Objects" +msgstr "" + +#: ../Doc/library/tarfile.rst:499 +msgid "" +"A :class:`TarInfo` object represents one member in a :class:`TarFile`. Aside " +"from storing all required attributes of a file (like file type, size, time, " +"permissions, owner etc.), it provides some useful methods to determine its " +"type. It does *not* contain the file's data itself." +msgstr "" + +#: ../Doc/library/tarfile.rst:504 +msgid "" +":class:`TarInfo` objects are returned by :class:`TarFile`'s methods :meth:" +"`getmember`, :meth:`getmembers` and :meth:`gettarinfo`." +msgstr "" + +#: ../Doc/library/tarfile.rst:510 +msgid "Create a :class:`TarInfo` object." +msgstr "" + +#: ../Doc/library/tarfile.rst:515 +msgid "Create and return a :class:`TarInfo` object from string buffer *buf*." +msgstr "" + +#: ../Doc/library/tarfile.rst:517 +msgid "Raises :exc:`HeaderError` if the buffer is invalid." +msgstr "" + +#: ../Doc/library/tarfile.rst:522 +msgid "" +"Read the next member from the :class:`TarFile` object *tarfile* and return " +"it as a :class:`TarInfo` object." +msgstr "" + +#: ../Doc/library/tarfile.rst:528 +msgid "" +"Create a string buffer from a :class:`TarInfo` object. For information on " +"the arguments see the constructor of the :class:`TarFile` class." +msgstr "" + +#: ../Doc/library/tarfile.rst:535 +msgid "A ``TarInfo`` object has the following public data attributes:" +msgstr "" + +#: ../Doc/library/tarfile.rst:540 +msgid "Name of the archive member." +msgstr "" + +#: ../Doc/library/tarfile.rst:545 +msgid "Size in bytes." +msgstr "" + +#: ../Doc/library/tarfile.rst:555 +msgid "Permission bits." +msgstr "" + +#: ../Doc/library/tarfile.rst:560 +msgid "" +"File type. *type* is usually one of these constants: :const:`REGTYPE`, :" +"const:`AREGTYPE`, :const:`LNKTYPE`, :const:`SYMTYPE`, :const:`DIRTYPE`, :" +"const:`FIFOTYPE`, :const:`CONTTYPE`, :const:`CHRTYPE`, :const:`BLKTYPE`, :" +"const:`GNUTYPE_SPARSE`. To determine the type of a :class:`TarInfo` object " +"more conveniently, use the ``is*()`` methods below." +msgstr "" + +#: ../Doc/library/tarfile.rst:569 +msgid "" +"Name of the target file name, which is only present in :class:`TarInfo` " +"objects of type :const:`LNKTYPE` and :const:`SYMTYPE`." +msgstr "" + +#: ../Doc/library/tarfile.rst:575 +msgid "User ID of the user who originally stored this member." +msgstr "" + +#: ../Doc/library/tarfile.rst:580 +msgid "Group ID of the user who originally stored this member." +msgstr "" + +#: ../Doc/library/tarfile.rst:585 +msgid "User name." +msgstr "" + +#: ../Doc/library/tarfile.rst:590 +msgid "Group name." +msgstr "" + +#: ../Doc/library/tarfile.rst:595 +msgid "" +"A dictionary containing key-value pairs of an associated pax extended header." +msgstr "" + +#: ../Doc/library/tarfile.rst:598 +msgid "A :class:`TarInfo` object also provides some convenient query methods:" +msgstr "" + +#: ../Doc/library/tarfile.rst:603 +msgid "Return :const:`True` if the :class:`Tarinfo` object is a regular file." +msgstr "" + +#: ../Doc/library/tarfile.rst:608 +msgid "Same as :meth:`isfile`." +msgstr "" + +#: ../Doc/library/tarfile.rst:613 +msgid "Return :const:`True` if it is a directory." +msgstr "" + +#: ../Doc/library/tarfile.rst:618 +msgid "Return :const:`True` if it is a symbolic link." +msgstr "" + +#: ../Doc/library/tarfile.rst:623 +msgid "Return :const:`True` if it is a hard link." +msgstr "" + +#: ../Doc/library/tarfile.rst:628 +msgid "Return :const:`True` if it is a character device." +msgstr "" + +#: ../Doc/library/tarfile.rst:633 +msgid "Return :const:`True` if it is a block device." +msgstr "" + +#: ../Doc/library/tarfile.rst:638 +msgid "Return :const:`True` if it is a FIFO." +msgstr "" + +#: ../Doc/library/tarfile.rst:643 +msgid "" +"Return :const:`True` if it is one of character device, block device or FIFO." +msgstr "" + +#: ../Doc/library/tarfile.rst:653 +msgid "" +"The :mod:`tarfile` module provides a simple command line interface to " +"interact with tar archives." +msgstr "" + +#: ../Doc/library/tarfile.rst:656 +msgid "" +"If you want to create a new tar archive, specify its name after the :option:" +"`-c` option and then list the filename(s) that should be included:" +msgstr "" + +#: ../Doc/library/tarfile.rst:663 +msgid "Passing a directory is also acceptable:" +msgstr "" + +#: ../Doc/library/tarfile.rst:669 +msgid "" +"If you want to extract a tar archive into the current directory, use the :" +"option:`-e` option:" +msgstr "" + +#: ../Doc/library/tarfile.rst:676 +msgid "" +"You can also extract a tar archive into a different directory by passing the " +"directory's name:" +msgstr "" + +#: ../Doc/library/tarfile.rst:683 +msgid "For a list of the files in a tar archive, use the :option:`-l` option:" +msgstr "" + +#: ../Doc/library/tarfile.rst:696 +msgid "List files in a tarfile." +msgstr "" + +#: ../Doc/library/tarfile.rst:701 +msgid "Create tarfile from source files." +msgstr "" + +#: ../Doc/library/tarfile.rst:706 +msgid "" +"Extract tarfile into the current directory if *output_dir* is not specified." +msgstr "" + +#: ../Doc/library/tarfile.rst:711 +msgid "Test whether the tarfile is valid or not." +msgstr "" + +#: ../Doc/library/tarfile.rst:715 ../Doc/library/unittest.rst:268 +msgid "Verbose output" +msgstr "" + +#: ../Doc/library/tarfile.rst:722 +msgid "How to extract an entire tar archive to the current working directory::" +msgstr "" + +#: ../Doc/library/tarfile.rst:729 +msgid "" +"How to extract a subset of a tar archive with :meth:`TarFile.extractall` " +"using a generator function instead of a list::" +msgstr "" + +#: ../Doc/library/tarfile.rst:744 +msgid "How to create an uncompressed tar archive from a list of filenames::" +msgstr "" + +#: ../Doc/library/tarfile.rst:752 +msgid "The same example using the :keyword:`with` statement::" +msgstr "" + +#: ../Doc/library/tarfile.rst:759 +msgid "" +"How to read a gzip compressed tar archive and display some member " +"information::" +msgstr "" + +#: ../Doc/library/tarfile.rst:773 +msgid "" +"How to create an archive and reset the user information using the *filter* " +"parameter in :meth:`TarFile.add`::" +msgstr "" + +#: ../Doc/library/tarfile.rst:789 +msgid "Supported tar formats" +msgstr "" + +#: ../Doc/library/tarfile.rst:791 +msgid "" +"There are three tar formats that can be created with the :mod:`tarfile` " +"module:" +msgstr "" + +#: ../Doc/library/tarfile.rst:793 +msgid "" +"The POSIX.1-1988 ustar format (:const:`USTAR_FORMAT`). It supports filenames " +"up to a length of at best 256 characters and linknames up to 100 characters. " +"The maximum file size is 8 GiB. This is an old and limited but widely " +"supported format." +msgstr "" + +#: ../Doc/library/tarfile.rst:798 +msgid "" +"The GNU tar format (:const:`GNU_FORMAT`). It supports long filenames and " +"linknames, files bigger than 8 GiB and sparse files. It is the de facto " +"standard on GNU/Linux systems. :mod:`tarfile` fully supports the GNU tar " +"extensions for long names, sparse file support is read-only." +msgstr "" + +#: ../Doc/library/tarfile.rst:803 +msgid "" +"The POSIX.1-2001 pax format (:const:`PAX_FORMAT`). It is the most flexible " +"format with virtually no limits. It supports long filenames and linknames, " +"large files and stores pathnames in a portable way. However, not all tar " +"implementations today are able to handle pax archives properly." +msgstr "" + +#: ../Doc/library/tarfile.rst:808 +msgid "" +"The *pax* format is an extension to the existing *ustar* format. It uses " +"extra headers for information that cannot be stored otherwise. There are two " +"flavours of pax headers: Extended headers only affect the subsequent file " +"header, global headers are valid for the complete archive and affect all " +"following files. All the data in a pax header is encoded in *UTF-8* for " +"portability reasons." +msgstr "" + +#: ../Doc/library/tarfile.rst:814 +msgid "" +"There are some more variants of the tar format which can be read, but not " +"created:" +msgstr "" + +#: ../Doc/library/tarfile.rst:817 +msgid "" +"The ancient V7 format. This is the first tar format from Unix Seventh " +"Edition, storing only regular files and directories. Names must not be " +"longer than 100 characters, there is no user/group name information. Some " +"archives have miscalculated header checksums in case of fields with non-" +"ASCII characters." +msgstr "" + +#: ../Doc/library/tarfile.rst:822 +msgid "" +"The SunOS tar extended format. This format is a variant of the POSIX.1-2001 " +"pax format, but is not compatible." +msgstr "" + +#: ../Doc/library/tarfile.rst:828 +msgid "Unicode issues" +msgstr "" + +#: ../Doc/library/tarfile.rst:830 +msgid "" +"The tar format was originally conceived to make backups on tape drives with " +"the main focus on preserving file system information. Nowadays tar archives " +"are commonly used for file distribution and exchanging archives over " +"networks. One problem of the original format (which is the basis of all " +"other formats) is that there is no concept of supporting different character " +"encodings. For example, an ordinary tar archive created on a *UTF-8* system " +"cannot be read correctly on a *Latin-1* system if it contains non-*ASCII* " +"characters. Textual metadata (like filenames, linknames, user/group names) " +"will appear damaged. Unfortunately, there is no way to autodetect the " +"encoding of an archive. The pax format was designed to solve this problem. " +"It stores non-ASCII metadata using the universal character encoding *UTF-8*." +msgstr "" + +#: ../Doc/library/tarfile.rst:842 +msgid "" +"The details of character conversion in :mod:`tarfile` are controlled by the " +"*encoding* and *errors* keyword arguments of the :class:`TarFile` class." +msgstr "" + +#: ../Doc/library/tarfile.rst:845 +msgid "" +"*encoding* defines the character encoding to use for the metadata in the " +"archive. The default value is :func:`sys.getfilesystemencoding` or " +"``'ascii'`` as a fallback. Depending on whether the archive is read or " +"written, the metadata must be either decoded or encoded. If *encoding* is " +"not set appropriately, this conversion may fail." +msgstr "" + +#: ../Doc/library/tarfile.rst:851 +msgid "" +"The *errors* argument defines how characters are treated that cannot be " +"converted. Possible values are listed in section :ref:`error-handlers`. The " +"default scheme is ``'surrogateescape'`` which Python also uses for its file " +"system calls, see :ref:`os-filenames`." +msgstr "" + +#: ../Doc/library/tarfile.rst:856 +msgid "" +"In case of :const:`PAX_FORMAT` archives, *encoding* is generally not needed " +"because all the metadata is stored using *UTF-8*. *encoding* is only used in " +"the rare cases when binary pax headers are decoded or when strings with " +"surrogate characters are stored." +msgstr "" + +#: ../Doc/library/telnetlib.rst:2 +msgid ":mod:`telnetlib` --- Telnet client" +msgstr "" + +#: ../Doc/library/telnetlib.rst:9 +msgid "**Source code:** :source:`Lib/telnetlib.py`" +msgstr "" + +#: ../Doc/library/telnetlib.rst:15 +msgid "" +"The :mod:`telnetlib` module provides a :class:`Telnet` class that implements " +"the Telnet protocol. See :rfc:`854` for details about the protocol. In " +"addition, it provides symbolic constants for the protocol characters (see " +"below), and for the telnet options. The symbolic names of the telnet options " +"follow the definitions in ``arpa/telnet.h``, with the leading ``TELOPT_`` " +"removed. For symbolic names of options which are traditionally not included " +"in ``arpa/telnet.h``, see the module source itself." +msgstr "" + +#: ../Doc/library/telnetlib.rst:23 +msgid "" +"The symbolic constants for the telnet commands are: IAC, DONT, DO, WONT, " +"WILL, SE (Subnegotiation End), NOP (No Operation), DM (Data Mark), BRK " +"(Break), IP (Interrupt process), AO (Abort output), AYT (Are You There), EC " +"(Erase Character), EL (Erase Line), GA (Go Ahead), SB (Subnegotiation Begin)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:31 +msgid "" +":class:`Telnet` represents a connection to a Telnet server. The instance is " +"initially not connected by default; the :meth:`open` method must be used to " +"establish a connection. Alternatively, the host name and optional port " +"number can be passed to the constructor too, in which case the connection to " +"the server will be established before the constructor returns. The optional " +"*timeout* parameter specifies a timeout in seconds for blocking operations " +"like the connection attempt (if not specified, the global default timeout " +"setting will be used)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:40 +msgid "Do not reopen an already connected instance." +msgstr "" + +#: ../Doc/library/telnetlib.rst:42 +msgid "" +"This class has many :meth:`read_\\*` methods. Note that some of them " +"raise :exc:`EOFError` when the end of the connection is read, because they " +"can return an empty string for other reasons. See the individual " +"descriptions below." +msgstr "" + +#: ../Doc/library/telnetlib.rst:46 +msgid "" +"A :class:`Telnet` object is a context manager and can be used in a :keyword:" +"`with` statement. When the :keyword:`with` block ends, the :meth:`close` " +"method is called::" +msgstr "" + +#: ../Doc/library/telnetlib.rst:55 +msgid "Context manager support added" +msgstr "" + +#: ../Doc/library/telnetlib.rst:60 +msgid ":rfc:`854` - Telnet Protocol Specification" +msgstr "" + +#: ../Doc/library/telnetlib.rst:61 +msgid "Definition of the Telnet protocol." +msgstr "" + +#: ../Doc/library/telnetlib.rst:67 +msgid "Telnet Objects" +msgstr "" + +#: ../Doc/library/telnetlib.rst:69 +msgid ":class:`Telnet` instances have the following methods:" +msgstr "" + +#: ../Doc/library/telnetlib.rst:74 +msgid "" +"Read until a given byte string, *expected*, is encountered or until " +"*timeout* seconds have passed." +msgstr "" + +#: ../Doc/library/telnetlib.rst:77 +msgid "" +"When no match is found, return whatever is available instead, possibly empty " +"bytes. Raise :exc:`EOFError` if the connection is closed and no cooked data " +"is available." +msgstr "" + +#: ../Doc/library/telnetlib.rst:84 +msgid "Read all data until EOF as bytes; block until connection closed." +msgstr "" + +#: ../Doc/library/telnetlib.rst:89 +msgid "" +"Read at least one byte of cooked data unless EOF is hit. Return ``b''`` if " +"EOF is hit. Block if no data is immediately available." +msgstr "" + +#: ../Doc/library/telnetlib.rst:95 +msgid "Read everything that can be without blocking in I/O (eager)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:97 ../Doc/library/telnetlib.rst:106 +msgid "" +"Raise :exc:`EOFError` if connection closed and no cooked data available. " +"Return ``b''`` if no cooked data available otherwise. Do not block unless in " +"the midst of an IAC sequence." +msgstr "" + +#: ../Doc/library/telnetlib.rst:104 +msgid "Read readily available data." +msgstr "" + +#: ../Doc/library/telnetlib.rst:113 +msgid "Process and return data already in the queues (lazy)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:115 +msgid "" +"Raise :exc:`EOFError` if connection closed and no data available. Return " +"``b''`` if no cooked data available otherwise. Do not block unless in the " +"midst of an IAC sequence." +msgstr "" + +#: ../Doc/library/telnetlib.rst:122 +msgid "Return any data available in the cooked queue (very lazy)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:124 +msgid "" +"Raise :exc:`EOFError` if connection closed and no data available. Return " +"``b''`` if no cooked data available otherwise. This method never blocks." +msgstr "" + +#: ../Doc/library/telnetlib.rst:130 +msgid "" +"Return the data collected between a SB/SE pair (suboption begin/end). The " +"callback should access these data when it was invoked with a ``SE`` command. " +"This method never blocks." +msgstr "" + +#: ../Doc/library/telnetlib.rst:137 +msgid "" +"Connect to a host. The optional second argument is the port number, which " +"defaults to the standard Telnet port (23). The optional *timeout* parameter " +"specifies a timeout in seconds for blocking operations like the connection " +"attempt (if not specified, the global default timeout setting will be used)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:142 +msgid "Do not try to reopen an already connected instance." +msgstr "" + +#: ../Doc/library/telnetlib.rst:147 +msgid "" +"Print a debug message when the debug level is ``>`` 0. If extra arguments " +"are present, they are substituted in the message using the standard string " +"formatting operator." +msgstr "" + +#: ../Doc/library/telnetlib.rst:154 +msgid "" +"Set the debug level. The higher the value of *debuglevel*, the more debug " +"output you get (on ``sys.stdout``)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:165 +msgid "Return the socket object used internally." +msgstr "" + +#: ../Doc/library/telnetlib.rst:170 +msgid "Return the file descriptor of the socket object used internally." +msgstr "" + +#: ../Doc/library/telnetlib.rst:175 +msgid "" +"Write a byte string to the socket, doubling any IAC characters. This can " +"block if the connection is blocked. May raise :exc:`OSError` if the " +"connection is closed." +msgstr "" + +#: ../Doc/library/telnetlib.rst:179 +msgid "" +"This method used to raise :exc:`socket.error`, which is now an alias of :exc:" +"`OSError`." +msgstr "" + +#: ../Doc/library/telnetlib.rst:186 +msgid "Interaction function, emulates a very dumb Telnet client." +msgstr "" + +#: ../Doc/library/telnetlib.rst:191 +msgid "Multithreaded version of :meth:`interact`." +msgstr "" + +#: ../Doc/library/telnetlib.rst:196 +msgid "Read until one from a list of a regular expressions matches." +msgstr "" + +#: ../Doc/library/telnetlib.rst:198 +msgid "" +"The first argument is a list of regular expressions, either compiled (:ref:" +"`regex objects `) or uncompiled (byte strings). The optional " +"second argument is a timeout, in seconds; the default is to block " +"indefinitely." +msgstr "" + +#: ../Doc/library/telnetlib.rst:203 +msgid "" +"Return a tuple of three items: the index in the list of the first regular " +"expression that matches; the match object returned; and the bytes read up " +"till and including the match." +msgstr "" + +#: ../Doc/library/telnetlib.rst:207 +msgid "" +"If end of file is found and no bytes were read, raise :exc:`EOFError`. " +"Otherwise, when nothing matches, return ``(-1, None, data)`` where *data* is " +"the bytes received so far (may be empty bytes if a timeout happened)." +msgstr "" + +#: ../Doc/library/telnetlib.rst:211 +msgid "" +"If a regular expression ends with a greedy match (such as ``.*``) or if more " +"than one expression can match the same input, the results are non-" +"deterministic, and may depend on the I/O timing." +msgstr "" + +#: ../Doc/library/telnetlib.rst:218 +msgid "" +"Each time a telnet option is read on the input flow, this *callback* (if " +"set) is called with the following parameters: callback(telnet socket, " +"command (DO/DONT/WILL/WONT), option). No other action is done afterwards by " +"telnetlib." +msgstr "" + +#: ../Doc/library/telnetlib.rst:226 +msgid "Telnet Example" +msgstr "" + +#: ../Doc/library/telnetlib.rst:231 +msgid "A simple example illustrating typical use::" +msgstr "" + +#: ../Doc/library/tempfile.rst:2 +msgid ":mod:`tempfile` --- Generate temporary files and directories" +msgstr "" + +#: ../Doc/library/tempfile.rst:9 +msgid "**Source code:** :source:`Lib/tempfile.py`" +msgstr "" + +#: ../Doc/library/tempfile.rst:17 +msgid "" +"This module creates temporary files and directories. It works on all " +"supported platforms. :class:`TemporaryFile`, :class:`NamedTemporaryFile`, :" +"class:`TemporaryDirectory`, and :class:`SpooledTemporaryFile` are high-level " +"interfaces which provide automatic cleanup and can be used as context " +"managers. :func:`mkstemp` and :func:`mkdtemp` are lower-level functions " +"which require manual cleanup." +msgstr "" + +#: ../Doc/library/tempfile.rst:24 +msgid "" +"All the user-callable functions and constructors take additional arguments " +"which allow direct control over the location and name of temporary files and " +"directories. Files names used by this module include a string of random " +"characters which allows those files to be securely created in shared " +"temporary directories. To maintain backward compatibility, the argument " +"order is somewhat odd; it is recommended to use keyword arguments for " +"clarity." +msgstr "" + +#: ../Doc/library/tempfile.rst:32 +msgid "The module defines the following user-callable items:" +msgstr "" + +#: ../Doc/library/tempfile.rst:36 +msgid "" +"Return a :term:`file-like object` that can be used as a temporary storage " +"area. The file is created securely, using the same rules as :func:`mkstemp`. " +"It will be destroyed as soon as it is closed (including an implicit close " +"when the object is garbage collected). Under Unix, the directory entry for " +"the file is either not created at all or is removed immediately after the " +"file is created. Other platforms do not support this; your code should not " +"rely on a temporary file created using this function having or not having a " +"visible name in the file system." +msgstr "" + +#: ../Doc/library/tempfile.rst:44 +msgid "" +"The resulting object can be used as a context manager (see :ref:`tempfile-" +"examples`). On completion of the context or destruction of the file object " +"the temporary file will be removed from the filesystem." +msgstr "" + +#: ../Doc/library/tempfile.rst:49 +msgid "" +"The *mode* parameter defaults to ``'w+b'`` so that the file created can be " +"read and written without being closed. Binary mode is used so that it " +"behaves consistently on all platforms without regard for the data that is " +"stored. *buffering*, *encoding* and *newline* are interpreted as for :func:" +"`open`." +msgstr "" + +#: ../Doc/library/tempfile.rst:55 +msgid "" +"The *dir*, *prefix* and *suffix* parameters have the same meaning and " +"defaults as with :func:`mkstemp`." +msgstr "" + +#: ../Doc/library/tempfile.rst:58 +msgid "" +"The returned object is a true file object on POSIX platforms. On other " +"platforms, it is a file-like object whose :attr:`!file` attribute is the " +"underlying true file object." +msgstr "" + +#: ../Doc/library/tempfile.rst:62 +msgid "" +"The :py:data:`os.O_TMPFILE` flag is used if it is available and works (Linux-" +"specific, requires Linux kernel 3.11 or later)." +msgstr "" + +#: ../Doc/library/tempfile.rst:67 +msgid "The :py:data:`os.O_TMPFILE` flag is now used if available." +msgstr "" + +#: ../Doc/library/tempfile.rst:72 +msgid "" +"This function operates exactly as :func:`TemporaryFile` does, except that " +"the file is guaranteed to have a visible name in the file system (on Unix, " +"the directory entry is not unlinked). That name can be retrieved from the :" +"attr:`name` attribute of the returned file-like object. Whether the name " +"can be used to open the file a second time, while the named temporary file " +"is still open, varies across platforms (it can be so used on Unix; it cannot " +"on Windows NT or later). If *delete* is true (the default), the file is " +"deleted as soon as it is closed. The returned object is always a file-like " +"object whose :attr:`!file` attribute is the underlying true file object. " +"This file-like object can be used in a :keyword:`with` statement, just like " +"a normal file." +msgstr "" + +#: ../Doc/library/tempfile.rst:88 +msgid "" +"This function operates exactly as :func:`TemporaryFile` does, except that " +"data is spooled in memory until the file size exceeds *max_size*, or until " +"the file's :func:`fileno` method is called, at which point the contents are " +"written to disk and operation proceeds as with :func:`TemporaryFile`." +msgstr "" + +#: ../Doc/library/tempfile.rst:94 +msgid "" +"The resulting file has one additional method, :func:`rollover`, which causes " +"the file to roll over to an on-disk file regardless of its size." +msgstr "" + +#: ../Doc/library/tempfile.rst:97 +msgid "" +"The returned object is a file-like object whose :attr:`_file` attribute is " +"either an :class:`io.BytesIO` or :class:`io.StringIO` object (depending on " +"whether binary or text *mode* was specified) or a true file object, " +"depending on whether :func:`rollover` has been called. This file-like " +"object can be used in a :keyword:`with` statement, just like a normal file." +msgstr "" + +#: ../Doc/library/tempfile.rst:104 +msgid "the truncate method now accepts a ``size`` argument." +msgstr "" + +#: ../Doc/library/tempfile.rst:110 +msgid "" +"This function securely creates a temporary directory using the same rules " +"as :func:`mkdtemp`. The resulting object can be used as a context manager " +"(see :ref:`tempfile-examples`). On completion of the context or destruction " +"of the temporary directory object the newly created temporary directory and " +"all its contents are removed from the filesystem." +msgstr "" + +#: ../Doc/library/tempfile.rst:116 +msgid "" +"The directory name can be retrieved from the :attr:`name` attribute of the " +"returned object. When the returned object is used as a context manager, " +"the :attr:`name` will be assigned to the target of the :keyword:`as` clause " +"in the :keyword:`with` statement, if there is one." +msgstr "" + +#: ../Doc/library/tempfile.rst:121 +msgid "" +"The directory can be explicitly cleaned up by calling the :func:`cleanup` " +"method." +msgstr "" + +#: ../Doc/library/tempfile.rst:129 +msgid "" +"Creates a temporary file in the most secure manner possible. There are no " +"race conditions in the file's creation, assuming that the platform properly " +"implements the :const:`os.O_EXCL` flag for :func:`os.open`. The file is " +"readable and writable only by the creating user ID. If the platform uses " +"permission bits to indicate whether a file is executable, the file is " +"executable by no one. The file descriptor is not inherited by child " +"processes." +msgstr "" + +#: ../Doc/library/tempfile.rst:137 +msgid "" +"Unlike :func:`TemporaryFile`, the user of :func:`mkstemp` is responsible for " +"deleting the temporary file when done with it." +msgstr "" + +#: ../Doc/library/tempfile.rst:140 +msgid "" +"If *suffix* is not ``None``, the file name will end with that suffix, " +"otherwise there will be no suffix. :func:`mkstemp` does not put a dot " +"between the file name and the suffix; if you need one, put it at the " +"beginning of *suffix*." +msgstr "" + +#: ../Doc/library/tempfile.rst:145 +msgid "" +"If *prefix* is not ``None``, the file name will begin with that prefix; " +"otherwise, a default prefix is used. The default is the return value of :" +"func:`gettempprefix` or :func:`gettempprefixb`, as appropriate." +msgstr "" + +#: ../Doc/library/tempfile.rst:149 +msgid "" +"If *dir* is not ``None``, the file will be created in that directory; " +"otherwise, a default directory is used. The default directory is chosen " +"from a platform-dependent list, but the user of the application can control " +"the directory location by setting the *TMPDIR*, *TEMP* or *TMP* environment " +"variables. There is thus no guarantee that the generated filename will have " +"any nice properties, such as not requiring quoting when passed to external " +"commands via ``os.popen()``." +msgstr "" + +#: ../Doc/library/tempfile.rst:157 +msgid "" +"If any of *suffix*, *prefix*, and *dir* are not ``None``, they must be the " +"same type. If they are bytes, the returned name will be bytes instead of " +"str. If you want to force a bytes return value with otherwise default " +"behavior, pass ``suffix=b''``." +msgstr "" + +#: ../Doc/library/tempfile.rst:163 +msgid "" +"If *text* is specified, it indicates whether to open the file in binary mode " +"(the default) or text mode. On some platforms, this makes no difference." +msgstr "" + +#: ../Doc/library/tempfile.rst:167 +msgid "" +":func:`mkstemp` returns a tuple containing an OS-level handle to an open " +"file (as would be returned by :func:`os.open`) and the absolute pathname of " +"that file, in that order." +msgstr "" + +#: ../Doc/library/tempfile.rst:171 ../Doc/library/tempfile.rst:192 +msgid "" +"*suffix*, *prefix*, and *dir* may now be supplied in bytes in order to " +"obtain a bytes return value. Prior to this, only str was allowed. *suffix* " +"and *prefix* now accept and default to ``None`` to cause an appropriate " +"default value to be used." +msgstr "" + +#: ../Doc/library/tempfile.rst:180 +msgid "" +"Creates a temporary directory in the most secure manner possible. There are " +"no race conditions in the directory's creation. The directory is readable, " +"writable, and searchable only by the creating user ID." +msgstr "" + +#: ../Doc/library/tempfile.rst:184 +msgid "" +"The user of :func:`mkdtemp` is responsible for deleting the temporary " +"directory and its contents when done with it." +msgstr "" + +#: ../Doc/library/tempfile.rst:187 +msgid "" +"The *prefix*, *suffix*, and *dir* arguments are the same as for :func:" +"`mkstemp`." +msgstr "" + +#: ../Doc/library/tempfile.rst:190 +msgid ":func:`mkdtemp` returns the absolute pathname of the new directory." +msgstr "" + +#: ../Doc/library/tempfile.rst:201 +msgid "" +"Return the name of the directory used for temporary files. This defines the " +"default value for the *dir* argument to all functions in this module." +msgstr "" + +#: ../Doc/library/tempfile.rst:205 +msgid "" +"Python searches a standard list of directories to find one which the calling " +"user can create files in. The list is:" +msgstr "" + +#: ../Doc/library/tempfile.rst:208 +msgid "The directory named by the :envvar:`TMPDIR` environment variable." +msgstr "" + +#: ../Doc/library/tempfile.rst:210 +msgid "The directory named by the :envvar:`TEMP` environment variable." +msgstr "" + +#: ../Doc/library/tempfile.rst:212 +msgid "The directory named by the :envvar:`TMP` environment variable." +msgstr "" + +#: ../Doc/library/tempfile.rst:214 +msgid "A platform-specific location:" +msgstr "" + +#: ../Doc/library/tempfile.rst:216 +msgid "" +"On Windows, the directories :file:`C:\\\\TEMP`, :file:`C:\\\\TMP`, :file:`\\" +"\\TEMP`, and :file:`\\\\TMP`, in that order." +msgstr "" + +#: ../Doc/library/tempfile.rst:219 +msgid "" +"On all other platforms, the directories :file:`/tmp`, :file:`/var/tmp`, and :" +"file:`/usr/tmp`, in that order." +msgstr "" + +#: ../Doc/library/tempfile.rst:222 +msgid "As a last resort, the current working directory." +msgstr "" + +#: ../Doc/library/tempfile.rst:224 +msgid "" +"The result of this search is cached, see the description of :data:`tempdir` " +"below." +msgstr "" + +#: ../Doc/library/tempfile.rst:229 +msgid "Same as :func:`gettempdir` but the return value is in bytes." +msgstr "" + +#: ../Doc/library/tempfile.rst:235 +msgid "" +"Return the filename prefix used to create temporary files. This does not " +"contain the directory component." +msgstr "" + +#: ../Doc/library/tempfile.rst:240 +msgid "Same as :func:`gettempprefix` but the return value is in bytes." +msgstr "" + +#: ../Doc/library/tempfile.rst:244 +msgid "" +"The module uses a global variable to store the name of the directory used " +"for temporary files returned by :func:`gettempdir`. It can be set directly " +"to override the selection process, but this is discouraged. All functions in " +"this module take a *dir* argument which can be used to specify the directory " +"and this is the recommend approach." +msgstr "" + +#: ../Doc/library/tempfile.rst:252 +msgid "" +"When set to a value other than ``None``, this variable defines the default " +"value for the *dir* argument to all the functions defined in this module." +msgstr "" + +#: ../Doc/library/tempfile.rst:256 +msgid "" +"If ``tempdir`` is unset or ``None`` at any call to any of the above " +"functions except :func:`gettempprefix` it is initialized following the " +"algorithm described in :func:`gettempdir`." +msgstr "" + +#: ../Doc/library/tempfile.rst:265 +msgid "Here are some examples of typical usage of the :mod:`tempfile` module::" +msgstr "" + +#: ../Doc/library/tempfile.rst:296 +msgid "Deprecated functions and variables" +msgstr "" + +#: ../Doc/library/tempfile.rst:298 +msgid "" +"A historical way to create temporary files was to first generate a file name " +"with the :func:`mktemp` function and then create a file using this name. " +"Unfortunately this is not secure, because a different process may create a " +"file with this name in the time between the call to :func:`mktemp` and the " +"subsequent attempt to create the file by the first process. The solution is " +"to combine the two steps and create the file immediately. This approach is " +"used by :func:`mkstemp` and the other functions described above." +msgstr "" + +#: ../Doc/library/tempfile.rst:309 +msgid "Use :func:`mkstemp` instead." +msgstr "" + +#: ../Doc/library/tempfile.rst:312 +msgid "" +"Return an absolute pathname of a file that did not exist at the time the " +"call is made. The *prefix*, *suffix*, and *dir* arguments are similar to " +"those of :func:`mkstemp`, except that bytes file names, ``suffix=None`` and " +"``prefix=None`` are not supported." +msgstr "" + +#: ../Doc/library/tempfile.rst:319 +msgid "" +"Use of this function may introduce a security hole in your program. By the " +"time you get around to doing anything with the file name it returns, someone " +"else may have beaten you to the punch. :func:`mktemp` usage can be replaced " +"easily with :func:`NamedTemporaryFile`, passing it the ``delete=False`` " +"parameter::" +msgstr "" + +#: ../Doc/library/termios.rst:2 +msgid ":mod:`termios` --- POSIX style tty control" +msgstr "" + +#: ../Doc/library/termios.rst:14 +msgid "" +"This module provides an interface to the POSIX calls for tty I/O control. " +"For a complete description of these calls, see :manpage:`termios(2)` Unix " +"manual page. It is only available for those Unix versions that support " +"POSIX *termios* style tty I/O control configured during installation." +msgstr "" + +#: ../Doc/library/termios.rst:19 +msgid "" +"All functions in this module take a file descriptor *fd* as their first " +"argument. This can be an integer file descriptor, such as returned by ``sys." +"stdin.fileno()``, or a :term:`file object`, such as ``sys.stdin`` itself." +msgstr "" + +#: ../Doc/library/termios.rst:23 +msgid "" +"This module also defines all the constants needed to work with the functions " +"provided here; these have the same name as their counterparts in C. Please " +"refer to your system documentation for more information on using these " +"terminal control interfaces." +msgstr "" + +#: ../Doc/library/termios.rst:33 +msgid "" +"Return a list containing the tty attributes for file descriptor *fd*, as " +"follows: ``[iflag, oflag, cflag, lflag, ispeed, ospeed, cc]`` where *cc* is " +"a list of the tty special characters (each a string of length 1, except the " +"items with indices :const:`VMIN` and :const:`VTIME`, which are integers when " +"these fields are defined). The interpretation of the flags and the speeds " +"as well as the indexing in the *cc* array must be done using the symbolic " +"constants defined in the :mod:`termios` module." +msgstr "" + +#: ../Doc/library/termios.rst:44 +msgid "" +"Set the tty attributes for file descriptor *fd* from the *attributes*, which " +"is a list like the one returned by :func:`tcgetattr`. The *when* argument " +"determines when the attributes are changed: :const:`TCSANOW` to change " +"immediately, :const:`TCSADRAIN` to change after transmitting all queued " +"output, or :const:`TCSAFLUSH` to change after transmitting all queued output " +"and discarding all queued input." +msgstr "" + +#: ../Doc/library/termios.rst:54 +msgid "" +"Send a break on file descriptor *fd*. A zero *duration* sends a break for " +"0.25 --0.5 seconds; a nonzero *duration* has a system dependent meaning." +msgstr "" + +#: ../Doc/library/termios.rst:60 +msgid "" +"Wait until all output written to file descriptor *fd* has been transmitted." +msgstr "" + +#: ../Doc/library/termios.rst:65 +msgid "" +"Discard queued data on file descriptor *fd*. The *queue* selector specifies " +"which queue: :const:`TCIFLUSH` for the input queue, :const:`TCOFLUSH` for " +"the output queue, or :const:`TCIOFLUSH` for both queues." +msgstr "" + +#: ../Doc/library/termios.rst:72 +msgid "" +"Suspend or resume input or output on file descriptor *fd*. The *action* " +"argument can be :const:`TCOOFF` to suspend output, :const:`TCOON` to restart " +"output, :const:`TCIOFF` to suspend input, or :const:`TCION` to restart input." +msgstr "" + +#: ../Doc/library/termios.rst:79 +msgid "Module :mod:`tty`" +msgstr "" + +#: ../Doc/library/termios.rst:80 +msgid "Convenience functions for common terminal control operations." +msgstr "" + +#: ../Doc/library/termios.rst:88 +msgid "" +"Here's a function that prompts for a password with echoing turned off. Note " +"the technique using a separate :func:`tcgetattr` call and a :keyword:" +"`try` ... :keyword:`finally` statement to ensure that the old tty attributes " +"are restored exactly no matter what happens::" +msgstr "" + +#: ../Doc/library/test.rst:2 +msgid ":mod:`test` --- Regression tests package for Python" +msgstr "" + +#: ../Doc/library/test.rst:10 +msgid "" +"The :mod:`test` package is meant for internal use by Python only. It is " +"documented for the benefit of the core developers of Python. Any use of this " +"package outside of Python's standard library is discouraged as code " +"mentioned here can change or be removed without notice between releases of " +"Python." +msgstr "" + +#: ../Doc/library/test.rst:18 +msgid "" +"The :mod:`test` package contains all regression tests for Python as well as " +"the modules :mod:`test.support` and :mod:`test.regrtest`. :mod:`test." +"support` is used to enhance your tests while :mod:`test.regrtest` drives the " +"testing suite." +msgstr "" + +#: ../Doc/library/test.rst:23 +msgid "" +"Each module in the :mod:`test` package whose name starts with ``test_`` is a " +"testing suite for a specific module or feature. All new tests should be " +"written using the :mod:`unittest` or :mod:`doctest` module. Some older " +"tests are written using a \"traditional\" testing style that compares output " +"printed to ``sys.stdout``; this style of test is considered deprecated." +msgstr "" + +#: ../Doc/library/test.rst:33 +msgid "Module :mod:`unittest`" +msgstr "" + +#: ../Doc/library/test.rst:33 +msgid "Writing PyUnit regression tests." +msgstr "" + +#: ../Doc/library/test.rst:35 ../Doc/library/unittest.rst:53 +msgid "Module :mod:`doctest`" +msgstr "" + +#: ../Doc/library/test.rst:36 +msgid "Tests embedded in documentation strings." +msgstr "" + +#: ../Doc/library/test.rst:42 +msgid "Writing Unit Tests for the :mod:`test` package" +msgstr "" + +#: ../Doc/library/test.rst:44 +msgid "" +"It is preferred that tests that use the :mod:`unittest` module follow a few " +"guidelines. One is to name the test module by starting it with ``test_`` and " +"end it with the name of the module being tested. The test methods in the " +"test module should start with ``test_`` and end with a description of what " +"the method is testing. This is needed so that the methods are recognized by " +"the test driver as test methods. Also, no documentation string for the " +"method should be included. A comment (such as ``# Tests function returns " +"only True or False``) should be used to provide documentation for test " +"methods. This is done because documentation strings get printed out if they " +"exist and thus what test is being run is not stated." +msgstr "" + +#: ../Doc/library/test.rst:55 +msgid "A basic boilerplate is often used::" +msgstr "" + +#: ../Doc/library/test.rst:88 +msgid "" +"This code pattern allows the testing suite to be run by :mod:`test." +"regrtest`, on its own as a script that supports the :mod:`unittest` CLI, or " +"via the ``python -m unittest`` CLI." +msgstr "" + +#: ../Doc/library/test.rst:92 +msgid "" +"The goal for regression testing is to try to break code. This leads to a few " +"guidelines to be followed:" +msgstr "" + +#: ../Doc/library/test.rst:95 +msgid "" +"The testing suite should exercise all classes, functions, and constants. " +"This includes not just the external API that is to be presented to the " +"outside world but also \"private\" code." +msgstr "" + +#: ../Doc/library/test.rst:99 +msgid "" +"Whitebox testing (examining the code being tested when the tests are being " +"written) is preferred. Blackbox testing (testing only the published user " +"interface) is not complete enough to make sure all boundary and edge cases " +"are tested." +msgstr "" + +#: ../Doc/library/test.rst:104 +msgid "" +"Make sure all possible values are tested including invalid ones. This makes " +"sure that not only all valid values are acceptable but also that improper " +"values are handled correctly." +msgstr "" + +#: ../Doc/library/test.rst:108 +msgid "" +"Exhaust as many code paths as possible. Test where branching occurs and thus " +"tailor input to make sure as many different paths through the code are taken." +msgstr "" + +#: ../Doc/library/test.rst:111 +msgid "" +"Add an explicit test for any bugs discovered for the tested code. This will " +"make sure that the error does not crop up again if the code is changed in " +"the future." +msgstr "" + +#: ../Doc/library/test.rst:115 +msgid "" +"Make sure to clean up after your tests (such as close and remove all " +"temporary files)." +msgstr "" + +#: ../Doc/library/test.rst:118 +msgid "" +"If a test is dependent on a specific condition of the operating system then " +"verify the condition already exists before attempting the test." +msgstr "" + +#: ../Doc/library/test.rst:121 +msgid "" +"Import as few modules as possible and do it as soon as possible. This " +"minimizes external dependencies of tests and also minimizes possible " +"anomalous behavior from side-effects of importing a module." +msgstr "" + +#: ../Doc/library/test.rst:125 +msgid "" +"Try to maximize code reuse. On occasion, tests will vary by something as " +"small as what type of input is used. Minimize code duplication by " +"subclassing a basic test class with a class that specifies the input::" +msgstr "" + +#: ../Doc/library/test.rst:145 +msgid "" +"When using this pattern, remember that all classes that inherit from :class:" +"`unittest.TestCase` are run as tests. The :class:`Mixin` class in the " +"example above does not have any data and so can't be run by itself, thus it " +"does not inherit from :class:`unittest.TestCase`." +msgstr "" + +#: ../Doc/library/test.rst:153 +msgid "Test Driven Development" +msgstr "" + +#: ../Doc/library/test.rst:154 +msgid "A book by Kent Beck on writing tests before code." +msgstr "" + +#: ../Doc/library/test.rst:160 +msgid "Running tests using the command-line interface" +msgstr "" + +#: ../Doc/library/test.rst:162 +msgid "" +"The :mod:`test` package can be run as a script to drive Python's regression " +"test suite, thanks to the :option:`-m` option: :program:`python -m test`. " +"Under the hood, it uses :mod:`test.regrtest`; the call :program:`python -m " +"test.regrtest` used in previous Python versions still works. Running the " +"script by itself automatically starts running all regression tests in the :" +"mod:`test` package. It does this by finding all modules in the package whose " +"name starts with ``test_``, importing them, and executing the function :func:" +"`test_main` if present or loading the tests via unittest.TestLoader." +"loadTestsFromModule if ``test_main`` does not exist. The names of tests to " +"execute may also be passed to the script. Specifying a single regression " +"test (:program:`python -m test test_spam`) will minimize output and only " +"print whether the test passed or failed." +msgstr "" + +#: ../Doc/library/test.rst:175 +msgid "" +"Running :mod:`test` directly allows what resources are available for tests " +"to use to be set. You do this by using the ``-u`` command-line option. " +"Specifying ``all`` as the value for the ``-u`` option enables all possible " +"resources: :program:`python -m test -uall`. If all but one resource is " +"desired (a more common case), a comma-separated list of resources that are " +"not desired may be listed after ``all``. The command :program:`python -m " +"test -uall,-audio,-largefile` will run :mod:`test` with all resources except " +"the ``audio`` and ``largefile`` resources. For a list of all resources and " +"more command-line options, run :program:`python -m test -h`." +msgstr "" + +#: ../Doc/library/test.rst:186 +msgid "" +"Some other ways to execute the regression tests depend on what platform the " +"tests are being executed on. On Unix, you can run :program:`make test` at " +"the top-level directory where Python was built. On Windows, executing :" +"program:`rt.bat` from your :file:`PCBuild` directory will run all regression " +"tests." +msgstr "" + +#: ../Doc/library/test.rst:194 +msgid ":mod:`test.support` --- Utilities for the Python test suite" +msgstr "" + +#: ../Doc/library/test.rst:200 +msgid "" +"The :mod:`test.support` module provides support for Python's regression test " +"suite." +msgstr "" + +#: ../Doc/library/test.rst:205 +msgid "" +":mod:`test.support` is not a public module. It is documented here to help " +"Python developers write tests. The API of this module is subject to change " +"without backwards compatibility concerns between releases." +msgstr "" + +#: ../Doc/library/test.rst:210 +msgid "This module defines the following exceptions:" +msgstr "" + +#: ../Doc/library/test.rst:214 +msgid "" +"Exception to be raised when a test fails. This is deprecated in favor of :" +"mod:`unittest`\\ -based tests and :class:`unittest.TestCase`'s assertion " +"methods." +msgstr "" + +#: ../Doc/library/test.rst:221 +msgid "" +"Subclass of :exc:`unittest.SkipTest`. Raised when a resource (such as a " +"network connection) is not available. Raised by the :func:`requires` " +"function." +msgstr "" + +#: ../Doc/library/test.rst:226 +msgid "The :mod:`test.support` module defines the following constants:" +msgstr "" + +#: ../Doc/library/test.rst:230 +msgid "" +"``True`` when verbose output is enabled. Should be checked when more " +"detailed information is desired about a running test. *verbose* is set by :" +"mod:`test.regrtest`." +msgstr "" + +#: ../Doc/library/test.rst:237 +msgid "``True`` if the running interpreter is Jython." +msgstr "" + +#: ../Doc/library/test.rst:242 +msgid "" +"Set to a name that is safe to use as the name of a temporary file. Any " +"temporary file that is created should be closed and unlinked (removed)." +msgstr "" + +#: ../Doc/library/test.rst:246 +msgid "The :mod:`test.support` module defines the following functions:" +msgstr "" + +#: ../Doc/library/test.rst:250 +msgid "" +"Remove the module named *module_name* from ``sys.modules`` and delete any " +"byte-compiled files of the module." +msgstr "" + +#: ../Doc/library/test.rst:256 +msgid "" +"Return ``True`` if *resource* is enabled and available. The list of " +"available resources is only set when :mod:`test.regrtest` is executing the " +"tests." +msgstr "" + +#: ../Doc/library/test.rst:263 +msgid "" +"Raise :exc:`ResourceDenied` if *resource* is not available. *msg* is the " +"argument to :exc:`ResourceDenied` if it is raised. Always returns ``True`` " +"if called by a function whose ``__name__`` is ``'__main__'``. Used when " +"tests are executed by :mod:`test.regrtest`." +msgstr "" + +#: ../Doc/library/test.rst:271 +msgid "" +"Return the path to the file named *filename*. If no match is found " +"*filename* is returned. This does not equal a failure since it could be the " +"path to the file." +msgstr "" + +#: ../Doc/library/test.rst:275 +msgid "" +"Setting *subdir* indicates a relative path to use to find the file rather " +"than looking directly in the path directories." +msgstr "" + +#: ../Doc/library/test.rst:281 +msgid "" +"Execute :class:`unittest.TestCase` subclasses passed to the function. The " +"function scans the classes for methods starting with the prefix ``test_`` " +"and executes the tests individually." +msgstr "" + +#: ../Doc/library/test.rst:285 +msgid "" +"It is also legal to pass strings as parameters; these should be keys in " +"``sys.modules``. Each associated module will be scanned by ``unittest." +"TestLoader.loadTestsFromModule()``. This is usually seen in the following :" +"func:`test_main` function::" +msgstr "" + +#: ../Doc/library/test.rst:293 +msgid "This will run all tests defined in the named module." +msgstr "" + +#: ../Doc/library/test.rst:298 +msgid "" +"Run :func:`doctest.testmod` on the given *module*. Return ``(failure_count, " +"test_count)``." +msgstr "" + +#: ../Doc/library/test.rst:301 +msgid "" +"If *verbosity* is ``None``, :func:`doctest.testmod` is run with verbosity " +"set to :data:`verbose`. Otherwise, it is run with verbosity set to ``None``." +msgstr "" + +#: ../Doc/library/test.rst:307 +msgid "" +"A convenience wrapper for :func:`warnings.catch_warnings()` that makes it " +"easier to test that a warning was correctly raised. It is approximately " +"equivalent to calling ``warnings.catch_warnings(record=True)`` with :meth:" +"`warnings.simplefilter` set to ``always`` and with the option to " +"automatically validate the results that are recorded." +msgstr "" + +#: ../Doc/library/test.rst:313 +msgid "" +"``check_warnings`` accepts 2-tuples of the form ``(\"message regexp\", " +"WarningCategory)`` as positional arguments. If one or more *filters* are " +"provided, or if the optional keyword argument *quiet* is ``False``, it " +"checks to make sure the warnings are as expected: each specified filter " +"must match at least one of the warnings raised by the enclosed code or the " +"test fails, and if any warnings are raised that do not match any of the " +"specified filters the test fails. To disable the first of these checks, set " +"*quiet* to ``True``." +msgstr "" + +#: ../Doc/library/test.rst:322 +msgid "If no arguments are specified, it defaults to::" +msgstr "" + +#: ../Doc/library/test.rst:326 +msgid "In this case all warnings are caught and no errors are raised." +msgstr "" + +#: ../Doc/library/test.rst:328 +msgid "" +"On entry to the context manager, a :class:`WarningRecorder` instance is " +"returned. The underlying warnings list from :func:`~warnings.catch_warnings` " +"is available via the recorder object's :attr:`warnings` attribute. As a " +"convenience, the attributes of the object representing the most recent " +"warning can also be accessed directly through the recorder object (see " +"example below). If no warning has been raised, then any of the attributes " +"that would otherwise be expected on an object representing a warning will " +"return ``None``." +msgstr "" + +#: ../Doc/library/test.rst:337 +msgid "" +"The recorder object also has a :meth:`reset` method, which clears the " +"warnings list." +msgstr "" + +#: ../Doc/library/test.rst:340 +msgid "The context manager is designed to be used like this::" +msgstr "" + +#: ../Doc/library/test.rst:347 +msgid "" +"In this case if either warning was not raised, or some other warning was " +"raised, :func:`check_warnings` would raise an error." +msgstr "" + +#: ../Doc/library/test.rst:350 +msgid "" +"When a test needs to look more deeply into the warnings, rather than just " +"checking whether or not they occurred, code like this can be used::" +msgstr "" + +#: ../Doc/library/test.rst:364 +msgid "" +"Here all warnings will be caught, and the test code tests the captured " +"warnings directly." +msgstr "" + +#: ../Doc/library/test.rst:367 +msgid "New optional arguments *filters* and *quiet*." +msgstr "" + +#: ../Doc/library/test.rst:375 +msgid "" +"A context managers that temporarily replaces the named stream with :class:" +"`io.StringIO` object." +msgstr "" + +#: ../Doc/library/test.rst:378 +msgid "Example use with output streams::" +msgstr "" + +#: ../Doc/library/test.rst:386 +msgid "Example use with input stream::" +msgstr "" + +#: ../Doc/library/test.rst:398 +msgid "" +"A context manager that creates a temporary directory at *path* and yields " +"the directory." +msgstr "" + +#: ../Doc/library/test.rst:401 +msgid "" +"If *path* is None, the temporary directory is created using :func:`tempfile." +"mkdtemp`. If *quiet* is ``False``, the context manager raises an exception " +"on error. Otherwise, if *path* is specified and cannot be created, only a " +"warning is issued." +msgstr "" + +#: ../Doc/library/test.rst:409 +msgid "" +"A context manager that temporarily changes the current working directory to " +"*path* and yields the directory." +msgstr "" + +#: ../Doc/library/test.rst:412 +msgid "" +"If *quiet* is ``False``, the context manager raises an exception on error. " +"Otherwise, it issues only a warning and keeps the current working directory " +"the same." +msgstr "" + +#: ../Doc/library/test.rst:419 +msgid "" +"A context manager that temporarily creates a new directory and changes the " +"current working directory (CWD)." +msgstr "" + +#: ../Doc/library/test.rst:422 +msgid "" +"The context manager creates a temporary directory in the current directory " +"with name *name* before temporarily changing the current working directory. " +"If *name* is None, the temporary directory is created using :func:`tempfile." +"mkdtemp`." +msgstr "" + +#: ../Doc/library/test.rst:427 +msgid "" +"If *quiet* is ``False`` and it is not possible to create or change the CWD, " +"an error is raised. Otherwise, only a warning is raised and the original " +"CWD is used." +msgstr "" + +#: ../Doc/library/test.rst:434 +msgid "A context manager that temporarily sets the process umask." +msgstr "" + +#: ../Doc/library/test.rst:439 +msgid "Return ``True`` if the OS supports symbolic links, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/test.rst:445 +msgid "A decorator for running tests that require support for symbolic links." +msgstr "" + +#: ../Doc/library/test.rst:450 +msgid "" +"A decorator to conditionally mark tests with :func:`unittest." +"expectedFailure`. Any use of this decorator should have an associated " +"comment identifying the relevant tracker issue." +msgstr "" + +#: ../Doc/library/test.rst:457 +msgid "" +"A decorator for running a function in a different locale, correctly " +"resetting it after it has finished. *catstr* is the locale category as a " +"string (for example ``\"LC_ALL\"``). The *locales* passed will be tried " +"sequentially, and the first valid locale will be used." +msgstr "" + +#: ../Doc/library/test.rst:465 +msgid "" +"Create an invalid file descriptor by opening and closing a temporary file, " +"and returning its descriptor." +msgstr "" + +#: ../Doc/library/test.rst:471 +msgid "" +"This function imports and returns the named module. Unlike a normal import, " +"this function raises :exc:`unittest.SkipTest` if the module cannot be " +"imported." +msgstr "" + +#: ../Doc/library/test.rst:475 ../Doc/library/test.rst:499 +msgid "" +"Module and package deprecation messages are suppressed during this import if " +"*deprecated* is ``True``." +msgstr "" + +#: ../Doc/library/test.rst:483 +msgid "" +"This function imports and returns a fresh copy of the named Python module by " +"removing the named module from ``sys.modules`` before doing the import. Note " +"that unlike :func:`reload`, the original module is not affected by this " +"operation." +msgstr "" + +#: ../Doc/library/test.rst:488 +msgid "" +"*fresh* is an iterable of additional module names that are also removed from " +"the ``sys.modules`` cache before doing the import." +msgstr "" + +#: ../Doc/library/test.rst:491 +msgid "" +"*blocked* is an iterable of module names that are replaced with ``None`` in " +"the module cache during the import to ensure that attempts to import them " +"raise :exc:`ImportError`." +msgstr "" + +#: ../Doc/library/test.rst:495 +msgid "" +"The named module and any modules named in the *fresh* and *blocked* " +"parameters are saved before starting the import and then reinserted into " +"``sys.modules`` when the fresh import is complete." +msgstr "" + +#: ../Doc/library/test.rst:502 +msgid "" +"This function will raise :exc:`ImportError` if the named module cannot be " +"imported." +msgstr "" + +#: ../Doc/library/test.rst:505 ../Doc/library/test.rst:605 +msgid "Example use::" +msgstr "" + +#: ../Doc/library/test.rst:519 +msgid "" +"Bind the socket to a free port and return the port number. Relies on " +"ephemeral ports in order to ensure we are using an unbound port. This is " +"important as many tests may be running simultaneously, especially in a " +"buildbot environment. This method raises an exception if the ``sock." +"family`` is :const:`~socket.AF_INET` and ``sock.type`` is :const:`~socket." +"SOCK_STREAM`, and the socket has :const:`~socket.SO_REUSEADDR` or :const:" +"`~socket.SO_REUSEPORT` set on it. Tests should never set these socket " +"options for TCP/IP sockets. The only case for setting these options is " +"testing multicasting via multiple UDP sockets." +msgstr "" + +#: ../Doc/library/test.rst:530 +msgid "" +"Additionally, if the :const:`~socket.SO_EXCLUSIVEADDRUSE` socket option is " +"available (i.e. on Windows), it will be set on the socket. This will " +"prevent anyone else from binding to our host/port for the duration of the " +"test." +msgstr "" + +#: ../Doc/library/test.rst:538 +msgid "" +"Returns an unused port that should be suitable for binding. This is " +"achieved by creating a temporary socket with the same family and type as the " +"``sock`` parameter (default is :const:`~socket.AF_INET`, :const:`~socket." +"SOCK_STREAM`), and binding it to the specified host address (defaults to " +"``0.0.0.0``) with the port set to 0, eliciting an unused ephemeral port from " +"the OS. The temporary socket is then closed and deleted, and the ephemeral " +"port is returned." +msgstr "" + +#: ../Doc/library/test.rst:547 +msgid "" +"Either this method or :func:`bind_port` should be used for any tests where a " +"server socket needs to be bound to a particular port for the duration of the " +"test. Which one to use depends on whether the calling code is creating a " +"python socket, or if an unused port needs to be provided in a constructor or " +"passed to an external program (i.e. the ``-accept`` argument to openssl's " +"s_server mode). Always prefer :func:`bind_port` over :func:" +"`find_unused_port` where possible. Using a hard coded port is discouraged " +"since it can make multiple instances of the test impossible to run " +"simultaneously, which is a problem for buildbots." +msgstr "" + +#: ../Doc/library/test.rst:561 +msgid "" +"Generic implementation of the :mod:`unittest` ``load_tests`` protocol for " +"use in test packages. *pkg_dir* is the root directory of the package; " +"*loader*, *standard_tests*, and *pattern* are the arguments expected by " +"``load_tests``. In simple cases, the test package's ``__init__.py`` can be " +"the following::" +msgstr "" + +#: ../Doc/library/test.rst:575 +msgid "" +"Returns the set of attributes, functions or methods of *ref_api* not found " +"on *other_api*, except for a defined list of items to be ignored in this " +"check specified in *ignore*." +msgstr "" + +#: ../Doc/library/test.rst:579 +msgid "" +"By default this skips private attributes beginning with '_' but includes all " +"magic methods, i.e. those starting and ending in '__'." +msgstr "" + +#: ../Doc/library/test.rst:587 +msgid "" +"Assert that the ``__all__`` variable of *module* contains all public names." +msgstr "" + +#: ../Doc/library/test.rst:589 +msgid "" +"The module's public names (its API) are detected automatically based on " +"whether they match the public name convention and were defined in *module*." +msgstr "" + +#: ../Doc/library/test.rst:593 +msgid "" +"The *name_of_module* argument can specify (as a string or tuple thereof) " +"what module(s) an API could be defined in in order to be detected as a " +"public API. One case for this is when *module* imports part of its public " +"API from other modules, possibly a C backend (like ``csv`` and its ``_csv``)." +msgstr "" + +#: ../Doc/library/test.rst:598 +msgid "" +"The *extra* argument can be a set of names that wouldn't otherwise be " +"automatically detected as \"public\", like objects without a proper " +"``__module__`` attribute. If provided, it will be added to the automatically " +"detected ones." +msgstr "" + +#: ../Doc/library/test.rst:602 +msgid "" +"The *blacklist* argument can be a set of names that must not be treated as " +"part of the public API even though their names indicate otherwise." +msgstr "" + +#: ../Doc/library/test.rst:627 +msgid "The :mod:`test.support` module defines the following classes:" +msgstr "" + +#: ../Doc/library/test.rst:631 +msgid "" +"Instances are a context manager that raises :exc:`ResourceDenied` if the " +"specified exception type is raised. Any keyword arguments are treated as " +"attribute/value pairs to be compared against any exception raised within " +"the :keyword:`with` statement. Only if all pairs match properly against " +"attributes on the exception is :exc:`ResourceDenied` raised." +msgstr "" + +#: ../Doc/library/test.rst:640 +msgid "" +"Class used to temporarily set or unset environment variables. Instances can " +"be used as a context manager and have a complete dictionary interface for " +"querying/modifying the underlying ``os.environ``. After exit from the " +"context manager all changes to environment variables done through this " +"instance will be rolled back." +msgstr "" + +#: ../Doc/library/test.rst:646 +msgid "Added dictionary interface." +msgstr "" + +#: ../Doc/library/test.rst:651 +msgid "" +"Temporarily set the environment variable ``envvar`` to the value of " +"``value``." +msgstr "" + +#: ../Doc/library/test.rst:657 +msgid "Temporarily unset the environment variable ``envvar``." +msgstr "" + +#: ../Doc/library/test.rst:662 +msgid "" +"A context manager used to try to prevent crash dialog popups on tests that " +"are expected to crash a subprocess." +msgstr "" + +#: ../Doc/library/test.rst:665 +msgid "" +"On Windows, it disables Windows Error Reporting dialogs using `SetErrorMode " +"`_." +msgstr "" + +#: ../Doc/library/test.rst:668 +msgid "" +"On UNIX, :func:`resource.setrlimit` is used to set :attr:`resource." +"RLIMIT_CORE`'s soft limit to 0 to prevent coredump file creation." +msgstr "" + +#: ../Doc/library/test.rst:672 +msgid "On both platforms, the old value is restored by :meth:`__exit__`." +msgstr "" + +#: ../Doc/library/test.rst:677 +msgid "" +"Class used to record warnings for unit tests. See documentation of :func:" +"`check_warnings` above for more details." +msgstr "" + +#: ../Doc/library/text.rst:6 +msgid "Text Processing Services" +msgstr "" + +#: ../Doc/library/text.rst:8 +msgid "" +"The modules described in this chapter provide a wide range of string " +"manipulation operations and other text processing services." +msgstr "" + +#: ../Doc/library/text.rst:11 +msgid "" +"The :mod:`codecs` module described under :ref:`binaryservices` is also " +"highly relevant to text processing. In addition, see the documentation for " +"Python's built-in string type in :ref:`textseq`." +msgstr "" + +#: ../Doc/library/textwrap.rst:2 +msgid ":mod:`textwrap` --- Text wrapping and filling" +msgstr "" + +#: ../Doc/library/textwrap.rst:10 +msgid "**Source code:** :source:`Lib/textwrap.py`" +msgstr "" + +#: ../Doc/library/textwrap.rst:14 +msgid "" +"The :mod:`textwrap` module provides some convenience functions, as well as :" +"class:`TextWrapper`, the class that does all the work. If you're just " +"wrapping or filling one or two text strings, the convenience functions " +"should be good enough; otherwise, you should use an instance of :class:" +"`TextWrapper` for efficiency." +msgstr "" + +#: ../Doc/library/textwrap.rst:22 +msgid "" +"Wraps the single paragraph in *text* (a string) so every line is at most " +"*width* characters long. Returns a list of output lines, without final " +"newlines." +msgstr "" + +#: ../Doc/library/textwrap.rst:26 +msgid "" +"Optional keyword arguments correspond to the instance attributes of :class:" +"`TextWrapper`, documented below. *width* defaults to ``70``." +msgstr "" + +#: ../Doc/library/textwrap.rst:29 +msgid "" +"See the :meth:`TextWrapper.wrap` method for additional details on how :func:" +"`wrap` behaves." +msgstr "" + +#: ../Doc/library/textwrap.rst:35 +msgid "" +"Wraps the single paragraph in *text*, and returns a single string containing " +"the wrapped paragraph. :func:`fill` is shorthand for ::" +msgstr "" + +#: ../Doc/library/textwrap.rst:40 +msgid "" +"In particular, :func:`fill` accepts exactly the same keyword arguments as :" +"func:`wrap`." +msgstr "" + +#: ../Doc/library/textwrap.rst:46 +msgid "Collapse and truncate the given *text* to fit in the given *width*." +msgstr "" + +#: ../Doc/library/textwrap.rst:48 +msgid "" +"First the whitespace in *text* is collapsed (all whitespace is replaced by " +"single spaces). If the result fits in the *width*, it is returned. " +"Otherwise, enough words are dropped from the end so that the remaining words " +"plus the :attr:`placeholder` fit within :attr:`width`::" +msgstr "" + +#: ../Doc/library/textwrap.rst:60 +msgid "" +"Optional keyword arguments correspond to the instance attributes of :class:" +"`TextWrapper`, documented below. Note that the whitespace is collapsed " +"before the text is passed to the :class:`TextWrapper` :meth:`fill` function, " +"so changing the value of :attr:`.tabsize`, :attr:`.expand_tabs`, :attr:`." +"drop_whitespace`, and :attr:`.replace_whitespace` will have no effect." +msgstr "" + +#: ../Doc/library/textwrap.rst:71 +msgid "Remove any common leading whitespace from every line in *text*." +msgstr "" + +#: ../Doc/library/textwrap.rst:73 +msgid "" +"This can be used to make triple-quoted strings line up with the left edge of " +"the display, while still presenting them in the source code in indented form." +msgstr "" + +#: ../Doc/library/textwrap.rst:76 +msgid "" +"Note that tabs and spaces are both treated as whitespace, but they are not " +"equal: the lines ``\" hello\"`` and ``\"\\thello\"`` are considered to have " +"no common leading whitespace." +msgstr "" + +#: ../Doc/library/textwrap.rst:94 +msgid "Add *prefix* to the beginning of selected lines in *text*." +msgstr "" + +#: ../Doc/library/textwrap.rst:96 +msgid "Lines are separated by calling ``text.splitlines(True)``." +msgstr "" + +#: ../Doc/library/textwrap.rst:98 +msgid "" +"By default, *prefix* is added to all lines that do not consist solely of " +"whitespace (including any line endings)." +msgstr "" + +#: ../Doc/library/textwrap.rst:107 +msgid "" +"The optional *predicate* argument can be used to control which lines are " +"indented. For example, it is easy to add *prefix* to even empty and " +"whitespace-only lines::" +msgstr "" + +#: ../Doc/library/textwrap.rst:120 +msgid "" +":func:`wrap`, :func:`fill` and :func:`shorten` work by creating a :class:" +"`TextWrapper` instance and calling a single method on it. That instance is " +"not reused, so for applications that process many text strings using :func:" +"`wrap` and/or :func:`fill`, it may be more efficient to create your own :" +"class:`TextWrapper` object." +msgstr "" + +#: ../Doc/library/textwrap.rst:126 +msgid "" +"Text is preferably wrapped on whitespaces and right after the hyphens in " +"hyphenated words; only then will long words be broken if necessary, unless :" +"attr:`TextWrapper.break_long_words` is set to false." +msgstr "" + +#: ../Doc/library/textwrap.rst:132 +msgid "" +"The :class:`TextWrapper` constructor accepts a number of optional keyword " +"arguments. Each keyword argument corresponds to an instance attribute, so " +"for example ::" +msgstr "" + +#: ../Doc/library/textwrap.rst:138 +msgid "is the same as ::" +msgstr "" + +#: ../Doc/library/textwrap.rst:143 +msgid "" +"You can re-use the same :class:`TextWrapper` object many times, and you can " +"change any of its options through direct assignment to instance attributes " +"between uses." +msgstr "" + +#: ../Doc/library/textwrap.rst:147 +msgid "" +"The :class:`TextWrapper` instance attributes (and keyword arguments to the " +"constructor) are as follows:" +msgstr "" + +#: ../Doc/library/textwrap.rst:153 +msgid "" +"(default: ``70``) The maximum length of wrapped lines. As long as there are " +"no individual words in the input text longer than :attr:`width`, :class:" +"`TextWrapper` guarantees that no output line will be longer than :attr:" +"`width` characters." +msgstr "" + +#: ../Doc/library/textwrap.rst:161 +msgid "" +"(default: ``True``) If true, then all tab characters in *text* will be " +"expanded to spaces using the :meth:`expandtabs` method of *text*." +msgstr "" + +#: ../Doc/library/textwrap.rst:167 +msgid "" +"(default: ``8``) If :attr:`expand_tabs` is true, then all tab characters in " +"*text* will be expanded to zero or more spaces, depending on the current " +"column and the given tab size." +msgstr "" + +#: ../Doc/library/textwrap.rst:176 +msgid "" +"(default: ``True``) If true, after tab expansion but before wrapping, the :" +"meth:`wrap` method will replace each whitespace character with a single " +"space. The whitespace characters replaced are as follows: tab, newline, " +"vertical tab, formfeed, and carriage return (``'\\t\\n\\v\\f\\r'``)." +msgstr "" + +#: ../Doc/library/textwrap.rst:184 +msgid "" +"If :attr:`expand_tabs` is false and :attr:`replace_whitespace` is true, each " +"tab character will be replaced by a single space, which is *not* the same as " +"tab expansion." +msgstr "" + +#: ../Doc/library/textwrap.rst:190 +msgid "" +"If :attr:`replace_whitespace` is false, newlines may appear in the middle of " +"a line and cause strange output. For this reason, text should be split into " +"paragraphs (using :meth:`str.splitlines` or similar) which are wrapped " +"separately." +msgstr "" + +#: ../Doc/library/textwrap.rst:198 +msgid "" +"(default: ``True``) If true, whitespace at the beginning and ending of every " +"line (after wrapping but before indenting) is dropped. Whitespace at the " +"beginning of the paragraph, however, is not dropped if non-whitespace " +"follows it. If whitespace being dropped takes up an entire line, the whole " +"line is dropped." +msgstr "" + +#: ../Doc/library/textwrap.rst:207 +msgid "" +"(default: ``''``) String that will be prepended to the first line of wrapped " +"output. Counts towards the length of the first line. The empty string is " +"not indented." +msgstr "" + +#: ../Doc/library/textwrap.rst:214 +msgid "" +"(default: ``''``) String that will be prepended to all lines of wrapped " +"output except the first. Counts towards the length of each line except the " +"first." +msgstr "" + +#: ../Doc/library/textwrap.rst:221 +msgid "" +"(default: ``False``) If true, :class:`TextWrapper` attempts to detect " +"sentence endings and ensure that sentences are always separated by exactly " +"two spaces. This is generally desired for text in a monospaced font. " +"However, the sentence detection algorithm is imperfect: it assumes that a " +"sentence ending consists of a lowercase letter followed by one of ``'.'``, " +"``'!'``, or ``'?'``, possibly followed by one of ``'\"'`` or ``\"'\"``, " +"followed by a space. One problem with this is algorithm is that it is " +"unable to detect the difference between \"Dr.\" in ::" +msgstr "" + +#: ../Doc/library/textwrap.rst:232 +msgid "and \"Spot.\" in ::" +msgstr "" + +#: ../Doc/library/textwrap.rst:236 +msgid ":attr:`fix_sentence_endings` is false by default." +msgstr "" + +#: ../Doc/library/textwrap.rst:238 +msgid "" +"Since the sentence detection algorithm relies on ``string.lowercase`` for " +"the definition of \"lowercase letter,\" and a convention of using two spaces " +"after a period to separate sentences on the same line, it is specific to " +"English-language texts." +msgstr "" + +#: ../Doc/library/textwrap.rst:246 +msgid "" +"(default: ``True``) If true, then words longer than :attr:`width` will be " +"broken in order to ensure that no lines are longer than :attr:`width`. If " +"it is false, long words will not be broken, and some lines may be longer " +"than :attr:`width`. (Long words will be put on a line by themselves, in " +"order to minimize the amount by which :attr:`width` is exceeded.)" +msgstr "" + +#: ../Doc/library/textwrap.rst:255 +msgid "" +"(default: ``True``) If true, wrapping will occur preferably on whitespaces " +"and right after hyphens in compound words, as it is customary in English. If " +"false, only whitespaces will be considered as potentially good places for " +"line breaks, but you need to set :attr:`break_long_words` to false if you " +"want truly insecable words. Default behaviour in previous versions was to " +"always allow breaking hyphenated words." +msgstr "" + +#: ../Doc/library/textwrap.rst:265 +msgid "" +"(default: ``None``) If not ``None``, then the output will contain at most " +"*max_lines* lines, with *placeholder* appearing at the end of the output." +msgstr "" + +#: ../Doc/library/textwrap.rst:273 +msgid "" +"(default: ``' [...]'``) String that will appear at the end of the output " +"text if it has been truncated." +msgstr "" + +#: ../Doc/library/textwrap.rst:279 +msgid "" +":class:`TextWrapper` also provides some public methods, analogous to the " +"module-level convenience functions:" +msgstr "" + +#: ../Doc/library/textwrap.rst:284 +msgid "" +"Wraps the single paragraph in *text* (a string) so every line is at most :" +"attr:`width` characters long. All wrapping options are taken from instance " +"attributes of the :class:`TextWrapper` instance. Returns a list of output " +"lines, without final newlines. If the wrapped output has no content, the " +"returned list is empty." +msgstr "" + +#: ../Doc/library/textwrap.rst:293 +msgid "" +"Wraps the single paragraph in *text*, and returns a single string containing " +"the wrapped paragraph." +msgstr "" + +#: ../Doc/library/threading.rst:2 +msgid ":mod:`threading` --- Thread-based parallelism" +msgstr "" + +#: ../Doc/library/threading.rst:7 +msgid "**Source code:** :source:`Lib/threading.py`" +msgstr "" + +#: ../Doc/library/threading.rst:11 +msgid "" +"This module constructs higher-level threading interfaces on top of the lower " +"level :mod:`_thread` module. See also the :mod:`queue` module." +msgstr "" + +#: ../Doc/library/threading.rst:14 +msgid "" +"The :mod:`dummy_threading` module is provided for situations where :mod:" +"`threading` cannot be used because :mod:`_thread` is missing." +msgstr "" + +#: ../Doc/library/threading.rst:19 +msgid "" +"While they are not listed below, the ``camelCase`` names used for some " +"methods and functions in this module in the Python 2.x series are still " +"supported by this module." +msgstr "" + +#: ../Doc/library/threading.rst:29 +msgid "" +"Return the number of :class:`Thread` objects currently alive. The returned " +"count is equal to the length of the list returned by :func:`.enumerate`." +msgstr "" + +#: ../Doc/library/threading.rst:35 +msgid "" +"Return the current :class:`Thread` object, corresponding to the caller's " +"thread of control. If the caller's thread of control was not created " +"through the :mod:`threading` module, a dummy thread object with limited " +"functionality is returned." +msgstr "" + +#: ../Doc/library/threading.rst:54 +msgid "" +"Return a list of all :class:`Thread` objects currently alive. The list " +"includes daemonic threads, dummy thread objects created by :func:" +"`current_thread`, and the main thread. It excludes terminated threads and " +"threads that have not yet been started." +msgstr "" + +#: ../Doc/library/threading.rst:62 +msgid "" +"Return the main :class:`Thread` object. In normal conditions, the main " +"thread is the thread from which the Python interpreter was started." +msgstr "" + +#: ../Doc/library/threading.rst:73 +msgid "" +"Set a trace function for all threads started from the :mod:`threading` " +"module. The *func* will be passed to :func:`sys.settrace` for each thread, " +"before its :meth:`~Thread.run` method is called." +msgstr "" + +#: ../Doc/library/threading.rst:82 +msgid "" +"Set a profile function for all threads started from the :mod:`threading` " +"module. The *func* will be passed to :func:`sys.setprofile` for each " +"thread, before its :meth:`~Thread.run` method is called." +msgstr "" + +#: ../Doc/library/threading.rst:106 +msgid "This module also defines the following constant:" +msgstr "" + +#: ../Doc/library/threading.rst:110 +msgid "" +"The maximum value allowed for the *timeout* parameter of blocking functions " +"(:meth:`Lock.acquire`, :meth:`RLock.acquire`, :meth:`Condition.wait`, etc.). " +"Specifying a timeout greater than this value will raise an :exc:" +"`OverflowError`." +msgstr "" + +#: ../Doc/library/threading.rst:118 +msgid "" +"This module defines a number of classes, which are detailed in the sections " +"below." +msgstr "" + +#: ../Doc/library/threading.rst:121 +msgid "" +"The design of this module is loosely based on Java's threading model. " +"However, where Java makes locks and condition variables basic behavior of " +"every object, they are separate objects in Python. Python's :class:`Thread` " +"class supports a subset of the behavior of Java's Thread class; currently, " +"there are no priorities, no thread groups, and threads cannot be destroyed, " +"stopped, suspended, resumed, or interrupted. The static methods of Java's " +"Thread class, when implemented, are mapped to module-level functions." +msgstr "" + +#: ../Doc/library/threading.rst:129 +msgid "All of the methods described below are executed atomically." +msgstr "" + +#: ../Doc/library/threading.rst:133 +msgid "Thread-Local Data" +msgstr "" + +#: ../Doc/library/threading.rst:135 +msgid "" +"Thread-local data is data whose values are thread specific. To manage " +"thread-local data, just create an instance of :class:`local` (or a subclass) " +"and store attributes on it::" +msgstr "" + +#: ../Doc/library/threading.rst:142 +msgid "The instance's values will be different for separate threads." +msgstr "" + +#: ../Doc/library/threading.rst:147 +msgid "A class that represents thread-local data." +msgstr "" + +#: ../Doc/library/threading.rst:149 +msgid "" +"For more details and extensive examples, see the documentation string of " +"the :mod:`_threading_local` module." +msgstr "" + +#: ../Doc/library/threading.rst:156 +msgid "Thread Objects" +msgstr "" + +#: ../Doc/library/threading.rst:158 +msgid "" +"The :class:`Thread` class represents an activity that is run in a separate " +"thread of control. There are two ways to specify the activity: by passing a " +"callable object to the constructor, or by overriding the :meth:`~Thread.run` " +"method in a subclass. No other methods (except for the constructor) should " +"be overridden in a subclass. In other words, *only* override the :meth:" +"`~Thread.__init__` and :meth:`~Thread.run` methods of this class." +msgstr "" + +#: ../Doc/library/threading.rst:165 +msgid "" +"Once a thread object is created, its activity must be started by calling the " +"thread's :meth:`~Thread.start` method. This invokes the :meth:`~Thread.run` " +"method in a separate thread of control." +msgstr "" + +#: ../Doc/library/threading.rst:169 +msgid "" +"Once the thread's activity is started, the thread is considered 'alive'. It " +"stops being alive when its :meth:`~Thread.run` method terminates -- either " +"normally, or by raising an unhandled exception. The :meth:`~Thread." +"is_alive` method tests whether the thread is alive." +msgstr "" + +#: ../Doc/library/threading.rst:174 +msgid "" +"Other threads can call a thread's :meth:`~Thread.join` method. This blocks " +"the calling thread until the thread whose :meth:`~Thread.join` method is " +"called is terminated." +msgstr "" + +#: ../Doc/library/threading.rst:178 +msgid "" +"A thread has a name. The name can be passed to the constructor, and read or " +"changed through the :attr:`~Thread.name` attribute." +msgstr "" + +#: ../Doc/library/threading.rst:181 +msgid "" +"A thread can be flagged as a \"daemon thread\". The significance of this " +"flag is that the entire Python program exits when only daemon threads are " +"left. The initial value is inherited from the creating thread. The flag " +"can be set through the :attr:`~Thread.daemon` property or the *daemon* " +"constructor argument." +msgstr "" + +#: ../Doc/library/threading.rst:188 +msgid "" +"Daemon threads are abruptly stopped at shutdown. Their resources (such as " +"open files, database transactions, etc.) may not be released properly. If " +"you want your threads to stop gracefully, make them non-daemonic and use a " +"suitable signalling mechanism such as an :class:`Event`." +msgstr "" + +#: ../Doc/library/threading.rst:193 +msgid "" +"There is a \"main thread\" object; this corresponds to the initial thread of " +"control in the Python program. It is not a daemon thread." +msgstr "" + +#: ../Doc/library/threading.rst:196 +msgid "" +"There is the possibility that \"dummy thread objects\" are created. These " +"are thread objects corresponding to \"alien threads\", which are threads of " +"control started outside the threading module, such as directly from C code. " +"Dummy thread objects have limited functionality; they are always considered " +"alive and daemonic, and cannot be :meth:`~Thread.join`\\ ed. They are never " +"deleted, since it is impossible to detect the termination of alien threads." +msgstr "" + +#: ../Doc/library/threading.rst:207 +msgid "" +"This constructor should always be called with keyword arguments. Arguments " +"are:" +msgstr "" + +#: ../Doc/library/threading.rst:210 +msgid "" +"*group* should be ``None``; reserved for future extension when a :class:" +"`ThreadGroup` class is implemented." +msgstr "" + +#: ../Doc/library/threading.rst:213 +msgid "" +"*target* is the callable object to be invoked by the :meth:`run` method. " +"Defaults to ``None``, meaning nothing is called." +msgstr "" + +#: ../Doc/library/threading.rst:216 +msgid "" +"*name* is the thread name. By default, a unique name is constructed of the " +"form \"Thread-*N*\" where *N* is a small decimal number." +msgstr "" + +#: ../Doc/library/threading.rst:219 +msgid "" +"*args* is the argument tuple for the target invocation. Defaults to ``()``." +msgstr "" + +#: ../Doc/library/threading.rst:221 +msgid "" +"*kwargs* is a dictionary of keyword arguments for the target invocation. " +"Defaults to ``{}``." +msgstr "" + +#: ../Doc/library/threading.rst:224 +msgid "" +"If not ``None``, *daemon* explicitly sets whether the thread is daemonic. If " +"``None`` (the default), the daemonic property is inherited from the current " +"thread." +msgstr "" + +#: ../Doc/library/threading.rst:228 +msgid "" +"If the subclass overrides the constructor, it must make sure to invoke the " +"base class constructor (``Thread.__init__()``) before doing anything else to " +"the thread." +msgstr "" + +#: ../Doc/library/threading.rst:237 +msgid "Start the thread's activity." +msgstr "" + +#: ../Doc/library/threading.rst:239 +msgid "" +"It must be called at most once per thread object. It arranges for the " +"object's :meth:`~Thread.run` method to be invoked in a separate thread of " +"control." +msgstr "" + +#: ../Doc/library/threading.rst:243 +msgid "" +"This method will raise a :exc:`RuntimeError` if called more than once on the " +"same thread object." +msgstr "" + +#: ../Doc/library/threading.rst:248 +msgid "Method representing the thread's activity." +msgstr "" + +#: ../Doc/library/threading.rst:250 +msgid "" +"You may override this method in a subclass. The standard :meth:`run` method " +"invokes the callable object passed to the object's constructor as the " +"*target* argument, if any, with sequential and keyword arguments taken from " +"the *args* and *kwargs* arguments, respectively." +msgstr "" + +#: ../Doc/library/threading.rst:257 +msgid "" +"Wait until the thread terminates. This blocks the calling thread until the " +"thread whose :meth:`~Thread.join` method is called terminates -- either " +"normally or through an unhandled exception --, or until the optional timeout " +"occurs." +msgstr "" + +#: ../Doc/library/threading.rst:262 +msgid "" +"When the *timeout* argument is present and not ``None``, it should be a " +"floating point number specifying a timeout for the operation in seconds (or " +"fractions thereof). As :meth:`~Thread.join` always returns ``None``, you " +"must call :meth:`~Thread.is_alive` after :meth:`~Thread.join` to decide " +"whether a timeout happened -- if the thread is still alive, the :meth:" +"`~Thread.join` call timed out." +msgstr "" + +#: ../Doc/library/threading.rst:269 +msgid "" +"When the *timeout* argument is not present or ``None``, the operation will " +"block until the thread terminates." +msgstr "" + +#: ../Doc/library/threading.rst:272 +msgid "A thread can be :meth:`~Thread.join`\\ ed many times." +msgstr "" + +#: ../Doc/library/threading.rst:274 +msgid "" +":meth:`~Thread.join` raises a :exc:`RuntimeError` if an attempt is made to " +"join the current thread as that would cause a deadlock. It is also an error " +"to :meth:`~Thread.join` a thread before it has been started and attempts to " +"do so raise the same exception." +msgstr "" + +#: ../Doc/library/threading.rst:281 +msgid "" +"A string used for identification purposes only. It has no semantics. " +"Multiple threads may be given the same name. The initial name is set by the " +"constructor." +msgstr "" + +#: ../Doc/library/threading.rst:288 +msgid "" +"Old getter/setter API for :attr:`~Thread.name`; use it directly as a " +"property instead." +msgstr "" + +#: ../Doc/library/threading.rst:293 +msgid "" +"The 'thread identifier' of this thread or ``None`` if the thread has not " +"been started. This is a nonzero integer. See the :func:`_thread." +"get_ident()` function. Thread identifiers may be recycled when a thread " +"exits and another thread is created. The identifier is available even after " +"the thread has exited." +msgstr "" + +#: ../Doc/library/threading.rst:301 +msgid "Return whether the thread is alive." +msgstr "" + +#: ../Doc/library/threading.rst:303 +msgid "" +"This method returns ``True`` just before the :meth:`~Thread.run` method " +"starts until just after the :meth:`~Thread.run` method terminates. The " +"module function :func:`.enumerate` returns a list of all alive threads." +msgstr "" + +#: ../Doc/library/threading.rst:309 +msgid "" +"A boolean value indicating whether this thread is a daemon thread (True) or " +"not (False). This must be set before :meth:`~Thread.start` is called, " +"otherwise :exc:`RuntimeError` is raised. Its initial value is inherited " +"from the creating thread; the main thread is not a daemon thread and " +"therefore all threads created in the main thread default to :attr:`~Thread." +"daemon` = ``False``." +msgstr "" + +#: ../Doc/library/threading.rst:316 +msgid "" +"The entire Python program exits when no alive non-daemon threads are left." +msgstr "" + +#: ../Doc/library/threading.rst:321 +msgid "" +"Old getter/setter API for :attr:`~Thread.daemon`; use it directly as a " +"property instead." +msgstr "" + +#: ../Doc/library/threading.rst:327 +msgid "" +"In CPython, due to the :term:`Global Interpreter Lock`, only one thread can " +"execute Python code at once (even though certain performance-oriented " +"libraries might overcome this limitation). If you want your application to " +"make better use of the computational resources of multi-core machines, you " +"are advised to use :mod:`multiprocessing` or :class:`concurrent.futures." +"ProcessPoolExecutor`. However, threading is still an appropriate model if " +"you want to run multiple I/O-bound tasks simultaneously." +msgstr "" + +#: ../Doc/library/threading.rst:340 +msgid "Lock Objects" +msgstr "" + +#: ../Doc/library/threading.rst:342 +msgid "" +"A primitive lock is a synchronization primitive that is not owned by a " +"particular thread when locked. In Python, it is currently the lowest level " +"synchronization primitive available, implemented directly by the :mod:" +"`_thread` extension module." +msgstr "" + +#: ../Doc/library/threading.rst:347 +msgid "" +"A primitive lock is in one of two states, \"locked\" or \"unlocked\". It is " +"created in the unlocked state. It has two basic methods, :meth:`~Lock." +"acquire` and :meth:`~Lock.release`. When the state is unlocked, :meth:" +"`~Lock.acquire` changes the state to locked and returns immediately. When " +"the state is locked, :meth:`~Lock.acquire` blocks until a call to :meth:" +"`~Lock.release` in another thread changes it to unlocked, then the :meth:" +"`~Lock.acquire` call resets it to locked and returns. The :meth:`~Lock." +"release` method should only be called in the locked state; it changes the " +"state to unlocked and returns immediately. If an attempt is made to release " +"an unlocked lock, a :exc:`RuntimeError` will be raised." +msgstr "" + +#: ../Doc/library/threading.rst:358 +msgid "Locks also support the :ref:`context management protocol `." +msgstr "" + +#: ../Doc/library/threading.rst:360 +msgid "" +"When more than one thread is blocked in :meth:`~Lock.acquire` waiting for " +"the state to turn to unlocked, only one thread proceeds when a :meth:`~Lock." +"release` call resets the state to unlocked; which one of the waiting threads " +"proceeds is not defined, and may vary across implementations." +msgstr "" + +#: ../Doc/library/threading.rst:365 +msgid "All methods are executed atomically." +msgstr "" + +#: ../Doc/library/threading.rst:370 +msgid "" +"The class implementing primitive lock objects. Once a thread has acquired a " +"lock, subsequent attempts to acquire it block, until it is released; any " +"thread may release it." +msgstr "" + +#: ../Doc/library/threading.rst:374 +msgid "Changed from a factory function to a class." +msgstr "" + +#: ../Doc/library/threading.rst:382 +msgid "" +"When invoked with the *blocking* argument set to ``True`` (the default), " +"block until the lock is unlocked, then set it to locked and return ``True``." +msgstr "" + +#: ../Doc/library/threading.rst:385 +msgid "" +"When invoked with the *blocking* argument set to ``False``, do not block. If " +"a call with *blocking* set to ``True`` would block, return ``False`` " +"immediately; otherwise, set the lock to locked and return ``True``." +msgstr "" + +#: ../Doc/library/threading.rst:389 +msgid "" +"When invoked with the floating-point *timeout* argument set to a positive " +"value, block for at most the number of seconds specified by *timeout* and as " +"long as the lock cannot be acquired. A *timeout* argument of ``-1`` " +"specifies an unbounded wait. It is forbidden to specify a *timeout* when " +"*blocking* is false." +msgstr "" + +#: ../Doc/library/threading.rst:395 +msgid "" +"The return value is ``True`` if the lock is acquired successfully, ``False`` " +"if not (for example if the *timeout* expired)." +msgstr "" + +#: ../Doc/library/threading.rst:407 +msgid "" +"Release a lock. This can be called from any thread, not only the thread " +"which has acquired the lock." +msgstr "" + +#: ../Doc/library/threading.rst:410 +msgid "" +"When the lock is locked, reset it to unlocked, and return. If any other " +"threads are blocked waiting for the lock to become unlocked, allow exactly " +"one of them to proceed." +msgstr "" + +#: ../Doc/library/threading.rst:422 +msgid "RLock Objects" +msgstr "" + +#: ../Doc/library/threading.rst:424 +msgid "" +"A reentrant lock is a synchronization primitive that may be acquired " +"multiple times by the same thread. Internally, it uses the concepts of " +"\"owning thread\" and \"recursion level\" in addition to the locked/unlocked " +"state used by primitive locks. In the locked state, some thread owns the " +"lock; in the unlocked state, no thread owns it." +msgstr "" + +#: ../Doc/library/threading.rst:430 +msgid "" +"To lock the lock, a thread calls its :meth:`~RLock.acquire` method; this " +"returns once the thread owns the lock. To unlock the lock, a thread calls " +"its :meth:`~Lock.release` method. :meth:`~Lock.acquire`/:meth:`~Lock." +"release` call pairs may be nested; only the final :meth:`~Lock.release` " +"(the :meth:`~Lock.release` of the outermost pair) resets the lock to " +"unlocked and allows another thread blocked in :meth:`~Lock.acquire` to " +"proceed." +msgstr "" + +#: ../Doc/library/threading.rst:437 +msgid "" +"Reentrant locks also support the :ref:`context management protocol `." +msgstr "" + +#: ../Doc/library/threading.rst:442 +msgid "" +"This class implements reentrant lock objects. A reentrant lock must be " +"released by the thread that acquired it. Once a thread has acquired a " +"reentrant lock, the same thread may acquire it again without blocking; the " +"thread must release it once for each time it has acquired it." +msgstr "" + +#: ../Doc/library/threading.rst:447 +msgid "" +"Note that ``RLock`` is actually a factory function which returns an instance " +"of the most efficient version of the concrete RLock class that is supported " +"by the platform." +msgstr "" + +#: ../Doc/library/threading.rst:456 +msgid "" +"When invoked without arguments: if this thread already owns the lock, " +"increment the recursion level by one, and return immediately. Otherwise, if " +"another thread owns the lock, block until the lock is unlocked. Once the " +"lock is unlocked (not owned by any thread), then grab ownership, set the " +"recursion level to one, and return. If more than one thread is blocked " +"waiting until the lock is unlocked, only one at a time will be able to grab " +"ownership of the lock. There is no return value in this case." +msgstr "" + +#: ../Doc/library/threading.rst:464 +msgid "" +"When invoked with the *blocking* argument set to true, do the same thing as " +"when called without arguments, and return true." +msgstr "" + +#: ../Doc/library/threading.rst:467 +msgid "" +"When invoked with the *blocking* argument set to false, do not block. If a " +"call without an argument would block, return false immediately; otherwise, " +"do the same thing as when called without arguments, and return true." +msgstr "" + +#: ../Doc/library/threading.rst:471 +msgid "" +"When invoked with the floating-point *timeout* argument set to a positive " +"value, block for at most the number of seconds specified by *timeout* and as " +"long as the lock cannot be acquired. Return true if the lock has been " +"acquired, false if the timeout has elapsed." +msgstr "" + +#: ../Doc/library/threading.rst:482 +msgid "" +"Release a lock, decrementing the recursion level. If after the decrement it " +"is zero, reset the lock to unlocked (not owned by any thread), and if any " +"other threads are blocked waiting for the lock to become unlocked, allow " +"exactly one of them to proceed. If after the decrement the recursion level " +"is still nonzero, the lock remains locked and owned by the calling thread." +msgstr "" + +#: ../Doc/library/threading.rst:488 +msgid "" +"Only call this method when the calling thread owns the lock. A :exc:" +"`RuntimeError` is raised if this method is called when the lock is unlocked." +msgstr "" + +#: ../Doc/library/threading.rst:498 +msgid "Condition Objects" +msgstr "" + +#: ../Doc/library/threading.rst:500 +msgid "" +"A condition variable is always associated with some kind of lock; this can " +"be passed in or one will be created by default. Passing one in is useful " +"when several condition variables must share the same lock. The lock is part " +"of the condition object: you don't have to track it separately." +msgstr "" + +#: ../Doc/library/threading.rst:505 +msgid "" +"A condition variable obeys the :ref:`context management protocol `: using the ``with`` statement acquires the associated lock for the " +"duration of the enclosed block. The :meth:`~Condition.acquire` and :meth:" +"`~Condition.release` methods also call the corresponding methods of the " +"associated lock." +msgstr "" + +#: ../Doc/library/threading.rst:511 +msgid "" +"Other methods must be called with the associated lock held. The :meth:" +"`~Condition.wait` method releases the lock, and then blocks until another " +"thread awakens it by calling :meth:`~Condition.notify` or :meth:`~Condition." +"notify_all`. Once awakened, :meth:`~Condition.wait` re-acquires the lock " +"and returns. It is also possible to specify a timeout." +msgstr "" + +#: ../Doc/library/threading.rst:517 +msgid "" +"The :meth:`~Condition.notify` method wakes up one of the threads waiting for " +"the condition variable, if any are waiting. The :meth:`~Condition." +"notify_all` method wakes up all threads waiting for the condition variable." +msgstr "" + +#: ../Doc/library/threading.rst:521 +msgid "" +"Note: the :meth:`~Condition.notify` and :meth:`~Condition.notify_all` " +"methods don't release the lock; this means that the thread or threads " +"awakened will not return from their :meth:`~Condition.wait` call " +"immediately, but only when the thread that called :meth:`~Condition.notify` " +"or :meth:`~Condition.notify_all` finally relinquishes ownership of the lock." +msgstr "" + +#: ../Doc/library/threading.rst:527 +msgid "" +"The typical programming style using condition variables uses the lock to " +"synchronize access to some shared state; threads that are interested in a " +"particular change of state call :meth:`~Condition.wait` repeatedly until " +"they see the desired state, while threads that modify the state call :meth:" +"`~Condition.notify` or :meth:`~Condition.notify_all` when they change the " +"state in such a way that it could possibly be a desired state for one of the " +"waiters. For example, the following code is a generic producer-consumer " +"situation with unlimited buffer capacity::" +msgstr "" + +#: ../Doc/library/threading.rst:547 +msgid "" +"The ``while`` loop checking for the application's condition is necessary " +"because :meth:`~Condition.wait` can return after an arbitrary long time, and " +"the condition which prompted the :meth:`~Condition.notify` call may no " +"longer hold true. This is inherent to multi-threaded programming. The :" +"meth:`~Condition.wait_for` method can be used to automate the condition " +"checking, and eases the computation of timeouts::" +msgstr "" + +#: ../Doc/library/threading.rst:559 +msgid "" +"To choose between :meth:`~Condition.notify` and :meth:`~Condition." +"notify_all`, consider whether one state change can be interesting for only " +"one or several waiting threads. E.g. in a typical producer-consumer " +"situation, adding one item to the buffer only needs to wake up one consumer " +"thread." +msgstr "" + +#: ../Doc/library/threading.rst:567 +msgid "" +"This class implements condition variable objects. A condition variable " +"allows one or more threads to wait until they are notified by another thread." +msgstr "" + +#: ../Doc/library/threading.rst:570 +msgid "" +"If the *lock* argument is given and not ``None``, it must be a :class:`Lock` " +"or :class:`RLock` object, and it is used as the underlying lock. Otherwise, " +"a new :class:`RLock` object is created and used as the underlying lock." +msgstr "" + +#: ../Doc/library/threading.rst:574 ../Doc/library/threading.rst:696 +#: ../Doc/library/threading.rst:739 ../Doc/library/threading.rst:791 +#: ../Doc/library/threading.rst:860 +msgid "changed from a factory function to a class." +msgstr "" + +#: ../Doc/library/threading.rst:579 +msgid "" +"Acquire the underlying lock. This method calls the corresponding method on " +"the underlying lock; the return value is whatever that method returns." +msgstr "" + +#: ../Doc/library/threading.rst:584 +msgid "" +"Release the underlying lock. This method calls the corresponding method on " +"the underlying lock; there is no return value." +msgstr "" + +#: ../Doc/library/threading.rst:589 +msgid "" +"Wait until notified or until a timeout occurs. If the calling thread has not " +"acquired the lock when this method is called, a :exc:`RuntimeError` is " +"raised." +msgstr "" + +#: ../Doc/library/threading.rst:593 +msgid "" +"This method releases the underlying lock, and then blocks until it is " +"awakened by a :meth:`notify` or :meth:`notify_all` call for the same " +"condition variable in another thread, or until the optional timeout occurs. " +"Once awakened or timed out, it re-acquires the lock and returns." +msgstr "" + +#: ../Doc/library/threading.rst:598 +msgid "" +"When the *timeout* argument is present and not ``None``, it should be a " +"floating point number specifying a timeout for the operation in seconds (or " +"fractions thereof)." +msgstr "" + +#: ../Doc/library/threading.rst:602 +msgid "" +"When the underlying lock is an :class:`RLock`, it is not released using its :" +"meth:`release` method, since this may not actually unlock the lock when it " +"was acquired multiple times recursively. Instead, an internal interface of " +"the :class:`RLock` class is used, which really unlocks it even when it has " +"been recursively acquired several times. Another internal interface is then " +"used to restore the recursion level when the lock is reacquired." +msgstr "" + +#: ../Doc/library/threading.rst:610 +msgid "" +"The return value is ``True`` unless a given *timeout* expired, in which case " +"it is ``False``." +msgstr "" + +#: ../Doc/library/threading.rst:613 ../Doc/library/threading.rst:825 +msgid "Previously, the method always returned ``None``." +msgstr "" + +#: ../Doc/library/threading.rst:618 +msgid "" +"Wait until a condition evaluates to True. *predicate* should be a callable " +"which result will be interpreted as a boolean value. A *timeout* may be " +"provided giving the maximum time to wait." +msgstr "" + +#: ../Doc/library/threading.rst:622 +msgid "" +"This utility method may call :meth:`wait` repeatedly until the predicate is " +"satisfied, or until a timeout occurs. The return value is the last return " +"value of the predicate and will evaluate to ``False`` if the method timed " +"out." +msgstr "" + +#: ../Doc/library/threading.rst:627 +msgid "" +"Ignoring the timeout feature, calling this method is roughly equivalent to " +"writing::" +msgstr "" + +#: ../Doc/library/threading.rst:633 +msgid "" +"Therefore, the same rules apply as with :meth:`wait`: The lock must be held " +"when called and is re-acquired on return. The predicate is evaluated with " +"the lock held." +msgstr "" + +#: ../Doc/library/threading.rst:641 +msgid "" +"By default, wake up one thread waiting on this condition, if any. If the " +"calling thread has not acquired the lock when this method is called, a :exc:" +"`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/threading.rst:645 +msgid "" +"This method wakes up at most *n* of the threads waiting for the condition " +"variable; it is a no-op if no threads are waiting." +msgstr "" + +#: ../Doc/library/threading.rst:648 +msgid "" +"The current implementation wakes up exactly *n* threads, if at least *n* " +"threads are waiting. However, it's not safe to rely on this behavior. A " +"future, optimized implementation may occasionally wake up more than *n* " +"threads." +msgstr "" + +#: ../Doc/library/threading.rst:653 +msgid "" +"Note: an awakened thread does not actually return from its :meth:`wait` call " +"until it can reacquire the lock. Since :meth:`notify` does not release the " +"lock, its caller should." +msgstr "" + +#: ../Doc/library/threading.rst:659 +msgid "" +"Wake up all threads waiting on this condition. This method acts like :meth:" +"`notify`, but wakes up all waiting threads instead of one. If the calling " +"thread has not acquired the lock when this method is called, a :exc:" +"`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/threading.rst:668 +msgid "Semaphore Objects" +msgstr "" + +#: ../Doc/library/threading.rst:670 +msgid "" +"This is one of the oldest synchronization primitives in the history of " +"computer science, invented by the early Dutch computer scientist Edsger W. " +"Dijkstra (he used the names ``P()`` and ``V()`` instead of :meth:`~Semaphore." +"acquire` and :meth:`~Semaphore.release`)." +msgstr "" + +#: ../Doc/library/threading.rst:675 +msgid "" +"A semaphore manages an internal counter which is decremented by each :meth:" +"`~Semaphore.acquire` call and incremented by each :meth:`~Semaphore.release` " +"call. The counter can never go below zero; when :meth:`~Semaphore.acquire` " +"finds that it is zero, it blocks, waiting until some other thread calls :" +"meth:`~Semaphore.release`." +msgstr "" + +#: ../Doc/library/threading.rst:681 +msgid "" +"Semaphores also support the :ref:`context management protocol `." +msgstr "" + +#: ../Doc/library/threading.rst:686 +msgid "" +"This class implements semaphore objects. A semaphore manages a counter " +"representing the number of :meth:`release` calls minus the number of :meth:" +"`acquire` calls, plus an initial value. The :meth:`acquire` method blocks " +"if necessary until it can return without making the counter negative. If not " +"given, *value* defaults to 1." +msgstr "" + +#: ../Doc/library/threading.rst:692 +msgid "" +"The optional argument gives the initial *value* for the internal counter; it " +"defaults to ``1``. If the *value* given is less than 0, :exc:`ValueError` is " +"raised." +msgstr "" + +#: ../Doc/library/threading.rst:703 +msgid "" +"When invoked without arguments: if the internal counter is larger than zero " +"on entry, decrement it by one and return immediately. If it is zero on " +"entry, block, waiting until some other thread has called :meth:`~Semaphore." +"release` to make it larger than zero. This is done with proper interlocking " +"so that if multiple :meth:`acquire` calls are blocked, :meth:`~Semaphore." +"release` will wake exactly one of them up. The implementation may pick one " +"at random, so the order in which blocked threads are awakened should not be " +"relied on. Returns true (or blocks indefinitely)." +msgstr "" + +#: ../Doc/library/threading.rst:713 +msgid "" +"When invoked with *blocking* set to false, do not block. If a call without " +"an argument would block, return false immediately; otherwise, do the same " +"thing as when called without arguments, and return true." +msgstr "" + +#: ../Doc/library/threading.rst:717 +msgid "" +"When invoked with a *timeout* other than None, it will block for at most " +"*timeout* seconds. If acquire does not complete successfully in that " +"interval, return false. Return true otherwise." +msgstr "" + +#: ../Doc/library/threading.rst:726 +msgid "" +"Release a semaphore, incrementing the internal counter by one. When it was " +"zero on entry and another thread is waiting for it to become larger than " +"zero again, wake up that thread." +msgstr "" + +#: ../Doc/library/threading.rst:733 +msgid "" +"Class implementing bounded semaphore objects. A bounded semaphore checks to " +"make sure its current value doesn't exceed its initial value. If it does, :" +"exc:`ValueError` is raised. In most situations semaphores are used to guard " +"resources with limited capacity. If the semaphore is released too many " +"times it's a sign of a bug. If not given, *value* defaults to 1." +msgstr "" + +#: ../Doc/library/threading.rst:746 +msgid ":class:`Semaphore` Example" +msgstr "" + +#: ../Doc/library/threading.rst:748 +msgid "" +"Semaphores are often used to guard resources with limited capacity, for " +"example, a database server. In any situation where the size of the resource " +"is fixed, you should use a bounded semaphore. Before spawning any worker " +"threads, your main thread would initialize the semaphore::" +msgstr "" + +#: ../Doc/library/threading.rst:757 +msgid "" +"Once spawned, worker threads call the semaphore's acquire and release " +"methods when they need to connect to the server::" +msgstr "" + +#: ../Doc/library/threading.rst:767 +msgid "" +"The use of a bounded semaphore reduces the chance that a programming error " +"which causes the semaphore to be released more than it's acquired will go " +"undetected." +msgstr "" + +#: ../Doc/library/threading.rst:774 +msgid "Event Objects" +msgstr "" + +#: ../Doc/library/threading.rst:776 +msgid "" +"This is one of the simplest mechanisms for communication between threads: " +"one thread signals an event and other threads wait for it." +msgstr "" + +#: ../Doc/library/threading.rst:779 +msgid "" +"An event object manages an internal flag that can be set to true with the :" +"meth:`~Event.set` method and reset to false with the :meth:`~Event.clear` " +"method. The :meth:`~Event.wait` method blocks until the flag is true." +msgstr "" + +#: ../Doc/library/threading.rst:786 +msgid "" +"Class implementing event objects. An event manages a flag that can be set " +"to true with the :meth:`~Event.set` method and reset to false with the :meth:" +"`clear` method. The :meth:`wait` method blocks until the flag is true. The " +"flag is initially false." +msgstr "" + +#: ../Doc/library/threading.rst:796 +msgid "Return true if and only if the internal flag is true." +msgstr "" + +#: ../Doc/library/threading.rst:800 +msgid "" +"Set the internal flag to true. All threads waiting for it to become true are " +"awakened. Threads that call :meth:`wait` once the flag is true will not " +"block at all." +msgstr "" + +#: ../Doc/library/threading.rst:806 +msgid "" +"Reset the internal flag to false. Subsequently, threads calling :meth:`wait` " +"will block until :meth:`.set` is called to set the internal flag to true " +"again." +msgstr "" + +#: ../Doc/library/threading.rst:812 +msgid "" +"Block until the internal flag is true. If the internal flag is true on " +"entry, return immediately. Otherwise, block until another thread calls :" +"meth:`.set` to set the flag to true, or until the optional timeout occurs." +msgstr "" + +#: ../Doc/library/threading.rst:816 +msgid "" +"When the timeout argument is present and not ``None``, it should be a " +"floating point number specifying a timeout for the operation in seconds (or " +"fractions thereof)." +msgstr "" + +#: ../Doc/library/threading.rst:820 +msgid "" +"This method returns true if and only if the internal flag has been set to " +"true, either before the wait call or after the wait starts, so it will " +"always return ``True`` except if a timeout is given and the operation times " +"out." +msgstr "" + +#: ../Doc/library/threading.rst:832 +msgid "Timer Objects" +msgstr "" + +#: ../Doc/library/threading.rst:834 +msgid "" +"This class represents an action that should be run only after a certain " +"amount of time has passed --- a timer. :class:`Timer` is a subclass of :" +"class:`Thread` and as such also functions as an example of creating custom " +"threads." +msgstr "" + +#: ../Doc/library/threading.rst:838 +msgid "" +"Timers are started, as with threads, by calling their :meth:`~Timer.start` " +"method. The timer can be stopped (before its action has begun) by calling " +"the :meth:`~Timer.cancel` method. The interval the timer will wait before " +"executing its action may not be exactly the same as the interval specified " +"by the user." +msgstr "" + +#: ../Doc/library/threading.rst:855 +msgid "" +"Create a timer that will run *function* with arguments *args* and keyword " +"arguments *kwargs*, after *interval* seconds have passed. If *args* is None " +"(the default) then an empty list will be used. If *kwargs* is None (the " +"default) then an empty dict will be used." +msgstr "" + +#: ../Doc/library/threading.rst:865 +msgid "" +"Stop the timer, and cancel the execution of the timer's action. This will " +"only work if the timer is still in its waiting stage." +msgstr "" + +#: ../Doc/library/threading.rst:870 +msgid "Barrier Objects" +msgstr "" + +#: ../Doc/library/threading.rst:874 +msgid "" +"This class provides a simple synchronization primitive for use by a fixed " +"number of threads that need to wait for each other. Each of the threads " +"tries to pass the barrier by calling the :meth:`~Barrier.wait` method and " +"will block until all of the threads have made the call. At this points, the " +"threads are released simultaneously." +msgstr "" + +#: ../Doc/library/threading.rst:880 +msgid "" +"The barrier can be reused any number of times for the same number of threads." +msgstr "" + +#: ../Doc/library/threading.rst:882 +msgid "" +"As an example, here is a simple way to synchronize a client and server " +"thread::" +msgstr "" + +#: ../Doc/library/threading.rst:902 +msgid "" +"Create a barrier object for *parties* number of threads. An *action*, when " +"provided, is a callable to be called by one of the threads when they are " +"released. *timeout* is the default timeout value if none is specified for " +"the :meth:`wait` method." +msgstr "" + +#: ../Doc/library/threading.rst:909 +msgid "" +"Pass the barrier. When all the threads party to the barrier have called " +"this function, they are all released simultaneously. If a *timeout* is " +"provided, it is used in preference to any that was supplied to the class " +"constructor." +msgstr "" + +#: ../Doc/library/threading.rst:914 +msgid "" +"The return value is an integer in the range 0 to *parties* -- 1, different " +"for each thread. This can be used to select a thread to do some special " +"housekeeping, e.g.::" +msgstr "" + +#: ../Doc/library/threading.rst:923 +msgid "" +"If an *action* was provided to the constructor, one of the threads will have " +"called it prior to being released. Should this call raise an error, the " +"barrier is put into the broken state." +msgstr "" + +#: ../Doc/library/threading.rst:927 +msgid "If the call times out, the barrier is put into the broken state." +msgstr "" + +#: ../Doc/library/threading.rst:929 +msgid "" +"This method may raise a :class:`BrokenBarrierError` exception if the barrier " +"is broken or reset while a thread is waiting." +msgstr "" + +#: ../Doc/library/threading.rst:934 +msgid "" +"Return the barrier to the default, empty state. Any threads waiting on it " +"will receive the :class:`BrokenBarrierError` exception." +msgstr "" + +#: ../Doc/library/threading.rst:937 +msgid "" +"Note that using this function may can require some external synchronization " +"if there are other threads whose state is unknown. If a barrier is broken " +"it may be better to just leave it and create a new one." +msgstr "" + +#: ../Doc/library/threading.rst:943 +msgid "" +"Put the barrier into a broken state. This causes any active or future calls " +"to :meth:`wait` to fail with the :class:`BrokenBarrierError`. Use this for " +"example if one of the needs to abort, to avoid deadlocking the application." +msgstr "" + +#: ../Doc/library/threading.rst:948 +msgid "" +"It may be preferable to simply create the barrier with a sensible *timeout* " +"value to automatically guard against one of the threads going awry." +msgstr "" + +#: ../Doc/library/threading.rst:954 +msgid "The number of threads required to pass the barrier." +msgstr "" + +#: ../Doc/library/threading.rst:958 +msgid "The number of threads currently waiting in the barrier." +msgstr "" + +#: ../Doc/library/threading.rst:962 +msgid "A boolean that is ``True`` if the barrier is in the broken state." +msgstr "" + +#: ../Doc/library/threading.rst:967 +msgid "" +"This exception, a subclass of :exc:`RuntimeError`, is raised when the :class:" +"`Barrier` object is reset or broken." +msgstr "" + +#: ../Doc/library/threading.rst:974 +msgid "" +"Using locks, conditions, and semaphores in the :keyword:`with` statement" +msgstr "" + +#: ../Doc/library/threading.rst:976 +msgid "" +"All of the objects provided by this module that have :meth:`acquire` and :" +"meth:`release` methods can be used as context managers for a :keyword:`with` " +"statement. The :meth:`acquire` method will be called when the block is " +"entered, and :meth:`release` will be called when the block is exited. " +"Hence, the following snippet::" +msgstr "" + +#: ../Doc/library/threading.rst:985 +msgid "is equivalent to::" +msgstr "" + +#: ../Doc/library/threading.rst:993 +msgid "" +"Currently, :class:`Lock`, :class:`RLock`, :class:`Condition`, :class:" +"`Semaphore`, and :class:`BoundedSemaphore` objects may be used as :keyword:" +"`with` statement context managers." +msgstr "" + +#: ../Doc/library/time.rst:2 +msgid ":mod:`time` --- Time access and conversions" +msgstr "" + +#: ../Doc/library/time.rst:9 +msgid "" +"This module provides various time-related functions. For related " +"functionality, see also the :mod:`datetime` and :mod:`calendar` modules." +msgstr "" + +#: ../Doc/library/time.rst:12 +msgid "" +"Although this module is always available, not all functions are available on " +"all platforms. Most of the functions defined in this module call platform C " +"library functions with the same name. It may sometimes be helpful to " +"consult the platform documentation, because the semantics of these functions " +"varies among platforms." +msgstr "" + +#: ../Doc/library/time.rst:18 +msgid "An explanation of some terminology and conventions is in order." +msgstr "" + +#: ../Doc/library/time.rst:22 +msgid "" +"The :dfn:`epoch` is the point where the time starts. On January 1st of that " +"year, at 0 hours, the \"time since the epoch\" is zero. For Unix, the epoch " +"is 1970. To find out what the epoch is, look at ``gmtime(0)``." +msgstr "" + +#: ../Doc/library/time.rst:28 +msgid "" +"The functions in this module may not handle dates and times before the epoch " +"or far in the future. The cut-off point in the future is determined by the " +"C library; for 32-bit systems, it is typically in 2038." +msgstr "" + +#: ../Doc/library/time.rst:38 +msgid "" +"**Year 2000 (Y2K) issues**: Python depends on the platform's C library, " +"which generally doesn't have year 2000 issues, since all dates and times are " +"represented internally as seconds since the epoch. Function :func:" +"`strptime` can parse 2-digit years when given ``%y`` format code. When 2-" +"digit years are parsed, they are converted according to the POSIX and ISO C " +"standards: values 69--99 are mapped to 1969--1999, and values 0--68 are " +"mapped to 2000--2068." +msgstr "" + +#: ../Doc/library/time.rst:50 +msgid "" +"UTC is Coordinated Universal Time (formerly known as Greenwich Mean Time, or " +"GMT). The acronym UTC is not a mistake but a compromise between English and " +"French." +msgstr "" + +#: ../Doc/library/time.rst:56 +msgid "" +"DST is Daylight Saving Time, an adjustment of the timezone by (usually) one " +"hour during part of the year. DST rules are magic (determined by local law) " +"and can change from year to year. The C library has a table containing the " +"local rules (often it is read from a system file for flexibility) and is the " +"only source of True Wisdom in this respect." +msgstr "" + +#: ../Doc/library/time.rst:62 +msgid "" +"The precision of the various real-time functions may be less than suggested " +"by the units in which their value or argument is expressed. E.g. on most " +"Unix systems, the clock \"ticks\" only 50 or 100 times a second." +msgstr "" + +#: ../Doc/library/time.rst:66 +msgid "" +"On the other hand, the precision of :func:`.time` and :func:`sleep` is " +"better than their Unix equivalents: times are expressed as floating point " +"numbers, :func:`.time` returns the most accurate time available (using Unix :" +"c:func:`gettimeofday` where available), and :func:`sleep` will accept a time " +"with a nonzero fraction (Unix :c:func:`select` is used to implement this, " +"where available)." +msgstr "" + +#: ../Doc/library/time.rst:73 +msgid "" +"The time value as returned by :func:`gmtime`, :func:`localtime`, and :func:" +"`strptime`, and accepted by :func:`asctime`, :func:`mktime` and :func:" +"`strftime`, is a sequence of 9 integers. The return values of :func:" +"`gmtime`, :func:`localtime`, and :func:`strptime` also offer attribute names " +"for individual fields." +msgstr "" + +#: ../Doc/library/time.rst:79 +msgid "See :class:`struct_time` for a description of these objects." +msgstr "" + +#: ../Doc/library/time.rst:81 +msgid "" +"The :class:`struct_time` type was extended to provide the :attr:`tm_gmtoff` " +"and :attr:`tm_zone` attributes when platform supports corresponding ``struct " +"tm`` members." +msgstr "" + +#: ../Doc/library/time.rst:86 +msgid "" +"The :class:`struct_time` attributes :attr:`tm_gmtoff` and :attr:`tm_zone` " +"are now available on all platforms." +msgstr "" + +#: ../Doc/library/time.rst:90 +msgid "Use the following functions to convert between time representations:" +msgstr "" + +#: ../Doc/library/time.rst:93 +msgid "Use" +msgstr "" + +#: ../Doc/library/time.rst:95 ../Doc/library/time.rst:98 +#: ../Doc/library/time.rst:101 ../Doc/library/time.rst:104 +msgid "seconds since the epoch" +msgstr "" + +#: ../Doc/library/time.rst:95 ../Doc/library/time.rst:101 +msgid ":class:`struct_time` in UTC" +msgstr "" + +#: ../Doc/library/time.rst:95 +msgid ":func:`gmtime`" +msgstr "" + +#: ../Doc/library/time.rst:98 ../Doc/library/time.rst:104 +msgid ":class:`struct_time` in local time" +msgstr "" + +#: ../Doc/library/time.rst:98 +msgid ":func:`localtime`" +msgstr "" + +#: ../Doc/library/time.rst:101 +msgid ":func:`calendar.timegm`" +msgstr "" + +#: ../Doc/library/time.rst:104 +msgid ":func:`mktime`" +msgstr "" + +#: ../Doc/library/time.rst:109 +msgid "The module defines the following functions and data items:" +msgstr "" + +#: ../Doc/library/time.rst:113 +msgid "" +"The offset of the local DST timezone, in seconds west of UTC, if one is " +"defined. This is negative if the local DST timezone is east of UTC (as in " +"Western Europe, including the UK). Only use this if ``daylight`` is nonzero." +msgstr "" + +#: ../Doc/library/time.rst:120 +msgid "" +"Convert a tuple or :class:`struct_time` representing a time as returned by :" +"func:`gmtime` or :func:`localtime` to a string of the following form: ``'Sun " +"Jun 20 23:21:05 1993'``. If *t* is not provided, the current time as " +"returned by :func:`localtime` is used. Locale information is not used by :" +"func:`asctime`." +msgstr "" + +#: ../Doc/library/time.rst:128 +msgid "" +"Unlike the C function of the same name, :func:`asctime` does not add a " +"trailing newline." +msgstr "" + +#: ../Doc/library/time.rst:139 +msgid "" +"On Unix, return the current processor time as a floating point number " +"expressed in seconds. The precision, and in fact the very definition of the " +"meaning of \"processor time\", depends on that of the C function of the same " +"name." +msgstr "" + +#: ../Doc/library/time.rst:143 +msgid "" +"On Windows, this function returns wall-clock seconds elapsed since the first " +"call to this function, as a floating point number, based on the Win32 " +"function :c:func:`QueryPerformanceCounter`. The resolution is typically " +"better than one microsecond." +msgstr "" + +#: ../Doc/library/time.rst:148 +msgid "" +"The behaviour of this function depends on the platform: use :func:" +"`perf_counter` or :func:`process_time` instead, depending on your " +"requirements, to have a well defined behaviour." +msgstr "" + +#: ../Doc/library/time.rst:156 +msgid "Return the resolution (precision) of the specified clock *clk_id*." +msgstr "" + +#: ../Doc/library/time.rst:165 +msgid "Return the time of the specified clock *clk_id*." +msgstr "" + +#: ../Doc/library/time.rst:174 +msgid "Set the time of the specified clock *clk_id*." +msgstr "" + +#: ../Doc/library/time.rst:183 +msgid "" +"The Solaris OS has a CLOCK_HIGHRES timer that attempts to use an optimal " +"hardware source, and may give close to nanosecond resolution. CLOCK_HIGHRES " +"is the nonadjustable, high-resolution clock." +msgstr "" + +#: ../Doc/library/time.rst:187 +msgid "Availability: Solaris." +msgstr "" + +#: ../Doc/library/time.rst:194 +msgid "" +"Clock that cannot be set and represents monotonic time since some " +"unspecified starting point." +msgstr "" + +#: ../Doc/library/time.rst:204 +msgid "" +"Similar to :data:`CLOCK_MONOTONIC`, but provides access to a raw hardware-" +"based time that is not subject to NTP adjustments." +msgstr "" + +#: ../Doc/library/time.rst:207 +msgid "Availability: Linux 2.6.28 or later." +msgstr "" + +#: ../Doc/library/time.rst:214 +msgid "High-resolution per-process timer from the CPU." +msgstr "" + +#: ../Doc/library/time.rst:223 +msgid "" +"System-wide real-time clock. Setting this clock requires appropriate " +"privileges." +msgstr "" + +#: ../Doc/library/time.rst:233 +msgid "Thread-specific CPU-time clock." +msgstr "" + +#: ../Doc/library/time.rst:242 +msgid "" +"Convert a time expressed in seconds since the epoch to a string representing " +"local time. If *secs* is not provided or :const:`None`, the current time as " +"returned by :func:`.time` is used. ``ctime(secs)`` is equivalent to " +"``asctime(localtime(secs))``. Locale information is not used by :func:" +"`ctime`." +msgstr "" + +#: ../Doc/library/time.rst:250 +msgid "Nonzero if a DST timezone is defined." +msgstr "" + +#: ../Doc/library/time.rst:255 +msgid "" +"Get information on the specified clock as a namespace object. Supported " +"clock names and the corresponding functions to read their value are:" +msgstr "" + +#: ../Doc/library/time.rst:259 +msgid "``'clock'``: :func:`time.clock`" +msgstr "" + +#: ../Doc/library/time.rst:260 +msgid "``'monotonic'``: :func:`time.monotonic`" +msgstr "" + +#: ../Doc/library/time.rst:261 +msgid "``'perf_counter'``: :func:`time.perf_counter`" +msgstr "" + +#: ../Doc/library/time.rst:262 +msgid "``'process_time'``: :func:`time.process_time`" +msgstr "" + +#: ../Doc/library/time.rst:263 +msgid "``'time'``: :func:`time.time`" +msgstr "" + +#: ../Doc/library/time.rst:265 +msgid "The result has the following attributes:" +msgstr "" + +#: ../Doc/library/time.rst:267 +msgid "" +"*adjustable*: ``True`` if the clock can be changed automatically (e.g. by a " +"NTP daemon) or manually by the system administrator, ``False`` otherwise" +msgstr "" + +#: ../Doc/library/time.rst:269 +msgid "" +"*implementation*: The name of the underlying C function used to get the " +"clock value" +msgstr "" + +#: ../Doc/library/time.rst:271 +msgid "" +"*monotonic*: ``True`` if the clock cannot go backward, ``False`` otherwise" +msgstr "" + +#: ../Doc/library/time.rst:273 +msgid "*resolution*: The resolution of the clock in seconds (:class:`float`)" +msgstr "" + +#: ../Doc/library/time.rst:280 +msgid "" +"Convert a time expressed in seconds since the epoch to a :class:" +"`struct_time` in UTC in which the dst flag is always zero. If *secs* is not " +"provided or :const:`None`, the current time as returned by :func:`.time` is " +"used. Fractions of a second are ignored. See above for a description of " +"the :class:`struct_time` object. See :func:`calendar.timegm` for the inverse " +"of this function." +msgstr "" + +#: ../Doc/library/time.rst:290 +msgid "" +"Like :func:`gmtime` but converts to local time. If *secs* is not provided " +"or :const:`None`, the current time as returned by :func:`.time` is used. " +"The dst flag is set to ``1`` when DST applies to the given time." +msgstr "" + +#: ../Doc/library/time.rst:297 +msgid "" +"This is the inverse function of :func:`localtime`. Its argument is the :" +"class:`struct_time` or full 9-tuple (since the dst flag is needed; use " +"``-1`` as the dst flag if it is unknown) which expresses the time in *local* " +"time, not UTC. It returns a floating point number, for compatibility with :" +"func:`.time`. If the input value cannot be represented as a valid time, " +"either :exc:`OverflowError` or :exc:`ValueError` will be raised (which " +"depends on whether the invalid value is caught by Python or the underlying C " +"libraries). The earliest date for which it can generate a time is platform-" +"dependent." +msgstr "" + +#: ../Doc/library/time.rst:309 +msgid "" +"Return the value (in fractional seconds) of a monotonic clock, i.e. a clock " +"that cannot go backwards. The clock is not affected by system clock " +"updates. The reference point of the returned value is undefined, so that " +"only the difference between the results of consecutive calls is valid." +msgstr "" + +#: ../Doc/library/time.rst:314 +msgid "" +"On Windows versions older than Vista, :func:`monotonic` detects :c:func:" +"`GetTickCount` integer overflow (32 bits, roll-over after 49.7 days). It " +"increases an internal epoch (reference time) by 2\\ :sup:`32` each time that " +"an overflow is detected. The epoch is stored in the process-local state and " +"so the value of :func:`monotonic` may be different in two Python processes " +"running for more than 49 days. On more recent versions of Windows and on " +"other operating systems, :func:`monotonic` is system-wide." +msgstr "" + +#: ../Doc/library/time.rst:323 +msgid "The function is now always available." +msgstr "" + +#: ../Doc/library/time.rst:329 +msgid "" +"Return the value (in fractional seconds) of a performance counter, i.e. a " +"clock with the highest available resolution to measure a short duration. It " +"does include time elapsed during sleep and is system-wide. The reference " +"point of the returned value is undefined, so that only the difference " +"between the results of consecutive calls is valid." +msgstr "" + +#: ../Doc/library/time.rst:340 +msgid "" +"Return the value (in fractional seconds) of the sum of the system and user " +"CPU time of the current process. It does not include time elapsed during " +"sleep. It is process-wide by definition. The reference point of the " +"returned value is undefined, so that only the difference between the results " +"of consecutive calls is valid." +msgstr "" + +#: ../Doc/library/time.rst:350 +msgid "" +"Suspend execution of the calling thread for the given number of seconds. The " +"argument may be a floating point number to indicate a more precise sleep " +"time. The actual suspension time may be less than that requested because any " +"caught signal will terminate the :func:`sleep` following execution of that " +"signal's catching routine. Also, the suspension time may be longer than " +"requested by an arbitrary amount because of the scheduling of other activity " +"in the system." +msgstr "" + +#: ../Doc/library/time.rst:358 +msgid "" +"The function now sleeps at least *secs* even if the sleep is interrupted by " +"a signal, except if the signal handler raises an exception (see :pep:`475` " +"for the rationale)." +msgstr "" + +#: ../Doc/library/time.rst:366 +msgid "" +"Convert a tuple or :class:`struct_time` representing a time as returned by :" +"func:`gmtime` or :func:`localtime` to a string as specified by the *format* " +"argument. If *t* is not provided, the current time as returned by :func:" +"`localtime` is used. *format* must be a string. :exc:`ValueError` is " +"raised if any field in *t* is outside of the allowed range." +msgstr "" + +#: ../Doc/library/time.rst:372 +msgid "" +"0 is a legal argument for any position in the time tuple; if it is normally " +"illegal the value is forced to a correct one." +msgstr "" + +#: ../Doc/library/time.rst:375 +msgid "" +"The following directives can be embedded in the *format* string. They are " +"shown without the optional field width and precision specification, and are " +"replaced by the indicated characters in the :func:`strftime` result:" +msgstr "" + +#: ../Doc/library/time.rst:382 +msgid "Locale's abbreviated weekday name." +msgstr "" + +#: ../Doc/library/time.rst:385 +msgid "Locale's full weekday name." +msgstr "" + +#: ../Doc/library/time.rst:387 +msgid "Locale's abbreviated month name." +msgstr "" + +#: ../Doc/library/time.rst:390 +msgid "Locale's full month name." +msgstr "" + +#: ../Doc/library/time.rst:395 +msgid "Day of the month as a decimal number [01,31]." +msgstr "" + +#: ../Doc/library/time.rst:398 +msgid "Hour (24-hour clock) as a decimal number [00,23]." +msgstr "" + +#: ../Doc/library/time.rst:401 +msgid "Hour (12-hour clock) as a decimal number [01,12]." +msgstr "" + +#: ../Doc/library/time.rst:404 +msgid "Day of the year as a decimal number [001,366]." +msgstr "" + +#: ../Doc/library/time.rst:407 +msgid "Month as a decimal number [01,12]." +msgstr "" + +#: ../Doc/library/time.rst:410 +msgid "Minute as a decimal number [00,59]." +msgstr "" + +#: ../Doc/library/time.rst:416 +msgid "Second as a decimal number [00,61]." +msgstr "" + +#: ../Doc/library/time.rst:419 +msgid "" +"Week number of the year (Sunday as the first day of the week) as a decimal " +"number [00,53]. All days in a new year preceding the first Sunday are " +"considered to be in week 0." +msgstr "" + +#: ../Doc/library/time.rst:427 +msgid "Weekday as a decimal number [0(Sunday),6]." +msgstr "" + +#: ../Doc/library/time.rst:430 +msgid "" +"Week number of the year (Monday as the first day of the week) as a decimal " +"number [00,53]. All days in a new year preceding the first Monday are " +"considered to be in week 0." +msgstr "" + +#: ../Doc/library/time.rst:444 +msgid "Year without century as a decimal number [00,99]." +msgstr "" + +#: ../Doc/library/time.rst:450 +msgid "" +"Time zone offset indicating a positive or negative time difference from UTC/" +"GMT of the form +HHMM or -HHMM, where H represents decimal hour digits and M " +"represents decimal minute digits [-23:59, +23:59]." +msgstr "" + +#: ../Doc/library/time.rst:456 +msgid "Time zone name (no characters if no time zone exists)." +msgstr "" + +#: ../Doc/library/time.rst:465 +msgid "" +"When used with the :func:`strptime` function, the ``%p`` directive only " +"affects the output hour field if the ``%I`` directive is used to parse the " +"hour." +msgstr "" + +#: ../Doc/library/time.rst:469 +msgid "" +"The range really is ``0`` to ``61``; value ``60`` is valid in timestamps " +"representing leap seconds and value ``61`` is supported for historical " +"reasons." +msgstr "" + +#: ../Doc/library/time.rst:474 +msgid "" +"When used with the :func:`strptime` function, ``%U`` and ``%W`` are only " +"used in calculations when the day of the week and the year are specified." +msgstr "" + +#: ../Doc/library/time.rst:477 +msgid "" +"Here is an example, a format for dates compatible with that specified in " +"the :rfc:`2822` Internet email standard. [#]_ ::" +msgstr "" + +#: ../Doc/library/time.rst:484 +msgid "" +"Additional directives may be supported on certain platforms, but only the " +"ones listed here have a meaning standardized by ANSI C. To see the full set " +"of format codes supported on your platform, consult the :manpage:" +"`strftime(3)` documentation." +msgstr "" + +#: ../Doc/library/time.rst:489 +msgid "" +"On some platforms, an optional field width and precision specification can " +"immediately follow the initial ``'%'`` of a directive in the following " +"order; this is also not portable. The field width is normally 2 except for ``" +"%j`` where it is 3." +msgstr "" + +#: ../Doc/library/time.rst:497 +msgid "" +"Parse a string representing a time according to a format. The return value " +"is a :class:`struct_time` as returned by :func:`gmtime` or :func:`localtime`." +msgstr "" + +#: ../Doc/library/time.rst:501 +msgid "" +"The *format* parameter uses the same directives as those used by :func:" +"`strftime`; it defaults to ``\"%a %b %d %H:%M:%S %Y\"`` which matches the " +"formatting returned by :func:`ctime`. If *string* cannot be parsed according " +"to *format*, or if it has excess data after parsing, :exc:`ValueError` is " +"raised. The default values used to fill in any missing data when more " +"accurate values cannot be inferred are ``(1900, 1, 1, 0, 0, 0, 0, 1, -1)``. " +"Both *string* and *format* must be strings." +msgstr "" + +#: ../Doc/library/time.rst:516 +msgid "" +"Support for the ``%Z`` directive is based on the values contained in " +"``tzname`` and whether ``daylight`` is true. Because of this, it is " +"platform-specific except for recognizing UTC and GMT which are always known " +"(and are considered to be non-daylight savings timezones)." +msgstr "" + +#: ../Doc/library/time.rst:521 +msgid "" +"Only the directives specified in the documentation are supported. Because " +"``strftime()`` is implemented per platform it can sometimes offer more " +"directives than those listed. But ``strptime()`` is independent of any " +"platform and thus does not necessarily support all directives available that " +"are not documented as supported." +msgstr "" + +#: ../Doc/library/time.rst:530 +msgid "" +"The type of the time value sequence returned by :func:`gmtime`, :func:" +"`localtime`, and :func:`strptime`. It is an object with a :term:`named " +"tuple` interface: values can be accessed by index and by attribute name. " +"The following values are present:" +msgstr "" + +#: ../Doc/library/time.rst:536 +msgid "Values" +msgstr "" + +#: ../Doc/library/time.rst:538 +msgid ":attr:`tm_year`" +msgstr "" + +#: ../Doc/library/time.rst:538 +msgid "(for example, 1993)" +msgstr "" + +#: ../Doc/library/time.rst:540 +msgid ":attr:`tm_mon`" +msgstr "" + +#: ../Doc/library/time.rst:540 +msgid "range [1, 12]" +msgstr "" + +#: ../Doc/library/time.rst:542 +msgid ":attr:`tm_mday`" +msgstr "" + +#: ../Doc/library/time.rst:542 +msgid "range [1, 31]" +msgstr "" + +#: ../Doc/library/time.rst:544 +msgid ":attr:`tm_hour`" +msgstr "" + +#: ../Doc/library/time.rst:544 +msgid "range [0, 23]" +msgstr "" + +#: ../Doc/library/time.rst:546 +msgid ":attr:`tm_min`" +msgstr "" + +#: ../Doc/library/time.rst:546 +msgid "range [0, 59]" +msgstr "" + +#: ../Doc/library/time.rst:548 +msgid ":attr:`tm_sec`" +msgstr "" + +#: ../Doc/library/time.rst:548 +msgid "range [0, 61]; see **(2)** in :func:`strftime` description" +msgstr "" + +#: ../Doc/library/time.rst:551 +msgid ":attr:`tm_wday`" +msgstr "" + +#: ../Doc/library/time.rst:551 +msgid "range [0, 6], Monday is 0" +msgstr "" + +#: ../Doc/library/time.rst:553 +msgid ":attr:`tm_yday`" +msgstr "" + +#: ../Doc/library/time.rst:553 +msgid "range [1, 366]" +msgstr "" + +#: ../Doc/library/time.rst:555 +msgid ":attr:`tm_isdst`" +msgstr "" + +#: ../Doc/library/time.rst:555 +msgid "0, 1 or -1; see below" +msgstr "" + +#: ../Doc/library/time.rst:557 ../Doc/library/time.rst:559 +msgid "N/A" +msgstr "" + +#: ../Doc/library/time.rst:557 +msgid ":attr:`tm_zone`" +msgstr "" + +#: ../Doc/library/time.rst:557 +msgid "abbreviation of timezone name" +msgstr "" + +#: ../Doc/library/time.rst:559 +msgid ":attr:`tm_gmtoff`" +msgstr "" + +#: ../Doc/library/time.rst:559 +msgid "offset east of UTC in seconds" +msgstr "" + +#: ../Doc/library/time.rst:562 +msgid "" +"Note that unlike the C structure, the month value is a range of [1, 12], not " +"[0, 11]." +msgstr "" + +#: ../Doc/library/time.rst:565 +msgid "" +"In calls to :func:`mktime`, :attr:`tm_isdst` may be set to 1 when daylight " +"savings time is in effect, and 0 when it is not. A value of -1 indicates " +"that this is not known, and will usually result in the correct state being " +"filled in." +msgstr "" + +#: ../Doc/library/time.rst:569 +msgid "" +"When a tuple with an incorrect length is passed to a function expecting a :" +"class:`struct_time`, or having elements of the wrong type, a :exc:" +"`TypeError` is raised." +msgstr "" + +#: ../Doc/library/time.rst:575 +msgid "" +"Return the time in seconds since the epoch as a floating point number. Note " +"that even though the time is always returned as a floating point number, not " +"all systems provide time with a better precision than 1 second. While this " +"function normally returns non-decreasing values, it can return a lower value " +"than a previous call if the system clock has been set back between the two " +"calls." +msgstr "" + +#: ../Doc/library/time.rst:584 +msgid "" +"The offset of the local (non-DST) timezone, in seconds west of UTC (negative " +"in most of Western Europe, positive in the US, zero in the UK)." +msgstr "" + +#: ../Doc/library/time.rst:590 +msgid "" +"A tuple of two strings: the first is the name of the local non-DST timezone, " +"the second is the name of the local DST timezone. If no DST timezone is " +"defined, the second string should not be used." +msgstr "" + +#: ../Doc/library/time.rst:597 +msgid "" +"Resets the time conversion rules used by the library routines. The " +"environment variable :envvar:`TZ` specifies how this is done." +msgstr "" + +#: ../Doc/library/time.rst:604 +msgid "" +"Although in many cases, changing the :envvar:`TZ` environment variable may " +"affect the output of functions like :func:`localtime` without calling :func:" +"`tzset`, this behavior should not be relied on." +msgstr "" + +#: ../Doc/library/time.rst:608 +msgid "The :envvar:`TZ` environment variable should contain no whitespace." +msgstr "" + +#: ../Doc/library/time.rst:610 +msgid "" +"The standard format of the :envvar:`TZ` environment variable is (whitespace " +"added for clarity)::" +msgstr "" + +#: ../Doc/library/time.rst:615 +msgid "Where the components are:" +msgstr "" + +#: ../Doc/library/time.rst:619 +msgid "``std`` and ``dst``" +msgstr "" + +#: ../Doc/library/time.rst:618 +msgid "" +"Three or more alphanumerics giving the timezone abbreviations. These will be " +"propagated into time.tzname" +msgstr "" + +#: ../Doc/library/time.rst:625 +msgid "``offset``" +msgstr "" + +#: ../Doc/library/time.rst:622 +msgid "" +"The offset has the form: ``± hh[:mm[:ss]]``. This indicates the value added " +"the local time to arrive at UTC. If preceded by a '-', the timezone is east " +"of the Prime Meridian; otherwise, it is west. If no offset follows dst, " +"summer time is assumed to be one hour ahead of standard time." +msgstr "" + +#: ../Doc/library/time.rst:647 +msgid "``start[/time], end[/time]``" +msgstr "" + +#: ../Doc/library/time.rst:628 +msgid "" +"Indicates when to change to and back from DST. The format of the start and " +"end dates are one of the following:" +msgstr "" + +#: ../Doc/library/time.rst:633 +msgid ":samp:`J{n}`" +msgstr "" + +#: ../Doc/library/time.rst:632 +msgid "" +"The Julian day *n* (1 <= *n* <= 365). Leap days are not counted, so in all " +"years February 28 is day 59 and March 1 is day 60." +msgstr "" + +#: ../Doc/library/time.rst:637 +msgid ":samp:`{n}`" +msgstr "" + +#: ../Doc/library/time.rst:636 +msgid "" +"The zero-based Julian day (0 <= *n* <= 365). Leap days are counted, and it " +"is possible to refer to February 29." +msgstr "" + +#: ../Doc/library/time.rst:644 +msgid ":samp:`M{m}.{n}.{d}`" +msgstr "" + +#: ../Doc/library/time.rst:640 +msgid "" +"The *d*'th day (0 <= *d* <= 6) of week *n* of month *m* of the year (1 <= " +"*n* <= 5, 1 <= *m* <= 12, where week 5 means \"the last *d* day in month *m*" +"\" which may occur in either the fourth or the fifth week). Week 1 is the " +"first week in which the *d*'th day occurs. Day zero is a Sunday." +msgstr "" + +#: ../Doc/library/time.rst:646 +msgid "" +"``time`` has the same format as ``offset`` except that no leading sign ('-' " +"or '+') is allowed. The default, if time is not given, is 02:00:00." +msgstr "" + +#: ../Doc/library/time.rst:660 +msgid "" +"On many Unix systems (including \\*BSD, Linux, Solaris, and Darwin), it is " +"more convenient to use the system's zoneinfo (:manpage:`tzfile(5)`) " +"database to specify the timezone rules. To do this, set the :envvar:`TZ` " +"environment variable to the path of the required timezone datafile, " +"relative to the root of the systems 'zoneinfo' timezone database, usually " +"located at :file:`/usr/share/zoneinfo`. For example, ``'US/Eastern'``, " +"``'Australia/Melbourne'``, ``'Egypt'`` or ``'Europe/Amsterdam'``. ::" +msgstr "" + +#: ../Doc/library/time.rst:681 +msgid "More object-oriented interface to dates and times." +msgstr "" + +#: ../Doc/library/time.rst:685 +msgid "Module :mod:`locale`" +msgstr "" + +#: ../Doc/library/time.rst:684 +msgid "" +"Internationalization services. The locale setting affects the " +"interpretation of many format specifiers in :func:`strftime` and :func:" +"`strptime`." +msgstr "" + +#: ../Doc/library/time.rst:688 +msgid "" +"General calendar-related functions. :func:`~calendar.timegm` is the " +"inverse of :func:`gmtime` from this module." +msgstr "" + +#: ../Doc/library/time.rst:693 +msgid "" +"The use of ``%Z`` is now deprecated, but the ``%z`` escape that expands to " +"the preferred hour/minute offset is not supported by all ANSI C libraries. " +"Also, a strict reading of the original 1982 :rfc:`822` standard calls for a " +"two-digit year (%y rather than %Y), but practice moved to 4-digit years long " +"before the year 2000. After that, :rfc:`822` became obsolete and the 4-" +"digit year has been first recommended by :rfc:`1123` and then mandated by :" +"rfc:`2822`." +msgstr "" + +#: ../Doc/library/timeit.rst:2 +msgid ":mod:`timeit` --- Measure execution time of small code snippets" +msgstr "" + +#: ../Doc/library/timeit.rst:7 +msgid "**Source code:** :source:`Lib/timeit.py`" +msgstr "" + +#: ../Doc/library/timeit.rst:15 +msgid "" +"This module provides a simple way to time small bits of Python code. It has " +"both a :ref:`timeit-command-line-interface` as well as a :ref:`callable " +"` one. It avoids a number of common traps for measuring " +"execution times. See also Tim Peters' introduction to the \"Algorithms\" " +"chapter in the *Python Cookbook*, published by O'Reilly." +msgstr "" + +#: ../Doc/library/timeit.rst:25 +msgid "" +"The following example shows how the :ref:`timeit-command-line-interface` can " +"be used to compare three different expressions:" +msgstr "" + +#: ../Doc/library/timeit.rst:37 +msgid "This can be achieved from the :ref:`python-interface` with::" +msgstr "" + +#: ../Doc/library/timeit.rst:48 +msgid "" +"Note however that :mod:`timeit` will automatically determine the number of " +"repetitions only when the command-line interface is used. In the :ref:" +"`timeit-examples` section you can find more advanced examples." +msgstr "" + +#: ../Doc/library/timeit.rst:56 +msgid "Python Interface" +msgstr "" + +#: ../Doc/library/timeit.rst:58 +msgid "The module defines three convenience functions and a public class:" +msgstr "" + +#: ../Doc/library/timeit.rst:63 +msgid "" +"Create a :class:`Timer` instance with the given statement, *setup* code and " +"*timer* function and run its :meth:`.timeit` method with *number* " +"executions. The optional *globals* argument specifies a namespace in which " +"to execute the code." +msgstr "" + +#: ../Doc/library/timeit.rst:68 ../Doc/library/timeit.rst:79 +#: ../Doc/library/timeit.rst:113 +msgid "The optional *globals* parameter was added." +msgstr "" + +#: ../Doc/library/timeit.rst:74 +msgid "" +"Create a :class:`Timer` instance with the given statement, *setup* code and " +"*timer* function and run its :meth:`.repeat` method with the given *repeat* " +"count and *number* executions. The optional *globals* argument specifies a " +"namespace in which to execute the code." +msgstr "" + +#: ../Doc/library/timeit.rst:84 +msgid "The default timer, which is always :func:`time.perf_counter`." +msgstr "" + +#: ../Doc/library/timeit.rst:86 +msgid ":func:`time.perf_counter` is now the default timer." +msgstr "" + +#: ../Doc/library/timeit.rst:92 +msgid "Class for timing execution speed of small code snippets." +msgstr "" + +#: ../Doc/library/timeit.rst:94 +msgid "" +"The constructor takes a statement to be timed, an additional statement used " +"for setup, and a timer function. Both statements default to ``'pass'``; the " +"timer function is platform-dependent (see the module doc string). *stmt* and " +"*setup* may also contain multiple statements separated by ``;`` or newlines, " +"as long as they don't contain multi-line string literals. The statement " +"will by default be executed within timeit's namespace; this behavior can be " +"controlled by passing a namespace to *globals*." +msgstr "" + +#: ../Doc/library/timeit.rst:102 +msgid "" +"To measure the execution time of the first statement, use the :meth:`." +"timeit` method. The :meth:`.repeat` and :meth:`.autorange` methods are " +"convenience methods to call :meth:`.timeit` multiple times." +msgstr "" + +#: ../Doc/library/timeit.rst:106 +msgid "" +"The execution time of *setup* is excluded from the overall timed execution " +"run." +msgstr "" + +#: ../Doc/library/timeit.rst:108 +msgid "" +"The *stmt* and *setup* parameters can also take objects that are callable " +"without arguments. This will embed calls to them in a timer function that " +"will then be executed by :meth:`.timeit`. Note that the timing overhead is " +"a little larger in this case because of the extra function calls." +msgstr "" + +#: ../Doc/library/timeit.rst:118 +msgid "" +"Time *number* executions of the main statement. This executes the setup " +"statement once, and then returns the time it takes to execute the main " +"statement a number of times, measured in seconds as a float. The argument is " +"the number of times through the loop, defaulting to one million. The main " +"statement, the setup statement and the timer function to be used are passed " +"to the constructor." +msgstr "" + +#: ../Doc/library/timeit.rst:127 +msgid "" +"By default, :meth:`.timeit` temporarily turns off :term:`garbage collection` " +"during the timing. The advantage of this approach is that it makes " +"independent timings more comparable. This disadvantage is that GC may be an " +"important component of the performance of the function being measured. If " +"so, GC can be re-enabled as the first statement in the *setup* string. For " +"example::" +msgstr "" + +#: ../Doc/library/timeit.rst:139 +msgid "Automatically determine how many times to call :meth:`.timeit`." +msgstr "" + +#: ../Doc/library/timeit.rst:141 +msgid "" +"This is a convenience function that calls :meth:`.timeit` repeatedly so that " +"the total time >= 0.2 second, returning the eventual (number of loops, time " +"taken for that number of loops). It calls :meth:`.timeit` with *number* set " +"to successive powers of ten (10, 100, 1000, ...) up to a maximum of one " +"billion, until the time taken is at least 0.2 second, or the maximum is " +"reached." +msgstr "" + +#: ../Doc/library/timeit.rst:148 +msgid "" +"If *callback* is given and is not *None*, it will be called after each trial " +"with two arguments: ``callback(number, time_taken)``." +msgstr "" + +#: ../Doc/library/timeit.rst:156 +msgid "Call :meth:`.timeit` a few times." +msgstr "" + +#: ../Doc/library/timeit.rst:158 +msgid "" +"This is a convenience function that calls the :meth:`.timeit` repeatedly, " +"returning a list of results. The first argument specifies how many times to " +"call :meth:`.timeit`. The second argument specifies the *number* argument " +"for :meth:`.timeit`." +msgstr "" + +#: ../Doc/library/timeit.rst:165 +msgid "" +"It's tempting to calculate mean and standard deviation from the result " +"vector and report these. However, this is not very useful. In a typical " +"case, the lowest value gives a lower bound for how fast your machine can run " +"the given code snippet; higher values in the result vector are typically not " +"caused by variability in Python's speed, but by other processes interfering " +"with your timing accuracy. So the :func:`min` of the result is probably the " +"only number you should be interested in. After that, you should look at the " +"entire vector and apply common sense rather than statistics." +msgstr "" + +#: ../Doc/library/timeit.rst:178 +msgid "Helper to print a traceback from the timed code." +msgstr "" + +#: ../Doc/library/timeit.rst:180 +msgid "Typical use::" +msgstr "" + +#: ../Doc/library/timeit.rst:188 +msgid "" +"The advantage over the standard traceback is that source lines in the " +"compiled template will be displayed. The optional *file* argument directs " +"where the traceback is sent; it defaults to :data:`sys.stderr`." +msgstr "" + +#: ../Doc/library/timeit.rst:196 ../Doc/library/unittest.rst:158 +#: ../Doc/library/zipapp.rst:40 +msgid "Command-Line Interface" +msgstr "" + +#: ../Doc/library/timeit.rst:198 +msgid "" +"When called as a program from the command line, the following form is used::" +msgstr "" + +#: ../Doc/library/timeit.rst:202 +msgid "Where the following options are understood:" +msgstr "" + +#: ../Doc/library/timeit.rst:208 +msgid "how many times to execute 'statement'" +msgstr "" + +#: ../Doc/library/timeit.rst:212 +msgid "how many times to repeat the timer (default 3)" +msgstr "" + +#: ../Doc/library/timeit.rst:216 +msgid "statement to be executed once initially (default ``pass``)" +msgstr "" + +#: ../Doc/library/timeit.rst:220 +msgid "" +"measure process time, not wallclock time, using :func:`time.process_time` " +"instead of :func:`time.perf_counter`, which is the default" +msgstr "" + +#: ../Doc/library/timeit.rst:227 +msgid "use :func:`time.time` (deprecated)" +msgstr "" + +#: ../Doc/library/timeit.rst:231 +msgid "specify a time unit for timer output; can select usec, msec, or sec" +msgstr "" + +#: ../Doc/library/timeit.rst:237 +msgid "use :func:`time.clock` (deprecated)" +msgstr "" + +#: ../Doc/library/timeit.rst:241 +msgid "print raw timing results; repeat for more digits precision" +msgstr "" + +#: ../Doc/library/timeit.rst:245 +msgid "print a short usage message and exit" +msgstr "" + +#: ../Doc/library/timeit.rst:247 +msgid "" +"A multi-line statement may be given by specifying each line as a separate " +"statement argument; indented lines are possible by enclosing an argument in " +"quotes and using leading spaces. Multiple :option:`-s` options are treated " +"similarly." +msgstr "" + +#: ../Doc/library/timeit.rst:252 +msgid "" +"If :option:`-n` is not given, a suitable number of loops is calculated by " +"trying successive powers of 10 until the total time is at least 0.2 seconds." +msgstr "" + +#: ../Doc/library/timeit.rst:255 +msgid "" +":func:`default_timer` measurements can be affected by other programs running " +"on the same machine, so the best thing to do when accurate timing is " +"necessary is to repeat the timing a few times and use the best time. The :" +"option:`-r` option is good for this; the default of 3 repetitions is " +"probably enough in most cases. You can use :func:`time.process_time` to " +"measure CPU time." +msgstr "" + +#: ../Doc/library/timeit.rst:263 +msgid "" +"There is a certain baseline overhead associated with executing a pass " +"statement. The code here doesn't try to hide it, but you should be aware of " +"it. The baseline overhead can be measured by invoking the program without " +"arguments, and it might differ between Python versions." +msgstr "" + +#: ../Doc/library/timeit.rst:274 +msgid "" +"It is possible to provide a setup statement that is executed only once at " +"the beginning:" +msgstr "" + +#: ../Doc/library/timeit.rst:291 +msgid "The same can be done using the :class:`Timer` class and its methods::" +msgstr "" + +#: ../Doc/library/timeit.rst:301 +msgid "" +"The following examples show how to time expressions that contain multiple " +"lines. Here we compare the cost of using :func:`hasattr` vs. :keyword:`try`/:" +"keyword:`except` to test for missing and present object attributes:" +msgstr "" + +#: ../Doc/library/timeit.rst:347 +msgid "" +"To give the :mod:`timeit` module access to functions you define, you can " +"pass a *setup* parameter which contains an import statement::" +msgstr "" + +#: ../Doc/library/timeit.rst:358 +msgid "" +"Another option is to pass :func:`globals` to the *globals* parameter, which " +"will cause the code to be executed within your current global namespace. " +"This can be more convenient than individually specifying imports::" +msgstr "" + +#: ../Doc/library/tk.rst:5 +msgid "Graphical User Interfaces with Tk" +msgstr "" + +#: ../Doc/library/tk.rst:13 +msgid "" +"Tk/Tcl has long been an integral part of Python. It provides a robust and " +"platform independent windowing toolkit, that is available to Python " +"programmers using the :mod:`tkinter` package, and its extension, the :mod:" +"`tkinter.tix` and the :mod:`tkinter.ttk` modules." +msgstr "" + +#: ../Doc/library/tk.rst:18 +msgid "" +"The :mod:`tkinter` package is a thin object-oriented layer on top of Tcl/Tk. " +"To use :mod:`tkinter`, you don't need to write Tcl code, but you will need " +"to consult the Tk documentation, and occasionally the Tcl documentation. :" +"mod:`tkinter` is a set of wrappers that implement the Tk widgets as Python " +"classes. In addition, the internal module :mod:`_tkinter` provides a " +"threadsafe mechanism which allows Python and Tcl to interact." +msgstr "" + +#: ../Doc/library/tk.rst:25 +msgid "" +":mod:`tkinter`'s chief virtues are that it is fast, and that it usually " +"comes bundled with Python. Although its standard documentation is weak, good " +"material is available, which includes: references, tutorials, a book and " +"others. :mod:`tkinter` is also famous for having an outdated look and feel, " +"which has been vastly improved in Tk 8.5. Nevertheless, there are many other " +"GUI libraries that you could be interested in. For more information about " +"alternatives, see the :ref:`other-gui-packages` section." +msgstr "" + +#: ../Doc/library/tkinter.rst:2 +msgid ":mod:`tkinter` --- Python interface to Tcl/Tk" +msgstr "" + +#: ../Doc/library/tkinter.rst:9 +msgid "**Source code:** :source:`Lib/tkinter/__init__.py`" +msgstr "" + +#: ../Doc/library/tkinter.rst:13 +msgid "" +"The :mod:`tkinter` package (\"Tk interface\") is the standard Python " +"interface to the Tk GUI toolkit. Both Tk and :mod:`tkinter` are available " +"on most Unix platforms, as well as on Windows systems. (Tk itself is not " +"part of Python; it is maintained at ActiveState.) You can check that :mod:" +"`tkinter` is properly installed on your system by running ``python -m " +"tkinter`` from the command line; this should open a window demonstrating a " +"simple Tk interface." +msgstr "" + +#: ../Doc/library/tkinter.rst:24 +msgid "`Python Tkinter Resources `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:23 +msgid "" +"The Python Tkinter Topic Guide provides a great deal of information on using " +"Tk from Python and links to other sources of information on Tk." +msgstr "" + +#: ../Doc/library/tkinter.rst:27 +msgid "`TKDocs `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:27 +msgid "" +"Extensive tutorial plus friendlier widget pages for some of the widgets." +msgstr "" + +#: ../Doc/library/tkinter.rst:30 +msgid "" +"`Tkinter reference: a GUI for Python `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:30 +msgid "On-line reference material." +msgstr "" + +#: ../Doc/library/tkinter.rst:33 +msgid "`Tkinter docs from effbot `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:33 +msgid "Online reference for tkinter supported by effbot.org." +msgstr "" + +#: ../Doc/library/tkinter.rst:36 +msgid "`Tcl/Tk manual `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:36 +msgid "Official manual for the latest tcl/tk version." +msgstr "" + +#: ../Doc/library/tkinter.rst:39 +msgid "" +"`Programming Python `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:39 +msgid "Book by Mark Lutz, has excellent coverage of Tkinter." +msgstr "" + +#: ../Doc/library/tkinter.rst:42 +msgid "" +"`Modern Tkinter for Busy Python Developers `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:42 +msgid "" +"Book by Mark Rozerman about building attractive and modern graphical user " +"interfaces with Python and Tkinter." +msgstr "" + +#: ../Doc/library/tkinter.rst:44 +msgid "" +"`Python and Tkinter Programming `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:45 +msgid "The book by John Grayson (ISBN 1-884777-81-3)." +msgstr "" + +#: ../Doc/library/tkinter.rst:49 +msgid "Tkinter Modules" +msgstr "" + +#: ../Doc/library/tkinter.rst:51 +msgid "" +"Most of the time, :mod:`tkinter` is all you really need, but a number of " +"additional modules are available as well. The Tk interface is located in a " +"binary module named :mod:`_tkinter`. This module contains the low-level " +"interface to Tk, and should never be used directly by application " +"programmers. It is usually a shared library (or DLL), but might in some " +"cases be statically linked with the Python interpreter." +msgstr "" + +#: ../Doc/library/tkinter.rst:58 +msgid "" +"In addition to the Tk interface module, :mod:`tkinter` includes a number of " +"Python modules, :mod:`tkinter.constants` being one of the most important. " +"Importing :mod:`tkinter` will automatically import :mod:`tkinter.constants`, " +"so, usually, to use Tkinter all you need is a simple import statement::" +msgstr "" + +#: ../Doc/library/tkinter.rst:65 +msgid "Or, more often::" +msgstr "" + +#: ../Doc/library/tkinter.rst:72 +msgid "" +"The :class:`Tk` class is instantiated without arguments. This creates a " +"toplevel widget of Tk which usually is the main window of an application. " +"Each instance has its own associated Tcl interpreter." +msgstr "" + +#: ../Doc/library/tkinter.rst:81 +msgid "" +"The :func:`Tcl` function is a factory function which creates an object much " +"like that created by the :class:`Tk` class, except that it does not " +"initialize the Tk subsystem. This is most often useful when driving the Tcl " +"interpreter in an environment where one doesn't want to create extraneous " +"toplevel windows, or where one cannot (such as Unix/Linux systems without an " +"X server). An object created by the :func:`Tcl` object can have a Toplevel " +"window created (and the Tk subsystem initialized) by calling its :meth:" +"`loadtk` method." +msgstr "" + +#: ../Doc/library/tkinter.rst:90 +msgid "Other modules that provide Tk support include:" +msgstr "" + +#: ../Doc/library/tkinter.rst:93 +msgid ":mod:`tkinter.scrolledtext`" +msgstr "" + +#: ../Doc/library/tkinter.rst:93 +msgid "Text widget with a vertical scroll bar built in." +msgstr "" + +#: ../Doc/library/tkinter.rst:96 +msgid ":mod:`tkinter.colorchooser`" +msgstr "" + +#: ../Doc/library/tkinter.rst:96 +msgid "Dialog to let the user choose a color." +msgstr "" + +#: ../Doc/library/tkinter.rst:99 +msgid ":mod:`tkinter.commondialog`" +msgstr "" + +#: ../Doc/library/tkinter.rst:99 +msgid "Base class for the dialogs defined in the other modules listed here." +msgstr "" + +#: ../Doc/library/tkinter.rst:102 +msgid ":mod:`tkinter.filedialog`" +msgstr "" + +#: ../Doc/library/tkinter.rst:102 +msgid "Common dialogs to allow the user to specify a file to open or save." +msgstr "" + +#: ../Doc/library/tkinter.rst:105 +msgid ":mod:`tkinter.font`" +msgstr "" + +#: ../Doc/library/tkinter.rst:105 +msgid "Utilities to help work with fonts." +msgstr "" + +#: ../Doc/library/tkinter.rst:108 +msgid ":mod:`tkinter.messagebox`" +msgstr "" + +#: ../Doc/library/tkinter.rst:108 +msgid "Access to standard Tk dialog boxes." +msgstr "" + +#: ../Doc/library/tkinter.rst:111 +msgid ":mod:`tkinter.simpledialog`" +msgstr "" + +#: ../Doc/library/tkinter.rst:111 +msgid "Basic dialogs and convenience functions." +msgstr "" + +#: ../Doc/library/tkinter.rst:115 +msgid ":mod:`tkinter.dnd`" +msgstr "" + +#: ../Doc/library/tkinter.rst:114 +msgid "" +"Drag-and-drop support for :mod:`tkinter`. This is experimental and should " +"become deprecated when it is replaced with the Tk DND." +msgstr "" + +#: ../Doc/library/tkinter.rst:119 +msgid ":mod:`turtle`" +msgstr "" + +#: ../Doc/library/tkinter.rst:118 +msgid "Turtle graphics in a Tk window." +msgstr "" + +#: ../Doc/library/tkinter.rst:122 +msgid "Tkinter Life Preserver" +msgstr "" + +#: ../Doc/library/tkinter.rst:127 +msgid "" +"This section is not designed to be an exhaustive tutorial on either Tk or " +"Tkinter. Rather, it is intended as a stop gap, providing some introductory " +"orientation on the system." +msgstr "" + +#: ../Doc/library/tkinter.rst:131 +msgid "Credits:" +msgstr "" + +#: ../Doc/library/tkinter.rst:133 +msgid "Tk was written by John Ousterhout while at Berkeley." +msgstr "" + +#: ../Doc/library/tkinter.rst:135 +msgid "Tkinter was written by Steen Lumholt and Guido van Rossum." +msgstr "" + +#: ../Doc/library/tkinter.rst:137 +msgid "" +"This Life Preserver was written by Matt Conway at the University of Virginia." +msgstr "" + +#: ../Doc/library/tkinter.rst:139 +msgid "" +"The HTML rendering, and some liberal editing, was produced from a FrameMaker " +"version by Ken Manheimer." +msgstr "" + +#: ../Doc/library/tkinter.rst:142 +msgid "" +"Fredrik Lundh elaborated and revised the class interface descriptions, to " +"get them current with Tk 4.2." +msgstr "" + +#: ../Doc/library/tkinter.rst:145 +msgid "" +"Mike Clarkson converted the documentation to LaTeX, and compiled the User " +"Interface chapter of the reference manual." +msgstr "" + +#: ../Doc/library/tkinter.rst:150 +msgid "How To Use This Section" +msgstr "" + +#: ../Doc/library/tkinter.rst:152 +msgid "" +"This section is designed in two parts: the first half (roughly) covers " +"background material, while the second half can be taken to the keyboard as a " +"handy reference." +msgstr "" + +#: ../Doc/library/tkinter.rst:156 +msgid "" +"When trying to answer questions of the form \"how do I do blah\", it is " +"often best to find out how to do\"blah\" in straight Tk, and then convert " +"this back into the corresponding :mod:`tkinter` call. Python programmers can " +"often guess at the correct Python command by looking at the Tk " +"documentation. This means that in order to use Tkinter, you will have to " +"know a little bit about Tk. This document can't fulfill that role, so the " +"best we can do is point you to the best documentation that exists. Here are " +"some hints:" +msgstr "" + +#: ../Doc/library/tkinter.rst:164 +msgid "" +"The authors strongly suggest getting a copy of the Tk man pages. " +"Specifically, the man pages in the ``manN`` directory are most useful. The " +"``man3`` man pages describe the C interface to the Tk library and thus are " +"not especially helpful for script writers." +msgstr "" + +#: ../Doc/library/tkinter.rst:169 +msgid "" +"Addison-Wesley publishes a book called Tcl and the Tk Toolkit by John " +"Ousterhout (ISBN 0-201-63337-X) which is a good introduction to Tcl and Tk " +"for the novice. The book is not exhaustive, and for many details it defers " +"to the man pages." +msgstr "" + +#: ../Doc/library/tkinter.rst:174 +msgid "" +":file:`tkinter/__init__.py` is a last resort for most, but can be a good " +"place to go when nothing else makes sense." +msgstr "" + +#: ../Doc/library/tkinter.rst:181 +msgid "`Tcl/Tk 8.6 man pages `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:181 +msgid "The Tcl/Tk manual on www.tcl.tk." +msgstr "" + +#: ../Doc/library/tkinter.rst:184 +msgid "`ActiveState Tcl Home Page `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:184 +msgid "The Tk/Tcl development is largely taking place at ActiveState." +msgstr "" + +#: ../Doc/library/tkinter.rst:187 +msgid "" +"`Tcl and the Tk Toolkit `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:187 +msgid "The book by John Ousterhout, the inventor of Tcl." +msgstr "" + +#: ../Doc/library/tkinter.rst:189 +msgid "`Practical Programming in Tcl and Tk `_" +msgstr "" + +#: ../Doc/library/tkinter.rst:190 +msgid "Brent Welch's encyclopedic book." +msgstr "" + +#: ../Doc/library/tkinter.rst:194 +msgid "A Simple Hello World Program" +msgstr "" + +#: ../Doc/library/tkinter.rst:225 +msgid "A (Very) Quick Look at Tcl/Tk" +msgstr "" + +#: ../Doc/library/tkinter.rst:227 +msgid "" +"The class hierarchy looks complicated, but in actual practice, application " +"programmers almost always refer to the classes at the very bottom of the " +"hierarchy." +msgstr "" + +#: ../Doc/library/tkinter.rst:233 +msgid "" +"These classes are provided for the purposes of organizing certain functions " +"under one namespace. They aren't meant to be instantiated independently." +msgstr "" + +#: ../Doc/library/tkinter.rst:236 +msgid "" +"The :class:`Tk` class is meant to be instantiated only once in an " +"application. Application programmers need not instantiate one explicitly, " +"the system creates one whenever any of the other classes are instantiated." +msgstr "" + +#: ../Doc/library/tkinter.rst:240 +msgid "" +"The :class:`Widget` class is not meant to be instantiated, it is meant only " +"for subclassing to make \"real\" widgets (in C++, this is called an " +"'abstract class')." +msgstr "" + +#: ../Doc/library/tkinter.rst:244 +msgid "" +"To make use of this reference material, there will be times when you will " +"need to know how to read short passages of Tk and how to identify the " +"various parts of a Tk command. (See section :ref:`tkinter-basic-mapping` " +"for the :mod:`tkinter` equivalents of what's below.)" +msgstr "" + +#: ../Doc/library/tkinter.rst:249 +msgid "" +"Tk scripts are Tcl programs. Like all Tcl programs, Tk scripts are just " +"lists of tokens separated by spaces. A Tk widget is just its *class*, the " +"*options* that help configure it, and the *actions* that make it do useful " +"things." +msgstr "" + +#: ../Doc/library/tkinter.rst:253 +msgid "To make a widget in Tk, the command is always of the form::" +msgstr "" + +#: ../Doc/library/tkinter.rst:258 +msgid "*classCommand*" +msgstr "" + +#: ../Doc/library/tkinter.rst:258 +msgid "denotes which kind of widget to make (a button, a label, a menu...)" +msgstr "" + +#: ../Doc/library/tkinter.rst:265 +msgid "*newPathname*" +msgstr "" + +#: ../Doc/library/tkinter.rst:261 +msgid "" +"is the new name for this widget. All names in Tk must be unique. To help " +"enforce this, widgets in Tk are named with *pathnames*, just like files in a " +"file system. The top level widget, the *root*, is called ``.`` (period) and " +"children are delimited by more periods. For example, ``.myApp.controlPanel." +"okButton`` might be the name of a widget." +msgstr "" + +#: ../Doc/library/tkinter.rst:271 +msgid "*options*" +msgstr "" + +#: ../Doc/library/tkinter.rst:268 +msgid "" +"configure the widget's appearance and in some cases, its behavior. The " +"options come in the form of a list of flags and values. Flags are preceded " +"by a '-', like Unix shell command flags, and values are put in quotes if " +"they are more than one word." +msgstr "" + +#: ../Doc/library/tkinter.rst:281 +msgid "" +"Once created, the pathname to the widget becomes a new command. This new " +"*widget command* is the programmer's handle for getting the new widget to " +"perform some *action*. In C, you'd express this as someAction(fred, " +"someOptions), in C++, you would express this as fred." +"someAction(someOptions), and in Tk, you say::" +msgstr "" + +#: ../Doc/library/tkinter.rst:289 +msgid "Note that the object name, ``.fred``, starts with a dot." +msgstr "" + +#: ../Doc/library/tkinter.rst:291 +msgid "" +"As you'd expect, the legal values for *someAction* will depend on the " +"widget's class: ``.fred disable`` works if fred is a button (fred gets " +"greyed out), but does not work if fred is a label (disabling of labels is " +"not supported in Tk)." +msgstr "" + +#: ../Doc/library/tkinter.rst:295 +msgid "" +"The legal values of *someOptions* is action dependent. Some actions, like " +"``disable``, require no arguments, others, like a text-entry box's " +"``delete`` command, would need arguments to specify what range of text to " +"delete." +msgstr "" + +#: ../Doc/library/tkinter.rst:303 +msgid "Mapping Basic Tk into Tkinter" +msgstr "" + +#: ../Doc/library/tkinter.rst:305 +msgid "Class commands in Tk correspond to class constructors in Tkinter. ::" +msgstr "" + +#: ../Doc/library/tkinter.rst:309 +msgid "" +"The master of an object is implicit in the new name given to it at creation " +"time. In Tkinter, masters are specified explicitly. ::" +msgstr "" + +#: ../Doc/library/tkinter.rst:314 +msgid "" +"The configuration options in Tk are given in lists of hyphened tags followed " +"by values. In Tkinter, options are specified as keyword-arguments in the " +"instance constructor, and keyword-args for configure calls or as instance " +"indices, in dictionary style, for established instances. See section :ref:" +"`tkinter-setting-options` on setting options. ::" +msgstr "" + +#: ../Doc/library/tkinter.rst:324 +msgid "" +"In Tk, to perform an action on a widget, use the widget name as a command, " +"and follow it with an action name, possibly with arguments (options). In " +"Tkinter, you call methods on the class instance to invoke actions on the " +"widget. The actions (methods) that a given widget can perform are listed " +"in :file:`tkinter/__init__.py`. ::" +msgstr "" + +#: ../Doc/library/tkinter.rst:332 +msgid "" +"To give a widget to the packer (geometry manager), you call pack with " +"optional arguments. In Tkinter, the Pack class holds all this " +"functionality, and the various forms of the pack command are implemented as " +"methods. All widgets in :mod:`tkinter` are subclassed from the Packer, and " +"so inherit all the packing methods. See the :mod:`tkinter.tix` module " +"documentation for additional information on the Form geometry manager. ::" +msgstr "" + +#: ../Doc/library/tkinter.rst:343 +msgid "How Tk and Tkinter are Related" +msgstr "" + +#: ../Doc/library/tkinter.rst:345 +msgid "From the top down:" +msgstr "" + +#: ../Doc/library/tkinter.rst:348 +msgid "Your App Here (Python)" +msgstr "" + +#: ../Doc/library/tkinter.rst:348 +msgid "A Python application makes a :mod:`tkinter` call." +msgstr "" + +#: ../Doc/library/tkinter.rst:355 +msgid "tkinter (Python Package)" +msgstr "" + +#: ../Doc/library/tkinter.rst:351 +msgid "" +"This call (say, for example, creating a button widget), is implemented in " +"the :mod:`tkinter` package, which is written in Python. This Python " +"function will parse the commands and the arguments and convert them into a " +"form that makes them look as if they had come from a Tk script instead of a " +"Python script." +msgstr "" + +#: ../Doc/library/tkinter.rst:359 +msgid "_tkinter (C)" +msgstr "" + +#: ../Doc/library/tkinter.rst:358 +msgid "" +"These commands and their arguments will be passed to a C function in the :" +"mod:`_tkinter` - note the underscore - extension module." +msgstr "" + +#: ../Doc/library/tkinter.rst:366 +msgid "Tk Widgets (C and Tcl)" +msgstr "" + +#: ../Doc/library/tkinter.rst:362 +msgid "" +"This C function is able to make calls into other C modules, including the C " +"functions that make up the Tk library. Tk is implemented in C and some Tcl. " +"The Tcl part of the Tk widgets is used to bind certain default behaviors to " +"widgets, and is executed once at the point where the Python :mod:`tkinter` " +"package is imported. (The user never sees this stage)." +msgstr "" + +#: ../Doc/library/tkinter.rst:369 +msgid "Tk (C)" +msgstr "" + +#: ../Doc/library/tkinter.rst:369 +msgid "The Tk part of the Tk Widgets implement the final mapping to ..." +msgstr "" + +#: ../Doc/library/tkinter.rst:373 +msgid "Xlib (C)" +msgstr "" + +#: ../Doc/library/tkinter.rst:372 +msgid "the Xlib library to draw graphics on the screen." +msgstr "" + +#: ../Doc/library/tkinter.rst:376 +msgid "Handy Reference" +msgstr "" + +#: ../Doc/library/tkinter.rst:382 +msgid "Setting Options" +msgstr "" + +#: ../Doc/library/tkinter.rst:384 +msgid "" +"Options control things like the color and border width of a widget. Options " +"can be set in three ways:" +msgstr "" + +#: ../Doc/library/tkinter.rst:390 +msgid "At object creation time, using keyword arguments" +msgstr "" + +#: ../Doc/library/tkinter.rst:396 +msgid "After object creation, treating the option name like a dictionary index" +msgstr "" + +#: ../Doc/library/tkinter.rst:401 +msgid "" +"Use the config() method to update multiple attrs subsequent to object " +"creation" +msgstr "" + +#: ../Doc/library/tkinter.rst:403 +msgid "" +"For a complete explanation of a given option and its behavior, see the Tk " +"man pages for the widget in question." +msgstr "" + +#: ../Doc/library/tkinter.rst:406 +msgid "" +"Note that the man pages list \"STANDARD OPTIONS\" and \"WIDGET SPECIFIC " +"OPTIONS\" for each widget. The former is a list of options that are common " +"to many widgets, the latter are the options that are idiosyncratic to that " +"particular widget. The Standard Options are documented on the :manpage:" +"`options(3)` man page." +msgstr "" + +#: ../Doc/library/tkinter.rst:412 +msgid "" +"No distinction between standard and widget-specific options is made in this " +"document. Some options don't apply to some kinds of widgets. Whether a " +"given widget responds to a particular option depends on the class of the " +"widget; buttons have a ``command`` option, labels do not." +msgstr "" + +#: ../Doc/library/tkinter.rst:417 +msgid "" +"The options supported by a given widget are listed in that widget's man " +"page, or can be queried at runtime by calling the :meth:`config` method " +"without arguments, or by calling the :meth:`keys` method on that widget. " +"The return value of these calls is a dictionary whose key is the name of the " +"option as a string (for example, ``'relief'``) and whose values are 5-tuples." +msgstr "" + +#: ../Doc/library/tkinter.rst:423 +msgid "" +"Some options, like ``bg`` are synonyms for common options with long names " +"(``bg`` is shorthand for \"background\"). Passing the ``config()`` method " +"the name of a shorthand option will return a 2-tuple, not 5-tuple. The 2-" +"tuple passed back will contain the name of the synonym and the \"real\" " +"option (such as ``('bg', 'background')``)." +msgstr "" + +#: ../Doc/library/tkinter.rst:432 +msgid "option name" +msgstr "" + +#: ../Doc/library/tkinter.rst:432 ../Doc/library/tkinter.rst:434 +msgid "``'relief'``" +msgstr "" + +#: ../Doc/library/tkinter.rst:434 +msgid "option name for database lookup" +msgstr "" + +#: ../Doc/library/tkinter.rst:436 +msgid "option class for database lookup" +msgstr "" + +#: ../Doc/library/tkinter.rst:436 +msgid "``'Relief'``" +msgstr "" + +#: ../Doc/library/tkinter.rst:439 +msgid "default value" +msgstr "" + +#: ../Doc/library/tkinter.rst:439 +msgid "``'raised'``" +msgstr "" + +#: ../Doc/library/tkinter.rst:441 +msgid "current value" +msgstr "" + +#: ../Doc/library/tkinter.rst:441 +msgid "``'groove'``" +msgstr "" + +#: ../Doc/library/tkinter.rst:449 +msgid "" +"Of course, the dictionary printed will include all the options available and " +"their values. This is meant only as an example." +msgstr "" + +#: ../Doc/library/tkinter.rst:454 +msgid "The Packer" +msgstr "" + +#: ../Doc/library/tkinter.rst:458 +msgid "" +"The packer is one of Tk's geometry-management mechanisms. Geometry " +"managers are used to specify the relative positioning of the positioning of " +"widgets within their container - their mutual *master*. In contrast to the " +"more cumbersome *placer* (which is used less commonly, and we do not cover " +"here), the packer takes qualitative relationship specification - *above*, " +"*to the left of*, *filling*, etc - and works everything out to determine the " +"exact placement coordinates for you." +msgstr "" + +#: ../Doc/library/tkinter.rst:466 +msgid "" +"The size of any *master* widget is determined by the size of the \"slave " +"widgets\" inside. The packer is used to control where slave widgets appear " +"inside the master into which they are packed. You can pack widgets into " +"frames, and frames into other frames, in order to achieve the kind of layout " +"you desire. Additionally, the arrangement is dynamically adjusted to " +"accommodate incremental changes to the configuration, once it is packed." +msgstr "" + +#: ../Doc/library/tkinter.rst:473 +msgid "" +"Note that widgets do not appear until they have had their geometry specified " +"with a geometry manager. It's a common early mistake to leave out the " +"geometry specification, and then be surprised when the widget is created but " +"nothing appears. A widget will appear only after it has had, for example, " +"the packer's :meth:`pack` method applied to it." +msgstr "" + +#: ../Doc/library/tkinter.rst:479 +msgid "" +"The pack() method can be called with keyword-option/value pairs that control " +"where the widget is to appear within its container, and how it is to behave " +"when the main application window is resized. Here are some examples::" +msgstr "" + +#: ../Doc/library/tkinter.rst:489 +msgid "Packer Options" +msgstr "" + +#: ../Doc/library/tkinter.rst:491 +msgid "" +"For more extensive information on the packer and the options that it can " +"take, see the man pages and page 183 of John Ousterhout's book." +msgstr "" + +#: ../Doc/library/tkinter.rst:495 ../Doc/library/tkinter.rst:611 +msgid "anchor" +msgstr "" + +#: ../Doc/library/tkinter.rst:495 +msgid "" +"Anchor type. Denotes where the packer is to place each slave in its parcel." +msgstr "" + +#: ../Doc/library/tkinter.rst:498 +msgid "expand" +msgstr "" + +#: ../Doc/library/tkinter.rst:498 +msgid "Boolean, ``0`` or ``1``." +msgstr "" + +#: ../Doc/library/tkinter.rst:501 +msgid "fill" +msgstr "" + +#: ../Doc/library/tkinter.rst:501 +msgid "Legal values: ``'x'``, ``'y'``, ``'both'``, ``'none'``." +msgstr "" + +#: ../Doc/library/tkinter.rst:504 +msgid "ipadx and ipady" +msgstr "" + +#: ../Doc/library/tkinter.rst:504 +msgid "" +"A distance - designating internal padding on each side of the slave widget." +msgstr "" + +#: ../Doc/library/tkinter.rst:507 +msgid "padx and pady" +msgstr "" + +#: ../Doc/library/tkinter.rst:507 +msgid "" +"A distance - designating external padding on each side of the slave widget." +msgstr "" + +#: ../Doc/library/tkinter.rst:511 +msgid "side" +msgstr "" + +#: ../Doc/library/tkinter.rst:510 +msgid "Legal values are: ``'left'``, ``'right'``, ``'top'``, ``'bottom'``." +msgstr "" + +#: ../Doc/library/tkinter.rst:514 +msgid "Coupling Widget Variables" +msgstr "" + +#: ../Doc/library/tkinter.rst:516 +msgid "" +"The current-value setting of some widgets (like text entry widgets) can be " +"connected directly to application variables by using special options. These " +"options are ``variable``, ``textvariable``, ``onvalue``, ``offvalue``, and " +"``value``. This connection works both ways: if the variable changes for any " +"reason, the widget it's connected to will be updated to reflect the new " +"value." +msgstr "" + +#: ../Doc/library/tkinter.rst:522 +msgid "" +"Unfortunately, in the current implementation of :mod:`tkinter` it is not " +"possible to hand over an arbitrary Python variable to a widget through a " +"``variable`` or ``textvariable`` option. The only kinds of variables for " +"which this works are variables that are subclassed from a class called " +"Variable, defined in :mod:`tkinter`." +msgstr "" + +#: ../Doc/library/tkinter.rst:528 +msgid "" +"There are many useful subclasses of Variable already defined: :class:" +"`StringVar`, :class:`IntVar`, :class:`DoubleVar`, and :class:`BooleanVar`. " +"To read the current value of such a variable, call the :meth:`get` method on " +"it, and to change its value you call the :meth:`!set` method. If you follow " +"this protocol, the widget will always track the value of the variable, with " +"no further intervention on your part." +msgstr "" + +#: ../Doc/library/tkinter.rst:564 +msgid "The Window Manager" +msgstr "" + +#: ../Doc/library/tkinter.rst:568 +msgid "" +"In Tk, there is a utility command, ``wm``, for interacting with the window " +"manager. Options to the ``wm`` command allow you to control things like " +"titles, placement, icon bitmaps, and the like. In :mod:`tkinter`, these " +"commands have been implemented as methods on the :class:`Wm` class. " +"Toplevel widgets are subclassed from the :class:`Wm` class, and so can call " +"the :class:`Wm` methods directly." +msgstr "" + +#: ../Doc/library/tkinter.rst:575 +msgid "" +"To get at the toplevel window that contains a given widget, you can often " +"just refer to the widget's master. Of course if the widget has been packed " +"inside of a frame, the master won't represent a toplevel window. To get at " +"the toplevel window that contains an arbitrary widget, you can call the :" +"meth:`_root` method. This method begins with an underscore to denote the " +"fact that this function is part of the implementation, and not an interface " +"to Tk functionality." +msgstr "" + +#: ../Doc/library/tkinter.rst:582 +msgid "Here are some examples of typical usage::" +msgstr "" + +#: ../Doc/library/tkinter.rst:605 +msgid "Tk Option Data Types" +msgstr "" + +#: ../Doc/library/tkinter.rst:610 +msgid "" +"Legal values are points of the compass: ``\"n\"``, ``\"ne\"``, ``\"e\"``, ``" +"\"se\"``, ``\"s\"``, ``\"sw\"``, ``\"w\"``, ``\"nw\"``, and also ``\"center" +"\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:617 +msgid "bitmap" +msgstr "" + +#: ../Doc/library/tkinter.rst:614 +msgid "" +"There are eight built-in, named bitmaps: ``'error'``, ``'gray25'``, " +"``'gray50'``, ``'hourglass'``, ``'info'``, ``'questhead'``, ``'question'``, " +"``'warning'``. To specify an X bitmap filename, give the full path to the " +"file, preceded with an ``@``, as in ``\"@/usr/contrib/bitmap/gumby.bit\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:620 +msgid "boolean" +msgstr "" + +#: ../Doc/library/tkinter.rst:620 +msgid "You can pass integers 0 or 1 or the strings ``\"yes\"`` or ``\"no\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:627 +msgid "callback" +msgstr "" + +#: ../Doc/library/tkinter.rst:623 +msgid "This is any Python function that takes no arguments. For example::" +msgstr "" + +#: ../Doc/library/tkinter.rst:633 +msgid "color" +msgstr "" + +#: ../Doc/library/tkinter.rst:630 +msgid "" +"Colors can be given as the names of X colors in the rgb.txt file, or as " +"strings representing RGB values in 4 bit: ``\"#RGB\"``, 8 bit: ``\"#RRGGBB" +"\"``, 12 bit\" ``\"#RRRGGGBBB\"``, or 16 bit ``\"#RRRRGGGGBBBB\"`` ranges, " +"where R,G,B here represent any legal hex digit. See page 160 of " +"Ousterhout's book for details." +msgstr "" + +#: ../Doc/library/tkinter.rst:639 ../Doc/library/tkinter.ttk.rst:121 +msgid "cursor" +msgstr "" + +#: ../Doc/library/tkinter.rst:636 +msgid "" +"The standard X cursor names from :file:`cursorfont.h` can be used, without " +"the ``XC_`` prefix. For example to get a hand cursor (:const:`XC_hand2`), " +"use the string ``\"hand2\"``. You can also specify a bitmap and mask file " +"of your own. See page 179 of Ousterhout's book." +msgstr "" + +#: ../Doc/library/tkinter.rst:646 +msgid "distance" +msgstr "" + +#: ../Doc/library/tkinter.rst:642 +msgid "" +"Screen distances can be specified in either pixels or absolute distances. " +"Pixels are given as numbers and absolute distances as strings, with the " +"trailing character denoting units: ``c`` for centimetres, ``i`` for inches, " +"``m`` for millimetres, ``p`` for printer's points. For example, 3.5 inches " +"is expressed as ``\"3.5i\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:651 ../Doc/library/tkinter.ttk.rst:814 +msgid "font" +msgstr "" + +#: ../Doc/library/tkinter.rst:649 +msgid "" +"Tk uses a list font name format, such as ``{courier 10 bold}``. Font sizes " +"with positive numbers are measured in points; sizes with negative numbers " +"are measured in pixels." +msgstr "" + +#: ../Doc/library/tkinter.rst:656 +msgid "geometry" +msgstr "" + +#: ../Doc/library/tkinter.rst:654 +msgid "" +"This is a string of the form ``widthxheight``, where width and height are " +"measured in pixels for most widgets (in characters for widgets displaying " +"text). For example: ``fred[\"geometry\"] = \"200x100\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:660 ../Doc/library/tkinter.ttk.rst:325 +msgid "justify" +msgstr "" + +#: ../Doc/library/tkinter.rst:659 +msgid "" +"Legal values are the strings: ``\"left\"``, ``\"center\"``, ``\"right\"``, " +"and ``\"fill\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:665 ../Doc/library/tkinter.ttk.rst:1002 +msgid "region" +msgstr "" + +#: ../Doc/library/tkinter.rst:663 +msgid "" +"This is a string with four space-delimited elements, each of which is a " +"legal distance (see above). For example: ``\"2 3 4 5\"`` and ``\"3i 2i 4.5i " +"2i\"`` and ``\"3c 2c 4c 10.43c\"`` are all legal regions." +msgstr "" + +#: ../Doc/library/tkinter.rst:669 +msgid "relief" +msgstr "" + +#: ../Doc/library/tkinter.rst:668 +msgid "" +"Determines what the border style of a widget will be. Legal values are: ``" +"\"raised\"``, ``\"sunken\"``, ``\"flat\"``, ``\"groove\"``, and ``\"ridge" +"\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:673 +msgid "scrollcommand" +msgstr "" + +#: ../Doc/library/tkinter.rst:672 +msgid "" +"This is almost always the :meth:`!set` method of some scrollbar widget, but " +"can be any widget method that takes a single argument." +msgstr "" + +#: ../Doc/library/tkinter.rst:677 +msgid "wrap:" +msgstr "" + +#: ../Doc/library/tkinter.rst:676 +msgid "Must be one of: ``\"none\"``, ``\"char\"``, or ``\"word\"``." +msgstr "" + +#: ../Doc/library/tkinter.rst:680 +msgid "Bindings and Events" +msgstr "" + +#: ../Doc/library/tkinter.rst:686 +msgid "" +"The bind method from the widget command allows you to watch for certain " +"events and to have a callback function trigger when that event type occurs. " +"The form of the bind method is::" +msgstr "" + +#: ../Doc/library/tkinter.rst:692 +msgid "where:" +msgstr "" + +#: ../Doc/library/tkinter.rst:696 +msgid "sequence" +msgstr "" + +#: ../Doc/library/tkinter.rst:695 +msgid "" +"is a string that denotes the target kind of event. (See the bind man page " +"and page 201 of John Ousterhout's book for details)." +msgstr "" + +#: ../Doc/library/tkinter.rst:701 +msgid "func" +msgstr "" + +#: ../Doc/library/tkinter.rst:699 +msgid "" +"is a Python function, taking one argument, to be invoked when the event " +"occurs. An Event instance will be passed as the argument. (Functions " +"deployed this way are commonly known as *callbacks*.)" +msgstr "" + +#: ../Doc/library/tkinter.rst:707 +msgid "add" +msgstr "" + +#: ../Doc/library/tkinter.rst:704 +msgid "" +"is optional, either ``''`` or ``'+'``. Passing an empty string denotes that " +"this binding is to replace any other bindings that this event is associated " +"with. Passing a ``'+'`` means that this function is to be added to the list " +"of functions bound to this event type." +msgstr "" + +#: ../Doc/library/tkinter.rst:716 +msgid "" +"Notice how the widget field of the event is being accessed in the " +"``turn_red()`` callback. This field contains the widget that caught the X " +"event. The following table lists the other event fields you can access, and " +"how they are denoted in Tk, which can be useful when referring to the Tk man " +"pages." +msgstr "" + +#: ../Doc/library/tkinter.rst:722 +msgid "Tk" +msgstr "" + +#: ../Doc/library/tkinter.rst:722 +msgid "Tkinter Event Field" +msgstr "" + +#: ../Doc/library/tkinter.rst:724 +msgid "%f" +msgstr "" + +#: ../Doc/library/tkinter.rst:724 ../Doc/library/tkinter.ttk.rst:239 +msgid "focus" +msgstr "" + +#: ../Doc/library/tkinter.rst:724 +msgid "%A" +msgstr "" + +#: ../Doc/library/tkinter.rst:724 +msgid "char" +msgstr "" + +#: ../Doc/library/tkinter.rst:726 +msgid "%h" +msgstr "" + +#: ../Doc/library/tkinter.rst:726 ../Doc/library/tkinter.ttk.rst:328 +#: ../Doc/library/tkinter.ttk.rst:402 ../Doc/library/tkinter.ttk.rst:739 +msgid "height" +msgstr "" + +#: ../Doc/library/tkinter.rst:726 +msgid "%E" +msgstr "" + +#: ../Doc/library/tkinter.rst:726 +msgid "send_event" +msgstr "" + +#: ../Doc/library/tkinter.rst:728 +msgid "%k" +msgstr "" + +#: ../Doc/library/tkinter.rst:728 +msgid "keycode" +msgstr "" + +#: ../Doc/library/tkinter.rst:728 +msgid "%K" +msgstr "" + +#: ../Doc/library/tkinter.rst:728 +msgid "keysym" +msgstr "" + +#: ../Doc/library/tkinter.rst:730 +msgid "%s" +msgstr "" + +#: ../Doc/library/tkinter.rst:730 ../Doc/library/tkinter.ttk.rst:218 +#: ../Doc/library/tkinter.ttk.rst:334 ../Doc/library/tkinter.ttk.rst:428 +msgid "state" +msgstr "" + +#: ../Doc/library/tkinter.rst:730 +msgid "%N" +msgstr "" + +#: ../Doc/library/tkinter.rst:730 +msgid "keysym_num" +msgstr "" + +#: ../Doc/library/tkinter.rst:732 +msgid "%t" +msgstr "" + +#: ../Doc/library/tkinter.rst:732 +msgid "time" +msgstr "" + +#: ../Doc/library/tkinter.rst:732 +msgid "%T" +msgstr "" + +#: ../Doc/library/tkinter.rst:734 +msgid "%w" +msgstr "" + +#: ../Doc/library/tkinter.rst:734 ../Doc/library/tkinter.ttk.rst:203 +#: ../Doc/library/tkinter.ttk.rst:349 ../Doc/library/tkinter.ttk.rst:412 +msgid "width" +msgstr "" + +#: ../Doc/library/tkinter.rst:734 +msgid "%W" +msgstr "" + +#: ../Doc/library/tkinter.rst:734 +msgid "widget" +msgstr "" + +#: ../Doc/library/tkinter.rst:736 +msgid "%x" +msgstr "" + +#: ../Doc/library/tkinter.rst:736 +msgid "x" +msgstr "" + +#: ../Doc/library/tkinter.rst:736 +msgid "%X" +msgstr "" + +#: ../Doc/library/tkinter.rst:736 +msgid "x_root" +msgstr "" + +#: ../Doc/library/tkinter.rst:738 +msgid "%y" +msgstr "" + +#: ../Doc/library/tkinter.rst:738 +msgid "y" +msgstr "" + +#: ../Doc/library/tkinter.rst:738 +msgid "%Y" +msgstr "" + +#: ../Doc/library/tkinter.rst:738 +msgid "y_root" +msgstr "" + +#: ../Doc/library/tkinter.rst:743 +msgid "The index Parameter" +msgstr "" + +#: ../Doc/library/tkinter.rst:745 +msgid "" +"A number of widgets require \"index\" parameters to be passed. These are " +"used to point at a specific place in a Text widget, or to particular " +"characters in an Entry widget, or to particular menu items in a Menu widget." +msgstr "" + +#: ../Doc/library/tkinter.rst:752 +msgid "Entry widget indexes (index, view index, etc.)" +msgstr "" + +#: ../Doc/library/tkinter.rst:750 +msgid "" +"Entry widgets have options that refer to character positions in the text " +"being displayed. You can use these :mod:`tkinter` functions to access these " +"special points in text widgets:" +msgstr "" + +#: ../Doc/library/tkinter.rst:756 +msgid "Text widget indexes" +msgstr "" + +#: ../Doc/library/tkinter.rst:755 +msgid "" +"The index notation for Text widgets is very rich and is best described in " +"the Tk man pages." +msgstr "" + +#: ../Doc/library/tkinter.rst:781 +msgid "Menu indexes (menu.invoke(), menu.entryconfig(), etc.)" +msgstr "" + +#: ../Doc/library/tkinter.rst:759 +msgid "" +"Some options and methods for menus manipulate specific menu entries. Anytime " +"a menu index is needed for an option or a parameter, you may pass in:" +msgstr "" + +#: ../Doc/library/tkinter.rst:762 +msgid "" +"an integer which refers to the numeric position of the entry in the widget, " +"counted from the top, starting with 0;" +msgstr "" + +#: ../Doc/library/tkinter.rst:765 +msgid "" +"the string ``\"active\"``, which refers to the menu position that is " +"currently under the cursor;" +msgstr "" + +#: ../Doc/library/tkinter.rst:768 +msgid "the string ``\"last\"`` which refers to the last menu item;" +msgstr "" + +#: ../Doc/library/tkinter.rst:770 +msgid "" +"An integer preceded by ``@``, as in ``@6``, where the integer is interpreted " +"as a y pixel coordinate in the menu's coordinate system;" +msgstr "" + +#: ../Doc/library/tkinter.rst:773 +msgid "" +"the string ``\"none\"``, which indicates no menu entry at all, most often " +"used with menu.activate() to deactivate all entries, and finally," +msgstr "" + +#: ../Doc/library/tkinter.rst:776 +msgid "" +"a text string that is pattern matched against the label of the menu entry, " +"as scanned from the top of the menu to the bottom. Note that this index " +"type is considered after all the others, which means that matches for menu " +"items labelled ``last``, ``active``, or ``none`` may be interpreted as the " +"above literals, instead." +msgstr "" + +#: ../Doc/library/tkinter.rst:784 +msgid "Images" +msgstr "" + +#: ../Doc/library/tkinter.rst:786 +msgid "" +"Bitmap/Pixelmap images can be created through the subclasses of :class:" +"`tkinter.Image`:" +msgstr "" + +#: ../Doc/library/tkinter.rst:789 +msgid ":class:`BitmapImage` can be used for X11 bitmap data." +msgstr "" + +#: ../Doc/library/tkinter.rst:791 +msgid ":class:`PhotoImage` can be used for GIF and PPM/PGM color bitmaps." +msgstr "" + +#: ../Doc/library/tkinter.rst:793 +msgid "" +"Either type of image is created through either the ``file`` or the ``data`` " +"option (other options are available as well)." +msgstr "" + +#: ../Doc/library/tkinter.rst:796 +msgid "" +"The image object can then be used wherever an ``image`` option is supported " +"by some widget (e.g. labels, buttons, menus). In these cases, Tk will not " +"keep a reference to the image. When the last Python reference to the image " +"object is deleted, the image data is deleted as well, and Tk will display an " +"empty box wherever the image was used." +msgstr "" + +#: ../Doc/library/tkinter.rst:806 +msgid "File Handlers" +msgstr "" + +#: ../Doc/library/tkinter.rst:808 +msgid "" +"Tk allows you to register and unregister a callback function which will be " +"called from the Tk mainloop when I/O is possible on a file descriptor. Only " +"one handler may be registered per file descriptor. Example code::" +msgstr "" + +#: ../Doc/library/tkinter.rst:819 +msgid "This feature is not available on Windows." +msgstr "" + +#: ../Doc/library/tkinter.rst:821 +msgid "" +"Since you don't know how many bytes are available for reading, you may not " +"want to use the :class:`~io.BufferedIOBase` or :class:`~io.TextIOBase` :meth:" +"`~io.BufferedIOBase.read` or :meth:`~io.IOBase.readline` methods, since " +"these will insist on reading a predefined number of bytes. For sockets, the :" +"meth:`~socket.socket.recv` or :meth:`~socket.socket.recvfrom` methods will " +"work fine; for other files, use raw reads or ``os.read(file.fileno(), " +"maxbytecount)``." +msgstr "" + +#: ../Doc/library/tkinter.rst:832 +msgid "" +"Registers the file handler callback function *func*. The *file* argument may " +"either be an object with a :meth:`~io.IOBase.fileno` method (such as a file " +"or socket object), or an integer file descriptor. The *mask* argument is an " +"ORed combination of any of the three constants below. The callback is called " +"as follows::" +msgstr "" + +#: ../Doc/library/tkinter.rst:843 +msgid "Unregisters a file handler." +msgstr "" + +#: ../Doc/library/tkinter.rst:850 +msgid "Constants used in the *mask* arguments." +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:2 +msgid ":mod:`tkinter.scrolledtext` --- Scrolled Text Widget" +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:10 +msgid "**Source code:** :source:`Lib/tkinter/scrolledtext.py`" +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:14 +msgid "" +"The :mod:`tkinter.scrolledtext` module provides a class of the same name " +"which implements a basic text widget which has a vertical scroll bar " +"configured to do the \"right thing.\" Using the :class:`ScrolledText` class " +"is a lot easier than setting up a text widget and scroll bar directly. The " +"constructor is the same as that of the :class:`tkinter.Text` class." +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:20 +msgid "" +"The text widget and scrollbar are packed together in a :class:`Frame`, and " +"the methods of the :class:`Grid` and :class:`Pack` geometry managers are " +"acquired from the :class:`Frame` object. This allows the :class:" +"`ScrolledText` widget to be used directly to achieve most normal geometry " +"management behavior." +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:25 +msgid "" +"Should more specific control be necessary, the following attributes are " +"available:" +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:31 +msgid "The frame which surrounds the text and scroll bar widgets." +msgstr "" + +#: ../Doc/library/tkinter.scrolledtext.rst:36 +msgid "The scroll bar widget." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:2 +msgid ":mod:`tkinter.tix` --- Extension widgets for Tk" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:9 +msgid "**Source code:** :source:`Lib/tkinter/tix.py`" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:13 +msgid "" +"This Tk extension is unmaintained and should not be used in new code. Use :" +"mod:`tkinter.ttk` instead." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:19 +msgid "" +"The :mod:`tkinter.tix` (Tk Interface Extension) module provides an " +"additional rich set of widgets. Although the standard Tk library has many " +"useful widgets, they are far from complete. The :mod:`tkinter.tix` library " +"provides most of the commonly needed widgets that are missing from standard " +"Tk: :class:`HList`, :class:`ComboBox`, :class:`Control` (a.k.a. SpinBox) and " +"an assortment of scrollable widgets. :mod:`tkinter.tix` also includes many " +"more widgets that are generally useful in a wide range of applications: :" +"class:`NoteBook`, :class:`FileEntry`, :class:`PanedWindow`, etc; there are " +"more than 40 of them." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:29 +msgid "" +"With all these new widgets, you can introduce new interaction techniques " +"into applications, creating more useful and more intuitive user interfaces. " +"You can design your application by choosing the most appropriate widgets to " +"match the special needs of your application and users." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:38 +msgid "`Tix Homepage `_" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:37 +msgid "" +"The home page for :mod:`Tix`. This includes links to additional " +"documentation and downloads." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:41 +msgid "`Tix Man Pages `_" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:41 +msgid "On-line version of the man pages and reference material." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:44 +msgid "" +"`Tix Programming Guide `_" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:44 +msgid "On-line version of the programmer's reference material." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:48 +msgid "" +"`Tix Development Applications `_" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:47 +msgid "" +"Tix applications for development of Tix and Tkinter programs. Tide " +"applications work under Tk or Tkinter, and include :program:`TixInspect`, an " +"inspector to remotely modify and debug Tix/Tk/Tkinter applications." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:53 +msgid "Using Tix" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:58 +msgid "" +"Toplevel widget of Tix which represents mostly the main window of an " +"application. It has an associated Tcl interpreter." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:61 +msgid "" +"Classes in the :mod:`tkinter.tix` module subclasses the classes in the :mod:" +"`tkinter`. The former imports the latter, so to use :mod:`tkinter.tix` with " +"Tkinter, all you need to do is to import one module. In general, you can " +"just import :mod:`tkinter.tix`, and replace the toplevel call to :class:" +"`tkinter.Tk` with :class:`tix.Tk`::" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:71 +msgid "" +"To use :mod:`tkinter.tix`, you must have the Tix widgets installed, usually " +"alongside your installation of the Tk widgets. To test your installation, " +"try the following::" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:79 +msgid "" +"If this fails, you have a Tk installation problem which must be resolved " +"before proceeding. Use the environment variable :envvar:`TIX_LIBRARY` to " +"point to the installed Tix library directory, and make sure you have the " +"dynamic object library (:file:`tix8183.dll` or :file:`libtix8183.so`) in " +"the same directory that contains your Tk dynamic object library (:file:" +"`tk8183.dll` or :file:`libtk8183.so`). The directory with the dynamic object " +"library should also have a file called :file:`pkgIndex.tcl` (case " +"sensitive), which contains the line::" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:92 +msgid "Tix Widgets" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:94 +msgid "" +"`Tix `_ introduces over 40 widget classes to the :mod:`tkinter` repertoire." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:99 +msgid "Basic Widgets" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:104 +msgid "" +"A `Balloon `_ that pops up over a widget to provide help. When the user " +"moves the cursor inside a widget to which a Balloon widget has been bound, a " +"small pop-up window with a descriptive message will be shown on the screen." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:116 +msgid "" +"The `ButtonBox `_ widget creates a box of buttons, such as is commonly " +"used for ``Ok Cancel``." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:126 +msgid "" +"The `ComboBox `_ widget is similar to the combo box control in MS Windows. " +"The user can select a choice by either typing in the entry subwidget or " +"selecting from the listbox subwidget." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:138 +msgid "" +"The `Control `_ widget is also known as the :class:`SpinBox` widget. The " +"user can adjust the value by pressing the two arrow buttons or by entering " +"the value directly into the entry. The new value will be checked against the " +"user-defined upper and lower limits." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:151 +msgid "" +"The `LabelEntry `_ widget packages an entry widget and a label into one " +"mega widget. It can be used to simplify the creation of \"entry-form\" type " +"of interface." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:162 +msgid "" +"The `LabelFrame `_ widget packages a frame widget and a label into one " +"mega widget. To create widgets inside a LabelFrame widget, one creates the " +"new widgets relative to the :attr:`frame` subwidget and manage them inside " +"the :attr:`frame` subwidget." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:174 +msgid "" +"The `Meter `_ widget can be used to show the progress of a background job which may " +"take a long time to execute." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:185 +msgid "" +"The `OptionMenu `_ creates a menu button of options." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:195 +msgid "" +"The `PopupMenu `_ widget can be used as a replacement of the ``tk_popup`` " +"command. The advantage of the :mod:`Tix` :class:`PopupMenu` widget is it " +"requires less application code to manipulate." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:207 +msgid "" +"The `Select `_ widget is a container of button subwidgets. It can be used " +"to provide radio-box or check-box style of selection options for the user." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:218 +msgid "" +"The `StdButtonBox `_ widget is a group of standard buttons for Motif-like " +"dialog boxes." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:227 +msgid "File Selectors" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:232 +msgid "" +"The `DirList `_ widget displays a list view of a directory, its previous " +"directories and its sub-directories. The user can choose one of the " +"directories displayed in the list or change to another directory." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:244 +msgid "" +"The `DirTree `_ widget displays a tree view of a directory, its previous " +"directories and its sub-directories. The user can choose one of the " +"directories displayed in the list or change to another directory." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:256 +msgid "" +"The `DirSelectDialog `_ widget presents the directories in the file " +"system in a dialog window. The user can use this dialog window to navigate " +"through the file system to select the desired directory." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:268 +msgid "" +"The :class:`DirSelectBox` is similar to the standard Motif(TM) directory-" +"selection box. It is generally used for the user to choose a directory. " +"DirSelectBox stores the directories mostly recently selected into a ComboBox " +"widget so that they can be quickly selected again." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:276 +msgid "" +"The `ExFileSelectBox `_ widget is usually embedded in a " +"tixExFileSelectDialog widget. It provides a convenient method for the user " +"to select files. The style of the :class:`ExFileSelectBox` widget is very " +"similar to the standard file dialog on MS Windows 3.1." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:289 +msgid "" +"The `FileSelectBox `_ is similar to the standard Motif(TM) file-selection " +"box. It is generally used for the user to choose a file. FileSelectBox " +"stores the files mostly recently selected into a :class:`ComboBox` widget so " +"that they can be quickly selected again." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:302 +msgid "" +"The `FileEntry `_ widget can be used to input a filename. The user can " +"type in the filename manually. Alternatively, the user can press the button " +"widget that sits next to the entry, which will bring up a file selection " +"dialog." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:313 +msgid "Hierarchical ListBox" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:318 +msgid "" +"The `HList `_ widget can be used to display any data that have a hierarchical " +"structure, for example, file system directory trees. The list entries are " +"indented and connected by branch lines according to their places in the " +"hierarchy." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:330 +msgid "" +"The `CheckList `_ widget displays a list of items to be selected by the " +"user. CheckList acts similarly to the Tk checkbutton or radiobutton widgets, " +"except it is capable of handling many more items than checkbuttons or " +"radiobuttons." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:346 +msgid "" +"The `Tree `_ widget can be used to display hierarchical data in a tree form. The " +"user can adjust the view of the tree by opening or closing parts of the tree." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:358 +msgid "Tabular ListBox" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:363 +msgid "" +"The `TList `_ widget can be used to display data in a tabular format. The list " +"entries of a :class:`TList` widget are similar to the entries in the Tk " +"listbox widget. The main differences are (1) the :class:`TList` widget can " +"display the list entries in a two dimensional format and (2) you can use " +"graphical images as well as multiple colors and fonts for the list entries." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:386 +msgid "Manager Widgets" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:391 +msgid "" +"The `PanedWindow `_ widget allows the user to interactively manipulate the " +"sizes of several panes. The panes can be arranged either vertically or " +"horizontally. The user changes the sizes of the panes by dragging the " +"resize handle between two panes." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:403 +msgid "" +"The `ListNoteBook `_ widget is very similar to the :class:`TixNoteBook` " +"widget: it can be used to display many windows in a limited space using a " +"notebook metaphor. The notebook is divided into a stack of pages (windows). " +"At one time only one of these pages can be shown. The user can navigate " +"through these pages by choosing the name of the desired page in the :attr:" +"`hlist` subwidget." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:417 +msgid "" +"The `NoteBook `_ widget can be used to display many windows in a limited " +"space using a notebook metaphor. The notebook is divided into a stack of " +"pages. At one time only one of these pages can be shown. The user can " +"navigate through these pages by choosing the visual \"tabs\" at the top of " +"the NoteBook widget." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:439 +msgid "Image Types" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:441 +msgid "The :mod:`tkinter.tix` module adds:" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:443 +msgid "" +"`pixmap `_ capabilities to all :mod:`tkinter.tix` and :mod:`tkinter` widgets to " +"create color images from XPM files." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:452 +msgid "" +"`Compound `_ image types can be used to create images that consists of multiple " +"horizontal lines; each line is composed of a series of items (texts, " +"bitmaps, images or spaces) arranged from left to right. For example, a " +"compound image can be used to display a bitmap and a text string " +"simultaneously in a Tk :class:`Button` widget." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:471 +msgid "Miscellaneous Widgets" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:476 +msgid "" +"The `InputOnly `_ widgets are to accept inputs from the user, which can be " +"done with the ``bind`` command (Unix only)." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:483 +msgid "Form Geometry Manager" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:485 +msgid "In addition, :mod:`tkinter.tix` augments :mod:`tkinter` by providing:" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:490 +msgid "" +"The `Form `_ geometry manager based on attachment rules for all Tk widgets." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:496 +msgid "Tix Commands" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:501 +msgid "" +"The `tix commands `_ provide access to miscellaneous elements of :mod:`Tix`'s internal " +"state and the :mod:`Tix` application context. Most of the information " +"manipulated by these methods pertains to the application as a whole, or to a " +"screen or display, rather than to a particular window." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:508 +msgid "To view the current settings, the common usage is::" +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:517 +msgid "" +"Query or modify the configuration options of the Tix application context. If " +"no option is specified, returns a dictionary all of the available options. " +"If option is specified with no value, then the method returns a list " +"describing the one named option (this list will be identical to the " +"corresponding sublist of the value returned if no option is specified). If " +"one or more option-value pairs are specified, then the method modifies the " +"given option(s) to have the given value(s); in this case the method returns " +"an empty string. Option may be any of the configuration options." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:529 +msgid "" +"Returns the current value of the configuration option given by *option*. " +"Option may be any of the configuration options." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:535 +msgid "" +"Locates a bitmap file of the name ``name.xpm`` or ``name`` in one of the " +"bitmap directories (see the :meth:`tix_addbitmapdir` method). By using :" +"meth:`tix_getbitmap`, you can avoid hard coding the pathnames of the bitmap " +"files in your application. When successful, it returns the complete pathname " +"of the bitmap file, prefixed with the character ``@``. The returned value " +"can be used to configure the ``bitmap`` option of the Tk and Tix widgets." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:545 +msgid "" +"Tix maintains a list of directories under which the :meth:`tix_getimage` " +"and :meth:`tix_getbitmap` methods will search for image files. The standard " +"bitmap directory is :file:`$TIX_LIBRARY/bitmaps`. The :meth:" +"`tix_addbitmapdir` method adds *directory* into this list. By using this " +"method, the image files of an applications can also be located using the :" +"meth:`tix_getimage` or :meth:`tix_getbitmap` method." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:555 +msgid "" +"Returns the file selection dialog that may be shared among different calls " +"from this application. This method will create a file selection dialog " +"widget when it is called the first time. This dialog will be returned by all " +"subsequent calls to :meth:`tix_filedialog`. An optional dlgclass parameter " +"can be passed as a string to specified what type of file selection dialog " +"widget is desired. Possible options are ``tix``, ``FileSelectDialog`` or " +"``tixExFileSelectDialog``." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:565 +msgid "" +"Locates an image file of the name :file:`name.xpm`, :file:`name.xbm` or :" +"file:`name.ppm` in one of the bitmap directories (see the :meth:" +"`tix_addbitmapdir` method above). If more than one file with the same name " +"(but different extensions) exist, then the image type is chosen according to " +"the depth of the X display: xbm images are chosen on monochrome displays and " +"color images are chosen on color displays. By using :meth:`tix_getimage`, " +"you can avoid hard coding the pathnames of the image files in your " +"application. When successful, this method returns the name of the newly " +"created image, which can be used to configure the ``image`` option of the Tk " +"and Tix widgets." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:578 +msgid "Gets the options maintained by the Tix scheme mechanism." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:583 +msgid "" +"Resets the scheme and fontset of the Tix application to *newScheme* and " +"*newFontSet*, respectively. This affects only those widgets created after " +"this call. Therefore, it is best to call the resetoptions method before the " +"creation of any widgets in a Tix application." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:588 +msgid "" +"The optional parameter *newScmPrio* can be given to reset the priority level " +"of the Tk options set by the Tix schemes." +msgstr "" + +#: ../Doc/library/tkinter.tix.rst:591 +msgid "" +"Because of the way Tk handles the X option database, after Tix has been has " +"imported and inited, it is not possible to reset the color schemes and font " +"sets using the :meth:`tix_config` method. Instead, the :meth:" +"`tix_resetoptions` method must be used." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:2 +msgid ":mod:`tkinter.ttk` --- Tk themed widgets" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:9 +msgid "**Source code:** :source:`Lib/tkinter/ttk.py`" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:15 +msgid "" +"The :mod:`tkinter.ttk` module provides access to the Tk themed widget set, " +"introduced in Tk 8.5. If Python has not been compiled against Tk 8.5, this " +"module can still be accessed if *Tile* has been installed. The former " +"method using Tk 8.5 provides additional benefits including anti-aliased font " +"rendering under X11 and window transparency (requiring a composition window " +"manager on X11)." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:22 +msgid "" +"The basic idea for :mod:`tkinter.ttk` is to separate, to the extent " +"possible, the code implementing a widget's behavior from the code " +"implementing its appearance." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:29 +msgid "`Tk Widget Styling Support `_" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:30 +msgid "A document introducing theming support for Tk" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:34 +msgid "Using Ttk" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:36 +msgid "To start using Ttk, import its module::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:40 +msgid "" +"To override the basic Tk widgets, the import should follow the Tk import::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:45 +msgid "" +"That code causes several :mod:`tkinter.ttk` widgets (:class:`Button`, :class:" +"`Checkbutton`, :class:`Entry`, :class:`Frame`, :class:`Label`, :class:" +"`LabelFrame`, :class:`Menubutton`, :class:`PanedWindow`, :class:" +"`Radiobutton`, :class:`Scale` and :class:`Scrollbar`) to automatically " +"replace the Tk widgets." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:51 +msgid "" +"This has the direct benefit of using the new widgets which gives a better " +"look and feel across platforms; however, the replacement widgets are not " +"completely compatible. The main difference is that widget options such as " +"\"fg\", \"bg\" and others related to widget styling are no longer present in " +"Ttk widgets. Instead, use the :class:`ttk.Style` class for improved " +"styling effects." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:62 +msgid "" +"`Converting existing applications to use Tile widgets `_" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:62 +msgid "" +"A monograph (using Tcl terminology) about differences typically encountered " +"when moving applications to use the new widgets." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:67 +msgid "Ttk Widgets" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:69 +msgid "" +"Ttk comes with 17 widgets, eleven of which already existed in tkinter: :" +"class:`Button`, :class:`Checkbutton`, :class:`Entry`, :class:`Frame`, :class:" +"`Label`, :class:`LabelFrame`, :class:`Menubutton`, :class:`PanedWindow`, :" +"class:`Radiobutton`, :class:`Scale` and :class:`Scrollbar`. The other six " +"are new: :class:`Combobox`, :class:`Notebook`, :class:`Progressbar`, :class:" +"`Separator`, :class:`Sizegrip` and :class:`Treeview`. And all them are " +"subclasses of :class:`Widget`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:77 +msgid "" +"Using the Ttk widgets gives the application an improved look and feel. As " +"discussed above, there are differences in how the styling is coded." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:80 +msgid "Tk code::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:86 +msgid "Ttk code::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:94 +msgid "" +"For more information about TtkStyling_, see the :class:`Style` class " +"documentation." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:98 +msgid "Widget" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:100 +msgid "" +":class:`ttk.Widget` defines standard options and methods supported by Tk " +"themed widgets and is not supposed to be directly instantiated." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:105 +msgid "Standard Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:107 +msgid "All the :mod:`ttk` Widgets accepts the following options:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:114 +msgid "" +"Specifies the window class. The class is used when querying the option " +"database for the window's other options, to determine the default bindtags " +"for the window, and to select the widget's default layout and style. This " +"option is read-only, and may only be specified when the window is created." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:121 +msgid "" +"Specifies the mouse cursor to be used for the widget. If set to the empty " +"string (the default), the cursor is inherited for the parent widget." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:125 +msgid "takefocus" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:125 +msgid "" +"Determines whether the window accepts the focus during keyboard traversal. " +"0, 1 or an empty string is returned. If 0 is returned, it means that the " +"window should be skipped entirely during keyboard traversal. If 1, it means " +"that the window should receive the input focus as long as it is viewable. " +"And an empty string means that the traversal scripts make the decision about " +"whether or not to focus on the window." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:134 +msgid "style" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:134 +msgid "May be used to specify a custom widget style." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:139 +msgid "Scrollable Widget Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:141 +msgid "" +"The following options are supported by widgets that are controlled by a " +"scrollbar." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:149 +msgid "xscrollcommand" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:149 +msgid "Used to communicate with horizontal scrollbars." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:151 +msgid "" +"When the view in the widget's window change, the widget will generate a Tcl " +"command based on the scrollcommand." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:154 +msgid "" +"Usually this option consists of the method :meth:`Scrollbar.set` of some " +"scrollbar. This will cause the scrollbar to be updated whenever the view in " +"the window changes." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:159 +msgid "yscrollcommand" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:159 +msgid "" +"Used to communicate with vertical scrollbars. For some more information, see " +"above." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:165 +msgid "Label Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:167 +msgid "" +"The following options are supported by labels, buttons and other button-like " +"widgets." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:175 ../Doc/library/tkinter.ttk.rst:442 +#: ../Doc/library/tkinter.ttk.rst:782 +msgid "text" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:175 +msgid "Specifies a text string to be displayed inside the widget." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:177 ../Doc/library/tkinter.ttk.rst:341 +msgid "textvariable" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:177 +msgid "" +"Specifies a name whose value will be used in place of the text option " +"resource." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:180 ../Doc/library/tkinter.ttk.rst:451 +msgid "underline" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:180 +msgid "" +"If set, specifies the index (0-based) of a character to underline in the " +"text string. The underline character is used for mnemonic activation." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:184 ../Doc/library/tkinter.ttk.rst:444 +#: ../Doc/library/tkinter.ttk.rst:784 ../Doc/library/tkinter.ttk.rst:816 +msgid "image" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:184 +msgid "" +"Specifies an image to display. This is a list of 1 or more elements. The " +"first element is the default image name. The rest of the list if a sequence " +"of statespec/value pairs as defined by :meth:`Style.map`, specifying " +"different images to use when the widget is in a particular state or a " +"combination of states. All images in the list should have the same size." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:192 ../Doc/library/tkinter.ttk.rst:447 +msgid "compound" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:192 +msgid "" +"Specifies how to display the image relative to the text, in the case both " +"text and images options are present. Valid values are:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:196 +msgid "text: display text only" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:197 +msgid "image: display image only" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:198 +msgid "" +"top, bottom, left, right: display image above, below, left of, or right of " +"the text, respectively." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:200 +msgid "none: the default. display the image if present, otherwise the text." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:203 +msgid "" +"If greater than zero, specifies how much space, in character widths, to " +"allocate for the text label, if less than zero, specifies a minimum width. " +"If zero or unspecified, the natural width of the text label is used." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:211 +msgid "Compatibility Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:218 +msgid "" +"May be set to \"normal\" or \"disabled\" to control the \"disabled\" state " +"bit. This is a write-only option: setting it changes the widget state, but " +"the :meth:`Widget.state` method does not affect this option." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:225 +msgid "Widget States" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:227 +msgid "The widget state is a bitmap of independent state flags." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:234 +msgid "active" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:234 +msgid "" +"The mouse cursor is over the widget and pressing a mouse button will cause " +"some action to occur" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:237 +msgid "disabled" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:237 +msgid "Widget is disabled under program control" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:239 +msgid "Widget has keyboard focus" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:241 +msgid "pressed" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:241 +msgid "Widget is being pressed" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:243 +msgid "selected" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:243 +msgid "" +"\"On\", \"true\", or \"current\" for things like Checkbuttons and " +"radiobuttons" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:246 ../Doc/library/tkinter.ttk.rst:812 +msgid "background" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:246 +msgid "" +"Windows and Mac have a notion of an \"active\" or foreground window. The " +"*background* state is set for widgets in a background window, and cleared " +"for those in the foreground window" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:251 +msgid "readonly" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:251 +msgid "Widget should not allow user modification" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:253 +msgid "alternate" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:253 +msgid "A widget-specific alternate display format" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:255 +msgid "invalid" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:255 +msgid "The widget's value is invalid" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:258 +msgid "" +"A state specification is a sequence of state names, optionally prefixed with " +"an exclamation point indicating that the bit is off." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:263 +msgid "ttk.Widget" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:265 +msgid "" +"Besides the methods described below, the :class:`ttk.Widget` supports the " +"methods :meth:`tkinter.Widget.cget` and :meth:`tkinter.Widget.configure`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:272 +msgid "" +"Returns the name of the element at position *x* *y*, or the empty string if " +"the point does not lie within any element." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:275 +msgid "*x* and *y* are pixel coordinates relative to the widget." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:280 +msgid "" +"Test the widget's state. If a callback is not specified, returns ``True`` if " +"the widget state matches *statespec* and ``False`` otherwise. If callback is " +"specified then it is called with args if widget state matches *statespec*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:288 +msgid "" +"Modify or inquire widget state. If *statespec* is specified, sets the widget " +"state according to it and return a new *statespec* indicating which flags " +"were changed. If *statespec* is not specified, returns the currently-enabled " +"state flags." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:293 +msgid "*statespec* will usually be a list or a tuple." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:297 +msgid "Combobox" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:299 +msgid "" +"The :class:`ttk.Combobox` widget combines a text field with a pop-down list " +"of values. This widget is a subclass of :class:`Entry`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:302 +msgid "" +"Besides the methods inherited from :class:`Widget`: :meth:`Widget.cget`, :" +"meth:`Widget.configure`, :meth:`Widget.identify`, :meth:`Widget.instate` " +"and :meth:`Widget.state`, and the following inherited from :class:`Entry`: :" +"meth:`Entry.bbox`, :meth:`Entry.delete`, :meth:`Entry.icursor`, :meth:`Entry." +"index`, :meth:`Entry.insert`, :meth:`Entry.selection`, :meth:`Entry.xview`, " +"it has some other methods, described at :class:`ttk.Combobox`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:314 ../Doc/library/tkinter.ttk.rst:395 +#: ../Doc/library/tkinter.ttk.rst:585 ../Doc/library/tkinter.ttk.rst:724 +msgid "This widget accepts the following specific options:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:321 +msgid "exportselection" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:321 +msgid "" +"Boolean value. If set, the widget selection is linked to the Window Manager " +"selection (which can be returned by invoking Misc.selection_get, for " +"example)." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:325 +msgid "" +"Specifies how the text is aligned within the widget. One of \"left\", " +"\"center\", or \"right\"." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:328 +msgid "Specifies the height of the pop-down listbox, in rows." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:330 +msgid "postcommand" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:330 +msgid "" +"A script (possibly registered with Misc.register) that is called immediately " +"before displaying the values. It may specify which values to display." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:334 +msgid "" +"One of \"normal\", \"readonly\", or \"disabled\". In the \"readonly\" state, " +"the value may not be edited directly, and the user can only selection of the " +"values from the dropdown list. In the \"normal\" state, the text field is " +"directly editable. In the \"disabled\" state, no interaction is possible." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:341 +msgid "" +"Specifies a name whose value is linked to the widget value. Whenever the " +"value associated with that name changes, the widget value is updated, and " +"vice versa. See :class:`tkinter.StringVar`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:346 ../Doc/library/tkinter.ttk.rst:786 +msgid "values" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:346 +msgid "Specifies the list of values to display in the drop-down listbox." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:349 +msgid "" +"Specifies an integer value indicating the desired width of the entry window, " +"in average-size characters of the widget's font." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:356 +msgid "Virtual events" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:358 +msgid "" +"The combobox widgets generates a **<>** virtual event when " +"the user selects an element from the list of values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:363 +msgid "ttk.Combobox" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:369 +msgid "" +"If *newindex* is specified, sets the combobox value to the element position " +"*newindex*. Otherwise, returns the index of the current value or -1 if the " +"current value is not in the values list." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:376 +msgid "Returns the current value of the combobox." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:381 +msgid "Sets the value of the combobox to *value*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:385 +msgid "Notebook" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:387 +msgid "" +"Ttk Notebook widget manages a collection of windows and displays a single " +"one at a time. Each child window is associated with a tab, which the user " +"may select to change the currently-displayed window." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:402 +msgid "" +"If present and greater than zero, specifies the desired height of the pane " +"area (not including internal padding or tabs). Otherwise, the maximum height " +"of all panes is used." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:406 ../Doc/library/tkinter.ttk.rst:438 +#: ../Doc/library/tkinter.ttk.rst:743 +msgid "padding" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:406 +msgid "" +"Specifies the amount of extra space to add around the outside of the " +"notebook. The padding is a list up to four length specifications left top " +"right bottom. If fewer than four elements are specified, bottom defaults to " +"top, right defaults to left, and top defaults to left." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:412 +msgid "" +"If present and greater than zero, specified the desired width of the pane " +"area (not including internal padding). Otherwise, the maximum width of all " +"panes is used." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:419 +msgid "Tab Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:421 +msgid "There are also specific options for tabs:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:428 +msgid "" +"Either \"normal\", \"disabled\" or \"hidden\". If \"disabled\", then the tab " +"is not selectable. If \"hidden\", then the tab is not shown." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:432 +msgid "sticky" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:432 +msgid "" +"Specifies how the child window is positioned within the pane area. Value is " +"a string containing zero or more of the characters \"n\", \"s\", \"e\" or \"w" +"\". Each letter refers to a side (north, south, east or west) that the child " +"window will stick to, as per the :meth:`grid` geometry manager." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:438 +msgid "" +"Specifies the amount of extra space to add between the notebook and this " +"pane. Syntax is the same as for the option padding used by this widget." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:442 +msgid "Specifies a text to be displayed in the tab." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:444 +msgid "" +"Specifies an image to display in the tab. See the option image described in :" +"class:`Widget`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:447 +msgid "" +"Specifies how to display the image relative to the text, in the case both " +"options text and image are present. See `Label Options`_ for legal values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:451 +msgid "" +"Specifies the index (0-based) of a character to underline in the text " +"string. The underlined character is used for mnemonic activation if :meth:" +"`Notebook.enable_traversal` is called." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:459 +msgid "Tab Identifiers" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:461 +msgid "" +"The tab_id present in several methods of :class:`ttk.Notebook` may take any " +"of the following forms:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:464 +msgid "An integer between zero and the number of tabs" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:465 +msgid "The name of a child window" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:466 +msgid "" +"A positional specification of the form \"@x,y\", which identifies the tab" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:467 +msgid "" +"The literal string \"current\", which identifies the currently-selected tab" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:468 +msgid "" +"The literal string \"end\", which returns the number of tabs (only valid " +"for :meth:`Notebook.index`)" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:473 ../Doc/library/tkinter.ttk.rst:846 +msgid "Virtual Events" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:475 +msgid "" +"This widget generates a **<>** virtual event after a new " +"tab is selected." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:480 +msgid "ttk.Notebook" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:486 +msgid "Adds a new tab to the notebook." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:488 +msgid "" +"If window is currently managed by the notebook but hidden, it is restored to " +"its previous position." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:491 ../Doc/library/tkinter.ttk.rst:529 +msgid "See `Tab Options`_ for the list of available options." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:496 +msgid "" +"Removes the tab specified by *tab_id*, unmaps and unmanages the associated " +"window." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:502 +msgid "Hides the tab specified by *tab_id*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:504 +msgid "" +"The tab will not be displayed, but the associated window remains managed by " +"the notebook and its configuration remembered. Hidden tabs may be restored " +"with the :meth:`add` command." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:511 +msgid "" +"Returns the name of the tab element at position *x*, *y*, or the empty " +"string if none." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:517 +msgid "" +"Returns the numeric index of the tab specified by *tab_id*, or the total " +"number of tabs if *tab_id* is the string \"end\"." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:523 +msgid "Inserts a pane at the specified position." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:525 +msgid "" +"*pos* is either the string \"end\", an integer index, or the name of a " +"managed child. If *child* is already managed by the notebook, moves it to " +"the specified position." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:534 +msgid "Selects the specified *tab_id*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:536 +msgid "" +"The associated child window will be displayed, and the previously-selected " +"window (if different) is unmapped. If *tab_id* is omitted, returns the " +"widget name of the currently selected pane." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:543 +msgid "Query or modify the options of the specific *tab_id*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:545 +msgid "" +"If *kw* is not given, returns a dictionary of the tab option values. If " +"*option* is specified, returns the value of that *option*. Otherwise, sets " +"the options to the corresponding values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:552 +msgid "Returns a list of windows managed by the notebook." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:557 +msgid "" +"Enable keyboard traversal for a toplevel window containing this notebook." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:559 +msgid "" +"This will extend the bindings for the toplevel window containing the " +"notebook as follows:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:562 +msgid "" +":kbd:`Control-Tab`: selects the tab following the currently selected one." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:563 +msgid "" +":kbd:`Shift-Control-Tab`: selects the tab preceding the currently selected " +"one." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:564 +msgid "" +":kbd:`Alt-K`: where *K* is the mnemonic (underlined) character of any tab, " +"will select that tab." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:567 +msgid "" +"Multiple notebooks in a single toplevel may be enabled for traversal, " +"including nested notebooks. However, notebook traversal only works properly " +"if all panes have the notebook they are in as master." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:573 +msgid "Progressbar" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:575 +msgid "" +"The :class:`ttk.Progressbar` widget shows the status of a long-running " +"operation. It can operate in two modes: 1) the determinate mode which shows " +"the amount completed relative to the total amount of work to be done and 2) " +"the indeterminate mode which provides an animated display to let the user " +"know that work is progressing." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:592 ../Doc/library/tkinter.ttk.rst:663 +msgid "orient" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:592 +msgid "" +"One of \"horizontal\" or \"vertical\". Specifies the orientation of the " +"progress bar." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:595 +msgid "length" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:595 +msgid "" +"Specifies the length of the long axis of the progress bar (width if " +"horizontal, height if vertical)." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:598 +msgid "One of \"determinate\" or \"indeterminate\"." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:600 +msgid "maximum" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:600 +msgid "A number specifying the maximum value. Defaults to 100." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:602 +msgid "value" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:602 +msgid "" +"The current value of the progress bar. In \"determinate\" mode, this " +"represents the amount of work completed. In \"indeterminate\" mode, it is " +"interpreted as modulo *maximum*; that is, the progress bar completes one " +"\"cycle\" when its value increases by *maximum*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:608 +msgid "variable" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:608 +msgid "" +"A name which is linked to the option value. If specified, the value of the " +"progress bar is automatically set to the value of this name whenever the " +"latter is modified." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:612 +msgid "phase" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:612 +msgid "" +"Read-only option. The widget periodically increments the value of this " +"option whenever its value is greater than 0 and, in determinate mode, less " +"than maximum. This option may be used by the current theme to provide " +"additional animation effects." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:620 +msgid "ttk.Progressbar" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:626 +msgid "" +"Begin autoincrement mode: schedules a recurring timer event that calls :meth:" +"`Progressbar.step` every *interval* milliseconds. If omitted, *interval* " +"defaults to 50 milliseconds." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:633 +msgid "Increments the progress bar's value by *amount*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:635 +msgid "*amount* defaults to 1.0 if omitted." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:640 +msgid "" +"Stop autoincrement mode: cancels any recurring timer event initiated by :" +"meth:`Progressbar.start` for this progress bar." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:645 +msgid "Separator" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:647 +msgid "" +"The :class:`ttk.Separator` widget displays a horizontal or vertical " +"separator bar." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:650 +msgid "" +"It has no other methods besides the ones inherited from :class:`ttk.Widget`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:656 +msgid "This widget accepts the following specific option:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:663 +msgid "" +"One of \"horizontal\" or \"vertical\". Specifies the orientation of the " +"separator." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:669 +msgid "Sizegrip" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:671 +msgid "" +"The :class:`ttk.Sizegrip` widget (also known as a grow box) allows the user " +"to resize the containing toplevel window by pressing and dragging the grip." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:674 +msgid "" +"This widget has neither specific options nor specific methods, besides the " +"ones inherited from :class:`ttk.Widget`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:679 +msgid "Platform-specific notes" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:681 +msgid "" +"On MacOS X, toplevel windows automatically include a built-in size grip by " +"default. Adding a :class:`Sizegrip` is harmless, since the built-in grip " +"will just mask the widget." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:687 +msgid "Bugs" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:689 +msgid "" +"If the containing toplevel's position was specified relative to the right or " +"bottom of the screen (e.g. ....), the :class:`Sizegrip` widget will not " +"resize the window." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:692 +msgid "This widget supports only \"southeast\" resizing." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:696 +msgid "Treeview" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:698 +msgid "" +"The :class:`ttk.Treeview` widget displays a hierarchical collection of " +"items. Each item has a textual label, an optional image, and an optional " +"list of data values. The data values are displayed in successive columns " +"after the tree label." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:703 +msgid "" +"The order in which data values are displayed may be controlled by setting " +"the widget option ``displaycolumns``. The tree widget can also display " +"column headings. Columns may be accessed by number or symbolic names listed " +"in the widget option columns. See `Column Identifiers`_." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:708 +msgid "" +"Each item is identified by a unique name. The widget will generate item IDs " +"if they are not supplied by the caller. There is a distinguished root item, " +"named ``{}``. The root item itself is not displayed; its children appear at " +"the top level of the hierarchy." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:713 +msgid "" +"Each item also has a list of tags, which can be used to associate event " +"bindings with individual items and control the appearance of the item." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:716 +msgid "" +"The Treeview widget supports horizontal and vertical scrolling, according to " +"the options described in `Scrollable Widget Options`_ and the methods :meth:" +"`Treeview.xview` and :meth:`Treeview.yview`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:731 +msgid "columns" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:731 +msgid "" +"A list of column identifiers, specifying the number of columns and their " +"names." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:734 +msgid "displaycolumns" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:734 +msgid "" +"A list of column identifiers (either symbolic or integer indices) specifying " +"which data columns are displayed and the order in which they appear, or the " +"string \"#all\"." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:739 +msgid "" +"Specifies the number of rows which should be visible. Note: the requested " +"width is determined from the sum of the column widths." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:743 +msgid "" +"Specifies the internal padding for the widget. The padding is a list of up " +"to four length specifications." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:746 +msgid "selectmode" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:746 +msgid "" +"Controls how the built-in class bindings manage the selection. One of " +"\"extended\", \"browse\" or \"none\". If set to \"extended\" (the default), " +"multiple items may be selected. If \"browse\", only a single item will be " +"selected at a time. If \"none\", the selection will not be changed." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:753 +msgid "" +"Note that the application code and tag bindings can set the selection " +"however they wish, regardless of the value of this option." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:757 +msgid "show" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:757 +msgid "" +"A list containing zero or more of the following values, specifying which " +"elements of the tree to display." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:760 +msgid "tree: display tree labels in column #0." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:761 +msgid "headings: display the heading row." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:763 +msgid "The default is \"tree headings\", i.e., show all elements." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:766 +msgid "" +"**Note**: Column #0 always refers to the tree column, even if show=\"tree\" " +"is not specified." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:772 +msgid "Item Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:774 +msgid "" +"The following item options may be specified for items in the insert and item " +"widget commands." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:782 +msgid "The textual label to display for the item." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:784 +msgid "A Tk Image, displayed to the left of the label." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:786 +msgid "The list of values associated with the item." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:788 +msgid "" +"Each item should have the same number of values as the widget option " +"columns. If there are fewer values than columns, the remaining values are " +"assumed empty. If there are more values than columns, the extra values are " +"ignored." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:793 +msgid "open" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:793 +msgid "" +"True/False value indicating whether the item's children should be displayed " +"or hidden." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:796 +msgid "tags" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:796 +msgid "A list of tags associated with this item." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:801 +msgid "Tag Options" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:803 +msgid "The following options may be specified on tags:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:810 +msgid "foreground" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:810 +msgid "Specifies the text foreground color." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:812 +msgid "Specifies the cell or item background color." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:814 +msgid "Specifies the font to use when drawing text." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:816 +msgid "Specifies the item image, in case the item's image option is empty." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:822 +msgid "Column Identifiers" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:824 +msgid "Column identifiers take any of the following forms:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:826 +msgid "A symbolic name from the list of columns option." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:827 +msgid "An integer n, specifying the nth data column." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:828 +msgid "" +"A string of the form #n, where n is an integer, specifying the nth display " +"column." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:833 +msgid "" +"Item's option values may be displayed in a different order than the order in " +"which they are stored." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:835 +msgid "" +"Column #0 always refers to the tree column, even if show=\"tree\" is not " +"specified." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:838 +msgid "" +"A data column number is an index into an item's option values list; a " +"display column number is the column number in the tree where the values are " +"displayed. Tree labels are displayed in column #0. If option displaycolumns " +"is not set, then data column n is displayed in column #n+1. Again, **column " +"#0 always refers to the tree column**." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:848 +msgid "The Treeview widget generates the following virtual events." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:855 +msgid "<>" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:855 +msgid "Generated whenever the selection changes." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:857 +msgid "<>" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:857 +msgid "Generated just before settings the focus item to open=True." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:860 +msgid "<>" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:860 +msgid "Generated just after setting the focus item to open=False." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:864 +msgid "" +"The :meth:`Treeview.focus` and :meth:`Treeview.selection` methods can be " +"used to determine the affected item or items." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:869 +msgid "ttk.Treeview" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:875 +msgid "" +"Returns the bounding box (relative to the treeview widget's window) of the " +"specified *item* in the form (x, y, width, height)." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:878 +msgid "" +"If *column* is specified, returns the bounding box of that cell. If the " +"*item* is not visible (i.e., if it is a descendant of a closed item or is " +"scrolled offscreen), returns an empty string." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:885 +msgid "Returns the list of children belonging to *item*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:887 +msgid "If *item* is not specified, returns root children." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:892 +msgid "Replaces *item*'s child with *newchildren*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:894 +msgid "" +"Children present in *item* that are not present in *newchildren* are " +"detached from the tree. No items in *newchildren* may be an ancestor of " +"*item*. Note that not specifying *newchildren* results in detaching *item*'s " +"children." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:902 +msgid "Query or modify the options for the specified *column*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:904 +msgid "" +"If *kw* is not given, returns a dict of the column option values. If " +"*option* is specified then the value for that *option* is returned. " +"Otherwise, sets the options to the corresponding values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:908 ../Doc/library/tkinter.ttk.rst:963 +msgid "The valid options/values are:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:910 +msgid "id" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:911 +msgid "Returns the column name. This is a read-only option." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:913 +msgid "anchor: One of the standard Tk anchor values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:913 +msgid "" +"Specifies how the text in this column should be aligned with respect to the " +"cell." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:917 +msgid "minwidth: width" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:916 +msgid "" +"The minimum width of the column in pixels. The treeview widget will not make " +"the column any smaller than specified by this option when the widget is " +"resized or the user drags a column." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:920 +msgid "stretch: True/False" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:920 +msgid "" +"Specifies whether the column's width should be adjusted when the widget is " +"resized." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:923 +msgid "width: width" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:923 +msgid "The width of the column in pixels." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:925 +msgid "To configure the tree column, call this with column = \"#0\"" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:929 +msgid "Delete all specified *items* and all their descendants." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:931 +msgid "The root item may not be deleted." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:936 +msgid "Unlinks all of the specified *items* from the tree." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:938 +msgid "" +"The items and all of their descendants are still present, and may be " +"reinserted at another point in the tree, but will not be displayed." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:941 +msgid "The root item may not be detached." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:946 +msgid "Returns ``True`` if the specified *item* is present in the tree." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:951 +msgid "" +"If *item* is specified, sets the focus item to *item*. Otherwise, returns " +"the current focus item, or '' if there is none." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:957 +msgid "Query or modify the heading options for the specified *column*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:959 +msgid "" +"If *kw* is not given, returns a dict of the heading option values. If " +"*option* is specified then the value for that *option* is returned. " +"Otherwise, sets the options to the corresponding values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:965 +msgid "text: text" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:966 +msgid "The text to display in the column heading." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:967 +msgid "image: imageName" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:968 +msgid "Specifies an image to display to the right of the column heading." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:970 +msgid "anchor: anchor" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:970 +msgid "" +"Specifies how the heading text should be aligned. One of the standard Tk " +"anchor values." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:973 +msgid "command: callback" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:973 +msgid "A callback to be invoked when the heading label is pressed." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:975 +msgid "To configure the tree column heading, call this with column = \"#0\"." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:980 +msgid "" +"Returns a description of the specified *component* under the point given by " +"*x* and *y*, or the empty string if no such *component* is present at that " +"position." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:987 +msgid "Returns the item ID of the item at position *y*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:992 +msgid "Returns the data column identifier of the cell at position *x*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:994 +msgid "The tree column has ID #0." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:999 +msgid "Returns one of:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1002 +msgid "meaning" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1004 +msgid "heading" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1004 +msgid "Tree heading area." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1006 +msgid "separator" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1006 +msgid "Space between two columns headings." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1008 ../Doc/library/turtle.rst:2362 +msgid "tree" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1008 +msgid "The tree area." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1010 +msgid "cell" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1010 +msgid "A data cell." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1013 ../Doc/library/tkinter.ttk.rst:1020 +msgid "Availability: Tk 8.6." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1018 +msgid "Returns the element at position *x*, *y*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1025 +msgid "" +"Returns the integer index of *item* within its parent's list of children." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1030 +msgid "" +"Creates a new item and returns the item identifier of the newly created item." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1033 +msgid "" +"*parent* is the item ID of the parent item, or the empty string to create a " +"new top-level item. *index* is an integer, or the value \"end\", specifying " +"where in the list of parent's children to insert the new item. If *index* is " +"less than or equal to zero, the new node is inserted at the beginning; if " +"*index* is greater than or equal to the current number of children, it is " +"inserted at the end. If *iid* is specified, it is used as the item " +"identifier; *iid* must not already exist in the tree. Otherwise, a new " +"unique identifier is generated." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1042 +msgid "See `Item Options`_ for the list of available points." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1047 +msgid "Query or modify the options for the specified *item*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1049 +msgid "" +"If no options are given, a dict with options/values for the item is " +"returned. If *option* is specified then the value for that option is " +"returned. Otherwise, sets the options to the corresponding values as given " +"by *kw*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1057 +msgid "Moves *item* to position *index* in *parent*'s list of children." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1059 +msgid "" +"It is illegal to move an item under one of its descendants. If *index* is " +"less than or equal to zero, *item* is moved to the beginning; if greater " +"than or equal to the number of children, it is moved to the end. If *item* " +"was detached it is reattached." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1067 +msgid "" +"Returns the identifier of *item*'s next sibling, or '' if *item* is the last " +"child of its parent." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1073 +msgid "" +"Returns the ID of the parent of *item*, or '' if *item* is at the top level " +"of the hierarchy." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1079 +msgid "" +"Returns the identifier of *item*'s previous sibling, or '' if *item* is the " +"first child of its parent." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1085 +msgid "An alias for :meth:`Treeview.move`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1090 +msgid "Ensure that *item* is visible." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1092 +msgid "" +"Sets all of *item*'s ancestors open option to ``True``, and scrolls the " +"widget if necessary so that *item* is within the visible portion of the tree." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1099 +msgid "" +"If *selop* is not specified, returns selected items. Otherwise, it will act " +"according to the following selection methods." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1105 +msgid "*items* becomes the new selection." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1110 +msgid "Add *items* to the selection." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1115 +msgid "Remove *items* from the selection." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1120 +msgid "Toggle the selection state of each item in *items*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1125 +msgid "" +"With one argument, returns a dictionary of column/value pairs for the " +"specified *item*. With two arguments, returns the current value of the " +"specified *column*. With three arguments, sets the value of given *column* " +"in given *item* to the specified *value*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1133 +msgid "" +"Bind a callback for the given event *sequence* to the tag *tagname*. When an " +"event is delivered to an item, the callbacks for each of the item's tags " +"option are called." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1140 +msgid "Query or modify the options for the specified *tagname*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1142 +msgid "" +"If *kw* is not given, returns a dict of the option settings for *tagname*. " +"If *option* is specified, returns the value for that *option* for the " +"specified *tagname*. Otherwise, sets the options to the corresponding values " +"for the given *tagname*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1150 +msgid "" +"If *item* is specified, returns 1 or 0 depending on whether the specified " +"*item* has the given *tagname*. Otherwise, returns a list of all items that " +"have the specified tag." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1154 +msgid "Availability: Tk 8.6" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1159 +msgid "Query or modify horizontal position of the treeview." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1164 +msgid "Query or modify vertical position of the treeview." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1170 +msgid "Ttk Styling" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1172 +msgid "" +"Each widget in :mod:`ttk` is assigned a style, which specifies the set of " +"elements making up the widget and how they are arranged, along with dynamic " +"and default settings for element options. By default the style name is the " +"same as the widget's class name, but it may be overridden by the widget's " +"style option. If you don't know the class name of a widget, use the method :" +"meth:`Misc.winfo_class` (somewidget.winfo_class())." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1181 +msgid "" +"`Tcl'2004 conference presentation `_" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1182 +msgid "This document explains how the theme engine works" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1187 +msgid "This class is used to manipulate the style database." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1192 +msgid "Query or set the default value of the specified option(s) in *style*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1194 +msgid "" +"Each key in *kw* is an option and each value is a string identifying the " +"value for that option." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1197 +msgid "" +"For example, to change every default button to be a flat button with some " +"padding and a different background color::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1216 +msgid "Query or sets dynamic values of the specified option(s) in *style*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1218 +msgid "" +"Each key in *kw* is an option and each value should be a list or a tuple " +"(usually) containing statespecs grouped in tuples, lists, or some other " +"preference. A statespec is a compound of one or more states and then a value." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1223 +msgid "An example may make it more understandable::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1241 +msgid "" +"Note that the order of the (states, value) sequences for an option does " +"matter, if the order is changed to ``[('active', 'blue'), ('pressed', " +"'red')]`` in the foreground option, for example, the result would be a blue " +"foreground when the widget were in active or pressed states." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1249 +msgid "Returns the value specified for *option* in *style*." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1251 +msgid "" +"If *state* is specified, it is expected to be a sequence of one or more " +"states. If the *default* argument is set, it is used as a fallback value in " +"case no specification for option is found." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1255 +msgid "To check what font a Button uses by default::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1264 +msgid "" +"Define the widget layout for given *style*. If *layoutspec* is omitted, " +"return the layout specification for given style." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1267 +msgid "" +"*layoutspec*, if specified, is expected to be a list or some other sequence " +"type (excluding strings), where each item should be a tuple and the first " +"item is the layout name and the second item should have the format described " +"in `Layouts`_." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1272 +msgid "" +"To understand the format, see the following example (it is not intended to " +"do anything useful)::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1299 +msgid "" +"Create a new element in the current theme, of the given *etype* which is " +"expected to be either \"image\", \"from\" or \"vsapi\". The latter is only " +"available in Tk 8.6a for Windows XP and Vista and is not described here." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1303 +msgid "" +"If \"image\" is used, *args* should contain the default image name followed " +"by statespec/value pairs (this is the imagespec), and *kw* may have the " +"following options:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1309 +msgid "border=padding" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1308 +msgid "" +"padding is a list of up to four integers, specifying the left, top, right, " +"and bottom borders, respectively." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1313 +msgid "height=height" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1312 +msgid "" +"Specifies a minimum height for the element. If less than zero, the base " +"image's height is used as a default." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1317 +msgid "padding=padding" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1316 +msgid "" +"Specifies the element's interior padding. Defaults to border's value if not " +"specified." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1321 +msgid "sticky=spec" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1320 +msgid "" +"Specifies how the image is placed within the final parcel. spec contains " +"zero or more characters \"n\", \"s\", \"w\", or \"e\"." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1325 +msgid "width=width" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1324 +msgid "" +"Specifies a minimum width for the element. If less than zero, the base " +"image's width is used as a default." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1327 +msgid "" +"If \"from\" is used as the value of *etype*, :meth:`element_create` will " +"clone an existing element. *args* is expected to contain a themename, from " +"which the element will be cloned, and optionally an element to clone from. " +"If this element to clone from is not specified, an empty element will be " +"used. *kw* is discarded." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1337 +msgid "Returns the list of elements defined in the current theme." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1342 +msgid "Returns the list of *elementname*'s options." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1347 +msgid "Create a new theme." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1349 +msgid "" +"It is an error if *themename* already exists. If *parent* is specified, the " +"new theme will inherit styles, elements and layouts from the parent theme. " +"If *settings* are present they are expected to have the same syntax used " +"for :meth:`theme_settings`." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1357 +msgid "" +"Temporarily sets the current theme to *themename*, apply specified " +"*settings* and then restore the previous theme." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1360 +msgid "" +"Each key in *settings* is a style and each value may contain the keys " +"'configure', 'map', 'layout' and 'element create' and they are expected to " +"have the same format as specified by the methods :meth:`Style.configure`, :" +"meth:`Style.map`, :meth:`Style.layout` and :meth:`Style.element_create` " +"respectively." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1366 +msgid "As an example, let's change the Combobox for the default theme a bit::" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1394 +msgid "Returns a list of all known themes." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1399 +msgid "" +"If *themename* is not given, returns the theme in use. Otherwise, sets the " +"current theme to *themename*, refreshes all widgets and emits a " +"<> event." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1405 +msgid "Layouts" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1407 +msgid "" +"A layout can be just None, if it takes no options, or a dict of options " +"specifying how to arrange the element. The layout mechanism uses a " +"simplified version of the pack geometry manager: given an initial cavity, " +"each element is allocated a parcel. Valid options/values are:" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1416 +msgid "side: whichside" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1414 +msgid "" +"Specifies which side of the cavity to place the element; one of top, right, " +"bottom or left. If omitted, the element occupies the entire cavity." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1419 +msgid "sticky: nswe" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1419 +msgid "Specifies where the element is placed inside its allocated parcel." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1424 +msgid "unit: 0 or 1" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1422 +msgid "" +"If set to 1, causes the element and all of its descendants to be treated as " +"a single element for the purposes of :meth:`Widget.identify` et al. It's " +"used for things like scrollbar thumbs with grips." +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1429 +msgid "children: [sublayout... ]" +msgstr "" + +#: ../Doc/library/tkinter.ttk.rst:1427 +msgid "" +"Specifies a list of elements to place inside the element. Each element is a " +"tuple (or other sequence type) where the first item is the layout name, and " +"the other is a `Layout`_." +msgstr "" + +#: ../Doc/library/token.rst:2 +msgid ":mod:`token` --- Constants used with Python parse trees" +msgstr "" + +#: ../Doc/library/token.rst:9 +msgid "**Source code:** :source:`Lib/token.py`" +msgstr "" + +#: ../Doc/library/token.rst:13 +msgid "" +"This module provides constants which represent the numeric values of leaf " +"nodes of the parse tree (terminal tokens). Refer to the file :file:`Grammar/" +"Grammar` in the Python distribution for the definitions of the names in the " +"context of the language grammar. The specific numeric values which the " +"names map to may change between Python versions." +msgstr "" + +#: ../Doc/library/token.rst:19 +msgid "" +"The module also provides a mapping from numeric codes to names and some " +"functions. The functions mirror definitions in the Python C header files." +msgstr "" + +#: ../Doc/library/token.rst:32 +msgid "Return true for terminal token values." +msgstr "" + +#: ../Doc/library/token.rst:37 +msgid "Return true for non-terminal token values." +msgstr "" + +#: ../Doc/library/token.rst:42 +msgid "Return true if *x* is the marker indicating the end of input." +msgstr "" + +#: ../Doc/library/token.rst:45 +msgid "The token constants are:" +msgstr "" + +#: ../Doc/library/token.rst:107 +msgid "" +"Added :data:`AWAIT` and :data:`ASYNC` tokens. Starting with Python 3.7, " +"\"async\" and \"await\" will be tokenized as :data:`NAME` tokens, and :data:" +"`AWAIT` and :data:`ASYNC` will be removed." +msgstr "" + +#: ../Doc/library/tokenize.rst:2 +msgid ":mod:`tokenize` --- Tokenizer for Python source" +msgstr "" + +#: ../Doc/library/tokenize.rst:10 +msgid "**Source code:** :source:`Lib/tokenize.py`" +msgstr "" + +#: ../Doc/library/tokenize.rst:14 +msgid "" +"The :mod:`tokenize` module provides a lexical scanner for Python source " +"code, implemented in Python. The scanner in this module returns comments as " +"tokens as well, making it useful for implementing \"pretty-printers,\" " +"including colorizers for on-screen displays." +msgstr "" + +#: ../Doc/library/tokenize.rst:19 +msgid "" +"To simplify token stream handling, all :ref:`operators` and :ref:" +"`delimiters` tokens are returned using the generic :data:`token.OP` token " +"type. The exact type can be determined by checking the ``exact_type`` " +"property on the :term:`named tuple` returned from :func:`tokenize.tokenize`." +msgstr "" + +#: ../Doc/library/tokenize.rst:25 +msgid "Tokenizing Input" +msgstr "" + +#: ../Doc/library/tokenize.rst:27 +msgid "The primary entry point is a :term:`generator`:" +msgstr "" + +#: ../Doc/library/tokenize.rst:31 +msgid "" +"The :func:`.tokenize` generator requires one argument, *readline*, which " +"must be a callable object which provides the same interface as the :meth:`io." +"IOBase.readline` method of file objects. Each call to the function should " +"return one line of input as bytes." +msgstr "" + +#: ../Doc/library/tokenize.rst:36 +msgid "" +"The generator produces 5-tuples with these members: the token type; the " +"token string; a 2-tuple ``(srow, scol)`` of ints specifying the row and " +"column where the token begins in the source; a 2-tuple ``(erow, ecol)`` of " +"ints specifying the row and column where the token ends in the source; and " +"the line on which the token was found. The line passed (the last tuple item) " +"is the *logical* line; continuation lines are included. The 5 tuple is " +"returned as a :term:`named tuple` with the field names: ``type string start " +"end line``." +msgstr "" + +#: ../Doc/library/tokenize.rst:45 +msgid "" +"The returned :term:`named tuple` has an additional property named " +"``exact_type`` that contains the exact operator type for :data:`token.OP` " +"tokens. For all other token types ``exact_type`` equals the named tuple " +"``type`` field." +msgstr "" + +#: ../Doc/library/tokenize.rst:50 +msgid "Added support for named tuples." +msgstr "" + +#: ../Doc/library/tokenize.rst:53 +msgid "Added support for ``exact_type``." +msgstr "" + +#: ../Doc/library/tokenize.rst:56 +msgid "" +":func:`.tokenize` determines the source encoding of the file by looking for " +"a UTF-8 BOM or encoding cookie, according to :pep:`263`." +msgstr "" + +#: ../Doc/library/tokenize.rst:60 +msgid "" +"All constants from the :mod:`token` module are also exported from :mod:" +"`tokenize`, as are three additional token type values:" +msgstr "" + +#: ../Doc/library/tokenize.rst:65 +msgid "Token value used to indicate a comment." +msgstr "" + +#: ../Doc/library/tokenize.rst:70 +msgid "" +"Token value used to indicate a non-terminating newline. The NEWLINE token " +"indicates the end of a logical line of Python code; NL tokens are generated " +"when a logical line of code is continued over multiple physical lines." +msgstr "" + +#: ../Doc/library/tokenize.rst:77 +msgid "" +"Token value that indicates the encoding used to decode the source bytes into " +"text. The first token returned by :func:`.tokenize` will always be an " +"ENCODING token." +msgstr "" + +#: ../Doc/library/tokenize.rst:82 +msgid "" +"Another function is provided to reverse the tokenization process. This is " +"useful for creating tools that tokenize a script, modify the token stream, " +"and write back the modified script." +msgstr "" + +#: ../Doc/library/tokenize.rst:89 +msgid "" +"Converts tokens back into Python source code. The *iterable* must return " +"sequences with at least two elements, the token type and the token string. " +"Any additional sequence elements are ignored." +msgstr "" + +#: ../Doc/library/tokenize.rst:93 +msgid "" +"The reconstructed script is returned as a single string. The result is " +"guaranteed to tokenize back to match the input so that the conversion is " +"lossless and round-trips are assured. The guarantee applies only to the " +"token type and token string as the spacing between tokens (column positions) " +"may change." +msgstr "" + +#: ../Doc/library/tokenize.rst:99 +msgid "" +"It returns bytes, encoded using the ENCODING token, which is the first token " +"sequence output by :func:`.tokenize`." +msgstr "" + +#: ../Doc/library/tokenize.rst:103 +msgid "" +":func:`.tokenize` needs to detect the encoding of source files it tokenizes. " +"The function it uses to do this is available:" +msgstr "" + +#: ../Doc/library/tokenize.rst:108 +msgid "" +"The :func:`detect_encoding` function is used to detect the encoding that " +"should be used to decode a Python source file. It requires one argument, " +"readline, in the same way as the :func:`.tokenize` generator." +msgstr "" + +#: ../Doc/library/tokenize.rst:112 +msgid "" +"It will call readline a maximum of twice, and return the encoding used (as a " +"string) and a list of any lines (not decoded from bytes) it has read in." +msgstr "" + +#: ../Doc/library/tokenize.rst:116 +msgid "" +"It detects the encoding from the presence of a UTF-8 BOM or an encoding " +"cookie as specified in :pep:`263`. If both a BOM and a cookie are present, " +"but disagree, a SyntaxError will be raised. Note that if the BOM is found, " +"``'utf-8-sig'`` will be returned as an encoding." +msgstr "" + +#: ../Doc/library/tokenize.rst:121 +msgid "" +"If no encoding is specified, then the default of ``'utf-8'`` will be " +"returned." +msgstr "" + +#: ../Doc/library/tokenize.rst:124 +msgid "" +"Use :func:`.open` to open Python source files: it uses :func:" +"`detect_encoding` to detect the file encoding." +msgstr "" + +#: ../Doc/library/tokenize.rst:130 +msgid "" +"Open a file in read only mode using the encoding detected by :func:" +"`detect_encoding`." +msgstr "" + +#: ../Doc/library/tokenize.rst:137 +msgid "" +"Raised when either a docstring or expression that may be split over several " +"lines is not completed anywhere in the file, for example::" +msgstr "" + +#: ../Doc/library/tokenize.rst:149 +msgid "" +"Note that unclosed single-quoted strings do not cause an error to be raised. " +"They are tokenized as ``ERRORTOKEN``, followed by the tokenization of their " +"contents." +msgstr "" + +#: ../Doc/library/tokenize.rst:157 ../Doc/library/trace.rst:19 +msgid "Command-Line Usage" +msgstr "" + +#: ../Doc/library/tokenize.rst:161 +msgid "" +"The :mod:`tokenize` module can be executed as a script from the command " +"line. It is as simple as:" +msgstr "" + +#: ../Doc/library/tokenize.rst:168 +msgid "The following options are accepted:" +msgstr "" + +#: ../Doc/library/tokenize.rst:174 +msgid "show this help message and exit" +msgstr "" + +#: ../Doc/library/tokenize.rst:178 +msgid "display token names using the exact type" +msgstr "" + +#: ../Doc/library/tokenize.rst:180 +msgid "" +"If :file:`filename.py` is specified its contents are tokenized to stdout. " +"Otherwise, tokenization is performed on stdin." +msgstr "" + +#: ../Doc/library/tokenize.rst:186 +msgid "" +"Example of a script rewriter that transforms float literals into Decimal " +"objects::" +msgstr "" + +#: ../Doc/library/tokenize.rst:228 +msgid "Example of tokenizing from the command line. The script::" +msgstr "" + +#: ../Doc/library/tokenize.rst:235 +msgid "" +"will be tokenized to the following output where the first column is the " +"range of the line/column coordinates where the token is found, the second " +"column is the name of the token, and the final column is the value of the " +"token (if any)" +msgstr "" + +#: ../Doc/library/tokenize.rst:263 +msgid "The exact token type names can be displayed using the ``-e`` option:" +msgstr "" + +#: ../Doc/library/trace.rst:2 +msgid ":mod:`trace` --- Trace or track Python statement execution" +msgstr "" + +#: ../Doc/library/trace.rst:7 +msgid "**Source code:** :source:`Lib/trace.py`" +msgstr "" + +#: ../Doc/library/trace.rst:11 +msgid "" +"The :mod:`trace` module allows you to trace program execution, generate " +"annotated statement coverage listings, print caller/callee relationships and " +"list functions executed during a program run. It can be used in another " +"program or from the command line." +msgstr "" + +#: ../Doc/library/trace.rst:21 +msgid "" +"The :mod:`trace` module can be invoked from the command line. It can be as " +"simple as ::" +msgstr "" + +#: ../Doc/library/trace.rst:26 +msgid "" +"The above will execute :file:`somefile.py` and generate annotated listings " +"of all Python modules imported during the execution into the current " +"directory." +msgstr "" + +#: ../Doc/library/trace.rst:33 +msgid "Display usage and exit." +msgstr "" + +#: ../Doc/library/trace.rst:37 +msgid "Display the version of the module and exit." +msgstr "" + +#: ../Doc/library/trace.rst:40 +msgid "Main options" +msgstr "" + +#: ../Doc/library/trace.rst:42 +msgid "" +"At least one of the following options must be specified when invoking :mod:" +"`trace`. The :option:`--listfuncs <-l>` option is mutually exclusive with " +"the :option:`--trace <-t>` and :option:`--count <-c>` options. When :option:" +"`--listfuncs <-l>` is provided, neither :option:`--count <-c>` nor :option:" +"`--trace <-t>` are accepted, and vice versa." +msgstr "" + +#: ../Doc/library/trace.rst:52 +msgid "" +"Produce a set of annotated listing files upon program completion that shows " +"how many times each statement was executed. See also :option:`--coverdir <-" +"C>`, :option:`--file <-f>` and :option:`--no-report <-R>` below." +msgstr "" + +#: ../Doc/library/trace.rst:59 +msgid "Display lines as they are executed." +msgstr "" + +#: ../Doc/library/trace.rst:63 +msgid "Display the functions executed by running the program." +msgstr "" + +#: ../Doc/library/trace.rst:67 +msgid "" +"Produce an annotated list from an earlier program run that used the :option:" +"`--count <-c>` and :option:`--file <-f>` option. This does not execute any " +"code." +msgstr "" + +#: ../Doc/library/trace.rst:73 +msgid "Display the calling relationships exposed by running the program." +msgstr "" + +#: ../Doc/library/trace.rst:76 +msgid "Modifiers" +msgstr "" + +#: ../Doc/library/trace.rst:82 +msgid "" +"Name of a file to accumulate counts over several tracing runs. Should be " +"used with the :option:`--count <-c>` option." +msgstr "" + +#: ../Doc/library/trace.rst:87 +msgid "" +"Directory where the report files go. The coverage report for ``package." +"module`` is written to file :file:`{dir}/{package}/{module}.cover`." +msgstr "" + +#: ../Doc/library/trace.rst:92 +msgid "" +"When generating annotated listings, mark lines which were not executed with " +"``>>>>>>``." +msgstr "" + +#: ../Doc/library/trace.rst:97 +msgid "" +"When using :option:`--count <-c>` or :option:`--report <-r>`, write a brief " +"summary to stdout for each file processed." +msgstr "" + +#: ../Doc/library/trace.rst:102 +msgid "" +"Do not generate annotated listings. This is useful if you intend to make " +"several runs with :option:`--count <-c>`, and then produce a single set of " +"annotated listings at the end." +msgstr "" + +#: ../Doc/library/trace.rst:108 +msgid "" +"Prefix each line with the time since the program started. Only used while " +"tracing." +msgstr "" + +#: ../Doc/library/trace.rst:112 +msgid "Filters" +msgstr "" + +#: ../Doc/library/trace.rst:114 +msgid "These options may be repeated multiple times." +msgstr "" + +#: ../Doc/library/trace.rst:120 +msgid "" +"Ignore each of the given module names and its submodules (if it is a " +"package). The argument can be a list of names separated by a comma." +msgstr "" + +#: ../Doc/library/trace.rst:125 +msgid "" +"Ignore all modules and packages in the named directory and subdirectories. " +"The argument can be a list of directories separated by :data:`os.pathsep`." +msgstr "" + +#: ../Doc/library/trace.rst:136 +msgid "" +"Create an object to trace execution of a single statement or expression. " +"All parameters are optional. *count* enables counting of line numbers. " +"*trace* enables line execution tracing. *countfuncs* enables listing of the " +"functions called during the run. *countcallers* enables call relationship " +"tracking. *ignoremods* is a list of modules or packages to ignore. " +"*ignoredirs* is a list of directories whose modules or packages should be " +"ignored. *infile* is the name of the file from which to read stored count " +"information. *outfile* is the name of the file in which to write updated " +"count information. *timing* enables a timestamp relative to when tracing " +"was started to be displayed." +msgstr "" + +#: ../Doc/library/trace.rst:149 +msgid "" +"Execute the command and gather statistics from the execution with the " +"current tracing parameters. *cmd* must be a string or code object, suitable " +"for passing into :func:`exec`." +msgstr "" + +#: ../Doc/library/trace.rst:155 +msgid "" +"Execute the command and gather statistics from the execution with the " +"current tracing parameters, in the defined global and local environments. " +"If not defined, *globals* and *locals* default to empty dictionaries." +msgstr "" + +#: ../Doc/library/trace.rst:162 +msgid "" +"Call *func* with the given arguments under control of the :class:`Trace` " +"object with the current tracing parameters." +msgstr "" + +#: ../Doc/library/trace.rst:167 +msgid "" +"Return a :class:`CoverageResults` object that contains the cumulative " +"results of all previous calls to ``run``, ``runctx`` and ``runfunc`` for the " +"given :class:`Trace` instance. Does not reset the accumulated trace results." +msgstr "" + +#: ../Doc/library/trace.rst:174 +msgid "" +"A container for coverage results, created by :meth:`Trace.results`. Should " +"not be created directly by the user." +msgstr "" + +#: ../Doc/library/trace.rst:179 +msgid "Merge in data from another :class:`CoverageResults` object." +msgstr "" + +#: ../Doc/library/trace.rst:183 +msgid "" +"Write coverage results. Set *show_missing* to show lines that had no hits. " +"Set *summary* to include in the output the coverage summary per module. " +"*coverdir* specifies the directory into which the coverage result files will " +"be output. If ``None``, the results for each source file are placed in its " +"directory." +msgstr "" + +#: ../Doc/library/trace.rst:189 +msgid "A simple example demonstrating the use of the programmatic interface::" +msgstr "" + +#: ../Doc/library/traceback.rst:2 +msgid ":mod:`traceback` --- Print or retrieve a stack traceback" +msgstr "" + +#: ../Doc/library/traceback.rst:7 +msgid "**Source code:** :source:`Lib/traceback.py`" +msgstr "" + +#: ../Doc/library/traceback.rst:11 +msgid "" +"This module provides a standard interface to extract, format and print stack " +"traces of Python programs. It exactly mimics the behavior of the Python " +"interpreter when it prints a stack trace. This is useful when you want to " +"print stack traces under program control, such as in a \"wrapper\" around " +"the interpreter." +msgstr "" + +#: ../Doc/library/traceback.rst:19 +msgid "" +"The module uses traceback objects --- this is the object type that is stored " +"in the :data:`sys.last_traceback` variable and returned as the third item " +"from :func:`sys.exc_info`." +msgstr "" + +#: ../Doc/library/traceback.rst:28 +msgid "" +"Print up to *limit* stack trace entries from traceback object *tb* (starting " +"from the caller's frame) if *limit* is positive. Otherwise, print the last " +"``abs(limit)`` entries. If *limit* is omitted or ``None``, all entries are " +"printed. If *file* is omitted or ``None``, the output goes to ``sys." +"stderr``; otherwise it should be an open file or file-like object to receive " +"the output." +msgstr "" + +#: ../Doc/library/traceback.rst:35 ../Doc/library/traceback.rst:82 +msgid "Added negative *limit* support." +msgstr "" + +#: ../Doc/library/traceback.rst:41 +msgid "" +"Print exception information and stack trace entries from traceback object " +"*tb* to *file*. This differs from :func:`print_tb` in the following ways:" +msgstr "" + +#: ../Doc/library/traceback.rst:45 +msgid "" +"if *tb* is not ``None``, it prints a header ``Traceback (most recent call " +"last):``" +msgstr "" + +#: ../Doc/library/traceback.rst:47 +msgid "it prints the exception *etype* and *value* after the stack trace" +msgstr "" + +#: ../Doc/library/traceback.rst:48 +msgid "" +"if *etype* is :exc:`SyntaxError` and *value* has the appropriate format, it " +"prints the line where the syntax error occurred with a caret indicating the " +"approximate position of the error." +msgstr "" + +#: ../Doc/library/traceback.rst:52 +msgid "" +"The optional *limit* argument has the same meaning as for :func:`print_tb`. " +"If *chain* is true (the default), then chained exceptions (the :attr:" +"`__cause__` or :attr:`__context__` attributes of the exception) will be " +"printed as well, like the interpreter itself does when printing an unhandled " +"exception." +msgstr "" + +#: ../Doc/library/traceback.rst:61 +msgid "" +"This is a shorthand for ``print_exception(*sys.exc_info(), limit, file, " +"chain)``." +msgstr "" + +#: ../Doc/library/traceback.rst:67 +msgid "" +"This is a shorthand for ``print_exception(sys.last_type, sys.last_value, sys." +"last_traceback, limit, file, chain)``. In general it will work only after " +"an exception has reached an interactive prompt (see :data:`sys.last_type`)." +msgstr "" + +#: ../Doc/library/traceback.rst:75 +msgid "" +"Print up to *limit* stack trace entries (starting from the invocation point) " +"if *limit* is positive. Otherwise, print the last ``abs(limit)`` entries. " +"If *limit* is omitted or ``None``, all entries are printed. The optional *f* " +"argument can be used to specify an alternate stack frame to start. The " +"optional *file* argument has the same meaning as for :func:`print_tb`." +msgstr "" + +#: ../Doc/library/traceback.rst:88 +msgid "" +"Return a list of \"pre-processed\" stack trace entries extracted from the " +"traceback object *tb*. It is useful for alternate formatting of stack " +"traces. The optional *limit* argument has the same meaning as for :func:" +"`print_tb`. A \"pre-processed\" stack trace entry is a 4-tuple (*filename*, " +"*line number*, *function name*, *text*) representing the information that is " +"usually printed for a stack trace. The *text* is a string with leading and " +"trailing whitespace stripped; if the source is not available it is ``None``." +msgstr "" + +#: ../Doc/library/traceback.rst:100 +msgid "" +"Extract the raw traceback from the current stack frame. The return value " +"has the same format as for :func:`extract_tb`. The optional *f* and *limit* " +"arguments have the same meaning as for :func:`print_stack`." +msgstr "" + +#: ../Doc/library/traceback.rst:107 +msgid "" +"Given a list of tuples as returned by :func:`extract_tb` or :func:" +"`extract_stack`, return a list of strings ready for printing. Each string in " +"the resulting list corresponds to the item with the same index in the " +"argument list. Each string ends in a newline; the strings may contain " +"internal newlines as well, for those items whose source text line is not " +"``None``." +msgstr "" + +#: ../Doc/library/traceback.rst:117 +msgid "" +"Format the exception part of a traceback. The arguments are the exception " +"type and value such as given by ``sys.last_type`` and ``sys.last_value``. " +"The return value is a list of strings, each ending in a newline. Normally, " +"the list contains a single string; however, for :exc:`SyntaxError` " +"exceptions, it contains several lines that (when printed) display detailed " +"information about where the syntax error occurred. The message indicating " +"which exception occurred is the always last string in the list." +msgstr "" + +#: ../Doc/library/traceback.rst:128 +msgid "" +"Format a stack trace and the exception information. The arguments have the " +"same meaning as the corresponding arguments to :func:`print_exception`. The " +"return value is a list of strings, each ending in a newline and some " +"containing internal newlines. When these lines are concatenated and " +"printed, exactly the same text is printed as does :func:`print_exception`." +msgstr "" + +#: ../Doc/library/traceback.rst:137 +msgid "" +"This is like ``print_exc(limit)`` but returns a string instead of printing " +"to a file." +msgstr "" + +#: ../Doc/library/traceback.rst:143 +msgid "A shorthand for ``format_list(extract_tb(tb, limit))``." +msgstr "" + +#: ../Doc/library/traceback.rst:148 +msgid "A shorthand for ``format_list(extract_stack(f, limit))``." +msgstr "" + +#: ../Doc/library/traceback.rst:152 +msgid "" +"Clears the local variables of all the stack frames in a traceback *tb* by " +"calling the :meth:`clear` method of each frame object." +msgstr "" + +#: ../Doc/library/traceback.rst:159 +msgid "" +"Walk a stack following ``f.f_back`` from the given frame, yielding the frame " +"and line number for each frame. If *f* is ``None``, the current stack is " +"used. This helper is used with :meth:`StackSummary.extract`." +msgstr "" + +#: ../Doc/library/traceback.rst:167 +msgid "" +"Walk a traceback following ``tb_next`` yielding the frame and line number " +"for each frame. This helper is used with :meth:`StackSummary.extract`." +msgstr "" + +#: ../Doc/library/traceback.rst:172 +msgid "The module also defines the following classes:" +msgstr "" + +#: ../Doc/library/traceback.rst:175 +msgid ":class:`TracebackException` Objects" +msgstr "" + +#: ../Doc/library/traceback.rst:179 +msgid "" +":class:`TracebackException` objects are created from actual exceptions to " +"capture data for later printing in a lightweight fashion." +msgstr "" + +#: ../Doc/library/traceback.rst:184 ../Doc/library/traceback.rst:231 +msgid "" +"Capture an exception for later rendering. *limit*, *lookup_lines* and " +"*capture_locals* are as for the :class:`StackSummary` class." +msgstr "" + +#: ../Doc/library/traceback.rst:187 ../Doc/library/traceback.rst:234 +msgid "" +"Note that when locals are captured, they are also shown in the traceback." +msgstr "" + +#: ../Doc/library/traceback.rst:191 +msgid "A :class:`TracebackException` of the original ``__cause__``." +msgstr "" + +#: ../Doc/library/traceback.rst:195 +msgid "A :class:`TracebackException` of the original ``__context__``." +msgstr "" + +#: ../Doc/library/traceback.rst:199 +msgid "The ``__suppress_context__`` value from the original exception." +msgstr "" + +#: ../Doc/library/traceback.rst:203 +msgid "A :class:`StackSummary` representing the traceback." +msgstr "" + +#: ../Doc/library/traceback.rst:207 +msgid "The class of the original traceback." +msgstr "" + +#: ../Doc/library/traceback.rst:211 +msgid "For syntax errors - the file name where the error occurred." +msgstr "" + +#: ../Doc/library/traceback.rst:215 +msgid "For syntax errors - the line number where the error occurred." +msgstr "" + +#: ../Doc/library/traceback.rst:219 +msgid "For syntax errors - the text where the error occurred." +msgstr "" + +#: ../Doc/library/traceback.rst:223 +msgid "For syntax errors - the offset into the text where the error occurred." +msgstr "" + +#: ../Doc/library/traceback.rst:227 +msgid "For syntax errors - the compiler error message." +msgstr "" + +#: ../Doc/library/traceback.rst:238 +msgid "Format the exception." +msgstr "" + +#: ../Doc/library/traceback.rst:240 +msgid "" +"If *chain* is not ``True``, ``__cause__`` and ``__context__`` will not be " +"formatted." +msgstr "" + +#: ../Doc/library/traceback.rst:243 +msgid "" +"The return value is a generator of strings, each ending in a newline and " +"some containing internal newlines. :func:`~traceback.print_exception` is a " +"wrapper around this method which just prints the lines to a file." +msgstr "" + +#: ../Doc/library/traceback.rst:247 ../Doc/library/traceback.rst:261 +msgid "" +"The message indicating which exception occurred is always the last string in " +"the output." +msgstr "" + +#: ../Doc/library/traceback.rst:252 +msgid "Format the exception part of the traceback." +msgstr "" + +#: ../Doc/library/traceback.rst:254 +msgid "The return value is a generator of strings, each ending in a newline." +msgstr "" + +#: ../Doc/library/traceback.rst:256 +msgid "" +"Normally, the generator emits a single string; however, for :exc:" +"`SyntaxError` exceptions, it emits several lines that (when printed) display " +"detailed information about where the syntax error occurred." +msgstr "" + +#: ../Doc/library/traceback.rst:266 +msgid ":class:`StackSummary` Objects" +msgstr "" + +#: ../Doc/library/traceback.rst:270 +msgid "" +":class:`StackSummary` objects represent a call stack ready for formatting." +msgstr "" + +#: ../Doc/library/traceback.rst:276 +msgid "" +"Construct a :class:`StackSummary` object from a frame generator (such as is " +"returned by :func:`~traceback.walk_stack` or :func:`~traceback.walk_tb`)." +msgstr "" + +#: ../Doc/library/traceback.rst:280 +msgid "" +"If *limit* is supplied, only this many frames are taken from *frame_gen*. If " +"*lookup_lines* is ``False``, the returned :class:`FrameSummary` objects will " +"not have read their lines in yet, making the cost of creating the :class:" +"`StackSummary` cheaper (which may be valuable if it may not actually get " +"formatted). If *capture_locals* is ``True`` the local variables in each :" +"class:`FrameSummary` are captured as object representations." +msgstr "" + +#: ../Doc/library/traceback.rst:290 +msgid "" +"Construct a :class:`StackSummary` object from a supplied old-style list of " +"tuples. Each tuple should be a 4-tuple with filename, lineno, name, line as " +"the elements." +msgstr "" + +#: ../Doc/library/traceback.rst:296 +msgid "" +"Returns a list of strings ready for printing. Each string in the resulting " +"list corresponds to a single frame from the stack. Each string ends in a " +"newline; the strings may contain internal newlines as well, for those items " +"with source text lines." +msgstr "" + +#: ../Doc/library/traceback.rst:301 +msgid "" +"For long sequences of the same frame and line, the first few repetitions are " +"shown, followed by a summary line stating the exact number of further " +"repetitions." +msgstr "" + +#: ../Doc/library/traceback.rst:305 +msgid "Long sequences of repeated frames are now abbreviated." +msgstr "" + +#: ../Doc/library/traceback.rst:310 +msgid ":class:`FrameSummary` Objects" +msgstr "" + +#: ../Doc/library/traceback.rst:314 +msgid ":class:`FrameSummary` objects represent a single frame in a traceback." +msgstr "" + +#: ../Doc/library/traceback.rst:318 +msgid "" +"Represent a single frame in the traceback or stack that is being formatted " +"or printed. It may optionally have a stringified version of the frames " +"locals included in it. If *lookup_line* is ``False``, the source code is not " +"looked up until the :class:`FrameSummary` has the :attr:`~FrameSummary.line` " +"attribute accessed (which also happens when casting it to a tuple). :attr:" +"`~FrameSummary.line` may be directly provided, and will prevent line lookups " +"happening at all. *locals* is an optional local variable dictionary, and if " +"supplied the variable representations are stored in the summary for later " +"display." +msgstr "" + +#: ../Doc/library/traceback.rst:331 +msgid "Traceback Examples" +msgstr "" + +#: ../Doc/library/traceback.rst:333 +msgid "" +"This simple example implements a basic read-eval-print loop, similar to (but " +"less useful than) the standard Python interactive interpreter loop. For a " +"more complete implementation of the interpreter loop, refer to the :mod:" +"`code` module. ::" +msgstr "" + +#: ../Doc/library/traceback.rst:355 +msgid "" +"The following example demonstrates the different ways to print and format " +"the exception and traceback:" +msgstr "" + +#: ../Doc/library/traceback.rst:392 +msgid "The output for the example would look similar to this:" +msgstr "" + +#: ../Doc/library/traceback.rst:434 +msgid "" +"The following example shows the different ways to print and format the " +"stack::" +msgstr "" + +#: ../Doc/library/traceback.rst:460 +msgid "This last example demonstrates the final few formatting functions:" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:2 +msgid ":mod:`tracemalloc` --- Trace memory allocations" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:9 +msgid "**Source code:** :source:`Lib/tracemalloc.py`" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:13 +msgid "" +"The tracemalloc module is a debug tool to trace memory blocks allocated by " +"Python. It provides the following information:" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:16 +msgid "Traceback where an object was allocated" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:17 +msgid "" +"Statistics on allocated memory blocks per filename and per line number: " +"total size, number and average size of allocated memory blocks" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:19 +msgid "Compute the differences between two snapshots to detect memory leaks" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:21 +msgid "" +"To trace most memory blocks allocated by Python, the module should be " +"started as early as possible by setting the :envvar:`PYTHONTRACEMALLOC` " +"environment variable to ``1``, or by using :option:`-X` ``tracemalloc`` " +"command line option. The :func:`tracemalloc.start` function can be called at " +"runtime to start tracing Python memory allocations." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:27 +msgid "" +"By default, a trace of an allocated memory block only stores the most recent " +"frame (1 frame). To store 25 frames at startup: set the :envvar:" +"`PYTHONTRACEMALLOC` environment variable to ``25``, or use the :option:`-X` " +"``tracemalloc=25`` command line option." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:37 +msgid "Display the top 10" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:39 +msgid "Display the 10 files allocating the most memory::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:55 ../Doc/library/tracemalloc.rst:227 +msgid "Example of output of the Python test suite::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:69 +msgid "" +"We can see that Python loaded ``4.8 MiB`` data (bytecode and constants) from " +"modules and that the :mod:`collections` module allocated ``244 KiB`` to " +"build :class:`~collections.namedtuple` types." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:73 ../Doc/library/tracemalloc.rst:252 +msgid "See :meth:`Snapshot.statistics` for more options." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:77 +msgid "Compute differences" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:79 +msgid "Take two snapshots and display the differences::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:95 +msgid "" +"Example of output before/after running some tests of the Python test suite::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:109 +msgid "" +"We can see that Python has loaded ``8.2 MiB`` of module data (bytecode and " +"constants), and that this is ``4.4 MiB`` more than had been loaded before " +"the tests, when the previous snapshot was taken. Similarly, the :mod:" +"`linecache` module has cached ``940 KiB`` of Python source code to format " +"tracebacks, all of it since the previous snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:115 +msgid "" +"If the system has little free memory, snapshots can be written on disk using " +"the :meth:`Snapshot.dump` method to analyze the snapshot offline. Then use " +"the :meth:`Snapshot.load` method reload the snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:121 +msgid "Get the traceback of a memory block" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:123 +msgid "Code to display the traceback of the biggest memory block::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:141 +msgid "" +"Example of output of the Python test suite (traceback limited to 25 frames)::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:178 +msgid "" +"We can see that the most memory was allocated in the :mod:`importlib` module " +"to load data (bytecode and constants) from modules: ``870 KiB``. The " +"traceback is where the :mod:`importlib` loaded data most recently: on the " +"``import pdb`` line of the :mod:`doctest` module. The traceback may change " +"if a new module is loaded." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:186 +msgid "Pretty top" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:188 +msgid "" +"Code to display the 10 lines allocating the most memory with a pretty " +"output, ignoring ```` and ```` files::" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:256 ../Doc/library/venv.rst:83 +msgid "API" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:263 +msgid "Clear traces of memory blocks allocated by Python." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:265 +msgid "See also :func:`stop`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:270 +msgid "" +"Get the traceback where the Python object *obj* was allocated. Return a :" +"class:`Traceback` instance, or ``None`` if the :mod:`tracemalloc` module is " +"not tracing memory allocations or did not trace the allocation of the object." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:275 +msgid "See also :func:`gc.get_referrers` and :func:`sys.getsizeof` functions." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:280 +msgid "Get the maximum number of frames stored in the traceback of a trace." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:282 +msgid "" +"The :mod:`tracemalloc` module must be tracing memory allocations to get the " +"limit, otherwise an exception is raised." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:285 +msgid "The limit is set by the :func:`start` function." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:290 +msgid "" +"Get the current size and peak size of memory blocks traced by the :mod:" +"`tracemalloc` module as a tuple: ``(current: int, peak: int)``." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:296 +msgid "" +"Get the memory usage in bytes of the :mod:`tracemalloc` module used to store " +"traces of memory blocks. Return an :class:`int`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:303 +msgid "" +"``True`` if the :mod:`tracemalloc` module is tracing Python memory " +"allocations, ``False`` otherwise." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:306 +msgid "See also :func:`start` and :func:`stop` functions." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:311 +msgid "" +"Start tracing Python memory allocations: install hooks on Python memory " +"allocators. Collected tracebacks of traces will be limited to *nframe* " +"frames. By default, a trace of a memory block only stores the most recent " +"frame: the limit is ``1``. *nframe* must be greater or equal to ``1``." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:316 +msgid "" +"Storing more than ``1`` frame is only useful to compute statistics grouped " +"by ``'traceback'`` or to compute cumulative statistics: see the :meth:" +"`Snapshot.compare_to` and :meth:`Snapshot.statistics` methods." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:320 +msgid "" +"Storing more frames increases the memory and CPU overhead of the :mod:" +"`tracemalloc` module. Use the :func:`get_tracemalloc_memory` function to " +"measure how much memory is used by the :mod:`tracemalloc` module." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:324 +msgid "" +"The :envvar:`PYTHONTRACEMALLOC` environment variable " +"(``PYTHONTRACEMALLOC=NFRAME``) and the :option:`-X` ``tracemalloc=NFRAME`` " +"command line option can be used to start tracing at startup." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:328 +msgid "" +"See also :func:`stop`, :func:`is_tracing` and :func:`get_traceback_limit` " +"functions." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:334 +msgid "" +"Stop tracing Python memory allocations: uninstall hooks on Python memory " +"allocators. Also clears all previously collected traces of memory blocks " +"allocated by Python." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:338 +msgid "" +"Call :func:`take_snapshot` function to take a snapshot of traces before " +"clearing them." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:341 +msgid "" +"See also :func:`start`, :func:`is_tracing` and :func:`clear_traces` " +"functions." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:347 +msgid "" +"Take a snapshot of traces of memory blocks allocated by Python. Return a " +"new :class:`Snapshot` instance." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:350 +msgid "" +"The snapshot does not include memory blocks allocated before the :mod:" +"`tracemalloc` module started to trace memory allocations." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:353 +msgid "" +"Tracebacks of traces are limited to :func:`get_traceback_limit` frames. Use " +"the *nframe* parameter of the :func:`start` function to store more frames." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:356 +msgid "" +"The :mod:`tracemalloc` module must be tracing memory allocations to take a " +"snapshot, see the :func:`start` function." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:359 +msgid "See also the :func:`get_object_traceback` function." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:363 +msgid "DomainFilter" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:367 +msgid "Filter traces of memory blocks by their address space (domain)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:373 +msgid "" +"If *inclusive* is ``True`` (include), match memory blocks allocated in the " +"address space :attr:`domain`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:376 +msgid "" +"If *inclusive* is ``False`` (exclude), match memory blocks not allocated in " +"the address space :attr:`domain`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:381 +msgid "Address space of a memory block (``int``). Read-only property." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:385 +msgid "Filter" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:389 +msgid "Filter on traces of memory blocks." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:391 +msgid "" +"See the :func:`fnmatch.fnmatch` function for the syntax of " +"*filename_pattern*. The ``'.pyc'`` file extension is replaced with ``'.py'``." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:397 +msgid "" +"``Filter(True, subprocess.__file__)`` only includes traces of the :mod:" +"`subprocess` module" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:399 +msgid "" +"``Filter(False, tracemalloc.__file__)`` excludes traces of the :mod:" +"`tracemalloc` module" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:401 +msgid "``Filter(False, \"\")`` excludes empty tracebacks" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:404 +msgid "The ``'.pyo'`` file extension is no longer replaced with ``'.py'``." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:407 +msgid "Added the :attr:`domain` attribute." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:413 +msgid "Address space of a memory block (``int`` or ``None``)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:417 +msgid "" +"If *inclusive* is ``True`` (include), only match memory blocks allocated in " +"a file with a name matching :attr:`filename_pattern` at line number :attr:" +"`lineno`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:421 +msgid "" +"If *inclusive* is ``False`` (exclude), ignore memory blocks allocated in a " +"file with a name matching :attr:`filename_pattern` at line number :attr:" +"`lineno`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:427 +msgid "" +"Line number (``int``) of the filter. If *lineno* is ``None``, the filter " +"matches any line number." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:432 +msgid "Filename pattern of the filter (``str``). Read-only property." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:436 +msgid "" +"If *all_frames* is ``True``, all frames of the traceback are checked. If " +"*all_frames* is ``False``, only the most recent frame is checked." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:439 +msgid "" +"This attribute has no effect if the traceback limit is ``1``. See the :func:" +"`get_traceback_limit` function and :attr:`Snapshot.traceback_limit` " +"attribute." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:445 +msgid "Frame" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:449 +msgid "Frame of a traceback." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:451 +msgid "The :class:`Traceback` class is a sequence of :class:`Frame` instances." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:455 +msgid "Filename (``str``)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:459 +msgid "Line number (``int``)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:463 +msgid "Snapshot" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:467 +msgid "Snapshot of traces of memory blocks allocated by Python." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:469 +msgid "The :func:`take_snapshot` function creates a snapshot instance." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:473 +msgid "" +"Compute the differences with an old snapshot. Get statistics as a sorted " +"list of :class:`StatisticDiff` instances grouped by *group_by*." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:476 +msgid "" +"See the :meth:`Snapshot.statistics` method for *group_by* and *cumulative* " +"parameters." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:479 +msgid "" +"The result is sorted from the biggest to the smallest by: absolute value of :" +"attr:`StatisticDiff.size_diff`, :attr:`StatisticDiff.size`, absolute value " +"of :attr:`StatisticDiff.count_diff`, :attr:`Statistic.count` and then by :" +"attr:`StatisticDiff.traceback`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:487 +msgid "Write the snapshot into a file." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:489 +msgid "Use :meth:`load` to reload the snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:494 +msgid "" +"Create a new :class:`Snapshot` instance with a filtered :attr:`traces` " +"sequence, *filters* is a list of :class:`DomainFilter` and :class:`Filter` " +"instances. If *filters* is an empty list, return a new :class:`Snapshot` " +"instance with a copy of the traces." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:499 +msgid "" +"All inclusive filters are applied at once, a trace is ignored if no " +"inclusive filters match it. A trace is ignored if at least one exclusive " +"filter matches it." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:503 +msgid ":class:`DomainFilter` instances are now also accepted in *filters*." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:509 +msgid "Load a snapshot from a file." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:511 +msgid "See also :meth:`dump`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:516 +msgid "" +"Get statistics as a sorted list of :class:`Statistic` instances grouped by " +"*group_by*:" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:520 +msgid "group_by" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:523 +msgid "``'lineno'``" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:523 +msgid "filename and line number" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:524 +msgid "``'traceback'``" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:527 +msgid "" +"If *cumulative* is ``True``, cumulate size and count of memory blocks of all " +"frames of the traceback of a trace, not only the most recent frame. The " +"cumulative mode can only be used with *group_by* equals to ``'filename'`` " +"and ``'lineno'``." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:532 +msgid "" +"The result is sorted from the biggest to the smallest by: :attr:`Statistic." +"size`, :attr:`Statistic.count` and then by :attr:`Statistic.traceback`." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:539 +msgid "" +"Maximum number of frames stored in the traceback of :attr:`traces`: result " +"of the :func:`get_traceback_limit` when the snapshot was taken." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:544 +msgid "" +"Traces of all memory blocks allocated by Python: sequence of :class:`Trace` " +"instances." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:547 +msgid "" +"The sequence has an undefined order. Use the :meth:`Snapshot.statistics` " +"method to get a sorted list of statistics." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:552 +msgid "Statistic" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:556 +msgid "Statistic on memory allocations." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:558 +msgid "" +":func:`Snapshot.statistics` returns a list of :class:`Statistic` instances." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:560 +msgid "See also the :class:`StatisticDiff` class." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:564 +msgid "Number of memory blocks (``int``)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:568 +msgid "Total size of memory blocks in bytes (``int``)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:572 ../Doc/library/tracemalloc.rst:631 +msgid "" +"Traceback where the memory block was allocated, :class:`Traceback` instance." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:577 +msgid "StatisticDiff" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:581 +msgid "" +"Statistic difference on memory allocations between an old and a new :class:" +"`Snapshot` instance." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:584 +msgid "" +":func:`Snapshot.compare_to` returns a list of :class:`StatisticDiff` " +"instances. See also the :class:`Statistic` class." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:589 +msgid "" +"Number of memory blocks in the new snapshot (``int``): ``0`` if the memory " +"blocks have been released in the new snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:594 +msgid "" +"Difference of number of memory blocks between the old and the new snapshots " +"(``int``): ``0`` if the memory blocks have been allocated in the new " +"snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:600 +msgid "" +"Total size of memory blocks in bytes in the new snapshot (``int``): ``0`` if " +"the memory blocks have been released in the new snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:605 +msgid "" +"Difference of total size of memory blocks in bytes between the old and the " +"new snapshots (``int``): ``0`` if the memory blocks have been allocated in " +"the new snapshot." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:611 +msgid "" +"Traceback where the memory blocks were allocated, :class:`Traceback` " +"instance." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:616 +msgid "Trace" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:620 +msgid "Trace of a memory block." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:622 +msgid "" +"The :attr:`Snapshot.traces` attribute is a sequence of :class:`Trace` " +"instances." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:627 +msgid "Size of the memory block in bytes (``int``)." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:636 +msgid "Traceback" +msgstr "" + +#: ../Doc/library/tracemalloc.rst:640 +msgid "" +"Sequence of :class:`Frame` instances sorted from the most recent frame to " +"the oldest frame." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:643 +msgid "" +"A traceback contains at least ``1`` frame. If the ``tracemalloc`` module " +"failed to get a frame, the filename ``\"\"`` at line number ``0`` " +"is used." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:647 +msgid "" +"When a snapshot is taken, tracebacks of traces are limited to :func:" +"`get_traceback_limit` frames. See the :func:`take_snapshot` function." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:650 +msgid "" +"The :attr:`Trace.traceback` attribute is an instance of :class:`Traceback` " +"instance." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:655 +msgid "" +"Format the traceback as a list of lines with newlines. Use the :mod:" +"`linecache` module to retrieve lines from the source code. If *limit* is " +"set, only format the *limit* most recent frames." +msgstr "" + +#: ../Doc/library/tracemalloc.rst:659 +msgid "" +"Similar to the :func:`traceback.format_tb` function, except that :meth:`." +"format` does not include newlines." +msgstr "" + +#: ../Doc/library/tty.rst:2 +msgid ":mod:`tty` --- Terminal control functions" +msgstr "" + +#: ../Doc/library/tty.rst:11 +msgid "**Source code:** :source:`Lib/tty.py`" +msgstr "" + +#: ../Doc/library/tty.rst:15 +msgid "" +"The :mod:`tty` module defines functions for putting the tty into cbreak and " +"raw modes." +msgstr "" + +#: ../Doc/library/tty.rst:18 +msgid "" +"Because it requires the :mod:`termios` module, it will work only on Unix." +msgstr "" + +#: ../Doc/library/tty.rst:20 +msgid "The :mod:`tty` module defines the following functions:" +msgstr "" + +#: ../Doc/library/tty.rst:25 +msgid "" +"Change the mode of the file descriptor *fd* to raw. If *when* is omitted, it " +"defaults to :const:`termios.TCSAFLUSH`, and is passed to :func:`termios." +"tcsetattr`." +msgstr "" + +#: ../Doc/library/tty.rst:32 +msgid "" +"Change the mode of file descriptor *fd* to cbreak. If *when* is omitted, it " +"defaults to :const:`termios.TCSAFLUSH`, and is passed to :func:`termios." +"tcsetattr`." +msgstr "" + +#: ../Doc/library/tty.rst:39 +msgid "Module :mod:`termios`" +msgstr "" + +#: ../Doc/library/tty.rst:40 +msgid "Low-level terminal control interface." +msgstr "" + +#: ../Doc/library/turtle.rst:3 +msgid ":mod:`turtle` --- Turtle graphics" +msgstr "" + +#: ../Doc/library/turtle.rst:10 +msgid "**Source code:** :source:`Lib/turtle.py`" +msgstr "" + +#: ../Doc/library/turtle.rst:22 +msgid "" +"Turtle graphics is a popular way for introducing programming to kids. It " +"was part of the original Logo programming language developed by Wally " +"Feurzig and Seymour Papert in 1966." +msgstr "" + +#: ../Doc/library/turtle.rst:26 +msgid "" +"Imagine a robotic turtle starting at (0, 0) in the x-y plane. After an " +"``import turtle``, give it the command ``turtle.forward(15)``, and it moves " +"(on-screen!) 15 pixels in the direction it is facing, drawing a line as it " +"moves. Give it the command ``turtle.right(25)``, and it rotates in-place 25 " +"degrees clockwise." +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid "Turtle star" +msgstr "" + +#: ../Doc/library/turtle.rst:33 +msgid "" +"Turtle can draw intricate shapes using programs that repeat simple moves." +msgstr "" + +#: ../Doc/library/turtle.rst:41 +msgid "" +"By combining together these and similar commands, intricate shapes and " +"pictures can easily be drawn." +msgstr "" + +#: ../Doc/library/turtle.rst:44 +msgid "" +"The :mod:`turtle` module is an extended reimplementation of the same-named " +"module from the Python standard distribution up to version Python 2.5." +msgstr "" + +#: ../Doc/library/turtle.rst:47 +msgid "" +"It tries to keep the merits of the old turtle module and to be (nearly) 100% " +"compatible with it. This means in the first place to enable the learning " +"programmer to use all the commands, classes and methods interactively when " +"using the module from within IDLE run with the ``-n`` switch." +msgstr "" + +#: ../Doc/library/turtle.rst:52 +msgid "" +"The turtle module provides turtle graphics primitives, in both object-" +"oriented and procedure-oriented ways. Because it uses :mod:`tkinter` for " +"the underlying graphics, it needs a version of Python installed with Tk " +"support." +msgstr "" + +#: ../Doc/library/turtle.rst:56 +msgid "The object-oriented interface uses essentially two+two classes:" +msgstr "" + +#: ../Doc/library/turtle.rst:58 +msgid "" +"The :class:`TurtleScreen` class defines graphics windows as a playground for " +"the drawing turtles. Its constructor needs a :class:`tkinter.Canvas` or a :" +"class:`ScrolledCanvas` as argument. It should be used when :mod:`turtle` is " +"used as part of some application." +msgstr "" + +#: ../Doc/library/turtle.rst:63 +msgid "" +"The function :func:`Screen` returns a singleton object of a :class:" +"`TurtleScreen` subclass. This function should be used when :mod:`turtle` is " +"used as a standalone tool for doing graphics. As a singleton object, " +"inheriting from its class is not possible." +msgstr "" + +#: ../Doc/library/turtle.rst:68 +msgid "" +"All methods of TurtleScreen/Screen also exist as functions, i.e. as part of " +"the procedure-oriented interface." +msgstr "" + +#: ../Doc/library/turtle.rst:71 +msgid "" +":class:`RawTurtle` (alias: :class:`RawPen`) defines Turtle objects which " +"draw on a :class:`TurtleScreen`. Its constructor needs a Canvas, " +"ScrolledCanvas or TurtleScreen as argument, so the RawTurtle objects know " +"where to draw." +msgstr "" + +#: ../Doc/library/turtle.rst:75 +msgid "" +"Derived from RawTurtle is the subclass :class:`Turtle` (alias: :class:" +"`Pen`), which draws on \"the\" :class:`Screen` instance which is " +"automatically created, if not already present." +msgstr "" + +#: ../Doc/library/turtle.rst:79 +msgid "" +"All methods of RawTurtle/Turtle also exist as functions, i.e. part of the " +"procedure-oriented interface." +msgstr "" + +#: ../Doc/library/turtle.rst:82 +msgid "" +"The procedural interface provides functions which are derived from the " +"methods of the classes :class:`Screen` and :class:`Turtle`. They have the " +"same names as the corresponding methods. A screen object is automatically " +"created whenever a function derived from a Screen method is called. An " +"(unnamed) turtle object is automatically created whenever any of the " +"functions derived from a Turtle method is called." +msgstr "" + +#: ../Doc/library/turtle.rst:89 +msgid "" +"To use multiple turtles on a screen one has to use the object-oriented " +"interface." +msgstr "" + +#: ../Doc/library/turtle.rst:92 +msgid "" +"In the following documentation the argument list for functions is given. " +"Methods, of course, have the additional first argument *self* which is " +"omitted here." +msgstr "" + +#: ../Doc/library/turtle.rst:98 +msgid "Overview of available Turtle and Screen methods" +msgstr "" + +#: ../Doc/library/turtle.rst:101 +msgid "Turtle methods" +msgstr "" + +#: ../Doc/library/turtle.rst:132 ../Doc/library/turtle.rst:242 +msgid "Turtle motion" +msgstr "" + +#: ../Doc/library/turtle.rst:120 +msgid "Move and draw" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`forward` | :func:`fd`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`backward` | :func:`bk` | :func:`back`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`right` | :func:`rt`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`left` | :func:`lt`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`goto` | :func:`setpos` | :func:`setposition`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`setx`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`sety`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`setheading` | :func:`seth`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`home`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 ../Doc/library/turtle.rst:2371 +msgid ":func:`circle`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`dot`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 ../Doc/library/turtle.rst:2349 +msgid ":func:`stamp`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`clearstamp`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`clearstamps`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`undo`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`speed`" +msgstr "" + +#: ../Doc/library/turtle.rst:128 ../Doc/library/turtle.rst:623 +msgid "Tell Turtle's state" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`position` | :func:`pos`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`towards`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`xcor`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`ycor`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`heading`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`distance`" +msgstr "" + +#: ../Doc/library/turtle.rst:132 +msgid "Setting and measurement" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`degrees`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`radians`" +msgstr "" + +#: ../Doc/library/turtle.rst:155 ../Doc/library/turtle.rst:765 +msgid "Pen control" +msgstr "" + +#: ../Doc/library/turtle.rst:140 ../Doc/library/turtle.rst:768 +msgid "Drawing state" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`pendown` | :func:`pd` | :func:`down`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`penup` | :func:`pu` | :func:`up`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`pensize` | :func:`width`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`pen`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`isdown`" +msgstr "" + +#: ../Doc/library/turtle.rst:145 ../Doc/library/turtle.rst:857 +msgid "Color control" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`color`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`pencolor`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`fillcolor`" +msgstr "" + +#: ../Doc/library/turtle.rst:150 ../Doc/library/turtle.rst:987 +msgid "Filling" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`filling`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`begin_fill`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`end_fill`" +msgstr "" + +#: ../Doc/library/turtle.rst:155 ../Doc/library/turtle.rst:1026 +msgid "More drawing control" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`reset`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`clear`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`write`" +msgstr "" + +#: ../Doc/library/turtle.rst:172 ../Doc/library/turtle.rst:1071 +msgid "Turtle state" +msgstr "" + +#: ../Doc/library/turtle.rst:161 ../Doc/library/turtle.rst:1074 +msgid "Visibility" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`showturtle` | :func:`st`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`hideturtle` | :func:`ht`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`isvisible`" +msgstr "" + +#: ../Doc/library/turtle.rst:172 ../Doc/library/turtle.rst:1111 +msgid "Appearance" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`shape`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`resizemode`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`shapesize` | :func:`turtlesize`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`shearfactor`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`settiltangle`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`tiltangle`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`tilt`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`shapetransform`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`get_shapepoly`" +msgstr "" + +#: ../Doc/library/turtle.rst:177 ../Doc/library/turtle.rst:1307 +msgid "Using events" +msgstr "" + +#: ../Doc/library/turtle.rst:0 ../Doc/library/turtle.rst:2343 +msgid ":func:`onclick`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`onrelease`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 ../Doc/library/turtle.rst:2326 +msgid ":func:`ondrag`" +msgstr "" + +#: ../Doc/library/turtle.rst:188 ../Doc/library/turtle.rst:1377 +msgid "Special Turtle methods" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`begin_poly`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`end_poly`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`get_poly`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 ../Doc/library/turtle.rst:2362 +msgid ":func:`clone`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`getturtle` | :func:`getpen`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`getscreen`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`setundobuffer`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`undobufferentries`" +msgstr "" + +#: ../Doc/library/turtle.rst:191 +msgid "Methods of TurtleScreen/Screen" +msgstr "" + +#: ../Doc/library/turtle.rst:199 ../Doc/library/turtle.rst:1522 +msgid "Window control" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`bgcolor`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`bgpic`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`clear` | :func:`clearscreen`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`reset` | :func:`resetscreen`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`screensize`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`setworldcoordinates`" +msgstr "" + +#: ../Doc/library/turtle.rst:204 ../Doc/library/turtle.rst:1636 +msgid "Animation control" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`delay`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`tracer`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`update`" +msgstr "" + +#: ../Doc/library/turtle.rst:212 ../Doc/library/turtle.rst:1687 +msgid "Using screen events" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`listen`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`onkey` | :func:`onkeyrelease`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`onkeypress`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`onclick` | :func:`onscreenclick`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`ontimer`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`mainloop` | :func:`done`" +msgstr "" + +#: ../Doc/library/turtle.rst:222 ../Doc/library/turtle.rst:1828 +msgid "Settings and special methods" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`colormode`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`getcanvas`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`getshapes`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`register_shape` | :func:`addshape`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`turtles`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`window_height`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`window_width`" +msgstr "" + +#: ../Doc/library/turtle.rst:226 ../Doc/library/turtle.rst:1792 +msgid "Input methods" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`textinput`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`numinput`" +msgstr "" + +#: ../Doc/library/turtle.rst:233 +msgid "Methods specific to Screen" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`bye`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`exitonclick`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`setup`" +msgstr "" + +#: ../Doc/library/turtle.rst:0 +msgid ":func:`title`" +msgstr "" + +#: ../Doc/library/turtle.rst:236 +msgid "Methods of RawTurtle/Turtle and corresponding functions" +msgstr "" + +#: ../Doc/library/turtle.rst:238 +msgid "" +"Most of the examples in this section refer to a Turtle instance called " +"``turtle``." +msgstr "" + +#: ../Doc/library/turtle.rst:247 ../Doc/library/turtle.rst:290 +#: ../Doc/library/turtle.rst:313 ../Doc/library/turtle.rst:369 +#: ../Doc/library/turtle.rst:390 ../Doc/library/turtle.rst:411 +msgid "a number (integer or float)" +msgstr "" + +#: ../Doc/library/turtle.rst:249 +msgid "" +"Move the turtle forward by the specified *distance*, in the direction the " +"turtle is headed." +msgstr "" + +#: ../Doc/library/turtle.rst:268 ../Doc/library/turtle.rst:458 +#: ../Doc/library/turtle.rst:721 ../Doc/library/turtle.rst:1206 +#: ../Doc/library/turtle.rst:1224 +msgid "a number" +msgstr "" + +#: ../Doc/library/turtle.rst:270 +msgid "" +"Move the turtle backward by *distance*, opposite to the direction the turtle " +"is headed. Do not change the turtle's heading." +msgstr "" + +#: ../Doc/library/turtle.rst:292 +msgid "" +"Turn turtle right by *angle* units. (Units are by default degrees, but can " +"be set via the :func:`degrees` and :func:`radians` functions.) Angle " +"orientation depends on the turtle mode, see :func:`mode`." +msgstr "" + +#: ../Doc/library/turtle.rst:315 +msgid "" +"Turn turtle left by *angle* units. (Units are by default degrees, but can " +"be set via the :func:`degrees` and :func:`radians` functions.) Angle " +"orientation depends on the turtle mode, see :func:`mode`." +msgstr "" + +#: ../Doc/library/turtle.rst:337 +msgid "a number or a pair/vector of numbers" +msgstr "" + +#: ../Doc/library/turtle.rst:338 +msgid "a number or ``None``" +msgstr "" + +#: ../Doc/library/turtle.rst:340 +msgid "" +"If *y* is ``None``, *x* must be a pair of coordinates or a :class:`Vec2D` (e." +"g. as returned by :func:`pos`)." +msgstr "" + +#: ../Doc/library/turtle.rst:343 +msgid "" +"Move turtle to an absolute position. If the pen is down, draw line. Do not " +"change the turtle's orientation." +msgstr "" + +#: ../Doc/library/turtle.rst:371 +msgid "" +"Set the turtle's first coordinate to *x*, leave second coordinate unchanged." +msgstr "" + +#: ../Doc/library/turtle.rst:392 +msgid "" +"Set the turtle's second coordinate to *y*, leave first coordinate unchanged." +msgstr "" + +#: ../Doc/library/turtle.rst:413 +msgid "" +"Set the orientation of the turtle to *to_angle*. Here are some common " +"directions in degrees:" +msgstr "" + +#: ../Doc/library/turtle.rst:417 +msgid "standard mode" +msgstr "" + +#: ../Doc/library/turtle.rst:417 +msgid "logo mode" +msgstr "" + +#: ../Doc/library/turtle.rst:419 +msgid "0 - east" +msgstr "" + +#: ../Doc/library/turtle.rst:419 +msgid "0 - north" +msgstr "" + +#: ../Doc/library/turtle.rst:420 +msgid "90 - north" +msgstr "" + +#: ../Doc/library/turtle.rst:420 +msgid "90 - east" +msgstr "" + +#: ../Doc/library/turtle.rst:421 +msgid "180 - west" +msgstr "" + +#: ../Doc/library/turtle.rst:421 +msgid "180 - south" +msgstr "" + +#: ../Doc/library/turtle.rst:422 +msgid "270 - south" +msgstr "" + +#: ../Doc/library/turtle.rst:422 +msgid "270 - west" +msgstr "" + +#: ../Doc/library/turtle.rst:434 +msgid "" +"Move turtle to the origin -- coordinates (0,0) -- and set its heading to its " +"start-orientation (which depends on the mode, see :func:`mode`)." +msgstr "" + +#: ../Doc/library/turtle.rst:459 +msgid "a number (or ``None``)" +msgstr "" + +#: ../Doc/library/turtle.rst:460 ../Doc/library/turtle.rst:550 +msgid "an integer (or ``None``)" +msgstr "" + +#: ../Doc/library/turtle.rst:462 +msgid "" +"Draw a circle with given *radius*. The center is *radius* units left of the " +"turtle; *extent* -- an angle -- determines which part of the circle is " +"drawn. If *extent* is not given, draw the entire circle. If *extent* is " +"not a full circle, one endpoint of the arc is the current pen position. " +"Draw the arc in counterclockwise direction if *radius* is positive, " +"otherwise in clockwise direction. Finally the direction of the turtle is " +"changed by the amount of *extent*." +msgstr "" + +#: ../Doc/library/turtle.rst:470 +msgid "" +"As the circle is approximated by an inscribed regular polygon, *steps* " +"determines the number of steps to use. If not given, it will be calculated " +"automatically. May be used to draw regular polygons." +msgstr "" + +#: ../Doc/library/turtle.rst:495 +msgid "an integer >= 1 (if given)" +msgstr "" + +#: ../Doc/library/turtle.rst:496 +msgid "a colorstring or a numeric color tuple" +msgstr "" + +#: ../Doc/library/turtle.rst:498 +msgid "" +"Draw a circular dot with diameter *size*, using *color*. If *size* is not " +"given, the maximum of pensize+4 and 2*pensize is used." +msgstr "" + +#: ../Doc/library/turtle.rst:515 +msgid "" +"Stamp a copy of the turtle shape onto the canvas at the current turtle " +"position. Return a stamp_id for that stamp, which can be used to delete it " +"by calling ``clearstamp(stamp_id)``." +msgstr "" + +#: ../Doc/library/turtle.rst:529 +msgid "an integer, must be return value of previous :func:`stamp` call" +msgstr "" + +#: ../Doc/library/turtle.rst:532 +msgid "Delete stamp with given *stampid*." +msgstr "" + +#: ../Doc/library/turtle.rst:552 +msgid "" +"Delete all or first/last *n* of turtle's stamps. If *n* is None, delete all " +"stamps, if *n* > 0 delete first *n* stamps, else if *n* < 0 delete last *n* " +"stamps." +msgstr "" + +#: ../Doc/library/turtle.rst:575 +msgid "" +"Undo (repeatedly) the last turtle action(s). Number of available undo " +"actions is determined by the size of the undobuffer." +msgstr "" + +#: ../Doc/library/turtle.rst:589 +msgid "an integer in the range 0..10 or a speedstring (see below)" +msgstr "" + +#: ../Doc/library/turtle.rst:591 +msgid "" +"Set the turtle's speed to an integer value in the range 0..10. If no " +"argument is given, return current speed." +msgstr "" + +#: ../Doc/library/turtle.rst:594 +msgid "" +"If input is a number greater than 10 or smaller than 0.5, speed is set to " +"0. Speedstrings are mapped to speedvalues as follows:" +msgstr "" + +#: ../Doc/library/turtle.rst:597 +msgid "\"fastest\": 0" +msgstr "" + +#: ../Doc/library/turtle.rst:598 +msgid "\"fast\": 10" +msgstr "" + +#: ../Doc/library/turtle.rst:599 +msgid "\"normal\": 6" +msgstr "" + +#: ../Doc/library/turtle.rst:600 +msgid "\"slow\": 3" +msgstr "" + +#: ../Doc/library/turtle.rst:601 +msgid "\"slowest\": 1" +msgstr "" + +#: ../Doc/library/turtle.rst:603 +msgid "" +"Speeds from 1 to 10 enforce increasingly faster animation of line drawing " +"and turtle turning." +msgstr "" + +#: ../Doc/library/turtle.rst:606 +msgid "" +"Attention: *speed* = 0 means that *no* animation takes place. forward/back " +"makes turtle jump and likewise left/right make the turtle turn instantly." +msgstr "" + +#: ../Doc/library/turtle.rst:628 +msgid "" +"Return the turtle's current location (x,y) (as a :class:`Vec2D` vector)." +msgstr "" + +#: ../Doc/library/turtle.rst:638 ../Doc/library/turtle.rst:697 +msgid "a number or a pair/vector of numbers or a turtle instance" +msgstr "" + +#: ../Doc/library/turtle.rst:639 ../Doc/library/turtle.rst:698 +msgid "a number if *x* is a number, else ``None``" +msgstr "" + +#: ../Doc/library/turtle.rst:641 +msgid "" +"Return the angle between the line from turtle position to position specified " +"by (x,y), the vector or the other turtle. This depends on the turtle's " +"start orientation which depends on the mode - \"standard\"/\"world\" or " +"\"logo\")." +msgstr "" + +#: ../Doc/library/turtle.rst:654 +msgid "Return the turtle's x coordinate." +msgstr "" + +#: ../Doc/library/turtle.rst:669 +msgid "Return the turtle's y coordinate." +msgstr "" + +#: ../Doc/library/turtle.rst:684 +msgid "" +"Return the turtle's current heading (value depends on the turtle mode, see :" +"func:`mode`)." +msgstr "" + +#: ../Doc/library/turtle.rst:700 +msgid "" +"Return the distance from the turtle to (x,y), the given vector, or the given " +"other turtle, in turtle step units." +msgstr "" + +#: ../Doc/library/turtle.rst:717 +msgid "Settings for measurement" +msgstr "" + +#: ../Doc/library/turtle.rst:723 +msgid "" +"Set angle measurement units, i.e. set number of \"degrees\" for a full " +"circle. Default value is 360 degrees." +msgstr "" + +#: ../Doc/library/turtle.rst:745 +msgid "" +"Set the angle measurement units to radians. Equivalent to ``degrees(2*math." +"pi)``." +msgstr "" + +#: ../Doc/library/turtle.rst:774 +msgid "Pull the pen down -- drawing when moving." +msgstr "" + +#: ../Doc/library/turtle.rst:781 +msgid "Pull the pen up -- no drawing when moving." +msgstr "" + +#: ../Doc/library/turtle.rst:787 +msgid "a positive number" +msgstr "" + +#: ../Doc/library/turtle.rst:789 +msgid "" +"Set the line thickness to *width* or return it. If resizemode is set to " +"\"auto\" and turtleshape is a polygon, that polygon is drawn with the same " +"line thickness. If no argument is given, the current pensize is returned." +msgstr "" + +#: ../Doc/library/turtle.rst:802 +msgid "a dictionary with some or all of the below listed keys" +msgstr "" + +#: ../Doc/library/turtle.rst:803 +msgid "one or more keyword-arguments with the below listed keys as keywords" +msgstr "" + +#: ../Doc/library/turtle.rst:805 +msgid "" +"Return or set the pen's attributes in a \"pen-dictionary\" with the " +"following key/value pairs:" +msgstr "" + +#: ../Doc/library/turtle.rst:808 +msgid "\"shown\": True/False" +msgstr "" + +#: ../Doc/library/turtle.rst:809 +msgid "\"pendown\": True/False" +msgstr "" + +#: ../Doc/library/turtle.rst:810 +msgid "\"pencolor\": color-string or color-tuple" +msgstr "" + +#: ../Doc/library/turtle.rst:811 +msgid "\"fillcolor\": color-string or color-tuple" +msgstr "" + +#: ../Doc/library/turtle.rst:812 +msgid "\"pensize\": positive number" +msgstr "" + +#: ../Doc/library/turtle.rst:813 +msgid "\"speed\": number in range 0..10" +msgstr "" + +#: ../Doc/library/turtle.rst:814 +msgid "\"resizemode\": \"auto\" or \"user\" or \"noresize\"" +msgstr "" + +#: ../Doc/library/turtle.rst:815 +msgid "\"stretchfactor\": (positive number, positive number)" +msgstr "" + +#: ../Doc/library/turtle.rst:816 +msgid "\"outline\": positive number" +msgstr "" + +#: ../Doc/library/turtle.rst:817 +msgid "\"tilt\": number" +msgstr "" + +#: ../Doc/library/turtle.rst:819 +msgid "" +"This dictionary can be used as argument for a subsequent call to :func:`pen` " +"to restore the former pen-state. Moreover one or more of these attributes " +"can be provided as keyword-arguments. This can be used to set several pen " +"attributes in one statement." +msgstr "" + +#: ../Doc/library/turtle.rst:844 +msgid "Return ``True`` if pen is down, ``False`` if it's up." +msgstr "" + +#: ../Doc/library/turtle.rst:861 +msgid "Return or set the pencolor." +msgstr "" + +#: ../Doc/library/turtle.rst:863 ../Doc/library/turtle.rst:911 +msgid "Four input formats are allowed:" +msgstr "" + +#: ../Doc/library/turtle.rst:868 +msgid "``pencolor()``" +msgstr "" + +#: ../Doc/library/turtle.rst:866 +msgid "" +"Return the current pencolor as color specification string or as a tuple (see " +"example). May be used as input to another color/pencolor/fillcolor call." +msgstr "" + +#: ../Doc/library/turtle.rst:872 +msgid "``pencolor(colorstring)``" +msgstr "" + +#: ../Doc/library/turtle.rst:871 +msgid "" +"Set pencolor to *colorstring*, which is a Tk color specification string, " +"such as ``\"red\"``, ``\"yellow\"``, or ``\"#33cc8c\"``." +msgstr "" + +#: ../Doc/library/turtle.rst:877 +msgid "``pencolor((r, g, b))``" +msgstr "" + +#: ../Doc/library/turtle.rst:875 +msgid "" +"Set pencolor to the RGB color represented by the tuple of *r*, *g*, and " +"*b*. Each of *r*, *g*, and *b* must be in the range 0..colormode, where " +"colormode is either 1.0 or 255 (see :func:`colormode`)." +msgstr "" + +#: ../Doc/library/turtle.rst:884 +msgid "``pencolor(r, g, b)``" +msgstr "" + +#: ../Doc/library/turtle.rst:880 +msgid "" +"Set pencolor to the RGB color represented by *r*, *g*, and *b*. Each of " +"*r*, *g*, and *b* must be in the range 0..colormode." +msgstr "" + +#: ../Doc/library/turtle.rst:883 +msgid "" +"If turtleshape is a polygon, the outline of that polygon is drawn with the " +"newly set pencolor." +msgstr "" + +#: ../Doc/library/turtle.rst:909 +msgid "Return or set the fillcolor." +msgstr "" + +#: ../Doc/library/turtle.rst:916 +msgid "``fillcolor()``" +msgstr "" + +#: ../Doc/library/turtle.rst:914 +msgid "" +"Return the current fillcolor as color specification string, possibly in " +"tuple format (see example). May be used as input to another color/pencolor/" +"fillcolor call." +msgstr "" + +#: ../Doc/library/turtle.rst:920 +msgid "``fillcolor(colorstring)``" +msgstr "" + +#: ../Doc/library/turtle.rst:919 +msgid "" +"Set fillcolor to *colorstring*, which is a Tk color specification string, " +"such as ``\"red\"``, ``\"yellow\"``, or ``\"#33cc8c\"``." +msgstr "" + +#: ../Doc/library/turtle.rst:925 +msgid "``fillcolor((r, g, b))``" +msgstr "" + +#: ../Doc/library/turtle.rst:923 +msgid "" +"Set fillcolor to the RGB color represented by the tuple of *r*, *g*, and " +"*b*. Each of *r*, *g*, and *b* must be in the range 0..colormode, where " +"colormode is either 1.0 or 255 (see :func:`colormode`)." +msgstr "" + +#: ../Doc/library/turtle.rst:932 +msgid "``fillcolor(r, g, b)``" +msgstr "" + +#: ../Doc/library/turtle.rst:928 +msgid "" +"Set fillcolor to the RGB color represented by *r*, *g*, and *b*. Each of " +"*r*, *g*, and *b* must be in the range 0..colormode." +msgstr "" + +#: ../Doc/library/turtle.rst:931 +msgid "" +"If turtleshape is a polygon, the interior of that polygon is drawn with the " +"newly set fillcolor." +msgstr "" + +#: ../Doc/library/turtle.rst:952 +msgid "Return or set pencolor and fillcolor." +msgstr "" + +#: ../Doc/library/turtle.rst:954 +msgid "" +"Several input formats are allowed. They use 0 to 3 arguments as follows:" +msgstr "" + +#: ../Doc/library/turtle.rst:960 +msgid "``color()``" +msgstr "" + +#: ../Doc/library/turtle.rst:958 +msgid "" +"Return the current pencolor and the current fillcolor as a pair of color " +"specification strings or tuples as returned by :func:`pencolor` and :func:" +"`fillcolor`." +msgstr "" + +#: ../Doc/library/turtle.rst:964 +msgid "``color(colorstring)``, ``color((r,g,b))``, ``color(r,g,b)``" +msgstr "" + +#: ../Doc/library/turtle.rst:963 +msgid "" +"Inputs as in :func:`pencolor`, set both, fillcolor and pencolor, to the " +"given value." +msgstr "" + +#: ../Doc/library/turtle.rst:971 +msgid "" +"``color(colorstring1, colorstring2)``, ``color((r1,g1,b1), (r2,g2,b2))``" +msgstr "" + +#: ../Doc/library/turtle.rst:967 +msgid "" +"Equivalent to ``pencolor(colorstring1)`` and ``fillcolor(colorstring2)`` and " +"analogously if the other input format is used." +msgstr "" + +#: ../Doc/library/turtle.rst:970 +msgid "" +"If turtleshape is a polygon, outline and interior of that polygon is drawn " +"with the newly set colors." +msgstr "" + +#: ../Doc/library/turtle.rst:983 +msgid "See also: Screen method :func:`colormode`." +msgstr "" + +#: ../Doc/library/turtle.rst:996 +msgid "Return fillstate (``True`` if filling, ``False`` else)." +msgstr "" + +#: ../Doc/library/turtle.rst:1010 +msgid "To be called just before drawing a shape to be filled." +msgstr "" + +#: ../Doc/library/turtle.rst:1015 +msgid "Fill the shape drawn after the last call to :func:`begin_fill`." +msgstr "" + +#: ../Doc/library/turtle.rst:1030 +msgid "" +"Delete the turtle's drawings from the screen, re-center the turtle and set " +"variables to the default values." +msgstr "" + +#: ../Doc/library/turtle.rst:1050 +msgid "" +"Delete the turtle's drawings from the screen. Do not move turtle. State " +"and position of the turtle as well as drawings of other turtles are not " +"affected." +msgstr "" + +#: ../Doc/library/turtle.rst:1056 +msgid "object to be written to the TurtleScreen" +msgstr "" + +#: ../Doc/library/turtle.rst:1057 +msgid "True/False" +msgstr "" + +#: ../Doc/library/turtle.rst:1058 +msgid "one of the strings \"left\", \"center\" or right\"" +msgstr "" + +#: ../Doc/library/turtle.rst:1059 +msgid "a triple (fontname, fontsize, fonttype)" +msgstr "" + +#: ../Doc/library/turtle.rst:1061 +msgid "" +"Write text - the string representation of *arg* - at the current turtle " +"position according to *align* (\"left\", \"center\" or right\") and with the " +"given font. If *move* is true, the pen is moved to the bottom-right corner " +"of the text. By default, *move* is ``False``." +msgstr "" + +#: ../Doc/library/turtle.rst:1079 +msgid "" +"Make the turtle invisible. It's a good idea to do this while you're in the " +"middle of doing some complex drawing, because hiding the turtle speeds up " +"the drawing observably." +msgstr "" + +#: ../Doc/library/turtle.rst:1091 +msgid "Make the turtle visible." +msgstr "" + +#: ../Doc/library/turtle.rst:1100 +msgid "Return ``True`` if the Turtle is shown, ``False`` if it's hidden." +msgstr "" + +#: ../Doc/library/turtle.rst:1115 +msgid "a string which is a valid shapename" +msgstr "" + +#: ../Doc/library/turtle.rst:1117 +msgid "" +"Set turtle shape to shape with given *name* or, if name is not given, return " +"name of current shape. Shape with *name* must exist in the TurtleScreen's " +"shape dictionary. Initially there are the following polygon shapes: \"arrow" +"\", \"turtle\", \"circle\", \"square\", \"triangle\", \"classic\". To learn " +"about how to deal with shapes see Screen method :func:`register_shape`." +msgstr "" + +#: ../Doc/library/turtle.rst:1134 +msgid "one of the strings \"auto\", \"user\", \"noresize\"" +msgstr "" + +#: ../Doc/library/turtle.rst:1136 +msgid "" +"Set resizemode to one of the values: \"auto\", \"user\", \"noresize\". If " +"*rmode* is not given, return current resizemode. Different resizemodes have " +"the following effects:" +msgstr "" + +#: ../Doc/library/turtle.rst:1140 +msgid "" +"\"auto\": adapts the appearance of the turtle corresponding to the value of " +"pensize." +msgstr "" + +#: ../Doc/library/turtle.rst:1141 +msgid "" +"\"user\": adapts the appearance of the turtle according to the values of " +"stretchfactor and outlinewidth (outline), which are set by :func:`shapesize`." +msgstr "" + +#: ../Doc/library/turtle.rst:1144 +msgid "\"noresize\": no adaption of the turtle's appearance takes place." +msgstr "" + +#: ../Doc/library/turtle.rst:1146 +msgid "" +"resizemode(\"user\") is called by :func:`shapesize` when used with arguments." +msgstr "" + +#: ../Doc/library/turtle.rst:1160 ../Doc/library/turtle.rst:1161 +#: ../Doc/library/turtle.rst:1162 +msgid "positive number" +msgstr "" + +#: ../Doc/library/turtle.rst:1164 +msgid "" +"Return or set the pen's attributes x/y-stretchfactors and/or outline. Set " +"resizemode to \"user\". If and only if resizemode is set to \"user\", the " +"turtle will be displayed stretched according to its stretchfactors: " +"*stretch_wid* is stretchfactor perpendicular to its orientation, " +"*stretch_len* is stretchfactor in direction of its orientation, *outline* " +"determines the width of the shapes's outline." +msgstr "" + +#: ../Doc/library/turtle.rst:1186 ../Doc/library/turtle.rst:1811 +#: ../Doc/library/turtle.rst:1812 ../Doc/library/turtle.rst:1813 +msgid "number (optional)" +msgstr "" + +#: ../Doc/library/turtle.rst:1188 +msgid "" +"Set or return the current shearfactor. Shear the turtleshape according to " +"the given shearfactor shear, which is the tangent of the shear angle. Do " +"*not* change the turtle's heading (direction of movement). If shear is not " +"given: return the current shearfactor, i. e. the tangent of the shear angle, " +"by which lines parallel to the heading of the turtle are sheared." +msgstr "" + +#: ../Doc/library/turtle.rst:1208 +msgid "" +"Rotate the turtleshape by *angle* from its current tilt-angle, but do *not* " +"change the turtle's heading (direction of movement)." +msgstr "" + +#: ../Doc/library/turtle.rst:1226 +msgid "" +"Rotate the turtleshape to point in the direction specified by *angle*, " +"regardless of its current tilt-angle. *Do not* change the turtle's heading " +"(direction of movement)." +msgstr "" + +#: ../Doc/library/turtle.rst:1245 ../Doc/library/turtle.rst:1267 +#: ../Doc/library/turtle.rst:1268 ../Doc/library/turtle.rst:1269 +#: ../Doc/library/turtle.rst:1270 +msgid "a number (optional)" +msgstr "" + +#: ../Doc/library/turtle.rst:1247 +msgid "" +"Set or return the current tilt-angle. If angle is given, rotate the " +"turtleshape to point in the direction specified by angle, regardless of its " +"current tilt-angle. Do *not* change the turtle's heading (direction of " +"movement). If angle is not given: return the current tilt-angle, i. e. the " +"angle between the orientation of the turtleshape and the heading of the " +"turtle (its direction of movement)." +msgstr "" + +#: ../Doc/library/turtle.rst:1272 +msgid "Set or return the current transformation matrix of the turtle shape." +msgstr "" + +#: ../Doc/library/turtle.rst:1274 +msgid "" +"If none of the matrix elements are given, return the transformation matrix " +"as a tuple of 4 elements. Otherwise set the given elements and transform the " +"turtleshape according to the matrix consisting of first row t11, t12 and " +"second row t21, 22. The determinant t11 * t22 - t12 * t21 must not be zero, " +"otherwise an error is raised. Modify stretchfactor, shearfactor and " +"tiltangle according to the given matrix." +msgstr "" + +#: ../Doc/library/turtle.rst:1295 +msgid "" +"Return the current shape polygon as tuple of coordinate pairs. This can be " +"used to define a new shape or components of a compound shape." +msgstr "" + +#: ../Doc/library/turtle.rst:1311 ../Doc/library/turtle.rst:1332 +#: ../Doc/library/turtle.rst:1356 ../Doc/library/turtle.rst:1737 +msgid "" +"a function with two arguments which will be called with the coordinates of " +"the clicked point on the canvas" +msgstr "" + +#: ../Doc/library/turtle.rst:1313 ../Doc/library/turtle.rst:1334 +#: ../Doc/library/turtle.rst:1358 ../Doc/library/turtle.rst:1739 +msgid "number of the mouse-button, defaults to 1 (left mouse button)" +msgstr "" + +#: ../Doc/library/turtle.rst:1314 ../Doc/library/turtle.rst:1335 +#: ../Doc/library/turtle.rst:1359 ../Doc/library/turtle.rst:1740 +msgid "" +"``True`` or ``False`` -- if ``True``, a new binding will be added, otherwise " +"it will replace a former binding" +msgstr "" + +#: ../Doc/library/turtle.rst:1317 +msgid "" +"Bind *fun* to mouse-click events on this turtle. If *fun* is ``None``, " +"existing bindings are removed. Example for the anonymous turtle, i.e. the " +"procedural way:" +msgstr "" + +#: ../Doc/library/turtle.rst:1338 +msgid "" +"Bind *fun* to mouse-button-release events on this turtle. If *fun* is " +"``None``, existing bindings are removed." +msgstr "" + +#: ../Doc/library/turtle.rst:1362 +msgid "" +"Bind *fun* to mouse-move events on this turtle. If *fun* is ``None``, " +"existing bindings are removed." +msgstr "" + +#: ../Doc/library/turtle.rst:1365 +msgid "" +"Remark: Every sequence of mouse-move-events on a turtle is preceded by a " +"mouse-click event on that turtle." +msgstr "" + +#: ../Doc/library/turtle.rst:1372 +msgid "" +"Subsequently, clicking and dragging the Turtle will move it across the " +"screen thereby producing handdrawings (if pen is down)." +msgstr "" + +#: ../Doc/library/turtle.rst:1381 +msgid "" +"Start recording the vertices of a polygon. Current turtle position is first " +"vertex of polygon." +msgstr "" + +#: ../Doc/library/turtle.rst:1387 +msgid "" +"Stop recording the vertices of a polygon. Current turtle position is last " +"vertex of polygon. This will be connected with the first vertex." +msgstr "" + +#: ../Doc/library/turtle.rst:1393 +msgid "Return the last recorded polygon." +msgstr "" + +#: ../Doc/library/turtle.rst:1411 +msgid "" +"Create and return a clone of the turtle with same position, heading and " +"turtle properties." +msgstr "" + +#: ../Doc/library/turtle.rst:1423 +msgid "" +"Return the Turtle object itself. Only reasonable use: as a function to " +"return the \"anonymous turtle\":" +msgstr "" + +#: ../Doc/library/turtle.rst:1436 +msgid "" +"Return the :class:`TurtleScreen` object the turtle is drawing on. " +"TurtleScreen methods can then be called for that object." +msgstr "" + +#: ../Doc/library/turtle.rst:1449 +msgid "an integer or ``None``" +msgstr "" + +#: ../Doc/library/turtle.rst:1451 +msgid "" +"Set or disable undobuffer. If *size* is an integer an empty undobuffer of " +"given size is installed. *size* gives the maximum number of turtle actions " +"that can be undone by the :func:`undo` method/function. If *size* is " +"``None``, the undobuffer is disabled." +msgstr "" + +#: ../Doc/library/turtle.rst:1463 +msgid "Return number of entries in the undobuffer." +msgstr "" + +#: ../Doc/library/turtle.rst:1475 +msgid "Compound shapes" +msgstr "" + +#: ../Doc/library/turtle.rst:1477 +msgid "" +"To use compound turtle shapes, which consist of several polygons of " +"different color, you must use the helper class :class:`Shape` explicitly as " +"described below:" +msgstr "" + +#: ../Doc/library/turtle.rst:1481 +msgid "Create an empty Shape object of type \"compound\"." +msgstr "" + +#: ../Doc/library/turtle.rst:1482 +msgid "" +"Add as many components to this object as desired, using the :meth:" +"`addcomponent` method." +msgstr "" + +#: ../Doc/library/turtle.rst:1495 +msgid "Now add the Shape to the Screen's shapelist and use it:" +msgstr "" + +#: ../Doc/library/turtle.rst:1505 +msgid "" +"The :class:`Shape` class is used internally by the :func:`register_shape` " +"method in different ways. The application programmer has to deal with the " +"Shape class *only* when using compound shapes like shown above!" +msgstr "" + +#: ../Doc/library/turtle.rst:1511 +msgid "Methods of TurtleScreen/Screen and corresponding functions" +msgstr "" + +#: ../Doc/library/turtle.rst:1513 +msgid "" +"Most of the examples in this section refer to a TurtleScreen instance called " +"``screen``." +msgstr "" + +#: ../Doc/library/turtle.rst:1526 +msgid "" +"a color string or three numbers in the range 0..colormode or a 3-tuple of " +"such numbers" +msgstr "" + +#: ../Doc/library/turtle.rst:1530 +msgid "Set or return background color of the TurtleScreen." +msgstr "" + +#: ../Doc/library/turtle.rst:1544 +msgid "a string, name of a gif-file or ``\"nopic\"``, or ``None``" +msgstr "" + +#: ../Doc/library/turtle.rst:1546 +msgid "" +"Set background image or return name of current backgroundimage. If " +"*picname* is a filename, set the corresponding image as background. If " +"*picname* is ``\"nopic\"``, delete background image, if present. If " +"*picname* is ``None``, return the filename of the current backgroundimage. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1561 +msgid "" +"Delete all drawings and all turtles from the TurtleScreen. Reset the now " +"empty TurtleScreen to its initial state: white background, no background " +"image, no event bindings and tracing on." +msgstr "" + +#: ../Doc/library/turtle.rst:1566 +msgid "" +"This TurtleScreen method is available as a global function only under the " +"name ``clearscreen``. The global function ``clear`` is a different one " +"derived from the Turtle method ``clear``." +msgstr "" + +#: ../Doc/library/turtle.rst:1574 +msgid "Reset all Turtles on the Screen to their initial state." +msgstr "" + +#: ../Doc/library/turtle.rst:1577 +msgid "" +"This TurtleScreen method is available as a global function only under the " +"name ``resetscreen``. The global function ``reset`` is another one derived " +"from the Turtle method ``reset``." +msgstr "" + +#: ../Doc/library/turtle.rst:1584 +msgid "positive integer, new width of canvas in pixels" +msgstr "" + +#: ../Doc/library/turtle.rst:1585 +msgid "positive integer, new height of canvas in pixels" +msgstr "" + +#: ../Doc/library/turtle.rst:1586 +msgid "colorstring or color-tuple, new background color" +msgstr "" + +#: ../Doc/library/turtle.rst:1588 +msgid "" +"If no arguments are given, return current (canvaswidth, canvasheight). Else " +"resize the canvas the turtles are drawing on. Do not alter the drawing " +"window. To observe hidden parts of the canvas, use the scrollbars. With " +"this method, one can make visible those parts of a drawing which were " +"outside the canvas before." +msgstr "" + +#: ../Doc/library/turtle.rst:1600 +msgid "e.g. to search for an erroneously escaped turtle ;-)" +msgstr "" + +#: ../Doc/library/turtle.rst:1605 +msgid "a number, x-coordinate of lower left corner of canvas" +msgstr "" + +#: ../Doc/library/turtle.rst:1606 +msgid "a number, y-coordinate of lower left corner of canvas" +msgstr "" + +#: ../Doc/library/turtle.rst:1607 +msgid "a number, x-coordinate of upper right corner of canvas" +msgstr "" + +#: ../Doc/library/turtle.rst:1608 +msgid "a number, y-coordinate of upper right corner of canvas" +msgstr "" + +#: ../Doc/library/turtle.rst:1610 +msgid "" +"Set up user-defined coordinate system and switch to mode \"world\" if " +"necessary. This performs a ``screen.reset()``. If mode \"world\" is " +"already active, all drawings are redrawn according to the new coordinates." +msgstr "" + +#: ../Doc/library/turtle.rst:1614 +msgid "" +"**ATTENTION**: in user-defined coordinate systems angles may appear " +"distorted." +msgstr "" + +#: ../Doc/library/turtle.rst:1640 +msgid "positive integer" +msgstr "" + +#: ../Doc/library/turtle.rst:1642 +msgid "" +"Set or return the drawing *delay* in milliseconds. (This is approximately " +"the time interval between two consecutive canvas updates.) The longer the " +"drawing delay, the slower the animation." +msgstr "" + +#: ../Doc/library/turtle.rst:1646 +msgid "Optional argument:" +msgstr "" + +#: ../Doc/library/turtle.rst:1659 ../Doc/library/turtle.rst:1660 +msgid "nonnegative integer" +msgstr "" + +#: ../Doc/library/turtle.rst:1662 +msgid "" +"Turn turtle animation on/off and set delay for update drawings. If *n* is " +"given, only each n-th regular screen update is really performed. (Can be " +"used to accelerate the drawing of complex graphics.) When called without " +"arguments, returns the currently stored value of n. Second argument sets " +"delay value (see :func:`delay`)." +msgstr "" + +#: ../Doc/library/turtle.rst:1681 +msgid "Perform a TurtleScreen update. To be used when tracer is turned off." +msgstr "" + +#: ../Doc/library/turtle.rst:1683 +msgid "See also the RawTurtle/Turtle method :func:`speed`." +msgstr "" + +#: ../Doc/library/turtle.rst:1691 +msgid "" +"Set focus on TurtleScreen (in order to collect key-events). Dummy arguments " +"are provided in order to be able to pass :func:`listen` to the onclick " +"method." +msgstr "" + +#: ../Doc/library/turtle.rst:1698 ../Doc/library/turtle.rst:1717 +msgid "a function with no arguments or ``None``" +msgstr "" + +#: ../Doc/library/turtle.rst:1699 ../Doc/library/turtle.rst:1718 +msgid "a string: key (e.g. \"a\") or key-symbol (e.g. \"space\")" +msgstr "" + +#: ../Doc/library/turtle.rst:1701 +msgid "" +"Bind *fun* to key-release event of key. If *fun* is ``None``, event " +"bindings are removed. Remark: in order to be able to register key-events, " +"TurtleScreen must have the focus. (See method :func:`listen`.)" +msgstr "" + +#: ../Doc/library/turtle.rst:1720 +msgid "" +"Bind *fun* to key-press event of key if key is given, or to any key-press-" +"event if no key is given. Remark: in order to be able to register key-" +"events, TurtleScreen must have focus. (See method :func:`listen`.)" +msgstr "" + +#: ../Doc/library/turtle.rst:1743 +msgid "" +"Bind *fun* to mouse-click events on this screen. If *fun* is ``None``, " +"existing bindings are removed." +msgstr "" + +#: ../Doc/library/turtle.rst:1746 +msgid "" +"Example for a TurtleScreen instance named ``screen`` and a Turtle instance " +"named turtle:" +msgstr "" + +#: ../Doc/library/turtle.rst:1756 +msgid "" +"This TurtleScreen method is available as a global function only under the " +"name ``onscreenclick``. The global function ``onclick`` is another one " +"derived from the Turtle method ``onclick``." +msgstr "" + +#: ../Doc/library/turtle.rst:1763 +msgid "a function with no arguments" +msgstr "" + +#: ../Doc/library/turtle.rst:1764 +msgid "a number >= 0" +msgstr "" + +#: ../Doc/library/turtle.rst:1766 +msgid "Install a timer that calls *fun* after *t* milliseconds." +msgstr "" + +#: ../Doc/library/turtle.rst:1783 +msgid "" +"Starts event loop - calling Tkinter's mainloop function. Must be the last " +"statement in a turtle graphics program. Must *not* be used if a script is " +"run from within IDLE in -n mode (No subprocess) - for interactive use of " +"turtle graphics. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1799 +msgid "" +"Pop up a dialog window for input of a string. Parameter title is the title " +"of the dialog window, propmt is a text mostly describing what information to " +"input. Return the string input. If the dialog is canceled, return None. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1815 +msgid "" +"Pop up a dialog window for input of a number. title is the title of the " +"dialog window, prompt is a text mostly describing what numerical information " +"to input. default: default value, minval: minimum value for input, maxval: " +"maximum value for input The number input must be in the range minval .. " +"maxval if these are given. If not, a hint is issued and the dialog remains " +"open for correction. Return the number input. If the dialog is canceled, " +"return None. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1832 +msgid "one of the strings \"standard\", \"logo\" or \"world\"" +msgstr "" + +#: ../Doc/library/turtle.rst:1834 +msgid "" +"Set turtle mode (\"standard\", \"logo\" or \"world\") and perform reset. If " +"mode is not given, current mode is returned." +msgstr "" + +#: ../Doc/library/turtle.rst:1837 +msgid "" +"Mode \"standard\" is compatible with old :mod:`turtle`. Mode \"logo\" is " +"compatible with most Logo turtle graphics. Mode \"world\" uses user-defined " +"\"world coordinates\". **Attention**: in this mode angles appear distorted " +"if ``x/y`` unit-ratio doesn't equal 1." +msgstr "" + +#: ../Doc/library/turtle.rst:1843 +msgid "Initial turtle heading" +msgstr "" + +#: ../Doc/library/turtle.rst:1843 +msgid "positive angles" +msgstr "" + +#: ../Doc/library/turtle.rst:1845 +msgid "\"standard\"" +msgstr "" + +#: ../Doc/library/turtle.rst:1845 +msgid "to the right (east)" +msgstr "" + +#: ../Doc/library/turtle.rst:1845 +msgid "counterclockwise" +msgstr "" + +#: ../Doc/library/turtle.rst:1846 +msgid "\"logo\"" +msgstr "" + +#: ../Doc/library/turtle.rst:1846 +msgid "upward (north)" +msgstr "" + +#: ../Doc/library/turtle.rst:1846 +msgid "clockwise" +msgstr "" + +#: ../Doc/library/turtle.rst:1858 +msgid "one of the values 1.0 or 255" +msgstr "" + +#: ../Doc/library/turtle.rst:1860 +msgid "" +"Return the colormode or set it to 1.0 or 255. Subsequently *r*, *g*, *b* " +"values of color triples have to be in the range 0..\\ *cmode*." +msgstr "" + +#: ../Doc/library/turtle.rst:1880 +msgid "" +"Return the Canvas of this TurtleScreen. Useful for insiders who know what " +"to do with a Tkinter Canvas." +msgstr "" + +#: ../Doc/library/turtle.rst:1892 +msgid "Return a list of names of all currently available turtle shapes." +msgstr "" + +#: ../Doc/library/turtle.rst:1903 +msgid "There are three different ways to call this function:" +msgstr "" + +#: ../Doc/library/turtle.rst:1905 +msgid "" +"*name* is the name of a gif-file and *shape* is ``None``: Install the " +"corresponding image shape. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1911 +msgid "" +"Image shapes *do not* rotate when turning the turtle, so they do not display " +"the heading of the turtle!" +msgstr "" + +#: ../Doc/library/turtle.rst:1914 +msgid "" +"*name* is an arbitrary string and *shape* is a tuple of pairs of " +"coordinates: Install the corresponding polygon shape." +msgstr "" + +#: ../Doc/library/turtle.rst:1921 +msgid "" +"*name* is an arbitrary string and shape is a (compound) :class:`Shape` " +"object: Install the corresponding compound shape." +msgstr "" + +#: ../Doc/library/turtle.rst:1924 +msgid "" +"Add a turtle shape to TurtleScreen's shapelist. Only thusly registered " +"shapes can be used by issuing the command ``shape(shapename)``." +msgstr "" + +#: ../Doc/library/turtle.rst:1930 +msgid "Return the list of turtles on the screen." +msgstr "" + +#: ../Doc/library/turtle.rst:1940 +msgid "Return the height of the turtle window. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1948 +msgid "Return the width of the turtle window. ::" +msgstr "" + +#: ../Doc/library/turtle.rst:1957 +msgid "Methods specific to Screen, not inherited from TurtleScreen" +msgstr "" + +#: ../Doc/library/turtle.rst:1961 +msgid "Shut the turtlegraphics window." +msgstr "" + +#: ../Doc/library/turtle.rst:1966 +msgid "Bind bye() method to mouse clicks on the Screen." +msgstr "" + +#: ../Doc/library/turtle.rst:1969 +msgid "" +"If the value \"using_IDLE\" in the configuration dictionary is ``False`` " +"(default value), also enter mainloop. Remark: If IDLE with the ``-n`` " +"switch (no subprocess) is used, this value should be set to ``True`` in :" +"file:`turtle.cfg`. In this case IDLE's own mainloop is active also for the " +"client script." +msgstr "" + +#: ../Doc/library/turtle.rst:1978 +msgid "" +"Set the size and position of the main window. Default values of arguments " +"are stored in the configuration dictionary and can be changed via a :file:" +"`turtle.cfg` file." +msgstr "" + +#: ../Doc/library/turtle.rst:1982 +msgid "" +"if an integer, a size in pixels, if a float, a fraction of the screen; " +"default is 50% of screen" +msgstr "" + +#: ../Doc/library/turtle.rst:1984 +msgid "" +"if an integer, the height in pixels, if a float, a fraction of the screen; " +"default is 75% of screen" +msgstr "" + +#: ../Doc/library/turtle.rst:1986 +msgid "" +"if positive, starting position in pixels from the left edge of the screen, " +"if negative from the right edge, if None, center window horizontally" +msgstr "" + +#: ../Doc/library/turtle.rst:1989 +msgid "" +"if positive, starting position in pixels from the top edge of the screen, if " +"negative from the bottom edge, if None, center window vertically" +msgstr "" + +#: ../Doc/library/turtle.rst:2003 +msgid "a string that is shown in the titlebar of the turtle graphics window" +msgstr "" + +#: ../Doc/library/turtle.rst:2006 +msgid "Set title of turtle window to *titlestring*." +msgstr "" + +#: ../Doc/library/turtle.rst:2014 +msgid "Public classes" +msgstr "" + +#: ../Doc/library/turtle.rst:2020 +msgid "" +"a :class:`tkinter.Canvas`, a :class:`ScrolledCanvas` or a :class:" +"`TurtleScreen`" +msgstr "" + +#: ../Doc/library/turtle.rst:2023 +msgid "" +"Create a turtle. The turtle has all methods described above as \"methods of " +"Turtle/RawTurtle\"." +msgstr "" + +#: ../Doc/library/turtle.rst:2029 +msgid "" +"Subclass of RawTurtle, has the same interface but draws on a default :class:" +"`Screen` object created automatically when needed for the first time." +msgstr "" + +#: ../Doc/library/turtle.rst:2035 +msgid "a :class:`tkinter.Canvas`" +msgstr "" + +#: ../Doc/library/turtle.rst:2037 +msgid "" +"Provides screen oriented methods like :func:`setbg` etc. that are described " +"above." +msgstr "" + +#: ../Doc/library/turtle.rst:2042 +msgid "" +"Subclass of TurtleScreen, with :ref:`four methods added `." +msgstr "" + +#: ../Doc/library/turtle.rst:2047 +msgid "" +"some Tkinter widget to contain the ScrolledCanvas, i.e. a Tkinter-canvas " +"with scrollbars added" +msgstr "" + +#: ../Doc/library/turtle.rst:2050 +msgid "" +"Used by class Screen, which thus automatically provides a ScrolledCanvas as " +"playground for the turtles." +msgstr "" + +#: ../Doc/library/turtle.rst:2055 +msgid "one of the strings \"polygon\", \"image\", \"compound\"" +msgstr "" + +#: ../Doc/library/turtle.rst:2057 +msgid "" +"Data structure modeling shapes. The pair ``(type_, data)`` must follow this " +"specification:" +msgstr "" + +#: ../Doc/library/turtle.rst:2062 +msgid "*type_*" +msgstr "" + +#: ../Doc/library/turtle.rst:2062 +msgid "*data*" +msgstr "" + +#: ../Doc/library/turtle.rst:2064 +msgid "\"polygon\"" +msgstr "" + +#: ../Doc/library/turtle.rst:2064 +msgid "a polygon-tuple, i.e. a tuple of pairs of coordinates" +msgstr "" + +#: ../Doc/library/turtle.rst:2065 +msgid "\"image\"" +msgstr "" + +#: ../Doc/library/turtle.rst:2065 +msgid "an image (in this form only used internally!)" +msgstr "" + +#: ../Doc/library/turtle.rst:2066 +msgid "\"compound\"" +msgstr "" + +#: ../Doc/library/turtle.rst:2066 +msgid "" +"``None`` (a compound shape has to be constructed using the :meth:" +"`addcomponent` method)" +msgstr "" + +#: ../Doc/library/turtle.rst:2072 +msgid "a polygon, i.e. a tuple of pairs of numbers" +msgstr "" + +#: ../Doc/library/turtle.rst:2073 +msgid "a color the *poly* will be filled with" +msgstr "" + +#: ../Doc/library/turtle.rst:2074 +msgid "a color for the poly's outline (if given)" +msgstr "" + +#: ../Doc/library/turtle.rst:2085 +msgid "See :ref:`compoundshapes`." +msgstr "" + +#: ../Doc/library/turtle.rst:2090 +msgid "" +"A two-dimensional vector class, used as a helper class for implementing " +"turtle graphics. May be useful for turtle graphics programs too. Derived " +"from tuple, so a vector is a tuple!" +msgstr "" + +#: ../Doc/library/turtle.rst:2094 +msgid "Provides (for *a*, *b* vectors, *k* number):" +msgstr "" + +#: ../Doc/library/turtle.rst:2096 +msgid "``a + b`` vector addition" +msgstr "" + +#: ../Doc/library/turtle.rst:2097 +msgid "``a - b`` vector subtraction" +msgstr "" + +#: ../Doc/library/turtle.rst:2098 +msgid "``a * b`` inner product" +msgstr "" + +#: ../Doc/library/turtle.rst:2099 +msgid "``k * a`` and ``a * k`` multiplication with scalar" +msgstr "" + +#: ../Doc/library/turtle.rst:2100 +msgid "``abs(a)`` absolute value of a" +msgstr "" + +#: ../Doc/library/turtle.rst:2101 +msgid "``a.rotate(angle)`` rotation" +msgstr "" + +#: ../Doc/library/turtle.rst:2105 +msgid "Help and configuration" +msgstr "" + +#: ../Doc/library/turtle.rst:2108 +msgid "How to use help" +msgstr "" + +#: ../Doc/library/turtle.rst:2110 +msgid "" +"The public methods of the Screen and Turtle classes are documented " +"extensively via docstrings. So these can be used as online-help via the " +"Python help facilities:" +msgstr "" + +#: ../Doc/library/turtle.rst:2114 +msgid "" +"When using IDLE, tooltips show the signatures and first lines of the " +"docstrings of typed in function-/method calls." +msgstr "" + +#: ../Doc/library/turtle.rst:2117 +msgid "Calling :func:`help` on methods or functions displays the docstrings::" +msgstr "" + +#: ../Doc/library/turtle.rst:2148 +msgid "" +"The docstrings of the functions which are derived from methods have a " +"modified form::" +msgstr "" + +#: ../Doc/library/turtle.rst:2182 +msgid "" +"These modified docstrings are created automatically together with the " +"function definitions that are derived from the methods at import time." +msgstr "" + +#: ../Doc/library/turtle.rst:2187 +msgid "Translation of docstrings into different languages" +msgstr "" + +#: ../Doc/library/turtle.rst:2189 +msgid "" +"There is a utility to create a dictionary the keys of which are the method " +"names and the values of which are the docstrings of the public methods of " +"the classes Screen and Turtle." +msgstr "" + +#: ../Doc/library/turtle.rst:2195 +msgid "a string, used as filename" +msgstr "" + +#: ../Doc/library/turtle.rst:2197 +msgid "" +"Create and write docstring-dictionary to a Python script with the given " +"filename. This function has to be called explicitly (it is not used by the " +"turtle graphics classes). The docstring dictionary will be written to the " +"Python script :file:`{filename}.py`. It is intended to serve as a template " +"for translation of the docstrings into different languages." +msgstr "" + +#: ../Doc/library/turtle.rst:2203 +msgid "" +"If you (or your students) want to use :mod:`turtle` with online help in your " +"native language, you have to translate the docstrings and save the resulting " +"file as e.g. :file:`turtle_docstringdict_german.py`." +msgstr "" + +#: ../Doc/library/turtle.rst:2207 +msgid "" +"If you have an appropriate entry in your :file:`turtle.cfg` file this " +"dictionary will be read in at import time and will replace the original " +"English docstrings." +msgstr "" + +#: ../Doc/library/turtle.rst:2210 +msgid "" +"At the time of this writing there are docstring dictionaries in German and " +"in Italian. (Requests please to glingl@aon.at.)" +msgstr "" + +#: ../Doc/library/turtle.rst:2216 +msgid "How to configure Screen and Turtles" +msgstr "" + +#: ../Doc/library/turtle.rst:2218 +msgid "" +"The built-in default configuration mimics the appearance and behaviour of " +"the old turtle module in order to retain best possible compatibility with it." +msgstr "" + +#: ../Doc/library/turtle.rst:2221 +msgid "" +"If you want to use a different configuration which better reflects the " +"features of this module or which better fits to your needs, e.g. for use in " +"a classroom, you can prepare a configuration file ``turtle.cfg`` which will " +"be read at import time and modify the configuration according to its " +"settings." +msgstr "" + +#: ../Doc/library/turtle.rst:2226 +msgid "" +"The built in configuration would correspond to the following turtle.cfg::" +msgstr "" + +#: ../Doc/library/turtle.rst:2249 +msgid "Short explanation of selected entries:" +msgstr "" + +#: ../Doc/library/turtle.rst:2251 +msgid "" +"The first four lines correspond to the arguments of the :meth:`Screen.setup` " +"method." +msgstr "" + +#: ../Doc/library/turtle.rst:2253 +msgid "" +"Line 5 and 6 correspond to the arguments of the method :meth:`Screen." +"screensize`." +msgstr "" + +#: ../Doc/library/turtle.rst:2255 +msgid "" +"*shape* can be any of the built-in shapes, e.g: arrow, turtle, etc. For " +"more info try ``help(shape)``." +msgstr "" + +#: ../Doc/library/turtle.rst:2257 +msgid "" +"If you want to use no fillcolor (i.e. make the turtle transparent), you have " +"to write ``fillcolor = \"\"`` (but all nonempty strings must not have quotes " +"in the cfg-file)." +msgstr "" + +#: ../Doc/library/turtle.rst:2260 +msgid "" +"If you want to reflect the turtle its state, you have to use ``resizemode = " +"auto``." +msgstr "" + +#: ../Doc/library/turtle.rst:2262 +msgid "" +"If you set e.g. ``language = italian`` the docstringdict :file:" +"`turtle_docstringdict_italian.py` will be loaded at import time (if present " +"on the import path, e.g. in the same directory as :mod:`turtle`." +msgstr "" + +#: ../Doc/library/turtle.rst:2265 +msgid "" +"The entries *exampleturtle* and *examplescreen* define the names of these " +"objects as they occur in the docstrings. The transformation of method-" +"docstrings to function-docstrings will delete these names from the " +"docstrings." +msgstr "" + +#: ../Doc/library/turtle.rst:2269 +msgid "" +"*using_IDLE*: Set this to ``True`` if you regularly work with IDLE and its -" +"n switch (\"no subprocess\"). This will prevent :func:`exitonclick` to " +"enter the mainloop." +msgstr "" + +#: ../Doc/library/turtle.rst:2273 +msgid "" +"There can be a :file:`turtle.cfg` file in the directory where :mod:`turtle` " +"is stored and an additional one in the current working directory. The " +"latter will override the settings of the first one." +msgstr "" + +#: ../Doc/library/turtle.rst:2277 +msgid "" +"The :file:`Lib/turtledemo` directory contains a :file:`turtle.cfg` file. " +"You can study it as an example and see its effects when running the demos " +"(preferably not from within the demo-viewer)." +msgstr "" + +#: ../Doc/library/turtle.rst:2283 +msgid ":mod:`turtledemo` --- Demo scripts" +msgstr "" + +#: ../Doc/library/turtle.rst:2288 +msgid "" +"The :mod:`turtledemo` package includes a set of demo scripts. These scripts " +"can be run and viewed using the supplied demo viewer as follows::" +msgstr "" + +#: ../Doc/library/turtle.rst:2293 +msgid "" +"Alternatively, you can run the demo scripts individually. For example, ::" +msgstr "" + +#: ../Doc/library/turtle.rst:2297 +msgid "The :mod:`turtledemo` package directory contains:" +msgstr "" + +#: ../Doc/library/turtle.rst:2299 +msgid "" +"A demo viewer :file:`__main__.py` which can be used to view the sourcecode " +"of the scripts and run them at the same time." +msgstr "" + +#: ../Doc/library/turtle.rst:2301 +msgid "" +"Multiple scripts demonstrating different features of the :mod:`turtle` " +"module. Examples can be accessed via the Examples menu. They can also be " +"run standalone." +msgstr "" + +#: ../Doc/library/turtle.rst:2304 +msgid "" +"A :file:`turtle.cfg` file which serves as an example of how to write and use " +"such files." +msgstr "" + +#: ../Doc/library/turtle.rst:2307 +msgid "The demo scripts are:" +msgstr "" + +#: ../Doc/library/turtle.rst:2314 +msgid "bytedesign" +msgstr "" + +#: ../Doc/library/turtle.rst:2314 +msgid "complex classical turtle graphics pattern" +msgstr "" + +#: ../Doc/library/turtle.rst:2314 +msgid ":func:`tracer`, delay, :func:`update`" +msgstr "" + +#: ../Doc/library/turtle.rst:2317 +msgid "chaos" +msgstr "" + +#: ../Doc/library/turtle.rst:2317 +msgid "" +"graphs Verhulst dynamics, shows that computer's computations can generate " +"results sometimes against the common sense expectations" +msgstr "" + +#: ../Doc/library/turtle.rst:2317 +msgid "world coordinates" +msgstr "" + +#: ../Doc/library/turtle.rst:2323 +msgid "clock" +msgstr "" + +#: ../Doc/library/turtle.rst:2323 +msgid "analog clock showing time of your computer" +msgstr "" + +#: ../Doc/library/turtle.rst:2323 +msgid "turtles as clock's hands, ontimer" +msgstr "" + +#: ../Doc/library/turtle.rst:2326 +msgid "colormixer" +msgstr "" + +#: ../Doc/library/turtle.rst:2326 +msgid "experiment with r, g, b" +msgstr "" + +#: ../Doc/library/turtle.rst:2328 +msgid "forest" +msgstr "" + +#: ../Doc/library/turtle.rst:2328 +msgid "3 breadth-first trees" +msgstr "" + +#: ../Doc/library/turtle.rst:2328 +msgid "randomization" +msgstr "" + +#: ../Doc/library/turtle.rst:2330 +msgid "fractalcurves" +msgstr "" + +#: ../Doc/library/turtle.rst:2330 +msgid "Hilbert & Koch curves" +msgstr "" + +#: ../Doc/library/turtle.rst:2330 +msgid "recursion" +msgstr "" + +#: ../Doc/library/turtle.rst:2332 +msgid "lindenmayer" +msgstr "" + +#: ../Doc/library/turtle.rst:2332 +msgid "ethnomathematics (indian kolams)" +msgstr "" + +#: ../Doc/library/turtle.rst:2332 +msgid "L-System" +msgstr "" + +#: ../Doc/library/turtle.rst:2335 +msgid "minimal_hanoi" +msgstr "" + +#: ../Doc/library/turtle.rst:2335 +msgid "Towers of Hanoi" +msgstr "" + +#: ../Doc/library/turtle.rst:2335 +msgid "Rectangular Turtles as Hanoi discs (shape, shapesize)" +msgstr "" + +#: ../Doc/library/turtle.rst:2339 +msgid "nim" +msgstr "" + +#: ../Doc/library/turtle.rst:2339 +msgid "" +"play the classical nim game with three heaps of sticks against the computer." +msgstr "" + +#: ../Doc/library/turtle.rst:2339 +msgid "turtles as nimsticks, event driven (mouse, keyboard)" +msgstr "" + +#: ../Doc/library/turtle.rst:2343 +msgid "paint" +msgstr "" + +#: ../Doc/library/turtle.rst:2343 +msgid "super minimalistic drawing program" +msgstr "" + +#: ../Doc/library/turtle.rst:2346 +msgid "peace" +msgstr "" + +#: ../Doc/library/turtle.rst:2346 +msgid "elementary" +msgstr "" + +#: ../Doc/library/turtle.rst:2346 +msgid "turtle: appearance and animation" +msgstr "" + +#: ../Doc/library/turtle.rst:2349 +msgid "penrose" +msgstr "" + +#: ../Doc/library/turtle.rst:2349 +msgid "aperiodic tiling with kites and darts" +msgstr "" + +#: ../Doc/library/turtle.rst:2352 +msgid "planet_and_moon" +msgstr "" + +#: ../Doc/library/turtle.rst:2352 +msgid "simulation of gravitational system" +msgstr "" + +#: ../Doc/library/turtle.rst:2352 +msgid "compound shapes, :class:`Vec2D`" +msgstr "" + +#: ../Doc/library/turtle.rst:2355 +msgid "round_dance" +msgstr "" + +#: ../Doc/library/turtle.rst:2355 +msgid "dancing turtles rotating pairwise in opposite direction" +msgstr "" + +#: ../Doc/library/turtle.rst:2355 +msgid "compound shapes, clone shapesize, tilt, get_shapepoly, update" +msgstr "" + +#: ../Doc/library/turtle.rst:2359 +msgid "sorting_animate" +msgstr "" + +#: ../Doc/library/turtle.rst:2359 +msgid "visual demonstration of different sorting methods" +msgstr "" + +#: ../Doc/library/turtle.rst:2359 +msgid "simple alignment, randomization" +msgstr "" + +#: ../Doc/library/turtle.rst:2362 +msgid "a (graphical) breadth first tree (using generators)" +msgstr "" + +#: ../Doc/library/turtle.rst:2365 +msgid "two_canvases" +msgstr "" + +#: ../Doc/library/turtle.rst:2365 +msgid "simple design" +msgstr "" + +#: ../Doc/library/turtle.rst:2365 +msgid "turtles on two canvases" +msgstr "" + +#: ../Doc/library/turtle.rst:2368 +msgid "wikipedia" +msgstr "" + +#: ../Doc/library/turtle.rst:2368 +msgid "a pattern from the wikipedia article on turtle graphics" +msgstr "" + +#: ../Doc/library/turtle.rst:2368 +msgid ":func:`clone`, :func:`undo`" +msgstr "" + +#: ../Doc/library/turtle.rst:2371 +msgid "yingyang" +msgstr "" + +#: ../Doc/library/turtle.rst:2371 +msgid "another elementary example" +msgstr "" + +#: ../Doc/library/turtle.rst:2374 +msgid "Have fun!" +msgstr "" + +#: ../Doc/library/turtle.rst:2378 +msgid "Changes since Python 2.6" +msgstr "" + +#: ../Doc/library/turtle.rst:2380 +msgid "" +"The methods :meth:`Turtle.tracer`, :meth:`Turtle.window_width` and :meth:" +"`Turtle.window_height` have been eliminated. Methods with these names and " +"functionality are now available only as methods of :class:`Screen`. The " +"functions derived from these remain available. (In fact already in Python " +"2.6 these methods were merely duplications of the corresponding :class:" +"`TurtleScreen`/:class:`Screen`-methods.)" +msgstr "" + +#: ../Doc/library/turtle.rst:2388 +msgid "" +"The method :meth:`Turtle.fill` has been eliminated. The behaviour of :meth:" +"`begin_fill` and :meth:`end_fill` have changed slightly: now every filling-" +"process must be completed with an ``end_fill()`` call." +msgstr "" + +#: ../Doc/library/turtle.rst:2393 +msgid "" +"A method :meth:`Turtle.filling` has been added. It returns a boolean value: " +"``True`` if a filling process is under way, ``False`` otherwise. This " +"behaviour corresponds to a ``fill()`` call without arguments in Python 2.6." +msgstr "" + +#: ../Doc/library/turtle.rst:2399 +msgid "Changes since Python 3.0" +msgstr "" + +#: ../Doc/library/turtle.rst:2401 +msgid "" +"The methods :meth:`Turtle.shearfactor`, :meth:`Turtle.shapetransform` and :" +"meth:`Turtle.get_shapepoly` have been added. Thus the full range of regular " +"linear transforms is now available for transforming turtle shapes. :meth:" +"`Turtle.tiltangle` has been enhanced in functionality: it now can be used to " +"get or set the tiltangle. :meth:`Turtle.settiltangle` has been deprecated." +msgstr "" + +#: ../Doc/library/turtle.rst:2408 +msgid "" +"The method :meth:`Screen.onkeypress` has been added as a complement to :meth:" +"`Screen.onkey` which in fact binds actions to the keyrelease event. " +"Accordingly the latter has got an alias: :meth:`Screen.onkeyrelease`." +msgstr "" + +#: ../Doc/library/turtle.rst:2412 +msgid "" +"The method :meth:`Screen.mainloop` has been added. So when working only " +"with Screen and Turtle objects one must not additionally import :func:" +"`mainloop` anymore." +msgstr "" + +#: ../Doc/library/turtle.rst:2416 +msgid "" +"Two input methods has been added :meth:`Screen.textinput` and :meth:`Screen." +"numinput`. These popup input dialogs and return strings and numbers " +"respectively." +msgstr "" + +#: ../Doc/library/turtle.rst:2420 +msgid "" +"Two example scripts :file:`tdemo_nim.py` and :file:`tdemo_round_dance.py` " +"have been added to the :file:`Lib/turtledemo` directory." +msgstr "" + +#: ../Doc/library/types.rst:2 +msgid ":mod:`types` --- Dynamic type creation and names for built-in types" +msgstr "" + +#: ../Doc/library/types.rst:7 +msgid "**Source code:** :source:`Lib/types.py`" +msgstr "" + +#: ../Doc/library/types.rst:11 +msgid "" +"This module defines utility function to assist in dynamic creation of new " +"types." +msgstr "" + +#: ../Doc/library/types.rst:14 +msgid "" +"It also defines names for some object types that are used by the standard " +"Python interpreter, but not exposed as builtins like :class:`int` or :class:" +"`str` are." +msgstr "" + +#: ../Doc/library/types.rst:18 +msgid "" +"Finally, it provides some additional type-related utility classes and " +"functions that are not fundamental enough to be builtins." +msgstr "" + +#: ../Doc/library/types.rst:23 +msgid "Dynamic Type Creation" +msgstr "" + +#: ../Doc/library/types.rst:27 +msgid "Creates a class object dynamically using the appropriate metaclass." +msgstr "" + +#: ../Doc/library/types.rst:29 +msgid "" +"The first three arguments are the components that make up a class definition " +"header: the class name, the base classes (in order), the keyword arguments " +"(such as ``metaclass``)." +msgstr "" + +#: ../Doc/library/types.rst:33 +msgid "" +"The *exec_body* argument is a callback that is used to populate the freshly " +"created class namespace. It should accept the class namespace as its sole " +"argument and update the namespace directly with the class contents. If no " +"callback is provided, it has the same effect as passing in ``lambda ns: ns``." +msgstr "" + +#: ../Doc/library/types.rst:43 +msgid "Calculates the appropriate metaclass and creates the class namespace." +msgstr "" + +#: ../Doc/library/types.rst:45 +msgid "" +"The arguments are the components that make up a class definition header: the " +"class name, the base classes (in order) and the keyword arguments (such as " +"``metaclass``)." +msgstr "" + +#: ../Doc/library/types.rst:49 +msgid "The return value is a 3-tuple: ``metaclass, namespace, kwds``" +msgstr "" + +#: ../Doc/library/types.rst:51 +msgid "" +"*metaclass* is the appropriate metaclass, *namespace* is the prepared class " +"namespace and *kwds* is an updated copy of the passed in *kwds* argument " +"with any ``'metaclass'`` entry removed. If no *kwds* argument is passed in, " +"this will be an empty dict." +msgstr "" + +#: ../Doc/library/types.rst:60 +msgid "" +"The default value for the ``namespace`` element of the returned tuple has " +"changed. Now an insertion-order-preserving mapping is used when the " +"metaclass does not have a ``__prepare__`` method," +msgstr "" + +#: ../Doc/library/types.rst:67 +msgid ":ref:`metaclasses`" +msgstr "" + +#: ../Doc/library/types.rst:67 +msgid "Full details of the class creation process supported by these functions" +msgstr "" + +#: ../Doc/library/types.rst:69 +msgid ":pep:`3115` - Metaclasses in Python 3000" +msgstr "" + +#: ../Doc/library/types.rst:70 +msgid "Introduced the ``__prepare__`` namespace hook" +msgstr "" + +#: ../Doc/library/types.rst:74 +msgid "Standard Interpreter Types" +msgstr "" + +#: ../Doc/library/types.rst:76 +msgid "" +"This module provides names for many of the types that are required to " +"implement a Python interpreter. It deliberately avoids including some of the " +"types that arise only incidentally during processing such as the " +"``listiterator`` type." +msgstr "" + +#: ../Doc/library/types.rst:81 +msgid "" +"Typical use of these names is for :func:`isinstance` or :func:`issubclass` " +"checks." +msgstr "" + +#: ../Doc/library/types.rst:84 +msgid "Standard names are defined for the following types:" +msgstr "" + +#: ../Doc/library/types.rst:89 +msgid "" +"The type of user-defined functions and functions created by :keyword:" +"`lambda` expressions." +msgstr "" + +#: ../Doc/library/types.rst:95 +msgid "" +"The type of :term:`generator`-iterator objects, created by generator " +"functions." +msgstr "" + +#: ../Doc/library/types.rst:101 +msgid "" +"The type of :term:`coroutine` objects, created by :keyword:`async def` " +"functions." +msgstr "" + +#: ../Doc/library/types.rst:111 +msgid "The type for code objects such as returned by :func:`compile`." +msgstr "" + +#: ../Doc/library/types.rst:116 +msgid "The type of methods of user-defined class instances." +msgstr "" + +#: ../Doc/library/types.rst:122 +msgid "" +"The type of built-in functions like :func:`len` or :func:`sys.exit`, and " +"methods of built-in classes. (Here, the term \"built-in\" means \"written " +"in C\".)" +msgstr "" + +#: ../Doc/library/types.rst:129 +msgid "" +"The type of :term:`modules `. Constructor takes the name of the " +"module to be created and optionally its :term:`docstring`." +msgstr "" + +#: ../Doc/library/types.rst:133 +msgid "" +"Use :func:`importlib.util.module_from_spec` to create a new module if you " +"wish to set the various import-controlled attributes." +msgstr "" + +#: ../Doc/library/types.rst:138 +msgid "The :term:`docstring` of the module. Defaults to ``None``." +msgstr "" + +#: ../Doc/library/types.rst:142 +msgid "The :term:`loader` which loaded the module. Defaults to ``None``." +msgstr "" + +#: ../Doc/library/types.rst:144 ../Doc/library/types.rst:158 +msgid "Defaults to ``None``. Previously the attribute was optional." +msgstr "" + +#: ../Doc/library/types.rst:153 +msgid "" +"Which :term:`package` a module belongs to. If the module is top-level (i.e. " +"not a part of any specific package) then the attribute should be set to " +"``''``, else it should be set to the name of the package (which can be :attr:" +"`__name__` if the module is a package itself). Defaults to ``None``." +msgstr "" + +#: ../Doc/library/types.rst:164 +msgid "The type of traceback objects such as found in ``sys.exc_info()[2]``." +msgstr "" + +#: ../Doc/library/types.rst:169 +msgid "" +"The type of frame objects such as found in ``tb.tb_frame`` if ``tb`` is a " +"traceback object." +msgstr "" + +#: ../Doc/library/types.rst:175 +msgid "" +"The type of objects defined in extension modules with ``PyGetSetDef``, such " +"as ``FrameType.f_locals`` or ``array.array.typecode``. This type is used as " +"descriptor for object attributes; it has the same purpose as the :class:" +"`property` type, but for classes defined in extension modules." +msgstr "" + +#: ../Doc/library/types.rst:183 +msgid "" +"The type of objects defined in extension modules with ``PyMemberDef``, such " +"as ``datetime.timedelta.days``. This type is used as descriptor for simple " +"C data members which use standard conversion functions; it has the same " +"purpose as the :class:`property` type, but for classes defined in extension " +"modules." +msgstr "" + +#: ../Doc/library/types.rst:190 +msgid "" +"In other implementations of Python, this type may be identical to " +"``GetSetDescriptorType``." +msgstr "" + +#: ../Doc/library/types.rst:195 +msgid "" +"Read-only proxy of a mapping. It provides a dynamic view on the mapping's " +"entries, which means that when the mapping changes, the view reflects these " +"changes." +msgstr "" + +#: ../Doc/library/types.rst:203 +msgid "" +"Return ``True`` if the underlying mapping has a key *key*, else ``False``." +msgstr "" + +#: ../Doc/library/types.rst:208 +msgid "" +"Return the item of the underlying mapping with key *key*. Raises a :exc:" +"`KeyError` if *key* is not in the underlying mapping." +msgstr "" + +#: ../Doc/library/types.rst:213 +msgid "" +"Return an iterator over the keys of the underlying mapping. This is a " +"shortcut for ``iter(proxy.keys())``." +msgstr "" + +#: ../Doc/library/types.rst:218 +msgid "Return the number of items in the underlying mapping." +msgstr "" + +#: ../Doc/library/types.rst:222 +msgid "Return a shallow copy of the underlying mapping." +msgstr "" + +#: ../Doc/library/types.rst:226 +msgid "" +"Return the value for *key* if *key* is in the underlying mapping, else " +"*default*. If *default* is not given, it defaults to ``None``, so that this " +"method never raises a :exc:`KeyError`." +msgstr "" + +#: ../Doc/library/types.rst:232 +msgid "" +"Return a new view of the underlying mapping's items (``(key, value)`` pairs)." +msgstr "" + +#: ../Doc/library/types.rst:237 +msgid "Return a new view of the underlying mapping's keys." +msgstr "" + +#: ../Doc/library/types.rst:241 +msgid "Return a new view of the underlying mapping's values." +msgstr "" + +#: ../Doc/library/types.rst:245 +msgid "Additional Utility Classes and Functions" +msgstr "" + +#: ../Doc/library/types.rst:249 +msgid "" +"A simple :class:`object` subclass that provides attribute access to its " +"namespace, as well as a meaningful repr." +msgstr "" + +#: ../Doc/library/types.rst:252 +msgid "" +"Unlike :class:`object`, with ``SimpleNamespace`` you can add and remove " +"attributes. If a ``SimpleNamespace`` object is initialized with keyword " +"arguments, those are directly added to the underlying namespace." +msgstr "" + +#: ../Doc/library/types.rst:256 +msgid "The type is roughly equivalent to the following code::" +msgstr "" + +#: ../Doc/library/types.rst:270 +msgid "" +"``SimpleNamespace`` may be useful as a replacement for ``class NS: pass``. " +"However, for a structured record type use :func:`~collections.namedtuple` " +"instead." +msgstr "" + +#: ../Doc/library/types.rst:279 +msgid "Route attribute access on a class to __getattr__." +msgstr "" + +#: ../Doc/library/types.rst:281 +msgid "" +"This is a descriptor, used to define attributes that act differently when " +"accessed through an instance and through a class. Instance access remains " +"normal, but access to an attribute through a class will be routed to the " +"class's __getattr__ method; this is done by raising AttributeError." +msgstr "" + +#: ../Doc/library/types.rst:286 +msgid "" +"This allows one to have properties active on an instance, and have virtual " +"attributes on the class with the same name (see Enum for an example)." +msgstr "" + +#: ../Doc/library/types.rst:293 +msgid "Coroutine Utility Functions" +msgstr "" + +#: ../Doc/library/types.rst:297 +msgid "" +"This function transforms a :term:`generator` function into a :term:" +"`coroutine function` which returns a generator-based coroutine. The " +"generator-based coroutine is still a :term:`generator iterator`, but is also " +"considered to be a :term:`coroutine` object and is :term:`awaitable`. " +"However, it may not necessarily implement the :meth:`__await__` method." +msgstr "" + +#: ../Doc/library/types.rst:304 +msgid "If *gen_func* is a generator function, it will be modified in-place." +msgstr "" + +#: ../Doc/library/types.rst:306 +msgid "" +"If *gen_func* is not a generator function, it will be wrapped. If it returns " +"an instance of :class:`collections.abc.Generator`, the instance will be " +"wrapped in an *awaitable* proxy object. All other types of objects will be " +"returned as is." +msgstr "" + +#: ../Doc/library/typing.rst:2 +msgid ":mod:`typing` --- Support for type hints" +msgstr "" + +#: ../Doc/library/typing.rst:9 +msgid "**Source code:** :source:`Lib/typing.py`" +msgstr "" + +#: ../Doc/library/typing.rst:13 +msgid "" +"This module supports type hints as specified by :pep:`484` and :pep:`526`. " +"The most fundamental support consists of the type :data:`Any`, :data:" +"`Union`, :data:`Tuple`, :data:`Callable`, :class:`TypeVar`, and :class:" +"`Generic`. For full specification please see :pep:`484`. For a simplified " +"introduction to type hints see :pep:`483`." +msgstr "" + +#: ../Doc/library/typing.rst:20 +msgid "" +"The function below takes and returns a string and is annotated as follows::" +msgstr "" + +#: ../Doc/library/typing.rst:25 +msgid "" +"In the function ``greeting``, the argument ``name`` is expected to be of " +"type :class:`str` and the return type :class:`str`. Subtypes are accepted as " +"arguments." +msgstr "" + +#: ../Doc/library/typing.rst:30 +msgid "Type aliases" +msgstr "" + +#: ../Doc/library/typing.rst:32 +msgid "" +"A type alias is defined by assigning the type to the alias. In this example, " +"``Vector`` and ``List[float]`` will be treated as interchangeable synonyms::" +msgstr "" + +#: ../Doc/library/typing.rst:44 +msgid "" +"Type aliases are useful for simplifying complex type signatures. For " +"example::" +msgstr "" + +#: ../Doc/library/typing.rst:62 +msgid "" +"Note that ``None`` as a type hint is a special case and is replaced by " +"``type(None)``." +msgstr "" + +#: ../Doc/library/typing.rst:68 +msgid "NewType" +msgstr "" + +#: ../Doc/library/typing.rst:70 +msgid "Use the :func:`NewType` helper function to create distinct types::" +msgstr "" + +#: ../Doc/library/typing.rst:77 +msgid "" +"The static type checker will treat the new type as if it were a subclass of " +"the original type. This is useful in helping catch logical errors::" +msgstr "" + +#: ../Doc/library/typing.rst:89 +msgid "" +"You may still perform all ``int`` operations on a variable of type " +"``UserId``, but the result will always be of type ``int``. This lets you " +"pass in a ``UserId`` wherever an ``int`` might be expected, but will prevent " +"you from accidentally creating a ``UserId`` in an invalid way::" +msgstr "" + +#: ../Doc/library/typing.rst:97 +msgid "" +"Note that these checks are enforced only by the static type checker. At " +"runtime the statement ``Derived = NewType('Derived', Base)`` will make " +"``Derived`` a function that immediately returns whatever parameter you pass " +"it. That means the expression ``Derived(some_value)`` does not create a new " +"class or introduce any overhead beyond that of a regular function call." +msgstr "" + +#: ../Doc/library/typing.rst:103 +msgid "" +"More precisely, the expression ``some_value is Derived(some_value)`` is " +"always true at runtime." +msgstr "" + +#: ../Doc/library/typing.rst:106 +msgid "" +"This also means that it is not possible to create a subtype of ``Derived`` " +"since it is an identity function at runtime, not an actual type. Similarly, " +"it is not possible to create another :func:`NewType` based on a ``Derived`` " +"type::" +msgstr "" + +#: ../Doc/library/typing.rst:120 +msgid "See :pep:`484` for more details." +msgstr "" + +#: ../Doc/library/typing.rst:124 +msgid "" +"Recall that the use of a type alias declares two types to be *equivalent* to " +"one another. Doing ``Alias = Original`` will make the static type checker " +"treat ``Alias`` as being *exactly equivalent* to ``Original`` in all cases. " +"This is useful when you want to simplify complex type signatures." +msgstr "" + +#: ../Doc/library/typing.rst:129 +msgid "" +"In contrast, ``NewType`` declares one type to be a *subtype* of another. " +"Doing ``Derived = NewType('Derived', Original)`` will make the static type " +"checker treat ``Derived`` as a *subclass* of ``Original``, which means a " +"value of type ``Original`` cannot be used in places where a value of type " +"``Derived`` is expected. This is useful when you want to prevent logic " +"errors with minimal runtime cost." +msgstr "" + +#: ../Doc/library/typing.rst:137 +msgid "Callable" +msgstr "" + +#: ../Doc/library/typing.rst:139 +msgid "" +"Frameworks expecting callback functions of specific signatures might be type " +"hinted using ``Callable[[Arg1Type, Arg2Type], ReturnType]``." +msgstr "" + +#: ../Doc/library/typing.rst:153 +msgid "" +"It is possible to declare the return type of a callable without specifying " +"the call signature by substituting a literal ellipsis for the list of " +"arguments in the type hint: ``Callable[..., ReturnType]``." +msgstr "" + +#: ../Doc/library/typing.rst:158 +msgid "Generics" +msgstr "" + +#: ../Doc/library/typing.rst:160 +msgid "" +"Since type information about objects kept in containers cannot be statically " +"inferred in a generic way, abstract base classes have been extended to " +"support subscription to denote expected types for container elements." +msgstr "" + +#: ../Doc/library/typing.rst:171 +msgid "" +"Generics can be parametrized by using a new factory available in typing " +"called :class:`TypeVar`." +msgstr "" + +#: ../Doc/library/typing.rst:185 +msgid "User-defined generic types" +msgstr "" + +#: ../Doc/library/typing.rst:187 +msgid "A user-defined class can be defined as a generic class." +msgstr "" + +#: ../Doc/library/typing.rst:213 +msgid "" +"``Generic[T]`` as a base class defines that the class ``LoggedVar`` takes a " +"single type parameter ``T`` . This also makes ``T`` valid as a type within " +"the class body." +msgstr "" + +#: ../Doc/library/typing.rst:217 +msgid "" +"The :class:`Generic` base class uses a metaclass that defines :meth:" +"`__getitem__` so that ``LoggedVar[t]`` is valid as a type::" +msgstr "" + +#: ../Doc/library/typing.rst:226 +msgid "" +"A generic type can have any number of type variables, and type variables may " +"be constrained::" +msgstr "" + +#: ../Doc/library/typing.rst:238 +msgid "" +"Each type variable argument to :class:`Generic` must be distinct. This is " +"thus invalid::" +msgstr "" + +#: ../Doc/library/typing.rst:249 +msgid "You can use multiple inheritance with :class:`Generic`::" +msgstr "" + +#: ../Doc/library/typing.rst:258 +msgid "" +"When inheriting from generic classes, some type variables could be fixed::" +msgstr "" + +#: ../Doc/library/typing.rst:267 +msgid "In this case ``MyDict`` has a single parameter, ``T``." +msgstr "" + +#: ../Doc/library/typing.rst:269 +msgid "" +"Using a generic class without specifying type parameters assumes :data:`Any` " +"for each position. In the following example, ``MyIterable`` is not generic " +"but implicitly inherits from ``Iterable[Any]``::" +msgstr "" + +#: ../Doc/library/typing.rst:277 +msgid "" +"The metaclass used by :class:`Generic` is a subclass of :class:`abc." +"ABCMeta`. A generic class can be an ABC by including abstract methods or " +"properties, and generic classes can also have ABCs as base classes without a " +"metaclass conflict. Generic metaclasses are not supported. The outcome of " +"parameterizing generics is cached, and most types in the typing module are " +"hashable and comparable for equality." +msgstr "" + +#: ../Doc/library/typing.rst:286 +msgid "The :data:`Any` type" +msgstr "" + +#: ../Doc/library/typing.rst:288 +msgid "" +"A special kind of type is :data:`Any`. A static type checker will treat " +"every type as being compatible with :data:`Any` and :data:`Any` as being " +"compatible with every type." +msgstr "" + +#: ../Doc/library/typing.rst:292 +msgid "" +"This means that it is possible to perform any operation or method call on a " +"value of type on :data:`Any` and assign it to any variable::" +msgstr "" + +#: ../Doc/library/typing.rst:310 +msgid "" +"Notice that no typechecking is performed when assigning a value of type :" +"data:`Any` to a more precise type. For example, the static type checker did " +"not report an error when assigning ``a`` to ``s`` even though ``s`` was " +"declared to be of type :class:`str` and receives an :class:`int` value at " +"runtime!" +msgstr "" + +#: ../Doc/library/typing.rst:316 +msgid "" +"Furthermore, all functions without a return type or parameter types will " +"implicitly default to using :data:`Any`::" +msgstr "" + +#: ../Doc/library/typing.rst:329 +msgid "" +"This behavior allows :data:`Any` to be used as an *escape hatch* when you " +"need to mix dynamically and statically typed code." +msgstr "" + +#: ../Doc/library/typing.rst:332 +msgid "" +"Contrast the behavior of :data:`Any` with the behavior of :class:`object`. " +"Similar to :data:`Any`, every type is a subtype of :class:`object`. However, " +"unlike :data:`Any`, the reverse is not true: :class:`object` is *not* a " +"subtype of every other type." +msgstr "" + +#: ../Doc/library/typing.rst:337 +msgid "" +"That means when the type of a value is :class:`object`, a type checker will " +"reject almost all operations on it, and assigning it to a variable (or using " +"it as a return value) of a more specialized type is a type error. For " +"example::" +msgstr "" + +#: ../Doc/library/typing.rst:359 +msgid "" +"Use :class:`object` to indicate that a value could be any type in a typesafe " +"manner. Use :data:`Any` to indicate that a value is dynamically typed." +msgstr "" + +#: ../Doc/library/typing.rst:363 +msgid "Classes, functions, and decorators" +msgstr "" + +#: ../Doc/library/typing.rst:365 +msgid "The module defines the following classes, functions and decorators:" +msgstr "" + +#: ../Doc/library/typing.rst:369 +msgid "Type variable." +msgstr "" + +#: ../Doc/library/typing.rst:376 +msgid "" +"Type variables exist primarily for the benefit of static type checkers. " +"They serve as the parameters for generic types as well as for generic " +"function definitions. See class Generic for more information on generic " +"types. Generic functions work as follows::" +msgstr "" + +#: ../Doc/library/typing.rst:389 +msgid "" +"The latter example's signature is essentially the overloading of ``(str, " +"str) -> str`` and ``(bytes, bytes) -> bytes``. Also note that if the " +"arguments are instances of some subclass of :class:`str`, the return type is " +"still plain :class:`str`." +msgstr "" + +#: ../Doc/library/typing.rst:394 +msgid "" +"At runtime, ``isinstance(x, T)`` will raise :exc:`TypeError`. In general, :" +"func:`isinstance` and :func:`issubclass` should not be used with types." +msgstr "" + +#: ../Doc/library/typing.rst:397 +msgid "" +"Type variables may be marked covariant or contravariant by passing " +"``covariant=True`` or ``contravariant=True``. See :pep:`484` for more " +"details. By default type variables are invariant. Alternatively, a type " +"variable may specify an upper bound using ``bound=``. This means that " +"an actual type substituted (explicitly or implicitly) for the type variable " +"must be a subclass of the boundary type, see :pep:`484`." +msgstr "" + +#: ../Doc/library/typing.rst:407 +msgid "Abstract base class for generic types." +msgstr "" + +#: ../Doc/library/typing.rst:409 +msgid "" +"A generic type is typically declared by inheriting from an instantiation of " +"this class with one or more type variables. For example, a generic mapping " +"type might be defined as::" +msgstr "" + +#: ../Doc/library/typing.rst:418 +msgid "This class can then be used as follows::" +msgstr "" + +#: ../Doc/library/typing.rst:431 +msgid "" +"A variable annotated with ``C`` may accept a value of type ``C``. In " +"contrast, a variable annotated with ``Type[C]`` may accept values that are " +"classes themselves -- specifically, it will accept the *class object* of " +"``C``. For example::" +msgstr "" + +#: ../Doc/library/typing.rst:440 +msgid "Note that ``Type[C]`` is covariant::" +msgstr "" + +#: ../Doc/library/typing.rst:452 +msgid "" +"The fact that ``Type[C]`` is covariant implies that all subclasses of ``C`` " +"should implement the same constructor signature and class method signatures " +"as ``C``. The type checker should flag violations of this, but should also " +"allow constructor calls in subclasses that match the constructor calls in " +"the indicated base class. How the type checker is required to handle this " +"particular case may change in future revisions of :pep:`484`." +msgstr "" + +#: ../Doc/library/typing.rst:460 +msgid "" +"The only legal parameters for :class:`Type` are classes, unions of classes, " +"and :data:`Any`. For example::" +msgstr "" + +#: ../Doc/library/typing.rst:465 +msgid "" +"``Type[Any]`` is equivalent to ``Type`` which in turn is equivalent to " +"``type``, which is the root of Python's metaclass hierarchy." +msgstr "" + +#: ../Doc/library/typing.rst:470 +msgid "A generic version of :class:`collections.abc.Iterable`." +msgstr "" + +#: ../Doc/library/typing.rst:474 +msgid "A generic version of :class:`collections.abc.Iterator`." +msgstr "" + +#: ../Doc/library/typing.rst:478 +msgid "A generic version of :class:`collections.abc.Reversible`." +msgstr "" + +#: ../Doc/library/typing.rst:482 +msgid "An ABC with one abstract method ``__int__``." +msgstr "" + +#: ../Doc/library/typing.rst:486 +msgid "An ABC with one abstract method ``__float__``." +msgstr "" + +#: ../Doc/library/typing.rst:490 +msgid "" +"An ABC with one abstract method ``__abs__`` that is covariant in its return " +"type." +msgstr "" + +#: ../Doc/library/typing.rst:495 +msgid "" +"An ABC with one abstract method ``__round__`` that is covariant in its " +"return type." +msgstr "" + +#: ../Doc/library/typing.rst:500 +msgid "A generic version of :class:`collections.abc.Container`." +msgstr "" + +#: ../Doc/library/typing.rst:504 +msgid "An alias to :class:`collections.abc.Hashable`" +msgstr "" + +#: ../Doc/library/typing.rst:508 +msgid "An alias to :class:`collections.abc.Sized`" +msgstr "" + +#: ../Doc/library/typing.rst:512 +msgid "A generic version of :class:`collections.abc.Collection`" +msgstr "" + +#: ../Doc/library/typing.rst:518 +msgid "A generic version of :class:`collections.abc.Set`." +msgstr "" + +#: ../Doc/library/typing.rst:522 +msgid "A generic version of :class:`collections.abc.MutableSet`." +msgstr "" + +#: ../Doc/library/typing.rst:526 +msgid "A generic version of :class:`collections.abc.Mapping`." +msgstr "" + +#: ../Doc/library/typing.rst:530 +msgid "A generic version of :class:`collections.abc.MutableMapping`." +msgstr "" + +#: ../Doc/library/typing.rst:534 +msgid "A generic version of :class:`collections.abc.Sequence`." +msgstr "" + +#: ../Doc/library/typing.rst:538 +msgid "A generic version of :class:`collections.abc.MutableSequence`." +msgstr "" + +#: ../Doc/library/typing.rst:542 +msgid "A generic version of :class:`collections.abc.ByteString`." +msgstr "" + +#: ../Doc/library/typing.rst:544 +msgid "" +"This type represents the types :class:`bytes`, :class:`bytearray`, and :" +"class:`memoryview`." +msgstr "" + +#: ../Doc/library/typing.rst:547 +msgid "" +"As a shorthand for this type, :class:`bytes` can be used to annotate " +"arguments of any of the types mentioned above." +msgstr "" + +#: ../Doc/library/typing.rst:552 +msgid "" +"Generic version of :class:`list`. Useful for annotating return types. To " +"annotate arguments it is preferred to use abstract collection types such as :" +"class:`Mapping`, :class:`Sequence`, or :class:`AbstractSet`." +msgstr "" + +#: ../Doc/library/typing.rst:557 +msgid "This type may be used as follows::" +msgstr "" + +#: ../Doc/library/typing.rst:569 +msgid "A generic version of :class:`builtins.set `." +msgstr "" + +#: ../Doc/library/typing.rst:573 +msgid "A generic version of :class:`collections.abc.MappingView`." +msgstr "" + +#: ../Doc/library/typing.rst:577 +msgid "A generic version of :class:`collections.abc.KeysView`." +msgstr "" + +#: ../Doc/library/typing.rst:581 +msgid "A generic version of :class:`collections.abc.ItemsView`." +msgstr "" + +#: ../Doc/library/typing.rst:585 +msgid "A generic version of :class:`collections.abc.ValuesView`." +msgstr "" + +#: ../Doc/library/typing.rst:589 +msgid "A generic version of :class:`collections.abc.Awaitable`." +msgstr "" + +#: ../Doc/library/typing.rst:593 +msgid "A generic version of :class:`collections.abc.AsyncIterable`." +msgstr "" + +#: ../Doc/library/typing.rst:597 +msgid "A generic version of :class:`collections.abc.AsyncIterator`." +msgstr "" + +#: ../Doc/library/typing.rst:601 +msgid "A generic version of :class:`contextlib.AbstractContextManager`." +msgstr "" + +#: ../Doc/library/typing.rst:607 +msgid "" +"A generic version of :class:`dict`. The usage of this type is as follows::" +msgstr "" + +#: ../Doc/library/typing.rst:615 +msgid "A generic version of :class:`collections.defaultdict`" +msgstr "" + +#: ../Doc/library/typing.rst:619 +msgid "" +"A generator can be annotated by the generic type ``Generator[YieldType, " +"SendType, ReturnType]``. For example::" +msgstr "" + +#: ../Doc/library/typing.rst:628 +msgid "" +"Note that unlike many other generics in the typing module, the ``SendType`` " +"of :class:`Generator` behaves contravariantly, not covariantly or " +"invariantly." +msgstr "" + +#: ../Doc/library/typing.rst:632 +msgid "" +"If your generator will only yield values, set the ``SendType`` and " +"``ReturnType`` to ``None``::" +msgstr "" + +#: ../Doc/library/typing.rst:640 +msgid "" +"Alternatively, annotate your generator as having a return type of either " +"``Iterable[YieldType]`` or ``Iterator[YieldType]``::" +msgstr "" + +#: ../Doc/library/typing.rst:650 +msgid "" +"``Text`` is an alias for ``str``. It is provided to supply a forward " +"compatible path for Python 2 code: in Python 2, ``Text`` is an alias for " +"``unicode``." +msgstr "" + +#: ../Doc/library/typing.rst:654 +msgid "" +"Use ``Text`` to indicate that a value must contain a unicode string in a " +"manner that is compatible with both Python 2 and Python 3::" +msgstr "" + +#: ../Doc/library/typing.rst:662 +msgid "Wrapper namespace for I/O stream types." +msgstr "" + +#: ../Doc/library/typing.rst:664 +msgid "" +"This defines the generic type ``IO[AnyStr]`` and aliases ``TextIO`` and " +"``BinaryIO`` for respectively ``IO[str]`` and ``IO[bytes]``. These " +"representing the types of I/O streams such as returned by :func:`open`." +msgstr "" + +#: ../Doc/library/typing.rst:671 +msgid "Wrapper namespace for regular expression matching types." +msgstr "" + +#: ../Doc/library/typing.rst:673 +msgid "" +"This defines the type aliases ``Pattern`` and ``Match`` which correspond to " +"the return types from :func:`re.compile` and :func:`re.match`. These types " +"(and the corresponding functions) are generic in ``AnyStr`` and can be made " +"specific by writing ``Pattern[str]``, ``Pattern[bytes]``, ``Match[str]``, or " +"``Match[bytes]``." +msgstr "" + +#: ../Doc/library/typing.rst:682 +msgid "Typed version of namedtuple." +msgstr "" + +#: ../Doc/library/typing.rst:692 +msgid "" +"The resulting class has one extra attribute: _field_types, giving a dict " +"mapping field names to types. (The field names are in the _fields " +"attribute, which is part of the namedtuple API.)" +msgstr "" + +#: ../Doc/library/typing.rst:699 +msgid "" +"A helper function to indicate a distinct types to a typechecker, see :ref:" +"`distinct`. At runtime it returns a function that returns its argument. " +"Usage::" +msgstr "" + +#: ../Doc/library/typing.rst:708 +msgid "Cast a value to a type." +msgstr "" + +#: ../Doc/library/typing.rst:710 +msgid "" +"This returns the value unchanged. To the type checker this signals that the " +"return value has the designated type, but at runtime we intentionally don't " +"check anything (we want this to be as fast as possible)." +msgstr "" + +#: ../Doc/library/typing.rst:717 +msgid "Return type hints for a class, module, function or method object." +msgstr "" + +#: ../Doc/library/typing.rst:719 +msgid "" +"This is often the same as ``obj.__annotations__``, but it handles forward " +"references encoded as string literals, and if necessary adds ``Optional[t]`` " +"if a default value equal to None is set." +msgstr "" + +#: ../Doc/library/typing.rst:725 +msgid "" +"The ``@overload`` decorator allows describing functions and methods that " +"support multiple different combinations of argument types. A series of " +"``@overload``-decorated definitions must be followed by exactly one non-" +"``@overload``-decorated definition (for the same function/method). The " +"``@overload``-decorated definitions are for the benefit of the type checker " +"only, since they will be overwritten by the non-``@overload``-decorated " +"definition, while the latter is used at runtime but should be ignored by a " +"type checker. At runtime, calling a ``@overload``-decorated function " +"directly will raise ``NotImplementedError``. An example of overload that " +"gives a more precise type than can be expressed using a union or a type " +"variable::" +msgstr "" + +#: ../Doc/library/typing.rst:749 +msgid "See :pep:`484` for details and comparison with other typing semantics." +msgstr "" + +#: ../Doc/library/typing.rst:753 +msgid "Decorator to indicate that annotations are not type hints." +msgstr "" + +#: ../Doc/library/typing.rst:755 +msgid "" +"The argument must be a class or function; if it is a class, it applies " +"recursively to all methods defined in that class (but not to methods defined " +"in its superclasses or subclasses)." +msgstr "" + +#: ../Doc/library/typing.rst:759 +msgid "This mutates the function(s) in place." +msgstr "" + +#: ../Doc/library/typing.rst:763 +msgid "Decorator to give another decorator the :func:`no_type_check` effect." +msgstr "" + +#: ../Doc/library/typing.rst:765 +msgid "" +"This wraps the decorator with something that wraps the decorated function " +"in :func:`no_type_check`." +msgstr "" + +#: ../Doc/library/typing.rst:770 +msgid "Special type indicating an unconstrained type." +msgstr "" + +#: ../Doc/library/typing.rst:772 +msgid "Every type is compatible with :data:`Any`." +msgstr "" + +#: ../Doc/library/typing.rst:773 +msgid ":data:`Any` is compatible with every type." +msgstr "" + +#: ../Doc/library/typing.rst:777 +msgid "Union type; ``Union[X, Y]`` means either X or Y." +msgstr "" + +#: ../Doc/library/typing.rst:779 +msgid "To define a union, use e.g. ``Union[int, str]``. Details:" +msgstr "" + +#: ../Doc/library/typing.rst:781 +msgid "The arguments must be types and there must be at least one." +msgstr "" + +#: ../Doc/library/typing.rst:783 +msgid "Unions of unions are flattened, e.g.::" +msgstr "" + +#: ../Doc/library/typing.rst:787 +msgid "Unions of a single argument vanish, e.g.::" +msgstr "" + +#: ../Doc/library/typing.rst:791 +msgid "Redundant arguments are skipped, e.g.::" +msgstr "" + +#: ../Doc/library/typing.rst:795 +msgid "When comparing unions, the argument order is ignored, e.g.::" +msgstr "" + +#: ../Doc/library/typing.rst:799 +msgid "" +"When a class and its subclass are present, the former is skipped, e.g.::" +msgstr "" + +#: ../Doc/library/typing.rst:803 +msgid "You cannot subclass or instantiate a union." +msgstr "" + +#: ../Doc/library/typing.rst:805 +msgid "You cannot write ``Union[X][Y]``." +msgstr "" + +#: ../Doc/library/typing.rst:807 +msgid "You can use ``Optional[X]`` as a shorthand for ``Union[X, None]``." +msgstr "" + +#: ../Doc/library/typing.rst:811 +msgid "Optional type." +msgstr "" + +#: ../Doc/library/typing.rst:813 +msgid "``Optional[X]`` is equivalent to ``Union[X, None]``." +msgstr "" + +#: ../Doc/library/typing.rst:815 +msgid "" +"Note that this is not the same concept as an optional argument, which is one " +"that has a default. An optional argument with a default needn't use the " +"``Optional`` qualifier on its type annotation (although it is inferred if " +"the default is ``None``). A mandatory argument may still have an " +"``Optional`` type if an explicit value of ``None`` is allowed." +msgstr "" + +#: ../Doc/library/typing.rst:824 +msgid "" +"Tuple type; ``Tuple[X, Y]`` is the type of a tuple of two items with the " +"first item of type X and the second of type Y." +msgstr "" + +#: ../Doc/library/typing.rst:827 +msgid "" +"Example: ``Tuple[T1, T2]`` is a tuple of two elements corresponding to type " +"variables T1 and T2. ``Tuple[int, float, str]`` is a tuple of an int, a " +"float and a string." +msgstr "" + +#: ../Doc/library/typing.rst:831 +msgid "" +"To specify a variable-length tuple of homogeneous type, use literal " +"ellipsis, e.g. ``Tuple[int, ...]``. A plain :data:`Tuple` is equivalent to " +"``Tuple[Any, ...]``, and in turn to :data:`tuple`." +msgstr "" + +#: ../Doc/library/typing.rst:837 +msgid "Callable type; ``Callable[[int], str]`` is a function of (int) -> str." +msgstr "" + +#: ../Doc/library/typing.rst:839 +msgid "" +"The subscription syntax must always be used with exactly two values: the " +"argument list and the return type. The argument list must be a list of " +"types; the return type must be a single type." +msgstr "" + +#: ../Doc/library/typing.rst:843 +msgid "" +"There is no syntax to indicate optional or keyword arguments; such function " +"types are rarely used as callback types. ``Callable[..., ReturnType]`` " +"(literal ellipsis) can be used to type hint a callable taking any number of " +"arguments and returning ``ReturnType``. A plain :data:`Callable` is " +"equivalent to ``Callable[..., Any]``, and in turn to :class:`collections.abc." +"Callable`." +msgstr "" + +#: ../Doc/library/typing.rst:853 +msgid "Special type construct to mark class variables." +msgstr "" + +#: ../Doc/library/typing.rst:855 +msgid "" +"As introduced in :pep:`526`, a variable annotation wrapped in ClassVar " +"indicates that a given attribute is intended to be used as a class variable " +"and should not be set on instances of that class. Usage::" +msgstr "" + +#: ../Doc/library/typing.rst:863 +msgid ":data:`ClassVar` accepts only types and cannot be further subscribed." +msgstr "" + +#: ../Doc/library/typing.rst:865 +msgid "" +":data:`ClassVar` is not a class itself, and should not be used with :func:" +"`isinstance` or :func:`issubclass`. Note that :data:`ClassVar` does not " +"change Python runtime behavior; it can be used by 3rd party type checkers, " +"so that the following code might flagged as an error by those::" +msgstr "" + +#: ../Doc/library/typing.rst:879 +msgid "" +"``AnyStr`` is a type variable defined as ``AnyStr = TypeVar('AnyStr', str, " +"bytes)``." +msgstr "" + +#: ../Doc/library/typing.rst:882 +msgid "" +"It is meant to be used for functions that may accept any kind of string " +"without allowing different kinds of strings to mix. For example::" +msgstr "" + +#: ../Doc/library/typing.rst:894 +msgid "" +"A special constant that is assumed to be ``True`` by 3rd party static type " +"checkers. It is ``False`` at runtime. Usage::" +msgstr "" + +#: ../Doc/library/undoc.rst:5 +msgid "Undocumented Modules" +msgstr "" + +#: ../Doc/library/undoc.rst:7 +msgid "" +"Here's a quick listing of modules that are currently undocumented, but that " +"should be documented. Feel free to contribute documentation for them! " +"(Send via email to docs@python.org.)" +msgstr "" + +#: ../Doc/library/undoc.rst:11 +msgid "" +"The idea and original contents for this chapter were taken from a posting by " +"Fredrik Lundh; the specific contents of this chapter have been substantially " +"revised." +msgstr "" + +#: ../Doc/library/undoc.rst:17 +msgid "Platform specific modules" +msgstr "" + +#: ../Doc/library/undoc.rst:19 +msgid "" +"These modules are used to implement the :mod:`os.path` module, and are not " +"documented beyond this mention. There's little need to document these." +msgstr "" + +#: ../Doc/library/undoc.rst:23 +msgid ":mod:`ntpath`" +msgstr "" + +#: ../Doc/library/undoc.rst:23 +msgid "--- Implementation of :mod:`os.path` on Win32 and Win64 platforms." +msgstr "" + +#: ../Doc/library/undoc.rst:25 +msgid ":mod:`posixpath`" +msgstr "" + +#: ../Doc/library/undoc.rst:26 +msgid "--- Implementation of :mod:`os.path` on POSIX." +msgstr "" + +#: ../Doc/library/unicodedata.rst:2 +msgid ":mod:`unicodedata` --- Unicode Database" +msgstr "" + +#: ../Doc/library/unicodedata.rst:18 +msgid "" +"This module provides access to the Unicode Character Database (UCD) which " +"defines character properties for all Unicode characters. The data contained " +"in this database is compiled from the `UCD version 9.0.0 `_." +msgstr "" + +#: ../Doc/library/unicodedata.rst:23 +msgid "" +"The module uses the same names and symbols as defined by Unicode Standard " +"Annex #44, `\"Unicode Character Database\" `_. It defines the following functions:" +msgstr "" + +#: ../Doc/library/unicodedata.rst:31 +msgid "" +"Look up character by name. If a character with the given name is found, " +"return the corresponding character. If not found, :exc:`KeyError` is raised." +msgstr "" + +#: ../Doc/library/unicodedata.rst:34 +msgid "Support for name aliases [#]_ and named sequences [#]_ has been added." +msgstr "" + +#: ../Doc/library/unicodedata.rst:40 +msgid "" +"Returns the name assigned to the character *chr* as a string. If no name is " +"defined, *default* is returned, or, if not given, :exc:`ValueError` is " +"raised." +msgstr "" + +#: ../Doc/library/unicodedata.rst:47 +msgid "" +"Returns the decimal value assigned to the character *chr* as integer. If no " +"such value is defined, *default* is returned, or, if not given, :exc:" +"`ValueError` is raised." +msgstr "" + +#: ../Doc/library/unicodedata.rst:54 +msgid "" +"Returns the digit value assigned to the character *chr* as integer. If no " +"such value is defined, *default* is returned, or, if not given, :exc:" +"`ValueError` is raised." +msgstr "" + +#: ../Doc/library/unicodedata.rst:61 +msgid "" +"Returns the numeric value assigned to the character *chr* as float. If no " +"such value is defined, *default* is returned, or, if not given, :exc:" +"`ValueError` is raised." +msgstr "" + +#: ../Doc/library/unicodedata.rst:68 +msgid "Returns the general category assigned to the character *chr* as string." +msgstr "" + +#: ../Doc/library/unicodedata.rst:74 +msgid "" +"Returns the bidirectional class assigned to the character *chr* as string. " +"If no such value is defined, an empty string is returned." +msgstr "" + +#: ../Doc/library/unicodedata.rst:80 +msgid "" +"Returns the canonical combining class assigned to the character *chr* as " +"integer. Returns ``0`` if no combining class is defined." +msgstr "" + +#: ../Doc/library/unicodedata.rst:86 +msgid "Returns the east asian width assigned to the character *chr* as string." +msgstr "" + +#: ../Doc/library/unicodedata.rst:92 +msgid "" +"Returns the mirrored property assigned to the character *chr* as integer. " +"Returns ``1`` if the character has been identified as a \"mirrored\" " +"character in bidirectional text, ``0`` otherwise." +msgstr "" + +#: ../Doc/library/unicodedata.rst:99 +msgid "" +"Returns the character decomposition mapping assigned to the character *chr* " +"as string. An empty string is returned in case no such mapping is defined." +msgstr "" + +#: ../Doc/library/unicodedata.rst:106 +msgid "" +"Return the normal form *form* for the Unicode string *unistr*. Valid values " +"for *form* are 'NFC', 'NFKC', 'NFD', and 'NFKD'." +msgstr "" + +#: ../Doc/library/unicodedata.rst:109 +msgid "" +"The Unicode standard defines various normalization forms of a Unicode " +"string, based on the definition of canonical equivalence and compatibility " +"equivalence. In Unicode, several characters can be expressed in various way. " +"For example, the character U+00C7 (LATIN CAPITAL LETTER C WITH CEDILLA) can " +"also be expressed as the sequence U+0043 (LATIN CAPITAL LETTER C) U+0327 " +"(COMBINING CEDILLA)." +msgstr "" + +#: ../Doc/library/unicodedata.rst:115 +msgid "" +"For each character, there are two normal forms: normal form C and normal " +"form D. Normal form D (NFD) is also known as canonical decomposition, and " +"translates each character into its decomposed form. Normal form C (NFC) " +"first applies a canonical decomposition, then composes pre-combined " +"characters again." +msgstr "" + +#: ../Doc/library/unicodedata.rst:120 +msgid "" +"In addition to these two forms, there are two additional normal forms based " +"on compatibility equivalence. In Unicode, certain characters are supported " +"which normally would be unified with other characters. For example, U+2160 " +"(ROMAN NUMERAL ONE) is really the same thing as U+0049 (LATIN CAPITAL LETTER " +"I). However, it is supported in Unicode for compatibility with existing " +"character sets (e.g. gb2312)." +msgstr "" + +#: ../Doc/library/unicodedata.rst:127 +msgid "" +"The normal form KD (NFKD) will apply the compatibility decomposition, i.e. " +"replace all compatibility characters with their equivalents. The normal form " +"KC (NFKC) first applies the compatibility decomposition, followed by the " +"canonical composition." +msgstr "" + +#: ../Doc/library/unicodedata.rst:132 +msgid "" +"Even if two unicode strings are normalized and look the same to a human " +"reader, if one has combining characters and the other doesn't, they may not " +"compare equal." +msgstr "" + +#: ../Doc/library/unicodedata.rst:137 +msgid "In addition, the module exposes the following constant:" +msgstr "" + +#: ../Doc/library/unicodedata.rst:141 +msgid "The version of the Unicode database used in this module." +msgstr "" + +#: ../Doc/library/unicodedata.rst:146 +msgid "" +"This is an object that has the same methods as the entire module, but uses " +"the Unicode database version 3.2 instead, for applications that require this " +"specific version of the Unicode database (such as IDNA)." +msgstr "" + +#: ../Doc/library/unicodedata.rst:171 +msgid "http://www.unicode.org/Public/9.0.0/ucd/NameAliases.txt" +msgstr "" + +#: ../Doc/library/unicodedata.rst:173 +msgid "http://www.unicode.org/Public/9.0.0/ucd/NamedSequences.txt" +msgstr "" + +#: ../Doc/library/unittest.rst:2 +msgid ":mod:`unittest` --- Unit testing framework" +msgstr "" + +#: ../Doc/library/unittest.rst:12 +msgid "**Source code:** :source:`Lib/unittest/__init__.py`" +msgstr "" + +#: ../Doc/library/unittest.rst:16 +msgid "" +"(If you are already familiar with the basic concepts of testing, you might " +"want to skip to :ref:`the list of assert methods `.)" +msgstr "" + +#: ../Doc/library/unittest.rst:19 +msgid "" +"The :mod:`unittest` unit testing framework was originally inspired by JUnit " +"and has a similar flavor as major unit testing frameworks in other " +"languages. It supports test automation, sharing of setup and shutdown code " +"for tests, aggregation of tests into collections, and independence of the " +"tests from the reporting framework." +msgstr "" + +#: ../Doc/library/unittest.rst:25 +msgid "" +"To achieve this, :mod:`unittest` supports some important concepts in an " +"object-oriented way:" +msgstr "" + +#: ../Doc/library/unittest.rst:32 +msgid "test fixture" +msgstr "" + +#: ../Doc/library/unittest.rst:29 +msgid "" +"A :dfn:`test fixture` represents the preparation needed to perform one or " +"more tests, and any associate cleanup actions. This may involve, for " +"example, creating temporary or proxy databases, directories, or starting a " +"server process." +msgstr "" + +#: ../Doc/library/unittest.rst:37 +msgid "test case" +msgstr "" + +#: ../Doc/library/unittest.rst:35 +msgid "" +"A :dfn:`test case` is the individual unit of testing. It checks for a " +"specific response to a particular set of inputs. :mod:`unittest` provides a " +"base class, :class:`TestCase`, which may be used to create new test cases." +msgstr "" + +#: ../Doc/library/unittest.rst:41 +msgid "test suite" +msgstr "" + +#: ../Doc/library/unittest.rst:40 +msgid "" +"A :dfn:`test suite` is a collection of test cases, test suites, or both. It " +"is used to aggregate tests that should be executed together." +msgstr "" + +#: ../Doc/library/unittest.rst:48 +msgid "test runner" +msgstr "" + +#: ../Doc/library/unittest.rst:44 +msgid "" +"A :dfn:`test runner` is a component which orchestrates the execution of " +"tests and provides the outcome to the user. The runner may use a graphical " +"interface, a textual interface, or return a special value to indicate the " +"results of executing the tests." +msgstr "" + +#: ../Doc/library/unittest.rst:53 +msgid "Another test-support module with a very different flavor." +msgstr "" + +#: ../Doc/library/unittest.rst:57 +msgid "" +"`Simple Smalltalk Testing: With Patterns `_" +msgstr "" + +#: ../Doc/library/unittest.rst:56 +msgid "" +"Kent Beck's original paper on testing frameworks using the pattern shared " +"by :mod:`unittest`." +msgstr "" + +#: ../Doc/library/unittest.rst:61 +msgid "" +"`Nose `_ and `py.test `_" +msgstr "" + +#: ../Doc/library/unittest.rst:60 +msgid "" +"Third-party unittest frameworks with a lighter-weight syntax for writing " +"tests. For example, ``assert func(10) == 42``." +msgstr "" + +#: ../Doc/library/unittest.rst:65 +msgid "" +"`The Python Testing Tools Taxonomy `_" +msgstr "" + +#: ../Doc/library/unittest.rst:64 +msgid "" +"An extensive list of Python testing tools including functional testing " +"frameworks and mock object libraries." +msgstr "" + +#: ../Doc/library/unittest.rst:69 +msgid "" +"`Testing in Python Mailing List `_" +msgstr "" + +#: ../Doc/library/unittest.rst:68 +msgid "" +"A special-interest-group for discussion of testing, and testing tools, in " +"Python." +msgstr "" + +#: ../Doc/library/unittest.rst:71 +msgid "" +"The script :file:`Tools/unittestgui/unittestgui.py` in the Python source " +"distribution is a GUI tool for test discovery and execution. This is " +"intended largely for ease of use for those new to unit testing. For " +"production environments it is recommended that tests be driven by a " +"continuous integration system such as `Buildbot `_, " +"`Jenkins `_ or `Hudson `_." +msgstr "" + +#: ../Doc/library/unittest.rst:82 +msgid "Basic example" +msgstr "" + +#: ../Doc/library/unittest.rst:84 +msgid "" +"The :mod:`unittest` module provides a rich set of tools for constructing and " +"running tests. This section demonstrates that a small subset of the tools " +"suffice to meet the needs of most users." +msgstr "" + +#: ../Doc/library/unittest.rst:88 +msgid "Here is a short script to test three string methods::" +msgstr "" + +#: ../Doc/library/unittest.rst:112 +msgid "" +"A testcase is created by subclassing :class:`unittest.TestCase`. The three " +"individual tests are defined with methods whose names start with the letters " +"``test``. This naming convention informs the test runner about which " +"methods represent tests." +msgstr "" + +#: ../Doc/library/unittest.rst:117 +msgid "" +"The crux of each test is a call to :meth:`~TestCase.assertEqual` to check " +"for an expected result; :meth:`~TestCase.assertTrue` or :meth:`~TestCase." +"assertFalse` to verify a condition; or :meth:`~TestCase.assertRaises` to " +"verify that a specific exception gets raised. These methods are used " +"instead of the :keyword:`assert` statement so the test runner can accumulate " +"all test results and produce a report." +msgstr "" + +#: ../Doc/library/unittest.rst:124 +msgid "" +"The :meth:`~TestCase.setUp` and :meth:`~TestCase.tearDown` methods allow you " +"to define instructions that will be executed before and after each test " +"method. They are covered in more detail in the section :ref:`organizing-" +"tests`." +msgstr "" + +#: ../Doc/library/unittest.rst:128 +msgid "" +"The final block shows a simple way to run the tests. :func:`unittest.main` " +"provides a command-line interface to the test script. When run from the " +"command line, the above script produces an output that looks like this::" +msgstr "" + +#: ../Doc/library/unittest.rst:138 +msgid "" +"Passing the ``-v`` option to your test script will instruct :func:`unittest." +"main` to enable a higher level of verbosity, and produce the following " +"output::" +msgstr "" + +#: ../Doc/library/unittest.rst:150 +msgid "" +"The above examples show the most commonly used :mod:`unittest` features " +"which are sufficient to meet many everyday testing needs. The remainder of " +"the documentation explores the full feature set from first principles." +msgstr "" + +#: ../Doc/library/unittest.rst:160 +msgid "" +"The unittest module can be used from the command line to run tests from " +"modules, classes or even individual test methods::" +msgstr "" + +#: ../Doc/library/unittest.rst:167 +msgid "" +"You can pass in a list with any combination of module names, and fully " +"qualified class or method names." +msgstr "" + +#: ../Doc/library/unittest.rst:170 +msgid "Test modules can be specified by file path as well::" +msgstr "" + +#: ../Doc/library/unittest.rst:174 +msgid "" +"This allows you to use the shell filename completion to specify the test " +"module. The file specified must still be importable as a module. The path is " +"converted to a module name by removing the '.py' and converting path " +"separators into '.'. If you want to execute a test file that isn't " +"importable as a module you should execute the file directly instead." +msgstr "" + +#: ../Doc/library/unittest.rst:180 +msgid "" +"You can run tests with more detail (higher verbosity) by passing in the -v " +"flag::" +msgstr "" + +#: ../Doc/library/unittest.rst:184 +msgid "" +"When executed without arguments :ref:`unittest-test-discovery` is started::" +msgstr "" + +#: ../Doc/library/unittest.rst:188 +msgid "For a list of all the command-line options::" +msgstr "" + +#: ../Doc/library/unittest.rst:192 +msgid "" +"In earlier versions it was only possible to run individual test methods and " +"not modules or classes." +msgstr "" + +#: ../Doc/library/unittest.rst:198 +msgid "Command-line options" +msgstr "" + +#: ../Doc/library/unittest.rst:200 +msgid ":program:`unittest` supports these command-line options:" +msgstr "" + +#: ../Doc/library/unittest.rst:206 +msgid "" +"The standard output and standard error streams are buffered during the test " +"run. Output during a passing test is discarded. Output is echoed normally on " +"test fail or error and is added to the failure messages." +msgstr "" + +#: ../Doc/library/unittest.rst:212 +msgid "" +":kbd:`Control-C` during the test run waits for the current test to end and " +"then reports all the results so far. A second :kbd:`Control-C` raises the " +"normal :exc:`KeyboardInterrupt` exception." +msgstr "" + +#: ../Doc/library/unittest.rst:216 +msgid "" +"See `Signal Handling`_ for the functions that provide this functionality." +msgstr "" + +#: ../Doc/library/unittest.rst:220 +msgid "Stop the test run on the first error or failure." +msgstr "" + +#: ../Doc/library/unittest.rst:224 +msgid "Show local variables in tracebacks." +msgstr "" + +#: ../Doc/library/unittest.rst:226 +msgid "The command-line options ``-b``, ``-c`` and ``-f`` were added." +msgstr "" + +#: ../Doc/library/unittest.rst:229 +msgid "The command-line option ``--locals``." +msgstr "" + +#: ../Doc/library/unittest.rst:232 +msgid "" +"The command line can also be used for test discovery, for running all of the " +"tests in a project or just a subset." +msgstr "" + +#: ../Doc/library/unittest.rst:239 +msgid "Test Discovery" +msgstr "" + +#: ../Doc/library/unittest.rst:243 +msgid "" +"Unittest supports simple test discovery. In order to be compatible with test " +"discovery, all of the test files must be :ref:`modules ` or :" +"ref:`packages ` (including :term:`namespace packages " +"`) importable from the top-level directory of the project " +"(this means that their filenames must be valid :ref:`identifiers " +"`)." +msgstr "" + +#: ../Doc/library/unittest.rst:250 +msgid "" +"Test discovery is implemented in :meth:`TestLoader.discover`, but can also " +"be used from the command line. The basic command-line usage is::" +msgstr "" + +#: ../Doc/library/unittest.rst:258 +msgid "" +"As a shortcut, ``python -m unittest`` is the equivalent of ``python -m " +"unittest discover``. If you want to pass arguments to test discovery the " +"``discover`` sub-command must be used explicitly." +msgstr "" + +#: ../Doc/library/unittest.rst:262 +msgid "The ``discover`` sub-command has the following options:" +msgstr "" + +#: ../Doc/library/unittest.rst:272 +msgid "Directory to start discovery (``.`` default)" +msgstr "" + +#: ../Doc/library/unittest.rst:276 +msgid "Pattern to match test files (``test*.py`` default)" +msgstr "" + +#: ../Doc/library/unittest.rst:280 +msgid "Top level directory of project (defaults to start directory)" +msgstr "" + +#: ../Doc/library/unittest.rst:282 +msgid "" +"The :option:`-s`, :option:`-p`, and :option:`-t` options can be passed in as " +"positional arguments in that order. The following two command lines are " +"equivalent::" +msgstr "" + +#: ../Doc/library/unittest.rst:289 +msgid "" +"As well as being a path it is possible to pass a package name, for example " +"``myproject.subpackage.test``, as the start directory. The package name you " +"supply will then be imported and its location on the filesystem will be used " +"as the start directory." +msgstr "" + +#: ../Doc/library/unittest.rst:296 +msgid "" +"Test discovery loads tests by importing them. Once test discovery has found " +"all the test files from the start directory you specify it turns the paths " +"into package names to import. For example :file:`foo/bar/baz.py` will be " +"imported as ``foo.bar.baz``." +msgstr "" + +#: ../Doc/library/unittest.rst:301 +msgid "" +"If you have a package installed globally and attempt test discovery on a " +"different copy of the package then the import *could* happen from the wrong " +"place. If this happens test discovery will warn you and exit." +msgstr "" + +#: ../Doc/library/unittest.rst:305 +msgid "" +"If you supply the start directory as a package name rather than a path to a " +"directory then discover assumes that whichever location it imports from is " +"the location you intended, so you will not get the warning." +msgstr "" + +#: ../Doc/library/unittest.rst:310 +msgid "" +"Test modules and packages can customize test loading and discovery by " +"through the `load_tests protocol`_." +msgstr "" + +#: ../Doc/library/unittest.rst:313 +msgid "Test discovery supports :term:`namespace packages `." +msgstr "" + +#: ../Doc/library/unittest.rst:320 +msgid "Organizing test code" +msgstr "" + +#: ../Doc/library/unittest.rst:322 +msgid "" +"The basic building blocks of unit testing are :dfn:`test cases` --- single " +"scenarios that must be set up and checked for correctness. In :mod:" +"`unittest`, test cases are represented by :class:`unittest.TestCase` " +"instances. To make your own test cases you must write subclasses of :class:" +"`TestCase` or use :class:`FunctionTestCase`." +msgstr "" + +#: ../Doc/library/unittest.rst:328 +msgid "" +"The testing code of a :class:`TestCase` instance should be entirely self " +"contained, such that it can be run either in isolation or in arbitrary " +"combination with any number of other test cases." +msgstr "" + +#: ../Doc/library/unittest.rst:332 +msgid "" +"The simplest :class:`TestCase` subclass will simply implement a test method " +"(i.e. a method whose name starts with ``test``) in order to perform specific " +"testing code::" +msgstr "" + +#: ../Doc/library/unittest.rst:343 +msgid "" +"Note that in order to test something, we use one of the :meth:`assert\\*` " +"methods provided by the :class:`TestCase` base class. If the test fails, an " +"exception will be raised, and :mod:`unittest` will identify the test case as " +"a :dfn:`failure`. Any other exceptions will be treated as :dfn:`errors`." +msgstr "" + +#: ../Doc/library/unittest.rst:348 +msgid "" +"Tests can be numerous, and their set-up can be repetitive. Luckily, we can " +"factor out set-up code by implementing a method called :meth:`~TestCase." +"setUp`, which the testing framework will automatically call for every single " +"test we run::" +msgstr "" + +#: ../Doc/library/unittest.rst:369 +msgid "" +"The order in which the various tests will be run is determined by sorting " +"the test method names with respect to the built-in ordering for strings." +msgstr "" + +#: ../Doc/library/unittest.rst:373 +msgid "" +"If the :meth:`~TestCase.setUp` method raises an exception while the test is " +"running, the framework will consider the test to have suffered an error, and " +"the test method will not be executed." +msgstr "" + +#: ../Doc/library/unittest.rst:377 +msgid "" +"Similarly, we can provide a :meth:`~TestCase.tearDown` method that tidies up " +"after the test method has been run::" +msgstr "" + +#: ../Doc/library/unittest.rst:389 +msgid "" +"If :meth:`~TestCase.setUp` succeeded, :meth:`~TestCase.tearDown` will be run " +"whether the test method succeeded or not." +msgstr "" + +#: ../Doc/library/unittest.rst:392 +msgid "" +"Such a working environment for the testing code is called a :dfn:`fixture`." +msgstr "" + +#: ../Doc/library/unittest.rst:394 +msgid "" +"Test case instances are grouped together according to the features they " +"test. :mod:`unittest` provides a mechanism for this: the :dfn:`test suite`, " +"represented by :mod:`unittest`'s :class:`TestSuite` class. In most cases, " +"calling :func:`unittest.main` will do the right thing and collect all the " +"module's test cases for you, and then execute them." +msgstr "" + +#: ../Doc/library/unittest.rst:400 +msgid "" +"However, should you want to customize the building of your test suite, you " +"can do it yourself::" +msgstr "" + +#: ../Doc/library/unittest.rst:409 +msgid "" +"You can place the definitions of test cases and test suites in the same " +"modules as the code they are to test (such as :file:`widget.py`), but there " +"are several advantages to placing the test code in a separate module, such " +"as :file:`test_widget.py`:" +msgstr "" + +#: ../Doc/library/unittest.rst:414 +msgid "The test module can be run standalone from the command line." +msgstr "" + +#: ../Doc/library/unittest.rst:416 +msgid "The test code can more easily be separated from shipped code." +msgstr "" + +#: ../Doc/library/unittest.rst:418 +msgid "" +"There is less temptation to change test code to fit the code it tests " +"without a good reason." +msgstr "" + +#: ../Doc/library/unittest.rst:421 +msgid "" +"Test code should be modified much less frequently than the code it tests." +msgstr "" + +#: ../Doc/library/unittest.rst:423 +msgid "Tested code can be refactored more easily." +msgstr "" + +#: ../Doc/library/unittest.rst:425 +msgid "" +"Tests for modules written in C must be in separate modules anyway, so why " +"not be consistent?" +msgstr "" + +#: ../Doc/library/unittest.rst:428 +msgid "" +"If the testing strategy changes, there is no need to change the source code." +msgstr "" + +#: ../Doc/library/unittest.rst:434 +msgid "Re-using old test code" +msgstr "" + +#: ../Doc/library/unittest.rst:436 +msgid "" +"Some users will find that they have existing test code that they would like " +"to run from :mod:`unittest`, without converting every old test function to " +"a :class:`TestCase` subclass." +msgstr "" + +#: ../Doc/library/unittest.rst:440 +msgid "" +"For this reason, :mod:`unittest` provides a :class:`FunctionTestCase` class. " +"This subclass of :class:`TestCase` can be used to wrap an existing test " +"function. Set-up and tear-down functions can also be provided." +msgstr "" + +#: ../Doc/library/unittest.rst:444 +msgid "Given the following test function::" +msgstr "" + +#: ../Doc/library/unittest.rst:451 +msgid "" +"one can create an equivalent test case instance as follows, with optional " +"set-up and tear-down methods::" +msgstr "" + +#: ../Doc/library/unittest.rst:460 +msgid "" +"Even though :class:`FunctionTestCase` can be used to quickly convert an " +"existing test base over to a :mod:`unittest`\\ -based system, this approach " +"is not recommended. Taking the time to set up proper :class:`TestCase` " +"subclasses will make future test refactorings infinitely easier." +msgstr "" + +#: ../Doc/library/unittest.rst:465 +msgid "" +"In some cases, the existing tests may have been written using the :mod:" +"`doctest` module. If so, :mod:`doctest` provides a :class:`DocTestSuite` " +"class that can automatically build :class:`unittest.TestSuite` instances " +"from the existing :mod:`doctest`\\ -based tests." +msgstr "" + +#: ../Doc/library/unittest.rst:474 +msgid "Skipping tests and expected failures" +msgstr "" + +#: ../Doc/library/unittest.rst:478 +msgid "" +"Unittest supports skipping individual test methods and even whole classes of " +"tests. In addition, it supports marking a test as an \"expected failure,\" " +"a test that is broken and will fail, but shouldn't be counted as a failure " +"on a :class:`TestResult`." +msgstr "" + +#: ../Doc/library/unittest.rst:483 +msgid "" +"Skipping a test is simply a matter of using the :func:`skip` :term:" +"`decorator` or one of its conditional variants." +msgstr "" + +#: ../Doc/library/unittest.rst:486 +msgid "Basic skipping looks like this::" +msgstr "" + +#: ../Doc/library/unittest.rst:505 +msgid "This is the output of running the example above in verbose mode::" +msgstr "" + +#: ../Doc/library/unittest.rst:516 +msgid "Classes can be skipped just like methods::" +msgstr "" + +#: ../Doc/library/unittest.rst:523 +msgid "" +":meth:`TestCase.setUp` can also skip the test. This is useful when a " +"resource that needs to be set up is not available." +msgstr "" + +#: ../Doc/library/unittest.rst:526 +msgid "Expected failures use the :func:`expectedFailure` decorator. ::" +msgstr "" + +#: ../Doc/library/unittest.rst:533 +msgid "" +"It's easy to roll your own skipping decorators by making a decorator that " +"calls :func:`skip` on the test when it wants it to be skipped. This " +"decorator skips the test unless the passed object has a certain attribute::" +msgstr "" + +#: ../Doc/library/unittest.rst:542 +msgid "The following decorators implement test skipping and expected failures:" +msgstr "" + +#: ../Doc/library/unittest.rst:546 +msgid "" +"Unconditionally skip the decorated test. *reason* should describe why the " +"test is being skipped." +msgstr "" + +#: ../Doc/library/unittest.rst:551 +msgid "Skip the decorated test if *condition* is true." +msgstr "" + +#: ../Doc/library/unittest.rst:555 +msgid "Skip the decorated test unless *condition* is true." +msgstr "" + +#: ../Doc/library/unittest.rst:559 +msgid "" +"Mark the test as an expected failure. If the test fails when run, the test " +"is not counted as a failure." +msgstr "" + +#: ../Doc/library/unittest.rst:564 +msgid "This exception is raised to skip a test." +msgstr "" + +#: ../Doc/library/unittest.rst:566 +msgid "" +"Usually you can use :meth:`TestCase.skipTest` or one of the skipping " +"decorators instead of raising this directly." +msgstr "" + +#: ../Doc/library/unittest.rst:569 +msgid "" +"Skipped tests will not have :meth:`~TestCase.setUp` or :meth:`~TestCase." +"tearDown` run around them. Skipped classes will not have :meth:`~TestCase." +"setUpClass` or :meth:`~TestCase.tearDownClass` run. Skipped modules will not " +"have :func:`setUpModule` or :func:`tearDownModule` run." +msgstr "" + +#: ../Doc/library/unittest.rst:577 +msgid "Distinguishing test iterations using subtests" +msgstr "" + +#: ../Doc/library/unittest.rst:581 +msgid "" +"When some of your tests differ only by a some very small differences, for " +"instance some parameters, unittest allows you to distinguish them inside the " +"body of a test method using the :meth:`~TestCase.subTest` context manager." +msgstr "" + +#: ../Doc/library/unittest.rst:585 +msgid "For example, the following test::" +msgstr "" + +#: ../Doc/library/unittest.rst:597 +msgid "will produce the following output::" +msgstr "" + +#: ../Doc/library/unittest.rst:623 +msgid "" +"Without using a subtest, execution would stop after the first failure, and " +"the error would be less easy to diagnose because the value of ``i`` wouldn't " +"be displayed::" +msgstr "" + +#: ../Doc/library/unittest.rst:641 +msgid "This section describes in depth the API of :mod:`unittest`." +msgstr "" + +#: ../Doc/library/unittest.rst:647 +msgid "Test cases" +msgstr "" + +#: ../Doc/library/unittest.rst:651 +msgid "" +"Instances of the :class:`TestCase` class represent the logical test units in " +"the :mod:`unittest` universe. This class is intended to be used as a base " +"class, with specific tests being implemented by concrete subclasses. This " +"class implements the interface needed by the test runner to allow it to " +"drive the tests, and methods that the test code can use to check for and " +"report various kinds of failure." +msgstr "" + +#: ../Doc/library/unittest.rst:658 +msgid "" +"Each instance of :class:`TestCase` will run a single base method: the method " +"named *methodName*. In most uses of :class:`TestCase`, you will neither " +"change the *methodName* nor reimplement the default ``runTest()`` method." +msgstr "" + +#: ../Doc/library/unittest.rst:663 +msgid "" +":class:`TestCase` can be instantiated successfully without providing a " +"*methodName*. This makes it easier to experiment with :class:`TestCase` from " +"the interactive interpreter." +msgstr "" + +#: ../Doc/library/unittest.rst:668 +msgid "" +":class:`TestCase` instances provide three groups of methods: one group used " +"to run the test, another used by the test implementation to check conditions " +"and report failures, and some inquiry methods allowing information about the " +"test itself to be gathered." +msgstr "" + +#: ../Doc/library/unittest.rst:673 +msgid "Methods in the first group (running the test) are:" +msgstr "" + +#: ../Doc/library/unittest.rst:677 +msgid "" +"Method called to prepare the test fixture. This is called immediately " +"before calling the test method; other than :exc:`AssertionError` or :exc:" +"`SkipTest`, any exception raised by this method will be considered an error " +"rather than a test failure. The default implementation does nothing." +msgstr "" + +#: ../Doc/library/unittest.rst:685 +msgid "" +"Method called immediately after the test method has been called and the " +"result recorded. This is called even if the test method raised an " +"exception, so the implementation in subclasses may need to be particularly " +"careful about checking internal state. Any exception, other than :exc:" +"`AssertionError` or :exc:`SkipTest`, raised by this method will be " +"considered an additional error rather than a test failure (thus increasing " +"the total number of reported errors). This method will only be called if " +"the :meth:`setUp` succeeds, regardless of the outcome of the test method. " +"The default implementation does nothing." +msgstr "" + +#: ../Doc/library/unittest.rst:698 +msgid "" +"A class method called before tests in an individual class run. " +"``setUpClass`` is called with the class as the only argument and must be " +"decorated as a :func:`classmethod`::" +msgstr "" + +#: ../Doc/library/unittest.rst:706 ../Doc/library/unittest.rst:721 +msgid "See `Class and Module Fixtures`_ for more details." +msgstr "" + +#: ../Doc/library/unittest.rst:713 +msgid "" +"A class method called after tests in an individual class have run. " +"``tearDownClass`` is called with the class as the only argument and must be " +"decorated as a :meth:`classmethod`::" +msgstr "" + +#: ../Doc/library/unittest.rst:728 +msgid "" +"Run the test, collecting the result into the :class:`TestResult` object " +"passed as *result*. If *result* is omitted or ``None``, a temporary result " +"object is created (by calling the :meth:`defaultTestResult` method) and " +"used. The result object is returned to :meth:`run`'s caller." +msgstr "" + +#: ../Doc/library/unittest.rst:734 +msgid "" +"The same effect may be had by simply calling the :class:`TestCase` instance." +msgstr "" + +#: ../Doc/library/unittest.rst:737 +msgid "" +"Previous versions of ``run`` did not return the result. Neither did calling " +"an instance." +msgstr "" + +#: ../Doc/library/unittest.rst:743 +msgid "" +"Calling this during a test method or :meth:`setUp` skips the current test. " +"See :ref:`unittest-skipping` for more information." +msgstr "" + +#: ../Doc/library/unittest.rst:751 +msgid "" +"Return a context manager which executes the enclosed code block as a " +"subtest. *msg* and *params* are optional, arbitrary values which are " +"displayed whenever a subtest fails, allowing you to identify them clearly." +msgstr "" + +#: ../Doc/library/unittest.rst:756 +msgid "" +"A test case can contain any number of subtest declarations, and they can be " +"arbitrarily nested." +msgstr "" + +#: ../Doc/library/unittest.rst:759 +msgid "See :ref:`subtests` for more information." +msgstr "" + +#: ../Doc/library/unittest.rst:766 +msgid "" +"Run the test without collecting the result. This allows exceptions raised " +"by the test to be propagated to the caller, and can be used to support " +"running tests under a debugger." +msgstr "" + +#: ../Doc/library/unittest.rst:772 +msgid "" +"The :class:`TestCase` class provides several assert methods to check for and " +"report failures. The following table lists the most commonly used methods " +"(see the tables below for more assert methods):" +msgstr "" + +#: ../Doc/library/unittest.rst:777 ../Doc/library/unittest.rst:899 +#: ../Doc/library/unittest.rst:1091 ../Doc/library/unittest.rst:1215 +msgid "Method" +msgstr "" + +#: ../Doc/library/unittest.rst:777 ../Doc/library/unittest.rst:899 +#: ../Doc/library/unittest.rst:1091 +msgid "Checks that" +msgstr "" + +#: ../Doc/library/unittest.rst:777 ../Doc/library/unittest.rst:899 +#: ../Doc/library/unittest.rst:1091 ../Doc/library/unittest.rst:1215 +msgid "New in" +msgstr "" + +#: ../Doc/library/unittest.rst:779 +msgid ":meth:`assertEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:782 +msgid ":meth:`assertNotEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:785 +msgid ":meth:`assertTrue(x) `" +msgstr "" + +#: ../Doc/library/unittest.rst:785 +msgid "``bool(x) is True``" +msgstr "" + +#: ../Doc/library/unittest.rst:788 +msgid ":meth:`assertFalse(x) `" +msgstr "" + +#: ../Doc/library/unittest.rst:788 +msgid "``bool(x) is False``" +msgstr "" + +#: ../Doc/library/unittest.rst:791 +msgid ":meth:`assertIs(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:791 ../Doc/library/unittest.rst:794 +#: ../Doc/library/unittest.rst:797 ../Doc/library/unittest.rst:800 +#: ../Doc/library/unittest.rst:803 ../Doc/library/unittest.rst:806 +#: ../Doc/library/unittest.rst:904 ../Doc/library/unittest.rst:1099 +#: ../Doc/library/unittest.rst:1102 ../Doc/library/unittest.rst:1105 +#: ../Doc/library/unittest.rst:1108 ../Doc/library/unittest.rst:1111 +#: ../Doc/library/unittest.rst:1217 ../Doc/library/unittest.rst:1220 +#: ../Doc/library/unittest.rst:1223 ../Doc/library/unittest.rst:1226 +#: ../Doc/library/unittest.rst:1229 ../Doc/library/unittest.rst:1232 +msgid "3.1" +msgstr "" + +#: ../Doc/library/unittest.rst:794 +msgid ":meth:`assertIsNot(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:797 +msgid ":meth:`assertIsNone(x) `" +msgstr "" + +#: ../Doc/library/unittest.rst:797 +msgid "``x is None``" +msgstr "" + +#: ../Doc/library/unittest.rst:800 +msgid ":meth:`assertIsNotNone(x) `" +msgstr "" + +#: ../Doc/library/unittest.rst:800 +msgid "``x is not None``" +msgstr "" + +#: ../Doc/library/unittest.rst:803 +msgid ":meth:`assertIn(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:803 +msgid "``a in b``" +msgstr "" + +#: ../Doc/library/unittest.rst:806 +msgid ":meth:`assertNotIn(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:806 +msgid "``a not in b``" +msgstr "" + +#: ../Doc/library/unittest.rst:809 +msgid ":meth:`assertIsInstance(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:809 +msgid "``isinstance(a, b)``" +msgstr "" + +#: ../Doc/library/unittest.rst:809 ../Doc/library/unittest.rst:812 +#: ../Doc/library/unittest.rst:907 ../Doc/library/unittest.rst:910 +#: ../Doc/library/unittest.rst:1114 ../Doc/library/unittest.rst:1117 +msgid "3.2" +msgstr "" + +#: ../Doc/library/unittest.rst:812 +msgid ":meth:`assertNotIsInstance(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:812 +msgid "``not isinstance(a, b)``" +msgstr "" + +#: ../Doc/library/unittest.rst:816 +msgid "" +"All the assert methods accept a *msg* argument that, if specified, is used " +"as the error message on failure (see also :data:`longMessage`). Note that " +"the *msg* keyword argument can be passed to :meth:`assertRaises`, :meth:" +"`assertRaisesRegex`, :meth:`assertWarns`, :meth:`assertWarnsRegex` only when " +"they are used as a context manager." +msgstr "" + +#: ../Doc/library/unittest.rst:824 +msgid "" +"Test that *first* and *second* are equal. If the values do not compare " +"equal, the test will fail." +msgstr "" + +#: ../Doc/library/unittest.rst:827 +msgid "" +"In addition, if *first* and *second* are the exact same type and one of " +"list, tuple, dict, set, frozenset or str or any type that a subclass " +"registers with :meth:`addTypeEqualityFunc` the type-specific equality " +"function will be called in order to generate a more useful default error " +"message (see also the :ref:`list of type-specific methods `)." +msgstr "" + +#: ../Doc/library/unittest.rst:834 +msgid "Added the automatic calling of type-specific equality function." +msgstr "" + +#: ../Doc/library/unittest.rst:837 +msgid "" +":meth:`assertMultiLineEqual` added as the default type equality function for " +"comparing strings." +msgstr "" + +#: ../Doc/library/unittest.rst:844 +msgid "" +"Test that *first* and *second* are not equal. If the values do compare " +"equal, the test will fail." +msgstr "" + +#: ../Doc/library/unittest.rst:850 +msgid "Test that *expr* is true (or false)." +msgstr "" + +#: ../Doc/library/unittest.rst:852 +msgid "" +"Note that this is equivalent to ``bool(expr) is True`` and not to ``expr is " +"True`` (use ``assertIs(expr, True)`` for the latter). This method should " +"also be avoided when more specific methods are available (e.g. " +"``assertEqual(a, b)`` instead of ``assertTrue(a == b)``), because they " +"provide a better error message in case of failure." +msgstr "" + +#: ../Doc/library/unittest.rst:862 +msgid "" +"Test that *first* and *second* evaluate (or don't evaluate) to the same " +"object." +msgstr "" + +#: ../Doc/library/unittest.rst:871 +msgid "Test that *expr* is (or is not) None." +msgstr "" + +#: ../Doc/library/unittest.rst:879 +msgid "Test that *first* is (or is not) in *second*." +msgstr "" + +#: ../Doc/library/unittest.rst:887 +msgid "" +"Test that *obj* is (or is not) an instance of *cls* (which can be a class or " +"a tuple of classes, as supported by :func:`isinstance`). To check for the " +"exact type, use :func:`assertIs(type(obj), cls) `." +msgstr "" + +#: ../Doc/library/unittest.rst:895 +msgid "" +"It is also possible to check the production of exceptions, warnings, and log " +"messages using the following methods:" +msgstr "" + +#: ../Doc/library/unittest.rst:901 +msgid ":meth:`assertRaises(exc, fun, *args, **kwds) `" +msgstr "" + +#: ../Doc/library/unittest.rst:901 +msgid "``fun(*args, **kwds)`` raises *exc*" +msgstr "" + +#: ../Doc/library/unittest.rst:904 +msgid "" +":meth:`assertRaisesRegex(exc, r, fun, *args, **kwds) `" +msgstr "" + +#: ../Doc/library/unittest.rst:904 +msgid "``fun(*args, **kwds)`` raises *exc* and the message matches regex *r*" +msgstr "" + +#: ../Doc/library/unittest.rst:907 +msgid ":meth:`assertWarns(warn, fun, *args, **kwds) `" +msgstr "" + +#: ../Doc/library/unittest.rst:907 +msgid "``fun(*args, **kwds)`` raises *warn*" +msgstr "" + +#: ../Doc/library/unittest.rst:910 +msgid "" +":meth:`assertWarnsRegex(warn, r, fun, *args, **kwds) `" +msgstr "" + +#: ../Doc/library/unittest.rst:910 +msgid "``fun(*args, **kwds)`` raises *warn* and the message matches regex *r*" +msgstr "" + +#: ../Doc/library/unittest.rst:913 +msgid ":meth:`assertLogs(logger, level) `" +msgstr "" + +#: ../Doc/library/unittest.rst:913 +msgid "The ``with`` block logs on *logger* with minimum *level*" +msgstr "" + +#: ../Doc/library/unittest.rst:913 +msgid "3.4" +msgstr "" + +#: ../Doc/library/unittest.rst:920 +msgid "" +"Test that an exception is raised when *callable* is called with any " +"positional or keyword arguments that are also passed to :meth:" +"`assertRaises`. The test passes if *exception* is raised, is an error if " +"another exception is raised, or fails if no exception is raised. To catch " +"any of a group of exceptions, a tuple containing the exception classes may " +"be passed as *exception*." +msgstr "" + +#: ../Doc/library/unittest.rst:927 +msgid "" +"If only the *exception* and possibly the *msg* arguments are given, return a " +"context manager so that the code under test can be written inline rather " +"than as a function::" +msgstr "" + +#: ../Doc/library/unittest.rst:934 +msgid "" +"When used as a context manager, :meth:`assertRaises` accepts the additional " +"keyword argument *msg*." +msgstr "" + +#: ../Doc/library/unittest.rst:937 +msgid "" +"The context manager will store the caught exception object in its :attr:" +"`exception` attribute. This can be useful if the intention is to perform " +"additional checks on the exception raised::" +msgstr "" + +#: ../Doc/library/unittest.rst:947 +msgid "Added the ability to use :meth:`assertRaises` as a context manager." +msgstr "" + +#: ../Doc/library/unittest.rst:950 +msgid "Added the :attr:`exception` attribute." +msgstr "" + +#: ../Doc/library/unittest.rst:953 ../Doc/library/unittest.rst:979 +#: ../Doc/library/unittest.rst:1020 ../Doc/library/unittest.rst:1043 +msgid "Added the *msg* keyword argument when used as a context manager." +msgstr "" + +#: ../Doc/library/unittest.rst:960 +msgid "" +"Like :meth:`assertRaises` but also tests that *regex* matches on the string " +"representation of the raised exception. *regex* may be a regular expression " +"object or a string containing a regular expression suitable for use by :func:" +"`re.search`. Examples::" +msgstr "" + +#: ../Doc/library/unittest.rst:973 +msgid "under the name ``assertRaisesRegexp``." +msgstr "" + +#: ../Doc/library/unittest.rst:976 +msgid "Renamed to :meth:`assertRaisesRegex`." +msgstr "" + +#: ../Doc/library/unittest.rst:986 +msgid "" +"Test that a warning is triggered when *callable* is called with any " +"positional or keyword arguments that are also passed to :meth:" +"`assertWarns`. The test passes if *warning* is triggered and fails if it " +"isn't. Any exception is an error. To catch any of a group of warnings, a " +"tuple containing the warning classes may be passed as *warnings*." +msgstr "" + +#: ../Doc/library/unittest.rst:993 +msgid "" +"If only the *warning* and possibly the *msg* arguments are given, return a " +"context manager so that the code under test can be written inline rather " +"than as a function::" +msgstr "" + +#: ../Doc/library/unittest.rst:1000 +msgid "" +"When used as a context manager, :meth:`assertWarns` accepts the additional " +"keyword argument *msg*." +msgstr "" + +#: ../Doc/library/unittest.rst:1003 +msgid "" +"The context manager will store the caught warning object in its :attr:" +"`warning` attribute, and the source line which triggered the warnings in " +"the :attr:`filename` and :attr:`lineno` attributes. This can be useful if " +"the intention is to perform additional checks on the warning caught::" +msgstr "" + +#: ../Doc/library/unittest.rst:1015 +msgid "" +"This method works regardless of the warning filters in place when it is " +"called." +msgstr "" + +#: ../Doc/library/unittest.rst:1027 +msgid "" +"Like :meth:`assertWarns` but also tests that *regex* matches on the message " +"of the triggered warning. *regex* may be a regular expression object or a " +"string containing a regular expression suitable for use by :func:`re." +"search`. Example::" +msgstr "" + +#: ../Doc/library/unittest.rst:1048 +msgid "" +"A context manager to test that at least one message is logged on the " +"*logger* or one of its children, with at least the given *level*." +msgstr "" + +#: ../Doc/library/unittest.rst:1052 +msgid "" +"If given, *logger* should be a :class:`logging.Logger` object or a :class:" +"`str` giving the name of a logger. The default is the root logger, which " +"will catch all messages." +msgstr "" + +#: ../Doc/library/unittest.rst:1056 +msgid "" +"If given, *level* should be either a numeric logging level or its string " +"equivalent (for example either ``\"ERROR\"`` or :attr:`logging.ERROR`). The " +"default is :attr:`logging.INFO`." +msgstr "" + +#: ../Doc/library/unittest.rst:1060 +msgid "" +"The test passes if at least one message emitted inside the ``with`` block " +"matches the *logger* and *level* conditions, otherwise it fails." +msgstr "" + +#: ../Doc/library/unittest.rst:1063 +msgid "" +"The object returned by the context manager is a recording helper which keeps " +"tracks of the matching log messages. It has two attributes:" +msgstr "" + +#: ../Doc/library/unittest.rst:1069 +msgid "" +"A list of :class:`logging.LogRecord` objects of the matching log messages." +msgstr "" + +#: ../Doc/library/unittest.rst:1074 +msgid "" +"A list of :class:`str` objects with the formatted output of matching " +"messages." +msgstr "" + +#: ../Doc/library/unittest.rst:1088 +msgid "" +"There are also other methods used to perform more specific checks, such as:" +msgstr "" + +#: ../Doc/library/unittest.rst:1093 +msgid ":meth:`assertAlmostEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1093 +msgid "``round(a-b, 7) == 0``" +msgstr "" + +#: ../Doc/library/unittest.rst:1096 +msgid ":meth:`assertNotAlmostEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1096 +msgid "``round(a-b, 7) != 0``" +msgstr "" + +#: ../Doc/library/unittest.rst:1099 +msgid ":meth:`assertGreater(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1102 +msgid ":meth:`assertGreaterEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1105 +msgid ":meth:`assertLess(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1108 +msgid ":meth:`assertLessEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1111 +msgid ":meth:`assertRegex(s, r) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1111 +msgid "``r.search(s)``" +msgstr "" + +#: ../Doc/library/unittest.rst:1114 +msgid ":meth:`assertNotRegex(s, r) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1114 +msgid "``not r.search(s)``" +msgstr "" + +#: ../Doc/library/unittest.rst:1117 +msgid ":meth:`assertCountEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1117 +msgid "" +"*a* and *b* have the same elements in the same number, regardless of their " +"order" +msgstr "" + +#: ../Doc/library/unittest.rst:1126 +msgid "" +"Test that *first* and *second* are approximately (or not approximately) " +"equal by computing the difference, rounding to the given number of decimal " +"*places* (default 7), and comparing to zero. Note that these methods round " +"the values to the given number of *decimal places* (i.e. like the :func:" +"`round` function) and not *significant digits*." +msgstr "" + +#: ../Doc/library/unittest.rst:1132 +msgid "" +"If *delta* is supplied instead of *places* then the difference between " +"*first* and *second* must be less or equal to (or greater than) *delta*." +msgstr "" + +#: ../Doc/library/unittest.rst:1135 +msgid "Supplying both *delta* and *places* raises a ``TypeError``." +msgstr "" + +#: ../Doc/library/unittest.rst:1137 +msgid "" +":meth:`assertAlmostEqual` automatically considers almost equal objects that " +"compare equal. :meth:`assertNotAlmostEqual` automatically fails if the " +"objects compare equal. Added the *delta* keyword argument." +msgstr "" + +#: ../Doc/library/unittest.rst:1148 +msgid "" +"Test that *first* is respectively >, >=, < or <= than *second* depending on " +"the method name. If not, the test will fail::" +msgstr "" + +#: ../Doc/library/unittest.rst:1160 +msgid "" +"Test that a *regex* search matches (or does not match) *text*. In case of " +"failure, the error message will include the pattern and the *text* (or the " +"pattern and the part of *text* that unexpectedly matched). *regex* may be a " +"regular expression object or a string containing a regular expression " +"suitable for use by :func:`re.search`." +msgstr "" + +#: ../Doc/library/unittest.rst:1166 +msgid "under the name ``assertRegexpMatches``." +msgstr "" + +#: ../Doc/library/unittest.rst:1168 +msgid "" +"The method ``assertRegexpMatches()`` has been renamed to :meth:`." +"assertRegex`." +msgstr "" + +#: ../Doc/library/unittest.rst:1171 +msgid ":meth:`.assertNotRegex`." +msgstr "" + +#: ../Doc/library/unittest.rst:1177 +msgid "" +"Test that sequence *first* contains the same elements as *second*, " +"regardless of their order. When they don't, an error message listing the " +"differences between the sequences will be generated." +msgstr "" + +#: ../Doc/library/unittest.rst:1181 +msgid "" +"Duplicate elements are *not* ignored when comparing *first* and *second*. It " +"verifies whether each element has the same count in both sequences. " +"Equivalent to: ``assertEqual(Counter(list(first)), Counter(list(second)))`` " +"but works with sequences of unhashable objects as well." +msgstr "" + +#: ../Doc/library/unittest.rst:1192 +msgid "" +"The :meth:`assertEqual` method dispatches the equality check for objects of " +"the same type to different type-specific methods. These methods are already " +"implemented for most of the built-in types, but it's also possible to " +"register new methods using :meth:`addTypeEqualityFunc`:" +msgstr "" + +#: ../Doc/library/unittest.rst:1199 +msgid "" +"Registers a type-specific method called by :meth:`assertEqual` to check if " +"two objects of exactly the same *typeobj* (not subclasses) compare equal. " +"*function* must take two positional arguments and a third msg=None keyword " +"argument just as :meth:`assertEqual` does. It must raise :data:`self." +"failureException(msg) ` when inequality between the first " +"two parameters is detected -- possibly providing useful information and " +"explaining the inequalities in details in the error message." +msgstr "" + +#: ../Doc/library/unittest.rst:1210 +msgid "" +"The list of type-specific methods automatically used by :meth:`~TestCase." +"assertEqual` are summarized in the following table. Note that it's usually " +"not necessary to invoke these methods directly." +msgstr "" + +#: ../Doc/library/unittest.rst:1215 +msgid "Used to compare" +msgstr "" + +#: ../Doc/library/unittest.rst:1217 +msgid ":meth:`assertMultiLineEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1217 +msgid "strings" +msgstr "" + +#: ../Doc/library/unittest.rst:1220 +msgid ":meth:`assertSequenceEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1220 +msgid "sequences" +msgstr "" + +#: ../Doc/library/unittest.rst:1223 +msgid ":meth:`assertListEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1223 +msgid "lists" +msgstr "" + +#: ../Doc/library/unittest.rst:1226 +msgid ":meth:`assertTupleEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1226 +msgid "tuples" +msgstr "" + +#: ../Doc/library/unittest.rst:1229 +msgid ":meth:`assertSetEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1229 +msgid "sets or frozensets" +msgstr "" + +#: ../Doc/library/unittest.rst:1232 +msgid ":meth:`assertDictEqual(a, b) `" +msgstr "" + +#: ../Doc/library/unittest.rst:1232 +msgid "dicts" +msgstr "" + +#: ../Doc/library/unittest.rst:1240 +msgid "" +"Test that the multiline string *first* is equal to the string *second*. When " +"not equal a diff of the two strings highlighting the differences will be " +"included in the error message. This method is used by default when comparing " +"strings with :meth:`assertEqual`." +msgstr "" + +#: ../Doc/library/unittest.rst:1250 +msgid "" +"Tests that two sequences are equal. If a *seq_type* is supplied, both " +"*first* and *second* must be instances of *seq_type* or a failure will be " +"raised. If the sequences are different an error message is constructed that " +"shows the difference between the two." +msgstr "" + +#: ../Doc/library/unittest.rst:1255 +msgid "" +"This method is not called directly by :meth:`assertEqual`, but it's used to " +"implement :meth:`assertListEqual` and :meth:`assertTupleEqual`." +msgstr "" + +#: ../Doc/library/unittest.rst:1265 +msgid "" +"Tests that two lists or tuples are equal. If not, an error message is " +"constructed that shows only the differences between the two. An error is " +"also raised if either of the parameters are of the wrong type. These methods " +"are used by default when comparing lists or tuples with :meth:`assertEqual`." +msgstr "" + +#: ../Doc/library/unittest.rst:1276 +msgid "" +"Tests that two sets are equal. If not, an error message is constructed that " +"lists the differences between the sets. This method is used by default when " +"comparing sets or frozensets with :meth:`assertEqual`." +msgstr "" + +#: ../Doc/library/unittest.rst:1280 +msgid "" +"Fails if either of *first* or *second* does not have a :meth:`set." +"difference` method." +msgstr "" + +#: ../Doc/library/unittest.rst:1288 +msgid "" +"Test that two dictionaries are equal. If not, an error message is " +"constructed that shows the differences in the dictionaries. This method will " +"be used by default to compare dictionaries in calls to :meth:`assertEqual`." +msgstr "" + +#: ../Doc/library/unittest.rst:1299 +msgid "" +"Finally the :class:`TestCase` provides the following methods and attributes:" +msgstr "" + +#: ../Doc/library/unittest.rst:1304 +msgid "" +"Signals a test failure unconditionally, with *msg* or ``None`` for the error " +"message." +msgstr "" + +#: ../Doc/library/unittest.rst:1310 +msgid "" +"This class attribute gives the exception raised by the test method. If a " +"test framework needs to use a specialized exception, possibly to carry " +"additional information, it must subclass this exception in order to \"play " +"fair\" with the framework. The initial value of this attribute is :exc:" +"`AssertionError`." +msgstr "" + +#: ../Doc/library/unittest.rst:1319 +msgid "" +"This class attribute determines what happens when a custom failure message " +"is passed as the msg argument to an assertXYY call that fails. ``True`` is " +"the default value. In this case, the custom message is appended to the end " +"of the standard failure message. When set to ``False``, the custom message " +"replaces the standard message." +msgstr "" + +#: ../Doc/library/unittest.rst:1325 +msgid "" +"The class setting can be overridden in individual test methods by assigning " +"an instance attribute, self.longMessage, to ``True`` or ``False`` before " +"calling the assert methods." +msgstr "" + +#: ../Doc/library/unittest.rst:1329 +msgid "The class setting gets reset before each test call." +msgstr "" + +#: ../Doc/library/unittest.rst:1336 +msgid "" +"This attribute controls the maximum length of diffs output by assert methods " +"that report diffs on failure. It defaults to 80*8 characters. Assert methods " +"affected by this attribute are :meth:`assertSequenceEqual` (including all " +"the sequence comparison methods that delegate to it), :meth:" +"`assertDictEqual` and :meth:`assertMultiLineEqual`." +msgstr "" + +#: ../Doc/library/unittest.rst:1343 +msgid "" +"Setting ``maxDiff`` to None means that there is no maximum length of diffs." +msgstr "" + +#: ../Doc/library/unittest.rst:1349 +msgid "" +"Testing frameworks can use the following methods to collect information on " +"the test:" +msgstr "" + +#: ../Doc/library/unittest.rst:1355 +msgid "" +"Return the number of tests represented by this test object. For :class:" +"`TestCase` instances, this will always be ``1``." +msgstr "" + +#: ../Doc/library/unittest.rst:1361 +msgid "" +"Return an instance of the test result class that should be used for this " +"test case class (if no other result instance is provided to the :meth:`run` " +"method)." +msgstr "" + +#: ../Doc/library/unittest.rst:1365 +msgid "" +"For :class:`TestCase` instances, this will always be an instance of :class:" +"`TestResult`; subclasses of :class:`TestCase` should override this as " +"necessary." +msgstr "" + +#: ../Doc/library/unittest.rst:1372 +msgid "" +"Return a string identifying the specific test case. This is usually the " +"full name of the test method, including the module and class name." +msgstr "" + +#: ../Doc/library/unittest.rst:1378 +msgid "" +"Returns a description of the test, or ``None`` if no description has been " +"provided. The default implementation of this method returns the first line " +"of the test method's docstring, if available, or ``None``." +msgstr "" + +#: ../Doc/library/unittest.rst:1383 +msgid "" +"In 3.1 this was changed to add the test name to the short description even " +"in the presence of a docstring. This caused compatibility issues with " +"unittest extensions and adding the test name was moved to the :class:" +"`TextTestResult` in Python 3.2." +msgstr "" + +#: ../Doc/library/unittest.rst:1392 +msgid "" +"Add a function to be called after :meth:`tearDown` to cleanup resources used " +"during the test. Functions will be called in reverse order to the order they " +"are added (:abbr:`LIFO (last-in, first-out)`). They are called with any " +"arguments and keyword arguments passed into :meth:`addCleanup` when they are " +"added." +msgstr "" + +#: ../Doc/library/unittest.rst:1398 +msgid "" +"If :meth:`setUp` fails, meaning that :meth:`tearDown` is not called, then " +"any cleanup functions added will still be called." +msgstr "" + +#: ../Doc/library/unittest.rst:1406 +msgid "" +"This method is called unconditionally after :meth:`tearDown`, or after :meth:" +"`setUp` if :meth:`setUp` raises an exception." +msgstr "" + +#: ../Doc/library/unittest.rst:1409 +msgid "" +"It is responsible for calling all the cleanup functions added by :meth:" +"`addCleanup`. If you need cleanup functions to be called *prior* to :meth:" +"`tearDown` then you can call :meth:`doCleanups` yourself." +msgstr "" + +#: ../Doc/library/unittest.rst:1414 +msgid "" +":meth:`doCleanups` pops methods off the stack of cleanup functions one at a " +"time, so it can be called at any time." +msgstr "" + +#: ../Doc/library/unittest.rst:1422 +msgid "" +"This class implements the portion of the :class:`TestCase` interface which " +"allows the test runner to drive the test, but does not provide the methods " +"which test code can use to check and report errors. This is used to create " +"test cases using legacy test code, allowing it to be integrated into a :mod:" +"`unittest`-based test framework." +msgstr "" + +#: ../Doc/library/unittest.rst:1432 +msgid "Deprecated aliases" +msgstr "" + +#: ../Doc/library/unittest.rst:1434 +msgid "" +"For historical reasons, some of the :class:`TestCase` methods had one or " +"more aliases that are now deprecated. The following table lists the correct " +"names along with their deprecated aliases:" +msgstr "" + +#: ../Doc/library/unittest.rst:1439 +msgid "Method Name" +msgstr "" + +#: ../Doc/library/unittest.rst:1439 +msgid "Deprecated alias" +msgstr "" + +#: ../Doc/library/unittest.rst:1441 +msgid ":meth:`.assertEqual`" +msgstr "" + +#: ../Doc/library/unittest.rst:1441 +msgid "failUnlessEqual" +msgstr "" + +#: ../Doc/library/unittest.rst:1441 +msgid "assertEquals" +msgstr "" + +#: ../Doc/library/unittest.rst:1442 +msgid ":meth:`.assertNotEqual`" +msgstr "" + +#: ../Doc/library/unittest.rst:1442 +msgid "failIfEqual" +msgstr "" + +#: ../Doc/library/unittest.rst:1442 +msgid "assertNotEquals" +msgstr "" + +#: ../Doc/library/unittest.rst:1443 +msgid ":meth:`.assertTrue`" +msgstr "" + +#: ../Doc/library/unittest.rst:1443 +msgid "failUnless" +msgstr "" + +#: ../Doc/library/unittest.rst:1443 +msgid "assert\\_" +msgstr "" + +#: ../Doc/library/unittest.rst:1444 +msgid ":meth:`.assertFalse`" +msgstr "" + +#: ../Doc/library/unittest.rst:1444 +msgid "failIf" +msgstr "" + +#: ../Doc/library/unittest.rst:1445 +msgid ":meth:`.assertRaises`" +msgstr "" + +#: ../Doc/library/unittest.rst:1445 +msgid "failUnlessRaises" +msgstr "" + +#: ../Doc/library/unittest.rst:1446 +msgid ":meth:`.assertAlmostEqual`" +msgstr "" + +#: ../Doc/library/unittest.rst:1446 +msgid "failUnlessAlmostEqual" +msgstr "" + +#: ../Doc/library/unittest.rst:1446 +msgid "assertAlmostEquals" +msgstr "" + +#: ../Doc/library/unittest.rst:1447 +msgid ":meth:`.assertNotAlmostEqual`" +msgstr "" + +#: ../Doc/library/unittest.rst:1447 +msgid "failIfAlmostEqual" +msgstr "" + +#: ../Doc/library/unittest.rst:1447 +msgid "assertNotAlmostEquals" +msgstr "" + +#: ../Doc/library/unittest.rst:1448 +msgid ":meth:`.assertRegex`" +msgstr "" + +#: ../Doc/library/unittest.rst:1448 +msgid "assertRegexpMatches" +msgstr "" + +#: ../Doc/library/unittest.rst:1449 +msgid ":meth:`.assertRaisesRegex`" +msgstr "" + +#: ../Doc/library/unittest.rst:1449 +msgid "assertRaisesRegexp" +msgstr "" + +#: ../Doc/library/unittest.rst:1452 +msgid "the fail* aliases listed in the second column." +msgstr "" + +#: ../Doc/library/unittest.rst:1454 +msgid "the assert* aliases listed in the third column." +msgstr "" + +#: ../Doc/library/unittest.rst:1456 +msgid "" +"``assertRegexpMatches`` and ``assertRaisesRegexp`` have been renamed to :" +"meth:`.assertRegex` and :meth:`.assertRaisesRegex`" +msgstr "" + +#: ../Doc/library/unittest.rst:1464 +msgid "Grouping tests" +msgstr "" + +#: ../Doc/library/unittest.rst:1468 +msgid "" +"This class represents an aggregation of individual tests cases and test " +"suites. The class presents the interface needed by the test runner to allow " +"it to be run as any other test case. Running a :class:`TestSuite` instance " +"is the same as iterating over the suite, running each test individually." +msgstr "" + +#: ../Doc/library/unittest.rst:1473 +msgid "" +"If *tests* is given, it must be an iterable of individual test cases or " +"other test suites that will be used to build the suite initially. Additional " +"methods are provided to add test cases and suites to the collection later on." +msgstr "" + +#: ../Doc/library/unittest.rst:1477 +msgid "" +":class:`TestSuite` objects behave much like :class:`TestCase` objects, " +"except they do not actually implement a test. Instead, they are used to " +"aggregate tests into groups of tests that should be run together. Some " +"additional methods are available to add tests to :class:`TestSuite` " +"instances:" +msgstr "" + +#: ../Doc/library/unittest.rst:1485 +msgid "Add a :class:`TestCase` or :class:`TestSuite` to the suite." +msgstr "" + +#: ../Doc/library/unittest.rst:1490 +msgid "" +"Add all the tests from an iterable of :class:`TestCase` and :class:" +"`TestSuite` instances to this test suite." +msgstr "" + +#: ../Doc/library/unittest.rst:1493 +msgid "" +"This is equivalent to iterating over *tests*, calling :meth:`addTest` for " +"each element." +msgstr "" + +#: ../Doc/library/unittest.rst:1496 +msgid ":class:`TestSuite` shares the following methods with :class:`TestCase`:" +msgstr "" + +#: ../Doc/library/unittest.rst:1501 +msgid "" +"Run the tests associated with this suite, collecting the result into the " +"test result object passed as *result*. Note that unlike :meth:`TestCase." +"run`, :meth:`TestSuite.run` requires the result object to be passed in." +msgstr "" + +#: ../Doc/library/unittest.rst:1509 +msgid "" +"Run the tests associated with this suite without collecting the result. This " +"allows exceptions raised by the test to be propagated to the caller and can " +"be used to support running tests under a debugger." +msgstr "" + +#: ../Doc/library/unittest.rst:1516 +msgid "" +"Return the number of tests represented by this test object, including all " +"individual tests and sub-suites." +msgstr "" + +#: ../Doc/library/unittest.rst:1522 +msgid "" +"Tests grouped by a :class:`TestSuite` are always accessed by iteration. " +"Subclasses can lazily provide tests by overriding :meth:`__iter__`. Note " +"that this method may be called several times on a single suite (for example " +"when counting tests or comparing for equality) so the tests returned by " +"repeated iterations before :meth:`TestSuite.run` must be the same for each " +"call iteration. After :meth:`TestSuite.run`, callers should not rely on the " +"tests returned by this method unless the caller uses a subclass that " +"overrides :meth:`TestSuite._removeTestAtIndex` to preserve test references." +msgstr "" + +#: ../Doc/library/unittest.rst:1532 +msgid "" +"In earlier versions the :class:`TestSuite` accessed tests directly rather " +"than through iteration, so overriding :meth:`__iter__` wasn't sufficient for " +"providing tests." +msgstr "" + +#: ../Doc/library/unittest.rst:1537 +msgid "" +"In earlier versions the :class:`TestSuite` held references to each :class:" +"`TestCase` after :meth:`TestSuite.run`. Subclasses can restore that behavior " +"by overriding :meth:`TestSuite._removeTestAtIndex`." +msgstr "" + +#: ../Doc/library/unittest.rst:1542 +msgid "" +"In the typical usage of a :class:`TestSuite` object, the :meth:`run` method " +"is invoked by a :class:`TestRunner` rather than by the end-user test harness." +msgstr "" + +#: ../Doc/library/unittest.rst:1547 +msgid "Loading and running tests" +msgstr "" + +#: ../Doc/library/unittest.rst:1551 +msgid "" +"The :class:`TestLoader` class is used to create test suites from classes and " +"modules. Normally, there is no need to create an instance of this class; " +"the :mod:`unittest` module provides an instance that can be shared as :data:" +"`unittest.defaultTestLoader`. Using a subclass or instance, however, allows " +"customization of some configurable properties." +msgstr "" + +#: ../Doc/library/unittest.rst:1557 +msgid ":class:`TestLoader` objects have the following attributes:" +msgstr "" + +#: ../Doc/library/unittest.rst:1562 +msgid "" +"A list of the non-fatal errors encountered while loading tests. Not reset by " +"the loader at any point. Fatal errors are signalled by the relevant a method " +"raising an exception to the caller. Non-fatal errors are also indicated by a " +"synthetic test that will raise the original error when run." +msgstr "" + +#: ../Doc/library/unittest.rst:1571 +msgid ":class:`TestLoader` objects have the following methods:" +msgstr "" + +#: ../Doc/library/unittest.rst:1576 +msgid "" +"Return a suite of all tests cases contained in the :class:`TestCase`\\ -" +"derived :class:`testCaseClass`." +msgstr "" + +#: ../Doc/library/unittest.rst:1579 +msgid "" +"A test case instance is created for each method named by :meth:" +"`getTestCaseNames`. By default these are the method names beginning with " +"``test``. If :meth:`getTestCaseNames` returns no methods, but the :meth:" +"`runTest` method is implemented, a single test case is created for that " +"method instead." +msgstr "" + +#: ../Doc/library/unittest.rst:1588 +msgid "" +"Return a suite of all tests cases contained in the given module. This method " +"searches *module* for classes derived from :class:`TestCase` and creates an " +"instance of the class for each test method defined for the class." +msgstr "" + +#: ../Doc/library/unittest.rst:1595 +msgid "" +"While using a hierarchy of :class:`TestCase`\\ -derived classes can be " +"convenient in sharing fixtures and helper functions, defining test methods " +"on base classes that are not intended to be instantiated directly does not " +"play well with this method. Doing so, however, can be useful when the " +"fixtures are different and defined in subclasses." +msgstr "" + +#: ../Doc/library/unittest.rst:1601 +msgid "" +"If a module provides a ``load_tests`` function it will be called to load the " +"tests. This allows modules to customize test loading. This is the " +"`load_tests protocol`_. The *pattern* argument is passed as the third " +"argument to ``load_tests``." +msgstr "" + +#: ../Doc/library/unittest.rst:1606 +msgid "Support for ``load_tests`` added." +msgstr "" + +#: ../Doc/library/unittest.rst:1609 +msgid "" +"The undocumented and unofficial *use_load_tests* default argument is " +"deprecated and ignored, although it is still accepted for backward " +"compatibility. The method also now accepts a keyword-only argument " +"*pattern* which is passed to ``load_tests`` as the third argument." +msgstr "" + +#: ../Doc/library/unittest.rst:1618 +msgid "Return a suite of all tests cases given a string specifier." +msgstr "" + +#: ../Doc/library/unittest.rst:1620 +msgid "" +"The specifier *name* is a \"dotted name\" that may resolve either to a " +"module, a test case class, a test method within a test case class, a :class:" +"`TestSuite` instance, or a callable object which returns a :class:`TestCase` " +"or :class:`TestSuite` instance. These checks are applied in the order " +"listed here; that is, a method on a possible test case class will be picked " +"up as \"a test method within a test case class\", rather than \"a callable " +"object\"." +msgstr "" + +#: ../Doc/library/unittest.rst:1628 +msgid "" +"For example, if you have a module :mod:`SampleTests` containing a :class:" +"`TestCase`\\ -derived class :class:`SampleTestCase` with three test methods " +"(:meth:`test_one`, :meth:`test_two`, and :meth:`test_three`), the specifier " +"``'SampleTests.SampleTestCase'`` would cause this method to return a suite " +"which will run all three test methods. Using the specifier ``'SampleTests." +"SampleTestCase.test_two'`` would cause it to return a test suite which will " +"run only the :meth:`test_two` test method. The specifier can refer to " +"modules and packages which have not been imported; they will be imported as " +"a side-effect." +msgstr "" + +#: ../Doc/library/unittest.rst:1638 +msgid "The method optionally resolves *name* relative to the given *module*." +msgstr "" + +#: ../Doc/library/unittest.rst:1640 +msgid "" +"If an :exc:`ImportError` or :exc:`AttributeError` occurs while traversing " +"*name* then a synthetic test that raises that error when run will be " +"returned. These errors are included in the errors accumulated by self.errors." +msgstr "" + +#: ../Doc/library/unittest.rst:1649 +msgid "" +"Similar to :meth:`loadTestsFromName`, but takes a sequence of names rather " +"than a single name. The return value is a test suite which supports all the " +"tests defined for each name." +msgstr "" + +#: ../Doc/library/unittest.rst:1656 +msgid "" +"Return a sorted sequence of method names found within *testCaseClass*; this " +"should be a subclass of :class:`TestCase`." +msgstr "" + +#: ../Doc/library/unittest.rst:1662 +msgid "" +"Find all the test modules by recursing into subdirectories from the " +"specified start directory, and return a TestSuite object containing them. " +"Only test files that match *pattern* will be loaded. (Using shell style " +"pattern matching.) Only module names that are importable (i.e. are valid " +"Python identifiers) will be loaded." +msgstr "" + +#: ../Doc/library/unittest.rst:1668 +msgid "" +"All test modules must be importable from the top level of the project. If " +"the start directory is not the top level directory then the top level " +"directory must be specified separately." +msgstr "" + +#: ../Doc/library/unittest.rst:1672 +msgid "" +"If importing a module fails, for example due to a syntax error, then this " +"will be recorded as a single error and discovery will continue. If the " +"import failure is due to :exc:`SkipTest` being raised, it will be recorded " +"as a skip instead of an error." +msgstr "" + +#: ../Doc/library/unittest.rst:1677 +msgid "" +"If a package (a directory containing a file named :file:`__init__.py`) is " +"found, the package will be checked for a ``load_tests`` function. If this " +"exists then it will be called ``package.load_tests(loader, tests, " +"pattern)``. Test discovery takes care to ensure that a package is only " +"checked for tests once during an invocation, even if the load_tests function " +"itself calls ``loader.discover``." +msgstr "" + +#: ../Doc/library/unittest.rst:1685 +msgid "" +"If ``load_tests`` exists then discovery does *not* recurse into the package, " +"``load_tests`` is responsible for loading all tests in the package." +msgstr "" + +#: ../Doc/library/unittest.rst:1689 +msgid "" +"The pattern is deliberately not stored as a loader attribute so that " +"packages can continue discovery themselves. *top_level_dir* is stored so " +"``load_tests`` does not need to pass this argument in to ``loader." +"discover()``." +msgstr "" + +#: ../Doc/library/unittest.rst:1694 +msgid "*start_dir* can be a dotted module name as well as a directory." +msgstr "" + +#: ../Doc/library/unittest.rst:1698 +msgid "" +"Modules that raise :exc:`SkipTest` on import are recorded as skips, not " +"errors. Discovery works for :term:`namespace packages `. " +"Paths are sorted before being imported so that execution order is the same " +"even if the underlying file system's ordering is not dependent on file " +"name." +msgstr "" + +#: ../Doc/library/unittest.rst:1706 +msgid "" +"Found packages are now checked for ``load_tests`` regardless of whether " +"their path matches *pattern*, because it is impossible for a package name to " +"match the default pattern." +msgstr "" + +#: ../Doc/library/unittest.rst:1712 +msgid "" +"The following attributes of a :class:`TestLoader` can be configured either " +"by subclassing or assignment on an instance:" +msgstr "" + +#: ../Doc/library/unittest.rst:1718 +msgid "" +"String giving the prefix of method names which will be interpreted as test " +"methods. The default value is ``'test'``." +msgstr "" + +#: ../Doc/library/unittest.rst:1721 +msgid "" +"This affects :meth:`getTestCaseNames` and all the :meth:`loadTestsFrom\\*` " +"methods." +msgstr "" + +#: ../Doc/library/unittest.rst:1727 +msgid "" +"Function to be used to compare method names when sorting them in :meth:" +"`getTestCaseNames` and all the :meth:`loadTestsFrom\\*` methods." +msgstr "" + +#: ../Doc/library/unittest.rst:1733 +msgid "" +"Callable object that constructs a test suite from a list of tests. No " +"methods on the resulting object are needed. The default value is the :class:" +"`TestSuite` class." +msgstr "" + +#: ../Doc/library/unittest.rst:1737 +msgid "This affects all the :meth:`loadTestsFrom\\*` methods." +msgstr "" + +#: ../Doc/library/unittest.rst:1742 +msgid "" +"This class is used to compile information about which tests have succeeded " +"and which have failed." +msgstr "" + +#: ../Doc/library/unittest.rst:1745 +msgid "" +"A :class:`TestResult` object stores the results of a set of tests. The :" +"class:`TestCase` and :class:`TestSuite` classes ensure that results are " +"properly recorded; test authors do not need to worry about recording the " +"outcome of tests." +msgstr "" + +#: ../Doc/library/unittest.rst:1750 +msgid "" +"Testing frameworks built on top of :mod:`unittest` may want access to the :" +"class:`TestResult` object generated by running a set of tests for reporting " +"purposes; a :class:`TestResult` instance is returned by the :meth:" +"`TestRunner.run` method for this purpose." +msgstr "" + +#: ../Doc/library/unittest.rst:1755 +msgid "" +":class:`TestResult` instances have the following attributes that will be of " +"interest when inspecting the results of running a set of tests:" +msgstr "" + +#: ../Doc/library/unittest.rst:1761 +msgid "" +"A list containing 2-tuples of :class:`TestCase` instances and strings " +"holding formatted tracebacks. Each tuple represents a test which raised an " +"unexpected exception." +msgstr "" + +#: ../Doc/library/unittest.rst:1767 +msgid "" +"A list containing 2-tuples of :class:`TestCase` instances and strings " +"holding formatted tracebacks. Each tuple represents a test where a failure " +"was explicitly signalled using the :meth:`TestCase.assert\\*` methods." +msgstr "" + +#: ../Doc/library/unittest.rst:1773 +msgid "" +"A list containing 2-tuples of :class:`TestCase` instances and strings " +"holding the reason for skipping the test." +msgstr "" + +#: ../Doc/library/unittest.rst:1780 +msgid "" +"A list containing 2-tuples of :class:`TestCase` instances and strings " +"holding formatted tracebacks. Each tuple represents an expected failure of " +"the test case." +msgstr "" + +#: ../Doc/library/unittest.rst:1786 +msgid "" +"A list containing :class:`TestCase` instances that were marked as expected " +"failures, but succeeded." +msgstr "" + +#: ../Doc/library/unittest.rst:1791 +msgid "" +"Set to ``True`` when the execution of tests should stop by :meth:`stop`." +msgstr "" + +#: ../Doc/library/unittest.rst:1795 +msgid "The total number of tests run so far." +msgstr "" + +#: ../Doc/library/unittest.rst:1799 +msgid "" +"If set to true, ``sys.stdout`` and ``sys.stderr`` will be buffered in " +"between :meth:`startTest` and :meth:`stopTest` being called. Collected " +"output will only be echoed onto the real ``sys.stdout`` and ``sys.stderr`` " +"if the test fails or errors. Any output is also attached to the failure / " +"error message." +msgstr "" + +#: ../Doc/library/unittest.rst:1808 +msgid "" +"If set to true :meth:`stop` will be called on the first failure or error, " +"halting the test run." +msgstr "" + +#: ../Doc/library/unittest.rst:1815 +msgid "If set to true then local variables will be shown in tracebacks." +msgstr "" + +#: ../Doc/library/unittest.rst:1821 +msgid "" +"Return ``True`` if all tests run so far have passed, otherwise returns " +"``False``." +msgstr "" + +#: ../Doc/library/unittest.rst:1824 +msgid "" +"Returns ``False`` if there were any :attr:`unexpectedSuccesses` from tests " +"marked with the :func:`expectedFailure` decorator." +msgstr "" + +#: ../Doc/library/unittest.rst:1830 +msgid "" +"This method can be called to signal that the set of tests being run should " +"be aborted by setting the :attr:`shouldStop` attribute to ``True``. :class:" +"`TestRunner` objects should respect this flag and return without running any " +"additional tests." +msgstr "" + +#: ../Doc/library/unittest.rst:1835 +msgid "" +"For example, this feature is used by the :class:`TextTestRunner` class to " +"stop the test framework when the user signals an interrupt from the " +"keyboard. Interactive tools which provide :class:`TestRunner` " +"implementations can use this in a similar manner." +msgstr "" + +#: ../Doc/library/unittest.rst:1840 +msgid "" +"The following methods of the :class:`TestResult` class are used to maintain " +"the internal data structures, and may be extended in subclasses to support " +"additional reporting requirements. This is particularly useful in building " +"tools which support interactive reporting while tests are being run." +msgstr "" + +#: ../Doc/library/unittest.rst:1848 +msgid "Called when the test case *test* is about to be run." +msgstr "" + +#: ../Doc/library/unittest.rst:1852 +msgid "" +"Called after the test case *test* has been executed, regardless of the " +"outcome." +msgstr "" + +#: ../Doc/library/unittest.rst:1857 +msgid "Called once before any tests are executed." +msgstr "" + +#: ../Doc/library/unittest.rst:1864 +msgid "Called once after all tests are executed." +msgstr "" + +#: ../Doc/library/unittest.rst:1871 +msgid "" +"Called when the test case *test* raises an unexpected exception. *err* is a " +"tuple of the form returned by :func:`sys.exc_info`: ``(type, value, " +"traceback)``." +msgstr "" + +#: ../Doc/library/unittest.rst:1875 +msgid "" +"The default implementation appends a tuple ``(test, formatted_err)`` to the " +"instance's :attr:`errors` attribute, where *formatted_err* is a formatted " +"traceback derived from *err*." +msgstr "" + +#: ../Doc/library/unittest.rst:1882 +msgid "" +"Called when the test case *test* signals a failure. *err* is a tuple of the " +"form returned by :func:`sys.exc_info`: ``(type, value, traceback)``." +msgstr "" + +#: ../Doc/library/unittest.rst:1885 +msgid "" +"The default implementation appends a tuple ``(test, formatted_err)`` to the " +"instance's :attr:`failures` attribute, where *formatted_err* is a formatted " +"traceback derived from *err*." +msgstr "" + +#: ../Doc/library/unittest.rst:1892 +msgid "Called when the test case *test* succeeds." +msgstr "" + +#: ../Doc/library/unittest.rst:1894 +msgid "The default implementation does nothing." +msgstr "" + +#: ../Doc/library/unittest.rst:1899 +msgid "" +"Called when the test case *test* is skipped. *reason* is the reason the " +"test gave for skipping." +msgstr "" + +#: ../Doc/library/unittest.rst:1902 +msgid "" +"The default implementation appends a tuple ``(test, reason)`` to the " +"instance's :attr:`skipped` attribute." +msgstr "" + +#: ../Doc/library/unittest.rst:1908 +msgid "" +"Called when the test case *test* fails, but was marked with the :func:" +"`expectedFailure` decorator." +msgstr "" + +#: ../Doc/library/unittest.rst:1911 +msgid "" +"The default implementation appends a tuple ``(test, formatted_err)`` to the " +"instance's :attr:`expectedFailures` attribute, where *formatted_err* is a " +"formatted traceback derived from *err*." +msgstr "" + +#: ../Doc/library/unittest.rst:1918 +msgid "" +"Called when the test case *test* was marked with the :func:`expectedFailure` " +"decorator, but succeeded." +msgstr "" + +#: ../Doc/library/unittest.rst:1921 +msgid "" +"The default implementation appends the test to the instance's :attr:" +"`unexpectedSuccesses` attribute." +msgstr "" + +#: ../Doc/library/unittest.rst:1927 +msgid "" +"Called when a subtest finishes. *test* is the test case corresponding to " +"the test method. *subtest* is a custom :class:`TestCase` instance " +"describing the subtest." +msgstr "" + +#: ../Doc/library/unittest.rst:1931 +msgid "" +"If *outcome* is :const:`None`, the subtest succeeded. Otherwise, it failed " +"with an exception where *outcome* is a tuple of the form returned by :func:" +"`sys.exc_info`: ``(type, value, traceback)``." +msgstr "" + +#: ../Doc/library/unittest.rst:1935 +msgid "" +"The default implementation does nothing when the outcome is a success, and " +"records subtest failures as normal failures." +msgstr "" + +#: ../Doc/library/unittest.rst:1943 +msgid "" +"A concrete implementation of :class:`TestResult` used by the :class:" +"`TextTestRunner`." +msgstr "" + +#: ../Doc/library/unittest.rst:1946 +msgid "" +"This class was previously named ``_TextTestResult``. The old name still " +"exists as an alias but is deprecated." +msgstr "" + +#: ../Doc/library/unittest.rst:1953 +msgid "" +"Instance of the :class:`TestLoader` class intended to be shared. If no " +"customization of the :class:`TestLoader` is needed, this instance can be " +"used instead of repeatedly creating new instances." +msgstr "" + +#: ../Doc/library/unittest.rst:1961 +msgid "" +"A basic test runner implementation that outputs results to a stream. If " +"*stream* is ``None``, the default, :data:`sys.stderr` is used as the output " +"stream. This class has a few configurable parameters, but is essentially " +"very simple. Graphical applications which run test suites should provide " +"alternate implementations. Such implementations should accept ``**kwargs`` " +"as the interface to construct runners changes when features are added to " +"unittest." +msgstr "" + +#: ../Doc/library/unittest.rst:1968 +msgid "" +"By default this runner shows :exc:`DeprecationWarning`, :exc:" +"`PendingDeprecationWarning`, :exc:`ResourceWarning` and :exc:`ImportWarning` " +"even if they are :ref:`ignored by default `. Deprecation " +"warnings caused by :ref:`deprecated unittest methods ` " +"are also special-cased and, when the warning filters are ``'default'`` or " +"``'always'``, they will appear only once per-module, in order to avoid too " +"many warning messages. This behavior can be overridden using the :option:`-" +"Wd` or :option:`-Wa` options and leaving *warnings* to ``None``." +msgstr "" + +#: ../Doc/library/unittest.rst:1978 +msgid "Added the ``warnings`` argument." +msgstr "" + +#: ../Doc/library/unittest.rst:1981 +msgid "" +"The default stream is set to :data:`sys.stderr` at instantiation time rather " +"than import time." +msgstr "" + +#: ../Doc/library/unittest.rst:1985 +msgid "Added the tb_locals parameter." +msgstr "" + +#: ../Doc/library/unittest.rst:1990 +msgid "" +"This method returns the instance of ``TestResult`` used by :meth:`run`. It " +"is not intended to be called directly, but can be overridden in subclasses " +"to provide a custom ``TestResult``." +msgstr "" + +#: ../Doc/library/unittest.rst:1994 +msgid "" +"``_makeResult()`` instantiates the class or callable passed in the " +"``TextTestRunner`` constructor as the ``resultclass`` argument. It defaults " +"to :class:`TextTestResult` if no ``resultclass`` is provided. The result " +"class is instantiated with the following arguments::" +msgstr "" + +#: ../Doc/library/unittest.rst:2003 +msgid "" +"This method is the main public interface to the `TextTestRunner`. This " +"method takes a :class:`TestSuite` or :class:`TestCase` instance. A :class:" +"`TestResult` is created by calling :func:`_makeResult` and the test(s) are " +"run and the results printed to stdout." +msgstr "" + +#: ../Doc/library/unittest.rst:2014 +msgid "" +"A command-line program that loads a set of tests from *module* and runs " +"them; this is primarily for making test modules conveniently executable. The " +"simplest use for this function is to include the following line at the end " +"of a test script::" +msgstr "" + +#: ../Doc/library/unittest.rst:2022 +msgid "" +"You can run tests with more detailed information by passing in the verbosity " +"argument::" +msgstr "" + +#: ../Doc/library/unittest.rst:2028 +msgid "" +"The *defaultTest* argument is either the name of a single test or an " +"iterable of test names to run if no test names are specified via *argv*. If " +"not specified or ``None`` and no test names are provided via *argv*, all " +"tests found in *module* are run." +msgstr "" + +#: ../Doc/library/unittest.rst:2033 +msgid "" +"The *argv* argument can be a list of options passed to the program, with the " +"first element being the program name. If not specified or ``None``, the " +"values of :data:`sys.argv` are used." +msgstr "" + +#: ../Doc/library/unittest.rst:2037 +msgid "" +"The *testRunner* argument can either be a test runner class or an already " +"created instance of it. By default ``main`` calls :func:`sys.exit` with an " +"exit code indicating success or failure of the tests run." +msgstr "" + +#: ../Doc/library/unittest.rst:2041 +msgid "" +"The *testLoader* argument has to be a :class:`TestLoader` instance, and " +"defaults to :data:`defaultTestLoader`." +msgstr "" + +#: ../Doc/library/unittest.rst:2044 +msgid "" +"``main`` supports being used from the interactive interpreter by passing in " +"the argument ``exit=False``. This displays the result on standard output " +"without calling :func:`sys.exit`::" +msgstr "" + +#: ../Doc/library/unittest.rst:2051 +msgid "" +"The *failfast*, *catchbreak* and *buffer* parameters have the same effect as " +"the same-name `command-line options`_." +msgstr "" + +#: ../Doc/library/unittest.rst:2054 +msgid "" +"The *warnings* argument specifies the :ref:`warning filter ` " +"that should be used while running the tests. If it's not specified, it will " +"remain ``None`` if a :option:`-W` option is passed to :program:`python`, " +"otherwise it will be set to ``'default'``." +msgstr "" + +#: ../Doc/library/unittest.rst:2059 +msgid "" +"Calling ``main`` actually returns an instance of the ``TestProgram`` class. " +"This stores the result of the tests run as the ``result`` attribute." +msgstr "" + +#: ../Doc/library/unittest.rst:2062 +msgid "The *exit* parameter was added." +msgstr "" + +#: ../Doc/library/unittest.rst:2065 +msgid "" +"The *verbosity*, *failfast*, *catchbreak*, *buffer* and *warnings* " +"parameters were added." +msgstr "" + +#: ../Doc/library/unittest.rst:2069 +msgid "" +"The *defaultTest* parameter was changed to also accept an iterable of test " +"names." +msgstr "" + +#: ../Doc/library/unittest.rst:2075 +msgid "load_tests Protocol" +msgstr "" + +#: ../Doc/library/unittest.rst:2079 +msgid "" +"Modules or packages can customize how tests are loaded from them during " +"normal test runs or test discovery by implementing a function called " +"``load_tests``." +msgstr "" + +#: ../Doc/library/unittest.rst:2082 +msgid "" +"If a test module defines ``load_tests`` it will be called by :meth:" +"`TestLoader.loadTestsFromModule` with the following arguments::" +msgstr "" + +#: ../Doc/library/unittest.rst:2087 +msgid "" +"where *pattern* is passed straight through from ``loadTestsFromModule``. It " +"defaults to ``None``." +msgstr "" + +#: ../Doc/library/unittest.rst:2090 +msgid "It should return a :class:`TestSuite`." +msgstr "" + +#: ../Doc/library/unittest.rst:2092 +msgid "" +"*loader* is the instance of :class:`TestLoader` doing the loading. " +"*standard_tests* are the tests that would be loaded by default from the " +"module. It is common for test modules to only want to add or remove tests " +"from the standard set of tests. The third argument is used when loading " +"packages as part of test discovery." +msgstr "" + +#: ../Doc/library/unittest.rst:2098 +msgid "" +"A typical ``load_tests`` function that loads tests from a specific set of :" +"class:`TestCase` classes may look like::" +msgstr "" + +#: ../Doc/library/unittest.rst:2110 +msgid "" +"If discovery is started in a directory containing a package, either from the " +"command line or by calling :meth:`TestLoader.discover`, then the package :" +"file:`__init__.py` will be checked for ``load_tests``. If that function " +"does not exist, discovery will recurse into the package as though it were " +"just another directory. Otherwise, discovery of the package's tests will be " +"left up to ``load_tests`` which is called with the following arguments::" +msgstr "" + +#: ../Doc/library/unittest.rst:2119 +msgid "" +"This should return a :class:`TestSuite` representing all the tests from the " +"package. (``standard_tests`` will only contain tests collected from :file:" +"`__init__.py`.)" +msgstr "" + +#: ../Doc/library/unittest.rst:2123 +msgid "" +"Because the pattern is passed into ``load_tests`` the package is free to " +"continue (and potentially modify) test discovery. A 'do nothing' " +"``load_tests`` function for a test package would look like::" +msgstr "" + +#: ../Doc/library/unittest.rst:2134 +msgid "" +"Discovery no longer checks package names for matching *pattern* due to the " +"impossibility of package names matching the default pattern." +msgstr "" + +#: ../Doc/library/unittest.rst:2141 +msgid "Class and Module Fixtures" +msgstr "" + +#: ../Doc/library/unittest.rst:2143 +msgid "" +"Class and module level fixtures are implemented in :class:`TestSuite`. When " +"the test suite encounters a test from a new class then :meth:`tearDownClass` " +"from the previous class (if there is one) is called, followed by :meth:" +"`setUpClass` from the new class." +msgstr "" + +#: ../Doc/library/unittest.rst:2148 +msgid "" +"Similarly if a test is from a different module from the previous test then " +"``tearDownModule`` from the previous module is run, followed by " +"``setUpModule`` from the new module." +msgstr "" + +#: ../Doc/library/unittest.rst:2152 +msgid "" +"After all the tests have run the final ``tearDownClass`` and " +"``tearDownModule`` are run." +msgstr "" + +#: ../Doc/library/unittest.rst:2155 +msgid "" +"Note that shared fixtures do not play well with [potential] features like " +"test parallelization and they break test isolation. They should be used with " +"care." +msgstr "" + +#: ../Doc/library/unittest.rst:2158 +msgid "" +"The default ordering of tests created by the unittest test loaders is to " +"group all tests from the same modules and classes together. This will lead " +"to ``setUpClass`` / ``setUpModule`` (etc) being called exactly once per " +"class and module. If you randomize the order, so that tests from different " +"modules and classes are adjacent to each other, then these shared fixture " +"functions may be called multiple times in a single test run." +msgstr "" + +#: ../Doc/library/unittest.rst:2165 +msgid "" +"Shared fixtures are not intended to work with suites with non-standard " +"ordering. A ``BaseTestSuite`` still exists for frameworks that don't want to " +"support shared fixtures." +msgstr "" + +#: ../Doc/library/unittest.rst:2169 +msgid "" +"If there are any exceptions raised during one of the shared fixture " +"functions the test is reported as an error. Because there is no " +"corresponding test instance an ``_ErrorHolder`` object (that has the same " +"interface as a :class:`TestCase`) is created to represent the error. If you " +"are just using the standard unittest test runner then this detail doesn't " +"matter, but if you are a framework author it may be relevant." +msgstr "" + +#: ../Doc/library/unittest.rst:2178 +msgid "setUpClass and tearDownClass" +msgstr "" + +#: ../Doc/library/unittest.rst:2180 +msgid "These must be implemented as class methods::" +msgstr "" + +#: ../Doc/library/unittest.rst:2193 +msgid "" +"If you want the ``setUpClass`` and ``tearDownClass`` on base classes called " +"then you must call up to them yourself. The implementations in :class:" +"`TestCase` are empty." +msgstr "" + +#: ../Doc/library/unittest.rst:2197 +msgid "" +"If an exception is raised during a ``setUpClass`` then the tests in the " +"class are not run and the ``tearDownClass`` is not run. Skipped classes will " +"not have ``setUpClass`` or ``tearDownClass`` run. If the exception is a :exc:" +"`SkipTest` exception then the class will be reported as having been skipped " +"instead of as an error." +msgstr "" + +#: ../Doc/library/unittest.rst:2205 +msgid "setUpModule and tearDownModule" +msgstr "" + +#: ../Doc/library/unittest.rst:2207 +msgid "These should be implemented as functions::" +msgstr "" + +#: ../Doc/library/unittest.rst:2215 +msgid "" +"If an exception is raised in a ``setUpModule`` then none of the tests in the " +"module will be run and the ``tearDownModule`` will not be run. If the " +"exception is a :exc:`SkipTest` exception then the module will be reported as " +"having been skipped instead of as an error." +msgstr "" + +#: ../Doc/library/unittest.rst:2222 +msgid "Signal Handling" +msgstr "" + +#: ../Doc/library/unittest.rst:2226 +msgid "" +"The :option:`-c/--catch ` command-line option to unittest, " +"along with the ``catchbreak`` parameter to :func:`unittest.main()`, provide " +"more friendly handling of control-C during a test run. With catch break " +"behavior enabled control-C will allow the currently running test to " +"complete, and the test run will then end and report all the results so far. " +"A second control-c will raise a :exc:`KeyboardInterrupt` in the usual way." +msgstr "" + +#: ../Doc/library/unittest.rst:2233 +msgid "" +"The control-c handling signal handler attempts to remain compatible with " +"code or tests that install their own :const:`signal.SIGINT` handler. If the " +"``unittest`` handler is called but *isn't* the installed :const:`signal." +"SIGINT` handler, i.e. it has been replaced by the system under test and " +"delegated to, then it calls the default handler. This will normally be the " +"expected behavior by code that replaces an installed handler and delegates " +"to it. For individual tests that need ``unittest`` control-c handling " +"disabled the :func:`removeHandler` decorator can be used." +msgstr "" + +#: ../Doc/library/unittest.rst:2242 +msgid "" +"There are a few utility functions for framework authors to enable control-c " +"handling functionality within test frameworks." +msgstr "" + +#: ../Doc/library/unittest.rst:2247 +msgid "" +"Install the control-c handler. When a :const:`signal.SIGINT` is received " +"(usually in response to the user pressing control-c) all registered results " +"have :meth:`~TestResult.stop` called." +msgstr "" + +#: ../Doc/library/unittest.rst:2254 +msgid "" +"Register a :class:`TestResult` object for control-c handling. Registering a " +"result stores a weak reference to it, so it doesn't prevent the result from " +"being garbage collected." +msgstr "" + +#: ../Doc/library/unittest.rst:2258 +msgid "" +"Registering a :class:`TestResult` object has no side-effects if control-c " +"handling is not enabled, so test frameworks can unconditionally register all " +"results they create independently of whether or not handling is enabled." +msgstr "" + +#: ../Doc/library/unittest.rst:2265 +msgid "" +"Remove a registered result. Once a result has been removed then :meth:" +"`~TestResult.stop` will no longer be called on that result object in " +"response to a control-c." +msgstr "" + +#: ../Doc/library/unittest.rst:2272 +msgid "" +"When called without arguments this function removes the control-c handler if " +"it has been installed. This function can also be used as a test decorator to " +"temporarily remove the handler whilst the test is being executed::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:3 +msgid ":mod:`unittest.mock` --- mock object library" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:13 +msgid "**Source code:** :source:`Lib/unittest/mock.py`" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:17 +msgid "" +":mod:`unittest.mock` is a library for testing in Python. It allows you to " +"replace parts of your system under test with mock objects and make " +"assertions about how they have been used." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:21 +msgid "" +":mod:`unittest.mock` provides a core :class:`Mock` class removing the need " +"to create a host of stubs throughout your test suite. After performing an " +"action, you can make assertions about which methods / attributes were used " +"and arguments they were called with. You can also specify return values and " +"set needed attributes in the normal way." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:27 +msgid "" +"Additionally, mock provides a :func:`patch` decorator that handles patching " +"module and class level attributes within the scope of a test, along with :" +"const:`sentinel` for creating unique objects. See the `quick guide`_ for " +"some examples of how to use :class:`Mock`, :class:`MagicMock` and :func:" +"`patch`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:33 +msgid "" +"Mock is very easy to use and is designed for use with :mod:`unittest`. Mock " +"is based on the 'action -> assertion' pattern instead of 'record -> replay' " +"used by many mocking frameworks." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:37 +msgid "" +"There is a backport of :mod:`unittest.mock` for earlier versions of Python, " +"available as `mock on PyPI `_." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:42 +msgid "Quick Guide" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:44 +msgid "" +":class:`Mock` and :class:`MagicMock` objects create all attributes and " +"methods as you access them and store details of how they have been used. You " +"can configure them, to specify return values or limit what attributes are " +"available, and then make assertions about how they have been used:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:56 +msgid "" +":attr:`side_effect` allows you to perform side effects, including raising an " +"exception when a mock is called:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:76 +msgid "" +"Mock has many other ways you can configure it and control its behaviour. For " +"example the *spec* argument configures the mock to take its specification " +"from another object. Attempting to access attributes or methods on the mock " +"that don't exist on the spec will fail with an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:81 +msgid "" +"The :func:`patch` decorator / context manager makes it easy to mock classes " +"or objects in a module under test. The object you specify will be replaced " +"with a mock (or other object) during the test and restored when the test " +"ends:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:100 +msgid "" +"When you nest patch decorators the mocks are passed in to the decorated " +"function in the same order they applied (the normal *python* order that " +"decorators are applied). This means from the bottom up, so in the example " +"above the mock for ``module.ClassName1`` is passed in first." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:105 +#: ../Doc/library/unittest.mock-examples.rst:305 +msgid "" +"With :func:`patch` it matters that you patch objects in the namespace where " +"they are looked up. This is normally straightforward, but for a quick guide " +"read :ref:`where to patch `." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:109 +msgid "" +"As well as a decorator :func:`patch` can be used as a context manager in a " +"with statement:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:119 +#: ../Doc/library/unittest.mock-examples.rst:399 +msgid "" +"There is also :func:`patch.dict` for setting values in a dictionary just " +"during a scope and restoring the dictionary to its original state when the " +"test ends:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:130 +msgid "" +"Mock supports the mocking of Python :ref:`magic methods `. " +"The easiest way of using magic methods is with the :class:`MagicMock` class. " +"It allows you to do things like:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:140 +msgid "" +"Mock allows you to assign functions (or other Mock instances) to magic " +"methods and they will be called appropriately. The :class:`MagicMock` class " +"is just a Mock variant that has all of the magic methods pre-created for you " +"(well, all the useful ones anyway)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:145 +msgid "" +"The following is an example of using magic methods with the ordinary Mock " +"class:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:153 +msgid "" +"For ensuring that the mock objects in your tests have the same api as the " +"objects they are replacing, you can use :ref:`auto-speccing `. Auto-speccing can be done through the *autospec* argument to " +"patch, or the :func:`create_autospec` function. Auto-speccing creates mock " +"objects that have the same attributes and methods as the objects they are " +"replacing, and any functions and methods (including constructors) have the " +"same call signature as the real object." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:161 +msgid "" +"This ensures that your mocks will fail in the same way as your production " +"code if they are used incorrectly:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:177 +msgid "" +":func:`create_autospec` can also be used on classes, where it copies the " +"signature of the ``__init__`` method, and on callable objects where it " +"copies the signature of the ``__call__`` method." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:184 +msgid "The Mock Class" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:187 +msgid "" +":class:`Mock` is a flexible mock object intended to replace the use of stubs " +"and test doubles throughout your code. Mocks are callable and create " +"attributes as new mocks when you access them [#]_. Accessing the same " +"attribute will always return the same mock. Mocks record how you use them, " +"allowing you to make assertions about what your code has done to them." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:193 +msgid "" +":class:`MagicMock` is a subclass of :class:`Mock` with all the magic methods " +"pre-created and ready to use. There are also non-callable variants, useful " +"when you are mocking out objects that aren't callable: :class:" +"`NonCallableMock` and :class:`NonCallableMagicMock`" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:198 +msgid "" +"The :func:`patch` decorators makes it easy to temporarily replace classes in " +"a particular module with a :class:`Mock` object. By default :func:`patch` " +"will create a :class:`MagicMock` for you. You can specify an alternative " +"class of :class:`Mock` using the *new_callable* argument to :func:`patch`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:206 +msgid "" +"Create a new :class:`Mock` object. :class:`Mock` takes several optional " +"arguments that specify the behaviour of the Mock object:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:209 +msgid "" +"*spec*: This can be either a list of strings or an existing object (a class " +"or instance) that acts as the specification for the mock object. If you pass " +"in an object then a list of strings is formed by calling dir on the object " +"(excluding unsupported magic attributes and methods). Accessing any " +"attribute not in this list will raise an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:215 +msgid "" +"If *spec* is an object (rather than a list of strings) then :attr:`~instance." +"__class__` returns the class of the spec object. This allows mocks to pass :" +"func:`isinstance` tests." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:219 +msgid "" +"*spec_set*: A stricter variant of *spec*. If used, attempting to *set* or " +"get an attribute on the mock that isn't on the object passed as *spec_set* " +"will raise an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:223 +msgid "" +"*side_effect*: A function to be called whenever the Mock is called. See the :" +"attr:`~Mock.side_effect` attribute. Useful for raising exceptions or " +"dynamically changing return values. The function is called with the same " +"arguments as the mock, and unless it returns :data:`DEFAULT`, the return " +"value of this function is used as the return value." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:229 +msgid "" +"Alternatively *side_effect* can be an exception class or instance. In this " +"case the exception will be raised when the mock is called." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:232 +msgid "" +"If *side_effect* is an iterable then each call to the mock will return the " +"next value from the iterable." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:235 +msgid "A *side_effect* can be cleared by setting it to ``None``." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:237 +msgid "" +"*return_value*: The value returned when the mock is called. By default this " +"is a new Mock (created on first access). See the :attr:`return_value` " +"attribute." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:241 +msgid "" +"*unsafe*: By default if any attribute starts with *assert* or *assret* will " +"raise an :exc:`AttributeError`. Passing ``unsafe=True`` will allow access to " +"these attributes." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:247 +msgid "" +"*wraps*: Item for the mock object to wrap. If *wraps* is not None then " +"calling the Mock will pass the call through to the wrapped object (returning " +"the real result). Attribute access on the mock will return a Mock object " +"that wraps the corresponding attribute of the wrapped object (so attempting " +"to access an attribute that doesn't exist will raise an :exc:" +"`AttributeError`)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:254 +msgid "" +"If the mock has an explicit *return_value* set then calls are not passed to " +"the wrapped object and the *return_value* is returned instead." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:257 +msgid "" +"*name*: If the mock has a name then it will be used in the repr of the mock. " +"This can be useful for debugging. The name is propagated to child mocks." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:261 +msgid "" +"Mocks can also be called with arbitrary keyword arguments. These will be " +"used to set attributes on the mock after it is created. See the :meth:" +"`configure_mock` method for details." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:267 +msgid "Assert that the mock was called at least once." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:278 +msgid "Assert that the mock was called exactly once." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:296 +msgid "" +"This method is a convenient way of asserting that calls are made in a " +"particular way:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:306 +msgid "" +"Assert that the mock was called exactly once and with the specified " +"arguments." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:321 +msgid "assert the mock has been called with the specified arguments." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:323 +msgid "" +"The assert passes if the mock has *ever* been called, unlike :meth:" +"`assert_called_with` and :meth:`assert_called_once_with` that only pass if " +"the call is the most recent one." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:335 +msgid "" +"assert the mock has been called with the specified calls. The :attr:" +"`mock_calls` list is checked for the calls." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:338 +msgid "" +"If *any_order* is false (the default) then the calls must be sequential. " +"There can be extra calls before or after the specified calls." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:342 +msgid "" +"If *any_order* is true then the calls can be in any order, but they must all " +"appear in :attr:`mock_calls`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:357 +msgid "Assert the mock was never called." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:372 +msgid "The reset_mock method resets all the call attributes on a mock object:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:382 +msgid "Added two keyword only argument to the reset_mock function." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:385 +msgid "" +"This can be useful where you want to make a series of assertions that reuse " +"the same object. Note that :meth:`reset_mock` *doesn't* clear the return " +"value, :attr:`side_effect` or any child attributes you have set using normal " +"assignment by default. In case you want to reset *return_value* or :attr:" +"`side_effect`, then pass the corresponding parameter as ``True``. Child " +"mocks and the return value mock (if any) are reset as well." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:393 +msgid "*return_value*, and :attr:`side_effect` are keyword only argument." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:399 +msgid "" +"Add a spec to a mock. *spec* can either be an object or a list of strings. " +"Only attributes on the *spec* can be fetched as attributes from the mock." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:403 +msgid "If *spec_set* is true then only attributes on the spec can be set." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:408 +msgid "" +"Attach a mock as an attribute of this one, replacing its name and parent. " +"Calls to the attached mock will be recorded in the :attr:`method_calls` and :" +"attr:`mock_calls` attributes of this one." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:415 +msgid "Set attributes on the mock through keyword arguments." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:417 +msgid "" +"Attributes plus return values and side effects can be set on child mocks " +"using standard dot notation and unpacking a dictionary in the method call:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:431 +msgid "The same thing can be achieved in the constructor call to mocks:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:444 +msgid "" +":meth:`configure_mock` exists to make it easier to do configuration after " +"the mock has been created." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:450 +msgid "" +":class:`Mock` objects limit the results of ``dir(some_mock)`` to useful " +"results. For mocks with a *spec* this includes all the permitted attributes " +"for the mock." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:454 +msgid "" +"See :data:`FILTER_DIR` for what this filtering does, and how to switch it " +"off." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:460 +msgid "" +"Create the child mocks for attributes and return value. By default child " +"mocks will be the same type as the parent. Subclasses of Mock may want to " +"override this to customize the way child mocks are made." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:465 +msgid "" +"For non-callable mocks the callable variant will be used (rather than any " +"custom subclass)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:471 +msgid "A boolean representing whether or not the mock object has been called:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:482 +msgid "An integer telling you how many times the mock object has been called:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:495 +msgid "Set this to configure the value returned by calling the mock:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:502 +msgid "" +"The default return value is a mock object and you can configure it in the " +"normal way:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:511 +msgid ":attr:`return_value` can also be set in the constructor:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:522 +msgid "" +"This can either be a function to be called when the mock is called, an " +"iterable or an exception (class or instance) to be raised." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:525 +msgid "" +"If you pass in a function it will be called with same arguments as the mock " +"and unless the function returns the :data:`DEFAULT` singleton the call to " +"the mock will then return whatever the function returns. If the function " +"returns :data:`DEFAULT` then the mock will return its normal value (from " +"the :attr:`return_value`)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:531 +msgid "" +"If you pass in an iterable, it is used to retrieve an iterator which must " +"yield a value on every call. This value can either be an exception instance " +"to be raised, or a value to be returned from the call to the mock (:data:" +"`DEFAULT` handling is identical to the function case)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:536 +msgid "" +"An example of a mock that raises an exception (to test exception handling of " +"an API):" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:546 +msgid "Using :attr:`side_effect` to return a sequence of values:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:553 +msgid "Using a callable:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:563 +msgid "" +":attr:`side_effect` can be set in the constructor. Here's an example that " +"adds one to the value the mock is called with and returns it:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:573 +msgid "Setting :attr:`side_effect` to ``None`` clears it:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:587 +msgid "" +"This is either ``None`` (if the mock hasn't been called), or the arguments " +"that the mock was last called with. This will be in the form of a tuple: the " +"first member is any ordered arguments the mock was called with (or an empty " +"tuple) and the second member is any keyword arguments (or an empty " +"dictionary)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:610 +msgid "" +":attr:`call_args`, along with members of the lists :attr:`call_args_list`, :" +"attr:`method_calls` and :attr:`mock_calls` are :data:`call` objects. These " +"are tuples, so they can be unpacked to get at the individual arguments and " +"make more complex assertions. See :ref:`calls as tuples `." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:619 +msgid "" +"This is a list of all the calls made to the mock object in sequence (so the " +"length of the list is the number of times it has been called). Before any " +"calls have been made it is an empty list. The :data:`call` object can be " +"used for conveniently constructing lists of calls to compare with :attr:" +"`call_args_list`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:635 +msgid "" +"Members of :attr:`call_args_list` are :data:`call` objects. These can be " +"unpacked as tuples to get at the individual arguments. See :ref:`calls as " +"tuples `." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:642 +msgid "" +"As well as tracking calls to themselves, mocks also track calls to methods " +"and attributes, and *their* methods and attributes:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:653 +msgid "" +"Members of :attr:`method_calls` are :data:`call` objects. These can be " +"unpacked as tuples to get at the individual arguments. See :ref:`calls as " +"tuples `." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:660 +msgid "" +":attr:`mock_calls` records *all* calls to the mock object, its methods, " +"magic methods *and* return value mocks." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:678 +msgid "" +"Members of :attr:`mock_calls` are :data:`call` objects. These can be " +"unpacked as tuples to get at the individual arguments. See :ref:`calls as " +"tuples `." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:685 +msgid "" +"Normally the :attr:`__class__` attribute of an object will return its type. " +"For a mock object with a :attr:`spec`, ``__class__`` returns the spec class " +"instead. This allows mock objects to pass :func:`isinstance` tests for the " +"object they are replacing / masquerading as:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:694 +msgid "" +":attr:`__class__` is assignable to, this allows a mock to pass an :func:" +"`isinstance` check without forcing you to use a spec:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:704 +msgid "" +"A non-callable version of :class:`Mock`. The constructor parameters have the " +"same meaning of :class:`Mock`, with the exception of *return_value* and " +"*side_effect* which have no meaning on a non-callable mock." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:708 +msgid "" +"Mock objects that use a class or an instance as a :attr:`spec` or :attr:" +"`spec_set` are able to pass :func:`isinstance` tests:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:718 +msgid "" +"The :class:`Mock` classes have support for mocking magic methods. See :ref:" +"`magic methods ` for the full details." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:721 +msgid "" +"The mock classes and the :func:`patch` decorators all take arbitrary keyword " +"arguments for configuration. For the :func:`patch` decorators the keywords " +"are passed to the constructor of the mock being created. The keyword " +"arguments are for configuring attributes of the mock:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:732 +msgid "" +"The return value and side effect of child mocks can be set in the same way, " +"using dotted notation. As you can't use dotted names directly in a call you " +"have to create a dictionary and unpack it using ``**``:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:747 +msgid "" +"A callable mock which was created with a *spec* (or a *spec_set*) will " +"introspect the specification object's signature when matching calls to the " +"mock. Therefore, it can match the actual call's arguments regardless of " +"whether they were passed positionally or by name::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:760 +msgid "" +"This applies to :meth:`~Mock.assert_called_with`, :meth:`~Mock." +"assert_called_once_with`, :meth:`~Mock.assert_has_calls` and :meth:`~Mock." +"assert_any_call`. When :ref:`auto-speccing`, it will also apply to method " +"calls on the mock object." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:765 +msgid "Added signature introspection on specced and autospecced mock objects." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:771 +msgid "" +"A mock intended to be used as a property, or other descriptor, on a class. :" +"class:`PropertyMock` provides :meth:`__get__` and :meth:`__set__` methods so " +"you can specify a return value when it is fetched." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:775 +msgid "" +"Fetching a :class:`PropertyMock` instance from an object calls the mock, " +"with no args. Setting it calls the mock with the value being set." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:796 +msgid "" +"Because of the way mock attributes are stored you can't directly attach a :" +"class:`PropertyMock` to a mock object. Instead you can attach it to the mock " +"type object::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:809 +msgid "Calling" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:811 +msgid "" +"Mock objects are callable. The call will return the value set as the :attr:" +"`~Mock.return_value` attribute. The default return value is a new Mock " +"object; it is created the first time the return value is accessed (either " +"explicitly or by calling the Mock) - but it is stored and the same one " +"returned each time." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:817 +msgid "" +"Calls made to the object will be recorded in the attributes like :attr:" +"`~Mock.call_args` and :attr:`~Mock.call_args_list`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:820 +msgid "" +"If :attr:`~Mock.side_effect` is set then it will be called after the call " +"has been recorded, so if :attr:`side_effect` raises an exception the call is " +"still recorded." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:824 +msgid "" +"The simplest way to make a mock raise an exception when called is to make :" +"attr:`~Mock.side_effect` an exception class or instance:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:842 +msgid "" +"If :attr:`side_effect` is a function then whatever that function returns is " +"what calls to the mock return. The :attr:`side_effect` function is called " +"with the same arguments as the mock. This allows you to vary the return " +"value of the call dynamically, based on the input:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:858 +msgid "" +"If you want the mock to still return the default return value (a new mock), " +"or any set return value, then there are two ways of doing this. Either " +"return :attr:`mock.return_value` from inside :attr:`side_effect`, or return :" +"data:`DEFAULT`:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:877 +msgid "" +"To remove a :attr:`side_effect`, and return to the default behaviour, set " +"the :attr:`side_effect` to ``None``:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:891 +msgid "" +"The :attr:`side_effect` can also be any iterable object. Repeated calls to " +"the mock will return values from the iterable (until the iterable is " +"exhausted and a :exc:`StopIteration` is raised):" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:907 +msgid "" +"If any members of the iterable are exceptions they will be raised instead of " +"returned::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:925 +msgid "Deleting Attributes" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:927 +msgid "" +"Mock objects create attributes on demand. This allows them to pretend to be " +"objects of any type." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:930 +msgid "" +"You may want a mock object to return ``False`` to a :func:`hasattr` call, or " +"raise an :exc:`AttributeError` when an attribute is fetched. You can do this " +"by providing an object as a :attr:`spec` for a mock, but that isn't always " +"convenient." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:934 +msgid "" +"You \"block\" attributes by deleting them. Once deleted, accessing an " +"attribute will raise an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:951 +msgid "Mock names and the name attribute" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:953 +msgid "" +"Since \"name\" is an argument to the :class:`Mock` constructor, if you want " +"your mock object to have a \"name\" attribute you can't just pass it in at " +"creation time. There are two alternatives. One option is to use :meth:`~Mock." +"configure_mock`::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:963 +msgid "" +"A simpler option is to simply set the \"name\" attribute after mock " +"creation::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:970 +msgid "Attaching Mocks as Attributes" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:972 +msgid "" +"When you attach a mock as an attribute of another mock (or as the return " +"value) it becomes a \"child\" of that mock. Calls to the child are recorded " +"in the :attr:`~Mock.method_calls` and :attr:`~Mock.mock_calls` attributes of " +"the parent. This is useful for configuring child mocks and then attaching " +"them to the parent, or for attaching mocks to a parent that records all " +"calls to the children and allows you to make assertions about the order of " +"calls between mocks:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:990 +msgid "" +"The exception to this is if the mock has a name. This allows you to prevent " +"the \"parenting\" if for some reason you don't want it to happen." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1001 +msgid "" +"Mocks created for you by :func:`patch` are automatically given names. To " +"attach mocks that have names to a parent you use the :meth:`~Mock." +"attach_mock` method:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1019 +msgid "" +"The only exceptions are magic methods and attributes (those that have " +"leading and trailing double underscores). Mock doesn't create these but " +"instead raises an :exc:`AttributeError`. This is because the interpreter " +"will often implicitly request these methods, and gets *very* confused to get " +"a new Mock object when it expects a magic method. If you need magic method " +"support see :ref:`magic methods `." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1028 +msgid "The patchers" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1030 +msgid "" +"The patch decorators are used for patching objects only within the scope of " +"the function they decorate. They automatically handle the unpatching for " +"you, even if exceptions are raised. All of these functions can also be used " +"in with statements or as class decorators." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1037 +msgid "patch" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1041 +msgid "" +":func:`patch` is straightforward to use. The key is to do the patching in " +"the right namespace. See the section `where to patch`_." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1046 +msgid "" +":func:`patch` acts as a function decorator, class decorator or a context " +"manager. Inside the body of the function or with statement, the *target* is " +"patched with a *new* object. When the function/with statement exits the " +"patch is undone." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1051 +msgid "" +"If *new* is omitted, then the target is replaced with a :class:`MagicMock`. " +"If :func:`patch` is used as a decorator and *new* is omitted, the created " +"mock is passed in as an extra argument to the decorated function. If :func:" +"`patch` is used as a context manager the created mock is returned by the " +"context manager." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1057 +msgid "" +"*target* should be a string in the form ``'package.module.ClassName'``. The " +"*target* is imported and the specified object replaced with the *new* " +"object, so the *target* must be importable from the environment you are " +"calling :func:`patch` from. The target is imported when the decorated " +"function is executed, not at decoration time." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1063 +msgid "" +"The *spec* and *spec_set* keyword arguments are passed to the :class:" +"`MagicMock` if patch is creating one for you." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1066 +msgid "" +"In addition you can pass ``spec=True`` or ``spec_set=True``, which causes " +"patch to pass in the object being mocked as the spec/spec_set object." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1069 +msgid "" +"*new_callable* allows you to specify a different class, or callable object, " +"that will be called to create the *new* object. By default :class:" +"`MagicMock` is used." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1073 +msgid "" +"A more powerful form of *spec* is *autospec*. If you set ``autospec=True`` " +"then the mock will be created with a spec from the object being replaced. " +"All attributes of the mock will also have the spec of the corresponding " +"attribute of the object being replaced. Methods and functions being mocked " +"will have their arguments checked and will raise a :exc:`TypeError` if they " +"are called with the wrong signature. For mocks replacing a class, their " +"return value (the 'instance') will have the same spec as the class. See the :" +"func:`create_autospec` function and :ref:`auto-speccing`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1083 +msgid "" +"Instead of ``autospec=True`` you can pass ``autospec=some_object`` to use an " +"arbitrary object as the spec instead of the one being replaced." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1086 +msgid "" +"By default :func:`patch` will fail to replace attributes that don't exist. " +"If you pass in ``create=True``, and the attribute doesn't exist, patch will " +"create the attribute for you when the patched function is called, and delete " +"it again afterwards. This is useful for writing tests against attributes " +"that your production code creates at runtime. It is off by default because " +"it can be dangerous. With it switched on you can write passing tests against " +"APIs that don't actually exist!" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1096 +msgid "" +"If you are patching builtins in a module then you don't need to pass " +"``create=True``, it will be added by default." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1100 +msgid "" +"Patch can be used as a :class:`TestCase` class decorator. It works by " +"decorating each test method in the class. This reduces the boilerplate code " +"when your test methods share a common patchings set. :func:`patch` finds " +"tests by looking for method names that start with ``patch.TEST_PREFIX``. By " +"default this is ``'test'``, which matches the way :mod:`unittest` finds " +"tests. You can specify an alternative prefix by setting ``patch." +"TEST_PREFIX``." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1107 +msgid "" +"Patch can be used as a context manager, with the with statement. Here the " +"patching applies to the indented block after the with statement. If you use " +"\"as\" then the patched object will be bound to the name after the \"as\"; " +"very useful if :func:`patch` is creating a mock object for you." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1112 +msgid "" +":func:`patch` takes arbitrary keyword arguments. These will be passed to " +"the :class:`Mock` (or *new_callable*) on construction." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1115 +msgid "" +"``patch.dict(...)``, ``patch.multiple(...)`` and ``patch.object(...)`` are " +"available for alternate use-cases." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1118 +msgid "" +":func:`patch` as function decorator, creating the mock for you and passing " +"it into the decorated function:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1128 +msgid "" +"Patching a class replaces the class with a :class:`MagicMock` *instance*. If " +"the class is instantiated in the code under test then it will be the :attr:" +"`~Mock.return_value` of the mock that will be used." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1132 +msgid "" +"If the class is instantiated multiple times you could use :attr:`~Mock." +"side_effect` to return a new mock each time. Alternatively you can set the " +"*return_value* to be anything you want." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1136 +msgid "" +"To configure return values on methods of *instances* on the patched class " +"you must do this on the :attr:`return_value`. For example:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1150 +msgid "" +"If you use *spec* or *spec_set* and :func:`patch` is replacing a *class*, " +"then the return value of the created mock will have the same spec." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1160 +msgid "" +"The *new_callable* argument is useful where you want to use an alternative " +"class to the default :class:`MagicMock` for the created mock. For example, " +"if you wanted a :class:`NonCallableMock` to be used:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1173 +msgid "" +"Another use case might be to replace an object with an :class:`io.StringIO` " +"instance:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1186 +msgid "" +"When :func:`patch` is creating a mock for you, it is common that the first " +"thing you need to do is to configure the mock. Some of that configuration " +"can be done in the call to patch. Any arbitrary keywords you pass into the " +"call will be used to set attributes on the created mock:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1198 +msgid "" +"As well as attributes on the created mock attributes, like the :attr:`~Mock." +"return_value` and :attr:`~Mock.side_effect`, of child mocks can also be " +"configured. These aren't syntactically valid to pass in directly as keyword " +"arguments, but a dictionary with these as keys can still be expanded into a :" +"func:`patch` call using ``**``:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1216 +msgid "patch.object" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1220 +msgid "" +"patch the named member (*attribute*) on an object (*target*) with a mock " +"object." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1223 +msgid "" +":func:`patch.object` can be used as a decorator, class decorator or a " +"context manager. Arguments *new*, *spec*, *create*, *spec_set*, *autospec* " +"and *new_callable* have the same meaning as for :func:`patch`. Like :func:" +"`patch`, :func:`patch.object` takes arbitrary keyword arguments for " +"configuring the mock object it creates." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1229 +msgid "" +"When used as a class decorator :func:`patch.object` honours ``patch." +"TEST_PREFIX`` for choosing which methods to wrap." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1232 +msgid "" +"You can either call :func:`patch.object` with three arguments or two " +"arguments. The three argument form takes the object to be patched, the " +"attribute name and the object to replace the attribute with." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1236 +msgid "" +"When calling with the two argument form you omit the replacement object, and " +"a mock is created for you and passed in as an extra argument to the " +"decorated function:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1247 +msgid "" +"*spec*, *create* and the other arguments to :func:`patch.object` have the " +"same meaning as they do for :func:`patch`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1252 +msgid "patch.dict" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1256 +msgid "" +"Patch a dictionary, or dictionary like object, and restore the dictionary to " +"its original state after the test." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1259 +msgid "" +"*in_dict* can be a dictionary or a mapping like container. If it is a " +"mapping then it must at least support getting, setting and deleting items " +"plus iterating over keys." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1263 +msgid "" +"*in_dict* can also be a string specifying the name of the dictionary, which " +"will then be fetched by importing it." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1266 +msgid "" +"*values* can be a dictionary of values to set in the dictionary. *values* " +"can also be an iterable of ``(key, value)`` pairs." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1269 +msgid "" +"If *clear* is true then the dictionary will be cleared before the new values " +"are set." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1272 +msgid "" +":func:`patch.dict` can also be called with arbitrary keyword arguments to " +"set values in the dictionary." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1275 +msgid "" +":func:`patch.dict` can be used as a context manager, decorator or class " +"decorator. When used as a class decorator :func:`patch.dict` honours ``patch." +"TEST_PREFIX`` for choosing which methods to wrap." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1279 +msgid "" +":func:`patch.dict` can be used to add members to a dictionary, or simply let " +"a test change a dictionary, and ensure the dictionary is restored when the " +"test ends." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1296 +msgid "" +"Keywords can be used in the :func:`patch.dict` call to set values in the " +"dictionary:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1306 +msgid "" +":func:`patch.dict` can be used with dictionary like objects that aren't " +"actually dictionaries. At the very minimum they must support item getting, " +"setting, deleting and either iteration or membership test. This corresponds " +"to the magic methods :meth:`__getitem__`, :meth:`__setitem__`, :meth:" +"`__delitem__` and either :meth:`__iter__` or :meth:`__contains__`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1335 +msgid "patch.multiple" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1339 +msgid "" +"Perform multiple patches in a single call. It takes the object to be patched " +"(either as an object or a string to fetch the object by importing) and " +"keyword arguments for the patches::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1346 +msgid "" +"Use :data:`DEFAULT` as the value if you want :func:`patch.multiple` to " +"create mocks for you. In this case the created mocks are passed into a " +"decorated function by keyword, and a dictionary is returned when :func:" +"`patch.multiple` is used as a context manager." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1351 +msgid "" +":func:`patch.multiple` can be used as a decorator, class decorator or a " +"context manager. The arguments *spec*, *spec_set*, *create*, *autospec* and " +"*new_callable* have the same meaning as for :func:`patch`. These arguments " +"will be applied to *all* patches done by :func:`patch.multiple`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1356 +msgid "" +"When used as a class decorator :func:`patch.multiple` honours ``patch." +"TEST_PREFIX`` for choosing which methods to wrap." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1359 +msgid "" +"If you want :func:`patch.multiple` to create mocks for you, then you can " +"use :data:`DEFAULT` as the value. If you use :func:`patch.multiple` as a " +"decorator then the created mocks are passed into the decorated function by " +"keyword." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1373 +msgid "" +":func:`patch.multiple` can be nested with other ``patch`` decorators, but " +"put arguments passed by keyword *after* any of the standard arguments " +"created by :func:`patch`:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1385 +msgid "" +"If :func:`patch.multiple` is used as a context manager, the value returned " +"by the context manger is a dictionary where created mocks are keyed by name:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1399 +msgid "patch methods: start and stop" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1401 +msgid "" +"All the patchers have :meth:`start` and :meth:`stop` methods. These make it " +"simpler to do patching in ``setUp`` methods or where you want to do multiple " +"patches without nesting decorators or with statements." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1405 +msgid "" +"To use them call :func:`patch`, :func:`patch.object` or :func:`patch.dict` " +"as normal and keep a reference to the returned ``patcher`` object. You can " +"then call :meth:`start` to put the patch in place and :meth:`stop` to undo " +"it." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1409 +msgid "" +"If you are using :func:`patch` to create a mock for you then it will be " +"returned by the call to ``patcher.start``." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1423 +msgid "" +"A typical use case for this might be for doing multiple patches in the " +"``setUp`` method of a :class:`TestCase`:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1445 +msgid "" +"If you use this technique you must ensure that the patching is \"undone\" by " +"calling ``stop``. This can be fiddlier than you might think, because if an " +"exception is raised in the ``setUp`` then ``tearDown`` is not called. :meth:" +"`unittest.TestCase.addCleanup` makes this easier:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1460 +msgid "" +"As an added bonus you no longer need to keep a reference to the ``patcher`` " +"object." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1463 +msgid "" +"It is also possible to stop all patches which have been started by using :" +"func:`patch.stopall`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1468 +msgid "Stop all active patches. Only stops patches started with ``start``." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1474 +msgid "patch builtins" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1475 +msgid "" +"You can patch any builtins within a module. The following example patches " +"builtin :func:`ord`:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1488 +msgid "TEST_PREFIX" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1490 +msgid "" +"All of the patchers can be used as class decorators. When used in this way " +"they wrap every test method on the class. The patchers recognise methods " +"that start with ``'test'`` as being test methods. This is the same way that " +"the :class:`unittest.TestLoader` finds test methods by default." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1495 +msgid "" +"It is possible that you want to use a different prefix for your tests. You " +"can inform the patchers of the different prefix by setting ``patch." +"TEST_PREFIX``:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1518 +msgid "Nesting Patch Decorators" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1520 +msgid "" +"If you want to perform multiple patches then you can simply stack up the " +"decorators." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1523 +#: ../Doc/library/unittest.mock-examples.rst:383 +msgid "You can stack up multiple patch decorators using this pattern:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1539 +msgid "" +"Note that the decorators are applied from the bottom upwards. This is the " +"standard way that Python applies decorators. The order of the created mocks " +"passed into your test function matches this order." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1547 +msgid "Where to patch" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1549 +msgid "" +":func:`patch` works by (temporarily) changing the object that a *name* " +"points to with another one. There can be many names pointing to any " +"individual object, so for patching to work you must ensure that you patch " +"the name used by the system under test." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1554 +msgid "" +"The basic principle is that you patch where an object is *looked up*, which " +"is not necessarily the same place as where it is defined. A couple of " +"examples will help to clarify this." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1558 +msgid "" +"Imagine we have a project that we want to test with the following structure::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1567 +msgid "" +"Now we want to test ``some_function`` but we want to mock out ``SomeClass`` " +"using :func:`patch`. The problem is that when we import module b, which we " +"will have to do then it imports ``SomeClass`` from module a. If we use :func:" +"`patch` to mock out ``a.SomeClass`` then it will have no effect on our test; " +"module b already has a reference to the *real* ``SomeClass`` and it looks " +"like our patching had no effect." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1574 +msgid "" +"The key is to patch out ``SomeClass`` where it is used (or where it is " +"looked up ). In this case ``some_function`` will actually look up " +"``SomeClass`` in module b, where we have imported it. The patching should " +"look like::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1580 +msgid "" +"However, consider the alternative scenario where instead of ``from a import " +"SomeClass`` module b does ``import a`` and ``some_function`` uses ``a." +"SomeClass``. Both of these import forms are common. In this case the class " +"we want to patch is being looked up in the module and so we have to patch " +"``a.SomeClass`` instead::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1589 +msgid "Patching Descriptors and Proxy Objects" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1591 +msgid "" +"Both patch_ and patch.object_ correctly patch and restore descriptors: class " +"methods, static methods and properties. You should patch these on the " +"*class* rather than an instance. They also work with *some* objects that " +"proxy attribute access, like the `django settings object `_." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1599 +msgid "MagicMock and magic method support" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1604 +msgid "Mocking Magic Methods" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1606 +msgid "" +":class:`Mock` supports mocking the Python protocol methods, also known as " +"\"magic methods\". This allows mock objects to replace containers or other " +"objects that implement Python protocols." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1610 +msgid "" +"Because magic methods are looked up differently from normal methods [#]_, " +"this support has been specially implemented. This means that only specific " +"magic methods are supported. The supported list includes *almost* all of " +"them. If there are any missing that you need please let us know." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1615 +msgid "" +"You mock magic methods by setting the method you are interested in to a " +"function or a mock instance. If you are using a function then it *must* take " +"``self`` as the first argument [#]_." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1638 +msgid "" +"One use case for this is for mocking objects used as context managers in a :" +"keyword:`with` statement:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1650 +msgid "" +"Calls to magic methods do not appear in :attr:`~Mock.method_calls`, but they " +"are recorded in :attr:`~Mock.mock_calls`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1655 +msgid "" +"If you use the *spec* keyword argument to create a mock then attempting to " +"set a magic method that isn't in the spec will raise an :exc:" +"`AttributeError`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1658 +msgid "The full list of supported magic methods is:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1660 +msgid "``__hash__``, ``__sizeof__``, ``__repr__`` and ``__str__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1661 +msgid "``__dir__``, ``__format__`` and ``__subclasses__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1662 +msgid "``__floor__``, ``__trunc__`` and ``__ceil__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1663 +msgid "" +"Comparisons: ``__lt__``, ``__gt__``, ``__le__``, ``__ge__``, ``__eq__`` and " +"``__ne__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1665 +msgid "" +"Container methods: ``__getitem__``, ``__setitem__``, ``__delitem__``, " +"``__contains__``, ``__len__``, ``__iter__``, ``__reversed__`` and " +"``__missing__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1668 +msgid "Context manager: ``__enter__`` and ``__exit__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1669 +msgid "Unary numeric methods: ``__neg__``, ``__pos__`` and ``__invert__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1670 +msgid "" +"The numeric methods (including right hand and in-place variants): " +"``__add__``, ``__sub__``, ``__mul__``, ``__matmul__``, ``__div__``, " +"``__truediv__``, ``__floordiv__``, ``__mod__``, ``__divmod__``, " +"``__lshift__``, ``__rshift__``, ``__and__``, ``__xor__``, ``__or__``, and " +"``__pow__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1674 +msgid "" +"Numeric conversion methods: ``__complex__``, ``__int__``, ``__float__`` and " +"``__index__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1676 +msgid "Descriptor methods: ``__get__``, ``__set__`` and ``__delete__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1677 +msgid "" +"Pickling: ``__reduce__``, ``__reduce_ex__``, ``__getinitargs__``, " +"``__getnewargs__``, ``__getstate__`` and ``__setstate__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1681 +msgid "" +"The following methods exist but are *not* supported as they are either in " +"use by mock, can't be set dynamically, or can cause problems:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1684 +msgid "``__getattr__``, ``__setattr__``, ``__init__`` and ``__new__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1685 +msgid "" +"``__prepare__``, ``__instancecheck__``, ``__subclasscheck__``, ``__del__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1690 +msgid "Magic Mock" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1692 +msgid "" +"There are two ``MagicMock`` variants: :class:`MagicMock` and :class:" +"`NonCallableMagicMock`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1697 +msgid "" +"``MagicMock`` is a subclass of :class:`Mock` with default implementations of " +"most of the magic methods. You can use ``MagicMock`` without having to " +"configure the magic methods yourself." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1701 +msgid "The constructor parameters have the same meaning as for :class:`Mock`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1703 +msgid "" +"If you use the *spec* or *spec_set* arguments then *only* magic methods that " +"exist in the spec will be created." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1709 +msgid "A non-callable version of :class:`MagicMock`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1711 +msgid "" +"The constructor parameters have the same meaning as for :class:`MagicMock`, " +"with the exception of *return_value* and *side_effect* which have no meaning " +"on a non-callable mock." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1715 +msgid "" +"The magic methods are setup with :class:`MagicMock` objects, so you can " +"configure them and use them in the usual way:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1725 +msgid "" +"By default many of the protocol methods are required to return objects of a " +"specific type. These methods are preconfigured with a default return value, " +"so that they can be used without you having to do anything if you aren't " +"interested in the return value. You can still *set* the return value " +"manually if you want to change the default." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1731 +msgid "Methods and their defaults:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1733 +msgid "``__lt__``: NotImplemented" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1734 +msgid "``__gt__``: NotImplemented" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1735 +msgid "``__le__``: NotImplemented" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1736 +msgid "``__ge__``: NotImplemented" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1737 +msgid "``__int__``: 1" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1738 +msgid "``__contains__``: False" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1739 +msgid "``__len__``: 0" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1740 +msgid "``__iter__``: iter([])" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1741 +msgid "``__exit__``: False" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1742 +msgid "``__complex__``: 1j" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1743 +msgid "``__float__``: 1.0" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1744 +msgid "``__bool__``: True" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1745 +msgid "``__index__``: 1" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1746 +msgid "``__hash__``: default hash for the mock" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1747 +msgid "``__str__``: default str for the mock" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1748 +msgid "``__sizeof__``: default sizeof for the mock" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1762 +msgid "" +"The two equality methods, :meth:`__eq__` and :meth:`__ne__`, are special. " +"They do the default equality comparison on identity, using the :attr:`~Mock." +"side_effect` attribute, unless you change their return value to return " +"something else::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1776 +msgid "" +"The return value of :meth:`MagicMock.__iter__` can be any iterable object " +"and isn't required to be an iterator:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1786 +msgid "" +"If the return value *is* an iterator, then iterating over it once will " +"consume it and subsequent iterations will result in an empty list:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1795 +msgid "" +"``MagicMock`` has all of the supported magic methods configured except for " +"some of the obscure and obsolete ones. You can still set these up if you " +"want." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1798 +msgid "" +"Magic methods that are supported but not setup by default in ``MagicMock`` " +"are:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1800 +msgid "``__subclasses__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1801 +msgid "``__dir__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1802 +msgid "``__format__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1803 +msgid "``__get__``, ``__set__`` and ``__delete__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1804 +msgid "``__reversed__`` and ``__missing__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1805 +msgid "" +"``__reduce__``, ``__reduce_ex__``, ``__getinitargs__``, ``__getnewargs__``, " +"``__getstate__`` and ``__setstate__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1807 +msgid "``__getformat__`` and ``__setformat__``" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1811 +msgid "" +"Magic methods *should* be looked up on the class rather than the instance. " +"Different versions of Python are inconsistent about applying this rule. The " +"supported protocol methods should work with all supported versions of Python." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1815 +msgid "" +"The function is basically hooked up to the class, but each ``Mock`` instance " +"is kept isolated from the others." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1820 +msgid "Helpers" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1823 +msgid "sentinel" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1827 +msgid "" +"The ``sentinel`` object provides a convenient way of providing unique " +"objects for your tests." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1830 +msgid "" +"Attributes are created on demand when you access them by name. Accessing the " +"same attribute will always return the same object. The objects returned have " +"a sensible repr so that test failure messages are readable." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1834 +msgid "" +"Sometimes when testing you need to test that a specific object is passed as " +"an argument to another method, or returned. It can be common to create named " +"sentinel objects to test this. :data:`sentinel` provides a convenient way of " +"creating and testing the identity of objects like this." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1839 +msgid "" +"In this example we monkey patch ``method`` to return ``sentinel." +"some_object``:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1851 +msgid "DEFAULT" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1856 +msgid "" +"The :data:`DEFAULT` object is a pre-created sentinel (actually ``sentinel." +"DEFAULT``). It can be used by :attr:`~Mock.side_effect` functions to " +"indicate that the normal return value should be used." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1862 +msgid "call" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1866 +msgid "" +":func:`call` is a helper object for making simpler assertions, for comparing " +"with :attr:`~Mock.call_args`, :attr:`~Mock.call_args_list`, :attr:`~Mock." +"mock_calls` and :attr:`~Mock.method_calls`. :func:`call` can also be used " +"with :meth:`~Mock.assert_has_calls`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1879 +msgid "" +"For a call object that represents multiple calls, :meth:`call_list` returns " +"a list of all the intermediate calls as well as the final call." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1883 +msgid "" +"``call_list`` is particularly useful for making assertions on \"chained calls" +"\". A chained call is multiple calls on a single line of code. This results " +"in multiple entries in :attr:`~Mock.mock_calls` on a mock. Manually " +"constructing the sequence of calls can be tedious." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1888 +msgid "" +":meth:`~call.call_list` can construct the sequence of calls from the same " +"chained call:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1905 +msgid "" +"A ``call`` object is either a tuple of (positional args, keyword args) or " +"(name, positional args, keyword args) depending on how it was constructed. " +"When you construct them yourself this isn't particularly interesting, but " +"the ``call`` objects that are in the :attr:`Mock.call_args`, :attr:`Mock." +"call_args_list` and :attr:`Mock.mock_calls` attributes can be introspected " +"to get at the individual arguments they contain." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1912 +msgid "" +"The ``call`` objects in :attr:`Mock.call_args` and :attr:`Mock." +"call_args_list` are two-tuples of (positional args, keyword args) whereas " +"the ``call`` objects in :attr:`Mock.mock_calls`, along with ones you " +"construct yourself, are three-tuples of (name, positional args, keyword " +"args)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1917 +msgid "" +"You can use their \"tupleness\" to pull out the individual arguments for " +"more complex introspection and assertions. The positional arguments are a " +"tuple (an empty tuple if there are no positional arguments) and the keyword " +"arguments are a dictionary:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1951 +msgid "create_autospec" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1955 +msgid "" +"Create a mock object using another object as a spec. Attributes on the mock " +"will use the corresponding attribute on the *spec* object as their spec." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1959 +msgid "" +"Functions or methods being mocked will have their arguments checked to " +"ensure that they are called with the correct signature." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1962 +msgid "" +"If *spec_set* is ``True`` then attempting to set attributes that don't exist " +"on the spec object will raise an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1965 +msgid "" +"If a class is used as a spec then the return value of the mock (the instance " +"of the class) will have the same spec. You can use a class as the spec for " +"an instance object by passing ``instance=True``. The returned mock will only " +"be callable if instances of the mock are callable." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1970 +msgid "" +":func:`create_autospec` also takes arbitrary keyword arguments that are " +"passed to the constructor of the created mock." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1973 +msgid "" +"See :ref:`auto-speccing` for examples of how to use auto-speccing with :func:" +"`create_autospec` and the *autospec* argument to :func:`patch`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1978 +msgid "ANY" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1982 +msgid "" +"Sometimes you may need to make assertions about *some* of the arguments in a " +"call to mock, but either not care about some of the arguments or want to " +"pull them individually out of :attr:`~Mock.call_args` and make more complex " +"assertions on them." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1987 +msgid "" +"To ignore certain arguments you can pass in objects that compare equal to " +"*everything*. Calls to :meth:`~Mock.assert_called_with` and :meth:`~Mock." +"assert_called_once_with` will then succeed no matter what was passed in." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:1996 +msgid "" +":data:`ANY` can also be used in comparisons with call lists like :attr:" +"`~Mock.mock_calls`:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2009 +msgid "FILTER_DIR" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2013 +msgid "" +":data:`FILTER_DIR` is a module level variable that controls the way mock " +"objects respond to :func:`dir` (only for Python 2.6 or more recent). The " +"default is ``True``, which uses the filtering described below, to only show " +"useful members. If you dislike this filtering, or need to switch it off for " +"diagnostic purposes, then set ``mock.FILTER_DIR = False``." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2019 +msgid "" +"With filtering on, ``dir(some_mock)`` shows only useful attributes and will " +"include any dynamically created attributes that wouldn't normally be shown. " +"If the mock was created with a *spec* (or *autospec* of course) then all the " +"attributes from the original are shown, even if they haven't been accessed " +"yet:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2040 +msgid "" +"Many of the not-very-useful (private to :class:`Mock` rather than the thing " +"being mocked) underscore and double underscore prefixed attributes have been " +"filtered from the result of calling :func:`dir` on a :class:`Mock`. If you " +"dislike this behaviour you can switch it off by setting the module level " +"switch :data:`FILTER_DIR`:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2058 +msgid "" +"Alternatively you can just use ``vars(my_mock)`` (instance members) and " +"``dir(type(my_mock))`` (type members) to bypass the filtering irrespective " +"of :data:`mock.FILTER_DIR`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2064 +msgid "mock_open" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2068 +msgid "" +"A helper function to create a mock to replace the use of :func:`open`. It " +"works for :func:`open` called directly or used as a context manager." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2071 +msgid "" +"The *mock* argument is the mock object to configure. If ``None`` (the " +"default) then a :class:`MagicMock` will be created for you, with the API " +"limited to methods or attributes available on standard file handles." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2075 +msgid "" +"*read_data* is a string for the :meth:`~io.IOBase.read`, :meth:`~io.IOBase." +"readline`, and :meth:`~io.IOBase.readlines` methods of the file handle to " +"return. Calls to those methods will take data from *read_data* until it is " +"depleted. The mock of these methods is pretty simplistic: every time the " +"*mock* is called, the *read_data* is rewound to the start. If you need more " +"control over the data that you are feeding to the tested code you will need " +"to customize this mock for yourself. When that is insufficient, one of the " +"in-memory filesystem packages on `PyPI `_ can " +"offer a realistic filesystem for testing." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2085 +msgid "" +"Added :meth:`~io.IOBase.readline` and :meth:`~io.IOBase.readlines` support. " +"The mock of :meth:`~io.IOBase.read` changed to consume *read_data* rather " +"than returning it on each call." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2090 +msgid "*read_data* is now reset on each call to the *mock*." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2093 +msgid "" +"Using :func:`open` as a context manager is a great way to ensure your file " +"handles are closed properly and is becoming common::" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2099 +msgid "" +"The issue is that even if you mock out the call to :func:`open` it is the " +"*returned object* that is used as a context manager (and has :meth:" +"`__enter__` and :meth:`__exit__` called)." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2103 +msgid "" +"Mocking context managers with a :class:`MagicMock` is common enough and " +"fiddly enough that a helper function is useful." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2120 +msgid "And for reading files:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2133 +msgid "Autospeccing" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2135 +msgid "" +"Autospeccing is based on the existing :attr:`spec` feature of mock. It " +"limits the api of mocks to the api of an original object (the spec), but it " +"is recursive (implemented lazily) so that attributes of mocks only have the " +"same api as the attributes of the spec. In addition mocked functions / " +"methods have the same call signature as the original so they raise a :exc:" +"`TypeError` if they are called incorrectly." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2142 +msgid "Before I explain how auto-speccing works, here's why it is needed." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2144 +msgid "" +":class:`Mock` is a very powerful and flexible object, but it suffers from " +"two flaws when used to mock out objects from a system under test. One of " +"these flaws is specific to the :class:`Mock` api and the other is a more " +"general problem with using mock objects." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2149 +msgid "" +"First the problem specific to :class:`Mock`. :class:`Mock` has two assert " +"methods that are extremely handy: :meth:`~Mock.assert_called_with` and :meth:" +"`~Mock.assert_called_once_with`." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2162 +msgid "" +"Because mocks auto-create attributes on demand, and allow you to call them " +"with arbitrary arguments, if you misspell one of these assert methods then " +"your assertion is gone:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2172 +msgid "Your tests can pass silently and incorrectly because of the typo." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2174 +msgid "" +"The second issue is more general to mocking. If you refactor some of your " +"code, rename members and so on, any tests for code that is still using the " +"*old api* but uses mocks instead of the real objects will still pass. This " +"means your tests can all pass even though your code is broken." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2179 +msgid "" +"Note that this is another reason why you need integration tests as well as " +"unit tests. Testing everything in isolation is all fine and dandy, but if " +"you don't test how your units are \"wired together\" there is still lots of " +"room for bugs that tests might have caught." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2184 +msgid "" +":mod:`mock` already provides a feature to help with this, called speccing. " +"If you use a class or instance as the :attr:`spec` for a mock then you can " +"only access attributes on the mock that exist on the real class:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2195 +msgid "" +"The spec only applies to the mock itself, so we still have the same issue " +"with any methods on the mock:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2204 +msgid "" +"Auto-speccing solves this problem. You can either pass ``autospec=True`` to :" +"func:`patch` / :func:`patch.object` or use the :func:`create_autospec` " +"function to create a mock with a spec. If you use the ``autospec=True`` " +"argument to :func:`patch` then the object that is being replaced will be " +"used as the spec object. Because the speccing is done \"lazily\" (the spec " +"is created as attributes on the mock are accessed) you can use it with very " +"complex or deeply nested objects (like modules that import modules that " +"import modules) without a big performance hit." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2213 +msgid "Here's an example of it in use:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2223 +msgid "" +"You can see that :class:`request.Request` has a spec. :class:`request." +"Request` takes two arguments in the constructor (one of which is *self*). " +"Here's what happens if we try to call it incorrectly:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2232 +msgid "" +"The spec also applies to instantiated classes (i.e. the return value of " +"specced mocks):" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2239 +msgid "" +":class:`Request` objects are not callable, so the return value of " +"instantiating our mocked out :class:`request.Request` is a non-callable " +"mock. With the spec in place any typos in our asserts will raise the correct " +"error:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2251 +msgid "" +"In many cases you will just be able to add ``autospec=True`` to your " +"existing :func:`patch` calls and then be protected against bugs due to typos " +"and api changes." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2255 +msgid "" +"As well as using *autospec* through :func:`patch` there is a :func:" +"`create_autospec` for creating autospecced mocks directly:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2263 +msgid "" +"This isn't without caveats and limitations however, which is why it is not " +"the default behaviour. In order to know what attributes are available on the " +"spec object, autospec has to introspect (access attributes) the spec. As you " +"traverse attributes on the mock a corresponding traversal of the original " +"object is happening under the hood. If any of your specced objects have " +"properties or descriptors that can trigger code execution then you may not " +"be able to use autospec. On the other hand it is much better to design your " +"objects so that introspection is safe [#]_." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2272 +msgid "" +"A more serious problem is that it is common for instance attributes to be " +"created in the :meth:`__init__` method and not to exist on the class at all. " +"*autospec* can't know about any dynamically created attributes and restricts " +"the api to visible attributes." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2289 +msgid "" +"There are a few different ways of resolving this problem. The easiest, but " +"not necessarily the least annoying, way is to simply set the required " +"attributes on the mock after creation. Just because *autospec* doesn't allow " +"you to fetch attributes that don't exist on the spec it doesn't prevent you " +"setting them:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2300 +msgid "" +"There is a more aggressive version of both *spec* and *autospec* that *does* " +"prevent you setting non-existent attributes. This is useful if you want to " +"ensure your code only *sets* valid attributes too, but obviously it prevents " +"this particular scenario:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2313 +msgid "" +"Probably the best way of solving the problem is to add class attributes as " +"default values for instance members initialised in :meth:`__init__`. Note " +"that if you are only setting default attributes in :meth:`__init__` then " +"providing them via class attributes (shared between instances of course) is " +"faster too. e.g." +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2323 +msgid "" +"This brings up another issue. It is relatively common to provide a default " +"value of ``None`` for members that will later be an object of a different " +"type. ``None`` would be useless as a spec because it wouldn't let you access " +"*any* attributes or methods on it. As ``None`` is *never* going to be useful " +"as a spec, and probably indicates a member that will normally of some other " +"type, autospec doesn't use a spec for members that are set to ``None``. " +"These will just be ordinary mocks (well - MagicMocks):" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2338 +msgid "" +"If modifying your production classes to add defaults isn't to your liking " +"then there are more options. One of these is simply to use an instance as " +"the spec rather than the class. The other is to create a subclass of the " +"production class and add the defaults to the subclass without affecting the " +"production class. Both of these require you to use an alternative object as " +"the spec. Thankfully :func:`patch` supports this - you can simply pass the " +"alternative object as the *autospec* argument:" +msgstr "" + +#: ../Doc/library/unittest.mock.rst:2359 +msgid "" +"This only applies to classes or already instantiated objects. Calling a " +"mocked class to create a mock instance *does not* create a real instance. It " +"is only attribute lookups - along with calls to :func:`dir` - that are done." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:2 +msgid ":mod:`unittest.mock` --- getting started" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:13 +msgid "Using Mock" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:16 +msgid "Mock Patching Methods" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:18 +msgid "Common uses for :class:`Mock` objects include:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:20 +msgid "Patching methods" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:21 +msgid "Recording method calls on objects" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:23 +msgid "" +"You might want to replace a method on an object to check that it is called " +"with the correct arguments by another part of the system:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:31 +msgid "" +"Once our mock has been used (``real.method`` in this example) it has methods " +"and attributes that allow you to make assertions about how it has been used." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:36 +msgid "" +"In most of these examples the :class:`Mock` and :class:`MagicMock` classes " +"are interchangeable. As the ``MagicMock`` is the more capable class it makes " +"a sensible one to use by default." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:40 +msgid "" +"Once the mock has been called its :attr:`~Mock.called` attribute is set to " +"``True``. More importantly we can use the :meth:`~Mock.assert_called_with` " +"or :meth:`~Mock.assert_called_once_with` method to check that it was called " +"with the correct arguments." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:45 +msgid "" +"This example tests that calling ``ProductionClass().method`` results in a " +"call to the ``something`` method:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:62 +msgid "Mock for Method Calls on an Object" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:64 +msgid "" +"In the last example we patched a method directly on an object to check that " +"it was called correctly. Another common use case is to pass an object into a " +"method (or some part of the system under test) and then check that it is " +"used in the correct way." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:69 +msgid "" +"The simple ``ProductionClass`` below has a ``closer`` method. If it is " +"called with an object then it calls ``close`` on it." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:77 +msgid "" +"So to test it we need to pass in an object with a ``close`` method and check " +"that it was called correctly." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:85 +msgid "" +"We don't have to do any work to provide the 'close' method on our mock. " +"Accessing close creates it. So, if 'close' hasn't already been called then " +"accessing it in the test will create it, but :meth:`~Mock." +"assert_called_with` will raise a failure exception." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:92 +msgid "Mocking Classes" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:94 +msgid "" +"A common use case is to mock out classes instantiated by your code under " +"test. When you patch a class, then that class is replaced with a mock. " +"Instances are created by *calling the class*. This means you access the " +"\"mock instance\" by looking at the return value of the mocked class." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:99 +msgid "" +"In the example below we have a function ``some_function`` that instantiates " +"``Foo`` and calls a method on it. The call to :func:`patch` replaces the " +"class ``Foo`` with a mock. The ``Foo`` instance is the result of calling the " +"mock, so it is configured by modifying the mock :attr:`~Mock.return_value`." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:116 +msgid "Naming your mocks" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:118 +msgid "" +"It can be useful to give your mocks a name. The name is shown in the repr of " +"the mock and can be helpful when the mock appears in test failure messages. " +"The name is also propagated to attributes or methods of the mock:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:130 +msgid "Tracking all Calls" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:132 +msgid "" +"Often you want to track more than a single call to a method. The :attr:" +"`~Mock.mock_calls` attribute records all calls to child attributes of the " +"mock - and also to their children." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:144 +msgid "" +"If you make an assertion about ``mock_calls`` and any unexpected methods " +"have been called, then the assertion will fail. This is useful because as " +"well as asserting that the calls you expected have been made, you are also " +"checking that they were made in the right order and with no additional calls:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:149 +msgid "" +"You use the :data:`call` object to construct lists for comparing with " +"``mock_calls``:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:158 +msgid "Setting Return Values and Attributes" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:160 +msgid "Setting the return values on a mock object is trivially easy:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:167 +msgid "Of course you can do the same for methods on the mock:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:174 +msgid "The return value can also be set in the constructor:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:180 +msgid "If you need an attribute setting on your mock, just do it:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:187 +msgid "" +"Sometimes you want to mock up a more complex situation, like for example " +"``mock.connection.cursor().execute(\"SELECT 1\")``. If we wanted this call " +"to return a list, then we have to configure the result of the nested call." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:191 +msgid "" +"We can use :data:`call` to construct the set of calls in a \"chained call\" " +"like this for easy assertion afterwards:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:205 +msgid "" +"It is the call to ``.call_list()`` that turns our call object into a list of " +"calls representing the chained calls." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:210 +msgid "Raising exceptions with mocks" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:212 +msgid "" +"A useful attribute is :attr:`~Mock.side_effect`. If you set this to an " +"exception class or instance then the exception will be raised when the mock " +"is called." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:224 +msgid "Side effect functions and iterables" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:226 +msgid "" +"``side_effect`` can also be set to a function or an iterable. The use case " +"for ``side_effect`` as an iterable is where your mock is going to be called " +"several times, and you want each call to return a different value. When you " +"set ``side_effect`` to an iterable every call to the mock returns the next " +"value from the iterable:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:241 +msgid "" +"For more advanced use cases, like dynamically varying the return values " +"depending on what the mock is called with, ``side_effect`` can be a " +"function. The function will be called with the same arguments as the mock. " +"Whatever the function returns is what the call returns:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:258 +msgid "Creating a Mock from an Existing Object" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:260 +msgid "" +"One problem with over use of mocking is that it couples your tests to the " +"implementation of your mocks rather than your real code. Suppose you have a " +"class that implements ``some_method``. In a test for another class, you " +"provide a mock of this object that *also* provides ``some_method``. If later " +"you refactor the first class, so that it no longer has ``some_method`` - " +"then your tests will continue to pass even though your code is now broken!" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:267 +msgid "" +":class:`Mock` allows you to provide an object as a specification for the " +"mock, using the *spec* keyword argument. Accessing methods / attributes on " +"the mock that don't exist on your specification object will immediately " +"raise an attribute error. If you change the implementation of your " +"specification, then tests that use that class will start failing immediately " +"without you having to instantiate the class in those tests." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:280 +msgid "" +"Using a specification also enables a smarter matching of calls made to the " +"mock, regardless of whether some parameters were passed as positional or " +"named arguments::" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:291 +msgid "" +"If you want this smarter matching to also work with method calls on the " +"mock, you can use :ref:`auto-speccing `." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:294 +msgid "" +"If you want a stronger form of specification that prevents the setting of " +"arbitrary attributes as well as the getting of them then you can use " +"*spec_set* instead of *spec*." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:301 +msgid "Patch Decorators" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:310 +msgid "" +"A common need in tests is to patch a class attribute or a module attribute, " +"for example patching a builtin or patching a class in a module to test that " +"it is instantiated. Modules and classes are effectively global, so patching " +"on them has to be undone after the test or the patch will persist into other " +"tests and cause hard to diagnose problems." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:316 +msgid "" +"mock provides three convenient decorators for this: :func:`patch`, :func:" +"`patch.object` and :func:`patch.dict`. ``patch`` takes a single string, of " +"the form ``package.module.Class.attribute`` to specify the attribute you are " +"patching. It also optionally takes a value that you want the attribute (or " +"class or whatever) to be replaced with. 'patch.object' takes an object and " +"the name of the attribute you would like patched, plus optionally the value " +"to patch it with." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:324 +msgid "``patch.object``:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:341 +msgid "" +"If you are patching a module (including :mod:`builtins`) then use :func:" +"`patch` instead of :func:`patch.object`:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:351 +msgid "" +"The module name can be 'dotted', in the form ``package.module`` if needed:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:360 +msgid "A nice pattern is to actually decorate test methods themselves:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:371 +msgid "" +"If you want to patch with a Mock, you can use :func:`patch` with only one " +"argument (or :func:`patch.object` with two arguments). The mock will be " +"created for you and passed into the test function / method:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:394 +msgid "" +"When you nest patch decorators the mocks are passed in to the decorated " +"function in the same order they applied (the normal *python* order that " +"decorators are applied). This means from the bottom up, so in the example " +"above the mock for ``test_module.ClassName2`` is passed in first." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:410 +msgid "" +"``patch``, ``patch.object`` and ``patch.dict`` can all be used as context " +"managers." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:412 +msgid "" +"Where you use :func:`patch` to create a mock for you, you can get a " +"reference to the mock using the \"as\" form of the with statement:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:427 +msgid "" +"As an alternative ``patch``, ``patch.object`` and ``patch.dict`` can be used " +"as class decorators. When used in this way it is the same as applying the " +"decorator individually to every method whose name starts with \"test\"." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:435 +msgid "Further Examples" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:438 +msgid "Here are some more examples for some slightly more advanced scenarios." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:442 +msgid "Mocking chained calls" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:444 +msgid "" +"Mocking chained calls is actually straightforward with mock once you " +"understand the :attr:`~Mock.return_value` attribute. When a mock is called " +"for the first time, or you fetch its ``return_value`` before it has been " +"called, a new :class:`Mock` is created." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:449 +msgid "" +"This means that you can see how the object returned from a call to a mocked " +"object has been used by interrogating the ``return_value`` mock:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:457 +msgid "" +"From here it is a simple step to configure and then make assertions about " +"chained calls. Of course another alternative is writing your code in a more " +"testable way in the first place..." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:461 +msgid "So, suppose we have some code that looks a little bit like this:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:470 +msgid "" +"Assuming that ``BackendProvider`` is already well tested, how do we test " +"``method()``? Specifically, we want to test that the code section ``# more " +"code`` uses the response object in the correct way." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:474 +msgid "" +"As this chain of calls is made from an instance attribute we can monkey " +"patch the ``backend`` attribute on a ``Something`` instance. In this " +"particular case we are only interested in the return value from the final " +"call to ``start_call`` so we don't have much configuration to do. Let's " +"assume the object it returns is 'file-like', so we'll ensure that our " +"response object uses the builtin :func:`open` as its ``spec``." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:481 +msgid "" +"To do this we create a mock instance as our mock backend and create a mock " +"response object for it. To set the response as the return value for that " +"final ``start_call`` we could do this::" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:487 +msgid "" +"We can do that in a slightly nicer way using the :meth:`~Mock." +"configure_mock` method to directly set the return value for us:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:496 +msgid "" +"With these we monkey patch the \"mock backend\" in place and can make the " +"real call:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:502 +msgid "" +"Using :attr:`~Mock.mock_calls` we can check the chained call with a single " +"assert. A chained call is several calls in one line of code, so there will " +"be several entries in ``mock_calls``. We can use :meth:`call.call_list` to " +"create this list of calls for us:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:513 +msgid "Partial mocking" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:515 +msgid "" +"In some tests I wanted to mock out a call to :meth:`datetime.date.today` to " +"return a known date, but I didn't want to prevent the code under test from " +"creating new date objects. Unfortunately :class:`datetime.date` is written " +"in C, and so I couldn't just monkey-patch out the static :meth:`date.today` " +"method." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:520 +msgid "" +"I found a simple way of doing this that involved effectively wrapping the " +"date class with a mock, but passing through calls to the constructor to the " +"real class (and returning real instances)." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:524 +msgid "" +"The :func:`patch decorator ` is used here to mock out the ``date`` " +"class in the module under test. The :attr:`side_effect` attribute on the " +"mock date class is then set to a lambda function that returns a real date. " +"When the mock date class is called a real date will be constructed and " +"returned by ``side_effect``." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:539 +msgid "" +"Note that we don't patch :class:`datetime.date` globally, we patch ``date`` " +"in the module that *uses* it. See :ref:`where to patch `." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:542 +msgid "" +"When ``date.today()`` is called a known date is returned, but calls to the " +"``date(...)`` constructor still return normal dates. Without this you can " +"find yourself having to calculate an expected result using exactly the same " +"algorithm as the code under test, which is a classic testing anti-pattern." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:547 +msgid "" +"Calls to the date constructor are recorded in the ``mock_date`` attributes " +"(``call_count`` and friends) which may also be useful for your tests." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:550 +msgid "" +"An alternative way of dealing with mocking dates, or other builtin classes, " +"is discussed in `this blog entry `_." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:556 +msgid "Mocking a Generator Method" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:558 +msgid "" +"A Python generator is a function or method that uses the :keyword:`yield` " +"statement to return a series of values when iterated over [#]_." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:561 +msgid "" +"A generator method / function is called to return the generator object. It " +"is the generator object that is then iterated over. The protocol method for " +"iteration is :meth:`~container.__iter__`, so we can mock this using a :class:" +"`MagicMock`." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:566 +msgid "" +"Here's an example class with an \"iter\" method implemented as a generator:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:578 +msgid "How would we mock this class, and in particular its \"iter\" method?" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:580 +msgid "" +"To configure the values returned from the iteration (implicit in the call " +"to :class:`list`), we need to configure the object returned by the call to " +"``foo.iter()``." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:588 +msgid "" +"There are also generator expressions and more `advanced uses `_ of generators, but we aren't concerned " +"about them here. A very good introduction to generators and how powerful " +"they are is: `Generator Tricks for Systems Programmers `_." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:596 +msgid "Applying the same patch to every test method" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:598 +msgid "" +"If you want several patches in place for multiple test methods the obvious " +"way is to apply the patch decorators to every method. This can feel like " +"unnecessary repetition. For Python 2.6 or more recent you can use :func:" +"`patch` (in all its various forms) as a class decorator. This applies the " +"patches to all test methods on the class. A test method is identified by " +"methods whose names start with ``test``:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:622 +msgid "" +"An alternative way of managing patches is to use the :ref:`start-and-stop`. " +"These allow you to move the patching into your ``setUp`` and ``tearDown`` " +"methods." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:638 +msgid "" +"If you use this technique you must ensure that the patching is \"undone\" by " +"calling ``stop``. This can be fiddlier than you might think, because if an " +"exception is raised in the setUp then tearDown is not called. :meth:" +"`unittest.TestCase.addCleanup` makes this easier:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:656 +msgid "Mocking Unbound Methods" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:658 +msgid "" +"Whilst writing tests today I needed to patch an *unbound method* (patching " +"the method on the class rather than on the instance). I needed self to be " +"passed in as the first argument because I want to make asserts about which " +"objects were calling this particular method. The issue is that you can't " +"patch with a mock for this, because if you replace an unbound method with a " +"mock it doesn't become a bound method when fetched from the instance, and so " +"it doesn't get self passed in. The workaround is to patch the unbound method " +"with a real function instead. The :func:`patch` decorator makes it so simple " +"to patch out methods with a mock that having to create a real function " +"becomes a nuisance." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:669 +msgid "" +"If you pass ``autospec=True`` to patch then it does the patching with a " +"*real* function object. This function object has the same signature as the " +"one it is replacing, but delegates to a mock under the hood. You still get " +"your mock auto-created in exactly the same way as before. What it means " +"though, is that if you use it to patch out an unbound method on a class the " +"mocked function will be turned into a bound method if it is fetched from an " +"instance. It will have ``self`` passed in as the first argument, which is " +"exactly what I wanted:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:690 +msgid "" +"If we don't use ``autospec=True`` then the unbound method is patched out " +"with a Mock instance instead, and isn't called with ``self``." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:695 +msgid "Checking multiple calls with mock" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:697 +msgid "" +"mock has a nice API for making assertions about how your mock objects are " +"used." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:704 +msgid "" +"If your mock is only being called once you can use the :meth:" +"`assert_called_once_with` method that also asserts that the :attr:" +"`call_count` is one." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:715 +msgid "" +"Both ``assert_called_with`` and ``assert_called_once_with`` make assertions " +"about the *most recent* call. If your mock is going to be called several " +"times, and you want to make assertions about *all* those calls you can use :" +"attr:`~Mock.call_args_list`:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:727 +msgid "" +"The :data:`call` helper makes it easy to make assertions about these calls. " +"You can build up a list of expected calls and compare it to " +"``call_args_list``. This looks remarkably similar to the repr of the " +"``call_args_list``:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:737 +msgid "Coping with mutable arguments" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:739 +msgid "" +"Another situation is rare, but can bite you, is when your mock is called " +"with mutable arguments. ``call_args`` and ``call_args_list`` store " +"*references* to the arguments. If the arguments are mutated by the code " +"under test then you can no longer make assertions about what the values were " +"when the mock was called." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:744 +msgid "" +"Here's some example code that shows the problem. Imagine the following " +"functions defined in 'mymodule'::" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:755 +msgid "" +"When we try to test that ``grob`` calls ``frob`` with the correct argument " +"look what happens:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:770 +msgid "" +"One possibility would be for mock to copy the arguments you pass in. This " +"could then cause problems if you do assertions that rely on object identity " +"for equality." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:774 +msgid "" +"Here's one solution that uses the :attr:`side_effect` functionality. If you " +"provide a ``side_effect`` function for a mock then ``side_effect`` will be " +"called with the same args as the mock. This gives us an opportunity to copy " +"the arguments and store them for later assertions. In this example I'm using " +"*another* mock to store the arguments so that I can use the mock methods for " +"doing the assertion. Again a helper function sets this up for me." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:803 +msgid "" +"``copy_call_args`` is called with the mock that will be called. It returns a " +"new mock that we do the assertion on. The ``side_effect`` function makes a " +"copy of the args and calls our ``new_mock`` with the copy." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:809 +msgid "" +"If your mock is only going to be used once there is an easier way of " +"checking arguments at the point they are called. You can simply do the " +"checking inside a ``side_effect`` function." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:823 +msgid "" +"An alternative approach is to create a subclass of :class:`Mock` or :class:" +"`MagicMock` that copies (using :func:`copy.deepcopy`) the arguments. Here's " +"an example implementation:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:847 +msgid "" +"When you subclass ``Mock`` or ``MagicMock`` all dynamically created " +"attributes, and the ``return_value`` will use your subclass automatically. " +"That means all children of a ``CopyingMock`` will also have the type " +"``CopyingMock``." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:853 +msgid "Nesting Patches" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:855 +msgid "" +"Using patch as a context manager is nice, but if you do multiple patches you " +"can end up with nested with statements indenting further and further to the " +"right:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:873 +msgid "" +"With unittest ``cleanup`` functions and the :ref:`start-and-stop` we can " +"achieve the same effect without the nested indentation. A simple helper " +"method, ``create_patch``, puts the patch in place and returns the created " +"mock for us:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:901 +msgid "Mocking a dictionary with MagicMock" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:903 +msgid "" +"You may want to mock a dictionary, or other container object, recording all " +"access to it whilst having it still behave like a dictionary." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:906 +msgid "" +"We can do this with :class:`MagicMock`, which will behave like a dictionary, " +"and using :data:`~Mock.side_effect` to delegate dictionary access to a real " +"underlying dictionary that is under our control." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:910 +msgid "" +"When the :meth:`__getitem__` and :meth:`__setitem__` methods of our " +"``MagicMock`` are called (normal dictionary access) then ``side_effect`` is " +"called with the key (and in the case of ``__setitem__`` the value too). We " +"can also control what is returned." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:914 +msgid "" +"After the ``MagicMock`` has been used we can use attributes like :data:" +"`~Mock.call_args_list` to assert about how the dictionary was used:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:930 +msgid "" +"An alternative to using ``MagicMock`` is to use ``Mock`` and *only* provide " +"the magic methods you specifically want:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:937 +msgid "" +"A *third* option is to use ``MagicMock`` but passing in ``dict`` as the " +"*spec* (or *spec_set*) argument so that the ``MagicMock`` created only has " +"dictionary magic methods available:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:945 +msgid "" +"With these side effect functions in place, the ``mock`` will behave like a " +"normal dictionary but recording the access. It even raises a :exc:`KeyError` " +"if you try to access a key that doesn't exist." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:964 +msgid "" +"After it has been used you can make assertions about the access using the " +"normal mock methods and attributes:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:976 +msgid "Mock subclasses and their attributes" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:978 +msgid "" +"There are various reasons why you might want to subclass :class:`Mock`. One " +"reason might be to add helper methods. Here's a silly example:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:994 +msgid "" +"The standard behaviour for ``Mock`` instances is that attributes and the " +"return value mocks are of the same type as the mock they are accessed on. " +"This ensures that ``Mock`` attributes are ``Mocks`` and ``MagicMock`` " +"attributes are ``MagicMocks`` [#]_. So if you're subclassing to add helper " +"methods then they'll also be available on the attributes and return value " +"mock of instances of your subclass." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1010 +msgid "" +"Sometimes this is inconvenient. For example, `one user `_ is subclassing mock to created a `Twisted " +"adaptor `_. Having this applied to attributes too actually causes " +"errors." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1016 +msgid "" +"``Mock`` (in all its flavours) uses a method called ``_get_child_mock`` to " +"create these \"sub-mocks\" for attributes and return values. You can prevent " +"your subclass being used for attributes by overriding this method. The " +"signature is that it takes arbitrary keyword arguments (``**kwargs``) which " +"are then passed onto the mock constructor:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1033 +msgid "" +"An exception to this rule are the non-callable mocks. Attributes use the " +"callable variant because otherwise non-callable mocks couldn't have callable " +"methods." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1039 +msgid "Mocking imports with patch.dict" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1041 +msgid "" +"One situation where mocking can be hard is where you have a local import " +"inside a function. These are harder to mock because they aren't using an " +"object from the module namespace that we can patch out." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1045 +msgid "" +"Generally local imports are to be avoided. They are sometimes done to " +"prevent circular dependencies, for which there is *usually* a much better " +"way to solve the problem (refactor the code) or to prevent \"up front costs" +"\" by delaying the import. This can also be solved in better ways than an " +"unconditional local import (store the module as a class or module attribute " +"and only do the import on first use)." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1052 +msgid "" +"That aside there is a way to use ``mock`` to affect the results of an " +"import. Importing fetches an *object* from the :data:`sys.modules` " +"dictionary. Note that it fetches an *object*, which need not be a module. " +"Importing a module for the first time results in a module object being put " +"in `sys.modules`, so usually when you import something you get a module " +"back. This need not be the case however." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1059 +msgid "" +"This means you can use :func:`patch.dict` to *temporarily* put a mock in " +"place in :data:`sys.modules`. Any imports whilst this patch is active will " +"fetch the mock. When the patch is complete (the decorated function exits, " +"the with statement body is complete or ``patcher.stop()`` is called) then " +"whatever was there previously will be restored safely." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1065 +msgid "Here's an example that mocks out the 'fooble' module." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1076 +msgid "" +"As you can see the ``import fooble`` succeeds, but on exit there is no " +"'fooble' left in :data:`sys.modules`." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1079 +msgid "This also works for the ``from module import name`` form:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1089 +msgid "With slightly more work you can also mock package imports:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1102 +msgid "Tracking order of calls and less verbose call assertions" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1104 +msgid "" +"The :class:`Mock` class allows you to track the *order* of method calls on " +"your mock objects through the :attr:`~Mock.method_calls` attribute. This " +"doesn't allow you to track the order of calls between separate mock objects, " +"however we can use :attr:`~Mock.mock_calls` to achieve the same effect." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1109 +msgid "" +"Because mocks track calls to child mocks in ``mock_calls``, and accessing an " +"arbitrary attribute of a mock creates a child mock, we can create our " +"separate mocks from a parent one. Calls to those child mock will then all be " +"recorded, in order, in the ``mock_calls`` of the parent:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1126 +msgid "" +"We can then assert about the calls, including the order, by comparing with " +"the ``mock_calls`` attribute on the manager mock:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1133 +msgid "" +"If ``patch`` is creating, and putting in place, your mocks then you can " +"attach them to a manager mock using the :meth:`~Mock.attach_mock` method. " +"After attaching calls will be recorded in ``mock_calls`` of the manager." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1153 +msgid "" +"If many calls have been made, but you're only interested in a particular " +"sequence of them then an alternative is to use the :meth:`~Mock." +"assert_has_calls` method. This takes a list of calls (constructed with the :" +"data:`call` object). If that sequence of calls are in :attr:`~Mock." +"mock_calls` then the assert succeeds." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1167 +msgid "" +"Even though the chained call ``m.one().two().three()`` aren't the only calls " +"that have been made to the mock, the assert still succeeds." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1170 +msgid "" +"Sometimes a mock may have several calls made to it, and you are only " +"interested in asserting about *some* of those calls. You may not even care " +"about the order. In this case you can pass ``any_order=True`` to " +"``assert_has_calls``:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1182 +msgid "More complex argument matching" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1184 +msgid "" +"Using the same basic concept as :data:`ANY` we can implement matchers to do " +"more complex assertions on objects used as arguments to mocks." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1187 +msgid "" +"Suppose we expect some object to be passed to a mock that by default " +"compares equal based on object identity (which is the Python default for " +"user defined classes). To use :meth:`~Mock.assert_called_with` we would need " +"to pass in the exact same object. If we are only interested in some of the " +"attributes of this object then we can create a matcher that will check these " +"attributes for us." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1194 +msgid "" +"You can see in this example how a 'standard' call to ``assert_called_with`` " +"isn't sufficient:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1209 +msgid "" +"A comparison function for our ``Foo`` class might look something like this:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1221 +msgid "" +"And a matcher object that can use comparison functions like this for its " +"equality operation would look something like this:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1232 +msgid "Putting all this together:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1237 +msgid "" +"The ``Matcher`` is instantiated with our compare function and the ``Foo`` " +"object we want to compare against. In ``assert_called_with`` the ``Matcher`` " +"equality method will be called, which compares the object the mock was " +"called with against the one we created our matcher with. If they match then " +"``assert_called_with`` passes, and if they don't an :exc:`AssertionError` is " +"raised:" +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1250 +msgid "" +"With a bit of tweaking you could have the comparison function raise the :exc:" +"`AssertionError` directly and provide a more useful failure message." +msgstr "" + +#: ../Doc/library/unittest.mock-examples.rst:1253 +msgid "" +"As of version 1.5, the Python testing library `PyHamcrest `_ provides similar functionality, that may be " +"useful here, in the form of its equality matcher (`hamcrest.library." +"integration.match_equality `_)." +msgstr "" + +#: ../Doc/library/unix.rst:5 +msgid "Unix Specific Services" +msgstr "" + +#: ../Doc/library/unix.rst:7 +msgid "" +"The modules described in this chapter provide interfaces to features that " +"are unique to the Unix operating system, or in some cases to some or many " +"variants of it. Here's an overview:" +msgstr "" + +#: ../Doc/library/urllib.rst:2 +msgid ":mod:`urllib` --- URL handling modules" +msgstr "" + +#: ../Doc/library/urllib.rst:6 +msgid "**Source code:** :source:`Lib/urllib/`" +msgstr "" + +#: ../Doc/library/urllib.rst:10 +msgid "" +"``urllib`` is a package that collects several modules for working with URLs:" +msgstr "" + +#: ../Doc/library/urllib.rst:12 +msgid ":mod:`urllib.request` for opening and reading URLs" +msgstr "" + +#: ../Doc/library/urllib.rst:13 +msgid "" +":mod:`urllib.error` containing the exceptions raised by :mod:`urllib.request`" +msgstr "" + +#: ../Doc/library/urllib.rst:14 +msgid ":mod:`urllib.parse` for parsing URLs" +msgstr "" + +#: ../Doc/library/urllib.rst:15 +msgid ":mod:`urllib.robotparser` for parsing ``robots.txt`` files" +msgstr "" + +#: ../Doc/library/urllib.error.rst:2 +msgid ":mod:`urllib.error` --- Exception classes raised by urllib.request" +msgstr "" + +#: ../Doc/library/urllib.error.rst:10 +msgid "**Source code:** :source:`Lib/urllib/error.py`" +msgstr "" + +#: ../Doc/library/urllib.error.rst:14 +msgid "" +"The :mod:`urllib.error` module defines the exception classes for exceptions " +"raised by :mod:`urllib.request`. The base exception class is :exc:" +"`URLError`." +msgstr "" + +#: ../Doc/library/urllib.error.rst:17 +msgid "" +"The following exceptions are raised by :mod:`urllib.error` as appropriate:" +msgstr "" + +#: ../Doc/library/urllib.error.rst:21 +msgid "" +"The handlers raise this exception (or derived exceptions) when they run into " +"a problem. It is a subclass of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/urllib.error.rst:26 +msgid "" +"The reason for this error. It can be a message string or another exception " +"instance." +msgstr "" + +#: ../Doc/library/urllib.error.rst:29 +msgid "" +":exc:`URLError` has been made a subclass of :exc:`OSError` instead of :exc:" +"`IOError`." +msgstr "" + +#: ../Doc/library/urllib.error.rst:36 +msgid "" +"Though being an exception (a subclass of :exc:`URLError`), an :exc:" +"`HTTPError` can also function as a non-exceptional file-like return value " +"(the same thing that :func:`~urllib.request.urlopen` returns). This is " +"useful when handling exotic HTTP errors, such as requests for authentication." +msgstr "" + +#: ../Doc/library/urllib.error.rst:44 +msgid "" +"An HTTP status code as defined in `RFC 2616 `_. This numeric value corresponds to a value found in the " +"dictionary of codes as found in :attr:`http.server.BaseHTTPRequestHandler." +"responses`." +msgstr "" + +#: ../Doc/library/urllib.error.rst:51 +msgid "This is usually a string explaining the reason for this error." +msgstr "" + +#: ../Doc/library/urllib.error.rst:55 +msgid "" +"The HTTP response headers for the HTTP request that caused the :exc:" +"`HTTPError`." +msgstr "" + +#: ../Doc/library/urllib.error.rst:62 +msgid "" +"This exception is raised when the :func:`~urllib.request.urlretrieve` " +"function detects that the amount of the downloaded data is less than the " +"expected amount (given by the *Content-Length* header). The :attr:`content` " +"attribute stores the downloaded (and supposedly truncated) data." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:2 +msgid ":mod:`urllib.parse` --- Parse URLs into components" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:7 +msgid "**Source code:** :source:`Lib/urllib/parse.py`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:18 +msgid "" +"This module defines a standard interface to break Uniform Resource Locator " +"(URL) strings up in components (addressing scheme, network location, path " +"etc.), to combine the components back into a URL string, and to convert a " +"\"relative URL\" to an absolute URL given a \"base URL.\"" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:23 +msgid "" +"The module has been designed to match the Internet RFC on Relative Uniform " +"Resource Locators. It supports the following URL schemes: ``file``, ``ftp``, " +"``gopher``, ``hdl``, ``http``, ``https``, ``imap``, ``mailto``, ``mms``, " +"``news``, ``nntp``, ``prospero``, ``rsync``, ``rtsp``, ``rtspu``, ``sftp``, " +"``shttp``, ``sip``, ``sips``, ``snews``, ``svn``, ``svn+ssh``, ``telnet``, " +"``wais``, ``ws``, ``wss``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:30 +msgid "" +"The :mod:`urllib.parse` module defines functions that fall into two broad " +"categories: URL parsing and URL quoting. These are covered in detail in the " +"following sections." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:35 +msgid "URL Parsing" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:37 +msgid "" +"The URL parsing functions focus on splitting a URL string into its " +"components, or on combining URL components into a URL string." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:42 +msgid "" +"Parse a URL into six components, returning a 6-tuple. This corresponds to " +"the general structure of a URL: ``scheme://netloc/path;parameters?" +"query#fragment``. Each tuple item is a string, possibly empty. The " +"components are not broken up in smaller parts (for example, the network " +"location is a single string), and % escapes are not expanded. The delimiters " +"as shown above are not part of the result, except for a leading slash in the " +"*path* component, which is retained if present. For example:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:62 +msgid "" +"Following the syntax specifications in :rfc:`1808`, urlparse recognizes a " +"netloc only if it is properly introduced by '//'. Otherwise the input is " +"presumed to be a relative URL and thus to start with a path component." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:78 +msgid "" +"The *scheme* argument gives the default addressing scheme, to be used only " +"if the URL does not specify one. It should be the same type (text or bytes) " +"as *urlstring*, except that the default value ``''`` is always allowed, and " +"is automatically converted to ``b''`` if appropriate." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:83 +msgid "" +"If the *allow_fragments* argument is false, fragment identifiers are not " +"recognized. Instead, they are parsed as part of the path, parameters or " +"query component, and :attr:`fragment` is set to the empty string in the " +"return value." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:88 ../Doc/library/urllib.parse.rst:209 +#: ../Doc/library/urllib.parse.rst:294 +msgid "" +"The return value is actually an instance of a subclass of :class:`tuple`. " +"This class has the following additional read-only convenience attributes:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:92 ../Doc/library/urllib.parse.rst:213 +#: ../Doc/library/urllib.parse.rst:298 +msgid "Value if not present" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:94 ../Doc/library/urllib.parse.rst:215 +msgid ":attr:`scheme`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:94 ../Doc/library/urllib.parse.rst:215 +msgid "URL scheme specifier" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:94 ../Doc/library/urllib.parse.rst:215 +msgid "*scheme* parameter" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:96 ../Doc/library/urllib.parse.rst:217 +msgid ":attr:`netloc`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:96 ../Doc/library/urllib.parse.rst:217 +msgid "Network location part" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:96 ../Doc/library/urllib.parse.rst:98 +#: ../Doc/library/urllib.parse.rst:100 ../Doc/library/urllib.parse.rst:103 +#: ../Doc/library/urllib.parse.rst:105 ../Doc/library/urllib.parse.rst:217 +#: ../Doc/library/urllib.parse.rst:219 ../Doc/library/urllib.parse.rst:221 +#: ../Doc/library/urllib.parse.rst:223 ../Doc/library/urllib.parse.rst:300 +#: ../Doc/library/urllib.parse.rst:302 +msgid "empty string" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:98 ../Doc/library/urllib.parse.rst:219 +msgid ":attr:`path`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:98 ../Doc/library/urllib.parse.rst:219 +msgid "Hierarchical path" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:100 +msgid ":attr:`params`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:100 +msgid "Parameters for last path element" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:103 ../Doc/library/urllib.parse.rst:221 +msgid ":attr:`query`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:103 ../Doc/library/urllib.parse.rst:221 +msgid "Query component" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:105 ../Doc/library/urllib.parse.rst:223 +#: ../Doc/library/urllib.parse.rst:302 +msgid ":attr:`fragment`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:105 ../Doc/library/urllib.parse.rst:223 +#: ../Doc/library/urllib.parse.rst:302 +msgid "Fragment identifier" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:107 ../Doc/library/urllib.parse.rst:225 +msgid ":attr:`username`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:107 ../Doc/library/urllib.parse.rst:225 +msgid "User name" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:109 ../Doc/library/urllib.parse.rst:227 +msgid ":attr:`password`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:109 ../Doc/library/urllib.parse.rst:227 +msgid "Password" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:111 ../Doc/library/urllib.parse.rst:229 +msgid ":attr:`hostname`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:111 ../Doc/library/urllib.parse.rst:229 +msgid "Host name (lower case)" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:113 ../Doc/library/urllib.parse.rst:231 +msgid ":attr:`port`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:113 ../Doc/library/urllib.parse.rst:231 +msgid "Port number as integer, if present" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:117 ../Doc/library/urllib.parse.rst:235 +msgid "" +"Reading the :attr:`port` attribute will raise a :exc:`ValueError` if an " +"invalid port is specified in the URL. See section :ref:`urlparse-result-" +"object` for more information on the result object." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:121 +msgid "Added IPv6 URL parsing capabilities." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:124 +msgid "" +"The fragment is now parsed for all URL schemes (unless *allow_fragment* is " +"false), in accordance with :rfc:`3986`. Previously, a whitelist of schemes " +"that support fragments existed." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:129 ../Doc/library/urllib.parse.rst:239 +msgid "" +"Out-of-range port numbers now raise :exc:`ValueError`, instead of returning :" +"const:`None`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:136 +msgid "" +"Parse a query string given as a string argument (data of type :mimetype:" +"`application/x-www-form-urlencoded`). Data are returned as a dictionary. " +"The dictionary keys are the unique query variable names and the values are " +"lists of values for each name." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:141 ../Doc/library/urllib.parse.rst:170 +msgid "" +"The optional argument *keep_blank_values* is a flag indicating whether blank " +"values in percent-encoded queries should be treated as blank strings. A true " +"value indicates that blanks should be retained as blank strings. The " +"default false value indicates that blank values are to be ignored and " +"treated as if they were not included." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:147 ../Doc/library/urllib.parse.rst:176 +msgid "" +"The optional argument *strict_parsing* is a flag indicating what to do with " +"parsing errors. If false (the default), errors are silently ignored. If " +"true, errors raise a :exc:`ValueError` exception." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:151 ../Doc/library/urllib.parse.rst:180 +msgid "" +"The optional *encoding* and *errors* parameters specify how to decode " +"percent-encoded sequences into Unicode characters, as accepted by the :meth:" +"`bytes.decode` method." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:155 +msgid "" +"Use the :func:`urllib.parse.urlencode` function (with the ``doseq`` " +"parameter set to ``True``) to convert such dictionaries into query strings." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:160 ../Doc/library/urllib.parse.rst:187 +msgid "Add *encoding* and *errors* parameters." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:166 +msgid "" +"Parse a query string given as a string argument (data of type :mimetype:" +"`application/x-www-form-urlencoded`). Data are returned as a list of name, " +"value pairs." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:184 +msgid "" +"Use the :func:`urllib.parse.urlencode` function to convert such lists of " +"pairs into query strings." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:193 +msgid "" +"Construct a URL from a tuple as returned by ``urlparse()``. The *parts* " +"argument can be any six-item iterable. This may result in a slightly " +"different, but equivalent URL, if the URL that was parsed originally had " +"unnecessary delimiters (for example, a ``?`` with an empty query; the RFC " +"states that these are equivalent)." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:202 +msgid "" +"This is similar to :func:`urlparse`, but does not split the params from the " +"URL. This should generally be used instead of :func:`urlparse` if the more " +"recent URL syntax allowing parameters to be applied to each segment of the " +"*path* portion of the URL (see :rfc:`2396`) is wanted. A separate function " +"is needed to separate the path segments and parameters. This function " +"returns a 5-tuple: (addressing scheme, network location, path, query, " +"fragment identifier)." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:246 +msgid "" +"Combine the elements of a tuple as returned by :func:`urlsplit` into a " +"complete URL as a string. The *parts* argument can be any five-item " +"iterable. This may result in a slightly different, but equivalent URL, if " +"the URL that was parsed originally had unnecessary delimiters (for example, " +"a ? with an empty query; the RFC states that these are equivalent)." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:255 +msgid "" +"Construct a full (\"absolute\") URL by combining a \"base URL\" (*base*) " +"with another URL (*url*). Informally, this uses components of the base URL, " +"in particular the addressing scheme, the network location and (part of) the " +"path, to provide missing components in the relative URL. For example:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:264 +msgid "" +"The *allow_fragments* argument has the same meaning and default as for :func:" +"`urlparse`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:269 +msgid "" +"If *url* is an absolute URL (that is, starting with ``//`` or ``scheme://" +"``), the *url*'s host name and/or scheme will be present in the result. For " +"example:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:278 +msgid "" +"If you do not want that behavior, preprocess the *url* with :func:`urlsplit` " +"and :func:`urlunsplit`, removing possible *scheme* and *netloc* parts." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:284 +msgid "Behaviour updated to match the semantics defined in :rfc:`3986`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:289 +msgid "" +"If *url* contains a fragment identifier, return a modified version of *url* " +"with no fragment identifier, and the fragment identifier as a separate " +"string. If there is no fragment identifier in *url*, return *url* " +"unmodified and an empty string." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:300 +msgid ":attr:`url`" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:300 +msgid "URL with no fragment" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:305 +msgid "" +"See section :ref:`urlparse-result-object` for more information on the result " +"object." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:308 +msgid "Result is a structured object rather than a simple 2-tuple." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:314 +msgid "Parsing ASCII Encoded Bytes" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:316 +msgid "" +"The URL parsing functions were originally designed to operate on character " +"strings only. In practice, it is useful to be able to manipulate properly " +"quoted and encoded URLs as sequences of ASCII bytes. Accordingly, the URL " +"parsing functions in this module all operate on :class:`bytes` and :class:" +"`bytearray` objects in addition to :class:`str` objects." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:322 +msgid "" +"If :class:`str` data is passed in, the result will also contain only :class:" +"`str` data. If :class:`bytes` or :class:`bytearray` data is passed in, the " +"result will contain only :class:`bytes` data." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:326 +msgid "" +"Attempting to mix :class:`str` data with :class:`bytes` or :class:" +"`bytearray` in a single function call will result in a :exc:`TypeError` " +"being raised, while attempting to pass in non-ASCII byte values will " +"trigger :exc:`UnicodeDecodeError`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:331 +msgid "" +"To support easier conversion of result objects between :class:`str` and :" +"class:`bytes`, all return values from URL parsing functions provide either " +"an :meth:`encode` method (when the result contains :class:`str` data) or a :" +"meth:`decode` method (when the result contains :class:`bytes` data). The " +"signatures of these methods match those of the corresponding :class:`str` " +"and :class:`bytes` methods (except that the default encoding is ``'ascii'`` " +"rather than ``'utf-8'``). Each produces a value of a corresponding type that " +"contains either :class:`bytes` data (for :meth:`encode` methods) or :class:" +"`str` data (for :meth:`decode` methods)." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:342 +msgid "" +"Applications that need to operate on potentially improperly quoted URLs that " +"may contain non-ASCII data will need to do their own decoding from bytes to " +"characters before invoking the URL parsing methods." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:346 +msgid "" +"The behaviour described in this section applies only to the URL parsing " +"functions. The URL quoting functions use their own rules when producing or " +"consuming byte sequences as detailed in the documentation of the individual " +"URL quoting functions." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:351 +msgid "URL parsing functions now accept ASCII encoded byte sequences" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:358 +msgid "Structured Parse Results" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:360 +msgid "" +"The result objects from the :func:`urlparse`, :func:`urlsplit` and :func:" +"`urldefrag` functions are subclasses of the :class:`tuple` type. These " +"subclasses add the attributes listed in the documentation for those " +"functions, the encoding and decoding support described in the previous " +"section, as well as an additional method:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:368 +msgid "" +"Return the re-combined version of the original URL as a string. This may " +"differ from the original URL in that the scheme may be normalized to lower " +"case and empty components may be dropped. Specifically, empty parameters, " +"queries, and fragment identifiers will be removed." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:373 +msgid "" +"For :func:`urldefrag` results, only empty fragment identifiers will be " +"removed. For :func:`urlsplit` and :func:`urlparse` results, all noted " +"changes will be made to the URL returned by this method." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:377 +msgid "" +"The result of this method remains unchanged if passed back through the " +"original parsing function:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:390 +msgid "" +"The following classes provide the implementations of the structured parse " +"results when operating on :class:`str` objects:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:395 +msgid "" +"Concrete class for :func:`urldefrag` results containing :class:`str` data. " +"The :meth:`encode` method returns a :class:`DefragResultBytes` instance." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:403 +msgid "" +"Concrete class for :func:`urlparse` results containing :class:`str` data. " +"The :meth:`encode` method returns a :class:`ParseResultBytes` instance." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:409 +msgid "" +"Concrete class for :func:`urlsplit` results containing :class:`str` data. " +"The :meth:`encode` method returns a :class:`SplitResultBytes` instance." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:414 +msgid "" +"The following classes provide the implementations of the parse results when " +"operating on :class:`bytes` or :class:`bytearray` objects:" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:419 +msgid "" +"Concrete class for :func:`urldefrag` results containing :class:`bytes` data. " +"The :meth:`decode` method returns a :class:`DefragResult` instance." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:427 +msgid "" +"Concrete class for :func:`urlparse` results containing :class:`bytes` data. " +"The :meth:`decode` method returns a :class:`ParseResult` instance." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:435 +msgid "" +"Concrete class for :func:`urlsplit` results containing :class:`bytes` data. " +"The :meth:`decode` method returns a :class:`SplitResult` instance." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:443 +msgid "URL Quoting" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:445 +msgid "" +"The URL quoting functions focus on taking program data and making it safe " +"for use as URL components by quoting special characters and appropriately " +"encoding non-ASCII text. They also support reversing these operations to " +"recreate the original data from the contents of a URL component if that task " +"isn't already covered by the URL parsing functions above." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:453 +msgid "" +"Replace special characters in *string* using the ``%xx`` escape. Letters, " +"digits, and the characters ``'_.-'`` are never quoted. By default, this " +"function is intended for quoting the path section of URL. The optional " +"*safe* parameter specifies additional ASCII characters that should not be " +"quoted --- its default value is ``'/'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:459 ../Doc/library/urllib.parse.rst:525 +msgid "*string* may be either a :class:`str` or a :class:`bytes`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:461 +msgid "" +"The optional *encoding* and *errors* parameters specify how to deal with non-" +"ASCII characters, as accepted by the :meth:`str.encode` method. *encoding* " +"defaults to ``'utf-8'``. *errors* defaults to ``'strict'``, meaning " +"unsupported characters raise a :class:`UnicodeEncodeError`. *encoding* and " +"*errors* must not be supplied if *string* is a :class:`bytes`, or a :class:" +"`TypeError` is raised." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:469 +msgid "" +"Note that ``quote(string, safe, encoding, errors)`` is equivalent to " +"``quote_from_bytes(string.encode(encoding, errors), safe)``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:472 +msgid "Example: ``quote('/El Niño/')`` yields ``'/El%20Ni%C3%B1o/'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:477 +msgid "" +"Like :func:`quote`, but also replace spaces by plus signs, as required for " +"quoting HTML form values when building up a query string to go into a URL. " +"Plus signs in the original string are escaped unless they are included in " +"*safe*. It also does not have *safe* default to ``'/'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:482 +msgid "Example: ``quote_plus('/El Niño/')`` yields ``'%2FEl+Ni%C3%B1o%2F'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:487 +msgid "" +"Like :func:`quote`, but accepts a :class:`bytes` object rather than a :class:" +"`str`, and does not perform string-to-bytes encoding." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:490 +msgid "Example: ``quote_from_bytes(b'a&\\xef')`` yields ``'a%26%EF'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:496 +msgid "" +"Replace ``%xx`` escapes by their single-character equivalent. The optional " +"*encoding* and *errors* parameters specify how to decode percent-encoded " +"sequences into Unicode characters, as accepted by the :meth:`bytes.decode` " +"method." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:501 ../Doc/library/urllib.parse.rst:515 +msgid "*string* must be a :class:`str`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:503 +msgid "" +"*encoding* defaults to ``'utf-8'``. *errors* defaults to ``'replace'``, " +"meaning invalid sequences are replaced by a placeholder character." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:507 +msgid "Example: ``unquote('/El%20Ni%C3%B1o/')`` yields ``'/El Niño/'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:512 +msgid "" +"Like :func:`unquote`, but also replace plus signs by spaces, as required for " +"unquoting HTML form values." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:517 +msgid "Example: ``unquote_plus('/El+Ni%C3%B1o/')`` yields ``'/El Niño/'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:522 +msgid "" +"Replace ``%xx`` escapes by their single-octet equivalent, and return a :" +"class:`bytes` object." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:527 +msgid "" +"If it is a :class:`str`, unescaped non-ASCII characters in *string* are " +"encoded into UTF-8 bytes." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:530 +msgid "Example: ``unquote_to_bytes('a%26%EF')`` yields ``b'a&\\xef'``." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:536 +msgid "" +"Convert a mapping object or a sequence of two-element tuples, which may " +"contain :class:`str` or :class:`bytes` objects, to a percent-encoded ASCII " +"text string. If the resultant string is to be used as a *data* for POST " +"operation with the :func:`~urllib.request.urlopen` function, then it should " +"be encoded to bytes, otherwise it would result in a :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:543 +msgid "" +"The resulting string is a series of ``key=value`` pairs separated by ``'&'`` " +"characters, where both *key* and *value* are quoted using the *quote_via* " +"function. By default, :func:`quote_plus` is used to quote the values, which " +"means spaces are quoted as a ``'+'`` character and '/' characters are " +"encoded as ``%2F``, which follows the standard for GET requests " +"(``application/x-www-form-urlencoded``). An alternate function that can be " +"passed as *quote_via* is :func:`quote`, which will encode spaces as ``%20`` " +"and not encode '/' characters. For maximum control of what is quoted, use " +"``quote`` and specify a value for *safe*." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:553 +msgid "" +"When a sequence of two-element tuples is used as the *query* argument, the " +"first element of each tuple is a key and the second is a value. The value " +"element in itself can be a sequence and in that case, if the optional " +"parameter *doseq* is evaluates to *True*, individual ``key=value`` pairs " +"separated by ``'&'`` are generated for each element of the value sequence " +"for the key. The order of parameters in the encoded string will match the " +"order of parameter tuples in the sequence." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:561 +msgid "" +"The *safe*, *encoding*, and *errors* parameters are passed down to " +"*quote_via* (the *encoding* and *errors* parameters are only passed when a " +"query element is a :class:`str`)." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:565 +msgid "" +"To reverse this encoding process, :func:`parse_qs` and :func:`parse_qsl` are " +"provided in this module to parse query strings into Python data structures." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:568 +msgid "" +"Refer to :ref:`urllib examples ` to find out how urlencode " +"method can be used for generating query string for a URL or data for POST." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:571 +msgid "Query parameter supports bytes and string objects." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:574 +msgid "*quote_via* parameter." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:584 +msgid ":rfc:`3986` - Uniform Resource Identifiers" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:581 +msgid "" +"This is the current standard (STD66). Any changes to urllib.parse module " +"should conform to this. Certain deviations could be observed, which are " +"mostly for backward compatibility purposes and for certain de-facto parsing " +"requirements as commonly observed in major browsers." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:587 +msgid ":rfc:`2732` - Format for Literal IPv6 Addresses in URL's." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:587 +msgid "This specifies the parsing requirements of IPv6 URLs." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:591 +msgid ":rfc:`2396` - Uniform Resource Identifiers (URI): Generic Syntax" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:590 +msgid "" +"Document describing the generic syntactic requirements for both Uniform " +"Resource Names (URNs) and Uniform Resource Locators (URLs)." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:594 +msgid ":rfc:`2368` - The mailto URL scheme." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:594 +msgid "Parsing requirements for mailto URL schemes." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:599 +msgid ":rfc:`1808` - Relative Uniform Resource Locators" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:597 +msgid "" +"This Request For Comments includes the rules for joining an absolute and a " +"relative URL, including a fair number of \"Abnormal Examples\" which govern " +"the treatment of border cases." +msgstr "" + +#: ../Doc/library/urllib.parse.rst:601 +msgid ":rfc:`1738` - Uniform Resource Locators (URL)" +msgstr "" + +#: ../Doc/library/urllib.parse.rst:602 +msgid "This specifies the formal syntax and semantics of absolute URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:2 +msgid ":mod:`urllib.request` --- Extensible library for opening URLs" +msgstr "" + +#: ../Doc/library/urllib.request.rst:11 +msgid "**Source code:** :source:`Lib/urllib/request.py`" +msgstr "" + +#: ../Doc/library/urllib.request.rst:15 +msgid "" +"The :mod:`urllib.request` module defines functions and classes which help in " +"opening URLs (mostly HTTP) in a complex world --- basic and digest " +"authentication, redirections, cookies and more." +msgstr "" + +#: ../Doc/library/urllib.request.rst:25 +msgid "The :mod:`urllib.request` module defines the following functions:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:30 +msgid "" +"Open the URL *url*, which can be either a string or a :class:`Request` " +"object." +msgstr "" + +#: ../Doc/library/urllib.request.rst:33 +msgid "" +"*data* must be an object specifying additional data to be sent to the " +"server, or ``None`` if no such data is needed. See :class:`Request` for " +"details." +msgstr "" + +#: ../Doc/library/urllib.request.rst:37 +msgid "" +"urllib.request module uses HTTP/1.1 and includes ``Connection:close`` header " +"in its HTTP requests." +msgstr "" + +#: ../Doc/library/urllib.request.rst:40 +msgid "" +"The optional *timeout* parameter specifies a timeout in seconds for blocking " +"operations like the connection attempt (if not specified, the global default " +"timeout setting will be used). This actually only works for HTTP, HTTPS and " +"FTP connections." +msgstr "" + +#: ../Doc/library/urllib.request.rst:45 +msgid "" +"If *context* is specified, it must be a :class:`ssl.SSLContext` instance " +"describing the various SSL options. See :class:`~http.client." +"HTTPSConnection` for more details." +msgstr "" + +#: ../Doc/library/urllib.request.rst:49 +msgid "" +"The optional *cafile* and *capath* parameters specify a set of trusted CA " +"certificates for HTTPS requests. *cafile* should point to a single file " +"containing a bundle of CA certificates, whereas *capath* should point to a " +"directory of hashed certificate files. More information can be found in :" +"meth:`ssl.SSLContext.load_verify_locations`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:55 +msgid "The *cadefault* parameter is ignored." +msgstr "" + +#: ../Doc/library/urllib.request.rst:57 +msgid "" +"This function always returns an object which can work as a :term:`context " +"manager` and has methods such as" +msgstr "" + +#: ../Doc/library/urllib.request.rst:60 +msgid "" +":meth:`~urllib.response.addinfourl.geturl` --- return the URL of the " +"resource retrieved, commonly used to determine if a redirect was followed" +msgstr "" + +#: ../Doc/library/urllib.request.rst:63 +msgid "" +":meth:`~urllib.response.addinfourl.info` --- return the meta-information of " +"the page, such as headers, in the form of an :func:`email." +"message_from_string` instance (see `Quick Reference to HTTP Headers `_)" +msgstr "" + +#: ../Doc/library/urllib.request.rst:67 +msgid "" +":meth:`~urllib.response.addinfourl.getcode` -- return the HTTP status code " +"of the response." +msgstr "" + +#: ../Doc/library/urllib.request.rst:69 +msgid "" +"For HTTP and HTTPS URLs, this function returns a :class:`http.client." +"HTTPResponse` object slightly modified. In addition to the three new methods " +"above, the msg attribute contains the same information as the :attr:`~http." +"client.HTTPResponse.reason` attribute --- the reason phrase returned by " +"server --- instead of the response headers as it is specified in the " +"documentation for :class:`~http.client.HTTPResponse`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:77 +msgid "" +"For FTP, file, and data URLs and requests explicitly handled by legacy :" +"class:`URLopener` and :class:`FancyURLopener` classes, this function returns " +"a :class:`urllib.response.addinfourl` object." +msgstr "" + +#: ../Doc/library/urllib.request.rst:81 +msgid "Raises :exc:`~urllib.error.URLError` on protocol errors." +msgstr "" + +#: ../Doc/library/urllib.request.rst:83 +msgid "" +"Note that ``None`` may be returned if no handler handles the request (though " +"the default installed global :class:`OpenerDirector` uses :class:" +"`UnknownHandler` to ensure this never happens)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:87 +msgid "" +"In addition, if proxy settings are detected (for example, when a ``*_proxy`` " +"environment variable like :envvar:`http_proxy` is set), :class:" +"`ProxyHandler` is default installed and makes sure the requests are handled " +"through the proxy." +msgstr "" + +#: ../Doc/library/urllib.request.rst:92 +msgid "" +"The legacy ``urllib.urlopen`` function from Python 2.6 and earlier has been " +"discontinued; :func:`urllib.request.urlopen` corresponds to the old " +"``urllib2.urlopen``. Proxy handling, which was done by passing a dictionary " +"parameter to ``urllib.urlopen``, can be obtained by using :class:" +"`ProxyHandler` objects." +msgstr "" + +#: ../Doc/library/urllib.request.rst:98 +msgid "*cafile* and *capath* were added." +msgstr "" + +#: ../Doc/library/urllib.request.rst:101 +msgid "" +"HTTPS virtual hosts are now supported if possible (that is, if :data:`ssl." +"HAS_SNI` is true)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:105 +msgid "*data* can be an iterable object." +msgstr "" + +#: ../Doc/library/urllib.request.rst:108 +msgid "*cadefault* was added." +msgstr "" + +#: ../Doc/library/urllib.request.rst:116 +msgid "" +"*cafile*, *capath* and *cadefault* are deprecated in favor of *context*. " +"Please use :meth:`ssl.SSLContext.load_cert_chain` instead, or let :func:`ssl." +"create_default_context` select the system's trusted CA certificates for you." +msgstr "" + +#: ../Doc/library/urllib.request.rst:123 +msgid "" +"Install an :class:`OpenerDirector` instance as the default global opener. " +"Installing an opener is only necessary if you want urlopen to use that " +"opener; otherwise, simply call :meth:`OpenerDirector.open` instead of :func:" +"`~urllib.request.urlopen`. The code does not check for a real :class:" +"`OpenerDirector`, and any class with the appropriate interface will work." +msgstr "" + +#: ../Doc/library/urllib.request.rst:133 +msgid "" +"Return an :class:`OpenerDirector` instance, which chains the handlers in the " +"order given. *handler*\\s can be either instances of :class:`BaseHandler`, " +"or subclasses of :class:`BaseHandler` (in which case it must be possible to " +"call the constructor without any parameters). Instances of the following " +"classes will be in front of the *handler*\\s, unless the *handler*\\s " +"contain them, instances of them or subclasses of them: :class:`ProxyHandler` " +"(if proxy settings are detected), :class:`UnknownHandler`, :class:" +"`HTTPHandler`, :class:`HTTPDefaultErrorHandler`, :class:" +"`HTTPRedirectHandler`, :class:`FTPHandler`, :class:`FileHandler`, :class:" +"`HTTPErrorProcessor`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:143 +msgid "" +"If the Python installation has SSL support (i.e., if the :mod:`ssl` module " +"can be imported), :class:`HTTPSHandler` will also be added." +msgstr "" + +#: ../Doc/library/urllib.request.rst:146 +msgid "" +"A :class:`BaseHandler` subclass may also change its :attr:`handler_order` " +"attribute to modify its position in the handlers list." +msgstr "" + +#: ../Doc/library/urllib.request.rst:152 +msgid "" +"Convert the pathname *path* from the local syntax for a path to the form " +"used in the path component of a URL. This does not produce a complete URL. " +"The return value will already be quoted using the :func:`~urllib.parse." +"quote` function." +msgstr "" + +#: ../Doc/library/urllib.request.rst:159 +msgid "" +"Convert the path component *path* from a percent-encoded URL to the local " +"syntax for a path. This does not accept a complete URL. This function " +"uses :func:`~urllib.parse.unquote` to decode *path*." +msgstr "" + +#: ../Doc/library/urllib.request.rst:165 +msgid "" +"This helper function returns a dictionary of scheme to proxy server URL " +"mappings. It scans the environment for variables named ``_proxy``, " +"in a case insensitive approach, for all operating systems first, and when it " +"cannot find it, looks for proxy information from Mac OSX System " +"Configuration for Mac OS X and Windows Systems Registry for Windows. If both " +"lowercase and uppercase environment variables exist (and disagree), " +"lowercase is preferred." +msgstr "" + +#: ../Doc/library/urllib.request.rst:175 +msgid "" +"If the environment variable ``REQUEST_METHOD`` is set, which usually " +"indicates your script is running in a CGI environment, the environment " +"variable ``HTTP_PROXY`` (uppercase ``_PROXY``) will be ignored. This is " +"because that variable can be injected by a client using the \"Proxy:\" HTTP " +"header. If you need to use an HTTP proxy in a CGI environment, either use " +"``ProxyHandler`` explicitly, or make sure the variable name is in lowercase " +"(or at least the ``_proxy`` suffix)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:188 +msgid "This class is an abstraction of a URL request." +msgstr "" + +#: ../Doc/library/urllib.request.rst:190 +msgid "*url* should be a string containing a valid URL." +msgstr "" + +#: ../Doc/library/urllib.request.rst:192 +msgid "" +"*data* must be an object specifying additional data to send to the server, " +"or ``None`` if no such data is needed. Currently HTTP requests are the only " +"ones that use *data*. The supported object types include bytes, file-like " +"objects, and iterables. If no ``Content-Length`` nor ``Transfer-Encoding`` " +"header field has been provided, :class:`HTTPHandler` will set these headers " +"according to the type of *data*. ``Content-Length`` will be used to send " +"bytes objects, while ``Transfer-Encoding: chunked`` as specified in :rfc:" +"`7230`, Section 3.3.1 will be used to send files and other iterables." +msgstr "" + +#: ../Doc/library/urllib.request.rst:202 +msgid "" +"For an HTTP POST request method, *data* should be a buffer in the standard :" +"mimetype:`application/x-www-form-urlencoded` format. The :func:`urllib." +"parse.urlencode` function takes a mapping or sequence of 2-tuples and " +"returns an ASCII string in this format. It should be encoded to bytes before " +"being used as the *data* parameter." +msgstr "" + +#: ../Doc/library/urllib.request.rst:208 +msgid "" +"*headers* should be a dictionary, and will be treated as if :meth:" +"`add_header` was called with each key and value as arguments. This is often " +"used to \"spoof\" the ``User-Agent`` header value, which is used by a " +"browser to identify itself -- some HTTP servers only allow requests coming " +"from common browsers as opposed to scripts. For example, Mozilla Firefox may " +"identify itself as ``\"Mozilla/5.0 (X11; U; Linux i686) Gecko/20071127 " +"Firefox/2.0.0.11\"``, while :mod:`urllib`'s default user agent string is ``" +"\"Python-urllib/2.6\"`` (on Python 2.6)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:218 +msgid "" +"An appropriate ``Content-Type`` header should be included if the *data* " +"argument is present. If this header has not been provided and *data* is not " +"None, ``Content-Type: application/x-www-form-urlencoded`` will be added as a " +"default." +msgstr "" + +#: ../Doc/library/urllib.request.rst:223 +msgid "" +"The final two arguments are only of interest for correct handling of third-" +"party HTTP cookies:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:226 +msgid "" +"*origin_req_host* should be the request-host of the origin transaction, as " +"defined by :rfc:`2965`. It defaults to ``http.cookiejar." +"request_host(self)``. This is the host name or IP address of the original " +"request that was initiated by the user. For example, if the request is for " +"an image in an HTML document, this should be the request-host of the request " +"for the page containing the image." +msgstr "" + +#: ../Doc/library/urllib.request.rst:234 +msgid "" +"*unverifiable* should indicate whether the request is unverifiable, as " +"defined by RFC 2965. It defaults to ``False``. An unverifiable request is " +"one whose URL the user did not have the option to approve. For example, if " +"the request is for an image in an HTML document, and the user had no option " +"to approve the automatic fetching of the image, this should be true." +msgstr "" + +#: ../Doc/library/urllib.request.rst:241 +msgid "" +"*method* should be a string that indicates the HTTP request method that will " +"be used (e.g. ``'HEAD'``). If provided, its value is stored in the :attr:" +"`~Request.method` attribute and is used by :meth:`get_method()`. The default " +"is ``'GET'`` if *data* is ``None`` or ``'POST'`` otherwise. Subclasses may " +"indicate a different default method by setting the :attr:`~Request.method` " +"attribute in the class itself." +msgstr "" + +#: ../Doc/library/urllib.request.rst:249 +msgid "" +"The request will not work as expected if the data object is unable to " +"deliver its content more than once (e.g. a file or an iterable that can " +"produce the content only once) and the request is retried for HTTP redirects " +"or authentication. The *data* is sent to the HTTP server right away after " +"the headers. There is no support for a 100-continue expectation in the " +"library." +msgstr "" + +#: ../Doc/library/urllib.request.rst:256 +msgid ":attr:`Request.method` argument is added to the Request class." +msgstr "" + +#: ../Doc/library/urllib.request.rst:259 +msgid "Default :attr:`Request.method` may be indicated at the class level." +msgstr "" + +#: ../Doc/library/urllib.request.rst:262 +msgid "" +"Do not raise an error if the ``Content-Length`` has not been provided and " +"*data* is neither ``None`` nor a bytes object. Fall back to use chunked " +"transfer encoding instead." +msgstr "" + +#: ../Doc/library/urllib.request.rst:269 +msgid "" +"The :class:`OpenerDirector` class opens URLs via :class:`BaseHandler`\\ s " +"chained together. It manages the chaining of handlers, and recovery from " +"errors." +msgstr "" + +#: ../Doc/library/urllib.request.rst:275 +msgid "" +"This is the base class for all registered handlers --- and handles only the " +"simple mechanics of registration." +msgstr "" + +#: ../Doc/library/urllib.request.rst:281 +msgid "" +"A class which defines a default handler for HTTP error responses; all " +"responses are turned into :exc:`~urllib.error.HTTPError` exceptions." +msgstr "" + +#: ../Doc/library/urllib.request.rst:287 +msgid "A class to handle redirections." +msgstr "" + +#: ../Doc/library/urllib.request.rst:292 +msgid "A class to handle HTTP Cookies." +msgstr "" + +#: ../Doc/library/urllib.request.rst:297 +msgid "" +"Cause requests to go through a proxy. If *proxies* is given, it must be a " +"dictionary mapping protocol names to URLs of proxies. The default is to read " +"the list of proxies from the environment variables :envvar:" +"`_proxy`. If no proxy environment variables are set, then in a " +"Windows environment proxy settings are obtained from the registry's Internet " +"Settings section, and in a Mac OS X environment proxy information is " +"retrieved from the OS X System Configuration Framework." +msgstr "" + +#: ../Doc/library/urllib.request.rst:305 +msgid "To disable autodetected proxy pass an empty dictionary." +msgstr "" + +#: ../Doc/library/urllib.request.rst:307 +msgid "" +"The :envvar:`no_proxy` environment variable can be used to specify hosts " +"which shouldn't be reached via proxy; if set, it should be a comma-separated " +"list of hostname suffixes, optionally with ``:port`` appended, for example " +"``cern.ch,ncsa.uiuc.edu,some.host:8080``." +msgstr "" + +#: ../Doc/library/urllib.request.rst:314 +msgid "" +"``HTTP_PROXY`` will be ignored if a variable ``REQUEST_METHOD`` is set; see " +"the documentation on :func:`~urllib.request.getproxies`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:320 +msgid "Keep a database of ``(realm, uri) -> (user, password)`` mappings." +msgstr "" + +#: ../Doc/library/urllib.request.rst:325 +msgid "" +"Keep a database of ``(realm, uri) -> (user, password)`` mappings. A realm " +"of ``None`` is considered a catch-all realm, which is searched if no other " +"realm fits." +msgstr "" + +#: ../Doc/library/urllib.request.rst:332 +msgid "" +"A variant of :class:`HTTPPasswordMgrWithDefaultRealm` that also has a " +"database of ``uri -> is_authenticated`` mappings. Can be used by a " +"BasicAuth handler to determine when to send authentication credentials " +"immediately instead of waiting for a ``401`` response first." +msgstr "" + +#: ../Doc/library/urllib.request.rst:342 +msgid "" +"This is a mixin class that helps with HTTP authentication, both to the " +"remote host and to a proxy. *password_mgr*, if given, should be something " +"that is compatible with :class:`HTTPPasswordMgr`; refer to section :ref:" +"`http-password-mgr` for information on the interface that must be " +"supported. If *passwd_mgr* also provides ``is_authenticated`` and " +"``update_authenticated`` methods (see :ref:`http-password-mgr-with-prior-" +"auth`), then the handler will use the ``is_authenticated`` result for a " +"given URI to determine whether or not to send authentication credentials " +"with the request. If ``is_authenticated`` returns ``True`` for the URI, " +"credentials are sent. If ``is_authenticated`` is ``False``, credentials are " +"not sent, and then if a ``401`` response is received the request is re-sent " +"with the authentication credentials. If authentication succeeds, " +"``update_authenticated`` is called to set ``is_authenticated`` ``True`` for " +"the URI, so that subsequent requests to the URI or any of its super-URIs " +"will automatically include the authentication credentials." +msgstr "" + +#: ../Doc/library/urllib.request.rst:359 +msgid "Added ``is_authenticated`` support." +msgstr "" + +#: ../Doc/library/urllib.request.rst:365 +msgid "" +"Handle authentication with the remote host. *password_mgr*, if given, should " +"be something that is compatible with :class:`HTTPPasswordMgr`; refer to " +"section :ref:`http-password-mgr` for information on the interface that must " +"be supported. HTTPBasicAuthHandler will raise a :exc:`ValueError` when " +"presented with a wrong Authentication scheme." +msgstr "" + +#: ../Doc/library/urllib.request.rst:374 ../Doc/library/urllib.request.rst:408 +msgid "" +"Handle authentication with the proxy. *password_mgr*, if given, should be " +"something that is compatible with :class:`HTTPPasswordMgr`; refer to " +"section :ref:`http-password-mgr` for information on the interface that must " +"be supported." +msgstr "" + +#: ../Doc/library/urllib.request.rst:382 +msgid "" +"This is a mixin class that helps with HTTP authentication, both to the " +"remote host and to a proxy. *password_mgr*, if given, should be something " +"that is compatible with :class:`HTTPPasswordMgr`; refer to section :ref:" +"`http-password-mgr` for information on the interface that must be supported." +msgstr "" + +#: ../Doc/library/urllib.request.rst:391 +msgid "" +"Handle authentication with the remote host. *password_mgr*, if given, should " +"be something that is compatible with :class:`HTTPPasswordMgr`; refer to " +"section :ref:`http-password-mgr` for information on the interface that must " +"be supported. When both Digest Authentication Handler and Basic " +"Authentication Handler are both added, Digest Authentication is always tried " +"first. If the Digest Authentication returns a 40x response again, it is sent " +"to Basic Authentication handler to Handle. This Handler method will raise " +"a :exc:`ValueError` when presented with an authentication scheme other than " +"Digest or Basic." +msgstr "" + +#: ../Doc/library/urllib.request.rst:401 +msgid "Raise :exc:`ValueError` on unsupported Authentication Scheme." +msgstr "" + +#: ../Doc/library/urllib.request.rst:416 +msgid "A class to handle opening of HTTP URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:421 +msgid "" +"A class to handle opening of HTTPS URLs. *context* and *check_hostname* " +"have the same meaning as in :class:`http.client.HTTPSConnection`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:424 +msgid "*context* and *check_hostname* were added." +msgstr "" + +#: ../Doc/library/urllib.request.rst:430 +msgid "Open local files." +msgstr "" + +#: ../Doc/library/urllib.request.rst:434 +msgid "Open data URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:440 +msgid "Open FTP URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:445 +msgid "" +"Open FTP URLs, keeping a cache of open FTP connections to minimize delays." +msgstr "" + +#: ../Doc/library/urllib.request.rst:450 +msgid "A catch-all class to handle unknown URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:455 ../Doc/library/urllib.request.rst:1130 +msgid "Process HTTP error responses." +msgstr "" + +#: ../Doc/library/urllib.request.rst:461 +msgid "Request Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:463 +msgid "" +"The following methods describe :class:`Request`'s public interface, and so " +"all may be overridden in subclasses. It also defines several public " +"attributes that can be used by clients to inspect the parsed request." +msgstr "" + +#: ../Doc/library/urllib.request.rst:470 +msgid "The original URL passed to the constructor." +msgstr "" + +#: ../Doc/library/urllib.request.rst:474 +msgid "" +"Request.full_url is a property with setter, getter and a deleter. Getting :" +"attr:`~Request.full_url` returns the original request URL with the fragment, " +"if it was present." +msgstr "" + +#: ../Doc/library/urllib.request.rst:480 +msgid "The URI scheme." +msgstr "" + +#: ../Doc/library/urllib.request.rst:484 +msgid "" +"The URI authority, typically a host, but may also contain a port separated " +"by a colon." +msgstr "" + +#: ../Doc/library/urllib.request.rst:489 +msgid "The original host for the request, without port." +msgstr "" + +#: ../Doc/library/urllib.request.rst:493 +msgid "" +"The URI path. If the :class:`Request` uses a proxy, then selector will be " +"the full URL that is passed to the proxy." +msgstr "" + +#: ../Doc/library/urllib.request.rst:498 +msgid "The entity body for the request, or None if not specified." +msgstr "" + +#: ../Doc/library/urllib.request.rst:500 +msgid "" +"Changing value of :attr:`Request.data` now deletes \"Content-Length\" header " +"if it was previously set or calculated." +msgstr "" + +#: ../Doc/library/urllib.request.rst:506 +msgid "" +"boolean, indicates whether the request is unverifiable as defined by RFC " +"2965." +msgstr "" + +#: ../Doc/library/urllib.request.rst:511 +msgid "" +"The HTTP request method to use. By default its value is :const:`None`, " +"which means that :meth:`~Request.get_method` will do its normal computation " +"of the method to be used. Its value can be set (thus overriding the default " +"computation in :meth:`~Request.get_method`) either by providing a default " +"value by setting it at the class level in a :class:`Request` subclass, or by " +"passing a value in to the :class:`Request` constructor via the *method* " +"argument." +msgstr "" + +#: ../Doc/library/urllib.request.rst:521 +msgid "" +"A default value can now be set in subclasses; previously it could only be " +"set via the constructor argument." +msgstr "" + +#: ../Doc/library/urllib.request.rst:528 +msgid "" +"Return a string indicating the HTTP request method. If :attr:`Request." +"method` is not ``None``, return its value, otherwise return ``'GET'`` if :" +"attr:`Request.data` is ``None``, or ``'POST'`` if it's not. This is only " +"meaningful for HTTP requests." +msgstr "" + +#: ../Doc/library/urllib.request.rst:533 +msgid "get_method now looks at the value of :attr:`Request.method`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:539 +msgid "" +"Add another header to the request. Headers are currently ignored by all " +"handlers except HTTP handlers, where they are added to the list of headers " +"sent to the server. Note that there cannot be more than one header with the " +"same name, and later calls will overwrite previous calls in case the *key* " +"collides. Currently, this is no loss of HTTP functionality, since all " +"headers which have meaning when used more than once have a (header-specific) " +"way of gaining the same functionality using only one header." +msgstr "" + +#: ../Doc/library/urllib.request.rst:550 +msgid "Add a header that will not be added to a redirected request." +msgstr "" + +#: ../Doc/library/urllib.request.rst:555 +msgid "" +"Return whether the instance has the named header (checks both regular and " +"unredirected)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:561 +msgid "" +"Remove named header from the request instance (both from regular and " +"unredirected headers)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:569 +msgid "Return the URL given in the constructor." +msgstr "" + +#: ../Doc/library/urllib.request.rst:573 +msgid "Returns :attr:`Request.full_url`" +msgstr "" + +#: ../Doc/library/urllib.request.rst:578 +msgid "" +"Prepare the request by connecting to a proxy server. The *host* and *type* " +"will replace those of the instance, and the instance's selector will be the " +"original URL given in the constructor." +msgstr "" + +#: ../Doc/library/urllib.request.rst:585 +msgid "" +"Return the value of the given header. If the header is not present, return " +"the default value." +msgstr "" + +#: ../Doc/library/urllib.request.rst:591 +msgid "" +"Return a list of tuples (header_name, header_value) of the Request headers." +msgstr "" + +#: ../Doc/library/urllib.request.rst:593 +msgid "" +"The request methods add_data, has_data, get_data, get_type, get_host, " +"get_selector, get_origin_req_host and is_unverifiable that were deprecated " +"since 3.3 have been removed." +msgstr "" + +#: ../Doc/library/urllib.request.rst:602 +msgid "OpenerDirector Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:604 +msgid ":class:`OpenerDirector` instances have the following methods:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:609 +msgid "" +"*handler* should be an instance of :class:`BaseHandler`. The following " +"methods are searched, and added to the possible chains (note that HTTP " +"errors are a special case)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:613 +msgid "" +":meth:`protocol_open` --- signal that the handler knows how to open " +"*protocol* URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:616 +msgid "" +":meth:`http_error_type` --- signal that the handler knows how to handle HTTP " +"errors with HTTP error code *type*." +msgstr "" + +#: ../Doc/library/urllib.request.rst:619 +msgid "" +":meth:`protocol_error` --- signal that the handler knows how to handle " +"errors from (non-\\ ``http``) *protocol*." +msgstr "" + +#: ../Doc/library/urllib.request.rst:622 +msgid "" +":meth:`protocol_request` --- signal that the handler knows how to pre-" +"process *protocol* requests." +msgstr "" + +#: ../Doc/library/urllib.request.rst:625 +msgid "" +":meth:`protocol_response` --- signal that the handler knows how to post-" +"process *protocol* responses." +msgstr "" + +#: ../Doc/library/urllib.request.rst:631 +msgid "" +"Open the given *url* (which can be a request object or a string), optionally " +"passing the given *data*. Arguments, return values and exceptions raised are " +"the same as those of :func:`urlopen` (which simply calls the :meth:`open` " +"method on the currently installed global :class:`OpenerDirector`). The " +"optional *timeout* parameter specifies a timeout in seconds for blocking " +"operations like the connection attempt (if not specified, the global default " +"timeout setting will be used). The timeout feature actually works only for " +"HTTP, HTTPS and FTP connections)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:643 +msgid "" +"Handle an error of the given protocol. This will call the registered error " +"handlers for the given protocol with the given arguments (which are protocol " +"specific). The HTTP protocol is a special case which uses the HTTP response " +"code to determine the specific error handler; refer to the :meth:`http_error_" +"\\*` methods of the handler classes." +msgstr "" + +#: ../Doc/library/urllib.request.rst:649 +msgid "" +"Return values and exceptions raised are the same as those of :func:`urlopen`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:651 +msgid "OpenerDirector objects open URLs in three stages:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:653 +msgid "" +"The order in which these methods are called within each stage is determined " +"by sorting the handler instances." +msgstr "" + +#: ../Doc/library/urllib.request.rst:656 +msgid "" +"Every handler with a method named like :meth:`protocol_request` has that " +"method called to pre-process the request." +msgstr "" + +#: ../Doc/library/urllib.request.rst:659 +msgid "" +"Handlers with a method named like :meth:`protocol_open` are called to handle " +"the request. This stage ends when a handler either returns a non-\\ :const:" +"`None` value (ie. a response), or raises an exception (usually :exc:`~urllib." +"error.URLError`). Exceptions are allowed to propagate." +msgstr "" + +#: ../Doc/library/urllib.request.rst:664 +msgid "" +"In fact, the above algorithm is first tried for methods named :meth:" +"`default_open`. If all such methods return :const:`None`, the algorithm is " +"repeated for methods named like :meth:`protocol_open`. If all such methods " +"return :const:`None`, the algorithm is repeated for methods named :meth:" +"`unknown_open`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:670 +msgid "" +"Note that the implementation of these methods may involve calls of the " +"parent :class:`OpenerDirector` instance's :meth:`~OpenerDirector.open` and :" +"meth:`~OpenerDirector.error` methods." +msgstr "" + +#: ../Doc/library/urllib.request.rst:674 +msgid "" +"Every handler with a method named like :meth:`protocol_response` has that " +"method called to post-process the response." +msgstr "" + +#: ../Doc/library/urllib.request.rst:681 +msgid "BaseHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:683 +msgid "" +":class:`BaseHandler` objects provide a couple of methods that are directly " +"useful, and others that are meant to be used by derived classes. These are " +"intended for direct use:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:690 +msgid "Add a director as parent." +msgstr "" + +#: ../Doc/library/urllib.request.rst:695 +msgid "Remove any parents." +msgstr "" + +#: ../Doc/library/urllib.request.rst:697 +msgid "" +"The following attribute and methods should only be used by classes derived " +"from :class:`BaseHandler`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:702 +msgid "" +"The convention has been adopted that subclasses defining :meth:" +"`protocol_request` or :meth:`protocol_response` methods are named :class:`" +"\\*Processor`; all others are named :class:`\\*Handler`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:709 +msgid "" +"A valid :class:`OpenerDirector`, which can be used to open using a different " +"protocol, or handle errors." +msgstr "" + +#: ../Doc/library/urllib.request.rst:715 +msgid "" +"This method is *not* defined in :class:`BaseHandler`, but subclasses should " +"define it if they want to catch all URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:718 +msgid "" +"This method, if implemented, will be called by the parent :class:" +"`OpenerDirector`. It should return a file-like object as described in the " +"return value of the :meth:`open` of :class:`OpenerDirector`, or ``None``. It " +"should raise :exc:`~urllib.error.URLError`, unless a truly exceptional thing " +"happens (for example, :exc:`MemoryError` should not be mapped to :exc:" +"`URLError`)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:725 +msgid "This method will be called before any protocol-specific open method." +msgstr "" + +#: ../Doc/library/urllib.request.rst:731 +msgid "" +"This method is *not* defined in :class:`BaseHandler`, but subclasses should " +"define it if they want to handle URLs with the given protocol." +msgstr "" + +#: ../Doc/library/urllib.request.rst:734 +msgid "" +"This method, if defined, will be called by the parent :class:" +"`OpenerDirector`. Return values should be the same as for :meth:" +"`default_open`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:740 +msgid "" +"This method is *not* defined in :class:`BaseHandler`, but subclasses should " +"define it if they want to catch all URLs with no specific registered handler " +"to open it." +msgstr "" + +#: ../Doc/library/urllib.request.rst:744 +msgid "" +"This method, if implemented, will be called by the :attr:`parent` :class:" +"`OpenerDirector`. Return values should be the same as for :meth:" +"`default_open`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:751 +msgid "" +"This method is *not* defined in :class:`BaseHandler`, but subclasses should " +"override it if they intend to provide a catch-all for otherwise unhandled " +"HTTP errors. It will be called automatically by the :class:" +"`OpenerDirector` getting the error, and should not normally be called in " +"other circumstances." +msgstr "" + +#: ../Doc/library/urllib.request.rst:756 +msgid "" +"*req* will be a :class:`Request` object, *fp* will be a file-like object " +"with the HTTP error body, *code* will be the three-digit code of the error, " +"*msg* will be the user-visible explanation of the code and *hdrs* will be a " +"mapping object with the headers of the error." +msgstr "" + +#: ../Doc/library/urllib.request.rst:761 +msgid "" +"Return values and exceptions raised should be the same as those of :func:" +"`urlopen`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:767 +msgid "" +"*nnn* should be a three-digit HTTP error code. This method is also not " +"defined in :class:`BaseHandler`, but will be called, if it exists, on an " +"instance of a subclass, when an HTTP error with code *nnn* occurs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:771 +msgid "Subclasses should override this method to handle specific HTTP errors." +msgstr "" + +#: ../Doc/library/urllib.request.rst:773 +msgid "" +"Arguments, return values and exceptions raised should be the same as for :" +"meth:`http_error_default`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:780 +msgid "" +"This method is *not* defined in :class:`BaseHandler`, but subclasses should " +"define it if they want to pre-process requests of the given protocol." +msgstr "" + +#: ../Doc/library/urllib.request.rst:783 +msgid "" +"This method, if defined, will be called by the parent :class:" +"`OpenerDirector`. *req* will be a :class:`Request` object. The return value " +"should be a :class:`Request` object." +msgstr "" + +#: ../Doc/library/urllib.request.rst:791 +msgid "" +"This method is *not* defined in :class:`BaseHandler`, but subclasses should " +"define it if they want to post-process responses of the given protocol." +msgstr "" + +#: ../Doc/library/urllib.request.rst:794 +msgid "" +"This method, if defined, will be called by the parent :class:" +"`OpenerDirector`. *req* will be a :class:`Request` object. *response* will " +"be an object implementing the same interface as the return value of :func:" +"`urlopen`. The return value should implement the same interface as the " +"return value of :func:`urlopen`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:804 +msgid "HTTPRedirectHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:808 +msgid "" +"Some HTTP redirections require action from this module's client code. If " +"this is the case, :exc:`~urllib.error.HTTPError` is raised. See :rfc:`2616` " +"for details of the precise meanings of the various redirection codes." +msgstr "" + +#: ../Doc/library/urllib.request.rst:812 +msgid "" +"An :class:`HTTPError` exception raised as a security consideration if the " +"HTTPRedirectHandler is presented with a redirected URL which is not an HTTP, " +"HTTPS or FTP URL." +msgstr "" + +#: ../Doc/library/urllib.request.rst:819 +msgid "" +"Return a :class:`Request` or ``None`` in response to a redirect. This is " +"called by the default implementations of the :meth:`http_error_30\\*` " +"methods when a redirection is received from the server. If a redirection " +"should take place, return a new :class:`Request` to allow :meth:" +"`http_error_30\\*` to perform the redirect to *newurl*. Otherwise, raise :" +"exc:`~urllib.error.HTTPError` if no other handler should try to handle this " +"URL, or return ``None`` if you can't but another handler might." +msgstr "" + +#: ../Doc/library/urllib.request.rst:829 +msgid "" +"The default implementation of this method does not strictly follow :rfc:" +"`2616`, which says that 301 and 302 responses to ``POST`` requests must not " +"be automatically redirected without confirmation by the user. In reality, " +"browsers do allow automatic redirection of these responses, changing the " +"POST to a ``GET``, and the default implementation reproduces this behavior." +msgstr "" + +#: ../Doc/library/urllib.request.rst:838 +msgid "" +"Redirect to the ``Location:`` or ``URI:`` URL. This method is called by the " +"parent :class:`OpenerDirector` when getting an HTTP 'moved permanently' " +"response." +msgstr "" + +#: ../Doc/library/urllib.request.rst:844 +msgid "" +"The same as :meth:`http_error_301`, but called for the 'found' response." +msgstr "" + +#: ../Doc/library/urllib.request.rst:849 +msgid "" +"The same as :meth:`http_error_301`, but called for the 'see other' response." +msgstr "" + +#: ../Doc/library/urllib.request.rst:854 +msgid "" +"The same as :meth:`http_error_301`, but called for the 'temporary redirect' " +"response." +msgstr "" + +#: ../Doc/library/urllib.request.rst:861 +msgid "HTTPCookieProcessor Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:863 +msgid ":class:`HTTPCookieProcessor` instances have one attribute:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:867 +msgid "The :class:`http.cookiejar.CookieJar` in which cookies are stored." +msgstr "" + +#: ../Doc/library/urllib.request.rst:873 +msgid "ProxyHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:879 +msgid "" +"The :class:`ProxyHandler` will have a method :meth:`protocol_open` for every " +"*protocol* which has a proxy in the *proxies* dictionary given in the " +"constructor. The method will modify requests to go through the proxy, by " +"calling ``request.set_proxy()``, and call the next handler in the chain to " +"actually execute the protocol." +msgstr "" + +#: ../Doc/library/urllib.request.rst:889 +msgid "HTTPPasswordMgr Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:891 +msgid "" +"These methods are available on :class:`HTTPPasswordMgr` and :class:" +"`HTTPPasswordMgrWithDefaultRealm` objects." +msgstr "" + +#: ../Doc/library/urllib.request.rst:897 +msgid "" +"*uri* can be either a single URI, or a sequence of URIs. *realm*, *user* and " +"*passwd* must be strings. This causes ``(user, passwd)`` to be used as " +"authentication tokens when authentication for *realm* and a super-URI of any " +"of the given URIs is given." +msgstr "" + +#: ../Doc/library/urllib.request.rst:905 +msgid "" +"Get user/password for given realm and URI, if any. This method will return " +"``(None, None)`` if there is no matching user/password." +msgstr "" + +#: ../Doc/library/urllib.request.rst:908 +msgid "" +"For :class:`HTTPPasswordMgrWithDefaultRealm` objects, the realm ``None`` " +"will be searched if the given *realm* has no matching user/password." +msgstr "" + +#: ../Doc/library/urllib.request.rst:915 +msgid "HTTPPasswordMgrWithPriorAuth Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:917 +msgid "" +"This password manager extends :class:`HTTPPasswordMgrWithDefaultRealm` to " +"support tracking URIs for which authentication credentials should always be " +"sent." +msgstr "" + +#: ../Doc/library/urllib.request.rst:924 +msgid "" +"*realm*, *uri*, *user*, *passwd* are as for :meth:`HTTPPasswordMgr." +"add_password`. *is_authenticated* sets the initial value of the " +"``is_authenticated`` flag for the given URI or list of URIs. If " +"*is_authenticated* is specified as ``True``, *realm* is ignored." +msgstr "" + +#: ../Doc/library/urllib.request.rst:932 +msgid "Same as for :class:`HTTPPasswordMgrWithDefaultRealm` objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:938 +msgid "" +"Update the ``is_authenticated`` flag for the given *uri* or list of URIs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:944 +msgid "" +"Returns the current state of the ``is_authenticated`` flag for the given URI." +msgstr "" + +#: ../Doc/library/urllib.request.rst:951 +msgid "AbstractBasicAuthHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:956 +msgid "" +"Handle an authentication request by getting a user/password pair, and re-" +"trying the request. *authreq* should be the name of the header where the " +"information about the realm is included in the request, *host* specifies the " +"URL and path to authenticate for, *req* should be the (failed) :class:" +"`Request` object, and *headers* should be the error headers." +msgstr "" + +#: ../Doc/library/urllib.request.rst:962 +msgid "" +"*host* is either an authority (e.g. ``\"python.org\"``) or a URL containing " +"an authority component (e.g. ``\"http://python.org/\"``). In either case, " +"the authority must not contain a userinfo component (so, ``\"python.org\"`` " +"and ``\"python.org:80\"`` are fine, ``\"joe:password@python.org\"`` is not)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:971 +msgid "HTTPBasicAuthHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:976 ../Doc/library/urllib.request.rst:987 +#: ../Doc/library/urllib.request.rst:1012 +#: ../Doc/library/urllib.request.rst:1023 +msgid "Retry the request with authentication information, if available." +msgstr "" + +#: ../Doc/library/urllib.request.rst:982 +msgid "ProxyBasicAuthHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:993 +msgid "AbstractDigestAuthHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:998 +msgid "" +"*authreq* should be the name of the header where the information about the " +"realm is included in the request, *host* should be the host to authenticate " +"to, *req* should be the (failed) :class:`Request` object, and *headers* " +"should be the error headers." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1007 +msgid "HTTPDigestAuthHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1018 +msgid "ProxyDigestAuthHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1029 +msgid "HTTPHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1034 +msgid "" +"Send an HTTP request, which can be either GET or POST, depending on ``req." +"has_data()``." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1041 +msgid "HTTPSHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1046 +msgid "" +"Send an HTTPS request, which can be either GET or POST, depending on ``req." +"has_data()``." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1053 +msgid "FileHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1058 +msgid "" +"Open the file locally, if there is no host name, or the host name is " +"``'localhost'``." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1061 +msgid "" +"This method is applicable only for local hostnames. When a remote hostname " +"is given, an :exc:`~urllib.error.URLError` is raised." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1069 +msgid "DataHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1073 +msgid "" +"Read a data URL. This kind of URL contains the content encoded in the URL " +"itself. The data URL syntax is specified in :rfc:`2397`. This implementation " +"ignores white spaces in base64 encoded data URLs so the URL may be wrapped " +"in whatever source file it comes from. But even though some browsers don't " +"mind about a missing padding at the end of a base64 encoded data URL, this " +"implementation will raise an :exc:`ValueError` in that case." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1084 +msgid "FTPHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1089 +msgid "" +"Open the FTP file indicated by *req*. The login is always done with empty " +"username and password." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1096 +msgid "CacheFTPHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1098 +msgid "" +":class:`CacheFTPHandler` objects are :class:`FTPHandler` objects with the " +"following additional methods:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1104 +msgid "Set timeout of connections to *t* seconds." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1109 +msgid "Set maximum number of cached connections to *m*." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1115 +msgid "UnknownHandler Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1120 +msgid "Raise a :exc:`~urllib.error.URLError` exception." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1126 +msgid "HTTPErrorProcessor Objects" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1132 +msgid "For 200 error codes, the response object is returned immediately." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1134 +msgid "" +"For non-200 error codes, this simply passes the job on to the :meth:" +"`protocol_error_code` handler methods, via :meth:`OpenerDirector.error`. " +"Eventually, :class:`HTTPDefaultErrorHandler` will raise an :exc:`~urllib." +"error.HTTPError` if no other handler handles the error." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1142 +msgid "Process HTTPS error responses." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1144 +msgid "The behavior is same as :meth:`http_response`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1152 +msgid "" +"In addition to the examples below, more examples are given in :ref:`urllib-" +"howto`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1155 +msgid "" +"This example gets the python.org main page and displays the first 300 bytes " +"of it. ::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1168 +msgid "" +"Note that urlopen returns a bytes object. This is because there is no way " +"for urlopen to automatically determine the encoding of the byte stream it " +"receives from the HTTP server. In general, a program will decode the " +"returned bytes object to string once it determines or guesses the " +"appropriate encoding." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1174 +msgid "" +"The following W3C document, https://www.w3.org/International/O-charset\\ , " +"lists the various ways in which an (X)HTML or an XML document could have " +"specified its encoding information." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1178 +msgid "" +"As the python.org website uses *utf-8* encoding as specified in its meta " +"tag, we will use the same for decoding the bytes object. ::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1187 +msgid "" +"It is also possible to achieve the same result without using the :term:" +"`context manager` approach. ::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1196 +msgid "" +"In the following example, we are sending a data-stream to the stdin of a CGI " +"and reading the data it returns to us. Note that this example will only work " +"when the Python installation supports SSL. ::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1208 +msgid "The code for the sample CGI used in the above example is::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1215 +msgid "Here is an example of doing a ``PUT`` request using :class:`Request`::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1225 +msgid "Use of Basic HTTP Authentication::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1239 +msgid "" +":func:`build_opener` provides many handlers by default, including a :class:" +"`ProxyHandler`. By default, :class:`ProxyHandler` uses the environment " +"variables named ``_proxy``, where ```` is the URL scheme " +"involved. For example, the :envvar:`http_proxy` environment variable is " +"read to obtain the HTTP proxy's URL." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1245 +msgid "" +"This example replaces the default :class:`ProxyHandler` with one that uses " +"programmatically-supplied proxy URLs, and adds proxy authorization support " +"with :class:`ProxyBasicAuthHandler`. ::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1257 +msgid "Adding HTTP headers:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1259 +msgid "Use the *headers* argument to the :class:`Request` constructor, or::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1268 +msgid "" +":class:`OpenerDirector` automatically adds a :mailheader:`User-Agent` header " +"to every :class:`Request`. To change this::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1276 +msgid "" +"Also, remember that a few standard headers (:mailheader:`Content-Length`, :" +"mailheader:`Content-Type` and :mailheader:`Host`) are added when the :class:" +"`Request` is passed to :func:`urlopen` (or :meth:`OpenerDirector.open`)." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1283 +msgid "" +"Here is an example session that uses the ``GET`` method to retrieve a URL " +"containing parameters::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1294 +msgid "" +"The following example uses the ``POST`` method instead. Note that params " +"output from urlencode is encoded to bytes before it is sent to urlopen as " +"data::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1305 +msgid "" +"The following example uses an explicitly specified HTTP proxy, overriding " +"environment settings::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1315 +msgid "" +"The following example uses no proxies at all, overriding environment " +"settings::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1325 +msgid "Legacy interface" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1327 +msgid "" +"The following functions and classes are ported from the Python 2 module " +"``urllib`` (as opposed to ``urllib2``). They might become deprecated at " +"some point in the future." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1333 +msgid "" +"Copy a network object denoted by a URL to a local file. If the URL points to " +"a local file, the object will not be copied unless filename is supplied. " +"Return a tuple ``(filename, headers)`` where *filename* is the local file " +"name under which the object can be found, and *headers* is whatever the :" +"meth:`info` method of the object returned by :func:`urlopen` returned (for a " +"remote object). Exceptions are the same as for :func:`urlopen`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1340 +msgid "" +"The second argument, if present, specifies the file location to copy to (if " +"absent, the location will be a tempfile with a generated name). The third " +"argument, if present, is a hook function that will be called once on " +"establishment of the network connection and once after each block read " +"thereafter. The hook will be passed three arguments; a count of blocks " +"transferred so far, a block size in bytes, and the total size of the file. " +"The third argument may be ``-1`` on older FTP servers which do not return a " +"file size in response to a retrieval request." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1349 +msgid "The following example illustrates the most common usage scenario::" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1356 +msgid "" +"If the *url* uses the :file:`http:` scheme identifier, the optional *data* " +"argument may be given to specify a ``POST`` request (normally the request " +"type is ``GET``). The *data* argument must be a bytes object in standard :" +"mimetype:`application/x-www-form-urlencoded` format; see the :func:`urllib." +"parse.urlencode` function." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1362 +msgid "" +":func:`urlretrieve` will raise :exc:`ContentTooShortError` when it detects " +"that the amount of data available was less than the expected amount (which " +"is the size reported by a *Content-Length* header). This can occur, for " +"example, when the download is interrupted." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1367 +msgid "" +"The *Content-Length* is treated as a lower bound: if there's more data to " +"read, urlretrieve reads more data, but if less data is available, it raises " +"the exception." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1371 +msgid "" +"You can still retrieve the downloaded data in this case, it is stored in " +"the :attr:`content` attribute of the exception instance." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1374 +msgid "" +"If no *Content-Length* header was supplied, urlretrieve can not check the " +"size of the data it has downloaded, and just returns it. In this case you " +"just have to assume that the download was successful." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1380 +msgid "" +"Cleans up temporary files that may have been left behind by previous calls " +"to :func:`urlretrieve`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1387 +msgid "" +"Base class for opening and reading URLs. Unless you need to support opening " +"objects using schemes other than :file:`http:`, :file:`ftp:`, or :file:`file:" +"`, you probably want to use :class:`FancyURLopener`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1391 +msgid "" +"By default, the :class:`URLopener` class sends a :mailheader:`User-Agent` " +"header of ``urllib/VVV``, where *VVV* is the :mod:`urllib` version number. " +"Applications can define their own :mailheader:`User-Agent` header by " +"subclassing :class:`URLopener` or :class:`FancyURLopener` and setting the " +"class attribute :attr:`version` to an appropriate string value in the " +"subclass definition." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1397 +msgid "" +"The optional *proxies* parameter should be a dictionary mapping scheme names " +"to proxy URLs, where an empty dictionary turns proxies off completely. Its " +"default value is ``None``, in which case environmental proxy settings will " +"be used if present, as discussed in the definition of :func:`urlopen`, above." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1402 +msgid "" +"Additional keyword parameters, collected in *x509*, may be used for " +"authentication of the client when using the :file:`https:` scheme. The " +"keywords *key_file* and *cert_file* are supported to provide an SSL key and " +"certificate; both are needed to support client authentication." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1407 +msgid "" +":class:`URLopener` objects will raise an :exc:`OSError` exception if the " +"server returns an error code." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1412 +msgid "" +"Open *fullurl* using the appropriate protocol. This method sets up cache " +"and proxy information, then calls the appropriate open method with its input " +"arguments. If the scheme is not recognized, :meth:`open_unknown` is called. " +"The *data* argument has the same meaning as the *data* argument of :func:" +"`urlopen`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1421 +msgid "Overridable interface to open unknown URL types." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1426 +msgid "" +"Retrieves the contents of *url* and places it in *filename*. The return " +"value is a tuple consisting of a local filename and either an :class:`email." +"message.Message` object containing the response headers (for remote URLs) or " +"``None`` (for local URLs). The caller must then open and read the contents " +"of *filename*. If *filename* is not given and the URL refers to a local " +"file, the input filename is returned. If the URL is non-local and " +"*filename* is not given, the filename is the output of :func:`tempfile." +"mktemp` with a suffix that matches the suffix of the last path component of " +"the input URL. If *reporthook* is given, it must be a function accepting " +"three numeric parameters: A chunk number, the maximum size chunks are read " +"in and the total size of the download (-1 if unknown). It will be called " +"once at the start and after each chunk of data is read from the network. " +"*reporthook* is ignored for local URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1439 +msgid "" +"If the *url* uses the :file:`http:` scheme identifier, the optional *data* " +"argument may be given to specify a ``POST`` request (normally the request " +"type is ``GET``). The *data* argument must in standard :mimetype:" +"`application/x-www-form-urlencoded` format; see the :func:`urllib.parse." +"urlencode` function." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1448 +msgid "" +"Variable that specifies the user agent of the opener object. To get :mod:" +"`urllib` to tell servers that it is a particular user agent, set this in a " +"subclass as a class variable or in the constructor before calling the base " +"constructor." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1458 +msgid "" +":class:`FancyURLopener` subclasses :class:`URLopener` providing default " +"handling for the following HTTP response codes: 301, 302, 303, 307 and 401. " +"For the 30x response codes listed above, the :mailheader:`Location` header " +"is used to fetch the actual URL. For 401 response codes (authentication " +"required), basic HTTP authentication is performed. For the 30x response " +"codes, recursion is bounded by the value of the *maxtries* attribute, which " +"defaults to 10." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1465 +msgid "" +"For all other response codes, the method :meth:`http_error_default` is " +"called which you can override in subclasses to handle the error " +"appropriately." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1470 +msgid "" +"According to the letter of :rfc:`2616`, 301 and 302 responses to POST " +"requests must not be automatically redirected without confirmation by the " +"user. In reality, browsers do allow automatic redirection of these " +"responses, changing the POST to a GET, and :mod:`urllib` reproduces this " +"behaviour." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1475 +msgid "" +"The parameters to the constructor are the same as those for :class:" +"`URLopener`." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1479 +msgid "" +"When performing basic authentication, a :class:`FancyURLopener` instance " +"calls its :meth:`prompt_user_passwd` method. The default implementation " +"asks the users for the required information on the controlling terminal. A " +"subclass may override this method to support more appropriate behavior if " +"needed." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1484 +msgid "" +"The :class:`FancyURLopener` class offers one additional method that should " +"be overloaded to provide the appropriate behavior:" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1489 +msgid "" +"Return information needed to authenticate the user at the given host in the " +"specified security realm. The return value should be a tuple, ``(user, " +"password)``, which can be used for basic authentication." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1493 +msgid "" +"The implementation prompts for this information on the terminal; an " +"application should override this method to use an appropriate interaction " +"model in the local environment." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1499 +msgid ":mod:`urllib.request` Restrictions" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1505 +msgid "" +"Currently, only the following protocols are supported: HTTP (versions 0.9 " +"and 1.0), FTP, local files, and data URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1508 +msgid "Added support for data URLs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1510 +msgid "" +"The caching feature of :func:`urlretrieve` has been disabled until someone " +"finds the time to hack proper processing of Expiration time headers." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1513 +msgid "" +"There should be a function to query whether a particular URL is in the cache." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1515 +msgid "" +"For backward compatibility, if a URL appears to point to a local file but " +"the file can't be opened, the URL is re-interpreted using the FTP protocol. " +"This can sometimes cause confusing error messages." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1519 +msgid "" +"The :func:`urlopen` and :func:`urlretrieve` functions can cause arbitrarily " +"long delays while waiting for a network connection to be set up. This means " +"that it is difficult to build an interactive Web client using these " +"functions without using threads." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1528 +msgid "" +"The data returned by :func:`urlopen` or :func:`urlretrieve` is the raw data " +"returned by the server. This may be binary data (such as an image), plain " +"text or (for example) HTML. The HTTP protocol provides type information in " +"the reply header, which can be inspected by looking at the :mailheader:" +"`Content-Type` header. If the returned data is HTML, you can use the " +"module :mod:`html.parser` to parse it." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1537 +msgid "" +"The code handling the FTP protocol cannot differentiate between a file and a " +"directory. This can lead to unexpected behavior when attempting to read a " +"URL that points to a file that is not accessible. If the URL ends in a ``/" +"``, it is assumed to refer to a directory and will be handled accordingly. " +"But if an attempt to read a file leads to a 550 error (meaning the URL " +"cannot be found or is not accessible, often for permission reasons), then " +"the path is treated as a directory in order to handle the case when a " +"directory is specified by a URL but the trailing ``/`` has been left off. " +"This can cause misleading results when you try to fetch a file whose read " +"permissions make it inaccessible; the FTP code will try to read it, fail " +"with a 550 error, and then perform a directory listing for the unreadable " +"file. If fine-grained control is needed, consider using the :mod:`ftplib` " +"module, subclassing :class:`FancyURLopener`, or changing *_urlopener* to " +"meet your needs." +msgstr "" + +#: ../Doc/library/urllib.request.rst:1554 +msgid ":mod:`urllib.response` --- Response classes used by urllib" +msgstr "" + +#: ../Doc/library/urllib.request.rst:1559 +msgid "" +"The :mod:`urllib.response` module defines functions and classes which define " +"a minimal file like interface, including ``read()`` and ``readline()``. The " +"typical response object is an addinfourl instance, which defines an " +"``info()`` method and that returns headers and a ``geturl()`` method that " +"returns the url. Functions defined by this module are used internally by " +"the :mod:`urllib.request` module." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:2 +msgid ":mod:`urllib.robotparser` --- Parser for robots.txt" +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:10 +msgid "**Source code:** :source:`Lib/urllib/robotparser.py`" +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:20 +msgid "" +"This module provides a single class, :class:`RobotFileParser`, which answers " +"questions about whether or not a particular user agent can fetch a URL on " +"the Web site that published the :file:`robots.txt` file. For more details " +"on the structure of :file:`robots.txt` files, see http://www.robotstxt.org/" +"orig.html." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:28 +msgid "" +"This class provides methods to read, parse and answer questions about the :" +"file:`robots.txt` file at *url*." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:33 +msgid "Sets the URL referring to a :file:`robots.txt` file." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:37 +msgid "Reads the :file:`robots.txt` URL and feeds it to the parser." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:41 +msgid "Parses the lines argument." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:45 +msgid "" +"Returns ``True`` if the *useragent* is allowed to fetch the *url* according " +"to the rules contained in the parsed :file:`robots.txt` file." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:51 +msgid "" +"Returns the time the ``robots.txt`` file was last fetched. This is useful " +"for long-running web spiders that need to check for new ``robots.txt`` files " +"periodically." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:57 +msgid "" +"Sets the time the ``robots.txt`` file was last fetched to the current time." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:62 +msgid "" +"Returns the value of the ``Crawl-delay`` parameter from ``robots.txt`` for " +"the *useragent* in question. If there is no such parameter or it doesn't " +"apply to the *useragent* specified or the ``robots.txt`` entry for this " +"parameter has invalid syntax, return ``None``." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:71 +msgid "" +"Returns the contents of the ``Request-rate`` parameter from ``robots.txt`` " +"in the form of a :func:`~collections.namedtuple` ``(requests, seconds)``. " +"If there is no such parameter or it doesn't apply to the *useragent* " +"specified or the ``robots.txt`` entry for this parameter has invalid syntax, " +"return ``None``." +msgstr "" + +#: ../Doc/library/urllib.robotparser.rst:80 +msgid "" +"The following example demonstrates basic use of the :class:`RobotFileParser` " +"class::" +msgstr "" + +#: ../Doc/library/uu.rst:2 +msgid ":mod:`uu` --- Encode and decode uuencode files" +msgstr "" + +#: ../Doc/library/uu.rst:9 +msgid "**Source code:** :source:`Lib/uu.py`" +msgstr "" + +#: ../Doc/library/uu.rst:13 +msgid "" +"This module encodes and decodes files in uuencode format, allowing arbitrary " +"binary data to be transferred over ASCII-only connections. Wherever a file " +"argument is expected, the methods accept a file-like object. For backwards " +"compatibility, a string containing a pathname is also accepted, and the " +"corresponding file will be opened for reading and writing; the pathname " +"``'-'`` is understood to mean the standard input or output. However, this " +"interface is deprecated; it's better for the caller to open the file itself, " +"and be sure that, when required, the mode is ``'rb'`` or ``'wb'`` on Windows." +msgstr "" + +#: ../Doc/library/uu.rst:26 +msgid "" +"This code was contributed by Lance Ellinghouse, and modified by Jack Jansen." +msgstr "" + +#: ../Doc/library/uu.rst:28 +msgid "The :mod:`uu` module defines the following functions:" +msgstr "" + +#: ../Doc/library/uu.rst:33 +msgid "" +"Uuencode file *in_file* into file *out_file*. The uuencoded file will have " +"the header specifying *name* and *mode* as the defaults for the results of " +"decoding the file. The default defaults are taken from *in_file*, or ``'-'`` " +"and ``0o666`` respectively." +msgstr "" + +#: ../Doc/library/uu.rst:41 +msgid "" +"This call decodes uuencoded file *in_file* placing the result on file " +"*out_file*. If *out_file* is a pathname, *mode* is used to set the " +"permission bits if the file must be created. Defaults for *out_file* and " +"*mode* are taken from the uuencode header. However, if the file specified " +"in the header already exists, a :exc:`uu.Error` is raised." +msgstr "" + +#: ../Doc/library/uu.rst:47 +msgid "" +":func:`decode` may print a warning to standard error if the input was " +"produced by an incorrect uuencoder and Python could recover from that " +"error. Setting *quiet* to a true value silences this warning." +msgstr "" + +#: ../Doc/library/uu.rst:54 +msgid "" +"Subclass of :exc:`Exception`, this can be raised by :func:`uu.decode` under " +"various situations, such as described above, but also including a badly " +"formatted header, or truncated input file." +msgstr "" + +#: ../Doc/library/uuid.rst:2 +msgid ":mod:`uuid` --- UUID objects according to RFC 4122" +msgstr "" + +#: ../Doc/library/uuid.rst:9 +msgid "**Source code:** :source:`Lib/uuid.py`" +msgstr "" + +#: ../Doc/library/uuid.rst:13 +msgid "" +"This module provides immutable :class:`UUID` objects (the :class:`UUID` " +"class) and the functions :func:`uuid1`, :func:`uuid3`, :func:`uuid4`, :func:" +"`uuid5` for generating version 1, 3, 4, and 5 UUIDs as specified in :rfc:" +"`4122`." +msgstr "" + +#: ../Doc/library/uuid.rst:17 +msgid "" +"If all you want is a unique ID, you should probably call :func:`uuid1` or :" +"func:`uuid4`. Note that :func:`uuid1` may compromise privacy since it " +"creates a UUID containing the computer's network address. :func:`uuid4` " +"creates a random UUID." +msgstr "" + +#: ../Doc/library/uuid.rst:25 +msgid "" +"Create a UUID from either a string of 32 hexadecimal digits, a string of 16 " +"bytes as the *bytes* argument, a string of 16 bytes in little-endian order " +"as the *bytes_le* argument, a tuple of six integers (32-bit *time_low*, 16-" +"bit *time_mid*, 16-bit *time_hi_version*, 8-bit *clock_seq_hi_variant*, 8-" +"bit *clock_seq_low*, 48-bit *node*) as the *fields* argument, or a single " +"128-bit integer as the *int* argument. When a string of hex digits is " +"given, curly braces, hyphens, and a URN prefix are all optional. For " +"example, these expressions all yield the same UUID::" +msgstr "" + +#: ../Doc/library/uuid.rst:43 +msgid "" +"Exactly one of *hex*, *bytes*, *bytes_le*, *fields*, or *int* must be given. " +"The *version* argument is optional; if given, the resulting UUID will have " +"its variant and version number set according to RFC 4122, overriding bits in " +"the given *hex*, *bytes*, *bytes_le*, *fields*, or *int*." +msgstr "" + +#: ../Doc/library/uuid.rst:49 +msgid ":class:`UUID` instances have these read-only attributes:" +msgstr "" + +#: ../Doc/library/uuid.rst:53 +msgid "" +"The UUID as a 16-byte string (containing the six integer fields in big-" +"endian byte order)." +msgstr "" + +#: ../Doc/library/uuid.rst:59 +msgid "" +"The UUID as a 16-byte string (with *time_low*, *time_mid*, and " +"*time_hi_version* in little-endian byte order)." +msgstr "" + +#: ../Doc/library/uuid.rst:65 +msgid "" +"A tuple of the six integer fields of the UUID, which are also available as " +"six individual attributes and two derived attributes:" +msgstr "" + +#: ../Doc/library/uuid.rst:71 +msgid ":attr:`time_low`" +msgstr "" + +#: ../Doc/library/uuid.rst:71 +msgid "the first 32 bits of the UUID" +msgstr "" + +#: ../Doc/library/uuid.rst:73 +msgid ":attr:`time_mid`" +msgstr "" + +#: ../Doc/library/uuid.rst:73 ../Doc/library/uuid.rst:75 +msgid "the next 16 bits of the UUID" +msgstr "" + +#: ../Doc/library/uuid.rst:75 +msgid ":attr:`time_hi_version`" +msgstr "" + +#: ../Doc/library/uuid.rst:77 +msgid ":attr:`clock_seq_hi_variant`" +msgstr "" + +#: ../Doc/library/uuid.rst:77 ../Doc/library/uuid.rst:79 +msgid "the next 8 bits of the UUID" +msgstr "" + +#: ../Doc/library/uuid.rst:79 +msgid ":attr:`clock_seq_low`" +msgstr "" + +#: ../Doc/library/uuid.rst:81 +msgid ":attr:`node`" +msgstr "" + +#: ../Doc/library/uuid.rst:81 +msgid "the last 48 bits of the UUID" +msgstr "" + +#: ../Doc/library/uuid.rst:83 +msgid ":attr:`time`" +msgstr "" + +#: ../Doc/library/uuid.rst:83 +msgid "the 60-bit timestamp" +msgstr "" + +#: ../Doc/library/uuid.rst:85 +msgid ":attr:`clock_seq`" +msgstr "" + +#: ../Doc/library/uuid.rst:85 +msgid "the 14-bit sequence number" +msgstr "" + +#: ../Doc/library/uuid.rst:91 +msgid "The UUID as a 32-character hexadecimal string." +msgstr "" + +#: ../Doc/library/uuid.rst:96 +msgid "The UUID as a 128-bit integer." +msgstr "" + +#: ../Doc/library/uuid.rst:101 +msgid "The UUID as a URN as specified in RFC 4122." +msgstr "" + +#: ../Doc/library/uuid.rst:106 +msgid "" +"The UUID variant, which determines the internal layout of the UUID. This " +"will be one of the integer constants :const:`RESERVED_NCS`, :const:" +"`RFC_4122`, :const:`RESERVED_MICROSOFT`, or :const:`RESERVED_FUTURE`." +msgstr "" + +#: ../Doc/library/uuid.rst:113 +msgid "" +"The UUID version number (1 through 5, meaningful only when the variant is :" +"const:`RFC_4122`)." +msgstr "" + +#: ../Doc/library/uuid.rst:116 +msgid "The :mod:`uuid` module defines the following functions:" +msgstr "" + +#: ../Doc/library/uuid.rst:121 +msgid "" +"Get the hardware address as a 48-bit positive integer. The first time this " +"runs, it may launch a separate program, which could be quite slow. If all " +"attempts to obtain the hardware address fail, we choose a random 48-bit " +"number with its eighth bit set to 1 as recommended in RFC 4122. \"Hardware " +"address\" means the MAC address of a network interface, and on a machine " +"with multiple network interfaces the MAC address of any one of them may be " +"returned." +msgstr "" + +#: ../Doc/library/uuid.rst:133 +msgid "" +"Generate a UUID from a host ID, sequence number, and the current time. If " +"*node* is not given, :func:`getnode` is used to obtain the hardware address. " +"If *clock_seq* is given, it is used as the sequence number; otherwise a " +"random 14-bit sequence number is chosen." +msgstr "" + +#: ../Doc/library/uuid.rst:143 +msgid "" +"Generate a UUID based on the MD5 hash of a namespace identifier (which is a " +"UUID) and a name (which is a string)." +msgstr "" + +#: ../Doc/library/uuid.rst:151 +msgid "Generate a random UUID." +msgstr "" + +#: ../Doc/library/uuid.rst:158 +msgid "" +"Generate a UUID based on the SHA-1 hash of a namespace identifier (which is " +"a UUID) and a name (which is a string)." +msgstr "" + +#: ../Doc/library/uuid.rst:163 +msgid "" +"The :mod:`uuid` module defines the following namespace identifiers for use " +"with :func:`uuid3` or :func:`uuid5`." +msgstr "" + +#: ../Doc/library/uuid.rst:169 +msgid "" +"When this namespace is specified, the *name* string is a fully-qualified " +"domain name." +msgstr "" + +#: ../Doc/library/uuid.rst:175 +msgid "When this namespace is specified, the *name* string is a URL." +msgstr "" + +#: ../Doc/library/uuid.rst:180 +msgid "When this namespace is specified, the *name* string is an ISO OID." +msgstr "" + +#: ../Doc/library/uuid.rst:185 +msgid "" +"When this namespace is specified, the *name* string is an X.500 DN in DER or " +"a text output format." +msgstr "" + +#: ../Doc/library/uuid.rst:188 +msgid "" +"The :mod:`uuid` module defines the following constants for the possible " +"values of the :attr:`variant` attribute:" +msgstr "" + +#: ../Doc/library/uuid.rst:194 +msgid "Reserved for NCS compatibility." +msgstr "" + +#: ../Doc/library/uuid.rst:199 +msgid "Specifies the UUID layout given in :rfc:`4122`." +msgstr "" + +#: ../Doc/library/uuid.rst:204 +msgid "Reserved for Microsoft compatibility." +msgstr "" + +#: ../Doc/library/uuid.rst:209 +msgid "Reserved for future definition." +msgstr "" + +#: ../Doc/library/uuid.rst:215 +msgid ":rfc:`4122` - A Universally Unique IDentifier (UUID) URN Namespace" +msgstr "" + +#: ../Doc/library/uuid.rst:215 +msgid "" +"This specification defines a Uniform Resource Name namespace for UUIDs, the " +"internal format of UUIDs, and methods of generating UUIDs." +msgstr "" + +#: ../Doc/library/uuid.rst:224 +msgid "Here are some examples of typical usage of the :mod:`uuid` module::" +msgstr "" + +#: ../Doc/library/venv.rst:2 +msgid ":mod:`venv` --- Creation of virtual environments" +msgstr "" + +#: ../Doc/library/venv.rst:12 +msgid "**Source code:** :source:`Lib/venv/`" +msgstr "" + +#: ../Doc/library/venv.rst:18 +msgid "" +"The :mod:`venv` module provides support for creating lightweight \"virtual " +"environments\" with their own site directories, optionally isolated from " +"system site directories. Each virtual environment has its own Python binary " +"(allowing creation of environments with various Python versions) and can " +"have its own independent set of installed Python packages in its site " +"directories." +msgstr "" + +#: ../Doc/library/venv.rst:24 +msgid "See :pep:`405` for more information about Python virtual environments." +msgstr "" + +#: ../Doc/library/venv.rst:27 +msgid "Creating virtual environments" +msgstr "" + +#: ../Doc/using/venv-create.inc:1 +msgid "" +"Creation of :ref:`virtual environments ` is done by executing the " +"command ``venv``::" +msgstr "" + +#: ../Doc/using/venv-create.inc:6 +msgid "" +"Running this command creates the target directory (creating any parent " +"directories that don't exist already) and places a ``pyvenv.cfg`` file in it " +"with a ``home`` key pointing to the Python installation from which the " +"command was run. It also creates a ``bin`` (or ``Scripts`` on Windows) " +"subdirectory containing a copy of the ``python`` binary (or binaries, in the " +"case of Windows). It also creates an (initially empty) ``lib/pythonX.Y/site-" +"packages`` subdirectory (on Windows, this is ``Lib\\site-packages``)." +msgstr "" + +#: ../Doc/using/venv-create.inc:14 +msgid "" +"``pyvenv`` was the recommended tool for creating virtual environments for " +"Python 3.3 and 3.4, and is `deprecated in Python 3.6 `_." +msgstr "" + +#: ../Doc/using/venv-create.inc:19 +msgid "" +"The use of ``venv`` is now recommended for creating virtual environments." +msgstr "" + +#: ../Doc/using/venv-create.inc:24 +msgid "" +"`Python Packaging User Guide: Creating and using virtual environments " +"`__" +msgstr "" + +#: ../Doc/using/venv-create.inc:29 +msgid "On Windows, invoke the ``venv`` command as follows::" +msgstr "" + +#: ../Doc/using/venv-create.inc:33 +msgid "" +"Alternatively, if you configured the ``PATH`` and ``PATHEXT`` variables for " +"your :ref:`Python installation `::" +msgstr "" + +#: ../Doc/using/venv-create.inc:38 +msgid "The command, if run with ``-h``, will show the available options::" +msgstr "" + +#: ../Doc/using/venv-create.inc:68 +msgid "" +"Installs pip by default, added the ``--without-pip`` and ``--copies`` " +"options" +msgstr "" + +#: ../Doc/using/venv-create.inc:72 +msgid "" +"In earlier versions, if the target directory already existed, an error was " +"raised, unless the ``--clear`` or ``--upgrade`` option was provided. Now, if " +"an existing directory is specified, its contents are removed and the " +"directory is processed as if it had been newly created." +msgstr "" + +#: ../Doc/using/venv-create.inc:78 +msgid "" +"The created ``pyvenv.cfg`` file also includes the ``include-system-site-" +"packages`` key, set to ``true`` if ``venv`` is run with the ``--system-site-" +"packages`` option, ``false`` otherwise." +msgstr "" + +#: ../Doc/using/venv-create.inc:82 +msgid "" +"Unless the ``--without-pip`` option is given, :mod:`ensurepip` will be " +"invoked to bootstrap ``pip`` into the virtual environment." +msgstr "" + +#: ../Doc/using/venv-create.inc:85 +msgid "" +"Multiple paths can be given to ``venv``, in which case an identical virtual " +"environment will be created, according to the given options, at each " +"provided path." +msgstr "" + +#: ../Doc/using/venv-create.inc:89 +msgid "" +"Once a virtual environment has been created, it can be \"activated\" using a " +"script in the virtual environment's binary directory. The invocation of the " +"script is platform-specific:" +msgstr "" + +#: ../Doc/using/venv-create.inc:94 +msgid "Platform" +msgstr "" + +#: ../Doc/using/venv-create.inc:94 +msgid "Shell" +msgstr "" + +#: ../Doc/using/venv-create.inc:94 +msgid "Command to activate virtual environment" +msgstr "" + +#: ../Doc/using/venv-create.inc:96 +msgid "Posix" +msgstr "" + +#: ../Doc/using/venv-create.inc:96 +msgid "bash/zsh" +msgstr "" + +#: ../Doc/using/venv-create.inc:96 +msgid "$ source /bin/activate" +msgstr "" + +#: ../Doc/using/venv-create.inc:98 +msgid "fish" +msgstr "" + +#: ../Doc/using/venv-create.inc:98 +msgid "$ . /bin/activate.fish" +msgstr "" + +#: ../Doc/using/venv-create.inc:100 +msgid "csh/tcsh" +msgstr "" + +#: ../Doc/using/venv-create.inc:100 +msgid "$ source /bin/activate.csh" +msgstr "" + +#: ../Doc/using/venv-create.inc:102 +msgid "cmd.exe" +msgstr "" + +#: ../Doc/using/venv-create.inc:102 +msgid "C:\\\\> \\\\Scripts\\\\activate.bat" +msgstr "" + +#: ../Doc/using/venv-create.inc:104 +msgid "PowerShell" +msgstr "" + +#: ../Doc/using/venv-create.inc:104 +msgid "PS C:\\\\> \\\\Scripts\\\\Activate.ps1" +msgstr "" + +#: ../Doc/using/venv-create.inc:107 +msgid "" +"You don't specifically *need* to activate an environment; activation just " +"prepends the virtual environment's binary directory to your path, so that " +"\"python\" invokes the virtual environment's Python interpreter and you can " +"run installed scripts without having to use their full path. However, all " +"scripts installed in a virtual environment should be runnable without " +"activating it, and run with the virtual environment's Python automatically." +msgstr "" + +#: ../Doc/using/venv-create.inc:114 +msgid "" +"You can deactivate a virtual environment by typing \"deactivate\" in your " +"shell. The exact mechanism is platform-specific: for example, the Bash " +"activation script defines a \"deactivate\" function, whereas on Windows " +"there are separate scripts called ``deactivate.bat`` and ``Deactivate.ps1`` " +"which are installed when the virtual environment is created." +msgstr "" + +#: ../Doc/using/venv-create.inc:120 +msgid "``fish`` and ``csh`` activation scripts." +msgstr "" + +#: ../Doc/library/venv.rst:34 +msgid "" +"A virtual environment is a Python environment such that the Python " +"interpreter, libraries and scripts installed into it are isolated from those " +"installed in other virtual environments, and (by default) any libraries " +"installed in a \"system\" Python, i.e., one which is installed as part of " +"your operating system." +msgstr "" + +#: ../Doc/library/venv.rst:40 +msgid "" +"A virtual environment is a directory tree which contains Python executable " +"files and other files which indicate that it is a virtual environment." +msgstr "" + +#: ../Doc/library/venv.rst:43 +msgid "" +"Common installation tools such as ``Setuptools`` and ``pip`` work as " +"expected with virtual environments. In other words, when a virtual " +"environment is active, they install Python packages into the virtual " +"environment without needing to be told to do so explicitly." +msgstr "" + +#: ../Doc/library/venv.rst:48 +msgid "" +"When a virtual environment is active (i.e., the virtual environment's Python " +"interpreter is running), the attributes :attr:`sys.prefix` and :attr:`sys." +"exec_prefix` point to the base directory of the virtual environment, " +"whereas :attr:`sys.base_prefix` and :attr:`sys.base_exec_prefix` point to " +"the non-virtual environment Python installation which was used to create the " +"virtual environment. If a virtual environment is not active, then :attr:`sys." +"prefix` is the same as :attr:`sys.base_prefix` and :attr:`sys.exec_prefix` " +"is the same as :attr:`sys.base_exec_prefix` (they all point to a non-virtual " +"environment Python installation)." +msgstr "" + +#: ../Doc/library/venv.rst:59 +msgid "" +"When a virtual environment is active, any options that change the " +"installation path will be ignored from all distutils configuration files to " +"prevent projects being inadvertently installed outside of the virtual " +"environment." +msgstr "" + +#: ../Doc/library/venv.rst:64 +msgid "" +"When working in a command shell, users can make a virtual environment active " +"by running an ``activate`` script in the virtual environment's executables " +"directory (the precise filename is shell-dependent), which prepends the " +"virtual environment's directory for executables to the ``PATH`` environment " +"variable for the running shell. There should be no need in other " +"circumstances to activate a virtual environment—scripts installed into " +"virtual environments have a \"shebang\" line which points to the virtual " +"environment's Python interpreter. This means that the script will run with " +"that interpreter regardless of the value of ``PATH``. On Windows, \"shebang" +"\" line processing is supported if you have the Python Launcher for Windows " +"installed (this was added to Python in 3.3 - see :pep:`397` for more " +"details). Thus, double-clicking an installed script in a Windows Explorer " +"window should run the script with the correct interpreter without there " +"needing to be any reference to its virtual environment in ``PATH``." +msgstr "" + +#: ../Doc/library/venv.rst:87 +msgid "" +"The high-level method described above makes use of a simple API which " +"provides mechanisms for third-party virtual environment creators to " +"customize environment creation according to their needs, the :class:" +"`EnvBuilder` class." +msgstr "" + +#: ../Doc/library/venv.rst:95 +msgid "" +"The :class:`EnvBuilder` class accepts the following keyword arguments on " +"instantiation:" +msgstr "" + +#: ../Doc/library/venv.rst:98 +msgid "" +"``system_site_packages`` -- a Boolean value indicating that the system " +"Python site-packages should be available to the environment (defaults to " +"``False``)." +msgstr "" + +#: ../Doc/library/venv.rst:101 +msgid "" +"``clear`` -- a Boolean value which, if true, will delete the contents of any " +"existing target directory, before creating the environment." +msgstr "" + +#: ../Doc/library/venv.rst:104 +msgid "" +"``symlinks`` -- a Boolean value indicating whether to attempt to symlink the " +"Python binary (and any necessary DLLs or other binaries, e.g. ``pythonw." +"exe``), rather than copying. Defaults to ``True`` on Linux and Unix systems, " +"but ``False`` on Windows." +msgstr "" + +#: ../Doc/library/venv.rst:109 +msgid "" +"``upgrade`` -- a Boolean value which, if true, will upgrade an existing " +"environment with the running Python - for use when that Python has been " +"upgraded in-place (defaults to ``False``)." +msgstr "" + +#: ../Doc/library/venv.rst:113 +msgid "" +"``with_pip`` -- a Boolean value which, if true, ensures pip is installed in " +"the virtual environment. This uses :mod:`ensurepip` with the ``--default-" +"pip`` option." +msgstr "" + +#: ../Doc/library/venv.rst:117 +msgid "" +"``prompt`` -- a String to be used after virtual environment is activated " +"(defaults to ``None`` which means directory name of the environment would be " +"used)." +msgstr "" + +#: ../Doc/library/venv.rst:121 ../Doc/library/venv.rst:229 +msgid "Added the ``with_pip`` parameter" +msgstr "" + +#: ../Doc/library/venv.rst:124 +msgid "Added the ``prompt`` parameter" +msgstr "" + +#: ../Doc/library/venv.rst:128 +msgid "" +"Creators of third-party virtual environment tools will be free to use the " +"provided ``EnvBuilder`` class as a base class." +msgstr "" + +#: ../Doc/library/venv.rst:131 +msgid "The returned env-builder is an object which has a method, ``create``:" +msgstr "" + +#: ../Doc/library/venv.rst:135 +msgid "" +"This method takes as required argument the path (absolute or relative to the " +"current directory) of the target directory which is to contain the virtual " +"environment. The ``create`` method will either create the environment in " +"the specified directory, or raise an appropriate exception." +msgstr "" + +#: ../Doc/library/venv.rst:141 +msgid "" +"The ``create`` method of the ``EnvBuilder`` class illustrates the hooks " +"available for subclass customization::" +msgstr "" + +#: ../Doc/library/venv.rst:156 +msgid "" +"Each of the methods :meth:`ensure_directories`, :meth:" +"`create_configuration`, :meth:`setup_python`, :meth:`setup_scripts` and :" +"meth:`post_setup` can be overridden." +msgstr "" + +#: ../Doc/library/venv.rst:162 +msgid "" +"Creates the environment directory and all necessary directories, and returns " +"a context object. This is just a holder for attributes (such as paths), for " +"use by the other methods. The directories are allowed to exist already, as " +"long as either ``clear`` or ``upgrade`` were specified to allow operating on " +"an existing environment directory." +msgstr "" + +#: ../Doc/library/venv.rst:170 +msgid "Creates the ``pyvenv.cfg`` configuration file in the environment." +msgstr "" + +#: ../Doc/library/venv.rst:174 +msgid "" +"Creates a copy of the Python executable (and, under Windows, DLLs) in the " +"environment. On a POSIX system, if a specific executable ``python3.x`` was " +"used, symlinks to ``python`` and ``python3`` will be created pointing to " +"that executable, unless files with those names already exist." +msgstr "" + +#: ../Doc/library/venv.rst:182 +msgid "" +"Installs activation scripts appropriate to the platform into the virtual " +"environment." +msgstr "" + +#: ../Doc/library/venv.rst:187 +msgid "" +"A placeholder method which can be overridden in third party implementations " +"to pre-install packages in the virtual environment or perform other post-" +"creation steps." +msgstr "" + +#: ../Doc/library/venv.rst:191 +msgid "" +"In addition, :class:`EnvBuilder` provides this utility method that can be " +"called from :meth:`setup_scripts` or :meth:`post_setup` in subclasses to " +"assist in installing custom scripts into the virtual environment." +msgstr "" + +#: ../Doc/library/venv.rst:197 +msgid "" +"*path* is the path to a directory that should contain subdirectories \"common" +"\", \"posix\", \"nt\", each containing scripts destined for the bin " +"directory in the environment. The contents of \"common\" and the directory " +"corresponding to :data:`os.name` are copied after some text replacement of " +"placeholders:" +msgstr "" + +#: ../Doc/library/venv.rst:203 +msgid "" +"``__VENV_DIR__`` is replaced with the absolute path of the environment " +"directory." +msgstr "" + +#: ../Doc/library/venv.rst:206 +msgid "" +"``__VENV_NAME__`` is replaced with the environment name (final path segment " +"of environment directory)." +msgstr "" + +#: ../Doc/library/venv.rst:209 +msgid "" +"``__VENV_PROMPT__`` is replaced with the prompt (the environment name " +"surrounded by parentheses and with a following space)" +msgstr "" + +#: ../Doc/library/venv.rst:212 +msgid "" +"``__VENV_BIN_NAME__`` is replaced with the name of the bin directory (either " +"``bin`` or ``Scripts``)." +msgstr "" + +#: ../Doc/library/venv.rst:215 +msgid "" +"``__VENV_PYTHON__`` is replaced with the absolute path of the environment's " +"executable." +msgstr "" + +#: ../Doc/library/venv.rst:218 +msgid "" +"The directories are allowed to exist (for when an existing environment is " +"being upgraded)." +msgstr "" + +#: ../Doc/library/venv.rst:221 +msgid "There is also a module-level convenience function:" +msgstr "" + +#: ../Doc/library/venv.rst:226 +msgid "" +"Create an :class:`EnvBuilder` with the given keyword arguments, and call " +"its :meth:`~EnvBuilder.create` method with the *env_dir* argument." +msgstr "" + +#: ../Doc/library/venv.rst:233 +msgid "An example of extending ``EnvBuilder``" +msgstr "" + +#: ../Doc/library/venv.rst:235 +msgid "" +"The following script shows how to extend :class:`EnvBuilder` by implementing " +"a subclass which installs setuptools and pip into a created virtual " +"environment::" +msgstr "" + +#: ../Doc/library/venv.rst:454 +msgid "" +"This script is also available for download `online `_." +msgstr "" + +#: ../Doc/library/warnings.rst:2 +msgid ":mod:`warnings` --- Warning control" +msgstr "" + +#: ../Doc/library/warnings.rst:7 +msgid "**Source code:** :source:`Lib/warnings.py`" +msgstr "" + +#: ../Doc/library/warnings.rst:13 +msgid "" +"Warning messages are typically issued in situations where it is useful to " +"alert the user of some condition in a program, where that condition " +"(normally) doesn't warrant raising an exception and terminating the " +"program. For example, one might want to issue a warning when a program uses " +"an obsolete module." +msgstr "" + +#: ../Doc/library/warnings.rst:18 +msgid "" +"Python programmers issue warnings by calling the :func:`warn` function " +"defined in this module. (C programmers use :c:func:`PyErr_WarnEx`; see :ref:" +"`exceptionhandling` for details)." +msgstr "" + +#: ../Doc/library/warnings.rst:22 +msgid "" +"Warning messages are normally written to ``sys.stderr``, but their " +"disposition can be changed flexibly, from ignoring all warnings to turning " +"them into exceptions. The disposition of warnings can vary based on the " +"warning category (see below), the text of the warning message, and the " +"source location where it is issued. Repetitions of a particular warning for " +"the same source location are typically suppressed." +msgstr "" + +#: ../Doc/library/warnings.rst:29 +msgid "" +"There are two stages in warning control: first, each time a warning is " +"issued, a determination is made whether a message should be issued or not; " +"next, if a message is to be issued, it is formatted and printed using a user-" +"settable hook." +msgstr "" + +#: ../Doc/library/warnings.rst:33 +msgid "" +"The determination whether to issue a warning message is controlled by the " +"warning filter, which is a sequence of matching rules and actions. Rules can " +"be added to the filter by calling :func:`filterwarnings` and reset to its " +"default state by calling :func:`resetwarnings`." +msgstr "" + +#: ../Doc/library/warnings.rst:38 +msgid "" +"The printing of warning messages is done by calling :func:`showwarning`, " +"which may be overridden; the default implementation of this function formats " +"the message by calling :func:`formatwarning`, which is also available for " +"use by custom implementations." +msgstr "" + +#: ../Doc/library/warnings.rst:44 +msgid "" +":func:`logging.captureWarnings` allows you to handle all warnings with the " +"standard logging infrastructure." +msgstr "" + +#: ../Doc/library/warnings.rst:51 +msgid "Warning Categories" +msgstr "" + +#: ../Doc/library/warnings.rst:53 +msgid "" +"There are a number of built-in exceptions that represent warning categories. " +"This categorization is useful to be able to filter out groups of warnings. " +"The following warnings category classes are currently defined:" +msgstr "" + +#: ../Doc/library/warnings.rst:60 +msgid "Class" +msgstr "" + +#: ../Doc/library/warnings.rst:62 +msgid ":exc:`Warning`" +msgstr "" + +#: ../Doc/library/warnings.rst:62 +msgid "" +"This is the base class of all warning category classes. It is a subclass " +"of :exc:`Exception`." +msgstr "" + +#: ../Doc/library/warnings.rst:66 +msgid ":exc:`UserWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:66 +msgid "The default category for :func:`warn`." +msgstr "" + +#: ../Doc/library/warnings.rst:68 +msgid ":exc:`DeprecationWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:68 +msgid "" +"Base category for warnings about deprecated features (ignored by default)." +msgstr "" + +#: ../Doc/library/warnings.rst:71 +msgid ":exc:`SyntaxWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:71 +msgid "Base category for warnings about dubious syntactic features." +msgstr "" + +#: ../Doc/library/warnings.rst:74 +msgid ":exc:`RuntimeWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:74 +msgid "Base category for warnings about dubious runtime features." +msgstr "" + +#: ../Doc/library/warnings.rst:77 +msgid ":exc:`FutureWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:77 +msgid "" +"Base category for warnings about constructs that will change semantically in " +"the future." +msgstr "" + +#: ../Doc/library/warnings.rst:80 +msgid ":exc:`PendingDeprecationWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:80 +msgid "" +"Base category for warnings about features that will be deprecated in the " +"future (ignored by default)." +msgstr "" + +#: ../Doc/library/warnings.rst:84 +msgid ":exc:`ImportWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:84 +msgid "" +"Base category for warnings triggered during the process of importing a " +"module (ignored by default)." +msgstr "" + +#: ../Doc/library/warnings.rst:88 +msgid ":exc:`UnicodeWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:88 +msgid "Base category for warnings related to Unicode." +msgstr "" + +#: ../Doc/library/warnings.rst:91 +msgid ":exc:`BytesWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:91 +msgid "" +"Base category for warnings related to :class:`bytes` and :class:`bytearray`." +msgstr "" + +#: ../Doc/library/warnings.rst:94 +msgid ":exc:`ResourceWarning`" +msgstr "" + +#: ../Doc/library/warnings.rst:94 +msgid "Base category for warnings related to resource usage." +msgstr "" + +#: ../Doc/library/warnings.rst:99 +msgid "" +"While these are technically built-in exceptions, they are documented here, " +"because conceptually they belong to the warnings mechanism." +msgstr "" + +#: ../Doc/library/warnings.rst:102 +msgid "" +"User code can define additional warning categories by subclassing one of the " +"standard warning categories. A warning category must always be a subclass " +"of the :exc:`Warning` class." +msgstr "" + +#: ../Doc/library/warnings.rst:110 +msgid "The Warnings Filter" +msgstr "" + +#: ../Doc/library/warnings.rst:112 +msgid "" +"The warnings filter controls whether warnings are ignored, displayed, or " +"turned into errors (raising an exception)." +msgstr "" + +#: ../Doc/library/warnings.rst:115 +msgid "" +"Conceptually, the warnings filter maintains an ordered list of filter " +"specifications; any specific warning is matched against each filter " +"specification in the list in turn until a match is found; the match " +"determines the disposition of the match. Each entry is a tuple of the form " +"(*action*, *message*, *category*, *module*, *lineno*), where:" +msgstr "" + +#: ../Doc/library/warnings.rst:121 +msgid "*action* is one of the following strings:" +msgstr "" + +#: ../Doc/library/warnings.rst:124 +msgid "Disposition" +msgstr "" + +#: ../Doc/library/warnings.rst:126 +msgid "``\"error\"``" +msgstr "" + +#: ../Doc/library/warnings.rst:126 +msgid "turn matching warnings into exceptions" +msgstr "" + +#: ../Doc/library/warnings.rst:128 +msgid "``\"ignore\"``" +msgstr "" + +#: ../Doc/library/warnings.rst:128 +msgid "never print matching warnings" +msgstr "" + +#: ../Doc/library/warnings.rst:130 +msgid "``\"always\"``" +msgstr "" + +#: ../Doc/library/warnings.rst:130 +msgid "always print matching warnings" +msgstr "" + +#: ../Doc/library/warnings.rst:132 +msgid "``\"default\"``" +msgstr "" + +#: ../Doc/library/warnings.rst:132 +msgid "" +"print the first occurrence of matching warnings for each location where the " +"warning is issued" +msgstr "" + +#: ../Doc/library/warnings.rst:136 +msgid "``\"module\"``" +msgstr "" + +#: ../Doc/library/warnings.rst:136 +msgid "" +"print the first occurrence of matching warnings for each module where the " +"warning is issued" +msgstr "" + +#: ../Doc/library/warnings.rst:140 +msgid "``\"once\"``" +msgstr "" + +#: ../Doc/library/warnings.rst:140 +msgid "" +"print only the first occurrence of matching warnings, regardless of location" +msgstr "" + +#: ../Doc/library/warnings.rst:144 +msgid "" +"*message* is a string containing a regular expression that the start of the " +"warning message must match. The expression is compiled to always be case-" +"insensitive." +msgstr "" + +#: ../Doc/library/warnings.rst:148 +msgid "" +"*category* is a class (a subclass of :exc:`Warning`) of which the warning " +"category must be a subclass in order to match." +msgstr "" + +#: ../Doc/library/warnings.rst:151 +msgid "" +"*module* is a string containing a regular expression that the module name " +"must match. The expression is compiled to be case-sensitive." +msgstr "" + +#: ../Doc/library/warnings.rst:154 +msgid "" +"*lineno* is an integer that the line number where the warning occurred must " +"match, or ``0`` to match all line numbers." +msgstr "" + +#: ../Doc/library/warnings.rst:157 +msgid "" +"Since the :exc:`Warning` class is derived from the built-in :exc:`Exception` " +"class, to turn a warning into an error we simply raise ``category(message)``." +msgstr "" + +#: ../Doc/library/warnings.rst:160 +msgid "" +"The warnings filter is initialized by :option:`-W` options passed to the " +"Python interpreter command line. The interpreter saves the arguments for " +"all :option:`-W` options without interpretation in ``sys.warnoptions``; the :" +"mod:`warnings` module parses these when it is first imported (invalid " +"options are ignored, after printing a message to ``sys.stderr``)." +msgstr "" + +#: ../Doc/library/warnings.rst:168 +msgid "Default Warning Filters" +msgstr "" + +#: ../Doc/library/warnings.rst:170 +msgid "" +"By default, Python installs several warning filters, which can be overridden " +"by the command-line options passed to :option:`-W` and calls to :func:" +"`filterwarnings`." +msgstr "" + +#: ../Doc/library/warnings.rst:174 +msgid "" +":exc:`DeprecationWarning` and :exc:`PendingDeprecationWarning`, and :exc:" +"`ImportWarning` are ignored." +msgstr "" + +#: ../Doc/library/warnings.rst:177 +msgid "" +":exc:`BytesWarning` is ignored unless the :option:`-b` option is given once " +"or twice; in this case this warning is either printed (``-b``) or turned " +"into an exception (``-bb``)." +msgstr "" + +#: ../Doc/library/warnings.rst:181 +msgid "" +":exc:`ResourceWarning` is ignored unless Python was built in debug mode." +msgstr "" + +#: ../Doc/library/warnings.rst:183 +msgid "" +":exc:`DeprecationWarning` is now ignored by default in addition to :exc:" +"`PendingDeprecationWarning`." +msgstr "" + +#: ../Doc/library/warnings.rst:191 +msgid "Temporarily Suppressing Warnings" +msgstr "" + +#: ../Doc/library/warnings.rst:193 +msgid "" +"If you are using code that you know will raise a warning, such as a " +"deprecated function, but do not want to see the warning, then it is possible " +"to suppress the warning using the :class:`catch_warnings` context manager::" +msgstr "" + +#: ../Doc/library/warnings.rst:206 +msgid "" +"While within the context manager all warnings will simply be ignored. This " +"allows you to use known-deprecated code without having to see the warning " +"while not suppressing the warning for other code that might not be aware of " +"its use of deprecated code. Note: this can only be guaranteed in a single-" +"threaded application. If two or more threads use the :class:`catch_warnings` " +"context manager at the same time, the behavior is undefined." +msgstr "" + +#: ../Doc/library/warnings.rst:218 +msgid "Testing Warnings" +msgstr "" + +#: ../Doc/library/warnings.rst:220 +msgid "" +"To test warnings raised by code, use the :class:`catch_warnings` context " +"manager. With it you can temporarily mutate the warnings filter to " +"facilitate your testing. For instance, do the following to capture all " +"raised warnings to check::" +msgstr "" + +#: ../Doc/library/warnings.rst:240 +msgid "" +"One can also cause all warnings to be exceptions by using ``error`` instead " +"of ``always``. One thing to be aware of is that if a warning has already " +"been raised because of a ``once``/``default`` rule, then no matter what " +"filters are set the warning will not be seen again unless the warnings " +"registry related to the warning has been cleared." +msgstr "" + +#: ../Doc/library/warnings.rst:246 +msgid "" +"Once the context manager exits, the warnings filter is restored to its state " +"when the context was entered. This prevents tests from changing the warnings " +"filter in unexpected ways between tests and leading to indeterminate test " +"results. The :func:`showwarning` function in the module is also restored to " +"its original value. Note: this can only be guaranteed in a single-threaded " +"application. If two or more threads use the :class:`catch_warnings` context " +"manager at the same time, the behavior is undefined." +msgstr "" + +#: ../Doc/library/warnings.rst:254 +msgid "" +"When testing multiple operations that raise the same kind of warning, it is " +"important to test them in a manner that confirms each operation is raising a " +"new warning (e.g. set warnings to be raised as exceptions and check the " +"operations raise exceptions, check that the length of the warning list " +"continues to increase after each operation, or else delete the previous " +"entries from the warnings list before each new operation)." +msgstr "" + +#: ../Doc/library/warnings.rst:265 +msgid "Updating Code For New Versions of Python" +msgstr "" + +#: ../Doc/library/warnings.rst:267 +msgid "" +"Warnings that are only of interest to the developer are ignored by default. " +"As such you should make sure to test your code with typically ignored " +"warnings made visible. You can do this from the command-line by passing :" +"option:`-Wd <-W>` to the interpreter (this is shorthand for :option:`-W " +"default`). This enables default handling for all warnings, including those " +"that are ignored by default. To change what action is taken for encountered " +"warnings you simply change what argument is passed to :option:`-W`, e.g. :" +"option:`-W error`. See the :option:`-W` flag for more details on what is " +"possible." +msgstr "" + +#: ../Doc/library/warnings.rst:276 +msgid "To programmatically do the same as :option:`-Wd`, use::" +msgstr "" + +#: ../Doc/library/warnings.rst:280 +msgid "" +"Make sure to execute this code as soon as possible. This prevents the " +"registering of what warnings have been raised from unexpectedly influencing " +"how future warnings are treated." +msgstr "" + +#: ../Doc/library/warnings.rst:284 +msgid "" +"Having certain warnings ignored by default is done to prevent a user from " +"seeing warnings that are only of interest to the developer. As you do not " +"necessarily have control over what interpreter a user uses to run their " +"code, it is possible that a new version of Python will be released between " +"your release cycles. The new interpreter release could trigger new warnings " +"in your code that were not there in an older interpreter, e.g. :exc:" +"`DeprecationWarning` for a module that you are using. While you as a " +"developer want to be notified that your code is using a deprecated module, " +"to a user this information is essentially noise and provides no benefit to " +"them." +msgstr "" + +#: ../Doc/library/warnings.rst:294 +msgid "" +"The :mod:`unittest` module has been also updated to use the ``'default'`` " +"filter while running tests." +msgstr "" + +#: ../Doc/library/warnings.rst:301 +msgid "Available Functions" +msgstr "" + +#: ../Doc/library/warnings.rst:306 +msgid "" +"Issue a warning, or maybe ignore it or raise an exception. The *category* " +"argument, if given, must be a warning category class (see above); it " +"defaults to :exc:`UserWarning`. Alternatively *message* can be a :exc:" +"`Warning` instance, in which case *category* will be ignored and ``message." +"__class__`` will be used. In this case the message text will be " +"``str(message)``. This function raises an exception if the particular " +"warning issued is changed into an error by the warnings filter see above. " +"The *stacklevel* argument can be used by wrapper functions written in " +"Python, like this::" +msgstr "" + +#: ../Doc/library/warnings.rst:318 +msgid "" +"This makes the warning refer to :func:`deprecation`'s caller, rather than to " +"the source of :func:`deprecation` itself (since the latter would defeat the " +"purpose of the warning message)." +msgstr "" + +#: ../Doc/library/warnings.rst:322 ../Doc/library/warnings.rst:345 +msgid "" +"*source*, if supplied, is the destroyed object which emitted a :exc:" +"`ResourceWarning`." +msgstr "" + +#: ../Doc/library/warnings.rst:325 +msgid "Added *source* parameter." +msgstr "" + +#: ../Doc/library/warnings.rst:331 +msgid "" +"This is a low-level interface to the functionality of :func:`warn`, passing " +"in explicitly the message, category, filename and line number, and " +"optionally the module name and the registry (which should be the " +"``__warningregistry__`` dictionary of the module). The module name defaults " +"to the filename with ``.py`` stripped; if no registry is passed, the warning " +"is never suppressed. *message* must be a string and *category* a subclass " +"of :exc:`Warning` or *message* may be a :exc:`Warning` instance, in which " +"case *category* will be ignored." +msgstr "" + +#: ../Doc/library/warnings.rst:340 +msgid "" +"*module_globals*, if supplied, should be the global namespace in use by the " +"code for which the warning is issued. (This argument is used to support " +"displaying source for modules found in zipfiles or other non-filesystem " +"import sources)." +msgstr "" + +#: ../Doc/library/warnings.rst:348 +msgid "Add the *source* parameter." +msgstr "" + +#: ../Doc/library/warnings.rst:354 +msgid "" +"Write a warning to a file. The default implementation calls " +"``formatwarning(message, category, filename, lineno, line)`` and writes the " +"resulting string to *file*, which defaults to ``sys.stderr``. You may " +"replace this function with any callable by assigning to ``warnings." +"showwarning``. *line* is a line of source code to be included in the warning " +"message; if *line* is not supplied, :func:`showwarning` will try to read the " +"line specified by *filename* and *lineno*." +msgstr "" + +#: ../Doc/library/warnings.rst:365 +msgid "" +"Format a warning the standard way. This returns a string which may contain " +"embedded newlines and ends in a newline. *line* is a line of source code to " +"be included in the warning message; if *line* is not supplied, :func:" +"`formatwarning` will try to read the line specified by *filename* and " +"*lineno*." +msgstr "" + +#: ../Doc/library/warnings.rst:374 +msgid "" +"Insert an entry into the list of :ref:`warnings filter specifications " +"`. The entry is inserted at the front by default; if " +"*append* is true, it is inserted at the end. This checks the types of the " +"arguments, compiles the *message* and *module* regular expressions, and " +"inserts them as a tuple in the list of warnings filters. Entries closer to " +"the front of the list override entries later in the list, if both match a " +"particular warning. Omitted arguments default to a value that matches " +"everything." +msgstr "" + +#: ../Doc/library/warnings.rst:386 +msgid "" +"Insert a simple entry into the list of :ref:`warnings filter specifications " +"`. The meaning of the function parameters is as for :func:" +"`filterwarnings`, but regular expressions are not needed as the filter " +"inserted always matches any message in any module as long as the category " +"and line number match." +msgstr "" + +#: ../Doc/library/warnings.rst:395 +msgid "" +"Reset the warnings filter. This discards the effect of all previous calls " +"to :func:`filterwarnings`, including that of the :option:`-W` command line " +"options and calls to :func:`simplefilter`." +msgstr "" + +#: ../Doc/library/warnings.rst:401 +msgid "Available Context Managers" +msgstr "" + +#: ../Doc/library/warnings.rst:405 +msgid "" +"A context manager that copies and, upon exit, restores the warnings filter " +"and the :func:`showwarning` function. If the *record* argument is :const:" +"`False` (the default) the context manager returns :class:`None` on entry. If " +"*record* is :const:`True`, a list is returned that is progressively " +"populated with objects as seen by a custom :func:`showwarning` function " +"(which also suppresses output to ``sys.stdout``). Each object in the list " +"has attributes with the same names as the arguments to :func:`showwarning`." +msgstr "" + +#: ../Doc/library/warnings.rst:414 +msgid "" +"The *module* argument takes a module that will be used instead of the module " +"returned when you import :mod:`warnings` whose filter will be protected. " +"This argument exists primarily for testing the :mod:`warnings` module itself." +msgstr "" + +#: ../Doc/library/warnings.rst:421 +msgid "" +"The :class:`catch_warnings` manager works by replacing and then later " +"restoring the module's :func:`showwarning` function and internal list of " +"filter specifications. This means the context manager is modifying global " +"state and therefore is not thread-safe." +msgstr "" + +#: ../Doc/library/wave.rst:2 +msgid ":mod:`wave` --- Read and write WAV files" +msgstr "" + +#: ../Doc/library/wave.rst:10 +msgid "**Source code:** :source:`Lib/wave.py`" +msgstr "" + +#: ../Doc/library/wave.rst:14 +msgid "" +"The :mod:`wave` module provides a convenient interface to the WAV sound " +"format. It does not support compression/decompression, but it does support " +"mono/stereo." +msgstr "" + +#: ../Doc/library/wave.rst:17 +msgid "The :mod:`wave` module defines the following function and exception:" +msgstr "" + +#: ../Doc/library/wave.rst:22 +msgid "" +"If *file* is a string, open the file by that name, otherwise treat it as a " +"file-like object. *mode* can be:" +msgstr "" + +#: ../Doc/library/wave.rst:26 +msgid "``'rb'``" +msgstr "" + +#: ../Doc/library/wave.rst:29 +msgid "``'wb'``" +msgstr "" + +#: ../Doc/library/wave.rst:31 +msgid "Note that it does not allow read/write WAV files." +msgstr "" + +#: ../Doc/library/wave.rst:33 +msgid "" +"A *mode* of ``'rb'`` returns a :class:`Wave_read` object, while a *mode* of " +"``'wb'`` returns a :class:`Wave_write` object. If *mode* is omitted and a " +"file-like object is passed as *file*, ``file.mode`` is used as the default " +"value for *mode*." +msgstr "" + +#: ../Doc/library/wave.rst:38 +msgid "" +"If you pass in a file-like object, the wave object will not close it when " +"its :meth:`close` method is called; it is the caller's responsibility to " +"close the file object." +msgstr "" + +#: ../Doc/library/wave.rst:42 +msgid "" +"The :func:`.open` function may be used in a :keyword:`with` statement. When " +"the :keyword:`with` block completes, the :meth:`Wave_read.close() ` or :meth:`Wave_write.close() ` " +"method is called." +msgstr "" + +#: ../Doc/library/wave.rst:47 ../Doc/library/wave.rst:168 +msgid "Added support for unseekable files." +msgstr "" + +#: ../Doc/library/wave.rst:57 +msgid "" +"An error raised when something is impossible because it violates the WAV " +"specification or hits an implementation deficiency." +msgstr "" + +#: ../Doc/library/wave.rst:64 +msgid "Wave_read Objects" +msgstr "" + +#: ../Doc/library/wave.rst:66 +msgid "" +"Wave_read objects, as returned by :func:`.open`, have the following methods:" +msgstr "" + +#: ../Doc/library/wave.rst:71 +msgid "" +"Close the stream if it was opened by :mod:`wave`, and make the instance " +"unusable. This is called automatically on object collection." +msgstr "" + +#: ../Doc/library/wave.rst:77 +msgid "Returns number of audio channels (``1`` for mono, ``2`` for stereo)." +msgstr "" + +#: ../Doc/library/wave.rst:97 +msgid "Returns compression type (``'NONE'`` is the only supported type)." +msgstr "" + +#: ../Doc/library/wave.rst:102 +msgid "" +"Human-readable version of :meth:`getcomptype`. Usually ``'not compressed'`` " +"parallels ``'NONE'``." +msgstr "" + +#: ../Doc/library/wave.rst:115 +msgid "" +"Reads and returns at most *n* frames of audio, as a :class:`bytes` object." +msgstr "" + +#: ../Doc/library/wave.rst:122 +msgid "" +"The following two methods are defined for compatibility with the :mod:`aifc` " +"module, and don't do anything interesting." +msgstr "" + +#: ../Doc/library/wave.rst:141 +msgid "Set the file pointer to the specified position." +msgstr "" + +#: ../Doc/library/wave.rst:146 +msgid "Return current file pointer position." +msgstr "" + +#: ../Doc/library/wave.rst:152 +msgid "Wave_write Objects" +msgstr "" + +#: ../Doc/library/wave.rst:154 +msgid "" +"For seekable output streams, the ``wave`` header will automatically be " +"updated to reflect the number of frames actually written. For unseekable " +"streams, the *nframes* value must be accurate when the first frame data is " +"written. An accurate *nframes* value can be achieved either by calling :" +"meth:`~Wave_write.setnframes` or :meth:`~Wave_write.setparams` with the " +"number of frames that will be written before :meth:`~Wave_write.close` is " +"called and then using :meth:`~Wave_write.writeframesraw` to write the frame " +"data, or by calling :meth:`~Wave_write.writeframes` with all of the frame " +"data to be written. In the latter case :meth:`~Wave_write.writeframes` will " +"calculate the number of frames in the data and set *nframes* accordingly " +"before writing the frame data." +msgstr "" + +#: ../Doc/library/wave.rst:166 +msgid "" +"Wave_write objects, as returned by :func:`.open`, have the following methods:" +msgstr "" + +#: ../Doc/library/wave.rst:174 +msgid "" +"Make sure *nframes* is correct, and close the file if it was opened by :mod:" +"`wave`. This method is called upon object collection. It will raise an " +"exception if the output stream is not seekable and *nframes* does not match " +"the number of frames actually written." +msgstr "" + +#: ../Doc/library/wave.rst:187 +msgid "Set the sample width to *n* bytes." +msgstr "" + +#: ../Doc/library/wave.rst:192 +msgid "Set the frame rate to *n*." +msgstr "" + +#: ../Doc/library/wave.rst:194 +msgid "A non-integral input to this method is rounded to the nearest integer." +msgstr "" + +#: ../Doc/library/wave.rst:201 +msgid "" +"Set the number of frames to *n*. This will be changed later if the number " +"of frames actually written is different (this update attempt will raise an " +"error if the output stream is not seekable)." +msgstr "" + +#: ../Doc/library/wave.rst:208 +msgid "" +"Set the compression type and description. At the moment, only compression " +"type ``NONE`` is supported, meaning no compression." +msgstr "" + +#: ../Doc/library/wave.rst:214 +msgid "" +"The *tuple* should be ``(nchannels, sampwidth, framerate, nframes, comptype, " +"compname)``, with values valid for the :meth:`set\\*` methods. Sets all " +"parameters." +msgstr "" + +#: ../Doc/library/wave.rst:221 +msgid "" +"Return current position in the file, with the same disclaimer for the :meth:" +"`Wave_read.tell` and :meth:`Wave_read.setpos` methods." +msgstr "" + +#: ../Doc/library/wave.rst:235 +msgid "" +"Write audio frames and make sure *nframes* is correct. It will raise an " +"error if the output stream is not seekable and the total number of frames " +"that have been written after *data* has been written does not match the " +"previously set value for *nframes*." +msgstr "" + +#: ../Doc/library/wave.rst:244 +msgid "" +"Note that it is invalid to set any parameters after calling :meth:" +"`writeframes` or :meth:`writeframesraw`, and any attempt to do so will " +"raise :exc:`wave.Error`." +msgstr "" + +#: ../Doc/library/weakref.rst:2 +msgid ":mod:`weakref` --- Weak references" +msgstr "" + +#: ../Doc/library/weakref.rst:12 +msgid "**Source code:** :source:`Lib/weakref.py`" +msgstr "" + +#: ../Doc/library/weakref.rst:16 +msgid "" +"The :mod:`weakref` module allows the Python programmer to create :dfn:`weak " +"references` to objects." +msgstr "" + +#: ../Doc/library/weakref.rst:22 +msgid "" +"In the following, the term :dfn:`referent` means the object which is " +"referred to by a weak reference." +msgstr "" + +#: ../Doc/library/weakref.rst:25 +msgid "" +"A weak reference to an object is not enough to keep the object alive: when " +"the only remaining references to a referent are weak references, :term:" +"`garbage collection` is free to destroy the referent and reuse its memory " +"for something else. However, until the object is actually destroyed the " +"weak reference may return the object even if there are no strong references " +"to it." +msgstr "" + +#: ../Doc/library/weakref.rst:31 +msgid "" +"A primary use for weak references is to implement caches or mappings holding " +"large objects, where it's desired that a large object not be kept alive " +"solely because it appears in a cache or mapping." +msgstr "" + +#: ../Doc/library/weakref.rst:35 +msgid "" +"For example, if you have a number of large binary image objects, you may " +"wish to associate a name with each. If you used a Python dictionary to map " +"names to images, or images to names, the image objects would remain alive " +"just because they appeared as values or keys in the dictionaries. The :" +"class:`WeakKeyDictionary` and :class:`WeakValueDictionary` classes supplied " +"by the :mod:`weakref` module are an alternative, using weak references to " +"construct mappings that don't keep objects alive solely because they appear " +"in the mapping objects. If, for example, an image object is a value in a :" +"class:`WeakValueDictionary`, then when the last remaining references to that " +"image object are the weak references held by weak mappings, garbage " +"collection can reclaim the object, and its corresponding entries in weak " +"mappings are simply deleted." +msgstr "" + +#: ../Doc/library/weakref.rst:48 +msgid "" +":class:`WeakKeyDictionary` and :class:`WeakValueDictionary` use weak " +"references in their implementation, setting up callback functions on the " +"weak references that notify the weak dictionaries when a key or value has " +"been reclaimed by garbage collection. :class:`WeakSet` implements the :" +"class:`set` interface, but keeps weak references to its elements, just like " +"a :class:`WeakKeyDictionary` does." +msgstr "" + +#: ../Doc/library/weakref.rst:55 +msgid "" +":class:`finalize` provides a straight forward way to register a cleanup " +"function to be called when an object is garbage collected. This is simpler " +"to use than setting up a callback function on a raw weak reference, since " +"the module automatically ensures that the finalizer remains alive until the " +"object is collected." +msgstr "" + +#: ../Doc/library/weakref.rst:61 +msgid "" +"Most programs should find that using one of these weak container types or :" +"class:`finalize` is all they need -- it's not usually necessary to create " +"your own weak references directly. The low-level machinery is exposed by " +"the :mod:`weakref` module for the benefit of advanced uses." +msgstr "" + +#: ../Doc/library/weakref.rst:66 +msgid "" +"Not all objects can be weakly referenced; those objects which can include " +"class instances, functions written in Python (but not in C), instance " +"methods, sets, frozensets, some :term:`file objects `, :term:" +"`generator`\\s, type objects, sockets, arrays, deques, regular expression " +"pattern objects, and code objects." +msgstr "" + +#: ../Doc/library/weakref.rst:72 +msgid "Added support for thread.lock, threading.Lock, and code objects." +msgstr "" + +#: ../Doc/library/weakref.rst:75 +msgid "" +"Several built-in types such as :class:`list` and :class:`dict` do not " +"directly support weak references but can add support through subclassing::" +msgstr "" + +#: ../Doc/library/weakref.rst:83 +msgid "" +"Other built-in types such as :class:`tuple` and :class:`int` do not support " +"weak references even when subclassed (This is an implementation detail and " +"may be different across various Python implementations.)." +msgstr "" + +#: ../Doc/library/weakref.rst:87 +msgid "" +"Extension types can easily be made to support weak references; see :ref:" +"`weakref-support`." +msgstr "" + +#: ../Doc/library/weakref.rst:93 +msgid "" +"Return a weak reference to *object*. The original object can be retrieved " +"by calling the reference object if the referent is still alive; if the " +"referent is no longer alive, calling the reference object will cause :const:" +"`None` to be returned. If *callback* is provided and not :const:`None`, and " +"the returned weakref object is still alive, the callback will be called when " +"the object is about to be finalized; the weak reference object will be " +"passed as the only parameter to the callback; the referent will no longer be " +"available." +msgstr "" + +#: ../Doc/library/weakref.rst:101 +msgid "" +"It is allowable for many weak references to be constructed for the same " +"object. Callbacks registered for each weak reference will be called from the " +"most recently registered callback to the oldest registered callback." +msgstr "" + +#: ../Doc/library/weakref.rst:105 +msgid "" +"Exceptions raised by the callback will be noted on the standard error " +"output, but cannot be propagated; they are handled in exactly the same way " +"as exceptions raised from an object's :meth:`__del__` method." +msgstr "" + +#: ../Doc/library/weakref.rst:109 +msgid "" +"Weak references are :term:`hashable` if the *object* is hashable. They will " +"maintain their hash value even after the *object* was deleted. If :func:" +"`hash` is called the first time only after the *object* was deleted, the " +"call will raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/library/weakref.rst:114 +msgid "" +"Weak references support tests for equality, but not ordering. If the " +"referents are still alive, two references have the same equality " +"relationship as their referents (regardless of the *callback*). If either " +"referent has been deleted, the references are equal only if the reference " +"objects are the same object." +msgstr "" + +#: ../Doc/library/weakref.rst:119 +msgid "This is a subclassable type rather than a factory function." +msgstr "" + +#: ../Doc/library/weakref.rst:123 +msgid "" +"This read-only attribute returns the callback currently associated to the " +"weakref. If there is no callback or if the referent of the weakref is no " +"longer alive then this attribute will have value ``None``." +msgstr "" + +#: ../Doc/library/weakref.rst:127 +msgid "Added the :attr:`__callback__` attribute." +msgstr "" + +#: ../Doc/library/weakref.rst:133 +msgid "" +"Return a proxy to *object* which uses a weak reference. This supports use " +"of the proxy in most contexts instead of requiring the explicit " +"dereferencing used with weak reference objects. The returned object will " +"have a type of either ``ProxyType`` or ``CallableProxyType``, depending on " +"whether *object* is callable. Proxy objects are not :term:`hashable` " +"regardless of the referent; this avoids a number of problems related to " +"their fundamentally mutable nature, and prevent their use as dictionary " +"keys. *callback* is the same as the parameter of the same name to the :func:" +"`ref` function." +msgstr "" + +#: ../Doc/library/weakref.rst:145 +msgid "" +"Return the number of weak references and proxies which refer to *object*." +msgstr "" + +#: ../Doc/library/weakref.rst:150 +msgid "" +"Return a list of all weak reference and proxy objects which refer to " +"*object*." +msgstr "" + +#: ../Doc/library/weakref.rst:155 +msgid "" +"Mapping class that references keys weakly. Entries in the dictionary will " +"be discarded when there is no longer a strong reference to the key. This " +"can be used to associate additional data with an object owned by other parts " +"of an application without adding attributes to those objects. This can be " +"especially useful with objects that override attribute accesses." +msgstr "" + +#: ../Doc/library/weakref.rst:163 +msgid "" +"Caution: Because a :class:`WeakKeyDictionary` is built on top of a Python " +"dictionary, it must not change size when iterating over it. This can be " +"difficult to ensure for a :class:`WeakKeyDictionary` because actions " +"performed by the program during iteration may cause items in the dictionary " +"to vanish \"by magic\" (as a side effect of garbage collection)." +msgstr "" + +#: ../Doc/library/weakref.rst:169 +msgid "" +":class:`WeakKeyDictionary` objects have the following additional methods. " +"These expose the internal references directly. The references are not " +"guaranteed to be \"live\" at the time they are used, so the result of " +"calling the references needs to be checked before being used. This can be " +"used to avoid creating references that will cause the garbage collector to " +"keep the keys around longer than needed." +msgstr "" + +#: ../Doc/library/weakref.rst:179 +msgid "Return an iterable of the weak references to the keys." +msgstr "" + +#: ../Doc/library/weakref.rst:184 +msgid "" +"Mapping class that references values weakly. Entries in the dictionary will " +"be discarded when no strong reference to the value exists any more." +msgstr "" + +#: ../Doc/library/weakref.rst:189 +msgid "" +"Caution: Because a :class:`WeakValueDictionary` is built on top of a Python " +"dictionary, it must not change size when iterating over it. This can be " +"difficult to ensure for a :class:`WeakValueDictionary` because actions " +"performed by the program during iteration may cause items in the dictionary " +"to vanish \"by magic\" (as a side effect of garbage collection)." +msgstr "" + +#: ../Doc/library/weakref.rst:195 +msgid "" +":class:`WeakValueDictionary` objects have the following additional methods. " +"These method have the same issues as the and :meth:`keyrefs` method of :" +"class:`WeakKeyDictionary` objects." +msgstr "" + +#: ../Doc/library/weakref.rst:202 +msgid "Return an iterable of the weak references to the values." +msgstr "" + +#: ../Doc/library/weakref.rst:207 +msgid "" +"Set class that keeps weak references to its elements. An element will be " +"discarded when no strong reference to it exists any more." +msgstr "" + +#: ../Doc/library/weakref.rst:213 +msgid "" +"A custom :class:`ref` subclass which simulates a weak reference to a bound " +"method (i.e., a method defined on a class and looked up on an instance). " +"Since a bound method is ephemeral, a standard weak reference cannot keep " +"hold of it. :class:`WeakMethod` has special code to recreate the bound " +"method until either the object or the original function dies::" +msgstr "" + +#: ../Doc/library/weakref.rst:241 +msgid "" +"Return a callable finalizer object which will be called when *obj* is " +"garbage collected. Unlike an ordinary weak reference, a finalizer will " +"always survive until the reference object is collected, greatly simplifying " +"lifecycle management." +msgstr "" + +#: ../Doc/library/weakref.rst:246 +msgid "" +"A finalizer is considered *alive* until it is called (either explicitly or " +"at garbage collection), and after that it is *dead*. Calling a live " +"finalizer returns the result of evaluating ``func(*arg, **kwargs)``, whereas " +"calling a dead finalizer returns :const:`None`." +msgstr "" + +#: ../Doc/library/weakref.rst:251 +msgid "" +"Exceptions raised by finalizer callbacks during garbage collection will be " +"shown on the standard error output, but cannot be propagated. They are " +"handled in the same way as exceptions raised from an object's :meth:" +"`__del__` method or a weak reference's callback." +msgstr "" + +#: ../Doc/library/weakref.rst:257 +msgid "" +"When the program exits, each remaining live finalizer is called unless its :" +"attr:`atexit` attribute has been set to false. They are called in reverse " +"order of creation." +msgstr "" + +#: ../Doc/library/weakref.rst:261 +msgid "" +"A finalizer will never invoke its callback during the later part of the :" +"term:`interpreter shutdown` when module globals are liable to have been " +"replaced by :const:`None`." +msgstr "" + +#: ../Doc/library/weakref.rst:267 +msgid "" +"If *self* is alive then mark it as dead and return the result of calling " +"``func(*args, **kwargs)``. If *self* is dead then return :const:`None`." +msgstr "" + +#: ../Doc/library/weakref.rst:273 +msgid "" +"If *self* is alive then mark it as dead and return the tuple ``(obj, func, " +"args, kwargs)``. If *self* is dead then return :const:`None`." +msgstr "" + +#: ../Doc/library/weakref.rst:279 +msgid "" +"If *self* is alive then return the tuple ``(obj, func, args, kwargs)``. If " +"*self* is dead then return :const:`None`." +msgstr "" + +#: ../Doc/library/weakref.rst:284 +msgid "Property which is true if the finalizer is alive, false otherwise." +msgstr "" + +#: ../Doc/library/weakref.rst:288 +msgid "" +"A writable boolean property which by default is true. When the program " +"exits, it calls all remaining live finalizers for which :attr:`.atexit` is " +"true. They are called in reverse order of creation." +msgstr "" + +#: ../Doc/library/weakref.rst:295 +msgid "" +"It is important to ensure that *func*, *args* and *kwargs* do not own any " +"references to *obj*, either directly or indirectly, since otherwise *obj* " +"will never be garbage collected. In particular, *func* should not be a " +"bound method of *obj*." +msgstr "" + +#: ../Doc/library/weakref.rst:305 +msgid "The type object for weak references objects." +msgstr "" + +#: ../Doc/library/weakref.rst:310 +msgid "The type object for proxies of objects which are not callable." +msgstr "" + +#: ../Doc/library/weakref.rst:315 +msgid "The type object for proxies of callable objects." +msgstr "" + +#: ../Doc/library/weakref.rst:320 +msgid "" +"Sequence containing all the type objects for proxies. This can make it " +"simpler to test if an object is a proxy without being dependent on naming " +"both proxy types." +msgstr "" + +#: ../Doc/library/weakref.rst:327 +msgid "" +"Exception raised when a proxy object is used but the underlying object has " +"been collected. This is the same as the standard :exc:`ReferenceError` " +"exception." +msgstr "" + +#: ../Doc/library/weakref.rst:334 +msgid ":pep:`205` - Weak References" +msgstr "" + +#: ../Doc/library/weakref.rst:334 +msgid "" +"The proposal and rationale for this feature, including links to earlier " +"implementations and information about similar features in other languages." +msgstr "" + +#: ../Doc/library/weakref.rst:341 +msgid "Weak Reference Objects" +msgstr "" + +#: ../Doc/library/weakref.rst:343 +msgid "" +"Weak reference objects have no methods and no attributes besides :attr:`ref." +"__callback__`. A weak reference object allows the referent to be obtained, " +"if it still exists, by calling it:" +msgstr "" + +#: ../Doc/library/weakref.rst:357 +msgid "" +"If the referent no longer exists, calling the reference object returns :" +"const:`None`:" +msgstr "" + +#: ../Doc/library/weakref.rst:364 +msgid "" +"Testing that a weak reference object is still live should be done using the " +"expression ``ref() is not None``. Normally, application code that needs to " +"use a reference object should follow this pattern::" +msgstr "" + +#: ../Doc/library/weakref.rst:377 +msgid "" +"Using a separate test for \"liveness\" creates race conditions in threaded " +"applications; another thread can cause a weak reference to become " +"invalidated before the weak reference is called; the idiom shown above is " +"safe in threaded applications as well as single-threaded applications." +msgstr "" + +#: ../Doc/library/weakref.rst:382 +msgid "" +"Specialized versions of :class:`ref` objects can be created through " +"subclassing. This is used in the implementation of the :class:" +"`WeakValueDictionary` to reduce the memory overhead for each entry in the " +"mapping. This may be most useful to associate additional information with a " +"reference, but could also be used to insert additional processing on calls " +"to retrieve the referent." +msgstr "" + +#: ../Doc/library/weakref.rst:388 +msgid "" +"This example shows how a subclass of :class:`ref` can be used to store " +"additional information about an object and affect the value that's returned " +"when the referent is accessed::" +msgstr "" + +#: ../Doc/library/weakref.rst:417 +msgid "" +"This simple example shows how an application can use object IDs to retrieve " +"objects that it has seen before. The IDs of the objects can then be used in " +"other data structures without forcing the objects to remain alive, but the " +"objects can still be retrieved by ID if they do." +msgstr "" + +#: ../Doc/library/weakref.rst:442 +msgid "Finalizer Objects" +msgstr "" + +#: ../Doc/library/weakref.rst:444 +msgid "" +"The main benefit of using :class:`finalize` is that it makes it simple to " +"register a callback without needing to preserve the returned finalizer " +"object. For instance" +msgstr "" + +#: ../Doc/library/weakref.rst:458 +msgid "" +"The finalizer can be called directly as well. However the finalizer will " +"invoke the callback at most once." +msgstr "" + +#: ../Doc/library/weakref.rst:474 +msgid "" +"You can unregister a finalizer using its :meth:`~finalize.detach` method. " +"This kills the finalizer and returns the arguments passed to the constructor " +"when it was created." +msgstr "" + +#: ../Doc/library/weakref.rst:488 +msgid "" +"Unless you set the :attr:`~finalize.atexit` attribute to :const:`False`, a " +"finalizer will be called when the program exits if it is still alive. For " +"instance" +msgstr "" + +#: ../Doc/library/weakref.rst:500 +msgid "Comparing finalizers with :meth:`__del__` methods" +msgstr "" + +#: ../Doc/library/weakref.rst:502 +msgid "" +"Suppose we want to create a class whose instances represent temporary " +"directories. The directories should be deleted with their contents when the " +"first of the following events occurs:" +msgstr "" + +#: ../Doc/library/weakref.rst:506 +msgid "the object is garbage collected," +msgstr "" + +#: ../Doc/library/weakref.rst:507 +msgid "the object's :meth:`remove` method is called, or" +msgstr "" + +#: ../Doc/library/weakref.rst:508 +msgid "the program exits." +msgstr "" + +#: ../Doc/library/weakref.rst:510 +msgid "" +"We might try to implement the class using a :meth:`__del__` method as " +"follows::" +msgstr "" + +#: ../Doc/library/weakref.rst:529 +msgid "" +"Starting with Python 3.4, :meth:`__del__` methods no longer prevent " +"reference cycles from being garbage collected, and module globals are no " +"longer forced to :const:`None` during :term:`interpreter shutdown`. So this " +"code should work without any issues on CPython." +msgstr "" + +#: ../Doc/library/weakref.rst:534 +msgid "" +"However, handling of :meth:`__del__` methods is notoriously implementation " +"specific, since it depends on internal details of the interpreter's garbage " +"collector implementation." +msgstr "" + +#: ../Doc/library/weakref.rst:538 +msgid "" +"A more robust alternative can be to define a finalizer which only references " +"the specific functions and objects that it needs, rather than having access " +"to the full state of the object::" +msgstr "" + +#: ../Doc/library/weakref.rst:554 +msgid "" +"Defined like this, our finalizer only receives a reference to the details it " +"needs to clean up the directory appropriately. If the object never gets " +"garbage collected the finalizer will still be called at exit." +msgstr "" + +#: ../Doc/library/weakref.rst:558 +msgid "" +"The other advantage of weakref based finalizers is that they can be used to " +"register finalizers for classes where the definition is controlled by a " +"third party, such as running code when a module is unloaded::" +msgstr "" + +#: ../Doc/library/weakref.rst:570 +msgid "" +"If you create a finalizer object in a daemonic thread just as the program " +"exits then there is the possibility that the finalizer does not get called " +"at exit. However, in a daemonic thread :func:`atexit.register`, ``try: ... " +"finally: ...`` and ``with: ...`` do not guarantee that cleanup occurs either." +msgstr "" + +#: ../Doc/library/webbrowser.rst:2 +msgid ":mod:`webbrowser` --- Convenient Web-browser controller" +msgstr "" + +#: ../Doc/library/webbrowser.rst:10 +msgid "**Source code:** :source:`Lib/webbrowser.py`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:14 +msgid "" +"The :mod:`webbrowser` module provides a high-level interface to allow " +"displaying Web-based documents to users. Under most circumstances, simply " +"calling the :func:`.open` function from this module will do the right thing." +msgstr "" + +#: ../Doc/library/webbrowser.rst:18 +msgid "" +"Under Unix, graphical browsers are preferred under X11, but text-mode " +"browsers will be used if graphical browsers are not available or an X11 " +"display isn't available. If text-mode browsers are used, the calling " +"process will block until the user exits the browser." +msgstr "" + +#: ../Doc/library/webbrowser.rst:23 +msgid "" +"If the environment variable :envvar:`BROWSER` exists, it is interpreted as " +"the :data:`os.pathsep`-separated list of browsers to try ahead of the " +"platform defaults. When the value of a list part contains the string ``" +"%s``, then it is interpreted as a literal browser command line to be used " +"with the argument URL substituted for ``%s``; if the part does not contain ``" +"%s``, it is simply interpreted as the name of the browser to launch. [1]_" +msgstr "" + +#: ../Doc/library/webbrowser.rst:30 +msgid "" +"For non-Unix platforms, or when a remote browser is available on Unix, the " +"controlling process will not wait for the user to finish with the browser, " +"but allow the remote browser to maintain its own windows on the display. If " +"remote browsers are not available on Unix, the controlling process will " +"launch a new browser and wait." +msgstr "" + +#: ../Doc/library/webbrowser.rst:36 +msgid "" +"The script :program:`webbrowser` can be used as a command-line interface for " +"the module. It accepts a URL as the argument. It accepts the following " +"optional parameters: ``-n`` opens the URL in a new browser window, if " +"possible; ``-t`` opens the URL in a new browser page (\"tab\"). The options " +"are, naturally, mutually exclusive. Usage example::" +msgstr "" + +#: ../Doc/library/webbrowser.rst:49 +msgid "Exception raised when a browser control error occurs." +msgstr "" + +#: ../Doc/library/webbrowser.rst:56 +msgid "" +"Display *url* using the default browser. If *new* is 0, the *url* is opened " +"in the same browser window if possible. If *new* is 1, a new browser window " +"is opened if possible. If *new* is 2, a new browser page (\"tab\") is " +"opened if possible. If *autoraise* is ``True``, the window is raised if " +"possible (note that under many window managers this will occur regardless of " +"the setting of this variable)." +msgstr "" + +#: ../Doc/library/webbrowser.rst:63 +msgid "" +"Note that on some platforms, trying to open a filename using this function, " +"may work and start the operating system's associated program. However, this " +"is neither supported nor portable." +msgstr "" + +#: ../Doc/library/webbrowser.rst:70 +msgid "" +"Open *url* in a new window of the default browser, if possible, otherwise, " +"open *url* in the only browser window." +msgstr "" + +#: ../Doc/library/webbrowser.rst:75 +msgid "" +"Open *url* in a new page (\"tab\") of the default browser, if possible, " +"otherwise equivalent to :func:`open_new`." +msgstr "" + +#: ../Doc/library/webbrowser.rst:81 +msgid "" +"Return a controller object for the browser type *using*. If *using* is " +"``None``, return a controller for a default browser appropriate to the " +"caller's environment." +msgstr "" + +#: ../Doc/library/webbrowser.rst:88 +msgid "" +"Register the browser type *name*. Once a browser type is registered, the :" +"func:`get` function can return a controller for that browser type. If " +"*instance* is not provided, or is ``None``, *constructor* will be called " +"without parameters to create an instance when needed. If *instance* is " +"provided, *constructor* will never be called, and may be ``None``." +msgstr "" + +#: ../Doc/library/webbrowser.rst:94 +msgid "" +"This entry point is only useful if you plan to either set the :envvar:" +"`BROWSER` variable or call :func:`get` with a nonempty argument matching the " +"name of a handler you declare." +msgstr "" + +#: ../Doc/library/webbrowser.rst:98 +msgid "" +"A number of browser types are predefined. This table gives the type names " +"that may be passed to the :func:`get` function and the corresponding " +"instantiations for the controller classes, all defined in this module." +msgstr "" + +#: ../Doc/library/webbrowser.rst:103 +msgid "Type Name" +msgstr "" + +#: ../Doc/library/webbrowser.rst:103 +msgid "Class Name" +msgstr "" + +#: ../Doc/library/webbrowser.rst:105 +msgid "``'mozilla'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:105 ../Doc/library/webbrowser.rst:107 +msgid ":class:`Mozilla('mozilla')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:107 +msgid "``'firefox'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:109 +msgid "``'netscape'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:109 +msgid ":class:`Mozilla('netscape')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:111 +msgid "``'galeon'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:111 +msgid ":class:`Galeon('galeon')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:113 +msgid "``'epiphany'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:113 +msgid ":class:`Galeon('epiphany')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:115 +msgid "``'skipstone'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:115 +msgid ":class:`BackgroundBrowser('skipstone')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:117 +msgid "``'kfmclient'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:117 ../Doc/library/webbrowser.rst:119 +#: ../Doc/library/webbrowser.rst:121 +msgid ":class:`Konqueror()`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:119 +msgid "``'konqueror'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:121 +msgid "``'kfm'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:123 +msgid "``'mosaic'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:123 +msgid ":class:`BackgroundBrowser('mosaic')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:125 +msgid "``'opera'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:125 +msgid ":class:`Opera()`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:127 +msgid "``'grail'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:127 +msgid ":class:`Grail()`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:129 +msgid "``'links'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:129 +msgid ":class:`GenericBrowser('links')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:131 +msgid "``'elinks'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:131 +msgid ":class:`Elinks('elinks')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:133 +msgid "``'lynx'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:133 +msgid ":class:`GenericBrowser('lynx')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:135 +msgid "``'w3m'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:135 +msgid ":class:`GenericBrowser('w3m')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:137 +msgid "``'windows-default'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:137 +msgid ":class:`WindowsDefault`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:139 +msgid "``'macosx'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:139 +msgid ":class:`MacOSX('default')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:141 +msgid "``'safari'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:141 +msgid ":class:`MacOSX('safari')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:143 +msgid "``'google-chrome'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:143 +msgid ":class:`Chrome('google-chrome')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:145 +msgid "``'chrome'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:145 +msgid ":class:`Chrome('chrome')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:147 +msgid "``'chromium'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:147 +msgid ":class:`Chromium('chromium')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:149 +msgid "``'chromium-browser'``" +msgstr "" + +#: ../Doc/library/webbrowser.rst:149 +msgid ":class:`Chromium('chromium-browser')`" +msgstr "" + +#: ../Doc/library/webbrowser.rst:155 +msgid "" +"\"Konqueror\" is the file manager for the KDE desktop environment for Unix, " +"and only makes sense to use if KDE is running. Some way of reliably " +"detecting KDE would be nice; the :envvar:`KDEDIR` variable is not " +"sufficient. Note also that the name \"kfm\" is used even when using the :" +"program:`konqueror` command with KDE 2 --- the implementation selects the " +"best strategy for running Konqueror." +msgstr "" + +#: ../Doc/library/webbrowser.rst:162 +msgid "Only on Windows platforms." +msgstr "" + +#: ../Doc/library/webbrowser.rst:165 +msgid "Only on Mac OS X platform." +msgstr "" + +#: ../Doc/library/webbrowser.rst:167 +msgid "Support for Chrome/Chromium has been added." +msgstr "" + +#: ../Doc/library/webbrowser.rst:170 +msgid "Here are some simple examples::" +msgstr "" + +#: ../Doc/library/webbrowser.rst:184 +msgid "Browser Controller Objects" +msgstr "" + +#: ../Doc/library/webbrowser.rst:186 +msgid "" +"Browser controllers provide these methods which parallel three of the module-" +"level convenience functions:" +msgstr "" + +#: ../Doc/library/webbrowser.rst:192 +msgid "" +"Display *url* using the browser handled by this controller. If *new* is 1, a " +"new browser window is opened if possible. If *new* is 2, a new browser page " +"(\"tab\") is opened if possible." +msgstr "" + +#: ../Doc/library/webbrowser.rst:199 +msgid "" +"Open *url* in a new window of the browser handled by this controller, if " +"possible, otherwise, open *url* in the only browser window. Alias :func:" +"`open_new`." +msgstr "" + +#: ../Doc/library/webbrowser.rst:206 +msgid "" +"Open *url* in a new page (\"tab\") of the browser handled by this " +"controller, if possible, otherwise equivalent to :func:`open_new`." +msgstr "" + +#: ../Doc/library/webbrowser.rst:212 +msgid "" +"Executables named here without a full path will be searched in the " +"directories given in the :envvar:`PATH` environment variable." +msgstr "" + +#: ../Doc/library/windows.rst:5 +msgid "MS Windows Specific Services" +msgstr "" + +#: ../Doc/library/windows.rst:7 +msgid "" +"This chapter describes modules that are only available on MS Windows " +"platforms." +msgstr "" + +#: ../Doc/library/winreg.rst:2 +msgid ":mod:`winreg` -- Windows registry access" +msgstr "" + +#: ../Doc/library/winreg.rst:12 +msgid "" +"These functions expose the Windows registry API to Python. Instead of using " +"an integer as the registry handle, a :ref:`handle object ` is " +"used to ensure that the handles are closed correctly, even if the programmer " +"neglects to explicitly close them." +msgstr "" + +#: ../Doc/library/winreg.rst:19 +msgid "" +"Several functions in this module used to raise a :exc:`WindowsError`, which " +"is now an alias of :exc:`OSError`." +msgstr "" + +#: ../Doc/library/winreg.rst:28 +msgid "This module offers the following functions:" +msgstr "" + +#: ../Doc/library/winreg.rst:33 +msgid "" +"Closes a previously opened registry key. The *hkey* argument specifies a " +"previously opened key." +msgstr "" + +#: ../Doc/library/winreg.rst:38 +msgid "" +"If *hkey* is not closed using this method (or via :meth:`hkey.Close() " +"`), it is closed when the *hkey* object is destroyed by Python." +msgstr "" + +#: ../Doc/library/winreg.rst:45 +msgid "" +"Establishes a connection to a predefined registry handle on another " +"computer, and returns a :ref:`handle object `." +msgstr "" + +#: ../Doc/library/winreg.rst:48 +msgid "" +"*computer_name* is the name of the remote computer, of the form ``r\"\\" +"\\computername\"``. If ``None``, the local computer is used." +msgstr "" + +#: ../Doc/library/winreg.rst:51 +msgid "*key* is the predefined handle to connect to." +msgstr "" + +#: ../Doc/library/winreg.rst:53 ../Doc/library/winreg.rst:75 +#: ../Doc/library/winreg.rst:103 +msgid "" +"The return value is the handle of the opened key. If the function fails, an :" +"exc:`OSError` exception is raised." +msgstr "" + +#: ../Doc/library/winreg.rst:56 ../Doc/library/winreg.rst:78 +#: ../Doc/library/winreg.rst:108 ../Doc/library/winreg.rst:127 +#: ../Doc/library/winreg.rst:163 ../Doc/library/winreg.rst:190 +#: ../Doc/library/winreg.rst:223 ../Doc/library/winreg.rst:303 +msgid "See :ref:`above `." +msgstr "" + +#: ../Doc/library/winreg.rst:62 ../Doc/library/winreg.rst:84 +msgid "" +"Creates or opens the specified key, returning a :ref:`handle object `." +msgstr "" + +#: ../Doc/library/winreg.rst:65 ../Doc/library/winreg.rst:87 +#: ../Doc/library/winreg.rst:116 ../Doc/library/winreg.rst:141 +#: ../Doc/library/winreg.rst:171 ../Doc/library/winreg.rst:181 +#: ../Doc/library/winreg.rst:198 ../Doc/library/winreg.rst:240 +#: ../Doc/library/winreg.rst:285 ../Doc/library/winreg.rst:311 +#: ../Doc/library/winreg.rst:335 ../Doc/library/winreg.rst:353 +#: ../Doc/library/winreg.rst:375 ../Doc/library/winreg.rst:398 +#: ../Doc/library/winreg.rst:424 ../Doc/library/winreg.rst:453 +#: ../Doc/library/winreg.rst:468 ../Doc/library/winreg.rst:481 +msgid "" +"*key* is an already open key, or one of the predefined :ref:`HKEY_* " +"constants `." +msgstr "" + +#: ../Doc/library/winreg.rst:68 ../Doc/library/winreg.rst:90 +msgid "*sub_key* is a string that names the key this method opens or creates." +msgstr "" + +#: ../Doc/library/winreg.rst:70 ../Doc/library/winreg.rst:98 +msgid "" +"If *key* is one of the predefined keys, *sub_key* may be ``None``. In that " +"case, the handle returned is the same key handle passed in to the function." +msgstr "" + +#: ../Doc/library/winreg.rst:73 ../Doc/library/winreg.rst:101 +msgid "If the key already exists, this function opens the existing key." +msgstr "" + +#: ../Doc/library/winreg.rst:92 ../Doc/library/winreg.rst:148 +msgid "" +"*reserved* is a reserved integer, and must be zero. The default is zero." +msgstr "" + +#: ../Doc/library/winreg.rst:94 +msgid "" +"*access* is an integer that specifies an access mask that describes the " +"desired security access for the key. Default is :const:`KEY_WRITE`. See :" +"ref:`Access Rights ` for other allowed values." +msgstr "" + +#: ../Doc/library/winreg.rst:114 ../Doc/library/winreg.rst:133 +msgid "Deletes the specified key." +msgstr "" + +#: ../Doc/library/winreg.rst:119 +msgid "" +"*sub_key* is a string that must be a subkey of the key identified by the " +"*key* parameter. This value must not be ``None``, and the key may not have " +"subkeys." +msgstr "" + +#: ../Doc/library/winreg.rst:122 ../Doc/library/winreg.rst:154 +msgid "*This method can not delete keys with subkeys.*" +msgstr "" + +#: ../Doc/library/winreg.rst:124 ../Doc/library/winreg.rst:156 +msgid "" +"If the method succeeds, the entire key, including all of its values, is " +"removed. If the method fails, an :exc:`OSError` exception is raised." +msgstr "" + +#: ../Doc/library/winreg.rst:136 +msgid "" +"The :func:`DeleteKeyEx` function is implemented with the RegDeleteKeyEx " +"Windows API function, which is specific to 64-bit versions of Windows. See " +"the `RegDeleteKeyEx documentation `__." +msgstr "" + +#: ../Doc/library/winreg.rst:144 +msgid "" +"*sub_key* is a string that must be a subkey of the key identified by the " +"*key* parameter. This value must not be ``None``, and the key may not have " +"subkeys." +msgstr "" + +#: ../Doc/library/winreg.rst:150 +msgid "" +"*access* is an integer that specifies an access mask that describes the " +"desired security access for the key. Default is :const:`KEY_WOW64_64KEY`. " +"See :ref:`Access Rights ` for other allowed values." +msgstr "" + +#: ../Doc/library/winreg.rst:159 +msgid "On unsupported Windows versions, :exc:`NotImplementedError` is raised." +msgstr "" + +#: ../Doc/library/winreg.rst:169 +msgid "Removes a named value from a registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:174 +msgid "*value* is a string that identifies the value to remove." +msgstr "" + +#: ../Doc/library/winreg.rst:179 +msgid "Enumerates subkeys of an open registry key, returning a string." +msgstr "" + +#: ../Doc/library/winreg.rst:184 +msgid "*index* is an integer that identifies the index of the key to retrieve." +msgstr "" + +#: ../Doc/library/winreg.rst:186 +msgid "" +"The function retrieves the name of one subkey each time it is called. It is " +"typically called repeatedly until an :exc:`OSError` exception is raised, " +"indicating, no more values are available." +msgstr "" + +#: ../Doc/library/winreg.rst:196 +msgid "Enumerates values of an open registry key, returning a tuple." +msgstr "" + +#: ../Doc/library/winreg.rst:201 +msgid "" +"*index* is an integer that identifies the index of the value to retrieve." +msgstr "" + +#: ../Doc/library/winreg.rst:203 +msgid "" +"The function retrieves the name of one subkey each time it is called. It is " +"typically called repeatedly, until an :exc:`OSError` exception is raised, " +"indicating no more values." +msgstr "" + +#: ../Doc/library/winreg.rst:207 ../Doc/library/winreg.rst:314 +msgid "The result is a tuple of 3 items:" +msgstr "" + +#: ../Doc/library/winreg.rst:212 +msgid "A string that identifies the value name" +msgstr "" + +#: ../Doc/library/winreg.rst:214 +msgid "" +"An object that holds the value data, and whose type depends on the " +"underlying registry type" +msgstr "" + +#: ../Doc/library/winreg.rst:218 +msgid "" +"An integer that identifies the type of the value data (see table in docs " +"for :meth:`SetValueEx`)" +msgstr "" + +#: ../Doc/library/winreg.rst:229 +msgid "" +"Expands environment variable placeholders ``%NAME%`` in strings like :const:" +"`REG_EXPAND_SZ`::" +msgstr "" + +#: ../Doc/library/winreg.rst:238 +msgid "Writes all the attributes of a key to the registry." +msgstr "" + +#: ../Doc/library/winreg.rst:243 +msgid "" +"It is not necessary to call :func:`FlushKey` to change a key. Registry " +"changes are flushed to disk by the registry using its lazy flusher. " +"Registry changes are also flushed to disk at system shutdown. Unlike :func:" +"`CloseKey`, the :func:`FlushKey` method returns only when all the data has " +"been written to the registry. An application should only call :func:" +"`FlushKey` if it requires absolute certainty that registry changes are on " +"disk." +msgstr "" + +#: ../Doc/library/winreg.rst:252 +msgid "" +"If you don't know whether a :func:`FlushKey` call is required, it probably " +"isn't." +msgstr "" + +#: ../Doc/library/winreg.rst:258 +msgid "" +"Creates a subkey under the specified key and stores registration information " +"from a specified file into that subkey." +msgstr "" + +#: ../Doc/library/winreg.rst:261 +msgid "" +"*key* is a handle returned by :func:`ConnectRegistry` or one of the " +"constants :const:`HKEY_USERS` or :const:`HKEY_LOCAL_MACHINE`." +msgstr "" + +#: ../Doc/library/winreg.rst:264 +msgid "*sub_key* is a string that identifies the subkey to load." +msgstr "" + +#: ../Doc/library/winreg.rst:266 +msgid "" +"*file_name* is the name of the file to load registry data from. This file " +"must have been created with the :func:`SaveKey` function. Under the file " +"allocation table (FAT) file system, the filename may not have an extension." +msgstr "" + +#: ../Doc/library/winreg.rst:270 +msgid "" +"A call to :func:`LoadKey` fails if the calling process does not have the :" +"const:`SE_RESTORE_PRIVILEGE` privilege. Note that privileges are different " +"from permissions -- see the `RegLoadKey documentation `__ for more details." +msgstr "" + +#: ../Doc/library/winreg.rst:276 +msgid "" +"If *key* is a handle returned by :func:`ConnectRegistry`, then the path " +"specified in *file_name* is relative to the remote computer." +msgstr "" + +#: ../Doc/library/winreg.rst:283 +msgid "" +"Opens the specified key, returning a :ref:`handle object `." +msgstr "" + +#: ../Doc/library/winreg.rst:288 +msgid "*sub_key* is a string that identifies the sub_key to open." +msgstr "" + +#: ../Doc/library/winreg.rst:290 +msgid "" +"*reserved* is a reserved integer, and must be zero. The default is zero." +msgstr "" + +#: ../Doc/library/winreg.rst:292 +msgid "" +"*access* is an integer that specifies an access mask that describes the " +"desired security access for the key. Default is :const:`KEY_READ`. See :" +"ref:`Access Rights ` for other allowed values." +msgstr "" + +#: ../Doc/library/winreg.rst:296 +msgid "The result is a new handle to the specified key." +msgstr "" + +#: ../Doc/library/winreg.rst:298 +msgid "If the function fails, :exc:`OSError` is raised." +msgstr "" + +#: ../Doc/library/winreg.rst:300 +msgid "Allow the use of named arguments." +msgstr "" + +#: ../Doc/library/winreg.rst:309 +msgid "Returns information about a key, as a tuple." +msgstr "" + +#: ../Doc/library/winreg.rst:319 +msgid "An integer giving the number of sub keys this key has." +msgstr "" + +#: ../Doc/library/winreg.rst:322 +msgid "An integer giving the number of values this key has." +msgstr "" + +#: ../Doc/library/winreg.rst:325 +msgid "" +"An integer giving when the key was last modified (if available) as 100's of " +"nanoseconds since Jan 1, 1601." +msgstr "" + +#: ../Doc/library/winreg.rst:333 +msgid "Retrieves the unnamed value for a key, as a string." +msgstr "" + +#: ../Doc/library/winreg.rst:338 +msgid "" +"*sub_key* is a string that holds the name of the subkey with which the value " +"is associated. If this parameter is ``None`` or empty, the function " +"retrieves the value set by the :func:`SetValue` method for the key " +"identified by *key*." +msgstr "" + +#: ../Doc/library/winreg.rst:342 +msgid "" +"Values in the registry have name, type, and data components. This method " +"retrieves the data for a key's first value that has a NULL name. But the " +"underlying API call doesn't return the type, so always use :func:" +"`QueryValueEx` if possible." +msgstr "" + +#: ../Doc/library/winreg.rst:350 +msgid "" +"Retrieves the type and data for a specified value name associated with an " +"open registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:356 +msgid "*value_name* is a string indicating the value to query." +msgstr "" + +#: ../Doc/library/winreg.rst:358 +msgid "The result is a tuple of 2 items:" +msgstr "" + +#: ../Doc/library/winreg.rst:363 +msgid "The value of the registry item." +msgstr "" + +#: ../Doc/library/winreg.rst:365 +msgid "" +"An integer giving the registry type for this value (see table in docs for :" +"meth:`SetValueEx`)" +msgstr "" + +#: ../Doc/library/winreg.rst:373 +msgid "Saves the specified key, and all its subkeys to the specified file." +msgstr "" + +#: ../Doc/library/winreg.rst:378 +msgid "" +"*file_name* is the name of the file to save registry data to. This file " +"cannot already exist. If this filename includes an extension, it cannot be " +"used on file allocation table (FAT) file systems by the :meth:`LoadKey` " +"method." +msgstr "" + +#: ../Doc/library/winreg.rst:383 +msgid "" +"If *key* represents a key on a remote computer, the path described by " +"*file_name* is relative to the remote computer. The caller of this method " +"must possess the :const:`SeBackupPrivilege` security privilege. Note that " +"privileges are different than permissions -- see the `Conflicts Between User " +"Rights and Permissions documentation `__ for more details." +msgstr "" + +#: ../Doc/library/winreg.rst:391 +msgid "This function passes NULL for *security_attributes* to the API." +msgstr "" + +#: ../Doc/library/winreg.rst:396 +msgid "Associates a value with a specified key." +msgstr "" + +#: ../Doc/library/winreg.rst:401 +msgid "" +"*sub_key* is a string that names the subkey with which the value is " +"associated." +msgstr "" + +#: ../Doc/library/winreg.rst:403 +msgid "" +"*type* is an integer that specifies the type of the data. Currently this " +"must be :const:`REG_SZ`, meaning only strings are supported. Use the :func:" +"`SetValueEx` function for support for other data types." +msgstr "" + +#: ../Doc/library/winreg.rst:407 ../Doc/library/winreg.rst:435 +msgid "*value* is a string that specifies the new value." +msgstr "" + +#: ../Doc/library/winreg.rst:409 +msgid "" +"If the key specified by the *sub_key* parameter does not exist, the SetValue " +"function creates it." +msgstr "" + +#: ../Doc/library/winreg.rst:412 ../Doc/library/winreg.rst:443 +msgid "" +"Value lengths are limited by available memory. Long values (more than 2048 " +"bytes) should be stored as files with the filenames stored in the " +"configuration registry. This helps the registry perform efficiently." +msgstr "" + +#: ../Doc/library/winreg.rst:416 +msgid "" +"The key identified by the *key* parameter must have been opened with :const:" +"`KEY_SET_VALUE` access." +msgstr "" + +#: ../Doc/library/winreg.rst:422 +msgid "Stores data in the value field of an open registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:427 +msgid "" +"*value_name* is a string that names the subkey with which the value is " +"associated." +msgstr "" + +#: ../Doc/library/winreg.rst:430 +msgid "*reserved* can be anything -- zero is always passed to the API." +msgstr "" + +#: ../Doc/library/winreg.rst:432 +msgid "" +"*type* is an integer that specifies the type of the data. See :ref:`Value " +"Types ` for the available types." +msgstr "" + +#: ../Doc/library/winreg.rst:437 +msgid "" +"This method can also set additional value and type information for the " +"specified key. The key identified by the key parameter must have been " +"opened with :const:`KEY_SET_VALUE` access." +msgstr "" + +#: ../Doc/library/winreg.rst:441 +msgid "To open the key, use the :func:`CreateKey` or :func:`OpenKey` methods." +msgstr "" + +#: ../Doc/library/winreg.rst:450 +msgid "" +"Disables registry reflection for 32-bit processes running on a 64-bit " +"operating system." +msgstr "" + +#: ../Doc/library/winreg.rst:456 ../Doc/library/winreg.rst:471 +#: ../Doc/library/winreg.rst:486 +msgid "" +"Will generally raise :exc:`NotImplemented` if executed on a 32-bit operating " +"system." +msgstr "" + +#: ../Doc/library/winreg.rst:459 +msgid "" +"If the key is not on the reflection list, the function succeeds but has no " +"effect. Disabling reflection for a key does not affect reflection of any " +"subkeys." +msgstr "" + +#: ../Doc/library/winreg.rst:466 +msgid "Restores registry reflection for the specified disabled key." +msgstr "" + +#: ../Doc/library/winreg.rst:474 +msgid "" +"Restoring reflection for a key does not affect reflection of any subkeys." +msgstr "" + +#: ../Doc/library/winreg.rst:479 +msgid "Determines the reflection state for the specified key." +msgstr "" + +#: ../Doc/library/winreg.rst:484 +msgid "Returns ``True`` if reflection is disabled." +msgstr "" + +#: ../Doc/library/winreg.rst:495 +msgid "" +"The following constants are defined for use in many :mod:`_winreg` functions." +msgstr "" + +#: ../Doc/library/winreg.rst:500 +msgid "HKEY_* Constants" +msgstr "" + +#: ../Doc/library/winreg.rst:504 +msgid "" +"Registry entries subordinate to this key define types (or classes) of " +"documents and the properties associated with those types. Shell and COM " +"applications use the information stored under this key." +msgstr "" + +#: ../Doc/library/winreg.rst:511 +msgid "" +"Registry entries subordinate to this key define the preferences of the " +"current user. These preferences include the settings of environment " +"variables, data about program groups, colors, printers, network connections, " +"and application preferences." +msgstr "" + +#: ../Doc/library/winreg.rst:518 +msgid "" +"Registry entries subordinate to this key define the physical state of the " +"computer, including data about the bus type, system memory, and installed " +"hardware and software." +msgstr "" + +#: ../Doc/library/winreg.rst:524 +msgid "" +"Registry entries subordinate to this key define the default user " +"configuration for new users on the local computer and the user configuration " +"for the current user." +msgstr "" + +#: ../Doc/library/winreg.rst:530 +msgid "" +"Registry entries subordinate to this key allow you to access performance " +"data. The data is not actually stored in the registry; the registry " +"functions cause the system to collect the data from its source." +msgstr "" + +#: ../Doc/library/winreg.rst:538 +msgid "" +"Contains information about the current hardware profile of the local " +"computer system." +msgstr "" + +#: ../Doc/library/winreg.rst:543 +msgid "This key is not used in versions of Windows after 98." +msgstr "" + +#: ../Doc/library/winreg.rst:549 +msgid "Access Rights" +msgstr "" + +#: ../Doc/library/winreg.rst:551 +msgid "" +"For more information, see `Registry Key Security and Access `__." +msgstr "" + +#: ../Doc/library/winreg.rst:556 +msgid "" +"Combines the STANDARD_RIGHTS_REQUIRED, :const:`KEY_QUERY_VALUE`, :const:" +"`KEY_SET_VALUE`, :const:`KEY_CREATE_SUB_KEY`, :const:" +"`KEY_ENUMERATE_SUB_KEYS`, :const:`KEY_NOTIFY`, and :const:`KEY_CREATE_LINK` " +"access rights." +msgstr "" + +#: ../Doc/library/winreg.rst:563 +msgid "" +"Combines the STANDARD_RIGHTS_WRITE, :const:`KEY_SET_VALUE`, and :const:" +"`KEY_CREATE_SUB_KEY` access rights." +msgstr "" + +#: ../Doc/library/winreg.rst:568 +msgid "" +"Combines the STANDARD_RIGHTS_READ, :const:`KEY_QUERY_VALUE`, :const:" +"`KEY_ENUMERATE_SUB_KEYS`, and :const:`KEY_NOTIFY` values." +msgstr "" + +#: ../Doc/library/winreg.rst:573 +msgid "Equivalent to :const:`KEY_READ`." +msgstr "" + +#: ../Doc/library/winreg.rst:577 +msgid "Required to query the values of a registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:581 +msgid "Required to create, delete, or set a registry value." +msgstr "" + +#: ../Doc/library/winreg.rst:585 +msgid "Required to create a subkey of a registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:589 +msgid "Required to enumerate the subkeys of a registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:593 +msgid "" +"Required to request change notifications for a registry key or for subkeys " +"of a registry key." +msgstr "" + +#: ../Doc/library/winreg.rst:598 +msgid "Reserved for system use." +msgstr "" + +#: ../Doc/library/winreg.rst:604 +msgid "64-bit Specific" +msgstr "" + +#: ../Doc/library/winreg.rst:606 +msgid "" +"For more information, see `Accessing an Alternate Registry View `__." +msgstr "" + +#: ../Doc/library/winreg.rst:611 +msgid "" +"Indicates that an application on 64-bit Windows should operate on the 64-bit " +"registry view." +msgstr "" + +#: ../Doc/library/winreg.rst:616 +msgid "" +"Indicates that an application on 64-bit Windows should operate on the 32-bit " +"registry view." +msgstr "" + +#: ../Doc/library/winreg.rst:623 +msgid "Value Types" +msgstr "" + +#: ../Doc/library/winreg.rst:625 +msgid "" +"For more information, see `Registry Value Types `__." +msgstr "" + +#: ../Doc/library/winreg.rst:630 +msgid "Binary data in any form." +msgstr "" + +#: ../Doc/library/winreg.rst:634 +msgid "32-bit number." +msgstr "" + +#: ../Doc/library/winreg.rst:638 +msgid "" +"A 32-bit number in little-endian format. Equivalent to :const:`REG_DWORD`." +msgstr "" + +#: ../Doc/library/winreg.rst:642 +msgid "A 32-bit number in big-endian format." +msgstr "" + +#: ../Doc/library/winreg.rst:646 +msgid "" +"Null-terminated string containing references to environment variables (``" +"%PATH%``)." +msgstr "" + +#: ../Doc/library/winreg.rst:651 +msgid "A Unicode symbolic link." +msgstr "" + +#: ../Doc/library/winreg.rst:655 +msgid "" +"A sequence of null-terminated strings, terminated by two null characters. " +"(Python handles this termination automatically.)" +msgstr "" + +#: ../Doc/library/winreg.rst:660 +msgid "No defined value type." +msgstr "" + +#: ../Doc/library/winreg.rst:664 +msgid "A 64-bit number." +msgstr "" + +#: ../Doc/library/winreg.rst:670 +msgid "" +"A 64-bit number in little-endian format. Equivalent to :const:`REG_QWORD`." +msgstr "" + +#: ../Doc/library/winreg.rst:676 +msgid "A device-driver resource list." +msgstr "" + +#: ../Doc/library/winreg.rst:680 +msgid "A hardware setting." +msgstr "" + +#: ../Doc/library/winreg.rst:684 +msgid "A hardware resource list." +msgstr "" + +#: ../Doc/library/winreg.rst:688 +msgid "A null-terminated string." +msgstr "" + +#: ../Doc/library/winreg.rst:694 +msgid "Registry Handle Objects" +msgstr "" + +#: ../Doc/library/winreg.rst:696 +msgid "" +"This object wraps a Windows HKEY object, automatically closing it when the " +"object is destroyed. To guarantee cleanup, you can call either the :meth:" +"`~PyHKEY.Close` method on the object, or the :func:`CloseKey` function." +msgstr "" + +#: ../Doc/library/winreg.rst:700 +msgid "All registry functions in this module return one of these objects." +msgstr "" + +#: ../Doc/library/winreg.rst:702 +msgid "" +"All registry functions in this module which accept a handle object also " +"accept an integer, however, use of the handle object is encouraged." +msgstr "" + +#: ../Doc/library/winreg.rst:705 +msgid "Handle objects provide semantics for :meth:`__bool__` -- thus ::" +msgstr "" + +#: ../Doc/library/winreg.rst:710 +msgid "" +"will print ``Yes`` if the handle is currently valid (has not been closed or " +"detached)." +msgstr "" + +#: ../Doc/library/winreg.rst:713 +msgid "" +"The object also support comparison semantics, so handle objects will compare " +"true if they both reference the same underlying Windows handle value." +msgstr "" + +#: ../Doc/library/winreg.rst:716 +msgid "" +"Handle objects can be converted to an integer (e.g., using the built-in :" +"func:`int` function), in which case the underlying Windows handle value is " +"returned. You can also use the :meth:`~PyHKEY.Detach` method to return the " +"integer handle, and also disconnect the Windows handle from the handle " +"object." +msgstr "" + +#: ../Doc/library/winreg.rst:724 +msgid "Closes the underlying Windows handle." +msgstr "" + +#: ../Doc/library/winreg.rst:726 +msgid "If the handle is already closed, no error is raised." +msgstr "" + +#: ../Doc/library/winreg.rst:731 +msgid "Detaches the Windows handle from the handle object." +msgstr "" + +#: ../Doc/library/winreg.rst:733 +msgid "" +"The result is an integer that holds the value of the handle before it is " +"detached. If the handle is already detached or closed, this will return " +"zero." +msgstr "" + +#: ../Doc/library/winreg.rst:737 +msgid "" +"After calling this function, the handle is effectively invalidated, but the " +"handle is not closed. You would call this function when you need the " +"underlying Win32 handle to exist beyond the lifetime of the handle object." +msgstr "" + +#: ../Doc/library/winreg.rst:744 +msgid "" +"The HKEY object implements :meth:`~object.__enter__` and :meth:`~object." +"__exit__` and thus supports the context protocol for the :keyword:`with` " +"statement::" +msgstr "" + +#: ../Doc/library/winreg.rst:751 +msgid "" +"will automatically close *key* when control leaves the :keyword:`with` block." +msgstr "" + +#: ../Doc/library/winsound.rst:2 +msgid ":mod:`winsound` --- Sound-playing interface for Windows" +msgstr "" + +#: ../Doc/library/winsound.rst:13 +msgid "" +"The :mod:`winsound` module provides access to the basic sound-playing " +"machinery provided by Windows platforms. It includes functions and several " +"constants." +msgstr "" + +#: ../Doc/library/winsound.rst:19 +msgid "" +"Beep the PC's speaker. The *frequency* parameter specifies frequency, in " +"hertz, of the sound, and must be in the range 37 through 32,767. The " +"*duration* parameter specifies the number of milliseconds the sound should " +"last. If the system is not able to beep the speaker, :exc:`RuntimeError` is " +"raised." +msgstr "" + +#: ../Doc/library/winsound.rst:27 +msgid "" +"Call the underlying :c:func:`PlaySound` function from the Platform API. The " +"*sound* parameter may be a filename, a system sound alias, audio data as a :" +"term:`bytes-like object`, or ``None``. Its interpretation depends on the " +"value of *flags*, which can be a bitwise ORed combination of the constants " +"described below. If the *sound* parameter is ``None``, any currently playing " +"waveform sound is stopped. If the system indicates an error, :exc:" +"`RuntimeError` is raised." +msgstr "" + +#: ../Doc/library/winsound.rst:38 +msgid "" +"Call the underlying :c:func:`MessageBeep` function from the Platform API. " +"This plays a sound as specified in the registry. The *type* argument " +"specifies which sound to play; possible values are ``-1``, " +"``MB_ICONASTERISK``, ``MB_ICONEXCLAMATION``, ``MB_ICONHAND``, " +"``MB_ICONQUESTION``, and ``MB_OK``, all described below. The value ``-1`` " +"produces a \"simple beep\"; this is the final fallback if a sound cannot be " +"played otherwise. If the system indicates an error, :exc:`RuntimeError` is " +"raised." +msgstr "" + +#: ../Doc/library/winsound.rst:49 +msgid "" +"The *sound* parameter is the name of a WAV file. Do not use with :const:" +"`SND_ALIAS`." +msgstr "" + +#: ../Doc/library/winsound.rst:55 +msgid "" +"The *sound* parameter is a sound association name from the registry. If the " +"registry contains no such name, play the system default sound unless :const:" +"`SND_NODEFAULT` is also specified. If no default sound is registered, raise :" +"exc:`RuntimeError`. Do not use with :const:`SND_FILENAME`." +msgstr "" + +#: ../Doc/library/winsound.rst:60 +msgid "" +"All Win32 systems support at least the following; most systems support many " +"more:" +msgstr "" + +#: ../Doc/library/winsound.rst:64 +msgid ":func:`PlaySound` *name*" +msgstr "" + +#: ../Doc/library/winsound.rst:64 +msgid "Corresponding Control Panel Sound name" +msgstr "" + +#: ../Doc/library/winsound.rst:66 +msgid "``'SystemAsterisk'``" +msgstr "" + +#: ../Doc/library/winsound.rst:66 +msgid "Asterisk" +msgstr "" + +#: ../Doc/library/winsound.rst:68 +msgid "``'SystemExclamation'``" +msgstr "" + +#: ../Doc/library/winsound.rst:68 +msgid "Exclamation" +msgstr "" + +#: ../Doc/library/winsound.rst:70 +msgid "``'SystemExit'``" +msgstr "" + +#: ../Doc/library/winsound.rst:70 +msgid "Exit Windows" +msgstr "" + +#: ../Doc/library/winsound.rst:72 +msgid "``'SystemHand'``" +msgstr "" + +#: ../Doc/library/winsound.rst:72 +msgid "Critical Stop" +msgstr "" + +#: ../Doc/library/winsound.rst:74 +msgid "``'SystemQuestion'``" +msgstr "" + +#: ../Doc/library/winsound.rst:74 +msgid "Question" +msgstr "" + +#: ../Doc/library/winsound.rst:90 +msgid "" +"Play the sound repeatedly. The :const:`SND_ASYNC` flag must also be used to " +"avoid blocking. Cannot be used with :const:`SND_MEMORY`." +msgstr "" + +#: ../Doc/library/winsound.rst:96 +msgid "" +"The *sound* parameter to :func:`PlaySound` is a memory image of a WAV file, " +"as a :term:`bytes-like object`." +msgstr "" + +#: ../Doc/library/winsound.rst:101 +msgid "" +"This module does not support playing from a memory image asynchronously, so " +"a combination of this flag and :const:`SND_ASYNC` will raise :exc:" +"`RuntimeError`." +msgstr "" + +#: ../Doc/library/winsound.rst:107 +msgid "Stop playing all instances of the specified sound." +msgstr "" + +#: ../Doc/library/winsound.rst:111 ../Doc/library/winsound.rst:135 +msgid "This flag is not supported on modern Windows platforms." +msgstr "" + +#: ../Doc/library/winsound.rst:116 +msgid "Return immediately, allowing sounds to play asynchronously." +msgstr "" + +#: ../Doc/library/winsound.rst:121 +msgid "" +"If the specified sound cannot be found, do not play the system default sound." +msgstr "" + +#: ../Doc/library/winsound.rst:126 +msgid "Do not interrupt sounds currently playing." +msgstr "" + +#: ../Doc/library/winsound.rst:131 +msgid "Return immediately if the sound driver is busy." +msgstr "" + +#: ../Doc/library/winsound.rst:140 ../Doc/library/winsound.rst:160 +msgid "Play the ``SystemDefault`` sound." +msgstr "" + +#: ../Doc/library/winsound.rst:145 +msgid "Play the ``SystemExclamation`` sound." +msgstr "" + +#: ../Doc/library/winsound.rst:150 +msgid "Play the ``SystemHand`` sound." +msgstr "" + +#: ../Doc/library/winsound.rst:155 +msgid "Play the ``SystemQuestion`` sound." +msgstr "" + +#: ../Doc/library/wsgiref.rst:2 +msgid ":mod:`wsgiref` --- WSGI Utilities and Reference Implementation" +msgstr "" + +#: ../Doc/library/wsgiref.rst:12 +msgid "" +"The Web Server Gateway Interface (WSGI) is a standard interface between web " +"server software and web applications written in Python. Having a standard " +"interface makes it easy to use an application that supports WSGI with a " +"number of different web servers." +msgstr "" + +#: ../Doc/library/wsgiref.rst:17 +msgid "" +"Only authors of web servers and programming frameworks need to know every " +"detail and corner case of the WSGI design. You don't need to understand " +"every detail of WSGI just to install a WSGI application or to write a web " +"application using an existing framework." +msgstr "" + +#: ../Doc/library/wsgiref.rst:22 +msgid "" +":mod:`wsgiref` is a reference implementation of the WSGI specification that " +"can be used to add WSGI support to a web server or framework. It provides " +"utilities for manipulating WSGI environment variables and response headers, " +"base classes for implementing WSGI servers, a demo HTTP server that serves " +"WSGI applications, and a validation tool that checks WSGI servers and " +"applications for conformance to the WSGI specification (:pep:`3333`)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:29 +msgid "" +"See https://wsgi.readthedocs.org/ for more information about WSGI, and links " +"to tutorials and other resources." +msgstr "" + +#: ../Doc/library/wsgiref.rst:36 +msgid ":mod:`wsgiref.util` -- WSGI environment utilities" +msgstr "" + +#: ../Doc/library/wsgiref.rst:42 +msgid "" +"This module provides a variety of utility functions for working with WSGI " +"environments. A WSGI environment is a dictionary containing HTTP request " +"variables as described in :pep:`3333`. All of the functions taking an " +"*environ* parameter expect a WSGI-compliant dictionary to be supplied; " +"please see :pep:`3333` for a detailed specification." +msgstr "" + +#: ../Doc/library/wsgiref.rst:51 +msgid "" +"Return a guess for whether ``wsgi.url_scheme`` should be \"http\" or \"https" +"\", by checking for a ``HTTPS`` environment variable in the *environ* " +"dictionary. The return value is a string." +msgstr "" + +#: ../Doc/library/wsgiref.rst:55 +msgid "" +"This function is useful when creating a gateway that wraps CGI or a CGI-like " +"protocol such as FastCGI. Typically, servers providing such protocols will " +"include a ``HTTPS`` variable with a value of \"1\" \"yes\", or \"on\" when a " +"request is received via SSL. So, this function returns \"https\" if such a " +"value is found, and \"http\" otherwise." +msgstr "" + +#: ../Doc/library/wsgiref.rst:64 +msgid "" +"Return the full request URI, optionally including the query string, using " +"the algorithm found in the \"URL Reconstruction\" section of :pep:`3333`. " +"If *include_query* is false, the query string is not included in the " +"resulting URI." +msgstr "" + +#: ../Doc/library/wsgiref.rst:71 +msgid "" +"Similar to :func:`request_uri`, except that the ``PATH_INFO`` and " +"``QUERY_STRING`` variables are ignored. The result is the base URI of the " +"application object addressed by the request." +msgstr "" + +#: ../Doc/library/wsgiref.rst:78 +msgid "" +"Shift a single name from ``PATH_INFO`` to ``SCRIPT_NAME`` and return the " +"name. The *environ* dictionary is *modified* in-place; use a copy if you " +"need to keep the original ``PATH_INFO`` or ``SCRIPT_NAME`` intact." +msgstr "" + +#: ../Doc/library/wsgiref.rst:82 +msgid "" +"If there are no remaining path segments in ``PATH_INFO``, ``None`` is " +"returned." +msgstr "" + +#: ../Doc/library/wsgiref.rst:84 +msgid "" +"Typically, this routine is used to process each portion of a request URI " +"path, for example to treat the path as a series of dictionary keys. This " +"routine modifies the passed-in environment to make it suitable for invoking " +"another WSGI application that is located at the target URI. For example, if " +"there is a WSGI application at ``/foo``, and the request URI path is ``/foo/" +"bar/baz``, and the WSGI application at ``/foo`` calls :func:" +"`shift_path_info`, it will receive the string \"bar\", and the environment " +"will be updated to be suitable for passing to a WSGI application at ``/foo/" +"bar``. That is, ``SCRIPT_NAME`` will change from ``/foo`` to ``/foo/bar``, " +"and ``PATH_INFO`` will change from ``/bar/baz`` to ``/baz``." +msgstr "" + +#: ../Doc/library/wsgiref.rst:95 +msgid "" +"When ``PATH_INFO`` is just a \"/\", this routine returns an empty string and " +"appends a trailing slash to ``SCRIPT_NAME``, even though empty path segments " +"are normally ignored, and ``SCRIPT_NAME`` doesn't normally end in a slash. " +"This is intentional behavior, to ensure that an application can tell the " +"difference between URIs ending in ``/x`` from ones ending in ``/x/`` when " +"using this routine to do object traversal." +msgstr "" + +#: ../Doc/library/wsgiref.rst:105 +msgid "Update *environ* with trivial defaults for testing purposes." +msgstr "" + +#: ../Doc/library/wsgiref.rst:107 +msgid "" +"This routine adds various parameters required for WSGI, including " +"``HTTP_HOST``, ``SERVER_NAME``, ``SERVER_PORT``, ``REQUEST_METHOD``, " +"``SCRIPT_NAME``, ``PATH_INFO``, and all of the :pep:`3333`\\ -defined ``wsgi." +"*`` variables. It only supplies default values, and does not replace any " +"existing settings for these variables." +msgstr "" + +#: ../Doc/library/wsgiref.rst:113 +msgid "" +"This routine is intended to make it easier for unit tests of WSGI servers " +"and applications to set up dummy environments. It should NOT be used by " +"actual WSGI servers or applications, since the data is fake!" +msgstr "" + +#: ../Doc/library/wsgiref.rst:141 +msgid "" +"In addition to the environment functions above, the :mod:`wsgiref.util` " +"module also provides these miscellaneous utilities:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:147 +msgid "" +"Return true if 'header_name' is an HTTP/1.1 \"Hop-by-Hop\" header, as " +"defined by :rfc:`2616`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:153 +msgid "" +"A wrapper to convert a file-like object to an :term:`iterator`. The " +"resulting objects support both :meth:`__getitem__` and :meth:`__iter__` " +"iteration styles, for compatibility with Python 2.1 and Jython. As the " +"object is iterated over, the optional *blksize* parameter will be repeatedly " +"passed to the *filelike* object's :meth:`read` method to obtain bytestrings " +"to yield. When :meth:`read` returns an empty bytestring, iteration is ended " +"and is not resumable." +msgstr "" + +#: ../Doc/library/wsgiref.rst:160 +msgid "" +"If *filelike* has a :meth:`close` method, the returned object will also have " +"a :meth:`close` method, and it will invoke the *filelike* object's :meth:" +"`close` method when called." +msgstr "" + +#: ../Doc/library/wsgiref.rst:179 +msgid ":mod:`wsgiref.headers` -- WSGI response header tools" +msgstr "" + +#: ../Doc/library/wsgiref.rst:185 +msgid "" +"This module provides a single class, :class:`Headers`, for convenient " +"manipulation of WSGI response headers using a mapping-like interface." +msgstr "" + +#: ../Doc/library/wsgiref.rst:191 +msgid "" +"Create a mapping-like object wrapping *headers*, which must be a list of " +"header name/value tuples as described in :pep:`3333`. The default value of " +"*headers* is an empty list." +msgstr "" + +#: ../Doc/library/wsgiref.rst:195 +msgid "" +":class:`Headers` objects support typical mapping operations including :meth:" +"`__getitem__`, :meth:`get`, :meth:`__setitem__`, :meth:`setdefault`, :meth:" +"`__delitem__` and :meth:`__contains__`. For each of these methods, the key " +"is the header name (treated case-insensitively), and the value is the first " +"value associated with that header name. Setting a header deletes any " +"existing values for that header, then adds a new value at the end of the " +"wrapped header list. Headers' existing order is generally maintained, with " +"new headers added to the end of the wrapped list." +msgstr "" + +#: ../Doc/library/wsgiref.rst:204 +msgid "" +"Unlike a dictionary, :class:`Headers` objects do not raise an error when you " +"try to get or delete a key that isn't in the wrapped header list. Getting a " +"nonexistent header just returns ``None``, and deleting a nonexistent header " +"does nothing." +msgstr "" + +#: ../Doc/library/wsgiref.rst:209 +msgid "" +":class:`Headers` objects also support :meth:`keys`, :meth:`values`, and :" +"meth:`items` methods. The lists returned by :meth:`keys` and :meth:`items` " +"can include the same key more than once if there is a multi-valued header. " +"The ``len()`` of a :class:`Headers` object is the same as the length of its :" +"meth:`items`, which is the same as the length of the wrapped header list. " +"In fact, the :meth:`items` method just returns a copy of the wrapped header " +"list." +msgstr "" + +#: ../Doc/library/wsgiref.rst:216 +msgid "" +"Calling ``bytes()`` on a :class:`Headers` object returns a formatted " +"bytestring suitable for transmission as HTTP response headers. Each header " +"is placed on a line with its value, separated by a colon and a space. Each " +"line is terminated by a carriage return and line feed, and the bytestring is " +"terminated with a blank line." +msgstr "" + +#: ../Doc/library/wsgiref.rst:222 +msgid "" +"In addition to their mapping interface and formatting features, :class:" +"`Headers` objects also have the following methods for querying and adding " +"multi-valued headers, and for adding headers with MIME parameters:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:229 +msgid "Return a list of all the values for the named header." +msgstr "" + +#: ../Doc/library/wsgiref.rst:231 +msgid "" +"The returned list will be sorted in the order they appeared in the original " +"header list or were added to this instance, and may contain duplicates. Any " +"fields deleted and re-inserted are always appended to the header list. If " +"no fields exist with the given name, returns an empty list." +msgstr "" + +#: ../Doc/library/wsgiref.rst:239 +msgid "" +"Add a (possibly multi-valued) header, with optional MIME parameters " +"specified via keyword arguments." +msgstr "" + +#: ../Doc/library/wsgiref.rst:242 +msgid "" +"*name* is the header field to add. Keyword arguments can be used to set " +"MIME parameters for the header field. Each parameter must be a string or " +"``None``. Underscores in parameter names are converted to dashes, since " +"dashes are illegal in Python identifiers, but many MIME parameter names " +"include dashes. If the parameter value is a string, it is added to the " +"header value parameters in the form ``name=\"value\"``. If it is ``None``, " +"only the parameter name is added. (This is used for MIME parameters without " +"a value.) Example usage::" +msgstr "" + +#: ../Doc/library/wsgiref.rst:252 +msgid "The above will add a header that looks like this::" +msgstr "" + +#: ../Doc/library/wsgiref.rst:257 +msgid "*headers* parameter is optional." +msgstr "" + +#: ../Doc/library/wsgiref.rst:262 +msgid ":mod:`wsgiref.simple_server` -- a simple WSGI HTTP server" +msgstr "" + +#: ../Doc/library/wsgiref.rst:268 +msgid "" +"This module implements a simple HTTP server (based on :mod:`http.server`) " +"that serves WSGI applications. Each server instance serves a single WSGI " +"application on a given host and port. If you want to serve multiple " +"applications on a single host and port, you should create a WSGI application " +"that parses ``PATH_INFO`` to select which application to invoke for each " +"request. (E.g., using the :func:`shift_path_info` function from :mod:" +"`wsgiref.util`.)" +msgstr "" + +#: ../Doc/library/wsgiref.rst:279 +msgid "" +"Create a new WSGI server listening on *host* and *port*, accepting " +"connections for *app*. The return value is an instance of the supplied " +"*server_class*, and will process requests using the specified " +"*handler_class*. *app* must be a WSGI application object, as defined by :" +"pep:`3333`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:300 +msgid "" +"This function is a small but complete WSGI application that returns a text " +"page containing the message \"Hello world!\" and a list of the key/value " +"pairs provided in the *environ* parameter. It's useful for verifying that a " +"WSGI server (such as :mod:`wsgiref.simple_server`) is able to run a simple " +"WSGI application correctly." +msgstr "" + +#: ../Doc/library/wsgiref.rst:309 +msgid "" +"Create a :class:`WSGIServer` instance. *server_address* should be a ``(host," +"port)`` tuple, and *RequestHandlerClass* should be the subclass of :class:" +"`http.server.BaseHTTPRequestHandler` that will be used to process requests." +msgstr "" + +#: ../Doc/library/wsgiref.rst:314 +msgid "" +"You do not normally need to call this constructor, as the :func:" +"`make_server` function can handle all the details for you." +msgstr "" + +#: ../Doc/library/wsgiref.rst:317 +msgid "" +":class:`WSGIServer` is a subclass of :class:`http.server.HTTPServer`, so all " +"of its methods (such as :meth:`serve_forever` and :meth:`handle_request`) " +"are available. :class:`WSGIServer` also provides these WSGI-specific methods:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:324 +msgid "" +"Sets the callable *application* as the WSGI application that will receive " +"requests." +msgstr "" + +#: ../Doc/library/wsgiref.rst:330 +msgid "Returns the currently-set application callable." +msgstr "" + +#: ../Doc/library/wsgiref.rst:332 +msgid "" +"Normally, however, you do not need to use these additional methods, as :meth:" +"`set_app` is normally called by :func:`make_server`, and the :meth:`get_app` " +"exists mainly for the benefit of request handler instances." +msgstr "" + +#: ../Doc/library/wsgiref.rst:339 +msgid "" +"Create an HTTP handler for the given *request* (i.e. a socket), " +"*client_address* (a ``(host,port)`` tuple), and *server* (:class:" +"`WSGIServer` instance)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:342 +msgid "" +"You do not need to create instances of this class directly; they are " +"automatically created as needed by :class:`WSGIServer` objects. You can, " +"however, subclass this class and supply it as a *handler_class* to the :func:" +"`make_server` function. Some possibly relevant methods for overriding in " +"subclasses:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:351 +msgid "" +"Returns a dictionary containing the WSGI environment for a request. The " +"default implementation copies the contents of the :class:`WSGIServer` " +"object's :attr:`base_environ` dictionary attribute and then adds various " +"headers derived from the HTTP request. Each call to this method should " +"return a new dictionary containing all of the relevant CGI environment " +"variables as specified in :pep:`3333`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:361 +msgid "" +"Return the object that should be used as the ``wsgi.errors`` stream. The " +"default implementation just returns ``sys.stderr``." +msgstr "" + +#: ../Doc/library/wsgiref.rst:367 +msgid "" +"Process the HTTP request. The default implementation creates a handler " +"instance using a :mod:`wsgiref.handlers` class to implement the actual WSGI " +"application interface." +msgstr "" + +#: ../Doc/library/wsgiref.rst:373 +msgid ":mod:`wsgiref.validate` --- WSGI conformance checker" +msgstr "" + +#: ../Doc/library/wsgiref.rst:379 +msgid "" +"When creating new WSGI application objects, frameworks, servers, or " +"middleware, it can be useful to validate the new code's conformance using :" +"mod:`wsgiref.validate`. This module provides a function that creates WSGI " +"application objects that validate communications between a WSGI server or " +"gateway and a WSGI application object, to check both sides for protocol " +"conformance." +msgstr "" + +#: ../Doc/library/wsgiref.rst:386 +msgid "" +"Note that this utility does not guarantee complete :pep:`3333` compliance; " +"an absence of errors from this module does not necessarily mean that errors " +"do not exist. However, if this module does produce an error, then it is " +"virtually certain that either the server or application is not 100% " +"compliant." +msgstr "" + +#: ../Doc/library/wsgiref.rst:391 +msgid "" +"This module is based on the :mod:`paste.lint` module from Ian Bicking's " +"\"Python Paste\" library." +msgstr "" + +#: ../Doc/library/wsgiref.rst:397 +msgid "" +"Wrap *application* and return a new WSGI application object. The returned " +"application will forward all requests to the original *application*, and " +"will check that both the *application* and the server invoking it are " +"conforming to the WSGI specification and to RFC 2616." +msgstr "" + +#: ../Doc/library/wsgiref.rst:402 +msgid "" +"Any detected nonconformance results in an :exc:`AssertionError` being " +"raised; note, however, that how these errors are handled is server-" +"dependent. For example, :mod:`wsgiref.simple_server` and other servers " +"based on :mod:`wsgiref.handlers` (that don't override the error handling " +"methods to do something else) will simply output a message that an error has " +"occurred, and dump the traceback to ``sys.stderr`` or some other error " +"stream." +msgstr "" + +#: ../Doc/library/wsgiref.rst:409 +msgid "" +"This wrapper may also generate output using the :mod:`warnings` module to " +"indicate behaviors that are questionable but which may not actually be " +"prohibited by :pep:`3333`. Unless they are suppressed using Python command-" +"line options or the :mod:`warnings` API, any such warnings will be written " +"to ``sys.stderr`` (*not* ``wsgi.errors``, unless they happen to be the same " +"object)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:441 +msgid ":mod:`wsgiref.handlers` -- server/gateway base classes" +msgstr "" + +#: ../Doc/library/wsgiref.rst:447 +msgid "" +"This module provides base handler classes for implementing WSGI servers and " +"gateways. These base classes handle most of the work of communicating with " +"a WSGI application, as long as they are given a CGI-like environment, along " +"with input, output, and error streams." +msgstr "" + +#: ../Doc/library/wsgiref.rst:455 +msgid "" +"CGI-based invocation via ``sys.stdin``, ``sys.stdout``, ``sys.stderr`` and " +"``os.environ``. This is useful when you have a WSGI application and want to " +"run it as a CGI script. Simply invoke ``CGIHandler().run(app)``, where " +"``app`` is the WSGI application object you wish to invoke." +msgstr "" + +#: ../Doc/library/wsgiref.rst:460 +msgid "" +"This class is a subclass of :class:`BaseCGIHandler` that sets ``wsgi." +"run_once`` to true, ``wsgi.multithread`` to false, and ``wsgi.multiprocess`` " +"to true, and always uses :mod:`sys` and :mod:`os` to obtain the necessary " +"CGI streams and environment." +msgstr "" + +#: ../Doc/library/wsgiref.rst:468 +msgid "" +"A specialized alternative to :class:`CGIHandler`, for use when deploying on " +"Microsoft's IIS web server, without having set the config allowPathInfo " +"option (IIS>=7) or metabase allowPathInfoForScriptMappings (IIS<7)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:472 +msgid "" +"By default, IIS gives a ``PATH_INFO`` that duplicates the ``SCRIPT_NAME`` at " +"the front, causing problems for WSGI applications that wish to implement " +"routing. This handler strips any such duplicated path." +msgstr "" + +#: ../Doc/library/wsgiref.rst:476 +msgid "" +"IIS can be configured to pass the correct ``PATH_INFO``, but this causes " +"another bug where ``PATH_TRANSLATED`` is wrong. Luckily this variable is " +"rarely used and is not guaranteed by WSGI. On IIS<7, though, the setting can " +"only be made on a vhost level, affecting all other script mappings, many of " +"which break when exposed to the ``PATH_TRANSLATED`` bug. For this reason " +"IIS<7 is almost never deployed with the fix. (Even IIS7 rarely uses it " +"because there is still no UI for it.)" +msgstr "" + +#: ../Doc/library/wsgiref.rst:484 +msgid "" +"There is no way for CGI code to tell whether the option was set, so a " +"separate handler class is provided. It is used in the same way as :class:" +"`CGIHandler`, i.e., by calling ``IISCGIHandler().run(app)``, where ``app`` " +"is the WSGI application object you wish to invoke." +msgstr "" + +#: ../Doc/library/wsgiref.rst:494 +msgid "" +"Similar to :class:`CGIHandler`, but instead of using the :mod:`sys` and :mod:" +"`os` modules, the CGI environment and I/O streams are specified explicitly. " +"The *multithread* and *multiprocess* values are used to set the ``wsgi." +"multithread`` and ``wsgi.multiprocess`` flags for any applications run by " +"the handler instance." +msgstr "" + +#: ../Doc/library/wsgiref.rst:500 +msgid "" +"This class is a subclass of :class:`SimpleHandler` intended for use with " +"software other than HTTP \"origin servers\". If you are writing a gateway " +"protocol implementation (such as CGI, FastCGI, SCGI, etc.) that uses a " +"``Status:`` header to send an HTTP status, you probably want to subclass " +"this instead of :class:`SimpleHandler`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:509 +msgid "" +"Similar to :class:`BaseCGIHandler`, but designed for use with HTTP origin " +"servers. If you are writing an HTTP server implementation, you will " +"probably want to subclass this instead of :class:`BaseCGIHandler`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:513 +msgid "" +"This class is a subclass of :class:`BaseHandler`. It overrides the :meth:" +"`__init__`, :meth:`get_stdin`, :meth:`get_stderr`, :meth:`add_cgi_vars`, :" +"meth:`_write`, and :meth:`_flush` methods to support explicitly setting the " +"environment and streams via the constructor. The supplied environment and " +"streams are stored in the :attr:`stdin`, :attr:`stdout`, :attr:`stderr`, " +"and :attr:`environ` attributes." +msgstr "" + +#: ../Doc/library/wsgiref.rst:520 +msgid "" +"The :meth:`~io.BufferedIOBase.write` method of *stdout* should write each " +"chunk in full, like :class:`io.BufferedIOBase`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:526 +msgid "" +"This is an abstract base class for running WSGI applications. Each instance " +"will handle a single HTTP request, although in principle you could create a " +"subclass that was reusable for multiple requests." +msgstr "" + +#: ../Doc/library/wsgiref.rst:530 +msgid "" +":class:`BaseHandler` instances have only one method intended for external " +"use:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:535 +msgid "Run the specified WSGI application, *app*." +msgstr "" + +#: ../Doc/library/wsgiref.rst:537 +msgid "" +"All of the other :class:`BaseHandler` methods are invoked by this method in " +"the process of running the application, and thus exist primarily to allow " +"customizing the process." +msgstr "" + +#: ../Doc/library/wsgiref.rst:541 +msgid "The following methods MUST be overridden in a subclass:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:546 +msgid "" +"Buffer the bytes *data* for transmission to the client. It's okay if this " +"method actually transmits the data; :class:`BaseHandler` just separates " +"write and flush operations for greater efficiency when the underlying system " +"actually has such a distinction." +msgstr "" + +#: ../Doc/library/wsgiref.rst:554 +msgid "" +"Force buffered data to be transmitted to the client. It's okay if this " +"method is a no-op (i.e., if :meth:`_write` actually sends the data)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:560 +msgid "" +"Return an input stream object suitable for use as the ``wsgi.input`` of the " +"request currently being processed." +msgstr "" + +#: ../Doc/library/wsgiref.rst:566 +msgid "" +"Return an output stream object suitable for use as the ``wsgi.errors`` of " +"the request currently being processed." +msgstr "" + +#: ../Doc/library/wsgiref.rst:572 +msgid "" +"Insert CGI variables for the current request into the :attr:`environ` " +"attribute." +msgstr "" + +#: ../Doc/library/wsgiref.rst:574 +msgid "" +"Here are some other methods and attributes you may wish to override. This " +"list is only a summary, however, and does not include every method that can " +"be overridden. You should consult the docstrings and source code for " +"additional information before attempting to create a customized :class:" +"`BaseHandler` subclass." +msgstr "" + +#: ../Doc/library/wsgiref.rst:580 +msgid "Attributes and methods for customizing the WSGI environment:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:585 +msgid "" +"The value to be used for the ``wsgi.multithread`` environment variable. It " +"defaults to true in :class:`BaseHandler`, but may have a different default " +"(or be set by the constructor) in the other subclasses." +msgstr "" + +#: ../Doc/library/wsgiref.rst:592 +msgid "" +"The value to be used for the ``wsgi.multiprocess`` environment variable. It " +"defaults to true in :class:`BaseHandler`, but may have a different default " +"(or be set by the constructor) in the other subclasses." +msgstr "" + +#: ../Doc/library/wsgiref.rst:599 +msgid "" +"The value to be used for the ``wsgi.run_once`` environment variable. It " +"defaults to false in :class:`BaseHandler`, but :class:`CGIHandler` sets it " +"to true by default." +msgstr "" + +#: ../Doc/library/wsgiref.rst:606 +msgid "" +"The default environment variables to be included in every request's WSGI " +"environment. By default, this is a copy of ``os.environ`` at the time that :" +"mod:`wsgiref.handlers` was imported, but subclasses can either create their " +"own at the class or instance level. Note that the dictionary should be " +"considered read-only, since the default value is shared between multiple " +"classes and instances." +msgstr "" + +#: ../Doc/library/wsgiref.rst:616 +msgid "" +"If the :attr:`origin_server` attribute is set, this attribute's value is " +"used to set the default ``SERVER_SOFTWARE`` WSGI environment variable, and " +"also to set a default ``Server:`` header in HTTP responses. It is ignored " +"for handlers (such as :class:`BaseCGIHandler` and :class:`CGIHandler`) that " +"are not HTTP origin servers." +msgstr "" + +#: ../Doc/library/wsgiref.rst:622 +msgid "" +"The term \"Python\" is replaced with implementation specific term like " +"\"CPython\", \"Jython\" etc." +msgstr "" + +#: ../Doc/library/wsgiref.rst:628 +msgid "" +"Return the URL scheme being used for the current request. The default " +"implementation uses the :func:`guess_scheme` function from :mod:`wsgiref." +"util` to guess whether the scheme should be \"http\" or \"https\", based on " +"the current request's :attr:`environ` variables." +msgstr "" + +#: ../Doc/library/wsgiref.rst:636 +msgid "" +"Set the :attr:`environ` attribute to a fully-populated WSGI environment. " +"The default implementation uses all of the above methods and attributes, " +"plus the :meth:`get_stdin`, :meth:`get_stderr`, and :meth:`add_cgi_vars` " +"methods and the :attr:`wsgi_file_wrapper` attribute. It also inserts a " +"``SERVER_SOFTWARE`` key if not present, as long as the :attr:`origin_server` " +"attribute is a true value and the :attr:`server_software` attribute is set." +msgstr "" + +#: ../Doc/library/wsgiref.rst:643 +msgid "Methods and attributes for customizing exception handling:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:648 +msgid "" +"Log the *exc_info* tuple in the server log. *exc_info* is a ``(type, value, " +"traceback)`` tuple. The default implementation simply writes the traceback " +"to the request's ``wsgi.errors`` stream and flushes it. Subclasses can " +"override this method to change the format or retarget the output, mail the " +"traceback to an administrator, or whatever other action may be deemed " +"suitable." +msgstr "" + +#: ../Doc/library/wsgiref.rst:657 +msgid "" +"The maximum number of frames to include in tracebacks output by the default :" +"meth:`log_exception` method. If ``None``, all frames are included." +msgstr "" + +#: ../Doc/library/wsgiref.rst:663 +msgid "" +"This method is a WSGI application to generate an error page for the user. " +"It is only invoked if an error occurs before headers are sent to the client." +msgstr "" + +#: ../Doc/library/wsgiref.rst:666 +msgid "" +"This method can access the current error information using ``sys." +"exc_info()``, and should pass that information to *start_response* when " +"calling it (as described in the \"Error Handling\" section of :pep:`3333`)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:670 +msgid "" +"The default implementation just uses the :attr:`error_status`, :attr:" +"`error_headers`, and :attr:`error_body` attributes to generate an output " +"page. Subclasses can override this to produce more dynamic error output." +msgstr "" + +#: ../Doc/library/wsgiref.rst:674 +msgid "" +"Note, however, that it's not recommended from a security perspective to spit " +"out diagnostics to any old user; ideally, you should have to do something " +"special to enable diagnostic output, which is why the default implementation " +"doesn't include any." +msgstr "" + +#: ../Doc/library/wsgiref.rst:682 +msgid "" +"The HTTP status used for error responses. This should be a status string as " +"defined in :pep:`3333`; it defaults to a 500 code and message." +msgstr "" + +#: ../Doc/library/wsgiref.rst:688 +msgid "" +"The HTTP headers used for error responses. This should be a list of WSGI " +"response headers (``(name, value)`` tuples), as described in :pep:`3333`. " +"The default list just sets the content type to ``text/plain``." +msgstr "" + +#: ../Doc/library/wsgiref.rst:695 +msgid "" +"The error response body. This should be an HTTP response body bytestring. " +"It defaults to the plain text, \"A server error occurred. Please contact " +"the administrator.\"" +msgstr "" + +#: ../Doc/library/wsgiref.rst:699 +msgid "" +"Methods and attributes for :pep:`3333`'s \"Optional Platform-Specific File " +"Handling\" feature:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:705 +msgid "" +"A ``wsgi.file_wrapper`` factory, or ``None``. The default value of this " +"attribute is the :class:`wsgiref.util.FileWrapper` class." +msgstr "" + +#: ../Doc/library/wsgiref.rst:711 +msgid "" +"Override to implement platform-specific file transmission. This method is " +"called only if the application's return value is an instance of the class " +"specified by the :attr:`wsgi_file_wrapper` attribute. It should return a " +"true value if it was able to successfully transmit the file, so that the " +"default transmission code will not be executed. The default implementation " +"of this method just returns a false value." +msgstr "" + +#: ../Doc/library/wsgiref.rst:718 +msgid "Miscellaneous methods and attributes:" +msgstr "" + +#: ../Doc/library/wsgiref.rst:723 +msgid "" +"This attribute should be set to a true value if the handler's :meth:`_write` " +"and :meth:`_flush` are being used to communicate directly to the client, " +"rather than via a CGI-like gateway protocol that wants the HTTP status in a " +"special ``Status:`` header." +msgstr "" + +#: ../Doc/library/wsgiref.rst:728 +msgid "" +"This attribute's default value is true in :class:`BaseHandler`, but false " +"in :class:`BaseCGIHandler` and :class:`CGIHandler`." +msgstr "" + +#: ../Doc/library/wsgiref.rst:734 +msgid "" +"If :attr:`origin_server` is true, this string attribute is used to set the " +"HTTP version of the response set to the client. It defaults to ``\"1.0\"``." +msgstr "" + +#: ../Doc/library/wsgiref.rst:740 +msgid "" +"Transcode CGI variables from ``os.environ`` to PEP 3333 \"bytes in unicode\" " +"strings, returning a new dictionary. This function is used by :class:" +"`CGIHandler` and :class:`IISCGIHandler` in place of directly using ``os." +"environ``, which is not necessarily WSGI-compliant on all platforms and web " +"servers using Python 3 -- specifically, ones where the OS's actual " +"environment is Unicode (i.e. Windows), or ones where the environment is " +"bytes, but the system encoding used by Python to decode it is anything other " +"than ISO-8859-1 (e.g. Unix systems using UTF-8)." +msgstr "" + +#: ../Doc/library/wsgiref.rst:749 +msgid "" +"If you are implementing a CGI-based handler of your own, you probably want " +"to use this routine instead of just copying values out of ``os.environ`` " +"directly." +msgstr "" + +#: ../Doc/library/wsgiref.rst:759 +msgid "This is a working \"Hello World\" WSGI application::" +msgstr "" + +#: ../Doc/library/xdrlib.rst:2 +msgid ":mod:`xdrlib` --- Encode and decode XDR data" +msgstr "" + +#: ../Doc/library/xdrlib.rst:7 +msgid "**Source code:** :source:`Lib/xdrlib.py`" +msgstr "" + +#: ../Doc/library/xdrlib.rst:15 +msgid "" +"The :mod:`xdrlib` module supports the External Data Representation Standard " +"as described in :rfc:`1014`, written by Sun Microsystems, Inc. June 1987. " +"It supports most of the data types described in the RFC." +msgstr "" + +#: ../Doc/library/xdrlib.rst:19 +msgid "" +"The :mod:`xdrlib` module defines two classes, one for packing variables into " +"XDR representation, and another for unpacking from XDR representation. " +"There are also two exception classes." +msgstr "" + +#: ../Doc/library/xdrlib.rst:26 +msgid "" +":class:`Packer` is the class for packing data into XDR representation. The :" +"class:`Packer` class is instantiated with no arguments." +msgstr "" + +#: ../Doc/library/xdrlib.rst:32 +msgid "" +"``Unpacker`` is the complementary class which unpacks XDR data values from a " +"string buffer. The input buffer is given as *data*." +msgstr "" + +#: ../Doc/library/xdrlib.rst:40 +msgid ":rfc:`1014` - XDR: External Data Representation Standard" +msgstr "" + +#: ../Doc/library/xdrlib.rst:39 +msgid "" +"This RFC defined the encoding of data which was XDR at the time this module " +"was originally written. It has apparently been obsoleted by :rfc:`1832`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:42 +msgid ":rfc:`1832` - XDR: External Data Representation Standard" +msgstr "" + +#: ../Doc/library/xdrlib.rst:43 +msgid "Newer RFC that provides a revised definition of XDR." +msgstr "" + +#: ../Doc/library/xdrlib.rst:49 +msgid "Packer Objects" +msgstr "" + +#: ../Doc/library/xdrlib.rst:51 +msgid ":class:`Packer` instances have the following methods:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:56 +msgid "Returns the current pack buffer as a string." +msgstr "" + +#: ../Doc/library/xdrlib.rst:61 +msgid "Resets the pack buffer to the empty string." +msgstr "" + +#: ../Doc/library/xdrlib.rst:63 +msgid "" +"In general, you can pack any of the most common XDR data types by calling " +"the appropriate ``pack_type()`` method. Each method takes a single " +"argument, the value to pack. The following simple data type packing methods " +"are supported: :meth:`pack_uint`, :meth:`pack_int`, :meth:`pack_enum`, :meth:" +"`pack_bool`, :meth:`pack_uhyper`, and :meth:`pack_hyper`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:72 +msgid "Packs the single-precision floating point number *value*." +msgstr "" + +#: ../Doc/library/xdrlib.rst:77 +msgid "Packs the double-precision floating point number *value*." +msgstr "" + +#: ../Doc/library/xdrlib.rst:79 +msgid "The following methods support packing strings, bytes, and opaque data:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:84 +msgid "" +"Packs a fixed length string, *s*. *n* is the length of the string but it is " +"*not* packed into the data buffer. The string is padded with null bytes if " +"necessary to guaranteed 4 byte alignment." +msgstr "" + +#: ../Doc/library/xdrlib.rst:91 +msgid "" +"Packs a fixed length opaque data stream, similarly to :meth:`pack_fstring`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:96 +msgid "" +"Packs a variable length string, *s*. The length of the string is first " +"packed as an unsigned integer, then the string data is packed with :meth:" +"`pack_fstring`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:103 +msgid "" +"Packs a variable length opaque data string, similarly to :meth:`pack_string`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:108 +msgid "Packs a variable length byte stream, similarly to :meth:`pack_string`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:110 +msgid "The following methods support packing arrays and lists:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:115 +msgid "" +"Packs a *list* of homogeneous items. This method is useful for lists with " +"an indeterminate size; i.e. the size is not available until the entire list " +"has been walked. For each item in the list, an unsigned integer ``1`` is " +"packed first, followed by the data value from the list. *pack_item* is the " +"function that is called to pack the individual item. At the end of the " +"list, an unsigned integer ``0`` is packed." +msgstr "" + +#: ../Doc/library/xdrlib.rst:122 +msgid "" +"For example, to pack a list of integers, the code might appear like this::" +msgstr "" + +#: ../Doc/library/xdrlib.rst:131 +msgid "" +"Packs a fixed length list (*array*) of homogeneous items. *n* is the length " +"of the list; it is *not* packed into the buffer, but a :exc:`ValueError` " +"exception is raised if ``len(array)`` is not equal to *n*. As above, " +"*pack_item* is the function used to pack each element." +msgstr "" + +#: ../Doc/library/xdrlib.rst:139 +msgid "" +"Packs a variable length *list* of homogeneous items. First, the length of " +"the list is packed as an unsigned integer, then each element is packed as " +"in :meth:`pack_farray` above." +msgstr "" + +#: ../Doc/library/xdrlib.rst:147 +msgid "Unpacker Objects" +msgstr "" + +#: ../Doc/library/xdrlib.rst:149 +msgid "The :class:`Unpacker` class offers the following methods:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:154 +msgid "Resets the string buffer with the given *data*." +msgstr "" + +#: ../Doc/library/xdrlib.rst:159 +msgid "Returns the current unpack position in the data buffer." +msgstr "" + +#: ../Doc/library/xdrlib.rst:164 +msgid "" +"Sets the data buffer unpack position to *position*. You should be careful " +"about using :meth:`get_position` and :meth:`set_position`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:170 +msgid "Returns the current unpack data buffer as a string." +msgstr "" + +#: ../Doc/library/xdrlib.rst:175 +msgid "" +"Indicates unpack completion. Raises an :exc:`Error` exception if all of the " +"data has not been unpacked." +msgstr "" + +#: ../Doc/library/xdrlib.rst:178 +msgid "" +"In addition, every data type that can be packed with a :class:`Packer`, can " +"be unpacked with an :class:`Unpacker`. Unpacking methods are of the form " +"``unpack_type()``, and take no arguments. They return the unpacked object." +msgstr "" + +#: ../Doc/library/xdrlib.rst:185 +msgid "Unpacks a single-precision floating point number." +msgstr "" + +#: ../Doc/library/xdrlib.rst:190 +msgid "" +"Unpacks a double-precision floating point number, similarly to :meth:" +"`unpack_float`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:193 +msgid "" +"In addition, the following methods unpack strings, bytes, and opaque data:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:198 +msgid "" +"Unpacks and returns a fixed length string. *n* is the number of characters " +"expected. Padding with null bytes to guaranteed 4 byte alignment is assumed." +msgstr "" + +#: ../Doc/library/xdrlib.rst:204 +msgid "" +"Unpacks and returns a fixed length opaque data stream, similarly to :meth:" +"`unpack_fstring`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:210 +msgid "" +"Unpacks and returns a variable length string. The length of the string is " +"first unpacked as an unsigned integer, then the string data is unpacked " +"with :meth:`unpack_fstring`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:217 +msgid "" +"Unpacks and returns a variable length opaque data string, similarly to :meth:" +"`unpack_string`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:223 +msgid "" +"Unpacks and returns a variable length byte stream, similarly to :meth:" +"`unpack_string`." +msgstr "" + +#: ../Doc/library/xdrlib.rst:226 +msgid "The following methods support unpacking arrays and lists:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:231 +msgid "" +"Unpacks and returns a list of homogeneous items. The list is unpacked one " +"element at a time by first unpacking an unsigned integer flag. If the flag " +"is ``1``, then the item is unpacked and appended to the list. A flag of " +"``0`` indicates the end of the list. *unpack_item* is the function that is " +"called to unpack the items." +msgstr "" + +#: ../Doc/library/xdrlib.rst:240 +msgid "" +"Unpacks and returns (as a list) a fixed length array of homogeneous items. " +"*n* is number of list elements to expect in the buffer. As above, " +"*unpack_item* is the function used to unpack each element." +msgstr "" + +#: ../Doc/library/xdrlib.rst:247 +msgid "" +"Unpacks and returns a variable length *list* of homogeneous items. First, " +"the length of the list is unpacked as an unsigned integer, then each element " +"is unpacked as in :meth:`unpack_farray` above." +msgstr "" + +#: ../Doc/library/xdrlib.rst:257 +msgid "Exceptions in this module are coded as class instances:" +msgstr "" + +#: ../Doc/library/xdrlib.rst:262 +msgid "" +"The base exception class. :exc:`Error` has a single public attribute :attr:" +"`msg` containing the description of the error." +msgstr "" + +#: ../Doc/library/xdrlib.rst:268 +msgid "" +"Class derived from :exc:`Error`. Contains no additional instance variables." +msgstr "" + +#: ../Doc/library/xdrlib.rst:270 +msgid "Here is an example of how you would catch one of these exceptions::" +msgstr "" + +#: ../Doc/library/xml.rst:4 +msgid "XML Processing Modules" +msgstr "" + +#: ../Doc/library/xml.rst:12 +msgid "**Source code:** :source:`Lib/xml/`" +msgstr "" + +#: ../Doc/library/xml.rst:16 +msgid "" +"Python's interfaces for processing XML are grouped in the ``xml`` package." +msgstr "" + +#: ../Doc/library/xml.rst:20 +msgid "" +"The XML modules are not secure against erroneous or maliciously constructed " +"data. If you need to parse untrusted or unauthenticated data see the :ref:" +"`xml-vulnerabilities` and :ref:`defused-packages` sections." +msgstr "" + +#: ../Doc/library/xml.rst:25 +msgid "" +"It is important to note that modules in the :mod:`xml` package require that " +"there be at least one SAX-compliant XML parser available. The Expat parser " +"is included with Python, so the :mod:`xml.parsers.expat` module will always " +"be available." +msgstr "" + +#: ../Doc/library/xml.rst:30 +msgid "" +"The documentation for the :mod:`xml.dom` and :mod:`xml.sax` packages are the " +"definition of the Python bindings for the DOM and SAX interfaces." +msgstr "" + +#: ../Doc/library/xml.rst:33 +msgid "The XML handling submodules are:" +msgstr "" + +#: ../Doc/library/xml.rst:35 +msgid "" +":mod:`xml.etree.ElementTree`: the ElementTree API, a simple and lightweight " +"XML processor" +msgstr "" + +#: ../Doc/library/xml.rst:40 +msgid ":mod:`xml.dom`: the DOM API definition" +msgstr "" + +#: ../Doc/library/xml.rst:41 +msgid ":mod:`xml.dom.minidom`: a minimal DOM implementation" +msgstr "" + +#: ../Doc/library/xml.rst:42 +msgid ":mod:`xml.dom.pulldom`: support for building partial DOM trees" +msgstr "" + +#: ../Doc/library/xml.rst:46 +msgid ":mod:`xml.sax`: SAX2 base classes and convenience functions" +msgstr "" + +#: ../Doc/library/xml.rst:47 +msgid ":mod:`xml.parsers.expat`: the Expat parser binding" +msgstr "" + +#: ../Doc/library/xml.rst:53 +msgid "XML vulnerabilities" +msgstr "" + +#: ../Doc/library/xml.rst:55 +msgid "" +"The XML processing modules are not secure against maliciously constructed " +"data. An attacker can abuse XML features to carry out denial of service " +"attacks, access local files, generate network connections to other machines, " +"or circumvent firewalls." +msgstr "" + +#: ../Doc/library/xml.rst:60 +msgid "" +"The following table gives an overview of the known attacks and whether the " +"various modules are vulnerable to them." +msgstr "" + +#: ../Doc/library/xml.rst:64 +msgid "kind" +msgstr "" + +#: ../Doc/library/xml.rst:64 +msgid "sax" +msgstr "" + +#: ../Doc/library/xml.rst:64 +msgid "etree" +msgstr "" + +#: ../Doc/library/xml.rst:64 +msgid "minidom" +msgstr "" + +#: ../Doc/library/xml.rst:64 +msgid "pulldom" +msgstr "" + +#: ../Doc/library/xml.rst:64 +msgid "xmlrpc" +msgstr "" + +#: ../Doc/library/xml.rst:66 +msgid "billion laughs" +msgstr "" + +#: ../Doc/library/xml.rst:66 ../Doc/library/xml.rst:67 +#: ../Doc/library/xml.rst:68 ../Doc/library/xml.rst:69 +#: ../Doc/library/xml.rst:70 +msgid "**Vulnerable**" +msgstr "" + +#: ../Doc/library/xml.rst:67 +msgid "quadratic blowup" +msgstr "" + +#: ../Doc/library/xml.rst:68 ../Doc/library/xml.rst:97 +msgid "external entity expansion" +msgstr "" + +#: ../Doc/library/xml.rst:68 +msgid "Safe (1)" +msgstr "" + +#: ../Doc/library/xml.rst:68 +msgid "Safe (2)" +msgstr "" + +#: ../Doc/library/xml.rst:68 +msgid "Safe (3)" +msgstr "" + +#: ../Doc/library/xml.rst:69 ../Doc/library/xml.rst:102 +msgid "`DTD`_ retrieval" +msgstr "" + +#: ../Doc/library/xml.rst:69 ../Doc/library/xml.rst:70 +msgid "Safe" +msgstr "" + +#: ../Doc/library/xml.rst:70 ../Doc/library/xml.rst:109 +msgid "decompression bomb" +msgstr "" + +#: ../Doc/library/xml.rst:73 +msgid "" +":mod:`xml.etree.ElementTree` doesn't expand external entities and raises a :" +"exc:`ParserError` when an entity occurs." +msgstr "" + +#: ../Doc/library/xml.rst:75 +msgid "" +":mod:`xml.dom.minidom` doesn't expand external entities and simply returns " +"the unexpanded entity verbatim." +msgstr "" + +#: ../Doc/library/xml.rst:77 +msgid ":mod:`xmlrpclib` doesn't expand external entities and omits them." +msgstr "" + +#: ../Doc/library/xml.rst:85 +msgid "billion laughs / exponential entity expansion" +msgstr "" + +#: ../Doc/library/xml.rst:81 +msgid "" +"The `Billion Laughs`_ attack -- also known as exponential entity expansion " +"-- uses multiple levels of nested entities. Each entity refers to another " +"entity several times, and the final entity definition contains a small " +"string. The exponential expansion results in several gigabytes of text and " +"consumes lots of memory and CPU time." +msgstr "" + +#: ../Doc/library/xml.rst:92 +msgid "quadratic blowup entity expansion" +msgstr "" + +#: ../Doc/library/xml.rst:88 +msgid "" +"A quadratic blowup attack is similar to a `Billion Laughs`_ attack; it " +"abuses entity expansion, too. Instead of nested entities it repeats one " +"large entity with a couple of thousand chars over and over again. The attack " +"isn't as efficient as the exponential case but it avoids triggering parser " +"countermeasures that forbid deeply-nested entities." +msgstr "" + +#: ../Doc/library/xml.rst:95 +msgid "" +"Entity declarations can contain more than just text for replacement. They " +"can also point to external resources or local files. The XML parser accesses " +"the resource and embeds the content into the XML document." +msgstr "" + +#: ../Doc/library/xml.rst:100 +msgid "" +"Some XML libraries like Python's :mod:`xml.dom.pulldom` retrieve document " +"type definitions from remote or local locations. The feature has similar " +"implications as the external entity expansion issue." +msgstr "" + +#: ../Doc/library/xml.rst:105 +msgid "" +"Decompression bombs (aka `ZIP bomb`_) apply to all XML libraries that can " +"parse compressed XML streams such as gzipped HTTP streams or LZMA-compressed " +"files. For an attacker it can reduce the amount of transmitted data by three " +"magnitudes or more." +msgstr "" + +#: ../Doc/library/xml.rst:111 +msgid "" +"The documentation for `defusedxml`_ on PyPI has further information about " +"all known attack vectors with examples and references." +msgstr "" + +#: ../Doc/library/xml.rst:117 +msgid "The :mod:`defusedxml` and :mod:`defusedexpat` Packages" +msgstr "" + +#: ../Doc/library/xml.rst:119 +msgid "" +"`defusedxml`_ is a pure Python package with modified subclasses of all " +"stdlib XML parsers that prevent any potentially malicious operation. Use of " +"this package is recommended for any server code that parses untrusted XML " +"data. The package also ships with example exploits and extended " +"documentation on more XML exploits such as XPath injection." +msgstr "" + +#: ../Doc/library/xml.rst:125 +msgid "" +"`defusedexpat`_ provides a modified libexpat and a patched :mod:`pyexpat` " +"module that have countermeasures against entity expansion DoS attacks. The :" +"mod:`defusedexpat` module still allows a sane and configurable amount of " +"entity expansions. The modifications may be included in some future release " +"of Python, but will not be included in any bugfix releases of Python because " +"they break backward compatibility." +msgstr "" + +#: ../Doc/library/xml.dom.rst:2 +msgid ":mod:`xml.dom` --- The Document Object Model API" +msgstr "" + +#: ../Doc/library/xml.dom.rst:10 +msgid "**Source code:** :source:`Lib/xml/dom/__init__.py`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:14 +msgid "" +"The Document Object Model, or \"DOM,\" is a cross-language API from the " +"World Wide Web Consortium (W3C) for accessing and modifying XML documents. " +"A DOM implementation presents an XML document as a tree structure, or allows " +"client code to build such a structure from scratch. It then gives access to " +"the structure through a set of objects which provided well-known interfaces." +msgstr "" + +#: ../Doc/library/xml.dom.rst:20 +msgid "" +"The DOM is extremely useful for random-access applications. SAX only allows " +"you a view of one bit of the document at a time. If you are looking at one " +"SAX element, you have no access to another. If you are looking at a text " +"node, you have no access to a containing element. When you write a SAX " +"application, you need to keep track of your program's position in the " +"document somewhere in your own code. SAX does not do it for you. Also, if " +"you need to look ahead in the XML document, you are just out of luck." +msgstr "" + +#: ../Doc/library/xml.dom.rst:28 +msgid "" +"Some applications are simply impossible in an event driven model with no " +"access to a tree. Of course you could build some sort of tree yourself in " +"SAX events, but the DOM allows you to avoid writing that code. The DOM is a " +"standard tree representation for XML data." +msgstr "" + +#: ../Doc/library/xml.dom.rst:33 +msgid "" +"The Document Object Model is being defined by the W3C in stages, or \"levels" +"\" in their terminology. The Python mapping of the API is substantially " +"based on the DOM Level 2 recommendation." +msgstr "" + +#: ../Doc/library/xml.dom.rst:45 +msgid "" +"DOM applications typically start by parsing some XML into a DOM. How this " +"is accomplished is not covered at all by DOM Level 1, and Level 2 provides " +"only limited improvements: There is a :class:`DOMImplementation` object " +"class which provides access to :class:`Document` creation methods, but no " +"way to access an XML reader/parser/Document builder in an implementation-" +"independent way. There is also no well-defined way to access these methods " +"without an existing :class:`Document` object. In Python, each DOM " +"implementation will provide a function :func:`getDOMImplementation`. DOM " +"Level 3 adds a Load/Store specification, which defines an interface to the " +"reader, but this is not yet available in the Python standard library." +msgstr "" + +#: ../Doc/library/xml.dom.rst:56 +msgid "" +"Once you have a DOM document object, you can access the parts of your XML " +"document through its properties and methods. These properties are defined " +"in the DOM specification; this portion of the reference manual describes the " +"interpretation of the specification in Python." +msgstr "" + +#: ../Doc/library/xml.dom.rst:61 +msgid "" +"The specification provided by the W3C defines the DOM API for Java, " +"ECMAScript, and OMG IDL. The Python mapping defined here is based in large " +"part on the IDL version of the specification, but strict compliance is not " +"required (though implementations are free to support the strict mapping from " +"IDL). See section :ref:`dom-conformance` for a detailed discussion of " +"mapping requirements." +msgstr "" + +#: ../Doc/library/xml.dom.rst:71 +msgid "" +"`Document Object Model (DOM) Level 2 Specification `_" +msgstr "" + +#: ../Doc/library/xml.dom.rst:71 +msgid "The W3C recommendation upon which the Python DOM API is based." +msgstr "" + +#: ../Doc/library/xml.dom.rst:74 ../Doc/library/xml.dom.minidom.rst:104 +msgid "" +"`Document Object Model (DOM) Level 1 Specification `_" +msgstr "" + +#: ../Doc/library/xml.dom.rst:74 ../Doc/library/xml.dom.minidom.rst:105 +msgid "The W3C recommendation for the DOM supported by :mod:`xml.dom.minidom`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:76 +msgid "" +"`Python Language Mapping Specification `_" +msgstr "" + +#: ../Doc/library/xml.dom.rst:77 +msgid "This specifies the mapping from OMG IDL to Python." +msgstr "" + +#: ../Doc/library/xml.dom.rst:83 +msgid "The :mod:`xml.dom` contains the following functions:" +msgstr "" + +#: ../Doc/library/xml.dom.rst:88 +msgid "" +"Register the *factory* function with the name *name*. The factory function " +"should return an object which implements the :class:`DOMImplementation` " +"interface. The factory function can return the same object every time, or a " +"new one for each call, as appropriate for the specific implementation (e.g. " +"if that implementation supports some customization)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:97 +msgid "" +"Return a suitable DOM implementation. The *name* is either well-known, the " +"module name of a DOM implementation, or ``None``. If it is not ``None``, " +"imports the corresponding module and returns a :class:`DOMImplementation` " +"object if the import succeeds. If no name is given, and if the environment " +"variable :envvar:`PYTHON_DOM` is set, this variable is used to find the " +"implementation." +msgstr "" + +#: ../Doc/library/xml.dom.rst:103 +msgid "" +"If name is not given, this examines the available implementations to find " +"one with the required feature set. If no implementation can be found, raise " +"an :exc:`ImportError`. The features list must be a sequence of ``(feature, " +"version)`` pairs which are passed to the :meth:`hasFeature` method on " +"available :class:`DOMImplementation` objects." +msgstr "" + +#: ../Doc/library/xml.dom.rst:109 +msgid "Some convenience constants are also provided:" +msgstr "" + +#: ../Doc/library/xml.dom.rst:114 +msgid "" +"The value used to indicate that no namespace is associated with a node in " +"the DOM. This is typically found as the :attr:`namespaceURI` of a node, or " +"used as the *namespaceURI* parameter to a namespaces-specific method." +msgstr "" + +#: ../Doc/library/xml.dom.rst:121 +msgid "" +"The namespace URI associated with the reserved prefix ``xml``, as defined by " +"`Namespaces in XML `_ (section 4)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:127 +msgid "" +"The namespace URI for namespace declarations, as defined by `Document Object " +"Model (DOM) Level 2 Core Specification `_ (section 1.1.8)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:134 +msgid "" +"The URI of the XHTML namespace as defined by `XHTML 1.0: The Extensible " +"HyperText Markup Language `_ (section 3.1.1)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:138 +msgid "" +"In addition, :mod:`xml.dom` contains a base :class:`Node` class and the DOM " +"exception classes. The :class:`Node` class provided by this module does not " +"implement any of the methods or attributes defined by the DOM specification; " +"concrete DOM implementations must provide those. The :class:`Node` class " +"provided as part of this module does provide the constants used for the :" +"attr:`nodeType` attribute on concrete :class:`Node` objects; they are " +"located within the class rather than at the module level to conform with the " +"DOM specifications." +msgstr "" + +#: ../Doc/library/xml.dom.rst:153 +msgid "Objects in the DOM" +msgstr "" + +#: ../Doc/library/xml.dom.rst:155 +msgid "" +"The definitive documentation for the DOM is the DOM specification from the " +"W3C." +msgstr "" + +#: ../Doc/library/xml.dom.rst:157 +msgid "" +"Note that DOM attributes may also be manipulated as nodes instead of as " +"simple strings. It is fairly rare that you must do this, however, so this " +"usage is not yet documented." +msgstr "" + +#: ../Doc/library/xml.dom.rst:162 +msgid "Interface" +msgstr "" + +#: ../Doc/library/xml.dom.rst:162 +msgid "Section" +msgstr "" + +#: ../Doc/library/xml.dom.rst:164 ../Doc/library/xml.dom.minidom.rst:232 +msgid ":class:`DOMImplementation`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:164 +msgid ":ref:`dom-implementation-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:164 +msgid "Interface to the underlying implementation." +msgstr "" + +#: ../Doc/library/xml.dom.rst:167 +msgid ":class:`Node`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:167 +msgid ":ref:`dom-node-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:167 +msgid "Base interface for most objects in a document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:170 +msgid ":class:`NodeList`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:170 +msgid ":ref:`dom-nodelist-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:170 +msgid "Interface for a sequence of nodes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:173 ../Doc/library/xml.dom.minidom.rst:230 +msgid ":class:`DocumentType`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:173 +msgid ":ref:`dom-documenttype-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:173 +msgid "Information about the declarations needed to process a document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:177 +msgid ":class:`Document`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:177 +msgid ":ref:`dom-document-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:177 +msgid "Object which represents an entire document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:180 +msgid ":class:`Element`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:180 +msgid ":ref:`dom-element-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:180 +msgid "Element nodes in the document hierarchy." +msgstr "" + +#: ../Doc/library/xml.dom.rst:183 +msgid ":class:`Attr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:183 +msgid ":ref:`dom-attr-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:183 +msgid "Attribute value nodes on element nodes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:186 +msgid ":class:`Comment`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:186 +msgid ":ref:`dom-comment-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:186 +msgid "Representation of comments in the source document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:189 +msgid ":class:`Text`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:189 +msgid ":ref:`dom-text-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:189 +msgid "Nodes containing textual content from the document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:192 +msgid ":class:`ProcessingInstruction`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:192 +msgid ":ref:`dom-pi-objects`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:192 +msgid "Processing instruction representation." +msgstr "" + +#: ../Doc/library/xml.dom.rst:196 +msgid "" +"An additional section describes the exceptions defined for working with the " +"DOM in Python." +msgstr "" + +#: ../Doc/library/xml.dom.rst:203 +msgid "DOMImplementation Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:205 +msgid "" +"The :class:`DOMImplementation` interface provides a way for applications to " +"determine the availability of particular features in the DOM they are using. " +"DOM Level 2 added the ability to create new :class:`Document` and :class:" +"`DocumentType` objects using the :class:`DOMImplementation` as well." +msgstr "" + +#: ../Doc/library/xml.dom.rst:213 +msgid "" +"Return true if the feature identified by the pair of strings *feature* and " +"*version* is implemented." +msgstr "" + +#: ../Doc/library/xml.dom.rst:219 +msgid "" +"Return a new :class:`Document` object (the root of the DOM), with a child :" +"class:`Element` object having the given *namespaceUri* and *qualifiedName*. " +"The *doctype* must be a :class:`DocumentType` object created by :meth:" +"`createDocumentType`, or ``None``. In the Python DOM API, the first two " +"arguments can also be ``None`` in order to indicate that no :class:`Element` " +"child is to be created." +msgstr "" + +#: ../Doc/library/xml.dom.rst:229 +msgid "" +"Return a new :class:`DocumentType` object that encapsulates the given " +"*qualifiedName*, *publicId*, and *systemId* strings, representing the " +"information contained in an XML document type declaration." +msgstr "" + +#: ../Doc/library/xml.dom.rst:237 +msgid "Node Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:239 +msgid "" +"All of the components of an XML document are subclasses of :class:`Node`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:244 +msgid "" +"An integer representing the node type. Symbolic constants for the types are " +"on the :class:`Node` object: :const:`ELEMENT_NODE`, :const:" +"`ATTRIBUTE_NODE`, :const:`TEXT_NODE`, :const:`CDATA_SECTION_NODE`, :const:" +"`ENTITY_NODE`, :const:`PROCESSING_INSTRUCTION_NODE`, :const:`COMMENT_NODE`, :" +"const:`DOCUMENT_NODE`, :const:`DOCUMENT_TYPE_NODE`, :const:`NOTATION_NODE`. " +"This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:254 +msgid "" +"The parent of the current node, or ``None`` for the document node. The value " +"is always a :class:`Node` object or ``None``. For :class:`Element` nodes, " +"this will be the parent element, except for the root element, in which case " +"it will be the :class:`Document` object. For :class:`Attr` nodes, this is " +"always ``None``. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:263 +msgid "" +"A :class:`NamedNodeMap` of attribute objects. Only elements have actual " +"values for this; others provide ``None`` for this attribute. This is a read-" +"only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:270 +msgid "" +"The node that immediately precedes this one with the same parent. For " +"instance the element with an end-tag that comes just before the *self* " +"element's start-tag. Of course, XML documents are made up of more than just " +"elements so the previous sibling could be text, a comment, or something " +"else. If this node is the first child of the parent, this attribute will be " +"``None``. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:280 +msgid "" +"The node that immediately follows this one with the same parent. See also :" +"attr:`previousSibling`. If this is the last child of the parent, this " +"attribute will be ``None``. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:287 +msgid "" +"A list of nodes contained within this node. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:292 +msgid "" +"The first child of the node, if there are any, or ``None``. This is a read-" +"only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:298 +msgid "" +"The last child of the node, if there are any, or ``None``. This is a read-" +"only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:304 +msgid "" +"The part of the :attr:`tagName` following the colon if there is one, else " +"the entire :attr:`tagName`. The value is a string." +msgstr "" + +#: ../Doc/library/xml.dom.rst:310 +msgid "" +"The part of the :attr:`tagName` preceding the colon if there is one, else " +"the empty string. The value is a string, or ``None``." +msgstr "" + +#: ../Doc/library/xml.dom.rst:316 +msgid "" +"The namespace associated with the element name. This will be a string or " +"``None``. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:322 +msgid "" +"This has a different meaning for each node type; see the DOM specification " +"for details. You can always get the information you would get here from " +"another property such as the :attr:`tagName` property for elements or the :" +"attr:`name` property for attributes. For all node types, the value of this " +"attribute will be either a string or ``None``. This is a read-only " +"attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:331 +msgid "" +"This has a different meaning for each node type; see the DOM specification " +"for details. The situation is similar to that with :attr:`nodeName`. The " +"value is a string or ``None``." +msgstr "" + +#: ../Doc/library/xml.dom.rst:338 +msgid "Returns true if the node has any attributes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:343 +msgid "Returns true if the node has any child nodes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:348 +msgid "" +"Returns true if *other* refers to the same node as this node. This is " +"especially useful for DOM implementations which use any sort of proxy " +"architecture (because more than one object can refer to the same node)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:354 +msgid "" +"This is based on a proposed DOM Level 3 API which is still in the \"working " +"draft\" stage, but this particular interface appears uncontroversial. " +"Changes from the W3C will not necessarily affect this method in the Python " +"DOM interface (though any new W3C API for this would also be supported)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:362 +msgid "" +"Add a new child node to this node at the end of the list of children, " +"returning *newChild*. If the node was already in the tree, it is removed " +"first." +msgstr "" + +#: ../Doc/library/xml.dom.rst:369 +msgid "" +"Insert a new child node before an existing child. It must be the case that " +"*refChild* is a child of this node; if not, :exc:`ValueError` is raised. " +"*newChild* is returned. If *refChild* is ``None``, it inserts *newChild* at " +"the end of the children's list." +msgstr "" + +#: ../Doc/library/xml.dom.rst:377 +msgid "" +"Remove a child node. *oldChild* must be a child of this node; if not, :exc:" +"`ValueError` is raised. *oldChild* is returned on success. If *oldChild* " +"will not be used further, its :meth:`unlink` method should be called." +msgstr "" + +#: ../Doc/library/xml.dom.rst:384 +msgid "" +"Replace an existing node with a new node. It must be the case that " +"*oldChild* is a child of this node; if not, :exc:`ValueError` is raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:390 +msgid "" +"Join adjacent text nodes so that all stretches of text are stored as single :" +"class:`Text` instances. This simplifies processing text from a DOM tree for " +"many applications." +msgstr "" + +#: ../Doc/library/xml.dom.rst:397 +msgid "" +"Clone this node. Setting *deep* means to clone all child nodes as well. " +"This returns the clone." +msgstr "" + +#: ../Doc/library/xml.dom.rst:404 +msgid "NodeList Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:406 +msgid "" +"A :class:`NodeList` represents a sequence of nodes. These objects are used " +"in two ways in the DOM Core recommendation: an :class:`Element` object " +"provides one as its list of child nodes, and the :meth:" +"`getElementsByTagName` and :meth:`getElementsByTagNameNS` methods of :class:" +"`Node` return objects with this interface to represent query results." +msgstr "" + +#: ../Doc/library/xml.dom.rst:412 +msgid "" +"The DOM Level 2 recommendation defines one method and one attribute for " +"these objects:" +msgstr "" + +#: ../Doc/library/xml.dom.rst:418 +msgid "" +"Return the *i*'th item from the sequence, if there is one, or ``None``. The " +"index *i* is not allowed to be less than zero or greater than or equal to " +"the length of the sequence." +msgstr "" + +#: ../Doc/library/xml.dom.rst:425 +msgid "The number of nodes in the sequence." +msgstr "" + +#: ../Doc/library/xml.dom.rst:427 +msgid "" +"In addition, the Python DOM interface requires that some additional support " +"is provided to allow :class:`NodeList` objects to be used as Python " +"sequences. All :class:`NodeList` implementations must include support for :" +"meth:`~object.__len__` and :meth:`~object.__getitem__`; this allows " +"iteration over the :class:`NodeList` in :keyword:`for` statements and proper " +"support for the :func:`len` built-in function." +msgstr "" + +#: ../Doc/library/xml.dom.rst:435 +msgid "" +"If a DOM implementation supports modification of the document, the :class:" +"`NodeList` implementation must also support the :meth:`~object.__setitem__` " +"and :meth:`~object.__delitem__` methods." +msgstr "" + +#: ../Doc/library/xml.dom.rst:443 +msgid "DocumentType Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:445 +msgid "" +"Information about the notations and entities declared by a document " +"(including the external subset if the parser uses it and can provide the " +"information) is available from a :class:`DocumentType` object. The :class:" +"`DocumentType` for a document is available from the :class:`Document` " +"object's :attr:`doctype` attribute; if there is no ``DOCTYPE`` declaration " +"for the document, the document's :attr:`doctype` attribute will be set to " +"``None`` instead of an instance of this interface." +msgstr "" + +#: ../Doc/library/xml.dom.rst:453 +msgid "" +":class:`DocumentType` is a specialization of :class:`Node`, and adds the " +"following attributes:" +msgstr "" + +#: ../Doc/library/xml.dom.rst:459 +msgid "" +"The public identifier for the external subset of the document type " +"definition. This will be a string or ``None``." +msgstr "" + +#: ../Doc/library/xml.dom.rst:465 +msgid "" +"The system identifier for the external subset of the document type " +"definition. This will be a URI as a string, or ``None``." +msgstr "" + +#: ../Doc/library/xml.dom.rst:471 +msgid "" +"A string giving the complete internal subset from the document. This does " +"not include the brackets which enclose the subset. If the document has no " +"internal subset, this should be ``None``." +msgstr "" + +#: ../Doc/library/xml.dom.rst:478 +msgid "" +"The name of the root element as given in the ``DOCTYPE`` declaration, if " +"present." +msgstr "" + +#: ../Doc/library/xml.dom.rst:484 +msgid "" +"This is a :class:`NamedNodeMap` giving the definitions of external entities. " +"For entity names defined more than once, only the first definition is " +"provided (others are ignored as required by the XML recommendation). This " +"may be ``None`` if the information is not provided by the parser, or if no " +"entities are defined." +msgstr "" + +#: ../Doc/library/xml.dom.rst:493 +msgid "" +"This is a :class:`NamedNodeMap` giving the definitions of notations. For " +"notation names defined more than once, only the first definition is provided " +"(others are ignored as required by the XML recommendation). This may be " +"``None`` if the information is not provided by the parser, or if no " +"notations are defined." +msgstr "" + +#: ../Doc/library/xml.dom.rst:503 +msgid "Document Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:505 +msgid "" +"A :class:`Document` represents an entire XML document, including its " +"constituent elements, attributes, processing instructions, comments etc. " +"Remember that it inherits properties from :class:`Node`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:512 +msgid "The one and only root element of the document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:517 +msgid "" +"Create and return a new element node. The element is not inserted into the " +"document when it is created. You need to explicitly insert it with one of " +"the other methods such as :meth:`insertBefore` or :meth:`appendChild`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:524 +msgid "" +"Create and return a new element with a namespace. The *tagName* may have a " +"prefix. The element is not inserted into the document when it is created. " +"You need to explicitly insert it with one of the other methods such as :meth:" +"`insertBefore` or :meth:`appendChild`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:532 +msgid "" +"Create and return a text node containing the data passed as a parameter. As " +"with the other creation methods, this one does not insert the node into the " +"tree." +msgstr "" + +#: ../Doc/library/xml.dom.rst:539 +msgid "" +"Create and return a comment node containing the data passed as a parameter. " +"As with the other creation methods, this one does not insert the node into " +"the tree." +msgstr "" + +#: ../Doc/library/xml.dom.rst:546 +msgid "" +"Create and return a processing instruction node containing the *target* and " +"*data* passed as parameters. As with the other creation methods, this one " +"does not insert the node into the tree." +msgstr "" + +#: ../Doc/library/xml.dom.rst:553 +msgid "" +"Create and return an attribute node. This method does not associate the " +"attribute node with any particular element. You must use :meth:" +"`setAttributeNode` on the appropriate :class:`Element` object to use the " +"newly created attribute instance." +msgstr "" + +#: ../Doc/library/xml.dom.rst:561 +msgid "" +"Create and return an attribute node with a namespace. The *tagName* may " +"have a prefix. This method does not associate the attribute node with any " +"particular element. You must use :meth:`setAttributeNode` on the " +"appropriate :class:`Element` object to use the newly created attribute " +"instance." +msgstr "" + +#: ../Doc/library/xml.dom.rst:569 +msgid "" +"Search for all descendants (direct children, children's children, etc.) with " +"a particular element type name." +msgstr "" + +#: ../Doc/library/xml.dom.rst:575 +msgid "" +"Search for all descendants (direct children, children's children, etc.) with " +"a particular namespace URI and localname. The localname is the part of the " +"namespace after the prefix." +msgstr "" + +#: ../Doc/library/xml.dom.rst:583 ../Doc/library/xml.etree.elementtree.rst:639 +msgid "Element Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:585 +msgid "" +":class:`Element` is a subclass of :class:`Node`, so inherits all the " +"attributes of that class." +msgstr "" + +#: ../Doc/library/xml.dom.rst:591 +msgid "" +"The element type name. In a namespace-using document it may have colons in " +"it. The value is a string." +msgstr "" + +#: ../Doc/library/xml.dom.rst:597 ../Doc/library/xml.dom.rst:602 +msgid "Same as equivalent method in the :class:`Document` class." +msgstr "" + +#: ../Doc/library/xml.dom.rst:607 +msgid "Returns true if the element has an attribute named by *name*." +msgstr "" + +#: ../Doc/library/xml.dom.rst:612 +msgid "" +"Returns true if the element has an attribute named by *namespaceURI* and " +"*localName*." +msgstr "" + +#: ../Doc/library/xml.dom.rst:618 +msgid "" +"Return the value of the attribute named by *name* as a string. If no such " +"attribute exists, an empty string is returned, as if the attribute had no " +"value." +msgstr "" + +#: ../Doc/library/xml.dom.rst:624 +msgid "Return the :class:`Attr` node for the attribute named by *attrname*." +msgstr "" + +#: ../Doc/library/xml.dom.rst:629 +msgid "" +"Return the value of the attribute named by *namespaceURI* and *localName* as " +"a string. If no such attribute exists, an empty string is returned, as if " +"the attribute had no value." +msgstr "" + +#: ../Doc/library/xml.dom.rst:636 +msgid "" +"Return an attribute value as a node, given a *namespaceURI* and *localName*." +msgstr "" + +#: ../Doc/library/xml.dom.rst:641 +msgid "" +"Remove an attribute by name. If there is no matching attribute, a :exc:" +"`NotFoundErr` is raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:647 +msgid "" +"Remove and return *oldAttr* from the attribute list, if present. If " +"*oldAttr* is not present, :exc:`NotFoundErr` is raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:653 +msgid "" +"Remove an attribute by name. Note that it uses a localName, not a qname. " +"No exception is raised if there is no matching attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:659 +msgid "Set an attribute value from a string." +msgstr "" + +#: ../Doc/library/xml.dom.rst:664 +msgid "" +"Add a new attribute node to the element, replacing an existing attribute if " +"necessary if the :attr:`name` attribute matches. If a replacement occurs, " +"the old attribute node will be returned. If *newAttr* is already in use, :" +"exc:`InuseAttributeErr` will be raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:672 +msgid "" +"Add a new attribute node to the element, replacing an existing attribute if " +"necessary if the :attr:`namespaceURI` and :attr:`localName` attributes " +"match. If a replacement occurs, the old attribute node will be returned. If " +"*newAttr* is already in use, :exc:`InuseAttributeErr` will be raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:680 +msgid "" +"Set an attribute value from a string, given a *namespaceURI* and a *qname*. " +"Note that a qname is the whole attribute name. This is different than above." +msgstr "" + +#: ../Doc/library/xml.dom.rst:687 +msgid "Attr Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:689 +msgid "" +":class:`Attr` inherits from :class:`Node`, so inherits all its attributes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:694 +msgid "" +"The attribute name. In a namespace-using document it may include a colon." +msgstr "" + +#: ../Doc/library/xml.dom.rst:700 +msgid "" +"The part of the name following the colon if there is one, else the entire " +"name. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:707 +msgid "" +"The part of the name preceding the colon if there is one, else the empty " +"string." +msgstr "" + +#: ../Doc/library/xml.dom.rst:713 +msgid "" +"The text value of the attribute. This is a synonym for the :attr:" +"`nodeValue` attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:720 +msgid "NamedNodeMap Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:722 +msgid ":class:`NamedNodeMap` does *not* inherit from :class:`Node`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:727 +msgid "The length of the attribute list." +msgstr "" + +#: ../Doc/library/xml.dom.rst:732 +msgid "" +"Return an attribute with a particular index. The order you get the " +"attributes in is arbitrary but will be consistent for the life of a DOM. " +"Each item is an attribute node. Get its value with the :attr:`value` " +"attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:736 +msgid "" +"There are also experimental methods that give this class more mapping " +"behavior. You can use them or you can use the standardized :meth:" +"`getAttribute\\*` family of methods on the :class:`Element` objects." +msgstr "" + +#: ../Doc/library/xml.dom.rst:744 +msgid "Comment Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:746 +msgid "" +":class:`Comment` represents a comment in the XML document. It is a subclass " +"of :class:`Node`, but cannot have child nodes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:752 +msgid "" +"The content of the comment as a string. The attribute contains all " +"characters between the leading ````, " +"but does not include them." +msgstr "" + +#: ../Doc/library/xml.dom.rst:760 +msgid "Text and CDATASection Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:762 +msgid "" +"The :class:`Text` interface represents text in the XML document. If the " +"parser and DOM implementation support the DOM's XML extension, portions of " +"the text enclosed in CDATA marked sections are stored in :class:" +"`CDATASection` objects. These two interfaces are identical, but provide " +"different values for the :attr:`nodeType` attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:768 +msgid "" +"These interfaces extend the :class:`Node` interface. They cannot have child " +"nodes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:774 +msgid "The content of the text node as a string." +msgstr "" + +#: ../Doc/library/xml.dom.rst:778 +msgid "" +"The use of a :class:`CDATASection` node does not indicate that the node " +"represents a complete CDATA marked section, only that the content of the " +"node was part of a CDATA section. A single CDATA section may be represented " +"by more than one node in the document tree. There is no way to determine " +"whether two adjacent :class:`CDATASection` nodes represent different CDATA " +"marked sections." +msgstr "" + +#: ../Doc/library/xml.dom.rst:788 +msgid "ProcessingInstruction Objects" +msgstr "" + +#: ../Doc/library/xml.dom.rst:790 +msgid "" +"Represents a processing instruction in the XML document; this inherits from " +"the :class:`Node` interface and cannot have child nodes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:796 +msgid "" +"The content of the processing instruction up to the first whitespace " +"character. This is a read-only attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:802 +msgid "" +"The content of the processing instruction following the first whitespace " +"character." +msgstr "" + +#: ../Doc/library/xml.dom.rst:811 +msgid "" +"The DOM Level 2 recommendation defines a single exception, :exc:" +"`DOMException`, and a number of constants that allow applications to " +"determine what sort of error occurred. :exc:`DOMException` instances carry " +"a :attr:`code` attribute that provides the appropriate value for the " +"specific exception." +msgstr "" + +#: ../Doc/library/xml.dom.rst:816 +msgid "" +"The Python DOM interface provides the constants, but also expands the set of " +"exceptions so that a specific exception exists for each of the exception " +"codes defined by the DOM. The implementations must raise the appropriate " +"specific exception, each of which carries the appropriate value for the :" +"attr:`code` attribute." +msgstr "" + +#: ../Doc/library/xml.dom.rst:825 +msgid "" +"Base exception class used for all specific DOM exceptions. This exception " +"class cannot be directly instantiated." +msgstr "" + +#: ../Doc/library/xml.dom.rst:831 +msgid "" +"Raised when a specified range of text does not fit into a string. This is " +"not known to be used in the Python DOM implementations, but may be received " +"from DOM implementations not written in Python." +msgstr "" + +#: ../Doc/library/xml.dom.rst:838 +msgid "" +"Raised when an attempt is made to insert a node where the node type is not " +"allowed." +msgstr "" + +#: ../Doc/library/xml.dom.rst:844 +msgid "" +"Raised when an index or size parameter to a method is negative or exceeds " +"the allowed values." +msgstr "" + +#: ../Doc/library/xml.dom.rst:850 +msgid "" +"Raised when an attempt is made to insert an :class:`Attr` node that is " +"already present elsewhere in the document." +msgstr "" + +#: ../Doc/library/xml.dom.rst:856 +msgid "" +"Raised if a parameter or an operation is not supported on the underlying " +"object." +msgstr "" + +#: ../Doc/library/xml.dom.rst:861 +msgid "" +"This exception is raised when a string parameter contains a character that " +"is not permitted in the context it's being used in by the XML 1.0 " +"recommendation. For example, attempting to create an :class:`Element` node " +"with a space in the element type name will cause this error to be raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:869 +msgid "Raised when an attempt is made to modify the type of a node." +msgstr "" + +#: ../Doc/library/xml.dom.rst:874 +msgid "" +"Raised when an attempt is made to use an object that is not defined or is no " +"longer usable." +msgstr "" + +#: ../Doc/library/xml.dom.rst:880 +msgid "" +"If an attempt is made to change any object in a way that is not permitted " +"with regard to the `Namespaces in XML `_ recommendation, this exception is raised." +msgstr "" + +#: ../Doc/library/xml.dom.rst:887 +msgid "" +"Exception when a node does not exist in the referenced context. For " +"example, :meth:`NamedNodeMap.removeNamedItem` will raise this if the node " +"passed in does not exist in the map." +msgstr "" + +#: ../Doc/library/xml.dom.rst:894 +msgid "" +"Raised when the implementation does not support the requested type of object " +"or operation." +msgstr "" + +#: ../Doc/library/xml.dom.rst:900 +msgid "" +"This is raised if data is specified for a node which does not support data." +msgstr "" + +#: ../Doc/library/xml.dom.rst:907 +msgid "" +"Raised on attempts to modify an object where modifications are not allowed " +"(such as for read-only nodes)." +msgstr "" + +#: ../Doc/library/xml.dom.rst:913 +msgid "Raised when an invalid or illegal string is specified." +msgstr "" + +#: ../Doc/library/xml.dom.rst:920 +msgid "" +"Raised when a node is inserted in a different document than it currently " +"belongs to, and the implementation does not support migrating the node from " +"one document to the other." +msgstr "" + +#: ../Doc/library/xml.dom.rst:924 +msgid "" +"The exception codes defined in the DOM recommendation map to the exceptions " +"described above according to this table:" +msgstr "" + +#: ../Doc/library/xml.dom.rst:928 +msgid "Exception" +msgstr "" + +#: ../Doc/library/xml.dom.rst:930 +msgid ":const:`DOMSTRING_SIZE_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:930 +msgid ":exc:`DomstringSizeErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:932 +msgid ":const:`HIERARCHY_REQUEST_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:932 +msgid ":exc:`HierarchyRequestErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:934 +msgid ":const:`INDEX_SIZE_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:934 +msgid ":exc:`IndexSizeErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:936 +msgid ":const:`INUSE_ATTRIBUTE_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:936 +msgid ":exc:`InuseAttributeErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:938 +msgid ":const:`INVALID_ACCESS_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:938 +msgid ":exc:`InvalidAccessErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:940 +msgid ":const:`INVALID_CHARACTER_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:940 +msgid ":exc:`InvalidCharacterErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:942 +msgid ":const:`INVALID_MODIFICATION_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:942 +msgid ":exc:`InvalidModificationErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:944 +msgid ":const:`INVALID_STATE_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:944 +msgid ":exc:`InvalidStateErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:946 +msgid ":const:`NAMESPACE_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:946 +msgid ":exc:`NamespaceErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:948 +msgid ":const:`NOT_FOUND_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:948 +msgid ":exc:`NotFoundErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:950 +msgid ":const:`NOT_SUPPORTED_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:950 +msgid ":exc:`NotSupportedErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:952 +msgid ":const:`NO_DATA_ALLOWED_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:952 +msgid ":exc:`NoDataAllowedErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:954 +msgid ":const:`NO_MODIFICATION_ALLOWED_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:954 +msgid ":exc:`NoModificationAllowedErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:956 +msgid ":const:`SYNTAX_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:956 +msgid ":exc:`SyntaxErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:958 +msgid ":const:`WRONG_DOCUMENT_ERR`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:958 +msgid ":exc:`WrongDocumentErr`" +msgstr "" + +#: ../Doc/library/xml.dom.rst:965 +msgid "Conformance" +msgstr "" + +#: ../Doc/library/xml.dom.rst:967 +msgid "" +"This section describes the conformance requirements and relationships " +"between the Python DOM API, the W3C DOM recommendations, and the OMG IDL " +"mapping for Python." +msgstr "" + +#: ../Doc/library/xml.dom.rst:975 +msgid "Type Mapping" +msgstr "" + +#: ../Doc/library/xml.dom.rst:977 +msgid "" +"The IDL types used in the DOM specification are mapped to Python types " +"according to the following table." +msgstr "" + +#: ../Doc/library/xml.dom.rst:981 +msgid "IDL Type" +msgstr "" + +#: ../Doc/library/xml.dom.rst:983 ../Doc/library/xmlrpc.client.rst:89 +msgid "``boolean``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:983 +msgid "``bool`` or ``int``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:985 ../Doc/library/xml.dom.rst:987 +#: ../Doc/library/xml.dom.rst:989 +msgid "``int``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:987 +msgid "``long int``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:989 +msgid "``unsigned int``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:991 +msgid "``DOMString``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:991 +msgid "``str`` or ``bytes``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:993 +msgid "``null``" +msgstr "" + +#: ../Doc/library/xml.dom.rst:999 +msgid "Accessor Methods" +msgstr "" + +#: ../Doc/library/xml.dom.rst:1001 +msgid "" +"The mapping from OMG IDL to Python defines accessor functions for IDL " +"``attribute`` declarations in much the way the Java mapping does. Mapping " +"the IDL declarations ::" +msgstr "" + +#: ../Doc/library/xml.dom.rst:1008 +msgid "" +"yields three accessor functions: a \"get\" method for :attr:`someValue` (:" +"meth:`_get_someValue`), and \"get\" and \"set\" methods for :attr:" +"`anotherValue` (:meth:`_get_anotherValue` and :meth:`_set_anotherValue`). " +"The mapping, in particular, does not require that the IDL attributes are " +"accessible as normal Python attributes: ``object.someValue`` is *not* " +"required to work, and may raise an :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/xml.dom.rst:1015 +msgid "" +"The Python DOM API, however, *does* require that normal attribute access " +"work. This means that the typical surrogates generated by Python IDL " +"compilers are not likely to work, and wrapper objects may be needed on the " +"client if the DOM objects are accessed via CORBA. While this does require " +"some additional consideration for CORBA DOM clients, the implementers with " +"experience using DOM over CORBA from Python do not consider this a problem. " +"Attributes that are declared ``readonly`` may not restrict write access in " +"all DOM implementations." +msgstr "" + +#: ../Doc/library/xml.dom.rst:1024 +msgid "" +"In the Python DOM API, accessor functions are not required. If provided, " +"they should take the form defined by the Python IDL mapping, but these " +"methods are considered unnecessary since the attributes are accessible " +"directly from Python. \"Set\" accessors should never be provided for " +"``readonly`` attributes." +msgstr "" + +#: ../Doc/library/xml.dom.rst:1029 +msgid "" +"The IDL definitions do not fully embody the requirements of the W3C DOM API, " +"such as the notion of certain objects, such as the return value of :meth:" +"`getElementsByTagName`, being \"live\". The Python DOM API does not require " +"implementations to enforce such requirements." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:2 +msgid ":mod:`xml.dom.minidom` --- Minimal DOM implementation" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:11 +msgid "**Source code:** :source:`Lib/xml/dom/minidom.py`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:15 +msgid "" +":mod:`xml.dom.minidom` is a minimal implementation of the Document Object " +"Model interface, with an API similar to that in other languages. It is " +"intended to be simpler than the full DOM and also significantly smaller. " +"Users who are not already proficient with the DOM should consider using the :" +"mod:`xml.etree.ElementTree` module for their XML processing instead." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:24 +msgid "" +"The :mod:`xml.dom.minidom` module is not secure against maliciously " +"constructed data. If you need to parse untrusted or unauthenticated data " +"see :ref:`xml-vulnerabilities`." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:29 +msgid "" +"DOM applications typically start by parsing some XML into a DOM. With :mod:" +"`xml.dom.minidom`, this is done through the parse functions::" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:41 +msgid "" +"The :func:`parse` function can take either a filename or an open file object." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:46 +msgid "" +"Return a :class:`Document` from the given input. *filename_or_file* may be " +"either a file name, or a file-like object. *parser*, if given, must be a " +"SAX2 parser object. This function will change the document handler of the " +"parser and activate namespace support; other parser configuration (like " +"setting an entity resolver) must have been done in advance." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:52 ../Doc/library/xml.dom.pulldom.rst:83 +msgid "" +"If you have XML in a string, you can use the :func:`parseString` function " +"instead:" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:58 +msgid "" +"Return a :class:`Document` that represents the *string*. This method creates " +"an :class:`io.StringIO` object for the string and passes that on to :func:" +"`parse`." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:61 +msgid "" +"Both functions return a :class:`Document` object representing the content of " +"the document." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:64 +msgid "" +"What the :func:`parse` and :func:`parseString` functions do is connect an " +"XML parser with a \"DOM builder\" that can accept parse events from any SAX " +"parser and convert them into a DOM tree. The name of the functions are " +"perhaps misleading, but are easy to grasp when learning the interfaces. The " +"parsing of the document will be completed before these functions return; " +"it's simply that these functions do not provide a parser implementation " +"themselves." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:71 +msgid "" +"You can also create a :class:`Document` by calling a method on a \"DOM " +"Implementation\" object. You can get this object either by calling the :" +"func:`getDOMImplementation` function in the :mod:`xml.dom` package or the :" +"mod:`xml.dom.minidom` module. Once you have a :class:`Document`, you can " +"add child nodes to it to populate the DOM::" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:86 +msgid "" +"Once you have a DOM document object, you can access the parts of your XML " +"document through its properties and methods. These properties are defined " +"in the DOM specification. The main property of the document object is the :" +"attr:`documentElement` property. It gives you the main element in the XML " +"document: the one that holds all others. Here is an example program::" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:95 +msgid "" +"When you are finished with a DOM tree, you may optionally call the :meth:" +"`unlink` method to encourage early cleanup of the now-unneeded objects. :" +"meth:`unlink` is an :mod:`xml.dom.minidom`\\ -specific extension to the DOM " +"API that renders the node and its descendants are essentially useless. " +"Otherwise, Python's garbage collector will eventually take care of the " +"objects in the tree." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:111 +msgid "DOM Objects" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:113 +msgid "" +"The definition of the DOM API for Python is given as part of the :mod:`xml." +"dom` module documentation. This section lists the differences between the " +"API and :mod:`xml.dom.minidom`." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:120 +msgid "" +"Break internal references within the DOM so that it will be garbage " +"collected on versions of Python without cyclic GC. Even when cyclic GC is " +"available, using this can make large amounts of memory available sooner, so " +"calling this on DOM objects as soon as they are no longer needed is good " +"practice. This only needs to be called on the :class:`Document` object, but " +"may be called on child nodes to discard children of that node." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:127 +msgid "" +"You can avoid calling this method explicitly by using the :keyword:`with` " +"statement. The following code will automatically unlink *dom* when the :" +"keyword:`with` block is exited::" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:137 +msgid "" +"Write XML to the writer object. The writer should have a :meth:`write` " +"method which matches that of the file object interface. The *indent* " +"parameter is the indentation of the current node. The *addindent* parameter " +"is the incremental indentation to use for subnodes of the current one. The " +"*newl* parameter specifies the string to use to terminate newlines." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:143 +msgid "" +"For the :class:`Document` node, an additional keyword argument *encoding* " +"can be used to specify the encoding field of the XML header." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:149 +msgid "" +"Return a string or byte string containing the XML represented by the DOM " +"node." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:152 +msgid "" +"With an explicit *encoding* [1]_ argument, the result is a byte string in " +"the specified encoding. With no *encoding* argument, the result is a Unicode " +"string, and the XML declaration in the resulting string does not specify an " +"encoding. Encoding this string in an encoding other than UTF-8 is likely " +"incorrect, since UTF-8 is the default encoding of XML." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:161 +msgid "" +"Return a pretty-printed version of the document. *indent* specifies the " +"indentation string and defaults to a tabulator; *newl* specifies the string " +"emitted at the end of each line and defaults to ``\\n``." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:165 +msgid "" +"The *encoding* argument behaves like the corresponding argument of :meth:" +"`toxml`." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:172 +msgid "DOM Example" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:174 +msgid "" +"This example program is a fairly realistic example of a simple program. In " +"this particular case, we do not take much advantage of the flexibility of " +"the DOM." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:183 +msgid "minidom and the DOM standard" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:185 +msgid "" +"The :mod:`xml.dom.minidom` module is essentially a DOM 1.0-compatible DOM " +"with some DOM 2 features (primarily namespace features)." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:188 +msgid "" +"Usage of the DOM interface in Python is straight-forward. The following " +"mapping rules apply:" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:191 +msgid "" +"Interfaces are accessed through instance objects. Applications should not " +"instantiate the classes themselves; they should use the creator functions " +"available on the :class:`Document` object. Derived interfaces support all " +"operations (and attributes) from the base interfaces, plus any new " +"operations." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:196 +msgid "" +"Operations are used as methods. Since the DOM uses only :keyword:`in` " +"parameters, the arguments are passed in normal order (from left to right). " +"There are no optional arguments. ``void`` operations return ``None``." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:200 +msgid "" +"IDL attributes map to instance attributes. For compatibility with the OMG " +"IDL language mapping for Python, an attribute ``foo`` can also be accessed " +"through accessor methods :meth:`_get_foo` and :meth:`_set_foo`. " +"``readonly`` attributes must not be changed; this is not enforced at runtime." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:205 +msgid "" +"The types ``short int``, ``unsigned int``, ``unsigned long long``, and " +"``boolean`` all map to Python integer objects." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:208 +msgid "" +"The type ``DOMString`` maps to Python strings. :mod:`xml.dom.minidom` " +"supports either bytes or strings, but will normally produce strings. Values " +"of type ``DOMString`` may also be ``None`` where allowed to have the IDL " +"``null`` value by the DOM specification from the W3C." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:213 +msgid "" +"``const`` declarations map to variables in their respective scope (e.g. " +"``xml.dom.minidom.Node.PROCESSING_INSTRUCTION_NODE``); they must not be " +"changed." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:216 +msgid "" +"``DOMException`` is currently not supported in :mod:`xml.dom.minidom`. " +"Instead, :mod:`xml.dom.minidom` uses standard Python exceptions such as :exc:" +"`TypeError` and :exc:`AttributeError`." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:220 +msgid "" +":class:`NodeList` objects are implemented using Python's built-in list type. " +"These objects provide the interface defined in the DOM specification, but " +"with earlier versions of Python they do not support the official API. They " +"are, however, much more \"Pythonic\" than the interface defined in the W3C " +"recommendations." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:226 +msgid "" +"The following interfaces have no implementation in :mod:`xml.dom.minidom`:" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:228 +msgid ":class:`DOMTimeStamp`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:234 +msgid ":class:`CharacterData`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:236 +msgid ":class:`CDATASection`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:238 +msgid ":class:`Notation`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:240 +msgid ":class:`Entity`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:242 +msgid ":class:`EntityReference`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:244 +msgid ":class:`DocumentFragment`" +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:246 +msgid "" +"Most of these reflect information in the XML document that is not of general " +"utility to most DOM users." +msgstr "" + +#: ../Doc/library/xml.dom.minidom.rst:251 +msgid "" +"The encoding name included in the XML output should conform to the " +"appropriate standards. For example, \"UTF-8\" is valid, but \"UTF8\" is not " +"valid in an XML document's declaration, even though Python accepts it as an " +"encoding name. See https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-" +"EncodingDecl and https://www.iana.org/assignments/character-sets/character-" +"sets.xhtml." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:2 +msgid ":mod:`xml.dom.pulldom` --- Support for building partial DOM trees" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:9 +msgid "**Source code:** :source:`Lib/xml/dom/pulldom.py`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:13 +msgid "" +"The :mod:`xml.dom.pulldom` module provides a \"pull parser\" which can also " +"be asked to produce DOM-accessible fragments of the document where " +"necessary. The basic concept involves pulling \"events\" from a stream of " +"incoming XML and processing them. In contrast to SAX which also employs an " +"event-driven processing model together with callbacks, the user of a pull " +"parser is responsible for explicitly pulling events from the stream, looping " +"over those events until either processing is finished or an error condition " +"occurs." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:24 +msgid "" +"The :mod:`xml.dom.pulldom` module is not secure against maliciously " +"constructed data. If you need to parse untrusted or unauthenticated data " +"see :ref:`xml-vulnerabilities`." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:40 +msgid "``event`` is a constant and can be one of:" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:42 +msgid ":data:`START_ELEMENT`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:43 +msgid ":data:`END_ELEMENT`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:44 +msgid ":data:`COMMENT`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:45 +msgid ":data:`START_DOCUMENT`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:46 +msgid ":data:`END_DOCUMENT`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:47 +msgid ":data:`CHARACTERS`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:48 +msgid ":data:`PROCESSING_INSTRUCTION`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:49 +msgid ":data:`IGNORABLE_WHITESPACE`" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:51 +msgid "" +"``node`` is an object of type :class:`xml.dom.minidom.Document`, :class:`xml." +"dom.minidom.Element` or :class:`xml.dom.minidom.Text`." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:54 +msgid "" +"Since the document is treated as a \"flat\" stream of events, the document " +"\"tree\" is implicitly traversed and the desired elements are found " +"regardless of their depth in the tree. In other words, one does not need to " +"consider hierarchical issues such as recursive searching of the document " +"nodes, although if the context of elements were important, one would either " +"need to maintain some context-related state (i.e. remembering where one is " +"in the document at any given point) or to make use of the :func:" +"`DOMEventStream.expandNode` method and switch to DOM-related processing." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:66 ../Doc/library/xml.dom.pulldom.rst:71 +msgid "Subclass of :class:`xml.sax.handler.ContentHandler`." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:76 +msgid "" +"Return a :class:`DOMEventStream` from the given input. *stream_or_string* " +"may be either a file name, or a file-like object. *parser*, if given, must " +"be an :class:`~xml.sax.xmlreader.XMLReader` object. This function will " +"change the document handler of the parser and activate namespace support; " +"other parser configuration (like setting an entity resolver) must have been " +"done in advance." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:87 +msgid "" +"Return a :class:`DOMEventStream` that represents the (Unicode) *string*." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:91 +msgid "Default value for the *bufsize* parameter to :func:`parse`." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:93 +msgid "" +"The value of this variable can be changed before calling :func:`parse` and " +"the new value will take effect." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:99 +msgid "DOMEventStream Objects" +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:106 +msgid "" +"Return a tuple containing *event* and the current *node* as :class:`xml.dom." +"minidom.Document` if event equals :data:`START_DOCUMENT`, :class:`xml.dom." +"minidom.Element` if event equals :data:`START_ELEMENT` or :data:" +"`END_ELEMENT` or :class:`xml.dom.minidom.Text` if event equals :data:" +"`CHARACTERS`. The current node does not contain informations about its " +"children, unless :func:`expandNode` is called." +msgstr "" + +#: ../Doc/library/xml.dom.pulldom.rst:116 +msgid "Expands all children of *node* into *node*. Example::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:2 +msgid ":mod:`xml.etree.ElementTree` --- The ElementTree XML API" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:9 +msgid "**Source code:** :source:`Lib/xml/etree/ElementTree.py`" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:13 +msgid "" +"The :mod:`xml.etree.ElementTree` module implements a simple and efficient " +"API for parsing and creating XML data." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:16 +msgid "" +"This module will use a fast implementation whenever available. The :mod:`xml." +"etree.cElementTree` module is deprecated." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:23 +msgid "" +"The :mod:`xml.etree.ElementTree` module is not secure against maliciously " +"constructed data. If you need to parse untrusted or unauthenticated data " +"see :ref:`xml-vulnerabilities`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:30 +msgid "" +"This is a short tutorial for using :mod:`xml.etree.ElementTree` (``ET`` in " +"short). The goal is to demonstrate some of the building blocks and basic " +"concepts of the module." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:35 +msgid "XML tree and elements" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:37 +msgid "" +"XML is an inherently hierarchical data format, and the most natural way to " +"represent it is with a tree. ``ET`` has two classes for this purpose - :" +"class:`ElementTree` represents the whole XML document as a tree, and :class:" +"`Element` represents a single node in this tree. Interactions with the " +"whole document (reading and writing to/from files) are usually done on the :" +"class:`ElementTree` level. Interactions with a single XML element and its " +"sub-elements are done on the :class:`Element` level." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:48 +msgid "Parsing XML" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:50 +msgid "" +"We'll be using the following XML document as the sample data for this " +"section:" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:78 +msgid "We can import this data by reading from a file::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:84 +msgid "Or directly from a string::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:88 +msgid "" +":func:`fromstring` parses XML from a string directly into an :class:" +"`Element`, which is the root element of the parsed tree. Other parsing " +"functions may create an :class:`ElementTree`. Check the documentation to be " +"sure." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:92 +msgid "" +"As an :class:`Element`, ``root`` has a tag and a dictionary of attributes::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:99 +msgid "It also has children nodes over which we can iterate::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:108 +msgid "Children are nested, and we can access specific child nodes by index::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:116 +msgid "" +"Not all elements of the XML input will end up as elements of the parsed " +"tree. Currently, this module skips over any XML comments, processing " +"instructions, and document type declarations in the input. Nevertheless, " +"trees built using this module's API rather than parsing from XML text can " +"have comments and processing instructions in them; they will be included " +"when generating XML output. A document type declaration may be accessed by " +"passing a custom :class:`TreeBuilder` instance to the :class:`XMLParser` " +"constructor." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:130 +msgid "Pull API for non-blocking parsing" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:132 +msgid "" +"Most parsing functions provided by this module require the whole document to " +"be read at once before returning any result. It is possible to use an :" +"class:`XMLParser` and feed data into it incrementally, but it is a push API " +"that calls methods on a callback target, which is too low-level and " +"inconvenient for most needs. Sometimes what the user really wants is to be " +"able to parse XML incrementally, without blocking operations, while enjoying " +"the convenience of fully constructed :class:`Element` objects." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:140 +msgid "" +"The most powerful tool for doing this is :class:`XMLPullParser`. It does " +"not require a blocking read to obtain the XML data, and is instead fed with " +"data incrementally with :meth:`XMLPullParser.feed` calls. To get the parsed " +"XML elements, call :meth:`XMLPullParser.read_events`. Here is an example::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:156 +msgid "" +"The obvious use case is applications that operate in a non-blocking fashion " +"where the XML data is being received from a socket or read incrementally " +"from some storage device. In such cases, blocking reads are unacceptable." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:160 +msgid "" +"Because it's so flexible, :class:`XMLPullParser` can be inconvenient to use " +"for simpler use-cases. If you don't mind your application blocking on " +"reading XML data but would still like to have incremental parsing " +"capabilities, take a look at :func:`iterparse`. It can be useful when " +"you're reading a large XML document and don't want to hold it wholly in " +"memory." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:167 +msgid "Finding interesting elements" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:169 +msgid "" +":class:`Element` has some useful methods that help iterate recursively over " +"all the sub-tree below it (its children, their children, and so on). For " +"example, :meth:`Element.iter`::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:182 +msgid "" +":meth:`Element.findall` finds only elements with a tag which are direct " +"children of the current element. :meth:`Element.find` finds the *first* " +"child with a particular tag, and :attr:`Element.text` accesses the element's " +"text content. :meth:`Element.get` accesses the element's attributes::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:196 +msgid "" +"More sophisticated specification of which elements to look for is possible " +"by using :ref:`XPath `." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:200 +msgid "Modifying an XML File" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:202 +msgid "" +":class:`ElementTree` provides a simple way to build XML documents and write " +"them to files. The :meth:`ElementTree.write` method serves this purpose." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:205 +msgid "" +"Once created, an :class:`Element` object may be manipulated by directly " +"changing its fields (such as :attr:`Element.text`), adding and modifying " +"attributes (:meth:`Element.set` method), as well as adding new children (for " +"example with :meth:`Element.append`)." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:210 +msgid "" +"Let's say we want to add one to each country's rank, and add an ``updated`` " +"attribute to the rank element::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:220 +#: ../Doc/library/xml.etree.elementtree.rst:258 +msgid "Our XML now looks like this:" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:248 +msgid "" +"We can remove elements using :meth:`Element.remove`. Let's say we want to " +"remove all countries with a rank higher than 50::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:280 +msgid "Building XML documents" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:282 +msgid "" +"The :func:`SubElement` function also provides a convenient way to create new " +"sub-elements for a given element::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:293 +msgid "Parsing XML with Namespaces" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:295 +msgid "" +"If the XML input has `namespaces `__, tags and attributes with prefixes in the form ``prefix:" +"sometag`` get expanded to ``{uri}sometag`` where the *prefix* is replaced by " +"the full *URI*. Also, if there is a `default namespace `__, that full URI gets prepended " +"to all of the non-prefixed tags." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:303 +msgid "" +"Here is an XML example that incorporates two namespaces, one with the prefix " +"\"fictional\" and the other serving as the default namespace:" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:324 +msgid "" +"One way to search and explore this XML example is to manually add the URI to " +"every tag or attribute in the xpath of a :meth:`~Element.find` or :meth:" +"`~Element.findall`::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:335 +msgid "" +"A better way to search the namespaced XML example is to create a dictionary " +"with your own prefixes and use those in the search functions::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:347 +msgid "These two approaches both output::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:359 +msgid "Additional resources" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:361 +msgid "" +"See http://effbot.org/zone/element-index.htm for tutorials and links to " +"other docs." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:368 +msgid "XPath support" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:370 +msgid "" +"This module provides limited support for `XPath expressions `_ for locating elements in a tree. The goal is to support a " +"small subset of the abbreviated syntax; a full XPath engine is outside the " +"scope of the module." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:378 +msgid "" +"Here's an example that demonstrates some of the XPath capabilities of the " +"module. We'll be using the ``countrydata`` XML document from the :ref:" +"`Parsing XML ` section::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:403 +msgid "Supported XPath syntax" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:410 +msgid "``tag``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:410 +msgid "" +"Selects all child elements with the given tag. For example, ``spam`` selects " +"all child elements named ``spam``, and ``spam/egg`` selects all " +"grandchildren named ``egg`` in all children named ``spam``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:416 +msgid "" +"Selects all child elements. For example, ``*/egg`` selects all " +"grandchildren named ``egg``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:419 +msgid "" +"Selects the current node. This is mostly useful at the beginning of the " +"path, to indicate that it's a relative path." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:423 +msgid "``//``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:423 +msgid "" +"Selects all subelements, on all levels beneath the current element. For " +"example, ``.//egg`` selects all ``egg`` elements in the entire tree." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:427 +msgid "``..``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:427 +msgid "" +"Selects the parent element. Returns ``None`` if the path attempts to reach " +"the ancestors of the start element (the element ``find`` was called on)." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:431 +msgid "``[@attrib]``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:431 +msgid "Selects all elements that have the given attribute." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:433 +msgid "``[@attrib='value']``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:433 +msgid "" +"Selects all elements for which the given attribute has the given value. The " +"value cannot contain quotes." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:437 +msgid "``[tag]``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:437 +msgid "" +"Selects all elements that have a child named ``tag``. Only immediate " +"children are supported." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:440 +msgid "``[tag='text']``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:440 +msgid "" +"Selects all elements that have a child named ``tag`` whose complete text " +"content, including descendants, equals the given ``text``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:444 +msgid "``[position]``" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:444 +msgid "" +"Selects all elements that are located at the given position. The position " +"can be either an integer (1 is the first position), the expression " +"``last()`` (for the last position), or a position relative to the last " +"position (e.g. ``last()-1``)." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:451 +msgid "" +"Predicates (expressions within square brackets) must be preceded by a tag " +"name, an asterisk, or another predicate. ``position`` predicates must be " +"preceded by a tag name." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:466 +msgid "" +"Comment element factory. This factory function creates a special element " +"that will be serialized as an XML comment by the standard serializer. The " +"comment string can be either a bytestring or a Unicode string. *text* is a " +"string containing the comment string. Returns an element instance " +"representing a comment." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:472 +msgid "" +"Note that :class:`XMLParser` skips over comments in the input instead of " +"creating comment objects for them. An :class:`ElementTree` will only contain " +"comment nodes if they have been inserted into to the tree using one of the :" +"class:`Element` methods." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:479 +msgid "" +"Writes an element tree or element structure to sys.stdout. This function " +"should be used for debugging only." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:482 +msgid "" +"The exact output format is implementation dependent. In this version, it's " +"written as an ordinary XML file." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:485 +msgid "*elem* is an element tree or an individual element." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:490 +msgid "" +"Parses an XML section from a string constant. Same as :func:`XML`. *text* " +"is a string containing XML data. Returns an :class:`Element` instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:496 +msgid "" +"Parses an XML document from a sequence of string fragments. *sequence* is a " +"list or other sequence containing XML data fragments. *parser* is an " +"optional parser instance. If not given, the standard :class:`XMLParser` " +"parser is used. Returns an :class:`Element` instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:506 +msgid "" +"Checks if an object appears to be a valid element object. *element* is an " +"element instance. Returns a true value if this is an element object." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:512 +msgid "" +"Parses an XML section into an element tree incrementally, and reports what's " +"going on to the user. *source* is a filename or :term:`file object` " +"containing XML data. *events* is a sequence of events to report back. The " +"supported events are the strings ``\"start\"``, ``\"end\"``, ``\"start-ns" +"\"`` and ``\"end-ns\"`` (the \"ns\" events are used to get detailed " +"namespace information). If *events* is omitted, only ``\"end\"`` events are " +"reported. *parser* is an optional parser instance. If not given, the " +"standard :class:`XMLParser` parser is used. *parser* must be a subclass of :" +"class:`XMLParser` and can only use the default :class:`TreeBuilder` as a " +"target. Returns an :term:`iterator` providing ``(event, elem)`` pairs." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:523 +msgid "" +"Note that while :func:`iterparse` builds the tree incrementally, it issues " +"blocking reads on *source* (or the file it names). As such, it's unsuitable " +"for applications where blocking reads can't be made. For fully non-blocking " +"parsing, see :class:`XMLPullParser`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:530 +msgid "" +":func:`iterparse` only guarantees that it has seen the \">\" character of a " +"starting tag when it emits a \"start\" event, so the attributes are defined, " +"but the contents of the text and tail attributes are undefined at that " +"point. The same applies to the element children; they may or may not be " +"present." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:536 +#: ../Doc/library/xml.etree.elementtree.rst:1170 +msgid "If you need a fully populated element, look for \"end\" events instead." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:538 +msgid "The *parser* argument." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:543 +msgid "" +"Parses an XML section into an element tree. *source* is a filename or file " +"object containing XML data. *parser* is an optional parser instance. If " +"not given, the standard :class:`XMLParser` parser is used. Returns an :" +"class:`ElementTree` instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:551 +msgid "" +"PI element factory. This factory function creates a special element that " +"will be serialized as an XML processing instruction. *target* is a string " +"containing the PI target. *text* is a string containing the PI contents, if " +"given. Returns an element instance, representing a processing instruction." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:556 +msgid "" +"Note that :class:`XMLParser` skips over processing instructions in the input " +"instead of creating comment objects for them. An :class:`ElementTree` will " +"only contain processing instruction nodes if they have been inserted into to " +"the tree using one of the :class:`Element` methods." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:564 +msgid "" +"Registers a namespace prefix. The registry is global, and any existing " +"mapping for either the given prefix or the namespace URI will be removed. " +"*prefix* is a namespace prefix. *uri* is a namespace uri. Tags and " +"attributes in this namespace will be serialized with the given prefix, if at " +"all possible." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:575 +msgid "" +"Subelement factory. This function creates an element instance, and appends " +"it to an existing element." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:578 +msgid "" +"The element name, attribute names, and attribute values can be either " +"bytestrings or Unicode strings. *parent* is the parent element. *tag* is " +"the subelement name. *attrib* is an optional dictionary, containing element " +"attributes. *extra* contains additional attributes, given as keyword " +"arguments. Returns an element instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:588 +msgid "" +"Generates a string representation of an XML element, including all " +"subelements. *element* is an :class:`Element` instance. *encoding* [1]_ is " +"the output encoding (default is US-ASCII). Use ``encoding=\"unicode\"`` to " +"generate a Unicode string (otherwise, a bytestring is generated). *method* " +"is either ``\"xml\"``, ``\"html\"`` or ``\"text\"`` (default is ``\"xml" +"\"``). *short_empty_elements* has the same meaning as in :meth:`ElementTree." +"write`. Returns an (optionally) encoded string containing the XML data." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:596 +#: ../Doc/library/xml.etree.elementtree.rst:615 +#: ../Doc/library/xml.etree.elementtree.rst:942 +#: ../Doc/library/xml.sax.utils.rst:69 +msgid "The *short_empty_elements* parameter." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:603 +msgid "" +"Generates a string representation of an XML element, including all " +"subelements. *element* is an :class:`Element` instance. *encoding* [1]_ is " +"the output encoding (default is US-ASCII). Use ``encoding=\"unicode\"`` to " +"generate a Unicode string (otherwise, a bytestring is generated). *method* " +"is either ``\"xml\"``, ``\"html\"`` or ``\"text\"`` (default is ``\"xml" +"\"``). *short_empty_elements* has the same meaning as in :meth:`ElementTree." +"write`. Returns a list of (optionally) encoded strings containing the XML " +"data. It does not guarantee any specific sequence, except that ``b\"\"." +"join(tostringlist(element)) == tostring(element)``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:621 +msgid "" +"Parses an XML section from a string constant. This function can be used to " +"embed \"XML literals\" in Python code. *text* is a string containing XML " +"data. *parser* is an optional parser instance. If not given, the standard :" +"class:`XMLParser` parser is used. Returns an :class:`Element` instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:629 +msgid "" +"Parses an XML section from a string constant, and also returns a dictionary " +"which maps from element id:s to elements. *text* is a string containing XML " +"data. *parser* is an optional parser instance. If not given, the standard :" +"class:`XMLParser` parser is used. Returns a tuple containing an :class:" +"`Element` instance and a dictionary." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:643 +msgid "" +"Element class. This class defines the Element interface, and provides a " +"reference implementation of this interface." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:646 +msgid "" +"The element name, attribute names, and attribute values can be either " +"bytestrings or Unicode strings. *tag* is the element name. *attrib* is an " +"optional dictionary, containing element attributes. *extra* contains " +"additional attributes, given as keyword arguments." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:654 +msgid "" +"A string identifying what kind of data this element represents (the element " +"type, in other words)." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:661 +msgid "" +"These attributes can be used to hold additional data associated with the " +"element. Their values are usually strings but may be any application-" +"specific object. If the element is created from an XML file, the *text* " +"attribute holds either the text between the element's start tag and its " +"first child or end tag, or ``None``, and the *tail* attribute holds either " +"the text between the element's end tag and the next tag, or ``None``. For " +"the XML data" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:673 +msgid "" +"the *a* element has ``None`` for both *text* and *tail* attributes, the *b* " +"element has *text* ``\"1\"`` and *tail* ``\"4\"``, the *c* element has " +"*text* ``\"2\"`` and *tail* ``None``, and the *d* element has *text* " +"``None`` and *tail* ``\"3\"``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:678 +msgid "" +"To collect the inner text of an element, see :meth:`itertext`, for example ``" +"\"\".join(element.itertext())``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:681 +msgid "Applications may store arbitrary objects in these attributes." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:686 +msgid "" +"A dictionary containing the element's attributes. Note that while the " +"*attrib* value is always a real mutable Python dictionary, an ElementTree " +"implementation may choose to use another internal representation, and create " +"the dictionary only if someone asks for it. To take advantage of such " +"implementations, use the dictionary methods below whenever possible." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:692 +msgid "The following dictionary-like methods work on the element attributes." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:697 +msgid "" +"Resets an element. This function removes all subelements, clears all " +"attributes, and sets the text and tail attributes to ``None``." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:703 +msgid "Gets the element attribute named *key*." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:705 +msgid "" +"Returns the attribute value, or *default* if the attribute was not found." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:710 +msgid "" +"Returns the element attributes as a sequence of (name, value) pairs. The " +"attributes are returned in an arbitrary order." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:716 +msgid "" +"Returns the elements attribute names as a list. The names are returned in " +"an arbitrary order." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:722 +msgid "Set the attribute *key* on the element to *value*." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:724 +msgid "The following methods work on the element's children (subelements)." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:729 +msgid "" +"Adds the element *subelement* to the end of this element's internal list of " +"subelements. Raises :exc:`TypeError` if *subelement* is not an :class:" +"`Element`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:736 +msgid "" +"Appends *subelements* from a sequence object with zero or more elements. " +"Raises :exc:`TypeError` if a subelement is not an :class:`Element`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:744 +msgid "" +"Finds the first subelement matching *match*. *match* may be a tag name or " +"a :ref:`path `. Returns an element instance or " +"``None``. *namespaces* is an optional mapping from namespace prefix to full " +"name." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:752 +msgid "" +"Finds all matching subelements, by tag name or :ref:`path `. Returns a list containing all matching elements in document " +"order. *namespaces* is an optional mapping from namespace prefix to full " +"name." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:760 +msgid "" +"Finds text for the first subelement matching *match*. *match* may be a tag " +"name or a :ref:`path `. Returns the text content of the " +"first matching element, or *default* if no element was found. Note that if " +"the matching element has no text content an empty string is returned. " +"*namespaces* is an optional mapping from namespace prefix to full name." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:770 +msgid "Use ``list(elem)`` or iteration." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:776 +msgid "Use method :meth:`Element.iter` instead." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:782 +msgid "" +"Inserts *subelement* at the given position in this element. Raises :exc:" +"`TypeError` if *subelement* is not an :class:`Element`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:788 +msgid "" +"Creates a tree :term:`iterator` with the current element as the root. The " +"iterator iterates over this element and all elements below it, in document " +"(depth first) order. If *tag* is not ``None`` or ``'*'``, only elements " +"whose tag equals *tag* are returned from the iterator. If the tree " +"structure is modified during iteration, the result is undefined." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:799 +msgid "" +"Finds all matching subelements, by tag name or :ref:`path `. Returns an iterable yielding all matching elements in document " +"order. *namespaces* is an optional mapping from namespace prefix to full " +"name." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:810 +msgid "" +"Creates a text iterator. The iterator loops over this element and all " +"subelements, in document order, and returns all inner text." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:818 +msgid "" +"Creates a new element object of the same type as this element. Do not call " +"this method, use the :func:`SubElement` factory function instead." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:824 +msgid "" +"Removes *subelement* from the element. Unlike the find\\* methods this " +"method compares elements based on the instance identity, not on tag value or " +"contents." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:828 +msgid "" +":class:`Element` objects also support the following sequence type methods " +"for working with subelements: :meth:`~object.__delitem__`, :meth:`~object." +"__getitem__`, :meth:`~object.__setitem__`, :meth:`~object.__len__`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:833 +msgid "" +"Caution: Elements with no subelements will test as ``False``. This behavior " +"will change in future versions. Use specific ``len(elem)`` or ``elem is " +"None`` test instead. ::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:849 +msgid "ElementTree Objects" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:854 +msgid "" +"ElementTree wrapper class. This class represents an entire element " +"hierarchy, and adds some extra support for serialization to and from " +"standard XML." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:858 +msgid "" +"*element* is the root element. The tree is initialized with the contents of " +"the XML *file* if given." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:864 +msgid "" +"Replaces the root element for this tree. This discards the current contents " +"of the tree, and replaces it with the given element. Use with care. " +"*element* is an element instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:871 +msgid "Same as :meth:`Element.find`, starting at the root of the tree." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:876 +msgid "Same as :meth:`Element.findall`, starting at the root of the tree." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:881 +msgid "Same as :meth:`Element.findtext`, starting at the root of the tree." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:886 +msgid "Use method :meth:`ElementTree.iter` instead." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:892 +msgid "Returns the root element for this tree." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:897 +msgid "" +"Creates and returns a tree iterator for the root element. The iterator " +"loops over all elements in this tree, in section order. *tag* is the tag to " +"look for (default is to return all elements)." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:904 +msgid "Same as :meth:`Element.iterfind`, starting at the root of the tree." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:911 +msgid "" +"Loads an external XML section into this element tree. *source* is a file " +"name or :term:`file object`. *parser* is an optional parser instance. If " +"not given, the standard :class:`XMLParser` parser is used. Returns the " +"section root element." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:921 +msgid "" +"Writes the element tree to a file, as XML. *file* is a file name, or a :" +"term:`file object` opened for writing. *encoding* [1]_ is the output " +"encoding (default is US-ASCII). *xml_declaration* controls if an XML " +"declaration should be added to the file. Use ``False`` for never, ``True`` " +"for always, ``None`` for only if not US-ASCII or UTF-8 or Unicode (default " +"is ``None``). *default_namespace* sets the default XML namespace (for \"xmlns" +"\"). *method* is either ``\"xml\"``, ``\"html\"`` or ``\"text\"`` (default " +"is ``\"xml\"``). The keyword-only *short_empty_elements* parameter controls " +"the formatting of elements that contain no content. If *True* (the " +"default), they are emitted as a single self-closed tag, otherwise they are " +"emitted as a pair of start/end tags." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:935 +msgid "" +"The output is either a string (:class:`str`) or binary (:class:`bytes`). " +"This is controlled by the *encoding* argument. If *encoding* is ``\"unicode" +"\"``, the output is a string; otherwise, it's binary. Note that this may " +"conflict with the type of *file* if it's an open :term:`file object`; make " +"sure you do not try to write a string to a binary stream and vice versa." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:946 +msgid "This is the XML file that is going to be manipulated::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:958 +msgid "" +"Example of changing the attribute \"target\" of every link in first " +"paragraph::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:977 +msgid "QName Objects" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:982 +msgid "" +"QName wrapper. This can be used to wrap a QName attribute value, in order " +"to get proper namespace handling on output. *text_or_uri* is a string " +"containing the QName value, in the form {uri}local, or, if the tag argument " +"is given, the URI part of a QName. If *tag* is given, the first argument is " +"interpreted as a URI, and this argument is interpreted as a local name. :" +"class:`QName` instances are opaque." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:994 +msgid "TreeBuilder Objects" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:999 +msgid "" +"Generic element structure builder. This builder converts a sequence of " +"start, data, and end method calls to a well-formed element structure. You " +"can use this class to build an element structure using a custom XML parser, " +"or a parser for some other XML-like format. *element_factory*, when given, " +"must be a callable accepting two positional arguments: a tag and a dict of " +"attributes. It is expected to return a new element instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1008 +msgid "" +"Flushes the builder buffers, and returns the toplevel document element. " +"Returns an :class:`Element` instance." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1014 +msgid "" +"Adds text to the current element. *data* is a string. This should be " +"either a bytestring, or a Unicode string." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1020 +msgid "" +"Closes the current element. *tag* is the element name. Returns the closed " +"element." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1026 +msgid "" +"Opens a new element. *tag* is the element name. *attrs* is a dictionary " +"containing element attributes. Returns the opened element." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1030 +msgid "" +"In addition, a custom :class:`TreeBuilder` object can provide the following " +"method:" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1035 +msgid "" +"Handles a doctype declaration. *name* is the doctype name. *pubid* is the " +"public identifier. *system* is the system identifier. This method does not " +"exist on the default :class:`TreeBuilder` class." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1050 +msgid "" +"This class is the low-level building block of the module. It uses :mod:`xml." +"parsers.expat` for efficient, event-based parsing of XML. It can be fed XML " +"data incrementally with the :meth:`feed` method, and parsing events are " +"translated to a push API - by invoking callbacks on the *target* object. If " +"*target* is omitted, the standard :class:`TreeBuilder` is used. The *html* " +"argument was historically used for backwards compatibility and is now " +"deprecated. If *encoding* [1]_ is given, the value overrides the encoding " +"specified in the XML file." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1059 +msgid "" +"The *html* argument. The remaining arguments should be passed via keyword " +"to prepare for the removal of the *html* argument." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1065 +msgid "" +"Finishes feeding data to the parser. Returns the result of calling the " +"``close()`` method of the *target* passed during construction; by default, " +"this is the toplevel document element." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1072 +msgid "" +"Define the :meth:`TreeBuilder.doctype` method on a custom TreeBuilder target." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1079 +msgid "Feeds data to the parser. *data* is encoded data." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1081 +msgid "" +":meth:`XMLParser.feed` calls *target*\\'s ``start(tag, attrs_dict)`` method " +"for each opening tag, its ``end(tag)`` method for each closing tag, and data " +"is processed by method ``data(data)``. :meth:`XMLParser.close` calls " +"*target*\\'s method ``close()``. :class:`XMLParser` can be used not only for " +"building a tree structure. This is an example of counting the maximum depth " +"of an XML file::" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1124 +msgid "XMLPullParser Objects" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1128 +msgid "" +"A pull parser suitable for non-blocking applications. Its input-side API is " +"similar to that of :class:`XMLParser`, but instead of pushing calls to a " +"callback target, :class:`XMLPullParser` collects an internal list of parsing " +"events and lets the user read from it. *events* is a sequence of events to " +"report back. The supported events are the strings ``\"start\"``, ``\"end" +"\"``, ``\"start-ns\"`` and ``\"end-ns\"`` (the \"ns\" events are used to get " +"detailed namespace information). If *events* is omitted, only ``\"end\"`` " +"events are reported." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1139 +msgid "Feed the given bytes data to the parser." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1143 +msgid "" +"Signal the parser that the data stream is terminated. Unlike :meth:" +"`XMLParser.close`, this method always returns :const:`None`. Any events not " +"yet retrieved when the parser is closed can still be read with :meth:" +"`read_events`." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1150 +msgid "" +"Return an iterator over the events which have been encountered in the data " +"fed to the parser. The iterator yields ``(event, elem)`` pairs, where " +"*event* is a string representing the type of event (e.g. ``\"end\"``) and " +"*elem* is the encountered :class:`Element` object." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1156 +msgid "" +"Events provided in a previous call to :meth:`read_events` will not be " +"yielded again. Events are consumed from the internal queue only when they " +"are retrieved from the iterator, so multiple readers iterating in parallel " +"over iterators obtained from :meth:`read_events` will have unpredictable " +"results." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1164 +msgid "" +":class:`XMLPullParser` only guarantees that it has seen the \">\" character " +"of a starting tag when it emits a \"start\" event, so the attributes are " +"defined, but the contents of the text and tail attributes are undefined at " +"that point. The same applies to the element children; they may or may not " +"be present." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1179 +msgid "" +"XML parse error, raised by the various parsing methods in this module when " +"parsing fails. The string representation of an instance of this exception " +"will contain a user-friendly error message. In addition, it will have the " +"following attributes available:" +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1186 +msgid "" +"A numeric error code from the expat parser. See the documentation of :mod:" +"`xml.parsers.expat` for the list of error codes and their meanings." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1191 +msgid "" +"A tuple of *line*, *column* numbers, specifying where the error occurred." +msgstr "" + +#: ../Doc/library/xml.etree.elementtree.rst:1195 +msgid "" +"The encoding string included in XML output should conform to the appropriate " +"standards. For example, \"UTF-8\" is valid, but \"UTF8\" is not. See " +"https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl and https://" +"www.iana.org/assignments/character-sets/character-sets.xhtml." +msgstr "" + +#: ../Doc/library/xml.sax.rst:2 +msgid ":mod:`xml.sax` --- Support for SAX2 parsers" +msgstr "" + +#: ../Doc/library/xml.sax.rst:11 +msgid "**Source code:** :source:`Lib/xml/sax/__init__.py`" +msgstr "" + +#: ../Doc/library/xml.sax.rst:15 +msgid "" +"The :mod:`xml.sax` package provides a number of modules which implement the " +"Simple API for XML (SAX) interface for Python. The package itself provides " +"the SAX exceptions and the convenience functions which will be most used by " +"users of the SAX API." +msgstr "" + +#: ../Doc/library/xml.sax.rst:23 +msgid "" +"The :mod:`xml.sax` module is not secure against maliciously constructed " +"data. If you need to parse untrusted or unauthenticated data see :ref:`xml-" +"vulnerabilities`." +msgstr "" + +#: ../Doc/library/xml.sax.rst:28 +msgid "The convenience functions are:" +msgstr "" + +#: ../Doc/library/xml.sax.rst:33 +msgid "" +"Create and return a SAX :class:`~xml.sax.xmlreader.XMLReader` object. The " +"first parser found will be used. If *parser_list* is provided, it must be a " +"sequence of strings which name modules that have a function named :func:" +"`create_parser`. Modules listed in *parser_list* will be used before " +"modules in the default list of parsers." +msgstr "" + +#: ../Doc/library/xml.sax.rst:42 +msgid "" +"Create a SAX parser and use it to parse a document. The document, passed in " +"as *filename_or_stream*, can be a filename or a file object. The *handler* " +"parameter needs to be a SAX :class:`~handler.ContentHandler` instance. If " +"*error_handler* is given, it must be a SAX :class:`~handler.ErrorHandler` " +"instance; if omitted, :exc:`SAXParseException` will be raised on all " +"errors. There is no return value; all work must be done by the *handler* " +"passed in." +msgstr "" + +#: ../Doc/library/xml.sax.rst:53 +msgid "" +"Similar to :func:`parse`, but parses from a buffer *string* received as a " +"parameter. *string* must be a :class:`str` instance or a :term:`bytes-like " +"object`." +msgstr "" + +#: ../Doc/library/xml.sax.rst:57 +msgid "Added support of :class:`str` instances." +msgstr "" + +#: ../Doc/library/xml.sax.rst:60 +msgid "" +"A typical SAX application uses three kinds of objects: readers, handlers and " +"input sources. \"Reader\" in this context is another term for parser, i.e. " +"some piece of code that reads the bytes or characters from the input source, " +"and produces a sequence of events. The events then get distributed to the " +"handler objects, i.e. the reader invokes a method on the handler. A SAX " +"application must therefore obtain a reader object, create or open the input " +"sources, create the handlers, and connect these objects all together. As " +"the final step of preparation, the reader is called to parse the input. " +"During parsing, methods on the handler objects are called based on " +"structural and syntactic events from the input data." +msgstr "" + +#: ../Doc/library/xml.sax.rst:71 +msgid "" +"For these objects, only the interfaces are relevant; they are normally not " +"instantiated by the application itself. Since Python does not have an " +"explicit notion of interface, they are formally introduced as classes, but " +"applications may use implementations which do not inherit from the provided " +"classes. The :class:`~xml.sax.xmlreader.InputSource`, :class:`~xml.sax." +"xmlreader.Locator`, :class:`~xml.sax.xmlreader.Attributes`, :class:`~xml.sax." +"xmlreader.AttributesNS`, and :class:`~xml.sax.xmlreader.XMLReader` " +"interfaces are defined in the module :mod:`xml.sax.xmlreader`. The handler " +"interfaces are defined in :mod:`xml.sax.handler`. For convenience, :class:" +"`~xml.sax.xmlreader.InputSource` (which is often instantiated directly) and " +"the handler classes are also available from :mod:`xml.sax`. These " +"interfaces are described below." +msgstr "" + +#: ../Doc/library/xml.sax.rst:84 +msgid "" +"In addition to these classes, :mod:`xml.sax` provides the following " +"exception classes." +msgstr "" + +#: ../Doc/library/xml.sax.rst:90 +msgid "" +"Encapsulate an XML error or warning. This class can contain basic error or " +"warning information from either the XML parser or the application: it can be " +"subclassed to provide additional functionality or to add localization. Note " +"that although the handlers defined in the :class:`~xml.sax.handler." +"ErrorHandler` interface receive instances of this exception, it is not " +"required to actually raise the exception --- it is also useful as a " +"container for information." +msgstr "" + +#: ../Doc/library/xml.sax.rst:98 +msgid "" +"When instantiated, *msg* should be a human-readable description of the " +"error. The optional *exception* parameter, if given, should be ``None`` or " +"an exception that was caught by the parsing code and is being passed along " +"as information." +msgstr "" + +#: ../Doc/library/xml.sax.rst:102 +msgid "This is the base class for the other SAX exception classes." +msgstr "" + +#: ../Doc/library/xml.sax.rst:107 +msgid "" +"Subclass of :exc:`SAXException` raised on parse errors. Instances of this " +"class are passed to the methods of the SAX :class:`~xml.sax.handler." +"ErrorHandler` interface to provide information about the parse error. This " +"class supports the SAX :class:`~xml.sax.xmlreader.Locator` interface as well " +"as the :class:`SAXException` interface." +msgstr "" + +#: ../Doc/library/xml.sax.rst:117 +msgid "" +"Subclass of :exc:`SAXException` raised when a SAX :class:`~xml.sax.xmlreader." +"XMLReader` is confronted with an unrecognized feature or property. SAX " +"applications and extensions may use this class for similar purposes." +msgstr "" + +#: ../Doc/library/xml.sax.rst:125 +msgid "" +"Subclass of :exc:`SAXException` raised when a SAX :class:`~xml.sax.xmlreader." +"XMLReader` is asked to enable a feature that is not supported, or to set a " +"property to a value that the implementation does not support. SAX " +"applications and extensions may use this class for similar purposes." +msgstr "" + +#: ../Doc/library/xml.sax.rst:137 +msgid "`SAX: The Simple API for XML `_" +msgstr "" + +#: ../Doc/library/xml.sax.rst:135 +msgid "" +"This site is the focal point for the definition of the SAX API. It provides " +"a Java implementation and online documentation. Links to implementations " +"and historical information are also available." +msgstr "" + +#: ../Doc/library/xml.sax.rst:140 +msgid "Module :mod:`xml.sax.handler`" +msgstr "" + +#: ../Doc/library/xml.sax.rst:140 +msgid "Definitions of the interfaces for application-provided objects." +msgstr "" + +#: ../Doc/library/xml.sax.rst:143 +msgid "Module :mod:`xml.sax.saxutils`" +msgstr "" + +#: ../Doc/library/xml.sax.rst:143 +msgid "Convenience functions for use in SAX applications." +msgstr "" + +#: ../Doc/library/xml.sax.rst:145 +msgid "Module :mod:`xml.sax.xmlreader`" +msgstr "" + +#: ../Doc/library/xml.sax.rst:146 +msgid "Definitions of the interfaces for parser-provided objects." +msgstr "" + +#: ../Doc/library/xml.sax.rst:152 +msgid "SAXException Objects" +msgstr "" + +#: ../Doc/library/xml.sax.rst:154 +msgid "" +"The :class:`SAXException` exception class supports the following methods:" +msgstr "" + +#: ../Doc/library/xml.sax.rst:159 +msgid "Return a human-readable message describing the error condition." +msgstr "" + +#: ../Doc/library/xml.sax.rst:164 +msgid "Return an encapsulated exception object, or ``None``." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:2 +msgid ":mod:`xml.sax.handler` --- Base classes for SAX handlers" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:10 +msgid "**Source code:** :source:`Lib/xml/sax/handler.py`" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:14 +msgid "" +"The SAX API defines four kinds of handlers: content handlers, DTD handlers, " +"error handlers, and entity resolvers. Applications normally only need to " +"implement those interfaces whose events they are interested in; they can " +"implement the interfaces in a single object or in multiple objects. Handler " +"implementations should inherit from the base classes provided in the module :" +"mod:`xml.sax.handler`, so that all methods get default implementations." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:24 +msgid "" +"This is the main callback interface in SAX, and the one most important to " +"applications. The order of events in this interface mirrors the order of the " +"information in the document." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:31 +msgid "Handle DTD events." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:33 +msgid "" +"This interface specifies only those DTD events required for basic parsing " +"(unparsed entities and attributes)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:39 +msgid "" +"Basic interface for resolving entities. If you create an object implementing " +"this interface, then register the object with your Parser, the parser will " +"call the method in your object to resolve all external entities." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:46 +msgid "" +"Interface used by the parser to present error and warning messages to the " +"application. The methods of this object control whether errors are " +"immediately converted to exceptions or are handled in some other way." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:50 +msgid "" +"In addition to these classes, :mod:`xml.sax.handler` provides symbolic " +"constants for the feature and property names." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:56 +msgid "value: ``\"http://xml.org/sax/features/namespaces\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:57 +msgid "true: Perform Namespace processing." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:59 +msgid "" +"false: Optionally do not perform Namespace processing (implies namespace-" +"prefixes; default)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:60 ../Doc/library/xml.sax.handler.rst:70 +#: ../Doc/library/xml.sax.handler.rst:79 ../Doc/library/xml.sax.handler.rst:88 +#: ../Doc/library/xml.sax.handler.rst:96 ../Doc/library/xml.sax.handler.rst:106 +#: ../Doc/library/xml.sax.handler.rst:138 +msgid "access: (parsing) read-only; (not parsing) read/write" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:65 +msgid "value: ``\"http://xml.org/sax/features/namespace-prefixes\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:67 +msgid "" +"true: Report the original prefixed names and attributes used for Namespace " +"declarations." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:69 +msgid "" +"false: Do not report attributes used for Namespace declarations, and " +"optionally do not report original prefixed names (default)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:75 +msgid "value: ``\"http://xml.org/sax/features/string-interning\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:77 +msgid "" +"true: All element names, prefixes, attribute names, Namespace URIs, and " +"local names are interned using the built-in intern function." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:78 +msgid "" +"false: Names are not necessarily interned, although they may be (default)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:84 +msgid "value: ``\"http://xml.org/sax/features/validation\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:86 +msgid "" +"true: Report all validation errors (implies external-general-entities and " +"external-parameter-entities)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:87 +msgid "false: Do not report validation errors." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:93 +msgid "value: ``\"http://xml.org/sax/features/external-general-entities\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:94 +msgid "true: Include all external general (text) entities." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:95 +msgid "false: Do not include external general entities." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:101 +msgid "value: ``\"http://xml.org/sax/features/external-parameter-entities\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:103 +msgid "" +"true: Include all external parameter entities, including the external DTD " +"subset." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:105 +msgid "" +"false: Do not include any external parameter entities, even the external DTD " +"subset." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:111 +msgid "List of all features." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:116 +msgid "value: ``\"http://xml.org/sax/properties/lexical-handler\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:117 +msgid "data type: xml.sax.sax2lib.LexicalHandler (not supported in Python 2)" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:119 +msgid "" +"description: An optional extension handler for lexical events like comments." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:120 +#: ../Doc/library/xml.sax.handler.rst:129 +msgid "access: read/write" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:125 +msgid "value: ``\"http://xml.org/sax/properties/declaration-handler\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:126 +msgid "data type: xml.sax.sax2lib.DeclHandler (not supported in Python 2)" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:128 +msgid "" +"description: An optional extension handler for DTD-related events other than " +"notations and unparsed entities." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:134 +msgid "value: ``\"http://xml.org/sax/properties/dom-node\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:135 +msgid "data type: org.w3c.dom.Node (not supported in Python 2)" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:137 +msgid "" +"description: When parsing, the current DOM node being visited if this is a " +"DOM iterator; when not parsing, the root DOM node for iteration." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:143 +msgid "value: ``\"http://xml.org/sax/properties/xml-string\"``" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:144 +msgid "data type: String" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:146 +msgid "" +"description: The literal string of characters that was the source for the " +"current event." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:147 +msgid "access: read-only" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:152 +msgid "List of all known property names." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:158 +msgid "ContentHandler Objects" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:160 +msgid "" +"Users are expected to subclass :class:`ContentHandler` to support their " +"application. The following methods are called by the parser on the " +"appropriate events in the input document:" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:167 +msgid "" +"Called by the parser to give the application a locator for locating the " +"origin of document events." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:170 +msgid "" +"SAX parsers are strongly encouraged (though not absolutely required) to " +"supply a locator: if it does so, it must supply the locator to the " +"application by invoking this method before invoking any of the other methods " +"in the DocumentHandler interface." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:175 +msgid "" +"The locator allows the application to determine the end position of any " +"document-related event, even if the parser is not reporting an error. " +"Typically, the application will use this information for reporting its own " +"errors (such as character content that does not match an application's " +"business rules). The information returned by the locator is probably not " +"sufficient for use with a search engine." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:182 +msgid "" +"Note that the locator will return correct information only during the " +"invocation of the events in this interface. The application should not " +"attempt to use it at any other time." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:189 +msgid "Receive notification of the beginning of a document." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:191 +msgid "" +"The SAX parser will invoke this method only once, before any other methods " +"in this interface or in DTDHandler (except for :meth:`setDocumentLocator`)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:197 +msgid "Receive notification of the end of a document." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:199 +msgid "" +"The SAX parser will invoke this method only once, and it will be the last " +"method invoked during the parse. The parser shall not invoke this method " +"until it has either abandoned parsing (because of an unrecoverable error) or " +"reached the end of input." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:207 +msgid "Begin the scope of a prefix-URI Namespace mapping." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:209 +msgid "" +"The information from this event is not necessary for normal Namespace " +"processing: the SAX XML reader will automatically replace prefixes for " +"element and attribute names when the ``feature_namespaces`` feature is " +"enabled (the default)." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:214 +msgid "" +"There are cases, however, when applications need to use prefixes in " +"character data or in attribute values, where they cannot safely be expanded " +"automatically; the :meth:`startPrefixMapping` and :meth:`endPrefixMapping` " +"events supply the information to the application to expand prefixes in those " +"contexts itself, if necessary." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:222 +msgid "" +"Note that :meth:`startPrefixMapping` and :meth:`endPrefixMapping` events are " +"not guaranteed to be properly nested relative to each-other: all :meth:" +"`startPrefixMapping` events will occur before the corresponding :meth:" +"`startElement` event, and all :meth:`endPrefixMapping` events will occur " +"after the corresponding :meth:`endElement` event, but their order is not " +"guaranteed." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:232 +msgid "End the scope of a prefix-URI mapping." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:234 +msgid "" +"See :meth:`startPrefixMapping` for details. This event will always occur " +"after the corresponding :meth:`endElement` event, but the order of :meth:" +"`endPrefixMapping` events is not otherwise guaranteed." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:241 +msgid "Signals the start of an element in non-namespace mode." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:243 +msgid "" +"The *name* parameter contains the raw XML 1.0 name of the element type as a " +"string and the *attrs* parameter holds an object of the :class:`~xml.sax." +"xmlreader.Attributes` interface (see :ref:`attributes-objects`) containing " +"the attributes of the element. The object passed as *attrs* may be re-used " +"by the parser; holding on to a reference to it is not a reliable way to keep " +"a copy of the attributes. To keep a copy of the attributes, use the :meth:" +"`copy` method of the *attrs* object." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:255 +msgid "Signals the end of an element in non-namespace mode." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:257 +msgid "" +"The *name* parameter contains the name of the element type, just as with " +"the :meth:`startElement` event." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:263 +msgid "Signals the start of an element in namespace mode." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:265 +msgid "" +"The *name* parameter contains the name of the element type as a ``(uri, " +"localname)`` tuple, the *qname* parameter contains the raw XML 1.0 name used " +"in the source document, and the *attrs* parameter holds an instance of the :" +"class:`~xml.sax.xmlreader.AttributesNS` interface (see :ref:`attributes-ns-" +"objects`) containing the attributes of the element. If no namespace is " +"associated with the element, the *uri* component of *name* will be " +"``None``. The object passed as *attrs* may be re-used by the parser; " +"holding on to a reference to it is not a reliable way to keep a copy of the " +"attributes. To keep a copy of the attributes, use the :meth:`copy` method " +"of the *attrs* object." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:276 +msgid "" +"Parsers may set the *qname* parameter to ``None``, unless the " +"``feature_namespace_prefixes`` feature is activated." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:282 +msgid "Signals the end of an element in namespace mode." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:284 +msgid "" +"The *name* parameter contains the name of the element type, just as with " +"the :meth:`startElementNS` method, likewise the *qname* parameter." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:290 +msgid "Receive notification of character data." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:292 +msgid "" +"The Parser will call this method to report each chunk of character data. SAX " +"parsers may return all contiguous character data in a single chunk, or they " +"may split it into several chunks; however, all of the characters in any " +"single event must come from the same external entity so that the Locator " +"provides useful information." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:298 +msgid "" +"*content* may be a string or bytes instance; the ``expat`` reader module " +"always produces strings." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:303 +msgid "" +"The earlier SAX 1 interface provided by the Python XML Special Interest " +"Group used a more Java-like interface for this method. Since most parsers " +"used from Python did not take advantage of the older interface, the simpler " +"signature was chosen to replace it. To convert old code to the new " +"interface, use *content* instead of slicing content with the old *offset* " +"and *length* parameters." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:312 +msgid "Receive notification of ignorable whitespace in element content." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:314 +msgid "" +"Validating Parsers must use this method to report each chunk of ignorable " +"whitespace (see the W3C XML 1.0 recommendation, section 2.10): non-" +"validating parsers may also use this method if they are capable of parsing " +"and using content models." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:319 +msgid "" +"SAX parsers may return all contiguous whitespace in a single chunk, or they " +"may split it into several chunks; however, all of the characters in any " +"single event must come from the same external entity, so that the Locator " +"provides useful information." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:327 +msgid "Receive notification of a processing instruction." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:329 +msgid "" +"The Parser will invoke this method once for each processing instruction " +"found: note that processing instructions may occur before or after the main " +"document element." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:333 +msgid "" +"A SAX parser should never report an XML declaration (XML 1.0, section 2.8) " +"or a text declaration (XML 1.0, section 4.3.1) using this method." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:339 +msgid "Receive notification of a skipped entity." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:341 +msgid "" +"The Parser will invoke this method once for each entity skipped. Non-" +"validating processors may skip entities if they have not seen the " +"declarations (because, for example, the entity was declared in an external " +"DTD subset). All processors may skip external entities, depending on the " +"values of the ``feature_external_ges`` and the ``feature_external_pes`` " +"properties." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:351 +msgid "DTDHandler Objects" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:353 +msgid ":class:`DTDHandler` instances provide the following methods:" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:358 +msgid "Handle a notation declaration event." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:363 +msgid "Handle an unparsed entity declaration event." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:369 +msgid "EntityResolver Objects" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:374 +msgid "" +"Resolve the system identifier of an entity and return either the system " +"identifier to read from as a string, or an InputSource to read from. The " +"default implementation returns *systemId*." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:382 +msgid "ErrorHandler Objects" +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:384 +msgid "" +"Objects with this interface are used to receive error and warning " +"information from the :class:`~xml.sax.xmlreader.XMLReader`. If you create " +"an object that implements this interface, then register the object with " +"your :class:`~xml.sax.xmlreader.XMLReader`, the parser will call the methods " +"in your object to report all warnings and errors. There are three levels of " +"errors available: warnings, (possibly) recoverable errors, and unrecoverable " +"errors. All methods take a :exc:`SAXParseException` as the only parameter. " +"Errors and warnings may be converted to an exception by raising the passed-" +"in exception object." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:397 +msgid "" +"Called when the parser encounters a recoverable error. If this method does " +"not raise an exception, parsing may continue, but further document " +"information should not be expected by the application. Allowing the parser " +"to continue may allow additional errors to be discovered in the input " +"document." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:405 +msgid "" +"Called when the parser encounters an error it cannot recover from; parsing " +"is expected to terminate when this method returns." +msgstr "" + +#: ../Doc/library/xml.sax.handler.rst:411 +msgid "" +"Called when the parser presents minor warning information to the " +"application. Parsing is expected to continue when this method returns, and " +"document information will continue to be passed to the application. Raising " +"an exception in this method will cause parsing to end." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:2 +msgid ":mod:`xml.sax.xmlreader` --- Interface for XML parsers" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:10 +msgid "**Source code:** :source:`Lib/xml/sax/xmlreader.py`" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:14 +msgid "" +"SAX parsers implement the :class:`XMLReader` interface. They are implemented " +"in a Python module, which must provide a function :func:`create_parser`. " +"This function is invoked by :func:`xml.sax.make_parser` with no arguments " +"to create a new parser object." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:22 +msgid "Base class which can be inherited by SAX parsers." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:27 +msgid "" +"In some cases, it is desirable not to parse an input source at once, but to " +"feed chunks of the document as they get available. Note that the reader will " +"normally not read the entire file, but read it in chunks as well; still :" +"meth:`parse` won't return until the entire document is processed. So these " +"interfaces should be used if the blocking behaviour of :meth:`parse` is not " +"desirable." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:33 +msgid "" +"When the parser is instantiated it is ready to begin accepting data from the " +"feed method immediately. After parsing has been finished with a call to " +"close the reset method must be called to make the parser ready to accept new " +"data, either from feed or using the parse method." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:38 +msgid "" +"Note that these methods must *not* be called during parsing, that is, after " +"parse has been called and before it returns." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:41 +msgid "" +"By default, the class also implements the parse method of the XMLReader " +"interface using the feed, close and reset methods of the IncrementalParser " +"interface as a convenience to SAX 2.0 driver writers." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:48 +msgid "" +"Interface for associating a SAX event with a document location. A locator " +"object will return valid results only during calls to DocumentHandler " +"methods; at any other time, the results are unpredictable. If information is " +"not available, methods may return ``None``." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:56 +msgid "" +"Encapsulation of the information needed by the :class:`XMLReader` to read " +"entities." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:59 +msgid "" +"This class may include information about the public identifier, system " +"identifier, byte stream (possibly with character encoding information) and/" +"or the character stream of an entity." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:63 +msgid "" +"Applications will create objects of this class for use in the :meth:" +"`XMLReader.parse` method and for returning from EntityResolver.resolveEntity." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:67 +msgid "" +"An :class:`InputSource` belongs to the application, the :class:`XMLReader` " +"is not allowed to modify :class:`InputSource` objects passed to it from the " +"application, although it may make copies and modify those." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:74 +msgid "" +"This is an implementation of the :class:`Attributes` interface (see section :" +"ref:`attributes-objects`). This is a dictionary-like object which " +"represents the element attributes in a :meth:`startElement` call. In " +"addition to the most useful dictionary operations, it supports a number of " +"other methods as described by the interface. Objects of this class should be " +"instantiated by readers; *attrs* must be a dictionary-like object containing " +"a mapping from attribute names to attribute values." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:85 +msgid "" +"Namespace-aware variant of :class:`AttributesImpl`, which will be passed to :" +"meth:`startElementNS`. It is derived from :class:`AttributesImpl`, but " +"understands attribute names as two-tuples of *namespaceURI* and *localname*. " +"In addition, it provides a number of methods expecting qualified names as " +"they appear in the original document. This class implements the :class:" +"`AttributesNS` interface (see section :ref:`attributes-ns-objects`)." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:96 +msgid "XMLReader Objects" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:98 +msgid "The :class:`XMLReader` interface supports the following methods:" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:103 +msgid "" +"Process an input source, producing SAX events. The *source* object can be a " +"system identifier (a string identifying the input source -- typically a file " +"name or a URL), a file-like object, or an :class:`InputSource` object. When :" +"meth:`parse` returns, the input is completely processed, and the parser " +"object can be discarded or reset." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:109 +msgid "Added support of character streams." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:115 +msgid "Return the current :class:`~xml.sax.handler.ContentHandler`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:120 +msgid "" +"Set the current :class:`~xml.sax.handler.ContentHandler`. If no :class:" +"`~xml.sax.handler.ContentHandler` is set, content events will be discarded." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:127 +msgid "Return the current :class:`~xml.sax.handler.DTDHandler`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:132 +msgid "" +"Set the current :class:`~xml.sax.handler.DTDHandler`. If no :class:`~xml." +"sax.handler.DTDHandler` is set, DTD events will be discarded." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:139 +msgid "Return the current :class:`~xml.sax.handler.EntityResolver`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:144 +msgid "" +"Set the current :class:`~xml.sax.handler.EntityResolver`. If no :class:" +"`~xml.sax.handler.EntityResolver` is set, attempts to resolve an external " +"entity will result in opening the system identifier for the entity, and fail " +"if it is not available." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:152 +msgid "Return the current :class:`~xml.sax.handler.ErrorHandler`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:157 +msgid "" +"Set the current error handler. If no :class:`~xml.sax.handler.ErrorHandler` " +"is set, errors will be raised as exceptions, and warnings will be printed." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:163 +msgid "Allow an application to set the locale for errors and warnings." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:165 +msgid "" +"SAX parsers are not required to provide localization for errors and " +"warnings; if they cannot support the requested locale, however, they must " +"raise a SAX exception. Applications may request a locale change in the " +"middle of a parse." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:172 +msgid "" +"Return the current setting for feature *featurename*. If the feature is not " +"recognized, :exc:`SAXNotRecognizedException` is raised. The well-known " +"featurenames are listed in the module :mod:`xml.sax.handler`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:179 +msgid "" +"Set the *featurename* to *value*. If the feature is not recognized, :exc:" +"`SAXNotRecognizedException` is raised. If the feature or its setting is not " +"supported by the parser, *SAXNotSupportedException* is raised." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:186 +msgid "" +"Return the current setting for property *propertyname*. If the property is " +"not recognized, a :exc:`SAXNotRecognizedException` is raised. The well-known " +"propertynames are listed in the module :mod:`xml.sax.handler`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:193 +msgid "" +"Set the *propertyname* to *value*. If the property is not recognized, :exc:" +"`SAXNotRecognizedException` is raised. If the property or its setting is not " +"supported by the parser, *SAXNotSupportedException* is raised." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:201 +msgid "IncrementalParser Objects" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:203 +msgid "" +"Instances of :class:`IncrementalParser` offer the following additional " +"methods:" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:208 +msgid "Process a chunk of *data*." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:213 +msgid "" +"Assume the end of the document. That will check well-formedness conditions " +"that can be checked only at the end, invoke handlers, and may clean up " +"resources allocated during parsing." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:220 +msgid "" +"This method is called after close has been called to reset the parser so " +"that it is ready to parse new documents. The results of calling parse or " +"feed after close without calling reset are undefined." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:228 +msgid "Locator Objects" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:230 +msgid "Instances of :class:`Locator` provide these methods:" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:235 +msgid "Return the column number where the current event begins." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:240 +msgid "Return the line number where the current event begins." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:245 +msgid "Return the public identifier for the current event." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:250 +msgid "Return the system identifier for the current event." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:256 +msgid "InputSource Objects" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:261 +msgid "Sets the public identifier of this :class:`InputSource`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:266 +msgid "Returns the public identifier of this :class:`InputSource`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:271 +msgid "Sets the system identifier of this :class:`InputSource`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:276 +msgid "Returns the system identifier of this :class:`InputSource`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:281 +msgid "Sets the character encoding of this :class:`InputSource`." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:283 +msgid "" +"The encoding must be a string acceptable for an XML encoding declaration " +"(see section 4.3.3 of the XML recommendation)." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:286 +msgid "" +"The encoding attribute of the :class:`InputSource` is ignored if the :class:" +"`InputSource` also contains a character stream." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:292 +msgid "Get the character encoding of this InputSource." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:297 +msgid "Set the byte stream (a :term:`binary file`) for this input source." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:299 +msgid "" +"The SAX parser will ignore this if there is also a character stream " +"specified, but it will use a byte stream in preference to opening a URI " +"connection itself." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:302 +msgid "" +"If the application knows the character encoding of the byte stream, it " +"should set it with the setEncoding method." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:308 +msgid "Get the byte stream for this input source." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:310 +msgid "" +"The getEncoding method will return the character encoding for this byte " +"stream, or None if unknown." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:316 +msgid "Set the character stream (a :term:`text file`) for this input source." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:318 +msgid "" +"If there is a character stream specified, the SAX parser will ignore any " +"byte stream and will not attempt to open a URI connection to the system " +"identifier." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:324 +msgid "Get the character stream for this input source." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:330 +msgid "The :class:`Attributes` Interface" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:332 +msgid "" +":class:`Attributes` objects implement a portion of the :term:`mapping " +"protocol `, including the methods :meth:`~collections.abc.Mapping." +"copy`, :meth:`~collections.abc.Mapping.get`, :meth:`~object.__contains__`, :" +"meth:`~collections.abc.Mapping.items`, :meth:`~collections.abc.Mapping." +"keys`, and :meth:`~collections.abc.Mapping.values`. The following methods " +"are also provided:" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:342 +msgid "Return the number of attributes." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:347 +msgid "Return the names of the attributes." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:352 +msgid "" +"Returns the type of the attribute *name*, which is normally ``'CDATA'``." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:357 +msgid "Return the value of attribute *name*." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:366 +msgid "The :class:`AttributesNS` Interface" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:368 +msgid "" +"This interface is a subtype of the :class:`Attributes` interface (see " +"section :ref:`attributes-objects`). All methods supported by that interface " +"are also available on :class:`AttributesNS` objects." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:372 +msgid "The following methods are also available:" +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:377 +msgid "Return the value for a qualified name." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:382 +msgid "Return the ``(namespace, localname)`` pair for a qualified *name*." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:387 +msgid "Return the qualified name for a ``(namespace, localname)`` pair." +msgstr "" + +#: ../Doc/library/xml.sax.reader.rst:392 +msgid "Return the qualified names of all attributes." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:2 +msgid ":mod:`xml.sax.saxutils` --- SAX Utilities" +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:10 +msgid "**Source code:** :source:`Lib/xml/sax/saxutils.py`" +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:14 +msgid "" +"The module :mod:`xml.sax.saxutils` contains a number of classes and " +"functions that are commonly useful when creating SAX applications, either in " +"direct use, or as base classes." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:21 +msgid "Escape ``'&'``, ``'<'``, and ``'>'`` in a string of data." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:23 +msgid "" +"You can escape other strings of data by passing a dictionary as the optional " +"*entities* parameter. The keys and values must all be strings; each key " +"will be replaced with its corresponding value. The characters ``'&'``, " +"``'<'`` and ``'>'`` are always escaped, even if *entities* is provided." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:31 +msgid "Unescape ``'&'``, ``'<'``, and ``'>'`` in a string of data." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:33 +msgid "" +"You can unescape other strings of data by passing a dictionary as the " +"optional *entities* parameter. The keys and values must all be strings; " +"each key will be replaced with its corresponding value. ``'&'``, " +"``'<'``, and ``'>'`` are always unescaped, even if *entities* is " +"provided." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:41 +msgid "" +"Similar to :func:`escape`, but also prepares *data* to be used as an " +"attribute value. The return value is a quoted version of *data* with any " +"additional required replacements. :func:`quoteattr` will select a quote " +"character based on the content of *data*, attempting to avoid encoding any " +"quote characters in the string. If both single- and double-quote characters " +"are already in *data*, the double-quote characters will be encoded and " +"*data* will be wrapped in double-quotes. The resulting string can be used " +"directly as an attribute value::" +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:53 +msgid "" +"This function is useful when generating attribute values for HTML or any " +"SGML using the reference concrete syntax." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:59 +msgid "" +"This class implements the :class:`~xml.sax.handler.ContentHandler` interface " +"by writing SAX events back into an XML document. In other words, using an :" +"class:`XMLGenerator` as the content handler will reproduce the original " +"document being parsed. *out* should be a file-like object which will default " +"to *sys.stdout*. *encoding* is the encoding of the output stream which " +"defaults to ``'iso-8859-1'``. *short_empty_elements* controls the formatting " +"of elements that contain no content: if *False* (the default) they are " +"emitted as a pair of start/end tags, if set to *True* they are emitted as a " +"single self-closed tag." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:75 +msgid "" +"This class is designed to sit between an :class:`~xml.sax.xmlreader." +"XMLReader` and the client application's event handlers. By default, it does " +"nothing but pass requests up to the reader and events on to the handlers " +"unmodified, but subclasses can override specific methods to modify the event " +"stream or the configuration requests as they pass through." +msgstr "" + +#: ../Doc/library/xml.sax.utils.rst:85 +msgid "" +"This function takes an input source and an optional base URL and returns a " +"fully resolved :class:`~xml.sax.xmlreader.InputSource` object ready for " +"reading. The input source can be given as a string, a file-like object, or " +"an :class:`~xml.sax.xmlreader.InputSource` object; parsers will use this " +"function to implement the polymorphic *source* argument to their :meth:" +"`parse` method." +msgstr "" + +#: ../Doc/library/xmlrpc.rst:2 +msgid ":mod:`xmlrpc` --- XMLRPC server and client modules" +msgstr "" + +#: ../Doc/library/xmlrpc.rst:4 +msgid "" +"XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP as a " +"transport. With it, a client can call methods with parameters on a remote " +"server (the server is named by a URI) and get back structured data." +msgstr "" + +#: ../Doc/library/xmlrpc.rst:8 +msgid "" +"``xmlrpc`` is a package that collects server and client modules implementing " +"XML-RPC. The modules are:" +msgstr "" + +#: ../Doc/library/xmlrpc.rst:11 +msgid ":mod:`xmlrpc.client`" +msgstr "" + +#: ../Doc/library/xmlrpc.rst:12 +msgid ":mod:`xmlrpc.server`" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:2 +msgid ":mod:`xmlrpc.client` --- XML-RPC client access" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:10 +msgid "**Source code:** :source:`Lib/xmlrpc/client.py`" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:17 +msgid "" +"XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP(S) " +"as a transport. With it, a client can call methods with parameters on a " +"remote server (the server is named by a URI) and get back structured data. " +"This module supports writing XML-RPC client code; it handles all the details " +"of translating between conformable Python objects and XML on the wire." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:26 +msgid "" +"The :mod:`xmlrpc.client` module is not secure against maliciously " +"constructed data. If you need to parse untrusted or unauthenticated data " +"see :ref:`xml-vulnerabilities`." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:32 +msgid "" +"For HTTPS URIs, :mod:`xmlrpc.client` now performs all the necessary " +"certificate and hostname checks by default." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:39 ../Doc/library/xmlrpc.client.rst:546 +#: ../Doc/library/xmlrpc.server.rst:47 ../Doc/library/xmlrpc.server.rst:61 +#: ../Doc/library/xmlrpc.server.rst:330 +msgid "The *use_builtin_types* flag was added." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:42 +msgid "" +"A :class:`ServerProxy` instance is an object that manages communication with " +"a remote XML-RPC server. The required first argument is a URI (Uniform " +"Resource Indicator), and will normally be the URL of the server. The " +"optional second argument is a transport factory instance; by default it is " +"an internal :class:`SafeTransport` instance for https: URLs and an internal " +"HTTP :class:`Transport` instance otherwise. The optional third argument is " +"an encoding, by default UTF-8. The optional fourth argument is a debugging " +"flag." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:50 +msgid "" +"The following parameters govern the use of the returned proxy instance. If " +"*allow_none* is true, the Python constant ``None`` will be translated into " +"XML; the default behaviour is for ``None`` to raise a :exc:`TypeError`. This " +"is a commonly-used extension to the XML-RPC specification, but isn't " +"supported by all clients and servers; see `http://ontosys.com/xml-rpc/" +"extensions.php `_ for a description. The *use_builtin_types* " +"flag can be used to cause date/time values to be presented as :class:" +"`datetime.datetime` objects and binary data to be presented as :class:" +"`bytes` objects; this flag is false by default. :class:`datetime.datetime`, :" +"class:`bytes` and :class:`bytearray` objects may be passed to calls. The " +"obsolete *use_datetime* flag is similar to *use_builtin_types* but it " +"applies only to date/time values." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:65 +msgid "" +"Both the HTTP and HTTPS transports support the URL syntax extension for HTTP " +"Basic Authentication: ``http://user:pass@host:port/path``. The ``user:" +"pass`` portion will be base64-encoded as an HTTP 'Authorization' header, and " +"sent to the remote server as part of the connection process when invoking an " +"XML-RPC method. You only need to use this if the remote server requires a " +"Basic Authentication user and password. If an HTTPS URL is provided, " +"*context* may be :class:`ssl.SSLContext` and configures the SSL settings of " +"the underlying HTTPS connection." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:74 +msgid "" +"The returned instance is a proxy object with methods that can be used to " +"invoke corresponding RPC calls on the remote server. If the remote server " +"supports the introspection API, the proxy can also be used to query the " +"remote server for the methods it supports (service discovery) and fetch " +"other server-associated metadata." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:80 +msgid "" +"Types that are conformable (e.g. that can be marshalled through XML), " +"include the following (and except where noted, they are unmarshalled as the " +"same Python type):" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:87 +msgid "XML-RPC type" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:89 +msgid ":class:`bool`" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:91 +msgid "``int``, ``i1``, ``i2``, ``i4``, ``i8`` or ``biginteger``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:91 +msgid "" +":class:`int` in range from -2147483648 to 2147483647. Values get the " +"```` tag." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:96 +msgid "``double`` or ``float``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:96 +msgid ":class:`float`. Values get the ```` tag." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:99 +msgid "``string``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:101 +msgid "``array``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:101 +msgid "" +":class:`list` or :class:`tuple` containing conformable elements. Arrays are " +"returned as :class:`lists `." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:105 +msgid "``struct``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:105 +msgid "" +":class:`dict`. Keys must be strings, values may be any conformable type. " +"Objects of user-defined classes can be passed in; only their :attr:`~object." +"__dict__` attribute is transmitted." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:110 +msgid "``dateTime.iso8601``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:110 +msgid "" +":class:`DateTime` or :class:`datetime.datetime`. Returned type depends on " +"values of *use_builtin_types* and *use_datetime* flags." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:114 +msgid "``base64``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:114 +msgid "" +":class:`Binary`, :class:`bytes` or :class:`bytearray`. Returned type " +"depends on the value of the *use_builtin_types* flag." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:118 +msgid "``nil``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:118 +msgid "" +"The ``None`` constant. Passing is allowed only if *allow_none* is true." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:121 +msgid "``bigdecimal``" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:121 +msgid ":class:`decimal.Decimal`. Returned type only." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:124 +msgid "" +"This is the full set of data types supported by XML-RPC. Method calls may " +"also raise a special :exc:`Fault` instance, used to signal XML-RPC server " +"errors, or :exc:`ProtocolError` used to signal an error in the HTTP/HTTPS " +"transport layer. Both :exc:`Fault` and :exc:`ProtocolError` derive from a " +"base class called :exc:`Error`. Note that the xmlrpc client module " +"currently does not marshal instances of subclasses of built-in types." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:131 +msgid "" +"When passing strings, characters special to XML such as ``<``, ``>``, and " +"``&`` will be automatically escaped. However, it's the caller's " +"responsibility to ensure that the string is free of characters that aren't " +"allowed in XML, such as the control characters with ASCII values between 0 " +"and 31 (except, of course, tab, newline and carriage return); failing to do " +"this will result in an XML-RPC request that isn't well-formed XML. If you " +"have to pass arbitrary bytes via XML-RPC, use :class:`bytes` or :class:" +"`bytearray` classes or the :class:`Binary` wrapper class described below." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:140 +msgid "" +":class:`Server` is retained as an alias for :class:`ServerProxy` for " +"backwards compatibility. New code should use :class:`ServerProxy`." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:143 +msgid "Added the *context* argument." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:146 +msgid "" +"Added support of type tags with prefixes (e.g. ``ex:nil``). Added support of " +"unmarsalling additional types used by Apache XML-RPC implementation for " +"numerics: ``i1``, ``i2``, ``i8``, ``biginteger``, ``float`` and " +"``bigdecimal``. See http://ws.apache.org/xmlrpc/types.html for a description." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:158 +msgid "`XML-RPC HOWTO `_" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:157 +msgid "" +"A good description of XML-RPC operation and client software in several " +"languages. Contains pretty much everything an XML-RPC client developer needs " +"to know." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:161 +msgid "" +"`XML-RPC Introspection `_" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:161 +msgid "Describes the XML-RPC protocol extension for introspection." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:164 +msgid "`XML-RPC Specification `_" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:164 +msgid "The official specification." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:169 +msgid "`Unofficial XML-RPC Errata `_" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:167 +msgid "" +"Fredrik Lundh's \"unofficial errata, intended to clarify certain details in " +"the XML-RPC specification, as well as hint at 'best practices' to use when " +"designing your own XML-RPC implementations.\"" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:175 +msgid "ServerProxy Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:177 +msgid "" +"A :class:`ServerProxy` instance has a method corresponding to each remote " +"procedure call accepted by the XML-RPC server. Calling the method performs " +"an RPC, dispatched by both name and argument signature (e.g. the same method " +"name can be overloaded with multiple argument signatures). The RPC finishes " +"by returning a value, which may be either returned data in a conformant type " +"or a :class:`Fault` or :class:`ProtocolError` object indicating an error." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:184 +msgid "" +"Servers that support the XML introspection API support some common methods " +"grouped under the reserved :attr:`~ServerProxy.system` attribute:" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:190 +msgid "" +"This method returns a list of strings, one for each (non-system) method " +"supported by the XML-RPC server." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:196 +msgid "" +"This method takes one parameter, the name of a method implemented by the XML-" +"RPC server. It returns an array of possible signatures for this method. A " +"signature is an array of types. The first of these types is the return type " +"of the method, the rest are parameters." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:201 +msgid "" +"Because multiple signatures (ie. overloading) is permitted, this method " +"returns a list of signatures rather than a singleton." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:204 +msgid "" +"Signatures themselves are restricted to the top level parameters expected by " +"a method. For instance if a method expects one array of structs as a " +"parameter, and it returns a string, its signature is simply \"string, array" +"\". If it expects three integers and returns a string, its signature is " +"\"string, int, int, int\"." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:209 +msgid "" +"If no signature is defined for the method, a non-array value is returned. In " +"Python this means that the type of the returned value will be something " +"other than list." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:216 +msgid "" +"This method takes one parameter, the name of a method implemented by the XML-" +"RPC server. It returns a documentation string describing the use of that " +"method. If no such string is available, an empty string is returned. The " +"documentation string may contain HTML markup." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:223 +msgid "" +"Instances of :class:`ServerProxy` support the :term:`context manager` " +"protocol for closing the underlying transport." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:227 ../Doc/library/xmlrpc.client.rst:273 +msgid "A working example follows. The server code::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:239 ../Doc/library/xmlrpc.client.rst:288 +#: ../Doc/library/xmlrpc.client.rst:398 ../Doc/library/xmlrpc.client.rst:504 +msgid "The client code for the preceding server::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:250 +msgid "DateTime Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:254 +msgid "" +"This class may be initialized with seconds since the epoch, a time tuple, an " +"ISO 8601 time/date string, or a :class:`datetime.datetime` instance. It has " +"the following methods, supported mainly for internal use by the marshalling/" +"unmarshalling code:" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:262 +msgid "Accept a string as the instance's new time value." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:267 +msgid "" +"Write the XML-RPC encoding of this :class:`DateTime` item to the *out* " +"stream object." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:270 +msgid "" +"It also supports certain of Python's built-in operators through rich " +"comparison and :meth:`__repr__` methods." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:303 +msgid "Binary Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:307 +msgid "" +"This class may be initialized from bytes data (which may include NULs). The " +"primary access to the content of a :class:`Binary` object is provided by an " +"attribute:" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:314 +msgid "" +"The binary data encapsulated by the :class:`Binary` instance. The data is " +"provided as a :class:`bytes` object." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:317 +msgid "" +":class:`Binary` objects have the following methods, supported mainly for " +"internal use by the marshalling/unmarshalling code:" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:323 +msgid "" +"Accept a base64 :class:`bytes` object and decode it as the instance's new " +"data." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:328 +msgid "" +"Write the XML-RPC base 64 encoding of this binary item to the *out* stream " +"object." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:330 +msgid "" +"The encoded data will have newlines every 76 characters as per `RFC 2045 " +"section 6.8 `_, which was " +"the de facto standard base64 specification when the XML-RPC spec was written." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:335 +msgid "" +"It also supports certain of Python's built-in operators through :meth:" +"`__eq__` and :meth:`__ne__` methods." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:338 +msgid "" +"Example usage of the binary objects. We're going to transfer an image over " +"XMLRPC::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:354 +msgid "The client gets the image and saves it to a file::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:365 +msgid "Fault Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:369 +msgid "" +"A :class:`Fault` object encapsulates the content of an XML-RPC fault tag. " +"Fault objects have the following attributes:" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:375 +msgid "A string indicating the fault type." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:380 +msgid "A string containing a diagnostic message associated with the fault." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:382 +msgid "" +"In the following example we're going to intentionally cause a :exc:`Fault` " +"by returning a complex type object. The server code::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:415 +msgid "ProtocolError Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:419 +msgid "" +"A :class:`ProtocolError` object describes a protocol error in the underlying " +"transport layer (such as a 404 'not found' error if the server named by the " +"URI does not exist). It has the following attributes:" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:426 +msgid "The URI or URL that triggered the error." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:431 +msgid "The error code." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:436 +msgid "The error message or diagnostic string." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:441 +msgid "" +"A dict containing the headers of the HTTP/HTTPS request that triggered the " +"error." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:444 +msgid "" +"In the following example we're going to intentionally cause a :exc:" +"`ProtocolError` by providing an invalid URI::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:462 +msgid "MultiCall Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:464 +msgid "" +"The :class:`MultiCall` object provides a way to encapsulate multiple calls " +"to a remote server into a single request [#]_." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:470 +msgid "" +"Create an object used to boxcar method calls. *server* is the eventual " +"target of the call. Calls can be made to the result object, but they will " +"immediately return ``None``, and only store the call name and parameters in " +"the :class:`MultiCall` object. Calling the object itself causes all stored " +"calls to be transmitted as a single ``system.multicall`` request. The result " +"of this call is a :term:`generator`; iterating over this generator yields " +"the individual results." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:478 +msgid "A usage example of this class follows. The server code::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:520 +msgid "Convenience Functions" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:524 +msgid "" +"Convert *params* into an XML-RPC request. or into a response if " +"*methodresponse* is true. *params* can be either a tuple of arguments or an " +"instance of the :exc:`Fault` exception class. If *methodresponse* is true, " +"only a single value can be returned, meaning that *params* must be of length " +"1. *encoding*, if supplied, is the encoding to use in the generated XML; the " +"default is UTF-8. Python's :const:`None` value cannot be used in standard " +"XML-RPC; to allow using it via an extension, provide a true value for " +"*allow_none*." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:535 +msgid "" +"Convert an XML-RPC request or response into Python objects, a ``(params, " +"methodname)``. *params* is a tuple of argument; *methodname* is a string, " +"or ``None`` if no method name is present in the packet. If the XML-RPC " +"packet represents a fault condition, this function will raise a :exc:`Fault` " +"exception. The *use_builtin_types* flag can be used to cause date/time " +"values to be presented as :class:`datetime.datetime` objects and binary data " +"to be presented as :class:`bytes` objects; this flag is false by default." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:543 +msgid "" +"The obsolete *use_datetime* flag is similar to *use_builtin_types* but it " +"applies only to date/time values." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:553 +msgid "Example of Client Usage" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:570 +msgid "" +"To access an XML-RPC server through a HTTP proxy, you need to define a " +"custom transport. The following example shows how::" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:595 +msgid "Example of Client and Server Usage" +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:597 +msgid "See :ref:`simplexmlrpcserver-example`." +msgstr "" + +#: ../Doc/library/xmlrpc.client.rst:602 +msgid "" +"This approach has been first presented in `a discussion on xmlrpc.com " +"`_." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:2 +msgid ":mod:`xmlrpc.server` --- Basic XML-RPC servers" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:10 +msgid "**Source code:** :source:`Lib/xmlrpc/server.py`" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:14 +msgid "" +"The :mod:`xmlrpc.server` module provides a basic server framework for XML-" +"RPC servers written in Python. Servers can either be free standing, using :" +"class:`SimpleXMLRPCServer`, or embedded in a CGI environment, using :class:" +"`CGIXMLRPCRequestHandler`." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:22 +msgid "" +"The :mod:`xmlrpc.server` module is not secure against maliciously " +"constructed data. If you need to parse untrusted or unauthenticated data " +"see :ref:`xml-vulnerabilities`." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:31 +msgid "" +"Create a new server instance. This class provides methods for registration " +"of functions that can be called by the XML-RPC protocol. The " +"*requestHandler* parameter should be a factory for request handler " +"instances; it defaults to :class:`SimpleXMLRPCRequestHandler`. The *addr* " +"and *requestHandler* parameters are passed to the :class:`socketserver." +"TCPServer` constructor. If *logRequests* is true (the default), requests " +"will be logged; setting this parameter to false will turn off logging. The " +"*allow_none* and *encoding* parameters are passed on to :mod:`xmlrpc.client` " +"and control the XML-RPC responses that will be returned from the server. The " +"*bind_and_activate* parameter controls whether :meth:`server_bind` and :meth:" +"`server_activate` are called immediately by the constructor; it defaults to " +"true. Setting it to false allows code to manipulate the " +"*allow_reuse_address* class variable before the address is bound. The " +"*use_builtin_types* parameter is passed to the :func:`~xmlrpc.client.loads` " +"function and controls which types are processed when date/times values or " +"binary data are received; it defaults to false." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:54 +msgid "" +"Create a new instance to handle XML-RPC requests in a CGI environment. The " +"*allow_none* and *encoding* parameters are passed on to :mod:`xmlrpc.client` " +"and control the XML-RPC responses that will be returned from the server. The " +"*use_builtin_types* parameter is passed to the :func:`~xmlrpc.client.loads` " +"function and controls which types are processed when date/times values or " +"binary data are received; it defaults to false." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:67 +msgid "" +"Create a new request handler instance. This request handler supports " +"``POST`` requests and modifies logging so that the *logRequests* parameter " +"to the :class:`SimpleXMLRPCServer` constructor parameter is honored." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:75 +msgid "SimpleXMLRPCServer Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:77 +msgid "" +"The :class:`SimpleXMLRPCServer` class is based on :class:`socketserver." +"TCPServer` and provides a means of creating simple, stand alone XML-RPC " +"servers." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:84 +msgid "" +"Register a function that can respond to XML-RPC requests. If *name* is " +"given, it will be the method name associated with *function*, otherwise " +"``function.__name__`` will be used. *name* can be either a normal or " +"Unicode string, and may contain characters not legal in Python identifiers, " +"including the period character." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:93 +msgid "" +"Register an object which is used to expose method names which have not been " +"registered using :meth:`register_function`. If *instance* contains a :meth:" +"`_dispatch` method, it is called with the requested method name and the " +"parameters from the request. Its API is ``def _dispatch(self, method, " +"params)`` (note that *params* does not represent a variable argument list). " +"If it calls an underlying function to perform its task, that function is " +"called as ``func(*params)``, expanding the parameter list. The return value " +"from :meth:`_dispatch` is returned to the client as the result. If " +"*instance* does not have a :meth:`_dispatch` method, it is searched for an " +"attribute matching the name of the requested method." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:104 +msgid "" +"If the optional *allow_dotted_names* argument is true and the instance does " +"not have a :meth:`_dispatch` method, then if the requested method name " +"contains periods, each component of the method name is searched for " +"individually, with the effect that a simple hierarchical search is " +"performed. The value found from this search is then called with the " +"parameters from the request, and the return value is passed back to the " +"client." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:113 +msgid "" +"Enabling the *allow_dotted_names* option allows intruders to access your " +"module's global variables and may allow intruders to execute arbitrary code " +"on your machine. Only use this option on a secure, closed network." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:120 +msgid "" +"Registers the XML-RPC introspection functions ``system.listMethods``, " +"``system.methodHelp`` and ``system.methodSignature``." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:126 +msgid "Registers the XML-RPC multicall function system.multicall." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:131 +msgid "" +"An attribute value that must be a tuple listing valid path portions of the " +"URL for receiving XML-RPC requests. Requests posted to other paths will " +"result in a 404 \"no such page\" HTTP error. If this tuple is empty, all " +"paths will be considered valid. The default value is ``('/', '/RPC2')``." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:140 +msgid "SimpleXMLRPCServer Example" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:141 +msgid "Server code::" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:175 +msgid "" +"The following client code will call the methods made available by the " +"preceding server::" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:188 +msgid "" +"The following example included in the :file:`Lib/xmlrpc/server.py` module " +"shows a server allowing dotted names and registering a multicall function." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:193 +msgid "" +"Enabling the *allow_dotted_names* option allows intruders to access your " +"module's global variables and may allow intruders to execute arbitrary code " +"on your machine. Only use this example only within a secure, closed network." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:222 +msgid "This ExampleService demo can be invoked from the command line::" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:227 +msgid "" +"The client that interacts with the above server is included in `Lib/xmlrpc/" +"client.py`::" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:247 +msgid "" +"This client which interacts with the demo XMLRPC server can be invoked as::" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:253 +msgid "CGIXMLRPCRequestHandler" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:255 +msgid "" +"The :class:`CGIXMLRPCRequestHandler` class can be used to handle XML-RPC " +"requests sent to Python CGI scripts." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:261 +msgid "" +"Register a function that can respond to XML-RPC requests. If *name* is " +"given, it will be the method name associated with function, otherwise " +"*function.__name__* will be used. *name* can be either a normal or Unicode " +"string, and may contain characters not legal in Python identifiers, " +"including the period character." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:270 +msgid "" +"Register an object which is used to expose method names which have not been " +"registered using :meth:`register_function`. If instance contains a :meth:" +"`_dispatch` method, it is called with the requested method name and the " +"parameters from the request; the return value is returned to the client as " +"the result. If instance does not have a :meth:`_dispatch` method, it is " +"searched for an attribute matching the name of the requested method; if the " +"requested method name contains periods, each component of the method name " +"is searched for individually, with the effect that a simple hierarchical " +"search is performed. The value found from this search is then called with " +"the parameters from the request, and the return value is passed back to " +"the client." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:284 +msgid "" +"Register the XML-RPC introspection functions ``system.listMethods``, " +"``system.methodHelp`` and ``system.methodSignature``." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:290 +msgid "Register the XML-RPC multicall function ``system.multicall``." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:295 +msgid "" +"Handle an XML-RPC request. If *request_text* is given, it should be the POST " +"data provided by the HTTP server, otherwise the contents of stdin will be " +"used." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:314 +msgid "Documenting XMLRPC server" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:316 +msgid "" +"These classes extend the above classes to serve HTML documentation in " +"response to HTTP GET requests. Servers can either be free standing, using :" +"class:`DocXMLRPCServer`, or embedded in a CGI environment, using :class:" +"`DocCGIXMLRPCRequestHandler`." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:326 +msgid "" +"Create a new server instance. All parameters have the same meaning as for :" +"class:`SimpleXMLRPCServer`; *requestHandler* defaults to :class:" +"`DocXMLRPCRequestHandler`." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:336 +msgid "Create a new instance to handle XML-RPC requests in a CGI environment." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:341 +msgid "" +"Create a new request handler instance. This request handler supports XML-RPC " +"POST requests, documentation GET requests, and modifies logging so that the " +"*logRequests* parameter to the :class:`DocXMLRPCServer` constructor " +"parameter is honored." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:350 +msgid "DocXMLRPCServer Objects" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:352 +msgid "" +"The :class:`DocXMLRPCServer` class is derived from :class:" +"`SimpleXMLRPCServer` and provides a means of creating self-documenting, " +"stand alone XML-RPC servers. HTTP POST requests are handled as XML-RPC " +"method calls. HTTP GET requests are handled by generating pydoc-style HTML " +"documentation. This allows a server to provide its own web-based " +"documentation." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:361 ../Doc/library/xmlrpc.server.rst:389 +msgid "" +"Set the title used in the generated HTML documentation. This title will be " +"used inside the HTML \"title\" element." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:367 ../Doc/library/xmlrpc.server.rst:395 +msgid "" +"Set the name used in the generated HTML documentation. This name will appear " +"at the top of the generated documentation inside a \"h1\" element." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:373 ../Doc/library/xmlrpc.server.rst:401 +msgid "" +"Set the description used in the generated HTML documentation. This " +"description will appear as a paragraph, below the server name, in the " +"documentation." +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:378 +msgid "DocCGIXMLRPCRequestHandler" +msgstr "" + +#: ../Doc/library/xmlrpc.server.rst:380 +msgid "" +"The :class:`DocCGIXMLRPCRequestHandler` class is derived from :class:" +"`CGIXMLRPCRequestHandler` and provides a means of creating self-documenting, " +"XML-RPC CGI scripts. HTTP POST requests are handled as XML-RPC method calls. " +"HTTP GET requests are handled by generating pydoc-style HTML documentation. " +"This allows a server to provide its own web-based documentation." +msgstr "" + +#: ../Doc/library/zipapp.rst:2 +msgid ":mod:`zipapp` --- Manage executable python zip archives" +msgstr "" + +#: ../Doc/library/zipapp.rst:9 +msgid "**Source code:** :source:`Lib/zipapp.py`" +msgstr "" + +#: ../Doc/library/zipapp.rst:16 +msgid "" +"This module provides tools to manage the creation of zip files containing " +"Python code, which can be :ref:`executed directly by the Python interpreter " +"`. The module provides both a :ref:`zipapp-" +"command-line-interface` and a :ref:`zipapp-python-api`." +msgstr "" + +#: ../Doc/library/zipapp.rst:23 +msgid "Basic Example" +msgstr "" + +#: ../Doc/library/zipapp.rst:25 +msgid "" +"The following example shows how the :ref:`zipapp-command-line-interface` can " +"be used to create an executable archive from a directory containing Python " +"code. When run, the archive will execute the ``main`` function from the " +"module ``myapp`` in the archive." +msgstr "" + +#: ../Doc/library/zipapp.rst:42 +msgid "" +"When called as a program from the command line, the following form is used:" +msgstr "" + +#: ../Doc/library/zipapp.rst:48 +msgid "" +"If *source* is a directory, this will create an archive from the contents of " +"*source*. If *source* is a file, it should be an archive, and it will be " +"copied to the target archive (or the contents of its shebang line will be " +"displayed if the --info option is specified)." +msgstr "" + +#: ../Doc/library/zipapp.rst:53 +msgid "The following options are understood:" +msgstr "" + +#: ../Doc/library/zipapp.rst:59 +msgid "" +"Write the output to a file named *output*. If this option is not specified, " +"the output filename will be the same as the input *source*, with the " +"extension ``.pyz`` added. If an explicit filename is given, it is used as " +"is (so a ``.pyz`` extension should be included if required)." +msgstr "" + +#: ../Doc/library/zipapp.rst:64 +msgid "" +"An output filename must be specified if the *source* is an archive (and in " +"that case, *output* must not be the same as *source*)." +msgstr "" + +#: ../Doc/library/zipapp.rst:69 +msgid "" +"Add a ``#!`` line to the archive specifying *interpreter* as the command to " +"run. Also, on POSIX, make the archive executable. The default is to write " +"no ``#!`` line, and not make the file executable." +msgstr "" + +#: ../Doc/library/zipapp.rst:75 +msgid "" +"Write a ``__main__.py`` file to the archive that executes *mainfn*. The " +"*mainfn* argument should have the form \"pkg.mod:fn\", where \"pkg.mod\" is " +"a package/module in the archive, and \"fn\" is a callable in the given " +"module. The ``__main__.py`` file will execute that callable." +msgstr "" + +#: ../Doc/library/zipapp.rst:80 +msgid ":option:`--main` cannot be specified when copying an archive." +msgstr "" + +#: ../Doc/library/zipapp.rst:84 +msgid "" +"Display the interpreter embedded in the archive, for diagnostic purposes. " +"In this case, any other options are ignored and SOURCE must be an archive, " +"not a directory." +msgstr "" + +#: ../Doc/library/zipapp.rst:90 +msgid "Print a short usage message and exit." +msgstr "" + +#: ../Doc/library/zipapp.rst:96 +msgid "Python API" +msgstr "" + +#: ../Doc/library/zipapp.rst:98 +msgid "The module defines two convenience functions:" +msgstr "" + +#: ../Doc/library/zipapp.rst:103 +msgid "" +"Create an application archive from *source*. The source can be any of the " +"following:" +msgstr "" + +#: ../Doc/library/zipapp.rst:106 +msgid "" +"The name of a directory, or a :class:`pathlib.Path` object referring to a " +"directory, in which case a new application archive will be created from the " +"content of that directory." +msgstr "" + +#: ../Doc/library/zipapp.rst:109 +msgid "" +"The name of an existing application archive file, or a :class:`pathlib.Path` " +"object referring to such a file, in which case the file is copied to the " +"target (modifying it to reflect the value given for the *interpreter* " +"argument). The file name should include the ``.pyz`` extension, if required." +msgstr "" + +#: ../Doc/library/zipapp.rst:113 +msgid "" +"A file object open for reading in bytes mode. The content of the file " +"should be an application archive, and the file object is assumed to be " +"positioned at the start of the archive." +msgstr "" + +#: ../Doc/library/zipapp.rst:117 +msgid "" +"The *target* argument determines where the resulting archive will be written:" +msgstr "" + +#: ../Doc/library/zipapp.rst:120 +msgid "" +"If it is the name of a file, or a :class:`pathlb.Path` object, the archive " +"will be written to that file." +msgstr "" + +#: ../Doc/library/zipapp.rst:122 +msgid "" +"If it is an open file object, the archive will be written to that file " +"object, which must be open for writing in bytes mode." +msgstr "" + +#: ../Doc/library/zipapp.rst:124 +msgid "" +"If the target is omitted (or None), the source must be a directory and the " +"target will be a file with the same name as the source, with a ``.pyz`` " +"extension added." +msgstr "" + +#: ../Doc/library/zipapp.rst:128 +msgid "" +"The *interpreter* argument specifies the name of the Python interpreter with " +"which the archive will be executed. It is written as a \"shebang\" line at " +"the start of the archive. On POSIX, this will be interpreted by the OS, and " +"on Windows it will be handled by the Python launcher. Omitting the " +"*interpreter* results in no shebang line being written. If an interpreter " +"is specified, and the target is a filename, the executable bit of the target " +"file will be set." +msgstr "" + +#: ../Doc/library/zipapp.rst:136 +msgid "" +"The *main* argument specifies the name of a callable which will be used as " +"the main program for the archive. It can only be specified if the source is " +"a directory, and the source does not already contain a ``__main__.py`` " +"file. The *main* argument should take the form \"pkg.module:callable\" and " +"the archive will be run by importing \"pkg.module\" and executing the given " +"callable with no arguments. It is an error to omit *main* if the source is " +"a directory and does not contain a ``__main__.py`` file, as otherwise the " +"resulting archive would not be executable." +msgstr "" + +#: ../Doc/library/zipapp.rst:146 +msgid "" +"If a file object is specified for *source* or *target*, it is the caller's " +"responsibility to close it after calling create_archive." +msgstr "" + +#: ../Doc/library/zipapp.rst:149 +msgid "" +"When copying an existing archive, file objects supplied only need ``read`` " +"and ``readline``, or ``write`` methods. When creating an archive from a " +"directory, if the target is a file object it will be passed to the ``zipfile." +"ZipFile`` class, and must supply the methods needed by that class." +msgstr "" + +#: ../Doc/library/zipapp.rst:157 +msgid "" +"Return the interpreter specified in the ``#!`` line at the start of the " +"archive. If there is no ``#!`` line, return :const:`None`. The *archive* " +"argument can be a filename or a file-like object open for reading in bytes " +"mode. It is assumed to be at the start of the archive." +msgstr "" + +#: ../Doc/library/zipapp.rst:168 +msgid "Pack up a directory into an archive, and run it." +msgstr "" + +#: ../Doc/library/zipapp.rst:176 +msgid "The same can be done using the :func:`create_archive` functon::" +msgstr "" + +#: ../Doc/library/zipapp.rst:181 +msgid "" +"To make the application directly executable on POSIX, specify an interpreter " +"to use." +msgstr "" + +#: ../Doc/library/zipapp.rst:190 +msgid "" +"To replace the shebang line on an existing archive, create a modified " +"archive using the :func:`create_archive` function::" +msgstr "" + +#: ../Doc/library/zipapp.rst:196 +msgid "" +"To update the file in place, do the replacement in memory using a :class:" +"`BytesIO` object, and then overwrite the source afterwards. Note that there " +"is a risk when overwriting a file in place that an error will result in the " +"loss of the original file. This code does not protect against such errors, " +"but production code should do so. Also, this method will only work if the " +"archive fits in memory::" +msgstr "" + +#: ../Doc/library/zipapp.rst:210 +msgid "" +"Note that if you specify an interpreter and then distribute your application " +"archive, you need to ensure that the interpreter used is portable. The " +"Python launcher for Windows supports most common forms of POSIX ``#!`` line, " +"but there are other issues to consider:" +msgstr "" + +#: ../Doc/library/zipapp.rst:215 +msgid "" +"If you use \"/usr/bin/env python\" (or other forms of the \"python\" " +"command, such as \"/usr/bin/python\"), you need to consider that your users " +"may have either Python 2 or Python 3 as their default, and write your code " +"to work under both versions." +msgstr "" + +#: ../Doc/library/zipapp.rst:219 +msgid "" +"If you use an explicit version, for example \"/usr/bin/env python3\" your " +"application will not work for users who do not have that version. (This may " +"be what you want if you have not made your code Python 2 compatible)." +msgstr "" + +#: ../Doc/library/zipapp.rst:222 +msgid "" +"There is no way to say \"python X.Y or later\", so be careful of using an " +"exact version like \"/usr/bin/env python3.4\" as you will need to change " +"your shebang line for users of Python 3.5, for example." +msgstr "" + +#: ../Doc/library/zipapp.rst:227 +msgid "The Python Zip Application Archive Format" +msgstr "" + +#: ../Doc/library/zipapp.rst:229 +msgid "" +"Python has been able to execute zip files which contain a ``__main__.py`` " +"file since version 2.6. In order to be executed by Python, an application " +"archive simply has to be a standard zip file containing a ``__main__.py`` " +"file which will be run as the entry point for the application. As usual for " +"any Python script, the parent of the script (in this case the zip file) will " +"be placed on :data:`sys.path` and thus further modules can be imported from " +"the zip file." +msgstr "" + +#: ../Doc/library/zipapp.rst:236 +msgid "" +"The zip file format allows arbitrary data to be prepended to a zip file. " +"The zip application format uses this ability to prepend a standard POSIX " +"\"shebang\" line to the file (``#!/path/to/interpreter``)." +msgstr "" + +#: ../Doc/library/zipapp.rst:240 +msgid "Formally, the Python zip application format is therefore:" +msgstr "" + +#: ../Doc/library/zipapp.rst:242 +msgid "" +"An optional shebang line, containing the characters ``b'#!'`` followed by an " +"interpreter name, and then a newline (``b'\\n'``) character. The " +"interpreter name can be anything acceptable to the OS \"shebang\" " +"processing, or the Python launcher on Windows. The interpreter should be " +"encoded in UTF-8 on Windows, and in :func:`sys.getfilesystemencoding()` on " +"POSIX." +msgstr "" + +#: ../Doc/library/zipapp.rst:247 +msgid "" +"Standard zipfile data, as generated by the :mod:`zipfile` module. The " +"zipfile content *must* include a file called ``__main__.py`` (which must be " +"in the \"root\" of the zipfile - i.e., it cannot be in a subdirectory). The " +"zipfile data can be compressed or uncompressed." +msgstr "" + +#: ../Doc/library/zipapp.rst:252 +msgid "" +"If an application archive has a shebang line, it may have the executable bit " +"set on POSIX systems, to allow it to be executed directly." +msgstr "" + +#: ../Doc/library/zipapp.rst:255 +msgid "" +"There is no requirement that the tools in this module are used to create " +"application archives - the module is a convenience, but archives in the " +"above format created by any means are acceptable to Python." +msgstr "" + +#: ../Doc/library/zipfile.rst:2 +msgid ":mod:`zipfile` --- Work with ZIP archives" +msgstr "" + +#: ../Doc/library/zipfile.rst:10 +msgid "**Source code:** :source:`Lib/zipfile.py`" +msgstr "" + +#: ../Doc/library/zipfile.rst:14 +msgid "" +"The ZIP file format is a common archive and compression standard. This " +"module provides tools to create, read, write, append, and list a ZIP file. " +"Any advanced use of this module will require an understanding of the format, " +"as defined in `PKZIP Application Note`_." +msgstr "" + +#: ../Doc/library/zipfile.rst:19 +msgid "" +"This module does not currently handle multi-disk ZIP files. It can handle " +"ZIP files that use the ZIP64 extensions (that is ZIP files that are more " +"than 4 GiB in size). It supports decryption of encrypted files in ZIP " +"archives, but it currently cannot create an encrypted file. Decryption is " +"extremely slow as it is implemented in native Python rather than C." +msgstr "" + +#: ../Doc/library/zipfile.rst:30 +msgid "The error raised for bad ZIP files." +msgstr "" + +#: ../Doc/library/zipfile.rst:37 +msgid "" +"Alias of :exc:`BadZipFile`, for compatibility with older Python versions." +msgstr "" + +#: ../Doc/library/zipfile.rst:44 +msgid "" +"The error raised when a ZIP file would require ZIP64 functionality but that " +"has not been enabled." +msgstr "" + +#: ../Doc/library/zipfile.rst:51 +msgid "" +"The class for reading and writing ZIP files. See section :ref:`zipfile-" +"objects` for constructor details." +msgstr "" + +#: ../Doc/library/zipfile.rst:58 +msgid "Class for creating ZIP archives containing Python libraries." +msgstr "" + +#: ../Doc/library/zipfile.rst:63 +msgid "" +"Class used to represent information about a member of an archive. Instances " +"of this class are returned by the :meth:`.getinfo` and :meth:`.infolist` " +"methods of :class:`ZipFile` objects. Most users of the :mod:`zipfile` " +"module will not need to create these, but only use those created by this " +"module. *filename* should be the full name of the archive member, and " +"*date_time* should be a tuple containing six fields which describe the time " +"of the last modification to the file; the fields are described in section :" +"ref:`zipinfo-objects`." +msgstr "" + +#: ../Doc/library/zipfile.rst:75 +msgid "" +"Returns ``True`` if *filename* is a valid ZIP file based on its magic " +"number, otherwise returns ``False``. *filename* may be a file or file-like " +"object too." +msgstr "" + +#: ../Doc/library/zipfile.rst:78 +msgid "Support for file and file-like objects." +msgstr "" + +#: ../Doc/library/zipfile.rst:84 +msgid "The numeric constant for an uncompressed archive member." +msgstr "" + +#: ../Doc/library/zipfile.rst:89 +msgid "" +"The numeric constant for the usual ZIP compression method. This requires " +"the :mod:`zlib` module." +msgstr "" + +#: ../Doc/library/zipfile.rst:95 +msgid "" +"The numeric constant for the BZIP2 compression method. This requires the :" +"mod:`bz2` module." +msgstr "" + +#: ../Doc/library/zipfile.rst:102 +msgid "" +"The numeric constant for the LZMA compression method. This requires the :" +"mod:`lzma` module." +msgstr "" + +#: ../Doc/library/zipfile.rst:109 +msgid "" +"The ZIP file format specification has included support for bzip2 compression " +"since 2001, and for LZMA compression since 2006. However, some tools " +"(including older Python releases) do not support these compression methods, " +"and may either refuse to process the ZIP file altogether, or fail to extract " +"individual files." +msgstr "" + +#: ../Doc/library/zipfile.rst:120 +msgid "`PKZIP Application Note`_" +msgstr "" + +#: ../Doc/library/zipfile.rst:119 ../Doc/library/zipimport.rst:36 +msgid "" +"Documentation on the ZIP file format by Phil Katz, the creator of the format " +"and algorithms used." +msgstr "" + +#: ../Doc/library/zipfile.rst:123 +msgid "`Info-ZIP Home Page `_" +msgstr "" + +#: ../Doc/library/zipfile.rst:123 +msgid "" +"Information about the Info-ZIP project's ZIP archive programs and " +"development libraries." +msgstr "" + +#: ../Doc/library/zipfile.rst:130 +msgid "ZipFile Objects" +msgstr "" + +#: ../Doc/library/zipfile.rst:135 +msgid "" +"Open a ZIP file, where *file* can be either a path to a file (a string) or a " +"file-like object. The *mode* parameter should be ``'r'`` to read an " +"existing file, ``'w'`` to truncate and write a new file, ``'a'`` to append " +"to an existing file, or ``'x'`` to exclusively create and write a new file. " +"If *mode* is ``'x'`` and *file* refers to an existing file, a :exc:" +"`FileExistsError` will be raised. If *mode* is ``'a'`` and *file* refers to " +"an existing ZIP file, then additional files are added to it. If *file* does " +"not refer to a ZIP file, then a new ZIP archive is appended to the file. " +"This is meant for adding a ZIP archive to another file (such as :file:" +"`python.exe`). If *mode* is ``'a'`` and the file does not exist at all, it " +"is created. If *mode* is ``'r'`` or ``'a'``, the file should be seekable. " +"*compression* is the ZIP compression method to use when writing the archive, " +"and should be :const:`ZIP_STORED`, :const:`ZIP_DEFLATED`, :const:`ZIP_BZIP2` " +"or :const:`ZIP_LZMA`; unrecognized values will cause :exc:" +"`NotImplementedError` to be raised. If :const:`ZIP_DEFLATED`, :const:" +"`ZIP_BZIP2` or :const:`ZIP_LZMA` is specified but the corresponding module (:" +"mod:`zlib`, :mod:`bz2` or :mod:`lzma`) is not available, :exc:`RuntimeError` " +"is raised. The default is :const:`ZIP_STORED`. If *allowZip64* is ``True`` " +"(the default) zipfile will create ZIP files that use the ZIP64 extensions " +"when the zipfile is larger than 2 GiB. If it is false :mod:`zipfile` will " +"raise an exception when the ZIP file would require ZIP64 extensions." +msgstr "" + +#: ../Doc/library/zipfile.rst:158 +msgid "" +"If the file is created with mode ``'w'``, ``'x'`` or ``'a'`` and then :meth:" +"`closed ` without adding any files to the archive, the appropriate " +"ZIP structures for an empty archive will be written to the file." +msgstr "" + +#: ../Doc/library/zipfile.rst:162 +msgid "" +"ZipFile is also a context manager and therefore supports the :keyword:`with` " +"statement. In the example, *myzip* is closed after the :keyword:`with` " +"statement's suite is finished---even if an exception occurs::" +msgstr "" + +#: ../Doc/library/zipfile.rst:169 +msgid "Added the ability to use :class:`ZipFile` as a context manager." +msgstr "" + +#: ../Doc/library/zipfile.rst:172 +msgid "Added support for :mod:`bzip2 ` and :mod:`lzma` compression." +msgstr "" + +#: ../Doc/library/zipfile.rst:175 ../Doc/library/zipfile.rst:436 +msgid "ZIP64 extensions are enabled by default." +msgstr "" + +#: ../Doc/library/zipfile.rst:178 +msgid "" +"Added support for writing to unseekable streams. Added support for the " +"``'x'`` mode." +msgstr "" + +#: ../Doc/library/zipfile.rst:182 +msgid "" +"Previously, a plain :exc:`RuntimeError` was raised for unrecognized " +"compression values." +msgstr "" + +#: ../Doc/library/zipfile.rst:189 +msgid "" +"Close the archive file. You must call :meth:`close` before exiting your " +"program or essential records will not be written." +msgstr "" + +#: ../Doc/library/zipfile.rst:195 +msgid "" +"Return a :class:`ZipInfo` object with information about the archive member " +"*name*. Calling :meth:`getinfo` for a name not currently contained in the " +"archive will raise a :exc:`KeyError`." +msgstr "" + +#: ../Doc/library/zipfile.rst:202 +msgid "" +"Return a list containing a :class:`ZipInfo` object for each member of the " +"archive. The objects are in the same order as their entries in the actual " +"ZIP file on disk if an existing archive was opened." +msgstr "" + +#: ../Doc/library/zipfile.rst:209 +msgid "Return a list of archive members by name." +msgstr "" + +#: ../Doc/library/zipfile.rst:214 +msgid "" +"Access a member of the archive as a binary file-like object. *name* can be " +"either the name of a file within the archive or a :class:`ZipInfo` object. " +"The *mode* parameter, if included, must be ``'r'`` (the default) or " +"``'w'``. *pwd* is the password used to decrypt encrypted ZIP files." +msgstr "" + +#: ../Doc/library/zipfile.rst:219 +msgid "" +":meth:`~ZipFile.open` is also a context manager and therefore supports the :" +"keyword:`with` statement::" +msgstr "" + +#: ../Doc/library/zipfile.rst:226 +msgid "" +"With *mode* ``'r'`` the file-like object (``ZipExtFile``) is read-only and " +"provides the following methods: :meth:`~io.BufferedIOBase.read`, :meth:`~io." +"IOBase.readline`, :meth:`~io.IOBase.readlines`, :meth:`__iter__`, :meth:" +"`~iterator.__next__`. These objects can operate independently of the " +"ZipFile." +msgstr "" + +#: ../Doc/library/zipfile.rst:233 +msgid "" +"With ``mode='w'``, a writable file handle is returned, which supports the :" +"meth:`~io.BufferedIOBase.write` method. While a writable file handle is " +"open, attempting to read or write other files in the ZIP file will raise a :" +"exc:`ValueError`." +msgstr "" + +#: ../Doc/library/zipfile.rst:238 +msgid "" +"When writing a file, if the file size is not known in advance but may exceed " +"2 GiB, pass ``force_zip64=True`` to ensure that the header format is capable " +"of supporting large files. If the file size is known in advance, construct " +"a :class:`ZipInfo` object with :attr:`~ZipInfo.file_size` set, and use that " +"as the *name* parameter." +msgstr "" + +#: ../Doc/library/zipfile.rst:246 +msgid "" +"The :meth:`.open`, :meth:`read` and :meth:`extract` methods can take a " +"filename or a :class:`ZipInfo` object. You will appreciate this when trying " +"to read a ZIP file that contains members with duplicate names." +msgstr "" + +#: ../Doc/library/zipfile.rst:250 +msgid "" +"Removed support of ``mode='U'``. Use :class:`io.TextIOWrapper` for reading " +"compressed text files in :term:`universal newlines` mode." +msgstr "" + +#: ../Doc/library/zipfile.rst:254 +msgid "" +":meth:`open` can now be used to write files into the archive with the " +"``mode='w'`` option." +msgstr "" + +#: ../Doc/library/zipfile.rst:258 +msgid "" +"Calling :meth:`.open` on a closed ZipFile will raise a :exc:`ValueError`. " +"Previously, a :exc:`RuntimeError` was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:265 +msgid "" +"Extract a member from the archive to the current working directory; *member* " +"must be its full name or a :class:`ZipInfo` object. Its file information is " +"extracted as accurately as possible. *path* specifies a different directory " +"to extract to. *member* can be a filename or a :class:`ZipInfo` object. " +"*pwd* is the password used for encrypted files." +msgstr "" + +#: ../Doc/library/zipfile.rst:271 +msgid "Returns the normalized path created (a directory or new file)." +msgstr "" + +#: ../Doc/library/zipfile.rst:275 +msgid "" +"If a member filename is an absolute path, a drive/UNC sharepoint and leading " +"(back)slashes will be stripped, e.g.: ``///foo/bar`` becomes ``foo/bar`` on " +"Unix, and ``C:\\foo\\bar`` becomes ``foo\\bar`` on Windows. And all ``\".." +"\"`` components in a member filename will be removed, e.g.: ``../../foo../../" +"ba..r`` becomes ``foo../ba..r``. On Windows illegal characters (``:``, " +"``<``, ``>``, ``|``, ``\"``, ``?``, and ``*``) replaced by underscore " +"(``_``)." +msgstr "" + +#: ../Doc/library/zipfile.rst:283 +msgid "" +"Calling :meth:`extract` on a closed ZipFile will raise a :exc:`ValueError`. " +"Previously, a :exc:`RuntimeError` was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:290 +msgid "" +"Extract all members from the archive to the current working directory. " +"*path* specifies a different directory to extract to. *members* is optional " +"and must be a subset of the list returned by :meth:`namelist`. *pwd* is the " +"password used for encrypted files." +msgstr "" + +#: ../Doc/library/zipfile.rst:297 +msgid "" +"Never extract archives from untrusted sources without prior inspection. It " +"is possible that files are created outside of *path*, e.g. members that have " +"absolute filenames starting with ``\"/\"`` or filenames with two dots ``\".." +"\"``. This module attempts to prevent that. See :meth:`extract` note." +msgstr "" + +#: ../Doc/library/zipfile.rst:303 +msgid "" +"Calling :meth:`extractall` on a closed ZipFile will raise a :exc:" +"`ValueError`. Previously, a :exc:`RuntimeError` was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:310 +msgid "Print a table of contents for the archive to ``sys.stdout``." +msgstr "" + +#: ../Doc/library/zipfile.rst:315 +msgid "Set *pwd* as default password to extract encrypted files." +msgstr "" + +#: ../Doc/library/zipfile.rst:320 +msgid "" +"Return the bytes of the file *name* in the archive. *name* is the name of " +"the file in the archive, or a :class:`ZipInfo` object. The archive must be " +"open for read or append. *pwd* is the password used for encrypted files " +"and, if specified, it will override the default password set with :meth:" +"`setpassword`. Calling :meth:`read` on a ZipFile that uses a compression " +"method other than :const:`ZIP_STORED`, :const:`ZIP_DEFLATED`, :const:" +"`ZIP_BZIP2` or :const:`ZIP_LZMA` will raise a :exc:`NotImplementedError`. An " +"error will also be raised if the corresponding compression module is not " +"available." +msgstr "" + +#: ../Doc/library/zipfile.rst:329 +msgid "" +"Calling :meth:`read` on a closed ZipFile will raise a :exc:`ValueError`. " +"Previously, a :exc:`RuntimeError` was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:336 +msgid "" +"Read all the files in the archive and check their CRC's and file headers. " +"Return the name of the first bad file, or else return ``None``." +msgstr "" + +#: ../Doc/library/zipfile.rst:339 +msgid "" +"Calling :meth:`testfile` on a closed ZipFile will raise a :exc:" +"`ValueError`. Previously, a :exc:`RuntimeError` was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:346 +msgid "" +"Write the file named *filename* to the archive, giving it the archive name " +"*arcname* (by default, this will be the same as *filename*, but without a " +"drive letter and with leading path separators removed). If given, " +"*compress_type* overrides the value given for the *compression* parameter to " +"the constructor for the new entry. The archive must be open with mode " +"``'w'``, ``'x'`` or ``'a'``." +msgstr "" + +#: ../Doc/library/zipfile.rst:355 +msgid "" +"There is no official file name encoding for ZIP files. If you have unicode " +"file names, you must convert them to byte strings in your desired encoding " +"before passing them to :meth:`write`. WinZip interprets all file names as " +"encoded in CP437, also known as DOS Latin." +msgstr "" + +#: ../Doc/library/zipfile.rst:362 +msgid "" +"Archive names should be relative to the archive root, that is, they should " +"not start with a path separator." +msgstr "" + +#: ../Doc/library/zipfile.rst:367 +msgid "" +"If ``arcname`` (or ``filename``, if ``arcname`` is not given) contains a " +"null byte, the name of the file in the archive will be truncated at the null " +"byte." +msgstr "" + +#: ../Doc/library/zipfile.rst:370 +msgid "" +"Calling :meth:`write` on a ZipFile created with mode ``'r'`` or a closed " +"ZipFile will raise a :exc:`ValueError`. Previously, a :exc:`RuntimeError` " +"was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:378 +msgid "" +"Write the string *data* to the archive; *zinfo_or_arcname* is either the " +"file name it will be given in the archive, or a :class:`ZipInfo` instance. " +"If it's an instance, at least the filename, date, and time must be given. " +"If it's a name, the date and time is set to the current date and time. The " +"archive must be opened with mode ``'w'``, ``'x'`` or ``'a'``." +msgstr "" + +#: ../Doc/library/zipfile.rst:384 +msgid "" +"If given, *compress_type* overrides the value given for the *compression* " +"parameter to the constructor for the new entry, or in the *zinfo_or_arcname* " +"(if that is a :class:`ZipInfo` instance)." +msgstr "" + +#: ../Doc/library/zipfile.rst:390 +msgid "" +"When passing a :class:`ZipInfo` instance as the *zinfo_or_arcname* " +"parameter, the compression method used will be that specified in the " +"*compress_type* member of the given :class:`ZipInfo` instance. By default, " +"the :class:`ZipInfo` constructor sets this member to :const:`ZIP_STORED`." +msgstr "" + +#: ../Doc/library/zipfile.rst:395 +msgid "The *compress_type* argument." +msgstr "" + +#: ../Doc/library/zipfile.rst:398 +msgid "" +"Calling :meth:`writestr` on a ZipFile created with mode ``'r'`` or a closed " +"ZipFile will raise a :exc:`ValueError`. Previously, a :exc:`RuntimeError` " +"was raised." +msgstr "" + +#: ../Doc/library/zipfile.rst:404 +msgid "The following data attributes are also available:" +msgstr "" + +#: ../Doc/library/zipfile.rst:409 +msgid "" +"The level of debug output to use. This may be set from ``0`` (the default, " +"no output) to ``3`` (the most output). Debugging information is written to " +"``sys.stdout``." +msgstr "" + +#: ../Doc/library/zipfile.rst:415 +msgid "" +"The comment text associated with the ZIP file. If assigning a comment to a :" +"class:`ZipFile` instance created with mode ``'w'``, ``'x'`` or ``'a'``, this " +"should be a string no longer than 65535 bytes. Comments longer than this " +"will be truncated in the written archive when :meth:`close` is called." +msgstr "" + +#: ../Doc/library/zipfile.rst:425 +msgid "PyZipFile Objects" +msgstr "" + +#: ../Doc/library/zipfile.rst:427 +msgid "" +"The :class:`PyZipFile` constructor takes the same parameters as the :class:" +"`ZipFile` constructor, and one additional parameter, *optimize*." +msgstr "" + +#: ../Doc/library/zipfile.rst:433 +msgid "The *optimize* parameter." +msgstr "" + +#: ../Doc/library/zipfile.rst:439 +msgid "" +"Instances have one method in addition to those of :class:`ZipFile` objects:" +msgstr "" + +#: ../Doc/library/zipfile.rst:443 +msgid "" +"Search for files :file:`\\*.py` and add the corresponding file to the " +"archive." +msgstr "" + +#: ../Doc/library/zipfile.rst:446 +msgid "" +"If the *optimize* parameter to :class:`PyZipFile` was not given or ``-1``, " +"the corresponding file is a :file:`\\*.pyc` file, compiling if necessary." +msgstr "" + +#: ../Doc/library/zipfile.rst:449 +msgid "" +"If the *optimize* parameter to :class:`PyZipFile` was ``0``, ``1`` or ``2``, " +"only files with that optimization level (see :func:`compile`) are added to " +"the archive, compiling if necessary." +msgstr "" + +#: ../Doc/library/zipfile.rst:453 +msgid "" +"If *pathname* is a file, the filename must end with :file:`.py`, and just " +"the (corresponding :file:`\\*.py[co]`) file is added at the top level (no " +"path information). If *pathname* is a file that does not end with :file:`." +"py`, a :exc:`RuntimeError` will be raised. If it is a directory, and the " +"directory is not a package directory, then all the files :file:`\\*.py[co]` " +"are added at the top level. If the directory is a package directory, then " +"all :file:`\\*.py[co]` are added under the package name as a file path, and " +"if any subdirectories are package directories, all of these are added " +"recursively." +msgstr "" + +#: ../Doc/library/zipfile.rst:463 +msgid "*basename* is intended for internal use only." +msgstr "" + +#: ../Doc/library/zipfile.rst:465 +msgid "" +"*filterfunc*, if given, must be a function taking a single string argument. " +"It will be passed each path (including each individual full file path) " +"before it is added to the archive. If *filterfunc* returns a false value, " +"the path will not be added, and if it is a directory its contents will be " +"ignored. For example, if our test files are all either in ``test`` " +"directories or start with the string ``test_``, we can use a *filterfunc* to " +"exclude them::" +msgstr "" + +#: ../Doc/library/zipfile.rst:479 +msgid "The :meth:`writepy` method makes archives with file names like this::" +msgstr "" + +#: ../Doc/library/zipfile.rst:488 +msgid "The *filterfunc* parameter." +msgstr "" + +#: ../Doc/library/zipfile.rst:495 +msgid "ZipInfo Objects" +msgstr "" + +#: ../Doc/library/zipfile.rst:497 +msgid "" +"Instances of the :class:`ZipInfo` class are returned by the :meth:`.getinfo` " +"and :meth:`.infolist` methods of :class:`ZipFile` objects. Each object " +"stores information about a single member of the ZIP archive." +msgstr "" + +#: ../Doc/library/zipfile.rst:501 +msgid "" +"There is one classmethod to make a :class:`ZipInfo` instance for a " +"filesystem file:" +msgstr "" + +#: ../Doc/library/zipfile.rst:506 +msgid "" +"Construct a :class:`ZipInfo` instance for a file on the filesystem, in " +"preparation for adding it to a zip file." +msgstr "" + +#: ../Doc/library/zipfile.rst:509 +msgid "*filename* should be the path to a file or directory on the filesystem." +msgstr "" + +#: ../Doc/library/zipfile.rst:511 +msgid "" +"If *arcname* is specified, it is used as the name within the archive. If " +"*arcname* is not specified, the name will be the same as *filename*, but " +"with any drive letter and leading path separators removed." +msgstr "" + +#: ../Doc/library/zipfile.rst:517 +msgid "Instances have the following methods and attributes:" +msgstr "" + +#: ../Doc/library/zipfile.rst:521 +msgid "Return True if this archive member is a directory." +msgstr "" + +#: ../Doc/library/zipfile.rst:523 +msgid "This uses the entry's name: directories should always end with ``/``." +msgstr "" + +#: ../Doc/library/zipfile.rst:530 +msgid "Name of the file in the archive." +msgstr "" + +#: ../Doc/library/zipfile.rst:535 +msgid "" +"The time and date of the last modification to the archive member. This is a " +"tuple of six values:" +msgstr "" + +#: ../Doc/library/zipfile.rst:541 +msgid "Year (>= 1980)" +msgstr "" + +#: ../Doc/library/zipfile.rst:543 +msgid "Month (one-based)" +msgstr "" + +#: ../Doc/library/zipfile.rst:545 +msgid "Day of month (one-based)" +msgstr "" + +#: ../Doc/library/zipfile.rst:547 +msgid "Hours (zero-based)" +msgstr "" + +#: ../Doc/library/zipfile.rst:549 +msgid "Minutes (zero-based)" +msgstr "" + +#: ../Doc/library/zipfile.rst:551 +msgid "Seconds (zero-based)" +msgstr "" + +#: ../Doc/library/zipfile.rst:556 +msgid "The ZIP file format does not support timestamps before 1980." +msgstr "" + +#: ../Doc/library/zipfile.rst:561 +msgid "Type of compression for the archive member." +msgstr "" + +#: ../Doc/library/zipfile.rst:566 +msgid "Comment for the individual archive member." +msgstr "" + +#: ../Doc/library/zipfile.rst:571 +msgid "" +"Expansion field data. The `PKZIP Application Note`_ contains some comments " +"on the internal structure of the data contained in this string." +msgstr "" + +#: ../Doc/library/zipfile.rst:577 +msgid "System which created ZIP archive." +msgstr "" + +#: ../Doc/library/zipfile.rst:582 +msgid "PKZIP version which created ZIP archive." +msgstr "" + +#: ../Doc/library/zipfile.rst:587 +msgid "PKZIP version needed to extract archive." +msgstr "" + +#: ../Doc/library/zipfile.rst:592 +msgid "Must be zero." +msgstr "" + +#: ../Doc/library/zipfile.rst:597 +msgid "ZIP flag bits." +msgstr "" + +#: ../Doc/library/zipfile.rst:602 +msgid "Volume number of file header." +msgstr "" + +#: ../Doc/library/zipfile.rst:607 +msgid "Internal attributes." +msgstr "" + +#: ../Doc/library/zipfile.rst:612 +msgid "External file attributes." +msgstr "" + +#: ../Doc/library/zipfile.rst:617 +msgid "Byte offset to the file header." +msgstr "" + +#: ../Doc/library/zipfile.rst:622 +msgid "CRC-32 of the uncompressed file." +msgstr "" + +#: ../Doc/library/zipfile.rst:627 +msgid "Size of the compressed data." +msgstr "" + +#: ../Doc/library/zipfile.rst:632 +msgid "Size of the uncompressed file." +msgstr "" + +#: ../Doc/library/zipimport.rst:2 +msgid ":mod:`zipimport` --- Import modules from Zip archives" +msgstr "" + +#: ../Doc/library/zipimport.rst:11 +msgid "" +"This module adds the ability to import Python modules (:file:`\\*.py`, :file:" +"`\\*.py[co]`) and packages from ZIP-format archives. It is usually not " +"needed to use the :mod:`zipimport` module explicitly; it is automatically " +"used by the built-in :keyword:`import` mechanism for :data:`sys.path` items " +"that are paths to ZIP archives." +msgstr "" + +#: ../Doc/library/zipimport.rst:17 +msgid "" +"Typically, :data:`sys.path` is a list of directory names as strings. This " +"module also allows an item of :data:`sys.path` to be a string naming a ZIP " +"file archive. The ZIP archive can contain a subdirectory structure to " +"support package imports, and a path within the archive can be specified to " +"only import from a subdirectory. For example, the path :file:`example.zip/" +"lib/` would only import from the :file:`lib/` subdirectory within the " +"archive." +msgstr "" + +#: ../Doc/library/zipimport.rst:24 +msgid "" +"Any files may be present in the ZIP archive, but only files :file:`.py` and :" +"file:`.pyc` are available for import. ZIP import of dynamic modules (:file:" +"`.pyd`, :file:`.so`) is disallowed. Note that if an archive only contains :" +"file:`.py` files, Python will not attempt to modify the archive by adding " +"the corresponding :file:`.pyc` file, meaning that if a ZIP archive doesn't " +"contain :file:`.pyc` files, importing may be rather slow." +msgstr "" + +#: ../Doc/library/zipimport.rst:31 +msgid "ZIP archives with an archive comment are currently not supported." +msgstr "" + +#: ../Doc/library/zipimport.rst:37 +msgid "" +"`PKZIP Application Note `_" +msgstr "" + +#: ../Doc/library/zipimport.rst:42 +msgid ":pep:`273` - Import Modules from Zip Archives" +msgstr "" + +#: ../Doc/library/zipimport.rst:40 +msgid "" +"Written by James C. Ahlstrom, who also provided an implementation. Python " +"2.3 follows the specification in PEP 273, but uses an implementation written " +"by Just van Rossum that uses the import hooks described in PEP 302." +msgstr "" + +#: ../Doc/library/zipimport.rst:44 +msgid ":pep:`302` - New Import Hooks" +msgstr "" + +#: ../Doc/library/zipimport.rst:45 +msgid "The PEP to add the import hooks that help this module work." +msgstr "" + +#: ../Doc/library/zipimport.rst:48 +msgid "This module defines an exception:" +msgstr "" + +#: ../Doc/library/zipimport.rst:52 +msgid "" +"Exception raised by zipimporter objects. It's a subclass of :exc:" +"`ImportError`, so it can be caught as :exc:`ImportError`, too." +msgstr "" + +#: ../Doc/library/zipimport.rst:59 +msgid "zipimporter Objects" +msgstr "" + +#: ../Doc/library/zipimport.rst:61 +msgid ":class:`zipimporter` is the class for importing ZIP files." +msgstr "" + +#: ../Doc/library/zipimport.rst:65 +msgid "" +"Create a new zipimporter instance. *archivepath* must be a path to a ZIP " +"file, or to a specific path within a ZIP file. For example, an " +"*archivepath* of :file:`foo/bar.zip/lib` will look for modules in the :file:" +"`lib` directory inside the ZIP file :file:`foo/bar.zip` (provided that it " +"exists)." +msgstr "" + +#: ../Doc/library/zipimport.rst:70 +msgid "" +":exc:`ZipImportError` is raised if *archivepath* doesn't point to a valid " +"ZIP archive." +msgstr "" + +#: ../Doc/library/zipimport.rst:75 +msgid "" +"Search for a module specified by *fullname*. *fullname* must be the fully " +"qualified (dotted) module name. It returns the zipimporter instance itself " +"if the module was found, or :const:`None` if it wasn't. The optional *path* " +"argument is ignored---it's there for compatibility with the importer " +"protocol." +msgstr "" + +#: ../Doc/library/zipimport.rst:84 +msgid "" +"Return the code object for the specified module. Raise :exc:`ZipImportError` " +"if the module couldn't be found." +msgstr "" + +#: ../Doc/library/zipimport.rst:90 +msgid "" +"Return the data associated with *pathname*. Raise :exc:`OSError` if the file " +"wasn't found." +msgstr "" + +#: ../Doc/library/zipimport.rst:99 +msgid "" +"Return the value ``__file__`` would be set to if the specified module was " +"imported. Raise :exc:`ZipImportError` if the module couldn't be found." +msgstr "" + +#: ../Doc/library/zipimport.rst:108 +msgid "" +"Return the source code for the specified module. Raise :exc:`ZipImportError` " +"if the module couldn't be found, return :const:`None` if the archive does " +"contain the module, but has no source for it." +msgstr "" + +#: ../Doc/library/zipimport.rst:116 +msgid "" +"Return ``True`` if the module specified by *fullname* is a package. Raise :" +"exc:`ZipImportError` if the module couldn't be found." +msgstr "" + +#: ../Doc/library/zipimport.rst:122 +msgid "" +"Load the module specified by *fullname*. *fullname* must be the fully " +"qualified (dotted) module name. It returns the imported module, or raises :" +"exc:`ZipImportError` if it wasn't found." +msgstr "" + +#: ../Doc/library/zipimport.rst:129 +msgid "" +"The file name of the importer's associated ZIP file, without a possible " +"subpath." +msgstr "" + +#: ../Doc/library/zipimport.rst:135 +msgid "" +"The subpath within the ZIP file where modules are searched. This is the " +"empty string for zipimporter objects which point to the root of the ZIP file." +msgstr "" + +#: ../Doc/library/zipimport.rst:139 +msgid "" +"The :attr:`archive` and :attr:`prefix` attributes, when combined with a " +"slash, equal the original *archivepath* argument given to the :class:" +"`zipimporter` constructor." +msgstr "" + +#: ../Doc/library/zipimport.rst:149 +msgid "" +"Here is an example that imports a module from a ZIP archive - note that the :" +"mod:`zipimport` module is not explicitly used." +msgstr "" + +#: ../Doc/library/zlib.rst:2 +msgid ":mod:`zlib` --- Compression compatible with :program:`gzip`" +msgstr "" + +#: ../Doc/library/zlib.rst:10 +msgid "" +"For applications that require data compression, the functions in this module " +"allow compression and decompression, using the zlib library. The zlib " +"library has its own home page at http://www.zlib.net. There are known " +"incompatibilities between the Python module and versions of the zlib library " +"earlier than 1.1.3; 1.1.3 has a security vulnerability, so we recommend " +"using 1.1.4 or later." +msgstr "" + +#: ../Doc/library/zlib.rst:17 +msgid "" +"zlib's functions have many options and often need to be used in a particular " +"order. This documentation doesn't attempt to cover all of the permutations; " +"consult the zlib manual at http://www.zlib.net/manual.html for authoritative " +"information." +msgstr "" + +#: ../Doc/library/zlib.rst:22 +msgid "For reading and writing ``.gz`` files see the :mod:`gzip` module." +msgstr "" + +#: ../Doc/library/zlib.rst:24 +msgid "The available exception and functions in this module are:" +msgstr "" + +#: ../Doc/library/zlib.rst:29 +msgid "Exception raised on compression and decompression errors." +msgstr "" + +#: ../Doc/library/zlib.rst:34 +msgid "" +"Computes an Adler-32 checksum of *data*. (An Adler-32 checksum is almost as " +"reliable as a CRC32 but can be computed much more quickly.) The result is " +"an unsigned 32-bit integer. If *value* is present, it is used as the " +"starting value of the checksum; otherwise, a default value of 1 is used. " +"Passing in *value* allows computing a running checksum over the " +"concatenation of several inputs. The algorithm is not cryptographically " +"strong, and should not be used for authentication or digital signatures. " +"Since the algorithm is designed for use as a checksum algorithm, it is not " +"suitable for use as a general hash algorithm." +msgstr "" + +#: ../Doc/library/zlib.rst:44 +msgid "" +"Always returns an unsigned value. To generate the same numeric value across " +"all Python versions and platforms, use ``adler32(data) & 0xffffffff``." +msgstr "" + +#: ../Doc/library/zlib.rst:52 +msgid "" +"Compresses the bytes in *data*, returning a bytes object containing " +"compressed data. *level* is an integer from ``0`` to ``9`` or ``-1`` " +"controlling the level of compression; ``1`` is fastest and produces the " +"least compression, ``9`` is slowest and produces the most. ``0`` is no " +"compression. The default value is ``-1`` (Z_DEFAULT_COMPRESSION). " +"Z_DEFAULT_COMPRESSION represents a default compromise between speed and " +"compression (currently equivalent to level 6). Raises the :exc:`error` " +"exception if any error occurs." +msgstr "" + +#: ../Doc/library/zlib.rst:60 +msgid "*level* can now be used as a keyword parameter." +msgstr "" + +#: ../Doc/library/zlib.rst:66 +msgid "" +"Returns a compression object, to be used for compressing data streams that " +"won't fit into memory at once." +msgstr "" + +#: ../Doc/library/zlib.rst:69 +msgid "" +"*level* is the compression level -- an integer from ``0`` to ``9`` or " +"``-1``. A value of ``1`` is fastest and produces the least compression, " +"while a value of ``9`` is slowest and produces the most. ``0`` is no " +"compression. The default value is ``-1`` (Z_DEFAULT_COMPRESSION). " +"Z_DEFAULT_COMPRESSION represents a default compromise between speed and " +"compression (currently equivalent to level 6)." +msgstr "" + +#: ../Doc/library/zlib.rst:75 +msgid "" +"*method* is the compression algorithm. Currently, the only supported value " +"is ``DEFLATED``." +msgstr "" + +#: ../Doc/library/zlib.rst:78 +msgid "" +"The *wbits* argument controls the size of the history buffer (or the " +"\"window size\") used when compressing data, and whether a header and " +"trailer is included in the output. It can take several ranges of values:" +msgstr "" + +#: ../Doc/library/zlib.rst:82 +msgid "" +"+9 to +15: The base-two logarithm of the window size, which therefore ranges " +"between 512 and 32768. Larger values produce better compression at the " +"expense of greater memory usage. The resulting output will include a zlib-" +"specific header and trailer." +msgstr "" + +#: ../Doc/library/zlib.rst:87 +msgid "" +"−9 to −15: Uses the absolute value of *wbits* as the window size logarithm, " +"while producing a raw output stream with no header or trailing checksum." +msgstr "" + +#: ../Doc/library/zlib.rst:91 +msgid "" +"+25 to +31 = 16 + (9 to 15): Uses the low 4 bits of the value as the window " +"size logarithm, while including a basic :program:`gzip` header and trailing " +"checksum in the output." +msgstr "" + +#: ../Doc/library/zlib.rst:95 +msgid "" +"The *memLevel* argument controls the amount of memory used for the internal " +"compression state. Valid values range from ``1`` to ``9``. Higher values use " +"more memory, but are faster and produce smaller output." +msgstr "" + +#: ../Doc/library/zlib.rst:99 +msgid "" +"*strategy* is used to tune the compression algorithm. Possible values are " +"``Z_DEFAULT_STRATEGY``, ``Z_FILTERED``, and ``Z_HUFFMAN_ONLY``." +msgstr "" + +#: ../Doc/library/zlib.rst:102 +msgid "" +"*zdict* is a predefined compression dictionary. This is a sequence of bytes " +"(such as a :class:`bytes` object) containing subsequences that are expected " +"to occur frequently in the data that is to be compressed. Those subsequences " +"that are expected to be most common should come at the end of the dictionary." +msgstr "" + +#: ../Doc/library/zlib.rst:107 +msgid "Added the *zdict* parameter and keyword argument support." +msgstr "" + +#: ../Doc/library/zlib.rst:117 +msgid "" +"Computes a CRC (Cyclic Redundancy Check) checksum of *data*. The result is " +"an unsigned 32-bit integer. If *value* is present, it is used as the " +"starting value of the checksum; otherwise, a default value of 0 is used. " +"Passing in *value* allows computing a running checksum over the " +"concatenation of several inputs. The algorithm is not cryptographically " +"strong, and should not be used for authentication or digital signatures. " +"Since the algorithm is designed for use as a checksum algorithm, it is not " +"suitable for use as a general hash algorithm." +msgstr "" + +#: ../Doc/library/zlib.rst:126 +msgid "" +"Always returns an unsigned value. To generate the same numeric value across " +"all Python versions and platforms, use ``crc32(data) & 0xffffffff``." +msgstr "" + +#: ../Doc/library/zlib.rst:134 +msgid "" +"Decompresses the bytes in *data*, returning a bytes object containing the " +"uncompressed data. The *wbits* parameter depends on the format of *data*, " +"and is discussed further below. If *bufsize* is given, it is used as the " +"initial size of the output buffer. Raises the :exc:`error` exception if any " +"error occurs." +msgstr "" + +#: ../Doc/library/zlib.rst:142 +msgid "" +"The *wbits* parameter controls the size of the history buffer (or \"window " +"size\"), and what header and trailer format is expected. It is similar to " +"the parameter for :func:`compressobj`, but accepts more ranges of values:" +msgstr "" + +#: ../Doc/library/zlib.rst:147 +msgid "" +"+8 to +15: The base-two logarithm of the window size. The input must " +"include a zlib header and trailer." +msgstr "" + +#: ../Doc/library/zlib.rst:150 +msgid "" +"0: Automatically determine the window size from the zlib header. Only " +"supported since zlib 1.2.3.5." +msgstr "" + +#: ../Doc/library/zlib.rst:153 +msgid "" +"−8 to −15: Uses the absolute value of *wbits* as the window size logarithm. " +"The input must be a raw stream with no header or trailer." +msgstr "" + +#: ../Doc/library/zlib.rst:156 +msgid "" +"+24 to +31 = 16 + (8 to 15): Uses the low 4 bits of the value as the window " +"size logarithm. The input must include a gzip header and trailer." +msgstr "" + +#: ../Doc/library/zlib.rst:160 +msgid "" +"+40 to +47 = 32 + (8 to 15): Uses the low 4 bits of the value as the window " +"size logarithm, and automatically accepts either the zlib or gzip format." +msgstr "" + +#: ../Doc/library/zlib.rst:164 +msgid "" +"When decompressing a stream, the window size must not be smaller than the " +"size originally used to compress the stream; using a too-small value may " +"result in an :exc:`error` exception. The default *wbits* value corresponds " +"to the largest window size and requires a zlib header and trailer to be " +"included." +msgstr "" + +#: ../Doc/library/zlib.rst:170 +msgid "" +"*bufsize* is the initial size of the buffer used to hold decompressed data. " +"If more space is required, the buffer size will be increased as needed, so " +"you don't have to get this value exactly right; tuning it will only save a " +"few calls to :c:func:`malloc`." +msgstr "" + +#: ../Doc/library/zlib.rst:175 +msgid "*wbits* and *bufsize* can be used as keyword arguments." +msgstr "" + +#: ../Doc/library/zlib.rst:180 +msgid "" +"Returns a decompression object, to be used for decompressing data streams " +"that won't fit into memory at once." +msgstr "" + +#: ../Doc/library/zlib.rst:183 +msgid "" +"The *wbits* parameter controls the size of the history buffer (or the " +"\"window size\"), and what header and trailer format is expected. It has " +"the same meaning as `described for decompress() <#decompress-wbits>`__." +msgstr "" + +#: ../Doc/library/zlib.rst:187 +msgid "" +"The *zdict* parameter specifies a predefined compression dictionary. If " +"provided, this must be the same dictionary as was used by the compressor " +"that produced the data that is to be decompressed." +msgstr "" + +#: ../Doc/library/zlib.rst:193 +msgid "" +"If *zdict* is a mutable object (such as a :class:`bytearray`), you must not " +"modify its contents between the call to :func:`decompressobj` and the first " +"call to the decompressor's ``decompress()`` method." +msgstr "" + +#: ../Doc/library/zlib.rst:197 +msgid "Added the *zdict* parameter." +msgstr "" + +#: ../Doc/library/zlib.rst:201 +msgid "Compression objects support the following methods:" +msgstr "" + +#: ../Doc/library/zlib.rst:206 +msgid "" +"Compress *data*, returning a bytes object containing compressed data for at " +"least part of the data in *data*. This data should be concatenated to the " +"output produced by any preceding calls to the :meth:`compress` method. Some " +"input may be kept in internal buffers for later processing." +msgstr "" + +#: ../Doc/library/zlib.rst:214 +msgid "" +"All pending input is processed, and a bytes object containing the remaining " +"compressed output is returned. *mode* can be selected from the constants :" +"const:`Z_SYNC_FLUSH`, :const:`Z_FULL_FLUSH`, or :const:`Z_FINISH`, " +"defaulting to :const:`Z_FINISH`. :const:`Z_SYNC_FLUSH` and :const:" +"`Z_FULL_FLUSH` allow compressing further bytestrings of data, while :const:" +"`Z_FINISH` finishes the compressed stream and prevents compressing any more " +"data. After calling :meth:`flush` with *mode* set to :const:`Z_FINISH`, " +"the :meth:`compress` method cannot be called again; the only realistic " +"action is to delete the object." +msgstr "" + +#: ../Doc/library/zlib.rst:227 +msgid "" +"Returns a copy of the compression object. This can be used to efficiently " +"compress a set of data that share a common initial prefix." +msgstr "" + +#: ../Doc/library/zlib.rst:231 +msgid "Decompression objects support the following methods and attributes:" +msgstr "" + +#: ../Doc/library/zlib.rst:236 +msgid "" +"A bytes object which contains any bytes past the end of the compressed data. " +"That is, this remains ``b\"\"`` until the last byte that contains " +"compression data is available. If the whole bytestring turned out to " +"contain compressed data, this is ``b\"\"``, an empty bytes object." +msgstr "" + +#: ../Doc/library/zlib.rst:244 +msgid "" +"A bytes object that contains any data that was not consumed by the last :" +"meth:`decompress` call because it exceeded the limit for the uncompressed " +"data buffer. This data has not yet been seen by the zlib machinery, so you " +"must feed it (possibly with further data concatenated to it) back to a " +"subsequent :meth:`decompress` method call in order to get correct output." +msgstr "" + +#: ../Doc/library/zlib.rst:253 +msgid "" +"A boolean indicating whether the end of the compressed data stream has been " +"reached." +msgstr "" + +#: ../Doc/library/zlib.rst:256 +msgid "" +"This makes it possible to distinguish between a properly-formed compressed " +"stream, and an incomplete or truncated one." +msgstr "" + +#: ../Doc/library/zlib.rst:264 +msgid "" +"Decompress *data*, returning a bytes object containing the uncompressed data " +"corresponding to at least part of the data in *string*. This data should be " +"concatenated to the output produced by any preceding calls to the :meth:" +"`decompress` method. Some of the input data may be preserved in internal " +"buffers for later processing." +msgstr "" + +#: ../Doc/library/zlib.rst:270 +msgid "" +"If the optional parameter *max_length* is non-zero then the return value " +"will be no longer than *max_length*. This may mean that not all of the " +"compressed input can be processed; and unconsumed data will be stored in the " +"attribute :attr:`unconsumed_tail`. This bytestring must be passed to a " +"subsequent call to :meth:`decompress` if decompression is to continue. If " +"*max_length* is zero then the whole input is decompressed, and :attr:" +"`unconsumed_tail` is empty." +msgstr "" + +#: ../Doc/library/zlib.rst:277 +msgid "*max_length* can be used as a keyword argument." +msgstr "" + +#: ../Doc/library/zlib.rst:283 +msgid "" +"All pending input is processed, and a bytes object containing the remaining " +"uncompressed output is returned. After calling :meth:`flush`, the :meth:" +"`decompress` method cannot be called again; the only realistic action is to " +"delete the object." +msgstr "" + +#: ../Doc/library/zlib.rst:288 +msgid "" +"The optional parameter *length* sets the initial size of the output buffer." +msgstr "" + +#: ../Doc/library/zlib.rst:293 +msgid "" +"Returns a copy of the decompression object. This can be used to save the " +"state of the decompressor midway through the data stream in order to speed " +"up random seeks into the stream at a future point." +msgstr "" + +#: ../Doc/library/zlib.rst:298 +msgid "" +"Information about the version of the zlib library in use is available " +"through the following constants:" +msgstr "" + +#: ../Doc/library/zlib.rst:304 +msgid "" +"The version string of the zlib library that was used for building the " +"module. This may be different from the zlib library actually used at " +"runtime, which is available as :const:`ZLIB_RUNTIME_VERSION`." +msgstr "" + +#: ../Doc/library/zlib.rst:311 +msgid "" +"The version string of the zlib library actually loaded by the interpreter." +msgstr "" + +#: ../Doc/library/zlib.rst:319 +msgid "Module :mod:`gzip`" +msgstr "" + +#: ../Doc/library/zlib.rst:319 +msgid "Reading and writing :program:`gzip`\\ -format files." +msgstr "" + +#: ../Doc/library/zlib.rst:322 +msgid "http://www.zlib.net" +msgstr "" + +#: ../Doc/library/zlib.rst:322 +msgid "The zlib library home page." +msgstr "" + +#: ../Doc/library/zlib.rst:325 +msgid "http://www.zlib.net/manual.html" +msgstr "" + +#: ../Doc/library/zlib.rst:325 +msgid "" +"The zlib manual explains the semantics and usage of the library's many " +"functions." +msgstr "" diff --git a/license.po b/license.po new file mode 100644 index 00000000..b3d4450f --- /dev/null +++ b/license.po @@ -0,0 +1,423 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/license.rst:7 +msgid "History and License" +msgstr "" + +#: ../Doc/license.rst:11 +msgid "History of the software" +msgstr "" + +#: ../Doc/license.rst:13 +msgid "" +"Python was created in the early 1990s by Guido van Rossum at Stichting " +"Mathematisch Centrum (CWI, see https://www.cwi.nl/) in the Netherlands as a " +"successor of a language called ABC. Guido remains Python's principal " +"author, although it includes many contributions from others." +msgstr "" + +#: ../Doc/license.rst:18 +msgid "" +"In 1995, Guido continued his work on Python at the Corporation for National " +"Research Initiatives (CNRI, see https://www.cnri.reston.va.us/) in Reston, " +"Virginia where he released several versions of the software." +msgstr "" + +#: ../Doc/license.rst:22 +msgid "" +"In May 2000, Guido and the Python core development team moved to BeOpen.com " +"to form the BeOpen PythonLabs team. In October of the same year, the " +"PythonLabs team moved to Digital Creations (now Zope Corporation; see http://" +"www.zope.com/). In 2001, the Python Software Foundation (PSF, see https://" +"www.python.org/psf/) was formed, a non-profit organization created " +"specifically to own Python-related Intellectual Property. Zope Corporation " +"is a sponsoring member of the PSF." +msgstr "" + +#: ../Doc/license.rst:30 +msgid "" +"All Python releases are Open Source (see https://opensource.org/ for the " +"Open Source Definition). Historically, most, but not all, Python releases " +"have also been GPL-compatible; the table below summarizes the various " +"releases." +msgstr "" + +#: ../Doc/license.rst:35 +msgid "Release" +msgstr "" + +#: ../Doc/license.rst:35 +msgid "Derived from" +msgstr "" + +#: ../Doc/license.rst:35 +msgid "Year" +msgstr "" + +#: ../Doc/license.rst:35 +msgid "Owner" +msgstr "" + +#: ../Doc/license.rst:35 +msgid "GPL compatible?" +msgstr "" + +#: ../Doc/license.rst:37 +msgid "0.9.0 thru 1.2" +msgstr "" + +#: ../Doc/license.rst:37 +msgid "n/a" +msgstr "" + +#: ../Doc/license.rst:37 +msgid "1991-1995" +msgstr "" + +#: ../Doc/license.rst:37 +msgid "CWI" +msgstr "" + +#: ../Doc/license.rst:37 ../Doc/license.rst:39 ../Doc/license.rst:49 +#: ../Doc/license.rst:51 ../Doc/license.rst:53 ../Doc/license.rst:55 +#: ../Doc/license.rst:57 +msgid "yes" +msgstr "" + +#: ../Doc/license.rst:39 +msgid "1.3 thru 1.5.2" +msgstr "" + +#: ../Doc/license.rst:39 +msgid "1.2" +msgstr "" + +#: ../Doc/license.rst:39 +msgid "1995-1999" +msgstr "" + +#: ../Doc/license.rst:39 ../Doc/license.rst:41 ../Doc/license.rst:45 +msgid "CNRI" +msgstr "" + +#: ../Doc/license.rst:41 ../Doc/license.rst:43 ../Doc/license.rst:45 +msgid "1.6" +msgstr "" + +#: ../Doc/license.rst:41 +msgid "1.5.2" +msgstr "" + +#: ../Doc/license.rst:41 ../Doc/license.rst:43 +msgid "2000" +msgstr "" + +#: ../Doc/license.rst:41 ../Doc/license.rst:43 ../Doc/license.rst:45 +#: ../Doc/license.rst:47 +msgid "no" +msgstr "" + +#: ../Doc/license.rst:43 +msgid "2.0" +msgstr "" + +#: ../Doc/license.rst:43 +msgid "BeOpen.com" +msgstr "" + +#: ../Doc/license.rst:45 +msgid "1.6.1" +msgstr "" + +#: ../Doc/license.rst:45 ../Doc/license.rst:47 ../Doc/license.rst:49 +#: ../Doc/license.rst:51 +msgid "2001" +msgstr "" + +#: ../Doc/license.rst:47 +msgid "2.1" +msgstr "" + +#: ../Doc/license.rst:47 ../Doc/license.rst:49 +msgid "2.0+1.6.1" +msgstr "" + +#: ../Doc/license.rst:47 ../Doc/license.rst:49 ../Doc/license.rst:51 +#: ../Doc/license.rst:53 ../Doc/license.rst:55 ../Doc/license.rst:57 +msgid "PSF" +msgstr "" + +#: ../Doc/license.rst:49 +msgid "2.0.1" +msgstr "" + +#: ../Doc/license.rst:51 ../Doc/license.rst:53 ../Doc/license.rst:57 +msgid "2.1.1" +msgstr "" + +#: ../Doc/license.rst:51 +msgid "2.1+2.0.1" +msgstr "" + +#: ../Doc/license.rst:53 ../Doc/license.rst:55 +msgid "2.1.2" +msgstr "" + +#: ../Doc/license.rst:53 ../Doc/license.rst:55 +msgid "2002" +msgstr "" + +#: ../Doc/license.rst:55 +msgid "2.1.3" +msgstr "" + +#: ../Doc/license.rst:57 +msgid "2.2 and above" +msgstr "" + +#: ../Doc/license.rst:57 +msgid "2001-now" +msgstr "" + +#: ../Doc/license.rst:62 +msgid "" +"GPL-compatible doesn't mean that we're distributing Python under the GPL. " +"All Python licenses, unlike the GPL, let you distribute a modified version " +"without making your changes open source. The GPL-compatible licenses make it " +"possible to combine Python with other software that is released under the " +"GPL; the others don't." +msgstr "" + +#: ../Doc/license.rst:68 +msgid "" +"Thanks to the many outside volunteers who have worked under Guido's " +"direction to make these releases possible." +msgstr "" + +#: ../Doc/license.rst:73 +msgid "Terms and conditions for accessing or otherwise using Python" +msgstr "" + +#: ../Doc/license.rst:77 +msgid "PSF LICENSE AGREEMENT FOR PYTHON |release|" +msgstr "" + +#: ../Doc/license.rst:125 +msgid "BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0" +msgstr "" + +#: ../Doc/license.rst:127 +msgid "BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1" +msgstr "" + +#: ../Doc/license.rst:172 +msgid "CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1" +msgstr "" + +#: ../Doc/license.rst:237 +msgid "CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2" +msgstr "" + +#: ../Doc/license.rst:262 +msgid "Licenses and Acknowledgements for Incorporated Software" +msgstr "" + +#: ../Doc/license.rst:264 +msgid "" +"This section is an incomplete, but growing list of licenses and " +"acknowledgements for third-party software incorporated in the Python " +"distribution." +msgstr "" + +#: ../Doc/license.rst:269 +msgid "Mersenne Twister" +msgstr "" + +#: ../Doc/license.rst:271 +msgid "" +"The :mod:`_random` module includes code based on a download from http://www." +"math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html. The following " +"are the verbatim comments from the original code::" +msgstr "" + +#: ../Doc/license.rst:318 +msgid "Sockets" +msgstr "" + +#: ../Doc/license.rst:320 +msgid "" +"The :mod:`socket` module uses the functions, :func:`getaddrinfo`, and :func:" +"`getnameinfo`, which are coded in separate source files from the WIDE " +"Project, http://www.wide.ad.jp/. ::" +msgstr "" + +#: ../Doc/license.rst:353 +msgid "Floating point exception control" +msgstr "" + +#: ../Doc/license.rst:355 +msgid "The source for the :mod:`fpectl` module includes the following notice::" +msgstr "" + +#: ../Doc/license.rst:395 +msgid "Asynchronous socket services" +msgstr "" + +#: ../Doc/license.rst:397 +msgid "" +"The :mod:`asynchat` and :mod:`asyncore` modules contain the following " +"notice::" +msgstr "" + +#: ../Doc/license.rst:422 +msgid "Cookie management" +msgstr "" + +#: ../Doc/license.rst:424 +msgid "The :mod:`http.cookies` module contains the following notice::" +msgstr "" + +#: ../Doc/license.rst:450 +msgid "Execution tracing" +msgstr "" + +#: ../Doc/license.rst:452 +msgid "The :mod:`trace` module contains the following notice::" +msgstr "" + +#: ../Doc/license.rst:483 +msgid "UUencode and UUdecode functions" +msgstr "" + +#: ../Doc/license.rst:485 +msgid "The :mod:`uu` module contains the following notice::" +msgstr "" + +#: ../Doc/license.rst:513 +msgid "XML Remote Procedure Calls" +msgstr "" + +#: ../Doc/license.rst:515 +msgid "The :mod:`xmlrpc.client` module contains the following notice::" +msgstr "" + +#: ../Doc/license.rst:546 +msgid "test_epoll" +msgstr "" + +#: ../Doc/license.rst:548 +msgid "The :mod:`test_epoll` contains the following notice::" +msgstr "" + +#: ../Doc/license.rst:572 +msgid "Select kqueue" +msgstr "" + +#: ../Doc/license.rst:574 +msgid "" +"The :mod:`select` and contains the following notice for the kqueue " +"interface::" +msgstr "" + +#: ../Doc/license.rst:602 +msgid "SipHash24" +msgstr "" + +#: ../Doc/license.rst:604 +msgid "" +"The file :file:`Python/pyhash.c` contains Marek Majkowski' implementation of " +"Dan Bernstein's SipHash24 algorithm. The contains the following note::" +msgstr "" + +#: ../Doc/license.rst:631 +msgid "strtod and dtoa" +msgstr "" + +#: ../Doc/license.rst:633 +msgid "" +"The file :file:`Python/dtoa.c`, which supplies C functions dtoa and strtod " +"for conversion of C doubles to and from strings, is derived from the file of " +"the same name by David M. Gay, currently available from http://www.netlib." +"org/fp/. The original file, as retrieved on March 16, 2009, contains the " +"following copyright and licensing notice::" +msgstr "" + +#: ../Doc/license.rst:661 +msgid "OpenSSL" +msgstr "" + +#: ../Doc/license.rst:663 +msgid "" +"The modules :mod:`hashlib`, :mod:`posix`, :mod:`ssl`, :mod:`crypt` use the " +"OpenSSL library for added performance if made available by the operating " +"system. Additionally, the Windows and Mac OS X installers for Python may " +"include a copy of the OpenSSL libraries, so we include a copy of the OpenSSL " +"license here::" +msgstr "" + +#: ../Doc/license.rst:798 +msgid "expat" +msgstr "" + +#: ../Doc/license.rst:800 +msgid "" +"The :mod:`pyexpat` extension is built using an included copy of the expat " +"sources unless the build is configured ``--with-system-expat``::" +msgstr "" + +#: ../Doc/license.rst:827 +msgid "libffi" +msgstr "" + +#: ../Doc/license.rst:829 +msgid "" +"The :mod:`_ctypes` extension is built using an included copy of the libffi " +"sources unless the build is configured ``--with-system-libffi``::" +msgstr "" + +#: ../Doc/license.rst:856 +msgid "zlib" +msgstr "" + +#: ../Doc/license.rst:858 +msgid "" +"The :mod:`zlib` extension is built using an included copy of the zlib " +"sources if the zlib version found on the system is too old to be used for " +"the build::" +msgstr "" + +#: ../Doc/license.rst:887 +msgid "cfuhash" +msgstr "" + +#: ../Doc/license.rst:889 +msgid "" +"The implementation of the hash table used by the :mod:`tracemalloc` is based " +"on the cfuhash project::" +msgstr "" + +#: ../Doc/license.rst:928 +msgid "libmpdec" +msgstr "" + +#: ../Doc/license.rst:930 +msgid "" +"The :mod:`_decimal` Module is built using an included copy of the libmpdec " +"library unless the build is configured ``--with-system-libmpdec``::" +msgstr "" diff --git a/reference.po b/reference.po new file mode 100644 index 00000000..6ce9d739 --- /dev/null +++ b/reference.po @@ -0,0 +1,9258 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/reference/compound_stmts.rst:5 +msgid "Compound statements" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:9 +msgid "" +"Compound statements contain (groups of) other statements; they affect or " +"control the execution of those other statements in some way. In general, " +"compound statements span multiple lines, although in simple incarnations a " +"whole compound statement may be contained in one line." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:14 +msgid "" +"The :keyword:`if`, :keyword:`while` and :keyword:`for` statements implement " +"traditional control flow constructs. :keyword:`try` specifies exception " +"handlers and/or cleanup code for a group of statements, while the :keyword:" +"`with` statement allows the execution of initialization and finalization " +"code around a block of code. Function and class definitions are also " +"syntactically compound statements." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:25 +msgid "" +"A compound statement consists of one or more 'clauses.' A clause consists " +"of a header and a 'suite.' The clause headers of a particular compound " +"statement are all at the same indentation level. Each clause header begins " +"with a uniquely identifying keyword and ends with a colon. A suite is a " +"group of statements controlled by a clause. A suite can be one or more " +"semicolon-separated simple statements on the same line as the header, " +"following the header's colon, or it can be one or more indented statements " +"on subsequent lines. Only the latter form of a suite can contain nested " +"compound statements; the following is illegal, mostly because it wouldn't be " +"clear to which :keyword:`if` clause a following :keyword:`else` clause would " +"belong::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:38 +msgid "" +"Also note that the semicolon binds tighter than the colon in this context, " +"so that in the following example, either all or none of the :func:`print` " +"calls are executed::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:44 +msgid "Summarizing:" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:66 +msgid "" +"Note that statements always end in a ``NEWLINE`` possibly followed by a " +"``DEDENT``. Also note that optional continuation clauses always begin with " +"a keyword that cannot start a statement, thus there are no ambiguities (the " +"'dangling :keyword:`else`' problem is solved in Python by requiring nested :" +"keyword:`if` statements to be indented)." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:72 +msgid "" +"The formatting of the grammar rules in the following sections places each " +"clause on a separate line for clarity." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:81 +msgid "The :keyword:`if` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:90 +msgid "The :keyword:`if` statement is used for conditional execution:" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:97 +msgid "" +"It selects exactly one of the suites by evaluating the expressions one by " +"one until one is found to be true (see section :ref:`booleans` for the " +"definition of true and false); then that suite is executed (and no other " +"part of the :keyword:`if` statement is executed or evaluated). If all " +"expressions are false, the suite of the :keyword:`else` clause, if present, " +"is executed." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:107 +msgid "The :keyword:`while` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:115 +msgid "" +"The :keyword:`while` statement is used for repeated execution as long as an " +"expression is true:" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:122 +msgid "" +"This repeatedly tests the expression and, if it is true, executes the first " +"suite; if the expression is false (which may be the first time it is tested) " +"the suite of the :keyword:`else` clause, if present, is executed and the " +"loop terminates." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:131 +msgid "" +"A :keyword:`break` statement executed in the first suite terminates the loop " +"without executing the :keyword:`else` clause's suite. A :keyword:`continue` " +"statement executed in the first suite skips the rest of the suite and goes " +"back to testing the expression." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:140 +msgid "The :keyword:`for` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:153 +msgid "" +"The :keyword:`for` statement is used to iterate over the elements of a " +"sequence (such as a string, tuple or list) or other iterable object:" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:160 +msgid "" +"The expression list is evaluated once; it should yield an iterable object. " +"An iterator is created for the result of the ``expression_list``. The suite " +"is then executed once for each item provided by the iterator, in the order " +"returned by the iterator. Each item in turn is assigned to the target list " +"using the standard rules for assignments (see :ref:`assignment`), and then " +"the suite is executed. When the items are exhausted (which is immediately " +"when the sequence is empty or an iterator raises a :exc:`StopIteration` " +"exception), the suite in the :keyword:`else` clause, if present, is " +"executed, and the loop terminates." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:173 +msgid "" +"A :keyword:`break` statement executed in the first suite terminates the loop " +"without executing the :keyword:`else` clause's suite. A :keyword:`continue` " +"statement executed in the first suite skips the rest of the suite and " +"continues with the next item, or with the :keyword:`else` clause if there is " +"no next item." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:179 +msgid "" +"The for-loop makes assignments to the variables(s) in the target list. This " +"overwrites all previous assignments to those variables including those made " +"in the suite of the for-loop::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:193 +msgid "" +"Names in the target list are not deleted when the loop is finished, but if " +"the sequence is empty, they will not have been assigned to at all by the " +"loop. Hint: the built-in function :func:`range` returns an iterator of " +"integers suitable to emulate the effect of Pascal's ``for i := a to b do``; " +"e.g., ``list(range(3))`` returns the list ``[0, 1, 2]``." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:205 +msgid "" +"There is a subtlety when the sequence is being modified by the loop (this " +"can only occur for mutable sequences, i.e. lists). An internal counter is " +"used to keep track of which item is used next, and this is incremented on " +"each iteration. When this counter has reached the length of the sequence " +"the loop terminates. This means that if the suite deletes the current (or a " +"previous) item from the sequence, the next item will be skipped (since it " +"gets the index of the current item which has already been treated). " +"Likewise, if the suite inserts an item in the sequence before the current " +"item, the current item will be treated again the next time through the loop. " +"This can lead to nasty bugs that can be avoided by making a temporary copy " +"using a slice of the whole sequence, e.g., ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:226 +msgid "The :keyword:`try` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:234 +msgid "" +"The :keyword:`try` statement specifies exception handlers and/or cleanup " +"code for a group of statements:" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:247 +msgid "" +"The :keyword:`except` clause(s) specify one or more exception handlers. When " +"no exception occurs in the :keyword:`try` clause, no exception handler is " +"executed. When an exception occurs in the :keyword:`try` suite, a search for " +"an exception handler is started. This search inspects the except clauses in " +"turn until one is found that matches the exception. An expression-less " +"except clause, if present, must be last; it matches any exception. For an " +"except clause with an expression, that expression is evaluated, and the " +"clause matches the exception if the resulting object is \"compatible\" with " +"the exception. An object is compatible with an exception if it is the class " +"or a base class of the exception object or a tuple containing an item " +"compatible with the exception." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:258 +msgid "" +"If no except clause matches the exception, the search for an exception " +"handler continues in the surrounding code and on the invocation stack. [#]_" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:261 +msgid "" +"If the evaluation of an expression in the header of an except clause raises " +"an exception, the original search for a handler is canceled and a search " +"starts for the new exception in the surrounding code and on the call stack " +"(it is treated as if the entire :keyword:`try` statement raised the " +"exception)." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:266 +msgid "" +"When a matching except clause is found, the exception is assigned to the " +"target specified after the :keyword:`as` keyword in that except clause, if " +"present, and the except clause's suite is executed. All except clauses must " +"have an executable block. When the end of this block is reached, execution " +"continues normally after the entire try statement. (This means that if two " +"nested handlers exist for the same exception, and the exception occurs in " +"the try clause of the inner handler, the outer handler will not handle the " +"exception.)" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:274 +msgid "" +"When an exception has been assigned using ``as target``, it is cleared at " +"the end of the except clause. This is as if ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:280 +msgid "was translated to ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:288 +msgid "" +"This means the exception must be assigned to a different name to be able to " +"refer to it after the except clause. Exceptions are cleared because with " +"the traceback attached to them, they form a reference cycle with the stack " +"frame, keeping all locals in that frame alive until the next garbage " +"collection occurs." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:297 +msgid "" +"Before an except clause's suite is executed, details about the exception are " +"stored in the :mod:`sys` module and can be accessed via :func:`sys." +"exc_info`. :func:`sys.exc_info` returns a 3-tuple consisting of the " +"exception class, the exception instance and a traceback object (see section :" +"ref:`types`) identifying the point in the program where the exception " +"occurred. :func:`sys.exc_info` values are restored to their previous values " +"(before the call) when returning from a function that handled an exception." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:311 +msgid "" +"The optional :keyword:`else` clause is executed if and when control flows " +"off the end of the :keyword:`try` clause. [#]_ Exceptions in the :keyword:" +"`else` clause are not handled by the preceding :keyword:`except` clauses." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:317 +msgid "" +"If :keyword:`finally` is present, it specifies a 'cleanup' handler. The :" +"keyword:`try` clause is executed, including any :keyword:`except` and :" +"keyword:`else` clauses. If an exception occurs in any of the clauses and is " +"not handled, the exception is temporarily saved. The :keyword:`finally` " +"clause is executed. If there is a saved exception it is re-raised at the " +"end of the :keyword:`finally` clause. If the :keyword:`finally` clause " +"raises another exception, the saved exception is set as the context of the " +"new exception. If the :keyword:`finally` clause executes a :keyword:`return` " +"or :keyword:`break` statement, the saved exception is discarded::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:336 +msgid "" +"The exception information is not available to the program during execution " +"of the :keyword:`finally` clause." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:344 +msgid "" +"When a :keyword:`return`, :keyword:`break` or :keyword:`continue` statement " +"is executed in the :keyword:`try` suite of a :keyword:`try`...\\ :keyword:" +"`finally` statement, the :keyword:`finally` clause is also executed 'on the " +"way out.' A :keyword:`continue` statement is illegal in the :keyword:" +"`finally` clause. (The reason is a problem with the current implementation " +"--- this restriction may be lifted in the future)." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:351 +msgid "" +"The return value of a function is determined by the last :keyword:`return` " +"statement executed. Since the :keyword:`finally` clause always executes, a :" +"keyword:`return` statement executed in the :keyword:`finally` clause will " +"always be the last one executed::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:365 +msgid "" +"Additional information on exceptions can be found in section :ref:" +"`exceptions`, and information on using the :keyword:`raise` statement to " +"generate exceptions may be found in section :ref:`raise`." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:374 +msgid "The :keyword:`with` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:380 +msgid "" +"The :keyword:`with` statement is used to wrap the execution of a block with " +"methods defined by a context manager (see section :ref:`context-managers`). " +"This allows common :keyword:`try`...\\ :keyword:`except`...\\ :keyword:" +"`finally` usage patterns to be encapsulated for convenient reuse." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:389 +msgid "" +"The execution of the :keyword:`with` statement with one \"item\" proceeds as " +"follows:" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:391 +msgid "" +"The context expression (the expression given in the :token:`with_item`) is " +"evaluated to obtain a context manager." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:394 +msgid "The context manager's :meth:`__exit__` is loaded for later use." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:396 +msgid "The context manager's :meth:`__enter__` method is invoked." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:398 +msgid "" +"If a target was included in the :keyword:`with` statement, the return value " +"from :meth:`__enter__` is assigned to it." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:403 +msgid "" +"The :keyword:`with` statement guarantees that if the :meth:`__enter__` " +"method returns without an error, then :meth:`__exit__` will always be " +"called. Thus, if an error occurs during the assignment to the target list, " +"it will be treated the same as an error occurring within the suite would be. " +"See step 6 below." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:409 +msgid "The suite is executed." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:411 +msgid "" +"The context manager's :meth:`__exit__` method is invoked. If an exception " +"caused the suite to be exited, its type, value, and traceback are passed as " +"arguments to :meth:`__exit__`. Otherwise, three :const:`None` arguments are " +"supplied." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:416 +msgid "" +"If the suite was exited due to an exception, and the return value from the :" +"meth:`__exit__` method was false, the exception is reraised. If the return " +"value was true, the exception is suppressed, and execution continues with " +"the statement following the :keyword:`with` statement." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:421 +msgid "" +"If the suite was exited for any reason other than an exception, the return " +"value from :meth:`__exit__` is ignored, and execution proceeds at the normal " +"location for the kind of exit that was taken." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:425 +msgid "" +"With more than one item, the context managers are processed as if multiple :" +"keyword:`with` statements were nested::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:431 +#: ../Doc/reference/compound_stmts.rst:622 +msgid "is equivalent to ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:437 +msgid "Support for multiple context expressions." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:443 ../Doc/reference/datamodel.rst:2263 +msgid ":pep:`343` - The \"with\" statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:443 ../Doc/reference/datamodel.rst:2263 +msgid "" +"The specification, background, and examples for the Python :keyword:`with` " +"statement." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:454 +msgid "Function definitions" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:466 +msgid "" +"A function definition defines a user-defined function object (see section :" +"ref:`types`):" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:483 +msgid "" +"A function definition is an executable statement. Its execution binds the " +"function name in the current local namespace to a function object (a wrapper " +"around the executable code for the function). This function object contains " +"a reference to the current global namespace as the global namespace to be " +"used when the function is called." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:489 +msgid "" +"The function definition does not execute the function body; this gets " +"executed only when the function is called. [#]_" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:495 +msgid "" +"A function definition may be wrapped by one or more :term:`decorator` " +"expressions. Decorator expressions are evaluated when the function is " +"defined, in the scope that contains the function definition. The result " +"must be a callable, which is invoked with the function object as the only " +"argument. The returned value is bound to the function name instead of the " +"function object. Multiple decorators are applied in nested fashion. For " +"example, the following code ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:506 +#: ../Doc/reference/compound_stmts.rst:649 +msgid "is roughly equivalent to ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:511 +msgid "" +"except that the original function is not temporarily bound to the name " +"``func``." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:517 +msgid "" +"When one or more :term:`parameters ` have the form *parameter* " +"``=`` *expression*, the function is said to have \"default parameter values." +"\" For a parameter with a default value, the corresponding :term:`argument` " +"may be omitted from a call, in which case the parameter's default value is " +"substituted. If a parameter has a default value, all following parameters " +"up until the \"``*``\" must also have a default value --- this is a " +"syntactic restriction that is not expressed by the grammar." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:525 +msgid "" +"**Default parameter values are evaluated from left to right when the " +"function definition is executed.** This means that the expression is " +"evaluated once, when the function is defined, and that the same \"pre-" +"computed\" value is used for each call. This is especially important to " +"understand when a default parameter is a mutable object, such as a list or a " +"dictionary: if the function modifies the object (e.g. by appending an item " +"to a list), the default value is in effect modified. This is generally not " +"what was intended. A way around this is to use ``None`` as the default, and " +"explicitly test for it in the body of the function, e.g.::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:545 +msgid "" +"Function call semantics are described in more detail in section :ref:" +"`calls`. A function call always assigns values to all parameters mentioned " +"in the parameter list, either from position arguments, from keyword " +"arguments, or from default values. If the form \"``*identifier``\" is " +"present, it is initialized to a tuple receiving any excess positional " +"parameters, defaulting to the empty tuple. If the form \"``**identifier``\" " +"is present, it is initialized to a new ordered mapping receiving any excess " +"keyword arguments, defaulting to a new empty mapping of the same type. " +"Parameters after \"``*``\" or \"``*identifier``\" are keyword-only " +"parameters and may only be passed used keyword arguments." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:558 +msgid "" +"Parameters may have annotations of the form \"``: expression``\" following " +"the parameter name. Any parameter may have an annotation even those of the " +"form ``*identifier`` or ``**identifier``. Functions may have \"return\" " +"annotation of the form \"``-> expression``\" after the parameter list. " +"These annotations can be any valid Python expression and are evaluated when " +"the function definition is executed. Annotations may be evaluated in a " +"different order than they appear in the source code. The presence of " +"annotations does not change the semantics of a function. The annotation " +"values are available as values of a dictionary keyed by the parameters' " +"names in the :attr:`__annotations__` attribute of the function object." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:571 +msgid "" +"It is also possible to create anonymous functions (functions not bound to a " +"name), for immediate use in expressions. This uses lambda expressions, " +"described in section :ref:`lambda`. Note that the lambda expression is " +"merely a shorthand for a simplified function definition; a function defined " +"in a \":keyword:`def`\" statement can be passed around or assigned to " +"another name just like a function defined by a lambda expression. The \":" +"keyword:`def`\" form is actually more powerful since it allows the execution " +"of multiple statements and annotations." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:579 +msgid "" +"**Programmer's note:** Functions are first-class objects. A \"``def``\" " +"statement executed inside a function definition defines a local function " +"that can be returned or passed around. Free variables used in the nested " +"function can access the local variables of the function containing the def. " +"See section :ref:`naming` for details." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:587 +msgid ":pep:`3107` - Function Annotations" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:588 +msgid "The original specification for function annotations." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:594 +msgid "Class definitions" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:606 +msgid "A class definition defines a class object (see section :ref:`types`):" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:613 +msgid "" +"A class definition is an executable statement. The inheritance list usually " +"gives a list of base classes (see :ref:`metaclasses` for more advanced " +"uses), so each item in the list should evaluate to a class object which " +"allows subclassing. Classes without an inheritance list inherit, by " +"default, from the base class :class:`object`; hence, ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:627 +msgid "" +"The class's suite is then executed in a new execution frame (see :ref:" +"`naming`), using a newly created local namespace and the original global " +"namespace. (Usually, the suite contains mostly function definitions.) When " +"the class's suite finishes execution, its execution frame is discarded but " +"its local namespace is saved. [#]_ A class object is then created using the " +"inheritance list for the base classes and the saved local namespace for the " +"attribute dictionary. The class name is bound to this class object in the " +"original local namespace." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:636 +msgid "" +"The order in which attributes are defined in the class body is preserved in " +"the new class's ``__dict__``. Note that this is reliable only right after " +"the class is created and only for classes that were defined using the " +"definition syntax." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:641 +msgid "" +"Class creation can be customized heavily using :ref:`metaclasses " +"`." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:643 +msgid "Classes can also be decorated: just like when decorating functions, ::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:654 +msgid "" +"The evaluation rules for the decorator expressions are the same as for " +"function decorators. The result is then bound to the class name." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:657 +msgid "" +"**Programmer's note:** Variables defined in the class definition are class " +"attributes; they are shared by instances. Instance attributes can be set in " +"a method with ``self.name = value``. Both class and instance attributes are " +"accessible through the notation \"``self.name``\", and an instance attribute " +"hides a class attribute with the same name when accessed in this way. Class " +"attributes can be used as defaults for instance attributes, but using " +"mutable values there can lead to unexpected results. :ref:`Descriptors " +"` can be used to create instance variables with different " +"implementation details." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:669 +msgid ":pep:`3115` - Metaclasses in Python 3 :pep:`3129` - Class Decorators" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:674 ../Doc/reference/datamodel.rst:2346 +msgid "Coroutines" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:682 +msgid "Coroutine function definition" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:691 +msgid "" +"Execution of Python coroutines can be suspended and resumed at many points " +"(see :term:`coroutine`). In the body of a coroutine, any ``await`` and " +"``async`` identifiers become reserved keywords; :keyword:`await` " +"expressions, :keyword:`async for` and :keyword:`async with` can only be used " +"in coroutine bodies." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:697 +msgid "" +"Functions defined with ``async def`` syntax are always coroutine functions, " +"even if they do not contain ``await`` or ``async`` keywords." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:700 +msgid "" +"It is a :exc:`SyntaxError` to use :keyword:`yield` expressions in ``async " +"def`` coroutines." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:703 +msgid "An example of a coroutine function::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:714 +msgid "The :keyword:`async for` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:719 +msgid "" +"An :term:`asynchronous iterable` is able to call asynchronous code in its " +"*iter* implementation, and :term:`asynchronous iterator` can call " +"asynchronous code in its *next* method." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:723 +msgid "" +"The ``async for`` statement allows convenient iteration over asynchronous " +"iterators." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:726 +#: ../Doc/reference/compound_stmts.rst:766 +msgid "The following code::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:733 +#: ../Doc/reference/compound_stmts.rst:771 +msgid "Is semantically equivalent to::" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:748 +msgid "See also :meth:`__aiter__` and :meth:`__anext__` for details." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:750 +msgid "" +"It is a :exc:`SyntaxError` to use ``async for`` statement outside of an :" +"keyword:`async def` function." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:758 +msgid "The :keyword:`async with` statement" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:763 +msgid "" +"An :term:`asynchronous context manager` is a :term:`context manager` that is " +"able to suspend execution in its *enter* and *exit* methods." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:787 +msgid "See also :meth:`__aenter__` and :meth:`__aexit__` for details." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:789 +msgid "" +"It is a :exc:`SyntaxError` to use ``async with`` statement outside of an :" +"keyword:`async def` function." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:794 +msgid ":pep:`492` - Coroutines with async and await syntax" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:798 ../Doc/reference/datamodel.rst:2540 +#: ../Doc/reference/executionmodel.rst:270 +#: ../Doc/reference/expressions.rst:1550 ../Doc/reference/import.rst:991 +#: ../Doc/reference/lexical_analysis.rst:861 +msgid "Footnotes" +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:799 +msgid "" +"The exception is propagated to the invocation stack unless there is a :" +"keyword:`finally` clause which happens to raise another exception. That new " +"exception causes the old one to be lost." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:803 +msgid "" +"Currently, control \"flows off the end\" except in the case of an exception " +"or the execution of a :keyword:`return`, :keyword:`continue`, or :keyword:" +"`break` statement." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:807 +msgid "" +"A string literal appearing as the first statement in the function body is " +"transformed into the function's ``__doc__`` attribute and therefore the " +"function's :term:`docstring`." +msgstr "" + +#: ../Doc/reference/compound_stmts.rst:811 +msgid "" +"A string literal appearing as the first statement in the class body is " +"transformed into the namespace's ``__doc__`` item and therefore the class's :" +"term:`docstring`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:6 +msgid "Data model" +msgstr "" + +#: ../Doc/reference/datamodel.rst:12 +msgid "Objects, values and types" +msgstr "" + +#: ../Doc/reference/datamodel.rst:18 +msgid "" +":dfn:`Objects` are Python's abstraction for data. All data in a Python " +"program is represented by objects or by relations between objects. (In a " +"sense, and in conformance to Von Neumann's model of a \"stored program " +"computer,\" code is also represented by objects.)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:35 +msgid "" +"Every object has an identity, a type and a value. An object's *identity* " +"never changes once it has been created; you may think of it as the object's " +"address in memory. The ':keyword:`is`' operator compares the identity of " +"two objects; the :func:`id` function returns an integer representing its " +"identity." +msgstr "" + +#: ../Doc/reference/datamodel.rst:42 +msgid "For CPython, ``id(x)`` is the memory address where ``x`` is stored." +msgstr "" + +#: ../Doc/reference/datamodel.rst:44 +msgid "" +"An object's type determines the operations that the object supports (e.g., " +"\"does it have a length?\") and also defines the possible values for objects " +"of that type. The :func:`type` function returns an object's type (which is " +"an object itself). Like its identity, an object's :dfn:`type` is also " +"unchangeable. [#]_" +msgstr "" + +#: ../Doc/reference/datamodel.rst:50 +msgid "" +"The *value* of some objects can change. Objects whose value can change are " +"said to be *mutable*; objects whose value is unchangeable once they are " +"created are called *immutable*. (The value of an immutable container object " +"that contains a reference to a mutable object can change when the latter's " +"value is changed; however the container is still considered immutable, " +"because the collection of objects it contains cannot be changed. So, " +"immutability is not strictly the same as having an unchangeable value, it is " +"more subtle.) An object's mutability is determined by its type; for " +"instance, numbers, strings and tuples are immutable, while dictionaries and " +"lists are mutable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:65 +msgid "" +"Objects are never explicitly destroyed; however, when they become " +"unreachable they may be garbage-collected. An implementation is allowed to " +"postpone garbage collection or omit it altogether --- it is a matter of " +"implementation quality how garbage collection is implemented, as long as no " +"objects are collected that are still reachable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:73 +msgid "" +"CPython currently uses a reference-counting scheme with (optional) delayed " +"detection of cyclically linked garbage, which collects most objects as soon " +"as they become unreachable, but is not guaranteed to collect garbage " +"containing circular references. See the documentation of the :mod:`gc` " +"module for information on controlling the collection of cyclic garbage. " +"Other implementations act differently and CPython may change. Do not depend " +"on immediate finalization of objects when they become unreachable (so you " +"should always close files explicitly)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:82 +msgid "" +"Note that the use of the implementation's tracing or debugging facilities " +"may keep objects alive that would normally be collectable. Also note that " +"catching an exception with a ':keyword:`try`...\\ :keyword:`except`' " +"statement may keep objects alive." +msgstr "" + +#: ../Doc/reference/datamodel.rst:87 +msgid "" +"Some objects contain references to \"external\" resources such as open files " +"or windows. It is understood that these resources are freed when the object " +"is garbage-collected, but since garbage collection is not guaranteed to " +"happen, such objects also provide an explicit way to release the external " +"resource, usually a :meth:`close` method. Programs are strongly recommended " +"to explicitly close such objects. The ':keyword:`try`...\\ :keyword:" +"`finally`' statement and the ':keyword:`with`' statement provide convenient " +"ways to do this." +msgstr "" + +#: ../Doc/reference/datamodel.rst:97 +msgid "" +"Some objects contain references to other objects; these are called " +"*containers*. Examples of containers are tuples, lists and dictionaries. " +"The references are part of a container's value. In most cases, when we talk " +"about the value of a container, we imply the values, not the identities of " +"the contained objects; however, when we talk about the mutability of a " +"container, only the identities of the immediately contained objects are " +"implied. So, if an immutable container (like a tuple) contains a reference " +"to a mutable object, its value changes if that mutable object is changed." +msgstr "" + +#: ../Doc/reference/datamodel.rst:106 +msgid "" +"Types affect almost all aspects of object behavior. Even the importance of " +"object identity is affected in some sense: for immutable types, operations " +"that compute new values may actually return a reference to any existing " +"object with the same type and value, while for mutable objects this is not " +"allowed. E.g., after ``a = 1; b = 1``, ``a`` and ``b`` may or may not refer " +"to the same object with the value one, depending on the implementation, but " +"after ``c = []; d = []``, ``c`` and ``d`` are guaranteed to refer to two " +"different, unique, newly created empty lists. (Note that ``c = d = []`` " +"assigns the same object to both ``c`` and ``d``.)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:120 +msgid "The standard type hierarchy" +msgstr "" + +#: ../Doc/reference/datamodel.rst:129 +msgid "" +"Below is a list of the types that are built into Python. Extension modules " +"(written in C, Java, or other languages, depending on the implementation) " +"can define additional types. Future versions of Python may add types to the " +"type hierarchy (e.g., rational numbers, efficiently stored arrays of " +"integers, etc.), although such additions will often be provided via the " +"standard library instead." +msgstr "" + +#: ../Doc/reference/datamodel.rst:140 +msgid "" +"Some of the type descriptions below contain a paragraph listing 'special " +"attributes.' These are attributes that provide access to the implementation " +"and are not intended for general use. Their definition may change in the " +"future." +msgstr "" + +#: ../Doc/reference/datamodel.rst:150 +msgid "None" +msgstr "" + +#: ../Doc/reference/datamodel.rst:147 +msgid "" +"This type has a single value. There is a single object with this value. " +"This object is accessed through the built-in name ``None``. It is used to " +"signify the absence of a value in many situations, e.g., it is returned from " +"functions that don't explicitly return anything. Its truth value is false." +msgstr "" + +#: ../Doc/reference/datamodel.rst:165 +msgid "NotImplemented" +msgstr "" + +#: ../Doc/reference/datamodel.rst:155 +msgid "" +"This type has a single value. There is a single object with this value. " +"This object is accessed through the built-in name ``NotImplemented``. " +"Numeric methods and rich comparison methods should return this value if they " +"do not implement the operation for the operands provided. (The interpreter " +"will then try the reflected operation, or some other fallback, depending on " +"the operator.) Its truth value is true." +msgstr "" + +#: ../Doc/reference/datamodel.rst:162 +msgid "See :ref:`implementing-the-arithmetic-operations` for more details." +msgstr "" + +#: ../Doc/reference/datamodel.rst:172 +msgid "Ellipsis" +msgstr "" + +#: ../Doc/reference/datamodel.rst:170 +msgid "" +"This type has a single value. There is a single object with this value. " +"This object is accessed through the literal ``...`` or the built-in name " +"``Ellipsis``. Its truth value is true." +msgstr "" + +#: ../Doc/reference/datamodel.rst:242 +msgid ":class:`numbers.Number`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:177 +msgid "" +"These are created by numeric literals and returned as results by arithmetic " +"operators and arithmetic built-in functions. Numeric objects are immutable; " +"once created their value never changes. Python numbers are of course " +"strongly related to mathematical numbers, but subject to the limitations of " +"numerical representation in computers." +msgstr "" + +#: ../Doc/reference/datamodel.rst:183 +msgid "" +"Python distinguishes between integers, floating point numbers, and complex " +"numbers:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:217 +msgid ":class:`numbers.Integral`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:189 +msgid "" +"These represent elements from the mathematical set of integers (positive and " +"negative)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:192 +msgid "There are two types of integers:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:194 +msgid "Integers (:class:`int`)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:196 +msgid "" +"These represent numbers in an unlimited range, subject to available " +"(virtual) memory only. For the purpose of shift and mask operations, a " +"binary representation is assumed, and negative numbers are represented in a " +"variant of 2's complement which gives the illusion of an infinite string of " +"sign bits extending to the left." +msgstr "" + +#: ../Doc/reference/datamodel.rst:212 +msgid "Booleans (:class:`bool`)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:208 +msgid "" +"These represent the truth values False and True. The two objects " +"representing the values ``False`` and ``True`` are the only Boolean objects. " +"The Boolean type is a subtype of the integer type, and Boolean values behave " +"like the values 0 and 1, respectively, in almost all contexts, the exception " +"being that when converted to a string, the strings ``\"False\"`` or ``\"True" +"\"`` are returned, respectively." +msgstr "" + +#: ../Doc/reference/datamodel.rst:216 +msgid "" +"The rules for integer representation are intended to give the most " +"meaningful interpretation of shift and mask operations involving negative " +"integers." +msgstr "" + +#: ../Doc/reference/datamodel.rst:232 +msgid ":class:`numbers.Real` (:class:`float`)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:226 +msgid "" +"These represent machine-level double precision floating point numbers. You " +"are at the mercy of the underlying machine architecture (and C or Java " +"implementation) for the accepted range and handling of overflow. Python does " +"not support single-precision floating point numbers; the savings in " +"processor and memory usage that are usually the reason for using these are " +"dwarfed by the overhead of using objects in Python, so there is no reason to " +"complicate the language with two kinds of floating point numbers." +msgstr "" + +#: ../Doc/reference/datamodel.rst:242 +msgid ":class:`numbers.Complex` (:class:`complex`)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:239 +msgid "" +"These represent complex numbers as a pair of machine-level double precision " +"floating point numbers. The same caveats apply as for floating point " +"numbers. The real and imaginary parts of a complex number ``z`` can be " +"retrieved through the read-only attributes ``z.real`` and ``z.imag``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:359 +msgid "Sequences" +msgstr "" + +#: ../Doc/reference/datamodel.rst:252 +msgid "" +"These represent finite ordered sets indexed by non-negative numbers. The " +"built-in function :func:`len` returns the number of items of a sequence. " +"When the length of a sequence is *n*, the index set contains the numbers 0, " +"1, ..., *n*-1. Item *i* of sequence *a* is selected by ``a[i]``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:259 +msgid "" +"Sequences also support slicing: ``a[i:j]`` selects all items with index *k* " +"such that *i* ``<=`` *k* ``<`` *j*. When used as an expression, a slice is " +"a sequence of the same type. This implies that the index set is renumbered " +"so that it starts at 0." +msgstr "" + +#: ../Doc/reference/datamodel.rst:264 +msgid "" +"Some sequences also support \"extended slicing\" with a third \"step\" " +"parameter: ``a[i:j:k]`` selects all items of *a* with index *x* where ``x = " +"i + n*k``, *n* ``>=`` ``0`` and *i* ``<=`` *x* ``<`` *j*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:268 +msgid "Sequences are distinguished according to their mutability:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:325 +msgid "Immutable sequences" +msgstr "" + +#: ../Doc/reference/datamodel.rst:275 +msgid "" +"An object of an immutable sequence type cannot change once it is created. " +"(If the object contains references to other objects, these other objects may " +"be mutable and may be changed; however, the collection of objects directly " +"referenced by an immutable object cannot change.)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:280 +msgid "The following types are immutable sequences:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:303 +msgid "Strings" +msgstr "" + +#: ../Doc/reference/datamodel.rst:293 +msgid "" +"A string is a sequence of values that represent Unicode code points. All the " +"code points in the range ``U+0000 - U+10FFFF`` can be represented in a " +"string. Python doesn't have a :c:type:`char` type; instead, every code " +"point in the string is represented as a string object with length ``1``. " +"The built-in function :func:`ord` converts a code point from its string form " +"to an integer in the range ``0 - 10FFFF``; :func:`chr` converts an integer " +"in the range ``0 - 10FFFF`` to the corresponding length ``1`` string " +"object. :meth:`str.encode` can be used to convert a :class:`str` to :class:" +"`bytes` using the given text encoding, and :meth:`bytes.decode` can be used " +"to achieve the opposite." +msgstr "" + +#: ../Doc/reference/datamodel.rst:316 +msgid "Tuples" +msgstr "" + +#: ../Doc/reference/datamodel.rst:311 +msgid "" +"The items of a tuple are arbitrary Python objects. Tuples of two or more " +"items are formed by comma-separated lists of expressions. A tuple of one " +"item (a 'singleton') can be formed by affixing a comma to an expression (an " +"expression by itself does not create a tuple, since parentheses must be " +"usable for grouping of expressions). An empty tuple can be formed by an " +"empty pair of parentheses." +msgstr "" + +#: ../Doc/reference/datamodel.rst:325 +msgid "Bytes" +msgstr "" + +#: ../Doc/reference/datamodel.rst:321 +msgid "" +"A bytes object is an immutable array. The items are 8-bit bytes, " +"represented by integers in the range 0 <= x < 256. Bytes literals (like " +"``b'abc'``) and the built-in function :func:`bytes` can be used to construct " +"bytes objects. Also, bytes objects can be decoded to strings via the :meth:" +"`~bytes.decode` method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:359 +msgid "Mutable sequences" +msgstr "" + +#: ../Doc/reference/datamodel.rst:335 +msgid "" +"Mutable sequences can be changed after they are created. The subscription " +"and slicing notations can be used as the target of assignment and :keyword:" +"`del` (delete) statements." +msgstr "" + +#: ../Doc/reference/datamodel.rst:339 +msgid "There are currently two intrinsic mutable sequence types:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:346 +msgid "Lists" +msgstr "" + +#: ../Doc/reference/datamodel.rst:344 +msgid "" +"The items of a list are arbitrary Python objects. Lists are formed by " +"placing a comma-separated list of expressions in square brackets. (Note that " +"there are no special cases needed to form lists of length 0 or 1.)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:354 +msgid "Byte Arrays" +msgstr "" + +#: ../Doc/reference/datamodel.rst:351 +msgid "" +"A bytearray object is a mutable array. They are created by the built-in :" +"func:`bytearray` constructor. Aside from being mutable (and hence " +"unhashable), byte arrays otherwise provide the same interface and " +"functionality as immutable bytes objects." +msgstr "" + +#: ../Doc/reference/datamodel.rst:358 +msgid "" +"The extension module :mod:`array` provides an additional example of a " +"mutable sequence type, as does the :mod:`collections` module." +msgstr "" + +#: ../Doc/reference/datamodel.rst:393 +msgid "Set types" +msgstr "" + +#: ../Doc/reference/datamodel.rst:366 +msgid "" +"These represent unordered, finite sets of unique, immutable objects. As " +"such, they cannot be indexed by any subscript. However, they can be iterated " +"over, and the built-in function :func:`len` returns the number of items in a " +"set. Common uses for sets are fast membership testing, removing duplicates " +"from a sequence, and computing mathematical operations such as intersection, " +"union, difference, and symmetric difference." +msgstr "" + +#: ../Doc/reference/datamodel.rst:373 +msgid "" +"For set elements, the same immutability rules apply as for dictionary keys. " +"Note that numeric types obey the normal rules for numeric comparison: if two " +"numbers compare equal (e.g., ``1`` and ``1.0``), only one of them can be " +"contained in a set." +msgstr "" + +#: ../Doc/reference/datamodel.rst:378 +msgid "There are currently two intrinsic set types:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:385 +msgid "Sets" +msgstr "" + +#: ../Doc/reference/datamodel.rst:383 +msgid "" +"These represent a mutable set. They are created by the built-in :func:`set` " +"constructor and can be modified afterwards by several methods, such as :meth:" +"`~set.add`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:393 +msgid "Frozen sets" +msgstr "" + +#: ../Doc/reference/datamodel.rst:390 +msgid "" +"These represent an immutable set. They are created by the built-in :func:" +"`frozenset` constructor. As a frozenset is immutable and :term:`hashable`, " +"it can be used again as an element of another set, or as a dictionary key." +msgstr "" + +#: ../Doc/reference/datamodel.rst:430 +msgid "Mappings" +msgstr "" + +#: ../Doc/reference/datamodel.rst:401 +msgid "" +"These represent finite sets of objects indexed by arbitrary index sets. The " +"subscript notation ``a[k]`` selects the item indexed by ``k`` from the " +"mapping ``a``; this can be used in expressions and as the target of " +"assignments or :keyword:`del` statements. The built-in function :func:`len` " +"returns the number of items in a mapping." +msgstr "" + +#: ../Doc/reference/datamodel.rst:407 +msgid "There is currently a single intrinsic mapping type:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:430 +msgid "Dictionaries" +msgstr "" + +#: ../Doc/reference/datamodel.rst:412 +msgid "" +"These represent finite sets of objects indexed by nearly arbitrary values. " +"The only types of values not acceptable as keys are values containing lists " +"or dictionaries or other mutable types that are compared by value rather " +"than by object identity, the reason being that the efficient implementation " +"of dictionaries requires a key's hash value to remain constant. Numeric " +"types used for keys obey the normal rules for numeric comparison: if two " +"numbers compare equal (e.g., ``1`` and ``1.0``) then they can be used " +"interchangeably to index the same dictionary entry." +msgstr "" + +#: ../Doc/reference/datamodel.rst:421 +msgid "" +"Dictionaries are mutable; they can be created by the ``{...}`` notation (see " +"section :ref:`dict`)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:428 +msgid "" +"The extension modules :mod:`dbm.ndbm` and :mod:`dbm.gnu` provide additional " +"examples of mapping types, as does the :mod:`collections` module." +msgstr "" + +#: ../Doc/reference/datamodel.rst:667 +msgid "Callable types" +msgstr "" + +#: ../Doc/reference/datamodel.rst:439 +msgid "" +"These are the types to which the function call operation (see section :ref:" +"`calls`) can be applied:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:534 +msgid "User-defined functions" +msgstr "" + +#: ../Doc/reference/datamodel.rst:448 +msgid "" +"A user-defined function object is created by a function definition (see " +"section :ref:`function`). It should be called with an argument list " +"containing the same number of items as the function's formal parameter list." +msgstr "" + +#: ../Doc/reference/datamodel.rst:453 +msgid "Special attributes:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:471 +msgid "Attribute" +msgstr "" + +#: ../Doc/reference/datamodel.rst:471 ../Doc/reference/lexical_analysis.rst:484 +#: ../Doc/reference/lexical_analysis.rst:517 +msgid "Meaning" +msgstr "" + +#: ../Doc/reference/datamodel.rst:473 +msgid ":attr:`__doc__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:473 +msgid "" +"The function's documentation string, or ``None`` if unavailable; not " +"inherited by subclasses" +msgstr "" + +#: ../Doc/reference/datamodel.rst:473 ../Doc/reference/datamodel.rst:478 +#: ../Doc/reference/datamodel.rst:481 ../Doc/reference/datamodel.rst:486 +#: ../Doc/reference/datamodel.rst:490 ../Doc/reference/datamodel.rst:496 +#: ../Doc/reference/datamodel.rst:506 ../Doc/reference/datamodel.rst:514 +#: ../Doc/reference/datamodel.rst:521 +msgid "Writable" +msgstr "" + +#: ../Doc/reference/datamodel.rst:478 +msgid ":attr:`~definition.\\ __name__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:478 +msgid "The function's name" +msgstr "" + +#: ../Doc/reference/datamodel.rst:481 +msgid ":attr:`~definition.\\ __qualname__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:481 +msgid "The function's :term:`qualified name`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:486 +msgid ":attr:`__module__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:486 +msgid "" +"The name of the module the function was defined in, or ``None`` if " +"unavailable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:490 +msgid ":attr:`__defaults__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:490 +msgid "" +"A tuple containing default argument values for those arguments that have " +"defaults, or ``None`` if no arguments have a default value" +msgstr "" + +#: ../Doc/reference/datamodel.rst:496 +msgid ":attr:`__code__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:496 +msgid "The code object representing the compiled function body." +msgstr "" + +#: ../Doc/reference/datamodel.rst:499 +msgid ":attr:`__globals__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:499 +msgid "" +"A reference to the dictionary that holds the function's global variables --- " +"the global namespace of the module in which the function was defined." +msgstr "" + +#: ../Doc/reference/datamodel.rst:499 ../Doc/reference/datamodel.rst:510 +msgid "Read-only" +msgstr "" + +#: ../Doc/reference/datamodel.rst:506 +msgid ":attr:`~object.__dict__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:506 +msgid "The namespace supporting arbitrary function attributes." +msgstr "" + +#: ../Doc/reference/datamodel.rst:510 +msgid ":attr:`__closure__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:510 +msgid "" +"``None`` or a tuple of cells that contain bindings for the function's free " +"variables." +msgstr "" + +#: ../Doc/reference/datamodel.rst:514 +msgid ":attr:`__annotations__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:514 +msgid "" +"A dict containing annotations of parameters. The keys of the dict are the " +"parameter names, and ``'return'`` for the return annotation, if provided." +msgstr "" + +#: ../Doc/reference/datamodel.rst:521 +msgid ":attr:`__kwdefaults__`" +msgstr "" + +#: ../Doc/reference/datamodel.rst:521 +msgid "A dict containing defaults for keyword-only parameters." +msgstr "" + +#: ../Doc/reference/datamodel.rst:525 +msgid "" +"Most of the attributes labelled \"Writable\" check the type of the assigned " +"value." +msgstr "" + +#: ../Doc/reference/datamodel.rst:527 +msgid "" +"Function objects also support getting and setting arbitrary attributes, " +"which can be used, for example, to attach metadata to functions. Regular " +"attribute dot-notation is used to get and set such attributes. *Note that " +"the current implementation only supports function attributes on user-defined " +"functions. Function attributes on built-in functions may be supported in the " +"future.*" +msgstr "" + +#: ../Doc/reference/datamodel.rst:533 +msgid "" +"Additional information about a function's definition can be retrieved from " +"its code object; see the description of internal types below." +msgstr "" + +#: ../Doc/reference/datamodel.rst:603 +msgid "Instance methods" +msgstr "" + +#: ../Doc/reference/datamodel.rst:542 +msgid "" +"An instance method object combines a class, a class instance and any " +"callable object (normally a user-defined function)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:552 +msgid "" +"Special read-only attributes: :attr:`__self__` is the class instance " +"object, :attr:`__func__` is the function object; :attr:`__doc__` is the " +"method's documentation (same as ``__func__.__doc__``); :attr:`~definition." +"__name__` is the method name (same as ``__func__.__name__``); :attr:" +"`__module__` is the name of the module the method was defined in, or " +"``None`` if unavailable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:558 +msgid "" +"Methods also support accessing (but not setting) the arbitrary function " +"attributes on the underlying function object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:561 +msgid "" +"User-defined method objects may be created when getting an attribute of a " +"class (perhaps via an instance of that class), if that attribute is a user-" +"defined function object or a class method object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:565 +msgid "" +"When an instance method object is created by retrieving a user-defined " +"function object from a class via one of its instances, its :attr:`__self__` " +"attribute is the instance, and the method object is said to be bound. The " +"new method's :attr:`__func__` attribute is the original function object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:571 +msgid "" +"When a user-defined method object is created by retrieving another method " +"object from a class or instance, the behaviour is the same as for a function " +"object, except that the :attr:`__func__` attribute of the new instance is " +"not the original method object but its :attr:`__func__` attribute." +msgstr "" + +#: ../Doc/reference/datamodel.rst:577 +msgid "" +"When an instance method object is created by retrieving a class method " +"object from a class or instance, its :attr:`__self__` attribute is the class " +"itself, and its :attr:`__func__` attribute is the function object underlying " +"the class method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:582 +msgid "" +"When an instance method object is called, the underlying function (:attr:" +"`__func__`) is called, inserting the class instance (:attr:`__self__`) in " +"front of the argument list. For instance, when :class:`C` is a class which " +"contains a definition for a function :meth:`f`, and ``x`` is an instance of :" +"class:`C`, calling ``x.f(1)`` is equivalent to calling ``C.f(x, 1)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:589 +msgid "" +"When an instance method object is derived from a class method object, the " +"\"class instance\" stored in :attr:`__self__` will actually be the class " +"itself, so that calling either ``x.f(1)`` or ``C.f(1)`` is equivalent to " +"calling ``f(C,1)`` where ``f`` is the underlying function." +msgstr "" + +#: ../Doc/reference/datamodel.rst:594 +msgid "" +"Note that the transformation from function object to instance method object " +"happens each time the attribute is retrieved from the instance. In some " +"cases, a fruitful optimization is to assign the attribute to a local " +"variable and call that local variable. Also notice that this transformation " +"only happens for user-defined functions; other callable objects (and all non-" +"callable objects) are retrieved without transformation. It is also " +"important to note that user-defined functions which are attributes of a " +"class instance are not converted to bound methods; this *only* happens when " +"the function is an attribute of the class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:618 +msgid "Generator functions" +msgstr "" + +#: ../Doc/reference/datamodel.rst:610 +msgid "" +"A function or method which uses the :keyword:`yield` statement (see section :" +"ref:`yield`) is called a :dfn:`generator function`. Such a function, when " +"called, always returns an iterator object which can be used to execute the " +"body of the function: calling the iterator's :meth:`iterator.__next__` " +"method will cause the function to execute until it provides a value using " +"the :keyword:`yield` statement. When the function executes a :keyword:" +"`return` statement or falls off the end, a :exc:`StopIteration` exception is " +"raised and the iterator will have reached the end of the set of values to be " +"returned." +msgstr "" + +#: ../Doc/reference/datamodel.rst:628 +msgid "Coroutine functions" +msgstr "" + +#: ../Doc/reference/datamodel.rst:624 +msgid "" +"A function or method which is defined using :keyword:`async def` is called " +"a :dfn:`coroutine function`. Such a function, when called, returns a :term:" +"`coroutine` object. It may contain :keyword:`await` expressions, as well " +"as :keyword:`async with` and :keyword:`async for` statements. See also the :" +"ref:`coroutine-objects` section." +msgstr "" + +#: ../Doc/reference/datamodel.rst:643 +msgid "Built-in functions" +msgstr "" + +#: ../Doc/reference/datamodel.rst:636 +msgid "" +"A built-in function object is a wrapper around a C function. Examples of " +"built-in functions are :func:`len` and :func:`math.sin` (:mod:`math` is a " +"standard built-in module). The number and type of the arguments are " +"determined by the C function. Special read-only attributes: :attr:`__doc__` " +"is the function's documentation string, or ``None`` if unavailable; :attr:" +"`~definition.__name__` is the function's name; :attr:`__self__` is set to " +"``None`` (but see the next item); :attr:`__module__` is the name of the " +"module the function was defined in or ``None`` if unavailable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:655 +msgid "Built-in methods" +msgstr "" + +#: ../Doc/reference/datamodel.rst:651 +msgid "" +"This is really a different disguise of a built-in function, this time " +"containing an object passed to the C function as an implicit extra " +"argument. An example of a built-in method is ``alist.append()``, assuming " +"*alist* is a list object. In this case, the special read-only attribute :" +"attr:`__self__` is set to the object denoted by *alist*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:662 +msgid "Classes" +msgstr "" + +#: ../Doc/reference/datamodel.rst:658 +msgid "" +"Classes are callable. These objects normally act as factories for new " +"instances of themselves, but variations are possible for class types that " +"override :meth:`__new__`. The arguments of the call are passed to :meth:" +"`__new__` and, in the typical case, to :meth:`__init__` to initialize the " +"new instance." +msgstr "" + +#: ../Doc/reference/datamodel.rst:667 +msgid "Class Instances" +msgstr "" + +#: ../Doc/reference/datamodel.rst:665 +msgid "" +"Instances of arbitrary classes can be made callable by defining a :meth:" +"`__call__` method in their class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:717 +msgid "Modules" +msgstr "" + +#: ../Doc/reference/datamodel.rst:674 +msgid "" +"Modules are a basic organizational unit of Python code, and are created by " +"the :ref:`import system ` as invoked either by the :keyword:" +"`import` statement (see :keyword:`import`), or by calling functions such as :" +"func:`importlib.import_module` and built-in :func:`__import__`. A module " +"object has a namespace implemented by a dictionary object (this is the " +"dictionary referenced by the ``__globals__`` attribute of functions defined " +"in the module). Attribute references are translated to lookups in this " +"dictionary, e.g., ``m.x`` is equivalent to ``m.__dict__[\"x\"]``. A module " +"object does not contain the code object used to initialize the module (since " +"it isn't needed once the initialization is done)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:686 +msgid "" +"Attribute assignment updates the module's namespace dictionary, e.g., ``m.x " +"= 1`` is equivalent to ``m.__dict__[\"x\"] = 1``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:696 +msgid "" +"Predefined (writable) attributes: :attr:`__name__` is the module's name; :" +"attr:`__doc__` is the module's documentation string, or ``None`` if " +"unavailable; :attr:`__annotations__` (optional) is a dictionary containing :" +"term:`variable annotations ` collected during module " +"body execution; :attr:`__file__` is the pathname of the file from which the " +"module was loaded, if it was loaded from a file. The :attr:`__file__` " +"attribute may be missing for certain types of modules, such as C modules " +"that are statically linked into the interpreter; for extension modules " +"loaded dynamically from a shared library, it is the pathname of the shared " +"library file." +msgstr "" + +#: ../Doc/reference/datamodel.rst:709 +msgid "" +"Special read-only attribute: :attr:`~object.__dict__` is the module's " +"namespace as a dictionary object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:714 +msgid "" +"Because of the way CPython clears module dictionaries, the module dictionary " +"will be cleared when the module falls out of scope even if the dictionary " +"still has live references. To avoid this, copy the dictionary or keep the " +"module around while using its dictionary directly." +msgstr "" + +#: ../Doc/reference/datamodel.rst:777 +msgid "Custom classes" +msgstr "" + +#: ../Doc/reference/datamodel.rst:720 +msgid "" +"Custom class types are typically created by class definitions (see section :" +"ref:`class`). A class has a namespace implemented by a dictionary object. " +"Class attribute references are translated to lookups in this dictionary, e." +"g., ``C.x`` is translated to ``C.__dict__[\"x\"]`` (although there are a " +"number of hooks which allow for other means of locating attributes). When " +"the attribute name is not found there, the attribute search continues in the " +"base classes. This search of the base classes uses the C3 method resolution " +"order which behaves correctly even in the presence of 'diamond' inheritance " +"structures where there are multiple inheritance paths leading back to a " +"common ancestor. Additional details on the C3 MRO used by Python can be " +"found in the documentation accompanying the 2.3 release at https://www." +"python.org/download/releases/2.3/mro/." +msgstr "" + +#: ../Doc/reference/datamodel.rst:744 +msgid "" +"When a class attribute reference (for class :class:`C`, say) would yield a " +"class method object, it is transformed into an instance method object whose :" +"attr:`__self__` attributes is :class:`C`. When it would yield a static " +"method object, it is transformed into the object wrapped by the static " +"method object. See section :ref:`descriptors` for another way in which " +"attributes retrieved from a class may differ from those actually contained " +"in its :attr:`~object.__dict__`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:754 +msgid "" +"Class attribute assignments update the class's dictionary, never the " +"dictionary of a base class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:759 +msgid "" +"A class object can be called (see above) to yield a class instance (see " +"below)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:769 +msgid "" +"Special attributes: :attr:`~definition.__name__` is the class name; :attr:" +"`__module__` is the module name in which the class was defined; :attr:" +"`~object.__dict__` is the dictionary containing the class's namespace; :attr:" +"`~class.__bases__` is a tuple (possibly empty or a singleton) containing the " +"base classes, in the order of their occurrence in the base class list; :attr:" +"`__doc__` is the class's documentation string, or None if undefined; :attr:" +"`__annotations__` (optional) is a dictionary containing :term:`variable " +"annotations ` collected during class body execution." +msgstr "" + +#: ../Doc/reference/datamodel.rst:820 +msgid "Class instances" +msgstr "" + +#: ../Doc/reference/datamodel.rst:786 +msgid "" +"A class instance is created by calling a class object (see above). A class " +"instance has a namespace implemented as a dictionary which is the first " +"place in which attribute references are searched. When an attribute is not " +"found there, and the instance's class has an attribute by that name, the " +"search continues with the class attributes. If a class attribute is found " +"that is a user-defined function object, it is transformed into an instance " +"method object whose :attr:`__self__` attribute is the instance. Static " +"method and class method objects are also transformed; see above under " +"\"Classes\". See section :ref:`descriptors` for another way in which " +"attributes of a class retrieved via its instances may differ from the " +"objects actually stored in the class's :attr:`~object.__dict__`. If no " +"class attribute is found, and the object's class has a :meth:`__getattr__` " +"method, that is called to satisfy the lookup." +msgstr "" + +#: ../Doc/reference/datamodel.rst:802 +msgid "" +"Attribute assignments and deletions update the instance's dictionary, never " +"a class's dictionary. If the class has a :meth:`__setattr__` or :meth:" +"`__delattr__` method, this is called instead of updating the instance " +"dictionary directly." +msgstr "" + +#: ../Doc/reference/datamodel.rst:812 +msgid "" +"Class instances can pretend to be numbers, sequences, or mappings if they " +"have methods with certain special names. See section :ref:`specialnames`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:819 +msgid "" +"Special attributes: :attr:`~object.__dict__` is the attribute dictionary; :" +"attr:`~instance.__class__` is the instance's class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:846 +msgid "I/O objects (also known as file objects)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:836 +msgid "" +"A :term:`file object` represents an open file. Various shortcuts are " +"available to create file objects: the :func:`open` built-in function, and " +"also :func:`os.popen`, :func:`os.fdopen`, and the :meth:`~socket.socket." +"makefile` method of socket objects (and perhaps by other functions or " +"methods provided by extension modules)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:842 +msgid "" +"The objects ``sys.stdin``, ``sys.stdout`` and ``sys.stderr`` are initialized " +"to file objects corresponding to the interpreter's standard input, output " +"and error streams; they are all open in text mode and therefore follow the " +"interface defined by the :class:`io.TextIOBase` abstract class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1052 +msgid "Internal types" +msgstr "" + +#: ../Doc/reference/datamodel.rst:853 +msgid "" +"A few types used internally by the interpreter are exposed to the user. " +"Their definitions may change with future versions of the interpreter, but " +"they are mentioned here for completeness." +msgstr "" + +#: ../Doc/reference/datamodel.rst:921 +msgid "Code objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:860 +msgid "" +"Code objects represent *byte-compiled* executable Python code, or :term:" +"`bytecode`. The difference between a code object and a function object is " +"that the function object contains an explicit reference to the function's " +"globals (the module in which it was defined), while a code object contains " +"no context; also the default argument values are stored in the function " +"object, not in the code object (because they represent values calculated at " +"run-time). Unlike function objects, code objects are immutable and contain " +"no references (directly or indirectly) to mutable objects." +msgstr "" + +#: ../Doc/reference/datamodel.rst:885 +msgid "" +"Special read-only attributes: :attr:`co_name` gives the function name; :attr:" +"`co_argcount` is the number of positional arguments (including arguments " +"with default values); :attr:`co_nlocals` is the number of local variables " +"used by the function (including arguments); :attr:`co_varnames` is a tuple " +"containing the names of the local variables (starting with the argument " +"names); :attr:`co_cellvars` is a tuple containing the names of local " +"variables that are referenced by nested functions; :attr:`co_freevars` is a " +"tuple containing the names of free variables; :attr:`co_code` is a string " +"representing the sequence of bytecode instructions; :attr:`co_consts` is a " +"tuple containing the literals used by the bytecode; :attr:`co_names` is a " +"tuple containing the names used by the bytecode; :attr:`co_filename` is the " +"filename from which the code was compiled; :attr:`co_firstlineno` is the " +"first line number of the function; :attr:`co_lnotab` is a string encoding " +"the mapping from bytecode offsets to line numbers (for details see the " +"source code of the interpreter); :attr:`co_stacksize` is the required stack " +"size (including local variables); :attr:`co_flags` is an integer encoding a " +"number of flags for the interpreter." +msgstr "" + +#: ../Doc/reference/datamodel.rst:904 +msgid "" +"The following flag bits are defined for :attr:`co_flags`: bit ``0x04`` is " +"set if the function uses the ``*arguments`` syntax to accept an arbitrary " +"number of positional arguments; bit ``0x08`` is set if the function uses the " +"``**keywords`` syntax to accept arbitrary keyword arguments; bit ``0x20`` is " +"set if the function is a generator." +msgstr "" + +#: ../Doc/reference/datamodel.rst:910 +msgid "" +"Future feature declarations (``from __future__ import division``) also use " +"bits in :attr:`co_flags` to indicate whether a code object was compiled with " +"a particular feature enabled: bit ``0x2000`` is set if the function was " +"compiled with future division enabled; bits ``0x10`` and ``0x1000`` were " +"used in earlier versions of Python." +msgstr "" + +#: ../Doc/reference/datamodel.rst:916 +msgid "Other bits in :attr:`co_flags` are reserved for internal use." +msgstr "" + +#: ../Doc/reference/datamodel.rst:920 +msgid "" +"If a code object represents a function, the first item in :attr:`co_consts` " +"is the documentation string of the function, or ``None`` if undefined." +msgstr "" + +#: ../Doc/reference/datamodel.rst:970 +msgid "Frame objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:928 +msgid "" +"Frame objects represent execution frames. They may occur in traceback " +"objects (see below)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:939 +msgid "" +"Special read-only attributes: :attr:`f_back` is to the previous stack frame " +"(towards the caller), or ``None`` if this is the bottom stack frame; :attr:" +"`f_code` is the code object being executed in this frame; :attr:`f_locals` " +"is the dictionary used to look up local variables; :attr:`f_globals` is used " +"for global variables; :attr:`f_builtins` is used for built-in (intrinsic) " +"names; :attr:`f_lasti` gives the precise instruction (this is an index into " +"the bytecode string of the code object)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:951 +msgid "" +"Special writable attributes: :attr:`f_trace`, if not ``None``, is a function " +"called at the start of each source code line (this is used by the " +"debugger); :attr:`f_lineno` is the current line number of the frame --- " +"writing to this from within a trace function jumps to the given line (only " +"for the bottom-most frame). A debugger can implement a Jump command (aka " +"Set Next Statement) by writing to f_lineno." +msgstr "" + +#: ../Doc/reference/datamodel.rst:958 +msgid "Frame objects support one method:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:962 +msgid "" +"This method clears all references to local variables held by the frame. " +"Also, if the frame belonged to a generator, the generator is finalized. " +"This helps break reference cycles involving frame objects (for example when " +"catching an exception and storing its traceback for later use)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:968 +msgid ":exc:`RuntimeError` is raised if the frame is currently executing." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1008 +msgid "Traceback objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:983 +msgid "" +"Traceback objects represent a stack trace of an exception. A traceback " +"object is created when an exception occurs. When the search for an " +"exception handler unwinds the execution stack, at each unwound level a " +"traceback object is inserted in front of the current traceback. When an " +"exception handler is entered, the stack trace is made available to the " +"program. (See section :ref:`try`.) It is accessible as the third item of the " +"tuple returned by ``sys.exc_info()``. When the program contains no suitable " +"handler, the stack trace is written (nicely formatted) to the standard error " +"stream; if the interpreter is interactive, it is also made available to the " +"user as ``sys.last_traceback``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1001 +msgid "" +"Special read-only attributes: :attr:`tb_next` is the next level in the stack " +"trace (towards the frame where the exception occurred), or ``None`` if there " +"is no next level; :attr:`tb_frame` points to the execution frame of the " +"current level; :attr:`tb_lineno` gives the line number where the exception " +"occurred; :attr:`tb_lasti` indicates the precise instruction. The line " +"number and last instruction in the traceback may differ from the line number " +"of its frame object if the exception occurred in a :keyword:`try` statement " +"with no matching except clause or with a finally clause." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1034 +msgid "Slice objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1013 +msgid "" +"Slice objects are used to represent slices for :meth:`__getitem__` methods. " +"They are also created by the built-in :func:`slice` function." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1021 +msgid "" +"Special read-only attributes: :attr:`~slice.start` is the lower bound; :attr:" +"`~slice.stop` is the upper bound; :attr:`~slice.step` is the step value; " +"each is ``None`` if omitted. These attributes can have any type." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1025 +msgid "Slice objects support one method:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1029 +msgid "" +"This method takes a single integer argument *length* and computes " +"information about the slice that the slice object would describe if applied " +"to a sequence of *length* items. It returns a tuple of three integers; " +"respectively these are the *start* and *stop* indices and the *step* or " +"stride length of the slice. Missing or out-of-bounds indices are handled in " +"a manner consistent with regular slices." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1044 +msgid "Static method objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1037 +msgid "" +"Static method objects provide a way of defeating the transformation of " +"function objects to method objects described above. A static method object " +"is a wrapper around any other object, usually a user-defined method object. " +"When a static method object is retrieved from a class or a class instance, " +"the object actually returned is the wrapped object, which is not subject to " +"any further transformation. Static method objects are not themselves " +"callable, although the objects they wrap usually are. Static method objects " +"are created by the built-in :func:`staticmethod` constructor." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1052 +msgid "Class method objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1047 +msgid "" +"A class method object, like a static method object, is a wrapper around " +"another object that alters the way in which that object is retrieved from " +"classes and class instances. The behaviour of class method objects upon such " +"retrieval is described above, under \"User-defined methods\". Class method " +"objects are created by the built-in :func:`classmethod` constructor." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1057 +msgid "Special method names" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1063 +msgid "" +"A class can implement certain operations that are invoked by special syntax " +"(such as arithmetic operations or subscripting and slicing) by defining " +"methods with special names. This is Python's approach to :dfn:`operator " +"overloading`, allowing classes to define their own behavior with respect to " +"language operators. For instance, if a class defines a method named :meth:" +"`__getitem__`, and ``x`` is an instance of this class, then ``x[i]`` is " +"roughly equivalent to ``type(x).__getitem__(x, i)``. Except where " +"mentioned, attempts to execute an operation raise an exception when no " +"appropriate method is defined (typically :exc:`AttributeError` or :exc:" +"`TypeError`)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1073 +msgid "" +"Setting a special method to ``None`` indicates that the corresponding " +"operation is not available. For example, if a class sets :meth:`__iter__` " +"to ``None``, the class is not iterable, so calling :func:`iter` on its " +"instances will raise a :exc:`TypeError` (without falling back to :meth:" +"`__getitem__`). [#]_" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1079 +msgid "" +"When implementing a class that emulates any built-in type, it is important " +"that the emulation only be implemented to the degree that it makes sense for " +"the object being modelled. For example, some sequences may work well with " +"retrieval of individual elements, but extracting a slice may not make " +"sense. (One example of this is the :class:`~xml.dom.NodeList` interface in " +"the W3C's Document Object Model.)" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1090 +msgid "Basic customization" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1096 +msgid "" +"Called to create a new instance of class *cls*. :meth:`__new__` is a static " +"method (special-cased so you need not declare it as such) that takes the " +"class of which an instance was requested as its first argument. The " +"remaining arguments are those passed to the object constructor expression " +"(the call to the class). The return value of :meth:`__new__` should be the " +"new object instance (usually an instance of *cls*)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1103 +msgid "" +"Typical implementations create a new instance of the class by invoking the " +"superclass's :meth:`__new__` method using ``super(currentclass, cls)." +"__new__(cls[, ...])`` with appropriate arguments and then modifying the " +"newly-created instance as necessary before returning it." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1108 +msgid "" +"If :meth:`__new__` returns an instance of *cls*, then the new instance's :" +"meth:`__init__` method will be invoked like ``__init__(self[, ...])``, where " +"*self* is the new instance and the remaining arguments are the same as were " +"passed to :meth:`__new__`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1113 +msgid "" +"If :meth:`__new__` does not return an instance of *cls*, then the new " +"instance's :meth:`__init__` method will not be invoked." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1116 +msgid "" +":meth:`__new__` is intended mainly to allow subclasses of immutable types " +"(like int, str, or tuple) to customize instance creation. It is also " +"commonly overridden in custom metaclasses in order to customize class " +"creation." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1125 +msgid "" +"Called after the instance has been created (by :meth:`__new__`), but before " +"it is returned to the caller. The arguments are those passed to the class " +"constructor expression. If a base class has an :meth:`__init__` method, the " +"derived class's :meth:`__init__` method, if any, must explicitly call it to " +"ensure proper initialization of the base class part of the instance; for " +"example: ``BaseClass.__init__(self, [args...])``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1132 +msgid "" +"Because :meth:`__new__` and :meth:`__init__` work together in constructing " +"objects (:meth:`__new__` to create it, and :meth:`__init__` to customize " +"it), no non-``None`` value may be returned by :meth:`__init__`; doing so " +"will cause a :exc:`TypeError` to be raised at runtime." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1144 +msgid "" +"Called when the instance is about to be destroyed. This is also called a " +"destructor. If a base class has a :meth:`__del__` method, the derived " +"class's :meth:`__del__` method, if any, must explicitly call it to ensure " +"proper deletion of the base class part of the instance. Note that it is " +"possible (though not recommended!) for the :meth:`__del__` method to " +"postpone destruction of the instance by creating a new reference to it. It " +"may then be called at a later time when this new reference is deleted. It " +"is not guaranteed that :meth:`__del__` methods are called for objects that " +"still exist when the interpreter exits." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1156 +msgid "" +"``del x`` doesn't directly call ``x.__del__()`` --- the former decrements " +"the reference count for ``x`` by one, and the latter is only called when " +"``x``'s reference count reaches zero. Some common situations that may " +"prevent the reference count of an object from going to zero include: " +"circular references between objects (e.g., a doubly-linked list or a tree " +"data structure with parent and child pointers); a reference to the object on " +"the stack frame of a function that caught an exception (the traceback stored " +"in ``sys.exc_info()[2]`` keeps the stack frame alive); or a reference to the " +"object on the stack frame that raised an unhandled exception in interactive " +"mode (the traceback stored in ``sys.last_traceback`` keeps the stack frame " +"alive). The first situation can only be remedied by explicitly breaking the " +"cycles; the second can be resolved by freeing the reference to the traceback " +"object when it is no longer useful, and the third can be resolved by storing " +"``None`` in ``sys.last_traceback``. Circular references which are garbage " +"are detected and cleaned up when the cyclic garbage collector is enabled " +"(it's on by default). Refer to the documentation for the :mod:`gc` module " +"for more information about this topic." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1178 +msgid "" +"Due to the precarious circumstances under which :meth:`__del__` methods are " +"invoked, exceptions that occur during their execution are ignored, and a " +"warning is printed to ``sys.stderr`` instead. Also, when :meth:`__del__` is " +"invoked in response to a module being deleted (e.g., when execution of the " +"program is done), other globals referenced by the :meth:`__del__` method may " +"already have been deleted or in the process of being torn down (e.g. the " +"import machinery shutting down). For this reason, :meth:`__del__` methods " +"should do the absolute minimum needed to maintain external invariants. " +"Starting with version 1.5, Python guarantees that globals whose name begins " +"with a single underscore are deleted from their module before other globals " +"are deleted; if no other references to such globals exist, this may help in " +"assuring that imported modules are still available at the time when the :" +"meth:`__del__` method is called." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1199 +msgid "" +"Called by the :func:`repr` built-in function to compute the \"official\" " +"string representation of an object. If at all possible, this should look " +"like a valid Python expression that could be used to recreate an object with " +"the same value (given an appropriate environment). If this is not possible, " +"a string of the form ``<...some useful description...>`` should be returned. " +"The return value must be a string object. If a class defines :meth:" +"`__repr__` but not :meth:`__str__`, then :meth:`__repr__` is also used when " +"an \"informal\" string representation of instances of that class is required." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1208 +msgid "" +"This is typically used for debugging, so it is important that the " +"representation is information-rich and unambiguous." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1219 +msgid "" +"Called by :func:`str(object) ` and the built-in functions :func:" +"`format` and :func:`print` to compute the \"informal\" or nicely printable " +"string representation of an object. The return value must be a :ref:`string " +"` object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1224 +msgid "" +"This method differs from :meth:`object.__repr__` in that there is no " +"expectation that :meth:`__str__` return a valid Python expression: a more " +"convenient or concise representation can be used." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1228 +msgid "" +"The default implementation defined by the built-in type :class:`object` " +"calls :meth:`object.__repr__`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1238 +msgid "" +"Called by :func:`bytes` to compute a byte-string representation of an " +"object. This should return a ``bytes`` object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1249 +msgid "" +"Called by the :func:`format` built-in function, and by extension, evaluation " +"of :ref:`formatted string literals ` and the :meth:`str.format` " +"method, to produce a \"formatted\" string representation of an object. The " +"``format_spec`` argument is a string that contains a description of the " +"formatting options desired. The interpretation of the ``format_spec`` " +"argument is up to the type implementing :meth:`__format__`, however most " +"classes will either delegate formatting to one of the built-in types, or use " +"a similar formatting option syntax." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1259 +msgid "" +"See :ref:`formatspec` for a description of the standard formatting syntax." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1261 +msgid "The return value must be a string object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1263 +msgid "" +"The __format__ method of ``object`` itself raises a :exc:`TypeError` if " +"passed any non-empty string." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1279 +msgid "" +"These are the so-called \"rich comparison\" methods. The correspondence " +"between operator symbols and method names is as follows: ``xy`` calls ``x.__gt__(y)``, and ``x>=y`` " +"calls ``x.__ge__(y)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1285 +msgid "" +"A rich comparison method may return the singleton ``NotImplemented`` if it " +"does not implement the operation for a given pair of arguments. By " +"convention, ``False`` and ``True`` are returned for a successful comparison. " +"However, these methods can return any value, so if the comparison operator " +"is used in a Boolean context (e.g., in the condition of an ``if`` " +"statement), Python will call :func:`bool` on the value to determine if the " +"result is true or false." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1292 +msgid "" +"By default, :meth:`__ne__` delegates to :meth:`__eq__` and inverts the " +"result unless it is ``NotImplemented``. There are no other implied " +"relationships among the comparison operators, for example, the truth of " +"``(x.__hash__``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1363 +msgid "" +"If a class that does not override :meth:`__eq__` wishes to suppress hash " +"support, it should include ``__hash__ = None`` in the class definition. A " +"class which defines its own :meth:`__hash__` that explicitly raises a :exc:" +"`TypeError` would be incorrectly identified as hashable by an " +"``isinstance(obj, collections.Hashable)`` call." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1372 +msgid "" +"By default, the :meth:`__hash__` values of str, bytes and datetime objects " +"are \"salted\" with an unpredictable random value. Although they remain " +"constant within an individual Python process, they are not predictable " +"between repeated invocations of Python." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1377 +msgid "" +"This is intended to provide protection against a denial-of-service caused by " +"carefully-chosen inputs that exploit the worst case performance of a dict " +"insertion, O(n^2) complexity. See http://www.ocert.org/advisories/" +"ocert-2011-003.html for details." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1382 +msgid "" +"Changing hash values affects the iteration order of dicts, sets and other " +"mappings. Python has never made guarantees about this ordering (and it " +"typically varies between 32-bit and 64-bit builds)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1386 +msgid "See also :envvar:`PYTHONHASHSEED`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1388 +msgid "Hash randomization is enabled by default." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1396 +msgid "" +"Called to implement truth value testing and the built-in operation " +"``bool()``; should return ``False`` or ``True``. When this method is not " +"defined, :meth:`__len__` is called, if it is defined, and the object is " +"considered true if its result is nonzero. If a class defines neither :meth:" +"`__len__` nor :meth:`__bool__`, all its instances are considered true." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1407 +msgid "Customizing attribute access" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1409 +msgid "" +"The following methods can be defined to customize the meaning of attribute " +"access (use of, assignment to, or deletion of ``x.name``) for class " +"instances." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1417 +msgid "" +"Called when an attribute lookup has not found the attribute in the usual " +"places (i.e. it is not an instance attribute nor is it found in the class " +"tree for ``self``). ``name`` is the attribute name. This method should " +"return the (computed) attribute value or raise an :exc:`AttributeError` " +"exception." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1422 +msgid "" +"Note that if the attribute is found through the normal mechanism, :meth:" +"`__getattr__` is not called. (This is an intentional asymmetry between :" +"meth:`__getattr__` and :meth:`__setattr__`.) This is done both for " +"efficiency reasons and because otherwise :meth:`__getattr__` would have no " +"way to access other attributes of the instance. Note that at least for " +"instance variables, you can fake total control by not inserting any values " +"in the instance attribute dictionary (but instead inserting them in another " +"object). See the :meth:`__getattribute__` method below for a way to " +"actually get total control over attribute access." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1435 +msgid "" +"Called unconditionally to implement attribute accesses for instances of the " +"class. If the class also defines :meth:`__getattr__`, the latter will not be " +"called unless :meth:`__getattribute__` either calls it explicitly or raises " +"an :exc:`AttributeError`. This method should return the (computed) attribute " +"value or raise an :exc:`AttributeError` exception. In order to avoid " +"infinite recursion in this method, its implementation should always call the " +"base class method with the same name to access any attributes it needs, for " +"example, ``object.__getattribute__(self, name)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1446 +msgid "" +"This method may still be bypassed when looking up special methods as the " +"result of implicit invocation via language syntax or built-in functions. " +"See :ref:`special-lookup`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1453 +msgid "" +"Called when an attribute assignment is attempted. This is called instead of " +"the normal mechanism (i.e. store the value in the instance dictionary). " +"*name* is the attribute name, *value* is the value to be assigned to it." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1457 +msgid "" +"If :meth:`__setattr__` wants to assign to an instance attribute, it should " +"call the base class method with the same name, for example, ``object." +"__setattr__(self, name, value)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1464 +msgid "" +"Like :meth:`__setattr__` but for attribute deletion instead of assignment. " +"This should only be implemented if ``del obj.name`` is meaningful for the " +"object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1470 +msgid "" +"Called when :func:`dir` is called on the object. A sequence must be " +"returned. :func:`dir` converts the returned sequence to a list and sorts it." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1477 +msgid "Implementing Descriptors" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1479 +msgid "" +"The following methods only apply when an instance of the class containing " +"the method (a so-called *descriptor* class) appears in an *owner* class (the " +"descriptor must be in either the owner's class dictionary or in the class " +"dictionary for one of its parents). In the examples below, \"the attribute" +"\" refers to the attribute whose name is the key of the property in the " +"owner class' :attr:`~object.__dict__`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1489 +msgid "" +"Called to get the attribute of the owner class (class attribute access) or " +"of an instance of that class (instance attribute access). *owner* is always " +"the owner class, while *instance* is the instance that the attribute was " +"accessed through, or ``None`` when the attribute is accessed through the " +"*owner*. This method should return the (computed) attribute value or raise " +"an :exc:`AttributeError` exception." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1499 +msgid "" +"Called to set the attribute on an instance *instance* of the owner class to " +"a new value, *value*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1505 +msgid "" +"Called to delete the attribute on an instance *instance* of the owner class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1510 +msgid "" +"Called at the time the owning class *owner* is created. The descriptor has " +"been assigned to *name*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1516 +msgid "" +"The attribute :attr:`__objclass__` is interpreted by the :mod:`inspect` " +"module as specifying the class where this object was defined (setting this " +"appropriately can assist in runtime introspection of dynamic class " +"attributes). For callables, it may indicate that an instance of the given " +"type (or a subclass) is expected or required as the first positional " +"argument (for example, CPython sets this attribute for unbound methods that " +"are implemented in C)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1527 +msgid "Invoking Descriptors" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1529 +msgid "" +"In general, a descriptor is an object attribute with \"binding behavior\", " +"one whose attribute access has been overridden by methods in the descriptor " +"protocol: :meth:`__get__`, :meth:`__set__`, and :meth:`__delete__`. If any " +"of those methods are defined for an object, it is said to be a descriptor." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1534 +msgid "" +"The default behavior for attribute access is to get, set, or delete the " +"attribute from an object's dictionary. For instance, ``a.x`` has a lookup " +"chain starting with ``a.__dict__['x']``, then ``type(a).__dict__['x']``, and " +"continuing through the base classes of ``type(a)`` excluding metaclasses." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1539 +msgid "" +"However, if the looked-up value is an object defining one of the descriptor " +"methods, then Python may override the default behavior and invoke the " +"descriptor method instead. Where this occurs in the precedence chain " +"depends on which descriptor methods were defined and how they were called." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1544 +msgid "" +"The starting point for descriptor invocation is a binding, ``a.x``. How the " +"arguments are assembled depends on ``a``:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1549 +msgid "Direct Call" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1548 +msgid "" +"The simplest and least common call is when user code directly invokes a " +"descriptor method: ``x.__get__(a)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1553 +msgid "Instance Binding" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1552 +msgid "" +"If binding to an object instance, ``a.x`` is transformed into the call: " +"``type(a).__dict__['x'].__get__(a, type(a))``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1557 +msgid "Class Binding" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1556 +msgid "" +"If binding to a class, ``A.x`` is transformed into the call: ``A." +"__dict__['x'].__get__(None, A)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1563 +msgid "Super Binding" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1560 +msgid "" +"If ``a`` is an instance of :class:`super`, then the binding ``super(B, obj)." +"m()`` searches ``obj.__class__.__mro__`` for the base class ``A`` " +"immediately preceding ``B`` and then invokes the descriptor with the call: " +"``A.__dict__['m'].__get__(obj, obj.__class__)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1565 +msgid "" +"For instance bindings, the precedence of descriptor invocation depends on " +"the which descriptor methods are defined. A descriptor can define any " +"combination of :meth:`__get__`, :meth:`__set__` and :meth:`__delete__`. If " +"it does not define :meth:`__get__`, then accessing the attribute will return " +"the descriptor object itself unless there is a value in the object's " +"instance dictionary. If the descriptor defines :meth:`__set__` and/or :meth:" +"`__delete__`, it is a data descriptor; if it defines neither, it is a non-" +"data descriptor. Normally, data descriptors define both :meth:`__get__` " +"and :meth:`__set__`, while non-data descriptors have just the :meth:" +"`__get__` method. Data descriptors with :meth:`__set__` and :meth:`__get__` " +"defined always override a redefinition in an instance dictionary. In " +"contrast, non-data descriptors can be overridden by instances." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1578 +msgid "" +"Python methods (including :func:`staticmethod` and :func:`classmethod`) are " +"implemented as non-data descriptors. Accordingly, instances can redefine " +"and override methods. This allows individual instances to acquire behaviors " +"that differ from other instances of the same class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1583 +msgid "" +"The :func:`property` function is implemented as a data descriptor. " +"Accordingly, instances cannot override the behavior of a property." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1590 +msgid "__slots__" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1592 +msgid "" +"By default, instances of classes have a dictionary for attribute storage. " +"This wastes space for objects having very few instance variables. The space " +"consumption can become acute when creating large numbers of instances." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1596 +msgid "" +"The default can be overridden by defining *__slots__* in a class definition. " +"The *__slots__* declaration takes a sequence of instance variables and " +"reserves just enough space in each instance to hold a value for each " +"variable. Space is saved because *__dict__* is not created for each " +"instance." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1604 +msgid "" +"This class variable can be assigned a string, iterable, or sequence of " +"strings with variable names used by instances. *__slots__* reserves space " +"for the declared variables and prevents the automatic creation of *__dict__* " +"and *__weakref__* for each instance." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1611 +msgid "Notes on using *__slots__*" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1613 +msgid "" +"When inheriting from a class without *__slots__*, the *__dict__* attribute " +"of that class will always be accessible, so a *__slots__* definition in the " +"subclass is meaningless." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1617 +msgid "" +"Without a *__dict__* variable, instances cannot be assigned new variables " +"not listed in the *__slots__* definition. Attempts to assign to an unlisted " +"variable name raises :exc:`AttributeError`. If dynamic assignment of new " +"variables is desired, then add ``'__dict__'`` to the sequence of strings in " +"the *__slots__* declaration." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1623 +msgid "" +"Without a *__weakref__* variable for each instance, classes defining " +"*__slots__* do not support weak references to its instances. If weak " +"reference support is needed, then add ``'__weakref__'`` to the sequence of " +"strings in the *__slots__* declaration." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1628 +msgid "" +"*__slots__* are implemented at the class level by creating descriptors (:ref:" +"`descriptors`) for each variable name. As a result, class attributes cannot " +"be used to set default values for instance variables defined by *__slots__*; " +"otherwise, the class attribute would overwrite the descriptor assignment." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1634 +msgid "" +"The action of a *__slots__* declaration is limited to the class where it is " +"defined. As a result, subclasses will have a *__dict__* unless they also " +"define *__slots__* (which must only contain names of any *additional* slots)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1638 +msgid "" +"If a class defines a slot also defined in a base class, the instance " +"variable defined by the base class slot is inaccessible (except by " +"retrieving its descriptor directly from the base class). This renders the " +"meaning of the program undefined. In the future, a check may be added to " +"prevent this." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1643 +msgid "" +"Nonempty *__slots__* does not work for classes derived from \"variable-length" +"\" built-in types such as :class:`int`, :class:`bytes` and :class:`tuple`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1646 +msgid "" +"Any non-string iterable may be assigned to *__slots__*. Mappings may also be " +"used; however, in the future, special meaning may be assigned to the values " +"corresponding to each key." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1650 +msgid "" +"*__class__* assignment works only if both classes have the same *__slots__*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1656 +msgid "Customizing class creation" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1658 +msgid "" +"Whenever a class inherits from another class, *__init_subclass__* is called " +"on that class. This way, it is possible to write classes which change the " +"behavior of subclasses. This is closely related to class decorators, but " +"where class decorators only affect the specific class they're applied to, " +"``__init_subclass__`` solely applies to future subclasses of the class " +"defining the method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1667 +msgid "" +"This method is called whenever the containing class is subclassed. *cls* is " +"then the new subclass. If defined as a normal instance method, this method " +"is implicitly converted to a class method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1671 +msgid "" +"Keyword arguments which are given to a new class are passed to the parent's " +"class ``__init_subclass__``. For compatibility with other classes using " +"``__init_subclass__``, one should take out the needed keyword arguments and " +"pass the others over to the base class, as in::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1685 +msgid "" +"The default implementation ``object.__init_subclass__`` does nothing, but " +"raises an error if it is called with any arguments." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1690 +msgid "" +"The metaclass hint ``metaclass`` is consumed by the rest of the type " +"machinery, and is never passed to ``__init_subclass__`` implementations. The " +"actual metaclass (rather than the explicit hint) can be accessed as " +"``type(cls)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1701 +msgid "Metaclasses" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1703 +msgid "" +"By default, classes are constructed using :func:`type`. The class body is " +"executed in a new namespace and the class name is bound locally to the " +"result of ``type(name, bases, namespace)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1707 +msgid "" +"The class creation process can be customized by passing the ``metaclass`` " +"keyword argument in the class definition line, or by inheriting from an " +"existing class that included such an argument. In the following example, " +"both ``MyClass`` and ``MySubclass`` are instances of ``Meta``::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1721 +msgid "" +"Any other keyword arguments that are specified in the class definition are " +"passed through to all metaclass operations described below." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1724 +msgid "When a class definition is executed, the following steps occur:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1726 +msgid "the appropriate metaclass is determined" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1727 +msgid "the class namespace is prepared" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1728 +msgid "the class body is executed" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1729 +msgid "the class object is created" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1732 +msgid "Determining the appropriate metaclass" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1734 +msgid "" +"The appropriate metaclass for a class definition is determined as follows:" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1736 +msgid "" +"if no bases and no explicit metaclass are given, then :func:`type` is used" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1737 +msgid "" +"if an explicit metaclass is given and it is *not* an instance of :func:" +"`type`, then it is used directly as the metaclass" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1739 +msgid "" +"if an instance of :func:`type` is given as the explicit metaclass, or bases " +"are defined, then the most derived metaclass is used" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1742 +msgid "" +"The most derived metaclass is selected from the explicitly specified " +"metaclass (if any) and the metaclasses (i.e. ``type(cls)``) of all specified " +"base classes. The most derived metaclass is one which is a subtype of *all* " +"of these candidate metaclasses. If none of the candidate metaclasses meets " +"that criterion, then the class definition will fail with ``TypeError``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1752 +msgid "Preparing the class namespace" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1754 +msgid "" +"Once the appropriate metaclass has been identified, then the class namespace " +"is prepared. If the metaclass has a ``__prepare__`` attribute, it is called " +"as ``namespace = metaclass.__prepare__(name, bases, **kwds)`` (where the " +"additional keyword arguments, if any, come from the class definition)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1759 +msgid "" +"If the metaclass has no ``__prepare__`` attribute, then the class namespace " +"is initialised as an empty ordered mapping." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1764 +msgid ":pep:`3115` - Metaclasses in Python 3000" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1765 +msgid "Introduced the ``__prepare__`` namespace hook" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1769 +msgid "Executing the class body" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1771 +msgid "" +"The class body is executed (approximately) as ``exec(body, globals(), " +"namespace)``. The key difference from a normal call to :func:`exec` is that " +"lexical scoping allows the class body (including any methods) to reference " +"names from the current and outer scopes when the class definition occurs " +"inside a function." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1777 +msgid "" +"However, even when the class definition occurs inside the function, methods " +"defined inside the class still cannot see names defined at the class scope. " +"Class variables must be accessed through the first parameter of instance or " +"class methods, and cannot be accessed at all from static methods." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1784 +msgid "Creating the class object" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1786 +msgid "" +"Once the class namespace has been populated by executing the class body, the " +"class object is created by calling ``metaclass(name, bases, namespace, " +"**kwds)`` (the additional keywords passed here are the same as those passed " +"to ``__prepare__``)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1791 +msgid "" +"This class object is the one that will be referenced by the zero-argument " +"form of :func:`super`. ``__class__`` is an implicit closure reference " +"created by the compiler if any methods in a class body refer to either " +"``__class__`` or ``super``. This allows the zero argument form of :func:" +"`super` to correctly identify the class being defined based on lexical " +"scoping, while the class or instance that was used to make the current call " +"is identified based on the first argument passed to the method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1799 +msgid "" +"After the class object is created, it is passed to the class decorators " +"included in the class definition (if any) and the resulting object is bound " +"in the local namespace as the defined class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1803 +msgid "" +"When a new class is created by ``type.__new__``, the object provided as the " +"namespace parameter is copied to a new ordered mapping and the original " +"object is discarded. The new copy is wrapped in a read-only proxy, which " +"becomes the :attr:`~object.__dict__` attribute of the class object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1810 +msgid ":pep:`3135` - New super" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1811 +msgid "Describes the implicit ``__class__`` closure reference" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1815 +msgid "Metaclass example" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1817 +msgid "" +"The potential uses for metaclasses are boundless. Some ideas that have been " +"explored include logging, interface checking, automatic delegation, " +"automatic property creation, proxies, frameworks, and automatic resource " +"locking/synchronization." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1822 +msgid "" +"Here is an example of a metaclass that uses an :class:`collections." +"OrderedDict` to remember the order that class variables are defined::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1845 +msgid "" +"When the class definition for *A* gets executed, the process begins with " +"calling the metaclass's :meth:`__prepare__` method which returns an empty :" +"class:`collections.OrderedDict`. That mapping records the methods and " +"attributes of *A* as they are defined within the body of the class " +"statement. Once those definitions are executed, the ordered dictionary is " +"fully populated and the metaclass's :meth:`__new__` method gets invoked. " +"That method builds the new type and it saves the ordered dictionary keys in " +"an attribute called ``members``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1856 +msgid "Customizing instance and subclass checks" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1858 +msgid "" +"The following methods are used to override the default behavior of the :func:" +"`isinstance` and :func:`issubclass` built-in functions." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1861 +msgid "" +"In particular, the metaclass :class:`abc.ABCMeta` implements these methods " +"in order to allow the addition of Abstract Base Classes (ABCs) as \"virtual " +"base classes\" to any class or type (including built-in types), including " +"other ABCs." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1868 +msgid "" +"Return true if *instance* should be considered a (direct or indirect) " +"instance of *class*. If defined, called to implement ``isinstance(instance, " +"class)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1875 +msgid "" +"Return true if *subclass* should be considered a (direct or indirect) " +"subclass of *class*. If defined, called to implement ``issubclass(subclass, " +"class)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1880 +msgid "" +"Note that these methods are looked up on the type (metaclass) of a class. " +"They cannot be defined as class methods in the actual class. This is " +"consistent with the lookup of special methods that are called on instances, " +"only in this case the instance is itself a class." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1891 +msgid ":pep:`3119` - Introducing Abstract Base Classes" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1888 +msgid "" +"Includes the specification for customizing :func:`isinstance` and :func:" +"`issubclass` behavior through :meth:`~class.__instancecheck__` and :meth:" +"`~class.__subclasscheck__`, with motivation for this functionality in the " +"context of adding Abstract Base Classes (see the :mod:`abc` module) to the " +"language." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1898 +msgid "Emulating callable objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1905 +msgid "" +"Called when the instance is \"called\" as a function; if this method is " +"defined, ``x(arg1, arg2, ...)`` is a shorthand for ``x.__call__(arg1, " +"arg2, ...)``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1912 +msgid "Emulating container types" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1914 +msgid "" +"The following methods can be defined to implement container objects. " +"Containers usually are sequences (such as lists or tuples) or mappings (like " +"dictionaries), but can represent other containers as well. The first set of " +"methods is used either to emulate a sequence or to emulate a mapping; the " +"difference is that for a sequence, the allowable keys should be the integers " +"*k* for which ``0 <= k < N`` where *N* is the length of the sequence, or " +"slice objects, which define a range of items. It is also recommended that " +"mappings provide the methods :meth:`keys`, :meth:`values`, :meth:`items`, :" +"meth:`get`, :meth:`clear`, :meth:`setdefault`, :meth:`pop`, :meth:" +"`popitem`, :meth:`!copy`, and :meth:`update` behaving similar to those for " +"Python's standard dictionary objects. The :mod:`collections` module " +"provides a :class:`~collections.abc.MutableMapping` abstract base class to " +"help create those methods from a base set of :meth:`__getitem__`, :meth:" +"`__setitem__`, :meth:`__delitem__`, and :meth:`keys`. Mutable sequences " +"should provide methods :meth:`append`, :meth:`count`, :meth:`index`, :meth:" +"`extend`, :meth:`insert`, :meth:`pop`, :meth:`remove`, :meth:`reverse` and :" +"meth:`sort`, like Python standard list objects. Finally, sequence types " +"should implement addition (meaning concatenation) and multiplication " +"(meaning repetition) by defining the methods :meth:`__add__`, :meth:" +"`__radd__`, :meth:`__iadd__`, :meth:`__mul__`, :meth:`__rmul__` and :meth:" +"`__imul__` described below; they should not define other numerical " +"operators. It is recommended that both mappings and sequences implement " +"the :meth:`__contains__` method to allow efficient use of the ``in`` " +"operator; for mappings, ``in`` should search the mapping's keys; for " +"sequences, it should search through the values. It is further recommended " +"that both mappings and sequences implement the :meth:`__iter__` method to " +"allow efficient iteration through the container; for mappings, :meth:" +"`__iter__` should be the same as :meth:`keys`; for sequences, it should " +"iterate through the values." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1949 +msgid "" +"Called to implement the built-in function :func:`len`. Should return the " +"length of the object, an integer ``>=`` 0. Also, an object that doesn't " +"define a :meth:`__bool__` method and whose :meth:`__len__` method returns " +"zero is considered to be false in a Boolean context." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1957 +msgid "" +"Called to implement :func:`operator.length_hint`. Should return an estimated " +"length for the object (which may be greater or less than the actual length). " +"The length must be an integer ``>=`` 0. This method is purely an " +"optimization and is never required for correctness." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1966 +msgid "" +"Slicing is done exclusively with the following three methods. A call like ::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1970 +msgid "is translated to ::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:1974 +msgid "and so forth. Missing slice items are always filled in with ``None``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1981 +msgid "" +"Called to implement evaluation of ``self[key]``. For sequence types, the " +"accepted keys should be integers and slice objects. Note that the special " +"interpretation of negative indexes (if the class wishes to emulate a " +"sequence type) is up to the :meth:`__getitem__` method. If *key* is of an " +"inappropriate type, :exc:`TypeError` may be raised; if of a value outside " +"the set of indexes for the sequence (after any special interpretation of " +"negative values), :exc:`IndexError` should be raised. For mapping types, if " +"*key* is missing (not in the container), :exc:`KeyError` should be raised." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1992 +msgid "" +":keyword:`for` loops expect that an :exc:`IndexError` will be raised for " +"illegal indexes to allow proper detection of the end of the sequence." +msgstr "" + +#: ../Doc/reference/datamodel.rst:1998 +msgid "" +"Called by :class:`dict`\\ .\\ :meth:`__getitem__` to implement ``self[key]`` " +"for dict subclasses when key is not in the dictionary." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2004 +msgid "" +"Called to implement assignment to ``self[key]``. Same note as for :meth:" +"`__getitem__`. This should only be implemented for mappings if the objects " +"support changes to the values for keys, or if new keys can be added, or for " +"sequences if elements can be replaced. The same exceptions should be raised " +"for improper *key* values as for the :meth:`__getitem__` method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2013 +msgid "" +"Called to implement deletion of ``self[key]``. Same note as for :meth:" +"`__getitem__`. This should only be implemented for mappings if the objects " +"support removal of keys, or for sequences if elements can be removed from " +"the sequence. The same exceptions should be raised for improper *key* " +"values as for the :meth:`__getitem__` method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2022 +msgid "" +"This method is called when an iterator is required for a container. This " +"method should return a new iterator object that can iterate over all the " +"objects in the container. For mappings, it should iterate over the keys of " +"the container." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2026 +msgid "" +"Iterator objects also need to implement this method; they are required to " +"return themselves. For more information on iterator objects, see :ref:" +"`typeiter`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2032 +msgid "" +"Called (if present) by the :func:`reversed` built-in to implement reverse " +"iteration. It should return a new iterator object that iterates over all " +"the objects in the container in reverse order." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2036 +msgid "" +"If the :meth:`__reversed__` method is not provided, the :func:`reversed` " +"built-in will fall back to using the sequence protocol (:meth:`__len__` and :" +"meth:`__getitem__`). Objects that support the sequence protocol should only " +"provide :meth:`__reversed__` if they can provide an implementation that is " +"more efficient than the one provided by :func:`reversed`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2043 +msgid "" +"The membership test operators (:keyword:`in` and :keyword:`not in`) are " +"normally implemented as an iteration through a sequence. However, container " +"objects can supply the following special method with a more efficient " +"implementation, which also does not require the object be a sequence." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2050 +msgid "" +"Called to implement membership test operators. Should return true if *item* " +"is in *self*, false otherwise. For mapping objects, this should consider " +"the keys of the mapping rather than the values or the key-item pairs." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2054 +msgid "" +"For objects that don't define :meth:`__contains__`, the membership test " +"first tries iteration via :meth:`__iter__`, then the old sequence iteration " +"protocol via :meth:`__getitem__`, see :ref:`this section in the language " +"reference `." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2063 +msgid "Emulating numeric types" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2065 +msgid "" +"The following methods can be defined to emulate numeric objects. Methods " +"corresponding to operations that are not supported by the particular kind of " +"number implemented (e.g., bitwise operations for non-integral numbers) " +"should be left undefined." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2091 +msgid "" +"These methods are called to implement the binary arithmetic operations (``" +"+``, ``-``, ``*``, ``@``, ``/``, ``//``, ``%``, :func:`divmod`, :func:`pow`, " +"``**``, ``<<``, ``>>``, ``&``, ``^``, ``|``). For instance, to evaluate the " +"expression ``x + y``, where *x* is an instance of a class that has an :meth:" +"`__add__` method, ``x.__add__(y)`` is called. The :meth:`__divmod__` method " +"should be the equivalent to using :meth:`__floordiv__` and :meth:`__mod__`; " +"it should not be related to :meth:`__truediv__`. Note that :meth:`__pow__` " +"should be defined to accept an optional third argument if the ternary " +"version of the built-in :func:`pow` function is to be supported." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2102 +msgid "" +"If one of those methods does not support the operation with the supplied " +"arguments, it should return ``NotImplemented``." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2125 +msgid "" +"These methods are called to implement the binary arithmetic operations (``" +"+``, ``-``, ``*``, ``@``, ``/``, ``//``, ``%``, :func:`divmod`, :func:`pow`, " +"``**``, ``<<``, ``>>``, ``&``, ``^``, ``|``) with reflected (swapped) " +"operands. These functions are only called if the left operand does not " +"support the corresponding operation [#]_ and the operands are of different " +"types. [#]_ For instance, to evaluate the expression ``x - y``, where *y* is " +"an instance of a class that has an :meth:`__rsub__` method, ``y." +"__rsub__(x)`` is called if ``x.__sub__(y)`` returns *NotImplemented*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2136 +msgid "" +"Note that ternary :func:`pow` will not try calling :meth:`__rpow__` (the " +"coercion rules would become too complicated)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2141 +msgid "" +"If the right operand's type is a subclass of the left operand's type and " +"that subclass provides the reflected method for the operation, this method " +"will be called before the left operand's non-reflected method. This " +"behavior allows subclasses to override their ancestors' operations." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2161 +msgid "" +"These methods are called to implement the augmented arithmetic assignments " +"(``+=``, ``-=``, ``*=``, ``@=``, ``/=``, ``//=``, ``%=``, ``**=``, ``<<=``, " +"``>>=``, ``&=``, ``^=``, ``|=``). These methods should attempt to do the " +"operation in-place (modifying *self*) and return the result (which could be, " +"but does not have to be, *self*). If a specific method is not defined, the " +"augmented assignment falls back to the normal methods. For instance, if *x* " +"is an instance of a class with an :meth:`__iadd__` method, ``x += y`` is " +"equivalent to ``x = x.__iadd__(y)`` . Otherwise, ``x.__add__(y)`` and ``y." +"__radd__(x)`` are considered, as with the evaluation of ``x + y``. In " +"certain situations, augmented assignment can result in unexpected errors " +"(see :ref:`faq-augmented-assignment-tuple-error`), but this behavior is in " +"fact part of the data model." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2182 +msgid "" +"Called to implement the unary arithmetic operations (``-``, ``+``, :func:" +"`abs` and ``~``)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2197 +msgid "" +"Called to implement the built-in functions :func:`complex`, :func:`int`, :" +"func:`float` and :func:`round`. Should return a value of the appropriate " +"type." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2204 +msgid "" +"Called to implement :func:`operator.index`, and whenever Python needs to " +"losslessly convert the numeric object to an integer object (such as in " +"slicing, or in the built-in :func:`bin`, :func:`hex` and :func:`oct` " +"functions). Presence of this method indicates that the numeric object is an " +"integer type. Must return an integer." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2212 +msgid "" +"In order to have a coherent integer type class, when :meth:`__index__` is " +"defined :meth:`__int__` should also be defined, and both should return the " +"same value." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2220 +msgid "With Statement Context Managers" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2222 +msgid "" +"A :dfn:`context manager` is an object that defines the runtime context to be " +"established when executing a :keyword:`with` statement. The context manager " +"handles the entry into, and the exit from, the desired runtime context for " +"the execution of the block of code. Context managers are normally invoked " +"using the :keyword:`with` statement (described in section :ref:`with`), but " +"can also be used by directly invoking their methods." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2233 +msgid "" +"Typical uses of context managers include saving and restoring various kinds " +"of global state, locking and unlocking resources, closing opened files, etc." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2236 +msgid "" +"For more information on context managers, see :ref:`typecontextmanager`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2241 +msgid "" +"Enter the runtime context related to this object. The :keyword:`with` " +"statement will bind this method's return value to the target(s) specified in " +"the :keyword:`as` clause of the statement, if any." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2248 +msgid "" +"Exit the runtime context related to this object. The parameters describe the " +"exception that caused the context to be exited. If the context was exited " +"without an exception, all three arguments will be :const:`None`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2252 +msgid "" +"If an exception is supplied, and the method wishes to suppress the exception " +"(i.e., prevent it from being propagated), it should return a true value. " +"Otherwise, the exception will be processed normally upon exit from this " +"method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2256 +msgid "" +"Note that :meth:`__exit__` methods should not reraise the passed-in " +"exception; this is the caller's responsibility." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2270 +msgid "Special method lookup" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2272 +msgid "" +"For custom classes, implicit invocations of special methods are only " +"guaranteed to work correctly if defined on an object's type, not in the " +"object's instance dictionary. That behaviour is the reason why the " +"following code raises an exception::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2287 +msgid "" +"The rationale behind this behaviour lies with a number of special methods " +"such as :meth:`__hash__` and :meth:`__repr__` that are implemented by all " +"objects, including type objects. If the implicit lookup of these methods " +"used the conventional lookup process, they would fail when invoked on the " +"type object itself::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2300 +msgid "" +"Incorrectly attempting to invoke an unbound method of a class in this way is " +"sometimes referred to as 'metaclass confusion', and is avoided by bypassing " +"the instance when looking up special methods::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2309 +msgid "" +"In addition to bypassing any instance attributes in the interest of " +"correctness, implicit special method lookup generally also bypasses the :" +"meth:`__getattribute__` method even of the object's metaclass::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2335 +msgid "" +"Bypassing the :meth:`__getattribute__` machinery in this fashion provides " +"significant scope for speed optimisations within the interpreter, at the " +"cost of some flexibility in the handling of special methods (the special " +"method *must* be set on the class object itself in order to be consistently " +"invoked by the interpreter)." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2350 +msgid "Awaitable Objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2352 +msgid "" +"An :term:`awaitable` object generally implements an :meth:`__await__` " +"method. :term:`Coroutine` objects returned from :keyword:`async def` " +"functions are awaitable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2358 +msgid "" +"The :term:`generator iterator` objects returned from generators decorated " +"with :func:`types.coroutine` or :func:`asyncio.coroutine` are also " +"awaitable, but they do not implement :meth:`__await__`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2364 +msgid "" +"Must return an :term:`iterator`. Should be used to implement :term:" +"`awaitable` objects. For instance, :class:`asyncio.Future` implements this " +"method to be compatible with the :keyword:`await` expression." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2370 +msgid ":pep:`492` for additional information about awaitable objects." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2376 +msgid "Coroutine Objects" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2378 +msgid "" +":term:`Coroutine` objects are :term:`awaitable` objects. A coroutine's " +"execution can be controlled by calling :meth:`__await__` and iterating over " +"the result. When the coroutine has finished executing and returns, the " +"iterator raises :exc:`StopIteration`, and the exception's :attr:" +"`~StopIteration.value` attribute holds the return value. If the coroutine " +"raises an exception, it is propagated by the iterator. Coroutines should " +"not directly raise unhandled :exc:`StopIteration` exceptions." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2386 +msgid "" +"Coroutines also have the methods listed below, which are analogous to those " +"of generators (see :ref:`generator-methods`). However, unlike generators, " +"coroutines do not directly support iteration." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2390 +msgid "It is a :exc:`RuntimeError` to await on a coroutine more than once." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2396 +msgid "" +"Starts or resumes execution of the coroutine. If *value* is ``None``, this " +"is equivalent to advancing the iterator returned by :meth:`__await__`. If " +"*value* is not ``None``, this method delegates to the :meth:`~generator." +"send` method of the iterator that caused the coroutine to suspend. The " +"result (return value, :exc:`StopIteration`, or other exception) is the same " +"as when iterating over the :meth:`__await__` return value, described above." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2406 +msgid "" +"Raises the specified exception in the coroutine. This method delegates to " +"the :meth:`~generator.throw` method of the iterator that caused the " +"coroutine to suspend, if it has such a method. Otherwise, the exception is " +"raised at the suspension point. The result (return value, :exc:" +"`StopIteration`, or other exception) is the same as when iterating over the :" +"meth:`__await__` return value, described above. If the exception is not " +"caught in the coroutine, it propagates back to the caller." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2417 +msgid "" +"Causes the coroutine to clean itself up and exit. If the coroutine is " +"suspended, this method first delegates to the :meth:`~generator.close` " +"method of the iterator that caused the coroutine to suspend, if it has such " +"a method. Then it raises :exc:`GeneratorExit` at the suspension point, " +"causing the coroutine to immediately clean itself up. Finally, the coroutine " +"is marked as having finished executing, even if it was never started." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2425 +msgid "" +"Coroutine objects are automatically closed using the above process when they " +"are about to be destroyed." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2431 +msgid "Asynchronous Iterators" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2433 +msgid "" +"An *asynchronous iterable* is able to call asynchronous code in its " +"``__aiter__`` implementation, and an *asynchronous iterator* can call " +"asynchronous code in its ``__anext__`` method." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2437 +msgid "" +"Asynchronous iterators can be used in an :keyword:`async for` statement." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2441 +msgid "Must return an *asynchronous iterator* object." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2445 +msgid "" +"Must return an *awaitable* resulting in a next value of the iterator. " +"Should raise a :exc:`StopAsyncIteration` error when the iteration is over." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2448 +msgid "An example of an asynchronous iterable object::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2467 +msgid "" +"Starting with CPython 3.5.2, ``__aiter__`` can directly return :term:" +"`asynchronous iterators `. Returning an :term:" +"`awaitable` object will result in a :exc:`PendingDeprecationWarning`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2473 +msgid "" +"The recommended way of writing backwards compatible code in CPython 3.5.x is " +"to continue returning awaitables from ``__aiter__``. If you want to avoid " +"the PendingDeprecationWarning and keep the code backwards compatible, the " +"following decorator can be used::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2492 +msgid "Example::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2503 +msgid "" +"Starting with CPython 3.6, the :exc:`PendingDeprecationWarning` will be " +"replaced with the :exc:`DeprecationWarning`. In CPython 3.7, returning an " +"awaitable from ``__aiter__`` will result in a :exc:`RuntimeError`." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2510 +msgid "Asynchronous Context Managers" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2512 +msgid "" +"An *asynchronous context manager* is a *context manager* that is able to " +"suspend execution in its ``__aenter__`` and ``__aexit__`` methods." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2515 +msgid "" +"Asynchronous context managers can be used in an :keyword:`async with` " +"statement." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2519 +msgid "" +"This method is semantically similar to the :meth:`__enter__`, with only " +"difference that it must return an *awaitable*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2524 +msgid "" +"This method is semantically similar to the :meth:`__exit__`, with only " +"difference that it must return an *awaitable*." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2527 +msgid "An example of an asynchronous context manager class::" +msgstr "" + +#: ../Doc/reference/datamodel.rst:2541 +msgid "" +"It *is* possible in some cases to change an object's type, under certain " +"controlled conditions. It generally isn't a good idea though, since it can " +"lead to some very strange behaviour if it is handled incorrectly." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2545 +msgid "" +"The :meth:`__hash__`, :meth:`__iter__`, :meth:`__reversed__`, and :meth:" +"`__contains__` methods have special handling for this; others will still " +"raise a :exc:`TypeError`, but may do so by relying on the behavior that " +"``None`` is not callable." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2550 +msgid "" +"\"Does not support\" here means that the class has no such method, or the " +"method returns ``NotImplemented``. Do not set the method to ``None`` if you " +"want to force fallback to the right operand's reflected method--that will " +"instead have the opposite effect of explicitly *blocking* such fallback." +msgstr "" + +#: ../Doc/reference/datamodel.rst:2556 +msgid "" +"For operands of the same type, it is assumed that if the non-reflected " +"method (such as :meth:`__add__`) fails the operation is not supported, which " +"is why the reflected method is not called." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:6 +msgid "Execution model" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:15 +msgid "Structure of a program" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:19 +msgid "" +"A Python program is constructed from code blocks. A :dfn:`block` is a piece " +"of Python program text that is executed as a unit. The following are blocks: " +"a module, a function body, and a class definition. Each command typed " +"interactively is a block. A script file (a file given as standard input to " +"the interpreter or specified as a command line argument to the interpreter) " +"is a code block. A script command (a command specified on the interpreter " +"command line with the '**-c**' option) is a code block. The string argument " +"passed to the built-in functions :func:`eval` and :func:`exec` is a code " +"block." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:31 +msgid "" +"A code block is executed in an :dfn:`execution frame`. A frame contains " +"some administrative information (used for debugging) and determines where " +"and how execution continues after the code block's execution has completed." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:38 +msgid "Naming and binding" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:47 +msgid "Binding of names" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:53 +msgid "" +":dfn:`Names` refer to objects. Names are introduced by name binding " +"operations." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:57 +msgid "" +"The following constructs bind names: formal parameters to functions, :" +"keyword:`import` statements, class and function definitions (these bind the " +"class or function name in the defining block), and targets that are " +"identifiers if occurring in an assignment, :keyword:`for` loop header, or " +"after :keyword:`as` in a :keyword:`with` statement or :keyword:`except` " +"clause. The :keyword:`import` statement of the form ``from ... import *`` " +"binds all names defined in the imported module, except those beginning with " +"an underscore. This form may only be used at the module level." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:67 +msgid "" +"A target occurring in a :keyword:`del` statement is also considered bound " +"for this purpose (though the actual semantics are to unbind the name)." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:70 +msgid "" +"Each assignment or import statement occurs within a block defined by a class " +"or function definition or at the module level (the top-level code block)." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:75 +msgid "" +"If a name is bound in a block, it is a local variable of that block, unless " +"declared as :keyword:`nonlocal` or :keyword:`global`. If a name is bound at " +"the module level, it is a global variable. (The variables of the module " +"code block are local and global.) If a variable is used in a code block but " +"not defined there, it is a :dfn:`free variable`." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:81 +msgid "" +"Each occurrence of a name in the program text refers to the :dfn:`binding` " +"of that name established by the following name resolution rules." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:87 +msgid "Resolution of names" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:91 +msgid "" +"A :dfn:`scope` defines the visibility of a name within a block. If a local " +"variable is defined in a block, its scope includes that block. If the " +"definition occurs in a function block, the scope extends to any blocks " +"contained within the defining one, unless a contained block introduces a " +"different binding for the name." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:99 +msgid "" +"When a name is used in a code block, it is resolved using the nearest " +"enclosing scope. The set of all such scopes visible to a code block is " +"called the block's :dfn:`environment`." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:107 +msgid "" +"When a name is not found at all, a :exc:`NameError` exception is raised. If " +"the current scope is a function scope, and the name refers to a local " +"variable that has not yet been bound to a value at the point where the name " +"is used, an :exc:`UnboundLocalError` exception is raised. :exc:" +"`UnboundLocalError` is a subclass of :exc:`NameError`." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:113 +msgid "" +"If a name binding operation occurs anywhere within a code block, all uses of " +"the name within the block are treated as references to the current block. " +"This can lead to errors when a name is used within a block before it is " +"bound. This rule is subtle. Python lacks declarations and allows name " +"binding operations to occur anywhere within a code block. The local " +"variables of a code block can be determined by scanning the entire text of " +"the block for name binding operations." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:120 +msgid "" +"If the :keyword:`global` statement occurs within a block, all uses of the " +"name specified in the statement refer to the binding of that name in the top-" +"level namespace. Names are resolved in the top-level namespace by searching " +"the global namespace, i.e. the namespace of the module containing the code " +"block, and the builtins namespace, the namespace of the module :mod:" +"`builtins`. The global namespace is searched first. If the name is not " +"found there, the builtins namespace is searched. The :keyword:`global` " +"statement must precede all uses of the name." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:129 +msgid "" +"The :keyword:`global` statement has the same scope as a name binding " +"operation in the same block. If the nearest enclosing scope for a free " +"variable contains a global statement, the free variable is treated as a " +"global." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:135 +msgid "" +"The :keyword:`nonlocal` statement causes corresponding names to refer to " +"previously bound variables in the nearest enclosing function scope. :exc:" +"`SyntaxError` is raised at compile time if the given name does not exist in " +"any enclosing function scope." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:142 +msgid "" +"The namespace for a module is automatically created the first time a module " +"is imported. The main module for a script is always called :mod:`__main__`." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:145 +msgid "" +"Class definition blocks and arguments to :func:`exec` and :func:`eval` are " +"special in the context of name resolution. A class definition is an " +"executable statement that may use and define names. These references follow " +"the normal rules for name resolution with an exception that unbound local " +"variables are looked up in the global namespace. The namespace of the class " +"definition becomes the attribute dictionary of the class. The scope of names " +"defined in a class block is limited to the class block; it does not extend " +"to the code blocks of methods -- this includes comprehensions and generator " +"expressions since they are implemented using a function scope. This means " +"that the following will fail::" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:163 +msgid "Builtins and restricted execution" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:167 +msgid "" +"The builtins namespace associated with the execution of a code block is " +"actually found by looking up the name ``__builtins__`` in its global " +"namespace; this should be a dictionary or a module (in the latter case the " +"module's dictionary is used). By default, when in the :mod:`__main__` " +"module, ``__builtins__`` is the built-in module :mod:`builtins`; when in any " +"other module, ``__builtins__`` is an alias for the dictionary of the :mod:" +"`builtins` module itself. ``__builtins__`` can be set to a user-created " +"dictionary to create a weak form of restricted execution." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:178 +msgid "" +"Users should not touch ``__builtins__``; it is strictly an implementation " +"detail. Users wanting to override values in the builtins namespace should :" +"keyword:`import` the :mod:`builtins` module and modify its attributes " +"appropriately." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:186 +msgid "Interaction with dynamic features" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:188 +msgid "" +"Name resolution of free variables occurs at runtime, not at compile time. " +"This means that the following code will print 42::" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:197 +msgid "" +"There are several cases where Python statements are illegal when used in " +"conjunction with nested scopes that contain free variables." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:200 +msgid "" +"If a variable is referenced in an enclosing scope, it is illegal to delete " +"the name. An error will be reported at compile time." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:205 +msgid "" +"The :func:`eval` and :func:`exec` functions do not have access to the full " +"environment for resolving names. Names may be resolved in the local and " +"global namespaces of the caller. Free variables are not resolved in the " +"nearest enclosing namespace, but in the global namespace. [#]_ The :func:" +"`exec` and :func:`eval` functions have optional arguments to override the " +"global and local namespace. If only one namespace is specified, it is used " +"for both." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:216 +msgid "Exceptions" +msgstr "" + +#: ../Doc/reference/executionmodel.rst:227 +msgid "" +"Exceptions are a means of breaking out of the normal flow of control of a " +"code block in order to handle errors or other exceptional conditions. An " +"exception is *raised* at the point where the error is detected; it may be " +"*handled* by the surrounding code block or by any code block that directly " +"or indirectly invoked the code block where the error occurred." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:233 +msgid "" +"The Python interpreter raises an exception when it detects a run-time error " +"(such as division by zero). A Python program can also explicitly raise an " +"exception with the :keyword:`raise` statement. Exception handlers are " +"specified with the :keyword:`try` ... :keyword:`except` statement. The :" +"keyword:`finally` clause of such a statement can be used to specify cleanup " +"code which does not handle the exception, but is executed whether an " +"exception occurred or not in the preceding code." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:243 +msgid "" +"Python uses the \"termination\" model of error handling: an exception " +"handler can find out what happened and continue execution at an outer level, " +"but it cannot repair the cause of the error and retry the failing operation " +"(except by re-entering the offending piece of code from the top)." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:250 +msgid "" +"When an exception is not handled at all, the interpreter terminates " +"execution of the program, or returns to its interactive main loop. In " +"either case, it prints a stack backtrace, except when the exception is :exc:" +"`SystemExit`." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:254 +msgid "" +"Exceptions are identified by class instances. The :keyword:`except` clause " +"is selected depending on the class of the instance: it must reference the " +"class of the instance or a base class thereof. The instance can be received " +"by the handler and can carry additional information about the exceptional " +"condition." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:261 +msgid "" +"Exception messages are not part of the Python API. Their contents may " +"change from one version of Python to the next without warning and should not " +"be relied on by code which will run under multiple versions of the " +"interpreter." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:265 +msgid "" +"See also the description of the :keyword:`try` statement in section :ref:" +"`try` and :keyword:`raise` statement in section :ref:`raise`." +msgstr "" + +#: ../Doc/reference/executionmodel.rst:271 +msgid "" +"This limitation occurs because the code that is executed by these operations " +"is not available at the time the module is compiled." +msgstr "" + +#: ../Doc/reference/expressions.rst:6 +msgid "Expressions" +msgstr "" + +#: ../Doc/reference/expressions.rst:10 +msgid "" +"This chapter explains the meaning of the elements of expressions in Python." +msgstr "" + +#: ../Doc/reference/expressions.rst:12 +msgid "" +"**Syntax Notes:** In this and the following chapters, extended BNF notation " +"will be used to describe syntax, not lexical analysis. When (one " +"alternative of) a syntax rule has the form" +msgstr "" + +#: ../Doc/reference/expressions.rst:19 +msgid "" +"and no semantics are given, the semantics of this form of ``name`` are the " +"same as for ``othername``." +msgstr "" + +#: ../Doc/reference/expressions.rst:26 +msgid "Arithmetic conversions" +msgstr "" + +#: ../Doc/reference/expressions.rst:30 +msgid "" +"When a description of an arithmetic operator below uses the phrase \"the " +"numeric arguments are converted to a common type,\" this means that the " +"operator implementation for built-in types works as follows:" +msgstr "" + +#: ../Doc/reference/expressions.rst:34 +msgid "" +"If either argument is a complex number, the other is converted to complex;" +msgstr "" + +#: ../Doc/reference/expressions.rst:36 +msgid "" +"otherwise, if either argument is a floating point number, the other is " +"converted to floating point;" +msgstr "" + +#: ../Doc/reference/expressions.rst:39 +msgid "otherwise, both must be integers and no conversion is necessary." +msgstr "" + +#: ../Doc/reference/expressions.rst:41 +msgid "" +"Some additional rules apply for certain operators (e.g., a string as a left " +"argument to the '%' operator). Extensions must define their own conversion " +"behavior." +msgstr "" + +#: ../Doc/reference/expressions.rst:49 +msgid "Atoms" +msgstr "" + +#: ../Doc/reference/expressions.rst:53 +msgid "" +"Atoms are the most basic elements of expressions. The simplest atoms are " +"identifiers or literals. Forms enclosed in parentheses, brackets or braces " +"are also categorized syntactically as atoms. The syntax for atoms is:" +msgstr "" + +#: ../Doc/reference/expressions.rst:66 +msgid "Identifiers (Names)" +msgstr "" + +#: ../Doc/reference/expressions.rst:70 +msgid "" +"An identifier occurring as an atom is a name. See section :ref:" +"`identifiers` for lexical definition and section :ref:`naming` for " +"documentation of naming and binding." +msgstr "" + +#: ../Doc/reference/expressions.rst:76 +msgid "" +"When the name is bound to an object, evaluation of the atom yields that " +"object. When a name is not bound, an attempt to evaluate it raises a :exc:" +"`NameError` exception." +msgstr "" + +#: ../Doc/reference/expressions.rst:84 +msgid "" +"**Private name mangling:** When an identifier that textually occurs in a " +"class definition begins with two or more underscore characters and does not " +"end in two or more underscores, it is considered a :dfn:`private name` of " +"that class. Private names are transformed to a longer form before code is " +"generated for them. The transformation inserts the class name, with leading " +"underscores removed and a single underscore inserted, in front of the name. " +"For example, the identifier ``__spam`` occurring in a class named ``Ham`` " +"will be transformed to ``_Ham__spam``. This transformation is independent " +"of the syntactical context in which the identifier is used. If the " +"transformed name is extremely long (longer than 255 characters), " +"implementation defined truncation may happen. If the class name consists " +"only of underscores, no transformation is done." +msgstr "" + +#: ../Doc/reference/expressions.rst:100 +#: ../Doc/reference/lexical_analysis.rst:390 +msgid "Literals" +msgstr "" + +#: ../Doc/reference/expressions.rst:104 +msgid "Python supports string and bytes literals and various numeric literals:" +msgstr "" + +#: ../Doc/reference/expressions.rst:110 +msgid "" +"Evaluation of a literal yields an object of the given type (string, bytes, " +"integer, floating point number, complex number) with the given value. The " +"value may be approximated in the case of floating point and imaginary " +"(complex) literals. See section :ref:`literals` for details." +msgstr "" + +#: ../Doc/reference/expressions.rst:119 +msgid "" +"All literals correspond to immutable data types, and hence the object's " +"identity is less important than its value. Multiple evaluations of literals " +"with the same value (either the same occurrence in the program text or a " +"different occurrence) may obtain the same object or a different object with " +"the same value." +msgstr "" + +#: ../Doc/reference/expressions.rst:129 +msgid "Parenthesized forms" +msgstr "" + +#: ../Doc/reference/expressions.rst:133 +msgid "" +"A parenthesized form is an optional expression list enclosed in parentheses:" +msgstr "" + +#: ../Doc/reference/expressions.rst:138 +msgid "" +"A parenthesized expression list yields whatever that expression list yields: " +"if the list contains at least one comma, it yields a tuple; otherwise, it " +"yields the single expression that makes up the expression list." +msgstr "" + +#: ../Doc/reference/expressions.rst:144 +msgid "" +"An empty pair of parentheses yields an empty tuple object. Since tuples are " +"immutable, the rules for literals apply (i.e., two occurrences of the empty " +"tuple may or may not yield the same object)." +msgstr "" + +#: ../Doc/reference/expressions.rst:152 +msgid "" +"Note that tuples are not formed by the parentheses, but rather by use of the " +"comma operator. The exception is the empty tuple, for which parentheses " +"*are* required --- allowing unparenthesized \"nothing\" in expressions would " +"cause ambiguities and allow common typos to pass uncaught." +msgstr "" + +#: ../Doc/reference/expressions.rst:161 +msgid "Displays for lists, sets and dictionaries" +msgstr "" + +#: ../Doc/reference/expressions.rst:163 +msgid "" +"For constructing a list, a set or a dictionary Python provides special " +"syntax called \"displays\", each of them in two flavors:" +msgstr "" + +#: ../Doc/reference/expressions.rst:166 +msgid "either the container contents are listed explicitly, or" +msgstr "" + +#: ../Doc/reference/expressions.rst:168 +msgid "" +"they are computed via a set of looping and filtering instructions, called a :" +"dfn:`comprehension`." +msgstr "" + +#: ../Doc/reference/expressions.rst:171 +msgid "Common syntax elements for comprehensions are:" +msgstr "" + +#: ../Doc/reference/expressions.rst:179 +msgid "" +"The comprehension consists of a single expression followed by at least one :" +"keyword:`for` clause and zero or more :keyword:`for` or :keyword:`if` " +"clauses. In this case, the elements of the new container are those that " +"would be produced by considering each of the :keyword:`for` or :keyword:`if` " +"clauses a block, nesting from left to right, and evaluating the expression " +"to produce an element each time the innermost block is reached." +msgstr "" + +#: ../Doc/reference/expressions.rst:186 +msgid "" +"Note that the comprehension is executed in a separate scope, so names " +"assigned to in the target list don't \"leak\" into the enclosing scope." +msgstr "" + +#: ../Doc/reference/expressions.rst:193 +msgid "List displays" +msgstr "" + +#: ../Doc/reference/expressions.rst:201 +msgid "" +"A list display is a possibly empty series of expressions enclosed in square " +"brackets:" +msgstr "" + +#: ../Doc/reference/expressions.rst:207 +msgid "" +"A list display yields a new list object, the contents being specified by " +"either a list of expressions or a comprehension. When a comma-separated " +"list of expressions is supplied, its elements are evaluated from left to " +"right and placed into the list object in that order. When a comprehension " +"is supplied, the list is constructed from the elements resulting from the " +"comprehension." +msgstr "" + +#: ../Doc/reference/expressions.rst:217 +msgid "Set displays" +msgstr "" + +#: ../Doc/reference/expressions.rst:222 +msgid "" +"A set display is denoted by curly braces and distinguishable from dictionary " +"displays by the lack of colons separating keys and values:" +msgstr "" + +#: ../Doc/reference/expressions.rst:228 +msgid "" +"A set display yields a new mutable set object, the contents being specified " +"by either a sequence of expressions or a comprehension. When a comma-" +"separated list of expressions is supplied, its elements are evaluated from " +"left to right and added to the set object. When a comprehension is " +"supplied, the set is constructed from the elements resulting from the " +"comprehension." +msgstr "" + +#: ../Doc/reference/expressions.rst:234 +msgid "" +"An empty set cannot be constructed with ``{}``; this literal constructs an " +"empty dictionary." +msgstr "" + +#: ../Doc/reference/expressions.rst:241 +msgid "Dictionary displays" +msgstr "" + +#: ../Doc/reference/expressions.rst:247 +msgid "" +"A dictionary display is a possibly empty series of key/datum pairs enclosed " +"in curly braces:" +msgstr "" + +#: ../Doc/reference/expressions.rst:256 +msgid "A dictionary display yields a new dictionary object." +msgstr "" + +#: ../Doc/reference/expressions.rst:258 +msgid "" +"If a comma-separated sequence of key/datum pairs is given, they are " +"evaluated from left to right to define the entries of the dictionary: each " +"key object is used as a key into the dictionary to store the corresponding " +"datum. This means that you can specify the same key multiple times in the " +"key/datum list, and the final dictionary's value for that key will be the " +"last one given." +msgstr "" + +#: ../Doc/reference/expressions.rst:266 +msgid "" +"A double asterisk ``**`` denotes :dfn:`dictionary unpacking`. Its operand " +"must be a :term:`mapping`. Each mapping item is added to the new " +"dictionary. Later values replace values already set by earlier key/datum " +"pairs and earlier dictionary unpackings." +msgstr "" + +#: ../Doc/reference/expressions.rst:271 +msgid "Unpacking into dictionary displays, originally proposed by :pep:`448`." +msgstr "" + +#: ../Doc/reference/expressions.rst:274 +msgid "" +"A dict comprehension, in contrast to list and set comprehensions, needs two " +"expressions separated with a colon followed by the usual \"for\" and \"if\" " +"clauses. When the comprehension is run, the resulting key and value elements " +"are inserted in the new dictionary in the order they are produced." +msgstr "" + +#: ../Doc/reference/expressions.rst:282 +msgid "" +"Restrictions on the types of the key values are listed earlier in section :" +"ref:`types`. (To summarize, the key type should be :term:`hashable`, which " +"excludes all mutable objects.) Clashes between duplicate keys are not " +"detected; the last datum (textually rightmost in the display) stored for a " +"given key value prevails." +msgstr "" + +#: ../Doc/reference/expressions.rst:292 +msgid "Generator expressions" +msgstr "" + +#: ../Doc/reference/expressions.rst:297 +msgid "A generator expression is a compact generator notation in parentheses:" +msgstr "" + +#: ../Doc/reference/expressions.rst:302 +msgid "" +"A generator expression yields a new generator object. Its syntax is the " +"same as for comprehensions, except that it is enclosed in parentheses " +"instead of brackets or curly braces." +msgstr "" + +#: ../Doc/reference/expressions.rst:306 +msgid "" +"Variables used in the generator expression are evaluated lazily when the :" +"meth:`~generator.__next__` method is called for the generator object (in the " +"same fashion as normal generators). However, the leftmost :keyword:`for` " +"clause is immediately evaluated, so that an error produced by it can be seen " +"before any other possible error in the code that handles the generator " +"expression. Subsequent :keyword:`for` clauses cannot be evaluated " +"immediately since they may depend on the previous :keyword:`for` loop. For " +"example: ``(x*y for x in range(10) for y in bar(x))``." +msgstr "" + +#: ../Doc/reference/expressions.rst:315 +msgid "" +"The parentheses can be omitted on calls with only one argument. See " +"section :ref:`calls` for details." +msgstr "" + +#: ../Doc/reference/expressions.rst:322 +msgid "Yield expressions" +msgstr "" + +#: ../Doc/reference/expressions.rst:333 +msgid "" +"The yield expression is only used when defining a :term:`generator` function " +"and thus can only be used in the body of a function definition. Using a " +"yield expression in a function's body causes that function to be a generator." +msgstr "" + +#: ../Doc/reference/expressions.rst:337 +msgid "" +"When a generator function is called, it returns an iterator known as a " +"generator. That generator then controls the execution of the generator " +"function. The execution starts when one of the generator's methods is " +"called. At that time, the execution proceeds to the first yield expression, " +"where it is suspended again, returning the value of :token:`expression_list` " +"to the generator's caller. By suspended, we mean that all local state is " +"retained, including the current bindings of local variables, the instruction " +"pointer, the internal evaluation stack, and the state of any exception " +"handling. When the execution is resumed by calling one of the generator's " +"methods, the function can proceed exactly as if the yield expression were " +"just another external call. The value of the yield expression after " +"resuming depends on the method which resumed the execution. If :meth:" +"`~generator.__next__` is used (typically via either a :keyword:`for` or the :" +"func:`next` builtin) then the result is :const:`None`. Otherwise, if :meth:" +"`~generator.send` is used, then the result will be the value passed in to " +"that method." +msgstr "" + +#: ../Doc/reference/expressions.rst:356 +msgid "" +"All of this makes generator functions quite similar to coroutines; they " +"yield multiple times, they have more than one entry point and their " +"execution can be suspended. The only difference is that a generator " +"function cannot control where the execution should continue after it yields; " +"the control is always transferred to the generator's caller." +msgstr "" + +#: ../Doc/reference/expressions.rst:362 +msgid "" +"Yield expressions are allowed anywhere in a :keyword:`try` construct. If " +"the generator is not resumed before it is finalized (by reaching a zero " +"reference count or by being garbage collected), the generator-iterator's :" +"meth:`~generator.close` method will be called, allowing any pending :keyword:" +"`finally` clauses to execute." +msgstr "" + +#: ../Doc/reference/expressions.rst:368 +msgid "" +"When ``yield from `` is used, it treats the supplied expression as a " +"subiterator. All values produced by that subiterator are passed directly to " +"the caller of the current generator's methods. Any values passed in with :" +"meth:`~generator.send` and any exceptions passed in with :meth:`~generator." +"throw` are passed to the underlying iterator if it has the appropriate " +"methods. If this is not the case, then :meth:`~generator.send` will raise :" +"exc:`AttributeError` or :exc:`TypeError`, while :meth:`~generator.throw` " +"will just raise the passed in exception immediately." +msgstr "" + +#: ../Doc/reference/expressions.rst:377 +msgid "" +"When the underlying iterator is complete, the :attr:`~StopIteration.value` " +"attribute of the raised :exc:`StopIteration` instance becomes the value of " +"the yield expression. It can be either set explicitly when raising :exc:" +"`StopIteration`, or automatically when the sub-iterator is a generator (by " +"returning a value from the sub-generator)." +msgstr "" + +#: ../Doc/reference/expressions.rst:383 +msgid "Added ``yield from `` to delegate control flow to a subiterator." +msgstr "" + +#: ../Doc/reference/expressions.rst:386 +msgid "" +"The parentheses may be omitted when the yield expression is the sole " +"expression on the right hand side of an assignment statement." +msgstr "" + +#: ../Doc/reference/expressions.rst:392 +msgid ":pep:`255` - Simple Generators" +msgstr "" + +#: ../Doc/reference/expressions.rst:392 +msgid "" +"The proposal for adding generators and the :keyword:`yield` statement to " +"Python." +msgstr "" + +#: ../Doc/reference/expressions.rst:396 +msgid ":pep:`342` - Coroutines via Enhanced Generators" +msgstr "" + +#: ../Doc/reference/expressions.rst:395 +msgid "" +"The proposal to enhance the API and syntax of generators, making them usable " +"as simple coroutines." +msgstr "" + +#: ../Doc/reference/expressions.rst:399 +msgid ":pep:`380` - Syntax for Delegating to a Subgenerator" +msgstr "" + +#: ../Doc/reference/expressions.rst:399 +msgid "" +"The proposal to introduce the :token:`yield_from` syntax, making delegation " +"to sub-generators easy." +msgstr "" + +#: ../Doc/reference/expressions.rst:406 +msgid "Generator-iterator methods" +msgstr "" + +#: ../Doc/reference/expressions.rst:408 +msgid "" +"This subsection describes the methods of a generator iterator. They can be " +"used to control the execution of a generator function." +msgstr "" + +#: ../Doc/reference/expressions.rst:411 +msgid "" +"Note that calling any of the generator methods below when the generator is " +"already executing raises a :exc:`ValueError` exception." +msgstr "" + +#: ../Doc/reference/expressions.rst:419 +msgid "" +"Starts the execution of a generator function or resumes it at the last " +"executed yield expression. When a generator function is resumed with a :" +"meth:`~generator.__next__` method, the current yield expression always " +"evaluates to :const:`None`. The execution then continues to the next yield " +"expression, where the generator is suspended again, and the value of the :" +"token:`expression_list` is returned to :meth:`__next__`'s caller. If the " +"generator exits without yielding another value, a :exc:`StopIteration` " +"exception is raised." +msgstr "" + +#: ../Doc/reference/expressions.rst:428 +msgid "" +"This method is normally called implicitly, e.g. by a :keyword:`for` loop, or " +"by the built-in :func:`next` function." +msgstr "" + +#: ../Doc/reference/expressions.rst:434 +msgid "" +"Resumes the execution and \"sends\" a value into the generator function. " +"The *value* argument becomes the result of the current yield expression. " +"The :meth:`send` method returns the next value yielded by the generator, or " +"raises :exc:`StopIteration` if the generator exits without yielding another " +"value. When :meth:`send` is called to start the generator, it must be " +"called with :const:`None` as the argument, because there is no yield " +"expression that could receive the value." +msgstr "" + +#: ../Doc/reference/expressions.rst:445 +msgid "" +"Raises an exception of type ``type`` at the point where the generator was " +"paused, and returns the next value yielded by the generator function. If " +"the generator exits without yielding another value, a :exc:`StopIteration` " +"exception is raised. If the generator function does not catch the passed-in " +"exception, or raises a different exception, then that exception propagates " +"to the caller." +msgstr "" + +#: ../Doc/reference/expressions.rst:456 +msgid "" +"Raises a :exc:`GeneratorExit` at the point where the generator function was " +"paused. If the generator function then exits gracefully, is already closed, " +"or raises :exc:`GeneratorExit` (by not catching the exception), close " +"returns to its caller. If the generator yields a value, a :exc:" +"`RuntimeError` is raised. If the generator raises any other exception, it " +"is propagated to the caller. :meth:`close` does nothing if the generator " +"has already exited due to an exception or normal exit." +msgstr "" + +#: ../Doc/reference/expressions.rst:467 +msgid "Examples" +msgstr "" + +#: ../Doc/reference/expressions.rst:469 +msgid "" +"Here is a simple example that demonstrates the behavior of generators and " +"generator functions::" +msgstr "" + +#: ../Doc/reference/expressions.rst:496 +msgid "" +"For examples using ``yield from``, see :ref:`pep-380` in \"What's New in " +"Python.\"" +msgstr "" + +#: ../Doc/reference/expressions.rst:503 +msgid "Primaries" +msgstr "" + +#: ../Doc/reference/expressions.rst:507 +msgid "" +"Primaries represent the most tightly bound operations of the language. Their " +"syntax is:" +msgstr "" + +#: ../Doc/reference/expressions.rst:517 +msgid "Attribute references" +msgstr "" + +#: ../Doc/reference/expressions.rst:521 +msgid "An attribute reference is a primary followed by a period and a name:" +msgstr "" + +#: ../Doc/reference/expressions.rst:531 +msgid "" +"The primary must evaluate to an object of a type that supports attribute " +"references, which most objects do. This object is then asked to produce the " +"attribute whose name is the identifier. This production can be customized " +"by overriding the :meth:`__getattr__` method. If this attribute is not " +"available, the exception :exc:`AttributeError` is raised. Otherwise, the " +"type and value of the object produced is determined by the object. Multiple " +"evaluations of the same attribute reference may yield different objects." +msgstr "" + +#: ../Doc/reference/expressions.rst:543 +msgid "Subscriptions" +msgstr "" + +#: ../Doc/reference/expressions.rst:556 +msgid "" +"A subscription selects an item of a sequence (string, tuple or list) or " +"mapping (dictionary) object:" +msgstr "" + +#: ../Doc/reference/expressions.rst:562 +msgid "" +"The primary must evaluate to an object that supports subscription (lists or " +"dictionaries for example). User-defined objects can support subscription by " +"defining a :meth:`__getitem__` method." +msgstr "" + +#: ../Doc/reference/expressions.rst:566 +msgid "" +"For built-in objects, there are two types of objects that support " +"subscription:" +msgstr "" + +#: ../Doc/reference/expressions.rst:568 +msgid "" +"If the primary is a mapping, the expression list must evaluate to an object " +"whose value is one of the keys of the mapping, and the subscription selects " +"the value in the mapping that corresponds to that key. (The expression list " +"is a tuple except if it has exactly one item.)" +msgstr "" + +#: ../Doc/reference/expressions.rst:573 +msgid "" +"If the primary is a sequence, the expression (list) must evaluate to an " +"integer or a slice (as discussed in the following section)." +msgstr "" + +#: ../Doc/reference/expressions.rst:576 +msgid "" +"The formal syntax makes no special provision for negative indices in " +"sequences; however, built-in sequences all provide a :meth:`__getitem__` " +"method that interprets negative indices by adding the length of the sequence " +"to the index (so that ``x[-1]`` selects the last item of ``x``). The " +"resulting value must be a nonnegative integer less than the number of items " +"in the sequence, and the subscription selects the item whose index is that " +"value (counting from zero). Since the support for negative indices and " +"slicing occurs in the object's :meth:`__getitem__` method, subclasses " +"overriding this method will need to explicitly add that support." +msgstr "" + +#: ../Doc/reference/expressions.rst:590 +msgid "" +"A string's items are characters. A character is not a separate data type " +"but a string of exactly one character." +msgstr "" + +#: ../Doc/reference/expressions.rst:597 +msgid "Slicings" +msgstr "" + +#: ../Doc/reference/expressions.rst:609 +msgid "" +"A slicing selects a range of items in a sequence object (e.g., a string, " +"tuple or list). Slicings may be used as expressions or as targets in " +"assignment or :keyword:`del` statements. The syntax for a slicing:" +msgstr "" + +#: ../Doc/reference/expressions.rst:622 +msgid "" +"There is ambiguity in the formal syntax here: anything that looks like an " +"expression list also looks like a slice list, so any subscription can be " +"interpreted as a slicing. Rather than further complicating the syntax, this " +"is disambiguated by defining that in this case the interpretation as a " +"subscription takes priority over the interpretation as a slicing (this is " +"the case if the slice list contains no proper slice)." +msgstr "" + +#: ../Doc/reference/expressions.rst:634 +msgid "" +"The semantics for a slicing are as follows. The primary is indexed (using " +"the same :meth:`__getitem__` method as normal subscription) with a key that " +"is constructed from the slice list, as follows. If the slice list contains " +"at least one comma, the key is a tuple containing the conversion of the " +"slice items; otherwise, the conversion of the lone slice item is the key. " +"The conversion of a slice item that is an expression is that expression. " +"The conversion of a proper slice is a slice object (see section :ref:" +"`types`) whose :attr:`~slice.start`, :attr:`~slice.stop` and :attr:`~slice." +"step` attributes are the values of the expressions given as lower bound, " +"upper bound and stride, respectively, substituting ``None`` for missing " +"expressions." +msgstr "" + +#: ../Doc/reference/expressions.rst:655 +msgid "Calls" +msgstr "" + +#: ../Doc/reference/expressions.rst:657 +msgid "" +"A call calls a callable object (e.g., a :term:`function`) with a possibly " +"empty series of :term:`arguments `:" +msgstr "" + +#: ../Doc/reference/expressions.rst:673 +msgid "" +"An optional trailing comma may be present after the positional and keyword " +"arguments but does not affect the semantics." +msgstr "" + +#: ../Doc/reference/expressions.rst:679 +msgid "" +"The primary must evaluate to a callable object (user-defined functions, " +"built-in functions, methods of built-in objects, class objects, methods of " +"class instances, and all objects having a :meth:`__call__` method are " +"callable). All argument expressions are evaluated before the call is " +"attempted. Please refer to section :ref:`function` for the syntax of " +"formal :term:`parameter` lists." +msgstr "" + +#: ../Doc/reference/expressions.rst:687 +msgid "" +"If keyword arguments are present, they are first converted to positional " +"arguments, as follows. First, a list of unfilled slots is created for the " +"formal parameters. If there are N positional arguments, they are placed in " +"the first N slots. Next, for each keyword argument, the identifier is used " +"to determine the corresponding slot (if the identifier is the same as the " +"first formal parameter name, the first slot is used, and so on). If the " +"slot is already filled, a :exc:`TypeError` exception is raised. Otherwise, " +"the value of the argument is placed in the slot, filling it (even if the " +"expression is ``None``, it fills the slot). When all arguments have been " +"processed, the slots that are still unfilled are filled with the " +"corresponding default value from the function definition. (Default values " +"are calculated, once, when the function is defined; thus, a mutable object " +"such as a list or dictionary used as default value will be shared by all " +"calls that don't specify an argument value for the corresponding slot; this " +"should usually be avoided.) If there are any unfilled slots for which no " +"default value is specified, a :exc:`TypeError` exception is raised. " +"Otherwise, the list of filled slots is used as the argument list for the " +"call." +msgstr "" + +#: ../Doc/reference/expressions.rst:707 +msgid "" +"An implementation may provide built-in functions whose positional parameters " +"do not have names, even if they are 'named' for the purpose of " +"documentation, and which therefore cannot be supplied by keyword. In " +"CPython, this is the case for functions implemented in C that use :c:func:" +"`PyArg_ParseTuple` to parse their arguments." +msgstr "" + +#: ../Doc/reference/expressions.rst:713 +msgid "" +"If there are more positional arguments than there are formal parameter " +"slots, a :exc:`TypeError` exception is raised, unless a formal parameter " +"using the syntax ``*identifier`` is present; in this case, that formal " +"parameter receives a tuple containing the excess positional arguments (or an " +"empty tuple if there were no excess positional arguments)." +msgstr "" + +#: ../Doc/reference/expressions.rst:719 +msgid "" +"If any keyword argument does not correspond to a formal parameter name, a :" +"exc:`TypeError` exception is raised, unless a formal parameter using the " +"syntax ``**identifier`` is present; in this case, that formal parameter " +"receives a dictionary containing the excess keyword arguments (using the " +"keywords as keys and the argument values as corresponding values), or a " +"(new) empty dictionary if there were no excess keyword arguments." +msgstr "" + +#: ../Doc/reference/expressions.rst:730 +msgid "" +"If the syntax ``*expression`` appears in the function call, ``expression`` " +"must evaluate to an :term:`iterable`. Elements from these iterables are " +"treated as if they were additional positional arguments. For the call " +"``f(x1, x2, *y, x3, x4)``, if *y* evaluates to a sequence *y1*, ..., *yM*, " +"this is equivalent to a call with M+4 positional arguments *x1*, *x2*, " +"*y1*, ..., *yM*, *x3*, *x4*." +msgstr "" + +#: ../Doc/reference/expressions.rst:737 +msgid "" +"A consequence of this is that although the ``*expression`` syntax may appear " +"*after* explicit keyword arguments, it is processed *before* the keyword " +"arguments (and any ``**expression`` arguments -- see below). So::" +msgstr "" + +#: ../Doc/reference/expressions.rst:753 +msgid "" +"It is unusual for both keyword arguments and the ``*expression`` syntax to " +"be used in the same call, so in practice this confusion does not arise." +msgstr "" + +#: ../Doc/reference/expressions.rst:759 +msgid "" +"If the syntax ``**expression`` appears in the function call, ``expression`` " +"must evaluate to a :term:`mapping`, the contents of which are treated as " +"additional keyword arguments. If a keyword is already present (as an " +"explicit keyword argument, or from another unpacking), a :exc:`TypeError` " +"exception is raised." +msgstr "" + +#: ../Doc/reference/expressions.rst:765 +msgid "" +"Formal parameters using the syntax ``*identifier`` or ``**identifier`` " +"cannot be used as positional argument slots or as keyword argument names." +msgstr "" + +#: ../Doc/reference/expressions.rst:768 +msgid "" +"Function calls accept any number of ``*`` and ``**`` unpackings, positional " +"arguments may follow iterable unpackings (``*``), and keyword arguments may " +"follow dictionary unpackings (``**``). Originally proposed by :pep:`448`." +msgstr "" + +#: ../Doc/reference/expressions.rst:774 +msgid "" +"A call always returns some value, possibly ``None``, unless it raises an " +"exception. How this value is computed depends on the type of the callable " +"object." +msgstr "" + +#: ../Doc/reference/expressions.rst:778 +msgid "If it is---" +msgstr "" + +#: ../Doc/reference/expressions.rst:791 +msgid "a user-defined function:" +msgstr "" + +#: ../Doc/reference/expressions.rst:787 +msgid "" +"The code block for the function is executed, passing it the argument list. " +"The first thing the code block will do is bind the formal parameters to the " +"arguments; this is described in section :ref:`function`. When the code " +"block executes a :keyword:`return` statement, this specifies the return " +"value of the function call." +msgstr "" + +#: ../Doc/reference/expressions.rst:805 +msgid "a built-in function or method:" +msgstr "" + +#: ../Doc/reference/expressions.rst:804 +msgid "" +"The result is up to the interpreter; see :ref:`built-in-funcs` for the " +"descriptions of built-in functions and methods." +msgstr "" + +#: ../Doc/reference/expressions.rst:812 +msgid "a class object:" +msgstr "" + +#: ../Doc/reference/expressions.rst:812 +msgid "A new instance of that class is returned." +msgstr "" + +#: ../Doc/reference/expressions.rst:822 +msgid "a class instance method:" +msgstr "" + +#: ../Doc/reference/expressions.rst:820 +msgid "" +"The corresponding user-defined function is called, with an argument list " +"that is one longer than the argument list of the call: the instance becomes " +"the first argument." +msgstr "" + +#: ../Doc/reference/expressions.rst:831 +msgid "a class instance:" +msgstr "" + +#: ../Doc/reference/expressions.rst:829 +msgid "" +"The class must define a :meth:`__call__` method; the effect is then the same " +"as if that method was called." +msgstr "" + +#: ../Doc/reference/expressions.rst:836 ../Doc/reference/expressions.rst:1537 +msgid "Await expression" +msgstr "" + +#: ../Doc/reference/expressions.rst:838 +msgid "" +"Suspend the execution of :term:`coroutine` on an :term:`awaitable` object. " +"Can only be used inside a :term:`coroutine function`." +msgstr "" + +#: ../Doc/reference/expressions.rst:850 +msgid "The power operator" +msgstr "" + +#: ../Doc/reference/expressions.rst:852 +msgid "" +"The power operator binds more tightly than unary operators on its left; it " +"binds less tightly than unary operators on its right. The syntax is:" +msgstr "" + +#: ../Doc/reference/expressions.rst:858 +msgid "" +"Thus, in an unparenthesized sequence of power and unary operators, the " +"operators are evaluated from right to left (this does not constrain the " +"evaluation order for the operands): ``-1**2`` results in ``-1``." +msgstr "" + +#: ../Doc/reference/expressions.rst:862 +msgid "" +"The power operator has the same semantics as the built-in :func:`pow` " +"function, when called with two arguments: it yields its left argument raised " +"to the power of its right argument. The numeric arguments are first " +"converted to a common type, and the result is of that type." +msgstr "" + +#: ../Doc/reference/expressions.rst:867 +msgid "" +"For int operands, the result has the same type as the operands unless the " +"second argument is negative; in that case, all arguments are converted to " +"float and a float result is delivered. For example, ``10**2`` returns " +"``100``, but ``10**-2`` returns ``0.01``." +msgstr "" + +#: ../Doc/reference/expressions.rst:872 +msgid "" +"Raising ``0.0`` to a negative power results in a :exc:`ZeroDivisionError`. " +"Raising a negative number to a fractional power results in a :class:" +"`complex` number. (In earlier versions it raised a :exc:`ValueError`.)" +msgstr "" + +#: ../Doc/reference/expressions.rst:880 +msgid "Unary arithmetic and bitwise operations" +msgstr "" + +#: ../Doc/reference/expressions.rst:886 +msgid "All unary arithmetic and bitwise operations have the same priority:" +msgstr "" + +#: ../Doc/reference/expressions.rst:895 +msgid "" +"The unary ``-`` (minus) operator yields the negation of its numeric argument." +msgstr "" + +#: ../Doc/reference/expressions.rst:899 +msgid "The unary ``+`` (plus) operator yields its numeric argument unchanged." +msgstr "" + +#: ../Doc/reference/expressions.rst:904 +msgid "" +"The unary ``~`` (invert) operator yields the bitwise inversion of its " +"integer argument. The bitwise inversion of ``x`` is defined as ``-(x+1)``. " +"It only applies to integral numbers." +msgstr "" + +#: ../Doc/reference/expressions.rst:910 +msgid "" +"In all three cases, if the argument does not have the proper type, a :exc:" +"`TypeError` exception is raised." +msgstr "" + +#: ../Doc/reference/expressions.rst:917 +msgid "Binary arithmetic operations" +msgstr "" + +#: ../Doc/reference/expressions.rst:921 +msgid "" +"The binary arithmetic operations have the conventional priority levels. " +"Note that some of these operations also apply to certain non-numeric types. " +"Apart from the power operator, there are only two levels, one for " +"multiplicative operators and one for additive operators:" +msgstr "" + +#: ../Doc/reference/expressions.rst:934 +msgid "" +"The ``*`` (multiplication) operator yields the product of its arguments. " +"The arguments must either both be numbers, or one argument must be an " +"integer and the other must be a sequence. In the former case, the numbers " +"are converted to a common type and then multiplied together. In the latter " +"case, sequence repetition is performed; a negative repetition factor yields " +"an empty sequence." +msgstr "" + +#: ../Doc/reference/expressions.rst:942 +msgid "" +"The ``@`` (at) operator is intended to be used for matrix multiplication. " +"No builtin Python types implement this operator." +msgstr "" + +#: ../Doc/reference/expressions.rst:951 +msgid "" +"The ``/`` (division) and ``//`` (floor division) operators yield the " +"quotient of their arguments. The numeric arguments are first converted to a " +"common type. Division of integers yields a float, while floor division of " +"integers results in an integer; the result is that of mathematical division " +"with the 'floor' function applied to the result. Division by zero raises " +"the :exc:`ZeroDivisionError` exception." +msgstr "" + +#: ../Doc/reference/expressions.rst:960 +msgid "" +"The ``%`` (modulo) operator yields the remainder from the division of the " +"first argument by the second. The numeric arguments are first converted to " +"a common type. A zero right argument raises the :exc:`ZeroDivisionError` " +"exception. The arguments may be floating point numbers, e.g., ``3.14%0.7`` " +"equals ``0.34`` (since ``3.14`` equals ``4*0.7 + 0.34``.) The modulo " +"operator always yields a result with the same sign as its second operand (or " +"zero); the absolute value of the result is strictly smaller than the " +"absolute value of the second operand [#]_." +msgstr "" + +#: ../Doc/reference/expressions.rst:969 +msgid "" +"The floor division and modulo operators are connected by the following " +"identity: ``x == (x//y)*y + (x%y)``. Floor division and modulo are also " +"connected with the built-in function :func:`divmod`: ``divmod(x, y) == (x//" +"y, x%y)``. [#]_." +msgstr "" + +#: ../Doc/reference/expressions.rst:974 +msgid "" +"In addition to performing the modulo operation on numbers, the ``%`` " +"operator is also overloaded by string objects to perform old-style string " +"formatting (also known as interpolation). The syntax for string formatting " +"is described in the Python Library Reference, section :ref:`old-string-" +"formatting`." +msgstr "" + +#: ../Doc/reference/expressions.rst:979 +msgid "" +"The floor division operator, the modulo operator, and the :func:`divmod` " +"function are not defined for complex numbers. Instead, convert to a " +"floating point number using the :func:`abs` function if appropriate." +msgstr "" + +#: ../Doc/reference/expressions.rst:985 +msgid "" +"The ``+`` (addition) operator yields the sum of its arguments. The " +"arguments must either both be numbers or both be sequences of the same " +"type. In the former case, the numbers are converted to a common type and " +"then added together. In the latter case, the sequences are concatenated." +msgstr "" + +#: ../Doc/reference/expressions.rst:992 +msgid "" +"The ``-`` (subtraction) operator yields the difference of its arguments. " +"The numeric arguments are first converted to a common type." +msgstr "" + +#: ../Doc/reference/expressions.rst:999 +msgid "Shifting operations" +msgstr "" + +#: ../Doc/reference/expressions.rst:1003 +msgid "" +"The shifting operations have lower priority than the arithmetic operations:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1008 +msgid "" +"These operators accept integers as arguments. They shift the first argument " +"to the left or right by the number of bits given by the second argument." +msgstr "" + +#: ../Doc/reference/expressions.rst:1013 +msgid "" +"A right shift by *n* bits is defined as floor division by ``pow(2,n)``. A " +"left shift by *n* bits is defined as multiplication with ``pow(2,n)``." +msgstr "" + +#: ../Doc/reference/expressions.rst:1018 +msgid "" +"In the current implementation, the right-hand operand is required to be at " +"most :attr:`sys.maxsize`. If the right-hand operand is larger than :attr:" +"`sys.maxsize` an :exc:`OverflowError` exception is raised." +msgstr "" + +#: ../Doc/reference/expressions.rst:1025 +msgid "Binary bitwise operations" +msgstr "" + +#: ../Doc/reference/expressions.rst:1029 +msgid "Each of the three bitwise operations has a different priority level:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1038 +msgid "" +"The ``&`` operator yields the bitwise AND of its arguments, which must be " +"integers." +msgstr "" + +#: ../Doc/reference/expressions.rst:1045 +msgid "" +"The ``^`` operator yields the bitwise XOR (exclusive OR) of its arguments, " +"which must be integers." +msgstr "" + +#: ../Doc/reference/expressions.rst:1052 +msgid "" +"The ``|`` operator yields the bitwise (inclusive) OR of its arguments, which " +"must be integers." +msgstr "" + +#: ../Doc/reference/expressions.rst:1059 +msgid "Comparisons" +msgstr "" + +#: ../Doc/reference/expressions.rst:1065 +msgid "" +"Unlike C, all comparison operations in Python have the same priority, which " +"is lower than that of any arithmetic, shifting or bitwise operation. Also " +"unlike C, expressions like ``a < b < c`` have the interpretation that is " +"conventional in mathematics:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1075 +msgid "Comparisons yield boolean values: ``True`` or ``False``." +msgstr "" + +#: ../Doc/reference/expressions.rst:1079 +msgid "" +"Comparisons can be chained arbitrarily, e.g., ``x < y <= z`` is equivalent " +"to ``x < y and y <= z``, except that ``y`` is evaluated only once (but in " +"both cases ``z`` is not evaluated at all when ``x < y`` is found to be " +"false)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1083 +msgid "" +"Formally, if *a*, *b*, *c*, ..., *y*, *z* are expressions and *op1*, " +"*op2*, ..., *opN* are comparison operators, then ``a op1 b op2 c ... y opN " +"z`` is equivalent to ``a op1 b and b op2 c and ... y opN z``, except that " +"each expression is evaluated at most once." +msgstr "" + +#: ../Doc/reference/expressions.rst:1088 +msgid "" +"Note that ``a op1 b op2 c`` doesn't imply any kind of comparison between *a* " +"and *c*, so that, e.g., ``x < y > z`` is perfectly legal (though perhaps not " +"pretty)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1093 +msgid "Value comparisons" +msgstr "" + +#: ../Doc/reference/expressions.rst:1095 +msgid "" +"The operators ``<``, ``>``, ``==``, ``>=``, ``<=``, and ``!=`` compare the " +"values of two objects. The objects do not need to have the same type." +msgstr "" + +#: ../Doc/reference/expressions.rst:1098 +msgid "" +"Chapter :ref:`objects` states that objects have a value (in addition to type " +"and identity). The value of an object is a rather abstract notion in " +"Python: For example, there is no canonical access method for an object's " +"value. Also, there is no requirement that the value of an object should be " +"constructed in a particular way, e.g. comprised of all its data attributes. " +"Comparison operators implement a particular notion of what the value of an " +"object is. One can think of them as defining the value of an object " +"indirectly, by means of their comparison implementation." +msgstr "" + +#: ../Doc/reference/expressions.rst:1107 +msgid "" +"Because all types are (direct or indirect) subtypes of :class:`object`, they " +"inherit the default comparison behavior from :class:`object`. Types can " +"customize their comparison behavior by implementing :dfn:`rich comparison " +"methods` like :meth:`__lt__`, described in :ref:`customization`." +msgstr "" + +#: ../Doc/reference/expressions.rst:1113 +msgid "" +"The default behavior for equality comparison (``==`` and ``!=``) is based on " +"the identity of the objects. Hence, equality comparison of instances with " +"the same identity results in equality, and equality comparison of instances " +"with different identities results in inequality. A motivation for this " +"default behavior is the desire that all objects should be reflexive (i.e. " +"``x is y`` implies ``x == y``)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1120 +msgid "" +"A default order comparison (``<``, ``>``, ``<=``, and ``>=``) is not " +"provided; an attempt raises :exc:`TypeError`. A motivation for this default " +"behavior is the lack of a similar invariant as for equality." +msgstr "" + +#: ../Doc/reference/expressions.rst:1124 +msgid "" +"The behavior of the default equality comparison, that instances with " +"different identities are always unequal, may be in contrast to what types " +"will need that have a sensible definition of object value and value-based " +"equality. Such types will need to customize their comparison behavior, and " +"in fact, a number of built-in types have done that." +msgstr "" + +#: ../Doc/reference/expressions.rst:1130 +msgid "" +"The following list describes the comparison behavior of the most important " +"built-in types." +msgstr "" + +#: ../Doc/reference/expressions.rst:1133 +msgid "" +"Numbers of built-in numeric types (:ref:`typesnumeric`) and of the standard " +"library types :class:`fractions.Fraction` and :class:`decimal.Decimal` can " +"be compared within and across their types, with the restriction that complex " +"numbers do not support order comparison. Within the limits of the types " +"involved, they compare mathematically (algorithmically) correct without loss " +"of precision." +msgstr "" + +#: ../Doc/reference/expressions.rst:1140 +msgid "" +"The not-a-number values :const:`float('NaN')` and :const:`Decimal('NaN')` " +"are special. They are identical to themselves (``x is x`` is true) but are " +"not equal to themselves (``x == x`` is false). Additionally, comparing any " +"number to a not-a-number value will return ``False``. For example, both ``3 " +"< float('NaN')`` and ``float('NaN') < 3`` will return ``False``." +msgstr "" + +#: ../Doc/reference/expressions.rst:1147 +msgid "" +"Binary sequences (instances of :class:`bytes` or :class:`bytearray`) can be " +"compared within and across their types. They compare lexicographically " +"using the numeric values of their elements." +msgstr "" + +#: ../Doc/reference/expressions.rst:1151 +msgid "" +"Strings (instances of :class:`str`) compare lexicographically using the " +"numerical Unicode code points (the result of the built-in function :func:" +"`ord`) of their characters. [#]_" +msgstr "" + +#: ../Doc/reference/expressions.rst:1155 +msgid "Strings and binary sequences cannot be directly compared." +msgstr "" + +#: ../Doc/reference/expressions.rst:1157 +msgid "" +"Sequences (instances of :class:`tuple`, :class:`list`, or :class:`range`) " +"can be compared only within each of their types, with the restriction that " +"ranges do not support order comparison. Equality comparison across these " +"types results in unequality, and ordering comparison across these types " +"raises :exc:`TypeError`." +msgstr "" + +#: ../Doc/reference/expressions.rst:1163 +msgid "" +"Sequences compare lexicographically using comparison of corresponding " +"elements, whereby reflexivity of the elements is enforced." +msgstr "" + +#: ../Doc/reference/expressions.rst:1166 +msgid "" +"In enforcing reflexivity of elements, the comparison of collections assumes " +"that for a collection element ``x``, ``x == x`` is always true. Based on " +"that assumption, element identity is compared first, and element comparison " +"is performed only for distinct elements. This approach yields the same " +"result as a strict element comparison would, if the compared elements are " +"reflexive. For non-reflexive elements, the result is different than for " +"strict element comparison, and may be surprising: The non-reflexive not-a-" +"number values for example result in the following comparison behavior when " +"used in a list::" +msgstr "" + +#: ../Doc/reference/expressions.rst:1184 +msgid "" +"Lexicographical comparison between built-in collections works as follows:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1186 +msgid "" +"For two collections to compare equal, they must be of the same type, have " +"the same length, and each pair of corresponding elements must compare equal " +"(for example, ``[1,2] == (1,2)`` is false because the type is not the same)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1191 +msgid "" +"Collections that support order comparison are ordered the same as their " +"first unequal elements (for example, ``[1,2,x] <= [1,2,y]`` has the same " +"value as ``x <= y``). If a corresponding element does not exist, the " +"shorter collection is ordered first (for example, ``[1,2] < [1,2,3]`` is " +"true)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1197 +msgid "" +"Mappings (instances of :class:`dict`) compare equal if and only if they have " +"equal `(key, value)` pairs. Equality comparison of the keys and elements " +"enforces reflexivity." +msgstr "" + +#: ../Doc/reference/expressions.rst:1201 +msgid "" +"Order comparisons (``<``, ``>``, ``<=``, and ``>=``) raise :exc:`TypeError`." +msgstr "" + +#: ../Doc/reference/expressions.rst:1203 +msgid "" +"Sets (instances of :class:`set` or :class:`frozenset`) can be compared " +"within and across their types." +msgstr "" + +#: ../Doc/reference/expressions.rst:1206 +msgid "" +"They define order comparison operators to mean subset and superset tests. " +"Those relations do not define total orderings (for example, the two sets " +"``{1,2}`` and ``{2,3}`` are not equal, nor subsets of one another, nor " +"supersets of one another). Accordingly, sets are not appropriate arguments " +"for functions which depend on total ordering (for example, :func:`min`, :" +"func:`max`, and :func:`sorted` produce undefined results given a list of " +"sets as inputs)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1214 +msgid "Comparison of sets enforces reflexivity of its elements." +msgstr "" + +#: ../Doc/reference/expressions.rst:1216 +msgid "" +"Most other built-in types have no comparison methods implemented, so they " +"inherit the default comparison behavior." +msgstr "" + +#: ../Doc/reference/expressions.rst:1219 +msgid "" +"User-defined classes that customize their comparison behavior should follow " +"some consistency rules, if possible:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1222 +msgid "" +"Equality comparison should be reflexive. In other words, identical objects " +"should compare equal:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1225 +msgid "``x is y`` implies ``x == y``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1227 +msgid "" +"Comparison should be symmetric. In other words, the following expressions " +"should have the same result:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1230 +msgid "``x == y`` and ``y == x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1232 +msgid "``x != y`` and ``y != x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1234 +msgid "``x < y`` and ``y > x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1236 +msgid "``x <= y`` and ``y >= x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1238 +msgid "" +"Comparison should be transitive. The following (non-exhaustive) examples " +"illustrate that:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1241 +msgid "``x > y and y > z`` implies ``x > z``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1243 +msgid "``x < y and y <= z`` implies ``x < z``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1245 +msgid "" +"Inverse comparison should result in the boolean negation. In other words, " +"the following expressions should have the same result:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1248 +msgid "``x == y`` and ``not x != y``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1250 +msgid "``x < y`` and ``not x >= y`` (for total ordering)" +msgstr "" + +#: ../Doc/reference/expressions.rst:1252 +msgid "``x > y`` and ``not x <= y`` (for total ordering)" +msgstr "" + +#: ../Doc/reference/expressions.rst:1254 +msgid "" +"The last two expressions apply to totally ordered collections (e.g. to " +"sequences, but not to sets or mappings). See also the :func:`~functools." +"total_ordering` decorator." +msgstr "" + +#: ../Doc/reference/expressions.rst:1258 +msgid "" +"Python does not enforce these consistency rules. In fact, the not-a-number " +"values are an example for not following these rules." +msgstr "" + +#: ../Doc/reference/expressions.rst:1267 +msgid "Membership test operations" +msgstr "" + +#: ../Doc/reference/expressions.rst:1269 +msgid "" +"The operators :keyword:`in` and :keyword:`not in` test for membership. ``x " +"in s`` evaluates to true if *x* is a member of *s*, and false otherwise. " +"``x not in s`` returns the negation of ``x in s``. All built-in sequences " +"and set types support this as well as dictionary, for which :keyword:`in` " +"tests whether the dictionary has a given key. For container types such as " +"list, tuple, set, frozenset, dict, or collections.deque, the expression ``x " +"in y`` is equivalent to ``any(x is e or x == e for e in y)``." +msgstr "" + +#: ../Doc/reference/expressions.rst:1277 +msgid "" +"For the string and bytes types, ``x in y`` is true if and only if *x* is a " +"substring of *y*. An equivalent test is ``y.find(x) != -1``. Empty strings " +"are always considered to be a substring of any other string, so ``\"\" in " +"\"abc\"`` will return ``True``." +msgstr "" + +#: ../Doc/reference/expressions.rst:1282 +msgid "" +"For user-defined classes which define the :meth:`__contains__` method, ``x " +"in y`` is true if and only if ``y.__contains__(x)`` is true." +msgstr "" + +#: ../Doc/reference/expressions.rst:1285 +msgid "" +"For user-defined classes which do not define :meth:`__contains__` but do " +"define :meth:`__iter__`, ``x in y`` is true if some value ``z`` with ``x == " +"z`` is produced while iterating over ``y``. If an exception is raised " +"during the iteration, it is as if :keyword:`in` raised that exception." +msgstr "" + +#: ../Doc/reference/expressions.rst:1290 +msgid "" +"Lastly, the old-style iteration protocol is tried: if a class defines :meth:" +"`__getitem__`, ``x in y`` is true if and only if there is a non-negative " +"integer index *i* such that ``x == y[i]``, and all lower integer indices do " +"not raise :exc:`IndexError` exception. (If any other exception is raised, " +"it is as if :keyword:`in` raised that exception)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1302 +msgid "" +"The operator :keyword:`not in` is defined to have the inverse true value of :" +"keyword:`in`." +msgstr "" + +#: ../Doc/reference/expressions.rst:1315 +msgid "Identity comparisons" +msgstr "" + +#: ../Doc/reference/expressions.rst:1317 +msgid "" +"The operators :keyword:`is` and :keyword:`is not` test for object identity: " +"``x is y`` is true if and only if *x* and *y* are the same object. Object " +"identity is determined using the :meth:`id` function. ``x is not y`` yields " +"the inverse truth value. [#]_" +msgstr "" + +#: ../Doc/reference/expressions.rst:1329 +msgid "Boolean operations" +msgstr "" + +#: ../Doc/reference/expressions.rst:1340 +msgid "" +"In the context of Boolean operations, and also when expressions are used by " +"control flow statements, the following values are interpreted as false: " +"``False``, ``None``, numeric zero of all types, and empty strings and " +"containers (including strings, tuples, lists, dictionaries, sets and " +"frozensets). All other values are interpreted as true. User-defined " +"objects can customize their truth value by providing a :meth:`__bool__` " +"method." +msgstr "" + +#: ../Doc/reference/expressions.rst:1349 +msgid "" +"The operator :keyword:`not` yields ``True`` if its argument is false, " +"``False`` otherwise." +msgstr "" + +#: ../Doc/reference/expressions.rst:1354 +msgid "" +"The expression ``x and y`` first evaluates *x*; if *x* is false, its value " +"is returned; otherwise, *y* is evaluated and the resulting value is returned." +msgstr "" + +#: ../Doc/reference/expressions.rst:1359 +msgid "" +"The expression ``x or y`` first evaluates *x*; if *x* is true, its value is " +"returned; otherwise, *y* is evaluated and the resulting value is returned." +msgstr "" + +#: ../Doc/reference/expressions.rst:1362 +msgid "" +"(Note that neither :keyword:`and` nor :keyword:`or` restrict the value and " +"type they return to ``False`` and ``True``, but rather return the last " +"evaluated argument. This is sometimes useful, e.g., if ``s`` is a string " +"that should be replaced by a default value if it is empty, the expression " +"``s or 'foo'`` yields the desired value. Because :keyword:`not` has to " +"create a new value, it returns a boolean value regardless of the type of its " +"argument (for example, ``not 'foo'`` produces ``False`` rather than ``''``.)" +msgstr "" + +#: ../Doc/reference/expressions.rst:1372 +msgid "Conditional expressions" +msgstr "" + +#: ../Doc/reference/expressions.rst:1383 +msgid "" +"Conditional expressions (sometimes called a \"ternary operator\") have the " +"lowest priority of all Python operations." +msgstr "" + +#: ../Doc/reference/expressions.rst:1386 +msgid "" +"The expression ``x if C else y`` first evaluates the condition, *C* rather " +"than *x*. If *C* is true, *x* is evaluated and its value is returned; " +"otherwise, *y* is evaluated and its value is returned." +msgstr "" + +#: ../Doc/reference/expressions.rst:1390 +msgid "See :pep:`308` for more details about conditional expressions." +msgstr "" + +#: ../Doc/reference/expressions.rst:1397 +msgid "Lambdas" +msgstr "" + +#: ../Doc/reference/expressions.rst:1408 +msgid "" +"Lambda expressions (sometimes called lambda forms) are used to create " +"anonymous functions. The expression ``lambda arguments: expression`` yields " +"a function object. The unnamed object behaves like a function object " +"defined with:" +msgstr "" + +#: ../Doc/reference/expressions.rst:1417 +msgid "" +"See section :ref:`function` for the syntax of parameter lists. Note that " +"functions created with lambda expressions cannot contain statements or " +"annotations." +msgstr "" + +#: ../Doc/reference/expressions.rst:1425 +msgid "Expression lists" +msgstr "" + +#: ../Doc/reference/expressions.rst:1437 +msgid "" +"Except when part of a list or set display, an expression list containing at " +"least one comma yields a tuple. The length of the tuple is the number of " +"expressions in the list. The expressions are evaluated from left to right." +msgstr "" + +#: ../Doc/reference/expressions.rst:1446 +msgid "" +"An asterisk ``*`` denotes :dfn:`iterable unpacking`. Its operand must be " +"an :term:`iterable`. The iterable is expanded into a sequence of items, " +"which are included in the new tuple, list, or set, at the site of the " +"unpacking." +msgstr "" + +#: ../Doc/reference/expressions.rst:1451 +msgid "" +"Iterable unpacking in expression lists, originally proposed by :pep:`448`." +msgstr "" + +#: ../Doc/reference/expressions.rst:1456 +msgid "" +"The trailing comma is required only to create a single tuple (a.k.a. a " +"*singleton*); it is optional in all other cases. A single expression " +"without a trailing comma doesn't create a tuple, but rather yields the value " +"of that expression. (To create an empty tuple, use an empty pair of " +"parentheses: ``()``.)" +msgstr "" + +#: ../Doc/reference/expressions.rst:1466 +msgid "Evaluation order" +msgstr "" + +#: ../Doc/reference/expressions.rst:1470 +msgid "" +"Python evaluates expressions from left to right. Notice that while " +"evaluating an assignment, the right-hand side is evaluated before the left-" +"hand side." +msgstr "" + +#: ../Doc/reference/expressions.rst:1473 +msgid "" +"In the following lines, expressions will be evaluated in the arithmetic " +"order of their suffixes::" +msgstr "" + +#: ../Doc/reference/expressions.rst:1487 +msgid "Operator precedence" +msgstr "" + +#: ../Doc/reference/expressions.rst:1491 +msgid "" +"The following table summarizes the operator precedence in Python, from " +"lowest precedence (least binding) to highest precedence (most binding). " +"Operators in the same box have the same precedence. Unless the syntax is " +"explicitly given, operators are binary. Operators in the same box group " +"left to right (except for exponentiation, which groups from right to left)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1497 +msgid "" +"Note that comparisons, membership tests, and identity tests, all have the " +"same precedence and have a left-to-right chaining feature as described in " +"the :ref:`comparisons` section." +msgstr "" + +#: ../Doc/reference/expressions.rst:1503 +msgid "Operator" +msgstr "" + +#: ../Doc/reference/expressions.rst:1503 +msgid "Description" +msgstr "" + +#: ../Doc/reference/expressions.rst:1505 +msgid ":keyword:`lambda`" +msgstr "" + +#: ../Doc/reference/expressions.rst:1505 +msgid "Lambda expression" +msgstr "" + +#: ../Doc/reference/expressions.rst:1507 +msgid ":keyword:`if` -- :keyword:`else`" +msgstr "" + +#: ../Doc/reference/expressions.rst:1507 +msgid "Conditional expression" +msgstr "" + +#: ../Doc/reference/expressions.rst:1509 +msgid ":keyword:`or`" +msgstr "" + +#: ../Doc/reference/expressions.rst:1509 +msgid "Boolean OR" +msgstr "" + +#: ../Doc/reference/expressions.rst:1511 +msgid ":keyword:`and`" +msgstr "" + +#: ../Doc/reference/expressions.rst:1511 +msgid "Boolean AND" +msgstr "" + +#: ../Doc/reference/expressions.rst:1513 +msgid ":keyword:`not` ``x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1513 +msgid "Boolean NOT" +msgstr "" + +#: ../Doc/reference/expressions.rst:1515 +msgid "" +":keyword:`in`, :keyword:`not in`, :keyword:`is`, :keyword:`is not`, ``<``, " +"``<=``, ``>``, ``>=``, ``!=``, ``==``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1515 +msgid "Comparisons, including membership tests and identity tests" +msgstr "" + +#: ../Doc/reference/expressions.rst:1519 +msgid "``|``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1519 +msgid "Bitwise OR" +msgstr "" + +#: ../Doc/reference/expressions.rst:1521 +msgid "``^``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1521 +msgid "Bitwise XOR" +msgstr "" + +#: ../Doc/reference/expressions.rst:1523 +msgid "``&``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1523 +msgid "Bitwise AND" +msgstr "" + +#: ../Doc/reference/expressions.rst:1525 +msgid "``<<``, ``>>``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1525 +msgid "Shifts" +msgstr "" + +#: ../Doc/reference/expressions.rst:1527 +msgid "``+``, ``-``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1527 +msgid "Addition and subtraction" +msgstr "" + +#: ../Doc/reference/expressions.rst:1529 +msgid "``*``, ``@``, ``/``, ``//``, ``%``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1529 +msgid "Multiplication, matrix multiplication division, remainder [#]_" +msgstr "" + +#: ../Doc/reference/expressions.rst:1533 +msgid "``+x``, ``-x``, ``~x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1533 +msgid "Positive, negative, bitwise NOT" +msgstr "" + +#: ../Doc/reference/expressions.rst:1535 +msgid "``**``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1535 +msgid "Exponentiation [#]_" +msgstr "" + +#: ../Doc/reference/expressions.rst:1537 +msgid "``await`` ``x``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1539 +msgid "``x[index]``, ``x[index:index]``, ``x(arguments...)``, ``x.attribute``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1539 +msgid "Subscription, slicing, call, attribute reference" +msgstr "" + +#: ../Doc/reference/expressions.rst:1542 +msgid "" +"``(expressions...)``, ``[expressions...]``, ``{key: value...}``, " +"``{expressions...}``" +msgstr "" + +#: ../Doc/reference/expressions.rst:1542 +msgid "Binding or tuple display, list display, dictionary display, set display" +msgstr "" + +#: ../Doc/reference/expressions.rst:1551 +msgid "" +"While ``abs(x%y) < abs(y)`` is true mathematically, for floats it may not be " +"true numerically due to roundoff. For example, and assuming a platform on " +"which a Python float is an IEEE 754 double-precision number, in order that " +"``-1e-100 % 1e100`` have the same sign as ``1e100``, the computed result is " +"``-1e-100 + 1e100``, which is numerically exactly equal to ``1e100``. The " +"function :func:`math.fmod` returns a result whose sign matches the sign of " +"the first argument instead, and so returns ``-1e-100`` in this case. Which " +"approach is more appropriate depends on the application." +msgstr "" + +#: ../Doc/reference/expressions.rst:1560 +msgid "" +"If x is very close to an exact integer multiple of y, it's possible for ``x//" +"y`` to be one larger than ``(x-x%y)//y`` due to rounding. In such cases, " +"Python returns the latter result, in order to preserve that ``divmod(x,y)[0] " +"* y + x % y`` be very close to ``x``." +msgstr "" + +#: ../Doc/reference/expressions.rst:1565 +msgid "" +"The Unicode standard distinguishes between :dfn:`code points` (e.g. U+0041) " +"and :dfn:`abstract characters` (e.g. \"LATIN CAPITAL LETTER A\"). While most " +"abstract characters in Unicode are only represented using one code point, " +"there is a number of abstract characters that can in addition be represented " +"using a sequence of more than one code point. For example, the abstract " +"character \"LATIN CAPITAL LETTER C WITH CEDILLA\" can be represented as a " +"single :dfn:`precomposed character` at code position U+00C7, or as a " +"sequence of a :dfn:`base character` at code position U+0043 (LATIN CAPITAL " +"LETTER C), followed by a :dfn:`combining character` at code position U+0327 " +"(COMBINING CEDILLA)." +msgstr "" + +#: ../Doc/reference/expressions.rst:1576 +msgid "" +"The comparison operators on strings compare at the level of Unicode code " +"points. This may be counter-intuitive to humans. For example, ``\"\\u00C7\" " +"== \"\\u0043\\u0327\"`` is ``False``, even though both strings represent the " +"same abstract character \"LATIN CAPITAL LETTER C WITH CEDILLA\"." +msgstr "" + +#: ../Doc/reference/expressions.rst:1581 +msgid "" +"To compare strings at the level of abstract characters (that is, in a way " +"intuitive to humans), use :func:`unicodedata.normalize`." +msgstr "" + +#: ../Doc/reference/expressions.rst:1584 +msgid "" +"Due to automatic garbage-collection, free lists, and the dynamic nature of " +"descriptors, you may notice seemingly unusual behaviour in certain uses of " +"the :keyword:`is` operator, like those involving comparisons between " +"instance methods, or constants. Check their documentation for more info." +msgstr "" + +#: ../Doc/reference/expressions.rst:1589 +msgid "" +"The ``%`` operator is also used for string formatting; the same precedence " +"applies." +msgstr "" + +#: ../Doc/reference/expressions.rst:1592 +msgid "" +"The power operator ``**`` binds less tightly than an arithmetic or bitwise " +"unary operator on its right, that is, ``2**-1`` is ``0.5``." +msgstr "" + +#: ../Doc/reference/grammar.rst:2 +msgid "Full Grammar specification" +msgstr "" + +#: ../Doc/reference/grammar.rst:4 +msgid "" +"This is the full Python grammar, as it is read by the parser generator and " +"used to parse Python source files:" +msgstr "" + +#: ../Doc/reference/import.rst:6 +msgid "The import system" +msgstr "" + +#: ../Doc/reference/import.rst:10 +msgid "" +"Python code in one :term:`module` gains access to the code in another module " +"by the process of :term:`importing` it. The :keyword:`import` statement is " +"the most common way of invoking the import machinery, but it is not the only " +"way. Functions such as :func:`importlib.import_module` and built-in :func:" +"`__import__` can also be used to invoke the import machinery." +msgstr "" + +#: ../Doc/reference/import.rst:16 +msgid "" +"The :keyword:`import` statement combines two operations; it searches for the " +"named module, then it binds the results of that search to a name in the " +"local scope. The search operation of the :keyword:`import` statement is " +"defined as a call to the :func:`__import__` function, with the appropriate " +"arguments. The return value of :func:`__import__` is used to perform the " +"name binding operation of the :keyword:`import` statement. See the :keyword:" +"`import` statement for the exact details of that name binding operation." +msgstr "" + +#: ../Doc/reference/import.rst:25 +msgid "" +"A direct call to :func:`__import__` performs only the module search and, if " +"found, the module creation operation. While certain side-effects may occur, " +"such as the importing of parent packages, and the updating of various caches " +"(including :data:`sys.modules`), only the :keyword:`import` statement " +"performs a name binding operation." +msgstr "" + +#: ../Doc/reference/import.rst:31 +msgid "" +"When calling :func:`__import__` as part of an import statement, the standard " +"builtin :func:`__import__` is called. Other mechanisms for invoking the " +"import system (such as :func:`importlib.import_module`) may choose to " +"subvert :func:`__import__` and use its own solution to implement import " +"semantics." +msgstr "" + +#: ../Doc/reference/import.rst:37 +msgid "" +"When a module is first imported, Python searches for the module and if " +"found, it creates a module object [#fnmo]_, initializing it. If the named " +"module cannot be found, an :exc:`ModuleNotFoundError` is raised. Python " +"implements various strategies to search for the named module when the import " +"machinery is invoked. These strategies can be modified and extended by " +"using various hooks described in the sections below." +msgstr "" + +#: ../Doc/reference/import.rst:44 +msgid "" +"The import system has been updated to fully implement the second phase of :" +"pep:`302`. There is no longer any implicit import machinery - the full " +"import system is exposed through :data:`sys.meta_path`. In addition, native " +"namespace package support has been implemented (see :pep:`420`)." +msgstr "" + +#: ../Doc/reference/import.rst:52 +msgid ":mod:`importlib`" +msgstr "" + +#: ../Doc/reference/import.rst:54 +msgid "" +"The :mod:`importlib` module provides a rich API for interacting with the " +"import system. For example :func:`importlib.import_module` provides a " +"recommended, simpler API than built-in :func:`__import__` for invoking the " +"import machinery. Refer to the :mod:`importlib` library documentation for " +"additional detail." +msgstr "" + +#: ../Doc/reference/import.rst:63 +msgid "Packages" +msgstr "" + +#: ../Doc/reference/import.rst:68 +msgid "" +"Python has only one type of module object, and all modules are of this type, " +"regardless of whether the module is implemented in Python, C, or something " +"else. To help organize modules and provide a naming hierarchy, Python has a " +"concept of :term:`packages `." +msgstr "" + +#: ../Doc/reference/import.rst:73 +msgid "" +"You can think of packages as the directories on a file system and modules as " +"files within directories, but don't take this analogy too literally since " +"packages and modules need not originate from the file system. For the " +"purposes of this documentation, we'll use this convenient analogy of " +"directories and files. Like file system directories, packages are organized " +"hierarchically, and packages may themselves contain subpackages, as well as " +"regular modules." +msgstr "" + +#: ../Doc/reference/import.rst:81 +msgid "" +"It's important to keep in mind that all packages are modules, but not all " +"modules are packages. Or put another way, packages are just a special kind " +"of module. Specifically, any module that contains a ``__path__`` attribute " +"is considered a package." +msgstr "" + +#: ../Doc/reference/import.rst:86 +msgid "" +"All modules have a name. Subpackage names are separated from their parent " +"package name by dots, akin to Python's standard attribute access syntax. " +"Thus you might have a module called :mod:`sys` and a package called :mod:" +"`email`, which in turn has a subpackage called :mod:`email.mime` and a " +"module within that subpackage called :mod:`email.mime.text`." +msgstr "" + +#: ../Doc/reference/import.rst:94 +msgid "Regular packages" +msgstr "" + +#: ../Doc/reference/import.rst:99 +msgid "" +"Python defines two types of packages, :term:`regular packages ` and :term:`namespace packages `. Regular " +"packages are traditional packages as they existed in Python 3.2 and earlier. " +"A regular package is typically implemented as a directory containing an " +"``__init__.py`` file. When a regular package is imported, this ``__init__." +"py`` file is implicitly executed, and the objects it defines are bound to " +"names in the package's namespace. The ``__init__.py`` file can contain the " +"same Python code that any other module can contain, and Python will add some " +"additional attributes to the module when it is imported." +msgstr "" + +#: ../Doc/reference/import.rst:109 +msgid "" +"For example, the following file system layout defines a top level ``parent`` " +"package with three subpackages::" +msgstr "" + +#: ../Doc/reference/import.rst:121 +msgid "" +"Importing ``parent.one`` will implicitly execute ``parent/__init__.py`` and " +"``parent/one/__init__.py``. Subsequent imports of ``parent.two`` or " +"``parent.three`` will execute ``parent/two/__init__.py`` and ``parent/three/" +"__init__.py`` respectively." +msgstr "" + +#: ../Doc/reference/import.rst:128 +msgid "Namespace packages" +msgstr "" + +#: ../Doc/reference/import.rst:134 +msgid "" +"A namespace package is a composite of various :term:`portions `, " +"where each portion contributes a subpackage to the parent package. Portions " +"may reside in different locations on the file system. Portions may also be " +"found in zip files, on the network, or anywhere else that Python searches " +"during import. Namespace packages may or may not correspond directly to " +"objects on the file system; they may be virtual modules that have no " +"concrete representation." +msgstr "" + +#: ../Doc/reference/import.rst:142 +msgid "" +"Namespace packages do not use an ordinary list for their ``__path__`` " +"attribute. They instead use a custom iterable type which will automatically " +"perform a new search for package portions on the next import attempt within " +"that package if the path of their parent package (or :data:`sys.path` for a " +"top level package) changes." +msgstr "" + +#: ../Doc/reference/import.rst:148 +msgid "" +"With namespace packages, there is no ``parent/__init__.py`` file. In fact, " +"there may be multiple ``parent`` directories found during import search, " +"where each one is provided by a different portion. Thus ``parent/one`` may " +"not be physically located next to ``parent/two``. In this case, Python will " +"create a namespace package for the top-level ``parent`` package whenever it " +"or one of its subpackages is imported." +msgstr "" + +#: ../Doc/reference/import.rst:155 +msgid "See also :pep:`420` for the namespace package specification." +msgstr "" + +#: ../Doc/reference/import.rst:159 +msgid "Searching" +msgstr "" + +#: ../Doc/reference/import.rst:161 +msgid "" +"To begin the search, Python needs the :term:`fully qualified ` name of the module (or package, but for the purposes of this " +"discussion, the difference is immaterial) being imported. This name may " +"come from various arguments to the :keyword:`import` statement, or from the " +"parameters to the :func:`importlib.import_module` or :func:`__import__` " +"functions." +msgstr "" + +#: ../Doc/reference/import.rst:167 +msgid "" +"This name will be used in various phases of the import search, and it may be " +"the dotted path to a submodule, e.g. ``foo.bar.baz``. In this case, Python " +"first tries to import ``foo``, then ``foo.bar``, and finally ``foo.bar." +"baz``. If any of the intermediate imports fail, an :exc:" +"`ModuleNotFoundError` is raised." +msgstr "" + +#: ../Doc/reference/import.rst:174 +msgid "The module cache" +msgstr "" + +#: ../Doc/reference/import.rst:179 +msgid "" +"The first place checked during import search is :data:`sys.modules`. This " +"mapping serves as a cache of all modules that have been previously imported, " +"including the intermediate paths. So if ``foo.bar.baz`` was previously " +"imported, :data:`sys.modules` will contain entries for ``foo``, ``foo.bar``, " +"and ``foo.bar.baz``. Each key will have as its value the corresponding " +"module object." +msgstr "" + +#: ../Doc/reference/import.rst:186 +msgid "" +"During import, the module name is looked up in :data:`sys.modules` and if " +"present, the associated value is the module satisfying the import, and the " +"process completes. However, if the value is ``None``, then an :exc:" +"`ModuleNotFoundError` is raised. If the module name is missing, Python will " +"continue searching for the module." +msgstr "" + +#: ../Doc/reference/import.rst:192 +msgid "" +":data:`sys.modules` is writable. Deleting a key may not destroy the " +"associated module (as other modules may hold references to it), but it will " +"invalidate the cache entry for the named module, causing Python to search " +"anew for the named module upon its next import. The key can also be assigned " +"to ``None``, forcing the next import of the module to result in an :exc:" +"`ModuleNotFoundError`." +msgstr "" + +#: ../Doc/reference/import.rst:199 +msgid "" +"Beware though, as if you keep a reference to the module object, invalidate " +"its cache entry in :data:`sys.modules`, and then re-import the named module, " +"the two module objects will *not* be the same. By contrast, :func:`importlib." +"reload` will reuse the *same* module object, and simply reinitialise the " +"module contents by rerunning the module's code." +msgstr "" + +#: ../Doc/reference/import.rst:207 +msgid "Finders and loaders" +msgstr "" + +#: ../Doc/reference/import.rst:214 +msgid "" +"If the named module is not found in :data:`sys.modules`, then Python's " +"import protocol is invoked to find and load the module. This protocol " +"consists of two conceptual objects, :term:`finders ` and :term:" +"`loaders `. A finder's job is to determine whether it can find the " +"named module using whatever strategy it knows about. Objects that implement " +"both of these interfaces are referred to as :term:`importers ` - " +"they return themselves when they find that they can load the requested " +"module." +msgstr "" + +#: ../Doc/reference/import.rst:222 +msgid "" +"Python includes a number of default finders and importers. The first one " +"knows how to locate built-in modules, and the second knows how to locate " +"frozen modules. A third default finder searches an :term:`import path` for " +"modules. The :term:`import path` is a list of locations that may name file " +"system paths or zip files. It can also be extended to search for any " +"locatable resource, such as those identified by URLs." +msgstr "" + +#: ../Doc/reference/import.rst:229 +msgid "" +"The import machinery is extensible, so new finders can be added to extend " +"the range and scope of module searching." +msgstr "" + +#: ../Doc/reference/import.rst:232 +msgid "" +"Finders do not actually load modules. If they can find the named module, " +"they return a :dfn:`module spec`, an encapsulation of the module's import-" +"related information, which the import machinery then uses when loading the " +"module." +msgstr "" + +#: ../Doc/reference/import.rst:236 +msgid "" +"The following sections describe the protocol for finders and loaders in more " +"detail, including how you can create and register new ones to extend the " +"import machinery." +msgstr "" + +#: ../Doc/reference/import.rst:240 +msgid "" +"In previous versions of Python, finders returned :term:`loaders ` " +"directly, whereas now they return module specs which *contain* loaders. " +"Loaders are still used during import but have fewer responsibilities." +msgstr "" + +#: ../Doc/reference/import.rst:246 +msgid "Import hooks" +msgstr "" + +#: ../Doc/reference/import.rst:256 +msgid "" +"The import machinery is designed to be extensible; the primary mechanism for " +"this are the *import hooks*. There are two types of import hooks: *meta " +"hooks* and *import path hooks*." +msgstr "" + +#: ../Doc/reference/import.rst:260 +msgid "" +"Meta hooks are called at the start of import processing, before any other " +"import processing has occurred, other than :data:`sys.modules` cache look " +"up. This allows meta hooks to override :data:`sys.path` processing, frozen " +"modules, or even built-in modules. Meta hooks are registered by adding new " +"finder objects to :data:`sys.meta_path`, as described below." +msgstr "" + +#: ../Doc/reference/import.rst:266 +msgid "" +"Import path hooks are called as part of :data:`sys.path` (or ``package." +"__path__``) processing, at the point where their associated path item is " +"encountered. Import path hooks are registered by adding new callables to :" +"data:`sys.path_hooks` as described below." +msgstr "" + +#: ../Doc/reference/import.rst:273 +msgid "The meta path" +msgstr "" + +#: ../Doc/reference/import.rst:279 +msgid "" +"When the named module is not found in :data:`sys.modules`, Python next " +"searches :data:`sys.meta_path`, which contains a list of meta path finder " +"objects. These finders are queried in order to see if they know how to " +"handle the named module. Meta path finders must implement a method called :" +"meth:`~importlib.abc.MetaPathFinder.find_spec()` which takes three " +"arguments: a name, an import path, and (optionally) a target module. The " +"meta path finder can use any strategy it wants to determine whether it can " +"handle the named module or not." +msgstr "" + +#: ../Doc/reference/import.rst:288 +msgid "" +"If the meta path finder knows how to handle the named module, it returns a " +"spec object. If it cannot handle the named module, it returns ``None``. " +"If :data:`sys.meta_path` processing reaches the end of its list without " +"returning a spec, then a :exc:`ModuleNotFoundError` is raised. Any other " +"exceptions raised are simply propagated up, aborting the import process." +msgstr "" + +#: ../Doc/reference/import.rst:294 +msgid "" +"The :meth:`~importlib.abc.MetaPathFinder.find_spec()` method of meta path " +"finders is called with two or three arguments. The first is the fully " +"qualified name of the module being imported, for example ``foo.bar.baz``. " +"The second argument is the path entries to use for the module search. For " +"top-level modules, the second argument is ``None``, but for submodules or " +"subpackages, the second argument is the value of the parent package's " +"``__path__`` attribute. If the appropriate ``__path__`` attribute cannot be " +"accessed, an :exc:`ModuleNotFoundError` is raised. The third argument is an " +"existing module object that will be the target of loading later. The import " +"system passes in a target module only during reload." +msgstr "" + +#: ../Doc/reference/import.rst:305 +msgid "" +"The meta path may be traversed multiple times for a single import request. " +"For example, assuming none of the modules involved has already been cached, " +"importing ``foo.bar.baz`` will first perform a top level import, calling " +"``mpf.find_spec(\"foo\", None, None)`` on each meta path finder (``mpf``). " +"After ``foo`` has been imported, ``foo.bar`` will be imported by traversing " +"the meta path a second time, calling ``mpf.find_spec(\"foo.bar\", foo." +"__path__, None)``. Once ``foo.bar`` has been imported, the final traversal " +"will call ``mpf.find_spec(\"foo.bar.baz\", foo.bar.__path__, None)``." +msgstr "" + +#: ../Doc/reference/import.rst:315 +msgid "" +"Some meta path finders only support top level imports. These importers will " +"always return ``None`` when anything other than ``None`` is passed as the " +"second argument." +msgstr "" + +#: ../Doc/reference/import.rst:319 +msgid "" +"Python's default :data:`sys.meta_path` has three meta path finders, one that " +"knows how to import built-in modules, one that knows how to import frozen " +"modules, and one that knows how to import modules from an :term:`import " +"path` (i.e. the :term:`path based finder`)." +msgstr "" + +#: ../Doc/reference/import.rst:324 +msgid "" +"The :meth:`~importlib.abc.MetaPathFinder.find_spec` method of meta path " +"finders replaced :meth:`~importlib.abc.MetaPathFinder.find_module`, which is " +"now deprecated. While it will continue to work without change, the import " +"machinery will try it only if the finder does not implement ``find_spec()``." +msgstr "" + +#: ../Doc/reference/import.rst:333 +msgid "Loading" +msgstr "" + +#: ../Doc/reference/import.rst:335 +msgid "" +"If and when a module spec is found, the import machinery will use it (and " +"the loader it contains) when loading the module. Here is an approximation " +"of what happens during the loading portion of import::" +msgstr "" + +#: ../Doc/reference/import.rst:370 +msgid "Note the following details:" +msgstr "" + +#: ../Doc/reference/import.rst:372 +msgid "" +"If there is an existing module object with the given name in :data:`sys." +"modules`, import will have already returned it." +msgstr "" + +#: ../Doc/reference/import.rst:375 +msgid "" +"The module will exist in :data:`sys.modules` before the loader executes the " +"module code. This is crucial because the module code may (directly or " +"indirectly) import itself; adding it to :data:`sys.modules` beforehand " +"prevents unbounded recursion in the worst case and multiple loading in the " +"best." +msgstr "" + +#: ../Doc/reference/import.rst:381 +msgid "" +"If loading fails, the failing module -- and only the failing module -- gets " +"removed from :data:`sys.modules`. Any module already in the :data:`sys." +"modules` cache, and any module that was successfully loaded as a side-" +"effect, must remain in the cache. This contrasts with reloading where even " +"the failing module is left in :data:`sys.modules`." +msgstr "" + +#: ../Doc/reference/import.rst:387 +msgid "" +"After the module is created but before execution, the import machinery sets " +"the import-related module attributes (\"_init_module_attrs\" in the pseudo-" +"code example above), as summarized in a :ref:`later section `." +msgstr "" + +#: ../Doc/reference/import.rst:392 +msgid "" +"Module execution is the key moment of loading in which the module's " +"namespace gets populated. Execution is entirely delegated to the loader, " +"which gets to decide what gets populated and how." +msgstr "" + +#: ../Doc/reference/import.rst:396 +msgid "" +"The module created during loading and passed to exec_module() may not be the " +"one returned at the end of import [#fnlo]_." +msgstr "" + +#: ../Doc/reference/import.rst:399 +msgid "" +"The import system has taken over the boilerplate responsibilities of " +"loaders. These were previously performed by the :meth:`importlib.abc.Loader." +"load_module` method." +msgstr "" + +#: ../Doc/reference/import.rst:405 +msgid "Loaders" +msgstr "" + +#: ../Doc/reference/import.rst:407 +msgid "" +"Module loaders provide the critical function of loading: module execution. " +"The import machinery calls the :meth:`importlib.abc.Loader.exec_module` " +"method with a single argument, the module object to execute. Any value " +"returned from :meth:`~importlib.abc.Loader.exec_module` is ignored." +msgstr "" + +#: ../Doc/reference/import.rst:412 +msgid "Loaders must satisfy the following requirements:" +msgstr "" + +#: ../Doc/reference/import.rst:414 +msgid "" +"If the module is a Python module (as opposed to a built-in module or a " +"dynamically loaded extension), the loader should execute the module's code " +"in the module's global name space (``module.__dict__``)." +msgstr "" + +#: ../Doc/reference/import.rst:418 +msgid "" +"If the loader cannot execute the module, it should raise an :exc:" +"`ImportError`, although any other exception raised during :meth:`~importlib." +"abc.Loader.exec_module` will be propagated." +msgstr "" + +#: ../Doc/reference/import.rst:422 +msgid "" +"In many cases, the finder and loader can be the same object; in such cases " +"the :meth:`~importlib.abc.MetaPathFinder.find_spec` method would just return " +"a spec with the loader set to ``self``." +msgstr "" + +#: ../Doc/reference/import.rst:426 +msgid "" +"Module loaders may opt in to creating the module object during loading by " +"implementing a :meth:`~importlib.abc.Loader.create_module` method. It takes " +"one argument, the module spec, and returns the new module object to use " +"during loading. ``create_module()`` does not need to set any attributes on " +"the module object. If the method returns ``None``, the import machinery " +"will create the new module itself." +msgstr "" + +#: ../Doc/reference/import.rst:433 +msgid "The create_module() method of loaders." +msgstr "" + +#: ../Doc/reference/import.rst:436 +msgid "" +"The :meth:`~importlib.abc.Loader.load_module` method was replaced by :meth:" +"`~importlib.abc.Loader.exec_module` and the import machinery assumed all the " +"boilerplate responsibilities of loading." +msgstr "" + +#: ../Doc/reference/import.rst:441 +msgid "" +"For compatibility with existing loaders, the import machinery will use the " +"``load_module()`` method of loaders if it exists and the loader does not " +"also implement ``exec_module()``. However, ``load_module()`` has been " +"deprecated and loaders should implement ``exec_module()`` instead." +msgstr "" + +#: ../Doc/reference/import.rst:446 +msgid "" +"The ``load_module()`` method must implement all the boilerplate loading " +"functionality described above in addition to executing the module. All the " +"same constraints apply, with some additional clarification:" +msgstr "" + +#: ../Doc/reference/import.rst:450 +msgid "" +"If there is an existing module object with the given name in :data:`sys." +"modules`, the loader must use that existing module. (Otherwise, :func:" +"`importlib.reload` will not work correctly.) If the named module does not " +"exist in :data:`sys.modules`, the loader must create a new module object and " +"add it to :data:`sys.modules`." +msgstr "" + +#: ../Doc/reference/import.rst:456 +msgid "" +"The module *must* exist in :data:`sys.modules` before the loader executes " +"the module code, to prevent unbounded recursion or multiple loading." +msgstr "" + +#: ../Doc/reference/import.rst:460 +msgid "" +"If loading fails, the loader must remove any modules it has inserted into :" +"data:`sys.modules`, but it must remove **only** the failing module(s), and " +"only if the loader itself has loaded the module(s) explicitly." +msgstr "" + +#: ../Doc/reference/import.rst:465 +msgid "" +"A :exc:`DeprecationWarning` is raised when ``exec_module()`` is defined but " +"``create_module()`` is not. Starting in Python 3.6 it will be an error to " +"not define ``create_module()`` on a loader attached to a ModuleSpec." +msgstr "" + +#: ../Doc/reference/import.rst:471 +msgid "Submodules" +msgstr "" + +#: ../Doc/reference/import.rst:473 +msgid "" +"When a submodule is loaded using any mechanism (e.g. ``importlib`` APIs, the " +"``import`` or ``import-from`` statements, or built-in ``__import__()``) a " +"binding is placed in the parent module's namespace to the submodule object. " +"For example, if package ``spam`` has a submodule ``foo``, after importing " +"``spam.foo``, ``spam`` will have an attribute ``foo`` which is bound to the " +"submodule. Let's say you have the following directory structure::" +msgstr "" + +#: ../Doc/reference/import.rst:485 +msgid "and ``spam/__init__.py`` has the following lines in it::" +msgstr "" + +#: ../Doc/reference/import.rst:490 +msgid "" +"then executing the following puts a name binding to ``foo`` and ``bar`` in " +"the ``spam`` module::" +msgstr "" + +#: ../Doc/reference/import.rst:499 +msgid "" +"Given Python's familiar name binding rules this might seem surprising, but " +"it's actually a fundamental feature of the import system. The invariant " +"holding is that if you have ``sys.modules['spam']`` and ``sys.modules['spam." +"foo']`` (as you would after the above import), the latter must appear as the " +"``foo`` attribute of the former." +msgstr "" + +#: ../Doc/reference/import.rst:506 +msgid "Module spec" +msgstr "" + +#: ../Doc/reference/import.rst:508 +msgid "" +"The import machinery uses a variety of information about each module during " +"import, especially before loading. Most of the information is common to all " +"modules. The purpose of a module's spec is to encapsulate this import-" +"related information on a per-module basis." +msgstr "" + +#: ../Doc/reference/import.rst:513 +msgid "" +"Using a spec during import allows state to be transferred between import " +"system components, e.g. between the finder that creates the module spec and " +"the loader that executes it. Most importantly, it allows the import " +"machinery to perform the boilerplate operations of loading, whereas without " +"a module spec the loader had that responsibility." +msgstr "" + +#: ../Doc/reference/import.rst:519 +msgid "" +"See :class:`~importlib.machinery.ModuleSpec` for more specifics on what " +"information a module's spec may hold." +msgstr "" + +#: ../Doc/reference/import.rst:527 +msgid "Import-related module attributes" +msgstr "" + +#: ../Doc/reference/import.rst:529 +msgid "" +"The import machinery fills in these attributes on each module object during " +"loading, based on the module's spec, before the loader executes the module." +msgstr "" + +#: ../Doc/reference/import.rst:535 +msgid "" +"The ``__name__`` attribute must be set to the fully-qualified name of the " +"module. This name is used to uniquely identify the module in the import " +"system." +msgstr "" + +#: ../Doc/reference/import.rst:541 +msgid "" +"The ``__loader__`` attribute must be set to the loader object that the " +"import machinery used when loading the module. This is mostly for " +"introspection, but can be used for additional loader-specific functionality, " +"for example getting data associated with a loader." +msgstr "" + +#: ../Doc/reference/import.rst:548 +msgid "" +"The module's ``__package__`` attribute must be set. Its value must be a " +"string, but it can be the same value as its ``__name__``. When the module " +"is a package, its ``__package__`` value should be set to its ``__name__``. " +"When the module is not a package, ``__package__`` should be set to the empty " +"string for top-level modules, or for submodules, to the parent package's " +"name. See :pep:`366` for further details." +msgstr "" + +#: ../Doc/reference/import.rst:556 +msgid "" +"This attribute is used instead of ``__name__`` to calculate explicit " +"relative imports for main modules, as defined in :pep:`366`. It is expected " +"to have the same value as ``__spec__.parent``." +msgstr "" + +#: ../Doc/reference/import.rst:560 +msgid "" +"The value of ``__package__`` is expected to be the same as ``__spec__." +"parent``." +msgstr "" + +#: ../Doc/reference/import.rst:566 +msgid "" +"The ``__spec__`` attribute must be set to the module spec that was used when " +"importing the module. Setting ``__spec__`` appropriately applies equally to :" +"ref:`modules initialized during interpreter startup `. The one " +"exception is ``__main__``, where ``__spec__`` is :ref:`set to None in some " +"cases `." +msgstr "" + +#: ../Doc/reference/import.rst:572 +msgid "" +"When ``__package__`` is not defined, ``__spec__.parent`` is used as a " +"fallback." +msgstr "" + +#: ../Doc/reference/import.rst:577 +msgid "" +"``__spec__.parent`` is used as a fallback when ``__package__`` is not " +"defined." +msgstr "" + +#: ../Doc/reference/import.rst:583 +msgid "" +"If the module is a package (either regular or namespace), the module " +"object's ``__path__`` attribute must be set. The value must be iterable, " +"but may be empty if ``__path__`` has no further significance. If " +"``__path__`` is not empty, it must produce strings when iterated over. More " +"details on the semantics of ``__path__`` are given :ref:`below `." +msgstr "" + +#: ../Doc/reference/import.rst:590 +msgid "Non-package modules should not have a ``__path__`` attribute." +msgstr "" + +#: ../Doc/reference/import.rst:595 +msgid "" +"``__file__`` is optional. If set, this attribute's value must be a string. " +"The import system may opt to leave ``__file__`` unset if it has no semantic " +"meaning (e.g. a module loaded from a database)." +msgstr "" + +#: ../Doc/reference/import.rst:599 +msgid "" +"If ``__file__`` is set, it may also be appropriate to set the ``__cached__`` " +"attribute which is the path to any compiled version of the code (e.g. byte-" +"compiled file). The file does not need to exist to set this attribute; the " +"path can simply point to where the compiled file would exist (see :pep:" +"`3147`)." +msgstr "" + +#: ../Doc/reference/import.rst:605 +msgid "" +"It is also appropriate to set ``__cached__`` when ``__file__`` is not set. " +"However, that scenario is quite atypical. Ultimately, the loader is what " +"makes use of ``__file__`` and/or ``__cached__``. So if a loader can load " +"from a cached module but otherwise does not load from a file, that atypical " +"scenario may be appropriate." +msgstr "" + +#: ../Doc/reference/import.rst:614 +msgid "module.__path__" +msgstr "" + +#: ../Doc/reference/import.rst:616 +msgid "" +"By definition, if a module has an ``__path__`` attribute, it is a package, " +"regardless of its value." +msgstr "" + +#: ../Doc/reference/import.rst:619 +msgid "" +"A package's ``__path__`` attribute is used during imports of its " +"subpackages. Within the import machinery, it functions much the same as :" +"data:`sys.path`, i.e. providing a list of locations to search for modules " +"during import. However, ``__path__`` is typically much more constrained " +"than :data:`sys.path`." +msgstr "" + +#: ../Doc/reference/import.rst:625 +msgid "" +"``__path__`` must be an iterable of strings, but it may be empty. The same " +"rules used for :data:`sys.path` also apply to a package's ``__path__``, and :" +"data:`sys.path_hooks` (described below) are consulted when traversing a " +"package's ``__path__``." +msgstr "" + +#: ../Doc/reference/import.rst:630 +msgid "" +"A package's ``__init__.py`` file may set or alter the package's ``__path__`` " +"attribute, and this was typically the way namespace packages were " +"implemented prior to :pep:`420`. With the adoption of :pep:`420`, namespace " +"packages no longer need to supply ``__init__.py`` files containing only " +"``__path__`` manipulation code; the import machinery automatically sets " +"``__path__`` correctly for the namespace package." +msgstr "" + +#: ../Doc/reference/import.rst:638 +msgid "Module reprs" +msgstr "" + +#: ../Doc/reference/import.rst:640 +msgid "" +"By default, all modules have a usable repr, however depending on the " +"attributes set above, and in the module's spec, you can more explicitly " +"control the repr of module objects." +msgstr "" + +#: ../Doc/reference/import.rst:644 +msgid "" +"If the module has a spec (``__spec__``), the import machinery will try to " +"generate a repr from it. If that fails or there is no spec, the import " +"system will craft a default repr using whatever information is available on " +"the module. It will try to use the ``module.__name__``, ``module." +"__file__``, and ``module.__loader__`` as input into the repr, with defaults " +"for whatever information is missing." +msgstr "" + +#: ../Doc/reference/import.rst:651 +msgid "Here are the exact rules used:" +msgstr "" + +#: ../Doc/reference/import.rst:653 +msgid "" +"If the module has a ``__spec__`` attribute, the information in the spec is " +"used to generate the repr. The \"name\", \"loader\", \"origin\", and " +"\"has_location\" attributes are consulted." +msgstr "" + +#: ../Doc/reference/import.rst:657 +msgid "" +"If the module has a ``__file__`` attribute, this is used as part of the " +"module's repr." +msgstr "" + +#: ../Doc/reference/import.rst:660 +msgid "" +"If the module has no ``__file__`` but does have a ``__loader__`` that is not " +"``None``, then the loader's repr is used as part of the module's repr." +msgstr "" + +#: ../Doc/reference/import.rst:663 +msgid "Otherwise, just use the module's ``__name__`` in the repr." +msgstr "" + +#: ../Doc/reference/import.rst:665 +msgid "" +"Use of :meth:`loader.module_repr() ` has " +"been deprecated and the module spec is now used by the import machinery to " +"generate a module repr." +msgstr "" + +#: ../Doc/reference/import.rst:670 +msgid "" +"For backward compatibility with Python 3.3, the module repr will be " +"generated by calling the loader's :meth:`~importlib.abc.Loader.module_repr` " +"method, if defined, before trying either approach described above. However, " +"the method is deprecated." +msgstr "" + +#: ../Doc/reference/import.rst:677 +msgid "The Path Based Finder" +msgstr "" + +#: ../Doc/reference/import.rst:682 +msgid "" +"As mentioned previously, Python comes with several default meta path " +"finders. One of these, called the :term:`path based finder` (:class:" +"`~importlib.machinery.PathFinder`), searches an :term:`import path`, which " +"contains a list of :term:`path entries `. Each path entry names " +"a location to search for modules." +msgstr "" + +#: ../Doc/reference/import.rst:688 +msgid "" +"The path based finder itself doesn't know how to import anything. Instead, " +"it traverses the individual path entries, associating each of them with a " +"path entry finder that knows how to handle that particular kind of path." +msgstr "" + +#: ../Doc/reference/import.rst:692 +msgid "" +"The default set of path entry finders implement all the semantics for " +"finding modules on the file system, handling special file types such as " +"Python source code (``.py`` files), Python byte code (``.pyc`` files) and " +"shared libraries (e.g. ``.so`` files). When supported by the :mod:" +"`zipimport` module in the standard library, the default path entry finders " +"also handle loading all of these file types (other than shared libraries) " +"from zipfiles." +msgstr "" + +#: ../Doc/reference/import.rst:699 +msgid "" +"Path entries need not be limited to file system locations. They can refer " +"to URLs, database queries, or any other location that can be specified as a " +"string." +msgstr "" + +#: ../Doc/reference/import.rst:703 +msgid "" +"The path based finder provides additional hooks and protocols so that you " +"can extend and customize the types of searchable path entries. For example, " +"if you wanted to support path entries as network URLs, you could write a " +"hook that implements HTTP semantics to find modules on the web. This hook " +"(a callable) would return a :term:`path entry finder` supporting the " +"protocol described below, which was then used to get a loader for the module " +"from the web." +msgstr "" + +#: ../Doc/reference/import.rst:711 +msgid "" +"A word of warning: this section and the previous both use the term *finder*, " +"distinguishing between them by using the terms :term:`meta path finder` and :" +"term:`path entry finder`. These two types of finders are very similar, " +"support similar protocols, and function in similar ways during the import " +"process, but it's important to keep in mind that they are subtly different. " +"In particular, meta path finders operate at the beginning of the import " +"process, as keyed off the :data:`sys.meta_path` traversal." +msgstr "" + +#: ../Doc/reference/import.rst:719 +msgid "" +"By contrast, path entry finders are in a sense an implementation detail of " +"the path based finder, and in fact, if the path based finder were to be " +"removed from :data:`sys.meta_path`, none of the path entry finder semantics " +"would be invoked." +msgstr "" + +#: ../Doc/reference/import.rst:726 +msgid "Path entry finders" +msgstr "" + +#: ../Doc/reference/import.rst:734 +msgid "" +"The :term:`path based finder` is responsible for finding and loading Python " +"modules and packages whose location is specified with a string :term:`path " +"entry`. Most path entries name locations in the file system, but they need " +"not be limited to this." +msgstr "" + +#: ../Doc/reference/import.rst:739 +msgid "" +"As a meta path finder, the :term:`path based finder` implements the :meth:" +"`~importlib.abc.MetaPathFinder.find_spec` protocol previously described, " +"however it exposes additional hooks that can be used to customize how " +"modules are found and loaded from the :term:`import path`." +msgstr "" + +#: ../Doc/reference/import.rst:744 +msgid "" +"Three variables are used by the :term:`path based finder`, :data:`sys." +"path`, :data:`sys.path_hooks` and :data:`sys.path_importer_cache`. The " +"``__path__`` attributes on package objects are also used. These provide " +"additional ways that the import machinery can be customized." +msgstr "" + +#: ../Doc/reference/import.rst:749 +msgid "" +":data:`sys.path` contains a list of strings providing search locations for " +"modules and packages. It is initialized from the :data:`PYTHONPATH` " +"environment variable and various other installation- and implementation-" +"specific defaults. Entries in :data:`sys.path` can name directories on the " +"file system, zip files, and potentially other \"locations\" (see the :mod:" +"`site` module) that should be searched for modules, such as URLs, or " +"database queries. Only strings and bytes should be present on :data:`sys." +"path`; all other data types are ignored. The encoding of bytes entries is " +"determined by the individual :term:`path entry finders `." +msgstr "" + +#: ../Doc/reference/import.rst:760 +msgid "" +"The :term:`path based finder` is a :term:`meta path finder`, so the import " +"machinery begins the :term:`import path` search by calling the path based " +"finder's :meth:`~importlib.machinery.PathFinder.find_spec` method as " +"described previously. When the ``path`` argument to :meth:`~importlib." +"machinery.PathFinder.find_spec` is given, it will be a list of string paths " +"to traverse - typically a package's ``__path__`` attribute for an import " +"within that package. If the ``path`` argument is ``None``, this indicates a " +"top level import and :data:`sys.path` is used." +msgstr "" + +#: ../Doc/reference/import.rst:769 +msgid "" +"The path based finder iterates over every entry in the search path, and for " +"each of these, looks for an appropriate :term:`path entry finder` (:class:" +"`~importlib.abc.PathEntryFinder`) for the path entry. Because this can be " +"an expensive operation (e.g. there may be `stat()` call overheads for this " +"search), the path based finder maintains a cache mapping path entries to " +"path entry finders. This cache is maintained in :data:`sys." +"path_importer_cache` (despite the name, this cache actually stores finder " +"objects rather than being limited to :term:`importer` objects). In this way, " +"the expensive search for a particular :term:`path entry` location's :term:" +"`path entry finder` need only be done once. User code is free to remove " +"cache entries from :data:`sys.path_importer_cache` forcing the path based " +"finder to perform the path entry search again [#fnpic]_." +msgstr "" + +#: ../Doc/reference/import.rst:782 +msgid "" +"If the path entry is not present in the cache, the path based finder " +"iterates over every callable in :data:`sys.path_hooks`. Each of the :term:" +"`path entry hooks ` in this list is called with a single " +"argument, the path entry to be searched. This callable may either return a :" +"term:`path entry finder` that can handle the path entry, or it may raise :" +"exc:`ImportError`. An :exc:`ImportError` is used by the path based finder " +"to signal that the hook cannot find a :term:`path entry finder` for that :" +"term:`path entry`. The exception is ignored and :term:`import path` " +"iteration continues. The hook should expect either a string or bytes " +"object; the encoding of bytes objects is up to the hook (e.g. it may be a " +"file system encoding, UTF-8, or something else), and if the hook cannot " +"decode the argument, it should raise :exc:`ImportError`." +msgstr "" + +#: ../Doc/reference/import.rst:796 +msgid "" +"If :data:`sys.path_hooks` iteration ends with no :term:`path entry finder` " +"being returned, then the path based finder's :meth:`~importlib.machinery." +"PathFinder.find_spec` method will store ``None`` in :data:`sys." +"path_importer_cache` (to indicate that there is no finder for this path " +"entry) and return ``None``, indicating that this :term:`meta path finder` " +"could not find the module." +msgstr "" + +#: ../Doc/reference/import.rst:803 +msgid "" +"If a :term:`path entry finder` *is* returned by one of the :term:`path entry " +"hook` callables on :data:`sys.path_hooks`, then the following protocol is " +"used to ask the finder for a module spec, which is then used when loading " +"the module." +msgstr "" + +#: ../Doc/reference/import.rst:808 +msgid "" +"The current working directory -- denoted by an empty string -- is handled " +"slightly differently from other entries on :data:`sys.path`. First, if the " +"current working directory is found to not exist, no value is stored in :data:" +"`sys.path_importer_cache`. Second, the value for the current working " +"directory is looked up fresh for each module lookup. Third, the path used " +"for :data:`sys.path_importer_cache` and returned by :meth:`importlib." +"machinery.PathFinder.find_spec` will be the actual current working directory " +"and not the empty string." +msgstr "" + +#: ../Doc/reference/import.rst:818 +msgid "Path entry finder protocol" +msgstr "" + +#: ../Doc/reference/import.rst:820 +msgid "" +"In order to support imports of modules and initialized packages and also to " +"contribute portions to namespace packages, path entry finders must implement " +"the :meth:`~importlib.abc.PathEntryFinder.find_spec` method." +msgstr "" + +#: ../Doc/reference/import.rst:824 +msgid "" +":meth:`~importlib.abc.PathEntryFinder.find_spec` takes two argument, the " +"fully qualified name of the module being imported, and the (optional) target " +"module. ``find_spec()`` returns a fully populated spec for the module. This " +"spec will always have \"loader\" set (with one exception)." +msgstr "" + +#: ../Doc/reference/import.rst:829 +msgid "" +"To indicate to the import machinery that the spec represents a namespace :" +"term:`portion`. the path entry finder sets \"loader\" on the spec to " +"``None`` and \"submodule_search_locations\" to a list containing the portion." +msgstr "" + +#: ../Doc/reference/import.rst:834 +msgid "" +":meth:`~importlib.abc.PathEntryFinder.find_spec` replaced :meth:`~importlib." +"abc.PathEntryFinder.find_loader` and :meth:`~importlib.abc.PathEntryFinder." +"find_module`, both of which are now deprecated, but will be used if " +"``find_spec()`` is not defined." +msgstr "" + +#: ../Doc/reference/import.rst:840 +msgid "" +"Older path entry finders may implement one of these two deprecated methods " +"instead of ``find_spec()``. The methods are still respected for the sake of " +"backward compatibility. However, if ``find_spec()`` is implemented on the " +"path entry finder, the legacy methods are ignored." +msgstr "" + +#: ../Doc/reference/import.rst:845 +msgid "" +":meth:`~importlib.abc.PathEntryFinder.find_loader` takes one argument, the " +"fully qualified name of the module being imported. ``find_loader()`` " +"returns a 2-tuple where the first item is the loader and the second item is " +"a namespace :term:`portion`. When the first item (i.e. the loader) is " +"``None``, this means that while the path entry finder does not have a loader " +"for the named module, it knows that the path entry contributes to a " +"namespace portion for the named module. This will almost always be the case " +"where Python is asked to import a namespace package that has no physical " +"presence on the file system. When a path entry finder returns ``None`` for " +"the loader, the second item of the 2-tuple return value must be a sequence, " +"although it can be empty." +msgstr "" + +#: ../Doc/reference/import.rst:857 +msgid "" +"If ``find_loader()`` returns a non-``None`` loader value, the portion is " +"ignored and the loader is returned from the path based finder, terminating " +"the search through the path entries." +msgstr "" + +#: ../Doc/reference/import.rst:861 +msgid "" +"For backwards compatibility with other implementations of the import " +"protocol, many path entry finders also support the same, traditional " +"``find_module()`` method that meta path finders support. However path entry " +"finder ``find_module()`` methods are never called with a ``path`` argument " +"(they are expected to record the appropriate path information from the " +"initial call to the path hook)." +msgstr "" + +#: ../Doc/reference/import.rst:868 +msgid "" +"The ``find_module()`` method on path entry finders is deprecated, as it does " +"not allow the path entry finder to contribute portions to namespace " +"packages. If both ``find_loader()`` and ``find_module()`` exist on a path " +"entry finder, the import system will always call ``find_loader()`` in " +"preference to ``find_module()``." +msgstr "" + +#: ../Doc/reference/import.rst:876 +msgid "Replacing the standard import system" +msgstr "" + +#: ../Doc/reference/import.rst:878 +msgid "" +"The most reliable mechanism for replacing the entire import system is to " +"delete the default contents of :data:`sys.meta_path`, replacing them " +"entirely with a custom meta path hook." +msgstr "" + +#: ../Doc/reference/import.rst:882 +msgid "" +"If it is acceptable to only alter the behaviour of import statements without " +"affecting other APIs that access the import system, then replacing the " +"builtin :func:`__import__` function may be sufficient. This technique may " +"also be employed at the module level to only alter the behaviour of import " +"statements within that module." +msgstr "" + +#: ../Doc/reference/import.rst:888 +msgid "" +"To selectively prevent import of some modules from a hook early on the meta " +"path (rather than disabling the standard import system entirely), it is " +"sufficient to raise :exc:`ModuleNoFoundError` directly from :meth:" +"`~importlib.abc.MetaPathFinder.find_spec` instead of returning ``None``. The " +"latter indicates that the meta path search should continue, while raising an " +"exception terminates it immediately." +msgstr "" + +#: ../Doc/reference/import.rst:897 +msgid "Special considerations for __main__" +msgstr "" + +#: ../Doc/reference/import.rst:899 +msgid "" +"The :mod:`__main__` module is a special case relative to Python's import " +"system. As noted :ref:`elsewhere `, the ``__main__`` module is " +"directly initialized at interpreter startup, much like :mod:`sys` and :mod:" +"`builtins`. However, unlike those two, it doesn't strictly qualify as a " +"built-in module. This is because the manner in which ``__main__`` is " +"initialized depends on the flags and other options with which the " +"interpreter is invoked." +msgstr "" + +#: ../Doc/reference/import.rst:910 +msgid "__main__.__spec__" +msgstr "" + +#: ../Doc/reference/import.rst:912 +msgid "" +"Depending on how :mod:`__main__` is initialized, ``__main__.__spec__`` gets " +"set appropriately or to ``None``." +msgstr "" + +#: ../Doc/reference/import.rst:915 +msgid "" +"When Python is started with the :option:`-m` option, ``__spec__`` is set to " +"the module spec of the corresponding module or package. ``__spec__`` is also " +"populated when the ``__main__`` module is loaded as part of executing a " +"directory, zipfile or other :data:`sys.path` entry." +msgstr "" + +#: ../Doc/reference/import.rst:920 +msgid "" +"In :ref:`the remaining cases ` ``__main__." +"__spec__`` is set to ``None``, as the code used to populate the :mod:" +"`__main__` does not correspond directly with an importable module:" +msgstr "" + +#: ../Doc/reference/import.rst:924 +msgid "interactive prompt" +msgstr "" + +#: ../Doc/reference/import.rst:925 +msgid "-c switch" +msgstr "" + +#: ../Doc/reference/import.rst:926 +msgid "running from stdin" +msgstr "" + +#: ../Doc/reference/import.rst:927 +msgid "running directly from a source or bytecode file" +msgstr "" + +#: ../Doc/reference/import.rst:929 +msgid "" +"Note that ``__main__.__spec__`` is always ``None`` in the last case, *even " +"if* the file could technically be imported directly as a module instead. Use " +"the :option:`-m` switch if valid module metadata is desired in :mod:" +"`__main__`." +msgstr "" + +#: ../Doc/reference/import.rst:934 +msgid "" +"Note also that even when ``__main__`` corresponds with an importable module " +"and ``__main__.__spec__`` is set accordingly, they're still considered " +"*distinct* modules. This is due to the fact that blocks guarded by ``if " +"__name__ == \"__main__\":`` checks only execute when the module is used to " +"populate the ``__main__`` namespace, and not during normal import." +msgstr "" + +#: ../Doc/reference/import.rst:942 +msgid "Open issues" +msgstr "" + +#: ../Doc/reference/import.rst:944 +msgid "XXX It would be really nice to have a diagram." +msgstr "" + +#: ../Doc/reference/import.rst:946 +msgid "" +"XXX * (import_machinery.rst) how about a section devoted just to the " +"attributes of modules and packages, perhaps expanding upon or supplanting " +"the related entries in the data model reference page?" +msgstr "" + +#: ../Doc/reference/import.rst:950 +msgid "" +"XXX runpy, pkgutil, et al in the library manual should all get \"See Also\" " +"links at the top pointing to the new import system section." +msgstr "" + +#: ../Doc/reference/import.rst:953 +msgid "" +"XXX Add more explanation regarding the different ways in which ``__main__`` " +"is initialized?" +msgstr "" + +#: ../Doc/reference/import.rst:956 +msgid "" +"XXX Add more info on ``__main__`` quirks/pitfalls (i.e. copy from :pep:" +"`395`)." +msgstr "" + +#: ../Doc/reference/import.rst:961 +msgid "References" +msgstr "" + +#: ../Doc/reference/import.rst:963 +msgid "" +"The import machinery has evolved considerably since Python's early days. " +"The original `specification for packages `_ is still available to read, although some details " +"have changed since the writing of that document." +msgstr "" + +#: ../Doc/reference/import.rst:968 +msgid "" +"The original specification for :data:`sys.meta_path` was :pep:`302`, with " +"subsequent extension in :pep:`420`." +msgstr "" + +#: ../Doc/reference/import.rst:971 +msgid "" +":pep:`420` introduced :term:`namespace packages ` for " +"Python 3.3. :pep:`420` also introduced the :meth:`find_loader` protocol as " +"an alternative to :meth:`find_module`." +msgstr "" + +#: ../Doc/reference/import.rst:975 +msgid "" +":pep:`366` describes the addition of the ``__package__`` attribute for " +"explicit relative imports in main modules." +msgstr "" + +#: ../Doc/reference/import.rst:978 +msgid "" +":pep:`328` introduced absolute and explicit relative imports and initially " +"proposed ``__name__`` for semantics :pep:`366` would eventually specify for " +"``__package__``." +msgstr "" + +#: ../Doc/reference/import.rst:982 +msgid ":pep:`338` defines executing modules as scripts." +msgstr "" + +#: ../Doc/reference/import.rst:984 +msgid "" +":pep:`451` adds the encapsulation of per-module import state in spec " +"objects. It also off-loads most of the boilerplate responsibilities of " +"loaders back onto the import machinery. These changes allow the deprecation " +"of several APIs in the import system and also addition of new methods to " +"finders and loaders." +msgstr "" + +#: ../Doc/reference/import.rst:992 +msgid "See :class:`types.ModuleType`." +msgstr "" + +#: ../Doc/reference/import.rst:994 +msgid "" +"The importlib implementation avoids using the return value directly. " +"Instead, it gets the module object by looking the module name up in :data:" +"`sys.modules`. The indirect effect of this is that an imported module may " +"replace itself in :data:`sys.modules`. This is implementation-specific " +"behavior that is not guaranteed to work in other Python implementations." +msgstr "" + +#: ../Doc/reference/import.rst:1001 +msgid "" +"In legacy code, it is possible to find instances of :class:`imp." +"NullImporter` in the :data:`sys.path_importer_cache`. It is recommended " +"that code be changed to use ``None`` instead. See :ref:`portingpythoncode` " +"for more details." +msgstr "" + +#: ../Doc/reference/index.rst:5 +msgid "The Python Language Reference" +msgstr "" + +#: ../Doc/reference/index.rst:7 +msgid "" +"This reference manual describes the syntax and \"core semantics\" of the " +"language. It is terse, but attempts to be exact and complete. The semantics " +"of non-essential built-in object types and of the built-in functions and " +"modules are described in :ref:`library-index`. For an informal introduction " +"to the language, see :ref:`tutorial-index`. For C or C++ programmers, two " +"additional manuals exist: :ref:`extending-index` describes the high-level " +"picture of how to write a Python extension module, and the :ref:`c-api-" +"index` describes the interfaces available to C/C++ programmers in detail." +msgstr "" + +#: ../Doc/reference/introduction.rst:6 +msgid "Introduction" +msgstr "" + +#: ../Doc/reference/introduction.rst:8 +msgid "" +"This reference manual describes the Python programming language. It is not " +"intended as a tutorial." +msgstr "" + +#: ../Doc/reference/introduction.rst:11 +msgid "" +"While I am trying to be as precise as possible, I chose to use English " +"rather than formal specifications for everything except syntax and lexical " +"analysis. This should make the document more understandable to the average " +"reader, but will leave room for ambiguities. Consequently, if you were " +"coming from Mars and tried to re-implement Python from this document alone, " +"you might have to guess things and in fact you would probably end up " +"implementing quite a different language. On the other hand, if you are using " +"Python and wonder what the precise rules about a particular area of the " +"language are, you should definitely be able to find them here. If you would " +"like to see a more formal definition of the language, maybe you could " +"volunteer your time --- or invent a cloning machine :-)." +msgstr "" + +#: ../Doc/reference/introduction.rst:23 +msgid "" +"It is dangerous to add too many implementation details to a language " +"reference document --- the implementation may change, and other " +"implementations of the same language may work differently. On the other " +"hand, CPython is the one Python implementation in widespread use (although " +"alternate implementations continue to gain support), and its particular " +"quirks are sometimes worth being mentioned, especially where the " +"implementation imposes additional limitations. Therefore, you'll find short " +"\"implementation notes\" sprinkled throughout the text." +msgstr "" + +#: ../Doc/reference/introduction.rst:32 +msgid "" +"Every Python implementation comes with a number of built-in and standard " +"modules. These are documented in :ref:`library-index`. A few built-in " +"modules are mentioned when they interact in a significant way with the " +"language definition." +msgstr "" + +#: ../Doc/reference/introduction.rst:41 +msgid "Alternate Implementations" +msgstr "" + +#: ../Doc/reference/introduction.rst:43 +msgid "" +"Though there is one Python implementation which is by far the most popular, " +"there are some alternate implementations which are of particular interest to " +"different audiences." +msgstr "" + +#: ../Doc/reference/introduction.rst:47 +msgid "Known implementations include:" +msgstr "" + +#: ../Doc/reference/introduction.rst:51 +msgid "CPython" +msgstr "" + +#: ../Doc/reference/introduction.rst:50 +msgid "" +"This is the original and most-maintained implementation of Python, written " +"in C. New language features generally appear here first." +msgstr "" + +#: ../Doc/reference/introduction.rst:57 +msgid "Jython" +msgstr "" + +#: ../Doc/reference/introduction.rst:54 +msgid "" +"Python implemented in Java. This implementation can be used as a scripting " +"language for Java applications, or can be used to create applications using " +"the Java class libraries. It is also often used to create tests for Java " +"libraries. More information can be found at `the Jython website `_." +msgstr "" + +#: ../Doc/reference/introduction.rst:63 +msgid "Python for .NET" +msgstr "" + +#: ../Doc/reference/introduction.rst:60 +msgid "" +"This implementation actually uses the CPython implementation, but is a " +"managed .NET application and makes .NET libraries available. It was created " +"by Brian Lloyd. For more information, see the `Python for .NET home page " +"`_." +msgstr "" + +#: ../Doc/reference/introduction.rst:69 +msgid "IronPython" +msgstr "" + +#: ../Doc/reference/introduction.rst:66 +msgid "" +"An alternate Python for .NET. Unlike Python.NET, this is a complete Python " +"implementation that generates IL, and compiles Python code directly to .NET " +"assemblies. It was created by Jim Hugunin, the original creator of Jython. " +"For more information, see `the IronPython website `_." +msgstr "" + +#: ../Doc/reference/introduction.rst:77 +msgid "PyPy" +msgstr "" + +#: ../Doc/reference/introduction.rst:72 +msgid "" +"An implementation of Python written completely in Python. It supports " +"several advanced features not found in other implementations like stackless " +"support and a Just in Time compiler. One of the goals of the project is to " +"encourage experimentation with the language itself by making it easier to " +"modify the interpreter (since it is written in Python). Additional " +"information is available on `the PyPy project's home page `_." +msgstr "" + +#: ../Doc/reference/introduction.rst:79 +msgid "" +"Each of these implementations varies in some way from the language as " +"documented in this manual, or introduces specific information beyond what's " +"covered in the standard Python documentation. Please refer to the " +"implementation-specific documentation to determine what else you need to " +"know about the specific implementation you're using." +msgstr "" + +#: ../Doc/reference/introduction.rst:89 +msgid "Notation" +msgstr "" + +#: ../Doc/reference/introduction.rst:93 +msgid "" +"The descriptions of lexical analysis and syntax use a modified BNF grammar " +"notation. This uses the following style of definition:" +msgstr "" + +#: ../Doc/reference/introduction.rst:100 +msgid "" +"The first line says that a ``name`` is an ``lc_letter`` followed by a " +"sequence of zero or more ``lc_letter``\\ s and underscores. An " +"``lc_letter`` in turn is any of the single characters ``'a'`` through " +"``'z'``. (This rule is actually adhered to for the names defined in lexical " +"and grammar rules in this document.)" +msgstr "" + +#: ../Doc/reference/introduction.rst:105 +msgid "" +"Each rule begins with a name (which is the name defined by the rule) and ``::" +"=``. A vertical bar (``|``) is used to separate alternatives; it is the " +"least binding operator in this notation. A star (``*``) means zero or more " +"repetitions of the preceding item; likewise, a plus (``+``) means one or " +"more repetitions, and a phrase enclosed in square brackets (``[ ]``) means " +"zero or one occurrences (in other words, the enclosed phrase is optional). " +"The ``*`` and ``+`` operators bind as tightly as possible; parentheses are " +"used for grouping. Literal strings are enclosed in quotes. White space is " +"only meaningful to separate tokens. Rules are normally contained on a single " +"line; rules with many alternatives may be formatted alternatively with each " +"line after the first beginning with a vertical bar." +msgstr "" + +#: ../Doc/reference/introduction.rst:119 +msgid "" +"In lexical definitions (as the example above), two more conventions are " +"used: Two literal characters separated by three dots mean a choice of any " +"single character in the given (inclusive) range of ASCII characters. A " +"phrase between angular brackets (``<...>``) gives an informal description of " +"the symbol defined; e.g., this could be used to describe the notion of " +"'control character' if needed." +msgstr "" + +#: ../Doc/reference/introduction.rst:126 +msgid "" +"Even though the notation used is almost the same, there is a big difference " +"between the meaning of lexical and syntactic definitions: a lexical " +"definition operates on the individual characters of the input source, while " +"a syntax definition operates on the stream of tokens generated by the " +"lexical analysis. All uses of BNF in the next chapter (\"Lexical Analysis\") " +"are lexical definitions; uses in subsequent chapters are syntactic " +"definitions." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:6 +msgid "Lexical analysis" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:10 +msgid "" +"A Python program is read by a *parser*. Input to the parser is a stream of " +"*tokens*, generated by the *lexical analyzer*. This chapter describes how " +"the lexical analyzer breaks a file into tokens." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:14 +msgid "" +"Python reads program text as Unicode code points; the encoding of a source " +"file can be given by an encoding declaration and defaults to UTF-8, see :pep:" +"`3120` for details. If the source file cannot be decoded, a :exc:" +"`SyntaxError` is raised." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:23 +msgid "Line structure" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:27 +msgid "A Python program is divided into a number of *logical lines*." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:33 +msgid "Logical lines" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:37 +msgid "" +"The end of a logical line is represented by the token NEWLINE. Statements " +"cannot cross logical line boundaries except where NEWLINE is allowed by the " +"syntax (e.g., between statements in compound statements). A logical line is " +"constructed from one or more *physical lines* by following the explicit or " +"implicit *line joining* rules." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:47 +msgid "Physical lines" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:49 +msgid "" +"A physical line is a sequence of characters terminated by an end-of-line " +"sequence. In source files, any of the standard platform line termination " +"sequences can be used - the Unix form using ASCII LF (linefeed), the Windows " +"form using the ASCII sequence CR LF (return followed by linefeed), or the " +"old Macintosh form using the ASCII CR (return) character. All of these " +"forms can be used equally, regardless of platform." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:56 +msgid "" +"When embedding Python, source code strings should be passed to Python APIs " +"using the standard C conventions for newline characters (the ``\\n`` " +"character, representing ASCII LF, is the line terminator)." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:64 +msgid "Comments" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:68 +msgid "" +"A comment starts with a hash character (``#``) that is not part of a string " +"literal, and ends at the end of the physical line. A comment signifies the " +"end of the logical line unless the implicit line joining rules are invoked. " +"Comments are ignored by the syntax; they are not tokens." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:77 +msgid "Encoding declarations" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:81 +msgid "" +"If a comment in the first or second line of the Python script matches the " +"regular expression ``coding[=:]\\s*([-\\w.]+)``, this comment is processed " +"as an encoding declaration; the first group of this expression names the " +"encoding of the source code file. The encoding declaration must appear on a " +"line of its own. If it is the second line, the first line must also be a " +"comment-only line. The recommended forms of an encoding expression are ::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:90 +msgid "which is recognized also by GNU Emacs, and ::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:94 +msgid "which is recognized by Bram Moolenaar's VIM." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:96 +msgid "" +"If no encoding declaration is found, the default encoding is UTF-8. In " +"addition, if the first bytes of the file are the UTF-8 byte-order mark " +"(``b'\\xef\\xbb\\xbf'``), the declared file encoding is UTF-8 (this is " +"supported, among others, by Microsoft's :program:`notepad`)." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:101 +msgid "" +"If an encoding is declared, the encoding name must be recognized by Python. " +"The encoding is used for all lexical analysis, including string literals, " +"comments and identifiers." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:111 +msgid "Explicit line joining" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:115 +msgid "" +"Two or more physical lines may be joined into logical lines using backslash " +"characters (``\\``), as follows: when a physical line ends in a backslash " +"that is not part of a string literal or comment, it is joined with the " +"following forming a single logical line, deleting the backslash and the " +"following end-of-line character. For example::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:126 +msgid "" +"A line ending in a backslash cannot carry a comment. A backslash does not " +"continue a comment. A backslash does not continue a token except for string " +"literals (i.e., tokens other than string literals cannot be split across " +"physical lines using a backslash). A backslash is illegal elsewhere on a " +"line outside a string literal." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:136 +msgid "Implicit line joining" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:138 +msgid "" +"Expressions in parentheses, square brackets or curly braces can be split " +"over more than one physical line without using backslashes. For example::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:146 +msgid "" +"Implicitly continued lines can carry comments. The indentation of the " +"continuation lines is not important. Blank continuation lines are allowed. " +"There is no NEWLINE token between implicit continuation lines. Implicitly " +"continued lines can also occur within triple-quoted strings (see below); in " +"that case they cannot carry comments." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:156 +msgid "Blank lines" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:160 +msgid "" +"A logical line that contains only spaces, tabs, formfeeds and possibly a " +"comment, is ignored (i.e., no NEWLINE token is generated). During " +"interactive input of statements, handling of a blank line may differ " +"depending on the implementation of the read-eval-print loop. In the " +"standard interactive interpreter, an entirely blank logical line (i.e. one " +"containing not even whitespace or a comment) terminates a multi-line " +"statement." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:171 +msgid "Indentation" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:175 +msgid "" +"Leading whitespace (spaces and tabs) at the beginning of a logical line is " +"used to compute the indentation level of the line, which in turn is used to " +"determine the grouping of statements." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:179 +msgid "" +"Tabs are replaced (from left to right) by one to eight spaces such that the " +"total number of characters up to and including the replacement is a multiple " +"of eight (this is intended to be the same rule as used by Unix). The total " +"number of spaces preceding the first non-blank character then determines the " +"line's indentation. Indentation cannot be split over multiple physical " +"lines using backslashes; the whitespace up to the first backslash determines " +"the indentation." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:187 +msgid "" +"Indentation is rejected as inconsistent if a source file mixes tabs and " +"spaces in a way that makes the meaning dependent on the worth of a tab in " +"spaces; a :exc:`TabError` is raised in that case." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:191 +msgid "" +"**Cross-platform compatibility note:** because of the nature of text editors " +"on non-UNIX platforms, it is unwise to use a mixture of spaces and tabs for " +"the indentation in a single source file. It should also be noted that " +"different platforms may explicitly limit the maximum indentation level." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:196 +msgid "" +"A formfeed character may be present at the start of the line; it will be " +"ignored for the indentation calculations above. Formfeed characters " +"occurring elsewhere in the leading whitespace have an undefined effect (for " +"instance, they may reset the space count to zero)." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:203 +msgid "" +"The indentation levels of consecutive lines are used to generate INDENT and " +"DEDENT tokens, using a stack, as follows." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:206 +msgid "" +"Before the first line of the file is read, a single zero is pushed on the " +"stack; this will never be popped off again. The numbers pushed on the stack " +"will always be strictly increasing from bottom to top. At the beginning of " +"each logical line, the line's indentation level is compared to the top of " +"the stack. If it is equal, nothing happens. If it is larger, it is pushed on " +"the stack, and one INDENT token is generated. If it is smaller, it *must* " +"be one of the numbers occurring on the stack; all numbers on the stack that " +"are larger are popped off, and for each number popped off a DEDENT token is " +"generated. At the end of the file, a DEDENT token is generated for each " +"number remaining on the stack that is larger than zero." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:217 +msgid "" +"Here is an example of a correctly (though confusingly) indented piece of " +"Python code::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:232 +msgid "The following example shows various indentation errors::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:242 +msgid "" +"(Actually, the first three errors are detected by the parser; only the last " +"error is found by the lexical analyzer --- the indentation of ``return r`` " +"does not match a level popped off the stack.)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:250 +msgid "Whitespace between tokens" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:252 +msgid "" +"Except at the beginning of a logical line or in string literals, the " +"whitespace characters space, tab and formfeed can be used interchangeably to " +"separate tokens. Whitespace is needed between two tokens only if their " +"concatenation could otherwise be interpreted as a different token (e.g., ab " +"is one token, but a b is two tokens)." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:262 +msgid "Other tokens" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:264 +msgid "" +"Besides NEWLINE, INDENT and DEDENT, the following categories of tokens " +"exist: *identifiers*, *keywords*, *literals*, *operators*, and *delimiters*. " +"Whitespace characters (other than line terminators, discussed earlier) are " +"not tokens, but serve to delimit tokens. Where ambiguity exists, a token " +"comprises the longest possible string that forms a legal token, when read " +"from left to right." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:274 +msgid "Identifiers and keywords" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:278 +msgid "" +"Identifiers (also referred to as *names*) are described by the following " +"lexical definitions." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:281 +msgid "" +"The syntax of identifiers in Python is based on the Unicode standard annex " +"UAX-31, with elaboration and changes as defined below; see also :pep:`3131` " +"for further details." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:285 +msgid "" +"Within the ASCII range (U+0001..U+007F), the valid characters for " +"identifiers are the same as in Python 2.x: the uppercase and lowercase " +"letters ``A`` through ``Z``, the underscore ``_`` and, except for the first " +"character, the digits ``0`` through ``9``." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:290 +msgid "" +"Python 3.0 introduces additional characters from outside the ASCII range " +"(see :pep:`3131`). For these characters, the classification uses the " +"version of the Unicode Character Database as included in the :mod:" +"`unicodedata` module." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:294 +msgid "Identifiers are unlimited in length. Case is significant." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:303 +msgid "The Unicode category codes mentioned above stand for:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:305 +msgid "*Lu* - uppercase letters" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:306 +msgid "*Ll* - lowercase letters" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:307 +msgid "*Lt* - titlecase letters" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:308 +msgid "*Lm* - modifier letters" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:309 +msgid "*Lo* - other letters" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:310 +msgid "*Nl* - letter numbers" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:311 +msgid "*Mn* - nonspacing marks" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:312 +msgid "*Mc* - spacing combining marks" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:313 +msgid "*Nd* - decimal numbers" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:314 +msgid "*Pc* - connector punctuations" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:315 +msgid "" +"*Other_ID_Start* - explicit list of characters in `PropList.txt `_ to support backwards " +"compatibility" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:318 +msgid "*Other_ID_Continue* - likewise" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:320 +msgid "" +"All identifiers are converted into the normal form NFKC while parsing; " +"comparison of identifiers is based on NFKC." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:323 +msgid "" +"A non-normative HTML file listing all valid identifier characters for " +"Unicode 4.1 can be found at https://www.dcl.hpi.uni-potsdam.de/home/loewis/" +"table-3131.html." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:331 +msgid "Keywords" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:337 +msgid "" +"The following identifiers are used as reserved words, or *keywords* of the " +"language, and cannot be used as ordinary identifiers. They must be spelled " +"exactly as written here:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:354 +msgid "Reserved classes of identifiers" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:356 +msgid "" +"Certain classes of identifiers (besides keywords) have special meanings. " +"These classes are identified by the patterns of leading and trailing " +"underscore characters:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:370 +msgid "``_*``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:361 +msgid "" +"Not imported by ``from module import *``. The special identifier ``_`` is " +"used in the interactive interpreter to store the result of the last " +"evaluation; it is stored in the :mod:`builtins` module. When not in " +"interactive mode, ``_`` has no special meaning and is not defined. See " +"section :ref:`import`." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:368 +msgid "" +"The name ``_`` is often used in conjunction with internationalization; refer " +"to the documentation for the :mod:`gettext` module for more information on " +"this convention." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:378 +msgid "``__*__``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:373 +msgid "" +"System-defined names. These names are defined by the interpreter and its " +"implementation (including the standard library). Current system names are " +"discussed in the :ref:`specialnames` section and elsewhere. More will " +"likely be defined in future versions of Python. *Any* use of ``__*__`` " +"names, in any context, that does not follow explicitly documented use, is " +"subject to breakage without warning." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:385 +msgid "``__*``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:381 +msgid "" +"Class-private names. Names in this category, when used within the context " +"of a class definition, are re-written to use a mangled form to help avoid " +"name clashes between \"private\" attributes of base and derived classes. See " +"section :ref:`atom-identifiers`." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:394 +msgid "Literals are notations for constant values of some built-in types." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:400 +msgid "String and Bytes literals" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:404 +msgid "String literals are described by the following lexical definitions:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:429 +msgid "" +"One syntactic restriction not indicated by these productions is that " +"whitespace is not allowed between the :token:`stringprefix` or :token:" +"`bytesprefix` and the rest of the literal. The source character set is " +"defined by the encoding declaration; it is UTF-8 if no encoding declaration " +"is given in the source file; see section :ref:`encodings`." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:437 +msgid "" +"In plain English: Both types of literals can be enclosed in matching single " +"quotes (``'``) or double quotes (``\"``). They can also be enclosed in " +"matching groups of three single or double quotes (these are generally " +"referred to as *triple-quoted strings*). The backslash (``\\``) character " +"is used to escape characters that otherwise have a special meaning, such as " +"newline, backslash itself, or the quote character." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:444 +msgid "" +"Bytes literals are always prefixed with ``'b'`` or ``'B'``; they produce an " +"instance of the :class:`bytes` type instead of the :class:`str` type. They " +"may only contain ASCII characters; bytes with a numeric value of 128 or " +"greater must be expressed with escapes." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:449 +msgid "" +"As of Python 3.3 it is possible again to prefix string literals with a ``u`` " +"prefix to simplify maintenance of dual 2.x and 3.x codebases." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:452 +msgid "" +"Both string and bytes literals may optionally be prefixed with a letter " +"``'r'`` or ``'R'``; such strings are called :dfn:`raw strings` and treat " +"backslashes as literal characters. As a result, in string literals, " +"``'\\U'`` and ``'\\u'`` escapes in raw strings are not treated specially. " +"Given that Python 2.x's raw unicode literals behave differently than Python " +"3.x's the ``'ur'`` syntax is not supported." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:459 +msgid "" +"The ``'rb'`` prefix of raw bytes literals has been added as a synonym of " +"``'br'``." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:463 +msgid "" +"Support for the unicode legacy literal (``u'value'``) was reintroduced to " +"simplify the maintenance of dual Python 2.x and 3.x codebases. See :pep:" +"`414` for more information." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:468 +msgid "" +"A string literal with ``'f'`` or ``'F'`` in its prefix is a :dfn:`formatted " +"string literal`; see :ref:`f-strings`. The ``'f'`` may be combined with " +"``'r'``, but not with ``'b'`` or ``'u'``, therefore raw formatted strings " +"are possible, but formatted bytes literals are not." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:473 +msgid "" +"In triple-quoted literals, unescaped newlines and quotes are allowed (and " +"are retained), except that three unescaped quotes in a row terminate the " +"literal. (A \"quote\" is the character used to open the literal, i.e. " +"either ``'`` or ``\"``.)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:479 +msgid "" +"Unless an ``'r'`` or ``'R'`` prefix is present, escape sequences in string " +"and bytes literals are interpreted according to rules similar to those used " +"by Standard C. The recognized escape sequences are:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:484 +#: ../Doc/reference/lexical_analysis.rst:517 +msgid "Escape Sequence" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:484 +#: ../Doc/reference/lexical_analysis.rst:517 +msgid "Notes" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:486 +msgid "``\\newline``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:486 +msgid "Backslash and newline ignored" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:488 +msgid "``\\\\``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:488 +msgid "Backslash (``\\``)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:490 +msgid "``\\'``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:490 +msgid "Single quote (``'``)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:492 +msgid "``\\\"``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:492 +msgid "Double quote (``\"``)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:494 +msgid "``\\a``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:494 +msgid "ASCII Bell (BEL)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:496 +msgid "``\\b``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:496 +msgid "ASCII Backspace (BS)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:498 +msgid "``\\f``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:498 +msgid "ASCII Formfeed (FF)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:500 +msgid "``\\n``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:500 +msgid "ASCII Linefeed (LF)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:502 +msgid "``\\r``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:502 +msgid "ASCII Carriage Return (CR)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:504 +msgid "``\\t``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:504 +msgid "ASCII Horizontal Tab (TAB)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:506 +msgid "``\\v``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:506 +msgid "ASCII Vertical Tab (VT)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:508 +msgid "``\\ooo``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:508 +msgid "Character with octal value *ooo*" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:508 +msgid "(1,3)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:511 +msgid "``\\xhh``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:511 +msgid "Character with hex value *hh*" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:511 +msgid "(2,3)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:514 +msgid "Escape sequences only recognized in string literals are:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:519 +msgid "``\\N{name}``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:519 +msgid "Character named *name* in the Unicode database" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:519 +msgid "\\(4)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:522 +msgid "``\\uxxxx``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:522 +msgid "Character with 16-bit hex value *xxxx*" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:522 +msgid "\\(5)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:525 +msgid "``\\Uxxxxxxxx``" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:525 +msgid "Character with 32-bit hex value *xxxxxxxx*" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:525 +msgid "\\(6)" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:529 +msgid "Notes:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:532 +msgid "As in Standard C, up to three octal digits are accepted." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:535 +msgid "Unlike in Standard C, exactly two hex digits are required." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:538 +msgid "" +"In a bytes literal, hexadecimal and octal escapes denote the byte with the " +"given value. In a string literal, these escapes denote a Unicode character " +"with the given value." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:543 +msgid "Support for name aliases [#]_ has been added." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:547 +msgid "Exactly four hex digits are required." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:550 +msgid "" +"Any Unicode character can be encoded this way. Exactly eight hex digits are " +"required." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:556 +msgid "" +"Unlike Standard C, all unrecognized escape sequences are left in the string " +"unchanged, i.e., *the backslash is left in the result*. (This behavior is " +"useful when debugging: if an escape sequence is mistyped, the resulting " +"output is more easily recognized as broken.) It is also important to note " +"that the escape sequences only recognized in string literals fall into the " +"category of unrecognized escapes for bytes literals." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:563 +msgid "" +"Unrecognized escape sequences produce a DeprecationWarning. In some future " +"version of Python they will be a SyntaxError." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:567 +msgid "" +"Even in a raw literal, quotes can be escaped with a backslash, but the " +"backslash remains in the result; for example, ``r\"\\\"\"`` is a valid " +"string literal consisting of two characters: a backslash and a double quote; " +"``r\"\\\"`` is not a valid string literal (even a raw string cannot end in " +"an odd number of backslashes). Specifically, *a raw literal cannot end in a " +"single backslash* (since the backslash would escape the following quote " +"character). Note also that a single backslash followed by a newline is " +"interpreted as those two characters as part of the literal, *not* as a line " +"continuation." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:580 +msgid "String literal concatenation" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:582 +msgid "" +"Multiple adjacent string or bytes literals (delimited by whitespace), " +"possibly using different quoting conventions, are allowed, and their meaning " +"is the same as their concatenation. Thus, ``\"hello\" 'world'`` is " +"equivalent to ``\"helloworld\"``. This feature can be used to reduce the " +"number of backslashes needed, to split long strings conveniently across long " +"lines, or even to add comments to parts of strings, for example::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:593 +msgid "" +"Note that this feature is defined at the syntactical level, but implemented " +"at compile time. The '+' operator must be used to concatenate string " +"expressions at run time. Also note that literal concatenation can use " +"different quoting styles for each component (even mixing raw strings and " +"triple quoted strings), and formatted string literals may be concatenated " +"with plain string literals." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:609 +msgid "Formatted string literals" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:613 +msgid "" +"A :dfn:`formatted string literal` or :dfn:`f-string` is a string literal " +"that is prefixed with ``'f'`` or ``'F'``. These strings may contain " +"replacement fields, which are expressions delimited by curly braces ``{}``. " +"While other string literals always have a constant value, formatted strings " +"are really expressions evaluated at run time." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:619 +msgid "" +"Escape sequences are decoded like in ordinary string literals (except when a " +"literal is also marked as a raw string). After decoding, the grammar for " +"the contents of the string is:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:633 +msgid "" +"The parts of the string outside curly braces are treated literally, except " +"that any doubled curly braces ``'{{'`` or ``'}}'`` are replaced with the " +"corresponding single curly brace. A single opening curly bracket ``'{'`` " +"marks a replacement field, which starts with a Python expression. After the " +"expression, there may be a conversion field, introduced by an exclamation " +"point ``'!'``. A format specifier may also be appended, introduced by a " +"colon ``':'``. A replacement field ends with a closing curly bracket " +"``'}'``." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:642 +msgid "" +"Expressions in formatted string literals are treated like regular Python " +"expressions surrounded by parentheses, with a few exceptions. An empty " +"expression is not allowed, and a :keyword:`lambda` expression must be " +"surrounded by explicit parentheses. Replacement expressions can contain " +"line breaks (e.g. in triple-quoted strings), but they cannot contain " +"comments. Each expression is evaluated in the context where the formatted " +"string literal appears, in order from left to right." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:650 +msgid "" +"If a conversion is specified, the result of evaluating the expression is " +"converted before formatting. Conversion ``'!s'`` calls :func:`str` on the " +"result, ``'!r'`` calls :func:`repr`, and ``'!a'`` calls :func:`ascii`." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:654 +msgid "" +"The result is then formatted using the :func:`format` protocol. The format " +"specifier is passed to the :meth:`__format__` method of the expression or " +"conversion result. An empty string is passed when the format specifier is " +"omitted. The formatted result is then included in the final value of the " +"whole string." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:660 +msgid "" +"Top-level format specifiers may include nested replacement fields. These " +"nested fields may include their own conversion fields and format specifiers, " +"but may not include more deeply-nested replacement fields." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:664 +msgid "" +"Formatted string literals may be concatenated, but replacement fields cannot " +"be split across literals." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:667 +msgid "Some examples of formatted string literals::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:680 +msgid "" +"A consequence of sharing the same syntax as regular string literals is that " +"characters in the replacement fields must not conflict with the quoting used " +"in the outer formatted string literal. Also, escape sequences normally " +"apply to the outer formatted string literal, rather than inner string " +"literals::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:694 +msgid "" +"See also :pep:`498` for the proposal that added formatted string literals, " +"and :meth:`str.format`, which uses a related format string mechanism." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:701 +msgid "Numeric literals" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:707 +msgid "" +"There are three types of numeric literals: integers, floating point numbers, " +"and imaginary numbers. There are no complex literals (complex numbers can " +"be formed by adding a real number and an imaginary number)." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:711 +msgid "" +"Note that numeric literals do not include a sign; a phrase like ``-1`` is " +"actually an expression composed of the unary operator '``-``' and the " +"literal ``1``." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:719 +msgid "Integer literals" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:721 +msgid "Integer literals are described by the following lexical definitions:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:735 +msgid "" +"There is no limit for the length of integer literals apart from what can be " +"stored in available memory." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:738 +msgid "" +"Underscores are ignored for determining the numeric value of the literal. " +"They can be used to group digits for enhanced readability. One underscore " +"can occur between digits, and after base specifiers like ``0x``." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:742 +msgid "" +"Note that leading zeros in a non-zero decimal number are not allowed. This " +"is for disambiguation with C-style octal literals, which Python used before " +"version 3.0." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:746 +msgid "Some examples of integer literals::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:752 +#: ../Doc/reference/lexical_analysis.rst:784 +msgid "Underscores are now allowed for grouping purposes in literals." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:759 +msgid "Floating point literals" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:761 +msgid "" +"Floating point literals are described by the following lexical definitions:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:771 +msgid "" +"Note that the integer and exponent parts are always interpreted using radix " +"10. For example, ``077e010`` is legal, and denotes the same number as " +"``77e10``. The allowed range of floating point literals is implementation-" +"dependent. As in integer literals, underscores are supported for digit " +"grouping." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:776 +msgid "Some examples of floating point literals::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:780 +msgid "" +"Note that numeric literals do not include a sign; a phrase like ``-1`` is " +"actually an expression composed of the unary operator ``-`` and the literal " +"``1``." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:791 +msgid "Imaginary literals" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:793 +msgid "Imaginary literals are described by the following lexical definitions:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:798 +msgid "" +"An imaginary literal yields a complex number with a real part of 0.0. " +"Complex numbers are represented as a pair of floating point numbers and have " +"the same restrictions on their range. To create a complex number with a " +"nonzero real part, add a floating point number to it, e.g., ``(3+4j)``. " +"Some examples of imaginary literals::" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:810 +msgid "Operators" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:814 +msgid "The following tokens are operators:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:827 +msgid "Delimiters" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:831 +msgid "The following tokens serve as delimiters in the grammar:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:840 +msgid "" +"The period can also occur in floating-point and imaginary literals. A " +"sequence of three periods has a special meaning as an ellipsis literal. The " +"second half of the list, the augmented assignment operators, serve lexically " +"as delimiters, but also perform an operation." +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:845 +msgid "" +"The following printing ASCII characters have special meaning as part of " +"other tokens or are otherwise significant to the lexical analyzer:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:852 +msgid "" +"The following printing ASCII characters are not used in Python. Their " +"occurrence outside string literals and comments is an unconditional error:" +msgstr "" + +#: ../Doc/reference/lexical_analysis.rst:862 +msgid "http://www.unicode.org/Public/8.0.0/ucd/NameAliases.txt" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:6 +msgid "Simple statements" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:10 +msgid "" +"A simple statement is comprised within a single logical line. Several simple " +"statements may occur on a single line separated by semicolons. The syntax " +"for simple statements is:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:35 +msgid "Expression statements" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:42 +msgid "" +"Expression statements are used (mostly interactively) to compute and write a " +"value, or (usually) to call a procedure (a function that returns no " +"meaningful result; in Python, procedures return the value ``None``). Other " +"uses of expression statements are allowed and occasionally useful. The " +"syntax for an expression statement is:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:51 +msgid "" +"An expression statement evaluates the expression list (which may be a single " +"expression)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:63 +msgid "" +"In interactive mode, if the value is not ``None``, it is converted to a " +"string using the built-in :func:`repr` function and the resulting string is " +"written to standard output on a line by itself (except if the result is " +"``None``, so that procedure calls do not cause any output.)" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:71 +msgid "Assignment statements" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:81 +msgid "" +"Assignment statements are used to (re)bind names to values and to modify " +"attributes or items of mutable objects:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:95 +msgid "" +"(See section :ref:`primaries` for the syntax definitions for *attributeref*, " +"*subscription*, and *slicing*.)" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:98 +msgid "" +"An assignment statement evaluates the expression list (remember that this " +"can be a single expression or a comma-separated list, the latter yielding a " +"tuple) and assigns the single resulting object to each of the target lists, " +"from left to right." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:107 +msgid "" +"Assignment is defined recursively depending on the form of the target " +"(list). When a target is part of a mutable object (an attribute reference, " +"subscription or slicing), the mutable object must ultimately perform the " +"assignment and decide about its validity, and may raise an exception if the " +"assignment is unacceptable. The rules observed by various types and the " +"exceptions raised are given with the definition of the object types (see " +"section :ref:`types`)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:116 +msgid "" +"Assignment of an object to a target list, optionally enclosed in parentheses " +"or square brackets, is recursively defined as follows." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:119 +msgid "If the target list is empty: The object must also be an empty iterable." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:121 +msgid "" +"If the target list is a single target in parentheses: The object is assigned " +"to that target." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:124 +msgid "" +"If the target list is a comma-separated list of targets, or a single target " +"in square brackets: The object must be an iterable with the same number of " +"items as there are targets in the target list, and the items are assigned, " +"from left to right, to the corresponding targets." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:129 +msgid "" +"If the target list contains one target prefixed with an asterisk, called a " +"\"starred\" target: The object must be an iterable with at least as many " +"items as there are targets in the target list, minus one. The first items " +"of the iterable are assigned, from left to right, to the targets before the " +"starred target. The final items of the iterable are assigned to the targets " +"after the starred target. A list of the remaining items in the iterable is " +"then assigned to the starred target (the list can be empty)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:137 +msgid "" +"Else: The object must be an iterable with the same number of items as there " +"are targets in the target list, and the items are assigned, from left to " +"right, to the corresponding targets." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:141 +msgid "" +"Assignment of an object to a single target is recursively defined as follows." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:143 +msgid "If the target is an identifier (name):" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:145 +msgid "" +"If the name does not occur in a :keyword:`global` or :keyword:`nonlocal` " +"statement in the current code block: the name is bound to the object in the " +"current local namespace." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:149 +msgid "" +"Otherwise: the name is bound to the object in the global namespace or the " +"outer namespace determined by :keyword:`nonlocal`, respectively." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:154 +msgid "" +"The name is rebound if it was already bound. This may cause the reference " +"count for the object previously bound to the name to reach zero, causing the " +"object to be deallocated and its destructor (if it has one) to be called." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:160 +msgid "" +"If the target is an attribute reference: The primary expression in the " +"reference is evaluated. It should yield an object with assignable " +"attributes; if this is not the case, :exc:`TypeError` is raised. That " +"object is then asked to assign the assigned object to the given attribute; " +"if it cannot perform the assignment, it raises an exception (usually but not " +"necessarily :exc:`AttributeError`)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:169 +msgid "" +"Note: If the object is a class instance and the attribute reference occurs " +"on both sides of the assignment operator, the RHS expression, ``a.x`` can " +"access either an instance attribute or (if no instance attribute exists) a " +"class attribute. The LHS target ``a.x`` is always set as an instance " +"attribute, creating it if necessary. Thus, the two occurrences of ``a.x`` " +"do not necessarily refer to the same attribute: if the RHS expression refers " +"to a class attribute, the LHS creates a new instance attribute as the target " +"of the assignment::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:183 +msgid "" +"This description does not necessarily apply to descriptor attributes, such " +"as properties created with :func:`property`." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:190 +msgid "" +"If the target is a subscription: The primary expression in the reference is " +"evaluated. It should yield either a mutable sequence object (such as a " +"list) or a mapping object (such as a dictionary). Next, the subscript " +"expression is evaluated." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:199 +msgid "" +"If the primary is a mutable sequence object (such as a list), the subscript " +"must yield an integer. If it is negative, the sequence's length is added to " +"it. The resulting value must be a nonnegative integer less than the " +"sequence's length, and the sequence is asked to assign the assigned object " +"to its item with that index. If the index is out of range, :exc:" +"`IndexError` is raised (assignment to a subscripted sequence cannot add new " +"items to a list)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:210 +msgid "" +"If the primary is a mapping object (such as a dictionary), the subscript " +"must have a type compatible with the mapping's key type, and the mapping is " +"then asked to create a key/datum pair which maps the subscript to the " +"assigned object. This can either replace an existing key/value pair with " +"the same key value, or insert a new key/value pair (if no key with the same " +"value existed)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:216 +msgid "" +"For user-defined objects, the :meth:`__setitem__` method is called with " +"appropriate arguments." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:221 +msgid "" +"If the target is a slicing: The primary expression in the reference is " +"evaluated. It should yield a mutable sequence object (such as a list). The " +"assigned object should be a sequence object of the same type. Next, the " +"lower and upper bound expressions are evaluated, insofar they are present; " +"defaults are zero and the sequence's length. The bounds should evaluate to " +"integers. If either bound is negative, the sequence's length is added to " +"it. The resulting bounds are clipped to lie between zero and the sequence's " +"length, inclusive. Finally, the sequence object is asked to replace the " +"slice with the items of the assigned sequence. The length of the slice may " +"be different from the length of the assigned sequence, thus changing the " +"length of the target sequence, if the target sequence allows it." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:235 +msgid "" +"In the current implementation, the syntax for targets is taken to be the " +"same as for expressions, and invalid syntax is rejected during the code " +"generation phase, causing less detailed error messages." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:239 +msgid "" +"Although the definition of assignment implies that overlaps between the left-" +"hand side and the right-hand side are 'simultaneous' (for example ``a, b = " +"b, a`` swaps two variables), overlaps *within* the collection of assigned-to " +"variables occur left-to-right, sometimes resulting in confusion. For " +"instance, the following program prints ``[0, 2]``::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:253 +msgid ":pep:`3132` - Extended Iterable Unpacking" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:254 +msgid "The specification for the ``*target`` feature." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:260 +msgid "Augmented assignment statements" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:278 +msgid "" +"Augmented assignment is the combination, in a single statement, of a binary " +"operation and an assignment statement:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:287 +msgid "" +"(See section :ref:`primaries` for the syntax definitions of the last three " +"symbols.)" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:290 +msgid "" +"An augmented assignment evaluates the target (which, unlike normal " +"assignment statements, cannot be an unpacking) and the expression list, " +"performs the binary operation specific to the type of assignment on the two " +"operands, and assigns the result to the original target. The target is only " +"evaluated once." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:295 +msgid "" +"An augmented assignment expression like ``x += 1`` can be rewritten as ``x = " +"x + 1`` to achieve a similar, but not exactly equal effect. In the augmented " +"version, ``x`` is only evaluated once. Also, when possible, the actual " +"operation is performed *in-place*, meaning that rather than creating a new " +"object and assigning that to the target, the old object is modified instead." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:301 +msgid "" +"Unlike normal assignments, augmented assignments evaluate the left-hand side " +"*before* evaluating the right-hand side. For example, ``a[i] += f(x)`` " +"first looks-up ``a[i]``, then it evaluates ``f(x)`` and performs the " +"addition, and lastly, it writes the result back to ``a[i]``." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:306 +msgid "" +"With the exception of assigning to tuples and multiple targets in a single " +"statement, the assignment done by augmented assignment statements is handled " +"the same way as normal assignments. Similarly, with the exception of the " +"possible *in-place* behavior, the binary operation performed by augmented " +"assignment is the same as the normal binary operations." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:312 +msgid "" +"For targets which are attribute references, the same :ref:`caveat about " +"class and instance attributes ` applies as for regular " +"assignments." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:319 +msgid "Annotated assignment statements" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:325 +msgid "" +"Annotation assignment is the combination, in a single statement, of a " +"variable or attribute annotation and an optional assignment statement:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:331 +msgid "" +"The difference from normal :ref:`assignment` is that only single target and " +"only single right hand side value is allowed." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:334 +msgid "" +"For simple names as assignment targets, if in class or module scope, the " +"annotations are evaluated and stored in a special class or module attribute :" +"attr:`__annotations__` that is a dictionary mapping from variable names " +"(mangled if private) to evaluated annotations. This attribute is writable " +"and is automatically created at the start of class or module body execution, " +"if annotations are found statically." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:342 +msgid "" +"For expressions as assignment targets, the annotations are evaluated if in " +"class or module scope, but not stored." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:345 +msgid "" +"If a name is annotated in a function scope, then this name is local for that " +"scope. Annotations are never evaluated and stored in function scopes." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:348 +msgid "" +"If the right hand side is present, an annotated assignment performs the " +"actual assignment before evaluating annotations (where applicable). If the " +"right hand side is not present for an expression target, then the " +"interpreter evaluates the target except for the last :meth:`__setitem__` or :" +"meth:`__setattr__` call." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:356 +msgid "" +":pep:`526` - Variable and attribute annotation syntax :pep:`484` - Type hints" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:363 +msgid "The :keyword:`assert` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:369 +msgid "" +"Assert statements are a convenient way to insert debugging assertions into a " +"program:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:375 +msgid "The simple form, ``assert expression``, is equivalent to ::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:380 +msgid "" +"The extended form, ``assert expression1, expression2``, is equivalent to ::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:389 +msgid "" +"These equivalences assume that :const:`__debug__` and :exc:`AssertionError` " +"refer to the built-in variables with those names. In the current " +"implementation, the built-in variable :const:`__debug__` is ``True`` under " +"normal circumstances, ``False`` when optimization is requested (command line " +"option -O). The current code generator emits no code for an assert " +"statement when optimization is requested at compile time. Note that it is " +"unnecessary to include the source code for the expression that failed in the " +"error message; it will be displayed as part of the stack trace." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:398 +msgid "" +"Assignments to :const:`__debug__` are illegal. The value for the built-in " +"variable is determined when the interpreter starts." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:405 +msgid "The :keyword:`pass` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:415 +msgid "" +":keyword:`pass` is a null operation --- when it is executed, nothing " +"happens. It is useful as a placeholder when a statement is required " +"syntactically, but no code needs to be executed, for example::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:427 +msgid "The :keyword:`del` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:437 +msgid "" +"Deletion is recursively defined very similar to the way assignment is " +"defined. Rather than spelling it out in full details, here are some hints." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:440 +msgid "" +"Deletion of a target list recursively deletes each target, from left to " +"right." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:446 +msgid "" +"Deletion of a name removes the binding of that name from the local or global " +"namespace, depending on whether the name occurs in a :keyword:`global` " +"statement in the same code block. If the name is unbound, a :exc:" +"`NameError` exception will be raised." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:453 +msgid "" +"Deletion of attribute references, subscriptions and slicings is passed to " +"the primary object involved; deletion of a slicing is in general equivalent " +"to assignment of an empty slice of the right type (but even this is " +"determined by the sliced object)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:458 +msgid "" +"Previously it was illegal to delete a name from the local namespace if it " +"occurs as a free variable in a nested block." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:466 +msgid "The :keyword:`return` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:476 +msgid "" +":keyword:`return` may only occur syntactically nested in a function " +"definition, not within a nested class definition." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:479 +msgid "" +"If an expression list is present, it is evaluated, else ``None`` is " +"substituted." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:481 +msgid "" +":keyword:`return` leaves the current function call with the expression list " +"(or ``None``) as return value." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:486 +msgid "" +"When :keyword:`return` passes control out of a :keyword:`try` statement with " +"a :keyword:`finally` clause, that :keyword:`finally` clause is executed " +"before really leaving the function." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:490 +msgid "" +"In a generator function, the :keyword:`return` statement indicates that the " +"generator is done and will cause :exc:`StopIteration` to be raised. The " +"returned value (if any) is used as an argument to construct :exc:" +"`StopIteration` and becomes the :attr:`StopIteration.value` attribute." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:499 +msgid "The :keyword:`yield` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:511 +msgid "" +"A :keyword:`yield` statement is semantically equivalent to a :ref:`yield " +"expression `. The yield statement can be used to omit the " +"parentheses that would otherwise be required in the equivalent yield " +"expression statement. For example, the yield statements ::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:519 +msgid "are equivalent to the yield expression statements ::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:524 +msgid "" +"Yield expressions and statements are only used when defining a :term:" +"`generator` function, and are only used in the body of the generator " +"function. Using yield in a function definition is sufficient to cause that " +"definition to create a generator function instead of a normal function." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:529 +msgid "" +"For full details of :keyword:`yield` semantics, refer to the :ref:" +"`yieldexpr` section." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:535 +msgid "The :keyword:`raise` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:546 +msgid "" +"If no expressions are present, :keyword:`raise` re-raises the last exception " +"that was active in the current scope. If no exception is active in the " +"current scope, a :exc:`RuntimeError` exception is raised indicating that " +"this is an error." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:551 +msgid "" +"Otherwise, :keyword:`raise` evaluates the first expression as the exception " +"object. It must be either a subclass or an instance of :class:" +"`BaseException`. If it is a class, the exception instance will be obtained " +"when needed by instantiating the class with no arguments." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:556 +msgid "" +"The :dfn:`type` of the exception is the exception instance's class, the :dfn:" +"`value` is the instance itself." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:561 +msgid "" +"A traceback object is normally created automatically when an exception is " +"raised and attached to it as the :attr:`__traceback__` attribute, which is " +"writable. You can create an exception and set your own traceback in one step " +"using the :meth:`with_traceback` exception method (which returns the same " +"exception instance, with its traceback set to its argument), like so::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:573 +msgid "" +"The ``from`` clause is used for exception chaining: if given, the second " +"*expression* must be another exception class or instance, which will then be " +"attached to the raised exception as the :attr:`__cause__` attribute (which " +"is writable). If the raised exception is not handled, both exceptions will " +"be printed::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:594 +msgid "" +"A similar mechanism works implicitly if an exception is raised inside an " +"exception handler or a :keyword:`finally` clause: the previous exception is " +"then attached as the new exception's :attr:`__context__` attribute::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:613 +msgid "" +"Additional information on exceptions can be found in section :ref:" +"`exceptions`, and information about handling exceptions is in section :ref:" +"`try`." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:620 +msgid "The :keyword:`break` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:631 +msgid "" +":keyword:`break` may only occur syntactically nested in a :keyword:`for` or :" +"keyword:`while` loop, but not nested in a function or class definition " +"within that loop." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:638 +msgid "" +"It terminates the nearest enclosing loop, skipping the optional :keyword:" +"`else` clause if the loop has one." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:641 +msgid "" +"If a :keyword:`for` loop is terminated by :keyword:`break`, the loop control " +"target keeps its current value." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:646 +msgid "" +"When :keyword:`break` passes control out of a :keyword:`try` statement with " +"a :keyword:`finally` clause, that :keyword:`finally` clause is executed " +"before really leaving the loop." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:654 +msgid "The :keyword:`continue` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:666 +msgid "" +":keyword:`continue` may only occur syntactically nested in a :keyword:`for` " +"or :keyword:`while` loop, but not nested in a function or class definition " +"or :keyword:`finally` clause within that loop. It continues with the next " +"cycle of the nearest enclosing loop." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:671 +msgid "" +"When :keyword:`continue` passes control out of a :keyword:`try` statement " +"with a :keyword:`finally` clause, that :keyword:`finally` clause is executed " +"before really starting the next loop cycle." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:680 +msgid "The :keyword:`import` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:699 +msgid "" +"The basic import statement (no :keyword:`from` clause) is executed in two " +"steps:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:702 +msgid "find a module, loading and initializing it if necessary" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:703 +msgid "" +"define a name or names in the local namespace for the scope where the :" +"keyword:`import` statement occurs." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:706 +msgid "" +"When the statement contains multiple clauses (separated by commas) the two " +"steps are carried out separately for each clause, just as though the clauses " +"had been separated out into individual import statements." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:711 +msgid "" +"The details of the first step, finding and loading modules are described in " +"greater detail in the section on the :ref:`import system `, " +"which also describes the various types of packages and modules that can be " +"imported, as well as all the hooks that can be used to customize the import " +"system. Note that failures in this step may indicate either that the module " +"could not be located, *or* that an error occurred while initializing the " +"module, which includes execution of the module's code." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:719 +msgid "" +"If the requested module is retrieved successfully, it will be made available " +"in the local namespace in one of three ways:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:724 +msgid "" +"If the module name is followed by :keyword:`as`, then the name following :" +"keyword:`as` is bound directly to the imported module." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:726 +msgid "" +"If no other name is specified, and the module being imported is a top level " +"module, the module's name is bound in the local namespace as a reference to " +"the imported module" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:729 +msgid "" +"If the module being imported is *not* a top level module, then the name of " +"the top level package that contains the module is bound in the local " +"namespace as a reference to the top level package. The imported module must " +"be accessed using its full qualified name rather than directly" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:740 +msgid "The :keyword:`from` form uses a slightly more complex process:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:742 +msgid "" +"find the module specified in the :keyword:`from` clause, loading and " +"initializing it if necessary;" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:744 +msgid "for each of the identifiers specified in the :keyword:`import` clauses:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:746 +msgid "check if the imported module has an attribute by that name" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:747 +msgid "" +"if not, attempt to import a submodule with that name and then check the " +"imported module again for that attribute" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:749 +msgid "if the attribute is not found, :exc:`ImportError` is raised." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:750 +msgid "" +"otherwise, a reference to that value is stored in the local namespace, using " +"the name in the :keyword:`as` clause if it is present, otherwise using the " +"attribute name" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:754 +msgid "Examples::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:762 +msgid "" +"If the list of identifiers is replaced by a star (``'*'``), all public names " +"defined in the module are bound in the local namespace for the scope where " +"the :keyword:`import` statement occurs." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:768 +msgid "" +"The *public names* defined by a module are determined by checking the " +"module's namespace for a variable named ``__all__``; if defined, it must be " +"a sequence of strings which are names defined or imported by that module. " +"The names given in ``__all__`` are all considered public and are required to " +"exist. If ``__all__`` is not defined, the set of public names includes all " +"names found in the module's namespace which do not begin with an underscore " +"character (``'_'``). ``__all__`` should contain the entire public API. It " +"is intended to avoid accidentally exporting items that are not part of the " +"API (such as library modules which were imported and used within the module)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:778 +msgid "" +"The wild card form of import --- ``from module import *`` --- is only " +"allowed at the module level. Attempting to use it in class or function " +"definitions will raise a :exc:`SyntaxError`." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:785 +msgid "" +"When specifying what module to import you do not have to specify the " +"absolute name of the module. When a module or package is contained within " +"another package it is possible to make a relative import within the same top " +"package without having to mention the package name. By using leading dots in " +"the specified module or package after :keyword:`from` you can specify how " +"high to traverse up the current package hierarchy without specifying exact " +"names. One leading dot means the current package where the module making the " +"import exists. Two dots means up one package level. Three dots is up two " +"levels, etc. So if you execute ``from . import mod`` from a module in the " +"``pkg`` package then you will end up importing ``pkg.mod``. If you execute " +"``from ..subpkg2 import mod`` from within ``pkg.subpkg1`` you will import " +"``pkg.subpkg2.mod``. The specification for relative imports is contained " +"within :pep:`328`." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:798 +msgid "" +":func:`importlib.import_module` is provided to support applications that " +"determine dynamically the modules to be loaded." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:805 +msgid "Future statements" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:809 +msgid "" +"A :dfn:`future statement` is a directive to the compiler that a particular " +"module should be compiled using syntax or semantics that will be available " +"in a specified future release of Python where the feature becomes standard." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:813 +msgid "" +"The future statement is intended to ease migration to future versions of " +"Python that introduce incompatible changes to the language. It allows use " +"of the new features on a per-module basis before the release in which the " +"feature becomes standard." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:826 +msgid "" +"A future statement must appear near the top of the module. The only lines " +"that can appear before a future statement are:" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:829 +msgid "the module docstring (if any)," +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:830 +msgid "comments," +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:831 +msgid "blank lines, and" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:832 +msgid "other future statements." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:836 +msgid "" +"The features recognized by Python 3.0 are ``absolute_import``, ``division``, " +"``generators``, ``unicode_literals``, ``print_function``, ``nested_scopes`` " +"and ``with_statement``. They are all redundant because they are always " +"enabled, and only kept for backwards compatibility." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:841 +msgid "" +"A future statement is recognized and treated specially at compile time: " +"Changes to the semantics of core constructs are often implemented by " +"generating different code. It may even be the case that a new feature " +"introduces new incompatible syntax (such as a new reserved word), in which " +"case the compiler may need to parse the module differently. Such decisions " +"cannot be pushed off until runtime." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:848 +msgid "" +"For any given release, the compiler knows which feature names have been " +"defined, and raises a compile-time error if a future statement contains a " +"feature not known to it." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:852 +msgid "" +"The direct runtime semantics are the same as for any import statement: there " +"is a standard module :mod:`__future__`, described later, and it will be " +"imported in the usual way at the time the future statement is executed." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:856 +msgid "" +"The interesting runtime semantics depend on the specific feature enabled by " +"the future statement." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:859 +msgid "Note that there is nothing special about the statement::" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:863 +msgid "" +"That is not a future statement; it's an ordinary import statement with no " +"special semantics or syntax restrictions." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:866 +msgid "" +"Code compiled by calls to the built-in functions :func:`exec` and :func:" +"`compile` that occur in a module :mod:`M` containing a future statement " +"will, by default, use the new syntax or semantics associated with the future " +"statement. This can be controlled by optional arguments to :func:`compile` " +"--- see the documentation of that function for details." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:872 +msgid "" +"A future statement typed at an interactive interpreter prompt will take " +"effect for the rest of the interpreter session. If an interpreter is " +"started with the :option:`-i` option, is passed a script name to execute, " +"and the script includes a future statement, it will be in effect in the " +"interactive session started after the script is executed." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:880 +msgid ":pep:`236` - Back to the __future__" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:881 +msgid "The original proposal for the __future__ mechanism." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:887 +msgid "The :keyword:`global` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:896 +msgid "" +"The :keyword:`global` statement is a declaration which holds for the entire " +"current code block. It means that the listed identifiers are to be " +"interpreted as globals. It would be impossible to assign to a global " +"variable without :keyword:`global`, although free variables may refer to " +"globals without being declared global." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:902 +msgid "" +"Names listed in a :keyword:`global` statement must not be used in the same " +"code block textually preceding that :keyword:`global` statement." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:905 +msgid "" +"Names listed in a :keyword:`global` statement must not be defined as formal " +"parameters or in a :keyword:`for` loop control target, :keyword:`class` " +"definition, function definition, :keyword:`import` statement, or variable " +"annotation." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:912 +msgid "" +"The current implementation does not enforce some of these restriction, but " +"programs should not abuse this freedom, as future implementations may " +"enforce them or silently change the meaning of the program." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:921 +msgid "" +"**Programmer's note:** the :keyword:`global` is a directive to the parser. " +"It applies only to code parsed at the same time as the :keyword:`global` " +"statement. In particular, a :keyword:`global` statement contained in a " +"string or code object supplied to the built-in :func:`exec` function does " +"not affect the code block *containing* the function call, and code contained " +"in such a string is unaffected by :keyword:`global` statements in the code " +"containing the function call. The same applies to the :func:`eval` and :" +"func:`compile` functions." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:933 +msgid "The :keyword:`nonlocal` statement" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:944 +msgid "" +"The :keyword:`nonlocal` statement causes the listed identifiers to refer to " +"previously bound variables in the nearest enclosing scope excluding globals. " +"This is important because the default behavior for binding is to search the " +"local namespace first. The statement allows encapsulated code to rebind " +"variables outside of the local scope besides the global (module) scope." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:954 +msgid "" +"Names listed in a :keyword:`nonlocal` statement, unlike those listed in a :" +"keyword:`global` statement, must refer to pre-existing bindings in an " +"enclosing scope (the scope in which a new binding should be created cannot " +"be determined unambiguously)." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:959 +msgid "" +"Names listed in a :keyword:`nonlocal` statement must not collide with pre-" +"existing bindings in the local scope." +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:964 +msgid ":pep:`3104` - Access to Names in Outer Scopes" +msgstr "" + +#: ../Doc/reference/simple_stmts.rst:965 +msgid "The specification for the :keyword:`nonlocal` statement." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:6 +msgid "Top-level components" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:10 +msgid "" +"The Python interpreter can get its input from a number of sources: from a " +"script passed to it as standard input or as program argument, typed in " +"interactively, from a module source file, etc. This chapter gives the " +"syntax used in these cases." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:19 +msgid "Complete Python programs" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:28 +msgid "" +"While a language specification need not prescribe how the language " +"interpreter is invoked, it is useful to have a notion of a complete Python " +"program. A complete Python program is executed in a minimally initialized " +"environment: all built-in and standard modules are available, but none have " +"been initialized, except for :mod:`sys` (various system services), :mod:" +"`builtins` (built-in functions, exceptions and ``None``) and :mod:" +"`__main__`. The latter is used to provide the local and global namespace " +"for execution of the complete program." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:36 +msgid "" +"The syntax for a complete Python program is that for file input, described " +"in the next section." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:43 +msgid "" +"The interpreter may also be invoked in interactive mode; in this case, it " +"does not read and execute a complete program but reads and executes one " +"statement (possibly compound) at a time. The initial environment is " +"identical to that of a complete program; each statement is executed in the " +"namespace of :mod:`__main__`." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:54 +msgid "" +"Under Unix, a complete program can be passed to the interpreter in three " +"forms: with the :option:`-c` *string* command line option, as a file passed " +"as the first command line argument, or as standard input. If the file or " +"standard input is a tty device, the interpreter enters interactive mode; " +"otherwise, it executes the file as a complete program." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:64 +msgid "File input" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:66 +msgid "All input read from non-interactive files has the same form:" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:71 +msgid "This syntax is used in the following situations:" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:73 +msgid "when parsing a complete Python program (from a file or from a string);" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:75 +msgid "when parsing a module;" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:77 +msgid "when parsing a string passed to the :func:`exec` function;" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:83 +msgid "Interactive input" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:85 +msgid "Input in interactive mode is parsed using the following grammar:" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:90 +msgid "" +"Note that a (top-level) compound statement must be followed by a blank line " +"in interactive mode; this is needed to help the parser detect the end of the " +"input." +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:97 +msgid "Expression input" +msgstr "" + +#: ../Doc/reference/toplevel_components.rst:102 +msgid "" +":func:`eval` is used for expression input. It ignores leading whitespace. " +"The string argument to :func:`eval` must have the following form:" +msgstr "" diff --git a/sphinx.po b/sphinx.po new file mode 100644 index 00000000..68bfe76d --- /dev/null +++ b/sphinx.po @@ -0,0 +1,265 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/tools/templates/customsourcelink.html:3 +msgid "This Page" +msgstr "" + +#: ../Doc/tools/templates/customsourcelink.html:5 +msgid "Report a Bug" +msgstr "" + +#: ../Doc/tools/templates/customsourcelink.html:7 +msgid "Show Source" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:1 +msgid "Download" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:2 +msgid "Download these documents" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:3 +msgid "Docs for other versions" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:5 +msgid "Python 2.7 (stable)" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:6 +msgid "Python 3.4 (stable)" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:7 +msgid "Old versions" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:10 +msgid "Other resources" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:13 +msgid "PEP Index" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:14 +msgid "Beginner's Guide" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:15 +msgid "Book List" +msgstr "" + +#: ../Doc/tools/templates/indexsidebar.html:16 +msgid "Audio/Visual Talks" +msgstr "" + +#: ../Doc/tools/templates/layout.html:9 +msgid "Documentation " +msgstr "" + +#: ../Doc/tools/templates/layout.html:20 +msgid "Quick search" +msgstr "" + +#: ../Doc/tools/templates/layout.html:21 +msgid "Go" +msgstr "" + +#: ../Doc/tools/templates/layout.html:106 +#: ../Doc/tools/templates/indexcontent.html:56 +msgid "Copyright" +msgstr "" + +#: ../Doc/tools/templates/layout.html:108 +msgid "The Python Software Foundation is a non-profit corporation." +msgstr "" + +#: ../Doc/tools/templates/layout.html:109 +msgid "Please donate." +msgstr "" + +#: ../Doc/tools/templates/layout.html:111 +msgid "Last updated on %(last_updated)s." +msgstr "" + +#: ../Doc/tools/templates/layout.html:112 +msgid "Found a bug?" +msgstr "" + +#: ../Doc/tools/templates/layout.html:114 +msgid "" +"Created using Sphinx " +"%(sphinx_version)s." +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:3 +msgid "Parts of the documentation:" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:6 +msgid "What's new in Python %(version)s?" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:7 +msgid "" +"or all \"What's new\" documents since 2.0" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:8 +msgid "Tutorial" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:9 +msgid "start here" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:10 +msgid "Library Reference" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:11 +msgid "keep this under your pillow" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:12 +msgid "Language Reference" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:13 +msgid "describes syntax and language elements" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:14 +msgid "Python Setup and Usage" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:15 +msgid "how to use Python on different platforms" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:16 +msgid "Python HOWTOs" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:17 +msgid "in-depth documents on specific topics" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:19 +msgid "Installing Python Modules" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:20 +msgid "installing from the Python Package Index & other sources" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:21 +msgid "Distributing Python Modules" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:22 +msgid "publishing modules for installation by others" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:23 +msgid "Extending and Embedding" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:24 +msgid "tutorial for C/C++ programmers" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:25 +msgid "Python/C API" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:26 +msgid "reference for C/C++ programmers" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:27 +msgid "FAQs" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:28 +msgid "frequently asked questions (with answers!)" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:32 +msgid "Indices and tables:" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:35 +msgid "Global Module Index" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:36 +msgid "quick access to all modules" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:37 +msgid "General Index" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:38 +msgid "all functions, classes, terms" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:39 +msgid "Glossary" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:40 +msgid "the most important terms explained" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:42 +msgid "Search page" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:43 +msgid "search this documentation" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:44 +msgid "Complete Table of Contents" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:45 +msgid "lists all sections and subsections" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:49 +msgid "Meta information:" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:52 +msgid "Reporting bugs" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:53 +msgid "About the documentation" +msgstr "" + +#: ../Doc/tools/templates/indexcontent.html:55 +msgid "History and License of Python" +msgstr "" diff --git a/tutorial.po b/tutorial.po new file mode 100644 index 00000000..4f5b3022 --- /dev/null +++ b/tutorial.po @@ -0,0 +1,5596 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/tutorial/appendix.rst:5 +msgid "Appendix" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:11 ../Doc/tutorial/interpreter.rst:90 +msgid "Interactive Mode" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:16 +msgid "Error Handling" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:18 +msgid "" +"When an error occurs, the interpreter prints an error message and a stack " +"trace. In interactive mode, it then returns to the primary prompt; when " +"input came from a file, it exits with a nonzero exit status after printing " +"the stack trace. (Exceptions handled by an :keyword:`except` clause in a :" +"keyword:`try` statement are not errors in this context.) Some errors are " +"unconditionally fatal and cause an exit with a nonzero exit; this applies to " +"internal inconsistencies and some cases of running out of memory. All error " +"messages are written to the standard error stream; normal output from " +"executed commands is written to standard output." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:28 +msgid "" +"Typing the interrupt character (usually :kbd:`Control-C` or :kbd:`Delete`) " +"to the primary or secondary prompt cancels the input and returns to the " +"primary prompt. [#]_ Typing an interrupt while a command is executing raises " +"the :exc:`KeyboardInterrupt` exception, which may be handled by a :keyword:" +"`try` statement." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:38 +msgid "Executable Python Scripts" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:40 +msgid "" +"On BSD'ish Unix systems, Python scripts can be made directly executable, " +"like shell scripts, by putting the line ::" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:45 +msgid "" +"(assuming that the interpreter is on the user's :envvar:`PATH`) at the " +"beginning of the script and giving the file an executable mode. The ``#!`` " +"must be the first two characters of the file. On some platforms, this first " +"line must end with a Unix-style line ending (``'\\n'``), not a Windows " +"(``'\\r\\n'``) line ending. Note that the hash, or pound, character, " +"``'#'``, is used to start a comment in Python." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:52 +msgid "" +"The script can be given an executable mode, or permission, using the :" +"program:`chmod` command." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:59 +msgid "" +"On Windows systems, there is no notion of an \"executable mode\". The " +"Python installer automatically associates ``.py`` files with ``python.exe`` " +"so that a double-click on a Python file will run it as a script. The " +"extension can also be ``.pyw``, in that case, the console window that " +"normally appears is suppressed." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:69 +msgid "The Interactive Startup File" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:71 +msgid "" +"When you use Python interactively, it is frequently handy to have some " +"standard commands executed every time the interpreter is started. You can " +"do this by setting an environment variable named :envvar:`PYTHONSTARTUP` to " +"the name of a file containing your start-up commands. This is similar to " +"the :file:`.profile` feature of the Unix shells." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:77 +msgid "" +"This file is only read in interactive sessions, not when Python reads " +"commands from a script, and not when :file:`/dev/tty` is given as the " +"explicit source of commands (which otherwise behaves like an interactive " +"session). It is executed in the same namespace where interactive commands " +"are executed, so that objects that it defines or imports can be used without " +"qualification in the interactive session. You can also change the prompts " +"``sys.ps1`` and ``sys.ps2`` in this file." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:85 +msgid "" +"If you want to read an additional start-up file from the current directory, " +"you can program this in the global start-up file using code like ``if os." +"path.isfile('.pythonrc.py'): exec(open('.pythonrc.py').read())``. If you " +"want to use the startup file in a script, you must do this explicitly in the " +"script::" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:102 +msgid "The Customization Modules" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:104 +msgid "" +"Python provides two hooks to let you customize it: :mod:`sitecustomize` and :" +"mod:`usercustomize`. To see how it works, you need first to find the " +"location of your user site-packages directory. Start Python and run this " +"code::" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:112 +msgid "" +"Now you can create a file named :file:`usercustomize.py` in that directory " +"and put anything you want in it. It will affect every invocation of Python, " +"unless it is started with the :option:`-s` option to disable the automatic " +"import." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:116 +msgid "" +":mod:`sitecustomize` works in the same way, but is typically created by an " +"administrator of the computer in the global site-packages directory, and is " +"imported before :mod:`usercustomize`. See the documentation of the :mod:" +"`site` module for more details." +msgstr "" + +#: ../Doc/tutorial/appendix.rst:123 ../Doc/tutorial/classes.rst:952 +#: ../Doc/tutorial/controlflow.rst:759 ../Doc/tutorial/datastructures.rst:707 +#: ../Doc/tutorial/interpreter.rst:162 ../Doc/tutorial/introduction.rst:529 +#: ../Doc/tutorial/modules.rst:550 +msgid "Footnotes" +msgstr "" + +#: ../Doc/tutorial/appendix.rst:124 +msgid "A problem with the GNU Readline package may prevent this." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:5 +msgid "Whetting Your Appetite" +msgstr "" + +#: ../Doc/tutorial/appetite.rst:7 +msgid "" +"If you do much work on computers, eventually you find that there's some task " +"you'd like to automate. For example, you may wish to perform a search-and-" +"replace over a large number of text files, or rename and rearrange a bunch " +"of photo files in a complicated way. Perhaps you'd like to write a small " +"custom database, or a specialized GUI application, or a simple game." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:13 +msgid "" +"If you're a professional software developer, you may have to work with " +"several C/C++/Java libraries but find the usual write/compile/test/re-" +"compile cycle is too slow. Perhaps you're writing a test suite for such a " +"library and find writing the testing code a tedious task. Or maybe you've " +"written a program that could use an extension language, and you don't want " +"to design and implement a whole new language for your application." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:20 +msgid "Python is just the language for you." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:22 +msgid "" +"You could write a Unix shell script or Windows batch files for some of these " +"tasks, but shell scripts are best at moving around files and changing text " +"data, not well-suited for GUI applications or games. You could write a C/C++/" +"Java program, but it can take a lot of development time to get even a first-" +"draft program. Python is simpler to use, available on Windows, Mac OS X, " +"and Unix operating systems, and will help you get the job done more quickly." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:29 +msgid "" +"Python is simple to use, but it is a real programming language, offering " +"much more structure and support for large programs than shell scripts or " +"batch files can offer. On the other hand, Python also offers much more " +"error checking than C, and, being a *very-high-level language*, it has high-" +"level data types built in, such as flexible arrays and dictionaries. " +"Because of its more general data types Python is applicable to a much larger " +"problem domain than Awk or even Perl, yet many things are at least as easy " +"in Python as in those languages." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:37 +msgid "" +"Python allows you to split your program into modules that can be reused in " +"other Python programs. It comes with a large collection of standard modules " +"that you can use as the basis of your programs --- or as examples to start " +"learning to program in Python. Some of these modules provide things like " +"file I/O, system calls, sockets, and even interfaces to graphical user " +"interface toolkits like Tk." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:44 +msgid "" +"Python is an interpreted language, which can save you considerable time " +"during program development because no compilation and linking is necessary. " +"The interpreter can be used interactively, which makes it easy to experiment " +"with features of the language, to write throw-away programs, or to test " +"functions during bottom-up program development. It is also a handy desk " +"calculator." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:50 +msgid "" +"Python enables programs to be written compactly and readably. Programs " +"written in Python are typically much shorter than equivalent C, C++, or " +"Java programs, for several reasons:" +msgstr "" + +#: ../Doc/tutorial/appetite.rst:54 +msgid "" +"the high-level data types allow you to express complex operations in a " +"single statement;" +msgstr "" + +#: ../Doc/tutorial/appetite.rst:57 +msgid "" +"statement grouping is done by indentation instead of beginning and ending " +"brackets;" +msgstr "" + +#: ../Doc/tutorial/appetite.rst:60 +msgid "no variable or argument declarations are necessary." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:62 +msgid "" +"Python is *extensible*: if you know how to program in C it is easy to add a " +"new built-in function or module to the interpreter, either to perform " +"critical operations at maximum speed, or to link Python programs to " +"libraries that may only be available in binary form (such as a vendor-" +"specific graphics library). Once you are really hooked, you can link the " +"Python interpreter into an application written in C and use it as an " +"extension or command language for that application." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:70 +msgid "" +"By the way, the language is named after the BBC show \"Monty Python's Flying " +"Circus\" and has nothing to do with reptiles. Making references to Monty " +"Python skits in documentation is not only allowed, it is encouraged!" +msgstr "" + +#: ../Doc/tutorial/appetite.rst:74 +msgid "" +"Now that you are all excited about Python, you'll want to examine it in some " +"more detail. Since the best way to learn a language is to use it, the " +"tutorial invites you to play with the Python interpreter as you read." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:78 +msgid "" +"In the next chapter, the mechanics of using the interpreter are explained. " +"This is rather mundane information, but essential for trying out the " +"examples shown later." +msgstr "" + +#: ../Doc/tutorial/appetite.rst:82 +msgid "" +"The rest of the tutorial introduces various features of the Python language " +"and system through examples, beginning with simple expressions, statements " +"and data types, through functions and modules, and finally touching upon " +"advanced concepts like exceptions and user-defined classes." +msgstr "" + +#: ../Doc/tutorial/classes.rst:5 +msgid "Classes" +msgstr "" + +#: ../Doc/tutorial/classes.rst:7 +msgid "" +"Compared with other programming languages, Python's class mechanism adds " +"classes with a minimum of new syntax and semantics. It is a mixture of the " +"class mechanisms found in C++ and Modula-3. Python classes provide all the " +"standard features of Object Oriented Programming: the class inheritance " +"mechanism allows multiple base classes, a derived class can override any " +"methods of its base class or classes, and a method can call the method of a " +"base class with the same name. Objects can contain arbitrary amounts and " +"kinds of data. As is true for modules, classes partake of the dynamic " +"nature of Python: they are created at runtime, and can be modified further " +"after creation." +msgstr "" + +#: ../Doc/tutorial/classes.rst:17 +msgid "" +"In C++ terminology, normally class members (including the data members) are " +"*public* (except see below :ref:`tut-private`), and all member functions are " +"*virtual*. As in Modula-3, there are no shorthands for referencing the " +"object's members from its methods: the method function is declared with an " +"explicit first argument representing the object, which is provided " +"implicitly by the call. As in Smalltalk, classes themselves are objects. " +"This provides semantics for importing and renaming. Unlike C++ and " +"Modula-3, built-in types can be used as base classes for extension by the " +"user. Also, like in C++, most built-in operators with special syntax " +"(arithmetic operators, subscripting etc.) can be redefined for class " +"instances." +msgstr "" + +#: ../Doc/tutorial/classes.rst:28 +msgid "" +"(Lacking universally accepted terminology to talk about classes, I will make " +"occasional use of Smalltalk and C++ terms. I would use Modula-3 terms, " +"since its object-oriented semantics are closer to those of Python than C++, " +"but I expect that few readers have heard of it.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:37 +msgid "A Word About Names and Objects" +msgstr "" + +#: ../Doc/tutorial/classes.rst:39 +msgid "" +"Objects have individuality, and multiple names (in multiple scopes) can be " +"bound to the same object. This is known as aliasing in other languages. " +"This is usually not appreciated on a first glance at Python, and can be " +"safely ignored when dealing with immutable basic types (numbers, strings, " +"tuples). However, aliasing has a possibly surprising effect on the " +"semantics of Python code involving mutable objects such as lists, " +"dictionaries, and most other types. This is usually used to the benefit of " +"the program, since aliases behave like pointers in some respects. For " +"example, passing an object is cheap since only a pointer is passed by the " +"implementation; and if a function modifies an object passed as an argument, " +"the caller will see the change --- this eliminates the need for two " +"different argument passing mechanisms as in Pascal." +msgstr "" + +#: ../Doc/tutorial/classes.rst:55 +msgid "Python Scopes and Namespaces" +msgstr "" + +#: ../Doc/tutorial/classes.rst:57 +msgid "" +"Before introducing classes, I first have to tell you something about " +"Python's scope rules. Class definitions play some neat tricks with " +"namespaces, and you need to know how scopes and namespaces work to fully " +"understand what's going on. Incidentally, knowledge about this subject is " +"useful for any advanced Python programmer." +msgstr "" + +#: ../Doc/tutorial/classes.rst:63 +msgid "Let's begin with some definitions." +msgstr "" + +#: ../Doc/tutorial/classes.rst:65 +msgid "" +"A *namespace* is a mapping from names to objects. Most namespaces are " +"currently implemented as Python dictionaries, but that's normally not " +"noticeable in any way (except for performance), and it may change in the " +"future. Examples of namespaces are: the set of built-in names (containing " +"functions such as :func:`abs`, and built-in exception names); the global " +"names in a module; and the local names in a function invocation. In a sense " +"the set of attributes of an object also form a namespace. The important " +"thing to know about namespaces is that there is absolutely no relation " +"between names in different namespaces; for instance, two different modules " +"may both define a function ``maximize`` without confusion --- users of the " +"modules must prefix it with the module name." +msgstr "" + +#: ../Doc/tutorial/classes.rst:76 +msgid "" +"By the way, I use the word *attribute* for any name following a dot --- for " +"example, in the expression ``z.real``, ``real`` is an attribute of the " +"object ``z``. Strictly speaking, references to names in modules are " +"attribute references: in the expression ``modname.funcname``, ``modname`` is " +"a module object and ``funcname`` is an attribute of it. In this case there " +"happens to be a straightforward mapping between the module's attributes and " +"the global names defined in the module: they share the same namespace! [#]_" +msgstr "" + +#: ../Doc/tutorial/classes.rst:84 +msgid "" +"Attributes may be read-only or writable. In the latter case, assignment to " +"attributes is possible. Module attributes are writable: you can write " +"``modname.the_answer = 42``. Writable attributes may also be deleted with " +"the :keyword:`del` statement. For example, ``del modname.the_answer`` will " +"remove the attribute :attr:`the_answer` from the object named by ``modname``." +msgstr "" + +#: ../Doc/tutorial/classes.rst:90 +msgid "" +"Namespaces are created at different moments and have different lifetimes. " +"The namespace containing the built-in names is created when the Python " +"interpreter starts up, and is never deleted. The global namespace for a " +"module is created when the module definition is read in; normally, module " +"namespaces also last until the interpreter quits. The statements executed " +"by the top-level invocation of the interpreter, either read from a script " +"file or interactively, are considered part of a module called :mod:" +"`__main__`, so they have their own global namespace. (The built-in names " +"actually also live in a module; this is called :mod:`builtins`.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:100 +msgid "" +"The local namespace for a function is created when the function is called, " +"and deleted when the function returns or raises an exception that is not " +"handled within the function. (Actually, forgetting would be a better way to " +"describe what actually happens.) Of course, recursive invocations each have " +"their own local namespace." +msgstr "" + +#: ../Doc/tutorial/classes.rst:106 +msgid "" +"A *scope* is a textual region of a Python program where a namespace is " +"directly accessible. \"Directly accessible\" here means that an unqualified " +"reference to a name attempts to find the name in the namespace." +msgstr "" + +#: ../Doc/tutorial/classes.rst:110 +msgid "" +"Although scopes are determined statically, they are used dynamically. At any " +"time during execution, there are at least three nested scopes whose " +"namespaces are directly accessible:" +msgstr "" + +#: ../Doc/tutorial/classes.rst:114 +msgid "the innermost scope, which is searched first, contains the local names" +msgstr "" + +#: ../Doc/tutorial/classes.rst:115 +msgid "" +"the scopes of any enclosing functions, which are searched starting with the " +"nearest enclosing scope, contains non-local, but also non-global names" +msgstr "" + +#: ../Doc/tutorial/classes.rst:117 +msgid "the next-to-last scope contains the current module's global names" +msgstr "" + +#: ../Doc/tutorial/classes.rst:118 +msgid "" +"the outermost scope (searched last) is the namespace containing built-in " +"names" +msgstr "" + +#: ../Doc/tutorial/classes.rst:120 +msgid "" +"If a name is declared global, then all references and assignments go " +"directly to the middle scope containing the module's global names. To " +"rebind variables found outside of the innermost scope, the :keyword:" +"`nonlocal` statement can be used; if not declared nonlocal, those variables " +"are read-only (an attempt to write to such a variable will simply create a " +"*new* local variable in the innermost scope, leaving the identically named " +"outer variable unchanged)." +msgstr "" + +#: ../Doc/tutorial/classes.rst:127 +msgid "" +"Usually, the local scope references the local names of the (textually) " +"current function. Outside functions, the local scope references the same " +"namespace as the global scope: the module's namespace. Class definitions " +"place yet another namespace in the local scope." +msgstr "" + +#: ../Doc/tutorial/classes.rst:132 +msgid "" +"It is important to realize that scopes are determined textually: the global " +"scope of a function defined in a module is that module's namespace, no " +"matter from where or by what alias the function is called. On the other " +"hand, the actual search for names is done dynamically, at run time --- " +"however, the language definition is evolving towards static name resolution, " +"at \"compile\" time, so don't rely on dynamic name resolution! (In fact, " +"local variables are already determined statically.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:140 +msgid "" +"A special quirk of Python is that -- if no :keyword:`global` statement is in " +"effect -- assignments to names always go into the innermost scope. " +"Assignments do not copy data --- they just bind names to objects. The same " +"is true for deletions: the statement ``del x`` removes the binding of ``x`` " +"from the namespace referenced by the local scope. In fact, all operations " +"that introduce new names use the local scope: in particular, :keyword:" +"`import` statements and function definitions bind the module or function " +"name in the local scope." +msgstr "" + +#: ../Doc/tutorial/classes.rst:148 +msgid "" +"The :keyword:`global` statement can be used to indicate that particular " +"variables live in the global scope and should be rebound there; the :keyword:" +"`nonlocal` statement indicates that particular variables live in an " +"enclosing scope and should be rebound there." +msgstr "" + +#: ../Doc/tutorial/classes.rst:156 +msgid "Scopes and Namespaces Example" +msgstr "" + +#: ../Doc/tutorial/classes.rst:158 +msgid "" +"This is an example demonstrating how to reference the different scopes and " +"namespaces, and how :keyword:`global` and :keyword:`nonlocal` affect " +"variable binding::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:185 +msgid "The output of the example code is:" +msgstr "" + +#: ../Doc/tutorial/classes.rst:194 +msgid "" +"Note how the *local* assignment (which is default) didn't change *scope_test*" +"\\'s binding of *spam*. The :keyword:`nonlocal` assignment changed " +"*scope_test*\\'s binding of *spam*, and the :keyword:`global` assignment " +"changed the module-level binding." +msgstr "" + +#: ../Doc/tutorial/classes.rst:199 +msgid "" +"You can also see that there was no previous binding for *spam* before the :" +"keyword:`global` assignment." +msgstr "" + +#: ../Doc/tutorial/classes.rst:206 +msgid "A First Look at Classes" +msgstr "" + +#: ../Doc/tutorial/classes.rst:208 +msgid "" +"Classes introduce a little bit of new syntax, three new object types, and " +"some new semantics." +msgstr "" + +#: ../Doc/tutorial/classes.rst:215 +msgid "Class Definition Syntax" +msgstr "" + +#: ../Doc/tutorial/classes.rst:217 +msgid "The simplest form of class definition looks like this::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:226 +msgid "" +"Class definitions, like function definitions (:keyword:`def` statements) " +"must be executed before they have any effect. (You could conceivably place " +"a class definition in a branch of an :keyword:`if` statement, or inside a " +"function.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:230 +msgid "" +"In practice, the statements inside a class definition will usually be " +"function definitions, but other statements are allowed, and sometimes useful " +"--- we'll come back to this later. The function definitions inside a class " +"normally have a peculiar form of argument list, dictated by the calling " +"conventions for methods --- again, this is explained later." +msgstr "" + +#: ../Doc/tutorial/classes.rst:236 +msgid "" +"When a class definition is entered, a new namespace is created, and used as " +"the local scope --- thus, all assignments to local variables go into this " +"new namespace. In particular, function definitions bind the name of the new " +"function here." +msgstr "" + +#: ../Doc/tutorial/classes.rst:241 +msgid "" +"When a class definition is left normally (via the end), a *class object* is " +"created. This is basically a wrapper around the contents of the namespace " +"created by the class definition; we'll learn more about class objects in the " +"next section. The original local scope (the one in effect just before the " +"class definition was entered) is reinstated, and the class object is bound " +"here to the class name given in the class definition header (:class:" +"`ClassName` in the example)." +msgstr "" + +#: ../Doc/tutorial/classes.rst:253 +msgid "Class Objects" +msgstr "" + +#: ../Doc/tutorial/classes.rst:255 +msgid "" +"Class objects support two kinds of operations: attribute references and " +"instantiation." +msgstr "" + +#: ../Doc/tutorial/classes.rst:258 +msgid "" +"*Attribute references* use the standard syntax used for all attribute " +"references in Python: ``obj.name``. Valid attribute names are all the names " +"that were in the class's namespace when the class object was created. So, " +"if the class definition looked like this::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:270 +msgid "" +"then ``MyClass.i`` and ``MyClass.f`` are valid attribute references, " +"returning an integer and a function object, respectively. Class attributes " +"can also be assigned to, so you can change the value of ``MyClass.i`` by " +"assignment. :attr:`__doc__` is also a valid attribute, returning the " +"docstring belonging to the class: ``\"A simple example class\"``." +msgstr "" + +#: ../Doc/tutorial/classes.rst:276 +msgid "" +"Class *instantiation* uses function notation. Just pretend that the class " +"object is a parameterless function that returns a new instance of the class. " +"For example (assuming the above class)::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:282 +msgid "" +"creates a new *instance* of the class and assigns this object to the local " +"variable ``x``." +msgstr "" + +#: ../Doc/tutorial/classes.rst:285 +msgid "" +"The instantiation operation (\"calling\" a class object) creates an empty " +"object. Many classes like to create objects with instances customized to a " +"specific initial state. Therefore a class may define a special method named :" +"meth:`__init__`, like this::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:293 +msgid "" +"When a class defines an :meth:`__init__` method, class instantiation " +"automatically invokes :meth:`__init__` for the newly-created class " +"instance. So in this example, a new, initialized instance can be obtained " +"by::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:299 +msgid "" +"Of course, the :meth:`__init__` method may have arguments for greater " +"flexibility. In that case, arguments given to the class instantiation " +"operator are passed on to :meth:`__init__`. For example, ::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:316 +msgid "Instance Objects" +msgstr "" + +#: ../Doc/tutorial/classes.rst:318 +msgid "" +"Now what can we do with instance objects? The only operations understood by " +"instance objects are attribute references. There are two kinds of valid " +"attribute names, data attributes and methods." +msgstr "" + +#: ../Doc/tutorial/classes.rst:322 +msgid "" +"*data attributes* correspond to \"instance variables\" in Smalltalk, and to " +"\"data members\" in C++. Data attributes need not be declared; like local " +"variables, they spring into existence when they are first assigned to. For " +"example, if ``x`` is the instance of :class:`MyClass` created above, the " +"following piece of code will print the value ``16``, without leaving a " +"trace::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:334 +msgid "" +"The other kind of instance attribute reference is a *method*. A method is a " +"function that \"belongs to\" an object. (In Python, the term method is not " +"unique to class instances: other object types can have methods as well. For " +"example, list objects have methods called append, insert, remove, sort, and " +"so on. However, in the following discussion, we'll use the term method " +"exclusively to mean methods of class instance objects, unless explicitly " +"stated otherwise.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:343 +msgid "" +"Valid method names of an instance object depend on its class. By " +"definition, all attributes of a class that are function objects define " +"corresponding methods of its instances. So in our example, ``x.f`` is a " +"valid method reference, since ``MyClass.f`` is a function, but ``x.i`` is " +"not, since ``MyClass.i`` is not. But ``x.f`` is not the same thing as " +"``MyClass.f`` --- it is a *method object*, not a function object." +msgstr "" + +#: ../Doc/tutorial/classes.rst:354 +msgid "Method Objects" +msgstr "" + +#: ../Doc/tutorial/classes.rst:356 +msgid "Usually, a method is called right after it is bound::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:360 +msgid "" +"In the :class:`MyClass` example, this will return the string ``'hello " +"world'``. However, it is not necessary to call a method right away: ``x.f`` " +"is a method object, and can be stored away and called at a later time. For " +"example::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:368 +msgid "will continue to print ``hello world`` until the end of time." +msgstr "" + +#: ../Doc/tutorial/classes.rst:370 +msgid "" +"What exactly happens when a method is called? You may have noticed that ``x." +"f()`` was called without an argument above, even though the function " +"definition for :meth:`f` specified an argument. What happened to the " +"argument? Surely Python raises an exception when a function that requires an " +"argument is called without any --- even if the argument isn't actually " +"used..." +msgstr "" + +#: ../Doc/tutorial/classes.rst:376 +msgid "" +"Actually, you may have guessed the answer: the special thing about methods " +"is that the object is passed as the first argument of the function. In our " +"example, the call ``x.f()`` is exactly equivalent to ``MyClass.f(x)``. In " +"general, calling a method with a list of *n* arguments is equivalent to " +"calling the corresponding function with an argument list that is created by " +"inserting the method's object before the first argument." +msgstr "" + +#: ../Doc/tutorial/classes.rst:383 +msgid "" +"If you still don't understand how methods work, a look at the implementation " +"can perhaps clarify matters. When an instance attribute is referenced that " +"isn't a data attribute, its class is searched. If the name denotes a valid " +"class attribute that is a function object, a method object is created by " +"packing (pointers to) the instance object and the function object just found " +"together in an abstract object: this is the method object. When the method " +"object is called with an argument list, a new argument list is constructed " +"from the instance object and the argument list, and the function object is " +"called with this new argument list." +msgstr "" + +#: ../Doc/tutorial/classes.rst:397 +msgid "Class and Instance Variables" +msgstr "" + +#: ../Doc/tutorial/classes.rst:399 +msgid "" +"Generally speaking, instance variables are for data unique to each instance " +"and class variables are for attributes and methods shared by all instances " +"of the class::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:421 +msgid "" +"As discussed in :ref:`tut-object`, shared data can have possibly surprising " +"effects with involving :term:`mutable` objects such as lists and " +"dictionaries. For example, the *tricks* list in the following code should " +"not be used as a class variable because just a single list would be shared " +"by all *Dog* instances::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:444 +msgid "Correct design of the class should use an instance variable instead::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:468 +msgid "Random Remarks" +msgstr "" + +#: ../Doc/tutorial/classes.rst:472 +msgid "" +"Data attributes override method attributes with the same name; to avoid " +"accidental name conflicts, which may cause hard-to-find bugs in large " +"programs, it is wise to use some kind of convention that minimizes the " +"chance of conflicts. Possible conventions include capitalizing method " +"names, prefixing data attribute names with a small unique string (perhaps " +"just an underscore), or using verbs for methods and nouns for data " +"attributes." +msgstr "" + +#: ../Doc/tutorial/classes.rst:479 +msgid "" +"Data attributes may be referenced by methods as well as by ordinary users " +"(\"clients\") of an object. In other words, classes are not usable to " +"implement pure abstract data types. In fact, nothing in Python makes it " +"possible to enforce data hiding --- it is all based upon convention. (On " +"the other hand, the Python implementation, written in C, can completely hide " +"implementation details and control access to an object if necessary; this " +"can be used by extensions to Python written in C.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:487 +msgid "" +"Clients should use data attributes with care --- clients may mess up " +"invariants maintained by the methods by stamping on their data attributes. " +"Note that clients may add data attributes of their own to an instance object " +"without affecting the validity of the methods, as long as name conflicts are " +"avoided --- again, a naming convention can save a lot of headaches here." +msgstr "" + +#: ../Doc/tutorial/classes.rst:493 +msgid "" +"There is no shorthand for referencing data attributes (or other methods!) " +"from within methods. I find that this actually increases the readability of " +"methods: there is no chance of confusing local variables and instance " +"variables when glancing through a method." +msgstr "" + +#: ../Doc/tutorial/classes.rst:498 +msgid "" +"Often, the first argument of a method is called ``self``. This is nothing " +"more than a convention: the name ``self`` has absolutely no special meaning " +"to Python. Note, however, that by not following the convention your code " +"may be less readable to other Python programmers, and it is also conceivable " +"that a *class browser* program might be written that relies upon such a " +"convention." +msgstr "" + +#: ../Doc/tutorial/classes.rst:504 +msgid "" +"Any function object that is a class attribute defines a method for instances " +"of that class. It is not necessary that the function definition is " +"textually enclosed in the class definition: assigning a function object to a " +"local variable in the class is also ok. For example::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:521 +msgid "" +"Now ``f``, ``g`` and ``h`` are all attributes of class :class:`C` that refer " +"to function objects, and consequently they are all methods of instances of :" +"class:`C` --- ``h`` being exactly equivalent to ``g``. Note that this " +"practice usually only serves to confuse the reader of a program." +msgstr "" + +#: ../Doc/tutorial/classes.rst:526 +msgid "" +"Methods may call other methods by using method attributes of the ``self`` " +"argument::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:540 +msgid "" +"Methods may reference global names in the same way as ordinary functions. " +"The global scope associated with a method is the module containing its " +"definition. (A class is never used as a global scope.) While one rarely " +"encounters a good reason for using global data in a method, there are many " +"legitimate uses of the global scope: for one thing, functions and modules " +"imported into the global scope can be used by methods, as well as functions " +"and classes defined in it. Usually, the class containing the method is " +"itself defined in this global scope, and in the next section we'll find some " +"good reasons why a method would want to reference its own class." +msgstr "" + +#: ../Doc/tutorial/classes.rst:550 +msgid "" +"Each value is an object, and therefore has a *class* (also called its " +"*type*). It is stored as ``object.__class__``." +msgstr "" + +#: ../Doc/tutorial/classes.rst:557 +msgid "Inheritance" +msgstr "" + +#: ../Doc/tutorial/classes.rst:559 +msgid "" +"Of course, a language feature would not be worthy of the name \"class\" " +"without supporting inheritance. The syntax for a derived class definition " +"looks like this::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:570 +msgid "" +"The name :class:`BaseClassName` must be defined in a scope containing the " +"derived class definition. In place of a base class name, other arbitrary " +"expressions are also allowed. This can be useful, for example, when the " +"base class is defined in another module::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:577 +msgid "" +"Execution of a derived class definition proceeds the same as for a base " +"class. When the class object is constructed, the base class is remembered. " +"This is used for resolving attribute references: if a requested attribute is " +"not found in the class, the search proceeds to look in the base class. This " +"rule is applied recursively if the base class itself is derived from some " +"other class." +msgstr "" + +#: ../Doc/tutorial/classes.rst:583 +msgid "" +"There's nothing special about instantiation of derived classes: " +"``DerivedClassName()`` creates a new instance of the class. Method " +"references are resolved as follows: the corresponding class attribute is " +"searched, descending down the chain of base classes if necessary, and the " +"method reference is valid if this yields a function object." +msgstr "" + +#: ../Doc/tutorial/classes.rst:589 +msgid "" +"Derived classes may override methods of their base classes. Because methods " +"have no special privileges when calling other methods of the same object, a " +"method of a base class that calls another method defined in the same base " +"class may end up calling a method of a derived class that overrides it. " +"(For C++ programmers: all methods in Python are effectively ``virtual``.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:595 +msgid "" +"An overriding method in a derived class may in fact want to extend rather " +"than simply replace the base class method of the same name. There is a " +"simple way to call the base class method directly: just call ``BaseClassName." +"methodname(self, arguments)``. This is occasionally useful to clients as " +"well. (Note that this only works if the base class is accessible as " +"``BaseClassName`` in the global scope.)" +msgstr "" + +#: ../Doc/tutorial/classes.rst:602 +msgid "Python has two built-in functions that work with inheritance:" +msgstr "" + +#: ../Doc/tutorial/classes.rst:604 +msgid "" +"Use :func:`isinstance` to check an instance's type: ``isinstance(obj, int)`` " +"will be ``True`` only if ``obj.__class__`` is :class:`int` or some class " +"derived from :class:`int`." +msgstr "" + +#: ../Doc/tutorial/classes.rst:608 +msgid "" +"Use :func:`issubclass` to check class inheritance: ``issubclass(bool, int)`` " +"is ``True`` since :class:`bool` is a subclass of :class:`int`. However, " +"``issubclass(float, int)`` is ``False`` since :class:`float` is not a " +"subclass of :class:`int`." +msgstr "" + +#: ../Doc/tutorial/classes.rst:618 +msgid "Multiple Inheritance" +msgstr "" + +#: ../Doc/tutorial/classes.rst:620 +msgid "" +"Python supports a form of multiple inheritance as well. A class definition " +"with multiple base classes looks like this::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:630 +msgid "" +"For most purposes, in the simplest cases, you can think of the search for " +"attributes inherited from a parent class as depth-first, left-to-right, not " +"searching twice in the same class where there is an overlap in the " +"hierarchy. Thus, if an attribute is not found in :class:`DerivedClassName`, " +"it is searched for in :class:`Base1`, then (recursively) in the base classes " +"of :class:`Base1`, and if it was not found there, it was searched for in :" +"class:`Base2`, and so on." +msgstr "" + +#: ../Doc/tutorial/classes.rst:637 +msgid "" +"In fact, it is slightly more complex than that; the method resolution order " +"changes dynamically to support cooperative calls to :func:`super`. This " +"approach is known in some other multiple-inheritance languages as call-next-" +"method and is more powerful than the super call found in single-inheritance " +"languages." +msgstr "" + +#: ../Doc/tutorial/classes.rst:643 +msgid "" +"Dynamic ordering is necessary because all cases of multiple inheritance " +"exhibit one or more diamond relationships (where at least one of the parent " +"classes can be accessed through multiple paths from the bottommost class). " +"For example, all classes inherit from :class:`object`, so any case of " +"multiple inheritance provides more than one path to reach :class:`object`. " +"To keep the base classes from being accessed more than once, the dynamic " +"algorithm linearizes the search order in a way that preserves the left-to-" +"right ordering specified in each class, that calls each parent only once, " +"and that is monotonic (meaning that a class can be subclassed without " +"affecting the precedence order of its parents). Taken together, these " +"properties make it possible to design reliable and extensible classes with " +"multiple inheritance. For more detail, see https://www.python.org/download/" +"releases/2.3/mro/." +msgstr "" + +#: ../Doc/tutorial/classes.rst:660 +msgid "Private Variables" +msgstr "" + +#: ../Doc/tutorial/classes.rst:662 +msgid "" +"\"Private\" instance variables that cannot be accessed except from inside an " +"object don't exist in Python. However, there is a convention that is " +"followed by most Python code: a name prefixed with an underscore (e.g. " +"``_spam``) should be treated as a non-public part of the API (whether it is " +"a function, a method or a data member). It should be considered an " +"implementation detail and subject to change without notice." +msgstr "" + +#: ../Doc/tutorial/classes.rst:669 +msgid "" +"Since there is a valid use-case for class-private members (namely to avoid " +"name clashes of names with names defined by subclasses), there is limited " +"support for such a mechanism, called :dfn:`name mangling`. Any identifier " +"of the form ``__spam`` (at least two leading underscores, at most one " +"trailing underscore) is textually replaced with ``_classname__spam``, where " +"``classname`` is the current class name with leading underscore(s) " +"stripped. This mangling is done without regard to the syntactic position of " +"the identifier, as long as it occurs within the definition of a class." +msgstr "" + +#: ../Doc/tutorial/classes.rst:678 +msgid "" +"Name mangling is helpful for letting subclasses override methods without " +"breaking intraclass method calls. For example::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:700 +msgid "" +"Note that the mangling rules are designed mostly to avoid accidents; it " +"still is possible to access or modify a variable that is considered " +"private. This can even be useful in special circumstances, such as in the " +"debugger." +msgstr "" + +#: ../Doc/tutorial/classes.rst:704 +msgid "" +"Notice that code passed to ``exec()`` or ``eval()`` does not consider the " +"classname of the invoking class to be the current class; this is similar to " +"the effect of the ``global`` statement, the effect of which is likewise " +"restricted to code that is byte-compiled together. The same restriction " +"applies to ``getattr()``, ``setattr()`` and ``delattr()``, as well as when " +"referencing ``__dict__`` directly." +msgstr "" + +#: ../Doc/tutorial/classes.rst:715 +msgid "Odds and Ends" +msgstr "" + +#: ../Doc/tutorial/classes.rst:717 +msgid "" +"Sometimes it is useful to have a data type similar to the Pascal \"record\" " +"or C \"struct\", bundling together a few named data items. An empty class " +"definition will do nicely::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:731 +msgid "" +"A piece of Python code that expects a particular abstract data type can " +"often be passed a class that emulates the methods of that data type " +"instead. For instance, if you have a function that formats some data from a " +"file object, you can define a class with methods :meth:`read` and :meth:`!" +"readline` that get the data from a string buffer instead, and pass it as an " +"argument." +msgstr "" + +#: ../Doc/tutorial/classes.rst:742 +msgid "" +"Instance method objects have attributes, too: ``m.__self__`` is the instance " +"object with the method :meth:`m`, and ``m.__func__`` is the function object " +"corresponding to the method." +msgstr "" + +#: ../Doc/tutorial/classes.rst:750 +msgid "Exceptions Are Classes Too" +msgstr "" + +#: ../Doc/tutorial/classes.rst:752 +msgid "" +"User-defined exceptions are identified by classes as well. Using this " +"mechanism it is possible to create extensible hierarchies of exceptions." +msgstr "" + +#: ../Doc/tutorial/classes.rst:755 +msgid "" +"There are two new valid (semantic) forms for the :keyword:`raise` statement::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:761 +msgid "" +"In the first form, ``Class`` must be an instance of :class:`type` or of a " +"class derived from it. The first form is a shorthand for::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:766 +msgid "" +"A class in an :keyword:`except` clause is compatible with an exception if it " +"is the same class or a base class thereof (but not the other way around --- " +"an except clause listing a derived class is not compatible with a base " +"class). For example, the following code will print B, C, D in that order::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:788 +msgid "" +"Note that if the except clauses were reversed (with ``except B`` first), it " +"would have printed B, B, B --- the first matching except clause is triggered." +msgstr "" + +#: ../Doc/tutorial/classes.rst:791 +msgid "" +"When an error message is printed for an unhandled exception, the exception's " +"class name is printed, then a colon and a space, and finally the instance " +"converted to a string using the built-in function :func:`str`." +msgstr "" + +#: ../Doc/tutorial/classes.rst:799 +msgid "Iterators" +msgstr "" + +#: ../Doc/tutorial/classes.rst:801 +msgid "" +"By now you have probably noticed that most container objects can be looped " +"over using a :keyword:`for` statement::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:815 +msgid "" +"This style of access is clear, concise, and convenient. The use of " +"iterators pervades and unifies Python. Behind the scenes, the :keyword:" +"`for` statement calls :func:`iter` on the container object. The function " +"returns an iterator object that defines the method :meth:`~iterator." +"__next__` which accesses elements in the container one at a time. When " +"there are no more elements, :meth:`~iterator.__next__` raises a :exc:" +"`StopIteration` exception which tells the :keyword:`for` loop to terminate. " +"You can call the :meth:`~iterator.__next__` method using the :func:`next` " +"built-in function; this example shows how it all works::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:840 +msgid "" +"Having seen the mechanics behind the iterator protocol, it is easy to add " +"iterator behavior to your classes. Define an :meth:`__iter__` method which " +"returns an object with a :meth:`~iterator.__next__` method. If the class " +"defines :meth:`__next__`, then :meth:`__iter__` can just return ``self``::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:877 +msgid "Generators" +msgstr "" + +#: ../Doc/tutorial/classes.rst:879 +msgid "" +":term:`Generator`\\s are a simple and powerful tool for creating iterators. " +"They are written like regular functions but use the :keyword:`yield` " +"statement whenever they want to return data. Each time :func:`next` is " +"called on it, the generator resumes where it left off (it remembers all the " +"data values and which statement was last executed). An example shows that " +"generators can be trivially easy to create::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:900 +msgid "" +"Anything that can be done with generators can also be done with class-based " +"iterators as described in the previous section. What makes generators so " +"compact is that the :meth:`__iter__` and :meth:`~generator.__next__` methods " +"are created automatically." +msgstr "" + +#: ../Doc/tutorial/classes.rst:905 +msgid "" +"Another key feature is that the local variables and execution state are " +"automatically saved between calls. This made the function easier to write " +"and much more clear than an approach using instance variables like ``self." +"index`` and ``self.data``." +msgstr "" + +#: ../Doc/tutorial/classes.rst:910 +msgid "" +"In addition to automatic method creation and saving program state, when " +"generators terminate, they automatically raise :exc:`StopIteration`. In " +"combination, these features make it easy to create iterators with no more " +"effort than writing a regular function." +msgstr "" + +#: ../Doc/tutorial/classes.rst:919 +msgid "Generator Expressions" +msgstr "" + +#: ../Doc/tutorial/classes.rst:921 +msgid "" +"Some simple generators can be coded succinctly as expressions using a syntax " +"similar to list comprehensions but with parentheses instead of brackets. " +"These expressions are designed for situations where the generator is used " +"right away by an enclosing function. Generator expressions are more compact " +"but less versatile than full generator definitions and tend to be more " +"memory friendly than equivalent list comprehensions." +msgstr "" + +#: ../Doc/tutorial/classes.rst:928 +msgid "Examples::" +msgstr "" + +#: ../Doc/tutorial/classes.rst:953 +msgid "" +"Except for one thing. Module objects have a secret read-only attribute " +"called :attr:`~object.__dict__` which returns the dictionary used to " +"implement the module's namespace; the name :attr:`~object.__dict__` is an " +"attribute but not a global name. Obviously, using this violates the " +"abstraction of namespace implementation, and should be restricted to things " +"like post-mortem debuggers." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:5 +msgid "More Control Flow Tools" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:7 +msgid "" +"Besides the :keyword:`while` statement just introduced, Python knows the " +"usual control flow statements known from other languages, with some twists." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:14 +msgid ":keyword:`if` Statements" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:16 +msgid "" +"Perhaps the most well-known statement type is the :keyword:`if` statement. " +"For example::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:33 +msgid "" +"There can be zero or more :keyword:`elif` parts, and the :keyword:`else` " +"part is optional. The keyword ':keyword:`elif`' is short for 'else if', and " +"is useful to avoid excessive indentation. An :keyword:`if` ... :keyword:" +"`elif` ... :keyword:`elif` ... sequence is a substitute for the ``switch`` " +"or ``case`` statements found in other languages." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:43 +msgid ":keyword:`for` Statements" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:48 +msgid "" +"The :keyword:`for` statement in Python differs a bit from what you may be " +"used to in C or Pascal. Rather than always iterating over an arithmetic " +"progression of numbers (like in Pascal), or giving the user the ability to " +"define both the iteration step and halting condition (as C), Python's :" +"keyword:`for` statement iterates over the items of any sequence (a list or a " +"string), in the order that they appear in the sequence. For example (no pun " +"intended):" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:69 +msgid "" +"If you need to modify the sequence you are iterating over while inside the " +"loop (for example to duplicate selected items), it is recommended that you " +"first make a copy. Iterating over a sequence does not implicitly make a " +"copy. The slice notation makes this especially convenient::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:81 +msgid "" +"With ``for w in words:``, the example would attempt to create an infinite " +"list, inserting ``defenestrate`` over and over again." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:88 +msgid "The :func:`range` Function" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:90 +msgid "" +"If you do need to iterate over a sequence of numbers, the built-in function :" +"func:`range` comes in handy. It generates arithmetic progressions::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:102 +msgid "" +"The given end point is never part of the generated sequence; ``range(10)`` " +"generates 10 values, the legal indices for items of a sequence of length " +"10. It is possible to let the range start at another number, or to specify " +"a different increment (even negative; sometimes this is called the 'step')::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:116 +msgid "" +"To iterate over the indices of a sequence, you can combine :func:`range` " +"and :func:`len` as follows::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:129 +msgid "" +"In most such cases, however, it is convenient to use the :func:`enumerate` " +"function, see :ref:`tut-loopidioms`." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:132 +msgid "A strange thing happens if you just print a range::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:137 +msgid "" +"In many ways the object returned by :func:`range` behaves as if it is a " +"list, but in fact it isn't. It is an object which returns the successive " +"items of the desired sequence when you iterate over it, but it doesn't " +"really make the list, thus saving space." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:142 +msgid "" +"We say such an object is *iterable*, that is, suitable as a target for " +"functions and constructs that expect something from which they can obtain " +"successive items until the supply is exhausted. We have seen that the :" +"keyword:`for` statement is such an *iterator*. The function :func:`list` is " +"another; it creates lists from iterables::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:152 +msgid "" +"Later we will see more functions that return iterables and take iterables as " +"argument." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:158 +msgid "" +":keyword:`break` and :keyword:`continue` Statements, and :keyword:`else` " +"Clauses on Loops" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:160 +msgid "" +"The :keyword:`break` statement, like in C, breaks out of the smallest " +"enclosing :keyword:`for` or :keyword:`while` loop." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:163 +msgid "" +"Loop statements may have an ``else`` clause; it is executed when the loop " +"terminates through exhaustion of the list (with :keyword:`for`) or when the " +"condition becomes false (with :keyword:`while`), but not when the loop is " +"terminated by a :keyword:`break` statement. This is exemplified by the " +"following loop, which searches for prime numbers::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:187 +msgid "" +"(Yes, this is the correct code. Look closely: the ``else`` clause belongs " +"to the :keyword:`for` loop, **not** the :keyword:`if` statement.)" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:190 +msgid "" +"When used with a loop, the ``else`` clause has more in common with the " +"``else`` clause of a :keyword:`try` statement than it does that of :keyword:" +"`if` statements: a :keyword:`try` statement's ``else`` clause runs when no " +"exception occurs, and a loop's ``else`` clause runs when no ``break`` " +"occurs. For more on the :keyword:`try` statement and exceptions, see :ref:" +"`tut-handling`." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:197 +msgid "" +"The :keyword:`continue` statement, also borrowed from C, continues with the " +"next iteration of the loop::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:217 +msgid ":keyword:`pass` Statements" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:219 +msgid "" +"The :keyword:`pass` statement does nothing. It can be used when a statement " +"is required syntactically but the program requires no action. For example::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:226 +msgid "This is commonly used for creating minimal classes::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:232 +msgid "" +"Another place :keyword:`pass` can be used is as a place-holder for a " +"function or conditional body when you are working on new code, allowing you " +"to keep thinking at a more abstract level. The :keyword:`pass` is silently " +"ignored::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:243 +msgid "Defining Functions" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:245 +msgid "" +"We can create a function that writes the Fibonacci series to an arbitrary " +"boundary::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:265 +msgid "" +"The keyword :keyword:`def` introduces a function *definition*. It must be " +"followed by the function name and the parenthesized list of formal " +"parameters. The statements that form the body of the function start at the " +"next line, and must be indented." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:270 +msgid "" +"The first statement of the function body can optionally be a string literal; " +"this string literal is the function's documentation string, or :dfn:" +"`docstring`. (More about docstrings can be found in the section :ref:`tut-" +"docstrings`.) There are tools which use docstrings to automatically produce " +"online or printed documentation, or to let the user interactively browse " +"through code; it's good practice to include docstrings in code that you " +"write, so make a habit of it." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:277 +msgid "" +"The *execution* of a function introduces a new symbol table used for the " +"local variables of the function. More precisely, all variable assignments " +"in a function store the value in the local symbol table; whereas variable " +"references first look in the local symbol table, then in the local symbol " +"tables of enclosing functions, then in the global symbol table, and finally " +"in the table of built-in names. Thus, global variables cannot be directly " +"assigned a value within a function (unless named in a :keyword:`global` " +"statement), although they may be referenced." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:286 +msgid "" +"The actual parameters (arguments) to a function call are introduced in the " +"local symbol table of the called function when it is called; thus, arguments " +"are passed using *call by value* (where the *value* is always an object " +"*reference*, not the value of the object). [#]_ When a function calls " +"another function, a new local symbol table is created for that call." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:292 +msgid "" +"A function definition introduces the function name in the current symbol " +"table. The value of the function name has a type that is recognized by the " +"interpreter as a user-defined function. This value can be assigned to " +"another name which can then also be used as a function. This serves as a " +"general renaming mechanism::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:304 +msgid "" +"Coming from other languages, you might object that ``fib`` is not a function " +"but a procedure since it doesn't return a value. In fact, even functions " +"without a :keyword:`return` statement do return a value, albeit a rather " +"boring one. This value is called ``None`` (it's a built-in name). Writing " +"the value ``None`` is normally suppressed by the interpreter if it would be " +"the only value written. You can see it if you really want to using :func:" +"`print`::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:315 +msgid "" +"It is simple to write a function that returns a list of the numbers of the " +"Fibonacci series, instead of printing it::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:331 +msgid "This example, as usual, demonstrates some new Python features:" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:333 +msgid "" +"The :keyword:`return` statement returns with a value from a function. :" +"keyword:`return` without an expression argument returns ``None``. Falling " +"off the end of a function also returns ``None``." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:337 +msgid "" +"The statement ``result.append(a)`` calls a *method* of the list object " +"``result``. A method is a function that 'belongs' to an object and is named " +"``obj.methodname``, where ``obj`` is some object (this may be an " +"expression), and ``methodname`` is the name of a method that is defined by " +"the object's type. Different types define different methods. Methods of " +"different types may have the same name without causing ambiguity. (It is " +"possible to define your own object types and methods, using *classes*, see :" +"ref:`tut-classes`) The method :meth:`append` shown in the example is defined " +"for list objects; it adds a new element at the end of the list. In this " +"example it is equivalent to ``result = result + [a]``, but more efficient." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:352 +msgid "More on Defining Functions" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:354 +msgid "" +"It is also possible to define functions with a variable number of arguments. " +"There are three forms, which can be combined." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:361 +msgid "Default Argument Values" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:363 +msgid "" +"The most useful form is to specify a default value for one or more " +"arguments. This creates a function that can be called with fewer arguments " +"than it is defined to allow. For example::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:379 +msgid "This function can be called in several ways:" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:381 +msgid "" +"giving only the mandatory argument: ``ask_ok('Do you really want to quit?')``" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:383 +msgid "" +"giving one of the optional arguments: ``ask_ok('OK to overwrite the file?', " +"2)``" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:385 +msgid "" +"or even giving all arguments: ``ask_ok('OK to overwrite the file?', 2, 'Come " +"on, only yes or no!')``" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:388 +msgid "" +"This example also introduces the :keyword:`in` keyword. This tests whether " +"or not a sequence contains a certain value." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:391 +msgid "" +"The default values are evaluated at the point of function definition in the " +"*defining* scope, so that ::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:402 +msgid "will print ``5``." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:404 +msgid "" +"**Important warning:** The default value is evaluated only once. This makes " +"a difference when the default is a mutable object such as a list, " +"dictionary, or instances of most classes. For example, the following " +"function accumulates the arguments passed to it on subsequent calls::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:417 +msgid "This will print ::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:423 +msgid "" +"If you don't want the default to be shared between subsequent calls, you can " +"write the function like this instead::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:436 +msgid "Keyword Arguments" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:438 +msgid "" +"Functions can also be called using :term:`keyword arguments ` of the form ``kwarg=value``. For instance, the following " +"function::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:447 +msgid "" +"accepts one required argument (``voltage``) and three optional arguments " +"(``state``, ``action``, and ``type``). This function can be called in any " +"of the following ways::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:458 +msgid "but all the following calls would be invalid::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:465 +msgid "" +"In a function call, keyword arguments must follow positional arguments. All " +"the keyword arguments passed must match one of the arguments accepted by the " +"function (e.g. ``actor`` is not a valid argument for the ``parrot`` " +"function), and their order is not important. This also includes non-" +"optional arguments (e.g. ``parrot(voltage=1000)`` is valid too). No argument " +"may receive a value more than once. Here's an example that fails due to this " +"restriction::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:481 +msgid "" +"When a final formal parameter of the form ``**name`` is present, it receives " +"a dictionary (see :ref:`typesmapping`) containing all keyword arguments " +"except for those corresponding to a formal parameter. This may be combined " +"with a formal parameter of the form ``*name`` (described in the next " +"subsection) which receives a tuple containing the positional arguments " +"beyond the formal parameter list. (``*name`` must occur before ``**name``.) " +"For example, if we define a function like this::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:499 +msgid "It could be called like this::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:507 +msgid "and of course it would print:" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:520 +msgid "" +"Note that the list of keyword argument names is created by sorting the " +"result of the keywords dictionary's ``keys()`` method before printing its " +"contents; if this is not done, the order in which the arguments are printed " +"is undefined." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:527 +msgid "Arbitrary Argument Lists" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:532 +msgid "" +"Finally, the least frequently used option is to specify that a function can " +"be called with an arbitrary number of arguments. These arguments will be " +"wrapped up in a tuple (see :ref:`tut-tuples`). Before the variable number " +"of arguments, zero or more normal arguments may occur. ::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:541 +msgid "" +"Normally, these ``variadic`` arguments will be last in the list of formal " +"parameters, because they scoop up all remaining input arguments that are " +"passed to the function. Any formal parameters which occur after the " +"``*args`` parameter are 'keyword-only' arguments, meaning that they can only " +"be used as keywords rather than positional arguments. ::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:558 +msgid "Unpacking Argument Lists" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:560 +msgid "" +"The reverse situation occurs when the arguments are already in a list or " +"tuple but need to be unpacked for a function call requiring separate " +"positional arguments. For instance, the built-in :func:`range` function " +"expects separate *start* and *stop* arguments. If they are not available " +"separately, write the function call with the ``*``\\ -operator to unpack " +"the arguments out of a list or tuple::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:576 +msgid "" +"In the same fashion, dictionaries can deliver keyword arguments with the " +"``**``\\ -operator::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:592 +msgid "Lambda Expressions" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:594 +msgid "" +"Small anonymous functions can be created with the :keyword:`lambda` keyword. " +"This function returns the sum of its two arguments: ``lambda a, b: a+b``. " +"Lambda functions can be used wherever function objects are required. They " +"are syntactically restricted to a single expression. Semantically, they are " +"just syntactic sugar for a normal function definition. Like nested function " +"definitions, lambda functions can reference variables from the containing " +"scope::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:611 +msgid "" +"The above example uses a lambda expression to return a function. Another " +"use is to pass a small function as an argument::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:623 +msgid "Documentation Strings" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:630 +msgid "" +"Here are some conventions about the content and formatting of documentation " +"strings." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:633 +msgid "" +"The first line should always be a short, concise summary of the object's " +"purpose. For brevity, it should not explicitly state the object's name or " +"type, since these are available by other means (except if the name happens " +"to be a verb describing a function's operation). This line should begin " +"with a capital letter and end with a period." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:639 +msgid "" +"If there are more lines in the documentation string, the second line should " +"be blank, visually separating the summary from the rest of the description. " +"The following lines should be one or more paragraphs describing the object's " +"calling conventions, its side effects, etc." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:644 +msgid "" +"The Python parser does not strip indentation from multi-line string literals " +"in Python, so tools that process documentation have to strip indentation if " +"desired. This is done using the following convention. The first non-blank " +"line *after* the first line of the string determines the amount of " +"indentation for the entire documentation string. (We can't use the first " +"line since it is generally adjacent to the string's opening quotes so its " +"indentation is not apparent in the string literal.) Whitespace \"equivalent" +"\" to this indentation is then stripped from the start of all lines of the " +"string. Lines that are indented less should not occur, but if they occur " +"all their leading whitespace should be stripped. Equivalence of whitespace " +"should be tested after expansion of tabs (to 8 spaces, normally)." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:656 +msgid "Here is an example of a multi-line docstring::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:674 +msgid "Function Annotations" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:681 +msgid "" +":ref:`Function annotations ` are completely optional metadata " +"information about the types used by user-defined functions (see :pep:`484` " +"for more information)." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:685 +msgid "" +"Annotations are stored in the :attr:`__annotations__` attribute of the " +"function as a dictionary and have no effect on any other part of the " +"function. Parameter annotations are defined by a colon after the parameter " +"name, followed by an expression evaluating to the value of the annotation. " +"Return annotations are defined by a literal ``->``, followed by an " +"expression, between the parameter list and the colon denoting the end of " +"the :keyword:`def` statement. The following example has a positional " +"argument, a keyword argument, and the return value annotated::" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:707 +msgid "Intermezzo: Coding Style" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:712 +msgid "" +"Now that you are about to write longer, more complex pieces of Python, it is " +"a good time to talk about *coding style*. Most languages can be written (or " +"more concise, *formatted*) in different styles; some are more readable than " +"others. Making it easy for others to read your code is always a good idea, " +"and adopting a nice coding style helps tremendously for that." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:718 +msgid "" +"For Python, :pep:`8` has emerged as the style guide that most projects " +"adhere to; it promotes a very readable and eye-pleasing coding style. Every " +"Python developer should read it at some point; here are the most important " +"points extracted for you:" +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:723 +msgid "Use 4-space indentation, and no tabs." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:725 +msgid "" +"4 spaces are a good compromise between small indentation (allows greater " +"nesting depth) and large indentation (easier to read). Tabs introduce " +"confusion, and are best left out." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:729 +msgid "Wrap lines so that they don't exceed 79 characters." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:731 +msgid "" +"This helps users with small displays and makes it possible to have several " +"code files side-by-side on larger displays." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:734 +msgid "" +"Use blank lines to separate functions and classes, and larger blocks of code " +"inside functions." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:737 +msgid "When possible, put comments on a line of their own." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:739 +msgid "Use docstrings." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:741 +msgid "" +"Use spaces around operators and after commas, but not directly inside " +"bracketing constructs: ``a = f(1, 2) + g(3, 4)``." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:744 +msgid "" +"Name your classes and functions consistently; the convention is to use " +"``CamelCase`` for classes and ``lower_case_with_underscores`` for functions " +"and methods. Always use ``self`` as the name for the first method argument " +"(see :ref:`tut-firstclasses` for more on classes and methods)." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:749 +msgid "" +"Don't use fancy encodings if your code is meant to be used in international " +"environments. Python's default, UTF-8, or even plain ASCII work best in any " +"case." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:753 +msgid "" +"Likewise, don't use non-ASCII characters in identifiers if there is only the " +"slightest chance people speaking a different language will read or maintain " +"the code." +msgstr "" + +#: ../Doc/tutorial/controlflow.rst:760 +msgid "" +"Actually, *call by object reference* would be a better description, since if " +"a mutable object is passed, the caller will see any changes the callee makes " +"to it (items inserted into a list)." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:5 +msgid "Data Structures" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:7 +msgid "" +"This chapter describes some things you've learned about already in more " +"detail, and adds some new things as well." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:13 +msgid "More on Lists" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:15 +msgid "" +"The list data type has some more methods. Here are all of the methods of " +"list objects:" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:22 +msgid "" +"Add an item to the end of the list. Equivalent to ``a[len(a):] = [x]``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:28 +msgid "" +"Extend the list by appending all the items in the given list. Equivalent to " +"``a[len(a):] = L``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:35 +msgid "" +"Insert an item at a given position. The first argument is the index of the " +"element before which to insert, so ``a.insert(0, x)`` inserts at the front " +"of the list, and ``a.insert(len(a), x)`` is equivalent to ``a.append(x)``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:43 +msgid "" +"Remove the first item from the list whose value is *x*. It is an error if " +"there is no such item." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:50 +msgid "" +"Remove the item at the given position in the list, and return it. If no " +"index is specified, ``a.pop()`` removes and returns the last item in the " +"list. (The square brackets around the *i* in the method signature denote " +"that the parameter is optional, not that you should type square brackets at " +"that position. You will see this notation frequently in the Python Library " +"Reference.)" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:60 +msgid "Remove all items from the list. Equivalent to ``del a[:]``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:66 +msgid "" +"Return the index in the list of the first item whose value is *x*. It is an " +"error if there is no such item." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:73 +msgid "Return the number of times *x* appears in the list." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:79 +msgid "" +"Sort the items of the list in place (the arguments can be used for sort " +"customization, see :func:`sorted` for their explanation)." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:86 +msgid "Reverse the elements of the list in place." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:92 +msgid "Return a shallow copy of the list. Equivalent to ``a[:]``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:95 +msgid "An example that uses most of the list methods::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:120 +msgid "" +"You might have noticed that methods like ``insert``, ``remove`` or ``sort`` " +"that only modify the list have no return value printed -- they return the " +"default ``None``. [1]_ This is a design principle for all mutable data " +"structures in Python." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:129 +msgid "Using Lists as Stacks" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:134 +msgid "" +"The list methods make it very easy to use a list as a stack, where the last " +"element added is the first element retrieved (\"last-in, first-out\"). To " +"add an item to the top of the stack, use :meth:`append`. To retrieve an " +"item from the top of the stack, use :meth:`pop` without an explicit index. " +"For example::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:159 +msgid "Using Lists as Queues" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:163 +msgid "" +"It is also possible to use a list as a queue, where the first element added " +"is the first element retrieved (\"first-in, first-out\"); however, lists are " +"not efficient for this purpose. While appends and pops from the end of list " +"are fast, doing inserts or pops from the beginning of a list is slow " +"(because all of the other elements have to be shifted by one)." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:169 +msgid "" +"To implement a queue, use :class:`collections.deque` which was designed to " +"have fast appends and pops from both ends. For example::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:187 +msgid "List Comprehensions" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:189 +msgid "" +"List comprehensions provide a concise way to create lists. Common " +"applications are to make new lists where each element is the result of some " +"operations applied to each member of another sequence or iterable, or to " +"create a subsequence of those elements that satisfy a certain condition." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:194 +msgid "For example, assume we want to create a list of squares, like::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:203 +msgid "" +"Note that this creates (or overwrites) a variable named ``x`` that still " +"exists after the loop completes. We can calculate the list of squares " +"without any side effects using::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:209 +msgid "or, equivalently::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:213 +msgid "which is more concise and readable." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:215 +msgid "" +"A list comprehension consists of brackets containing an expression followed " +"by a :keyword:`for` clause, then zero or more :keyword:`for` or :keyword:" +"`if` clauses. The result will be a new list resulting from evaluating the " +"expression in the context of the :keyword:`for` and :keyword:`if` clauses " +"which follow it. For example, this listcomp combines the elements of two " +"lists if they are not equal::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:225 +msgid "and it's equivalent to::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:236 +msgid "" +"Note how the order of the :keyword:`for` and :keyword:`if` statements is the " +"same in both these snippets." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:239 +msgid "" +"If the expression is a tuple (e.g. the ``(x, y)`` in the previous example), " +"it must be parenthesized. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:270 +msgid "" +"List comprehensions can contain complex expressions and nested functions::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:277 +msgid "Nested List Comprehensions" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:279 +msgid "" +"The initial expression in a list comprehension can be any arbitrary " +"expression, including another list comprehension." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:282 +msgid "" +"Consider the following example of a 3x4 matrix implemented as a list of 3 " +"lists of length 4::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:291 +msgid "The following list comprehension will transpose rows and columns::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:296 +msgid "" +"As we saw in the previous section, the nested listcomp is evaluated in the " +"context of the :keyword:`for` that follows it, so this example is equivalent " +"to::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:307 +msgid "which, in turn, is the same as::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:320 +msgid "" +"In the real world, you should prefer built-in functions to complex flow " +"statements. The :func:`zip` function would do a great job for this use case::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:326 +msgid "" +"See :ref:`tut-unpacking-arguments` for details on the asterisk in this line." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:331 +msgid "The :keyword:`del` statement" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:333 +msgid "" +"There is a way to remove an item from a list given its index instead of its " +"value: the :keyword:`del` statement. This differs from the :meth:`pop` " +"method which returns a value. The :keyword:`del` statement can also be used " +"to remove slices from a list or clear the entire list (which we did earlier " +"by assignment of an empty list to the slice). For example::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:350 +msgid ":keyword:`del` can also be used to delete entire variables::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:354 +msgid "" +"Referencing the name ``a`` hereafter is an error (at least until another " +"value is assigned to it). We'll find other uses for :keyword:`del` later." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:361 +msgid "Tuples and Sequences" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:363 +msgid "" +"We saw that lists and strings have many common properties, such as indexing " +"and slicing operations. They are two examples of *sequence* data types " +"(see :ref:`typesseq`). Since Python is an evolving language, other sequence " +"data types may be added. There is also another standard sequence data type: " +"the *tuple*." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:369 +msgid "" +"A tuple consists of a number of values separated by commas, for instance::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:391 +msgid "" +"As you see, on output tuples are always enclosed in parentheses, so that " +"nested tuples are interpreted correctly; they may be input with or without " +"surrounding parentheses, although often parentheses are necessary anyway (if " +"the tuple is part of a larger expression). It is not possible to assign to " +"the individual items of a tuple, however it is possible to create tuples " +"which contain mutable objects, such as lists." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:398 +msgid "" +"Though tuples may seem similar to lists, they are often used in different " +"situations and for different purposes. Tuples are :term:`immutable`, and " +"usually contain a heterogeneous sequence of elements that are accessed via " +"unpacking (see later in this section) or indexing (or even by attribute in " +"the case of :func:`namedtuples `). Lists are :term:" +"`mutable`, and their elements are usually homogeneous and are accessed by " +"iterating over the list." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:406 +msgid "" +"A special problem is the construction of tuples containing 0 or 1 items: the " +"syntax has some extra quirks to accommodate these. Empty tuples are " +"constructed by an empty pair of parentheses; a tuple with one item is " +"constructed by following a value with a comma (it is not sufficient to " +"enclose a single value in parentheses). Ugly, but effective. For example::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:421 +msgid "" +"The statement ``t = 12345, 54321, 'hello!'`` is an example of *tuple " +"packing*: the values ``12345``, ``54321`` and ``'hello!'`` are packed " +"together in a tuple. The reverse operation is also possible::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:427 +msgid "" +"This is called, appropriately enough, *sequence unpacking* and works for any " +"sequence on the right-hand side. Sequence unpacking requires that there are " +"as many variables on the left side of the equals sign as there are elements " +"in the sequence. Note that multiple assignment is really just a combination " +"of tuple packing and sequence unpacking." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:437 +msgid "Sets" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:439 +msgid "" +"Python also includes a data type for *sets*. A set is an unordered " +"collection with no duplicate elements. Basic uses include membership " +"testing and eliminating duplicate entries. Set objects also support " +"mathematical operations like union, intersection, difference, and symmetric " +"difference." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:444 +msgid "" +"Curly braces or the :func:`set` function can be used to create sets. Note: " +"to create an empty set you have to use ``set()``, not ``{}``; the latter " +"creates an empty dictionary, a data structure that we discuss in the next " +"section." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:448 +msgid "Here is a brief demonstration::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:473 +msgid "" +"Similarly to :ref:`list comprehensions `, set comprehensions " +"are also supported::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:484 +msgid "Dictionaries" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:486 +msgid "" +"Another useful data type built into Python is the *dictionary* (see :ref:" +"`typesmapping`). Dictionaries are sometimes found in other languages as " +"\"associative memories\" or \"associative arrays\". Unlike sequences, which " +"are indexed by a range of numbers, dictionaries are indexed by *keys*, which " +"can be any immutable type; strings and numbers can always be keys. Tuples " +"can be used as keys if they contain only strings, numbers, or tuples; if a " +"tuple contains any mutable object either directly or indirectly, it cannot " +"be used as a key. You can't use lists as keys, since lists can be modified " +"in place using index assignments, slice assignments, or methods like :meth:" +"`append` and :meth:`extend`." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:497 +msgid "" +"It is best to think of a dictionary as an unordered set of *key: value* " +"pairs, with the requirement that the keys are unique (within one " +"dictionary). A pair of braces creates an empty dictionary: ``{}``. Placing a " +"comma-separated list of key:value pairs within the braces adds initial key:" +"value pairs to the dictionary; this is also the way dictionaries are written " +"on output." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:503 +msgid "" +"The main operations on a dictionary are storing a value with some key and " +"extracting the value given the key. It is also possible to delete a key:" +"value pair with ``del``. If you store using a key that is already in use, " +"the old value associated with that key is forgotten. It is an error to " +"extract a value using a non-existent key." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:509 +msgid "" +"Performing ``list(d.keys())`` on a dictionary returns a list of all the keys " +"used in the dictionary, in arbitrary order (if you want it sorted, just use " +"``sorted(d.keys())`` instead). [2]_ To check whether a single key is in the " +"dictionary, use the :keyword:`in` keyword." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:514 +msgid "Here is a small example using a dictionary::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:535 +msgid "" +"The :func:`dict` constructor builds dictionaries directly from sequences of " +"key-value pairs::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:541 +msgid "" +"In addition, dict comprehensions can be used to create dictionaries from " +"arbitrary key and value expressions::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:547 +msgid "" +"When the keys are simple strings, it is sometimes easier to specify pairs " +"using keyword arguments::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:557 +msgid "Looping Techniques" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:559 +msgid "" +"When looping through dictionaries, the key and corresponding value can be " +"retrieved at the same time using the :meth:`items` method. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:569 +msgid "" +"When looping through a sequence, the position index and corresponding value " +"can be retrieved at the same time using the :func:`enumerate` function. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:579 +msgid "" +"To loop over two or more sequences at the same time, the entries can be " +"paired with the :func:`zip` function. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:591 +msgid "" +"To loop over a sequence in reverse, first specify the sequence in a forward " +"direction and then call the :func:`reversed` function. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:603 +msgid "" +"To loop over a sequence in sorted order, use the :func:`sorted` function " +"which returns a new sorted list while leaving the source unaltered. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:615 +msgid "" +"It is sometimes tempting to change a list while you are looping over it; " +"however, it is often simpler and safer to create a new list instead. ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:632 +msgid "More on Conditions" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:634 +msgid "" +"The conditions used in ``while`` and ``if`` statements can contain any " +"operators, not just comparisons." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:637 +msgid "" +"The comparison operators ``in`` and ``not in`` check whether a value occurs " +"(does not occur) in a sequence. The operators ``is`` and ``is not`` compare " +"whether two objects are really the same object; this only matters for " +"mutable objects like lists. All comparison operators have the same " +"priority, which is lower than that of all numerical operators." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:643 +msgid "" +"Comparisons can be chained. For example, ``a < b == c`` tests whether ``a`` " +"is less than ``b`` and moreover ``b`` equals ``c``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:646 +msgid "" +"Comparisons may be combined using the Boolean operators ``and`` and ``or``, " +"and the outcome of a comparison (or of any other Boolean expression) may be " +"negated with ``not``. These have lower priorities than comparison " +"operators; between them, ``not`` has the highest priority and ``or`` the " +"lowest, so that ``A and not B or C`` is equivalent to ``(A and (not B)) or " +"C``. As always, parentheses can be used to express the desired composition." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:653 +msgid "" +"The Boolean operators ``and`` and ``or`` are so-called *short-circuit* " +"operators: their arguments are evaluated from left to right, and evaluation " +"stops as soon as the outcome is determined. For example, if ``A`` and ``C`` " +"are true but ``B`` is false, ``A and B and C`` does not evaluate the " +"expression ``C``. When used as a general value and not as a Boolean, the " +"return value of a short-circuit operator is the last evaluated argument." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:660 +msgid "" +"It is possible to assign the result of a comparison or other Boolean " +"expression to a variable. For example, ::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:668 +msgid "" +"Note that in Python, unlike C, assignment cannot occur inside expressions. C " +"programmers may grumble about this, but it avoids a common class of problems " +"encountered in C programs: typing ``=`` in an expression when ``==`` was " +"intended." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:677 +msgid "Comparing Sequences and Other Types" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:679 +msgid "" +"Sequence objects may be compared to other objects with the same sequence " +"type. The comparison uses *lexicographical* ordering: first the first two " +"items are compared, and if they differ this determines the outcome of the " +"comparison; if they are equal, the next two items are compared, and so on, " +"until either sequence is exhausted. If two items to be compared are " +"themselves sequences of the same type, the lexicographical comparison is " +"carried out recursively. If all items of two sequences compare equal, the " +"sequences are considered equal. If one sequence is an initial sub-sequence " +"of the other, the shorter sequence is the smaller (lesser) one. " +"Lexicographical ordering for strings uses the Unicode code point number to " +"order individual characters. Some examples of comparisons between sequences " +"of the same type::" +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:699 +msgid "" +"Note that comparing objects of different types with ``<`` or ``>`` is legal " +"provided that the objects have appropriate comparison methods. For example, " +"mixed numeric types are compared according to their numeric value, so 0 " +"equals 0.0, etc. Otherwise, rather than providing an arbitrary ordering, " +"the interpreter will raise a :exc:`TypeError` exception." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:708 +msgid "" +"Other languages may return the mutated object, which allows method chaining, " +"such as ``d->insert(\"a\")->remove(\"b\")->sort();``." +msgstr "" + +#: ../Doc/tutorial/datastructures.rst:711 +msgid "" +"Calling ``d.keys()`` will return a :dfn:`dictionary view` object. It " +"supports operations like membership test and iteration, but its contents are " +"not independent of the original dictionary -- it is only a *view*." +msgstr "" + +#: ../Doc/tutorial/errors.rst:5 +msgid "Errors and Exceptions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:7 +msgid "" +"Until now error messages haven't been more than mentioned, but if you have " +"tried out the examples you have probably seen some. There are (at least) " +"two distinguishable kinds of errors: *syntax errors* and *exceptions*." +msgstr "" + +#: ../Doc/tutorial/errors.rst:15 +msgid "Syntax Errors" +msgstr "" + +#: ../Doc/tutorial/errors.rst:17 +msgid "" +"Syntax errors, also known as parsing errors, are perhaps the most common " +"kind of complaint you get while you are still learning Python::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:26 +msgid "" +"The parser repeats the offending line and displays a little 'arrow' pointing " +"at the earliest point in the line where the error was detected. The error " +"is caused by (or at least detected at) the token *preceding* the arrow: in " +"the example, the error is detected at the function :func:`print`, since a " +"colon (``':'``) is missing before it. File name and line number are printed " +"so you know where to look in case the input came from a script." +msgstr "" + +#: ../Doc/tutorial/errors.rst:37 +msgid "Exceptions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:39 +msgid "" +"Even if a statement or expression is syntactically correct, it may cause an " +"error when an attempt is made to execute it. Errors detected during " +"execution are called *exceptions* and are not unconditionally fatal: you " +"will soon learn how to handle them in Python programs. Most exceptions are " +"not handled by programs, however, and result in error messages as shown " +"here::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:58 +msgid "" +"The last line of the error message indicates what happened. Exceptions come " +"in different types, and the type is printed as part of the message: the " +"types in the example are :exc:`ZeroDivisionError`, :exc:`NameError` and :exc:" +"`TypeError`. The string printed as the exception type is the name of the " +"built-in exception that occurred. This is true for all built-in exceptions, " +"but need not be true for user-defined exceptions (although it is a useful " +"convention). Standard exception names are built-in identifiers (not reserved " +"keywords)." +msgstr "" + +#: ../Doc/tutorial/errors.rst:66 +msgid "" +"The rest of the line provides detail based on the type of exception and what " +"caused it." +msgstr "" + +#: ../Doc/tutorial/errors.rst:69 +msgid "" +"The preceding part of the error message shows the context where the " +"exception happened, in the form of a stack traceback. In general it contains " +"a stack traceback listing source lines; however, it will not display lines " +"read from standard input." +msgstr "" + +#: ../Doc/tutorial/errors.rst:74 +msgid "" +":ref:`bltin-exceptions` lists the built-in exceptions and their meanings." +msgstr "" + +#: ../Doc/tutorial/errors.rst:80 +msgid "Handling Exceptions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:82 +msgid "" +"It is possible to write programs that handle selected exceptions. Look at " +"the following example, which asks the user for input until a valid integer " +"has been entered, but allows the user to interrupt the program (using :kbd:" +"`Control-C` or whatever the operating system supports); note that a user-" +"generated interruption is signalled by raising the :exc:`KeyboardInterrupt` " +"exception. ::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:96 +msgid "The :keyword:`try` statement works as follows." +msgstr "" + +#: ../Doc/tutorial/errors.rst:98 +msgid "" +"First, the *try clause* (the statement(s) between the :keyword:`try` and :" +"keyword:`except` keywords) is executed." +msgstr "" + +#: ../Doc/tutorial/errors.rst:101 +msgid "" +"If no exception occurs, the *except clause* is skipped and execution of the :" +"keyword:`try` statement is finished." +msgstr "" + +#: ../Doc/tutorial/errors.rst:104 +msgid "" +"If an exception occurs during execution of the try clause, the rest of the " +"clause is skipped. Then if its type matches the exception named after the :" +"keyword:`except` keyword, the except clause is executed, and then execution " +"continues after the :keyword:`try` statement." +msgstr "" + +#: ../Doc/tutorial/errors.rst:109 +msgid "" +"If an exception occurs which does not match the exception named in the " +"except clause, it is passed on to outer :keyword:`try` statements; if no " +"handler is found, it is an *unhandled exception* and execution stops with a " +"message as shown above." +msgstr "" + +#: ../Doc/tutorial/errors.rst:114 +msgid "" +"A :keyword:`try` statement may have more than one except clause, to specify " +"handlers for different exceptions. At most one handler will be executed. " +"Handlers only handle exceptions that occur in the corresponding try clause, " +"not in other handlers of the same :keyword:`try` statement. An except " +"clause may name multiple exceptions as a parenthesized tuple, for example::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:123 +msgid "" +"The last except clause may omit the exception name(s), to serve as a " +"wildcard. Use this with extreme caution, since it is easy to mask a real " +"programming error in this way! It can also be used to print an error " +"message and then re-raise the exception (allowing a caller to handle the " +"exception as well)::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:142 +msgid "" +"The :keyword:`try` ... :keyword:`except` statement has an optional *else " +"clause*, which, when present, must follow all except clauses. It is useful " +"for code that must be executed if the try clause does not raise an " +"exception. For example::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:156 +msgid "" +"The use of the :keyword:`else` clause is better than adding additional code " +"to the :keyword:`try` clause because it avoids accidentally catching an " +"exception that wasn't raised by the code being protected by the :keyword:" +"`try` ... :keyword:`except` statement." +msgstr "" + +#: ../Doc/tutorial/errors.rst:161 +msgid "" +"When an exception occurs, it may have an associated value, also known as the " +"exception's *argument*. The presence and type of the argument depend on the " +"exception type." +msgstr "" + +#: ../Doc/tutorial/errors.rst:165 +msgid "" +"The except clause may specify a variable after the exception name. The " +"variable is bound to an exception instance with the arguments stored in " +"``instance.args``. For convenience, the exception instance defines :meth:" +"`__str__` so the arguments can be printed directly without having to " +"reference ``.args``. One may also instantiate an exception first before " +"raising it and add any attributes to it as desired. ::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:189 +msgid "" +"If an exception has arguments, they are printed as the last part ('detail') " +"of the message for unhandled exceptions." +msgstr "" + +#: ../Doc/tutorial/errors.rst:192 +msgid "" +"Exception handlers don't just handle exceptions if they occur immediately in " +"the try clause, but also if they occur inside functions that are called " +"(even indirectly) in the try clause. For example::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:210 +msgid "Raising Exceptions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:212 +msgid "" +"The :keyword:`raise` statement allows the programmer to force a specified " +"exception to occur. For example::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:220 +msgid "" +"The sole argument to :keyword:`raise` indicates the exception to be raised. " +"This must be either an exception instance or an exception class (a class " +"that derives from :class:`Exception`)." +msgstr "" + +#: ../Doc/tutorial/errors.rst:224 +msgid "" +"If you need to determine whether an exception was raised but don't intend to " +"handle it, a simpler form of the :keyword:`raise` statement allows you to re-" +"raise the exception::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:243 +msgid "User-defined Exceptions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:245 +msgid "" +"Programs may name their own exceptions by creating a new exception class " +"(see :ref:`tut-classes` for more about Python classes). Exceptions should " +"typically be derived from the :exc:`Exception` class, either directly or " +"indirectly." +msgstr "" + +#: ../Doc/tutorial/errors.rst:249 +msgid "" +"Exception classes can be defined which do anything any other class can do, " +"but are usually kept simple, often only offering a number of attributes that " +"allow information about the error to be extracted by handlers for the " +"exception. When creating a module that can raise several distinct errors, a " +"common practice is to create a base class for exceptions defined by that " +"module, and subclass that to create specific exception classes for different " +"error conditions::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:287 +msgid "" +"Most exceptions are defined with names that end in \"Error,\" similar to the " +"naming of the standard exceptions." +msgstr "" + +#: ../Doc/tutorial/errors.rst:290 +msgid "" +"Many standard modules define their own exceptions to report errors that may " +"occur in functions they define. More information on classes is presented in " +"chapter :ref:`tut-classes`." +msgstr "" + +#: ../Doc/tutorial/errors.rst:298 +msgid "Defining Clean-up Actions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:300 +msgid "" +"The :keyword:`try` statement has another optional clause which is intended " +"to define clean-up actions that must be executed under all circumstances. " +"For example::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:314 +msgid "" +"A *finally clause* is always executed before leaving the :keyword:`try` " +"statement, whether an exception has occurred or not. When an exception has " +"occurred in the :keyword:`try` clause and has not been handled by an :" +"keyword:`except` clause (or it has occurred in an :keyword:`except` or :" +"keyword:`else` clause), it is re-raised after the :keyword:`finally` clause " +"has been executed. The :keyword:`finally` clause is also executed \"on the " +"way out\" when any other clause of the :keyword:`try` statement is left via " +"a :keyword:`break`, :keyword:`continue` or :keyword:`return` statement. A " +"more complicated example::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:347 +msgid "" +"As you can see, the :keyword:`finally` clause is executed in any event. " +"The :exc:`TypeError` raised by dividing two strings is not handled by the :" +"keyword:`except` clause and therefore re-raised after the :keyword:`finally` " +"clause has been executed." +msgstr "" + +#: ../Doc/tutorial/errors.rst:352 +msgid "" +"In real world applications, the :keyword:`finally` clause is useful for " +"releasing external resources (such as files or network connections), " +"regardless of whether the use of the resource was successful." +msgstr "" + +#: ../Doc/tutorial/errors.rst:360 +msgid "Predefined Clean-up Actions" +msgstr "" + +#: ../Doc/tutorial/errors.rst:362 +msgid "" +"Some objects define standard clean-up actions to be undertaken when the " +"object is no longer needed, regardless of whether or not the operation using " +"the object succeeded or failed. Look at the following example, which tries " +"to open a file and print its contents to the screen. ::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:370 +msgid "" +"The problem with this code is that it leaves the file open for an " +"indeterminate amount of time after this part of the code has finished " +"executing. This is not an issue in simple scripts, but can be a problem for " +"larger applications. The :keyword:`with` statement allows objects like files " +"to be used in a way that ensures they are always cleaned up promptly and " +"correctly. ::" +msgstr "" + +#: ../Doc/tutorial/errors.rst:380 +msgid "" +"After the statement is executed, the file *f* is always closed, even if a " +"problem was encountered while processing the lines. Objects which, like " +"files, provide predefined clean-up actions will indicate this in their " +"documentation." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:9 +msgid "Floating Point Arithmetic: Issues and Limitations" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:14 +msgid "" +"Floating-point numbers are represented in computer hardware as base 2 " +"(binary) fractions. For example, the decimal fraction ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:19 +msgid "" +"has value 1/10 + 2/100 + 5/1000, and in the same way the binary fraction ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:23 +msgid "" +"has value 0/2 + 0/4 + 1/8. These two fractions have identical values, the " +"only real difference being that the first is written in base 10 fractional " +"notation, and the second in base 2." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:27 +msgid "" +"Unfortunately, most decimal fractions cannot be represented exactly as " +"binary fractions. A consequence is that, in general, the decimal floating-" +"point numbers you enter are only approximated by the binary floating-point " +"numbers actually stored in the machine." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:32 +msgid "" +"The problem is easier to understand at first in base 10. Consider the " +"fraction 1/3. You can approximate that as a base 10 fraction::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:37 ../Doc/tutorial/floatingpoint.rst:41 +msgid "or, better, ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:45 +msgid "" +"and so on. No matter how many digits you're willing to write down, the " +"result will never be exactly 1/3, but will be an increasingly better " +"approximation of 1/3." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:49 +msgid "" +"In the same way, no matter how many base 2 digits you're willing to use, the " +"decimal value 0.1 cannot be represented exactly as a base 2 fraction. In " +"base 2, 1/10 is the infinitely repeating fraction ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:55 +msgid "" +"Stop at any finite number of bits, and you get an approximation. On most " +"machines today, floats are approximated using a binary fraction with the " +"numerator using the first 53 bits starting with the most significant bit and " +"with the denominator as a power of two. In the case of 1/10, the binary " +"fraction is ``3602879701896397 / 2 ** 55`` which is close to but not exactly " +"equal to the true value of 1/10." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:62 +msgid "" +"Many users are not aware of the approximation because of the way values are " +"displayed. Python only prints a decimal approximation to the true decimal " +"value of the binary approximation stored by the machine. On most machines, " +"if Python were to print the true decimal value of the binary approximation " +"stored for 0.1, it would have to display ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:71 +msgid "" +"That is more digits than most people find useful, so Python keeps the number " +"of digits manageable by displaying a rounded value instead ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:77 +msgid "" +"Just remember, even though the printed result looks like the exact value of " +"1/10, the actual stored value is the nearest representable binary fraction." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:80 +msgid "" +"Interestingly, there are many different decimal numbers that share the same " +"nearest approximate binary fraction. For example, the numbers ``0.1`` and " +"``0.10000000000000001`` and " +"``0.1000000000000000055511151231257827021181583404541015625`` are all " +"approximated by ``3602879701896397 / 2 ** 55``. Since all of these decimal " +"values share the same approximation, any one of them could be displayed " +"while still preserving the invariant ``eval(repr(x)) == x``." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:88 +msgid "" +"Historically, the Python prompt and built-in :func:`repr` function would " +"choose the one with 17 significant digits, ``0.10000000000000001``. " +"Starting with Python 3.1, Python (on most systems) is now able to choose the " +"shortest of these and simply display ``0.1``." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:93 +msgid "" +"Note that this is in the very nature of binary floating-point: this is not a " +"bug in Python, and it is not a bug in your code either. You'll see the same " +"kind of thing in all languages that support your hardware's floating-point " +"arithmetic (although some languages may not *display* the difference by " +"default, or in all output modes)." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:99 +msgid "" +"For more pleasant output, you may wish to use string formatting to produce a " +"limited number of significant digits::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:111 +msgid "" +"It's important to realize that this is, in a real sense, an illusion: you're " +"simply rounding the *display* of the true machine value." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:114 +msgid "" +"One illusion may beget another. For example, since 0.1 is not exactly 1/10, " +"summing three values of 0.1 may not yield exactly 0.3, either::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:120 +msgid "" +"Also, since the 0.1 cannot get any closer to the exact value of 1/10 and 0.3 " +"cannot get any closer to the exact value of 3/10, then pre-rounding with :" +"func:`round` function cannot help::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:127 +msgid "" +"Though the numbers cannot be made closer to their intended exact values, " +"the :func:`round` function can be useful for post-rounding so that results " +"with inexact values become comparable to one another::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:134 +msgid "" +"Binary floating-point arithmetic holds many surprises like this. The " +"problem with \"0.1\" is explained in precise detail below, in the " +"\"Representation Error\" section. See `The Perils of Floating Point `_ for a more complete account of other common " +"surprises." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:139 +msgid "" +"As that says near the end, \"there are no easy answers.\" Still, don't be " +"unduly wary of floating-point! The errors in Python float operations are " +"inherited from the floating-point hardware, and on most machines are on the " +"order of no more than 1 part in 2\\*\\*53 per operation. That's more than " +"adequate for most tasks, but you do need to keep in mind that it's not " +"decimal arithmetic and that every float operation can suffer a new rounding " +"error." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:146 +msgid "" +"While pathological cases do exist, for most casual use of floating-point " +"arithmetic you'll see the result you expect in the end if you simply round " +"the display of your final results to the number of decimal digits you " +"expect. :func:`str` usually suffices, and for finer control see the :meth:" +"`str.format` method's format specifiers in :ref:`formatstrings`." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:152 +msgid "" +"For use cases which require exact decimal representation, try using the :mod:" +"`decimal` module which implements decimal arithmetic suitable for accounting " +"applications and high-precision applications." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:156 +msgid "" +"Another form of exact arithmetic is supported by the :mod:`fractions` module " +"which implements arithmetic based on rational numbers (so the numbers like " +"1/3 can be represented exactly)." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:160 +msgid "" +"If you are a heavy user of floating point operations you should take a look " +"at the Numerical Python package and many other packages for mathematical and " +"statistical operations supplied by the SciPy project. See ." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:164 +msgid "" +"Python provides tools that may help on those rare occasions when you really " +"*do* want to know the exact value of a float. The :meth:`float." +"as_integer_ratio` method expresses the value of a float as a fraction::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:173 +msgid "" +"Since the ratio is exact, it can be used to losslessly recreate the original " +"value::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:179 +msgid "" +"The :meth:`float.hex` method expresses a float in hexadecimal (base 16), " +"again giving the exact value stored by your computer::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:185 +msgid "" +"This precise hexadecimal representation can be used to reconstruct the float " +"value exactly::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:191 +msgid "" +"Since the representation is exact, it is useful for reliably porting values " +"across different versions of Python (platform independence) and exchanging " +"data with other languages that support the same format (such as Java and " +"C99)." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:195 +msgid "" +"Another helpful tool is the :func:`math.fsum` function which helps mitigate " +"loss-of-precision during summation. It tracks \"lost digits\" as values are " +"added onto a running total. That can make a difference in overall accuracy " +"so that the errors do not accumulate to the point where they affect the " +"final total:" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:209 +msgid "Representation Error" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:211 +msgid "" +"This section explains the \"0.1\" example in detail, and shows how you can " +"perform an exact analysis of cases like this yourself. Basic familiarity " +"with binary floating-point representation is assumed." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:215 +msgid "" +":dfn:`Representation error` refers to the fact that some (most, actually) " +"decimal fractions cannot be represented exactly as binary (base 2) " +"fractions. This is the chief reason why Python (or Perl, C, C++, Java, " +"Fortran, and many others) often won't display the exact decimal number you " +"expect." +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:220 +msgid "" +"Why is that? 1/10 is not exactly representable as a binary fraction. Almost " +"all machines today (November 2000) use IEEE-754 floating point arithmetic, " +"and almost all platforms map Python floats to IEEE-754 \"double precision" +"\". 754 doubles contain 53 bits of precision, so on input the computer " +"strives to convert 0.1 to the closest fraction it can of the form *J*/2**\\ " +"*N* where *J* is an integer containing exactly 53 bits. Rewriting ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:229 +msgid "as ::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:233 +msgid "" +"and recalling that *J* has exactly 53 bits (is ``>= 2**52`` but ``< " +"2**53``), the best value for *N* is 56::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:239 +msgid "" +"That is, 56 is the only value for *N* that leaves *J* with exactly 53 bits. " +"The best possible value for *J* is then that quotient rounded::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:246 +msgid "" +"Since the remainder is more than half of 10, the best approximation is " +"obtained by rounding up::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:252 +msgid "" +"Therefore the best possible approximation to 1/10 in 754 double precision " +"is::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:256 +msgid "" +"Dividing both the numerator and denominator by two reduces the fraction to::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:260 +msgid "" +"Note that since we rounded up, this is actually a little bit larger than " +"1/10; if we had not rounded up, the quotient would have been a little bit " +"smaller than 1/10. But in no case can it be *exactly* 1/10!" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:264 +msgid "" +"So the computer never \"sees\" 1/10: what it sees is the exact fraction " +"given above, the best 754 double approximation it can get::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:270 +msgid "" +"If we multiply that fraction by 10\\*\\*55, we can see the value out to 55 " +"decimal digits::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:276 +msgid "" +"meaning that the exact number stored in the computer is equal to the decimal " +"value 0.1000000000000000055511151231257827021181583404541015625. Instead of " +"displaying the full decimal value, many languages (including older versions " +"of Python), round the result to 17 significant digits::" +msgstr "" + +#: ../Doc/tutorial/floatingpoint.rst:284 +msgid "" +"The :mod:`fractions` and :mod:`decimal` modules make these calculations " +"easy::" +msgstr "" + +#: ../Doc/tutorial/index.rst:5 +msgid "The Python Tutorial" +msgstr "" + +#: ../Doc/tutorial/index.rst:7 +msgid "" +"Python is an easy to learn, powerful programming language. It has efficient " +"high-level data structures and a simple but effective approach to object-" +"oriented programming. Python's elegant syntax and dynamic typing, together " +"with its interpreted nature, make it an ideal language for scripting and " +"rapid application development in many areas on most platforms." +msgstr "" + +#: ../Doc/tutorial/index.rst:13 +msgid "" +"The Python interpreter and the extensive standard library are freely " +"available in source or binary form for all major platforms from the Python " +"Web site, https://www.python.org/, and may be freely distributed. The same " +"site also contains distributions of and pointers to many free third party " +"Python modules, programs and tools, and additional documentation." +msgstr "" + +#: ../Doc/tutorial/index.rst:19 +msgid "" +"The Python interpreter is easily extended with new functions and data types " +"implemented in C or C++ (or other languages callable from C). Python is also " +"suitable as an extension language for customizable applications." +msgstr "" + +#: ../Doc/tutorial/index.rst:23 +msgid "" +"This tutorial introduces the reader informally to the basic concepts and " +"features of the Python language and system. It helps to have a Python " +"interpreter handy for hands-on experience, but all examples are self-" +"contained, so the tutorial can be read off-line as well." +msgstr "" + +#: ../Doc/tutorial/index.rst:28 +msgid "" +"For a description of standard objects and modules, see :ref:`library-" +"index`. :ref:`reference-index` gives a more formal definition of the " +"language. To write extensions in C or C++, read :ref:`extending-index` and :" +"ref:`c-api-index`. There are also several books covering Python in depth." +msgstr "" + +#: ../Doc/tutorial/index.rst:33 +msgid "" +"This tutorial does not attempt to be comprehensive and cover every single " +"feature, or even every commonly used feature. Instead, it introduces many of " +"Python's most noteworthy features, and will give you a good idea of the " +"language's flavor and style. After reading it, you will be able to read and " +"write Python modules and programs, and you will be ready to learn more about " +"the various Python library modules described in :ref:`library-index`." +msgstr "" + +#: ../Doc/tutorial/index.rst:40 +msgid "The :ref:`glossary` is also worth going through." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:5 +msgid "Input and Output" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:7 +msgid "" +"There are several ways to present the output of a program; data can be " +"printed in a human-readable form, or written to a file for future use. This " +"chapter will discuss some of the possibilities." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:15 +msgid "Fancier Output Formatting" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:17 +msgid "" +"So far we've encountered two ways of writing values: *expression statements* " +"and the :func:`print` function. (A third way is using the :meth:`write` " +"method of file objects; the standard output file can be referenced as ``sys." +"stdout``. See the Library Reference for more information on this.)" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:22 +msgid "" +"Often you'll want more control over the formatting of your output than " +"simply printing space-separated values. There are two ways to format your " +"output; the first way is to do all the string handling yourself; using " +"string slicing and concatenation operations you can create any layout you " +"can imagine. The string type has some methods that perform useful " +"operations for padding strings to a given column width; these will be " +"discussed shortly. The second way is to use :ref:`formatted string literals " +"`, or the :meth:`str.format` method." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:31 +msgid "" +"The :mod:`string` module contains a :class:`~string.Template` class which " +"offers yet another way to substitute values into strings." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:34 +msgid "" +"One question remains, of course: how do you convert values to strings? " +"Luckily, Python has ways to convert any value to a string: pass it to the :" +"func:`repr` or :func:`str` functions." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:38 +msgid "" +"The :func:`str` function is meant to return representations of values which " +"are fairly human-readable, while :func:`repr` is meant to generate " +"representations which can be read by the interpreter (or will force a :exc:" +"`SyntaxError` if there is no equivalent syntax). For objects which don't " +"have a particular representation for human consumption, :func:`str` will " +"return the same value as :func:`repr`. Many values, such as numbers or " +"structures like lists and dictionaries, have the same representation using " +"either function. Strings, in particular, have two distinct representations." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:47 ../Doc/tutorial/introduction.rst:22 +msgid "Some examples::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:70 +msgid "Here are two ways to write a table of squares and cubes::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:102 +msgid "" +"(Note that in the first example, one space between each column was added by " +"the way :func:`print` works: it always adds spaces between its arguments.)" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:105 +msgid "" +"This example demonstrates the :meth:`str.rjust` method of string objects, " +"which right-justifies a string in a field of a given width by padding it " +"with spaces on the left. There are similar methods :meth:`str.ljust` and :" +"meth:`str.center`. These methods do not write anything, they just return a " +"new string. If the input string is too long, they don't truncate it, but " +"return it unchanged; this will mess up your column lay-out but that's " +"usually better than the alternative, which would be lying about a value. " +"(If you really want truncation you can always add a slice operation, as in " +"``x.ljust(n)[:n]``.)" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:115 +msgid "" +"There is another method, :meth:`str.zfill`, which pads a numeric string on " +"the left with zeros. It understands about plus and minus signs::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:125 +msgid "Basic usage of the :meth:`str.format` method looks like this::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:130 +msgid "" +"The brackets and characters within them (called format fields) are replaced " +"with the objects passed into the :meth:`str.format` method. A number in the " +"brackets can be used to refer to the position of the object passed into the :" +"meth:`str.format` method. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:140 +msgid "" +"If keyword arguments are used in the :meth:`str.format` method, their values " +"are referred to by using the name of the argument. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:147 +msgid "Positional and keyword arguments can be arbitrarily combined::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:153 +msgid "" +"``'!a'`` (apply :func:`ascii`), ``'!s'`` (apply :func:`str`) and ``'!r'`` " +"(apply :func:`repr`) can be used to convert the value before it is " +"formatted::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:162 +msgid "" +"An optional ``':'`` and format specifier can follow the field name. This " +"allows greater control over how the value is formatted. The following " +"example rounds Pi to three places after the decimal." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:170 +msgid "" +"Passing an integer after the ``':'`` will cause that field to be a minimum " +"number of characters wide. This is useful for making tables pretty. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:181 +msgid "" +"If you have a really long format string that you don't want to split up, it " +"would be nice if you could reference the variables to be formatted by name " +"instead of by position. This can be done by simply passing the dict and " +"using square brackets ``'[]'`` to access the keys ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:191 +msgid "" +"This could also be done by passing the table as keyword arguments with the " +"'**' notation. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:198 +msgid "" +"This is particularly useful in combination with the built-in function :func:" +"`vars`, which returns a dictionary containing all local variables." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:201 +msgid "" +"For a complete overview of string formatting with :meth:`str.format`, see :" +"ref:`formatstrings`." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:206 +msgid "Old string formatting" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:208 +msgid "" +"The ``%`` operator can also be used for string formatting. It interprets the " +"left argument much like a :c:func:`sprintf`\\ -style format string to be " +"applied to the right argument, and returns the string resulting from this " +"formatting operation. For example::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:217 +msgid "" +"More information can be found in the :ref:`old-string-formatting` section." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:223 +msgid "Reading and Writing Files" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:229 +msgid "" +":func:`open` returns a :term:`file object`, and is most commonly used with " +"two arguments: ``open(filename, mode)``." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:241 +msgid "" +"The first argument is a string containing the filename. The second argument " +"is another string containing a few characters describing the way in which " +"the file will be used. *mode* can be ``'r'`` when the file will only be " +"read, ``'w'`` for only writing (an existing file with the same name will be " +"erased), and ``'a'`` opens the file for appending; any data written to the " +"file is automatically added to the end. ``'r+'`` opens the file for both " +"reading and writing. The *mode* argument is optional; ``'r'`` will be " +"assumed if it's omitted." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:250 +msgid "" +"Normally, files are opened in :dfn:`text mode`, that means, you read and " +"write strings from and to the file, which are encoded in a specific " +"encoding. If encoding is not specified, the default is platform dependent " +"(see :func:`open`). ``'b'`` appended to the mode opens the file in :dfn:" +"`binary mode`: now the data is read and written in the form of bytes " +"objects. This mode should be used for all files that don't contain text." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:257 +msgid "" +"In text mode, the default when reading is to convert platform-specific line " +"endings (``\\n`` on Unix, ``\\r\\n`` on Windows) to just ``\\n``. When " +"writing in text mode, the default is to convert occurrences of ``\\n`` back " +"to platform-specific line endings. This behind-the-scenes modification to " +"file data is fine for text files, but will corrupt binary data like that in :" +"file:`JPEG` or :file:`EXE` files. Be very careful to use binary mode when " +"reading and writing such files." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:269 +msgid "Methods of File Objects" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:271 +msgid "" +"The rest of the examples in this section will assume that a file object " +"called ``f`` has already been created." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:274 +msgid "" +"To read a file's contents, call ``f.read(size)``, which reads some quantity " +"of data and returns it as a string (in text mode) or bytes object (in binary " +"mode). *size* is an optional numeric argument. When *size* is omitted or " +"negative, the entire contents of the file will be read and returned; it's " +"your problem if the file is twice as large as your machine's memory. " +"Otherwise, at most *size* bytes are read and returned. If the end of the " +"file has been reached, ``f.read()`` will return an empty string (``''``). ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:288 +msgid "" +"``f.readline()`` reads a single line from the file; a newline character (``" +"\\n``) is left at the end of the string, and is only omitted on the last " +"line of the file if the file doesn't end in a newline. This makes the " +"return value unambiguous; if ``f.readline()`` returns an empty string, the " +"end of the file has been reached, while a blank line is represented by " +"``'\\n'``, a string containing only a single newline. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:302 +msgid "" +"For reading lines from a file, you can loop over the file object. This is " +"memory efficient, fast, and leads to simple code::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:311 +msgid "" +"If you want to read all the lines of a file in a list you can also use " +"``list(f)`` or ``f.readlines()``." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:314 +msgid "" +"``f.write(string)`` writes the contents of *string* to the file, returning " +"the number of characters written. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:320 +msgid "" +"Other types of objects need to be converted -- either to a string (in text " +"mode) or a bytes object (in binary mode) -- before writing them::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:328 +msgid "" +"``f.tell()`` returns an integer giving the file object's current position in " +"the file represented as number of bytes from the beginning of the file when " +"in binary mode and an opaque number when in text mode." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:332 +msgid "" +"To change the file object's position, use ``f.seek(offset, from_what)``. " +"The position is computed from adding *offset* to a reference point; the " +"reference point is selected by the *from_what* argument. A *from_what* " +"value of 0 measures from the beginning of the file, 1 uses the current file " +"position, and 2 uses the end of the file as the reference point. " +"*from_what* can be omitted and defaults to 0, using the beginning of the " +"file as the reference point. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:351 +msgid "" +"In text files (those opened without a ``b`` in the mode string), only seeks " +"relative to the beginning of the file are allowed (the exception being " +"seeking to the very file end with ``seek(0, 2)``) and the only valid " +"*offset* values are those returned from the ``f.tell()``, or zero. Any other " +"*offset* value produces undefined behaviour." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:358 +msgid "" +"When you're done with a file, call ``f.close()`` to close it and free up any " +"system resources taken up by the open file. After calling ``f.close()``, " +"attempts to use the file object will automatically fail. ::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:368 +msgid "" +"It is good practice to use the :keyword:`with` keyword when dealing with " +"file objects. This has the advantage that the file is properly closed after " +"its suite finishes, even if an exception is raised on the way. It is also " +"much shorter than writing equivalent :keyword:`try`\\ -\\ :keyword:`finally` " +"blocks::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:378 +msgid "" +"File objects have some additional methods, such as :meth:`~file.isatty` and :" +"meth:`~file.truncate` which are less frequently used; consult the Library " +"Reference for a complete guide to file objects." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:386 +msgid "Saving structured data with :mod:`json`" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:390 +msgid "" +"Strings can easily be written to and read from a file. Numbers take a bit " +"more effort, since the :meth:`read` method only returns strings, which will " +"have to be passed to a function like :func:`int`, which takes a string like " +"``'123'`` and returns its numeric value 123. When you want to save more " +"complex data types like nested lists and dictionaries, parsing and " +"serializing by hand becomes complicated." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:397 +msgid "" +"Rather than having users constantly writing and debugging code to save " +"complicated data types to files, Python allows you to use the popular data " +"interchange format called `JSON (JavaScript Object Notation) `_. The standard module called :mod:`json` can take Python data " +"hierarchies, and convert them to string representations; this process is " +"called :dfn:`serializing`. Reconstructing the data from the string " +"representation is called :dfn:`deserializing`. Between serializing and " +"deserializing, the string representing the object may have been stored in a " +"file or data, or sent over a network connection to some distant machine." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:408 +msgid "" +"The JSON format is commonly used by modern applications to allow for data " +"exchange. Many programmers are already familiar with it, which makes it a " +"good choice for interoperability." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:412 +msgid "" +"If you have an object ``x``, you can view its JSON string representation " +"with a simple line of code::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:418 +msgid "" +"Another variant of the :func:`~json.dumps` function, called :func:`~json." +"dump`, simply serializes the object to a :term:`text file`. So if ``f`` is " +"a :term:`text file` object opened for writing, we can do this::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:424 +msgid "" +"To decode the object again, if ``f`` is a :term:`text file` object which has " +"been opened for reading::" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:429 +msgid "" +"This simple serialization technique can handle lists and dictionaries, but " +"serializing arbitrary class instances in JSON requires a bit of extra " +"effort. The reference for the :mod:`json` module contains an explanation of " +"this." +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:435 +msgid ":mod:`pickle` - the pickle module" +msgstr "" + +#: ../Doc/tutorial/inputoutput.rst:437 +msgid "" +"Contrary to :ref:`JSON `, *pickle* is a protocol which allows the " +"serialization of arbitrarily complex Python objects. As such, it is " +"specific to Python and cannot be used to communicate with applications " +"written in other languages. It is also insecure by default: deserializing " +"pickle data coming from an untrusted source can execute arbitrary code, if " +"the data was crafted by a skilled attacker." +msgstr "" + +#: ../Doc/tutorial/interactive.rst:5 +msgid "Interactive Input Editing and History Substitution" +msgstr "" + +#: ../Doc/tutorial/interactive.rst:7 +msgid "" +"Some versions of the Python interpreter support editing of the current input " +"line and history substitution, similar to facilities found in the Korn shell " +"and the GNU Bash shell. This is implemented using the `GNU Readline`_ " +"library, which supports various styles of editing. This library has its own " +"documentation which we won't duplicate here." +msgstr "" + +#: ../Doc/tutorial/interactive.rst:17 +msgid "Tab Completion and History Editing" +msgstr "" + +#: ../Doc/tutorial/interactive.rst:19 +msgid "" +"Completion of variable and module names is :ref:`automatically enabled " +"` at interpreter startup so that the :kbd:`Tab` key " +"invokes the completion function; it looks at Python statement names, the " +"current local variables, and the available module names. For dotted " +"expressions such as ``string.a``, it will evaluate the expression up to the " +"final ``'.'`` and then suggest completions from the attributes of the " +"resulting object. Note that this may execute application-defined code if an " +"object with a :meth:`__getattr__` method is part of the expression. The " +"default configuration also saves your history into a file named :file:`." +"python_history` in your user directory. The history will be available again " +"during the next interactive interpreter session." +msgstr "" + +#: ../Doc/tutorial/interactive.rst:36 +msgid "Alternatives to the Interactive Interpreter" +msgstr "" + +#: ../Doc/tutorial/interactive.rst:38 +msgid "" +"This facility is an enormous step forward compared to earlier versions of " +"the interpreter; however, some wishes are left: It would be nice if the " +"proper indentation were suggested on continuation lines (the parser knows if " +"an indent token is required next). The completion mechanism might use the " +"interpreter's symbol table. A command to check (or even suggest) matching " +"parentheses, quotes, etc., would also be useful." +msgstr "" + +#: ../Doc/tutorial/interactive.rst:45 +msgid "" +"One alternative enhanced interactive interpreter that has been around for " +"quite some time is IPython_, which features tab completion, object " +"exploration and advanced history management. It can also be thoroughly " +"customized and embedded into other applications. Another similar enhanced " +"interactive environment is bpython_." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:5 +msgid "Using the Python Interpreter" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:11 +msgid "Invoking the Interpreter" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:13 +msgid "" +"The Python interpreter is usually installed as :file:`/usr/local/bin/" +"python3.6` on those machines where it is available; putting :file:`/usr/" +"local/bin` in your Unix shell's search path makes it possible to start it by " +"typing the command:" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:21 +msgid "" +"to the shell. [#]_ Since the choice of the directory where the interpreter " +"lives is an installation option, other places are possible; check with your " +"local Python guru or system administrator. (E.g., :file:`/usr/local/python` " +"is a popular alternative location.)" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:26 +msgid "" +"On Windows machines, the Python installation is usually placed in :file:`C:\\" +"\\Python36`, though you can change this when you're running the installer. " +"To add this directory to your path, you can type the following command into " +"the command prompt in a DOS box::" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:33 +msgid "" +"Typing an end-of-file character (:kbd:`Control-D` on Unix, :kbd:`Control-Z` " +"on Windows) at the primary prompt causes the interpreter to exit with a zero " +"exit status. If that doesn't work, you can exit the interpreter by typing " +"the following command: ``quit()``." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:38 +msgid "" +"The interpreter's line-editing features include interactive editing, history " +"substitution and code completion on systems that support readline. Perhaps " +"the quickest check to see whether command line editing is supported is " +"typing :kbd:`Control-P` to the first Python prompt you get. If it beeps, " +"you have command line editing; see Appendix :ref:`tut-interacting` for an " +"introduction to the keys. If nothing appears to happen, or if ``^P`` is " +"echoed, command line editing isn't available; you'll only be able to use " +"backspace to remove characters from the current line." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:47 +msgid "" +"The interpreter operates somewhat like the Unix shell: when called with " +"standard input connected to a tty device, it reads and executes commands " +"interactively; when called with a file name argument or with a file as " +"standard input, it reads and executes a *script* from that file." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:52 +msgid "" +"A second way of starting the interpreter is ``python -c command [arg] ...``, " +"which executes the statement(s) in *command*, analogous to the shell's :" +"option:`-c` option. Since Python statements often contain spaces or other " +"characters that are special to the shell, it is usually advised to quote " +"*command* in its entirety with single quotes." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:58 +msgid "" +"Some Python modules are also useful as scripts. These can be invoked using " +"``python -m module [arg] ...``, which executes the source file for *module* " +"as if you had spelled out its full name on the command line." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:62 +msgid "" +"When a script file is used, it is sometimes useful to be able to run the " +"script and enter interactive mode afterwards. This can be done by passing :" +"option:`-i` before the script." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:66 +msgid "All command line options are described in :ref:`using-on-general`." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:72 +msgid "Argument Passing" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:74 +msgid "" +"When known to the interpreter, the script name and additional arguments " +"thereafter are turned into a list of strings and assigned to the ``argv`` " +"variable in the ``sys`` module. You can access this list by executing " +"``import sys``. The length of the list is at least one; when no script and " +"no arguments are given, ``sys.argv[0]`` is an empty string. When the script " +"name is given as ``'-'`` (meaning standard input), ``sys.argv[0]`` is set " +"to ``'-'``. When :option:`-c` *command* is used, ``sys.argv[0]`` is set to " +"``'-c'``. When :option:`-m` *module* is used, ``sys.argv[0]`` is set to " +"the full name of the located module. Options found after :option:`-c` " +"*command* or :option:`-m` *module* are not consumed by the Python " +"interpreter's option processing but left in ``sys.argv`` for the command or " +"module to handle." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:92 +msgid "" +"When commands are read from a tty, the interpreter is said to be in " +"*interactive mode*. In this mode it prompts for the next command with the " +"*primary prompt*, usually three greater-than signs (``>>>``); for " +"continuation lines it prompts with the *secondary prompt*, by default three " +"dots (``...``). The interpreter prints a welcome message stating its version " +"number and a copyright notice before printing the first prompt:" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:109 +msgid "" +"Continuation lines are needed when entering a multi-line construct. As an " +"example, take a look at this :keyword:`if` statement::" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:119 +msgid "For more on interactive mode, see :ref:`tut-interac`." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:125 +msgid "The Interpreter and Its Environment" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:131 +msgid "Source Code Encoding" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:133 +msgid "" +"By default, Python source files are treated as encoded in UTF-8. In that " +"encoding, characters of most languages in the world can be used " +"simultaneously in string literals, identifiers and comments --- although the " +"standard library only uses ASCII characters for identifiers, a convention " +"that any portable code should follow. To display all these characters " +"properly, your editor must recognize that the file is UTF-8, and it must use " +"a font that supports all the characters in the file." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:141 +msgid "" +"It is also possible to specify a different encoding for source files. In " +"order to do this, put one more special comment line right after the ``#!`` " +"line to define the source file encoding::" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:147 +msgid "" +"With that declaration, everything in the source file will be treated as " +"having the encoding *encoding* instead of UTF-8. The list of possible " +"encodings can be found in the Python Library Reference, in the section on :" +"mod:`codecs`." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:151 +msgid "" +"For example, if your editor of choice does not support UTF-8 encoded files " +"and insists on using some other encoding, say Windows-1252, you can write::" +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:156 +msgid "" +"and still use all characters in the Windows-1252 character set in the source " +"files. The special encoding comment must be in the *first or second* line " +"within the file." +msgstr "" + +#: ../Doc/tutorial/interpreter.rst:163 +msgid "" +"On Unix, the Python 3.x interpreter is by default not installed with the " +"executable named ``python``, so that it does not conflict with a " +"simultaneously installed Python 2.x executable." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:5 +msgid "An Informal Introduction to Python" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:7 +msgid "" +"In the following examples, input and output are distinguished by the " +"presence or absence of prompts (:term:`>>>` and :term:`...`): to repeat the " +"example, you must type everything after the prompt, when the prompt appears; " +"lines that do not begin with a prompt are output from the interpreter. Note " +"that a secondary prompt on a line by itself in an example means you must " +"type a blank line; this is used to end a multi-line command." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:14 +msgid "" +"Many of the examples in this manual, even those entered at the interactive " +"prompt, include comments. Comments in Python start with the hash character, " +"``#``, and extend to the end of the physical line. A comment may appear at " +"the start of a line or following whitespace or code, but not within a string " +"literal. A hash character within a string literal is just a hash character. " +"Since comments are to clarify code and are not interpreted by Python, they " +"may be omitted when typing in examples." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:33 +msgid "Using Python as a Calculator" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:35 +msgid "" +"Let's try some simple Python commands. Start the interpreter and wait for " +"the primary prompt, ``>>>``. (It shouldn't take long.)" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:42 +msgid "Numbers" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:44 +msgid "" +"The interpreter acts as a simple calculator: you can type an expression at " +"it and it will write the value. Expression syntax is straightforward: the " +"operators ``+``, ``-``, ``*`` and ``/`` work just like in most other " +"languages (for example, Pascal or C); parentheses (``()``) can be used for " +"grouping. For example::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:59 +msgid "" +"The integer numbers (e.g. ``2``, ``4``, ``20``) have type :class:`int`, the " +"ones with a fractional part (e.g. ``5.0``, ``1.6``) have type :class:" +"`float`. We will see more about numeric types later in the tutorial." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:63 +msgid "" +"Division (``/``) always returns a float. To do :term:`floor division` and " +"get an integer result (discarding any fractional result) you can use the ``//" +"`` operator; to calculate the remainder you can use ``%``::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:77 +msgid "" +"With Python, it is possible to use the ``**`` operator to calculate powers " +"[#]_::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:84 +msgid "" +"The equal sign (``=``) is used to assign a value to a variable. Afterwards, " +"no result is displayed before the next interactive prompt::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:92 +msgid "" +"If a variable is not \"defined\" (assigned a value), trying to use it will " +"give you an error::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:100 +msgid "" +"There is full support for floating point; operators with mixed type operands " +"convert the integer operand to floating point::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:108 +msgid "" +"In interactive mode, the last printed expression is assigned to the variable " +"``_``. This means that when you are using Python as a desk calculator, it " +"is somewhat easier to continue calculations, for example::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:121 +msgid "" +"This variable should be treated as read-only by the user. Don't explicitly " +"assign a value to it --- you would create an independent local variable with " +"the same name masking the built-in variable with its magic behavior." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:125 +msgid "" +"In addition to :class:`int` and :class:`float`, Python supports other types " +"of numbers, such as :class:`~decimal.Decimal` and :class:`~fractions." +"Fraction`. Python also has built-in support for :ref:`complex numbers " +"`, and uses the ``j`` or ``J`` suffix to indicate the " +"imaginary part (e.g. ``3+5j``)." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:135 +msgid "Strings" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:137 +msgid "" +"Besides numbers, Python can also manipulate strings, which can be expressed " +"in several ways. They can be enclosed in single quotes (``'...'``) or " +"double quotes (``\"...\"``) with the same result [#]_. ``\\`` can be used " +"to escape quotes::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:155 +msgid "" +"In the interactive interpreter, the output string is enclosed in quotes and " +"special characters are escaped with backslashes. While this might sometimes " +"look different from the input (the enclosing quotes could change), the two " +"strings are equivalent. The string is enclosed in double quotes if the " +"string contains a single quote and no double quotes, otherwise it is " +"enclosed in single quotes. The :func:`print` function produces a more " +"readable output, by omitting the enclosing quotes and by printing escaped " +"and special characters::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:175 +msgid "" +"If you don't want characters prefaced by ``\\`` to be interpreted as special " +"characters, you can use *raw strings* by adding an ``r`` before the first " +"quote::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:185 +msgid "" +"String literals can span multiple lines. One way is using triple-quotes: ``" +"\"\"\"...\"\"\"`` or ``'''...'''``. End of lines are automatically included " +"in the string, but it's possible to prevent this by adding a ``\\`` at the " +"end of the line. The following example::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:196 +msgid "" +"produces the following output (note that the initial newline is not " +"included):" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:204 +msgid "" +"Strings can be concatenated (glued together) with the ``+`` operator, and " +"repeated with ``*``::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:211 +msgid "" +"Two or more *string literals* (i.e. the ones enclosed between quotes) next " +"to each other are automatically concatenated. ::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:217 +msgid "" +"This only works with two literals though, not with variables or expressions::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:227 +msgid "" +"If you want to concatenate variables or a variable and a literal, use ``+``::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:232 +msgid "" +"This feature is particularly useful when you want to break long strings::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:239 +msgid "" +"Strings can be *indexed* (subscripted), with the first character having " +"index 0. There is no separate character type; a character is simply a string " +"of size one::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:249 +msgid "" +"Indices may also be negative numbers, to start counting from the right::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:258 +msgid "Note that since -0 is the same as 0, negative indices start from -1." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:260 +msgid "" +"In addition to indexing, *slicing* is also supported. While indexing is " +"used to obtain individual characters, *slicing* allows you to obtain " +"substring::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:268 +msgid "" +"Note how the start is always included, and the end always excluded. This " +"makes sure that ``s[:i] + s[i:]`` is always equal to ``s``::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:276 +msgid "" +"Slice indices have useful defaults; an omitted first index defaults to zero, " +"an omitted second index defaults to the size of the string being sliced. ::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:286 +msgid "" +"One way to remember how slices work is to think of the indices as pointing " +"*between* characters, with the left edge of the first character numbered 0. " +"Then the right edge of the last character of a string of *n* characters has " +"index *n*, for example::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:297 +msgid "" +"The first row of numbers gives the position of the indices 0...6 in the " +"string; the second row gives the corresponding negative indices. The slice " +"from *i* to *j* consists of all characters between the edges labeled *i* and " +"*j*, respectively." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:302 +msgid "" +"For non-negative indices, the length of a slice is the difference of the " +"indices, if both are within bounds. For example, the length of " +"``word[1:3]`` is 2." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:306 +msgid "Attempting to use an index that is too large will result in an error::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:313 +msgid "" +"However, out of range slice indexes are handled gracefully when used for " +"slicing::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:321 +msgid "" +"Python strings cannot be changed --- they are :term:`immutable`. Therefore, " +"assigning to an indexed position in the string results in an error::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:331 +msgid "If you need a different string, you should create a new one::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:338 +msgid "The built-in function :func:`len` returns the length of a string::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:349 +msgid ":ref:`textseq`" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:348 +msgid "" +"Strings are examples of *sequence types*, and support the common operations " +"supported by such types." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:353 +msgid ":ref:`string-methods`" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:352 +msgid "" +"Strings support a large number of methods for basic transformations and " +"searching." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:356 +msgid ":ref:`f-strings`" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:356 +msgid "String literals that have embedded expressions." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:359 +msgid ":ref:`formatstrings`" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:359 +msgid "Information about string formatting with :meth:`str.format`." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:362 +msgid ":ref:`old-string-formatting`" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:362 +msgid "" +"The old formatting operations invoked when strings and Unicode strings are " +"the left operand of the ``%`` operator are described in more detail here." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:369 +msgid "Lists" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:371 +msgid "" +"Python knows a number of *compound* data types, used to group together other " +"values. The most versatile is the *list*, which can be written as a list of " +"comma-separated values (items) between square brackets. Lists might contain " +"items of different types, but usually the items all have the same type. ::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:380 +msgid "" +"Like strings (and all other built-in :term:`sequence` type), lists can be " +"indexed and sliced::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:390 +msgid "" +"All slice operations return a new list containing the requested elements. " +"This means that the following slice returns a new (shallow) copy of the " +"list::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:396 +msgid "Lists also support operations like concatenation::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:401 +msgid "" +"Unlike strings, which are :term:`immutable`, lists are a :term:`mutable` " +"type, i.e. it is possible to change their content::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:411 +msgid "" +"You can also add new items at the end of the list, by using the :meth:`~list." +"append` *method* (we will see more about methods later)::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:419 +msgid "" +"Assignment to slices is also possible, and this can even change the size of " +"the list or clear it entirely::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:438 +msgid "The built-in function :func:`len` also applies to lists::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:444 +msgid "" +"It is possible to nest lists (create lists containing other lists), for " +"example::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:460 +msgid "First Steps Towards Programming" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:462 +msgid "" +"Of course, we can use Python for more complicated tasks than adding two and " +"two together. For instance, we can write an initial sub-sequence of the " +"*Fibonacci* series as follows::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:480 +msgid "This example introduces several new features." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:482 +msgid "" +"The first line contains a *multiple assignment*: the variables ``a`` and " +"``b`` simultaneously get the new values 0 and 1. On the last line this is " +"used again, demonstrating that the expressions on the right-hand side are " +"all evaluated first before any of the assignments take place. The right-" +"hand side expressions are evaluated from the left to the right." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:488 +msgid "" +"The :keyword:`while` loop executes as long as the condition (here: ``b < " +"10``) remains true. In Python, like in C, any non-zero integer value is " +"true; zero is false. The condition may also be a string or list value, in " +"fact any sequence; anything with a non-zero length is true, empty sequences " +"are false. The test used in the example is a simple comparison. The " +"standard comparison operators are written the same as in C: ``<`` (less " +"than), ``>`` (greater than), ``==`` (equal to), ``<=`` (less than or equal " +"to), ``>=`` (greater than or equal to) and ``!=`` (not equal to)." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:497 +msgid "" +"The *body* of the loop is *indented*: indentation is Python's way of " +"grouping statements. At the interactive prompt, you have to type a tab or " +"space(s) for each indented line. In practice you will prepare more " +"complicated input for Python with a text editor; all decent text editors " +"have an auto-indent facility. When a compound statement is entered " +"interactively, it must be followed by a blank line to indicate completion " +"(since the parser cannot guess when you have typed the last line). Note " +"that each line within a basic block must be indented by the same amount." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:506 +msgid "" +"The :func:`print` function writes the value of the argument(s) it is given. " +"It differs from just writing the expression you want to write (as we did " +"earlier in the calculator examples) in the way it handles multiple " +"arguments, floating point quantities, and strings. Strings are printed " +"without quotes, and a space is inserted between items, so you can format " +"things nicely, like this::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:517 +msgid "" +"The keyword argument *end* can be used to avoid the newline after the " +"output, or end the output with a different string::" +msgstr "" + +#: ../Doc/tutorial/introduction.rst:530 +msgid "" +"Since ``**`` has higher precedence than ``-``, ``-3**2`` will be interpreted " +"as ``-(3**2)`` and thus result in ``-9``. To avoid this and get ``9``, you " +"can use ``(-3)**2``." +msgstr "" + +#: ../Doc/tutorial/introduction.rst:534 +msgid "" +"Unlike other languages, special characters such as ``\\n`` have the same " +"meaning with both single (``'...'``) and double (``\"...\"``) quotes. The " +"only difference between the two is that within single quotes you don't need " +"to escape ``\"`` (but you have to escape ``\\'``) and vice versa." +msgstr "" + +#: ../Doc/tutorial/modules.rst:5 +msgid "Modules" +msgstr "" + +#: ../Doc/tutorial/modules.rst:7 +msgid "" +"If you quit from the Python interpreter and enter it again, the definitions " +"you have made (functions and variables) are lost. Therefore, if you want to " +"write a somewhat longer program, you are better off using a text editor to " +"prepare the input for the interpreter and running it with that file as input " +"instead. This is known as creating a *script*. As your program gets " +"longer, you may want to split it into several files for easier maintenance. " +"You may also want to use a handy function that you've written in several " +"programs without copying its definition into each program." +msgstr "" + +#: ../Doc/tutorial/modules.rst:16 +msgid "" +"To support this, Python has a way to put definitions in a file and use them " +"in a script or in an interactive instance of the interpreter. Such a file is " +"called a *module*; definitions from a module can be *imported* into other " +"modules or into the *main* module (the collection of variables that you have " +"access to in a script executed at the top level and in calculator mode)." +msgstr "" + +#: ../Doc/tutorial/modules.rst:22 +msgid "" +"A module is a file containing Python definitions and statements. The file " +"name is the module name with the suffix :file:`.py` appended. Within a " +"module, the module's name (as a string) is available as the value of the " +"global variable ``__name__``. For instance, use your favorite text editor " +"to create a file called :file:`fibo.py` in the current directory with the " +"following contents::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:45 +msgid "" +"Now enter the Python interpreter and import this module with the following " +"command::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:50 +msgid "" +"This does not enter the names of the functions defined in ``fibo`` directly " +"in the current symbol table; it only enters the module name ``fibo`` there. " +"Using the module name you can access the functions::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:61 +msgid "" +"If you intend to use a function often you can assign it to a local name::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:71 +msgid "More on Modules" +msgstr "" + +#: ../Doc/tutorial/modules.rst:73 +msgid "" +"A module can contain executable statements as well as function definitions. " +"These statements are intended to initialize the module. They are executed " +"only the *first* time the module name is encountered in an import statement. " +"[#]_ (They are also run if the file is executed as a script.)" +msgstr "" + +#: ../Doc/tutorial/modules.rst:78 +msgid "" +"Each module has its own private symbol table, which is used as the global " +"symbol table by all functions defined in the module. Thus, the author of a " +"module can use global variables in the module without worrying about " +"accidental clashes with a user's global variables. On the other hand, if you " +"know what you are doing you can touch a module's global variables with the " +"same notation used to refer to its functions, ``modname.itemname``." +msgstr "" + +#: ../Doc/tutorial/modules.rst:85 +msgid "" +"Modules can import other modules. It is customary but not required to place " +"all :keyword:`import` statements at the beginning of a module (or script, " +"for that matter). The imported module names are placed in the importing " +"module's global symbol table." +msgstr "" + +#: ../Doc/tutorial/modules.rst:90 +msgid "" +"There is a variant of the :keyword:`import` statement that imports names " +"from a module directly into the importing module's symbol table. For " +"example::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:97 +msgid "" +"This does not introduce the module name from which the imports are taken in " +"the local symbol table (so in the example, ``fibo`` is not defined)." +msgstr "" + +#: ../Doc/tutorial/modules.rst:100 +msgid "There is even a variant to import all names that a module defines::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:106 +msgid "" +"This imports all names except those beginning with an underscore (``_``). In " +"most cases Python programmers do not use this facility since it introduces " +"an unknown set of names into the interpreter, possibly hiding some things " +"you have already defined." +msgstr "" + +#: ../Doc/tutorial/modules.rst:111 +msgid "" +"Note that in general the practice of importing ``*`` from a module or " +"package is frowned upon, since it often causes poorly readable code. " +"However, it is okay to use it to save typing in interactive sessions." +msgstr "" + +#: ../Doc/tutorial/modules.rst:117 +msgid "" +"For efficiency reasons, each module is only imported once per interpreter " +"session. Therefore, if you change your modules, you must restart the " +"interpreter -- or, if it's just one module you want to test interactively, " +"use :func:`importlib.reload`, e.g. ``import importlib; importlib." +"reload(modulename)``." +msgstr "" + +#: ../Doc/tutorial/modules.rst:127 +msgid "Executing modules as scripts" +msgstr "" + +#: ../Doc/tutorial/modules.rst:129 +msgid "When you run a Python module with ::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:133 +msgid "" +"the code in the module will be executed, just as if you imported it, but " +"with the ``__name__`` set to ``\"__main__\"``. That means that by adding " +"this code at the end of your module::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:141 +msgid "" +"you can make the file usable as a script as well as an importable module, " +"because the code that parses the command line only runs if the module is " +"executed as the \"main\" file:" +msgstr "" + +#: ../Doc/tutorial/modules.rst:150 +msgid "If the module is imported, the code is not run::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:155 +msgid "" +"This is often used either to provide a convenient user interface to a " +"module, or for testing purposes (running the module as a script executes a " +"test suite)." +msgstr "" + +#: ../Doc/tutorial/modules.rst:162 +msgid "The Module Search Path" +msgstr "" + +#: ../Doc/tutorial/modules.rst:166 +msgid "" +"When a module named :mod:`spam` is imported, the interpreter first searches " +"for a built-in module with that name. If not found, it then searches for a " +"file named :file:`spam.py` in a list of directories given by the variable :" +"data:`sys.path`. :data:`sys.path` is initialized from these locations:" +msgstr "" + +#: ../Doc/tutorial/modules.rst:171 +msgid "" +"The directory containing the input script (or the current directory when no " +"file is specified)." +msgstr "" + +#: ../Doc/tutorial/modules.rst:173 +msgid "" +":envvar:`PYTHONPATH` (a list of directory names, with the same syntax as the " +"shell variable :envvar:`PATH`)." +msgstr "" + +#: ../Doc/tutorial/modules.rst:175 +msgid "The installation-dependent default." +msgstr "" + +#: ../Doc/tutorial/modules.rst:178 +msgid "" +"On file systems which support symlinks, the directory containing the input " +"script is calculated after the symlink is followed. In other words the " +"directory containing the symlink is **not** added to the module search path." +msgstr "" + +#: ../Doc/tutorial/modules.rst:182 +msgid "" +"After initialization, Python programs can modify :data:`sys.path`. The " +"directory containing the script being run is placed at the beginning of the " +"search path, ahead of the standard library path. This means that scripts in " +"that directory will be loaded instead of modules of the same name in the " +"library directory. This is an error unless the replacement is intended. See " +"section :ref:`tut-standardmodules` for more information." +msgstr "" + +#: ../Doc/tutorial/modules.rst:193 +msgid "\"Compiled\" Python files" +msgstr "" + +#: ../Doc/tutorial/modules.rst:195 +msgid "" +"To speed up loading modules, Python caches the compiled version of each " +"module in the ``__pycache__`` directory under the name :file:`module." +"{version}.pyc`, where the version encodes the format of the compiled file; " +"it generally contains the Python version number. For example, in CPython " +"release 3.3 the compiled version of spam.py would be cached as ``__pycache__/" +"spam.cpython-33.pyc``. This naming convention allows compiled modules from " +"different releases and different versions of Python to coexist." +msgstr "" + +#: ../Doc/tutorial/modules.rst:203 +msgid "" +"Python checks the modification date of the source against the compiled " +"version to see if it's out of date and needs to be recompiled. This is a " +"completely automatic process. Also, the compiled modules are platform-" +"independent, so the same library can be shared among systems with different " +"architectures." +msgstr "" + +#: ../Doc/tutorial/modules.rst:208 +msgid "" +"Python does not check the cache in two circumstances. First, it always " +"recompiles and does not store the result for the module that's loaded " +"directly from the command line. Second, it does not check the cache if " +"there is no source module. To support a non-source (compiled only) " +"distribution, the compiled module must be in the source directory, and there " +"must not be a source module." +msgstr "" + +#: ../Doc/tutorial/modules.rst:215 +msgid "Some tips for experts:" +msgstr "" + +#: ../Doc/tutorial/modules.rst:217 +msgid "" +"You can use the :option:`-O` or :option:`-OO` switches on the Python command " +"to reduce the size of a compiled module. The ``-O`` switch removes assert " +"statements, the ``-OO`` switch removes both assert statements and __doc__ " +"strings. Since some programs may rely on having these available, you should " +"only use this option if you know what you're doing. \"Optimized\" modules " +"have an ``opt-`` tag and are usually smaller. Future releases may change " +"the effects of optimization." +msgstr "" + +#: ../Doc/tutorial/modules.rst:225 +msgid "" +"A program doesn't run any faster when it is read from a ``.pyc`` file than " +"when it is read from a ``.py`` file; the only thing that's faster about ``." +"pyc`` files is the speed with which they are loaded." +msgstr "" + +#: ../Doc/tutorial/modules.rst:229 +msgid "" +"The module :mod:`compileall` can create .pyc files for all modules in a " +"directory." +msgstr "" + +#: ../Doc/tutorial/modules.rst:232 +msgid "" +"There is more detail on this process, including a flow chart of the " +"decisions, in PEP 3147." +msgstr "" + +#: ../Doc/tutorial/modules.rst:239 +msgid "Standard Modules" +msgstr "" + +#: ../Doc/tutorial/modules.rst:243 +msgid "" +"Python comes with a library of standard modules, described in a separate " +"document, the Python Library Reference (\"Library Reference\" hereafter). " +"Some modules are built into the interpreter; these provide access to " +"operations that are not part of the core of the language but are " +"nevertheless built in, either for efficiency or to provide access to " +"operating system primitives such as system calls. The set of such modules " +"is a configuration option which also depends on the underlying platform. " +"For example, the :mod:`winreg` module is only provided on Windows systems. " +"One particular module deserves some attention: :mod:`sys`, which is built " +"into every Python interpreter. The variables ``sys.ps1`` and ``sys.ps2`` " +"define the strings used as primary and secondary prompts::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:266 +msgid "" +"These two variables are only defined if the interpreter is in interactive " +"mode." +msgstr "" + +#: ../Doc/tutorial/modules.rst:268 +msgid "" +"The variable ``sys.path`` is a list of strings that determines the " +"interpreter's search path for modules. It is initialized to a default path " +"taken from the environment variable :envvar:`PYTHONPATH`, or from a built-in " +"default if :envvar:`PYTHONPATH` is not set. You can modify it using " +"standard list operations::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:281 +msgid "The :func:`dir` Function" +msgstr "" + +#: ../Doc/tutorial/modules.rst:283 +msgid "" +"The built-in function :func:`dir` is used to find out which names a module " +"defines. It returns a sorted list of strings::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:308 +msgid "" +"Without arguments, :func:`dir` lists the names you have defined currently::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:316 +msgid "" +"Note that it lists all types of names: variables, modules, functions, etc." +msgstr "" + +#: ../Doc/tutorial/modules.rst:320 +msgid "" +":func:`dir` does not list the names of built-in functions and variables. If " +"you want a list of those, they are defined in the standard module :mod:" +"`builtins`::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:359 +msgid "Packages" +msgstr "" + +#: ../Doc/tutorial/modules.rst:361 +msgid "" +"Packages are a way of structuring Python's module namespace by using " +"\"dotted module names\". For example, the module name :mod:`A.B` designates " +"a submodule named ``B`` in a package named ``A``. Just like the use of " +"modules saves the authors of different modules from having to worry about " +"each other's global variable names, the use of dotted module names saves the " +"authors of multi-module packages like NumPy or the Python Imaging Library " +"from having to worry about each other's module names." +msgstr "" + +#: ../Doc/tutorial/modules.rst:369 +msgid "" +"Suppose you want to design a collection of modules (a \"package\") for the " +"uniform handling of sound files and sound data. There are many different " +"sound file formats (usually recognized by their extension, for example: :" +"file:`.wav`, :file:`.aiff`, :file:`.au`), so you may need to create and " +"maintain a growing collection of modules for the conversion between the " +"various file formats. There are also many different operations you might " +"want to perform on sound data (such as mixing, adding echo, applying an " +"equalizer function, creating an artificial stereo effect), so in addition " +"you will be writing a never-ending stream of modules to perform these " +"operations. Here's a possible structure for your package (expressed in " +"terms of a hierarchical filesystem):" +msgstr "" + +#: ../Doc/tutorial/modules.rst:406 +msgid "" +"When importing the package, Python searches through the directories on ``sys." +"path`` looking for the package subdirectory." +msgstr "" + +#: ../Doc/tutorial/modules.rst:409 +msgid "" +"The :file:`__init__.py` files are required to make Python treat the " +"directories as containing packages; this is done to prevent directories with " +"a common name, such as ``string``, from unintentionally hiding valid modules " +"that occur later on the module search path. In the simplest case, :file:" +"`__init__.py` can just be an empty file, but it can also execute " +"initialization code for the package or set the ``__all__`` variable, " +"described later." +msgstr "" + +#: ../Doc/tutorial/modules.rst:416 +msgid "" +"Users of the package can import individual modules from the package, for " +"example::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:421 +msgid "" +"This loads the submodule :mod:`sound.effects.echo`. It must be referenced " +"with its full name. ::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:426 +msgid "An alternative way of importing the submodule is::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:430 +msgid "" +"This also loads the submodule :mod:`echo`, and makes it available without " +"its package prefix, so it can be used as follows::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:435 +msgid "" +"Yet another variation is to import the desired function or variable " +"directly::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:439 +msgid "" +"Again, this loads the submodule :mod:`echo`, but this makes its function :" +"func:`echofilter` directly available::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:444 +msgid "" +"Note that when using ``from package import item``, the item can be either a " +"submodule (or subpackage) of the package, or some other name defined in the " +"package, like a function, class or variable. The ``import`` statement first " +"tests whether the item is defined in the package; if not, it assumes it is a " +"module and attempts to load it. If it fails to find it, an :exc:" +"`ImportError` exception is raised." +msgstr "" + +#: ../Doc/tutorial/modules.rst:451 +msgid "" +"Contrarily, when using syntax like ``import item.subitem.subsubitem``, each " +"item except for the last must be a package; the last item can be a module or " +"a package but can't be a class or function or variable defined in the " +"previous item." +msgstr "" + +#: ../Doc/tutorial/modules.rst:460 +msgid "Importing \\* From a Package" +msgstr "" + +#: ../Doc/tutorial/modules.rst:464 +msgid "" +"Now what happens when the user writes ``from sound.effects import *``? " +"Ideally, one would hope that this somehow goes out to the filesystem, finds " +"which submodules are present in the package, and imports them all. This " +"could take a long time and importing sub-modules might have unwanted side-" +"effects that should only happen when the sub-module is explicitly imported." +msgstr "" + +#: ../Doc/tutorial/modules.rst:470 +msgid "" +"The only solution is for the package author to provide an explicit index of " +"the package. The :keyword:`import` statement uses the following convention: " +"if a package's :file:`__init__.py` code defines a list named ``__all__``, it " +"is taken to be the list of module names that should be imported when ``from " +"package import *`` is encountered. It is up to the package author to keep " +"this list up-to-date when a new version of the package is released. Package " +"authors may also decide not to support it, if they don't see a use for " +"importing \\* from their package. For example, the file :file:`sound/" +"effects/__init__.py` could contain the following code::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:482 +msgid "" +"This would mean that ``from sound.effects import *`` would import the three " +"named submodules of the :mod:`sound` package." +msgstr "" + +#: ../Doc/tutorial/modules.rst:485 +msgid "" +"If ``__all__`` is not defined, the statement ``from sound.effects import *`` " +"does *not* import all submodules from the package :mod:`sound.effects` into " +"the current namespace; it only ensures that the package :mod:`sound.effects` " +"has been imported (possibly running any initialization code in :file:" +"`__init__.py`) and then imports whatever names are defined in the package. " +"This includes any names defined (and submodules explicitly loaded) by :file:" +"`__init__.py`. It also includes any submodules of the package that were " +"explicitly loaded by previous :keyword:`import` statements. Consider this " +"code::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:498 +msgid "" +"In this example, the :mod:`echo` and :mod:`surround` modules are imported in " +"the current namespace because they are defined in the :mod:`sound.effects` " +"package when the ``from...import`` statement is executed. (This also works " +"when ``__all__`` is defined.)" +msgstr "" + +#: ../Doc/tutorial/modules.rst:503 +msgid "" +"Although certain modules are designed to export only names that follow " +"certain patterns when you use ``import *``, it is still considered bad " +"practise in production code." +msgstr "" + +#: ../Doc/tutorial/modules.rst:507 +msgid "" +"Remember, there is nothing wrong with using ``from Package import " +"specific_submodule``! In fact, this is the recommended notation unless the " +"importing module needs to use submodules with the same name from different " +"packages." +msgstr "" + +#: ../Doc/tutorial/modules.rst:514 +msgid "Intra-package References" +msgstr "" + +#: ../Doc/tutorial/modules.rst:516 +msgid "" +"When packages are structured into subpackages (as with the :mod:`sound` " +"package in the example), you can use absolute imports to refer to submodules " +"of siblings packages. For example, if the module :mod:`sound.filters." +"vocoder` needs to use the :mod:`echo` module in the :mod:`sound.effects` " +"package, it can use ``from sound.effects import echo``." +msgstr "" + +#: ../Doc/tutorial/modules.rst:522 +msgid "" +"You can also write relative imports, with the ``from module import name`` " +"form of import statement. These imports use leading dots to indicate the " +"current and parent packages involved in the relative import. From the :mod:" +"`surround` module for example, you might use::" +msgstr "" + +#: ../Doc/tutorial/modules.rst:531 +msgid "" +"Note that relative imports are based on the name of the current module. " +"Since the name of the main module is always ``\"__main__\"``, modules " +"intended for use as the main module of a Python application must always use " +"absolute imports." +msgstr "" + +#: ../Doc/tutorial/modules.rst:537 +msgid "Packages in Multiple Directories" +msgstr "" + +#: ../Doc/tutorial/modules.rst:539 +msgid "" +"Packages support one more special attribute, :attr:`__path__`. This is " +"initialized to be a list containing the name of the directory holding the " +"package's :file:`__init__.py` before the code in that file is executed. " +"This variable can be modified; doing so affects future searches for modules " +"and subpackages contained in the package." +msgstr "" + +#: ../Doc/tutorial/modules.rst:545 +msgid "" +"While this feature is not often needed, it can be used to extend the set of " +"modules found in a package." +msgstr "" + +#: ../Doc/tutorial/modules.rst:551 +msgid "" +"In fact function definitions are also 'statements' that are 'executed'; the " +"execution of a module-level function definition enters the function name in " +"the module's global symbol table." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:5 +msgid "Brief Tour of the Standard Library" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:11 +msgid "Operating System Interface" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:13 +msgid "" +"The :mod:`os` module provides dozens of functions for interacting with the " +"operating system::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:23 +msgid "" +"Be sure to use the ``import os`` style instead of ``from os import *``. " +"This will keep :func:`os.open` from shadowing the built-in :func:`open` " +"function which operates much differently." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:29 +msgid "" +"The built-in :func:`dir` and :func:`help` functions are useful as " +"interactive aids for working with large modules like :mod:`os`::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:38 +msgid "" +"For daily file and directory management tasks, the :mod:`shutil` module " +"provides a higher level interface that is easier to use::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:51 +msgid "File Wildcards" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:53 +msgid "" +"The :mod:`glob` module provides a function for making file lists from " +"directory wildcard searches::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:64 +msgid "Command Line Arguments" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:66 +msgid "" +"Common utility scripts often need to process command line arguments. These " +"arguments are stored in the :mod:`sys` module's *argv* attribute as a list. " +"For instance the following output results from running ``python demo.py one " +"two three`` at the command line::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:75 +msgid "" +"The :mod:`getopt` module processes *sys.argv* using the conventions of the " +"Unix :func:`getopt` function. More powerful and flexible command line " +"processing is provided by the :mod:`argparse` module." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:83 +msgid "Error Output Redirection and Program Termination" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:85 +msgid "" +"The :mod:`sys` module also has attributes for *stdin*, *stdout*, and " +"*stderr*. The latter is useful for emitting warnings and error messages to " +"make them visible even when *stdout* has been redirected::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:92 +msgid "The most direct way to terminate a script is to use ``sys.exit()``." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:98 +msgid "String Pattern Matching" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:100 +msgid "" +"The :mod:`re` module provides regular expression tools for advanced string " +"processing. For complex matching and manipulation, regular expressions offer " +"succinct, optimized solutions::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:110 +msgid "" +"When only simple capabilities are needed, string methods are preferred " +"because they are easier to read and debug::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:120 +msgid "Mathematics" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:122 +msgid "" +"The :mod:`math` module gives access to the underlying C library functions " +"for floating point math::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:131 +msgid "The :mod:`random` module provides tools for making random selections::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:143 +msgid "" +"The :mod:`statistics` module calculates basic statistical properties (the " +"mean, median, variance, etc.) of numeric data::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:155 +msgid "" +"The SciPy project has many other modules for numerical " +"computations." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:161 +msgid "Internet Access" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:163 +msgid "" +"There are a number of modules for accessing the internet and processing " +"internet protocols. Two of the simplest are :mod:`urllib.request` for " +"retrieving data from URLs and :mod:`smtplib` for sending mail::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:186 +msgid "(Note that the second example needs a mailserver running on localhost.)" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:192 +msgid "Dates and Times" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:194 +msgid "" +"The :mod:`datetime` module supplies classes for manipulating dates and times " +"in both simple and complex ways. While date and time arithmetic is " +"supported, the focus of the implementation is on efficient member extraction " +"for output formatting and manipulation. The module also supports objects " +"that are timezone aware. ::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:218 +msgid "Data Compression" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:220 +msgid "" +"Common data archiving and compression formats are directly supported by " +"modules including: :mod:`zlib`, :mod:`gzip`, :mod:`bz2`, :mod:`lzma`, :mod:" +"`zipfile` and :mod:`tarfile`. ::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:240 +msgid "Performance Measurement" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:242 +msgid "" +"Some Python users develop a deep interest in knowing the relative " +"performance of different approaches to the same problem. Python provides a " +"measurement tool that answers those questions immediately." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:246 +msgid "" +"For example, it may be tempting to use the tuple packing and unpacking " +"feature instead of the traditional approach to swapping arguments. The :mod:" +"`timeit` module quickly demonstrates a modest performance advantage::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:256 +msgid "" +"In contrast to :mod:`timeit`'s fine level of granularity, the :mod:`profile` " +"and :mod:`pstats` modules provide tools for identifying time critical " +"sections in larger blocks of code." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:264 +msgid "Quality Control" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:266 +msgid "" +"One approach for developing high quality software is to write tests for each " +"function as it is developed and to run those tests frequently during the " +"development process." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:270 +msgid "" +"The :mod:`doctest` module provides a tool for scanning a module and " +"validating tests embedded in a program's docstrings. Test construction is " +"as simple as cutting-and-pasting a typical call along with its results into " +"the docstring. This improves the documentation by providing the user with an " +"example and it allows the doctest module to make sure the code remains true " +"to the documentation::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:288 +msgid "" +"The :mod:`unittest` module is not as effortless as the :mod:`doctest` " +"module, but it allows a more comprehensive set of tests to be maintained in " +"a separate file::" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:310 +msgid "Batteries Included" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:312 +msgid "" +"Python has a \"batteries included\" philosophy. This is best seen through " +"the sophisticated and robust capabilities of its larger packages. For " +"example:" +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:315 +msgid "" +"The :mod:`xmlrpc.client` and :mod:`xmlrpc.server` modules make implementing " +"remote procedure calls into an almost trivial task. Despite the modules " +"names, no direct knowledge or handling of XML is needed." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:319 +msgid "" +"The :mod:`email` package is a library for managing email messages, including " +"MIME and other RFC 2822-based message documents. Unlike :mod:`smtplib` and :" +"mod:`poplib` which actually send and receive messages, the email package has " +"a complete toolset for building or decoding complex message structures " +"(including attachments) and for implementing internet encoding and header " +"protocols." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:326 +msgid "" +"The :mod:`json` package provides robust support for parsing this popular " +"data interchange format. The :mod:`csv` module supports direct reading and " +"writing of files in Comma-Separated Value format, commonly supported by " +"databases and spreadsheets. XML processing is supported by the :mod:`xml." +"etree.ElementTree`, :mod:`xml.dom` and :mod:`xml.sax` packages. Together, " +"these modules and packages greatly simplify data interchange between Python " +"applications and other tools." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:335 +msgid "" +"The :mod:`sqlite3` module is a wrapper for the SQLite database library, " +"providing a persistent database that can be updated and accessed using " +"slightly nonstandard SQL syntax." +msgstr "" + +#: ../Doc/tutorial/stdlib.rst:339 +msgid "" +"Internationalization is supported by a number of modules including :mod:" +"`gettext`, :mod:`locale`, and the :mod:`codecs` package." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:5 +msgid "Brief Tour of the Standard Library -- Part II" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:7 +msgid "" +"This second tour covers more advanced modules that support professional " +"programming needs. These modules rarely occur in small scripts." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:14 +msgid "Output Formatting" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:16 +msgid "" +"The :mod:`reprlib` module provides a version of :func:`repr` customized for " +"abbreviated displays of large or deeply nested containers::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:23 +msgid "" +"The :mod:`pprint` module offers more sophisticated control over printing " +"both built-in and user defined objects in a way that is readable by the " +"interpreter. When the result is longer than one line, the \"pretty printer\" " +"adds line breaks and indentation to more clearly reveal data structure::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:39 +msgid "" +"The :mod:`textwrap` module formats paragraphs of text to fit a given screen " +"width::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:53 +msgid "" +"The :mod:`locale` module accesses a database of culture specific data " +"formats. The grouping attribute of locale's format function provides a " +"direct way of formatting numbers with group separators::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:72 +msgid "Templating" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:74 +msgid "" +"The :mod:`string` module includes a versatile :class:`~string.Template` " +"class with a simplified syntax suitable for editing by end-users. This " +"allows users to customize their applications without having to alter the " +"application." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:78 +msgid "" +"The format uses placeholder names formed by ``$`` with valid Python " +"identifiers (alphanumeric characters and underscores). Surrounding the " +"placeholder with braces allows it to be followed by more alphanumeric " +"letters with no intervening spaces. Writing ``$$`` creates a single escaped " +"``$``::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:88 +msgid "" +"The :meth:`~string.Template.substitute` method raises a :exc:`KeyError` when " +"a placeholder is not supplied in a dictionary or a keyword argument. For " +"mail-merge style applications, user supplied data may be incomplete and the :" +"meth:`~string.Template.safe_substitute` method may be more appropriate --- " +"it will leave placeholders unchanged if data is missing::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:103 +msgid "" +"Template subclasses can specify a custom delimiter. For example, a batch " +"renaming utility for a photo browser may elect to use percent signs for " +"placeholders such as the current date, image sequence number, or file " +"format::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:125 +msgid "" +"Another application for templating is separating program logic from the " +"details of multiple output formats. This makes it possible to substitute " +"custom templates for XML files, plain text reports, and HTML web reports." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:133 +msgid "Working with Binary Data Record Layouts" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:135 +msgid "" +"The :mod:`struct` module provides :func:`~struct.pack` and :func:`~struct." +"unpack` functions for working with variable length binary record formats. " +"The following example shows how to loop through header information in a ZIP " +"file without using the :mod:`zipfile` module. Pack codes ``\"H\"`` and ``\"I" +"\"`` represent two and four byte unsigned numbers respectively. The ``\"<" +"\"`` indicates that they are standard size and in little-endian byte order::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:166 +msgid "Multi-threading" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:168 +msgid "" +"Threading is a technique for decoupling tasks which are not sequentially " +"dependent. Threads can be used to improve the responsiveness of " +"applications that accept user input while other tasks run in the " +"background. A related use case is running I/O in parallel with computations " +"in another thread." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:173 +msgid "" +"The following code shows how the high level :mod:`threading` module can run " +"tasks in background while the main program continues to run::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:197 +msgid "" +"The principal challenge of multi-threaded applications is coordinating " +"threads that share data or other resources. To that end, the threading " +"module provides a number of synchronization primitives including locks, " +"events, condition variables, and semaphores." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:202 +msgid "" +"While those tools are powerful, minor design errors can result in problems " +"that are difficult to reproduce. So, the preferred approach to task " +"coordination is to concentrate all access to a resource in a single thread " +"and then use the :mod:`queue` module to feed that thread with requests from " +"other threads. Applications using :class:`~queue.Queue` objects for inter-" +"thread communication and coordination are easier to design, more readable, " +"and more reliable." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:213 +msgid "Logging" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:215 +msgid "" +"The :mod:`logging` module offers a full featured and flexible logging " +"system. At its simplest, log messages are sent to a file or to ``sys." +"stderr``::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:225 +msgid "This produces the following output:" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:233 +msgid "" +"By default, informational and debugging messages are suppressed and the " +"output is sent to standard error. Other output options include routing " +"messages through email, datagrams, sockets, or to an HTTP Server. New " +"filters can select different routing based on message priority: :const:" +"`~logging.DEBUG`, :const:`~logging.INFO`, :const:`~logging.WARNING`, :const:" +"`~logging.ERROR`, and :const:`~logging.CRITICAL`." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:240 +msgid "" +"The logging system can be configured directly from Python or can be loaded " +"from a user editable configuration file for customized logging without " +"altering the application." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:248 +msgid "Weak References" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:250 +msgid "" +"Python does automatic memory management (reference counting for most objects " +"and :term:`garbage collection` to eliminate cycles). The memory is freed " +"shortly after the last reference to it has been eliminated." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:254 +msgid "" +"This approach works fine for most applications but occasionally there is a " +"need to track objects only as long as they are being used by something else. " +"Unfortunately, just tracking them creates a reference that makes them " +"permanent. The :mod:`weakref` module provides tools for tracking objects " +"without creating a reference. When the object is no longer needed, it is " +"automatically removed from a weakref table and a callback is triggered for " +"weakref objects. Typical applications include caching objects that are " +"expensive to create::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:289 +msgid "Tools for Working with Lists" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:291 +msgid "" +"Many data structure needs can be met with the built-in list type. However, " +"sometimes there is a need for alternative implementations with different " +"performance trade-offs." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:295 +msgid "" +"The :mod:`array` module provides an :class:`~array.array()` object that is " +"like a list that stores only homogeneous data and stores it more compactly. " +"The following example shows an array of numbers stored as two byte unsigned " +"binary numbers (typecode ``\"H\"``) rather than the usual 16 bytes per entry " +"for regular lists of Python int objects::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:308 +msgid "" +"The :mod:`collections` module provides a :class:`~collections.deque()` " +"object that is like a list with faster appends and pops from the left side " +"but slower lookups in the middle. These objects are well suited for " +"implementing queues and breadth first tree searches::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:329 +msgid "" +"In addition to alternative list implementations, the library also offers " +"other tools such as the :mod:`bisect` module with functions for manipulating " +"sorted lists::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:339 +msgid "" +"The :mod:`heapq` module provides functions for implementing heaps based on " +"regular lists. The lowest valued entry is always kept at position zero. " +"This is useful for applications which repeatedly access the smallest element " +"but do not want to run a full list sort::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:355 +msgid "Decimal Floating Point Arithmetic" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:357 +msgid "" +"The :mod:`decimal` module offers a :class:`~decimal.Decimal` datatype for " +"decimal floating point arithmetic. Compared to the built-in :class:`float` " +"implementation of binary floating point, the class is especially helpful for" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:361 +msgid "" +"financial applications and other uses which require exact decimal " +"representation," +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:363 +msgid "control over precision," +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:364 +msgid "control over rounding to meet legal or regulatory requirements," +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:365 +msgid "tracking of significant decimal places, or" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:366 +msgid "" +"applications where the user expects the results to match calculations done " +"by hand." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:369 +msgid "" +"For example, calculating a 5% tax on a 70 cent phone charge gives different " +"results in decimal floating point and binary floating point. The difference " +"becomes significant if the results are rounded to the nearest cent::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:379 +msgid "" +"The :class:`~decimal.Decimal` result keeps a trailing zero, automatically " +"inferring four place significance from multiplicands with two place " +"significance. Decimal reproduces mathematics as done by hand and avoids " +"issues that can arise when binary floating point cannot exactly represent " +"decimal quantities." +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:385 +msgid "" +"Exact representation enables the :class:`~decimal.Decimal` class to perform " +"modulo calculations and equality tests that are unsuitable for binary " +"floating point::" +msgstr "" + +#: ../Doc/tutorial/stdlib2.rst:399 +msgid "" +"The :mod:`decimal` module provides arithmetic with as much precision as " +"needed::" +msgstr "" + +#: ../Doc/tutorial/venv.rst:6 +msgid "Virtual Environments and Packages" +msgstr "" + +#: ../Doc/tutorial/venv.rst:9 +msgid "Introduction" +msgstr "" + +#: ../Doc/tutorial/venv.rst:11 +msgid "" +"Python applications will often use packages and modules that don't come as " +"part of the standard library. Applications will sometimes need a specific " +"version of a library, because the application may require that a particular " +"bug has been fixed or the application may be written using an obsolete " +"version of the library's interface." +msgstr "" + +#: ../Doc/tutorial/venv.rst:17 +msgid "" +"This means it may not be possible for one Python installation to meet the " +"requirements of every application. If application A needs version 1.0 of a " +"particular module but application B needs version 2.0, then the requirements " +"are in conflict and installing either version 1.0 or 2.0 will leave one " +"application unable to run." +msgstr "" + +#: ../Doc/tutorial/venv.rst:23 +msgid "" +"The solution for this problem is to create a :term:`virtual environment`, a " +"self-contained directory tree that contains a Python installation for a " +"particular version of Python, plus a number of additional packages." +msgstr "" + +#: ../Doc/tutorial/venv.rst:27 +msgid "" +"Different applications can then use different virtual environments. To " +"resolve the earlier example of conflicting requirements, application A can " +"have its own virtual environment with version 1.0 installed while " +"application B has another virtual environment with version 2.0. If " +"application B requires a library be upgraded to version 3.0, this will not " +"affect application A's environment." +msgstr "" + +#: ../Doc/tutorial/venv.rst:36 +msgid "Creating Virtual Environments" +msgstr "" + +#: ../Doc/tutorial/venv.rst:38 +msgid "" +"The module used to create and manage virtual environments is called :mod:" +"`venv`. :mod:`venv` will usually install the most recent version of Python " +"that you have available. If you have multiple versions of Python on your " +"system, you can select a specific Python version by running ``python3`` or " +"whichever version you want." +msgstr "" + +#: ../Doc/tutorial/venv.rst:44 +msgid "" +"To create a virtual environment, decide upon a directory where you want to " +"place it, and run the :mod:`venv` module as a script with the directory " +"path::" +msgstr "" + +#: ../Doc/tutorial/venv.rst:49 +msgid "" +"This will create the ``tutorial-env`` directory if it doesn't exist, and " +"also create directories inside it containing a copy of the Python " +"interpreter, the standard library, and various supporting files." +msgstr "" + +#: ../Doc/tutorial/venv.rst:53 +msgid "Once you've created a virtual environment, you may activate it." +msgstr "" + +#: ../Doc/tutorial/venv.rst:55 +msgid "On Windows, run::" +msgstr "" + +#: ../Doc/tutorial/venv.rst:59 +msgid "On Unix or MacOS, run::" +msgstr "" + +#: ../Doc/tutorial/venv.rst:63 +msgid "" +"(This script is written for the bash shell. If you use the :program:`csh` " +"or :program:`fish` shells, there are alternate ``activate.csh`` and " +"``activate.fish`` scripts you should use instead.)" +msgstr "" + +#: ../Doc/tutorial/venv.rst:68 +msgid "" +"Activating the virtual environment will change your shell's prompt to show " +"what virtual environment you're using, and modify the environment so that " +"running ``python`` will get you that particular version and installation of " +"Python. For example:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:87 +msgid "Managing Packages with pip" +msgstr "" + +#: ../Doc/tutorial/venv.rst:89 +msgid "" +"You can install, upgrade, and remove packages using a program called :" +"program:`pip`. By default ``pip`` will install packages from the Python " +"Package Index, . You can browse the Python " +"Package Index by going to it in your web browser, or you can use ``pip``'s " +"limited search feature:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:105 +msgid "" +"``pip`` has a number of subcommands: \"search\", \"install\", \"uninstall\", " +"\"freeze\", etc. (Consult the :ref:`installing-index` guide for complete " +"documentation for ``pip``.)" +msgstr "" + +#: ../Doc/tutorial/venv.rst:109 +msgid "" +"You can install the latest version of a package by specifying a package's " +"name:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:120 +msgid "" +"You can also install a specific version of a package by giving the package " +"name followed by ``==`` and the version number:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:131 +msgid "" +"If you re-run this command, ``pip`` will notice that the requested version " +"is already installed and do nothing. You can supply a different version " +"number to get that version, or you can run ``pip install --upgrade`` to " +"upgrade the package to the latest version:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:146 +msgid "" +"``pip uninstall`` followed by one or more package names will remove the " +"packages from the virtual environment." +msgstr "" + +#: ../Doc/tutorial/venv.rst:149 +msgid "``pip show`` will display information about a particular package:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:166 +msgid "" +"``pip list`` will display all of the packages installed in the virtual " +"environment:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:178 +msgid "" +"``pip freeze`` will produce a similar list of the installed packages, but " +"the output uses the format that ``pip install`` expects. A common convention " +"is to put this list in a ``requirements.txt`` file:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:190 +msgid "" +"The ``requirements.txt`` can then be committed to version control and " +"shipped as part of an application. Users can then install all the necessary " +"packages with ``install -r``:" +msgstr "" + +#: ../Doc/tutorial/venv.rst:207 +msgid "" +"``pip`` has many more options. Consult the :ref:`installing-index` guide " +"for complete documentation for ``pip``. When you've written a package and " +"want to make it available on the Python Package Index, consult the :ref:" +"`distributing-index` guide." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:5 +msgid "What Now?" +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:7 +msgid "" +"Reading this tutorial has probably reinforced your interest in using Python " +"--- you should be eager to apply Python to solving your real-world problems. " +"Where should you go to learn more?" +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:11 +msgid "" +"This tutorial is part of Python's documentation set. Some other documents " +"in the set are:" +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:14 +msgid ":ref:`library-index`:" +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:16 +msgid "" +"You should browse through this manual, which gives complete (though terse) " +"reference material about types, functions, and the modules in the standard " +"library. The standard Python distribution includes a *lot* of additional " +"code. There are modules to read Unix mailboxes, retrieve documents via HTTP, " +"generate random numbers, parse command-line options, write CGI programs, " +"compress data, and many other tasks. Skimming through the Library Reference " +"will give you an idea of what's available." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:24 +msgid "" +":ref:`installing-index` explains how to install additional modules written " +"by other Python users." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:27 +msgid "" +":ref:`reference-index`: A detailed explanation of Python's syntax and " +"semantics. It's heavy reading, but is useful as a complete guide to the " +"language itself." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:31 +msgid "More Python resources:" +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:33 +msgid "" +"https://www.python.org: The major Python Web site. It contains code, " +"documentation, and pointers to Python-related pages around the Web. This " +"Web site is mirrored in various places around the world, such as Europe, " +"Japan, and Australia; a mirror may be faster than the main site, depending " +"on your geographical location." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:39 +msgid "https://docs.python.org: Fast access to Python's documentation." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:41 +msgid "" +"https://pypi.python.org/pypi: The Python Package Index, previously also " +"nicknamed the Cheese Shop, is an index of user-created Python modules that " +"are available for download. Once you begin releasing code, you can register " +"it here so that others can find it." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:46 +msgid "" +"https://code.activestate.com/recipes/langs/python/: The Python Cookbook is a " +"sizable collection of code examples, larger modules, and useful scripts. " +"Particularly notable contributions are collected in a book also titled " +"Python Cookbook (O'Reilly & Associates, ISBN 0-596-00797-3.)" +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:51 +msgid "" +"http://www.pyvideo.org collects links to Python-related videos from " +"conferences and user-group meetings." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:54 +msgid "" +"https://scipy.org: The Scientific Python project includes modules for fast " +"array computations and manipulations plus a host of packages for such things " +"as linear algebra, Fourier transforms, non-linear solvers, random number " +"distributions, statistical analysis and the like." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:59 +msgid "" +"For Python-related questions and problem reports, you can post to the " +"newsgroup :newsgroup:`comp.lang.python`, or send them to the mailing list at " +"python-list@python.org. The newsgroup and mailing list are gatewayed, so " +"messages posted to one will automatically be forwarded to the other. There " +"are hundreds of postings a day, asking (and answering) questions, suggesting " +"new features, and announcing new modules. Mailing list archives are " +"available at https://mail.python.org/pipermail/." +msgstr "" + +#: ../Doc/tutorial/whatnow.rst:67 +msgid "" +"Before posting, be sure to check the list of :ref:`Frequently Asked " +"Questions ` (also called the FAQ). The FAQ answers many of the " +"questions that come up again and again, and may already contain the solution " +"for your problem." +msgstr "" diff --git a/using.po b/using.po new file mode 100644 index 00000000..af9d02fb --- /dev/null +++ b/using.po @@ -0,0 +1,3098 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/using/cmdline.rst:9 +msgid "Command line and environment" +msgstr "" + +#: ../Doc/using/cmdline.rst:11 +msgid "" +"The CPython interpreter scans the command line and the environment for " +"various settings." +msgstr "" + +#: ../Doc/using/cmdline.rst:16 +msgid "" +"Other implementations' command line schemes may differ. See :ref:" +"`implementations` for further resources." +msgstr "" + +#: ../Doc/using/cmdline.rst:23 +msgid "Command line" +msgstr "" + +#: ../Doc/using/cmdline.rst:25 +msgid "When invoking Python, you may specify any of these options::" +msgstr "" + +#: ../Doc/using/cmdline.rst:29 +msgid "" +"The most common use case is, of course, a simple invocation of a script::" +msgstr "" + +#: ../Doc/using/cmdline.rst:37 +msgid "Interface options" +msgstr "" + +#: ../Doc/using/cmdline.rst:39 +msgid "" +"The interpreter interface resembles that of the UNIX shell, but provides " +"some additional methods of invocation:" +msgstr "" + +#: ../Doc/using/cmdline.rst:42 +msgid "" +"When called with standard input connected to a tty device, it prompts for " +"commands and executes them until an EOF (an end-of-file character, you can " +"produce that with :kbd:`Ctrl-D` on UNIX or :kbd:`Ctrl-Z, Enter` on Windows) " +"is read." +msgstr "" + +#: ../Doc/using/cmdline.rst:45 +msgid "" +"When called with a file name argument or with a file as standard input, it " +"reads and executes a script from that file." +msgstr "" + +#: ../Doc/using/cmdline.rst:47 +msgid "" +"When called with a directory name argument, it reads and executes an " +"appropriately named script from that directory." +msgstr "" + +#: ../Doc/using/cmdline.rst:49 +msgid "" +"When called with ``-c command``, it executes the Python statement(s) given " +"as *command*. Here *command* may contain multiple statements separated by " +"newlines. Leading whitespace is significant in Python statements!" +msgstr "" + +#: ../Doc/using/cmdline.rst:52 +msgid "" +"When called with ``-m module-name``, the given module is located on the " +"Python module path and executed as a script." +msgstr "" + +#: ../Doc/using/cmdline.rst:55 +msgid "" +"In non-interactive mode, the entire input is parsed before it is executed." +msgstr "" + +#: ../Doc/using/cmdline.rst:57 +msgid "" +"An interface option terminates the list of options consumed by the " +"interpreter, all consecutive arguments will end up in :data:`sys.argv` -- " +"note that the first element, subscript zero (``sys.argv[0]``), is a string " +"reflecting the program's source." +msgstr "" + +#: ../Doc/using/cmdline.rst:64 +msgid "" +"Execute the Python code in *command*. *command* can be one or more " +"statements separated by newlines, with significant leading whitespace as in " +"normal module code." +msgstr "" + +#: ../Doc/using/cmdline.rst:68 +msgid "" +"If this option is given, the first element of :data:`sys.argv` will be ``\"-c" +"\"`` and the current directory will be added to the start of :data:`sys." +"path` (allowing modules in that directory to be imported as top level " +"modules)." +msgstr "" + +#: ../Doc/using/cmdline.rst:76 +msgid "" +"Search :data:`sys.path` for the named module and execute its contents as " +"the :mod:`__main__` module." +msgstr "" + +#: ../Doc/using/cmdline.rst:79 +msgid "" +"Since the argument is a *module* name, you must not give a file extension " +"(``.py``). The module name should be a valid absolute Python module name, " +"but the implementation may not always enforce this (e.g. it may allow you to " +"use a name that includes a hyphen)." +msgstr "" + +#: ../Doc/using/cmdline.rst:84 +msgid "" +"Package names (including namespace packages) are also permitted. When a " +"package name is supplied instead of a normal module, the interpreter will " +"execute ``.__main__`` as the main module. This behaviour is " +"deliberately similar to the handling of directories and zipfiles that are " +"passed to the interpreter as the script argument." +msgstr "" + +#: ../Doc/using/cmdline.rst:93 +msgid "" +"This option cannot be used with built-in modules and extension modules " +"written in C, since they do not have Python module files. However, it can " +"still be used for precompiled modules, even if the original source file is " +"not available." +msgstr "" + +#: ../Doc/using/cmdline.rst:98 +msgid "" +"If this option is given, the first element of :data:`sys.argv` will be the " +"full path to the module file (while the module file is being located, the " +"first element will be set to ``\"-m\"``). As with the :option:`-c` option, " +"the current directory will be added to the start of :data:`sys.path`." +msgstr "" + +#: ../Doc/using/cmdline.rst:103 +msgid "" +"Many standard library modules contain code that is invoked on their " +"execution as a script. An example is the :mod:`timeit` module::" +msgstr "" + +#: ../Doc/using/cmdline.rst:111 +msgid ":func:`runpy.run_module`" +msgstr "" + +#: ../Doc/using/cmdline.rst:111 ../Doc/using/cmdline.rst:153 +msgid "Equivalent functionality directly available to Python code" +msgstr "" + +#: ../Doc/using/cmdline.rst:113 +msgid ":pep:`338` -- Executing modules as scripts" +msgstr "" + +#: ../Doc/using/cmdline.rst:116 +msgid "Supply the package name to run a ``__main__`` submodule." +msgstr "" + +#: ../Doc/using/cmdline.rst:119 +msgid "namespace packages are also supported" +msgstr "" + +#: ../Doc/using/cmdline.rst:125 +msgid "" +"Read commands from standard input (:data:`sys.stdin`). If standard input is " +"a terminal, :option:`-i` is implied." +msgstr "" + +#: ../Doc/using/cmdline.rst:128 +msgid "" +"If this option is given, the first element of :data:`sys.argv` will be ``\"-" +"\"`` and the current directory will be added to the start of :data:`sys." +"path`." +msgstr "" + +#: ../Doc/using/cmdline.rst:135 +msgid "" +"Execute the Python code contained in *script*, which must be a filesystem " +"path (absolute or relative) referring to either a Python file, a directory " +"containing a ``__main__.py`` file, or a zipfile containing a ``__main__.py`` " +"file." +msgstr "" + +#: ../Doc/using/cmdline.rst:140 +msgid "" +"If this option is given, the first element of :data:`sys.argv` will be the " +"script name as given on the command line." +msgstr "" + +#: ../Doc/using/cmdline.rst:143 +msgid "" +"If the script name refers directly to a Python file, the directory " +"containing that file is added to the start of :data:`sys.path`, and the file " +"is executed as the :mod:`__main__` module." +msgstr "" + +#: ../Doc/using/cmdline.rst:147 +msgid "" +"If the script name refers to a directory or zipfile, the script name is " +"added to the start of :data:`sys.path` and the ``__main__.py`` file in that " +"location is executed as the :mod:`__main__` module." +msgstr "" + +#: ../Doc/using/cmdline.rst:152 +msgid ":func:`runpy.run_path`" +msgstr "" + +#: ../Doc/using/cmdline.rst:156 +msgid "" +"If no interface option is given, :option:`-i` is implied, ``sys.argv[0]`` is " +"an empty string (``\"\"``) and the current directory will be added to the " +"start of :data:`sys.path`. Also, tab-completion and history editing is " +"automatically enabled, if available on your platform (see :ref:`rlcompleter-" +"config`)." +msgstr "" + +#: ../Doc/using/cmdline.rst:162 +msgid ":ref:`tut-invoking`" +msgstr "" + +#: ../Doc/using/cmdline.rst:164 +msgid "Automatic enabling of tab-completion and history editing." +msgstr "" + +#: ../Doc/using/cmdline.rst:169 +msgid "Generic options" +msgstr "" + +#: ../Doc/using/cmdline.rst:175 +msgid "Print a short description of all command line options." +msgstr "" + +#: ../Doc/using/cmdline.rst:181 +msgid "Print the Python version number and exit. Example output could be::" +msgstr "" + +#: ../Doc/using/cmdline.rst:189 +msgid "Miscellaneous options" +msgstr "" + +#: ../Doc/using/cmdline.rst:193 +msgid "" +"Issue a warning when comparing :class:`bytes` or :class:`bytearray` with :" +"class:`str` or :class:`bytes` with :class:`int`. Issue an error when the " +"option is given twice (:option:`-bb`)." +msgstr "" + +#: ../Doc/using/cmdline.rst:197 +msgid "Affects comparisons of :class:`bytes` with :class:`int`." +msgstr "" + +#: ../Doc/using/cmdline.rst:202 +msgid "" +"If given, Python won't try to write ``.pyc`` files on the import of source " +"modules. See also :envvar:`PYTHONDONTWRITEBYTECODE`." +msgstr "" + +#: ../Doc/using/cmdline.rst:208 +msgid "" +"Turn on parser debugging output (for wizards only, depending on compilation " +"options). See also :envvar:`PYTHONDEBUG`." +msgstr "" + +#: ../Doc/using/cmdline.rst:214 +msgid "" +"Ignore all :envvar:`PYTHON*` environment variables, e.g. :envvar:" +"`PYTHONPATH` and :envvar:`PYTHONHOME`, that might be set." +msgstr "" + +#: ../Doc/using/cmdline.rst:220 +msgid "" +"When a script is passed as first argument or the :option:`-c` option is " +"used, enter interactive mode after executing the script or the command, even " +"when :data:`sys.stdin` does not appear to be a terminal. The :envvar:" +"`PYTHONSTARTUP` file is not read." +msgstr "" + +#: ../Doc/using/cmdline.rst:225 +msgid "" +"This can be useful to inspect global variables or a stack trace when a " +"script raises an exception. See also :envvar:`PYTHONINSPECT`." +msgstr "" + +#: ../Doc/using/cmdline.rst:231 +msgid "" +"Run Python in isolated mode. This also implies -E and -s. In isolated mode :" +"data:`sys.path` contains neither the script's directory nor the user's site-" +"packages directory. All :envvar:`PYTHON*` environment variables are ignored, " +"too. Further restrictions may be imposed to prevent the user from injecting " +"malicious code." +msgstr "" + +#: ../Doc/using/cmdline.rst:242 +msgid "Turn on basic optimizations. See also :envvar:`PYTHONOPTIMIZE`." +msgstr "" + +#: ../Doc/using/cmdline.rst:247 +msgid "Discard docstrings in addition to the :option:`-O` optimizations." +msgstr "" + +#: ../Doc/using/cmdline.rst:252 +msgid "" +"Don't display the copyright and version messages even in interactive mode." +msgstr "" + +#: ../Doc/using/cmdline.rst:259 +msgid "" +"Kept for compatibility. On Python 3.3 and greater, hash randomization is " +"turned on by default." +msgstr "" + +#: ../Doc/using/cmdline.rst:262 +msgid "" +"On previous versions of Python, this option turns on hash randomization, so " +"that the :meth:`__hash__` values of str, bytes and datetime are \"salted\" " +"with an unpredictable random value. Although they remain constant within an " +"individual Python process, they are not predictable between repeated " +"invocations of Python." +msgstr "" + +#: ../Doc/using/cmdline.rst:268 +msgid "" +"Hash randomization is intended to provide protection against a denial-of-" +"service caused by carefully-chosen inputs that exploit the worst case " +"performance of a dict construction, O(n^2) complexity. See http://www.ocert." +"org/advisories/ocert-2011-003.html for details." +msgstr "" + +#: ../Doc/using/cmdline.rst:273 +msgid "" +":envvar:`PYTHONHASHSEED` allows you to set a fixed value for the hash seed " +"secret." +msgstr "" + +#: ../Doc/using/cmdline.rst:281 +msgid "" +"Don't add the :data:`user site-packages directory ` to :data:" +"`sys.path`." +msgstr "" + +#: ../Doc/using/cmdline.rst:286 ../Doc/using/cmdline.rst:574 +#: ../Doc/using/cmdline.rst:586 +msgid ":pep:`370` -- Per user site-packages directory" +msgstr "" + +#: ../Doc/using/cmdline.rst:291 +msgid "" +"Disable the import of the module :mod:`site` and the site-dependent " +"manipulations of :data:`sys.path` that it entails. Also disable these " +"manipulations if :mod:`site` is explicitly imported later (call :func:`site." +"main` if you want them to be triggered)." +msgstr "" + +#: ../Doc/using/cmdline.rst:299 +msgid "" +"Force the binary layer of the stdout and stderr streams (which is available " +"as their ``buffer`` attribute) to be unbuffered. The text I/O layer will " +"still be line-buffered if writing to the console, or block-buffered if " +"redirected to a non-interactive file." +msgstr "" + +#: ../Doc/using/cmdline.rst:304 +msgid "See also :envvar:`PYTHONUNBUFFERED`." +msgstr "" + +#: ../Doc/using/cmdline.rst:309 +msgid "" +"Print a message each time a module is initialized, showing the place " +"(filename or built-in module) from which it is loaded. When given twice (:" +"option:`-vv`), print a message for each file that is checked for when " +"searching for a module. Also provides information on module cleanup at " +"exit. See also :envvar:`PYTHONVERBOSE`." +msgstr "" + +#: ../Doc/using/cmdline.rst:318 +msgid "" +"Warning control. Python's warning machinery by default prints warning " +"messages to :data:`sys.stderr`. A typical warning message has the following " +"form::" +msgstr "" + +#: ../Doc/using/cmdline.rst:324 +msgid "" +"By default, each warning is printed once for each source line where it " +"occurs. This option controls how often warnings are printed." +msgstr "" + +#: ../Doc/using/cmdline.rst:327 +msgid "" +"Multiple :option:`-W` options may be given; when a warning matches more than " +"one option, the action for the last matching option is performed. Invalid :" +"option:`-W` options are ignored (though, a warning message is printed about " +"invalid options when the first warning is issued)." +msgstr "" + +#: ../Doc/using/cmdline.rst:332 +msgid "" +"Warnings can also be controlled from within a Python program using the :mod:" +"`warnings` module." +msgstr "" + +#: ../Doc/using/cmdline.rst:335 +msgid "" +"The simplest form of argument is one of the following action strings (or a " +"unique abbreviation):" +msgstr "" + +#: ../Doc/using/cmdline.rst:338 +msgid "``ignore``" +msgstr "" + +#: ../Doc/using/cmdline.rst:339 +msgid "Ignore all warnings." +msgstr "" + +#: ../Doc/using/cmdline.rst:341 +msgid "``default``" +msgstr "" + +#: ../Doc/using/cmdline.rst:341 +msgid "" +"Explicitly request the default behavior (printing each warning once per " +"source line)." +msgstr "" + +#: ../Doc/using/cmdline.rst:345 +msgid "``all``" +msgstr "" + +#: ../Doc/using/cmdline.rst:344 +msgid "" +"Print a warning each time it occurs (this may generate many messages if a " +"warning is triggered repeatedly for the same source line, such as inside a " +"loop)." +msgstr "" + +#: ../Doc/using/cmdline.rst:347 +msgid "``module``" +msgstr "" + +#: ../Doc/using/cmdline.rst:348 +msgid "Print each warning only the first time it occurs in each module." +msgstr "" + +#: ../Doc/using/cmdline.rst:349 +msgid "``once``" +msgstr "" + +#: ../Doc/using/cmdline.rst:350 +msgid "Print each warning only the first time it occurs in the program." +msgstr "" + +#: ../Doc/using/cmdline.rst:352 +msgid "``error``" +msgstr "" + +#: ../Doc/using/cmdline.rst:352 +msgid "Raise an exception instead of printing a warning message." +msgstr "" + +#: ../Doc/using/cmdline.rst:354 +msgid "The full form of argument is::" +msgstr "" + +#: ../Doc/using/cmdline.rst:358 +msgid "" +"Here, *action* is as explained above but only applies to messages that match " +"the remaining fields. Empty fields match all values; trailing empty fields " +"may be omitted. The *message* field matches the start of the warning " +"message printed; this match is case-insensitive. The *category* field " +"matches the warning category. This must be a class name; the match tests " +"whether the actual warning category of the message is a subclass of the " +"specified warning category. The full class name must be given. The " +"*module* field matches the (fully-qualified) module name; this match is case-" +"sensitive. The *line* field matches the line number, where zero matches all " +"line numbers and is thus equivalent to an omitted line number." +msgstr "" + +#: ../Doc/using/cmdline.rst:370 +msgid ":mod:`warnings` -- the warnings module" +msgstr "" + +#: ../Doc/using/cmdline.rst:372 +msgid ":pep:`230` -- Warning framework" +msgstr "" + +#: ../Doc/using/cmdline.rst:374 +msgid ":envvar:`PYTHONWARNINGS`" +msgstr "" + +#: ../Doc/using/cmdline.rst:379 +msgid "" +"Skip the first line of the source, allowing use of non-Unix forms of ``#!" +"cmd``. This is intended for a DOS specific hack only." +msgstr "" + +#: ../Doc/using/cmdline.rst:382 +msgid "The line numbers in error messages will be off by one." +msgstr "" + +#: ../Doc/using/cmdline.rst:387 +msgid "" +"Reserved for various implementation-specific options. CPython currently " +"defines the following possible values:" +msgstr "" + +#: ../Doc/using/cmdline.rst:390 +msgid "``-X faulthandler`` to enable :mod:`faulthandler`;" +msgstr "" + +#: ../Doc/using/cmdline.rst:391 +msgid "" +"``-X showrefcount`` to enable the output of the total reference count and " +"memory blocks (only works on debug builds);" +msgstr "" + +#: ../Doc/using/cmdline.rst:393 +msgid "" +"``-X tracemalloc`` to start tracing Python memory allocations using the :mod:" +"`tracemalloc` module. By default, only the most recent frame is stored in a " +"traceback of a trace. Use ``-X tracemalloc=NFRAME`` to start tracing with a " +"traceback limit of *NFRAME* frames. See the :func:`tracemalloc.start` for " +"more information." +msgstr "" + +#: ../Doc/using/cmdline.rst:398 +msgid "" +"``-X showalloccount`` to enable the output of the total count of allocated " +"objects for each type (only works when built with ``COUNT_ALLOCS`` defined);" +msgstr "" + +#: ../Doc/using/cmdline.rst:401 +msgid "" +"It also allows passing arbitrary values and retrieving them through the :" +"data:`sys._xoptions` dictionary." +msgstr "" + +#: ../Doc/using/cmdline.rst:404 +msgid "It is now allowed to pass :option:`-X` with CPython." +msgstr "" + +#: ../Doc/using/cmdline.rst:407 +msgid "The ``-X faulthandler`` option." +msgstr "" + +#: ../Doc/using/cmdline.rst:410 +msgid "The ``-X showrefcount`` and ``-X tracemalloc`` options." +msgstr "" + +#: ../Doc/using/cmdline.rst:413 +msgid "The ``-X showalloccount`` option." +msgstr "" + +#: ../Doc/using/cmdline.rst:418 +msgid "Options you shouldn't use" +msgstr "" + +#: ../Doc/using/cmdline.rst:422 +msgid "Reserved for use by Jython_." +msgstr "" + +#: ../Doc/using/cmdline.rst:430 +msgid "Environment variables" +msgstr "" + +#: ../Doc/using/cmdline.rst:432 +msgid "" +"These environment variables influence Python's behavior, they are processed " +"before the command-line switches other than -E or -I. It is customary that " +"command-line switches override environmental variables where there is a " +"conflict." +msgstr "" + +#: ../Doc/using/cmdline.rst:439 +msgid "" +"Change the location of the standard Python libraries. By default, the " +"libraries are searched in :file:`{prefix}/lib/python{version}` and :file:" +"`{exec_prefix}/lib/python{version}`, where :file:`{prefix}` and :file:" +"`{exec_prefix}` are installation-dependent directories, both defaulting to :" +"file:`/usr/local`." +msgstr "" + +#: ../Doc/using/cmdline.rst:445 +msgid "" +"When :envvar:`PYTHONHOME` is set to a single directory, its value replaces " +"both :file:`{prefix}` and :file:`{exec_prefix}`. To specify different " +"values for these, set :envvar:`PYTHONHOME` to :file:`{prefix}:{exec_prefix}`." +msgstr "" + +#: ../Doc/using/cmdline.rst:452 +msgid "" +"Augment the default search path for module files. The format is the same as " +"the shell's :envvar:`PATH`: one or more directory pathnames separated by :" +"data:`os.pathsep` (e.g. colons on Unix or semicolons on Windows). Non-" +"existent directories are silently ignored." +msgstr "" + +#: ../Doc/using/cmdline.rst:457 +msgid "" +"In addition to normal directories, individual :envvar:`PYTHONPATH` entries " +"may refer to zipfiles containing pure Python modules (in either source or " +"compiled form). Extension modules cannot be imported from zipfiles." +msgstr "" + +#: ../Doc/using/cmdline.rst:461 +msgid "" +"The default search path is installation dependent, but generally begins " +"with :file:`{prefix}/lib/python{version}` (see :envvar:`PYTHONHOME` above). " +"It is *always* appended to :envvar:`PYTHONPATH`." +msgstr "" + +#: ../Doc/using/cmdline.rst:465 +msgid "" +"An additional directory will be inserted in the search path in front of :" +"envvar:`PYTHONPATH` as described above under :ref:`using-on-interface-" +"options`. The search path can be manipulated from within a Python program as " +"the variable :data:`sys.path`." +msgstr "" + +#: ../Doc/using/cmdline.rst:473 +msgid "" +"If this is the name of a readable file, the Python commands in that file are " +"executed before the first prompt is displayed in interactive mode. The file " +"is executed in the same namespace where interactive commands are executed so " +"that objects defined or imported in it can be used without qualification in " +"the interactive session. You can also change the prompts :data:`sys.ps1` " +"and :data:`sys.ps2` and the hook :data:`sys.__interactivehook__` in this " +"file." +msgstr "" + +#: ../Doc/using/cmdline.rst:483 +msgid "" +"If this is set to a non-empty string it is equivalent to specifying the :" +"option:`-O` option. If set to an integer, it is equivalent to specifying :" +"option:`-O` multiple times." +msgstr "" + +#: ../Doc/using/cmdline.rst:490 +msgid "" +"If this is set to a non-empty string it is equivalent to specifying the :" +"option:`-d` option. If set to an integer, it is equivalent to specifying :" +"option:`-d` multiple times." +msgstr "" + +#: ../Doc/using/cmdline.rst:497 +msgid "" +"If this is set to a non-empty string it is equivalent to specifying the :" +"option:`-i` option." +msgstr "" + +#: ../Doc/using/cmdline.rst:500 +msgid "" +"This variable can also be modified by Python code using :data:`os.environ` " +"to force inspect mode on program termination." +msgstr "" + +#: ../Doc/using/cmdline.rst:506 +msgid "" +"If this is set to a non-empty string it is equivalent to specifying the :" +"option:`-u` option." +msgstr "" + +#: ../Doc/using/cmdline.rst:512 +msgid "" +"If this is set to a non-empty string it is equivalent to specifying the :" +"option:`-v` option. If set to an integer, it is equivalent to specifying :" +"option:`-v` multiple times." +msgstr "" + +#: ../Doc/using/cmdline.rst:519 +msgid "" +"If this is set, Python ignores case in :keyword:`import` statements. This " +"only works on Windows and OS X." +msgstr "" + +#: ../Doc/using/cmdline.rst:525 +msgid "" +"If this is set to a non-empty string, Python won't try to write ``.pyc`` or " +"``.pyo`` files on the import of source modules. This is equivalent to " +"specifying the :option:`-B` option." +msgstr "" + +#: ../Doc/using/cmdline.rst:532 +msgid "" +"If this variable is not set or set to ``random``, a random value is used to " +"seed the hashes of str, bytes and datetime objects." +msgstr "" + +#: ../Doc/using/cmdline.rst:535 +msgid "" +"If :envvar:`PYTHONHASHSEED` is set to an integer value, it is used as a " +"fixed seed for generating the hash() of the types covered by the hash " +"randomization." +msgstr "" + +#: ../Doc/using/cmdline.rst:539 +msgid "" +"Its purpose is to allow repeatable hashing, such as for selftests for the " +"interpreter itself, or to allow a cluster of python processes to share hash " +"values." +msgstr "" + +#: ../Doc/using/cmdline.rst:543 +msgid "" +"The integer must be a decimal number in the range [0,4294967295]. " +"Specifying the value 0 will disable hash randomization." +msgstr "" + +#: ../Doc/using/cmdline.rst:551 +msgid "" +"If this is set before running the interpreter, it overrides the encoding " +"used for stdin/stdout/stderr, in the syntax ``encodingname:errorhandler``. " +"Both the ``encodingname`` and the ``:errorhandler`` parts are optional and " +"have the same meaning as in :func:`str.encode`." +msgstr "" + +#: ../Doc/using/cmdline.rst:556 +msgid "" +"For stderr, the ``:errorhandler`` part is ignored; the handler will always " +"be ``'backslashreplace'``." +msgstr "" + +#: ../Doc/using/cmdline.rst:559 +msgid "The ``encodingname`` part is now optional." +msgstr "" + +#: ../Doc/using/cmdline.rst:562 +msgid "" +"On Windows, the encoding specified by this variable is ignored for " +"interactive console buffers unless :envvar:`PYTHONLEGACYWINDOWSIOENCODING` " +"is also specified. Files and pipes redirected through the standard streams " +"are not affected." +msgstr "" + +#: ../Doc/using/cmdline.rst:569 +msgid "" +"If this is set, Python won't add the :data:`user site-packages directory " +"` to :data:`sys.path`." +msgstr "" + +#: ../Doc/using/cmdline.rst:579 +msgid "" +"Defines the :data:`user base directory `, which is used to " +"compute the path of the :data:`user site-packages directory ` and :ref:`Distutils installation paths ` " +"for ``python setup.py install --user``." +msgstr "" + +#: ../Doc/using/cmdline.rst:591 +msgid "" +"If this environment variable is set, ``sys.argv[0]`` will be set to its " +"value instead of the value got through the C runtime. Only works on Mac OS " +"X." +msgstr "" + +#: ../Doc/using/cmdline.rst:597 +msgid "" +"This is equivalent to the :option:`-W` option. If set to a comma separated " +"string, it is equivalent to specifying :option:`-W` multiple times." +msgstr "" + +#: ../Doc/using/cmdline.rst:603 +msgid "" +"If this environment variable is set to a non-empty string, :func:" +"`faulthandler.enable` is called at startup: install a handler for :const:" +"`SIGSEGV`, :const:`SIGFPE`, :const:`SIGABRT`, :const:`SIGBUS` and :const:" +"`SIGILL` signals to dump the Python traceback. This is equivalent to :" +"option:`-X` ``faulthandler`` option." +msgstr "" + +#: ../Doc/using/cmdline.rst:614 +msgid "" +"If this environment variable is set to a non-empty string, start tracing " +"Python memory allocations using the :mod:`tracemalloc` module. The value of " +"the variable is the maximum number of frames stored in a traceback of a " +"trace. For example, ``PYTHONTRACEMALLOC=1`` stores only the most recent " +"frame. See the :func:`tracemalloc.start` for more information." +msgstr "" + +#: ../Doc/using/cmdline.rst:625 +msgid "" +"If this environment variable is set to a non-empty string, enable the :ref:" +"`debug mode ` of the :mod:`asyncio` module." +msgstr "" + +#: ../Doc/using/cmdline.rst:633 +msgid "Set the Python memory allocators and/or install debug hooks." +msgstr "" + +#: ../Doc/using/cmdline.rst:635 +msgid "Set the family of memory allocators used by Python:" +msgstr "" + +#: ../Doc/using/cmdline.rst:637 +msgid "" +"``malloc``: use the :c:func:`malloc` function of the C library for all " +"domains (:c:data:`PYMEM_DOMAIN_RAW`, :c:data:`PYMEM_DOMAIN_MEM`, :c:data:" +"`PYMEM_DOMAIN_OBJ`)." +msgstr "" + +#: ../Doc/using/cmdline.rst:640 +msgid "" +"``pymalloc``: use the :ref:`pymalloc allocator ` for :c:data:" +"`PYMEM_DOMAIN_MEM` and :c:data:`PYMEM_DOMAIN_OBJ` domains and use the :c:" +"func:`malloc` function for the :c:data:`PYMEM_DOMAIN_RAW` domain." +msgstr "" + +#: ../Doc/using/cmdline.rst:644 +msgid "Install debug hooks:" +msgstr "" + +#: ../Doc/using/cmdline.rst:646 +msgid "``debug``: install debug hooks on top of the default memory allocator" +msgstr "" + +#: ../Doc/using/cmdline.rst:647 +msgid "``malloc_debug``: same as ``malloc`` but also install debug hooks" +msgstr "" + +#: ../Doc/using/cmdline.rst:648 +msgid "``pymalloc_debug``: same as ``pymalloc`` but also install debug hooks" +msgstr "" + +#: ../Doc/using/cmdline.rst:650 +msgid "" +"When Python is compiled in release mode, the default is ``pymalloc``. When " +"compiled in debug mode, the default is ``pymalloc_debug`` and the debug " +"hooks are used automatically." +msgstr "" + +#: ../Doc/using/cmdline.rst:654 +msgid "" +"If Python is configured without ``pymalloc`` support, ``pymalloc`` and " +"``pymalloc_debug`` are not available, the default is ``malloc`` in release " +"mode and ``malloc_debug`` in debug mode." +msgstr "" + +#: ../Doc/using/cmdline.rst:658 +msgid "" +"See the :c:func:`PyMem_SetupDebugHooks` function for debug hooks on Python " +"memory allocators." +msgstr "" + +#: ../Doc/using/cmdline.rst:666 +msgid "" +"If set to a non-empty string, Python will print statistics of the :ref:" +"`pymalloc memory allocator ` every time a new pymalloc object " +"arena is created, and on shutdown." +msgstr "" + +#: ../Doc/using/cmdline.rst:670 +msgid "" +"This variable is ignored if the :envvar:`PYTHONMALLOC` environment variable " +"is used to force the :c:func:`malloc` allocator of the C library, or if " +"Python is configured without ``pymalloc`` support." +msgstr "" + +#: ../Doc/using/cmdline.rst:674 +msgid "" +"This variable can now also be used on Python compiled in release mode. It " +"now has no effect if set to an empty string." +msgstr "" + +#: ../Doc/using/cmdline.rst:681 +msgid "" +"If set to a non-empty string, the default filesystem encoding and errors " +"mode will revert to their pre-3.6 values of 'mbcs' and 'replace', " +"respectively. Otherwise, the new defaults 'utf-8' and 'surrogatepass' are " +"used." +msgstr "" + +#: ../Doc/using/cmdline.rst:685 +msgid "" +"This may also be enabled at runtime with :func:`sys." +"_enablelegacywindowsfsencoding()`." +msgstr "" + +#: ../Doc/using/cmdline.rst:688 ../Doc/using/cmdline.rst:702 +msgid "Availability: Windows" +msgstr "" + +#: ../Doc/using/cmdline.rst:690 +msgid "See :pep:`529` for more details." +msgstr "" + +#: ../Doc/using/cmdline.rst:695 +msgid "" +"If set to a non-empty string, does not use the new console reader and " +"writer. This means that Unicode characters will be encoded according to the " +"active console code page, rather than using utf-8." +msgstr "" + +#: ../Doc/using/cmdline.rst:699 +msgid "" +"This variable is ignored if the standard streams are redirected (to files or " +"pipes) rather than referring to console buffers." +msgstr "" + +#: ../Doc/using/cmdline.rst:707 +msgid "Debug-mode variables" +msgstr "" + +#: ../Doc/using/cmdline.rst:709 +msgid "" +"Setting these variables only has an effect in a debug build of Python, that " +"is, if Python was configured with the ``--with-pydebug`` build option." +msgstr "" + +#: ../Doc/using/cmdline.rst:714 +msgid "If set, Python will print threading debug info." +msgstr "" + +#: ../Doc/using/cmdline.rst:719 +msgid "" +"If set, Python will dump objects and reference counts still alive after " +"shutting down the interpreter." +msgstr "" + +#: ../Doc/using/index.rst:5 +msgid "Python Setup and Usage" +msgstr "" + +#: ../Doc/using/index.rst:8 +msgid "" +"This part of the documentation is devoted to general information on the " +"setup of the Python environment on different platform, the invocation of the " +"interpreter and things that make working with Python easier." +msgstr "" + +#: ../Doc/using/mac.rst:6 +msgid "Using Python on a Macintosh" +msgstr "" + +#: ../Doc/using/mac.rst:8 +msgid "Bob Savage " +msgstr "" + +#: ../Doc/using/mac.rst:11 +msgid "" +"Python on a Macintosh running Mac OS X is in principle very similar to " +"Python on any other Unix platform, but there are a number of additional " +"features such as the IDE and the Package Manager that are worth pointing out." +msgstr "" + +#: ../Doc/using/mac.rst:18 +msgid "Getting and Installing MacPython" +msgstr "" + +#: ../Doc/using/mac.rst:20 +msgid "" +"Mac OS X 10.8 comes with Python 2.7 pre-installed by Apple. If you wish, " +"you are invited to install the most recent version of Python 3 from the " +"Python website (https://www.python.org). A current \"universal binary\" " +"build of Python, which runs natively on the Mac's new Intel and legacy PPC " +"CPU's, is available there." +msgstr "" + +#: ../Doc/using/mac.rst:26 +msgid "What you get after installing is a number of things:" +msgstr "" + +#: ../Doc/using/mac.rst:28 +msgid "" +"A :file:`MacPython 3.6` folder in your :file:`Applications` folder. In here " +"you find IDLE, the development environment that is a standard part of " +"official Python distributions; PythonLauncher, which handles double-clicking " +"Python scripts from the Finder; and the \"Build Applet\" tool, which allows " +"you to package Python scripts as standalone applications on your system." +msgstr "" + +#: ../Doc/using/mac.rst:34 +msgid "" +"A framework :file:`/Library/Frameworks/Python.framework`, which includes the " +"Python executable and libraries. The installer adds this location to your " +"shell path. To uninstall MacPython, you can simply remove these three " +"things. A symlink to the Python executable is placed in /usr/local/bin/." +msgstr "" + +#: ../Doc/using/mac.rst:39 +msgid "" +"The Apple-provided build of Python is installed in :file:`/System/Library/" +"Frameworks/Python.framework` and :file:`/usr/bin/python`, respectively. You " +"should never modify or delete these, as they are Apple-controlled and are " +"used by Apple- or third-party software. Remember that if you choose to " +"install a newer Python version from python.org, you will have two different " +"but functional Python installations on your computer, so it will be " +"important that your paths and usages are consistent with what you want to do." +msgstr "" + +#: ../Doc/using/mac.rst:47 +msgid "" +"IDLE includes a help menu that allows you to access Python documentation. If " +"you are completely new to Python you should start reading the tutorial " +"introduction in that document." +msgstr "" + +#: ../Doc/using/mac.rst:51 +msgid "" +"If you are familiar with Python on other Unix platforms you should read the " +"section on running Python scripts from the Unix shell." +msgstr "" + +#: ../Doc/using/mac.rst:56 +msgid "How to run a Python script" +msgstr "" + +#: ../Doc/using/mac.rst:58 +msgid "" +"Your best way to get started with Python on Mac OS X is through the IDLE " +"integrated development environment, see section :ref:`ide` and use the Help " +"menu when the IDE is running." +msgstr "" + +#: ../Doc/using/mac.rst:62 +msgid "" +"If you want to run Python scripts from the Terminal window command line or " +"from the Finder you first need an editor to create your script. Mac OS X " +"comes with a number of standard Unix command line editors, :program:`vim` " +"and :program:`emacs` among them. If you want a more Mac-like editor, :" +"program:`BBEdit` or :program:`TextWrangler` from Bare Bones Software (see " +"http://www.barebones.com/products/bbedit/index.html) are good choices, as " +"is :program:`TextMate` (see https://macromates.com/). Other editors include :" +"program:`Gvim` (http://macvim.org) and :program:`Aquamacs` (http://aquamacs." +"org/)." +msgstr "" + +#: ../Doc/using/mac.rst:72 +msgid "" +"To run your script from the Terminal window you must make sure that :file:`/" +"usr/local/bin` is in your shell search path." +msgstr "" + +#: ../Doc/using/mac.rst:75 +msgid "To run your script from the Finder you have two options:" +msgstr "" + +#: ../Doc/using/mac.rst:77 +msgid "Drag it to :program:`PythonLauncher`" +msgstr "" + +#: ../Doc/using/mac.rst:79 +msgid "" +"Select :program:`PythonLauncher` as the default application to open your " +"script (or any .py script) through the finder Info window and double-click " +"it. :program:`PythonLauncher` has various preferences to control how your " +"script is launched. Option-dragging allows you to change these for one " +"invocation, or use its Preferences menu to change things globally." +msgstr "" + +#: ../Doc/using/mac.rst:89 +msgid "Running scripts with a GUI" +msgstr "" + +#: ../Doc/using/mac.rst:91 +msgid "" +"With older versions of Python, there is one Mac OS X quirk that you need to " +"be aware of: programs that talk to the Aqua window manager (in other words, " +"anything that has a GUI) need to be run in a special way. Use :program:" +"`pythonw` instead of :program:`python` to start such scripts." +msgstr "" + +#: ../Doc/using/mac.rst:96 +msgid "" +"With Python 3.6, you can use either :program:`python` or :program:`pythonw`." +msgstr "" + +#: ../Doc/using/mac.rst:100 +msgid "Configuration" +msgstr "" + +#: ../Doc/using/mac.rst:102 +msgid "" +"Python on OS X honors all standard Unix environment variables such as :" +"envvar:`PYTHONPATH`, but setting these variables for programs started from " +"the Finder is non-standard as the Finder does not read your :file:`.profile` " +"or :file:`.cshrc` at startup. You need to create a file :file:`~/.MacOSX/" +"environment.plist`. See Apple's Technical Document QA1067 for details." +msgstr "" + +#: ../Doc/using/mac.rst:109 +msgid "" +"For more information on installation Python packages in MacPython, see " +"section :ref:`mac-package-manager`." +msgstr "" + +#: ../Doc/using/mac.rst:116 +msgid "The IDE" +msgstr "" + +#: ../Doc/using/mac.rst:118 +msgid "" +"MacPython ships with the standard IDLE development environment. A good " +"introduction to using IDLE can be found at https://hkn.eecs.berkeley.edu/" +"~dyoo/python/idle_intro/index.html." +msgstr "" + +#: ../Doc/using/mac.rst:126 +msgid "Installing Additional Python Packages" +msgstr "" + +#: ../Doc/using/mac.rst:128 +msgid "There are several methods to install additional Python packages:" +msgstr "" + +#: ../Doc/using/mac.rst:130 +msgid "" +"Packages can be installed via the standard Python distutils mode (``python " +"setup.py install``)." +msgstr "" + +#: ../Doc/using/mac.rst:133 +msgid "" +"Many packages can also be installed via the :program:`setuptools` extension " +"or :program:`pip` wrapper, see https://pip.pypa.io/." +msgstr "" + +#: ../Doc/using/mac.rst:138 +msgid "GUI Programming on the Mac" +msgstr "" + +#: ../Doc/using/mac.rst:140 +msgid "" +"There are several options for building GUI applications on the Mac with " +"Python." +msgstr "" + +#: ../Doc/using/mac.rst:142 +msgid "" +"*PyObjC* is a Python binding to Apple's Objective-C/Cocoa framework, which " +"is the foundation of most modern Mac development. Information on PyObjC is " +"available from https://pythonhosted.org/pyobjc/." +msgstr "" + +#: ../Doc/using/mac.rst:146 +msgid "" +"The standard Python GUI toolkit is :mod:`tkinter`, based on the cross-" +"platform Tk toolkit (https://www.tcl.tk). An Aqua-native version of Tk is " +"bundled with OS X by Apple, and the latest version can be downloaded and " +"installed from https://www.activestate.com; it can also be built from source." +msgstr "" + +#: ../Doc/using/mac.rst:151 +msgid "" +"*wxPython* is another popular cross-platform GUI toolkit that runs natively " +"on Mac OS X. Packages and documentation are available from http://www." +"wxpython.org." +msgstr "" + +#: ../Doc/using/mac.rst:154 +msgid "" +"*PyQt* is another popular cross-platform GUI toolkit that runs natively on " +"Mac OS X. More information can be found at https://riverbankcomputing.com/" +"software/pyqt/intro." +msgstr "" + +#: ../Doc/using/mac.rst:160 +msgid "Distributing Python Applications on the Mac" +msgstr "" + +#: ../Doc/using/mac.rst:162 +msgid "" +"The \"Build Applet\" tool that is placed in the MacPython 3.6 folder is fine " +"for packaging small Python scripts on your own machine to run as a standard " +"Mac application. This tool, however, is not robust enough to distribute " +"Python applications to other users." +msgstr "" + +#: ../Doc/using/mac.rst:167 +msgid "" +"The standard tool for deploying standalone Python applications on the Mac " +"is :program:`py2app`. More information on installing and using py2app can be " +"found at http://undefined.org/python/#py2app." +msgstr "" + +#: ../Doc/using/mac.rst:173 +msgid "Other Resources" +msgstr "" + +#: ../Doc/using/mac.rst:175 +msgid "" +"The MacPython mailing list is an excellent support resource for Python users " +"and developers on the Mac:" +msgstr "" + +#: ../Doc/using/mac.rst:178 +msgid "https://www.python.org/community/sigs/current/pythonmac-sig/" +msgstr "" + +#: ../Doc/using/mac.rst:180 +msgid "Another useful resource is the MacPython wiki:" +msgstr "" + +#: ../Doc/using/mac.rst:182 +msgid "https://wiki.python.org/moin/MacPython" +msgstr "" + +#: ../Doc/using/unix.rst:7 +msgid "Using Python on Unix platforms" +msgstr "" + +#: ../Doc/using/unix.rst:13 +msgid "Getting and installing the latest version of Python" +msgstr "" + +#: ../Doc/using/unix.rst:16 +msgid "On Linux" +msgstr "" + +#: ../Doc/using/unix.rst:18 +msgid "" +"Python comes preinstalled on most Linux distributions, and is available as a " +"package on all others. However there are certain features you might want to " +"use that are not available on your distro's package. You can easily compile " +"the latest version of Python from source." +msgstr "" + +#: ../Doc/using/unix.rst:23 +msgid "" +"In the event that Python doesn't come preinstalled and isn't in the " +"repositories as well, you can easily make packages for your own distro. " +"Have a look at the following links:" +msgstr "" + +#: ../Doc/using/unix.rst:29 +msgid "https://www.debian.org/doc/manuals/maint-guide/first.en.html" +msgstr "" + +#: ../Doc/using/unix.rst:30 +msgid "for Debian users" +msgstr "" + +#: ../Doc/using/unix.rst:31 +msgid "https://en.opensuse.org/Portal:Packaging" +msgstr "" + +#: ../Doc/using/unix.rst:32 +msgid "for OpenSuse users" +msgstr "" + +#: ../Doc/using/unix.rst:33 +msgid "" +"https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/" +"RPM_Guide/ch-creating-rpms.html" +msgstr "" + +#: ../Doc/using/unix.rst:34 +msgid "for Fedora users" +msgstr "" + +#: ../Doc/using/unix.rst:35 +msgid "http://www.slackbook.org/html/package-management-making-packages.html" +msgstr "" + +#: ../Doc/using/unix.rst:36 +msgid "for Slackware users" +msgstr "" + +#: ../Doc/using/unix.rst:40 +msgid "On FreeBSD and OpenBSD" +msgstr "" + +#: ../Doc/using/unix.rst:42 +msgid "FreeBSD users, to add the package use::" +msgstr "" + +#: ../Doc/using/unix.rst:46 +msgid "OpenBSD users use::" +msgstr "" + +#: ../Doc/using/unix.rst:50 +msgid "For example i386 users get the 2.5.1 version of Python using::" +msgstr "" + +#: ../Doc/using/unix.rst:56 +msgid "On OpenSolaris" +msgstr "" + +#: ../Doc/using/unix.rst:58 +msgid "" +"You can get Python from `OpenCSW `_. Various " +"versions of Python are available and can be installed with e.g. ``pkgutil -i " +"python27``." +msgstr "" + +#: ../Doc/using/unix.rst:65 +msgid "Building Python" +msgstr "" + +#: ../Doc/using/unix.rst:67 +msgid "" +"If you want to compile CPython yourself, first thing you should do is get " +"the `source `_. You can download " +"either the latest release's source or just grab a fresh `clone `_. (If you want to " +"contribute patches, you will need a clone.)" +msgstr "" + +#: ../Doc/using/unix.rst:73 +msgid "The build process consists in the usual ::" +msgstr "" + +#: ../Doc/using/unix.rst:79 +msgid "" +"invocations. Configuration options and caveats for specific Unix platforms " +"are extensively documented in the :source:`README` file in the root of the " +"Python source tree." +msgstr "" + +#: ../Doc/using/unix.rst:85 +msgid "" +"``make install`` can overwrite or masquerade the :file:`python3` binary. " +"``make altinstall`` is therefore recommended instead of ``make install`` " +"since it only installs :file:`{exec_prefix}/bin/python{version}`." +msgstr "" + +#: ../Doc/using/unix.rst:91 +msgid "Python-related paths and files" +msgstr "" + +#: ../Doc/using/unix.rst:93 +msgid "" +"These are subject to difference depending on local installation " +"conventions; :envvar:`prefix` (``${prefix}``) and :envvar:`exec_prefix` (``" +"${exec_prefix}``) are installation-dependent and should be interpreted as " +"for GNU software; they may be the same." +msgstr "" + +#: ../Doc/using/unix.rst:98 +msgid "" +"For example, on most Linux systems, the default for both is :file:`/usr`." +msgstr "" + +#: ../Doc/using/unix.rst:101 +msgid "File/directory" +msgstr "" + +#: ../Doc/using/unix.rst:101 +msgid "Meaning" +msgstr "" + +#: ../Doc/using/unix.rst:103 +msgid ":file:`{exec_prefix}/bin/python3`" +msgstr "" + +#: ../Doc/using/unix.rst:103 +msgid "Recommended location of the interpreter." +msgstr "" + +#: ../Doc/using/unix.rst:105 +msgid "" +":file:`{prefix}/lib/python{version}`, :file:`{exec_prefix}/lib/" +"python{version}`" +msgstr "" + +#: ../Doc/using/unix.rst:105 +msgid "" +"Recommended locations of the directories containing the standard modules." +msgstr "" + +#: ../Doc/using/unix.rst:108 +msgid "" +":file:`{prefix}/include/python{version}`, :file:`{exec_prefix}/include/" +"python{version}`" +msgstr "" + +#: ../Doc/using/unix.rst:108 +msgid "" +"Recommended locations of the directories containing the include files needed " +"for developing Python extensions and embedding the interpreter." +msgstr "" + +#: ../Doc/using/unix.rst:116 +msgid "Miscellaneous" +msgstr "" + +#: ../Doc/using/unix.rst:118 +msgid "" +"To easily use Python scripts on Unix, you need to make them executable, e.g. " +"with ::" +msgstr "" + +#: ../Doc/using/unix.rst:123 +msgid "" +"and put an appropriate Shebang line at the top of the script. A good choice " +"is usually ::" +msgstr "" + +#: ../Doc/using/unix.rst:128 +msgid "" +"which searches for the Python interpreter in the whole :envvar:`PATH`. " +"However, some Unices may not have the :program:`env` command, so you may " +"need to hardcode ``/usr/bin/python3`` as the interpreter path." +msgstr "" + +#: ../Doc/using/unix.rst:132 +msgid "" +"To use shell commands in your Python scripts, look at the :mod:`subprocess` " +"module." +msgstr "" + +#: ../Doc/using/unix.rst:136 +msgid "Editors" +msgstr "" + +#: ../Doc/using/unix.rst:138 +msgid "" +"Vim and Emacs are excellent editors which support Python very well. For " +"more information on how to code in Python in these editors, look at:" +msgstr "" + +#: ../Doc/using/unix.rst:141 +msgid "http://www.vim.org/scripts/script.php?script_id=790" +msgstr "" + +#: ../Doc/using/unix.rst:142 +msgid "https://sourceforge.net/projects/python-mode" +msgstr "" + +#: ../Doc/using/unix.rst:144 +msgid "" +"Geany is an excellent IDE with support for a lot of languages. For more " +"information, read: https://www.geany.org/" +msgstr "" + +#: ../Doc/using/unix.rst:147 +msgid "" +"Komodo edit is another extremely good IDE. It also has support for a lot of " +"languages. For more information, read https://komodoide.com/." +msgstr "" + +#: ../Doc/using/windows.rst:7 +msgid "Using Python on Windows" +msgstr "" + +#: ../Doc/using/windows.rst:12 +msgid "" +"This document aims to give an overview of Windows-specific behaviour you " +"should know about when using Python on Microsoft Windows." +msgstr "" + +#: ../Doc/using/windows.rst:16 +msgid "Installing Python" +msgstr "" + +#: ../Doc/using/windows.rst:18 +msgid "" +"Unlike most Unix systems and services, Windows does not include a system " +"supported installation of Python. To make Python available, the CPython team " +"has compiled Windows installers (MSI packages) with every `release `_ for many years. These installers are " +"primarily intended to add a per-user installation of Python, with the core " +"interpreter and library being used by a single user. The installer is also " +"able to install for all users of a single machine, and a separate ZIP file " +"is available for application-local distributions." +msgstr "" + +#: ../Doc/using/windows.rst:28 +msgid "Supported Versions" +msgstr "" + +#: ../Doc/using/windows.rst:30 +msgid "" +"As specified in :pep:`11`, a Python release only supports a Windows platform " +"while Microsoft considers the platform under extended support. This means " +"that Python |version| supports Windows Vista and newer. If you require " +"Windows XP support then please install Python 3.4." +msgstr "" + +#: ../Doc/using/windows.rst:36 +msgid "Installation Steps" +msgstr "" + +#: ../Doc/using/windows.rst:38 +msgid "" +"Four Python |version| installers are available for download - two each for " +"the 32-bit and 64-bit versions of the interpreter. The *web installer* is a " +"small initial download, and it will automatically download the required " +"components as necessary. The *offline installer* includes the components " +"necessary for a default installation and only requires an internet " +"connection for optional features. See :ref:`install-layout-option` for other " +"ways to avoid downloading during installation." +msgstr "" + +#: ../Doc/using/windows.rst:46 +msgid "After starting the installer, one of two options may be selected:" +msgstr "" + +#: ../Doc/using/windows.rst:50 +msgid "If you select \"Install Now\":" +msgstr "" + +#: ../Doc/using/windows.rst:52 +msgid "" +"You will *not* need to be an administrator (unless a system update for the C " +"Runtime Library is required or you install the :ref:`launcher` for all users)" +msgstr "" + +#: ../Doc/using/windows.rst:55 +msgid "Python will be installed into your user directory" +msgstr "" + +#: ../Doc/using/windows.rst:56 +msgid "" +"The :ref:`launcher` will be installed according to the option at the bottom " +"of the first page" +msgstr "" + +#: ../Doc/using/windows.rst:58 +msgid "The standard library, test suite, launcher and pip will be installed" +msgstr "" + +#: ../Doc/using/windows.rst:59 +msgid "If selected, the install directory will be added to your :envvar:`PATH`" +msgstr "" + +#: ../Doc/using/windows.rst:60 +msgid "Shortcuts will only be visible for the current user" +msgstr "" + +#: ../Doc/using/windows.rst:62 +msgid "" +"Selecting \"Customize installation\" will allow you to select the features " +"to install, the installation location and other options or post-install " +"actions. To install debugging symbols or binaries, you will need to use this " +"option." +msgstr "" + +#: ../Doc/using/windows.rst:66 +msgid "" +"To perform an all-users installation, you should select \"Customize " +"installation\". In this case:" +msgstr "" + +#: ../Doc/using/windows.rst:69 +msgid "You may be required to provide administrative credentials or approval" +msgstr "" + +#: ../Doc/using/windows.rst:70 +msgid "Python will be installed into the Program Files directory" +msgstr "" + +#: ../Doc/using/windows.rst:71 +msgid "The :ref:`launcher` will be installed into the Windows directory" +msgstr "" + +#: ../Doc/using/windows.rst:72 +msgid "Optional features may be selected during installation" +msgstr "" + +#: ../Doc/using/windows.rst:73 +msgid "The standard library can be pre-compiled to bytecode" +msgstr "" + +#: ../Doc/using/windows.rst:74 +msgid "" +"If selected, the install directory will be added to the system :envvar:`PATH`" +msgstr "" + +#: ../Doc/using/windows.rst:75 +msgid "Shortcuts are available for all users" +msgstr "" + +#: ../Doc/using/windows.rst:80 +msgid "Removing the MAX_PATH Limitation" +msgstr "" + +#: ../Doc/using/windows.rst:82 +msgid "" +"Windows historically has limited path lengths to 260 characters. This meant " +"that paths longer than this would not resolve and errors would result." +msgstr "" + +#: ../Doc/using/windows.rst:85 +msgid "" +"In the latest versions of Windows, this limitation can be expanded to " +"approximately 32,000 characters. Your administrator will need to activate " +"the \"Enable Win32 long paths\" group policy, or set the registry value " +"``HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control" +"\\FileSystem@LongPathsEnabled`` to ``1``." +msgstr "" + +#: ../Doc/using/windows.rst:91 +msgid "" +"This allows the :func:`open` function, the :mod:`os` module and most other " +"path functionality to accept and return paths longer than 260 characters " +"when using strings. (Use of bytes as paths is deprecated on Windows, and " +"this feature is not available when using bytes.)" +msgstr "" + +#: ../Doc/using/windows.rst:96 +msgid "After changing the above option, no further configuration is required." +msgstr "" + +#: ../Doc/using/windows.rst:100 +msgid "Support for long paths was enabled in Python." +msgstr "" + +#: ../Doc/using/windows.rst:105 +msgid "Installing Without UI" +msgstr "" + +#: ../Doc/using/windows.rst:107 +msgid "" +"All of the options available in the installer UI can also be specified from " +"the command line, allowing scripted installers to replicate an installation " +"on many machines without user interaction. These options may also be set " +"without suppressing the UI in order to change some of the defaults." +msgstr "" + +#: ../Doc/using/windows.rst:112 +msgid "" +"To completely hide the installer UI and install Python silently, pass the ``/" +"quiet`` option. To skip past the user interaction but still display progress " +"and errors, pass the ``/passive`` option. The ``/uninstall`` option may be " +"passed to immediately begin removing Python - no prompt will be displayed." +msgstr "" + +#: ../Doc/using/windows.rst:118 +msgid "" +"All other options are passed as ``name=value``, where the value is usually " +"``0`` to disable a feature, ``1`` to enable a feature, or a path. The full " +"list of available options is shown below." +msgstr "" + +#: ../Doc/using/windows.rst:123 +msgid "Name" +msgstr "" + +#: ../Doc/using/windows.rst:123 +msgid "Description" +msgstr "" + +#: ../Doc/using/windows.rst:123 +msgid "Default" +msgstr "" + +#: ../Doc/using/windows.rst:125 +msgid "InstallAllUsers" +msgstr "" + +#: ../Doc/using/windows.rst:125 +msgid "Perform a system-wide installation." +msgstr "" + +#: ../Doc/using/windows.rst:125 ../Doc/using/windows.rst:146 +#: ../Doc/using/windows.rst:149 ../Doc/using/windows.rst:158 +#: ../Doc/using/windows.rst:176 ../Doc/using/windows.rst:184 +#: ../Doc/using/windows.rst:187 +msgid "0" +msgstr "" + +#: ../Doc/using/windows.rst:127 +msgid "TargetDir" +msgstr "" + +#: ../Doc/using/windows.rst:127 +msgid "The installation directory" +msgstr "" + +#: ../Doc/using/windows.rst:127 +msgid "Selected based on InstallAllUsers" +msgstr "" + +#: ../Doc/using/windows.rst:130 +msgid "DefaultAllUsersTargetDir" +msgstr "" + +#: ../Doc/using/windows.rst:130 +msgid "The default installation directory for all-user installs" +msgstr "" + +#: ../Doc/using/windows.rst:130 +msgid "" +":file:`%ProgramFiles%\\\\\\ Python X.Y` or :file:`\\ %ProgramFiles(x86)%\\\\" +"\\ Python X.Y`" +msgstr "" + +#: ../Doc/using/windows.rst:135 +msgid "DefaultJustForMeTargetDir" +msgstr "" + +#: ../Doc/using/windows.rst:135 +msgid "The default install directory for just-for-me installs" +msgstr "" + +#: ../Doc/using/windows.rst:135 +msgid "" +":file:`%LocalAppData%\\\\\\ Programs\\\\PythonXY` or :file:`%LocalAppData%\\" +"\\\\ Programs\\\\PythonXY-32`" +msgstr "" + +#: ../Doc/using/windows.rst:140 +msgid "DefaultCustomTargetDir" +msgstr "" + +#: ../Doc/using/windows.rst:140 +msgid "The default custom install directory displayed in the UI" +msgstr "" + +#: ../Doc/using/windows.rst:140 ../Doc/using/windows.rst:189 +msgid "(empty)" +msgstr "" + +#: ../Doc/using/windows.rst:143 +msgid "AssociateFiles" +msgstr "" + +#: ../Doc/using/windows.rst:143 +msgid "Create file associations if the launcher is also installed." +msgstr "" + +#: ../Doc/using/windows.rst:143 ../Doc/using/windows.rst:153 +#: ../Doc/using/windows.rst:156 ../Doc/using/windows.rst:160 +#: ../Doc/using/windows.rst:163 ../Doc/using/windows.rst:166 +#: ../Doc/using/windows.rst:168 ../Doc/using/windows.rst:171 +#: ../Doc/using/windows.rst:174 ../Doc/using/windows.rst:178 +#: ../Doc/using/windows.rst:180 ../Doc/using/windows.rst:182 +msgid "1" +msgstr "" + +#: ../Doc/using/windows.rst:146 +msgid "CompileAll" +msgstr "" + +#: ../Doc/using/windows.rst:146 +msgid "Compile all ``.py`` files to ``.pyc``." +msgstr "" + +#: ../Doc/using/windows.rst:149 +msgid "PrependPath" +msgstr "" + +#: ../Doc/using/windows.rst:149 +msgid "" +"Add install and Scripts directories tho :envvar:`PATH` and ``.PY`` to :" +"envvar:`PATHEXT`" +msgstr "" + +#: ../Doc/using/windows.rst:153 +msgid "Shortcuts" +msgstr "" + +#: ../Doc/using/windows.rst:153 +msgid "" +"Create shortcuts for the interpreter, documentation and IDLE if installed." +msgstr "" + +#: ../Doc/using/windows.rst:156 +msgid "Include_doc" +msgstr "" + +#: ../Doc/using/windows.rst:156 +msgid "Install Python manual" +msgstr "" + +#: ../Doc/using/windows.rst:158 +msgid "Include_debug" +msgstr "" + +#: ../Doc/using/windows.rst:158 +msgid "Install debug binaries" +msgstr "" + +#: ../Doc/using/windows.rst:160 +msgid "Include_dev" +msgstr "" + +#: ../Doc/using/windows.rst:160 +msgid "Install developer headers and libraries" +msgstr "" + +#: ../Doc/using/windows.rst:163 +msgid "Include_exe" +msgstr "" + +#: ../Doc/using/windows.rst:163 +msgid "Install :file:`python.exe` and related files" +msgstr "" + +#: ../Doc/using/windows.rst:166 +msgid "Include_launcher" +msgstr "" + +#: ../Doc/using/windows.rst:166 +msgid "Install :ref:`launcher`." +msgstr "" + +#: ../Doc/using/windows.rst:168 +msgid "InstallLauncherAllUsers" +msgstr "" + +#: ../Doc/using/windows.rst:168 +msgid "Installs :ref:`launcher` for all users." +msgstr "" + +#: ../Doc/using/windows.rst:171 +msgid "Include_lib" +msgstr "" + +#: ../Doc/using/windows.rst:171 +msgid "Install standard library and extension modules" +msgstr "" + +#: ../Doc/using/windows.rst:174 +msgid "Include_pip" +msgstr "" + +#: ../Doc/using/windows.rst:174 +msgid "Install bundled pip and setuptools" +msgstr "" + +#: ../Doc/using/windows.rst:176 +msgid "Include_symbols" +msgstr "" + +#: ../Doc/using/windows.rst:176 +msgid "Install debugging symbols (`*`.pdb)" +msgstr "" + +#: ../Doc/using/windows.rst:178 +msgid "Include_tcltk" +msgstr "" + +#: ../Doc/using/windows.rst:178 +msgid "Install Tcl/Tk support and IDLE" +msgstr "" + +#: ../Doc/using/windows.rst:180 +msgid "Include_test" +msgstr "" + +#: ../Doc/using/windows.rst:180 +msgid "Install standard library test suite" +msgstr "" + +#: ../Doc/using/windows.rst:182 +msgid "Include_tools" +msgstr "" + +#: ../Doc/using/windows.rst:182 +msgid "Install utility scripts" +msgstr "" + +#: ../Doc/using/windows.rst:184 +msgid "LauncherOnly" +msgstr "" + +#: ../Doc/using/windows.rst:184 +msgid "Only installs the launcher. This will override most other options." +msgstr "" + +#: ../Doc/using/windows.rst:187 +msgid "SimpleInstall" +msgstr "" + +#: ../Doc/using/windows.rst:187 +msgid "Disable most install UI" +msgstr "" + +#: ../Doc/using/windows.rst:189 +msgid "SimpleInstallDescription" +msgstr "" + +#: ../Doc/using/windows.rst:189 +msgid "A custom message to display when the simplified install UI is used." +msgstr "" + +#: ../Doc/using/windows.rst:193 +msgid "" +"For example, to silently install a default, system-wide Python installation, " +"you could use the following command (from an elevated command prompt)::" +msgstr "" + +#: ../Doc/using/windows.rst:198 +msgid "" +"To allow users to easily install a personal copy of Python without the test " +"suite, you could provide a shortcut with the following command. This will " +"display a simplified initial page and disallow customization::" +msgstr "" + +#: ../Doc/using/windows.rst:205 +msgid "" +"(Note that omitting the launcher also omits file associations, and is only " +"recommended for per-user installs when there is also a system-wide " +"installation that included the launcher.)" +msgstr "" + +#: ../Doc/using/windows.rst:209 +msgid "" +"The options listed above can also be provided in a file named ``unattend." +"xml`` alongside the executable. This file specifies a list of options and " +"values. When a value is provided as an attribute, it will be converted to a " +"number if possible. Values provided as element text are always left as " +"strings. This example file sets the same options and the previous example::" +msgstr "" + +#: ../Doc/using/windows.rst:226 +msgid "Installing Without Downloading" +msgstr "" + +#: ../Doc/using/windows.rst:228 +msgid "" +"As some features of Python are not included in the initial installer " +"download, selecting those features may require an internet connection. To " +"avoid this need, all possible components may be downloaded on-demand to " +"create a complete *layout* that will no longer require an internet " +"connection regardless of the selected features. Note that this download may " +"be bigger than required, but where a large number of installations are going " +"to be performed it is very useful to have a locally cached copy." +msgstr "" + +#: ../Doc/using/windows.rst:236 +msgid "" +"Execute the following command from Command Prompt to download all possible " +"required files. Remember to substitute ``python-3.6.0.exe`` for the actual " +"name of your installer, and to create layouts in their own directories to " +"avoid collisions between files with the same name." +msgstr "" + +#: ../Doc/using/windows.rst:245 +msgid "" +"You may also specify the ``/quiet`` option to hide the progress display." +msgstr "" + +#: ../Doc/using/windows.rst:248 +msgid "Modifying an install" +msgstr "" + +#: ../Doc/using/windows.rst:250 +msgid "" +"Once Python has been installed, you can add or remove features through the " +"Programs and Features tool that is part of Windows. Select the Python entry " +"and choose \"Uninstall/Change\" to open the installer in maintenance mode." +msgstr "" + +#: ../Doc/using/windows.rst:254 +msgid "" +"\"Modify\" allows you to add or remove features by modifying the checkboxes " +"- unchanged checkboxes will not install or remove anything. Some options " +"cannot be changed in this mode, such as the install directory; to modify " +"these, you will need to remove and then reinstall Python completely." +msgstr "" + +#: ../Doc/using/windows.rst:259 +msgid "" +"\"Repair\" will verify all the files that should be installed using the " +"current settings and replace any that have been removed or modified." +msgstr "" + +#: ../Doc/using/windows.rst:262 +msgid "" +"\"Uninstall\" will remove Python entirely, with the exception of the :ref:" +"`launcher`, which has its own entry in Programs and Features." +msgstr "" + +#: ../Doc/using/windows.rst:266 +msgid "Other Platforms" +msgstr "" + +#: ../Doc/using/windows.rst:268 +msgid "" +"With ongoing development of Python, some platforms that used to be supported " +"earlier are no longer supported (due to the lack of users or developers). " +"Check :pep:`11` for details on all unsupported platforms." +msgstr "" + +#: ../Doc/using/windows.rst:272 +msgid "`Windows CE `_ is still supported." +msgstr "" + +#: ../Doc/using/windows.rst:273 +msgid "" +"The `Cygwin `_ installer offers to install the Python " +"interpreter as well (cf. `Cygwin package source `_, `Maintainer " +"releases `_)" +msgstr "" + +#: ../Doc/using/windows.rst:279 +msgid "" +"See `Python for Windows `_ for " +"detailed information about platforms with pre-compiled installers." +msgstr "" + +#: ../Doc/using/windows.rst:286 +msgid "" +"`Python on XP `_" +msgstr "" + +#: ../Doc/using/windows.rst:285 +msgid "\"7 Minutes to \"Hello World!\"\" by Richard Dooling, 2006" +msgstr "" + +#: ../Doc/using/windows.rst:292 +msgid "" +"`Installing on Windows `_" +msgstr "" + +#: ../Doc/using/windows.rst:289 +msgid "" +"in \"`Dive into Python: Python from novice to pro `_\" by Mark Pilgrim, 2004, ISBN 1-59059-356-1" +msgstr "" + +#: ../Doc/using/windows.rst:296 +msgid "" +"`For Windows users `_" +msgstr "" + +#: ../Doc/using/windows.rst:295 +msgid "" +"in \"Installing Python\" in \"`A Byte of Python `_\" by Swaroop C H, 2003" +msgstr "" + +#: ../Doc/using/windows.rst:301 +msgid "Alternative bundles" +msgstr "" + +#: ../Doc/using/windows.rst:303 +msgid "" +"Besides the standard CPython distribution, there are modified packages " +"including additional functionality. The following is a list of popular " +"versions and their key features:" +msgstr "" + +#: ../Doc/using/windows.rst:308 +msgid "`ActivePython `_" +msgstr "" + +#: ../Doc/using/windows.rst:308 +msgid "Installer with multi-platform compatibility, documentation, PyWin32" +msgstr "" + +#: ../Doc/using/windows.rst:312 +msgid "`Anaconda `_" +msgstr "" + +#: ../Doc/using/windows.rst:311 +msgid "" +"Popular scientific modules (such as numpy, scipy and pandas) and the " +"``conda`` package manager." +msgstr "" + +#: ../Doc/using/windows.rst:316 +msgid "`Canopy `_" +msgstr "" + +#: ../Doc/using/windows.rst:315 +msgid "" +"A \"comprehensive Python analysis environment\" with editors and other " +"development tools." +msgstr "" + +#: ../Doc/using/windows.rst:320 +msgid "`WinPython `_" +msgstr "" + +#: ../Doc/using/windows.rst:319 +msgid "" +"Windows-specific distribution with prebuilt scientific packages and tools " +"for building packages." +msgstr "" + +#: ../Doc/using/windows.rst:322 +msgid "" +"Note that these packages may not include the latest versions of Python or " +"other libraries, and are not maintained or supported by the core Python team." +msgstr "" + +#: ../Doc/using/windows.rst:328 +msgid "Configuring Python" +msgstr "" + +#: ../Doc/using/windows.rst:330 +msgid "" +"To run Python conveniently from a command prompt, you might consider " +"changing some default environment variables in Windows. While the installer " +"provides an option to configure the PATH and PATHEXT variables for you, this " +"is only reliable for a single, system-wide installation. If you regularly " +"use multiple versions of Python, consider using the :ref:`launcher`." +msgstr "" + +#: ../Doc/using/windows.rst:340 +msgid "Excursus: Setting environment variables" +msgstr "" + +#: ../Doc/using/windows.rst:342 +msgid "" +"Windows allows environment variables to be configured permanently at both " +"the User level and the System level, or temporarily in a command prompt." +msgstr "" + +#: ../Doc/using/windows.rst:345 +msgid "" +"To temporarily set environment variables, open Command Prompt and use the :" +"command:`set` command::" +msgstr "" + +#: ../Doc/using/windows.rst:352 +msgid "" +"These changes will apply to any further commands executed in that console, " +"and will be inherited by any applications started from the console." +msgstr "" + +#: ../Doc/using/windows.rst:355 +msgid "" +"Including the variable name within percent signs will expand to the existing " +"value, allowing you to add your new value at either the start or the end. " +"Modifying :envvar:`PATH` by adding the directory containing :program:`python." +"exe` to the start is a common way to ensure the correct version of Python is " +"launched." +msgstr "" + +#: ../Doc/using/windows.rst:361 +msgid "" +"To permanently modify the default environment variables, click Start and " +"search for 'edit environment variables', or open System properties, :" +"guilabel:`Advanced system settings` and click the :guilabel:`Environment " +"Variables` button. In this dialog, you can add or modify User and System " +"variables. To change System variables, you need non-restricted access to " +"your machine (i.e. Administrator rights)." +msgstr "" + +#: ../Doc/using/windows.rst:370 +msgid "" +"Windows will concatenate User variables *after* System variables, which may " +"cause unexpected results when modifying :envvar:`PATH`." +msgstr "" + +#: ../Doc/using/windows.rst:373 +msgid "" +"The :envvar:`PYTHONPATH` variable is used by all versions of Python 2 and " +"Python 3, so you should not permanently configure this variable unless it " +"only includes code that is compatible with all of your installed Python " +"versions." +msgstr "" + +#: ../Doc/using/windows.rst:381 +msgid "https://support.microsoft.com/kb/100843" +msgstr "" + +#: ../Doc/using/windows.rst:381 +msgid "Environment variables in Windows NT" +msgstr "" + +#: ../Doc/using/windows.rst:384 +msgid "https://technet.microsoft.com/en-us/library/cc754250.aspx" +msgstr "" + +#: ../Doc/using/windows.rst:384 +msgid "The SET command, for temporarily modifying environment variables" +msgstr "" + +#: ../Doc/using/windows.rst:387 +msgid "https://technet.microsoft.com/en-us/library/cc755104.aspx" +msgstr "" + +#: ../Doc/using/windows.rst:387 +msgid "The SETX command, for permanently modifying environment variables" +msgstr "" + +#: ../Doc/using/windows.rst:390 +msgid "https://support.microsoft.com/kb/310519" +msgstr "" + +#: ../Doc/using/windows.rst:390 +msgid "How To Manage Environment Variables in Windows XP" +msgstr "" + +#: ../Doc/using/windows.rst:392 +msgid "https://www.chem.gla.ac.uk/~louis/software/faq/q1.html" +msgstr "" + +#: ../Doc/using/windows.rst:393 +msgid "Setting Environment variables, Louis J. Farrugia" +msgstr "" + +#: ../Doc/using/windows.rst:398 +msgid "Finding the Python executable" +msgstr "" + +#: ../Doc/using/windows.rst:402 +msgid "" +"Besides using the automatically created start menu entry for the Python " +"interpreter, you might want to start Python in the command prompt. The " +"installer has an option to set that up for you." +msgstr "" + +#: ../Doc/using/windows.rst:406 +msgid "" +"On the first page of the installer, an option labelled \"Add Python to PATH" +"\" may be selected to have the installer add the install location into the :" +"envvar:`PATH`. The location of the :file:`Scripts\\\\` folder is also " +"added. This allows you to type :command:`python` to run the interpreter, " +"and :command:`pip` for the package installer. Thus, you can also execute " +"your scripts with command line options, see :ref:`using-on-cmdline` " +"documentation." +msgstr "" + +#: ../Doc/using/windows.rst:413 +msgid "" +"If you don't enable this option at install time, you can always re-run the " +"installer, select Modify, and enable it. Alternatively, you can manually " +"modify the :envvar:`PATH` using the directions in :ref:`setting-envvars`. " +"You need to set your :envvar:`PATH` environment variable to include the " +"directory of your Python installation, delimited by a semicolon from other " +"entries. An example variable could look like this (assuming the first two " +"entries already existed)::" +msgstr "" + +#: ../Doc/using/windows.rst:426 +msgid "Python Launcher for Windows" +msgstr "" + +#: ../Doc/using/windows.rst:430 +msgid "" +"The Python launcher for Windows is a utility which aids in locating and " +"executing of different Python versions. It allows scripts (or the command-" +"line) to indicate a preference for a specific Python version, and will " +"locate and execute that version." +msgstr "" + +#: ../Doc/using/windows.rst:435 +msgid "" +"Unlike the :envvar:`PATH` variable, the launcher will correctly select the " +"most appropriate version of Python. It will prefer per-user installations " +"over system-wide ones, and orders by language version rather than using the " +"most recently installed version." +msgstr "" + +#: ../Doc/using/windows.rst:441 +msgid "Getting started" +msgstr "" + +#: ../Doc/using/windows.rst:444 +msgid "From the command-line" +msgstr "" + +#: ../Doc/using/windows.rst:448 +msgid "" +"System-wide installations of Python 3.3 and later will put the launcher on " +"your :envvar:`PATH`. The launcher is compatible with all available versions " +"of Python, so it does not matter which version is installed. To check that " +"the launcher is available, execute the following command in Command Prompt:" +msgstr "" + +#: ../Doc/using/windows.rst:457 +msgid "" +"You should find that the latest version of Python you have installed is " +"started - it can be exited as normal, and any additional command-line " +"arguments specified will be sent directly to Python." +msgstr "" + +#: ../Doc/using/windows.rst:461 +msgid "" +"If you have multiple versions of Python installed (e.g., 2.7 and |version|) " +"you will have noticed that Python |version| was started - to launch Python " +"2.7, try the command:" +msgstr "" + +#: ../Doc/using/windows.rst:469 +msgid "" +"If you want the latest version of Python 2.x you have installed, try the " +"command:" +msgstr "" + +#: ../Doc/using/windows.rst:476 +msgid "You should find the latest version of Python 2.x starts." +msgstr "" + +#: ../Doc/using/windows.rst:478 +msgid "If you see the following error, you do not have the launcher installed:" +msgstr "" + +#: ../Doc/using/windows.rst:485 +msgid "" +"Per-user installations of Python do not add the launcher to :envvar:`PATH` " +"unless the option was selected on installation." +msgstr "" + +#: ../Doc/using/windows.rst:489 +msgid "Virtual environments" +msgstr "" + +#: ../Doc/using/windows.rst:493 +msgid "" +"If the launcher is run with no explicit Python version specification, and a " +"virtual environment (created with the standard library :mod:`venv` module or " +"the external ``virtualenv`` tool) active, the launcher will run the virtual " +"environment's interpreter rather than the global one. To run the global " +"interpreter, either deactivate the virtual environment, or explicitly " +"specify the global Python version." +msgstr "" + +#: ../Doc/using/windows.rst:501 +msgid "From a script" +msgstr "" + +#: ../Doc/using/windows.rst:503 +msgid "" +"Let's create a test Python script - create a file called ``hello.py`` with " +"the following contents" +msgstr "" + +#: ../Doc/using/windows.rst:512 +msgid "From the directory in which hello.py lives, execute the command:" +msgstr "" + +#: ../Doc/using/windows.rst:518 +msgid "" +"You should notice the version number of your latest Python 2.x installation " +"is printed. Now try changing the first line to be:" +msgstr "" + +#: ../Doc/using/windows.rst:525 +msgid "" +"Re-executing the command should now print the latest Python 3.x information. " +"As with the above command-line examples, you can specify a more explicit " +"version qualifier. Assuming you have Python 2.6 installed, try changing the " +"first line to ``#! python2.6`` and you should find the 2.6 version " +"information printed." +msgstr "" + +#: ../Doc/using/windows.rst:531 +msgid "" +"Note that unlike interactive use, a bare \"python\" will use the latest " +"version of Python 2.x that you have installed. This is for backward " +"compatibility and for compatibility with Unix, where the command ``python`` " +"typically refers to Python 2." +msgstr "" + +#: ../Doc/using/windows.rst:537 +msgid "From file associations" +msgstr "" + +#: ../Doc/using/windows.rst:539 +msgid "" +"The launcher should have been associated with Python files (i.e. ``.py``, ``." +"pyw``, ``.pyc`` files) when it was installed. This means that when you " +"double-click on one of these files from Windows explorer the launcher will " +"be used, and therefore you can use the same facilities described above to " +"have the script specify the version which should be used." +msgstr "" + +#: ../Doc/using/windows.rst:545 +msgid "" +"The key benefit of this is that a single launcher can support multiple " +"Python versions at the same time depending on the contents of the first line." +msgstr "" + +#: ../Doc/using/windows.rst:549 +msgid "Shebang Lines" +msgstr "" + +#: ../Doc/using/windows.rst:551 +msgid "" +"If the first line of a script file starts with ``#!``, it is known as a " +"\"shebang\" line. Linux and other Unix like operating systems have native " +"support for such lines and are commonly used on such systems to indicate how " +"a script should be executed. This launcher allows the same facilities to be " +"using with Python scripts on Windows and the examples above demonstrate " +"their use." +msgstr "" + +#: ../Doc/using/windows.rst:558 +msgid "" +"To allow shebang lines in Python scripts to be portable between Unix and " +"Windows, this launcher supports a number of 'virtual' commands to specify " +"which interpreter to use. The supported virtual commands are:" +msgstr "" + +#: ../Doc/using/windows.rst:562 +msgid "``/usr/bin/env python``" +msgstr "" + +#: ../Doc/using/windows.rst:563 +msgid "``/usr/bin/python``" +msgstr "" + +#: ../Doc/using/windows.rst:564 +msgid "``/usr/local/bin/python``" +msgstr "" + +#: ../Doc/using/windows.rst:565 +msgid "``python``" +msgstr "" + +#: ../Doc/using/windows.rst:567 +msgid "For example, if the first line of your script starts with" +msgstr "" + +#: ../Doc/using/windows.rst:573 +msgid "" +"The default Python will be located and used. As many Python scripts written " +"to work on Unix will already have this line, you should find these scripts " +"can be used by the launcher without modification. If you are writing a new " +"script on Windows which you hope will be useful on Unix, you should use one " +"of the shebang lines starting with ``/usr``." +msgstr "" + +#: ../Doc/using/windows.rst:579 +msgid "" +"Any of the above virtual commands can be suffixed with an explicit version " +"(either just the major version, or the major and minor version) - for " +"example ``/usr/bin/python2.7`` - which will cause that specific version to " +"be located and used." +msgstr "" + +#: ../Doc/using/windows.rst:584 +msgid "" +"The ``/usr/bin/env`` form of shebang line has one further special property. " +"Before looking for installed Python interpreters, this form will search the " +"executable :envvar:`PATH` for a Python executable. This corresponds to the " +"behaviour of the Unix ``env`` program, which performs a :envvar:`PATH` " +"search." +msgstr "" + +#: ../Doc/using/windows.rst:590 +msgid "Arguments in shebang lines" +msgstr "" + +#: ../Doc/using/windows.rst:592 +msgid "" +"The shebang lines can also specify additional options to be passed to the " +"Python interpreter. For example, if you have a shebang line:" +msgstr "" + +#: ../Doc/using/windows.rst:599 +msgid "Then Python will be started with the ``-v`` option" +msgstr "" + +#: ../Doc/using/windows.rst:602 +msgid "Customization" +msgstr "" + +#: ../Doc/using/windows.rst:605 +msgid "Customization via INI files" +msgstr "" + +#: ../Doc/using/windows.rst:607 +msgid "" +"Two .ini files will be searched by the launcher - ``py.ini`` in the current " +"user's \"application data\" directory (i.e. the directory returned by " +"calling the Windows function SHGetFolderPath with CSIDL_LOCAL_APPDATA) and " +"``py.ini`` in the same directory as the launcher. The same .ini files are " +"used for both the 'console' version of the launcher (i.e. py.exe) and for " +"the 'windows' version (i.e. pyw.exe)" +msgstr "" + +#: ../Doc/using/windows.rst:614 +msgid "" +"Customization specified in the \"application directory\" will have " +"precedence over the one next to the executable, so a user, who may not have " +"write access to the .ini file next to the launcher, can override commands in " +"that global .ini file)" +msgstr "" + +#: ../Doc/using/windows.rst:619 +msgid "Customizing default Python versions" +msgstr "" + +#: ../Doc/using/windows.rst:621 +msgid "" +"In some cases, a version qualifier can be included in a command to dictate " +"which version of Python will be used by the command. A version qualifier " +"starts with a major version number and can optionally be followed by a " +"period ('.') and a minor version specifier. If the minor qualifier is " +"specified, it may optionally be followed by \"-32\" to indicate the 32-bit " +"implementation of that version be used." +msgstr "" + +#: ../Doc/using/windows.rst:628 +msgid "" +"For example, a shebang line of ``#!python`` has no version qualifier, while " +"``#!python3`` has a version qualifier which specifies only a major version." +msgstr "" + +#: ../Doc/using/windows.rst:631 +msgid "" +"If no version qualifiers are found in a command, the environment variable " +"``PY_PYTHON`` can be set to specify the default version qualifier - the " +"default value is \"2\". Note this value could specify just a major version " +"(e.g. \"2\") or a major.minor qualifier (e.g. \"2.6\"), or even major." +"minor-32." +msgstr "" + +#: ../Doc/using/windows.rst:636 +msgid "" +"If no minor version qualifiers are found, the environment variable " +"``PY_PYTHON{major}`` (where ``{major}`` is the current major version " +"qualifier as determined above) can be set to specify the full version. If no " +"such option is found, the launcher will enumerate the installed Python " +"versions and use the latest minor release found for the major version, which " +"is likely, although not guaranteed, to be the most recently installed " +"version in that family." +msgstr "" + +#: ../Doc/using/windows.rst:644 +msgid "" +"On 64-bit Windows with both 32-bit and 64-bit implementations of the same " +"(major.minor) Python version installed, the 64-bit version will always be " +"preferred. This will be true for both 32-bit and 64-bit implementations of " +"the launcher - a 32-bit launcher will prefer to execute a 64-bit Python " +"installation of the specified version if available. This is so the behavior " +"of the launcher can be predicted knowing only what versions are installed on " +"the PC and without regard to the order in which they were installed (i.e., " +"without knowing whether a 32 or 64-bit version of Python and corresponding " +"launcher was installed last). As noted above, an optional \"-32\" suffix can " +"be used on a version specifier to change this behaviour." +msgstr "" + +#: ../Doc/using/windows.rst:655 +msgid "Examples:" +msgstr "" + +#: ../Doc/using/windows.rst:657 +msgid "" +"If no relevant options are set, the commands ``python`` and ``python2`` will " +"use the latest Python 2.x version installed and the command ``python3`` will " +"use the latest Python 3.x installed." +msgstr "" + +#: ../Doc/using/windows.rst:661 +msgid "" +"The commands ``python3.1`` and ``python2.7`` will not consult any options at " +"all as the versions are fully specified." +msgstr "" + +#: ../Doc/using/windows.rst:664 +msgid "" +"If ``PY_PYTHON=3``, the commands ``python`` and ``python3`` will both use " +"the latest installed Python 3 version." +msgstr "" + +#: ../Doc/using/windows.rst:667 +msgid "" +"If ``PY_PYTHON=3.1-32``, the command ``python`` will use the 32-bit " +"implementation of 3.1 whereas the command ``python3`` will use the latest " +"installed Python (PY_PYTHON was not considered at all as a major version was " +"specified.)" +msgstr "" + +#: ../Doc/using/windows.rst:672 +msgid "" +"If ``PY_PYTHON=3`` and ``PY_PYTHON3=3.1``, the commands ``python`` and " +"``python3`` will both use specifically 3.1" +msgstr "" + +#: ../Doc/using/windows.rst:675 +msgid "" +"In addition to environment variables, the same settings can be configured in " +"the .INI file used by the launcher. The section in the INI file is called " +"``[defaults]`` and the key name will be the same as the environment " +"variables without the leading ``PY_`` prefix (and note that the key names in " +"the INI file are case insensitive.) The contents of an environment variable " +"will override things specified in the INI file." +msgstr "" + +#: ../Doc/using/windows.rst:682 +msgid "For example:" +msgstr "" + +#: ../Doc/using/windows.rst:684 +msgid "Setting ``PY_PYTHON=3.1`` is equivalent to the INI file containing:" +msgstr "" + +#: ../Doc/using/windows.rst:691 +msgid "" +"Setting ``PY_PYTHON=3`` and ``PY_PYTHON3=3.1`` is equivalent to the INI file " +"containing:" +msgstr "" + +#: ../Doc/using/windows.rst:701 +msgid "Diagnostics" +msgstr "" + +#: ../Doc/using/windows.rst:703 +msgid "" +"If an environment variable ``PYLAUNCH_DEBUG`` is set (to any value), the " +"launcher will print diagnostic information to stderr (i.e. to the console). " +"While this information manages to be simultaneously verbose *and* terse, it " +"should allow you to see what versions of Python were located, why a " +"particular version was chosen and the exact command-line used to execute the " +"target Python." +msgstr "" + +#: ../Doc/using/windows.rst:715 +msgid "Finding modules" +msgstr "" + +#: ../Doc/using/windows.rst:717 +msgid "" +"Python usually stores its library (and thereby your site-packages folder) in " +"the installation directory. So, if you had installed Python to :file:`C:\\" +"\\Python\\\\`, the default library would reside in :file:`C:\\\\Python\\\\Lib" +"\\\\` and third-party modules should be stored in :file:`C:\\\\Python\\\\Lib" +"\\\\site-packages\\\\`." +msgstr "" + +#: ../Doc/using/windows.rst:723 +msgid "" +"To completely override :data:`sys.path`, create a ``._pth`` file with the " +"same name as the DLL (``python36._pth``) or the executable (``python._pth``) " +"and specify one line for each path to add to :data:`sys.path`. The file " +"based on the DLL name overrides the one based on the executable, which " +"allows paths to be restricted for any program loading the runtime if desired." +msgstr "" + +#: ../Doc/using/windows.rst:729 +msgid "" +"When the file exists, all registry and environment variables are ignored, " +"isolated mode is enabled, and :mod:`site` is not imported unless one line in " +"the file specifies ``import site``. Blank paths and lines starting with " +"``#`` are ignored. Each path may be absolute or relative to the location of " +"the file. Import statements other than to ``site`` are not permitted, and " +"arbitrary code cannot be specified." +msgstr "" + +#: ../Doc/using/windows.rst:736 +msgid "" +"Note that ``.pth`` files (without leading underscore) will be processed " +"normally by the :mod:`site` module." +msgstr "" + +#: ../Doc/using/windows.rst:739 +msgid "" +"When no ``._pth`` file is found, this is how :data:`sys.path` is populated " +"on Windows:" +msgstr "" + +#: ../Doc/using/windows.rst:742 +msgid "" +"An empty entry is added at the start, which corresponds to the current " +"directory." +msgstr "" + +#: ../Doc/using/windows.rst:745 +msgid "" +"If the environment variable :envvar:`PYTHONPATH` exists, as described in :" +"ref:`using-on-envvars`, its entries are added next. Note that on Windows, " +"paths in this variable must be separated by semicolons, to distinguish them " +"from the colon used in drive identifiers (``C:\\`` etc.)." +msgstr "" + +#: ../Doc/using/windows.rst:750 +msgid "" +"Additional \"application paths\" can be added in the registry as subkeys of :" +"samp:`\\\\SOFTWARE\\\\Python\\\\PythonCore\\\\{version}\\\\PythonPath` under " +"both the ``HKEY_CURRENT_USER`` and ``HKEY_LOCAL_MACHINE`` hives. Subkeys " +"which have semicolon-delimited path strings as their default value will " +"cause each path to be added to :data:`sys.path`. (Note that all known " +"installers only use HKLM, so HKCU is typically empty.)" +msgstr "" + +#: ../Doc/using/windows.rst:757 +msgid "" +"If the environment variable :envvar:`PYTHONHOME` is set, it is assumed as " +"\"Python Home\". Otherwise, the path of the main Python executable is used " +"to locate a \"landmark file\" (either ``Lib\\os.py`` or ``pythonXY.zip``) to " +"deduce the \"Python Home\". If a Python home is found, the relevant sub-" +"directories added to :data:`sys.path` (``Lib``, ``plat-win``, etc) are based " +"on that folder. Otherwise, the core Python path is constructed from the " +"PythonPath stored in the registry." +msgstr "" + +#: ../Doc/using/windows.rst:765 +msgid "" +"If the Python Home cannot be located, no :envvar:`PYTHONPATH` is specified " +"in the environment, and no registry entries can be found, a default path " +"with relative entries is used (e.g. ``.\\Lib;.\\plat-win``, etc)." +msgstr "" + +#: ../Doc/using/windows.rst:769 +msgid "" +"If a ``pyvenv.cfg`` file is found alongside the main executable or in the " +"directory one level above the executable, the following variations apply:" +msgstr "" + +#: ../Doc/using/windows.rst:772 +msgid "" +"If ``home`` is an absolute path and :envvar:`PYTHONHOME` is not set, this " +"path is used instead of the path to the main executable when deducing the " +"home location." +msgstr "" + +#: ../Doc/using/windows.rst:776 +msgid "The end result of all this is:" +msgstr "" + +#: ../Doc/using/windows.rst:778 +msgid "" +"When running :file:`python.exe`, or any other .exe in the main Python " +"directory (either an installed version, or directly from the PCbuild " +"directory), the core path is deduced, and the core paths in the registry are " +"ignored. Other \"application paths\" in the registry are always read." +msgstr "" + +#: ../Doc/using/windows.rst:783 +msgid "" +"When Python is hosted in another .exe (different directory, embedded via " +"COM, etc), the \"Python Home\" will not be deduced, so the core path from " +"the registry is used. Other \"application paths\" in the registry are " +"always read." +msgstr "" + +#: ../Doc/using/windows.rst:787 +msgid "" +"If Python can't find its home and there are no registry value (frozen .exe, " +"some very strange installation setup) you get a path with some default, but " +"relative, paths." +msgstr "" + +#: ../Doc/using/windows.rst:791 +msgid "" +"For those who want to bundle Python into their application or distribution, " +"the following advice will prevent conflicts with other installations:" +msgstr "" + +#: ../Doc/using/windows.rst:794 +msgid "" +"Include a ``._pth`` file alongside your executable containing the " +"directories to include. This will ignore paths listed in the registry and " +"environment variables, and also ignore :mod:`site` unless ``import site`` is " +"listed." +msgstr "" + +#: ../Doc/using/windows.rst:799 +msgid "" +"If you are loading :file:`python3.dll` or :file:`python36.dll` in your own " +"executable, explicitly call :c:func:`Py_SetPath` or (at least) :c:func:" +"`Py_SetProgramName` before :c:func:`Py_Initialize`." +msgstr "" + +#: ../Doc/using/windows.rst:803 +msgid "" +"Clear and/or overwrite :envvar:`PYTHONPATH` and set :envvar:`PYTHONHOME` " +"before launching :file:`python.exe` from your application." +msgstr "" + +#: ../Doc/using/windows.rst:806 +msgid "" +"If you cannot use the previous suggestions (for example, you are a " +"distribution that allows people to run :file:`python.exe` directly), ensure " +"that the landmark file (:file:`Lib\\\\os.py`) exists in your install " +"directory. (Note that it will not be detected inside a ZIP file, but a " +"correctly named ZIP file will be detected instead.)" +msgstr "" + +#: ../Doc/using/windows.rst:812 +msgid "" +"These will ensure that the files in a system-wide installation will not take " +"precedence over the copy of the standard library bundled with your " +"application. Otherwise, your users may experience problems using your " +"application. Note that the first suggestion is the best, as the other may " +"still be susceptible to non-standard paths in the registry and user site-" +"packages." +msgstr "" + +#: ../Doc/using/windows.rst:821 +msgid "" +"Adds ``._pth`` file support and removes ``applocal`` option from ``pyvenv." +"cfg``." +msgstr "" + +#: ../Doc/using/windows.rst:823 +msgid "" +"Adds ``pythonXX.zip`` as a potential landmark when directly adjacent to the " +"executable." +msgstr "" + +#: ../Doc/using/windows.rst:827 +msgid "Additional modules" +msgstr "" + +#: ../Doc/using/windows.rst:829 +msgid "" +"Even though Python aims to be portable among all platforms, there are " +"features that are unique to Windows. A couple of modules, both in the " +"standard library and external, and snippets exist to use these features." +msgstr "" + +#: ../Doc/using/windows.rst:833 +msgid "" +"The Windows-specific standard modules are documented in :ref:`mswin-specific-" +"services`." +msgstr "" + +#: ../Doc/using/windows.rst:837 +msgid "PyWin32" +msgstr "" + +#: ../Doc/using/windows.rst:839 +msgid "" +"The `PyWin32 `_ module by Mark Hammond " +"is a collection of modules for advanced Windows-specific support. This " +"includes utilities for:" +msgstr "" + +#: ../Doc/using/windows.rst:843 +msgid "`Component Object Model `_ (COM)" +msgstr "" + +#: ../Doc/using/windows.rst:844 +msgid "Win32 API calls" +msgstr "" + +#: ../Doc/using/windows.rst:845 +msgid "Registry" +msgstr "" + +#: ../Doc/using/windows.rst:846 +msgid "Event log" +msgstr "" + +#: ../Doc/using/windows.rst:847 +msgid "" +"`Microsoft Foundation Classes `_ (MFC) user interfaces" +msgstr "" + +#: ../Doc/using/windows.rst:850 +msgid "" +"`PythonWin `_ is a sample MFC application shipped with PyWin32. " +"It is an embeddable IDE with a built-in debugger." +msgstr "" + +#: ../Doc/using/windows.rst:857 +msgid "" +"`Win32 How Do I...? `_" +msgstr "" + +#: ../Doc/using/windows.rst:857 +msgid "by Tim Golden" +msgstr "" + +#: ../Doc/using/windows.rst:859 +msgid "`Python and COM `_" +msgstr "" + +#: ../Doc/using/windows.rst:860 +msgid "by David and Paul Boddie" +msgstr "" + +#: ../Doc/using/windows.rst:864 +msgid "cx_Freeze" +msgstr "" + +#: ../Doc/using/windows.rst:866 +msgid "" +"`cx_Freeze `_ is a :mod:`distutils` " +"extension (see :ref:`extending-distutils`) which wraps Python scripts into " +"executable Windows programs (:file:`{*}.exe` files). When you have done " +"this, you can distribute your application without requiring your users to " +"install Python." +msgstr "" + +#: ../Doc/using/windows.rst:874 +msgid "WConio" +msgstr "" + +#: ../Doc/using/windows.rst:876 +msgid "" +"Since Python's advanced terminal handling layer, :mod:`curses`, is " +"restricted to Unix-like systems, there is a library exclusive to Windows as " +"well: Windows Console I/O for Python." +msgstr "" + +#: ../Doc/using/windows.rst:880 +msgid "" +"`WConio `_ is a wrapper " +"for Turbo-C's :file:`CONIO.H`, used to create text user interfaces." +msgstr "" + +#: ../Doc/using/windows.rst:886 +msgid "Compiling Python on Windows" +msgstr "" + +#: ../Doc/using/windows.rst:888 +msgid "" +"If you want to compile CPython yourself, first thing you should do is get " +"the `source `_. You can download " +"either the latest release's source or just grab a fresh `checkout `_." +msgstr "" + +#: ../Doc/using/windows.rst:893 +msgid "" +"The source tree contains a build solution and project files for Microsoft " +"Visual Studio 2015, which is the compiler used to build the official Python " +"releases. These files are in the :file:`PCbuild` directory." +msgstr "" + +#: ../Doc/using/windows.rst:897 +msgid "" +"Check :file:`PCbuild/readme.txt` for general information on the build " +"process." +msgstr "" + +#: ../Doc/using/windows.rst:900 +msgid "For extension modules, consult :ref:`building-on-windows`." +msgstr "" + +#: ../Doc/using/windows.rst:907 +msgid "" +"`Python + Windows + distutils + SWIG + gcc MinGW `_" +msgstr "" + +#: ../Doc/using/windows.rst:905 +msgid "" +"or \"Creating Python extensions in C/C++ with SWIG and compiling them with " +"MinGW gcc under Windows\" or \"Installing Python extension with distutils " +"and without Microsoft Visual C++\" by Sébastien Sauvage, 2003" +msgstr "" + +#: ../Doc/using/windows.rst:909 +msgid "" +"`MingW -- Python extensions `_" +msgstr "" + +#: ../Doc/using/windows.rst:910 +msgid "by Trent Apted et al, 2007" +msgstr "" + +#: ../Doc/using/windows.rst:914 +msgid "Embedded Distribution" +msgstr "" + +#: ../Doc/using/windows.rst:918 +msgid "" +"The embedded distribution is a ZIP file containing a minimal Python " +"environment. It is intended for acting as part of another application, " +"rather than being directly accessed by end-users." +msgstr "" + +#: ../Doc/using/windows.rst:922 +msgid "" +"When extracted, the embedded distribution is (almost) fully isolated from " +"the user's system, including environment variables, system registry " +"settings, and installed packages. The standard library is included as pre-" +"compiled and optimized ``.pyc`` files in a ZIP, and ``python3.dll``, " +"``python36.dll``, ``python.exe`` and ``pythonw.exe`` are all provided. Tcl/" +"tk (including all dependants, such as Idle), pip and the Python " +"documentation are not included." +msgstr "" + +#: ../Doc/using/windows.rst:931 +msgid "" +"The embedded distribution does not include the `Microsoft C Runtime `_ and it is the " +"responsibility of the application installer to provide this. The runtime may " +"have already been installed on a user's system previously or automatically " +"via Windows Update, and can be detected by finding ``ucrtbase.dll`` in the " +"system directory." +msgstr "" + +#: ../Doc/using/windows.rst:938 +msgid "" +"Third-party packages should be installed by the application installer " +"alongside the embedded distribution. Using pip to manage dependencies as for " +"a regular Python installation is not supported with this distribution, " +"though with some care it may be possible to include and use pip for " +"automatic updates. In general, third-party packages should be treated as " +"part of the application (\"vendoring\") so that the developer can ensure " +"compatibility with newer versions before providing updates to users." +msgstr "" + +#: ../Doc/using/windows.rst:946 +msgid "" +"The two recommended use cases for this distribution are described below." +msgstr "" + +#: ../Doc/using/windows.rst:949 +msgid "Python Application" +msgstr "" + +#: ../Doc/using/windows.rst:951 +msgid "" +"An application written in Python does not necessarily require users to be " +"aware of that fact. The embedded distribution may be used in this case to " +"include a private version of Python in an install package. Depending on how " +"transparent it should be (or conversely, how professional it should appear), " +"there are two options." +msgstr "" + +#: ../Doc/using/windows.rst:957 +msgid "" +"Using a specialized executable as a launcher requires some coding, but " +"provides the most transparent experience for users. With a customized " +"launcher, there are no obvious indications that the program is running on " +"Python: icons can be customized, company and version information can be " +"specified, and file associations behave properly. In most cases, a custom " +"launcher should simply be able to call ``Py_Main`` with a hard-coded command " +"line." +msgstr "" + +#: ../Doc/using/windows.rst:964 +msgid "" +"The simpler approach is to provide a batch file or generated shortcut that " +"directly calls the ``python.exe`` or ``pythonw.exe`` with the required " +"command-line arguments. In this case, the application will appear to be " +"Python and not its actual name, and users may have trouble distinguishing it " +"from other running Python processes or file associations." +msgstr "" + +#: ../Doc/using/windows.rst:970 +msgid "" +"With the latter approach, packages should be installed as directories " +"alongside the Python executable to ensure they are available on the path. " +"With the specialized launcher, packages can be located in other locations as " +"there is an opportunity to specify the search path before launching the " +"application." +msgstr "" + +#: ../Doc/using/windows.rst:976 +msgid "Embedding Python" +msgstr "" + +#: ../Doc/using/windows.rst:978 +msgid "" +"Applications written in native code often require some form of scripting " +"language, and the embedded Python distribution can be used for this purpose. " +"In general, the majority of the application is in native code, and some part " +"will either invoke ``python.exe`` or directly use ``python3.dll``. For " +"either case, extracting the embedded distribution to a subdirectory of the " +"application installation is sufficient to provide a loadable Python " +"interpreter." +msgstr "" + +#: ../Doc/using/windows.rst:985 +msgid "" +"As with the application use, packages can be installed to any location as " +"there is an opportunity to specify search paths before initializing the " +"interpreter. Otherwise, there is no fundamental differences between using " +"the embedded distribution and a regular installation." +msgstr "" + +#: ../Doc/using/windows.rst:991 +msgid "Other resources" +msgstr "" + +#: ../Doc/using/windows.rst:998 +msgid "" +"`Python Programming On Win32 `_" +msgstr "" + +#: ../Doc/using/windows.rst:996 +msgid "" +"\"Help for Windows Programmers\" by Mark Hammond and Andy Robinson, O'Reilly " +"Media, 2000, ISBN 1-56592-621-8" +msgstr "" + +#: ../Doc/using/windows.rst:1001 +msgid "" +"`A Python for Windows Tutorial `_" +msgstr "" + +#: ../Doc/using/windows.rst:1001 +msgid "by Amanda Birmingham, 2004" +msgstr "" + +#: ../Doc/using/windows.rst:1003 +msgid ":pep:`397` - Python launcher for Windows" +msgstr "" + +#: ../Doc/using/windows.rst:1004 +msgid "" +"The proposal for the launcher to be included in the Python distribution." +msgstr "" diff --git a/whatsnew.po b/whatsnew.po new file mode 100644 index 00000000..857fa3af --- /dev/null +++ b/whatsnew.po @@ -0,0 +1,55182 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) 2001-2016, Python Software Foundation +# This file is distributed under the same license as the Python package. +# FIRST AUTHOR , 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 \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../Doc/whatsnew/2.0.rst:3 +msgid "What's New in Python 2.0" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:5 +msgid "A.M. Kuchling and Moshe Zadka" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:13 ../Doc/whatsnew/2.1.rst:13 +#: ../Doc/whatsnew/2.2.rst:13 +msgid "Introduction" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:15 +msgid "" +"A new release of Python, version 2.0, was released on October 16, 2000. This " +"article covers the exciting new features in 2.0, highlights some other " +"useful changes, and points out a few incompatible changes that may require " +"rewriting code." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:20 +msgid "" +"Python's development never completely stops between releases, and a steady " +"flow of bug fixes and improvements are always being submitted. A host of " +"minor fixes, a few optimizations, additional docstrings, and better error " +"messages went into 2.0; to list them all would be impossible, but they're " +"certainly significant. Consult the publicly-available CVS logs if you want " +"to see the full list. This progress is due to the five developers working " +"for PythonLabs are now getting paid to spend their days fixing bugs, and " +"also due to the improved communication resulting from moving to SourceForge." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:33 +msgid "What About Python 1.6?" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:35 +msgid "" +"Python 1.6 can be thought of as the Contractual Obligations Python release. " +"After the core development team left CNRI in May 2000, CNRI requested that a " +"1.6 release be created, containing all the work on Python that had been " +"performed at CNRI. Python 1.6 therefore represents the state of the CVS " +"tree as of May 2000, with the most significant new feature being Unicode " +"support. Development continued after May, of course, so the 1.6 tree " +"received a few fixes to ensure that it's forward-compatible with Python " +"2.0. 1.6 is therefore part of Python's evolution, and not a side branch." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:44 +msgid "" +"So, should you take much interest in Python 1.6? Probably not. The " +"1.6final and 2.0beta1 releases were made on the same day (September 5, " +"2000), the plan being to finalize Python 2.0 within a month or so. If you " +"have applications to maintain, there seems little point in breaking things " +"by moving to 1.6, fixing them, and then having another round of breakage " +"within a month by moving to 2.0; you're better off just going straight to " +"2.0. Most of the really interesting features described in this document are " +"only in 2.0, because a lot of work was done between May and September." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:57 +msgid "New Development Process" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:59 +msgid "" +"The most important change in Python 2.0 may not be to the code at all, but " +"to how Python is developed: in May 2000 the Python developers began using " +"the tools made available by SourceForge for storing source code, tracking " +"bug reports, and managing the queue of patch submissions. To report bugs or " +"submit patches for Python 2.0, use the bug tracking and patch manager tools " +"available from Python's project page, located at https://sourceforge.net/" +"projects/python/." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:66 +msgid "" +"The most important of the services now hosted at SourceForge is the Python " +"CVS tree, the version-controlled repository containing the source code for " +"Python. Previously, there were roughly 7 or so people who had write access " +"to the CVS tree, and all patches had to be inspected and checked in by one " +"of the people on this short list. Obviously, this wasn't very scalable. By " +"moving the CVS tree to SourceForge, it became possible to grant write access " +"to more people; as of September 2000 there were 27 people able to check in " +"changes, a fourfold increase. This makes possible large-scale changes that " +"wouldn't be attempted if they'd have to be filtered through the small group " +"of core developers. For example, one day Peter Schneider-Kamp took it into " +"his head to drop K&R C compatibility and convert the C source for Python to " +"ANSI C. After getting approval on the python-dev mailing list, he launched " +"into a flurry of checkins that lasted about a week, other developers joined " +"in to help, and the job was done. If there were only 5 people with write " +"access, probably that task would have been viewed as \"nice, but not worth " +"the time and effort needed\" and it would never have gotten done." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:83 +msgid "" +"The shift to using SourceForge's services has resulted in a remarkable " +"increase in the speed of development. Patches now get submitted, commented " +"on, revised by people other than the original submitter, and bounced back " +"and forth between people until the patch is deemed worth checking in. Bugs " +"are tracked in one central location and can be assigned to a specific person " +"for fixing, and we can count the number of open bugs to measure progress. " +"This didn't come without a cost: developers now have more e-mail to deal " +"with, more mailing lists to follow, and special tools had to be written for " +"the new environment. For example, SourceForge sends default patch and bug " +"notification e-mail messages that are completely unhelpful, so Ka-Ping Yee " +"wrote an HTML screen-scraper that sends more useful messages." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:95 +msgid "" +"The ease of adding code caused a few initial growing pains, such as code was " +"checked in before it was ready or without getting clear agreement from the " +"developer group. The approval process that has emerged is somewhat similar " +"to that used by the Apache group. Developers can vote +1, +0, -0, or -1 on a " +"patch; +1 and -1 denote acceptance or rejection, while +0 and -0 mean the " +"developer is mostly indifferent to the change, though with a slight positive " +"or negative slant. The most significant change from the Apache model is " +"that the voting is essentially advisory, letting Guido van Rossum, who has " +"Benevolent Dictator For Life status, know what the general opinion is. He " +"can still ignore the result of a vote, and approve or reject a change even " +"if the community disagrees with him." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:106 +msgid "" +"Producing an actual patch is the last step in adding a new feature, and is " +"usually easy compared to the earlier task of coming up with a good design. " +"Discussions of new features can often explode into lengthy mailing list " +"threads, making the discussion hard to follow, and no one can read every " +"posting to python-dev. Therefore, a relatively formal process has been set " +"up to write Python Enhancement Proposals (PEPs), modelled on the Internet " +"RFC process. PEPs are draft documents that describe a proposed new feature, " +"and are continually revised until the community reaches a consensus, either " +"accepting or rejecting the proposal. Quoting from the introduction to PEP " +"1, \"PEP Purpose and Guidelines\":" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:120 +msgid "" +"PEP stands for Python Enhancement Proposal. A PEP is a design document " +"providing information to the Python community, or describing a new feature " +"for Python. The PEP should provide a concise technical specification of the " +"feature and a rationale for the feature." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:125 +msgid "" +"We intend PEPs to be the primary mechanisms for proposing new features, for " +"collecting community input on an issue, and for documenting the design " +"decisions that have gone into Python. The PEP author is responsible for " +"building consensus within the community and documenting dissenting opinions." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:130 +msgid "" +"Read the rest of PEP 1 for the details of the PEP editorial process, style, " +"and format. PEPs are kept in the Python CVS tree on SourceForge, though " +"they're not part of the Python 2.0 distribution, and are also available in " +"HTML form from https://www.python.org/dev/peps/. As of September 2000, " +"there are 25 PEPS, ranging from PEP 201, \"Lockstep Iteration\", to PEP 225, " +"\"Elementwise/Objectwise Operators\"." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:141 ../Doc/whatsnew/3.2.rst:2412 +msgid "Unicode" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:143 +msgid "" +"The largest new feature in Python 2.0 is a new fundamental data type: " +"Unicode strings. Unicode uses 16-bit numbers to represent characters " +"instead of the 8-bit number used by ASCII, meaning that 65,536 distinct " +"characters can be supported." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:148 +msgid "" +"The final interface for Unicode support was arrived at through countless " +"often- stormy discussions on the python-dev mailing list, and mostly " +"implemented by Marc-André Lemburg, based on a Unicode string type " +"implementation by Fredrik Lundh. A detailed explanation of the interface " +"was written up as :pep:`100`, \"Python Unicode Integration\". This article " +"will simply cover the most significant points about the Unicode interfaces." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:155 +msgid "" +"In Python source code, Unicode strings are written as ``u\"string\"``. " +"Arbitrary Unicode characters can be written using a new escape sequence, ``" +"\\uHHHH``, where *HHHH* is a 4-digit hexadecimal number from 0000 to FFFF. " +"The existing ``\\xHHHH`` escape sequence can also be used, and octal escapes " +"can be used for characters up to U+01FF, which is represented by ``\\777``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:161 +msgid "" +"Unicode strings, just like regular strings, are an immutable sequence type. " +"They can be indexed and sliced, but not modified in place. Unicode strings " +"have an ``encode( [encoding] )`` method that returns an 8-bit string in the " +"desired encoding. Encodings are named by strings, such as ``'ascii'``, " +"``'utf-8'``, ``'iso-8859-1'``, or whatever. A codec API is defined for " +"implementing and registering new encodings that are then available " +"throughout a Python program. If an encoding isn't specified, the default " +"encoding is usually 7-bit ASCII, though it can be changed for your Python " +"installation by calling the ``sys.setdefaultencoding(encoding)`` function in " +"a customized version of :file:`site.py`." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:172 +msgid "" +"Combining 8-bit and Unicode strings always coerces to Unicode, using the " +"default ASCII encoding; the result of ``'a' + u'bc'`` is ``u'abc'``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:175 +msgid "" +"New built-in functions have been added, and existing built-ins modified to " +"support Unicode:" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:178 +msgid "" +"``unichr(ch)`` returns a Unicode string 1 character long, containing the " +"character *ch*." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:181 +msgid "" +"``ord(u)``, where *u* is a 1-character regular or Unicode string, returns " +"the number of the character as an integer." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:184 +msgid "" +"``unicode(string [, encoding] [, errors] )`` creates a Unicode string from " +"an 8-bit string. ``encoding`` is a string naming the encoding to use. The " +"``errors`` parameter specifies the treatment of characters that are invalid " +"for the current encoding; passing ``'strict'`` as the value causes an " +"exception to be raised on any encoding error, while ``'ignore'`` causes " +"errors to be silently ignored and ``'replace'`` uses U+FFFD, the official " +"replacement character, in case of any problems." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:192 +msgid "" +"The ``exec`` statement, and various built-ins such as ``eval()``, " +"``getattr()``, and ``setattr()`` will also accept Unicode strings as well as " +"regular strings. (It's possible that the process of fixing this missed some " +"built-ins; if you find a built-in function that accepts strings but doesn't " +"accept Unicode strings at all, please report it as a bug.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:198 +msgid "" +"A new module, :mod:`unicodedata`, provides an interface to Unicode character " +"properties. For example, ``unicodedata.category(u'A')`` returns the 2-" +"character string 'Lu', the 'L' denoting it's a letter, and 'u' meaning that " +"it's uppercase. ``unicodedata.bidirectional(u'\\u0660')`` returns 'AN', " +"meaning that U+0660 is an Arabic number." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:204 +msgid "" +"The :mod:`codecs` module contains functions to look up existing encodings " +"and register new ones. Unless you want to implement a new encoding, you'll " +"most often use the ``codecs.lookup(encoding)`` function, which returns a 4-" +"element tuple: ``(encode_func, decode_func, stream_reader, stream_writer)``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:209 +msgid "" +"*encode_func* is a function that takes a Unicode string, and returns a 2-" +"tuple ``(string, length)``. *string* is an 8-bit string containing a " +"portion (perhaps all) of the Unicode string converted into the given " +"encoding, and *length* tells you how much of the Unicode string was " +"converted." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:214 +msgid "" +"*decode_func* is the opposite of *encode_func*, taking an 8-bit string and " +"returning a 2-tuple ``(ustring, length)``, consisting of the resulting " +"Unicode string *ustring* and the integer *length* telling how much of the 8-" +"bit string was consumed." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:219 +msgid "" +"*stream_reader* is a class that supports decoding input from a stream. " +"*stream_reader(file_obj)* returns an object that supports the :meth:`read`, :" +"meth:`readline`, and :meth:`readlines` methods. These methods will all " +"translate from the given encoding and return Unicode strings." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:224 +msgid "" +"*stream_writer*, similarly, is a class that supports encoding output to a " +"stream. *stream_writer(file_obj)* returns an object that supports the :meth:" +"`write` and :meth:`writelines` methods. These methods expect Unicode " +"strings, translating them to the given encoding on output." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:229 +msgid "" +"For example, the following code writes a Unicode string into a file, " +"encoding it as UTF-8::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:243 +msgid "The following code would then read UTF-8 input from the file::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:249 +msgid "" +"Unicode-aware regular expressions are available through the :mod:`re` " +"module, which has a new underlying implementation called SRE written by " +"Fredrik Lundh of Secret Labs AB." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:253 +msgid "" +"A ``-U`` command line option was added which causes the Python compiler to " +"interpret all string literals as Unicode string literals. This is intended " +"to be used in testing and future-proofing your Python code, since some " +"future version of Python may drop support for 8-bit strings and provide only " +"Unicode strings." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:262 +msgid "List Comprehensions" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:264 +msgid "" +"Lists are a workhorse data type in Python, and many programs manipulate a " +"list at some point. Two common operations on lists are to loop over them, " +"and either pick out the elements that meet a certain criterion, or apply " +"some function to each element. For example, given a list of strings, you " +"might want to pull out all the strings containing a given substring, or " +"strip off trailing whitespace from each line." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:271 +msgid "" +"The existing :func:`map` and :func:`filter` functions can be used for this " +"purpose, but they require a function as one of their arguments. This is " +"fine if there's an existing built-in function that can be passed directly, " +"but if there isn't, you have to create a little function to do the required " +"work, and Python's scoping rules make the result ugly if the little function " +"needs additional information. Take the first example in the previous " +"paragraph, finding all the strings in the list containing a given " +"substring. You could write the following to do it::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:286 +msgid "" +"Because of Python's scoping rules, a default argument is used so that the " +"anonymous function created by the :keyword:`lambda` statement knows what " +"substring is being searched for. List comprehensions make this cleaner::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:292 +msgid "List comprehensions have the form::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:299 +msgid "" +"The :keyword:`for`...\\ :keyword:`in` clauses contain the sequences to be " +"iterated over. The sequences do not have to be the same length, because " +"they are *not* iterated over in parallel, but from left to right; this is " +"explained more clearly in the following paragraphs. The elements of the " +"generated list will be the successive values of *expression*. The final :" +"keyword:`if` clause is optional; if present, *expression* is only evaluated " +"and added to the result if *condition* is true." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:307 +msgid "" +"To make the semantics very clear, a list comprehension is equivalent to the " +"following Python code::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:319 +msgid "" +"This means that when there are multiple :keyword:`for`...\\ :keyword:`in` " +"clauses, the resulting list will be equal to the product of the lengths of " +"all the sequences. If you have two lists of length 3, the output list is 9 " +"elements long::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:330 +msgid "" +"To avoid introducing an ambiguity into Python's grammar, if *expression* is " +"creating a tuple, it must be surrounded with parentheses. The first list " +"comprehension below is a syntax error, while the second one is correct::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:339 +msgid "" +"The idea of list comprehensions originally comes from the functional " +"programming language Haskell (https://www.haskell.org). Greg Ewing argued " +"most effectively for adding them to Python and wrote the initial list " +"comprehension patch, which was then discussed for a seemingly endless time " +"on the python-dev mailing list and kept up-to-date by Skip Montanaro." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:349 +msgid "Augmented Assignment" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:351 +msgid "" +"Augmented assignment operators, another long-requested feature, have been " +"added to Python 2.0. Augmented assignment operators include ``+=``, ``-=``, " +"``*=``, and so forth. For example, the statement ``a += 2`` increments the " +"value of the variable ``a`` by 2, equivalent to the slightly lengthier ``a " +"= a + 2``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:356 +msgid "" +"The full list of supported assignment operators is ``+=``, ``-=``, ``*=``, " +"``/=``, ``%=``, ``**=``, ``&=``, ``|=``, ``^=``, ``>>=``, and ``<<=``. " +"Python classes can override the augmented assignment operators by defining " +"methods named :meth:`__iadd__`, :meth:`__isub__`, etc. For example, the " +"following :class:`Number` class stores a number and supports using += to " +"create a new instance with an incremented value." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:377 +msgid "" +"The :meth:`__iadd__` special method is called with the value of the " +"increment, and should return a new instance with an appropriately modified " +"value; this return value is bound as the new value of the variable on the " +"left-hand side." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:381 +msgid "" +"Augmented assignment operators were first introduced in the C programming " +"language, and most C-derived languages, such as :program:`awk`, C++, Java, " +"Perl, and PHP also support them. The augmented assignment patch was " +"implemented by Thomas Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:390 +msgid "String Methods" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:392 +msgid "" +"Until now string-manipulation functionality was in the :mod:`string` module, " +"which was usually a front-end for the :mod:`strop` module written in C. The " +"addition of Unicode posed a difficulty for the :mod:`strop` module, because " +"the functions would all need to be rewritten in order to accept either 8-bit " +"or Unicode strings. For functions such as :func:`string.replace`, which " +"takes 3 string arguments, that means eight possible permutations, and " +"correspondingly complicated code." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:400 +msgid "" +"Instead, Python 2.0 pushes the problem onto the string type, making string " +"manipulation functionality available through methods on both 8-bit strings " +"and Unicode strings. ::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:411 +msgid "" +"One thing that hasn't changed, a noteworthy April Fools' joke " +"notwithstanding, is that Python strings are immutable. Thus, the string " +"methods return new strings, and do not modify the string on which they " +"operate." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:415 +msgid "" +"The old :mod:`string` module is still around for backwards compatibility, " +"but it mostly acts as a front-end to the new string methods." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:418 +msgid "" +"Two methods which have no parallel in pre-2.0 versions, although they did " +"exist in JPython for quite some time, are :meth:`startswith` and :meth:" +"`endswith`. ``s.startswith(t)`` is equivalent to ``s[:len(t)] == t``, while " +"``s.endswith(t)`` is equivalent to ``s[-len(t):] == t``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:423 +msgid "" +"One other method which deserves special mention is :meth:`join`. The :meth:" +"`join` method of a string receives one parameter, a sequence of strings, and " +"is equivalent to the :func:`string.join` function from the old :mod:`string` " +"module, with the arguments reversed. In other words, ``s.join(seq)`` is " +"equivalent to the old ``string.join(seq, s)``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:433 +msgid "Garbage Collection of Cycles" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:435 +msgid "" +"The C implementation of Python uses reference counting to implement garbage " +"collection. Every Python object maintains a count of the number of " +"references pointing to itself, and adjusts the count as references are " +"created or destroyed. Once the reference count reaches zero, the object is " +"no longer accessible, since you need to have a reference to an object to " +"access it, and if the count is zero, no references exist any longer." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:442 +msgid "" +"Reference counting has some pleasant properties: it's easy to understand and " +"implement, and the resulting implementation is portable, fairly fast, and " +"reacts well with other libraries that implement their own memory handling " +"schemes. The major problem with reference counting is that it sometimes " +"doesn't realise that objects are no longer accessible, resulting in a memory " +"leak. This happens when there are cycles of references." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:449 +msgid "" +"Consider the simplest possible cycle, a class instance which has a " +"reference to itself::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:455 +msgid "" +"After the above two lines of code have been executed, the reference count of " +"``instance`` is 2; one reference is from the variable named ``'instance'``, " +"and the other is from the ``myself`` attribute of the instance." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:459 +msgid "" +"If the next line of code is ``del instance``, what happens? The reference " +"count of ``instance`` is decreased by 1, so it has a reference count of 1; " +"the reference in the ``myself`` attribute still exists. Yet the instance is " +"no longer accessible through Python code, and it could be deleted. Several " +"objects can participate in a cycle if they have references to each other, " +"causing all of the objects to be leaked." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:466 +msgid "" +"Python 2.0 fixes this problem by periodically executing a cycle detection " +"algorithm which looks for inaccessible cycles and deletes the objects " +"involved. A new :mod:`gc` module provides functions to perform a garbage " +"collection, obtain debugging statistics, and tuning the collector's " +"parameters." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:471 +msgid "" +"Running the cycle detection algorithm takes some time, and therefore will " +"result in some additional overhead. It is hoped that after we've gotten " +"experience with the cycle collection from using 2.0, Python 2.1 will be able " +"to minimize the overhead with careful tuning. It's not yet obvious how much " +"performance is lost, because benchmarking this is tricky and depends " +"crucially on how often the program creates and destroys objects. The " +"detection of cycles can be disabled when Python is compiled, if you can't " +"afford even a tiny speed penalty or suspect that the cycle collection is " +"buggy, by specifying the :option:`--without-cycle-gc` switch when running " +"the :program:`configure` script." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:482 +msgid "" +"Several people tackled this problem and contributed to a solution. An early " +"implementation of the cycle detection approach was written by Toby Kelsey. " +"The current algorithm was suggested by Eric Tiedemann during a visit to " +"CNRI, and Guido van Rossum and Neil Schemenauer wrote two different " +"implementations, which were later integrated by Neil. Lots of other people " +"offered suggestions along the way; the March 2000 archives of the python-dev " +"mailing list contain most of the relevant discussion, especially in the " +"threads titled \"Reference cycle collection for Python\" and \"Finalization " +"again\"." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:495 +msgid "Other Core Changes" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:497 +msgid "" +"Various minor changes have been made to Python's syntax and built-in " +"functions. None of the changes are very far-reaching, but they're handy " +"conveniences." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:502 +msgid "Minor Language Changes" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:504 +msgid "" +"A new syntax makes it more convenient to call a given function with a tuple " +"of arguments and/or a dictionary of keyword arguments. In Python 1.5 and " +"earlier, you'd use the :func:`apply` built-in function: ``apply(f, args, " +"kw)`` calls the function :func:`f` with the argument tuple *args* and the " +"keyword arguments in the dictionary *kw*. :func:`apply` is the same in " +"2.0, but thanks to a patch from Greg Ewing, ``f(*args, **kw)`` is a shorter " +"and clearer way to achieve the same effect. This syntax is symmetrical with " +"the syntax for defining functions::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:518 +msgid "" +"The ``print`` statement can now have its output directed to a file-like " +"object by following the ``print`` with ``>> file``, similar to the " +"redirection operator in Unix shells. Previously you'd either have to use " +"the :meth:`write` method of the file-like object, which lacks the " +"convenience and simplicity of ``print``, or you could assign a new value to " +"``sys.stdout`` and then restore the old value. For sending output to " +"standard error, it's much easier to write this::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:528 +msgid "" +"Modules can now be renamed on importing them, using the syntax ``import " +"module as name`` or ``from module import name as othername``. The patch was " +"submitted by Thomas Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:532 +msgid "" +"A new format style is available when using the ``%`` operator; '%r' will " +"insert the :func:`repr` of its argument. This was also added from symmetry " +"considerations, this time for symmetry with the existing '%s' format style, " +"which inserts the :func:`str` of its argument. For example, ``'%r %s' % " +"('abc', 'abc')`` returns a string containing ``'abc' abc``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:538 +msgid "" +"Previously there was no way to implement a class that overrode Python's " +"built-in :keyword:`in` operator and implemented a custom version. ``obj in " +"seq`` returns true if *obj* is present in the sequence *seq*; Python " +"computes this by simply trying every index of the sequence until either " +"*obj* is found or an :exc:`IndexError` is encountered. Moshe Zadka " +"contributed a patch which adds a :meth:`__contains__` magic method for " +"providing a custom implementation for :keyword:`in`. Additionally, new built-" +"in objects written in C can define what :keyword:`in` means for them via a " +"new slot in the sequence protocol." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:547 +msgid "" +"Earlier versions of Python used a recursive algorithm for deleting objects. " +"Deeply nested data structures could cause the interpreter to fill up the C " +"stack and crash; Christian Tismer rewrote the deletion logic to fix this " +"problem. On a related note, comparing recursive objects recursed infinitely " +"and crashed; Jeremy Hylton rewrote the code to no longer crash, producing a " +"useful result instead. For example, after this code::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:559 +msgid "" +"The comparison ``a==b`` returns true, because the two recursive data " +"structures are isomorphic. See the thread \"trashcan and PR#7\" in the April " +"2000 archives of the python-dev mailing list for the discussion leading up " +"to this implementation, and some useful relevant links. Note that " +"comparisons can now also raise exceptions. In earlier versions of Python, a " +"comparison operation such as ``cmp(a,b)`` would always produce an answer, " +"even if a user-defined :meth:`__cmp__` method encountered an error, since " +"the resulting exception would simply be silently swallowed." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:571 +msgid "" +"Work has been done on porting Python to 64-bit Windows on the Itanium " +"processor, mostly by Trent Mick of ActiveState. (Confusingly, ``sys." +"platform`` is still ``'win32'`` on Win64 because it seems that for ease of " +"porting, MS Visual C++ treats code as 32 bit on Itanium.) PythonWin also " +"supports Windows CE; see the Python CE page at http://pythonce.sourceforge." +"net/ for more information." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:577 +msgid "" +"Another new platform is Darwin/MacOS X; initial support for it is in Python " +"2.0. Dynamic loading works, if you specify \"configure --with-dyld --with-" +"suffix=.x\". Consult the README in the Python source distribution for more " +"instructions." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:581 +msgid "" +"An attempt has been made to alleviate one of Python's warts, the often-" +"confusing :exc:`NameError` exception when code refers to a local variable " +"before the variable has been assigned a value. For example, the following " +"code raises an exception on the ``print`` statement in both 1.5.2 and 2.0; " +"in 1.5.2 a :exc:`NameError` exception is raised, while 2.0 raises a new :exc:" +"`UnboundLocalError` exception. :exc:`UnboundLocalError` is a subclass of :" +"exc:`NameError`, so any existing code that expects :exc:`NameError` to be " +"raised should still work. ::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:595 +msgid "" +"Two new exceptions, :exc:`TabError` and :exc:`IndentationError`, have been " +"introduced. They're both subclasses of :exc:`SyntaxError`, and are raised " +"when Python code is found to be improperly indented." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:601 +msgid "Changes to Built-in Functions" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:603 +msgid "" +"A new built-in, ``zip(seq1, seq2, ...)``, has been added. :func:`zip` " +"returns a list of tuples where each tuple contains the i-th element from " +"each of the argument sequences. The difference between :func:`zip` and " +"``map(None, seq1, seq2)`` is that :func:`map` pads the sequences with " +"``None`` if the sequences aren't all of the same length, while :func:`zip` " +"truncates the returned list to the length of the shortest argument sequence." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:610 +msgid "" +"The :func:`int` and :func:`long` functions now accept an optional \"base\" " +"parameter when the first argument is a string. ``int('123', 10)`` returns " +"123, while ``int('123', 16)`` returns 291. ``int(123, 16)`` raises a :exc:" +"`TypeError` exception with the message \"can't convert non-string with " +"explicit base\"." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:616 +msgid "" +"A new variable holding more detailed version information has been added to " +"the :mod:`sys` module. ``sys.version_info`` is a tuple ``(major, minor, " +"micro, level, serial)`` For example, in a hypothetical 2.0.1beta1, ``sys." +"version_info`` would be ``(2, 0, 1, 'beta', 1)``. *level* is a string such " +"as ``\"alpha\"``, ``\"beta\"``, or ``\"final\"`` for a final release." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:622 +msgid "" +"Dictionaries have an odd new method, ``setdefault(key, default)``, which " +"behaves similarly to the existing :meth:`get` method. However, if the key " +"is missing, :meth:`setdefault` both returns the value of *default* as :meth:" +"`get` would do, and also inserts it into the dictionary as the value for " +"*key*. Thus, the following lines of code::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:633 +msgid "" +"can be reduced to a single ``return dict.setdefault(key, [])`` statement." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:635 +msgid "" +"The interpreter sets a maximum recursion depth in order to catch runaway " +"recursion before filling the C stack and causing a core dump or GPF.. " +"Previously this limit was fixed when you compiled Python, but in 2.0 the " +"maximum recursion depth can be read and modified using :func:`sys." +"getrecursionlimit` and :func:`sys.setrecursionlimit`. The default value is " +"1000, and a rough maximum value for a given platform can be found by running " +"a new script, :file:`Misc/find_recursionlimit.py`." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:647 +msgid "Porting to 2.0" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:649 +msgid "" +"New Python releases try hard to be compatible with previous releases, and " +"the record has been pretty good. However, some changes are considered " +"useful enough, usually because they fix initial design decisions that turned " +"out to be actively mistaken, that breaking backward compatibility can't " +"always be avoided. This section lists the changes in Python 2.0 that may " +"cause old Python code to break." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:656 +msgid "" +"The change which will probably break the most code is tightening up the " +"arguments accepted by some methods. Some methods would take multiple " +"arguments and treat them as a tuple, particularly various list methods such " +"as :meth:`append` and :meth:`insert`. In earlier versions of Python, if " +"``L`` is a list, ``L.append( 1,2 )`` appends the tuple ``(1,2)`` to the " +"list. In Python 2.0 this causes a :exc:`TypeError` exception to be raised, " +"with the message: 'append requires exactly 1 argument; 2 given'. The fix is " +"to simply add an extra set of parentheses to pass both values as a tuple: " +"``L.append( (1,2) )``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:665 +msgid "" +"The earlier versions of these methods were more forgiving because they used " +"an old function in Python's C interface to parse their arguments; 2.0 " +"modernizes them to use :func:`PyArg_ParseTuple`, the current argument " +"parsing function, which provides more helpful error messages and treats " +"multi-argument calls as errors. If you absolutely must use 2.0 but can't " +"fix your code, you can edit :file:`Objects/listobject.c` and define the " +"preprocessor symbol ``NO_STRICT_LIST_APPEND`` to preserve the old behaviour; " +"this isn't recommended." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:673 +msgid "" +"Some of the functions in the :mod:`socket` module are still forgiving in " +"this way. For example, :func:`socket.connect( ('hostname', 25) )` is the " +"correct form, passing a tuple representing an IP address, but :func:`socket." +"connect( 'hostname', 25 )` also works. :func:`socket.connect_ex` and :func:" +"`socket.bind` are similarly easy-going. 2.0alpha1 tightened these functions " +"up, but because the documentation actually used the erroneous multiple " +"argument form, many people wrote code which would break with the stricter " +"checking. GvR backed out the changes in the face of public reaction, so for " +"the :mod:`socket` module, the documentation was fixed and the multiple " +"argument form is simply marked as deprecated; it *will* be tightened up " +"again in a future Python version." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:684 +msgid "" +"The ``\\x`` escape in string literals now takes exactly 2 hex digits. " +"Previously it would consume all the hex digits following the 'x' and take " +"the lowest 8 bits of the result, so ``\\x123456`` was equivalent to ``" +"\\x56``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:688 +msgid "" +"The :exc:`AttributeError` and :exc:`NameError` exceptions have a more " +"friendly error message, whose text will be something like ``'Spam' instance " +"has no attribute 'eggs'`` or ``name 'eggs' is not defined``. Previously the " +"error message was just the missing attribute name ``eggs``, and code written " +"to take advantage of this fact will break in 2.0." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:694 +msgid "" +"Some work has been done to make integers and long integers a bit more " +"interchangeable. In 1.5.2, large-file support was added for Solaris, to " +"allow reading files larger than 2 GiB; this made the :meth:`tell` method of " +"file objects return a long integer instead of a regular integer. Some code " +"would subtract two file offsets and attempt to use the result to multiply a " +"sequence or slice a string, but this raised a :exc:`TypeError`. In 2.0, " +"long integers can be used to multiply or slice a sequence, and it'll behave " +"as you'd intuitively expect it to; ``3L * 'abc'`` produces 'abcabcabc', and " +"``(0,1,2,3)[2L:4L]`` produces (2,3). Long integers can also be used in " +"various contexts where previously only integers were accepted, such as in " +"the :meth:`seek` method of file objects, and in the formats supported by the " +"``%`` operator (``%d``, ``%i``, ``%x``, etc.). For example, ``\"%d\" % " +"2L**64`` will produce the string ``18446744073709551616``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:708 +msgid "" +"The subtlest long integer change of all is that the :func:`str` of a long " +"integer no longer has a trailing 'L' character, though :func:`repr` still " +"includes it. The 'L' annoyed many people who wanted to print long integers " +"that looked just like regular integers, since they had to go out of their " +"way to chop off the character. This is no longer a problem in 2.0, but code " +"which does ``str(longval)[:-1]`` and assumes the 'L' is there, will now lose " +"the final digit." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:716 +msgid "" +"Taking the :func:`repr` of a float now uses a different formatting precision " +"than :func:`str`. :func:`repr` uses ``%.17g`` format string for C's :func:" +"`sprintf`, while :func:`str` uses ``%.12g`` as before. The effect is that :" +"func:`repr` may occasionally show more decimal places than :func:`str`, for " +"certain numbers. For example, the number 8.1 can't be represented exactly " +"in binary, so ``repr(8.1)`` is ``'8.0999999999999996'``, while str(8.1) is " +"``'8.1'``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:724 +msgid "" +"The ``-X`` command-line option, which turned all standard exceptions into " +"strings instead of classes, has been removed; the standard exceptions will " +"now always be classes. The :mod:`exceptions` module containing the standard " +"exceptions was translated from Python to a built-in C module, written by " +"Barry Warsaw and Fredrik Lundh." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:740 +msgid "Extending/Embedding Changes" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:742 +msgid "" +"Some of the changes are under the covers, and will only be apparent to " +"people writing C extension modules or embedding a Python interpreter in a " +"larger application. If you aren't dealing with Python's C API, you can " +"safely skip this section." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:747 +msgid "" +"The version number of the Python C API was incremented, so C extensions " +"compiled for 1.5.2 must be recompiled in order to work with 2.0. On " +"Windows, it's not possible for Python 2.0 to import a third party extension " +"built for Python 1.5.x due to how Windows DLLs work, so Python will raise an " +"exception and the import will fail." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:753 +msgid "" +"Users of Jim Fulton's ExtensionClass module will be pleased to find out that " +"hooks have been added so that ExtensionClasses are now supported by :func:" +"`isinstance` and :func:`issubclass`. This means you no longer have to " +"remember to write code such as ``if type(obj) == myExtensionClass``, but can " +"use the more natural ``if isinstance(obj, myExtensionClass)``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:759 +msgid "" +"The :file:`Python/importdl.c` file, which was a mass of #ifdefs to support " +"dynamic loading on many different platforms, was cleaned up and reorganised " +"by Greg Stein. :file:`importdl.c` is now quite small, and platform-specific " +"code has been moved into a bunch of :file:`Python/dynload_\\*.c` files. " +"Another cleanup: there were also a number of :file:`my\\*.h` files in the " +"Include/ directory that held various portability hacks; they've been merged " +"into a single file, :file:`Include/pyport.h`." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:767 +msgid "" +"Vladimir Marangozov's long-awaited malloc restructuring was completed, to " +"make it easy to have the Python interpreter use a custom allocator instead " +"of C's standard :func:`malloc`. For documentation, read the comments in :" +"file:`Include/pymem.h` and :file:`Include/objimpl.h`. For the lengthy " +"discussions during which the interface was hammered out, see the Web " +"archives of the 'patches' and 'python-dev' lists at python.org." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:774 +msgid "" +"Recent versions of the GUSI development environment for MacOS support POSIX " +"threads. Therefore, Python's POSIX threading support now works on the " +"Macintosh. Threading support using the user-space GNU ``pth`` library was " +"also contributed." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:779 +msgid "" +"Threading support on Windows was enhanced, too. Windows supports thread " +"locks that use kernel objects only in case of contention; in the common case " +"when there's no contention, they use simpler functions which are an order of " +"magnitude faster. A threaded version of Python 1.5.2 on NT is twice as slow " +"as an unthreaded version; with the 2.0 changes, the difference is only 10%. " +"These improvements were contributed by Yakov Markovitch." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:786 +msgid "" +"Python 2.0's source now uses only ANSI C prototypes, so compiling Python now " +"requires an ANSI C compiler, and can no longer be done using a compiler that " +"only supports K&R C." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:790 +msgid "" +"Previously the Python virtual machine used 16-bit numbers in its bytecode, " +"limiting the size of source files. In particular, this affected the maximum " +"size of literal lists and dictionaries in Python source; occasionally people " +"who are generating Python code would run into this limit. A patch by " +"Charles G. Waldman raises the limit from ``2^16`` to ``2^{32}``." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:796 +msgid "" +"Three new convenience functions intended for adding constants to a module's " +"dictionary at module initialization time were added: :func:" +"`PyModule_AddObject`, :func:`PyModule_AddIntConstant`, and :func:" +"`PyModule_AddStringConstant`. Each of these functions takes a module " +"object, a null-terminated C string containing the name to be added, and a " +"third argument for the value to be assigned to the name. This third " +"argument is, respectively, a Python object, a C long, or a C string." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:804 +msgid "" +"A wrapper API was added for Unix-style signal handlers. :func:`PyOS_getsig` " +"gets a signal handler and :func:`PyOS_setsig` will set a new handler." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:811 +msgid "Distutils: Making Modules Easy to Install" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:813 +msgid "" +"Before Python 2.0, installing modules was a tedious affair -- there was no " +"way to figure out automatically where Python is installed, or what compiler " +"options to use for extension modules. Software authors had to go through an " +"arduous ritual of editing Makefiles and configuration files, which only " +"really work on Unix and leave Windows and MacOS unsupported. Python users " +"faced wildly differing installation instructions which varied between " +"different extension packages, which made administering a Python installation " +"something of a chore." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:821 +msgid "" +"The SIG for distribution utilities, shepherded by Greg Ward, has created the " +"Distutils, a system to make package installation much easier. They form " +"the :mod:`distutils` package, a new part of Python's standard library. In " +"the best case, installing a Python module from source will require the same " +"steps: first you simply mean unpack the tarball or zip archive, and the run " +"\"``python setup.py install``\". The platform will be automatically " +"detected, the compiler will be recognized, C extension modules will be " +"compiled, and the distribution installed into the proper directory. " +"Optional command-line arguments provide more control over the installation " +"process, the distutils package offers many places to override defaults -- " +"separating the build from the install, building or installing in non-default " +"directories, and more." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:833 +msgid "" +"In order to use the Distutils, you need to write a :file:`setup.py` script. " +"For the simple case, when the software contains only .py files, a minimal :" +"file:`setup.py` can be just a few lines long::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:841 +msgid "" +"The :file:`setup.py` file isn't much more complicated if the software " +"consists of a few packages::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:848 +msgid "" +"A C extension can be the most complicated case; here's an example taken from " +"the PyXML package::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:864 +msgid "" +"The Distutils can also take care of creating source and binary " +"distributions. The \"sdist\" command, run by \"``python setup.py sdist``', " +"builds a source distribution such as :file:`foo-1.0.tar.gz`. Adding new " +"commands isn't difficult, \"bdist_rpm\" and \"bdist_wininst\" commands have " +"already been contributed to create an RPM distribution and a Windows " +"installer for the software, respectively. Commands to create other " +"distribution formats such as Debian packages and Solaris :file:`.pkg` files " +"are in various stages of development." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:873 +msgid "" +"All this is documented in a new manual, *Distributing Python Modules*, that " +"joins the basic set of Python documentation." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:880 +msgid "XML Modules" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:882 +msgid "" +"Python 1.5.2 included a simple XML parser in the form of the :mod:`xmllib` " +"module, contributed by Sjoerd Mullender. Since 1.5.2's release, two " +"different interfaces for processing XML have become common: SAX2 (version 2 " +"of the Simple API for XML) provides an event-driven interface with some " +"similarities to :mod:`xmllib`, and the DOM (Document Object Model) provides " +"a tree-based interface, transforming an XML document into a tree of nodes " +"that can be traversed and modified. Python 2.0 includes a SAX2 interface " +"and a stripped- down DOM interface as part of the :mod:`xml` package. Here " +"we will give a brief overview of these new interfaces; consult the Python " +"documentation or the source code for complete details. The Python XML SIG is " +"also working on improved documentation." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:896 +msgid "SAX2 Support" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:898 +msgid "" +"SAX defines an event-driven interface for parsing XML. To use SAX, you must " +"write a SAX handler class. Handler classes inherit from various classes " +"provided by SAX, and override various methods that will then be called by " +"the XML parser. For example, the :meth:`startElement` and :meth:" +"`endElement` methods are called for every starting and end tag encountered " +"by the parser, the :meth:`characters` method is called for every chunk of " +"character data, and so forth." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:906 +msgid "" +"The advantage of the event-driven approach is that the whole document " +"doesn't have to be resident in memory at any one time, which matters if you " +"are processing really huge documents. However, writing the SAX handler " +"class can get very complicated if you're trying to modify the document " +"structure in some elaborate way." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:912 +msgid "" +"For example, this little example program defines a handler that prints a " +"message for every starting and ending tag, and then parses the file :file:" +"`hamlet.xml` using it::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:935 +msgid "" +"For more information, consult the Python documentation, or the XML HOWTO at " +"http://pyxml.sourceforge.net/topics/howto/xml-howto.html." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:940 +msgid "DOM Support" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:942 +msgid "" +"The Document Object Model is a tree-based representation for an XML " +"document. A top-level :class:`Document` instance is the root of the tree, " +"and has a single child which is the top-level :class:`Element` instance. " +"This :class:`Element` has children nodes representing character data and any " +"sub-elements, which may have further children of their own, and so forth. " +"Using the DOM you can traverse the resulting tree any way you like, access " +"element and attribute values, insert and delete nodes, and convert the tree " +"back into XML." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:950 +msgid "" +"The DOM is useful for modifying XML documents, because you can create a DOM " +"tree, modify it by adding new nodes or rearranging subtrees, and then " +"produce a new XML document as output. You can also construct a DOM tree " +"manually and convert it to XML, which can be a more flexible way of " +"producing XML output than simply writing ````...\\ ```` to a " +"file." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:956 +msgid "" +"The DOM implementation included with Python lives in the :mod:`xml.dom." +"minidom` module. It's a lightweight implementation of the Level 1 DOM with " +"support for XML namespaces. The :func:`parse` and :func:`parseString` " +"convenience functions are provided for generating a DOM tree::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:964 +msgid "" +"``doc`` is a :class:`Document` instance. :class:`Document`, like all the " +"other DOM classes such as :class:`Element` and :class:`Text`, is a subclass " +"of the :class:`Node` base class. All the nodes in a DOM tree therefore " +"support certain common methods, such as :meth:`toxml` which returns a string " +"containing the XML representation of the node and its children. Each class " +"also has special methods of its own; for example, :class:`Element` and :" +"class:`Document` instances have a method to find all child elements with a " +"given tag name. Continuing from the previous 2-line example::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:977 +msgid "For the *Hamlet* XML file, the above few lines output::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:982 +msgid "" +"The root element of the document is available as ``doc.documentElement``, " +"and its children can be easily modified by deleting, adding, or removing " +"nodes::" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:997 +msgid "" +"Again, I will refer you to the Python documentation for a complete listing " +"of the different :class:`Node` classes and their various methods." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1002 +msgid "Relationship to PyXML" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1004 +msgid "" +"The XML Special Interest Group has been working on XML-related Python code " +"for a while. Its code distribution, called PyXML, is available from the " +"SIG's Web pages at https://www.python.org/community/sigs/current/xml-sig. " +"The PyXML distribution also used the package name ``xml``. If you've " +"written programs that used PyXML, you're probably wondering about its " +"compatibility with the 2.0 :mod:`xml` package." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1010 +msgid "" +"The answer is that Python 2.0's :mod:`xml` package isn't compatible with " +"PyXML, but can be made compatible by installing a recent version PyXML. " +"Many applications can get by with the XML support that is included with " +"Python 2.0, but more complicated applications will require that the full " +"PyXML package will be installed. When installed, PyXML versions 0.6.0 or " +"greater will replace the :mod:`xml` package shipped with Python, and will be " +"a strict superset of the standard package, adding a bunch of additional " +"features. Some of the additional features in PyXML include:" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1019 +msgid "4DOM, a full DOM implementation from FourThought, Inc." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1021 +msgid "The xmlproc validating parser, written by Lars Marius Garshol." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1023 +msgid "The :mod:`sgmlop` parser accelerator module, written by Fredrik Lundh." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1029 +msgid "Module changes" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1031 +msgid "" +"Lots of improvements and bugfixes were made to Python's extensive standard " +"library; some of the affected modules include :mod:`readline`, :mod:" +"`ConfigParser`, :mod:`cgi`, :mod:`calendar`, :mod:`posix`, :mod:`readline`, :" +"mod:`xmllib`, :mod:`aifc`, :mod:`chunk, wave`, :mod:`random`, :mod:`shelve`, " +"and :mod:`nntplib`. Consult the CVS logs for the exact patch-by-patch " +"details." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1037 +msgid "" +"Brian Gallew contributed OpenSSL support for the :mod:`socket` module. " +"OpenSSL is an implementation of the Secure Socket Layer, which encrypts the " +"data being sent over a socket. When compiling Python, you can edit :file:" +"`Modules/Setup` to include SSL support, which adds an additional function to " +"the :mod:`socket` module: ``socket.ssl(socket, keyfile, certfile)``, which " +"takes a socket object and returns an SSL socket. The :mod:`httplib` and :" +"mod:`urllib` modules were also changed to support ``https://`` URLs, though " +"no one has implemented FTP or SMTP over SSL." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1046 +msgid "" +"The :mod:`httplib` module has been rewritten by Greg Stein to support " +"HTTP/1.1. Backward compatibility with the 1.5 version of :mod:`httplib` is " +"provided, though using HTTP/1.1 features such as pipelining will require " +"rewriting code to use a different set of interfaces." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1051 +msgid "" +"The :mod:`Tkinter` module now supports Tcl/Tk version 8.1, 8.2, or 8.3, and " +"support for the older 7.x versions has been dropped. The Tkinter module now " +"supports displaying Unicode strings in Tk widgets. Also, Fredrik Lundh " +"contributed an optimization which makes operations like ``create_line`` and " +"``create_polygon`` much faster, especially when using lots of coordinates." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1057 +msgid "" +"The :mod:`curses` module has been greatly extended, starting from Oliver " +"Andrich's enhanced version, to provide many additional functions from " +"ncurses and SYSV curses, such as colour, alternative character set support, " +"pads, and mouse support. This means the module is no longer compatible with " +"operating systems that only have BSD curses, but there don't seem to be any " +"currently maintained OSes that fall into this category." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1064 +msgid "" +"As mentioned in the earlier discussion of 2.0's Unicode support, the " +"underlying implementation of the regular expressions provided by the :mod:" +"`re` module has been changed. SRE, a new regular expression engine written " +"by Fredrik Lundh and partially funded by Hewlett Packard, supports matching " +"against both 8-bit strings and Unicode strings." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1074 +msgid "New modules" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1076 +msgid "" +"A number of new modules were added. We'll simply list them with brief " +"descriptions; consult the 2.0 documentation for the details of a particular " +"module." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1080 +msgid "" +":mod:`atexit`: For registering functions to be called before the Python " +"interpreter exits. Code that currently sets ``sys.exitfunc`` directly should " +"be changed to use the :mod:`atexit` module instead, importing :mod:`atexit` " +"and calling :func:`atexit.register` with the function to be called on exit. " +"(Contributed by Skip Montanaro.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1086 +msgid "" +":mod:`codecs`, :mod:`encodings`, :mod:`unicodedata`: Added as part of the " +"new Unicode support." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1089 +msgid "" +":mod:`filecmp`: Supersedes the old :mod:`cmp`, :mod:`cmpcache` and :mod:" +"`dircmp` modules, which have now become deprecated. (Contributed by Gordon " +"MacMillan and Moshe Zadka.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1093 +msgid "" +":mod:`gettext`: This module provides internationalization (I18N) and " +"localization (L10N) support for Python programs by providing an interface to " +"the GNU gettext message catalog library. (Integrated by Barry Warsaw, from " +"separate contributions by Martin von Löwis, Peter Funk, and James " +"Henstridge.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1098 +msgid "" +":mod:`linuxaudiodev`: Support for the :file:`/dev/audio` device on Linux, a " +"twin to the existing :mod:`sunaudiodev` module. (Contributed by Peter Bosch, " +"with fixes by Jeremy Hylton.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1102 +msgid "" +":mod:`mmap`: An interface to memory-mapped files on both Windows and Unix. " +"A file's contents can be mapped directly into memory, at which point it " +"behaves like a mutable string, so its contents can be read and modified. " +"They can even be passed to functions that expect ordinary strings, such as " +"the :mod:`re` module. (Contributed by Sam Rushing, with some extensions by A." +"M. Kuchling.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1108 +msgid "" +":mod:`pyexpat`: An interface to the Expat XML parser. (Contributed by Paul " +"Prescod.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1111 +msgid "" +":mod:`robotparser`: Parse a :file:`robots.txt` file, which is used for " +"writing Web spiders that politely avoid certain areas of a Web site. The " +"parser accepts the contents of a :file:`robots.txt` file, builds a set of " +"rules from it, and can then answer questions about the fetchability of a " +"given URL. (Contributed by Skip Montanaro.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1117 +msgid "" +":mod:`tabnanny`: A module/script to check Python source code for ambiguous " +"indentation. (Contributed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1120 +msgid "" +":mod:`UserString`: A base class useful for deriving objects that behave like " +"strings." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1123 +msgid "" +":mod:`webbrowser`: A module that provides a platform independent way to " +"launch a web browser on a specific URL. For each platform, various browsers " +"are tried in a specific order. The user can alter which browser is launched " +"by setting the *BROWSER* environment variable. (Originally inspired by Eric " +"S. Raymond's patch to :mod:`urllib` which added similar functionality, but " +"the final module comes from code originally implemented by Fred Drake as :" +"file:`Tools/idle/BrowserControl.py`, and adapted for the standard library by " +"Fred.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1132 +msgid "" +":mod:`_winreg`: An interface to the Windows registry. :mod:`_winreg` is an " +"adaptation of functions that have been part of PythonWin since 1995, but has " +"now been added to the core distribution, and enhanced to support Unicode. :" +"mod:`_winreg` was written by Bill Tutt and Mark Hammond." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1137 +msgid "" +":mod:`zipfile`: A module for reading and writing ZIP-format archives. These " +"are archives produced by :program:`PKZIP` on DOS/Windows or :program:`zip` " +"on Unix, not to be confused with :program:`gzip`\\ -format files (which are " +"supported by the :mod:`gzip` module) (Contributed by James C. Ahlstrom.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1142 +msgid "" +":mod:`imputil`: A module that provides a simpler way for writing customized " +"import hooks, in comparison to the existing :mod:`ihooks` module. " +"(Implemented by Greg Stein, with much discussion on python-dev along the " +"way.)" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1150 +msgid "IDLE Improvements" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1152 +msgid "" +"IDLE is the official Python cross-platform IDE, written using Tkinter. " +"Python 2.0 includes IDLE 0.6, which adds a number of new features and " +"improvements. A partial list:" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1156 +msgid "" +"UI improvements and optimizations, especially in the area of syntax " +"highlighting and auto-indentation." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1159 +msgid "" +"The class browser now shows more information, such as the top level " +"functions in a module." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1162 +msgid "" +"Tab width is now a user settable option. When opening an existing Python " +"file, IDLE automatically detects the indentation conventions, and adapts." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1165 +msgid "" +"There is now support for calling browsers on various platforms, used to open " +"the Python documentation in a browser." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1168 +msgid "" +"IDLE now has a command line, which is largely similar to the vanilla Python " +"interpreter." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1171 +msgid "Call tips were added in many places." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1173 +msgid "IDLE can now be installed as a package." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1175 +msgid "In the editor window, there is now a line/column bar at the bottom." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1177 +msgid "" +"Three new keystroke commands: Check module (:kbd:`Alt-F5`), Import module (:" +"kbd:`F5`) and Run script (:kbd:`Ctrl-F5`)." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1184 +msgid "Deleted and Deprecated Modules" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1186 +msgid "" +"A few modules have been dropped because they're obsolete, or because there " +"are now better ways to do the same thing. The :mod:`stdwin` module is gone; " +"it was for a platform-independent windowing toolkit that's no longer " +"developed." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1190 +msgid "" +"A number of modules have been moved to the :file:`lib-old` subdirectory: :" +"mod:`cmp`, :mod:`cmpcache`, :mod:`dircmp`, :mod:`dump`, :mod:`find`, :mod:" +"`grep`, :mod:`packmail`, :mod:`poly`, :mod:`util`, :mod:`whatsound`, :mod:" +"`zmod`. If you have code which relies on a module that's been moved to :" +"file:`lib-old`, you can simply add that directory to ``sys.path`` to get " +"them back, but you're encouraged to update any code that uses these modules." +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1199 ../Doc/whatsnew/2.1.rst:789 +#: ../Doc/whatsnew/2.2.rst:1260 ../Doc/whatsnew/2.3.rst:2077 +#: ../Doc/whatsnew/2.4.rst:1559 ../Doc/whatsnew/2.5.rst:2280 +#: ../Doc/whatsnew/2.6.rst:3308 ../Doc/whatsnew/2.7.rst:2615 +msgid "Acknowledgements" +msgstr "" + +#: ../Doc/whatsnew/2.0.rst:1201 +msgid "" +"The authors would like to thank the following people for offering " +"suggestions on various drafts of this article: David Bolen, Mark Hammond, " +"Gregg Hauser, Jeremy Hylton, Fredrik Lundh, Detlef Lannert, Aahz Maruch, " +"Skip Montanaro, Vladimir Marangozov, Tobias Polzin, Guido van Rossum, Neil " +"Schemenauer, and Russ Schmidt." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:3 +msgid "What's New in Python 2.1" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:5 ../Doc/whatsnew/2.2.rst:5 +#: ../Doc/whatsnew/2.3.rst:5 ../Doc/whatsnew/2.4.rst:5 +#: ../Doc/whatsnew/2.5.rst:5 +msgid "A.M. Kuchling" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:15 +msgid "" +"This article explains the new features in Python 2.1. While there aren't as " +"many changes in 2.1 as there were in Python 2.0, there are still some " +"pleasant surprises in store. 2.1 is the first release to be steered through " +"the use of Python Enhancement Proposals, or PEPs, so most of the sizable " +"changes have accompanying PEPs that provide more complete documentation and " +"a design rationale for the change. This article doesn't attempt to document " +"the new features completely, but simply provides an overview of the new " +"features for Python programmers. Refer to the Python 2.1 documentation, or " +"to the specific PEP, for more details about any new feature that " +"particularly interests you." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:25 +msgid "" +"One recent goal of the Python development team has been to accelerate the " +"pace of new releases, with a new release coming every 6 to 9 months. 2.1 is " +"the first release to come out at this faster pace, with the first alpha " +"appearing in January, 3 months after the final version of 2.0 was released." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:30 +msgid "The final release of Python 2.1 was made on April 17, 2001." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:36 ../Doc/whatsnew/2.2.rst:839 +msgid "PEP 227: Nested Scopes" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:38 +msgid "" +"The largest change in Python 2.1 is to Python's scoping rules. In Python " +"2.0, at any given time there are at most three namespaces used to look up " +"variable names: local, module-level, and the built-in namespace. This often " +"surprised people because it didn't match their intuitive expectations. For " +"example, a nested recursive function definition doesn't work::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:51 ../Doc/whatsnew/2.2.rst:862 +msgid "" +"The function :func:`g` will always raise a :exc:`NameError` exception, " +"because the binding of the name ``g`` isn't in either its local namespace or " +"in the module-level namespace. This isn't much of a problem in practice " +"(how often do you recursively define interior functions like this?), but " +"this also made using the :keyword:`lambda` statement clumsier, and this was " +"a problem in practice. In code which uses :keyword:`lambda` you can often " +"find local variables being copied by passing them as the default values of " +"arguments. ::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:65 ../Doc/whatsnew/2.2.rst:876 +msgid "" +"The readability of Python code written in a strongly functional style " +"suffers greatly as a result." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:68 +msgid "" +"The most significant change to Python 2.1 is that static scoping has been " +"added to the language to fix this problem. As a first effect, the " +"``name=name`` default argument is now unnecessary in the above example. Put " +"simply, when a given variable name is not assigned a value within a function " +"(by an assignment, or the :keyword:`def`, :keyword:`class`, or :keyword:" +"`import` statements), references to the variable will be looked up in the " +"local namespace of the enclosing scope. A more detailed explanation of the " +"rules, and a dissection of the implementation, can be found in the PEP." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:77 ../Doc/whatsnew/2.2.rst:888 +msgid "" +"This change may cause some compatibility problems for code where the same " +"variable name is used both at the module level and as a local variable " +"within a function that contains further function definitions. This seems " +"rather unlikely though, since such code would have been pretty confusing to " +"read in the first place." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:83 ../Doc/whatsnew/2.2.rst:894 +msgid "" +"One side effect of the change is that the ``from module import *`` and " +"``exec`` statements have been made illegal inside a function scope under " +"certain conditions. The Python reference manual has said all along that " +"``from module import *`` is only legal at the top level of a module, but the " +"CPython interpreter has never enforced this before. As part of the " +"implementation of nested scopes, the compiler which turns Python source into " +"bytecodes has to generate different code to access variables in a containing " +"scope. ``from module import *`` and ``exec`` make it impossible for the " +"compiler to figure this out, because they add names to the local namespace " +"that are unknowable at compile time. Therefore, if a function contains " +"function definitions or :keyword:`lambda` expressions with free variables, " +"the compiler will flag this by raising a :exc:`SyntaxError` exception." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:96 ../Doc/whatsnew/2.2.rst:907 +msgid "To make the preceding explanation a bit clearer, here's an example::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:105 ../Doc/whatsnew/2.2.rst:916 +msgid "" +"Line 4 containing the ``exec`` statement is a syntax error, since ``exec`` " +"would define a new local variable named ``x`` whose value should be accessed " +"by :func:`g`." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:109 ../Doc/whatsnew/2.2.rst:920 +msgid "" +"This shouldn't be much of a limitation, since ``exec`` is rarely used in " +"most Python code (and when it is used, it's often a sign of a poor design " +"anyway)." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:113 +msgid "" +"Compatibility concerns have led to nested scopes being introduced gradually; " +"in Python 2.1, they aren't enabled by default, but can be turned on within a " +"module by using a future statement as described in PEP 236. (See the " +"following section for further discussion of PEP 236.) In Python 2.2, nested " +"scopes will become the default and there will be no way to turn them off, " +"but users will have had all of 2.1's lifetime to fix any breakage resulting " +"from their introduction." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:123 ../Doc/whatsnew/2.2.rst:927 +msgid ":pep:`227` - Statically Nested Scopes" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:124 ../Doc/whatsnew/2.2.rst:928 +msgid "Written and implemented by Jeremy Hylton." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:130 +msgid "PEP 236: __future__ Directives" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:132 +msgid "" +"The reaction to nested scopes was widespread concern about the dangers of " +"breaking code with the 2.1 release, and it was strong enough to make the " +"Pythoneers take a more conservative approach. This approach consists of " +"introducing a convention for enabling optional functionality in release N " +"that will become compulsory in release N+1." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:138 +msgid "" +"The syntax uses a ``from...import`` statement using the reserved module " +"name :mod:`__future__`. Nested scopes can be enabled by the following " +"statement::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:143 +msgid "" +"While it looks like a normal :keyword:`import` statement, it's not; there " +"are strict rules on where such a future statement can be put. They can only " +"be at the top of a module, and must precede any Python code or regular :" +"keyword:`import` statements. This is because such statements can affect how " +"the Python bytecode compiler parses code and generates bytecode, so they " +"must precede any statement that will result in bytecodes being produced." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:153 +msgid ":pep:`236` - Back to the :mod:`__future__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:154 +msgid "Written by Tim Peters, and primarily implemented by Jeremy Hylton." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:160 +msgid "PEP 207: Rich Comparisons" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:162 +msgid "" +"In earlier versions, Python's support for implementing comparisons on user- " +"defined classes and extension types was quite simple. Classes could " +"implement a :meth:`__cmp__` method that was given two instances of a class, " +"and could only return 0 if they were equal or +1 or -1 if they weren't; the " +"method couldn't raise an exception or return anything other than a Boolean " +"value. Users of Numeric Python often found this model too weak and " +"restrictive, because in the number-crunching programs that numeric Python is " +"used for, it would be more useful to be able to perform elementwise " +"comparisons of two matrices, returning a matrix containing the results of a " +"given comparison for each element. If the two matrices are of different " +"sizes, then the compare has to be able to raise an exception to signal the " +"error." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:174 +msgid "" +"In Python 2.1, rich comparisons were added in order to support this need. " +"Python classes can now individually overload each of the ``<``, ``<=``, " +"``>``, ``>=``, ``==``, and ``!=`` operations. The new magic method names " +"are:" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:179 ../Doc/whatsnew/2.5.rst:1807 +msgid "Operation" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:179 +msgid "Method name" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:181 +msgid "``<``" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:181 +msgid ":meth:`__lt__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:183 +msgid "``<=``" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:183 +msgid ":meth:`__le__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:185 +msgid "``>``" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:185 +msgid ":meth:`__gt__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:187 +msgid "``>=``" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:187 +msgid ":meth:`__ge__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:189 +msgid "``==``" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:189 +msgid ":meth:`__eq__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:191 +msgid "``!=``" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:191 +msgid ":meth:`__ne__`" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:194 +msgid "" +"(The magic methods are named after the corresponding Fortran operators ``.LT." +"``. ``.LE.``, &c. Numeric programmers are almost certainly quite familiar " +"with these names and will find them easy to remember.)" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:198 +msgid "" +"Each of these magic methods is of the form ``method(self, other)``, where " +"``self`` will be the object on the left-hand side of the operator, while " +"``other`` will be the object on the right-hand side. For example, the " +"expression ``A < B`` will cause ``A.__lt__(B)`` to be called." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:203 +msgid "" +"Each of these magic methods can return anything at all: a Boolean, a matrix, " +"a list, or any other Python object. Alternatively they can raise an " +"exception if the comparison is impossible, inconsistent, or otherwise " +"meaningless." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:207 +msgid "" +"The built-in ``cmp(A,B)`` function can use the rich comparison machinery, " +"and now accepts an optional argument specifying which comparison operation " +"to use; this is given as one of the strings ``\"<\"``, ``\"<=\"``, ``\">" +"\"``, ``\">=\"``, ``\"==\"``, or ``\"!=\"``. If called without the optional " +"third argument, :func:`cmp` will only return -1, 0, or +1 as in previous " +"versions of Python; otherwise it will call the appropriate method and can " +"return any Python object." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:214 +msgid "" +"There are also corresponding changes of interest to C programmers; there's a " +"new slot ``tp_richcmp`` in type objects and an API for performing a given " +"rich comparison. I won't cover the C API here, but will refer you to PEP " +"207, or to 2.1's C API documentation, for the full list of related functions." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:223 +msgid ":pep:`207` - Rich Comparisons" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:223 +msgid "" +"Written by Guido van Rossum, heavily based on earlier work by David Ascher, " +"and implemented by Guido van Rossum." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:230 +msgid "PEP 230: Warning Framework" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:232 +msgid "" +"Over its 10 years of existence, Python has accumulated a certain number of " +"obsolete modules and features along the way. It's difficult to know when a " +"feature is safe to remove, since there's no way of knowing how much code " +"uses it --- perhaps no programs depend on the feature, or perhaps many do. " +"To enable removing old features in a more structured way, a warning " +"framework was added. When the Python developers want to get rid of a " +"feature, it will first trigger a warning in the next version of Python. The " +"following Python version can then drop the feature, and users will have had " +"a full release cycle to remove uses of the old feature." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:242 +msgid "" +"Python 2.1 adds the warning framework to be used in this scheme. It adds a :" +"mod:`warnings` module that provide functions to issue warnings, and to " +"filter out warnings that you don't want to be displayed. Third-party modules " +"can also use this framework to deprecate old features that they no longer " +"wish to support." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:248 +msgid "" +"For example, in Python 2.1 the :mod:`regex` module is deprecated, so " +"importing it causes a warning to be printed::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:256 +msgid "Warnings can be issued by calling the :func:`warnings.warn` function::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:260 +msgid "" +"The first parameter is the warning message; an additional optional " +"parameters can be used to specify a particular warning category." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:263 +msgid "" +"Filters can be added to disable certain warnings; a regular expression " +"pattern can be applied to the message or to the module name in order to " +"suppress a warning. For example, you may have a program that uses the :mod:" +"`regex` module and not want to spare the time to convert it to use the :mod:" +"`re` module right now. The warning can be suppressed by calling ::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:275 +msgid "" +"This adds a filter that will apply only to warnings of the class :class:" +"`DeprecationWarning` triggered in the :mod:`__main__` module, and applies a " +"regular expression to only match the message about the :mod:`regex` module " +"being deprecated, and will cause such warnings to be ignored. Warnings can " +"also be printed only once, printed every time the offending code is " +"executed, or turned into exceptions that will cause the program to stop " +"(unless the exceptions are caught in the usual way, of course)." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:283 +msgid "" +"Functions were also added to Python's C API for issuing warnings; refer to " +"PEP 230 or to Python's API documentation for the details." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:293 +msgid ":pep:`5` - Guidelines for Language Evolution" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:290 +msgid "" +"Written by Paul Prescod, to specify procedures to be followed when removing " +"old features from Python. The policy described in this PEP hasn't been " +"officially adopted, but the eventual policy probably won't be too different " +"from Prescod's proposal." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:295 +msgid ":pep:`230` - Warning Framework" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:296 +msgid "Written and implemented by Guido van Rossum." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:302 +msgid "PEP 229: New Build System" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:304 +msgid "" +"When compiling Python, the user had to go in and edit the :file:`Modules/" +"Setup` file in order to enable various additional modules; the default set " +"is relatively small and limited to modules that compile on most Unix " +"platforms. This means that on Unix platforms with many more features, most " +"notably Linux, Python installations often don't contain all useful modules " +"they could." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:310 +msgid "" +"Python 2.0 added the Distutils, a set of modules for distributing and " +"installing extensions. In Python 2.1, the Distutils are used to compile " +"much of the standard library of extension modules, autodetecting which ones " +"are supported on the current machine. It's hoped that this will make Python " +"installations easier and more featureful." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:316 +msgid "" +"Instead of having to edit the :file:`Modules/Setup` file in order to enable " +"modules, a :file:`setup.py` script in the top directory of the Python source " +"distribution is run at build time, and attempts to discover which modules " +"can be enabled by examining the modules and header files on the system. If " +"a module is configured in :file:`Modules/Setup`, the :file:`setup.py` script " +"won't attempt to compile that module and will defer to the :file:`Modules/" +"Setup` file's contents. This provides a way to specific any strange command-" +"line flags or libraries that are required for a specific platform." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:325 +msgid "" +"In another far-reaching change to the build mechanism, Neil Schemenauer " +"restructured things so Python now uses a single makefile that isn't " +"recursive, instead of makefiles in the top directory and in each of the :" +"file:`Python/`, :file:`Parser/`, :file:`Objects/`, and :file:`Modules/` " +"subdirectories. This makes building Python faster and also makes hacking " +"the Makefiles clearer and simpler." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:335 +msgid ":pep:`229` - Using Distutils to Build Python" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:336 ../Doc/whatsnew/2.1.rst:571 +msgid "Written and implemented by A.M. Kuchling." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:342 +msgid "PEP 205: Weak References" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:344 +msgid "" +"Weak references, available through the :mod:`weakref` module, are a minor " +"but useful new data type in the Python programmer's toolbox." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:347 +msgid "" +"Storing a reference to an object (say, in a dictionary or a list) has the " +"side effect of keeping that object alive forever. There are a few specific " +"cases where this behaviour is undesirable, object caches being the most " +"common one, and another being circular references in data structures such as " +"trees." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:352 +msgid "" +"For example, consider a memoizing function that caches the results of " +"another function ``f(x)`` by storing the function's argument and its result " +"in a dictionary::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:368 +msgid "" +"This version works for simple things such as integers, but it has a side " +"effect; the ``_cache`` dictionary holds a reference to the return values, so " +"they'll never be deallocated until the Python process exits and cleans up. " +"This isn't very noticeable for integers, but if :func:`f` returns an object, " +"or a data structure that takes up a lot of memory, this can be a problem." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:374 +msgid "" +"Weak references provide a way to implement a cache that won't keep objects " +"alive beyond their time. If an object is only accessible through weak " +"references, the object will be deallocated and the weak references will now " +"indicate that the object it referred to no longer exists. A weak reference " +"to an object *obj* is created by calling ``wr = weakref.ref(obj)``. The " +"object being referred to is returned by calling the weak reference as if it " +"were a function: ``wr()``. It will return the referenced object, or " +"``None`` if the object no longer exists." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:382 +msgid "" +"This makes it possible to write a :func:`memoize` function whose cache " +"doesn't keep objects alive, by storing weak references in the cache. ::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:400 +msgid "" +"The :mod:`weakref` module also allows creating proxy objects which behave " +"like weak references --- an object referenced only by proxy objects is " +"deallocated -- but instead of requiring an explicit call to retrieve the " +"object, the proxy transparently forwards all operations to the object as " +"long as the object still exists. If the object is deallocated, attempting " +"to use a proxy will cause a :exc:`weakref.ReferenceError` exception to be " +"raised. ::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:416 +msgid ":pep:`205` - Weak References" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:417 +msgid "Written and implemented by Fred L. Drake, Jr." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:423 +msgid "PEP 232: Function Attributes" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:425 +msgid "" +"In Python 2.1, functions can now have arbitrary information attached to " +"them. People were often using docstrings to hold information about functions " +"and methods, because the ``__doc__`` attribute was the only way of attaching " +"any information to a function. For example, in the Zope Web application " +"server, functions are marked as safe for public access by having a " +"docstring, and in John Aycock's SPARK parsing framework, docstrings hold " +"parts of the BNF grammar to be parsed. This overloading is unfortunate, " +"since docstrings are really intended to hold a function's documentation; for " +"example, it means you can't properly document functions intended for private " +"use in Zope." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:435 +msgid "" +"Arbitrary attributes can now be set and retrieved on functions using the " +"regular Python syntax::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:444 +msgid "" +"The dictionary containing attributes can be accessed as the function's :attr:" +"`~object.__dict__`. Unlike the :attr:`~object.__dict__` attribute of class " +"instances, in functions you can actually assign a new dictionary to :attr:" +"`~object.__dict__`, though the new value is restricted to a regular Python " +"dictionary; you *can't* be tricky and set it to a :class:`UserDict` " +"instance, or any other random object that behaves like a mapping." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:454 +msgid ":pep:`232` - Function Attributes" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:455 +msgid "Written and implemented by Barry Warsaw." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:461 +msgid "PEP 235: Importing Modules on Case-Insensitive Platforms" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:463 +msgid "" +"Some operating systems have filesystems that are case-insensitive, MacOS and " +"Windows being the primary examples; on these systems, it's impossible to " +"distinguish the filenames ``FILE.PY`` and ``file.py``, even though they do " +"store the file's name in its original case (they're case-preserving, too)." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:468 +msgid "" +"In Python 2.1, the :keyword:`import` statement will work to simulate case- " +"sensitivity on case-insensitive platforms. Python will now search for the " +"first case-sensitive match by default, raising an :exc:`ImportError` if no " +"such file is found, so ``import file`` will not import a module named ``FILE." +"PY``. Case- insensitive matching can be requested by setting the :envvar:" +"`PYTHONCASEOK` environment variable before starting the Python interpreter." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:479 +msgid "PEP 217: Interactive Display Hook" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:481 +msgid "" +"When using the Python interpreter interactively, the output of commands is " +"displayed using the built-in :func:`repr` function. In Python 2.1, the " +"variable :func:`sys.displayhook` can be set to a callable object which will " +"be called instead of :func:`repr`. For example, you can set it to a special " +"pretty- printing function::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:502 +msgid ":pep:`217` - Display Hook for Interactive Use" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:503 +msgid "Written and implemented by Moshe Zadka." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:509 +msgid "PEP 208: New Coercion Model" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:511 +msgid "" +"How numeric coercion is done at the C level was significantly modified. " +"This will only affect the authors of C extensions to Python, allowing them " +"more flexibility in writing extension types that support numeric operations." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:515 +msgid "" +"Extension types can now set the type flag ``Py_TPFLAGS_CHECKTYPES`` in their " +"``PyTypeObject`` structure to indicate that they support the new coercion " +"model. In such extension types, the numeric slot functions can no longer " +"assume that they'll be passed two arguments of the same type; instead they " +"may be passed two arguments of differing types, and can then perform their " +"own internal coercion. If the slot function is passed a type it can't " +"handle, it can indicate the failure by returning a reference to the " +"``Py_NotImplemented`` singleton value. The numeric functions of the other " +"type will then be tried, and perhaps they can handle the operation; if the " +"other type also returns ``Py_NotImplemented``, then a :exc:`TypeError` will " +"be raised. Numeric methods written in Python can also return " +"``Py_NotImplemented``, causing the interpreter to act as if the method did " +"not exist (perhaps raising a :exc:`TypeError`, perhaps trying another " +"object's numeric methods)." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:534 +msgid ":pep:`208` - Reworking the Coercion Model" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:533 +msgid "" +"Written and implemented by Neil Schemenauer, heavily based upon earlier work " +"by Marc-André Lemburg. Read this to understand the fine points of how " +"numeric operations will now be processed at the C level." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:541 +msgid "PEP 241: Metadata in Python Packages" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:543 +msgid "" +"A common complaint from Python users is that there's no single catalog of " +"all the Python modules in existence. T. Middleton's Vaults of Parnassus at " +"http://www.vex.net/parnassus/ are the largest catalog of Python modules, but " +"registering software at the Vaults is optional, and many people don't bother." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:548 +msgid "" +"As a first small step toward fixing the problem, Python software packaged " +"using the Distutils :command:`sdist` command will include a file named :file:" +"`PKG-INFO` containing information about the package such as its name, " +"version, and author (metadata, in cataloguing terminology). PEP 241 " +"contains the full list of fields that can be present in the :file:`PKG-INFO` " +"file. As people began to package their software using Python 2.1, more and " +"more packages will include metadata, making it possible to build automated " +"cataloguing systems and experiment with them. With the result experience, " +"perhaps it'll be possible to design a really good catalog and then build " +"support for it into Python 2.2. For example, the Distutils :command:`sdist` " +"and :command:`bdist_\\*` commands could support an ``upload`` option that " +"would automatically upload your package to a catalog server." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:561 +msgid "" +"You can start creating packages containing :file:`PKG-INFO` even if you're " +"not using Python 2.1, since a new release of the Distutils will be made for " +"users of earlier Python versions. Version 1.0.2 of the Distutils includes " +"the changes described in PEP 241, as well as various bugfixes and " +"enhancements. It will be available from the Distutils SIG at https://www." +"python.org/community/sigs/current/distutils-sig/." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:571 +msgid ":pep:`241` - Metadata for Python Software Packages" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:574 +msgid ":pep:`243` - Module Repository Upload Mechanism" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:574 +msgid "" +"Written by Sean Reifschneider, this draft PEP describes a proposed mechanism " +"for uploading Python packages to a central server." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:581 ../Doc/whatsnew/2.2.rst:934 +#: ../Doc/whatsnew/2.6.rst:1783 ../Doc/whatsnew/2.7.rst:1025 +msgid "New and Improved Modules" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:583 +msgid "" +"Ka-Ping Yee contributed two new modules: :mod:`inspect.py`, a module for " +"getting information about live Python code, and :mod:`pydoc.py`, a module " +"for interactively converting docstrings to HTML or text. As a bonus, :file:" +"`Tools/scripts/pydoc`, which is now automatically installed, uses :mod:" +"`pydoc.py` to display documentation given a Python module, package, or class " +"name. For example, ``pydoc xml.dom`` displays the following::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:605 +msgid "" +":file:`pydoc` also includes a Tk-based interactive help browser. :file:" +"`pydoc` quickly becomes addictive; try it out!" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:608 +msgid "" +"Two different modules for unit testing were added to the standard library. " +"The :mod:`doctest` module, contributed by Tim Peters, provides a testing " +"framework based on running embedded examples in docstrings and comparing the " +"results against the expected output. PyUnit, contributed by Steve Purcell, " +"is a unit testing framework inspired by JUnit, which was in turn an " +"adaptation of Kent Beck's Smalltalk testing framework. See http://pyunit." +"sourceforge.net/ for more information about PyUnit." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:616 +msgid "" +"The :mod:`difflib` module contains a class, :class:`SequenceMatcher`, which " +"compares two sequences and computes the changes required to transform one " +"sequence into the other. For example, this module can be used to write a " +"tool similar to the Unix :program:`diff` program, and in fact the sample " +"program :file:`Tools/scripts/ndiff.py` demonstrates how to write such a " +"script." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:622 +msgid "" +":mod:`curses.panel`, a wrapper for the panel library, part of ncurses and of " +"SYSV curses, was contributed by Thomas Gellekum. The panel library provides " +"windows with the additional feature of depth. Windows can be moved higher or " +"lower in the depth ordering, and the panel library figures out where panels " +"overlap and which sections are visible." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:628 +msgid "" +"The PyXML package has gone through a few releases since Python 2.0, and " +"Python 2.1 includes an updated version of the :mod:`xml` package. Some of " +"the noteworthy changes include support for Expat 1.2 and later versions, the " +"ability for Expat parsers to handle files in any encoding supported by " +"Python, and various bugfixes for SAX, DOM, and the :mod:`minidom` module." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:634 +msgid "" +"Ping also contributed another hook for handling uncaught exceptions. :func:" +"`sys.excepthook` can be set to a callable object. When an exception isn't " +"caught by any :keyword:`try`...\\ :keyword:`except` blocks, the exception " +"will be passed to :func:`sys.excepthook`, which can then do whatever it " +"likes. At the Ninth Python Conference, Ping demonstrated an application for " +"this hook: printing an extended traceback that not only lists the stack " +"frames, but also lists the function arguments and the local variables for " +"each frame." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:642 +msgid "" +"Various functions in the :mod:`time` module, such as :func:`asctime` and :" +"func:`localtime`, require a floating point argument containing the time in " +"seconds since the epoch. The most common use of these functions is to work " +"with the current time, so the floating point argument has been made " +"optional; when a value isn't provided, the current time will be used. For " +"example, log file entries usually need a string containing the current time; " +"in Python 2.1, ``time.asctime()`` can be used, instead of the lengthier " +"``time.asctime(time.localtime(time.time()))`` that was previously required." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:651 +msgid "This change was proposed and implemented by Thomas Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:653 +msgid "" +"The :mod:`ftplib` module now defaults to retrieving files in passive mode, " +"because passive mode is more likely to work from behind a firewall. This " +"request came from the Debian bug tracking system, since other Debian " +"packages use :mod:`ftplib` to retrieve files and then don't work from behind " +"a firewall. It's deemed unlikely that this will cause problems for anyone, " +"because Netscape defaults to passive mode and few people complain, but if " +"passive mode is unsuitable for your application or network setup, call " +"``set_pasv(0)`` on FTP objects to disable passive mode." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:662 +msgid "" +"Support for raw socket access has been added to the :mod:`socket` module, " +"contributed by Grant Edwards." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:665 +msgid "" +"The :mod:`pstats` module now contains a simple interactive statistics " +"browser for displaying timing profiles for Python programs, invoked when the " +"module is run as a script. Contributed by Eric S. Raymond." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:669 +msgid "" +"A new implementation-dependent function, ``sys._getframe([depth])``, has " +"been added to return a given frame object from the current call stack. :func:" +"`sys._getframe` returns the frame at the top of the call stack; if the " +"optional integer argument *depth* is supplied, the function returns the " +"frame that is *depth* calls below the top of the stack. For example, ``sys." +"_getframe(1)`` returns the caller's frame object." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:676 +msgid "" +"This function is only present in CPython, not in Jython or the .NET " +"implementation. Use it for debugging, and resist the temptation to put it " +"into production code." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:684 ../Doc/whatsnew/2.2.rst:1129 +#: ../Doc/whatsnew/2.3.rst:1966 ../Doc/whatsnew/2.7.rst:2379 +msgid "Other Changes and Fixes" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:686 +msgid "" +"There were relatively few smaller changes made in Python 2.1 due to the " +"shorter release cycle. A search through the CVS change logs turns up 117 " +"patches applied, and 136 bugs fixed; both figures are likely to be " +"underestimates. Some of the more notable changes are:" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:691 +msgid "" +"A specialized object allocator is now optionally available, that should be " +"faster than the system :func:`malloc` and have less memory overhead. The " +"allocator uses C's :func:`malloc` function to get large pools of memory, and " +"then fulfills smaller memory requests from these pools. It can be enabled " +"by providing the :option:`--with-pymalloc` option to the :program:" +"`configure` script; see :file:`Objects/obmalloc.c` for the implementation " +"details." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:698 +msgid "" +"Authors of C extension modules should test their code with the object " +"allocator enabled, because some incorrect code may break, causing core dumps " +"at runtime. There are a bunch of memory allocation functions in Python's C " +"API that have previously been just aliases for the C library's :func:" +"`malloc` and :func:`free`, meaning that if you accidentally called " +"mismatched functions, the error wouldn't be noticeable. When the object " +"allocator is enabled, these functions aren't aliases of :func:`malloc` and :" +"func:`free` any more, and calling the wrong function to free memory will get " +"you a core dump. For example, if memory was allocated using :func:" +"`PyMem_New`, it has to be freed using :func:`PyMem_Del`, not :func:`free`. " +"A few modules included with Python fell afoul of this and had to be fixed; " +"doubtless there are more third-party modules that will have the same problem." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:711 +msgid "The object allocator was contributed by Vladimir Marangozov." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:713 +msgid "" +"The speed of line-oriented file I/O has been improved because people often " +"complain about its lack of speed, and because it's often been used as a " +"naïve benchmark. The :meth:`readline` method of file objects has therefore " +"been rewritten to be much faster. The exact amount of the speedup will vary " +"from platform to platform depending on how slow the C library's :func:`getc` " +"was, but is around 66%, and potentially much faster on some particular " +"operating systems. Tim Peters did much of the benchmarking and coding for " +"this change, motivated by a discussion in comp.lang.python." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:722 +msgid "" +"A new module and method for file objects was also added, contributed by Jeff " +"Epler. The new method, :meth:`xreadlines`, is similar to the existing :func:" +"`xrange` built-in. :func:`xreadlines` returns an opaque sequence object " +"that only supports being iterated over, reading a line on every iteration " +"but not reading the entire file into memory as the existing :meth:" +"`readlines` method does. You'd use it like this::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:733 +msgid "" +"For a fuller discussion of the line I/O changes, see the python-dev summary " +"for January 1-15, 2001 at https://mail.python.org/pipermail/python-dev/2001-" +"January/." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:736 +msgid "" +"A new method, :meth:`popitem`, was added to dictionaries to enable " +"destructively iterating through the contents of a dictionary; this can be " +"faster for large dictionaries because there's no need to construct a list " +"containing all the keys or values. ``D.popitem()`` removes a random ``(key, " +"value)`` pair from the dictionary ``D`` and returns it as a 2-tuple. This " +"was implemented mostly by Tim Peters and Guido van Rossum, after a " +"suggestion and preliminary patch by Moshe Zadka." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:744 +msgid "" +"Modules can now control which names are imported when ``from module import " +"*`` is used, by defining an ``__all__`` attribute containing a list of names " +"that will be imported. One common complaint is that if the module imports " +"other modules such as :mod:`sys` or :mod:`string`, ``from module import *`` " +"will add them to the importing module's namespace. To fix this, simply list " +"the public names in ``__all__``::" +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:754 +msgid "" +"A stricter version of this patch was first suggested and implemented by Ben " +"Wolfson, but after some python-dev discussion, a weaker final version was " +"checked in." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:758 +msgid "" +"Applying :func:`repr` to strings previously used octal escapes for non-" +"printable characters; for example, a newline was ``'\\012'``. This was a " +"vestigial trace of Python's C ancestry, but today octal is of very little " +"practical use. Ka-Ping Yee suggested using hex escapes instead of octal " +"ones, and using the ``\\n``, ``\\t``, ``\\r`` escapes for the appropriate " +"characters, and implemented this new formatting." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:765 +msgid "" +"Syntax errors detected at compile-time can now raise exceptions containing " +"the filename and line number of the error, a pleasant side effect of the " +"compiler reorganization done by Jeremy Hylton." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:769 +msgid "" +"C extensions which import other modules have been changed to use :func:" +"`PyImport_ImportModule`, which means that they will use any import hooks " +"that have been installed. This is also encouraged for third-party " +"extensions that need to import some other module from C code." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:774 +msgid "" +"The size of the Unicode character database was shrunk by another 340K thanks " +"to Fredrik Lundh." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:777 +msgid "" +"Some new ports were contributed: MacOS X (by Steven Majewski), Cygwin (by " +"Jason Tishler); RISCOS (by Dietmar Schwertberger); Unixware 7 (by Billy G. " +"Allie)." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:781 +msgid "" +"And there's the usual list of minor bugfixes, minor memory leaks, docstring " +"edits, and other tweaks, too lengthy to be worth itemizing; see the CVS logs " +"for the full details if you want them." +msgstr "" + +#: ../Doc/whatsnew/2.1.rst:791 +msgid "" +"The author would like to thank the following people for offering suggestions " +"on various drafts of this article: Graeme Cross, David Goodger, Jay Graves, " +"Michael Hudson, Marc-André Lemburg, Fredrik Lundh, Neil Schemenauer, Thomas " +"Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:3 +msgid "What's New in Python 2.2" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:15 +msgid "" +"This article explains the new features in Python 2.2.2, released on October " +"14, 2002. Python 2.2.2 is a bugfix release of Python 2.2, originally " +"released on December 21, 2001." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:19 +msgid "" +"Python 2.2 can be thought of as the \"cleanup release\". There are some " +"features such as generators and iterators that are completely new, but most " +"of the changes, significant and far-reaching though they may be, are aimed " +"at cleaning up irregularities and dark corners of the language design." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:24 +msgid "" +"This article doesn't attempt to provide a complete specification of the new " +"features, but instead provides a convenient overview. For full details, you " +"should refer to the documentation for Python 2.2, such as the `Python " +"Library Reference `_ and the " +"`Python Reference Manual `_. If " +"you want to understand the complete implementation and design rationale for " +"a change, refer to the PEP for a particular new feature." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:43 +msgid "PEPs 252 and 253: Type and Class Changes" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:45 +msgid "" +"The largest and most far-reaching changes in Python 2.2 are to Python's " +"model of objects and classes. The changes should be backward compatible, so " +"it's likely that your code will continue to run unchanged, but the changes " +"provide some amazing new capabilities. Before beginning this, the longest " +"and most complicated section of this article, I'll provide an overview of " +"the changes and offer some comments." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:52 +msgid "" +"A long time ago I wrote a Web page listing flaws in Python's design. One of " +"the most significant flaws was that it's impossible to subclass Python types " +"implemented in C. In particular, it's not possible to subclass built-in " +"types, so you can't just subclass, say, lists in order to add a single " +"useful method to them. The :mod:`UserList` module provides a class that " +"supports all of the methods of lists and that can be subclassed further, but " +"there's lots of C code that expects a regular Python list and won't accept " +"a :class:`UserList` instance." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:61 +msgid "" +"Python 2.2 fixes this, and in the process adds some exciting new " +"capabilities. A brief summary:" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:64 +msgid "" +"You can subclass built-in types such as lists and even integers, and your " +"subclasses should work in every place that requires the original type." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:67 +msgid "" +"It's now possible to define static and class methods, in addition to the " +"instance methods available in previous versions of Python." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:70 +msgid "" +"It's also possible to automatically call methods on accessing or setting an " +"instance attribute by using a new mechanism called :dfn:`properties`. Many " +"uses of :meth:`__getattr__` can be rewritten to use properties instead, " +"making the resulting code simpler and faster. As a small side benefit, " +"attributes can now have docstrings, too." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:76 +msgid "" +"The list of legal attributes for an instance can be limited to a particular " +"set using :dfn:`slots`, making it possible to safeguard against typos and " +"perhaps make more optimizations possible in future versions of Python." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:80 +msgid "" +"Some users have voiced concern about all these changes. Sure, they say, the " +"new features are neat and lend themselves to all sorts of tricks that " +"weren't possible in previous versions of Python, but they also make the " +"language more complicated. Some people have said that they've always " +"recommended Python for its simplicity, and feel that its simplicity is being " +"lost." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:86 +msgid "" +"Personally, I think there's no need to worry. Many of the new features are " +"quite esoteric, and you can write a lot of Python code without ever needed " +"to be aware of them. Writing a simple class is no more difficult than it " +"ever was, so you don't need to bother learning or teaching them unless " +"they're actually needed. Some very complicated tasks that were previously " +"only possible from C will now be possible in pure Python, and to my mind " +"that's all for the better." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:93 +msgid "" +"I'm not going to attempt to cover every single corner case and small change " +"that were required to make the new features work. Instead this section will " +"paint only the broad strokes. See section :ref:`sect-rellinks`, \"Related " +"Links\", for further sources of information about Python 2.2's new object " +"model." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:100 +msgid "Old and New Classes" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:102 +msgid "" +"First, you should know that Python 2.2 really has two kinds of classes: " +"classic or old-style classes, and new-style classes. The old-style class " +"model is exactly the same as the class model in earlier versions of Python. " +"All the new features described in this section apply only to new-style " +"classes. This divergence isn't intended to last forever; eventually old-" +"style classes will be dropped, possibly in Python 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:109 +msgid "" +"So how do you define a new-style class? You do it by subclassing an " +"existing new-style class. Most of Python's built-in types, such as " +"integers, lists, dictionaries, and even files, are new-style classes now. A " +"new-style class named :class:`object`, the base class for all built-in " +"types, has also been added so if no built-in type is suitable, you can just " +"subclass :class:`object`::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:121 +msgid "" +"This means that :keyword:`class` statements that don't have any base classes " +"are always classic classes in Python 2.2. (Actually you can also change " +"this by setting a module-level variable named :attr:`__metaclass__` --- see :" +"pep:`253` for the details --- but it's easier to just subclass :keyword:" +"`object`.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:126 +msgid "" +"The type objects for the built-in types are available as built-ins, named " +"using a clever trick. Python has always had built-in functions named :func:" +"`int`, :func:`float`, and :func:`str`. In 2.2, they aren't functions any " +"more, but type objects that behave as factories when called. ::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:136 +msgid "" +"To make the set of types complete, new type objects such as :func:`dict` " +"and :func:`file` have been added. Here's a more interesting example, adding " +"a :meth:`lock` method to file objects::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:146 +msgid "" +"The now-obsolete :mod:`posixfile` module contained a class that emulated all " +"of a file object's methods and also added a :meth:`lock` method, but this " +"class couldn't be passed to internal functions that expected a built-in " +"file, something which is possible with our new :class:`LockableFile`." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:153 +msgid "Descriptors" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:155 +msgid "" +"In previous versions of Python, there was no consistent way to discover what " +"attributes and methods were supported by an object. There were some informal " +"conventions, such as defining :attr:`__members__` and :attr:`__methods__` " +"attributes that were lists of names, but often the author of an extension " +"type or a class wouldn't bother to define them. You could fall back on " +"inspecting the :attr:`~object.__dict__` of an object, but when class " +"inheritance or an arbitrary :meth:`__getattr__` hook were in use this could " +"still be inaccurate." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:163 +msgid "" +"The one big idea underlying the new class model is that an API for " +"describing the attributes of an object using :dfn:`descriptors` has been " +"formalized. Descriptors specify the value of an attribute, stating whether " +"it's a method or a field. With the descriptor API, static methods and class " +"methods become possible, as well as more exotic constructs." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:169 +msgid "" +"Attribute descriptors are objects that live inside class objects, and have a " +"few attributes of their own:" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:172 +msgid ":attr:`~definition.__name__` is the attribute's name." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:174 +msgid ":attr:`__doc__` is the attribute's docstring." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:176 +msgid "" +"``__get__(object)`` is a method that retrieves the attribute value from " +"*object*." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:179 +msgid "``__set__(object, value)`` sets the attribute on *object* to *value*." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:181 +msgid "" +"``__delete__(object, value)`` deletes the *value* attribute of *object*." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:183 +msgid "" +"For example, when you write ``obj.x``, the steps that Python actually " +"performs are::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:189 +msgid "" +"For methods, :meth:`descriptor.__get__` returns a temporary object that's " +"callable, and wraps up the instance and the method to be called on it. This " +"is also why static methods and class methods are now possible; they have " +"descriptors that wrap up just the method, or the method and the class. As a " +"brief explanation of these new kinds of methods, static methods aren't " +"passed the instance, and therefore resemble regular functions. Class " +"methods are passed the class of the object, but not the object itself. " +"Static and class methods are defined like this::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:207 +msgid "" +"The :func:`staticmethod` function takes the function :func:`f`, and returns " +"it wrapped up in a descriptor so it can be stored in the class object. You " +"might expect there to be special syntax for creating such methods (``def " +"static f``, ``defstatic f()``, or something like that) but no such syntax " +"has been defined yet; that's been left for future versions of Python." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:213 +msgid "" +"More new features, such as slots and properties, are also implemented as new " +"kinds of descriptors, and it's not difficult to write a descriptor class " +"that does something novel. For example, it would be possible to write a " +"descriptor class that made it possible to write Eiffel-style preconditions " +"and postconditions for a method. A class that used this feature might be " +"defined like this::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:235 +msgid "" +"Note that a person using the new :func:`eiffelmethod` doesn't have to " +"understand anything about descriptors. This is why I think the new features " +"don't increase the basic complexity of the language. There will be a few " +"wizards who need to know about it in order to write :func:`eiffelmethod` or " +"the ZODB or whatever, but most users will just write code on top of the " +"resulting libraries and ignore the implementation details." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:244 +msgid "Multiple Inheritance: The Diamond Rule" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:246 +msgid "" +"Multiple inheritance has also been made more useful through changing the " +"rules under which names are resolved. Consider this set of classes (diagram " +"taken from :pep:`253` by Guido van Rossum)::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:264 +msgid "" +"The lookup rule for classic classes is simple but not very smart; the base " +"classes are searched depth-first, going from left to right. A reference to :" +"meth:`D.save` will search the classes :class:`D`, :class:`B`, and then :" +"class:`A`, where :meth:`save` would be found and returned. :meth:`C.save` " +"would never be found at all. This is bad, because if :class:`C`'s :meth:" +"`save` method is saving some internal state specific to :class:`C`, not " +"calling it will result in that state never getting saved." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:272 +msgid "" +"New-style classes follow a different algorithm that's a bit more complicated " +"to explain, but does the right thing in this situation. (Note that Python " +"2.3 changes this algorithm to one that produces the same results in most " +"cases, but produces more useful results for really complicated inheritance " +"graphs.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:277 +msgid "" +"List all the base classes, following the classic lookup rule and include a " +"class multiple times if it's visited repeatedly. In the above example, the " +"list of visited classes is [:class:`D`, :class:`B`, :class:`A`, :class:`C`, :" +"class:`A`]." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:282 +msgid "" +"Scan the list for duplicated classes. If any are found, remove all but one " +"occurrence, leaving the *last* one in the list. In the above example, the " +"list becomes [:class:`D`, :class:`B`, :class:`C`, :class:`A`] after dropping " +"duplicates." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:287 +msgid "" +"Following this rule, referring to :meth:`D.save` will return :meth:`C.save`, " +"which is the behaviour we're after. This lookup rule is the same as the one " +"followed by Common Lisp. A new built-in function, :func:`super`, provides a " +"way to get at a class's superclasses without having to reimplement Python's " +"algorithm. The most commonly used form will be ``super(class, obj)``, which " +"returns a bound superclass object (not the actual class object). This form " +"will be used in methods to call a method in the superclass; for example, :" +"class:`D`'s :meth:`save` method would look like this::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:303 +msgid "" +":func:`super` can also return unbound superclass objects when called as " +"``super(class)`` or ``super(class1, class2)``, but this probably won't often " +"be useful." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:309 +msgid "Attribute Access" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:311 +msgid "" +"A fair number of sophisticated Python classes define hooks for attribute " +"access using :meth:`__getattr__`; most commonly this is done for " +"convenience, to make code more readable by automatically mapping an " +"attribute access such as ``obj.parent`` into a method call such as ``obj." +"get_parent``. Python 2.2 adds some new ways of controlling attribute access." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:317 +msgid "" +"First, ``__getattr__(attr_name)`` is still supported by new-style classes, " +"and nothing about it has changed. As before, it will be called when an " +"attempt is made to access ``obj.foo`` and no attribute named ``foo`` is " +"found in the instance's dictionary." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:322 +msgid "" +"New-style classes also support a new method, " +"``__getattribute__(attr_name)``. The difference between the two methods is " +"that :meth:`__getattribute__` is *always* called whenever any attribute is " +"accessed, while the old :meth:`__getattr__` is only called if ``foo`` isn't " +"found in the instance's dictionary." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:328 +msgid "" +"However, Python 2.2's support for :dfn:`properties` will often be a simpler " +"way to trap attribute references. Writing a :meth:`__getattr__` method is " +"complicated because to avoid recursion you can't use regular attribute " +"accesses inside them, and instead have to mess around with the contents of :" +"attr:`~object.__dict__`. :meth:`__getattr__` methods also end up being " +"called by Python when it checks for other methods such as :meth:`__repr__` " +"or :meth:`__coerce__`, and so have to be written with this in mind. Finally, " +"calling a function on every attribute access results in a sizable " +"performance loss." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:337 +msgid "" +":class:`property` is a new built-in type that packages up three functions " +"that get, set, or delete an attribute, and a docstring. For example, if you " +"want to define a :attr:`size` attribute that's computed, but also settable, " +"you could write::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:357 +msgid "" +"That is certainly clearer and easier to write than a pair of :meth:" +"`__getattr__`/:meth:`__setattr__` methods that check for the :attr:`size` " +"attribute and handle it specially while retrieving all other attributes from " +"the instance's :attr:`~object.__dict__`. Accesses to :attr:`size` are also " +"the only ones which have to perform the work of calling a function, so " +"references to other attributes run at their usual speed." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:364 +msgid "" +"Finally, it's possible to constrain the list of attributes that can be " +"referenced on an object using the new :attr:`~object.__slots__` class " +"attribute. Python objects are usually very dynamic; at any time it's " +"possible to define a new attribute on an instance by just doing ``obj." +"new_attr=1``. A new-style class can define a class attribute named :attr:" +"`~object.__slots__` to limit the legal attributes to a particular set of " +"names. An example will make this clear::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:385 +msgid "" +"Note how you get an :exc:`AttributeError` on the attempt to assign to an " +"attribute not listed in :attr:`~object.__slots__`." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:392 +msgid "Related Links" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:394 +msgid "" +"This section has just been a quick overview of the new features, giving " +"enough of an explanation to start you programming, but many details have " +"been simplified or ignored. Where should you go to get a more complete " +"picture?" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:398 +msgid "" +"https://docs.python.org/dev/howto/descriptor.html is a lengthy tutorial " +"introduction to the descriptor features, written by Guido van Rossum. If my " +"description has whetted your appetite, go read this tutorial next, because " +"it goes into much more detail about the new features while still remaining " +"quite easy to read." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:403 +msgid "" +"Next, there are two relevant PEPs, :pep:`252` and :pep:`253`. :pep:`252` is " +"titled \"Making Types Look More Like Classes\", and covers the descriptor " +"API. :pep:`253` is titled \"Subtyping Built-in Types\", and describes the " +"changes to type objects that make it possible to subtype built-in objects. :" +"pep:`253` is the more complicated PEP of the two, and at a few points the " +"necessary explanations of types and meta-types may cause your head to " +"explode. Both PEPs were written and implemented by Guido van Rossum, with " +"substantial assistance from the rest of the Zope Corp. team." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:412 +msgid "" +"Finally, there's the ultimate authority: the source code. Most of the " +"machinery for the type handling is in :file:`Objects/typeobject.c`, but you " +"should only resort to it after all other avenues have been exhausted, " +"including posting a question to python-list or python-dev." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:421 +msgid "PEP 234: Iterators" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:423 +msgid "" +"Another significant addition to 2.2 is an iteration interface at both the C " +"and Python levels. Objects can define how they can be looped over by " +"callers." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:426 +msgid "" +"In Python versions up to 2.1, the usual way to make ``for item in obj`` work " +"is to define a :meth:`__getitem__` method that looks something like this::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:432 +msgid "" +":meth:`__getitem__` is more properly used to define an indexing operation on " +"an object so that you can write ``obj[5]`` to retrieve the sixth element. " +"It's a bit misleading when you're using this only to support :keyword:`for` " +"loops. Consider some file-like object that wants to be looped over; the " +"*index* parameter is essentially meaningless, as the class probably assumes " +"that a series of :meth:`__getitem__` calls will be made with *index* " +"incrementing by one each time. In other words, the presence of the :meth:" +"`__getitem__` method doesn't mean that using ``file[5]`` to randomly access " +"the sixth element will work, though it really should." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:442 +msgid "" +"In Python 2.2, iteration can be implemented separately, and :meth:" +"`__getitem__` methods can be limited to classes that really do support " +"random access. The basic idea of iterators is simple. A new built-in " +"function, ``iter(obj)`` or ``iter(C, sentinel)``, is used to get an " +"iterator. ``iter(obj)`` returns an iterator for the object *obj*, while " +"``iter(C, sentinel)`` returns an iterator that will invoke the callable " +"object *C* until it returns *sentinel* to signal that the iterator is done." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:450 +msgid "" +"Python classes can define an :meth:`__iter__` method, which should create " +"and return a new iterator for the object; if the object is its own iterator, " +"this method can just return ``self``. In particular, iterators will usually " +"be their own iterators. Extension types implemented in C can implement a :c:" +"member:`~PyTypeObject.tp_iter` function in order to return an iterator, and " +"extension types that want to behave as iterators can define a :c:member:" +"`~PyTypeObject.tp_iternext` function." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:457 +msgid "" +"So, after all this, what do iterators actually do? They have one required " +"method, :meth:`next`, which takes no arguments and returns the next value. " +"When there are no more values to be returned, calling :meth:`next` should " +"raise the :exc:`StopIteration` exception. ::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:478 +msgid "" +"In 2.2, Python's :keyword:`for` statement no longer expects a sequence; it " +"expects something for which :func:`iter` will return an iterator. For " +"backward compatibility and convenience, an iterator is automatically " +"constructed for sequences that don't implement :meth:`__iter__` or a :c:" +"member:`~PyTypeObject.tp_iter` slot, so ``for i in [1,2,3]`` will still " +"work. Wherever the Python interpreter loops over a sequence, it's been " +"changed to use the iterator protocol. This means you can do things like " +"this::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:492 +msgid "" +"Iterator support has been added to some of Python's basic types. Calling :" +"func:`iter` on a dictionary will return an iterator which loops over its " +"keys::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:512 +msgid "" +"That's just the default behaviour. If you want to iterate over keys, " +"values, or key/value pairs, you can explicitly call the :meth:`iterkeys`, :" +"meth:`itervalues`, or :meth:`iteritems` methods to get an appropriate " +"iterator. In a minor related change, the :keyword:`in` operator now works on " +"dictionaries, so ``key in dict`` is now equivalent to ``dict.has_key(key)``." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:518 +msgid "" +"Files also provide an iterator, which calls the :meth:`readline` method " +"until there are no more lines in the file. This means you can now read each " +"line of a file using code like this::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:526 +msgid "" +"Note that you can only go forward in an iterator; there's no way to get the " +"previous element, reset the iterator, or make a copy of it. An iterator " +"object could provide such additional capabilities, but the iterator protocol " +"only requires a :meth:`next` method." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:535 +msgid ":pep:`234` - Iterators" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:535 +msgid "" +"Written by Ka-Ping Yee and GvR; implemented by the Python Labs crew, mostly " +"by GvR and Tim Peters." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:542 ../Doc/whatsnew/2.3.rst:126 +msgid "PEP 255: Simple Generators" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:544 +msgid "" +"Generators are another new feature, one that interacts with the introduction " +"of iterators." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:547 +msgid "" +"You're doubtless familiar with how function calls work in Python or C. When " +"you call a function, it gets a private namespace where its local variables " +"are created. When the function reaches a :keyword:`return` statement, the " +"local variables are destroyed and the resulting value is returned to the " +"caller. A later call to the same function will get a fresh new set of local " +"variables. But, what if the local variables weren't thrown away on exiting a " +"function? What if you could later resume the function where it left off? " +"This is what generators provide; they can be thought of as resumable " +"functions." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:556 ../Doc/whatsnew/2.3.rst:145 +msgid "Here's the simplest example of a generator function::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:562 +msgid "" +"A new keyword, :keyword:`yield`, was introduced for generators. Any " +"function containing a :keyword:`yield` statement is a generator function; " +"this is detected by Python's bytecode compiler which compiles the function " +"specially as a result. Because a new keyword was introduced, generators " +"must be explicitly enabled in a module by including a ``from __future__ " +"import generators`` statement near the top of the module's source code. In " +"Python 2.3 this statement will become unnecessary." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:570 +msgid "" +"When you call a generator function, it doesn't return a single value; " +"instead it returns a generator object that supports the iterator protocol. " +"On executing the :keyword:`yield` statement, the generator outputs the value " +"of ``i``, similar to a :keyword:`return` statement. The big difference " +"between :keyword:`yield` and a :keyword:`return` statement is that on " +"reaching a :keyword:`yield` the generator's state of execution is suspended " +"and local variables are preserved. On the next call to the generator's " +"``next()`` method, the function will resume executing immediately after the :" +"keyword:`yield` statement. (For complicated reasons, the :keyword:`yield` " +"statement isn't allowed inside the :keyword:`try` block of a :keyword:" +"`try`...\\ :keyword:`finally` statement; read :pep:`255` for a full " +"explanation of the interaction between :keyword:`yield` and exceptions.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:583 ../Doc/whatsnew/2.3.rst:169 +msgid "Here's a sample usage of the :func:`generate_ints` generator::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:600 ../Doc/whatsnew/2.3.rst:186 +msgid "" +"You could equally write ``for i in generate_ints(5)``, or ``a,b,c = " +"generate_ints(3)``." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:603 ../Doc/whatsnew/2.3.rst:189 +msgid "" +"Inside a generator function, the :keyword:`return` statement can only be " +"used without a value, and signals the end of the procession of values; " +"afterwards the generator cannot return any further values. :keyword:`return` " +"with a value, such as ``return 5``, is a syntax error inside a generator " +"function. The end of the generator's results can also be indicated by " +"raising :exc:`StopIteration` manually, or by just letting the flow of " +"execution fall off the bottom of the function." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:611 ../Doc/whatsnew/2.3.rst:197 +msgid "" +"You could achieve the effect of generators manually by writing your own " +"class and storing all the local variables of the generator as instance " +"variables. For example, returning a list of integers could be done by " +"setting ``self.count`` to 0, and having the :meth:`next` method increment " +"``self.count`` and return it. However, for a moderately complicated " +"generator, writing a corresponding class would be much messier. :file:`Lib/" +"test/test_generators.py` contains a number of more interesting examples. " +"The simplest one implements an in-order traversal of a tree using generators " +"recursively. ::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:629 ../Doc/whatsnew/2.3.rst:215 +msgid "" +"Two other examples in :file:`Lib/test/test_generators.py` produce solutions " +"for the N-Queens problem (placing $N$ queens on an $NxN$ chess board so that " +"no queen threatens another) and the Knight's Tour (a route that takes a " +"knight to every square of an $NxN$ chessboard without visiting any square " +"twice)." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:634 ../Doc/whatsnew/2.3.rst:220 +msgid "" +"The idea of generators comes from other programming languages, especially " +"Icon (https://www.cs.arizona.edu/icon/), where the idea of generators is " +"central. In Icon, every expression and function call behaves like a " +"generator. One example from \"An Overview of the Icon Programming Language" +"\" at https://www.cs.arizona.edu/icon/docs/ipd266.htm gives an idea of what " +"this looks like::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:644 ../Doc/whatsnew/2.3.rst:230 +msgid "" +"In Icon the :func:`find` function returns the indexes at which the substring " +"\"or\" is found: 3, 23, 33. In the :keyword:`if` statement, ``i`` is first " +"assigned a value of 3, but 3 is less than 5, so the comparison fails, and " +"Icon retries it with the second value of 23. 23 is greater than 5, so the " +"comparison now succeeds, and the code prints the value 23 to the screen." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:650 +msgid "" +"Python doesn't go nearly as far as Icon in adopting generators as a central " +"concept. Generators are considered a new part of the core Python language, " +"but learning or using them isn't compulsory; if they don't solve any " +"problems that you have, feel free to ignore them. One novel feature of " +"Python's interface as compared to Icon's is that a generator's state is " +"represented as a concrete object (the iterator) that can be passed around to " +"other functions or stored in a data structure." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:662 ../Doc/whatsnew/2.3.rst:248 +msgid ":pep:`255` - Simple Generators" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:662 ../Doc/whatsnew/2.3.rst:248 +msgid "" +"Written by Neil Schemenauer, Tim Peters, Magnus Lie Hetland. Implemented " +"mostly by Neil Schemenauer and Tim Peters, with other fixes from the Python " +"Labs crew." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:669 ../Doc/whatsnew/2.4.rst:90 +msgid "PEP 237: Unifying Long Integers and Integers" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:671 +msgid "" +"In recent versions, the distinction between regular integers, which are 32-" +"bit values on most machines, and long integers, which can be of arbitrary " +"size, was becoming an annoyance. For example, on platforms that support " +"files larger than ``2**32`` bytes, the :meth:`tell` method of file objects " +"has to return a long integer. However, there were various bits of Python " +"that expected plain integers and would raise an error if a long integer was " +"provided instead. For example, in Python 1.5, only regular integers could " +"be used as a slice index, and ``'abc'[1L:]`` would raise a :exc:`TypeError` " +"exception with the message 'slice index must be int'." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:681 +msgid "" +"Python 2.2 will shift values from short to long integers as required. The " +"'L' suffix is no longer needed to indicate a long integer literal, as now " +"the compiler will choose the appropriate type. (Using the 'L' suffix will " +"be discouraged in future 2.x versions of Python, triggering a warning in " +"Python 2.4, and probably dropped in Python 3.0.) Many operations that used " +"to raise an :exc:`OverflowError` will now return a long integer as their " +"result. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:694 +msgid "" +"In most cases, integers and long integers will now be treated identically. " +"You can still distinguish them with the :func:`type` built-in function, but " +"that's rarely needed." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:702 ../Doc/whatsnew/2.4.rst:108 +msgid ":pep:`237` - Unifying Long Integers and Integers" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:702 +msgid "" +"Written by Moshe Zadka and Guido van Rossum. Implemented mostly by Guido " +"van Rossum." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:709 +msgid "PEP 238: Changing the Division Operator" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:711 +msgid "" +"The most controversial change in Python 2.2 heralds the start of an effort " +"to fix an old design flaw that's been in Python from the beginning. " +"Currently Python's division operator, ``/``, behaves like C's division " +"operator when presented with two integer arguments: it returns an integer " +"result that's truncated down when there would be a fractional part. For " +"example, ``3/2`` is 1, not 1.5, and ``(-1)/2`` is -1, not -0.5. This means " +"that the results of division can vary unexpectedly depending on the type of " +"the two operands and because Python is dynamically typed, it can be " +"difficult to determine the possible types of the operands." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:721 +msgid "" +"(The controversy is over whether this is *really* a design flaw, and whether " +"it's worth breaking existing code to fix this. It's caused endless " +"discussions on python-dev, and in July 2001 erupted into a storm of acidly " +"sarcastic postings on :newsgroup:`comp.lang.python`. I won't argue for " +"either side here and will stick to describing what's implemented in 2.2. " +"Read :pep:`238` for a summary of arguments and counter-arguments.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:728 +msgid "" +"Because this change might break code, it's being introduced very gradually. " +"Python 2.2 begins the transition, but the switch won't be complete until " +"Python 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:732 +msgid "" +"First, I'll borrow some terminology from :pep:`238`. \"True division\" is " +"the division that most non-programmers are familiar with: 3/2 is 1.5, 1/4 is " +"0.25, and so forth. \"Floor division\" is what Python's ``/`` operator " +"currently does when given integer operands; the result is the floor of the " +"value returned by true division. \"Classic division\" is the current mixed " +"behaviour of ``/``; it returns the result of floor division when the " +"operands are integers, and returns the result of true division when one of " +"the operands is a floating-point number." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:740 +msgid "Here are the changes 2.2 introduces:" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:742 +msgid "" +"A new operator, ``//``, is the floor division operator. (Yes, we know it " +"looks like C++'s comment symbol.) ``//`` *always* performs floor division " +"no matter what the types of its operands are, so ``1 // 2`` is 0 and " +"``1.0 // 2.0`` is also 0.0." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:747 +msgid "" +"``//`` is always available in Python 2.2; you don't need to enable it using " +"a ``__future__`` statement." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:750 +msgid "" +"By including a ``from __future__ import division`` in a module, the ``/`` " +"operator will be changed to return the result of true division, so ``1/2`` " +"is 0.5. Without the ``__future__`` statement, ``/`` still means classic " +"division. The default meaning of ``/`` will not change until Python 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:755 +msgid "" +"Classes can define methods called :meth:`__truediv__` and :meth:" +"`__floordiv__` to overload the two division operators. At the C level, " +"there are also slots in the :c:type:`PyNumberMethods` structure so extension " +"types can define the two operators." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:760 +msgid "" +"Python 2.2 supports some command-line arguments for testing whether code " +"will work with the changed division semantics. Running python with :option:" +"`-Q warn` will cause a warning to be issued whenever division is applied to " +"two integers. You can use this to find code that's affected by the change " +"and fix it. By default, Python 2.2 will simply perform classic division " +"without a warning; the warning will be turned on by default in Python 2.3." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:770 +msgid ":pep:`238` - Changing the Division Operator" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:771 +msgid "" +"Written by Moshe Zadka and Guido van Rossum. Implemented by Guido van " +"Rossum.." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:777 +msgid "Unicode Changes" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:779 +msgid "" +"Python's Unicode support has been enhanced a bit in 2.2. Unicode strings " +"are usually stored as UCS-2, as 16-bit unsigned integers. Python 2.2 can " +"also be compiled to use UCS-4, 32-bit unsigned integers, as its internal " +"encoding by supplying :option:`--enable-unicode=ucs4` to the configure " +"script. (It's also possible to specify :option:`--disable-unicode` to " +"completely disable Unicode support.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:786 +msgid "" +"When built to use UCS-4 (a \"wide Python\"), the interpreter can natively " +"handle Unicode characters from U+000000 to U+110000, so the range of legal " +"values for the :func:`unichr` function is expanded accordingly. Using an " +"interpreter compiled to use UCS-2 (a \"narrow Python\"), values greater than " +"65535 will still cause :func:`unichr` to raise a :exc:`ValueError` " +"exception. This is all described in :pep:`261`, \"Support for 'wide' Unicode " +"characters\"; consult it for further details." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:794 +msgid "" +"Another change is simpler to explain. Since their introduction, Unicode " +"strings have supported an :meth:`encode` method to convert the string to a " +"selected encoding such as UTF-8 or Latin-1. A symmetric " +"``decode([*encoding*])`` method has been added to 8-bit strings (though not " +"to Unicode strings) in 2.2. :meth:`decode` assumes that the string is in the " +"specified encoding and decodes it, returning whatever is returned by the " +"codec." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:801 +msgid "" +"Using this new feature, codecs have been added for tasks not directly " +"related to Unicode. For example, codecs have been added for uu-encoding, " +"MIME's base64 encoding, and compression with the :mod:`zlib` module::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:822 +msgid "" +"To convert a class instance to Unicode, a :meth:`__unicode__` method can be " +"defined by a class, analogous to :meth:`__str__`." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:825 +msgid "" +":meth:`encode`, :meth:`decode`, and :meth:`__unicode__` were implemented by " +"Marc-André Lemburg. The changes to support using UCS-4 internally were " +"implemented by Fredrik Lundh and Martin von Löwis." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:832 +msgid ":pep:`261` - Support for 'wide' Unicode characters" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:833 +msgid "Written by Paul Prescod." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:841 +msgid "" +"In Python 2.1, statically nested scopes were added as an optional feature, " +"to be enabled by a ``from __future__ import nested_scopes`` directive. In " +"2.2 nested scopes no longer need to be specially enabled, and are now always " +"present. The rest of this section is a copy of the description of nested " +"scopes from my \"What's New in Python 2.1\" document; if you read it when " +"2.1 came out, you can skip the rest of this section." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:848 +msgid "" +"The largest change introduced in Python 2.1, and made complete in 2.2, is to " +"Python's scoping rules. In Python 2.0, at any given time there are at most " +"three namespaces used to look up variable names: local, module-level, and " +"the built-in namespace. This often surprised people because it didn't match " +"their intuitive expectations. For example, a nested recursive function " +"definition doesn't work::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:879 +msgid "" +"The most significant change to Python 2.2 is that static scoping has been " +"added to the language to fix this problem. As a first effect, the " +"``name=name`` default argument is now unnecessary in the above example. Put " +"simply, when a given variable name is not assigned a value within a function " +"(by an assignment, or the :keyword:`def`, :keyword:`class`, or :keyword:" +"`import` statements), references to the variable will be looked up in the " +"local namespace of the enclosing scope. A more detailed explanation of the " +"rules, and a dissection of the implementation, can be found in the PEP." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:936 +msgid "" +"The :mod:`xmlrpclib` module was contributed to the standard library by " +"Fredrik Lundh, providing support for writing XML-RPC clients. XML-RPC is a " +"simple remote procedure call protocol built on top of HTTP and XML. For " +"example, the following snippet retrieves a list of RSS channels from the " +"O'Reilly Network, and then lists the recent headlines for one channel::" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:959 +msgid "" +"The :mod:`SimpleXMLRPCServer` module makes it easy to create straightforward " +"XML-RPC servers. See http://www.xmlrpc.com/ for more information about XML-" +"RPC." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:962 +msgid "" +"The new :mod:`hmac` module implements the HMAC algorithm described by :rfc:" +"`2104`. (Contributed by Gerhard Häring.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:965 +msgid "" +"Several functions that originally returned lengthy tuples now return pseudo- " +"sequences that still behave like tuples but also have mnemonic attributes " +"such as memberst_mtime or :attr:`tm_year`. The enhanced functions include :" +"func:`stat`, :func:`fstat`, :func:`statvfs`, and :func:`fstatvfs` in the :" +"mod:`os` module, and :func:`localtime`, :func:`gmtime`, and :func:`strptime` " +"in the :mod:`time` module." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:972 +msgid "" +"For example, to obtain a file's size using the old tuples, you'd end up " +"writing something like ``file_size = os.stat(filename)[stat.ST_SIZE]``, but " +"now this can be written more clearly as ``file_size = os.stat(filename)." +"st_size``." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:976 +msgid "The original patch for this feature was contributed by Nick Mathewson." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:978 +msgid "" +"The Python profiler has been extensively reworked and various errors in its " +"output have been corrected. (Contributed by Fred L. Drake, Jr. and Tim " +"Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:981 +msgid "" +"The :mod:`socket` module can be compiled to support IPv6; specify the :" +"option:`--enable-ipv6` option to Python's configure script. (Contributed by " +"Jun-ichiro \"itojun\" Hagino.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:985 +msgid "" +"Two new format characters were added to the :mod:`struct` module for 64-bit " +"integers on platforms that support the C :c:type:`long long` type. ``q`` is " +"for a signed 64-bit integer, and ``Q`` is for an unsigned one. The value is " +"returned in Python's long integer type. (Contributed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:990 +msgid "" +"In the interpreter's interactive mode, there's a new built-in function :func:" +"`help` that uses the :mod:`pydoc` module introduced in Python 2.1 to provide " +"interactive help. ``help(object)`` displays any available help text about " +"*object*. :func:`help` with no argument puts you in an online help utility, " +"where you can enter the names of functions, classes, or modules to read " +"their help text. (Contributed by Guido van Rossum, using Ka-Ping Yee's :mod:" +"`pydoc` module.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:998 +msgid "" +"Various bugfixes and performance improvements have been made to the SRE " +"engine underlying the :mod:`re` module. For example, the :func:`re.sub` " +"and :func:`re.split` functions have been rewritten in C. Another " +"contributed patch speeds up certain Unicode character ranges by a factor of " +"two, and a new :meth:`finditer` method that returns an iterator over all " +"the non-overlapping matches in a given string. (SRE is maintained by " +"Fredrik Lundh. The BIGCHARSET patch was contributed by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1006 +msgid "" +"The :mod:`smtplib` module now supports :rfc:`2487`, \"Secure SMTP over TLS" +"\", so it's now possible to encrypt the SMTP traffic between a Python " +"program and the mail transport agent being handed a message. :mod:`smtplib` " +"also supports SMTP authentication. (Contributed by Gerhard Häring.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1011 +msgid "" +"The :mod:`imaplib` module, maintained by Piers Lauder, has support for " +"several new extensions: the NAMESPACE extension defined in :rfc:`2342`, " +"SORT, GETACL and SETACL. (Contributed by Anthony Baxter and Michel " +"Pelletier.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1015 +msgid "" +"The :mod:`rfc822` module's parsing of email addresses is now compliant with :" +"rfc:`2822`, an update to :rfc:`822`. (The module's name is *not* going to " +"be changed to ``rfc2822``.) A new package, :mod:`email`, has also been " +"added for parsing and generating e-mail messages. (Contributed by Barry " +"Warsaw, and arising out of his work on Mailman.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1021 +msgid "" +"The :mod:`difflib` module now contains a new :class:`Differ` class for " +"producing human-readable lists of changes (a \"delta\") between two " +"sequences of lines of text. There are also two generator functions, :func:" +"`ndiff` and :func:`restore`, which respectively return a delta from two " +"sequences, or one of the original sequences from a delta. (Grunt work " +"contributed by David Goodger, from ndiff.py code by Tim Peters who then did " +"the generatorization.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1028 +msgid "" +"New constants :const:`ascii_letters`, :const:`ascii_lowercase`, and :const:" +"`ascii_uppercase` were added to the :mod:`string` module. There were " +"several modules in the standard library that used :const:`string.letters` to " +"mean the ranges A-Za-z, but that assumption is incorrect when locales are in " +"use, because :const:`string.letters` varies depending on the set of legal " +"characters defined by the current locale. The buggy modules have all been " +"fixed to use :const:`ascii_letters` instead. (Reported by an unknown person; " +"fixed by Fred L. Drake, Jr.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1037 +msgid "" +"The :mod:`mimetypes` module now makes it easier to use alternative MIME-type " +"databases by the addition of a :class:`MimeTypes` class, which takes a list " +"of filenames to be parsed. (Contributed by Fred L. Drake, Jr.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1041 +msgid "" +"A :class:`Timer` class was added to the :mod:`threading` module that allows " +"scheduling an activity to happen at some future time. (Contributed by " +"Itamar Shtull-Trauring.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1049 +msgid "Interpreter Changes and Fixes" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1051 +msgid "" +"Some of the changes only affect people who deal with the Python interpreter " +"at the C level because they're writing Python extension modules, embedding " +"the interpreter, or just hacking on the interpreter itself. If you only " +"write Python code, none of the changes described here will affect you very " +"much." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1056 +msgid "" +"Profiling and tracing functions can now be implemented in C, which can " +"operate at much higher speeds than Python-based functions and should reduce " +"the overhead of profiling and tracing. This will be of interest to authors " +"of development environments for Python. Two new C functions were added to " +"Python's API, :c:func:`PyEval_SetProfile` and :c:func:`PyEval_SetTrace`. The " +"existing :func:`sys.setprofile` and :func:`sys.settrace` functions still " +"exist, and have simply been changed to use the new C-level interface. " +"(Contributed by Fred L. Drake, Jr.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1065 +msgid "" +"Another low-level API, primarily of interest to implementors of Python " +"debuggers and development tools, was added. :c:func:" +"`PyInterpreterState_Head` and :c:func:`PyInterpreterState_Next` let a caller " +"walk through all the existing interpreter objects; :c:func:" +"`PyInterpreterState_ThreadHead` and :c:func:`PyThreadState_Next` allow " +"looping over all the thread states for a given interpreter. (Contributed by " +"David Beazley.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1072 +msgid "" +"The C-level interface to the garbage collector has been changed to make it " +"easier to write extension types that support garbage collection and to debug " +"misuses of the functions. Various functions have slightly different " +"semantics, so a bunch of functions had to be renamed. Extensions that use " +"the old API will still compile but will *not* participate in garbage " +"collection, so updating them for 2.2 should be considered fairly high " +"priority." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1079 +msgid "" +"To upgrade an extension module to the new API, perform the following steps:" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1081 +msgid "Rename :c:func:`Py_TPFLAGS_GC` to :c:func:`PyTPFLAGS_HAVE_GC`." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1084 +msgid "" +"Use :c:func:`PyObject_GC_New` or :c:func:`PyObject_GC_NewVar` to allocate" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1084 +msgid "objects, and :c:func:`PyObject_GC_Del` to deallocate them." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1087 +msgid "Rename :c:func:`PyObject_GC_Init` to :c:func:`PyObject_GC_Track` and" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1087 +msgid ":c:func:`PyObject_GC_Fini` to :c:func:`PyObject_GC_UnTrack`." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1089 +msgid "Remove :c:func:`PyGC_HEAD_SIZE` from object size calculations." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1091 +msgid "" +"Remove calls to :c:func:`PyObject_AS_GC` and :c:func:`PyObject_FROM_GC`." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1093 +msgid "" +"A new ``et`` format sequence was added to :c:func:`PyArg_ParseTuple`; ``et`` " +"takes both a parameter and an encoding name, and converts the parameter to " +"the given encoding if the parameter turns out to be a Unicode string, or " +"leaves it alone if it's an 8-bit string, assuming it to already be in the " +"desired encoding. This differs from the ``es`` format character, which " +"assumes that 8-bit strings are in Python's default ASCII encoding and " +"converts them to the specified new encoding. (Contributed by M.-A. Lemburg, " +"and used for the MBCS support on Windows described in the following section.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1102 +msgid "" +"A different argument parsing function, :c:func:`PyArg_UnpackTuple`, has been " +"added that's simpler and presumably faster. Instead of specifying a format " +"string, the caller simply gives the minimum and maximum number of arguments " +"expected, and a set of pointers to :c:type:`PyObject\\*` variables that will " +"be filled in with argument values." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1108 +msgid "" +"Two new flags :const:`METH_NOARGS` and :const:`METH_O` are available in " +"method definition tables to simplify implementation of methods with no " +"arguments or a single untyped argument. Calling such methods is more " +"efficient than calling a corresponding method that uses :const:" +"`METH_VARARGS`. Also, the old :const:`METH_OLDARGS` style of writing C " +"methods is now officially deprecated." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1114 +msgid "" +"Two new wrapper functions, :c:func:`PyOS_snprintf` and :c:func:" +"`PyOS_vsnprintf` were added to provide cross-platform implementations for " +"the relatively new :c:func:`snprintf` and :c:func:`vsnprintf` C lib APIs. In " +"contrast to the standard :c:func:`sprintf` and :c:func:`vsprintf` functions, " +"the Python versions check the bounds of the buffer used to protect against " +"buffer overruns. (Contributed by M.-A. Lemburg.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1121 +msgid "" +"The :c:func:`_PyTuple_Resize` function has lost an unused parameter, so now " +"it takes 2 parameters instead of 3. The third argument was never used, and " +"can simply be discarded when porting code from earlier versions to Python " +"2.2." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1131 +msgid "" +"As usual there were a bunch of other improvements and bugfixes scattered " +"throughout the source tree. A search through the CVS change logs finds " +"there were 527 patches applied and 683 bugs fixed between Python 2.1 and " +"2.2; 2.2.1 applied 139 patches and fixed 143 bugs; 2.2.2 applied 106 patches " +"and fixed 82 bugs. These figures are likely to be underestimates." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1137 ../Doc/whatsnew/2.3.rst:1973 +msgid "Some of the more notable changes are:" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1139 +msgid "" +"The code for the MacOS port for Python, maintained by Jack Jansen, is now " +"kept in the main Python CVS tree, and many changes have been made to support " +"MacOS X." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1142 +msgid "" +"The most significant change is the ability to build Python as a framework, " +"enabled by supplying the :option:`--enable-framework` option to the " +"configure script when compiling Python. According to Jack Jansen, \"This " +"installs a self- contained Python installation plus the OS X framework \"glue" +"\" into :file:`/Library/Frameworks/Python.framework` (or another location of " +"choice). For now there is little immediate added benefit to this (actually, " +"there is the disadvantage that you have to change your PATH to be able to " +"find Python), but it is the basis for creating a full-blown Python " +"application, porting the MacPython IDE, possibly using Python as a standard " +"OSA scripting language and much more.\"" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1153 +msgid "" +"Most of the MacPython toolbox modules, which interface to MacOS APIs such as " +"windowing, QuickTime, scripting, etc. have been ported to OS X, but they've " +"been left commented out in :file:`setup.py`. People who want to experiment " +"with these modules can uncomment them manually." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1176 +msgid "" +"Keyword arguments passed to built-in functions that don't take them now " +"cause a :exc:`TypeError` exception to be raised, with the message " +"\"*function* takes no keyword arguments\"." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1180 +msgid "" +"Weak references, added in Python 2.1 as an extension module, are now part of " +"the core because they're used in the implementation of new-style classes. " +"The :exc:`ReferenceError` exception has therefore moved from the :mod:" +"`weakref` module to become a built-in exception." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1185 +msgid "" +"A new script, :file:`Tools/scripts/cleanfuture.py` by Tim Peters, " +"automatically removes obsolete ``__future__`` statements from Python source " +"code." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1189 +msgid "" +"An additional *flags* argument has been added to the built-in function :func:" +"`compile`, so the behaviour of ``__future__`` statements can now be " +"correctly observed in simulated shells, such as those presented by IDLE and " +"other development environments. This is described in :pep:`264`. " +"(Contributed by Michael Hudson.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1195 +msgid "" +"The new license introduced with Python 1.6 wasn't GPL-compatible. This is " +"fixed by some minor textual changes to the 2.2 license, so it's now legal to " +"embed Python inside a GPLed program again. Note that Python itself is not " +"GPLed, but instead is under a license that's essentially equivalent to the " +"BSD license, same as it always was. The license changes were also applied " +"to the Python 2.0.1 and 2.1.1 releases." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1202 +msgid "" +"When presented with a Unicode filename on Windows, Python will now convert " +"it to an MBCS encoded string, as used by the Microsoft file APIs. As MBCS " +"is explicitly used by the file APIs, Python's choice of ASCII as the default " +"encoding turns out to be an annoyance. On Unix, the locale's character set " +"is used if ``locale.nl_langinfo(CODESET)`` is available. (Windows support " +"was contributed by Mark Hammond with assistance from Marc-André Lemburg. " +"Unix support was added by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1210 +msgid "" +"Large file support is now enabled on Windows. (Contributed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1212 +msgid "" +"The :file:`Tools/scripts/ftpmirror.py` script now parses a :file:`.netrc` " +"file, if you have one. (Contributed by Mike Romberg.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1215 +msgid "" +"Some features of the object returned by the :func:`xrange` function are now " +"deprecated, and trigger warnings when they're accessed; they'll disappear in " +"Python 2.3. :class:`xrange` objects tried to pretend they were full sequence " +"types by supporting slicing, sequence multiplication, and the :keyword:`in` " +"operator, but these features were rarely used and therefore buggy. The :" +"meth:`tolist` method and the :attr:`start`, :attr:`stop`, and :attr:`step` " +"attributes are also being deprecated. At the C level, the fourth argument " +"to the :c:func:`PyRange_New` function, ``repeat``, has also been deprecated." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1224 +msgid "" +"There were a bunch of patches to the dictionary implementation, mostly to " +"fix potential core dumps if a dictionary contains objects that sneakily " +"changed their hash value, or mutated the dictionary they were contained in. " +"For a while python-dev fell into a gentle rhythm of Michael Hudson finding a " +"case that dumped core, Tim Peters fixing the bug, Michael finding another " +"case, and round and round it went." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1231 +msgid "" +"On Windows, Python can now be compiled with Borland C thanks to a number of " +"patches contributed by Stephen Hansen, though the result isn't fully " +"functional yet. (But this *is* progress...)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1235 +msgid "" +"Another Windows enhancement: Wise Solutions generously offered PythonLabs " +"use of their InstallerMaster 8.1 system. Earlier PythonLabs Windows " +"installers used Wise 5.0a, which was beginning to show its age. (Packaged " +"up by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1239 +msgid "" +"Files ending in ``.pyw`` can now be imported on Windows. ``.pyw`` is a " +"Windows-only thing, used to indicate that a script needs to be run using " +"PYTHONW.EXE instead of PYTHON.EXE in order to prevent a DOS console from " +"popping up to display the output. This patch makes it possible to import " +"such scripts, in case they're also usable as modules. (Implemented by David " +"Bolen.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1245 +msgid "" +"On platforms where Python uses the C :c:func:`dlopen` function to load " +"extension modules, it's now possible to set the flags used by :c:func:" +"`dlopen` using the :func:`sys.getdlopenflags` and :func:`sys.setdlopenflags` " +"functions. (Contributed by Bram Stolk.)" +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1250 +msgid "" +"The :func:`pow` built-in function no longer supports 3 arguments when " +"floating-point numbers are supplied. ``pow(x, y, z)`` returns ``(x**y) % " +"z``, but this is never useful for floating point numbers, and the final " +"result varies unpredictably depending on the platform. A call such as " +"``pow(2.0, 8.0, 7.0)`` will now raise a :exc:`TypeError` exception." +msgstr "" + +#: ../Doc/whatsnew/2.2.rst:1262 +msgid "" +"The author would like to thank the following people for offering " +"suggestions, corrections and assistance with various drafts of this article: " +"Fred Bremmer, Keith Briggs, Andrew Dalke, Fred L. Drake, Jr., Carel " +"Fellinger, David Goodger, Mark Hammond, Stephen Hansen, Michael Hudson, Jack " +"Jansen, Marc-André Lemburg, Martin von Löwis, Fredrik Lundh, Michael McLay, " +"Nick Mathewson, Paul Moore, Gustavo Niemeyer, Don O'Donnell, Joonas " +"Paalasma, Tim Peters, Jens Quade, Tom Reinhardt, Neil Schemenauer, Guido van " +"Rossum, Greg Ward, Edward Welbourne." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:3 +msgid "What's New in Python 2.3" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:11 +msgid "" +"This article explains the new features in Python 2.3. Python 2.3 was " +"released on July 29, 2003." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:14 +msgid "" +"The main themes for Python 2.3 are polishing some of the features added in " +"2.2, adding various small but useful enhancements to the core language, and " +"expanding the standard library. The new object model introduced in the " +"previous version has benefited from 18 months of bugfixes and from " +"optimization efforts that have improved the performance of new-style " +"classes. A few new built-in functions have been added such as :func:`sum` " +"and :func:`enumerate`. The :keyword:`in` operator can now be used for " +"substring searches (e.g. ``\"ab\" in \"abc\"`` returns :const:`True`)." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:23 +msgid "" +"Some of the many new library features include Boolean, set, heap, and date/" +"time data types, the ability to import modules from ZIP-format archives, " +"metadata support for the long-awaited Python catalog, an updated version of " +"IDLE, and modules for logging messages, wrapping text, parsing CSV files, " +"processing command-line options, using BerkeleyDB databases... the list of " +"new and enhanced modules is lengthy." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:30 +msgid "" +"This article doesn't attempt to provide a complete specification of the new " +"features, but instead provides a convenient overview. For full details, you " +"should refer to the documentation for Python 2.3, such as the Python Library " +"Reference and the Python Reference Manual. If you want to understand the " +"complete implementation and design rationale, refer to the PEP for a " +"particular new feature." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:41 +msgid "PEP 218: A Standard Set Datatype" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:43 +msgid "" +"The new :mod:`sets` module contains an implementation of a set datatype. " +"The :class:`Set` class is for mutable sets, sets that can have members added " +"and removed. The :class:`ImmutableSet` class is for sets that can't be " +"modified, and instances of :class:`ImmutableSet` can therefore be used as " +"dictionary keys. Sets are built on top of dictionaries, so the elements " +"within a set must be hashable." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:50 +msgid "Here's a simple example::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:66 +msgid "" +"The union and intersection of sets can be computed with the :meth:`union` " +"and :meth:`intersection` methods; an alternative notation uses the bitwise " +"operators ``&`` and ``|``. Mutable sets also have in-place versions of these " +"methods, :meth:`union_update` and :meth:`intersection_update`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:86 +msgid "" +"It's also possible to take the symmetric difference of two sets. This is " +"the set of all elements in the union that aren't in the intersection. " +"Another way of putting it is that the symmetric difference contains all " +"elements that are in exactly one set. Again, there's an alternative " +"notation (``^``), and an in- place version with the ungainly name :meth:" +"`symmetric_difference_update`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:100 +msgid "" +"There are also :meth:`issubset` and :meth:`issuperset` methods for checking " +"whether one set is a subset or superset of another::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:117 ../Doc/whatsnew/2.4.rst:83 +msgid ":pep:`218` - Adding a Built-In Set Object Type" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:117 +msgid "" +"PEP written by Greg V. Wilson. Implemented by Greg V. Wilson, Alex Martelli, " +"and GvR." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:128 +msgid "" +"In Python 2.2, generators were added as an optional feature, to be enabled " +"by a ``from __future__ import generators`` directive. In 2.3 generators no " +"longer need to be specially enabled, and are now always present; this means " +"that :keyword:`yield` is now always a keyword. The rest of this section is " +"a copy of the description of generators from the \"What's New in Python " +"2.2\" document; if you read it back when Python 2.2 came out, you can skip " +"the rest of this section." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:136 +msgid "" +"You're doubtless familiar with how function calls work in Python or C. When " +"you call a function, it gets a private namespace where its local variables " +"are created. When the function reaches a :keyword:`return` statement, the " +"local variables are destroyed and the resulting value is returned to the " +"caller. A later call to the same function will get a fresh new set of local " +"variables. But, what if the local variables weren't thrown away on exiting a " +"function? What if you could later resume the function where it left off? " +"This is what generators provide; they can be thought of as resumable " +"functions." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:151 +msgid "" +"A new keyword, :keyword:`yield`, was introduced for generators. Any " +"function containing a :keyword:`yield` statement is a generator function; " +"this is detected by Python's bytecode compiler which compiles the function " +"specially as a result." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:156 +msgid "" +"When you call a generator function, it doesn't return a single value; " +"instead it returns a generator object that supports the iterator protocol. " +"On executing the :keyword:`yield` statement, the generator outputs the value " +"of ``i``, similar to a :keyword:`return` statement. The big difference " +"between :keyword:`yield` and a :keyword:`return` statement is that on " +"reaching a :keyword:`yield` the generator's state of execution is suspended " +"and local variables are preserved. On the next call to the generator's ``." +"next()`` method, the function will resume executing immediately after the :" +"keyword:`yield` statement. (For complicated reasons, the :keyword:`yield` " +"statement isn't allowed inside the :keyword:`try` block of a :keyword:" +"`try`...\\ :keyword:`finally` statement; read :pep:`255` for a full " +"explanation of the interaction between :keyword:`yield` and exceptions.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:236 +msgid "" +"Python doesn't go nearly as far as Icon in adopting generators as a central " +"concept. Generators are considered part of the core Python language, but " +"learning or using them isn't compulsory; if they don't solve any problems " +"that you have, feel free to ignore them. One novel feature of Python's " +"interface as compared to Icon's is that a generator's state is represented " +"as a concrete object (the iterator) that can be passed around to other " +"functions or stored in a data structure." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:257 +msgid "PEP 263: Source Code Encodings" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:259 +msgid "" +"Python source files can now be declared as being in different character set " +"encodings. Encodings are declared by including a specially formatted " +"comment in the first or second line of the source file. For example, a " +"UTF-8 file can be declared with::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:267 +msgid "" +"Without such an encoding declaration, the default encoding used is 7-bit " +"ASCII. Executing or importing modules that contain string literals with 8-" +"bit characters and have no encoding declaration will result in a :exc:" +"`DeprecationWarning` being signalled by Python 2.3; in 2.4 this will be a " +"syntax error." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:273 +msgid "" +"The encoding declaration only affects Unicode string literals, which will be " +"converted to Unicode using the specified encoding. Note that Python " +"identifiers are still restricted to ASCII characters, so you can't have " +"variable names that use characters outside of the usual alphanumerics." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:282 +msgid ":pep:`263` - Defining Python Source Code Encodings" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:282 +msgid "" +"Written by Marc-André Lemburg and Martin von Löwis; implemented by Suzuki " +"Hisao and Martin von Löwis." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:289 +msgid "PEP 273: Importing Modules from ZIP Archives" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:291 +msgid "" +"The new :mod:`zipimport` module adds support for importing modules from a " +"ZIP- format archive. You don't need to import the module explicitly; it " +"will be automatically imported if a ZIP archive's filename is added to ``sys." +"path``. For example:" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:314 +msgid "" +"An entry in ``sys.path`` can now be the filename of a ZIP archive. The ZIP " +"archive can contain any kind of files, but only files named :file:`\\*.py`, :" +"file:`\\*.pyc`, or :file:`\\*.pyo` can be imported. If an archive only " +"contains :file:`\\*.py` files, Python will not attempt to modify the archive " +"by adding the corresponding :file:`\\*.pyc` file, meaning that if a ZIP " +"archive doesn't contain :file:`\\*.pyc` files, importing may be rather slow." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:321 +msgid "" +"A path within the archive can also be specified to only import from a " +"subdirectory; for example, the path :file:`/tmp/example.zip/lib/` would only " +"import from the :file:`lib/` subdirectory within the archive." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:331 +msgid ":pep:`273` - Import Modules from Zip Archives" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:329 +msgid "" +"Written by James C. Ahlstrom, who also provided an implementation. Python " +"2.3 follows the specification in :pep:`273`, but uses an implementation " +"written by Just van Rossum that uses the import hooks described in :pep:" +"`302`. See section :ref:`section-pep302` for a description of the new import " +"hooks." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:338 +msgid "PEP 277: Unicode file name support for Windows NT" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:340 +msgid "" +"On Windows NT, 2000, and XP, the system stores file names as Unicode " +"strings. Traditionally, Python has represented file names as byte strings, " +"which is inadequate because it renders some file names inaccessible." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:344 +msgid "" +"Python now allows using arbitrary Unicode strings (within the limitations of " +"the file system) for all functions that expect file names, most notably the :" +"func:`open` built-in function. If a Unicode string is passed to :func:`os." +"listdir`, Python now returns a list of Unicode strings. A new function, :" +"func:`os.getcwdu`, returns the current directory as a Unicode string." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:350 +msgid "" +"Byte strings still work as file names, and on Windows Python will " +"transparently convert them to Unicode using the ``mbcs`` encoding." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:353 +msgid "" +"Other systems also allow Unicode strings as file names but convert them to " +"byte strings before passing them to the system, which can cause a :exc:" +"`UnicodeError` to be raised. Applications can test whether arbitrary Unicode " +"strings are supported as file names by checking :attr:`os.path." +"supports_unicode_filenames`, a Boolean value." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:359 +msgid "Under MacOS, :func:`os.listdir` may now return Unicode filenames." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:365 +msgid ":pep:`277` - Unicode file name support for Windows NT" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:365 +msgid "" +"Written by Neil Hodgson; implemented by Neil Hodgson, Martin von Löwis, and " +"Mark Hammond." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:375 +msgid "PEP 278: Universal Newline Support" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:377 +msgid "" +"The three major operating systems used today are Microsoft Windows, Apple's " +"Macintosh OS, and the various Unix derivatives. A minor irritation of " +"cross- platform work is that these three platforms all use different " +"characters to mark the ends of lines in text files. Unix uses the linefeed " +"(ASCII character 10), MacOS uses the carriage return (ASCII character 13), " +"and Windows uses a two-character sequence of a carriage return plus a " +"newline." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:384 +msgid "" +"Python's file objects can now support end of line conventions other than the " +"one followed by the platform on which Python is running. Opening a file with " +"the mode ``'U'`` or ``'rU'`` will open a file for reading in :term:" +"`universal newlines` mode. All three line ending conventions will be " +"translated to a ``'\\n'`` in the strings returned by the various file " +"methods such as :meth:`read` and :meth:`readline`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:391 +msgid "" +"Universal newline support is also used when importing modules and when " +"executing a file with the :func:`execfile` function. This means that Python " +"modules can be shared between all three operating systems without needing to " +"convert the line-endings." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:396 +msgid "" +"This feature can be disabled when compiling Python by specifying the :option:" +"`--without-universal-newlines` switch when running Python's :program:" +"`configure` script." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:403 +msgid ":pep:`278` - Universal Newline Support" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:404 +msgid "Written and implemented by Jack Jansen." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:412 +msgid "PEP 279: enumerate()" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:414 +msgid "" +"A new built-in function, :func:`enumerate`, will make certain loops a bit " +"clearer. ``enumerate(thing)``, where *thing* is either an iterator or a " +"sequence, returns an iterator that will return ``(0, thing[0])``, ``(1, " +"thing[1])``, ``(2, thing[2])``, and so forth." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:419 +msgid "A common idiom to change every element of a list looks like this::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:426 +msgid "This can be rewritten using :func:`enumerate` as::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:435 +msgid ":pep:`279` - The enumerate() built-in function" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:436 +msgid "Written and implemented by Raymond D. Hettinger." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:442 +msgid "PEP 282: The logging Package" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:444 +msgid "" +"A standard package for writing logs, :mod:`logging`, has been added to " +"Python 2.3. It provides a powerful and flexible mechanism for generating " +"logging output which can then be filtered and processed in various ways. A " +"configuration file written in a standard format can be used to control the " +"logging behavior of a program. Python includes handlers that will write log " +"records to standard error or to a file or socket, send them to the system " +"log, or even e-mail them to a particular address; of course, it's also " +"possible to write your own handler classes." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:453 +msgid "" +"The :class:`Logger` class is the primary class. Most application code will " +"deal with one or more :class:`Logger` objects, each one used by a particular " +"subsystem of the application. Each :class:`Logger` is identified by a name, " +"and names are organized into a hierarchy using ``.`` as the component " +"separator. For example, you might have :class:`Logger` instances named " +"``server``, ``server.auth`` and ``server.network``. The latter two " +"instances are below ``server`` in the hierarchy. This means that if you " +"turn up the verbosity for ``server`` or direct ``server`` messages to a " +"different handler, the changes will also apply to records logged to ``server." +"auth`` and ``server.network``. There's also a root :class:`Logger` that's " +"the parent of all other loggers." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:464 +msgid "" +"For simple uses, the :mod:`logging` package contains some convenience " +"functions that always use the root log::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:475 ../Doc/whatsnew/2.3.rst:500 +#: ../Doc/whatsnew/2.6.rst:642 +msgid "This produces the following output::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:481 +msgid "" +"In the default configuration, informational and debugging messages are " +"suppressed and the output is sent to standard error. You can enable the " +"display of informational and debugging messages by calling the :meth:" +"`setLevel` method on the root logger." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:486 +msgid "" +"Notice the :func:`warning` call's use of string formatting operators; all of " +"the functions for logging messages take the arguments ``(msg, arg1, " +"arg2, ...)`` and log the string resulting from ``msg % (arg1, arg2, ...)``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:490 +msgid "" +"There's also an :func:`exception` function that records the most recent " +"traceback. Any of the other functions will also record the traceback if you " +"specify a true value for the keyword argument *exc_info*. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:508 +msgid "" +"Slightly more advanced programs will use a logger other than the root " +"logger. The ``getLogger(name)`` function is used to get a particular log, " +"creating it if it doesn't exist yet. ``getLogger(None)`` returns the root " +"logger. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:519 +msgid "" +"Log records are usually propagated up the hierarchy, so a message logged to " +"``server.auth`` is also seen by ``server`` and ``root``, but a :class:" +"`Logger` can prevent this by setting its :attr:`propagate` attribute to :" +"const:`False`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:523 +msgid "" +"There are more classes provided by the :mod:`logging` package that can be " +"customized. When a :class:`Logger` instance is told to log a message, it " +"creates a :class:`LogRecord` instance that is sent to any number of " +"different :class:`Handler` instances. Loggers and handlers can also have an " +"attached list of filters, and each filter can cause the :class:`LogRecord` " +"to be ignored or can modify the record before passing it along. When " +"they're finally output, :class:`LogRecord` instances are converted to text " +"by a :class:`Formatter` class. All of these classes can be replaced by your " +"own specially-written classes." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:533 +msgid "" +"With all of these features the :mod:`logging` package should provide enough " +"flexibility for even the most complicated applications. This is only an " +"incomplete overview of its features, so please see the package's reference " +"documentation for all of the details. Reading :pep:`282` will also be " +"helpful." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:541 +msgid ":pep:`282` - A Logging System" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:542 +msgid "Written by Vinay Sajip and Trent Mick; implemented by Vinay Sajip." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:550 +msgid "PEP 285: A Boolean Type" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:552 +msgid "" +"A Boolean type was added to Python 2.3. Two new constants were added to " +"the :mod:`__builtin__` module, :const:`True` and :const:`False`. (:const:" +"`True` and :const:`False` constants were added to the built-ins in Python " +"2.2.1, but the 2.2.1 versions are simply set to integer values of 1 and 0 " +"and aren't a different type.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:558 +msgid "" +"The type object for this new type is named :class:`bool`; the constructor " +"for it takes any Python value and converts it to :const:`True` or :const:" +"`False`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:570 +msgid "" +"Most of the standard library modules and built-in functions have been " +"changed to return Booleans. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:581 +msgid "" +"Python's Booleans were added with the primary goal of making code clearer. " +"For example, if you're reading a function and encounter the statement " +"``return 1``, you might wonder whether the ``1`` represents a Boolean truth " +"value, an index, or a coefficient that multiplies some other quantity. If " +"the statement is ``return True``, however, the meaning of the return value " +"is quite clear." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:587 +msgid "" +"Python's Booleans were *not* added for the sake of strict type-checking. A " +"very strict language such as Pascal would also prevent you performing " +"arithmetic with Booleans, and would require that the expression in an :" +"keyword:`if` statement always evaluate to a Boolean result. Python is not " +"this strict and never will be, as :pep:`285` explicitly says. This means " +"you can still use any expression in an :keyword:`if` statement, even ones " +"that evaluate to a list or tuple or some random object. The Boolean type is " +"a subclass of the :class:`int` class so that arithmetic using a Boolean " +"still works. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:605 +msgid "" +"To sum up :const:`True` and :const:`False` in a sentence: they're " +"alternative ways to spell the integer values 1 and 0, with the single " +"difference that :func:`str` and :func:`repr` return the strings ``'True'`` " +"and ``'False'`` instead of ``'1'`` and ``'0'``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:613 +msgid ":pep:`285` - Adding a bool type" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:614 +msgid "Written and implemented by GvR." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:620 +msgid "PEP 293: Codec Error Handling Callbacks" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:622 +msgid "" +"When encoding a Unicode string into a byte string, unencodable characters " +"may be encountered. So far, Python has allowed specifying the error " +"processing as either \"strict\" (raising :exc:`UnicodeError`), \"ignore" +"\" (skipping the character), or \"replace\" (using a question mark in the " +"output string), with \"strict\" being the default behavior. It may be " +"desirable to specify alternative processing of such errors, such as " +"inserting an XML character reference or HTML entity reference into the " +"converted string." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:630 +msgid "" +"Python now has a flexible framework to add different processing strategies. " +"New error handlers can be added with :func:`codecs.register_error`, and " +"codecs then can access the error handler with :func:`codecs.lookup_error`. " +"An equivalent C API has been added for codecs written in C. The error " +"handler gets the necessary state information such as the string being " +"converted, the position in the string where the error was detected, and the " +"target encoding. The handler can then either raise an exception or return a " +"replacement string." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:638 +msgid "" +"Two additional error handlers have been implemented using this framework: " +"\"backslashreplace\" uses Python backslash quoting to represent unencodable " +"characters and \"xmlcharrefreplace\" emits XML character references." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:645 +msgid ":pep:`293` - Codec Error Handling Callbacks" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:646 +msgid "Written and implemented by Walter Dörwald." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:654 +msgid "PEP 301: Package Index and Metadata for Distutils" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:656 +msgid "" +"Support for the long-requested Python catalog makes its first appearance in " +"2.3." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:658 +msgid "" +"The heart of the catalog is the new Distutils :command:`register` command. " +"Running ``python setup.py register`` will collect the metadata describing a " +"package, such as its name, version, maintainer, description, &c., and send " +"it to a central catalog server. The resulting catalog is available from " +"https://pypi.python.org/pypi." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:664 +msgid "" +"To make the catalog a bit more useful, a new optional *classifiers* keyword " +"argument has been added to the Distutils :func:`setup` function. A list of " +"`Trove `_-style strings can be supplied to help " +"classify the software." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:669 +msgid "" +"Here's an example :file:`setup.py` with classifiers, written to be " +"compatible with older versions of the Distutils::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:688 +msgid "" +"The full list of classifiers can be obtained by running ``python setup.py " +"register --list-classifiers``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:694 +msgid ":pep:`301` - Package Index and Metadata for Distutils" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:695 +msgid "Written and implemented by Richard Jones." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:703 +msgid "PEP 302: New Import Hooks" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:705 +msgid "" +"While it's been possible to write custom import hooks ever since the :mod:" +"`ihooks` module was introduced in Python 1.3, no one has ever been really " +"happy with it because writing new import hooks is difficult and messy. " +"There have been various proposed alternatives such as the :mod:`imputil` " +"and :mod:`iu` modules, but none of them has ever gained much acceptance, and " +"none of them were easily usable from C code." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:712 +msgid "" +":pep:`302` borrows ideas from its predecessors, especially from Gordon " +"McMillan's :mod:`iu` module. Three new items are added to the :mod:`sys` " +"module:" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:716 +msgid "" +"``sys.path_hooks`` is a list of callable objects; most often they'll be " +"classes. Each callable takes a string containing a path and either returns " +"an importer object that will handle imports from this path or raises an :exc:" +"`ImportError` exception if it can't handle this path." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:721 +msgid "" +"``sys.path_importer_cache`` caches importer objects for each path, so ``sys." +"path_hooks`` will only need to be traversed once for each path." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:724 +msgid "" +"``sys.meta_path`` is a list of importer objects that will be traversed " +"before ``sys.path`` is checked. This list is initially empty, but user code " +"can add objects to it. Additional built-in and frozen modules can be " +"imported by an object added to this list." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:729 +msgid "" +"Importer objects must have a single method, ``find_module(fullname, " +"path=None)``. *fullname* will be a module or package name, e.g. ``string`` " +"or ``distutils.core``. :meth:`find_module` must return a loader object that " +"has a single method, ``load_module(fullname)``, that creates and returns the " +"corresponding module object." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:735 +msgid "" +"Pseudo-code for Python's new import logic, therefore, looks something like " +"this (simplified a bit; see :pep:`302` for the full details)::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:760 +msgid ":pep:`302` - New Import Hooks" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:761 +msgid "" +"Written by Just van Rossum and Paul Moore. Implemented by Just van Rossum." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:769 +msgid "PEP 305: Comma-separated Files" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:771 +msgid "" +"Comma-separated files are a format frequently used for exporting data from " +"databases and spreadsheets. Python 2.3 adds a parser for comma-separated " +"files." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:774 +msgid "Comma-separated format is deceptively simple at first glance::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:778 +msgid "" +"Read a line and call ``line.split(',')``: what could be simpler? But toss in " +"string data that can contain commas, and things get more complicated::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:783 +msgid "" +"A big ugly regular expression can parse this, but using the new :mod:`csv` " +"package is much simpler::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:793 +msgid "" +"The :func:`reader` function takes a number of different options. The field " +"separator isn't limited to the comma and can be changed to any character, " +"and so can the quoting and line-ending characters." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:797 +msgid "" +"Different dialects of comma-separated files can be defined and registered; " +"currently there are two dialects, both used by Microsoft Excel. A separate :" +"class:`csv.writer` class will generate comma-separated files from a " +"succession of tuples or lists, quoting strings that contain the delimiter." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:806 +msgid ":pep:`305` - CSV File API" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:806 +msgid "" +"Written and implemented by Kevin Altis, Dave Cole, Andrew McNamara, Skip " +"Montanaro, Cliff Wells." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:815 +msgid "PEP 307: Pickle Enhancements" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:817 +msgid "" +"The :mod:`pickle` and :mod:`cPickle` modules received some attention during " +"the 2.3 development cycle. In 2.2, new-style classes could be pickled " +"without difficulty, but they weren't pickled very compactly; :pep:`307` " +"quotes a trivial example where a new-style class results in a pickled string " +"three times longer than that for a classic class." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:823 +msgid "" +"The solution was to invent a new pickle protocol. The :func:`pickle.dumps` " +"function has supported a text-or-binary flag for a long time. In 2.3, this " +"flag is redefined from a Boolean to an integer: 0 is the old text-mode " +"pickle format, 1 is the old binary format, and now 2 is a new 2.3-specific " +"format. A new constant, :const:`pickle.HIGHEST_PROTOCOL`, can be used to " +"select the fanciest protocol available." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:830 +msgid "" +"Unpickling is no longer considered a safe operation. 2.2's :mod:`pickle` " +"provided hooks for trying to prevent unsafe classes from being unpickled " +"(specifically, a :attr:`__safe_for_unpickling__` attribute), but none of " +"this code was ever audited and therefore it's all been ripped out in 2.3. " +"You should not unpickle untrusted data in any version of Python." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:836 +msgid "" +"To reduce the pickling overhead for new-style classes, a new interface for " +"customizing pickling was added using three special methods: :meth:" +"`__getstate__`, :meth:`__setstate__`, and :meth:`__getnewargs__`. Consult :" +"pep:`307` for the full semantics of these methods." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:841 +msgid "" +"As a way to compress pickles yet further, it's now possible to use integer " +"codes instead of long strings to identify pickled classes. The Python " +"Software Foundation will maintain a list of standardized codes; there's also " +"a range of codes for private use. Currently no codes have been specified." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:849 +msgid ":pep:`307` - Extensions to the pickle protocol" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:850 +msgid "Written and implemented by Guido van Rossum and Tim Peters." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:858 +msgid "Extended Slices" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:860 +msgid "" +"Ever since Python 1.4, the slicing syntax has supported an optional third " +"\"step\" or \"stride\" argument. For example, these are all legal Python " +"syntax: ``L[1:10:2]``, ``L[:-1:1]``, ``L[::-1]``. This was added to Python " +"at the request of the developers of Numerical Python, which uses the third " +"argument extensively. However, Python's built-in list, tuple, and string " +"sequence types have never supported this feature, raising a :exc:`TypeError` " +"if you tried it. Michael Hudson contributed a patch to fix this shortcoming." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:868 +msgid "" +"For example, you can now easily extract the elements of a list that have " +"even indexes::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:875 +msgid "" +"Negative values also work to make a copy of the same list in reverse order::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:880 +msgid "This also works for tuples, arrays, and strings::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:888 +msgid "" +"If you have a mutable sequence such as a list or an array you can assign to " +"or delete an extended slice, but there are some differences between " +"assignment to extended and regular slices. Assignment to a regular slice " +"can be used to change the length of the sequence::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:900 +msgid "" +"Extended slices aren't this flexible. When assigning to an extended slice, " +"the list on the right hand side of the statement must contain the same " +"number of items as the slice it is replacing::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:917 +msgid "Deletion is more straightforward::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:928 +msgid "" +"One can also now pass slice objects to the :meth:`__getitem__` methods of " +"the built-in sequences::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:934 +msgid "Or use slice objects directly in subscripts::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:939 +msgid "" +"To simplify implementing sequences that support extended slicing, slice " +"objects now have a method ``indices(length)`` which, given the length of a " +"sequence, returns a ``(start, stop, step)`` tuple that can be passed " +"directly to :func:`range`. :meth:`indices` handles omitted and out-of-bounds " +"indices in a manner consistent with regular slices (and this innocuous " +"phrase hides a welter of confusing details!). The method is intended to be " +"used like this::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:957 +msgid "" +"From this example you can also see that the built-in :class:`slice` object " +"is now the type object for the slice type, and is no longer a function. " +"This is consistent with Python 2.2, where :class:`int`, :class:`str`, etc., " +"underwent the same change." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:966 ../Doc/whatsnew/2.4.rst:774 +#: ../Doc/whatsnew/2.5.rst:973 ../Doc/whatsnew/2.6.rst:1485 +#: ../Doc/whatsnew/2.7.rst:672 ../Doc/whatsnew/3.1.rst:116 +#: ../Doc/whatsnew/3.2.rst:433 ../Doc/whatsnew/3.3.rst:776 +#: ../Doc/whatsnew/3.4.rst:401 ../Doc/whatsnew/3.5.rst:701 +#: ../Doc/whatsnew/3.6.rst:545 +msgid "Other Language Changes" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:968 +msgid "" +"Here are all of the changes that Python 2.3 makes to the core Python " +"language." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:970 +msgid "" +"The :keyword:`yield` statement is now always a keyword, as described in " +"section :ref:`section-generators` of this document." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:973 +msgid "" +"A new built-in function :func:`enumerate` was added, as described in " +"section :ref:`section-enumerate` of this document." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:976 +msgid "" +"Two new constants, :const:`True` and :const:`False` were added along with " +"the built-in :class:`bool` type, as described in section :ref:`section-bool` " +"of this document." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:980 +msgid "" +"The :func:`int` type constructor will now return a long integer instead of " +"raising an :exc:`OverflowError` when a string or floating-point number is " +"too large to fit into an integer. This can lead to the paradoxical result " +"that ``isinstance(int(expression), int)`` is false, but that seems unlikely " +"to cause problems in practice." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:986 +msgid "" +"Built-in types now support the extended slicing syntax, as described in " +"section :ref:`section-slices` of this document." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:989 +msgid "" +"A new built-in function, ``sum(iterable, start=0)``, adds up the numeric " +"items in the iterable object and returns their sum. :func:`sum` only " +"accepts numbers, meaning that you can't use it to concatenate a bunch of " +"strings. (Contributed by Alex Martelli.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:994 +msgid "" +"``list.insert(pos, value)`` used to insert *value* at the front of the list " +"when *pos* was negative. The behaviour has now been changed to be " +"consistent with slice indexing, so when *pos* is -1 the value will be " +"inserted before the last element, and so forth." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:999 +msgid "" +"``list.index(value)``, which searches for *value* within the list and " +"returns its index, now takes optional *start* and *stop* arguments to limit " +"the search to only part of the list." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1003 +msgid "" +"Dictionaries have a new method, ``pop(key[, *default*])``, that returns the " +"value corresponding to *key* and removes that key/value pair from the " +"dictionary. If the requested key isn't present in the dictionary, *default* " +"is returned if it's specified and :exc:`KeyError` raised if it isn't. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1025 +msgid "" +"There's also a new class method, ``dict.fromkeys(iterable, value)``, that " +"creates a dictionary with keys taken from the supplied iterator *iterable* " +"and all values set to *value*, defaulting to ``None``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1029 +msgid "(Patches contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1031 +msgid "" +"Also, the :func:`dict` constructor now accepts keyword arguments to simplify " +"creating small dictionaries::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1037 +msgid "(Contributed by Just van Rossum.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1039 +msgid "" +"The :keyword:`assert` statement no longer checks the ``__debug__`` flag, so " +"you can no longer disable assertions by assigning to ``__debug__``. Running " +"Python with the :option:`-O` switch will still generate code that doesn't " +"execute any assertions." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1044 +msgid "" +"Most type objects are now callable, so you can use them to create new " +"objects such as functions, classes, and modules. (This means that the :mod:" +"`new` module can be deprecated in a future Python version, because you can " +"now use the type objects available in the :mod:`types` module.) For example, " +"you can create a new module object with the following code:" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1059 +msgid "" +"A new warning, :exc:`PendingDeprecationWarning` was added to indicate " +"features which are in the process of being deprecated. The warning will " +"*not* be printed by default. To check for use of features that will be " +"deprecated in the future, supply :option:`-Walways::" +"PendingDeprecationWarning:: <-W>` on the command line or use :func:`warnings." +"filterwarnings`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1065 +msgid "" +"The process of deprecating string-based exceptions, as in ``raise \"Error " +"occurred\"``, has begun. Raising a string will now trigger :exc:" +"`PendingDeprecationWarning`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1069 +msgid "" +"Using ``None`` as a variable name will now result in a :exc:`SyntaxWarning` " +"warning. In a future version of Python, ``None`` may finally become a " +"keyword." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1072 +msgid "" +"The :meth:`xreadlines` method of file objects, introduced in Python 2.1, is " +"no longer necessary because files now behave as their own iterator. :meth:" +"`xreadlines` was originally introduced as a faster way to loop over all the " +"lines in a file, but now you can simply write ``for line in file_obj``. File " +"objects also have a new read-only :attr:`encoding` attribute that gives the " +"encoding used by the file; Unicode strings written to the file will be " +"automatically converted to bytes using the given encoding." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1080 +msgid "" +"The method resolution order used by new-style classes has changed, though " +"you'll only notice the difference if you have a really complicated " +"inheritance hierarchy. Classic classes are unaffected by this change. " +"Python 2.2 originally used a topological sort of a class's ancestors, but " +"2.3 now uses the C3 algorithm as described in the paper `\"A Monotonic " +"Superclass Linearization for Dylan\" `_. To understand the motivation for this " +"change, read Michele Simionato's article `\"Python 2.3 Method Resolution " +"Order\" `_, or read the " +"thread on python-dev starting with the message at https://mail.python.org/" +"pipermail/python-dev/2002-October/029035.html. Samuele Pedroni first pointed " +"out the problem and also implemented the fix by coding the C3 algorithm." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1093 +msgid "" +"Python runs multithreaded programs by switching between threads after " +"executing N bytecodes. The default value for N has been increased from 10 " +"to 100 bytecodes, speeding up single-threaded applications by reducing the " +"switching overhead. Some multithreaded applications may suffer slower " +"response time, but that's easily fixed by setting the limit back to a lower " +"number using ``sys.setcheckinterval(N)``. The limit can be retrieved with " +"the new :func:`sys.getcheckinterval` function." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1101 +msgid "" +"One minor but far-reaching change is that the names of extension types " +"defined by the modules included with Python now contain the module and a " +"``'.'`` in front of the type name. For example, in Python 2.2, if you " +"created a socket and printed its :attr:`__class__`, you'd get this output::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1110 +msgid "In 2.3, you get this::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1115 +msgid "" +"One of the noted incompatibilities between old- and new-style classes has " +"been removed: you can now assign to the :attr:`~definition.__name__` and :" +"attr:`~class.__bases__` attributes of new-style classes. There are some " +"restrictions on what can be assigned to :attr:`~class.__bases__` along the " +"lines of those relating to assigning to an instance's :attr:`~instance." +"__class__` attribute." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1125 +msgid "String Changes" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1127 +msgid "" +"The :keyword:`in` operator now works differently for strings. Previously, " +"when evaluating ``X in Y`` where *X* and *Y* are strings, *X* could only be " +"a single character. That's now changed; *X* can be a string of any length, " +"and ``X in Y`` will return :const:`True` if *X* is a substring of *Y*. If " +"*X* is the empty string, the result is always :const:`True`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1140 +msgid "" +"Note that this doesn't tell you where the substring starts; if you need that " +"information, use the :meth:`find` string method." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1143 +msgid "" +"The :meth:`strip`, :meth:`lstrip`, and :meth:`rstrip` string methods now " +"have an optional argument for specifying the characters to strip. The " +"default is still to remove all whitespace characters::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1157 +msgid "(Suggested by Simon Brunning and implemented by Walter Dörwald.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1159 +msgid "" +"The :meth:`startswith` and :meth:`endswith` string methods now accept " +"negative numbers for the *start* and *end* parameters." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1162 +msgid "" +"Another new string method is :meth:`zfill`, originally a function in the :" +"mod:`string` module. :meth:`zfill` pads a numeric string with zeros on the " +"left until it's the specified width. Note that the ``%`` operator is still " +"more flexible and powerful than :meth:`zfill`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1174 +msgid "(Contributed by Walter Dörwald.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1176 +msgid "" +"A new type object, :class:`basestring`, has been added. Both 8-bit strings " +"and Unicode strings inherit from this type, so ``isinstance(obj, " +"basestring)`` will return :const:`True` for either kind of string. It's a " +"completely abstract type, so you can't create :class:`basestring` instances." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1181 +msgid "" +"Interned strings are no longer immortal and will now be garbage-collected in " +"the usual way when the only reference to them is from the internal " +"dictionary of interned strings. (Implemented by Oren Tirosh.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1189 ../Doc/whatsnew/2.4.rst:933 +#: ../Doc/whatsnew/2.5.rst:1138 ../Doc/whatsnew/2.6.rst:1693 +#: ../Doc/whatsnew/2.7.rst:928 ../Doc/whatsnew/3.1.rst:416 +#: ../Doc/whatsnew/3.2.rst:2340 ../Doc/whatsnew/3.3.rst:2149 +#: ../Doc/whatsnew/3.5.rst:2105 ../Doc/whatsnew/3.6.rst:1113 +msgid "Optimizations" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1191 +msgid "" +"The creation of new-style class instances has been made much faster; they're " +"now faster than classic classes!" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1194 +msgid "" +"The :meth:`sort` method of list objects has been extensively rewritten by " +"Tim Peters, and the implementation is significantly faster." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1197 +msgid "" +"Multiplication of large long integers is now much faster thanks to an " +"implementation of Karatsuba multiplication, an algorithm that scales better " +"than the O(n\\*n) required for the grade-school multiplication algorithm. " +"(Original patch by Christopher A. Craig, and significantly reworked by Tim " +"Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1202 +msgid "" +"The ``SET_LINENO`` opcode is now gone. This may provide a small speed " +"increase, depending on your compiler's idiosyncrasies. See section :ref:" +"`23section-other` for a longer explanation. (Removed by Michael Hudson.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1206 +msgid "" +":func:`xrange` objects now have their own iterator, making ``for i in " +"xrange(n)`` slightly faster than ``for i in range(n)``. (Patch by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1210 +msgid "" +"A number of small rearrangements have been made in various hotspots to " +"improve performance, such as inlining a function or removing some code. " +"(Implemented mostly by GvR, but lots of people have contributed single " +"changes.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1214 +msgid "" +"The net result of the 2.3 optimizations is that Python 2.3 runs the pystone " +"benchmark around 25% faster than Python 2.2." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1221 ../Doc/whatsnew/2.4.rst:990 +#: ../Doc/whatsnew/3.1.rst:224 ../Doc/whatsnew/3.2.rst:654 +msgid "New, Improved, and Deprecated Modules" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1223 ../Doc/whatsnew/2.4.rst:992 +msgid "" +"As usual, Python's standard library received a number of enhancements and " +"bug fixes. Here's a partial list of the most notable changes, sorted " +"alphabetically by module name. Consult the :file:`Misc/NEWS` file in the " +"source tree for a more complete list of changes, or look through the CVS " +"logs for all the details." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1228 +msgid "" +"The :mod:`array` module now supports arrays of Unicode characters using the " +"``'u'`` format character. Arrays also now support using the ``+=`` " +"assignment operator to add another array's contents, and the ``*=`` " +"assignment operator to repeat an array. (Contributed by Jason Orendorff.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1233 +msgid "" +"The :mod:`bsddb` module has been replaced by version 4.1.6 of the `PyBSDDB " +"`_ package, providing a more complete " +"interface to the transactional features of the BerkeleyDB library." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1237 +msgid "" +"The old version of the module has been renamed to :mod:`bsddb185` and is no " +"longer built automatically; you'll have to edit :file:`Modules/Setup` to " +"enable it. Note that the new :mod:`bsddb` package is intended to be " +"compatible with the old module, so be sure to file bugs if you discover any " +"incompatibilities. When upgrading to Python 2.3, if the new interpreter is " +"compiled with a new version of the underlying BerkeleyDB library, you will " +"almost certainly have to convert your database files to the new version. " +"You can do this fairly easily with the new scripts :file:`db2pickle.py` and :" +"file:`pickle2db.py` which you will find in the distribution's :file:`Tools/" +"scripts` directory. If you've already been using the PyBSDDB package and " +"importing it as :mod:`bsddb3`, you will have to change your ``import`` " +"statements to import it as :mod:`bsddb`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1249 +msgid "" +"The new :mod:`bz2` module is an interface to the bz2 data compression " +"library. bz2-compressed data is usually smaller than corresponding :mod:" +"`zlib`\\ -compressed data. (Contributed by Gustavo Niemeyer.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1253 +msgid "" +"A set of standard date/time types has been added in the new :mod:`datetime` " +"module. See the following section for more details." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1256 +msgid "" +"The Distutils :class:`Extension` class now supports an extra constructor " +"argument named *depends* for listing additional source files that an " +"extension depends on. This lets Distutils recompile the module if any of " +"the dependency files are modified. For example, if :file:`sampmodule.c` " +"includes the header file :file:`sample.h`, you would create the :class:" +"`Extension` object like this::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1267 +msgid "" +"Modifying :file:`sample.h` would then cause the module to be recompiled. " +"(Contributed by Jeremy Hylton.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1270 +msgid "" +"Other minor changes to Distutils: it now checks for the :envvar:`CC`, :" +"envvar:`CFLAGS`, :envvar:`CPP`, :envvar:`LDFLAGS`, and :envvar:`CPPFLAGS` " +"environment variables, using them to override the settings in Python's " +"configuration (contributed by Robert Weber)." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1275 +msgid "" +"Previously the :mod:`doctest` module would only search the docstrings of " +"public methods and functions for test cases, but it now also examines " +"private ones as well. The :func:`DocTestSuite` function creates a :class:" +"`unittest.TestSuite` object from a set of :mod:`doctest` tests." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1280 +msgid "" +"The new ``gc.get_referents(object)`` function returns a list of all the " +"objects referenced by *object*." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1283 +msgid "" +"The :mod:`getopt` module gained a new function, :func:`gnu_getopt`, that " +"supports the same arguments as the existing :func:`getopt` function but uses " +"GNU-style scanning mode. The existing :func:`getopt` stops processing " +"options as soon as a non-option argument is encountered, but in GNU-style " +"mode processing continues, meaning that options and arguments can be mixed. " +"For example::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1294 +msgid "(Contributed by Peter Åstrand.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1296 +msgid "" +"The :mod:`grp`, :mod:`pwd`, and :mod:`resource` modules now return enhanced " +"tuples::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1304 +msgid "The :mod:`gzip` module can now handle files exceeding 2 GiB." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1306 +msgid "" +"The new :mod:`heapq` module contains an implementation of a heap queue " +"algorithm. A heap is an array-like data structure that keeps items in a " +"partially sorted order such that, for every index *k*, ``heap[k] <= heap[2*k" +"+1]`` and ``heap[k] <= heap[2*k+2]``. This makes it quick to remove the " +"smallest item, and inserting a new item while maintaining the heap property " +"is O(lg n). (See https://xlinux.nist.gov/dads//HTML/priorityque.html for " +"more information about the priority queue data structure.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1314 +msgid "" +"The :mod:`heapq` module provides :func:`heappush` and :func:`heappop` " +"functions for adding and removing items while maintaining the heap property " +"on top of some other mutable Python sequence type. Here's an example that " +"uses a Python list::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1332 +msgid "(Contributed by Kevin O'Connor.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1334 +msgid "" +"The IDLE integrated development environment has been updated using the code " +"from the IDLEfork project (http://idlefork.sourceforge.net). The most " +"notable feature is that the code being developed is now executed in a " +"subprocess, meaning that there's no longer any need for manual ``reload()`` " +"operations. IDLE's core code has been incorporated into the standard library " +"as the :mod:`idlelib` package." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1340 +msgid "" +"The :mod:`imaplib` module now supports IMAP over SSL. (Contributed by Piers " +"Lauder and Tino Lange.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1343 +msgid "" +"The :mod:`itertools` contains a number of useful functions for use with " +"iterators, inspired by various functions provided by the ML and Haskell " +"languages. For example, ``itertools.ifilter(predicate, iterator)`` returns " +"all elements in the iterator for which the function :func:`predicate` " +"returns :const:`True`, and ``itertools.repeat(obj, N)`` returns ``obj`` *N* " +"times. There are a number of other functions in the module; see the " +"package's reference documentation for details. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1352 +msgid "" +"Two new functions in the :mod:`math` module, ``degrees(rads)`` and " +"``radians(degs)``, convert between radians and degrees. Other functions in " +"the :mod:`math` module such as :func:`math.sin` and :func:`math.cos` have " +"always required input values measured in radians. Also, an optional *base* " +"argument was added to :func:`math.log` to make it easier to compute " +"logarithms for bases other than ``e`` and ``10``. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1359 +msgid "" +"Several new POSIX functions (:func:`getpgid`, :func:`killpg`, :func:" +"`lchown`, :func:`loadavg`, :func:`major`, :func:`makedev`, :func:`minor`, " +"and :func:`mknod`) were added to the :mod:`posix` module that underlies the :" +"mod:`os` module. (Contributed by Gustavo Niemeyer, Geert Jansen, and Denis " +"S. Otkidach.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1365 +msgid "" +"In the :mod:`os` module, the :func:`\\*stat` family of functions can now " +"report fractions of a second in a timestamp. Such time stamps are " +"represented as floats, similar to the value returned by :func:`time.time`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1369 +msgid "" +"During testing, it was found that some applications will break if time " +"stamps are floats. For compatibility, when using the tuple interface of " +"the :class:`stat_result` time stamps will be represented as integers. When " +"using named fields (a feature first introduced in Python 2.2), time stamps " +"are still represented as integers, unless :func:`os.stat_float_times` is " +"invoked to enable float return values::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1382 +msgid "In Python 2.4, the default will change to always returning floats." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1384 +msgid "" +"Application developers should enable this feature only if all their " +"libraries work properly when confronted with floating point time stamps, or " +"if they use the tuple API. If used, the feature should be activated on an " +"application level instead of trying to enable it on a per-use basis." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1389 +msgid "" +"The :mod:`optparse` module contains a new parser for command-line arguments " +"that can convert option values to a particular Python type and will " +"automatically generate a usage message. See the following section for more " +"details." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1394 +msgid "" +"The old and never-documented :mod:`linuxaudiodev` module has been " +"deprecated, and a new version named :mod:`ossaudiodev` has been added. The " +"module was renamed because the OSS sound drivers can be used on platforms " +"other than Linux, and the interface has also been tidied and brought up to " +"date in various ways. (Contributed by Greg Ward and Nicholas FitzRoy-Dale.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1400 +msgid "" +"The new :mod:`platform` module contains a number of functions that try to " +"determine various properties of the platform you're running on. There are " +"functions for getting the architecture, CPU type, the Windows OS version, " +"and even the Linux distribution version. (Contributed by Marc-André Lemburg.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1405 +msgid "" +"The parser objects provided by the :mod:`pyexpat` module can now optionally " +"buffer character data, resulting in fewer calls to your character data " +"handler and therefore faster performance. Setting the parser object's :attr:" +"`buffer_text` attribute to :const:`True` will enable buffering." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1410 +msgid "" +"The ``sample(population, k)`` function was added to the :mod:`random` " +"module. *population* is a sequence or :class:`xrange` object containing the " +"elements of a population, and :func:`sample` chooses *k* elements from the " +"population without replacing chosen elements. *k* can be any value up to " +"``len(population)``. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1432 +msgid "" +"The :mod:`random` module now uses a new algorithm, the Mersenne Twister, " +"implemented in C. It's faster and more extensively studied than the " +"previous algorithm." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1436 +msgid "(All changes contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1438 +msgid "" +"The :mod:`readline` module also gained a number of new functions: :func:" +"`get_history_item`, :func:`get_current_history_length`, and :func:" +"`redisplay`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1442 +msgid "" +"The :mod:`rexec` and :mod:`Bastion` modules have been declared dead, and " +"attempts to import them will fail with a :exc:`RuntimeError`. New-style " +"classes provide new ways to break out of the restricted execution " +"environment provided by :mod:`rexec`, and no one has interest in fixing them " +"or time to do so. If you have applications using :mod:`rexec`, rewrite them " +"to use something else." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1448 +msgid "" +"(Sticking with Python 2.2 or 2.1 will not make your applications any safer " +"because there are known bugs in the :mod:`rexec` module in those versions. " +"To repeat: if you're using :mod:`rexec`, stop using it immediately.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1452 +msgid "" +"The :mod:`rotor` module has been deprecated because the algorithm it uses " +"for encryption is not believed to be secure. If you need encryption, use " +"one of the several AES Python modules that are available separately." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1456 +msgid "" +"The :mod:`shutil` module gained a ``move(src, dest)`` function that " +"recursively moves a file or directory to a new location." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1459 +msgid "" +"Support for more advanced POSIX signal handling was added to the :mod:" +"`signal` but then removed again as it proved impossible to make it work " +"reliably across platforms." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1463 +msgid "" +"The :mod:`socket` module now supports timeouts. You can call the " +"``settimeout(t)`` method on a socket object to set a timeout of *t* seconds. " +"Subsequent socket operations that take longer than *t* seconds to complete " +"will abort and raise a :exc:`socket.timeout` exception." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1468 +msgid "" +"The original timeout implementation was by Tim O'Malley. Michael Gilfix " +"integrated it into the Python :mod:`socket` module and shepherded it through " +"a lengthy review. After the code was checked in, Guido van Rossum rewrote " +"parts of it. (This is a good example of a collaborative development process " +"in action.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1474 +msgid "" +"On Windows, the :mod:`socket` module now ships with Secure Sockets Layer " +"(SSL) support." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1477 +msgid "" +"The value of the C :const:`PYTHON_API_VERSION` macro is now exposed at the " +"Python level as ``sys.api_version``. The current exception can be cleared " +"by calling the new :func:`sys.exc_clear` function." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1481 +msgid "" +"The new :mod:`tarfile` module allows reading from and writing to :program:" +"`tar`\\ -format archive files. (Contributed by Lars Gustäbel.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1484 +msgid "" +"The new :mod:`textwrap` module contains functions for wrapping strings " +"containing paragraphs of text. The ``wrap(text, width)`` function takes a " +"string and returns a list containing the text split into lines of no more " +"than the chosen width. The ``fill(text, width)`` function returns a single " +"string, reformatted to fit into lines no longer than the chosen width. (As " +"you can guess, :func:`fill` is built on top of :func:`wrap`. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1506 +msgid "" +"The module also contains a :class:`TextWrapper` class that actually " +"implements the text wrapping strategy. Both the :class:`TextWrapper` class " +"and the :func:`wrap` and :func:`fill` functions support a number of " +"additional keyword arguments for fine-tuning the formatting; consult the " +"module's documentation for details. (Contributed by Greg Ward.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1512 +msgid "" +"The :mod:`thread` and :mod:`threading` modules now have companion modules, :" +"mod:`dummy_thread` and :mod:`dummy_threading`, that provide a do-nothing " +"implementation of the :mod:`thread` module's interface for platforms where " +"threads are not supported. The intention is to simplify thread-aware " +"modules (ones that *don't* rely on threads to run) by putting the following " +"code at the top::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1524 +msgid "" +"In this example, :mod:`_threading` is used as the module name to make it " +"clear that the module being used is not necessarily the actual :mod:" +"`threading` module. Code can call functions and use classes in :mod:" +"`_threading` whether or not threads are supported, avoiding an :keyword:`if` " +"statement and making the code slightly clearer. This module will not " +"magically make multithreaded code run without threads; code that waits for " +"another thread to return or to do something will simply hang forever." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1532 +msgid "" +"The :mod:`time` module's :func:`strptime` function has long been an " +"annoyance because it uses the platform C library's :func:`strptime` " +"implementation, and different platforms sometimes have odd bugs. Brett " +"Cannon contributed a portable implementation that's written in pure Python " +"and should behave identically on all platforms." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1538 +msgid "" +"The new :mod:`timeit` module helps measure how long snippets of Python code " +"take to execute. The :file:`timeit.py` file can be run directly from the " +"command line, or the module's :class:`Timer` class can be imported and used " +"directly. Here's a short example that figures out whether it's faster to " +"convert an 8-bit string to Unicode by appending an empty Unicode string to " +"it or by using the :func:`unicode` function::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1558 +msgid "" +"The :mod:`Tix` module has received various bug fixes and updates for the " +"current version of the Tix package." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1561 +msgid "" +"The :mod:`Tkinter` module now works with a thread-enabled version of Tcl. " +"Tcl's threading model requires that widgets only be accessed from the thread " +"in which they're created; accesses from another thread can cause Tcl to " +"panic. For certain Tcl interfaces, :mod:`Tkinter` will now automatically " +"avoid this when a widget is accessed from a different thread by marshalling " +"a command, passing it to the correct thread, and waiting for the results. " +"Other interfaces can't be handled automatically but :mod:`Tkinter` will now " +"raise an exception on such an access so that you can at least find out about " +"the problem. See https://mail.python.org/pipermail/python-dev/2002-" +"December/031107.html for a more detailed explanation of this change. " +"(Implemented by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1572 +msgid "" +"Calling Tcl methods through :mod:`_tkinter` no longer returns only strings. " +"Instead, if Tcl returns other objects those objects are converted to their " +"Python equivalent, if one exists, or wrapped with a :class:`_tkinter." +"Tcl_Obj` object if no Python equivalent exists. This behavior can be " +"controlled through the :meth:`wantobjects` method of :class:`tkapp` objects." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1578 +msgid "" +"When using :mod:`_tkinter` through the :mod:`Tkinter` module (as most " +"Tkinter applications will), this feature is always activated. It should not " +"cause compatibility problems, since Tkinter would always convert string " +"results to Python types where possible." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1583 +msgid "" +"If any incompatibilities are found, the old behavior can be restored by " +"setting the :attr:`wantobjects` variable in the :mod:`Tkinter` module to " +"false before creating the first :class:`tkapp` object. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1590 +msgid "Any breakage caused by this change should be reported as a bug." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1592 +msgid "" +"The :mod:`UserDict` module has a new :class:`DictMixin` class which defines " +"all dictionary methods for classes that already have a minimum mapping " +"interface. This greatly simplifies writing classes that need to be " +"substitutable for dictionaries, such as the classes in the :mod:`shelve` " +"module." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1598 +msgid "" +"Adding the mix-in as a superclass provides the full dictionary interface " +"whenever the class defines :meth:`__getitem__`, :meth:`__setitem__`, :meth:" +"`__delitem__`, and :meth:`keys`. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1639 ../Doc/whatsnew/2.4.rst:891 +#: ../Doc/whatsnew/2.4.rst:919 ../Doc/whatsnew/2.4.rst:1212 +#: ../Doc/whatsnew/2.5.rst:1372 ../Doc/whatsnew/2.5.rst:1381 +#: ../Doc/whatsnew/2.6.rst:1596 ../Doc/whatsnew/2.6.rst:1880 +#: ../Doc/whatsnew/2.6.rst:1901 ../Doc/whatsnew/3.1.rst:281 +#: ../Doc/whatsnew/3.2.rst:820 ../Doc/whatsnew/3.2.rst:832 +#: ../Doc/whatsnew/3.2.rst:876 ../Doc/whatsnew/3.2.rst:897 +#: ../Doc/whatsnew/3.2.rst:911 ../Doc/whatsnew/3.2.rst:1778 +#: ../Doc/whatsnew/3.2.rst:1823 +msgid "(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1641 +msgid "" +"The DOM implementation in :mod:`xml.dom.minidom` can now generate XML output " +"in a particular encoding by providing an optional encoding argument to the :" +"meth:`toxml` and :meth:`toprettyxml` methods of DOM nodes." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1645 +msgid "" +"The :mod:`xmlrpclib` module now supports an XML-RPC extension for handling " +"nil data values such as Python's ``None``. Nil values are always supported " +"on unmarshalling an XML-RPC response. To generate requests containing " +"``None``, you must supply a true value for the *allow_none* parameter when " +"creating a :class:`Marshaller` instance." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1651 +msgid "" +"The new :mod:`DocXMLRPCServer` module allows writing self-documenting XML-" +"RPC servers. Run it in demo mode (as a program) to see it in action. " +"Pointing the Web browser to the RPC server produces pydoc-style " +"documentation; pointing xmlrpclib to the server allows invoking the actual " +"methods. (Contributed by Brian Quinlan.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1657 +msgid "" +"Support for internationalized domain names (RFCs 3454, 3490, 3491, and 3492) " +"has been added. The \"idna\" encoding can be used to convert between a " +"Unicode domain name and the ASCII-compatible encoding (ACE) of that name. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1664 +msgid "" +"The :mod:`socket` module has also been extended to transparently convert " +"Unicode hostnames to the ACE version before passing them to the C library. " +"Modules that deal with hostnames such as :mod:`httplib` and :mod:`ftplib`) " +"also support Unicode host names; :mod:`httplib` also sends HTTP ``Host`` " +"headers using the ACE version of the domain name. :mod:`urllib` supports " +"Unicode URLs with non-ASCII host names as long as the ``path`` part of the " +"URL is ASCII only." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1672 +msgid "" +"To implement this change, the :mod:`stringprep` module, the " +"``mkstringprep`` tool and the ``punycode`` encoding have been added." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1679 +msgid "Date/Time Type" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1681 +msgid "" +"Date and time types suitable for expressing timestamps were added as the :" +"mod:`datetime` module. The types don't support different calendars or many " +"fancy features, and just stick to the basics of representing time." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1685 +msgid "" +"The three primary types are: :class:`date`, representing a day, month, and " +"year; :class:`time`, consisting of hour, minute, and second; and :class:" +"`datetime`, which contains all the attributes of both :class:`date` and :" +"class:`time`. There's also a :class:`timedelta` class representing " +"differences between two points in time, and time zone logic is implemented " +"by classes inheriting from the abstract :class:`tzinfo` class." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1692 +msgid "" +"You can create instances of :class:`date` and :class:`time` by either " +"supplying keyword arguments to the appropriate constructor, e.g. ``datetime." +"date(year=1972, month=10, day=15)``, or by using one of a number of class " +"methods. For example, the :meth:`date.today` class method returns the " +"current local date." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1698 +msgid "" +"Once created, instances of the date/time classes are all immutable. There " +"are a number of methods for producing formatted strings from objects::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1710 +msgid "" +"The :meth:`replace` method allows modifying one or more fields of a :class:" +"`date` or :class:`datetime` instance, returning a new instance::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1720 +msgid "" +"Instances can be compared, hashed, and converted to strings (the result is " +"the same as that of :meth:`isoformat`). :class:`date` and :class:`datetime` " +"instances can be subtracted from each other, and added to :class:`timedelta` " +"instances. The largest missing feature is that there's no standard library " +"support for parsing strings and getting back a :class:`date` or :class:" +"`datetime`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1727 +msgid "" +"For more information, refer to the module's reference documentation. " +"(Contributed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1734 +msgid "The optparse Module" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1736 +msgid "" +"The :mod:`getopt` module provides simple parsing of command-line arguments. " +"The new :mod:`optparse` module (originally named Optik) provides more " +"elaborate command-line parsing that follows the Unix conventions, " +"automatically creates the output for :option:`!--help`, and can perform " +"different actions for different options." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1742 +msgid "" +"You start by creating an instance of :class:`OptionParser` and telling it " +"what your program's options are. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1756 +msgid "" +"Parsing a command line is then done by calling the :meth:`parse_args` " +"method. ::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1762 +msgid "" +"This returns an object containing all of the option values, and a list of " +"strings containing the remaining arguments." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1765 +msgid "" +"Invoking the script with the various arguments now works as you'd expect it " +"to. Note that the length argument is automatically converted to an integer." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1778 +msgid "The help message is automatically generated for you:" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1793 +msgid "See the module's documentation for more details." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1796 +msgid "" +"Optik was written by Greg Ward, with suggestions from the readers of the " +"Getopt SIG." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1805 +msgid "Pymalloc: A Specialized Object Allocator" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1807 +msgid "" +"Pymalloc, a specialized object allocator written by Vladimir Marangozov, was " +"a feature added to Python 2.1. Pymalloc is intended to be faster than the " +"system :c:func:`malloc` and to have less memory overhead for allocation " +"patterns typical of Python programs. The allocator uses C's :c:func:`malloc` " +"function to get large pools of memory and then fulfills smaller memory " +"requests from these pools." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1813 +msgid "" +"In 2.1 and 2.2, pymalloc was an experimental feature and wasn't enabled by " +"default; you had to explicitly enable it when compiling Python by providing " +"the :option:`--with-pymalloc` option to the :program:`configure` script. In " +"2.3, pymalloc has had further enhancements and is now enabled by default; " +"you'll have to supply :option:`--without-pymalloc` to disable it." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1819 +msgid "" +"This change is transparent to code written in Python; however, pymalloc may " +"expose bugs in C extensions. Authors of C extension modules should test " +"their code with pymalloc enabled, because some incorrect code may cause core " +"dumps at runtime." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1824 +msgid "" +"There's one particularly common error that causes problems. There are a " +"number of memory allocation functions in Python's C API that have previously " +"just been aliases for the C library's :c:func:`malloc` and :c:func:`free`, " +"meaning that if you accidentally called mismatched functions the error " +"wouldn't be noticeable. When the object allocator is enabled, these " +"functions aren't aliases of :c:func:`malloc` and :c:func:`free` any more, " +"and calling the wrong function to free memory may get you a core dump. For " +"example, if memory was allocated using :c:func:`PyObject_Malloc`, it has to " +"be freed using :c:func:`PyObject_Free`, not :c:func:`free`. A few modules " +"included with Python fell afoul of this and had to be fixed; doubtless there " +"are more third-party modules that will have the same problem." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1836 +msgid "" +"As part of this change, the confusing multiple interfaces for allocating " +"memory have been consolidated down into two API families. Memory allocated " +"with one family must not be manipulated with functions from the other " +"family. There is one family for allocating chunks of memory and another " +"family of functions specifically for allocating Python objects." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1842 +msgid "" +"To allocate and free an undistinguished chunk of memory use the \"raw memory" +"\" family: :c:func:`PyMem_Malloc`, :c:func:`PyMem_Realloc`, and :c:func:" +"`PyMem_Free`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1845 +msgid "" +"The \"object memory\" family is the interface to the pymalloc facility " +"described above and is biased towards a large number of \"small\" " +"allocations: :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc`, and :c:" +"func:`PyObject_Free`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1849 +msgid "" +"To allocate and free Python objects, use the \"object\" family :c:func:" +"`PyObject_New`, :c:func:`PyObject_NewVar`, and :c:func:`PyObject_Del`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1852 +msgid "" +"Thanks to lots of work by Tim Peters, pymalloc in 2.3 also provides " +"debugging features to catch memory overwrites and doubled frees in both " +"extension modules and in the interpreter itself. To enable this support, " +"compile a debugging version of the Python interpreter by running :program:" +"`configure` with :option:`--with-pydebug`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1858 +msgid "" +"To aid extension writers, a header file :file:`Misc/pymemcompat.h` is " +"distributed with the source to Python 2.3 that allows Python extensions to " +"use the 2.3 interfaces to memory allocation while compiling against any " +"version of Python since 1.5.2. You would copy the file from Python's source " +"distribution and bundle it with the source of your extension." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1869 +msgid "https://hg.python.org/cpython/file/default/Objects/obmalloc.c" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1868 +msgid "" +"For the full details of the pymalloc implementation, see the comments at the " +"top of the file :file:`Objects/obmalloc.c` in the Python source code. The " +"above link points to the file within the python.org SVN browser." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1876 ../Doc/whatsnew/2.4.rst:1448 +#: ../Doc/whatsnew/2.5.rst:2079 ../Doc/whatsnew/2.6.rst:2979 +#: ../Doc/whatsnew/2.7.rst:2100 ../Doc/whatsnew/3.0.rst:852 +#: ../Doc/whatsnew/3.1.rst:473 ../Doc/whatsnew/3.2.rst:2518 +#: ../Doc/whatsnew/3.3.rst:2169 ../Doc/whatsnew/3.5.rst:2173 +#: ../Doc/whatsnew/3.6.rst:1168 +msgid "Build and C API Changes" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1878 ../Doc/whatsnew/2.5.rst:2081 +#: ../Doc/whatsnew/2.6.rst:2981 ../Doc/whatsnew/2.7.rst:2102 +#: ../Doc/whatsnew/3.1.rst:475 ../Doc/whatsnew/3.2.rst:2520 +#: ../Doc/whatsnew/3.3.rst:2171 +msgid "Changes to Python's build process and to the C API include:" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1880 +msgid "" +"The cycle detection implementation used by the garbage collection has proven " +"to be stable, so it's now been made mandatory. You can no longer compile " +"Python without it, and the :option:`--with-cycle-gc` switch to :program:" +"`configure` has been removed." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1885 +msgid "" +"Python can now optionally be built as a shared library (:file:`libpython2.3." +"so`) by supplying :option:`--enable-shared` when running Python's :program:" +"`configure` script. (Contributed by Ondrej Palkovsky.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1889 +msgid "" +"The :c:macro:`DL_EXPORT` and :c:macro:`DL_IMPORT` macros are now deprecated. " +"Initialization functions for Python extension modules should now be declared " +"using the new macro :c:macro:`PyMODINIT_FUNC`, while the Python core will " +"generally use the :c:macro:`PyAPI_FUNC` and :c:macro:`PyAPI_DATA` macros." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1894 +msgid "" +"The interpreter can be compiled without any docstrings for the built-in " +"functions and modules by supplying :option:`--without-doc-strings` to the :" +"program:`configure` script. This makes the Python executable about 10% " +"smaller, but will also mean that you can't get help for Python's built-ins. " +"(Contributed by Gustavo Niemeyer.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1900 +msgid "" +"The :c:func:`PyArg_NoArgs` macro is now deprecated, and code that uses it " +"should be changed. For Python 2.2 and later, the method definition table " +"can specify the :const:`METH_NOARGS` flag, signalling that there are no " +"arguments, and the argument checking can then be removed. If compatibility " +"with pre-2.2 versions of Python is important, the code could use " +"``PyArg_ParseTuple(args, \"\")`` instead, but this will be slower than " +"using :const:`METH_NOARGS`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1907 +msgid "" +":c:func:`PyArg_ParseTuple` accepts new format characters for various sizes " +"of unsigned integers: ``B`` for :c:type:`unsigned char`, ``H`` for :c:type:" +"`unsigned short int`, ``I`` for :c:type:`unsigned int`, and ``K`` for :c:" +"type:`unsigned long long`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1912 +msgid "" +"A new function, ``PyObject_DelItemString(mapping, char *key)`` was added as " +"shorthand for ``PyObject_DelItem(mapping, PyString_New(key))``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1915 +msgid "" +"File objects now manage their internal string buffer differently, increasing " +"it exponentially when needed. This results in the benchmark tests in :file:" +"`Lib/test/test_bufio.py` speeding up considerably (from 57 seconds to 1.7 " +"seconds, according to one measurement)." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1920 +msgid "" +"It's now possible to define class and static methods for a C extension type " +"by setting either the :const:`METH_CLASS` or :const:`METH_STATIC` flags in a " +"method's :c:type:`PyMethodDef` structure." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1924 +msgid "" +"Python now includes a copy of the Expat XML parser's source code, removing " +"any dependence on a system version or local installation of Expat." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1927 +msgid "" +"If you dynamically allocate type objects in your extension, you should be " +"aware of a change in the rules relating to the :attr:`__module__` and :attr:" +"`~definition.__name__` attributes. In summary, you will want to ensure the " +"type's dictionary contains a ``'__module__'`` key; making the module name " +"the part of the type name leading up to the final period will no longer have " +"the desired effect. For more detail, read the API reference documentation " +"or the source." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1938 ../Doc/whatsnew/2.4.rst:1501 +#: ../Doc/whatsnew/2.5.rst:2207 +msgid "Port-Specific Changes" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1940 +msgid "" +"Support for a port to IBM's OS/2 using the EMX runtime environment was " +"merged into the main Python source tree. EMX is a POSIX emulation layer " +"over the OS/2 system APIs. The Python port for EMX tries to support all the " +"POSIX-like capability exposed by the EMX runtime, and mostly succeeds; :func:" +"`fork` and :func:`fcntl` are restricted by the limitations of the underlying " +"emulation layer. The standard OS/2 port, which uses IBM's Visual Age " +"compiler, also gained support for case-sensitive import semantics as part of " +"the integration of the EMX port into CVS. (Contributed by Andrew MacIntyre.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1949 +msgid "" +"On MacOS, most toolbox modules have been weaklinked to improve backward " +"compatibility. This means that modules will no longer fail to load if a " +"single routine is missing on the current OS version. Instead calling the " +"missing routine will raise an exception. (Contributed by Jack Jansen.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1954 +msgid "" +"The RPM spec files, found in the :file:`Misc/RPM/` directory in the Python " +"source distribution, were updated for 2.3. (Contributed by Sean " +"Reifschneider.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1957 +msgid "" +"Other new platforms now supported by Python include AtheOS (http://atheos." +"cx/), GNU/Hurd, and OpenVMS." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1968 +msgid "" +"As usual, there were a bunch of other improvements and bugfixes scattered " +"throughout the source tree. A search through the CVS change logs finds " +"there were 523 patches applied and 514 bugs fixed between Python 2.2 and " +"2.3. Both figures are likely to be underestimates." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1975 +msgid "" +"If the :envvar:`PYTHONINSPECT` environment variable is set, the Python " +"interpreter will enter the interactive prompt after running a Python " +"program, as if Python had been invoked with the :option:`-i` option. The " +"environment variable can be set before running the Python interpreter, or it " +"can be set by the Python program as part of its execution." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1981 +msgid "" +"The :file:`regrtest.py` script now provides a way to allow \"all resources " +"except *foo*.\" A resource name passed to the :option:`!-u` option can now " +"be prefixed with a hyphen (``'-'``) to mean \"remove this resource.\" For " +"example, the option '``-uall,-bsddb``' could be used to enable the use of " +"all resources except ``bsddb``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1987 +msgid "" +"The tools used to build the documentation now work under Cygwin as well as " +"Unix." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1990 +msgid "" +"The ``SET_LINENO`` opcode has been removed. Back in the mists of time, this " +"opcode was needed to produce line numbers in tracebacks and support trace " +"functions (for, e.g., :mod:`pdb`). Since Python 1.5, the line numbers in " +"tracebacks have been computed using a different mechanism that works with " +"\"python -O\". For Python 2.3 Michael Hudson implemented a similar scheme " +"to determine when to call the trace function, removing the need for " +"``SET_LINENO`` entirely." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:1998 +msgid "" +"It would be difficult to detect any resulting difference from Python code, " +"apart from a slight speed up when Python is run without :option:`-O`." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2001 +msgid "" +"C extensions that access the :attr:`f_lineno` field of frame objects should " +"instead call ``PyCode_Addr2Line(f->f_code, f->f_lasti)``. This will have the " +"added effect of making the code work as desired under \"python -O\" in " +"earlier versions of Python." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2006 +msgid "" +"A nifty new feature is that trace functions can now assign to the :attr:" +"`f_lineno` attribute of frame objects, changing the line that will be " +"executed next. A ``jump`` command has been added to the :mod:`pdb` debugger " +"taking advantage of this new feature. (Implemented by Richie Hindle.)" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2015 +msgid "Porting to Python 2.3" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2017 ../Doc/whatsnew/2.4.rst:1512 +#: ../Doc/whatsnew/2.5.rst:2229 +msgid "" +"This section lists previously described changes that may require changes to " +"your code:" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2020 +msgid "" +":keyword:`yield` is now always a keyword; if it's used as a variable name in " +"your code, a different name must be chosen." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2023 +msgid "" +"For strings *X* and *Y*, ``X in Y`` now works if *X* is more than one " +"character long." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2026 +msgid "" +"The :func:`int` type constructor will now return a long integer instead of " +"raising an :exc:`OverflowError` when a string or floating-point number is " +"too large to fit into an integer." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2030 +msgid "" +"If you have Unicode strings that contain 8-bit characters, you must declare " +"the file's encoding (UTF-8, Latin-1, or whatever) by adding a comment to the " +"top of the file. See section :ref:`section-encodings` for more information." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2034 +msgid "" +"Calling Tcl methods through :mod:`_tkinter` no longer returns only strings. " +"Instead, if Tcl returns other objects those objects are converted to their " +"Python equivalent, if one exists, or wrapped with a :class:`_tkinter." +"Tcl_Obj` object if no Python equivalent exists." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2039 +msgid "" +"Large octal and hex literals such as ``0xffffffff`` now trigger a :exc:" +"`FutureWarning`. Currently they're stored as 32-bit numbers and result in a " +"negative value, but in Python 2.4 they'll become positive long integers." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2043 +msgid "" +"There are a few ways to fix this warning. If you really need a positive " +"number, just add an ``L`` to the end of the literal. If you're trying to " +"get a 32-bit integer with low bits set and have previously used an " +"expression such as ``~(1 << 31)``, it's probably clearest to start with all " +"bits set and clear the desired upper bits. For example, to clear just the " +"top bit (bit 31), you could write ``0xffffffffL &~(1L<<31)``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2050 +msgid "You can no longer disable assertions by assigning to ``__debug__``." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2052 +msgid "" +"The Distutils :func:`setup` function has gained various new keyword " +"arguments such as *depends*. Old versions of the Distutils will abort if " +"passed unknown keywords. A solution is to check for the presence of the " +"new :func:`get_distutil_options` function in your :file:`setup.py` and only " +"uses the new keywords with a version of the Distutils that supports them::" +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2065 +msgid "" +"Using ``None`` as a variable name will now result in a :exc:`SyntaxWarning` " +"warning." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2068 +msgid "" +"Names of extension types defined by the modules included with Python now " +"contain the module and a ``'.'`` in front of the type name." +msgstr "" + +#: ../Doc/whatsnew/2.3.rst:2079 +msgid "" +"The author would like to thank the following people for offering " +"suggestions, corrections and assistance with various drafts of this article: " +"Jeff Bauer, Simon Brunning, Brett Cannon, Michael Chermside, Andrew Dalke, " +"Scott David Daniels, Fred L. Drake, Jr., David Fraser, Kelly Gerber, " +"Raymond Hettinger, Michael Hudson, Chris Lambert, Detlef Lannert, Martin von " +"Löwis, Andrew MacIntyre, Lalo Martins, Chad Netzer, Gustavo Niemeyer, Neal " +"Norwitz, Hans Nowak, Chris Reedy, Francesco Ricciardi, Vinay Sajip, Neil " +"Schemenauer, Roman Suzi, Jason Tishler, Just van Rossum." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:3 +msgid "What's New in Python 2.4" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:14 +msgid "" +"This article explains the new features in Python 2.4.1, released on March " +"30, 2005." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:17 +msgid "" +"Python 2.4 is a medium-sized release. It doesn't introduce as many changes " +"as the radical Python 2.2, but introduces more features than the " +"conservative 2.3 release. The most significant new language features are " +"function decorators and generator expressions; most other changes are to the " +"standard library." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:22 +msgid "" +"According to the CVS change logs, there were 481 patches applied and 502 " +"bugs fixed between Python 2.3 and 2.4. Both figures are likely to be " +"underestimates." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:25 +msgid "" +"This article doesn't attempt to provide a complete specification of every " +"single new feature, but instead provides a brief introduction to each " +"feature. For full details, you should refer to the documentation for Python " +"2.4, such as the Python Library Reference and the Python Reference Manual. " +"Often you will be referred to the PEP for a particular new feature for " +"explanations of the implementation and design rationale." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:36 +msgid "PEP 218: Built-In Set Objects" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:38 +msgid "" +"Python 2.3 introduced the :mod:`sets` module. C implementations of set data " +"types have now been added to the Python core as two new built-in types, " +"``set(iterable)`` and ``frozenset(iterable)``. They provide high speed " +"operations for membership testing, for eliminating duplicates from " +"sequences, and for mathematical operations like unions, intersections, " +"differences, and symmetric differences. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:71 +msgid "" +"The :func:`frozenset` type is an immutable version of :func:`set`. Since it " +"is immutable and hashable, it may be used as a dictionary key or as a member " +"of another set." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:75 +msgid "" +"The :mod:`sets` module remains in the standard library, and may be useful if " +"you wish to subclass the :class:`Set` or :class:`ImmutableSet` classes. " +"There are currently no plans to deprecate the module." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:83 +msgid "" +"Originally proposed by Greg Wilson and ultimately implemented by Raymond " +"Hettinger." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:92 +msgid "" +"The lengthy transition process for this PEP, begun in Python 2.2, takes " +"another step forward in Python 2.4. In 2.3, certain integer operations that " +"would behave differently after int/long unification triggered :exc:" +"`FutureWarning` warnings and returned values limited to 32 or 64 bits " +"(depending on your platform). In 2.4, these expressions no longer produce a " +"warning and instead produce a different result that's usually a long integer." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:99 +msgid "" +"The problematic expressions are primarily left shifts and lengthy " +"hexadecimal and octal constants. For example, ``2 << 32`` results in a " +"warning in 2.3, evaluating to 0 on 32-bit platforms. In Python 2.4, this " +"expression now returns the correct answer, 8589934592." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:108 +msgid "" +"Original PEP written by Moshe Zadka and GvR. The changes for 2.4 were " +"implemented by Kalle Svensson." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:115 +msgid "PEP 289: Generator Expressions" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:117 +msgid "" +"The iterator feature introduced in Python 2.2 and the :mod:`itertools` " +"module make it easier to write programs that loop through large data sets " +"without having the entire data set in memory at one time. List " +"comprehensions don't fit into this picture very well because they produce a " +"Python list object containing all of the items. This unavoidably pulls all " +"of the objects into memory, which can be a problem if your data set is very " +"large. When trying to write a functionally-styled program, it would be " +"natural to write something like::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:129 +msgid "instead of ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:136 +msgid "" +"The first form is more concise and perhaps more readable, but if you're " +"dealing with a large number of link objects you'd have to write the second " +"form to avoid having all link objects in memory at the same time." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:140 +msgid "" +"Generator expressions work similarly to list comprehensions but don't " +"materialize the entire list; instead they create a generator that will " +"return elements one by one. The above example could be written as::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:148 +msgid "" +"Generator expressions always have to be written inside parentheses, as in " +"the above example. The parentheses signalling a function call also count, " +"so if you want to create an iterator that will be immediately passed to a " +"function you could write::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:155 +msgid "" +"Generator expressions differ from list comprehensions in various small ways. " +"Most notably, the loop variable (*obj* in the above example) is not " +"accessible outside of the generator expression. List comprehensions leave " +"the variable assigned to its last value; future versions of Python will " +"change this, making list comprehensions match generator expressions in this " +"respect." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:165 +msgid ":pep:`289` - Generator Expressions" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:165 +msgid "" +"Proposed by Raymond Hettinger and implemented by Jiwon Seo with early " +"efforts steered by Hye-Shik Chang." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:172 +msgid "PEP 292: Simpler String Substitutions" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:174 +msgid "" +"Some new classes in the standard library provide an alternative mechanism " +"for substituting variables into strings; this style of substitution may be " +"better for applications where untrained users need to edit templates." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:178 +msgid "The usual way of substituting variables by name is the ``%`` operator::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:183 +msgid "" +"When writing the template string, it can be easy to forget the ``i`` or " +"``s`` after the closing parenthesis. This isn't a big problem if the " +"template is in a Python module, because you run the code, get an " +"\"Unsupported format character\" :exc:`ValueError`, and fix the problem. " +"However, consider an application such as Mailman where template strings or " +"translations are being edited by users who aren't aware of the Python " +"language. The format string's syntax is complicated to explain to such " +"users, and if they make a mistake, it's difficult to provide helpful " +"feedback to them." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:192 +msgid "" +"PEP 292 adds a :class:`Template` class to the :mod:`string` module that uses " +"``$`` to indicate a substitution::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:200 +msgid "" +"If a key is missing from the dictionary, the :meth:`substitute` method will " +"raise a :exc:`KeyError`. There's also a :meth:`safe_substitute` method that " +"ignores missing keys::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:211 +msgid ":pep:`292` - Simpler String Substitutions" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:212 +msgid "Written and implemented by Barry Warsaw." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:218 +msgid "PEP 318: Decorators for Functions and Methods" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:220 +msgid "" +"Python 2.2 extended Python's object model by adding static methods and class " +"methods, but it didn't extend Python's syntax to provide any new way of " +"defining static or class methods. Instead, you had to write a :keyword:" +"`def` statement in the usual way, and pass the resulting method to a :func:" +"`staticmethod` or :func:`classmethod` function that would wrap up the " +"function as a method of the new type. Your code would look like this::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:233 +msgid "" +"If the method was very long, it would be easy to miss or forget the :func:" +"`classmethod` invocation after the function body." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:236 +msgid "" +"The intention was always to add some syntax to make such definitions more " +"readable, but at the time of 2.2's release a good syntax was not obvious. " +"Today a good syntax *still* isn't obvious but users are asking for easier " +"access to the feature; a new syntactic feature has been added to meet this " +"need." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:241 +msgid "" +"The new feature is called \"function decorators\". The name comes from the " +"idea that :func:`classmethod`, :func:`staticmethod`, and friends are storing " +"additional information on a function object; they're *decorating* functions " +"with more details." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:246 +msgid "" +"The notation borrows from Java and uses the ``'@'`` character as an " +"indicator. Using the new syntax, the example above would be written::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:256 +msgid "" +"The ``@classmethod`` is shorthand for the ``meth=classmethod(meth)`` " +"assignment. More generally, if you have the following::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:265 +msgid "It's equivalent to the following pre-decorator code::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:270 +msgid "" +"Decorators must come on the line before a function definition, one decorator " +"per line, and can't be on the same line as the def statement, meaning that " +"``@A def f(): ...`` is illegal. You can only decorate function definitions, " +"either at the module level or inside a class; you can't decorate class " +"definitions." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:275 +msgid "" +"A decorator is just a function that takes the function to be decorated as an " +"argument and returns either the same function or some new object. The " +"return value of the decorator need not be callable (though it typically is), " +"unless further decorators will be applied to the result. It's easy to write " +"your own decorators. The following simple example just sets an attribute on " +"the function object::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:295 +msgid "" +"As a slightly more realistic example, the following decorator checks that " +"the supplied argument is an integer::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:313 +msgid "" +"An example in :pep:`318` contains a fancier version of this idea that lets " +"you both specify the required type and check the returned type." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:316 +msgid "" +"Decorator functions can take arguments. If arguments are supplied, your " +"decorator function is called with only those arguments and must return a new " +"decorator function; this function must take a single function and return a " +"function, as previously described. In other words, ``@A @B @C(args)`` " +"becomes::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:325 +msgid "" +"Getting this right can be slightly brain-bending, but it's not too difficult." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:327 +msgid "" +"A small related change makes the :attr:`func_name` attribute of functions " +"writable. This attribute is used to display function names in tracebacks, " +"so decorators should change the name of any new function that's constructed " +"and returned." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:338 +msgid ":pep:`318` - Decorators for Functions, Methods and Classes" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:336 +msgid "" +"Written by Kevin D. Smith, Jim Jewett, and Skip Montanaro. Several people " +"wrote patches implementing function decorators, but the one that was " +"actually checked in was patch #979728, written by Mark Russell." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:340 +msgid "https://wiki.python.org/moin/PythonDecoratorLibrary" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:341 +msgid "This Wiki page contains several examples of decorators." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:347 +msgid "PEP 322: Reverse Iteration" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:349 +msgid "" +"A new built-in function, ``reversed(seq)``, takes a sequence and returns an " +"iterator that loops over the elements of the sequence in reverse order. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:359 +msgid "" +"Compared to extended slicing, such as ``range(1,4)[::-1]``, :func:`reversed` " +"is easier to read, runs faster, and uses substantially less memory." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:362 +msgid "" +"Note that :func:`reversed` only accepts sequences, not arbitrary iterators. " +"If you want to reverse an iterator, first convert it to a list with :func:" +"`list`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:376 +msgid ":pep:`322` - Reverse Iteration" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:377 +msgid "Written and implemented by Raymond Hettinger." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:383 +msgid "PEP 324: New subprocess Module" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:385 +msgid "" +"The standard library provides a number of ways to execute a subprocess, " +"offering different features and different levels of complexity. ``os." +"system(command)`` is easy to use, but slow (it runs a shell process which " +"executes the command) and dangerous (you have to be careful about escaping " +"the shell's metacharacters). The :mod:`popen2` module offers classes that " +"can capture standard output and standard error from the subprocess, but the " +"naming is confusing. The :mod:`subprocess` module cleans this up, " +"providing a unified interface that offers all the features you might need." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:394 +msgid "" +"Instead of :mod:`popen2`'s collection of classes, :mod:`subprocess` contains " +"a single class called :class:`Popen` whose constructor supports a number of " +"different keyword arguments. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:404 +msgid "" +"*args* is commonly a sequence of strings that will be the arguments to the " +"program executed as the subprocess. (If the *shell* argument is true, " +"*args* can be a string which will then be passed on to the shell for " +"interpretation, just as :func:`os.system` does.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:409 +msgid "" +"*stdin*, *stdout*, and *stderr* specify what the subprocess's input, output, " +"and error streams will be. You can provide a file object or a file " +"descriptor, or you can use the constant ``subprocess.PIPE`` to create a pipe " +"between the subprocess and the parent." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:417 +msgid "The constructor has a number of handy options:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:419 +msgid "" +"*close_fds* requests that all file descriptors be closed before running the " +"subprocess." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:422 +msgid "" +"*cwd* specifies the working directory in which the subprocess will be " +"executed (defaulting to whatever the parent's working directory is)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:425 +msgid "*env* is a dictionary specifying environment variables." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:427 +msgid "" +"*preexec_fn* is a function that gets called before the child is started." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:429 +msgid "" +"*universal_newlines* opens the child's input and output using Python's :term:" +"`universal newlines` feature." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:432 +msgid "" +"Once you've created the :class:`Popen` instance, you can call its :meth:" +"`wait` method to pause until the subprocess has exited, :meth:`poll` to " +"check if it's exited without pausing, or ``communicate(data)`` to send the " +"string *data* to the subprocess's standard input. ``communicate(data)`` " +"then reads any data that the subprocess has sent to its standard output or " +"standard error, returning a tuple ``(stdout_data, stderr_data)``." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:439 +msgid "" +":func:`call` is a shortcut that passes its arguments along to the :class:" +"`Popen` constructor, waits for the command to complete, and returns the " +"status code of the subprocess. It can serve as a safer analog to :func:`os." +"system`::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:451 +msgid "" +"The command is invoked without use of the shell. If you really do want to " +"use the shell, you can add ``shell=True`` as a keyword argument and provide " +"a string instead of a sequence::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:457 +msgid "" +"The PEP takes various examples of shell and Python code and shows how they'd " +"be translated into Python code that uses :mod:`subprocess`. Reading this " +"section of the PEP is highly recommended." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:465 +msgid ":pep:`324` - subprocess - New process module" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:465 +msgid "" +"Written and implemented by Peter Åstrand, with assistance from Fredrik Lundh " +"and others." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:472 +msgid "PEP 327: Decimal Data Type" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:474 +msgid "" +"Python has always supported floating-point (FP) numbers, based on the " +"underlying C :c:type:`double` type, as a data type. However, while most " +"programming languages provide a floating-point type, many people (even " +"programmers) are unaware that floating-point numbers don't represent certain " +"decimal fractions accurately. The new :class:`Decimal` type can represent " +"these fractions accurately, up to a user-specified precision limit." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:483 +msgid "Why is Decimal needed?" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:485 +msgid "" +"The limitations arise from the representation used for floating-point " +"numbers. FP numbers are made up of three components:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:488 +msgid "The sign, which is positive or negative." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:490 +msgid "" +"The mantissa, which is a single-digit binary number followed by a " +"fractional part. For example, ``1.01`` in base-2 notation is ``1 + 0/2 + " +"1/4``, or 1.25 in decimal notation." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:494 +msgid "" +"The exponent, which tells where the decimal point is located in the number " +"represented." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:497 +msgid "" +"For example, the number 1.25 has positive sign, a mantissa value of 1.01 (in " +"binary), and an exponent of 0 (the decimal point doesn't need to be " +"shifted). The number 5 has the same sign and mantissa, but the exponent is 2 " +"because the mantissa is multiplied by 4 (2 to the power of the exponent 2); " +"1.25 \\* 4 equals 5." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:503 +msgid "" +"Modern systems usually provide floating-point support that conforms to a " +"standard called IEEE 754. C's :c:type:`double` type is usually implemented " +"as a 64-bit IEEE 754 number, which uses 52 bits of space for the mantissa. " +"This means that numbers can only be specified to 52 bits of precision. If " +"you're trying to represent numbers whose expansion repeats endlessly, the " +"expansion is cut off after 52 bits. Unfortunately, most software needs to " +"produce output in base 10, and common fractions in base 10 are often " +"repeating decimals in binary. For example, 1.1 decimal is binary " +"``1.0001100110011 ...``; .1 = 1/16 + 1/32 + 1/256 plus an infinite number of " +"additional terms. IEEE 754 has to chop off that infinitely repeated decimal " +"after 52 digits, so the representation is slightly inaccurate." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:515 +msgid "Sometimes you can see this inaccuracy when the number is printed::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:520 +msgid "" +"The inaccuracy isn't always visible when you print the number because the FP-" +"to- decimal-string conversion is provided by the C library, and most C " +"libraries try to produce sensible output. Even if it's not displayed, " +"however, the inaccuracy is still there and subsequent operations can magnify " +"the error." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:525 +msgid "" +"For many applications this doesn't matter. If I'm plotting points and " +"displaying them on my monitor, the difference between 1.1 and " +"1.1000000000000001 is too small to be visible. Reports often limit output " +"to a certain number of decimal places, and if you round the number to two or " +"three or even eight decimal places, the error is never apparent. However, " +"for applications where it does matter, it's a lot of work to implement your " +"own custom arithmetic routines." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:533 +msgid "Hence, the :class:`Decimal` type was created." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:537 +msgid "The :class:`Decimal` type" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:539 +msgid "" +"A new module, :mod:`decimal`, was added to Python's standard library. It " +"contains two classes, :class:`Decimal` and :class:`Context`. :class:" +"`Decimal` instances represent numbers, and :class:`Context` instances are " +"used to wrap up various settings such as the precision and default rounding " +"mode." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:544 +msgid "" +":class:`Decimal` instances are immutable, like regular Python integers and " +"FP numbers; once it's been created, you can't change the value an instance " +"represents. :class:`Decimal` instances can be created from integers or " +"strings::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:555 +msgid "" +"You can also provide tuples containing the sign, the mantissa represented " +"as a tuple of decimal digits, and the exponent::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:561 +msgid "" +"Cautionary note: the sign bit is a Boolean value, so 0 is positive and 1 is " +"negative." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:564 +msgid "" +"Converting from floating-point numbers poses a bit of a problem: should the " +"FP number representing 1.1 turn into the decimal number for exactly 1.1, or " +"for 1.1 plus whatever inaccuracies are introduced? The decision was to dodge " +"the issue and leave such a conversion out of the API. Instead, you should " +"convert the floating-point number into a string using the desired precision " +"and pass the string to the :class:`Decimal` constructor::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:577 +msgid "" +"Once you have :class:`Decimal` instances, you can perform the usual " +"mathematical operations on them. One limitation: exponentiation requires an " +"integer exponent::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:598 +msgid "" +"You can combine :class:`Decimal` instances with integers, but not with " +"floating- point numbers::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:609 +msgid "" +":class:`Decimal` numbers can be used with the :mod:`math` and :mod:`cmath` " +"modules, but note that they'll be immediately converted to floating-point " +"numbers before the operation is performed, resulting in a possible loss of " +"precision and accuracy. You'll also get back a regular floating-point " +"number and not a :class:`Decimal`. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:622 +msgid "" +":class:`Decimal` instances have a :meth:`sqrt` method that returns a :class:" +"`Decimal`, but if you need other things such as trigonometric functions " +"you'll have to implement them. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:631 +msgid "The :class:`Context` type" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:633 +msgid "" +"Instances of the :class:`Context` class encapsulate several settings for " +"decimal operations:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:636 +msgid ":attr:`prec` is the precision, the number of decimal places." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:638 +msgid "" +":attr:`rounding` specifies the rounding mode. The :mod:`decimal` module has " +"constants for the various possibilities: :const:`ROUND_DOWN`, :const:" +"`ROUND_CEILING`, :const:`ROUND_HALF_EVEN`, and various others." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:642 +msgid "" +":attr:`traps` is a dictionary specifying what happens on encountering " +"certain error conditions: either an exception is raised or a value is " +"returned. Some examples of error conditions are division by zero, loss of " +"precision, and overflow." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:647 +msgid "" +"There's a thread-local default context available by calling :func:" +"`getcontext`; you can change the properties of this context to alter the " +"default precision, rounding, or trap handling. The following example shows " +"the effect of changing the precision of the default context::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:660 +msgid "" +"The default action for error conditions is selectable; the module can either " +"return a special value such as infinity or not-a-number, or exceptions can " +"be raised::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:673 +msgid "" +"The :class:`Context` instance also has various methods for formatting " +"numbers such as :meth:`to_eng_string` and :meth:`to_sci_string`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:676 +msgid "" +"For more information, see the documentation for the :mod:`decimal` module, " +"which includes a quick-start tutorial and a reference." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:684 +msgid ":pep:`327` - Decimal Data Type" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:683 +msgid "" +"Written by Facundo Batista and implemented by Facundo Batista, Eric Price, " +"Raymond Hettinger, Aahz, and Tim Peters." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:688 +msgid "http://www.lahey.com/float.htm" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:687 +msgid "" +"The article uses Fortran code to illustrate many of the problems that " +"floating- point inaccuracy can cause." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:692 +msgid "http://speleotrove.com/decimal/" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:691 +msgid "" +"A description of a decimal-based representation. This representation is " +"being proposed as a standard, and underlies the new Python decimal type. " +"Much of this material was written by Mike Cowlishaw, designer of the Rexx " +"language." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:699 +msgid "PEP 328: Multi-line Imports" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:701 +msgid "" +"One language change is a small syntactic tweak aimed at making it easier to " +"import many names from a module. In a ``from module import names`` " +"statement, *names* is a sequence of names separated by commas. If the " +"sequence is very long, you can either write multiple imports from the same " +"module, or you can use backslashes to escape the line endings like this::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:712 +msgid "" +"The syntactic change in Python 2.4 simply allows putting the names within " +"parentheses. Python ignores newlines within a parenthesized expression, so " +"the backslashes are no longer needed::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:721 +msgid "" +"The PEP also proposes that all :keyword:`import` statements be absolute " +"imports, with a leading ``.`` character to indicate a relative import. This " +"part of the PEP was not implemented for Python 2.4, but was completed for " +"Python 2.5." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:728 ../Doc/whatsnew/2.5.rst:331 +msgid ":pep:`328` - Imports: Multi-Line and Absolute/Relative" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:729 +msgid "Written by Aahz. Multi-line imports were implemented by Dima Dorfman." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:735 +msgid "PEP 331: Locale-Independent Float/String Conversions" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:737 +msgid "" +"The :mod:`locale` modules lets Python software select various conversions " +"and display conventions that are localized to a particular country or " +"language. However, the module was careful to not change the numeric locale " +"because various functions in Python's implementation required that the " +"numeric locale remain set to the ``'C'`` locale. Often this was because the " +"code was using the C library's :c:func:`atof` function." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:744 +msgid "" +"Not setting the numeric locale caused trouble for extensions that used " +"third- party C libraries, however, because they wouldn't have the correct " +"locale set. The motivating example was GTK+, whose user interface widgets " +"weren't displaying numbers in the current locale." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:749 +msgid "" +"The solution described in the PEP is to add three new functions to the " +"Python API that perform ASCII-only conversions, ignoring the locale setting:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:752 +msgid "" +"``PyOS_ascii_strtod(str, ptr)`` and ``PyOS_ascii_atof(str, ptr)`` both " +"convert a string to a C :c:type:`double`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:755 +msgid "" +"``PyOS_ascii_formatd(buffer, buf_len, format, d)`` converts a :c:type:" +"`double` to an ASCII string." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:758 +msgid "" +"The code for these functions came from the GLib library (https://developer." +"gnome.org/glib/stable/), whose developers kindly relicensed the relevant " +"functions and donated them to the Python Software Foundation. The :mod:" +"`locale` module can now change the numeric locale, letting extensions such " +"as GTK+ produce the correct results." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:767 +msgid ":pep:`331` - Locale-Independent Float/String Conversions" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:768 +msgid "Written by Christian R. Reis, and implemented by Gustavo Carneiro." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:776 +msgid "" +"Here are all of the changes that Python 2.4 makes to the core Python " +"language." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:778 +msgid "Decorators for functions and methods were added (:pep:`318`)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:780 +msgid "" +"Built-in :func:`set` and :func:`frozenset` types were added (:pep:`218`). " +"Other new built-ins include the ``reversed(seq)`` function (:pep:`322`)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:783 +msgid "Generator expressions were added (:pep:`289`)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:785 +msgid "" +"Certain numeric expressions no longer return values restricted to 32 or 64 " +"bits (:pep:`237`)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:788 +msgid "" +"You can now put parentheses around the list of names in a ``from module " +"import names`` statement (:pep:`328`)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:791 +msgid "" +"The :meth:`dict.update` method now accepts the same argument forms as the :" +"class:`dict` constructor. This includes any mapping, any iterable of key/" +"value pairs, and keyword arguments. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:795 +msgid "" +"The string methods :meth:`ljust`, :meth:`rjust`, and :meth:`center` now take " +"an optional argument for specifying a fill character other than a space. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:799 +msgid "" +"Strings also gained an :meth:`rsplit` method that works like the :meth:" +"`split` method but splits from the end of the string. (Contributed by Sean " +"Reifschneider.) ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:808 +msgid "" +"Three keyword parameters, *cmp*, *key*, and *reverse*, were added to the :" +"meth:`sort` method of lists. These parameters make some common usages of :" +"meth:`sort` simpler. All of these parameters are optional." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:812 +msgid "" +"For the *cmp* parameter, the value should be a comparison function that " +"takes two parameters and returns -1, 0, or +1 depending on how the " +"parameters compare. This function will then be used to sort the list. " +"Previously this was the only parameter that could be provided to :meth:" +"`sort`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:817 +msgid "" +"*key* should be a single-parameter function that takes a list element and " +"returns a comparison key for the element. The list is then sorted using the " +"comparison keys. The following example sorts a list case-insensitively::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:834 +msgid "" +"The last example, which uses the *cmp* parameter, is the old way to perform " +"a case-insensitive sort. It works but is slower than using a *key* " +"parameter. Using *key* calls :meth:`lower` method once for each element in " +"the list while using *cmp* will call it twice for each comparison, so using " +"*key* saves on invocations of the :meth:`lower` method." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:840 +msgid "" +"For simple key functions and comparison functions, it is often possible to " +"avoid a :keyword:`lambda` expression by using an unbound method instead. " +"For example, the above case-insensitive sort is best written as::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:848 +msgid "" +"Finally, the *reverse* parameter takes a Boolean value. If the value is " +"true, the list will be sorted into reverse order. Instead of ``L.sort(); L." +"reverse()``, you can now write ``L.sort(reverse=True)``." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:852 +msgid "" +"The results of sorting are now guaranteed to be stable. This means that two " +"entries with equal keys will be returned in the same order as they were " +"input. For example, you can sort a list of people by name, and then sort the " +"list by age, resulting in a list sorted by age where people with the same " +"age are in name-sorted order." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:858 +msgid "(All changes to :meth:`sort` contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:860 +msgid "" +"There is a new built-in function ``sorted(iterable)`` that works like the in-" +"place :meth:`list.sort` method but can be used in expressions. The " +"differences are:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:864 +msgid "the input may be any iterable;" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:866 +msgid "a newly formed copy is sorted, leaving the original intact; and" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:868 +msgid "the expression returns the new sorted copy" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:893 ../Doc/whatsnew/2.4.rst:1519 +msgid "" +"Integer operations will no longer trigger an :exc:`OverflowWarning`. The :" +"exc:`OverflowWarning` warning will disappear in Python 2.5." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:896 +msgid "" +"The interpreter gained a new switch, :option:`-m`, that takes a name, " +"searches for the corresponding module on ``sys.path``, and runs the module " +"as a script. For example, you can now run the Python profiler with ``python " +"-m profile``. (Contributed by Nick Coghlan.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:901 +msgid "" +"The ``eval(expr, globals, locals)`` and ``execfile(filename, globals, " +"locals)`` functions and the ``exec`` statement now accept any mapping type " +"for the *locals* parameter. Previously this had to be a regular Python " +"dictionary. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:906 +msgid "" +"The :func:`zip` built-in function and :func:`itertools.izip` now return an " +"empty list if called with no arguments. Previously they raised a :exc:" +"`TypeError` exception. This makes them more suitable for use with variable " +"length argument lists::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:921 +msgid "" +"Encountering a failure while importing a module no longer leaves a " +"partially- initialized module object in ``sys.modules``. The incomplete " +"module object left behind would fool further imports of the same module into " +"succeeding, leading to confusing errors. (Fixed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:926 +msgid "" +":const:`None` is now a constant; code that binds a new value to the name " +"``None`` is now a syntax error. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:935 +msgid "" +"The inner loops for list and tuple slicing were optimized and now run about " +"one-third faster. The inner loops for dictionaries were also optimized, " +"resulting in performance boosts for :meth:`keys`, :meth:`values`, :meth:" +"`items`, :meth:`iterkeys`, :meth:`itervalues`, and :meth:`iteritems`. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:941 +msgid "" +"The machinery for growing and shrinking lists was optimized for speed and " +"for space efficiency. Appending and popping from lists now runs faster due " +"to more efficient code paths and less frequent use of the underlying system :" +"c:func:`realloc`. List comprehensions also benefit. :meth:`list.extend` " +"was also optimized and no longer converts its argument into a temporary list " +"before extending the base list. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:948 +msgid "" +":func:`list`, :func:`tuple`, :func:`map`, :func:`filter`, and :func:`zip` " +"now run several times faster with non-sequence arguments that supply a :meth:" +"`__len__` method. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:952 +msgid "" +"The methods :meth:`list.__getitem__`, :meth:`dict.__getitem__`, and :meth:" +"`dict.__contains__` are now implemented as :class:`method_descriptor` " +"objects rather than :class:`wrapper_descriptor` objects. This form of " +"access doubles their performance and makes them more suitable for use as " +"arguments to functionals: ``map(mydict.__getitem__, keylist)``. (Contributed " +"by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:959 +msgid "" +"Added a new opcode, ``LIST_APPEND``, that simplifies the generated bytecode " +"for list comprehensions and speeds them up by about a third. (Contributed " +"by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:963 +msgid "" +"The peephole bytecode optimizer has been improved to produce shorter, " +"faster bytecode; remarkably, the resulting bytecode is more readable. " +"(Enhanced by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:967 +msgid "" +"String concatenations in statements of the form ``s = s + \"abc\"`` and ``s " +"+= \"abc\"`` are now performed more efficiently in certain circumstances. " +"This optimization won't be present in other Python implementations such as " +"Jython, so you shouldn't rely on it; using the :meth:`join` method of " +"strings is still recommended when you want to efficiently glue a large " +"number of strings together. (Contributed by Armin Rigo.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:974 +msgid "" +"The net result of the 2.4 optimizations is that Python 2.4 runs the pystone " +"benchmark around 5% faster than Python 2.3 and 35% faster than Python 2.2. " +"(pystone is not a particularly good benchmark, but it's the most commonly " +"used measurement of Python's performance. Your own applications may show " +"greater or smaller benefits from Python 2.4.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:997 +msgid "" +"The :mod:`asyncore` module's :func:`loop` function now has a *count* " +"parameter that lets you perform a limited number of passes through the " +"polling loop. The default is still to loop forever." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1001 +msgid "" +"The :mod:`base64` module now has more complete RFC 3548 support for Base64, " +"Base32, and Base16 encoding and decoding, including optional case folding " +"and optional alternative alphabets. (Contributed by Barry Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1005 +msgid "" +"The :mod:`bisect` module now has an underlying C implementation for improved " +"performance. (Contributed by Dmitry Vasiliev.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1008 +msgid "" +"The CJKCodecs collections of East Asian codecs, maintained by Hye-Shik " +"Chang, was integrated into 2.4. The new encodings are:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1011 +msgid "Chinese (PRC): gb2312, gbk, gb18030, big5hkscs, hz" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1013 +msgid "Chinese (ROC): big5, cp950" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1017 +msgid "Japanese: cp932, euc-jis-2004, euc-jp, euc-jisx0213, iso-2022-jp," +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1016 +msgid "" +"iso-2022-jp-1, iso-2022-jp-2, iso-2022-jp-3, iso-2022-jp-ext, iso-2022-" +"jp-2004, shift-jis, shift-jisx0213, shift-jis-2004" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1019 +msgid "Korean: cp949, euc-kr, johab, iso-2022-kr" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1021 +msgid "" +"Some other new encodings were added: HP Roman8, ISO_8859-11, ISO_8859-16, " +"PCTP-154, and TIS-620." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1024 +msgid "" +"The UTF-8 and UTF-16 codecs now cope better with receiving partial input. " +"Previously the :class:`StreamReader` class would try to read more data, " +"making it impossible to resume decoding from the stream. The :meth:`read` " +"method will now return as much data as it can and future calls will resume " +"decoding where previous ones left off. (Implemented by Walter Dörwald.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1030 +msgid "" +"There is a new :mod:`collections` module for various specialized collection " +"datatypes. Currently it contains just one type, :class:`deque`, a double- " +"ended queue that supports efficiently adding and removing elements from " +"either end::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1050 +msgid "" +"Several modules, such as the :mod:`Queue` and :mod:`threading` modules, now " +"take advantage of :class:`collections.deque` for improved performance. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1054 +msgid "" +"The :mod:`ConfigParser` classes have been enhanced slightly. The :meth:" +"`read` method now returns a list of the files that were successfully parsed, " +"and the :meth:`set` method raises :exc:`TypeError` if passed a *value* " +"argument that isn't a string. (Contributed by John Belmonte and David " +"Goodger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1059 +msgid "" +"The :mod:`curses` module now supports the ncurses extension :func:" +"`use_default_colors`. On platforms where the terminal supports " +"transparency, this makes it possible to use a transparent background. " +"(Contributed by Jörg Lehmann.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1064 +msgid "" +"The :mod:`difflib` module now includes an :class:`HtmlDiff` class that " +"creates an HTML table showing a side by side comparison of two versions of a " +"text. (Contributed by Dan Gass.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1068 +msgid "" +"The :mod:`email` package was updated to version 3.0, which dropped various " +"deprecated APIs and removes support for Python versions earlier than 2.3. " +"The 3.0 version of the package uses a new incremental parser for MIME " +"messages, available in the :mod:`email.FeedParser` module. The new parser " +"doesn't require reading the entire message into memory, and doesn't raise " +"exceptions if a message is malformed; instead it records any problems in " +"the :attr:`defect` attribute of the message. (Developed by Anthony Baxter, " +"Barry Warsaw, Thomas Wouters, and others.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1077 +msgid "" +"The :mod:`heapq` module has been converted to C. The resulting tenfold " +"improvement in speed makes the module suitable for handling high volumes of " +"data. In addition, the module has two new functions :func:`nlargest` and :" +"func:`nsmallest` that use heaps to find the N largest or smallest values in " +"a dataset without the expense of a full sort. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1083 +msgid "" +"The :mod:`httplib` module now contains constants for HTTP status codes " +"defined in various HTTP-related RFC documents. Constants have names such " +"as :const:`OK`, :const:`CREATED`, :const:`CONTINUE`, and :const:" +"`MOVED_PERMANENTLY`; use pydoc to get a full list. (Contributed by Andrew " +"Eland.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1089 +msgid "" +"The :mod:`imaplib` module now supports IMAP's THREAD command (contributed by " +"Yves Dionne) and new :meth:`deleteacl` and :meth:`myrights` methods " +"(contributed by Arnaud Mazin)." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1093 +msgid "" +"The :mod:`itertools` module gained a ``groupby(iterable[, *func*])`` " +"function. *iterable* is something that can be iterated over to return a " +"stream of elements, and the optional *func* parameter is a function that " +"takes an element and returns a key value; if omitted, the key is simply the " +"element itself. :func:`groupby` then groups the elements into subsequences " +"which have matching values of the key, and returns a series of 2-tuples " +"containing the key value and an iterator over the subsequence." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1101 +msgid "" +"Here's an example to make this clearer. The *key* function simply returns " +"whether a number is even or odd, so the result of :func:`groupby` is to " +"return consecutive runs of odd or even numbers. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1117 +msgid "" +":func:`groupby` is typically used with sorted input. The logic for :func:" +"`groupby` is similar to the Unix ``uniq`` filter which makes it handy for " +"eliminating, counting, or identifying duplicate elements::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1140 +msgid "(Contributed by Hye-Shik Chang.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1142 +msgid "" +":mod:`itertools` also gained a function named ``tee(iterator, N)`` that " +"returns *N* independent iterators that replicate *iterator*. If *N* is " +"omitted, the default is 2. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1155 +msgid "" +"Note that :func:`tee` has to keep copies of the values returned by the " +"iterator; in the worst case, it may need to keep all of them. This should " +"therefore be used carefully if the leading iterator can run far ahead of the " +"trailing iterator in a long stream of inputs. If the separation is large, " +"then you might as well use :func:`list` instead. When the iterators track " +"closely with one another, :func:`tee` is ideal. Possible applications " +"include bookmarking, windowing, or lookahead iterators. (Contributed by " +"Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1164 +msgid "" +"A number of functions were added to the :mod:`locale` module, such as :func:" +"`bind_textdomain_codeset` to specify a particular encoding and a family of :" +"func:`l\\*gettext` functions that return messages in the chosen encoding. " +"(Contributed by Gustavo Niemeyer.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1169 +msgid "" +"Some keyword arguments were added to the :mod:`logging` package's :func:" +"`basicConfig` function to simplify log configuration. The default behavior " +"is to log messages to standard error, but various keyword arguments can be " +"specified to log to a particular file, change the logging format, or set the " +"logging level. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1180 +msgid "" +"Other additions to the :mod:`logging` package include a ``log(level, msg)`` " +"convenience method, as well as a :class:`TimedRotatingFileHandler` class " +"that rotates its log files at a timed interval. The module already had :" +"class:`RotatingFileHandler`, which rotated logs once the file exceeded a " +"certain size. Both classes derive from a new :class:`BaseRotatingHandler` " +"class that can be used to implement other rotating handlers." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1187 +msgid "(Changes implemented by Vinay Sajip.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1189 +msgid "" +"The :mod:`marshal` module now shares interned strings on unpacking a data " +"structure. This may shrink the size of certain pickle strings, but the " +"primary effect is to make :file:`.pyc` files significantly smaller. " +"(Contributed by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1194 +msgid "" +"The :mod:`nntplib` module's :class:`NNTP` class gained :meth:`description` " +"and :meth:`descriptions` methods to retrieve newsgroup descriptions for a " +"single group or for a range of groups. (Contributed by Jürgen A. Erhard.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1198 +msgid "" +"Two new functions were added to the :mod:`operator` module, " +"``attrgetter(attr)`` and ``itemgetter(index)``. Both functions return " +"callables that take a single argument and return the corresponding attribute " +"or item; these callables make excellent data extractors when used with :func:" +"`map` or :func:`sorted`. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1214 +msgid "" +"The :mod:`optparse` module was updated in various ways. The module now " +"passes its messages through :func:`gettext.gettext`, making it possible to " +"internationalize Optik's help and error messages. Help messages for options " +"can now include the string ``'%default'``, which will be replaced by the " +"option's default value. (Contributed by Greg Ward.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1220 +msgid "" +"The long-term plan is to deprecate the :mod:`rfc822` module in some future " +"Python release in favor of the :mod:`email` package. To this end, the :func:" +"`email.Utils.formatdate` function has been changed to make it usable as a " +"replacement for :func:`rfc822.formatdate`. You may want to write new e-mail " +"processing code with this in mind. (Change implemented by Anthony Baxter.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1226 +msgid "" +"A new ``urandom(n)`` function was added to the :mod:`os` module, returning a " +"string containing *n* bytes of random data. This function provides access " +"to platform-specific sources of randomness such as :file:`/dev/urandom` on " +"Linux or the Windows CryptoAPI. (Contributed by Trevor Perrin.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1231 +msgid "" +"Another new function: ``os.path.lexists(path)`` returns true if the file " +"specified by *path* exists, whether or not it's a symbolic link. This " +"differs from the existing ``os.path.exists(path)`` function, which returns " +"false if *path* is a symlink that points to a destination that doesn't " +"exist. (Contributed by Beni Cherniavsky.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1237 +msgid "" +"A new :func:`getsid` function was added to the :mod:`posix` module that " +"underlies the :mod:`os` module. (Contributed by J. Raynor.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1240 +msgid "" +"The :mod:`poplib` module now supports POP over SSL. (Contributed by Hector " +"Urtubia.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1243 +msgid "" +"The :mod:`profile` module can now profile C extension functions. " +"(Contributed by Nick Bastin.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1246 +msgid "" +"The :mod:`random` module has a new method called ``getrandbits(N)`` that " +"returns a long integer *N* bits in length. The existing :meth:`randrange` " +"method now uses :meth:`getrandbits` where appropriate, making generation of " +"arbitrarily large random numbers more efficient. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1252 +msgid "" +"The regular expression language accepted by the :mod:`re` module was " +"extended with simple conditional expressions, written as ``(?(group)A|B)``. " +"*group* is either a numeric group ID or a group name defined with ``(?" +"P...)`` earlier in the expression. If the specified group matched, " +"the regular expression pattern *A* will be tested against the string; if the " +"group didn't match, the pattern *B* will be used instead. (Contributed by " +"Gustavo Niemeyer.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1259 +msgid "" +"The :mod:`re` module is also no longer recursive, thanks to a massive amount " +"of work by Gustavo Niemeyer. In a recursive regular expression engine, " +"certain patterns result in a large amount of C stack space being consumed, " +"and it was possible to overflow the stack. For example, if you matched a " +"30000-byte string of ``a`` characters against the expression ``(a|b)+``, one " +"stack frame was consumed per character. Python 2.3 tried to check for stack " +"overflow and raise a :exc:`RuntimeError` exception, but certain patterns " +"could sidestep the checking and if you were unlucky Python could segfault. " +"Python 2.4's regular expression engine can match this pattern without " +"problems." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1269 +msgid "" +"The :mod:`signal` module now performs tighter error-checking on the " +"parameters to the :func:`signal.signal` function. For example, you can't " +"set a handler on the :const:`SIGKILL` signal; previous versions of Python " +"would quietly accept this, but 2.4 will raise a :exc:`RuntimeError` " +"exception." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1274 +msgid "" +"Two new functions were added to the :mod:`socket` module. :func:`socketpair` " +"returns a pair of connected sockets and ``getservbyport(port)`` looks up the " +"service name for a given port number. (Contributed by Dave Cole and Barry " +"Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1279 +msgid "" +"The :func:`sys.exitfunc` function has been deprecated. Code should be using " +"the existing :mod:`atexit` module, which correctly handles calling multiple " +"exit functions. Eventually :func:`sys.exitfunc` will become a purely " +"internal interface, accessed only by :mod:`atexit`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1284 +msgid "" +"The :mod:`tarfile` module now generates GNU-format tar files by default. " +"(Contributed by Lars Gustäbel.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1287 +msgid "" +"The :mod:`threading` module now has an elegantly simple way to support " +"thread-local data. The module contains a :class:`local` class whose " +"attribute values are local to different threads. ::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1297 +msgid "" +"Other threads can assign and retrieve their own values for the :attr:" +"`number` and :attr:`url` attributes. You can subclass :class:`local` to " +"initialize attributes or to add methods. (Contributed by Jim Fulton.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1301 +msgid "" +"The :mod:`timeit` module now automatically disables periodic garbage " +"collection during the timing loop. This change makes consecutive timings " +"more comparable. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1305 +msgid "" +"The :mod:`weakref` module now supports a wider variety of objects including " +"Python functions, class instances, sets, frozensets, deques, arrays, files, " +"sockets, and regular expression pattern objects. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1310 +msgid "" +"The :mod:`xmlrpclib` module now supports a multi-call extension for " +"transmitting multiple XML-RPC calls in a single HTTP operation. (Contributed " +"by Brian Quinlan.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1314 +msgid "" +"The :mod:`mpz`, :mod:`rotor`, and :mod:`xreadlines` modules have been " +"removed." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1323 +msgid "cookielib" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1325 +msgid "" +"The :mod:`cookielib` library supports client-side handling for HTTP cookies, " +"mirroring the :mod:`Cookie` module's server-side cookie support. Cookies are " +"stored in cookie jars; the library transparently stores cookies offered by " +"the web server in the cookie jar, and fetches the cookie from the jar when " +"connecting to the server. As in web browsers, policy objects control whether " +"cookies are accepted or not." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1332 +msgid "" +"In order to store cookies across sessions, two implementations of cookie " +"jars are provided: one that stores cookies in the Netscape format so " +"applications can use the Mozilla or Lynx cookie files, and one that stores " +"cookies in the same format as the Perl libwww library." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1337 +msgid "" +":mod:`urllib2` has been changed to interact with :mod:`cookielib`: :class:" +"`HTTPCookieProcessor` manages a cookie jar that is used when accessing URLs." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1341 +msgid "This module was contributed by John J. Lee." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1347 ../Doc/whatsnew/3.4.rst:776 +#: ../Doc/whatsnew/3.5.rst:1088 +msgid "doctest" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1349 +msgid "" +"The :mod:`doctest` module underwent considerable refactoring thanks to " +"Edward Loper and Tim Peters. Testing can still be as simple as running :" +"func:`doctest.testmod`, but the refactorings allow customizing the module's " +"operation in various ways" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1354 +msgid "" +"The new :class:`DocTestFinder` class extracts the tests from a given " +"object's docstrings::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1370 +msgid "" +"The new :class:`DocTestRunner` class then runs individual tests and can " +"produce a summary of the results::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1379 +msgid "The above example produces the following output::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1387 +msgid "" +":class:`DocTestRunner` uses an instance of the :class:`OutputChecker` class " +"to compare the expected output with the actual output. This class takes a " +"number of different flags that customize its behaviour; ambitious users can " +"also write a completely new subclass of :class:`OutputChecker`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1392 +msgid "" +"The default output checker provides a number of handy features. For example, " +"with the :const:`doctest.ELLIPSIS` option flag, an ellipsis (``...``) in the " +"expected output matches any substring, making it easier to accommodate " +"outputs that vary in minor ways::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1403 +msgid "Another special string, ````, matches a blank line::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1411 +msgid "" +"Another new capability is producing a diff-style display of the output by " +"specifying the :const:`doctest.REPORT_UDIFF` (unified diffs), :const:" +"`doctest.REPORT_CDIFF` (context diffs), or :const:`doctest.REPORT_NDIFF` " +"(delta-style) option flags. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1427 +msgid "" +"Running the above function's tests with :const:`doctest.REPORT_UDIFF` " +"specified, you get the following output:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1450 +msgid "Some of the changes to Python's build process and to the C API are:" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1452 +msgid "" +"Three new convenience macros were added for common return values from " +"extension functions: :c:macro:`Py_RETURN_NONE`, :c:macro:`Py_RETURN_TRUE`, " +"and :c:macro:`Py_RETURN_FALSE`. (Contributed by Brett Cannon.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1456 +msgid "" +"Another new macro, :c:macro:`Py_CLEAR(obj)`, decreases the reference count " +"of *obj* and sets *obj* to the null pointer. (Contributed by Jim Fulton.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1459 +msgid "" +"A new function, ``PyTuple_Pack(N, obj1, obj2, ..., objN)``, constructs " +"tuples from a variable length argument list of Python objects. (Contributed " +"by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1463 +msgid "" +"A new function, ``PyDict_Contains(d, k)``, implements fast dictionary " +"lookups without masking exceptions raised during the look-up process. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1467 +msgid "" +"The :c:macro:`Py_IS_NAN(X)` macro returns 1 if its float or double argument " +"*X* is a NaN. (Contributed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1470 +msgid "" +"C code can avoid unnecessary locking by using the new :c:func:" +"`PyEval_ThreadsInitialized` function to tell if any thread operations have " +"been performed. If this function returns false, no lock operations are " +"needed. (Contributed by Nick Coghlan.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1475 +msgid "" +"A new function, :c:func:`PyArg_VaParseTupleAndKeywords`, is the same as :c:" +"func:`PyArg_ParseTupleAndKeywords` but takes a :c:type:`va_list` instead of " +"a number of arguments. (Contributed by Greg Chapman.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1479 +msgid "" +"A new method flag, :const:`METH_COEXISTS`, allows a function defined in " +"slots to co-exist with a :c:type:`PyCFunction` having the same name. This " +"can halve the access time for a method such as :meth:`set.__contains__`. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1484 +msgid "" +"Python can now be built with additional profiling for the interpreter " +"itself, intended as an aid to people developing the Python core. Providing :" +"option:`--enable-profiling` to the :program:`configure` script will let you " +"profile the interpreter with :program:`gprof`, and providing the :option:`--" +"with-tsc` switch enables profiling using the Pentium's Time-Stamp- Counter " +"register. Note that the :option:`--with-tsc` switch is slightly misnamed, " +"because the profiling feature also works on the PowerPC platform, though " +"that processor architecture doesn't call that register \"the TSC register" +"\". (Contributed by Jeremy Hylton.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1494 +msgid "" +"The :c:type:`tracebackobject` type has been renamed to :c:type:" +"`PyTracebackObject`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1503 +msgid "" +"The Windows port now builds under MSVC++ 7.1 as well as version 6. " +"(Contributed by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1510 +msgid "Porting to Python 2.4" +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1515 +msgid "" +"Left shifts and hexadecimal/octal constants that are too large no longer " +"trigger a :exc:`FutureWarning` and return a value limited to 32 or 64 bits; " +"instead they return a long integer." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1522 +msgid "" +"The :func:`zip` built-in function and :func:`itertools.izip` now return an " +"empty list instead of raising a :exc:`TypeError` exception if called with no " +"arguments." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1526 +msgid "" +"You can no longer compare the :class:`date` and :class:`datetime` instances " +"provided by the :mod:`datetime` module. Two instances of different classes " +"will now always be unequal, and relative comparisons (``<``, ``>``) will " +"raise a :exc:`TypeError`." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1531 +msgid "" +":func:`dircache.listdir` now passes exceptions to the caller instead of " +"returning empty lists." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1534 +msgid "" +":func:`LexicalHandler.startDTD` used to receive the public and system IDs in " +"the wrong order. This has been corrected; applications relying on the wrong " +"order need to be fixed." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1538 +msgid "" +":func:`fcntl.ioctl` now warns if the *mutate* argument is omitted and " +"relevant." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1541 +msgid "" +"The :mod:`tarfile` module now generates GNU-format tar files by default." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1543 +msgid "" +"Encountering a failure while importing a module no longer leaves a " +"partially- initialized module object in ``sys.modules``." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1546 +msgid "" +":const:`None` is now a constant; code that binds a new value to the name " +"``None`` is now a syntax error." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1549 +msgid "" +"The :func:`signals.signal` function now raises a :exc:`RuntimeError` " +"exception for certain illegal values; previously these errors would pass " +"silently. For example, you can no longer set a handler on the :const:" +"`SIGKILL` signal." +msgstr "" + +#: ../Doc/whatsnew/2.4.rst:1561 +msgid "" +"The author would like to thank the following people for offering " +"suggestions, corrections and assistance with various drafts of this article: " +"Koray Can, Hye-Shik Chang, Michael Dyck, Raymond Hettinger, Brian Hurt, " +"Hamish Lawson, Fredrik Lundh, Sean Reifschneider, Sadruddin Rejeb." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:3 +msgid "What's New in Python 2.5" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:12 +msgid "" +"This article explains the new features in Python 2.5. The final release of " +"Python 2.5 is scheduled for August 2006; :pep:`356` describes the planned " +"release schedule." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:16 +msgid "" +"The changes in Python 2.5 are an interesting mix of language and library " +"improvements. The library enhancements will be more important to Python's " +"user community, I think, because several widely-useful packages were added. " +"New modules include ElementTree for XML processing (:mod:`xml.etree`), the " +"SQLite database module (:mod:`sqlite`), and the :mod:`ctypes` module for " +"calling C functions." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:23 +msgid "" +"The language changes are of middling significance. Some pleasant new " +"features were added, but most of them aren't features that you'll use every " +"day. Conditional expressions were finally added to the language using a " +"novel syntax; see section :ref:`pep-308`. The new ':keyword:`with`' " +"statement will make writing cleanup code easier (section :ref:`pep-343`). " +"Values can now be passed into generators (section :ref:`pep-342`). Imports " +"are now visible as either absolute or relative (section :ref:`pep-328`). " +"Some corner cases of exception handling are handled better (section :ref:" +"`pep-341`). All these improvements are worthwhile, but they're improvements " +"to one specific language feature or another; none of them are broad " +"modifications to Python's semantics." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:34 +msgid "" +"As well as the language and library additions, other improvements and " +"bugfixes were made throughout the source tree. A search through the SVN " +"change logs finds there were 353 patches applied and 458 bugs fixed between " +"Python 2.4 and 2.5. (Both figures are likely to be underestimates.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:39 +msgid "" +"This article doesn't try to be a complete specification of the new features; " +"instead changes are briefly introduced using helpful examples. For full " +"details, you should always refer to the documentation for Python 2.5 at " +"https://docs.python.org. If you want to understand the complete " +"implementation and design rationale, refer to the PEP for a particular new " +"feature." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:45 +msgid "" +"Comments, suggestions, and error reports for this document are welcome; " +"please e-mail them to the author or open a bug in the Python bug tracker." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:54 +msgid "PEP 308: Conditional Expressions" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:56 +msgid "" +"For a long time, people have been requesting a way to write conditional " +"expressions, which are expressions that return value A or value B depending " +"on whether a Boolean value is true or false. A conditional expression lets " +"you write a single assignment statement that has the same effect as the " +"following::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:66 +msgid "" +"There have been endless tedious discussions of syntax on both python-dev and " +"comp.lang.python. A vote was even held that found the majority of voters " +"wanted conditional expressions in some form, but there was no syntax that " +"was preferred by a clear majority. Candidates included C's ``cond ? true_v : " +"false_v``, ``if cond then true_v else false_v``, and 16 other variations." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:72 +msgid "Guido van Rossum eventually chose a surprising syntax::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:76 +msgid "" +"Evaluation is still lazy as in existing Boolean expressions, so the order of " +"evaluation jumps around a bit. The *condition* expression in the middle is " +"evaluated first, and the *true_value* expression is evaluated only if the " +"condition was true. Similarly, the *false_value* expression is only " +"evaluated when the condition is false." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:82 +msgid "" +"This syntax may seem strange and backwards; why does the condition go in the " +"*middle* of the expression, and not in the front as in C's ``c ? x : y``? " +"The decision was checked by applying the new syntax to the modules in the " +"standard library and seeing how the resulting code read. In many cases " +"where a conditional expression is used, one value seems to be the 'common " +"case' and one value is an 'exceptional case', used only on rarer occasions " +"when the condition isn't met. The conditional syntax makes this pattern a " +"bit more obvious::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:92 +msgid "" +"I read the above statement as meaning \"here *contents* is usually assigned " +"a value of ``doc+'\\n'``; sometimes *doc* is empty, in which special case " +"an empty string is returned.\" I doubt I will use conditional expressions " +"very often where there isn't a clear common and uncommon case." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:97 +msgid "" +"There was some discussion of whether the language should require surrounding " +"conditional expressions with parentheses. The decision was made to *not* " +"require parentheses in the Python language's grammar, but as a matter of " +"style I think you should always use them. Consider these two statements::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:108 +msgid "" +"In the first version, I think a reader's eye might group the statement into " +"'level = 1', 'if logging', 'else 0', and think that the condition decides " +"whether the assignment to *level* is performed. The second version reads " +"better, in my opinion, because it makes it clear that the assignment is " +"always performed and the choice is being made between two values." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:114 +msgid "" +"Another reason for including the brackets: a few odd combinations of list " +"comprehensions and lambdas could look like incorrect conditional " +"expressions. See :pep:`308` for some examples. If you put parentheses " +"around your conditional expressions, you won't run into this case." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:123 +msgid ":pep:`308` - Conditional Expressions" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:123 +msgid "" +"PEP written by Guido van Rossum and Raymond D. Hettinger; implemented by " +"Thomas Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:132 +msgid "PEP 309: Partial Function Application" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:134 +msgid "" +"The :mod:`functools` module is intended to contain tools for functional-" +"style programming." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:137 +msgid "" +"One useful tool in this module is the :func:`partial` function. For programs " +"written in a functional style, you'll sometimes want to construct variants " +"of existing functions that have some of the parameters filled in. Consider " +"a Python function ``f(a, b, c)``; you could create a new function ``g(b, " +"c)`` that was equivalent to ``f(1, b, c)``. This is called \"partial " +"function application\"." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:144 +msgid "" +":func:`partial` takes the arguments ``(function, arg1, arg2, ... " +"kwarg1=value1, kwarg2=value2)``. The resulting object is callable, so you " +"can just call it to invoke *function* with the filled-in arguments." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:148 +msgid "Here's a small but realistic example::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:160 +msgid "" +"Here's another example, from a program that uses PyGTK. Here a context- " +"sensitive pop-up menu is being constructed dynamically. The callback " +"provided for the menu option is a partially applied version of the :meth:" +"`open_item` method, where the first argument has been provided. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:173 +msgid "" +"Another function in the :mod:`functools` module is the " +"``update_wrapper(wrapper, wrapped)`` function that helps you write well- " +"behaved decorators. :func:`update_wrapper` copies the name, module, and " +"docstring attribute to a wrapper function so that tracebacks inside the " +"wrapped function are easier to understand. For example, you might write::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:186 +msgid "" +":func:`wraps` is a decorator that can be used inside your own decorators to " +"copy the wrapped function's information. An alternate version of the " +"previous example would be::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:201 +msgid ":pep:`309` - Partial Function Application" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:201 +msgid "" +"PEP proposed and written by Peter Harris; implemented by Hye-Shik Chang and " +"Nick Coghlan, with adaptations by Raymond Hettinger." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:210 +msgid "PEP 314: Metadata for Python Software Packages v1.1" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:212 +msgid "" +"Some simple dependency support was added to Distutils. The :func:`setup` " +"function now has ``requires``, ``provides``, and ``obsoletes`` keyword " +"parameters. When you build a source distribution using the ``sdist`` " +"command, the dependency information will be recorded in the :file:`PKG-INFO` " +"file." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:217 +msgid "" +"Another new keyword parameter is ``download_url``, which should be set to a " +"URL for the package's source code. This means it's now possible to look up " +"an entry in the package index, determine the dependencies for a package, and " +"download the required packages. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:231 +msgid "" +"Another new enhancement to the Python package index at https://pypi.python." +"org is storing source and binary archives for a package. The new :command:" +"`upload` Distutils command will upload a package to the repository." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:236 +msgid "" +"Before a package can be uploaded, you must be able to build a distribution " +"using the :command:`sdist` Distutils command. Once that works, you can run " +"``python setup.py upload`` to add your package to the PyPI archive. " +"Optionally you can GPG-sign the package by supplying the :option:`--sign` " +"and :option:`--identity` options." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:242 +msgid "" +"Package uploading was implemented by Martin von Löwis and Richard Jones." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:248 +msgid ":pep:`314` - Metadata for Python Software Packages v1.1" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:248 +msgid "" +"PEP proposed and written by A.M. Kuchling, Richard Jones, and Fred Drake; " +"implemented by Richard Jones and Fred Drake." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:257 +msgid "PEP 328: Absolute and Relative Imports" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:259 +msgid "" +"The simpler part of PEP 328 was implemented in Python 2.4: parentheses could " +"now be used to enclose the names imported from a module using the ``from ... " +"import ...`` statement, making it easier to import many different names." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:263 +msgid "" +"The more complicated part has been implemented in Python 2.5: importing a " +"module can be specified to use absolute or package-relative imports. The " +"plan is to move toward making absolute imports the default in future " +"versions of Python." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:267 +msgid "Let's say you have a package directory like this::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:274 +msgid "" +"This defines a package named :mod:`pkg` containing the :mod:`pkg.main` and :" +"mod:`pkg.string` submodules." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:277 +msgid "" +"Consider the code in the :file:`main.py` module. What happens if it " +"executes the statement ``import string``? In Python 2.4 and earlier, it " +"will first look in the package's directory to perform a relative import, " +"finds :file:`pkg/string.py`, imports the contents of that file as the :mod:" +"`pkg.string` module, and that module is bound to the name ``string`` in the :" +"mod:`pkg.main` module's namespace." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:284 +msgid "" +"That's fine if :mod:`pkg.string` was what you wanted. But what if you " +"wanted Python's standard :mod:`string` module? There's no clean way to " +"ignore :mod:`pkg.string` and look for the standard module; generally you had " +"to look at the contents of ``sys.modules``, which is slightly unclean. " +"Holger Krekel's :mod:`py.std` package provides a tidier way to perform " +"imports from the standard library, ``import py; py.std.string.join()``, but " +"that package isn't available on all Python installations." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:292 +msgid "" +"Reading code which relies on relative imports is also less clear, because a " +"reader may be confused about which module, :mod:`string` or :mod:`pkg." +"string`, is intended to be used. Python users soon learned not to duplicate " +"the names of standard library modules in the names of their packages' " +"submodules, but you can't protect against having your submodule's name being " +"used for a new module added in a future version of Python." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:299 +msgid "" +"In Python 2.5, you can switch :keyword:`import`'s behaviour to absolute " +"imports using a ``from __future__ import absolute_import`` directive. This " +"absolute- import behaviour will become the default in a future version " +"(probably Python 2.7). Once absolute imports are the default, ``import " +"string`` will always find the standard library's version. It's suggested " +"that users should begin using absolute imports as much as possible, so it's " +"preferable to begin writing ``from pkg import string`` in your code." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:307 +msgid "" +"Relative imports are still possible by adding a leading period to the " +"module name when using the ``from ... import`` form::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:315 +msgid "" +"This imports the :mod:`string` module relative to the current package, so " +"in :mod:`pkg.main` this will import *name1* and *name2* from :mod:`pkg." +"string`. Additional leading periods perform the relative import starting " +"from the parent of the current package. For example, code in the :mod:`A.B." +"C` module can do::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:324 +msgid "" +"Leading periods cannot be used with the ``import modname`` form of the " +"import statement, only the ``from ... import`` form." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:331 +msgid "PEP written by Aahz; implemented by Thomas Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:333 +msgid "https://pylib.readthedocs.org/" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:334 +msgid "" +"The py library by Holger Krekel, which contains the :mod:`py.std` package." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:342 +msgid "PEP 338: Executing Modules as Scripts" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:344 +msgid "" +"The :option:`-m` switch added in Python 2.4 to execute a module as a script " +"gained a few more abilities. Instead of being implemented in C code inside " +"the Python interpreter, the switch now uses an implementation in a new " +"module, :mod:`runpy`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:349 +msgid "" +"The :mod:`runpy` module implements a more sophisticated import mechanism so " +"that it's now possible to run modules in a package such as :mod:`pychecker." +"checker`. The module also supports alternative import mechanisms such as " +"the :mod:`zipimport` module. This means you can add a .zip archive's path " +"to ``sys.path`` and then use the :option:`-m` switch to execute code from " +"the archive." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:359 +msgid ":pep:`338` - Executing modules as scripts" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:360 +msgid "PEP written and implemented by Nick Coghlan." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:368 +msgid "PEP 341: Unified try/except/finally" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:370 +msgid "" +"Until Python 2.5, the :keyword:`try` statement came in two flavours. You " +"could use a :keyword:`finally` block to ensure that code is always executed, " +"or one or more :keyword:`except` blocks to catch specific exceptions. You " +"couldn't combine both :keyword:`except` blocks and a :keyword:`finally` " +"block, because generating the right bytecode for the combined version was " +"complicated and it wasn't clear what the semantics of the combined statement " +"should be." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:377 +msgid "" +"Guido van Rossum spent some time working with Java, which does support the " +"equivalent of combining :keyword:`except` blocks and a :keyword:`finally` " +"block, and this clarified what the statement should mean. In Python 2.5, " +"you can now write::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:393 +msgid "" +"The code in *block-1* is executed. If the code raises an exception, the " +"various :keyword:`except` blocks are tested: if the exception is of class :" +"class:`Exception1`, *handler-1* is executed; otherwise if it's of class :" +"class:`Exception2`, *handler-2* is executed, and so forth. If no exception " +"is raised, the *else-block* is executed." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:399 +msgid "" +"No matter what happened previously, the *final-block* is executed once the " +"code block is complete and any raised exceptions handled. Even if there's an " +"error in an exception handler or the *else-block* and a new exception is " +"raised, the code in the *final-block* is still run." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:407 +msgid ":pep:`341` - Unifying try-except and try-finally" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:408 +msgid "PEP written by Georg Brandl; implementation by Thomas Lee." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:416 +msgid "PEP 342: New Generator Features" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:418 +msgid "" +"Python 2.5 adds a simple way to pass values *into* a generator. As " +"introduced in Python 2.3, generators only produce output; once a generator's " +"code was invoked to create an iterator, there was no way to pass any new " +"information into the function when its execution is resumed. Sometimes the " +"ability to pass in some information would be useful. Hackish solutions to " +"this include making the generator's code look at a global variable and then " +"changing the global variable's value, or passing in some mutable object that " +"callers then modify." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:426 +msgid "To refresh your memory of basic generators, here's a simple example::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:434 +msgid "" +"When you call ``counter(10)``, the result is an iterator that returns the " +"values from 0 up to 9. On encountering the :keyword:`yield` statement, the " +"iterator returns the provided value and suspends the function's execution, " +"preserving the local variables. Execution resumes on the following call to " +"the iterator's :meth:`next` method, picking up after the :keyword:`yield` " +"statement." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:440 +msgid "" +"In Python 2.3, :keyword:`yield` was a statement; it didn't return any " +"value. In 2.5, :keyword:`yield` is now an expression, returning a value " +"that can be assigned to a variable or otherwise operated on::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:446 +msgid "" +"I recommend that you always put parentheses around a :keyword:`yield` " +"expression when you're doing something with the returned value, as in the " +"above example. The parentheses aren't always necessary, but it's easier to " +"always add them instead of having to remember when they're needed." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:451 +msgid "" +"(:pep:`342` explains the exact rules, which are that a :keyword:`yield`\\ -" +"expression must always be parenthesized except when it occurs at the top-" +"level expression on the right-hand side of an assignment. This means you " +"can write ``val = yield i`` but have to use parentheses when there's an " +"operation, as in ``val = (yield i) + 12``.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:457 +msgid "" +"Values are sent into a generator by calling its ``send(value)`` method. The " +"generator's code is then resumed and the :keyword:`yield` expression returns " +"the specified *value*. If the regular :meth:`next` method is called, the :" +"keyword:`yield` returns :const:`None`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:462 +msgid "" +"Here's the previous example, modified to allow changing the value of the " +"internal counter. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:475 +msgid "And here's an example of changing the counter::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:492 +msgid "" +":keyword:`yield` will usually return :const:`None`, so you should always " +"check for this case. Don't just use its value in expressions unless you're " +"sure that the :meth:`send` method will be the only method used to resume " +"your generator function." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:497 +msgid "" +"In addition to :meth:`send`, there are two other new methods on generators:" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:499 +msgid "" +"``throw(type, value=None, traceback=None)`` is used to raise an exception " +"inside the generator; the exception is raised by the :keyword:`yield` " +"expression where the generator's execution is paused." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:503 +msgid "" +":meth:`close` raises a new :exc:`GeneratorExit` exception inside the " +"generator to terminate the iteration. On receiving this exception, the " +"generator's code must either raise :exc:`GeneratorExit` or :exc:" +"`StopIteration`. Catching the :exc:`GeneratorExit` exception and returning " +"a value is illegal and will trigger a :exc:`RuntimeError`; if the function " +"raises some other exception, that exception is propagated to the caller. :" +"meth:`close` will also be called by Python's garbage collector when the " +"generator is garbage-collected." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:511 +msgid "" +"If you need to run cleanup code when a :exc:`GeneratorExit` occurs, I " +"suggest using a ``try: ... finally:`` suite instead of catching :exc:" +"`GeneratorExit`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:514 +msgid "" +"The cumulative effect of these changes is to turn generators from one-way " +"producers of information into both producers and consumers." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:517 +msgid "" +"Generators also become *coroutines*, a more generalized form of subroutines. " +"Subroutines are entered at one point and exited at another point (the top of " +"the function, and a :keyword:`return` statement), but coroutines can be " +"entered, exited, and resumed at many different points (the :keyword:`yield` " +"statements). We'll have to figure out patterns for using coroutines " +"effectively in Python." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:523 +msgid "" +"The addition of the :meth:`close` method has one side effect that isn't " +"obvious. :meth:`close` is called when a generator is garbage-collected, so " +"this means the generator's code gets one last chance to run before the " +"generator is destroyed. This last chance means that ``try...finally`` " +"statements in generators can now be guaranteed to work; the :keyword:" +"`finally` clause will now always get a chance to run. The syntactic " +"restriction that you couldn't mix :keyword:`yield` statements with a ``try..." +"finally`` suite has therefore been removed. This seems like a minor bit of " +"language trivia, but using generators and ``try...finally`` is actually " +"necessary in order to implement the :keyword:`with` statement described by " +"PEP 343. I'll look at this new statement in the following section." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:535 +msgid "" +"Another even more esoteric effect of this change: previously, the :attr:" +"`gi_frame` attribute of a generator was always a frame object. It's now " +"possible for :attr:`gi_frame` to be ``None`` once the generator has been " +"exhausted." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:548 +msgid ":pep:`342` - Coroutines via Enhanced Generators" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:544 +msgid "" +"PEP written by Guido van Rossum and Phillip J. Eby; implemented by Phillip " +"J. Eby. Includes examples of some fancier uses of generators as coroutines." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:547 +msgid "" +"Earlier versions of these features were proposed in :pep:`288` by Raymond " +"Hettinger and :pep:`325` by Samuele Pedroni." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:551 +msgid "https://en.wikipedia.org/wiki/Coroutine" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:551 +msgid "The Wikipedia entry for coroutines." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:553 +msgid "http://www.sidhe.org/~dan/blog/archives/000178.html" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:554 +msgid "" +"An explanation of coroutines from a Perl point of view, written by Dan " +"Sugalski." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:562 ../Doc/whatsnew/2.6.rst:248 +msgid "PEP 343: The 'with' statement" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:564 ../Doc/whatsnew/2.6.rst:259 +msgid "" +"The ':keyword:`with`' statement clarifies code that previously would use " +"``try...finally`` blocks to ensure that clean-up code is executed. In this " +"section, I'll discuss the statement as it will commonly be used. In the " +"next section, I'll examine the implementation details and show how to write " +"objects for use with this statement." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:570 +msgid "" +"The ':keyword:`with`' statement is a new control-flow structure whose basic " +"structure is::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:576 +msgid "" +"The expression is evaluated, and it should result in an object that supports " +"the context management protocol (that is, has :meth:`__enter__` and :meth:" +"`__exit__` methods." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:580 ../Doc/whatsnew/2.6.rst:275 +msgid "" +"The object's :meth:`__enter__` is called before *with-block* is executed and " +"therefore can run set-up code. It also may return a value that is bound to " +"the name *variable*, if given. (Note carefully that *variable* is *not* " +"assigned the result of *expression*.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:585 ../Doc/whatsnew/2.6.rst:280 +msgid "" +"After execution of the *with-block* is finished, the object's :meth:" +"`__exit__` method is called, even if the block raised an exception, and can " +"therefore run clean-up code." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:589 +msgid "" +"To enable the statement in Python 2.5, you need to add the following " +"directive to your module::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:594 +msgid "The statement will always be enabled in Python 2.6." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:596 ../Doc/whatsnew/2.6.rst:284 +msgid "" +"Some standard Python objects now support the context management protocol and " +"can be used with the ':keyword:`with`' statement. File objects are one " +"example::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:604 ../Doc/whatsnew/2.6.rst:292 +msgid "" +"After this statement has executed, the file object in *f* will have been " +"automatically closed, even if the :keyword:`for` loop raised an exception " +"part- way through the block." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:610 ../Doc/whatsnew/2.6.rst:298 +msgid "" +"In this case, *f* is the same object created by :func:`open`, because :meth:" +"`file.__enter__` returns *self*." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:613 ../Doc/whatsnew/2.6.rst:301 +msgid "" +"The :mod:`threading` module's locks and condition variables also support " +"the ':keyword:`with`' statement::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:621 ../Doc/whatsnew/2.6.rst:309 +msgid "" +"The lock is acquired before the block is executed and always released once " +"the block is complete." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:624 +msgid "" +"The new :func:`localcontext` function in the :mod:`decimal` module makes it " +"easy to save and restore the current decimal context, which encapsulates the " +"desired precision and rounding characteristics for computations::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:643 ../Doc/whatsnew/2.6.rst:331 +msgid "Writing Context Managers" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:645 ../Doc/whatsnew/2.6.rst:333 +msgid "" +"Under the hood, the ':keyword:`with`' statement is fairly complicated. Most " +"people will only use ':keyword:`with`' in company with existing objects and " +"don't need to know these details, so you can skip the rest of this section " +"if you like. Authors of new objects will need to understand the details of " +"the underlying implementation and should keep reading." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:651 ../Doc/whatsnew/2.6.rst:339 +msgid "A high-level explanation of the context management protocol is:" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:653 ../Doc/whatsnew/2.6.rst:341 +msgid "" +"The expression is evaluated and should result in an object called a " +"\"context manager\". The context manager must have :meth:`__enter__` and :" +"meth:`__exit__` methods." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:657 +msgid "" +"The context manager's :meth:`__enter__` method is called. The value " +"returned is assigned to *VAR*. If no ``'as VAR'`` clause is present, the " +"value is simply discarded." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:661 ../Doc/whatsnew/2.6.rst:349 +msgid "The code in *BLOCK* is executed." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:663 +msgid "" +"If *BLOCK* raises an exception, the ``__exit__(type, value, traceback)`` is " +"called with the exception details, the same values returned by :func:`sys." +"exc_info`. The method's return value controls whether the exception is re-" +"raised: any false value re-raises the exception, and ``True`` will result in " +"suppressing it. You'll only rarely want to suppress the exception, because " +"if you do the author of the code containing the ':keyword:`with`' statement " +"will never realize anything went wrong." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:671 ../Doc/whatsnew/2.6.rst:360 +msgid "" +"If *BLOCK* didn't raise an exception, the :meth:`__exit__` method is still " +"called, but *type*, *value*, and *traceback* are all ``None``." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:674 ../Doc/whatsnew/2.6.rst:363 +msgid "" +"Let's think through an example. I won't present detailed code but will only " +"sketch the methods necessary for a database that supports transactions." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:677 ../Doc/whatsnew/2.6.rst:366 +msgid "" +"(For people unfamiliar with database terminology: a set of changes to the " +"database are grouped into a transaction. Transactions can be either " +"committed, meaning that all the changes are written into the database, or " +"rolled back, meaning that the changes are all discarded and the database is " +"unchanged. See any database textbook for more information.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:683 ../Doc/whatsnew/2.6.rst:372 +msgid "" +"Let's assume there's an object representing a database connection. Our goal " +"will be to let the user write code like this::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:692 ../Doc/whatsnew/2.6.rst:381 +msgid "" +"The transaction should be committed if the code in the block runs flawlessly " +"or rolled back if there's an exception. Here's the basic interface for :" +"class:`DatabaseConnection` that I'll assume::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:705 ../Doc/whatsnew/2.6.rst:394 +msgid "" +"The :meth:`__enter__` method is pretty easy, having only to start a new " +"transaction. For this application the resulting cursor object would be a " +"useful result, so the method will return it. The user can then add ``as " +"cursor`` to their ':keyword:`with`' statement to bind the cursor to a " +"variable name. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:717 ../Doc/whatsnew/2.6.rst:406 +msgid "" +"The :meth:`__exit__` method is the most complicated because it's where most " +"of the work has to be done. The method has to check if an exception " +"occurred. If there was no exception, the transaction is committed. The " +"transaction is rolled back if there was an exception." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:722 ../Doc/whatsnew/2.6.rst:411 +msgid "" +"In the code below, execution will just fall off the end of the function, " +"returning the default value of ``None``. ``None`` is false, so the " +"exception will be re-raised automatically. If you wished, you could be more " +"explicit and add a :keyword:`return` statement at the marked location. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:742 ../Doc/whatsnew/2.6.rst:431 +msgid "The contextlib module" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:744 +msgid "" +"The new :mod:`contextlib` module provides some functions and a decorator " +"that are useful for writing objects for use with the ':keyword:`with`' " +"statement." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:747 ../Doc/whatsnew/2.6.rst:436 +msgid "" +"The decorator is called :func:`contextmanager`, and lets you write a single " +"generator function instead of defining a new class. The generator should " +"yield exactly one value. The code up to the :keyword:`yield` will be " +"executed as the :meth:`__enter__` method, and the value yielded will be the " +"method's return value that will get bound to the variable in the ':keyword:" +"`with`' statement's :keyword:`as` clause, if any. The code after the :" +"keyword:`yield` will be executed in the :meth:`__exit__` method. Any " +"exception raised in the block will be raised by the :keyword:`yield` " +"statement." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:756 +msgid "" +"Our database example from the previous section could be written using this " +"decorator as::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:776 ../Doc/whatsnew/2.6.rst:465 +msgid "" +"The :mod:`contextlib` module also has a ``nested(mgr1, mgr2, ...)`` function " +"that combines a number of context managers so you don't need to write nested " +"':keyword:`with`' statements. In this example, the single ':keyword:`with`' " +"statement both starts a database transaction and acquires a thread lock::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:785 +msgid "" +"Finally, the ``closing(object)`` function returns *object* so that it can be " +"bound to a variable, and calls ``object.close`` at the end of the block. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:802 ../Doc/whatsnew/2.6.rst:492 +msgid ":pep:`343` - The \"with\" statement" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:799 ../Doc/whatsnew/2.6.rst:489 +msgid "" +"PEP written by Guido van Rossum and Nick Coghlan; implemented by Mike Bland, " +"Guido van Rossum, and Neal Norwitz. The PEP shows the code generated for a " +"':keyword:`with`' statement, which can be helpful in learning how the " +"statement works." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:804 ../Doc/whatsnew/2.6.rst:494 +msgid "The documentation for the :mod:`contextlib` module." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:812 +msgid "PEP 352: Exceptions as New-Style Classes" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:814 +msgid "" +"Exception classes can now be new-style classes, not just classic classes, " +"and the built-in :exc:`Exception` class and all the standard built-in " +"exceptions (:exc:`NameError`, :exc:`ValueError`, etc.) are now new-style " +"classes." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:818 +msgid "" +"The inheritance hierarchy for exceptions has been rearranged a bit. In 2.5, " +"the inheritance relationships are::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:827 +msgid "" +"This rearrangement was done because people often want to catch all " +"exceptions that indicate program errors. :exc:`KeyboardInterrupt` and :exc:" +"`SystemExit` aren't errors, though, and usually represent an explicit action " +"such as the user hitting :kbd:`Control-C` or code calling :func:`sys.exit`. " +"A bare ``except:`` will catch all exceptions, so you commonly need to list :" +"exc:`KeyboardInterrupt` and :exc:`SystemExit` in order to re-raise them. " +"The usual pattern is::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:842 +msgid "" +"In Python 2.5, you can now write ``except Exception`` to achieve the same " +"result, catching all the exceptions that usually indicate errors but " +"leaving :exc:`KeyboardInterrupt` and :exc:`SystemExit` alone. As in " +"previous versions, a bare ``except:`` still catches all exceptions." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:847 +msgid "" +"The goal for Python 3.0 is to require any class raised as an exception to " +"derive from :exc:`BaseException` or some descendant of :exc:`BaseException`, " +"and future releases in the Python 2.x series may begin to enforce this " +"constraint. Therefore, I suggest you begin making all your exception classes " +"derive from :exc:`Exception` now. It's been suggested that the bare " +"``except:`` form should be removed in Python 3.0, but Guido van Rossum " +"hasn't decided whether to do this or not." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:855 +msgid "" +"Raising of strings as exceptions, as in the statement ``raise \"Error " +"occurred\"``, is deprecated in Python 2.5 and will trigger a warning. The " +"aim is to be able to remove the string-exception feature in a few releases." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:862 +msgid ":pep:`352` - Required Superclass for Exceptions" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:863 +msgid "" +"PEP written by Brett Cannon and Guido van Rossum; implemented by Brett " +"Cannon." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:871 +msgid "PEP 353: Using ssize_t as the index type" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:873 +msgid "" +"A wide-ranging change to Python's C API, using a new :c:type:`Py_ssize_t` " +"type definition instead of :c:type:`int`, will permit the interpreter to " +"handle more data on 64-bit platforms. This change doesn't affect Python's " +"capacity on 32-bit platforms." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:878 +msgid "" +"Various pieces of the Python interpreter used C's :c:type:`int` type to " +"store sizes or counts; for example, the number of items in a list or tuple " +"were stored in an :c:type:`int`. The C compilers for most 64-bit platforms " +"still define :c:type:`int` as a 32-bit type, so that meant that lists could " +"only hold up to ``2**31 - 1`` = 2147483647 items. (There are actually a few " +"different programming models that 64-bit C compilers can use -- see http://" +"www.unix.org/version2/whatsnew/lp64_wp.html for a discussion -- but the most " +"commonly available model leaves :c:type:`int` as 32 bits.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:887 +msgid "" +"A limit of 2147483647 items doesn't really matter on a 32-bit platform " +"because you'll run out of memory before hitting the length limit. Each list " +"item requires space for a pointer, which is 4 bytes, plus space for a :c:" +"type:`PyObject` representing the item. 2147483647\\*4 is already more bytes " +"than a 32-bit address space can contain." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:893 +msgid "" +"It's possible to address that much memory on a 64-bit platform, however. " +"The pointers for a list that size would only require 16 GiB of space, so " +"it's not unreasonable that Python programmers might construct lists that " +"large. Therefore, the Python interpreter had to be changed to use some type " +"other than :c:type:`int`, and this will be a 64-bit type on 64-bit " +"platforms. The change will cause incompatibilities on 64-bit machines, so " +"it was deemed worth making the transition now, while the number of 64-bit " +"users is still relatively small. (In 5 or 10 years, we may *all* be on 64-" +"bit machines, and the transition would be more painful then.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:903 +msgid "" +"This change most strongly affects authors of C extension modules. Python " +"strings and container types such as lists and tuples now use :c:type:" +"`Py_ssize_t` to store their size. Functions such as :c:func:`PyList_Size` " +"now return :c:type:`Py_ssize_t`. Code in extension modules may therefore " +"need to have some variables changed to :c:type:`Py_ssize_t`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:909 +msgid "" +"The :c:func:`PyArg_ParseTuple` and :c:func:`Py_BuildValue` functions have a " +"new conversion code, ``n``, for :c:type:`Py_ssize_t`. :c:func:" +"`PyArg_ParseTuple`'s ``s#`` and ``t#`` still output :c:type:`int` by " +"default, but you can define the macro :c:macro:`PY_SSIZE_T_CLEAN` before " +"including :file:`Python.h` to make them return :c:type:`Py_ssize_t`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:915 +msgid "" +":pep:`353` has a section on conversion guidelines that extension authors " +"should read to learn about supporting 64-bit platforms." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:921 +msgid ":pep:`353` - Using ssize_t as the index type" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:922 +msgid "PEP written and implemented by Martin von Löwis." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:930 +msgid "PEP 357: The '__index__' method" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:932 +msgid "" +"The NumPy developers had a problem that could only be solved by adding a new " +"special method, :meth:`__index__`. When using slice notation, as in " +"``[start:stop:step]``, the values of the *start*, *stop*, and *step* indexes " +"must all be either integers or long integers. NumPy defines a variety of " +"specialized integer types corresponding to unsigned and signed integers of " +"8, 16, 32, and 64 bits, but there was no way to signal that these types " +"could be used as slice indexes." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:940 +msgid "" +"Slicing can't just use the existing :meth:`__int__` method because that " +"method is also used to implement coercion to integers. If slicing used :" +"meth:`__int__`, floating-point numbers would also become legal slice indexes " +"and that's clearly an undesirable behaviour." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:945 +msgid "" +"Instead, a new special method called :meth:`__index__` was added. It takes " +"no arguments and returns an integer giving the slice index to use. For " +"example::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:952 +msgid "" +"The return value must be either a Python integer or long integer. The " +"interpreter will check that the type returned is correct, and raises a :exc:" +"`TypeError` if this requirement isn't met." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:956 +msgid "" +"A corresponding :attr:`nb_index` slot was added to the C-level :c:type:" +"`PyNumberMethods` structure to let C extensions implement this protocol. " +"``PyNumber_Index(obj)`` can be used in extension code to call the :meth:" +"`__index__` function and retrieve its result." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:964 +msgid ":pep:`357` - Allowing Any Object to be Used for Slicing" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:965 +msgid "PEP written and implemented by Travis Oliphant." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:975 +msgid "" +"Here are all of the changes that Python 2.5 makes to the core Python " +"language." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:977 +msgid "" +"The :class:`dict` type has a new hook for letting subclasses provide a " +"default value when a key isn't contained in the dictionary. When a key isn't " +"found, the dictionary's ``__missing__(key)`` method will be called. This " +"hook is used to implement the new :class:`defaultdict` class in the :mod:" +"`collections` module. The following example defines a dictionary that " +"returns zero for any missing key::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:992 +msgid "" +"Both 8-bit and Unicode strings have new ``partition(sep)`` and " +"``rpartition(sep)`` methods that simplify a common use case." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:995 +msgid "" +"The ``find(S)`` method is often used to get an index which is then used to " +"slice the string and obtain the pieces that are before and after the " +"separator. ``partition(sep)`` condenses this pattern into a single method " +"call that returns a 3-tuple containing the substring before the separator, " +"the separator itself, and the substring after the separator. If the " +"separator isn't found, the first element of the tuple is the entire string " +"and the other two elements are empty. ``rpartition(sep)`` also returns a 3-" +"tuple but starts searching from the end of the string; the ``r`` stands for " +"'reverse'." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1004 +msgid "Some examples::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1017 +msgid "" +"(Implemented by Fredrik Lundh following a suggestion by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1019 +msgid "" +"The :meth:`startswith` and :meth:`endswith` methods of string types now " +"accept tuples of strings to check for. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1025 +msgid "(Implemented by Georg Brandl following a suggestion by Tom Lynn.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1029 +msgid "" +"The :func:`min` and :func:`max` built-in functions gained a ``key`` keyword " +"parameter analogous to the ``key`` argument for :meth:`sort`. This " +"parameter supplies a function that takes a single argument and is called for " +"every value in the list; :func:`min`/:func:`max` will return the element " +"with the smallest/largest return value from this function. For example, to " +"find the longest string in a list, you can do::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1042 +msgid "(Contributed by Steven Bethard and Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1044 +msgid "" +"Two new built-in functions, :func:`any` and :func:`all`, evaluate whether an " +"iterator contains any true or false values. :func:`any` returns :const:" +"`True` if any value returned by the iterator is true; otherwise it will " +"return :const:`False`. :func:`all` returns :const:`True` only if all of the " +"values returned by the iterator evaluate as true. (Suggested by Guido van " +"Rossum, and implemented by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1051 +msgid "" +"The result of a class's :meth:`__hash__` method can now be either a long " +"integer or a regular integer. If a long integer is returned, the hash of " +"that value is taken. In earlier versions the hash value was required to be " +"a regular integer, but in 2.5 the :func:`id` built-in was changed to always " +"return non-negative numbers, and users often seem to use ``id(self)`` in :" +"meth:`__hash__` methods (though this is discouraged)." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1060 +msgid "" +"ASCII is now the default encoding for modules. It's now a syntax error if " +"a module contains string literals with 8-bit characters but doesn't have an " +"encoding declaration. In Python 2.4 this triggered a warning, not a syntax " +"error. See :pep:`263` for how to declare a module's encoding; for example, " +"you might add a line like this near the top of the source file::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1068 +msgid "" +"A new warning, :class:`UnicodeWarning`, is triggered when you attempt to " +"compare a Unicode string and an 8-bit string that can't be converted to " +"Unicode using the default ASCII encoding. The result of the comparison is " +"false::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1080 +msgid "" +"Previously this would raise a :class:`UnicodeDecodeError` exception, but in " +"2.5 this could result in puzzling problems when accessing a dictionary. If " +"you looked up ``unichr(128)`` and ``chr(128)`` was being used as a key, " +"you'd get a :class:`UnicodeDecodeError` exception. Other changes in 2.5 " +"resulted in this exception being raised instead of suppressed by the code " +"in :file:`dictobject.c` that implements dictionaries." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1087 +msgid "" +"Raising an exception for such a comparison is strictly correct, but the " +"change might have broken code, so instead :class:`UnicodeWarning` was " +"introduced." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1090 +msgid "(Implemented by Marc-André Lemburg.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1092 +msgid "" +"One error that Python programmers sometimes make is forgetting to include " +"an :file:`__init__.py` module in a package directory. Debugging this mistake " +"can be confusing, and usually requires running Python with the :option:`-v` " +"switch to log all the paths searched. In Python 2.5, a new :exc:" +"`ImportWarning` warning is triggered when an import would have picked up a " +"directory as a package but no :file:`__init__.py` was found. This warning " +"is silently ignored by default; provide the :option:`-Wd <-W>` option when " +"running the Python executable to display the warning message. (Implemented " +"by Thomas Wouters.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1101 +msgid "" +"The list of base classes in a class definition can now be empty. As an " +"example, this is now legal::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1107 +msgid "(Implemented by Brett Cannon.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1115 +msgid "Interactive Interpreter Changes" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1117 +msgid "" +"In the interactive interpreter, ``quit`` and ``exit`` have long been " +"strings so that new users get a somewhat helpful message when they try to " +"quit::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1123 +msgid "" +"In Python 2.5, ``quit`` and ``exit`` are now objects that still produce " +"string representations of themselves, but are also callable. Newbies who try " +"``quit()`` or ``exit()`` will now exit the interpreter as they expect. " +"(Implemented by Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1128 +msgid "" +"The Python executable now accepts the standard long options :option:`--" +"help` and :option:`--version`; on Windows, it also accepts the :option:`/? " +"<-?>` option for displaying a help message. (Implemented by Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1140 +msgid "" +"Several of the optimizations were developed at the NeedForSpeed sprint, an " +"event held in Reykjavik, Iceland, from May 21--28 2006. The sprint focused " +"on speed enhancements to the CPython implementation and was funded by EWT " +"LLC with local support from CCP Games. Those optimizations added at this " +"sprint are specially marked in the following list." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1146 +msgid "" +"When they were introduced in Python 2.4, the built-in :class:`set` and :" +"class:`frozenset` types were built on top of Python's dictionary type. In " +"2.5 the internal data structure has been customized for implementing sets, " +"and as a result sets will use a third less memory and are somewhat faster. " +"(Implemented by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1152 +msgid "" +"The speed of some Unicode operations, such as finding substrings, string " +"splitting, and character map encoding and decoding, has been improved. " +"(Substring search and splitting improvements were added by Fredrik Lundh and " +"Andrew Dalke at the NeedForSpeed sprint. Character maps were improved by " +"Walter Dörwald and Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1160 +msgid "" +"The ``long(str, base)`` function is now faster on long digit strings because " +"fewer intermediate results are calculated. The peak is for strings of " +"around 800--1000 digits where the function is 6 times faster. (Contributed " +"by Alan McIntyre and committed at the NeedForSpeed sprint.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1167 +msgid "" +"It's now illegal to mix iterating over a file with ``for line in file`` and " +"calling the file object's :meth:`read`/:meth:`readline`/:meth:`readlines` " +"methods. Iteration uses an internal buffer and the :meth:`read\\*` methods " +"don't use that buffer. Instead they would return the data following the " +"buffer, causing the data to appear out of order. Mixing iteration and these " +"methods will now trigger a :exc:`ValueError` from the :meth:`read\\*` " +"method. (Implemented by Thomas Wouters.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1177 +msgid "" +"The :mod:`struct` module now compiles structure format strings into an " +"internal representation and caches this representation, yielding a 20% " +"speedup. (Contributed by Bob Ippolito at the NeedForSpeed sprint.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1181 +msgid "" +"The :mod:`re` module got a 1 or 2% speedup by switching to Python's " +"allocator functions instead of the system's :c:func:`malloc` and :c:func:" +"`free`. (Contributed by Jack Diederich at the NeedForSpeed sprint.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1185 +msgid "" +"The code generator's peephole optimizer now performs simple constant folding " +"in expressions. If you write something like ``a = 2+3``, the code generator " +"will do the arithmetic and produce code corresponding to ``a = 5``. " +"(Proposed and implemented by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1190 +msgid "" +"Function calls are now faster because code objects now keep the most " +"recently finished frame (a \"zombie frame\") in an internal field of the " +"code object, reusing it the next time the code object is invoked. (Original " +"patch by Michael Hudson, modified by Armin Rigo and Richard Jones; committed " +"at the NeedForSpeed sprint.) Frame objects are also slightly smaller, which " +"may improve cache locality and reduce memory usage a bit. (Contributed by " +"Neal Norwitz.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1200 +msgid "" +"Python's built-in exceptions are now new-style classes, a change that speeds " +"up instantiation considerably. Exception handling in Python 2.5 is " +"therefore about 30% faster than in 2.4. (Contributed by Richard Jones, Georg " +"Brandl and Sean Reifschneider at the NeedForSpeed sprint.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1205 +msgid "" +"Importing now caches the paths tried, recording whether they exist or not " +"so that the interpreter makes fewer :c:func:`open` and :c:func:`stat` calls " +"on startup. (Contributed by Martin von Löwis and Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1217 +msgid "New, Improved, and Removed Modules" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1219 +msgid "" +"The standard library received many enhancements and bug fixes in Python 2.5. " +"Here's a partial list of the most notable changes, sorted alphabetically by " +"module name. Consult the :file:`Misc/NEWS` file in the source tree for a " +"more complete list of changes, or look through the SVN logs for all the " +"details." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1224 +msgid "" +"The :mod:`audioop` module now supports the a-LAW encoding, and the code for " +"u-LAW encoding has been improved. (Contributed by Lars Immisch.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1227 +msgid "" +"The :mod:`codecs` module gained support for incremental codecs. The :func:" +"`codec.lookup` function now returns a :class:`CodecInfo` instance instead of " +"a tuple. :class:`CodecInfo` instances behave like a 4-tuple to preserve " +"backward compatibility but also have the attributes :attr:`encode`, :attr:" +"`decode`, :attr:`incrementalencoder`, :attr:`incrementaldecoder`, :attr:" +"`streamwriter`, and :attr:`streamreader`. Incremental codecs can receive " +"input and produce output in multiple chunks; the output is the same as if " +"the entire input was fed to the non-incremental codec. See the :mod:`codecs` " +"module documentation for details. (Designed and implemented by Walter " +"Dörwald.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1239 +msgid "" +"The :mod:`collections` module gained a new type, :class:`defaultdict`, that " +"subclasses the standard :class:`dict` type. The new type mostly behaves " +"like a dictionary but constructs a default value when a key isn't present, " +"automatically adding it to the dictionary for the requested key value." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1244 +msgid "" +"The first argument to :class:`defaultdict`'s constructor is a factory " +"function that gets called whenever a key is requested but not found. This " +"factory function receives no arguments, so you can use built-in type " +"constructors such as :func:`list` or :func:`int`. For example, you can " +"make an index of words based on their initial letter like this::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1260 +msgid "Printing ``index`` results in the following output::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1268 +msgid "(Contributed by Guido van Rossum.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1270 +msgid "" +"The :class:`deque` double-ended queue type supplied by the :mod:" +"`collections` module now has a ``remove(value)`` method that removes the " +"first occurrence of *value* in the queue, raising :exc:`ValueError` if the " +"value isn't found. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1275 +msgid "" +"New module: The :mod:`contextlib` module contains helper functions for use " +"with the new ':keyword:`with`' statement. See section :ref:`contextlibmod` " +"for more about this module." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1279 +msgid "" +"New module: The :mod:`cProfile` module is a C implementation of the " +"existing :mod:`profile` module that has much lower overhead. The module's " +"interface is the same as :mod:`profile`: you run ``cProfile.run('main()')`` " +"to profile a function, can save profile data to a file, etc. It's not yet " +"known if the Hotshot profiler, which is also written in C but doesn't match " +"the :mod:`profile` module's interface, will continue to be maintained in " +"future versions of Python. (Contributed by Armin Rigo.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1287 +msgid "" +"Also, the :mod:`pstats` module for analyzing the data measured by the " +"profiler now supports directing the output to any file object by supplying a " +"*stream* argument to the :class:`Stats` constructor. (Contributed by Skip " +"Montanaro.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1291 +msgid "" +"The :mod:`csv` module, which parses files in comma-separated value format, " +"received several enhancements and a number of bugfixes. You can now set the " +"maximum size in bytes of a field by calling the ``csv." +"field_size_limit(new_limit)`` function; omitting the *new_limit* argument " +"will return the currently-set limit. The :class:`reader` class now has a :" +"attr:`line_num` attribute that counts the number of physical lines read from " +"the source; records can span multiple physical lines, so :attr:`line_num` is " +"not the same as the number of records read." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1300 +msgid "" +"The CSV parser is now stricter about multi-line quoted fields. Previously, " +"if a line ended within a quoted field without a terminating newline " +"character, a newline would be inserted into the returned field. This " +"behavior caused problems when reading files that contained carriage return " +"characters within fields, so the code was changed to return the field " +"without inserting newlines. As a consequence, if newlines embedded within " +"fields are important, the input should be split into lines in a manner that " +"preserves the newline characters." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1308 +msgid "(Contributed by Skip Montanaro and Andrew McNamara.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1310 +msgid "" +"The :class:`datetime` class in the :mod:`datetime` module now has a " +"``strptime(string, format)`` method for parsing date strings, contributed " +"by Josh Spoerri. It uses the same format characters as :func:`time.strptime` " +"and :func:`time.strftime`::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1320 +msgid "" +"The :meth:`SequenceMatcher.get_matching_blocks` method in the :mod:`difflib` " +"module now guarantees to return a minimal list of blocks describing matching " +"subsequences. Previously, the algorithm would occasionally break a block of " +"matching elements into two list entries. (Enhancement by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1325 +msgid "" +"The :mod:`doctest` module gained a ``SKIP`` option that keeps an example " +"from being executed at all. This is intended for code snippets that are " +"usage examples intended for the reader and aren't actually test cases." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1329 +msgid "" +"An *encoding* parameter was added to the :func:`testfile` function and the :" +"class:`DocFileSuite` class to specify the file's encoding. This makes it " +"easier to use non-ASCII characters in tests contained within a docstring. " +"(Contributed by Bjorn Tillenius.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1336 +msgid "" +"The :mod:`email` package has been updated to version 4.0. (Contributed by " +"Barry Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1344 +msgid "" +"The :mod:`fileinput` module was made more flexible. Unicode filenames are " +"now supported, and a *mode* parameter that defaults to ``\"r\"`` was added " +"to the :func:`input` function to allow opening files in binary or :term:" +"`universal newlines` mode. Another new parameter, *openhook*, lets you use " +"a function other than :func:`open` to open the input files. Once you're " +"iterating over the set of files, the :class:`FileInput` object's new :meth:" +"`fileno` returns the file descriptor for the currently opened file. " +"(Contributed by Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1353 +msgid "" +"In the :mod:`gc` module, the new :func:`get_count` function returns a 3-" +"tuple containing the current collection counts for the three GC " +"generations. This is accounting information for the garbage collector; when " +"these counts reach a specified threshold, a garbage collection sweep will be " +"made. The existing :func:`gc.collect` function now takes an optional " +"*generation* argument of 0, 1, or 2 to specify which generation to collect. " +"(Contributed by Barry Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1360 +msgid "" +"The :func:`nsmallest` and :func:`nlargest` functions in the :mod:`heapq` " +"module now support a ``key`` keyword parameter similar to the one provided " +"by the :func:`min`/:func:`max` functions and the :meth:`sort` methods. For " +"example::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1374 +msgid "" +"The :func:`itertools.islice` function now accepts ``None`` for the start and " +"step arguments. This makes it more compatible with the attributes of slice " +"objects, so that you can now write the following::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1383 +msgid "" +"The :func:`format` function in the :mod:`locale` module has been modified " +"and two new functions were added, :func:`format_string` and :func:`currency`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1386 +msgid "" +"The :func:`format` function's *val* parameter could previously be a string " +"as long as no more than one %char specifier appeared; now the parameter must " +"be exactly one %char specifier with no surrounding text. An optional " +"*monetary* parameter was also added which, if ``True``, will use the " +"locale's rules for formatting currency in placing a separator between groups " +"of three digits." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1392 +msgid "" +"To format strings with multiple %char specifiers, use the new :func:" +"`format_string` function that works like :func:`format` but also supports " +"mixing %char specifiers with arbitrary text." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1396 +msgid "" +"A new :func:`currency` function was also added that formats a number " +"according to the current locale's settings." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1399 +msgid "(Contributed by Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1403 +msgid "" +"The :mod:`mailbox` module underwent a massive rewrite to add the capability " +"to modify mailboxes in addition to reading them. A new set of classes that " +"include :class:`mbox`, :class:`MH`, and :class:`Maildir` are used to read " +"mailboxes, and have an ``add(message)`` method to add messages, " +"``remove(key)`` to remove messages, and :meth:`lock`/:meth:`unlock` to lock/" +"unlock the mailbox. The following example converts a maildir-format mailbox " +"into an mbox-format one::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1421 +msgid "" +"(Contributed by Gregory K. Johnson. Funding was provided by Google's 2005 " +"Summer of Code.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1424 +msgid "" +"New module: the :mod:`msilib` module allows creating Microsoft Installer :" +"file:`.msi` files and CAB files. Some support for reading the :file:`.msi` " +"database is also included. (Contributed by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1428 +msgid "" +"The :mod:`nis` module now supports accessing domains other than the system " +"default domain by supplying a *domain* argument to the :func:`nis.match` " +"and :func:`nis.maps` functions. (Contributed by Ben Bell.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1432 +msgid "" +"The :mod:`operator` module's :func:`itemgetter` and :func:`attrgetter` " +"functions now support multiple fields. A call such as ``operator." +"attrgetter('a', 'b')`` will return a function that retrieves the :attr:`a` " +"and :attr:`b` attributes. Combining this new feature with the :meth:`sort` " +"method's ``key`` parameter lets you easily sort lists using multiple " +"fields. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1439 +msgid "" +"The :mod:`optparse` module was updated to version 1.5.1 of the Optik " +"library. The :class:`OptionParser` class gained an :attr:`epilog` attribute, " +"a string that will be printed after the help message, and a :meth:`destroy` " +"method to break reference cycles created by the object. (Contributed by Greg " +"Ward.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1444 +msgid "" +"The :mod:`os` module underwent several changes. The :attr:" +"`stat_float_times` variable now defaults to true, meaning that :func:`os." +"stat` will now return time values as floats. (This doesn't necessarily mean " +"that :func:`os.stat` will return times that are precise to fractions of a " +"second; not all systems support such precision.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1450 +msgid "" +"Constants named :attr:`os.SEEK_SET`, :attr:`os.SEEK_CUR`, and :attr:`os." +"SEEK_END` have been added; these are the parameters to the :func:`os.lseek` " +"function. Two new constants for locking are :attr:`os.O_SHLOCK` and :attr:" +"`os.O_EXLOCK`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1455 +msgid "" +"Two new functions, :func:`wait3` and :func:`wait4`, were added. They're " +"similar the :func:`waitpid` function which waits for a child process to exit " +"and returns a tuple of the process ID and its exit status, but :func:`wait3` " +"and :func:`wait4` return additional information. :func:`wait3` doesn't take " +"a process ID as input, so it waits for any child process to exit and returns " +"a 3-tuple of *process-id*, *exit-status*, *resource-usage* as returned from " +"the :func:`resource.getrusage` function. ``wait4(pid)`` does take a process " +"ID. (Contributed by Chad J. Schroeder.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1464 +msgid "" +"On FreeBSD, the :func:`os.stat` function now returns times with nanosecond " +"resolution, and the returned object now has :attr:`st_gen` and :attr:" +"`st_birthtime`. The :attr:`st_flags` attribute is also available, if the " +"platform supports it. (Contributed by Antti Louko and Diego Pettenò.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1471 +msgid "" +"The Python debugger provided by the :mod:`pdb` module can now store lists of " +"commands to execute when a breakpoint is reached and execution stops. Once " +"breakpoint #1 has been created, enter ``commands 1`` and enter a series of " +"commands to be executed, finishing the list with ``end``. The command list " +"can include commands that resume execution, such as ``continue`` or " +"``next``. (Contributed by Grégoire Dooms.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1480 +msgid "" +"The :mod:`pickle` and :mod:`cPickle` modules no longer accept a return value " +"of ``None`` from the :meth:`__reduce__` method; the method must return a " +"tuple of arguments instead. The ability to return ``None`` was deprecated " +"in Python 2.4, so this completes the removal of the feature." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1485 +msgid "" +"The :mod:`pkgutil` module, containing various utility functions for finding " +"packages, was enhanced to support PEP 302's import hooks and now also works " +"for packages stored in ZIP-format archives. (Contributed by Phillip J. Eby.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1489 +msgid "" +"The pybench benchmark suite by Marc-André Lemburg is now included in the :" +"file:`Tools/pybench` directory. The pybench suite is an improvement on the " +"commonly used :file:`pystone.py` program because pybench provides a more " +"detailed measurement of the interpreter's speed. It times particular " +"operations such as function calls, tuple slicing, method lookups, and " +"numeric operations, instead of performing many different operations and " +"reducing the result to a single number as :file:`pystone.py` does." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1497 +msgid "" +"The :mod:`pyexpat` module now uses version 2.0 of the Expat parser. " +"(Contributed by Trent Mick.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1500 +msgid "" +"The :class:`Queue` class provided by the :mod:`Queue` module gained two new " +"methods. :meth:`join` blocks until all items in the queue have been " +"retrieved and all processing work on the items have been completed. Worker " +"threads call the other new method, :meth:`task_done`, to signal that " +"processing for an item has been completed. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1506 +msgid "" +"The old :mod:`regex` and :mod:`regsub` modules, which have been deprecated " +"ever since Python 2.0, have finally been deleted. Other deleted modules: :" +"mod:`statcache`, :mod:`tzparse`, :mod:`whrandom`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1510 +msgid "" +"Also deleted: the :file:`lib-old` directory, which includes ancient modules " +"such as :mod:`dircmp` and :mod:`ni`, was removed. :file:`lib-old` wasn't on " +"the default ``sys.path``, so unless your programs explicitly added the " +"directory to ``sys.path``, this removal shouldn't affect your code." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1515 +msgid "" +"The :mod:`rlcompleter` module is no longer dependent on importing the :mod:" +"`readline` module and therefore now works on non-Unix platforms. (Patch from " +"Robert Kiendl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1521 +msgid "" +"The :mod:`SimpleXMLRPCServer` and :mod:`DocXMLRPCServer` classes now have " +"a :attr:`rpc_paths` attribute that constrains XML-RPC operations to a " +"limited set of URL paths; the default is to allow only ``'/'`` and ``'/" +"RPC2'``. Setting :attr:`rpc_paths` to ``None`` or an empty tuple disables " +"this path checking." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1528 +msgid "" +"The :mod:`socket` module now supports :const:`AF_NETLINK` sockets on Linux, " +"thanks to a patch from Philippe Biondi. Netlink sockets are a Linux-" +"specific mechanism for communications between a user-space process and " +"kernel code; an introductory article about them is at https://www." +"linuxjournal.com/article/7356. In Python code, netlink addresses are " +"represented as a tuple of 2 integers, ``(pid, group_mask)``." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1535 +msgid "" +"Two new methods on socket objects, ``recv_into(buffer)`` and " +"``recvfrom_into(buffer)``, store the received data in an object that " +"supports the buffer protocol instead of returning the data as a string. " +"This means you can put the data directly into an array or a memory-mapped " +"file." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1540 +msgid "" +"Socket objects also gained :meth:`getfamily`, :meth:`gettype`, and :meth:" +"`getproto` accessor methods to retrieve the family, type, and protocol " +"values for the socket." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1544 +msgid "" +"New module: the :mod:`spwd` module provides functions for accessing the " +"shadow password database on systems that support shadow passwords." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1547 +msgid "" +"The :mod:`struct` is now faster because it compiles format strings into :" +"class:`Struct` objects with :meth:`pack` and :meth:`unpack` methods. This " +"is similar to how the :mod:`re` module lets you create compiled regular " +"expression objects. You can still use the module-level :func:`pack` and :" +"func:`unpack` functions; they'll create :class:`Struct` objects and cache " +"them. Or you can use :class:`Struct` instances directly::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1559 +msgid "" +"You can also pack and unpack data to and from buffer objects directly using " +"the ``pack_into(buffer, offset, v1, v2, ...)`` and ``unpack_from(buffer, " +"offset)`` methods. This lets you store data directly into an array or a " +"memory- mapped file." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1564 +msgid "" +"(:class:`Struct` objects were implemented by Bob Ippolito at the " +"NeedForSpeed sprint. Support for buffer objects was added by Martin Blais, " +"also at the NeedForSpeed sprint.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1568 +msgid "" +"The Python developers switched from CVS to Subversion during the 2.5 " +"development process. Information about the exact build version is available " +"as the ``sys.subversion`` variable, a 3-tuple of ``(interpreter-name, branch-" +"name, revision-range)``. For example, at the time of writing my copy of 2.5 " +"was reporting ``('CPython', 'trunk', '45313:45315')``." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1574 +msgid "" +"This information is also available to C extensions via the :c:func:" +"`Py_GetBuildInfo` function that returns a string of build information like " +"this: ``\"trunk:45355:45356M, Apr 13 2006, 07:42:19\"``. (Contributed by " +"Barry Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1579 +msgid "" +"Another new function, :func:`sys._current_frames`, returns the current stack " +"frames for all running threads as a dictionary mapping thread identifiers to " +"the topmost stack frame currently active in that thread at the time the " +"function is called. (Contributed by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1584 +msgid "" +"The :class:`TarFile` class in the :mod:`tarfile` module now has an :meth:" +"`extractall` method that extracts all members from the archive into the " +"current working directory. It's also possible to set a different directory " +"as the extraction target, and to unpack only a subset of the archive's " +"members." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1589 +msgid "" +"The compression used for a tarfile opened in stream mode can now be " +"autodetected using the mode ``'r|*'``. (Contributed by Lars Gustäbel.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1594 +msgid "" +"The :mod:`threading` module now lets you set the stack size used when new " +"threads are created. The ``stack_size([*size*])`` function returns the " +"currently configured stack size, and supplying the optional *size* parameter " +"sets a new value. Not all platforms support changing the stack size, but " +"Windows, POSIX threading, and OS/2 all do. (Contributed by Andrew MacIntyre.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1602 +msgid "" +"The :mod:`unicodedata` module has been updated to use version 4.1.0 of the " +"Unicode character database. Version 3.2.0 is required by some " +"specifications, so it's still available as :attr:`unicodedata.ucd_3_2_0`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1606 +msgid "" +"New module: the :mod:`uuid` module generates universally unique " +"identifiers (UUIDs) according to :rfc:`4122`. The RFC defines several " +"different UUID versions that are generated from a starting string, from " +"system properties, or purely randomly. This module contains a :class:`UUID` " +"class and functions named :func:`uuid1`, :func:`uuid3`, :func:`uuid4`, " +"and :func:`uuid5` to generate different versions of UUID. (Version 2 " +"UUIDs are not specified in :rfc:`4122` and are not supported by this " +"module.) ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1631 +msgid "(Contributed by Ka-Ping Yee.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1633 +msgid "" +"The :mod:`weakref` module's :class:`WeakKeyDictionary` and :class:" +"`WeakValueDictionary` types gained new methods for iterating over the weak " +"references contained in the dictionary. :meth:`iterkeyrefs` and :meth:" +"`keyrefs` methods were added to :class:`WeakKeyDictionary`, and :meth:" +"`itervaluerefs` and :meth:`valuerefs` were added to :class:" +"`WeakValueDictionary`. (Contributed by Fred L. Drake, Jr.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1640 +msgid "" +"The :mod:`webbrowser` module received a number of enhancements. It's now " +"usable as a script with ``python -m webbrowser``, taking a URL as the " +"argument; there are a number of switches to control the behaviour (:option:" +"`-n` for a new browser window, :option:`!-t` for a new tab). New module-" +"level functions, :func:`open_new` and :func:`open_new_tab`, were added to " +"support this. The module's :func:`open` function supports an additional " +"feature, an *autoraise* parameter that signals whether to raise the open " +"window when possible. A number of additional browsers were added to the " +"supported list such as Firefox, Opera, Konqueror, and elinks. (Contributed " +"by Oleg Broytmann and Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1652 +msgid "" +"The :mod:`xmlrpclib` module now supports returning :class:`datetime` " +"objects for the XML-RPC date type. Supply ``use_datetime=True`` to the :" +"func:`loads` function or the :class:`Unmarshaller` class to enable this " +"feature. (Contributed by Skip Montanaro.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1659 +msgid "" +"The :mod:`zipfile` module now supports the ZIP64 version of the format, " +"meaning that a .zip archive can now be larger than 4 GiB and can contain " +"individual files larger than 4 GiB. (Contributed by Ronald Oussoren.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1665 +msgid "" +"The :mod:`zlib` module's :class:`Compress` and :class:`Decompress` objects " +"now support a :meth:`copy` method that makes a copy of the object's " +"internal state and returns a new :class:`Compress` or :class:`Decompress` " +"object. (Contributed by Chris AtLee.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1678 +msgid "The ctypes package" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1680 +msgid "" +"The :mod:`ctypes` package, written by Thomas Heller, has been added to the " +"standard library. :mod:`ctypes` lets you call arbitrary functions in " +"shared libraries or DLLs. Long-time users may remember the :mod:`dl` " +"module, which provides functions for loading shared libraries and calling " +"functions in them. The :mod:`ctypes` package is much fancier." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1686 +msgid "" +"To load a shared library or DLL, you must create an instance of the :class:" +"`CDLL` class and provide the name or path of the shared library or DLL. Once " +"that's done, you can call arbitrary functions by accessing them as " +"attributes of the :class:`CDLL` object. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1696 +msgid "" +"Type constructors for the various C types are provided: :func:`c_int`, :func:" +"`c_float`, :func:`c_double`, :func:`c_char_p` (equivalent to :c:type:`char " +"\\*`), and so forth. Unlike Python's types, the C versions are all mutable; " +"you can assign to their :attr:`value` attribute to change the wrapped " +"value. Python integers and strings will be automatically converted to the " +"corresponding C types, but for other types you must call the correct type " +"constructor. (And I mean *must*; getting it wrong will often result in the " +"interpreter crashing with a segmentation fault.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1705 +msgid "" +"You shouldn't use :func:`c_char_p` with a Python string when the C function " +"will be modifying the memory area, because Python strings are supposed to " +"be immutable; breaking this rule will cause puzzling bugs. When you need a " +"modifiable memory area, use :func:`create_string_buffer`::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1714 +msgid "" +"C functions are assumed to return integers, but you can set the :attr:" +"`restype` attribute of the function object to change this::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1723 +msgid "" +":mod:`ctypes` also provides a wrapper for Python's C API as the ``ctypes." +"pythonapi`` object. This object does *not* release the global interpreter " +"lock before calling a function, because the lock must be held when calling " +"into the interpreter's code. There's a :class:`py_object()` type " +"constructor that will create a :c:type:`PyObject \\*` pointer. A simple " +"usage::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1736 +msgid "" +"Don't forget to use :class:`py_object()`; if it's omitted you end up with a " +"segmentation fault." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1739 +msgid "" +":mod:`ctypes` has been around for a while, but people still write and " +"distribution hand-coded extension modules because you can't rely on :mod:" +"`ctypes` being present. Perhaps developers will begin to write Python " +"wrappers atop a library accessed through :mod:`ctypes` instead of extension " +"modules, now that :mod:`ctypes` is included with core Python." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1749 +msgid "http://starship.python.net/crew/theller/ctypes/" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1749 +msgid "The ctypes web page, with a tutorial, reference, and FAQ." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1751 +msgid "The documentation for the :mod:`ctypes` module." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1759 +msgid "The ElementTree package" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1761 +msgid "" +"A subset of Fredrik Lundh's ElementTree library for processing XML has been " +"added to the standard library as :mod:`xml.etree`. The available modules " +"are :mod:`ElementTree`, :mod:`ElementPath`, and :mod:`ElementInclude` from " +"ElementTree 1.2.6. The :mod:`cElementTree` accelerator module is also " +"included." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1767 +msgid "" +"The rest of this section will provide a brief overview of using ElementTree. " +"Full documentation for ElementTree is available at http://effbot.org/zone/" +"element-index.htm." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1771 +msgid "" +"ElementTree represents an XML document as a tree of element nodes. The text " +"content of the document is stored as the :attr:`text` and :attr:`tail` " +"attributes of (This is one of the major differences between ElementTree and " +"the Document Object Model; in the DOM there are many different types of " +"node, including :class:`TextNode`.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1777 +msgid "" +"The most commonly used parsing function is :func:`parse`, that takes either " +"a string (assumed to contain a filename) or a file-like object and returns " +"an :class:`ElementTree` instance::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1789 +msgid "" +"Once you have an :class:`ElementTree` instance, you can call its :meth:" +"`getroot` method to get the root :class:`Element` node." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1792 +msgid "" +"There's also an :func:`XML` function that takes a string literal and returns " +"an :class:`Element` node (not an :class:`ElementTree`). This function " +"provides a tidy way to incorporate XML fragments, approaching the " +"convenience of an XML literal::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1802 +msgid "" +"Each XML element supports some dictionary-like and some list-like access " +"methods. Dictionary-like operations are used to access attribute values, " +"and list-like operations are used to access child nodes." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1807 +msgid "Result" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1809 +msgid "``elem[n]``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1809 +msgid "Returns n'th child element." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1811 +msgid "``elem[m:n]``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1811 +msgid "Returns list of m'th through n'th child elements." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1814 +msgid "``len(elem)``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1814 +msgid "Returns number of child elements." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1816 +msgid "``list(elem)``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1816 +msgid "Returns list of child elements." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1818 +msgid "``elem.append(elem2)``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1818 +msgid "Adds *elem2* as a child." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1820 +msgid "``elem.insert(index, elem2)``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1820 +msgid "Inserts *elem2* at the specified location." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1822 +msgid "``del elem[n]``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1822 +msgid "Deletes n'th child element." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1824 +msgid "``elem.keys()``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1824 +msgid "Returns list of attribute names." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1826 +msgid "``elem.get(name)``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1826 +msgid "Returns value of attribute *name*." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1828 +msgid "``elem.set(name, value)``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1828 +msgid "Sets new value for attribute *name*." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1830 +msgid "``elem.attrib``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1830 +msgid "Retrieves the dictionary containing attributes." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1833 +msgid "``del elem.attrib[name]``" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1833 +msgid "Deletes attribute *name*." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1836 +msgid "" +"Comments and processing instructions are also represented as :class:" +"`Element` nodes. To check if a node is a comment or processing " +"instructions::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1844 +msgid "" +"To generate XML output, you should call the :meth:`ElementTree.write` " +"method. Like :func:`parse`, it can take either a string or a file-like " +"object::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1854 +msgid "" +"(Caution: the default encoding used for output is ASCII. For general XML " +"work, where an element's name may contain arbitrary Unicode characters, " +"ASCII isn't a very useful encoding because it will raise an exception if an " +"element's name contains any characters with values greater than 127. " +"Therefore, it's best to specify a different encoding such as UTF-8 that can " +"handle any Unicode character.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1861 +msgid "" +"This section is only a partial description of the ElementTree interfaces. " +"Please read the package's official documentation for more details." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1867 +msgid "http://effbot.org/zone/element-index.htm" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1868 +msgid "Official documentation for ElementTree." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1876 +msgid "The hashlib package" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1878 +msgid "" +"A new :mod:`hashlib` module, written by Gregory P. Smith, has been added to " +"replace the :mod:`md5` and :mod:`sha` modules. :mod:`hashlib` adds support " +"for additional secure hashes (SHA-224, SHA-256, SHA-384, and SHA-512). When " +"available, the module uses OpenSSL for fast platform optimized " +"implementations of algorithms." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1884 +msgid "" +"The old :mod:`md5` and :mod:`sha` modules still exist as wrappers around " +"hashlib to preserve backwards compatibility. The new module's interface is " +"very close to that of the old modules, but not identical. The most " +"significant difference is that the constructor functions for creating new " +"hashing objects are named differently. ::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1913 +msgid "" +"Once a hash object has been created, its methods are the same as before: " +"``update(string)`` hashes the specified string into the current digest " +"state, :meth:`digest` and :meth:`hexdigest` return the digest value as a " +"binary string or a string of hex digits, and :meth:`copy` returns a new " +"hashing object with the same digest state." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1922 +msgid "The documentation for the :mod:`hashlib` module." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1930 +msgid "The sqlite3 package" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1932 +msgid "" +"The pysqlite module (http://www.pysqlite.org), a wrapper for the SQLite " +"embedded database, has been added to the standard library under the package " +"name :mod:`sqlite3`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1936 +msgid "" +"SQLite is a C library that provides a lightweight disk-based database that " +"doesn't require a separate server process and allows accessing the database " +"using a nonstandard variant of the SQL query language. Some applications can " +"use SQLite for internal data storage. It's also possible to prototype an " +"application using SQLite and then port the code to a larger database such as " +"PostgreSQL or Oracle." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1943 +msgid "" +"pysqlite was written by Gerhard Häring and provides a SQL interface " +"compliant with the DB-API 2.0 specification described by :pep:`249`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1946 +msgid "" +"If you're compiling the Python source yourself, note that the source tree " +"doesn't include the SQLite code, only the wrapper module. You'll need to " +"have the SQLite libraries and headers installed before compiling Python, and " +"the build process will compile the module when the necessary headers are " +"available." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1951 +msgid "" +"To use the module, you must first create a :class:`Connection` object that " +"represents the database. Here the data will be stored in the :file:`/tmp/" +"example` file::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1957 +msgid "" +"You can also supply the special name ``:memory:`` to create a database in " +"RAM." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1959 +msgid "" +"Once you have a :class:`Connection`, you can create a :class:`Cursor` " +"object and call its :meth:`execute` method to perform SQL commands::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1973 +msgid "" +"Usually your SQL operations will need to use values from Python variables. " +"You shouldn't assemble your query using Python's string operations because " +"doing so is insecure; it makes your program vulnerable to an SQL injection " +"attack." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1977 +msgid "" +"Instead, use the DB-API's parameter substitution. Put ``?`` as a " +"placeholder wherever you want to use a value, and then provide a tuple of " +"values as the second argument to the cursor's :meth:`execute` method. " +"(Other database modules may use a different placeholder, such as ``%s`` or " +"``:1``.) For example::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:1997 +msgid "" +"To retrieve data after executing a SELECT statement, you can either treat " +"the cursor as an iterator, call the cursor's :meth:`fetchone` method to " +"retrieve a single matching row, or call :meth:`fetchall` to get a list of " +"the matching rows." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2002 +msgid "This example uses the iterator form::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2015 +msgid "" +"For more information about the SQL dialect supported by SQLite, see https://" +"www.sqlite.org." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2022 +msgid "http://www.pysqlite.org" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2022 +msgid "The pysqlite web page." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2026 +msgid "https://www.sqlite.org" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2025 +msgid "" +"The SQLite web page; the documentation describes the syntax and the " +"available data types for the supported SQL dialect." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2028 +msgid "The documentation for the :mod:`sqlite3` module." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2030 +msgid ":pep:`249` - Database API Specification 2.0" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2031 +msgid "PEP written by Marc-André Lemburg." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2039 +msgid "The wsgiref package" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2041 +msgid "" +"The Web Server Gateway Interface (WSGI) v1.0 defines a standard interface " +"between web servers and Python web applications and is described in :pep:" +"`333`. The :mod:`wsgiref` package is a reference implementation of the WSGI " +"specification." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2048 +msgid "" +"The package includes a basic HTTP server that will run a WSGI application; " +"this server is useful for debugging but isn't intended for production use. " +"Setting up a server takes only a few lines of code::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2068 +msgid "http://www.wsgi.org" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2068 +msgid "A central web site for WSGI-related resources." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2070 +msgid ":pep:`333` - Python Web Server Gateway Interface v1.0" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2071 +msgid "PEP written by Phillip J. Eby." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2083 +msgid "" +"The Python source tree was converted from CVS to Subversion, in a complex " +"migration procedure that was supervised and flawlessly carried out by Martin " +"von Löwis. The procedure was developed as :pep:`347`." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2087 +msgid "" +"Coverity, a company that markets a source code analysis tool called Prevent, " +"provided the results of their examination of the Python source code. The " +"analysis found about 60 bugs that were quickly fixed. Many of the bugs " +"were refcounting problems, often occurring in error-handling code. See " +"https://scan.coverity.com for the statistics." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2093 +msgid "" +"The largest change to the C API came from :pep:`353`, which modifies the " +"interpreter to use a :c:type:`Py_ssize_t` type definition instead of :c:type:" +"`int`. See the earlier section :ref:`pep-353` for a discussion of this " +"change." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2098 +msgid "" +"The design of the bytecode compiler has changed a great deal, no longer " +"generating bytecode by traversing the parse tree. Instead the parse tree is " +"converted to an abstract syntax tree (or AST), and it is the abstract " +"syntax tree that's traversed to produce the bytecode." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2103 +msgid "" +"It's possible for Python code to obtain AST objects by using the :func:" +"`compile` built-in and specifying ``_ast.PyCF_ONLY_AST`` as the value of " +"the *flags* parameter::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2116 +msgid "" +"No official documentation has been written for the AST code yet, but :pep:" +"`339` discusses the design. To start learning about the code, read the " +"definition of the various AST nodes in :file:`Parser/Python.asdl`. A Python " +"script reads this file and generates a set of C structure definitions in :" +"file:`Include/Python-ast.h`. The :c:func:`PyParser_ASTFromString` and :c:" +"func:`PyParser_ASTFromFile`, defined in :file:`Include/pythonrun.h`, take " +"Python source as input and return the root of an AST representing the " +"contents. This AST can then be turned into a code object by :c:func:" +"`PyAST_Compile`. For more information, read the source code, and then ask " +"questions on python-dev." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2126 +msgid "" +"The AST code was developed under Jeremy Hylton's management, and implemented " +"by (in alphabetical order) Brett Cannon, Nick Coghlan, Grant Edwards, John " +"Ehresman, Kurt Kaiser, Neal Norwitz, Tim Peters, Armin Rigo, and Neil " +"Schemenauer, plus the participants in a number of AST sprints at conferences " +"such as PyCon." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2135 +msgid "" +"Evan Jones's patch to obmalloc, first described in a talk at PyCon DC 2005, " +"was applied. Python 2.4 allocated small objects in 256K-sized arenas, but " +"never freed arenas. With this patch, Python will free arenas when they're " +"empty. The net effect is that on some platforms, when you allocate many " +"objects, Python's memory usage may actually drop when you delete them and " +"the memory may be returned to the operating system. (Implemented by Evan " +"Jones, and reworked by Tim Peters.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2143 +msgid "" +"Note that this change means extension modules must be more careful when " +"allocating memory. Python's API has many different functions for allocating " +"memory that are grouped into families. For example, :c:func:" +"`PyMem_Malloc`, :c:func:`PyMem_Realloc`, and :c:func:`PyMem_Free` are one " +"family that allocates raw memory, while :c:func:`PyObject_Malloc`, :c:func:" +"`PyObject_Realloc`, and :c:func:`PyObject_Free` are another family that's " +"supposed to be used for creating Python objects." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2151 +msgid "" +"Previously these different families all reduced to the platform's :c:func:" +"`malloc` and :c:func:`free` functions. This meant it didn't matter if you " +"got things wrong and allocated memory with the :c:func:`PyMem` function but " +"freed it with the :c:func:`PyObject` function. With 2.5's changes to " +"obmalloc, these families now do different things and mismatches will " +"probably result in a segfault. You should carefully test your C extension " +"modules with Python 2.5." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2158 +msgid "" +"The built-in set types now have an official C API. Call :c:func:`PySet_New` " +"and :c:func:`PyFrozenSet_New` to create a new set, :c:func:`PySet_Add` and :" +"c:func:`PySet_Discard` to add and remove elements, and :c:func:" +"`PySet_Contains` and :c:func:`PySet_Size` to examine the set's state. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2164 +msgid "" +"C code can now obtain information about the exact revision of the Python " +"interpreter by calling the :c:func:`Py_GetBuildInfo` function that returns " +"a string of build information like this: ``\"trunk:45355:45356M, Apr 13 " +"2006, 07:42:19\"``. (Contributed by Barry Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2169 +msgid "" +"Two new macros can be used to indicate C functions that are local to the " +"current file so that a faster calling convention can be used. " +"``Py_LOCAL(type)`` declares the function as returning a value of the " +"specified *type* and uses a fast-calling qualifier. " +"``Py_LOCAL_INLINE(type)`` does the same thing and also requests the function " +"be inlined. If :c:func:`PY_LOCAL_AGGRESSIVE` is defined before :file:" +"`python.h` is included, a set of more aggressive optimizations are enabled " +"for the module; you should benchmark the results to find out if these " +"optimizations actually make the code faster. (Contributed by Fredrik Lundh " +"at the NeedForSpeed sprint.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2180 +msgid "" +"``PyErr_NewException(name, base, dict)`` can now accept a tuple of base " +"classes as its *base* argument. (Contributed by Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2183 +msgid "" +"The :c:func:`PyErr_Warn` function for issuing warnings is now deprecated in " +"favour of ``PyErr_WarnEx(category, message, stacklevel)`` which lets you " +"specify the number of stack frames separating this function and the caller. " +"A *stacklevel* of 1 is the function calling :c:func:`PyErr_WarnEx`, 2 is the " +"function above that, and so forth. (Added by Neal Norwitz.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2189 +msgid "" +"The CPython interpreter is still written in C, but the code can now be " +"compiled with a C++ compiler without errors. (Implemented by Anthony " +"Baxter, Martin von Löwis, Skip Montanaro.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2193 +msgid "" +"The :c:func:`PyRange_New` function was removed. It was never documented, " +"never used in the core code, and had dangerously lax error checking. In the " +"unlikely case that your extensions were using it, you can replace it by " +"something like the following::" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2209 +msgid "" +"MacOS X (10.3 and higher): dynamic loading of modules now uses the :c:func:" +"`dlopen` function instead of MacOS-specific functions." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2212 +msgid "" +"MacOS X: an :option:`--enable-universalsdk` switch was added to the :program:" +"`configure` script that compiles the interpreter as a universal binary able " +"to run on both PowerPC and Intel processors. (Contributed by Ronald " +"Oussoren; :issue:`2573`.)" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2217 +msgid "" +"Windows: :file:`.dll` is no longer supported as a filename extension for " +"extension modules. :file:`.pyd` is now the only filename extension that " +"will be searched for." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2227 +msgid "Porting to Python 2.5" +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2232 +msgid "" +"ASCII is now the default encoding for modules. It's now a syntax error if " +"a module contains string literals with 8-bit characters but doesn't have an " +"encoding declaration. In Python 2.4 this triggered a warning, not a syntax " +"error." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2237 +msgid "" +"Previously, the :attr:`gi_frame` attribute of a generator was always a frame " +"object. Because of the :pep:`342` changes described in section :ref:" +"`pep-342`, it's now possible for :attr:`gi_frame` to be ``None``." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2241 +msgid "" +"A new warning, :class:`UnicodeWarning`, is triggered when you attempt to " +"compare a Unicode string and an 8-bit string that can't be converted to " +"Unicode using the default ASCII encoding. Previously such comparisons would " +"raise a :class:`UnicodeDecodeError` exception." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2246 +msgid "" +"Library: the :mod:`csv` module is now stricter about multi-line quoted " +"fields. If your files contain newlines embedded within fields, the input " +"should be split into lines in a manner which preserves the newline " +"characters." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2250 +msgid "" +"Library: the :mod:`locale` module's :func:`format` function's would " +"previously accept any string as long as no more than one %char specifier " +"appeared. In Python 2.5, the argument must be exactly one %char specifier " +"with no surrounding text." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2255 +msgid "" +"Library: The :mod:`pickle` and :mod:`cPickle` modules no longer accept a " +"return value of ``None`` from the :meth:`__reduce__` method; the method must " +"return a tuple of arguments instead. The modules also no longer accept the " +"deprecated *bin* keyword parameter." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2260 +msgid "" +"Library: The :mod:`SimpleXMLRPCServer` and :mod:`DocXMLRPCServer` classes " +"now have a :attr:`rpc_paths` attribute that constrains XML-RPC operations to " +"a limited set of URL paths; the default is to allow only ``'/'`` and ``'/" +"RPC2'``. Setting :attr:`rpc_paths` to ``None`` or an empty tuple disables " +"this path checking." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2266 +msgid "" +"C API: Many functions now use :c:type:`Py_ssize_t` instead of :c:type:`int` " +"to allow processing more data on 64-bit machines. Extension code may need " +"to make the same change to avoid warnings and to support 64-bit machines. " +"See the earlier section :ref:`pep-353` for a discussion of this change." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2271 +msgid "" +"C API: The obmalloc changes mean that you must be careful to not mix usage " +"of the :c:func:`PyMem_\\*` and :c:func:`PyObject_\\*` families of functions. " +"Memory allocated with one family's :c:func:`\\*_Malloc` must be freed with " +"the corresponding family's :c:func:`\\*_Free` function." +msgstr "" + +#: ../Doc/whatsnew/2.5.rst:2282 +msgid "" +"The author would like to thank the following people for offering " +"suggestions, corrections and assistance with various drafts of this article: " +"Georg Brandl, Nick Coghlan, Phillip J. Eby, Lars Gustäbel, Raymond " +"Hettinger, Ralf W. Grosse- Kunstleve, Kent Johnson, Iain Lowe, Martin von " +"Löwis, Fredrik Lundh, Andrew McNamara, Skip Montanaro, Gustavo Niemeyer, " +"Paul Prescod, James Pryor, Mike Rovner, Scott Weikart, Barry Warsaw, Thomas " +"Wouters." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:5 +msgid "What's New in Python 2.6" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:9 ../Doc/whatsnew/2.7.rst:5 +msgid "A.M. Kuchling (amk at amk.ca)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:52 +msgid "" +"This article explains the new features in Python 2.6, released on October 1 " +"2008. The release schedule is described in :pep:`361`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:55 +msgid "" +"The major theme of Python 2.6 is preparing the migration path to Python 3.0, " +"a major redesign of the language. Whenever possible, Python 2.6 " +"incorporates new features and syntax from 3.0 while remaining compatible " +"with existing code by not removing older features or syntax. When it's not " +"possible to do that, Python 2.6 tries to do what it can, adding " +"compatibility functions in a :mod:`future_builtins` module and a :option:" +"`-3` switch to warn about usages that will become unsupported in 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:64 +msgid "" +"Some significant new packages have been added to the standard library, such " +"as the :mod:`multiprocessing` and :mod:`json` modules, but there aren't many " +"new features that aren't related to Python 3.0 in some way." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:69 +msgid "" +"Python 2.6 also sees a number of improvements and bugfixes throughout the " +"source. A search through the change logs finds there were 259 patches " +"applied and 612 bugs fixed between Python 2.5 and 2.6. Both figures are " +"likely to be underestimates." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:74 +msgid "" +"This article doesn't attempt to provide a complete specification of the new " +"features, but instead provides a convenient overview. For full details, you " +"should refer to the documentation for Python 2.6. If you want to understand " +"the rationale for the design and implementation, refer to the PEP for a " +"particular new feature. Whenever possible, \"What's New in Python\" links to " +"the bug/patch item for each change." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:90 +msgid "Python 3.0" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:92 +msgid "" +"The development cycle for Python versions 2.6 and 3.0 was synchronized, with " +"the alpha and beta releases for both versions being made on the same days. " +"The development of 3.0 has influenced many features in 2.6." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:97 +msgid "" +"Python 3.0 is a far-ranging redesign of Python that breaks compatibility " +"with the 2.x series. This means that existing Python code will need some " +"conversion in order to run on Python 3.0. However, not all the changes in " +"3.0 necessarily break compatibility. In cases where new features won't " +"cause existing code to break, they've been backported to 2.6 and are " +"described in this document in the appropriate place. Some of the 3.0-" +"derived features are:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:106 +msgid "" +"A :meth:`__complex__` method for converting objects to a complex number." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:107 +msgid "Alternate syntax for catching exceptions: ``except TypeError as exc``." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:108 +msgid "" +"The addition of :func:`functools.reduce` as a synonym for the built-in :func:" +"`reduce` function." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:111 +msgid "" +"Python 3.0 adds several new built-in functions and changes the semantics of " +"some existing builtins. Functions that are new in 3.0 such as :func:`bin` " +"have simply been added to Python 2.6, but existing builtins haven't been " +"changed; instead, the :mod:`future_builtins` module has versions with the " +"new 3.0 semantics. Code written to be compatible with 3.0 can do ``from " +"future_builtins import hex, map`` as necessary." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:119 +msgid "" +"A new command-line switch, :option:`-3`, enables warnings about features " +"that will be removed in Python 3.0. You can run code with this switch to " +"see how much work will be necessary to port code to 3.0. The value of this " +"switch is available to Python code as the boolean variable :data:`sys." +"py3kwarning`, and to C extension code as :c:data:`Py_Py3kWarningFlag`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:128 +msgid "" +"The 3xxx series of PEPs, which contains proposals for Python 3.0. :pep:" +"`3000` describes the development process for Python 3.0. Start with :pep:" +"`3100` that describes the general goals for Python 3.0, and then explore the " +"higher-numbered PEPS that propose specific features." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:136 +msgid "Changes to the Development Process" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:138 +msgid "" +"While 2.6 was being developed, the Python development process underwent two " +"significant changes: we switched from SourceForge's issue tracker to a " +"customized Roundup installation, and the documentation was converted from " +"LaTeX to reStructuredText." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:145 +msgid "New Issue Tracker: Roundup" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:147 +msgid "" +"For a long time, the Python developers had been growing increasingly annoyed " +"by SourceForge's bug tracker. SourceForge's hosted solution doesn't permit " +"much customization; for example, it wasn't possible to customize the life " +"cycle of issues." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:152 +msgid "" +"The infrastructure committee of the Python Software Foundation therefore " +"posted a call for issue trackers, asking volunteers to set up different " +"products and import some of the bugs and patches from SourceForge. Four " +"different trackers were examined: `Jira `__, `Launchpad `__, `Roundup `__, and `Trac `__. The " +"committee eventually settled on Jira and Roundup as the two candidates. " +"Jira is a commercial product that offers no-cost hosted instances to free-" +"software projects; Roundup is an open-source project that requires " +"volunteers to administer it and a server to host it." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:166 +msgid "" +"After posting a call for volunteers, a new Roundup installation was set up " +"at https://bugs.python.org. One installation of Roundup can host multiple " +"trackers, and this server now also hosts issue trackers for Jython and for " +"the Python web site. It will surely find other uses in the future. Where " +"possible, this edition of \"What's New in Python\" links to the bug/patch " +"item for each change." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:174 +msgid "" +"Hosting of the Python bug tracker is kindly provided by `Upfront Systems " +"`__ of Stellenbosch, South Africa. Martin " +"von Löwis put a lot of effort into importing existing bugs and patches from " +"SourceForge; his scripts for this import operation are at http://svn.python." +"org/view/tracker/importer/ and may be useful to other projects wishing to " +"move from SourceForge to Roundup." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:185 +msgid "https://bugs.python.org" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:185 +msgid "The Python bug tracker." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:188 +msgid "http://bugs.jython.org:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:188 +msgid "The Jython bug tracker." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:191 +msgid "http://roundup.sourceforge.net/" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:191 +msgid "Roundup downloads and documentation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:193 +msgid "http://svn.python.org/view/tracker/importer/" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:194 +msgid "Martin von Löwis's conversion scripts." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:197 +msgid "New Documentation Format: reStructuredText Using Sphinx" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:199 +msgid "" +"The Python documentation was written using LaTeX since the project started " +"around 1989. In the 1980s and early 1990s, most documentation was printed " +"out for later study, not viewed online. LaTeX was widely used because it " +"provided attractive printed output while remaining straightforward to write " +"once the basic rules of the markup were learned." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:206 +msgid "" +"Today LaTeX is still used for writing publications destined for printing, " +"but the landscape for programming tools has shifted. We no longer print out " +"reams of documentation; instead, we browse through it online and HTML has " +"become the most important format to support. Unfortunately, converting LaTeX " +"to HTML is fairly complicated and Fred L. Drake Jr., the long-time Python " +"documentation editor, spent a lot of time maintaining the conversion " +"process. Occasionally people would suggest converting the documentation " +"into SGML and later XML, but performing a good conversion is a major task " +"and no one ever committed the time required to finish the job." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:217 +msgid "" +"During the 2.6 development cycle, Georg Brandl put a lot of effort into " +"building a new toolchain for processing the documentation. The resulting " +"package is called Sphinx, and is available from http://sphinx-doc.org/." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:222 +msgid "" +"Sphinx concentrates on HTML output, producing attractively styled and modern " +"HTML; printed output is still supported through conversion to LaTeX. The " +"input format is reStructuredText, a markup syntax supporting custom " +"extensions and directives that is commonly used in the Python community." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:228 +msgid "" +"Sphinx is a standalone package that can be used for writing, and almost two " +"dozen other projects (`listed on the Sphinx web site `__) have adopted Sphinx as their documentation tool." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:236 +msgid "" +"`Documenting Python `__" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:236 +msgid "Describes how to write for Python's documentation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:239 +msgid "`Sphinx `__" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:239 +msgid "Documentation and code for the Sphinx toolchain." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:241 +msgid "`Docutils `__" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:242 +msgid "The underlying reStructuredText parser and toolset." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:250 +msgid "" +"The previous version, Python 2.5, added the ':keyword:`with`' statement as " +"an optional feature, to be enabled by a ``from __future__ import " +"with_statement`` directive. In 2.6 the statement no longer needs to be " +"specially enabled; this means that :keyword:`with` is now always a keyword. " +"The rest of this section is a copy of the corresponding section from the " +"\"What's New in Python 2.5\" document; if you're familiar with the ':keyword:" +"`with`' statement from Python 2.5, you can skip this section." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:265 +msgid "" +"The ':keyword:`with`' statement is a control-flow structure whose basic " +"structure is::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:271 +msgid "" +"The expression is evaluated, and it should result in an object that supports " +"the context management protocol (that is, has :meth:`__enter__` and :meth:" +"`__exit__` methods)." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:312 +msgid "" +"The :func:`localcontext` function in the :mod:`decimal` module makes it easy " +"to save and restore the current decimal context, which encapsulates the " +"desired precision and rounding characteristics for computations::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:345 +msgid "" +"The context manager's :meth:`__enter__` method is called. The value " +"returned is assigned to *VAR*. If no ``as VAR`` clause is present, the " +"value is simply discarded." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:351 +msgid "" +"If *BLOCK* raises an exception, the context manager's :meth:`__exit__` " +"method is called with three arguments, the exception details (``type, value, " +"traceback``, the same values returned by :func:`sys.exc_info`, which can " +"also be ``None`` if no exception occurred). The method's return value " +"controls whether an exception is re-raised: any false value re-raises the " +"exception, and ``True`` will result in suppressing it. You'll only rarely " +"want to suppress the exception, because if you do the author of the code " +"containing the ':keyword:`with`' statement will never realize anything went " +"wrong." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:433 +msgid "" +"The :mod:`contextlib` module provides some functions and a decorator that " +"are useful when writing objects for use with the ':keyword:`with`' statement." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:445 +msgid "" +"Using this decorator, our database example from the previous section could " +"be written as::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:474 +msgid "" +"Finally, the :func:`closing` function returns its argument so that it can be " +"bound to a variable, and calls the argument's ``.close()`` method at the end " +"of the block. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:501 +msgid "PEP 366: Explicit Relative Imports From a Main Module" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:503 +msgid "" +"Python's :option:`-m` switch allows running a module as a script. When you " +"ran a module that was located inside a package, relative imports didn't work " +"correctly." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:507 +msgid "" +"The fix for Python 2.6 adds a :attr:`__package__` attribute to modules. " +"When this attribute is present, relative imports will be relative to the " +"value of this attribute instead of the :attr:`__name__` attribute." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:512 +msgid "" +"PEP 302-style importers can then set :attr:`__package__` as necessary. The :" +"mod:`runpy` module that implements the :option:`-m` switch now does this, so " +"relative imports will now work correctly in scripts running from inside a " +"package." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:522 +msgid "PEP 370: Per-user ``site-packages`` Directory" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:524 +msgid "" +"When you run Python, the module search path ``sys.path`` usually includes a " +"directory whose path ends in ``\"site-packages\"``. This directory is " +"intended to hold locally-installed packages available to all users using a " +"machine or a particular site installation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:529 +msgid "" +"Python 2.6 introduces a convention for user-specific site directories. The " +"directory varies depending on the platform:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:532 +msgid "Unix and Mac OS X: :file:`~/.local/`" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:533 +msgid "Windows: :file:`%APPDATA%/Python`" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:535 +msgid "" +"Within this directory, there will be version-specific subdirectories, such " +"as :file:`lib/python2.6/site-packages` on Unix/Mac OS and :file:`Python26/" +"site-packages` on Windows." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:539 +msgid "" +"If you don't like the default directory, it can be overridden by an " +"environment variable. :envvar:`PYTHONUSERBASE` sets the root directory used " +"for all Python versions supporting this feature. On Windows, the directory " +"for application-specific data can be changed by setting the :envvar:" +"`APPDATA` environment variable. You can also modify the :file:`site.py` " +"file for your Python installation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:546 +msgid "" +"The feature can be disabled entirely by running Python with the :option:`-s` " +"option or setting the :envvar:`PYTHONNOUSERSITE` environment variable." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:552 +msgid ":pep:`370` - Per-user ``site-packages`` Directory" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:553 +msgid "PEP written and implemented by Christian Heimes." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:561 +msgid "PEP 371: The ``multiprocessing`` Package" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:563 +msgid "" +"The new :mod:`multiprocessing` package lets Python programs create new " +"processes that will perform a computation and return a result to the " +"parent. The parent and child processes can communicate using queues and " +"pipes, synchronize their operations using locks and semaphores, and can " +"share simple arrays of data." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:569 +msgid "" +"The :mod:`multiprocessing` module started out as an exact emulation of the :" +"mod:`threading` module using processes instead of threads. That goal was " +"discarded along the path to Python 2.6, but the general approach of the " +"module is still similar. The fundamental class is the :class:`Process`, " +"which is passed a callable object and a collection of arguments. The :meth:" +"`start` method sets the callable running in a subprocess, after which you " +"can call the :meth:`is_alive` method to check whether the subprocess is " +"still running and the :meth:`join` method to wait for the process to exit." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:579 +msgid "" +"Here's a simple example where the subprocess will calculate a factorial. " +"The function doing the calculation is written strangely so that it takes " +"significantly longer when the input argument is a multiple of 4." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:616 +msgid "" +"A :class:`Queue` is used to communicate the result of the factorial. The :" +"class:`Queue` object is stored in a global variable. The child process will " +"use the value of the variable when the child was created; because it's a :" +"class:`Queue`, parent and child can use the object to communicate. (If the " +"parent were to change the value of the global variable, the child's value " +"would be unaffected, and vice versa.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:624 +msgid "" +"Two other classes, :class:`Pool` and :class:`Manager`, provide higher-level " +"interfaces. :class:`Pool` will create a fixed number of worker processes, " +"and requests can then be distributed to the workers by calling :meth:`apply` " +"or :meth:`apply_async` to add a single request, and :meth:`map` or :meth:" +"`map_async` to add a number of requests. The following code uses a :class:" +"`Pool` to spread requests across 5 worker processes and retrieve a list of " +"results::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:651 +msgid "" +"The other high-level interface, the :class:`Manager` class, creates a " +"separate server process that can hold master copies of Python data " +"structures. Other processes can then access and modify these data " +"structures using proxy objects. The following example creates a shared " +"dictionary by calling the :meth:`dict` method; the worker processes then " +"insert values into the dictionary. (Locking is not done for you " +"automatically, which doesn't matter in this example. :class:`Manager`'s " +"methods also include :meth:`Lock`, :meth:`RLock`, and :meth:`Semaphore` to " +"create shared locks.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:695 +msgid "This will produce the output::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:706 +msgid "The documentation for the :mod:`multiprocessing` module." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:709 +msgid ":pep:`371` - Addition of the multiprocessing package" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:709 +msgid "" +"PEP written by Jesse Noller and Richard Oudkerk; implemented by Richard " +"Oudkerk and Jesse Noller." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:718 +msgid "PEP 3101: Advanced String Formatting" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:720 +msgid "" +"In Python 3.0, the `%` operator is supplemented by a more powerful string " +"formatting method, :meth:`format`. Support for the :meth:`str.format` " +"method has been backported to Python 2.6." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:724 +msgid "" +"In 2.6, both 8-bit and Unicode strings have a `.format()` method that treats " +"the string as a template and takes the arguments to be formatted. The " +"formatting template uses curly brackets (`{`, `}`) as special characters::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:737 +msgid "Curly brackets can be escaped by doubling them::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:742 +msgid "" +"Field names can be integers indicating positional arguments, such as ``{0}" +"``, ``{1}``, etc. or names of keyword arguments. You can also supply " +"compound field names that read attributes or access dictionary keys::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:756 +msgid "" +"Note that when using dictionary-style notation such as ``[.mp4]``, you don't " +"need to put any quotation marks around the string; it will look up the value " +"using ``.mp4`` as the key. Strings beginning with a number will be " +"converted to an integer. You can't write more complicated expressions " +"inside a format string." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:762 +msgid "" +"So far we've shown how to specify which field to substitute into the " +"resulting string. The precise formatting used is also controllable by " +"adding a colon followed by a format specifier. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:776 +msgid "Format specifiers can reference other fields through nesting::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:786 +msgid "The alignment of a field within the desired width can be specified:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:789 +msgid "Character" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:789 +msgid "Effect" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:791 +msgid "< (default)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:791 +msgid "Left-align" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:792 +msgid ">" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:792 +msgid "Right-align" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:793 +msgid "^" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:793 +msgid "Center" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:794 +msgid "=" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:794 +msgid "(For numeric types only) Pad after the sign." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:797 +msgid "" +"Format specifiers can also include a presentation type, which controls how " +"the value is formatted. For example, floating-point numbers can be " +"formatted as a general number or in exponential notation::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:806 +msgid "" +"A variety of presentation types are available. Consult the 2.6 " +"documentation for a :ref:`complete list `; here's a sample:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:810 +msgid "``b``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:810 +msgid "Binary. Outputs the number in base 2." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:811 +msgid "``c``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:811 +msgid "" +"Character. Converts the integer to the corresponding Unicode character " +"before printing." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:813 +msgid "``d``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:813 +msgid "Decimal Integer. Outputs the number in base 10." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:814 +msgid "``o``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:814 +msgid "Octal format. Outputs the number in base 8." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:815 +msgid "``x``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:815 +msgid "" +"Hex format. Outputs the number in base 16, using lower-case letters for the " +"digits above 9." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:817 +msgid "``e``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:817 +msgid "" +"Exponent notation. Prints the number in scientific notation using the letter " +"'e' to indicate the exponent." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:819 +msgid "``g``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:819 +msgid "" +"General format. This prints the number as a fixed-point number, unless the " +"number is too large, in which case it switches to 'e' exponent notation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:822 +msgid "``n``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:822 +msgid "" +"Number. This is the same as 'g' (for floats) or 'd' (for integers), except " +"that it uses the current locale setting to insert the appropriate number " +"separator characters." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:825 +msgid "``%``" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:825 +msgid "" +"Percentage. Multiplies the number by 100 and displays in fixed ('f') format, " +"followed by a percent sign." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:829 +msgid "" +"Classes and types can define a :meth:`__format__` method to control how " +"they're formatted. It receives a single argument, the format specifier::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:838 +msgid "" +"There's also a :func:`format` builtin that will format a single value. It " +"calls the type's :meth:`__format__` method with the provided specifier::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:849 +msgid ":ref:`formatstrings`" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:849 +msgid "The reference documentation for format fields." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:851 +msgid ":pep:`3101` - Advanced String Formatting" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:852 +msgid "PEP written by Talin. Implemented by Eric Smith." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:859 +msgid "PEP 3105: ``print`` As a Function" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:861 +msgid "" +"The ``print`` statement becomes the :func:`print` function in Python 3.0. " +"Making :func:`print` a function makes it possible to replace the function by " +"doing ``def print(...)`` or importing a new function from somewhere else." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:865 +msgid "" +"Python 2.6 has a ``__future__`` import that removes ``print`` as language " +"syntax, letting you use the functional form instead. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:871 +msgid "The signature of the new function is::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:876 +msgid "The parameters are:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:878 +msgid "*args*: positional arguments whose values will be printed out." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:879 +msgid "*sep*: the separator, which will be printed between arguments." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:880 +msgid "" +"*end*: the ending text, which will be printed after all of the arguments " +"have been output." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:882 +msgid "*file*: the file object to which the output will be sent." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:886 +msgid ":pep:`3105` - Make print a function" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:887 +msgid "PEP written by Georg Brandl." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:894 +msgid "PEP 3110: Exception-Handling Changes" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:896 +msgid "" +"One error that Python programmers occasionally make is writing the following " +"code::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:904 +msgid "" +"The author is probably trying to catch both :exc:`TypeError` and :exc:" +"`ValueError` exceptions, but this code actually does something different: it " +"will catch :exc:`TypeError` and bind the resulting exception object to the " +"local name ``\"ValueError\"``. The :exc:`ValueError` exception will not be " +"caught at all. The correct code specifies a tuple of exceptions::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:916 +msgid "" +"This error happens because the use of the comma here is ambiguous: does it " +"indicate two different nodes in the parse tree, or a single node that's a " +"tuple?" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:920 +msgid "" +"Python 3.0 makes this unambiguous by replacing the comma with the word \"as" +"\". To catch an exception and store the exception object in the variable " +"``exc``, you must write::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:929 +msgid "" +"Python 3.0 will only support the use of \"as\", and therefore interprets the " +"first example as catching two different exceptions. Python 2.6 supports " +"both the comma and \"as\", so existing code will continue to work. We " +"therefore suggest using \"as\" when writing new Python code that will only " +"be executed with 2.6." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:937 +msgid ":pep:`3110` - Catching Exceptions in Python 3000" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:938 +msgid "PEP written and implemented by Collin Winter." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:945 +msgid "PEP 3112: Byte Literals" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:947 +msgid "" +"Python 3.0 adopts Unicode as the language's fundamental string type and " +"denotes 8-bit literals differently, either as ``b'string'`` or using a :" +"class:`bytes` constructor. For future compatibility, Python 2.6 adds :class:" +"`bytes` as a synonym for the :class:`str` type, and it also supports the " +"``b''`` notation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:954 +msgid "" +"The 2.6 :class:`str` differs from 3.0's :class:`bytes` type in various ways; " +"most notably, the constructor is completely different. In 3.0, ``bytes([65, " +"66, 67])`` is 3 elements long, containing the bytes representing ``ABC``; in " +"2.6, ``bytes([65, 66, 67])`` returns the 12-byte string representing the :" +"func:`str` of the list." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:960 +msgid "" +"The primary use of :class:`bytes` in 2.6 will be to write tests of object " +"type such as ``isinstance(x, bytes)``. This will help the 2to3 converter, " +"which can't tell whether 2.x code intends strings to contain either " +"characters or 8-bit bytes; you can now use either :class:`bytes` or :class:" +"`str` to represent your intention exactly, and the resulting code will also " +"be correct in Python 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:967 +msgid "" +"There's also a ``__future__`` import that causes all string literals to " +"become Unicode strings. This means that ``\\u`` escape sequences can be " +"used to include Unicode characters::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:979 +msgid "" +"At the C level, Python 3.0 will rename the existing 8-bit string type, " +"called :c:type:`PyStringObject` in Python 2.x, to :c:type:`PyBytesObject`. " +"Python 2.6 uses ``#define`` to support using the names :c:func:" +"`PyBytesObject`, :c:func:`PyBytes_Check`, :c:func:" +"`PyBytes_FromStringAndSize`, and all the other functions and macros used " +"with strings." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:986 +msgid "" +"Instances of the :class:`bytes` type are immutable just as strings are. A " +"new :class:`bytearray` type stores a mutable sequence of bytes::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1001 +msgid "" +"Byte arrays support most of the methods of string types, such as :meth:" +"`startswith`/:meth:`endswith`, :meth:`find`/:meth:`rfind`, and some of the " +"methods of lists, such as :meth:`append`, :meth:`pop`, and :meth:`reverse`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1014 +msgid "" +"There's also a corresponding C API, with :c:func:`PyByteArray_FromObject`, :" +"c:func:`PyByteArray_FromStringAndSize`, and various other functions." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1021 +msgid ":pep:`3112` - Bytes literals in Python 3000" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1022 +msgid "PEP written by Jason Orendorff; backported to 2.6 by Christian Heimes." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1029 +msgid "PEP 3116: New I/O Library" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1031 +msgid "" +"Python's built-in file objects support a number of methods, but file-like " +"objects don't necessarily support all of them. Objects that imitate files " +"usually support :meth:`read` and :meth:`write`, but they may not support :" +"meth:`readline`, for example. Python 3.0 introduces a layered I/O library " +"in the :mod:`io` module that separates buffering and text-handling features " +"from the fundamental read and write operations." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1039 +msgid "" +"There are three levels of abstract base classes provided by the :mod:`io` " +"module:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1042 +msgid "" +":class:`RawIOBase` defines raw I/O operations: :meth:`read`, :meth:" +"`readinto`, :meth:`write`, :meth:`seek`, :meth:`tell`, :meth:`truncate`, " +"and :meth:`close`. Most of the methods of this class will often map to a " +"single system call. There are also :meth:`readable`, :meth:`writable`, and :" +"meth:`seekable` methods for determining what operations a given object will " +"allow." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1050 +msgid "" +"Python 3.0 has concrete implementations of this class for files and sockets, " +"but Python 2.6 hasn't restructured its file and socket objects in this way." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1056 +msgid "" +":class:`BufferedIOBase` is an abstract base class that buffers data in " +"memory to reduce the number of system calls used, making I/O processing more " +"efficient. It supports all of the methods of :class:`RawIOBase`, and adds a :" +"attr:`raw` attribute holding the underlying raw object." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1062 +msgid "" +"There are five concrete classes implementing this ABC. :class:" +"`BufferedWriter` and :class:`BufferedReader` are for objects that support " +"write-only or read-only usage that have a :meth:`seek` method for random " +"access. :class:`BufferedRandom` objects support read and write access upon " +"the same underlying stream, and :class:`BufferedRWPair` is for objects such " +"as TTYs that have both read and write operations acting upon unconnected " +"streams of data. The :class:`BytesIO` class supports reading, writing, and " +"seeking over an in-memory buffer." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1075 +msgid "" +":class:`TextIOBase`: Provides functions for reading and writing strings " +"(remember, strings will be Unicode in Python 3.0), and supporting :term:" +"`universal newlines`. :class:`TextIOBase` defines the :meth:`readline` " +"method and supports iteration upon objects." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1081 +msgid "" +"There are two concrete implementations. :class:`TextIOWrapper` wraps a " +"buffered I/O object, supporting all of the methods for text I/O and adding " +"a :attr:`buffer` attribute for access to the underlying object. :class:" +"`StringIO` simply buffers everything in memory without ever writing anything " +"to disk." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1087 +msgid "" +"(In Python 2.6, :class:`io.StringIO` is implemented in pure Python, so it's " +"pretty slow. You should therefore stick with the existing :mod:`StringIO` " +"module or :mod:`cStringIO` for now. At some point Python 3.0's :mod:`io` " +"module will be rewritten into C for speed, and perhaps the C implementation " +"will be backported to the 2.x releases.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1093 +msgid "" +"In Python 2.6, the underlying implementations haven't been restructured to " +"build on top of the :mod:`io` module's classes. The module is being " +"provided to make it easier to write code that's forward-compatible with 3.0, " +"and to save developers the effort of writing their own implementations of " +"buffering and text I/O." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1103 +msgid ":pep:`3116` - New I/O" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1102 +msgid "" +"PEP written by Daniel Stutzbach, Mike Verdone, and Guido van Rossum. Code by " +"Guido van Rossum, Georg Brandl, Walter Doerwald, Jeremy Hylton, Martin von " +"Löwis, Tony Lownds, and others." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1111 +msgid "PEP 3118: Revised Buffer Protocol" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1113 +msgid "" +"The buffer protocol is a C-level API that lets Python types exchange " +"pointers into their internal representations. A memory-mapped file can be " +"viewed as a buffer of characters, for example, and this lets another module " +"such as :mod:`re` treat memory-mapped files as a string of characters to be " +"searched." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1119 +msgid "" +"The primary users of the buffer protocol are numeric-processing packages " +"such as NumPy, which expose the internal representation of arrays so that " +"callers can write data directly into an array instead of going through a " +"slower API. This PEP updates the buffer protocol in light of experience " +"from NumPy development, adding a number of new features such as indicating " +"the shape of an array or locking a memory region." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1126 +msgid "" +"The most important new C API function is ``PyObject_GetBuffer(PyObject *obj, " +"Py_buffer *view, int flags)``, which takes an object and a set of flags, and " +"fills in the ``Py_buffer`` structure with information about the object's " +"memory representation. Objects can use this operation to lock memory in " +"place while an external caller could be modifying the contents, so there's a " +"corresponding ``PyBuffer_Release(Py_buffer *view)`` to indicate that the " +"external caller is done." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1138 +msgid "" +"The *flags* argument to :c:func:`PyObject_GetBuffer` specifies constraints " +"upon the memory returned. Some examples are:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1141 +msgid ":const:`PyBUF_WRITABLE` indicates that the memory must be writable." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1143 +msgid "" +":const:`PyBUF_LOCK` requests a read-only or exclusive lock on the memory." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1145 +msgid "" +":const:`PyBUF_C_CONTIGUOUS` and :const:`PyBUF_F_CONTIGUOUS` requests a C-" +"contiguous (last dimension varies the fastest) or Fortran-contiguous (first " +"dimension varies the fastest) array layout." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1149 +msgid "" +"Two new argument codes for :c:func:`PyArg_ParseTuple`, ``s*`` and ``z*``, " +"return locked buffer objects for a parameter." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1155 +msgid ":pep:`3118` - Revising the buffer protocol" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1155 +msgid "" +"PEP written by Travis Oliphant and Carl Banks; implemented by Travis " +"Oliphant." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1164 +msgid "PEP 3119: Abstract Base Classes" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1166 +msgid "" +"Some object-oriented languages such as Java support interfaces, declaring " +"that a class has a given set of methods or supports a given access " +"protocol. Abstract Base Classes (or ABCs) are an equivalent feature for " +"Python. The ABC support consists of an :mod:`abc` module containing a " +"metaclass called :class:`ABCMeta`, special handling of this metaclass by " +"the :func:`isinstance` and :func:`issubclass` builtins, and a collection of " +"basic ABCs that the Python developers think will be widely useful. Future " +"versions of Python will probably add more ABCs." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1176 +msgid "" +"Let's say you have a particular class and wish to know whether it supports " +"dictionary-style access. The phrase \"dictionary-style\" is vague, however. " +"It probably means that accessing items with ``obj[1]`` works. Does it imply " +"that setting items with ``obj[2] = value`` works? Or that the object will " +"have :meth:`keys`, :meth:`values`, and :meth:`items` methods? What about " +"the iterative variants such as :meth:`iterkeys`? :meth:`copy` and :meth:" +"`update`? Iterating over the object with :func:`iter`?" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1184 +msgid "" +"The Python 2.6 :mod:`collections` module includes a number of different ABCs " +"that represent these distinctions. :class:`Iterable` indicates that a class " +"defines :meth:`__iter__`, and :class:`Container` means the class defines a :" +"meth:`__contains__` method and therefore supports ``x in y`` expressions. " +"The basic dictionary interface of getting items, setting items, and :meth:" +"`keys`, :meth:`values`, and :meth:`items`, is defined by the :class:" +"`MutableMapping` ABC." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1193 +msgid "" +"You can derive your own classes from a particular ABC to indicate they " +"support that ABC's interface::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1202 +msgid "" +"Alternatively, you could write the class without deriving from the desired " +"ABC and instead register the class by calling the ABC's :meth:`register` " +"method::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1213 +msgid "" +"For classes that you write, deriving from the ABC is probably clearer. The :" +"meth:`register` method is useful when you've written a new ABC that can " +"describe an existing type or class, or if you want to declare that some " +"third-party class implements an ABC. For example, if you defined a :class:" +"`PrintableType` ABC, it's legal to do::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1225 +msgid "" +"Classes should obey the semantics specified by an ABC, but Python can't " +"check this; it's up to the class author to understand the ABC's requirements " +"and to implement the code accordingly." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1229 +msgid "" +"To check whether an object supports a particular interface, you can now " +"write::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1236 +msgid "" +"Don't feel that you must now begin writing lots of checks as in the above " +"example. Python has a strong tradition of duck-typing, where explicit type-" +"checking is never done and code simply calls methods on an object, trusting " +"that those methods will be there and raising an exception if they aren't. " +"Be judicious in checking for ABCs and only do it where it's absolutely " +"necessary." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1243 +msgid "" +"You can write your own ABCs by using ``abc.ABCMeta`` as the metaclass in a " +"class definition::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1264 +msgid "" +"In the :class:`Drawable` ABC above, the :meth:`draw_doubled` method renders " +"the object at twice its size and can be implemented in terms of other " +"methods described in :class:`Drawable`. Classes implementing this ABC " +"therefore don't need to provide their own implementation of :meth:" +"`draw_doubled`, though they can do so. An implementation of :meth:`draw` is " +"necessary, though; the ABC can't provide a useful generic implementation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1272 +msgid "" +"You can apply the ``@abstractmethod`` decorator to methods such as :meth:" +"`draw` that must be implemented; Python will then raise an exception for " +"classes that don't define the method. Note that the exception is only raised " +"when you actually try to create an instance of a subclass lacking the " +"method::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1287 +msgid "" +"Abstract data attributes can be declared using the ``@abstractproperty`` " +"decorator::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1297 +msgid "Subclasses must then define a :meth:`readonly` property." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1303 +msgid ":pep:`3119` - Introducing Abstract Base Classes" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1302 +msgid "" +"PEP written by Guido van Rossum and Talin. Implemented by Guido van Rossum. " +"Backported to 2.6 by Benjamin Aranguren, with Alex Martelli." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1311 +msgid "PEP 3127: Integer Literal Support and Syntax" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1313 +msgid "" +"Python 3.0 changes the syntax for octal (base-8) integer literals, prefixing " +"them with \"0o\" or \"0O\" instead of a leading zero, and adds support for " +"binary (base-2) integer literals, signalled by a \"0b\" or \"0B\" prefix." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1318 +msgid "" +"Python 2.6 doesn't drop support for a leading 0 signalling an octal number, " +"but it does add support for \"0o\" and \"0b\"::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1326 +msgid "" +"The :func:`oct` builtin still returns numbers prefixed with a leading zero, " +"and a new :func:`bin` builtin returns the binary representation for a " +"number::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1337 +msgid "" +"The :func:`int` and :func:`long` builtins will now accept the \"0o\" and \"0b" +"\" prefixes when base-8 or base-2 are requested, or when the *base* argument " +"is zero (signalling that the base used should be determined from the " +"string)::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1355 +msgid ":pep:`3127` - Integer Literal Support and Syntax" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1355 +msgid "PEP written by Patrick Maupin; backported to 2.6 by Eric Smith." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1363 +msgid "PEP 3129: Class Decorators" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1365 +msgid "" +"Decorators have been extended from functions to classes. It's now legal to " +"write::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1373 +msgid "This is equivalent to::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1382 +msgid ":pep:`3129` - Class Decorators" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1383 +msgid "PEP written by Collin Winter." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1390 +msgid "PEP 3141: A Type Hierarchy for Numbers" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1392 +msgid "" +"Python 3.0 adds several abstract base classes for numeric types inspired by " +"Scheme's numeric tower. These classes were backported to 2.6 as the :mod:" +"`numbers` module." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1396 +msgid "" +"The most general ABC is :class:`Number`. It defines no operations at all, " +"and only exists to allow checking if an object is a number by doing " +"``isinstance(obj, Number)``." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1400 +msgid "" +":class:`Complex` is a subclass of :class:`Number`. Complex numbers can " +"undergo the basic operations of addition, subtraction, multiplication, " +"division, and exponentiation, and you can retrieve the real and imaginary " +"parts and obtain a number's conjugate. Python's built-in complex type is an " +"implementation of :class:`Complex`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1406 +msgid "" +":class:`Real` further derives from :class:`Complex`, and adds operations " +"that only work on real numbers: :func:`floor`, :func:`trunc`, rounding, " +"taking the remainder mod N, floor division, and comparisons." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1411 +msgid "" +":class:`Rational` numbers derive from :class:`Real`, have :attr:`numerator` " +"and :attr:`denominator` properties, and can be converted to floats. Python " +"2.6 adds a simple rational-number class, :class:`Fraction`, in the :mod:" +"`fractions` module. (It's called :class:`Fraction` instead of :class:" +"`Rational` to avoid a name clash with :class:`numbers.Rational`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1418 +msgid "" +":class:`Integral` numbers derive from :class:`Rational`, and can be shifted " +"left and right with ``<<`` and ``>>``, combined using bitwise operations " +"such as ``&`` and ``|``, and can be used as array indexes and slice " +"boundaries." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1423 +msgid "" +"In Python 3.0, the PEP slightly redefines the existing builtins :func:" +"`round`, :func:`math.floor`, :func:`math.ceil`, and adds a new one, :func:" +"`math.trunc`, that's been backported to Python 2.6. :func:`math.trunc` " +"rounds toward zero, returning the closest :class:`Integral` that's between " +"the function's argument and zero." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1432 +msgid ":pep:`3141` - A Type Hierarchy for Numbers" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1432 +msgid "PEP written by Jeffrey Yasskin." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1434 +msgid "" +"`Scheme's numerical tower `__, from the Guile manual." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1436 +msgid "" +"`Scheme's number datatypes `__ from the R5RS Scheme specification." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1440 +msgid "The :mod:`fractions` Module" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1442 +msgid "" +"To fill out the hierarchy of numeric types, the :mod:`fractions` module " +"provides a rational-number class. Rational numbers store their values as a " +"numerator and denominator forming a fraction, and can exactly represent " +"numbers such as ``2/3`` that floating-point numbers can only approximate." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1448 +msgid "" +"The :class:`Fraction` constructor takes two :class:`Integral` values that " +"will be the numerator and denominator of the resulting fraction. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1461 +msgid "" +"For converting floating-point numbers to rationals, the float type now has " +"an :meth:`as_integer_ratio()` method that returns the numerator and " +"denominator for a fraction that evaluates to the same floating-point value::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1473 +msgid "" +"Note that values that can only be approximated by floating-point numbers, " +"such as 1./3, are not simplified to the number being approximated; the " +"fraction attempts to match the floating-point value **exactly**." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1478 +msgid "" +"The :mod:`fractions` module is based upon an implementation by Sjoerd " +"Mullender that was in Python's :file:`Demo/classes/` directory for a long " +"time. This implementation was significantly updated by Jeffrey Yasskin." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1487 ../Doc/whatsnew/2.7.rst:674 +#: ../Doc/whatsnew/3.1.rst:118 ../Doc/whatsnew/3.2.rst:435 +#: ../Doc/whatsnew/3.3.rst:778 ../Doc/whatsnew/3.4.rst:403 +#: ../Doc/whatsnew/3.5.rst:703 ../Doc/whatsnew/3.6.rst:547 +msgid "Some smaller changes made to the core Python language are:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1489 +msgid "" +"Directories and zip archives containing a :file:`__main__.py` file can now " +"be executed directly by passing their name to the interpreter. The directory " +"or zip archive is automatically inserted as the first entry in sys.path. " +"(Suggestion and initial patch by Andy Chu, subsequently revised by Phillip " +"J. Eby and Nick Coghlan; :issue:`1739468`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1496 +msgid "" +"The :func:`hasattr` function was catching and ignoring all errors, under the " +"assumption that they meant a :meth:`__getattr__` method was failing somehow " +"and the return value of :func:`hasattr` would therefore be ``False``. This " +"logic shouldn't be applied to :exc:`KeyboardInterrupt` and :exc:" +"`SystemExit`, however; Python 2.6 will no longer discard such exceptions " +"when :func:`hasattr` encounters them. (Fixed by Benjamin Peterson; :issue:" +"`2196`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1504 +msgid "" +"When calling a function using the ``**`` syntax to provide keyword " +"arguments, you are no longer required to use a Python dictionary; any " +"mapping will now work::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1517 +msgid "(Contributed by Alexander Belopolsky; :issue:`1686487`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1519 +msgid "" +"It's also become legal to provide keyword arguments after a ``*args`` " +"argument to a function call. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1528 +msgid "" +"Previously this would have been a syntax error. (Contributed by Amaury " +"Forgeot d'Arc; :issue:`3473`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1531 +msgid "" +"A new builtin, ``next(iterator, [default])`` returns the next item from the " +"specified iterator. If the *default* argument is supplied, it will be " +"returned if *iterator* has been exhausted; otherwise, the :exc:" +"`StopIteration` exception will be raised. (Backported in :issue:`2719`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1537 +msgid "" +"Tuples now have :meth:`index` and :meth:`count` methods matching the list " +"type's :meth:`index` and :meth:`count` methods::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1546 +msgid "(Contributed by Raymond Hettinger)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1548 +msgid "" +"The built-in types now have improved support for extended slicing syntax, " +"accepting various combinations of ``(start, stop, step)``. Previously, the " +"support was partial and certain corner cases wouldn't work. (Implemented by " +"Thomas Wouters.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1555 +msgid "" +"Properties now have three attributes, :attr:`getter`, :attr:`setter` and :" +"attr:`deleter`, that are decorators providing useful shortcuts for adding a " +"getter, setter or deleter function to an existing property. You would use " +"them like this::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1582 +msgid "" +"Several methods of the built-in set types now accept multiple iterables: :" +"meth:`intersection`, :meth:`intersection_update`, :meth:`union`, :meth:" +"`update`, :meth:`difference` and :meth:`difference_update`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1598 +msgid "" +"Many floating-point features were added. The :func:`float` function will " +"now turn the string ``nan`` into an IEEE 754 Not A Number value, and ``" +"+inf`` and ``-inf`` into positive or negative infinity. This works on any " +"platform with IEEE 754 semantics. (Contributed by Christian Heimes; :issue:" +"`1635`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1604 +msgid "" +"Other functions in the :mod:`math` module, :func:`isinf` and :func:`isnan`, " +"return true if their floating-point argument is infinite or Not A Number. (:" +"issue:`1640`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1608 +msgid "" +"Conversion functions were added to convert floating-point numbers into " +"hexadecimal strings (:issue:`3008`). These functions convert floats to and " +"from a string representation without introducing rounding errors from the " +"conversion between decimal and binary. Floats have a :meth:`hex` method " +"that returns a string representation, and the ``float.fromhex()`` method " +"converts a string back into a number::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1625 +msgid "" +"A numerical nicety: when creating a complex number from two floats on " +"systems that support signed zeros (-0 and +0), the :func:`complex` " +"constructor will now preserve the sign of the zero. (Fixed by Mark T. " +"Dickinson; :issue:`1507`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1630 +msgid "" +"Classes that inherit a :meth:`__hash__` method from a parent class can set " +"``__hash__ = None`` to indicate that the class isn't hashable. This will " +"make ``hash(obj)`` raise a :exc:`TypeError` and the class will not be " +"indicated as implementing the :class:`Hashable` ABC." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1636 +msgid "" +"You should do this when you've defined a :meth:`__cmp__` or :meth:`__eq__` " +"method that compares objects by their value rather than by identity. All " +"objects have a default hash method that uses ``id(obj)`` as the hash value. " +"There's no tidy way to remove the :meth:`__hash__` method inherited from a " +"parent class, so assigning ``None`` was implemented as an override. At the " +"C level, extensions can set ``tp_hash`` to :c:func:" +"`PyObject_HashNotImplemented`. (Fixed by Nick Coghlan and Amaury Forgeot " +"d'Arc; :issue:`2235`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1646 +msgid "" +"The :exc:`GeneratorExit` exception now subclasses :exc:`BaseException` " +"instead of :exc:`Exception`. This means that an exception handler that does " +"``except Exception:`` will not inadvertently catch :exc:`GeneratorExit`. " +"(Contributed by Chad Austin; :issue:`1537`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1652 +msgid "" +"Generator objects now have a :attr:`gi_code` attribute that refers to the " +"original code object backing the generator. (Contributed by Collin Winter; :" +"issue:`1473257`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1656 +msgid "" +"The :func:`compile` built-in function now accepts keyword arguments as well " +"as positional parameters. (Contributed by Thomas Wouters; :issue:`1444529`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1660 +msgid "" +"The :func:`complex` constructor now accepts strings containing parenthesized " +"complex numbers, meaning that ``complex(repr(cplx))`` will now round-trip " +"values. For example, ``complex('(3+4j)')`` now returns the value (3+4j). (:" +"issue:`1491866`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1665 +msgid "" +"The string :meth:`translate` method now accepts ``None`` as the translation " +"table parameter, which is treated as the identity transformation. This " +"makes it easier to carry out operations that only delete characters. " +"(Contributed by Bengt Richter and implemented by Raymond Hettinger; :issue:" +"`1193128`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1671 +msgid "" +"The built-in :func:`dir` function now checks for a :meth:`__dir__` method on " +"the objects it receives. This method must return a list of strings " +"containing the names of valid attributes for the object, and lets the object " +"control the value that :func:`dir` produces. Objects that have :meth:" +"`__getattr__` or :meth:`__getattribute__` methods can use this to advertise " +"pseudo-attributes they will honor. (:issue:`1591665`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1679 +msgid "" +"Instance method objects have new attributes for the object and function " +"comprising the method; the new synonym for :attr:`im_self` is :attr:" +"`__self__`, and :attr:`im_func` is also available as :attr:`__func__`. The " +"old names are still supported in Python 2.6, but are gone in 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1684 +msgid "" +"An obscure change: when you use the :func:`locals` function inside a :" +"keyword:`class` statement, the resulting dictionary no longer returns free " +"variables. (Free variables, in this case, are variables referenced in the :" +"keyword:`class` statement that aren't attributes of the class.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1695 +msgid "" +"The :mod:`warnings` module has been rewritten in C. This makes it possible " +"to invoke warnings from the parser, and may also make the interpreter's " +"startup faster. (Contributed by Neal Norwitz and Brett Cannon; :issue:" +"`1631171`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1700 +msgid "" +"Type objects now have a cache of methods that can reduce the work required " +"to find the correct method implementation for a particular class; once " +"cached, the interpreter doesn't need to traverse base classes to figure out " +"the right method to call. The cache is cleared if a base class or the class " +"itself is modified, so the cache should remain correct even in the face of " +"Python's dynamic nature. (Original optimization implemented by Armin Rigo, " +"updated for Python 2.6 by Kevin Jacobs; :issue:`1700288`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1710 +msgid "" +"By default, this change is only applied to types that are included with the " +"Python core. Extension modules may not necessarily be compatible with this " +"cache, so they must explicitly add :c:macro:`Py_TPFLAGS_HAVE_VERSION_TAG` to " +"the module's ``tp_flags`` field to enable the method cache. (To be " +"compatible with the method cache, the extension module's code must not " +"directly access and modify the ``tp_dict`` member of any of the types it " +"implements. Most modules don't do this, but it's impossible for the Python " +"interpreter to determine that. See :issue:`1878` for some discussion.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1721 +msgid "" +"Function calls that use keyword arguments are significantly faster by doing " +"a quick pointer comparison, usually saving the time of a full string " +"comparison. (Contributed by Raymond Hettinger, after an initial " +"implementation by Antoine Pitrou; :issue:`1819`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1726 +msgid "" +"All of the functions in the :mod:`struct` module have been rewritten in C, " +"thanks to work at the Need For Speed sprint. (Contributed by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1730 +msgid "" +"Some of the standard built-in types now set a bit in their type objects. " +"This speeds up checking whether an object is a subclass of one of these " +"types. (Contributed by Neal Norwitz.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1734 +msgid "" +"Unicode strings now use faster code for detecting whitespace and line " +"breaks; this speeds up the :meth:`split` method by about 25% and :meth:" +"`splitlines` by 35%. (Contributed by Antoine Pitrou.) Memory usage is " +"reduced by using pymalloc for the Unicode string's data." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1740 +msgid "" +"The ``with`` statement now stores the :meth:`__exit__` method on the stack, " +"producing a small speedup. (Implemented by Jeffrey Yasskin.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1743 +msgid "" +"To reduce memory usage, the garbage collector will now clear internal free " +"lists when garbage-collecting the highest generation of objects. This may " +"return memory to the operating system sooner." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1752 ../Doc/whatsnew/2.7.rst:907 +msgid "Interpreter Changes" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1754 +msgid "" +"Two command-line options have been reserved for use by other Python " +"implementations. The :option:`-J` switch has been reserved for use by " +"Jython for Jython-specific options, such as switches that are passed to the " +"underlying JVM. :option:`-X` has been reserved for options specific to a " +"particular implementation of Python such as CPython, Jython, or IronPython. " +"If either option is used with Python 2.6, the interpreter will report that " +"the option isn't currently used." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1762 +msgid "" +"Python can now be prevented from writing :file:`.pyc` or :file:`.pyo` files " +"by supplying the :option:`-B` switch to the Python interpreter, or by " +"setting the :envvar:`PYTHONDONTWRITEBYTECODE` environment variable before " +"running the interpreter. This setting is available to Python programs as " +"the ``sys.dont_write_bytecode`` variable, and Python code can change the " +"value to modify the interpreter's behaviour. (Contributed by Neal Norwitz " +"and Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1770 +msgid "" +"The encoding used for standard input, output, and standard error can be " +"specified by setting the :envvar:`PYTHONIOENCODING` environment variable " +"before running the interpreter. The value should be a string in the form " +"```` or ``:``. The *encoding* part " +"specifies the encoding's name, e.g. ``utf-8`` or ``latin-1``; the optional " +"*errorhandler* part specifies what to do with characters that can't be " +"handled by the encoding, and should be one of \"error\", \"ignore\", or " +"\"replace\". (Contributed by Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1785 ../Doc/whatsnew/2.7.rst:1027 +msgid "" +"As in every release, Python's standard library received a number of " +"enhancements and bug fixes. Here's a partial list of the most notable " +"changes, sorted alphabetically by module name. Consult the :file:`Misc/NEWS` " +"file in the source tree for a more complete list of changes, or look through " +"the Subversion logs for all the details." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1791 +msgid "" +"The :mod:`asyncore` and :mod:`asynchat` modules are being actively " +"maintained again, and a number of patches and bugfixes were applied. " +"(Maintained by Josiah Carlson; see :issue:`1736190` for one patch.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1796 +msgid "" +"The :mod:`bsddb` module also has a new maintainer, Jesús Cea Avión, and the " +"package is now available as a standalone package. The web page for the " +"package is `www.jcea.es/programacion/pybsddb.htm `__. The plan is to remove the package from the " +"standard library in Python 3.0, because its pace of releases is much more " +"frequent than Python's." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1804 +msgid "" +"The :mod:`bsddb.dbshelve` module now uses the highest pickling protocol " +"available, instead of restricting itself to protocol 1. (Contributed by W. " +"Barnes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1808 +msgid "" +"The :mod:`cgi` module will now read variables from the query string of an " +"HTTP POST request. This makes it possible to use form actions with URLs " +"that include query strings such as \"/cgi-bin/add.py?category=1\". " +"(Contributed by Alexandre Fiori and Nubis; :issue:`1817`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1814 +msgid "" +"The :func:`parse_qs` and :func:`parse_qsl` functions have been relocated " +"from the :mod:`cgi` module to the :mod:`urlparse` module. The versions still " +"available in the :mod:`cgi` module will trigger :exc:" +"`PendingDeprecationWarning` messages in 2.6 (:issue:`600362`)." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1820 +msgid "" +"The :mod:`cmath` module underwent extensive revision, contributed by Mark " +"Dickinson and Christian Heimes. Five new functions were added:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1824 +msgid "" +":func:`polar` converts a complex number to polar form, returning the modulus " +"and argument of the complex number." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1827 +msgid "" +":func:`rect` does the opposite, turning a modulus, argument pair back into " +"the corresponding complex number." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1830 +msgid "" +":func:`phase` returns the argument (also called the angle) of a complex " +"number." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1833 +msgid "" +":func:`isnan` returns True if either the real or imaginary part of its " +"argument is a NaN." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1836 +msgid "" +":func:`isinf` returns True if either the real or imaginary part of its " +"argument is infinite." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1839 +msgid "" +"The revisions also improved the numerical soundness of the :mod:`cmath` " +"module. For all functions, the real and imaginary parts of the results are " +"accurate to within a few units of least precision (ulps) whenever possible. " +"See :issue:`1381` for the details. The branch cuts for :func:`asinh`, :func:" +"`atanh`: and :func:`atan` have also been corrected." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1846 +msgid "" +"The tests for the module have been greatly expanded; nearly 2000 new test " +"cases exercise the algebraic functions." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1849 +msgid "" +"On IEEE 754 platforms, the :mod:`cmath` module now handles IEEE 754 special " +"values and floating-point exceptions in a manner consistent with Annex 'G' " +"of the C99 standard." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1853 +msgid "" +"A new data type in the :mod:`collections` module: :class:" +"`namedtuple(typename, fieldnames)` is a factory function that creates " +"subclasses of the standard tuple whose fields are accessible by name as well " +"as index. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1875 +msgid "" +"Several places in the standard library that returned tuples have been " +"modified to return :class:`namedtuple` instances. For example, the :meth:" +"`Decimal.as_tuple` method now returns a named tuple with :attr:`sign`, :attr:" +"`digits`, and :attr:`exponent` fields." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1882 +msgid "" +"Another change to the :mod:`collections` module is that the :class:`deque` " +"type now supports an optional *maxlen* parameter; if supplied, the deque's " +"size will be restricted to no more than *maxlen* items. Adding more items " +"to a full deque causes old items to be discarded." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1903 +msgid "" +"The :mod:`Cookie` module's :class:`Morsel` objects now support an :attr:" +"`httponly` attribute. In some browsers. cookies with this attribute set " +"cannot be accessed or manipulated by JavaScript code. (Contributed by Arvin " +"Schnell; :issue:`1638033`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1908 +msgid "" +"A new window method in the :mod:`curses` module, :meth:`chgat`, changes the " +"display attributes for a certain number of characters on a single line. " +"(Contributed by Fabian Kreutz.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1918 +msgid "" +"The :class:`Textbox` class in the :mod:`curses.textpad` module now supports " +"editing in insert mode as well as overwrite mode. Insert mode is enabled by " +"supplying a true value for the *insert_mode* parameter when creating the :" +"class:`Textbox` instance." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1923 +msgid "" +"The :mod:`datetime` module's :meth:`strftime` methods now support a ``%f`` " +"format code that expands to the number of microseconds in the object, zero-" +"padded on the left to six places. (Contributed by Skip Montanaro; :issue:" +"`1158`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1928 +msgid "" +"The :mod:`decimal` module was updated to version 1.66 of `the General " +"Decimal Specification `__. " +"New features include some methods for some basic mathematical functions such " +"as :meth:`exp` and :meth:`log10`::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1940 +msgid "" +"The :meth:`as_tuple` method of :class:`Decimal` objects now returns a named " +"tuple with :attr:`sign`, :attr:`digits`, and :attr:`exponent` fields." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1943 +msgid "" +"(Implemented by Facundo Batista and Mark Dickinson. Named tuple support " +"added by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1946 +msgid "" +"The :mod:`difflib` module's :class:`SequenceMatcher` class now returns named " +"tuples representing matches, with :attr:`a`, :attr:`b`, and :attr:`size` " +"attributes. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1951 +msgid "" +"An optional ``timeout`` parameter, specifying a timeout measured in seconds, " +"was added to the :class:`ftplib.FTP` class constructor as well as the :meth:" +"`connect` method. (Added by Facundo Batista.) Also, the :class:`FTP` " +"class's :meth:`storbinary` and :meth:`storlines` now take an optional " +"*callback* parameter that will be called with each block of data after the " +"data has been sent. (Contributed by Phil Schwartz; :issue:`1221598`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1959 +msgid "" +"The :func:`reduce` built-in function is also available in the :mod:" +"`functools` module. In Python 3.0, the builtin has been dropped and :func:" +"`reduce` is only available from :mod:`functools`; currently there are no " +"plans to drop the builtin in the 2.x series. (Patched by Christian Heimes; :" +"issue:`1739906`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1965 +msgid "" +"When possible, the :mod:`getpass` module will now use :file:`/dev/tty` to " +"print a prompt message and read the password, falling back to standard error " +"and standard input. If the password may be echoed to the terminal, a " +"warning is printed before the prompt is displayed. (Contributed by Gregory " +"P. Smith.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1971 +msgid "" +"The :func:`glob.glob` function can now return Unicode filenames if a Unicode " +"path was used and Unicode filenames are matched within the directory. (:" +"issue:`1001604`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1975 +msgid "" +"A new function in the :mod:`heapq` module, ``merge(iter1, iter2, ...)``, " +"takes any number of iterables returning data in sorted order, and returns a " +"new generator that returns the contents of all the iterators, also in sorted " +"order. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1983 +msgid "" +"Another new function, ``heappushpop(heap, item)``, pushes *item* onto " +"*heap*, then pops off and returns the smallest item. This is more efficient " +"than making a call to :func:`heappush` and then :func:`heappop`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1988 +msgid "" +":mod:`heapq` is now implemented to only use less-than comparison, instead of " +"the less-than-or-equal comparison it previously used. This makes :mod:" +"`heapq`'s usage of a type match the :meth:`list.sort` method. (Contributed " +"by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1994 +msgid "" +"An optional ``timeout`` parameter, specifying a timeout measured in seconds, " +"was added to the :class:`httplib.HTTPConnection` and :class:" +"`HTTPSConnection` class constructors. (Added by Facundo Batista.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:1999 +msgid "" +"Most of the :mod:`inspect` module's functions, such as :func:`getmoduleinfo` " +"and :func:`getargs`, now return named tuples. In addition to behaving like " +"tuples, the elements of the return value can also be accessed as " +"attributes. (Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2005 +msgid "" +"Some new functions in the module include :func:`isgenerator`, :func:" +"`isgeneratorfunction`, and :func:`isabstract`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2009 +msgid "The :mod:`itertools` module gained several new functions." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2011 +msgid "" +"``izip_longest(iter1, iter2, ...[, fillvalue])`` makes tuples from each of " +"the elements; if some of the iterables are shorter than others, the missing " +"values are set to *fillvalue*. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2018 +msgid "" +"``product(iter1, iter2, ..., [repeat=N])`` returns the Cartesian product of " +"the supplied iterables, a set of tuples containing every possible " +"combination of the elements returned from each iterable. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2027 +msgid "" +"The optional *repeat* keyword argument is used for taking the product of an " +"iterable or a set of iterables with themselves, repeated *N* times. With a " +"single iterable argument, *N*-tuples are returned::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2036 +msgid "With two iterables, *2N*-tuples are returned. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2044 +msgid "" +"``combinations(iterable, r)`` returns sub-sequences of length *r* from the " +"elements of *iterable*. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2055 +msgid "" +"``permutations(iter[, r])`` returns all the permutations of length *r* of " +"the iterable's elements. If *r* is not specified, it will default to the " +"number of elements produced by the iterable. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2065 +msgid "" +"``itertools.chain(*iterables)`` is an existing function in :mod:`itertools` " +"that gained a new constructor in Python 2.6. ``itertools.chain." +"from_iterable(iterable)`` takes a single iterable that should return other " +"iterables. :func:`chain` will then return all the elements of the first " +"iterable, then all the elements of the second, and so on. ::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2075 +msgid "(All contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2077 +msgid "" +"The :mod:`logging` module's :class:`FileHandler` class and its subclasses :" +"class:`WatchedFileHandler`, :class:`RotatingFileHandler`, and :class:" +"`TimedRotatingFileHandler` now have an optional *delay* parameter to their " +"constructors. If *delay* is true, opening of the log file is deferred until " +"the first :meth:`emit` call is made. (Contributed by Vinay Sajip.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2084 +msgid "" +":class:`TimedRotatingFileHandler` also has a *utc* constructor parameter. " +"If the argument is true, UTC time will be used in determining when midnight " +"occurs and in generating filenames; otherwise local time will be used." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2089 +msgid "Several new functions were added to the :mod:`math` module:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2091 +msgid "" +":func:`~math.isinf` and :func:`~math.isnan` determine whether a given float " +"is a (positive or negative) infinity or a NaN (Not a Number), respectively." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2094 +msgid "" +":func:`~math.copysign` copies the sign bit of an IEEE 754 number, returning " +"the absolute value of *x* combined with the sign bit of *y*. For example, " +"``math.copysign(1, -0.0)`` returns -1.0. (Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2099 +msgid "" +":func:`~math.factorial` computes the factorial of a number. (Contributed by " +"Raymond Hettinger; :issue:`2138`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2102 +msgid "" +":func:`~math.fsum` adds up the stream of numbers from an iterable, and is " +"careful to avoid loss of precision through using partial sums. (Contributed " +"by Jean Brouwers, Raymond Hettinger, and Mark Dickinson; :issue:`2819`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2107 +msgid "" +":func:`~math.acosh`, :func:`~math.asinh` and :func:`~math.atanh` compute the " +"inverse hyperbolic functions." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2110 +msgid ":func:`~math.log1p` returns the natural logarithm of *1+x* (base *e*)." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2113 +msgid "" +":func:`trunc` rounds a number toward zero, returning the closest :class:" +"`Integral` that's between the function's argument and zero. Added as part of " +"the backport of `PEP 3141's type hierarchy for numbers <#pep-3141>`__." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2118 +msgid "" +"The :mod:`math` module has been improved to give more consistent behaviour " +"across platforms, especially with respect to handling of floating-point " +"exceptions and IEEE 754 special values." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2122 +msgid "" +"Whenever possible, the module follows the recommendations of the C99 " +"standard about 754's special values. For example, ``sqrt(-1.)`` should now " +"give a :exc:`ValueError` across almost all platforms, while " +"``sqrt(float('NaN'))`` should return a NaN on all IEEE 754 platforms. Where " +"Annex 'F' of the C99 standard recommends signaling 'divide-by-zero' or " +"'invalid', Python will raise :exc:`ValueError`. Where Annex 'F' of the C99 " +"standard recommends signaling 'overflow', Python will raise :exc:" +"`OverflowError`. (See :issue:`711019` and :issue:`1640`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2132 +msgid "(Contributed by Christian Heimes and Mark Dickinson.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2134 +msgid "" +":class:`mmap` objects now have a :meth:`rfind` method that searches for a " +"substring beginning at the end of the string and searching backwards. The :" +"meth:`find` method also gained an *end* parameter giving an index at which " +"to stop searching. (Contributed by John Lenton.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2140 +msgid "" +"The :mod:`operator` module gained a :func:`methodcaller` function that takes " +"a name and an optional set of arguments, returning a callable that will call " +"the named function on any arguments passed to it. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2150 +msgid "(Contributed by Georg Brandl, after a suggestion by Gregory Petrosyan.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2152 +msgid "" +"The :func:`attrgetter` function now accepts dotted names and performs the " +"corresponding attribute lookups::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2162 +msgid "(Contributed by Georg Brandl, after a suggestion by Barry Warsaw.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2164 +msgid "" +"The :mod:`os` module now wraps several new system calls. ``fchmod(fd, " +"mode)`` and ``fchown(fd, uid, gid)`` change the mode and ownership of an " +"opened file, and ``lchmod(path, mode)`` changes the mode of a symlink. " +"(Contributed by Georg Brandl and Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2170 +msgid "" +":func:`chflags` and :func:`lchflags` are wrappers for the corresponding " +"system calls (where they're available), changing the flags set on a file. " +"Constants for the flag values are defined in the :mod:`stat` module; some " +"possible values include :const:`UF_IMMUTABLE` to signal the file may not be " +"changed and :const:`UF_APPEND` to indicate that data can only be appended to " +"the file. (Contributed by M. Levinson.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2178 +msgid "" +"``os.closerange(low, high)`` efficiently closes all file descriptors from " +"*low* to *high*, ignoring any errors and not including *high* itself. This " +"function is now used by the :mod:`subprocess` module to make starting " +"processes faster. (Contributed by Georg Brandl; :issue:`1663329`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2183 +msgid "" +"The ``os.environ`` object's :meth:`clear` method will now unset the " +"environment variables using :func:`os.unsetenv` in addition to clearing the " +"object's keys. (Contributed by Martin Horcicka; :issue:`1181`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2187 +msgid "" +"The :func:`os.walk` function now has a ``followlinks`` parameter. If set to " +"True, it will follow symlinks pointing to directories and visit the " +"directory's contents. For backward compatibility, the parameter's default " +"value is false. Note that the function can fall into an infinite recursion " +"if there's a symlink that points to a parent directory. (:issue:`1273829`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2194 +msgid "" +"In the :mod:`os.path` module, the :func:`splitext` function has been changed " +"to not split on leading period characters. This produces better results when " +"operating on Unix's dot-files. For example, ``os.path.splitext('.ipython')`` " +"now returns ``('.ipython', '')`` instead of ``('', '.ipython')``. (:issue:" +"`1115886`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2201 +msgid "" +"A new function, ``os.path.relpath(path, start='.')``, returns a relative " +"path from the ``start`` path, if it's supplied, or from the current working " +"directory to the destination ``path``. (Contributed by Richard Barran; :" +"issue:`1339796`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2206 +msgid "" +"On Windows, :func:`os.path.expandvars` will now expand environment variables " +"given in the form \"%var%\", and \"~user\" will be expanded into the user's " +"home directory path. (Contributed by Josiah Carlson; :issue:`957650`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2211 +msgid "" +"The Python debugger provided by the :mod:`pdb` module gained a new command: " +"\"run\" restarts the Python program being debugged and can optionally take " +"new command-line arguments for the program. (Contributed by Rocky " +"Bernstein; :issue:`1393667`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2216 +msgid "" +"The :func:`pdb.post_mortem` function, used to begin debugging a traceback, " +"will now use the traceback returned by :func:`sys.exc_info` if no traceback " +"is supplied. (Contributed by Facundo Batista; :issue:`1106316`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2221 +msgid "" +"The :mod:`pickletools` module now has an :func:`optimize` function that " +"takes a string containing a pickle and removes some unused opcodes, " +"returning a shorter pickle that contains the same data structure. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2226 +msgid "" +"A :func:`get_data` function was added to the :mod:`pkgutil` module that " +"returns the contents of resource files included with an installed Python " +"package. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2241 +msgid "(Contributed by Paul Moore; :issue:`2439`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2243 +msgid "" +"The :mod:`pyexpat` module's :class:`Parser` objects now allow setting their :" +"attr:`buffer_size` attribute to change the size of the buffer used to hold " +"character data. (Contributed by Achim Gaedke; :issue:`1137`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2248 +msgid "" +"The :mod:`Queue` module now provides queue variants that retrieve entries in " +"different orders. The :class:`PriorityQueue` class stores queued items in a " +"heap and retrieves them in priority order, and :class:`LifoQueue` retrieves " +"the most recently added entries first, meaning that it behaves like a stack. " +"(Contributed by Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2255 +msgid "" +"The :mod:`random` module's :class:`Random` objects can now be pickled on a " +"32-bit system and unpickled on a 64-bit system, and vice versa. " +"Unfortunately, this change also means that Python 2.6's :class:`Random` " +"objects can't be unpickled correctly on earlier versions of Python. " +"(Contributed by Shawn Ligocki; :issue:`1727780`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2262 +msgid "" +"The new ``triangular(low, high, mode)`` function returns random numbers " +"following a triangular distribution. The returned values are between *low* " +"and *high*, not including *high* itself, and with *mode* as the most " +"frequently occurring value in the distribution. (Contributed by Wladmir van " +"der Laan and Raymond Hettinger; :issue:`1681432`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2269 +msgid "" +"Long regular expression searches carried out by the :mod:`re` module will " +"check for signals being delivered, so time-consuming searches can now be " +"interrupted. (Contributed by Josh Hoyt and Ralf Schmitt; :issue:`846388`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2274 +msgid "" +"The regular expression module is implemented by compiling bytecodes for a " +"tiny regex-specific virtual machine. Untrusted code could create malicious " +"strings of bytecode directly and cause crashes, so Python 2.6 includes a " +"verifier for the regex bytecode. (Contributed by Guido van Rossum from work " +"for Google App Engine; :issue:`3487`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2281 +msgid "" +"The :mod:`rlcompleter` module's :meth:`Completer.complete()` method will now " +"ignore exceptions triggered while evaluating a name. (Fixed by Lorenz " +"Quack; :issue:`2250`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2285 +msgid "" +"The :mod:`sched` module's :class:`scheduler` instances now have a read-only :" +"attr:`queue` attribute that returns the contents of the scheduler's queue, " +"represented as a list of named tuples with the fields ``(time, priority, " +"action, argument)``. (Contributed by Raymond Hettinger; :issue:`1861`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2291 +msgid "" +"The :mod:`select` module now has wrapper functions for the Linux :c:func:" +"`epoll` and BSD :c:func:`kqueue` system calls. :meth:`modify` method was " +"added to the existing :class:`poll` objects; ``pollobj.modify(fd, " +"eventmask)`` takes a file descriptor or file object and an event mask, " +"modifying the recorded event mask for that file. (Contributed by Christian " +"Heimes; :issue:`1657`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2299 +msgid "" +"The :func:`shutil.copytree` function now has an optional *ignore* argument " +"that takes a callable object. This callable will receive each directory " +"path and a list of the directory's contents, and returns a list of names " +"that will be ignored, not copied." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2304 +msgid "" +"The :mod:`shutil` module also provides an :func:`ignore_patterns` function " +"for use with this new parameter. :func:`ignore_patterns` takes an arbitrary " +"number of glob-style patterns and returns a callable that will ignore any " +"files and directories that match any of these patterns. The following " +"example copies a directory tree, but skips both :file:`.svn` directories and " +"Emacs backup files, which have names ending with '~'::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2315 +msgid "(Contributed by Tarek Ziadé; :issue:`2663`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2317 +msgid "" +"Integrating signal handling with GUI handling event loops like those used by " +"Tkinter or GTk+ has long been a problem; most software ends up polling, " +"waking up every fraction of a second to check if any GUI events have " +"occurred. The :mod:`signal` module can now make this more efficient. Calling " +"``signal.set_wakeup_fd(fd)`` sets a file descriptor to be used; when a " +"signal is received, a byte is written to that file descriptor. There's also " +"a C-level function, :c:func:`PySignal_SetWakeupFd`, for setting the " +"descriptor." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2327 +msgid "" +"Event loops will use this by opening a pipe to create two descriptors, one " +"for reading and one for writing. The writable descriptor will be passed to :" +"func:`set_wakeup_fd`, and the readable descriptor will be added to the list " +"of descriptors monitored by the event loop via :c:func:`select` or :c:func:" +"`poll`. On receiving a signal, a byte will be written and the main event " +"loop will be woken up, avoiding the need to poll." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2335 +msgid "(Contributed by Adam Olsen; :issue:`1583`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2337 +msgid "" +"The :func:`siginterrupt` function is now available from Python code, and " +"allows changing whether signals can interrupt system calls or not. " +"(Contributed by Ralf Schmitt.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2341 +msgid "" +"The :func:`setitimer` and :func:`getitimer` functions have also been added " +"(where they're available). :func:`setitimer` allows setting interval timers " +"that will cause a signal to be delivered to the process after a specified " +"time, measured in wall-clock time, consumed process time, or combined process" +"+system time. (Contributed by Guilherme Polo; :issue:`2240`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2348 +msgid "" +"The :mod:`smtplib` module now supports SMTP over SSL thanks to the addition " +"of the :class:`SMTP_SSL` class. This class supports an interface identical " +"to the existing :class:`SMTP` class. (Contributed by Monty Taylor.) Both " +"class constructors also have an optional ``timeout`` parameter that " +"specifies a timeout for the initial connection attempt, measured in " +"seconds. (Contributed by Facundo Batista.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2356 +msgid "" +"An implementation of the LMTP protocol (:rfc:`2033`) was also added to the " +"module. LMTP is used in place of SMTP when transferring e-mail between " +"agents that don't manage a mail queue. (LMTP implemented by Leif Hedstrom; :" +"issue:`957003`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2361 +msgid "" +":meth:`SMTP.starttls` now complies with :rfc:`3207` and forgets any " +"knowledge obtained from the server not obtained from the TLS negotiation " +"itself. (Patch contributed by Bill Fenner; :issue:`829951`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2366 +msgid "" +"The :mod:`socket` module now supports TIPC (http://tipc.sourceforge.net/), a " +"high-performance non-IP-based protocol designed for use in clustered " +"environments. TIPC addresses are 4- or 5-tuples. (Contributed by Alberto " +"Bertogli; :issue:`1646`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2371 +msgid "" +"A new function, :func:`create_connection`, takes an address and connects to " +"it using an optional timeout value, returning the connected socket object. " +"This function also looks up the address's type and connects to it using IPv4 " +"or IPv6 as appropriate. Changing your code to use :func:`create_connection` " +"instead of ``socket(socket.AF_INET, ...)`` may be all that's required to " +"make your code work with IPv6." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2379 +msgid "" +"The base classes in the :mod:`SocketServer` module now support calling a :" +"meth:`handle_timeout` method after a span of inactivity specified by the " +"server's :attr:`timeout` attribute. (Contributed by Michael Pomraning.) " +"The :meth:`serve_forever` method now takes an optional poll interval " +"measured in seconds, controlling how often the server will check for a " +"shutdown request. (Contributed by Pedro Werneck and Jeffrey Yasskin; :issue:" +"`742598`, :issue:`1193577`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2388 +msgid "" +"The :mod:`sqlite3` module, maintained by Gerhard Häring, has been updated " +"from version 2.3.2 in Python 2.5 to version 2.4.1." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2392 +msgid "" +"The :mod:`struct` module now supports the C99 :c:type:`_Bool` type, using " +"the format character ``'?'``. (Contributed by David Remahl.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2396 +msgid "" +"The :class:`Popen` objects provided by the :mod:`subprocess` module now " +"have :meth:`terminate`, :meth:`kill`, and :meth:`send_signal` methods. On " +"Windows, :meth:`send_signal` only supports the :const:`SIGTERM` signal, and " +"all these methods are aliases for the Win32 API function :c:func:" +"`TerminateProcess`. (Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2403 +msgid "" +"A new variable in the :mod:`sys` module, :attr:`float_info`, is an object " +"containing information derived from the :file:`float.h` file about the " +"platform's floating-point support. Attributes of this object include :attr:" +"`mant_dig` (number of digits in the mantissa), :attr:`epsilon` (smallest " +"difference between 1.0 and the next largest value representable), and " +"several others. (Contributed by Christian Heimes; :issue:`1534`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2411 +msgid "" +"Another new variable, :attr:`dont_write_bytecode`, controls whether Python " +"writes any :file:`.pyc` or :file:`.pyo` files on importing a module. If this " +"variable is true, the compiled files are not written. The variable is " +"initially set on start-up by supplying the :option:`-B` switch to the Python " +"interpreter, or by setting the :envvar:`PYTHONDONTWRITEBYTECODE` environment " +"variable before running the interpreter. Python code can subsequently " +"change the value of this variable to control whether bytecode files are " +"written or not. (Contributed by Neal Norwitz and Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2422 +msgid "" +"Information about the command-line arguments supplied to the Python " +"interpreter is available by reading attributes of a named tuple available as " +"``sys.flags``. For example, the :attr:`verbose` attribute is true if Python " +"was executed in verbose mode, :attr:`debug` is true in debugging mode, etc. " +"These attributes are all read-only. (Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2430 +msgid "" +"A new function, :func:`getsizeof`, takes a Python object and returns the " +"amount of memory used by the object, measured in bytes. Built-in objects " +"return correct results; third-party extensions may not, but can define a :" +"meth:`__sizeof__` method to return the object's size. (Contributed by Robert " +"Schuppenies; :issue:`2898`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2437 +msgid "" +"It's now possible to determine the current profiler and tracer functions by " +"calling :func:`sys.getprofile` and :func:`sys.gettrace`. (Contributed by " +"Georg Brandl; :issue:`1648`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2441 +msgid "" +"The :mod:`tarfile` module now supports POSIX.1-2001 (pax) tarfiles in " +"addition to the POSIX.1-1988 (ustar) and GNU tar formats that were already " +"supported. The default format is GNU tar; specify the ``format`` parameter " +"to open a file using a different format::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2449 +msgid "" +"The new ``encoding`` and ``errors`` parameters specify an encoding and an " +"error handling scheme for character conversions. ``'strict'``, " +"``'ignore'``, and ``'replace'`` are the three standard ways Python can " +"handle errors,; ``'utf-8'`` is a special value that replaces bad characters " +"with their UTF-8 representation. (Character conversions occur because the " +"PAX format supports Unicode filenames, defaulting to UTF-8 encoding.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2457 +msgid "" +"The :meth:`TarFile.add` method now accepts an ``exclude`` argument that's a " +"function that can be used to exclude certain filenames from an archive. The " +"function must take a filename and return true if the file should be excluded " +"or false if it should be archived. The function is applied to both the name " +"initially passed to :meth:`add` and to the names of files in recursively-" +"added directories." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2465 +msgid "(All changes contributed by Lars Gustäbel)." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2467 +msgid "" +"An optional ``timeout`` parameter was added to the :class:`telnetlib.Telnet` " +"class constructor, specifying a timeout measured in seconds. (Added by " +"Facundo Batista.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2471 +msgid "" +"The :class:`tempfile.NamedTemporaryFile` class usually deletes the temporary " +"file it created when the file is closed. This behaviour can now be changed " +"by passing ``delete=False`` to the constructor. (Contributed by Damien " +"Miller; :issue:`1537850`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2476 +msgid "" +"A new class, :class:`SpooledTemporaryFile`, behaves like a temporary file " +"but stores its data in memory until a maximum size is exceeded. On reaching " +"that limit, the contents will be written to an on-disk temporary file. " +"(Contributed by Dustin J. Mitchell.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2481 +msgid "" +"The :class:`NamedTemporaryFile` and :class:`SpooledTemporaryFile` classes " +"both work as context managers, so you can write ``with tempfile." +"NamedTemporaryFile() as tmp: ...``. (Contributed by Alexander Belopolsky; :" +"issue:`2021`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2486 +msgid "" +"The :mod:`test.test_support` module gained a number of context managers " +"useful for writing tests. :func:`EnvironmentVarGuard` is a context manager " +"that temporarily changes environment variables and automatically restores " +"them to their old values." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2492 +msgid "" +"Another context manager, :class:`TransientResource`, can surround calls to " +"resources that may or may not be available; it will catch and ignore a " +"specified list of exceptions. For example, a network test may ignore " +"certain failures when connecting to an external web site::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2503 +msgid "" +"Finally, :func:`check_warnings` resets the :mod:`warning` module's warning " +"filters and returns an object that will record all warning messages " +"triggered (:issue:`3781`)::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2513 ../Doc/whatsnew/3.1.rst:413 +msgid "(Contributed by Brett Cannon.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2515 +msgid "" +"The :mod:`textwrap` module can now preserve existing whitespace at the " +"beginnings and ends of the newly-created lines by specifying " +"``drop_whitespace=False`` as an argument::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2534 +msgid "(Contributed by Dwayne Bailey; :issue:`1581073`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2536 +msgid "" +"The :mod:`threading` module API is being changed to use properties such as :" +"attr:`daemon` instead of :meth:`setDaemon` and :meth:`isDaemon` methods, and " +"some methods have been renamed to use underscores instead of camel-case; for " +"example, the :meth:`activeCount` method is renamed to :meth:`active_count`. " +"Both the 2.6 and 3.0 versions of the module support the same properties and " +"renamed methods, but don't remove the old methods. No date has been set for " +"the deprecation of the old APIs in Python 3.x; the old APIs won't be removed " +"in any 2.x version. (Carried out by several people, most notably Benjamin " +"Peterson.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2547 +msgid "" +"The :mod:`threading` module's :class:`Thread` objects gained an :attr:" +"`ident` property that returns the thread's identifier, a nonzero integer. " +"(Contributed by Gregory P. Smith; :issue:`2871`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2552 +msgid "" +"The :mod:`timeit` module now accepts callables as well as strings for the " +"statement being timed and for the setup code. Two convenience functions were " +"added for creating :class:`Timer` instances: ``repeat(stmt, setup, time, " +"repeat, number)`` and ``timeit(stmt, setup, time, number)`` create an " +"instance and call the corresponding method. (Contributed by Erik Demaine; :" +"issue:`1533909`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2561 +msgid "" +"The :mod:`Tkinter` module now accepts lists and tuples for options, " +"separating the elements by spaces before passing the resulting value to Tcl/" +"Tk. (Contributed by Guilherme Polo; :issue:`2906`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2566 +msgid "" +"The :mod:`turtle` module for turtle graphics was greatly enhanced by Gregor " +"Lingl. New features in the module include:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2569 +msgid "Better animation of turtle movement and rotation." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2570 +msgid "" +"Control over turtle movement using the new :meth:`delay`, :meth:`tracer`, " +"and :meth:`speed` methods." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2572 +msgid "" +"The ability to set new shapes for the turtle, and to define a new coordinate " +"system." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2574 +msgid "Turtles now have an :meth:`undo()` method that can roll back actions." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2575 +msgid "" +"Simple support for reacting to input events such as mouse and keyboard " +"activity, making it possible to write simple games." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2577 +msgid "" +"A :file:`turtle.cfg` file can be used to customize the starting appearance " +"of the turtle's screen." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2579 +msgid "" +"The module's docstrings can be replaced by new docstrings that have been " +"translated into another language." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2582 +msgid "(:issue:`1513695`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2584 +msgid "" +"An optional ``timeout`` parameter was added to the :func:`urllib.urlopen` " +"function and the :class:`urllib.ftpwrapper` class constructor, as well as " +"the :func:`urllib2.urlopen` function. The parameter specifies a timeout " +"measured in seconds. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2597 +msgid "(Added by Facundo Batista.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2599 +msgid "" +"The Unicode database provided by the :mod:`unicodedata` module has been " +"updated to version 5.1.0. (Updated by Martin von Löwis; :issue:`3811`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2603 +msgid "" +"The :mod:`warnings` module's :func:`formatwarning` and :func:`showwarning` " +"gained an optional *line* argument that can be used to supply the line of " +"source code. (Added as part of :issue:`1631171`, which re-implemented part " +"of the :mod:`warnings` module in C code.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2608 +msgid "" +"A new function, :func:`catch_warnings`, is a context manager intended for " +"testing purposes that lets you temporarily modify the warning filters and " +"then restore their original values (:issue:`3781`)." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2612 +msgid "" +"The XML-RPC :class:`SimpleXMLRPCServer` and :class:`DocXMLRPCServer` classes " +"can now be prevented from immediately opening and binding to their socket by " +"passing True as the ``bind_and_activate`` constructor parameter. This can " +"be used to modify the instance's :attr:`allow_reuse_address` attribute " +"before calling the :meth:`server_bind` and :meth:`server_activate` methods " +"to open the socket and begin listening for connections. (Contributed by " +"Peter Parente; :issue:`1599845`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2621 +msgid "" +":class:`SimpleXMLRPCServer` also has a :attr:`_send_traceback_header` " +"attribute; if true, the exception and formatted traceback are returned as " +"HTTP headers \"X-Exception\" and \"X-Traceback\". This feature is for " +"debugging purposes only and should not be used on production servers because " +"the tracebacks might reveal passwords or other sensitive information. " +"(Contributed by Alan McIntyre as part of his project for Google's Summer of " +"Code 2007.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2629 +msgid "" +"The :mod:`xmlrpclib` module no longer automatically converts :class:" +"`datetime.date` and :class:`datetime.time` to the :class:`xmlrpclib." +"DateTime` type; the conversion semantics were not necessarily correct for " +"all applications. Code using :mod:`xmlrpclib` should convert :class:`date` " +"and :class:`time` instances. (:issue:`1330538`) The code can also handle " +"dates before 1900 (contributed by Ralf Schmitt; :issue:`2014`) and 64-bit " +"integers represented by using ```` in XML-RPC responses (contributed by " +"Riku Lindblad; :issue:`2985`)." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2639 +msgid "" +"The :mod:`zipfile` module's :class:`ZipFile` class now has :meth:`extract` " +"and :meth:`extractall` methods that will unpack a single file or all the " +"files in the archive to the current directory, or to a specified directory::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2653 +msgid "(Contributed by Alan McIntyre; :issue:`467924`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2655 +msgid "" +"The :meth:`open`, :meth:`read` and :meth:`extract` methods can now take " +"either a filename or a :class:`ZipInfo` object. This is useful when an " +"archive accidentally contains a duplicated filename. (Contributed by Graham " +"Horler; :issue:`1775025`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2660 +msgid "" +"Finally, :mod:`zipfile` now supports using Unicode filenames for archived " +"files. (Contributed by Alexey Borzenkov; :issue:`1734346`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2667 +msgid "The :mod:`ast` module" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2669 +msgid "" +"The :mod:`ast` module provides an Abstract Syntax Tree representation of " +"Python code, and Armin Ronacher contributed a set of helper functions that " +"perform a variety of common tasks. These will be useful for HTML templating " +"packages, code analyzers, and similar tools that process Python code." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2676 +msgid "" +"The :func:`parse` function takes an expression and returns an AST. The :func:" +"`dump` function outputs a representation of a tree, suitable for debugging::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2690 +msgid "This outputs a deeply nested tree::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2723 +msgid "" +"The :func:`literal_eval` method takes a string or an AST representing a " +"literal expression, parses and evaluates it, and returns the resulting " +"value. A literal expression is a Python expression containing only strings, " +"numbers, dictionaries, etc. but no statements or function calls. If you " +"need to evaluate an expression but cannot accept the security risk of using " +"an :func:`eval` call, :func:`literal_eval` will handle it safely::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2739 +msgid "" +"The module also includes :class:`NodeVisitor` and :class:`NodeTransformer` " +"classes for traversing and modifying an AST, and functions for common " +"transformations such as changing line numbers." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2747 +msgid "The :mod:`future_builtins` module" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2749 +msgid "" +"Python 3.0 makes many changes to the repertoire of built-in functions, and " +"most of the changes can't be introduced in the Python 2.x series because " +"they would break compatibility. The :mod:`future_builtins` module provides " +"versions of these built-in functions that can be imported when writing 3.0-" +"compatible code." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2756 +msgid "The functions in this module currently include:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2758 +msgid "" +"``ascii(obj)``: equivalent to :func:`repr`. In Python 3.0, :func:`repr` " +"will return a Unicode string, while :func:`ascii` will return a pure ASCII " +"bytestring." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2762 +msgid "" +"``filter(predicate, iterable)``, ``map(func, iterable1, ...)``: the 3.0 " +"versions return iterators, unlike the 2.x builtins which return lists." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2766 +msgid "" +"``hex(value)``, ``oct(value)``: instead of calling the :meth:`__hex__` or :" +"meth:`__oct__` methods, these versions will call the :meth:`__index__` " +"method and convert the result to hexadecimal or octal. :func:`oct` will use " +"the new ``0o`` notation for its result." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2775 +msgid "The :mod:`json` module: JavaScript Object Notation" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2777 +msgid "" +"The new :mod:`json` module supports the encoding and decoding of Python " +"types in JSON (Javascript Object Notation). JSON is a lightweight " +"interchange format often used in web applications. For more information " +"about JSON, see http://www.json.org." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2782 +msgid "" +":mod:`json` comes with support for decoding and encoding most built-in " +"Python types. The following example encodes and decodes a dictionary::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2793 +msgid "" +"It's also possible to write your own decoders and encoders to support more " +"types. Pretty-printing of the JSON strings is also supported." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2796 +msgid ":mod:`json` (originally called simplejson) was written by Bob Ippolito." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2803 +msgid "The :mod:`plistlib` module: A Property-List Parser" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2805 +msgid "" +"The ``.plist`` format is commonly used on Mac OS X to store basic data types " +"(numbers, strings, lists, and dictionaries) by serializing them into an XML-" +"based format. It resembles the XML-RPC serialization of data types." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2810 +msgid "" +"Despite being primarily used on Mac OS X, the format has nothing Mac-" +"specific about it and the Python implementation works on any platform that " +"Python supports, so the :mod:`plistlib` module has been promoted to the " +"standard library." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2815 +msgid "Using the module is simple::" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2842 +msgid "ctypes Enhancements" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2844 +msgid "" +"Thomas Heller continued to maintain and enhance the :mod:`ctypes` module." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2847 +msgid "" +":mod:`ctypes` now supports a :class:`c_bool` datatype that represents the " +"C99 ``bool`` type. (Contributed by David Remahl; :issue:`1649190`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2851 +msgid "" +"The :mod:`ctypes` string, buffer and array types have improved support for " +"extended slicing syntax, where various combinations of ``(start, stop, " +"step)`` are supplied. (Implemented by Thomas Wouters.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2858 +msgid "" +"All :mod:`ctypes` data types now support :meth:`from_buffer` and :meth:" +"`from_buffer_copy` methods that create a ctypes instance based on a provided " +"buffer object. :meth:`from_buffer_copy` copies the contents of the object, " +"while :meth:`from_buffer` will share the same memory area." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2865 +msgid "" +"A new calling convention tells :mod:`ctypes` to clear the ``errno`` or Win32 " +"LastError variables at the outset of each wrapped call. (Implemented by " +"Thomas Heller; :issue:`1798`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2869 +msgid "" +"You can now retrieve the Unix ``errno`` variable after a function call. " +"When creating a wrapped function, you can supply ``use_errno=True`` as a " +"keyword parameter to the :func:`DLL` function and then call the module-level " +"methods :meth:`set_errno` and :meth:`get_errno` to set and retrieve the " +"error value." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2875 +msgid "" +"The Win32 LastError variable is similarly supported by the :func:`DLL`, :" +"func:`OleDLL`, and :func:`WinDLL` functions. You supply " +"``use_last_error=True`` as a keyword parameter and then call the module-" +"level methods :meth:`set_last_error` and :meth:`get_last_error`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2881 +msgid "" +"The :func:`byref` function, used to retrieve a pointer to a ctypes instance, " +"now has an optional *offset* parameter that is a byte count that will be " +"added to the returned pointer." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2888 +msgid "Improved SSL Support" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2890 +msgid "" +"Bill Janssen made extensive improvements to Python 2.6's support for the " +"Secure Sockets Layer by adding a new module, :mod:`ssl`, that's built atop " +"the `OpenSSL `__ library. This new module provides " +"more control over the protocol negotiated, the X.509 certificates used, and " +"has better support for writing SSL servers (as opposed to clients) in " +"Python. The existing SSL support in the :mod:`socket` module hasn't been " +"removed and continues to work, though it will be removed in Python 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2899 +msgid "" +"To use the new module, you must first create a TCP connection in the usual " +"way and then pass it to the :func:`ssl.wrap_socket` function. It's possible " +"to specify whether a certificate is required, and to obtain certificate info " +"by calling the :meth:`getpeercert` method." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2906 +msgid "The documentation for the :mod:`ssl` module." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2911 +msgid "Deprecations and Removals" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2913 ../Doc/whatsnew/2.6.rst:3241 +msgid "" +"String exceptions have been removed. Attempting to use them raises a :exc:" +"`TypeError`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2916 +msgid "" +"Changes to the :class:`Exception` interface as dictated by :pep:`352` " +"continue to be made. For 2.6, the :attr:`message` attribute is being " +"deprecated in favor of the :attr:`args` attribute." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2921 +msgid "" +"(3.0-warning mode) Python 3.0 will feature a reorganized standard library " +"that will drop many outdated modules and rename others. Python 2.6 running " +"in 3.0-warning mode will warn about these modules when they are imported." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2926 +msgid "" +"The list of deprecated modules is: :mod:`audiodev`, :mod:`bgenlocations`, :" +"mod:`buildtools`, :mod:`bundlebuilder`, :mod:`Canvas`, :mod:`compiler`, :mod:" +"`dircache`, :mod:`dl`, :mod:`fpformat`, :mod:`gensuitemodule`, :mod:" +"`ihooks`, :mod:`imageop`, :mod:`imgfile`, :mod:`linuxaudiodev`, :mod:" +"`mhlib`, :mod:`mimetools`, :mod:`multifile`, :mod:`new`, :mod:`pure`, :mod:" +"`statvfs`, :mod:`sunaudiodev`, :mod:`test.testall`, and :mod:`toaiff`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2951 +msgid "The :mod:`gopherlib` module has been removed." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2953 +msgid "" +"The :mod:`MimeWriter` module and :mod:`mimify` module have been deprecated; " +"use the :mod:`email` package instead." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2957 +msgid "" +"The :mod:`md5` module has been deprecated; use the :mod:`hashlib` module " +"instead." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2960 +msgid "" +"The :mod:`posixfile` module has been deprecated; :func:`fcntl.lockf` " +"provides better locking." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2963 +msgid "" +"The :mod:`popen2` module has been deprecated; use the :mod:`subprocess` " +"module." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2966 +msgid "The :mod:`rgbimg` module has been removed." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2968 +msgid "" +"The :mod:`sets` module has been deprecated; it's better to use the built-in :" +"class:`set` and :class:`frozenset` types." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2971 +msgid "" +"The :mod:`sha` module has been deprecated; use the :mod:`hashlib` module " +"instead." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2983 +msgid "" +"Python now must be compiled with C89 compilers (after 19 years!). This " +"means that the Python source tree has dropped its own implementations of :c:" +"func:`memmove` and :c:func:`strerror`, which are in the C89 standard library." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2988 +msgid "" +"Python 2.6 can be built with Microsoft Visual Studio 2008 (version 9.0), and " +"this is the new default compiler. See the :file:`PCbuild` directory for the " +"build files. (Implemented by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:2993 +msgid "" +"On Mac OS X, Python 2.6 can be compiled as a 4-way universal build. The :" +"program:`configure` script can take a :option:`--with-universal-archs=[32-" +"bit|64-bit|all]` switch, controlling whether the binaries are built for 32-" +"bit architectures (x86, PowerPC), 64-bit (x86-64 and PPC-64), or both. " +"(Contributed by Ronald Oussoren.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3000 +msgid "" +"The BerkeleyDB module now has a C API object, available as ``bsddb.db." +"api``. This object can be used by other C extensions that wish to use the :" +"mod:`bsddb` module for their own purposes. (Contributed by Duncan Grisby.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3005 +msgid "" +"The new buffer interface, previously described in `the PEP 3118 section " +"<#pep-3118-revised-buffer-protocol>`__, adds :c:func:`PyObject_GetBuffer` " +"and :c:func:`PyBuffer_Release`, as well as a few other functions." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3010 +msgid "" +"Python's use of the C stdio library is now thread-safe, or at least as " +"thread-safe as the underlying library is. A long-standing potential bug " +"occurred if one thread closed a file object while another thread was reading " +"from or writing to the object. In 2.6 file objects have a reference count, " +"manipulated by the :c:func:`PyFile_IncUseCount` and :c:func:" +"`PyFile_DecUseCount` functions. File objects can't be closed unless the " +"reference count is zero. :c:func:`PyFile_IncUseCount` should be called " +"while the GIL is still held, before carrying out an I/O operation using the " +"``FILE *`` pointer, and :c:func:`PyFile_DecUseCount` should be called " +"immediately after the GIL is re-acquired. (Contributed by Antoine Pitrou and " +"Gregory P. Smith.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3023 +msgid "" +"Importing modules simultaneously in two different threads no longer " +"deadlocks; it will now raise an :exc:`ImportError`. A new API function, :c:" +"func:`PyImport_ImportModuleNoBlock`, will look for a module in ``sys." +"modules`` first, then try to import it after acquiring an import lock. If " +"the import lock is held by another thread, an :exc:`ImportError` is raised. " +"(Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3031 +msgid "" +"Several functions return information about the platform's floating-point " +"support. :c:func:`PyFloat_GetMax` returns the maximum representable " +"floating point value, and :c:func:`PyFloat_GetMin` returns the minimum " +"positive value. :c:func:`PyFloat_GetInfo` returns an object containing more " +"information from the :file:`float.h` file, such as ``\"mant_dig\"`` (number " +"of digits in the mantissa), ``\"epsilon\"`` (smallest difference between 1.0 " +"and the next largest value representable), and several others. (Contributed " +"by Christian Heimes; :issue:`1534`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3042 +msgid "" +"C functions and methods that use :c:func:`PyComplex_AsCComplex` will now " +"accept arguments that have a :meth:`__complex__` method. In particular, the " +"functions in the :mod:`cmath` module will now accept objects with this " +"method. This is a backport of a Python 3.0 change. (Contributed by Mark " +"Dickinson; :issue:`1675423`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3049 +msgid "" +"Python's C API now includes two functions for case-insensitive string " +"comparisons, ``PyOS_stricmp(char*, char*)`` and ``PyOS_strnicmp(char*, " +"char*, Py_ssize_t)``. (Contributed by Christian Heimes; :issue:`1635`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3054 +msgid "" +"Many C extensions define their own little macro for adding integers and " +"strings to the module's dictionary in the ``init*`` function. Python 2.6 " +"finally defines standard macros for adding values to a module, :c:macro:" +"`PyModule_AddStringMacro` and :c:macro:`PyModule_AddIntMacro()`. " +"(Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3061 +msgid "" +"Some macros were renamed in both 3.0 and 2.6 to make it clearer that they " +"are macros, not functions. :c:macro:`Py_Size()` became :c:macro:" +"`Py_SIZE()`, :c:macro:`Py_Type()` became :c:macro:`Py_TYPE()`, and :c:macro:" +"`Py_Refcnt()` became :c:macro:`Py_REFCNT()`. The mixed-case macros are still " +"available in Python 2.6 for backward compatibility. (:issue:`1629`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3070 +msgid "" +"Distutils now places C extensions it builds in a different directory when " +"running on a debug version of Python. (Contributed by Collin Winter; :issue:" +"`1530959`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3074 +msgid "" +"Several basic data types, such as integers and strings, maintain internal " +"free lists of objects that can be re-used. The data structures for these " +"free lists now follow a naming convention: the variable is always named " +"``free_list``, the counter is always named ``numfree``, and a macro " +"``Py_MAXFREELIST`` is always defined." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3081 +msgid "" +"A new Makefile target, \"make patchcheck\", prepares the Python source tree " +"for making a patch: it fixes trailing whitespace in all modified ``.py`` " +"files, checks whether the documentation has been changed, and reports " +"whether the :file:`Misc/ACKS` and :file:`Misc/NEWS` files have been updated. " +"(Contributed by Brett Cannon.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3088 +msgid "" +"Another new target, \"make profile-opt\", compiles a Python binary using " +"GCC's profile-guided optimization. It compiles Python with profiling " +"enabled, runs the test suite to obtain a set of profiling results, and then " +"compiles using these results for optimization. (Contributed by Gregory P. " +"Smith.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3097 ../Doc/whatsnew/2.7.rst:2325 +msgid "Port-Specific Changes: Windows" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3099 +msgid "" +"The support for Windows 95, 98, ME and NT4 has been dropped. Python 2.6 " +"requires at least Windows 2000 SP4." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3102 +msgid "" +"The new default compiler on Windows is Visual Studio 2008 (version 9.0). The " +"build directories for Visual Studio 2003 (version 7.1) and 2005 (version " +"8.0) were moved into the PC/ directory. The new :file:`PCbuild` directory " +"supports cross compilation for X64, debug builds and Profile Guided " +"Optimization (PGO). PGO builds are roughly 10% faster than normal builds. " +"(Contributed by Christian Heimes with help from Amaury Forgeot d'Arc and " +"Martin von Löwis.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3110 +msgid "" +"The :mod:`msvcrt` module now supports both the normal and wide char variants " +"of the console I/O API. The :func:`getwch` function reads a keypress and " +"returns a Unicode value, as does the :func:`getwche` function. The :func:" +"`putwch` function takes a Unicode character and writes it to the console. " +"(Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3117 +msgid "" +":func:`os.path.expandvars` will now expand environment variables in the form " +"\"%var%\", and \"~user\" will be expanded into the user's home directory " +"path. (Contributed by Josiah Carlson; :issue:`957650`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3121 +msgid "" +"The :mod:`socket` module's socket objects now have an :meth:`ioctl` method " +"that provides a limited interface to the :c:func:`WSAIoctl` system interface." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3125 +msgid "" +"The :mod:`_winreg` module now has a function, :func:" +"`ExpandEnvironmentStrings`, that expands environment variable references " +"such as ``%NAME%`` in an input string. The handle objects provided by this " +"module now support the context protocol, so they can be used in :keyword:" +"`with` statements. (Contributed by Christian Heimes.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3132 +msgid "" +":mod:`_winreg` also has better support for x64 systems, exposing the :func:" +"`DisableReflectionKey`, :func:`EnableReflectionKey`, and :func:" +"`QueryReflectionKey` functions, which enable and disable registry reflection " +"for 32-bit processes running on 64-bit systems. (:issue:`1753245`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3138 +msgid "" +"The :mod:`msilib` module's :class:`Record` object gained :meth:`GetInteger` " +"and :meth:`GetString` methods that return field values as an integer or a " +"string. (Contributed by Floris Bruynooghe; :issue:`2125`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3146 ../Doc/whatsnew/2.7.rst:2363 +msgid "Port-Specific Changes: Mac OS X" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3148 +msgid "" +"When compiling a framework build of Python, you can now specify the " +"framework name to be used by providing the :option:`--with-framework-name=` " +"option to the :program:`configure` script." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3153 +msgid "" +"The :mod:`macfs` module has been removed. This in turn required the :func:" +"`macostools.touched` function to be removed because it depended on the :mod:" +"`macfs` module. (:issue:`1490190`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3157 +msgid "" +"Many other Mac OS modules have been deprecated and will be removed in Python " +"3.0: :mod:`_builtinSuites`, :mod:`aepack`, :mod:`aetools`, :mod:`aetypes`, :" +"mod:`applesingle`, :mod:`appletrawmain`, :mod:`appletrunner`, :mod:" +"`argvemulator`, :mod:`Audio_mac`, :mod:`autoGIL`, :mod:`Carbon`, :mod:" +"`cfmfile`, :mod:`CodeWarrior`, :mod:`ColorPicker`, :mod:`EasyDialogs`, :mod:" +"`Explorer`, :mod:`Finder`, :mod:`FrameWork`, :mod:`findertools`, :mod:`ic`, :" +"mod:`icglue`, :mod:`icopen`, :mod:`macerrors`, :mod:`MacOS`, :mod:`macfs`, :" +"mod:`macostools`, :mod:`macresource`, :mod:`MiniAEFrame`, :mod:`Nav`, :mod:" +"`Netscape`, :mod:`OSATerminology`, :mod:`pimp`, :mod:`PixMapWrapper`, :mod:" +"`StdSuites`, :mod:`SystemEvents`, :mod:`Terminal`, and :mod:" +"`terminalcommand`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3200 +msgid "Port-Specific Changes: IRIX" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3202 +msgid "" +"A number of old IRIX-specific modules were deprecated and will be removed in " +"Python 3.0: :mod:`al` and :mod:`AL`, :mod:`cd`, :mod:`cddb`, :mod:" +"`cdplayer`, :mod:`CL` and :mod:`cl`, :mod:`DEVICE`, :mod:`ERRNO`, :mod:" +"`FILE`, :mod:`FL` and :mod:`fl`, :mod:`flp`, :mod:`fm`, :mod:`GET`, :mod:" +"`GLWS`, :mod:`GL` and :mod:`gl`, :mod:`IN`, :mod:`IOCTL`, :mod:`jpeg`, :mod:" +"`panelparser`, :mod:`readcd`, :mod:`SV` and :mod:`sv`, :mod:`torgb`, :mod:" +"`videoreader`, and :mod:`WAIT`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3232 +msgid "Porting to Python 2.6" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3234 ../Doc/whatsnew/2.7.rst:2425 +#: ../Doc/whatsnew/3.1.rst:523 ../Doc/whatsnew/3.2.rst:2601 +msgid "" +"This section lists previously described changes and other bugfixes that may " +"require changes to your code:" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3237 +msgid "" +"Classes that aren't supposed to be hashable should set ``__hash__ = None`` " +"in their definitions to indicate the fact." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3244 +msgid "" +"The :meth:`__init__` method of :class:`collections.deque` now clears any " +"existing contents of the deque before adding elements from the iterable. " +"This change makes the behavior match ``list.__init__()``." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3249 +msgid "" +":meth:`object.__init__` previously accepted arbitrary arguments and keyword " +"arguments, ignoring them. In Python 2.6, this is no longer allowed and will " +"result in a :exc:`TypeError`. This will affect :meth:`__init__` methods " +"that end up calling the corresponding method on :class:`object` (perhaps " +"through using :func:`super`). See :issue:`1683368` for discussion." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3256 +msgid "" +"The :class:`Decimal` constructor now accepts leading and trailing whitespace " +"when passed a string. Previously it would raise an :exc:`InvalidOperation` " +"exception. On the other hand, the :meth:`create_decimal` method of :class:" +"`Context` objects now explicitly disallows extra whitespace, raising a :exc:" +"`ConversionSyntax` exception." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3263 +msgid "" +"Due to an implementation accident, if you passed a file path to the built-" +"in :func:`__import__` function, it would actually import the specified " +"file. This was never intended to work, however, and the implementation now " +"explicitly checks for this case and raises an :exc:`ImportError`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3269 +msgid "" +"C API: the :c:func:`PyImport_Import` and :c:func:`PyImport_ImportModule` " +"functions now default to absolute imports, not relative imports. This will " +"affect C extensions that import other modules." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3273 +msgid "" +"C API: extension data types that shouldn't be hashable should define their " +"``tp_hash`` slot to :c:func:`PyObject_HashNotImplemented`." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3277 +msgid "" +"The :mod:`socket` module exception :exc:`socket.error` now inherits from :" +"exc:`IOError`. Previously it wasn't a subclass of :exc:`StandardError` but " +"now it is, through :exc:`IOError`. (Implemented by Gregory P. Smith; :issue:" +"`1706815`.)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3282 +msgid "" +"The :mod:`xmlrpclib` module no longer automatically converts :class:" +"`datetime.date` and :class:`datetime.time` to the :class:`xmlrpclib." +"DateTime` type; the conversion semantics were not necessarily correct for " +"all applications. Code using :mod:`xmlrpclib` should convert :class:`date` " +"and :class:`time` instances. (:issue:`1330538`)" +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3289 +msgid "" +"(3.0-warning mode) The :class:`Exception` class now warns when accessed " +"using slicing or index access; having :class:`Exception` behave like a tuple " +"is being phased out." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3293 +msgid "" +"(3.0-warning mode) inequality comparisons between two dictionaries or two " +"objects that don't implement comparison methods are reported as warnings. " +"``dict1 == dict2`` still works, but ``dict1 < dict2`` is being phased out." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3298 +msgid "" +"Comparisons between cells, which are an implementation detail of Python's " +"scoping rules, also cause warnings because such comparisons are forbidden " +"entirely in 3.0." +msgstr "" + +#: ../Doc/whatsnew/2.6.rst:3310 +msgid "" +"The author would like to thank the following people for offering " +"suggestions, corrections and assistance with various drafts of this article: " +"Georg Brandl, Steve Brown, Nick Coghlan, Ralph Corderoy, Jim Jewett, Kent " +"Johnson, Chris Lambacher, Martin Michlmayr, Antoine Pitrou, Brian Warner." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:3 +msgid "What's New in Python 2.7" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:52 +msgid "" +"This article explains the new features in Python 2.7. Python 2.7 was " +"released on July 3, 2010." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:55 +msgid "" +"Numeric handling has been improved in many ways, for both floating-point " +"numbers and for the :class:`~decimal.Decimal` class. There are some useful " +"additions to the standard library, such as a greatly enhanced :mod:" +"`unittest` module, the :mod:`argparse` module for parsing command-line " +"options, convenient :class:`~collections.OrderedDict` and :class:" +"`~collections.Counter` classes in the :mod:`collections` module, and many " +"other improvements." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:63 +msgid "" +"Python 2.7 is planned to be the last of the 2.x releases, so we worked on " +"making it a good release for the long term. To help with porting to Python " +"3, several new features from the Python 3.x series have been included in 2.7." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:68 +msgid "" +"This article doesn't attempt to provide a complete specification of the new " +"features, but instead provides a convenient overview. For full details, you " +"should refer to the documentation for Python 2.7 at https://docs.python.org. " +"If you want to understand the rationale for the design and implementation, " +"refer to the PEP for a particular new feature or the issue on https://bugs." +"python.org in which a change was discussed. Whenever possible, \"What's New " +"in Python\" links to the bug/patch item for each change." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:80 +msgid "The Future for Python 2.x" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:82 +msgid "" +"Python 2.7 is the last major release in the 2.x series, as the Python " +"maintainers have shifted the focus of their new feature development efforts " +"to the Python 3.x series. This means that while Python 2 continues to " +"receive bug fixes, and to be updated to build correctly on new hardware and " +"versions of supported operated systems, there will be no new full feature " +"releases for the language or standard library." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:89 +msgid "" +"However, while there is a large common subset between Python 2.7 and Python " +"3, and many of the changes involved in migrating to that common subset, or " +"directly to Python 3, can be safely automated, some other changes (notably " +"those associated with Unicode handling) may require careful consideration, " +"and preferably robust automated regression test suites, to migrate " +"effectively." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:96 +msgid "" +"This means that Python 2.7 will remain in place for a long time, providing a " +"stable and supported base platform for production systems that have not yet " +"been ported to Python 3. The full expected lifecycle of the Python 2.7 " +"series is detailed in :pep:`373`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:101 +msgid "Some key consequences of the long-term significance of 2.7 are:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:103 +msgid "" +"As noted above, the 2.7 release has a much longer period of maintenance when " +"compared to earlier 2.x versions. Python 2.7 is currently expected to remain " +"supported by the core development team (receiving security updates and other " +"bug fixes) until at least 2020 (10 years after its initial release, compared " +"to the more typical support period of 18-24 months)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:109 +msgid "" +"As the Python 2.7 standard library ages, making effective use of the Python " +"Package Index (either directly or via a redistributor) becomes more " +"important for Python 2 users. In addition to a wide variety of third party " +"packages for various tasks, the available packages include backports of new " +"modules and features from the Python 3 standard library that are compatible " +"with Python 2, as well as various tools and libraries that can make it " +"easier to migrate to Python 3. The `Python Packaging User Guide `__ provides guidance on downloading and installing " +"software from the Python Package Index." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:119 +msgid "" +"While the preferred approach to enhancing Python 2 is now the publication of " +"new packages on the Python Package Index, this approach doesn't necessarily " +"work in all cases, especially those related to network security. In " +"exceptional cases that cannot be handled adequately by publishing new or " +"updated packages on PyPI, the Python Enhancement Proposal process may be " +"used to make the case for adding new features directly to the Python 2 " +"standard library. Any such additions, and the maintenance releases where " +"they were added, will be noted in the :ref:`py27-maintenance-enhancements` " +"section below." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:129 +msgid "" +"For projects wishing to migrate from Python 2 to Python 3, or for library " +"and framework developers wishing to support users on both Python 2 and " +"Python 3, there are a variety of tools and guides available to help decide " +"on a suitable approach and manage some of the technical details involved. " +"The recommended starting point is the :ref:`pyporting-howto` HOWTO guide." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:137 +msgid "Changes to the Handling of Deprecation Warnings" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:139 +msgid "" +"For Python 2.7, a policy decision was made to silence warnings only of " +"interest to developers by default. :exc:`DeprecationWarning` and its " +"descendants are now ignored unless otherwise requested, preventing users " +"from seeing warnings triggered by an application. This change was also made " +"in the branch that became Python 3.2. (Discussed on stdlib-sig and carried " +"out in :issue:`7319`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:146 +msgid "" +"In previous releases, :exc:`DeprecationWarning` messages were enabled by " +"default, providing Python developers with a clear indication of where their " +"code may break in a future major version of Python." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:151 +msgid "" +"However, there are increasingly many users of Python-based applications who " +"are not directly involved in the development of those applications. :exc:" +"`DeprecationWarning` messages are irrelevant to such users, making them " +"worry about an application that's actually working correctly and burdening " +"application developers with responding to these concerns." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:158 +msgid "" +"You can re-enable display of :exc:`DeprecationWarning` messages by running " +"Python with the :option:`-Wdefault <-W>` (short form: :option:`-Wd <-W>`) " +"switch, or by setting the :envvar:`PYTHONWARNINGS` environment variable to ``" +"\"default\"`` (or ``\"d\"``) before running Python. Python code can also re-" +"enable them by calling ``warnings.simplefilter('default')``." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:165 +msgid "" +"The ``unittest`` module also automatically reenables deprecation warnings " +"when running tests." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:170 +msgid "Python 3.1 Features" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:172 +msgid "" +"Much as Python 2.6 incorporated features from Python 3.0, version 2.7 " +"incorporates some of the new features in Python 3.1. The 2.x series " +"continues to provide tools for migrating to the 3.x series." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:177 +msgid "A partial list of 3.1 features that were backported to 2.7:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:179 +msgid "The syntax for set literals (``{1,2,3}`` is a mutable set)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:180 +msgid "Dictionary and set comprehensions (``{i: i*2 for i in range(3)}``)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:181 +msgid "Multiple context managers in a single :keyword:`with` statement." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:182 +msgid "A new version of the :mod:`io` library, rewritten in C for performance." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:183 +msgid "The ordered-dictionary type described in :ref:`pep-0372`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:184 +msgid "The new ``\",\"`` format specifier described in :ref:`pep-0378`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:185 +msgid "The :class:`memoryview` object." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:186 +msgid "" +"A small subset of the :mod:`importlib` module, `described below <#importlib-" +"section>`__." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:188 +msgid "" +"The :func:`repr` of a float ``x`` is shorter in many cases: it's now based " +"on the shortest decimal string that's guaranteed to round back to ``x``. As " +"in previous versions of Python, it's guaranteed that ``float(repr(x))`` " +"recovers ``x``." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:192 +msgid "" +"Float-to-string and string-to-float conversions are correctly rounded. The :" +"func:`round` function is also now correctly rounded." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:194 +msgid "" +"The :c:type:`PyCapsule` type, used to provide a C API for extension modules." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:195 +msgid "The :c:func:`PyLong_AsLongAndOverflow` C API function." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:197 +msgid "Other new Python3-mode warnings include:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:199 +msgid "" +":func:`operator.isCallable` and :func:`operator.sequenceIncludes`, which are " +"not supported in 3.x, now trigger warnings." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:201 +msgid "" +"The :option:`-3` switch now automatically enables the :option:`-Qwarn <-Q>` " +"switch that causes warnings about using classic division with integers and " +"long integers." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:214 +msgid "PEP 372: Adding an Ordered Dictionary to collections" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:216 +msgid "" +"Regular Python dictionaries iterate over key/value pairs in arbitrary order. " +"Over the years, a number of authors have written alternative implementations " +"that remember the order that the keys were originally inserted. Based on " +"the experiences from those implementations, 2.7 introduces a new :class:" +"`~collections.OrderedDict` class in the :mod:`collections` module." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:222 +msgid "" +"The :class:`~collections.OrderedDict` API provides the same interface as " +"regular dictionaries but iterates over keys and values in a guaranteed order " +"depending on when a key was first inserted::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:233 +msgid "" +"If a new entry overwrites an existing entry, the original insertion position " +"is left unchanged::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:240 +msgid "Deleting an entry and reinserting it will move it to the end::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:247 +msgid "" +"The :meth:`~collections.OrderedDict.popitem` method has an optional *last* " +"argument that defaults to True. If *last* is True, the most recently added " +"key is returned and removed; if it's False, the oldest key is selected::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:262 +msgid "" +"Comparing two ordered dictionaries checks both the keys and values, and " +"requires that the insertion order was the same::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:278 +msgid "" +"Comparing an :class:`~collections.OrderedDict` with a regular dictionary " +"ignores the insertion order and just compares the keys and values." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:281 +msgid "" +"How does the :class:`~collections.OrderedDict` work? It maintains a doubly-" +"linked list of keys, appending new keys to the list as they're inserted. A " +"secondary dictionary maps keys to their corresponding list node, so deletion " +"doesn't have to traverse the entire linked list and therefore remains O(1)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:287 +msgid "" +"The standard library now supports use of ordered dictionaries in several " +"modules." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:290 +msgid "" +"The :mod:`ConfigParser` module uses them by default, meaning that " +"configuration files can now be read, modified, and then written back in " +"their original order." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:294 +msgid "" +"The :meth:`~collections.somenamedtuple._asdict()` method for :func:" +"`collections.namedtuple` now returns an ordered dictionary with the values " +"appearing in the same order as the underlying tuple indices." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:298 +msgid "" +"The :mod:`json` module's :class:`~json.JSONDecoder` class constructor was " +"extended with an *object_pairs_hook* parameter to allow :class:`OrderedDict` " +"instances to be built by the decoder. Support was also added for third-party " +"tools like `PyYAML `_." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:307 +msgid ":pep:`372` - Adding an ordered dictionary to collections" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:307 +msgid "" +"PEP written by Armin Ronacher and Raymond Hettinger; implemented by Raymond " +"Hettinger." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:313 ../Doc/whatsnew/3.1.rst:84 +msgid "PEP 378: Format Specifier for Thousands Separator" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:315 +msgid "" +"To make program output more readable, it can be useful to add separators to " +"large numbers, rendering them as 18,446,744,073,709,551,616 instead of " +"18446744073709551616." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:319 +msgid "" +"The fully general solution for doing this is the :mod:`locale` module, which " +"can use different separators (\",\" in North America, \".\" in Europe) and " +"different grouping sizes, but :mod:`locale` is complicated to use and " +"unsuitable for multi-threaded applications where different threads are " +"producing output for different locales." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:325 +msgid "" +"Therefore, a simple comma-grouping mechanism has been added to the mini-" +"language used by the :meth:`str.format` method. When formatting a floating-" +"point number, simply include a comma between the width and the precision::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:333 +msgid "When formatting an integer, include the comma after the width:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:338 +msgid "" +"This mechanism is not adaptable at all; commas are always used as the " +"separator and the grouping is always into three-digit groups. The comma-" +"formatting mechanism isn't as general as the :mod:`locale` module, but it's " +"easier to use." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:345 ../Doc/whatsnew/3.1.rst:111 +msgid ":pep:`378` - Format Specifier for Thousands Separator" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:346 +msgid "PEP written by Raymond Hettinger; implemented by Eric Smith." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:349 +msgid "PEP 389: The argparse Module for Parsing Command Lines" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:351 +msgid "" +"The :mod:`argparse` module for parsing command-line arguments was added as a " +"more powerful replacement for the :mod:`optparse` module." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:355 +msgid "" +"This means Python now supports three different modules for parsing command-" +"line arguments: :mod:`getopt`, :mod:`optparse`, and :mod:`argparse`. The :" +"mod:`getopt` module closely resembles the C library's :c:func:`getopt` " +"function, so it remains useful if you're writing a Python prototype that " +"will eventually be rewritten in C. :mod:`optparse` becomes redundant, but " +"there are no plans to remove it because there are many scripts still using " +"it, and there's no automated way to update these scripts. (Making the :mod:" +"`argparse` API consistent with :mod:`optparse`'s interface was discussed but " +"rejected as too messy and difficult.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:366 +msgid "" +"In short, if you're writing a new script and don't need to worry about " +"compatibility with earlier versions of Python, use :mod:`argparse` instead " +"of :mod:`optparse`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:370 +msgid "Here's an example::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:393 +msgid "" +"Unless you override it, :option:`-h` and :option:`--help` switches are " +"automatically added, and produce neatly formatted output::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:410 +msgid "" +"As with :mod:`optparse`, the command-line switches and arguments are " +"returned as an object with attributes named by the *dest* parameters::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:425 +msgid "" +":mod:`argparse` has much fancier validation than :mod:`optparse`; you can " +"specify an exact number of arguments as an integer, 0 or more arguments by " +"passing ``'*'``, 1 or more by passing ``'+'``, or an optional argument with " +"``'?'``. A top-level parser can contain sub-parsers to define subcommands " +"that have different sets of switches, as in ``svn commit``, ``svn " +"checkout``, etc. You can specify an argument's type as :class:`~argparse." +"FileType`, which will automatically open files for you and understands that " +"``'-'`` means standard input or output." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:438 +msgid ":mod:`argparse` documentation" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:438 +msgid "The documentation page of the argparse module." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:442 +msgid ":ref:`upgrading-optparse-code`" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:441 +msgid "" +"Part of the Python documentation, describing how to convert code that uses :" +"mod:`optparse`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:444 +msgid ":pep:`389` - argparse - New Command Line Parsing Module" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:445 +msgid "PEP written and implemented by Steven Bethard." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:448 +msgid "PEP 391: Dictionary-Based Configuration For Logging" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:450 +msgid "" +"The :mod:`logging` module is very flexible; applications can define a tree " +"of logging subsystems, and each logger in this tree can filter out certain " +"messages, format them differently, and direct messages to a varying number " +"of handlers." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:455 +msgid "" +"All this flexibility can require a lot of configuration. You can write " +"Python statements to create objects and set their properties, but a complex " +"set-up requires verbose but boring code. :mod:`logging` also supports a :" +"func:`~logging.fileConfig` function that parses a file, but the file format " +"doesn't support configuring filters, and it's messier to generate " +"programmatically." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:462 +msgid "" +"Python 2.7 adds a :func:`~logging.dictConfig` function that uses a " +"dictionary to configure logging. There are many ways to produce a " +"dictionary from different sources: construct one with code; parse a file " +"containing JSON; or use a YAML parsing library if one is installed. For " +"more information see :ref:`logging-config-api`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:468 +msgid "" +"The following example configures two loggers, the root logger and a logger " +"named \"network\". Messages sent to the root logger will be sent to the " +"system log using the syslog protocol, and messages to the \"network\" logger " +"will be written to a :file:`network.log` file that will be rotated once the " +"log reaches 1MB." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:518 +msgid "" +"Three smaller enhancements to the :mod:`logging` module, all implemented by " +"Vinay Sajip, are:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:523 +msgid "" +"The :class:`~logging.handlers.SysLogHandler` class now supports syslogging " +"over TCP. The constructor has a *socktype* parameter giving the type of " +"socket to use, either :const:`socket.SOCK_DGRAM` for UDP or :const:`socket." +"SOCK_STREAM` for TCP. The default protocol remains UDP." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:529 +msgid "" +":class:`~logging.Logger` instances gained a :meth:`~logging.Logger.getChild` " +"method that retrieves a descendant logger using a relative path. For " +"example, once you retrieve a logger by doing ``log = getLogger('app')``, " +"calling ``log.getChild('network.listen')`` is equivalent to ``getLogger('app." +"network.listen')``." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:535 +msgid "" +"The :class:`~logging.LoggerAdapter` class gained an :meth:`~logging." +"LoggerAdapter.isEnabledFor` method that takes a *level* and returns whether " +"the underlying logger would process a message of that level of importance." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:544 +msgid ":pep:`391` - Dictionary-Based Configuration For Logging" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:545 +msgid "PEP written and implemented by Vinay Sajip." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:548 +msgid "PEP 3106: Dictionary Views" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:550 +msgid "" +"The dictionary methods :meth:`~dict.keys`, :meth:`~dict.values`, and :meth:" +"`~dict.items` are different in Python 3.x. They return an object called a :" +"dfn:`view` instead of a fully materialized list." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:554 +msgid "" +"It's not possible to change the return values of :meth:`~dict.keys`, :meth:" +"`~dict.values`, and :meth:`~dict.items` in Python 2.7 because too much code " +"would break. Instead the 3.x versions were added under the new names :meth:" +"`~dict.viewkeys`, :meth:`~dict.viewvalues`, and :meth:`~dict.viewitems`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:568 +msgid "" +"Views can be iterated over, but the key and item views also behave like " +"sets. The ``&`` operator performs intersection, and ``|`` performs a union::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:579 +msgid "" +"The view keeps track of the dictionary and its contents change as the " +"dictionary is modified::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:589 +msgid "" +"However, note that you can't add or remove keys while you're iterating over " +"the view::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:599 +msgid "" +"You can use the view methods in Python 2.x code, and the 2to3 converter will " +"change them to the standard :meth:`~dict.keys`, :meth:`~dict.values`, and :" +"meth:`~dict.items` methods." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:606 +msgid ":pep:`3106` - Revamping dict.keys(), .values() and .items()" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:606 +msgid "" +"PEP written by Guido van Rossum. Backported to 2.7 by Alexandre Vassalotti; :" +"issue:`1967`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:611 +msgid "PEP 3137: The memoryview Object" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:613 +msgid "" +"The :class:`memoryview` object provides a view of another object's memory " +"content that matches the :class:`bytes` type's interface." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:631 +msgid "" +"The content of the view can be converted to a string of bytes or a list of " +"integers:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:643 +msgid "" +":class:`memoryview` objects allow modifying the underlying object if it's a " +"mutable object." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:666 +msgid ":pep:`3137` - Immutable Bytes and Mutable Buffer" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:665 +msgid "" +"PEP written by Guido van Rossum. Implemented by Travis Oliphant, Antoine " +"Pitrou and others. Backported to 2.7 by Antoine Pitrou; :issue:`2396`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:676 +msgid "" +"The syntax for set literals has been backported from Python 3.x. Curly " +"brackets are used to surround the contents of the resulting mutable set; set " +"literals are distinguished from dictionaries by not containing colons and " +"values. ``{}`` continues to represent an empty dictionary; use ``set()`` for " +"an empty set." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:693 +msgid "Backported by Alexandre Vassalotti; :issue:`2335`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:695 +msgid "" +"Dictionary and set comprehensions are another feature backported from 3.x, " +"generalizing list/generator comprehensions to use the literal syntax for " +"sets and dictionaries." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:707 +msgid "Backported by Alexandre Vassalotti; :issue:`2333`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:709 +msgid "" +"The :keyword:`with` statement can now use multiple context managers in one " +"statement. Context managers are processed from left to right and each one " +"is treated as beginning a new :keyword:`with` statement. This means that::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:717 +msgid "is equivalent to::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:723 +msgid "" +"The :func:`contextlib.nested` function provides a very similar function, so " +"it's no longer necessary and has been deprecated." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:726 +msgid "" +"(Proposed in https://codereview.appspot.com/53094; implemented by Georg " +"Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:729 +msgid "" +"Conversions between floating-point numbers and strings are now correctly " +"rounded on most platforms. These conversions occur in many different " +"places: :func:`str` on floats and complex numbers; the :class:`float` and :" +"class:`complex` constructors; numeric formatting; serializing and " +"deserializing floats and complex numbers using the :mod:`marshal`, :mod:" +"`pickle` and :mod:`json` modules; parsing of float and imaginary literals in " +"Python code; and :class:`~decimal.Decimal`-to-float conversion." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:741 +msgid "" +"Related to this, the :func:`repr` of a floating-point number *x* now returns " +"a result based on the shortest decimal string that's guaranteed to round " +"back to *x* under correct rounding (with round-half-to-even rounding mode). " +"Previously it gave a string based on rounding x to 17 decimal digits." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:749 +msgid "" +"The rounding library responsible for this improvement works on Windows and " +"on Unix platforms using the gcc, icc, or suncc compilers. There may be a " +"small number of platforms where correct operation of this code cannot be " +"guaranteed, so the code is not used on such systems. You can find out which " +"code is being used by checking :data:`sys.float_repr_style`, which will be " +"``short`` if the new code is in use and ``legacy`` if it isn't." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:757 +msgid "" +"Implemented by Eric Smith and Mark Dickinson, using David Gay's :file:`dtoa." +"c` library; :issue:`7117`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:760 +msgid "" +"Conversions from long integers and regular integers to floating point now " +"round differently, returning the floating-point number closest to the " +"number. This doesn't matter for small integers that can be converted " +"exactly, but for large numbers that will unavoidably lose precision, Python " +"2.7 now approximates more closely. For example, Python 2.6 computed the " +"following::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:773 +msgid "" +"Python 2.7's floating-point result is larger, but much closer to the true " +"value::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:782 +msgid "(Implemented by Mark Dickinson; :issue:`3166`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:784 +msgid "" +"Integer division is also more accurate in its rounding behaviours. (Also " +"implemented by Mark Dickinson; :issue:`1811`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:787 +msgid "" +"Implicit coercion for complex numbers has been removed; the interpreter will " +"no longer ever attempt to call a :meth:`__coerce__` method on complex " +"objects. (Removed by Meador Inge and Mark Dickinson; :issue:`5211`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:791 +msgid "" +"The :meth:`str.format` method now supports automatic numbering of the " +"replacement fields. This makes using :meth:`str.format` more closely " +"resemble using ``%s`` formatting::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:800 +msgid "" +"The auto-numbering takes the fields from left to right, so the first ``{...}" +"`` specifier will use the first argument to :meth:`str.format`, the next " +"specifier will use the next argument, and so on. You can't mix auto-" +"numbering and explicit numbering -- either number all of your specifier " +"fields or none of them -- but you can mix auto-numbering and named fields, " +"as in the second example above. (Contributed by Eric Smith; :issue:`5237`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:807 +msgid "" +"Complex numbers now correctly support usage with :func:`format`, and default " +"to being right-aligned. Specifying a precision or comma-separation applies " +"to both the real and imaginary parts of the number, but a specified field " +"width and alignment is applied to the whole of the resulting ``1.5+3j`` " +"output. (Contributed by Eric Smith; :issue:`1588` and :issue:`7988`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:814 +msgid "" +"The 'F' format code now always formats its output using uppercase " +"characters, so it will now produce 'INF' and 'NAN'. (Contributed by Eric " +"Smith; :issue:`3382`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:818 +msgid "" +"A low-level change: the :meth:`object.__format__` method now triggers a :exc:" +"`PendingDeprecationWarning` if it's passed a format string, because the :" +"meth:`__format__` method for :class:`object` converts the object to a string " +"representation and formats that. Previously the method silently applied the " +"format string to the string representation, but that could hide mistakes in " +"Python code. If you're supplying formatting information such as an " +"alignment or precision, presumably you're expecting the formatting to be " +"applied in some object-specific way. (Fixed by Eric Smith; :issue:`7994`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:828 +msgid "" +"The :func:`int` and :func:`long` types gained a ``bit_length`` method that " +"returns the number of bits necessary to represent its argument in binary::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:843 +msgid "(Contributed by Fredrik Johansson and Victor Stinner; :issue:`3439`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:845 +msgid "" +"The :keyword:`import` statement will no longer try an absolute import if a " +"relative import (e.g. ``from .os import sep``) fails. This fixes a bug, but " +"could possibly break certain :keyword:`import` statements that were only " +"working by accident. (Fixed by Meador Inge; :issue:`7902`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:851 +msgid "" +"It's now possible for a subclass of the built-in :class:`unicode` type to " +"override the :meth:`__unicode__` method. (Implemented by Victor Stinner; :" +"issue:`1583863`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:855 +msgid "" +"The :class:`bytearray` type's :meth:`~bytearray.translate` method now " +"accepts ``None`` as its first argument. (Fixed by Georg Brandl; :issue:" +"`4759`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:861 +msgid "" +"When using ``@classmethod`` and ``@staticmethod`` to wrap methods as class " +"or static methods, the wrapper object now exposes the wrapped function as " +"their :attr:`__func__` attribute. (Contributed by Amaury Forgeot d'Arc, " +"after a suggestion by George Sakkis; :issue:`5982`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:867 ../Doc/whatsnew/2.7.rst:2450 +msgid "" +"When a restricted set of attributes were set using ``__slots__``, deleting " +"an unset attribute would not raise :exc:`AttributeError` as you would " +"expect. Fixed by Benjamin Peterson; :issue:`7604`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:871 +msgid "" +"Two new encodings are now supported: \"cp720\", used primarily for Arabic " +"text; and \"cp858\", a variant of CP 850 that adds the euro symbol. (CP720 " +"contributed by Alexander Belchenko and Amaury Forgeot d'Arc in :issue:" +"`1616979`; CP858 contributed by Tim Hatch in :issue:`8016`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:877 +msgid "" +"The :class:`file` object will now set the :attr:`filename` attribute on the :" +"exc:`IOError` exception when trying to open a directory on POSIX platforms " +"(noted by Jan Kaliszewski; :issue:`4764`), and now explicitly checks for and " +"forbids writing to read-only file objects instead of trusting the C library " +"to catch and report the error (fixed by Stefan Krah; :issue:`5677`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:884 +msgid "" +"The Python tokenizer now translates line endings itself, so the :func:" +"`compile` built-in function now accepts code using any line-ending " +"convention. Additionally, it no longer requires that the code end in a " +"newline." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:889 +msgid "" +"Extra parentheses in function definitions are illegal in Python 3.x, meaning " +"that you get a syntax error from ``def f((x)): pass``. In Python3-warning " +"mode, Python 2.7 will now warn about this odd usage. (Noted by James " +"Lingard; :issue:`7362`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:894 +msgid "" +"It's now possible to create weak references to old-style class objects. New-" +"style classes were always weak-referenceable. (Fixed by Antoine Pitrou; :" +"issue:`8268`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:898 +msgid "" +"When a module object is garbage-collected, the module's dictionary is now " +"only cleared if no one else is holding a reference to the dictionary (:issue:" +"`7140`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:909 +msgid "" +"A new environment variable, :envvar:`PYTHONWARNINGS`, allows controlling " +"warnings. It should be set to a string containing warning settings, " +"equivalent to those used with the :option:`-W` switch, separated by commas. " +"(Contributed by Brian Curtin; :issue:`7301`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:915 +msgid "" +"For example, the following setting will print warnings every time they " +"occur, but turn warnings from the :mod:`Cookie` module into an error. (The " +"exact syntax for setting an environment variable varies across operating " +"systems and shells.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:930 +msgid "Several performance enhancements have been added:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:932 +msgid "" +"A new opcode was added to perform the initial setup for :keyword:`with` " +"statements, looking up the :meth:`__enter__` and :meth:`__exit__` methods. " +"(Contributed by Benjamin Peterson.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:936 +msgid "" +"The garbage collector now performs better for one common usage pattern: when " +"many objects are being allocated without deallocating any of them. This " +"would previously take quadratic time for garbage collection, but now the " +"number of full garbage collections is reduced as the number of objects on " +"the heap grows. The new logic only performs a full garbage collection pass " +"when the middle generation has been collected 10 times and when the number " +"of survivor objects from the middle generation exceeds 10% of the number of " +"objects in the oldest generation. (Suggested by Martin von Löwis and " +"implemented by Antoine Pitrou; :issue:`4074`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:947 +msgid "" +"The garbage collector tries to avoid tracking simple containers which can't " +"be part of a cycle. In Python 2.7, this is now true for tuples and dicts " +"containing atomic types (such as ints, strings, etc.). Transitively, a dict " +"containing tuples of atomic types won't be tracked either. This helps reduce " +"the cost of each garbage collection by decreasing the number of objects to " +"be considered and traversed by the collector. (Contributed by Antoine " +"Pitrou; :issue:`4688`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:956 +msgid "" +"Long integers are now stored internally either in base 2**15 or in base " +"2**30, the base being determined at build time. Previously, they were " +"always stored in base 2**15. Using base 2**30 gives significant performance " +"improvements on 64-bit machines, but benchmark results on 32-bit machines " +"have been mixed. Therefore, the default is to use base 2**30 on 64-bit " +"machines and base 2**15 on 32-bit machines; on Unix, there's a new configure " +"option :option:`--enable-big-digits` that can be used to override this " +"default." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:965 +msgid "" +"Apart from the performance improvements this change should be invisible to " +"end users, with one exception: for testing and debugging purposes there's a " +"new structseq :data:`sys.long_info` that provides information about the " +"internal format, giving the number of bits per digit and the size in bytes " +"of the C type used to store each digit::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:976 ../Doc/whatsnew/3.1.rst:496 +msgid "(Contributed by Mark Dickinson; :issue:`4258`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:978 +msgid "" +"Another set of changes made long objects a few bytes smaller: 2 bytes " +"smaller on 32-bit systems and 6 bytes on 64-bit. (Contributed by Mark " +"Dickinson; :issue:`5260`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:982 +msgid "" +"The division algorithm for long integers has been made faster by tightening " +"the inner loop, doing shifts instead of multiplications, and fixing an " +"unnecessary extra iteration. Various benchmarks show speedups of between 50% " +"and 150% for long integer divisions and modulo operations. (Contributed by " +"Mark Dickinson; :issue:`5512`.) Bitwise operations are also significantly " +"faster (initial patch by Gregory Smith; :issue:`1087418`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:991 +msgid "" +"The implementation of ``%`` checks for the left-side operand being a Python " +"string and special-cases it; this results in a 1-3% performance increase for " +"applications that frequently use ``%`` with strings, such as templating " +"libraries. (Implemented by Collin Winter; :issue:`5176`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:997 +msgid "" +"List comprehensions with an ``if`` condition are compiled into faster " +"bytecode. (Patch by Antoine Pitrou, back-ported to 2.7 by Jeffrey Yasskin; :" +"issue:`4715`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1001 +msgid "" +"Converting an integer or long integer to a decimal string was made faster by " +"special-casing base 10 instead of using a generalized conversion function " +"that supports arbitrary bases. (Patch by Gawain Bolton; :issue:`6713`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1006 +msgid "" +"The :meth:`split`, :meth:`replace`, :meth:`rindex`, :meth:`rpartition`, and :" +"meth:`rsplit` methods of string-like types (strings, Unicode strings, and :" +"class:`bytearray` objects) now use a fast reverse-search algorithm instead " +"of a character-by-character scan. This is sometimes faster by a factor of " +"10. (Added by Florent Xicluna; :issue:`7462` and :issue:`7622`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1013 +msgid "" +"The :mod:`pickle` and :mod:`cPickle` modules now automatically intern the " +"strings used for attribute names, reducing memory usage of the objects " +"resulting from unpickling. (Contributed by Jake McGuire; :issue:`5084`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1018 +msgid "" +"The :mod:`cPickle` module now special-cases dictionaries, nearly halving the " +"time required to pickle them. (Contributed by Collin Winter; :issue:`5670`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1033 +msgid "" +"The :mod:`bdb` module's base debugging class :class:`~bdb.Bdb` gained a " +"feature for skipping modules. The constructor now takes an iterable " +"containing glob-style patterns such as ``django.*``; the debugger will not " +"step into stack frames from a module that matches one of these patterns. " +"(Contributed by Maru Newby after a suggestion by Senthil Kumaran; :issue:" +"`5142`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1041 +msgid "" +"The :mod:`binascii` module now supports the buffer API, so it can be used " +"with :class:`memoryview` instances and other similar buffer objects. " +"(Backported from 3.x by Florent Xicluna; :issue:`7703`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1045 +msgid "" +"Updated module: the :mod:`bsddb` module has been updated from 4.7.2devel9 to " +"version 4.8.4 of `the pybsddb package `__. The new version features better Python 3.x compatibility, " +"various bug fixes, and adds several new BerkeleyDB flags and methods. " +"(Updated by Jesús Cea Avión; :issue:`8156`. The pybsddb changelog can be " +"read at http://hg.jcea.es/pybsddb/file/tip/ChangeLog.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1053 +msgid "" +"The :mod:`bz2` module's :class:`~bz2.BZ2File` now supports the context " +"management protocol, so you can write ``with bz2.BZ2File(...) as f:``. " +"(Contributed by Hagen Fürstenau; :issue:`3860`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1057 +msgid "" +"New class: the :class:`~collections.Counter` class in the :mod:`collections` " +"module is useful for tallying data. :class:`~collections.Counter` instances " +"behave mostly like dictionaries but return zero for missing keys instead of " +"raising a :exc:`KeyError`:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1079 +msgid "" +"There are three additional :class:`~collections.Counter` methods. :meth:" +"`~collections.Counter.most_common` returns the N most common elements and " +"their counts. :meth:`~collections.Counter.elements` returns an iterator " +"over the contained elements, repeating each element as many times as its " +"count. :meth:`~collections.Counter.subtract` takes an iterable and subtracts " +"one for each element instead of adding; if the argument is a dictionary or " +"another :class:`Counter`, the counts are subtracted. ::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1102 +msgid "Contributed by Raymond Hettinger; :issue:`1696199`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1106 +msgid "" +"New class: :class:`~collections.OrderedDict` is described in the earlier " +"section :ref:`pep-0372`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1109 +msgid "" +"New method: The :class:`~collections.deque` data type now has a :meth:" +"`~collections.deque.count` method that returns the number of contained " +"elements equal to the supplied argument *x*, and a :meth:`~collections.deque." +"reverse` method that reverses the elements of the deque in-place. :class:" +"`~collections.deque` also exposes its maximum length as the read-only :attr:" +"`~collections.deque.maxlen` attribute. (Both features added by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1117 +msgid "" +"The :class:`~collections.namedtuple` class now has an optional *rename* " +"parameter. If *rename* is true, field names that are invalid because they've " +"been repeated or aren't legal Python identifiers will be renamed to legal " +"names that are derived from the field's position within the list of fields:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1128 +msgid "(Added by Raymond Hettinger; :issue:`1818`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1130 +msgid "" +"Finally, the :class:`~collections.Mapping` abstract base class now returns :" +"const:`NotImplemented` if a mapping is compared to another type that isn't " +"a :class:`Mapping`. (Fixed by Daniel Stutzbach; :issue:`8729`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1135 +msgid "" +"Constructors for the parsing classes in the :mod:`ConfigParser` module now " +"take an *allow_no_value* parameter, defaulting to false; if true, options " +"without values will be allowed. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1157 +msgid "(Contributed by Mats Kindahl; :issue:`7005`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1159 +msgid "" +"Deprecated function: :func:`contextlib.nested`, which allows handling more " +"than one context manager with a single :keyword:`with` statement, has been " +"deprecated, because the :keyword:`with` statement now supports multiple " +"context managers." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1164 +msgid "" +"The :mod:`cookielib` module now ignores cookies that have an invalid version " +"field, one that doesn't contain an integer value. (Fixed by John J. Lee; :" +"issue:`3924`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1168 +msgid "" +"The :mod:`copy` module's :func:`~copy.deepcopy` function will now correctly " +"copy bound instance methods. (Implemented by Robert Collins; :issue:`1515`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1172 +msgid "" +"The :mod:`ctypes` module now always converts ``None`` to a C NULL pointer " +"for arguments declared as pointers. (Changed by Thomas Heller; :issue:" +"`4606`.) The underlying `libffi library `__ " +"has been updated to version 3.0.9, containing various fixes for different " +"platforms. (Updated by Matthias Klose; :issue:`8142`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1179 +msgid "" +"New method: the :mod:`datetime` module's :class:`~datetime.timedelta` class " +"gained a :meth:`~datetime.timedelta.total_seconds` method that returns the " +"number of seconds in the duration. (Contributed by Brian Quinlan; :issue:" +"`5788`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1183 +msgid "" +"New method: the :class:`~decimal.Decimal` class gained a :meth:`~decimal." +"Decimal.from_float` class method that performs an exact conversion of a " +"floating-point number to a :class:`~decimal.Decimal`. This exact conversion " +"strives for the closest decimal approximation to the floating-point " +"representation's value; the resulting decimal value will therefore still " +"include the inaccuracy, if any. For example, ``Decimal.from_float(0.1)`` " +"returns " +"``Decimal('0.1000000000000000055511151231257827021181583404541015625')``. " +"(Implemented by Raymond Hettinger; :issue:`4796`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1194 +msgid "" +"Comparing instances of :class:`~decimal.Decimal` with floating-point numbers " +"now produces sensible results based on the numeric values of the operands. " +"Previously such comparisons would fall back to Python's default rules for " +"comparing objects, which produced arbitrary results based on their type. " +"Note that you still cannot combine :class:`Decimal` and floating-point in " +"other operations such as addition, since you should be explicitly choosing " +"how to convert between float and :class:`~decimal.Decimal`. (Fixed by Mark " +"Dickinson; :issue:`2531`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1203 +msgid "" +"The constructor for :class:`~decimal.Decimal` now accepts floating-point " +"numbers (added by Raymond Hettinger; :issue:`8257`) and non-European Unicode " +"characters such as Arabic-Indic digits (contributed by Mark Dickinson; :" +"issue:`6595`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1208 +msgid "" +"Most of the methods of the :class:`~decimal.Context` class now accept " +"integers as well as :class:`~decimal.Decimal` instances; the only exceptions " +"are the :meth:`~decimal.Context.canonical` and :meth:`~decimal.Context." +"is_canonical` methods. (Patch by Juan José Conti; :issue:`7633`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1213 +msgid "" +"When using :class:`~decimal.Decimal` instances with a string's :meth:`~str." +"format` method, the default alignment was previously left-alignment. This " +"has been changed to right-alignment, which is more sensible for numeric " +"types. (Changed by Mark Dickinson; :issue:`6857`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1218 +msgid "" +"Comparisons involving a signaling NaN value (or ``sNAN``) now signal :const:" +"`InvalidOperation` instead of silently returning a true or false value " +"depending on the comparison operator. Quiet NaN values (or ``NaN``) are now " +"hashable. (Fixed by Mark Dickinson; :issue:`7279`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1224 +msgid "" +"The :mod:`difflib` module now produces output that is more compatible with " +"modern :command:`diff`/:command:`patch` tools through one small change, " +"using a tab character instead of spaces as a separator in the header giving " +"the filename. (Fixed by Anatoly Techtonik; :issue:`7585`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1230 +msgid "" +"The Distutils ``sdist`` command now always regenerates the :file:`MANIFEST` " +"file, since even if the :file:`MANIFEST.in` or :file:`setup.py` files " +"haven't been modified, the user might have created some new files that " +"should be included. (Fixed by Tarek Ziadé; :issue:`8688`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1236 +msgid "" +"The :mod:`doctest` module's :const:`IGNORE_EXCEPTION_DETAIL` flag will now " +"ignore the name of the module containing the exception being tested. (Patch " +"by Lennart Regebro; :issue:`7490`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1240 +msgid "" +"The :mod:`email` module's :class:`~email.message.Message` class will now " +"accept a Unicode-valued payload, automatically converting the payload to the " +"encoding specified by :attr:`output_charset`. (Added by R. David Murray; :" +"issue:`1368247`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1245 +msgid "" +"The :class:`~fractions.Fraction` class now accepts a single float or :class:" +"`~decimal.Decimal` instance, or two rational numbers, as arguments to its " +"constructor. (Implemented by Mark Dickinson; rationals added in :issue:" +"`5812`, and float/decimal in :issue:`8294`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1251 +msgid "" +"Ordering comparisons (``<``, ``<=``, ``>``, ``>=``) between fractions and " +"complex numbers now raise a :exc:`TypeError`. This fixes an oversight, " +"making the :class:`~fractions.Fraction` match the other numeric types." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1258 +msgid "" +"New class: :class:`~ftplib.FTP_TLS` in the :mod:`ftplib` module provides " +"secure FTP connections using TLS encapsulation of authentication as well as " +"subsequent control and data transfers. (Contributed by Giampaolo Rodola; :" +"issue:`2054`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1264 +msgid "" +"The :meth:`~ftplib.FTP.storbinary` method for binary uploads can now restart " +"uploads thanks to an added *rest* parameter (patch by Pablo Mouzo; :issue:" +"`6845`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1268 +msgid "" +"New class decorator: :func:`~functools.total_ordering` in the :mod:" +"`functools` module takes a class that defines an :meth:`__eq__` method and " +"one of :meth:`__lt__`, :meth:`__le__`, :meth:`__gt__`, or :meth:`__ge__`, " +"and generates the missing comparison methods. Since the :meth:`__cmp__` " +"method is being deprecated in Python 3.x, this decorator makes it easier to " +"define ordered classes. (Added by Raymond Hettinger; :issue:`5479`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1276 +msgid "" +"New function: :func:`~functools.cmp_to_key` will take an old-style " +"comparison function that expects two arguments and return a new callable " +"that can be used as the *key* parameter to functions such as :func:" +"`sorted`, :func:`min` and :func:`max`, etc. The primary intended use is to " +"help with making code compatible with Python 3.x. (Added by Raymond " +"Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1283 +msgid "" +"New function: the :mod:`gc` module's :func:`~gc.is_tracked` returns true if " +"a given instance is tracked by the garbage collector, false otherwise. " +"(Contributed by Antoine Pitrou; :issue:`4688`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1287 +msgid "" +"The :mod:`gzip` module's :class:`~gzip.GzipFile` now supports the context " +"management protocol, so you can write ``with gzip.GzipFile(...) as f:`` " +"(contributed by Hagen Fürstenau; :issue:`3860`), and it now implements the :" +"class:`io.BufferedIOBase` ABC, so you can wrap it with :class:`io." +"BufferedReader` for faster processing (contributed by Nir Aides; :issue:" +"`7471`). It's also now possible to override the modification time recorded " +"in a gzipped file by providing an optional timestamp to the constructor. " +"(Contributed by Jacques Frechet; :issue:`4272`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1297 +msgid "" +"Files in gzip format can be padded with trailing zero bytes; the :mod:`gzip` " +"module will now consume these trailing bytes. (Fixed by Tadek Pietraszek " +"and Brian Curtin; :issue:`2846`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1301 +msgid "" +"New attribute: the :mod:`hashlib` module now has an :attr:`~hashlib.hashlib." +"algorithms` attribute containing a tuple naming the supported algorithms. In " +"Python 2.7, ``hashlib.algorithms`` contains ``('md5', 'sha1', 'sha224', " +"'sha256', 'sha384', 'sha512')``. (Contributed by Carl Chenet; :issue:`7418`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1307 +msgid "" +"The default :class:`~httplib.HTTPResponse` class used by the :mod:`httplib` " +"module now supports buffering, resulting in much faster reading of HTTP " +"responses. (Contributed by Kristján Valur Jónsson; :issue:`4879`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1311 +msgid "" +"The :class:`~httplib.HTTPConnection` and :class:`~httplib.HTTPSConnection` " +"classes now support a *source_address* parameter, a ``(host, port)`` 2-tuple " +"giving the source address that will be used for the connection. (Contributed " +"by Eldon Ziegler; :issue:`3972`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1316 +msgid "" +"The :mod:`ihooks` module now supports relative imports. Note that :mod:" +"`ihooks` is an older module for customizing imports, superseded by the :mod:" +"`imputil` module added in Python 2.0. (Relative import support added by Neil " +"Schemenauer.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1323 +msgid "" +"The :mod:`imaplib` module now supports IPv6 addresses. (Contributed by Derek " +"Morr; :issue:`1655`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1326 +msgid "" +"New function: the :mod:`inspect` module's :func:`~inspect.getcallargs` takes " +"a callable and its positional and keyword arguments, and figures out which " +"of the callable's parameters will receive each argument, returning a " +"dictionary mapping argument names to their values. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1343 +msgid "Contributed by George Sakkis; :issue:`3135`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1345 +msgid "" +"Updated module: The :mod:`io` library has been upgraded to the version " +"shipped with Python 3.1. For 3.1, the I/O library was entirely rewritten in " +"C and is 2 to 20 times faster depending on the task being performed. The " +"original Python version was renamed to the :mod:`_pyio` module." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1350 +msgid "" +"One minor resulting change: the :class:`io.TextIOBase` class now has an :" +"attr:`errors` attribute giving the error setting used for encoding and " +"decoding errors (one of ``'strict'``, ``'replace'``, ``'ignore'``)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1355 +msgid "" +"The :class:`io.FileIO` class now raises an :exc:`OSError` when passed an " +"invalid file descriptor. (Implemented by Benjamin Peterson; :issue:" +"`4991`.) The :meth:`~io.IOBase.truncate` method now preserves the file " +"position; previously it would change the file position to the end of the new " +"file. (Fixed by Pascal Chambon; :issue:`6939`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1361 +msgid "" +"New function: ``itertools.compress(data, selectors)`` takes two iterators. " +"Elements of *data* are returned if the corresponding value in *selectors* is " +"true::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1370 +msgid "" +"New function: ``itertools.combinations_with_replacement(iter, r)`` returns " +"all the possible *r*-length combinations of elements from the iterable " +"*iter*. Unlike :func:`~itertools.combinations`, individual elements can be " +"repeated in the generated combinations::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1379 +msgid "" +"Note that elements are treated as unique depending on their position in the " +"input, not their actual values." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1382 +msgid "" +"The :func:`itertools.count` function now has a *step* argument that allows " +"incrementing by values other than 1. :func:`~itertools.count` also now " +"allows keyword arguments, and using non-integer values such as floats or :" +"class:`~decimal.Decimal` instances. (Implemented by Raymond Hettinger; :" +"issue:`5032`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1388 +msgid "" +":func:`itertools.combinations` and :func:`itertools.product` previously " +"raised :exc:`ValueError` for values of *r* larger than the input iterable. " +"This was deemed a specification error, so they now return an empty " +"iterator. (Fixed by Raymond Hettinger; :issue:`4816`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1393 +msgid "" +"Updated module: The :mod:`json` module was upgraded to version 2.0.9 of the " +"simplejson package, which includes a C extension that makes encoding and " +"decoding faster. (Contributed by Bob Ippolito; :issue:`4136`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1398 +msgid "" +"To support the new :class:`collections.OrderedDict` type, :func:`json.load` " +"now has an optional *object_pairs_hook* parameter that will be called with " +"any object literal that decodes to a list of pairs. (Contributed by Raymond " +"Hettinger; :issue:`5381`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1403 +msgid "" +"The :mod:`mailbox` module's :class:`~mailbox.Maildir` class now records the " +"timestamp on the directories it reads, and only re-reads them if the " +"modification time has subsequently changed. This improves performance by " +"avoiding unneeded directory scans. (Fixed by A.M. Kuchling and Antoine " +"Pitrou; :issue:`1607951`, :issue:`6896`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1409 +msgid "" +"New functions: the :mod:`math` module gained :func:`~math.erf` and :func:" +"`~math.erfc` for the error function and the complementary error function, :" +"func:`~math.expm1` which computes ``e**x - 1`` with more precision than " +"using :func:`~math.exp` and subtracting 1, :func:`~math.gamma` for the Gamma " +"function, and :func:`~math.lgamma` for the natural log of the Gamma " +"function. (Contributed by Mark Dickinson and nirinA raseliarison; :issue:" +"`3366`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1417 +msgid "" +"The :mod:`multiprocessing` module's :class:`Manager*` classes can now be " +"passed a callable that will be called whenever a subprocess is started, " +"along with a set of arguments that will be passed to the callable. " +"(Contributed by lekma; :issue:`5585`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1423 +msgid "" +"The :class:`~multiprocessing.Pool` class, which controls a pool of worker " +"processes, now has an optional *maxtasksperchild* parameter. Worker " +"processes will perform the specified number of tasks and then exit, causing " +"the :class:`~multiprocessing.Pool` to start a new worker. This is useful if " +"tasks may leak memory or other resources, or if some tasks will cause the " +"worker to become very large. (Contributed by Charles Cazabon; :issue:`6963`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1431 +msgid "" +"The :mod:`nntplib` module now supports IPv6 addresses. (Contributed by Derek " +"Morr; :issue:`1664`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1434 +msgid "" +"New functions: the :mod:`os` module wraps the following POSIX system calls: :" +"func:`~os.getresgid` and :func:`~os.getresuid`, which return the real, " +"effective, and saved GIDs and UIDs; :func:`~os.setresgid` and :func:`~os." +"setresuid`, which set real, effective, and saved GIDs and UIDs to new " +"values; :func:`~os.initgroups`, which initialize the group access list for " +"the current process. (GID/UID functions contributed by Travis H.; :issue:" +"`6508`. Support for initgroups added by Jean-Paul Calderone; :issue:`7333`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1444 +msgid "" +"The :func:`os.fork` function now re-initializes the import lock in the child " +"process; this fixes problems on Solaris when :func:`~os.fork` is called from " +"a thread. (Fixed by Zsolt Cserna; :issue:`7242`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1448 +msgid "" +"In the :mod:`os.path` module, the :func:`~os.path.normpath` and :func:`~os." +"path.abspath` functions now preserve Unicode; if their input path is a " +"Unicode string, the return value is also a Unicode string. (:meth:`~os.path." +"normpath` fixed by Matt Giuca in :issue:`5827`; :meth:`~os.path.abspath` " +"fixed by Ezio Melotti in :issue:`3426`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1454 +msgid "" +"The :mod:`pydoc` module now has help for the various symbols that Python " +"uses. You can now do ``help('<<')`` or ``help('@')``, for example. " +"(Contributed by David Laban; :issue:`4739`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1458 +msgid "" +"The :mod:`re` module's :func:`~re.split`, :func:`~re.sub`, and :func:`~re." +"subn` now accept an optional *flags* argument, for consistency with the " +"other functions in the module. (Added by Gregory P. Smith.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1462 +msgid "" +"New function: :func:`~runpy.run_path` in the :mod:`runpy` module will " +"execute the code at a provided *path* argument. *path* can be the path of a " +"Python source file (:file:`example.py`), a compiled bytecode file (:file:" +"`example.pyc`), a directory (:file:`./package/`), or a zip archive (:file:" +"`example.zip`). If a directory or zip path is provided, it will be added to " +"the front of ``sys.path`` and the module :mod:`__main__` will be imported. " +"It's expected that the directory or zip contains a :file:`__main__.py`; if " +"it doesn't, some other :file:`__main__.py` might be imported from a location " +"later in ``sys.path``. This makes more of the machinery of :mod:`runpy` " +"available to scripts that want to mimic the way Python's command line " +"processes an explicit path name. (Added by Nick Coghlan; :issue:`6816`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1476 +msgid "" +"New function: in the :mod:`shutil` module, :func:`~shutil.make_archive` " +"takes a filename, archive type (zip or tar-format), and a directory path, " +"and creates an archive containing the directory's contents. (Added by Tarek " +"Ziadé.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1481 +msgid "" +":mod:`shutil`'s :func:`~shutil.copyfile` and :func:`~shutil.copytree` " +"functions now raise a :exc:`~shutil.SpecialFileError` exception when asked " +"to copy a named pipe. Previously the code would treat named pipes like a " +"regular file by opening them for reading, and this would block " +"indefinitely. (Fixed by Antoine Pitrou; :issue:`3002`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1487 +msgid "" +"The :mod:`signal` module no longer re-installs the signal handler unless " +"this is truly necessary, which fixes a bug that could make it impossible to " +"catch the EINTR signal robustly. (Fixed by Charles-Francois Natali; :issue:" +"`8354`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1492 +msgid "" +"New functions: in the :mod:`site` module, three new functions return various " +"site- and user-specific paths. :func:`~site.getsitepackages` returns a list " +"containing all global site-packages directories, :func:`~site." +"getusersitepackages` returns the path of the user's site-packages directory, " +"and :func:`~site.getuserbase` returns the value of the :envvar:`USER_BASE` " +"environment variable, giving the path to a directory that can be used to " +"store data. (Contributed by Tarek Ziadé; :issue:`6693`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1503 +msgid "" +"The :mod:`site` module now reports exceptions occurring when the :mod:" +"`sitecustomize` module is imported, and will no longer catch and swallow " +"the :exc:`KeyboardInterrupt` exception. (Fixed by Victor Stinner; :issue:" +"`3137`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1508 +msgid "" +"The :func:`~socket.create_connection` function gained a *source_address* " +"parameter, a ``(host, port)`` 2-tuple giving the source address that will be " +"used for the connection. (Contributed by Eldon Ziegler; :issue:`3972`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1513 +msgid "" +"The :meth:`~socket.socket.recv_into` and :meth:`~socket.socket." +"recvfrom_into` methods will now write into objects that support the buffer " +"API, most usefully the :class:`bytearray` and :class:`memoryview` objects. " +"(Implemented by Antoine Pitrou; :issue:`8104`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1518 +msgid "" +"The :mod:`SocketServer` module's :class:`~SocketServer.TCPServer` class now " +"supports socket timeouts and disabling the Nagle algorithm. The :attr:" +"`~SocketServer.TCPServer.disable_nagle_algorithm` class attribute defaults " +"to False; if overridden to be True, new request connections will have the " +"TCP_NODELAY option set to prevent buffering many small sends into a single " +"TCP packet. The :attr:`~SocketServer.BaseServer.timeout` class attribute can " +"hold a timeout in seconds that will be applied to the request socket; if no " +"request is received within that time, :meth:`~SocketServer.BaseServer." +"handle_timeout` will be called and :meth:`~SocketServer.BaseServer." +"handle_request` will return. (Contributed by Kristján Valur Jónsson; :issue:" +"`6192` and :issue:`6267`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1530 +msgid "" +"Updated module: the :mod:`sqlite3` module has been updated to version 2.6.0 " +"of the `pysqlite package `__. Version " +"2.6.0 includes a number of bugfixes, and adds the ability to load SQLite " +"extensions from shared libraries. Call the ``enable_load_extension(True)`` " +"method to enable extensions, and then call :meth:`~sqlite3.Connection." +"load_extension` to load a particular shared library. (Updated by Gerhard " +"Häring.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1537 +msgid "" +"The :mod:`ssl` module's :class:`~ssl.SSLSocket` objects now support the " +"buffer API, which fixed a test suite failure (fix by Antoine Pitrou; :issue:" +"`7133`) and automatically set OpenSSL's :c:macro:`SSL_MODE_AUTO_RETRY`, " +"which will prevent an error code being returned from :meth:`recv` operations " +"that trigger an SSL renegotiation (fix by Antoine Pitrou; :issue:`8222`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1544 +msgid "" +"The :func:`ssl.wrap_socket` constructor function now takes a *ciphers* " +"argument that's a string listing the encryption algorithms to be allowed; " +"the format of the string is described `in the OpenSSL documentation `__. (Added by " +"Antoine Pitrou; :issue:`8322`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1551 +msgid "" +"Another change makes the extension load all of OpenSSL's ciphers and digest " +"algorithms so that they're all available. Some SSL certificates couldn't be " +"verified, reporting an \"unknown algorithm\" error. (Reported by Beda " +"Kosata, and fixed by Antoine Pitrou; :issue:`8484`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1557 +msgid "" +"The version of OpenSSL being used is now available as the module attributes :" +"data:`ssl.OPENSSL_VERSION` (a string), :data:`ssl.OPENSSL_VERSION_INFO` (a 5-" +"tuple), and :data:`ssl.OPENSSL_VERSION_NUMBER` (an integer). (Added by " +"Antoine Pitrou; :issue:`8321`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1563 +msgid "" +"The :mod:`struct` module will no longer silently ignore overflow errors when " +"a value is too large for a particular integer format code (one of " +"``bBhHiIlLqQ``); it now always raises a :exc:`struct.error` exception. " +"(Changed by Mark Dickinson; :issue:`1523`.) The :func:`~struct.pack` " +"function will also attempt to use :meth:`__index__` to convert and pack non-" +"integers before trying the :meth:`__int__` method or reporting an error. " +"(Changed by Mark Dickinson; :issue:`8300`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1572 +msgid "" +"New function: the :mod:`subprocess` module's :func:`~subprocess." +"check_output` runs a command with a specified set of arguments and returns " +"the command's output as a string when the command runs without error, or " +"raises a :exc:`~subprocess.CalledProcessError` exception otherwise." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1587 +msgid "(Contributed by Gregory P. Smith.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1589 +msgid "" +"The :mod:`subprocess` module will now retry its internal system calls on " +"receiving an :const:`EINTR` signal. (Reported by several people; final " +"patch by Gregory P. Smith in :issue:`1068268`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1593 +msgid "" +"New function: :func:`~symtable.Symbol.is_declared_global` in the :mod:" +"`symtable` module returns true for variables that are explicitly declared to " +"be global, false for ones that are implicitly global. (Contributed by Jeremy " +"Hylton.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1598 ../Doc/whatsnew/2.7.rst:2484 +msgid "" +"The :mod:`syslog` module will now use the value of ``sys.argv[0]`` as the " +"identifier instead of the previous default value of ``'python'``. (Changed " +"by Sean Reifschneider; :issue:`8451`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1602 +msgid "" +"The ``sys.version_info`` value is now a named tuple, with attributes named :" +"attr:`major`, :attr:`minor`, :attr:`micro`, :attr:`releaselevel`, and :attr:" +"`serial`. (Contributed by Ross Light; :issue:`4285`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1607 +msgid "" +":func:`sys.getwindowsversion` also returns a named tuple, with attributes " +"named :attr:`major`, :attr:`minor`, :attr:`build`, :attr:`platform`, :attr:" +"`service_pack`, :attr:`service_pack_major`, :attr:`service_pack_minor`, :" +"attr:`suite_mask`, and :attr:`product_type`. (Contributed by Brian Curtin; :" +"issue:`7766`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1613 ../Doc/whatsnew/2.7.rst:2488 +msgid "" +"The :mod:`tarfile` module's default error handling has changed, to no longer " +"suppress fatal errors. The default error level was previously 0, which " +"meant that errors would only result in a message being written to the debug " +"log, but because the debug log is not activated by default, these errors go " +"unnoticed. The default error level is now 1, which raises an exception if " +"there's an error. (Changed by Lars Gustäbel; :issue:`7357`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1621 +msgid "" +":mod:`tarfile` now supports filtering the :class:`~tarfile.TarInfo` objects " +"being added to a tar file. When you call :meth:`~tarfile.TarFile.add`, you " +"may supply an optional *filter* argument that's a callable. The *filter* " +"callable will be passed the :class:`~tarfile.TarInfo` for every file being " +"added, and can modify and return it. If the callable returns ``None``, the " +"file will be excluded from the resulting archive. This is more powerful " +"than the existing *exclude* argument, which has therefore been deprecated. " +"(Added by Lars Gustäbel; :issue:`6856`.) The :class:`~tarfile.TarFile` class " +"also now supports the context management protocol. (Added by Lars Gustäbel; :" +"issue:`7232`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1633 +msgid "" +"The :meth:`~threading.Event.wait` method of the :class:`threading.Event` " +"class now returns the internal flag on exit. This means the method will " +"usually return true because :meth:`~threading.Event.wait` is supposed to " +"block until the internal flag becomes true. The return value will only be " +"false if a timeout was provided and the operation timed out. (Contributed by " +"Tim Lesher; :issue:`1674032`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1640 +msgid "" +"The Unicode database provided by the :mod:`unicodedata` module is now used " +"internally to determine which characters are numeric, whitespace, or " +"represent line breaks. The database also includes information from the :" +"file:`Unihan.txt` data file (patch by Anders Chrigström and Amaury Forgeot " +"d'Arc; :issue:`1571184`) and has been updated to version 5.2.0 (updated by " +"Florent Xicluna; :issue:`8024`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1648 ../Doc/whatsnew/2.7.rst:2496 +msgid "" +"The :mod:`urlparse` module's :func:`~urlparse.urlsplit` now handles unknown " +"URL schemes in a fashion compliant with :rfc:`3986`: if the URL is of the " +"form ``\"://...\"``, the text before the ``://`` is treated as " +"the scheme, even if it's a made-up scheme that the module doesn't know " +"about. This change may break code that worked around the old behaviour. " +"For example, Python 2.6.4 or 2.5 will return the following:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1663 ../Doc/whatsnew/2.7.rst:2511 +msgid "Python 2.7 (and Python 2.6.5) will return:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1672 ../Doc/whatsnew/2.7.rst:2520 +msgid "" +"(Python 2.7 actually produces slightly different output, since it returns a " +"named tuple instead of a standard tuple.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1675 +msgid "" +"The :mod:`urlparse` module also supports IPv6 literal addresses as defined " +"by :rfc:`2732` (contributed by Senthil Kumaran; :issue:`2987`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1685 +msgid "" +"New class: the :class:`~weakref.WeakSet` class in the :mod:`weakref` module " +"is a set that only holds weak references to its elements; elements will be " +"removed once there are no references pointing to them. (Originally " +"implemented in Python 3.x by Raymond Hettinger, and backported to 2.7 by " +"Michael Foord.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1691 +msgid "" +"The ElementTree library, :mod:`xml.etree`, no longer escapes ampersands and " +"angle brackets when outputting an XML processing instruction (which looks " +"like ````) or comment (which looks like " +"````). (Patch by Neil Muller; :issue:`2746`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1697 +msgid "" +"The XML-RPC client and server, provided by the :mod:`xmlrpclib` and :mod:" +"`SimpleXMLRPCServer` modules, have improved performance by supporting " +"HTTP/1.1 keep-alive and by optionally using gzip encoding to compress the " +"XML being exchanged. The gzip compression is controlled by the :attr:" +"`encode_threshold` attribute of :class:`SimpleXMLRPCRequestHandler`, which " +"contains a size in bytes; responses larger than this will be compressed. " +"(Contributed by Kristján Valur Jónsson; :issue:`6267`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1706 +msgid "" +"The :mod:`zipfile` module's :class:`~zipfile.ZipFile` now supports the " +"context management protocol, so you can write ``with zipfile.ZipFile(...) as " +"f:``. (Contributed by Brian Curtin; :issue:`5511`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1710 +msgid "" +":mod:`zipfile` now also supports archiving empty directories and extracts " +"them correctly. (Fixed by Kuba Wieczorek; :issue:`4710`.) Reading files out " +"of an archive is faster, and interleaving :meth:`~zipfile.ZipFile.read` and :" +"meth:`~zipfile.ZipFile.readline` now works correctly. (Contributed by Nir " +"Aides; :issue:`7610`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1716 +msgid "" +"The :func:`~zipfile.is_zipfile` function now accepts a file object, in " +"addition to the path names accepted in earlier versions. (Contributed by " +"Gabriel Genellina; :issue:`4756`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1720 +msgid "" +"The :meth:`~zipfile.ZipFile.writestr` method now has an optional " +"*compress_type* parameter that lets you override the default compression " +"method specified in the :class:`~zipfile.ZipFile` constructor. (Contributed " +"by Ronald Oussoren; :issue:`6003`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1733 +msgid "New module: importlib" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1735 +msgid "" +"Python 3.1 includes the :mod:`importlib` package, a re-implementation of the " +"logic underlying Python's :keyword:`import` statement. :mod:`importlib` is " +"useful for implementors of Python interpreters and to users who wish to " +"write new importers that can participate in the import process. Python 2.7 " +"doesn't contain the complete :mod:`importlib` package, but instead has a " +"tiny subset that contains a single function, :func:`~importlib." +"import_module`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1743 +msgid "" +"``import_module(name, package=None)`` imports a module. *name* is a string " +"containing the module or package's name. It's possible to do relative " +"imports by providing a string that begins with a ``.`` character, such as " +"``..utils.errors``. For relative imports, the *package* argument must be " +"provided and is the name of the package that will be used as the anchor for " +"the relative import. :func:`~importlib.import_module` both inserts the " +"imported module into ``sys.modules`` and returns the module object." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1752 +msgid "Here are some examples::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1763 +msgid "" +":mod:`importlib` was implemented by Brett Cannon and introduced in Python " +"3.1." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1768 +msgid "New module: sysconfig" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1770 +msgid "" +"The :mod:`sysconfig` module has been pulled out of the Distutils package, " +"becoming a new top-level module in its own right. :mod:`sysconfig` provides " +"functions for getting information about Python's build process: compiler " +"switches, installation paths, the platform name, and whether Python is " +"running from its source directory." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1777 +msgid "Some of the functions in the module are:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1779 +msgid "" +":func:`~sysconfig.get_config_var` returns variables from Python's Makefile " +"and the :file:`pyconfig.h` file." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1781 +msgid "" +":func:`~sysconfig.get_config_vars` returns a dictionary containing all of " +"the configuration variables." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1783 +msgid "" +":func:`~sysconfig.get_path` returns the configured path for a particular " +"type of module: the standard library, site-specific modules, platform-" +"specific modules, etc." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1786 +msgid "" +":func:`~sysconfig.is_python_build` returns true if you're running a binary " +"from a Python source tree, and false otherwise." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1789 +msgid "" +"Consult the :mod:`sysconfig` documentation for more details and for a " +"complete list of functions." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1792 +msgid "" +"The Distutils package and :mod:`sysconfig` are now maintained by Tarek " +"Ziadé, who has also started a Distutils2 package (source repository at " +"https://hg.python.org/distutils2/) for developing a next-generation version " +"of Distutils." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1799 +msgid "ttk: Themed Widgets for Tk" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1801 +msgid "" +"Tcl/Tk 8.5 includes a set of themed widgets that re-implement basic Tk " +"widgets but have a more customizable appearance and can therefore more " +"closely resemble the native platform's widgets. This widget set was " +"originally called Tile, but was renamed to Ttk (for \"themed Tk\") on being " +"added to Tcl/Tck release 8.5." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1807 +msgid "" +"To learn more, read the :mod:`ttk` module documentation. You may also wish " +"to read the Tcl/Tk manual page describing the Ttk theme engine, available at " +"https://www.tcl.tk/man/tcl8.5/TkCmd/ttk_intro.htm. Some screenshots of the " +"Python/Ttk code in use are at http://code.google.com/p/python-ttk/wiki/" +"Screenshots." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1814 +msgid "" +"The :mod:`ttk` module was written by Guilherme Polo and added in :issue:" +"`2983`. An alternate version called ``Tile.py``, written by Martin Franklin " +"and maintained by Kevin Walzer, was proposed for inclusion in :issue:`2618`, " +"but the authors argued that Guilherme Polo's work was more comprehensive." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1824 +msgid "Updated module: unittest" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1826 +msgid "" +"The :mod:`unittest` module was greatly enhanced; many new features were " +"added. Most of these features were implemented by Michael Foord, unless " +"otherwise noted. The enhanced version of the module is downloadable " +"separately for use with Python versions 2.4 to 2.6, packaged as the :mod:" +"`unittest2` package, from https://pypi.python.org/pypi/unittest2." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1833 +msgid "" +"When used from the command line, the module can automatically discover " +"tests. It's not as fancy as `py.test `__ or `nose " +"`__, but provides a simple way to run " +"tests kept within a set of package directories. For example, the following " +"command will search the :file:`test/` subdirectory for any importable test " +"files named ``test*.py``::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1842 +msgid "" +"Consult the :mod:`unittest` module documentation for more details. " +"(Developed in :issue:`6001`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1845 +msgid "The :func:`~unittest.main` function supports some other new options:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1847 +msgid "" +":option:`-b ` or :option:`--buffer` will buffer the standard " +"output and standard error streams during each test. If the test passes, any " +"resulting output will be discarded; on failure, the buffered output will be " +"displayed." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1852 +msgid "" +":option:`-c ` or :option:`--catch` will cause the control-C " +"interrupt to be handled more gracefully. Instead of interrupting the test " +"process immediately, the currently running test will be completed and then " +"the partial results up to the interruption will be reported. If you're " +"impatient, a second press of control-C will cause an immediate interruption." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1859 +msgid "" +"This control-C handler tries to avoid causing problems when the code being " +"tested or the tests being run have defined a signal handler of their own, by " +"noticing that a signal handler was already set and calling it. If this " +"doesn't work for you, there's a :func:`~unittest.removeHandler` decorator " +"that can be used to mark tests that should have the control-C handling " +"disabled." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1866 +msgid "" +":option:`-f ` or :option:`--failfast` makes test execution stop " +"immediately when a test fails instead of continuing to execute further " +"tests. (Suggested by Cliff Dyer and implemented by Michael Foord; :issue:" +"`8074`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1871 +msgid "" +"The progress messages now show 'x' for expected failures and 'u' for " +"unexpected successes when run in verbose mode. (Contributed by Benjamin " +"Peterson.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1875 +msgid "" +"Test cases can raise the :exc:`~unittest.SkipTest` exception to skip a test " +"(:issue:`1034053`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1878 +msgid "" +"The error messages for :meth:`~unittest.TestCase.assertEqual`, :meth:" +"`~unittest.TestCase.assertTrue`, and :meth:`~unittest.TestCase.assertFalse` " +"failures now provide more information. If you set the :attr:`~unittest." +"TestCase.longMessage` attribute of your :class:`~unittest.TestCase` classes " +"to True, both the standard error message and any additional message you " +"provide will be printed for failures. (Added by Michael Foord; :issue:" +"`5663`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1885 +msgid "" +"The :meth:`~unittest.TestCase.assertRaises` method now returns a context " +"handler when called without providing a callable object to run. For " +"example, you can write this::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1892 +msgid "(Implemented by Antoine Pitrou; :issue:`4444`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1896 +msgid "" +"Module- and class-level setup and teardown fixtures are now supported. " +"Modules can contain :func:`~unittest.setUpModule` and :func:`~unittest." +"tearDownModule` functions. Classes can have :meth:`~unittest.TestCase." +"setUpClass` and :meth:`~unittest.TestCase.tearDownClass` methods that must " +"be defined as class methods (using ``@classmethod`` or equivalent). These " +"functions and methods are invoked when the test runner switches to a test " +"case in a different module or class." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1904 +msgid "" +"The methods :meth:`~unittest.TestCase.addCleanup` and :meth:`~unittest." +"TestCase.doCleanups` were added. :meth:`~unittest.TestCase.addCleanup` lets " +"you add cleanup functions that will be called unconditionally (after :meth:" +"`~unittest.TestCase.setUp` if :meth:`~unittest.TestCase.setUp` fails, " +"otherwise after :meth:`~unittest.TestCase.tearDown`). This allows for much " +"simpler resource allocation and deallocation during tests (:issue:`5679`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1912 +msgid "" +"A number of new methods were added that provide more specialized tests. " +"Many of these methods were written by Google engineers for use in their test " +"suites; Gregory P. Smith, Michael Foord, and GvR worked on merging them into " +"Python's version of :mod:`unittest`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1917 +msgid "" +":meth:`~unittest.TestCase.assertIsNone` and :meth:`~unittest.TestCase." +"assertIsNotNone` take one expression and verify that the result is or is not " +"``None``." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1920 +msgid "" +":meth:`~unittest.TestCase.assertIs` and :meth:`~unittest.TestCase." +"assertIsNot` take two values and check whether the two values evaluate to " +"the same object or not. (Added by Michael Foord; :issue:`2578`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1924 +msgid "" +":meth:`~unittest.TestCase.assertIsInstance` and :meth:`~unittest.TestCase." +"assertNotIsInstance` check whether the resulting object is an instance of a " +"particular class, or of one of a tuple of classes. (Added by Georg Brandl; :" +"issue:`7031`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1929 +msgid "" +":meth:`~unittest.TestCase.assertGreater`, :meth:`~unittest.TestCase." +"assertGreaterEqual`, :meth:`~unittest.TestCase.assertLess`, and :meth:" +"`~unittest.TestCase.assertLessEqual` compare two quantities." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1933 +msgid "" +":meth:`~unittest.TestCase.assertMultiLineEqual` compares two strings, and if " +"they're not equal, displays a helpful comparison that highlights the " +"differences in the two strings. This comparison is now used by default when " +"Unicode strings are compared with :meth:`~unittest.TestCase.assertEqual`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1938 +msgid "" +":meth:`~unittest.TestCase.assertRegexpMatches` and :meth:`~unittest.TestCase." +"assertNotRegexpMatches` checks whether the first argument is a string " +"matching or not matching the regular expression provided as the second " +"argument (:issue:`8038`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1943 +msgid "" +":meth:`~unittest.TestCase.assertRaisesRegexp` checks whether a particular " +"exception is raised, and then also checks that the string representation of " +"the exception matches the provided regular expression." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1947 +msgid "" +":meth:`~unittest.TestCase.assertIn` and :meth:`~unittest.TestCase." +"assertNotIn` tests whether *first* is or is not in *second*." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1950 +msgid "" +":meth:`~unittest.TestCase.assertItemsEqual` tests whether two provided " +"sequences contain the same elements." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1953 +msgid "" +":meth:`~unittest.TestCase.assertSetEqual` compares whether two sets are " +"equal, and only reports the differences between the sets in case of error." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1956 +msgid "" +"Similarly, :meth:`~unittest.TestCase.assertListEqual` and :meth:`~unittest." +"TestCase.assertTupleEqual` compare the specified types and explain any " +"differences without necessarily printing their full values; these methods " +"are now used by default when comparing lists and tuples using :meth:" +"`~unittest.TestCase.assertEqual`. More generally, :meth:`~unittest.TestCase." +"assertSequenceEqual` compares two sequences and can optionally check whether " +"both sequences are of a particular type." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1964 +msgid "" +":meth:`~unittest.TestCase.assertDictEqual` compares two dictionaries and " +"reports the differences; it's now used by default when you compare two " +"dictionaries using :meth:`~unittest.TestCase.assertEqual`. :meth:`~unittest." +"TestCase.assertDictContainsSubset` checks whether all of the key/value pairs " +"in *first* are found in *second*." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1969 +msgid "" +":meth:`~unittest.TestCase.assertAlmostEqual` and :meth:`~unittest.TestCase." +"assertNotAlmostEqual` test whether *first* and *second* are approximately " +"equal. This method can either round their difference to an optionally-" +"specified number of *places* (the default is 7) and compare it to zero, or " +"require the difference to be smaller than a supplied *delta* value." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1975 +msgid "" +":meth:`~unittest.TestLoader.loadTestsFromName` properly honors the :attr:" +"`~unittest.TestLoader.suiteClass` attribute of the :class:`~unittest." +"TestLoader`. (Fixed by Mark Roddy; :issue:`6866`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1979 +msgid "" +"A new hook lets you extend the :meth:`~unittest.TestCase.assertEqual` method " +"to handle new data types. The :meth:`~unittest.TestCase." +"addTypeEqualityFunc` method takes a type object and a function. The function " +"will be used when both of the objects being compared are of the specified " +"type. This function should compare the two objects and raise an exception " +"if they don't match; it's a good idea for the function to provide additional " +"information about why the two objects aren't matching, much as the new " +"sequence comparison methods do." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1988 +msgid "" +":func:`unittest.main` now takes an optional ``exit`` argument. If False, :" +"func:`~unittest.main` doesn't call :func:`sys.exit`, allowing :func:" +"`~unittest.main` to be used from the interactive interpreter. (Contributed " +"by J. Pablo Fernández; :issue:`3379`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1993 +msgid "" +":class:`~unittest.TestResult` has new :meth:`~unittest.TestResult." +"startTestRun` and :meth:`~unittest.TestResult.stopTestRun` methods that are " +"called immediately before and after a test run. (Contributed by Robert " +"Collins; :issue:`5728`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:1997 +msgid "" +"With all these changes, the :file:`unittest.py` was becoming awkwardly " +"large, so the module was turned into a package and the code split into " +"several files (by Benjamin Peterson). This doesn't affect how the module is " +"imported or used." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2005 +msgid "http://www.voidspace.org.uk/python/articles/unittest2.shtml" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2005 +msgid "" +"Describes the new features, how to use them, and the rationale for various " +"design decisions. (By Michael Foord.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2011 +msgid "Updated module: ElementTree 1.3" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2013 +msgid "" +"The version of the ElementTree library included with Python was updated to " +"version 1.3. Some of the new features are:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2016 +msgid "" +"The various parsing functions now take a *parser* keyword argument giving " +"an :class:`~xml.etree.ElementTree.XMLParser` instance that will be used. " +"This makes it possible to override the file's internal encoding::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2023 +msgid "" +"Errors in parsing XML now raise a :exc:`ParseError` exception, whose " +"instances have a :attr:`position` attribute containing a (*line*, *column*) " +"tuple giving the location of the problem." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2027 +msgid "" +"ElementTree's code for converting trees to a string has been significantly " +"reworked, making it roughly twice as fast in many cases. The :meth:" +"`ElementTree.write() ` and :meth:" +"`Element.write` methods now have a *method* parameter that can be \"xml" +"\" (the default), \"html\", or \"text\". HTML mode will output empty " +"elements as ```` instead of ````, and text mode will " +"skip over elements and only output the text chunks. If you set the :attr:" +"`tag` attribute of an element to ``None`` but leave its children in place, " +"the element will be omitted when the tree is written out, so you don't need " +"to do more extensive rearrangement to remove a single element." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2039 +msgid "" +"Namespace handling has also been improved. All ``xmlns:`` " +"declarations are now output on the root element, not scattered throughout " +"the resulting XML. You can set the default namespace for a tree by setting " +"the :attr:`default_namespace` attribute and can register new prefixes with :" +"meth:`~xml.etree.ElementTree.register_namespace`. In XML mode, you can use " +"the true/false *xml_declaration* parameter to suppress the XML declaration." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2047 +msgid "" +"New :class:`~xml.etree.ElementTree.Element` method: :meth:`~xml.etree." +"ElementTree.Element.extend` appends the items from a sequence to the " +"element's children. Elements themselves behave like sequences, so it's easy " +"to move children from one element to another::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2064 +msgid "" +"New :class:`Element` method: :meth:`~xml.etree.ElementTree.Element.iter` " +"yields the children of the element as a generator. It's also possible to " +"write ``for child in elem:`` to loop over an element's children. The " +"existing method :meth:`getiterator` is now deprecated, as is :meth:" +"`getchildren` which constructs and returns a list of children." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2071 +msgid "" +"New :class:`Element` method: :meth:`~xml.etree.ElementTree.Element.itertext` " +"yields all chunks of text that are descendants of the element. For example::" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2082 +msgid "" +"Deprecated: using an element as a Boolean (i.e., ``if elem:``) would return " +"true if the element had any children, or false if there were no children. " +"This behaviour is confusing -- ``None`` is false, but so is a childless " +"element? -- so it will now trigger a :exc:`FutureWarning`. In your code, " +"you should be explicit: write ``len(elem) != 0`` if you're interested in the " +"number of children, or ``elem is not None``." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2090 +msgid "" +"Fredrik Lundh develops ElementTree and produced the 1.3 version; you can " +"read his article describing 1.3 at http://effbot.org/zone/elementtree-13-" +"intro.htm. Florent Xicluna updated the version included with Python, after " +"discussions on python-dev and in :issue:`6472`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2104 +msgid "" +"The latest release of the GNU Debugger, GDB 7, can be `scripted using Python " +"`__. When you " +"begin debugging an executable program P, GDB will look for a file named ``P-" +"gdb.py`` and automatically read it. Dave Malcolm contributed a :file:" +"`python-gdb.py` that adds a number of commands useful when debugging Python " +"itself. For example, ``py-up`` and ``py-down`` go up or down one Python " +"stack frame, which usually corresponds to several C stack frames. ``py-" +"print`` prints the value of a Python variable, and ``py-bt`` prints the " +"Python stack trace. (Added as a result of :issue:`8032`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2116 +msgid "" +"If you use the :file:`.gdbinit` file provided with Python, the \"pyo\" macro " +"in the 2.7 version now works correctly when the thread being debugged " +"doesn't hold the GIL; the macro now acquires it before printing. " +"(Contributed by Victor Stinner; :issue:`3632`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2121 +msgid "" +":c:func:`Py_AddPendingCall` is now thread-safe, letting any worker thread " +"submit notifications to the main Python thread. This is particularly useful " +"for asynchronous IO operations. (Contributed by Kristján Valur Jónsson; :" +"issue:`4293`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2126 +msgid "" +"New function: :c:func:`PyCode_NewEmpty` creates an empty code object; only " +"the filename, function name, and first line number are required. This is " +"useful for extension modules that are attempting to construct a more useful " +"traceback stack. Previously such extensions needed to call :c:func:" +"`PyCode_New`, which had many more arguments. (Added by Jeffrey Yasskin.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2133 +msgid "" +"New function: :c:func:`PyErr_NewExceptionWithDoc` creates a new exception " +"class, just as the existing :c:func:`PyErr_NewException` does, but takes an " +"extra ``char *`` argument containing the docstring for the new exception " +"class. (Added by 'lekma' on the Python bug tracker; :issue:`7033`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2139 +msgid "" +"New function: :c:func:`PyFrame_GetLineNumber` takes a frame object and " +"returns the line number that the frame is currently executing. Previously " +"code would need to get the index of the bytecode instruction currently " +"executing, and then look up the line number corresponding to that address. " +"(Added by Jeffrey Yasskin.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2145 +msgid "" +"New functions: :c:func:`PyLong_AsLongAndOverflow` and :c:func:" +"`PyLong_AsLongLongAndOverflow` approximates a Python long integer as a C :c:" +"type:`long` or :c:type:`long long`. If the number is too large to fit into " +"the output type, an *overflow* flag is set and returned to the caller. " +"(Contributed by Case Van Horsen; :issue:`7528` and :issue:`7767`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2152 +msgid "" +"New function: stemming from the rewrite of string-to-float conversion, a " +"new :c:func:`PyOS_string_to_double` function was added. The old :c:func:" +"`PyOS_ascii_strtod` and :c:func:`PyOS_ascii_atof` functions are now " +"deprecated." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2157 +msgid "" +"New function: :c:func:`PySys_SetArgvEx` sets the value of ``sys.argv`` and " +"can optionally update ``sys.path`` to include the directory containing the " +"script named by ``sys.argv[0]`` depending on the value of an *updatepath* " +"parameter." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2162 +msgid "" +"This function was added to close a security hole for applications that embed " +"Python. The old function, :c:func:`PySys_SetArgv`, would always update " +"``sys.path``, and sometimes it would add the current directory. This meant " +"that, if you ran an application embedding Python in a directory controlled " +"by someone else, attackers could put a Trojan-horse module in the directory " +"(say, a file named :file:`os.py`) that your application would then import " +"and run." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2170 +msgid "" +"If you maintain a C/C++ application that embeds Python, check whether you're " +"calling :c:func:`PySys_SetArgv` and carefully consider whether the " +"application should be using :c:func:`PySys_SetArgvEx` with *updatepath* set " +"to false." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2175 +msgid "" +"Security issue reported as `CVE-2008-5983 `_; discussed in :issue:`5753`, and fixed by " +"Antoine Pitrou." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2179 +msgid "" +"New macros: the Python header files now define the following macros: :c:" +"macro:`Py_ISALNUM`, :c:macro:`Py_ISALPHA`, :c:macro:`Py_ISDIGIT`, :c:macro:" +"`Py_ISLOWER`, :c:macro:`Py_ISSPACE`, :c:macro:`Py_ISUPPER`, :c:macro:" +"`Py_ISXDIGIT`, :c:macro:`Py_TOLOWER`, and :c:macro:`Py_TOUPPER`. All of " +"these functions are analogous to the C standard macros for classifying " +"characters, but ignore the current locale setting, because in several places " +"Python needs to analyze characters in a locale-independent way. (Added by " +"Eric Smith; :issue:`5793`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2197 +msgid "" +"Removed function: :c:macro:`PyEval_CallObject` is now only available as a " +"macro. A function version was being kept around to preserve ABI linking " +"compatibility, but that was in 1997; it can certainly be deleted by now. " +"(Removed by Antoine Pitrou; :issue:`8276`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2202 +msgid "" +"New format codes: the :c:func:`PyFormat_FromString`, :c:func:" +"`PyFormat_FromStringV`, and :c:func:`PyErr_Format` functions now accept ``" +"%lld`` and ``%llu`` format codes for displaying C's :c:type:`long long` " +"types. (Contributed by Mark Dickinson; :issue:`7228`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2208 +msgid "" +"The complicated interaction between threads and process forking has been " +"changed. Previously, the child process created by :func:`os.fork` might " +"fail because the child is created with only a single thread running, the " +"thread performing the :func:`os.fork`. If other threads were holding a lock, " +"such as Python's import lock, when the fork was performed, the lock would " +"still be marked as \"held\" in the new process. But in the child process " +"nothing would ever release the lock, since the other threads weren't " +"replicated, and the child process would no longer be able to perform imports." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2218 +msgid "" +"Python 2.7 acquires the import lock before performing an :func:`os.fork`, " +"and will also clean up any locks created using the :mod:`threading` module. " +"C extension modules that have internal locks, or that call :c:func:`fork()` " +"themselves, will not benefit from this clean-up." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2224 +msgid "(Fixed by Thomas Wouters; :issue:`1590864`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2226 +msgid "" +"The :c:func:`Py_Finalize` function now calls the internal :func:`threading." +"_shutdown` function; this prevents some exceptions from being raised when an " +"interpreter shuts down. (Patch by Adam Olsen; :issue:`1722344`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2231 +msgid "" +"When using the :c:type:`PyMemberDef` structure to define attributes of a " +"type, Python will no longer let you try to delete or set a :const:" +"`T_STRING_INPLACE` attribute." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2237 +msgid "" +"Global symbols defined by the :mod:`ctypes` module are now prefixed with " +"``Py``, or with ``_ctypes``. (Implemented by Thomas Heller; :issue:`3102`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2241 +msgid "" +"New configure option: the :option:`--with-system-expat` switch allows " +"building the :mod:`pyexpat` module to use the system Expat library. " +"(Contributed by Arfrever Frehtes Taifersar Arahesis; :issue:`7609`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2245 +msgid "" +"New configure option: the :option:`--with-valgrind` option will now disable " +"the pymalloc allocator, which is difficult for the Valgrind memory-error " +"detector to analyze correctly. Valgrind will therefore be better at " +"detecting memory leaks and overruns. (Contributed by James Henstridge; :" +"issue:`2422`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2252 +msgid "" +"New configure option: you can now supply an empty string to :option:`--with-" +"dbmliborder=` in order to disable all of the various DBM modules. (Added by " +"Arfrever Frehtes Taifersar Arahesis; :issue:`6491`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2257 +msgid "" +"The :program:`configure` script now checks for floating-point rounding bugs " +"on certain 32-bit Intel chips and defines a :c:macro:`X87_DOUBLE_ROUNDING` " +"preprocessor definition. No code currently uses this definition, but it's " +"available if anyone wishes to use it. (Added by Mark Dickinson; :issue:" +"`2937`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2263 +msgid "" +":program:`configure` also now sets a :envvar:`LDCXXSHARED` Makefile variable " +"for supporting C++ linking. (Contributed by Arfrever Frehtes Taifersar " +"Arahesis; :issue:`1222585`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2267 +msgid "" +"The build process now creates the necessary files for pkg-config support. " +"(Contributed by Clinton Roy; :issue:`3585`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2270 +msgid "" +"The build process now supports Subversion 1.7. (Contributed by Arfrever " +"Frehtes Taifersar Arahesis; :issue:`6094`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2277 +msgid "Capsules" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2279 +msgid "" +"Python 3.1 adds a new C datatype, :c:type:`PyCapsule`, for providing a C API " +"to an extension module. A capsule is essentially the holder of a C ``void " +"*`` pointer, and is made available as a module attribute; for example, the :" +"mod:`socket` module's API is exposed as ``socket.CAPI``, and :mod:" +"`unicodedata` exposes ``ucnhash_CAPI``. Other extensions can import the " +"module, access its dictionary to get the capsule object, and then get the " +"``void *`` pointer, which will usually point to an array of pointers to the " +"module's various API functions." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2288 +msgid "" +"There is an existing data type already used for this, :c:type:`PyCObject`, " +"but it doesn't provide type safety. Evil code written in pure Python could " +"cause a segmentation fault by taking a :c:type:`PyCObject` from module A and " +"somehow substituting it for the :c:type:`PyCObject` in module B. Capsules " +"know their own name, and getting the pointer requires providing the name:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2306 +msgid "" +"You are assured that ``vtable`` points to whatever you're expecting. If a " +"different capsule was passed in, :c:func:`PyCapsule_IsValid` would detect " +"the mismatched name and return false. Refer to :ref:`using-capsules` for " +"more information on using these objects." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2311 +msgid "" +"Python 2.7 now uses capsules internally to provide various extension-module " +"APIs, but the :c:func:`PyCObject_AsVoidPtr` was modified to handle capsules, " +"preserving compile-time compatibility with the :c:type:`CObject` interface. " +"Use of :c:func:`PyCObject_AsVoidPtr` will signal a :exc:" +"`PendingDeprecationWarning`, which is silent by default." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2318 +msgid "" +"Implemented in Python 3.1 and backported to 2.7 by Larry Hastings; discussed " +"in :issue:`5630`." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2327 +msgid "" +"The :mod:`msvcrt` module now contains some constants from the :file:" +"`crtassem.h` header file: :data:`CRT_ASSEMBLY_VERSION`, :data:" +"`VC_ASSEMBLY_PUBLICKEYTOKEN`, and :data:`LIBRARIES_ASSEMBLY_NAME_PREFIX`. " +"(Contributed by David Cournapeau; :issue:`4365`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2334 +msgid "" +"The :mod:`_winreg` module for accessing the registry now implements the :" +"func:`~_winreg.CreateKeyEx` and :func:`~_winreg.DeleteKeyEx` functions, " +"extended versions of previously-supported functions that take several extra " +"arguments. The :func:`~_winreg.DisableReflectionKey`, :func:`~_winreg." +"EnableReflectionKey`, and :func:`~_winreg.QueryReflectionKey` were also " +"tested and documented. (Implemented by Brian Curtin: :issue:`7347`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2342 +msgid "" +"The new :c:func:`_beginthreadex` API is used to start threads, and the " +"native thread-local storage functions are now used. (Contributed by Kristján " +"Valur Jónsson; :issue:`3582`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2346 +msgid "" +"The :func:`os.kill` function now works on Windows. The signal value can be " +"the constants :const:`CTRL_C_EVENT`, :const:`CTRL_BREAK_EVENT`, or any " +"integer. The first two constants will send :kbd:`Control-C` and :kbd:" +"`Control-Break` keystroke events to subprocesses; any other value will use " +"the :c:func:`TerminateProcess` API. (Contributed by Miki Tebeka; :issue:" +"`1220212`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2353 +msgid "" +"The :func:`os.listdir` function now correctly fails for an empty path. " +"(Fixed by Hirokazu Yamamoto; :issue:`5913`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2356 +msgid "" +"The :mod:`mimelib` module will now read the MIME database from the Windows " +"registry when initializing. (Patch by Gabriel Genellina; :issue:`4969`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2365 +msgid "" +"The path ``/Library/Python/2.7/site-packages`` is now appended to ``sys." +"path``, in order to share added packages between the system installation and " +"a user-installed copy of the same version. (Changed by Ronald Oussoren; :" +"issue:`4865`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2371 +msgid "Port-Specific Changes: FreeBSD" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2373 +msgid "" +"FreeBSD 7.1's :const:`SO_SETFIB` constant, used with :func:`~socket." +"getsockopt`/:func:`~socket.setsockopt` to select an alternate routing table, " +"is now available in the :mod:`socket` module. (Added by Kyle VanderBeek; :" +"issue:`8235`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2381 +msgid "" +"Two benchmark scripts, :file:`iobench` and :file:`ccbench`, were added to " +"the :file:`Tools` directory. :file:`iobench` measures the speed of the " +"built-in file I/O objects returned by :func:`open` while performing various " +"operations, and :file:`ccbench` is a concurrency benchmark that tries to " +"measure computing throughput, thread switching latency, and IO processing " +"bandwidth when performing several tasks using a varying number of threads." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2389 +msgid "" +"The :file:`Tools/i18n/msgfmt.py` script now understands plural forms in :" +"file:`.po` files. (Fixed by Martin von Löwis; :issue:`5464`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2393 +msgid "" +"When importing a module from a :file:`.pyc` or :file:`.pyo` file with an " +"existing :file:`.py` counterpart, the :attr:`co_filename` attributes of the " +"resulting code objects are overwritten when the original filename is " +"obsolete. This can happen if the file has been renamed, moved, or is " +"accessed through different paths. (Patch by Ziga Seilnacht and Jean-Paul " +"Calderone; :issue:`1180193`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2400 +msgid "" +"The :file:`regrtest.py` script now takes a :option:`--randseed=` switch that " +"takes an integer that will be used as the random seed for the :option:`-r` " +"option that executes tests in random order. The :option:`-r` option also " +"reports the seed that was used (Added by Collin Winter.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2406 +msgid "" +"Another :file:`regrtest.py` switch is :option:`-j`, which takes an integer " +"specifying how many tests run in parallel. This allows reducing the total " +"runtime on multi-core machines. This option is compatible with several other " +"options, including the :option:`!-R` switch which is known to produce long " +"runtimes. (Added by Antoine Pitrou, :issue:`6152`.) This can also be used " +"with a new :option:`-F` switch that runs selected tests in a loop until they " +"fail. (Added by Antoine Pitrou; :issue:`7312`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2415 +msgid "" +"When executed as a script, the :file:`py_compile.py` module now accepts " +"``'-'`` as an argument, which will read standard input for the list of " +"filenames to be compiled. (Contributed by Piotr Ożarowski; :issue:`8233`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2423 +msgid "Porting to Python 2.7" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2428 +msgid "" +"The :func:`range` function processes its arguments more consistently; it " +"will now call :meth:`__int__` on non-float, non-integer arguments that are " +"supplied to it. (Fixed by Alexander Belopolsky; :issue:`1533`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2433 +msgid "" +"The string :meth:`format` method changed the default precision used for " +"floating-point and complex numbers from 6 decimal places to 12, which " +"matches the precision used by :func:`str`. (Changed by Eric Smith; :issue:" +"`5920`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2438 +msgid "" +"Because of an optimization for the :keyword:`with` statement, the special " +"methods :meth:`__enter__` and :meth:`__exit__` must belong to the object's " +"type, and cannot be directly attached to the object's instance. This " +"affects new-style classes (derived from :class:`object`) and C extension " +"types. (:issue:`6101`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2444 +msgid "" +"Due to a bug in Python 2.6, the *exc_value* parameter to :meth:`__exit__` " +"methods was often the string representation of the exception, not an " +"instance. This was fixed in 2.7, so *exc_value* will be an instance as " +"expected. (Fixed by Florent Xicluna; :issue:`7853`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2454 +msgid "In the standard library:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2456 +msgid "" +"Operations with :class:`~datetime.datetime` instances that resulted in a " +"year falling outside the supported range didn't always raise :exc:" +"`OverflowError`. Such errors are now checked more carefully and will now " +"raise the exception. (Reported by Mark Leander, patch by Anand B. Pillai and " +"Alexander Belopolsky; :issue:`7150`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2462 +msgid "" +"When using :class:`~decimal.Decimal` instances with a string's :meth:" +"`format` method, the default alignment was previously left-alignment. This " +"has been changed to right-alignment, which might change the output of your " +"programs. (Changed by Mark Dickinson; :issue:`6857`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2468 +msgid "" +"Comparisons involving a signaling NaN value (or ``sNAN``) now signal :const:" +"`~decimal.InvalidOperation` instead of silently returning a true or false " +"value depending on the comparison operator. Quiet NaN values (or ``NaN``) " +"are now hashable. (Fixed by Mark Dickinson; :issue:`7279`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2474 +msgid "" +"The ElementTree library, :mod:`xml.etree`, no longer escapes ampersands and " +"angle brackets when outputting an XML processing instruction (which looks " +"like ``) or comment (which looks like " +"``). (Patch by Neil Muller; :issue:`2746`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2480 +msgid "" +"The :meth:`~StringIO.StringIO.readline` method of :class:`~StringIO." +"StringIO` objects now does nothing when a negative length is requested, as " +"other file-like objects do. (:issue:`7348`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2523 +msgid "For C extensions:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2525 +msgid "" +"C extensions that use integer format codes with the ``PyArg_Parse*`` family " +"of functions will now raise a :exc:`TypeError` exception instead of " +"triggering a :exc:`DeprecationWarning` (:issue:`5080`)." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2529 +msgid "" +"Use the new :c:func:`PyOS_string_to_double` function instead of the old :c:" +"func:`PyOS_ascii_strtod` and :c:func:`PyOS_ascii_atof` functions, which are " +"now deprecated." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2533 +msgid "For applications that embed Python:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2535 +msgid "" +"The :c:func:`PySys_SetArgvEx` function was added, letting applications close " +"a security hole when the existing :c:func:`PySys_SetArgv` function was " +"used. Check whether you're calling :c:func:`PySys_SetArgv` and carefully " +"consider whether the application should be using :c:func:`PySys_SetArgvEx` " +"with *updatepath* set to false." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2548 +msgid "New Features Added to Python 2.7 Maintenance Releases" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2550 +msgid "" +"New features may be added to Python 2.7 maintenance releases when the " +"situation genuinely calls for it. Any such additions must go through the " +"Python Enhancement Proposal process, and make a compelling case for why they " +"can't be adequately addressed by either adding the new feature solely to " +"Python 3, or else by publishing it on the Python Package Index." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2556 +msgid "" +"In addition to the specific proposals listed below, there is a general " +"exemption allowing new ``-3`` warnings to be added in any Python 2.7 " +"maintenance release." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2562 +msgid "PEP 434: IDLE Enhancement Exception for All Branches" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2564 +msgid "" +":pep:`434` describes a general exemption for changes made to the IDLE " +"development environment shipped along with Python. This exemption makes it " +"possible for the IDLE developers to provide a more consistent user " +"experience across all supported versions of Python 2 and 3." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2569 +msgid "" +"For details of any IDLE changes, refer to the NEWS file for the specific " +"release." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2574 +msgid "PEP 466: Network Security Enhancements for Python 2.7" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2576 +msgid "" +":pep:`466` describes a number of network security enhancement proposals that " +"have been approved for inclusion in Python 2.7 maintenance releases, with " +"the first of those changes appearing in the Python 2.7.7 release." +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2580 +msgid ":pep:`466` related features added in Python 2.7.7:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2582 +msgid "" +":func:`hmac.compare_digest` was backported from Python 3 to make a timing " +"attack resistant comparison operation available to Python 2 applications. " +"(Contributed by Alex Gaynor; :issue:`21306`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2586 +msgid "" +"OpenSSL 1.0.1g was upgraded in the official Windows installers published on " +"python.org. (Contributed by Zachary Ware; :issue:`21462`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2589 +msgid ":pep:`466` related features added in Python 2.7.8:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2591 +msgid "" +":func:`hashlib.pbkdf2_hmac` was backported from Python 3 to make a hashing " +"algorithm suitable for secure password storage broadly available to Python 2 " +"applications. (Contributed by Alex Gaynor; :issue:`21304`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2595 +msgid "" +"OpenSSL 1.0.1h was upgraded for the official Windows installers published on " +"python.org. (contributed by Zachary Ware in :issue:`21671` for CVE-2014-0224)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2598 +msgid ":pep:`466` related features added in Python 2.7.9:" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2600 +msgid "" +"Most of Python 3.4's :mod:`ssl` module was backported. This means :mod:`ssl` " +"now supports Server Name Indication, TLS1.x settings, access to the platform " +"certificate store, the :class:`~ssl.SSLContext` class, and other features. " +"(Contributed by Alex Gaynor and David Reid; :issue:`21308`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2605 +msgid "" +":func:`os.urandom` was changed to cache a file descriptor to ``/dev/" +"urandom`` instead of reopening ``/dev/urandom`` on every call. (Contributed " +"by Alex Gaynor; :issue:`21305`.)" +msgstr "" + +#: ../Doc/whatsnew/2.7.rst:2617 +msgid "" +"The author would like to thank the following people for offering " +"suggestions, corrections and assistance with various drafts of this article: " +"Nick Coghlan, Philip Jenvey, Ryan Lovett, R. David Murray, Hugh Secker-" +"Walker." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:3 +msgid "What's New In Python 3.0" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:7 +msgid "Guido van Rossum" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:54 +msgid "" +"This article explains the new features in Python 3.0, compared to 2.6. " +"Python 3.0, also known as \"Python 3000\" or \"Py3K\", is the first ever " +"*intentionally backwards incompatible* Python release. There are more " +"changes than in a typical release, and more that are important for all " +"Python users. Nevertheless, after digesting the changes, you'll find that " +"Python really hasn't changed all that much -- by and large, we're mostly " +"fixing well-known annoyances and warts, and removing a lot of old cruft." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:63 +msgid "" +"This article doesn't attempt to provide a complete specification of all new " +"features, but instead tries to give a convenient overview. For full details, " +"you should refer to the documentation for Python 3.0, and/or the many PEPs " +"referenced in the text. If you want to understand the complete " +"implementation and design rationale for a particular feature, PEPs usually " +"have more details than the regular documentation; but note that PEPs usually " +"are not kept up-to-date once a feature has been fully implemented." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:72 +msgid "" +"Due to time constraints this document is not as complete as it should have " +"been. As always for a new release, the ``Misc/NEWS`` file in the source " +"distribution contains a wealth of detailed information about every small " +"thing that was changed." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:89 +msgid "Common Stumbling Blocks" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:91 +msgid "" +"This section lists those few changes that are most likely to trip you up if " +"you're used to Python 2.5." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:95 +msgid "Print Is A Function" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:97 +msgid "" +"The ``print`` statement has been replaced with a :func:`print` function, " +"with keyword arguments to replace most of the special syntax of the old " +"``print`` statement (:pep:`3105`). Examples::" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:116 +msgid "You can also customize the separator between items, e.g.::" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:120 +msgid "which produces:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:126 +msgid "Note:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:128 +msgid "" +"The :func:`print` function doesn't support the \"softspace\" feature of the " +"old ``print`` statement. For example, in Python 2.x, ``print \"A\\n\", \"B" +"\"`` would write ``\"A\\nB\\n\"``; but in Python 3.0, ``print(\"A\\n\", \"B" +"\")`` writes ``\"A\\n B\\n\"``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:133 +msgid "" +"Initially, you'll be finding yourself typing the old ``print x`` a lot in " +"interactive mode. Time to retrain your fingers to type ``print(x)`` instead!" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:137 +msgid "" +"When using the ``2to3`` source-to-source conversion tool, all ``print`` " +"statements are automatically converted to :func:`print` function calls, so " +"this is mostly a non-issue for larger projects." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:143 +msgid "Views And Iterators Instead Of Lists" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:145 +msgid "Some well-known APIs no longer return lists:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:147 +msgid "" +":class:`dict` methods :meth:`dict.keys`, :meth:`dict.items` and :meth:`dict." +"values` return \"views\" instead of lists. For example, this no longer " +"works: ``k = d.keys(); k.sort()``. Use ``k = sorted(d)`` instead (this " +"works in Python 2.5 too and is just as efficient)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:153 +msgid "" +"Also, the :meth:`dict.iterkeys`, :meth:`dict.iteritems` and :meth:`dict." +"itervalues` methods are no longer supported." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:156 +msgid "" +":func:`map` and :func:`filter` return iterators. If you really need a list " +"and the input sequences are all of equal length, a quick fix is to wrap :" +"func:`map` in :func:`list`, e.g. ``list(map(...))``, but a better fix is " +"often to use a list comprehension (especially when the original code uses :" +"keyword:`lambda`), or rewriting the code so it doesn't need a list at all. " +"Particularly tricky is :func:`map` invoked for the side effects of the " +"function; the correct transformation is to use a regular :keyword:`for` loop " +"(since creating a list would just be wasteful)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:167 +msgid "" +"If the input sequences are not of equal length, :func:`map` will stop at the " +"termination of the shortest of the sequences. For full compatibility with :" +"func:`map` from Python 2.x, also wrap the sequences in :func:`itertools." +"zip_longest`, e.g. ``map(func, *sequences)`` becomes ``list(map(func, " +"itertools.zip_longest(*sequences)))``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:173 +msgid "" +":func:`range` now behaves like :func:`xrange` used to behave, except it " +"works with values of arbitrary size. The latter no longer exists." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:177 +msgid ":func:`zip` now returns an iterator." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:180 +msgid "Ordering Comparisons" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:182 +msgid "Python 3.0 has simplified the rules for ordering comparisons:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:184 +msgid "" +"The ordering comparison operators (``<``, ``<=``, ``>=``, ``>``) raise a " +"TypeError exception when the operands don't have a meaningful natural " +"ordering. Thus, expressions like ``1 < ''``, ``0 > None`` or ``len <= len`` " +"are no longer valid, and e.g. ``None < None`` raises :exc:`TypeError` " +"instead of returning ``False``. A corollary is that sorting a heterogeneous " +"list no longer makes sense -- all the elements must be comparable to each " +"other. Note that this does not apply to the ``==`` and ``!=`` operators: " +"objects of different incomparable types always compare unequal to each other." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:195 +msgid "" +":meth:`builtin.sorted` and :meth:`list.sort` no longer accept the *cmp* " +"argument providing a comparison function. Use the *key* argument instead. N." +"B. the *key* and *reverse* arguments are now \"keyword-only\"." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:200 +msgid "" +"The :func:`cmp` function should be treated as gone, and the :meth:`__cmp__` " +"special method is no longer supported. Use :meth:`__lt__` for sorting, :" +"meth:`__eq__` with :meth:`__hash__`, and other rich comparisons as needed. " +"(If you really need the :func:`cmp` functionality, you could use the " +"expression ``(a > b) - (a < b)`` as the equivalent for ``cmp(a, b)``.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:207 +msgid "Integers" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:209 +msgid "" +":pep:`237`: Essentially, :class:`long` renamed to :class:`int`. That is, " +"there is only one built-in integral type, named :class:`int`; but it behaves " +"mostly like the old :class:`long` type." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:213 +msgid "" +":pep:`238`: An expression like ``1/2`` returns a float. Use ``1//2`` to get " +"the truncating behavior. (The latter syntax has existed for years, at least " +"since Python 2.2.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:217 +msgid "" +"The :data:`sys.maxint` constant was removed, since there is no longer a " +"limit to the value of integers. However, :data:`sys.maxsize` can be used as " +"an integer larger than any practical list or string index. It conforms to " +"the implementation's \"natural\" integer size and is typically the same as :" +"data:`sys.maxint` in previous releases on the same platform (assuming the " +"same build options)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:224 +msgid "" +"The :func:`repr` of a long integer doesn't include the trailing ``L`` " +"anymore, so code that unconditionally strips that character will chop off " +"the last digit instead. (Use :func:`str` instead.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:228 +msgid "" +"Octal literals are no longer of the form ``0720``; use ``0o720`` instead." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:232 +msgid "Text Vs. Data Instead Of Unicode Vs. 8-bit" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:234 +msgid "" +"Everything you thought you knew about binary data and Unicode has changed." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:237 +msgid "" +"Python 3.0 uses the concepts of *text* and (binary) *data* instead of " +"Unicode strings and 8-bit strings. All text is Unicode; however *encoded* " +"Unicode is represented as binary data. The type used to hold text is :class:" +"`str`, the type used to hold data is :class:`bytes`. The biggest difference " +"with the 2.x situation is that any attempt to mix text and data in Python " +"3.0 raises :exc:`TypeError`, whereas if you were to mix Unicode and 8-bit " +"strings in Python 2.x, it would work if the 8-bit string happened to contain " +"only 7-bit (ASCII) bytes, but you would get :exc:`UnicodeDecodeError` if it " +"contained non-ASCII values. This value-specific behavior has caused " +"numerous sad faces over the years." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:250 +msgid "" +"As a consequence of this change in philosophy, pretty much all code that " +"uses Unicode, encodings or binary data most likely has to change. The " +"change is for the better, as in the 2.x world there were numerous bugs " +"having to do with mixing encoded and unencoded text. To be prepared in " +"Python 2.x, start using :class:`unicode` for all unencoded text, and :class:" +"`str` for binary or encoded data only. Then the ``2to3`` tool will do most " +"of the work for you." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:258 +msgid "" +"You can no longer use ``u\"...\"`` literals for Unicode text. However, you " +"must use ``b\"...\"`` literals for binary data." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:261 +msgid "" +"As the :class:`str` and :class:`bytes` types cannot be mixed, you must " +"always explicitly convert between them. Use :meth:`str.encode` to go from :" +"class:`str` to :class:`bytes`, and :meth:`bytes.decode` to go from :class:" +"`bytes` to :class:`str`. You can also use ``bytes(s, encoding=...)`` and " +"``str(b, encoding=...)``, respectively." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:268 +msgid "" +"Like :class:`str`, the :class:`bytes` type is immutable. There is a " +"separate *mutable* type to hold buffered binary data, :class:`bytearray`. " +"Nearly all APIs that accept :class:`bytes` also accept :class:`bytearray`. " +"The mutable API is based on :class:`collections.MutableSequence`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:274 +msgid "" +"All backslashes in raw string literals are interpreted literally. This means " +"that ``'\\U'`` and ``'\\u'`` escapes in raw strings are not treated " +"specially. For example, ``r'\\u20ac'`` is a string of 6 characters in " +"Python 3.0, whereas in 2.6, ``ur'\\u20ac'`` was the single \"euro\" " +"character. (Of course, this change only affects raw string literals; the " +"euro character is ``'\\u20ac'`` in Python 3.0.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:281 +msgid "" +"The built-in :class:`basestring` abstract type was removed. Use :class:" +"`str` instead. The :class:`str` and :class:`bytes` types don't have " +"functionality enough in common to warrant a shared base class. The ``2to3`` " +"tool (see below) replaces every occurrence of :class:`basestring` with :" +"class:`str`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:287 +msgid "" +"Files opened as text files (still the default mode for :func:`open`) always " +"use an encoding to map between strings (in memory) and bytes (on disk). " +"Binary files (opened with a ``b`` in the mode argument) always use bytes in " +"memory. This means that if a file is opened using an incorrect mode or " +"encoding, I/O will likely fail loudly, instead of silently producing " +"incorrect data. It also means that even Unix users will have to specify the " +"correct mode (text or binary) when opening a file. There is a platform-" +"dependent default encoding, which on Unixy platforms can be set with the " +"``LANG`` environment variable (and sometimes also with some other platform-" +"specific locale-related environment variables). In many cases, but not all, " +"the system default is UTF-8; you should never count on this default. Any " +"application reading or writing more than pure ASCII text should probably " +"have a way to override the encoding. There is no longer any need for using " +"the encoding-aware streams in the :mod:`codecs` module." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:304 +msgid "" +"The initial values of :data:`sys.stdin`, :data:`sys.stdout` and :data:`sys." +"stderr` are now unicode-only text files (i.e., they are instances of :class:" +"`io.TextIOBase`). To read and write bytes data with these streams, you need " +"to use their :data:`io.TextIOBase.buffer` attribute." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:310 +msgid "" +"Filenames are passed to and returned from APIs as (Unicode) strings. This " +"can present platform-specific problems because on some platforms filenames " +"are arbitrary byte strings. (On the other hand, on Windows filenames are " +"natively stored as Unicode.) As a work-around, most APIs (e.g. :func:`open` " +"and many functions in the :mod:`os` module) that take filenames accept :" +"class:`bytes` objects as well as strings, and a few APIs have a way to ask " +"for a :class:`bytes` return value. Thus, :func:`os.listdir` returns a list " +"of :class:`bytes` instances if the argument is a :class:`bytes` instance, " +"and :func:`os.getcwdb` returns the current working directory as a :class:" +"`bytes` instance. Note that when :func:`os.listdir` returns a list of " +"strings, filenames that cannot be decoded properly are omitted rather than " +"raising :exc:`UnicodeError`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:325 +msgid "" +"Some system APIs like :data:`os.environ` and :data:`sys.argv` can also " +"present problems when the bytes made available by the system is not " +"interpretable using the default encoding. Setting the ``LANG`` variable and " +"rerunning the program is probably the best approach." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:330 +msgid "" +":pep:`3138`: The :func:`repr` of a string no longer escapes non-ASCII " +"characters. It still escapes control characters and code points with non-" +"printable status in the Unicode standard, however." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:334 +msgid ":pep:`3120`: The default source encoding is now UTF-8." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:336 +msgid "" +":pep:`3131`: Non-ASCII letters are now allowed in identifiers. (However, the " +"standard library remains ASCII-only with the exception of contributor names " +"in comments.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:340 +msgid "" +"The :mod:`StringIO` and :mod:`cStringIO` modules are gone. Instead, import " +"the :mod:`io` module and use :class:`io.StringIO` or :class:`io.BytesIO` for " +"text and data respectively." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:344 +msgid "See also the :ref:`unicode-howto`, which was updated for Python 3.0." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:348 +msgid "Overview Of Syntax Changes" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:350 +msgid "" +"This section gives a brief overview of every *syntactic* change in Python " +"3.0." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:354 +msgid "New Syntax" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:356 +msgid "" +":pep:`3107`: Function argument and return value annotations. This provides " +"a standardized way of annotating a function's parameters and return value. " +"There are no semantics attached to such annotations except that they can be " +"introspected at runtime using the :attr:`__annotations__` attribute. The " +"intent is to encourage experimentation through metaclasses, decorators or " +"frameworks." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:363 +msgid "" +":pep:`3102`: Keyword-only arguments. Named parameters occurring after " +"``*args`` in the parameter list *must* be specified using keyword syntax in " +"the call. You can also use a bare ``*`` in the parameter list to indicate " +"that you don't accept a variable-length argument list, but you do have " +"keyword-only arguments." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:369 +msgid "" +"Keyword arguments are allowed after the list of base classes in a class " +"definition. This is used by the new convention for specifying a metaclass " +"(see next section), but can be used for other purposes as well, as long as " +"the metaclass supports it." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:374 +msgid "" +":pep:`3104`: :keyword:`nonlocal` statement. Using ``nonlocal x`` you can " +"now assign directly to a variable in an outer (but non-global) scope. :" +"keyword:`nonlocal` is a new reserved word." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:378 +msgid "" +":pep:`3132`: Extended Iterable Unpacking. You can now write things like " +"``a, b, *rest = some_sequence``. And even ``*rest, a = stuff``. The " +"``rest`` object is always a (possibly empty) list; the right-hand side may " +"be any iterable. Example::" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:385 +msgid "This sets *a* to ``0``, *b* to ``4``, and *rest* to ``[1, 2, 3]``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:387 +msgid "" +"Dictionary comprehensions: ``{k: v for k, v in stuff}`` means the same thing " +"as ``dict(stuff)`` but is more flexible. (This is :pep:`274` vindicated. :-)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:391 +msgid "" +"Set literals, e.g. ``{1, 2}``. Note that ``{}`` is an empty dictionary; use " +"``set()`` for an empty set. Set comprehensions are also supported; e.g., " +"``{x for x in stuff}`` means the same thing as ``set(stuff)`` but is more " +"flexible." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:396 +msgid "" +"New octal literals, e.g. ``0o720`` (already in 2.6). The old octal literals " +"(``0720``) are gone." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:399 +msgid "" +"New binary literals, e.g. ``0b1010`` (already in 2.6), and there is a new " +"corresponding built-in function, :func:`bin`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:402 +msgid "" +"Bytes literals are introduced with a leading ``b`` or ``B``, and there is a " +"new corresponding built-in function, :func:`bytes`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:406 +msgid "Changed Syntax" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:408 +msgid "" +":pep:`3109` and :pep:`3134`: new :keyword:`raise` statement syntax: :samp:" +"`raise [{expr} [from {expr}]]`. See below." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:411 +msgid "" +":keyword:`as` and :keyword:`with` are now reserved words. (Since 2.6, " +"actually.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:414 +msgid "" +"``True``, ``False``, and ``None`` are reserved words. (2.6 partially " +"enforced the restrictions on ``None`` already.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:417 +msgid "" +"Change from :keyword:`except` *exc*, *var* to :keyword:`except` *exc* :" +"keyword:`as` *var*. See :pep:`3110`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:420 +msgid ":pep:`3115`: New Metaclass Syntax. Instead of::" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:426 +msgid "you must now use::" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:431 +msgid "" +"The module-global :data:`__metaclass__` variable is no longer supported. " +"(It was a crutch to make it easier to default to new-style classes without " +"deriving every class from :class:`object`.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:436 +msgid "" +"List comprehensions no longer support the syntactic form :samp:`[... for " +"{var} in {item1}, {item2}, ...]`. Use :samp:`[... for {var} in ({item1}, " +"{item2}, ...)]` instead. Also note that list comprehensions have different " +"semantics: they are closer to syntactic sugar for a generator expression " +"inside a :func:`list` constructor, and in particular the loop control " +"variables are no longer leaked into the surrounding scope." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:444 +msgid "" +"The *ellipsis* (``...``) can be used as an atomic expression anywhere. " +"(Previously it was only allowed in slices.) Also, it *must* now be spelled " +"as ``...``. (Previously it could also be spelled as ``. . .``, by a mere " +"accident of the grammar.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:450 +msgid "Removed Syntax" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:452 +msgid "" +":pep:`3113`: Tuple parameter unpacking removed. You can no longer write " +"``def foo(a, (b, c)): ...``. Use ``def foo(a, b_c): b, c = b_c`` instead." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:456 +msgid "Removed backticks (use :func:`repr` instead)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:458 +msgid "Removed ``<>`` (use ``!=`` instead)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:460 +msgid "" +"Removed keyword: :func:`exec` is no longer a keyword; it remains as a " +"function. (Fortunately the function syntax was also accepted in 2.x.) Also " +"note that :func:`exec` no longer takes a stream argument; instead of " +"``exec(f)`` you can use ``exec(f.read())``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:465 +msgid "Integer literals no longer support a trailing ``l`` or ``L``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:467 +msgid "String literals no longer support a leading ``u`` or ``U``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:469 +msgid "" +"The :keyword:`from` *module* :keyword:`import` ``*`` syntax is only allowed " +"at the module level, no longer inside functions." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:472 +msgid "" +"The only acceptable syntax for relative imports is :samp:`from .[{module}] " +"import {name}`. All :keyword:`import` forms not starting with ``.`` are " +"interpreted as absolute imports. (:pep:`328`)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:476 +msgid "Classic classes are gone." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:480 +msgid "Changes Already Present In Python 2.6" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:482 +msgid "" +"Since many users presumably make the jump straight from Python 2.5 to Python " +"3.0, this section reminds the reader of new features that were originally " +"designed for Python 3.0 but that were back-ported to Python 2.6. The " +"corresponding sections in :ref:`whats-new-in-2.6` should be consulted for " +"longer descriptions." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:488 +msgid "" +":ref:`pep-0343`. The :keyword:`with` statement is now a standard feature " +"and no longer needs to be imported from the :mod:`__future__`. Also check " +"out :ref:`new-26-context-managers` and :ref:`new-module-contextlib`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:493 +msgid "" +":ref:`pep-0366`. This enhances the usefulness of the :option:`-m` option " +"when the referenced module lives in a package." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:496 +msgid ":ref:`pep-0370`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:498 +msgid ":ref:`pep-0371`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:500 +msgid "" +":ref:`pep-3101`. Note: the 2.6 description mentions the :meth:`format` " +"method for both 8-bit and Unicode strings. In 3.0, only the :class:`str` " +"type (text strings with Unicode support) supports this method; the :class:" +"`bytes` type does not. The plan is to eventually make this the only API for " +"string formatting, and to start deprecating the ``%`` operator in Python 3.1." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:507 +msgid "" +":ref:`pep-3105`. This is now a standard feature and no longer needs to be " +"imported from :mod:`__future__`. More details were given above." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:510 +msgid "" +":ref:`pep-3110`. The :keyword:`except` *exc* :keyword:`as` *var* syntax is " +"now standard and :keyword:`except` *exc*, *var* is no longer supported. (Of " +"course, the :keyword:`as` *var* part is still optional.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:515 +msgid "" +":ref:`pep-3112`. The ``b\"...\"`` string literal notation (and its variants " +"like ``b'...'``, ``b\"\"\"...\"\"\"``, and ``br\"...\"``) now produces a " +"literal of type :class:`bytes`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:519 +msgid "" +":ref:`pep-3116`. The :mod:`io` module is now the standard way of doing file " +"I/O. The built-in :func:`open` function is now an alias for :func:`io.open` " +"and has additional keyword arguments *encoding*, *errors*, *newline* and " +"*closefd*. Also note that an invalid *mode* argument now raises :exc:" +"`ValueError`, not :exc:`IOError`. The binary file object underlying a text " +"file object can be accessed as :attr:`f.buffer` (but beware that the text " +"object maintains a buffer of itself in order to speed up the encoding and " +"decoding operations)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:529 +msgid "" +":ref:`pep-3118`. The old builtin :func:`buffer` is now really gone; the new " +"builtin :func:`memoryview` provides (mostly) similar functionality." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:533 +msgid "" +":ref:`pep-3119`. The :mod:`abc` module and the ABCs defined in the :mod:" +"`collections` module plays a somewhat more prominent role in the language " +"now, and built-in collection types like :class:`dict` and :class:`list` " +"conform to the :class:`collections.MutableMapping` and :class:`collections." +"MutableSequence` ABCs, respectively." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:539 +msgid "" +":ref:`pep-3127`. As mentioned above, the new octal literal notation is the " +"only one supported, and binary literals have been added." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:543 +msgid ":ref:`pep-3129`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:545 +msgid "" +":ref:`pep-3141`. The :mod:`numbers` module is another new use of ABCs, " +"defining Python's \"numeric tower\". Also note the new :mod:`fractions` " +"module which implements :class:`numbers.Rational`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:551 +msgid "Library Changes" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:553 +msgid "" +"Due to time constraints, this document does not exhaustively cover the very " +"extensive changes to the standard library. :pep:`3108` is the reference for " +"the major changes to the library. Here's a capsule review:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:558 +msgid "" +"Many old modules were removed. Some, like :mod:`gopherlib` (no longer used) " +"and :mod:`md5` (replaced by :mod:`hashlib`), were already deprecated by :pep:" +"`4`. Others were removed as a result of the removal of support for various " +"platforms such as Irix, BeOS and Mac OS 9 (see :pep:`11`). Some modules " +"were also selected for removal in Python 3.0 due to lack of use or because a " +"better replacement exists. See :pep:`3108` for an exhaustive list." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:566 +msgid "" +"The :mod:`bsddb3` package was removed because its presence in the core " +"standard library has proved over time to be a particular burden for the core " +"developers due to testing instability and Berkeley DB's release schedule. " +"However, the package is alive and well, externally maintained at https://www." +"jcea.es/programacion/pybsddb.htm." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:572 +msgid "" +"Some modules were renamed because their old name disobeyed :pep:`8`, or for " +"various other reasons. Here's the list:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:576 ../Doc/whatsnew/3.2.rst:1803 +msgid "Old Name" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:576 +msgid "New Name" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:578 +msgid "_winreg" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:578 ../Doc/whatsnew/3.6.rst:1062 +msgid "winreg" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:579 +msgid "ConfigParser" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:579 ../Doc/whatsnew/3.2.rst:2123 +#: ../Doc/whatsnew/3.5.rst:990 +msgid "configparser" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:580 +msgid "copy_reg" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:580 +msgid "copyreg" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:581 +msgid "Queue" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:581 +msgid "queue" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:582 +msgid "SocketServer" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:582 ../Doc/whatsnew/3.3.rst:1906 +#: ../Doc/whatsnew/3.6.rst:875 +msgid "socketserver" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:583 +msgid "markupbase" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:583 +msgid "_markupbase" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:584 +msgid "repr" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:584 ../Doc/whatsnew/3.2.rst:1139 +msgid "reprlib" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:585 +msgid "test.test_support" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:585 +msgid "test.support" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:588 +msgid "" +"A common pattern in Python 2.x is to have one version of a module " +"implemented in pure Python, with an optional accelerated version implemented " +"as a C extension; for example, :mod:`pickle` and :mod:`cPickle`. This " +"places the burden of importing the accelerated version and falling back on " +"the pure Python version on each user of these modules. In Python 3.0, the " +"accelerated versions are considered implementation details of the pure " +"Python versions. Users should always import the standard version, which " +"attempts to import the accelerated version and falls back to the pure Python " +"version. The :mod:`pickle` / :mod:`cPickle` pair received this treatment. " +"The :mod:`profile` module is on the list for 3.1. The :mod:`StringIO` " +"module has been turned into a class in the :mod:`io` module." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:602 +msgid "" +"Some related modules have been grouped into packages, and usually the " +"submodule names have been simplified. The resulting new packages are:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:606 +msgid "" +":mod:`dbm` (:mod:`anydbm`, :mod:`dbhash`, :mod:`dbm`, :mod:`dumbdbm`, :mod:" +"`gdbm`, :mod:`whichdb`)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:609 +msgid ":mod:`html` (:mod:`HTMLParser`, :mod:`htmlentitydefs`)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:611 +msgid "" +":mod:`http` (:mod:`httplib`, :mod:`BaseHTTPServer`, :mod:`CGIHTTPServer`, :" +"mod:`SimpleHTTPServer`, :mod:`Cookie`, :mod:`cookielib`)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:615 +msgid "" +":mod:`tkinter` (all :mod:`Tkinter`-related modules except :mod:`turtle`). " +"The target audience of :mod:`turtle` doesn't really care about :mod:" +"`tkinter`. Also note that as of Python 2.6, the functionality of :mod:" +"`turtle` has been greatly enhanced." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:620 +msgid "" +":mod:`urllib` (:mod:`urllib`, :mod:`urllib2`, :mod:`urlparse`, :mod:" +"`robotparse`)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:623 +msgid "" +":mod:`xmlrpc` (:mod:`xmlrpclib`, :mod:`DocXMLRPCServer`, :mod:" +"`SimpleXMLRPCServer`)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:626 +msgid "" +"Some other changes to standard library modules, not covered by :pep:`3108`:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:629 +msgid "Killed :mod:`sets`. Use the built-in :func:`set` class." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:631 +msgid "" +"Cleanup of the :mod:`sys` module: removed :func:`sys.exitfunc`, :func:`sys." +"exc_clear`, :data:`sys.exc_type`, :data:`sys.exc_value`, :data:`sys." +"exc_traceback`. (Note that :data:`sys.last_type` etc. remain.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:636 +msgid "" +"Cleanup of the :class:`array.array` type: the :meth:`read` and :meth:`write` " +"methods are gone; use :meth:`fromfile` and :meth:`tofile` instead. Also, " +"the ``'c'`` typecode for array is gone -- use either ``'b'`` for bytes or " +"``'u'`` for Unicode characters." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:642 +msgid "" +"Cleanup of the :mod:`operator` module: removed :func:`sequenceIncludes` and :" +"func:`isCallable`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:645 +msgid "" +"Cleanup of the :mod:`thread` module: :func:`acquire_lock` and :func:" +"`release_lock` are gone; use :func:`acquire` and :func:`release` instead." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:649 +msgid "Cleanup of the :mod:`random` module: removed the :func:`jumpahead` API." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:651 +msgid "The :mod:`new` module is gone." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:653 +msgid "" +"The functions :func:`os.tmpnam`, :func:`os.tempnam` and :func:`os.tmpfile` " +"have been removed in favor of the :mod:`tempfile` module." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:657 +msgid "" +"The :mod:`tokenize` module has been changed to work with bytes. The main " +"entry point is now :func:`tokenize.tokenize`, instead of generate_tokens." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:661 +msgid "" +":data:`string.letters` and its friends (:data:`string.lowercase` and :data:" +"`string.uppercase`) are gone. Use :data:`string.ascii_letters` etc. " +"instead. (The reason for the removal is that :data:`string.letters` and " +"friends had locale-specific behavior, which is a bad idea for such " +"attractively-named global \"constants\".)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:668 +msgid "" +"Renamed module :mod:`__builtin__` to :mod:`builtins` (removing the " +"underscores, adding an 's'). The :data:`__builtins__` variable found in " +"most global namespaces is unchanged. To modify a builtin, you should use :" +"mod:`builtins`, not :data:`__builtins__`!" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:675 +msgid ":pep:`3101`: A New Approach To String Formatting" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:677 +msgid "" +"A new system for built-in string formatting operations replaces the ``%`` " +"string formatting operator. (However, the ``%`` operator is still " +"supported; it will be deprecated in Python 3.1 and removed from the " +"language at some later time.) Read :pep:`3101` for the full scoop." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:685 +msgid "Changes To Exceptions" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:687 +msgid "" +"The APIs for raising and catching exception have been cleaned up and new " +"powerful features added:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:690 +msgid "" +":pep:`352`: All exceptions must be derived (directly or indirectly) from :" +"exc:`BaseException`. This is the root of the exception hierarchy. This is " +"not new as a recommendation, but the *requirement* to inherit from :exc:" +"`BaseException` is new. (Python 2.6 still allowed classic classes to be " +"raised, and placed no restriction on what you can catch.) As a consequence, " +"string exceptions are finally truly and utterly dead." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:698 +msgid "" +"Almost all exceptions should actually derive from :exc:`Exception`; :exc:" +"`BaseException` should only be used as a base class for exceptions that " +"should only be handled at the top level, such as :exc:`SystemExit` or :exc:" +"`KeyboardInterrupt`. The recommended idiom for handling all exceptions " +"except for this latter category is to use :keyword:`except` :exc:`Exception`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:705 +msgid ":exc:`StandardError` was removed." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:707 +msgid "" +"Exceptions no longer behave as sequences. Use the :attr:`args` attribute " +"instead." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:710 +msgid "" +":pep:`3109`: Raising exceptions. You must now use :samp:`raise {Exception}" +"({args})` instead of :samp:`raise {Exception}, {args}`. Additionally, you " +"can no longer explicitly specify a traceback; instead, if you *have* to do " +"this, you can assign directly to the :attr:`__traceback__` attribute (see " +"below)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:716 +msgid "" +":pep:`3110`: Catching exceptions. You must now use :samp:`except " +"{SomeException} as {variable}` instead of :samp:`except {SomeException}, " +"{variable}`. Moreover, the *variable* is explicitly deleted when the :" +"keyword:`except` block is left." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:722 +msgid "" +":pep:`3134`: Exception chaining. There are two cases: implicit chaining and " +"explicit chaining. Implicit chaining happens when an exception is raised in " +"an :keyword:`except` or :keyword:`finally` handler block. This usually " +"happens due to a bug in the handler block; we call this a *secondary* " +"exception. In this case, the original exception (that was being handled) is " +"saved as the :attr:`__context__` attribute of the secondary exception. " +"Explicit chaining is invoked with this syntax::" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:733 +msgid "" +"(where *primary_exception* is any expression that produces an exception " +"object, probably an exception that was previously caught). In this case, the " +"primary exception is stored on the :attr:`__cause__` attribute of the " +"secondary exception. The traceback printed when an unhandled exception " +"occurs walks the chain of :attr:`__cause__` and :attr:`__context__` " +"attributes and prints a separate traceback for each component of the chain, " +"with the primary exception at the top. (Java users may recognize this " +"behavior.)" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:742 +msgid "" +":pep:`3134`: Exception objects now store their traceback as the :attr:" +"`__traceback__` attribute. This means that an exception object now contains " +"all the information pertaining to an exception, and there are fewer reasons " +"to use :func:`sys.exc_info` (though the latter is not removed)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:748 +msgid "" +"A few exception messages are improved when Windows fails to load an " +"extension module. For example, ``error code 193`` is now ``%1 is not a " +"valid Win32 application``. Strings now deal with non-English locales." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:755 +msgid "Miscellaneous Other Changes" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:758 +msgid "Operators And Special Methods" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:760 +msgid "" +"``!=`` now returns the opposite of ``==``, unless ``==`` returns :data:" +"`NotImplemented`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:763 +msgid "" +"The concept of \"unbound methods\" has been removed from the language. When " +"referencing a method as a class attribute, you now get a plain function " +"object." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:767 +msgid "" +":meth:`__getslice__`, :meth:`__setslice__` and :meth:`__delslice__` were " +"killed. The syntax ``a[i:j]`` now translates to ``a.__getitem__(slice(i, " +"j))`` (or :meth:`__setitem__` or :meth:`__delitem__`, when used as an " +"assignment or deletion target, respectively)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:773 +msgid "" +":pep:`3114`: the standard :meth:`next` method has been renamed to :meth:" +"`~iterator.__next__`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:776 +msgid "" +"The :meth:`__oct__` and :meth:`__hex__` special methods are removed -- :func:" +"`oct` and :func:`hex` use :meth:`__index__` now to convert the argument to " +"an integer." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:780 +msgid "Removed support for :attr:`__members__` and :attr:`__methods__`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:782 +msgid "" +"The function attributes named :attr:`func_X` have been renamed to use the :" +"data:`__X__` form, freeing up these names in the function attribute " +"namespace for user-defined attributes. To wit, :attr:`func_closure`, :attr:" +"`func_code`, :attr:`func_defaults`, :attr:`func_dict`, :attr:`func_doc`, :" +"attr:`func_globals`, :attr:`func_name` were renamed to :attr:`__closure__`, :" +"attr:`__code__`, :attr:`__defaults__`, :attr:`~object.__dict__`, :attr:" +"`__doc__`, :attr:`__globals__`, :attr:`~definition.__name__`, respectively." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:792 +msgid ":meth:`__nonzero__` is now :meth:`__bool__`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:795 +msgid "Builtins" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:797 +msgid "" +":pep:`3135`: New :func:`super`. You can now invoke :func:`super` without " +"arguments and (assuming this is in a regular instance method defined inside " +"a :keyword:`class` statement) the right class and instance will " +"automatically be chosen. With arguments, the behavior of :func:`super` is " +"unchanged." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:803 +msgid "" +":pep:`3111`: :func:`raw_input` was renamed to :func:`input`. That is, the " +"new :func:`input` function reads a line from :data:`sys.stdin` and returns " +"it with the trailing newline stripped. It raises :exc:`EOFError` if the " +"input is terminated prematurely. To get the old behavior of :func:`input`, " +"use ``eval(input())``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:809 +msgid "" +"A new built-in function :func:`next` was added to call the :meth:`~iterator." +"__next__` method on an object." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:812 +msgid "" +"The :func:`round` function rounding strategy and return type have changed. " +"Exact halfway cases are now rounded to the nearest even result instead of " +"away from zero. (For example, ``round(2.5)`` now returns ``2`` rather than " +"``3``.) ``round(x[, n])`` now delegates to ``x.__round__([n])`` instead of " +"always returning a float. It generally returns an integer when called with " +"a single argument and a value of the same type as ``x`` when called with two " +"arguments." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:821 +msgid "Moved :func:`intern` to :func:`sys.intern`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:823 +msgid "" +"Removed: :func:`apply`. Instead of ``apply(f, args)`` use ``f(*args)``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:826 +msgid "" +"Removed :func:`callable`. Instead of ``callable(f)`` you can use " +"``isinstance(f, collections.Callable)``. The :func:`operator.isCallable` " +"function is also gone." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:830 +msgid "" +"Removed :func:`coerce`. This function no longer serves a purpose now that " +"classic classes are gone." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:833 +msgid "" +"Removed :func:`execfile`. Instead of ``execfile(fn)`` use ``exec(open(fn)." +"read())``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:836 +msgid "" +"Removed the :class:`file` type. Use :func:`open`. There are now several " +"different kinds of streams that open can return in the :mod:`io` module." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:839 +msgid "" +"Removed :func:`reduce`. Use :func:`functools.reduce` if you really need it; " +"however, 99 percent of the time an explicit :keyword:`for` loop is more " +"readable." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:843 +msgid "Removed :func:`reload`. Use :func:`imp.reload`." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:845 +msgid "" +"Removed. :meth:`dict.has_key` -- use the :keyword:`in` operator instead." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:854 +msgid "" +"Due to time constraints, here is a *very* incomplete list of changes to the " +"C API." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:857 +msgid "" +"Support for several platforms was dropped, including but not limited to Mac " +"OS 9, BeOS, RISCOS, Irix, and Tru64." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:860 +msgid ":pep:`3118`: New Buffer API." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:862 +msgid ":pep:`3121`: Extension Module Initialization & Finalization." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:864 +msgid ":pep:`3123`: Making :c:macro:`PyObject_HEAD` conform to standard C." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:866 +msgid "No more C API support for restricted execution." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:868 +msgid "" +":c:func:`PyNumber_Coerce`, :c:func:`PyNumber_CoerceEx`, :c:func:" +"`PyMember_Get`, and :c:func:`PyMember_Set` C APIs are removed." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:871 +msgid "" +"New C API :c:func:`PyImport_ImportModuleNoBlock`, works like :c:func:" +"`PyImport_ImportModule` but won't block on the import lock (returning an " +"error instead)." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:875 +msgid "" +"Renamed the boolean conversion C-level slot and method: ``nb_nonzero`` is " +"now ``nb_bool``." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:878 +msgid "" +"Removed :c:macro:`METH_OLDARGS` and :c:macro:`WITH_CYCLE_GC` from the C API." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:884 +msgid "Performance" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:886 +msgid "" +"The net result of the 3.0 generalizations is that Python 3.0 runs the " +"pystone benchmark around 10% slower than Python 2.5. Most likely the " +"biggest cause is the removal of special-casing for small integers. There's " +"room for improvement, but it will happen after 3.0 is released!" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:896 +msgid "Porting To Python 3.0" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:898 +msgid "" +"For porting existing Python 2.5 or 2.6 source code to Python 3.0, the best " +"strategy is the following:" +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:901 +msgid "(Prerequisite:) Start with excellent test coverage." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:903 +msgid "" +"Port to Python 2.6. This should be no more work than the average port from " +"Python 2.x to Python 2.(x+1). Make sure all your tests pass." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:907 +msgid "" +"(Still using 2.6:) Turn on the :option:`-3` command line switch. This " +"enables warnings about features that will be removed (or change) in 3.0. " +"Run your test suite again, and fix code that you get warnings about until " +"there are no warnings left, and all your tests still pass." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:913 +msgid "" +"Run the ``2to3`` source-to-source translator over your source code tree. " +"(See :ref:`2to3-reference` for more on this tool.) Run the result of the " +"translation under Python 3.0. Manually fix up any remaining issues, fixing " +"problems until all tests pass again." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:918 +msgid "" +"It is not recommended to try to write source code that runs unchanged under " +"both Python 2.6 and 3.0; you'd have to use a very contorted coding style, e." +"g. avoiding ``print`` statements, metaclasses, and much more. If you are " +"maintaining a library that needs to support both Python 2.6 and Python 3.0, " +"the best approach is to modify step 3 above by editing the 2.6 version of " +"the source code and running the ``2to3`` translator again, rather than " +"editing the 3.0 version of the source code." +msgstr "" + +#: ../Doc/whatsnew/3.0.rst:927 +msgid "" +"For porting C extensions to Python 3.0, please see :ref:`cporting-howto`." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:3 +msgid "What's New In Python 3.1" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:5 ../Doc/whatsnew/3.2.rst:5 +msgid "Raymond Hettinger" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:49 +msgid "This article explains the new features in Python 3.1, compared to 3.0." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:53 +msgid "PEP 372: Ordered Dictionaries" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:55 +msgid "" +"Regular Python dictionaries iterate over key/value pairs in arbitrary order. " +"Over the years, a number of authors have written alternative implementations " +"that remember the order that the keys were originally inserted. Based on " +"the experiences from those implementations, a new :class:`collections." +"OrderedDict` class has been introduced." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:61 +msgid "" +"The OrderedDict API is substantially the same as regular dictionaries but " +"will iterate over keys and values in a guaranteed order depending on when a " +"key was first inserted. If a new entry overwrites an existing entry, the " +"original insertion position is left unchanged. Deleting an entry and " +"reinserting it will move it to the end." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:67 +msgid "" +"The standard library now supports use of ordered dictionaries in several " +"modules. The :mod:`configparser` module uses them by default. This lets " +"configuration files be read, modified, and then written back in their " +"original order. The *_asdict()* method for :func:`collections.namedtuple` " +"now returns an ordered dictionary with the values appearing in the same " +"order as the underlying tuple indicies. The :mod:`json` module is being " +"built-out with an *object_pairs_hook* to allow OrderedDicts to be built by " +"the decoder. Support was also added for third-party tools like `PyYAML " +"`_." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:79 +msgid ":pep:`372` - Ordered Dictionaries" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:79 +msgid "" +"PEP written by Armin Ronacher and Raymond Hettinger. Implementation written " +"by Raymond Hettinger." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:86 +msgid "" +"The built-in :func:`format` function and the :meth:`str.format` method use a " +"mini-language that now includes a simple, non-locale aware way to format a " +"number with a thousands separator. That provides a way to humanize a " +"program's output, improving its professional appearance and readability::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:100 +msgid "" +"The supported types are :class:`int`, :class:`float`, :class:`complex` and :" +"class:`decimal.Decimal`." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:103 +msgid "" +"Discussions are underway about how to specify alternative separators like " +"dots, spaces, apostrophes, or underscores. Locale-aware applications should " +"use the existing *n* format specifier which already has some support for " +"thousands separators." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:111 +msgid "" +"PEP written by Raymond Hettinger and implemented by Eric Smith and Mark " +"Dickinson." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:120 +msgid "" +"Directories and zip archives containing a :file:`__main__.py` file can now " +"be executed directly by passing their name to the interpreter. The directory/" +"zipfile is automatically inserted as the first entry in sys.path. " +"(Suggestion and initial patch by Andy Chu; revised patch by Phillip J. Eby " +"and Nick Coghlan; :issue:`1739468`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:126 +msgid "" +"The :func:`int` type gained a ``bit_length`` method that returns the number " +"of bits necessary to represent its argument in binary::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:140 +msgid "" +"(Contributed by Fredrik Johansson, Victor Stinner, Raymond Hettinger, and " +"Mark Dickinson; :issue:`3439`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:143 +msgid "" +"The fields in :func:`format` strings can now be automatically numbered::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:149 +msgid "" +"Formerly, the string would have required numbered fields such as: ``'Sir {0} " +"of {1}'``." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:152 +msgid "(Contributed by Eric Smith; :issue:`5237`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:154 +msgid "" +"The :func:`string.maketrans` function is deprecated and is replaced by new " +"static methods, :meth:`bytes.maketrans` and :meth:`bytearray.maketrans`. " +"This change solves the confusion around which types were supported by the :" +"mod:`string` module. Now, :class:`str`, :class:`bytes`, and :class:" +"`bytearray` each have their own **maketrans** and **translate** methods with " +"intermediate translation tables of the appropriate type." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:161 ../Doc/whatsnew/3.2.rst:2671 +msgid "(Contributed by Georg Brandl; :issue:`5675`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:163 +msgid "" +"The syntax of the :keyword:`with` statement now allows multiple context " +"managers in a single statement::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:171 +msgid "" +"With the new syntax, the :func:`contextlib.nested` function is no longer " +"needed and is now deprecated." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:174 ../Doc/whatsnew/3.2.rst:2684 +msgid "" +"(Contributed by Georg Brandl and Mattias Brändström; `appspot issue 53094 " +"`_.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:177 +msgid "" +"``round(x, n)`` now returns an integer if *x* is an integer. Previously it " +"returned a float::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:183 +msgid "(Contributed by Mark Dickinson; :issue:`4707`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:185 +msgid "" +"Python now uses David Gay's algorithm for finding the shortest floating " +"point representation that doesn't change its value. This should help " +"mitigate some of the confusion surrounding binary floating point numbers." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:190 +msgid "" +"The significance is easily seen with a number like ``1.1`` which does not " +"have an exact equivalent in binary floating point. Since there is no exact " +"equivalent, an expression like ``float('1.1')`` evaluates to the nearest " +"representable value which is ``0x1.199999999999ap+0`` in hex or " +"``1.100000000000000088817841970012523233890533447265625`` in decimal. That " +"nearest value was and still is used in subsequent floating point " +"calculations." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:198 +msgid "" +"What is new is how the number gets displayed. Formerly, Python used a " +"simple approach. The value of ``repr(1.1)`` was computed as ``format(1.1, " +"'.17g')`` which evaluated to ``'1.1000000000000001'``. The advantage of " +"using 17 digits was that it relied on IEEE-754 guarantees to assure that " +"``eval(repr(1.1))`` would round-trip exactly to its original value. The " +"disadvantage is that many people found the output to be confusing (mistaking " +"intrinsic limitations of binary floating point representation as being a " +"problem with Python itself)." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:207 +msgid "" +"The new algorithm for ``repr(1.1)`` is smarter and returns ``'1.1'``. " +"Effectively, it searches all equivalent string representations (ones that " +"get stored with the same underlying float value) and returns the shortest " +"representation." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:212 +msgid "" +"The new algorithm tends to emit cleaner representations when possible, but " +"it does not change the underlying values. So, it is still the case that " +"``1.1 + 2.2 != 3.3`` even though the representations may suggest otherwise." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:216 +msgid "" +"The new algorithm depends on certain features in the underlying floating " +"point implementation. If the required features are not found, the old " +"algorithm will continue to be used. Also, the text pickle protocols assure " +"cross-platform portability by using the old algorithm." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:221 +msgid "(Contributed by Eric Smith and Mark Dickinson; :issue:`1580`)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:226 +msgid "" +"Added a :class:`collections.Counter` class to support convenient counting of " +"unique items in a sequence or iterable::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:232 +msgid "(Contributed by Raymond Hettinger; :issue:`1696199`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:234 +msgid "" +"Added a new module, :mod:`tkinter.ttk` for access to the Tk themed widget " +"set. The basic idea of ttk is to separate, to the extent possible, the code " +"implementing a widget's behavior from the code implementing its appearance." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:238 +msgid "(Contributed by Guilherme Polo; :issue:`2983`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:240 +msgid "" +"The :class:`gzip.GzipFile` and :class:`bz2.BZ2File` classes now support the " +"context management protocol::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:247 ../Doc/whatsnew/3.2.rst:2323 +msgid "(Contributed by Antoine Pitrou.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:249 +msgid "" +"The :mod:`decimal` module now supports methods for creating a decimal object " +"from a binary :class:`float`. The conversion is exact but can sometimes be " +"surprising::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:256 +msgid "" +"The long decimal result shows the actual binary fraction being stored for " +"*1.1*. The fraction has many digits because *1.1* cannot be exactly " +"represented in binary." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:260 +msgid "(Contributed by Raymond Hettinger and Mark Dickinson.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:262 +msgid "" +"The :mod:`itertools` module grew two new functions. The :func:`itertools." +"combinations_with_replacement` function is one of four for generating " +"combinatorics including permutations and Cartesian products. The :func:" +"`itertools.compress` function mimics its namesake from APL. Also, the " +"existing :func:`itertools.count` function now has an optional *step* " +"argument and can accept any type of counting sequence including :class:" +"`fractions.Fraction` and :class:`decimal.Decimal`::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:283 +msgid "" +":func:`collections.namedtuple` now supports a keyword argument *rename* " +"which lets invalid fieldnames be automatically converted to positional names " +"in the form _0, _1, etc. This is useful when the field names are being " +"created by an external source such as a CSV header, SQL field list, or user " +"input::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:300 +msgid "(Contributed by Raymond Hettinger; :issue:`1818`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:302 +msgid "" +"The :func:`re.sub`, :func:`re.subn` and :func:`re.split` functions now " +"accept a flags parameter." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:305 +msgid "(Contributed by Gregory Smith.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:307 +msgid "" +"The :mod:`logging` module now implements a simple :class:`logging." +"NullHandler` class for applications that are not using logging but are " +"calling library code that does. Setting-up a null handler will suppress " +"spurious warnings such as \"No handlers could be found for logger foo\"::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:315 +msgid "(Contributed by Vinay Sajip; :issue:`4384`)." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:317 +msgid "" +"The :mod:`runpy` module which supports the ``-m`` command line switch now " +"supports the execution of packages by looking for and executing a " +"``__main__`` submodule when a package name is supplied." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:321 +msgid "(Contributed by Andi Vajda; :issue:`4195`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:323 +msgid "" +"The :mod:`pdb` module can now access and display source code loaded via :mod:" +"`zipimport` (or any other conformant :pep:`302` loader)." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:326 +msgid "(Contributed by Alexander Belopolsky; :issue:`4201`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:328 +msgid ":class:`functools.partial` objects can now be pickled." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:330 +msgid "" +"(Suggested by Antoine Pitrou and Jesse Noller. Implemented by Jack " +"Diederich; :issue:`5228`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:333 +msgid "" +"Add :mod:`pydoc` help topics for symbols so that ``help('@')`` works as " +"expected in the interactive environment." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:336 +msgid "(Contributed by David Laban; :issue:`4739`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:338 +msgid "" +"The :mod:`unittest` module now supports skipping individual tests or classes " +"of tests. And it supports marking a test as an expected failure, a test that " +"is known to be broken, but shouldn't be counted as a failure on a " +"TestResult::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:353 +msgid "" +"Also, tests for exceptions have been builtout to work with context managers " +"using the :keyword:`with` statement::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:360 +msgid "" +"In addition, several new assertion methods were added including :func:" +"`assertSetEqual`, :func:`assertDictEqual`, :func:" +"`assertDictContainsSubset`, :func:`assertListEqual`, :func:" +"`assertTupleEqual`, :func:`assertSequenceEqual`, :func:" +"`assertRaisesRegexp`, :func:`assertIsNone`, and :func:`assertIsNotNone`." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:367 +msgid "(Contributed by Benjamin Peterson and Antoine Pitrou.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:369 +msgid "" +"The :mod:`io` module has three new constants for the :meth:`seek` method :" +"data:`SEEK_SET`, :data:`SEEK_CUR`, and :data:`SEEK_END`." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:372 +msgid "The :attr:`sys.version_info` tuple is now a named tuple::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:377 +msgid "(Contributed by Ross Light; :issue:`4285`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:379 +msgid "The :mod:`nntplib` and :mod:`imaplib` modules now support IPv6." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:381 +msgid "(Contributed by Derek Morr; :issue:`1655` and :issue:`1664`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:383 +msgid "" +"The :mod:`pickle` module has been adapted for better interoperability with " +"Python 2.x when used with protocol 2 or lower. The reorganization of the " +"standard library changed the formal reference for many objects. For " +"example, ``__builtin__.set`` in Python 2 is called ``builtins.set`` in " +"Python 3. This change confounded efforts to share data between different " +"versions of Python. But now when protocol 2 or lower is selected, the " +"pickler will automatically use the old Python 2 names for both loading and " +"dumping. This remapping is turned-on by default but can be disabled with the " +"*fix_imports* option::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:399 +msgid "" +"An unfortunate but unavoidable side-effect of this change is that protocol 2 " +"pickles produced by Python 3.1 won't be readable with Python 3.0. The latest " +"pickle protocol, protocol 3, should be used when migrating data between " +"Python 3.x implementations, as it doesn't attempt to remain compatible with " +"Python 2.x." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:405 +msgid "" +"(Contributed by Alexandre Vassalotti and Antoine Pitrou, :issue:`6137`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:407 +msgid "" +"A new module, :mod:`importlib` was added. It provides a complete, portable, " +"pure Python reference implementation of the :keyword:`import` statement and " +"its counterpart, the :func:`__import__` function. It represents a " +"substantial step forward in documenting and defining the actions that take " +"place during imports." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:418 ../Doc/whatsnew/3.3.rst:2151 +msgid "Major performance enhancements have been added:" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:420 +msgid "" +"The new I/O library (as defined in :pep:`3116`) was mostly written in Python " +"and quickly proved to be a problematic bottleneck in Python 3.0. In Python " +"3.1, the I/O library has been entirely rewritten in C and is 2 to 20 times " +"faster depending on the task at hand. The pure Python version is still " +"available for experimentation purposes through the ``_pyio`` module." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:427 +msgid "(Contributed by Amaury Forgeot d'Arc and Antoine Pitrou.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:429 +msgid "" +"Added a heuristic so that tuples and dicts containing only untrackable " +"objects are not tracked by the garbage collector. This can reduce the size " +"of collections and therefore the garbage collection overhead on long-running " +"programs, depending on their particular use of datatypes." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:434 +msgid "(Contributed by Antoine Pitrou, :issue:`4688`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:436 +msgid "" +"Enabling a configure option named ``--with-computed-gotos`` on compilers " +"that support it (notably: gcc, SunPro, icc), the bytecode evaluation loop is " +"compiled with a new dispatch mechanism which gives speedups of up to 20%, " +"depending on the system, the compiler, and the benchmark." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:442 +msgid "" +"(Contributed by Antoine Pitrou along with a number of other participants, :" +"issue:`4753`)." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:445 +msgid "" +"The decoding of UTF-8, UTF-16 and LATIN-1 is now two to four times faster." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:448 +msgid "" +"(Contributed by Antoine Pitrou and Amaury Forgeot d'Arc, :issue:`4868`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:450 +msgid "" +"The :mod:`json` module now has a C extension to substantially improve its " +"performance. In addition, the API was modified so that json works only " +"with :class:`str`, not with :class:`bytes`. That change makes the module " +"closely match the `JSON specification `_ which is defined " +"in terms of Unicode." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:456 +msgid "" +"(Contributed by Bob Ippolito and converted to Py3.1 by Antoine Pitrou and " +"Benjamin Peterson; :issue:`4136`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:459 +msgid "" +"Unpickling now interns the attribute names of pickled objects. This saves " +"memory and allows pickles to be smaller." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:462 +msgid "(Contributed by Jake McGuire and Antoine Pitrou; :issue:`5084`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:465 ../Doc/whatsnew/3.2.rst:2489 +#: ../../../Misc/NEWS:684 ../../../Misc/NEWS:956 ../../../Misc/NEWS:1155 +#: ../../../Misc/NEWS:1411 ../../../Misc/NEWS:2537 ../../../Misc/NEWS:3142 +#: ../../../Misc/NEWS:3473 ../../../Misc/NEWS:3979 ../../../Misc/NEWS:5996 +#: ../../../Misc/NEWS:6714 ../../../Misc/NEWS:6916 ../../../Misc/NEWS:7318 +#: ../../../Misc/NEWS:8206 ../../../Misc/NEWS:8472 ../../../Misc/NEWS:10082 +msgid "IDLE" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:467 +msgid "" +"IDLE's format menu now provides an option to strip trailing whitespace from " +"a source file." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:470 +msgid "(Contributed by Roger D. Serwy; :issue:`5150`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:477 +msgid "" +"Integers are now stored internally either in base 2**15 or in base 2**30, " +"the base being determined at build time. Previously, they were always " +"stored in base 2**15. Using base 2**30 gives significant performance " +"improvements on 64-bit machines, but benchmark results on 32-bit machines " +"have been mixed. Therefore, the default is to use base 2**30 on 64-bit " +"machines and base 2**15 on 32-bit machines; on Unix, there's a new configure " +"option ``--enable-big-digits`` that can be used to override this default." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:486 +msgid "" +"Apart from the performance improvements this change should be invisible to " +"end users, with one exception: for testing and debugging purposes there's a " +"new :attr:`sys.int_info` that provides information about the internal " +"format, giving the number of bits per digit and the size in bytes of the C " +"type used to store each digit::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:498 +msgid "" +"The :c:func:`PyLong_AsUnsignedLongLong()` function now handles a negative " +"*pylong* by raising :exc:`OverflowError` instead of :exc:`TypeError`." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:501 +msgid "(Contributed by Mark Dickinson and Lisandro Dalcrin; :issue:`5175`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:503 +msgid "" +"Deprecated :c:func:`PyNumber_Int`. Use :c:func:`PyNumber_Long` instead." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:505 +msgid "(Contributed by Mark Dickinson; :issue:`4910`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:507 +msgid "" +"Added a new :c:func:`PyOS_string_to_double` function to replace the " +"deprecated functions :c:func:`PyOS_ascii_strtod` and :c:func:" +"`PyOS_ascii_atof`." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:510 +msgid "(Contributed by Mark Dickinson; :issue:`5914`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:512 +msgid "" +"Added :c:type:`PyCapsule` as a replacement for the :c:type:`PyCObject` API. " +"The principal difference is that the new type has a well defined interface " +"for passing typing safety information and a less complicated signature for " +"calling a destructor. The old type had a problematic API and is now " +"deprecated." +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:518 +msgid "(Contributed by Larry Hastings; :issue:`5630`.)" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:521 +msgid "Porting to Python 3.1" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:526 +msgid "" +"The new floating point string representations can break existing doctests. " +"For example::" +msgstr "" + +#: ../Doc/whatsnew/3.1.rst:549 +msgid "" +"The automatic name remapping in the pickle module for protocol 2 or lower " +"can make Python 3.1 pickles unreadable in Python 3.0. One solution is to " +"use protocol 3. Another solution is to set the *fix_imports* option to " +"**False**. See the discussion above for more details." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:3 +msgid "What's New In Python 3.2" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:51 +msgid "" +"This article explains the new features in Python 3.2 as compared to 3.1. It " +"focuses on a few highlights and gives a few examples. For full details, see " +"the `Misc/NEWS `_ file." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:57 +msgid ":pep:`392` - Python 3.2 Release Schedule" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:61 +msgid "PEP 384: Defining a Stable ABI" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:63 +msgid "" +"In the past, extension modules built for one Python version were often not " +"usable with other Python versions. Particularly on Windows, every feature " +"release of Python required rebuilding all extension modules that one wanted " +"to use. This requirement was the result of the free access to Python " +"interpreter internals that extension modules could use." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:69 +msgid "" +"With Python 3.2, an alternative approach becomes available: extension " +"modules which restrict themselves to a limited API (by defining " +"Py_LIMITED_API) cannot use many of the internals, but are constrained to a " +"set of API functions that are promised to be stable for several releases. As " +"a consequence, extension modules built for 3.2 in that mode will also work " +"with 3.3, 3.4, and so on. Extension modules that make use of details of " +"memory structures can still be built, but will need to be recompiled for " +"every feature release." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:80 +msgid ":pep:`384` - Defining a Stable ABI" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:81 +msgid "PEP written by Martin von Löwis." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:85 +msgid "PEP 389: Argparse Command Line Parsing Module" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:87 +msgid "" +"A new module for command line parsing, :mod:`argparse`, was introduced to " +"overcome the limitations of :mod:`optparse` which did not provide support " +"for positional arguments (not just options), subcommands, required options " +"and other common patterns of specifying and validating options." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:92 +msgid "" +"This module has already had widespread success in the community as a third-" +"party module. Being more fully featured than its predecessor, the :mod:" +"`argparse` module is now the preferred module for command-line processing. " +"The older module is still being kept available because of the substantial " +"amount of legacy code that depends on it." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:98 +msgid "" +"Here's an annotated example parser showing features like limiting results to " +"a set of choices, specifying a *metavar* in the help screen, validating that " +"one or more positional arguments is present, and making a required option::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:117 +msgid "Example of calling the parser on a command string::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:128 +msgid "Example of the parser's automatically generated help::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:147 +msgid "" +"An especially nice :mod:`argparse` feature is the ability to define " +"subparsers, each with their own argument patterns and help displays::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:173 +msgid ":pep:`389` - New Command Line Parsing Module" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:173 +msgid "PEP written by Steven Bethard." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:175 +msgid "" +":ref:`upgrading-optparse-code` for details on the differences from :mod:" +"`optparse`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:179 +msgid "PEP 391: Dictionary Based Configuration for Logging" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:181 +msgid "" +"The :mod:`logging` module provided two kinds of configuration, one style " +"with function calls for each option or another style driven by an external " +"file saved in a :mod:`ConfigParser` format. Those options did not provide " +"the flexibility to create configurations from JSON or YAML files, nor did " +"they support incremental configuration, which is needed for specifying " +"logger options from a command line." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:188 +msgid "" +"To support a more flexible style, the module now offers :func:`logging." +"config.dictConfig` for specifying logging configuration with plain Python " +"dictionaries. The configuration options include formatters, handlers, " +"filters, and loggers. Here's a working example of a configuration " +"dictionary::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:212 +msgid "" +"If that dictionary is stored in a file called :file:`conf.json`, it can be " +"loaded and called with code like this::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:227 +msgid ":pep:`391` - Dictionary Based Configuration for Logging" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:228 +msgid "PEP written by Vinay Sajip." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:232 +msgid "PEP 3148: The ``concurrent.futures`` module" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:234 +msgid "" +"Code for creating and managing concurrency is being collected in a new top-" +"level namespace, *concurrent*. Its first member is a *futures* package " +"which provides a uniform high-level interface for managing threads and " +"processes." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:238 +msgid "" +"The design for :mod:`concurrent.futures` was inspired by the *java.util." +"concurrent* package. In that model, a running call and its result are " +"represented by a :class:`~concurrent.futures.Future` object that abstracts " +"features common to threads, processes, and remote procedure calls. That " +"object supports status checks (running or done), timeouts, cancellations, " +"adding callbacks, and access to results or exceptions." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:245 +msgid "" +"The primary offering of the new module is a pair of executor classes for " +"launching and managing calls. The goal of the executors is to make it " +"easier to use existing tools for making parallel calls. They save the effort " +"needed to setup a pool of resources, launch the calls, create a results " +"queue, add time-out handling, and limit the total number of threads, " +"processes, or remote procedure calls." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:252 +msgid "" +"Ideally, each application should share a single executor across multiple " +"components so that process and thread limits can be centrally managed. This " +"solves the design challenge that arises when each component has its own " +"competing strategy for resource management." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:257 +msgid "" +"Both classes share a common interface with three methods: :meth:`~concurrent." +"futures.Executor.submit` for scheduling a callable and returning a :class:" +"`~concurrent.futures.Future` object; :meth:`~concurrent.futures.Executor." +"map` for scheduling many asynchronous calls at a time, and :meth:" +"`~concurrent.futures.Executor.shutdown` for freeing resources. The class is " +"a :term:`context manager` and can be used in a :keyword:`with` statement to " +"assure that resources are automatically released when currently pending " +"futures are done executing." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:266 +msgid "" +"A simple of example of :class:`~concurrent.futures.ThreadPoolExecutor` is a " +"launch of four parallel threads for copying files::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:279 +msgid ":pep:`3148` - Futures -- Execute Computations Asynchronously" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:279 +msgid "PEP written by Brian Quinlan." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:281 +msgid "" +":ref:`Code for Threaded Parallel URL reads`, an " +"example using threads to fetch multiple web pages in parallel." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:284 +msgid "" +":ref:`Code for computing prime numbers in parallel`, an example demonstrating :class:`~concurrent.futures." +"ProcessPoolExecutor`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:290 +msgid "PEP 3147: PYC Repository Directories" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:292 +msgid "" +"Python's scheme for caching bytecode in *.pyc* files did not work well in " +"environments with multiple Python interpreters. If one interpreter " +"encountered a cached file created by another interpreter, it would recompile " +"the source and overwrite the cached file, thus losing the benefits of " +"caching." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:297 +msgid "" +"The issue of \"pyc fights\" has become more pronounced as it has become " +"commonplace for Linux distributions to ship with multiple versions of " +"Python. These conflicts also arise with CPython alternatives such as Unladen " +"Swallow." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:301 +msgid "" +"To solve this problem, Python's import machinery has been extended to use " +"distinct filenames for each interpreter. Instead of Python 3.2 and Python " +"3.3 and Unladen Swallow each competing for a file called \"mymodule.pyc\", " +"they will now look for \"mymodule.cpython-32.pyc\", \"mymodule.cpython-33.pyc" +"\", and \"mymodule.unladen10.pyc\". And to prevent all of these new files " +"from cluttering source directories, the *pyc* files are now collected in a " +"\"__pycache__\" directory stored under the package directory." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:309 +msgid "" +"Aside from the filenames and target directories, the new scheme has a few " +"aspects that are visible to the programmer:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:312 +msgid "" +"Imported modules now have a :attr:`__cached__` attribute which stores the " +"name of the actual file that was imported:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:319 +msgid "" +"The tag that is unique to each interpreter is accessible from the :mod:`imp` " +"module:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:326 +msgid "" +"Scripts that try to deduce source filename from the imported file now need " +"to be smarter. It is no longer sufficient to simply strip the \"c\" from a " +"\".pyc\" filename. Instead, use the new functions in the :mod:`imp` module:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:335 +msgid "" +"The :mod:`py_compile` and :mod:`compileall` modules have been updated to " +"reflect the new naming convention and target directory. The command-line " +"invocation of *compileall* has new options: ``-i`` for specifying a list of " +"files and directories to compile and ``-b`` which causes bytecode files to " +"be written to their legacy location rather than *__pycache__*." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:342 +msgid "" +"The :mod:`importlib.abc` module has been updated with new :term:`abstract " +"base classes ` for loading bytecode files. The " +"obsolete ABCs, :class:`~importlib.abc.PyLoader` and :class:`~importlib.abc." +"PyPycLoader`, have been deprecated (instructions on how to stay Python 3.1 " +"compatible are included with the documentation)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:350 +msgid ":pep:`3147` - PYC Repository Directories" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:351 ../Doc/whatsnew/3.2.rst:382 +msgid "PEP written by Barry Warsaw." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:355 +msgid "PEP 3149: ABI Version Tagged .so Files" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:357 +msgid "" +"The PYC repository directory allows multiple bytecode cache files to be co-" +"located. This PEP implements a similar mechanism for shared object files by " +"giving them a common directory and distinct names for each version." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:361 +msgid "" +"The common directory is \"pyshared\" and the file names are made distinct by " +"identifying the Python implementation (such as CPython, PyPy, Jython, etc.), " +"the major and minor version numbers, and optional build flags (such as \"d\" " +"for debug, \"m\" for pymalloc, \"u\" for wide-unicode). For an arbitrary " +"package \"foo\", you may see these files when the distribution package is " +"installed::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:370 +msgid "" +"In Python itself, the tags are accessible from functions in the :mod:" +"`sysconfig` module::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:381 +msgid ":pep:`3149` - ABI Version Tagged .so Files" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:386 +msgid "PEP 3333: Python Web Server Gateway Interface v1.0.1" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:388 +msgid "" +"This informational PEP clarifies how bytes/text issues are to be handled by " +"the WSGI protocol. The challenge is that string handling in Python 3 is " +"most conveniently handled with the :class:`str` type even though the HTTP " +"protocol is itself bytes oriented." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:393 +msgid "" +"The PEP differentiates so-called *native strings* that are used for request/" +"response headers and metadata versus *byte strings* which are used for the " +"bodies of requests and responses." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:397 +msgid "" +"The *native strings* are always of type :class:`str` but are restricted to " +"code points between *U+0000* through *U+00FF* which are translatable to " +"bytes using *Latin-1* encoding. These strings are used for the keys and " +"values in the environment dictionary and for response headers and statuses " +"in the :func:`start_response` function. They must follow :rfc:`2616` with " +"respect to encoding. That is, they must either be *ISO-8859-1* characters or " +"use :rfc:`2047` MIME encoding." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:405 +msgid "" +"For developers porting WSGI applications from Python 2, here are the salient " +"points:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:408 +msgid "" +"If the app already used strings for headers in Python 2, no change is needed." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:410 +msgid "" +"If instead, the app encoded output headers or decoded input headers, then " +"the headers will need to be re-encoded to Latin-1. For example, an output " +"header encoded in utf-8 was using ``h.encode('utf-8')`` now needs to convert " +"from bytes to native strings using ``h.encode('utf-8').decode('latin-1')``." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:415 +msgid "" +"Values yielded by an application or sent using the :meth:`write` method must " +"be byte strings. The :func:`start_response` function and environ must use " +"native strings. The two cannot be mixed." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:419 +msgid "" +"For server implementers writing CGI-to-WSGI pathways or other CGI-style " +"protocols, the users must to be able access the environment using native " +"strings even though the underlying platform may have a different " +"convention. To bridge this gap, the :mod:`wsgiref` module has a new " +"function, :func:`wsgiref.handlers.read_environ` for transcoding CGI " +"variables from :attr:`os.environ` into native strings and returning a new " +"dictionary." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:428 +msgid ":pep:`3333` - Python Web Server Gateway Interface v1.0.1" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:429 +msgid "PEP written by Phillip Eby." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:437 +msgid "" +"String formatting for :func:`format` and :meth:`str.format` gained new " +"capabilities for the format character **#**. Previously, for integers in " +"binary, octal, or hexadecimal, it caused the output to be prefixed with " +"'0b', '0o', or '0x' respectively. Now it can also handle floats, complex, " +"and Decimal, causing the output to always have a decimal point even when no " +"digits follow it." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:449 +msgid "" +"(Suggested by Mark Dickinson and implemented by Eric Smith in :issue:`7094`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:451 +msgid "" +"There is also a new :meth:`str.format_map` method that extends the " +"capabilities of the existing :meth:`str.format` method by accepting " +"arbitrary :term:`mapping` objects. This new method makes it possible to use " +"string formatting with any of Python's many dictionary-like objects such as :" +"class:`~collections.defaultdict`, :class:`~shelve.Shelf`, :class:" +"`~configparser.ConfigParser`, or :mod:`dbm`. It is also useful with custom :" +"class:`dict` subclasses that normalize keys before look-up or that supply a :" +"meth:`__missing__` method for unknown keys::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:478 +msgid "" +"(Suggested by Raymond Hettinger and implemented by Eric Smith in :issue:" +"`6081`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:481 +msgid "" +"The interpreter can now be started with a quiet option, ``-q``, to prevent " +"the copyright and version information from being displayed in the " +"interactive mode. The option can be introspected using the :attr:`sys." +"flags` attribute:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:493 +msgid "(Contributed by Marcin Wojdyr in :issue:`1772833`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:495 +msgid "" +"The :func:`hasattr` function works by calling :func:`getattr` and detecting " +"whether an exception is raised. This technique allows it to detect methods " +"created dynamically by :meth:`__getattr__` or :meth:`__getattribute__` which " +"would otherwise be absent from the class dictionary. Formerly, *hasattr* " +"would catch any exception, possibly masking genuine errors. Now, *hasattr* " +"has been tightened to only catch :exc:`AttributeError` and let other " +"exceptions pass through::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:514 +msgid "" +"(Discovered by Yury Selivanov and fixed by Benjamin Peterson; :issue:`9666`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:516 +msgid "" +"The :func:`str` of a float or complex number is now the same as its :func:" +"`repr`. Previously, the :func:`str` form was shorter but that just caused " +"confusion and is no longer needed now that the shortest possible :func:" +"`repr` is displayed by default:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:527 +msgid "(Proposed and implemented by Mark Dickinson; :issue:`9337`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:529 +msgid "" +":class:`memoryview` objects now have a :meth:`~memoryview.release()` method " +"and they also now support the context management protocol. This allows " +"timely release of any resources that were acquired when requesting a buffer " +"from the original object." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:538 +msgid "(Added by Antoine Pitrou; :issue:`9757`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:540 +msgid "" +"Previously it was illegal to delete a name from the local namespace if it " +"occurs as a free variable in a nested block::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:549 +msgid "" +"This is now allowed. Remember that the target of an :keyword:`except` " +"clause is cleared, so this code which used to work with Python 2.6, raised " +"a :exc:`SyntaxError` with Python 3.1 and now works again::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:562 +msgid "(See :issue:`4617`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:564 +msgid "" +"The internal :c:type:`structsequence` tool now creates subclasses of tuple. " +"This means that C structures like those returned by :func:`os.stat`, :func:" +"`time.gmtime`, and :attr:`sys.version_info` now work like a :term:`named " +"tuple` and now work with functions and methods that expect a tuple as an " +"argument. This is a big step forward in making the C structures as flexible " +"as their pure Python counterparts:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:577 +msgid "" +"(Suggested by Arfrever Frehtes Taifersar Arahesis and implemented by " +"Benjamin Peterson in :issue:`8413`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:580 +msgid "" +"Warnings are now easier to control using the :envvar:`PYTHONWARNINGS` " +"environment variable as an alternative to using ``-W`` at the command line:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:587 +msgid "" +"(Suggested by Barry Warsaw and implemented by Philip Jenvey in :issue:" +"`7301`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:589 +msgid "" +"A new warning category, :exc:`ResourceWarning`, has been added. It is " +"emitted when potential issues with resource consumption or cleanup are " +"detected. It is silenced by default in normal release builds but can be " +"enabled through the means provided by the :mod:`warnings` module, or on the " +"command line." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:595 +msgid "" +"A :exc:`ResourceWarning` is issued at interpreter shutdown if the :data:`gc." +"garbage` list isn't empty, and if :attr:`gc.DEBUG_UNCOLLECTABLE` is set, all " +"uncollectable objects are printed. This is meant to make the programmer " +"aware that their code contains object finalization issues." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:600 +msgid "" +"A :exc:`ResourceWarning` is also issued when a :term:`file object` is " +"destroyed without having been explicitly closed. While the deallocator for " +"such object ensures it closes the underlying operating system resource " +"(usually, a file descriptor), the delay in deallocating the object could " +"produce various issues, especially under Windows. Here is an example of " +"enabling the warning from the command line:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:614 +msgid "" +"(Added by Antoine Pitrou and Georg Brandl in :issue:`10093` and :issue:" +"`477863`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:616 +msgid "" +":class:`range` objects now support *index* and *count* methods. This is part " +"of an effort to make more objects fully implement the :class:`collections." +"Sequence` :term:`abstract base class`. As a result, the language will have " +"a more uniform API. In addition, :class:`range` objects now support slicing " +"and negative indices, even with values larger than :attr:`sys.maxsize`. " +"This makes *range* more interoperable with lists::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:632 +msgid "" +"(Contributed by Daniel Stutzbach in :issue:`9213`, by Alexander Belopolsky " +"in :issue:`2690`, and by Nick Coghlan in :issue:`10889`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:635 +msgid "" +"The :func:`callable` builtin function from Py2.x was resurrected. It " +"provides a concise, readable alternative to using an :term:`abstract base " +"class` in an expression like ``isinstance(x, collections.Callable)``:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:644 +msgid "(See :issue:`10518`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:646 +msgid "" +"Python's import mechanism can now load modules installed in directories with " +"non-ASCII characters in the path name. This solved an aggravating problem " +"with home directories for users with non-ASCII characters in their usernames." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:650 +msgid "(Required extensive work by Victor Stinner in :issue:`9425`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:656 +msgid "" +"Python's standard library has undergone significant maintenance efforts and " +"quality improvements." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:659 +msgid "" +"The biggest news for Python 3.2 is that the :mod:`email` package, :mod:" +"`mailbox` module, and :mod:`nntplib` modules now work correctly with the " +"bytes/text model in Python 3. For the first time, there is correct handling " +"of messages with mixed encodings." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:664 +msgid "" +"Throughout the standard library, there has been more careful attention to " +"encodings and text versus bytes issues. In particular, interactions with " +"the operating system are now better able to exchange non-ASCII data using " +"the Windows MBCS encoding, locale-aware encodings, or UTF-8." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:669 +msgid "" +"Another significant win is the addition of substantially better support for " +"*SSL* connections and security certificates." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:672 +msgid "" +"In addition, more classes now implement a :term:`context manager` to support " +"convenient and reliable resource clean-up using a :keyword:`with` statement." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:676 ../Doc/whatsnew/3.3.rst:1192 +#: ../Doc/whatsnew/3.4.rst:793 ../Doc/whatsnew/3.5.rst:1096 +#: ../Doc/whatsnew/3.6.rst:678 +msgid "email" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:678 +msgid "" +"The usability of the :mod:`email` package in Python 3 has been mostly fixed " +"by the extensive efforts of R. David Murray. The problem was that emails " +"are typically read and stored in the form of :class:`bytes` rather than :" +"class:`str` text, and they may contain multiple encodings within a single " +"email. So, the email package had to be extended to parse and generate email " +"messages in bytes format." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:685 +msgid "" +"New functions :func:`~email.message_from_bytes` and :func:`~email." +"message_from_binary_file`, and new classes :class:`~email.parser." +"BytesFeedParser` and :class:`~email.parser.BytesParser` allow binary message " +"data to be parsed into model objects." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:690 +msgid "" +"Given bytes input to the model, :meth:`~email.message.Message.get_payload` " +"will by default decode a message body that has a :mailheader:`Content-" +"Transfer-Encoding` of *8bit* using the charset specified in the MIME headers " +"and return the resulting string." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:695 +msgid "" +"Given bytes input to the model, :class:`~email.generator.Generator` will " +"convert message bodies that have a :mailheader:`Content-Transfer-Encoding` " +"of *8bit* to instead have a *7bit* :mailheader:`Content-Transfer-Encoding`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:699 +msgid "" +"Headers with unencoded non-ASCII bytes are deemed to be :rfc:`2047`\\ -" +"encoded using the *unknown-8bit* character set." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:702 +msgid "" +"A new class :class:`~email.generator.BytesGenerator` produces bytes as " +"output, preserving any unchanged non-ASCII data that was present in the " +"input used to build the model, including message bodies with a :mailheader:" +"`Content-Transfer-Encoding` of *8bit*." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:707 +msgid "" +"The :mod:`smtplib` :class:`~smtplib.SMTP` class now accepts a byte string " +"for the *msg* argument to the :meth:`~smtplib.SMTP.sendmail` method, and a " +"new method, :meth:`~smtplib.SMTP.send_message` accepts a :class:`~email." +"message.Message` object and can optionally obtain the *from_addr* and " +"*to_addrs* addresses directly from the object." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:713 +msgid "" +"(Proposed and implemented by R. David Murray, :issue:`4661` and :issue:" +"`10321`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:716 +msgid "elementtree" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:718 +msgid "" +"The :mod:`xml.etree.ElementTree` package and its :mod:`xml.etree." +"cElementTree` counterpart have been updated to version 1.3." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:721 +msgid "Several new and useful functions and methods have been added:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:723 +msgid "" +":func:`xml.etree.ElementTree.fromstringlist` which builds an XML document " +"from a sequence of fragments" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:725 +msgid "" +":func:`xml.etree.ElementTree.register_namespace` for registering a global " +"namespace prefix" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:727 +msgid "" +":func:`xml.etree.ElementTree.tostringlist` for string representation " +"including all sublists" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:729 +msgid "" +":meth:`xml.etree.ElementTree.Element.extend` for appending a sequence of " +"zero or more elements" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:731 +msgid "" +":meth:`xml.etree.ElementTree.Element.iterfind` searches an element and " +"subelements" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:733 +msgid "" +":meth:`xml.etree.ElementTree.Element.itertext` creates a text iterator over " +"an element and its subelements" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:735 +msgid "" +":meth:`xml.etree.ElementTree.TreeBuilder.end` closes the current element" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:736 +msgid "" +":meth:`xml.etree.ElementTree.TreeBuilder.doctype` handles a doctype " +"declaration" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:739 +msgid "Two methods have been deprecated:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:741 +msgid ":meth:`xml.etree.ElementTree.getchildren` use ``list(elem)`` instead." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:742 +msgid ":meth:`xml.etree.ElementTree.getiterator` use ``Element.iter`` instead." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:744 +msgid "" +"For details of the update, see `Introducing ElementTree `_ on Fredrik Lundh's website." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:747 +msgid "(Contributed by Florent Xicluna and Fredrik Lundh, :issue:`6472`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:750 ../Doc/whatsnew/3.3.rst:1388 +#: ../Doc/whatsnew/3.4.rst:851 ../Doc/whatsnew/3.5.rst:1148 +msgid "functools" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:752 +msgid "" +"The :mod:`functools` module includes a new decorator for caching function " +"calls. :func:`functools.lru_cache` can save repeated queries to an external " +"resource whenever the results are expected to be the same." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:756 +msgid "" +"For example, adding a caching decorator to a database query function can " +"save database accesses for popular searches:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:769 +msgid "" +"To help with choosing an effective cache size, the wrapped function is " +"instrumented for tracking cache statistics:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:775 +msgid "" +"If the phonelist table gets updated, the outdated contents of the cache can " +"be cleared with:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:780 +msgid "" +"(Contributed by Raymond Hettinger and incorporating design ideas from Jim " +"Baker, Miki Tebeka, and Nick Coghlan; see `recipe 498245 `_\\, `recipe 577479 `_\\, :issue:`10586`, and :issue:`10593`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:786 +msgid "" +"The :func:`functools.wraps` decorator now adds a :attr:`__wrapped__` " +"attribute pointing to the original callable function. This allows wrapped " +"functions to be introspected. It also copies :attr:`__annotations__` if " +"defined. And now it also gracefully skips over missing attributes such as :" +"attr:`__doc__` which might not be defined for the wrapped callable." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:792 +msgid "" +"In the above example, the cache can be removed by recovering the original " +"function:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:797 +msgid "" +"(By Nick Coghlan and Terrence Cole; :issue:`9567`, :issue:`3445`, and :issue:" +"`8814`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:800 +msgid "" +"To help write classes with rich comparison methods, a new decorator :func:" +"`functools.total_ordering` will use existing equality and inequality methods " +"to fill in the remaining methods." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:804 +msgid "" +"For example, supplying *__eq__* and *__lt__* will enable :func:`~functools." +"total_ordering` to fill-in *__le__*, *__gt__* and *__ge__*::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:817 +msgid "" +"With the *total_ordering* decorator, the remaining comparison methods are " +"filled in automatically." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:822 +msgid "" +"To aid in porting programs from Python 2, the :func:`functools.cmp_to_key` " +"function converts an old-style comparison function to modern :term:`key " +"function`:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:829 +msgid "" +"For sorting examples and a brief sorting tutorial, see the `Sorting HowTo " +"`_ tutorial." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:835 ../Doc/whatsnew/3.3.rst:1492 +msgid "itertools" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:837 +msgid "" +"The :mod:`itertools` module has a new :func:`~itertools.accumulate` function " +"modeled on APL's *scan* operator and Numpy's *accumulate* function:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:848 +msgid "" +"For an example using :func:`~itertools.accumulate`, see the :ref:`examples " +"for the random module `." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:851 +msgid "" +"(Contributed by Raymond Hettinger and incorporating design suggestions from " +"Mark Dickinson.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:855 ../Doc/whatsnew/3.3.rst:1018 +#: ../Doc/whatsnew/3.4.rst:662 ../Doc/whatsnew/3.5.rst:901 +msgid "collections" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:857 +msgid "" +"The :class:`collections.Counter` class now has two forms of in-place " +"subtraction, the existing *-=* operator for `saturating subtraction `_ and the new :meth:" +"`~collections.Counter.subtract` method for regular subtraction. The former " +"is suitable for `multisets `_ which " +"only have positive counts, and the latter is more suitable for use cases " +"that allow negative counts:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:878 +msgid "" +"The :class:`collections.OrderedDict` class has a new method :meth:" +"`~collections.OrderedDict.move_to_end` which takes an existing key and moves " +"it to either the first or last position in the ordered sequence." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:882 +msgid "" +"The default is to move an item to the last position. This is equivalent of " +"renewing an entry with ``od[k] = od.pop(k)``." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:885 +msgid "" +"A fast move-to-end operation is useful for resequencing entries. For " +"example, an ordered dictionary can be used to track order of access by aging " +"entries from the oldest to the most recently accessed." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:899 +msgid "" +"The :class:`collections.deque` class grew two new methods :meth:" +"`~collections.deque.count` and :meth:`~collections.deque.reverse` that make " +"them more substitutable for :class:`list` objects:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:914 ../Doc/whatsnew/3.3.rst:2034 +#: ../Doc/whatsnew/3.4.rst:1595 ../Doc/whatsnew/3.5.rst:1908 +msgid "threading" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:916 +msgid "" +"The :mod:`threading` module has a new :class:`~threading.Barrier` " +"synchronization class for making multiple threads wait until all of them " +"have reached a common barrier point. Barriers are useful for making sure " +"that a task with multiple preconditions does not run until all of the " +"predecessor tasks are complete." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:922 +msgid "" +"Barriers can work with an arbitrary number of threads. This is a " +"generalization of a `Rendezvous `_ which is defined for only two threads." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:926 +msgid "" +"Implemented as a two-phase cyclic barrier, :class:`~threading.Barrier` " +"objects are suitable for use in loops. The separate *filling* and " +"*draining* phases assure that all threads get released (drained) before any " +"one of them can loop back and re-enter the barrier. The barrier fully " +"resets after each cycle." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:931 +msgid "Example of using barriers::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:945 +msgid "" +"In this example, the barrier enforces a rule that votes cannot be counted at " +"any polling site until all polls are closed. Notice how a solution with a " +"barrier is similar to one with :meth:`threading.Thread.join`, but the " +"threads stay alive and continue to do work (summarizing ballots) after the " +"barrier point is crossed." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:951 +msgid "" +"If any of the predecessor tasks can hang or be delayed, a barrier can be " +"created with an optional *timeout* parameter. Then if the timeout period " +"elapses before all the predecessor tasks reach the barrier point, all " +"waiting threads are released and a :exc:`~threading.BrokenBarrierError` " +"exception is raised::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:967 +msgid "" +"In this example, the barrier enforces a more robust rule. If some election " +"sites do not finish before midnight, the barrier times-out and the ballots " +"are sealed and deposited in a queue for later handling." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:971 +msgid "" +"See `Barrier Synchronization Patterns `_ for more examples of how barriers can " +"be used in parallel computing. Also, there is a simple but thorough " +"explanation of barriers in `The Little Book of Semaphores `_, *section 3.6*." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:977 +msgid "" +"(Contributed by Kristján Valur Jónsson with an API review by Jeffrey Yasskin " +"in :issue:`8777`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:981 +msgid "datetime and time" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:983 +msgid "" +"The :mod:`datetime` module has a new type :class:`~datetime.timezone` that " +"implements the :class:`~datetime.tzinfo` interface by returning a fixed UTC " +"offset and timezone name. This makes it easier to create timezone-aware " +"datetime objects::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:996 +msgid "" +"Also, :class:`~datetime.timedelta` objects can now be multiplied by :class:" +"`float` and divided by :class:`float` and :class:`int` objects. And :class:" +"`~datetime.timedelta` objects can now divide one another." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1000 +msgid "" +"The :meth:`datetime.date.strftime` method is no longer restricted to years " +"after 1900. The new supported year range is from 1000 to 9999 inclusive." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1003 +msgid "" +"Whenever a two-digit year is used in a time tuple, the interpretation has " +"been governed by :attr:`time.accept2dyear`. The default is *True* which " +"means that for a two-digit year, the century is guessed according to the " +"POSIX rules governing the ``%y`` strptime format." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1008 +msgid "" +"Starting with Py3.2, use of the century guessing heuristic will emit a :exc:" +"`DeprecationWarning`. Instead, it is recommended that :attr:`time." +"accept2dyear` be set to *False* so that large date ranges can be used " +"without guesswork::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1027 +msgid "" +"Several functions now have significantly expanded date ranges. When :attr:" +"`time.accept2dyear` is false, the :func:`time.asctime` function will accept " +"any year that fits in a C int, while the :func:`time.mktime` and :func:`time." +"strftime` functions will accept the full range supported by the " +"corresponding operating system functions." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1033 +msgid "" +"(Contributed by Alexander Belopolsky and Victor Stinner in :issue:" +"`1289118`, :issue:`5094`, :issue:`6641`, :issue:`2706`, :issue:`1777412`, :" +"issue:`8013`, and :issue:`10827`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1040 ../Doc/whatsnew/3.3.rst:1512 +#: ../Doc/whatsnew/3.5.rst:1446 +msgid "math" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1042 +msgid "" +"The :mod:`math` module has been updated with six new functions inspired by " +"the C99 standard." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1045 +msgid "" +"The :func:`~math.isfinite` function provides a reliable and fast way to " +"detect special values. It returns *True* for regular numbers and *False* " +"for *Nan* or *Infinity*:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1053 +msgid "" +"The :func:`~math.expm1` function computes ``e**x-1`` for small values of *x* " +"without incurring the loss of precision that usually accompanies the " +"subtraction of nearly equal quantities:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1061 +msgid "" +"The :func:`~math.erf` function computes a probability integral or `Gaussian " +"error function `_. The " +"complementary error function, :func:`~math.erfc`, is ``1 - erf(x)``:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1073 +msgid "" +"The :func:`~math.gamma` function is a continuous extension of the factorial " +"function. See https://en.wikipedia.org/wiki/Gamma_function for details. " +"Because the function is related to factorials, it grows large even for small " +"values of *x*, so there is also a :func:`~math.lgamma` function for " +"computing the natural logarithm of the gamma function:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1085 +msgid "(Contributed by Mark Dickinson.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1088 ../Doc/whatsnew/3.3.rst:912 +#: ../Doc/whatsnew/3.4.rst:593 +msgid "abc" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1090 +msgid "" +"The :mod:`abc` module now supports :func:`~abc.abstractclassmethod` and :" +"func:`~abc.abstractstaticmethod`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1093 +msgid "" +"These tools make it possible to define an :term:`abstract base class` that " +"requires a particular :func:`classmethod` or :func:`staticmethod` to be " +"implemented::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1105 +msgid "(Patch submitted by Daniel Urban; :issue:`5867`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1108 ../Doc/whatsnew/3.3.rst:1476 +#: ../Doc/whatsnew/3.5.rst:1326 +msgid "io" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1110 +msgid "" +"The :class:`io.BytesIO` has a new method, :meth:`~io.BytesIO.getbuffer`, " +"which provides functionality similar to :func:`memoryview`. It creates an " +"editable view of the data without making a copy. The buffer's random access " +"and support for slice notation are well-suited to in-place editing::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1136 +msgid "(Contributed by Antoine Pitrou in :issue:`5506`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1141 +msgid "" +"When writing a :meth:`__repr__` method for a custom container, it is easy to " +"forget to handle the case where a member refers back to the container " +"itself. Python's builtin objects such as :class:`list` and :class:`set` " +"handle self-reference by displaying \"...\" in the recursive part of the " +"representation string." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1147 +msgid "" +"To help write such :meth:`__repr__` methods, the :mod:`reprlib` module has a " +"new decorator, :func:`~reprlib.recursive_repr`, for detecting recursive " +"calls to :meth:`__repr__` and substituting a placeholder string instead::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1162 +msgid "(Contributed by Raymond Hettinger in :issue:`9826` and :issue:`9840`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1165 ../Doc/whatsnew/3.3.rst:1499 +#: ../Doc/whatsnew/3.4.rst:1073 ../Doc/whatsnew/3.5.rst:1408 +msgid "logging" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1167 +msgid "" +"In addition to dictionary-based configuration described above, the :mod:" +"`logging` package has many other improvements." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1170 +msgid "" +"The logging documentation has been augmented by a :ref:`basic tutorial " +"`\\, an :ref:`advanced tutorial `\\, and a :ref:`cookbook ` of logging recipes. " +"These documents are the fastest way to learn about logging." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1175 +msgid "" +"The :func:`logging.basicConfig` set-up function gained a *style* argument to " +"support three different types of string formatting. It defaults to \"%\" " +"for traditional %-formatting, can be set to \"{\" for the new :meth:`str." +"format` style, or can be set to \"$\" for the shell-style formatting " +"provided by :class:`string.Template`. The following three configurations " +"are equivalent::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1186 +msgid "" +"If no configuration is set-up before a logging event occurs, there is now a " +"default configuration using a :class:`~logging.StreamHandler` directed to :" +"attr:`sys.stderr` for events of ``WARNING`` level or higher. Formerly, an " +"event occurring before a configuration was set-up would either raise an " +"exception or silently drop the event depending on the value of :attr:" +"`logging.raiseExceptions`. The new default handler is stored in :attr:" +"`logging.lastResort`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1194 +msgid "" +"The use of filters has been simplified. Instead of creating a :class:" +"`~logging.Filter` object, the predicate can be any Python callable that " +"returns *True* or *False*." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1198 +msgid "" +"There were a number of other improvements that add flexibility and simplify " +"configuration. See the module documentation for a full listing of changes " +"in Python 3.2." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1203 ../Doc/whatsnew/3.5.rst:1039 +msgid "csv" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1205 +msgid "" +"The :mod:`csv` module now supports a new dialect, :class:`~csv." +"unix_dialect`, which applies quoting for all fields and a traditional Unix " +"style with ``'\\n'`` as the line terminator. The registered dialect name is " +"``unix``." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1209 +msgid "" +"The :class:`csv.DictWriter` has a new method, :meth:`~csv.DictWriter." +"writeheader` for writing-out an initial row to document the field names::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1223 +msgid "" +"(New dialect suggested by Jay Talbot in :issue:`5975`, and the new method " +"suggested by Ed Abraham in :issue:`1537721`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1227 ../Doc/whatsnew/3.3.rst:1037 +#: ../Doc/whatsnew/3.4.rst:680 ../Doc/whatsnew/3.5.rst:1020 +#: ../Doc/whatsnew/3.6.rst:639 +msgid "contextlib" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1229 +msgid "" +"There is a new and slightly mind-blowing tool :class:`~contextlib." +"ContextDecorator` that is helpful for creating a :term:`context manager` " +"that does double duty as a function decorator." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1233 +msgid "" +"As a convenience, this new functionality is used by :func:`~contextlib." +"contextmanager` so that no extra effort is needed to support both roles." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1237 +msgid "" +"The basic idea is that both context managers and function decorators can be " +"used for pre-action and post-action wrappers. Context managers wrap a group " +"of statements using a :keyword:`with` statement, and function decorators " +"wrap a group of statements enclosed in a function. So, occasionally there " +"is a need to write a pre-action or post-action wrapper that can be used in " +"either role." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1243 +msgid "" +"For example, it is sometimes useful to wrap functions or groups of " +"statements with a logger that can track the time of entry and time of exit. " +"Rather than writing both a function decorator and a context manager for the " +"task, the :func:`~contextlib.contextmanager` provides both capabilities in a " +"single definition::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1260 +msgid "Formerly, this would have only been usable as a context manager::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1266 +msgid "Now, it can be used as a decorator as well::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1273 +msgid "" +"Trying to fulfill two roles at once places some limitations on the " +"technique. Context managers normally have the flexibility to return an " +"argument usable by a :keyword:`with` statement, but there is no parallel for " +"function decorators." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1277 +msgid "" +"In the above example, there is not a clean way for the " +"*track_entry_and_exit* context manager to return a logging instance for use " +"in the body of enclosed statements." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1281 +msgid "(Contributed by Michael Foord in :issue:`9110`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1284 +msgid "decimal and fractions" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1286 +msgid "" +"Mark Dickinson crafted an elegant and efficient scheme for assuring that " +"different numeric datatypes will have the same hash value whenever their " +"actual values are equal (:issue:`8188`)::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1293 +msgid "" +"Some of the hashing details are exposed through a new attribute, :attr:`sys." +"hash_info`, which describes the bit width of the hash value, the prime " +"modulus, the hash values for *infinity* and *nan*, and the multiplier used " +"for the imaginary part of a number:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1301 +msgid "" +"An early decision to limit the inter-operability of various numeric types " +"has been relaxed. It is still unsupported (and ill-advised) to have " +"implicit mixing in arithmetic expressions such as ``Decimal('1.1') + " +"float('1.1')`` because the latter loses information in the process of " +"constructing the binary float. However, since existing floating point value " +"can be converted losslessly to either a decimal or rational representation, " +"it makes sense to add them to the constructor and to support mixed-type " +"comparisons." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1309 +msgid "" +"The :class:`decimal.Decimal` constructor now accepts :class:`float` objects " +"directly so there in no longer a need to use the :meth:`~decimal.Decimal." +"from_float` method (:issue:`8257`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1313 +msgid "" +"Mixed type comparisons are now fully supported so that :class:`~decimal." +"Decimal` objects can be directly compared with :class:`float` and :class:" +"`fractions.Fraction` (:issue:`2531` and :issue:`8188`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1317 +msgid "" +"Similar changes were made to :class:`fractions.Fraction` so that the :meth:" +"`~fractions.Fraction.from_float()` and :meth:`~fractions.Fraction." +"from_decimal` methods are no longer needed (:issue:`8294`):" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1328 +msgid "" +"Another useful change for the :mod:`decimal` module is that the :attr:" +"`Context.clamp` attribute is now public. This is useful in creating " +"contexts that correspond to the decimal interchange formats specified in " +"IEEE 754 (see :issue:`8540`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1333 +msgid "(Contributed by Mark Dickinson and Raymond Hettinger.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1336 +msgid "ftp" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1338 +msgid "" +"The :class:`ftplib.FTP` class now supports the context management protocol " +"to unconditionally consume :exc:`socket.error` exceptions and to close the " +"FTP connection when done::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1353 +msgid "" +"Other file-like objects such as :class:`mmap.mmap` and :func:`fileinput." +"input` also grew auto-closing context managers::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1360 +msgid "" +"(Contributed by Tarek Ziadé and Giampaolo Rodolà in :issue:`4972`, and by " +"Georg Brandl in :issue:`8046` and :issue:`1286`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1363 +msgid "" +"The :class:`~ftplib.FTP_TLS` class now accepts a *context* parameter, which " +"is a :class:`ssl.SSLContext` object allowing bundling SSL configuration " +"options, certificates and private keys into a single (potentially long-" +"lived) structure." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1367 +msgid "(Contributed by Giampaolo Rodolà; :issue:`8806`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1370 +msgid "popen" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1372 +msgid "" +"The :func:`os.popen` and :func:`subprocess.Popen` functions now support :" +"keyword:`with` statements for auto-closing of the file descriptors." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1375 +msgid "" +"(Contributed by Antoine Pitrou and Brian Curtin in :issue:`7461` and :issue:" +"`10554`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1379 ../Doc/whatsnew/3.3.rst:1769 +#: ../Doc/whatsnew/3.4.rst:1338 +msgid "select" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1381 +msgid "" +"The :mod:`select` module now exposes a new, constant attribute, :attr:" +"`~select.PIPE_BUF`, which gives the minimum number of bytes which are " +"guaranteed not to block when :func:`select.select` says a pipe is ready for " +"writing." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1390 +msgid "(Available on Unix systems. Patch by Sébastien Sablé in :issue:`9862`)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1393 +msgid "gzip and zipfile" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1395 +msgid "" +":class:`gzip.GzipFile` now implements the :class:`io.BufferedIOBase` :term:" +"`abstract base class` (except for ``truncate()``). It also has a :meth:" +"`~gzip.GzipFile.peek` method and supports unseekable as well as zero-padded " +"file objects." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1400 +msgid "" +"The :mod:`gzip` module also gains the :func:`~gzip.compress` and :func:" +"`~gzip.decompress` functions for easier in-memory compression and " +"decompression. Keep in mind that text needs to be encoded as :class:`bytes` " +"before compressing and decompressing:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1417 +msgid "" +"(Contributed by Anand B. Pillai in :issue:`3488`; and by Antoine Pitrou, Nir " +"Aides and Brian Curtin in :issue:`9962`, :issue:`1675951`, :issue:`7471` " +"and :issue:`2846`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1421 +msgid "" +"Also, the :class:`zipfile.ZipExtFile` class was reworked internally to " +"represent files stored inside an archive. The new implementation is " +"significantly faster and can be wrapped in an :class:`io.BufferedReader` " +"object for more speedups. It also solves an issue where interleaved calls " +"to *read* and *readline* gave the wrong results." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1427 +msgid "(Patch submitted by Nir Aides in :issue:`7610`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1430 ../Doc/whatsnew/3.3.rst:2011 +#: ../Doc/whatsnew/3.4.rst:1573 ../Doc/whatsnew/3.5.rst:1888 +msgid "tarfile" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1432 +msgid "" +"The :class:`~tarfile.TarFile` class can now be used as a context manager. " +"In addition, its :meth:`~tarfile.TarFile.add` method has a new option, " +"*filter*, that controls which files are added to the archive and allows the " +"file metadata to be edited." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1437 +msgid "" +"The new *filter* option replaces the older, less flexible *exclude* " +"parameter which is now deprecated. If specified, the optional *filter* " +"parameter needs to be a :term:`keyword argument`. The user-supplied filter " +"function accepts a :class:`~tarfile.TarInfo` object and returns an updated :" +"class:`~tarfile.TarInfo` object, or if it wants the file to be excluded, the " +"function can return *None*::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1461 +msgid "" +"(Proposed by Tarek Ziadé and implemented by Lars Gustäbel in :issue:`6856`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1464 ../Doc/whatsnew/3.4.rst:901 +#: ../Doc/whatsnew/3.6.rst:715 +msgid "hashlib" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1466 +msgid "" +"The :mod:`hashlib` module has two new constant attributes listing the " +"hashing algorithms guaranteed to be present in all implementations and those " +"available on the current implementation::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1481 +msgid "(Suggested by Carl Chenet in :issue:`7418`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1484 +msgid "ast" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1486 +msgid "" +"The :mod:`ast` module has a wonderful a general-purpose tool for safely " +"evaluating expression strings using the Python literal syntax. The :func:" +"`ast.literal_eval` function serves as a secure alternative to the builtin :" +"func:`eval` function which is easily abused. Python 3.2 adds :class:`bytes` " +"and :class:`set` literals to the list of supported types: strings, bytes, " +"numbers, tuples, lists, dicts, sets, booleans, and None." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1507 +msgid "(Implemented by Benjamin Peterson and Georg Brandl.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1510 ../Doc/whatsnew/3.3.rst:1575 +#: ../Doc/whatsnew/3.4.rst:1171 ../Doc/whatsnew/3.5.rst:1480 +#: ../Doc/whatsnew/3.6.rst:782 +msgid "os" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1512 +msgid "" +"Different operating systems use various encodings for filenames and " +"environment variables. The :mod:`os` module provides two new functions, :" +"func:`~os.fsencode` and :func:`~os.fsdecode`, for encoding and decoding " +"filenames:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1522 +msgid "" +"Some operating systems allow direct access to encoded bytes in the " +"environment. If so, the :attr:`os.supports_bytes_environ` constant will be " +"true." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1526 +msgid "" +"For direct access to encoded environment variables (if available), use the " +"new :func:`os.getenvb` function or use :data:`os.environb` which is a bytes " +"version of :data:`os.environ`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1530 +msgid "(Contributed by Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1533 ../Doc/whatsnew/3.3.rst:1786 +#: ../Doc/whatsnew/3.4.rst:1360 ../Doc/whatsnew/3.5.rst:1639 +msgid "shutil" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1535 +msgid "The :func:`shutil.copytree` function has two new options:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1537 +msgid "" +"*ignore_dangling_symlinks*: when ``symlinks=False`` so that the function " +"copies a file pointed to by a symlink, not the symlink itself. This option " +"will silence the error raised if the file doesn't exist." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1541 +msgid "" +"*copy_function*: is a callable that will be used to copy files. :func:" +"`shutil.copy2` is used by default." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1544 ../Doc/whatsnew/3.2.rst:1582 +msgid "(Contributed by Tarek Ziadé.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1546 +msgid "" +"In addition, the :mod:`shutil` module now supports :ref:`archiving " +"operations ` for zipfiles, uncompressed tarfiles, " +"gzipped tarfiles, and bzipped tarfiles. And there are functions for " +"registering additional archiving file formats (such as xz compressed " +"tarfiles or custom formats)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1551 +msgid "" +"The principal functions are :func:`~shutil.make_archive` and :func:`~shutil." +"unpack_archive`. By default, both operate on the current directory (which " +"can be set by :func:`os.chdir`) and on any sub-directories. The archive " +"filename needs to be specified with a full pathname. The archiving step is " +"non-destructive (the original files are left unchanged)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1585 ../Doc/whatsnew/3.3.rst:1916 +#: ../Doc/whatsnew/3.4.rst:1409 ../Doc/whatsnew/3.5.rst:1827 +#: ../Doc/whatsnew/3.6.rst:851 +msgid "sqlite3" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1587 +msgid "" +"The :mod:`sqlite3` module was updated to pysqlite version 2.6.0. It has two " +"new capabilities." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1589 +msgid "" +"The :attr:`sqlite3.Connection.in_transit` attribute is true if there is an " +"active transaction for uncommitted changes." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1592 +msgid "" +"The :meth:`sqlite3.Connection.enable_load_extension` and :meth:`sqlite3." +"Connection.load_extension` methods allows you to load SQLite extensions from " +"\".so\" files. One well-known extension is the fulltext-search extension " +"distributed with SQLite." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1597 +msgid "(Contributed by R. David Murray and Shashwat Anand; :issue:`8845`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1600 ../Doc/whatsnew/3.3.rst:1430 +#: ../Doc/whatsnew/3.4.rst:938 +msgid "html" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1602 +msgid "" +"A new :mod:`html` module was introduced with only a single function, :func:" +"`~html.escape`, which is used for escaping reserved characters from HTML " +"markup:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1611 ../Doc/whatsnew/3.3.rst:1875 +#: ../Doc/whatsnew/3.4.rst:1389 ../Doc/whatsnew/3.5.rst:1723 +#: ../Doc/whatsnew/3.6.rst:858 +msgid "socket" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1613 +msgid "The :mod:`socket` module has two new improvements." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1615 +msgid "" +"Socket objects now have a :meth:`~socket.socket.detach()` method which puts " +"the socket into closed state without actually closing the underlying file " +"descriptor. The latter can then be reused for other purposes. (Added by " +"Antoine Pitrou; :issue:`8524`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1620 +msgid "" +":func:`socket.create_connection` now supports the context management " +"protocol to unconditionally consume :exc:`socket.error` exceptions and to " +"close the socket when done. (Contributed by Giampaolo Rodolà; :issue:`9794`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1626 ../Doc/whatsnew/3.3.rst:1925 +#: ../Doc/whatsnew/3.4.rst:1418 ../Doc/whatsnew/3.5.rst:1746 +#: ../Doc/whatsnew/3.6.rst:890 +msgid "ssl" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1628 +msgid "" +"The :mod:`ssl` module added a number of features to satisfy common " +"requirements for secure (encrypted, authenticated) internet connections:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1631 +msgid "" +"A new class, :class:`~ssl.SSLContext`, serves as a container for persistent " +"SSL data, such as protocol settings, certificates, private keys, and various " +"other options. It includes a :meth:`~ssl.SSLContext.wrap_socket` for " +"creating an SSL socket from an SSL context." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1636 +msgid "" +"A new function, :func:`ssl.match_hostname`, supports server identity " +"verification for higher-level protocols by implementing the rules of HTTPS " +"(from :rfc:`2818`) which are also suitable for other protocols." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1640 +msgid "" +"The :func:`ssl.wrap_socket` constructor function now takes a *ciphers* " +"argument. The *ciphers* string lists the allowed encryption algorithms " +"using the format described in the `OpenSSL documentation `__." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1645 +msgid "" +"When linked against recent versions of OpenSSL, the :mod:`ssl` module now " +"supports the Server Name Indication extension to the TLS protocol, allowing " +"multiple \"virtual hosts\" using different certificates on a single IP port. " +"This extension is only supported in client mode, and is activated by passing " +"the *server_hostname* argument to :meth:`ssl.SSLContext.wrap_socket`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1651 +msgid "" +"Various options have been added to the :mod:`ssl` module, such as :data:" +"`~ssl.OP_NO_SSLv2` which disables the insecure and obsolete SSLv2 protocol." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1655 +msgid "" +"The extension now loads all the OpenSSL ciphers and digest algorithms. If " +"some SSL certificates cannot be verified, they are reported as an \"unknown " +"algorithm\" error." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1659 +msgid "" +"The version of OpenSSL being used is now accessible using the module " +"attributes :data:`ssl.OPENSSL_VERSION` (a string), :data:`ssl." +"OPENSSL_VERSION_INFO` (a 5-tuple), and :data:`ssl.OPENSSL_VERSION_NUMBER` " +"(an integer)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1664 +msgid "" +"(Contributed by Antoine Pitrou in :issue:`8850`, :issue:`1589`, :issue:" +"`8322`, :issue:`5639`, :issue:`4870`, :issue:`8484`, and :issue:`8321`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1668 +msgid "nntp" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1670 +msgid "" +"The :mod:`nntplib` module has a revamped implementation with better bytes " +"and text semantics as well as more practical APIs. These improvements break " +"compatibility with the nntplib version in Python 3.1, which was partly " +"dysfunctional in itself." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1675 +msgid "" +"Support for secure connections through both implicit (using :class:`nntplib." +"NNTP_SSL`) and explicit (using :meth:`nntplib.NNTP.starttls`) TLS has also " +"been added." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1679 +msgid "" +"(Contributed by Antoine Pitrou in :issue:`9360` and Andrew Vant in :issue:" +"`1926`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1682 +msgid "certificates" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1684 +msgid "" +":class:`http.client.HTTPSConnection`, :class:`urllib.request.HTTPSHandler` " +"and :func:`urllib.request.urlopen` now take optional arguments to allow for " +"server certificate checking against a set of Certificate Authorities, as " +"recommended in public uses of HTTPS." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1689 +msgid "(Added by Antoine Pitrou, :issue:`9003`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1692 ../Doc/whatsnew/3.3.rst:1450 +#: ../Doc/whatsnew/3.5.rst:1233 +msgid "imaplib" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1694 +msgid "" +"Support for explicit TLS on standard IMAP4 connections has been added " +"through the new :mod:`imaplib.IMAP4.starttls` method." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1697 +msgid "(Contributed by Lorenzo M. Catucci and Antoine Pitrou, :issue:`4471`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1700 ../Doc/whatsnew/3.5.rst:1201 +#: ../Doc/whatsnew/3.6.rst:740 +msgid "http.client" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1702 +msgid "" +"There were a number of small API improvements in the :mod:`http.client` " +"module. The old-style HTTP 0.9 simple responses are no longer supported and " +"the *strict* parameter is deprecated in all classes." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1706 +msgid "" +"The :class:`~http.client.HTTPConnection` and :class:`~http.client." +"HTTPSConnection` classes now have a *source_address* parameter for a (host, " +"port) tuple indicating where the HTTP connection is made from." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1711 +msgid "" +"Support for certificate checking and HTTPS virtual hosts were added to :" +"class:`~http.client.HTTPSConnection`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1714 +msgid "" +"The :meth:`~http.client.HTTPConnection.request` method on connection objects " +"allowed an optional *body* argument so that a :term:`file object` could be " +"used to supply the content of the request. Conveniently, the *body* " +"argument now also accepts an :term:`iterable` object so long as it includes " +"an explicit ``Content-Length`` header. This extended interface is much more " +"flexible than before." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1721 +msgid "" +"To establish an HTTPS connection through a proxy server, there is a new :" +"meth:`~http.client.HTTPConnection.set_tunnel` method that sets the host and " +"port for HTTP Connect tunneling." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1725 +msgid "" +"To match the behavior of :mod:`http.server`, the HTTP client library now " +"also encodes headers with ISO-8859-1 (Latin-1) encoding. It was already " +"doing that for incoming headers, so now the behavior is consistent for both " +"incoming and outgoing traffic. (See work by Armin Ronacher in :issue:" +"`10980`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1731 ../Doc/whatsnew/3.3.rst:2089 +#: ../Doc/whatsnew/3.4.rst:1655 ../Doc/whatsnew/3.5.rst:1984 +msgid "unittest" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1733 +msgid "" +"The unittest module has a number of improvements supporting test discovery " +"for packages, easier experimentation at the interactive prompt, new testcase " +"methods, improved diagnostic messages for test failures, and better method " +"names." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1738 +msgid "" +"The command-line call ``python -m unittest`` can now accept file paths " +"instead of module names for running specific tests (:issue:`10620`). The " +"new test discovery can find tests within packages, locating any test " +"importable from the top-level directory. The top-level directory can be " +"specified with the `-t` option, a pattern for matching files with ``-p``, " +"and a directory to start discovery with ``-s``:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1749 ../Doc/whatsnew/3.2.rst:1758 +#: ../Doc/whatsnew/3.2.rst:1914 +msgid "(Contributed by Michael Foord.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1751 +msgid "" +"Experimentation at the interactive prompt is now easier because the :class:" +"`unittest.case.TestCase` class can now be instantiated without arguments:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1760 +msgid "" +"The :mod:`unittest` module has two new methods, :meth:`~unittest.TestCase." +"assertWarns` and :meth:`~unittest.TestCase.assertWarnsRegex` to verify that " +"a given warning type is triggered by the code under test::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1768 +msgid "(Contributed by Antoine Pitrou, :issue:`9754`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1770 +msgid "" +"Another new method, :meth:`~unittest.TestCase.assertCountEqual` is used to " +"compare two iterables to determine if their element counts are equal " +"(whether the same elements are present with the same number of occurrences " +"regardless of order)::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1780 +msgid "" +"A principal feature of the unittest module is an effort to produce " +"meaningful diagnostics when a test fails. When possible, the failure is " +"recorded along with a diff of the output. This is especially helpful for " +"analyzing log files of failed test runs. However, since diffs can sometime " +"be voluminous, there is a new :attr:`~unittest.TestCase.maxDiff` attribute " +"that sets maximum length of diffs displayed." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1787 +msgid "" +"In addition, the method names in the module have undergone a number of clean-" +"ups." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1789 +msgid "" +"For example, :meth:`~unittest.TestCase.assertRegex` is the new name for :" +"meth:`~unittest.TestCase.assertRegexpMatches` which was misnamed because the " +"test uses :func:`re.search`, not :func:`re.match`. Other methods using " +"regular expressions are now named using short form \"Regex\" in preference " +"to \"Regexp\" -- this matches the names used in other unittest " +"implementations, matches Python's old name for the :mod:`re` module, and it " +"has unambiguous camel-casing." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1797 +msgid "(Contributed by Raymond Hettinger and implemented by Ezio Melotti.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1799 +msgid "" +"To improve consistency, some long-standing method aliases are being " +"deprecated in favor of the preferred names:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1803 +msgid "Preferred Name" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1805 +msgid ":meth:`assert_`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1805 +msgid ":meth:`.assertTrue`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1806 +msgid ":meth:`assertEquals`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1806 +msgid ":meth:`.assertEqual`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1807 +msgid ":meth:`assertNotEquals`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1807 +msgid ":meth:`.assertNotEqual`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1808 +msgid ":meth:`assertAlmostEquals`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1808 +msgid ":meth:`.assertAlmostEqual`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1809 +msgid ":meth:`assertNotAlmostEquals`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1809 +msgid ":meth:`.assertNotAlmostEqual`" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1812 +msgid "" +"Likewise, the ``TestCase.fail*`` methods deprecated in Python 3.1 are " +"expected to be removed in Python 3.3. Also see the :ref:`deprecated-" +"aliases` section in the :mod:`unittest` documentation." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1816 +msgid "(Contributed by Ezio Melotti; :issue:`9424`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1818 +msgid "" +"The :meth:`~unittest.TestCase.assertDictContainsSubset` method was " +"deprecated because it was misimplemented with the arguments in the wrong " +"order. This created hard-to-debug optical illusions where tests like " +"``TestCase().assertDictContainsSubset({'a':1, 'b':2}, {'a':1})`` would fail." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1826 +msgid "random" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1828 +msgid "" +"The integer methods in the :mod:`random` module now do a better job of " +"producing uniform distributions. Previously, they computed selections with " +"``int(n*random())`` which had a slight bias whenever *n* was not a power of " +"two. Now, multiple selections are made from a range up to the next power of " +"two and a selection is kept only when it falls within the range ``0 <= x < " +"n``. The functions and methods affected are :func:`~random.randrange`, :" +"func:`~random.randint`, :func:`~random.choice`, :func:`~random.shuffle` and :" +"func:`~random.sample`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1837 +msgid "(Contributed by Raymond Hettinger; :issue:`9025`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1840 ../Doc/whatsnew/3.4.rst:1247 +#: ../Doc/whatsnew/3.5.rst:1576 +msgid "poplib" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1842 +msgid "" +":class:`~poplib.POP3_SSL` class now accepts a *context* parameter, which is " +"a :class:`ssl.SSLContext` object allowing bundling SSL configuration " +"options, certificates and private keys into a single (potentially long-" +"lived) structure." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1847 +msgid "(Contributed by Giampaolo Rodolà; :issue:`8807`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1850 +msgid "asyncore" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1852 +msgid "" +":class:`asyncore.dispatcher` now provides a :meth:`~asyncore.dispatcher." +"handle_accepted()` method returning a `(sock, addr)` pair which is called " +"when a connection has actually been established with a new remote endpoint. " +"This is supposed to be used as a replacement for old :meth:`~asyncore." +"dispatcher.handle_accept()` and avoids the user to call :meth:`~asyncore." +"dispatcher.accept()` directly." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1859 +msgid "(Contributed by Giampaolo Rodolà; :issue:`6706`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1862 ../Doc/whatsnew/3.3.rst:2018 +msgid "tempfile" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1864 +msgid "" +"The :mod:`tempfile` module has a new context manager, :class:`~tempfile." +"TemporaryDirectory` which provides easy deterministic cleanup of temporary " +"directories::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1871 +msgid "(Contributed by Neil Schemenauer and Nick Coghlan; :issue:`5178`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1874 ../Doc/whatsnew/3.3.rst:1459 +#: ../Doc/whatsnew/3.4.rst:1024 ../Doc/whatsnew/3.5.rst:1283 +msgid "inspect" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1876 +msgid "" +"The :mod:`inspect` module has a new function :func:`~inspect." +"getgeneratorstate` to easily identify the current state of a generator-" +"iterator::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1894 +msgid "(Contributed by Rodolpho Eckhardt and Nick Coghlan, :issue:`10220`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1896 +msgid "" +"To support lookups without the possibility of activating a dynamic " +"attribute, the :mod:`inspect` module has a new function, :func:`~inspect." +"getattr_static`. Unlike :func:`hasattr`, this is a true read-only search, " +"guaranteed not to change state while it is searching::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1917 ../Doc/whatsnew/3.3.rst:1726 +#: ../Doc/whatsnew/3.4.rst:1278 +msgid "pydoc" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1919 +msgid "" +"The :mod:`pydoc` module now provides a much-improved Web server interface, " +"as well as a new command-line option ``-b`` to automatically open a browser " +"window to display that server:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1927 +msgid "(Contributed by Ron Adam; :issue:`2001`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1930 ../Doc/whatsnew/3.4.rst:713 +msgid "dis" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1932 +msgid "" +"The :mod:`dis` module gained two new functions for inspecting code, :func:" +"`~dis.code_info` and :func:`~dis.show_code`. Both provide detailed code " +"object information for the supplied function, method, source code string or " +"code object. The former returns a string and the latter prints it::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1959 +msgid "" +"In addition, the :func:`~dis.dis` function now accepts string arguments so " +"that the common idiom ``dis(compile(s, '', 'eval'))`` can be shortened to " +"``dis(s)``::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1981 +msgid "" +"Taken together, these improvements make it easier to explore how CPython is " +"implemented and to see for yourself what the language syntax does under-the-" +"hood." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1985 +msgid "(Contributed by Nick Coghlan in :issue:`9147`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1988 ../Doc/whatsnew/3.4.rst:704 +#: ../Doc/whatsnew/3.5.rst:1054 +msgid "dbm" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1990 +msgid "" +"All database modules now support the :meth:`get` and :meth:`setdefault` " +"methods." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1992 +msgid "(Suggested by Ray Allen in :issue:`9523`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1995 +msgid "ctypes" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:1997 +msgid "" +"A new type, :class:`ctypes.c_ssize_t` represents the C :c:type:`ssize_t` " +"datatype." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2000 ../Doc/whatsnew/3.6.rst:843 +msgid "site" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2002 +msgid "" +"The :mod:`site` module has three new functions useful for reporting on the " +"details of a given Python installation." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2005 +msgid "" +":func:`~site.getsitepackages` lists all global site-packages directories." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2007 +msgid "" +":func:`~site.getuserbase` reports on the user's base directory where data " +"can be stored." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2010 +msgid "" +":func:`~site.getusersitepackages` reveals the user-specific site-packages " +"directory path." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2025 +msgid "" +"Conveniently, some of site's functionality is accessible directly from the " +"command-line:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2035 +msgid "(Contributed by Tarek Ziadé in :issue:`6693`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2038 ../Doc/whatsnew/3.5.rst:1880 +msgid "sysconfig" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2040 +msgid "" +"The new :mod:`sysconfig` module makes it straightforward to discover " +"installation paths and configuration variables that vary across platforms " +"and installations." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2044 +msgid "" +"The module offers access simple access functions for platform and version " +"information:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2047 +msgid "" +":func:`~sysconfig.get_platform` returning values like *linux-i586* or " +"*macosx-10.6-ppc*." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2049 +msgid "" +":func:`~sysconfig.get_python_version` returns a Python version string such " +"as \"3.2\"." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2052 +msgid "" +"It also provides access to the paths and variables corresponding to one of " +"seven named schemes used by :mod:`distutils`. Those include *posix_prefix*, " +"*posix_home*, *posix_user*, *nt*, *nt_user*, *os2*, *os2_home*:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2056 +msgid "" +":func:`~sysconfig.get_paths` makes a dictionary containing installation " +"paths for the current installation scheme." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2058 +msgid "" +":func:`~sysconfig.get_config_vars` returns a dictionary of platform specific " +"variables." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2061 +msgid "There is also a convenient command-line interface:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2100 +msgid "(Moved out of Distutils by Tarek Ziadé.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2103 ../Doc/whatsnew/3.3.rst:1706 +#: ../Doc/whatsnew/3.4.rst:1199 +msgid "pdb" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2105 +msgid "" +"The :mod:`pdb` debugger module gained a number of usability improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2107 +msgid "" +":file:`pdb.py` now has a ``-c`` option that executes commands as given in a :" +"file:`.pdbrc` script file." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2109 +msgid "" +"A :file:`.pdbrc` script file can contain ``continue`` and ``next`` commands " +"that continue debugging." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2111 +msgid "The :class:`Pdb` class constructor now accepts a *nosigint* argument." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2112 +msgid "" +"New commands: ``l(list)``, ``ll(long list)`` and ``source`` for listing " +"source code." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2114 +msgid "" +"New commands: ``display`` and ``undisplay`` for showing or hiding the value " +"of an expression if it has changed." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2116 +msgid "" +"New command: ``interact`` for starting an interactive interpreter containing " +"the global and local names found in the current scope." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2118 +msgid "Breakpoints can be cleared by breakpoint number." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2120 +msgid "(Contributed by Georg Brandl, Antonio Cuni and Ilya Sandler.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2125 +msgid "" +"The :mod:`configparser` module was modified to improve usability and " +"predictability of the default parser and its supported INI syntax. The old :" +"class:`ConfigParser` class was removed in favor of :class:`SafeConfigParser` " +"which has in turn been renamed to :class:`~configparser.ConfigParser`. " +"Support for inline comments is now turned off by default and section or " +"option duplicates are not allowed in a single configuration source." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2132 +msgid "Config parsers gained a new API based on the mapping protocol::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2160 +msgid "" +"The new API is implemented on top of the classical API, so custom parser " +"subclasses should be able to use it without modifications." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2163 +msgid "" +"The INI file structure accepted by config parsers can now be customized. " +"Users can specify alternative option/value delimiters and comment prefixes, " +"change the name of the *DEFAULT* section or switch the interpolation syntax." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2167 +msgid "" +"There is support for pluggable interpolation including an additional " +"interpolation handler :class:`~configparser.ExtendedInterpolation`::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2200 +msgid "" +"A number of smaller features were also introduced, like support for " +"specifying encoding in read operations, specifying fallback values for get-" +"functions, or reading directly from dictionaries and strings." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2204 +msgid "(All changes contributed by Łukasz Langa.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2209 +msgid "urllib.parse" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2211 +msgid "" +"A number of usability improvements were made for the :mod:`urllib.parse` " +"module." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2213 +msgid "" +"The :func:`~urllib.parse.urlparse` function now supports `IPv6 `_ addresses as described in :rfc:`2732`:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2225 +msgid "" +"The :func:`~urllib.parse.urldefrag` function now returns a :term:`named " +"tuple`::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2235 +msgid "" +"And, the :func:`~urllib.parse.urlencode` function is now much more flexible, " +"accepting either a string or bytes type for the *query* argument. If it is " +"a string, then the *safe*, *encoding*, and *error* parameters are sent to :" +"func:`~urllib.parse.quote_plus` for encoding::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2246 +msgid "" +"As detailed in :ref:`parsing-ascii-encoded-bytes`, all the :mod:`urllib." +"parse` functions now accept ASCII-encoded byte strings as input, so long as " +"they are not mixed with regular strings. If ASCII-encoded byte strings are " +"given as parameters, the return types will also be an ASCII-encoded byte " +"strings:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2255 +msgid "" +"(Work by Nick Coghlan, Dan Mahn, and Senthil Kumaran in :issue:`2987`, :" +"issue:`5468`, and :issue:`9873`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2259 +msgid "mailbox" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2261 +msgid "" +"Thanks to a concerted effort by R. David Murray, the :mod:`mailbox` module " +"has been fixed for Python 3.2. The challenge was that mailbox had been " +"originally designed with a text interface, but email messages are best " +"represented with :class:`bytes` because various parts of a message may have " +"different encodings." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2266 +msgid "" +"The solution harnessed the :mod:`email` package's binary support for parsing " +"arbitrary email messages. In addition, the solution required a number of " +"API changes." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2270 +msgid "" +"As expected, the :meth:`~mailbox.Mailbox.add` method for :class:`mailbox." +"Mailbox` objects now accepts binary input." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2273 +msgid "" +":class:`~io.StringIO` and text file input are deprecated. Also, string " +"input will fail early if non-ASCII characters are used. Previously it would " +"fail when the email was processed in a later step." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2277 +msgid "" +"There is also support for binary output. The :meth:`~mailbox.Mailbox." +"get_file` method now returns a file in the binary mode (where it used to " +"incorrectly set the file to text-mode). There is also a new :meth:`~mailbox." +"Mailbox.get_bytes` method that returns a :class:`bytes` representation of a " +"message corresponding to a given *key*." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2283 +msgid "" +"It is still possible to get non-binary output using the old API's :meth:" +"`~mailbox.Mailbox.get_string` method, but that approach is not very useful. " +"Instead, it is best to extract messages from a :class:`~mailbox.Message` " +"object or to load them from binary input." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2288 +msgid "" +"(Contributed by R. David Murray, with efforts from Steffen Daode Nurpmeso " +"and an initial patch by Victor Stinner in :issue:`9124`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2292 +msgid "turtledemo" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2294 +msgid "" +"The demonstration code for the :mod:`turtle` module was moved from the " +"*Demo* directory to main library. It includes over a dozen sample scripts " +"with lively displays. Being on :attr:`sys.path`, it can now be run directly " +"from the command-line:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2303 +msgid "" +"(Moved from the Demo directory by Alexander Belopolsky in :issue:`10199`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2306 +msgid "Multi-threading" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2308 +msgid "" +"The mechanism for serializing execution of concurrently running Python " +"threads (generally known as the :term:`GIL` or :term:`Global Interpreter " +"Lock`) has been rewritten. Among the objectives were more predictable " +"switching intervals and reduced overhead due to lock contention and the " +"number of ensuing system calls. The notion of a \"check interval\" to allow " +"thread switches has been abandoned and replaced by an absolute duration " +"expressed in seconds. This parameter is tunable through :func:`sys." +"setswitchinterval()`. It currently defaults to 5 milliseconds." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2317 +msgid "" +"Additional details about the implementation can be read from a `python-dev " +"mailing-list message `_ (however, \"priority requests\" as exposed in this " +"message have not been kept for inclusion)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2325 +msgid "" +"Regular and recursive locks now accept an optional *timeout* argument to " +"their :meth:`~threading.Lock.acquire` method. (Contributed by Antoine " +"Pitrou; :issue:`7316`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2329 +msgid "" +"Similarly, :meth:`threading.Semaphore.acquire` also gained a *timeout* " +"argument. (Contributed by Torsten Landschoff; :issue:`850728`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2332 +msgid "" +"Regular and recursive lock acquisitions can now be interrupted by signals on " +"platforms using Pthreads. This means that Python programs that deadlock " +"while acquiring locks can be successfully killed by repeatedly sending " +"SIGINT to the process (by pressing :kbd:`Ctrl+C` in most shells). " +"(Contributed by Reid Kleckner; :issue:`8844`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2342 +msgid "A number of small performance enhancements have been added:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2344 +msgid "" +"Python's peephole optimizer now recognizes patterns such ``x in {1, 2, 3}`` " +"as being a test for membership in a set of constants. The optimizer recasts " +"the :class:`set` as a :class:`frozenset` and stores the pre-built constant." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2348 +msgid "" +"Now that the speed penalty is gone, it is practical to start writing " +"membership tests using set-notation. This style is both semantically clear " +"and operationally fast::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2356 +msgid "" +"(Patch and additional tests contributed by Dave Malcolm; :issue:`6690`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2358 +msgid "" +"Serializing and unserializing data using the :mod:`pickle` module is now " +"several times faster." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2361 +msgid "" +"(Contributed by Alexandre Vassalotti, Antoine Pitrou and the Unladen Swallow " +"team in :issue:`9410` and :issue:`3873`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2364 +msgid "" +"The `Timsort algorithm `_ used in :" +"meth:`list.sort` and :func:`sorted` now runs faster and uses less memory " +"when called with a :term:`key function`. Previously, every element of a " +"list was wrapped with a temporary object that remembered the key value " +"associated with each element. Now, two arrays of keys and values are sorted " +"in parallel. This saves the memory consumed by the sort wrappers, and it " +"saves time lost to delegating comparisons." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2372 +msgid "(Patch by Daniel Stutzbach in :issue:`9915`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2374 +msgid "" +"JSON decoding performance is improved and memory consumption is reduced " +"whenever the same string is repeated for multiple keys. Also, JSON encoding " +"now uses the C speedups when the ``sort_keys`` argument is true." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2378 +msgid "" +"(Contributed by Antoine Pitrou in :issue:`7451` and by Raymond Hettinger and " +"Antoine Pitrou in :issue:`10314`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2381 +msgid "" +"Recursive locks (created with the :func:`threading.RLock` API) now benefit " +"from a C implementation which makes them as fast as regular locks, and " +"between 10x and 15x faster than their previous pure Python implementation." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2385 +msgid "(Contributed by Antoine Pitrou; :issue:`3001`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2387 +msgid "" +"The fast-search algorithm in stringlib is now used by the :meth:`split`, :" +"meth:`rsplit`, :meth:`splitlines` and :meth:`replace` methods on :class:" +"`bytes`, :class:`bytearray` and :class:`str` objects. Likewise, the " +"algorithm is also used by :meth:`rfind`, :meth:`rindex`, :meth:`rsplit` and :" +"meth:`rpartition`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2393 +msgid "(Patch by Florent Xicluna in :issue:`7622` and :issue:`7462`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2396 +msgid "" +"Integer to string conversions now work two \"digits\" at a time, reducing " +"the number of division and modulo operations." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2399 +msgid "(:issue:`6713` by Gawain Bolton, Mark Dickinson, and Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2401 +msgid "" +"There were several other minor optimizations. Set differencing now runs " +"faster when one operand is much larger than the other (patch by Andress " +"Bennetts in :issue:`8685`). The :meth:`array.repeat` method has a faster " +"implementation (:issue:`1569291` by Alexander Belopolsky). The :class:" +"`BaseHTTPRequestHandler` has more efficient buffering (:issue:`3709` by " +"Andrew Schaaf). The :func:`operator.attrgetter` function has been sped-up (:" +"issue:`10160` by Christos Georgiou). And :class:`ConfigParser` loads multi-" +"line arguments a bit faster (:issue:`7113` by Łukasz Langa)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2414 +msgid "" +"Python has been updated to `Unicode 6.0.0 `_. The update to the standard adds over 2,000 new characters " +"including `emoji `_ symbols which are " +"important for mobile phones." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2419 +msgid "" +"In addition, the updated standard has altered the character properties for " +"two Kannada characters (U+0CF1, U+0CF2) and one New Tai Lue numeric " +"character (U+19DA), making the former eligible for use in identifiers while " +"disqualifying the latter. For more information, see `Unicode Character " +"Database Changes `_." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2427 +msgid "Codecs" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2429 +msgid "Support was added for *cp720* Arabic DOS encoding (:issue:`1616979`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2431 +msgid "" +"MBCS encoding no longer ignores the error handler argument. In the default " +"strict mode, it raises an :exc:`UnicodeDecodeError` when it encounters an " +"undecodable byte sequence and an :exc:`UnicodeEncodeError` for an " +"unencodable character." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2436 +msgid "" +"The MBCS codec supports ``'strict'`` and ``'ignore'`` error handlers for " +"decoding, and ``'strict'`` and ``'replace'`` for encoding." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2439 +msgid "" +"To emulate Python3.1 MBCS encoding, select the ``'ignore'`` handler for " +"decoding and the ``'replace'`` handler for encoding." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2442 +msgid "" +"On Mac OS X, Python decodes command line arguments with ``'utf-8'`` rather " +"than the locale encoding." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2445 +msgid "" +"By default, :mod:`tarfile` uses ``'utf-8'`` encoding on Windows (instead of " +"``'mbcs'``) and the ``'surrogateescape'`` error handler on all operating " +"systems." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2451 ../../../Misc/NEWS:1227 ../../../Misc/NEWS:1479 +#: ../../../Misc/NEWS:2647 ../../../Misc/NEWS:3239 ../../../Misc/NEWS:3489 +#: ../../../Misc/NEWS:3684 ../../../Misc/NEWS:3994 ../../../Misc/NEWS:6184 +#: ../../../Misc/NEWS:6408 ../../../Misc/NEWS:6782 ../../../Misc/NEWS:7381 +#: ../../../Misc/NEWS:7813 ../../../Misc/NEWS:8087 ../../../Misc/NEWS:8214 +#: ../../../Misc/NEWS:8477 ../../../Misc/NEWS:10528 +msgid "Documentation" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2453 +msgid "The documentation continues to be improved." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2455 +msgid "" +"A table of quick links has been added to the top of lengthy sections such " +"as :ref:`built-in-funcs`. In the case of :mod:`itertools`, the links are " +"accompanied by tables of cheatsheet-style summaries to provide an overview " +"and memory jog without having to read all of the docs." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2460 +msgid "" +"In some cases, the pure Python source code can be a helpful adjunct to the " +"documentation, so now many modules now feature quick links to the latest " +"version of the source code. For example, the :mod:`functools` module " +"documentation has a quick link at the top labeled:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2465 +msgid "**Source code** :source:`Lib/functools.py`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2467 +msgid "" +"(Contributed by Raymond Hettinger; see `rationale `_.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2470 +msgid "" +"The docs now contain more examples and recipes. In particular, :mod:`re` " +"module has an extensive section, :ref:`re-examples`. Likewise, the :mod:" +"`itertools` module continues to be updated with new :ref:`itertools-recipes`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2475 +msgid "" +"The :mod:`datetime` module now has an auxiliary implementation in pure " +"Python. No functionality was changed. This just provides an easier-to-read " +"alternate implementation." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2479 +msgid "(Contributed by Alexander Belopolsky in :issue:`9528`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2481 +msgid "" +"The unmaintained :file:`Demo` directory has been removed. Some demos were " +"integrated into the documentation, some were moved to the :file:`Tools/demo` " +"directory, and others were removed altogether." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2485 +msgid "(Contributed by Georg Brandl in :issue:`7962`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2491 +msgid "" +"The format menu now has an option to clean source files by stripping " +"trailing whitespace." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2494 +msgid "(Contributed by Raymond Hettinger; :issue:`5150`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2496 +msgid "IDLE on Mac OS X now works with both Carbon AquaTk and Cocoa AquaTk." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2498 +msgid "" +"(Contributed by Kevin Walzer, Ned Deily, and Ronald Oussoren; :issue:`6075`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2501 +msgid "Code Repository" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2503 +msgid "" +"In addition to the existing Subversion code repository at http://svn.python." +"org there is now a `Mercurial `_ repository " +"at https://hg.python.org/\\ ." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2507 +msgid "" +"After the 3.2 release, there are plans to switch to Mercurial as the primary " +"repository. This distributed version control system should make it easier " +"for members of the community to create and share external changesets. See :" +"pep:`385` for details." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2512 +msgid "" +"To learn to use the new version control system, see the `tutorial by Joel " +"Spolsky `_ or the `Guide to Mercurial Workflows `_." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2522 +msgid "" +"The *idle*, *pydoc* and *2to3* scripts are now installed with a version-" +"specific suffix on ``make altinstall`` (:issue:`10679`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2525 +msgid "" +"The C functions that access the Unicode Database now accept and return " +"characters from the full Unicode range, even on narrow unicode builds " +"(Py_UNICODE_TOLOWER, Py_UNICODE_ISDECIMAL, and others). A visible " +"difference in Python is that :func:`unicodedata.numeric` now returns the " +"correct value for large code points, and :func:`repr` may consider more " +"characters as printable." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2532 +msgid "" +"(Reported by Bupjoe Lee and fixed by Amaury Forgeot D'Arc; :issue:`5127`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2534 +msgid "" +"Computed gotos are now enabled by default on supported compilers (which are " +"detected by the configure script). They can still be disabled selectively " +"by specifying ``--without-computed-gotos``." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2538 +msgid "(Contributed by Antoine Pitrou; :issue:`9203`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2540 +msgid "" +"The option ``--with-wctype-functions`` was removed. The built-in unicode " +"database is now used for all functions." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2543 +msgid "(Contributed by Amaury Forgeot D'Arc; :issue:`9210`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2545 +msgid "" +"Hash values are now values of a new type, :c:type:`Py_hash_t`, which is " +"defined to be the same size as a pointer. Previously they were of type " +"long, which on some 64-bit operating systems is still only 32 bits long. As " +"a result of this fix, :class:`set` and :class:`dict` can now hold more than " +"``2**32`` entries on builds with 64-bit pointers (previously, they could " +"grow to that size but their performance degraded catastrophically)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2552 +msgid "" +"(Suggested by Raymond Hettinger and implemented by Benjamin Peterson; :issue:" +"`9778`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2555 +msgid "" +"A new macro :c:macro:`Py_VA_COPY` copies the state of the variable argument " +"list. It is equivalent to C99 *va_copy* but available on all Python " +"platforms (:issue:`2443`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2559 +msgid "" +"A new C API function :c:func:`PySys_SetArgvEx` allows an embedded " +"interpreter to set :attr:`sys.argv` without also modifying :attr:`sys.path` " +"(:issue:`5753`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2563 +msgid "" +":c:macro:`PyEval_CallObject` is now only available in macro form. The " +"function declaration, which was kept for backwards compatibility reasons, is " +"now removed -- the macro was introduced in 1997 (:issue:`8276`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2567 +msgid "" +"There is a new function :c:func:`PyLong_AsLongLongAndOverflow` which is " +"analogous to :c:func:`PyLong_AsLongAndOverflow`. They both serve to convert " +"Python :class:`int` into a native fixed-width type while providing detection " +"of cases where the conversion won't fit (:issue:`7767`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2572 +msgid "" +"The :c:func:`PyUnicode_CompareWithASCIIString` function now returns *not " +"equal* if the Python string is *NUL* terminated." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2575 +msgid "" +"There is a new function :c:func:`PyErr_NewExceptionWithDoc` that is like :c:" +"func:`PyErr_NewException` but allows a docstring to be specified. This lets " +"C exceptions have the same self-documenting capabilities as their pure " +"Python counterparts (:issue:`7033`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2580 +msgid "" +"When compiled with the ``--with-valgrind`` option, the pymalloc allocator " +"will be automatically disabled when running under Valgrind. This gives " +"improved memory leak detection when running under Valgrind, while taking " +"advantage of pymalloc at other times (:issue:`2422`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2585 +msgid "" +"Removed the ``O?`` format from the *PyArg_Parse* functions. The format is " +"no longer used and it had never been documented (:issue:`8837`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2588 +msgid "" +"There were a number of other small changes to the C-API. See the :source:" +"`Misc/NEWS` file for a complete list." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2591 +msgid "" +"Also, there were a number of updates to the Mac OS X build, see :source:`Mac/" +"BuildScript/README.txt` for details. For users running a 32/64-bit build, " +"there is a known problem with the default Tcl/Tk on Mac OS X 10.6. " +"Accordingly, we recommend installing an updated alternative such as " +"`ActiveState Tcl/Tk 8.5.9 `_" +"\\. See https://www.python.org/download/mac/tcltk/ for additional details." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2599 +msgid "Porting to Python 3.2" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2604 +msgid "" +"The :mod:`configparser` module has a number of clean-ups. The major change " +"is to replace the old :class:`ConfigParser` class with long-standing " +"preferred alternative :class:`SafeConfigParser`. In addition there are a " +"number of smaller incompatibilities:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2609 +msgid "" +"The interpolation syntax is now validated on :meth:`~configparser." +"ConfigParser.get` and :meth:`~configparser.ConfigParser.set` operations. In " +"the default interpolation scheme, only two tokens with percent signs are " +"valid: ``%(name)s`` and ``%%``, the latter being an escaped percent sign." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2615 +msgid "" +"The :meth:`~configparser.ConfigParser.set` and :meth:`~configparser." +"ConfigParser.add_section` methods now verify that values are actual " +"strings. Formerly, unsupported types could be introduced unintentionally." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2620 +msgid "" +"Duplicate sections or options from a single source now raise either :exc:" +"`~configparser.DuplicateSectionError` or :exc:`~configparser." +"DuplicateOptionError`. Formerly, duplicates would silently overwrite a " +"previous entry." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2625 +msgid "" +"Inline comments are now disabled by default so now the **;** character can " +"be safely used in values." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2628 +msgid "" +"Comments now can be indented. Consequently, for **;** or **#** to appear at " +"the start of a line in multiline values, it has to be interpolated. This " +"keeps comment prefix characters in values from being mistaken as comments." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2632 +msgid "" +"``\"\"`` is now a valid value and is no longer automatically converted to an " +"empty string. For empty strings, use ``\"option =\"`` in a line." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2635 +msgid "" +"The :mod:`nntplib` module was reworked extensively, meaning that its APIs " +"are often incompatible with the 3.1 APIs." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2638 +msgid "" +":class:`bytearray` objects can no longer be used as filenames; instead, they " +"should be converted to :class:`bytes`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2641 +msgid "" +"The :meth:`array.tostring` and :meth:`array.fromstring` have been renamed " +"to :meth:`array.tobytes` and :meth:`array.frombytes` for clarity. The old " +"names have been deprecated. (See :issue:`8990`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2645 +msgid "``PyArg_Parse*()`` functions:" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2647 +msgid "\"t#\" format has been removed: use \"s#\" or \"s*\" instead" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2648 +msgid "\"w\" and \"w#\" formats has been removed: use \"w*\" instead" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2650 +msgid "" +"The :c:type:`PyCObject` type, deprecated in 3.1, has been removed. To wrap " +"opaque C pointers in Python objects, the :c:type:`PyCapsule` API should be " +"used instead; the new type has a well-defined interface for passing typing " +"safety information and a less complicated signature for calling a destructor." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2655 +msgid "" +"The :func:`sys.setfilesystemencoding` function was removed because it had a " +"flawed design." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2658 +msgid "" +"The :func:`random.seed` function and method now salt string seeds with an " +"sha512 hash function. To access the previous version of *seed* in order to " +"reproduce Python 3.1 sequences, set the *version* argument to *1*, ``random." +"seed(s, version=1)``." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2663 +msgid "" +"The previously deprecated :func:`string.maketrans` function has been removed " +"in favor of the static methods :meth:`bytes.maketrans` and :meth:`bytearray." +"maketrans`. This change solves the confusion around which types were " +"supported by the :mod:`string` module. Now, :class:`str`, :class:`bytes`, " +"and :class:`bytearray` each have their own **maketrans** and **translate** " +"methods with intermediate translation tables of the appropriate type." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2673 +msgid "" +"The previously deprecated :func:`contextlib.nested` function has been " +"removed in favor of a plain :keyword:`with` statement which can accept " +"multiple context managers. The latter technique is faster (because it is " +"built-in), and it does a better job finalizing multiple context managers " +"when one of them raises an exception::" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2687 +msgid "" +":func:`struct.pack` now only allows bytes for the ``s`` string pack code. " +"Formerly, it would accept text arguments and implicitly encode them to bytes " +"using UTF-8. This was problematic because it made assumptions about the " +"correct encoding and because a variable-length encoding can fail when " +"writing to fixed length segment of a structure." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2693 +msgid "" +"Code such as ``struct.pack('<6sHHBBB', 'GIF87a', x, y)`` should be rewritten " +"with to use bytes instead of text, ``struct.pack('<6sHHBBB', b'GIF87a', x, " +"y)``." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2696 +msgid "" +"(Discovered by David Beazley and fixed by Victor Stinner; :issue:`10783`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2698 +msgid "" +"The :class:`xml.etree.ElementTree` class now raises an :exc:`xml.etree." +"ElementTree.ParseError` when a parse fails. Previously it raised an :exc:" +"`xml.parsers.expat.ExpatError`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2702 +msgid "" +"The new, longer :func:`str` value on floats may break doctests which rely on " +"the old output format." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2705 +msgid "" +"In :class:`subprocess.Popen`, the default value for *close_fds* is now " +"``True`` under Unix; under Windows, it is ``True`` if the three standard " +"streams are set to ``None``, ``False`` otherwise. Previously, *close_fds* " +"was always ``False`` by default, which produced difficult to solve bugs or " +"race conditions when open file descriptors would leak into the child process." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2712 +msgid "" +"Support for legacy HTTP 0.9 has been removed from :mod:`urllib.request` and :" +"mod:`http.client`. Such support is still present on the server side (in :" +"mod:`http.server`)." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2716 +msgid "(Contributed by Antoine Pitrou, :issue:`10711`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2718 +msgid "" +"SSL sockets in timeout mode now raise :exc:`socket.timeout` when a timeout " +"occurs, rather than a generic :exc:`~ssl.SSLError`." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2721 +msgid "(Contributed by Antoine Pitrou, :issue:`10272`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2723 +msgid "" +"The misleading functions :c:func:`PyEval_AcquireLock()` and :c:func:" +"`PyEval_ReleaseLock()` have been officially deprecated. The thread-state " +"aware APIs (such as :c:func:`PyEval_SaveThread()` and :c:func:" +"`PyEval_RestoreThread()`) should be used instead." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2728 +msgid "" +"Due to security risks, :func:`asyncore.handle_accept` has been deprecated, " +"and a new function, :func:`asyncore.handle_accepted`, was added to replace " +"it." +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2731 +msgid "(Contributed by Giampaolo Rodola in :issue:`6706`.)" +msgstr "" + +#: ../Doc/whatsnew/3.2.rst:2733 +msgid "" +"Due to the new :term:`GIL` implementation, :c:func:`PyEval_InitThreads()` " +"cannot be called before :c:func:`Py_Initialize()` anymore." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:3 +msgid "What's New In Python 3.3" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:45 +msgid "" +"This article explains the new features in Python 3.3, compared to 3.2. " +"Python 3.3 was released on September 29, 2012. For full details, see the " +"`changelog `_." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:51 +msgid ":pep:`398` - Python 3.3 Release Schedule" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:55 ../Doc/whatsnew/3.5.rst:58 +#: ../Doc/whatsnew/3.6.rst:60 +msgid "Summary -- Release highlights" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:60 ../Doc/whatsnew/3.4.rst:80 +#: ../Doc/whatsnew/3.5.rst:60 ../Doc/whatsnew/3.6.rst:65 +msgid "New syntax features:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:62 +msgid "" +"New ``yield from`` expression for :ref:`generator delegation `." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:63 +msgid "The ``u'unicode'`` syntax is accepted again for :class:`str` objects." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:65 ../Doc/whatsnew/3.4.rst:98 +#: ../Doc/whatsnew/3.5.rst:67 +msgid "New library modules:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:67 +msgid ":mod:`faulthandler` (helps debugging low-level crashes)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:68 +msgid "" +":mod:`ipaddress` (high-level objects representing IP addresses and masks)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:69 +msgid ":mod:`lzma` (compress data using the XZ / LZMA algorithm)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:70 +msgid "" +":mod:`unittest.mock` (replace parts of your system under test with mock " +"objects)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:71 +msgid "" +":mod:`venv` (Python :ref:`virtual environments `, as in the popular " +"``virtualenv`` package)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:74 ../Doc/whatsnew/3.5.rst:74 +#: ../Doc/whatsnew/3.6.rst:134 +msgid "New built-in features:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:76 +msgid "Reworked :ref:`I/O exception hierarchy `." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:78 +msgid "Implementation improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:80 +msgid "" +"Rewritten :ref:`import machinery ` based on :mod:`importlib`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:81 +msgid "More compact :ref:`unicode strings `." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:82 +msgid "More compact :ref:`attribute dictionaries `." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:84 +msgid "Significantly Improved Library Modules:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:86 +msgid "C Accelerator for the :ref:`decimal ` module." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:87 +msgid "" +"Better unicode handling in the :ref:`email ` module (:term:" +"`provisional `)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:90 ../Doc/whatsnew/3.4.rst:132 +#: ../Doc/whatsnew/3.5.rst:136 ../Doc/whatsnew/3.6.rst:83 +msgid "Security improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:92 +msgid "Hash randomization is switched on by default." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:94 +msgid "Please read on for a comprehensive list of user-facing changes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:100 +msgid "PEP 405: Virtual Environments" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:102 +msgid "" +"Virtual environments help create separate Python setups while sharing a " +"system-wide base install, for ease of maintenance. Virtual environments " +"have their own set of private site packages (i.e. locally-installed " +"libraries), and are optionally segregated from the system-wide site " +"packages. Their concept and implementation are inspired by the popular " +"``virtualenv`` third-party package, but benefit from tighter integration " +"with the interpreter core." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:110 +msgid "" +"This PEP adds the :mod:`venv` module for programmatic access, and the " +"``pyvenv`` script for command-line access and administration. The Python " +"interpreter checks for a ``pyvenv.cfg``, file whose existence signals the " +"base of a virtual environment's directory tree." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:118 +msgid ":pep:`405` - Python Virtual Environments" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:119 +msgid "PEP written by Carl Meyer; implementation by Carl Meyer and Vinay Sajip" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:123 +msgid "PEP 420: Implicit Namespace Packages" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:125 +msgid "" +"Native support for package directories that don't require ``__init__.py`` " +"marker files and can automatically span multiple path segments (inspired by " +"various third party approaches to namespace packages, as described in :pep:" +"`420`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:133 +msgid ":pep:`420` - Implicit Namespace Packages" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:133 +msgid "" +"PEP written by Eric V. Smith; implementation by Eric V. Smith and Barry " +"Warsaw" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:140 +msgid "" +"PEP 3118: New memoryview implementation and buffer protocol documentation" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:142 +msgid "The implementation of :pep:`3118` has been significantly improved." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:144 +msgid "" +"The new memoryview implementation comprehensively fixes all ownership and " +"lifetime issues of dynamically allocated fields in the Py_buffer struct that " +"led to multiple crash reports. Additionally, several functions that crashed " +"or returned incorrect results for non-contiguous or multi-dimensional input " +"have been fixed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:150 +msgid "" +"The memoryview object now has a PEP-3118 compliant getbufferproc() that " +"checks the consumer's request type. Many new features have been added, most " +"of them work in full generality for non-contiguous arrays and arrays with " +"suboffsets." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:155 +msgid "" +"The documentation has been updated, clearly spelling out responsibilities " +"for both exporters and consumers. Buffer request flags are grouped into " +"basic and compound flags. The memory layout of non-contiguous and multi-" +"dimensional NumPy-style arrays is explained." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:161 ../Doc/whatsnew/3.3.rst:1122 +msgid "Features" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:163 +msgid "" +"All native single character format specifiers in struct module syntax " +"(optionally prefixed with '@') are now supported." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:166 +msgid "" +"With some restrictions, the cast() method allows changing of format and " +"shape of C-contiguous arrays." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:169 +msgid "" +"Multi-dimensional list representations are supported for any array type." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:171 +msgid "Multi-dimensional comparisons are supported for any array type." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:173 +msgid "" +"One-dimensional memoryviews of hashable (read-only) types with formats B, b " +"or c are now hashable. (Contributed by Antoine Pitrou in :issue:`13411`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:176 +msgid "" +"Arbitrary slicing of any 1-D arrays type is supported. For example, it is " +"now possible to reverse a memoryview in O(1) by using a negative step." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:180 ../Doc/whatsnew/3.3.rst:1132 +msgid "API changes" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:182 +msgid "The maximum number of dimensions is officially limited to 64." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:184 +msgid "" +"The representation of empty shape, strides and suboffsets is now an empty " +"tuple instead of None." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:187 +msgid "" +"Accessing a memoryview element with format 'B' (unsigned bytes) now returns " +"an integer (in accordance with the struct module syntax). For returning a " +"bytes object the view must be cast to 'c' first." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:191 +msgid "" +"memoryview comparisons now use the logical structure of the operands and " +"compare all array elements by value. All format strings in struct module " +"syntax are supported. Views with unrecognised format strings are still " +"permitted, but will always compare as unequal, regardless of view contents." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:197 +msgid "" +"For further changes see `Build and C API Changes`_ and `Porting C code`_." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:199 +msgid "(Contributed by Stefan Krah in :issue:`10181`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:203 +msgid ":pep:`3118` - Revising the Buffer Protocol" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:209 +msgid "PEP 393: Flexible String Representation" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:211 +msgid "" +"The Unicode string type is changed to support multiple internal " +"representations, depending on the character with the largest Unicode ordinal " +"(1, 2, or 4 bytes) in the represented string. This allows a space-efficient " +"representation in common cases, but gives access to full UCS-4 on all " +"systems. For compatibility with existing APIs, several representations may " +"exist in parallel; over time, this compatibility should be phased out." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:218 +msgid "On the Python side, there should be no downside to this change." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:220 +msgid "" +"On the C API side, PEP 393 is fully backward compatible. The legacy API " +"should remain available at least five years. Applications using the legacy " +"API will not fully benefit of the memory reduction, or - worse - may use a " +"bit more memory, because Python may have to maintain two versions of each " +"string (in the legacy format and in the new efficient storage)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:227 +msgid "Functionality" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:229 +msgid "Changes introduced by :pep:`393` are the following:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:231 +msgid "" +"Python now always supports the full range of Unicode code points, including " +"non-BMP ones (i.e. from ``U+0000`` to ``U+10FFFF``). The distinction " +"between narrow and wide builds no longer exists and Python now behaves like " +"a wide build, even under Windows." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:236 +msgid "" +"With the death of narrow builds, the problems specific to narrow builds have " +"also been fixed, for example:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:239 +msgid "" +":func:`len` now always returns 1 for non-BMP characters, so " +"``len('\\U0010FFFF') == 1``;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:242 +msgid "" +"surrogate pairs are not recombined in string literals, so ``'\\uDBFF" +"\\uDFFF' != '\\U0010FFFF'``;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:245 +msgid "" +"indexing or slicing non-BMP characters returns the expected value, so " +"``'\\U0010FFFF'[0]`` now returns ``'\\U0010FFFF'`` and not ``'\\uDBFF'``;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:248 +msgid "" +"all other functions in the standard library now correctly handle non-BMP " +"code points." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:251 +msgid "" +"The value of :data:`sys.maxunicode` is now always ``1114111`` (``0x10FFFF`` " +"in hexadecimal). The :c:func:`PyUnicode_GetMax` function still returns " +"either ``0xFFFF`` or ``0x10FFFF`` for backward compatibility, and it should " +"not be used with the new Unicode API (see :issue:`13054`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:256 +msgid "The :file:`./configure` flag ``--with-wide-unicode`` has been removed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:259 +msgid "Performance and resource usage" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:261 +msgid "" +"The storage of Unicode strings now depends on the highest code point in the " +"string:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:263 +msgid "" +"pure ASCII and Latin1 strings (``U+0000-U+00FF``) use 1 byte per code point;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:265 +msgid "BMP strings (``U+0000-U+FFFF``) use 2 bytes per code point;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:267 +msgid "non-BMP strings (``U+10000-U+10FFFF``) use 4 bytes per code point." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:269 +msgid "" +"The net effect is that for most applications, memory usage of string storage " +"should decrease significantly - especially compared to former wide unicode " +"builds - as, in many cases, strings will be pure ASCII even in international " +"contexts (because many strings store non-human language data, such as XML " +"fragments, HTTP headers, JSON-encoded data, etc.). We also hope that it " +"will, for the same reasons, increase CPU cache efficiency on non-trivial " +"applications. The memory usage of Python 3.3 is two to three times smaller " +"than Python 3.2, and a little bit better than Python 2.7, on a Django " +"benchmark (see the PEP for details)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:283 +msgid ":pep:`393` - Flexible String Representation" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:283 +msgid "" +"PEP written by Martin von Löwis; implementation by Torsten Becker and Martin " +"von Löwis." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:290 +msgid "PEP 397: Python Launcher for Windows" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:292 +msgid "" +"The Python 3.3 Windows installer now includes a ``py`` launcher application " +"that can be used to launch Python applications in a version independent " +"fashion." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:296 +msgid "" +"This launcher is invoked implicitly when double-clicking ``*.py`` files. If " +"only a single Python version is installed on the system, that version will " +"be used to run the file. If multiple versions are installed, the most recent " +"version is used by default, but this can be overridden by including a Unix-" +"style \"shebang line\" in the Python script." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:302 +msgid "" +"The launcher can also be used explicitly from the command line as the ``py`` " +"application. Running ``py`` follows the same version selection rules as " +"implicitly launching scripts, but a more specific version can be selected by " +"passing appropriate arguments (such as ``-3`` to request Python 3 when " +"Python 2 is also installed, or ``-2.6`` to specifclly request an earlier " +"Python version when a more recent version is installed)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:309 +msgid "" +"In addition to the launcher, the Windows installer now includes an option to " +"add the newly installed Python to the system PATH. (Contributed by Brian " +"Curtin in :issue:`3561`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:317 +msgid ":pep:`397` - Python Launcher for Windows" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:316 +msgid "" +"PEP written by Mark Hammond and Martin v. Löwis; implementation by Vinay " +"Sajip." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:319 +msgid "Launcher documentation: :ref:`launcher`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:321 +msgid "Installer PATH modification: :ref:`windows-path-mod`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:327 +msgid "PEP 3151: Reworking the OS and IO exception hierarchy" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:329 +msgid "" +"The hierarchy of exceptions raised by operating system errors is now both " +"simplified and finer-grained." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:332 +msgid "" +"You don't have to worry anymore about choosing the appropriate exception " +"type between :exc:`OSError`, :exc:`IOError`, :exc:`EnvironmentError`, :exc:" +"`WindowsError`, :exc:`mmap.error`, :exc:`socket.error` or :exc:`select." +"error`. All these exception types are now only one: :exc:`OSError`. The " +"other names are kept as aliases for compatibility reasons." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:339 +msgid "" +"Also, it is now easier to catch a specific error condition. Instead of " +"inspecting the ``errno`` attribute (or ``args[0]``) for a particular " +"constant from the :mod:`errno` module, you can catch the adequate :exc:" +"`OSError` subclass. The available subclasses are the following:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:344 +msgid ":exc:`BlockingIOError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:345 +msgid ":exc:`ChildProcessError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:346 +msgid ":exc:`ConnectionError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:347 +msgid ":exc:`FileExistsError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:348 +msgid ":exc:`FileNotFoundError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:349 +msgid ":exc:`InterruptedError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:350 +msgid ":exc:`IsADirectoryError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:351 +msgid ":exc:`NotADirectoryError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:352 +msgid ":exc:`PermissionError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:353 +msgid ":exc:`ProcessLookupError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:354 +msgid ":exc:`TimeoutError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:356 +msgid "And the :exc:`ConnectionError` itself has finer-grained subclasses:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:358 +msgid ":exc:`BrokenPipeError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:359 +msgid ":exc:`ConnectionAbortedError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:360 +msgid ":exc:`ConnectionRefusedError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:361 +msgid ":exc:`ConnectionResetError`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:363 +msgid "" +"Thanks to the new exceptions, common usages of the :mod:`errno` can now be " +"avoided. For example, the following code written for Python 3.2::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:379 +msgid "" +"can now be written without the :mod:`errno` import and without manual " +"inspection of exception attributes::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:392 +msgid ":pep:`3151` - Reworking the OS and IO Exception Hierarchy" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:393 +msgid "PEP written and implemented by Antoine Pitrou" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:402 +msgid "PEP 380: Syntax for Delegating to a Subgenerator" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:404 +msgid "" +"PEP 380 adds the ``yield from`` expression, allowing a :term:`generator` to " +"delegate part of its operations to another generator. This allows a section " +"of code containing :keyword:`yield` to be factored out and placed in another " +"generator. Additionally, the subgenerator is allowed to return with a value, " +"and the value is made available to the delegating generator." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:411 +msgid "" +"While designed primarily for use in delegating to a subgenerator, the " +"``yield from`` expression actually allows delegation to arbitrary " +"subiterators." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:414 +msgid "" +"For simple iterators, ``yield from iterable`` is essentially just a " +"shortened form of ``for item in iterable: yield item``::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:424 +msgid "" +"However, unlike an ordinary loop, ``yield from`` allows subgenerators to " +"receive sent and thrown values directly from the calling scope, and return a " +"final value to the outer generator::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:455 +msgid "" +"The main principle driving this change is to allow even generators that are " +"designed to be used with the ``send`` and ``throw`` methods to be split into " +"multiple subgenerators as easily as a single large function can be split " +"into multiple subfunctions." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:464 +msgid ":pep:`380` - Syntax for Delegating to a Subgenerator" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:463 +msgid "" +"PEP written by Greg Ewing; implementation by Greg Ewing, integrated into 3.3 " +"by Renaud Blanch, Ryan Kelly and Nick Coghlan; documentation by Zbigniew " +"Jędrzejewski-Szmek and Nick Coghlan" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:469 +msgid "PEP 409: Suppressing exception context" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:471 +msgid "" +"PEP 409 introduces new syntax that allows the display of the chained " +"exception context to be disabled. This allows cleaner error messages in " +"applications that convert between exception types::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:490 +msgid "" +"Without the ``from None`` suffix to suppress the cause, the original " +"exception would be displayed by default::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:514 +msgid "" +"No debugging capability is lost, as the original exception context remains " +"available if needed (for example, if an intervening library has incorrectly " +"suppressed valuable underlying details)::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:528 +msgid ":pep:`409` - Suppressing exception context" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:528 +msgid "" +"PEP written by Ethan Furman; implemented by Ethan Furman and Nick Coghlan." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:533 +msgid "PEP 414: Explicit Unicode literals" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:535 +msgid "" +"To ease the transition from Python 2 for Unicode aware Python applications " +"that make heavy use of Unicode literals, Python 3.3 once again supports the " +"\"``u``\" prefix for string literals. This prefix has no semantic " +"significance in Python 3, it is provided solely to reduce the number of " +"purely mechanical changes in migrating to Python 3, making it easier for " +"developers to focus on the more significant semantic changes (such as the " +"stricter default separation of binary and text data)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:545 +msgid ":pep:`414` - Explicit Unicode literals" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:546 +msgid "PEP written by Armin Ronacher." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:550 +msgid "PEP 3155: Qualified name for classes and functions" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:552 +msgid "" +"Functions and class objects have a new ``__qualname__`` attribute " +"representing the \"path\" from the module top-level to their definition. " +"For global functions and classes, this is the same as ``__name__``. For " +"other functions and classes, it provides better information about where they " +"were actually defined, and how they might be accessible from the global " +"scope." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:558 +msgid "Example with (non-bound) methods::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:568 +msgid "Example with nested classes::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:584 +msgid "Example with nested functions::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:596 +msgid "" +"The string representation of those objects is also changed to include the " +"new, more precise information::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:606 +msgid ":pep:`3155` - Qualified name for classes and functions" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:607 ../Doc/whatsnew/3.4.rst:539 +#: ../Doc/whatsnew/3.4.rst:1835 +msgid "PEP written and implemented by Antoine Pitrou." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:613 +msgid "PEP 412: Key-Sharing Dictionary" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:615 +msgid "" +"Dictionaries used for the storage of objects' attributes are now able to " +"share part of their internal storage between each other (namely, the part " +"which stores the keys and their respective hashes). This reduces the memory " +"consumption of programs creating many instances of non-builtin types." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:622 +msgid ":pep:`412` - Key-Sharing Dictionary" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:623 +msgid "PEP written and implemented by Mark Shannon." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:627 +msgid "PEP 362: Function Signature Object" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:629 +msgid "" +"A new function :func:`inspect.signature` makes introspection of python " +"callables easy and straightforward. A broad range of callables is " +"supported: python functions, decorated or not, classes, and :func:`functools." +"partial` objects. New classes :class:`inspect.Signature`, :class:`inspect." +"Parameter` and :class:`inspect.BoundArguments` hold information about the " +"call signatures, such as, annotations, default values, parameters kinds, and " +"bound arguments, which considerably simplifies writing decorators and any " +"code that validates or amends calling signatures or arguments." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:641 +msgid ":pep:`362`: - Function Signature Object" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:641 +msgid "" +"PEP written by Brett Cannon, Yury Selivanov, Larry Hastings, Jiwon Seo; " +"implemented by Yury Selivanov." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:646 +msgid "PEP 421: Adding sys.implementation" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:648 +msgid "" +"A new attribute on the :mod:`sys` module exposes details specific to the " +"implementation of the currently running interpreter. The initial set of " +"attributes on :attr:`sys.implementation` are ``name``, ``version``, " +"``hexversion``, and ``cache_tag``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:653 +msgid "" +"The intention of ``sys.implementation`` is to consolidate into one namespace " +"the implementation-specific data used by the standard library. This allows " +"different Python implementations to share a single standard library code " +"base much more easily. In its initial state, ``sys.implementation`` holds " +"only a small portion of the implementation-specific data. Over time that " +"ratio will shift in order to make the standard library more portable." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:660 +msgid "" +"One example of improved standard library portability is ``cache_tag``. As " +"of Python 3.3, ``sys.implementation.cache_tag`` is used by :mod:`importlib` " +"to support :pep:`3147` compliance. Any Python implementation that uses " +"``importlib`` for its built-in import system may use ``cache_tag`` to " +"control the caching behavior for modules." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:667 +msgid "SimpleNamespace" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:669 +msgid "" +"The implementation of ``sys.implementation`` also introduces a new type to " +"Python: :class:`types.SimpleNamespace`. In contrast to a mapping-based " +"namespace, like :class:`dict`, ``SimpleNamespace`` is attribute-based, like :" +"class:`object`. However, unlike ``object``, ``SimpleNamespace`` instances " +"are writable. This means that you can add, remove, and modify the namespace " +"through normal attribute access." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:678 +msgid ":pep:`421` - Adding sys.implementation" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:679 ../Doc/whatsnew/3.6.rst:516 +#: ../Doc/whatsnew/3.6.rst:530 +msgid "PEP written and implemented by Eric Snow." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:685 +msgid "Using importlib as the Implementation of Import" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:686 +msgid "" +":issue:`2377` - Replace __import__ w/ importlib.__import__ :issue:`13959` - " +"Re-implement parts of :mod:`imp` in pure Python :issue:`14605` - Make import " +"machinery explicit :issue:`14646` - Require loaders set __loader__ and " +"__package__" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:691 +msgid "" +"The :func:`__import__` function is now powered by :func:`importlib." +"__import__`. This work leads to the completion of \"phase 2\" of :pep:`302`. " +"There are multiple benefits to this change. First, it has allowed for more " +"of the machinery powering import to be exposed instead of being implicit and " +"hidden within the C code. It also provides a single implementation for all " +"Python VMs supporting Python 3.3 to use, helping to end any VM-specific " +"deviations in import semantics. And finally it eases the maintenance of " +"import, allowing for future growth to occur." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:700 +msgid "" +"For the common user, there should be no visible change in semantics. For " +"those whose code currently manipulates import or calls import " +"programmatically, the code changes that might possibly be required are " +"covered in the `Porting Python code`_ section of this document." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:706 +msgid "New APIs" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:707 +msgid "" +"One of the large benefits of this work is the exposure of what goes into " +"making the import statement work. That means the various importers that were " +"once implicit are now fully exposed as part of the :mod:`importlib` package." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:711 +msgid "" +"The abstract base classes defined in :mod:`importlib.abc` have been expanded " +"to properly delineate between :term:`meta path finders ` " +"and :term:`path entry finders ` by introducing :class:" +"`importlib.abc.MetaPathFinder` and :class:`importlib.abc.PathEntryFinder`, " +"respectively. The old ABC of :class:`importlib.abc.Finder` is now only " +"provided for backwards-compatibility and does not enforce any method " +"requirements." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:719 +msgid "" +"In terms of finders, :class:`importlib.machinery.FileFinder` exposes the " +"mechanism used to search for source and bytecode files of a module. " +"Previously this class was an implicit member of :attr:`sys.path_hooks`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:723 +msgid "" +"For loaders, the new abstract base class :class:`importlib.abc.FileLoader` " +"helps write a loader that uses the file system as the storage mechanism for " +"a module's code. The loader for source files (:class:`importlib.machinery." +"SourceFileLoader`), sourceless bytecode files (:class:`importlib.machinery." +"SourcelessFileLoader`), and extension modules (:class:`importlib.machinery." +"ExtensionFileLoader`) are now available for direct use." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:731 +msgid "" +":exc:`ImportError` now has ``name`` and ``path`` attributes which are set " +"when there is relevant data to provide. The message for failed imports will " +"also provide the full name of the module now instead of just the tail end of " +"the module's name." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:736 +msgid "" +"The :func:`importlib.invalidate_caches` function will now call the method " +"with the same name on all finders cached in :attr:`sys.path_importer_cache` " +"to help clean up any stored state as necessary." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:741 +msgid "Visible Changes" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:743 +msgid "" +"For potential required changes to code, see the `Porting Python code`_ " +"section." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:746 +msgid "" +"Beyond the expanse of what :mod:`importlib` now exposes, there are other " +"visible changes to import. The biggest is that :attr:`sys.meta_path` and :" +"attr:`sys.path_hooks` now store all of the meta path finders and path entry " +"hooks used by import. Previously the finders were implicit and hidden " +"within the C code of import instead of being directly exposed. This means " +"that one can now easily remove or change the order of the various finders to " +"fit one's needs." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:753 +msgid "" +"Another change is that all modules have a ``__loader__`` attribute, storing " +"the loader used to create the module. :pep:`302` has been updated to make " +"this attribute mandatory for loaders to implement, so in the future once 3rd-" +"party loaders have been updated people will be able to rely on the existence " +"of the attribute. Until such time, though, import is setting the module post-" +"load." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:759 +msgid "" +"Loaders are also now expected to set the ``__package__`` attribute from :pep:" +"`366`. Once again, import itself is already setting this on all loaders " +"from :mod:`importlib` and import itself is setting the attribute post-load." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:763 +msgid "" +"``None`` is now inserted into :attr:`sys.path_importer_cache` when no finder " +"can be found on :attr:`sys.path_hooks`. Since :class:`imp.NullImporter` is " +"not directly exposed on :attr:`sys.path_hooks` it could no longer be relied " +"upon to always be available to use as a value representing no finder found." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:768 +msgid "" +"All other changes relate to semantic changes which should be taken into " +"consideration when updating code for Python 3.3, and thus should be read " +"about in the `Porting Python code`_ section of this document." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:772 +msgid "(Implementation by Brett Cannon)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:780 +msgid "" +"Added support for Unicode name aliases and named sequences. Both :func:" +"`unicodedata.lookup()` and ``'\\N{...}'`` now resolve name aliases, and :" +"func:`unicodedata.lookup()` resolves named sequences too." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:784 +msgid "(Contributed by Ezio Melotti in :issue:`12753`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:786 +msgid "Unicode database updated to UCD version 6.1.0" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:788 +msgid "" +"Equality comparisons on :func:`range` objects now return a result reflecting " +"the equality of the underlying sequences generated by those range objects. (:" +"issue:`13201`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:792 +msgid "" +"The ``count()``, ``find()``, ``rfind()``, ``index()`` and ``rindex()`` " +"methods of :class:`bytes` and :class:`bytearray` objects now accept an " +"integer between 0 and 255 as their first argument." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:796 +msgid "(Contributed by Petri Lehtinen in :issue:`12170`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:798 +msgid "" +"The ``rjust()``, ``ljust()``, and ``center()`` methods of :class:`bytes` " +"and :class:`bytearray` now accept a :class:`bytearray` for the ``fill`` " +"argument. (Contributed by Petri Lehtinen in :issue:`12380`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:802 +msgid "" +"New methods have been added to :class:`list` and :class:`bytearray`: " +"``copy()`` and ``clear()`` (:issue:`10516`). Consequently, :class:" +"`~collections.abc.MutableSequence` now also defines a :meth:`~collections." +"abc.MutableSequence.clear` method (:issue:`11388`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:807 +msgid "" +"Raw bytes literals can now be written ``rb\"...\"`` as well as ``br\"...\"``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:809 +msgid "(Contributed by Antoine Pitrou in :issue:`13748`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:811 +msgid "" +":meth:`dict.setdefault` now does only one lookup for the given key, making " +"it atomic when used with built-in types." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:814 +msgid "(Contributed by Filip Gruszczyński in :issue:`13521`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:816 +msgid "" +"The error messages produced when a function call does not match the function " +"signature have been significantly improved." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:819 +msgid "(Contributed by Benjamin Peterson.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:823 +msgid "A Finer-Grained Import Lock" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:825 +msgid "" +"Previous versions of CPython have always relied on a global import lock. " +"This led to unexpected annoyances, such as deadlocks when importing a module " +"would trigger code execution in a different thread as a side-effect. Clumsy " +"workarounds were sometimes employed, such as the :c:func:" +"`PyImport_ImportModuleNoBlock` C API function." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:831 +msgid "" +"In Python 3.3, importing a module takes a per-module lock. This correctly " +"serializes importation of a given module from multiple threads (preventing " +"the exposure of incompletely initialized modules), while eliminating the " +"aforementioned annoyances." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:836 +msgid "(Contributed by Antoine Pitrou in :issue:`9260`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:840 +msgid "Builtin functions and types" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:842 +msgid "" +":func:`open` gets a new *opener* parameter: the underlying file descriptor " +"for the file object is then obtained by calling *opener* with (*file*, " +"*flags*). It can be used to use custom flags like :data:`os.O_CLOEXEC` for " +"example. The ``'x'`` mode was added: open for exclusive creation, failing if " +"the file already exists." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:847 +msgid "" +":func:`print`: added the *flush* keyword argument. If the *flush* keyword " +"argument is true, the stream is forcibly flushed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:849 +msgid "" +":func:`hash`: hash randomization is enabled by default, see :meth:`object." +"__hash__` and :envvar:`PYTHONHASHSEED`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:851 +msgid "" +"The :class:`str` type gets a new :meth:`~str.casefold` method: return a " +"casefolded copy of the string, casefolded strings may be used for caseless " +"matching. For example, ``'ß'.casefold()`` returns ``'ss'``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:854 +msgid "" +"The sequence documentation has been substantially rewritten to better " +"explain the binary/text sequence distinction and to provide specific " +"documentation sections for the individual builtin sequence types (:issue:" +"`4966`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:861 ../Doc/whatsnew/3.4.rst:458 +#: ../Doc/whatsnew/3.5.rst:724 ../Doc/whatsnew/3.6.rst:578 +msgid "New Modules" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:864 ../Doc/whatsnew/3.5.rst:1138 +#: ../Doc/whatsnew/3.6.rst:707 +msgid "faulthandler" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:866 +msgid "" +"This new debug module :mod:`faulthandler` contains functions to dump Python " +"tracebacks explicitly, on a fault (a crash like a segmentation fault), after " +"a timeout, or on a user signal. Call :func:`faulthandler.enable` to install " +"fault handlers for the :const:`SIGSEGV`, :const:`SIGFPE`, :const:`SIGABRT`, :" +"const:`SIGBUS`, and :const:`SIGILL` signals. You can also enable them at " +"startup by setting the :envvar:`PYTHONFAULTHANDLER` environment variable or " +"by using :option:`-X` ``faulthandler`` command line option." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:874 +msgid "Example of a segmentation fault on Linux:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:890 ../Doc/whatsnew/3.4.rst:1059 +#: ../Doc/whatsnew/3.5.rst:1336 +msgid "ipaddress" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:892 +msgid "" +"The new :mod:`ipaddress` module provides tools for creating and manipulating " +"objects representing IPv4 and IPv6 addresses, networks and interfaces (i.e. " +"an IP address associated with a specific IP subnet)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:896 +msgid "(Contributed by Google and Peter Moody in :pep:`3144`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:899 ../Doc/whatsnew/3.5.rst:1437 +msgid "lzma" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:901 +msgid "" +"The newly-added :mod:`lzma` module provides data compression and " +"decompression using the LZMA algorithm, including support for the ``.xz`` " +"and ``.lzma`` file formats." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:905 +msgid "(Contributed by Nadeem Vawda and Per Øyvind Karlsen in :issue:`6715`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:909 ../Doc/whatsnew/3.4.rst:589 +#: ../Doc/whatsnew/3.5.rst:761 ../Doc/whatsnew/3.6.rst:584 +msgid "Improved Modules" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:914 +msgid "" +"Improved support for abstract base classes containing descriptors composed " +"with abstract methods. The recommended approach to declaring abstract " +"descriptors is now to provide :attr:`__isabstractmethod__` as a dynamically " +"updated property. The built-in descriptors have been updated accordingly." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:919 ../Doc/whatsnew/3.3.rst:2245 +msgid "" +":class:`abc.abstractproperty` has been deprecated, use :class:`property` " +"with :func:`abc.abstractmethod` instead." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:921 ../Doc/whatsnew/3.3.rst:2247 +msgid "" +":class:`abc.abstractclassmethod` has been deprecated, use :class:" +"`classmethod` with :func:`abc.abstractmethod` instead." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:923 ../Doc/whatsnew/3.3.rst:2249 +msgid "" +":class:`abc.abstractstaticmethod` has been deprecated, use :class:" +"`staticmethod` with :func:`abc.abstractmethod` instead." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:926 +msgid "(Contributed by Darren Dale in :issue:`11610`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:928 +msgid "" +":meth:`abc.ABCMeta.register` now returns the registered subclass, which " +"means it can now be used as a class decorator (:issue:`10868`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:933 +msgid "array" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:935 +msgid "" +"The :mod:`array` module supports the :c:type:`long long` type using ``q`` " +"and ``Q`` type codes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:938 +msgid "(Contributed by Oren Tirosh and Hirokazu Yamamoto in :issue:`1172711`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:942 ../Doc/whatsnew/3.4.rst:645 +msgid "base64" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:944 +msgid "" +"ASCII-only Unicode strings are now accepted by the decoding functions of " +"the :mod:`base64` modern interface. For example, ``base64." +"b64decode('YWJj')`` returns ``b'abc'``. (Contributed by Catalin Iacob in :" +"issue:`13641`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:950 +msgid "binascii" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:952 +msgid "" +"In addition to the binary objects they normally accept, the ``a2b_`` " +"functions now all also accept ASCII-only strings as input. (Contributed by " +"Antoine Pitrou in :issue:`13637`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:958 ../Doc/whatsnew/3.5.rst:871 +msgid "bz2" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:960 +msgid "" +"The :mod:`bz2` module has been rewritten from scratch. In the process, " +"several new features have been added:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:963 +msgid "" +"New :func:`bz2.open` function: open a bzip2-compressed file in binary or " +"text mode." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:966 +msgid "" +":class:`bz2.BZ2File` can now read from and write to arbitrary file-like " +"objects, by means of its constructor's *fileobj* argument." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:969 +msgid "(Contributed by Nadeem Vawda in :issue:`5863`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:971 +msgid "" +":class:`bz2.BZ2File` and :func:`bz2.decompress` can now decompress multi-" +"stream inputs (such as those produced by the :program:`pbzip2` tool). :class:" +"`bz2.BZ2File` can now also be used to create this type of file, using the " +"``'a'`` (append) mode." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:976 +msgid "(Contributed by Nir Aides in :issue:`1625`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:978 +msgid "" +":class:`bz2.BZ2File` now implements all of the :class:`io.BufferedIOBase` " +"API, except for the :meth:`detach` and :meth:`truncate` methods." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:983 +msgid "codecs" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:985 +msgid "" +"The :mod:`~encodings.mbcs` codec has been rewritten to handle correctly " +"``replace`` and ``ignore`` error handlers on all Windows versions. The :mod:" +"`~encodings.mbcs` codec now supports all error handlers, instead of only " +"``replace`` to encode and ``ignore`` to decode." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:990 +msgid "" +"A new Windows-only codec has been added: ``cp65001`` (:issue:`13216`). It is " +"the Windows code page 65001 (Windows UTF-8, ``CP_UTF8``). For example, it " +"is used by ``sys.stdout`` if the console output code page is set to cp65001 " +"(e.g., using ``chcp 65001`` command)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:995 +msgid "" +"Multibyte CJK decoders now resynchronize faster. They only ignore the first " +"byte of an invalid byte sequence. For example, ``b'\\xff\\n'." +"decode('gb2312', 'replace')`` now returns a ``\\n`` after the replacement " +"character." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:999 +msgid "(:issue:`12016`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1001 +msgid "" +"Incremental CJK codec encoders are no longer reset at each call to their " +"encode() methods. For example::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1009 +msgid "" +"This example gives ``b'~{Np~}~{J)~}~{l6~}~{HK~}~{!#~} Bye.'`` with older " +"Python versions." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1012 +msgid "(:issue:`12100`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1014 +msgid "The ``unicode_internal`` codec has been deprecated." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1020 +msgid "" +"Addition of a new :class:`~collections.ChainMap` class to allow treating a " +"number of mappings as a single unit. (Written by Raymond Hettinger for :" +"issue:`11089`, made public in :issue:`11297`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1024 +msgid "" +"The abstract base classes have been moved in a new :mod:`collections.abc` " +"module, to better differentiate between the abstract and the concrete " +"collections classes. Aliases for ABCs are still present in the :mod:" +"`collections` module to preserve existing imports. (:issue:`11085`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1031 +msgid "" +"The :class:`~collections.Counter` class now supports the unary ``+`` and ``-" +"`` operators, as well as the in-place operators ``+=``, ``-=``, ``|=``, and " +"``&=``. (Contributed by Raymond Hettinger in :issue:`13121`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1039 +msgid "" +":class:`~contextlib.ExitStack` now provides a solid foundation for " +"programmatic manipulation of context managers and similar cleanup " +"functionality. Unlike the previous ``contextlib.nested`` API (which was " +"deprecated and removed), the new API is designed to work correctly " +"regardless of whether context managers acquire their resources in their " +"``__init__`` method (for example, file objects) or in their ``__enter__`` " +"method (for example, synchronisation objects from the :mod:`threading` " +"module)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1048 +msgid "(:issue:`13585`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1052 +msgid "crypt" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1054 +msgid "" +"Addition of salt and modular crypt format (hashing method) and the :func:" +"`~crypt.mksalt` function to the :mod:`crypt` module." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1057 +msgid "(:issue:`10924`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1060 ../Doc/whatsnew/3.5.rst:1046 +msgid "curses" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1062 +msgid "" +"If the :mod:`curses` module is linked to the ncursesw library, use Unicode " +"functions when Unicode strings or characters are passed (e.g. :c:func:" +"`waddwstr`), and bytes functions otherwise (e.g. :c:func:`waddstr`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1065 +msgid "Use the locale encoding instead of ``utf-8`` to encode Unicode strings." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1066 +msgid "" +":class:`curses.window` has a new :attr:`curses.window.encoding` attribute." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1067 +msgid "" +"The :class:`curses.window` class has a new :meth:`~curses.window.get_wch` " +"method to get a wide character" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1069 +msgid "" +"The :mod:`curses` module has a new :meth:`~curses.unget_wch` function to " +"push a wide character so the next :meth:`~curses.window.get_wch` will return " +"it" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1073 +msgid "(Contributed by Iñigo Serna in :issue:`6755`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1076 ../Doc/whatsnew/3.6.rst:659 +msgid "datetime" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1078 +msgid "" +"Equality comparisons between naive and aware :class:`~datetime.datetime` " +"instances now return :const:`False` instead of raising :exc:`TypeError` (:" +"issue:`15006`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1081 +msgid "" +"New :meth:`datetime.datetime.timestamp` method: Return POSIX timestamp " +"corresponding to the :class:`~datetime.datetime` instance." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1083 +msgid "" +"The :meth:`datetime.datetime.strftime` method supports formatting years " +"older than 1000." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1085 +msgid "" +"The :meth:`datetime.datetime.astimezone` method can now be called without " +"arguments to convert datetime instance to the system timezone." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1093 +msgid "decimal" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1096 +msgid ":issue:`7652` - integrate fast native decimal arithmetic." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1096 +msgid "C-module and libmpdec written by Stefan Krah." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1098 +msgid "" +"The new C version of the decimal module integrates the high speed libmpdec " +"library for arbitrary precision correctly-rounded decimal floating point " +"arithmetic. libmpdec conforms to IBM's General Decimal Arithmetic " +"Specification." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1102 +msgid "" +"Performance gains range from 10x for database applications to 100x for " +"numerically intensive applications. These numbers are expected gains for " +"standard precisions used in decimal floating point arithmetic. Since the " +"precision is user configurable, the exact figures may vary. For example, in " +"integer bignum arithmetic the differences can be significantly higher." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1108 +msgid "" +"The following table is meant as an illustration. Benchmarks are available at " +"http://www.bytereef.org/mpdecimal/quickstart.html." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1112 +msgid "decimal.py" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1112 +msgid "_decimal" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1112 +msgid "speedup" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1114 +msgid "pi" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1114 +msgid "42.02s" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1114 +msgid "0.345s" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1114 +msgid "120x" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1116 +msgid "telco" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1116 +msgid "172.19s" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1116 +msgid "5.68s" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1116 +msgid "30x" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1118 +msgid "psycopg" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1118 +msgid "3.57s" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1118 +msgid "0.29s" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1118 +msgid "12x" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1124 +msgid "" +"The :exc:`~decimal.FloatOperation` signal optionally enables stricter " +"semantics for mixing floats and Decimals." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1127 +msgid "" +"If Python is compiled without threads, the C version automatically disables " +"the expensive thread local context machinery. In this case, the variable :" +"data:`~decimal.HAVE_THREADS` is set to ``False``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1134 +msgid "" +"The C module has the following context limits, depending on the machine " +"architecture:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1138 +msgid "32-bit" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1138 +msgid "64-bit" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1140 +msgid ":const:`MAX_PREC`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1140 ../Doc/whatsnew/3.3.rst:1142 +msgid ":const:`425000000`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1140 ../Doc/whatsnew/3.3.rst:1142 +msgid ":const:`999999999999999999`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1142 +msgid ":const:`MAX_EMAX`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1144 +msgid ":const:`MIN_EMIN`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1144 +msgid ":const:`-425000000`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1144 +msgid ":const:`-999999999999999999`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1147 +msgid "" +"In the context templates (:class:`~decimal.DefaultContext`, :class:`~decimal." +"BasicContext` and :class:`~decimal.ExtendedContext`) the magnitude of :attr:" +"`~decimal.Context.Emax` and :attr:`~decimal.Context.Emin` has changed to :" +"const:`999999`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1152 +msgid "" +"The :class:`~decimal.Decimal` constructor in decimal.py does not observe the " +"context limits and converts values with arbitrary exponents or precision " +"exactly. Since the C version has internal limits, the following scheme is " +"used: If possible, values are converted exactly, otherwise :exc:`~decimal." +"InvalidOperation` is raised and the result is NaN. In the latter case it is " +"always possible to use :meth:`~decimal.Context.create_decimal` in order to " +"obtain a rounded or inexact value." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1161 +msgid "" +"The power function in decimal.py is always correctly-rounded. In the C " +"version, it is defined in terms of the correctly-rounded :meth:`~decimal." +"Decimal.exp` and :meth:`~decimal.Decimal.ln` functions, but the final result " +"is only \"almost always correctly rounded\"." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1167 +msgid "" +"In the C version, the context dictionary containing the signals is a :class:" +"`~collections.abc.MutableMapping`. For speed reasons, :attr:`~decimal." +"Context.flags` and :attr:`~decimal.Context.traps` always refer to the same :" +"class:`~collections.abc.MutableMapping` that the context was initialized " +"with. If a new signal dictionary is assigned, :attr:`~decimal.Context.flags` " +"and :attr:`~decimal.Context.traps` are updated with the new values, but they " +"do not reference the RHS dictionary." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1177 +msgid "" +"Pickling a :class:`~decimal.Context` produces a different output in order to " +"have a common interchange format for the Python and C versions." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1181 +msgid "" +"The order of arguments in the :class:`~decimal.Context` constructor has been " +"changed to match the order displayed by :func:`repr`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1185 +msgid "" +"The ``watchexp`` parameter in the :meth:`~decimal.Decimal.quantize` method " +"is deprecated." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1195 +msgid "Policy Framework" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1197 +msgid "" +"The email package now has a :mod:`~email.policy` framework. A :class:" +"`~email.policy.Policy` is an object with several methods and properties that " +"control how the email package behaves. The primary policy for Python 3.3 is " +"the :class:`~email.policy.Compat32` policy, which provides backward " +"compatibility with the email package in Python 3.2. A ``policy`` can be " +"specified when an email message is parsed by a :mod:`~email.parser`, or when " +"a :class:`~email.message.Message` object is created, or when an email is " +"serialized using a :mod:`~email.generator`. Unless overridden, a policy " +"passed to a ``parser`` is inherited by all the ``Message`` object and sub-" +"objects created by the ``parser``. By default a ``generator`` will use the " +"policy of the ``Message`` object it is serializing. The default policy is :" +"data:`~email.policy.compat32`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1210 +msgid "The minimum set of controls implemented by all ``policy`` objects are:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1215 +msgid "max_line_length" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1215 +msgid "" +"The maximum length, excluding the linesep character(s), individual lines may " +"have when a ``Message`` is serialized. Defaults to 78." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1219 +msgid "linesep" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1219 +msgid "" +"The character used to separate individual lines when a ``Message`` is " +"serialized. Defaults to ``\\n``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1222 +msgid "cte_type" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1222 +msgid "" +"``7bit`` or ``8bit``. ``8bit`` applies only to a ``Bytes`` ``generator``, " +"and means that non-ASCII may be used where allowed by the protocol (or where " +"it exists in the original input)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1227 +msgid "raise_on_defect" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1227 +msgid "" +"Causes a ``parser`` to raise error when defects are encountered instead of " +"adding them to the ``Message`` object's ``defects`` list." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1232 +msgid "" +"A new policy instance, with new settings, is created using the :meth:`~email." +"policy.Policy.clone` method of policy objects. ``clone`` takes any of the " +"above controls as keyword arguments. Any control not specified in the call " +"retains its default value. Thus you can create a policy that uses ``\\r" +"\\n`` linesep characters like this::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1240 +msgid "" +"Policies can be used to make the generation of messages in the format needed " +"by your application simpler. Instead of having to remember to specify " +"``linesep='\\r\\n'`` in all the places you call a ``generator``, you can " +"specify it once, when you set the policy used by the ``parser`` or the " +"``Message``, whichever your program uses to create ``Message`` objects. On " +"the other hand, if you need to generate messages in multiple forms, you can " +"still specify the parameters in the appropriate ``generator`` call. Or you " +"can have custom policy instances for your different cases, and pass those in " +"when you create the ``generator``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1252 +msgid "Provisional Policy with New Header API" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1254 +msgid "" +"While the policy framework is worthwhile all by itself, the main motivation " +"for introducing it is to allow the creation of new policies that implement " +"new features for the email package in a way that maintains backward " +"compatibility for those who do not use the new policies. Because the new " +"policies introduce a new API, we are releasing them in Python 3.3 as a :term:" +"`provisional policy `. Backwards incompatible changes " +"(up to and including removal of the code) may occur if deemed necessary by " +"the core developers." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1262 +msgid "" +"The new policies are instances of :class:`~email.policy.EmailPolicy`, and " +"add the following additional controls:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1268 +msgid "refold_source" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1268 +msgid "" +"Controls whether or not headers parsed by a :mod:`~email.parser` are " +"refolded by the :mod:`~email.generator`. It can be ``none``, ``long``, or " +"``all``. The default is ``long``, which means that source headers with a " +"line longer than ``max_line_length`` get refolded. ``none`` means no line " +"get refolded, and ``all`` means that all lines get refolded." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1277 +msgid "header_factory" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1277 +msgid "" +"A callable that take a ``name`` and ``value`` and produces a custom header " +"object." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1281 +msgid "" +"The ``header_factory`` is the key to the new features provided by the new " +"policies. When one of the new policies is used, any header retrieved from a " +"``Message`` object is an object produced by the ``header_factory``, and any " +"time you set a header on a ``Message`` it becomes an object produced by " +"``header_factory``. All such header objects have a ``name`` attribute equal " +"to the header name. Address and Date headers have additional attributes " +"that give you access to the parsed data of the header. This means you can " +"now do things like this::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1309 +msgid "" +"You will note that the unicode display name is automatically encoded as " +"``utf-8`` when the message is serialized, but that when the header is " +"accessed directly, you get the unicode version. This eliminates any need to " +"deal with the :mod:`email.header` :meth:`~email.header.decode_header` or :" +"meth:`~email.header.make_header` functions." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1315 +msgid "You can also create addresses from parts::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1325 +msgid "Decoding to unicode is done automatically::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1331 +msgid "" +"When you parse a message, you can use the ``addresses`` and ``groups`` " +"attributes of the header objects to access the groups and individual " +"addresses::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1340 +msgid "" +"In summary, if you use one of the new policies, header manipulation works " +"the way it ought to: your application works with unicode strings, and the " +"email package transparently encodes and decodes the unicode to and from the " +"RFC standard Content Transfer Encodings." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1346 +msgid "Other API Changes" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1348 +msgid "" +"New :class:`~email.parser.BytesHeaderParser`, added to the :mod:`~email." +"parser` module to complement :class:`~email.parser.HeaderParser` and " +"complete the Bytes API." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1352 +msgid "New utility functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1354 +msgid "" +":func:`~email.utils.format_datetime`: given a :class:`~datetime.datetime`, " +"produce a string formatted for use in an email header." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1357 +msgid "" +":func:`~email.utils.parsedate_to_datetime`: given a date string from an " +"email header, convert it into an aware :class:`~datetime.datetime`, or a " +"naive :class:`~datetime.datetime` if the offset is ``-0000``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1361 +msgid "" +":func:`~email.utils.localtime`: With no argument, returns the current local " +"time as an aware :class:`~datetime.datetime` using the local :class:" +"`~datetime.timezone`. Given an aware :class:`~datetime.datetime`, converts " +"it into an aware :class:`~datetime.datetime` using the local :class:" +"`~datetime.timezone`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1369 +msgid "ftplib" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1371 +msgid "" +":class:`ftplib.FTP` now accepts a ``source_address`` keyword argument to " +"specify the ``(host, port)`` to use as the source address in the bind call " +"when creating the outgoing socket. (Contributed by Giampaolo Rodolà in :" +"issue:`8594`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1376 +msgid "" +"The :class:`~ftplib.FTP_TLS` class now provides a new :func:`~ftplib.FTP_TLS." +"ccc` function to revert control channel back to plaintext. This can be " +"useful to take advantage of firewalls that know how to handle NAT with non-" +"secure FTP without opening fixed ports. (Contributed by Giampaolo Rodolà " +"in :issue:`12139`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1382 +msgid "" +"Added :meth:`ftplib.FTP.mlsd` method which provides a parsable directory " +"listing format and deprecates :meth:`ftplib.FTP.nlst` and :meth:`ftplib.FTP." +"dir`. (Contributed by Giampaolo Rodolà in :issue:`11072`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1390 +msgid "" +"The :func:`functools.lru_cache` decorator now accepts a ``typed`` keyword " +"argument (that defaults to ``False`` to ensure that it caches values of " +"different types that compare equal in separate cache slots. (Contributed by " +"Raymond Hettinger in :issue:`13227`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1397 ../Doc/whatsnew/3.4.rst:885 +msgid "gc" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1399 +msgid "" +"It is now possible to register callbacks invoked by the garbage collector " +"before and after collection using the new :data:`~gc.callbacks` list." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1404 ../Doc/whatsnew/3.4.rst:917 +msgid "hmac" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1406 +msgid "" +"A new :func:`~hmac.compare_digest` function has been added to prevent side " +"channel attacks on digests through timing analysis. (Contributed by Nick " +"Coghlan and Christian Heimes in :issue:`15061`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1412 ../Doc/whatsnew/3.4.rst:956 +#: ../Doc/whatsnew/3.5.rst:1193 +msgid "http" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1414 +msgid "" +":class:`http.server.BaseHTTPRequestHandler` now buffers the headers and " +"writes them all at once when :meth:`~http.server.BaseHTTPRequestHandler." +"end_headers` is called. A new method :meth:`~http.server." +"BaseHTTPRequestHandler.flush_headers` can be used to directly manage when " +"the accumlated headers are sent. (Contributed by Andrew Schaaf in :issue:" +"`3709`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1420 +msgid "" +":class:`http.server` now produces valid ``HTML 4.01 strict`` output. " +"(Contributed by Ezio Melotti in :issue:`13295`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1423 +msgid "" +":class:`http.client.HTTPResponse` now has a :meth:`~http.client.HTTPResponse." +"readinto` method, which means it can be used as an :class:`io.RawIOBase` " +"class. (Contributed by John Kuhn in :issue:`13464`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1432 +msgid "" +":class:`html.parser.HTMLParser` is now able to parse broken markup without " +"raising errors, therefore the *strict* argument of the constructor and the :" +"exc:`~html.parser.HTMLParseError` exception are now deprecated. The ability " +"to parse broken markup is the result of a number of bug fixes that are also " +"available on the latest bug fix releases of Python 2.7/3.2. (Contributed by " +"Ezio Melotti in :issue:`15114`, and :issue:`14538`, :issue:`13993`, :issue:" +"`13960`, :issue:`13358`, :issue:`1745761`, :issue:`755670`, :issue:`13357`, :" +"issue:`12629`, :issue:`1200313`, :issue:`670664`, :issue:`13273`, :issue:" +"`12888`, :issue:`7311`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1442 +msgid "" +"A new :data:`~html.entities.html5` dictionary that maps HTML5 named " +"character references to the equivalent Unicode character(s) (e.g. " +"``html5['gt;'] == '>'``) has been added to the :mod:`html.entities` module. " +"The dictionary is now also used by :class:`~html.parser.HTMLParser`. " +"(Contributed by Ezio Melotti in :issue:`11113` and :issue:`15156`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1452 +msgid "" +"The :class:`~imaplib.IMAP4_SSL` constructor now accepts an SSLContext " +"parameter to control parameters of the secure channel." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1455 +msgid "(Contributed by Sijin Joseph in :issue:`8808`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1461 +msgid "" +"A new :func:`~inspect.getclosurevars` function has been added. This function " +"reports the current binding of all names referenced from the function body " +"and where those names were resolved, making it easier to verify correct " +"internal state when testing code that relies on stateful closures." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1466 +msgid "(Contributed by Meador Inge and Nick Coghlan in :issue:`13062`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1468 +msgid "" +"A new :func:`~inspect.getgeneratorlocals` function has been added. This " +"function reports the current binding of local variables in the generator's " +"stack frame, making it easier to verify correct internal state when testing " +"generators." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1473 +msgid "(Contributed by Meador Inge in :issue:`15153`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1478 +msgid "" +"The :func:`~io.open` function has a new ``'x'`` mode that can be used to " +"exclusively create a new file, and raise a :exc:`FileExistsError` if the " +"file already exists. It is based on the C11 'x' mode to fopen()." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1482 +msgid "(Contributed by David Townshend in :issue:`12760`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1484 +msgid "" +"The constructor of the :class:`~io.TextIOWrapper` class has a new " +"*write_through* optional argument. If *write_through* is ``True``, calls to :" +"meth:`~io.TextIOWrapper.write` are guaranteed not to be buffered: any data " +"written on the :class:`~io.TextIOWrapper` object is immediately handled to " +"its underlying binary buffer." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1494 +msgid "" +":func:`~itertools.accumulate` now takes an optional ``func`` argument for " +"providing a user-supplied binary function." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1501 +msgid "" +"The :func:`~logging.basicConfig` function now supports an optional " +"``handlers`` argument taking an iterable of handlers to be added to the root " +"logger." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1504 +msgid "" +"A class level attribute :attr:`~logging.handlers.SysLogHandler.append_nul` " +"has been added to :class:`~logging.handlers.SysLogHandler` to allow control " +"of the appending of the ``NUL`` (``\\000``) byte to syslog records, since " +"for some deamons it is required while for others it is passed through to the " +"log." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1514 +msgid "" +"The :mod:`math` module has a new function, :func:`~math.log2`, which " +"returns the base-2 logarithm of *x*." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1517 +msgid "(Written by Mark Dickinson in :issue:`11888`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1521 ../Doc/whatsnew/3.4.rst:1114 +msgid "mmap" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1523 +msgid "" +"The :meth:`~mmap.mmap.read` method is now more compatible with other file-" +"like objects: if the argument is omitted or specified as ``None``, it " +"returns the bytes from the current file position to the end of the mapping. " +"(Contributed by Petri Lehtinen in :issue:`12021`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1530 ../Doc/whatsnew/3.4.rst:1121 +#: ../Doc/whatsnew/3.5.rst:1460 +msgid "multiprocessing" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1532 +msgid "" +"The new :func:`multiprocessing.connection.wait` function allows polling " +"multiple objects (such as connections, sockets and pipes) with a timeout. " +"(Contributed by Richard Oudkerk in :issue:`12328`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1536 +msgid "" +":class:`multiprocessing.Connection` objects can now be transferred over " +"multiprocessing connections. (Contributed by Richard Oudkerk in :issue:" +"`4892`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1540 +msgid "" +":class:`multiprocessing.Process` now accepts a ``daemon`` keyword argument " +"to override the default behavior of inheriting the ``daemon`` flag from the " +"parent process (:issue:`6064`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1544 +msgid "" +"New attribute :data:`multiprocessing.Process.sentinel` allows a program to " +"wait on multiple :class:`~multiprocessing.Process` objects at one time using " +"the appropriate OS primitives (for example, :mod:`select` on posix systems)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1549 +msgid "" +"New methods :meth:`multiprocessing.pool.Pool.starmap` and :meth:" +"`~multiprocessing.pool.Pool.starmap_async` provide :func:`itertools.starmap` " +"equivalents to the existing :meth:`multiprocessing.pool.Pool.map` and :meth:" +"`~multiprocessing.pool.Pool.map_async` functions. (Contributed by Hynek " +"Schlawack in :issue:`12708`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1558 +msgid "nntplib" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1560 +msgid "" +"The :class:`nntplib.NNTP` class now supports the context management protocol " +"to unconditionally consume :exc:`socket.error` exceptions and to close the " +"NNTP connection when done::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1571 +msgid "(Contributed by Giampaolo Rodolà in :issue:`9795`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1577 +msgid "" +"The :mod:`os` module has a new :func:`~os.pipe2` function that makes it " +"possible to create a pipe with :data:`~os.O_CLOEXEC` or :data:`~os." +"O_NONBLOCK` flags set atomically. This is especially useful to avoid race " +"conditions in multi-threaded programs." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1582 +msgid "" +"The :mod:`os` module has a new :func:`~os.sendfile` function which provides " +"an efficient \"zero-copy\" way for copying data from one file (or socket) " +"descriptor to another. The phrase \"zero-copy\" refers to the fact that all " +"of the copying of data between the two descriptors is done entirely by the " +"kernel, with no copying of data into userspace buffers. :func:`~os.sendfile` " +"can be used to efficiently copy data from a file on disk to a network " +"socket, e.g. for downloading a file." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1590 +msgid "" +"(Patch submitted by Ross Lagerwall and Giampaolo Rodolà in :issue:`10882`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1592 +msgid "" +"To avoid race conditions like symlink attacks and issues with temporary " +"files and directories, it is more reliable (and also faster) to manipulate " +"file descriptors instead of file names. Python 3.3 enhances existing " +"functions and introduces new functions to work on file descriptors (:issue:" +"`4761`, :issue:`10755` and :issue:`14626`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1598 +msgid "" +"The :mod:`os` module has a new :func:`~os.fwalk` function similar to :func:" +"`~os.walk` except that it also yields file descriptors referring to the " +"directories visited. This is especially useful to avoid symlink races." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1602 +msgid "" +"The following functions get new optional *dir_fd* (:ref:`paths relative to " +"directory descriptors `) and/or *follow_symlinks* (:ref:`not " +"following symlinks `): :func:`~os.access`, :func:`~os." +"chflags`, :func:`~os.chmod`, :func:`~os.chown`, :func:`~os.link`, :func:`~os." +"lstat`, :func:`~os.mkdir`, :func:`~os.mkfifo`, :func:`~os.mknod`, :func:`~os." +"open`, :func:`~os.readlink`, :func:`~os.remove`, :func:`~os.rename`, :func:" +"`~os.replace`, :func:`~os.rmdir`, :func:`~os.stat`, :func:`~os.symlink`, :" +"func:`~os.unlink`, :func:`~os.utime`. Platform support for using these " +"parameters can be checked via the sets :data:`os.supports_dir_fd` and :data:" +"`os.supports_follows_symlinks`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1613 +msgid "" +"The following functions now support a file descriptor for their path " +"argument: :func:`~os.chdir`, :func:`~os.chmod`, :func:`~os.chown`, :func:" +"`~os.execve`, :func:`~os.listdir`, :func:`~os.pathconf`, :func:`~os.path." +"exists`, :func:`~os.stat`, :func:`~os.statvfs`, :func:`~os.utime`. Platform " +"support for this can be checked via the :data:`os.supports_fd` set." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1619 +msgid "" +":func:`~os.access` accepts an ``effective_ids`` keyword argument to turn on " +"using the effective uid/gid rather than the real uid/gid in the access " +"check. Platform support for this can be checked via the :data:`~os." +"supports_effective_ids` set." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1624 +msgid "" +"The :mod:`os` module has two new functions: :func:`~os.getpriority` and :" +"func:`~os.setpriority`. They can be used to get or set process niceness/" +"priority in a fashion similar to :func:`os.nice` but extended to all " +"processes instead of just the current one." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1629 +msgid "(Patch submitted by Giampaolo Rodolà in :issue:`10784`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1631 +msgid "" +"The new :func:`os.replace` function allows cross-platform renaming of a file " +"with overwriting the destination. With :func:`os.rename`, an existing " +"destination file is overwritten under POSIX, but raises an error under " +"Windows. (Contributed by Antoine Pitrou in :issue:`8828`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1637 +msgid "" +"The stat family of functions (:func:`~os.stat`, :func:`~os.fstat`, and :func:" +"`~os.lstat`) now support reading a file's timestamps with nanosecond " +"precision. Symmetrically, :func:`~os.utime` can now write file timestamps " +"with nanosecond precision. (Contributed by Larry Hastings in :issue:" +"`14127`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1643 +msgid "" +"The new :func:`os.get_terminal_size` function queries the size of the " +"terminal attached to a file descriptor. See also :func:`shutil." +"get_terminal_size`. (Contributed by Zbigniew Jędrzejewski-Szmek in :issue:" +"`13609`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1650 +msgid "" +"New functions to support Linux extended attributes (:issue:`12720`): :func:" +"`~os.getxattr`, :func:`~os.listxattr`, :func:`~os.removexattr`, :func:`~os." +"setxattr`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1654 +msgid "" +"New interface to the scheduler. These functions control how a process is " +"allocated CPU time by the operating system. New functions: :func:`~os." +"sched_get_priority_max`, :func:`~os.sched_get_priority_min`, :func:`~os." +"sched_getaffinity`, :func:`~os.sched_getparam`, :func:`~os." +"sched_getscheduler`, :func:`~os.sched_rr_get_interval`, :func:`~os." +"sched_setaffinity`, :func:`~os.sched_setparam`, :func:`~os." +"sched_setscheduler`, :func:`~os.sched_yield`," +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1663 +msgid "New functions to control the file system:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1665 +msgid "" +":func:`~os.posix_fadvise`: Announces an intention to access data in a " +"specific pattern thus allowing the kernel to make optimizations." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1667 +msgid "" +":func:`~os.posix_fallocate`: Ensures that enough disk space is allocated for " +"a file." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1669 +msgid ":func:`~os.sync`: Force write of everything to disk." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1671 +msgid "Additional new posix functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1673 +msgid "" +":func:`~os.lockf`: Apply, test or remove a POSIX lock on an open file " +"descriptor." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1674 +msgid "" +":func:`~os.pread`: Read from a file descriptor at an offset, the file offset " +"remains unchanged." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1676 +msgid "" +":func:`~os.pwrite`: Write to a file descriptor from an offset, leaving the " +"file offset unchanged." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1678 +msgid "" +":func:`~os.readv`: Read from a file descriptor into a number of writable " +"buffers." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1679 +msgid "" +":func:`~os.truncate`: Truncate the file corresponding to *path*, so that it " +"is at most *length* bytes in size." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1681 +msgid "" +":func:`~os.waitid`: Wait for the completion of one or more child processes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1682 +msgid "" +":func:`~os.writev`: Write the contents of *buffers* to a file descriptor, " +"where *buffers* is an arbitrary sequence of buffers." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1684 +msgid "" +":func:`~os.getgrouplist` (:issue:`9344`): Return list of group ids that " +"specified user belongs to." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1687 +msgid "" +":func:`~os.times` and :func:`~os.uname`: Return type changed from a tuple to " +"a tuple-like object with named attributes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1690 +msgid "" +"Some platforms now support additional constants for the :func:`~os.lseek` " +"function, such as ``os.SEEK_HOLE`` and ``os.SEEK_DATA``." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1693 +msgid "" +"New constants :data:`~os.RTLD_LAZY`, :data:`~os.RTLD_NOW`, :data:`~os." +"RTLD_GLOBAL`, :data:`~os.RTLD_LOCAL`, :data:`~os.RTLD_NODELETE`, :data:`~os." +"RTLD_NOLOAD`, and :data:`~os.RTLD_DEEPBIND` are available on platforms that " +"support them. These are for use with the :func:`sys.setdlopenflags` " +"function, and supersede the similar constants defined in :mod:`ctypes` and :" +"mod:`DLFCN`. (Contributed by Victor Stinner in :issue:`13226`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1701 +msgid "" +":func:`os.symlink` now accepts (and ignores) the ``target_is_directory`` " +"keyword argument on non-Windows platforms, to ease cross-platform support." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1708 +msgid "" +"Tab-completion is now available not only for command names, but also their " +"arguments. For example, for the ``break`` command, function and file names " +"are completed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1712 +msgid "(Contributed by Georg Brandl in :issue:`14210`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1716 ../Doc/whatsnew/3.4.rst:1220 +#: ../Doc/whatsnew/3.5.rst:1567 ../Doc/whatsnew/3.6.rst:801 +msgid "pickle" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1718 +msgid "" +":class:`pickle.Pickler` objects now have an optional :attr:`~pickle.Pickler." +"dispatch_table` attribute allowing per-pickler reduction functions to be set." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1722 +msgid "(Contributed by Richard Oudkerk in :issue:`14166`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1728 +msgid "" +"The Tk GUI and the :func:`~pydoc.serve` function have been removed from the :" +"mod:`pydoc` module: ``pydoc -g`` and :func:`~pydoc.serve` have been " +"deprecated in Python 3.2." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1734 ../Doc/whatsnew/3.4.rst:1301 +#: ../Doc/whatsnew/3.5.rst:1584 ../Doc/whatsnew/3.6.rst:810 +msgid "re" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1736 +msgid "" +":class:`str` regular expressions now support ``\\u`` and ``\\U`` escapes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1738 +msgid "(Contributed by Serhiy Storchaka in :issue:`3665`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1742 +msgid "sched" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1744 +msgid "" +":meth:`~sched.scheduler.run` now accepts a *blocking* parameter which when " +"set to False makes the method execute the scheduled events due to expire " +"soonest (if any) and then return immediately. This is useful in case you " +"want to use the :class:`~sched.scheduler` in non-blocking applications. " +"(Contributed by Giampaolo Rodolà in :issue:`13449`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1750 +msgid "" +":class:`~sched.scheduler` class can now be safely used in multi-threaded " +"environments. (Contributed by Josiah Carlson and Giampaolo Rodolà in :issue:" +"`8684`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1754 +msgid "" +"*timefunc* and *delayfunct* parameters of :class:`~sched.scheduler` class " +"constructor are now optional and defaults to :func:`time.time` and :func:" +"`time.sleep` respectively. (Contributed by Chris Clark in :issue:`13245`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1759 +msgid "" +":meth:`~sched.scheduler.enter` and :meth:`~sched.scheduler.enterabs` " +"*argument* parameter is now optional. (Contributed by Chris Clark in :issue:" +"`13245`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1763 +msgid "" +":meth:`~sched.scheduler.enter` and :meth:`~sched.scheduler.enterabs` now " +"accept a *kwargs* parameter. (Contributed by Chris Clark in :issue:`13245`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1771 +msgid "" +"Solaris and derivative platforms have a new class :class:`select.devpoll` " +"for high performance asynchronous sockets via :file:`/dev/poll`. " +"(Contributed by Jesús Cea Avión in :issue:`6397`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1777 +msgid "shlex" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1779 +msgid "" +"The previously undocumented helper function ``quote`` from the :mod:`pipes` " +"modules has been moved to the :mod:`shlex` module and documented. :func:" +"`~shlex.quote` properly escapes all characters in a string that might be " +"otherwise given special meaning by the shell." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1788 +msgid "New functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1790 +msgid "" +":func:`~shutil.disk_usage`: provides total, used and free disk space " +"statistics. (Contributed by Giampaolo Rodolà in :issue:`12442`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1792 +msgid "" +":func:`~shutil.chown`: allows one to change user and/or group of the given " +"path also specifying the user/group names and not only their numeric ids. " +"(Contributed by Sandro Tosi in :issue:`12191`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1795 +msgid "" +":func:`shutil.get_terminal_size`: returns the size of the terminal window to " +"which the interpreter is attached. (Contributed by Zbigniew Jędrzejewski-" +"Szmek in :issue:`13609`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1799 +msgid "" +":func:`~shutil.copy2` and :func:`~shutil.copystat` now preserve file " +"timestamps with nanosecond precision on platforms that support it. They also " +"preserve file \"extended attributes\" on Linux. (Contributed by Larry " +"Hastings in :issue:`14127` and :issue:`15238`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1804 +msgid "" +"Several functions now take an optional ``symlinks`` argument: when that " +"parameter is true, symlinks aren't dereferenced and the operation instead " +"acts on the symlink itself (or creates one, if relevant). (Contributed by " +"Hynek Schlawack in :issue:`12715`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1809 +msgid "" +"When copying files to a different file system, :func:`~shutil.move` now " +"handles symlinks the way the posix ``mv`` command does, recreating the " +"symlink rather than copying the target file contents. (Contributed by " +"Jonathan Niehof in :issue:`9993`.) :func:`~shutil.move` now also returns " +"the ``dst`` argument as its result." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1815 +msgid "" +":func:`~shutil.rmtree` is now resistant to symlink attacks on platforms " +"which support the new ``dir_fd`` parameter in :func:`os.open` and :func:`os." +"unlink`. (Contributed by Martin von Löwis and Hynek Schlawack in :issue:" +"`4489`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1822 ../Doc/whatsnew/3.5.rst:1652 +msgid "signal" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1824 +msgid "The :mod:`signal` module has new functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1826 +msgid "" +":func:`~signal.pthread_sigmask`: fetch and/or change the signal mask of the " +"calling thread (Contributed by Jean-Paul Calderone in :issue:`8407`);" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1828 +msgid ":func:`~signal.pthread_kill`: send a signal to a thread;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1829 +msgid ":func:`~signal.sigpending`: examine pending functions;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1830 +msgid ":func:`~signal.sigwait`: wait a signal;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1831 +msgid "" +":func:`~signal.sigwaitinfo`: wait for a signal, returning detailed " +"information about it;" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1833 +msgid "" +":func:`~signal.sigtimedwait`: like :func:`~signal.sigwaitinfo` but with a " +"timeout." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1836 +msgid "" +"The signal handler writes the signal number as a single byte instead of a " +"nul byte into the wakeup file descriptor. So it is possible to wait more " +"than one signal and know which signals were raised." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1840 +msgid "" +":func:`signal.signal` and :func:`signal.siginterrupt` raise an OSError, " +"instead of a RuntimeError: OSError has an errno attribute." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1845 ../Doc/whatsnew/3.4.rst:1370 +#: ../Doc/whatsnew/3.5.rst:1664 +msgid "smtpd" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1847 +msgid "" +"The :mod:`smtpd` module now supports :rfc:`5321` (extended SMTP) and :rfc:" +"`1870` (size extension). Per the standard, these extensions are enabled if " +"and only if the client initiates the session with an ``EHLO`` command." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1851 +msgid "" +"(Initial ``ELHO`` support by Alberto Trevino. Size extension by Juhana " +"Jauhiainen. Substantial additional work on the patch contributed by Michele " +"Orrù and Dan Boswell. :issue:`8739`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1857 ../Doc/whatsnew/3.4.rst:1380 +#: ../Doc/whatsnew/3.5.rst:1698 +msgid "smtplib" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1859 +msgid "" +"The :class:`~smtplib.SMTP`, :class:`~smtplib.SMTP_SSL`, and :class:`~smtplib." +"LMTP` classes now accept a ``source_address`` keyword argument to specify " +"the ``(host, port)`` to use as the source address in the bind call when " +"creating the outgoing socket. (Contributed by Paulo Scardine in :issue:" +"`11281`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1865 +msgid "" +":class:`~smtplib.SMTP` now supports the context management protocol, " +"allowing an ``SMTP`` instance to be used in a ``with`` statement. " +"(Contributed by Giampaolo Rodolà in :issue:`11289`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1869 +msgid "" +"The :class:`~smtplib.SMTP_SSL` constructor and the :meth:`~smtplib.SMTP." +"starttls` method now accept an SSLContext parameter to control parameters of " +"the secure channel. (Contributed by Kasun Herath in :issue:`8809`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1877 +msgid "" +"The :class:`~socket.socket` class now exposes additional methods to process " +"ancillary data when supported by the underlying platform:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1880 +msgid ":func:`~socket.socket.sendmsg`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1881 +msgid ":func:`~socket.socket.recvmsg`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1882 +msgid ":func:`~socket.socket.recvmsg_into`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1884 +msgid "" +"(Contributed by David Watson in :issue:`6560`, based on an earlier patch by " +"Heiko Wundram)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1887 +msgid "" +"The :class:`~socket.socket` class now supports the PF_CAN protocol family " +"(https://en.wikipedia.org/wiki/Socketcan), on Linux (https://lwn.net/" +"Articles/253425)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1891 +msgid "" +"(Contributed by Matthias Fuchs, updated by Tiago Gonçalves in :issue:" +"`10141`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1893 +msgid "" +"The :class:`~socket.socket` class now supports the PF_RDS protocol family " +"(https://en.wikipedia.org/wiki/Reliable_Datagram_Sockets and https://oss." +"oracle.com/projects/rds/)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1897 +msgid "" +"The :class:`~socket.socket` class now supports the ``PF_SYSTEM`` protocol " +"family on OS X. (Contributed by Michael Goderbauer in :issue:`13777`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1900 +msgid "" +"New function :func:`~socket.sethostname` allows the hostname to be set on " +"unix systems if the calling process has sufficient privileges. (Contributed " +"by Ross Lagerwall in :issue:`10866`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1908 +msgid "" +":class:`~socketserver.BaseServer` now has an overridable method :meth:" +"`~socketserver.BaseServer.service_actions` that is called by the :meth:" +"`~socketserver.BaseServer.serve_forever` method in the service loop. :class:" +"`~socketserver.ForkingMixIn` now uses this to clean up zombie child " +"processes. (Contributed by Justin Warkentin in :issue:`11109`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1918 +msgid "" +"New :class:`sqlite3.Connection` method :meth:`~sqlite3.Connection." +"set_trace_callback` can be used to capture a trace of all sql commands " +"processed by sqlite. (Contributed by Torsten Landschoff in :issue:`11688`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1927 +msgid "The :mod:`ssl` module has two new random generation functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1929 +msgid "" +":func:`~ssl.RAND_bytes`: generate cryptographically strong pseudo-random " +"bytes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1931 +msgid ":func:`~ssl.RAND_pseudo_bytes`: generate pseudo-random bytes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1933 +msgid "(Contributed by Victor Stinner in :issue:`12049`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1935 +msgid "" +"The :mod:`ssl` module now exposes a finer-grained exception hierarchy in " +"order to make it easier to inspect the various kinds of errors. (Contributed " +"by Antoine Pitrou in :issue:`11183`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1939 +msgid "" +":meth:`~ssl.SSLContext.load_cert_chain` now accepts a *password* argument to " +"be used if the private key is encrypted. (Contributed by Adam Simpkins in :" +"issue:`12803`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1943 +msgid "" +"Diffie-Hellman key exchange, both regular and Elliptic Curve-based, is now " +"supported through the :meth:`~ssl.SSLContext.load_dh_params` and :meth:`~ssl." +"SSLContext.set_ecdh_curve` methods. (Contributed by Antoine Pitrou in :issue:" +"`13626` and :issue:`13627`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1948 +msgid "" +"SSL sockets have a new :meth:`~ssl.SSLSocket.get_channel_binding` method " +"allowing the implementation of certain authentication mechanisms such as " +"SCRAM-SHA-1-PLUS. (Contributed by Jacek Konieczny in :issue:`12551`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1952 +msgid "" +"You can query the SSL compression algorithm used by an SSL socket, thanks to " +"its new :meth:`~ssl.SSLSocket.compression` method. The new attribute :attr:" +"`~ssl.OP_NO_COMPRESSION` can be used to disable compression. (Contributed by " +"Antoine Pitrou in :issue:`13634`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1957 +msgid "" +"Support has been added for the Next Protocol Negotiation extension using " +"the :meth:`ssl.SSLContext.set_npn_protocols` method. (Contributed by Colin " +"Marc in :issue:`14204`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1961 +msgid "" +"SSL errors can now be introspected more easily thanks to :attr:`~ssl." +"SSLError.library` and :attr:`~ssl.SSLError.reason` attributes. (Contributed " +"by Antoine Pitrou in :issue:`14837`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1965 +msgid "" +"The :func:`~ssl.get_server_certificate` function now supports IPv6. " +"(Contributed by Charles-François Natali in :issue:`11811`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1968 +msgid "" +"New attribute :attr:`~ssl.OP_CIPHER_SERVER_PREFERENCE` allows setting SSLv3 " +"server sockets to use the server's cipher ordering preference rather than " +"the client's (:issue:`13635`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1974 ../Doc/whatsnew/3.4.rst:1496 +msgid "stat" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1976 +msgid "" +"The undocumented tarfile.filemode function has been moved to :func:`stat." +"filemode`. It can be used to convert a file's mode to a string of the form '-" +"rwxrwxrwx'." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1980 +msgid "(Contributed by Giampaolo Rodolà in :issue:`14807`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1984 ../Doc/whatsnew/3.4.rst:1508 +msgid "struct" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1986 +msgid "" +"The :mod:`struct` module now supports ``ssize_t`` and ``size_t`` via the new " +"codes ``n`` and ``N``, respectively. (Contributed by Antoine Pitrou in :" +"issue:`3163`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1992 ../Doc/whatsnew/3.4.rst:1517 +#: ../Doc/whatsnew/3.5.rst:1838 ../Doc/whatsnew/3.6.rst:924 +msgid "subprocess" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1994 +msgid "" +"Command strings can now be bytes objects on posix platforms. (Contributed " +"by Victor Stinner in :issue:`8513`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:1997 +msgid "" +"A new constant :data:`~subprocess.DEVNULL` allows suppressing output in a " +"platform-independent fashion. (Contributed by Ross Lagerwall in :issue:" +"`5870`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2003 ../Doc/whatsnew/3.4.rst:1549 +#: ../Doc/whatsnew/3.5.rst:1864 +msgid "sys" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2005 +msgid "" +"The :mod:`sys` module has a new :data:`~sys.thread_info` :term:`struct " +"sequence` holding informations about the thread implementation (:issue:" +"`11223`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2013 +msgid "" +":mod:`tarfile` now supports ``lzma`` encoding via the :mod:`lzma` module. " +"(Contributed by Lars Gustäbel in :issue:`5689`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2020 +msgid "" +":class:`tempfile.SpooledTemporaryFile`\\'s :meth:`~tempfile." +"SpooledTemporaryFile.truncate` method now accepts a ``size`` parameter. " +"(Contributed by Ryan Kelly in :issue:`9957`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2026 ../Doc/whatsnew/3.4.rst:1581 +msgid "textwrap" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2028 +msgid "" +"The :mod:`textwrap` module has a new :func:`~textwrap.indent` that makes it " +"straightforward to add a common prefix to selected lines in a block of text " +"(:issue:`13857`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2036 +msgid "" +":class:`threading.Condition`, :class:`threading.Semaphore`, :class:" +"`threading.BoundedSemaphore`, :class:`threading.Event`, and :class:" +"`threading.Timer`, all of which used to be factory functions returning a " +"class instance, are now classes and may be subclassed. (Contributed by Éric " +"Araujo in :issue:`10968`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2042 +msgid "" +"The :class:`threading.Thread` constructor now accepts a ``daemon`` keyword " +"argument to override the default behavior of inheriting the ``deamon`` flag " +"value from the parent thread (:issue:`6064`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2046 +msgid "" +"The formerly private function ``_thread.get_ident`` is now available as the " +"public function :func:`threading.get_ident`. This eliminates several cases " +"of direct access to the ``_thread`` module in the stdlib. Third party code " +"that used ``_thread.get_ident`` should likewise be changed to use the new " +"public interface." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2054 ../Doc/whatsnew/3.5.rst:1917 +msgid "time" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2056 +msgid "The :pep:`418` added new functions to the :mod:`time` module:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2058 +msgid ":func:`~time.get_clock_info`: Get information on a clock." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2059 +msgid "" +":func:`~time.monotonic`: Monotonic clock (cannot go backward), not affected " +"by system clock updates." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2061 +msgid "" +":func:`~time.perf_counter`: Performance counter with the highest available " +"resolution to measure a short duration." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2063 +msgid "" +":func:`~time.process_time`: Sum of the system and user CPU time of the " +"current process." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2066 +msgid "Other new functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2068 +msgid "" +":func:`~time.clock_getres`, :func:`~time.clock_gettime` and :func:`~time." +"clock_settime` functions with ``CLOCK_xxx`` constants. (Contributed by " +"Victor Stinner in :issue:`10278`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2072 +msgid "" +"To improve cross platform consistency, :func:`~time.sleep` now raises a :exc:" +"`ValueError` when passed a negative sleep value. Previously this was an " +"error on posix, but produced an infinite sleep on Windows." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2078 ../Doc/whatsnew/3.4.rst:1613 +#: ../Doc/whatsnew/3.5.rst:1963 +msgid "types" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2080 +msgid "" +"Add a new :class:`types.MappingProxyType` class: Read-only proxy of a " +"mapping. (:issue:`14386`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2084 +msgid "" +"The new functions :func:`types.new_class` and :func:`types.prepare_class` " +"provide support for PEP 3115 compliant dynamic type creation. (:issue:" +"`14588`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2091 +msgid "" +":meth:`.assertRaises`, :meth:`.assertRaisesRegex`, :meth:`.assertWarns`, " +"and :meth:`.assertWarnsRegex` now accept a keyword argument *msg* when used " +"as context managers. (Contributed by Ezio Melotti and Winston Ewert in :" +"issue:`10775`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2096 +msgid "" +":meth:`unittest.TestCase.run` now returns the :class:`~unittest.TestResult` " +"object." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2101 ../Doc/whatsnew/3.4.rst:1624 +#: ../Doc/whatsnew/3.5.rst:2027 +msgid "urllib" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2103 +msgid "" +"The :class:`~urllib.request.Request` class, now accepts a *method* argument " +"used by :meth:`~urllib.request.Request.get_method` to determine what HTTP " +"method should be used. For example, this will send a ``'HEAD'`` request::" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2109 +msgid "(:issue:`1673007`)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2113 +msgid "webbrowser" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2115 +msgid "" +"The :mod:`webbrowser` module supports more \"browsers\": Google Chrome " +"(named :program:`chrome`, :program:`chromium`, :program:`chrome-browser` or :" +"program:`chromium-browser` depending on the version and operating system), " +"and the generic launchers :program:`xdg-open`, from the FreeDesktop.org " +"project, and :program:`gvfs-open`, which is the default URI handler for " +"GNOME 3. (The former contributed by Arnaud Calmettes in :issue:`13620`, the " +"latter by Matthias Klose in :issue:`14493`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2125 +msgid "xml.etree.ElementTree" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2127 +msgid "" +"The :mod:`xml.etree.ElementTree` module now imports its C accelerator by " +"default; there is no longer a need to explicitly import :mod:`xml.etree." +"cElementTree` (this module stays for backwards compatibility, but is now " +"deprecated). In addition, the ``iter`` family of methods of :class:`~xml." +"etree.ElementTree.Element` has been optimized (rewritten in C). The module's " +"documentation has also been greatly improved with added examples and a more " +"detailed reference." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2137 ../Doc/whatsnew/3.6.rst:1099 +msgid "zlib" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2139 +msgid "" +"New attribute :attr:`zlib.Decompress.eof` makes it possible to distinguish " +"between a properly-formed compressed stream and an incomplete or truncated " +"one. (Contributed by Nadeem Vawda in :issue:`12646`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2143 +msgid "" +"New attribute :attr:`zlib.ZLIB_RUNTIME_VERSION` reports the version string " +"of the underlying ``zlib`` library that is loaded at runtime. (Contributed " +"by Torsten Landschoff in :issue:`12306`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2153 +msgid "" +"Thanks to :pep:`393`, some operations on Unicode strings have been optimized:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2155 +msgid "the memory footprint is divided by 2 to 4 depending on the text" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2156 +msgid "" +"encode an ASCII string to UTF-8 doesn't need to encode characters anymore, " +"the UTF-8 representation is shared with the ASCII representation" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2158 +msgid "the UTF-8 encoder has been optimized" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2159 +msgid "" +"repeating a single ASCII letter and getting a substring of an ASCII string " +"is 4 times faster" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2162 +msgid "UTF-8 is now 2x to 4x faster. UTF-16 encoding is now up to 10x faster." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2164 +msgid "" +"(Contributed by Serhiy Storchaka, :issue:`14624`, :issue:`14738` and :issue:" +"`15026`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2173 +msgid "New :pep:`3118` related function:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2175 +msgid ":c:func:`PyMemoryView_FromMemory`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2177 +msgid ":pep:`393` added new Unicode types, macros and functions:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2179 +msgid "High-level API:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2181 +msgid ":c:func:`PyUnicode_CopyCharacters`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2182 +msgid ":c:func:`PyUnicode_FindChar`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2183 +msgid ":c:func:`PyUnicode_GetLength`, :c:macro:`PyUnicode_GET_LENGTH`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2184 +msgid ":c:func:`PyUnicode_New`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2185 +msgid ":c:func:`PyUnicode_Substring`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2186 +msgid ":c:func:`PyUnicode_ReadChar`, :c:func:`PyUnicode_WriteChar`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2188 +msgid "Low-level API:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2190 +msgid ":c:type:`Py_UCS1`, :c:type:`Py_UCS2`, :c:type:`Py_UCS4` types" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2191 +msgid ":c:type:`PyASCIIObject` and :c:type:`PyCompactUnicodeObject` structures" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2192 +msgid ":c:macro:`PyUnicode_READY`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2193 +msgid ":c:func:`PyUnicode_FromKindAndData`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2194 +msgid ":c:func:`PyUnicode_AsUCS4`, :c:func:`PyUnicode_AsUCS4Copy`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2195 +msgid "" +":c:macro:`PyUnicode_DATA`, :c:macro:`PyUnicode_1BYTE_DATA`, :c:macro:" +"`PyUnicode_2BYTE_DATA`, :c:macro:`PyUnicode_4BYTE_DATA`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2197 +msgid "" +":c:macro:`PyUnicode_KIND` with :c:type:`PyUnicode_Kind` enum: :c:data:" +"`PyUnicode_WCHAR_KIND`, :c:data:`PyUnicode_1BYTE_KIND`, :c:data:" +"`PyUnicode_2BYTE_KIND`, :c:data:`PyUnicode_4BYTE_KIND`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2200 +msgid "" +":c:macro:`PyUnicode_READ`, :c:macro:`PyUnicode_READ_CHAR`, :c:macro:" +"`PyUnicode_WRITE`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2201 +msgid ":c:macro:`PyUnicode_MAX_CHAR_VALUE`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2203 +msgid "" +":c:macro:`PyArg_ParseTuple` now accepts a :class:`bytearray` for the ``c`` " +"format (:issue:`12380`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2209 ../Doc/whatsnew/3.4.rst:2067 +#: ../Doc/whatsnew/3.5.rst:2262 ../Doc/whatsnew/3.6.rst:1196 +msgid "Deprecated" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2212 ../Doc/whatsnew/3.5.rst:2283 +msgid "Unsupported Operating Systems" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2214 +msgid "OS/2 and VMS are no longer supported due to the lack of a maintainer." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2216 +msgid "" +"Windows 2000 and Windows platforms which set ``COMSPEC`` to ``command.com`` " +"are no longer supported due to maintenance burden." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2219 +msgid "OSF support, which was deprecated in 3.2, has been completely removed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2223 ../Doc/whatsnew/3.5.rst:2290 +#: ../Doc/whatsnew/3.6.rst:1217 +msgid "Deprecated Python modules, functions and methods" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2225 +msgid "" +"Passing a non-empty string to ``object.__format__()`` is deprecated, and " +"will produce a :exc:`TypeError` in Python 3.4 (:issue:`9856`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2227 +msgid "" +"The ``unicode_internal`` codec has been deprecated because of the :pep:" +"`393`, use UTF-8, UTF-16 (``utf-16-le`` or ``utf-16-be``), or UTF-32 " +"(``utf-32-le`` or ``utf-32-be``)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2230 +msgid "" +":meth:`ftplib.FTP.nlst` and :meth:`ftplib.FTP.dir`: use :meth:`ftplib.FTP." +"mlsd`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2232 +msgid "" +":func:`platform.popen`: use the :mod:`subprocess` module. Check especially " +"the :ref:`subprocess-replacements` section (:issue:`11377`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2234 +msgid "" +":issue:`13374`: The Windows bytes API has been deprecated in the :mod:`os` " +"module. Use Unicode filenames, instead of bytes filenames, to not depend on " +"the ANSI code page anymore and to support any filename." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2237 +msgid "" +":issue:`13988`: The :mod:`xml.etree.cElementTree` module is deprecated. The " +"accelerator is used automatically whenever available." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2239 +msgid "" +"The behaviour of :func:`time.clock` depends on the platform: use the new :" +"func:`time.perf_counter` or :func:`time.process_time` function instead, " +"depending on your requirements, to have a well defined behaviour." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2242 +msgid "The :func:`os.stat_float_times` function is deprecated." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2243 +msgid ":mod:`abc` module:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2252 +msgid ":mod:`importlib` package:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2254 +msgid "" +":meth:`importlib.abc.SourceLoader.path_mtime` is now deprecated in favour " +"of :meth:`importlib.abc.SourceLoader.path_stats` as bytecode files now store " +"both the modification time and size of the source file the bytecode file was " +"compiled from." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2264 ../Doc/whatsnew/3.6.rst:1231 +msgid "Deprecated functions and types of the C API" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2266 +msgid "" +"The :c:type:`Py_UNICODE` has been deprecated by :pep:`393` and will be " +"removed in Python 4. All functions using this type are deprecated:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2269 +msgid "" +"Unicode functions and methods using :c:type:`Py_UNICODE` and :c:type:" +"`Py_UNICODE*` types:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2272 +msgid "" +":c:macro:`PyUnicode_FromUnicode`: use :c:func:`PyUnicode_FromWideChar` or :c:" +"func:`PyUnicode_FromKindAndData`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2274 +msgid "" +":c:macro:`PyUnicode_AS_UNICODE`, :c:func:`PyUnicode_AsUnicode`, :c:func:" +"`PyUnicode_AsUnicodeAndSize`: use :c:func:`PyUnicode_AsWideCharString`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2276 +msgid "" +":c:macro:`PyUnicode_AS_DATA`: use :c:macro:`PyUnicode_DATA` with :c:macro:" +"`PyUnicode_READ` and :c:macro:`PyUnicode_WRITE`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2278 +msgid "" +":c:macro:`PyUnicode_GET_SIZE`, :c:func:`PyUnicode_GetSize`: use :c:macro:" +"`PyUnicode_GET_LENGTH` or :c:func:`PyUnicode_GetLength`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2280 +msgid "" +":c:macro:`PyUnicode_GET_DATA_SIZE`: use ``PyUnicode_GET_LENGTH(str) * " +"PyUnicode_KIND(str)`` (only work on ready strings)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2283 +msgid "" +":c:func:`PyUnicode_AsUnicodeCopy`: use :c:func:`PyUnicode_AsUCS4Copy` or :c:" +"func:`PyUnicode_AsWideCharString`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2285 +msgid ":c:func:`PyUnicode_GetMax`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2288 +msgid "Functions and macros manipulating Py_UNICODE* strings:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2290 +msgid "" +":c:macro:`Py_UNICODE_strlen`: use :c:func:`PyUnicode_GetLength` or :c:macro:" +"`PyUnicode_GET_LENGTH`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2292 +msgid "" +":c:macro:`Py_UNICODE_strcat`: use :c:func:`PyUnicode_CopyCharacters` or :c:" +"func:`PyUnicode_FromFormat`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2294 +msgid "" +":c:macro:`Py_UNICODE_strcpy`, :c:macro:`Py_UNICODE_strncpy`, :c:macro:" +"`Py_UNICODE_COPY`: use :c:func:`PyUnicode_CopyCharacters` or :c:func:" +"`PyUnicode_Substring`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2297 +msgid ":c:macro:`Py_UNICODE_strcmp`: use :c:func:`PyUnicode_Compare`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2298 +msgid ":c:macro:`Py_UNICODE_strncmp`: use :c:func:`PyUnicode_Tailmatch`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2299 +msgid "" +":c:macro:`Py_UNICODE_strchr`, :c:macro:`Py_UNICODE_strrchr`: use :c:func:" +"`PyUnicode_FindChar`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2301 +msgid ":c:macro:`Py_UNICODE_FILL`: use :c:func:`PyUnicode_Fill`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2302 +msgid ":c:macro:`Py_UNICODE_MATCH`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2304 +msgid "Encoders:" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2306 +msgid ":c:func:`PyUnicode_Encode`: use :c:func:`PyUnicode_AsEncodedObject`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2307 +msgid ":c:func:`PyUnicode_EncodeUTF7`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2308 +msgid "" +":c:func:`PyUnicode_EncodeUTF8`: use :c:func:`PyUnicode_AsUTF8` or :c:func:" +"`PyUnicode_AsUTF8String`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2310 +msgid ":c:func:`PyUnicode_EncodeUTF32`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2311 +msgid ":c:func:`PyUnicode_EncodeUTF16`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2312 +msgid "" +":c:func:`PyUnicode_EncodeUnicodeEscape:` use :c:func:" +"`PyUnicode_AsUnicodeEscapeString`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2314 +msgid "" +":c:func:`PyUnicode_EncodeRawUnicodeEscape:` use :c:func:" +"`PyUnicode_AsRawUnicodeEscapeString`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2316 +msgid "" +":c:func:`PyUnicode_EncodeLatin1`: use :c:func:`PyUnicode_AsLatin1String`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2317 +msgid ":c:func:`PyUnicode_EncodeASCII`: use :c:func:`PyUnicode_AsASCIIString`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2318 +msgid ":c:func:`PyUnicode_EncodeCharmap`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2319 +msgid ":c:func:`PyUnicode_TranslateCharmap`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2320 +msgid "" +":c:func:`PyUnicode_EncodeMBCS`: use :c:func:`PyUnicode_AsMBCSString` or :c:" +"func:`PyUnicode_EncodeCodePage` (with ``CP_ACP`` code_page)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2322 +msgid "" +":c:func:`PyUnicode_EncodeDecimal`, :c:func:" +"`PyUnicode_TransformDecimalToASCII`" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2327 ../Doc/whatsnew/3.6.rst:1237 +msgid "Deprecated features" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2329 +msgid "" +"The :mod:`array` module's ``'u'`` format code is now deprecated and will be " +"removed in Python 4 together with the rest of the (:c:type:`Py_UNICODE`) API." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2334 +msgid "Porting to Python 3.3" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2336 ../Doc/whatsnew/3.4.rst:2242 +#: ../Doc/whatsnew/3.5.rst:2377 ../Doc/whatsnew/3.6.rst:1336 +msgid "" +"This section lists previously described changes and other bugfixes that may " +"require changes to your code." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2342 +msgid "Porting Python code" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2344 +msgid "" +"Hash randomization is enabled by default. Set the :envvar:`PYTHONHASHSEED` " +"environment variable to ``0`` to disable hash randomization. See also the :" +"meth:`object.__hash__` method." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2348 +msgid "" +":issue:`12326`: On Linux, sys.platform doesn't contain the major version " +"anymore. It is now always 'linux', instead of 'linux2' or 'linux3' depending " +"on the Linux version used to build Python. Replace sys.platform == 'linux2' " +"with sys.platform.startswith('linux'), or directly sys.platform == 'linux' " +"if you don't need to support older Python versions." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2354 +msgid "" +":issue:`13847`, :issue:`14180`: :mod:`time` and :mod:`datetime`: :exc:" +"`OverflowError` is now raised instead of :exc:`ValueError` if a timestamp is " +"out of range. :exc:`OSError` is now raised if C functions :c:func:`gmtime` " +"or :c:func:`localtime` failed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2359 +msgid "" +"The default finders used by import now utilize a cache of what is contained " +"within a specific directory. If you create a Python source file or " +"sourceless bytecode file, make sure to call :func:`importlib." +"invalidate_caches` to clear out the cache for the finders to notice the new " +"file." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2364 +msgid "" +":exc:`ImportError` now uses the full name of the module that was attempted " +"to be imported. Doctests that check ImportErrors' message will need to be " +"updated to use the full name of the module instead of just the tail of the " +"name." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2369 +msgid "" +"The *index* argument to :func:`__import__` now defaults to 0 instead of -1 " +"and no longer support negative values. It was an oversight when :pep:`328` " +"was implemented that the default value remained -1. If you need to continue " +"to perform a relative import followed by an absolute import, then perform " +"the relative import using an index of 1, followed by another import using an " +"index of 0. It is preferred, though, that you use :func:`importlib." +"import_module` rather than call :func:`__import__` directly." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2377 +msgid "" +":func:`__import__` no longer allows one to use an index value other than 0 " +"for top-level modules. E.g. ``__import__('sys', level=1)`` is now an error." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2380 +msgid "" +"Because :attr:`sys.meta_path` and :attr:`sys.path_hooks` now have finders on " +"them by default, you will most likely want to use :meth:`list.insert` " +"instead of :meth:`list.append` to add to those lists." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2384 +msgid "" +"Because ``None`` is now inserted into :attr:`sys.path_importer_cache`, if " +"you are clearing out entries in the dictionary of paths that do not have a " +"finder, you will need to remove keys paired with values of ``None`` **and** :" +"class:`imp.NullImporter` to be backwards-compatible. This will lead to extra " +"overhead on older versions of Python that re-insert ``None`` into :attr:`sys." +"path_importer_cache` where it repesents the use of implicit finders, but " +"semantically it should not change anything." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2392 +msgid "" +":class:`importlib.abc.Finder` no longer specifies a `find_module()` abstract " +"method that must be implemented. If you were relying on subclasses to " +"implement that method, make sure to check for the method's existence first. " +"You will probably want to check for `find_loader()` first, though, in the " +"case of working with :term:`path entry finders `." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2398 +msgid "" +":mod:`pkgutil` has been converted to use :mod:`importlib` internally. This " +"eliminates many edge cases where the old behaviour of the PEP 302 import " +"emulation failed to match the behaviour of the real import system. The " +"import emulation itself is still present, but is now deprecated. The :func:" +"`pkgutil.iter_importers` and :func:`pkgutil.walk_packages` functions special " +"case the standard import hooks so they are still supported even though they " +"do not provide the non-standard ``iter_modules()`` method." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2406 +msgid "" +"A longstanding RFC-compliance bug (:issue:`1079`) in the parsing done by :" +"func:`email.header.decode_header` has been fixed. Code that uses the " +"standard idiom to convert encoded headers into unicode " +"(``str(make_header(decode_header(h))``) will see no change, but code that " +"looks at the individual tuples returned by decode_header will see that " +"whitespace that precedes or follows ``ASCII`` sections is now included in " +"the ``ASCII`` section. Code that builds headers using ``make_header`` " +"should also continue to work without change, since ``make_header`` continues " +"to add whitespace between ``ASCII`` and non-``ASCII`` sections if it is not " +"already present in the input strings." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2417 +msgid "" +":func:`email.utils.formataddr` now does the correct content transfer " +"encoding when passed non-``ASCII`` display names. Any code that depended on " +"the previous buggy behavior that preserved the non-``ASCII`` unicode in the " +"formatted output string will need to be changed (:issue:`1690608`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2422 +msgid "" +":meth:`poplib.POP3.quit` may now raise protocol errors like all other " +"``poplib`` methods. Code that assumes ``quit`` does not raise :exc:`poplib." +"error_proto` errors may need to be changed if errors on ``quit`` are " +"encountered by a particular application (:issue:`11291`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2427 +msgid "" +"The ``strict`` argument to :class:`email.parser.Parser`, deprecated since " +"Python 2.4, has finally been removed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2430 +msgid "" +"The deprecated method ``unittest.TestCase.assertSameElements`` has been " +"removed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2433 +msgid "The deprecated variable ``time.accept2dyear`` has been removed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2435 +msgid "" +"The deprecated ``Context._clamp`` attribute has been removed from the :mod:" +"`decimal` module. It was previously replaced by the public attribute :attr:" +"`~decimal.Context.clamp`. (See :issue:`8540`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2439 +msgid "" +"The undocumented internal helper class ``SSLFakeFile`` has been removed " +"from :mod:`smtplib`, since its functionality has long been provided directly " +"by :meth:`socket.socket.makefile`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2443 +msgid "" +"Passing a negative value to :func:`time.sleep` on Windows now raises an " +"error instead of sleeping forever. It has always raised an error on posix." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2446 +msgid "" +"The ``ast.__version__`` constant has been removed. If you need to make " +"decisions affected by the AST version, use :attr:`sys.version_info` to make " +"the decision." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2450 +msgid "" +"Code that used to work around the fact that the :mod:`threading` module used " +"factory functions by subclassing the private classes will need to change to " +"subclass the now-public classes." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2454 +msgid "" +"The undocumented debugging machinery in the threading module has been " +"removed, simplifying the code. This should have no effect on production " +"code, but is mentioned here in case any application debug frameworks were " +"interacting with it (:issue:`13550`)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2461 +msgid "Porting C code" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2463 +msgid "" +"In the course of changes to the buffer API the undocumented :c:member:" +"`~Py_buffer.smalltable` member of the :c:type:`Py_buffer` structure has been " +"removed and the layout of the :c:type:`PyMemoryViewObject` has changed." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2468 +msgid "" +"All extensions relying on the relevant parts in ``memoryobject.h`` or " +"``object.h`` must be rebuilt." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2471 +msgid "" +"Due to :ref:`PEP 393 `, the :c:type:`Py_UNICODE` type and all " +"functions using this type are deprecated (but will stay available for at " +"least five years). If you were using low-level Unicode APIs to construct " +"and access unicode objects and you want to benefit of the memory footprint " +"reduction provided by PEP 393, you have to convert your code to the new :doc:" +"`Unicode API <../c-api/unicode>`." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2478 +msgid "" +"However, if you only have been using high-level functions such as :c:func:" +"`PyUnicode_Concat()`, :c:func:`PyUnicode_Join` or :c:func:" +"`PyUnicode_FromFormat()`, your code will automatically take advantage of the " +"new unicode representations." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2483 +msgid ":c:func:`PyImport_GetMagicNumber` now returns -1 upon failure." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2485 +msgid "" +"As a negative value for the *level* argument to :func:`__import__` is no " +"longer valid, the same now holds for :c:func:`PyImport_ImportModuleLevel`. " +"This also means that the value of *level* used by :c:func:" +"`PyImport_ImportModuleEx` is now 0 instead of -1." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2492 +msgid "Building C extensions" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2494 +msgid "" +"The range of possible file names for C extensions has been narrowed. Very " +"rarely used spellings have been suppressed: under POSIX, files named " +"``xxxmodule.so``, ``xxxmodule.abi3.so`` and ``xxxmodule.cpython-*.so`` are " +"no longer recognized as implementing the ``xxx`` module. If you had been " +"generating such files, you have to switch to the other spellings (i.e., " +"remove the ``module`` string from the file names)." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2502 +msgid "(implemented in :issue:`14040`.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2506 +msgid "Command Line Switch Changes" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2508 +msgid "" +"The -Q command-line flag and related artifacts have been removed. Code " +"checking sys.flags.division_warning will need updating." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2511 +msgid "(:issue:`10998`, contributed by Éric Araujo.)" +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2513 +msgid "" +"When :program:`python` is started with :option:`-S`, ``import site`` will no " +"longer add site-specific paths to the module search paths. In previous " +"versions, it did." +msgstr "" + +#: ../Doc/whatsnew/3.3.rst:2517 +msgid "" +"(:issue:`11591`, contributed by Carl Meyer with editions by Éric Araujo.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:3 +msgid "What's New In Python 3.4" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:5 +msgid "R. David Murray (Editor)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:63 +msgid "" +"This article explains the new features in Python 3.4, compared to 3.3. " +"Python 3.4 was released on March 16, 2014. For full details, see the " +"`changelog `_." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:70 +msgid ":pep:`429` -- Python 3.4 Release Schedule" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:75 +msgid "Summary -- Release Highlights" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:82 +msgid "No new syntax features were added in Python 3.4." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:84 +msgid "Other new features:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:86 +msgid ":ref:`pip should always be available ` (:pep:`453`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:87 +msgid "" +":ref:`Newly created file descriptors are non-inheritable ` " +"(:pep:`446`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:89 +msgid "" +"command line option for :ref:`isolated mode ` (:" +"issue:`16499`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:91 +msgid "" +":ref:`improvements in the handling of codecs ` " +"that are not text encodings (multiple issues)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:93 +msgid "" +":ref:`A ModuleSpec Type ` for the Import System (:pep:" +"`451`). (Affects importer authors.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:95 +msgid "" +"The :mod:`marshal` format has been made :ref:`more compact and efficient " +"` (:issue:`16475`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:100 +msgid "" +":mod:`asyncio`: :ref:`New provisional API for asynchronous IO ` (:pep:`3156`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:102 +msgid "" +":mod:`ensurepip`: :ref:`Bootstrapping the pip installer ` (:pep:`453`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:104 +msgid "" +":mod:`enum`: :ref:`Support for enumeration types ` (:pep:" +"`435`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:106 +msgid "" +":mod:`pathlib`: :ref:`Object-oriented filesystem paths ` (:" +"pep:`428`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:108 +msgid "" +":mod:`selectors`: :ref:`High-level and efficient I/O multiplexing `, built upon the :mod:`select` module primitives (part of :pep:" +"`3156`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:111 +msgid "" +":mod:`statistics`: A basic :ref:`numerically stable statistics library " +"` (:pep:`450`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:113 +msgid "" +":mod:`tracemalloc`: :ref:`Trace Python memory allocations ` (:pep:`454`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:116 +msgid "Significantly improved library modules:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:118 +msgid "" +":ref:`Single-dispatch generic functions ` in :mod:" +"`functools` (:pep:`443`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:120 +msgid "" +"New :mod:`pickle` :ref:`protocol 4 ` (:pep:`3154`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:121 +msgid "" +":mod:`multiprocessing` now has :ref:`an option to avoid using os.fork on " +"Unix ` (:issue:`8713`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:123 +msgid "" +":mod:`email` has a new submodule, :mod:`~email.contentmanager`, and a new :" +"mod:`~email.message.Message` subclass (:class:`~email.contentmanager." +"EmailMessage`) that :ref:`simplify MIME handling " +"` (:issue:`18891`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:127 +msgid "" +"The :mod:`inspect` and :mod:`pydoc` modules are now capable of correct " +"introspection of a much wider variety of callable objects, which improves " +"the output of the Python :func:`help` system." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:130 +msgid "The :mod:`ipaddress` module API has been declared stable" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:134 +msgid "" +":ref:`Secure and interchangeable hash algorithm ` (:pep:" +"`456`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:136 +msgid "" +":ref:`Make newly created file descriptors non-inheritable ` (:pep:`446`) to avoid leaking file descriptors to child processes." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:138 +msgid "" +"New command line option for :ref:`isolated mode `, (:" +"issue:`16499`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:140 +msgid "" +":mod:`multiprocessing` now has :ref:`an option to avoid using os.fork on " +"Unix `. *spawn* and *forkserver* are more " +"secure because they avoid sharing data with child processes." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:143 +msgid "" +":mod:`multiprocessing` child processes on Windows no longer inherit all of " +"the parent's inheritable handles, only the necessary ones." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:145 +msgid "" +"A new :func:`hashlib.pbkdf2_hmac` function provides the `PKCS#5 password-" +"based key derivation function 2 `_." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:148 +msgid ":ref:`TLSv1.1 and TLSv1.2 support ` for :mod:`ssl`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:149 +msgid "" +":ref:`Retrieving certificates from the Windows system cert store support " +"` for :mod:`ssl`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:151 +msgid "" +":ref:`Server-side SNI (Server Name Indication) support ` " +"for :mod:`ssl`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:153 +msgid "" +"The :class:`ssl.SSLContext` class has a :ref:`lot of improvements " +"`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:155 +msgid "" +"All modules in the standard library that support SSL now support server " +"certificate verification, including hostname matching (:func:`ssl." +"match_hostname`) and CRLs (Certificate Revocation lists, see :func:`ssl." +"SSLContext.load_verify_locations`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:160 ../Doc/whatsnew/3.5.rst:94 +msgid "CPython implementation improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:162 +msgid ":ref:`Safe object finalization ` (:pep:`442`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:163 +msgid "" +"Leveraging :pep:`442`, in most cases :ref:`module globals are no longer set " +"to None during finalization ` (:issue:`18214`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:165 +msgid ":ref:`Configurable memory allocators ` (:pep:`445`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:166 +msgid ":ref:`Argument Clinic ` (:pep:`436`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:168 ../Doc/whatsnew/3.5.rst:157 +msgid "" +"Please read on for a comprehensive list of user-facing changes, including " +"many other smaller improvements, CPython optimizations, deprecations, and " +"potential porting issues." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:175 ../Doc/whatsnew/3.5.rst:163 +#: ../Doc/whatsnew/3.6.rst:161 +msgid "New Features" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:180 +msgid "PEP 453: Explicit Bootstrapping of PIP in Python Installations" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:183 +msgid "Bootstrapping pip By Default" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:185 +msgid "" +"The new :mod:`ensurepip` module (defined in :pep:`453`) provides a standard " +"cross-platform mechanism to bootstrap the pip installer into Python " +"installations and virtual environments. The version of ``pip`` included with " +"Python 3.4.0 is ``pip`` 1.5.4, and future 3.4.x maintenance releases will " +"update the bundled version to the latest version of ``pip`` that is " +"available at the time of creating the release candidate." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:192 +msgid "" +"By default, the commands ``pipX`` and ``pipX.Y`` will be installed on all " +"platforms (where X.Y stands for the version of the Python installation), " +"along with the ``pip`` Python package and its dependencies. On Windows and " +"in virtual environments on all platforms, the unversioned ``pip`` command " +"will also be installed. On other platforms, the system wide unversioned " +"``pip`` command typically refers to the separately installed Python 2 " +"version." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:200 +msgid "" +"The ``pyvenv`` command line utility and the :mod:`venv` module make use of " +"the :mod:`ensurepip` module to make ``pip`` readily available in virtual " +"environments. When using the command line utility, ``pip`` is installed by " +"default, while when using the :mod:`venv` module :ref:`venv-api` " +"installation of ``pip`` must be requested explicitly." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:206 +msgid "" +"For CPython :ref:`source builds on POSIX systems `, " +"the ``make install`` and ``make altinstall`` commands bootstrap ``pip`` by " +"default. This behaviour can be controlled through configure options, and " +"overridden through Makefile options." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:211 +msgid "" +"On Windows and Mac OS X, the CPython installers now default to installing " +"``pip`` along with CPython itself (users may opt out of installing it during " +"the installation process). Window users will need to opt in to the automatic " +"``PATH`` modifications to have ``pip`` available from the command line by " +"default, otherwise it can still be accessed through the Python launcher for " +"Windows as ``py -m pip``." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:218 +msgid "" +"As `discussed in the PEP`__, platform packagers may choose not to install " +"these commands by default, as long as, when invoked, they provide clear and " +"simple directions on how to install them on that platform (usually using the " +"system package manager)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:227 +msgid "" +"To avoid conflicts between parallel Python 2 and Python 3 installations, " +"only the versioned ``pip3`` and ``pip3.4`` commands are bootstrapped by " +"default when ``ensurepip`` is invoked directly - the ``--default-pip`` " +"option is needed to also request the unversioned ``pip`` command. ``pyvenv`` " +"and the Windows installer ensure that the unqualified ``pip`` command is " +"made available in those environments, and ``pip`` can always be invoked via " +"the ``-m`` switch rather than directly to avoid ambiguity on systems with " +"multiple Python installations." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:238 +msgid "Documentation Changes" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:240 +msgid "" +"As part of this change, the :ref:`installing-index` and :ref:`distributing-" +"index` sections of the documentation have been completely redesigned as " +"short getting started and FAQ documents. Most packaging documentation has " +"now been moved out to the Python Packaging Authority maintained `Python " +"Packaging User Guide `__ and the documentation " +"of the individual projects." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:248 +msgid "" +"However, as this migration is currently still incomplete, the legacy " +"versions of those guides remaining available as :ref:`install-index` and :" +"ref:`distutils-index`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:255 +msgid ":pep:`453` -- Explicit bootstrapping of pip in Python installations" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:255 +msgid "" +"PEP written by Donald Stufft and Nick Coghlan, implemented by Donald Stufft, " +"Nick Coghlan, Martin von Löwis and Ned Deily." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:262 +msgid "PEP 446: Newly Created File Descriptors Are Non-Inheritable" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:264 +msgid "" +":pep:`446` makes newly created file descriptors :ref:`non-inheritable " +"`. In general, this is the behavior an application will " +"want: when launching a new process, having currently open files also open in " +"the new process can lead to all sorts of hard to find bugs, and potentially " +"to security issues." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:270 +msgid "" +"However, there are occasions when inheritance is desired. To support these " +"cases, the following new functions and methods are available:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:273 +msgid ":func:`os.get_inheritable`, :func:`os.set_inheritable`" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:274 +msgid ":func:`os.get_handle_inheritable`, :func:`os.set_handle_inheritable`" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:275 +msgid "" +":meth:`socket.socket.get_inheritable`, :meth:`socket.socket.set_inheritable`" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:279 +msgid ":pep:`446` -- Make newly created file descriptors non-inheritable" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:280 ../Doc/whatsnew/3.4.rst:1812 +msgid "PEP written and implemented by Victor Stinner." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:286 +msgid "Improvements to Codec Handling" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:288 +msgid "" +"Since it was first introduced, the :mod:`codecs` module has always been " +"intended to operate as a type-neutral dynamic encoding and decoding system. " +"However, its close coupling with the Python text model, especially the type " +"restricted convenience methods on the builtin :class:`str`, :class:`bytes` " +"and :class:`bytearray` types, has historically obscured that fact." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:295 +msgid "" +"As a key step in clarifying the situation, the :meth:`codecs.encode` and :" +"meth:`codecs.decode` convenience functions are now properly documented in " +"Python 2.7, 3.3 and 3.4. These functions have existed in the :mod:`codecs` " +"module (and have been covered by the regression test suite) since Python " +"2.4, but were previously only discoverable through runtime introspection." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:301 +msgid "" +"Unlike the convenience methods on :class:`str`, :class:`bytes` and :class:" +"`bytearray`, the :mod:`codecs` convenience functions support arbitrary " +"codecs in both Python 2 and Python 3, rather than being limited to Unicode " +"text encodings (in Python 3) or ``basestring`` <-> ``basestring`` " +"conversions (in Python 2)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:307 +msgid "" +"In Python 3.4, the interpreter is able to identify the known non-text " +"encodings provided in the standard library and direct users towards these " +"general purpose convenience functions when appropriate::" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:326 +msgid "" +"In a related change, whenever it is feasible without breaking backwards " +"compatibility, exceptions raised during encoding and decoding operations are " +"wrapped in a chained exception of the same type that mentions the name of " +"the codec responsible for producing the error::" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:359 +msgid "" +"Finally, as the examples above show, these improvements have permitted the " +"restoration of the convenience aliases for the non-Unicode codecs that were " +"themselves restored in Python 3.2. This means that encoding binary data to " +"and from its hexadecimal representation (for example) can now be written as::" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:371 +msgid "" +"The binary and text transforms provided in the standard library are detailed " +"in :ref:`binary-transforms` and :ref:`text-transforms`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:374 +msgid "" +"(Contributed by Nick Coghlan in :issue:`7475`, :issue:`17827`, :issue:" +"`17828` and :issue:`19619`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:381 +msgid "PEP 451: A ModuleSpec Type for the Import System" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:383 +msgid "" +":pep:`451` provides an encapsulation of the information about a module that " +"the import machinery will use to load it (that is, a module specification). " +"This helps simplify both the import implementation and several import-" +"related APIs. The change is also a stepping stone for `several future import-" +"related improvements`__." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:391 +msgid "" +"The public-facing changes from the PEP are entirely backward-compatible. " +"Furthermore, they should be transparent to everyone but importer authors. " +"Key finder and loader methods have been deprecated, but they will continue " +"working. New importers should use the new methods described in the PEP. " +"Existing importers should be updated to implement the new methods. See the :" +"ref:`deprecated-3.4` section for a list of methods that should be replaced " +"and their replacements." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:405 +msgid "Unicode database updated to UCD version 6.3." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:407 +msgid "" +":func:`min` and :func:`max` now accept a *default* keyword-only argument " +"that can be used to specify the value they return if the iterable they are " +"evaluating has no elements. (Contributed by Julian Berman in :issue:" +"`18111`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:412 +msgid "Module objects are now :mod:`weakref`'able." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:414 +msgid "" +"Module ``__file__`` attributes (and related values) should now always " +"contain absolute paths by default, with the sole exception of ``__main__." +"__file__`` when a script has been executed directly using a relative path. " +"(Contributed by Brett Cannon in :issue:`18416`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:419 +msgid "" +"All the UTF-\\* codecs (except UTF-7) now reject surrogates during both " +"encoding and decoding unless the ``surrogatepass`` error handler is used, " +"with the exception of the UTF-16 decoder (which accepts valid surrogate " +"pairs) and the UTF-16 encoder (which produces them while encoding non-BMP " +"characters). (Contributed by Victor Stinner, Kang-Hao (Kenny) Lu and Serhiy " +"Storchaka in :issue:`12892`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:426 +msgid "" +"New German EBCDIC :ref:`codec ` ``cp273``. (Contributed " +"by Michael Bierenfeld and Andrew Kuchling in :issue:`1097797`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:429 +msgid "" +"New Ukrainian :ref:`codec ` ``cp1125``. (Contributed by " +"Serhiy Storchaka in :issue:`19668`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:432 +msgid "" +":class:`bytes`.join() and :class:`bytearray`.join() now accept arbitrary " +"buffer objects as arguments. (Contributed by Antoine Pitrou in :issue:" +"`15958`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:436 +msgid "" +"The :class:`int` constructor now accepts any object that has an " +"``__index__`` method for its *base* argument. (Contributed by Mark " +"Dickinson in :issue:`16772`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:440 +msgid "" +"Frame objects now have a :func:`~frame.clear` method that clears all " +"references to local variables from the frame. (Contributed by Antoine " +"Pitrou in :issue:`17934`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:444 +msgid "" +":class:`memoryview` is now registered as a :class:`Sequence `, and supports the :func:`reversed` builtin. (Contributed by Nick " +"Coghlan and Claudiu Popa in :issue:`18690` and :issue:`19078`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:448 +msgid "" +"Signatures reported by :func:`help` have been modified and improved in " +"several cases as a result of the introduction of Argument Clinic and other " +"changes to the :mod:`inspect` and :mod:`pydoc` modules." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:452 +msgid "" +":meth:`~object.__length_hint__` is now part of the formal language " +"specification (see :pep:`424`). (Contributed by Armin Ronacher in :issue:" +"`16148`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:464 ../Doc/whatsnew/3.5.rst:773 +#: ../Doc/whatsnew/3.6.rst:591 +msgid "asyncio" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:466 +msgid "" +"The new :mod:`asyncio` module (defined in :pep:`3156`) provides a standard " +"pluggable event loop model for Python, providing solid asynchronous IO " +"support in the standard library, and making it easier for other event loop " +"implementations to interoperate with the standard library and each other." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:471 ../Doc/whatsnew/3.4.rst:534 +msgid "For Python 3.4, this module is considered a :term:`provisional API`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:475 +msgid ":pep:`3156` -- Asynchronous IO Support Rebooted: the \"asyncio\" Module" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:476 +msgid "PEP written and implementation led by Guido van Rossum." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:482 +msgid "ensurepip" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:484 +msgid "" +"The new :mod:`ensurepip` module is the primary infrastructure for the :pep:" +"`453` implementation. In the normal course of events end users will not " +"need to interact with this module, but it can be used to manually bootstrap " +"``pip`` if the automated bootstrapping into an installation or virtual " +"environment was declined." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:490 +msgid "" +":mod:`ensurepip` includes a bundled copy of ``pip``, up-to-date as of the " +"first release candidate of the release of CPython with which it ships (this " +"applies to both maintenance releases and feature releases). ``ensurepip`` " +"does not access the internet. If the installation has Internet access, " +"after ``ensurepip`` is run the bundled ``pip`` can be used to upgrade " +"``pip`` to a more recent release than the bundled one. (Note that such an " +"upgraded version of ``pip`` is considered to be a separately installed " +"package and will not be removed if Python is uninstalled.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:499 +msgid "" +"The module is named *ensure*\\ pip because if called when ``pip`` is already " +"installed, it does nothing. It also has an ``--upgrade`` option that will " +"cause it to install the bundled copy of ``pip`` if the existing installed " +"version of ``pip`` is older than the bundled copy." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:508 ../Doc/whatsnew/3.5.rst:1123 +msgid "enum" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:510 +msgid "" +"The new :mod:`enum` module (defined in :pep:`435`) provides a standard " +"implementation of enumeration types, allowing other modules (such as :mod:" +"`socket`) to provide more informative error messages and better debugging " +"support by replacing opaque integer constants with backwards compatible " +"enumeration values." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:519 +msgid ":pep:`435` -- Adding an Enum type to the Python standard library" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:519 +msgid "" +"PEP written by Barry Warsaw, Eli Bendersky and Ethan Furman, implemented by " +"Ethan Furman." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:526 ../Doc/whatsnew/3.5.rst:1522 +msgid "pathlib" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:528 +msgid "" +"The new :mod:`pathlib` module offers classes representing filesystem paths " +"with semantics appropriate for different operating systems. Path classes " +"are divided between *pure paths*, which provide purely computational " +"operations without I/O, and *concrete paths*, which inherit from pure paths " +"but also provide I/O operations." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:538 +msgid ":pep:`428` -- The pathlib module -- object-oriented filesystem paths" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:545 ../Doc/whatsnew/3.5.rst:1631 +msgid "selectors" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:547 +msgid "" +"The new :mod:`selectors` module (created as part of implementing :pep:" +"`3156`) allows high-level and efficient I/O multiplexing, built upon the :" +"mod:`select` module primitives." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:555 +msgid "statistics" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:557 +msgid "" +"The new :mod:`statistics` module (defined in :pep:`450`) offers some core " +"statistics functionality directly in the standard library. This module " +"supports calculation of the mean, median, mode, variance and standard " +"deviation of a data series." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:564 +msgid ":pep:`450` -- Adding A Statistics Module To The Standard Library" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:565 +msgid "PEP written and implemented by Steven D'Aprano" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:571 +msgid "tracemalloc" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:573 +msgid "" +"The new :mod:`tracemalloc` module (defined in :pep:`454`) is a debug tool to " +"trace memory blocks allocated by Python. It provides the following " +"information:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:576 +msgid "Trace where an object was allocated" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:577 +msgid "" +"Statistics on allocated memory blocks per filename and per line number: " +"total size, number and average size of allocated memory blocks" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:579 +msgid "Compute the differences between two snapshots to detect memory leaks" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:583 +msgid "" +":pep:`454` -- Add a new tracemalloc module to trace Python memory allocations" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:584 +msgid "PEP written and implemented by Victor Stinner" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:595 +msgid "" +"New function :func:`abc.get_cache_token` can be used to know when to " +"invalidate caches that are affected by changes in the object graph. " +"(Contributed by Łukasz Langa in :issue:`16832`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:599 +msgid "" +"New class :class:`~abc.ABC` has :class:`~abc.ABCMeta` as its meta class. " +"Using ``ABC`` as a base class has essentially the same effect as specifying " +"``metaclass=abc.ABCMeta``, but is simpler to type and easier to read. " +"(Contributed by Bruno Dupuis in :issue:`16049`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:606 +msgid "aifc" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:608 +msgid "" +"The :meth:`~aifc.aifc.getparams` method now returns a namedtuple rather than " +"a plain tuple. (Contributed by Claudiu Popa in :issue:`17818`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:611 +msgid "" +":func:`aifc.open` now supports the context management protocol: when used in " +"a :keyword:`with` block, the :meth:`~aifc.aifc.close` method of the returned " +"object will be called automatically at the end of the block. (Contributed " +"by Serhiy Storchacha in :issue:`16486`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:616 +msgid "" +"The :meth:`~aifc.aifc.writeframesraw` and :meth:`~aifc.aifc.writeframes` " +"methods now accept any :term:`bytes-like object`. (Contributed by Serhiy " +"Storchaka in :issue:`8311`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:622 ../Doc/whatsnew/3.5.rst:764 +msgid "argparse" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:624 +msgid "" +"The :class:`~argparse.FileType` class now accepts *encoding* and *errors* " +"arguments, which are passed through to :func:`open`. (Contributed by Lucas " +"Maystre in :issue:`11175`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:630 +msgid "audioop" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:632 +msgid "" +":mod:`audioop` now supports 24-bit samples. (Contributed by Serhiy " +"Storchaka in :issue:`12866`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:635 +msgid "" +"New :func:`~audioop.byteswap` function converts big-endian samples to little-" +"endian and vice versa. (Contributed by Serhiy Storchaka in :issue:`19641`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:639 +msgid "" +"All :mod:`audioop` functions now accept any :term:`bytes-like object`. " +"Strings are not accepted: they didn't work before, now they raise an error " +"right away. (Contributed by Serhiy Storchaka in :issue:`16685`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:647 +msgid "" +"The encoding and decoding functions in :mod:`base64` now accept any :term:" +"`bytes-like object` in cases where it previously required a :class:`bytes` " +"or :class:`bytearray` instance. (Contributed by Nick Coghlan in :issue:" +"`17839`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:652 +msgid "" +"New functions :func:`~base64.a85encode`, :func:`~base64.a85decode`, :func:" +"`~base64.b85encode`, and :func:`~base64.b85decode` provide the ability to " +"encode and decode binary data from and to ``Ascii85`` and the git/mercurial " +"``Base85`` formats, respectively. The ``a85`` functions have options that " +"can be used to make them compatible with the variants of the ``Ascii85`` " +"encoding, including the Adobe variant. (Contributed by Martin Morrison, the " +"Mercurial project, Serhiy Storchaka, and Antoine Pitrou in :issue:`17618`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:664 +msgid "" +"The :meth:`.ChainMap.new_child` method now accepts an *m* argument " +"specifying the child map to add to the chain. This allows an existing " +"mapping and/or a custom mapping type to be used for the child. (Contributed " +"by Vinay Sajip in :issue:`16613`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:671 +msgid "colorsys" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:673 +msgid "" +"The number of digits in the coefficients for the RGB --- YIQ conversions " +"have been expanded so that they match the FCC NTSC versions. The change in " +"results should be less than 1% and may better match results found elsewhere. " +"(Contributed by Brian Landers and Serhiy Storchaka in :issue:`14323`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:682 +msgid "" +"The new :class:`contextlib.suppress` context manager helps to clarify the " +"intent of code that deliberately suppresses exceptions from a single " +"statement. (Contributed by Raymond Hettinger in :issue:`15806` and Zero " +"Piraeus in :issue:`19266`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:687 +msgid "" +"The new :func:`contextlib.redirect_stdout` context manager makes it easier " +"for utility scripts to handle inflexible APIs that write their output to :" +"data:`sys.stdout` and don't provide any options to redirect it. Using the " +"context manager, the :data:`sys.stdout` output can be redirected to any " +"other stream or, in conjunction with :class:`io.StringIO`, to a string. The " +"latter can be especially useful, for example, to capture output from a " +"function that was written to implement a command line interface. It is " +"recommended only for utility scripts because it affects the global state of :" +"data:`sys.stdout`. (Contributed by Raymond Hettinger in :issue:`15805`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:698 +msgid "" +"The :mod:`contextlib` documentation has also been updated to include a :ref:" +"`discussion ` of the differences " +"between single use, reusable and reentrant context managers." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:706 +msgid "" +":func:`dbm.open` objects now support the context management protocol. When " +"used in a :keyword:`with` statement, the ``close`` method of the database " +"object will be called automatically at the end of the block. (Contributed " +"by Claudiu Popa and Nick Coghlan in :issue:`19282`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:715 +msgid "" +"Functions :func:`~dis.show_code`, :func:`~dis.dis`, :func:`~dis.distb`, and :" +"func:`~dis.disassemble` now accept a keyword-only *file* argument that " +"controls where they write their output." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:719 +msgid "" +"The :mod:`dis` module is now built around an :class:`~dis.Instruction` class " +"that provides object oriented access to the details of each individual " +"bytecode operation." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:723 +msgid "" +"A new method, :func:`~dis.get_instructions`, provides an iterator that emits " +"the Instruction stream for a given piece of Python code. Thus it is now " +"possible to write a program that inspects and manipulates a bytecode object " +"in ways different from those provided by the :mod:`~dis` module itself. For " +"example::" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:737 +msgid "" +"The various display tools in the :mod:`dis` module have been rewritten to " +"use these new components." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:740 +msgid "" +"In addition, a new application-friendly class :class:`~dis.Bytecode` " +"provides an object-oriented API for inspecting bytecode in both in human-" +"readable form and for iterating over instructions. The :class:`~dis." +"Bytecode` constructor takes the same arguments that :func:`~dis." +"get_instruction` does (plus an optional *current_offset*), and the resulting " +"object can be iterated to produce :class:`~dis.Instruction` objects. But it " +"also has a :mod:`~dis.Bytecode.dis` method, equivalent to calling :mod:`~dis." +"dis` on the constructor argument, but returned as a multi-line string::" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:762 +msgid "" +":class:`~dis.Bytecode` also has a class method, :meth:`~dis.Bytecode." +"from_traceback`, that provides the ability to manipulate a traceback (that " +"is, ``print(Bytecode.from_traceback(tb).dis())`` is equivalent to " +"``distb(tb)``)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:767 +msgid "" +"(Contributed by Nick Coghlan, Ryan Kelly and Thomas Kluyver in :issue:" +"`11816` and Claudiu Popa in :issue:`17916`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:770 +msgid "" +"New function :func:`~dis.stack_effect` computes the effect on the Python " +"stack of a given opcode and argument, information that is not otherwise " +"available. (Contributed by Larry Hastings in :issue:`19722`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:778 +msgid "" +"A new :ref:`option flag `, :data:`~doctest.FAIL_FAST`, " +"halts test running as soon as the first failure is detected. (Contributed " +"by R. David Murray and Daniel Urban in :issue:`16522`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:782 +msgid "" +"The :mod:`doctest` command line interface now uses :mod:`argparse`, and has " +"two new options, ``-o`` and ``-f``. ``-o`` allows :ref:`doctest options " +"` to be specified on the command line, and ``-f`` is a " +"shorthand for ``-o FAIL_FAST`` (to parallel the similar option supported by " +"the :mod:`unittest` CLI). (Contributed by R. David Murray in :issue:" +"`11390`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:788 +msgid "" +":mod:`doctest` will now find doctests in extension module ``__doc__`` " +"strings. (Contributed by Zachary Ware in :issue:`3158`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:795 +msgid "" +":meth:`~email.message.Message.as_string` now accepts a *policy* argument to " +"override the default policy of the message when generating a string " +"representation of it. This means that ``as_string`` can now be used in more " +"circumstances, instead of having to create and use a :mod:`~email.generator` " +"in order to pass formatting parameters to its ``flatten`` method. " +"(Contributed by R. David Murray in :issue:`18600`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:802 +msgid "" +"New method :meth:`~email.message.Message.as_bytes` added to produce a bytes " +"representation of the message in a fashion similar to how ``as_string`` " +"produces a string representation. It does not accept the *maxheaderlen* " +"argument, but does accept the *unixfrom* and *policy* arguments. The :class:" +"`~email.message.Message` :meth:`~email.message.Message.__bytes__` method " +"calls it, meaning that ``bytes(mymsg)`` will now produce the intuitive " +"result: a bytes object containing the fully formatted message. " +"(Contributed by R. David Murray in :issue:`18600`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:811 +msgid "" +"The :meth:`.Message.set_param` message now accepts a *replace* keyword " +"argument. When specified, the associated header will be updated without " +"changing its location in the list of headers. For backward compatibility, " +"the default is ``False``. (Contributed by R. David Murray in :issue:" +"`18891`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:819 +msgid "" +"A pair of new subclasses of :class:`~email.message.Message` have been added " +"(:class:`.EmailMessage` and :class:`.MIMEPart`), along with a new sub-" +"module, :mod:`~email.contentmanager` and a new :mod:`~email.policy` " +"attribute :attr:`~email.policy.EmailPolicy.content_manager`. All " +"documentation is currently in the new module, which is being added as part " +"of email's new :term:`provisional API`. These classes provide a number of " +"new methods that make extracting content from and inserting content into " +"email messages much easier. For details, see the :mod:`~email." +"contentmanager` documentation and the :ref:`email-examples`. These API " +"additions complete the bulk of the work that was planned as part of the " +"email6 project. The currently provisional API is scheduled to become final " +"in Python 3.5 (possibly with a few minor additions in the area of error " +"handling). (Contributed by R. David Murray in :issue:`18891`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:835 +msgid "filecmp" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:837 +msgid "" +"A new :func:`~filecmp.clear_cache` function provides the ability to clear " +"the :mod:`filecmp` comparison cache, which uses :func:`os.stat` information " +"to determine if the file has changed since the last compare. This can be " +"used, for example, if the file might have been changed and re-checked in " +"less time than the resolution of a particular filesystem's file modification " +"time field. (Contributed by Mark Levitt in :issue:`18149`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:844 +msgid "" +"New module attribute :data:`~filecmp.DEFAULT_IGNORES` provides the list of " +"directories that are used as the default value for the *ignore* parameter of " +"the :func:`~filecmp.dircmp` function. (Contributed by Eli Bendersky in :" +"issue:`15442`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:853 +msgid "" +"The new :func:`~functools.partialmethod` descriptor brings partial argument " +"application to descriptors, just as :func:`~functools.partial` provides for " +"normal callables. The new descriptor also makes it easier to get arbitrary " +"callables (including :func:`~functools.partial` instances) to behave like " +"normal instance methods when included in a class definition. (Contributed by " +"Alon Horev and Nick Coghlan in :issue:`4331`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:862 +msgid "" +"The new :func:`~functools.singledispatch` decorator brings support for " +"single-dispatch generic functions to the Python standard library. Where " +"object oriented programming focuses on grouping multiple operations on a " +"common set of data into a class, a generic function focuses on grouping " +"multiple implementations of an operation that allows it to work with " +"*different* kinds of data." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:871 +msgid ":pep:`443` -- Single-dispatch generic functions" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:872 +msgid "PEP written and implemented by Łukasz Langa." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:874 +msgid "" +":func:`~functools.total_ordering` now supports a return value of :const:" +"`NotImplemented` from the underlying comparison function. (Contributed by " +"Katie Miller in :issue:`10042`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:878 +msgid "" +"A pure-python version of the :func:`~functools.partial` function is now in " +"the stdlib; in CPython it is overridden by the C accelerated version, but it " +"is available for other implementations to use. (Contributed by Brian Thorne " +"in :issue:`12428`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:887 +msgid "" +"New function :func:`~gc.get_stats` returns a list of three per-generation " +"dictionaries containing the collections statistics since interpreter " +"startup. (Contributed by Antoine Pitrou in :issue:`16351`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:893 ../Doc/whatsnew/3.5.rst:1158 +msgid "glob" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:895 +msgid "" +"A new function :func:`~glob.escape` provides a way to escape special " +"characters in a filename so that they do not become part of the globbing " +"expansion but are instead matched literally. (Contributed by Serhiy " +"Storchaka in :issue:`8402`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:903 +msgid "" +"A new :func:`hashlib.pbkdf2_hmac` function provides the `PKCS#5 password-" +"based key derivation function 2 `_. " +"(Contributed by Christian Heimes in :issue:`18582`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:908 +msgid "" +"The :attr:`~hashlib.hash.name` attribute of :mod:`hashlib` hash objects is " +"now a formally supported interface. It has always existed in CPython's :mod:" +"`hashlib` (although it did not return lower case names for all supported " +"hashes), but it was not a public interface and so some other Python " +"implementations have not previously supported it. (Contributed by Jason R. " +"Coombs in :issue:`18532`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:919 +msgid "" +":mod:`hmac` now accepts ``bytearray`` as well as ``bytes`` for the *key* " +"argument to the :func:`~hmac.new` function, and the *msg* parameter to both " +"the :func:`~hmac.new` function and the :meth:`~hmac.HMAC.update` method now " +"accepts any type supported by the :mod:`hashlib` module. (Contributed by " +"Jonas Borgström in :issue:`18240`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:925 +msgid "" +"The *digestmod* argument to the :func:`hmac.new` function may now be any " +"hash digest name recognized by :mod:`hashlib`. In addition, the current " +"behavior in which the value of *digestmod* defaults to ``MD5`` is " +"deprecated: in a future version of Python there will be no default value. " +"(Contributed by Christian Heimes in :issue:`17276`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:931 +msgid "" +"With the addition of :attr:`~hmac.HMAC.block_size` and :attr:`~hmac.HMAC." +"name` attributes (and the formal documentation of the :attr:`~hmac.HMAC." +"digest_size` attribute), the :mod:`hmac` module now conforms fully to the :" +"pep:`247` API. (Contributed by Christian Heimes in :issue:`18775`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:940 +msgid "" +"New function :func:`~html.unescape` function converts HTML5 character " +"references to the corresponding Unicode characters. (Contributed by Ezio " +"Melotti in :issue:`2927`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:944 +msgid "" +":class:`~html.parser.HTMLParser` accepts a new keyword argument " +"*convert_charrefs* that, when ``True``, automatically converts all character " +"references. For backward-compatibility, its value defaults to ``False``, " +"but it will change to ``True`` in a future version of Python, so you are " +"invited to set it explicitly and update your code to use this new feature. " +"(Contributed by Ezio Melotti in :issue:`13633`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:951 +msgid "" +"The *strict* argument of :class:`~html.parser.HTMLParser` is now deprecated. " +"(Contributed by Ezio Melotti in :issue:`15114`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:958 +msgid "" +":meth:`~http.server.BaseHTTPRequestHandler.send_error` now accepts an " +"optional additional *explain* parameter which can be used to provide an " +"extended error description, overriding the hardcoded default if there is " +"one. This extended error description will be formatted using the :attr:" +"`~http.server.HTTP.error_message_format` attribute and sent as the body of " +"the error response. (Contributed by Karl Cow in :issue:`12921`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:965 +msgid "" +"The :mod:`http.server` :ref:`command line interface ` now " +"has a ``-b/--bind`` option that causes the server to listen on a specific " +"address. (Contributed by Malte Swart in :issue:`17764`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:971 ../Doc/whatsnew/3.5.rst:1223 +#: ../Doc/whatsnew/3.6.rst:749 +msgid "idlelib and IDLE" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:973 +msgid "" +"Since idlelib implements the IDLE shell and editor and is not intended for " +"import by other programs, it gets improvements with every release. See :file:" +"`Lib/idlelib/NEWS.txt` for a cumulative list of changes since 3.3.0, as well " +"as changes made in future 3.4.x releases. This file is also available from " +"the IDLE :menuselection:`Help --> About IDLE` dialog." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:981 ../Doc/whatsnew/3.5.rst:1263 +#: ../Doc/whatsnew/3.6.rst:759 +msgid "importlib" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:983 +msgid "" +"The :class:`~importlib.abc.InspectLoader` ABC defines a new method, :meth:" +"`~importlib.abc.InspectLoader.source_to_code` that accepts source data and a " +"path and returns a code object. The default implementation is equivalent to " +"``compile(data, path, 'exec', dont_inherit=True)``. (Contributed by Eric " +"Snow and Brett Cannon in :issue:`15627`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:989 +msgid "" +":class:`~importlib.abc.InspectLoader` also now has a default implementation " +"for the :meth:`~importlib.abc.InspectLoader.get_code` method. However, it " +"will normally be desirable to override the default implementation for " +"performance reasons. (Contributed by Brett Cannon in :issue:`18072`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:994 +msgid "" +"The :func:`~importlib.reload` function has been moved from :mod:`imp` to :" +"mod:`importlib` as part of the :mod:`imp` module deprecation. (Contributed " +"by Berker Peksag in :issue:`18193`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:998 +msgid "" +":mod:`importlib.util` now has a :data:`~importlib.util.MAGIC_NUMBER` " +"attribute providing access to the bytecode version number. This replaces " +"the :func:`~imp.get_magic` function in the deprecated :mod:`imp` module. " +"(Contributed by Brett Cannon in :issue:`18192`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1003 +msgid "" +"New :mod:`importlib.util` functions :func:`~importlib.util." +"cache_from_source` and :func:`~importlib.util.source_from_cache` replace the " +"same-named functions in the deprecated :mod:`imp` module. (Contributed by " +"Brett Cannon in :issue:`18194`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1008 +msgid "" +"The :mod:`importlib` bootstrap :class:`.NamespaceLoader` now conforms to " +"the :class:`.InspectLoader` ABC, which means that ``runpy`` and ``python -" +"m`` can now be used with namespace packages. (Contributed by Brett Cannon " +"in :issue:`18058`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1013 +msgid "" +":mod:`importlib.util` has a new function :func:`~importlib.util." +"decode_source` that decodes source from bytes using universal newline " +"processing. This is useful for implementing :meth:`.InspectLoader." +"get_source` methods." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1017 +msgid "" +":class:`importlib.machinery.ExtensionFileLoader` now has a :meth:`~importlib." +"machinery.ExtensionFileLoader.get_filename` method. This was inadvertently " +"omitted in the original implementation. (Contributed by Eric Snow in :issue:" +"`19152`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1026 +msgid "" +"The :mod:`inspect` module now offers a basic :ref:`command line interface " +"` to quickly display source code and other information " +"for modules, classes and functions. (Contributed by Claudiu Popa and Nick " +"Coghlan in :issue:`18626`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1031 +msgid "" +":func:`~inspect.unwrap` makes it easy to unravel wrapper function chains " +"created by :func:`functools.wraps` (and any other API that sets the " +"``__wrapped__`` attribute on a wrapper function). (Contributed by Daniel " +"Urban, Aaron Iles and Nick Coghlan in :issue:`13266`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1036 +msgid "" +"As part of the implementation of the new :mod:`enum` module, the :mod:" +"`inspect` module now has substantially better support for custom ``__dir__`` " +"methods and dynamic class attributes provided through metaclasses. " +"(Contributed by Ethan Furman in :issue:`18929` and :issue:`19030`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1042 +msgid "" +":func:`~inspect.getfullargspec` and :func:`~inspect.getargspec` now use the :" +"func:`~inspect.signature` API. This allows them to support a much broader " +"range of callables, including those with ``__signature__`` attributes, those " +"with metadata provided by argument clinic, :func:`functools.partial` objects " +"and more. Note that, unlike :func:`~inspect.signature`, these functions " +"still ignore ``__wrapped__`` attributes, and report the already bound first " +"argument for bound methods, so it is still necessary to update your code to " +"use :func:`~inspect.signature` directly if those features are desired. " +"(Contributed by Yury Selivanov in :issue:`17481`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1053 +msgid "" +":func:`~inspect.signature` now supports duck types of CPython functions, " +"which adds support for functions compiled with Cython. (Contributed by " +"Stefan Behnel and Yury Selivanov in :issue:`17159`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1061 +msgid "" +":mod:`ipaddress` was added to the standard library in Python 3.3 as a :term:" +"`provisional API`. With the release of Python 3.4, this qualification has " +"been removed: :mod:`ipaddress` is now considered a stable API, covered by " +"the normal standard library requirements to maintain backwards compatibility." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1067 +msgid "" +"A new :attr:`~ipaddress.IPv4Address.is_global` property is ``True`` if an " +"address is globally routeable. (Contributed by Peter Moody in :issue:" +"`17400`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1075 +msgid "" +"The :class:`~logging.handlers.TimedRotatingFileHandler` has a new *atTime* " +"parameter that can be used to specify the time of day when rollover should " +"happen. (Contributed by Ronald Oussoren in :issue:`9556`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1079 +msgid "" +":class:`~logging.handlers.SocketHandler` and :class:`~logging.handlers." +"DatagramHandler` now support Unix domain sockets (by setting *port* to " +"``None``). (Contributed by Vinay Sajip in commit ce46195b56a9.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1084 +msgid "" +":func:`~logging.config.fileConfig` now accepts a :class:`configparser." +"RawConfigParser` subclass instance for the *fname* parameter. This " +"facilitates using a configuration file when logging configuration is just a " +"part of the overall application configuration, or where the application " +"modifies the configuration before passing it to :func:`~logging.config." +"fileConfig`. (Contributed by Vinay Sajip in :issue:`16110`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1092 +msgid "" +"Logging configuration data received from a socket via the :func:`logging." +"config.listen` function can now be validated before being processed by " +"supplying a verification function as the argument to the new *verify* " +"keyword argument. (Contributed by Vinay Sajip in :issue:`15452`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1101 +msgid "marshal" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1103 +msgid "" +"The default :mod:`marshal` version has been bumped to 3. The code " +"implementing the new version restores the Python2 behavior of recording only " +"one copy of interned strings and preserving the interning on " +"deserialization, and extends this \"one copy\" ability to any object type " +"(including handling recursive references). This reduces both the size of ``." +"pyc`` files and the amount of memory a module occupies in memory when it is " +"loaded from a ``.pyc`` (or ``.pyo``) file. (Contributed by Kristján Valur " +"Jónsson in :issue:`16475`, with additional speedups by Antoine Pitrou in :" +"issue:`19219`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1116 +msgid "" +"mmap objects can now be :mod:`weakref`\\ ed. (Contributed by Valerie " +"Lambert in :issue:`4885`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1125 +msgid "" +"On Unix two new :ref:`start methods `, " +"``spawn`` and ``forkserver``, have been added for starting processes using :" +"mod:`multiprocessing`. These make the mixing of processes with threads more " +"robust, and the ``spawn`` method matches the semantics that multiprocessing " +"has always used on Windows. New function :func:`~multiprocessing." +"get_all_start_methods` reports all start methods available on the platform, :" +"func:`~multiprocessing.get_start_method` reports the current start method, " +"and :func:`~multiprocessing.set_start_method` sets the start method. " +"(Contributed by Richard Oudkerk in :issue:`8713`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1135 +msgid "" +":mod:`multiprocessing` also now has the concept of a ``context``, which " +"determines how child processes are created. New function :func:" +"`~multiprocessing.get_context` returns a context that uses a specified start " +"method. It has the same API as the :mod:`multiprocessing` module itself, so " +"you can use it to create :class:`~multiprocessing.pool.Pool`\\ s and other " +"objects that will operate within that context. This allows a framework and " +"an application or different parts of the same application to use " +"multiprocessing without interfering with each other. (Contributed by " +"Richard Oudkerk in :issue:`18999`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1145 +msgid "" +"Except when using the old *fork* start method, child processes no longer " +"inherit unneeded handles/file descriptors from their parents (part of :issue:" +"`8713`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1149 +msgid "" +":mod:`multiprocessing` now relies on :mod:`runpy` (which implements the ``-" +"m`` switch) to initialise ``__main__`` appropriately in child processes when " +"using the ``spawn`` or ``forkserver`` start methods. This resolves some edge " +"cases where combining multiprocessing, the ``-m`` command line switch, and " +"explicit relative imports could cause obscure failures in child processes. " +"(Contributed by Nick Coghlan in :issue:`19946`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1158 ../Doc/whatsnew/3.5.rst:1468 +msgid "operator" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1160 +msgid "" +"New function :func:`~operator.length_hint` provides an implementation of the " +"specification for how the :meth:`~object.__length_hint__` special method " +"should be used, as part of the :pep:`424` formal specification of this " +"language feature. (Contributed by Armin Ronacher in :issue:`16148`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1165 +msgid "" +"There is now a pure-python version of the :mod:`operator` module available " +"for reference and for use by alternate implementations of Python. " +"(Contributed by Zachary Ware in :issue:`16694`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1173 +msgid "" +"There are new functions to get and set the :ref:`inheritable flag " +"` of a file descriptor (:func:`os.get_inheritable`, :func:" +"`os.set_inheritable`) or a Windows handle (:func:`os." +"get_handle_inheritable`, :func:`os.set_handle_inheritable`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1178 +msgid "" +"New function :func:`~os.cpu_count` reports the number of CPUs available on " +"the platform on which Python is running (or ``None`` if the count can't be " +"determined). The :func:`multiprocessing.cpu_count` function is now " +"implemented in terms of this function). (Contributed by Trent Nelson, " +"Yogesh Chaudhari, Victor Stinner, and Charles-François Natali in :issue:" +"`17914`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1184 +msgid "" +":func:`os.path.samestat` is now available on the Windows platform (and the :" +"func:`os.path.samefile` implementation is now shared between Unix and " +"Windows). (Contributed by Brian Curtin in :issue:`11939`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1188 +msgid "" +":func:`os.path.ismount` now recognizes volumes mounted below a drive root on " +"Windows. (Contributed by Tim Golden in :issue:`9035`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1191 +msgid "" +":func:`os.open` supports two new flags on platforms that provide them, :data:" +"`~os.O_PATH` (un-opened file descriptor), and :data:`~os.O_TMPFILE` (unnamed " +"temporary file; as of 3.4.0 release available only on Linux systems with a " +"kernel version of 3.11 or newer that have uapi headers). (Contributed by " +"Christian Heimes in :issue:`18673` and Benjamin Peterson, respectively.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1201 +msgid "" +":mod:`pdb` has been enhanced to handle generators, :keyword:`yield`, and " +"``yield from`` in a more useful fashion. This is especially helpful when " +"debugging :mod:`asyncio` based programs. (Contributed by Andrew Svetlov and " +"Xavier de Gaye in :issue:`16596`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1206 +msgid "" +"The ``print`` command has been removed from :mod:`pdb`, restoring access to " +"the Python :func:`print` function from the pdb command line. Python2's " +"``pdb`` did not have a ``print`` command; instead, entering ``print`` " +"executed the ``print`` statement. In Python3 ``print`` was mistakenly made " +"an alias for the pdb :pdbcmd:`p` command. ``p``, however, prints the " +"``repr`` of its argument, not the ``str`` like the Python2 ``print`` command " +"did. Worse, the Python3 ``pdb print`` command shadowed the Python3 " +"``print`` function, making it inaccessible at the ``pdb`` prompt. " +"(Contributed by Connor Osborn in :issue:`18764`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1222 +msgid "" +":mod:`pickle` now supports (but does not use by default) a new pickle " +"protocol, protocol 4. This new protocol addresses a number of issues that " +"were present in previous protocols, such as the serialization of nested " +"classes, very large strings and containers, and classes whose :meth:" +"`__new__` method takes keyword-only arguments. It also provides some " +"efficiency improvements." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1230 +msgid ":pep:`3154` -- Pickle protocol 4" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1231 +msgid "PEP written by Antoine Pitrou and implemented by Alexandre Vassalotti." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1235 +msgid "plistlib" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1237 +msgid "" +":mod:`plistlib` now has an API that is similar to the standard pattern for " +"stdlib serialization protocols, with new :func:`~plistlib.load`, :func:" +"`~plistlib.dump`, :func:`~plistlib.loads`, and :func:`~plistlib.dumps` " +"functions. (The older API is now deprecated.) In addition to the already " +"supported XML plist format (:data:`~plistlib.FMT_XML`), it also now supports " +"the binary plist format (:data:`~plistlib.FMT_BINARY`). (Contributed by " +"Ronald Oussoren and others in :issue:`14455`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1249 +msgid "" +"Two new methods have been added to :mod:`poplib`: :meth:`~poplib.POP3.capa`, " +"which returns the list of capabilities advertised by the POP server, and :" +"meth:`~poplib.POP3.stls`, which switches a clear-text POP3 session into an " +"encrypted POP3 session if the POP server supports it. (Contributed by " +"Lorenzo Catucci in :issue:`4473`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1257 +msgid "pprint" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1259 +msgid "" +"The :mod:`pprint` module's :class:`~pprint.PrettyPrinter` class and its :" +"func:`~pprint.pformat`, and :func:`~pprint.pprint` functions have a new " +"option, *compact*, that controls how the output is formatted. Currently " +"setting *compact* to ``True`` means that sequences will be printed with as " +"many sequence elements as will fit within *width* on each (indented) line. " +"(Contributed by Serhiy Storchaka in :issue:`19132`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1266 +msgid "" +"Long strings are now wrapped using Python's normal line continuation " +"syntax. (Contributed by Antoine Pitrou in :issue:`17150`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1271 +msgid "pty" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1273 +msgid "" +":func:`pty.spawn` now returns the status value from :func:`os.waitpid` on " +"the child process, instead of ``None``. (Contributed by Gregory P. Smith.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1280 +msgid "" +"The :mod:`pydoc` module is now based directly on the :func:`inspect." +"signature` introspection API, allowing it to provide signature information " +"for a wider variety of callable objects. This change also means that " +"``__wrapped__`` attributes are now taken into account when displaying help " +"information. (Contributed by Larry Hastings in :issue:`19674`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1286 +msgid "" +"The :mod:`pydoc` module no longer displays the ``self`` parameter for " +"already bound methods. Instead, it aims to always display the exact current " +"signature of the supplied callable. (Contributed by Larry Hastings in :" +"issue:`20710`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1291 +msgid "" +"In addition to the changes that have been made to :mod:`pydoc` directly, its " +"handling of custom ``__dir__`` methods and various descriptor behaviours has " +"also been improved substantially by the underlying changes in the :mod:" +"`inspect` module." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1296 +msgid "" +"As the :func:`help` builtin is based on :mod:`pydoc`, the above changes also " +"affect the behaviour of :func:`help`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1303 +msgid "" +"New :func:`~re.fullmatch` function and :meth:`.regex.fullmatch` method " +"anchor the pattern at both ends of the string to match. This provides a way " +"to be explicit about the goal of the match, which avoids a class of subtle " +"bugs where ``$`` characters get lost during code changes or the addition of " +"alternatives to an existing regular expression. (Contributed by Matthew " +"Barnett in :issue:`16203`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1310 +msgid "" +"The repr of :ref:`regex objects ` now includes the pattern and " +"the flags; the repr of :ref:`match objects ` now includes the " +"start, end, and the part of the string that matched. (Contributed by Hugo " +"Lopes Tavares and Serhiy Storchaka in :issue:`13592` and :issue:`17087`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1318 +msgid "resource" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1320 +msgid "" +"New :func:`~resource.prlimit` function, available on Linux platforms with a " +"kernel version of 2.6.36 or later and glibc of 2.13 or later, provides the " +"ability to query or set the resource limits for processes other than the one " +"making the call. (Contributed by Christian Heimes in :issue:`16595`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1325 +msgid "" +"On Linux kernel version 2.6.36 or later, there are also some new Linux " +"specific constants: :attr:`~resource.RLIMIT_MSGQUEUE`, :attr:`~resource." +"RLIMIT_NICE`, :attr:`~resource.RLIMIT_RTPRIO`, :attr:`~resource." +"RLIMIT_RTTIME`, and :attr:`~resource.RLIMIT_SIGPENDING`. (Contributed by " +"Christian Heimes in :issue:`19324`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1331 +msgid "" +"On FreeBSD version 9 and later, there some new FreeBSD specific constants: :" +"attr:`~resource.RLIMIT_SBSIZE`, :attr:`~resource.RLIMIT_SWAP`, and :attr:" +"`~resource.RLIMIT_NPTS`. (Contributed by Claudiu Popa in :issue:`19343`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1340 +msgid "" +":class:`~select.epoll` objects now support the context management protocol. " +"When used in a :keyword:`with` statement, the :meth:`~select.epoll.close` " +"method will be called automatically at the end of the block. (Contributed " +"by Serhiy Storchaka in :issue:`16488`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1345 +msgid "" +":class:`~select.devpoll` objects now have :meth:`~select.devpoll.fileno` " +"and :meth:`~select.devpoll.close` methods, as well as a new attribute :attr:" +"`~select.devpoll.closed`. (Contributed by Victor Stinner in :issue:`18794`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1352 +msgid "shelve" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1354 +msgid "" +":class:`~shelve.Shelf` instances may now be used in :keyword:`with` " +"statements, and will be automatically closed at the end of the :keyword:" +"`with` block. (Contributed by Filip Gruszczyński in :issue:`13896`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1362 +msgid "" +":func:`~shutil.copyfile` now raises a specific :exc:`~shutil.Error` " +"subclass, :exc:`~shutil.SameFileError`, when the source and destination are " +"the same file, which allows an application to take appropriate action on " +"this specific error. (Contributed by Atsuo Ishimoto and Hynek Schlawack in :" +"issue:`1492704`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1372 +msgid "" +"The :class:`~smtpd.SMTPServer` and :class:`~smtpd.SMTPChannel` classes now " +"accept a *map* keyword argument which, if specified, is passed in to :class:" +"`asynchat.async_chat` as its *map* argument. This allows an application to " +"avoid affecting the global socket map. (Contributed by Vinay Sajip in :" +"issue:`11959`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1382 +msgid "" +":exc:`~smtplib.SMTPException` is now a subclass of :exc:`OSError`, which " +"allows both socket level errors and SMTP protocol level errors to be caught " +"in one try/except statement by code that only cares whether or not an error " +"occurred. (Contributed by Ned Jackson Lovely in :issue:`2118`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1391 +msgid "" +"The socket module now supports the :data:`~socket.CAN_BCM` protocol on " +"platforms that support it. (Contributed by Brian Thorne in :issue:`15359`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1394 +msgid "" +"Socket objects have new methods to get or set their :ref:`inheritable flag " +"`, :meth:`~socket.socket.get_inheritable` and :meth:`~socket." +"socket.set_inheritable`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1398 +msgid "" +"The ``socket.AF_*`` and ``socket.SOCK_*`` constants are now enumeration " +"values using the new :mod:`enum` module. This allows meaningful names to be " +"printed during debugging, instead of integer \"magic numbers\"." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1402 +msgid "The :data:`~socket.AF_LINK` constant is now available on BSD and OSX." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1404 +msgid "" +":func:`~socket.inet_pton` and :func:`~socket.inet_ntop` are now supported on " +"Windows. (Contributed by Atsuo Ishimoto in :issue:`7171`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1411 +msgid "" +"A new boolean parameter to the :func:`~sqlite3.connect` function, *uri*, can " +"be used to indicate that the *database* parameter is a ``uri`` (see the " +"`SQLite URI documentation `_). " +"(Contributed by poq in :issue:`13773`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1422 +msgid "" +":data:`~ssl.PROTOCOL_TLSv1_1` and :data:`~ssl.PROTOCOL_TLSv1_2` (TLSv1.1 and " +"TLSv1.2 support) have been added; support for these protocols is only " +"available if Python is linked with OpenSSL 1.0.1 or later. (Contributed by " +"Michele Orrù and Antoine Pitrou in :issue:`16692`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1429 +msgid "" +"New function :func:`~ssl.create_default_context` provides a standard way to " +"obtain an :class:`~ssl.SSLContext` whose settings are intended to be a " +"reasonable balance between compatibility and security. These settings are " +"more stringent than the defaults provided by the :class:`~ssl.SSLContext` " +"constructor, and may be adjusted in the future, without prior deprecation, " +"if best-practice security requirements change. The new recommended best " +"practice for using stdlib libraries that support SSL is to use :func:`~ssl." +"create_default_context` to obtain an :class:`~ssl.SSLContext` object, modify " +"it if needed, and then pass it as the *context* argument of the appropriate " +"stdlib API. (Contributed by Christian Heimes in :issue:`19689`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1441 +msgid "" +":class:`~ssl.SSLContext` method :meth:`~ssl.SSLContext." +"load_verify_locations` accepts a new optional argument *cadata*, which can " +"be used to provide PEM or DER encoded certificates directly via strings or " +"bytes, respectively. (Contributed by Christian Heimes in :issue:`18138`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1446 +msgid "" +"New function :func:`~ssl.get_default_verify_paths` returns a named tuple of " +"the paths and environment variables that the :meth:`~ssl.SSLContext." +"set_default_verify_paths` method uses to set OpenSSL's default ``cafile`` " +"and ``capath``. This can be an aid in debugging default verification " +"issues. (Contributed by Christian Heimes in :issue:`18143`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1453 +msgid "" +":class:`~ssl.SSLContext` has a new method, :meth:`~ssl.SSLContext." +"cert_store_stats`, that reports the number of loaded ``X.509`` certs, " +"``X.509 CA`` certs, and certificate revocation lists (``crl``\\ s), as well " +"as a :meth:`~ssl.SSLContext.get_ca_certs` method that returns a list of the " +"loaded ``CA`` certificates. (Contributed by Christian Heimes in :issue:" +"`18147`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1460 +msgid "" +"If OpenSSL 0.9.8 or later is available, :class:`~ssl.SSLContext` has a new " +"attribute :attr:`~ssl.SSLContext.verify_flags` that can be used to control " +"the certificate verification process by setting it to some combination of " +"the new constants :data:`~ssl.VERIFY_DEFAULT`, :data:`~ssl." +"VERIFY_CRL_CHECK_LEAF`, :data:`~ssl.VERIFY_CRL_CHECK_CHAIN`, or :data:`~ssl." +"VERIFY_X509_STRICT`. OpenSSL does not do any CRL verification by default. " +"(Contributed by Christien Heimes in :issue:`8813`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1468 +msgid "" +"New :class:`~ssl.SSLContext` method :meth:`~ssl.SSLContext." +"load_default_certs` loads a set of default \"certificate authority\" (CA) " +"certificates from default locations, which vary according to the platform. " +"It can be used to load both TLS web server authentication certificates " +"(``purpose=``:data:`~ssl.Purpose.SERVER_AUTH`) for a client to use to verify " +"a server, and certificates for a server to use in verifying client " +"certificates (``purpose=``:data:`~ssl.Purpose.CLIENT_AUTH`). (Contributed " +"by Christian Heimes in :issue:`19292`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1479 +msgid "" +"Two new windows-only functions, :func:`~ssl.enum_certificates` and :func:" +"`~ssl.enum_crls` provide the ability to retrieve certificates, certificate " +"information, and CRLs from the Windows cert store. (Contributed by " +"Christian Heimes in :issue:`17134`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1486 +msgid "" +"Support for server-side SNI (Server Name Indication) using the new :meth:" +"`ssl.SSLContext.set_servername_callback` method. (Contributed by Daniel " +"Black in :issue:`8109`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1490 +msgid "" +"The dictionary returned by :meth:`.SSLSocket.getpeercert` contains " +"additional ``X509v3`` extension items: ``crlDistributionPoints``, " +"``calIssuers``, and ``OCSP`` URIs. (Contributed by Christian Heimes in :" +"issue:`18379`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1498 +msgid "" +"The :mod:`stat` module is now backed by a C implementation in :mod:`_stat`. " +"A C implementation is required as most of the values aren't standardized and " +"are platform-dependent. (Contributed by Christian Heimes in :issue:`11016`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1502 +msgid "" +"The module supports new :mod:`~stat.ST_MODE` flags, :mod:`~stat.S_IFDOOR`, :" +"attr:`~stat.S_IFPORT`, and :attr:`~stat.S_IFWHT`. (Contributed by Christian " +"Hiemes in :issue:`11016`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1510 +msgid "" +"New function :mod:`~struct.iter_unpack` and a new :meth:`struct.Struct." +"iter_unpack` method on compiled formats provide streamed unpacking of a " +"buffer containing repeated instances of a given format of data. (Contributed " +"by Antoine Pitrou in :issue:`17804`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1519 +msgid "" +":func:`~subprocess.check_output` now accepts an *input* argument that can be " +"used to provide the contents of ``stdin`` for the command that is run. " +"(Contributed by Zack Weinberg in :issue:`16624`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1523 +msgid "" +":func:`~subprocess.getstatus` and :func:`~subprocess.getstatusoutput` now " +"work on Windows. This change was actually inadvertently made in 3.3.4. " +"(Contributed by Tim Golden in :issue:`10197`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1529 +msgid "sunau" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1531 +msgid "" +"The :meth:`~sunau.getparams` method now returns a namedtuple rather than a " +"plain tuple. (Contributed by Claudiu Popa in :issue:`18901`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1534 +msgid "" +":meth:`sunau.open` now supports the context management protocol: when used " +"in a :keyword:`with` block, the ``close`` method of the returned object will " +"be called automatically at the end of the block. (Contributed by Serhiy " +"Storchaka in :issue:`18878`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1539 +msgid "" +":meth:`.AU_write.setsampwidth` now supports 24 bit samples, thus adding " +"support for writing 24 sample using the module. (Contributed by Serhiy " +"Storchaka in :issue:`19261`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1543 +msgid "" +"The :meth:`~sunau.AU_write.writeframesraw` and :meth:`~sunau.AU_write." +"writeframes` methods now accept any :term:`bytes-like object`. (Contributed " +"by Serhiy Storchaka in :issue:`8311`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1551 +msgid "" +"New function :func:`sys.getallocatedblocks` returns the current number of " +"blocks allocated by the interpreter. (In CPython with the default ``--with-" +"pymalloc`` setting, this is allocations made through the :c:func:" +"`PyObject_Malloc` API.) This can be useful for tracking memory leaks, " +"especially if automated via a test suite. (Contributed by Antoine Pitrou " +"in :issue:`13390`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1558 +msgid "" +"When the Python interpreter starts in :ref:`interactive mode `, it checks for an :data:`~sys.__interactivehook__` attribute " +"on the :mod:`sys` module. If the attribute exists, its value is called with " +"no arguments just before interactive mode is started. The check is made " +"after the :envvar:`PYTHONSTARTUP` file is read, so it can be set there. " +"The :mod:`site` module :ref:`sets it ` to a function " +"that enables tab completion and history saving (in :file:`~/.python-" +"history`) if the platform supports :mod:`readline`. If you do not want this " +"(new) behavior, you can override it in :envvar:`PYTHONSTARTUP`, :mod:" +"`sitecustomize`, or :mod:`usercustomize` by deleting this attribute from :" +"mod:`sys` (or setting it to some other callable). (Contributed by Éric " +"Araujo and Antoine Pitrou in :issue:`5845`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1575 +msgid "" +"The :mod:`tarfile` module now supports a simple :ref:`tarfile-commandline` " +"when called as a script directly or via ``-m``. This can be used to create " +"and extract tarfile archives. (Contributed by Berker Peksag in :issue:" +"`13477`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1583 +msgid "" +"The :class:`~textwrap.TextWrapper` class has two new attributes/constructor " +"arguments: :attr:`~textwrap.TextWrapper.max_lines`, which limits the number " +"of lines in the output, and :attr:`~textwrap.TextWrapper.placeholder`, which " +"is a string that will appear at the end of the output if it has been " +"truncated because of *max_lines*. Building on these capabilities, a new " +"convenience function :func:`~textwrap.shorten` collapses all of the " +"whitespace in the input to single spaces and produces a single line of a " +"given *width* that ends with the *placeholder* (by default, ``[...]``). " +"(Contributed by Antoine Pitrou and Serhiy Storchaka in :issue:`18585` and :" +"issue:`18725`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1597 +msgid "" +"The :class:`~threading.Thread` object representing the main thread can be " +"obtained from the new :func:`~threading.main_thread` function. In normal " +"conditions this will be the thread from which the Python interpreter was " +"started. (Contributed by Andrew Svetlov in :issue:`18882`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1604 ../Doc/whatsnew/3.5.rst:1947 +#: ../Doc/whatsnew/3.6.rst:959 +msgid "traceback" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1606 +msgid "" +"A new :func:`traceback.clear_frames` function takes a traceback object and " +"clears the local variables in all of the frames it references, reducing the " +"amount of memory consumed. (Contributed by Andrew Kuchling in :issue:" +"`1565525`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1615 +msgid "" +"A new :func:`~types.DynamicClassAttribute` descriptor provides a way to " +"define an attribute that acts normally when looked up through an instance " +"object, but which is routed to the *class* ``__getattr__`` when looked up " +"through the class. This allows one to have properties active on a class, " +"and have virtual attributes on the class with the same name (see :mod:`Enum` " +"for an example). (Contributed by Ethan Furman in :issue:`19030`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1626 +msgid "" +":mod:`urllib.request` now supports ``data:`` URLs via the :class:`~urllib." +"request.DataHandler` class. (Contributed by Mathias Panzenböck in :issue:" +"`16423`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1630 +msgid "" +"The http method that will be used by a :class:`~urllib.request.Request` " +"class can now be specified by setting a :class:`~urllib.request.Request." +"method` class attribute on the subclass. (Contributed by Jason R Coombs in :" +"issue:`18978`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1635 +msgid "" +":class:`~urllib.request.Request` objects are now reusable: if the :attr:" +"`~urllib.request.Request.full_url` or :attr:`~urllib.request.Request.data` " +"attributes are modified, all relevant internal properties are updated. This " +"means, for example, that it is now possible to use the same :class:`~urllib." +"request.Request` object in more than one :meth:`.OpenerDirector.open` call " +"with different *data* arguments, or to modify a :class:`~urllib.request." +"Request`\\ 's ``url`` rather than recomputing it from scratch. There is " +"also a new :meth:`~urllib.request.Request.remove_header` method that can be " +"used to remove headers from a :class:`~urllib.request.Request`. " +"(Contributed by Alexey Kachayev in :issue:`16464`, Daniel Wozniak in :issue:" +"`17485`, and Damien Brecht and Senthil Kumaran in :issue:`17272`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1648 +msgid "" +":class:`~urllib.error.HTTPError` objects now have a :attr:`~urllib.error." +"HTTPError.headers` attribute that provides access to the HTTP response " +"headers associated with the error. (Contributed by Berker Peksag in :issue:" +"`15701`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1657 +msgid "" +"The :class:`~unittest.TestCase` class has a new method, :meth:`~unittest." +"TestCase.subTest`, that produces a context manager whose :keyword:`with` " +"block becomes a \"sub-test\". This context manager allows a test method to " +"dynamically generate subtests by, say, calling the ``subTest`` context " +"manager inside a loop. A single test method can thereby produce an " +"indefinite number of separately-identified and separately-counted tests, all " +"of which will run even if one or more of them fail. For example::" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1671 +msgid "" +"will result in six subtests, each identified in the unittest verbose output " +"with a label consisting of the variable name ``i`` and a particular value " +"for that variable (``i=0``, ``i=1``, etc). See :ref:`subtests` for the full " +"version of this example. (Contributed by Antoine Pitrou in :issue:`16997`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1676 +msgid "" +":func:`unittest.main` now accepts an iterable of test names for " +"*defaultTest*, where previously it only accepted a single test name as a " +"string. (Contributed by Jyrki Pulliainen in :issue:`15132`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1680 +msgid "" +"If :class:`~unittest.SkipTest` is raised during test discovery (that is, at " +"the module level in the test file), it is now reported as a skip instead of " +"an error. (Contributed by Zach Ware in :issue:`16935`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1684 +msgid "" +":meth:`~unittest.TestLoader.discover` now sorts the discovered files to " +"provide consistent test ordering. (Contributed by Martin Melin and Jeff " +"Ramnani in :issue:`16709`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1688 +msgid "" +":class:`~unittest.TestSuite` now drops references to tests as soon as the " +"test has been run, if the test is successful. On Python interpreters that " +"do garbage collection, this allows the tests to be garbage collected if " +"nothing else is holding a reference to the test. It is possible to override " +"this behavior by creating a :class:`~unittest.TestSuite` subclass that " +"defines a custom ``_removeTestAtIndex`` method. (Contributed by Tom " +"Wardill, Matt McClure, and Andrew Svetlov in :issue:`11798`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1696 +msgid "" +"A new test assertion context-manager, :meth:`~unittest.TestCase.assertLogs`, " +"will ensure that a given block of code emits a log message using the :mod:" +"`logging` module. By default the message can come from any logger and have " +"a priority of ``INFO`` or higher, but both the logger name and an " +"alternative minimum logging level may be specified. The object returned by " +"the context manager can be queried for the :class:`~logging.LogRecord`\\ s " +"and/or formatted messages that were logged. (Contributed by Antoine Pitrou " +"in :issue:`18937`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1705 +msgid "" +"Test discovery now works with namespace packages (Contributed by Claudiu " +"Popa in :issue:`17457`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1708 +msgid "" +":mod:`unittest.mock` objects now inspect their specification signatures when " +"matching calls, which means an argument can now be matched by either " +"position or name, instead of only by position. (Contributed by Antoine " +"Pitrou in :issue:`17015`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1713 +msgid "" +":func:`~mock.mock_open` objects now have ``readline`` and ``readlines`` " +"methods. (Contributed by Toshio Kuratomi in :issue:`17467`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1718 ../Doc/whatsnew/3.6.rst:651 +msgid "venv" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1720 +msgid "" +":mod:`venv` now includes activation scripts for the ``csh`` and ``fish`` " +"shells. (Contributed by Andrew Svetlov in :issue:`15417`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1723 +msgid "" +":class:`~venv.EnvBuilder` and the :func:`~venv.create` convenience function " +"take a new keyword argument *with_pip*, which defaults to ``False``, that " +"controls whether or not :class:`~venv.EnvBuilder` ensures that ``pip`` is " +"installed in the virtual environment. (Contributed by Nick Coghlan in :" +"issue:`19552` as part of the :pep:`453` implementation.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1731 +msgid "wave" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1733 +msgid "" +"The :meth:`~wave.getparams` method now returns a namedtuple rather than a " +"plain tuple. (Contributed by Claudiu Popa in :issue:`17487`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1736 +msgid "" +":meth:`wave.open` now supports the context management protocol. " +"(Contributed by Claudiu Popa in :issue:`17616`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1739 +msgid "" +":mod:`wave` can now :ref:`write output to unseekable files `. (Contributed by David Jones, Guilherme Polo, and Serhiy " +"Storchaka in :issue:`5202`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1743 +msgid "" +"The :meth:`~wave.Wave_write.writeframesraw` and :meth:`~wave.Wave_write." +"writeframes` methods now accept any :term:`bytes-like object`. (Contributed " +"by Serhiy Storchaka in :issue:`8311`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1749 +msgid "weakref" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1751 +msgid "" +"New :class:`~weakref.WeakMethod` class simulates weak references to bound " +"methods. (Contributed by Antoine Pitrou in :issue:`14631`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1754 +msgid "" +"New :class:`~weakref.finalize` class makes it possible to register a " +"callback to be invoked when an object is garbage collected, without needing " +"to carefully manage the lifecycle of the weak reference itself. " +"(Contributed by Richard Oudkerk in :issue:`15528`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1759 +msgid "" +"The callback, if any, associated with a :class:`~weakref.ref` is now exposed " +"via the :attr:`~weakref.ref.__callback__` attribute. (Contributed by Mark " +"Dickinson in :issue:`17643`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1765 +msgid "xml.etree" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1767 +msgid "" +"A new parser, :class:`~xml.etree.ElementTree.XMLPullParser`, allows a non-" +"blocking applications to parse XML documents. An example can be seen at :" +"ref:`elementtree-pull-parsing`. (Contributed by Antoine Pitrou in :issue:" +"`17741`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1772 +msgid "" +"The :mod:`xml.etree.ElementTree` :func:`~xml.etree.ElementTree.tostring` " +"and :func:`~xml.etree.ElementTree.tostringlist` functions, and the :class:" +"`~xml.etree.ElementTree.ElementTree` :meth:`~xml.etree.ElementTree." +"ElementTree.write` method, now have a *short_empty_elements* :ref:`keyword-" +"only parameter ` providing control over whether " +"elements with no content are written in abbreviated (````) or " +"expanded (````) form. (Contributed by Ariel Poliak and Serhiy " +"Storchaka in :issue:`14377`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1783 ../Doc/whatsnew/3.5.rst:2085 +#: ../Doc/whatsnew/3.6.rst:1085 +msgid "zipfile" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1785 +msgid "" +"The :meth:`~zipfile.PyZipFile.writepy` method of the :class:`~zipfile." +"PyZipFile` class has a new *filterfunc* option that can be used to control " +"which directories and files are added to the archive. For example, this " +"could be used to exclude test files from the archive. (Contributed by " +"Christian Tismer in :issue:`19274`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1791 +msgid "" +"The *allowZip64* parameter to :class:`~zipfile.ZipFile` and :class:`~zipfile." +"PyZipfile` is now ``True`` by default. (Contributed by William Mallard in :" +"issue:`17201`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1798 +msgid "CPython Implementation Changes" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1804 +msgid "PEP 445: Customization of CPython Memory Allocators" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1806 +msgid "" +":pep:`445` adds new C level interfaces to customize memory allocation in the " +"CPython interpreter." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1811 +msgid ":pep:`445` -- Add new APIs to customize Python memory allocators" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1818 +msgid "PEP 442: Safe Object Finalization" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1820 +msgid "" +":pep:`442` removes the current limitations and quirks of object finalization " +"in CPython. With it, objects with :meth:`__del__` methods, as well as " +"generators with :keyword:`finally` clauses, can be finalized when they are " +"part of a reference cycle." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1825 +msgid "" +"As part of this change, module globals are no longer forcibly set to :const:" +"`None` during interpreter shutdown in most cases, instead relying on the " +"normal operation of the cyclic garbage collector. This avoids a whole class " +"of interpreter-shutdown-time errors, usually involving ``__del__`` methods, " +"that have plagued Python since the cyclic GC was first introduced." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1834 +msgid ":pep:`442` -- Safe object finalization" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1841 +msgid "PEP 456: Secure and Interchangeable Hash Algorithm" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1843 +msgid "" +":pep:`456` follows up on earlier security fix work done on Python's hash " +"algorithm to address certain DOS attacks to which public facing APIs backed " +"by dictionary lookups may be subject. (See :issue:`14621` for the start of " +"the current round of improvements.) The PEP unifies CPython's hash code to " +"make it easier for a packager to substitute a different hash algorithm, and " +"switches Python's default implementation to a SipHash implementation on " +"platforms that have a 64 bit data type. Any performance differences in " +"comparison with the older FNV algorithm are trivial." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1852 +msgid "" +"The PEP adds additional fields to the :attr:`sys.hash_info` struct sequence " +"to describe the hash algorithm in use by the currently executing binary. " +"Otherwise, the PEP does not alter any existing CPython APIs." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1860 +msgid "PEP 436: Argument Clinic" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1862 +msgid "" +"\"Argument Clinic\" (:pep:`436`) is now part of the CPython build process " +"and can be used to simplify the process of defining and maintaining accurate " +"signatures for builtins and standard library extension modules implemented " +"in C." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1867 +msgid "" +"Some standard library extension modules have been converted to use Argument " +"Clinic in Python 3.4, and :mod:`pydoc` and :mod:`inspect` have been updated " +"accordingly." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1871 +msgid "" +"It is expected that signature metadata for programmatic introspection will " +"be added to additional callables implemented in C as part of Python 3.4 " +"maintenance releases." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1876 +msgid "" +"The Argument Clinic PEP is not fully up to date with the state of the " +"implementation. This has been deemed acceptable by the release manager and " +"core development team in this case, as Argument Clinic will not be made " +"available as a public API for third party use in Python 3.4." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1883 +msgid ":pep:`436` -- The Argument Clinic DSL" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1884 +msgid "PEP written and implemented by Larry Hastings." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1888 +msgid "Other Build and C API Changes" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1890 +msgid "" +"The new :c:func:`PyType_GetSlot` function has been added to the stable ABI, " +"allowing retrieval of function pointers from named type slots when using the " +"limited API. (Contributed by Martin von Löwis in :issue:`17162`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1894 +msgid "" +"The new :c:func:`Py_SetStandardStreamEncoding` pre-initialization API allows " +"applications embedding the CPython interpreter to reliably force a " +"particular encoding and error handler for the standard streams. (Contributed " +"by Bastien Montagne and Nick Coghlan in :issue:`16129`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1899 +msgid "" +"Most Python C APIs that don't mutate string arguments are now correctly " +"marked as accepting ``const char *`` rather than ``char *``. (Contributed " +"by Serhiy Storchaka in :issue:`1772673`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1903 +msgid "" +"A new shell version of ``python-config`` can be used even when a python " +"interpreter is not available (for example, in cross compilation scenarios)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1906 +msgid "" +":c:func:`PyUnicode_FromFormat` now supports width and precision " +"specifications for ``%s``, ``%A``, ``%U``, ``%V``, ``%S``, and ``%R``. " +"(Contributed by Ysj Ray and Victor Stinner in :issue:`7330`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1910 +msgid "" +"New function :c:func:`PyStructSequence_InitType2` supplements the existing :" +"c:func:`PyStructSequence_InitType` function. The difference is that it " +"returns ``0`` on success and ``-1`` on failure." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1914 +msgid "" +"The CPython source can now be compiled using the address sanity checking " +"features of recent versions of GCC and clang: the false alarms in the small " +"object allocator have been silenced. (Contributed by Dhiru Kholia in :issue:" +"`18596`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1919 +msgid "" +"The Windows build now uses `Address Space Layout Randomization `_ and `Data Execution " +"Prevention `_. " +"(Contributed by Christian Heimes in :issue:`16632`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1924 +msgid "" +"New function :c:func:`PyObject_LengthHint` is the C API equivalent of :func:" +"`operator.length_hint`. (Contributed by Armin Ronacher in :issue:`16148`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1932 +msgid "Other Improvements" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1936 +msgid "" +"The :ref:`python ` command has a new :ref:`option `, ``-I``, which causes it to run in \"isolated mode\", " +"which means that :data:`sys.path` contains neither the script's directory " +"nor the user's ``site-packages`` directory, and all :envvar:`PYTHON*` " +"environment variables are ignored (it implies both ``-s`` and ``-E``). " +"Other restrictions may also be applied in the future, with the goal being to " +"isolate the execution of a script from the user's environment. This is " +"appropriate, for example, when Python is used to run a system script. On " +"most POSIX systems it can and should be used in the ``#!`` line of system " +"scripts. (Contributed by Christian Heimes in :issue:`16499`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1947 +msgid "" +"Tab-completion is now enabled by default in the interactive interpreter on " +"systems that support :mod:`readline`. History is also enabled by default, " +"and is written to (and read from) the file :file:`~/.python-history`. " +"(Contributed by Antoine Pitrou and Éric Araujo in :issue:`5845`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1952 +msgid "" +"Invoking the Python interpreter with ``--version`` now outputs the version " +"to standard output instead of standard error (:issue:`18338`). Similar " +"changes were made to :mod:`argparse` (:issue:`18920`) and other modules that " +"have script-like invocation capabilities (:issue:`18922`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1957 +msgid "" +"The CPython Windows installer now adds ``.py`` to the :envvar:`PATHEXT` " +"variable when extensions are registered, allowing users to run a python " +"script at the windows command prompt by just typing its name without the ``." +"py`` extension. (Contributed by Paul Moore in :issue:`18569`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1962 +msgid "" +"A new ``make`` target `coverage-report `_ will build " +"python, run the test suite, and generate an HTML coverage report for the C " +"codebase using ``gcov`` and `lcov `_." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1968 +msgid "" +"The ``-R`` option to the :ref:`python regression test suite ` now " +"also checks for memory allocation leaks, using :func:`sys." +"getallocatedblocks()`. (Contributed by Antoine Pitrou in :issue:`13390`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1973 +msgid "``python -m`` now works with namespace packages." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1975 +msgid "" +"The :mod:`stat` module is now implemented in C, which means it gets the " +"values for its constants from the C header files, instead of having the " +"values hard-coded in the python module as was previously the case." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1979 +msgid "" +"Loading multiple python modules from a single OS module (``.so``, ``.dll``) " +"now works correctly (previously it silently returned the first python module " +"in the file). (Contributed by Václav Šmilauer in :issue:`16421`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1983 +msgid "" +"A new opcode, :opcode:`LOAD_CLASSDEREF`, has been added to fix a bug in the " +"loading of free variables in class bodies that could be triggered by certain " +"uses of :ref:`__prepare__ `. (Contributed by Benjamin Peterson in :" +"issue:`17853`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1988 +msgid "" +"A number of MemoryError-related crashes were identified and fixed by Victor " +"Stinner using his :pep:`445`-based ``pyfailmalloc`` tool (:issue:`18408`, :" +"issue:`18520`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1992 +msgid "" +"The ``pyvenv`` command now accepts a ``--copies`` option to use copies " +"rather than symlinks even on systems where symlinks are the default. " +"(Contributed by Vinay Sajip in :issue:`18807`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:1996 +msgid "" +"The ``pyvenv`` command also accepts a ``--without-pip`` option to suppress " +"the otherwise-automatic bootstrapping of pip into the virtual environment. " +"(Contributed by Nick Coghlan in :issue:`19552` as part of the :pep:`453` " +"implementation.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2001 +msgid "" +"The encoding name is now optional in the value set for the :envvar:" +"`PYTHONIOENCODING` environment variable. This makes it possible to set just " +"the error handler, without changing the default encoding. (Contributed by " +"Serhiy Storchaka in :issue:`18818`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2006 +msgid "" +"The :mod:`bz2`, :mod:`lzma`, and :mod:`gzip` module ``open`` functions now " +"support ``x`` (exclusive creation) mode. (Contributed by Tim Heaney and " +"Vajrasky Kok in :issue:`19201`, :issue:`19222`, and :issue:`19223`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2012 +msgid "Significant Optimizations" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2014 +msgid "" +"The UTF-32 decoder is now 3x to 4x faster. (Contributed by Serhiy Storchaka " +"in :issue:`14625`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2017 +msgid "" +"The cost of hash collisions for sets is now reduced. Each hash table probe " +"now checks a series of consecutive, adjacent key/hash pairs before " +"continuing to make random probes through the hash table. This exploits " +"cache locality to make collision resolution less expensive. The collision " +"resolution scheme can be described as a hybrid of linear probing and open " +"addressing. The number of additional linear probes defaults to nine. This " +"can be changed at compile-time by defining LINEAR_PROBES to be any value. " +"Set LINEAR_PROBES=0 to turn-off linear probing entirely. (Contributed by " +"Raymond Hettinger in :issue:`18771`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2028 +msgid "" +"The interpreter starts about 30% faster. A couple of measures lead to the " +"speedup. The interpreter loads fewer modules on startup, e.g. the :mod:" +"`re`, :mod:`collections` and :mod:`locale` modules and their dependencies " +"are no longer imported by default. The marshal module has been improved to " +"load compiled Python code faster. (Contributed by Antoine Pitrou, Christian " +"Heimes and Victor Stinner in :issue:`19219`, :issue:`19218`, :issue:" +"`19209`, :issue:`19205` and :issue:`9548`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2036 +msgid "" +":class:`bz2.BZ2File` is now as fast or faster than the Python2 version for " +"most cases. :class:`lzma.LZMAFile` has also been optimized. (Contributed " +"by Serhiy Storchaka and Nadeem Vawda in :issue:`16034`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2040 +msgid "" +":func:`random.getrandbits` is 20%-40% faster for small integers (the most " +"common use case). (Contributed by Serhiy Storchaka in :issue:`16674`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2043 +msgid "" +"By taking advantage of the new storage format for strings, pickling of " +"strings is now significantly faster. (Contributed by Victor Stinner and " +"Antoine Pitrou in :issue:`15596`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2047 +msgid "" +"A performance issue in :meth:`io.FileIO.readall` has been solved. This " +"particularly affects Windows, and significantly speeds up the case of piping " +"significant amounts of data through :mod:`subprocess`. (Contributed by " +"Richard Oudkerk in :issue:`15758`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2052 +msgid "" +":func:`html.escape` is now 10x faster. (Contributed by Matt Bryant in :" +"issue:`18020`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2055 +msgid "" +"On Windows, the native ``VirtualAlloc`` is now used instead of the CRT " +"``malloc`` in ``obmalloc``. Artificial benchmarks show about a 3% memory " +"savings." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2059 +msgid "" +":func:`os.urandom` now uses a lazily-opened persistent file descriptor so as " +"to avoid using many file descriptors when run in parallel from multiple " +"threads. (Contributed by Antoine Pitrou in :issue:`18756`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2069 +msgid "" +"This section covers various APIs and other features that have been " +"deprecated in Python 3.4, and will be removed in Python 3.5 or later. In " +"most (but not all) cases, using the deprecated APIs will produce a :exc:" +"`DeprecationWarning` when the interpreter is run with deprecation warnings " +"enabled (for example, by using ``-Wd``)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2077 +msgid "Deprecations in the Python API" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2079 +msgid "" +"As mentioned in :ref:`whatsnew-pep-451`, a number of :mod:`importlib` " +"methods and functions are deprecated: :meth:`importlib.find_loader` is " +"replaced by :func:`importlib.util.find_spec`; :meth:`importlib.machinery." +"PathFinder.find_module` is replaced by :meth:`importlib.machinery.PathFinder." +"find_spec`; :meth:`importlib.abc.MetaPathFinder.find_module` is replaced by :" +"meth:`importlib.abc.MetaPathFinder.find_spec`; :meth:`importlib.abc." +"PathEntryFinder.find_loader` and :meth:`~importlib.abc.PathEntryFinder." +"find_module` are replaced by :meth:`importlib.abc.PathEntryFinder." +"find_spec`; all of the ``xxxLoader`` ABC ``load_module`` methods (:meth:" +"`importlib.abc.Loader.load_module`, :meth:`importlib.abc.InspectLoader." +"load_module`, :meth:`importlib.abc.FileLoader.load_module`, :meth:`importlib." +"abc.SourceLoader.load_module`) should no longer be implemented, instead " +"loaders should implement an ``exec_module`` method (:meth:`importlib.abc." +"Loader.exec_module`, :meth:`importlib.abc.InspectLoader.exec_module` :meth:" +"`importlib.abc.SourceLoader.exec_module`) and let the import system take " +"care of the rest; and :meth:`importlib.abc.Loader.module_repr`, :meth:" +"`importlib.util.module_for_loader`, :meth:`importlib.util.set_loader`, and :" +"meth:`importlib.util.set_package` are no longer needed because their " +"functions are now handled automatically by the import system." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2104 +msgid "" +"The :mod:`imp` module is pending deprecation. To keep compatibility with " +"Python 2/3 code bases, the module's removal is currently not scheduled." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2107 +msgid "" +"The :mod:`formatter` module is pending deprecation and is slated for removal " +"in Python 3.6." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2110 +msgid "" +"``MD5`` as the default *digestmod* for the :func:`hmac.new` function is " +"deprecated. Python 3.6 will require an explicit digest name or constructor " +"as *digestmod* argument." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2114 +msgid "" +"The internal ``Netrc`` class in the :mod:`ftplib` module has been documented " +"as deprecated in its docstring for quite some time. It now emits a :exc:" +"`DeprecationWarning` and will be removed completely in Python 3.5." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2118 +msgid "" +"The undocumented *endtime* argument to :meth:`subprocess.Popen.wait` should " +"not have been exposed and is hopefully not in use; it is deprecated and will " +"mostly likely be removed in Python 3.5." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2122 +msgid "" +"The *strict* argument of :class:`~html.parser.HTMLParser` is deprecated." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2124 +msgid "" +"The :mod:`plistlib` :func:`~plistlib.readPlist`, :func:`~plistlib." +"writePlist`, :func:`~plistlib.readPlistFromBytes`, and :func:`~plistlib." +"writePlistToBytes` functions are deprecated in favor of the corresponding " +"new functions :func:`~plistlib.load`, :func:`~plistlib.dump`, :func:" +"`~plistlib.loads`, and :func:`~plistlib.dumps`. :func:`~plistlib.Data` is " +"deprecated in favor of just using the :class:`bytes` constructor." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2131 +msgid "" +"The :mod:`sysconfig` key ``SO`` is deprecated, it has been replaced by " +"``EXT_SUFFIX``." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2134 +msgid "" +"The ``U`` mode accepted by various ``open`` functions is deprecated. In " +"Python3 it does not do anything useful, and should be replaced by " +"appropriate uses of :class:`io.TextIOWrapper` (if needed) and its *newline* " +"argument." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2139 +msgid "" +"The *parser* argument of :func:`xml.etree.ElementTree.iterparse` has been " +"deprecated, as has the *html* argument of :func:`~xml.etree.ElementTree." +"XMLParser`. To prepare for the removal of the latter, all arguments to " +"``XMLParser`` should be passed by keyword." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2146 +msgid "Deprecated Features" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2148 +msgid "" +"Running :ref:`idle` with the ``-n`` flag (no subprocess) is deprecated. " +"However, the feature will not be removed until :issue:`18823` is resolved." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2151 +msgid "" +"The site module adding a \"site-python\" directory to sys.path, if it " +"exists, is deprecated (:issue:`19375`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2157 ../Doc/whatsnew/3.5.rst:2351 +#: ../Doc/whatsnew/3.6.rst:1300 +msgid "Removed" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2161 +msgid "Operating Systems No Longer Supported" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2163 +msgid "" +"Support for the following operating systems has been removed from the source " +"and build tools:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2166 +msgid "OS/2 (:issue:`16135`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2167 +msgid "Windows 2000 (changeset e52df05b496a)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2168 +msgid "" +"Windows systems where ``COMSPEC`` points to ``command.com`` (:issue:`14470`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2169 +msgid "VMS (:issue:`16136`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2173 ../Doc/whatsnew/3.5.rst:2354 +#: ../Doc/whatsnew/3.6.rst:1303 +msgid "API and Feature Removals" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2175 ../Doc/whatsnew/3.5.rst:2356 +msgid "" +"The following obsolete and previously deprecated APIs and features have been " +"removed:" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2178 +msgid "" +"The unmaintained ``Misc/TextMate`` and ``Misc/vim`` directories have been " +"removed (see the `devguide `_ for " +"suggestions on what to use instead)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2182 +msgid "" +"The ``SO`` makefile macro is removed (it was replaced by the " +"``SHLIB_SUFFIX`` and ``EXT_SUFFIX`` macros) (:issue:`16754`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2185 +msgid "" +"The ``PyThreadState.tick_counter`` field has been removed; its value has " +"been meaningless since Python 3.2, when the \"new GIL\" was introduced (:" +"issue:`19199`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2189 +msgid "" +"``PyLoader`` and ``PyPycLoader`` have been removed from :mod:`importlib`. " +"(Contributed by Taras Lyapun in :issue:`15641`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2192 +msgid "" +"The *strict* argument to :class:`~http.client.HTTPConnection` and :class:" +"`~http.client.HTTPSConnection` has been removed. HTTP 0.9-style \"Simple " +"Responses\" are no longer supported." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2196 +msgid "" +"The deprecated :mod:`urllib.request.Request` getter and setter methods " +"``add_data``, ``has_data``, ``get_data``, ``get_type``, ``get_host``, " +"``get_selector``, ``set_proxy``, ``get_origin_req_host``, and " +"``is_unverifiable`` have been removed (use direct attribute access instead)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2201 +msgid "" +"Support for loading the deprecated ``TYPE_INT64`` has been removed from :mod:" +"`marshal`. (Contributed by Dan Riti in :issue:`15480`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2204 +msgid "" +":class:`inspect.Signature`: positional-only parameters are now required to " +"have a valid name." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2207 +msgid "" +":meth:`object.__format__` no longer accepts non-empty format strings, it now " +"raises a :exc:`TypeError` instead. Using a non-empty string has been " +"deprecated since Python 3.2. This change has been made to prevent a " +"situation where previously working (but incorrect) code would start failing " +"if an object gained a __format__ method, which means that your code may now " +"raise a :exc:`TypeError` if you are using an ``'s'`` format code with " +"objects that do not have a __format__ method that handles it. See :issue:" +"`7994` for background." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2216 +msgid "" +":meth:`difflib.SequenceMatcher.isbjunk` and :meth:`difflib.SequenceMatcher." +"isbpopular` were deprecated in 3.2, and have now been removed: use ``x in sm." +"bjunk`` and ``x in sm.bpopular``, where *sm* is a :class:`~difflib." +"SequenceMatcher` object (:issue:`13248`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2224 +msgid "Code Cleanups" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2226 +msgid "" +"The unused and undocumented internal ``Scanner`` class has been removed from " +"the :mod:`pydoc` module." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2229 +msgid "" +"The private and effectively unused ``_gestalt`` module has been removed, " +"along with the private :mod:`platform` functions ``_mac_ver_lookup``, " +"``_mac_ver_gstalt``, and ``_bcd2str``, which would only have ever been " +"called on badly broken OSX systems (see :issue:`18393`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2234 +msgid "" +"The hardcoded copies of certain :mod:`stat` constants that were included in " +"the :mod:`tarfile` module namespace have been removed." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2240 +msgid "Porting to Python 3.4" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2247 ../Doc/whatsnew/3.6.rst:1340 +msgid "Changes in 'python' Command Behavior" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2249 +msgid "" +"In a posix shell, setting the :envvar:`PATH` environment variable to an " +"empty value is equivalent to not setting it at all. However, setting :" +"envvar:`PYTHONPATH` to an empty value was *not* equivalent to not setting it " +"at all: setting :envvar:`PYTHONPATH` to an empty value was equivalent to " +"setting it to ``.``, which leads to confusion when reasoning by analogy to " +"how :envvar:`PATH` works. The behavior now conforms to the posix convention " +"for :envvar:`PATH`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2257 +msgid "" +"The [X refs, Y blocks] output of a debug (``--with-pydebug``) build of the " +"CPython interpreter is now off by default. It can be re-enabled using the " +"``-X showrefcount`` option. (Contributed by Ezio Melotti in :issue:`17323`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2261 +msgid "" +"The python command and most stdlib scripts (as well as :mod:`argparse`) now " +"output ``--version`` information to ``stdout`` instead of ``stderr`` (for " +"issue list see :ref:`other-improvements-3.4` above)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2267 ../Doc/whatsnew/3.5.rst:2395 +#: ../Doc/whatsnew/3.6.rst:1350 +msgid "Changes in the Python API" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2269 +msgid "" +"The ABCs defined in :mod:`importlib.abc` now either raise the appropriate " +"exception or return a default value instead of raising :exc:" +"`NotImplementedError` blindly. This will only affect code calling :func:" +"`super` and falling through all the way to the ABCs. For compatibility, " +"catch both :exc:`NotImplementedError` or the appropriate exception as needed." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2275 +msgid "" +"The module type now initializes the :attr:`__package__` and :attr:" +"`__loader__` attributes to ``None`` by default. To determine if these " +"attributes were set in a backwards-compatible fashion, use e.g. " +"``getattr(module, '__loader__', None) is not None``. (:issue:`17115`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2280 +msgid "" +":meth:`importlib.util.module_for_loader` now sets ``__loader__`` and " +"``__package__`` unconditionally to properly support reloading. If this is " +"not desired then you will need to set these attributes manually. You can " +"use :func:`importlib.util.module_to_load` for module management." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2285 +msgid "" +"Import now resets relevant attributes (e.g. ``__name__``, ``__loader__``, " +"``__package__``, ``__file__``, ``__cached__``) unconditionally when " +"reloading. Note that this restores a pre-3.3 behavior in that it means a " +"module is re-found when re-loaded (:issue:`19413`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2290 +msgid "" +"Frozen packages no longer set ``__path__`` to a list containing the package " +"name, they now set it to an empty list. The previous behavior could cause " +"the import system to do the wrong thing on submodule imports if there was " +"also a directory with the same name as the frozen package. The correct way " +"to determine if a module is a package or not is to use ``hasattr(module, " +"'__path__')`` (:issue:`18065`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2297 +msgid "" +"Frozen modules no longer define a ``__file__`` attribute. It's semantically " +"incorrect for frozen modules to set the attribute as they are not loaded " +"from any explicit location. If you must know that a module comes from frozen " +"code then you can see if the module's ``__spec__.location`` is set to " +"``'frozen'``, check if the loader is a subclass of :class:`importlib." +"machinery.FrozenImporter`, or if Python 2 compatibility is necessary you can " +"use :func:`imp.is_frozen`." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2305 +msgid "" +":func:`py_compile.compile` now raises :exc:`FileExistsError` if the file " +"path it would write to is a symlink or a non-regular file. This is to act as " +"a warning that import will overwrite those files with a regular file " +"regardless of what type of file path they were originally." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2310 +msgid "" +":meth:`importlib.abc.SourceLoader.get_source` no longer raises :exc:" +"`ImportError` when the source code being loaded triggers a :exc:" +"`SyntaxError` or :exc:`UnicodeDecodeError`. As :exc:`ImportError` is meant " +"to be raised only when source code cannot be found but it should, it was " +"felt to be over-reaching/overloading of that meaning when the source code is " +"found but improperly structured. If you were catching ImportError before and " +"wish to continue to ignore syntax or decoding issues, catch all three " +"exceptions now." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2319 +msgid "" +":func:`functools.update_wrapper` and :func:`functools.wraps` now correctly " +"set the ``__wrapped__`` attribute to the function being wrapped, even if " +"that function also had its ``__wrapped__`` attribute set. This means " +"``__wrapped__`` attributes now correctly link a stack of decorated functions " +"rather than every ``__wrapped__`` attribute in the chain referring to the " +"innermost function. Introspection libraries that assumed the previous " +"behaviour was intentional can use :func:`inspect.unwrap` to access the first " +"function in the chain that has no ``__wrapped__`` attribute." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2329 +msgid "" +":func:`inspect.getfullargspec` has been reimplemented on top of :func:" +"`inspect.signature` and hence handles a much wider variety of callable " +"objects than it did in the past. It is expected that additional builtin and " +"extension module callables will gain signature metadata over the course of " +"the Python 3.4 series. Code that assumes that :func:`inspect.getfullargspec` " +"will fail on non-Python callables may need to be adjusted accordingly." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2337 +msgid "" +":class:`importlib.machinery.PathFinder` now passes on the current working " +"directory to objects in :data:`sys.path_hooks` for the empty string. This " +"results in :data:`sys.path_importer_cache` never containing ``''``, thus " +"iterating through :data:`sys.path_importer_cache` based on :data:`sys.path` " +"will not find all keys. A module's ``__file__`` when imported in the current " +"working directory will also now have an absolute path, including when using " +"``-m`` with the interpreter (except for ``__main__.__file__`` when a script " +"has been executed directly using a relative path) (Contributed by Brett " +"Cannon in :issue:`18416`). is specified on the command-line) (:issue:" +"`18416`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2348 +msgid "" +"The removal of the *strict* argument to :class:`~http.client.HTTPConnection` " +"and :class:`~http.client.HTTPSConnection` changes the meaning of the " +"remaining arguments if you are specifying them positionally rather than by " +"keyword. If you've been paying attention to deprecation warnings your code " +"should already be specifying any additional arguments via keywords." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2354 +msgid "" +"Strings between ``from __future__ import ...`` statements now *always* raise " +"a :exc:`SyntaxError`. Previously if there was no leading docstring, an " +"interstitial string would sometimes be ignored. This brings CPython into " +"compliance with the language spec; Jython and PyPy already were. (:issue:" +"`17434`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2360 +msgid "" +":meth:`ssl.SSLSocket.getpeercert` and :meth:`ssl.SSLSocket.do_handshake` now " +"raise an :exc:`OSError` with ``ENOTCONN`` when the ``SSLSocket`` is not " +"connected, instead of the previous behavior of raising an :exc:" +"`AttributeError`. In addition, :meth:`~ssl.SSLSocket.getpeercert` will " +"raise a :exc:`ValueError` if the handshake has not yet been done." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2366 +msgid "" +":func:`base64.b32decode` now raises a :exc:`binascii.Error` when the input " +"string contains non-b32-alphabet characters, instead of a :exc:`TypeError`. " +"This particular :exc:`TypeError` was missed when the other :exc:`TypeError`" +"\\ s were converted. (Contributed by Serhiy Storchaka in :issue:`18011`.) " +"Note: this change was also inadvertently applied in Python 3.3.3." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2373 +msgid "" +"The :attr:`~cgi.FieldStorage.file` attribute is now automatically closed " +"when the creating :class:`cgi.FieldStorage` instance is garbage collected. " +"If you were pulling the file object out separately from the :class:`cgi." +"FieldStorage` instance and not keeping the instance alive, then you should " +"either store the entire :class:`cgi.FieldStorage` instance or read the " +"contents of the file before the :class:`cgi.FieldStorage` instance is " +"garbage collected." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2380 +msgid "" +"Calling ``read`` or ``write`` on a closed SSL socket now raises an " +"informative :exc:`ValueError` rather than the previous more mysterious :exc:" +"`AttributeError` (:issue:`9177`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2384 +msgid "" +":meth:`slice.indices` no longer produces an :exc:`OverflowError` for huge " +"values. As a consequence of this fix, :meth:`slice.indices` now raises a :" +"exc:`ValueError` if given a negative length; previously it returned nonsense " +"values (:issue:`14794`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2389 +msgid "" +"The :class:`complex` constructor, unlike the :mod:`cmath` functions, was " +"incorrectly accepting :class:`float` values if an object's ``__complex__`` " +"special method returned one. This now raises a :exc:`TypeError`. (:issue:" +"`16290`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2394 +msgid "" +"The :class:`int` constructor in 3.2 and 3.3 erroneously accepts :class:" +"`float` values for the *base* parameter. It is unlikely anyone was doing " +"this, but if so, it will now raise a :exc:`TypeError` (:issue:`16772`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2398 +msgid "" +"Defaults for keyword-only arguments are now evaluated *after* defaults for " +"regular keyword arguments, instead of before. Hopefully no one wrote any " +"code that depends on the previous buggy behavior (:issue:`16967`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2402 +msgid "" +"Stale thread states are now cleared after :func:`~os.fork`. This may cause " +"some system resources to be released that previously were incorrectly kept " +"perpetually alive (for example, database connections kept in thread-local " +"storage). (:issue:`17094`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2407 +msgid "" +"Parameter names in ``__annotations__`` dicts are now mangled properly, " +"similarly to ``__kwdefaults__``. (Contributed by Yury Selivanov in :issue:" +"`20625`.)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2411 +msgid "" +":attr:`hashlib.hash.name` now always returns the identifier in lower case. " +"Previously some builtin hashes had uppercase names, but now that it is a " +"formal public interface the naming has been made consistent (:issue:`18532`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2415 +msgid "" +"Because :mod:`unittest.TestSuite` now drops references to tests after they " +"are run, test harnesses that re-use a :class:`~unittest.TestSuite` to re-run " +"a set of tests may fail. Test suites should not be re-used in this fashion " +"since it means state is retained between test runs, breaking the test " +"isolation that :mod:`unittest` is designed to provide. However, if the lack " +"of isolation is considered acceptable, the old behavior can be restored by " +"creating a :mod:`~unittest.TestSuite` subclass that defines a " +"``_removeTestAtIndex`` method that does nothing (see :meth:`.TestSuite." +"__iter__`) (:issue:`11798`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2425 +msgid "" +":mod:`unittest` now uses :mod:`argparse` for command line parsing. There " +"are certain invalid command forms that used to work that are no longer " +"allowed; in theory this should not cause backward compatibility issues since " +"the disallowed command forms didn't make any sense and are unlikely to be in " +"use." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2430 +msgid "" +"The :func:`re.split`, :func:`re.findall`, and :func:`re.sub` functions, and " +"the :meth:`~re.match.group` and :meth:`~re.match.groups` methods of " +"``match`` objects now always return a *bytes* object when the string to be " +"matched is a :term:`bytes-like object`. Previously the return type matched " +"the input type, so if your code was depending on the return value being, " +"say, a ``bytearray``, you will need to change your code." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2437 +msgid "" +":mod:`audioop` functions now raise an error immediately if passed string " +"input, instead of failing randomly later on (:issue:`16685`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2440 +msgid "" +"The new *convert_charrefs* argument to :class:`~html.parser.HTMLParser` " +"currently defaults to ``False`` for backward compatibility, but will " +"eventually be changed to default to ``True``. It is recommended that you " +"add this keyword, with the appropriate value, to any :class:`~html.parser." +"HTMLParser` calls in your code (:issue:`13633`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2446 +msgid "" +"Since the *digestmod* argument to the :func:`hmac.new` function will in the " +"future have no default, all calls to :func:`hmac.new` should be changed to " +"explicitly specify a *digestmod* (:issue:`17276`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2450 +msgid "" +"Calling :func:`sysconfig.get_config_var` with the ``SO`` key, or looking " +"``SO`` up in the results of a call to :func:`sysconfig.get_config_vars` is " +"deprecated. This key should be replaced by ``EXT_SUFFIX`` or " +"``SHLIB_SUFFIX``, depending on the context (:issue:`19555`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2455 +msgid "" +"Any calls to ``open`` functions that specify ``U`` should be modified. ``U`` " +"is ineffective in Python3 and will eventually raise an error if used. " +"Depending on the function, the equivalent of its old Python2 behavior can be " +"achieved using either a *newline* argument, or if necessary by wrapping the " +"stream in :mod:`~io.TextIOWrapper` to use its *newline* argument (:issue:" +"`15204`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2462 +msgid "" +"If you use ``pyvenv`` in a script and desire that pip *not* be installed, " +"you must add ``--without-pip`` to your command invocation." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2466 +msgid "" +"The default behavior of :func:`json.dump` and :func:`json.dumps` when an " +"indent is specified has changed: it no longer produces trailing spaces after " +"the item separating commas at the ends of lines. This will matter only if " +"you have tests that are doing white-space-sensitive comparisons of such " +"output (:issue:`16333`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2472 +msgid "" +":mod:`doctest` now looks for doctests in extension module ``__doc__`` " +"strings, so if your doctest test discovery includes extension modules that " +"have things that look like doctests in them you may see test failures you've " +"never seen before when running your tests (:issue:`3158`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2477 +msgid "" +"The :mod:`collections.abc` module has been slightly refactored as part of " +"the Python startup improvements. As a consequence of this, it is no longer " +"the case that importing :mod:`collections` automatically imports :mod:" +"`collections.abc`. If your program depended on the (undocumented) implicit " +"import, you will need to add an explicit ``import collections.abc`` (:issue:" +"`20784`)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2486 ../Doc/whatsnew/3.5.rst:2512 +#: ../Doc/whatsnew/3.6.rst:1467 +msgid "Changes in the C API" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2488 +msgid "" +":c:func:`PyEval_EvalFrameEx`, :c:func:`PyObject_Repr`, and :c:func:" +"`PyObject_Str`, along with some other internal C APIs, now include a " +"debugging assertion that ensures they are not used in situations where they " +"may silently discard a currently active exception. In cases where discarding " +"the active exception is expected and desired (for example, because it has " +"already been saved locally with :c:func:`PyErr_Fetch` or is being " +"deliberately replaced with a different exception), an explicit :c:func:" +"`PyErr_Clear` call will be needed to avoid triggering the assertion when " +"invoking these operations (directly or indirectly) and running against a " +"version of Python that is compiled with assertions enabled." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2500 +msgid "" +":c:func:`PyErr_SetImportError` now sets :exc:`TypeError` when its **msg** " +"argument is not set. Previously only ``NULL`` was returned with no exception " +"set." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2504 +msgid "" +"The result of the :c:data:`PyOS_ReadlineFunctionPointer` callback must now " +"be a string allocated by :c:func:`PyMem_RawMalloc` or :c:func:" +"`PyMem_RawRealloc`, or *NULL* if an error occurred, instead of a string " +"allocated by :c:func:`PyMem_Malloc` or :c:func:`PyMem_Realloc` (:issue:" +"`16742`)" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2510 +msgid "" +":c:func:`PyThread_set_key_value` now always set the value. In Python 3.3, " +"the function did nothing if the key already exists (if the current value is " +"a non-NULL pointer)." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2514 +msgid "" +"The ``f_tstate`` (thread state) field of the :c:type:`PyFrameObject` " +"structure has been removed to fix a bug: see :issue:`14432` for the " +"rationale." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2519 +msgid "Changed in 3.4.3" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2524 +msgid "" +"PEP 476: Enabling certificate verification by default for stdlib http clients" +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2526 +msgid "" +":mod:`http.client` and modules which use it, such as :mod:`urllib.request` " +"and :mod:`xmlrpc.client`, will now verify that the server presents a " +"certificate which is signed by a CA in the platform trust store and whose " +"hostname matches the hostname being requested by default, significantly " +"improving security for many applications." +msgstr "" + +#: ../Doc/whatsnew/3.4.rst:2532 +msgid "" +"For applications which require the old previous behavior, they can pass an " +"alternate context::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:3 +msgid "What's New In Python 3.5" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:5 +msgid "Elvis Pranskevichus , Yury Selivanov " +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:47 +msgid "" +"This article explains the new features in Python 3.5, compared to 3.4. " +"Python 3.5 was released on September 13, 2015.  See the `changelog `_ for a full list of changes." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:54 +msgid ":pep:`478` - Python 3.5 Release Schedule" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:62 +msgid "" +":ref:`PEP 492 `, coroutines with async and await syntax." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:63 +msgid "" +":ref:`PEP 465 `, a new matrix multiplication operator: ``a " +"@ b``." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:64 +msgid "" +":ref:`PEP 448 `, additional unpacking generalizations." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:69 +msgid ":mod:`typing`: :ref:`PEP 484 -- Type Hints `." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:70 +msgid "" +":mod:`zipapp`: :ref:`PEP 441 Improving Python ZIP Application Support " +"`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:76 +msgid "" +"``bytes % args``, ``bytearray % args``: :ref:`PEP 461 ` -- " +"Adding ``%`` formatting to bytes and bytearray." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:79 +msgid "" +"New :meth:`bytes.hex`, :meth:`bytearray.hex` and :meth:`memoryview.hex` " +"methods. (Contributed by Arnon Yaari in :issue:`9951`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:82 +msgid "" +":class:`memoryview` now supports tuple indexing (including multi-" +"dimensional). (Contributed by Antoine Pitrou in :issue:`23632`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:85 +msgid "" +"Generators have a new ``gi_yieldfrom`` attribute, which returns the object " +"being iterated by ``yield from`` expressions. (Contributed by Benno Leslie " +"and Yury Selivanov in :issue:`24450`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:89 +msgid "" +"A new :exc:`RecursionError` exception is now raised when maximum recursion " +"depth is reached. (Contributed by Georg Brandl in :issue:`19235`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:96 +msgid "" +"When the ``LC_TYPE`` locale is the POSIX locale (``C`` locale), :py:data:" +"`sys.stdin` and :py:data:`sys.stdout` now use the ``surrogateescape`` error " +"handler, instead of the ``strict`` error handler. (Contributed by Victor " +"Stinner in :issue:`19977`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:101 +msgid "" +"``.pyo`` files are no longer used and have been replaced by a more flexible " +"scheme that includes the optimization level explicitly in ``.pyc`` name. " +"(See :ref:`PEP 488 overview `.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:105 +msgid "" +"Builtin and extension modules are now initialized in a multi-phase process, " +"which is similar to how Python modules are loaded. (See :ref:`PEP 489 " +"overview `.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:110 +msgid "Significant improvements in the standard library:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:112 +msgid "" +":class:`collections.OrderedDict` is now :ref:`implemented in C `, which makes it 4 to 100 times faster." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:116 +msgid "" +"The :mod:`ssl` module gained :ref:`support for Memory BIO `, which decouples SSL protocol handling from network IO." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:120 +msgid "" +"The new :func:`os.scandir` function provides a :ref:`better and " +"significantly faster way ` of directory traversal." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:124 +msgid "" +":func:`functools.lru_cache` has been mostly :ref:`reimplemented in C " +"`, yielding much better performance." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:128 +msgid "" +"The new :func:`subprocess.run` function provides a :ref:`streamlined way to " +"run subprocesses `." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:131 +msgid "" +"The :mod:`traceback` module has been significantly :ref:`enhanced ` for improved performance and developer convenience." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:138 +msgid "" +"SSLv3 is now disabled throughout the standard library. It can still be " +"enabled by instantiating a :class:`ssl.SSLContext` manually. (See :issue:" +"`22638` for more details; this change was backported to CPython 3.4 and 2.7.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:143 +msgid "" +"HTTP cookie parsing is now stricter, in order to protect against potential " +"injection attacks. (Contributed by Antoine Pitrou in :issue:`22796`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:148 ../Doc/whatsnew/3.6.rst:96 +msgid "Windows improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:150 +msgid "" +"A new installer for Windows has replaced the old MSI. See :ref:`using-on-" +"windows` for more information." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:153 +msgid "" +"Windows builds now use Microsoft Visual C++ 14.0, and extension modules " +"should use the same." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:168 +msgid "PEP 492 - Coroutines with async and await syntax" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:170 +msgid "" +":pep:`492` greatly improves support for asynchronous programming in Python " +"by adding :term:`awaitable objects `, :term:`coroutine functions " +"`, :term:`asynchronous iteration `, and :term:`asynchronous context managers `." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:176 +msgid "" +"Coroutine functions are declared using the new :keyword:`async def` syntax::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:181 +msgid "" +"Inside a coroutine function, the new :keyword:`await` expression can be used " +"to suspend coroutine execution until the result is available. Any object " +"can be *awaited*, as long as it implements the :term:`awaitable` protocol by " +"defining the :meth:`__await__` method." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:186 +msgid "" +"PEP 492 also adds :keyword:`async for` statement for convenient iteration " +"over asynchronous iterables." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:189 +msgid "An example of a rudimentary HTTP client written using the new syntax::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:215 +msgid "" +"Similarly to asynchronous iteration, there is a new syntax for asynchronous " +"context managers. The following script::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:235 +msgid "will output::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:244 +msgid "" +"Note that both :keyword:`async for` and :keyword:`async with` can only be " +"used inside a coroutine function declared with :keyword:`async def`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:247 +msgid "" +"Coroutine functions are intended to be run inside a compatible event loop, " +"such as the :ref:`asyncio loop `." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:253 +msgid "" +"Starting with CPython 3.5.2, ``__aiter__`` can directly return :term:" +"`asynchronous iterators `. Returning an :term:" +"`awaitable` object will result in a :exc:`PendingDeprecationWarning`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:259 +msgid "See more details in the :ref:`async-iterators` documentation section." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:265 +msgid ":pep:`492` -- Coroutines with async and await syntax" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:266 +msgid "PEP written and implemented by Yury Selivanov." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:272 +msgid "PEP 465 - A dedicated infix operator for matrix multiplication" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:274 +msgid "" +":pep:`465` adds the ``@`` infix operator for matrix multiplication. " +"Currently, no builtin Python types implement the new operator, however, it " +"can be implemented by defining :meth:`__matmul__`, :meth:`__rmatmul__`, and :" +"meth:`__imatmul__` for regular, reflected, and in-place matrix " +"multiplication. The semantics of these methods is similar to that of " +"methods defining other infix arithmetic operators." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:281 +msgid "" +"Matrix multiplication is a notably common operation in many fields of " +"mathematics, science, engineering, and the addition of ``@`` allows writing " +"cleaner code::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:287 +msgid "instead of::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:292 +msgid "NumPy 1.10 has support for the new operator::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:312 +msgid ":pep:`465` -- A dedicated infix operator for matrix multiplication" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:313 +msgid "PEP written by Nathaniel J. Smith; implemented by Benjamin Peterson." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:319 +msgid "PEP 448 - Additional Unpacking Generalizations" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:321 +msgid "" +":pep:`448` extends the allowed uses of the ``*`` iterable unpacking operator " +"and ``**`` dictionary unpacking operator. It is now possible to use an " +"arbitrary number of unpackings in :ref:`function calls `::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:335 +msgid "" +"Similarly, tuple, list, set, and dictionary displays allow multiple " +"unpackings (see :ref:`exprlists` and :ref:`dict`)::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:353 +msgid ":pep:`448` -- Additional Unpacking Generalizations" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:353 +msgid "" +"PEP written by Joshua Landau; implemented by Neil Girdhar, Thomas Wouters, " +"and Joshua Landau." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:360 +msgid "PEP 461 - percent formatting support for bytes and bytearray" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:362 +msgid "" +":pep:`461` adds support for the ``%`` :ref:`interpolation operator ` to :class:`bytes` and :class:`bytearray`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:366 +msgid "" +"While interpolation is usually thought of as a string operation, there are " +"cases where interpolation on ``bytes`` or ``bytearrays`` makes sense, and " +"the work needed to make up for this missing functionality detracts from the " +"overall readability of the code. This issue is particularly important when " +"dealing with wire format protocols, which are often a mixture of binary and " +"ASCII compatible text." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:373 ../Doc/whatsnew/3.5.rst:1848 +msgid "Examples::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:381 +msgid "" +"Unicode is not allowed for ``%b``, but it is accepted by ``%a`` (equivalent " +"of ``repr(obj).encode('ascii', 'backslashreplace')``)::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:392 +msgid "" +"Note that ``%s`` and ``%r`` conversion types, although supported, should " +"only be used in codebases that need compatibility with Python 2." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:398 +msgid ":pep:`461` -- Adding % formatting to bytes and bytearray" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:398 +msgid "" +"PEP written by Ethan Furman; implemented by Neil Schemenauer and Ethan " +"Furman." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:405 +msgid "PEP 484 - Type Hints" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:407 +msgid "" +"Function annotation syntax has been a Python feature since version 3.0 (:pep:" +"`3107`), however the semantics of annotations has been left undefined." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:410 +msgid "" +"Experience has shown that the majority of function annotation uses were to " +"provide type hints to function parameters and return values. It became " +"evident that it would be beneficial for Python users, if the standard " +"library included the base definitions and tools for type annotations." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:415 +msgid "" +":pep:`484` introduces a :term:`provisional module ` to " +"provide these standard definitions and tools, along with some conventions " +"for situations where annotations are not available." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:419 +msgid "" +"For example, here is a simple function whose argument and return type are " +"declared in the annotations::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:425 +msgid "" +"While these annotations are available at runtime through the usual :attr:" +"`__annotations__` attribute, *no automatic type checking happens at " +"runtime*. Instead, it is assumed that a separate off-line type checker (e." +"g. `mypy `_) will be used for on-demand source code " +"analysis." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:431 +msgid "" +"The type system supports unions, generic types, and a special type named :" +"class:`~typing.Any` which is consistent with (i.e. assignable to and from) " +"all types." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:437 +msgid ":mod:`typing` module documentation" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:439 +msgid ":pep:`484` -- Type Hints" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:439 +msgid "" +"PEP written by Guido van Rossum, Jukka Lehtosalo, and Łukasz Langa; " +"implemented by Guido van Rossum." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:441 +msgid ":pep:`483` -- The Theory of Type Hints" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:442 +msgid "PEP written by Guido van Rossum" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:448 +msgid "" +"PEP 471 - os.scandir() function -- a better and faster directory iterator" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:450 +msgid "" +":pep:`471` adds a new directory iteration function, :func:`os.scandir`, to " +"the standard library. Additionally, :func:`os.walk` is now implemented " +"using ``scandir``, which makes it 3 to 5 times faster on POSIX systems and 7 " +"to 20 times faster on Windows systems. This is largely achieved by greatly " +"reducing the number of calls to :func:`os.stat` required to walk a directory " +"tree." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:457 +msgid "" +"Additionally, ``scandir`` returns an iterator, as opposed to returning a " +"list of file names, which improves memory efficiency when iterating over " +"very large directories." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:461 +msgid "" +"The following example shows a simple use of :func:`os.scandir` to display " +"all the files (excluding directories) in the given *path* that don't start " +"with ``'.'``. The :meth:`entry.is_file() ` call will " +"generally not make an additional system call::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:472 +msgid "" +":pep:`471` -- os.scandir() function -- a better and faster directory iterator" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:473 +msgid "" +"PEP written and implemented by Ben Hoyt with the help of Victor Stinner." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:479 +msgid "PEP 475: Retry system calls failing with EINTR" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:481 +msgid "" +"An :py:data:`errno.EINTR` error code is returned whenever a system call, " +"that is waiting for I/O, is interrupted by a signal. Previously, Python " +"would raise :exc:`InterruptedError` in such cases. This meant that, when " +"writing a Python application, the developer had two choices:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:486 +msgid "Ignore the ``InterruptedError``." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:487 +msgid "" +"Handle the ``InterruptedError`` and attempt to restart the interrupted " +"system call at every call site." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:490 +msgid "" +"The first option makes an application fail intermittently. The second option " +"adds a large amount of boilerplate that makes the code nearly unreadable. " +"Compare::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:496 +msgid "and::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:505 +msgid "" +":pep:`475` implements automatic retry of system calls on ``EINTR``. This " +"removes the burden of dealing with ``EINTR`` or :exc:`InterruptedError` in " +"user code in most situations and makes Python programs, including the " +"standard library, more robust. Note that the system call is only retried if " +"the signal handler does not raise an exception." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:512 +msgid "" +"Below is a list of functions which are now retried when interrupted by a " +"signal:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:515 +msgid ":func:`open` and :func:`io.open`;" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:517 +msgid "functions of the :mod:`faulthandler` module;" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:519 +msgid "" +":mod:`os` functions: :func:`~os.fchdir`, :func:`~os.fchmod`, :func:`~os." +"fchown`, :func:`~os.fdatasync`, :func:`~os.fstat`, :func:`~os.fstatvfs`, :" +"func:`~os.fsync`, :func:`~os.ftruncate`, :func:`~os.mkfifo`, :func:`~os." +"mknod`, :func:`~os.open`, :func:`~os.posix_fadvise`, :func:`~os." +"posix_fallocate`, :func:`~os.pread`, :func:`~os.pwrite`, :func:`~os.read`, :" +"func:`~os.readv`, :func:`~os.sendfile`, :func:`~os.wait3`, :func:`~os." +"wait4`, :func:`~os.wait`, :func:`~os.waitid`, :func:`~os.waitpid`, :func:" +"`~os.write`, :func:`~os.writev`;" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:529 +msgid "" +"special cases: :func:`os.close` and :func:`os.dup2` now ignore :py:data:" +"`~errno.EINTR` errors; the syscall is not retried (see the PEP for the " +"rationale);" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:533 +msgid "" +":mod:`select` functions: :func:`devpoll.poll() `, :func:" +"`epoll.poll() `, :func:`kqueue.control() `, :func:`poll.poll() `, :func:`~select.select`;" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:538 +msgid "" +"methods of the :class:`~socket.socket` class: :meth:`~socket.socket." +"accept`, :meth:`~socket.socket.connect` (except for non-blocking sockets), :" +"meth:`~socket.socket.recv`, :meth:`~socket.socket.recvfrom`, :meth:`~socket." +"socket.recvmsg`, :meth:`~socket.socket.send`, :meth:`~socket.socket." +"sendall`, :meth:`~socket.socket.sendmsg`, :meth:`~socket.socket.sendto`;" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:545 +msgid ":func:`signal.sigtimedwait` and :func:`signal.sigwaitinfo`;" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:547 +msgid ":func:`time.sleep`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:552 +msgid ":pep:`475` -- Retry system calls failing with EINTR" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:552 +msgid "" +"PEP and implementation written by Charles-François Natali and Victor " +"Stinner, with the help of Antoine Pitrou (the French connection)." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:559 +msgid "PEP 479: Change StopIteration handling inside generators" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:561 +msgid "" +"The interaction of generators and :exc:`StopIteration` in Python 3.4 and " +"earlier was sometimes surprising, and could conceal obscure bugs. " +"Previously, ``StopIteration`` raised accidentally inside a generator " +"function was interpreted as the end of the iteration by the loop construct " +"driving the generator." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:567 +msgid "" +":pep:`479` changes the behavior of generators: when a ``StopIteration`` " +"exception is raised inside a generator, it is replaced with a :exc:" +"`RuntimeError` before it exits the generator frame. The main goal of this " +"change is to ease debugging in the situation where an unguarded :func:`next` " +"call raises ``StopIteration`` and causes the iteration controlled by the " +"generator to terminate silently. This is particularly pernicious in " +"combination with the ``yield from`` construct." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:575 +msgid "" +"This is a backwards incompatible change, so to enable the new behavior, a :" +"term:`__future__` import is necessary::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:595 +msgid "" +"Without a ``__future__`` import, a :exc:`PendingDeprecationWarning` will be " +"raised whenever a ``StopIteration`` exception is raised inside a generator." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:601 +msgid ":pep:`479` -- Change StopIteration handling inside generators" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:601 +msgid "" +"PEP written by Chris Angelico and Guido van Rossum. Implemented by Chris " +"Angelico, Yury Selivanov and Nick Coghlan." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:608 +msgid "PEP 485: A function for testing approximate equality" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:610 +msgid "" +":pep:`485` adds the :func:`math.isclose` and :func:`cmath.isclose` functions " +"which tell whether two values are approximately equal or \"close\" to each " +"other. Whether or not two values are considered close is determined " +"according to given absolute and relative tolerances. Relative tolerance is " +"the maximum allowed difference between ``isclose`` arguments, relative to " +"the larger absolute value::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:625 +msgid "" +"It is also possible to compare two values using absolute tolerance, which " +"must be a non-negative value::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:639 +msgid ":pep:`485` -- A function for testing approximate equality" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:639 +msgid "" +"PEP written by Christopher Barker; implemented by Chris Barker and Tal Einat." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:646 +msgid "PEP 486: Make the Python Launcher aware of virtual environments" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:648 +msgid "" +":pep:`486` makes the Windows launcher (see :pep:`397`) aware of an active " +"virtual environment. When the default interpreter would be used and the " +"``VIRTUAL_ENV`` environment variable is set, the interpreter in the virtual " +"environment will be used." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:655 +msgid ":pep:`486` -- Make the Python Launcher aware of virtual environments" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:656 +msgid "PEP written and implemented by Paul Moore." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:662 +msgid "PEP 488: Elimination of PYO files" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:664 +msgid "" +":pep:`488` does away with the concept of ``.pyo`` files. This means that ``." +"pyc`` files represent both unoptimized and optimized bytecode. To prevent " +"the need to constantly regenerate bytecode files, ``.pyc`` files now have an " +"optional ``opt-`` tag in their name when the bytecode is optimized. This has " +"the side-effect of no more bytecode file name clashes when running under " +"either :option:`-O` or :option:`-OO`. Consequently, bytecode files generated " +"from :option:`-O`, and :option:`-OO` may now exist simultaneously. :func:" +"`importlib.util.cache_from_source` has an updated API to help with this " +"change." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:676 +msgid ":pep:`488` -- Elimination of PYO files" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:677 +msgid "PEP written and implemented by Brett Cannon." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:683 +msgid "PEP 489: Multi-phase extension module initialization" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:685 +msgid "" +":pep:`489` updates extension module initialization to take advantage of the " +"two step module loading mechanism introduced by :pep:`451` in Python 3.4." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:688 +msgid "" +"This change brings the import semantics of extension modules that opt-in to " +"using the new mechanism much closer to those of Python source and bytecode " +"modules, including the ability to use any valid identifier as a module name, " +"rather than being restricted to ASCII." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:696 +msgid ":pep:`489` -- Multi-phase extension module initialization" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:696 +msgid "" +"PEP written by Petr Viktorin, Stefan Behnel, and Nick Coghlan; implemented " +"by Petr Viktorin." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:705 +msgid "" +"Added the ``\"namereplace\"`` error handlers. The ``\"backslashreplace\"`` " +"error handlers now work with decoding and translating. (Contributed by " +"Serhiy Storchaka in :issue:`19676` and :issue:`22286`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:709 +msgid "" +"The :option:`-b` option now affects comparisons of :class:`bytes` with :" +"class:`int`. (Contributed by Serhiy Storchaka in :issue:`23681`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:712 +msgid "" +"New Kazakh ``kz1048`` and Tajik ``koi8_t`` :ref:`codecs `. (Contributed by Serhiy Storchaka in :issue:`22682` and :issue:" +"`22681`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:715 +msgid "" +"Property docstrings are now writable. This is especially useful for :func:" +"`collections.namedtuple` docstrings. (Contributed by Berker Peksag in :issue:" +"`24064`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:719 +msgid "" +"Circular imports involving relative imports are now supported. (Contributed " +"by Brett Cannon and Antoine Pitrou in :issue:`17636`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:727 ../Doc/whatsnew/3.6.rst:980 +msgid "typing" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:729 +msgid "" +"The new :mod:`typing` :term:`provisional ` module provides " +"standard definitions and tools for function type annotations. See :ref:`Type " +"Hints ` for more information." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:736 +msgid "zipapp" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:738 +msgid "" +"The new :mod:`zipapp` module (specified in :pep:`441`) provides an API and " +"command line tool for creating executable Python Zip Applications, which " +"were introduced in Python 2.6 in :issue:`1739468`, but which were not well " +"publicized, either at the time or since." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:743 +msgid "" +"With the new module, bundling your application is as simple as putting all " +"the files, including a ``__main__.py`` file, into a directory ``myapp`` and " +"running:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:752 +msgid "" +"The module implementation has been contributed by Paul Moore in :issue:" +"`23491`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:757 +msgid ":pep:`441` -- Improving Python ZIP Application Support" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:766 +msgid "" +"The :class:`~argparse.ArgumentParser` class now allows disabling :ref:" +"`abbreviated usage ` of long options by setting :ref:" +"`allow_abbrev` to ``False``. (Contributed by Jonathan Paugh, Steven " +"Bethard, paul j3 and Daniel Eriksson in :issue:`14910`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:775 +msgid "" +"Since the :mod:`asyncio` module is :term:`provisional `, " +"all changes introduced in Python 3.5 have also been backported to Python 3.4." +"x." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:778 +msgid "Notable changes in the :mod:`asyncio` module since Python 3.4.0:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:780 +msgid "" +"New debugging APIs: :meth:`loop.set_debug() ` and :meth:`loop.get_debug() ` " +"methods. (Contributed by Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:784 +msgid "" +"The proactor event loop now supports SSL. (Contributed by Antoine Pitrou and " +"Victor Stinner in :issue:`22560`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:787 +msgid "" +"A new :meth:`loop.is_closed() ` method to " +"check if the event loop is closed. (Contributed by Victor Stinner in :issue:" +"`21326`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:791 +msgid "" +"A new :meth:`loop.create_task() ` to " +"conveniently create and schedule a new :class:`~asyncio.Task` for a " +"coroutine. The ``create_task`` method is also used by all asyncio functions " +"that wrap coroutines into tasks, such as :func:`asyncio.wait`, :func:" +"`asyncio.gather`, etc. (Contributed by Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:798 +msgid "" +"A new :meth:`transport.get_write_buffer_limits() ` method to inquire for *high-* and *low-* water " +"limits of the flow control. (Contributed by Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:803 +msgid "" +"The :func:`~asyncio.async` function is deprecated in favor of :func:" +"`~asyncio.ensure_future`. (Contributed by Yury Selivanov.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:807 +msgid "" +"New :meth:`loop.set_task_factory() ` and :meth:`loop.get_task_factory() ` methods to customize the task factory " +"that :meth:`loop.create_task() ` method " +"uses. (Contributed by Yury Selivanov.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:814 +msgid "" +"New :meth:`Queue.join() ` and :meth:`Queue.task_done() " +"` queue methods. (Contributed by Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:818 +msgid "" +"The ``JoinableQueue`` class was removed, in favor of the :class:`asyncio." +"Queue` class. (Contributed by Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:822 +msgid "Updates in 3.5.1:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:824 ../Doc/whatsnew/3.6.rst:599 +msgid "" +"The :func:`~asyncio.ensure_future` function and all functions that use it, " +"such as :meth:`loop.run_until_complete() `, now accept all kinds of :term:`awaitable objects " +"`. (Contributed by Yury Selivanov.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:829 ../Doc/whatsnew/3.6.rst:604 +msgid "" +"New :func:`~asyncio.run_coroutine_threadsafe` function to submit coroutines " +"to event loops from other threads. (Contributed by Vincent Michel.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:833 ../Doc/whatsnew/3.6.rst:608 +msgid "" +"New :meth:`Transport.is_closing() ` method " +"to check if the transport is closing or closed. (Contributed by Yury " +"Selivanov.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:837 ../Doc/whatsnew/3.6.rst:612 +msgid "" +"The :meth:`loop.create_server() ` " +"method can now accept a list of hosts. (Contributed by Yann Sionneau.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:841 +msgid "Updates in 3.5.2:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:843 ../Doc/whatsnew/3.6.rst:616 +msgid "" +"New :meth:`loop.create_future() ` " +"method to create Future objects. This allows alternative event loop " +"implementations, such as `uvloop `_, " +"to provide a faster :class:`asyncio.Future` implementation. (Contributed by " +"Yury Selivanov.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:850 ../Doc/whatsnew/3.6.rst:623 +msgid "" +"New :meth:`loop.get_exception_handler() ` method to get the current exception handler. " +"(Contributed by Yury Selivanov.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:854 ../Doc/whatsnew/3.6.rst:627 +msgid "" +"New :meth:`StreamReader.readuntil() ` method " +"to read data from the stream until a separator bytes sequence appears. " +"(Contributed by Mark Korenberg.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:859 +msgid "" +"The :meth:`loop.create_connection() ` and :meth:`loop.create_server() ` methods are optimized to avoid calling the system " +"``getaddrinfo`` function if the address is already resolved. (Contributed by " +"A. Jesse Jiryu Davis.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:865 +msgid "" +"The :meth:`loop.sock_connect(sock, address) ` no longer requires the *address* to be resolved prior to the " +"call. (Contributed by A. Jesse Jiryu Davis.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:873 +msgid "" +"The :meth:`BZ2Decompressor.decompress ` " +"method now accepts an optional *max_length* argument to limit the maximum " +"size of decompressed data. (Contributed by Nikolaus Rath in :issue:`15955`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:879 +msgid "cgi" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:881 +msgid "" +"The :class:`~cgi.FieldStorage` class now supports the :term:`context " +"manager` protocol. (Contributed by Berker Peksag in :issue:`20289`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:886 +msgid "cmath" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:888 +msgid "" +"A new function :func:`~cmath.isclose` provides a way to test for approximate " +"equality. (Contributed by Chris Barker and Tal Einat in :issue:`24270`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:893 +msgid "code" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:895 +msgid "" +"The :func:`InteractiveInterpreter.showtraceback() ` method now prints the full chained " +"traceback, just like the interactive interpreter. (Contributed by Claudiu " +"Popa in :issue:`17442`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:905 +msgid "" +"The :class:`~collections.OrderedDict` class is now implemented in C, which " +"makes it 4 to 100 times faster. (Contributed by Eric Snow in :issue:" +"`16991`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:908 +msgid "" +":meth:`OrderedDict.items() `, :meth:" +"`OrderedDict.keys() `, :meth:`OrderedDict." +"values() ` views now support :func:" +"`reversed` iteration. (Contributed by Serhiy Storchaka in :issue:`19505`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:914 +msgid "" +"The :class:`~collections.deque` class now defines :meth:`~collections.deque." +"index`, :meth:`~collections.deque.insert`, and :meth:`~collections.deque." +"copy`, and supports the ``+`` and ``*`` operators. This allows deques to be " +"recognized as a :class:`~collections.abc.MutableSequence` and improves their " +"substitutability for lists. (Contributed by Raymond Hettinger in :issue:" +"`23704`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:921 +msgid "" +"Docstrings produced by :func:`~collections.namedtuple` can now be updated::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:928 +msgid "(Contributed by Berker Peksag in :issue:`24064`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:930 +msgid "" +"The :class:`~collections.UserString` class now implements the :meth:" +"`__getnewargs__`, :meth:`__rmod__`, :meth:`~str.casefold`, :meth:`~str." +"format_map`, :meth:`~str.isprintable`, and :meth:`~str.maketrans` methods to " +"match the corresponding methods of :class:`str`. (Contributed by Joe Jevnik " +"in :issue:`22189`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:938 +msgid "collections.abc" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:940 +msgid "" +"The :meth:`Sequence.index() ` method now " +"accepts *start* and *stop* arguments to match the corresponding methods of :" +"class:`tuple`, :class:`list`, etc. (Contributed by Devin Jeanpierre in :" +"issue:`23086`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:945 +msgid "" +"A new :class:`~collections.abc.Generator` abstract base class. (Contributed " +"by Stefan Behnel in :issue:`24018`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:948 +msgid "" +"New :class:`~collections.abc.Awaitable`, :class:`~collections.abc." +"Coroutine`, :class:`~collections.abc.AsyncIterator`, and :class:" +"`~collections.abc.AsyncIterable` abstract base classes. (Contributed by Yury " +"Selivanov in :issue:`24184`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:953 +msgid "" +"For earlier Python versions, a backport of the new ABCs is available in an " +"external `PyPI package `_." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:958 +msgid "compileall" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:960 +msgid "" +"A new :mod:`compileall` option, :samp:`-j {N}`, allows running *N* workers " +"simultaneously to perform parallel bytecode compilation. The :func:" +"`~compileall.compile_dir` function has a corresponding ``workers`` " +"parameter. (Contributed by Claudiu Popa in :issue:`16104`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:965 +msgid "" +"Another new option, ``-r``, allows controlling the maximum recursion level " +"for subdirectories. (Contributed by Claudiu Popa in :issue:`19628`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:968 +msgid "" +"The ``-q`` command line option can now be specified more than once, in which " +"case all output, including errors, will be suppressed. The corresponding " +"``quiet`` parameter in :func:`~compileall.compile_dir`, :func:`~compileall." +"compile_file`, and :func:`~compileall.compile_path` can now accept an " +"integer value indicating the level of output suppression. (Contributed by " +"Thomas Kluyver in :issue:`21338`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:977 +msgid "concurrent.futures" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:979 +msgid "" +"The :meth:`Executor.map() ` method now " +"accepts a *chunksize* argument to allow batching of tasks to improve " +"performance when :meth:`~concurrent.futures.ProcessPoolExecutor` is used. " +"(Contributed by Dan O'Reilly in :issue:`11271`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:984 +msgid "" +"The number of workers in the :class:`~concurrent.futures.ThreadPoolExecutor` " +"constructor is optional now. The default value is 5 times the number of " +"CPUs. (Contributed by Claudiu Popa in :issue:`21527`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:992 +msgid "" +":mod:`configparser` now provides a way to customize the conversion of values " +"by specifying a dictionary of converters in the :class:`~configparser." +"ConfigParser` constructor, or by defining them as methods in " +"``ConfigParser`` subclasses. Converters defined in a parser instance are " +"inherited by its section proxies." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:998 +msgid "Example::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1016 +msgid "(Contributed by Łukasz Langa in :issue:`18159`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1022 +msgid "" +"The new :func:`~contextlib.redirect_stderr` :term:`context manager` (similar " +"to :func:`~contextlib.redirect_stdout`) makes it easier for utility scripts " +"to handle inflexible APIs that write their output to :data:`sys.stderr` and " +"don't provide any options to redirect it::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1035 +msgid "(Contributed by Berker Peksag in :issue:`22389`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1041 +msgid "" +"The :meth:`~csv.csvwriter.writerow` method now supports arbitrary iterables, " +"not just sequences. (Contributed by Serhiy Storchaka in :issue:`23171`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1048 +msgid "" +"The new :func:`~curses.update_lines_cols` function updates the :envvar:" +"`LINES` and :envvar:`COLS` environment variables. This is useful for " +"detecting manual screen resizing. (Contributed by Arnon Yaari in :issue:" +"`4254`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1056 +msgid "" +":func:`dumb.open ` always creates a new database when the " +"flag has the value ``\"n\"``. (Contributed by Claudiu Popa in :issue:" +"`18039`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1061 +msgid "difflib" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1063 +msgid "" +"The charset of HTML documents generated by :meth:`HtmlDiff.make_file() " +"` can now be customized by using a new *charset* " +"keyword-only argument. The default charset of HTML document changed from ``" +"\"ISO-8859-1\"`` to ``\"utf-8\"``. (Contributed by Berker Peksag in :issue:" +"`2052`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1070 +msgid "" +"The :func:`~difflib.diff_bytes` function can now compare lists of byte " +"strings. This fixes a regression from Python 2. (Contributed by Terry J. " +"Reedy and Greg Ward in :issue:`17445`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1076 +msgid "distutils" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1078 +msgid "" +"Both the ``build`` and ``build_ext`` commands now accept a ``-j`` option to " +"enable parallel building of extension modules. (Contributed by Antoine " +"Pitrou in :issue:`5309`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1082 +msgid "" +"The :mod:`distutils` module now supports ``xz`` compression, and can be " +"enabled by passing ``xztar`` as an argument to ``bdist --format``. " +"(Contributed by Serhiy Storchaka in :issue:`16314`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1090 +msgid "" +"The :func:`~doctest.DocTestSuite` function returns an empty :class:`unittest." +"TestSuite` if *module* contains no docstrings, instead of raising :exc:" +"`ValueError`. (Contributed by Glenn Jones in :issue:`15916`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1098 +msgid "" +"A new policy option :attr:`Policy.mangle_from_ ` controls whether or not lines that start with ``\"From \"`` " +"in email bodies are prefixed with a ``\">\"`` character by generators. The " +"default is ``True`` for :attr:`~email.policy.compat32` and ``False`` for all " +"other policies. (Contributed by Milan Oberkirch in :issue:`20098`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1104 +msgid "" +"A new :meth:`Message.get_content_disposition() ` method provides easy access to a canonical value " +"for the :mailheader:`Content-Disposition` header. (Contributed by Abhilash " +"Raj in :issue:`21083`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1110 +msgid "" +"A new policy option :attr:`EmailPolicy.utf8 ` " +"can be set to ``True`` to encode email headers using the UTF-8 charset " +"instead of using encoded words. This allows ``Messages`` to be formatted " +"according to :rfc:`6532` and used with an SMTP server that supports the :rfc:" +"`6531` ``SMTPUTF8`` extension. (Contributed by R. David Murray in :issue:" +"`24211`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1117 +msgid "" +"The :class:`mime.text.MIMEText ` constructor now " +"accepts a :class:`charset.Charset ` instance. " +"(Contributed by Claude Paroz and Berker Peksag in :issue:`16324`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1125 +msgid "" +"The :class:`~enum.Enum` callable has a new parameter *start* to specify the " +"initial number of enum values if only *names* are provided::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1134 +msgid "(Contributed by Ethan Furman in :issue:`21706`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1140 +msgid "" +"The :func:`~faulthandler.enable`, :func:`~faulthandler.register`, :func:" +"`~faulthandler.dump_traceback` and :func:`~faulthandler." +"dump_traceback_later` functions now accept file descriptors in addition to " +"file-like objects. (Contributed by Wei Wu in :issue:`23566`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1152 +msgid "" +"Most of the :func:`~functools.lru_cache` machinery is now implemented in C, " +"making it significantly faster. (Contributed by Matt Joiner, Alexey " +"Kachayev, and Serhiy Storchaka in :issue:`14373`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1160 +msgid "" +"The :func:`~glob.iglob` and :func:`~glob.glob` functions now support " +"recursive search in subdirectories, using the ``\"**\"`` pattern. " +"(Contributed by Serhiy Storchaka in :issue:`13968`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1166 +msgid "gzip" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1168 +msgid "" +"The *mode* argument of the :class:`~gzip.GzipFile` constructor now accepts ``" +"\"x\"`` to request exclusive creation. (Contributed by Tim Heaney in :issue:" +"`19222`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1174 +msgid "heapq" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1176 +msgid "" +"Element comparison in :func:`~heapq.merge` can now be customized by passing " +"a :term:`key function` in a new optional *key* keyword argument, and a new " +"optional *reverse* keyword argument can be used to reverse element " +"comparison::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1189 +msgid "(Contributed by Raymond Hettinger in :issue:`13742`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1195 +msgid "" +"A new :class:`HTTPStatus ` enum that defines a set of HTTP " +"status codes, reason phrases and long descriptions written in English. " +"(Contributed by Demian Brecht in :issue:`21793`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1203 +msgid "" +":meth:`HTTPConnection.getresponse() ` now raises a :exc:`~http.client.RemoteDisconnected` exception " +"when a remote server connection is closed unexpectedly. Additionally, if a :" +"exc:`ConnectionError` (of which ``RemoteDisconnected`` is a subclass) is " +"raised, the client socket is now closed automatically, and will reconnect on " +"the next request::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1219 +msgid "(Contributed by Martin Panter in :issue:`3566`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1225 +msgid "" +"Since idlelib implements the IDLE shell and editor and is not intended for " +"import by other programs, it gets improvements with every release. See :" +"file:`Lib/idlelib/NEWS.txt` for a cumulative list of changes since 3.4.0, as " +"well as changes made in future 3.5.x releases. This file is also available " +"from the IDLE :menuselection:`Help --> About IDLE` dialog." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1235 +msgid "" +"The :class:`~imaplib.IMAP4` class now supports the :term:`context manager` " +"protocol. When used in a :keyword:`with` statement, the IMAP4 ``LOGOUT`` " +"command will be called automatically at the end of the block. (Contributed " +"by Tarek Ziadé and Serhiy Storchaka in :issue:`4972`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1240 +msgid "" +"The :mod:`imaplib` module now supports :rfc:`5161` (ENABLE Extension) and :" +"rfc:`6855` (UTF-8 Support) via the :meth:`IMAP4.enable() ` method. A new :attr:`IMAP4.utf8_enabled ` attribute tracks whether or not :rfc:`6855` support is " +"enabled. (Contributed by Milan Oberkirch, R. David Murray, and Maciej Szulik " +"in :issue:`21800`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1247 +msgid "" +"The :mod:`imaplib` module now automatically encodes non-ASCII string " +"usernames and passwords using UTF-8, as recommended by the RFCs. " +"(Contributed by Milan Oberkirch in :issue:`21800`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1253 +msgid "imghdr" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1255 +msgid "" +"The :func:`~imghdr.what` function now recognizes the `OpenEXR `_ format (contributed by Martin Vignali and Claudiu Popa in :" +"issue:`20295`), and the `WebP `_ format " +"(contributed by Fabrice Aneche and Claudiu Popa in :issue:`20197`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1265 +msgid "" +"The :class:`util.LazyLoader ` class allows for " +"lazy loading of modules in applications where startup time is important. " +"(Contributed by Brett Cannon in :issue:`17621`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1269 +msgid "" +"The :func:`abc.InspectLoader.source_to_code() ` method is now a static method. This makes it easier to " +"initialize a module object with code compiled from a string by running " +"``exec(code, module.__dict__)``. (Contributed by Brett Cannon in :issue:" +"`21156`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1275 +msgid "" +"The new :func:`util.module_from_spec() ` " +"function is now the preferred way to create a new module. As opposed to " +"creating a :class:`types.ModuleType` instance directly, this new function " +"will set the various import-controlled attributes based on the passed-in " +"spec object. (Contributed by Brett Cannon in :issue:`20383`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1285 +msgid "" +"Both the :class:`~inspect.Signature` and :class:`~inspect.Parameter` classes " +"are now picklable and hashable. (Contributed by Yury Selivanov in :issue:" +"`20726` and :issue:`20334`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1289 +msgid "" +"A new :meth:`BoundArguments.apply_defaults() ` method provides a way to set default values for missing " +"arguments::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1299 +msgid "(Contributed by Yury Selivanov in :issue:`24190`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1301 +msgid "" +"A new class method :meth:`Signature.from_callable() ` makes subclassing of :class:`~inspect.Signature` easier. " +"(Contributed by Yury Selivanov and Eric Snow in :issue:`17373`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1306 +msgid "" +"The :func:`~inspect.signature` function now accepts a *follow_wrapped* " +"optional keyword argument, which, when set to ``False``, disables automatic " +"following of ``__wrapped__`` links. (Contributed by Yury Selivanov in :issue:" +"`20691`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1311 +msgid "" +"A set of new functions to inspect :term:`coroutine functions ` and :term:`coroutine objects ` has been added: :func:" +"`~inspect.iscoroutine`, :func:`~inspect.iscoroutinefunction`, :func:" +"`~inspect.isawaitable`, :func:`~inspect.getcoroutinelocals`, and :func:" +"`~inspect.getcoroutinestate`. (Contributed by Yury Selivanov in :issue:" +"`24017` and :issue:`24400`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1319 +msgid "" +"The :func:`~inspect.stack`, :func:`~inspect.trace`, :func:`~inspect." +"getouterframes`, and :func:`~inspect.getinnerframes` functions now return a " +"list of named tuples. (Contributed by Daniel Shahaf in :issue:`16808`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1328 +msgid "" +"A new :meth:`BufferedIOBase.readinto1() ` " +"method, that uses at most one call to the underlying raw stream's :meth:" +"`RawIOBase.read() ` or :meth:`RawIOBase.readinto() ` methods. (Contributed by Nikolaus Rath in :issue:" +"`20578`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1338 +msgid "" +"Both the :class:`~ipaddress.IPv4Network` and :class:`~ipaddress.IPv6Network` " +"classes now accept an ``(address, netmask)`` tuple argument, so as to easily " +"construct network objects from existing addresses::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1348 +msgid "(Contributed by Peter Moody and Antoine Pitrou in :issue:`16531`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1350 +msgid "" +"A new :attr:`~ipaddress.IPv4Network.reverse_pointer` attribute for the :" +"class:`~ipaddress.IPv4Network` and :class:`~ipaddress.IPv6Network` classes " +"returns the name of the reverse DNS PTR record::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1362 +msgid "(Contributed by Leon Weber in :issue:`20480`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1366 ../Doc/whatsnew/3.6.rst:774 +msgid "json" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1368 +msgid "" +"The :mod:`json.tool` command line interface now preserves the order of keys " +"in JSON objects passed in input. The new ``--sort-keys`` option can be used " +"to sort the keys alphabetically. (Contributed by Berker Peksag in :issue:" +"`21650`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1373 +msgid "" +"JSON decoder now raises :exc:`~json.JSONDecodeError` instead of :exc:" +"`ValueError` to provide better context information about the error. " +"(Contributed by Serhiy Storchaka in :issue:`19361`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1379 +msgid "linecache" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1381 +msgid "" +"A new :func:`~linecache.lazycache` function can be used to capture " +"information about a non-file-based module to permit getting its lines later " +"via :func:`~linecache.getline`. This avoids doing I/O until a line is " +"actually needed, without having to carry the module globals around " +"indefinitely. (Contributed by Robert Collins in :issue:`17911`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1389 +msgid "locale" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1391 +msgid "" +"A new :func:`~locale.delocalize` function can be used to convert a string " +"into a normalized number string, taking the ``LC_NUMERIC`` settings into " +"account::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1404 +msgid "(Contributed by Cédric Krier in :issue:`13918`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1410 +msgid "" +"All logging methods (:class:`~logging.Logger` :meth:`~logging.Logger.log`, :" +"meth:`~logging.Logger.exception`, :meth:`~logging.Logger.critical`, :meth:" +"`~logging.Logger.debug`, etc.), now accept exception instances as an " +"*exc_info* argument, in addition to boolean values and exception tuples::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1423 +msgid "(Contributed by Yury Selivanov in :issue:`20537`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1425 +msgid "" +"The :class:`handlers.HTTPHandler ` class now " +"accepts an optional :class:`ssl.SSLContext` instance to configure SSL " +"settings used in an HTTP connection. (Contributed by Alex Gaynor in :issue:" +"`22788`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1430 +msgid "" +"The :class:`handlers.QueueListener ` class " +"now takes a *respect_handler_level* keyword argument which, if set to " +"``True``, will pass messages to handlers taking handler levels into account. " +"(Contributed by Vinay Sajip.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1439 +msgid "" +"The :meth:`LZMADecompressor.decompress() ` " +"method now accepts an optional *max_length* argument to limit the maximum " +"size of decompressed data. (Contributed by Martin Panter in :issue:`15955`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1448 +msgid "" +"Two new constants have been added to the :mod:`math` module: :data:`~math." +"inf` and :data:`~math.nan`. (Contributed by Mark Dickinson in :issue:" +"`23185`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1451 +msgid "" +"A new function :func:`~math.isclose` provides a way to test for approximate " +"equality. (Contributed by Chris Barker and Tal Einat in :issue:`24270`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1454 +msgid "" +"A new :func:`~math.gcd` function has been added. The :func:`fractions.gcd` " +"function is now deprecated. (Contributed by Mark Dickinson and Serhiy " +"Storchaka in :issue:`22486`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1462 +msgid "" +":func:`sharedctypes.synchronized() ` objects now support the :term:`context manager` protocol. " +"(Contributed by Charles-François Natali in :issue:`21565`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1470 +msgid "" +":func:`~operator.attrgetter`, :func:`~operator.itemgetter`, and :func:" +"`~operator.methodcaller` objects now support pickling. (Contributed by Josh " +"Rosenberg and Serhiy Storchaka in :issue:`22955`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1474 +msgid "" +"New :func:`~operator.matmul` and :func:`~operator.imatmul` functions to " +"perform matrix multiplication. (Contributed by Benjamin Peterson in :issue:" +"`21176`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1482 +msgid "" +"The new :func:`~os.scandir` function returning an iterator of :class:`~os." +"DirEntry` objects has been added. If possible, :func:`~os.scandir` extracts " +"file attributes while scanning a directory, removing the need to perform " +"subsequent system calls to determine file type or attributes, which may " +"significantly improve performance. (Contributed by Ben Hoyt with the help " +"of Victor Stinner in :issue:`22524`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1489 +msgid "" +"On Windows, a new :attr:`stat_result.st_file_attributes ` attribute is now available. It corresponds to the " +"``dwFileAttributes`` member of the ``BY_HANDLE_FILE_INFORMATION`` structure " +"returned by ``GetFileInformationByHandle()``. (Contributed by Ben Hoyt in :" +"issue:`21719`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1495 +msgid "" +"The :func:`~os.urandom` function now uses the ``getrandom()`` syscall on " +"Linux 3.17 or newer, and ``getentropy()`` on OpenBSD 5.6 and newer, removing " +"the need to use ``/dev/urandom`` and avoiding failures due to potential file " +"descriptor exhaustion. (Contributed by Victor Stinner in :issue:`22181`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1500 +msgid "" +"New :func:`~os.get_blocking` and :func:`~os.set_blocking` functions allow " +"getting and setting a file descriptor's blocking mode (:data:`~os." +"O_NONBLOCK`.) (Contributed by Victor Stinner in :issue:`22054`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1504 +msgid "" +"The :func:`~os.truncate` and :func:`~os.ftruncate` functions are now " +"supported on Windows. (Contributed by Steve Dower in :issue:`23668`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1507 +msgid "" +"There is a new :func:`os.path.commonpath` function returning the longest " +"common sub-path of each passed pathname. Unlike the :func:`os.path." +"commonprefix` function, it always returns a valid path::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1518 +msgid "(Contributed by Rafik Draoui and Serhiy Storchaka in :issue:`10395`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1524 +msgid "" +"The new :meth:`Path.samefile() ` method can be used " +"to check whether the path points to the same file as another path, which can " +"be either another :class:`~pathlib.Path` object, or a string::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1534 +msgid "(Contributed by Vajrasky Kok and Antoine Pitrou in :issue:`19775`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1536 +msgid "" +"The :meth:`Path.mkdir() ` method now accepts a new " +"optional *exist_ok* argument to match ``mkdir -p`` and :func:`os.makedirs` " +"functionality. (Contributed by Berker Peksag in :issue:`21539`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1540 +msgid "" +"There is a new :meth:`Path.expanduser() ` method to " +"expand ``~`` and ``~user`` prefixes. (Contributed by Serhiy Storchaka and " +"Claudiu Popa in :issue:`19776`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1544 +msgid "" +"A new :meth:`Path.home() ` class method can be used to " +"get a :class:`~pathlib.Path` instance representing the user’s home " +"directory. (Contributed by Victor Salgado and Mayank Tripathi in :issue:" +"`19777`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1549 +msgid "" +"New :meth:`Path.write_text() `, :meth:`Path." +"read_text() `, :meth:`Path.write_bytes() `, :meth:`Path.read_bytes() ` " +"methods to simplify read/write operations on files." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1555 +msgid "" +"The following code snippet will create or rewrite existing file ``~/" +"spam42``::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1563 +msgid "(Contributed by Christopher Welborn in :issue:`20218`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1569 +msgid "" +"Nested objects, such as unbound methods or nested classes, can now be " +"pickled using :ref:`pickle protocols ` older than protocol " +"version 4. Protocol version 4 already supports these cases. (Contributed by " +"Serhiy Storchaka in :issue:`23611`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1578 +msgid "" +"A new :meth:`POP3.utf8() ` command enables :rfc:`6856` " +"(Internationalized Email) support, if a POP server supports it. (Contributed " +"by Milan OberKirch in :issue:`21804`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1586 +msgid "" +"References and conditional references to groups with fixed length are now " +"allowed in lookbehind assertions::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1596 +msgid "(Contributed by Serhiy Storchaka in :issue:`9179`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1598 +msgid "" +"The number of capturing groups in regular expressions is no longer limited " +"to 100. (Contributed by Serhiy Storchaka in :issue:`22437`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1601 +msgid "" +"The :func:`~re.sub` and :func:`~re.subn` functions now replace unmatched " +"groups with empty strings instead of raising an exception. (Contributed by " +"Serhiy Storchaka in :issue:`1519638`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1605 +msgid "" +"The :class:`re.error` exceptions have new attributes, :attr:`~re.error." +"msg`, :attr:`~re.error.pattern`, :attr:`~re.error.pos`, :attr:`~re.error." +"lineno`, and :attr:`~re.error.colno`, that provide better context " +"information about the error::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1619 +msgid "(Contributed by Serhiy Storchaka in :issue:`22578`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1623 ../Doc/whatsnew/3.6.rst:823 +msgid "readline" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1625 +msgid "" +"A new :func:`~readline.append_history_file` function can be used to append " +"the specified number of trailing elements in history to the given file. " +"(Contributed by Bruno Cauet in :issue:`22940`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1633 +msgid "" +"The new :class:`~selectors.DevpollSelector` supports efficient ``/dev/poll`` " +"polling on Solaris. (Contributed by Giampaolo Rodola' in :issue:`18931`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1641 +msgid "" +"The :func:`~shutil.move` function now accepts a *copy_function* argument, " +"allowing, for example, the :func:`~shutil.copy` function to be used instead " +"of the default :func:`~shutil.copy2` if there is a need to ignore file " +"metadata when moving. (Contributed by Claudiu Popa in :issue:`19840`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1647 +msgid "" +"The :func:`~shutil.make_archive` function now supports the *xztar* format. " +"(Contributed by Serhiy Storchaka in :issue:`5411`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1654 +msgid "" +"On Windows, the :func:`~signal.set_wakeup_fd` function now also supports " +"socket handles. (Contributed by Victor Stinner in :issue:`22018`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1657 +msgid "" +"Various ``SIG*`` constants in the :mod:`signal` module have been converted " +"into :mod:`Enums `. This allows meaningful names to be printed during " +"debugging, instead of integer \"magic numbers\". (Contributed by Giampaolo " +"Rodola' in :issue:`21076`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1666 +msgid "" +"Both the :class:`~smtpd.SMTPServer` and :class:`~smtpd.SMTPChannel` classes " +"now accept a *decode_data* keyword argument to determine if the ``DATA`` " +"portion of the SMTP transaction is decoded using the ``\"utf-8\"`` codec or " +"is instead provided to the :meth:`SMTPServer.process_message() ` method as a byte string. The default is " +"``True`` for backward compatibility reasons, but will change to ``False`` in " +"Python 3.6. If *decode_data* is set to ``False``, the ``process_message`` " +"method must be prepared to accept keyword arguments. (Contributed by Maciej " +"Szulik in :issue:`19662`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1677 +msgid "" +"The :class:`~smtpd.SMTPServer` class now advertises the ``8BITMIME`` " +"extension (:rfc:`6152`) if *decode_data* has been set ``True``. If the " +"client specifies ``BODY=8BITMIME`` on the ``MAIL`` command, it is passed to :" +"meth:`SMTPServer.process_message() ` via " +"the *mail_options* keyword. (Contributed by Milan Oberkirch and R. David " +"Murray in :issue:`21795`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1684 +msgid "" +"The :class:`~smtpd.SMTPServer` class now also supports the ``SMTPUTF8`` " +"extension (:rfc:`6531`: Internationalized Email). If the client specified " +"``SMTPUTF8 BODY=8BITMIME`` on the ``MAIL`` command, they are passed to :meth:" +"`SMTPServer.process_message() ` via the " +"*mail_options* keyword. It is the responsibility of the ``process_message`` " +"method to correctly handle the ``SMTPUTF8`` data. (Contributed by Milan " +"Oberkirch in :issue:`21725`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1692 +msgid "" +"It is now possible to provide, directly or via name resolution, IPv6 " +"addresses in the :class:`~smtpd.SMTPServer` constructor, and have it " +"successfully connect. (Contributed by Milan Oberkirch in :issue:`14758`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1700 +msgid "" +"A new :meth:`SMTP.auth() ` method provides a convenient " +"way to implement custom authentication mechanisms. (Contributed by Milan " +"Oberkirch in :issue:`15014`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1704 +msgid "" +"The :meth:`SMTP.set_debuglevel() ` method now " +"accepts an additional debuglevel (2), which enables timestamps in debug " +"messages. (Contributed by Gavin Chappell and Maciej Szulik in :issue:" +"`16914`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1708 +msgid "" +"Both the :meth:`SMTP.sendmail() ` and :meth:`SMTP." +"send_message() ` methods now support :rfc:`6531` " +"(SMTPUTF8). (Contributed by Milan Oberkirch and R. David Murray in :issue:" +"`22027`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1715 +msgid "sndhdr" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1717 +msgid "" +"The :func:`~sndhdr.what` and :func:`~sndhdr.whathdr` functions now return " +"a :func:`~collections.namedtuple`. (Contributed by Claudiu Popa in :issue:" +"`18615`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1725 +msgid "" +"Functions with timeouts now use a monotonic clock, instead of a system " +"clock. (Contributed by Victor Stinner in :issue:`22043`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1728 +msgid "" +"A new :meth:`socket.sendfile() ` method allows " +"sending a file over a socket by using the high-performance :func:`os." +"sendfile` function on UNIX, resulting in uploads being from 2 to 3 times " +"faster than when using plain :meth:`socket.send() `. " +"(Contributed by Giampaolo Rodola' in :issue:`17552`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1734 +msgid "" +"The :meth:`socket.sendall() ` method no longer resets " +"the socket timeout every time bytes are received or sent. The socket " +"timeout is now the maximum total duration to send all data. (Contributed by " +"Victor Stinner in :issue:`23853`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1739 +msgid "" +"The *backlog* argument of the :meth:`socket.listen() ` " +"method is now optional. By default it is set to :data:`SOMAXCONN ` or to ``128``, whichever is less. (Contributed by Charles-" +"François Natali in :issue:`21455`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1751 +msgid "Memory BIO Support" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1753 +msgid "(Contributed by Geert Jansen in :issue:`21965`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1755 +msgid "" +"The new :class:`~ssl.SSLObject` class has been added to provide SSL protocol " +"support for cases when the network I/O capabilities of :class:`~ssl." +"SSLSocket` are not necessary or are suboptimal. ``SSLObject`` represents an " +"SSL protocol instance, but does not implement any network I/O methods, and " +"instead provides a memory buffer interface. The new :class:`~ssl.MemoryBIO` " +"class can be used to pass data between Python and an SSL protocol instance." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1762 +msgid "" +"The memory BIO SSL support is primarily intended to be used in frameworks " +"implementing asynchronous I/O for which :class:`~ssl.SSLSocket`'s readiness " +"model (\"select/poll\") is inefficient." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1766 +msgid "" +"A new :meth:`SSLContext.wrap_bio() ` method can be " +"used to create a new ``SSLObject`` instance." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1771 +msgid "Application-Layer Protocol Negotiation Support" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1773 +msgid "(Contributed by Benjamin Peterson in :issue:`20188`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1775 +msgid "" +"Where OpenSSL support is present, the :mod:`ssl` module now implements the " +"*Application-Layer Protocol Negotiation* TLS extension as described in :rfc:" +"`7301`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1779 +msgid "" +"The new :meth:`SSLContext.set_alpn_protocols() ` can be used to specify which protocols a socket should " +"advertise during the TLS handshake." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1783 +msgid "" +"The new :meth:`SSLSocket.selected_alpn_protocol() ` returns the protocol that was selected during the " +"TLS handshake. The :data:`~ssl.HAS_ALPN` flag indicates whether ALPN support " +"is present." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1790 +msgid "Other Changes" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1792 +msgid "" +"There is a new :meth:`SSLSocket.version() ` method to " +"query the actual protocol version in use. (Contributed by Antoine Pitrou in :" +"issue:`20421`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1796 +msgid "" +"The :class:`~ssl.SSLSocket` class now implements a :meth:`SSLSocket." +"sendfile() ` method. (Contributed by Giampaolo " +"Rodola' in :issue:`17552`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1800 +msgid "" +"The :meth:`SSLSocket.send() ` method now raises either " +"the :exc:`ssl.SSLWantReadError` or :exc:`ssl.SSLWantWriteError` exception on " +"a non-blocking socket if the operation would block. Previously, it would " +"return ``0``. (Contributed by Nikolaus Rath in :issue:`20951`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1805 +msgid "" +"The :func:`~ssl.cert_time_to_seconds` function now interprets the input time " +"as UTC and not as local time, per :rfc:`5280`. Additionally, the return " +"value is always an :class:`int`. (Contributed by Akira Li in :issue:`19940`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1809 +msgid "" +"New :meth:`SSLObject.shared_ciphers() ` and :" +"meth:`SSLSocket.shared_ciphers() ` methods " +"return the list of ciphers sent by the client during the handshake. " +"(Contributed by Benjamin Peterson in :issue:`23186`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1814 +msgid "" +"The :meth:`SSLSocket.do_handshake() `, :meth:" +"`SSLSocket.read() `, :meth:`SSLSocket.shutdown() `, and :meth:`SSLSocket.write() ` " +"methods of the :class:`~ssl.SSLSocket` class no longer reset the socket " +"timeout every time bytes are received or sent. The socket timeout is now the " +"maximum total duration of the method. (Contributed by Victor Stinner in :" +"issue:`23853`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1822 +msgid "" +"The :func:`~ssl.match_hostname` function now supports matching of IP " +"addresses. (Contributed by Antoine Pitrou in :issue:`23239`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1829 +msgid "" +"The :class:`~sqlite3.Row` class now fully supports the sequence protocol, in " +"particular :func:`reversed` iteration and slice indexing. (Contributed by " +"Claudiu Popa in :issue:`10203`; by Lucas Sinclair, Jessica McKellar, and " +"Serhiy Storchaka in :issue:`13583`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1840 +msgid "" +"The new :func:`~subprocess.run` function has been added. It runs the " +"specified command and returns a :class:`~subprocess.CompletedProcess` " +"object, which describes a finished process. The new API is more consistent " +"and is the recommended approach to invoking subprocesses in Python code that " +"does not need to maintain compatibility with earlier Python versions. " +"(Contributed by Thomas Kluyver in :issue:`23342`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1866 +msgid "" +"A new :func:`~sys.set_coroutine_wrapper` function allows setting a global " +"hook that will be called whenever a :term:`coroutine object ` is " +"created by an :keyword:`async def` function. A corresponding :func:`~sys." +"get_coroutine_wrapper` can be used to obtain a currently set wrapper. Both " +"functions are :term:`provisional `, and are intended for " +"debugging purposes only. (Contributed by Yury Selivanov in :issue:`24017`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1874 +msgid "" +"A new :func:`~sys.is_finalizing` function can be used to check if the Python " +"interpreter is :term:`shutting down `. (Contributed by " +"Antoine Pitrou in :issue:`22696`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1882 +msgid "" +"The name of the user scripts directory on Windows now includes the first two " +"components of the Python version. (Contributed by Paul Moore in :issue:" +"`23437`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1890 +msgid "" +"The *mode* argument of the :func:`~tarfile.open` function now accepts ``\"x" +"\"`` to request exclusive creation. (Contributed by Berker Peksag in :issue:" +"`21717`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1893 +msgid "" +"The :meth:`TarFile.extractall() ` and :meth:" +"`TarFile.extract() ` methods now take a keyword " +"argument *numeric_only*. If set to ``True``, the extracted files and " +"directories will be owned by the numeric ``uid`` and ``gid`` from the " +"tarfile. If set to ``False`` (the default, and the behavior in versions " +"prior to 3.5), they will be owned by the named user and group in the " +"tarfile. (Contributed by Michael Vogt and Eric Smith in :issue:`23193`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1901 +msgid "" +"The :meth:`TarFile.list() ` now accepts an optional " +"*members* keyword argument that can be set to a subset of the list returned " +"by :meth:`TarFile.getmembers() `. (Contributed " +"by Serhiy Storchaka in :issue:`21549`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1910 +msgid "" +"Both the :meth:`Lock.acquire() ` and :meth:`RLock." +"acquire() ` methods now use a monotonic clock for " +"timeout management. (Contributed by Victor Stinner in :issue:`22043`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1919 +msgid "" +"The :func:`~time.monotonic` function is now always available. (Contributed " +"by Victor Stinner in :issue:`22043`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1924 +msgid "timeit" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1926 +msgid "" +"A new command line option ``-u`` or :samp:`--unit={U}` can be used to " +"specify the time unit for the timer output. Supported options are ``usec``, " +"``msec``, or ``sec``. (Contributed by Julian Gindi in :issue:`18983`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1930 +msgid "" +"The :func:`~timeit.timeit` function has a new *globals* parameter for " +"specifying the namespace in which the code will be running. (Contributed by " +"Ben Roberts in :issue:`2527`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1936 ../Doc/whatsnew/3.6.rst:944 +msgid "tkinter" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1938 +msgid "" +"The :mod:`tkinter._fix` module used for setting up the Tcl/Tk environment on " +"Windows has been replaced by a private function in the :mod:`_tkinter` " +"module which makes no permanent changes to environment variables. " +"(Contributed by Zachary Ware in :issue:`20035`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1949 +msgid "" +"New :func:`~traceback.walk_stack` and :func:`~traceback.walk_tb` functions " +"to conveniently traverse frame and traceback objects. (Contributed by Robert " +"Collins in :issue:`17911`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1953 +msgid "" +"New lightweight classes: :class:`~traceback.TracebackException`, :class:" +"`~traceback.StackSummary`, and :class:`~traceback.FrameSummary`. " +"(Contributed by Robert Collins in :issue:`17911`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1957 +msgid "" +"Both the :func:`~traceback.print_tb` and :func:`~traceback.print_stack` " +"functions now support negative values for the *limit* argument. (Contributed " +"by Dmitry Kazakov in :issue:`22619`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1965 +msgid "" +"A new :func:`~types.coroutine` function to transform :term:`generator " +"` and :class:`generator-like ` objects into :term:`awaitables `. (Contributed by " +"Yury Selivanov in :issue:`24017`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1971 +msgid "" +"A new type called :class:`~types.CoroutineType`, which is used for :term:" +"`coroutine` objects created by :keyword:`async def` functions. (Contributed " +"by Yury Selivanov in :issue:`24400`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1977 ../Doc/whatsnew/3.6.rst:988 +msgid "unicodedata" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1979 +msgid "" +"The :mod:`unicodedata` module now uses data from `Unicode 8.0.0 `_." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1986 +msgid "" +"The :meth:`TestLoader.loadTestsFromModule() ` method now accepts a keyword-only argument *pattern* " +"which is passed to ``load_tests`` as the third argument. Found packages are " +"now checked for ``load_tests`` regardless of whether their path matches " +"*pattern*, because it is impossible for a package name to match the default " +"pattern. (Contributed by Robert Collins and Barry A. Warsaw in :issue:" +"`16662`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1993 +msgid "" +"Unittest discovery errors now are exposed in the :data:`TestLoader.errors " +"` attribute of the :class:`~unittest.TestLoader` " +"instance. (Contributed by Robert Collins in :issue:`19746`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:1998 +msgid "" +"A new command line option ``--locals`` to show local variables in " +"tracebacks. (Contributed by Robert Collins in :issue:`22936`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2003 ../Doc/whatsnew/3.6.rst:995 +msgid "unittest.mock" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2005 ../Doc/whatsnew/3.6.rst:997 +msgid "The :class:`~unittest.mock.Mock` class has the following improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2007 +msgid "" +"The class constructor has a new *unsafe* parameter, which causes mock " +"objects to raise :exc:`AttributeError` on attribute names starting with ``" +"\"assert\"``. (Contributed by Kushal Das in :issue:`21238`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2012 +msgid "" +"A new :meth:`Mock.assert_not_called() ` method to check if the mock object was called. " +"(Contributed by Kushal Das in :issue:`21262`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2016 +msgid "" +"The :class:`~unittest.mock.MagicMock` class now supports :meth:" +"`__truediv__`, :meth:`__divmod__` and :meth:`__matmul__` operators. " +"(Contributed by Johannes Baiter in :issue:`20968`, and Håkan Lövdahl in :" +"issue:`23581` and :issue:`23568`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2021 +msgid "" +"It is no longer necessary to explicitly pass ``create=True`` to the :func:" +"`~unittest.mock.patch` function when patching builtin names. (Contributed by " +"Kushal Das in :issue:`17660`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2029 +msgid "" +"A new :class:`request.HTTPPasswordMgrWithPriorAuth ` class allows HTTP Basic Authentication " +"credentials to be managed so as to eliminate unnecessary ``401`` response " +"handling, or to unconditionally send credentials on the first request in " +"order to communicate with servers that return a ``404`` response instead of " +"a ``401`` if the ``Authorization`` header is not sent. (Contributed by Matej " +"Cepl in :issue:`19494` and Akshit Khurana in :issue:`7159`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2038 +msgid "" +"A new *quote_via* argument for the :func:`parse.urlencode() ` function provides a way to control the encoding of query parts " +"if needed. (Contributed by Samwyse and Arnon Yaari in :issue:`13866`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2043 +msgid "" +"The :func:`request.urlopen() ` function accepts an :" +"class:`ssl.SSLContext` object as a *context* argument, which will be used " +"for the HTTPS connection. (Contributed by Alex Gaynor in :issue:`22366`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2047 +msgid "" +"The :func:`parse.urljoin() ` was updated to use the :" +"rfc:`3986` semantics for the resolution of relative URLs, rather than :rfc:" +"`1808` and :rfc:`2396`. (Contributed by Demian Brecht and Senthil Kumaran " +"in :issue:`22118`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2054 +msgid "wsgiref" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2056 +msgid "" +"The *headers* argument of the :class:`headers.Headers ` class constructor is now optional. (Contributed by Pablo Torres " +"Navarrete and SilentGhost in :issue:`5800`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2062 +msgid "xmlrpc" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2064 +msgid "" +"The :class:`client.ServerProxy ` class now " +"supports the :term:`context manager` protocol. (Contributed by Claudiu Popa " +"in :issue:`20627`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2068 +msgid "" +"The :class:`client.ServerProxy ` constructor now " +"accepts an optional :class:`ssl.SSLContext` instance. (Contributed by Alex " +"Gaynor in :issue:`22960`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2074 +msgid "xml.sax" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2076 +msgid "" +"SAX parsers now support a character stream of the :class:`xmlreader." +"InputSource ` object. (Contributed by Serhiy " +"Storchaka in :issue:`2175`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2080 +msgid "" +":func:`~xml.sax.parseString` now accepts a :class:`str` instance. " +"(Contributed by Serhiy Storchaka in :issue:`10590`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2087 +msgid "" +"ZIP output can now be written to unseekable streams. (Contributed by Serhiy " +"Storchaka in :issue:`23252`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2090 +msgid "" +"The *mode* argument of :meth:`ZipFile.open() ` method " +"now accepts ``\"x\"`` to request exclusive creation. (Contributed by Serhiy " +"Storchaka in :issue:`21717`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2096 +msgid "Other module-level changes" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2098 +msgid "" +"Many functions in the :mod:`mmap`, :mod:`ossaudiodev`, :mod:`socket`, :mod:" +"`ssl`, and :mod:`codecs` modules now accept writable :term:`bytes-like " +"objects `. (Contributed by Serhiy Storchaka in :issue:" +"`23001`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2107 +msgid "" +"The :func:`os.walk` function has been sped up by 3 to 5 times on POSIX " +"systems, and by 7 to 20 times on Windows. This was done using the new :func:" +"`os.scandir` function, which exposes file information from the underlying " +"``readdir`` or ``FindFirstFile``/``FindNextFile`` system calls. " +"(Contributed by Ben Hoyt with help from Victor Stinner in :issue:`23605`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2113 +msgid "" +"Construction of ``bytes(int)`` (filled by zero bytes) is faster and uses " +"less memory for large objects. ``calloc()`` is used instead of ``malloc()`` " +"to allocate memory for these objects. (Contributed by Victor Stinner in :" +"issue:`21233`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2118 +msgid "" +"Some operations on :mod:`ipaddress` :class:`~ipaddress.IPv4Network` and :" +"class:`~ipaddress.IPv6Network` have been massively sped up, such as :meth:" +"`~ipaddress.IPv4Network.subnets`, :meth:`~ipaddress.IPv4Network.supernet`, :" +"func:`~ipaddress.summarize_address_range`, :func:`~ipaddress." +"collapse_addresses`. The speed up can range from 3 to 15 times. (Contributed " +"by Antoine Pitrou, Michel Albert, and Markus in :issue:`21486`, :issue:" +"`21487`, :issue:`20826`, :issue:`23266`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2126 +msgid "" +"Pickling of :mod:`ipaddress` objects was optimized to produce significantly " +"smaller output. (Contributed by Serhiy Storchaka in :issue:`23133`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2129 +msgid "" +"Many operations on :class:`io.BytesIO` are now 50% to 100% faster. " +"(Contributed by Serhiy Storchaka in :issue:`15381` and David Wilson in :" +"issue:`22003`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2133 +msgid "" +"The :func:`marshal.dumps` function is now faster: 65-85% with versions 3 and " +"4, 20-25% with versions 0 to 2 on typical data, and up to 5 times in best " +"cases. (Contributed by Serhiy Storchaka in :issue:`20416` and :issue:" +"`23344`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2138 +msgid "" +"The UTF-32 encoder is now 3 to 7 times faster. (Contributed by Serhiy " +"Storchaka in :issue:`15027`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2141 +msgid "" +"Regular expressions are now parsed up to 10% faster. (Contributed by Serhiy " +"Storchaka in :issue:`19380`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2144 +msgid "" +"The :func:`json.dumps` function was optimized to run with " +"``ensure_ascii=False`` as fast as with ``ensure_ascii=True``. (Contributed " +"by Naoki Inada in :issue:`23206`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2148 +msgid "" +"The :c:func:`PyObject_IsInstance` and :c:func:`PyObject_IsSubclass` " +"functions have been sped up in the common case that the second argument has :" +"class:`type` as its metaclass. (Contributed Georg Brandl by in :issue:" +"`22540`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2153 +msgid "" +"Method caching was slightly improved, yielding up to 5% performance " +"improvement in some benchmarks. (Contributed by Antoine Pitrou in :issue:" +"`22847`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2157 +msgid "" +"Objects from the :mod:`random` module now use 50% less memory on 64-bit " +"builds. (Contributed by Serhiy Storchaka in :issue:`23488`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2160 +msgid "" +"The :func:`property` getter calls are up to 25% faster. (Contributed by Joe " +"Jevnik in :issue:`23910`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2163 +msgid "" +"Instantiation of :class:`fractions.Fraction` is now up to 30% faster. " +"(Contributed by Stefan Behnel in :issue:`22464`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2166 +msgid "" +"String methods :meth:`~str.find`, :meth:`~str.rfind`, :meth:`~str.split`, :" +"meth:`~str.partition` and the :keyword:`in` string operator are now " +"significantly faster for searching 1-character substrings. (Contributed by " +"Serhiy Storchaka in :issue:`23573`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2175 +msgid "New ``calloc`` functions were added:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2177 +msgid ":c:func:`PyMem_RawCalloc`," +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2178 +msgid ":c:func:`PyMem_Calloc`," +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2179 +msgid ":c:func:`PyObject_Calloc`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2181 +msgid "(Contributed by Victor Stinner in :issue:`21233`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2183 +msgid "New encoding/decoding helper functions:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2185 +msgid ":c:func:`Py_DecodeLocale` (replaced ``_Py_char2wchar()``)," +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2186 +msgid ":c:func:`Py_EncodeLocale` (replaced ``_Py_wchar2char()``)." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2188 +msgid "(Contributed by Victor Stinner in :issue:`18395`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2190 +msgid "" +"A new :c:func:`PyCodec_NameReplaceErrors` function to replace the unicode " +"encode error with ``\\N{...}`` escapes. (Contributed by Serhiy Storchaka in :" +"issue:`19676`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2194 +msgid "" +"A new :c:func:`PyErr_FormatV` function similar to :c:func:`PyErr_Format`, " +"but accepts a ``va_list`` argument. (Contributed by Antoine Pitrou in :issue:" +"`18711`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2198 +msgid "" +"A new :c:data:`PyExc_RecursionError` exception. (Contributed by Georg Brandl " +"in :issue:`19235`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2201 +msgid "" +"New :c:func:`PyModule_FromDefAndSpec`, :c:func:`PyModule_FromDefAndSpec2`, " +"and :c:func:`PyModule_ExecDef` functions introduced by :pep:`489` -- multi-" +"phase extension module initialization. (Contributed by Petr Viktorin in :" +"issue:`24268`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2206 +msgid "" +"New :c:func:`PyNumber_MatrixMultiply` and :c:func:" +"`PyNumber_InPlaceMatrixMultiply` functions to perform matrix multiplication. " +"(Contributed by Benjamin Peterson in :issue:`21176`. See also :pep:`465` " +"for details.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2212 +msgid "" +"The :c:member:`PyTypeObject.tp_finalize` slot is now part of the stable ABI." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2214 +msgid "" +"Windows builds now require Microsoft Visual C++ 14.0, which is available as " +"part of `Visual Studio 2015 `_." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2217 +msgid "" +"Extension modules now include a platform information tag in their filename " +"on some platforms (the tag is optional, and CPython will import extensions " +"without it, although if the tag is present and mismatched, the extension " +"won't be loaded):" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2222 +msgid "" +"On Linux, extension module filenames end with ``.cpython-m-" +"-.pyd``:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2225 ../Doc/whatsnew/3.5.rst:2242 +msgid "" +"```` is the major number of the Python version; for Python 3.5 this " +"is ``3``." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2228 ../Doc/whatsnew/3.5.rst:2245 +msgid "" +"```` is the minor number of the Python version; for Python 3.5 this " +"is ``5``." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2231 +msgid "" +"```` is the hardware architecture the extension module was " +"built to run on. It's most commonly either ``i386`` for 32-bit Intel " +"platforms or ``x86_64`` for 64-bit Intel (and AMD) platforms." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2235 +msgid "" +"```` is always ``linux-gnu``, except for extensions built to talk to the " +"32-bit ABI on 64-bit platforms, in which case it is ``linux-gnu32`` (and " +"```` will be ``x86_64``)." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2239 +msgid "" +"On Windows, extension module filenames end with ``.cp-" +".pyd``:" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2248 +msgid "" +"```` is the platform the extension module was built for, either " +"``win32`` for Win32, ``win_amd64`` for Win64, ``win_ia64`` for Windows " +"Itanium 64, and ``win_arm`` for Windows on ARM." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2252 +msgid "" +"If built in debug mode, ```` will be ``_d``, otherwise it will be " +"blank." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2255 +msgid "" +"On OS X platforms, extension module filenames now end with ``-darwin.so``." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2257 +msgid "" +"On all other platforms, extension module filenames are the same as they were " +"with Python 3.4." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2265 ../Doc/whatsnew/3.6.rst:1209 +msgid "New Keywords" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2267 ../Doc/whatsnew/3.6.rst:1211 +msgid "" +"``async`` and ``await`` are not recommended to be used as variable, class, " +"function or module names. Introduced by :pep:`492` in Python 3.5, they will " +"become proper keywords in Python 3.7." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2273 +msgid "Deprecated Python Behavior" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2275 +msgid "" +"Raising the :exc:`StopIteration` exception inside a generator will now " +"generate a silent :exc:`PendingDeprecationWarning`, which will become a non-" +"silent deprecation warning in Python 3.6 and will trigger a :exc:" +"`RuntimeError` in Python 3.7. See :ref:`PEP 479: Change StopIteration " +"handling inside generators ` for details." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2285 +msgid "" +"Windows XP is no longer supported by Microsoft, thus, per :PEP:`11`, CPython " +"3.5 is no longer officially supported on this OS." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2292 +msgid "" +"The :mod:`formatter` module has now graduated to full deprecation and is " +"still slated for removal in Python 3.6." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2295 +msgid "" +"The :func:`asyncio.async` function is deprecated in favor of :func:`~asyncio." +"ensure_future`." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2298 +msgid "" +"The :mod:`smtpd` module has in the past always decoded the DATA portion of " +"email messages using the ``utf-8`` codec. This can now be controlled by the " +"new *decode_data* keyword to :class:`~smtpd.SMTPServer`. The default value " +"is ``True``, but this default is deprecated. Specify the *decode_data* " +"keyword with an appropriate value to avoid the deprecation warning." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2304 +msgid "" +"Directly assigning values to the :attr:`~http.cookies.Morsel.key`, :attr:" +"`~http.cookies.Morsel.value` and :attr:`~http.cookies.Morsel.coded_value` " +"of :class:`http.cookies.Morsel` objects is deprecated. Use the :meth:`~http." +"cookies.Morsel.set` method instead. In addition, the undocumented " +"*LegalChars* parameter of :meth:`~http.cookies.Morsel.set` is deprecated, " +"and is now ignored." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2311 +msgid "" +"Passing a format string as keyword argument *format_string* to the :meth:" +"`~string.Formatter.format` method of the :class:`string.Formatter` class has " +"been deprecated. (Contributed by Serhiy Storchaka in :issue:`23671`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2316 +msgid "" +"The :func:`platform.dist` and :func:`platform.linux_distribution` functions " +"are now deprecated. Linux distributions use too many different ways of " +"describing themselves, so the functionality is left to a package. " +"(Contributed by Vajrasky Kok and Berker Peksag in :issue:`1322`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2321 +msgid "" +"The previously undocumented ``from_function`` and ``from_builtin`` methods " +"of :class:`inspect.Signature` are deprecated. Use the new :meth:`Signature." +"from_callable() ` method instead. " +"(Contributed by Yury Selivanov in :issue:`24248`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2326 +msgid "" +"The :func:`inspect.getargspec` function is deprecated and scheduled to be " +"removed in Python 3.6. (See :issue:`20438` for details.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2329 +msgid "" +"The :mod:`inspect` :func:`~inspect.getfullargspec`, :func:`~inspect." +"getargvalues`, :func:`~inspect.getcallargs`, :func:`~inspect.getargvalues`, :" +"func:`~inspect.formatargspec`, and :func:`~inspect.formatargvalues` " +"functions are deprecated in favor of the :func:`inspect.signature` API. " +"(Contributed by Yury Selivanov in :issue:`20438`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2336 +msgid "" +"Use of :const:`re.LOCALE` flag with str patterns or :const:`re.ASCII` is now " +"deprecated. (Contributed by Serhiy Storchaka in :issue:`22407`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2339 +msgid "" +"Use of unrecognized special sequences consisting of ``'\\'`` and an ASCII " +"letter in regular expression patterns and replacement patterns now raises a " +"deprecation warning and will be forbidden in Python 3.6. (Contributed by " +"Serhiy Storchaka in :issue:`23622`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2344 +msgid "" +"The undocumented and unofficial *use_load_tests* default argument of the :" +"meth:`unittest.TestLoader.loadTestsFromModule` method now is deprecated and " +"ignored. (Contributed by Robert Collins and Barry A. Warsaw in :issue:" +"`16662`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2359 +msgid "" +"The ``__version__`` attribute has been dropped from the email package. The " +"email code hasn't been shipped separately from the stdlib for a long time, " +"and the ``__version__`` string was not updated in the last few releases." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2363 +msgid "" +"The internal ``Netrc`` class in the :mod:`ftplib` module was deprecated in " +"3.4, and has now been removed. (Contributed by Matt Chaput in :issue:`6623`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2367 +msgid "The concept of ``.pyo`` files has been removed." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2369 +msgid "" +"The JoinableQueue class in the provisional :mod:`asyncio` module was " +"deprecated in 3.4.4 and is now removed. (Contributed by A. Jesse Jiryu Davis " +"in :issue:`23464`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2375 +msgid "Porting to Python 3.5" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2382 +msgid "Changes in Python behavior" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2384 +msgid "" +"Due to an oversight, earlier Python versions erroneously accepted the " +"following syntax::" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2390 +msgid "" +"Python 3.5 now correctly raises a :exc:`SyntaxError`, as generator " +"expressions must be put in parentheses if not a sole argument to a function." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2397 +msgid "" +":pep:`475`: System calls are now retried when interrupted by a signal " +"instead of raising :exc:`InterruptedError` if the Python signal handler does " +"not raise an exception." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2401 +msgid "" +"Before Python 3.5, a :class:`datetime.time` object was considered to be " +"false if it represented midnight in UTC. This behavior was considered " +"obscure and error-prone and has been removed in Python 3.5. See :issue:" +"`13936` for full details." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2406 +msgid "" +"The :meth:`ssl.SSLSocket.send()` method now raises either :exc:`ssl." +"SSLWantReadError` or :exc:`ssl.SSLWantWriteError` on a non-blocking socket " +"if the operation would block. Previously, it would return ``0``. " +"(Contributed by Nikolaus Rath in :issue:`20951`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2411 +msgid "" +"The ``__name__`` attribute of generators is now set from the function name, " +"instead of being set from the code name. Use ``gen.gi_code.co_name`` to " +"retrieve the code name. Generators also have a new ``__qualname__`` " +"attribute, the qualified name, which is now used for the representation of a " +"generator (``repr(gen)``). (Contributed by Victor Stinner in :issue:`21205`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2418 +msgid "" +"The deprecated \"strict\" mode and argument of :class:`~html.parser." +"HTMLParser`, :meth:`HTMLParser.error`, and the :exc:`HTMLParserError` " +"exception have been removed. (Contributed by Ezio Melotti in :issue:" +"`15114`.) The *convert_charrefs* argument of :class:`~html.parser." +"HTMLParser` is now ``True`` by default. (Contributed by Berker Peksag in :" +"issue:`21047`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2424 +msgid "" +"Although it is not formally part of the API, it is worth noting for porting " +"purposes (ie: fixing tests) that error messages that were previously of the " +"form \"'sometype' does not support the buffer protocol\" are now of the form " +"\"a :term:`bytes-like object` is required, not 'sometype'\". (Contributed by " +"Ezio Melotti in :issue:`16518`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2430 +msgid "" +"If the current directory is set to a directory that no longer exists then :" +"exc:`FileNotFoundError` will no longer be raised and instead :meth:" +"`~importlib.machinery.FileFinder.find_spec` will return ``None`` **without** " +"caching ``None`` in :data:`sys.path_importer_cache`, which is different than " +"the typical case (:issue:`22834`)." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2436 +msgid "" +"HTTP status code and messages from :mod:`http.client` and :mod:`http.server` " +"were refactored into a common :class:`~http.HTTPStatus` enum. The values " +"in :mod:`http.client` and :mod:`http.server` remain available for backwards " +"compatibility. (Contributed by Demian Brecht in :issue:`21793`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2441 +msgid "" +"When an import loader defines :meth:`importlib.machinery.Loader.exec_module` " +"it is now expected to also define :meth:`~importlib.machinery.Loader." +"create_module` (raises a :exc:`DeprecationWarning` now, will be an error in " +"Python 3.6). If the loader inherits from :class:`importlib.abc.Loader` then " +"there is nothing to do, else simply define :meth:`~importlib.machinery." +"Loader.create_module` to return ``None``. (Contributed by Brett Cannon in :" +"issue:`23014`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2449 +msgid "" +"The :func:`re.split` function always ignored empty pattern matches, so the ``" +"\"x*\"`` pattern worked the same as ``\"x+\"``, and the ``\"\\b\"`` pattern " +"never worked. Now :func:`re.split` raises a warning if the pattern could " +"match an empty string. For compatibility, use patterns that never match an " +"empty string (e.g. ``\"x+\"`` instead of ``\"x*\"``). Patterns that could " +"only match an empty string (such as ``\"\\b\"``) now raise an error. " +"(Contributed by Serhiy Storchaka in :issue:`22818`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2457 +msgid "" +"The :class:`http.cookies.Morsel` dict-like interface has been made self " +"consistent: morsel comparison now takes the :attr:`~http.cookies.Morsel." +"key` and :attr:`~http.cookies.Morsel.value` into account, :meth:`~http." +"cookies.Morsel.copy` now results in a :class:`~http.cookies.Morsel` instance " +"rather than a :class:`dict`, and :meth:`~http.cookies.Morsel.update` will " +"now raise an exception if any of the keys in the update dictionary are " +"invalid. In addition, the undocumented *LegalChars* parameter of :func:" +"`~http.cookies.Morsel.set` is deprecated and is now ignored. (Contributed " +"by Demian Brecht in :issue:`2211`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2467 +msgid "" +":pep:`488` has removed ``.pyo`` files from Python and introduced the " +"optional ``opt-`` tag in ``.pyc`` file names. The :func:`importlib.util." +"cache_from_source` has gained an *optimization* parameter to help control " +"the ``opt-`` tag. Because of this, the *debug_override* parameter of the " +"function is now deprecated. `.pyo` files are also no longer supported as a " +"file argument to the Python interpreter and thus serve no purpose when " +"distributed on their own (i.e. sourcless code distribution). Due to the fact " +"that the magic number for bytecode has changed in Python 3.5, all old `.pyo` " +"files from previous versions of Python are invalid regardless of this PEP." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2478 +msgid "" +"The :mod:`socket` module now exports the :data:`~socket.CAN_RAW_FD_FRAMES` " +"constant on linux 3.6 and greater." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2481 +msgid "" +"The :func:`ssl.cert_time_to_seconds` function now interprets the input time " +"as UTC and not as local time, per :rfc:`5280`. Additionally, the return " +"value is always an :class:`int`. (Contributed by Akira Li in :issue:`19940`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2485 +msgid "" +"The ``pygettext.py`` Tool now uses the standard +NNNN format for timezones " +"in the POT-Creation-Date header." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2488 +msgid "" +"The :mod:`smtplib` module now uses :data:`sys.stderr` instead of the " +"previous module-level :data:`stderr` variable for debug output. If your " +"(test) program depends on patching the module-level variable to capture the " +"debug output, you will need to update it to capture sys.stderr instead." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2493 +msgid "" +"The :meth:`str.startswith` and :meth:`str.endswith` methods no longer return " +"``True`` when finding the empty string and the indexes are completely out of " +"range. (Contributed by Serhiy Storchaka in :issue:`24284`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2497 +msgid "" +"The :func:`inspect.getdoc` function now returns documentation strings " +"inherited from base classes. Documentation strings no longer need to be " +"duplicated if the inherited documentation is appropriate. To suppress an " +"inherited string, an empty string must be specified (or the documentation " +"may be filled in). This change affects the output of the :mod:`pydoc` " +"module and the :func:`help` function. (Contributed by Serhiy Storchaka in :" +"issue:`15582`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2505 +msgid "" +"Nested :func:`functools.partial` calls are now flattened. If you were " +"relying on the previous behavior, you can now either add an attribute to a :" +"func:`functools.partial` object or you can create a subclass of :func:" +"`functools.partial`. (Contributed by Alexander Belopolsky in :issue:`7830`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2514 +msgid "" +"The undocumented :c:member:`~PyMemoryViewObject.format` member of the (non-" +"public) :c:type:`PyMemoryViewObject` structure has been removed. All " +"extensions relying on the relevant parts in ``memoryobject.h`` must be " +"rebuilt." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2519 +msgid "" +"The :c:type:`PyMemAllocator` structure was renamed to :c:type:" +"`PyMemAllocatorEx` and a new ``calloc`` field was added." +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2522 +msgid "" +"Removed non-documented macro :c:macro:`PyObject_REPR` which leaked " +"references. Use format character ``%R`` in :c:func:`PyUnicode_FromFormat`-" +"like functions to format the :func:`repr` of the object. (Contributed by " +"Serhiy Storchaka in :issue:`22453`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2527 +msgid "" +"Because the lack of the :attr:`__module__` attribute breaks pickling and " +"introspection, a deprecation warning is now raised for builtin types without " +"the :attr:`__module__` attribute. This would be an AttributeError in the " +"future. (Contributed by Serhiy Storchaka in :issue:`20204`.)" +msgstr "" + +#: ../Doc/whatsnew/3.5.rst:2533 +msgid "" +"As part of the :pep:`492` implementation, the ``tp_reserved`` slot of :c:" +"type:`PyTypeObject` was replaced with a :c:member:`tp_as_async` slot. Refer " +"to :ref:`coro-objects` for new types, structures and functions." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:3 +msgid "What's New In Python 3.6" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:5 +msgid "|release|" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:6 +msgid "|today|" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:48 +msgid "This article explains the new features in Python 3.6, compared to 3.5." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:50 +msgid "For full details, see the :ref:`changelog `." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:54 +msgid "" +"Prerelease users should be aware that this document is currently in draft " +"form. It will be updated substantially as Python 3.6 moves towards release, " +"so it's worth checking back even after reading earlier versions." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:67 +msgid "" +"A ``global`` or ``nonlocal`` statement must now textually appear before the " +"first use of the affected name in the same scope. Previously this was a " +"SyntaxWarning." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:71 +msgid "PEP 498: :ref:`Formatted string literals `" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:73 ../Doc/whatsnew/3.6.rst:166 +msgid "PEP 515: Underscores in Numeric Literals" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:75 +msgid "PEP 526: :ref:`Syntax for Variable Annotations `" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:77 +msgid "PEP 525: Asynchronous Generators" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:79 +msgid "PEP 530: Asynchronous Comprehensions" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:81 +msgid "Standard library improvements:" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:85 ../Doc/whatsnew/3.6.rst:586 +msgid "" +"On Linux, :func:`os.urandom` now blocks until the system urandom entropy " +"pool is initialized to increase the security. See the :pep:`524` for the " +"rationale." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:89 +msgid ":mod:`hashlib` and :mod:`ssl` now support OpenSSL 1.1.0." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:91 +msgid "" +"The default settings and feature set of the :mod:`ssl` have been improved." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:93 +msgid "" +"The :mod:`hashlib` module has got support for BLAKE2, SHA-3 and SHAKE hash " +"algorithms and :func:`~hashlib.scrypt` key derivation function." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:98 +msgid "PEP 529: :ref:`Change Windows filesystem encoding to UTF-8 `" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:100 +msgid "PEP 528: :ref:`Change Windows console encoding to UTF-8 `" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:102 +msgid "" +"The ``py.exe`` launcher, when used interactively, no longer prefers Python 2 " +"over Python 3 when the user doesn't specify a version (via command line " +"arguments or a config file). Handling of shebang lines remains unchanged - " +"\"python\" refers to Python 2 in that case." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:107 +msgid "" +"``python.exe`` and ``pythonw.exe`` have been marked as long-path aware, " +"which means that when the 260 character path limit may no longer apply. See :" +"ref:`removing the MAX_PATH limitation ` for details." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:111 +msgid "" +"A ``._pth`` file can be added to force isolated mode and fully specify all " +"search paths to avoid registry and environment lookup. See :ref:`the " +"documentation ` for more information." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:115 +msgid "" +"A ``python36.zip`` file now works as a landmark to infer :envvar:" +"`PYTHONHOME`. See :ref:`the documentation ` for more " +"information." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:136 +msgid "" +"PEP 520: :ref:`Preserving Class Attribute Definition Order`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:138 +msgid "PEP 468: :ref:`Preserving Keyword Argument Order`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:140 +msgid "A complete list of PEP's implemented in Python 3.6:" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:142 +msgid ":pep:`468`, :ref:`Preserving Keyword Argument Order`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:143 +msgid "" +":pep:`487`, :ref:`Simpler customization of class creation`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:144 +msgid ":pep:`495`, Local Time Disambiguation" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:145 +msgid ":pep:`498`, :ref:`Formatted string literals `" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:146 +msgid ":pep:`506`, Adding A Secrets Module To The Standard Library" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:147 +msgid ":pep:`509`, :ref:`Add a private version to dict`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:148 +msgid ":pep:`515`, :ref:`Underscores in Numeric Literals`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:149 +msgid ":pep:`519`, :ref:`Adding a file system path protocol`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:150 +msgid "" +":pep:`520`, :ref:`Preserving Class Attribute Definition Order`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:151 +msgid ":pep:`523`, :ref:`Adding a frame evaluation API to CPython`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:152 +msgid ":pep:`524`, Make os.urandom() blocking on Linux (during system startup)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:153 +msgid ":pep:`525`, Asynchronous Generators (provisional)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:154 +msgid "" +":pep:`526`, :ref:`Syntax for Variable Annotations (provisional)`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:155 +msgid "" +":pep:`528`, :ref:`Change Windows console encoding to UTF-8 " +"(provisional)`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:156 +msgid "" +":pep:`529`, :ref:`Change Windows filesystem encoding to UTF-8 " +"(provisional)`" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:157 +msgid ":pep:`530`, Asynchronous Comprehensions" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:168 +msgid "" +"Prior to PEP 515, there was no support for writing long numeric literals " +"with some form of separator to improve readability. For instance, how big is " +"``1000000000000000``? With :pep:`515`, though, you can use underscores to " +"separate digits as desired to make numeric literals easier to read: " +"``1_000_000_000_000_000``. Underscores can be used with other numeric " +"literals beyond integers, e.g. ``0x_FF_FF_FF_FF``." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:176 +msgid "" +"Single underscores are allowed between digits and after any base specifier. " +"More than a single underscore in a row, leading, or trailing underscores are " +"not allowed." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:182 +msgid ":pep:`515` -- Underscores in Numeric Literals" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:183 +msgid "PEP written by Georg Brandl and Serhiy Storchaka." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:189 +msgid "PEP 523: Adding a frame evaluation API to CPython" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:191 +msgid "" +"While Python provides extensive support to customize how code executes, one " +"place it has not done so is in the evaluation of frame objects. If you " +"wanted some way to intercept frame evaluation in Python there really wasn't " +"any way without directly manipulating function pointers for defined " +"functions." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:197 +msgid "" +":pep:`523` changes this by providing an API to make frame evaluation " +"pluggable at the C level. This will allow for tools such as debuggers and " +"JITs to intercept frame evaluation before the execution of Python code " +"begins. This enables the use of alternative evaluation implementations for " +"Python code, tracking frame evaluation, etc." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:204 +msgid "" +"This API is not part of the limited C API and is marked as private to signal " +"that usage of this API is expected to be limited and only applicable to very " +"select, low-level use-cases. Semantics of the API will change with Python as " +"necessary." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:211 +msgid ":pep:`523` -- Adding a frame evaluation API to CPython" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:212 +msgid "PEP written by Brett Cannon and Dino Viehland." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:218 +msgid "PEP 519: Adding a file system path protocol" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:220 +msgid "" +"File system paths have historically been represented as :class:`str` or :" +"class:`bytes` objects. This has led to people who write code which operate " +"on file system paths to assume that such objects are only one of those two " +"types (an :class:`int` representing a file descriptor does not count as that " +"is not a file path). Unfortunately that assumption prevents alternative " +"object representations of file system paths like :mod:`pathlib` from working " +"with pre-existing code, including Python's standard library." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:229 +msgid "" +"To fix this situation, a new interface represented by :class:`os.PathLike` " +"has been defined. By implementing the :meth:`~os.PathLike.__fspath__` " +"method, an object signals that it represents a path. An object can then " +"provide a low-level representation of a file system path as a :class:`str` " +"or :class:`bytes` object. This means an object is considered :term:`path-" +"like ` if it implements :class:`os.PathLike` or is a :" +"class:`str` or :class:`bytes` object which represents a file system path. " +"Code can use :func:`os.fspath`, :func:`os.fsdecode`, or :func:`os.fsencode` " +"to explicitly get a :class:`str` and/or :class:`bytes` representation of a " +"path-like object." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:242 +msgid "" +"The built-in :func:`open` function has been updated to accept :class:`os." +"PathLike` objects as have all relevant functions in the :mod:`os` and :mod:" +"`os.path` modules. :c:func:`PyUnicode_FSConverter` and :c:func:" +"`PyUnicode_FSConverter` have been changed to accept path-like objects. The :" +"class:`os.DirEntry` class and relevant classes in :mod:`pathlib` have also " +"been updated to implement :class:`os.PathLike`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:250 +msgid "" +"The hope in is that updating the fundamental functions for operating on file " +"system paths will lead to third-party code to implicitly support all :term:" +"`path-like objects ` without any code changes or at least " +"very minimal ones (e.g. calling :func:`os.fspath` at the beginning of code " +"before operating on a path-like object)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:257 +msgid "" +"Here are some examples of how the new interface allows for :class:`pathlib." +"Path` to be used more easily and transparently with pre-existing code::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:274 +msgid "" +"(Implemented by Brett Cannon, Ethan Furman, Dusty Phillips, and Jelle " +"Zijlstra.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:278 +msgid ":pep:`519` -- Adding a file system path protocol" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:279 +msgid "PEP written by Brett Cannon and Koos Zevenhoven." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:285 +msgid "PEP 498: Formatted string literals" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:287 +msgid "" +"Formatted string literals are a new kind of string literal, prefixed with " +"``'f'``. They are similar to the format strings accepted by :meth:`str." +"format`. They contain replacement fields surrounded by curly braces. The " +"replacement fields are expressions, which are evaluated at run time, and " +"then formatted using the :func:`format` protocol::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:297 +msgid "See :pep:`498` and the main documentation at :ref:`f-strings`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:303 +msgid "PEP 526: Syntax for variable annotations" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:305 +msgid "" +":pep:`484` introduced standard for type annotations of function parameters, " +"a.k.a. type hints. This PEP adds syntax to Python for annotating the types " +"of variables including class variables and instance variables::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:316 +msgid "" +"Just as for function annotations, the Python interpreter does not attach any " +"particular meaning to variable annotations and only stores them in a special " +"attribute ``__annotations__`` of a class or module. In contrast to variable " +"declarations in statically typed languages, the goal of annotation syntax is " +"to provide an easy way to specify structured type metadata for third party " +"tools and libraries via the abstract syntax tree and the ``__annotations__`` " +"attribute." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:328 +msgid ":pep:`526` -- Syntax for variable annotations." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:327 +msgid "" +"PEP written by Ryan Gonzalez, Philip House, Ivan Levkivskyi, Lisa Roach, and " +"Guido van Rossum. Implemented by Ivan Levkivskyi." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:330 +msgid "" +"Tools that use or will use the new syntax: `mypy `_, `pytype `_, PyCharm, etc." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:338 +msgid "PEP 529: Change Windows filesystem encoding to UTF-8" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:340 +msgid "" +"Representing filesystem paths is best performed with str (Unicode) rather " +"than bytes. However, there are some situations where using bytes is " +"sufficient and correct." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:344 +msgid "" +"Prior to Python 3.6, data loss could result when using bytes paths on " +"Windows. With this change, using bytes to represent paths is now supported " +"on Windows, provided those bytes are encoded with the encoding returned by :" +"func:`sys.getfilesystemencoding()`, which now defaults to ``'utf-8'``." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:349 +msgid "" +"Applications that do not use str to represent paths should use :func:`os." +"fsencode()` and :func:`os.fsdecode()` to ensure their bytes are correctly " +"encoded. To revert to the previous behaviour, set :envvar:" +"`PYTHONLEGACYWINDOWSFSENCODING` or call :func:`sys." +"_enablelegacywindowsfsencoding`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:355 +msgid "" +"See :pep:`529` for more information and discussion of code modifications " +"that may be required." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:360 +msgid "" +"This change is considered experimental for 3.6.0 beta releases. The default " +"encoding may change before the final release." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:366 +msgid "PEP 487: Simpler customization of class creation" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:368 +msgid "" +"Upon subclassing a class, the ``__init_subclass__`` classmethod (if defined) " +"is called on the base class. This makes it straightforward to write classes " +"that customize initialization of future subclasses without introducing the " +"complexity of a full custom metaclass." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:373 +msgid "" +"The descriptor protocol has also been expanded to include a new optional " +"method, ``__set_name__``. Whenever a new class is defined, the new method " +"will be called on all descriptors included in the definition, providing them " +"with a reference to the class being defined and the name given to the " +"descriptor within the class namespace." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:379 +msgid "" +"Also see :pep:`487` and the updated class customization documentation at :" +"ref:`class-customization` and :ref:`descriptors`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:382 +msgid "(Contributed by Martin Teichmann in :issue:`27366`)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:387 +msgid "PEP 528: Change Windows console encoding to UTF-8" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:389 +msgid "" +"The default console on Windows will now accept all Unicode characters and " +"provide correctly read str objects to Python code. ``sys.stdin``, ``sys." +"stdout`` and ``sys.stderr`` now default to utf-8 encoding." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:393 +msgid "" +"This change only applies when using an interactive console, and not when " +"redirecting files or pipes. To revert to the previous behaviour for " +"interactive console use, set :envvar:`PYTHONLEGACYWINDOWSIOENCODING`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:399 +msgid ":pep:`528` -- Change Windows console encoding to UTF-8" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:400 +msgid "PEP written and implemented by Steve Dower." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:403 +msgid "PYTHONMALLOC environment variable" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:405 +msgid "" +"The new :envvar:`PYTHONMALLOC` environment variable allows setting the " +"Python memory allocators and/or install debug hooks." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:408 +msgid "" +"It is now possible to install debug hooks on Python memory allocators on " +"Python compiled in release mode using ``PYTHONMALLOC=debug``. Effects of " +"debug hooks:" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:411 +msgid "Newly allocated memory is filled with the byte ``0xCB``" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:412 +msgid "Freed memory is filled with the byte ``0xDB``" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:413 +msgid "" +"Detect violations of Python memory allocator API. For example, :c:func:" +"`PyObject_Free` called on a memory block allocated by :c:func:`PyMem_Malloc`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:416 +msgid "Detect write before the start of the buffer (buffer underflow)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:417 +msgid "Detect write after the end of the buffer (buffer overflow)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:418 +msgid "" +"Check that the :term:`GIL ` is held when allocator " +"functions of :c:data:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) and :" +"c:data:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) domains are called." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:422 +msgid "Checking if the GIL is held is also a new feature of Python 3.6." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:424 +msgid "" +"See the :c:func:`PyMem_SetupDebugHooks` function for debug hooks on Python " +"memory allocators." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:427 +msgid "" +"It is now also possible to force the usage of the :c:func:`malloc` allocator " +"of the C library for all Python memory allocations using " +"``PYTHONMALLOC=malloc``. It helps to use external memory debuggers like " +"Valgrind on a Python compiled in release mode." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:432 +msgid "" +"On error, the debug hooks on Python memory allocators now use the :mod:" +"`tracemalloc` module to get the traceback where a memory block was allocated." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:436 +msgid "" +"Example of fatal error on buffer overflow using ``python3.6 -X " +"tracemalloc=5`` (store 5 frames in traces)::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:473 +msgid "(Contributed by Victor Stinner in :issue:`26516` and :issue:`26564`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:477 +msgid "DTrace and SystemTap probing support" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:479 +msgid "" +"Python can now be built ``--with-dtrace`` which enables static markers for " +"the following events in the interpreter:" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:482 +msgid "function call/return" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:484 +msgid "garbage collection started/finished" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:486 +msgid "line of code executed." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:488 +msgid "" +"This can be used to instrument running interpreters in production, without " +"the need to recompile specific debug builds or providing application-" +"specific profiling/debugging code." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:492 +msgid "More details in :ref:`instrumentation`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:494 +msgid "" +"The current implementation is tested on Linux and macOS. Additional markers " +"may be added in the future." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:497 +msgid "" +"(Contributed by Łukasz Langa in :issue:`21590`, based on patches by Jesús " +"Cea Avión, David Malcolm, and Nikhil Benesch.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:504 +msgid "PEP 520: Preserving Class Attribute Definition Order" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:506 +msgid "" +"Attributes in a class definition body have a natural ordering: the same " +"order in which the names appear in the source. This order is now preserved " +"in the new class's ``__dict__`` attribute." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:510 +msgid "" +"Also, the effective default class *execution* namespace (returned from " +"``type.__prepare__()``) is now an insertion-order-preserving mapping." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:515 +msgid ":pep:`520` -- Preserving Class Attribute Definition Order" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:522 +msgid "PEP 468: Preserving Keyword Argument Order" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:524 +msgid "" +"``**kwargs`` in a function signature is now guaranteed to be an insertion-" +"order-preserving mapping." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:529 +msgid ":pep:`468` -- Preserving Keyword Argument Order" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:535 +msgid "PEP 509: Add a private version to dict" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:537 +msgid "" +"Add a new private version to the builtin ``dict`` type, incremented at each " +"dictionary creation and at each dictionary change, to implement fast guards " +"on namespaces." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:541 +msgid "(Contributed by Victor Stinner in :issue:`26058`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:549 +msgid "" +":func:`dict` now uses a \"compact\" representation `pioneered by PyPy " +"`_. The memory usage of the new :func:`dict` is between 20% and 25% " +"smaller compared to Python 3.5. :pep:`468` (Preserving the order of " +"``**kwargs`` in a function.) is implemented by this. The order-preserving " +"aspect of this new implementation is considered an implementation detail and " +"should not be relied upon (this may change in the future, but it is desired " +"to have this new dict implementation in the language for a few releases " +"before changing the language spec to mandate order-preserving semantics for " +"all current and future Python implementations; this also helps preserve " +"backwards-compatibility with older versions of the language where random " +"iteration order is still in effect, e.g. Python 3.5). (Contributed by INADA " +"Naoki in :issue:`27350`. Idea `originally suggested by Raymond Hettinger " +"`_.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:567 +msgid "" +"Long sequences of repeated traceback lines are now abbreviated as ``" +"\"[Previous line repeated {count} more times]\"`` (see :ref:`py36-traceback` " +"for an example). (Contributed by Emanuel Barry in :issue:`26823`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:572 +msgid "" +"Import now raises the new exception :exc:`ModuleNotFoundError` (subclass of :" +"exc:`ImportError`) when it cannot find a module. Code that current checks " +"for ImportError (in try-except) will still work." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:580 ../Doc/whatsnew/3.6.rst:1233 +msgid "None yet." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:593 +msgid "" +"Since the :mod:`asyncio` module is :term:`provisional `, " +"all changes introduced in Python 3.6 have also been backported to Python 3.5." +"x." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:597 +msgid "Notable changes in the :mod:`asyncio` module since Python 3.5.0:" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:632 +msgid "" +"The :meth:`loop.getaddrinfo() ` method is " +"optimized to avoid calling the system ``getaddrinfo`` function if the " +"address is already resolved. (Contributed by A. Jesse Jiryu Davis.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:641 +msgid "" +"The :class:`contextlib.AbstractContextManager` class has been added to " +"provide an abstract base class for context managers. It provides a sensible " +"default implementation for `__enter__()` which returns ``self`` and leaves " +"`__exit__()` an abstract method. A matching class has been added to the :mod:" +"`typing` module as :class:`typing.ContextManager`. (Contributed by Brett " +"Cannon in :issue:`25609`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:653 +msgid "" +":mod:`venv` accepts a new parameter ``--prompt``. This parameter provides an " +"alternative prefix for the virtual environment. (Proposed by Łukasz." +"Balcerzak and ported to 3.6 by Stéphane Wirtel in :issue:`22829`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:661 +msgid "" +"The :meth:`datetime.strftime() ` and :meth:`date." +"strftime() ` methods now support ISO 8601 date " +"directives ``%G``, ``%u`` and ``%V``. (Contributed by Ashley Anderson in :" +"issue:`12006`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:668 +msgid "distutils.command.sdist" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:670 +msgid "" +"The ``default_format`` attribute has been removed from :class:`distutils." +"command.sdist.sdist` and the ``formats`` attribute defaults to " +"``['gztar']``. Although not anticipated, Any code relying on the presence of " +"``default_format`` may need to be adapted. See :issue:`27819` for more " +"details." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:680 +msgid "" +"The new email API, enabled via the *policy* keyword to various constructors, " +"is no longer provisional. The :mod:`email` documentation has been " +"reorganized and rewritten to focus on the new API, while retaining the old " +"documentation for the legacy API. (Contributed by R. David Murray in :issue:" +"`24277`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:685 +msgid "" +"The :mod:`email.mime` classes now all accept an optional *policy* keyword. " +"(Contributed by Berker Peksag in :issue:`27331`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:688 +msgid "" +"The :class:`~email.generator.DecodedGenerator` now supports the *policy* " +"keyword." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:691 +msgid "" +"There is a new :mod:`~email.policy` attribute, :attr:`~email.policy.Policy." +"message_factory`, that controls what class is used by default when the " +"parser creates new message objects. For the :attr:`email.policy.compat32` " +"policy this is :class:`~email.message.Message`, for the new policies it is :" +"class:`~email.message.EmailMessage`. (Contributed by R. David Murray in :" +"issue:`20476`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:700 +msgid "encodings" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:702 +msgid "" +"On Windows, added the ``'oem'`` encoding to use ``CP_OEMCP`` and the " +"``'ansi'`` alias for the existing ``'mbcs'`` encoding, which uses the " +"``CP_ACP`` code page." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:709 +msgid "" +"On Windows, the :mod:`faulthandler` module now installs a handler for " +"Windows exceptions: see :func:`faulthandler.enable`. (Contributed by Victor " +"Stinner in :issue:`23848`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:717 +msgid "" +":mod:`hashlib` supports OpenSSL 1.1.0. The minimum recommend version is " +"1.0.2. It has been tested with 0.9.8zc, 0.9.8zh and 1.0.1t as well as " +"LibreSSL 2.3 and 2.4. (Contributed by Christian Heimes in :issue:`26470`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:722 +msgid "" +"BLAKE2 hash functions were added to the module. :func:`~hashlib.blake2b` " +"and :func:`~hashlib.blake2s` are always available and support the full " +"feature set of BLAKE2. (Contributed by Christian Heimes in :issue:`26798` " +"based on code by Dmitry Chestnykh and Samuel Neves. Documentation written by " +"Dmitry Chestnykh.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:728 +msgid "" +"The SHA-3 hash functions :func:`~hashlib.sha3_224`, :func:`~hashlib." +"sha3_256`, :func:`~hashlib.sha3_384`, :func:`~hashlib.sha3_512`, and SHAKE " +"hash functions :func:`~hashlib.shake_128` and :func:`~hashlib.shake_256` " +"were added. (Contributed by Christian Heimes in :issue:`16113`. Keccak Code " +"Package by Guido Bertoni, Joan Daemen, Michaël Peeters, Gilles Van Assche, " +"and Ronny Van Keer.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:735 +msgid "" +"The password-based key derivation function :func:`~hashlib.scrypt` is now " +"available with OpenSSL 1.1.0 and newer. (Contributed by Christian Heimes in :" +"issue:`27928`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:742 +msgid "" +":meth:`HTTPConnection.request() ` and :" +"meth:`~http.client.HTTPConnection.endheaders` both now support chunked " +"encoding request bodies. (Contributed by Demian Brecht and Rolf Krahl in :" +"issue:`12319`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:751 +msgid "" +"The idlelib package is being modernized and refactored to make IDLE look and " +"work better and to make the code easier to understand, test, and improve. " +"Part of making IDLE look better, especially on Linux and Mac, is using ttk " +"widgets, mostly in the dialogs. As a result, IDLE no longer runs with tcl/" +"tk 8.4. It now requires tcl/tk 8.5 or 8.6. We recommend running the latest " +"release of either." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:753 +msgid "" +"'Modernizing' includes renaming and consolidation of idlelib modules. The " +"renaming of files with partial uppercase names is similar to the renaming " +"of, for instance, Tkinter and TkFont to tkinter and tkinter.font in 3.0. As " +"a result, imports of idlelib files that worked in 3.5 will usually not work " +"in 3.6. At least a module name change will be needed (see idlelib/README." +"txt), sometimes more. (Name changes contributed by Al Swiegart and Terry " +"Reedy in :issue:`24225`. Most idlelib patches since have been and will be " +"part of the process.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:755 +msgid "" +"In compensation, the eventual result with be that some idlelib classes will " +"be easier to use, with better APIs and docstrings explaining them. " +"Additional useful information will be added to idlelib when available." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:761 +msgid "" +":class:`importlib.util.LazyLoader` now calls :meth:`~importlib.abc.Loader." +"create_module` on the wrapped loader, removing the restriction that :class:" +"`importlib.machinery.BuiltinImporter` and :class:`importlib.machinery." +"ExtensionFileLoader` couldn't be used with :class:`importlib.util." +"LazyLoader`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:767 +msgid "" +":func:`importlib.util.cache_from_source`, :func:`importlib.util." +"source_from_cache`, and :func:`importlib.util.spec_from_file_location` now " +"accept a :term:`path-like object`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:776 +msgid "" +":func:`json.load` and :func:`json.loads` now support binary input. Encoded " +"JSON should be represented using either UTF-8, UTF-16, or UTF-32. " +"(Contributed by Serhiy Storchaka in :issue:`17909`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:784 +msgid "" +"A new :meth:`~os.scandir.close` method allows explicitly closing a :func:" +"`~os.scandir` iterator. The :func:`~os.scandir` iterator now supports the :" +"term:`context manager` protocol. If a :func:`scandir` iterator is neither " +"exhausted nor explicitly closed a :exc:`ResourceWarning` will be emitted in " +"its destructor. (Contributed by Serhiy Storchaka in :issue:`25994`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:791 +msgid "" +"The Linux ``getrandom()`` syscall (get random bytes) is now exposed as the " +"new :func:`os.getrandom` function. (Contributed by Victor Stinner, part of " +"the :pep:`524`)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:795 +msgid "" +"See the summary for :ref:`PEP 519 ` for details on how the :mod:" +"`os` and :mod:`os.path` modules now support :term:`path-like objects `." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:803 +msgid "" +"Objects that need calling ``__new__`` with keyword arguments can now be " +"pickled using :ref:`pickle protocols ` older than protocol " +"version 4. Protocol version 4 already supports this case. (Contributed by " +"Serhiy Storchaka in :issue:`24164`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:812 +msgid "" +"Added support of modifier spans in regular expressions. Examples: ``'(?i:" +"p)ython'`` matches ``'python'`` and ``'Python'``, but not ``'PYTHON'``; ``'(?" +"i)g(?-i:v)r'`` matches ``'GvR'`` and ``'gvr'``, but not ``'GVR'``. " +"(Contributed by Serhiy Storchaka in :issue:`433028`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:817 +msgid "" +"Match object groups can be accessed by ``__getitem__``, which is equivalent " +"to ``group()``. So ``mo['name']`` is now equivalent to ``mo." +"group('name')``. (Contributed by Eric Smith in :issue:`24454`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:825 +msgid "" +"Added :func:`~readline.set_auto_history` to enable or disable automatic " +"addition of input to the history list. (Contributed by Tyler Crompton in :" +"issue:`26870`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:831 +msgid "rlcompleter" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:833 +msgid "" +"Private and special attribute names now are omitted unless the prefix starts " +"with underscores. A space or a colon is added after some completed " +"keywords. (Contributed by Serhiy Storchaka in :issue:`25011` and :issue:" +"`25209`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:837 +msgid "" +"Names of most attributes listed by :func:`dir` are now completed. " +"Previously, names of properties and slots which were not yet created on an " +"instance were excluded. (Contributed by Martin Panter in :issue:`25590`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:845 +msgid "" +"When specifying paths to add to :attr:`sys.path` in a `.pth` file, you may " +"now specify file paths on top of directories (e.g. zip files). (Contributed " +"by Wolfgang Langner in :issue:`26587`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:853 +msgid "" +":attr:`sqlite3.Cursor.lastrowid` now supports the ``REPLACE`` statement. " +"(Contributed by Alex LordThorsen in :issue:`16864`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:860 +msgid "" +"The :func:`~socket.socket.ioctl` function now supports the :data:`~socket." +"SIO_LOOPBACK_FAST_PATH` control code. (Contributed by Daniel Stokes in :" +"issue:`26536`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:864 +msgid "" +"The :meth:`~socket.socket.getsockopt` constants ``SO_DOMAIN``, " +"``SO_PROTOCOL``, ``SO_PEERSEC``, and ``SO_PASSSEC`` are now supported. " +"(Contributed by Christian Heimes in :issue:`26907`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:868 +msgid "" +"The socket module now supports the address family :data:`~socket.AF_ALG` to " +"interface with Linux Kernel crypto API. ``ALG_*``, ``SOL_ALG`` and :meth:" +"`~socket.socket.sendmsg_afalg` were added. (Contributed by Christian Heimes " +"in :issue:`27744` with support from Victor Stinner.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:877 +msgid "" +"Servers based on the :mod:`socketserver` module, including those defined in :" +"mod:`http.server`, :mod:`xmlrpc.server` and :mod:`wsgiref.simple_server`, " +"now support the :term:`context manager` protocol. (Contributed by Aviv " +"Palivoda in :issue:`26404`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:883 +msgid "" +"The :attr:`~socketserver.StreamRequestHandler.wfile` attribute of :class:" +"`~socketserver.StreamRequestHandler` classes now implements the :class:`io." +"BufferedIOBase` writable interface. In particular, calling :meth:`~io." +"BufferedIOBase.write` is now guaranteed to send the data in full. " +"(Contributed by Martin Panter in :issue:`26721`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:892 +msgid "" +":mod:`ssl` supports OpenSSL 1.1.0. The minimum recommend version is 1.0.2. " +"It has been tested with 0.9.8zc, 0.9.8zh and 1.0.1t as well as LibreSSL 2.3 " +"and 2.4. (Contributed by Christian Heimes in :issue:`26470`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:897 +msgid "" +"3DES has been removed from the default cipher suites and ChaCha20 Poly1305 " +"cipher suites are now in the right position. (Contributed by Christian " +"Heimes in :issue:`27850` and :issue:`27766`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:901 +msgid "" +":class:`~ssl.SSLContext` has better default configuration for options and " +"ciphers. (Contributed by Christian Heimes in :issue:`28043`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:905 +msgid "" +"SSL session can be copied from one client-side connection to another with :" +"class:`~ssl.SSLSession`. TLS session resumption can speed up the initial " +"handshake, reduce latency and improve performance (Contributed by Christian " +"Heimes in :issue:`19500` based on a draft by Alex Warhawk.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:911 +msgid "" +"All constants and flags have been converted to :class:`~enum.IntEnum` and :" +"class:`~enum.IntFlags`. (Contributed by Christian Heimes in :issue:`28025`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:915 +msgid "" +"Server and client-side specific TLS protocols for :class:`~ssl.SSLContext` " +"were added. (Contributed by Christian Heimes in :issue:`28085`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:919 +msgid "" +"General resource ids (``GEN_RID``) in subject alternative name extensions no " +"longer case a SystemError. (Contributed by Christian Heimes in :issue:" +"`27691`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:926 +msgid "" +":class:`subprocess.Popen` destructor now emits a :exc:`ResourceWarning` " +"warning if the child process is still running. Use the context manager " +"protocol (``with proc: ...``) or call explicitly the :meth:`~subprocess." +"Popen.wait` method to read the exit status of the child process (Contributed " +"by Victor Stinner in :issue:`26741`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:932 +msgid "" +"The :class:`subprocess.Popen` constructor and all functions that pass " +"arguments through to it now accept *encoding* and *errors* arguments. " +"Specifying either of these will enable text mode for the *stdin*, *stdout* " +"and *stderr* streams." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:937 +msgid "telnetlib" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:939 +msgid "" +":class:`~telnetlib.Telnet` is now a context manager (contributed by Stéphane " +"Wirtel in :issue:`25485`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:946 +msgid "" +"Added methods :meth:`~tkinter.Variable.trace_add`, :meth:`~tkinter.Variable." +"trace_remove` and :meth:`~tkinter.Variable.trace_info` in the :class:" +"`tkinter.Variable` class. They replace old methods :meth:`~tkinter.Variable." +"trace_variable`, :meth:`~tkinter.Variable.trace`, :meth:`~tkinter.Variable." +"trace_vdelete` and :meth:`~tkinter.Variable.trace_vinfo` that use obsolete " +"Tcl commands and might not work in future versions of Tcl. (Contributed by " +"Serhiy Storchaka in :issue:`22115`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:961 +msgid "" +"Both the traceback module and the interpreter's builtin exception display " +"now abbreviate long sequences of repeated lines in tracebacks as shown in " +"the following example::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:976 +msgid "(Contributed by Emanuel Barry in :issue:`26823`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:982 +msgid "" +"The :class:`typing.ContextManager` class has been added for representing :" +"class:`contextlib.AbstractContextManager`. (Contributed by Brett Cannon in :" +"issue:`25609`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:990 +msgid "" +"The internal database has been upgraded to use Unicode 9.0.0. (Contributed " +"by Benjamin Peterson.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:999 +msgid "" +"Two new methods, :meth:`Mock.assert_called() ` and :meth:`Mock.assert_called_once() ` to check if the mock object was called. (Contributed by " +"Amit Saha in :issue:`26323`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1007 +msgid "urllib.request" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1009 +msgid "" +"If a HTTP request has a file or iterable body (other than a bytes object) " +"but no Content-Length header, rather than throwing an error, :class:`~urllib." +"request.AbstractHTTPHandler` now falls back to use chunked transfer " +"encoding. (Contributed by Demian Brecht and Rolf Krahl in :issue:`12319`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1017 +msgid "urllib.robotparser" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1019 +msgid "" +":class:`~urllib.robotparser.RobotFileParser` now supports the ``Crawl-" +"delay`` and ``Request-rate`` extensions. (Contributed by Nikolay Bogoychev " +"in :issue:`16099`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1025 +msgid "warnings" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1027 +msgid "" +"A new optional *source* parameter has been added to the :func:`warnings." +"warn_explicit` function: the destroyed object which emitted a :exc:" +"`ResourceWarning`. A *source* attribute has also been added to :class:" +"`warnings.WarningMessage` (contributed by Victor Stinner in :issue:`26568` " +"and :issue:`26567`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1033 +msgid "" +"When a :exc:`ResourceWarning` warning is logged, the :mod:`tracemalloc` is " +"now used to try to retrieve the traceback where the detroyed object was " +"allocated." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1036 +msgid "Example with the script ``example.py``::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1046 +msgid "Output of the command ``python3.6 -Wd -X tracemalloc=5 example.py``::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1056 +msgid "" +"The \"Object allocated at\" traceback is new and only displayed if :mod:" +"`tracemalloc` is tracing Python memory allocations and if the :mod:" +"`warnings` was already imported." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1064 +msgid "" +"Added the 64-bit integer type :data:`REG_QWORD `. " +"(Contributed by Clement Rouault in :issue:`23026`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1069 +msgid "winsound" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1071 +msgid "" +"Allowed keyword arguments to be passed to :func:`Beep `, :" +"func:`MessageBeep `, and :func:`PlaySound ` (:issue:`27982`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1077 +msgid "xmlrpc.client" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1079 +msgid "" +"The module now supports unmarshalling additional data types used by Apache " +"XML-RPC implementation for numerics and ``None``. (Contributed by Serhiy " +"Storchaka in :issue:`26885`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1087 +msgid "" +"A new :meth:`ZipInfo.from_file() ` class method " +"allows making a :class:`~zipfile.ZipInfo` instance from a filesystem file. A " +"new :meth:`ZipInfo.is_dir() ` method can be used to " +"check if the :class:`~zipfile.ZipInfo` instance represents a directory. " +"(Contributed by Thomas Kluyver in :issue:`26039`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1093 +msgid "" +"The :meth:`ZipFile.open() ` method can now be used to " +"write data into a ZIP file, as well as for extracting data. (Contributed by " +"Thomas Kluyver in :issue:`26039`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1101 +msgid "" +"The :func:`~zlib.compress` function now accepts keyword arguments. " +"(Contributed by Aviv Palivoda in :issue:`26243`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1106 +msgid "fileinput" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1108 +msgid "" +":func:`~fileinput.hook_encoded` now supports the *errors* argument. " +"(Contributed by Joseph Hackman in :issue:`25788`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1115 +msgid "" +"The ASCII decoder is now up to 60 times as fast for error handlers " +"``surrogateescape``, ``ignore`` and ``replace`` (Contributed by Victor " +"Stinner in :issue:`24870`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1119 +msgid "" +"The ASCII and the Latin1 encoders are now up to 3 times as fast for the " +"error handler ``surrogateescape`` (Contributed by Victor Stinner in :issue:" +"`25227`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1122 +msgid "" +"The UTF-8 encoder is now up to 75 times as fast for error handlers " +"``ignore``, ``replace``, ``surrogateescape``, ``surrogatepass`` (Contributed " +"by Victor Stinner in :issue:`25267`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1126 +msgid "" +"The UTF-8 decoder is now up to 15 times as fast for error handlers " +"``ignore``, ``replace`` and ``surrogateescape`` (Contributed by Victor " +"Stinner in :issue:`25301`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1130 +msgid "" +"``bytes % args`` is now up to 2 times faster. (Contributed by Victor Stinner " +"in :issue:`25349`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1133 +msgid "" +"``bytearray % args`` is now between 2.5 and 5 times faster. (Contributed by " +"Victor Stinner in :issue:`25399`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1136 +msgid "" +"Optimize :meth:`bytes.fromhex` and :meth:`bytearray.fromhex`: they are now " +"between 2x and 3.5x faster. (Contributed by Victor Stinner in :issue:" +"`25401`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1139 +msgid "" +"Optimize ``bytes.replace(b'', b'.')`` and ``bytearray.replace(b'', b'.')``: " +"up to 80% faster. (Contributed by Josh Snider in :issue:`26574`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1142 +msgid "" +"Allocator functions of the :c:func:`PyMem_Malloc` domain (:c:data:" +"`PYMEM_DOMAIN_MEM`) now use the :ref:`pymalloc memory allocator ` " +"instead of :c:func:`malloc` function of the C library. The pymalloc " +"allocator is optimized for objects smaller or equal to 512 bytes with a " +"short lifetime, and use :c:func:`malloc` for larger memory blocks. " +"(Contributed by Victor Stinner in :issue:`26249`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1149 +msgid "" +":func:`pickle.load` and :func:`pickle.loads` are now up to 10% faster when " +"deserializing many small objects (Contributed by Victor Stinner in :issue:" +"`27056`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1153 +msgid "" +"Passing :term:`keyword arguments ` to a function has an " +"overhead in comparison with passing :term:`positional arguments `. Now in extension functions implemented with using Argument " +"Clinic this overhead is significantly decreased. (Contributed by Serhiy " +"Storchaka in :issue:`27574`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1159 +msgid "" +"Optimized :func:`~glob.glob` and :func:`~glob.iglob` functions in the :mod:" +"`glob` module; they are now about 3--6 times faster. (Contributed by Serhiy " +"Storchaka in :issue:`25596`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1163 +msgid "" +"Optimized globbing in :mod:`pathlib` by using :func:`os.scandir`; it is now " +"about 1.5--4 times faster. (Contributed by Serhiy Storchaka in :issue:" +"`26032`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1170 +msgid "" +"Python now requires some C99 support in the toolchain to build. For more " +"information, see :pep:`7`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1173 +msgid "" +"Cross-compiling CPython with the Android NDK and the Android API level set " +"to 21 (Android 5.0 Lollilop) or greater, runs successfully. While Android is " +"not yet a supported platform, the Python test suite runs on the Android " +"emulator with only about 16 tests failures. See the Android meta-issue :" +"issue:`26865`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1178 +msgid "" +"The ``--with-optimizations`` configure flag has been added. Turning it on " +"will activate LTO and PGO build support (when available). (Original patch by " +"Alecsandru Patrascu of Intel in :issue:`26539`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1182 +msgid "" +"New :c:func:`Py_FinalizeEx` API which indicates if flushing buffered data " +"failed (:issue:`5319`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1185 +msgid "" +":c:func:`PyArg_ParseTupleAndKeywords` now supports :ref:`positional-only " +"parameters `. Positional-only parameters are " +"defined by empty names. (Contributed by Serhiy Storchaka in :issue:`26282`)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1190 +msgid "" +"``PyTraceback_Print`` method now abbreviates long sequences of repeated " +"lines as ``\"[Previous line repeated {count} more times]\"``. (Contributed " +"by Emanuel Barry in :issue:`26823`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1199 +msgid "Deprecated Build Options" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1201 +msgid "" +"The ``--with-system-ffi`` configure flag is now on by default on non-OSX " +"UNIX platforms. It may be disabled by using ``--without-system-ffi``, but " +"using the flag is deprecated and will not be accepted in Python 3.7. OSX is " +"unaffected by this change. Note that many OS distributors already use the " +"``--with-system-ffi`` flag when building their system Python." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1219 +msgid "" +":meth:`importlib.machinery.SourceFileLoader.load_module` and :meth:" +"`importlib.machinery.SourcelessFileLoader.load_module` are now deprecated. " +"They were the only remaining implementations of :meth:`importlib.abc.Loader." +"load_module` in :mod:`importlib` that had not been deprecated in previous " +"versions of Python in favour of :meth:`importlib.abc.Loader.exec_module`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1226 +msgid "" +"The :mod:`tkinter.tix` module is now deprecated. :mod:`tkinter` users " +"should use :mod:`tkinter.ttk` instead." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1239 +msgid "" +"The ``pyvenv`` script has been deprecated in favour of ``python3 -m venv``. " +"This prevents confusion as to what Python interpreter ``pyvenv`` is " +"connected to and thus what Python interpreter will be used by the virtual " +"environment. (Contributed by Brett Cannon in :issue:`25154`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1244 +msgid "" +"When performing a relative import, falling back on ``__name__`` and " +"``__path__`` from the calling module when ``__spec__`` or ``__package__`` " +"are not defined now raises an :exc:`ImportWarning`. (Contributed by Rose " +"Ames in :issue:`25791`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1249 +msgid "" +"Unlike to other :mod:`dbm` implementations, the :mod:`dbm.dumb` module " +"creates database in ``'r'`` and ``'w'`` modes if it doesn't exist and allows " +"modifying database in ``'r'`` mode. This behavior is now deprecated and " +"will be removed in 3.8. (Contributed by Serhiy Storchaka in :issue:`21708`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1255 +msgid "" +"Undocumented support of general :term:`bytes-like objects ` as paths in :mod:`os` functions, :func:`compile` and similar " +"functions is now deprecated. (Contributed by Serhiy Storchaka in :issue:" +"`25791` and :issue:`26754`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1260 +msgid "" +"The undocumented ``extra_path`` argument to a distutils Distribution is now " +"considered deprecated, will raise a warning during install if set. Support " +"for this parameter will be dropped in a future Python release and likely " +"earlier through third party tools. See :issue:`27919` for details." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1266 +msgid "" +"A backslash-character pair that is not a valid escape sequence now generates " +"a DeprecationWarning. Although this will eventually become a SyntaxError, " +"that will not be for several Python releases. (Contributed by Emanuel Barry " +"in :issue:`27364`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1271 +msgid "" +"Inline flags ``(?letters)`` now should be used only at the start of the " +"regular expression. Inline flags in the middle of the regular expression " +"affects global flags in Python :mod:`re` module. This is an exception to " +"other regular expression engines that either apply flags to only part of the " +"regular expression or treat them as an error. To avoid distinguishing " +"inline flags in the middle of the regular expression now emit a deprecation " +"warning. It will be an error in future Python releases. (Contributed by " +"Serhiy Storchaka in :issue:`22493`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1280 +msgid "" +"SSL-related arguments like ``certfile``, ``keyfile`` and ``check_hostname`` " +"in :mod:`ftplib`, :mod:`http.client`, :mod:`imaplib`, :mod:`poplib`, and :" +"mod:`smtplib` have been deprecated in favor of ``context``. (Contributed by " +"Christian Heimes in :issue:`28022`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1285 +msgid "" +"A couple of protocols and functions of the :mod:`ssl` module are now " +"deprecated. Some features will no longer be available in future versions of " +"OpenSSL. Other features are deprecated in favor of a different API. " +"(Contributed by Christian Heimes in :issue:`28022` and :issue:`26470`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1292 +msgid "Deprecated Python behavior" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1294 +msgid "" +"Raising the :exc:`StopIteration` exception inside a generator will now " +"generate a :exc:`DeprecationWarning`, and will trigger a :exc:`RuntimeError` " +"in Python 3.7. See :ref:`whatsnew-pep-479` for details." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1305 +msgid "" +"``inspect.getmoduleinfo()`` was removed (was deprecated since CPython 3.3). :" +"func:`inspect.getmodulename` should be used for obtaining the module name " +"for a given path." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1309 +msgid "" +"``traceback.Ignore`` class and ``traceback.usage``, ``traceback.modname``, " +"``traceback.fullmodname``, ``traceback.find_lines_from_code``, ``traceback." +"find_lines``, ``traceback.find_strings``, ``traceback." +"find_executable_lines`` methods were removed from the :mod:`traceback` " +"module. They were undocumented methods deprecated since Python 3.2 and " +"equivalent functionality is available from private methods." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1316 +msgid "" +"The ``tk_menuBar()`` and ``tk_bindForTraversal()`` dummy methods in :mod:" +"`tkinter` widget classes were removed (corresponding Tk commands were " +"obsolete since Tk 4.0)." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1320 +msgid "" +"The :meth:`~zipfile.ZipFile.open` method of the :class:`zipfile.ZipFile` " +"class no longer supports the ``'U'`` mode (was deprecated since Python 3.4). " +"Use :class:`io.TextIOWrapper` for reading compressed text files in :term:" +"`universal newlines` mode." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1325 +msgid "" +"The undocumented ``IN``, ``CDROM``, ``DLFCN``, ``TYPES``, ``CDIO``, and " +"``STROPTS`` modules have been removed. They had been available in the " +"platform specific ``Lib/plat-*/`` directories, but were chronically out of " +"date, inconsistently available across platforms, and unmaintained. The " +"script that created these modules is still available in the source " +"distribution at :source:`Tools/scripts/h2py.py`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1334 +msgid "Porting to Python 3.6" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1342 +msgid "" +"The output of a special Python build with defined ``COUNT_ALLOCS``, " +"``SHOW_ALLOC_COUNT`` or ``SHOW_TRACK_COUNT`` macros is now off by default. " +"It can be re-enabled using the ``-X showalloccount`` option. It now outputs " +"to ``stderr`` instead of ``stdout``. (Contributed by Serhiy Storchaka in :" +"issue:`23034`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1352 +msgid "" +":mod:`sqlite3` no longer implicitly commit an open transaction before DDL " +"statements." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1355 +msgid "" +"On Linux, :func:`os.urandom` now blocks until the system urandom entropy " +"pool is initialized to increase the security." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1358 +msgid "" +"When :meth:`importlib.abc.Loader.exec_module` is defined, :meth:`importlib." +"abc.Loader.create_module` must also be defined." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1361 +msgid "" +":c:func:`PyErr_SetImportError` now sets :exc:`TypeError` when its **msg** " +"argument is not set. Previously only ``NULL`` was returned." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1364 +msgid "" +"The format of the ``co_lnotab`` attribute of code objects changed to support " +"negative line number delta. By default, Python does not emit bytecode with " +"negative line number delta. Functions using ``frame.f_lineno``, " +"``PyFrame_GetLineNumber()`` or ``PyCode_Addr2Line()`` are not affected. " +"Functions decoding directly ``co_lnotab`` should be updated to use a signed " +"8-bit integer type for the line number delta, but it's only required to " +"support applications using negative line number delta. See ``Objects/" +"lnotab_notes.txt`` for the ``co_lnotab`` format and how to decode it, and " +"see the :pep:`511` for the rationale." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1374 +msgid "" +"The functions in the :mod:`compileall` module now return booleans instead of " +"``1`` or ``0`` to represent success or failure, respectively. Thanks to " +"booleans being a subclass of integers, this should only be an issue if you " +"were doing identity checks for ``1`` or ``0``. See :issue:`25768`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1379 +msgid "" +"Reading the :attr:`~urllib.parse.SplitResult.port` attribute of :func:" +"`urllib.parse.urlsplit` and :func:`~urllib.parse.urlparse` results now " +"raises :exc:`ValueError` for out-of-range values, rather than returning :" +"const:`None`. See :issue:`20059`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1384 +msgid "" +"The :mod:`imp` module now raises a :exc:`DeprecationWarning` instead of :exc:" +"`PendingDeprecationWarning`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1387 +msgid "" +"The following modules have had missing APIs added to their :attr:`__all__` " +"attributes to match the documented APIs: :mod:`calendar`, :mod:`cgi`, :mod:" +"`csv`, :mod:`~xml.etree.ElementTree`, :mod:`enum`, :mod:`fileinput`, :mod:" +"`ftplib`, :mod:`logging`, :mod:`mailbox`, :mod:`mimetypes`, :mod:" +"`optparse`, :mod:`plistlib`, :mod:`smtpd`, :mod:`subprocess`, :mod:" +"`tarfile`, :mod:`threading` and :mod:`wave`. This means they will export " +"new symbols when ``import *`` is used. See :issue:`23883`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1397 +msgid "" +"When performing a relative import, if ``__package__`` does not compare equal " +"to ``__spec__.parent`` then :exc:`ImportWarning` is raised. (Contributed by " +"Brett Cannon in :issue:`25791`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1401 +msgid "" +"When a relative import is performed and no parent package is known, then :" +"exc:`ImportError` will be raised. Previously, :exc:`SystemError` could be " +"raised. (Contributed by Brett Cannon in :issue:`18018`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1405 +msgid "" +"Servers based on the :mod:`socketserver` module, including those defined in :" +"mod:`http.server`, :mod:`xmlrpc.server` and :mod:`wsgiref.simple_server`, " +"now only catch exceptions derived from :exc:`Exception`. Therefore if a " +"request handler raises an exception like :exc:`SystemExit` or :exc:" +"`KeyboardInterrupt`, :meth:`~socketserver.BaseServer.handle_error` is no " +"longer called, and the exception will stop a single-threaded server. " +"(Contributed by Martin Panter in :issue:`23430`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1414 +msgid "" +":func:`spwd.getspnam` now raises a :exc:`PermissionError` instead of :exc:" +"`KeyError` if the user doesn't have privileges." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1417 +msgid "" +"The :meth:`socket.socket.close` method now raises an exception if an error " +"(e.g. EBADF) was reported by the underlying system call. See :issue:`26685`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1421 +msgid "" +"The *decode_data* argument for :class:`smtpd.SMTPChannel` and :class:`smtpd." +"SMTPServer` constructors is now ``False`` by default. This means that the " +"argument passed to :meth:`~smtpd.SMTPServer.process_message` is now a bytes " +"object by default, and ``process_message()`` will be passed keyword " +"arguments. Code that has already been updated in accordance with the " +"deprecation warning generated by 3.5 will not be affected." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1429 +msgid "" +"All optional parameters of the :func:`~json.dump`, :func:`~json.dumps`, :" +"func:`~json.load` and :func:`~json.loads` functions and :class:`~json." +"JSONEncoder` and :class:`~json.JSONDecoder` class constructors in the :mod:" +"`json` module are now :ref:`keyword-only `. " +"(Contributed by Serhiy Storchaka in :issue:`18726`.)" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1436 +msgid "" +"As part of :pep:`487`, the handling of keyword arguments passed to :class:" +"`type` (other than the metaclass hint, ``metaclass``) is now consistently " +"delegated to :meth:`object.__init_subclass__`. This means that :meth:`type." +"__new__` and :meth:`type.__init__` both now accept arbitrary keyword " +"arguments, but :meth:`object.__init_subclass__` (which is called from :meth:" +"`type.__new__`) will reject them by default. Custom metaclasses accepting " +"additional keyword arguments will need to adjust their calls to :meth:`type." +"__new__` (whether direct or via :class:`super`) accordingly." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1445 +msgid "" +"In :class:`distutils.command.sdist.sdist`, the ``default_format`` attribute " +"has been removed and is no longer honored. Instead, the gzipped tarfile " +"format is the default on all platforms and no platform-specific selection is " +"made. In environments where distributions are built on Windows and zip " +"distributions are required, configure the project with a ``setup.cfg`` file " +"containing the following::" +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1456 +msgid "" +"This behavior has also been backported to earlier Python versions by " +"Setuptools 26.0.0." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1459 +msgid "" +"In the :mod:`urllib.request` module and the :meth:`http.client." +"HTTPConnection.request` method, if no Content-Length header field has been " +"specified and the request body is a file object, it is now sent with HTTP " +"1.1 chunked encoding. If a file object has to be sent to a HTTP 1.0 server, " +"the Content-Length value now has to be specified by the caller. See :issue:" +"`12319`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1469 +msgid "" +":c:func:`PyMem_Malloc` allocator family now uses the :ref:`pymalloc " +"allocator ` rather than system :c:func:`malloc`. Applications " +"calling :c:func:`PyMem_Malloc` without holding the GIL can now crash. Set " +"the :envvar:`PYTHONMALLOC` environment variable to ``debug`` to validate the " +"usage of memory allocators in your application. See :issue:`26249`." +msgstr "" + +#: ../Doc/whatsnew/3.6.rst:1475 +msgid "" +":c:func:`Py_Exit` (and the main interpreter) now override the exit status " +"with 120 if flushing buffered data failed. See :issue:`5319`." +msgstr "" + +#: ../Doc/whatsnew/changelog.rst:5 +msgid "Changelog" +msgstr "" + +#: ../../../Misc/NEWS:5 +msgid "Python 3.6.0 beta 3" +msgstr "" + +#: ../../../Misc/NEWS:7 +msgid "*Release date: XXXX-XX-XX*" +msgstr "" + +#: ../../../Misc/NEWS:10 ../../../Misc/NEWS:39 ../../../Misc/NEWS:304 +#: ../../../Misc/NEWS:803 ../../../Misc/NEWS:1040 ../../../Misc/NEWS:1248 +#: ../../../Misc/NEWS:1543 ../../../Misc/NEWS:2828 ../../../Misc/NEWS:2846 +#: ../../../Misc/NEWS:3363 ../../../Misc/NEWS:3398 ../../../Misc/NEWS:3426 +#: ../../../Misc/NEWS:3517 ../../../Misc/NEWS:3600 ../../../Misc/NEWS:3705 +#: ../../../Misc/NEWS:3747 ../../../Misc/NEWS:4023 ../../../Misc/NEWS:4254 +#: ../../../Misc/NEWS:4440 ../../../Misc/NEWS:4580 ../../../Misc/NEWS:6419 +#: ../../../Misc/NEWS:6456 ../../../Misc/NEWS:6535 ../../../Misc/NEWS:6798 +#: ../../../Misc/NEWS:7038 ../../../Misc/NEWS:7414 ../../../Misc/NEWS:7888 +#: ../../../Misc/NEWS:8118 ../../../Misc/NEWS:8239 ../../../Misc/NEWS:8508 +msgid "Core and Builtins" +msgstr "" + +#: ../../../Misc/NEWS:13 ../../../Misc/NEWS:108 ../../../Misc/NEWS:439 +#: ../../../Misc/NEWS:848 ../../../Misc/NEWS:1057 ../../../Misc/NEWS:1288 +#: ../../../Misc/NEWS:1827 ../../../Misc/NEWS:2912 ../../../Misc/NEWS:3346 +#: ../../../Misc/NEWS:3373 ../../../Misc/NEWS:3411 ../../../Misc/NEWS:3431 +#: ../../../Misc/NEWS:3538 ../../../Misc/NEWS:3627 ../../../Misc/NEWS:3723 +#: ../../../Misc/NEWS:3800 ../../../Misc/NEWS:4055 ../../../Misc/NEWS:4274 +#: ../../../Misc/NEWS:4447 ../../../Misc/NEWS:4807 ../../../Misc/NEWS:6402 +#: ../../../Misc/NEWS:6425 ../../../Misc/NEWS:6472 ../../../Misc/NEWS:6562 +#: ../../../Misc/NEWS:6819 ../../../Misc/NEWS:7083 ../../../Misc/NEWS:7475 +#: ../../../Misc/NEWS:7940 ../../../Misc/NEWS:8126 ../../../Misc/NEWS:8285 +#: ../../../Misc/NEWS:8925 +msgid "Library" +msgstr "" + +#: ../../../Misc/NEWS:15 +msgid "" +"`Issue #24452 `__: Make webbrowser support " +"Chrome on Mac OS X." +msgstr "" + +#: ../../../Misc/NEWS:17 +msgid "" +"`Issue #20766 `__: Fix references leaked by " +"pdb in the handling of SIGINT handlers." +msgstr "" + +#: ../../../Misc/NEWS:21 ../../../Misc/NEWS:282 ../../../Misc/NEWS:726 +#: ../../../Misc/NEWS:1012 ../../../Misc/NEWS:1196 ../../../Misc/NEWS:1508 +#: ../../../Misc/NEWS:2708 ../../../Misc/NEWS:3274 ../../../Misc/NEWS:3334 +#: ../../../Misc/NEWS:3351 ../../../Misc/NEWS:3589 ../../../Misc/NEWS:3693 +#: ../../../Misc/NEWS:4203 ../../../Misc/NEWS:4415 ../../../Misc/NEWS:4551 +#: ../../../Misc/NEWS:6075 ../../../Misc/NEWS:6432 ../../../Misc/NEWS:6517 +#: ../../../Misc/NEWS:6770 ../../../Misc/NEWS:7026 ../../../Misc/NEWS:7364 +#: ../../../Misc/NEWS:7820 ../../../Misc/NEWS:8094 ../../../Misc/NEWS:8220 +#: ../../../Misc/NEWS:8485 ../../../Misc/NEWS:10398 +msgid "Build" +msgstr "" + +#: ../../../Misc/NEWS:23 +msgid "" +"`Issue #28208 `__: Update Windows build to " +"use SQLite 3.14.2.0." +msgstr "" + +#: ../../../Misc/NEWS:25 +msgid "" +"`Issue #28248 `__: Update Windows build to " +"use OpenSSL 1.0.2j." +msgstr "" + +#: ../../../Misc/NEWS:28 ../../../Misc/NEWS:293 ../../../Misc/NEWS:712 +#: ../../../Misc/NEWS:985 ../../../Misc/NEWS:1236 ../../../Misc/NEWS:1491 +#: ../../../Misc/NEWS:2665 ../../../Misc/NEWS:3261 ../../../Misc/NEWS:3504 +#: ../../../Misc/NEWS:3677 ../../../Misc/NEWS:3985 ../../../Misc/NEWS:4211 +#: ../../../Misc/NEWS:4420 ../../../Misc/NEWS:6224 ../../../Misc/NEWS:6726 +#: ../../../Misc/NEWS:6925 ../../../Misc/NEWS:7328 ../../../Misc/NEWS:7788 +#: ../../../Misc/NEWS:8075 ../../../Misc/NEWS:8199 ../../../Misc/NEWS:8452 +#: ../../../Misc/NEWS:10177 +msgid "Tests" +msgstr "" + +#: ../../../Misc/NEWS:30 +msgid "" +"`Issue #28409 `__: regrtest: fix the parser " +"of command line arguments." +msgstr "" + +#: ../../../Misc/NEWS:34 +msgid "Python 3.6.0 beta 2" +msgstr "" + +#: ../../../Misc/NEWS:36 +msgid "*Release date: 2016-10-10*" +msgstr "" + +#: ../../../Misc/NEWS:41 +msgid "" +"`Issue #28183 `__: Optimize and cleanup dict " +"iteration." +msgstr "" + +#: ../../../Misc/NEWS:43 +msgid "" +"`Issue #26081 `__: Added C implementation of " +"asyncio.Future. Original patch by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:46 +msgid "" +"`Issue #28379 `__: Added sanity checks and " +"tests for PyUnicode_CopyCharacters(). Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:49 +msgid "" +"`Issue #28376 `__: The type of long range " +"iterator is now registered as Iterator. Patch by Oren Milman." +msgstr "" + +#: ../../../Misc/NEWS:52 +msgid "" +"`Issue #28376 `__: Creating instances of " +"range_iterator by calling range_iterator type now is deprecated. Patch by " +"Oren Milman." +msgstr "" + +#: ../../../Misc/NEWS:55 +msgid "" +"`Issue #28376 `__: The constructor of " +"range_iterator now checks that step is not 0. Patch by Oren Milman." +msgstr "" + +#: ../../../Misc/NEWS:58 +msgid "" +"`Issue #26906 `__: Resolving special methods " +"of uninitialized type now causes implicit initialization of the type instead " +"of a fail." +msgstr "" + +#: ../../../Misc/NEWS:61 +msgid "" +"`Issue #18287 `__: PyType_Ready() now checks " +"that tp_name is not NULL. Original patch by Niklas Koep." +msgstr "" + +#: ../../../Misc/NEWS:64 +msgid "" +"`Issue #24098 `__: Fixed possible crash when " +"AST is changed in process of compiling it." +msgstr "" + +#: ../../../Misc/NEWS:67 +msgid "" +"`Issue #28201 `__: Dict reduces possibility " +"of 2nd conflict in hash table when hashes have same lower bits." +msgstr "" + +#: ../../../Misc/NEWS:70 +msgid "" +"`Issue #28350 `__: String constants with null " +"character no longer interned." +msgstr "" + +#: ../../../Misc/NEWS:72 +msgid "" +"`Issue #26617 `__: Fix crash when GC runs " +"during weakref callbacks." +msgstr "" + +#: ../../../Misc/NEWS:74 +msgid "" +"`Issue #27942 `__: String constants now " +"interned recursively in tuples and frozensets." +msgstr "" + +#: ../../../Misc/NEWS:76 +msgid "" +"`Issue #21578 `__: Fixed misleading error " +"message when ImportError called with invalid keyword args." +msgstr "" + +#: ../../../Misc/NEWS:79 +msgid "" +"`Issue #28203 `__: Fix incorrect type in " +"complex(1.0, {2:3}) error message. Patch by Soumya Sharma." +msgstr "" + +#: ../../../Misc/NEWS:82 +msgid "" +"`Issue #28086 `__: Single var-positional " +"argument of tuple subtype was passed unscathed to the C-defined function. " +"Now it is converted to exact tuple." +msgstr "" + +#: ../../../Misc/NEWS:85 +msgid "" +"`Issue #28214 `__: Now __set_name__ is looked " +"up on the class instead of the instance." +msgstr "" + +#: ../../../Misc/NEWS:88 +msgid "" +"`Issue #27955 `__: Fallback on reading /dev/" +"urandom device when the getrandom() syscall fails with EPERM, for example " +"when blocked by SECCOMP." +msgstr "" + +#: ../../../Misc/NEWS:91 +msgid "" +"`Issue #28192 `__: Don't import readline in " +"isolated mode." +msgstr "" + +#: ../../../Misc/NEWS:93 +msgid "Upgrade internal unicode databases to Unicode version 9.0.0." +msgstr "" + +#: ../../../Misc/NEWS:95 +msgid "" +"`Issue #28131 `__: Fix a regression in " +"zipimport's compile_source(). zipimport should use the same optimization " +"level as the interpreter." +msgstr "" + +#: ../../../Misc/NEWS:98 +msgid "" +"`Issue #28126 `__: Replace Py_MEMCPY with " +"memcpy(). Visual Studio can properly optimize memcpy()." +msgstr "" + +#: ../../../Misc/NEWS:101 +msgid "" +"`Issue #28120 `__: Fix dict.pop() for " +"splitted dictionary when trying to remove a \"pending key\" (Not yet " +"inserted in split-table). Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:104 +msgid "" +"`Issue #26182 `__: Raise DeprecationWarning " +"when async and await keywords are used as variable/attribute/class/function " +"name." +msgstr "" + +#: ../../../Misc/NEWS:110 +msgid "" +"`Issue #27998 `__: Fixed bytes path support " +"in os.scandir() on Windows. Patch by Eryk Sun." +msgstr "" + +#: ../../../Misc/NEWS:113 +msgid "" +"`Issue #28317 `__: The disassembler now " +"decodes FORMAT_VALUE argument." +msgstr "" + +#: ../../../Misc/NEWS:115 +msgid "" +"`Issue #26293 `__: Fixed writing ZIP files " +"that starts not from the start of the file. Offsets in ZIP file now are " +"relative to the start of the archive in conforming to the specification." +msgstr "" + +#: ../../../Misc/NEWS:119 +msgid "" +"`Issue #28380 `__: unittest.mock Mock " +"autospec functions now properly support assert_called, assert_not_called, " +"and assert_called_once." +msgstr "" + +#: ../../../Misc/NEWS:122 +msgid "" +"`Issue #27181 `__ remove statistics." +"geometric_mean and defer until 3.7." +msgstr "" + +#: ../../../Misc/NEWS:124 +msgid "" +"`Issue #28229 `__: lzma module now supports " +"pathlib." +msgstr "" + +#: ../../../Misc/NEWS:126 +msgid "" +"`Issue #28321 `__: Fixed writing non-BMP " +"characters with binary format in plistlib." +msgstr "" + +#: ../../../Misc/NEWS:128 +msgid "" +"`Issue #28225 `__: bz2 module now supports " +"pathlib. Initial patch by Ethan Furman." +msgstr "" + +#: ../../../Misc/NEWS:130 +msgid "" +"`Issue #28227 `__: gzip now supports " +"pathlib. Patch by Ethan Furman." +msgstr "" + +#: ../../../Misc/NEWS:132 +msgid "" +"`Issue #27358 `__: Optimized merging var-" +"keyword arguments and improved error message when pass a non-mapping as a " +"var-keyword argument." +msgstr "" + +#: ../../../Misc/NEWS:135 +msgid "" +"`Issue #28257 `__: Improved error message " +"when pass a non-iterable as a var-positional argument. Added opcode " +"BUILD_TUPLE_UNPACK_WITH_CALL." +msgstr "" + +#: ../../../Misc/NEWS:138 +msgid "" +"`Issue #28322 `__: Fixed possible crashes " +"when unpickle itertools objects from incorrect pickle data. Based on patch " +"by John Leitch." +msgstr "" + +#: ../../../Misc/NEWS:141 +msgid "" +"`Issue #28228 `__: imghdr now supports " +"pathlib." +msgstr "" + +#: ../../../Misc/NEWS:143 +msgid "" +"`Issue #28226 `__: compileall now supports " +"pathlib." +msgstr "" + +#: ../../../Misc/NEWS:145 +msgid "" +"`Issue #28314 `__: Fix function declaration " +"(C flags) for the getiterator() method of xml.etree.ElementTree.Element." +msgstr "" + +#: ../../../Misc/NEWS:148 +msgid "" +"`Issue #28148 `__: Stop using localtime() and " +"gmtime() in the time module." +msgstr "" + +#: ../../../Misc/NEWS:151 +msgid "" +"Introduced platform independent _PyTime_localtime API that is similar to " +"POSIX localtime_r, but available on all platforms. Patch by Ed Schouten." +msgstr "" + +#: ../../../Misc/NEWS:155 +msgid "" +"`Issue #28253 `__: Fixed calendar functions " +"for extreme months: 0001-01 and 9999-12." +msgstr "" + +#: ../../../Misc/NEWS:158 +msgid "" +"Methods itermonthdays() and itermonthdays2() are reimplemented so that they " +"don't call itermonthdates() which can cause datetime.date under/overflow." +msgstr "" + +#: ../../../Misc/NEWS:162 +msgid "" +"`Issue #28275 `__: Fixed possible use after " +"free in the decompress() methods of the LZMADecompressor and BZ2Decompressor " +"classes. Original patch by John Leitch." +msgstr "" + +#: ../../../Misc/NEWS:166 +msgid "" +"`Issue #27897 `__: Fixed possible crash in " +"sqlite3.Connection.create_collation() if pass invalid string-like object as " +"a name. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:169 +msgid "" +"`Issue #18844 `__: random.choices() now has k " +"as a keyword-only argument to improve the readability of common cases and " +"the come into line with the signature used in other languages." +msgstr "" + +#: ../../../Misc/NEWS:173 +msgid "" +"`Issue #18893 `__: Fix invalid exception " +"handling in Lib/ctypes/macholib/dyld.py. Patch by Madison May." +msgstr "" + +#: ../../../Misc/NEWS:176 +msgid "" +"`Issue #27611 `__: Fixed support of default " +"root window in the tkinter.tix module. Added the master parameter in the " +"DisplayStyle constructor." +msgstr "" + +#: ../../../Misc/NEWS:179 +msgid "" +"`Issue #27348 `__: In the traceback module, " +"restore the formatting of exception messages like \"Exception: None\". This " +"fixes a regression introduced in 3.5a2." +msgstr "" + +#: ../../../Misc/NEWS:183 +msgid "" +"`Issue #25651 `__: Allow falsy values to be " +"used for msg parameter of subTest()." +msgstr "" + +#: ../../../Misc/NEWS:185 +msgid "" +"`Issue #27778 `__: Fix a memory leak in os." +"getrandom() when the getrandom() is interrupted by a signal and a signal " +"handler raises a Python exception." +msgstr "" + +#: ../../../Misc/NEWS:188 +msgid "" +"`Issue #28200 `__: Fix memory leak on Windows " +"in the os module (fix path_converter() function)." +msgstr "" + +#: ../../../Misc/NEWS:191 +msgid "" +"`Issue #25400 `__: RobotFileParser now " +"correctly returns default values for crawl_delay and request_rate. Initial " +"patch by Peter Wirtz." +msgstr "" + +#: ../../../Misc/NEWS:194 +msgid "" +"`Issue #27932 `__: Prevent memory leak in " +"win32_ver()." +msgstr "" + +#: ../../../Misc/NEWS:196 +msgid "Fix UnboundLocalError in socket._sendfile_use_sendfile." +msgstr "" + +#: ../../../Misc/NEWS:198 +msgid "" +"`Issue #28075 `__: Check for " +"ERROR_ACCESS_DENIED in Windows implementation of os.stat(). Patch by Eryk " +"Sun." +msgstr "" + +#: ../../../Misc/NEWS:201 +msgid "" +"`Issue #22493 `__: Warning message emitted by " +"using inline flags in the middle of regular expression now contains a " +"(truncated) regex pattern. Patch by Tim Graham." +msgstr "" + +#: ../../../Misc/NEWS:205 +msgid "" +"`Issue #25270 `__: Prevent codecs." +"escape_encode() from raising SystemError when an empty bytestring is passed." +msgstr "" + +#: ../../../Misc/NEWS:208 +msgid "" +"`Issue #28181 `__: Get antigravity over " +"HTTPS. Patch by Kaartic Sivaraam." +msgstr "" + +#: ../../../Misc/NEWS:210 +msgid "" +"`Issue #25895 `__: Enable WebSocket URL " +"schemes in urllib.parse.urljoin. Patch by Gergely Imreh and Markus " +"Holtermann." +msgstr "" + +#: ../../../Misc/NEWS:213 +msgid "" +"`Issue #28114 `__: Fix a crash in " +"parse_envlist() when env contains byte strings. Patch by Eryk Sun." +msgstr "" + +#: ../../../Misc/NEWS:216 +msgid "" +"`Issue #27599 `__: Fixed buffer overrun in " +"binascii.b2a_qp() and binascii.a2b_qp()." +msgstr "" + +#: ../../../Misc/NEWS:218 +msgid "" +"`Issue #27906 `__: Fix socket accept " +"exhaustion during high TCP traffic. Patch by Kevin Conway." +msgstr "" + +#: ../../../Misc/NEWS:221 +msgid "" +"`Issue #28174 `__: Handle when SO_REUSEPORT " +"isn't properly supported. Patch by Seth Michael Larson." +msgstr "" + +#: ../../../Misc/NEWS:224 +msgid "" +"`Issue #26654 `__: Inspect functools.partial " +"in asyncio.Handle.__repr__. Patch by iceboy." +msgstr "" + +#: ../../../Misc/NEWS:227 +msgid "" +"`Issue #26909 `__: Fix slow pipes IO in " +"asyncio. Patch by INADA Naoki." +msgstr "" + +#: ../../../Misc/NEWS:230 +msgid "" +"`Issue #28176 `__: Fix callbacks race in " +"asyncio.SelectorLoop.sock_connect." +msgstr "" + +#: ../../../Misc/NEWS:232 +msgid "" +"`Issue #27759 `__: Fix selectors incorrectly " +"retain invalid file descriptors. Patch by Mark Williams." +msgstr "" + +#: ../../../Misc/NEWS:235 +msgid "" +"`Issue #28368 `__: Refuse monitoring " +"processes if the child watcher has no loop attached. Patch by Vincent Michel." +msgstr "" + +#: ../../../Misc/NEWS:239 +msgid "" +"`Issue #28369 `__: Raise RuntimeError when " +"transport's FD is used with add_reader, add_writer, etc." +msgstr "" + +#: ../../../Misc/NEWS:242 +msgid "" +"`Issue #28370 `__: Speedup asyncio." +"StreamReader.readexactly. Patch by Коренберг Марк." +msgstr "" + +#: ../../../Misc/NEWS:245 +msgid "" +"`Issue #28371 `__: Deprecate passing asyncio." +"Handles to run_in_executor." +msgstr "" + +#: ../../../Misc/NEWS:247 +msgid "" +"`Issue #28372 `__: Fix asyncio to support " +"formatting of non-python coroutines." +msgstr "" + +#: ../../../Misc/NEWS:249 +msgid "" +"`Issue #28399 `__: Remove UNIX socket from FS " +"before binding. Patch by Коренберг Марк." +msgstr "" + +#: ../../../Misc/NEWS:252 +msgid "" +"`Issue #27972 `__: Prohibit Tasks to await on " +"themselves." +msgstr "" + +#: ../../../Misc/NEWS:255 ../../../Misc/NEWS:768 ../../../Misc/NEWS:1000 +#: ../../../Misc/NEWS:1501 ../../../Misc/NEWS:2771 ../../../Misc/NEWS:2834 +#: ../../../Misc/NEWS:3285 ../../../Misc/NEWS:4565 ../../../Misc/NEWS:6370 +#: ../../../Misc/NEWS:10691 +msgid "Windows" +msgstr "" + +#: ../../../Misc/NEWS:257 +msgid "" +"`Issue #28402 `__: Adds signed catalog files " +"for stdlib on Windows." +msgstr "" + +#: ../../../Misc/NEWS:259 +msgid "" +"`Issue #28333 `__: Enables Unicode for ps1/" +"ps2 and input() prompts. (Patch by Eryk Sun)" +msgstr "" + +#: ../../../Misc/NEWS:262 +msgid "" +"`Issue #28251 `__: Improvements to help " +"manuals on Windows." +msgstr "" + +#: ../../../Misc/NEWS:264 +msgid "" +"`Issue #28110 `__: launcher.msi has different " +"product codes between 32-bit and 64-bit" +msgstr "" + +#: ../../../Misc/NEWS:267 +msgid "" +"`Issue #28161 `__: Opening CON for write " +"access fails" +msgstr "" + +#: ../../../Misc/NEWS:269 +msgid "" +"`Issue #28162 `__: WindowsConsoleIO readall() " +"fails if first line starts with Ctrl+Z" +msgstr "" + +#: ../../../Misc/NEWS:272 +msgid "" +"`Issue #28163 `__: WindowsConsoleIO fileno() " +"passes wrong flags to _open_osfhandle" +msgstr "" + +#: ../../../Misc/NEWS:275 +msgid "" +"`Issue #28164 `__: _PyIO_get_console_type " +"fails for various paths" +msgstr "" + +#: ../../../Misc/NEWS:277 +msgid "" +"`Issue #28137 `__: Renames Windows path file " +"to ._pth" +msgstr "" + +#: ../../../Misc/NEWS:279 +msgid "" +"`Issue #28138 `__: Windows ._pth file should " +"allow import site" +msgstr "" + +#: ../../../Misc/NEWS:284 +msgid "" +"`Issue #28258 `__: Fixed build with Estonian " +"locale (python-config and distclean targets in Makefile). Patch by Arfrever " +"Frehtes Taifersar Arahesis." +msgstr "" + +#: ../../../Misc/NEWS:287 +msgid "" +"`Issue #26661 `__: setup.py now detects " +"system libffi with multiarch wrapper." +msgstr "" + +#: ../../../Misc/NEWS:289 +msgid "" +"`Issue #15819 `__: Remove redundant include " +"search directory option for building outside the source tree." +msgstr "" + +#: ../../../Misc/NEWS:295 +msgid "" +"`Issue #28217 `__: Adds _testconsole module " +"to test console input." +msgstr "" + +#: ../../../Misc/NEWS:299 +msgid "Python 3.6.0 beta 1" +msgstr "" + +#: ../../../Misc/NEWS:301 +msgid "*Release date: 2016-09-12*" +msgstr "" + +#: ../../../Misc/NEWS:306 +msgid "" +"`Issue #23722 `__: The __class__ cell used by " +"zero-argument super() is now initialized from type.__new__ rather than " +"__build_class__, so class methods relying on that will now work correctly " +"when called from metaclass methods during class creation. Patch by Martin " +"Teichmann." +msgstr "" + +#: ../../../Misc/NEWS:311 +msgid "" +"`Issue #25221 `__: Fix corrupted result from " +"PyLong_FromLong(0) when Python is compiled with NSMALLPOSINTS = 0." +msgstr "" + +#: ../../../Misc/NEWS:314 +msgid "" +"`Issue #27080 `__: Implement formatting " +"support for PEP 515. Initial patch by Chris Angelico." +msgstr "" + +#: ../../../Misc/NEWS:317 +msgid "" +"`Issue #27199 `__: In tarfile, expose " +"copyfileobj bufsize to improve throughput. Patch by Jason Fried." +msgstr "" + +#: ../../../Misc/NEWS:320 +msgid "" +"`Issue #27948 `__: In f-strings, only allow " +"backslashes inside the braces (where the expressions are). This is a " +"breaking change from the 3.6 alpha releases, where backslashes are allowed " +"anywhere in an f-string. Also, require that expressions inside f-strings be " +"enclosed within literal braces, and not escapes like f'\\x7b\"hi\"\\x7d'." +msgstr "" + +#: ../../../Misc/NEWS:327 +msgid "" +"`Issue #28046 `__: Remove platform-specific " +"directories from sys.path." +msgstr "" + +#: ../../../Misc/NEWS:329 +msgid "" +"`Issue #28071 `__: Add early-out for " +"differencing from an empty set." +msgstr "" + +#: ../../../Misc/NEWS:331 +msgid "" +"`Issue #25758 `__: Prevents zipimport from " +"unnecessarily encoding a filename (patch by Eryk Sun)" +msgstr "" + +#: ../../../Misc/NEWS:334 +msgid "" +"`Issue #25856 `__: The __module__ attribute " +"of extension classes and functions now is interned. This leads to more " +"compact pickle data with protocol 4." +msgstr "" + +#: ../../../Misc/NEWS:337 +msgid "" +"`Issue #27213 `__: Rework CALL_FUNCTION* " +"opcodes to produce shorter and more efficient bytecode. Patch by Demur " +"Rumed, design by Serhiy Storchaka, reviewed by Serhiy Storchaka and Victor " +"Stinner." +msgstr "" + +#: ../../../Misc/NEWS:341 +msgid "" +"`Issue #26331 `__: Implement tokenizing " +"support for PEP 515. Patch by Georg Brandl." +msgstr "" + +#: ../../../Misc/NEWS:343 +msgid "" +"`Issue #27999 `__: Make \"global after use\" " +"a SyntaxError, and ditto for nonlocal. Patch by Ivan Levkivskyi." +msgstr "" + +#: ../../../Misc/NEWS:346 +msgid "" +"`Issue #28003 `__: Implement PEP 525 -- " +"Asynchronous Generators." +msgstr "" + +#: ../../../Misc/NEWS:348 +msgid "" +"`Issue #27985 `__: Implement PEP 526 -- " +"Syntax for Variable Annotations. Patch by Ivan Levkivskyi." +msgstr "" + +#: ../../../Misc/NEWS:351 +msgid "" +"`Issue #26058 `__: Add a new private version " +"to the builtin dict type, incremented at each dictionary creation and at " +"each dictionary change. Implementation of the PEP 509." +msgstr "" + +#: ../../../Misc/NEWS:355 +msgid "" +"`Issue #27364 `__: A backslash-character pair " +"that is not a valid escape sequence now generates a DeprecationWarning. " +"Patch by Emanuel Barry." +msgstr "" + +#: ../../../Misc/NEWS:358 +msgid "" +"`Issue #27350 `__: `dict` implementation is " +"changed like PyPy. It is more compact and preserves insertion order. " +"(Concept developed by Raymond Hettinger and patch by Inada Naoki.)" +msgstr "" + +#: ../../../Misc/NEWS:362 +msgid "" +"`Issue #27911 `__: Remove unnecessary error " +"checks in ``exec_builtin_or_dynamic()``." +msgstr "" + +#: ../../../Misc/NEWS:365 +msgid "" +"`Issue #27078 `__: Added BUILD_STRING " +"opcode. Optimized f-strings evaluation." +msgstr "" + +#: ../../../Misc/NEWS:367 +msgid "" +"`Issue #17884 `__: Python now requires " +"systems with inttypes.h and stdint.h" +msgstr "" + +#: ../../../Misc/NEWS:369 +msgid "" +"`Issue #27961 `__: Require platforms to " +"support ``long long``. Python hasn't compiled without ``long long`` for " +"years, so this is basically a formality." +msgstr "" + +#: ../../../Misc/NEWS:372 +msgid "" +"`Issue #27355 `__: Removed support for " +"Windows CE. It was never finished, and Windows CE is no longer a relevant " +"platform for Python." +msgstr "" + +#: ../../../Misc/NEWS:375 +msgid "Implement PEP 523." +msgstr "" + +#: ../../../Misc/NEWS:377 +msgid "" +"`Issue #27870 `__: A left shift of zero by a " +"large integer no longer attempts to allocate large amounts of memory." +msgstr "" + +#: ../../../Misc/NEWS:380 +msgid "" +"`Issue #25402 `__: In int-to-decimal-string " +"conversion, improve the estimate of the intermediate memory required, and " +"remove an unnecessarily strict overflow check. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:384 +msgid "" +"`Issue #27214 `__: In long_invert, be more " +"careful about modifying object returned by long_add, and remove an " +"unnecessary check for small longs. Thanks Oren Milman for analysis and patch." +msgstr "" + +#: ../../../Misc/NEWS:388 +msgid "" +"`Issue #27506 `__: Support passing the bytes/" +"bytearray.translate() \"delete\" argument by keyword." +msgstr "" + +#: ../../../Misc/NEWS:391 +msgid "" +"`Issue #27812 `__: Properly clear out a " +"generator's frame's backreference to the generator to prevent crashes in " +"frame.clear()." +msgstr "" + +#: ../../../Misc/NEWS:394 +msgid "" +"`Issue #27811 `__: Fix a crash when a " +"coroutine that has not been awaited is finalized with warnings-as-errors " +"enabled." +msgstr "" + +#: ../../../Misc/NEWS:397 +msgid "" +"`Issue #27587 `__: Fix another issue found by " +"PVS-Studio: Null pointer check after use of 'def' in _PyState_AddModule(). " +"Initial patch by Christian Heimes." +msgstr "" + +#: ../../../Misc/NEWS:401 +msgid "" +"`Issue #27792 `__: The modulo operation " +"applied to ``bool`` and other ``int`` subclasses now always returns an " +"``int``. Previously the return type depended on the input values. Patch by " +"Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:405 +msgid "" +"`Issue #26984 `__: int() now always returns " +"an instance of exact int." +msgstr "" + +#: ../../../Misc/NEWS:407 +msgid "" +"`Issue #25604 `__: Fix a minor bug in integer " +"true division; this bug could potentially have caused off-by-one-ulp results " +"on platforms with unreliable ldexp implementations." +msgstr "" + +#: ../../../Misc/NEWS:411 +msgid "" +"`Issue #24254 `__: Make class definition " +"namespace ordered by default." +msgstr "" + +#: ../../../Misc/NEWS:413 +msgid "" +"`Issue #27662 `__: Fix an overflow check in " +"``List_New``: the original code was checking against ``Py_SIZE_MAX`` instead " +"of the correct upper bound of ``Py_SSIZE_T_MAX``. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:417 +msgid "" +"`Issue #27782 `__: Multi-phase extension " +"module import now correctly allows the ``m_methods`` field to be used to add " +"module level functions to instances of non-module types returned from " +"``Py_create_mod``. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:421 +msgid "" +"`Issue #27936 `__: The round() function " +"accepted a second None argument for some types but not for others. Fixed " +"the inconsistency by accepting None for all numeric types." +msgstr "" + +#: ../../../Misc/NEWS:425 +msgid "" +"`Issue #27487 `__: Warn if a submodule " +"argument to \"python -m\" or runpy.run_module() is found in sys.modules " +"after parent packages are imported, but before the submodule is executed." +msgstr "" + +#: ../../../Misc/NEWS:429 +msgid "" +"`Issue #27157 `__: Make only type() itself " +"accept the one-argument form. Patch by Eryk Sun and Emanuel Barry." +msgstr "" + +#: ../../../Misc/NEWS:432 +msgid "" +"`Issue #27558 `__: Fix a SystemError in the " +"implementation of \"raise\" statement. In a brand new thread, raise a " +"RuntimeError since there is no active exception to reraise. Patch written by " +"Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:436 +msgid "" +"`Issue #28008 `__: Implement PEP 530 -- " +"asynchronous comprehensions." +msgstr "" + +#: ../../../Misc/NEWS:441 +msgid "" +"`Issue #28037 `__: Use " +"sqlite3_get_autocommit() instead of setting Connection->inTransaction " +"manually." +msgstr "" + +#: ../../../Misc/NEWS:444 +msgid "" +"`Issue #25283 `__: Attributes tm_gmtoff and " +"tm_zone are now available on all platforms in the return values of time." +"localtime() and time.gmtime()." +msgstr "" + +#: ../../../Misc/NEWS:448 +msgid "" +"`Issue #24454 `__: Regular expression match " +"object groups are now accessible using __getitem__. \"mo[x]\" is equivalent " +"to \"mo.group(x)\"." +msgstr "" + +#: ../../../Misc/NEWS:452 +msgid "" +"`Issue #10740 `__: sqlite3 no longer " +"implicitly commit an open transaction before DDL statements." +msgstr "" + +#: ../../../Misc/NEWS:455 +msgid "" +"`Issue #17941 `__: Add a *module* parameter " +"to collections.namedtuple()." +msgstr "" + +#: ../../../Misc/NEWS:457 +msgid "" +"`Issue #22493 `__: Inline flags now should be " +"used only at the start of the regular expression. Deprecation warning is " +"emitted if uses them in the middle of the regular expression." +msgstr "" + +#: ../../../Misc/NEWS:461 +msgid "" +"`Issue #26885 `__: xmlrpc now supports " +"unmarshalling additional data types used by Apache XML-RPC implementation " +"for numerics and None." +msgstr "" + +#: ../../../Misc/NEWS:464 +msgid "" +"`Issue #28070 `__: Fixed parsing inline " +"verbose flag in regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:466 +msgid "" +"`Issue #19500 `__: Add client-side SSL " +"session resumption to the ssl module." +msgstr "" + +#: ../../../Misc/NEWS:468 +msgid "" +"`Issue #28022 `__: Deprecate ssl-related " +"arguments in favor of SSLContext. The deprecation include manual creation of " +"SSLSocket and certfile/keyfile (or similar) in ftplib, httplib, imaplib, " +"smtplib, poplib and urllib." +msgstr "" + +#: ../../../Misc/NEWS:472 +msgid "" +"`Issue #28043 `__: SSLContext has improved " +"default settings: OP_NO_SSLv2, OP_NO_SSLv3, OP_NO_COMPRESSION, " +"OP_CIPHER_SERVER_PREFERENCE, OP_SINGLE_DH_USE, OP_SINGLE_ECDH_USE and HIGH " +"ciphers without MD5." +msgstr "" + +#: ../../../Misc/NEWS:476 +msgid "" +"`Issue #24693 `__: Changed some " +"RuntimeError's in the zipfile module to more appropriate types. Improved " +"some error messages and debugging output." +msgstr "" + +#: ../../../Misc/NEWS:479 +msgid "" +"`Issue #17909 `__: ``json.load`` and ``json." +"loads`` now support binary input encoded as UTF-8, UTF-16 or UTF-32. Patch " +"by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:482 +msgid "" +"`Issue #27137 `__: the pure Python fallback " +"implementation of ``functools.partial`` now matches the behaviour of its " +"accelerated C counterpart for subclassing, pickling and text representation " +"purposes. Patch by Emanuel Barry and Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:487 +msgid "" +"Fix possible integer overflows and crashes in the mmap module with unusual " +"usage patterns." +msgstr "" + +#: ../../../Misc/NEWS:490 +msgid "" +"`Issue #1703178 `__: Fix the ability to " +"pass the --link-objects option to the distutils build_ext command." +msgstr "" + +#: ../../../Misc/NEWS:493 +msgid "" +"`Issue #28019 `__: itertools.count() no " +"longer rounds non-integer step in range between 1.0 and 2.0 to 1." +msgstr "" + +#: ../../../Misc/NEWS:496 +msgid "" +"`Issue #18401 `__: Pdb now supports the " +"'readrc' keyword argument to control whether .pdbrc files should be read. " +"Patch by Martin Matusiak and Sam Kimbrel." +msgstr "" + +#: ../../../Misc/NEWS:500 +msgid "" +"`Issue #25969 `__: Update the lib2to3 grammar " +"to handle the unpacking generalizations added in 3.5." +msgstr "" + +#: ../../../Misc/NEWS:503 +msgid "" +"`Issue #14977 `__: mailcap now respects the " +"order of the lines in the mailcap files (\"first match\"), as required by " +"RFC 1542. Patch by Michael Lazar." +msgstr "" + +#: ../../../Misc/NEWS:506 +msgid "" +"`Issue #28025 `__: Convert all ssl module " +"constants to IntEnum and IntFlags. SSLContext properties now return flags " +"and enums." +msgstr "" + +#: ../../../Misc/NEWS:509 +msgid "" +"`Issue #433028 `__: Added support of " +"modifier spans in regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:511 +msgid "" +"`Issue #24594 `__: Validates persist " +"parameter when opening MSI database" +msgstr "" + +#: ../../../Misc/NEWS:513 +msgid "" +"`Issue #17582 `__: xml.etree.ElementTree nows " +"preserves whitespaces in attributes (Patch by Duane Griffin. Reviewed and " +"approved by Stefan Behnel.)" +msgstr "" + +#: ../../../Misc/NEWS:516 +msgid "" +"`Issue #28047 `__: Fixed calculation of line " +"length used for the base64 CTE in the new email policies." +msgstr "" + +#: ../../../Misc/NEWS:519 +msgid "" +"`Issue #27576 `__: Fix call order in " +"OrderedDict.__init__()." +msgstr "" + +#: ../../../Misc/NEWS:521 +msgid "email.generator.DecodedGenerator now supports the policy keyword." +msgstr "" + +#: ../../../Misc/NEWS:523 +msgid "" +"`Issue #28027 `__: Remove undocumented " +"modules from ``Lib/plat-*``: IN, CDROM, DLFCN, TYPES, CDIO, and STROPTS." +msgstr "" + +#: ../../../Misc/NEWS:526 +msgid "" +"`Issue #27445 `__: Don't pass str(_charset) " +"to MIMEText.set_payload(). Patch by Claude Paroz." +msgstr "" + +#: ../../../Misc/NEWS:529 +msgid "" +"`Issue #24277 `__: The new email API is no " +"longer provisional, and the docs have been reorganized and rewritten to " +"emphasize the new API." +msgstr "" + +#: ../../../Misc/NEWS:532 +msgid "" +"`Issue #22450 `__: urllib now includes an " +"\"Accept: */*\" header among the default headers. This makes the results of " +"REST API requests more consistent and predictable especially when proxy " +"servers are involved." +msgstr "" + +#: ../../../Misc/NEWS:536 +msgid "" +"lib2to3.pgen3.driver.load_grammar() now creates a stable cache file between " +"runs given the same Grammar.txt input regardless of the hash randomization " +"setting." +msgstr "" + +#: ../../../Misc/NEWS:540 +msgid "" +"`Issue #28005 `__: Allow ImportErrors in " +"encoding implementation to propagate." +msgstr "" + +#: ../../../Misc/NEWS:542 +msgid "" +"`Issue #26667 `__: Support path-like objects " +"in importlib.util." +msgstr "" + +#: ../../../Misc/NEWS:544 +msgid "" +"`Issue #27570 `__: Avoid zero-length memcpy() " +"etc calls with null source pointers in the \"ctypes\" and \"array\" modules." +msgstr "" + +#: ../../../Misc/NEWS:547 +msgid "" +"`Issue #22233 `__: Break email header lines " +"*only* on the RFC specified CR and LF characters, not on arbitrary unicode " +"line breaks. This also fixes a bug in HTTP header parsing." +msgstr "" + +#: ../../../Misc/NEWS:551 +msgid "" +"Issue 27331: The email.mime classes now all accept an optional policy " +"keyword." +msgstr "" + +#: ../../../Misc/NEWS:553 +msgid "" +"Issue 27988: Fix email iter_attachments incorrect mutation of payload list." +msgstr "" + +#: ../../../Misc/NEWS:555 +msgid "" +"`Issue #16113 `__: Add SHA-3 and SHAKE " +"support to hashlib module." +msgstr "" + +#: ../../../Misc/NEWS:557 +msgid "Eliminate a tautological-pointer-compare warning in _scproxy.c." +msgstr "" + +#: ../../../Misc/NEWS:559 +msgid "" +"`Issue #27776 `__: The :func:`os.urandom` " +"function does now block on Linux 3.17 and newer until the system urandom " +"entropy pool is initialized to increase the security. This change is part of " +"the :pep:`524`." +msgstr "" + +#: ../../../Misc/NEWS:563 +msgid "" +"`Issue #27778 `__: Expose the Linux " +"``getrandom()`` syscall as a new :func:`os.getrandom` function. This change " +"is part of the :pep:`524`." +msgstr "" + +#: ../../../Misc/NEWS:566 +msgid "" +"`Issue #27691 `__: Fix ssl module's parsing " +"of GEN_RID subject alternative name fields in X.509 certs." +msgstr "" + +#: ../../../Misc/NEWS:569 +msgid "`Issue #18844 `__: Add random.choices()." +msgstr "" + +#: ../../../Misc/NEWS:571 +msgid "" +"`Issue #25761 `__: Improved error reporting " +"about truncated pickle data in C implementation of unpickler. " +"UnpicklingError is now raised instead of AttributeError and ValueError in " +"some cases." +msgstr "" + +#: ../../../Misc/NEWS:575 +msgid "" +"`Issue #26798 `__: Add BLAKE2 (blake2b and " +"blake2s) to hashlib." +msgstr "" + +#: ../../../Misc/NEWS:577 +msgid "" +"`Issue #26032 `__: Optimized globbing in " +"pathlib by using os.scandir(); it is now about 1.5--4 times faster." +msgstr "" + +#: ../../../Misc/NEWS:580 +msgid "" +"`Issue #25596 `__: Optimized glob() and " +"iglob() functions in the glob module; they are now about 3--6 times faster." +msgstr "" + +#: ../../../Misc/NEWS:583 +msgid "" +"`Issue #27928 `__: Add scrypt (password-based " +"key derivation function) to hashlib module (requires OpenSSL 1.1.0)." +msgstr "" + +#: ../../../Misc/NEWS:586 +msgid "" +"`Issue #27850 `__: Remove 3DES from ssl " +"module's default cipher list to counter measure sweet32 attack " +"(CVE-2016-2183)." +msgstr "" + +#: ../../../Misc/NEWS:589 +msgid "" +"`Issue #27766 `__: Add ChaCha20 Poly1305 to " +"ssl module's default ciper list. (Required OpenSSL 1.1.0 or LibreSSL)." +msgstr "" + +#: ../../../Misc/NEWS:592 +msgid "" +"`Issue #25387 `__: Check return value of " +"winsound.MessageBeep." +msgstr "" + +#: ../../../Misc/NEWS:594 +msgid "" +"`Issue #27866 `__: Add SSLContext." +"get_ciphers() method to get a list of all enabled ciphers." +msgstr "" + +#: ../../../Misc/NEWS:597 +msgid "" +"`Issue #27744 `__: Add AF_ALG (Linux Kernel " +"crypto) to socket module." +msgstr "" + +#: ../../../Misc/NEWS:599 +msgid "" +"`Issue #26470 `__: Port ssl and hashlib " +"module to OpenSSL 1.1.0." +msgstr "" + +#: ../../../Misc/NEWS:601 +msgid "" +"`Issue #11620 `__: Fix support for SND_MEMORY " +"in winsound.PlaySound. Based on a patch by Tim Lesher." +msgstr "" + +#: ../../../Misc/NEWS:604 +msgid "" +"`Issue #11734 `__: Add support for IEEE 754 " +"half-precision floats to the struct module. Based on a patch by Eli Stevens." +msgstr "" + +#: ../../../Misc/NEWS:607 +msgid "" +"`Issue #27919 `__: Deprecated ``extra_path`` " +"distribution option in distutils packaging." +msgstr "" + +#: ../../../Misc/NEWS:610 +msgid "" +"`Issue #23229 `__: Add new ``cmath`` " +"constants: ``cmath.inf`` and ``cmath.nan`` to match ``math.inf`` and ``math." +"nan``, and also ``cmath.infj`` and ``cmath.nanj`` to match the format used " +"by complex repr." +msgstr "" + +#: ../../../Misc/NEWS:614 +msgid "" +"`Issue #27842 `__: The csv.DictReader now " +"returns rows of type OrderedDict. (Contributed by Steve Holden.)" +msgstr "" + +#: ../../../Misc/NEWS:617 +msgid "" +"Remove support for passing a file descriptor to os.access. It never worked " +"but previously didn't raise." +msgstr "" + +#: ../../../Misc/NEWS:620 +msgid "" +"`Issue #12885 `__: Fix error when distutils " +"encounters symlink." +msgstr "" + +#: ../../../Misc/NEWS:622 +msgid "" +"`Issue #27881 `__: Fixed possible bugs when " +"setting sqlite3.Connection.isolation_level. Based on patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:625 +msgid "" +"`Issue #27861 `__: Fixed a crash in sqlite3." +"Connection.cursor() when a factory creates not a cursor. Patch by Xiang " +"Zhang." +msgstr "" + +#: ../../../Misc/NEWS:628 +msgid "" +"`Issue #19884 `__: Avoid spurious output on " +"OS X with Gnu Readline." +msgstr "" + +#: ../../../Misc/NEWS:630 +msgid "" +"`Issue #27706 `__: Restore deterministic " +"behavior of random.Random().seed() for string seeds using seeding version " +"1. Allows sequences of calls to random() to exactly match those obtained in " +"Python 2. Patch by Nofar Schnider." +msgstr "" + +#: ../../../Misc/NEWS:635 +msgid "" +"`Issue #10513 `__: Fix a regression in " +"Connection.commit(). Statements should not be reset after a commit." +msgstr "" + +#: ../../../Misc/NEWS:638 +msgid "" +"`Issue #12319 `__: Chunked transfer encoding " +"support added to http.client.HTTPConnection requests. The urllib.request." +"AbstractHTTPHandler class does not enforce a Content-Length header any " +"more. If a HTTP request has a file or iterable body, but no Content-Length " +"header, the library now falls back to use chunked transfer- encoding." +msgstr "" + +#: ../../../Misc/NEWS:645 +msgid "" +"A new version of typing.py from https://github.com/python/typing: - " +"Collection (only for 3.6) (`Issue #27598 `__) " +"- Add FrozenSet to __all__ (upstream #261) - fix crash in _get_type_vars() " +"(upstream #259) - Remove the dict constraint in ForwardRef._eval_type " +"(upstream #252)" +msgstr "" + +#: ../../../Misc/NEWS:651 +msgid "" +"`Issue #27832 `__: Make ``_normalize`` " +"parameter to ``Fraction`` constuctor keyword-only, so that ``Fraction(2, 3, " +"4)`` now raises ``TypeError``." +msgstr "" + +#: ../../../Misc/NEWS:654 +msgid "" +"`Issue #27539 `__: Fix unnormalised " +"``Fraction.__pow__`` result in the case of negative exponent and negative " +"base." +msgstr "" + +#: ../../../Misc/NEWS:657 +msgid "" +"`Issue #21718 `__: cursor.description is now " +"available for queries using CTEs." +msgstr "" + +#: ../../../Misc/NEWS:659 +msgid "" +"`Issue #27819 `__: In distutils sdists, " +"simply produce the \"gztar\" (gzipped tar format) distributions on all " +"platforms unless \"formats\" is supplied." +msgstr "" + +#: ../../../Misc/NEWS:662 +msgid "" +"`Issue #2466 `__: posixpath.ismount now " +"correctly recognizes mount points which the user does not have permission to " +"access." +msgstr "" + +#: ../../../Misc/NEWS:665 +msgid "" +"`Issue #9998 `__: On Linux, ctypes.util." +"find_library now looks in LD_LIBRARY_PATH for shared libraries." +msgstr "" + +#: ../../../Misc/NEWS:668 +msgid "" +"`Issue #27573 `__: exit message for code." +"interact is now configurable." +msgstr "" + +#: ../../../Misc/NEWS:670 +msgid "" +"`Issue #27930 `__: Improved behaviour of " +"logging.handlers.QueueListener. Thanks to Paulo Andrade and Petr Viktorin " +"for the analysis and patch." +msgstr "" + +#: ../../../Misc/NEWS:673 +msgid "" +"`Issue #6766 `__: Distributed reference " +"counting added to multiprocessing to support nesting of shared values / " +"proxy objects." +msgstr "" + +#: ../../../Misc/NEWS:676 +msgid "" +"`Issue #21201 `__: Improves readability of " +"multiprocessing error message. Thanks to Wojciech Walczak for patch." +msgstr "" + +#: ../../../Misc/NEWS:679 +msgid "asyncio: Add set_protocol / get_protocol to Transports." +msgstr "" + +#: ../../../Misc/NEWS:681 +msgid "" +"`Issue #27456 `__: asyncio: Set TCP_NODELAY " +"by default." +msgstr "" + +#: ../../../Misc/NEWS:686 +msgid "" +"`Issue #15308 `__: Add 'interrupt " +"execution' (^C) to Shell menu. Patch by Roger Serwy, updated by Bayard " +"Randel." +msgstr "" + +#: ../../../Misc/NEWS:689 +msgid "" +"`Issue #27922 `__: Stop IDLE tests from " +"'flashing' gui widgets on the screen." +msgstr "" + +#: ../../../Misc/NEWS:691 +msgid "" +"`Issue #27891 `__: Consistently group and " +"sort imports within idlelib modules." +msgstr "" + +#: ../../../Misc/NEWS:693 +msgid "" +"`Issue #17642 `__: add larger font sizes for " +"classroom projection." +msgstr "" + +#: ../../../Misc/NEWS:695 +msgid "Add version to title of IDLE help window." +msgstr "" + +#: ../../../Misc/NEWS:697 +msgid "" +"`Issue #25564 `__: In section on IDLE -- " +"console differences, mention that using exec means that __builtins__ is " +"defined for each statement." +msgstr "" + +#: ../../../Misc/NEWS:700 +msgid "" +"`Issue #27821 `__: Fix 3.6.0a3 regression " +"that prevented custom key sets from being selected when no custom theme was " +"defined." +msgstr "" + +#: ../../../Misc/NEWS:704 ../../../Misc/NEWS:1190 ../../../Misc/NEWS:1523 +#: ../../../Misc/NEWS:2811 ../../../Misc/NEWS:4243 ../../../Misc/NEWS:4559 +#: ../../../Misc/NEWS:6155 ../../../Misc/NEWS:8065 +msgid "C API" +msgstr "" + +#: ../../../Misc/NEWS:706 +msgid "" +"`Issue #26900 `__: Excluded underscored names " +"and other private API from limited API." +msgstr "" + +#: ../../../Misc/NEWS:708 +msgid "" +"`Issue #26027 `__: Add support for path-like " +"objects in PyUnicode_FSConverter() & PyUnicode_FSDecoder()." +msgstr "" + +#: ../../../Misc/NEWS:714 +msgid "" +"`Issue #27427 `__: Additional tests for the " +"math module. Patch by Francisco Couzo." +msgstr "" + +#: ../../../Misc/NEWS:716 +msgid "" +"`Issue #27953 `__: Skip math and cmath tests " +"that fail on OS X 10.4 due to a poor libm implementation of tan." +msgstr "" + +#: ../../../Misc/NEWS:719 +msgid "" +"`Issue #26040 `__: Improve test_math and " +"test_cmath coverage and rigour. Patch by Jeff Allen." +msgstr "" + +#: ../../../Misc/NEWS:722 +msgid "" +"`Issue #27787 `__: Call gc.collect() before " +"checking each test for \"dangling threads\", since the dangling threads are " +"weak references." +msgstr "" + +#: ../../../Misc/NEWS:728 +msgid "" +"`Issue #27566 `__: Fix clean target in freeze " +"makefile (patch by Lisa Roach)" +msgstr "" + +#: ../../../Misc/NEWS:730 +msgid "" +"`Issue #27705 `__: Update message in " +"validate_ucrtbase.py" +msgstr "" + +#: ../../../Misc/NEWS:732 +msgid "" +"`Issue #27976 `__: Deprecate building _ctypes " +"with the bundled copy of libffi on non-OSX UNIX platforms." +msgstr "" + +#: ../../../Misc/NEWS:735 +msgid "" +"`Issue #27983 `__: Cause lack of llvm-" +"profdata tool when using clang as required for PGO linking to be a configure " +"time error rather than make time when --with-optimizations is enabled. Also " +"improve our ability to find the llvm-profdata tool on MacOS and some Linuxes." +msgstr "" + +#: ../../../Misc/NEWS:740 +msgid "" +"`Issue #21590 `__: Support for DTrace and " +"SystemTap probes." +msgstr "" + +#: ../../../Misc/NEWS:742 +msgid "" +"`Issue #26307 `__: The profile-opt build now " +"applies PGO to the built-in modules." +msgstr "" + +#: ../../../Misc/NEWS:744 +msgid "" +"`Issue #26539 `__: Add the --with-" +"optimizations flag to turn on LTO and PGO build support when available." +msgstr "" + +#: ../../../Misc/NEWS:747 +msgid "" +"`Issue #27917 `__: Set platform triplets for " +"Android builds." +msgstr "" + +#: ../../../Misc/NEWS:749 +msgid "" +"`Issue #25825 `__: Update references to the " +"$(LIBPL) installation path on AIX. This path was changed in 3.2a4." +msgstr "" + +#: ../../../Misc/NEWS:752 +msgid "Update OS X installer to use SQLite 3.14.1 and XZ 5.2.2." +msgstr "" + +#: ../../../Misc/NEWS:754 +msgid "" +"`Issue #21122 `__: Fix LTO builds on OS X." +msgstr "" + +#: ../../../Misc/NEWS:756 +msgid "" +"`Issue #17128 `__: Build OS X installer with " +"a private copy of OpenSSL. Also provide a sample Install Certificates " +"command script to install a set of root certificates from the third-party " +"certifi module." +msgstr "" + +#: ../../../Misc/NEWS:761 ../../../Misc/NEWS:1219 ../../../Misc/NEWS:1531 +#: ../../../Misc/NEWS:2790 ../../../Misc/NEWS:3323 ../../../Misc/NEWS:4004 +#: ../../../Misc/NEWS:4220 ../../../Misc/NEWS:4427 ../../../Misc/NEWS:6330 +#: ../../../Misc/NEWS:6738 ../../../Misc/NEWS:6936 ../../../Misc/NEWS:7400 +#: ../../../Misc/NEWS:7869 ../../../Misc/NEWS:8227 ../../../Misc/NEWS:8496 +#: ../../../Misc/NEWS:10640 +msgid "Tools/Demos" +msgstr "" + +#: ../../../Misc/NEWS:763 +msgid "" +"`Issue #27952 `__: Get Tools/scripts/fixcid." +"py working with Python 3 and the current \"re\" module, avoid invalid Python " +"backslash escapes, and fix a bug parsing escaped C quote signs." +msgstr "" + +#: ../../../Misc/NEWS:770 +msgid "" +"`Issue #28065 `__: Update xz dependency to " +"5.2.2 and build it from source." +msgstr "" + +#: ../../../Misc/NEWS:772 +msgid "" +"`Issue #25144 `__: Ensures TargetDir is set " +"before continuing with custom install." +msgstr "" + +#: ../../../Misc/NEWS:775 +msgid "" +"`Issue #1602 `__: Windows console doesn't " +"input or print Unicode (PEP 528)" +msgstr "" + +#: ../../../Misc/NEWS:777 +msgid "" +"`Issue #27781 `__: Change file system " +"encoding on Windows to UTF-8 (PEP 529)" +msgstr "" + +#: ../../../Misc/NEWS:779 +msgid "" +"`Issue #27731 `__: Opt-out of MAX_PATH on " +"Windows 10" +msgstr "" + +#: ../../../Misc/NEWS:781 +msgid "" +"`Issue #6135 `__: Adds encoding and errors " +"parameters to subprocess." +msgstr "" + +#: ../../../Misc/NEWS:783 +msgid "" +"`Issue #27959 `__: Adds oem encoding, alias " +"ansi to mbcs, move aliasmbcs to codec lookup." +msgstr "" + +#: ../../../Misc/NEWS:786 +msgid "" +"`Issue #27982 `__: The functions of the " +"winsound module now accept keyword arguments." +msgstr "" + +#: ../../../Misc/NEWS:789 +msgid "" +"`Issue #20366 `__: Build full text search " +"support into SQLite on Windows." +msgstr "" + +#: ../../../Misc/NEWS:791 +msgid "" +"`Issue #27756 `__: Adds new icons for Python " +"files and processes on Windows. Designs by Cherry Wang." +msgstr "" + +#: ../../../Misc/NEWS:794 +msgid "" +"`Issue #27883 `__: Update sqlite to 3.14.1.0 " +"on Windows." +msgstr "" + +#: ../../../Misc/NEWS:798 +msgid "Python 3.6.0 alpha 4" +msgstr "" + +#: ../../../Misc/NEWS:800 +msgid "*Release date: 2016-08-15*" +msgstr "" + +#: ../../../Misc/NEWS:805 +msgid "" +"`Issue #27704 `__: Optimized creating bytes " +"and bytearray from byte-like objects and iterables. Speed up to 3 times for " +"short objects. Original patch by Naoki Inada." +msgstr "" + +#: ../../../Misc/NEWS:809 +msgid "" +"`Issue #26823 `__: Large sections of repeated " +"lines in tracebacks are now abbreviated as \"[Previous line repeated {count} " +"more times]\" by the builtin traceback rendering. Patch by Emanuel Barry." +msgstr "" + +#: ../../../Misc/NEWS:813 +msgid "" +"`Issue #27574 `__: Decreased an overhead of " +"parsing keyword arguments in functions implemented with using Argument " +"Clinic." +msgstr "" + +#: ../../../Misc/NEWS:816 +msgid "" +"`Issue #22557 `__: Now importing already " +"imported modules is up to 2.5 times faster." +msgstr "" + +#: ../../../Misc/NEWS:819 +msgid "" +"`Issue #17596 `__: Include to " +"help with Min GW building." +msgstr "" + +#: ../../../Misc/NEWS:821 +msgid "" +"`Issue #17599 `__: On Windows, rename the " +"privately defined REPARSE_DATA_BUFFER structure to avoid conflicting with " +"the definition from Min GW." +msgstr "" + +#: ../../../Misc/NEWS:824 +msgid "" +"`Issue #27507 `__: Add integer overflow check " +"in bytearray.extend(). Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:827 +msgid "" +"`Issue #27581 `__: Don't rely on wrapping for " +"overflow check in PySequence_Tuple(). Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:830 +msgid "" +"`Issue #1621 `__: Avoid signed integer " +"overflow in list and tuple operations. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:833 +msgid "" +"`Issue #27419 `__: Standard __import__() no " +"longer look up \"__import__\" in globals or builtins for importing " +"submodules or \"from import\". Fixed a crash if raise a warning about " +"unabling to resolve package from __spec__ or __package__." +msgstr "" + +#: ../../../Misc/NEWS:838 +msgid "" +"`Issue #27083 `__: Respect the PYTHONCASEOK " +"environment variable under Windows." +msgstr "" + +#: ../../../Misc/NEWS:840 +msgid "" +"`Issue #27514 `__: Make having too many " +"statically nested blocks a SyntaxError instead of SystemError." +msgstr "" + +#: ../../../Misc/NEWS:843 +msgid "" +"`Issue #27366 `__: Implemented PEP 487 " +"(Simpler customization of class creation). Upon subclassing, the " +"__init_subclass__ classmethod is called on the base class. Descriptors are " +"initialized with __set_name__ after class creation." +msgstr "" + +#: ../../../Misc/NEWS:850 +msgid "" +"`Issue #26027 `__, #27524: Add PEP 519/" +"__fspath__() support to the os and os.path modules. Includes code from Jelle " +"Zijlstra." +msgstr "" + +#: ../../../Misc/NEWS:853 +msgid "" +"`Issue #27598 `__: Add Collections to " +"collections.abc. Patch by Ivan Levkivskyi, docs by Neil Girdhar." +msgstr "" + +#: ../../../Misc/NEWS:856 +msgid "" +"`Issue #25958 `__: Support \"anti-registration" +"\" of special methods from various ABCs, like __hash__, __iter__ or " +"__len__. All these (and several more) can be set to None in an " +"implementation class and the behavior will be as if the method is not " +"defined at all. (Previously, this mechanism existed only for __hash__, to " +"make mutable classes unhashable.) Code contributed by Andrew Barnert and " +"Ivan Levkivskyi." +msgstr "" + +#: ../../../Misc/NEWS:864 +msgid "" +"`Issue #16764 `__: Support keyword arguments " +"to zlib.decompress(). Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:867 +msgid "" +"`Issue #27736 `__: Prevent segfault after " +"interpreter re-initialization due to ref count problem introduced in code " +"for `Issue #27038 `__ in 3.6.0a3. Patch by " +"Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:871 +msgid "" +"`Issue #25628 `__: The *verbose* and " +"*rename* parameters for collections.namedtuple are now keyword-only." +msgstr "" + +#: ../../../Misc/NEWS:874 +msgid "" +"`Issue #12345 `__: Add mathematical constant " +"tau to math and cmath. See also PEP 628." +msgstr "" + +#: ../../../Misc/NEWS:877 +msgid "" +"`Issue #26823 `__: traceback.StackSummary." +"format now abbreviates large sections of repeated lines as \"[Previous line " +"repeated {count} more times]\" (this change then further affects other " +"traceback display operations in the module). Patch by Emanuel Barry." +msgstr "" + +#: ../../../Misc/NEWS:882 +msgid "" +"`Issue #27664 `__: Add to concurrent.futures." +"thread.ThreadPoolExecutor() the ability to specify a thread name prefix." +msgstr "" + +#: ../../../Misc/NEWS:885 +msgid "" +"`Issue #27181 `__: Add geometric_mean and " +"harmonic_mean to statistics module." +msgstr "" + +#: ../../../Misc/NEWS:887 +msgid "" +"`Issue #27573 `__: code.interact now prints " +"an message when exiting." +msgstr "" + +#: ../../../Misc/NEWS:889 +msgid "" +"`Issue #6422 `__: Add autorange method to " +"timeit.Timer objects." +msgstr "" + +#: ../../../Misc/NEWS:891 +msgid "" +"`Issue #27773 `__: Correct some memory " +"management errors server_hostname in _ssl.wrap_socket()." +msgstr "" + +#: ../../../Misc/NEWS:894 +msgid "" +"`Issue #26750 `__: unittest.mock." +"create_autospec() now works properly for subclasses of property() and other " +"data descriptors. Removes the never publicly used, never documented " +"unittest.mock.DescriptorTypes tuple." +msgstr "" + +#: ../../../Misc/NEWS:898 +msgid "" +"`Issue #26754 `__: Undocumented support of " +"general bytes-like objects as path in compile() and similar functions is now " +"deprecated." +msgstr "" + +#: ../../../Misc/NEWS:901 +msgid "" +"`Issue #26800 `__: Undocumented support of " +"general bytes-like objects as paths in os functions is now deprecated." +msgstr "" + +#: ../../../Misc/NEWS:904 +msgid "" +"`Issue #26981 `__: Add _order_ compatibility " +"shim to enum.Enum for Python 2/3 code bases." +msgstr "" + +#: ../../../Misc/NEWS:907 +msgid "" +"`Issue #27661 `__: Added tzinfo keyword " +"argument to datetime.combine." +msgstr "" + +#: ../../../Misc/NEWS:909 +msgid "" +"In the curses module, raise an error if window.getstr() or window.instr() is " +"passed a negative value." +msgstr "" + +#: ../../../Misc/NEWS:912 +msgid "" +"`Issue #27783 `__: Fix possible usage of " +"uninitialized memory in operator.methodcaller." +msgstr "" + +#: ../../../Misc/NEWS:915 +msgid "" +"`Issue #27774 `__: Fix possible Py_DECREF on " +"unowned object in _sre." +msgstr "" + +#: ../../../Misc/NEWS:917 +msgid "" +"`Issue #27760 `__: Fix possible integer " +"overflow in binascii.b2a_qp." +msgstr "" + +#: ../../../Misc/NEWS:919 +msgid "" +"`Issue #27758 `__: Fix possible integer " +"overflow in the _csv module for large record lengths." +msgstr "" + +#: ../../../Misc/NEWS:922 +msgid "" +"`Issue #27568 `__: Prevent HTTPoxy attack " +"(CVE-2016-1000110). Ignore the HTTP_PROXY variable when REQUEST_METHOD " +"environment is set, which indicates that the script is in CGI mode." +msgstr "" + +#: ../../../Misc/NEWS:926 +msgid "" +"`Issue #7063 `__: Remove dead code from the " +"\"array\" module's slice handling. Patch by Chuck." +msgstr "" + +#: ../../../Misc/NEWS:929 +msgid "" +"`Issue #27656 `__: Do not assume sched.h " +"defines any SCHED_* constants." +msgstr "" + +#: ../../../Misc/NEWS:931 +msgid "" +"`Issue #27130 `__: In the \"zlib\" module, " +"fix handling of large buffers (typically 4 GiB) when compressing and " +"decompressing. Previously, inputs were limited to 4 GiB, and compression " +"and decompression operations did not properly handle results of 4 GiB." +msgstr "" + +#: ../../../Misc/NEWS:936 +msgid "" +"`Issue #24773 `__: Implemented PEP 495 (Local " +"Time Disambiguation)." +msgstr "" + +#: ../../../Misc/NEWS:938 +msgid "" +"Expose the EPOLLEXCLUSIVE constant (when it is defined) in the select module." +msgstr "" + +#: ../../../Misc/NEWS:940 +msgid "" +"`Issue #27567 `__: Expose the EPOLLRDHUP and " +"POLLRDHUP constants in the select module." +msgstr "" + +#: ../../../Misc/NEWS:943 +msgid "" +"`Issue #1621 `__: Avoid signed int negation " +"overflow in the \"audioop\" module." +msgstr "" + +#: ../../../Misc/NEWS:945 +msgid "" +"`Issue #27533 `__: Release GIL in nt._isdir" +msgstr "" + +#: ../../../Misc/NEWS:947 +msgid "" +"`Issue #17711 `__: Fixed unpickling by the " +"persistent ID with protocol 0. Original patch by Alexandre Vassalotti." +msgstr "" + +#: ../../../Misc/NEWS:950 +msgid "" +"`Issue #27522 `__: Avoid an unintentional " +"reference cycle in email.feedparser." +msgstr "" + +#: ../../../Misc/NEWS:952 +msgid "" +"`Issue #27512 `__: Fix a segfault when os." +"fspath() called an __fspath__() method that raised an exception. Patch by " +"Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:958 +msgid "" +"`Issue #27714 `__: text_textview and " +"test_autocomplete now pass when re-run in the same process. This occurs " +"when test_idle fails when run with the -w option but without -jn. Fix " +"warning from test_config." +msgstr "" + +#: ../../../Misc/NEWS:962 +msgid "" +"`Issue #27621 `__: Put query response " +"validation error messages in the query box itself instead of in a separate " +"massagebox. Redo tests to match. Add Mac OSX refinements. Original patch " +"by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:966 +msgid "" +"`Issue #27620 `__: Escape key now closes " +"Query box as cancelled." +msgstr "" + +#: ../../../Misc/NEWS:968 +msgid "" +"`Issue #27609 `__: IDLE: tab after initial " +"whitespace should tab, not autocomplete. This fixes problem with writing " +"docstrings at least twice indented." +msgstr "" + +#: ../../../Misc/NEWS:972 +msgid "" +"`Issue #27609 `__: Explicitly return None " +"when there are also non-None returns. In a few cases, reverse a condition " +"and eliminate a return." +msgstr "" + +#: ../../../Misc/NEWS:975 +msgid "" +"`Issue #25507 `__: IDLE no longer runs buggy " +"code because of its tkinter imports. Users must include the same imports " +"required to run directly in Python." +msgstr "" + +#: ../../../Misc/NEWS:978 ../../../Misc/NEWS:1159 +msgid "" +"`Issue #27173 `__: Add 'IDLE Modern Unix' to " +"the built-in key sets. Make the default key set depend on the platform. Add " +"tests for the changes to the config module." +msgstr "" + +#: ../../../Misc/NEWS:982 ../../../Misc/NEWS:1166 +msgid "" +"`Issue #27452 `__: add line counter and crc " +"to IDLE configHandler test dump." +msgstr "" + +#: ../../../Misc/NEWS:987 +msgid "" +"`Issue #25805 `__: Skip a test in " +"test_pkgutil as needed that doesn't work when ``__name__ == __main__``. " +"Patch by SilentGhost." +msgstr "" + +#: ../../../Misc/NEWS:990 +msgid "" +"`Issue #27472 `__: Add test.support." +"unix_shell as the path to the default shell." +msgstr "" + +#: ../../../Misc/NEWS:992 +msgid "" +"`Issue #27369 `__: In test_pyexpat, avoid " +"testing an error message detail that changed in Expat 2.2.0." +msgstr "" + +#: ../../../Misc/NEWS:995 +msgid "" +"`Issue #27594 `__: Prevent assertion error " +"when running test_ast with coverage enabled: ensure code object has a valid " +"first line number. Patch suggested by Ivan Levkivskyi." +msgstr "" + +#: ../../../Misc/NEWS:1002 +msgid "" +"`Issue #27647 `__: Update bundled Tcl/Tk to " +"8.6.6." +msgstr "" + +#: ../../../Misc/NEWS:1004 +msgid "" +"`Issue #27610 `__: Adds PEP 514 metadata to " +"Windows installer" +msgstr "" + +#: ../../../Misc/NEWS:1006 +msgid "" +"`Issue #27469 `__: Adds a shell extension to " +"the launcher so that drag and drop works correctly." +msgstr "" + +#: ../../../Misc/NEWS:1009 +msgid "" +"`Issue #27309 `__: Enables proper Windows " +"styles in python[w].exe manifest." +msgstr "" + +#: ../../../Misc/NEWS:1014 +msgid "" +"`Issue #27713 `__: Suppress spurious build " +"warnings when updating importlib's bootstrap files. Patch by Xiang Zhang" +msgstr "" + +#: ../../../Misc/NEWS:1017 +msgid "" +"`Issue #25825 `__: Correct the references to " +"Modules/python.exp, which is required on AIX. The references were " +"accidentally changed in 3.5.0a1." +msgstr "" + +#: ../../../Misc/NEWS:1020 +msgid "" +"`Issue #27453 `__: CPP invocation in " +"configure must use CPPFLAGS. Patch by Chi Hsuan Yen." +msgstr "" + +#: ../../../Misc/NEWS:1023 +msgid "" +"`Issue #27641 `__: The configure script now " +"inserts comments into the makefile to prevent the pgen and _freeze_importlib " +"executables from being cross- compiled." +msgstr "" + +#: ../../../Misc/NEWS:1027 +msgid "" +"`Issue #26662 `__: Set PYTHON_FOR_GEN in " +"configure as the Python program to be used for file generation during the " +"build." +msgstr "" + +#: ../../../Misc/NEWS:1030 +msgid "" +"`Issue #10910 `__: Avoid C++ compilation " +"errors on FreeBSD and OS X. Also update FreedBSD version checks for the " +"original ctype UTF-8 workaround." +msgstr "" + +#: ../../../Misc/NEWS:1035 +msgid "Python 3.6.0 alpha 3" +msgstr "" + +#: ../../../Misc/NEWS:1037 +msgid "*Release date: 2016-07-11*" +msgstr "" + +#: ../../../Misc/NEWS:1042 +msgid "" +"`Issue #27473 `__: Fixed possible integer " +"overflow in bytes and bytearray concatenations. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1045 +msgid "" +"`Issue #23034 `__: The output of a special " +"Python build with defined COUNT_ALLOCS, SHOW_ALLOC_COUNT or SHOW_TRACK_COUNT " +"macros is now off by default. It can be re-enabled using the \"-X " +"showalloccount\" option. It now outputs to stderr instead of stdout." +msgstr "" + +#: ../../../Misc/NEWS:1050 +msgid "" +"`Issue #27443 `__: __length_hint__() of " +"bytearray iterators no longer return a negative integer for a resized " +"bytearray." +msgstr "" + +#: ../../../Misc/NEWS:1053 +msgid "" +"`Issue #27007 `__: The fromhex() class " +"methods of bytes and bytearray subclasses now return an instance of " +"corresponding subclass." +msgstr "" + +#: ../../../Misc/NEWS:1059 +msgid "" +"`Issue #26844 `__: Fix error message for imp." +"find_module() to refer to 'path' instead of 'name'. Patch by Lev Maximov." +msgstr "" + +#: ../../../Misc/NEWS:1062 +msgid "" +"`Issue #23804 `__: Fix SSL zero-length recv() " +"calls to not block and not raise an error about unclean EOF." +msgstr "" + +#: ../../../Misc/NEWS:1065 +msgid "" +"`Issue #27466 `__: Change time format " +"returned by http.cookie.time2netscape, confirming the netscape cookie format " +"and making it consistent with documentation." +msgstr "" + +#: ../../../Misc/NEWS:1069 +msgid "" +"`Issue #21708 `__: Deprecated dbm.dumb " +"behavior that differs from common dbm behavior: creating a database in 'r' " +"and 'w' modes and modifying a database in 'r' mode." +msgstr "" + +#: ../../../Misc/NEWS:1073 +msgid "" +"`Issue #26721 `__: Change the socketserver." +"StreamRequestHandler.wfile attribute to implement BufferedIOBase. In " +"particular, the write() method no longer does partial writes." +msgstr "" + +#: ../../../Misc/NEWS:1077 +msgid "" +"`Issue #22115 `__: Added methods trace_add, " +"trace_remove and trace_info in the tkinter.Variable class. They replace old " +"methods trace_variable, trace, trace_vdelete and trace_vinfo that use " +"obsolete Tcl commands and might not work in future versions of Tcl. Fixed " +"old tracing methods: trace_vdelete() with wrong mode no longer break " +"tracing, trace_vinfo() now always returns a list of pairs of strings, " +"tracing in the \"u\" mode now works." +msgstr "" + +#: ../../../Misc/NEWS:1084 +msgid "" +"`Issue #26243 `__: Only the level argument to " +"zlib.compress() is keyword argument now. The first argument is positional-" +"only." +msgstr "" + +#: ../../../Misc/NEWS:1087 +msgid "" +"`Issue #27038 `__: Expose the DirEntry type " +"as os.DirEntry. Code patch by Jelle Zijlstra." +msgstr "" + +#: ../../../Misc/NEWS:1090 +msgid "" +"`Issue #27186 `__: Update os.fspath()/" +"PyOS_FSPath() to check the return value of __fspath__() to be either str or " +"bytes." +msgstr "" + +#: ../../../Misc/NEWS:1093 +msgid "" +"`Issue #18726 `__: All optional parameters of " +"the dump(), dumps(), load() and loads() functions and JSONEncoder and " +"JSONDecoder class constructors in the json module are now keyword-only." +msgstr "" + +#: ../../../Misc/NEWS:1097 +msgid "" +"`Issue #27319 `__: Methods selection_set(), " +"selection_add(), selection_remove() and selection_toggle() of ttk.TreeView " +"now allow passing multiple items as multiple arguments instead of passing " +"them as a tuple. Deprecated undocumented ability of calling the selection() " +"method with arguments." +msgstr "" + +#: ../../../Misc/NEWS:1102 +msgid "" +"`Issue #27079 `__: Fixed curses.ascii " +"functions isblank(), iscntrl() and ispunct()." +msgstr "" + +#: ../../../Misc/NEWS:1104 +msgid "" +"`Issue #27294 `__: Numerical state in the " +"repr for Tkinter event objects is now represented as a combination of known " +"flags." +msgstr "" + +#: ../../../Misc/NEWS:1107 +msgid "" +"`Issue #27177 `__: Match objects in the re " +"module now support index-like objects as group indices. Based on patches by " +"Jeroen Demeyer and Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1110 +msgid "" +"`Issue #26754 `__: Some functions (compile() " +"etc) accepted a filename argument encoded as an iterable of integers. Now " +"only strings and byte-like objects are accepted." +msgstr "" + +#: ../../../Misc/NEWS:1114 +msgid "" +"`Issue #26536 `__: socket.ioctl now supports " +"SIO_LOOPBACK_FAST_PATH. Patch by Daniel Stokes." +msgstr "" + +#: ../../../Misc/NEWS:1117 +msgid "" +"`Issue #27048 `__: Prevents distutils failing " +"on Windows when environment variables contain non-ASCII characters" +msgstr "" + +#: ../../../Misc/NEWS:1120 +msgid "" +"`Issue #27330 `__: Fixed possible leaks in " +"the ctypes module." +msgstr "" + +#: ../../../Misc/NEWS:1122 +msgid "" +"`Issue #27238 `__: Got rid of bare excepts in " +"the turtle module. Original patch by Jelle Zijlstra." +msgstr "" + +#: ../../../Misc/NEWS:1125 +msgid "" +"`Issue #27122 `__: When an exception is " +"raised within the context being managed by a contextlib.ExitStack() and one " +"of the exit stack generators catches and raises it in a chain, do not re-" +"raise the original exception when exiting, let the new chained one through. " +"This avoids the PEP 479 bug described in issue25782." +msgstr "" + +#: ../../../Misc/NEWS:1131 +msgid "" +"[Security] `Issue #27278 `__: Fix os." +"urandom() implementation using getrandom() on Linux. Truncate size to " +"INT_MAX and loop until we collected enough random bytes, instead of casting " +"a directly Py_ssize_t to int." +msgstr "" + +#: ../../../Misc/NEWS:1135 +msgid "" +"`Issue #16864 `__: sqlite3.Cursor.lastrowid " +"now supports REPLACE statement. Initial patch by Alex LordThorsen." +msgstr "" + +#: ../../../Misc/NEWS:1138 +msgid "" +"`Issue #26386 `__: Fixed ttk.TreeView " +"selection operations with item id's containing spaces." +msgstr "" + +#: ../../../Misc/NEWS:1141 +msgid "" +"`Issue #8637 `__: Honor a pager set by the env " +"var MANPAGER (in preference to one set by the env var PAGER)." +msgstr "" + +#: ../../../Misc/NEWS:1144 +msgid "" +"[Security] `Issue #22636 `__: Avoid shell " +"injection problems with ctypes.util.find_library()." +msgstr "" + +#: ../../../Misc/NEWS:1147 +msgid "" +"`Issue #16182 `__: Fix various functions in " +"the \"readline\" module to use the locale encoding, and fix get_begidx() and " +"get_endidx() to return code point indexes." +msgstr "" + +#: ../../../Misc/NEWS:1151 +msgid "" +"`Issue #27392 `__: Add loop." +"connect_accepted_socket(). Patch by Jim Fulton." +msgstr "" + +#: ../../../Misc/NEWS:1157 +msgid "" +"`Issue #27477 `__: IDLE search dialogs now " +"use ttk widgets." +msgstr "" + +#: ../../../Misc/NEWS:1163 +msgid "" +"`Issue #27452 `__: make command line \"idle-" +"test> python test_help.py\" work. __file__ is relative when python is " +"started in the file's directory." +msgstr "" + +#: ../../../Misc/NEWS:1168 +msgid "" +"`Issue #27380 `__: IDLE: add query.py with " +"base Query dialog and ttk widgets. Module had subclasses SectionName, " +"ModuleName, and HelpSource, which are used to get information from users by " +"configdialog and file =>Load Module. Each subclass has itw own validity " +"checks. Using ModuleName allows users to edit bad module names instead of " +"starting over. Add tests and delete the two files combined into the new one." +msgstr "" + +#: ../../../Misc/NEWS:1175 +msgid "" +"`Issue #27372 `__: Test_idle no longer " +"changes the locale." +msgstr "" + +#: ../../../Misc/NEWS:1177 +msgid "" +"`Issue #27365 `__: Allow non-ascii chars in " +"IDLE NEWS.txt, for contributor names." +msgstr "" + +#: ../../../Misc/NEWS:1179 +msgid "" +"`Issue #27245 `__: IDLE: Cleanly delete " +"custom themes and key bindings. Previously, when IDLE was started from a " +"console or by import, a cascade of warnings was emitted. Patch by Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:1183 +msgid "" +"`Issue #24137 `__: Run IDLE, test_idle, and " +"htest with tkinter default root disabled. Fix code and tests that fail with " +"this restriction. Fix htests to not create a second and redundant root and " +"mainloop." +msgstr "" + +#: ../../../Misc/NEWS:1187 +msgid "" +"`Issue #27310 `__: Fix IDLE.app failure to " +"launch on OS X due to vestigial import." +msgstr "" + +#: ../../../Misc/NEWS:1192 +msgid "" +"`Issue #26754 `__: PyUnicode_FSDecoder() " +"accepted a filename argument encoded as an iterable of integers. Now only " +"strings and byte-like objects are accepted." +msgstr "" + +#: ../../../Misc/NEWS:1198 +msgid "" +"`Issue #28066 `__: Fix the logic that " +"searches build directories for generated include files when building outside " +"the source tree." +msgstr "" + +#: ../../../Misc/NEWS:1201 +msgid "" +"`Issue #27442 `__: Expose the Android API " +"level that python was built against, in sysconfig.get_config_vars() as " +"'ANDROID_API_LEVEL'." +msgstr "" + +#: ../../../Misc/NEWS:1204 +msgid "" +"`Issue #27434 `__: The interpreter that runs " +"the cross-build, found in PATH, must now be of the same feature version (e." +"g. 3.6) as the source being built." +msgstr "" + +#: ../../../Misc/NEWS:1207 +msgid "" +"`Issue #26930 `__: Update Windows builds to " +"use OpenSSL 1.0.2h." +msgstr "" + +#: ../../../Misc/NEWS:1209 +msgid "" +"`Issue #23968 `__: Rename the platform " +"directory from plat-$(MACHDEP) to plat-$(PLATFORM_TRIPLET). Rename the " +"config directory (LIBPL) from config-$(LDVERSION) to config-$(LDVERSION)-" +"$(PLATFORM_TRIPLET). Install the platform specifc _sysconfigdata module into " +"the platform directory and rename it to include the ABIFLAGS." +msgstr "" + +#: ../../../Misc/NEWS:1216 +msgid "Don't use largefile support for GNU/Hurd." +msgstr "" + +#: ../../../Misc/NEWS:1221 +msgid "" +"`Issue #27332 `__: Fixed the type of the " +"first argument of module-level functions generated by Argument Clinic. " +"Patch by Petr Viktorin." +msgstr "" + +#: ../../../Misc/NEWS:1224 +msgid "" +"`Issue #27418 `__: Fixed Tools/importbench/" +"importbench.py." +msgstr "" + +#: ../../../Misc/NEWS:1229 +msgid "" +"`Issue #19489 `__: Moved the search box from " +"the sidebar to the header and footer of each page. Patch by Ammar Askar." +msgstr "" + +#: ../../../Misc/NEWS:1232 +msgid "" +"`Issue #27285 `__: Update documentation to " +"reflect the deprecation of ``pyvenv`` and normalize on the term \"virtual " +"environment\". Patch by Steve Piercy." +msgstr "" + +#: ../../../Misc/NEWS:1238 +msgid "" +"`Issue #27027 `__: Added test.support." +"is_android that is True when this is an Android build." +msgstr "" + +#: ../../../Misc/NEWS:1243 +msgid "Python 3.6.0 alpha 2" +msgstr "" + +#: ../../../Misc/NEWS:1245 +msgid "*Release date: 2016-06-13*" +msgstr "" + +#: ../../../Misc/NEWS:1250 +msgid "" +"`Issue #27095 `__: Simplified MAKE_FUNCTION " +"and removed MAKE_CLOSURE opcodes. Patch by Demur Rumed." +msgstr "" + +#: ../../../Misc/NEWS:1253 +msgid "" +"`Issue #27190 `__: Raise NotSupportedError if " +"sqlite3 is older than 3.3.1. Patch by Dave Sawyer." +msgstr "" + +#: ../../../Misc/NEWS:1256 +msgid "" +"`Issue #27286 `__: Fixed compiling " +"BUILD_MAP_UNPACK_WITH_CALL opcode. Calling function with generalized " +"unpacking (PEP 448) and conflicting keyword names could cause undefined " +"behavior." +msgstr "" + +#: ../../../Misc/NEWS:1260 +msgid "" +"`Issue #27140 `__: Added BUILD_CONST_KEY_MAP " +"opcode." +msgstr "" + +#: ../../../Misc/NEWS:1262 +msgid "" +"`Issue #27186 `__: Add support for os." +"PathLike objects to open() (part of PEP 519)." +msgstr "" + +#: ../../../Misc/NEWS:1264 +msgid "" +"`Issue #27066 `__: Fixed SystemError if a " +"custom opener (for open()) returns a negative number without setting an " +"exception." +msgstr "" + +#: ../../../Misc/NEWS:1267 +msgid "" +"`Issue #26983 `__: float() now always return " +"an instance of exact float. The deprecation warning is emitted if __float__ " +"returns an instance of a strict subclass of float. In a future versions of " +"Python this can be an error." +msgstr "" + +#: ../../../Misc/NEWS:1272 +msgid "" +"`Issue #27097 `__: Python interpreter is now " +"about 7% faster due to optimized instruction decoding. Based on patch by " +"Demur Rumed." +msgstr "" + +#: ../../../Misc/NEWS:1275 +msgid "" +"`Issue #26647 `__: Python interpreter now " +"uses 16-bit wordcode instead of bytecode. Patch by Demur Rumed." +msgstr "" + +#: ../../../Misc/NEWS:1278 +msgid "" +"`Issue #23275 `__: Allow assigning to an " +"empty target list in round brackets: () = iterable." +msgstr "" + +#: ../../../Misc/NEWS:1281 +msgid "" +"`Issue #27243 `__: Update the __aiter__ " +"protocol: instead of returning an awaitable that resolves to an asynchronous " +"iterator, the asynchronous iterator should be returned directly. Doing the " +"former will trigger a PendingDeprecationWarning." +msgstr "" + +#: ../../../Misc/NEWS:1290 +msgid "" +"Comment out socket (SO_REUSEPORT) and posix (O_SHLOCK, O_EXLOCK) constants " +"exposed on the API which are not implemented on GNU/Hurd. They would not " +"work at runtime anyway." +msgstr "" + +#: ../../../Misc/NEWS:1294 +msgid "" +"`Issue #25455 `__: Fixed crashes in repr of " +"recursive ElementTree.Element and functools.partial objects." +msgstr "" + +#: ../../../Misc/NEWS:1297 +msgid "" +"`Issue #27294 `__: Improved repr for Tkinter " +"event objects." +msgstr "" + +#: ../../../Misc/NEWS:1299 +msgid "" +"`Issue #20508 `__: Improve exception message " +"of IPv{4,6}Network.__getitem__. Patch by Gareth Rees." +msgstr "" + +#: ../../../Misc/NEWS:1302 +msgid "" +"[Security] `Issue #26556 `__: Update expat to " +"2.1.1, fixes CVE-2015-1283." +msgstr "" + +#: ../../../Misc/NEWS:1304 +msgid "" +"[Security] Fix TLS stripping vulnerability in smtplib, CVE-2016-0772. " +"Reported by Team Oststrom." +msgstr "" + +#: ../../../Misc/NEWS:1307 +msgid "" +"`Issue #21386 `__: Implement missing " +"IPv4Address.is_global property. It was documented since 07a5610bae9d. " +"Initial patch by Roger Luethi." +msgstr "" + +#: ../../../Misc/NEWS:1310 +msgid "" +"`Issue #27029 `__: Removed deprecated support " +"of universal newlines mode from ZipFile.open()." +msgstr "" + +#: ../../../Misc/NEWS:1313 +msgid "" +"`Issue #27030 `__: Unknown escapes consisting " +"of ``'\\'`` and an ASCII letter in regular expressions now are errors. The " +"re.LOCALE flag now can be used only with bytes patterns." +msgstr "" + +#: ../../../Misc/NEWS:1317 +msgid "" +"`Issue #27186 `__: Add os.PathLike support to " +"DirEntry (part of PEP 519). Initial patch by Jelle Zijlstra." +msgstr "" + +#: ../../../Misc/NEWS:1320 +msgid "" +"`Issue #20900 `__: distutils register command " +"now decodes HTTP responses correctly. Initial patch by ingrid." +msgstr "" + +#: ../../../Misc/NEWS:1323 +msgid "" +"`Issue #27186 `__: Add os.PathLike support to " +"pathlib, removing its provisional status (part of PEP 519). Initial patch by " +"Dusty Phillips." +msgstr "" + +#: ../../../Misc/NEWS:1326 +msgid "" +"`Issue #27186 `__: Add support for os." +"PathLike objects to os.fsencode() and os.fsdecode() (part of PEP 519)." +msgstr "" + +#: ../../../Misc/NEWS:1329 +msgid "" +"`Issue #27186 `__: Introduce os.PathLike and " +"os.fspath() (part of PEP 519)." +msgstr "" + +#: ../../../Misc/NEWS:1331 +msgid "" +"A new version of typing.py provides several new classes and features: " +"@overload outside stubs, Reversible, DefaultDict, Text, ContextManager, " +"Type[], NewType(), TYPE_CHECKING, and numerous bug fixes (note that some of " +"the new features are not yet implemented in mypy or other static " +"analyzers). Also classes for PEP 492 (Awaitable, AsyncIterable, " +"AsyncIterator) have been added (in fact they made it into 3.5.1 but were " +"never mentioned)." +msgstr "" + +#: ../../../Misc/NEWS:1339 +msgid "" +"`Issue #25738 `__: Stop http.server." +"BaseHTTPRequestHandler.send_error() from sending a message body for 205 " +"Reset Content. Also, don't send Content header fields in responses that " +"don't have a body. Patch by Susumu Koshiba." +msgstr "" + +#: ../../../Misc/NEWS:1344 +msgid "" +"`Issue #21313 `__: Fix the \"platform\" " +"module to tolerate when sys.version contains truncated build information." +msgstr "" + +#: ../../../Misc/NEWS:1347 +msgid "" +"[Security] `Issue #26839 `__: On Linux, :func:" +"`os.urandom` now calls ``getrandom()`` with ``GRND_NONBLOCK`` to fall back " +"on reading ``/dev/urandom`` if the urandom entropy pool is not initialized " +"yet. Patch written by Colm Buckley." +msgstr "" + +#: ../../../Misc/NEWS:1352 +msgid "" +"`Issue #23883 `__: Added missing APIs to " +"__all__ to match the documented APIs for the following modules: cgi, " +"mailbox, mimetypes, plistlib and smtpd. Patches by Jacek Kołodziej." +msgstr "" + +#: ../../../Misc/NEWS:1356 +msgid "" +"`Issue #27164 `__: In the zlib module, allow " +"decompressing raw Deflate streams with a predefined zdict. Based on patch " +"by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1359 +msgid "" +"`Issue #24291 `__: Fix wsgiref.simple_server." +"WSGIRequestHandler to completely write data to the client. Previously it " +"could do partial writes and truncate data. Also, wsgiref.handler." +"ServerHandler can now handle stdout doing partial writes, but this is " +"deprecated." +msgstr "" + +#: ../../../Misc/NEWS:1364 +msgid "" +"`Issue #21272 `__: Use _sysconfigdata.py to " +"initialize distutils.sysconfig." +msgstr "" + +#: ../../../Misc/NEWS:1366 +msgid "" +"`Issue #19611 `__: :mod:`inspect` now reports " +"the implicit ``.0`` parameters generated by the compiler for comprehension " +"and generator expression scopes as if they were positional-only parameters " +"called ``implicit0``. Patch by Jelle Zijlstra." +msgstr "" + +#: ../../../Misc/NEWS:1371 +msgid "" +"`Issue #26809 `__: Add ``__all__`` to :mod:" +"`string`. Patch by Emanuel Barry." +msgstr "" + +#: ../../../Misc/NEWS:1373 +msgid "" +"`Issue #26373 `__: subprocess.Popen." +"communicate now correctly ignores BrokenPipeError when the child process " +"dies before .communicate() is called in more/all circumstances." +msgstr "" + +#: ../../../Misc/NEWS:1377 +msgid "" +"signal, socket, and ssl module IntEnum constant name lookups now return a " +"consistent name for values having multiple names. Ex: signal.Signals(6) now " +"refers to itself as signal.SIGALRM rather than flipping between that and " +"signal.SIGIOT based on the interpreter's hash randomization seed." +msgstr "" + +#: ../../../Misc/NEWS:1382 +msgid "" +"`Issue #27167 `__: Clarify the subprocess." +"CalledProcessError error message text when the child process died due to a " +"signal." +msgstr "" + +#: ../../../Misc/NEWS:1385 +msgid "" +"`Issue #25931 `__: Don't define socketserver." +"Forking* names on platforms such as Windows that do not support os.fork()." +msgstr "" + +#: ../../../Misc/NEWS:1388 +msgid "" +"`Issue #21776 `__: distutils.upload now " +"correctly handles HTTPError. Initial patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:1391 +msgid "" +"`Issue #26526 `__: Replace custom parse tree " +"validation in the parser module with a simple DFA validator." +msgstr "" + +#: ../../../Misc/NEWS:1394 +msgid "" +"`Issue #27114 `__: Fix SSLContext." +"_load_windows_store_certs fails with PermissionError" +msgstr "" + +#: ../../../Misc/NEWS:1397 +msgid "" +"`Issue #18383 `__: Avoid creating duplicate " +"filters when using filterwarnings and simplefilter. Based on patch by Alex " +"Shkop." +msgstr "" + +#: ../../../Misc/NEWS:1400 +msgid "" +"`Issue #23026 `__: winreg.QueryValueEx() now " +"return an integer for REG_QWORD type." +msgstr "" + +#: ../../../Misc/NEWS:1402 +msgid "" +"`Issue #26741 `__: subprocess.Popen " +"destructor now emits a ResourceWarning warning if the child process is still " +"running." +msgstr "" + +#: ../../../Misc/NEWS:1405 +msgid "" +"`Issue #27056 `__: Optimize pickle.load() and " +"pickle.loads(), up to 10% faster to deserialize a lot of small objects." +msgstr "" + +#: ../../../Misc/NEWS:1408 +msgid "" +"`Issue #21271 `__: New keyword only " +"parameters in reset_mock call." +msgstr "" + +#: ../../../Misc/NEWS:1413 +msgid "" +"`Issue #5124 `__: Paste with text selected now " +"replaces the selection on X11. This matches how paste works on Windows, Mac, " +"most modern Linux apps, and ttk widgets. Original patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:1417 +msgid "" +"`Issue #24750 `__: Switch all scrollbars in " +"IDLE to ttk versions. Where needed, minimal tests are added to cover changes." +msgstr "" + +#: ../../../Misc/NEWS:1420 +msgid "" +"`Issue #24759 `__: IDLE requires tk 8.5 and " +"availability ttk widgets. Delete now unneeded tk version tests and code for " +"older versions. Add test for IDLE syntax colorizoer." +msgstr "" + +#: ../../../Misc/NEWS:1424 +msgid "" +"`Issue #27239 `__: idlelib.macosx.isXyzTk " +"functions initialize as needed." +msgstr "" + +#: ../../../Misc/NEWS:1426 +msgid "" +"`Issue #27262 `__: move Aqua unbinding code, " +"which enable context menus, to maxosx." +msgstr "" + +#: ../../../Misc/NEWS:1428 +msgid "" +"`Issue #24759 `__: Make clear in idlelib." +"idle_test.__init__ that the directory is a private implementation of test." +"test_idle and tool for maintainers." +msgstr "" + +#: ../../../Misc/NEWS:1431 +msgid "" +"`Issue #27196 `__: Stop 'ThemeChanged' " +"warnings when running IDLE tests. These persisted after other warnings were " +"suppressed in #20567. Apply Serhiy Storchaka's update_idletasks solution to " +"four test files. Record this additional advice in idle_test/README.txt" +msgstr "" + +#: ../../../Misc/NEWS:1436 +msgid "" +"`Issue #20567 `__: Revise idle_test/README." +"txt with advice about avoiding tk warning messages from tests. Apply advice " +"to several IDLE tests." +msgstr "" + +#: ../../../Misc/NEWS:1439 +msgid "" +"`Issue #24225 `__: Update idlelib/README.txt " +"with new file names and event handlers." +msgstr "" + +#: ../../../Misc/NEWS:1442 +msgid "" +"`Issue #27156 `__: Remove obsolete code not " +"used by IDLE. Replacements: 1. help.txt, replaced by help.html, is out-of-" +"date and should not be used. Its dedicated viewer has be replaced by the " +"html viewer in help.py. 2. ``import idlever; I = idlever.IDLE_VERSION`` is " +"the same as ``import sys; I = version[:version.index(' ')]`` 3. After ``ob = " +"stackviewer.VariablesTreeItem(*args)``, ``ob.keys() == list(ob.object." +"keys)``. 4. In macosc, runningAsOSXAPP == isAquaTk; idCarbonAquaTk == " +"isCarbonTk" +msgstr "" + +#: ../../../Misc/NEWS:1451 +msgid "" +"`Issue #27117 `__: Make colorizer htest and " +"turtledemo work with dark themes. Move code for configuring text widget " +"colors to a new function." +msgstr "" + +#: ../../../Misc/NEWS:1454 +msgid "" +"`Issue #24225 `__: Rename many `idlelib/*.py` " +"and `idle_test/test_*.py` files. Edit files to replace old names with new " +"names when the old name referred to the module rather than the class it " +"contained. See the issue and IDLE section in What's New in 3.6 for more." +msgstr "" + +#: ../../../Misc/NEWS:1459 +msgid "" +"`Issue #26673 `__: When tk reports font size " +"as 0, change to size 10. Such fonts on Linux prevented the configuration " +"dialog from opening." +msgstr "" + +#: ../../../Misc/NEWS:1462 +msgid "" +"`Issue #21939 `__: Add test for IDLE's " +"percolator. Original patch by Saimadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:1465 +msgid "" +"`Issue #21676 `__: Add test for IDLE's " +"replace dialog. Original patch by Saimadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:1468 +msgid "" +"`Issue #18410 `__: Add test for IDLE's search " +"dialog. Original patch by Westley Martínez." +msgstr "" + +#: ../../../Misc/NEWS:1471 +msgid "" +"`Issue #21703 `__: Add test for undo " +"delegator. Patch mostly by Saimadhav Heblikar ." +msgstr "" + +#: ../../../Misc/NEWS:1474 +msgid "" +"`Issue #27044 `__: Add ConfigDialog." +"remove_var_callbacks to stop memory leaks." +msgstr "" + +#: ../../../Misc/NEWS:1476 +msgid "" +"`Issue #23977 `__: Add more asserts to " +"test_delegator." +msgstr "" + +#: ../../../Misc/NEWS:1481 +msgid "" +"`Issue #16484 `__: Change the default " +"PYTHONDOCS URL to \"https:\", and fix the resulting links to use lowercase. " +"Patch by Sean Rodman, test by Kaushik Nadikuditi." +msgstr "" + +#: ../../../Misc/NEWS:1485 +msgid "" +"`Issue #24136 `__: Document the new PEP 448 " +"unpacking syntax of 3.5." +msgstr "" + +#: ../../../Misc/NEWS:1487 +msgid "" +"`Issue #22558 `__: Add remaining doc links to " +"source code for Python-coded modules. Patch by Yoni Lavi." +msgstr "" + +#: ../../../Misc/NEWS:1493 +msgid "" +"`Issue #25285 `__: regrtest now uses " +"subprocesses when the -j1 command line option is used: each test file runs " +"in a fresh child process. Before, the -j1 option was ignored." +msgstr "" + +#: ../../../Misc/NEWS:1497 +msgid "" +"`Issue #25285 `__: Tools/buildbot/test.bat " +"script now uses -j1 by default to run each test file in fresh child process." +msgstr "" + +#: ../../../Misc/NEWS:1503 +msgid "" +"`Issue #27064 `__: The py.exe launcher now " +"defaults to Python 3. The Windows launcher ``py.exe`` no longer prefers an " +"installed Python 2 version over Python 3 by default when used interactively." +msgstr "" + +#: ../../../Misc/NEWS:1510 +msgid "" +"`Issue #27229 `__: Fix the cross-compiling " +"pgen rule for in-tree builds. Patch by Xavier de Gaye." +msgstr "" + +#: ../../../Misc/NEWS:1513 +msgid "" +"`Issue #26930 `__: Update OS X 10.5+ 32-bit-" +"only installer to build and link with OpenSSL 1.0.2h." +msgstr "" + +#: ../../../Misc/NEWS:1517 +msgid "Misc" +msgstr "" + +#: ../../../Misc/NEWS:1519 +msgid "" +"`Issue #17500 `__, and https://github.com/" +"python/pythondotorg/issues/945: Remove unused and outdated icons." +msgstr "" + +#: ../../../Misc/NEWS:1525 +msgid "" +"`Issue #27186 `__: Add the PyOS_FSPath() " +"function (part of PEP 519)." +msgstr "" + +#: ../../../Misc/NEWS:1527 +msgid "" +"`Issue #26282 `__: " +"PyArg_ParseTupleAndKeywords() now supports positional-only parameters." +msgstr "" + +#: ../../../Misc/NEWS:1533 +msgid "" +"`Issue #26282 `__: Argument Clinic now " +"supports positional-only and keyword parameters in the same function." +msgstr "" + +#: ../../../Misc/NEWS:1538 +msgid "Python 3.6.0 alpha 1" +msgstr "" + +#: ../../../Misc/NEWS:1540 +msgid "Release date: 2016-05-16" +msgstr "" + +#: ../../../Misc/NEWS:1545 +msgid "" +"`Issue #20041 `__: Fixed TypeError when frame." +"f_trace is set to None. Patch by Xavier de Gaye." +msgstr "" + +#: ../../../Misc/NEWS:1548 +msgid "" +"`Issue #26168 `__: Fixed possible refleaks in " +"failing Py_BuildValue() with the \"N\" format unit." +msgstr "" + +#: ../../../Misc/NEWS:1551 +msgid "" +"`Issue #26991 `__: Fix possible refleak when " +"creating a function with annotations." +msgstr "" + +#: ../../../Misc/NEWS:1553 +msgid "" +"`Issue #27039 `__: Fixed bytearray.remove() " +"for values greater than 127. Based on patch by Joe Jevnik." +msgstr "" + +#: ../../../Misc/NEWS:1556 +msgid "" +"`Issue #23640 `__: int.from_bytes() no longer " +"bypasses constructors for subclasses." +msgstr "" + +#: ../../../Misc/NEWS:1558 +msgid "" +"`Issue #27005 `__: Optimized the float." +"fromhex() class method for exact float. It is now 2 times faster." +msgstr "" + +#: ../../../Misc/NEWS:1561 +msgid "" +"`Issue #18531 `__: Single var-keyword " +"argument of dict subtype was passed unscathed to the C-defined function. " +"Now it is converted to exact dict." +msgstr "" + +#: ../../../Misc/NEWS:1564 +msgid "" +"`Issue #26811 `__: gc.get_objects() no longer " +"contains a broken tuple with NULL pointer." +msgstr "" + +#: ../../../Misc/NEWS:1567 +msgid "" +"`Issue #20120 `__: Use RawConfigParser for ." +"pypirc parsing, removing support for interpolation unintentionally added " +"with move to Python 3. Behavior no longer does any interpolation in .pypirc " +"files, matching behavior in Python 2.7 and Setuptools 19.0." +msgstr "" + +#: ../../../Misc/NEWS:1573 +msgid "" +"`Issue #26249 `__: Memory functions of the :c:" +"func:`PyMem_Malloc` domain (:c:data:`PYMEM_DOMAIN_MEM`) now use the :ref:" +"`pymalloc allocator ` rather than system :c:func:`malloc`. " +"Applications calling :c:func:`PyMem_Malloc` without holding the GIL can now " +"crash: use ``PYTHONMALLOC=debug`` environment variable to validate the usage " +"of memory allocators in your application." +msgstr "" + +#: ../../../Misc/NEWS:1580 +msgid "" +"`Issue #26802 `__: Optimize function calls " +"only using unpacking like ``func(*tuple)`` (no other positional argument, no " +"keyword): avoid copying the tuple. Patch written by Joe Jevnik." +msgstr "" + +#: ../../../Misc/NEWS:1584 +msgid "" +"`Issue #26659 `__: Make the builtin slice " +"type support cycle collection." +msgstr "" + +#: ../../../Misc/NEWS:1586 +msgid "" +"`Issue #26718 `__: super.__init__ no longer " +"leaks memory if called multiple times. NOTE: A direct call of super.__init__ " +"is not endorsed!" +msgstr "" + +#: ../../../Misc/NEWS:1589 +msgid "" +"`Issue #27138 `__: Fix the doc comment for " +"FileFinder.find_spec()." +msgstr "" + +#: ../../../Misc/NEWS:1591 +msgid "" +"`Issue #27147 `__: Mention PEP 420 in the " +"importlib docs." +msgstr "" + +#: ../../../Misc/NEWS:1593 +msgid "" +"`Issue #25339 `__: PYTHONIOENCODING now has " +"priority over locale in setting the error handler for stdin and stdout." +msgstr "" + +#: ../../../Misc/NEWS:1596 +msgid "" +"`Issue #26494 `__: Fixed crash on iterating " +"exhausting iterators. Affected classes are generic sequence iterators, " +"iterators of str, bytes, bytearray, list, tuple, set, frozenset, dict, " +"OrderedDict, corresponding views and os.scandir() iterator." +msgstr "" + +#: ../../../Misc/NEWS:1601 +msgid "" +"`Issue #26574 `__: Optimize ``bytes." +"replace(b'', b'.')`` and ``bytearray.replace(b'', b'.')``. Patch written by " +"Josh Snider." +msgstr "" + +#: ../../../Misc/NEWS:1604 +msgid "" +"`Issue #26581 `__: If coding cookie is " +"specified multiple times on a line in Python source code file, only the " +"first one is taken to account." +msgstr "" + +#: ../../../Misc/NEWS:1607 +msgid "" +"`Issue #19711 `__: Add tests for reloading " +"namespace packages." +msgstr "" + +#: ../../../Misc/NEWS:1609 +msgid "" +"`Issue #21099 `__: Switch applicable " +"importlib tests to use PEP 451 API." +msgstr "" + +#: ../../../Misc/NEWS:1611 +msgid "" +"`Issue #26563 `__: Debug hooks on Python " +"memory allocators now raise a fatal error if functions of the :c:func:" +"`PyMem_Malloc` family are called without holding the GIL." +msgstr "" + +#: ../../../Misc/NEWS:1615 +msgid "" +"`Issue #26564 `__: On error, the debug hooks " +"on Python memory allocators now use the :mod:`tracemalloc` module to get the " +"traceback where a memory block was allocated." +msgstr "" + +#: ../../../Misc/NEWS:1619 +msgid "" +"`Issue #26558 `__: The debug hooks on Python " +"memory allocator :c:func:`PyObject_Malloc` now detect when functions are " +"called without holding the GIL." +msgstr "" + +#: ../../../Misc/NEWS:1623 +msgid "" +"`Issue #26516 `__: Add :envvar:`PYTHONMALLOC` " +"environment variable to set the Python memory allocators and/or install " +"debug hooks." +msgstr "" + +#: ../../../Misc/NEWS:1626 +msgid "" +"`Issue #26516 `__: The :c:func:" +"`PyMem_SetupDebugHooks` function can now also be used on Python compiled in " +"release mode." +msgstr "" + +#: ../../../Misc/NEWS:1629 +msgid "" +"`Issue #26516 `__: The :envvar:" +"`PYTHONMALLOCSTATS` environment variable can now also be used on Python " +"compiled in release mode. It now has no effect if set to an empty string." +msgstr "" + +#: ../../../Misc/NEWS:1633 +msgid "" +"`Issue #26516 `__: In debug mode, debug hooks " +"are now also installed on Python memory allocators when Python is configured " +"without pymalloc." +msgstr "" + +#: ../../../Misc/NEWS:1636 +msgid "" +"`Issue #26464 `__: Fix str.translate() when " +"string is ASCII and first replacements removes character, but next " +"replacement uses a non-ASCII character or a string longer than 1 character. " +"Regression introduced in Python 3.5.0." +msgstr "" + +#: ../../../Misc/NEWS:1640 +msgid "" +"`Issue #22836 `__: Ensure exception reports " +"from PyErr_Display() and PyErr_WriteUnraisable() are sensible even when " +"formatting them produces secondary errors. This affects the reports " +"produced by sys.__excepthook__() and when __del__() raises an exception." +msgstr "" + +#: ../../../Misc/NEWS:1645 +msgid "" +"`Issue #26302 `__: Correct behavior to reject " +"comma as a legal character for cookie names." +msgstr "" + +#: ../../../Misc/NEWS:1648 +msgid "" +"`Issue #26136 `__: Upgrade the warning when a " +"generator raises StopIteration from PendingDeprecationWarning to " +"DeprecationWarning. Patch by Anish Shah." +msgstr "" + +#: ../../../Misc/NEWS:1652 +msgid "" +"`Issue #26204 `__: The compiler now ignores " +"all constant statements: bytes, str, int, float, complex, name constants " +"(None, False, True), Ellipsis and ast.Constant; not only str and int. For " +"example, ``1.0`` is now ignored in ``def f(): 1.0``." +msgstr "" + +#: ../../../Misc/NEWS:1657 +msgid "" +"`Issue #4806 `__: Avoid masking the original " +"TypeError exception when using star (*) unpacking in function calls. Based " +"on patch by Hagen Fürstenau and Daniel Urban." +msgstr "" + +#: ../../../Misc/NEWS:1661 +msgid "" +"`Issue #26146 `__: Add a new kind of AST " +"node: ``ast.Constant``. It can be used by external AST optimizers, but the " +"compiler does not emit directly such node." +msgstr "" + +#: ../../../Misc/NEWS:1665 +msgid "" +"`Issue #23601 `__: Sped-up allocation of " +"dict key objects by using Python's small object allocator. (Contributed by " +"Julian Taylor.)" +msgstr "" + +#: ../../../Misc/NEWS:1668 +msgid "" +"`Issue #18018 `__: Import raises ImportError " +"instead of SystemError if a relative import is attempted without a known " +"parent package." +msgstr "" + +#: ../../../Misc/NEWS:1671 +msgid "" +"`Issue #25843 `__: When compiling code, don't " +"merge constants if they are equal but have a different types. For example, " +"``f1, f2 = lambda: 1, lambda: 1.0`` is now correctly compiled to two " +"different functions: ``f1()`` returns ``1`` (``int``) and ``f2()`` returns " +"``1.0`` (``float``), even if ``1`` and ``1.0`` are equal." +msgstr "" + +#: ../../../Misc/NEWS:1677 +msgid "" +"`Issue #26107 `__: The format of the " +"``co_lnotab`` attribute of code objects changes to support negative line " +"number delta." +msgstr "" + +#: ../../../Misc/NEWS:1680 +msgid "" +"`Issue #26154 `__: Add a new private " +"_PyThreadState_UncheckedGet() function to get the current Python thread " +"state, but don't issue a fatal error if it is NULL. This new function must " +"be used instead of accessing directly the _PyThreadState_Current variable. " +"The variable is no more exposed since Python 3.5.1 to hide the exact " +"implementation of atomic C types, to avoid compiler issues." +msgstr "" + +#: ../../../Misc/NEWS:1687 +msgid "" +"`Issue #25791 `__: If __package__ != __spec__." +"parent or if neither __package__ or __spec__ are defined then ImportWarning " +"is raised." +msgstr "" + +#: ../../../Misc/NEWS:1690 +msgid "" +"`Issue #22995 `__: [UPDATE] Comment out the " +"one of the pickleability tests in _PyObject_GetState() due to regressions " +"observed in Cython-based projects." +msgstr "" + +#: ../../../Misc/NEWS:1693 +msgid "" +"`Issue #25961 `__: Disallowed null characters " +"in the type name." +msgstr "" + +#: ../../../Misc/NEWS:1695 +msgid "" +"`Issue #25973 `__: Fix segfault when an " +"invalid nonlocal statement binds a name starting with two underscores." +msgstr "" + +#: ../../../Misc/NEWS:1698 +msgid "" +"`Issue #22995 `__: Instances of extension " +"types with a state that aren't subclasses of list or dict and haven't " +"implemented any pickle-related methods (__reduce__, __reduce_ex__, " +"__getnewargs__, __getnewargs_ex__, or __getstate__), can no longer be " +"pickled. Including memoryview." +msgstr "" + +#: ../../../Misc/NEWS:1703 +msgid "" +"`Issue #20440 `__: Massive replacing unsafe " +"attribute setting code with special macro Py_SETREF." +msgstr "" + +#: ../../../Misc/NEWS:1706 +msgid "" +"`Issue #25766 `__: Special method __bytes__() " +"now works in str subclasses." +msgstr "" + +#: ../../../Misc/NEWS:1708 +msgid "" +"`Issue #25421 `__: __sizeof__ methods of " +"builtin types now use dynamic basic size. This allows sys.getsize() to work " +"correctly with their subclasses with __slots__ defined." +msgstr "" + +#: ../../../Misc/NEWS:1712 ../../../Misc/NEWS:2830 +msgid "" +"`Issue #25709 `__: Fixed problem with in-" +"place string concatenation and utf-8 cache." +msgstr "" + +#: ../../../Misc/NEWS:1715 +msgid "" +"`Issue #5319 `__: New Py_FinalizeEx() API " +"allowing Python to set an exit status of 120 on failure to flush buffered " +"streams." +msgstr "" + +#: ../../../Misc/NEWS:1718 +msgid "" +"`Issue #25485 `__: telnetlib.Telnet is now a " +"context manager." +msgstr "" + +#: ../../../Misc/NEWS:1720 +msgid "" +"`Issue #24097 `__: Fixed crash in object." +"__reduce__() if slot name is freed inside __getattr__." +msgstr "" + +#: ../../../Misc/NEWS:1723 +msgid "" +"`Issue #24731 `__: Fixed crash on converting " +"objects with special methods __bytes__, __trunc__, and __float__ returning " +"instances of subclasses of bytes, int, and float to subclasses of bytes, " +"int, and float correspondingly." +msgstr "" + +#: ../../../Misc/NEWS:1727 ../../../Misc/NEWS:2848 +msgid "" +"`Issue #25630 `__: Fix a possible segfault " +"during argument parsing in functions that accept filesystem paths." +msgstr "" + +#: ../../../Misc/NEWS:1730 ../../../Misc/NEWS:2851 +msgid "" +"`Issue #23564 `__: Fixed a partially broken " +"sanity check in the _posixsubprocess internals regarding how fds_to_pass " +"were passed to the child. The bug had no actual impact as subprocess.py " +"already avoided it." +msgstr "" + +#: ../../../Misc/NEWS:1734 ../../../Misc/NEWS:2855 +msgid "" +"`Issue #25388 `__: Fixed tokenizer crash when " +"processing undecodable source code with a null byte." +msgstr "" + +#: ../../../Misc/NEWS:1737 ../../../Misc/NEWS:2858 +msgid "" +"`Issue #25462 `__: The hash of the key now is " +"calculated only once in most operations in C implementation of OrderedDict." +msgstr "" + +#: ../../../Misc/NEWS:1740 ../../../Misc/NEWS:2861 +msgid "" +"`Issue #22995 `__: Default implementation of " +"__reduce__ and __reduce_ex__ now rejects builtin types with not defined " +"__new__." +msgstr "" + +#: ../../../Misc/NEWS:1743 ../../../Misc/NEWS:2867 +msgid "" +"`Issue #24802 `__: Avoid buffer overreads " +"when int(), float(), compile(), exec() and eval() are passed bytes-like " +"objects. These objects are not necessarily terminated by a null byte, but " +"the functions assumed they were." +msgstr "" + +#: ../../../Misc/NEWS:1747 ../../../Misc/NEWS:2864 +msgid "" +"`Issue #25555 `__: Fix parser and AST: fill " +"lineno and col_offset of \"arg\" node when compiling AST from Python objects." +msgstr "" + +#: ../../../Misc/NEWS:1750 ../../../Misc/NEWS:2871 +msgid "" +"`Issue #24726 `__: Fixed a crash and leaking " +"NULL in repr() of OrderedDict that was mutated by direct calls of dict " +"methods." +msgstr "" + +#: ../../../Misc/NEWS:1753 ../../../Misc/NEWS:2874 +msgid "" +"`Issue #25449 `__: Iterating OrderedDict with " +"keys with unstable hash now raises KeyError in C implementations as well as " +"in Python implementation." +msgstr "" + +#: ../../../Misc/NEWS:1756 ../../../Misc/NEWS:2877 +msgid "" +"`Issue #25395 `__: Fixed crash when highly " +"nested OrderedDict structures were garbage collected." +msgstr "" + +#: ../../../Misc/NEWS:1759 +msgid "" +"`Issue #25401 `__: Optimize bytes.fromhex() " +"and bytearray.fromhex(): they are now between 2x and 3.5x faster." +msgstr "" + +#: ../../../Misc/NEWS:1762 +msgid "" +"`Issue #25399 `__: Optimize bytearray % args " +"using the new private _PyBytesWriter API. Formatting is now between 2.5 and " +"5 times faster." +msgstr "" + +#: ../../../Misc/NEWS:1765 ../../../Misc/NEWS:2880 +msgid "" +"`Issue #25274 `__: sys.setrecursionlimit() " +"now raises a RecursionError if the new recursion limit is too low depending " +"at the current recursion depth. Modify also the \"lower-water mark\" formula " +"to make it monotonic. This mark is used to decide when the overflowed flag " +"of the thread state is reset." +msgstr "" + +#: ../../../Misc/NEWS:1770 ../../../Misc/NEWS:2885 +msgid "" +"`Issue #24402 `__: Fix input() to prompt to " +"the redirected stdout when sys.stdout.fileno() fails." +msgstr "" + +#: ../../../Misc/NEWS:1773 +msgid "" +"`Issue #25349 `__: Optimize bytes % args " +"using the new private _PyBytesWriter API. Formatting is now up to 2 times " +"faster." +msgstr "" + +#: ../../../Misc/NEWS:1776 ../../../Misc/NEWS:2888 +msgid "" +"`Issue #24806 `__: Prevent builtin types that " +"are not allowed to be subclassed from being subclassed through multiple " +"inheritance." +msgstr "" + +#: ../../../Misc/NEWS:1779 +msgid "" +"`Issue #25301 `__: The UTF-8 decoder is now " +"up to 15 times as fast for error handlers: ``ignore``, ``replace`` and " +"``surrogateescape``." +msgstr "" + +#: ../../../Misc/NEWS:1782 ../../../Misc/NEWS:2891 +msgid "" +"`Issue #24848 `__: Fixed a number of bugs in " +"UTF-7 decoding of misformed data." +msgstr "" + +#: ../../../Misc/NEWS:1784 +msgid "" +"`Issue #25267 `__: The UTF-8 encoder is now " +"up to 75 times as fast for error handlers: ``ignore``, ``replace``, " +"``surrogateescape``, ``surrogatepass``. Patch co-written with Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:1788 ../../../Misc/NEWS:2893 +msgid "" +"`Issue #25280 `__: Import trace messages " +"emitted in verbose (-v) mode are no longer formatted twice." +msgstr "" + +#: ../../../Misc/NEWS:1791 +msgid "" +"`Issue #25227 `__: Optimize ASCII and latin1 " +"encoders with the ``surrogateescape`` error handler: the encoders are now up " +"to 3 times as fast. Initial patch written by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:1795 ../../../Misc/NEWS:2896 +msgid "" +"`Issue #25003 `__: On Solaris 11.3 or newer, " +"os.urandom() now uses the getrandom() function instead of the getentropy() " +"function. The getentropy() function is blocking to generate very good " +"quality entropy, os.urandom() doesn't need such high-quality entropy." +msgstr "" + +#: ../../../Misc/NEWS:1800 +msgid "" +"`Issue #9232 `__: Modify Python's grammar to " +"allow trailing commas in the argument list of a function declaration. For " +"example, \"def f(\\*, a = 3,): pass\" is now legal. Patch from Mark " +"Dickinson." +msgstr "" + +#: ../../../Misc/NEWS:1804 +msgid "" +"`Issue #24965 `__: Implement PEP 498 " +"\"Literal String Interpolation\". This allows you to embed expressions " +"inside f-strings, which are converted to normal strings at run time. Given " +"x=3, then f'value={x}' == 'value=3'. Patch by Eric V. Smith." +msgstr "" + +#: ../../../Misc/NEWS:1809 +msgid "" +"`Issue #26478 `__: Fix semantic bugs when " +"using binary operators with dictionary views and tuples." +msgstr "" + +#: ../../../Misc/NEWS:1812 +msgid "" +"`Issue #26171 `__: Fix possible integer " +"overflow and heap corruption in zipimporter.get_data()." +msgstr "" + +#: ../../../Misc/NEWS:1815 +msgid "" +"`Issue #25660 `__: Fix TAB key behaviour in " +"REPL with readline." +msgstr "" + +#: ../../../Misc/NEWS:1817 +msgid "" +"`Issue #26288 `__: Optimize PyLong_AsDouble." +msgstr "" + +#: ../../../Misc/NEWS:1819 +msgid "" +"Issues #26289 and #26315: Optimize floor and modulo division for single-" +"digit longs. Microbenchmarks show 2-2.5x improvement. Built-in 'divmod' " +"function is now also ~10% faster." +msgstr "" + +#: ../../../Misc/NEWS:1823 +msgid "" +"`Issue #25887 `__: Raise a RuntimeError when " +"a coroutine object is awaited more than once." +msgstr "" + +#: ../../../Misc/NEWS:1829 +msgid "" +"`Issue #27057 `__: Fix os.set_inheritable() " +"on Android, ioctl() is blocked by SELinux and fails with EACCESS. The " +"function now falls back to fcntl(). Patch written by Michał Bednarski." +msgstr "" + +#: ../../../Misc/NEWS:1833 +msgid "" +"`Issue #27014 `__: Fix infinite recursion " +"using typing.py. Thanks to Kalle Tuure!" +msgstr "" + +#: ../../../Misc/NEWS:1835 +msgid "" +"`Issue #27031 `__: Removed dummy methods in " +"Tkinter widget classes: tk_menuBar() and tk_bindForTraversal()." +msgstr "" + +#: ../../../Misc/NEWS:1838 +msgid "" +"`Issue #14132 `__: Fix urllib.request " +"redirect handling when the target only has a query string. Original fix by " +"Ján Janech." +msgstr "" + +#: ../../../Misc/NEWS:1841 +msgid "" +"`Issue #17214 `__: The \"urllib.request\" " +"module now percent-encodes non-ASCII bytes found in redirect target URLs. " +"Some servers send Location header fields with non-ASCII bytes, but \"http." +"client\" requires the request target to be ASCII-encodable, otherwise a " +"UnicodeEncodeError is raised. Based on patch by Christian Heimes." +msgstr "" + +#: ../../../Misc/NEWS:1847 +msgid "" +"`Issue #27033 `__: The default value of the " +"decode_data parameter for smtpd.SMTPChannel and smtpd.SMTPServer " +"constructors is changed to False." +msgstr "" + +#: ../../../Misc/NEWS:1850 +msgid "" +"`Issue #27034 `__: Removed deprecated class " +"asynchat.fifo." +msgstr "" + +#: ../../../Misc/NEWS:1852 +msgid "" +"`Issue #26870 `__: Added readline." +"set_auto_history(), which can stop entries being automatically added to the " +"history list. Based on patch by Tyler Crompton." +msgstr "" + +#: ../../../Misc/NEWS:1856 +msgid "" +"`Issue #26039 `__: zipfile.ZipFile.open() can " +"now be used to write data into a ZIP file, as well as for extracting data. " +"Patch by Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:1859 +msgid "" +"`Issue #26892 `__: Honor debuglevel flag in " +"urllib.request.HTTPHandler. Patch contributed by Chi Hsuan Yen." +msgstr "" + +#: ../../../Misc/NEWS:1862 +msgid "" +"`Issue #22274 `__: In the subprocess module, " +"allow stderr to be redirected to stdout even when stdout is not redirected. " +"Patch by Akira Li." +msgstr "" + +#: ../../../Misc/NEWS:1865 +msgid "" +"`Issue #26807 `__: mock_open 'files' no " +"longer error on readline at end of file. Patch from Yolanda Robla." +msgstr "" + +#: ../../../Misc/NEWS:1868 +msgid "" +"`Issue #25745 `__: Fixed leaking a userptr in " +"curses panel destructor." +msgstr "" + +#: ../../../Misc/NEWS:1870 +msgid "" +"`Issue #26977 `__: Removed unnecessary, and " +"ignored, call to sum of squares helper in statistics.pvariance." +msgstr "" + +#: ../../../Misc/NEWS:1873 +msgid "" +"`Issue #26002 `__: Use bisect in statistics." +"median instead of a linear search. Patch by Upendra Kuma." +msgstr "" + +#: ../../../Misc/NEWS:1876 +msgid "" +"`Issue #25974 `__: Make use of new Decimal." +"as_integer_ratio() method in statistics module. Patch by Stefan Krah." +msgstr "" + +#: ../../../Misc/NEWS:1879 +msgid "" +"`Issue #26996 `__: Add secrets module as " +"described in PEP 506." +msgstr "" + +#: ../../../Misc/NEWS:1881 +msgid "" +"`Issue #26881 `__: The modulefinder module " +"now supports extended opcode arguments." +msgstr "" + +#: ../../../Misc/NEWS:1883 +msgid "" +"`Issue #23815 `__: Fixed crashes related to " +"directly created instances of types in _tkinter and curses.panel modules." +msgstr "" + +#: ../../../Misc/NEWS:1886 +msgid "" +"`Issue #17765 `__: weakref.ref() no longer " +"silently ignores keyword arguments. Patch by Georg Brandl." +msgstr "" + +#: ../../../Misc/NEWS:1889 +msgid "" +"`Issue #26873 `__: xmlrpc now raises " +"ResponseError on unsupported type tags instead of silently return incorrect " +"result." +msgstr "" + +#: ../../../Misc/NEWS:1892 +msgid "" +"`Issue #26915 `__: The __contains__ methods " +"in the collections ABCs now check for identity before checking equality. " +"This better matches the behavior of the concrete classes, allows sensible " +"handling of NaNs, and makes it easier to reason about container invariants." +msgstr "" + +#: ../../../Misc/NEWS:1897 +msgid "" +"`Issue #26711 `__: Fixed the comparison of " +"plistlib.Data with other types." +msgstr "" + +#: ../../../Misc/NEWS:1899 +msgid "" +"`Issue #24114 `__: Fix an uninitialized " +"variable in `ctypes.util`." +msgstr "" + +#: ../../../Misc/NEWS:1901 +msgid "" +"The bug only occurs on SunOS when the ctypes implementation searches for the " +"`crle` program. Patch by Xiang Zhang. Tested on SunOS by Kees Bos." +msgstr "" + +#: ../../../Misc/NEWS:1905 +msgid "" +"`Issue #26864 `__: In urllib.request, change " +"the proxy bypass host checking against no_proxy to be case-insensitive, and " +"to not match unrelated host names that happen to have a bypassed hostname as " +"a suffix. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1910 +msgid "" +"`Issue #24902 `__: Print server URL on http." +"server startup. Initial patch by Felix Kaiser." +msgstr "" + +#: ../../../Misc/NEWS:1913 +msgid "" +"`Issue #25788 `__: fileinput.hook_encoded() " +"now supports an \"errors\" argument for passing to open. Original patch by " +"Joseph Hackman." +msgstr "" + +#: ../../../Misc/NEWS:1916 +msgid "" +"`Issue #26634 `__: recursive_repr() now sets " +"__qualname__ of wrapper. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1919 +msgid "" +"`Issue #26804 `__: urllib.request will prefer " +"lower_case proxy environment variables over UPPER_CASE or Mixed_Case ones. " +"Patch contributed by Hans-Peter Jansen." +msgstr "" + +#: ../../../Misc/NEWS:1923 +msgid "" +"`Issue #26837 `__: assertSequenceEqual() now " +"correctly outputs non-stringified differing items (like bytes in the -b " +"mode). This affects assertListEqual() and assertTupleEqual()." +msgstr "" + +#: ../../../Misc/NEWS:1927 +msgid "" +"`Issue #26041 `__: Remove \"will be removed " +"in Python 3.7\" from deprecation messages of platform.dist() and platform." +"linux_distribution(). Patch by Kumaripaba Miyurusara Athukorala." +msgstr "" + +#: ../../../Misc/NEWS:1931 +msgid "" +"`Issue #26822 `__: itemgetter, attrgetter and " +"methodcaller objects no longer silently ignore keyword arguments." +msgstr "" + +#: ../../../Misc/NEWS:1934 +msgid "" +"`Issue #26733 `__: Disassembling a class now " +"disassembles class and static methods. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1937 +msgid "" +"`Issue #26801 `__: Fix error handling in :" +"func:`shutil.get_terminal_size`, catch :exc:`AttributeError` instead of :exc:" +"`NameError`. Patch written by Emanuel Barry." +msgstr "" + +#: ../../../Misc/NEWS:1941 +msgid "" +"`Issue #24838 `__: tarfile's ustar and gnu " +"formats now correctly calculate name and link field limits for multibyte " +"character encodings like utf-8." +msgstr "" + +#: ../../../Misc/NEWS:1944 +msgid "" +"[Security] `Issue #26657 `__: Fix directory " +"traversal vulnerability with http.server on Windows. This fixes a " +"regression that was introduced in 3.3.4rc1 and 3.4.0rc1. Based on patch by " +"Philipp Hagemeister." +msgstr "" + +#: ../../../Misc/NEWS:1948 +msgid "" +"`Issue #26717 `__: Stop encoding Latin-1-ized " +"WSGI paths with UTF-8. Patch by Anthony Sottile." +msgstr "" + +#: ../../../Misc/NEWS:1951 +msgid "" +"`Issue #26782 `__: Add STARTUPINFO to " +"subprocess.__all__ on Windows." +msgstr "" + +#: ../../../Misc/NEWS:1953 +msgid "" +"`Issue #26404 `__: Add context manager to " +"socketserver. Patch by Aviv Palivoda." +msgstr "" + +#: ../../../Misc/NEWS:1955 +msgid "" +"`Issue #26735 `__: Fix :func:`os.urandom` on " +"Solaris 11.3 and newer when reading more than 1,024 bytes: call " +"``getrandom()`` multiple times with a limit of 1024 bytes per call." +msgstr "" + +#: ../../../Misc/NEWS:1959 +msgid "" +"`Issue #26585 `__: Eliminate http.server." +"_quote_html() and use html.escape(quote=False). Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1962 +msgid "" +"`Issue #26685 `__: Raise OSError if closing a " +"socket fails." +msgstr "" + +#: ../../../Misc/NEWS:1964 +msgid "" +"`Issue #16329 `__: Add .webm to mimetypes." +"types_map. Patch by Giampaolo Rodola'." +msgstr "" + +#: ../../../Misc/NEWS:1966 +msgid "" +"`Issue #13952 `__: Add .csv to mimetypes." +"types_map. Patch by Geoff Wilson." +msgstr "" + +#: ../../../Misc/NEWS:1968 +msgid "" +"`Issue #26587 `__: the site module now " +"allows .pth files to specify files to be added to sys.path (e.g. zip files)." +msgstr "" + +#: ../../../Misc/NEWS:1971 +msgid "" +"`Issue #25609 `__: Introduce contextlib." +"AbstractContextManager and typing.ContextManager." +msgstr "" + +#: ../../../Misc/NEWS:1974 +msgid "" +"`Issue #26709 `__: Fixed Y2038 problem in " +"loading binary PLists." +msgstr "" + +#: ../../../Misc/NEWS:1976 +msgid "" +"`Issue #23735 `__: Handle terminal resizing " +"with Readline 6.3+ by installing our own SIGWINCH handler. Patch by Eric " +"Price." +msgstr "" + +#: ../../../Misc/NEWS:1979 +msgid "" +"`Issue #25951 `__: Change SSLSocket.sendall() " +"to return None, as explicitly documented for plain socket objects. Patch by " +"Aviv Palivoda." +msgstr "" + +#: ../../../Misc/NEWS:1982 +msgid "" +"`Issue #26586 `__: In http.server, respond " +"with \"413 Request header fields too large\" if there are too many header " +"fields to parse, rather than killing the connection and raising an unhandled " +"exception. Patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:1986 +msgid "" +"`Issue #26676 `__: Added missing " +"XMLPullParser to ElementTree.__all__." +msgstr "" + +#: ../../../Misc/NEWS:1988 +msgid "" +"`Issue #22854 `__: Change BufferedReader." +"writable() and BufferedWriter.readable() to always return False." +msgstr "" + +#: ../../../Misc/NEWS:1991 +msgid "" +"`Issue #26492 `__: Exhausted iterator of " +"array.array now conforms with the behavior of iterators of other mutable " +"sequences: it lefts exhausted even if iterated array is extended." +msgstr "" + +#: ../../../Misc/NEWS:1995 +msgid "" +"`Issue #26641 `__: doctest.DocFileTest and " +"doctest.testfile() now support packages (module splitted into multiple " +"directories) for the package parameter." +msgstr "" + +#: ../../../Misc/NEWS:1999 +msgid "" +"`Issue #25195 `__: Fix a regression in mock." +"MagicMock. _Call is a subclass of tuple (changeset 3603bae63c13 only works " +"for classes) so we need to implement __ne__ ourselves. Patch by Andrew " +"Plummer." +msgstr "" + +#: ../../../Misc/NEWS:2003 +msgid "" +"`Issue #26644 `__: Raise ValueError rather " +"than SystemError when a negative length is passed to SSLSocket.recv() or " +"read()." +msgstr "" + +#: ../../../Misc/NEWS:2006 +msgid "" +"`Issue #23804 `__: Fix SSL recv(0) and " +"read(0) methods to return zero bytes instead of up to 1024." +msgstr "" + +#: ../../../Misc/NEWS:2009 +msgid "" +"`Issue #26616 `__: Fixed a bug in datetime." +"astimezone() method." +msgstr "" + +#: ../../../Misc/NEWS:2011 +msgid "" +"`Issue #26637 `__: The :mod:`importlib` " +"module now emits an :exc:`ImportError` rather than a :exc:`TypeError` if :" +"func:`__import__` is tried during the Python shutdown process but :data:`sys." +"path` is already cleared (set to ``None``)." +msgstr "" + +#: ../../../Misc/NEWS:2016 +msgid "" +"`Issue #21925 `__: :func:`warnings." +"formatwarning` now catches exceptions when calling :func:`linecache.getline` " +"and :func:`tracemalloc.get_object_traceback` to be able to log :exc:" +"`ResourceWarning` emitted late during the Python shutdown process." +msgstr "" + +#: ../../../Misc/NEWS:2021 +msgid "" +"`Issue #23848 `__: On Windows, faulthandler." +"enable() now also installs an exception handler to dump the traceback of all " +"Python threads on any Windows exception, not only on UNIX signals (SIGSEGV, " +"SIGFPE, SIGABRT)." +msgstr "" + +#: ../../../Misc/NEWS:2025 +msgid "" +"`Issue #26530 `__: Add C functions :c:func:" +"`_PyTraceMalloc_Track` and :c:func:`_PyTraceMalloc_Untrack` to track memory " +"blocks using the :mod:`tracemalloc` module. Add :c:func:" +"`_PyTraceMalloc_GetTraceback` to get the traceback of an object." +msgstr "" + +#: ../../../Misc/NEWS:2030 +msgid "" +"`Issue #26588 `__: The _tracemalloc now " +"supports tracing memory allocations of multiple address spaces (domains)." +msgstr "" + +#: ../../../Misc/NEWS:2033 +msgid "" +"`Issue #24266 `__: Ctrl+C during Readline " +"history search now cancels the search mode when compiled with Readline 7." +msgstr "" + +#: ../../../Misc/NEWS:2036 +msgid "" +"`Issue #26590 `__: Implement a safe finalizer " +"for the _socket.socket type. It now releases the GIL to close the socket." +msgstr "" + +#: ../../../Misc/NEWS:2039 +msgid "" +"`Issue #18787 `__: spwd.getspnam() now raises " +"a PermissionError if the user doesn't have privileges." +msgstr "" + +#: ../../../Misc/NEWS:2042 +msgid "" +"`Issue #26560 `__: Avoid potential ValueError " +"in BaseHandler.start_response. Initial patch by Peter Inglesby." +msgstr "" + +#: ../../../Misc/NEWS:2045 +msgid "" +"`Issue #26567 `__: Add a new function :c:func:" +"`PyErr_ResourceWarning` function to pass the destroyed object. Add a " +"*source* attribute to :class:`warnings.WarningMessage`. Add warnings." +"_showwarnmsg() which uses tracemalloc to get the traceback where source " +"object was allocated." +msgstr "" + +#: ../../../Misc/NEWS:2050 +msgid "" +"[Security] `Issue #26313 `__: ssl.py " +"_load_windows_store_certs fails if windows cert store is empty. Patch by " +"Baji." +msgstr "" + +#: ../../../Misc/NEWS:2053 +msgid "" +"`Issue #26569 `__: Fix :func:`pyclbr." +"readmodule` and :func:`pyclbr.readmodule_ex` to support importing packages." +msgstr "" + +#: ../../../Misc/NEWS:2056 +msgid "" +"`Issue #26499 `__: Account for remaining " +"Content-Length in HTTPResponse.readline() and read1(). Based on patch by " +"Silent Ghost. Also document that HTTPResponse now supports these methods." +msgstr "" + +#: ../../../Misc/NEWS:2060 +msgid "" +"`Issue #25320 `__: Handle sockets in " +"directories unittest discovery is scanning. Patch from Victor van den Elzen." +msgstr "" + +#: ../../../Misc/NEWS:2063 +msgid "" +"`Issue #16181 `__: cookiejar.http2time() now " +"returns None if year is higher than datetime.MAXYEAR." +msgstr "" + +#: ../../../Misc/NEWS:2066 +msgid "" +"`Issue #26513 `__: Fixes platform module " +"detection of Windows Server" +msgstr "" + +#: ../../../Misc/NEWS:2068 +msgid "" +"`Issue #23718 `__: Fixed parsing time in week " +"0 before Jan 1. Original patch by Tamás Bence Gedai." +msgstr "" + +#: ../../../Misc/NEWS:2071 +msgid "" +"`Issue #26323 `__: Add Mock.assert_called() " +"and Mock.assert_called_once() methods to unittest.mock. Patch written by " +"Amit Saha." +msgstr "" + +#: ../../../Misc/NEWS:2074 +msgid "" +"`Issue #20589 `__: Invoking Path.owner() and " +"Path.group() on Windows now raise NotImplementedError instead of ImportError." +msgstr "" + +#: ../../../Misc/NEWS:2077 +msgid "" +"`Issue #26177 `__: Fixed the keys() method " +"for Canvas and Scrollbar widgets." +msgstr "" + +#: ../../../Misc/NEWS:2079 +msgid "" +"`Issue #15068 `__: Got rid of excessive " +"buffering in fileinput. The bufsize parameter is now deprecated and ignored." +msgstr "" + +#: ../../../Misc/NEWS:2082 +msgid "" +"`Issue #19475 `__: Added an optional argument " +"timespec to the datetime isoformat() method to choose the precision of the " +"time component." +msgstr "" + +#: ../../../Misc/NEWS:2085 +msgid "" +"`Issue #2202 `__: Fix UnboundLocalError in " +"AbstractDigestAuthHandler.get_algorithm_impls. Initial patch by Mathieu " +"Dupuy." +msgstr "" + +#: ../../../Misc/NEWS:2089 +msgid "" +"`Issue #26167 `__: Minimized overhead in copy." +"copy() and copy.deepcopy(). Optimized copying and deepcopying bytearrays, " +"NotImplemented, slices, short lists, tuples, dicts, sets." +msgstr "" + +#: ../../../Misc/NEWS:2093 +msgid "" +"`Issue #25718 `__: Fixed pickling and copying " +"the accumulate() iterator with total is None." +msgstr "" + +#: ../../../Misc/NEWS:2096 +msgid "" +"`Issue #26475 `__: Fixed debugging output for " +"regular expressions with the (?x) flag." +msgstr "" + +#: ../../../Misc/NEWS:2099 +msgid "" +"`Issue #26482 `__: Allowed pickling recursive " +"dequeues." +msgstr "" + +#: ../../../Misc/NEWS:2101 +msgid "" +"`Issue #26335 `__: Make mmap.write() return " +"the number of bytes written like other write methods. Patch by Jakub " +"Stasiak." +msgstr "" + +#: ../../../Misc/NEWS:2104 +msgid "" +"`Issue #26457 `__: Fixed the subnets() " +"methods in IP network classes for the case when resulting prefix length is " +"equal to maximal prefix length. Based on patch by Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:2108 +msgid "" +"`Issue #26385 `__: Remove the file if the " +"internal open() call in NamedTemporaryFile() fails. Patch by Silent Ghost." +msgstr "" + +#: ../../../Misc/NEWS:2111 +msgid "" +"`Issue #26402 `__: Fix XML-RPC client to " +"retry when the server shuts down a persistent connection. This was a " +"regression related to the new http.client.RemoteDisconnected exception in " +"3.5.0a4." +msgstr "" + +#: ../../../Misc/NEWS:2115 +msgid "" +"`Issue #25913 `__: Leading ``<~`` is optional " +"now in base64.a85decode() with adobe=True. Patch by Swati Jaiswal." +msgstr "" + +#: ../../../Misc/NEWS:2118 +msgid "" +"`Issue #26186 `__: Remove an invalid type " +"check in importlib.util.LazyLoader." +msgstr "" + +#: ../../../Misc/NEWS:2120 +msgid "" +"`Issue #26367 `__: importlib.__import__() " +"raises ImportError like builtins.__import__() when ``level`` is specified " +"but without an accompanying package specified." +msgstr "" + +#: ../../../Misc/NEWS:2124 +msgid "" +"`Issue #26309 `__: In the \"socketserver\" " +"module, shut down the request (closing the connected socket) when " +"verify_request() returns false. Patch by Aviv Palivoda." +msgstr "" + +#: ../../../Misc/NEWS:2128 +msgid "" +"`Issue #23430 `__: Change the socketserver " +"module to only catch exceptions raised from a request handler that are " +"derived from Exception (instead of BaseException). Therefore SystemExit and " +"KeyboardInterrupt no longer trigger the handle_error() method, and will now " +"to stop a single-threaded server." +msgstr "" + +#: ../../../Misc/NEWS:2134 +msgid "" +"[Security] `Issue #25939 `__: On Windows open " +"the cert store readonly in ssl.enum_certificates." +msgstr "" + +#: ../../../Misc/NEWS:2137 +msgid "" +"`Issue #25995 `__: os.walk() no longer uses " +"FDs proportional to the tree depth." +msgstr "" + +#: ../../../Misc/NEWS:2139 +msgid "" +"`Issue #25994 `__: Added the close() method " +"and the support of the context manager protocol for the os.scandir() " +"iterator." +msgstr "" + +#: ../../../Misc/NEWS:2142 +msgid "" +"`Issue #23992 `__: multiprocessing: make " +"MapResult not fail-fast upon exception." +msgstr "" + +#: ../../../Misc/NEWS:2144 +msgid "" +"`Issue #26243 `__: Support keyword arguments " +"to zlib.compress(). Patch by Aviv Palivoda." +msgstr "" + +#: ../../../Misc/NEWS:2147 +msgid "" +"`Issue #26117 `__: The os.scandir() iterator " +"now closes file descriptor not only when the iteration is finished, but when " +"it was failed with error." +msgstr "" + +#: ../../../Misc/NEWS:2150 +msgid "" +"`Issue #25949 `__: __dict__ for an " +"OrderedDict instance is now created only when needed." +msgstr "" + +#: ../../../Misc/NEWS:2153 +msgid "" +"`Issue #25911 `__: Restored support of bytes " +"paths in os.walk() on Windows." +msgstr "" + +#: ../../../Misc/NEWS:2155 +msgid "" +"`Issue #26045 `__: Add UTF-8 suggestion to " +"error message when posting a non-Latin-1 string with http.client." +msgstr "" + +#: ../../../Misc/NEWS:2158 +msgid "" +"`Issue #26039 `__: Added zipfile.ZipInfo." +"from_file() and zipinfo.ZipInfo.is_dir(). Patch by Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:2161 +msgid "" +"`Issue #12923 `__: Reset FancyURLopener's " +"redirect counter even if there is an exception. Based on patches by Brian " +"Brazil and Daniel Rocco." +msgstr "" + +#: ../../../Misc/NEWS:2164 +msgid "" +"`Issue #25945 `__: Fixed a crash when " +"unpickle the functools.partial object with wrong state. Fixed a leak in " +"failed functools.partial constructor. \"args\" and \"keywords\" attributes " +"of functools.partial have now always types tuple and dict correspondingly." +msgstr "" + +#: ../../../Misc/NEWS:2169 +msgid "" +"`Issue #26202 `__: copy.deepcopy() now " +"correctly copies range() objects with non-atomic attributes." +msgstr "" + +#: ../../../Misc/NEWS:2172 +msgid "" +"`Issue #23076 `__: Path.glob() now raises a " +"ValueError if it's called with an invalid pattern. Patch by Thomas Nyberg." +msgstr "" + +#: ../../../Misc/NEWS:2175 +msgid "" +"`Issue #19883 `__: Fixed possible integer " +"overflows in zipimport." +msgstr "" + +#: ../../../Misc/NEWS:2177 +msgid "" +"`Issue #26227 `__: On Windows, getnameinfo(), " +"gethostbyaddr() and gethostbyname_ex() functions of the socket module now " +"decode the hostname from the ANSI code page rather than UTF-8." +msgstr "" + +#: ../../../Misc/NEWS:2181 +msgid "" +"`Issue #26099 `__: The site module now writes " +"an error into stderr if sitecustomize module can be imported but executing " +"the module raise an ImportError. Same change for usercustomize." +msgstr "" + +#: ../../../Misc/NEWS:2185 +msgid "" +"`Issue #26147 `__: xmlrpc now works with " +"strings not encodable with used non-UTF-8 encoding." +msgstr "" + +#: ../../../Misc/NEWS:2188 +msgid "" +"`Issue #25935 `__: Garbage collector now " +"breaks reference loops with OrderedDict." +msgstr "" + +#: ../../../Misc/NEWS:2190 +msgid "" +"`Issue #16620 `__: Fixed AttributeError in " +"msilib.Directory.glob()." +msgstr "" + +#: ../../../Misc/NEWS:2192 +msgid "" +"`Issue #26013 `__: Added compatibility with " +"broken protocol 2 pickles created in old Python 3 versions (3.4.3 and lower)." +msgstr "" + +#: ../../../Misc/NEWS:2195 +msgid "" +"`Issue #26129 `__: Deprecated accepting non-" +"integers in grp.getgrgid()." +msgstr "" + +#: ../../../Misc/NEWS:2197 +msgid "" +"`Issue #25850 `__: Use cross-compilation by " +"default for 64-bit Windows." +msgstr "" + +#: ../../../Misc/NEWS:2199 +msgid "" +"`Issue #25822 `__: Add docstrings to the " +"fields of urllib.parse results. Patch contributed by Swati Jaiswal." +msgstr "" + +#: ../../../Misc/NEWS:2202 +msgid "" +"`Issue #22642 `__: Convert trace module " +"option parsing mechanism to argparse. Patch contributed by SilentGhost." +msgstr "" + +#: ../../../Misc/NEWS:2205 +msgid "" +"`Issue #24705 `__: Fix sysconfig." +"_parse_makefile not expanding ${} vars appearing before $() vars." +msgstr "" + +#: ../../../Misc/NEWS:2208 +msgid "" +"`Issue #26069 `__: Remove the deprecated apis " +"in the trace module." +msgstr "" + +#: ../../../Misc/NEWS:2210 +msgid "" +"`Issue #22138 `__: Fix mock.patch behavior " +"when patching descriptors. Restore original values after patching. Patch " +"contributed by Sean McCully." +msgstr "" + +#: ../../../Misc/NEWS:2213 +msgid "" +"`Issue #25672 `__: In the ssl module, enable " +"the SSL_MODE_RELEASE_BUFFERS mode option if it is safe to do so." +msgstr "" + +#: ../../../Misc/NEWS:2216 +msgid "" +"`Issue #26012 `__: Don't traverse into " +"symlinks for ** pattern in pathlib.Path.[r]glob()." +msgstr "" + +#: ../../../Misc/NEWS:2219 +msgid "" +"`Issue #24120 `__: Ignore PermissionError " +"when traversing a tree with pathlib.Path.[r]glob(). Patch by Ulrich Petri." +msgstr "" + +#: ../../../Misc/NEWS:2222 +msgid "" +"`Issue #21815 `__: Accept ] characters in the " +"data portion of imap responses, in order to handle the flags with square " +"brackets accepted and produced by servers such as gmail." +msgstr "" + +#: ../../../Misc/NEWS:2226 +msgid "" +"`Issue #25447 `__: fileinput now uses sys." +"stdin as-is if it does not have a buffer attribute (restores backward " +"compatibility)." +msgstr "" + +#: ../../../Misc/NEWS:2229 +msgid "" +"`Issue #25971 `__: Optimized creating " +"Fractions from floats by 2 times and from Decimals by 3 times." +msgstr "" + +#: ../../../Misc/NEWS:2232 +msgid "" +"`Issue #25802 `__: Document as deprecated the " +"remaining implementations of importlib.abc.Loader.load_module()." +msgstr "" + +#: ../../../Misc/NEWS:2235 +msgid "" +"`Issue #25928 `__: Add Decimal." +"as_integer_ratio()." +msgstr "" + +#: ../../../Misc/NEWS:2237 +msgid "" +"`Issue #25447 `__: Copying the lru_cache() " +"wrapper object now always works, independently from the type of the wrapped " +"object (by returning the original object unchanged)." +msgstr "" + +#: ../../../Misc/NEWS:2241 +msgid "" +"`Issue #25768 `__: Have the functions in " +"compileall return booleans instead of ints and add proper documentation and " +"tests for the return values." +msgstr "" + +#: ../../../Misc/NEWS:2244 +msgid "" +"`Issue #24103 `__: Fixed possible use after " +"free in ElementTree.XMLPullParser." +msgstr "" + +#: ../../../Misc/NEWS:2246 +msgid "" +"`Issue #25860 `__: os.fwalk() no longer skips " +"remaining directories when error occurs. Original patch by Samson Lee." +msgstr "" + +#: ../../../Misc/NEWS:2249 +msgid "" +"`Issue #25914 `__: Fixed and simplified " +"OrderedDict.__sizeof__." +msgstr "" + +#: ../../../Misc/NEWS:2251 +msgid "" +"`Issue #25869 `__: Optimized deepcopying " +"ElementTree; it is now 20 times faster." +msgstr "" + +#: ../../../Misc/NEWS:2253 +msgid "" +"`Issue #25873 `__: Optimized iterating " +"ElementTree. Iterating elements Element.iter() is now 40% faster, iterating " +"text Element.itertext() is now up to 2.5 times faster." +msgstr "" + +#: ../../../Misc/NEWS:2257 +msgid "" +"`Issue #25902 `__: Fixed various refcount " +"issues in ElementTree iteration." +msgstr "" + +#: ../../../Misc/NEWS:2259 +msgid "" +"`Issue #22227 `__: The TarFile iterator is " +"reimplemented using generator. This implementation is simpler that using " +"class." +msgstr "" + +#: ../../../Misc/NEWS:2262 +msgid "" +"`Issue #25638 `__: Optimized ElementTree." +"iterparse(); it is now 2x faster. Optimized ElementTree parsing; it is now " +"10% faster." +msgstr "" + +#: ../../../Misc/NEWS:2265 +msgid "" +"`Issue #25761 `__: Improved detecting errors " +"in broken pickle data." +msgstr "" + +#: ../../../Misc/NEWS:2267 +msgid "" +"`Issue #25717 `__: Restore the previous " +"behaviour of tolerating most fstat() errors when opening files. This was a " +"regression in 3.5a1, and stopped anonymous temporary files from working in " +"special cases." +msgstr "" + +#: ../../../Misc/NEWS:2271 +msgid "" +"`Issue #24903 `__: Fix regression in number " +"of arguments compileall accepts when '-d' is specified. The check on the " +"number of arguments has been dropped completely as it never worked correctly " +"anyway." +msgstr "" + +#: ../../../Misc/NEWS:2275 +msgid "" +"`Issue #25764 `__: In the subprocess module, " +"preserve any exception caused by fork() failure when preexec_fn is used." +msgstr "" + +#: ../../../Misc/NEWS:2278 +msgid "" +"`Issue #25771 `__: Tweak the exception " +"message for importlib.util.resolve_name() when 'package' isn't specified but " +"necessary." +msgstr "" + +#: ../../../Misc/NEWS:2281 +msgid "" +"`Issue #6478 `__: _strptime's regexp cache now " +"is reset after changing timezone with time.tzset()." +msgstr "" + +#: ../../../Misc/NEWS:2284 +msgid "" +"`Issue #14285 `__: When executing a package " +"with the \"python -m package\" option, and package initialization fails, a " +"proper traceback is now reported. The \"runpy\" module now lets exceptions " +"from package initialization pass back to the caller, rather than raising " +"ImportError." +msgstr "" + +#: ../../../Misc/NEWS:2289 +msgid "" +"`Issue #19771 `__: Also in runpy and the \"-m" +"\" option, omit the irrelevant message \". . . is a package and cannot be " +"directly executed\" if the package could not even be initialized (e.g. due " +"to a bad ``*.pyc`` file)." +msgstr "" + +#: ../../../Misc/NEWS:2293 +msgid "" +"`Issue #25177 `__: Fixed problem with the " +"mean of very small and very large numbers. As a side effect, statistics.mean " +"and statistics.variance should be significantly faster." +msgstr "" + +#: ../../../Misc/NEWS:2297 +msgid "" +"`Issue #25718 `__: Fixed copying object with " +"state with boolean value is false." +msgstr "" + +#: ../../../Misc/NEWS:2299 +msgid "" +"`Issue #10131 `__: Fixed deep copying of " +"minidom documents. Based on patch by Marian Ganisin." +msgstr "" + +#: ../../../Misc/NEWS:2302 +msgid "" +"`Issue #7990 `__: dir() on ElementTree.Element " +"now lists properties: \"tag\", \"text\", \"tail\" and \"attrib\". Original " +"patch by Santoso Wijaya." +msgstr "" + +#: ../../../Misc/NEWS:2305 +msgid "" +"`Issue #25725 `__: Fixed a reference leak in " +"pickle.loads() when unpickling invalid data including tuple instructions." +msgstr "" + +#: ../../../Misc/NEWS:2308 +msgid "" +"`Issue #25663 `__: In the Readline completer, " +"avoid listing duplicate global names, and search the global namespace before " +"searching builtins." +msgstr "" + +#: ../../../Misc/NEWS:2311 +msgid "" +"`Issue #25688 `__: Fixed file leak in " +"ElementTree.iterparse() raising an error." +msgstr "" + +#: ../../../Misc/NEWS:2313 +msgid "" +"`Issue #23914 `__: Fixed SystemError raised " +"by unpickler on broken pickle data." +msgstr "" + +#: ../../../Misc/NEWS:2315 +msgid "" +"`Issue #25691 `__: Fixed crash on deleting " +"ElementTree.Element attributes." +msgstr "" + +#: ../../../Misc/NEWS:2317 +msgid "" +"`Issue #25624 `__: ZipFile now always writes " +"a ZIP_STORED header for directory entries. Patch by Dingyuan Wang." +msgstr "" + +#: ../../../Misc/NEWS:2320 ../../../Misc/NEWS:2914 +msgid "" +"`Issue #25626 `__: Change three zlib " +"functions to accept sizes that fit in Py_ssize_t, but internally cap those " +"sizes to UINT_MAX. This resolves a regression in 3.5 where GzipFile.read() " +"failed to read chunks larger than 2 or 4 GiB. The change affects the zlib." +"Decompress.decompress() max_length parameter, the zlib.decompress() bufsize " +"parameter, and the zlib.Decompress.flush() length parameter." +msgstr "" + +#: ../../../Misc/NEWS:2327 ../../../Misc/NEWS:2921 +msgid "" +"`Issue #25583 `__: Avoid incorrect errors " +"raised by os.makedirs(exist_ok=True) when the OS gives priority to errors " +"such as EACCES over EEXIST." +msgstr "" + +#: ../../../Misc/NEWS:2330 ../../../Misc/NEWS:2924 +msgid "" +"`Issue #25593 `__: Change semantics of " +"EventLoop.stop() in asyncio." +msgstr "" + +#: ../../../Misc/NEWS:2332 ../../../Misc/NEWS:2926 +msgid "" +"`Issue #6973 `__: When we know a subprocess." +"Popen process has died, do not allow the send_signal(), terminate(), or " +"kill() methods to do anything as they could potentially signal a different " +"process." +msgstr "" + +#: ../../../Misc/NEWS:2336 +msgid "" +"`Issue #23883 `__: Added missing APIs to " +"__all__ to match the documented APIs for the following modules: calendar, " +"csv, enum, fileinput, ftplib, logging, optparse, tarfile, threading and " +"wave. Also added a test.support.check__all__() helper. Patches by Jacek " +"Kołodziej, Mauro S. M. Rodrigues and Joel Taddei." +msgstr "" + +#: ../../../Misc/NEWS:2342 +msgid "" +"`Issue #25590 `__: In the Readline completer, " +"only call getattr() once per attribute. Also complete names of attributes " +"such as properties and slots which are listed by dir() but not yet created " +"on an instance." +msgstr "" + +#: ../../../Misc/NEWS:2346 ../../../Misc/NEWS:2933 +msgid "" +"`Issue #25498 `__: Fix a crash when garbage-" +"collecting ctypes objects created by wrapping a memoryview. This was a " +"regression made in 3.5a1. Based on patch by Eryksun." +msgstr "" + +#: ../../../Misc/NEWS:2350 ../../../Misc/NEWS:2937 +msgid "" +"`Issue #25584 `__: Added \"escape\" to the " +"__all__ list in the glob module." +msgstr "" + +#: ../../../Misc/NEWS:2352 ../../../Misc/NEWS:2939 +msgid "" +"`Issue #25584 `__: Fixed recursive glob() " +"with patterns starting with '\\*\\*'." +msgstr "" + +#: ../../../Misc/NEWS:2354 ../../../Misc/NEWS:2941 +msgid "" +"`Issue #25446 `__: Fix regression in " +"smtplib's AUTH LOGIN support." +msgstr "" + +#: ../../../Misc/NEWS:2356 ../../../Misc/NEWS:2943 +msgid "" +"`Issue #18010 `__: Fix the pydoc web server's " +"module search function to handle exceptions from importing packages." +msgstr "" + +#: ../../../Misc/NEWS:2359 ../../../Misc/NEWS:2946 +msgid "" +"`Issue #25554 `__: Got rid of circular " +"references in regular expression parsing." +msgstr "" + +#: ../../../Misc/NEWS:2361 +msgid "" +"`Issue #18973 `__: Command-line interface of " +"the calendar module now uses argparse instead of optparse." +msgstr "" + +#: ../../../Misc/NEWS:2364 ../../../Misc/NEWS:2948 +msgid "" +"`Issue #25510 `__: fileinput.FileInput." +"readline() now returns b'' instead of '' at the end if the FileInput was " +"opened with binary mode. Patch by Ryosuke Ito." +msgstr "" + +#: ../../../Misc/NEWS:2368 ../../../Misc/NEWS:2952 +msgid "" +"`Issue #25503 `__: Fixed inspect.getdoc() for " +"inherited docstrings of properties. Original patch by John Mark Vandenberg." +msgstr "" + +#: ../../../Misc/NEWS:2371 ../../../Misc/NEWS:2955 +msgid "" +"`Issue #25515 `__: Always use os.urandom as a " +"source of randomness in uuid.uuid4." +msgstr "" + +#: ../../../Misc/NEWS:2373 ../../../Misc/NEWS:2957 +msgid "" +"`Issue #21827 `__: Fixed textwrap.dedent() " +"for the case when largest common whitespace is a substring of smallest " +"leading whitespace. Based on patch by Robert Li." +msgstr "" + +#: ../../../Misc/NEWS:2377 ../../../Misc/NEWS:2961 +msgid "" +"`Issue #25447 `__: The lru_cache() wrapper " +"objects now can be copied and pickled (by returning the original object " +"unchanged)." +msgstr "" + +#: ../../../Misc/NEWS:2380 ../../../Misc/NEWS:2964 +msgid "" +"`Issue #25390 `__: typing: Don't crash on " +"Union[str, Pattern]." +msgstr "" + +#: ../../../Misc/NEWS:2382 ../../../Misc/NEWS:2966 +msgid "" +"`Issue #25441 `__: asyncio: Raise error from " +"drain() when socket is closed." +msgstr "" + +#: ../../../Misc/NEWS:2384 ../../../Misc/NEWS:2968 +msgid "" +"`Issue #25410 `__: Cleaned up and fixed minor " +"bugs in C implementation of OrderedDict." +msgstr "" + +#: ../../../Misc/NEWS:2387 ../../../Misc/NEWS:2971 +msgid "" +"`Issue #25411 `__: Improved Unicode support " +"in SMTPHandler through better use of the email package. Thanks to user " +"simon04 for the patch." +msgstr "" + +#: ../../../Misc/NEWS:2390 +msgid "" +"Move the imp module from a PendingDeprecationWarning to DeprecationWarning." +msgstr "" + +#: ../../../Misc/NEWS:2392 ../../../Misc/NEWS:2974 +msgid "" +"`Issue #25407 `__: Remove mentions of the " +"formatter module being removed in Python 3.6." +msgstr "" + +#: ../../../Misc/NEWS:2395 ../../../Misc/NEWS:2977 +msgid "" +"`Issue #25406 `__: Fixed a bug in C " +"implementation of OrderedDict.move_to_end() that caused segmentation fault " +"or hang in iterating after moving several items to the start of ordered dict." +msgstr "" + +#: ../../../Misc/NEWS:2399 +msgid "" +"`Issue #25382 `__: pickletools.dis() now " +"outputs implicit memo index for the MEMOIZE opcode." +msgstr "" + +#: ../../../Misc/NEWS:2402 +msgid "" +"`Issue #25357 `__: Add an optional newline " +"paramer to binascii.b2a_base64(). base64.b64encode() uses it to avoid a " +"memory copy." +msgstr "" + +#: ../../../Misc/NEWS:2405 +msgid "" +"`Issue #24164 `__: Objects that need calling " +"``__new__`` with keyword arguments, can now be pickled using pickle " +"protocols older than protocol version 4." +msgstr "" + +#: ../../../Misc/NEWS:2408 ../../../Misc/NEWS:2981 +msgid "" +"`Issue #25364 `__: zipfile now works in " +"threads disabled builds." +msgstr "" + +#: ../../../Misc/NEWS:2410 ../../../Misc/NEWS:2983 +msgid "" +"`Issue #25328 `__: smtpd's SMTPChannel now " +"correctly raises a ValueError if both decode_data and enable_SMTPUTF8 are " +"set to true." +msgstr "" + +#: ../../../Misc/NEWS:2413 +msgid "" +"`Issue #16099 `__: RobotFileParser now " +"supports Crawl-delay and Request-rate extensions. Patch by Nikolay " +"Bogoychev." +msgstr "" + +#: ../../../Misc/NEWS:2416 ../../../Misc/NEWS:2986 +msgid "" +"`Issue #25316 `__: distutils raises OSError " +"instead of DistutilsPlatformError when MSVC is not installed." +msgstr "" + +#: ../../../Misc/NEWS:2419 ../../../Misc/NEWS:2989 +msgid "" +"`Issue #25380 `__: Fixed protocol for the " +"STACK_GLOBAL opcode in pickletools.opcodes." +msgstr "" + +#: ../../../Misc/NEWS:2422 ../../../Misc/NEWS:2992 +msgid "" +"`Issue #23972 `__: Updates asyncio datagram " +"create method allowing reuseport and reuseaddr socket options to be set " +"prior to binding the socket. Mirroring the existing asyncio create_server " +"method the reuseaddr option for datagram sockets defaults to True if the O/S " +"is 'posix' (except if the platform is Cygwin). Patch by Chris Laws." +msgstr "" + +#: ../../../Misc/NEWS:2428 ../../../Misc/NEWS:2998 +msgid "" +"`Issue #25304 `__: Add asyncio." +"run_coroutine_threadsafe(). This lets you submit a coroutine to a loop from " +"another thread, returning a concurrent.futures.Future. By Vincent Michel." +msgstr "" + +#: ../../../Misc/NEWS:2432 ../../../Misc/NEWS:3002 +msgid "" +"`Issue #25232 `__: Fix CGIRequestHandler to " +"split the query from the URL at the first question mark (?) rather than the " +"last. Patch from Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:2435 ../../../Misc/NEWS:3005 +msgid "" +"`Issue #24657 `__: Prevent CGIRequestHandler " +"from collapsing slashes in the query part of the URL as if it were a path. " +"Patch from Xiang Zhang." +msgstr "" + +#: ../../../Misc/NEWS:2438 +msgid "" +"`Issue #25287 `__: Don't add crypt." +"METHOD_CRYPT to crypt.methods if it's not supported. Check if it is " +"supported, it may not be supported on OpenBSD for example." +msgstr "" + +#: ../../../Misc/NEWS:2442 ../../../Misc/NEWS:3032 +msgid "" +"`Issue #23600 `__: Default implementation of " +"tzinfo.fromutc() was returning wrong results in some cases." +msgstr "" + +#: ../../../Misc/NEWS:2445 ../../../Misc/NEWS:3029 +msgid "" +"`Issue #25203 `__: Failed readline." +"set_completer_delims() no longer left the module in inconsistent state." +msgstr "" + +#: ../../../Misc/NEWS:2448 +msgid "" +"`Issue #25011 `__: rlcompleter now omits " +"private and special attribute names unless the prefix starts with " +"underscores." +msgstr "" + +#: ../../../Misc/NEWS:2451 +msgid "" +"`Issue #25209 `__: rlcompleter now can add a " +"space or a colon after completed keyword." +msgstr "" + +#: ../../../Misc/NEWS:2454 +msgid "" +"`Issue #22241 `__: timezone.utc name is now " +"plain 'UTC', not 'UTC-00:00'." +msgstr "" + +#: ../../../Misc/NEWS:2456 +msgid "" +"`Issue #23517 `__: fromtimestamp() and " +"utcfromtimestamp() methods of datetime.datetime now round microseconds to " +"nearest with ties going to nearest even integer (ROUND_HALF_EVEN), as " +"round(float), instead of rounding towards -Infinity (ROUND_FLOOR)." +msgstr "" + +#: ../../../Misc/NEWS:2461 +msgid "" +"`Issue #23552 `__: Timeit now warns when " +"there is substantial (4x) variance between best and worst times. Patch from " +"Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:2464 +msgid "" +"`Issue #24633 `__: site-packages/README -> " +"README.txt." +msgstr "" + +#: ../../../Misc/NEWS:2466 +msgid "" +"`Issue #24879 `__: help() and pydoc can now " +"list named tuple fields in the order they were defined rather than " +"alphabetically. The ordering is determined by the _fields attribute if " +"present." +msgstr "" + +#: ../../../Misc/NEWS:2470 +msgid "" +"`Issue #24874 `__: Improve speed of itertools." +"cycle() and make its pickle more compact." +msgstr "" + +#: ../../../Misc/NEWS:2473 +msgid "" +"Fix crash in itertools.cycle.__setstate__() when the first argument wasn't a " +"list." +msgstr "" + +#: ../../../Misc/NEWS:2476 +msgid "" +"`Issue #20059 `__: urllib.parse raises " +"ValueError on all invalid ports. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:2479 +msgid "" +"`Issue #24360 `__: Improve __repr__ of " +"argparse.Namespace() for invalid identifiers. Patch by Matthias Bussonnier." +msgstr "" + +#: ../../../Misc/NEWS:2482 +msgid "" +"`Issue #23426 `__: run_setup was broken in " +"distutils. Patch from Alexander Belopolsky." +msgstr "" + +#: ../../../Misc/NEWS:2485 +msgid "" +"`Issue #13938 `__: 2to3 converts StringTypes " +"to a tuple. Patch from Mark Hammond." +msgstr "" + +#: ../../../Misc/NEWS:2487 +msgid "" +"`Issue #2091 `__: open() accepted a 'U' mode " +"string containing '+', but 'U' can only be used with 'r'. Patch from Jeff " +"Balogh and John O'Connor." +msgstr "" + +#: ../../../Misc/NEWS:2490 +msgid "" +"`Issue #8585 `__: improved tests for " +"zipimporter2. Patch from Mark Lawrence." +msgstr "" + +#: ../../../Misc/NEWS:2492 +msgid "" +"`Issue #18622 `__: unittest.mock.mock_open()." +"reset_mock would recurse infinitely. Patch from Nicola Palumbo and Laurent " +"De Buyst." +msgstr "" + +#: ../../../Misc/NEWS:2495 +msgid "" +"`Issue #24426 `__: Fast searching " +"optimization in regular expressions now works for patterns that starts with " +"capturing groups. Fast searching optimization now can't be disabled at " +"compile time." +msgstr "" + +#: ../../../Misc/NEWS:2499 +msgid "" +"`Issue #23661 `__: unittest.mock side_effects " +"can now be exceptions again. This was a regression vs Python 3.4. Patch from " +"Ignacio Rossi" +msgstr "" + +#: ../../../Misc/NEWS:2502 +msgid "" +"`Issue #13248 `__: Remove deprecated inspect." +"getmoduleinfo function." +msgstr "" + +#: ../../../Misc/NEWS:2504 ../../../Misc/NEWS:3105 +msgid "" +"`Issue #25578 `__: Fix (another) memory leak " +"in SSLSocket.getpeercer()." +msgstr "" + +#: ../../../Misc/NEWS:2506 ../../../Misc/NEWS:3107 +msgid "" +"`Issue #25530 `__: Disable the vulnerable " +"SSLv3 protocol by default when creating ssl.SSLContext." +msgstr "" + +#: ../../../Misc/NEWS:2509 ../../../Misc/NEWS:3110 +msgid "" +"`Issue #25569 `__: Fix memory leak in " +"SSLSocket.getpeercert()." +msgstr "" + +#: ../../../Misc/NEWS:2511 ../../../Misc/NEWS:3112 +msgid "" +"`Issue #25471 `__: Sockets returned from " +"accept() shouldn't appear to be nonblocking." +msgstr "" + +#: ../../../Misc/NEWS:2514 ../../../Misc/NEWS:3115 +msgid "" +"`Issue #25319 `__: When threading.Event is " +"reinitialized, the underlying condition should use a regular lock rather " +"than a recursive lock." +msgstr "" + +#: ../../../Misc/NEWS:2517 +msgid "" +"Skip getaddrinfo if host is already resolved. Patch by A. Jesse Jiryu Davis." +msgstr "" + +#: ../../../Misc/NEWS:2520 +msgid "" +"`Issue #26050 `__: Add asyncio.StreamReader." +"readuntil() method. Patch by Марк Коренберг." +msgstr "" + +#: ../../../Misc/NEWS:2523 +msgid "" +"`Issue #25924 `__: Avoid unnecessary " +"serialization of getaddrinfo(3) calls on OS X versions 10.5 or higher. " +"Original patch by A. Jesse Jiryu Davis." +msgstr "" + +#: ../../../Misc/NEWS:2526 +msgid "" +"`Issue #26406 `__: Avoid unnecessary " +"serialization of getaddrinfo(3) calls on current versions of OpenBSD and " +"NetBSD. Patch by A. Jesse Jiryu Davis." +msgstr "" + +#: ../../../Misc/NEWS:2529 +msgid "" +"`Issue #26848 `__: Fix asyncio/subprocess." +"communicate() to handle empty input. Patch by Jack O'Connor." +msgstr "" + +#: ../../../Misc/NEWS:2532 +msgid "" +"`Issue #27040 `__: Add loop." +"get_exception_handler method" +msgstr "" + +#: ../../../Misc/NEWS:2534 +msgid "" +"`Issue #27041 `__: asyncio: Add loop." +"create_future method" +msgstr "" + +#: ../../../Misc/NEWS:2539 +msgid "" +"`Issue #20640 `__: Add tests for idlelib." +"configHelpSourceEdit. Patch by Saimadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:2542 +msgid "" +"In the 'IDLE-console differences' section of the IDLE doc, clarify how " +"running with IDLE affects sys.modules and the standard streams." +msgstr "" + +#: ../../../Misc/NEWS:2545 +msgid "" +"`Issue #25507 `__: fix incorrect change in " +"IOBinding that prevented printing. Augment IOBinding htest to include all " +"major IOBinding functions." +msgstr "" + +#: ../../../Misc/NEWS:2548 +msgid "" +"`Issue #25905 `__: Revert unwanted conversion " +"of ' to ’ RIGHT SINGLE QUOTATION MARK in README.txt and open this and NEWS." +"txt with 'ascii'. Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'." +msgstr "" + +#: ../../../Misc/NEWS:2552 ../../../Misc/NEWS:3144 +msgid "" +"`Issue #15348 `__: Stop the debugger engine " +"(normally in a user process) before closing the debugger window (running in " +"the IDLE process). This prevents the RuntimeErrors that were being caught " +"and ignored." +msgstr "" + +#: ../../../Misc/NEWS:2556 ../../../Misc/NEWS:3148 +msgid "" +"`Issue #24455 `__: Prevent IDLE from hanging " +"when a) closing the shell while the debugger is active (15347); b) closing " +"the debugger with the [X] button (15348); and c) activating the debugger " +"when already active (24455). The patch by Mark Roseman does this by making " +"two changes. 1. Suspend and resume the gui.interaction method with the tcl " +"vwait mechanism intended for this purpose (instead of root.mainloop & ." +"quit). 2. In gui.run, allow any existing interaction to terminate first." +msgstr "" + +#: ../../../Misc/NEWS:2564 ../../../Misc/NEWS:3156 +msgid "" +"Change 'The program' to 'Your program' in an IDLE 'kill program?' message to " +"make it clearer that the program referred to is the currently running user " +"program, not IDLE itself." +msgstr "" + +#: ../../../Misc/NEWS:2568 ../../../Misc/NEWS:3160 +msgid "" +"`Issue #24750 `__: Improve the appearance of " +"the IDLE editor window status bar. Patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2571 ../../../Misc/NEWS:3163 +msgid "" +"`Issue #25313 `__: Change the handling of new " +"built-in text color themes to better address the compatibility problem " +"introduced by the addition of IDLE Dark. Consistently use the revised " +"idleConf.CurrentTheme everywhere in idlelib." +msgstr "" + +#: ../../../Misc/NEWS:2575 ../../../Misc/NEWS:3167 +msgid "" +"`Issue #24782 `__: Extension configuration is " +"now a tab in the IDLE Preferences dialog rather than a separate dialog. The " +"former tabs are now a sorted list. Patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2579 ../../../Misc/NEWS:3171 +msgid "" +"`Issue #22726 `__: Re-activate the config " +"dialog help button with some content about the other buttons and the new " +"IDLE Dark theme." +msgstr "" + +#: ../../../Misc/NEWS:2582 ../../../Misc/NEWS:3174 +msgid "" +"`Issue #24820 `__: IDLE now has an 'IDLE " +"Dark' built-in text color theme. It is more or less IDLE Classic inverted, " +"with a cobalt blue background. Strings, comments, keywords, ... are still " +"green, red, orange, ... . To use it with IDLEs released before November " +"2015, hit the 'Save as New Custom Theme' button and enter a new name, such " +"as 'Custom Dark'. The custom theme will work with any IDLE release, and can " +"be modified." +msgstr "" + +#: ../../../Misc/NEWS:2590 ../../../Misc/NEWS:3182 +msgid "" +"`Issue #25224 `__: README.txt is now an " +"idlelib index for IDLE developers and curious users. The previous user " +"content is now in the IDLE doc chapter. 'IDLE' now means 'Integrated " +"Development and Learning Environment'." +msgstr "" + +#: ../../../Misc/NEWS:2594 ../../../Misc/NEWS:3186 +msgid "" +"`Issue #24820 `__: Users can now set " +"breakpoint colors in Settings -> Custom Highlighting. Original patch by " +"Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2597 ../../../Misc/NEWS:3189 +msgid "" +"`Issue #24972 `__: Inactive selection " +"background now matches active selection background, as configured by users, " +"on all systems. Found items are now always highlighted on Windows. Initial " +"patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2601 ../../../Misc/NEWS:3193 +msgid "" +"`Issue #24570 `__: Idle: make calltip and " +"completion boxes appear on Macs affected by a tk regression. Initial patch " +"by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2604 ../../../Misc/NEWS:3196 +msgid "" +"`Issue #24988 `__: Idle ScrolledList context " +"menus (used in debugger) now work on Mac Aqua. Patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2607 ../../../Misc/NEWS:3199 +msgid "" +"`Issue #24801 `__: Make right-click for " +"context menu work on Mac Aqua. Patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2610 ../../../Misc/NEWS:3202 +msgid "" +"`Issue #25173 `__: Associate tkinter " +"messageboxes with a specific widget. For Mac OSX, make them a 'sheet'. " +"Patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:2613 ../../../Misc/NEWS:3205 +msgid "" +"`Issue #25198 `__: Enhance the initial html " +"viewer now used for Idle Help. * Properly indent fixed-pitch text (patch by " +"Mark Roseman). * Give code snippet a very Sphinx-like light blueish-gray " +"background. * Re-use initial width and height set by users for shell and " +"editor. * When the Table of Contents (TOC) menu is used, put the section " +"header at the top of the screen." +msgstr "" + +#: ../../../Misc/NEWS:2620 ../../../Misc/NEWS:3212 +msgid "" +"`Issue #25225 `__: Condense and rewrite Idle " +"doc section on text colors." +msgstr "" + +#: ../../../Misc/NEWS:2622 ../../../Misc/NEWS:3214 +msgid "" +"`Issue #21995 `__: Explain some differences " +"between IDLE and console Python." +msgstr "" + +#: ../../../Misc/NEWS:2624 ../../../Misc/NEWS:3216 +msgid "" +"`Issue #22820 `__: Explain need for *print* " +"when running file from Idle editor." +msgstr "" + +#: ../../../Misc/NEWS:2626 ../../../Misc/NEWS:3218 +msgid "" +"`Issue #25224 `__: Doc: augment Idle feature " +"list and no-subprocess section." +msgstr "" + +#: ../../../Misc/NEWS:2628 ../../../Misc/NEWS:3220 +msgid "" +"`Issue #25219 `__: Update doc for Idle " +"command line options. Some were missing and notes were not correct." +msgstr "" + +#: ../../../Misc/NEWS:2631 ../../../Misc/NEWS:3223 +msgid "" +"`Issue #24861 `__: Most of idlelib is private " +"and subject to change. Use idleib.idle.* to start Idle. See idlelib.__init__." +"__doc__." +msgstr "" + +#: ../../../Misc/NEWS:2634 ../../../Misc/NEWS:3226 +msgid "" +"`Issue #25199 `__: Idle: add synchronization " +"comments for future maintainers." +msgstr "" + +#: ../../../Misc/NEWS:2636 +msgid "" +"`Issue #16893 `__: Replace help.txt with help." +"html for Idle doc display. The new idlelib/help.html is rstripped Doc/build/" +"html/library/idle.html. It looks better than help.txt and will better " +"document Idle as released. The tkinter html viewer that works for this file " +"was written by Rose Roseman. The now unused EditorWindow.HelpDialog class " +"and helt.txt file are deprecated." +msgstr "" + +#: ../../../Misc/NEWS:2642 ../../../Misc/NEWS:3234 +msgid "" +"`Issue #24199 `__: Deprecate unused idlelib." +"idlever with possible removal in 3.6." +msgstr "" + +#: ../../../Misc/NEWS:2644 ../../../Misc/NEWS:3236 +msgid "" +"`Issue #24790 `__: Remove extraneous code " +"(which also create 2 & 3 conflicts)." +msgstr "" + +#: ../../../Misc/NEWS:2649 +msgid "" +"`Issue #26736 `__: Used HTTPS for external " +"links in the documentation if possible." +msgstr "" + +#: ../../../Misc/NEWS:2651 +msgid "" +"`Issue #6953 `__: Rework the Readline module " +"documentation to group related functions together, and add more details such " +"as what underlying Readline functions and variables are accessed." +msgstr "" + +#: ../../../Misc/NEWS:2655 +msgid "" +"`Issue #23606 `__: Adds note to ctypes " +"documentation regarding cdll.msvcrt." +msgstr "" + +#: ../../../Misc/NEWS:2657 ../../../Misc/NEWS:3248 +msgid "" +"`Issue #24952 `__: Clarify the default size " +"argument of stack_size() in the \"threading\" and \"_thread\" modules. Patch " +"from Mattip." +msgstr "" + +#: ../../../Misc/NEWS:2660 +msgid "" +"`Issue #26014 `__: Update 3.x packaging " +"documentation: * \"See also\" links to the new docs are now provided in the " +"legacy pages * links to setuptools documentation have been updated" +msgstr "" + +#: ../../../Misc/NEWS:2667 +msgid "" +"`Issue #21916 `__: Added tests for the turtle " +"module. Patch by ingrid, Gregory Loyse and Jelle Zijlstra." +msgstr "" + +#: ../../../Misc/NEWS:2670 +msgid "" +"`Issue #26295 `__: When using \"python3 -m " +"test --testdir=TESTDIR\", regrtest doesn't add \"test.\" prefix to test " +"module names." +msgstr "" + +#: ../../../Misc/NEWS:2673 +msgid "" +"`Issue #26523 `__: The multiprocessing thread " +"pool (multiprocessing.dummy.Pool) was untested." +msgstr "" + +#: ../../../Misc/NEWS:2676 +msgid "" +"`Issue #26015 `__: Added new tests for " +"pickling iterators of mutable sequences." +msgstr "" + +#: ../../../Misc/NEWS:2678 +msgid "" +"`Issue #26325 `__: Added test.support." +"check_no_resource_warning() to check that no ResourceWarning is emitted." +msgstr "" + +#: ../../../Misc/NEWS:2681 +msgid "" +"`Issue #25940 `__: Changed test_ssl to use " +"its internal local server more. This avoids relying on svn.python.org, " +"which recently changed root certificate." +msgstr "" + +#: ../../../Misc/NEWS:2684 +msgid "" +"`Issue #25616 `__: Tests for OrderedDict are " +"extracted from test_collections into separate file test_ordered_dict." +msgstr "" + +#: ../../../Misc/NEWS:2687 ../../../Misc/NEWS:3263 +msgid "" +"`Issue #25449 `__: Added tests for " +"OrderedDict subclasses." +msgstr "" + +#: ../../../Misc/NEWS:2689 +msgid "" +"`Issue #25188 `__: Add -P/--pgo to test." +"regrtest to suppress error output when running the test suite for the " +"purposes of a PGO build. Initial patch by Alecsandru Patrascu." +msgstr "" + +#: ../../../Misc/NEWS:2693 +msgid "" +"`Issue #22806 `__: Add ``python -m test --" +"list-tests`` command to list tests." +msgstr "" + +#: ../../../Misc/NEWS:2695 +msgid "" +"`Issue #18174 `__: ``python -m test --" +"huntrleaks ...`` now also checks for leak of file descriptors. Patch written " +"by Richard Oudkerk." +msgstr "" + +#: ../../../Misc/NEWS:2698 +msgid "" +"`Issue #25260 `__: Fix ``python -m test --" +"coverage`` on Windows. Remove the list of ignored directories." +msgstr "" + +#: ../../../Misc/NEWS:2701 ../../../Misc/NEWS:3270 +msgid "" +"``PCbuild\\rt.bat`` now accepts an unlimited number of arguments to pass " +"along to regrtest.py. Previously there was a limit of 9." +msgstr "" + +#: ../../../Misc/NEWS:2704 +msgid "" +"`Issue #26583 `__: Skip " +"test_timestamp_overflow in test_import if bytecode files cannot be written." +msgstr "" + +#: ../../../Misc/NEWS:2710 +msgid "" +"`Issue #21277 `__: Don't try to link _ctypes " +"with a ffi_convenience library." +msgstr "" + +#: ../../../Misc/NEWS:2712 +msgid "" +"`Issue #26884 `__: Fix linking extension " +"modules for cross builds. Patch by Xavier de Gaye." +msgstr "" + +#: ../../../Misc/NEWS:2715 +msgid "" +"`Issue #26932 `__: Fixed support of RTLD_* " +"constants defined as enum values, not via macros (in particular on " +"Android). Patch by Chi Hsuan Yen." +msgstr "" + +#: ../../../Misc/NEWS:2718 +msgid "" +"`Issue #22359 `__: Disable the rules for " +"running _freeze_importlib and pgen when cross-compiling. The output of " +"these programs is normally saved with the source code anyway, and is still " +"regenerated when doing a native build. Patch by Xavier de Gaye." +msgstr "" + +#: ../../../Misc/NEWS:2723 +msgid "" +"`Issue #21668 `__: Link audioop, _datetime, " +"_ctypes_test modules to libm, except on Mac OS X. Patch written by Chi Hsuan " +"Yen." +msgstr "" + +#: ../../../Misc/NEWS:2726 +msgid "" +"`Issue #25702 `__: A --with-lto configure " +"option has been added that will enable link time optimizations at build time " +"during a make profile-opt. Some compilers and toolchains are known to not " +"produce stable code when using LTO, be sure to test things thoroughly before " +"relying on it. It can provide a few % speed up over profile-opt alone." +msgstr "" + +#: ../../../Misc/NEWS:2732 +msgid "" +"`Issue #26624 `__: Adds validation of " +"ucrtbase[d].dll version with warning for old versions." +msgstr "" + +#: ../../../Misc/NEWS:2735 +msgid "" +"`Issue #17603 `__: Avoid error about " +"nonexistant fileblocks.o file by using a lower-level check for st_blocks in " +"struct stat." +msgstr "" + +#: ../../../Misc/NEWS:2738 +msgid "" +"`Issue #26079 `__: Fixing the build output " +"folder for tix-8.4.3.6. Patch by Bjoern Thiel." +msgstr "" + +#: ../../../Misc/NEWS:2741 +msgid "" +"`Issue #26465 `__: Update Windows builds to " +"use OpenSSL 1.0.2g." +msgstr "" + +#: ../../../Misc/NEWS:2743 +msgid "" +"`Issue #25348 `__: Added ``--pgo`` and ``--" +"pgo-job`` arguments to ``PCbuild\\build.bat`` for building with Profile-" +"Guided Optimization. The old ``PCbuild\\build_pgo.bat`` script is removed." +msgstr "" + +#: ../../../Misc/NEWS:2747 +msgid "" +"`Issue #25827 `__: Add support for building " +"with ICC to ``configure``, including a new ``--with-icc`` flag." +msgstr "" + +#: ../../../Misc/NEWS:2750 +msgid "" +"`Issue #25696 `__: Fix installation of Python " +"on UNIX with make -j9." +msgstr "" + +#: ../../../Misc/NEWS:2752 ../../../Misc/NEWS:3281 +msgid "" +"`Issue #24986 `__: It is now possible to " +"build Python on Windows without errors when external libraries are not " +"available." +msgstr "" + +#: ../../../Misc/NEWS:2755 +msgid "" +"`Issue #24421 `__: Compile Modules/_math.c " +"once, before building extensions. Previously it could fail to compile " +"properly if the math and cmath builds were concurrent." +msgstr "" + +#: ../../../Misc/NEWS:2759 +msgid "" +"`Issue #26465 `__: Update OS X 10.5+ 32-bit-" +"only installer to build and link with OpenSSL 1.0.2g." +msgstr "" + +#: ../../../Misc/NEWS:2762 +msgid "" +"`Issue #26268 `__: Update Windows builds to " +"use OpenSSL 1.0.2f." +msgstr "" + +#: ../../../Misc/NEWS:2764 +msgid "" +"`Issue #25136 `__: Support Apple Xcode 7's " +"new textual SDK stub libraries." +msgstr "" + +#: ../../../Misc/NEWS:2766 +msgid "" +"`Issue #24324 `__: Do not enable unreachable " +"code warnings when using gcc as the option does not work correctly in older " +"versions of gcc and has been silently removed as of gcc-4.5." +msgstr "" + +#: ../../../Misc/NEWS:2773 +msgid "" +"`Issue #27053 `__: Updates make_zip.py to " +"correctly generate library ZIP file." +msgstr "" + +#: ../../../Misc/NEWS:2775 +msgid "" +"`Issue #26268 `__: Update the prepare_ssl.py " +"script to handle OpenSSL releases that don't include the contents of the " +"include directory (that is, 1.0.2e and later)." +msgstr "" + +#: ../../../Misc/NEWS:2779 +msgid "" +"`Issue #26071 `__: bdist_wininst created " +"binaries fail to start and find 32bit Python" +msgstr "" + +#: ../../../Misc/NEWS:2782 +msgid "" +"`Issue #26073 `__: Update the list of magic " +"numbers in launcher" +msgstr "" + +#: ../../../Misc/NEWS:2784 +msgid "" +"`Issue #26065 `__: Excludes venv from library " +"when generating embeddable distro." +msgstr "" + +#: ../../../Misc/NEWS:2787 ../../../Misc/NEWS:3320 +msgid "" +"`Issue #25022 `__: Removed very outdated PC/" +"example_nt/ directory." +msgstr "" + +#: ../../../Misc/NEWS:2792 +msgid "" +"`Issue #26799 `__: Fix python-gdb.py: don't " +"get C types once when the Python code is loaded, but get C types on demand. " +"The C types can change if python-gdb.py is loaded before the Python " +"executable. Patch written by Thomas Ilsche." +msgstr "" + +#: ../../../Misc/NEWS:2797 +msgid "" +"`Issue #26271 `__: Fix the Freeze tool to " +"properly use flags passed through configure. Patch by Daniel Shaulov." +msgstr "" + +#: ../../../Misc/NEWS:2800 +msgid "" +"`Issue #26489 `__: Add dictionary unpacking " +"support to Tools/parser/unparse.py. Patch by Guo Ci Teo." +msgstr "" + +#: ../../../Misc/NEWS:2803 +msgid "" +"`Issue #26316 `__: Fix variable name typo in " +"Argument Clinic." +msgstr "" + +#: ../../../Misc/NEWS:2805 ../../../Misc/NEWS:3325 +msgid "" +"`Issue #25440 `__: Fix output of python-" +"config --extension-suffix." +msgstr "" + +#: ../../../Misc/NEWS:2807 +msgid "" +"`Issue #25154 `__: The pyvenv script has been " +"deprecated in favour of `python3 -m venv`." +msgstr "" + +#: ../../../Misc/NEWS:2813 +msgid "" +"`Issue #26312 `__: SystemError is now raised " +"in all programming bugs with using PyArg_ParseTupleAndKeywords(). " +"RuntimeError did raised before in some programming bugs." +msgstr "" + +#: ../../../Misc/NEWS:2817 +msgid "" +"`Issue #26198 `__: ValueError is now raised " +"instead of TypeError on buffer overflow in parsing \"es#\" and \"et#\" " +"format units. SystemError is now raised instead of TypeError on " +"programmical error in parsing format string." +msgstr "" + +#: ../../../Misc/NEWS:2823 +msgid "Python 3.5.1 final" +msgstr "" + +#: ../../../Misc/NEWS:2825 +msgid "Release date: 2015-12-06" +msgstr "" + +#: ../../../Misc/NEWS:2836 +msgid "" +"`Issue #25715 `__: Python 3.5.1 installer " +"shows wrong upgrade path and incorrect logic for launcher detection." +msgstr "" + +#: ../../../Misc/NEWS:2841 +msgid "Python 3.5.1 release candidate 1" +msgstr "" + +#: ../../../Misc/NEWS:2843 +msgid "Release date: 2015-11-22" +msgstr "" + +#: ../../../Misc/NEWS:2901 +msgid "" +"`Issue #25182 `__: The stdprinter (used as " +"sys.stderr before the io module is imported at startup) now uses the " +"backslashreplace error handler." +msgstr "" + +#: ../../../Misc/NEWS:2904 +msgid "" +"`Issue #25131 `__: Make the line number and " +"column offset of set/dict literals and comprehensions correspond to the " +"opening brace." +msgstr "" + +#: ../../../Misc/NEWS:2907 +msgid "" +"`Issue #25150 `__: Hide the private " +"_Py_atomic_xxx symbols from the public Python.h header to fix a compilation " +"error with OpenMP. PyThreadState_GET() becomes an alias to " +"PyThreadState_Get() to avoid ABI incompatibilies." +msgstr "" + +#: ../../../Misc/NEWS:2930 +msgid "" +"`Issue #25590 `__: In the Readline completer, " +"only call getattr() once per attribute." +msgstr "" + +#: ../../../Misc/NEWS:3008 +msgid "" +"`Issue #24483 `__: C implementation of " +"functools.lru_cache() now calculates key's hash only once." +msgstr "" + +#: ../../../Misc/NEWS:3011 +msgid "" +"`Issue #22958 `__: Constructor and update " +"method of weakref.WeakValueDictionary now accept the self and the dict " +"keyword arguments." +msgstr "" + +#: ../../../Misc/NEWS:3014 +msgid "" +"`Issue #22609 `__: Constructor of collections." +"UserDict now accepts the self keyword argument." +msgstr "" + +#: ../../../Misc/NEWS:3017 +msgid "" +"`Issue #25111 `__: Fixed comparison of " +"traceback.FrameSummary." +msgstr "" + +#: ../../../Misc/NEWS:3019 +msgid "" +"`Issue #25262 `__: Added support for " +"BINBYTES8 opcode in Python implementation of unpickler. Highest 32 bits of " +"64-bit size for BINUNICODE8 and BINBYTES8 opcodes no longer silently ignored " +"on 32-bit platforms in C implementation." +msgstr "" + +#: ../../../Misc/NEWS:3023 +msgid "" +"`Issue #25034 `__: Fix string.Formatter " +"problem with auto-numbering and nested format_specs. Patch by Anthon van der " +"Neut." +msgstr "" + +#: ../../../Misc/NEWS:3026 +msgid "" +"`Issue #25233 `__: Rewrite the guts of " +"asyncio.Queue and asyncio.Semaphore to be more understandable and correct." +msgstr "" + +#: ../../../Misc/NEWS:3035 +msgid "" +"`Issue #23329 `__: Allow the ssl module to be " +"built with older versions of LibreSSL." +msgstr "" + +#: ../../../Misc/NEWS:3038 +msgid "Prevent overflow in _Unpickler_Read." +msgstr "" + +#: ../../../Misc/NEWS:3040 +msgid "" +"`Issue #25047 `__: The XML encoding " +"declaration written by Element Tree now respects the letter case given by " +"the user. This restores the ability to write encoding names in uppercase " +"like \"UTF-8\", which worked in Python 2." +msgstr "" + +#: ../../../Misc/NEWS:3044 +msgid "" +"`Issue #25135 `__: Make deque_clear() safer " +"by emptying the deque before clearing. This helps avoid possible reentrancy " +"issues." +msgstr "" + +#: ../../../Misc/NEWS:3047 +msgid "" +"`Issue #19143 `__: platform module now reads " +"Windows version from kernel32.dll to avoid compatibility shims." +msgstr "" + +#: ../../../Misc/NEWS:3050 +msgid "" +"`Issue #25092 `__: Fix datetime.strftime() " +"failure when errno was already set to EINVAL." +msgstr "" + +#: ../../../Misc/NEWS:3053 +msgid "" +"`Issue #23517 `__: Fix rounding in " +"fromtimestamp() and utcfromtimestamp() methods of datetime.datetime: " +"microseconds are now rounded to nearest with ties going to nearest even " +"integer (ROUND_HALF_EVEN), instead of being rounding towards minus infinity " +"(ROUND_FLOOR). It's important that these methods use the same rounding mode " +"than datetime.timedelta to keep the property: (datetime(1970,1,1) + " +"timedelta(seconds=t)) == datetime.utcfromtimestamp(t). It also the rounding " +"mode used by round(float) for example." +msgstr "" + +#: ../../../Misc/NEWS:3061 +msgid "" +"`Issue #25155 `__: Fix datetime.datetime." +"now() and datetime.datetime.utcnow() on Windows to support date after year " +"2038. It was a regression introduced in Python 3.5.0." +msgstr "" + +#: ../../../Misc/NEWS:3065 +msgid "" +"`Issue #25108 `__: Omitted internal frames in " +"traceback functions print_stack(), format_stack(), and extract_stack() " +"called without arguments." +msgstr "" + +#: ../../../Misc/NEWS:3068 +msgid "" +"`Issue #25118 `__: Fix a regression of Python " +"3.5.0 in os.waitpid() on Windows." +msgstr "" + +#: ../../../Misc/NEWS:3070 +msgid "" +"`Issue #24684 `__: socket.socket." +"getaddrinfo() now calls PyUnicode_AsEncodedString() instead of calling the " +"encode() method of the host, to handle correctly custom string with an " +"encode() method which doesn't return a byte string. The encoder of the IDNA " +"codec is now called directly instead of calling the encode() method of the " +"string." +msgstr "" + +#: ../../../Misc/NEWS:3076 +msgid "" +"`Issue #25060 `__: Correctly compute stack " +"usage of the BUILD_MAP opcode." +msgstr "" + +#: ../../../Misc/NEWS:3078 +msgid "" +"`Issue #24857 `__: Comparing call_args to a " +"long sequence now correctly returns a boolean result instead of raising an " +"exception. Patch by A Kaptur." +msgstr "" + +#: ../../../Misc/NEWS:3081 +msgid "" +"`Issue #23144 `__: Make sure that HTMLParser." +"feed() returns all the data, even when convert_charrefs is True." +msgstr "" + +#: ../../../Misc/NEWS:3084 +msgid "" +"`Issue #24982 `__: shutil.make_archive() with " +"the \"zip\" format now adds entries for directories (including empty " +"directories) in ZIP file." +msgstr "" + +#: ../../../Misc/NEWS:3087 +msgid "" +"`Issue #25019 `__: Fixed a crash caused by " +"setting non-string key of expat parser. Based on patch by John Leitch." +msgstr "" + +#: ../../../Misc/NEWS:3090 +msgid "" +"`Issue #16180 `__: Exit pdb if file has " +"syntax error, instead of trapping user in an infinite loop. Patch by Xavier " +"de Gaye." +msgstr "" + +#: ../../../Misc/NEWS:3093 +msgid "" +"`Issue #24891 `__: Fix a race condition at " +"Python startup if the file descriptor of stdin (0), stdout (1) or stderr (2) " +"is closed while Python is creating sys.stdin, sys.stdout and sys.stderr " +"objects. These attributes are now set to None if the creation of the object " +"failed, instead of raising an OSError exception. Initial patch written by " +"Marco Paolini." +msgstr "" + +#: ../../../Misc/NEWS:3099 +msgid "" +"`Issue #24992 `__: Fix error handling and a " +"race condition (related to garbage collection) in collections.OrderedDict " +"constructor." +msgstr "" + +#: ../../../Misc/NEWS:3102 +msgid "" +"`Issue #24881 `__: Fixed setting binary mode " +"in Python implementation of FileIO on Windows and Cygwin. Patch from Akira " +"Li." +msgstr "" + +#: ../../../Misc/NEWS:3118 +msgid "" +"`Issue #21112 `__: Fix regression in unittest." +"expectedFailure on subclasses. Patch from Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:3121 +msgid "" +"`Issue #24764 `__: cgi.FieldStorage." +"read_multi() now ignores the Content-Length header in part headers. Patch " +"written by Peter Landry and reviewed by Pierre Quentel." +msgstr "" + +#: ../../../Misc/NEWS:3125 ../../../Misc/NEWS:3388 +msgid "" +"`Issue #24913 `__: Fix overrun error in deque." +"index(). Found by John Leitch and Bryce Darling." +msgstr "" + +#: ../../../Misc/NEWS:3128 +msgid "" +"`Issue #24774 `__: Fix docstring in http." +"server.test. Patch from Chiu-Hsiang Hsu." +msgstr "" + +#: ../../../Misc/NEWS:3130 +msgid "" +"`Issue #21159 `__: Improve message in " +"configparser.InterpolationMissingOptionError. Patch from �?ukasz Langa." +msgstr "" + +#: ../../../Misc/NEWS:3133 +msgid "" +"`Issue #20362 `__: Honour TestCase." +"longMessage correctly in assertRegex. Patch from Ilia Kurenkov." +msgstr "" + +#: ../../../Misc/NEWS:3136 +msgid "" +"`Issue #23572 `__: Fixed functools." +"singledispatch on classes with falsy metaclasses. Patch by Ethan Furman." +msgstr "" + +#: ../../../Misc/NEWS:3139 +msgid "asyncio: ensure_future() now accepts awaitable objects." +msgstr "" + +#: ../../../Misc/NEWS:3228 +msgid "" +"`Issue #16893 `__: Replace help.txt with help." +"html for Idle doc display. The new idlelib/help.html is rstripped Doc/build/" +"html/library/idle.html. It looks better than help.txt and will better " +"document Idle as released. The tkinter html viewer that works for this file " +"was written by Mark Roseman. The now unused EditorWindow.HelpDialog class " +"and helt.txt file are deprecated." +msgstr "" + +#: ../../../Misc/NEWS:3241 +msgid "" +"`Issue #12067 `__: Rewrite Comparisons " +"section in the Expressions chapter of the language reference. Some of the " +"details of comparing mixed types were incorrect or ambiguous. NotImplemented " +"is only relevant at a lower level than the Expressions chapter. Added " +"details of comparing range() objects, and default behaviour and consistency " +"suggestions for user-defined classes. Patch from Andy Maier." +msgstr "" + +#: ../../../Misc/NEWS:3251 +msgid "" +"`Issue #23725 `__: Overhaul tempfile docs. " +"Note deprecated status of mktemp. Patch from Zbigniew Jędrzejewski-Szmek." +msgstr "" + +#: ../../../Misc/NEWS:3254 +msgid "" +"`Issue #24808 `__: Update the types of some " +"PyTypeObject fields. Patch by Joseph Weston." +msgstr "" + +#: ../../../Misc/NEWS:3257 +msgid "" +"`Issue #22812 `__: Fix unittest discovery " +"examples. Patch from Pam McA'Nulty." +msgstr "" + +#: ../../../Misc/NEWS:3265 +msgid "" +"`Issue #25099 `__: Make test_compileall not " +"fail when an entry on sys.path cannot be written to (commonly seen in " +"administrative installs on Windows)." +msgstr "" + +#: ../../../Misc/NEWS:3268 +msgid "" +"`Issue #23919 `__: Prevents assert dialogs " +"appearing in the test suite." +msgstr "" + +#: ../../../Misc/NEWS:3276 +msgid "" +"`Issue #24915 `__: Add LLVM support for PGO " +"builds and use the test suite to generate the profile data. Initial patch by " +"Alecsandru Patrascu of Intel." +msgstr "" + +#: ../../../Misc/NEWS:3279 +msgid "" +"`Issue #24910 `__: Windows MSIs now have " +"unique display names." +msgstr "" + +#: ../../../Misc/NEWS:3287 +msgid "" +"`Issue #25450 `__: Updates shortcuts to start " +"Python in installation directory." +msgstr "" + +#: ../../../Misc/NEWS:3289 +msgid "" +"`Issue #25164 `__: Changes default all-users " +"install directory to match per-user directory." +msgstr "" + +#: ../../../Misc/NEWS:3292 +msgid "" +"`Issue #25143 `__: Improves installer error " +"messages for unsupported platforms." +msgstr "" + +#: ../../../Misc/NEWS:3294 +msgid "" +"`Issue #25163 `__: Display correct directory " +"in installer when using non-default settings." +msgstr "" + +#: ../../../Misc/NEWS:3297 +msgid "" +"`Issue #25361 `__: Disables use of SSE2 " +"instructions in Windows 32-bit build" +msgstr "" + +#: ../../../Misc/NEWS:3299 +msgid "" +"`Issue #25089 `__: Adds logging to installer " +"for case where launcher is not selected on upgrade." +msgstr "" + +#: ../../../Misc/NEWS:3302 +msgid "" +"`Issue #25165 `__: Windows uninstallation " +"should not remove launcher if other versions remain" +msgstr "" + +#: ../../../Misc/NEWS:3305 +msgid "" +"`Issue #25112 `__: py.exe launcher is missing " +"icons" +msgstr "" + +#: ../../../Misc/NEWS:3307 +msgid "" +"`Issue #25102 `__: Windows installer does not " +"precompile for -O or -OO." +msgstr "" + +#: ../../../Misc/NEWS:3309 +msgid "" +"`Issue #25081 `__: Makes Back button in " +"installer go back to upgrade page when upgrading." +msgstr "" + +#: ../../../Misc/NEWS:3312 +msgid "" +"`Issue #25091 `__: Increases font size of the " +"installer." +msgstr "" + +#: ../../../Misc/NEWS:3314 +msgid "" +"`Issue #25126 `__: Clarifies that the non-web " +"installer will download some components." +msgstr "" + +#: ../../../Misc/NEWS:3317 +msgid "" +"`Issue #25213 `__: Restores " +"requestedExecutionLevel to manifest to disable UAC virtualization." +msgstr "" + +#: ../../../Misc/NEWS:3329 +msgid "Python 3.5.0 final" +msgstr "" + +#: ../../../Misc/NEWS:3331 +msgid "Release date: 2015-09-13" +msgstr "" + +#: ../../../Misc/NEWS:3336 +msgid "" +"`Issue #25071 `__: Windows installer should " +"not require TargetDir parameter when installing quietly." +msgstr "" + +#: ../../../Misc/NEWS:3341 +msgid "Python 3.5.0 release candidate 4" +msgstr "" + +#: ../../../Misc/NEWS:3343 +msgid "Release date: 2015-09-09" +msgstr "" + +#: ../../../Misc/NEWS:3348 +msgid "" +"`Issue #25029 `__: Fixes MemoryError in " +"test_strptime." +msgstr "" + +#: ../../../Misc/NEWS:3353 +msgid "" +"`Issue #25027 `__: Reverts partial-static " +"build options and adds vcruntime140.dll to Windows installation." +msgstr "" + +#: ../../../Misc/NEWS:3358 +msgid "Python 3.5.0 release candidate 3" +msgstr "" + +#: ../../../Misc/NEWS:3360 +msgid "Release date: 2015-09-07" +msgstr "" + +#: ../../../Misc/NEWS:3365 +msgid "" +"`Issue #24305 `__: Prevent import subsystem " +"stack frames from being counted by the warnings.warn(stacklevel=) parameter." +msgstr "" + +#: ../../../Misc/NEWS:3368 +msgid "" +"`Issue #24912 `__: Prevent __class__ " +"assignment to immutable built-in objects." +msgstr "" + +#: ../../../Misc/NEWS:3370 +msgid "" +"`Issue #24975 `__: Fix AST compilation for " +"PEP 448 syntax." +msgstr "" + +#: ../../../Misc/NEWS:3375 +msgid "" +"`Issue #24917 `__: time_strftime() buffer " +"over-read." +msgstr "" + +#: ../../../Misc/NEWS:3377 +msgid "" +"`Issue #24748 `__: To resolve a compatibility " +"problem found with py2exe and pywin32, imp.load_dynamic() once again ignores " +"previously loaded modules to support Python modules replacing themselves " +"with extension modules. Patch by Petr Viktorin." +msgstr "" + +#: ../../../Misc/NEWS:3382 +msgid "" +"`Issue #24635 `__: Fixed a bug in typing.py " +"where isinstance([], typing.Iterable) would return True once, then False on " +"subsequent calls." +msgstr "" + +#: ../../../Misc/NEWS:3385 +msgid "" +"`Issue #24989 `__: Fixed buffer overread in " +"BytesIO.readline() if a position is set beyond size. Based on patch by John " +"Leitch." +msgstr "" + +#: ../../../Misc/NEWS:3393 +msgid "Python 3.5.0 release candidate 2" +msgstr "" + +#: ../../../Misc/NEWS:3395 +msgid "Release date: 2015-08-25" +msgstr "" + +#: ../../../Misc/NEWS:3400 +msgid "" +"`Issue #24769 `__: Interpreter now starts " +"properly when dynamic loading is disabled. Patch by Petr Viktorin." +msgstr "" + +#: ../../../Misc/NEWS:3403 +msgid "" +"`Issue #21167 `__: NAN operations are now " +"handled correctly when python is compiled with ICC even if -fp-model strict " +"is not specified." +msgstr "" + +#: ../../../Misc/NEWS:3406 +msgid "" +"`Issue #24492 `__: A \"package\" lacking a " +"__name__ attribute when trying to perform a ``from .. import ...`` statement " +"will trigger an ImportError instead of an AttributeError." +msgstr "" + +#: ../../../Misc/NEWS:3413 +msgid "" +"`Issue #24847 `__: Removes vcruntime140.dll " +"dependency from Tcl/Tk." +msgstr "" + +#: ../../../Misc/NEWS:3415 +msgid "" +"`Issue #24839 `__: platform._syscmd_ver " +"raises DeprecationWarning" +msgstr "" + +#: ../../../Misc/NEWS:3417 +msgid "" +"`Issue #24867 `__: Fix Task.get_stack() for " +"'async def' coroutines" +msgstr "" + +#: ../../../Misc/NEWS:3421 +msgid "Python 3.5.0 release candidate 1" +msgstr "" + +#: ../../../Misc/NEWS:3423 +msgid "Release date: 2015-08-09" +msgstr "" + +#: ../../../Misc/NEWS:3428 +msgid "" +"`Issue #24667 `__: Resize odict in all cases " +"that the underlying dict resizes." +msgstr "" + +#: ../../../Misc/NEWS:3433 +msgid "" +"`Issue #24824 `__: Signatures of codecs." +"encode() and codecs.decode() now are compatible with pydoc." +msgstr "" + +#: ../../../Misc/NEWS:3436 +msgid "" +"`Issue #24634 `__: Importing uuid should not " +"try to load libc on Windows" +msgstr "" + +#: ../../../Misc/NEWS:3438 +msgid "" +"`Issue #24798 `__: _msvccompiler.py doesn't " +"properly support manifests" +msgstr "" + +#: ../../../Misc/NEWS:3440 +msgid "" +"`Issue #4395 `__: Better testing and " +"documentation of binary operators. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:3443 +msgid "" +"`Issue #23973 `__: Update typing.py from " +"GitHub repo." +msgstr "" + +#: ../../../Misc/NEWS:3445 +msgid "" +"`Issue #23004 `__: mock_open() now reads " +"binary data correctly when the type of read_data is bytes. Initial patch by " +"Aaron Hill." +msgstr "" + +#: ../../../Misc/NEWS:3448 +msgid "" +"`Issue #23888 `__: Handle fractional time in " +"cookie expiry. Patch by ssh." +msgstr "" + +#: ../../../Misc/NEWS:3450 +msgid "" +"`Issue #23652 `__: Make it possible to " +"compile the select module against the libc headers from the Linux Standard " +"Base, which do not include some EPOLL macros. Patch by Matt Frank." +msgstr "" + +#: ../../../Misc/NEWS:3454 +msgid "" +"`Issue #22932 `__: Fix timezones in email." +"utils.formatdate. Patch from Dmitry Shachnev." +msgstr "" + +#: ../../../Misc/NEWS:3457 +msgid "" +"`Issue #23779 `__: imaplib raises TypeError " +"if authenticator tries to abort. Patch from Craig Holmquist." +msgstr "" + +#: ../../../Misc/NEWS:3460 +msgid "" +"`Issue #23319 `__: Fix ctypes." +"BigEndianStructure, swap correctly bytes. Patch written by Matthieu Gautier." +msgstr "" + +#: ../../../Misc/NEWS:3463 +msgid "" +"`Issue #23254 `__: Document how to close the " +"TCPServer listening socket. Patch from Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:3466 +msgid "" +"`Issue #19450 `__: Update Windows and OS X " +"installer builds to use SQLite 3.8.11." +msgstr "" + +#: ../../../Misc/NEWS:3468 +msgid "" +"`Issue #17527 `__: Add PATCH to wsgiref." +"validator. Patch from Luca Sbardella." +msgstr "" + +#: ../../../Misc/NEWS:3470 +msgid "" +"`Issue #24791 `__: Fix grammar regression for " +"call syntax: 'g(\\*a or b)'." +msgstr "" + +#: ../../../Misc/NEWS:3475 +msgid "" +"`Issue #23672 `__: Allow Idle to edit and run " +"files with astral chars in name. Patch by Mohd Sanad Zaki Rizvi." +msgstr "" + +#: ../../../Misc/NEWS:3478 +msgid "" +"`Issue #24745 `__: Idle editor default font. " +"Switch from Courier to platform-sensitive TkFixedFont. This should not " +"affect current customized font selections. If there is a problem, edit " +"$HOME/.idlerc/config-main.cfg and remove 'fontxxx' entries from [Editor " +"Window]. Patch by Mark Roseman." +msgstr "" + +#: ../../../Misc/NEWS:3483 +msgid "" +"`Issue #21192 `__: Idle editor. When a file " +"is run, put its name in the restart bar. Do not print false prompts. " +"Original patch by Adnan Umer." +msgstr "" + +#: ../../../Misc/NEWS:3486 +msgid "" +"`Issue #13884 `__: Idle menus. Remove tearoff " +"lines. Patch by Roger Serwy." +msgstr "" + +#: ../../../Misc/NEWS:3491 +msgid "" +"`Issue #24129 `__: Clarify the reference " +"documentation for name resolution. This includes removing the assumption " +"that readers will be familiar with the name resolution scheme Python used " +"prior to the introduction of lexical scoping for function namespaces. Patch " +"by Ivan Levkivskyi." +msgstr "" + +#: ../../../Misc/NEWS:3496 +msgid "" +"`Issue #20769 `__: Improve reload() docs. " +"Patch by Dorian Pula." +msgstr "" + +#: ../../../Misc/NEWS:3498 +msgid "" +"`Issue #23589 `__: Remove duplicate sentence " +"from the FAQ. Patch by Yongzhi Pan." +msgstr "" + +#: ../../../Misc/NEWS:3500 +msgid "" +"`Issue #24729 `__: Correct IO tutorial to " +"match implementation regarding encoding parameter to open function." +msgstr "" + +#: ../../../Misc/NEWS:3506 +msgid "" +"`Issue #24751 `__: When running regrtest with " +"the ``-w`` command line option, a test run is no longer marked as a failure " +"if all tests succeed when re-run." +msgstr "" + +#: ../../../Misc/NEWS:3512 +msgid "Python 3.5.0 beta 4" +msgstr "" + +#: ../../../Misc/NEWS:3514 +msgid "Release date: 2015-07-26" +msgstr "" + +#: ../../../Misc/NEWS:3519 +msgid "" +"`Issue #23573 `__: Restored optimization of " +"bytes.rfind() and bytearray.rfind() for single-byte argument on Linux." +msgstr "" + +#: ../../../Misc/NEWS:3522 +msgid "" +"`Issue #24569 `__: Make PEP 448 dictionary " +"evaluation more consistent." +msgstr "" + +#: ../../../Misc/NEWS:3524 +msgid "" +"`Issue #24583 `__: Fix crash when set is " +"mutated while being updated." +msgstr "" + +#: ../../../Misc/NEWS:3526 +msgid "" +"`Issue #24407 `__: Fix crash when dict is " +"mutated while being updated." +msgstr "" + +#: ../../../Misc/NEWS:3528 +msgid "" +"`Issue #24619 `__: New approach for " +"tokenizing async/await. As a consequence, it is now possible to have one-" +"line 'async def foo(): await ..' functions." +msgstr "" + +#: ../../../Misc/NEWS:3531 +msgid "" +"`Issue #24687 `__: Plug refleak on " +"SyntaxError in function parameters annotations." +msgstr "" + +#: ../../../Misc/NEWS:3534 +msgid "" +"`Issue #15944 `__: memoryview: Allow " +"arbitrary formats when casting to bytes. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:3540 +msgid "" +"`Issue #23441 `__: rcompleter now prints a " +"tab character instead of displaying possible completions for an empty word. " +"Initial patch by Martin Sekera." +msgstr "" + +#: ../../../Misc/NEWS:3543 +msgid "" +"`Issue #24683 `__: Fixed crashes in _json " +"functions called with arguments of inappropriate type." +msgstr "" + +#: ../../../Misc/NEWS:3546 +msgid "" +"`Issue #21697 `__: shutil.copytree() now " +"correctly handles symbolic links that point to directories. Patch by " +"Eduardo Seabra and Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:3549 +msgid "" +"`Issue #14373 `__: Fixed segmentation fault " +"when gc.collect() is called during constructing lru_cache (C implementation)." +msgstr "" + +#: ../../../Misc/NEWS:3552 +msgid "" +"`Issue #24695 `__: Fix a regression in " +"traceback.print_exception(). If exc_traceback is None we shouldn't print a " +"traceback header like described in the documentation." +msgstr "" + +#: ../../../Misc/NEWS:3556 +msgid "" +"`Issue #24620 `__: Random.setstate() now " +"validates the value of state last element." +msgstr "" + +#: ../../../Misc/NEWS:3558 +msgid "" +"`Issue #22485 `__: Fixed an issue that caused " +"`inspect.getsource` to return incorrect results on nested functions." +msgstr "" + +#: ../../../Misc/NEWS:3561 +msgid "" +"`Issue #22153 `__: Improve unittest docs. " +"Patch from Martin Panter and evilzero." +msgstr "" + +#: ../../../Misc/NEWS:3563 +msgid "" +"`Issue #24580 `__: Symbolic group references " +"to open group in re patterns now are explicitly forbidden as well as numeric " +"group references." +msgstr "" + +#: ../../../Misc/NEWS:3566 +msgid "" +"`Issue #24206 `__: Fixed __eq__ and __ne__ " +"methods of inspect classes." +msgstr "" + +#: ../../../Misc/NEWS:3568 +msgid "" +"`Issue #24631 `__: Fixed regression in the " +"timeit module with multiline setup." +msgstr "" + +#: ../../../Misc/NEWS:3570 +msgid "" +"`Issue #24608 `__: chunk.Chunk.read() now " +"always returns bytes, not str." +msgstr "" + +#: ../../../Misc/NEWS:3572 +msgid "" +"`Issue #18684 `__: Fixed reading out of the " +"buffer in the re module." +msgstr "" + +#: ../../../Misc/NEWS:3574 +msgid "" +"`Issue #24259 `__: tarfile now raises a " +"ReadError if an archive is truncated inside a data segment." +msgstr "" + +#: ../../../Misc/NEWS:3577 +msgid "" +"`Issue #15014 `__: SMTP.auth() and SMTP." +"login() now support RFC 4954's optional initial-response argument to the " +"SMTP AUTH command." +msgstr "" + +#: ../../../Misc/NEWS:3580 +msgid "" +"`Issue #6549 `__: Remove hyphen from ttk." +"Style().element options. Only return result from ttk.Style().configure if a " +"result was generated or a query submitted." +msgstr "" + +#: ../../../Misc/NEWS:3583 +msgid "" +"`Issue #24669 `__: Fix inspect.getsource() " +"for 'async def' functions. Patch by Kai Groner." +msgstr "" + +#: ../../../Misc/NEWS:3586 +msgid "" +"`Issue #24688 `__: ast.get_docstring() for " +"'async def' functions." +msgstr "" + +#: ../../../Misc/NEWS:3591 +msgid "" +"`Issue #24603 `__: Update Windows builds and " +"OS X 10.5 installer to use OpenSSL 1.0.2d." +msgstr "" + +#: ../../../Misc/NEWS:3595 +msgid "Python 3.5.0 beta 3" +msgstr "" + +#: ../../../Misc/NEWS:3597 +msgid "Release date: 2015-07-05" +msgstr "" + +#: ../../../Misc/NEWS:3602 +msgid "" +"`Issue #24467 `__: Fixed possible buffer over-" +"read in bytearray. The bytearray object now always allocates place for " +"trailing null byte and it's buffer now is always null-terminated." +msgstr "" + +#: ../../../Misc/NEWS:3606 +msgid "Upgrade to Unicode 8.0.0." +msgstr "" + +#: ../../../Misc/NEWS:3608 +msgid "" +"`Issue #24345 `__: Add Py_tp_finalize slot " +"for the stable ABI." +msgstr "" + +#: ../../../Misc/NEWS:3610 +msgid "" +"`Issue #24400 `__: Introduce a distinct type " +"for PEP 492 coroutines; add types.CoroutineType, inspect.getcoroutinestate, " +"inspect.getcoroutinelocals; coroutines no longer use CO_GENERATOR flag; sys." +"set_coroutine_wrapper works only for 'async def' coroutines; inspect." +"iscoroutine no longer uses collections.abc.Coroutine, it's intended to test " +"for pure 'async def' coroutines only; add new opcode: GET_YIELD_FROM_ITER; " +"fix generators wrapper used in types.coroutine to be instance of collections." +"abc.Generator; collections.abc.Awaitable and collections.abc.Coroutine can " +"no longer be used to detect generator-based coroutines--use inspect." +"isawaitable instead." +msgstr "" + +#: ../../../Misc/NEWS:3621 +msgid "" +"`Issue #24450 `__: Add gi_yieldfrom to " +"generators and cr_await to coroutines. Contributed by Benno Leslie and Yury " +"Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3624 +msgid "" +"`Issue #19235 `__: Add new RecursionError " +"exception. Patch by Georg Brandl." +msgstr "" + +#: ../../../Misc/NEWS:3629 +msgid "" +"`Issue #21750 `__: mock_open.read_data can " +"now be read from each instance, as it could in Python 3.3." +msgstr "" + +#: ../../../Misc/NEWS:3632 +msgid "" +"`Issue #24552 `__: Fix use after free in an " +"error case of the _pickle module." +msgstr "" + +#: ../../../Misc/NEWS:3634 +msgid "" +"`Issue #24514 `__: tarfile now tolerates " +"number fields consisting of only whitespace." +msgstr "" + +#: ../../../Misc/NEWS:3637 +msgid "" +"`Issue #19176 `__: Fixed doctype() related " +"bugs in C implementation of ElementTree. A deprecation warning no longer " +"issued by XMLParser subclass with default doctype() method. Direct call of " +"doctype() now issues a warning. Parser's doctype() now is not called if " +"target's doctype() is called. Based on patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:3643 +msgid "" +"`Issue #20387 `__: Restore semantic round-" +"trip correctness in tokenize/untokenize for tab-indented blocks." +msgstr "" + +#: ../../../Misc/NEWS:3646 +msgid "" +"`Issue #24456 `__: Fixed possible buffer over-" +"read in adpcm2lin() and lin2adpcm() functions of the audioop module." +msgstr "" + +#: ../../../Misc/NEWS:3649 +msgid "" +"`Issue #24336 `__: The contextmanager " +"decorator now works with functions with keyword arguments called \"func\" " +"and \"self\". Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:3652 +msgid "" +"`Issue #24522 `__: Fix possible integer " +"overflow in json accelerator module." +msgstr "" + +#: ../../../Misc/NEWS:3654 +msgid "" +"`Issue #24489 `__: ensure a previously set C " +"errno doesn't disturb cmath.polar()." +msgstr "" + +#: ../../../Misc/NEWS:3656 +msgid "" +"`Issue #24408 `__: Fixed AttributeError in " +"measure() and metrics() methods of tkinter.Font." +msgstr "" + +#: ../../../Misc/NEWS:3659 +msgid "" +"`Issue #14373 `__: C implementation of " +"functools.lru_cache() now can be used with methods." +msgstr "" + +#: ../../../Misc/NEWS:3662 +msgid "" +"`Issue #24347 `__: Set KeyError if " +"PyDict_GetItemWithError returns NULL." +msgstr "" + +#: ../../../Misc/NEWS:3664 +msgid "" +"`Issue #24348 `__: Drop superfluous incref/" +"decref." +msgstr "" + +#: ../../../Misc/NEWS:3666 +msgid "" +"`Issue #24359 `__: Check for changed " +"OrderedDict size during iteration." +msgstr "" + +#: ../../../Misc/NEWS:3668 +msgid "" +"`Issue #24368 `__: Support keyword arguments " +"in OrderedDict methods." +msgstr "" + +#: ../../../Misc/NEWS:3670 +msgid "" +"`Issue #24362 `__: Simplify the C OrderedDict " +"fast nodes resize logic." +msgstr "" + +#: ../../../Misc/NEWS:3672 +msgid "" +"`Issue #24377 `__: Fix a ref leak in " +"OrderedDict.__repr__." +msgstr "" + +#: ../../../Misc/NEWS:3674 +msgid "" +"`Issue #24369 `__: Defend against key-changes " +"during iteration." +msgstr "" + +#: ../../../Misc/NEWS:3679 +msgid "" +"`Issue #24373 `__: _testmultiphase and " +"xxlimited now use tp_traverse and tp_finalize to avoid reference leaks " +"encountered when combining tp_dealloc with PyType_FromSpec (see `issue " +"#16690 `__ for details)" +msgstr "" + +#: ../../../Misc/NEWS:3686 +msgid "" +"`Issue #24458 `__: Update documentation to " +"cover multi-phase initialization for extension modules (PEP 489). Patch by " +"Petr Viktorin." +msgstr "" + +#: ../../../Misc/NEWS:3689 +msgid "" +"`Issue #24351 `__: Clarify what is meant by " +"\"identifier\" in the context of string.Template instances." +msgstr "" + +#: ../../../Misc/NEWS:3695 +msgid "" +"`Issue #24432 `__: Update Windows builds and " +"OS X 10.5 installer to use OpenSSL 1.0.2c." +msgstr "" + +#: ../../../Misc/NEWS:3700 +msgid "Python 3.5.0 beta 2" +msgstr "" + +#: ../../../Misc/NEWS:3702 +msgid "Release date: 2015-05-31" +msgstr "" + +#: ../../../Misc/NEWS:3707 +msgid "" +"`Issue #24284 `__: The startswith and " +"endswith methods of the str class no longer return True when finding the " +"empty string and the indexes are completely out of range." +msgstr "" + +#: ../../../Misc/NEWS:3711 +msgid "" +"`Issue #24115 `__: Update uses of " +"PyObject_IsTrue(), PyObject_Not(), PyObject_IsInstance(), " +"PyObject_RichCompareBool() and _PyDict_Contains() to check for and handle " +"errors correctly." +msgstr "" + +#: ../../../Misc/NEWS:3715 +msgid "" +"`Issue #24328 `__: Fix importing one " +"character extension modules." +msgstr "" + +#: ../../../Misc/NEWS:3717 +msgid "" +"`Issue #11205 `__: In dictionary displays, " +"evaluate the key before the value." +msgstr "" + +#: ../../../Misc/NEWS:3719 +msgid "" +"`Issue #24285 `__: Fixed regression that " +"prevented importing extension modules from inside packages. Patch by Petr " +"Viktorin." +msgstr "" + +#: ../../../Misc/NEWS:3725 +msgid "" +"`Issue #23247 `__: Fix a crash in the " +"StreamWriter.reset() of CJK codecs." +msgstr "" + +#: ../../../Misc/NEWS:3727 +msgid "" +"`Issue #24270 `__: Add math.isclose() and " +"cmath.isclose() functions as per PEP 485. Contributed by Chris Barker and " +"Tal Einat." +msgstr "" + +#: ../../../Misc/NEWS:3730 +msgid "" +"`Issue #5633 `__: Fixed timeit when the " +"statement is a string and the setup is not." +msgstr "" + +#: ../../../Misc/NEWS:3732 +msgid "" +"`Issue #24326 `__: Fixed audioop.ratecv() " +"with non-default weightB argument. Original patch by David Moore." +msgstr "" + +#: ../../../Misc/NEWS:3735 +msgid "" +"`Issue #16991 `__: Add a C implementation of " +"OrderedDict." +msgstr "" + +#: ../../../Misc/NEWS:3737 +msgid "" +"`Issue #23934 `__: Fix inspect.signature to " +"fail correctly for builtin types lacking signature information. Initial " +"patch by James Powell." +msgstr "" + +#: ../../../Misc/NEWS:3742 +msgid "Python 3.5.0 beta 1" +msgstr "" + +#: ../../../Misc/NEWS:3744 +msgid "Release date: 2015-05-24" +msgstr "" + +#: ../../../Misc/NEWS:3749 +msgid "" +"`Issue #24276 `__: Fixed optimization of " +"property descriptor getter." +msgstr "" + +#: ../../../Misc/NEWS:3751 +msgid "" +"`Issue #24268 `__: PEP 489: Multi-phase " +"extension module initialization. Patch by Petr Viktorin." +msgstr "" + +#: ../../../Misc/NEWS:3754 +msgid "" +"`Issue #23359 `__: Optimize set object " +"internals by specializing the hash table search into a lookup function and " +"an insert function." +msgstr "" + +#: ../../../Misc/NEWS:3757 +msgid "" +"`Issue #23955 `__: Add pyvenv.cfg option to " +"suppress registry/environment lookup for generating sys.path on Windows." +msgstr "" + +#: ../../../Misc/NEWS:3760 +msgid "" +"`Issue #24257 `__: Fixed system error in the " +"comparison of faked types.SimpleNamespace." +msgstr "" + +#: ../../../Misc/NEWS:3763 +msgid "" +"`Issue #22939 `__: Fixed integer overflow in " +"iterator object. Patch by Clement Rouault." +msgstr "" + +#: ../../../Misc/NEWS:3766 +msgid "" +"`Issue #23985 `__: Fix a possible buffer " +"overrun when deleting a slice from the front of a bytearray and then " +"appending some other bytes data." +msgstr "" + +#: ../../../Misc/NEWS:3769 +msgid "" +"`Issue #24102 `__: Fixed exception type " +"checking in standard error handlers." +msgstr "" + +#: ../../../Misc/NEWS:3771 +msgid "" +"`Issue #15027 `__: The UTF-32 encoder is now " +"3x to 7x faster." +msgstr "" + +#: ../../../Misc/NEWS:3773 +msgid "" +"`Issue #23290 `__: Optimize set_merge() for " +"cases where the target is empty. (Contributed by Serhiy Storchaka.)" +msgstr "" + +#: ../../../Misc/NEWS:3776 +msgid "" +"`Issue #2292 `__: PEP 448: Additional " +"Unpacking Generalizations." +msgstr "" + +#: ../../../Misc/NEWS:3778 +msgid "" +"`Issue #24096 `__: Make warnings." +"warn_explicit more robust against mutation of the warnings.filters list." +msgstr "" + +#: ../../../Misc/NEWS:3781 +msgid "" +"`Issue #23996 `__: Avoid a crash when a " +"delegated generator raises an unnormalized StopIteration exception. Patch " +"by Stefan Behnel." +msgstr "" + +#: ../../../Misc/NEWS:3784 +msgid "" +"`Issue #23910 `__: Optimize property() getter " +"calls. Patch by Joe Jevnik." +msgstr "" + +#: ../../../Misc/NEWS:3786 +msgid "" +"`Issue #23911 `__: Move path-based importlib " +"bootstrap code to a separate frozen module." +msgstr "" + +#: ../../../Misc/NEWS:3789 +msgid "" +"`Issue #24192 `__: Fix namespace package " +"imports." +msgstr "" + +#: ../../../Misc/NEWS:3791 +msgid "" +"`Issue #24022 `__: Fix tokenizer crash when " +"processing undecodable source code." +msgstr "" + +#: ../../../Misc/NEWS:3793 +msgid "" +"`Issue #9951 `__: Added a hex() method to " +"bytes, bytearray, and memoryview." +msgstr "" + +#: ../../../Misc/NEWS:3795 +msgid "" +"`Issue #22906 `__: PEP 479: Change " +"StopIteration handling inside generators." +msgstr "" + +#: ../../../Misc/NEWS:3797 +msgid "" +"`Issue #24017 `__: PEP 492: Coroutines with " +"async and await syntax." +msgstr "" + +#: ../../../Misc/NEWS:3802 +msgid "" +"`Issue #14373 `__: Added C implementation of " +"functools.lru_cache(). Based on patches by Matt Joiner and Alexey Kachayev." +msgstr "" + +#: ../../../Misc/NEWS:3805 +msgid "" +"`Issue #24230 `__: The tempfile module now " +"accepts bytes for prefix, suffix and dir parameters and returns bytes in " +"such situations (matching the os module APIs)." +msgstr "" + +#: ../../../Misc/NEWS:3808 +msgid "" +"`Issue #22189 `__: collections.UserString now " +"supports __getnewargs__(), __rmod__(), casefold(), format_map(), " +"isprintable(), and maketrans(). Patch by Joe Jevnik." +msgstr "" + +#: ../../../Misc/NEWS:3812 +msgid "" +"`Issue #24244 `__: Prevents termination when " +"an invalid format string is encountered on Windows in strftime." +msgstr "" + +#: ../../../Misc/NEWS:3815 +msgid "" +"`Issue #23973 `__: PEP 484: Add the typing " +"module." +msgstr "" + +#: ../../../Misc/NEWS:3817 +msgid "" +"`Issue #23086 `__: The collections.abc." +"Sequence() abstract base class added *start* and *stop* parameters to the " +"index() mixin. Patch by Devin Jeanpierre." +msgstr "" + +#: ../../../Misc/NEWS:3821 +msgid "" +"`Issue #20035 `__: Replaced the ``tkinter." +"_fix`` module used for setting up the Tcl/Tk environment on Windows with a " +"private function in the ``_tkinter`` module that makes no permanent changes " +"to the environment." +msgstr "" + +#: ../../../Misc/NEWS:3825 +msgid "" +"`Issue #24257 `__: Fixed segmentation fault " +"in sqlite3.Row constructor with faked cursor type." +msgstr "" + +#: ../../../Misc/NEWS:3828 +msgid "" +"`Issue #15836 `__: assertRaises(), " +"assertRaisesRegex(), assertWarns() and assertWarnsRegex() assertments now " +"check the type of the first argument to prevent possible user error. Based " +"on patch by Daniel Wagner-Hall." +msgstr "" + +#: ../../../Misc/NEWS:3832 +msgid "" +"`Issue #9858 `__: Add missing method stubs to " +"_io.RawIOBase. Patch by Laura Rupprecht." +msgstr "" + +#: ../../../Misc/NEWS:3835 +msgid "" +"`Issue #22955 `__: attrgetter, itemgetter and " +"methodcaller objects in the operator module now support pickling. Added " +"readable and evaluable repr for these objects. Based on patch by Josh " +"Rosenberg." +msgstr "" + +#: ../../../Misc/NEWS:3839 +msgid "" +"`Issue #22107 `__: tempfile.gettempdir() and " +"tempfile.mkdtemp() now try again when a directory with the chosen name " +"already exists on Windows as well as on Unix. tempfile.mkstemp() now fails " +"early if parent directory is not valid (not exists or is a file) on Windows." +msgstr "" + +#: ../../../Misc/NEWS:3844 +msgid "" +"`Issue #23780 `__: Improved error message in " +"os.path.join() with single argument." +msgstr "" + +#: ../../../Misc/NEWS:3846 +msgid "" +"`Issue #6598 `__: Increased time precision and " +"random number range in email.utils.make_msgid() to strengthen the uniqueness " +"of the message ID." +msgstr "" + +#: ../../../Misc/NEWS:3849 +msgid "" +"`Issue #24091 `__: Fixed various crashes in " +"corner cases in C implementation of ElementTree." +msgstr "" + +#: ../../../Misc/NEWS:3852 +msgid "" +"`Issue #21931 `__: msilib.FCICreate() now " +"raises TypeError in the case of a bad argument instead of a ValueError with " +"a bogus FCI error number. Patch by Jeffrey Armstrong." +msgstr "" + +#: ../../../Misc/NEWS:3856 +msgid "" +"`Issue #13866 `__: *quote_via* argument added " +"to urllib.parse.urlencode." +msgstr "" + +#: ../../../Misc/NEWS:3858 +msgid "" +"`Issue #20098 `__: New mangle_from policy " +"option for email, default True for compat32, but False for all other " +"policies." +msgstr "" + +#: ../../../Misc/NEWS:3861 +msgid "" +"`Issue #24211 `__: The email library now " +"supports RFC 6532: it can generate headers using utf-8 instead of encoded " +"words." +msgstr "" + +#: ../../../Misc/NEWS:3864 +msgid "" +"`Issue #16314 `__: Added support for the LZMA " +"compression in distutils." +msgstr "" + +#: ../../../Misc/NEWS:3866 +msgid "" +"`Issue #21804 `__: poplib now supports RFC " +"6856 (UTF8)." +msgstr "" + +#: ../../../Misc/NEWS:3868 +msgid "" +"`Issue #18682 `__: Optimized pprint functions " +"for builtin scalar types." +msgstr "" + +#: ../../../Misc/NEWS:3870 +msgid "" +"`Issue #22027 `__: smtplib now supports RFC " +"6531 (SMTPUTF8)." +msgstr "" + +#: ../../../Misc/NEWS:3872 +msgid "" +"`Issue #23488 `__: Random generator objects " +"now consume 2x less memory on 64-bit." +msgstr "" + +#: ../../../Misc/NEWS:3874 +msgid "" +"`Issue #1322 `__: platform.dist() and platform." +"linux_distribution() functions are now deprecated. Initial patch by " +"Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:3877 +msgid "" +"`Issue #22486 `__: Added the math.gcd() " +"function. The fractions.gcd() function now is deprecated. Based on patch " +"by Mark Dickinson." +msgstr "" + +#: ../../../Misc/NEWS:3880 +msgid "" +"`Issue #24064 `__: Property() docstrings are " +"now writeable. (Patch by Berker Peksag.)" +msgstr "" + +#: ../../../Misc/NEWS:3883 +msgid "" +"`Issue #22681 `__: Added support for the " +"koi8_t encoding." +msgstr "" + +#: ../../../Misc/NEWS:3885 +msgid "" +"`Issue #22682 `__: Added support for the " +"kz1048 encoding." +msgstr "" + +#: ../../../Misc/NEWS:3887 +msgid "" +"`Issue #23796 `__: peek and read1 methods of " +"BufferedReader now raise ValueError if they called on a closed object. Patch " +"by John Hergenroeder." +msgstr "" + +#: ../../../Misc/NEWS:3890 +msgid "" +"`Issue #21795 `__: smtpd now supports the " +"8BITMIME extension whenever the new *decode_data* constructor argument is " +"set to False." +msgstr "" + +#: ../../../Misc/NEWS:3893 +msgid "" +"`Issue #24155 `__: optimize heapq.heapify() " +"for better cache performance when heapifying large lists." +msgstr "" + +#: ../../../Misc/NEWS:3896 +msgid "" +"`Issue #21800 `__: imaplib now supports RFC " +"5161 (enable), RFC 6855 (utf8/internationalized email) and automatically " +"encodes non-ASCII usernames and passwords to UTF8." +msgstr "" + +#: ../../../Misc/NEWS:3900 +msgid "" +"`Issue #20274 `__: When calling a _sqlite." +"Connection, it now complains if passed any keyword arguments. Previously it " +"silently ignored them." +msgstr "" + +#: ../../../Misc/NEWS:3903 +msgid "" +"`Issue #20274 `__: Remove ignored and " +"erroneous \"kwargs\" parameters from three METH_VARARGS methods on _sqlite." +"Connection." +msgstr "" + +#: ../../../Misc/NEWS:3906 +msgid "" +"`Issue #24134 `__: assertRaises(), " +"assertRaisesRegex(), assertWarns() and assertWarnsRegex() checks now emits a " +"deprecation warning when callable is None or keyword arguments except msg is " +"passed in the context manager mode." +msgstr "" + +#: ../../../Misc/NEWS:3910 +msgid "" +"`Issue #24018 `__: Add a collections.abc." +"Generator abstract base class. Contributed by Stefan Behnel." +msgstr "" + +#: ../../../Misc/NEWS:3913 +msgid "" +"`Issue #23880 `__: Tkinter's getint() and " +"getdouble() now support Tcl_Obj. Tkinter's getdouble() now supports any " +"numbers (in particular int)." +msgstr "" + +#: ../../../Misc/NEWS:3916 +msgid "" +"`Issue #22619 `__: Added negative limit " +"support in the traceback module. Based on patch by Dmitry Kazakov." +msgstr "" + +#: ../../../Misc/NEWS:3919 +msgid "" +"`Issue #24094 `__: Fix possible crash in json." +"encode with poorly behaved dict subclasses." +msgstr "" + +#: ../../../Misc/NEWS:3922 +msgid "" +"`Issue #9246 `__: On POSIX, os.getcwd() now " +"supports paths longer than 1025 bytes. Patch written by William Orr." +msgstr "" + +#: ../../../Misc/NEWS:3925 +msgid "" +"`Issue #17445 `__: add difflib.diff_bytes() " +"to support comparison of byte strings (fixes a regression from Python 2)." +msgstr "" + +#: ../../../Misc/NEWS:3928 +msgid "" +"`Issue #23917 `__: Fall back to sequential " +"compilation when ProcessPoolExecutor doesn't exist. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:3931 +msgid "" +"`Issue #23008 `__: Fixed resolving attributes " +"with boolean value is False in pydoc." +msgstr "" + +#: ../../../Misc/NEWS:3933 +msgid "" +"Fix asyncio issue 235: LifoQueue and PriorityQueue's put didn't increment " +"unfinished tasks (this bug was introduced when JoinableQueue was merged with " +"Queue)." +msgstr "" + +#: ../../../Misc/NEWS:3937 +msgid "" +"`Issue #23908 `__: os functions now reject " +"paths with embedded null character on Windows instead of silently truncating " +"them." +msgstr "" + +#: ../../../Misc/NEWS:3940 +msgid "" +"`Issue #23728 `__: binascii.crc_hqx() could " +"return an integer outside of the range 0-0xffff for empty data." +msgstr "" + +#: ../../../Misc/NEWS:3943 +msgid "" +"`Issue #23887 `__: urllib.error.HTTPError now " +"has a proper repr() representation. Patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:3946 +msgid "" +"asyncio: New event loop APIs: set_task_factory() and get_task_factory()." +msgstr "" + +#: ../../../Misc/NEWS:3948 +msgid "asyncio: async() function is deprecated in favour of ensure_future()." +msgstr "" + +#: ../../../Misc/NEWS:3950 +msgid "" +"`Issue #24178 `__: asyncio.Lock, Condition, " +"Semaphore, and BoundedSemaphore support new 'async with' syntax. " +"Contributed by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3953 +msgid "" +"`Issue #24179 `__: Support 'async for' for " +"asyncio.StreamReader. Contributed by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3956 +msgid "" +"`Issue #24184 `__: Add AsyncIterator and " +"AsyncIterable ABCs to collections.abc. Contributed by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3959 +msgid "" +"`Issue #22547 `__: Implement informative " +"__repr__ for inspect.BoundArguments. Contributed by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3962 +msgid "" +"`Issue #24190 `__: Implement inspect." +"BoundArgument.apply_defaults() method. Contributed by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3965 +msgid "" +"`Issue #20691 `__: Add 'follow_wrapped' " +"argument to inspect.Signature.from_callable() and inspect.signature(). " +"Contributed by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:3969 +msgid "" +"`Issue #24248 `__: Deprecate inspect." +"Signature.from_function() and inspect.Signature.from_builtin()." +msgstr "" + +#: ../../../Misc/NEWS:3972 +msgid "" +"`Issue #23898 `__: Fix inspect." +"classify_class_attrs() to support attributes with overloaded __eq__ and " +"__bool__. Patch by Mike Bayer." +msgstr "" + +#: ../../../Misc/NEWS:3975 +msgid "" +"`Issue #24298 `__: Fix inspect.signature() to " +"correctly unwrap wrappers around bound methods." +msgstr "" + +#: ../../../Misc/NEWS:3981 +msgid "" +"`Issue #23184 `__: remove unused names and " +"imports in idlelib. Initial patch by Al Sweigart." +msgstr "" + +#: ../../../Misc/NEWS:3987 +msgid "" +"`Issue #21520 `__: test_zipfile no longer " +"fails if the word 'bad' appears anywhere in the name of the current " +"directory." +msgstr "" + +#: ../../../Misc/NEWS:3990 +msgid "" +"`Issue #9517 `__: Move script_helper into the " +"support package. Patch by Christie Wilson." +msgstr "" + +#: ../../../Misc/NEWS:3996 +msgid "" +"`Issue #22155 `__: Add File Handlers " +"subsection with createfilehandler to tkinter doc. Remove obsolete example " +"from FAQ. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:3999 +msgid "" +"`Issue #24029 `__: Document the name binding " +"behavior for submodule imports." +msgstr "" + +#: ../../../Misc/NEWS:4001 +msgid "" +"`Issue #24077 `__: Fix typo in man page for -" +"I command option: -s, not -S" +msgstr "" + +#: ../../../Misc/NEWS:4006 +msgid "" +"`Issue #24000 `__: Improved Argument Clinic's " +"mapping of converters to legacy \"format units\". Updated the documentation " +"to match." +msgstr "" + +#: ../../../Misc/NEWS:4009 +msgid "" +"`Issue #24001 `__: Argument Clinic converters " +"now use accept={type} instead of types={'type'} to specify the types the " +"converter accepts." +msgstr "" + +#: ../../../Misc/NEWS:4012 +msgid "" +"`Issue #23330 `__: h2py now supports " +"arbitrary filenames in #include." +msgstr "" + +#: ../../../Misc/NEWS:4014 +msgid "" +"`Issue #24031 `__: make patchcheck now " +"supports git checkouts, too." +msgstr "" + +#: ../../../Misc/NEWS:4018 +msgid "Python 3.5.0 alpha 4" +msgstr "" + +#: ../../../Misc/NEWS:4020 +msgid "Release date: 2015-04-19" +msgstr "" + +#: ../../../Misc/NEWS:4025 +msgid "" +"`Issue #22980 `__: Under Linux, GNU/KFreeBSD " +"and the Hurd, C extensions now include the architecture triplet in the " +"extension name, to make it easy to test builds for different ABIs in the " +"same working tree. Under OS X, the extension name now includes PEP 3149-" +"style information." +msgstr "" + +#: ../../../Misc/NEWS:4030 +msgid "" +"`Issue #22631 `__: Added Linux-specific " +"socket constant CAN_RAW_FD_FRAMES. Patch courtesy of Joe Jevnik." +msgstr "" + +#: ../../../Misc/NEWS:4033 +msgid "" +"`Issue #23731 `__: Implement PEP 488: removal " +"of .pyo files." +msgstr "" + +#: ../../../Misc/NEWS:4035 +msgid "" +"`Issue #23726 `__: Don't enable GC for user " +"subclasses of non-GC types that don't add any new fields. Patch by Eugene " +"Toder." +msgstr "" + +#: ../../../Misc/NEWS:4038 +msgid "" +"`Issue #23309 `__: Avoid a deadlock at " +"shutdown if a daemon thread is aborted while it is holding a lock to a " +"buffered I/O object, and the main thread tries to use the same I/O object " +"(typically stdout or stderr). A fatal error is emitted instead." +msgstr "" + +#: ../../../Misc/NEWS:4043 +msgid "" +"`Issue #22977 `__: Fixed formatting Windows " +"error messages on Wine. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4046 +msgid "" +"`Issue #23466 `__: %c, %o, %x, and %X in " +"bytes formatting now raise TypeError on non-integer input." +msgstr "" + +#: ../../../Misc/NEWS:4049 +msgid "" +"`Issue #24044 `__: Fix possible null pointer " +"dereference in list.sort in out of memory conditions." +msgstr "" + +#: ../../../Misc/NEWS:4052 +msgid "" +"`Issue #21354 `__: PyCFunction_New function " +"is exposed by python DLL again." +msgstr "" + +#: ../../../Misc/NEWS:4057 +msgid "" +"`Issue #23840 `__: tokenize.open() now closes " +"the temporary binary file on error to fix a resource warning." +msgstr "" + +#: ../../../Misc/NEWS:4060 +msgid "" +"`Issue #16914 `__: new debuglevel 2 in " +"smtplib adds timestamps to debug output." +msgstr "" + +#: ../../../Misc/NEWS:4062 +msgid "" +"`Issue #7159 `__: urllib.request now supports " +"sending auth credentials automatically after the first 401. This " +"enhancement is a superset of the enhancement from `issue #19494 `__ and supersedes that change." +msgstr "" + +#: ../../../Misc/NEWS:4066 +msgid "" +"`Issue #23703 `__: Fix a regression in " +"urljoin() introduced in 901e4e52b20a. Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4069 +msgid "" +"`Issue #4254 `__: Adds _curses." +"update_lines_cols(). Patch by Arnon Yaari" +msgstr "" + +#: ../../../Misc/NEWS:4071 +msgid "" +"`Issue #19933 `__: Provide default argument " +"for ndigits in round. Patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:4074 +msgid "" +"`Issue #23193 `__: Add a numeric_owner " +"parameter to tarfile.TarFile.extract and tarfile.TarFile.extractall. Patch " +"by Michael Vogt and Eric Smith." +msgstr "" + +#: ../../../Misc/NEWS:4078 +msgid "" +"`Issue #23342 `__: Add a subprocess.run() " +"function than returns a CalledProcess instance for a more consistent API " +"than the existing call* functions." +msgstr "" + +#: ../../../Misc/NEWS:4081 +msgid "" +"`Issue #21217 `__: inspect.getsourcelines() " +"now tries to compute the start and end lines from the code object, fixing an " +"issue when a lambda function is used as decorator argument. Patch by Thomas " +"Ballinger and Allison Kaptur." +msgstr "" + +#: ../../../Misc/NEWS:4085 +msgid "" +"`Issue #24521 `__: Fix possible integer " +"overflows in the pickle module." +msgstr "" + +#: ../../../Misc/NEWS:4087 +msgid "" +"`Issue #22931 `__: Allow '[' and ']' in " +"cookie values." +msgstr "" + +#: ../../../Misc/NEWS:4089 +msgid "The keywords attribute of functools.partial is now always a dictionary." +msgstr "" + +#: ../../../Misc/NEWS:4091 +msgid "" +"`Issue #23811 `__: Add missing newline to the " +"PyCompileError error message. Patch by Alex Shkop." +msgstr "" + +#: ../../../Misc/NEWS:4094 +msgid "" +"`Issue #21116 `__: Avoid blowing memory when " +"allocating a multiprocessing shared array that's larger than 50% of the " +"available RAM. Patch by Médéric Boquien." +msgstr "" + +#: ../../../Misc/NEWS:4097 +msgid "" +"`Issue #22982 `__: Improve BOM handling when " +"seeking to multiple positions of a writable text file." +msgstr "" + +#: ../../../Misc/NEWS:4100 +msgid "" +"`Issue #23464 `__: Removed deprecated asyncio " +"JoinableQueue." +msgstr "" + +#: ../../../Misc/NEWS:4102 +msgid "" +"`Issue #23529 `__: Limit the size of " +"decompressed data when reading from GzipFile, BZ2File or LZMAFile. This " +"defeats denial of service attacks using compressed bombs (i.e. compressed " +"payloads which decompress to a huge size). Patch by Martin Panter and " +"Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:4107 +msgid "" +"`Issue #21859 `__: Added Python " +"implementation of io.FileIO." +msgstr "" + +#: ../../../Misc/NEWS:4109 +msgid "" +"`Issue #23865 `__: close() methods in " +"multiple modules now are idempotent and more robust at shutdown. If they " +"need to release multiple resources, all are released even if errors occur." +msgstr "" + +#: ../../../Misc/NEWS:4113 +msgid "" +"`Issue #23400 `__: Raise same exception on " +"both Python 2 and 3 if sem_open is not available. Patch by Davin Potts." +msgstr "" + +#: ../../../Misc/NEWS:4116 +msgid "" +"`Issue #10838 `__: The subprocess now module " +"includes SubprocessError and TimeoutError in its list of exported names for " +"the users wild enough to use ``from subprocess import *``." +msgstr "" + +#: ../../../Misc/NEWS:4120 +msgid "" +"`Issue #23411 `__: Added DefragResult, " +"ParseResult, SplitResult, DefragResultBytes, ParseResultBytes, and " +"SplitResultBytes to urllib.parse.__all__. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4124 +msgid "" +"`Issue #23881 `__: urllib.request.ftpwrapper " +"constructor now closes the socket if the FTP connection failed to fix a " +"ResourceWarning." +msgstr "" + +#: ../../../Misc/NEWS:4127 +msgid "" +"`Issue #23853 `__: :meth:`socket.socket." +"sendall` does no more reset the socket timeout each time data is sent " +"successfully. The socket timeout is now the maximum total duration to send " +"all data." +msgstr "" + +#: ../../../Misc/NEWS:4131 +msgid "" +"`Issue #22721 `__: An order of multiline " +"pprint output of set or dict containing orderable and non-orderable elements " +"no longer depends on iteration order of set or dict." +msgstr "" + +#: ../../../Misc/NEWS:4135 +msgid "" +"`Issue #15133 `__: _tkinter.tkapp." +"getboolean() now supports Tcl_Obj and always returns bool. tkinter." +"BooleanVar now validates input values (accepted bool, int, str, and " +"Tcl_Obj). tkinter.BooleanVar.get() now always returns bool." +msgstr "" + +#: ../../../Misc/NEWS:4139 +msgid "" +"`Issue #10590 `__: xml.sax.parseString() now " +"supports string argument." +msgstr "" + +#: ../../../Misc/NEWS:4141 +msgid "" +"`Issue #23338 `__: Fixed formatting ctypes " +"error messages on Cygwin. Patch by Makoto Kato." +msgstr "" + +#: ../../../Misc/NEWS:4144 +msgid "" +"`Issue #15582 `__: inspect.getdoc() now " +"follows inheritance chains." +msgstr "" + +#: ../../../Misc/NEWS:4146 +msgid "" +"`Issue #2175 `__: SAX parsers now support a " +"character stream of InputSource object." +msgstr "" + +#: ../../../Misc/NEWS:4148 +msgid "" +"`Issue #16840 `__: Tkinter now supports 64-" +"bit integers added in Tcl 8.4 and arbitrary precision integers added in Tcl " +"8.5." +msgstr "" + +#: ../../../Misc/NEWS:4151 +msgid "" +"`Issue #23834 `__: Fix socket.sendto(), use " +"the C Py_ssize_t type to store the result of sendto() instead of the C int " +"type." +msgstr "" + +#: ../../../Misc/NEWS:4154 +msgid "" +"`Issue #23618 `__: :meth:`socket.socket." +"connect` now waits until the connection completes instead of raising :exc:" +"`InterruptedError` if the connection is interrupted by signals, signal " +"handlers don't raise an exception and the socket is blocking or has a " +"timeout. :meth:`socket.socket.connect` still raise :exc:`InterruptedError` " +"for non-blocking sockets." +msgstr "" + +#: ../../../Misc/NEWS:4160 +msgid "" +"`Issue #21526 `__: Tkinter now supports new " +"boolean type in Tcl 8.5." +msgstr "" + +#: ../../../Misc/NEWS:4162 +msgid "" +"`Issue #23836 `__: Fix the faulthandler " +"module to handle reentrant calls to its signal handlers." +msgstr "" + +#: ../../../Misc/NEWS:4165 +msgid "" +"`Issue #23838 `__: linecache now clears the " +"cache and returns an empty result on MemoryError." +msgstr "" + +#: ../../../Misc/NEWS:4168 +msgid "" +"`Issue #10395 `__: Added os.path." +"commonpath(). Implemented in posixpath and ntpath. Based on patch by Rafik " +"Draoui." +msgstr "" + +#: ../../../Misc/NEWS:4171 +msgid "" +"`Issue #23611 `__: Serializing more " +"\"lookupable\" objects (such as unbound methods or nested classes) now are " +"supported with pickle protocols < 4." +msgstr "" + +#: ../../../Misc/NEWS:4174 +msgid "" +"`Issue #13583 `__: sqlite3.Row now supports " +"slice indexing." +msgstr "" + +#: ../../../Misc/NEWS:4176 +msgid "" +"`Issue #18473 `__: Fixed 2to3 and 3to2 " +"compatible pickle mappings. Fixed ambigious reverse mappings. Added many " +"new mappings. Import mapping is no longer applied to modules already mapped " +"with full name mapping." +msgstr "" + +#: ../../../Misc/NEWS:4180 +msgid "" +"`Issue #23485 `__: select.select() is now " +"retried automatically with the recomputed timeout when interrupted by a " +"signal, except if the signal handler raises an exception. This change is " +"part of the PEP 475." +msgstr "" + +#: ../../../Misc/NEWS:4184 +msgid "" +"`Issue #23752 `__: When built from an " +"existing file descriptor, io.FileIO() now only calls fstat() once. Before " +"fstat() was called twice, which was not necessary." +msgstr "" + +#: ../../../Misc/NEWS:4188 +msgid "" +"`Issue #23704 `__: collections.deque() " +"objects now support __add__, __mul__, and __imul__()." +msgstr "" + +#: ../../../Misc/NEWS:4191 +msgid "" +"`Issue #23171 `__: csv.Writer.writerow() now " +"supports arbitrary iterables." +msgstr "" + +#: ../../../Misc/NEWS:4193 +msgid "" +"`Issue #23745 `__: The new email header " +"parser now handles duplicate MIME parameter names without error, similar to " +"how get_param behaves." +msgstr "" + +#: ../../../Misc/NEWS:4196 +msgid "" +"`Issue #22117 `__: Fix os.utime(), it now " +"rounds the timestamp towards minus infinity (-inf) instead of rounding " +"towards zero." +msgstr "" + +#: ../../../Misc/NEWS:4199 +msgid "" +"`Issue #23310 `__: Fix MagicMock's " +"initializer to work with __methods__, just like configure_mock(). Patch by " +"Kasia Jachim." +msgstr "" + +#: ../../../Misc/NEWS:4205 +msgid "" +"`Issue #23817 `__: FreeBSD now uses \"1.0\" " +"in the SOVERSION as other operating systems, instead of just \"1\"." +msgstr "" + +#: ../../../Misc/NEWS:4208 +msgid "" +"`Issue #23501 `__: Argument Clinic now " +"generates code into separate files by default." +msgstr "" + +#: ../../../Misc/NEWS:4213 +msgid "" +"`Issue #23799 `__: Added test.support." +"start_threads() for running and cleaning up multiple threads." +msgstr "" + +#: ../../../Misc/NEWS:4216 +msgid "" +"`Issue #22390 `__: test.regrtest now emits a " +"warning if temporary files or directories are left after running a test." +msgstr "" + +#: ../../../Misc/NEWS:4222 +msgid "" +"`Issue #18128 `__: pygettext now uses " +"standard +NNNN format in the POT-Creation-Date header." +msgstr "" + +#: ../../../Misc/NEWS:4225 +msgid "" +"`Issue #23935 `__: Argument Clinic's " +"understanding of format units accepting bytes, bytearrays, and buffers is " +"now consistent with both the documentation and the implementation." +msgstr "" + +#: ../../../Misc/NEWS:4229 +msgid "" +"`Issue #23944 `__: Argument Clinic now wraps " +"long impl prototypes at column 78." +msgstr "" + +#: ../../../Misc/NEWS:4231 +msgid "" +"`Issue #20586 `__: Argument Clinic now " +"ensures that functions without docstrings have signatures." +msgstr "" + +#: ../../../Misc/NEWS:4234 +msgid "" +"`Issue #23492 `__: Argument Clinic now " +"generates argument parsing code with PyArg_Parse instead of PyArg_ParseTuple " +"if possible." +msgstr "" + +#: ../../../Misc/NEWS:4237 +msgid "" +"`Issue #23500 `__: Argument Clinic is now " +"smarter about generating the \"#ifndef\" (empty) definition of the methoddef " +"macro: it's only generated once, even if Argument Clinic processes the same " +"symbol multiple times, and it's emitted at the end of all processing rather " +"than immediately after the first use." +msgstr "" + +#: ../../../Misc/NEWS:4245 +msgid "" +"`Issue #23998 `__: PyImport_ReInitLock() now " +"checks for lock allocation error" +msgstr "" + +#: ../../../Misc/NEWS:4249 +msgid "Python 3.5.0 alpha 3" +msgstr "" + +#: ../../../Misc/NEWS:4251 +msgid "Release date: 2015-03-28" +msgstr "" + +#: ../../../Misc/NEWS:4256 +msgid "" +"`Issue #23573 `__: Increased performance of " +"string search operations (str.find, str.index, str.count, the in operator, " +"str.split, str.partition) with arguments of different kinds (UCS1, UCS2, " +"UCS4)." +msgstr "" + +#: ../../../Misc/NEWS:4260 +msgid "" +"`Issue #23753 `__: Python doesn't support " +"anymore platforms without stat() or fstat(), these functions are always " +"required." +msgstr "" + +#: ../../../Misc/NEWS:4263 +msgid "" +"`Issue #23681 `__: The -b option now affects " +"comparisons of bytes with int." +msgstr "" + +#: ../../../Misc/NEWS:4265 +msgid "" +"`Issue #23632 `__: Memoryviews now allow " +"tuple indexing (including for multi-dimensional memoryviews)." +msgstr "" + +#: ../../../Misc/NEWS:4268 +msgid "" +"`Issue #23192 `__: Fixed generator lambdas. " +"Patch by Bruno Cauet." +msgstr "" + +#: ../../../Misc/NEWS:4270 +msgid "" +"`Issue #23629 `__: Fix the default __sizeof__ " +"implementation for variable-sized objects." +msgstr "" + +#: ../../../Misc/NEWS:4276 +msgid "" +"`Issue #14260 `__: The groupindex attribute " +"of regular expression pattern object now is non-modifiable mapping." +msgstr "" + +#: ../../../Misc/NEWS:4279 +msgid "" +"`Issue #23792 `__: Ignore KeyboardInterrupt " +"when the pydoc pager is active. This mimics the behavior of the standard " +"unix pagers, and prevents pipepager from shutting down while the pager " +"itself is still running." +msgstr "" + +#: ../../../Misc/NEWS:4283 +msgid "" +"`Issue #23775 `__: pprint() of OrderedDict " +"now outputs the same representation as repr()." +msgstr "" + +#: ../../../Misc/NEWS:4286 +msgid "" +"`Issue #23765 `__: Removed IsBadStringPtr " +"calls in ctypes" +msgstr "" + +#: ../../../Misc/NEWS:4288 +msgid "" +"`Issue #22364 `__: Improved some re error " +"messages using regex for hints." +msgstr "" + +#: ../../../Misc/NEWS:4290 +msgid "" +"`Issue #23742 `__: ntpath.expandvars() no " +"longer loses unbalanced single quotes." +msgstr "" + +#: ../../../Misc/NEWS:4292 +msgid "" +"`Issue #21717 `__: The zipfile.ZipFile.open " +"function now supports 'x' (exclusive creation) mode." +msgstr "" + +#: ../../../Misc/NEWS:4295 +msgid "" +"`Issue #21802 `__: The reader in " +"BufferedRWPair now is closed even when closing writer failed in " +"BufferedRWPair.close()." +msgstr "" + +#: ../../../Misc/NEWS:4298 +msgid "" +"`Issue #23622 `__: Unknown escapes in regular " +"expressions that consist of ``'\\'`` and an ASCII letter now raise a " +"deprecation warning and will be forbidden in Python 3.6." +msgstr "" + +#: ../../../Misc/NEWS:4302 +msgid "" +"`Issue #23671 `__: string.Template now allows " +"specifying the \"self\" parameter as a keyword argument. string.Formatter " +"now allows specifying the \"self\" and the \"format_string\" parameters as " +"keyword arguments." +msgstr "" + +#: ../../../Misc/NEWS:4306 +msgid "" +"`Issue #23502 `__: The pprint module now " +"supports mapping proxies." +msgstr "" + +#: ../../../Misc/NEWS:4308 +msgid "" +"`Issue #17530 `__: pprint now wraps long " +"bytes objects and bytearrays." +msgstr "" + +#: ../../../Misc/NEWS:4310 +msgid "" +"`Issue #22687 `__: Fixed some corner cases in " +"breaking words in tetxtwrap. Got rid of quadratic complexity in breaking " +"long words." +msgstr "" + +#: ../../../Misc/NEWS:4313 +msgid "" +"`Issue #4727 `__: The copy module now uses " +"pickle protocol 4 (PEP 3154) and supports copying of instances of classes " +"whose __new__ method takes keyword-only arguments." +msgstr "" + +#: ../../../Misc/NEWS:4317 +msgid "" +"`Issue #23491 `__: Added a zipapp module to " +"support creating executable zip file archives of Python code. Registered \"." +"pyz\" and \".pyzw\" extensions on Windows for these archives (PEP 441)." +msgstr "" + +#: ../../../Misc/NEWS:4321 +msgid "" +"`Issue #23657 `__: Avoid explicit checks for " +"str in zipapp, adding support for pathlib.Path objects as arguments." +msgstr "" + +#: ../../../Misc/NEWS:4324 +msgid "" +"`Issue #23688 `__: Added support of arbitrary " +"bytes-like objects and avoided unnecessary copying of memoryview in gzip." +"GzipFile.write(). Original patch by Wolfgang Maier." +msgstr "" + +#: ../../../Misc/NEWS:4328 +msgid "" +"`Issue #23252 `__: Added support for writing " +"ZIP files to unseekable streams." +msgstr "" + +#: ../../../Misc/NEWS:4330 +msgid "" +"`Issue #23647 `__: Increase impalib's MAXLINE " +"to accommodate modern mailbox sizes." +msgstr "" + +#: ../../../Misc/NEWS:4332 +msgid "" +"`Issue #23539 `__: If body is None, http." +"client.HTTPConnection.request now sets Content-Length to 0 for PUT, POST, " +"and PATCH headers to avoid 411 errors from some web servers." +msgstr "" + +#: ../../../Misc/NEWS:4336 +msgid "" +"`Issue #22351 `__: The nntplib.NNTP " +"constructor no longer leaves the connection and socket open until the " +"garbage collector cleans them up. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4340 +msgid "" +"`Issue #23704 `__: collections.deque() " +"objects now support methods for index(), insert(), and copy(). This allows " +"deques to be registered as a MutableSequence and it improves their " +"substitutability for lists." +msgstr "" + +#: ../../../Misc/NEWS:4344 +msgid "" +"`Issue #23715 `__: :func:`signal.sigwaitinfo` " +"and :func:`signal.sigtimedwait` are now retried when interrupted by a signal " +"not in the *sigset* parameter, if the signal handler does not raise an " +"exception. signal.sigtimedwait() recomputes the timeout with a monotonic " +"clock when it is retried." +msgstr "" + +#: ../../../Misc/NEWS:4349 +msgid "" +"`Issue #23001 `__: Few functions in modules " +"mmap, ossaudiodev, socket, ssl, and codecs, that accepted only read-only " +"bytes-like object now accept writable bytes-like object too." +msgstr "" + +#: ../../../Misc/NEWS:4353 +msgid "" +"`Issue #23646 `__: If time.sleep() is " +"interrupted by a signal, the sleep is now retried with the recomputed delay, " +"except if the signal handler raises an exception (PEP 475)." +msgstr "" + +#: ../../../Misc/NEWS:4357 +msgid "" +"`Issue #23136 `__: _strptime now uniformly " +"handles all days in week 0, including Dec 30 of previous year. Based on " +"patch by Jim Carroll." +msgstr "" + +#: ../../../Misc/NEWS:4360 +msgid "" +"`Issue #23700 `__: Iterator of " +"NamedTemporaryFile now keeps a reference to NamedTemporaryFile instance. " +"Patch by Bohuslav Kabrda." +msgstr "" + +#: ../../../Misc/NEWS:4363 +msgid "" +"`Issue #22903 `__: The fake test case created " +"by unittest.loader when it fails importing a test module is now picklable." +msgstr "" + +#: ../../../Misc/NEWS:4366 +msgid "" +"`Issue #22181 `__: On Linux, os.urandom() now " +"uses the new getrandom() syscall if available, syscall introduced in the " +"Linux kernel 3.17. It is more reliable and more secure, because it avoids " +"the need of a file descriptor and waits until the kernel has enough entropy." +msgstr "" + +#: ../../../Misc/NEWS:4371 +msgid "" +"`Issue #2211 `__: Updated the implementation " +"of the http.cookies.Morsel class. Setting attributes key, value and " +"coded_value directly now is deprecated. update() and setdefault() now " +"transform and check keys. Comparing for equality now takes into account " +"attributes key, value and coded_value. copy() now returns a Morsel, not a " +"dict. repr() now contains all attributes. Optimized checking keys and " +"quoting values. Added new tests. Original patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4379 +msgid "" +"`Issue #18983 `__: Allow selection of output " +"units in timeit. Patch by Julian Gindi." +msgstr "" + +#: ../../../Misc/NEWS:4382 +msgid "" +"`Issue #23631 `__: Fix traceback.format_list " +"when a traceback has been mutated." +msgstr "" + +#: ../../../Misc/NEWS:4384 +msgid "" +"`Issue #23568 `__: Add rdivmod support to " +"MagicMock() objects. Patch by Håkan Lövdahl." +msgstr "" + +#: ../../../Misc/NEWS:4387 +msgid "" +"`Issue #2052 `__: Add charset parameter to " +"HtmlDiff.make_file()." +msgstr "" + +#: ../../../Misc/NEWS:4389 +msgid "" +"`Issue #23668 `__: Support os.truncate and os." +"ftruncate on Windows." +msgstr "" + +#: ../../../Misc/NEWS:4391 +msgid "" +"`Issue #23138 `__: Fixed parsing cookies with " +"absent keys or values in cookiejar. Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4394 +msgid "" +"`Issue #23051 `__: multiprocessing.Pool " +"methods imap() and imap_unordered() now handle exceptions raised by an " +"iterator. Patch by Alon Diamant and Davin Potts." +msgstr "" + +#: ../../../Misc/NEWS:4398 +msgid "" +"`Issue #23581 `__: Add matmul support to " +"MagicMock. Patch by Håkan Lövdahl." +msgstr "" + +#: ../../../Misc/NEWS:4400 +msgid "" +"`Issue #23566 `__: enable(), register(), " +"dump_traceback() and dump_traceback_later() functions of faulthandler now " +"accept file descriptors. Patch by Wei Wu." +msgstr "" + +#: ../../../Misc/NEWS:4404 +msgid "" +"`Issue #22928 `__: Disabled HTTP header " +"injections in http.client. Original patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4407 +msgid "" +"`Issue #23615 `__: Modules bz2, tarfile and " +"tokenize now can be reloaded with imp.reload(). Patch by Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:4410 +msgid "" +"`Issue #23605 `__: os.walk() now calls os." +"scandir() instead of os.listdir(). The usage of os.scandir() reduces the " +"number of calls to os.stat(). Initial patch written by Ben Hoyt." +msgstr "" + +#: ../../../Misc/NEWS:4417 +msgid "" +"`Issue #23585 `__: make patchcheck will " +"ensure the interpreter is built." +msgstr "" + +#: ../../../Misc/NEWS:4422 +msgid "" +"`Issue #23583 `__: Added tests for standard " +"IO streams in IDLE." +msgstr "" + +#: ../../../Misc/NEWS:4424 +msgid "" +"`Issue #22289 `__: Prevent test_urllib2net " +"failures due to ftp connection timeout." +msgstr "" + +#: ../../../Misc/NEWS:4429 +msgid "" +"`Issue #22826 `__: The result of open() in " +"Tools/freeze/bkfile.py is now better compatible with regular files (in " +"particular it now supports the context management protocol)." +msgstr "" + +#: ../../../Misc/NEWS:4435 +msgid "Python 3.5 alpha 2" +msgstr "" + +#: ../../../Misc/NEWS:4437 +msgid "Release date: 2015-03-09" +msgstr "" + +#: ../../../Misc/NEWS:4442 +msgid "" +"`Issue #23571 `__: PyObject_Call() and " +"PyCFunction_Call() now raise a SystemError if a function returns a result " +"and raises an exception. The SystemError is chained to the previous " +"exception." +msgstr "" + +#: ../../../Misc/NEWS:4449 +msgid "" +"`Issue #22524 `__: New os.scandir() function, " +"part of the PEP 471: \"os.scandir() function -- a better and faster " +"directory iterator\". Patch written by Ben Hoyt." +msgstr "" + +#: ../../../Misc/NEWS:4453 +msgid "" +"`Issue #23103 `__: Reduced the memory " +"consumption of IPv4Address and IPv6Address." +msgstr "" + +#: ../../../Misc/NEWS:4455 +msgid "" +"`Issue #21793 `__: BaseHTTPRequestHandler " +"again logs response code as numeric, not as stringified enum. Patch by " +"Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4458 +msgid "" +"`Issue #23476 `__: In the ssl module, enable " +"OpenSSL's X509_V_FLAG_TRUSTED_FIRST flag on certificate stores when it is " +"available." +msgstr "" + +#: ../../../Misc/NEWS:4461 +msgid "" +"`Issue #23576 `__: Avoid stalling in SSL " +"reads when EOF has been reached in the SSL layer but the underlying " +"connection hasn't been closed." +msgstr "" + +#: ../../../Misc/NEWS:4464 +msgid "" +"`Issue #23504 `__: Added an __all__ to the " +"types module." +msgstr "" + +#: ../../../Misc/NEWS:4466 +msgid "" +"`Issue #23563 `__: Optimized utility " +"functions in urllib.parse." +msgstr "" + +#: ../../../Misc/NEWS:4468 +msgid "" +"`Issue #7830 `__: Flatten nested functools." +"partial." +msgstr "" + +#: ../../../Misc/NEWS:4470 +msgid "" +"`Issue #20204 `__: Added the __module__ " +"attribute to _tkinter classes." +msgstr "" + +#: ../../../Misc/NEWS:4472 +msgid "" +"`Issue #19980 `__: Improved help() for non-" +"recognized strings. help('') now shows the help on str. help('help') now " +"shows the help on help(). Original patch by Mark Lawrence." +msgstr "" + +#: ../../../Misc/NEWS:4476 +msgid "" +"`Issue #23521 `__: Corrected pure python " +"implementation of timedelta division." +msgstr "" + +#: ../../../Misc/NEWS:4478 +msgid "Eliminated OverflowError from timedelta * float for some floats;" +msgstr "" + +#: ../../../Misc/NEWS:4479 +msgid "Corrected rounding in timedlta true division." +msgstr "" + +#: ../../../Misc/NEWS:4481 +msgid "" +"`Issue #21619 `__: Popen objects no longer " +"leave a zombie after exit in the with statement if the pipe was broken. " +"Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4484 +msgid "" +"`Issue #22936 `__: Make it possible to show " +"local variables in tracebacks for both the traceback module and unittest." +msgstr "" + +#: ../../../Misc/NEWS:4487 +msgid "" +"`Issue #15955 `__: Add an option to limit the " +"output size in bz2.decompress(). Patch by Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:4490 +msgid "" +"`Issue #6639 `__: Module-level turtle " +"functions no longer raise TclError after closing the window." +msgstr "" + +#: ../../../Misc/NEWS:4493 +msgid "" +"Issues #814253, #9179: Group references and conditional group references now " +"work in lookbehind assertions in regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:4496 +msgid "" +"`Issue #23215 `__: Multibyte codecs with " +"custom error handlers that ignores errors consumed too much memory and " +"raised SystemError or MemoryError. Original patch by Aleksi Torhamo." +msgstr "" + +#: ../../../Misc/NEWS:4500 +msgid "" +"`Issue #5700 `__: io.FileIO() called flush() " +"after closing the file. flush() was not called in close() if closefd=False." +msgstr "" + +#: ../../../Misc/NEWS:4503 +msgid "" +"`Issue #23374 `__: Fixed pydoc failure with " +"non-ASCII files when stdout encoding differs from file system encoding (e.g. " +"on Mac OS)." +msgstr "" + +#: ../../../Misc/NEWS:4506 +msgid "" +"`Issue #23481 `__: Remove RC4 from the SSL " +"module's default cipher list." +msgstr "" + +#: ../../../Misc/NEWS:4508 +msgid "" +"`Issue #21548 `__: Fix pydoc.synopsis() and " +"pydoc.apropos() on modules with empty docstrings." +msgstr "" + +#: ../../../Misc/NEWS:4511 +msgid "" +"`Issue #22885 `__: Fixed arbitrary code " +"execution vulnerability in the dbm.dumb module. Original patch by Claudiu " +"Popa." +msgstr "" + +#: ../../../Misc/NEWS:4514 +msgid "" +"`Issue #23239 `__: ssl.match_hostname() now " +"supports matching of IP addresses." +msgstr "" + +#: ../../../Misc/NEWS:4516 +msgid "" +"`Issue #23146 `__: Fix mishandling of " +"absolute Windows paths with forward slashes in pathlib." +msgstr "" + +#: ../../../Misc/NEWS:4519 +msgid "" +"`Issue #23096 `__: Pickle representation of " +"floats with protocol 0 now is the same for both Python and C implementations." +msgstr "" + +#: ../../../Misc/NEWS:4522 +msgid "" +"`Issue #19105 `__: pprint now more " +"efficiently uses free space at the right." +msgstr "" + +#: ../../../Misc/NEWS:4524 +msgid "" +"`Issue #14910 `__: Add allow_abbrev parameter " +"to argparse.ArgumentParser. Patch by Jonathan Paugh, Steven Bethard, paul j3 " +"and Daniel Eriksson." +msgstr "" + +#: ../../../Misc/NEWS:4527 +msgid "" +"`Issue #21717 `__: tarfile.open() now " +"supports 'x' (exclusive creation) mode." +msgstr "" + +#: ../../../Misc/NEWS:4529 +msgid "" +"`Issue #23344 `__: marshal.dumps() is now " +"20-25% faster on average." +msgstr "" + +#: ../../../Misc/NEWS:4531 +msgid "" +"`Issue #20416 `__: marshal.dumps() with " +"protocols 3 and 4 is now 40-50% faster on average." +msgstr "" + +#: ../../../Misc/NEWS:4534 +msgid "" +"`Issue #23421 `__: Fixed compression in " +"tarfile CLI. Patch by wdv4758h." +msgstr "" + +#: ../../../Misc/NEWS:4536 +msgid "" +"`Issue #23367 `__: Fix possible overflows in " +"the unicodedata module." +msgstr "" + +#: ../../../Misc/NEWS:4538 +msgid "" +"`Issue #23361 `__: Fix possible overflow in " +"Windows subprocess creation code." +msgstr "" + +#: ../../../Misc/NEWS:4540 +msgid "" +"logging.handlers.QueueListener now takes a respect_handler_level keyword " +"argument which, if set to True, will pass messages to handlers taking " +"handler levels into account." +msgstr "" + +#: ../../../Misc/NEWS:4544 +msgid "" +"`Issue #19705 `__: turtledemo now has a " +"visual sorting algorithm demo. Original patch from Jason Yeo." +msgstr "" + +#: ../../../Misc/NEWS:4547 +msgid "" +"`Issue #23801 `__: Fix issue where cgi." +"FieldStorage did not always ignore the entire preamble to a multipart body." +msgstr "" + +#: ../../../Misc/NEWS:4553 +msgid "" +"`Issue #23445 `__: pydebug builds now use " +"\"gcc -Og\" where possible, to make the resulting executable faster." +msgstr "" + +#: ../../../Misc/NEWS:4556 +msgid "" +"`Issue #23686 `__: Update OS X 10.5 installer " +"build to use OpenSSL 1.0.2a." +msgstr "" + +#: ../../../Misc/NEWS:4561 +msgid "" +"`Issue #20204 `__: Deprecation warning is now " +"raised for builtin types without the __module__ attribute." +msgstr "" + +#: ../../../Misc/NEWS:4567 +msgid "" +"`Issue #23465 `__: Implement PEP 486 - Make " +"the Python Launcher aware of virtual environments. Patch by Paul Moore." +msgstr "" + +#: ../../../Misc/NEWS:4570 +msgid "" +"`Issue #23437 `__: Make user scripts " +"directory versioned on Windows. Patch by Paul Moore." +msgstr "" + +#: ../../../Misc/NEWS:4575 +msgid "Python 3.5 alpha 1" +msgstr "" + +#: ../../../Misc/NEWS:4577 +msgid "Release date: 2015-02-08" +msgstr "" + +#: ../../../Misc/NEWS:4582 +msgid "" +"`Issue #23285 `__: PEP 475 - EINTR handling." +msgstr "" + +#: ../../../Misc/NEWS:4584 +msgid "" +"`Issue #22735 `__: Fix many edge cases " +"(including crashes) involving custom mro() implementations." +msgstr "" + +#: ../../../Misc/NEWS:4587 +msgid "" +"`Issue #22896 `__: Avoid using " +"PyObject_AsCharBuffer(), PyObject_AsReadBuffer() and " +"PyObject_AsWriteBuffer()." +msgstr "" + +#: ../../../Misc/NEWS:4590 +msgid "" +"`Issue #21295 `__: Revert some changes " +"(`issue #16795 `__) to AST line numbers and " +"column offsets that constituted a regression." +msgstr "" + +#: ../../../Misc/NEWS:4593 +msgid "" +"`Issue #22986 `__: Allow changing an object's " +"__class__ between a dynamic type and static type in some cases." +msgstr "" + +#: ../../../Misc/NEWS:4596 +msgid "" +"`Issue #15859 `__: " +"PyUnicode_EncodeFSDefault(), PyUnicode_EncodeMBCS() and " +"PyUnicode_EncodeCodePage() now raise an exception if the object is not a " +"Unicode object. For PyUnicode_EncodeFSDefault(), it was already the case on " +"platforms other than Windows. Patch written by Campbell Barton." +msgstr "" + +#: ../../../Misc/NEWS:4601 +msgid "" +"`Issue #21408 `__: The default __ne__() now " +"returns NotImplemented if __eq__() returned NotImplemented. Original patch " +"by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4604 +msgid "" +"`Issue #23321 `__: Fixed a crash in str." +"decode() when error handler returned replacment string longer than " +"mailformed input data." +msgstr "" + +#: ../../../Misc/NEWS:4607 +msgid "" +"`Issue #22286 `__: The \"backslashreplace\" " +"error handlers now works with decoding and translating." +msgstr "" + +#: ../../../Misc/NEWS:4610 +msgid "" +"`Issue #23253 `__: Delay-load " +"ShellExecute[AW] in os.startfile for reduced startup overhead on Windows." +msgstr "" + +#: ../../../Misc/NEWS:4613 +msgid "" +"`Issue #22038 `__: pyatomic.h now uses " +"stdatomic.h or GCC built-in functions for atomic memory access if available. " +"Patch written by Vitor de Lima and Gustavo Temple." +msgstr "" + +#: ../../../Misc/NEWS:4617 +msgid "" +"`Issue #20284 `__: %-interpolation (aka " +"printf) formatting added for bytes and bytearray." +msgstr "" + +#: ../../../Misc/NEWS:4620 +msgid "" +"`Issue #23048 `__: Fix jumping out of an " +"infinite while loop in the pdb." +msgstr "" + +#: ../../../Misc/NEWS:4622 +msgid "" +"`Issue #20335 `__: bytes constructor now " +"raises TypeError when encoding or errors is specified with non-string " +"argument. Based on patch by Renaud Blanch." +msgstr "" + +#: ../../../Misc/NEWS:4625 +msgid "" +"`Issue #22834 `__: If the current working " +"directory ends up being set to a non-existent directory then import will no " +"longer raise FileNotFoundError." +msgstr "" + +#: ../../../Misc/NEWS:4628 +msgid "" +"`Issue #22869 `__: Move the interpreter " +"startup & shutdown code to a new dedicated pylifecycle.c module" +msgstr "" + +#: ../../../Misc/NEWS:4631 +msgid "" +"`Issue #22847 `__: Improve method cache " +"efficiency." +msgstr "" + +#: ../../../Misc/NEWS:4633 +msgid "" +"`Issue #22335 `__: Fix crash when trying to " +"enlarge a bytearray to 0x7fffffff bytes on a 32-bit platform." +msgstr "" + +#: ../../../Misc/NEWS:4636 +msgid "" +"`Issue #22653 `__: Fix an assertion failure " +"in debug mode when doing a reentrant dict insertion in debug mode." +msgstr "" + +#: ../../../Misc/NEWS:4639 +msgid "" +"`Issue #22643 `__: Fix integer overflow in " +"Unicode case operations (upper, lower, title, swapcase, casefold)." +msgstr "" + +#: ../../../Misc/NEWS:4642 +msgid "" +"`Issue #17636 `__: Circular imports involving " +"relative imports are now supported." +msgstr "" + +#: ../../../Misc/NEWS:4645 +msgid "" +"`Issue #22604 `__: Fix assertion error in " +"debug mode when dividing a complex number by (nan+0j)." +msgstr "" + +#: ../../../Misc/NEWS:4648 +msgid "" +"`Issue #21052 `__: Do not raise ImportWarning " +"when sys.path_hooks or sys.meta_path are set to None." +msgstr "" + +#: ../../../Misc/NEWS:4651 +msgid "" +"`Issue #16518 `__: Use 'bytes-like object " +"required' in error messages that previously used the far more cryptic \"'x' " +"does not support the buffer protocol." +msgstr "" + +#: ../../../Misc/NEWS:4655 +msgid "" +"`Issue #22470 `__: Fixed integer overflow " +"issues in \"backslashreplace\", \"xmlcharrefreplace\", and \"surrogatepass\" " +"error handlers." +msgstr "" + +#: ../../../Misc/NEWS:4658 +msgid "" +"`Issue #22540 `__: speed up " +"`PyObject_IsInstance` and `PyObject_IsSubclass` in the common case that the " +"second argument has metaclass `type`." +msgstr "" + +#: ../../../Misc/NEWS:4661 +msgid "" +"`Issue #18711 `__: Add a new `PyErr_FormatV` " +"function, similar to `PyErr_Format` but accepting a `va_list` argument." +msgstr "" + +#: ../../../Misc/NEWS:4664 +msgid "" +"`Issue #22520 `__: Fix overflow checking when " +"generating the repr of a unicode object." +msgstr "" + +#: ../../../Misc/NEWS:4667 +msgid "" +"`Issue #22519 `__: Fix overflow checking in " +"PyBytes_Repr." +msgstr "" + +#: ../../../Misc/NEWS:4669 +msgid "" +"`Issue #22518 `__: Fix integer overflow " +"issues in latin-1 encoding." +msgstr "" + +#: ../../../Misc/NEWS:4671 +msgid "" +"`Issue #16324 `__: _charset parameter of " +"MIMEText now also accepts email.charset.Charset instances. Initial patch by " +"Claude Paroz." +msgstr "" + +#: ../../../Misc/NEWS:4674 +msgid "" +"`Issue #1764286 `__: Fix inspect." +"getsource() to support decorated functions. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:4677 +msgid "" +"`Issue #18554 `__: os.__all__ includes posix " +"functions." +msgstr "" + +#: ../../../Misc/NEWS:4679 +msgid "" +"`Issue #21391 `__: Use os.path.abspath in the " +"shutil module." +msgstr "" + +#: ../../../Misc/NEWS:4681 +msgid "" +"`Issue #11471 `__: avoid generating a " +"JUMP_FORWARD instruction at the end of an if-block if there is no else-" +"clause. Original patch by Eugene Toder." +msgstr "" + +#: ../../../Misc/NEWS:4684 +msgid "" +"`Issue #22215 `__: Now ValueError is raised " +"instead of TypeError when str or bytes argument contains not permitted null " +"character or byte." +msgstr "" + +#: ../../../Misc/NEWS:4687 +msgid "" +"`Issue #22258 `__: Fix the internal function " +"set_inheritable() on Illumos. This platform exposes the function " +"``ioctl(FIOCLEX)``, but calling it fails with errno is ENOTTY: " +"\"Inappropriate ioctl for device\". set_inheritable() now falls back to the " +"slower ``fcntl()`` (``F_GETFD`` and then ``F_SETFD``)." +msgstr "" + +#: ../../../Misc/NEWS:4692 +msgid "" +"`Issue #21389 `__: Displaying the " +"__qualname__ of the underlying function in the repr of a bound method." +msgstr "" + +#: ../../../Misc/NEWS:4695 +msgid "" +"`Issue #22206 `__: Using pthread, " +"PyThread_create_key() now sets errno to ENOMEM and returns -1 (error) on " +"integer overflow." +msgstr "" + +#: ../../../Misc/NEWS:4698 +msgid "" +"`Issue #20184 `__: Argument Clinic based " +"signature introspection added for 30 of the builtin functions." +msgstr "" + +#: ../../../Misc/NEWS:4701 +msgid "" +"`Issue #22116 `__: C functions and methods " +"(of the 'builtin_function_or_method' type) can now be weakref'ed. Patch by " +"Wei Wu." +msgstr "" + +#: ../../../Misc/NEWS:4704 +msgid "" +"`Issue #22077 `__: Improve index error " +"messages for bytearrays, bytes, lists, and tuples by adding 'or slices'. " +"Added ', not ' for bytearrays. Original patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:4708 +msgid "" +"`Issue #20179 `__: Apply Argument Clinic to " +"bytes and bytearray. Patch by Tal Einat." +msgstr "" + +#: ../../../Misc/NEWS:4711 +msgid "" +"`Issue #22082 `__: Clear interned strings in " +"slotdefs." +msgstr "" + +#: ../../../Misc/NEWS:4713 +msgid "Upgrade Unicode database to Unicode 7.0.0." +msgstr "" + +#: ../../../Misc/NEWS:4715 +msgid "" +"`Issue #21897 `__: Fix a crash with the " +"f_locals attribute with closure variables when frame.clear() has been called." +msgstr "" + +#: ../../../Misc/NEWS:4718 +msgid "" +"`Issue #21205 `__: Add a new ``__qualname__`` " +"attribute to generator, the qualified name, and use it in the representation " +"of a generator (``repr(gen)``). The default name of the generator " +"(``__name__`` attribute) is now get from the function instead of the code. " +"Use ``gen.gi_code.co_name`` to get the name of the code." +msgstr "" + +#: ../../../Misc/NEWS:4724 +msgid "" +"`Issue #21669 `__: With the aid of heuristics " +"in SyntaxError.__init__, the parser now attempts to generate more meaningful " +"(or at least more search engine friendly) error messages when \"exec\" and " +"\"print\" are used as statements." +msgstr "" + +#: ../../../Misc/NEWS:4729 +msgid "" +"`Issue #21642 `__: In the conditional if-else " +"expression, allow an integer written with no space between itself and the " +"``else`` keyword (e.g. ``True if 42else False``) to be valid syntax." +msgstr "" + +#: ../../../Misc/NEWS:4733 +msgid "" +"`Issue #21523 `__: Fix over-pessimistic " +"computation of the stack effect of some opcodes in the compiler. This also " +"fixes a quadratic compilation time issue noticeable when compiling code with " +"a large number of \"and\" and \"or\" operators." +msgstr "" + +#: ../../../Misc/NEWS:4738 +msgid "" +"`Issue #21418 `__: Fix a crash in the builtin " +"function super() when called without argument and without current frame (ex: " +"embedded Python)." +msgstr "" + +#: ../../../Misc/NEWS:4741 +msgid "" +"`Issue #21425 `__: Fix flushing of standard " +"streams in the interactive interpreter." +msgstr "" + +#: ../../../Misc/NEWS:4744 +msgid "" +"`Issue #21435 `__: In rare cases, when " +"running finalizers on objects in cyclic trash a bad pointer dereference " +"could occur due to a subtle flaw in internal iteration logic." +msgstr "" + +#: ../../../Misc/NEWS:4748 +msgid "" +"`Issue #21377 `__: PyBytes_Concat() now tries " +"to concatenate in-place when the first argument has a reference count of 1. " +"Patch by Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:4751 +msgid "" +"`Issue #20355 `__: -W command line options " +"now have higher priority than the PYTHONWARNINGS environment variable. " +"Patch by Arfrever." +msgstr "" + +#: ../../../Misc/NEWS:4754 +msgid "" +"`Issue #21274 `__: Define PATH_MAX for GNU/" +"Hurd in Python/pythonrun.c." +msgstr "" + +#: ../../../Misc/NEWS:4756 +msgid "" +"`Issue #20904 `__: Support setting FPU " +"precision on m68k." +msgstr "" + +#: ../../../Misc/NEWS:4758 +msgid "" +"`Issue #21209 `__: Fix sending tuples to " +"custom generator objects with the yield from syntax." +msgstr "" + +#: ../../../Misc/NEWS:4761 +msgid "" +"`Issue #21193 `__: pow(a, b, c) now raises " +"ValueError rather than TypeError when b is negative. Patch by Josh " +"Rosenberg." +msgstr "" + +#: ../../../Misc/NEWS:4764 +msgid "" +"PEP 465 and `Issue #21176 `__: Add the '@' " +"operator for matrix multiplication." +msgstr "" + +#: ../../../Misc/NEWS:4766 +msgid "" +"`Issue #21134 `__: Fix segfault when str is " +"called on an uninitialized UnicodeEncodeError, UnicodeDecodeError, or " +"UnicodeTranslateError object." +msgstr "" + +#: ../../../Misc/NEWS:4769 +msgid "" +"`Issue #19537 `__: Fix PyUnicode_DATA() " +"alignment under m68k. Patch by Andreas Schwab." +msgstr "" + +#: ../../../Misc/NEWS:4772 +msgid "" +"`Issue #20929 `__: Add a type cast to avoid " +"shifting a negative number." +msgstr "" + +#: ../../../Misc/NEWS:4774 +msgid "" +"`Issue #20731 `__: Properly position in " +"source code files even if they are opened in text mode. Patch by Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:4777 +msgid "" +"`Issue #20637 `__: Key-sharing now also works " +"for instance dictionaries of subclasses. Patch by Peter Ingebretson." +msgstr "" + +#: ../../../Misc/NEWS:4780 +msgid "" +"`Issue #8297 `__: Attributes missing from " +"modules now include the module name in the error text. Original patch by " +"ysj.ray." +msgstr "" + +#: ../../../Misc/NEWS:4783 +msgid "" +"`Issue #19995 `__: %c, %o, %x, and %X now " +"raise TypeError on non-integer input." +msgstr "" + +#: ../../../Misc/NEWS:4785 +msgid "" +"`Issue #19655 `__: The ASDL parser - used by " +"the build process to generate code for managing the Python AST in C - was " +"rewritten. The new parser is self contained and does not require to carry " +"long the spark.py parser-generator library; spark.py was removed from the " +"source base." +msgstr "" + +#: ../../../Misc/NEWS:4790 +msgid "" +"`Issue #12546 `__: Allow ``\\x00`` to be used " +"as a fill character when using str, int, float, and complex __format__ " +"methods." +msgstr "" + +#: ../../../Misc/NEWS:4793 +msgid "" +"`Issue #20480 `__: Add ipaddress." +"reverse_pointer. Patch by Leon Weber." +msgstr "" + +#: ../../../Misc/NEWS:4795 +msgid "" +"`Issue #13598 `__: Modify string.Formatter to " +"support auto-numbering of replacement fields. It now matches the behavior of " +"str.format() in this regard. Patches by Phil Elson and Ramchandra Apte." +msgstr "" + +#: ../../../Misc/NEWS:4799 +msgid "" +"`Issue #8931 `__: Make alternate formatting " +"('#') for type 'c' raise an exception. In versions prior to 3.5, '#' with " +"'c' had no effect. Now specifying it is an error. Patch by Torsten " +"Landschoff." +msgstr "" + +#: ../../../Misc/NEWS:4803 +msgid "" +"`Issue #23165 `__: Perform overflow checks " +"before allocating memory in the _Py_char2wchar function." +msgstr "" + +#: ../../../Misc/NEWS:4809 +msgid "" +"`Issue #23399 `__: pyvenv creates relative " +"symlinks where possible." +msgstr "" + +#: ../../../Misc/NEWS:4811 +msgid "" +"`Issue #20289 `__: cgi.FieldStorage() now " +"supports the context management protocol." +msgstr "" + +#: ../../../Misc/NEWS:4814 +msgid "" +"`Issue #13128 `__: Print response headers for " +"CONNECT requests when debuglevel > 0. Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4817 +msgid "" +"`Issue #15381 `__: Optimized io.BytesIO to " +"make less allocations and copyings." +msgstr "" + +#: ../../../Misc/NEWS:4819 +msgid "" +"`Issue #22818 `__: Splitting on a pattern " +"that could match an empty string now raises a warning. Patterns that can " +"only match empty strings are now rejected." +msgstr "" + +#: ../../../Misc/NEWS:4823 +msgid "" +"`Issue #23099 `__: Closing io.BytesIO with " +"exported buffer is rejected now to prevent corrupting exported buffer." +msgstr "" + +#: ../../../Misc/NEWS:4826 +msgid "" +"`Issue #23326 `__: Removed __ne__ " +"implementations. Since fixing default __ne__ implementation in `issue " +"#21408 `__ they are redundant." +msgstr "" + +#: ../../../Misc/NEWS:4829 +msgid "" +"`Issue #23363 `__: Fix possible overflow in " +"itertools.permutations." +msgstr "" + +#: ../../../Misc/NEWS:4831 +msgid "" +"`Issue #23364 `__: Fix possible overflow in " +"itertools.product." +msgstr "" + +#: ../../../Misc/NEWS:4833 +msgid "" +"`Issue #23366 `__: Fixed possible integer " +"overflow in itertools.combinations." +msgstr "" + +#: ../../../Misc/NEWS:4835 +msgid "" +"`Issue #23369 `__: Fixed possible integer " +"overflow in _json.encode_basestring_ascii." +msgstr "" + +#: ../../../Misc/NEWS:4838 +msgid "" +"`Issue #23353 `__: Fix the exception handling " +"of generators in PyEval_EvalFrameEx(). At entry, save or swap the exception " +"state even if PyEval_EvalFrameEx() is called with throwflag=0. At exit, the " +"exception state is now always restored or swapped, not only if why is " +"WHY_YIELD or WHY_RETURN. Patch co-written with Antoine Pitrou." +msgstr "" + +#: ../../../Misc/NEWS:4844 +msgid "" +"`Issue #14099 `__: Restored support of " +"writing ZIP files to tellable but non-seekable streams." +msgstr "" + +#: ../../../Misc/NEWS:4847 +msgid "" +"`Issue #14099 `__: Writing to ZipFile and " +"reading multiple ZipExtFiles is threadsafe now." +msgstr "" + +#: ../../../Misc/NEWS:4850 +msgid "" +"`Issue #19361 `__: JSON decoder now raises " +"JSONDecodeError instead of ValueError." +msgstr "" + +#: ../../../Misc/NEWS:4852 +msgid "" +"`Issue #18518 `__: timeit now rejects " +"statements which can't be compiled outside a function or a loop (e.g. " +"\"return\" or \"break\")." +msgstr "" + +#: ../../../Misc/NEWS:4855 +msgid "" +"`Issue #23094 `__: Fixed readline with frames " +"in Python implementation of pickle." +msgstr "" + +#: ../../../Misc/NEWS:4857 +msgid "" +"`Issue #23268 `__: Fixed bugs in the " +"comparison of ipaddress classes." +msgstr "" + +#: ../../../Misc/NEWS:4859 +msgid "" +"`Issue #21408 `__: Removed incorrect " +"implementations of __ne__() which didn't returned NotImplemented if __eq__() " +"returned NotImplemented. The default __ne__() now works correctly." +msgstr "" + +#: ../../../Misc/NEWS:4863 +msgid "" +"`Issue #19996 `__: :class:`email.feedparser." +"FeedParser` now handles (malformed) headers with no key rather than assuming " +"the body has started." +msgstr "" + +#: ../../../Misc/NEWS:4866 +msgid "" +"`Issue #20188 `__: Support Application-Layer " +"Protocol Negotiation (ALPN) in the ssl module." +msgstr "" + +#: ../../../Misc/NEWS:4869 +msgid "" +"`Issue #23133 `__: Pickling of ipaddress " +"objects now produces more compact and portable representation." +msgstr "" + +#: ../../../Misc/NEWS:4872 +msgid "" +"`Issue #23248 `__: Update ssl error codes " +"from latest OpenSSL git master." +msgstr "" + +#: ../../../Misc/NEWS:4874 +msgid "" +"`Issue #23266 `__: Much faster implementation " +"of ipaddress.collapse_addresses() when there are many non-consecutive " +"addresses." +msgstr "" + +#: ../../../Misc/NEWS:4877 +msgid "" +"`Issue #23098 `__: 64-bit dev_t is now " +"supported in the os module." +msgstr "" + +#: ../../../Misc/NEWS:4879 +msgid "" +"`Issue #21817 `__: When an exception is " +"raised in a task submitted to a ProcessPoolExecutor, the remote traceback is " +"now displayed in the parent process. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:4883 +msgid "" +"`Issue #15955 `__: Add an option to limit " +"output size when decompressing LZMA data. Patch by Nikolaus Rath and Martin " +"Panter." +msgstr "" + +#: ../../../Misc/NEWS:4886 +msgid "" +"`Issue #23250 `__: In the http.cookies " +"module, capitalize \"HttpOnly\" and \"Secure\" as they are written in the " +"standard." +msgstr "" + +#: ../../../Misc/NEWS:4889 +msgid "" +"`Issue #23063 `__: In the disutils' check " +"command, fix parsing of reST with code or code-block directives." +msgstr "" + +#: ../../../Misc/NEWS:4892 +msgid "" +"`Issue #23209 `__, #23225: selectors." +"BaseSelector.get_key() now raises a RuntimeError if the selector is closed. " +"And selectors.BaseSelector.close() now clears its internal reference to the " +"selector mapping to break a reference cycle. Initial patch written by Martin " +"Richard." +msgstr "" + +#: ../../../Misc/NEWS:4897 +msgid "" +"`Issue #17911 `__: Provide a way to seed the " +"linecache for a PEP-302 module without actually loading the code." +msgstr "" + +#: ../../../Misc/NEWS:4900 +msgid "" +"`Issue #17911 `__: Provide a new object API " +"for traceback, including the ability to not lookup lines at all until the " +"traceback is actually rendered, without any trace of the original objects " +"being kept alive." +msgstr "" + +#: ../../../Misc/NEWS:4904 +msgid "" +"`Issue #19777 `__: Provide a home() " +"classmethod on Path objects. Contributed by Victor Salgado and Mayank " +"Tripathi." +msgstr "" + +#: ../../../Misc/NEWS:4907 +msgid "" +"`Issue #23206 `__: Make ``json.dumps(..., " +"ensure_ascii=False)`` as fast as the default case of ``ensure_ascii=True``. " +"Patch by Naoki Inada." +msgstr "" + +#: ../../../Misc/NEWS:4910 +msgid "" +"`Issue #23185 `__: Add math.inf and math.nan " +"constants." +msgstr "" + +#: ../../../Misc/NEWS:4912 +msgid "" +"`Issue #23186 `__: Add ssl.SSLObject." +"shared_ciphers() and ssl.SSLSocket.shared_ciphers() to fetch the client's " +"list ciphers sent at handshake." +msgstr "" + +#: ../../../Misc/NEWS:4916 +msgid "" +"`Issue #23143 `__: Remove compatibility with " +"OpenSSLs older than 0.9.8." +msgstr "" + +#: ../../../Misc/NEWS:4918 +msgid "" +"`Issue #23132 `__: Improve performance and " +"introspection support of comparison methods created by functool." +"total_ordering." +msgstr "" + +#: ../../../Misc/NEWS:4921 +msgid "" +"`Issue #19776 `__: Add an expanduser() method " +"on Path objects." +msgstr "" + +#: ../../../Misc/NEWS:4923 +msgid "" +"`Issue #23112 `__: Fix SimpleHTTPServer to " +"correctly carry the query string and fragment when it redirects to add a " +"trailing slash." +msgstr "" + +#: ../../../Misc/NEWS:4926 +msgid "" +"`Issue #21793 `__: Added http.HTTPStatus " +"enums (i.e. HTTPStatus.OK, HTTPStatus.NOT_FOUND). Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4929 +msgid "" +"`Issue #23093 `__: In the io, module allow " +"more operations to work on detached streams." +msgstr "" + +#: ../../../Misc/NEWS:4932 +msgid "" +"`Issue #23111 `__: In the ftplib, make ssl." +"PROTOCOL_SSLv23 the default protocol version." +msgstr "" + +#: ../../../Misc/NEWS:4935 +msgid "" +"`Issue #22585 `__: On OpenBSD 5.6 and newer, " +"os.urandom() now calls getentropy(), instead of reading /dev/urandom, to get " +"pseudo-random bytes." +msgstr "" + +#: ../../../Misc/NEWS:4938 +msgid "" +"`Issue #19104 `__: pprint now produces " +"evaluable output for wrapped strings." +msgstr "" + +#: ../../../Misc/NEWS:4940 +msgid "" +"`Issue #23071 `__: Added missing names to " +"codecs.__all__. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4942 +msgid "" +"`Issue #22783 `__: Pickling now uses the " +"NEWOBJ opcode instead of the NEWOBJ_EX opcode if possible." +msgstr "" + +#: ../../../Misc/NEWS:4945 +msgid "" +"`Issue #15513 `__: Added a __sizeof__ " +"implementation for pickle classes." +msgstr "" + +#: ../../../Misc/NEWS:4947 +msgid "" +"`Issue #19858 `__: pickletools.optimize() now " +"aware of the MEMOIZE opcode, can produce more compact result and no longer " +"produces invalid output if input data contains MEMOIZE opcodes together with " +"PUT or BINPUT opcodes." +msgstr "" + +#: ../../../Misc/NEWS:4951 +msgid "" +"`Issue #22095 `__: Fixed HTTPConnection." +"set_tunnel with default port. The port value in the host header was set to " +"\"None\". Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:4954 +msgid "" +"`Issue #23016 `__: A warning no longer " +"produces an AttributeError when the program is run with pythonw.exe." +msgstr "" + +#: ../../../Misc/NEWS:4957 +msgid "" +"`Issue #21775 `__: shutil.copytree(): fix " +"crash when copying to VFAT. An exception handler assumed that OSError " +"objects always have a 'winerror' attribute. That is not the case, so the " +"exception handler itself raised AttributeError when run on Linux (and, " +"presumably, any other non-Windows OS). Patch by Greg Ward." +msgstr "" + +#: ../../../Misc/NEWS:4963 +msgid "" +"`Issue #1218234 `__: Fix inspect." +"getsource() to load updated source of reloaded module. Initial patch by " +"Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:4966 +msgid "" +"`Issue #21740 `__: Support wrapped callables " +"in doctest. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:4968 +msgid "" +"`Issue #23009 `__: Make sure selectors." +"EpollSelecrtor.select() works when no FD is registered." +msgstr "" + +#: ../../../Misc/NEWS:4971 +msgid "" +"`Issue #22959 `__: In the constructor of http." +"client.HTTPSConnection, prefer the context's check_hostname attribute over " +"the *check_hostname* parameter." +msgstr "" + +#: ../../../Misc/NEWS:4974 +msgid "" +"`Issue #22696 `__: Add function :func:`sys." +"is_finalizing` to know about interpreter shutdown." +msgstr "" + +#: ../../../Misc/NEWS:4977 +msgid "" +"`Issue #16043 `__: Add a default limit for " +"the amount of data xmlrpclib.gzip_decode will return. This resolves " +"CVE-2013-1753." +msgstr "" + +#: ../../../Misc/NEWS:4980 +msgid "" +"`Issue #14099 `__: ZipFile.open() no longer " +"reopen the underlying file. Objects returned by ZipFile.open() can now " +"operate independently of the ZipFile even if the ZipFile was created by " +"passing in a file-like object as the first argument to the constructor." +msgstr "" + +#: ../../../Misc/NEWS:4985 +msgid "" +"`Issue #22966 `__: Fix __pycache__ pyc file " +"name clobber when pyc_compile is asked to compile a source file containing " +"multiple dots in the source file name." +msgstr "" + +#: ../../../Misc/NEWS:4989 +msgid "" +"`Issue #21971 `__: Update turtledemo doc and " +"add module to the index." +msgstr "" + +#: ../../../Misc/NEWS:4991 +msgid "" +"`Issue #21032 `__: Fixed socket leak if " +"HTTPConnection.getresponse() fails. Original patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:4994 +msgid "" +"`Issue #22407 `__: Deprecated the use of re." +"LOCALE flag with str patterns or re.ASCII. It was newer worked." +msgstr "" + +#: ../../../Misc/NEWS:4997 +msgid "" +"`Issue #22902 `__: The \"ip\" command is now " +"used on Linux to determine MAC address in uuid.getnode(). Pach by Bruno " +"Cauet." +msgstr "" + +#: ../../../Misc/NEWS:5000 +msgid "" +"`Issue #22960 `__: Add a context argument to " +"xmlrpclib.ServerProxy constructor." +msgstr "" + +#: ../../../Misc/NEWS:5002 +msgid "" +"`Issue #22389 `__: Add contextlib." +"redirect_stderr()." +msgstr "" + +#: ../../../Misc/NEWS:5004 +msgid "" +"`Issue #21356 `__: Make ssl.RAND_egd() " +"optional to support LibreSSL. The availability of the function is checked " +"during the compilation. Patch written by Bernard Spil." +msgstr "" + +#: ../../../Misc/NEWS:5008 +msgid "" +"`Issue #22915 `__: SAX parser now supports " +"files opened with file descriptor or bytes path." +msgstr "" + +#: ../../../Misc/NEWS:5011 +msgid "" +"`Issue #22609 `__: Constructors and update " +"methods of mapping classes in the collections module now accept the self " +"keyword argument." +msgstr "" + +#: ../../../Misc/NEWS:5014 +msgid "" +"`Issue #22940 `__: Add readline." +"append_history_file." +msgstr "" + +#: ../../../Misc/NEWS:5016 +msgid "" +"`Issue #19676 `__: Added the \"namereplace\" " +"error handler." +msgstr "" + +#: ../../../Misc/NEWS:5018 +msgid "" +"`Issue #22788 `__: Add *context* parameter to " +"logging.handlers.HTTPHandler." +msgstr "" + +#: ../../../Misc/NEWS:5020 +msgid "" +"`Issue #22921 `__: Allow SSLContext to take " +"the *hostname* parameter even if OpenSSL doesn't support SNI." +msgstr "" + +#: ../../../Misc/NEWS:5023 +msgid "" +"`Issue #22894 `__: TestCase.subTest() would " +"cause the test suite to be stopped when in failfast mode, even in the " +"absence of failures." +msgstr "" + +#: ../../../Misc/NEWS:5026 +msgid "" +"`Issue #22796 `__: HTTP cookie parsing is now " +"stricter, in order to protect against potential injection attacks." +msgstr "" + +#: ../../../Misc/NEWS:5029 +msgid "" +"`Issue #22370 `__: Windows detection in " +"pathlib is now more robust." +msgstr "" + +#: ../../../Misc/NEWS:5031 +msgid "" +"`Issue #22841 `__: Reject coroutines in " +"asyncio add_signal_handler(). Patch by Ludovic.Gasc." +msgstr "" + +#: ../../../Misc/NEWS:5034 +msgid "" +"`Issue #19494 `__: Added urllib.request." +"HTTPBasicPriorAuthHandler. Patch by Matej Cepl." +msgstr "" + +#: ../../../Misc/NEWS:5037 +msgid "" +"`Issue #22578 `__: Added attributes to the re." +"error class." +msgstr "" + +#: ../../../Misc/NEWS:5039 +msgid "" +"`Issue #22849 `__: Fix possible double free " +"in the io.TextIOWrapper constructor." +msgstr "" + +#: ../../../Misc/NEWS:5041 +msgid "" +"`Issue #12728 `__: Different Unicode " +"characters having the same uppercase but different lowercase are now matched " +"in case-insensitive regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:5044 +msgid "" +"`Issue #22821 `__: Fixed fcntl() with integer " +"argument on 64-bit big-endian platforms." +msgstr "" + +#: ../../../Misc/NEWS:5047 +msgid "" +"`Issue #21650 `__: Add an `--sort-keys` " +"option to json.tool CLI." +msgstr "" + +#: ../../../Misc/NEWS:5049 +msgid "" +"`Issue #22824 `__: Updated reprlib output " +"format for sets to use set literals. Patch contributed by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:5052 +msgid "" +"`Issue #22824 `__: Updated reprlib output " +"format for arrays to display empty arrays without an unnecessary empty " +"list. Suggested by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:5055 +msgid "" +"`Issue #22406 `__: Fixed the uu_codec codec " +"incorrectly ported to 3.x. Based on patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:5058 +msgid "" +"`Issue #17293 `__: uuid.getnode() now " +"determines MAC address on AIX using netstat. Based on patch by Aivars Kalv�?" +"ns." +msgstr "" + +#: ../../../Misc/NEWS:5061 +msgid "" +"`Issue #22769 `__: Fixed ttk.Treeview." +"tag_has() when called without arguments." +msgstr "" + +#: ../../../Misc/NEWS:5063 +msgid "" +"`Issue #22417 `__: Verify certificates by " +"default in httplib (PEP 476)." +msgstr "" + +#: ../../../Misc/NEWS:5065 +msgid "" +"`Issue #22775 `__: Fixed unpickling of http." +"cookies.SimpleCookie with protocol 2 and above. Patch by Tim Graham." +msgstr "" + +#: ../../../Misc/NEWS:5068 +msgid "" +"`Issue #22776 `__: Brought excluded code into " +"the scope of a try block in SysLogHandler.emit()." +msgstr "" + +#: ../../../Misc/NEWS:5071 +msgid "" +"`Issue #22665 `__: Add missing " +"get_terminal_size and SameFileError to shutil.__all__." +msgstr "" + +#: ../../../Misc/NEWS:5074 +msgid "" +"`Issue #6623 `__: Remove deprecated Netrc " +"class in the ftplib module. Patch by Matt Chaput." +msgstr "" + +#: ../../../Misc/NEWS:5077 +msgid "" +"`Issue #17381 `__: Fixed handling of case-" +"insensitive ranges in regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:5080 +msgid "" +"`Issue #22410 `__: Module level functions in " +"the re module now cache compiled locale-dependent regular expressions taking " +"into account the locale." +msgstr "" + +#: ../../../Misc/NEWS:5083 +msgid "" +"`Issue #22759 `__: Query methods on pathlib." +"Path() (exists(), is_dir(), etc.) now return False when the underlying stat " +"call raises NotADirectoryError." +msgstr "" + +#: ../../../Misc/NEWS:5086 +msgid "" +"`Issue #8876 `__: distutils now falls back to " +"copying files when hard linking doesn't work. This allows use with special " +"filesystems such as VirtualBox shared folders." +msgstr "" + +#: ../../../Misc/NEWS:5090 +msgid "" +"`Issue #22217 `__: Implemented reprs of " +"classes in the zipfile module." +msgstr "" + +#: ../../../Misc/NEWS:5092 +msgid "" +"`Issue #22457 `__: Honour load_tests in the " +"start_dir of discovery." +msgstr "" + +#: ../../../Misc/NEWS:5094 +msgid "" +"`Issue #18216 `__: gettext now raises an " +"error when a .mo file has an unsupported major version number. Patch by " +"Aaron Hill." +msgstr "" + +#: ../../../Misc/NEWS:5097 +msgid "" +"`Issue #13918 `__: Provide a locale." +"delocalize() function which can remove locale-specific number formatting " +"from a string representing a number, without then converting it to a " +"specific type. Patch by Cédric Krier." +msgstr "" + +#: ../../../Misc/NEWS:5101 +msgid "" +"`Issue #22676 `__: Make the pickling of " +"global objects which don't have a __module__ attribute less slow." +msgstr "" + +#: ../../../Misc/NEWS:5104 +msgid "" +"`Issue #18853 `__: Fixed ResourceWarning in " +"shlex.__nain__." +msgstr "" + +#: ../../../Misc/NEWS:5106 +msgid "" +"`Issue #9351 `__: Defaults set with " +"set_defaults on an argparse subparser are no longer ignored when also set on " +"the parent parser." +msgstr "" + +#: ../../../Misc/NEWS:5109 +msgid "" +"`Issue #7559 `__: unittest test loading " +"ImportErrors are reported as import errors with their import exception " +"rather than as attribute errors after the import has already failed." +msgstr "" + +#: ../../../Misc/NEWS:5113 +msgid "" +"`Issue #19746 `__: Make it possible to " +"examine the errors from unittest discovery without executing the test suite. " +"The new `errors` attribute on TestLoader exposes these non-fatal errors " +"encountered during discovery." +msgstr "" + +#: ../../../Misc/NEWS:5117 +msgid "" +"`Issue #21991 `__: Make email." +"headerregistry's header 'params' attributes be read-only " +"(MappingProxyType). Previously the dictionary was modifiable but a new one " +"was created on each access of the attribute." +msgstr "" + +#: ../../../Misc/NEWS:5121 +msgid "" +"`Issue #22638 `__: SSLv3 is now disabled " +"throughout the standard library. It can still be enabled by instantiating a " +"SSLContext manually." +msgstr "" + +#: ../../../Misc/NEWS:5124 +msgid "" +"`Issue #22641 `__: In asyncio, the default " +"SSL context for client connections is now created using ssl." +"create_default_context(), for stronger security." +msgstr "" + +#: ../../../Misc/NEWS:5127 +msgid "" +"`Issue #17401 `__: Include closefd in io." +"FileIO repr." +msgstr "" + +#: ../../../Misc/NEWS:5129 +msgid "" +"`Issue #21338 `__: Add silent mode for " +"compileall. quiet parameters of compile_{dir, file, path} functions now have " +"a multilevel value. Also, -q option of the CLI now have a multilevel value. " +"Patch by Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:5133 +msgid "" +"`Issue #20152 `__: Convert the array and " +"cmath modules to Argument Clinic." +msgstr "" + +#: ../../../Misc/NEWS:5135 +msgid "" +"`Issue #18643 `__: Add socket.socketpair() on " +"Windows." +msgstr "" + +#: ../../../Misc/NEWS:5137 +msgid "" +"`Issue #22435 `__: Fix a file descriptor leak " +"when socketserver bind fails." +msgstr "" + +#: ../../../Misc/NEWS:5139 +msgid "" +"`Issue #13096 `__: Fixed segfault in CTypes " +"POINTER handling of large values." +msgstr "" + +#: ../../../Misc/NEWS:5142 +msgid "" +"`Issue #11694 `__: Raise ConversionError in " +"xdrlib as documented. Patch by Filip Gruszczyński and Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5145 +msgid "" +"`Issue #19380 `__: Optimized parsing of " +"regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:5147 +msgid "" +"`Issue #1519638 `__: Now unmatched groups " +"are replaced with empty strings in re.sub() and re.subn()." +msgstr "" + +#: ../../../Misc/NEWS:5150 +msgid "" +"`Issue #18615 `__: sndhdr.what/whathdr now " +"return a namedtuple." +msgstr "" + +#: ../../../Misc/NEWS:5152 +msgid "" +"`Issue #22462 `__: Fix pyexpat's creation of " +"a dummy frame to make it appear in exception tracebacks." +msgstr "" + +#: ../../../Misc/NEWS:5155 +msgid "" +"`Issue #21965 `__: Add support for in-memory " +"SSL to the ssl module. Patch by Geert Jansen." +msgstr "" + +#: ../../../Misc/NEWS:5158 +msgid "" +"`Issue #21173 `__: Fix len() on a " +"WeakKeyDictionary when .clear() was called with an iterator alive." +msgstr "" + +#: ../../../Misc/NEWS:5161 +msgid "" +"`Issue #11866 `__: Eliminated race condition " +"in the computation of names for new threads." +msgstr "" + +#: ../../../Misc/NEWS:5164 +msgid "" +"`Issue #21905 `__: Avoid RuntimeError in " +"pickle.whichmodule() when sys.modules is mutated while iterating. Patch by " +"Olivier Grisel." +msgstr "" + +#: ../../../Misc/NEWS:5167 +msgid "" +"`Issue #11271 `__: concurrent.futures." +"Executor.map() now takes a *chunksize* argument to allow batching of tasks " +"in child processes and improve performance of ProcessPoolExecutor. Patch by " +"Dan O'Reilly." +msgstr "" + +#: ../../../Misc/NEWS:5171 +msgid "" +"`Issue #21883 `__: os.path.join() and os.path." +"relpath() now raise a TypeError with more helpful error message for " +"unsupported or mismatched types of arguments." +msgstr "" + +#: ../../../Misc/NEWS:5174 +msgid "" +"`Issue #22219 `__: The zipfile module CLI now " +"adds entries for directories (including empty directories) in ZIP file." +msgstr "" + +#: ../../../Misc/NEWS:5177 +msgid "" +"`Issue #22449 `__: In the ssl.SSLContext." +"load_default_certs, consult the environmental variables SSL_CERT_DIR and " +"SSL_CERT_FILE on Windows." +msgstr "" + +#: ../../../Misc/NEWS:5180 +msgid "" +"`Issue #22508 `__: The email.__version__ " +"variable has been removed; the email code is no longer shipped separately " +"from the stdlib, and __version__ hasn't been updated in several releases." +msgstr "" + +#: ../../../Misc/NEWS:5184 +msgid "" +"`Issue #20076 `__: Added non derived UTF-8 " +"aliases to locale aliases table." +msgstr "" + +#: ../../../Misc/NEWS:5186 +msgid "" +"`Issue #20079 `__: Added locales supported in " +"glibc 2.18 to locale alias table." +msgstr "" + +#: ../../../Misc/NEWS:5188 +msgid "" +"`Issue #20218 `__: Added convenience methods " +"read_text/write_text and read_bytes/ write_bytes to pathlib.Path objects." +msgstr "" + +#: ../../../Misc/NEWS:5191 +msgid "" +"`Issue #22396 `__: On 32-bit AIX platform, " +"don't expose os.posix_fadvise() nor os.posix_fallocate() because their " +"prototypes in system headers are wrong." +msgstr "" + +#: ../../../Misc/NEWS:5194 +msgid "" +"`Issue #22517 `__: When an io.BufferedRWPair " +"object is deallocated, clear its weakrefs." +msgstr "" + +#: ../../../Misc/NEWS:5197 +msgid "" +"`Issue #22437 `__: Number of capturing groups " +"in regular expression is no longer limited by 100." +msgstr "" + +#: ../../../Misc/NEWS:5200 +msgid "" +"`Issue #17442 `__: InteractiveInterpreter now " +"displays the full chained traceback in its showtraceback method, to match " +"the built in interactive interpreter." +msgstr "" + +#: ../../../Misc/NEWS:5203 +msgid "" +"`Issue #23392 `__: Added tests for marshal C " +"API that works with FILE*." +msgstr "" + +#: ../../../Misc/NEWS:5206 +msgid "" +"`Issue #10510 `__: distutils register and " +"upload methods now use HTML standards compliant CRLF line endings." +msgstr "" + +#: ../../../Misc/NEWS:5209 +msgid "" +"`Issue #9850 `__: Fixed macpath.join() for " +"empty first component. Patch by Oleg Oshmyan." +msgstr "" + +#: ../../../Misc/NEWS:5212 +msgid "" +"`Issue #5309 `__: distutils' build and " +"build_ext commands now accept a ``-j`` option to enable parallel building of " +"extension modules." +msgstr "" + +#: ../../../Misc/NEWS:5215 +msgid "" +"`Issue #22448 `__: Improve canceled timer " +"handles cleanup to prevent unbound memory usage. Patch by Joshua Moore-Oliva." +msgstr "" + +#: ../../../Misc/NEWS:5218 +msgid "" +"`Issue #22427 `__: TemporaryDirectory no " +"longer attempts to clean up twice when used in the with statement in " +"generator." +msgstr "" + +#: ../../../Misc/NEWS:5221 +msgid "" +"`Issue #22362 `__: Forbidden ambiguous octal " +"escapes out of range 0-0o377 in regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:5224 +msgid "" +"`Issue #20912 `__: Now directories added to " +"ZIP file have correct Unix and MS-DOS directory attributes." +msgstr "" + +#: ../../../Misc/NEWS:5227 +msgid "" +"`Issue #21866 `__: ZipFile.close() no longer " +"writes ZIP64 central directory records if allowZip64 is false." +msgstr "" + +#: ../../../Misc/NEWS:5230 +msgid "" +"`Issue #22278 `__: Fix urljoin problem with " +"relative urls, a regression observed after changes to issue22118 were " +"submitted." +msgstr "" + +#: ../../../Misc/NEWS:5233 +msgid "" +"`Issue #22415 `__: Fixed debugging output of " +"the GROUPREF_EXISTS opcode in the re module. Removed trailing spaces in " +"debugging output." +msgstr "" + +#: ../../../Misc/NEWS:5236 +msgid "" +"`Issue #22423 `__: Unhandled exception in " +"thread no longer causes unhandled AttributeError when sys.stderr is None." +msgstr "" + +#: ../../../Misc/NEWS:5239 +msgid "" +"`Issue #21332 `__: Ensure that ``bufsize=1`` " +"in subprocess.Popen() selects line buffering, rather than block buffering. " +"Patch by Akira Li." +msgstr "" + +#: ../../../Misc/NEWS:5242 +msgid "" +"`Issue #21091 `__: Fix API bug: email.message." +"EmailMessage.is_attachment is now a method." +msgstr "" + +#: ../../../Misc/NEWS:5245 +msgid "" +"`Issue #21079 `__: Fix email.message." +"EmailMessage.is_attachment to return the correct result when the header has " +"parameters as well as a value." +msgstr "" + +#: ../../../Misc/NEWS:5248 +msgid "" +"`Issue #22247 `__: Add NNTPError to nntplib." +"__all__." +msgstr "" + +#: ../../../Misc/NEWS:5250 +msgid "" +"`Issue #22366 `__: urllib.request.urlopen " +"will accept a context object (SSLContext) as an argument which will then be " +"used for HTTPS connection. Patch by Alex Gaynor." +msgstr "" + +#: ../../../Misc/NEWS:5254 +msgid "" +"`Issue #4180 `__: The warnings registries are " +"now reset when the filters are modified." +msgstr "" + +#: ../../../Misc/NEWS:5257 +msgid "" +"`Issue #22419 `__: Limit the length of " +"incoming HTTP request in wsgiref server to 65536 bytes and send a 414 error " +"code for higher lengths. Patch contributed by Devin Cook." +msgstr "" + +#: ../../../Misc/NEWS:5261 +msgid "" +"Lax cookie parsing in http.cookies could be a security issue when combined " +"with non-standard cookie handling in some Web browsers. Reported by Sergey " +"Bobrov." +msgstr "" + +#: ../../../Misc/NEWS:5265 +msgid "" +"`Issue #20537 `__: logging methods now accept " +"an exception instance as well as a Boolean value or exception tuple. Thanks " +"to Yury Selivanov for the patch." +msgstr "" + +#: ../../../Misc/NEWS:5268 +msgid "" +"`Issue #22384 `__: An exception in Tkinter " +"callback no longer crashes the program when it is run with pythonw.exe." +msgstr "" + +#: ../../../Misc/NEWS:5271 +msgid "" +"`Issue #22168 `__: Prevent turtle " +"AttributeError with non-default Canvas on OS X." +msgstr "" + +#: ../../../Misc/NEWS:5273 +msgid "" +"`Issue #21147 `__: sqlite3 now raises an " +"exception if the request contains a null character instead of truncating " +"it. Based on patch by Victor Stinner." +msgstr "" + +#: ../../../Misc/NEWS:5276 +msgid "" +"`Issue #13968 `__: The glob module now " +"supports recursive search in subdirectories using the \"**\" pattern." +msgstr "" + +#: ../../../Misc/NEWS:5279 +msgid "" +"`Issue #21951 `__: Fixed a crash in Tkinter " +"on AIX when called Tcl command with empty string or tuple argument." +msgstr "" + +#: ../../../Misc/NEWS:5282 +msgid "" +"`Issue #21951 `__: Tkinter now most likely " +"raises MemoryError instead of crash if the memory allocation fails." +msgstr "" + +#: ../../../Misc/NEWS:5285 +msgid "" +"`Issue #22338 `__: Fix a crash in the json " +"module on memory allocation failure." +msgstr "" + +#: ../../../Misc/NEWS:5287 +msgid "" +"`Issue #12410 `__: imaplib.IMAP4 now supports " +"the context management protocol. Original patch by Tarek Ziadé." +msgstr "" + +#: ../../../Misc/NEWS:5290 +msgid "" +"`Issue #21270 `__: We now override tuple " +"methods in mock.call objects so that they can be used as normal call " +"attributes." +msgstr "" + +#: ../../../Misc/NEWS:5293 +msgid "" +"`Issue #16662 `__: load_tests() is now " +"unconditionally run when it is present in a package's __init__.py. " +"TestLoader.loadTestsFromModule() still accepts use_load_tests, but it is " +"deprecated and ignored. A new keyword-only attribute `pattern` is added and " +"documented. Patch given by Robert Collins, tweaked by Barry Warsaw." +msgstr "" + +#: ../../../Misc/NEWS:5299 +msgid "" +"`Issue #22226 `__: First letter no longer is " +"stripped from the \"status\" key in the result of Treeview.heading()." +msgstr "" + +#: ../../../Misc/NEWS:5302 +msgid "" +"`Issue #19524 `__: Fixed resource leak in the " +"HTTP connection when an invalid response is received. Patch by Martin " +"Panter." +msgstr "" + +#: ../../../Misc/NEWS:5305 +msgid "" +"`Issue #20421 `__: Add a .version() method to " +"SSL sockets exposing the actual protocol version in use." +msgstr "" + +#: ../../../Misc/NEWS:5308 +msgid "" +"`Issue #19546 `__: configparser exceptions no " +"longer expose implementation details. Chained KeyErrors are removed, which " +"leads to cleaner tracebacks. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5312 +msgid "" +"`Issue #22051 `__: turtledemo no longer " +"reloads examples to re-run them. Initialization of variables and gui setup " +"should be done in main(), which is called each time a demo is run, but not " +"on import." +msgstr "" + +#: ../../../Misc/NEWS:5316 +msgid "" +"`Issue #21933 `__: Turtledemo users can " +"change the code font size with a menu selection or control(command) '-' or " +"'+' or control-mousewheel. Original patch by Lita Cho." +msgstr "" + +#: ../../../Misc/NEWS:5320 +msgid "" +"`Issue #21597 `__: The separator between the " +"turtledemo text pane and the drawing canvas can now be grabbed and dragged " +"with a mouse. The code text pane can be widened to easily view or copy the " +"full width of the text. The canvas can be widened on small screens. " +"Original patches by Jan Kanis and Lita Cho." +msgstr "" + +#: ../../../Misc/NEWS:5325 +msgid "" +"`Issue #18132 `__: Turtledemo buttons no " +"longer disappear when the window is shrunk. Original patches by Jan Kanis " +"and Lita Cho." +msgstr "" + +#: ../../../Misc/NEWS:5328 +msgid "" +"`Issue #22043 `__: time.monotonic() is now " +"always available. ``threading.Lock.acquire()``, ``threading.RLock." +"acquire()`` and socket operations now use a monotonic clock, instead of the " +"system clock, when a timeout is used." +msgstr "" + +#: ../../../Misc/NEWS:5333 +msgid "" +"`Issue #21527 `__: Add a default number of " +"workers to ThreadPoolExecutor equal to 5 times the number of CPUs. Patch by " +"Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5336 +msgid "" +"`Issue #22216 `__: smtplib now resets its " +"state more completely after a quit. The most obvious consequence of the " +"previous behavior was a STARTTLS failure during a connect/starttls/quit/" +"connect/starttls sequence." +msgstr "" + +#: ../../../Misc/NEWS:5340 +msgid "" +"`Issue #22098 `__: ctypes' BigEndianStructure " +"and LittleEndianStructure now define an empty __slots__ so that subclasses " +"don't always get an instance dict. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5344 +msgid "" +"`Issue #22185 `__: Fix an occasional " +"RuntimeError in threading.Condition.wait() caused by mutation of the waiters " +"queue without holding the lock. Patch by Doug Zongker." +msgstr "" + +#: ../../../Misc/NEWS:5348 +msgid "" +"`Issue #22287 `__: On UNIX, " +"_PyTime_gettimeofday() now uses clock_gettime(CLOCK_REALTIME) if available. " +"As a side effect, Python now depends on the librt library on Solaris and on " +"Linux (only with glibc older than 2.17)." +msgstr "" + +#: ../../../Misc/NEWS:5353 +msgid "" +"`Issue #22182 `__: Use e.args to unpack " +"exceptions correctly in distutils.file_util.move_file. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5356 +msgid "" +"The webbrowser module now uses subprocess's start_new_session=True rather " +"than a potentially risky preexec_fn=os.setsid call." +msgstr "" + +#: ../../../Misc/NEWS:5359 +msgid "" +"`Issue #22042 `__: signal.set_wakeup_fd(fd) " +"now raises an exception if the file descriptor is in blocking mode." +msgstr "" + +#: ../../../Misc/NEWS:5362 +msgid "" +"`Issue #16808 `__: inspect.stack() now " +"returns a named tuple instead of a tuple. Patch by Daniel Shahaf." +msgstr "" + +#: ../../../Misc/NEWS:5365 +msgid "" +"`Issue #22236 `__: Fixed Tkinter images " +"copying operations in NoDefaultRoot mode." +msgstr "" + +#: ../../../Misc/NEWS:5367 +msgid "" +"`Issue #2527 `__: Add a *globals* argument to " +"timeit functions, in order to override the globals namespace in which the " +"timed code is executed. Patch by Ben Roberts." +msgstr "" + +#: ../../../Misc/NEWS:5371 +msgid "" +"`Issue #22118 `__: Switch urllib.parse to use " +"RFC 3986 semantics for the resolution of relative URLs, rather than RFCs " +"1808 and 2396. Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:5375 +msgid "" +"`Issue #21549 `__: Added the \"members\" " +"parameter to TarFile.list()." +msgstr "" + +#: ../../../Misc/NEWS:5377 +msgid "" +"`Issue #19628 `__: Allow compileall recursion " +"depth to be specified with a -r option." +msgstr "" + +#: ../../../Misc/NEWS:5380 +msgid "" +"`Issue #15696 `__: Add a __sizeof__ " +"implementation for mmap objects on Windows." +msgstr "" + +#: ../../../Misc/NEWS:5382 +msgid "" +"`Issue #22068 `__: Avoided reference loops " +"with Variables and Fonts in Tkinter." +msgstr "" + +#: ../../../Misc/NEWS:5384 +msgid "" +"`Issue #22165 `__: SimpleHTTPRequestHandler " +"now supports undecodable file names." +msgstr "" + +#: ../../../Misc/NEWS:5386 +msgid "" +"`Issue #15381 `__: Optimized line reading in " +"io.BytesIO." +msgstr "" + +#: ../../../Misc/NEWS:5388 +msgid "" +"`Issue #8797 `__: Raise HTTPError on failed " +"Basic Authentication immediately. Initial patch by Sam Bull." +msgstr "" + +#: ../../../Misc/NEWS:5391 +msgid "" +"`Issue #20729 `__: Restored the use of lazy " +"iterkeys()/itervalues()/iteritems() in the mailbox module." +msgstr "" + +#: ../../../Misc/NEWS:5394 +msgid "" +"`Issue #21448 `__: Changed FeedParser feed() " +"to avoid O(N**2) behavior when parsing long line. Original patch by Raymond " +"Hettinger." +msgstr "" + +#: ../../../Misc/NEWS:5397 +msgid "" +"`Issue #22184 `__: The functools LRU Cache " +"decorator factory now gives an earlier and clearer error message when the " +"user forgets the required parameters." +msgstr "" + +#: ../../../Misc/NEWS:5400 +msgid "" +"`Issue #17923 `__: glob() patterns ending " +"with a slash no longer match non-dirs on AIX. Based on patch by Delhallt." +msgstr "" + +#: ../../../Misc/NEWS:5403 +msgid "" +"`Issue #21725 `__: Added support for RFC 6531 " +"(SMTPUTF8) in smtpd." +msgstr "" + +#: ../../../Misc/NEWS:5405 +msgid "" +"`Issue #22176 `__: Update the ctypes module's " +"libffi to v3.1. This release adds support for the Linux AArch64 and POWERPC " +"ELF ABIv2 little endian architectures." +msgstr "" + +#: ../../../Misc/NEWS:5409 +msgid "" +"`Issue #5411 `__: Added support for the \"xztar" +"\" format in the shutil module." +msgstr "" + +#: ../../../Misc/NEWS:5411 +msgid "" +"`Issue #21121 `__: Don't force 3rd party C " +"extensions to be built with -Werror=declaration-after-statement." +msgstr "" + +#: ../../../Misc/NEWS:5414 +msgid "" +"`Issue #21975 `__: Fixed crash when using " +"uninitialized sqlite3.Row (in particular when unpickling pickled sqlite3." +"Row). sqlite3.Row is now initialized in the __new__() method." +msgstr "" + +#: ../../../Misc/NEWS:5418 +msgid "" +"`Issue #20170 `__: Convert posixmodule to use " +"Argument Clinic." +msgstr "" + +#: ../../../Misc/NEWS:5420 +msgid "" +"`Issue #21539 `__: Add an *exists_ok* " +"argument to `Pathlib.mkdir()` to mimic `mkdir -p` and `os.makedirs()` " +"functionality. When true, ignore FileExistsErrors. Patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:5424 +msgid "" +"`Issue #22127 `__: Bypass IDNA for pure-ASCII " +"host names in the socket module (in particular for numeric IPs)." +msgstr "" + +#: ../../../Misc/NEWS:5427 +msgid "" +"`Issue #21047 `__: set the default value for " +"the *convert_charrefs* argument of HTMLParser to True. Patch by Berker " +"Peksag." +msgstr "" + +#: ../../../Misc/NEWS:5430 +msgid "Add an __all__ to html.entities." +msgstr "" + +#: ../../../Misc/NEWS:5432 +msgid "" +"`Issue #15114 `__: the strict mode and " +"argument of HTMLParser, HTMLParser.error, and the HTMLParserError exception " +"have been removed." +msgstr "" + +#: ../../../Misc/NEWS:5435 +msgid "" +"`Issue #22085 `__: Dropped support of Tk 8.3 " +"in Tkinter." +msgstr "" + +#: ../../../Misc/NEWS:5437 +msgid "" +"`Issue #21580 `__: Now Tkinter correctly " +"handles bytes arguments passed to Tk. In particular this allows initializing " +"images from binary data." +msgstr "" + +#: ../../../Misc/NEWS:5440 +msgid "" +"`Issue #22003 `__: When initialized from a " +"bytes object, io.BytesIO() now defers making a copy until it is mutated, " +"improving performance and memory use on some use cases. Patch by David " +"Wilson." +msgstr "" + +#: ../../../Misc/NEWS:5444 +msgid "" +"`Issue #22018 `__: On Windows, signal." +"set_wakeup_fd() now also supports sockets. A side effect is that Python " +"depends to the WinSock library." +msgstr "" + +#: ../../../Misc/NEWS:5447 +msgid "" +"`Issue #22054 `__: Add os.get_blocking() and " +"os.set_blocking() functions to get and set the blocking mode of a file " +"descriptor (False if the O_NONBLOCK flag is set, True otherwise). These " +"functions are not available on Windows." +msgstr "" + +#: ../../../Misc/NEWS:5451 +msgid "" +"`Issue #17172 `__: Make turtledemo start as " +"active on OS X even when run with subprocess. Patch by Lita Cho." +msgstr "" + +#: ../../../Misc/NEWS:5454 +msgid "" +"`Issue #21704 `__: Fix build error for " +"_multiprocessing when semaphores are not available. Patch by Arfrever " +"Frehtes Taifersar Arahesis." +msgstr "" + +#: ../../../Misc/NEWS:5457 +msgid "" +"`Issue #20173 `__: Convert sha1, sha256, " +"sha512 and md5 to ArgumentClinic. Patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:5460 +msgid "" +"Fix repr(_socket.socket) on Windows 64-bit: don't fail with OverflowError on " +"closed socket. repr(socket.socket) already works fine." +msgstr "" + +#: ../../../Misc/NEWS:5463 +msgid "" +"`Issue #22033 `__: Reprs of most Python " +"implemened classes now contain actual class name instead of hardcoded one." +msgstr "" + +#: ../../../Misc/NEWS:5466 +msgid "" +"`Issue #21947 `__: The dis module can now " +"disassemble generator-iterator objects based on their gi_code attribute. " +"Patch by Clement Rouault." +msgstr "" + +#: ../../../Misc/NEWS:5469 +msgid "" +"`Issue #16133 `__: The asynchat.async_chat." +"handle_read() method now ignores BlockingIOError exceptions." +msgstr "" + +#: ../../../Misc/NEWS:5472 +msgid "" +"`Issue #22044 `__: Fixed premature DECREF in " +"call_tzinfo_method. Patch by Tom Flanagan." +msgstr "" + +#: ../../../Misc/NEWS:5475 +msgid "" +"`Issue #19884 `__: readline: Disable the meta " +"modifier key if stdout is not a terminal to not write the ANSI sequence ``" +"\"\\033[1034h\"`` into stdout. This sequence is used on some terminal (ex: " +"TERM=xterm-256color\") to enable support of 8 bit characters." +msgstr "" + +#: ../../../Misc/NEWS:5480 +msgid "" +"`Issue #4350 `__: Removed a number of out-of-" +"dated and non-working for a long time Tkinter methods." +msgstr "" + +#: ../../../Misc/NEWS:5483 +msgid "" +"`Issue #6167 `__: Scrollbar.activate() now " +"returns the name of active element if the argument is not specified. " +"Scrollbar.set() now always accepts only 2 arguments." +msgstr "" + +#: ../../../Misc/NEWS:5487 +msgid "" +"`Issue #15275 `__: Clean up and speed up the " +"ntpath module." +msgstr "" + +#: ../../../Misc/NEWS:5489 +msgid "" +"`Issue #21888 `__: plistlib's load() and " +"loads() now work if the fmt parameter is specified." +msgstr "" + +#: ../../../Misc/NEWS:5492 +msgid "" +"`Issue #22032 `__: __qualname__ instead of " +"__name__ is now always used to format fully qualified class names of Python " +"implemented classes." +msgstr "" + +#: ../../../Misc/NEWS:5495 +msgid "" +"`Issue #22031 `__: Reprs now always use " +"hexadecimal format with the \"0x\" prefix when contain an id in form \" at " +"0x...\"." +msgstr "" + +#: ../../../Misc/NEWS:5498 +msgid "" +"`Issue #22018 `__: signal.set_wakeup_fd() now " +"raises an OSError instead of a ValueError on ``fstat()`` failure." +msgstr "" + +#: ../../../Misc/NEWS:5501 +msgid "" +"`Issue #21044 `__: tarfile.open() now handles " +"fileobj with an integer 'name' attribute. Based on patch by Antoine Pietri." +msgstr "" + +#: ../../../Misc/NEWS:5504 +msgid "" +"`Issue #21966 `__: Respect -q command-line " +"option when code module is ran." +msgstr "" + +#: ../../../Misc/NEWS:5506 +msgid "" +"`Issue #19076 `__: Don't pass the redundant " +"'file' argument to self.error()." +msgstr "" + +#: ../../../Misc/NEWS:5508 +msgid "" +"`Issue #16382 `__: Improve exception message " +"of warnings.warn() for bad category. Initial patch by Phil Elson." +msgstr "" + +#: ../../../Misc/NEWS:5511 +msgid "" +"`Issue #21932 `__: os.read() now uses a :c:" +"func:`Py_ssize_t` type instead of :c:type:`int` for the size to support " +"reading more than 2 GB at once. On Windows, the size is truncted to INT_MAX. " +"As any call to os.read(), the OS may read less bytes than the number of " +"requested bytes." +msgstr "" + +#: ../../../Misc/NEWS:5516 +msgid "" +"`Issue #21942 `__: Fixed source file viewing " +"in pydoc's server mode on Windows." +msgstr "" + +#: ../../../Misc/NEWS:5518 +msgid "" +"`Issue #11259 `__: asynchat.async_chat()." +"set_terminator() now raises a ValueError if the number of received bytes is " +"negative." +msgstr "" + +#: ../../../Misc/NEWS:5521 +msgid "" +"`Issue #12523 `__: asynchat.async_chat.push() " +"now raises a TypeError if it doesn't get a bytes string" +msgstr "" + +#: ../../../Misc/NEWS:5524 +msgid "" +"`Issue #21707 `__: Add missing kwonlyargcount " +"argument to ModuleFinder.replace_paths_in_code()." +msgstr "" + +#: ../../../Misc/NEWS:5527 +msgid "" +"`Issue #20639 `__: calling Path." +"with_suffix('') allows removing the suffix again. Patch by July Tikhonov." +msgstr "" + +#: ../../../Misc/NEWS:5530 +msgid "" +"`Issue #21714 `__: Disallow the construction " +"of invalid paths using Path.with_name(). Original patch by Antony Lee." +msgstr "" + +#: ../../../Misc/NEWS:5533 +msgid "" +"`Issue #15014 `__: Added 'auth' method to " +"smtplib to make implementing auth mechanisms simpler, and used it internally " +"in the login method." +msgstr "" + +#: ../../../Misc/NEWS:5536 +msgid "" +"`Issue #21151 `__: Fixed a segfault in the " +"winreg module when ``None`` is passed as a ``REG_BINARY`` value to " +"SetValueEx. Patch by John Ehresman." +msgstr "" + +#: ../../../Misc/NEWS:5539 +msgid "" +"`Issue #21090 `__: io.FileIO.readall() does " +"not ignore I/O errors anymore. Before, it ignored I/O errors if at least the " +"first C call read() succeed." +msgstr "" + +#: ../../../Misc/NEWS:5542 +msgid "" +"`Issue #5800 `__: headers parameter of wsgiref." +"headers.Headers is now optional. Initial patch by Pablo Torres Navarrete and " +"SilentGhost." +msgstr "" + +#: ../../../Misc/NEWS:5545 +msgid "" +"`Issue #21781 `__: ssl.RAND_add() now " +"supports strings longer than 2 GB." +msgstr "" + +#: ../../../Misc/NEWS:5547 +msgid "" +"`Issue #21679 `__: Prevent extraneous fstat() " +"calls during open(). Patch by Bohuslav Kabrda." +msgstr "" + +#: ../../../Misc/NEWS:5550 +msgid "" +"`Issue #21863 `__: cProfile now displays the " +"module name of C extension functions, in addition to their own name." +msgstr "" + +#: ../../../Misc/NEWS:5553 +msgid "" +"`Issue #11453 `__: asyncore: emit a " +"ResourceWarning when an unclosed file_wrapper object is destroyed. The " +"destructor now closes the file if needed. The close() method can now be " +"called twice: the second call does nothing." +msgstr "" + +#: ../../../Misc/NEWS:5557 +msgid "" +"`Issue #21858 `__: Better handling of Python " +"exceptions in the sqlite3 module." +msgstr "" + +#: ../../../Misc/NEWS:5559 +msgid "" +"`Issue #21476 `__: Make sure the email.parser." +"BytesParser TextIOWrapper is discarded after parsing, so the input file " +"isn't unexpectedly closed." +msgstr "" + +#: ../../../Misc/NEWS:5562 +msgid "" +"`Issue #20295 `__: imghdr now recognizes " +"OpenEXR format images." +msgstr "" + +#: ../../../Misc/NEWS:5564 +msgid "" +"`Issue #21729 `__: Used the \"with\" " +"statement in the dbm.dumb module to ensure files closing. Patch by Claudiu " +"Popa." +msgstr "" + +#: ../../../Misc/NEWS:5567 +msgid "" +"`Issue #21491 `__: socketserver: Fix a race " +"condition in child processes reaping." +msgstr "" + +#: ../../../Misc/NEWS:5569 +msgid "" +"`Issue #21719 `__: Added the " +"``st_file_attributes`` field to os.stat_result on Windows." +msgstr "" + +#: ../../../Misc/NEWS:5572 +msgid "" +"`Issue #21832 `__: Require named tuple inputs " +"to be exact strings." +msgstr "" + +#: ../../../Misc/NEWS:5574 +msgid "" +"`Issue #21722 `__: The distutils \"upload\" " +"command now exits with a non-zero return code when uploading fails. Patch " +"by Martin Dengler." +msgstr "" + +#: ../../../Misc/NEWS:5577 +msgid "" +"`Issue #21723 `__: asyncio.Queue: support any " +"type of number (ex: float) for the maximum size. Patch written by Vajrasky " +"Kok." +msgstr "" + +#: ../../../Misc/NEWS:5580 +msgid "" +"`Issue #21711 `__: support for \"site-python" +"\" directories has now been removed from the site module (it was deprecated " +"in 3.4)." +msgstr "" + +#: ../../../Misc/NEWS:5583 +msgid "" +"`Issue #17552 `__: new socket.sendfile() " +"method allowing a file to be sent over a socket by using high-performance os." +"sendfile() on UNIX. Patch by Giampaolo Rodola'." +msgstr "" + +#: ../../../Misc/NEWS:5587 +msgid "" +"`Issue #18039 `__: dbm.dump.open() now always " +"creates a new database when the flag has the value 'n'. Patch by Claudiu " +"Popa." +msgstr "" + +#: ../../../Misc/NEWS:5590 +msgid "" +"`Issue #21326 `__: Add a new is_closed() " +"method to asyncio.BaseEventLoop. run_forever() and run_until_complete() " +"methods of asyncio.BaseEventLoop now raise an exception if the event loop " +"was closed." +msgstr "" + +#: ../../../Misc/NEWS:5594 +msgid "" +"`Issue #21766 `__: Prevent a security hole in " +"CGIHTTPServer by URL unquoting paths before checking for a CGI script at " +"that path." +msgstr "" + +#: ../../../Misc/NEWS:5597 +msgid "" +"`Issue #21310 `__: Fixed possible resource " +"leak in failed open()." +msgstr "" + +#: ../../../Misc/NEWS:5599 +msgid "" +"`Issue #21256 `__: Printout of keyword args " +"should be in deterministic order in a mock function call. This will help to " +"write better doctests." +msgstr "" + +#: ../../../Misc/NEWS:5602 +msgid "" +"`Issue #21677 `__: Fixed chaining " +"nonnormalized exceptions in io close() methods." +msgstr "" + +#: ../../../Misc/NEWS:5604 +msgid "" +"`Issue #11709 `__: Fix the pydoc.help " +"function to not fail when sys.stdin is not a valid file." +msgstr "" + +#: ../../../Misc/NEWS:5607 +msgid "" +"`Issue #21515 `__: tempfile.TemporaryFile now " +"uses os.O_TMPFILE flag is available." +msgstr "" + +#: ../../../Misc/NEWS:5609 +msgid "" +"`Issue #13223 `__: Fix pydoc.writedoc so that " +"the HTML documentation for methods that use 'self' in the example code is " +"generated correctly." +msgstr "" + +#: ../../../Misc/NEWS:5612 +msgid "" +"`Issue #21463 `__: In urllib.request, fix " +"pruning of the FTP cache." +msgstr "" + +#: ../../../Misc/NEWS:5614 +msgid "" +"`Issue #21618 `__: The subprocess module " +"could fail to close open fds that were inherited by the calling process and " +"already higher than POSIX resource limits would otherwise allow. On systems " +"with a functioning /proc/self/fd or /dev/fd interface the max is now ignored " +"and all fds are closed." +msgstr "" + +#: ../../../Misc/NEWS:5619 +msgid "" +"`Issue #20383 `__: Introduce importlib.util." +"module_from_spec() as the preferred way to create a new module." +msgstr "" + +#: ../../../Misc/NEWS:5622 +msgid "" +"`Issue #21552 `__: Fixed possible integer " +"overflow of too long string lengths in the tkinter module on 64-bit " +"platforms." +msgstr "" + +#: ../../../Misc/NEWS:5625 +msgid "" +"`Issue #14315 `__: The zipfile module now " +"ignores extra fields in the central directory that are too short to be " +"parsed instead of letting a struct.unpack error bubble up as this \"bad data" +"\" appears in many real world zip files in the wild and is ignored by other " +"zip tools." +msgstr "" + +#: ../../../Misc/NEWS:5630 +msgid "" +"`Issue #13742 `__: Added \"key\" and \"reverse" +"\" parameters to heapq.merge(). (First draft of patch contributed by Simon " +"Sapin.)" +msgstr "" + +#: ../../../Misc/NEWS:5633 +msgid "" +"`Issue #21402 `__: tkinter.ttk now works when " +"default root window is not set." +msgstr "" + +#: ../../../Misc/NEWS:5635 +msgid "" +"`Issue #3015 `__: _tkinter.create() now " +"creates tkapp object with wantobject=1 by default." +msgstr "" + +#: ../../../Misc/NEWS:5638 +msgid "" +"`Issue #10203 `__: sqlite3.Row now truly " +"supports sequence protocol. In particular it supports reverse() and " +"negative indices. Original patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5641 +msgid "" +"`Issue #18807 `__: If copying (no symlinks) " +"specified for a venv, then the python interpreter aliases (python, python3) " +"are now created by copying rather than symlinking." +msgstr "" + +#: ../../../Misc/NEWS:5645 +msgid "" +"`Issue #20197 `__: Added support for the WebP " +"image type in the imghdr module. Patch by Fabrice Aneche and Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5648 +msgid "" +"`Issue #21513 `__: Speedup some properties of " +"IP addresses (IPv4Address, IPv6Address) such as .is_private or .is_multicast." +msgstr "" + +#: ../../../Misc/NEWS:5651 +msgid "" +"`Issue #21137 `__: Improve the repr for " +"threading.Lock() and its variants by showing the \"locked\" or \"unlocked\" " +"status. Patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:5654 +msgid "" +"`Issue #21538 `__: The plistlib module now " +"supports loading of binary plist files when reference or offset size is not " +"a power of two." +msgstr "" + +#: ../../../Misc/NEWS:5657 +msgid "" +"`Issue #21455 `__: Add a default backlog to " +"socket.listen()." +msgstr "" + +#: ../../../Misc/NEWS:5659 +msgid "" +"`Issue #21525 `__: Most Tkinter methods which " +"accepted tuples now accept lists too." +msgstr "" + +#: ../../../Misc/NEWS:5661 +msgid "" +"`Issue #22166 `__: With the assistance of a " +"new internal _codecs._forget_codec helping function, test_codecs now clears " +"the encoding caches to avoid the appearance of a reference leak" +msgstr "" + +#: ../../../Misc/NEWS:5665 +msgid "" +"`Issue #22236 `__: Tkinter tests now don't " +"reuse default root window. New root window is created for every test class." +msgstr "" + +#: ../../../Misc/NEWS:5668 +msgid "" +"`Issue #10744 `__: Fix PEP 3118 format " +"strings on ctypes objects with a nontrivial shape." +msgstr "" + +#: ../../../Misc/NEWS:5671 +msgid "" +"`Issue #20826 `__: Optimize ipaddress." +"collapse_addresses()." +msgstr "" + +#: ../../../Misc/NEWS:5673 +msgid "" +"`Issue #21487 `__: Optimize ipaddress." +"summarize_address_range() and ipaddress.{IPv4Network,IPv6Network}.subnets()." +msgstr "" + +#: ../../../Misc/NEWS:5676 +msgid "" +"`Issue #21486 `__: Optimize parsing of " +"netmasks in ipaddress.IPv4Network and ipaddress.IPv6Network." +msgstr "" + +#: ../../../Misc/NEWS:5679 +msgid "" +"`Issue #13916 `__: Disallowed the " +"surrogatepass error handler for non UTF-\\* encodings." +msgstr "" + +#: ../../../Misc/NEWS:5682 +msgid "" +"`Issue #20998 `__: Fixed re.fullmatch() of " +"repeated single character pattern with ignore case. Original patch by " +"Matthew Barnett." +msgstr "" + +#: ../../../Misc/NEWS:5685 +msgid "" +"`Issue #21075 `__: fileinput.FileInput now " +"reads bytes from standard stream if binary mode is specified. Patch by Sam " +"Kimbrel." +msgstr "" + +#: ../../../Misc/NEWS:5688 +msgid "" +"`Issue #19775 `__: Add a samefile() method to " +"pathlib Path objects. Initial patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:5691 +msgid "" +"`Issue #21226 `__: Set up modules properly in " +"PyImport_ExecCodeModuleObject (and friends)." +msgstr "" + +#: ../../../Misc/NEWS:5694 +msgid "" +"`Issue #21398 `__: Fix a unicode error in the " +"pydoc pager when the documentation contains characters not encodable to the " +"stdout encoding." +msgstr "" + +#: ../../../Misc/NEWS:5697 +msgid "" +"`Issue #16531 `__: ipaddress.IPv4Network and " +"ipaddress.IPv6Network now accept an (address, netmask) tuple argument, so as " +"to easily construct network objects from existing addresses." +msgstr "" + +#: ../../../Misc/NEWS:5701 +msgid "" +"`Issue #21156 `__: importlib.abc." +"InspectLoader.source_to_code() is now a staticmethod." +msgstr "" + +#: ../../../Misc/NEWS:5704 +msgid "" +"`Issue #21424 `__: Simplified and optimized " +"heaqp.nlargest() and nmsmallest() to make fewer tuple comparisons." +msgstr "" + +#: ../../../Misc/NEWS:5707 +msgid "" +"`Issue #21396 `__: Fix TextIOWrapper(..., " +"write_through=True) to not force a flush() on the underlying binary stream. " +"Patch by akira." +msgstr "" + +#: ../../../Misc/NEWS:5710 +msgid "" +"`Issue #18314 `__: Unlink now removes " +"junctions on Windows. Patch by Kim Gräsman" +msgstr "" + +#: ../../../Misc/NEWS:5712 +msgid "" +"`Issue #21088 `__: Bugfix for curses.window." +"addch() regression in 3.4.0. In porting to Argument Clinic, the first two " +"arguments were reversed." +msgstr "" + +#: ../../../Misc/NEWS:5715 +msgid "" +"`Issue #21407 `__: _decimal: The module now " +"supports function signatures." +msgstr "" + +#: ../../../Misc/NEWS:5717 +msgid "" +"`Issue #10650 `__: Remove the non-standard " +"'watchexp' parameter from the Decimal.quantize() method in the Python " +"version. It had never been present in the C version." +msgstr "" + +#: ../../../Misc/NEWS:5721 +msgid "" +"`Issue #21469 `__: Reduced the risk of false " +"positives in robotparser by checking to make sure that robots.txt has been " +"read or does not exist prior to returning True in can_fetch()." +msgstr "" + +#: ../../../Misc/NEWS:5725 +msgid "" +"`Issue #19414 `__: Have the OrderedDict mark " +"deleted links as unusable. This gives an early failure if the link is " +"deleted during iteration." +msgstr "" + +#: ../../../Misc/NEWS:5728 +msgid "" +"`Issue #21421 `__: Add __slots__ to the " +"MappingViews ABC. Patch by Josh Rosenberg." +msgstr "" + +#: ../../../Misc/NEWS:5731 +msgid "" +"`Issue #21101 `__: Eliminate double hashing " +"in the C speed-up code for collections.Counter()." +msgstr "" + +#: ../../../Misc/NEWS:5734 +msgid "" +"`Issue #21321 `__: itertools.islice() now " +"releases the reference to the source iterator when the slice is exhausted. " +"Patch by Anton Afanasyev." +msgstr "" + +#: ../../../Misc/NEWS:5737 +msgid "" +"`Issue #21057 `__: TextIOWrapper now allows " +"the underlying binary stream's read() or read1() method to return an " +"arbitrary bytes-like object (such as a memoryview). Patch by Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:5741 +msgid "" +"`Issue #20951 `__: SSLSocket.send() now " +"raises either SSLWantReadError or SSLWantWriteError on a non-blocking socket " +"if the operation would block. Previously, it would return 0. Patch by " +"Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:5745 +msgid "" +"`Issue #13248 `__: removed previously " +"deprecated asyncore.dispatcher __getattr__ cheap inheritance hack." +msgstr "" + +#: ../../../Misc/NEWS:5748 +msgid "" +"`Issue #9815 `__: assertRaises now tries to " +"clear references to local variables in the exception's traceback." +msgstr "" + +#: ../../../Misc/NEWS:5751 +msgid "" +"`Issue #19940 `__: ssl.cert_time_to_seconds() " +"now interprets the given time string in the UTC timezone (as specified in " +"RFC 5280), not the local timezone." +msgstr "" + +#: ../../../Misc/NEWS:5755 +msgid "" +"`Issue #13204 `__: Calling sys.flags.__new__ " +"would crash the interpreter, now it raises a TypeError." +msgstr "" + +#: ../../../Misc/NEWS:5758 +msgid "" +"`Issue #19385 `__: Make operations on a " +"closed dbm.dumb database always raise the same exception." +msgstr "" + +#: ../../../Misc/NEWS:5761 +msgid "" +"`Issue #21207 `__: Detect when the os.urandom " +"cached fd has been closed or replaced, and open it anew." +msgstr "" + +#: ../../../Misc/NEWS:5764 +msgid "" +"`Issue #21291 `__: subprocess's Popen.wait() " +"is now thread safe so that multiple threads may be calling wait() or poll() " +"on a Popen instance at the same time without losing the Popen.returncode " +"value." +msgstr "" + +#: ../../../Misc/NEWS:5768 +msgid "" +"`Issue #21127 `__: Path objects can now be " +"instantiated from str subclass instances (such as ``numpy.str_``)." +msgstr "" + +#: ../../../Misc/NEWS:5771 +msgid "" +"`Issue #15002 `__: urllib.response object to " +"use _TemporaryFileWrapper (and _TemporaryFileCloser) facility. Provides a " +"better way to handle file descriptor close. Patch contributed by Christian " +"Theune." +msgstr "" + +#: ../../../Misc/NEWS:5775 +msgid "" +"`Issue #12220 `__: mindom now raises a custom " +"ValueError indicating it doesn't support spaces in URIs instead of letting a " +"'split' ValueError bubble up." +msgstr "" + +#: ../../../Misc/NEWS:5778 +msgid "" +"`Issue #21068 `__: The ssl.PROTOCOL* " +"constants are now enum members." +msgstr "" + +#: ../../../Misc/NEWS:5780 +msgid "" +"`Issue #21276 `__: posixmodule: Don't define " +"USE_XATTRS on KFreeBSD and the Hurd." +msgstr "" + +#: ../../../Misc/NEWS:5782 +msgid "" +"`Issue #21262 `__: New method " +"assert_not_called for Mock. It raises AssertionError if the mock has been " +"called." +msgstr "" + +#: ../../../Misc/NEWS:5785 +msgid "" +"`Issue #21238 `__: New keyword argument " +"`unsafe` to Mock. It raises `AttributeError` incase of an attribute " +"startswith assert or assret." +msgstr "" + +#: ../../../Misc/NEWS:5788 +msgid "" +"`Issue #20896 `__: ssl." +"get_server_certificate() now uses PROTOCOL_SSLv23, not PROTOCOL_SSLv3, for " +"maximum compatibility." +msgstr "" + +#: ../../../Misc/NEWS:5791 +msgid "" +"`Issue #21239 `__: patch.stopall() didn't " +"work deterministically when the same name was patched more than once." +msgstr "" + +#: ../../../Misc/NEWS:5794 +msgid "" +"`Issue #21203 `__: Updated fileConfig and " +"dictConfig to remove inconsistencies. Thanks to Jure Koren for the patch." +msgstr "" + +#: ../../../Misc/NEWS:5797 +msgid "" +"`Issue #21222 `__: Passing name keyword " +"argument to mock.create_autospec now works." +msgstr "" + +#: ../../../Misc/NEWS:5800 +msgid "" +"`Issue #21197 `__: Add lib64 -> lib symlink " +"in venvs on 64-bit non-OS X POSIX." +msgstr "" + +#: ../../../Misc/NEWS:5802 +msgid "" +"`Issue #17498 `__: Some SMTP servers " +"disconnect after certain errors, violating strict RFC conformance. Instead " +"of losing the error code when we issue the subsequent RSET, smtplib now " +"returns the error code and defers raising the SMTPServerDisconnected error " +"until the next command is issued." +msgstr "" + +#: ../../../Misc/NEWS:5807 +msgid "" +"`Issue #17826 `__: setting an iterable " +"side_effect on a mock function created by create_autospec now works. Patch " +"by Kushal Das." +msgstr "" + +#: ../../../Misc/NEWS:5810 +msgid "" +"`Issue #7776 `__: Fix ``Host:`` header and " +"reconnection when using http.client.HTTPConnection.set_tunnel(). Patch by " +"Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:5813 +msgid "" +"`Issue #20968 `__: unittest.mock.MagicMock " +"now supports division. Patch by Johannes Baiter." +msgstr "" + +#: ../../../Misc/NEWS:5816 +msgid "" +"`Issue #21529 `__ (CVE-2014-4616): Fix " +"arbitrary memory access in JSONDecoder.raw_decode with a negative second " +"parameter. Bug reported by Guido Vranken." +msgstr "" + +#: ../../../Misc/NEWS:5820 +msgid "" +"`Issue #21169 `__: getpass now handles non-" +"ascii characters that the input stream encoding cannot encode by re-encoding " +"using the replace error handler." +msgstr "" + +#: ../../../Misc/NEWS:5824 +msgid "" +"`Issue #21171 `__: Fixed undocumented filter " +"API of the rot13 codec. Patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:5827 +msgid "" +"`Issue #20539 `__: Improved math.factorial " +"error message for large positive inputs and changed exception type " +"(OverflowError -> ValueError) for large negative inputs." +msgstr "" + +#: ../../../Misc/NEWS:5831 +msgid "" +"`Issue #21172 `__: isinstance check relaxed " +"from dict to collections.Mapping." +msgstr "" + +#: ../../../Misc/NEWS:5833 +msgid "" +"`Issue #21155 `__: asyncio.EventLoop." +"create_unix_server() now raises a ValueError if path and sock are specified " +"at the same time." +msgstr "" + +#: ../../../Misc/NEWS:5836 +msgid "" +"`Issue #21136 `__: Avoid unnecessary " +"normalization of Fractions resulting from power and other operations. Patch " +"by Raymond Hettinger." +msgstr "" + +#: ../../../Misc/NEWS:5839 +msgid "" +"`Issue #17621 `__: Introduce importlib.util." +"LazyLoader." +msgstr "" + +#: ../../../Misc/NEWS:5841 +msgid "" +"`Issue #21076 `__: signal module constants " +"were turned into enums. Patch by Giampaolo Rodola'." +msgstr "" + +#: ../../../Misc/NEWS:5844 +msgid "" +"`Issue #20636 `__: Improved the repr of " +"Tkinter widgets." +msgstr "" + +#: ../../../Misc/NEWS:5846 +msgid "" +"`Issue #19505 `__: The items, keys, and " +"values views of OrderedDict now support reverse iteration using reversed()." +msgstr "" + +#: ../../../Misc/NEWS:5849 +msgid "" +"`Issue #21149 `__: Improved thread-safety in " +"logging cleanup during interpreter shutdown. Thanks to Devin Jeanpierre for " +"the patch." +msgstr "" + +#: ../../../Misc/NEWS:5852 +msgid "" +"`Issue #21058 `__: Fix a leak of file " +"descriptor in :func:`tempfile.NamedTemporaryFile`, close the file descriptor " +"if :func:`io.open` fails" +msgstr "" + +#: ../../../Misc/NEWS:5856 +msgid "" +"`Issue #21200 `__: Return None from pkgutil." +"get_loader() when __spec__ is missing." +msgstr "" + +#: ../../../Misc/NEWS:5858 +msgid "" +"`Issue #21013 `__: Enhance ssl." +"create_default_context() when used for server side sockets to provide better " +"security by default." +msgstr "" + +#: ../../../Misc/NEWS:5861 +msgid "" +"`Issue #20145 `__: `assertRaisesRegex` and " +"`assertWarnsRegex` now raise a TypeError if the second argument is not a " +"string or compiled regex." +msgstr "" + +#: ../../../Misc/NEWS:5864 +msgid "" +"`Issue #20633 `__: Replace relative import by " +"absolute import." +msgstr "" + +#: ../../../Misc/NEWS:5866 +msgid "" +"`Issue #20980 `__: Stop wrapping exception " +"when using ThreadPool." +msgstr "" + +#: ../../../Misc/NEWS:5868 +msgid "" +"`Issue #21082 `__: In os.makedirs, do not set " +"the process-wide umask. Note this changes behavior of makedirs when " +"exist_ok=True." +msgstr "" + +#: ../../../Misc/NEWS:5871 +msgid "" +"`Issue #20990 `__: Fix issues found by " +"pyflakes for multiprocessing." +msgstr "" + +#: ../../../Misc/NEWS:5873 +msgid "" +"`Issue #21015 `__: SSL contexts will now " +"automatically select an elliptic curve for ECDH key exchange on OpenSSL " +"1.0.2 and later, and otherwise default to \"prime256v1\"." +msgstr "" + +#: ../../../Misc/NEWS:5877 +msgid "" +"`Issue #21000 `__: Improve the command-line " +"interface of json.tool." +msgstr "" + +#: ../../../Misc/NEWS:5879 +msgid "" +"`Issue #20995 `__: Enhance default ciphers " +"used by the ssl module to enable better security and prioritize perfect " +"forward secrecy." +msgstr "" + +#: ../../../Misc/NEWS:5882 +msgid "" +"`Issue #20884 `__: Don't assume that __file__ " +"is defined on importlib.__init__." +msgstr "" + +#: ../../../Misc/NEWS:5884 +msgid "" +"`Issue #21499 `__: Ignore __builtins__ in " +"several test_importlib.test_api tests." +msgstr "" + +#: ../../../Misc/NEWS:5886 +msgid "" +"`Issue #20627 `__: xmlrpc.client.ServerProxy " +"is now a context manager." +msgstr "" + +#: ../../../Misc/NEWS:5888 +msgid "" +"`Issue #19165 `__: The formatter module now " +"raises DeprecationWarning instead of PendingDeprecationWarning." +msgstr "" + +#: ../../../Misc/NEWS:5891 +msgid "" +"`Issue #13936 `__: Remove the ability of " +"datetime.time instances to be considered false in boolean contexts." +msgstr "" + +#: ../../../Misc/NEWS:5894 +msgid "" +"`Issue #18931 `__: selectors module now " +"supports /dev/poll on Solaris. Patch by Giampaolo Rodola'." +msgstr "" + +#: ../../../Misc/NEWS:5897 +msgid "" +"`Issue #19977 `__: When the ``LC_TYPE`` " +"locale is the POSIX locale (``C`` locale), :py:data:`sys.stdin` and :py:data:" +"`sys.stdout` are now using the ``surrogateescape`` error handler, instead of " +"the ``strict`` error handler." +msgstr "" + +#: ../../../Misc/NEWS:5901 +msgid "" +"`Issue #20574 `__: Implement incremental " +"decoder for cp65001 code (Windows code page 65001, Microsoft UTF-8)." +msgstr "" + +#: ../../../Misc/NEWS:5904 +msgid "" +"`Issue #20879 `__: Delay the initialization " +"of encoding and decoding tables for base32, ascii85 and base85 codecs in the " +"base64 module, and delay the initialization of the unquote_to_bytes() table " +"of the urllib.parse module, to not waste memory if these modules are not " +"used." +msgstr "" + +#: ../../../Misc/NEWS:5909 +msgid "" +"`Issue #19157 `__: Include the broadcast " +"address in the usuable hosts for IPv6 in ipaddress." +msgstr "" + +#: ../../../Misc/NEWS:5912 +msgid "" +"`Issue #11599 `__: When an external command " +"(e.g. compiler) fails, distutils now prints out the whole command line " +"(instead of just the command name) if the environment variable " +"DISTUTILS_DEBUG is set." +msgstr "" + +#: ../../../Misc/NEWS:5916 +msgid "" +"`Issue #4931 `__: distutils should not produce " +"unhelpful \"error: None\" messages anymore. distutils.util." +"grok_environment_error is kept but doc-deprecated." +msgstr "" + +#: ../../../Misc/NEWS:5919 +msgid "" +"`Issue #20875 `__: Prevent possible gzip " +"\"'read' is not defined\" NameError. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:5922 +msgid "" +"`Issue #11558 `__: ``email.message.Message." +"attach`` now returns a more useful error message if ``attach`` is called on " +"a message for which ``is_multipart`` is False." +msgstr "" + +#: ../../../Misc/NEWS:5926 +msgid "" +"`Issue #20283 `__: RE pattern methods now " +"accept the string keyword parameters as documented. The pattern and source " +"keyword parameters are left as deprecated aliases." +msgstr "" + +#: ../../../Misc/NEWS:5930 +msgid "" +"`Issue #20778 `__: Fix modulefinder to work " +"with bytecode-only modules." +msgstr "" + +#: ../../../Misc/NEWS:5932 +msgid "" +"`Issue #20791 `__: copy.copy() now doesn't " +"make a copy when the input is a bytes object. Initial patch by Peter Otten." +msgstr "" + +#: ../../../Misc/NEWS:5935 +msgid "" +"`Issue #19748 `__: On AIX, time.mktime() now " +"raises an OverflowError for year outsize range [1902; 2037]." +msgstr "" + +#: ../../../Misc/NEWS:5938 +msgid "" +"`Issue #19573 `__: inspect.signature: Use " +"enum for parameter kind constants." +msgstr "" + +#: ../../../Misc/NEWS:5940 +msgid "" +"`Issue #20726 `__: inspect.signature: Make " +"Signature and Parameter picklable." +msgstr "" + +#: ../../../Misc/NEWS:5942 +msgid "" +"`Issue #17373 `__: Add inspect.Signature." +"from_callable method." +msgstr "" + +#: ../../../Misc/NEWS:5944 +msgid "" +"`Issue #20378 `__: Improve repr of inspect." +"Signature and inspect.Parameter." +msgstr "" + +#: ../../../Misc/NEWS:5946 +msgid "" +"`Issue #20816 `__: Fix inspect.getcallargs() " +"to raise correct TypeError for missing keyword-only arguments. Patch by " +"Jeremiah Lowin." +msgstr "" + +#: ../../../Misc/NEWS:5949 +msgid "" +"`Issue #20817 `__: Fix inspect.getcallargs() " +"to fail correctly if more than 3 arguments are missing. Patch by Jeremiah " +"Lowin." +msgstr "" + +#: ../../../Misc/NEWS:5952 +msgid "" +"`Issue #6676 `__: Ensure a meaningful " +"exception is raised when attempting to parse more than one XML document per " +"pyexpat xmlparser instance. (Original patches by Hirokazu Yamamoto and " +"Amaury Forgeot d'Arc, with suggested wording by David Gutteridge)" +msgstr "" + +#: ../../../Misc/NEWS:5957 +msgid "" +"`Issue #21117 `__: Fix inspect.signature to " +"better support functools.partial. Due to the specifics of functools.partial " +"implementation, positional-or-keyword arguments passed as keyword arguments " +"become keyword-only." +msgstr "" + +#: ../../../Misc/NEWS:5962 +msgid "" +"`Issue #20334 `__: inspect.Signature and " +"inspect.Parameter are now hashable. Thanks to Antony Lee for bug reports and " +"suggestions." +msgstr "" + +#: ../../../Misc/NEWS:5965 +msgid "" +"`Issue #15916 `__: doctest.DocTestSuite " +"returns an empty unittest.TestSuite instead of raising ValueError if it " +"finds no tests" +msgstr "" + +#: ../../../Misc/NEWS:5968 +msgid "" +"`Issue #21209 `__: Fix asyncio.tasks." +"CoroWrapper to workaround a bug in yield-from implementation in CPythons " +"prior to 3.4.1." +msgstr "" + +#: ../../../Misc/NEWS:5971 +msgid "" +"asyncio: Add gi_{frame,running,code} properties to CoroWrapper (upstream " +"`issue #163 `__)." +msgstr "" + +#: ../../../Misc/NEWS:5974 +msgid "" +"`Issue #21311 `__: Avoid exception in " +"_osx_support with non-standard compiler configurations. Patch by John " +"Szakmeister." +msgstr "" + +#: ../../../Misc/NEWS:5977 +msgid "" +"`Issue #11571 `__: Ensure that the turtle " +"window becomes the topmost window when launched on OS X." +msgstr "" + +#: ../../../Misc/NEWS:5980 +msgid "" +"`Issue #21801 `__: Validate that " +"__signature__ is None or an instance of Signature." +msgstr "" + +#: ../../../Misc/NEWS:5982 +msgid "" +"`Issue #21923 `__: Prevent AttributeError in " +"distutils.sysconfig.customize_compiler due to possible uninitialized " +"_config_vars." +msgstr "" + +#: ../../../Misc/NEWS:5985 +msgid "" +"`Issue #21323 `__: Fix http.server to again " +"handle scripts in CGI subdirectories, broken by the fix for security `issue " +"#19435 `__. Patch by Zach Byrne." +msgstr "" + +#: ../../../Misc/NEWS:5988 +msgid "" +"`Issue #22733 `__: Fix ffi_prep_args not zero-" +"extending argument values correctly on 64-bit Windows." +msgstr "" + +#: ../../../Misc/NEWS:5991 +msgid "" +"`Issue #23302 `__: Default to TCP_NODELAY=1 " +"upon establishing an HTTPConnection. Removed use of hard-coded MSS as it's " +"an optimization that's no longer needed with Nagle disabled." +msgstr "" + +#: ../../../Misc/NEWS:5998 +msgid "" +"`Issue #20577 `__: Configuration of the max " +"line length for the FormatParagraph extension has been moved from the " +"General tab of the Idle preferences dialog to the FormatParagraph tab of the " +"Config Extensions dialog. Patch by Tal Einat." +msgstr "" + +#: ../../../Misc/NEWS:6003 +msgid "" +"`Issue #16893 `__: Update Idle doc chapter to " +"match current Idle and add new information." +msgstr "" + +#: ../../../Misc/NEWS:6006 +msgid "" +"`Issue #3068 `__: Add Idle extension " +"configuration dialog to Options menu. Changes are written to HOME/.idlerc/" +"config-extensions.cfg. Original patch by Tal Einat." +msgstr "" + +#: ../../../Misc/NEWS:6010 +msgid "" +"`Issue #16233 `__: A module browser (File : " +"Class Browser, Alt+C) requires an editor window with a filename. When Class " +"Browser is requested otherwise, from a shell, output window, or 'Untitled' " +"editor, Idle no longer displays an error box. It now pops up an Open Module " +"box (Alt+M). If a valid name is entered and a module is opened, a " +"corresponding browser is also opened." +msgstr "" + +#: ../../../Misc/NEWS:6016 +msgid "" +"`Issue #4832 `__: Save As to type Python files " +"automatically adds .py to the name you enter (even if your system does not " +"display it). Some systems automatically add .txt when type is Text files." +msgstr "" + +#: ../../../Misc/NEWS:6020 +msgid "" +"`Issue #21986 `__: Code objects are not " +"normally pickled by the pickle module. To match this, they are no longer " +"pickled when running under Idle." +msgstr "" + +#: ../../../Misc/NEWS:6023 +msgid "" +"`Issue #17390 `__: Adjust Editor window " +"title; remove 'Python', move version to end." +msgstr "" + +#: ../../../Misc/NEWS:6026 +msgid "" +"`Issue #14105 `__: Idle debugger breakpoints " +"no longer disappear when inserting or deleting lines." +msgstr "" + +#: ../../../Misc/NEWS:6029 +msgid "" +"`Issue #17172 `__: Turtledemo can now be run " +"from Idle. Currently, the entry is on the Help menu, but it may move to Run. " +"Patch by Ramchandra Apt and Lita Cho." +msgstr "" + +#: ../../../Misc/NEWS:6033 +msgid "" +"`Issue #21765 `__: Add support for non-ascii " +"identifiers to HyperParser." +msgstr "" + +#: ../../../Misc/NEWS:6035 +msgid "" +"`Issue #21940 `__: Add unittest for " +"WidgetRedirector. Initial patch by Saimadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:6038 +msgid "" +"`Issue #18592 `__: Add unittest for " +"SearchDialogBase. Patch by Phil Webster." +msgstr "" + +#: ../../../Misc/NEWS:6040 +msgid "" +"`Issue #21694 `__: Add unittest for " +"ParenMatch. Patch by Saimadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:6042 +msgid "" +"`Issue #21686 `__: add unittest for " +"HyperParser. Original patch by Saimadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:6045 +msgid "" +"`Issue #12387 `__: Add missing " +"upper(lower)case versions of default Windows key bindings for Idle so Caps " +"Lock does not disable them. Patch by Roger Serwy." +msgstr "" + +#: ../../../Misc/NEWS:6048 +msgid "" +"`Issue #21695 `__: Closing a Find-in-files " +"output window while the search is still in progress no longer closes Idle." +msgstr "" + +#: ../../../Misc/NEWS:6051 +msgid "" +"`Issue #18910 `__: Add unittest for textView. " +"Patch by Phil Webster." +msgstr "" + +#: ../../../Misc/NEWS:6053 +msgid "" +"`Issue #18292 `__: Add unittest for " +"AutoExpand. Patch by Saihadhav Heblikar." +msgstr "" + +#: ../../../Misc/NEWS:6055 +msgid "" +"`Issue #18409 `__: Add unittest for " +"AutoComplete. Patch by Phil Webster." +msgstr "" + +#: ../../../Misc/NEWS:6057 +msgid "" +"`Issue #21477 `__: htest.py - Improve " +"framework, complete set of tests. Patches by Saimadhav Heblikar" +msgstr "" + +#: ../../../Misc/NEWS:6060 +msgid "" +"`Issue #18104 `__: Add idlelib/idle_test/" +"htest.py with a few sample tests to begin consolidating and improving human-" +"validated tests of Idle. Change other files as needed to work with htest. " +"Running the module as __main__ runs all tests." +msgstr "" + +#: ../../../Misc/NEWS:6064 +msgid "" +"`Issue #21139 `__: Change default paragraph " +"width to 72, the PEP 8 recommendation." +msgstr "" + +#: ../../../Misc/NEWS:6066 +msgid "" +"`Issue #21284 `__: Paragraph reformat test " +"passes after user changes reformat width." +msgstr "" + +#: ../../../Misc/NEWS:6068 +msgid "" +"`Issue #17654 `__: Ensure IDLE menus are " +"customized properly on OS X for non-framework builds and for all variants of " +"Tk." +msgstr "" + +#: ../../../Misc/NEWS:6071 +msgid "" +"`Issue #23180 `__: Rename IDLE \"Windows\" " +"menu item to \"Window\". Patch by Al Sweigart." +msgstr "" + +#: ../../../Misc/NEWS:6077 +msgid "" +"`Issue #15506 `__: Use standard " +"PKG_PROG_PKG_CONFIG autoconf macro in the configure script." +msgstr "" + +#: ../../../Misc/NEWS:6080 +msgid "" +"`Issue #22935 `__: Allow the ssl module to be " +"compiled if openssl doesn't support SSL 3." +msgstr "" + +#: ../../../Misc/NEWS:6083 +msgid "" +"`Issue #22592 `__: Drop support of the " +"Borland C compiler to build Python. The distutils module still supports it " +"to build extensions." +msgstr "" + +#: ../../../Misc/NEWS:6086 +msgid "" +"`Issue #22591 `__: Drop support of MS-DOS, " +"especially of the DJGPP compiler (MS-DOS port of GCC)." +msgstr "" + +#: ../../../Misc/NEWS:6089 +msgid "" +"`Issue #16537 `__: Check whether self." +"extensions is empty in setup.py. Patch by Jonathan Hosmer." +msgstr "" + +#: ../../../Misc/NEWS:6092 +msgid "" +"`Issue #22359 `__: Remove incorrect uses of " +"recursive make. Patch by Jonas Wagner." +msgstr "" + +#: ../../../Misc/NEWS:6095 +msgid "" +"`Issue #21958 `__: Define HAVE_ROUND when " +"building with Visual Studio 2013 and above. Patch by Zachary Turner." +msgstr "" + +#: ../../../Misc/NEWS:6098 +msgid "" +"`Issue #18093 `__: the programs that embed " +"the CPython runtime are now in a separate \"Programs\" directory, rather " +"than being kept in the Modules directory." +msgstr "" + +#: ../../../Misc/NEWS:6102 +msgid "" +"`Issue #15759 `__: \"make suspicious\", " +"\"make linkcheck\" and \"make doctest\" in Doc/ now display special message " +"when and only when there are failures." +msgstr "" + +#: ../../../Misc/NEWS:6105 +msgid "" +"`Issue #21141 `__: The Windows build process " +"no longer attempts to find Perl, instead relying on OpenSSL source being " +"configured and ready to build. The ``PCbuild\\build_ssl.py`` script has " +"been re-written and re-named to ``PCbuild\\prepare_ssl.py``, and takes care " +"of configuring OpenSSL source for both 32 and 64 bit platforms. OpenSSL " +"sources obtained from svn.python.org will always be pre-configured and ready " +"to build." +msgstr "" + +#: ../../../Misc/NEWS:6112 +msgid "" +"`Issue #21037 `__: Add a build option to " +"enable AddressSanitizer support." +msgstr "" + +#: ../../../Misc/NEWS:6114 +msgid "" +"`Issue #19962 `__: The Windows build process " +"now creates \"python.bat\" in the root of the source tree, which passes all " +"arguments through to the most recently built interpreter." +msgstr "" + +#: ../../../Misc/NEWS:6118 +msgid "" +"`Issue #21285 `__: Refactor and fix curses " +"configure check to always search in a ncursesw directory." +msgstr "" + +#: ../../../Misc/NEWS:6121 +msgid "" +"`Issue #15234 `__: For BerkelyDB and Sqlite, " +"only add the found library and include directories if they aren't already " +"being searched. This avoids an explicit runtime library dependency." +msgstr "" + +#: ../../../Misc/NEWS:6125 +msgid "" +"`Issue #17861 `__: Tools/scripts/" +"generate_opcode_h.py automatically regenerates Include/opcode.h from Lib/" +"opcode.py if the latter gets any change." +msgstr "" + +#: ../../../Misc/NEWS:6128 +msgid "" +"`Issue #20644 `__: OS X installer build " +"support for documentation build changes in 3.4.1: assume externally supplied " +"sphinx-build is available in /usr/bin." +msgstr "" + +#: ../../../Misc/NEWS:6131 +msgid "" +"`Issue #20022 `__: Eliminate use of " +"deprecated bundlebuilder in OS X builds." +msgstr "" + +#: ../../../Misc/NEWS:6133 +msgid "" +"`Issue #15968 `__: Incorporated Tcl, Tk, and " +"Tix builds into the Windows build solution." +msgstr "" + +#: ../../../Misc/NEWS:6136 +msgid "" +"`Issue #17095 `__: Fix Modules/Setup *shared* " +"support." +msgstr "" + +#: ../../../Misc/NEWS:6138 +msgid "" +"`Issue #21811 `__: Anticipated fixes to " +"support OS X versions > 10.9." +msgstr "" + +#: ../../../Misc/NEWS:6140 +msgid "" +"`Issue #21166 `__: Prevent possible segfaults " +"and other random failures of python --generate-posix-vars in pybuilddir.txt " +"build target." +msgstr "" + +#: ../../../Misc/NEWS:6143 +msgid "" +"`Issue #18096 `__: Fix library order returned " +"by python-config." +msgstr "" + +#: ../../../Misc/NEWS:6145 +msgid "" +"`Issue #17219 `__: Add library build dir for " +"Python extension cross-builds." +msgstr "" + +#: ../../../Misc/NEWS:6147 +msgid "" +"`Issue #22919 `__: Windows build updated to " +"support VC 14.0 (Visual Studio 2015), which will be used for the official " +"release." +msgstr "" + +#: ../../../Misc/NEWS:6150 +msgid "" +"`Issue #21236 `__: Build _msi.pyd with " +"cabinet.lib instead of fci.lib" +msgstr "" + +#: ../../../Misc/NEWS:6152 +msgid "" +"`Issue #17128 `__: Use private version of " +"OpenSSL for OS X 10.5+ installer." +msgstr "" + +#: ../../../Misc/NEWS:6157 +msgid "" +"`Issue #14203 `__: Remove obsolete support " +"for view==NULL in PyBuffer_FillInfo(), bytearray_getbuffer(), " +"bytesiobuf_getbuffer() and array_buffer_getbuf(). All functions now raise " +"BufferError in that case." +msgstr "" + +#: ../../../Misc/NEWS:6161 +msgid "" +"`Issue #22445 `__: PyBuffer_IsContiguous() " +"now implements precise contiguity tests, compatible with NumPy's " +"NPY_RELAXED_STRIDES_CHECKING compilation flag. Previously the function " +"reported false negatives for corner cases." +msgstr "" + +#: ../../../Misc/NEWS:6165 +msgid "" +"`Issue #22079 `__: PyType_Ready() now checks " +"that statically allocated type has no dynamically allocated bases." +msgstr "" + +#: ../../../Misc/NEWS:6168 +msgid "" +"`Issue #22453 `__: Removed non-documented " +"macro PyObject_REPR()." +msgstr "" + +#: ../../../Misc/NEWS:6170 +msgid "" +"`Issue #18395 `__: Rename " +"``_Py_char2wchar()`` to :c:func:`Py_DecodeLocale`, rename " +"``_Py_wchar2char()`` to :c:func:`Py_EncodeLocale`, and document these " +"functions." +msgstr "" + +#: ../../../Misc/NEWS:6174 +msgid "" +"`Issue #21233 `__: Add new C functions: " +"PyMem_RawCalloc(), PyMem_Calloc(), PyObject_Calloc(), _PyObject_GC_Calloc(). " +"bytes(int) is now using ``calloc()`` instead of ``malloc()`` for large " +"objects which is faster and use less memory." +msgstr "" + +#: ../../../Misc/NEWS:6179 +msgid "" +"`Issue #20942 `__: " +"PyImport_ImportFrozenModuleObject() no longer sets __file__ to match what " +"importlib does; this affects _frozen_importlib as well as any module loaded " +"using imp.init_frozen()." +msgstr "" + +#: ../../../Misc/NEWS:6186 +msgid "" +"`Issue #19548 `__: Update the codecs module " +"documentation to better cover the distinction between text encodings and " +"other codecs, together with other clarifications. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:6190 +msgid "" +"`Issue #22394 `__: Doc/Makefile now supports " +"``make venv PYTHON=../python`` to create a venv for generating the " +"documentation, e.g., ``make html PYTHON=venv/bin/python3``." +msgstr "" + +#: ../../../Misc/NEWS:6194 +msgid "" +"`Issue #21514 `__: The documentation of the " +"json module now refers to new JSON RFC 7159 instead of obsoleted RFC 4627." +msgstr "" + +#: ../../../Misc/NEWS:6197 +msgid "" +"`Issue #21777 `__: The binary sequence " +"methods on bytes and bytearray are now documented explicitly, rather than " +"assuming users will be able to derive the expected behaviour from the " +"behaviour of the corresponding str methods." +msgstr "" + +#: ../../../Misc/NEWS:6201 +msgid "" +"`Issue #6916 `__: undocument deprecated " +"asynchat.fifo class." +msgstr "" + +#: ../../../Misc/NEWS:6203 +msgid "" +"`Issue #17386 `__: Expanded functionality of " +"the ``Doc/make.bat`` script to make it much more comparable to ``Doc/" +"Makefile``." +msgstr "" + +#: ../../../Misc/NEWS:6206 +msgid "" +"`Issue #21312 `__: Update the thread_foobar.h " +"template file to include newer threading APIs. Patch by Jack McCracken." +msgstr "" + +#: ../../../Misc/NEWS:6209 +msgid "" +"`Issue #21043 `__: Remove the recommendation " +"for specific CA organizations and to mention the ability to load the OS " +"certificates." +msgstr "" + +#: ../../../Misc/NEWS:6212 +msgid "" +"`Issue #20765 `__: Add missing documentation " +"for PurePath.with_name() and PurePath.with_suffix()." +msgstr "" + +#: ../../../Misc/NEWS:6215 +msgid "" +"`Issue #19407 `__: New package installation " +"and distribution guides based on the Python Packaging Authority tools. " +"Existing guides have been retained as legacy links from the distutils docs, " +"as they still contain some required reference material for tool developers " +"that isn't recorded anywhere else." +msgstr "" + +#: ../../../Misc/NEWS:6221 +msgid "" +"`Issue #19697 `__: Document cases where " +"__main__.__spec__ is None." +msgstr "" + +#: ../../../Misc/NEWS:6226 +msgid "" +"`Issue #18982 `__: Add tests for CLI of the " +"calendar module." +msgstr "" + +#: ../../../Misc/NEWS:6228 +msgid "" +"`Issue #19548 `__: Added some additional " +"checks to test_codecs to ensure that statements in the updated documentation " +"remain accurate. Patch by Martin Panter." +msgstr "" + +#: ../../../Misc/NEWS:6232 +msgid "" +"`Issue #22838 `__: All test_re tests now work " +"with unittest test discovery." +msgstr "" + +#: ../../../Misc/NEWS:6234 +msgid "" +"`Issue #22173 `__: Update lib2to3 tests to " +"use unittest test discovery." +msgstr "" + +#: ../../../Misc/NEWS:6236 +msgid "" +"`Issue #16000 `__: Convert test_curses to use " +"unittest." +msgstr "" + +#: ../../../Misc/NEWS:6238 +msgid "" +"`Issue #21456 `__: Skip two tests in " +"test_urllib2net.py if _ssl module not present. Patch by Remi Pointel." +msgstr "" + +#: ../../../Misc/NEWS:6241 +msgid "" +"`Issue #20746 `__: Fix test_pdb to run in " +"refleak mode (-R). Patch by Xavier de Gaye." +msgstr "" + +#: ../../../Misc/NEWS:6244 +msgid "" +"`Issue #22060 `__: test_ctypes has been " +"somewhat cleaned up and simplified; it now uses unittest test discovery to " +"find its tests." +msgstr "" + +#: ../../../Misc/NEWS:6247 +msgid "" +"`Issue #22104 `__: regrtest.py no longer " +"holds a reference to the suite of tests loaded from test modules that don't " +"define test_main()." +msgstr "" + +#: ../../../Misc/NEWS:6250 +msgid "" +"`Issue #22111 `__: Assorted cleanups in " +"test_imaplib. Patch by Milan Oberkirch." +msgstr "" + +#: ../../../Misc/NEWS:6252 +msgid "" +"`Issue #22002 `__: Added " +"``load_package_tests`` function to test.support and used it to implement/" +"augment test discovery in test_asyncio, test_email, test_importlib, " +"test_json, and test_tools." +msgstr "" + +#: ../../../Misc/NEWS:6256 +msgid "" +"`Issue #21976 `__: Fix test_ssl to accept " +"LibreSSL version strings. Thanks to William Orr." +msgstr "" + +#: ../../../Misc/NEWS:6259 +msgid "" +"`Issue #21918 `__: Converted test_tools from " +"a module to a package containing separate test files for each tested script." +msgstr "" + +#: ../../../Misc/NEWS:6262 +msgid "" +"`Issue #9554 `__: Use modern unittest features " +"in test_argparse. Initial patch by Denver Coneybeare and Radu Voicilas." +msgstr "" + +#: ../../../Misc/NEWS:6265 +msgid "" +"`Issue #20155 `__: Changed HTTP method names " +"in failing tests in test_httpservers so that packet filtering software " +"(specifically Windows Base Filtering Engine) does not interfere with the " +"transaction semantics expected by the tests." +msgstr "" + +#: ../../../Misc/NEWS:6269 +msgid "" +"`Issue #19493 `__: Refactored the ctypes test " +"package to skip tests explicitly rather than silently." +msgstr "" + +#: ../../../Misc/NEWS:6272 +msgid "" +"`Issue #18492 `__: All resources are now " +"allowed when tests are not run by regrtest.py." +msgstr "" + +#: ../../../Misc/NEWS:6275 +msgid "" +"`Issue #21634 `__: Fix pystone micro-" +"benchmark: use floor division instead of true division to benchmark integers " +"instead of floating point numbers. Set pystone version to 1.2. Patch written " +"by Lennart Regebro." +msgstr "" + +#: ../../../Misc/NEWS:6279 +msgid "" +"`Issue #21605 `__: Added tests for Tkinter " +"images." +msgstr "" + +#: ../../../Misc/NEWS:6281 +msgid "" +"`Issue #21493 `__: Added test for ntpath." +"expanduser(). Original patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:6284 +msgid "" +"`Issue #19925 `__: Added tests for the spwd " +"module. Original patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:6286 +msgid "" +"`Issue #21522 `__: Added Tkinter tests for " +"Listbox.itemconfigure(), PanedWindow.paneconfigure(), and Menu." +"entryconfigure()." +msgstr "" + +#: ../../../Misc/NEWS:6289 +msgid "" +"`Issue #17756 `__: Fix test_code test when " +"run from the installed location." +msgstr "" + +#: ../../../Misc/NEWS:6291 +msgid "" +"`Issue #17752 `__: Fix distutils tests when " +"run from the installed location." +msgstr "" + +#: ../../../Misc/NEWS:6293 +msgid "" +"`Issue #18604 `__: Consolidated checks for " +"GUI availability. All platforms now at least check whether Tk can be " +"instantiated when the GUI resource is requested." +msgstr "" + +#: ../../../Misc/NEWS:6297 +msgid "" +"`Issue #21275 `__: Fix a socket test on " +"KFreeBSD." +msgstr "" + +#: ../../../Misc/NEWS:6299 +msgid "" +"`Issue #21223 `__: Pass test_site/" +"test_startup_imports when some of the extensions are built as builtins." +msgstr "" + +#: ../../../Misc/NEWS:6302 +msgid "" +"`Issue #20635 `__: Added tests for Tk " +"geometry managers." +msgstr "" + +#: ../../../Misc/NEWS:6304 +msgid "Add test case for freeze." +msgstr "" + +#: ../../../Misc/NEWS:6306 +msgid "" +"`Issue #20743 `__: Fix a reference leak in " +"test_tcl." +msgstr "" + +#: ../../../Misc/NEWS:6308 +msgid "" +"`Issue #21097 `__: Move test_namespace_pkgs " +"into test_importlib." +msgstr "" + +#: ../../../Misc/NEWS:6310 +msgid "" +"`Issue #21503 `__: Use test_both() " +"consistently in test_importlib." +msgstr "" + +#: ../../../Misc/NEWS:6312 +msgid "" +"`Issue #20939 `__: Avoid various network test " +"failures due to new redirect of http://www.python.org/ to https://www.python." +"org: use http://www.example.com instead." +msgstr "" + +#: ../../../Misc/NEWS:6316 +msgid "" +"`Issue #20668 `__: asyncio tests no longer " +"rely on tests.txt file. (Patch by Vajrasky Kok)" +msgstr "" + +#: ../../../Misc/NEWS:6319 +msgid "" +"`Issue #21093 `__: Prevent failures of ctypes " +"test_macholib on OS X if a copy of libz exists in $HOME/lib or /usr/local/" +"lib." +msgstr "" + +#: ../../../Misc/NEWS:6322 +msgid "" +"`Issue #22770 `__: Prevent some Tk segfaults " +"on OS X when running gui tests." +msgstr "" + +#: ../../../Misc/NEWS:6324 +msgid "" +"`Issue #23211 `__: Workaround test_logging " +"failure on some OS X 10.6 systems." +msgstr "" + +#: ../../../Misc/NEWS:6326 +msgid "" +"`Issue #23345 `__: Prevent test_ssl failures " +"with large OpenSSL patch level values (like 0.9.8zc)." +msgstr "" + +#: ../../../Misc/NEWS:6332 +msgid "" +"`Issue #22314 `__: pydoc now works when the " +"LINES environment variable is set." +msgstr "" + +#: ../../../Misc/NEWS:6334 +msgid "" +"`Issue #22615 `__: Argument Clinic now " +"supports the \"type\" argument for the int converter. This permits using " +"the int converter with enums and typedefs." +msgstr "" + +#: ../../../Misc/NEWS:6338 +msgid "" +"`Issue #20076 `__: The makelocalealias.py " +"script no longer ignores UTF-8 mapping." +msgstr "" + +#: ../../../Misc/NEWS:6340 +msgid "" +"`Issue #20079 `__: The makelocalealias.py " +"script now can parse the SUPPORTED file from glibc sources and supports " +"command line options for source paths." +msgstr "" + +#: ../../../Misc/NEWS:6343 +msgid "" +"`Issue #22201 `__: Command-line interface of " +"the zipfile module now correctly extracts ZIP files with directory entries. " +"Patch by Ryan Wilson." +msgstr "" + +#: ../../../Misc/NEWS:6346 +msgid "" +"`Issue #22120 `__: For functions using an " +"unsigned integer return converter, Argument Clinic now generates a cast to " +"that type for the comparison to -1 in the generated code. (This suppresses " +"a compilation warning.)" +msgstr "" + +#: ../../../Misc/NEWS:6350 +msgid "" +"`Issue #18974 `__: Tools/scripts/diff.py now " +"uses argparse instead of optparse." +msgstr "" + +#: ../../../Misc/NEWS:6352 +msgid "" +"`Issue #21906 `__: Make Tools/scripts/md5sum." +"py work in Python 3. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:6355 +msgid "" +"`Issue #21629 `__: Fix Argument Clinic's \"--" +"converters\" feature." +msgstr "" + +#: ../../../Misc/NEWS:6357 +msgid "Add support for ``yield from`` to 2to3." +msgstr "" + +#: ../../../Misc/NEWS:6359 +msgid "Add support for the PEP 465 matrix multiplication operator to 2to3." +msgstr "" + +#: ../../../Misc/NEWS:6361 +msgid "" +"`Issue #16047 `__: Fix module exception list " +"and __file__ handling in freeze. Patch by Meador Inge." +msgstr "" + +#: ../../../Misc/NEWS:6364 +msgid "" +"`Issue #11824 `__: Consider ABI tags in " +"freeze. Patch by Meador Inge." +msgstr "" + +#: ../../../Misc/NEWS:6366 +msgid "" +"`Issue #20535 `__: PYTHONWARNING no longer " +"affects the run_tests.py script. Patch by Arfrever Frehtes Taifersar " +"Arahesis." +msgstr "" + +#: ../../../Misc/NEWS:6372 +msgid "" +"`Issue #23260 `__: Update Windows installer" +msgstr "" + +#: ../../../Misc/NEWS:6374 +msgid "" +"The bundled version of Tcl/Tk has been updated to 8.6.3. The most visible " +"result of this change is the addition of new native file dialogs when " +"running on Windows Vista or newer. See Tcl/Tk's TIP 432 for more " +"information. Also, this version of Tcl/Tk includes support for Windows 10." +msgstr "" + +#: ../../../Misc/NEWS:6379 +msgid "" +"`Issue #17896 `__: The Windows build scripts " +"now expect external library sources to be in ``PCbuild\\..\\externals`` " +"rather than ``PCbuild\\..\\..``." +msgstr "" + +#: ../../../Misc/NEWS:6382 +msgid "" +"`Issue #17717 `__: The Windows build scripts " +"now use a copy of NASM pulled from svn.python.org to build OpenSSL." +msgstr "" + +#: ../../../Misc/NEWS:6385 +msgid "" +"`Issue #21907 `__: Improved the batch scripts " +"provided for building Python." +msgstr "" + +#: ../../../Misc/NEWS:6387 +msgid "" +"`Issue #22644 `__: The bundled version of " +"OpenSSL has been updated to 1.0.1j." +msgstr "" + +#: ../../../Misc/NEWS:6389 +msgid "" +"`Issue #10747 `__: Use versioned labels in " +"the Windows start menu. Patch by Olive Kilburn." +msgstr "" + +#: ../../../Misc/NEWS:6392 +msgid "" +"`Issue #22980 `__: .pyd files with a version " +"and platform tag (for example, \".cp35-win32.pyd\") will now be loaded in " +"preference to those without tags." +msgstr "" + +#: ../../../Misc/NEWS:6397 +msgid "Python 3.4.0" +msgstr "" + +#: ../../../Misc/NEWS:6399 +msgid "Release date: 2014-03-16" +msgstr "" + +#: ../../../Misc/NEWS:6404 +msgid "" +"`Issue #20939 `__: Fix test_geturl failure in " +"test_urllibnet due to new redirect of http://www.python.org/ to https://www." +"python.org." +msgstr "" + +#: ../../../Misc/NEWS:6410 +msgid "Merge in all documentation changes since branching 3.4.0rc1." +msgstr "" + +#: ../../../Misc/NEWS:6414 +msgid "Python 3.4.0 release candidate 3" +msgstr "" + +#: ../../../Misc/NEWS:6416 +msgid "Release date: 2014-03-09" +msgstr "" + +#: ../../../Misc/NEWS:6421 +msgid "" +"`Issue #20786 `__: Fix signatures for dict." +"__delitem__ and property.__delete__ builtins." +msgstr "" + +#: ../../../Misc/NEWS:6427 +msgid "" +"`Issue #20839 `__: Don't trigger a " +"DeprecationWarning in the still supported pkgutil.get_loader() API when " +"__loader__ isn't set on a module (nor when pkgutil.find_loader() is called " +"directly)." +msgstr "" + +#: ../../../Misc/NEWS:6434 +msgid "" +"`Issue #14512 `__: Launch pydoc -b instead of " +"pydocgui.pyw on Windows." +msgstr "" + +#: ../../../Misc/NEWS:6436 +msgid "" +"`Issue #20748 `__: Uninstalling pip does not " +"leave behind the pyc of the uninstaller anymore." +msgstr "" + +#: ../../../Misc/NEWS:6439 +msgid "" +"`Issue #20568 `__: The Windows installer now " +"installs the unversioned ``pip`` command in addition to the versioned " +"``pip3`` and ``pip3.4`` commands." +msgstr "" + +#: ../../../Misc/NEWS:6442 +msgid "" +"`Issue #20757 `__: The ensurepip helper for " +"the Windows uninstaller now skips uninstalling pip (rather than failing) if " +"the user has updated pip to a different version from the one bundled with " +"ensurepip." +msgstr "" + +#: ../../../Misc/NEWS:6446 +msgid "" +"`Issue #20465 `__: Update OS X and Windows " +"installer builds to use SQLite 3.8.3.1." +msgstr "" + +#: ../../../Misc/NEWS:6451 +msgid "Python 3.4.0 release candidate 2" +msgstr "" + +#: ../../../Misc/NEWS:6453 +msgid "Release date: 2014-02-23" +msgstr "" + +#: ../../../Misc/NEWS:6458 +msgid "" +"`Issue #20625 `__: Parameter names in " +"__annotations__ were not mangled properly. Discovered by Jonas Wielicki, " +"patch by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:6461 +msgid "" +"`Issue #20261 `__: In pickle, lookup " +"__getnewargs__ and __getnewargs_ex__ on the type of the object." +msgstr "" + +#: ../../../Misc/NEWS:6464 +msgid "" +"`Issue #20619 `__: Give the AST nodes of " +"keyword-only arguments a column and line number." +msgstr "" + +#: ../../../Misc/NEWS:6467 +msgid "" +"`Issue #20526 `__: Revert changes of `issue " +"#19466 `__ which introduces a regression: " +"don't clear anymore the state of Python threads early during the Python " +"shutdown." +msgstr "" + +#: ../../../Misc/NEWS:6474 +msgid "" +"`Issue #20710 `__: The pydoc summary line no " +"longer displays the \"self\" parameter for bound methods." +msgstr "" + +#: ../../../Misc/NEWS:6477 +msgid "" +"`Issue #20566 `__: Change asyncio." +"as_completed() to use a Queue, to avoid O(N**2) behavior." +msgstr "" + +#: ../../../Misc/NEWS:6480 +msgid "" +"`Issue #20704 `__: Implement new debug API in " +"asyncio. Add new methods BaseEventLoop.set_debug() and BaseEventLoop." +"get_debug(). Add support for setting 'asyncio.tasks._DEBUG' variable with " +"'PYTHONASYNCIODEBUG' environment variable." +msgstr "" + +#: ../../../Misc/NEWS:6485 +msgid "" +"asyncio: Refactoring and fixes: BaseEventLoop.sock_connect() raises an error " +"if the address is not resolved; use __slots__ in Handle and TimerHandle; " +"as_completed() and wait() raise TypeError if the passed list of Futures is a " +"single Future; call_soon() and other 'call_*()' functions raise TypeError if " +"the passed callback is a coroutine function; _ProactorBasePipeTransport uses " +"_FlowControlMixin; WriteTransport.set_write_buffer_size() calls " +"_maybe_pause_protocol() to consider pausing receiving if the watermark " +"limits have changed; fix _check_resolved_address() for IPv6 address; and " +"other minor improvements, along with multiple documentation updates." +msgstr "" + +#: ../../../Misc/NEWS:6496 +msgid "" +"`Issue #20684 `__: Fix inspect." +"getfullargspec() to not to follow __wrapped__ chains. Make its behaviour " +"consistent with bound methods first argument. Patch by Nick Coghlan and Yury " +"Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:6500 +msgid "" +"`Issue #20681 `__: Add new error handling API " +"in asyncio. New APIs: loop.set_exception_handler(), loop." +"default_exception_handler(), and loop.call_exception_handler()." +msgstr "" + +#: ../../../Misc/NEWS:6504 +msgid "" +"`Issue #20673 `__: Implement support for UNIX " +"Domain Sockets in asyncio. New APIs: loop.create_unix_connection(), loop." +"create_unix_server(), streams.open_unix_connection(), and streams." +"start_unix_server()." +msgstr "" + +#: ../../../Misc/NEWS:6508 +msgid "" +"`Issue #20616 `__: Add a format() method to " +"tracemalloc.Traceback." +msgstr "" + +#: ../../../Misc/NEWS:6510 +msgid "" +"`Issue #19744 `__: the ensurepip installation " +"step now just prints a warning to stderr rather than failing outright if SSL/" +"TLS is unavailable. This allows local installation of POSIX builds without " +"SSL/TLS support." +msgstr "" + +#: ../../../Misc/NEWS:6514 +msgid "" +"`Issue #20594 `__: Avoid name clash with the " +"libc function posix_close." +msgstr "" + +#: ../../../Misc/NEWS:6519 +msgid "" +"`Issue #20641 `__: Run MSI custom actions " +"(pip installation, pyc compilation) with the NoImpersonate flag, to support " +"elevated execution (UAC)." +msgstr "" + +#: ../../../Misc/NEWS:6522 +msgid "" +"`Issue #20221 `__: Removed conflicting (or " +"circular) hypot definition when compiled with VS 2010 or above. Initial " +"patch by Tabrez Mohammed." +msgstr "" + +#: ../../../Misc/NEWS:6525 +msgid "" +"`Issue #20609 `__: Restored the ability to " +"build 64-bit Windows binaries on 32-bit Windows, which was broken by the " +"change in `issue #19788 `__." +msgstr "" + +#: ../../../Misc/NEWS:6530 +msgid "Python 3.4.0 release candidate 1" +msgstr "" + +#: ../../../Misc/NEWS:6532 +msgid "Release date: 2014-02-10" +msgstr "" + +#: ../../../Misc/NEWS:6537 +msgid "" +"`Issue #19255 `__: The builtins module is " +"restored to initial value before cleaning other modules. The sys and " +"builtins modules are cleaned last." +msgstr "" + +#: ../../../Misc/NEWS:6540 +msgid "" +"`Issue #20588 `__: Make Python-ast.c C89 " +"compliant." +msgstr "" + +#: ../../../Misc/NEWS:6542 +msgid "" +"`Issue #20437 `__: Fixed 22 potential bugs " +"when deleting object references." +msgstr "" + +#: ../../../Misc/NEWS:6544 +msgid "" +"`Issue #20500 `__: Displaying an exception at " +"interpreter shutdown no longer risks triggering an assertion failure in " +"PyObject_Str." +msgstr "" + +#: ../../../Misc/NEWS:6547 +msgid "" +"`Issue #20538 `__: UTF-7 incremental decoder " +"produced inconsistent string when input was truncated in BASE64 section." +msgstr "" + +#: ../../../Misc/NEWS:6550 +msgid "" +"`Issue #20404 `__: io.TextIOWrapper (and " +"hence the open() builtin) now uses the internal codec marking system added " +"for `issue #19619 `__ to throw LookupError " +"for known non-text encodings at stream construction time. The existing " +"output type checks remain in place to deal with unmarked third party codecs." +msgstr "" + +#: ../../../Misc/NEWS:6556 +msgid "`Issue #17162 `__: Add PyType_GetSlot." +msgstr "" + +#: ../../../Misc/NEWS:6558 +msgid "" +"`Issue #20162 `__: Fix an alignment issue in " +"the siphash24() hash function which caused a crash on PowerPC 64-bit (ppc64)." +msgstr "" + +#: ../../../Misc/NEWS:6564 +msgid "" +"`Issue #20530 `__: The signatures for slot " +"builtins have been updated to reflect the fact that they only accept " +"positional-only arguments." +msgstr "" + +#: ../../../Misc/NEWS:6567 +msgid "" +"`Issue #20517 `__: Functions in the os module " +"that accept two filenames now register both filenames in the exception on " +"failure." +msgstr "" + +#: ../../../Misc/NEWS:6570 +msgid "" +"`Issue #20563 `__: The ipaddress module API " +"is now considered stable." +msgstr "" + +#: ../../../Misc/NEWS:6572 +msgid "" +"`Issue #14983 `__: email.generator now always " +"adds a line end after each MIME boundary marker, instead of doing so only " +"when there is an epilogue. This fixes an RFC compliance bug and solves an " +"issue with signed MIME parts." +msgstr "" + +#: ../../../Misc/NEWS:6576 +msgid "" +"`Issue #20540 `__: Fix a performance " +"regression (vs. Python 3.2) when layering a multiprocessing Connection over " +"a TCP socket. For small payloads, Nagle's algorithm would introduce idle " +"delays before the entire transmission of a message." +msgstr "" + +#: ../../../Misc/NEWS:6581 +msgid "" +"`Issue #16983 `__: the new email header " +"parsing code will now decode encoded words that are (incorrectly) surrounded " +"by quotes, and register a defect." +msgstr "" + +#: ../../../Misc/NEWS:6584 +msgid "" +"`Issue #19772 `__: email.generator no longer " +"mutates the message object when doing a down-transform from 8bit to 7bit " +"CTEs." +msgstr "" + +#: ../../../Misc/NEWS:6587 +msgid "" +"`Issue #20536 `__: the statistics module now " +"correctly handle Decimal instances with positive exponents" +msgstr "" + +#: ../../../Misc/NEWS:6590 +msgid "" +"`Issue #18805 `__: the netmask/hostmask " +"parsing in ipaddress now more reliably filters out illegal values and " +"correctly allows any valid prefix length." +msgstr "" + +#: ../../../Misc/NEWS:6593 +msgid "" +"`Issue #20481 `__: For at least Python 3.4, " +"the statistics module will require that all inputs for a single operation be " +"of a single consistent type, or else a mixed of ints and a single other " +"consistent type. This avoids some interoperability issues that arose with " +"the previous approach of coercing to a suitable common type." +msgstr "" + +#: ../../../Misc/NEWS:6599 +msgid "" +"`Issue #20478 `__: the statistics module now " +"treats collections.Counter inputs like any other iterable." +msgstr "" + +#: ../../../Misc/NEWS:6602 +msgid "" +"`Issue #17369 `__: get_filename was raising " +"an exception if the filename parameter's RFC2231 encoding was broken in " +"certain ways. This was a regression relative to python2." +msgstr "" + +#: ../../../Misc/NEWS:6606 +msgid "" +"`Issue #20013 `__: Some imap servers " +"disconnect if the current mailbox is deleted, and imaplib did not handle " +"that case gracefully. Now it handles the 'bye' correctly." +msgstr "" + +#: ../../../Misc/NEWS:6610 +msgid "" +"`Issue #20531 `__: Revert 3.4 version of fix " +"for #19063, and apply the 3.3 version. That is, do *not* raise an error if " +"unicode is passed to email.message.Message.set_payload." +msgstr "" + +#: ../../../Misc/NEWS:6614 +msgid "" +"`Issue #20476 `__: If a non-compat32 policy " +"is used with any of the email parsers, EmailMessage is now used as the " +"factory class. The factory class should really come from the policy; that " +"will get fixed in 3.5." +msgstr "" + +#: ../../../Misc/NEWS:6618 +msgid "" +"`Issue #19920 `__: TarFile.list() no longer " +"fails when outputs a listing containing non-encodable characters. Based on " +"patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:6621 +msgid "" +"`Issue #20515 `__: Fix NULL pointer " +"dereference introduced by `issue #20368 `__." +msgstr "" + +#: ../../../Misc/NEWS:6623 +msgid "" +"`Issue #19186 `__: Restore namespacing of " +"expat symbols inside the pyexpat module." +msgstr "" + +#: ../../../Misc/NEWS:6625 +msgid "" +"`Issue #20053 `__: ensurepip (and hence venv) " +"are no longer affected by the settings in the default pip configuration file." +msgstr "" + +#: ../../../Misc/NEWS:6628 +msgid "" +"`Issue #20426 `__: When passing the re.DEBUG " +"flag, re.compile() displays the debug output every time it is called, " +"regardless of the compilation cache." +msgstr "" + +#: ../../../Misc/NEWS:6631 +msgid "" +"`Issue #20368 `__: The null character now " +"correctly passed from Tcl to Python. Improved error handling in variables-" +"related commands." +msgstr "" + +#: ../../../Misc/NEWS:6634 +msgid "" +"`Issue #20435 `__: Fix _pyio.StringIO." +"getvalue() to take into account newline translation settings." +msgstr "" + +#: ../../../Misc/NEWS:6637 +msgid "tracemalloc: Fix slicing traces and fix slicing a traceback." +msgstr "" + +#: ../../../Misc/NEWS:6639 +msgid "" +"`Issue #20354 `__: Fix an alignment issue in " +"the tracemalloc module on 64-bit platforms. Bug seen on 64-bit Linux when " +"using \"make profile-opt\"." +msgstr "" + +#: ../../../Misc/NEWS:6642 +msgid "" +"`Issue #17159 `__: inspect.signature now " +"accepts duck types of functions, which adds support for Cython functions. " +"Initial patch by Stefan Behnel." +msgstr "" + +#: ../../../Misc/NEWS:6645 +msgid "" +"`Issue #18801 `__: Fix inspect." +"classify_class_attrs to correctly classify object.__new__ and object." +"__init__." +msgstr "" + +#: ../../../Misc/NEWS:6648 +msgid "Fixed cmath.isinf's name in its argument parsing code." +msgstr "" + +#: ../../../Misc/NEWS:6650 +msgid "" +"`Issue #20311 `__, #20452: poll and epoll now " +"round the timeout away from zero, instead of rounding towards zero, in " +"select and selectors modules: select.epoll.poll(), selectors.PollSelector." +"poll() and selectors.EpollSelector.poll(). For example, a timeout of one " +"microsecond (1e-6) is now rounded to one millisecondi (1e-3), instead of " +"being rounded to zero. However, the granularity property and asyncio's " +"resolution feature were removed again." +msgstr "" + +#: ../../../Misc/NEWS:6658 +msgid "" +"asyncio: Some refactoring; various fixes; add write flow control to unix " +"pipes; Future.set_exception() instantiates the exception argument if it is a " +"class; improved proactor pipe transport; support wait_for(f, None); don't " +"log broken/disconnected pipes; use ValueError instead of assert for " +"forbidden subprocess_{shell,exec} arguments; added a convenience API for " +"subprocess management; added StreamReader.at_eof(); properly handle " +"duplicate coroutines/futures in gather(), wait(), as_completed(); use a " +"bytearray for buffering in StreamReader; and more." +msgstr "" + +#: ../../../Misc/NEWS:6668 +msgid "" +"`Issue #20288 `__: fix handling of invalid " +"numeric charrefs in HTMLParser." +msgstr "" + +#: ../../../Misc/NEWS:6670 +msgid "" +"`Issue #20424 `__: Python implementation of " +"io.StringIO now supports lone surrogates." +msgstr "" + +#: ../../../Misc/NEWS:6672 +msgid "" +"`Issue #20308 `__: inspect.signature now " +"works on classes without user-defined __init__ or __new__ methods." +msgstr "" + +#: ../../../Misc/NEWS:6675 +msgid "" +"`Issue #20372 `__: inspect.getfile (and a " +"bunch of other inspect functions that use it) doesn't crash with unexpected " +"AttributeError on classes defined in C without __module__." +msgstr "" + +#: ../../../Misc/NEWS:6679 +msgid "" +"`Issue #20356 `__: inspect.signature " +"formatting uses '/' to separate positional-only parameters from others." +msgstr "" + +#: ../../../Misc/NEWS:6682 +msgid "" +"`Issue #20223 `__: inspect.signature now " +"supports methods defined with functools.partialmethods." +msgstr "" + +#: ../../../Misc/NEWS:6685 +msgid "" +"`Issue #19456 `__: ntpath.join() now joins " +"relative paths correctly when a drive is present." +msgstr "" + +#: ../../../Misc/NEWS:6688 +msgid "" +"`Issue #19077 `__: tempfile." +"TemporaryDirectory cleanup no longer fails when called during shutdown. " +"Emitting resource warning in __del__ no longer fails. Original patch by " +"Antoine Pitrou." +msgstr "" + +#: ../../../Misc/NEWS:6692 +msgid "" +"`Issue #20394 `__: Silence Coverity warning " +"in audioop module." +msgstr "" + +#: ../../../Misc/NEWS:6694 +msgid "" +"`Issue #20367 `__: Fix behavior of concurrent." +"futures.as_completed() for duplicate arguments. Patch by Glenn Langford." +msgstr "" + +#: ../../../Misc/NEWS:6697 +msgid "" +"`Issue #8260 `__: The read(), readline() and " +"readlines() methods of codecs.StreamReader returned incomplete data when " +"were called after readline() or read(size). Based on patch by Amaury " +"Forgeot d'Arc." +msgstr "" + +#: ../../../Misc/NEWS:6701 +msgid "" +"`Issue #20105 `__: the codec exception " +"chaining now correctly sets the traceback of the original exception as its " +"__traceback__ attribute." +msgstr "" + +#: ../../../Misc/NEWS:6704 +msgid "" +"`Issue #17481 `__: inspect.getfullargspec() " +"now uses inspect.signature() API." +msgstr "" + +#: ../../../Misc/NEWS:6706 +msgid "" +"`Issue #15304 `__: concurrent.futures.wait() " +"can block forever even if Futures have completed. Patch by Glenn Langford." +msgstr "" + +#: ../../../Misc/NEWS:6709 +msgid "" +"`Issue #14455 `__: plistlib: fix serializing " +"integers in the range of an unsigned long long but outside of the range of " +"signed long long for binary plist files." +msgstr "" + +#: ../../../Misc/NEWS:6716 +msgid "" +"`Issue #20406 `__: Use Python application " +"icons for Idle window title bars. Patch mostly by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:6719 +msgid "" +"Update the python.gif icon for the Idle classbrowser and pathbowser from the " +"old green snake to the new blue and yellow snakes." +msgstr "" + +#: ../../../Misc/NEWS:6722 +msgid "" +"`Issue #17721 `__: Remove non-functional " +"configuration dialog help button until we make it actually gives some help " +"when clicked. Patch by Guilherme Simões." +msgstr "" + +#: ../../../Misc/NEWS:6728 +msgid "" +"`Issue #20532 `__: Tests which use _testcapi " +"now are marked as CPython only." +msgstr "" + +#: ../../../Misc/NEWS:6730 +msgid "" +"`Issue #19920 `__: Added tests for TarFile." +"list(). Based on patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:6732 +msgid "" +"`Issue #19990 `__: Added tests for the imghdr " +"module. Based on patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:6735 +msgid "" +"`Issue #20474 `__: Fix test_socket " +"\"unexpected success\" failures on OS X 10.7+." +msgstr "" + +#: ../../../Misc/NEWS:6740 +msgid "" +"`Issue #20530 `__: Argument Clinic's " +"signature format has been revised again. The new syntax is highly human " +"readable while still preventing false positives. The syntax also extends " +"Python syntax to denote \"self\" and positional-only parameters, allowing " +"inspect.Signature objects to be totally accurate for all supported builtins " +"in Python 3.4." +msgstr "" + +#: ../../../Misc/NEWS:6746 +msgid "" +"`Issue #20456 `__: Argument Clinic now " +"observes the C preprocessor conditional compilation statements of the C " +"files it parses. When a Clinic block is inside a conditional code, it " +"adjusts its output to match, including automatically generating an empty " +"methoddef macro." +msgstr "" + +#: ../../../Misc/NEWS:6751 +msgid "" +"`Issue #20456 `__: Cloned functions in " +"Argument Clinic now use the correct name, not the name of the function they " +"were cloned from, for text strings inside generated code." +msgstr "" + +#: ../../../Misc/NEWS:6755 +msgid "" +"`Issue #20456 `__: Fixed Argument Clinic's " +"test suite and \"--converters\" feature." +msgstr "" + +#: ../../../Misc/NEWS:6757 +msgid "" +"`Issue #20456 `__: Argument Clinic now allows " +"specifying different names for a parameter in Python and C, using \"as\" on " +"the parameter line." +msgstr "" + +#: ../../../Misc/NEWS:6760 +msgid "" +"`Issue #20326 `__: Argument Clinic now uses a " +"simple, unique signature to annotate text signatures in docstrings, " +"resulting in fewer false positives. \"self\" parameters are also explicitly " +"marked, allowing inspect.Signature() to authoritatively detect (and skip) " +"said parameters." +msgstr "" + +#: ../../../Misc/NEWS:6765 +msgid "" +"`Issue #20326 `__: Argument Clinic now " +"generates separate checksums for the input and output sections of the block, " +"allowing external tools to verify that the input has not changed (and thus " +"the output is not out-of-date)." +msgstr "" + +#: ../../../Misc/NEWS:6772 +msgid "" +"`Issue #20465 `__: Update SQLite shipped with " +"OS X installer to 3.8.3." +msgstr "" + +#: ../../../Misc/NEWS:6775 ../../../Misc/NEWS:10493 +msgid "C-API" +msgstr "" + +#: ../../../Misc/NEWS:6777 +msgid "" +"`Issue #20517 `__: Added new functions " +"allowing OSError exceptions to reference two filenames instead of one: " +"PyErr_SetFromErrnoWithFilenameObjects() and " +"PyErr_SetExcFromWindowsErrWithFilenameObjects()." +msgstr "" + +#: ../../../Misc/NEWS:6784 +msgid "" +"`Issue #20488 `__: Change wording to say " +"importlib is *the* implementation of import instead of just *an* " +"implementation." +msgstr "" + +#: ../../../Misc/NEWS:6787 +msgid "" +"`Issue #6386 `__: Clarify in the tutorial that " +"specifying a symlink to execute means the directory containing the executed " +"script and not the symlink is added to sys.path." +msgstr "" + +#: ../../../Misc/NEWS:6793 +msgid "Python 3.4.0 Beta 3" +msgstr "" + +#: ../../../Misc/NEWS:6795 +msgid "Release date: 2014-01-26" +msgstr "" + +#: ../../../Misc/NEWS:6800 +msgid "" +"`Issue #20189 `__: Four additional builtin " +"types (PyTypeObject, PyMethodDescr_Type, _PyMethodWrapper_Type, and " +"PyWrapperDescr_Type) have been modified to provide introspection information " +"for builtins." +msgstr "" + +#: ../../../Misc/NEWS:6804 +msgid "" +"`Issue #17825 `__: Cursor \"^\" is correctly " +"positioned for SyntaxError and IndentationError." +msgstr "" + +#: ../../../Misc/NEWS:6807 +msgid "" +"`Issue #2382 `__: SyntaxError cursor \"^\" is " +"now written at correct position in most cases when multibyte characters are " +"in line (before \"^\"). This still not works correctly with wide East Asian " +"characters." +msgstr "" + +#: ../../../Misc/NEWS:6811 +msgid "" +"`Issue #18960 `__: The first line of Python " +"script could be executed twice when the source encoding was specified on the " +"second line. Now the source encoding declaration on the second line isn't " +"effective if the first line contains anything except a comment. 'python -x' " +"works now again with files with the source encoding declarations, and can be " +"used to make Python batch files on Windows." +msgstr "" + +#: ../../../Misc/NEWS:6821 +msgid "" +"asyncio: Various improvements and small changes not all covered by issues " +"listed below. E.g. wait_for() now cancels the inner task if the timeout " +"occcurs; tweaked the set of exported symbols; renamed Empty/Full to " +"QueueEmpty/QueueFull; \"with (yield from lock)\" now uses a separate context " +"manager; readexactly() raises if not enough data was read; PTY support " +"tweaks." +msgstr "" + +#: ../../../Misc/NEWS:6828 +msgid "" +"`Issue #20311 `__: asyncio: Add a granularity " +"attribute to BaseEventLoop: maximum between the resolution of the " +"BaseEventLoop.time() method and the resolution of the selector. The " +"granuarility is used in the scheduler to round time and deadline." +msgstr "" + +#: ../../../Misc/NEWS:6833 +msgid "" +"`Issue #20311 `__: selectors: Add a " +"resolution attribute to BaseSelector." +msgstr "" + +#: ../../../Misc/NEWS:6835 +msgid "" +"`Issue #20189 `__: unittest.mock now no " +"longer assumes that any object for which it could get an inspect.Signature " +"is a callable written in Python. Fix courtesy of Michael Foord." +msgstr "" + +#: ../../../Misc/NEWS:6839 +msgid "" +"`Issue #20317 `__: ExitStack.__exit__ could " +"create a self-referential loop if an exception raised by a cleanup operation " +"already had its context set correctly (for example, by the @contextmanager " +"decorator). The infinite loop this caused is now avoided by checking if the " +"expected context is already set before trying to fix it." +msgstr "" + +#: ../../../Misc/NEWS:6845 +msgid "" +"`Issue #20374 `__: Fix build with GNU " +"readline >= 6.3." +msgstr "" + +#: ../../../Misc/NEWS:6847 +msgid "" +"`Issue #20262 `__: Warnings are raised now " +"when duplicate names are added in the ZIP file or too long ZIP file comment " +"is truncated." +msgstr "" + +#: ../../../Misc/NEWS:6850 +msgid "" +"`Issue #20165 `__: The unittest module no " +"longer considers tests marked with @expectedFailure successful if they pass." +msgstr "" + +#: ../../../Misc/NEWS:6853 +msgid "" +"`Issue #18574 `__: Added missing newline in " +"100-Continue reply from http.server.BaseHTTPRequestHandler. Patch by " +"Nikolaus Rath." +msgstr "" + +#: ../../../Misc/NEWS:6856 +msgid "" +"`Issue #20270 `__: urllib.urlparse now " +"supports empty ports." +msgstr "" + +#: ../../../Misc/NEWS:6858 +msgid "" +"`Issue #20243 `__: TarFile no longer raise " +"ReadError when opened in write mode." +msgstr "" + +#: ../../../Misc/NEWS:6860 +msgid "" +"`Issue #20238 `__: TarFile opened with " +"external fileobj and \"w:gz\" mode didn't write complete output on close." +msgstr "" + +#: ../../../Misc/NEWS:6863 +msgid "" +"`Issue #20245 `__: The open functions in the " +"tarfile module now correctly handle empty mode." +msgstr "" + +#: ../../../Misc/NEWS:6866 +msgid "" +"`Issue #20242 `__: Fixed basicConfig() format " +"strings for the alternative formatting styles. Thanks to kespindler for the " +"bug report and patch." +msgstr "" + +#: ../../../Misc/NEWS:6869 +msgid "" +"`Issue #20246 `__: Fix buffer overflow in " +"socket.recvfrom_into." +msgstr "" + +#: ../../../Misc/NEWS:6871 +msgid "" +"Issues #20206 and #5803: Fix edge case in email.quoprimime.encode where it " +"truncated lines ending in a character needing encoding but no newline by " +"using a more efficient algorithm that doesn't have the bug." +msgstr "" + +#: ../../../Misc/NEWS:6875 +msgid "" +"`Issue #19082 `__: Working xmlrpc.server and " +"xmlrpc.client examples. Both in modules and in documentation. Initial patch " +"contributed by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:6878 +msgid "" +"`Issue #20138 `__: The wsgiref." +"application_uri() and wsgiref.request_uri() functions now conform to PEP " +"3333 when handle non-ASCII URLs." +msgstr "" + +#: ../../../Misc/NEWS:6881 +msgid "" +"`Issue #19097 `__: Raise the correct " +"Exception when cgi.FieldStorage is given an invalid fileobj." +msgstr "" + +#: ../../../Misc/NEWS:6884 +msgid "" +"`Issue #20152 `__: Ported Python/import.c " +"over to Argument Clinic." +msgstr "" + +#: ../../../Misc/NEWS:6886 +msgid "" +"`Issue #13107 `__: argparse and optparse no " +"longer raises an exception when output a help on environment with too small " +"COLUMNS. Based on patch by Elazar Gershuni." +msgstr "" + +#: ../../../Misc/NEWS:6890 +msgid "" +"`Issue #20207 `__: Always disable SSLv2 " +"except when PROTOCOL_SSLv2 is explicitly asked for." +msgstr "" + +#: ../../../Misc/NEWS:6893 +msgid "" +"`Issue #18960 `__: The tokenize module now " +"ignore the source encoding declaration on the second line if the first line " +"contains anything except a comment." +msgstr "" + +#: ../../../Misc/NEWS:6896 +msgid "" +"`Issue #20078 `__: Reading malformed zipfiles " +"no longer hangs with 100% CPU consumption." +msgstr "" + +#: ../../../Misc/NEWS:6899 +msgid "" +"`Issue #20113 `__: os.readv() and os.writev() " +"now raise an OSError exception on error instead of returning -1." +msgstr "" + +#: ../../../Misc/NEWS:6902 +msgid "" +"`Issue #19719 `__: Make importlib.abc." +"MetaPathFinder.find_module(), PathEntryFinder.find_loader(), and Loader." +"load_module() use PEP 451 APIs to help with backwards-compatibility." +msgstr "" + +#: ../../../Misc/NEWS:6906 +msgid "" +"`Issue #20144 `__: inspect.Signature now " +"supports parsing simple symbolic constants as parameter default values in " +"__text_signature__." +msgstr "" + +#: ../../../Misc/NEWS:6909 +msgid "" +"`Issue #20072 `__: Fixed multiple errors in " +"tkinter with wantobjects is False." +msgstr "" + +#: ../../../Misc/NEWS:6911 +msgid "" +"`Issue #20229 `__: Avoid plistlib deprecation " +"warning in platform.mac_ver()." +msgstr "" + +#: ../../../Misc/NEWS:6913 +msgid "" +"`Issue #14455 `__: Fix some problems with the " +"new binary plist support in plistlib." +msgstr "" + +#: ../../../Misc/NEWS:6918 +msgid "" +"`Issue #17390 `__: Add Python version to Idle " +"editor window title bar. Original patches by Edmond Burnett and Kent Johnson." +msgstr "" + +#: ../../../Misc/NEWS:6921 +msgid "" +"`Issue #18960 `__: IDLE now ignores the " +"source encoding declaration on the second line if the first line contains " +"anything except a comment." +msgstr "" + +#: ../../../Misc/NEWS:6927 +msgid "" +"`Issue #20358 `__: Tests for curses.window." +"overlay and curses.window.overwrite no longer specify min{row,col} > max{row," +"col}." +msgstr "" + +#: ../../../Misc/NEWS:6930 +msgid "" +"`Issue #19804 `__: The test_find_mac test in " +"test_uuid is now skipped if the ifconfig executable is not available." +msgstr "" + +#: ../../../Misc/NEWS:6933 +msgid "" +"`Issue #19886 `__: Use better estimated " +"memory requirements for bigmem tests." +msgstr "" + +#: ../../../Misc/NEWS:6938 +msgid "" +"`Issue #20390 `__: Argument Clinic's \"file\" " +"output preset now defaults to \"{dirname}/clinic/{basename}.h\"." +msgstr "" + +#: ../../../Misc/NEWS:6941 +msgid "" +"`Issue #20390 `__: Argument Clinic's \"class" +"\" directive syntax has been extended with two new required arguments: " +"\"typedef\" and \"type_object\"." +msgstr "" + +#: ../../../Misc/NEWS:6944 +msgid "" +"`Issue #20390 `__: Argument Clinic: If " +"__new__ or __init__ functions didn't use kwargs (or args), the " +"PyArg_NoKeywords (or PyArg_NoPositional) calls generated are only run when " +"the type object is an exact match." +msgstr "" + +#: ../../../Misc/NEWS:6948 +msgid "" +"`Issue #20390 `__: Argument Clinic now fails " +"if you have required parameters after optional parameters." +msgstr "" + +#: ../../../Misc/NEWS:6951 +msgid "" +"`Issue #20390 `__: Argument Clinic converters " +"now have a new template they can inject code into: \"modifiers\". Code put " +"there is run in the parsing function after argument parsing but before the " +"call to the impl." +msgstr "" + +#: ../../../Misc/NEWS:6955 +msgid "" +"`Issue #20376 `__: Argument Clinic now " +"escapes backslashes in docstrings." +msgstr "" + +#: ../../../Misc/NEWS:6957 +msgid "" +"`Issue #20381 `__: Argument Clinic now sanity " +"checks the default argument when c_default is also specified, providing a " +"nice failure message for disallowed values." +msgstr "" + +#: ../../../Misc/NEWS:6961 +msgid "" +"`Issue #20189 `__: Argument Clinic now " +"ensures that parser functions for __new__ are always of type newfunc, the " +"type of the tp_new slot. Similarly, parser functions for __init__ are now " +"always of type initproc, the type of tp_init." +msgstr "" + +#: ../../../Misc/NEWS:6966 +msgid "" +"`Issue #20189 `__: Argument Clinic now " +"suppresses the docstring for __new__ and __init__ functions if no docstring " +"is provided in the input." +msgstr "" + +#: ../../../Misc/NEWS:6969 +msgid "" +"`Issue #20189 `__: Argument Clinic now " +"suppresses the \"self\" parameter in the impl for @staticmethod functions." +msgstr "" + +#: ../../../Misc/NEWS:6972 +msgid "" +"`Issue #20294 `__: Argument Clinic now " +"supports argument parsing for __new__ and __init__ functions." +msgstr "" + +#: ../../../Misc/NEWS:6975 +msgid "" +"`Issue #20299 `__: Argument Clinic custom " +"converters may now change the default value of c_default and py_default with " +"a class member." +msgstr "" + +#: ../../../Misc/NEWS:6978 +msgid "" +"`Issue #20287 `__: Argument Clinic's output " +"is now configurable, allowing delaying its output or even redirecting it to " +"a separate file." +msgstr "" + +#: ../../../Misc/NEWS:6981 +msgid "" +"`Issue #20226 `__: Argument Clinic now " +"permits simple expressions (e.g. \"sys.maxsize - 1\") as default values for " +"parameters." +msgstr "" + +#: ../../../Misc/NEWS:6984 +msgid "" +"`Issue #19936 `__: Added executable bits or " +"shebang lines to Python scripts which requires them. Disable executable " +"bits and shebang lines in test and benchmark files in order to prevent using " +"a random system python, and in source files of modules which don't provide " +"command line interface. Fixed shebang lines in the unittestgui and checkpip " +"scripts." +msgstr "" + +#: ../../../Misc/NEWS:6990 +msgid "" +"`Issue #20268 `__: Argument Clinic now " +"supports cloning the parameters and return converter of existing functions." +msgstr "" + +#: ../../../Misc/NEWS:6993 +msgid "" +"`Issue #20228 `__: Argument Clinic now has " +"special support for class special methods." +msgstr "" + +#: ../../../Misc/NEWS:6996 +msgid "" +"`Issue #20214 `__: Fixed a number of small " +"issues and documentation errors in Argument Clinic (see issue for details)." +msgstr "" + +#: ../../../Misc/NEWS:6999 +msgid "" +"`Issue #20196 `__: Fixed a bug where Argument " +"Clinic did not generate correct parsing code for functions with positional-" +"only parameters where all arguments are optional." +msgstr "" + +#: ../../../Misc/NEWS:7003 +msgid "" +"`Issue #18960 `__: 2to3 and the findnocoding." +"py script now ignore the source encoding declaration on the second line if " +"the first line contains anything except a comment." +msgstr "" + +#: ../../../Misc/NEWS:7007 +msgid "" +"`Issue #19723 `__: The marker comments " +"Argument Clinic uses have been changed to improve readability." +msgstr "" + +#: ../../../Misc/NEWS:7010 +msgid "" +"`Issue #20157 `__: When Argument Clinic " +"renames a parameter because its name collides with a C keyword, it no longer " +"exposes that rename to PyArg_Parse." +msgstr "" + +#: ../../../Misc/NEWS:7013 +msgid "" +"`Issue #20141 `__: Improved Argument Clinic's " +"support for the PyArg_Parse \"O!\" format unit." +msgstr "" + +#: ../../../Misc/NEWS:7016 +msgid "" +"`Issue #20144 `__: Argument Clinic now " +"supports simple symbolic constants as parameter default values." +msgstr "" + +#: ../../../Misc/NEWS:7019 +msgid "" +"`Issue #20143 `__: The line numbers reported " +"in Argument Clinic errors are now more accurate." +msgstr "" + +#: ../../../Misc/NEWS:7022 +msgid "" +"`Issue #20142 `__: Py_buffer variables " +"generated by Argument Clinic are now initialized with a default value." +msgstr "" + +#: ../../../Misc/NEWS:7028 +msgid "" +"`Issue #12837 `__: Silence a tautological " +"comparison warning on OS X under Clang in socketmodule.c." +msgstr "" + +#: ../../../Misc/NEWS:7033 +msgid "Python 3.4.0 Beta 2" +msgstr "" + +#: ../../../Misc/NEWS:7035 +msgid "Release date: 2014-01-05" +msgstr "" + +#: ../../../Misc/NEWS:7040 +msgid "" +"`Issue #17432 `__: Drop UCS2 from names of " +"Unicode functions in python3.def." +msgstr "" + +#: ../../../Misc/NEWS:7042 +msgid "" +"`Issue #19526 `__: Exclude all new API from " +"the stable ABI. Exceptions can be made if a need is demonstrated." +msgstr "" + +#: ../../../Misc/NEWS:7045 +msgid "" +"`Issue #19969 `__: PyBytes_FromFormatV() now " +"raises an OverflowError if \"%c\" argument is not in range [0; 255]." +msgstr "" + +#: ../../../Misc/NEWS:7048 +msgid "" +"`Issue #19995 `__: %c, %o, %x, and %X now " +"issue a DeprecationWarning on non-integer input; reworded docs to clarify " +"that an integer type should define both __int__ and __index__." +msgstr "" + +#: ../../../Misc/NEWS:7052 +msgid "" +"`Issue #19787 `__: PyThread_set_key_value() " +"now always set the value. In Python 3.3, the function did nothing if the key " +"already exists (if the current value is a non-NULL pointer)." +msgstr "" + +#: ../../../Misc/NEWS:7056 +msgid "" +"`Issue #14432 `__: Remove the thread state " +"field from the frame structure. Fix a crash when a generator is created in a " +"C thread that is destroyed while the generator is still used. The issue was " +"that a generator contains a frame, and the frame kept a reference to the " +"Python state of the destroyed C thread. The crash occurs when a trace " +"function is setup." +msgstr "" + +#: ../../../Misc/NEWS:7062 +msgid "" +"`Issue #19576 `__: PyGILState_Ensure() now " +"initializes threads. At startup, Python has no concrete GIL. If " +"PyGILState_Ensure() is called from a new thread for the first time and " +"PyEval_InitThreads() was not called yet, a GIL needs to be created." +msgstr "" + +#: ../../../Misc/NEWS:7067 +msgid "" +"`Issue #17576 `__: Deprecation warning " +"emitted now when __int__() or __index__() return not int instance." +msgstr "" + +#: ../../../Misc/NEWS:7070 +msgid "" +"`Issue #19932 `__: Fix typo in import.h, " +"missing whitespaces in function prototypes." +msgstr "" + +#: ../../../Misc/NEWS:7072 +msgid "" +"`Issue #19736 `__: Add module-level statvfs " +"constants defined for GNU/glibc based systems." +msgstr "" + +#: ../../../Misc/NEWS:7075 +msgid "" +"`Issue #20097 `__: Fix bad use of \"self\" in " +"importlib's WindowsRegistryFinder." +msgstr "" + +#: ../../../Misc/NEWS:7077 +msgid "" +"`Issue #19729 `__: In str.format(), fix " +"recursive expansion in format spec." +msgstr "" + +#: ../../../Misc/NEWS:7079 +msgid "" +"`Issue #19638 `__: Fix possible crash / " +"undefined behaviour from huge (more than 2 billion characters) input strings " +"in _Py_dg_strtod." +msgstr "" + +#: ../../../Misc/NEWS:7085 +msgid "" +"`Issue #20154 `__: Deadlock in asyncio." +"StreamReader.readexactly()." +msgstr "" + +#: ../../../Misc/NEWS:7087 +msgid "" +"`Issue #16113 `__: Remove sha3 module again." +msgstr "" + +#: ../../../Misc/NEWS:7089 +msgid "" +"`Issue #20111 `__: pathlib.Path.with_suffix() " +"now sanity checks the given suffix." +msgstr "" + +#: ../../../Misc/NEWS:7091 +msgid "" +"Fix breakage in TestSuite.countTestCases() introduced by `issue #11798 " +"`__." +msgstr "" + +#: ../../../Misc/NEWS:7093 +msgid "" +"`Issue #20108 `__: Avoid parameter name clash " +"in inspect.getcallargs()." +msgstr "" + +#: ../../../Misc/NEWS:7095 +msgid "" +"`Issue #19918 `__: Fix PurePath.relative_to() " +"under Windows." +msgstr "" + +#: ../../../Misc/NEWS:7097 +msgid "" +"`Issue #19422 `__: Explicitly disallow non-" +"SOCK_STREAM sockets in the ssl module, rather than silently let them emit " +"clear text data." +msgstr "" + +#: ../../../Misc/NEWS:7100 +msgid "" +"`Issue #20046 `__: Locale alias table no " +"longer contains entities which can be calculated. Generalized support of " +"the euro modifier." +msgstr "" + +#: ../../../Misc/NEWS:7103 +msgid "" +"`Issue #20027 `__: Fixed locale aliases for " +"devanagari locales." +msgstr "" + +#: ../../../Misc/NEWS:7105 +msgid "" +"`Issue #20067 `__: Tkinter variables now work " +"when wantobjects is false." +msgstr "" + +#: ../../../Misc/NEWS:7107 +msgid "" +"`Issue #19020 `__: Tkinter now uses " +"splitlist() instead of split() in configure methods." +msgstr "" + +#: ../../../Misc/NEWS:7110 +msgid "" +"`Issue #19744 `__: ensurepip now provides a " +"better error message when Python is built without SSL/TLS support (pip " +"currently requires that support to run, even if only operating with local " +"wheel files)" +msgstr "" + +#: ../../../Misc/NEWS:7114 +msgid "" +"`Issue #19734 `__: ensurepip now ignores all " +"pip environment variables to avoid odd behaviour based on user configuration " +"settings" +msgstr "" + +#: ../../../Misc/NEWS:7117 +msgid "Fix TypeError on \"setup.py upload --show-response\"." +msgstr "" + +#: ../../../Misc/NEWS:7119 +msgid "" +"`Issue #20045 `__: Fix \"setup.py register --" +"list-classifiers\"." +msgstr "" + +#: ../../../Misc/NEWS:7121 +msgid "" +"`Issue #18879 `__: When a method is looked up " +"on a temporary file, avoid closing the file before the method is possibly " +"called." +msgstr "" + +#: ../../../Misc/NEWS:7124 +msgid "" +"`Issue #20037 `__: Avoid crashes when opening " +"a text file late at interpreter shutdown." +msgstr "" + +#: ../../../Misc/NEWS:7127 +msgid "" +"`Issue #19967 `__: Thanks to the PEP 442, " +"asyncio.Future now uses a destructor to log uncaught exceptions, instead of " +"the dedicated _TracebackLogger class." +msgstr "" + +#: ../../../Misc/NEWS:7131 +msgid "Added a Task.current_task() class method to asyncio." +msgstr "" + +#: ../../../Misc/NEWS:7133 +msgid "" +"`Issue #19850 `__: Set SA_RESTART in asyncio " +"when registering a signal handler to limit EINTR occurrences." +msgstr "" + +#: ../../../Misc/NEWS:7136 +msgid "" +"Implemented write flow control in asyncio for proactor event loop (Windows)." +msgstr "" + +#: ../../../Misc/NEWS:7138 +msgid "" +"Change write buffer in asyncio use to avoid O(N**2) behavior. Make write()/" +"sendto() accept bytearray/memoryview." +msgstr "" + +#: ../../../Misc/NEWS:7141 +msgid "" +"`Issue #20034 `__: Updated alias mapping to " +"most recent locale.alias file from X.org distribution using makelocalealias." +"py." +msgstr "" + +#: ../../../Misc/NEWS:7144 +msgid "" +"`Issue #5815 `__: Fixed support for locales " +"with modifiers. Fixed support for locale encodings with hyphens." +msgstr "" + +#: ../../../Misc/NEWS:7147 +msgid "" +"`Issue #20026 `__: Fix the sqlite module to " +"handle correctly invalid isolation level (wrong type)." +msgstr "" + +#: ../../../Misc/NEWS:7150 +msgid "" +"`Issue #18829 `__: csv.Dialect() now checks " +"type for delimiter, escapechar and quotechar fields. Original patch by " +"Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:7153 +msgid "" +"`Issue #19855 `__: uuid.getnode() on Unix now " +"looks on the PATH for the executables used to find the mac address, with /" +"sbin and /usr/sbin as fallbacks." +msgstr "" + +#: ../../../Misc/NEWS:7157 +msgid "" +"`Issue #20007 `__: HTTPResponse.read(0) no " +"more prematurely closes connection. Original patch by Simon Sapin." +msgstr "" + +#: ../../../Misc/NEWS:7160 +msgid "" +"`Issue #19946 `__: multiprocessing now uses " +"runpy to initialize __main__ in child processes when necessary, allowing it " +"to correctly handle scripts without suffixes and submodules that use " +"explicit relative imports or otherwise rely on parent modules being " +"correctly imported prior to execution." +msgstr "" + +#: ../../../Misc/NEWS:7166 +msgid "" +"`Issue #19921 `__: When Path.mkdir() is " +"called with parents=True, any missing parent is created with the default " +"permissions, ignoring the mode argument (mimicking the POSIX \"mkdir -p\" " +"command)." +msgstr "" + +#: ../../../Misc/NEWS:7170 +msgid "" +"`Issue #19887 `__: Improve the Path.resolve() " +"algorithm to support certain symlink chains." +msgstr "" + +#: ../../../Misc/NEWS:7173 +msgid "" +"`Issue #19912 `__: Fixed numerous bugs in " +"ntpath.splitunc()." +msgstr "" + +#: ../../../Misc/NEWS:7175 +msgid "" +"`Issue #19911 `__: ntpath.splitdrive() now " +"correctly processes the 'İ' character (U+0130, LATIN CAPITAL LETTER I WITH " +"DOT ABOVE)." +msgstr "" + +#: ../../../Misc/NEWS:7178 +msgid "" +"`Issue #19532 `__: python -m compileall with " +"no filename/directory arguments now respects the -f and -q flags instead of " +"ignoring them." +msgstr "" + +#: ../../../Misc/NEWS:7181 +msgid "" +"`Issue #19623 `__: Fixed writing to " +"unseekable files in the aifc module." +msgstr "" + +#: ../../../Misc/NEWS:7183 +msgid "" +"`Issue #19946 `__: multiprocessing.spawn now " +"raises ImportError when the module to be used as the main module cannot be " +"imported." +msgstr "" + +#: ../../../Misc/NEWS:7186 +msgid "" +"`Issue #17919 `__: select.poll.register() " +"again works with poll.POLLNVAL on AIX. Fixed integer overflow in the " +"eventmask parameter." +msgstr "" + +#: ../../../Misc/NEWS:7189 +msgid "" +"`Issue #19063 `__: if a Charset's " +"body_encoding was set to None, the email package would generate a message " +"claiming the Content-Transfer-Encoding was 7bit, and produce garbage output " +"for the content. This now works. A couple of other set_payload mishandlings " +"of non-ASCII are also fixed. In addition, calling set_payload with a string " +"argument without specifying a charset now raises an error (this is a new " +"error in 3.4)." +msgstr "" + +#: ../../../Misc/NEWS:7196 +msgid "" +"`Issue #15475 `__: Add __sizeof__ " +"implementations for itertools objects." +msgstr "" + +#: ../../../Misc/NEWS:7198 +msgid "" +"`Issue #19944 `__: Fix importlib.find_spec() " +"so it imports parents as needed and move the function to importlib.util." +msgstr "" + +#: ../../../Misc/NEWS:7201 +msgid "" +"`Issue #19880 `__: Fix a reference leak in " +"unittest.TestCase. Explicitly break reference cycles between frames and the " +"_Outcome instance." +msgstr "" + +#: ../../../Misc/NEWS:7204 +msgid "" +"`Issue #17429 `__: platform." +"linux_distribution() now decodes files from the UTF-8 encoding with the " +"surrogateescape error handler, instead of decoding from the locale encoding " +"in strict mode. It fixes the function on Fedora 19 which is probably the " +"first major distribution release with a non-ASCII name. Patch written by " +"Toshio Kuratomi." +msgstr "" + +#: ../../../Misc/NEWS:7210 +msgid "" +"`Issue #19343 `__: Expose FreeBSD-specific " +"APIs in resource module. Original patch by Koobs." +msgstr "" + +#: ../../../Misc/NEWS:7213 +msgid "" +"`Issue #19929 `__: Call os.read with 32768 " +"within subprocess.Popen.communicate rather than 4096 for efficiency. A " +"microbenchmark shows Linux and OS X both using ~50% less cpu time this way." +msgstr "" + +#: ../../../Misc/NEWS:7217 +msgid "" +"`Issue #19506 `__: Use a memoryview to avoid " +"a data copy when piping data to stdin within subprocess.Popen.communicate. " +"5-10% less cpu usage." +msgstr "" + +#: ../../../Misc/NEWS:7220 +msgid "" +"`Issue #19876 `__: selectors unregister() no " +"longer raises ValueError or OSError if the FD is closed (as long as it was " +"registered)." +msgstr "" + +#: ../../../Misc/NEWS:7223 +msgid "" +"`Issue #19908 `__: pathlib now joins relative " +"Windows paths correctly when a drive is present. Original patch by Antoine " +"Pitrou." +msgstr "" + +#: ../../../Misc/NEWS:7226 +msgid "" +"`Issue #19296 `__: Silence compiler warning " +"in dbm_open" +msgstr "" + +#: ../../../Misc/NEWS:7228 +msgid "" +"`Issue #6784 `__: Strings from Python 2 can " +"now be unpickled as bytes objects by setting the encoding argument of " +"Unpickler to be 'bytes'. Initial patch by Merlijn van Deen." +msgstr "" + +#: ../../../Misc/NEWS:7232 +msgid "" +"`Issue #19839 `__: Fix regression in bz2 " +"module's handling of non-bzip2 data at EOF, and analogous bug in lzma module." +msgstr "" + +#: ../../../Misc/NEWS:7235 +msgid "" +"`Issue #19881 `__: Fix pickling bug where " +"cpickle would emit bad pickle data for large bytes string (i.e., with size " +"greater than 2**32-1)." +msgstr "" + +#: ../../../Misc/NEWS:7238 +msgid "" +"`Issue #19138 `__: doctest's " +"IGNORE_EXCEPTION_DETAIL now allows a match when no exception detail exists " +"(no colon following the exception's name, or a colon does follow but no text " +"follows the colon)." +msgstr "" + +#: ../../../Misc/NEWS:7242 +msgid "" +"`Issue #19927 `__: Add __eq__ to path-based " +"loaders in importlib." +msgstr "" + +#: ../../../Misc/NEWS:7244 +msgid "" +"`Issue #19827 `__: On UNIX, setblocking() and " +"settimeout() methods of socket.socket can now avoid a second syscall if the " +"ioctl() function can be used, or if the non-blocking flag of the socket is " +"unchanged." +msgstr "" + +#: ../../../Misc/NEWS:7248 +msgid "" +"`Issue #19785 `__: smtplib now supports " +"SSLContext.check_hostname and server name indication for TLS/SSL connections." +msgstr "" + +#: ../../../Misc/NEWS:7251 +msgid "" +"`Issue #19784 `__: poplib now supports " +"SSLContext.check_hostname and server name indication for TLS/SSL connections." +msgstr "" + +#: ../../../Misc/NEWS:7254 +msgid "" +"`Issue #19783 `__: nntplib now supports " +"SSLContext.check_hostname and server name indication for TLS/SSL connections." +msgstr "" + +#: ../../../Misc/NEWS:7257 +msgid "" +"`Issue #19782 `__: imaplib now supports " +"SSLContext.check_hostname and server name indication for TLS/SSL connections." +msgstr "" + +#: ../../../Misc/NEWS:7260 +msgid "" +"`Issue #20123 `__: Fix pydoc.synopsis() for " +"\"binary\" modules." +msgstr "" + +#: ../../../Misc/NEWS:7262 +msgid "" +"`Issue #19834 `__: Support unpickling of " +"exceptions pickled by Python 2." +msgstr "" + +#: ../../../Misc/NEWS:7264 +msgid "" +"`Issue #19781 `__: ftplib now supports " +"SSLContext.check_hostname and server name indication for TLS/SSL connections." +msgstr "" + +#: ../../../Misc/NEWS:7267 +msgid "" +"`Issue #19509 `__: Add SSLContext." +"check_hostname to match the peer's certificate with server_hostname on " +"handshake." +msgstr "" + +#: ../../../Misc/NEWS:7270 +msgid "" +"`Issue #15798 `__: Fixed subprocess.Popen() " +"to no longer fail if file descriptor 0, 1 or 2 is closed." +msgstr "" + +#: ../../../Misc/NEWS:7273 +msgid "" +"`Issue #17897 `__: Optimized unpickle " +"prefetching." +msgstr "" + +#: ../../../Misc/NEWS:7275 +msgid "" +"`Issue #3693 `__: Make the error message more " +"helpful when the array.array() constructor is given a str. Move the array " +"module typecode documentation to the docstring of the constructor." +msgstr "" + +#: ../../../Misc/NEWS:7279 +msgid "" +"`Issue #19088 `__: Fixed incorrect caching of " +"the copyreg module in object.__reduce__() and object.__reduce_ex__()." +msgstr "" + +#: ../../../Misc/NEWS:7282 +msgid "" +"`Issue #19698 `__: Removed exec_module() " +"methods from importlib.machinery.BuiltinImporter and ExtensionFileLoader." +msgstr "" + +#: ../../../Misc/NEWS:7285 +msgid "" +"`Issue #18864 `__: Added a setter for " +"ModuleSpec.has_location." +msgstr "" + +#: ../../../Misc/NEWS:7287 +msgid "" +"Fixed _pickle.Unpickler to not fail when loading empty strings as persistent " +"IDs." +msgstr "" + +#: ../../../Misc/NEWS:7290 +msgid "" +"`Issue #11480 `__: Fixed copy.copy to work " +"with classes with custom metaclasses. Patch by Daniel Urban." +msgstr "" + +#: ../../../Misc/NEWS:7293 +msgid "" +"`Issue #6477 `__: Added support for pickling " +"the types of built-in singletons (i.e., Ellipsis, NotImplemented, None)." +msgstr "" + +#: ../../../Misc/NEWS:7296 +msgid "" +"`Issue #19713 `__: Add remaining PEP 451-" +"related deprecations and move away from using find_module/find_loaer/" +"load_module." +msgstr "" + +#: ../../../Misc/NEWS:7299 +msgid "" +"`Issue #19708 `__: Update pkgutil to use the " +"new importer APIs." +msgstr "" + +#: ../../../Misc/NEWS:7301 +msgid "" +"`Issue #19703 `__: Update pydoc to use the " +"new importer APIs." +msgstr "" + +#: ../../../Misc/NEWS:7303 +msgid "" +"`Issue #19851 `__: Fixed a regression in " +"reloading sub-modules." +msgstr "" + +#: ../../../Misc/NEWS:7305 +msgid "ssl.create_default_context() sets OP_NO_COMPRESSION to prevent CRIME." +msgstr "" + +#: ../../../Misc/NEWS:7307 +msgid "" +"`Issue #19802 `__: Add socket.SO_PRIORITY." +msgstr "" + +#: ../../../Misc/NEWS:7309 +msgid "" +"`Issue #11508 `__: Fixed uuid.getnode() and " +"uuid.uuid1() on environment with virtual interface. Original patch by Kent " +"Frazier." +msgstr "" + +#: ../../../Misc/NEWS:7312 +msgid "" +"`Issue #11489 `__: JSON decoder now accepts " +"lone surrogates." +msgstr "" + +#: ../../../Misc/NEWS:7314 +msgid "" +"`Issue #19545 `__: Avoid chained exceptions " +"while passing stray % to time.strptime(). Initial patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:7320 +msgid "" +"`Issue #20058 `__: sys.stdin.readline() in " +"IDLE now always returns only one line." +msgstr "" + +#: ../../../Misc/NEWS:7322 +msgid "" +"`Issue #19481 `__: print() of string subclass " +"instance in IDLE no longer hangs." +msgstr "" + +#: ../../../Misc/NEWS:7324 +msgid "" +"`Issue #18270 `__: Prevent possible IDLE " +"AttributeError on OS X when no initial shell window is present." +msgstr "" + +#: ../../../Misc/NEWS:7330 +msgid "" +"`Issue #20055 `__: Fix test_shutil under " +"Windows with symlink privileges held. Patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:7333 +msgid "" +"`Issue #20070 `__: Don't run test_urllib2net " +"when network resources are not enabled." +msgstr "" + +#: ../../../Misc/NEWS:7336 +msgid "" +"`Issue #19938 `__: Re-enabled " +"test_bug_1333982 in test_dis, which had been disabled since 3.0 due to the " +"changes in listcomp handling." +msgstr "" + +#: ../../../Misc/NEWS:7339 +msgid "" +"`Issue #19320 `__: test_tcl no longer fails " +"when wantobjects is false." +msgstr "" + +#: ../../../Misc/NEWS:7341 +msgid "" +"`Issue #19919 `__: Fix flaky SSL test. " +"connect_ex() sometimes returns EWOULDBLOCK on Windows or VMs hosted on " +"Windows." +msgstr "" + +#: ../../../Misc/NEWS:7344 +msgid "" +"`Issue #19912 `__: Added tests for ntpath." +"splitunc()." +msgstr "" + +#: ../../../Misc/NEWS:7346 +msgid "" +"`Issue #19828 `__: Fixed test_site when the " +"whole suite is run with -S." +msgstr "" + +#: ../../../Misc/NEWS:7348 +msgid "" +"`Issue #19928 `__: Implemented a test for " +"repr() of cell objects." +msgstr "" + +#: ../../../Misc/NEWS:7350 +msgid "" +"`Issue #19535 `__: Fixed test_docxmlrpc, " +"test_functools, test_inspect, and test_statistics when python is run with -" +"OO." +msgstr "" + +#: ../../../Misc/NEWS:7353 +msgid "" +"`Issue #19926 `__: Removed unneeded test_main " +"from test_abstract_numbers. Patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:7356 +msgid "" +"`Issue #19572 `__: More skipped tests " +"explicitly marked as skipped." +msgstr "" + +#: ../../../Misc/NEWS:7358 +msgid "" +"`Issue #19595 `__, #19987: Re-enabled a long-" +"disabled test in test_winsound." +msgstr "" + +#: ../../../Misc/NEWS:7360 +msgid "" +"`Issue #19588 `__: Fixed tests in test_random " +"that were silently skipped most of the time. Patch by Julian Gindi." +msgstr "" + +#: ../../../Misc/NEWS:7366 +msgid "" +"`Issue #19728 `__: Enable pip installation by " +"default on Windows." +msgstr "" + +#: ../../../Misc/NEWS:7368 +msgid "`Issue #16136 `__: Remove VMS support" +msgstr "" + +#: ../../../Misc/NEWS:7370 +msgid "" +"`Issue #18215 `__: Add script Tools/ssl/" +"test_multiple_versions.py to compile and run Python's unit tests with " +"multiple versions of OpenSSL." +msgstr "" + +#: ../../../Misc/NEWS:7373 +msgid "" +"`Issue #19922 `__: define " +"_INCLUDE__STDC_A1_SOURCE in HP-UX to include mbstate_t for mbrtowc()." +msgstr "" + +#: ../../../Misc/NEWS:7376 +msgid "" +"`Issue #19788 `__: kill_python(_d).exe is now " +"run as a PreBuildEvent on the pythoncore sub-project. This should prevent " +"build errors due a previous build's python(_d).exe still running." +msgstr "" + +#: ../../../Misc/NEWS:7383 +msgid "" +"`Issue #20265 `__: Updated some parts of the " +"Using Windows document." +msgstr "" + +#: ../../../Misc/NEWS:7385 +msgid "" +"`Issue #20266 `__: Updated some parts of the " +"Windows FAQ." +msgstr "" + +#: ../../../Misc/NEWS:7387 +msgid "" +"`Issue #20255 `__: Updated the about and bugs " +"pages." +msgstr "" + +#: ../../../Misc/NEWS:7389 +msgid "" +"`Issue #20253 `__: Fixed a typo in the " +"ipaddress docs that advertised an illegal attribute name. Found by INADA " +"Naoki." +msgstr "" + +#: ../../../Misc/NEWS:7392 +msgid "" +"`Issue #18840 `__: Introduce the json module " +"in the tutorial, and de-emphasize the pickle module." +msgstr "" + +#: ../../../Misc/NEWS:7395 +msgid "" +"`Issue #19845 `__: Updated the Compiling " +"Python on Windows section." +msgstr "" + +#: ../../../Misc/NEWS:7397 +msgid "" +"`Issue #19795 `__: Improved markup of True/" +"False constants." +msgstr "" + +#: ../../../Misc/NEWS:7402 +msgid "" +"`Issue #19659 `__: Added documentation for " +"Argument Clinic." +msgstr "" + +#: ../../../Misc/NEWS:7404 +msgid "" +"`Issue #19976 `__: Argument Clinic " +"METH_NOARGS functions now always take two parameters." +msgstr "" + +#: ../../../Misc/NEWS:7409 +msgid "Python 3.4.0 Beta 1" +msgstr "" + +#: ../../../Misc/NEWS:7411 +msgid "Release date: 2013-11-24" +msgstr "" + +#: ../../../Misc/NEWS:7416 +msgid "" +"Use the repr of a module name in more places in import, especially " +"exceptions." +msgstr "" + +#: ../../../Misc/NEWS:7419 +msgid "" +"`Issue #19619 `__: str.encode, bytes.decode " +"and bytearray.decode now use an internal API to throw LookupError for known " +"non-text encodings, rather than attempting the encoding or decoding " +"operation and then throwing a TypeError for an unexpected output type. (The " +"latter mechanism remains in place for third party non-text encodings)" +msgstr "" + +#: ../../../Misc/NEWS:7425 +msgid "" +"`Issue #19183 `__: Implement PEP 456 'secure " +"and interchangeable hash algorithm'. Python now uses SipHash24 on all major " +"platforms." +msgstr "" + +#: ../../../Misc/NEWS:7428 +msgid "" +"`Issue #12892 `__: The utf-16* and utf-32* " +"encoders no longer allow surrogate code points (U+D800-U+DFFF) to be " +"encoded. The utf-32* decoders no longer decode byte sequences that " +"correspond to surrogate code points. The surrogatepass error handler now " +"works with the utf-16* and utf-32* codecs. Based on patches by Victor " +"Stinner and Kang-Hao (Kenny) Lu." +msgstr "" + +#: ../../../Misc/NEWS:7434 +msgid "" +"`Issue #17806 `__: Added keyword-argument " +"support for \"tabsize\" to str/bytes.expandtabs()." +msgstr "" + +#: ../../../Misc/NEWS:7437 +msgid "" +"`Issue #17828 `__: Output type errors in str." +"encode(), bytes.decode() and bytearray.decode() now direct users to codecs." +"encode() or codecs.decode() as appropriate." +msgstr "" + +#: ../../../Misc/NEWS:7441 +msgid "" +"`Issue #17828 `__: The interpreter now " +"attempts to chain errors that occur in codec processing with a replacement " +"exception of the same type that includes the codec name in the error " +"message. It ensures it only does this when the creation of the replacement " +"exception won't lose any information." +msgstr "" + +#: ../../../Misc/NEWS:7446 +msgid "" +"`Issue #19466 `__: Clear the frames of daemon " +"threads earlier during the Python shutdown to call object destructors. So " +"\"unclosed file\" resource warnings are now correctly emitted for daemon " +"threads." +msgstr "" + +#: ../../../Misc/NEWS:7450 +msgid "" +"`Issue #19514 `__: Deduplicate some " +"_Py_IDENTIFIER declarations. Patch by Andrei Dorian Duma." +msgstr "" + +#: ../../../Misc/NEWS:7453 +msgid "" +"`Issue #17936 `__: Fix O(n**2) behaviour when " +"adding or removing many subclasses of a given type." +msgstr "" + +#: ../../../Misc/NEWS:7456 +msgid "" +"`Issue #19428 `__: zipimport now handles " +"errors when reading truncated or invalid ZIP archive." +msgstr "" + +#: ../../../Misc/NEWS:7459 +msgid "" +"`Issue #18408 `__: Add a new " +"PyFrame_FastToLocalsWithError() function to handle exceptions when merging " +"fast locals into f_locals of a frame. PyEval_GetLocals() now raises an " +"exception and return NULL on failure." +msgstr "" + +#: ../../../Misc/NEWS:7463 +msgid "" +"`Issue #19369 `__: Optimized the usage of " +"__length_hint__()." +msgstr "" + +#: ../../../Misc/NEWS:7465 +msgid "" +"`Issue #28026 `__: Raise ImportError when " +"exec_module() exists but create_module() is missing." +msgstr "" + +#: ../../../Misc/NEWS:7468 +msgid "" +"`Issue #18603 `__: Ensure that PyOS_mystricmp " +"and PyOS_mystrnicmp are in the Python executable and not removed by the " +"linker's optimizer." +msgstr "" + +#: ../../../Misc/NEWS:7471 +msgid "" +"`Issue #19306 `__: Add extra hints to the " +"faulthandler module's stack dumps that these are \"upside down\"." +msgstr "" + +#: ../../../Misc/NEWS:7477 +msgid "" +"`Issue #3158 `__: doctest can now find " +"doctests in functions and methods written in C." +msgstr "" + +#: ../../../Misc/NEWS:7480 +msgid "" +"`Issue #13477 `__: Added command line " +"interface to the tarfile module. Original patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:7483 +msgid "" +"`Issue #19674 `__: inspect.signature() now " +"produces a correct signature for some builtins." +msgstr "" + +#: ../../../Misc/NEWS:7486 +msgid "" +"`Issue #19722 `__: Added opcode." +"stack_effect(), which computes the stack effect of bytecode instructions." +msgstr "" + +#: ../../../Misc/NEWS:7489 +msgid "" +"`Issue #19735 `__: Implement private function " +"ssl._create_stdlib_context() to create SSLContext objects in Python's stdlib " +"module. It provides a single configuration point and makes use of SSLContext." +"load_default_certs()." +msgstr "" + +#: ../../../Misc/NEWS:7493 +msgid "" +"`Issue #16203 `__: Add re.fullmatch() " +"function and regex.fullmatch() method, which anchor the pattern at both ends " +"of the string to match. Original patch by Matthew Barnett." +msgstr "" + +#: ../../../Misc/NEWS:7497 +msgid "" +"`Issue #13592 `__: Improved the repr for " +"regular expression pattern objects. Based on patch by Hugo Lopes Tavares." +msgstr "" + +#: ../../../Misc/NEWS:7500 +msgid "" +"`Issue #19641 `__: Added the audioop." +"byteswap() function to convert big-endian samples to little-endian and vice " +"versa." +msgstr "" + +#: ../../../Misc/NEWS:7503 +msgid "" +"`Issue #15204 `__: Deprecated the 'U' mode in " +"file-like objects." +msgstr "" + +#: ../../../Misc/NEWS:7505 +msgid "" +"`Issue #17810 `__: Implement PEP 3154, pickle " +"protocol 4." +msgstr "" + +#: ../../../Misc/NEWS:7507 +msgid "" +"`Issue #19668 `__: Added support for the " +"cp1125 encoding." +msgstr "" + +#: ../../../Misc/NEWS:7509 +msgid "" +"`Issue #19689 `__: Add ssl." +"create_default_context() factory function. It creates a new SSLContext " +"object with secure default settings." +msgstr "" + +#: ../../../Misc/NEWS:7512 +msgid "" +"`Issue #19727 `__: os.utime(..., None) is now " +"potentially more precise under Windows." +msgstr "" + +#: ../../../Misc/NEWS:7515 +msgid "" +"`Issue #17201 `__: ZIP64 extensions now are " +"enabled by default. Patch by William Mallard." +msgstr "" + +#: ../../../Misc/NEWS:7518 +msgid "" +"`Issue #19292 `__: Add SSLContext." +"load_default_certs() to load default root CA certificates from default " +"stores or system stores. By default the method loads CA certs for " +"authentication of server certs." +msgstr "" + +#: ../../../Misc/NEWS:7522 +msgid "" +"`Issue #19673 `__: Add pathlib to the stdlib " +"as a provisional module (PEP 428)." +msgstr "" + +#: ../../../Misc/NEWS:7524 +msgid "" +"`Issue #16596 `__: pdb in a generator now " +"properly skips over yield and yield from rather than stepping out of the " +"generator into its caller. (This is essential for stepping through asyncio " +"coroutines.)" +msgstr "" + +#: ../../../Misc/NEWS:7528 +msgid "" +"`Issue #17916 `__: Added dis.Bytecode." +"from_traceback() and dis.Bytecode.current_offset to easily display \"current " +"instruction\" markers in the new disassembly API (Patch by Claudiu Popa)." +msgstr "" + +#: ../../../Misc/NEWS:7532 +msgid "" +"`Issue #19552 `__: venv now supports " +"bootstrapping pip into virtual environments" +msgstr "" + +#: ../../../Misc/NEWS:7534 +msgid "" +"`Issue #17134 `__: Finalize interface to " +"Windows' certificate store. Cert and CRL enumeration are now two functions. " +"enum_certificates() also returns purpose flags as set of OIDs." +msgstr "" + +#: ../../../Misc/NEWS:7538 +msgid "" +"`Issue #19555 `__: Restore sysconfig." +"get_config_var('SO'), (and the distutils equivalent) with a " +"DeprecationWarning pointing people at $EXT_SUFFIX." +msgstr "" + +#: ../../../Misc/NEWS:7541 +msgid "" +"`Issue #8813 `__: Add SSLContext.verify_flags " +"to change the verification flags of the context in order to enable " +"certification revocation list (CRL) checks or strict X509 rules." +msgstr "" + +#: ../../../Misc/NEWS:7545 +msgid "" +"`Issue #18294 `__: Fix the zlib module to " +"make it 64-bit safe." +msgstr "" + +#: ../../../Misc/NEWS:7547 +msgid "" +"`Issue #19682 `__: Fix compatibility issue " +"with old version of OpenSSL that was introduced by `Issue #18379 `__." +msgstr "" + +#: ../../../Misc/NEWS:7550 +msgid "" +"`Issue #14455 `__: plistlib now supports " +"binary plists and has an updated API." +msgstr "" + +#: ../../../Misc/NEWS:7552 +msgid "" +"`Issue #19633 `__: Fixed writing not " +"compressed 16- and 32-bit wave files on big-endian platforms." +msgstr "" + +#: ../../../Misc/NEWS:7555 +msgid "" +"`Issue #18379 `__: SSLSocket.getpeercert() " +"returns CA issuer AIA fields, OCSP and CRL distribution points." +msgstr "" + +#: ../../../Misc/NEWS:7558 +msgid "" +"`Issue #18138 `__: Implement cadata argument " +"of SSLContext.load_verify_location() to load CA certificates and CRL from " +"memory. It supports PEM and DER encoded strings." +msgstr "" + +#: ../../../Misc/NEWS:7562 +msgid "" +"`Issue #18775 `__: Add name and block_size " +"attribute to HMAC object. They now provide the same API elements as non-" +"keyed cryptographic hash functions." +msgstr "" + +#: ../../../Misc/NEWS:7565 +msgid "" +"`Issue #17276 `__: MD5 as default digestmod " +"for HMAC is deprecated. The HMAC module supports digestmod names, e.g. hmac." +"HMAC('sha1')." +msgstr "" + +#: ../../../Misc/NEWS:7568 +msgid "" +"`Issue #19449 `__: in csv's writerow, handle " +"non-string keys when generating the error message that certain keys are not " +"in the 'fieldnames' list." +msgstr "" + +#: ../../../Misc/NEWS:7571 +msgid "" +"`Issue #13633 `__: Added a new " +"convert_charrefs keyword arg to HTMLParser that, when True, automatically " +"converts all character references." +msgstr "" + +#: ../../../Misc/NEWS:7574 +msgid "" +"`Issue #2927 `__: Added the unescape() " +"function to the html module." +msgstr "" + +#: ../../../Misc/NEWS:7576 +msgid "" +"`Issue #8402 `__: Added the escape() function " +"to the glob module." +msgstr "" + +#: ../../../Misc/NEWS:7578 +msgid "" +"`Issue #17618 `__: Add Base85 and Ascii85 " +"encoding/decoding to the base64 module." +msgstr "" + +#: ../../../Misc/NEWS:7580 +msgid "" +"`Issue #19634 `__: time.strftime(\"%y\") now " +"raises a ValueError on AIX when given a year before 1900." +msgstr "" + +#: ../../../Misc/NEWS:7583 +msgid "" +"Fix test.support.bind_port() to not cause an error when Python was compiled " +"on a system with SO_REUSEPORT defined in the headers but run on a system " +"with an OS kernel that does not support that reasonably new socket option." +msgstr "" + +#: ../../../Misc/NEWS:7587 +msgid "" +"Fix compilation error under gcc of the ctypes module bundled libffi for arm." +msgstr "" + +#: ../../../Misc/NEWS:7589 +msgid "" +"`Issue #19448 `__: Add private API to SSL " +"module to lookup ASN.1 objects by OID, NID, short name and long name." +msgstr "" + +#: ../../../Misc/NEWS:7592 +msgid "" +"`Issue #19282 `__: dbm.open now supports the " +"context management protocol. (Initial patch by Claudiu Popa)" +msgstr "" + +#: ../../../Misc/NEWS:7595 +msgid "" +"`Issue #8311 `__: Added support for writing " +"any bytes-like objects in the aifc, sunau, and wave modules." +msgstr "" + +#: ../../../Misc/NEWS:7598 +msgid "" +"`Issue #5202 `__: Added support for unseekable " +"files in the wave module." +msgstr "" + +#: ../../../Misc/NEWS:7600 +msgid "" +"`Issue #19544 `__ and `Issue #1180 `__: Restore global option to ignore ~/.pydistutils.cfg " +"in Distutils, accidentally removed in backout of distutils2 changes." +msgstr "" + +#: ../../../Misc/NEWS:7604 +msgid "" +"`Issue #19523 `__: Closed FileHandler leak " +"which occurred when delay was set." +msgstr "" + +#: ../../../Misc/NEWS:7606 +msgid "" +"`Issue #19544 `__ and `Issue #6516 `__: Restore support for --user and --group parameters " +"to sdist command accidentally rolled back as part of the distutils2 rollback." +msgstr "" + +#: ../../../Misc/NEWS:7610 +msgid "" +"`Issue #13674 `__: Prevented time.strftime " +"from crashing on Windows when given a year before 1900 and a format of %y." +msgstr "" + +#: ../../../Misc/NEWS:7613 +msgid "" +"`Issue #19406 `__: implementation of the " +"ensurepip module (part of PEP 453). Patch by Donald Stufft and Nick Coghlan." +msgstr "" + +#: ../../../Misc/NEWS:7616 +msgid "" +"`Issue #19544 `__ and `Issue #6286 `__: Restore use of urllib over http allowing use of " +"http_proxy for Distutils upload command, a feature accidentally lost in the " +"rollback of distutils2." +msgstr "" + +#: ../../../Misc/NEWS:7620 +msgid "" +"`Issue #19544 `__ and `Issue #7457 `__: Restore the read_pkg_file method to distutils.dist." +"DistributionMetadata accidentally removed in the undo of distutils2." +msgstr "" + +#: ../../../Misc/NEWS:7624 +msgid "" +"`Issue #16685 `__: Added support for any " +"bytes-like objects in the audioop module. Removed support for strings." +msgstr "" + +#: ../../../Misc/NEWS:7627 +msgid "" +"`Issue #7171 `__: Add Windows implementation " +"of ``inet_ntop`` and ``inet_pton`` to socket module. Patch by Atsuo Ishimoto." +msgstr "" + +#: ../../../Misc/NEWS:7630 +msgid "" +"`Issue #19261 `__: Added support for writing " +"24-bit samples in the sunau module." +msgstr "" + +#: ../../../Misc/NEWS:7632 +msgid "" +"`Issue #1097797 `__: Added CP273 encoding, " +"used on IBM mainframes in Germany and Austria. Mapping provided by Michael " +"Bierenfeld." +msgstr "" + +#: ../../../Misc/NEWS:7635 +msgid "" +"`Issue #1575020 `__: Fixed support of 24-" +"bit wave files on big-endian platforms." +msgstr "" + +#: ../../../Misc/NEWS:7637 +msgid "" +"`Issue #19378 `__: Fixed a number of cases in " +"the dis module where the new \"file\" parameter was not being honoured " +"correctly" +msgstr "" + +#: ../../../Misc/NEWS:7640 +msgid "" +"`Issue #19378 `__: Removed the \"dis.Bytecode." +"show_info\" method" +msgstr "" + +#: ../../../Misc/NEWS:7642 +msgid "" +"`Issue #19378 `__: Renamed the \"dis.Bytecode." +"display_code\" method to \"dis.Bytecode.dis\" and converted it to returning " +"a string rather than printing output." +msgstr "" + +#: ../../../Misc/NEWS:7646 +msgid "" +"`Issue #19378 `__: the \"line_offset\" " +"parameter in the new \"dis.get_instructions\" API has been renamed to " +"\"first_line\" (and the default value and usage changed accordingly). This " +"should reduce confusion with the more common use of \"offset\" in the dis " +"docs to refer to bytecode offsets." +msgstr "" + +#: ../../../Misc/NEWS:7651 +msgid "" +"`Issue #18678 `__: Corrected spwd struct " +"member names in spwd module: sp_nam->sp_namp, and sp_pwd->sp_pwdp. The old " +"names are kept as extra structseq members, for backward compatibility." +msgstr "" + +#: ../../../Misc/NEWS:7655 +msgid "" +"`Issue #6157 `__: Fixed tkinter.Text.debug(). " +"tkinter.Text.bbox() now raises TypeError instead of TclError on wrong number " +"of arguments. Original patch by Guilherme Polo." +msgstr "" + +#: ../../../Misc/NEWS:7659 +msgid "" +"`Issue #10197 `__: Rework subprocess." +"get[status]output to use subprocess functionality and thus to work on " +"Windows. Patch by Nick Coghlan" +msgstr "" + +#: ../../../Misc/NEWS:7662 +msgid "" +"`Issue #6160 `__: The bbox() method of tkinter." +"Spinbox now returns a tuple of integers instead of a string. Based on patch " +"by Guilherme Polo." +msgstr "" + +#: ../../../Misc/NEWS:7665 +msgid "" +"`Issue #19403 `__: contextlib.redirect_stdout " +"is now reentrant" +msgstr "" + +#: ../../../Misc/NEWS:7667 +msgid "" +"`Issue #19286 `__: Directories in " +"``package_data`` are no longer added to the filelist, preventing failure " +"outlined in the ticket." +msgstr "" + +#: ../../../Misc/NEWS:7670 +msgid "" +"`Issue #19480 `__: HTMLParser now accepts all " +"valid start-tag names as defined by the HTML5 standard." +msgstr "" + +#: ../../../Misc/NEWS:7673 +msgid "" +"`Issue #15114 `__: The html.parser module now " +"raises a DeprecationWarning when the strict argument of HTMLParser or the " +"HTMLParser.error method are used." +msgstr "" + +#: ../../../Misc/NEWS:7676 +msgid "" +"`Issue #19410 `__: Undo the special-casing " +"removal of '' for importlib.machinery.FileFinder." +msgstr "" + +#: ../../../Misc/NEWS:7679 +msgid "" +"`Issue #19424 `__: Fix the warnings module to " +"accept filename containing surrogate characters." +msgstr "" + +#: ../../../Misc/NEWS:7682 +msgid "" +"`Issue #19435 `__: Fix directory traversal " +"attack on CGIHttpRequestHandler." +msgstr "" + +#: ../../../Misc/NEWS:7684 +msgid "" +"`Issue #19227 `__: Remove pthread_atfork() " +"handler. The handler was added to solve #18747 but has caused issues." +msgstr "" + +#: ../../../Misc/NEWS:7687 +msgid "" +"`Issue #19420 `__: Fix reference leak in " +"module initialization code of _hashopenssl.c" +msgstr "" + +#: ../../../Misc/NEWS:7690 +msgid "" +"`Issue #19329 `__: Optimized compiling " +"charsets in regular expressions." +msgstr "" + +#: ../../../Misc/NEWS:7692 +msgid "" +"`Issue #19227 `__: Try to fix deadlocks " +"caused by re-seeding then OpenSSL pseudo-random number generator on fork()." +msgstr "" + +#: ../../../Misc/NEWS:7695 +msgid "" +"`Issue #16037 `__: HTTPMessage.readheaders() " +"raises an HTTPException when more than 100 headers are read. Adapted from " +"patch by Jyrki Pulliainen." +msgstr "" + +#: ../../../Misc/NEWS:7698 +msgid "" +"`Issue #16040 `__: CVE-2013-1752: nntplib: " +"Limit maximum line lengths to 2048 to prevent readline() calls from " +"consuming too much memory. Patch by Jyrki Pulliainen." +msgstr "" + +#: ../../../Misc/NEWS:7702 +msgid "" +"`Issue #16041 `__: CVE-2013-1752: poplib: " +"Limit maximum line lengths to 2048 to prevent readline() calls from " +"consuming too much memory. Patch by Jyrki Pulliainen." +msgstr "" + +#: ../../../Misc/NEWS:7706 +msgid "" +"`Issue #17997 `__: Change behavior of ``ssl." +"match_hostname()`` to follow RFC 6125, for security reasons. It now doesn't " +"match multiple wildcards nor wildcards inside IDN fragments." +msgstr "" + +#: ../../../Misc/NEWS:7710 +msgid "" +"`Issue #16039 `__: CVE-2013-1752: Change use " +"of readline in imaplib module to limit line length. Patch by Emil Lind." +msgstr "" + +#: ../../../Misc/NEWS:7713 +msgid "" +"`Issue #19330 `__: the unnecessary wrapper " +"functions have been removed from the implementations of the new contextlib." +"redirect_stdout and contextlib.suppress context managers, which also ensures " +"they provide reasonable help() output on instances" +msgstr "" + +#: ../../../Misc/NEWS:7718 +msgid "" +"`Issue #19393 `__: Fix symtable.symtable " +"function to not be confused when there are functions or classes named \"top" +"\"." +msgstr "" + +#: ../../../Misc/NEWS:7721 +msgid "" +"`Issue #18685 `__: Restore re performance to " +"pre-PEP 393 levels." +msgstr "" + +#: ../../../Misc/NEWS:7723 +msgid "" +"`Issue #19339 `__: telnetlib module is now " +"using time.monotonic() when available to compute timeout." +msgstr "" + +#: ../../../Misc/NEWS:7726 +msgid "" +"`Issue #19399 `__: fix sporadic " +"test_subprocess failure." +msgstr "" + +#: ../../../Misc/NEWS:7728 +msgid "" +"`Issue #13234 `__: Fix os.listdir to work " +"with extended paths on Windows. Patch by Santoso Wijaya." +msgstr "" + +#: ../../../Misc/NEWS:7731 +msgid "" +"`Issue #19375 `__: The site module adding a " +"\"site-python\" directory to sys.path, if it exists, is now deprecated." +msgstr "" + +#: ../../../Misc/NEWS:7734 +msgid "" +"`Issue #19379 `__: Lazily import linecache in " +"the warnings module, to make startup with warnings faster until a warning " +"gets printed." +msgstr "" + +#: ../../../Misc/NEWS:7737 +msgid "" +"`Issue #19288 `__: Fixed the \"in\" operator " +"of dbm.gnu databases for string argument. Original patch by Arfrever " +"Frehtes Taifersar Arahesis." +msgstr "" + +#: ../../../Misc/NEWS:7740 +msgid "" +"`Issue #19287 `__: Fixed the \"in\" operator " +"of dbm.ndbm databases for string argument. Original patch by Arfrever " +"Frehtes Taifersar Arahesis." +msgstr "" + +#: ../../../Misc/NEWS:7743 +msgid "" +"`Issue #19327 `__: Fixed the working of " +"regular expressions with too big charset." +msgstr "" + +#: ../../../Misc/NEWS:7745 +msgid "" +"`Issue #17400 `__: New 'is_global' attribute " +"for ipaddress to tell if an address is allocated by IANA for global or " +"private networks." +msgstr "" + +#: ../../../Misc/NEWS:7748 +msgid "" +"`Issue #19350 `__: Increasing the test " +"coverage of macurl2path. Patch by Colin Williams." +msgstr "" + +#: ../../../Misc/NEWS:7751 +msgid "" +"`Issue #19365 `__: Optimized the parsing of " +"long replacement string in re.sub*() functions." +msgstr "" + +#: ../../../Misc/NEWS:7754 +msgid "" +"`Issue #19352 `__: Fix unittest discovery " +"when a module can be reached through several paths (e.g. under Debian/Ubuntu " +"with virtualenv)." +msgstr "" + +#: ../../../Misc/NEWS:7757 +msgid "" +"`Issue #15207 `__: Fix mimetypes to read from " +"correct part of Windows registry Original patch by Dave Chambers" +msgstr "" + +#: ../../../Misc/NEWS:7760 +msgid "" +"`Issue #16595 `__: Add prlimit() to resource " +"module." +msgstr "" + +#: ../../../Misc/NEWS:7762 +msgid "" +"`Issue #19324 `__: Expose Linux-specific " +"constants in resource module." +msgstr "" + +#: ../../../Misc/NEWS:7764 +msgid "Load SSL's error strings in hashlib." +msgstr "" + +#: ../../../Misc/NEWS:7766 +msgid "" +"`Issue #18527 `__: Upgrade internal copy of " +"zlib to 1.2.8." +msgstr "" + +#: ../../../Misc/NEWS:7768 +msgid "" +"`Issue #19274 `__: Add a filterfunc parameter " +"to PyZipFile.writepy." +msgstr "" + +#: ../../../Misc/NEWS:7770 +msgid "" +"`Issue #8964 `__: fix platform._sys_version to " +"handle IronPython 2.6+. Patch by Martin Matusiak." +msgstr "" + +#: ../../../Misc/NEWS:7773 +msgid "" +"`Issue #19413 `__: Restore pre-3.3 reload() " +"semantics of re-finding modules." +msgstr "" + +#: ../../../Misc/NEWS:7775 +msgid "" +"`Issue #18958 `__: Improve error message for " +"json.load(s) while passing a string that starts with a UTF-8 BOM." +msgstr "" + +#: ../../../Misc/NEWS:7778 +msgid "" +"`Issue #19307 `__: Improve error message for " +"json.load(s) while passing objects of the wrong type." +msgstr "" + +#: ../../../Misc/NEWS:7781 +msgid "" +"`Issue #16038 `__: CVE-2013-1752: ftplib: " +"Limit amount of data read by limiting the call to readline(). Original " +"patch by Michał Jastrzębski and Giampaolo Rodola." +msgstr "" + +#: ../../../Misc/NEWS:7785 +msgid "" +"`Issue #17087 `__: Improved the repr for " +"regular expression match objects." +msgstr "" + +#: ../../../Misc/NEWS:7790 +msgid "" +"`Issue #19664 `__: test_userdict's repr test " +"no longer depends on the order of dict elements." +msgstr "" + +#: ../../../Misc/NEWS:7793 +msgid "" +"`Issue #19440 `__: Clean up test_capi by " +"removing an unnecessary __future__ import, converting from test_main to " +"unittest.main, and running the _testcapi module tests as subTests of a " +"unittest TestCase method." +msgstr "" + +#: ../../../Misc/NEWS:7797 +msgid "" +"`Issue #19378 `__: the main dis module tests " +"are now run with both stdout redirection *and* passing an explicit file " +"parameter" +msgstr "" + +#: ../../../Misc/NEWS:7800 +msgid "" +"`Issue #19378 `__: removed the not-actually-" +"helpful assertInstructionMatches and assertBytecodeExactlyMatches helpers " +"from bytecode_helper" +msgstr "" + +#: ../../../Misc/NEWS:7803 +msgid "" +"`Issue #18702 `__: All skipped tests now " +"reported as skipped." +msgstr "" + +#: ../../../Misc/NEWS:7805 +msgid "" +"`Issue #19439 `__: interpreter embedding " +"tests are now executed on Windows (Patch by Zachary Ware)" +msgstr "" + +#: ../../../Misc/NEWS:7808 +msgid "" +"`Issue #19085 `__: Added basic tests for all " +"tkinter widget options." +msgstr "" + +#: ../../../Misc/NEWS:7810 +msgid "" +"`Issue #19384 `__: Fix test_py_compile for " +"root user, patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:7815 +msgid "" +"`Issue #18326 `__: Clarify that list.sort's " +"arguments are keyword-only. Also, attempt to reduce confusion in the " +"glossary by not saying there are different \"types\" of arguments and " +"parameters." +msgstr "" + +#: ../../../Misc/NEWS:7822 +msgid "" +"`Issue #19358 `__: \"make clinic\" now runs " +"the Argument Clinic preprocessor over all CPython source files." +msgstr "" + +#: ../../../Misc/NEWS:7825 +msgid "Update SQLite to 3.8.1, xz to 5.0.5, and Tcl/Tk to 8.6.1 on Windows." +msgstr "" + +#: ../../../Misc/NEWS:7827 +msgid "" +"`Issue #16632 `__: Enable DEP and ASLR on " +"Windows." +msgstr "" + +#: ../../../Misc/NEWS:7829 +msgid "" +"`Issue #17791 `__: Drop PREFIX and " +"EXEC_PREFIX definitions from PC/pyconfig.h" +msgstr "" + +#: ../../../Misc/NEWS:7831 +msgid "" +"Add workaround for VS 2010 nmake clean issue. VS 2010 doesn't set up PATH " +"for nmake.exe correctly." +msgstr "" + +#: ../../../Misc/NEWS:7834 +msgid "" +"`Issue #19550 `__: Implement Windows " +"installer changes of PEP 453 (ensurepip)." +msgstr "" + +#: ../../../Misc/NEWS:7836 +msgid "" +"`Issue #19520 `__: Fix compiler warning in " +"the _sha3 module on 32bit Windows." +msgstr "" + +#: ../../../Misc/NEWS:7838 +msgid "" +"`Issue #19356 `__: Avoid using a C variabled " +"named \"_self\", it's a reserved word in some C compilers." +msgstr "" + +#: ../../../Misc/NEWS:7841 +msgid "" +"`Issue #15792 `__: Correct build options on " +"Win64. Patch by Jeremy Kloth." +msgstr "" + +#: ../../../Misc/NEWS:7843 +msgid "" +"`Issue #19373 `__: Apply upstream change to " +"Tk 8.5.15 fixing OS X 10.9 screen refresh problem for OS X installer build." +msgstr "" + +#: ../../../Misc/NEWS:7846 +msgid "" +"`Issue #19649 `__: On OS X, the same set of " +"file names are now installed in bin directories for all configurations: non-" +"framework vs framework, and single arch vs universal builds. pythonx.y-32 " +"is now always installed for 64-bit/32-bit universal builds. The obsolete " +"and undocumented pythonw* symlinks are no longer installed anywhere." +msgstr "" + +#: ../../../Misc/NEWS:7852 +msgid "" +"`Issue #19553 `__: PEP 453 - \"make install\" " +"and \"make altinstall\" now install or upgrade pip by default, using the " +"bundled pip provided by the new ensurepip module. A new configure option, --" +"with-ensurepip[=upgrade|install|no], is available to override the default " +"ensurepip \"--upgrade\" option. The option can also be set with \"make " +"[alt]install ENSUREPIP=[upgrade|install|no]\"." +msgstr "" + +#: ../../../Misc/NEWS:7858 +msgid "" +"`Issue #19551 `__: PEP 453 - the OS X " +"installer now installs pip by default." +msgstr "" + +#: ../../../Misc/NEWS:7860 +msgid "" +"Update third-party libraries for OS X installers: xz 5.0.3 -> 5.0.5, SQLite " +"3.7.13 -> 3.8.1" +msgstr "" + +#: ../../../Misc/NEWS:7863 +msgid "" +"`Issue #15663 `__: Revert OS X installer " +"built-in Tcl/Tk support for 3.4.0b1. Some third-party projects, such as " +"Matplotlib and PIL/Pillow, depended on being able to build with Tcl and Tk " +"frameworks in /Library/Frameworks." +msgstr "" + +#: ../../../Misc/NEWS:7871 +msgid "" +"`Issue #19730 `__: Argument Clinic now " +"supports all the existing PyArg \"format units\" as legacy converters, as " +"well as two new features: \"self converters\" and the \"version\" directive." +msgstr "" + +#: ../../../Misc/NEWS:7875 +msgid "" +"`Issue #19552 `__: pyvenv now bootstraps pip " +"into virtual environments by default (pass --without-pip to request the old " +"behaviour)" +msgstr "" + +#: ../../../Misc/NEWS:7878 +msgid "" +"`Issue #19390 `__: Argument Clinic no longer " +"accepts malformed Python and C ids." +msgstr "" + +#: ../../../Misc/NEWS:7883 +msgid "Python 3.4.0 Alpha 4" +msgstr "" + +#: ../../../Misc/NEWS:7885 +msgid "Release date: 2013-10-20" +msgstr "" + +#: ../../../Misc/NEWS:7890 +msgid "" +"`Issue #19301 `__: Give classes and functions " +"that are explicitly marked global a global qualname." +msgstr "" + +#: ../../../Misc/NEWS:7893 +msgid "" +"`Issue #19279 `__: UTF-7 decoder no longer " +"produces illegal strings." +msgstr "" + +#: ../../../Misc/NEWS:7895 +msgid "" +"`Issue #16612 `__: Add \"Argument Clinic\", a " +"compile-time preprocessor for C files to generate argument parsing code. " +"(See PEP 436.)" +msgstr "" + +#: ../../../Misc/NEWS:7898 +msgid "" +"`Issue #18810 `__: Shift stat calls in " +"importlib.machinery.FileFinder such that the code is optimistic that if " +"something exists in a directory named exactly like the possible package " +"being searched for that it's in actuality a directory." +msgstr "" + +#: ../../../Misc/NEWS:7903 +msgid "" +"`Issue #18416 `__: importlib.machinery." +"PathFinder now treats '' as the cwd and importlib.machinery.FileFinder no " +"longer special-cases '' to '.'. This leads to modules imported from cwd to " +"now possess an absolute file path for __file__ (this does not affect modules " +"specified by path on the CLI but it does affect -m/runpy). It also allows " +"FileFinder to be more consistent by not having an edge case." +msgstr "" + +#: ../../../Misc/NEWS:7910 +msgid "" +"`Issue #4555 `__: All exported C symbols are " +"now prefixed with either \"Py\" or \"_Py\"." +msgstr "" + +#: ../../../Misc/NEWS:7913 +msgid "" +"`Issue #19219 `__: Speed up marshal.loads(), " +"and make pyc files slightly (5% to 10%) smaller." +msgstr "" + +#: ../../../Misc/NEWS:7916 +msgid "" +"`Issue #19221 `__: Upgrade Unicode database " +"to version 6.3.0." +msgstr "" + +#: ../../../Misc/NEWS:7918 +msgid "" +"`Issue #16742 `__: The result of the C " +"callback PyOS_ReadlineFunctionPointer must now be a string allocated by " +"PyMem_RawMalloc() or PyMem_RawRealloc() (or NULL if an error occurred), " +"instead of a string allocated by PyMem_Malloc() or PyMem_Realloc()." +msgstr "" + +#: ../../../Misc/NEWS:7923 +msgid "" +"`Issue #19199 `__: Remove ``PyThreadState." +"tick_counter`` field" +msgstr "" + +#: ../../../Misc/NEWS:7925 +msgid "" +"Fix macro expansion of _PyErr_OCCURRED(), and make sure to use it in at " +"least one place so as to avoid regressions." +msgstr "" + +#: ../../../Misc/NEWS:7928 +msgid "" +"`Issue #19087 `__: Improve bytearray " +"allocation in order to allow cheap popping of data at the front (slice " +"deletion)." +msgstr "" + +#: ../../../Misc/NEWS:7931 +msgid "" +"`Issue #19014 `__: memoryview.cast() is now " +"allowed on zero-length views." +msgstr "" + +#: ../../../Misc/NEWS:7933 +msgid "" +"`Issue #18690 `__: memoryview is now " +"automatically registered with collections.abc.Sequence" +msgstr "" + +#: ../../../Misc/NEWS:7936 +msgid "" +"`Issue #19078 `__: memoryview now correctly " +"supports the reversed builtin (Patch by Claudiu Popa)" +msgstr "" + +#: ../../../Misc/NEWS:7942 +msgid "" +"`Issue #17457 `__: unittest test discovery " +"now works with namespace packages. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:7945 +msgid "" +"`Issue #18235 `__: Fix the sysconfig " +"variables LDSHARED and BLDSHARED under AIX. Patch by David Edelsohn." +msgstr "" + +#: ../../../Misc/NEWS:7948 +msgid "" +"`Issue #18606 `__: Add the new \"statistics\" " +"module (PEP 450). Contributed by Steven D'Aprano." +msgstr "" + +#: ../../../Misc/NEWS:7951 +msgid "" +"`Issue #12866 `__: The audioop module now " +"supports 24-bit samples." +msgstr "" + +#: ../../../Misc/NEWS:7953 +msgid "" +"`Issue #19254 `__: Provide an optimized " +"Python implementation of pbkdf2_hmac." +msgstr "" + +#: ../../../Misc/NEWS:7955 +msgid "" +"Issues #19201, `Issue #19222 `__, `Issue " +"#19223 `__: Add \"x\" mode (exclusive " +"creation) in opening file to bz2, gzip and lzma modules. Patches by Tim " +"Heaney and Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:7959 +msgid "Fix a reference count leak in _sre." +msgstr "" + +#: ../../../Misc/NEWS:7961 +msgid "" +"`Issue #19262 `__: Initial check in of the " +"'asyncio' package (a.k.a. Tulip, a.k.a. PEP 3156). There are no docs yet, " +"and the PEP is slightly out of date with the code. This module will have " +"*provisional* status in Python 3.4." +msgstr "" + +#: ../../../Misc/NEWS:7966 +msgid "" +"`Issue #19276 `__: Fixed the wave module on " +"64-bit big-endian platforms." +msgstr "" + +#: ../../../Misc/NEWS:7968 +msgid "" +"`Issue #19266 `__: Rename the new-in-3.4 " +"``contextlib.ignore`` context manager to ``contextlib.suppress`` in order to " +"be more consistent with existing descriptions of that operation elsewhere in " +"the language and standard library documentation (Patch by Zero Piraeus)." +msgstr "" + +#: ../../../Misc/NEWS:7973 +msgid "" +"`Issue #18891 `__: Completed the new email " +"package (provisional) API additions by adding new classes EmailMessage, " +"MIMEPart, and ContentManager." +msgstr "" + +#: ../../../Misc/NEWS:7976 +msgid "" +"`Issue #18281 `__: Unused stat constants " +"removed from `tarfile`." +msgstr "" + +#: ../../../Misc/NEWS:7978 +msgid "" +"`Issue #18999 `__: Multiprocessing now " +"supports 'contexts' with the same API as the module, but bound to specified " +"start methods." +msgstr "" + +#: ../../../Misc/NEWS:7981 +msgid "" +"`Issue #18468 `__: The re.split, re.findall, " +"and re.sub functions and the group() and groups() methods of match object " +"now always return a string or a bytes object." +msgstr "" + +#: ../../../Misc/NEWS:7985 +msgid "" +"`Issue #18725 `__: The textwrap module now " +"supports truncating multiline text." +msgstr "" + +#: ../../../Misc/NEWS:7987 +msgid "" +"`Issue #18776 `__: atexit callbacks now " +"display their full traceback when they raise an exception." +msgstr "" + +#: ../../../Misc/NEWS:7990 +msgid "" +"`Issue #17827 `__: Add the missing " +"documentation for ``codecs.encode`` and ``codecs.decode``." +msgstr "" + +#: ../../../Misc/NEWS:7993 +msgid "" +"`Issue #19218 `__: Rename collections.abc to " +"_collections_abc in order to speed up interpreter start." +msgstr "" + +#: ../../../Misc/NEWS:7996 +msgid "" +"`Issue #18582 `__: Add 'pbkdf2_hmac' to the " +"hashlib module. It implements PKCS#5 password-based key derivation functions " +"with HMAC as pseudorandom function." +msgstr "" + +#: ../../../Misc/NEWS:7999 +msgid "" +"`Issue #19131 `__: The aifc module now " +"correctly reads and writes sampwidth of compressed streams." +msgstr "" + +#: ../../../Misc/NEWS:8002 +msgid "" +"`Issue #19209 `__: Remove import of copyreg " +"from the os module to speed up interpreter startup. stat_result and " +"statvfs_result are now hard-coded to reside in the os module." +msgstr "" + +#: ../../../Misc/NEWS:8006 +msgid "" +"`Issue #19205 `__: Don't import the 're' " +"module in site and sysconfig module to speed up interpreter start." +msgstr "" + +#: ../../../Misc/NEWS:8009 +msgid "" +"`Issue #9548 `__: Add a minimal \"_bootlocale" +"\" module that is imported by the _io module instead of the full locale " +"module." +msgstr "" + +#: ../../../Misc/NEWS:8012 +msgid "" +"`Issue #18764 `__: Remove the 'print' alias " +"for the PDB 'p' command so that it no longer shadows the print function." +msgstr "" + +#: ../../../Misc/NEWS:8015 +msgid "" +"`Issue #19158 `__: A rare race in " +"BoundedSemaphore could allow .release() too often." +msgstr "" + +#: ../../../Misc/NEWS:8018 +msgid "" +"`Issue #15805 `__: Add contextlib." +"redirect_stdout()." +msgstr "" + +#: ../../../Misc/NEWS:8020 +msgid "" +"`Issue #18716 `__: Deprecate the formatter " +"module." +msgstr "" + +#: ../../../Misc/NEWS:8022 +msgid "" +"`Issue #10712 `__: 2to3 has a new \"asserts\" " +"fixer that replaces deprecated names of unittest methods (e.g. " +"failUnlessEqual -> assertEqual)." +msgstr "" + +#: ../../../Misc/NEWS:8025 +msgid "" +"`Issue #18037 `__: 2to3 now escapes ``'\\u'`` " +"and ``'\\U'`` in native strings." +msgstr "" + +#: ../../../Misc/NEWS:8027 +msgid "" +"`Issue #17839 `__: base64.decodebytes and " +"base64.encodebytes now accept any object that exports a 1 dimensional array " +"of bytes (this means the same is now also true for base64_codec)" +msgstr "" + +#: ../../../Misc/NEWS:8031 +msgid "" +"`Issue #19132 `__: The pprint module now " +"supports compact mode." +msgstr "" + +#: ../../../Misc/NEWS:8033 +msgid "" +"`Issue #19137 `__: The pprint module now " +"correctly formats instances of set and frozenset subclasses." +msgstr "" + +#: ../../../Misc/NEWS:8036 +msgid "" +"`Issue #10042 `__: functools.total_ordering " +"now correctly handles NotImplemented being returned by the underlying " +"comparison function (Patch by Katie Miller)" +msgstr "" + +#: ../../../Misc/NEWS:8040 +msgid "" +"`Issue #19092 `__: contextlib.ExitStack now " +"correctly reraises exceptions from the __exit__ callbacks of inner context " +"managers (Patch by Hrvoje Nikšić)" +msgstr "" + +#: ../../../Misc/NEWS:8044 +msgid "" +"`Issue #12641 `__: Avoid passing \"-mno-cygwin" +"\" to the mingw32 compiler, except when necessary. Patch by Oscar Benjamin." +msgstr "" + +#: ../../../Misc/NEWS:8047 +msgid "" +"`Issue #5845 `__: In site.py, only load " +"readline history from ~/.python_history if no history has been read " +"already. This avoids double writes to the history file at shutdown." +msgstr "" + +#: ../../../Misc/NEWS:8051 +msgid "Properly initialize all fields of a SSL object after allocation." +msgstr "" + +#: ../../../Misc/NEWS:8053 +msgid "" +"`Issue #19095 `__: SSLSocket.getpeercert() " +"now raises ValueError when the SSL handshake hasn't been done." +msgstr "" + +#: ../../../Misc/NEWS:8056 +msgid "" +"`Issue #4366 `__: Fix building extensions on " +"all platforms when --enable-shared is used." +msgstr "" + +#: ../../../Misc/NEWS:8059 +msgid "" +"`Issue #19030 `__: Fixed `inspect.getmembers` " +"and `inspect.classify_class_attrs` to attempt activating descriptors before " +"falling back to a __dict__ search for faulty descriptors. `inspect." +"classify_class_attrs` no longer returns Attributes whose home class is None." +msgstr "" + +#: ../../../Misc/NEWS:8067 +msgid "" +"`Issue #1772673 `__: The type of `char*` " +"arguments now changed to `const char*`." +msgstr "" + +#: ../../../Misc/NEWS:8069 +msgid "" +"`Issue #16129 `__: Added a " +"`Py_SetStandardStreamEncoding` pre-initialization API to allow embedding " +"applications like Blender to force a particular encoding and error handler " +"for the standard IO streams (initial patch by Bastien Montagne)" +msgstr "" + +#: ../../../Misc/NEWS:8077 +msgid "" +"`Issue #19275 `__: Fix test_site on AMD64 " +"Snow Leopard" +msgstr "" + +#: ../../../Misc/NEWS:8079 +msgid "" +"`Issue #14407 `__: Fix unittest test " +"discovery in test_concurrent_futures." +msgstr "" + +#: ../../../Misc/NEWS:8081 +msgid "" +"`Issue #18919 `__: Unified and extended tests " +"for audio modules: aifc, sunau and wave." +msgstr "" + +#: ../../../Misc/NEWS:8084 +msgid "" +"`Issue #18714 `__: Added tests for ``pdb." +"find_function()``." +msgstr "" + +#: ../../../Misc/NEWS:8089 +msgid "" +"`Issue #18758 `__: Fixed and improved cross-" +"references." +msgstr "" + +#: ../../../Misc/NEWS:8091 +msgid "" +"`Issue #18972 `__: Modernize email examples " +"and use the argparse module in them." +msgstr "" + +#: ../../../Misc/NEWS:8096 +msgid "" +"`Issue #19130 `__: Correct PCbuild/readme." +"txt, Python 3.3 and 3.4 require VS 2010." +msgstr "" + +#: ../../../Misc/NEWS:8098 +msgid "" +"`Issue #15663 `__: Update OS X 10.6+ " +"installer to use Tcl/Tk 8.5.15." +msgstr "" + +#: ../../../Misc/NEWS:8104 +msgid "" +"`Issue #14499 `__: Fix several problems with " +"OS X universal build support:" +msgstr "" + +#: ../../../Misc/NEWS:8101 +msgid "ppc arch detection for extension module builds broke with Xcode 5" +msgstr "" + +#: ../../../Misc/NEWS:8102 +msgid "ppc arch detection in configure did not work on OS X 10.4" +msgstr "" + +#: ../../../Misc/NEWS:8103 +msgid "-sysroot and -arch flags were unnecessarily duplicated" +msgstr "" + +#: ../../../Misc/NEWS:8104 +msgid "there was no obvious way to configure an intel-32 only build." +msgstr "" + +#: ../../../Misc/NEWS:8106 +msgid "" +"`Issue #19019 `__: Change the OS X installer " +"build script to use CFLAGS instead of OPT for special build options. By " +"setting OPT, some compiler-specific options like -fwrapv were overridden and " +"thus not used, which could result in broken interpreters when building with " +"clang." +msgstr "" + +#: ../../../Misc/NEWS:8113 +msgid "Python 3.4.0 Alpha 3" +msgstr "" + +#: ../../../Misc/NEWS:8115 +msgid "Release date: 2013-09-29" +msgstr "" + +#: ../../../Misc/NEWS:8120 +msgid "" +"`Issue #18818 `__: The \"encodingname\" part " +"of PYTHONIOENCODING is now optional." +msgstr "" + +#: ../../../Misc/NEWS:8122 +msgid "" +"`Issue #19098 `__: Prevent overflow in the " +"compiler when the recursion limit is set absurdly high." +msgstr "" + +#: ../../../Misc/NEWS:8128 +msgid "" +"`Issue #18929 `__: `inspect." +"classify_class_attrs()` now correctly finds class attributes returned by " +"`dir()` that are located in the metaclass." +msgstr "" + +#: ../../../Misc/NEWS:8131 +msgid "" +"`Issue #18950 `__: Fix miscellaneous bugs in " +"the sunau module. Au_read.readframes() now updates current file position and " +"reads correct number of frames from multichannel stream. Au_write." +"writeframesraw() now correctly updates current file position. Au_read." +"getnframes() now returns an integer (as in Python 2). Au_read and Au_write " +"now correctly works with file object if start file position is not a zero." +msgstr "" + +#: ../../../Misc/NEWS:8138 +msgid "" +"`Issue #18594 `__: The fast path for " +"collections.Counter() was never taken due to an over-restrictive type check." +msgstr "" + +#: ../../../Misc/NEWS:8141 +msgid "" +"`Issue #19053 `__: ZipExtFile.read1() with " +"non-zero argument no more returns empty bytes until end of data." +msgstr "" + +#: ../../../Misc/NEWS:8144 +msgid "" +"logging: added support for Unix domain sockets to SocketHandler and " +"DatagramHandler." +msgstr "" + +#: ../../../Misc/NEWS:8147 +msgid "" +"`Issue #18996 `__: TestCase.assertEqual() now " +"more cleverly shorten differing strings in error report." +msgstr "" + +#: ../../../Misc/NEWS:8150 +msgid "" +"`Issue #19034 `__: repr() for tkinter.Tcl_Obj " +"now exposes string reperesentation." +msgstr "" + +#: ../../../Misc/NEWS:8152 +msgid "" +"`Issue #18978 `__: ``urllib.request.Request`` " +"now allows the method to be indicated on the class and no longer sets it to " +"None in ``__init__``." +msgstr "" + +#: ../../../Misc/NEWS:8155 +msgid "" +"`Issue #18626 `__: the inspect module now " +"offers a basic command line introspection interface (Initial patch by " +"Claudiu Popa)" +msgstr "" + +#: ../../../Misc/NEWS:8158 +msgid "" +"`Issue #3015 `__: Fixed tkinter with " +"wantobject=False. Any Tcl command call returned empty string." +msgstr "" + +#: ../../../Misc/NEWS:8161 +msgid "" +"`Issue #19037 `__: The mailbox module now " +"makes all changes to maildir files before moving them into place, to avoid " +"race conditions with other programs that may be accessing the maildir " +"directory." +msgstr "" + +#: ../../../Misc/NEWS:8165 +msgid "" +"`Issue #14984 `__: On POSIX systems, when " +"netrc is called without a filename argument (and therefore is reading the " +"user's $HOME/.netrc file), it now enforces the same security rules as " +"typical ftp clients: the .netrc file must be owned by the user that owns the " +"process and must not be readable by any other user." +msgstr "" + +#: ../../../Misc/NEWS:8171 +msgid "" +"`Issue #18873 `__: The tokenize module now " +"detects Python source code encoding only in comment lines." +msgstr "" + +#: ../../../Misc/NEWS:8174 +msgid "" +"`Issue #17764 `__: Enable http.server to bind " +"to a user specified network interface. Patch contributed by Malte Swart." +msgstr "" + +#: ../../../Misc/NEWS:8177 +msgid "" +"`Issue #18937 `__: Add an assertLogs() " +"context manager to unittest.TestCase to ensure that a block of code emits a " +"message using the logging module." +msgstr "" + +#: ../../../Misc/NEWS:8180 +msgid "" +"`Issue #17324 `__: Fix http.server's request " +"handling case on trailing '/'. Patch contributed by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:8183 +msgid "" +"`Issue #19018 `__: The heapq.merge() function " +"no longer suppresses IndexError in the underlying iterables." +msgstr "" + +#: ../../../Misc/NEWS:8186 +msgid "" +"`Issue #18784 `__: The uuid module no longer " +"attempts to load libc via ctypes.CDLL if all the necessary functions have " +"already been found in libuuid. Patch by Evgeny Sologubov." +msgstr "" + +#: ../../../Misc/NEWS:8190 +msgid "" +"The :envvar:`PYTHONFAULTHANDLER` environment variable now only enables the " +"faulthandler module if the variable is non-empty. Same behaviour than other " +"variables like :envvar:`PYTHONDONTWRITEBYTECODE`." +msgstr "" + +#: ../../../Misc/NEWS:8194 +msgid "" +"`Issue #1565525 `__: New function " +"``traceback.clear_frames`` will clear the local variables of all the stack " +"frames referenced by a traceback object." +msgstr "" + +#: ../../../Misc/NEWS:8201 +msgid "" +"`Issue #18952 `__: Fix regression in support " +"data downloads introduced when test.support was converted to a package. " +"Regression noticed by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:8208 +msgid "" +"`Issue #18873 `__: IDLE now detects Python " +"source code encoding only in comment lines." +msgstr "" + +#: ../../../Misc/NEWS:8211 +msgid "" +"`Issue #18988 `__: The \"Tab\" key now works " +"when a word is already autocompleted." +msgstr "" + +#: ../../../Misc/NEWS:8216 +msgid "" +"`Issue #17003 `__: Unified the size argument " +"names in the io module with common practice." +msgstr "" + +#: ../../../Misc/NEWS:8222 +msgid "" +"`Issue #18596 `__: Support the use of address " +"sanity checking in recent versions of clang and GCC by appropriately marking " +"known false alarms in the small object allocator. Patch contributed by Dhiru " +"Kholia." +msgstr "" + +#: ../../../Misc/NEWS:8229 +msgid "" +"`Issue #18873 `__: 2to3 and the findnocoding." +"py script now detect Python source code encoding only in comment lines." +msgstr "" + +#: ../../../Misc/NEWS:8234 +msgid "Python 3.4.0 Alpha 2" +msgstr "" + +#: ../../../Misc/NEWS:8236 +msgid "Release date: 2013-09-09" +msgstr "" + +#: ../../../Misc/NEWS:8241 +msgid "" +"`Issue #18942 `__: sys._debugmallocstats() " +"output was damaged on Windows." +msgstr "" + +#: ../../../Misc/NEWS:8243 +msgid "" +"`Issue #18571 `__: Implementation of the PEP " +"446: file descriptors and file handles are now created non-inheritable; add " +"functions os.get/set_inheritable(), os.get/set_handle_inheritable() and " +"socket.socket.get/set_inheritable()." +msgstr "" + +#: ../../../Misc/NEWS:8248 +msgid "" +"`Issue #11619 `__: The parser and the import " +"machinery do not encode Unicode filenames anymore on Windows." +msgstr "" + +#: ../../../Misc/NEWS:8251 +msgid "" +"`Issue #18808 `__: Non-daemon threads are now " +"automatically joined when a sub-interpreter is shutdown (it would previously " +"dump a fatal error)." +msgstr "" + +#: ../../../Misc/NEWS:8254 +msgid "Remove support for compiling on systems without getcwd()." +msgstr "" + +#: ../../../Misc/NEWS:8256 +msgid "" +"`Issue #18774 `__: Remove last bits of GNU " +"PTH thread code and thread_pth.h." +msgstr "" + +#: ../../../Misc/NEWS:8258 +msgid "" +"`Issue #18771 `__: Add optimization to set " +"object lookups to reduce the cost of hash collisions. The core idea is to " +"inspect a second key/hash pair for each cache line retrieved." +msgstr "" + +#: ../../../Misc/NEWS:8262 +msgid "" +"`Issue #16105 `__: When a signal handler " +"fails to write to the file descriptor registered with ``signal." +"set_wakeup_fd()``, report an exception instead of ignoring the error." +msgstr "" + +#: ../../../Misc/NEWS:8266 +msgid "" +"`Issue #18722 `__: Remove uses of the " +"\"register\" keyword in C code." +msgstr "" + +#: ../../../Misc/NEWS:8268 +msgid "" +"`Issue #18667 `__: Add missing \"HAVE_FCHOWNAT" +"\" symbol to posix._have_functions." +msgstr "" + +#: ../../../Misc/NEWS:8270 +msgid "" +"`Issue #16499 `__: Add command line option " +"for isolated mode." +msgstr "" + +#: ../../../Misc/NEWS:8272 +msgid "" +"`Issue #15301 `__: Parsing fd, uid, and gid " +"parameters for builtins in Modules/posixmodule.c is now far more robust." +msgstr "" + +#: ../../../Misc/NEWS:8275 +msgid "" +"`Issue #18368 `__: PyOS_StdioReadline() no " +"longer leaks memory when realloc() fail." +msgstr "" + +#: ../../../Misc/NEWS:8278 +msgid "" +"`Issue #17934 `__: Add a clear() method to " +"frame objects, to help clean up expensive details (local variables) and " +"break reference cycles." +msgstr "" + +#: ../../../Misc/NEWS:8281 +msgid "" +"`Issue #18780 `__: %-formatting codes %d, %i, " +"and %u now treat int-subclasses as int (displays value of int-subclass " +"instead of str(int-subclass) )." +msgstr "" + +#: ../../../Misc/NEWS:8287 +msgid "" +"`Issue #18808 `__: Thread.join() now waits " +"for the underlying thread state to be destroyed before returning. This " +"prevents unpredictable aborts in Py_EndInterpreter() when some non-daemon " +"threads are still running." +msgstr "" + +#: ../../../Misc/NEWS:8291 +msgid "" +"`Issue #18458 `__: Prevent crashes with newer " +"versions of libedit. Its readline emulation has changed from 0-based " +"indexing to 1-based like gnu readline." +msgstr "" + +#: ../../../Misc/NEWS:8294 +msgid "" +"`Issue #18852 `__: Handle case of ``readline." +"__doc__`` being ``None`` in the new readline activation code in ``site.py``." +msgstr "" + +#: ../../../Misc/NEWS:8297 +msgid "" +"`Issue #18672 `__: Fixed format specifiers " +"for Py_ssize_t in debugging output in the _sre module." +msgstr "" + +#: ../../../Misc/NEWS:8300 +msgid "" +"`Issue #18830 `__: inspect.getclasstree() no " +"longer produces duplicate entries even when input list contains duplicates." +msgstr "" + +#: ../../../Misc/NEWS:8303 +msgid "" +"`Issue #18878 `__: sunau.open now supports " +"the context management protocol. Based on patches by Claudiu Popa and R. " +"David Murray." +msgstr "" + +#: ../../../Misc/NEWS:8306 +msgid "" +"`Issue #18909 `__: Fix _tkinter.tkapp." +"interpaddr() on Windows 64-bit, don't cast 64-bit pointer to long (32 bits)." +msgstr "" + +#: ../../../Misc/NEWS:8309 +msgid "" +"`Issue #18876 `__: The FileIO.mode attribute " +"now better reflects the actual mode under which the file was opened. Patch " +"by Erik Bray." +msgstr "" + +#: ../../../Misc/NEWS:8312 +msgid "" +"`Issue #16853 `__: Add new selectors module." +msgstr "" + +#: ../../../Misc/NEWS:8314 +msgid "" +"`Issue #18882 `__: Add threading." +"main_thread() function." +msgstr "" + +#: ../../../Misc/NEWS:8316 +msgid "" +"`Issue #18901 `__: The sunau getparams method " +"now returns a namedtuple rather than a plain tuple. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:8319 +msgid "" +"`Issue #17487 `__: The result of the wave " +"getparams method now is pickleable again. Patch by Claudiu Popa." +msgstr "" + +#: ../../../Misc/NEWS:8322 +msgid "" +"`Issue #18756 `__: os.urandom() now uses a " +"lazily-opened persistent file descriptor, so as to avoid using many file " +"descriptors when run in parallel from multiple threads." +msgstr "" + +#: ../../../Misc/NEWS:8326 +msgid "" +"`Issue #18418 `__: After fork(), reinit all " +"threads states, not only active ones. Patch by A. Jesse Jiryu Davis." +msgstr "" + +#: ../../../Misc/NEWS:8329 +msgid "" +"`Issue #17974 `__: Switch unittest from using " +"getopt to using argparse." +msgstr "" + +#: ../../../Misc/NEWS:8331 +msgid "" +"`Issue #11798 `__: TestSuite now drops " +"references to own tests after execution." +msgstr "" + +#: ../../../Misc/NEWS:8333 +msgid "" +"`Issue #16611 `__: http.cookie now correctly " +"parses the 'secure' and 'httponly' cookie flags." +msgstr "" + +#: ../../../Misc/NEWS:8336 +msgid "" +"`Issue #11973 `__: Fix a problem in kevent. " +"The flags and fflags fields are now properly handled as unsigned." +msgstr "" + +#: ../../../Misc/NEWS:8339 +msgid "" +"`Issue #18807 `__: ``pyvenv`` now takes a --" +"copies argument allowing copies instead of symlinks even where symlinks are " +"available and the default." +msgstr "" + +#: ../../../Misc/NEWS:8342 +msgid "" +"`Issue #18538 `__: ``python -m dis`` now uses " +"argparse for argument processing. Patch by Michele Orrù." +msgstr "" + +#: ../../../Misc/NEWS:8345 +msgid "" +"`Issue #18394 `__: Close cgi.FieldStorage's " +"optional file." +msgstr "" + +#: ../../../Misc/NEWS:8347 +msgid "" +"`Issue #17702 `__: On error, os.environb now " +"suppresses the exception context when raising a new KeyError with the " +"original key." +msgstr "" + +#: ../../../Misc/NEWS:8350 +msgid "" +"`Issue #16809 `__: Fixed some tkinter " +"incompabilities with Tcl/Tk 8.6." +msgstr "" + +#: ../../../Misc/NEWS:8352 +msgid "" +"`Issue #16809 `__: Tkinter's splitlist() and " +"split() methods now accept Tcl_Obj argument." +msgstr "" + +#: ../../../Misc/NEWS:8355 +msgid "" +"`Issue #17211 `__: Yield a namedtuple in " +"pkgutil. Patch by Ramchandra Apte." +msgstr "" + +#: ../../../Misc/NEWS:8358 +msgid "" +"`Issue #18324 `__: set_payload now correctly " +"handles binary input. This also supersedes the previous fixes for #14360, " +"#1717, and #16564." +msgstr "" + +#: ../../../Misc/NEWS:8361 +msgid "" +"`Issue #18794 `__: Add a fileno() method and " +"a closed attribute to select.devpoll objects." +msgstr "" + +#: ../../../Misc/NEWS:8364 +msgid "" +"`Issue #17119 `__: Fixed integer overflows " +"when processing large strings and tuples in the tkinter module." +msgstr "" + +#: ../../../Misc/NEWS:8367 +msgid "" +"`Issue #15352 `__: Rebuild frozen modules " +"when marshal.c is changed." +msgstr "" + +#: ../../../Misc/NEWS:8369 +msgid "" +"`Issue #18747 `__: Re-seed OpenSSL's pseudo-" +"random number generator after fork. A pthread_atfork() parent handler is " +"used to seed the PRNG with pid, time and some stack data." +msgstr "" + +#: ../../../Misc/NEWS:8373 +msgid "" +"`Issue #8865 `__: Concurrent invocation of " +"select.poll.poll() now raises a RuntimeError exception. Patch by Christian " +"Schubert." +msgstr "" + +#: ../../../Misc/NEWS:8376 +msgid "" +"`Issue #18777 `__: The ssl module now uses " +"the new CRYPTO_THREADID API of OpenSSL 1.0.0+ instead of the deprecated " +"CRYPTO id callback function." +msgstr "" + +#: ../../../Misc/NEWS:8379 +msgid "" +"`Issue #18768 `__: Correct doc string of " +"RAND_edg(). Patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:8381 +msgid "" +"`Issue #18178 `__: Fix ctypes on BSD. " +"dlmalloc.c was compiled twice which broke malloc weak symbols." +msgstr "" + +#: ../../../Misc/NEWS:8384 +msgid "" +"`Issue #18709 `__: Fix CVE-2013-4238. The SSL " +"module now handles NULL bytes inside subjectAltName correctly. Formerly the " +"module has used OpenSSL's GENERAL_NAME_print() function to get the string " +"representation of ASN.1 strings for ``rfc822Name`` (email), ``dNSName`` " +"(DNS) and ``uniformResourceIdentifier`` (URI)." +msgstr "" + +#: ../../../Misc/NEWS:8390 +msgid "" +"`Issue #18701 `__: Remove support of old " +"CPython versions (<3.0) from C code." +msgstr "" + +#: ../../../Misc/NEWS:8392 +msgid "" +"`Issue #18756 `__: Improve error reporting in " +"os.urandom() when the failure is due to something else than /dev/urandom not " +"existing (for example, exhausting the file descriptor limit)." +msgstr "" + +#: ../../../Misc/NEWS:8396 +msgid "" +"`Issue #18673 `__: Add O_TMPFILE to os " +"module. O_TMPFILE requires Linux kernel 3.11 or newer. It's only defined on " +"system with 3.11 uapi headers, too." +msgstr "" + +#: ../../../Misc/NEWS:8399 +msgid "" +"`Issue #18532 `__: Change the builtin hash " +"algorithms' names to lower case names as promised by hashlib's documentation." +msgstr "" + +#: ../../../Misc/NEWS:8402 +msgid "" +"`Issue #8713 `__: add new spwan and forkserver " +"start methods, and new functions get_all_start_methods, get_start_method, " +"and set_start_method, to multiprocessing." +msgstr "" + +#: ../../../Misc/NEWS:8406 +msgid "" +"`Issue #18405 `__: Improve the entropy of " +"crypt.mksalt()." +msgstr "" + +#: ../../../Misc/NEWS:8408 +msgid "" +"`Issue #12015 `__: The tempfile module now " +"uses a suffix of 8 random characters instead of 6, to reduce the risk of " +"filename collision. The entropy was reduced when uppercase letters were " +"removed from the charset used to generate random characters." +msgstr "" + +#: ../../../Misc/NEWS:8413 +msgid "" +"`Issue #18585 `__: Add :func:`textwrap." +"shorten` to collapse and truncate a piece of text to a given length." +msgstr "" + +#: ../../../Misc/NEWS:8416 +msgid "" +"`Issue #18598 `__: Tweak exception message " +"for importlib.import_module() to include the module name when a key argument " +"is missing." +msgstr "" + +#: ../../../Misc/NEWS:8419 +msgid "" +"`Issue #19151 `__: Fix docstring and use of " +"_get_supported_file_loaders() to reflect 2-tuples." +msgstr "" + +#: ../../../Misc/NEWS:8422 +msgid "" +"`Issue #19152 `__: Add ExtensionFileLoader." +"get_filename()." +msgstr "" + +#: ../../../Misc/NEWS:8424 +msgid "" +"`Issue #18676 `__: Change 'positive' to 'non-" +"negative' in queue.py put and get docstrings and ValueError messages. Patch " +"by Zhongyue Luo" +msgstr "" + +#: ../../../Misc/NEWS:8427 +msgid "Fix refcounting issue with extension types in tkinter." +msgstr "" + +#: ../../../Misc/NEWS:8429 +msgid "" +"`Issue #8112 `__: xlmrpc.server's " +"DocXMLRPCServer server no longer raises an error if methods have " +"annotations; it now correctly displays the annotations." +msgstr "" + +#: ../../../Misc/NEWS:8432 +msgid "" +"`Issue #18600 `__: Added policy argument to " +"email.message.Message.as_string, and as_bytes and __bytes__ methods to " +"Message." +msgstr "" + +#: ../../../Misc/NEWS:8435 +msgid "" +"`Issue #18671 `__: Output more information " +"when logging exceptions occur." +msgstr "" + +#: ../../../Misc/NEWS:8437 +msgid "" +"`Issue #18621 `__: Prevent the site module's " +"patched builtins from keeping too many references alive for too long." +msgstr "" + +#: ../../../Misc/NEWS:8440 +msgid "" +"`Issue #4885 `__: Add weakref support to mmap " +"objects. Patch by Valerie Lambert." +msgstr "" + +#: ../../../Misc/NEWS:8442 +msgid "" +"`Issue #8860 `__: Fixed rounding in timedelta " +"constructor." +msgstr "" + +#: ../../../Misc/NEWS:8444 +msgid "" +"`Issue #18849 `__: Fixed a Windows-specific " +"tempfile bug where collision with an existing directory caused mkstemp and " +"related APIs to fail instead of retrying. Report and fix by Vlad Shcherbina." +msgstr "" + +#: ../../../Misc/NEWS:8448 +msgid "" +"`Issue #18920 `__: argparse's default " +"destination for the version action (-v, --version) has also been changed to " +"stdout, to match the Python executable." +msgstr "" + +#: ../../../Misc/NEWS:8454 +msgid "" +"`Issue #18623 `__: Factor out the " +"_SuppressCoreFiles context manager into test.support. Patch by Valerie " +"Lambert." +msgstr "" + +#: ../../../Misc/NEWS:8457 +msgid "" +"`Issue #12037 `__: Fix test_email for desktop " +"Windows." +msgstr "" + +#: ../../../Misc/NEWS:8459 +msgid "" +"`Issue #15507 `__: test_subprocess's " +"test_send_signal could fail if the test runner were run in an environment " +"where the process inherited an ignore setting for SIGINT. Restore the " +"SIGINT handler to the desired KeyboardInterrupt raising one during that test." +msgstr "" + +#: ../../../Misc/NEWS:8464 +msgid "" +"`Issue #16799 `__: Switched from getopt to " +"argparse style in regrtest's argument parsing. Added more tests for " +"regrtest's argument parsing." +msgstr "" + +#: ../../../Misc/NEWS:8467 +msgid "" +"`Issue #18792 `__: Use \"127.0.0.1\" or " +"\"::1\" instead of \"localhost\" as much as possible, since \"localhost\" " +"goes through a DNS lookup under recent Windows versions." +msgstr "" + +#: ../../../Misc/NEWS:8474 +msgid "" +"`Issue #18489 `__: Add tests for " +"SearchEngine. Original patch by Phil Webster." +msgstr "" + +#: ../../../Misc/NEWS:8479 +msgid "" +"`Issue #18743 `__: Fix references to non-" +"existent \"StringIO\" module." +msgstr "" + +#: ../../../Misc/NEWS:8481 +msgid "" +"`Issue #18783 `__: Removed existing mentions " +"of Python long type in docstrings, error messages and comments." +msgstr "" + +#: ../../../Misc/NEWS:8487 +msgid "" +"`Issue #1584 `__: Provide configure options to " +"override default search paths for Tcl and Tk when building _tkinter." +msgstr "" + +#: ../../../Misc/NEWS:8490 +msgid "" +"`Issue #15663 `__: Tcl/Tk 8.5.14 is now " +"included with the OS X 10.6+ 64-/32-bit installer. It is no longer " +"necessary to install a third-party version of Tcl/Tk 8.5 to work around the " +"problems in the Apple-supplied Tcl/Tk 8.5 shipped in OS X 10.6 and later " +"releases." +msgstr "" + +#: ../../../Misc/NEWS:8498 +msgid "" +"`Issue #18922 `__: Now The Lib/smtpd.py and " +"Tools/i18n/msgfmt.py scripts write their version strings to stdout, and not " +"to sderr." +msgstr "" + +#: ../../../Misc/NEWS:8503 +msgid "Python 3.4.0 Alpha 1" +msgstr "" + +#: ../../../Misc/NEWS:8505 +msgid "Release date: 2013-08-03" +msgstr "" + +#: ../../../Misc/NEWS:8510 +msgid "" +"`Issue #16741 `__: Fix an error reporting in " +"int()." +msgstr "" + +#: ../../../Misc/NEWS:8512 +msgid "" +"`Issue #17899 `__: Fix rare file descriptor " +"leak in os.listdir()." +msgstr "" + +#: ../../../Misc/NEWS:8514 +msgid "" +"`Issue #10241 `__: Clear extension module " +"dict copies at interpreter shutdown. Patch by Neil Schemenauer, minimally " +"modified." +msgstr "" + +#: ../../../Misc/NEWS:8517 +msgid "" +"`Issue #9035 `__: ismount now recognises " +"volumes mounted below a drive root on Windows. Original patch by Atsuo " +"Ishimoto." +msgstr "" + +#: ../../../Misc/NEWS:8520 +msgid "" +"`Issue #18214 `__: Improve finalization of " +"Python modules to avoid setting their globals to None, in most cases." +msgstr "" + +#: ../../../Misc/NEWS:8523 +msgid "" +"`Issue #18112 `__: PEP 442 implementation " +"(safe object finalization)." +msgstr "" + +#: ../../../Misc/NEWS:8525 +msgid "" +"`Issue #18552 `__: Check return value of " +"PyArena_AddPyObject() in obj2ast_object()." +msgstr "" + +#: ../../../Misc/NEWS:8528 +msgid "" +"`Issue #18560 `__: Fix potential NULL pointer " +"dereference in sum()." +msgstr "" + +#: ../../../Misc/NEWS:8530 +msgid "" +"`Issue #18520 `__: Add a new " +"PyStructSequence_InitType2() function, same than PyStructSequence_InitType() " +"except that it has a return value (0 on success, -1 on error)." +msgstr "" + +#: ../../../Misc/NEWS:8534 +msgid "" +"`Issue #15905 `__: Fix theoretical buffer " +"overflow in handling of sys.argv[0], prefix and exec_prefix if the operation " +"system does not obey MAXPATHLEN." +msgstr "" + +#: ../../../Misc/NEWS:8537 +msgid "" +"`Issue #18408 `__: Fix many various bugs in " +"code handling errors, especially on memory allocation failure (MemoryError)." +msgstr "" + +#: ../../../Misc/NEWS:8540 +msgid "" +"`Issue #18344 `__: Fix potential ref-leaks in " +"_bufferedreader_read_all()." +msgstr "" + +#: ../../../Misc/NEWS:8542 +msgid "" +"`Issue #18342 `__: Use the repr of a module " +"name when an import fails when using ``from ... import ...``." +msgstr "" + +#: ../../../Misc/NEWS:8545 +msgid "" +"`Issue #17872 `__: Fix a segfault in marshal." +"load() when input stream returns more bytes than requested." +msgstr "" + +#: ../../../Misc/NEWS:8548 +msgid "" +"`Issue #18338 `__: `python --version` now " +"prints version string to stdout, and not to stderr. Patch by Berker Peksag " +"and Michael Dickens." +msgstr "" + +#: ../../../Misc/NEWS:8551 +msgid "" +"`Issue #18426 `__: Fix NULL pointer " +"dereference in C extension import when PyModule_GetDef() returns an error." +msgstr "" + +#: ../../../Misc/NEWS:8554 +msgid "" +"`Issue #17206 `__: On Windows, increase the " +"stack size from 2 MB to 4.2 MB to fix a stack overflow in the marshal module " +"(fix a crash in test_marshal). Patch written by Jeremy Kloth." +msgstr "" + +#: ../../../Misc/NEWS:8558 +msgid "" +"`Issue #3329 `__: Implement the PEP 445: Add " +"new APIs to customize Python memory allocators." +msgstr "" + +#: ../../../Misc/NEWS:8561 +msgid "" +"`Issue #18328 `__: Reorder ops in " +"PyThreadState_Delete*() functions. Now the tstate is first removed from TLS " +"and then deallocated." +msgstr "" + +#: ../../../Misc/NEWS:8564 +msgid "" +"`Issue #13483 `__: Use VirtualAlloc in " +"obmalloc on Windows." +msgstr "" + +#: ../../../Misc/NEWS:8566 +msgid "" +"`Issue #18184 `__: PyUnicode_FromFormat() and " +"PyUnicode_FromFormatV() now raise OverflowError when an argument of %c " +"format is out of range." +msgstr "" + +#: ../../../Misc/NEWS:8569 +msgid "" +"`Issue #18111 `__: The min() and max() " +"functions now support a default argument to be returned instead of raising a " +"ValueError on an empty sequence. (Contributed by Julian Berman.)" +msgstr "" + +#: ../../../Misc/NEWS:8573 +msgid "" +"`Issue #18137 `__: Detect integer overflow on " +"precision in float.__format__() and complex.__format__()." +msgstr "" + +#: ../../../Misc/NEWS:8576 +msgid "" +"`Issue #15767 `__: Introduce " +"ModuleNotFoundError which is raised when a module could not be found." +msgstr "" + +#: ../../../Misc/NEWS:8579 +msgid "" +"`Issue #18183 `__: Fix various unicode " +"operations on strings with large unicode codepoints." +msgstr "" + +#: ../../../Misc/NEWS:8582 +msgid "" +"`Issue #18180 `__: Fix ref leak in " +"_PyImport_GetDynLoadWindows()." +msgstr "" + +#: ../../../Misc/NEWS:8584 +msgid "" +"`Issue #18038 `__: SyntaxError raised during " +"compilation sources with illegal encoding now always contains an encoding " +"name." +msgstr "" + +#: ../../../Misc/NEWS:8587 +msgid "" +"`Issue #17931 `__: Resolve confusion on " +"Windows between pids and process handles." +msgstr "" + +#: ../../../Misc/NEWS:8590 +msgid "" +"Tweak the exception message when the magic number or size value in a " +"bytecode file is truncated." +msgstr "" + +#: ../../../Misc/NEWS:8593 +msgid "" +"`Issue #17932 `__: Fix an integer overflow " +"issue on Windows 64-bit in iterators: change the C type of seqiterobject." +"it_index from long to Py_ssize_t." +msgstr "" + +#: ../../../Misc/NEWS:8596 +msgid "" +"`Issue #18065 `__: Don't set __path__ to the " +"package name for frozen packages." +msgstr "" + +#: ../../../Misc/NEWS:8598 +msgid "" +"`Issue #18088 `__: When reloading a module, " +"unconditionally reset all relevant attributes on the module (e.g. __name__, " +"__loader__, __package__, __file__, __cached__)." +msgstr "" + +#: ../../../Misc/NEWS:8602 +msgid "" +"`Issue #17937 `__: Try harder to collect " +"cyclic garbage at shutdown." +msgstr "" + +#: ../../../Misc/NEWS:8604 +msgid "" +"`Issue #12370 `__: Prevent class bodies from " +"interfering with the __class__ closure." +msgstr "" + +#: ../../../Misc/NEWS:8607 +msgid "" +"`Issue #17644 `__: Fix a crash in str.format " +"when curly braces are used in square brackets." +msgstr "" + +#: ../../../Misc/NEWS:8610 +msgid "" +"`Issue #17237 `__: Fix crash in the ASCII " +"decoder on m68k." +msgstr "" + +#: ../../../Misc/NEWS:8612 +msgid "" +"`Issue #17927 `__: Frame objects kept " +"arguments alive if they had been copied into a cell, even if the cell was " +"cleared." +msgstr "" + +#: ../../../Misc/NEWS:8615 +msgid "" +"`Issue #1545463 `__: At shutdown, defer " +"finalization of codec modules so that stderr remains usable." +msgstr "" + +#: ../../../Misc/NEWS:8618 +msgid "" +"`Issue #7330 `__: Implement width and " +"precision (ex: \"%5.3s\") for the format string of PyUnicode_FromFormat() " +"function, original patch written by Ysj Ray." +msgstr "" + +#: ../../../Misc/NEWS:8621 +msgid "" +"`Issue #1545463 `__: Global variables " +"caught in reference cycles are now garbage-collected at shutdown." +msgstr "" + +#: ../../../Misc/NEWS:8624 +msgid "" +"`Issue #17094 `__: Clear stale thread states " +"after fork(). Note that this is a potentially disruptive change since it " +"may release some system resources which would otherwise remain perpetually " +"alive (e.g. database connections kept in thread-local storage)." +msgstr "" + +#: ../../../Misc/NEWS:8629 +msgid "" +"`Issue #17408 `__: Avoid using an obsolete " +"instance of the copyreg module when the interpreter is shutdown and then " +"started again." +msgstr "" + +#: ../../../Misc/NEWS:8632 +msgid "" +"`Issue #5845 `__: Enable tab-completion in the " +"interactive interpreter by default, thanks to a new sys.__interactivehook__." +msgstr "" + +#: ../../../Misc/NEWS:8635 +msgid "" +"`Issue #17115 `__,17116: Module " +"initialization now includes setting __package__ and __loader__ attributes to " +"None." +msgstr "" + +#: ../../../Misc/NEWS:8638 +msgid "" +"`Issue #17853 `__: Ensure locals of a class " +"that shadow free variables always win over the closures." +msgstr "" + +#: ../../../Misc/NEWS:8641 +msgid "" +"`Issue #17863 `__: In the interactive " +"console, don't loop forever if the encoding can't be fetched from stdin." +msgstr "" + +#: ../../../Misc/NEWS:8644 +msgid "" +"`Issue #17867 `__: Raise an ImportError if " +"__import__ is not found in __builtins__." +msgstr "" + +#: ../../../Misc/NEWS:8646 +msgid "" +"`Issue #18698 `__: Ensure importlib.reload() " +"returns the module out of sys.modules." +msgstr "" + +#: ../../../Misc/NEWS:8648 +msgid "" +"`Issue #17857 `__: Prevent build failures " +"with pre-3.5.0 versions of sqlite3, such as was shipped with Centos 5 and " +"Mac OS X 10.4." +msgstr "" + +#: ../../../Misc/NEWS:8651 +msgid "" +"`Issue #17413 `__: sys.settrace callbacks " +"were being passed a string instead of an exception instance for the 'value' " +"element of the arg tuple if the exception originated from C code; now an " +"exception instance is always provided." +msgstr "" + +#: ../../../Misc/NEWS:8655 +msgid "" +"`Issue #17782 `__: Fix undefined behaviour on " +"platforms where ``struct timespec``'s \"tv_nsec\" member is not a C long." +msgstr "" + +#: ../../../Misc/NEWS:8658 +msgid "" +"`Issue #17722 `__: When looking up __round__, " +"resolve descriptors." +msgstr "" + +#: ../../../Misc/NEWS:8660 +msgid "" +"`Issue #16061 `__: Speed up str.replace() for " +"replacing 1-character strings." +msgstr "" + +#: ../../../Misc/NEWS:8662 +msgid "" +"`Issue #17715 `__: Fix segmentation fault " +"from raising an exception in a __trunc__ method." +msgstr "" + +#: ../../../Misc/NEWS:8665 +msgid "" +"`Issue #17643 `__: Add __callback__ attribute " +"to weakref.ref." +msgstr "" + +#: ../../../Misc/NEWS:8667 +msgid "" +"`Issue #16447 `__: Fixed potential " +"segmentation fault when setting __name__ on a class." +msgstr "" + +#: ../../../Misc/NEWS:8670 +msgid "" +"`Issue #17669 `__: Fix crash involving " +"finalization of generators using yield from." +msgstr "" + +#: ../../../Misc/NEWS:8672 +msgid "" +"`Issue #14439 `__: Python now prints the " +"traceback on runpy failure at startup." +msgstr "" + +#: ../../../Misc/NEWS:8674 +msgid "" +"`Issue #17469 `__: Fix " +"_Py_GetAllocatedBlocks() and sys.getallocatedblocks() when running on " +"valgrind." +msgstr "" + +#: ../../../Misc/NEWS:8677 +msgid "" +"`Issue #17619 `__: Make input() check for " +"Ctrl-C correctly on Windows." +msgstr "" + +#: ../../../Misc/NEWS:8679 +msgid "" +"`Issue #17357 `__: Add missing verbosity " +"messages for -v/-vv that were lost during the importlib transition." +msgstr "" + +#: ../../../Misc/NEWS:8682 +msgid "" +"`Issue #17610 `__: Don't rely on non-standard " +"behavior of the C qsort() function." +msgstr "" + +#: ../../../Misc/NEWS:8684 +msgid "" +"`Issue #17323 `__: The \"[X refs, Y blocks]\" " +"printed by debug builds has been disabled by default. It can be re-enabled " +"with the `-X showrefcount` option." +msgstr "" + +#: ../../../Misc/NEWS:8687 +msgid "" +"`Issue #17328 `__: Fix possible refleak in " +"dict.setdefault." +msgstr "" + +#: ../../../Misc/NEWS:8689 +msgid "" +"`Issue #17275 `__: Corrected class name in " +"init error messages of the C version of BufferedWriter and BufferedRandom." +msgstr "" + +#: ../../../Misc/NEWS:8692 +msgid "" +"`Issue #7963 `__: Fixed misleading error " +"message that issued when object is called without arguments." +msgstr "" + +#: ../../../Misc/NEWS:8695 +msgid "" +"`Issue #8745 `__: Small speed up zipimport on " +"Windows. Patch by Catalin Iacob." +msgstr "" + +#: ../../../Misc/NEWS:8697 +msgid "" +"`Issue #5308 `__: Raise ValueError when " +"marshalling too large object (a sequence with size >= 2**31), instead of " +"producing illegal marshal data." +msgstr "" + +#: ../../../Misc/NEWS:8700 +msgid "" +"`Issue #12983 `__: Bytes literals with " +"invalid ``\\x`` escape now raise a SyntaxError and a full traceback " +"including line number." +msgstr "" + +#: ../../../Misc/NEWS:8703 +msgid "" +"`Issue #16967 `__: In function definition, " +"evaluate positional defaults before keyword-only defaults." +msgstr "" + +#: ../../../Misc/NEWS:8706 +msgid "" +"`Issue #17173 `__: Remove uses of locale-" +"dependent C functions (isalpha() etc.) in the interpreter." +msgstr "" + +#: ../../../Misc/NEWS:8709 +msgid "" +"`Issue #17137 `__: When a Unicode string is " +"resized, the internal wide character string (wstr) format is now cleared." +msgstr "" + +#: ../../../Misc/NEWS:8712 +msgid "" +"`Issue #17043 `__: The unicode-internal " +"decoder no longer read past the end of input buffer." +msgstr "" + +#: ../../../Misc/NEWS:8715 +msgid "" +"`Issue #17098 `__: All modules now have " +"__loader__ set even if they pre-exist the bootstrapping of importlib." +msgstr "" + +#: ../../../Misc/NEWS:8718 +msgid "" +"`Issue #16979 `__: Fix error handling bugs in " +"the unicode-escape-decode decoder." +msgstr "" + +#: ../../../Misc/NEWS:8720 +msgid "" +"`Issue #16772 `__: The base argument to the " +"int constructor no longer accepts floats, or other non-integer objects with " +"an __int__ method. Objects with an __index__ method are now accepted." +msgstr "" + +#: ../../../Misc/NEWS:8724 +msgid "" +"`Issue #10156 `__: In the interpreter's " +"initialization phase, unicode globals are now initialized dynamically as " +"needed." +msgstr "" + +#: ../../../Misc/NEWS:8727 +msgid "" +"`Issue #16980 `__: Fix processing of escaped " +"non-ascii bytes in the unicode-escape-decode decoder." +msgstr "" + +#: ../../../Misc/NEWS:8730 +msgid "" +"`Issue #16975 `__: Fix error handling bug in " +"the escape-decode bytes decoder." +msgstr "" + +#: ../../../Misc/NEWS:8732 +msgid "" +"`Issue #14850 `__: Now a charmap decoder " +"treats U+FFFE as \"undefined mapping\" in any mapping, not only in a string." +msgstr "" + +#: ../../../Misc/NEWS:8735 +msgid "" +"`Issue #16613 `__: Add *m* argument to " +"``collections.Chainmap.new_child`` to allow the new child map to be " +"specified explicitly." +msgstr "" + +#: ../../../Misc/NEWS:8738 +msgid "" +"`Issue #16730 `__: importlib.machinery." +"FileFinder now no longers raises an exception when trying to populate its " +"cache and it finds out the directory is unreadable or has turned into a " +"file. Reported and diagnosed by David Pritchard." +msgstr "" + +#: ../../../Misc/NEWS:8743 +msgid "" +"`Issue #16906 `__: Fix a logic error that " +"prevented most static strings from being cleared." +msgstr "" + +#: ../../../Misc/NEWS:8746 +msgid "" +"`Issue #11461 `__: Fix the incremental UTF-16 " +"decoder. Original patch by Amaury Forgeot d'Arc." +msgstr "" + +#: ../../../Misc/NEWS:8749 +msgid "" +"`Issue #16856 `__: Fix a segmentation fault " +"from calling repr() on a dict with a key whose repr raise an exception." +msgstr "" + +#: ../../../Misc/NEWS:8752 +msgid "" +"`Issue #16367 `__: Fix FileIO.readall() on " +"Windows for files larger than 2 GB." +msgstr "" + +#: ../../../Misc/NEWS:8754 +msgid "" +"`Issue #16761 `__: Calling int() with base " +"argument only now raises TypeError." +msgstr "" + +#: ../../../Misc/NEWS:8756 +msgid "" +"`Issue #16759 `__: Support the full DWORD " +"(unsigned long) range in Reg2Py when retrieving a REG_DWORD value. This " +"corrects functions like winreg.QueryValueEx that may have been returning " +"truncated values." +msgstr "" + +#: ../../../Misc/NEWS:8760 +msgid "" +"`Issue #14420 `__: Support the full DWORD " +"(unsigned long) range in Py2Reg when passed a REG_DWORD value. Fixes " +"OverflowError in winreg.SetValueEx." +msgstr "" + +#: ../../../Misc/NEWS:8763 +msgid "" +"`Issue #11939 `__: Set the st_dev attribute " +"of stat_result to allow Windows to take advantage of the os.path.samefile/" +"sameopenfile/samestat implementations used by other platforms." +msgstr "" + +#: ../../../Misc/NEWS:8767 +msgid "" +"`Issue #16772 `__: The int() constructor's " +"second argument (base) no longer accepts non integer values. Consistent " +"with the behavior in Python 2." +msgstr "" + +#: ../../../Misc/NEWS:8770 +msgid "" +"`Issue #14470 `__: Remove w9xpopen support " +"per PEP 11." +msgstr "" + +#: ../../../Misc/NEWS:8772 +msgid "" +"`Issue #9856 `__: Replace deprecation warning " +"with raising TypeError in object.__format__. Patch by Florent Xicluna." +msgstr "" + +#: ../../../Misc/NEWS:8775 +msgid "" +"`Issue #16597 `__: In buffered and text IO, " +"call close() on the underlying stream if invoking flush() fails." +msgstr "" + +#: ../../../Misc/NEWS:8778 +msgid "" +"`Issue #16722 `__: In the bytes() " +"constructor, try to call __bytes__ on the argument before __index__." +msgstr "" + +#: ../../../Misc/NEWS:8781 +msgid "" +"`Issue #16421 `__: loading multiple modules " +"from one shared object is now handled correctly (previously, the first " +"module loaded from that file was silently returned). Patch by Václav " +"Šmilauer." +msgstr "" + +#: ../../../Misc/NEWS:8785 +msgid "" +"`Issue #16602 `__: When a weakref's target " +"was part of a long deallocation chain, the object could remain reachable " +"through its weakref even though its refcount had dropped to zero." +msgstr "" + +#: ../../../Misc/NEWS:8789 +msgid "" +"`Issue #16495 `__: Remove extraneous NULL " +"encoding check from bytes_decode()." +msgstr "" + +#: ../../../Misc/NEWS:8791 +msgid "" +"`Issue #16619 `__: Create NameConstant AST " +"class to represent None, True, and False literals. As a result, these " +"constants are never loaded at runtime from builtins." +msgstr "" + +#: ../../../Misc/NEWS:8795 +msgid "" +"`Issue #16455 `__: On FreeBSD and Solaris, if " +"the locale is C, the ASCII/surrogateescape codec is now used (instead of the " +"locale encoding) to decode the command line arguments. This change fixes " +"inconsistencies with os.fsencode() and os.fsdecode(), because these " +"operating systems announce an ASCII locale encoding, but actually use the " +"ISO-8859-1 encoding in practice." +msgstr "" + +#: ../../../Misc/NEWS:8801 +msgid "" +"`Issue #16562 `__: Optimize dict equality " +"testing. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8803 +msgid "" +"`Issue #16588 `__: Silence unused-but-set " +"warnings in Python/thread_pthread" +msgstr "" + +#: ../../../Misc/NEWS:8805 +msgid "" +"`Issue #16592 `__: stringlib_bytes_join " +"doesn't raise MemoryError on allocation failure." +msgstr "" + +#: ../../../Misc/NEWS:8808 +msgid "" +"`Issue #16546 `__: Fix: ast.YieldFrom " +"argument is now mandatory." +msgstr "" + +#: ../../../Misc/NEWS:8810 +msgid "" +"`Issue #16514 `__: Fix regression causing a " +"traceback when sys.path[0] is None (actually, any non-string or non-bytes " +"type)." +msgstr "" + +#: ../../../Misc/NEWS:8813 +msgid "" +"`Issue #16306 `__: Fix multiple error " +"messages when unknown command line parameters where passed to the " +"interpreter. Patch by Hieu Nguyen." +msgstr "" + +#: ../../../Misc/NEWS:8816 +msgid "" +"`Issue #16215 `__: Fix potential double " +"memory free in str.replace(). Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8819 +msgid "" +"`Issue #16290 `__: A float return value from " +"the __complex__ special method is no longer accepted in the complex() " +"constructor." +msgstr "" + +#: ../../../Misc/NEWS:8822 +msgid "" +"`Issue #16416 `__: On Mac OS X, operating " +"system data are now always encoded/decoded to/from UTF-8/surrogateescape, " +"instead of the locale encoding (which may be ASCII if no locale environment " +"variable is set), to avoid inconsistencies with os.fsencode() and os." +"fsdecode() functions which are already using UTF-8/surrogateescape." +msgstr "" + +#: ../../../Misc/NEWS:8828 +msgid "" +"`Issue #16453 `__: Fix equality testing of " +"dead weakref objects." +msgstr "" + +#: ../../../Misc/NEWS:8830 +msgid "" +"`Issue #9535 `__: Fix pending signals that " +"have been received but not yet handled by Python to not persist after os." +"fork() in the child process." +msgstr "" + +#: ../../../Misc/NEWS:8833 +msgid "" +"`Issue #14794 `__: Fix slice.indices to " +"return correct results for huge values, rather than raising OverflowError." +msgstr "" + +#: ../../../Misc/NEWS:8836 +msgid "" +"`Issue #15001 `__: fix segfault on \"del sys." +"modules['__main__']\". Patch by Victor Stinner." +msgstr "" + +#: ../../../Misc/NEWS:8839 +msgid "" +"`Issue #8271 `__: the utf-8 decoder now " +"outputs the correct number of U+FFFD characters when used with the 'replace' " +"error handler on invalid utf-8 sequences. Patch by Serhiy Storchaka, tests " +"by Ezio Melotti." +msgstr "" + +#: ../../../Misc/NEWS:8843 +msgid "" +"`Issue #5765 `__: Apply a hard recursion limit " +"in the compiler instead of blowing the stack and segfaulting. Initial patch " +"by Andrea Griffini." +msgstr "" + +#: ../../../Misc/NEWS:8846 +msgid "" +"`Issue #16402 `__: When slicing a range, fix " +"shadowing of exceptions from __index__." +msgstr "" + +#: ../../../Misc/NEWS:8849 +msgid "" +"`Issue #16336 `__: fix input checking in the " +"surrogatepass error handler. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8852 +msgid "" +"`Issue #8401 `__: assigning an int to a " +"bytearray slice (e.g. b[3:4] = 5) now raises an error." +msgstr "" + +#: ../../../Misc/NEWS:8855 +msgid "" +"`Issue #7317 `__: Display full tracebacks when " +"an error occurs asynchronously. Patch by Alon Horev with update by Alexey " +"Kachayev." +msgstr "" + +#: ../../../Misc/NEWS:8858 +msgid "" +"`Issue #16309 `__: Make PYTHONPATH=\"\" " +"behavior the same as if PYTHONPATH not set at all." +msgstr "" + +#: ../../../Misc/NEWS:8861 +msgid "" +"`Issue #10189 `__: Improve the error " +"reporting of SyntaxErrors related to global and nonlocal statements." +msgstr "" + +#: ../../../Misc/NEWS:8864 +msgid "" +"Fix segfaults on setting __qualname__ on builtin types and attempting to " +"delete it on any type." +msgstr "" + +#: ../../../Misc/NEWS:8867 +msgid "" +"`Issue #14625 `__: Rewrite the UTF-32 " +"decoder. It is now 3x to 4x faster. Patch written by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8870 +msgid "" +"`Issue #16345 `__: Fix an infinite loop when " +"``fromkeys`` on a dict subclass received a nonempty dict from the " +"constructor." +msgstr "" + +#: ../../../Misc/NEWS:8873 +msgid "" +"`Issue #16271 `__: Fix strange bugs that " +"resulted from __qualname__ appearing in a class's __dict__ and on type." +msgstr "" + +#: ../../../Misc/NEWS:8876 +msgid "" +"`Issue #12805 `__: Make bytes.join and " +"bytearray.join faster when the separator is empty. Patch by Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8879 +msgid "" +"`Issue #6074 `__: Ensure cached bytecode files " +"can always be updated by the user that created them, even when the source " +"file is read-only." +msgstr "" + +#: ../../../Misc/NEWS:8882 +msgid "" +"`Issue #15958 `__: bytes.join and bytearray." +"join now accept arbitrary buffer objects." +msgstr "" + +#: ../../../Misc/NEWS:8885 +msgid "" +"`Issue #14783 `__: Improve int() docstring " +"and switch docstrings for str(), range(), and slice() to use multi-line " +"signatures." +msgstr "" + +#: ../../../Misc/NEWS:8888 +msgid "" +"`Issue #16160 `__: Subclass support now works " +"for types.SimpleNamespace." +msgstr "" + +#: ../../../Misc/NEWS:8890 +msgid "" +"`Issue #16148 `__: Implement PEP 424, adding " +"operator.length_hint and PyObject_LengthHint." +msgstr "" + +#: ../../../Misc/NEWS:8893 +msgid "Upgrade Unicode data (UCD) to version 6.2." +msgstr "" + +#: ../../../Misc/NEWS:8895 +msgid "" +"`Issue #15379 `__: Fix passing of non-BMP " +"characters as integers for the charmap decoder (already working as unicode " +"strings). Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8898 +msgid "" +"`Issue #15144 `__: Fix possible integer " +"overflow when handling pointers as integer values, by using `Py_uintptr_t` " +"instead of `size_t`. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:8902 +msgid "" +"`Issue #15965 `__: Explicitly cast `AT_FDCWD` " +"as (int). Required on Solaris 10 (which defines `AT_FDCWD` as " +"``0xffd19553``), harmless on other platforms." +msgstr "" + +#: ../../../Misc/NEWS:8905 +msgid "" +"`Issue #15839 `__: Convert SystemErrors in " +"`super()` to RuntimeErrors." +msgstr "" + +#: ../../../Misc/NEWS:8907 +msgid "" +"`Issue #15448 `__: Buffered IO now frees the " +"buffer when closed, instead of when deallocating." +msgstr "" + +#: ../../../Misc/NEWS:8910 +msgid "" +"`Issue #15846 `__: Fix SystemError which " +"happened when using `ast.parse()` in an exception handler on code with " +"syntax errors." +msgstr "" + +#: ../../../Misc/NEWS:8913 +msgid "" +"`Issue #15897 `__: zipimport.c doesn't check " +"return value of fseek(). Patch by Felipe Cruz." +msgstr "" + +#: ../../../Misc/NEWS:8916 +msgid "" +"`Issue #15801 `__: Make sure mappings passed " +"to '%' formatting are actually subscriptable." +msgstr "" + +#: ../../../Misc/NEWS:8919 +msgid "" +"`Issue #15111 `__: __import__ should " +"propagate ImportError when raised as a side-effect of a module triggered " +"from using fromlist." +msgstr "" + +#: ../../../Misc/NEWS:8922 +msgid "" +"`Issue #15022 `__: Add pickle and comparison " +"support to types.SimpleNamespace." +msgstr "" + +#: ../../../Misc/NEWS:8927 +msgid "" +"`Issue #4331 `__: Added functools." +"partialmethod (Initial patch by Alon Horev)" +msgstr "" + +#: ../../../Misc/NEWS:8929 +msgid "" +"`Issue #13461 `__: Fix a crash in the " +"TextIOWrapper.tell method on 64-bit platforms. Patch by Yogesh Chaudhari." +msgstr "" + +#: ../../../Misc/NEWS:8932 +msgid "" +"`Issue #18681 `__: Fix a NameError in " +"importlib.reload() (noticed by Weizhao Li)." +msgstr "" + +#: ../../../Misc/NEWS:8934 +msgid "" +"`Issue #14323 `__: Expanded the number of " +"digits in the coefficients for the RGB -- YIQ conversions so that they match " +"the FCC NTSC versions." +msgstr "" + +#: ../../../Misc/NEWS:8937 +msgid "" +"`Issue #17998 `__: Fix an internal error in " +"regular expression engine." +msgstr "" + +#: ../../../Misc/NEWS:8939 +msgid "" +"`Issue #17557 `__: Fix os.getgroups() to work " +"with the modified behavior of getgroups(2) on OS X 10.8. Original patch by " +"Mateusz Lenik." +msgstr "" + +#: ../../../Misc/NEWS:8942 +msgid "" +"`Issue #18608 `__: Avoid keeping a strong " +"reference to the locale module inside the _io module." +msgstr "" + +#: ../../../Misc/NEWS:8945 +msgid "" +"`Issue #18619 `__: Fix atexit leaking " +"callbacks registered from sub-interpreters, and make it GC-aware." +msgstr "" + +#: ../../../Misc/NEWS:8948 +msgid "" +"`Issue #15699 `__: The readline module now " +"uses PEP 3121-style module initialization, so as to reclaim allocated " +"resources (Python callbacks) at shutdown. Original patch by Robin Schreiber." +msgstr "" + +#: ../../../Misc/NEWS:8952 +msgid "" +"`Issue #17616 `__: wave.open now supports the " +"context management protocol." +msgstr "" + +#: ../../../Misc/NEWS:8954 +msgid "" +"`Issue #18599 `__: Fix name attribute of " +"_sha1.sha1() object. It now returns 'SHA1' instead of 'SHA'." +msgstr "" + +#: ../../../Misc/NEWS:8957 +msgid "" +"`Issue #13266 `__: Added inspect.unwrap to " +"easily unravel __wrapped__ chains (initial patch by Daniel Urban and Aaron " +"Iles)" +msgstr "" + +#: ../../../Misc/NEWS:8960 +msgid "" +"`Issue #18561 `__: Skip name in ctypes' " +"_build_callargs() if name is NULL." +msgstr "" + +#: ../../../Misc/NEWS:8962 +msgid "" +"`Issue #18559 `__: Fix NULL pointer " +"dereference error in _pickle module" +msgstr "" + +#: ../../../Misc/NEWS:8964 +msgid "" +"`Issue #18556 `__: Check the return type of " +"PyUnicode_AsWideChar() in ctype's U_set()." +msgstr "" + +#: ../../../Misc/NEWS:8967 +msgid "" +"`Issue #17818 `__: aifc.getparams now returns " +"a namedtuple." +msgstr "" + +#: ../../../Misc/NEWS:8969 +msgid "" +"`Issue #18549 `__: Eliminate dead code in " +"socket_ntohl()" +msgstr "" + +#: ../../../Misc/NEWS:8971 +msgid "" +"`Issue #18530 `__: Remove additional stat " +"call from posixpath.ismount. Patch by Alex Gaynor." +msgstr "" + +#: ../../../Misc/NEWS:8974 +msgid "" +"`Issue #18514 `__: Fix unreachable " +"Py_DECREF() call in PyCData_FromBaseObj()" +msgstr "" + +#: ../../../Misc/NEWS:8976 +msgid "" +"`Issue #9177 `__: Calling read() or write() " +"now raises ValueError, not AttributeError, on a closed SSL socket. Patch by " +"Senko Rasic." +msgstr "" + +#: ../../../Misc/NEWS:8979 +msgid "" +"`Issue #18513 `__: Fix behaviour of cmath." +"rect w.r.t. signed zeros on OS X 10.8 + gcc." +msgstr "" + +#: ../../../Misc/NEWS:8982 +msgid "" +"`Issue #18479 `__: Changed venv Activate.ps1 " +"to make deactivate a function, and removed Deactivate.ps1." +msgstr "" + +#: ../../../Misc/NEWS:8985 +msgid "" +"`Issue #18480 `__: Add missing call to " +"PyType_Ready to the _elementtree extension." +msgstr "" + +#: ../../../Misc/NEWS:8987 +msgid "" +"`Issue #17778 `__: Fix test discovery for " +"test_multiprocessing. (Patch by Zachary Ware.)" +msgstr "" + +#: ../../../Misc/NEWS:8990 +msgid "" +"`Issue #18393 `__: The private module " +"_gestalt and private functions platform._mac_ver_gestalt, platform." +"_mac_ver_lookup and platform._bcd2str have been removed. This does not " +"affect the public interface of the platform module." +msgstr "" + +#: ../../../Misc/NEWS:8995 +msgid "" +"`Issue #17482 `__: functools.update_wrapper " +"(and functools.wraps) now set the __wrapped__ attribute correctly even if " +"the underlying function has a __wrapped__ attribute set." +msgstr "" + +#: ../../../Misc/NEWS:8999 +msgid "" +"`Issue #18431 `__: The new email header " +"parser now decodes RFC2047 encoded words in structured headers." +msgstr "" + +#: ../../../Misc/NEWS:9002 +msgid "" +"`Issue #18432 `__: The sched module's queue " +"method was incorrectly returning an iterator instead of a list." +msgstr "" + +#: ../../../Misc/NEWS:9005 +msgid "" +"`Issue #18044 `__: The new email header " +"parser was mis-parsing encoded words where an encoded character immediately " +"followed the '?' that follows the CTE character, resulting in a decoding " +"failure. They are now decoded correctly." +msgstr "" + +#: ../../../Misc/NEWS:9009 +msgid "" +"`Issue #18101 `__: Tcl.split() now process " +"strings nested in a tuple as it do with byte strings." +msgstr "" + +#: ../../../Misc/NEWS:9012 +msgid "" +"`Issue #18116 `__: getpass was always getting " +"an error when testing /dev/tty, and thus was always falling back to stdin, " +"and would then raise an exception if stdin could not be used (such as /dev/" +"null). It also leaked an open file. All of these issues are now fixed." +msgstr "" + +#: ../../../Misc/NEWS:9017 +msgid "" +"`Issue #17198 `__: Fix a NameError in the dbm " +"module. Patch by Valentina Mukhamedzhanova." +msgstr "" + +#: ../../../Misc/NEWS:9020 +msgid "" +"`Issue #18013 `__: Fix cgi.FieldStorage to " +"parse the W3C sample form." +msgstr "" + +#: ../../../Misc/NEWS:9022 +msgid "" +"`Issue #18020 `__: improve html.escape speed " +"by an order of magnitude. Patch by Matt Bryant." +msgstr "" + +#: ../../../Misc/NEWS:9025 +msgid "" +"`Issue #18347 `__: ElementTree's html " +"serializer now preserves the case of closing tags." +msgstr "" + +#: ../../../Misc/NEWS:9028 +msgid "" +"`Issue #17261 `__: Ensure multiprocessing's " +"proxies use proper address." +msgstr "" + +#: ../../../Misc/NEWS:9030 +msgid "" +"`Issue #18343 `__: faulthandler.register() " +"now keeps the previous signal handler when the function is called twice, so " +"faulthandler.unregister() restores correctly the original signal handler." +msgstr "" + +#: ../../../Misc/NEWS:9034 +msgid "" +"`Issue #17097 `__: Make multiprocessing " +"ignore EINTR." +msgstr "" + +#: ../../../Misc/NEWS:9036 +msgid "" +"`Issue #18339 `__: Negative ints keys in " +"unpickler.memo dict no longer cause a segfault inside the _pickle C " +"extension." +msgstr "" + +#: ../../../Misc/NEWS:9039 +msgid "" +"`Issue #18240 `__: The HMAC module is no " +"longer restricted to bytes and accepts any bytes-like object, e.g. " +"memoryview. Original patch by Jonas Borgström." +msgstr "" + +#: ../../../Misc/NEWS:9042 +msgid "" +"`Issue #18224 `__: Removed pydoc script from " +"created venv, as it causes problems on Windows and adds no value over and " +"above python -m pydoc ..." +msgstr "" + +#: ../../../Misc/NEWS:9045 +msgid "" +"`Issue #18155 `__: The csv module now " +"correctly handles csv files that use a delimiter character that has a " +"special meaning in regexes, instead of throwing an exception." +msgstr "" + +#: ../../../Misc/NEWS:9049 +msgid "" +"`Issue #14360 `__: encode_quopri can now be " +"successfully used as an encoder when constructing a MIMEApplication object." +msgstr "" + +#: ../../../Misc/NEWS:9052 +msgid "" +"`Issue #11390 `__: Add -o and -f command line " +"options to the doctest CLI to specify doctest options (and convert it to " +"using argparse)." +msgstr "" + +#: ../../../Misc/NEWS:9055 +msgid "" +"`Issue #18135 `__: ssl.SSLSocket.write() now " +"raises an OverflowError if the input string in longer than 2 gigabytes, and " +"ssl.SSLContext.load_cert_chain() raises a ValueError if the password is " +"longer than 2 gigabytes. The ssl module does not support partial write." +msgstr "" + +#: ../../../Misc/NEWS:9060 +msgid "" +"`Issue #11016 `__: Add C implementation of " +"the stat module as _stat." +msgstr "" + +#: ../../../Misc/NEWS:9062 +msgid "" +"`Issue #18248 `__: Fix libffi build on AIX." +msgstr "" + +#: ../../../Misc/NEWS:9064 +msgid "" +"`Issue #18259 `__: Declare sethostname in " +"socketmodule.c for AIX" +msgstr "" + +#: ../../../Misc/NEWS:9066 +msgid "" +"`Issue #18147 `__: Add diagnostic functions " +"to ssl.SSLContext(). get_ca_list() lists all loaded CA certificates and " +"cert_store_stats() returns amount of loaded X.509 certs, X.509 CA certs and " +"CRLs." +msgstr "" + +#: ../../../Misc/NEWS:9070 +msgid "" +"`Issue #18167 `__: cgi.FieldStorage no longer " +"fails to handle multipart/form-data when ``\\r\\n`` appears at end of 65535 " +"bytes without other newlines." +msgstr "" + +#: ../../../Misc/NEWS:9073 +msgid "" +"`Issue #18076 `__: Introduce importlib.util." +"decode_source()." +msgstr "" + +#: ../../../Misc/NEWS:9075 +msgid "" +"`Issue #18357 `__: add tests for dictview set " +"difference. Patch by Fraser Tweedale." +msgstr "" + +#: ../../../Misc/NEWS:9078 +msgid "" +"importlib.abc.SourceLoader.get_source() no longer changes SyntaxError or " +"UnicodeDecodeError into ImportError." +msgstr "" + +#: ../../../Misc/NEWS:9081 +msgid "" +"`Issue #18058 `__, 18057: Make the namespace " +"package loader meet the importlib.abc.InspectLoader ABC, allowing for " +"namespace packages to work with runpy." +msgstr "" + +#: ../../../Misc/NEWS:9085 +msgid "" +"`Issue #17177 `__: The imp module is pending " +"deprecation." +msgstr "" + +#: ../../../Misc/NEWS:9087 +msgid "" +"subprocess: Prevent a possible double close of parent pipe fds when the " +"subprocess exec runs into an error. Prevent a regular multi-close of the /" +"dev/null fd when any of stdin, stdout and stderr was set to DEVNULL." +msgstr "" + +#: ../../../Misc/NEWS:9091 +msgid "" +"`Issue #18194 `__: Introduce importlib.util." +"cache_from_source() and source_from_cache() while documenting the equivalent " +"functions in imp as deprecated." +msgstr "" + +#: ../../../Misc/NEWS:9095 +msgid "" +"`Issue #17907 `__: Document imp.new_module() " +"as deprecated in favour of types.ModuleType." +msgstr "" + +#: ../../../Misc/NEWS:9098 +msgid "" +"`Issue #18192 `__: Introduce importlib.util." +"MAGIC_NUMBER and document as deprecated imp.get_magic()." +msgstr "" + +#: ../../../Misc/NEWS:9101 +msgid "" +"`Issue #18149 `__: Add filecmp.clear_cache() " +"to manually clear the filecmp cache. Patch by Mark Levitt" +msgstr "" + +#: ../../../Misc/NEWS:9104 +msgid "" +"`Issue #18193 `__: Add importlib.reload()." +msgstr "" + +#: ../../../Misc/NEWS:9106 +msgid "" +"`Issue #18157 `__: Stop using imp." +"load_module() in pydoc." +msgstr "" + +#: ../../../Misc/NEWS:9108 +msgid "" +"`Issue #16102 `__: Make uuid." +"_netbios_getnode() work again on Python 3." +msgstr "" + +#: ../../../Misc/NEWS:9110 +msgid "" +"`Issue #17134 `__: Add ssl.enum_cert_store() " +"as interface to Windows' cert store." +msgstr "" + +#: ../../../Misc/NEWS:9112 +msgid "" +"`Issue #18143 `__: Implement ssl." +"get_default_verify_paths() in order to debug the default locations for " +"cafile and capath." +msgstr "" + +#: ../../../Misc/NEWS:9115 +msgid "" +"`Issue #17314 `__: Move multiprocessing." +"forking over to importlib." +msgstr "" + +#: ../../../Misc/NEWS:9117 +msgid "" +"`Issue #11959 `__: SMTPServer and SMTPChannel " +"now take an optional map, use of which avoids affecting global state." +msgstr "" + +#: ../../../Misc/NEWS:9120 +msgid "" +"`Issue #18109 `__: os.uname() now decodes " +"fields from the locale encoding, and socket.gethostname() now decodes the " +"hostname from the locale encoding, instead of using the UTF-8 encoding in " +"strict mode." +msgstr "" + +#: ../../../Misc/NEWS:9124 +msgid "" +"`Issue #18089 `__: Implement importlib.abc." +"InspectLoader.load_module." +msgstr "" + +#: ../../../Misc/NEWS:9126 +msgid "" +"`Issue #18088 `__: Introduce importlib.abc." +"Loader.init_module_attrs for setting module attributes. Leads to the pending " +"deprecation of importlib.util.module_for_loader." +msgstr "" + +#: ../../../Misc/NEWS:9130 +msgid "" +"`Issue #17403 `__: urllib.parse.robotparser " +"normalizes the urls before adding to ruleline. This helps in handling " +"certain types invalid urls in a conservative manner. Patch contributed by " +"Mher Movsisyan." +msgstr "" + +#: ../../../Misc/NEWS:9134 +msgid "" +"`Issue #18070 `__: Have importlib.util." +"module_for_loader() set attributes unconditionally in order to properly " +"support reloading." +msgstr "" + +#: ../../../Misc/NEWS:9137 +msgid "" +"Added importlib.util.module_to_load to return a context manager to provide " +"the proper module object to load." +msgstr "" + +#: ../../../Misc/NEWS:9140 +msgid "" +"`Issue #18025 `__: Fixed a segfault in io." +"BufferedIOBase.readinto() when raw stream's read() returns more bytes than " +"requested." +msgstr "" + +#: ../../../Misc/NEWS:9143 +msgid "" +"`Issue #18011 `__: As was originally " +"intended, base64.b32decode() now raises a binascii.Error if there are non-" +"b32-alphabet characters present in the input string, instead of a TypeError." +msgstr "" + +#: ../../../Misc/NEWS:9147 +msgid "" +"`Issue #18072 `__: Implement importlib.abc." +"InspectLoader.get_code() and importlib.abc.ExecutionLoader.get_code()." +msgstr "" + +#: ../../../Misc/NEWS:9150 +msgid "" +"`Issue #8240 `__: Set the " +"SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER flag on SSL sockets." +msgstr "" + +#: ../../../Misc/NEWS:9153 +msgid "" +"`Issue #17269 `__: Workaround for socket." +"getaddrinfo crash on MacOS X with port None or \"0\" and flags " +"AI_NUMERICSERV." +msgstr "" + +#: ../../../Misc/NEWS:9156 +msgid "" +"`Issue #16986 `__: ElementTree now correctly " +"works with string input when the internal XML encoding is not UTF-8 or US-" +"ASCII." +msgstr "" + +#: ../../../Misc/NEWS:9159 +msgid "" +"`Issue #17996 `__: socket module now exposes " +"AF_LINK constant on BSD and OSX." +msgstr "" + +#: ../../../Misc/NEWS:9161 +msgid "" +"`Issue #17900 `__: Allowed pickling of " +"recursive OrderedDicts. Decreased pickled size and pickling time." +msgstr "" + +#: ../../../Misc/NEWS:9164 +msgid "" +"`Issue #17914 `__: Add os.cpu_count(). Patch " +"by Yogesh Chaudhari, based on an initial patch by Trent Nelson." +msgstr "" + +#: ../../../Misc/NEWS:9167 +msgid "" +"`Issue #17812 `__: Fixed quadratic complexity " +"of base64.b32encode(). Optimize base64.b32encode() and base64.b32decode() " +"(speed up to 3x)." +msgstr "" + +#: ../../../Misc/NEWS:9170 +msgid "" +"`Issue #17980 `__: Fix possible abuse of ssl." +"match_hostname() for denial of service using certificates with many " +"wildcards (CVE-2013-2099)." +msgstr "" + +#: ../../../Misc/NEWS:9173 +msgid "" +"`Issue #15758 `__: Fix FileIO.readall() so it " +"no longer has O(n**2) complexity." +msgstr "" + +#: ../../../Misc/NEWS:9175 +msgid "" +"`Issue #14596 `__: The struct.Struct() " +"objects now use a more compact implementation." +msgstr "" + +#: ../../../Misc/NEWS:9178 +msgid "" +"`Issue #17981 `__: logging's SysLogHandler " +"now closes the socket when it catches socket OSErrors." +msgstr "" + +#: ../../../Misc/NEWS:9181 +msgid "" +"`Issue #17964 `__: Fix os.sysconf(): the " +"return type of the C sysconf() function is long, not int." +msgstr "" + +#: ../../../Misc/NEWS:9184 +msgid "Fix typos in the multiprocessing module." +msgstr "" + +#: ../../../Misc/NEWS:9186 +msgid "" +"`Issue #17754 `__: Make ctypes.util." +"find_library() independent of the locale." +msgstr "" + +#: ../../../Misc/NEWS:9188 +msgid "" +"`Issue #17968 `__: Fix memory leak in os." +"listxattr()." +msgstr "" + +#: ../../../Misc/NEWS:9190 +msgid "" +"`Issue #17606 `__: Fixed support of encoded " +"byte strings in the XMLGenerator characters() and ignorableWhitespace() " +"methods. Original patch by Sebastian Ortiz Vasquez." +msgstr "" + +#: ../../../Misc/NEWS:9194 +msgid "" +"`Issue #17732 `__: Ignore distutils.cfg " +"options pertaining to install paths if a virtual environment is active." +msgstr "" + +#: ../../../Misc/NEWS:9197 +msgid "" +"`Issue #17915 `__: Fix interoperability of " +"xml.sax with file objects returned by codecs.open()." +msgstr "" + +#: ../../../Misc/NEWS:9200 +msgid "" +"`Issue #16601 `__: Restarting iteration over " +"tarfile really restarts rather than continuing from where it left off. " +"Patch by Michael Birtwell." +msgstr "" + +#: ../../../Misc/NEWS:9203 +msgid "" +"`Issue #17289 `__: The readline module now " +"plays nicer with external modules or applications changing the " +"rl_completer_word_break_characters global variable. Initial patch by " +"Bradley Froehle." +msgstr "" + +#: ../../../Misc/NEWS:9207 +msgid "" +"`Issue #12181 `__: select module: Fix struct " +"kevent definition on OpenBSD 64-bit platforms. Patch by Federico Schwindt." +msgstr "" + +#: ../../../Misc/NEWS:9210 +msgid "" +"`Issue #11816 `__: multiple improvements to " +"the dis module: get_instructions generator, ability to redirect output to a " +"file, Bytecode and Instruction abstractions. Patch by Nick Coghlan, Ryan " +"Kelly and Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:9214 +msgid "" +"`Issue #13831 `__: Embed stringification of " +"remote traceback in local traceback raised when pool task raises an " +"exception." +msgstr "" + +#: ../../../Misc/NEWS:9217 +msgid "" +"`Issue #15528 `__: Add weakref.finalize to " +"support finalization using weakref callbacks." +msgstr "" + +#: ../../../Misc/NEWS:9220 +msgid "" +"`Issue #14173 `__: Avoid crashing when " +"reading a signal handler during interpreter shutdown." +msgstr "" + +#: ../../../Misc/NEWS:9223 +msgid "" +"`Issue #15902 `__: Fix imp.load_module() " +"accepting None as a file when loading an extension module." +msgstr "" + +#: ../../../Misc/NEWS:9226 +msgid "" +"`Issue #13721 `__: SSLSocket.getpeercert() " +"and SSLSocket.do_handshake() now raise an OSError with ENOTCONN, instead of " +"an AttributeError, when the SSLSocket is not connected." +msgstr "" + +#: ../../../Misc/NEWS:9230 +msgid "" +"`Issue #14679 `__: add an __all__ (that " +"contains only HTMLParser) to html.parser." +msgstr "" + +#: ../../../Misc/NEWS:9232 +msgid "" +"`Issue #17802 `__: Fix an UnboundLocalError " +"in html.parser. Initial tests by Thomas Barlow." +msgstr "" + +#: ../../../Misc/NEWS:9235 +msgid "" +"`Issue #17358 `__: Modules loaded by imp." +"load_source() and load_compiled() (and by extension load_module()) now have " +"a better chance of working when reloaded." +msgstr "" + +#: ../../../Misc/NEWS:9238 +msgid "" +"`Issue #17804 `__: New function ``struct." +"iter_unpack`` allows for streaming struct unpacking." +msgstr "" + +#: ../../../Misc/NEWS:9241 +msgid "" +"`Issue #17830 `__: When keyword.py is used to " +"update a keyword file, it now preserves the line endings of the original " +"file." +msgstr "" + +#: ../../../Misc/NEWS:9244 +msgid "" +"`Issue #17272 `__: Making the urllib." +"request's Request.full_url a descriptor. Fixes bugs with assignment to " +"full_url. Patch by Demian Brecht." +msgstr "" + +#: ../../../Misc/NEWS:9247 +msgid "" +"`Issue #17353 `__: Plistlib emitted empty " +"data tags with deeply nested datastructures" +msgstr "" + +#: ../../../Misc/NEWS:9249 +msgid "" +"`Issue #11714 `__: Use 'with' statements to " +"assure a Semaphore releases a condition variable. Original patch by Thomas " +"Rachel." +msgstr "" + +#: ../../../Misc/NEWS:9252 +msgid "" +"`Issue #16624 `__: `subprocess.check_output` " +"now accepts an `input` argument, allowing the subprocess's stdin to be " +"provided as a (byte) string. Patch by Zack Weinberg." +msgstr "" + +#: ../../../Misc/NEWS:9256 +msgid "" +"`Issue #17795 `__: Reverted backwards-" +"incompatible change in SysLogHandler with Unix domain sockets." +msgstr "" + +#: ../../../Misc/NEWS:9259 +msgid "" +"`Issue #16694 `__: Add a pure Python " +"implementation of the operator module. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:9262 +msgid "" +"`Issue #11182 `__: remove the unused and " +"undocumented pydoc.Scanner class. Patch by Martin Morrison." +msgstr "" + +#: ../../../Misc/NEWS:9265 +msgid "" +"`Issue #17741 `__: Add ElementTree." +"XMLPullParser, an event-driven parser for non-blocking applications." +msgstr "" + +#: ../../../Misc/NEWS:9268 +msgid "" +"`Issue #17555 `__: Fix ForkAwareThreadLock so " +"that size of after fork registry does not grow exponentially with generation " +"of process." +msgstr "" + +#: ../../../Misc/NEWS:9271 +msgid "" +"`Issue #17707 `__: fix regression in " +"multiprocessing.Queue's get() method where it did not block for short " +"timeouts." +msgstr "" + +#: ../../../Misc/NEWS:9274 +msgid "" +"`Issue #17720 `__: Fix the Python " +"implementation of pickle.Unpickler to correctly process the APPENDS opcode " +"when it is used on non-list objects." +msgstr "" + +#: ../../../Misc/NEWS:9277 +msgid "" +"`Issue #17012 `__: shutil.which() no longer " +"falls back to the PATH environment variable if an empty path argument is " +"specified. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9280 +msgid "" +"`Issue #17710 `__: Fix pickle raising a " +"SystemError on bogus input." +msgstr "" + +#: ../../../Misc/NEWS:9282 +msgid "" +"`Issue #17341 `__: Include the invalid name " +"in the error messages from re about invalid group names." +msgstr "" + +#: ../../../Misc/NEWS:9285 +msgid "" +"`Issue #17702 `__: os.environ now raises " +"KeyError with the original environment variable name (str on UNIX), instead " +"of using the encoded name (bytes on UNIX)." +msgstr "" + +#: ../../../Misc/NEWS:9289 +msgid "" +"`Issue #16163 `__: Make the importlib based " +"version of pkgutil.iter_importers work for submodules. Initial patch by " +"Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:9292 +msgid "" +"`Issue #16804 `__: Fix a bug in the 'site' " +"module that caused running 'python -S -m site' to incorrectly throw an " +"exception." +msgstr "" + +#: ../../../Misc/NEWS:9295 +msgid "" +"`Issue #15480 `__: Remove the deprecated and " +"unused TYPE_INT64 code from marshal. Initial patch by Daniel Riti." +msgstr "" + +#: ../../../Misc/NEWS:9298 +msgid "" +"`Issue #2118 `__: SMTPException is now a " +"subclass of OSError." +msgstr "" + +#: ../../../Misc/NEWS:9300 +msgid "" +"`Issue #17016 `__: Get rid of possible " +"pointer wraparounds and integer overflows in the re module. Patch by " +"Nickolai Zeldovich." +msgstr "" + +#: ../../../Misc/NEWS:9303 +msgid "" +"`Issue #16658 `__: add missing return to " +"HTTPConnection.send(). Patch by Jeff Knupp." +msgstr "" + +#: ../../../Misc/NEWS:9306 +msgid "" +"`Issue #9556 `__: the logging package now " +"allows specifying a time-of-day for a TimedRotatingFileHandler to rotate." +msgstr "" + +#: ../../../Misc/NEWS:9309 +msgid "" +"`Issue #14971 `__: unittest test discovery no " +"longer gets confused when a function has a different __name__ than its name " +"in the TestCase class dictionary." +msgstr "" + +#: ../../../Misc/NEWS:9312 +msgid "" +"`Issue #17487 `__: The wave getparams method " +"now returns a namedtuple rather than a plain tuple." +msgstr "" + +#: ../../../Misc/NEWS:9315 +msgid "" +"`Issue #17675 `__: socket repr() provides " +"local and remote addresses (if any). Patch by Giampaolo Rodola'" +msgstr "" + +#: ../../../Misc/NEWS:9318 +msgid "" +"`Issue #17093 `__: Make the ABCs in importlib." +"abc provide default values or raise reasonable exceptions for their methods " +"to make them more amenable to super() calls." +msgstr "" + +#: ../../../Misc/NEWS:9322 +msgid "" +"`Issue #17566 `__: Make importlib.abc.Loader." +"module_repr() optional instead of an abstractmethod; now it raises " +"NotImplementedError so as to be ignored by default." +msgstr "" + +#: ../../../Misc/NEWS:9325 +msgid "" +"`Issue #17678 `__: Remove the use of " +"deprecated method in http/cookiejar.py by changing the call to " +"get_origin_req_host() to origin_req_host." +msgstr "" + +#: ../../../Misc/NEWS:9328 +msgid "" +"`Issue #17666 `__: Fix reading gzip files " +"with an extra field." +msgstr "" + +#: ../../../Misc/NEWS:9330 +msgid "" +"`Issue #16475 `__: Support object instancing, " +"recursion and interned strings in marshal" +msgstr "" + +#: ../../../Misc/NEWS:9333 +msgid "" +"`Issue #17502 `__: Process DEFAULT values in " +"mock side_effect that returns iterator." +msgstr "" + +#: ../../../Misc/NEWS:9335 +msgid "" +"`Issue #16795 `__: On the ast.arguments " +"object, unify vararg with varargannotation and kwarg and kwargannotation. " +"Change the column offset of ast.Attribute to be at the attribute name." +msgstr "" + +#: ../../../Misc/NEWS:9339 +msgid "" +"`Issue #17434 `__: Properly raise a " +"SyntaxError when a string occurs between future imports." +msgstr "" + +#: ../../../Misc/NEWS:9342 +msgid "" +"`Issue #17117 `__: Import and @importlib.util." +"set_loader now set __loader__ when it has a value of None or the attribute " +"doesn't exist." +msgstr "" + +#: ../../../Misc/NEWS:9345 +msgid "" +"`Issue #17032 `__: The \"global\" in the " +"\"NameError: global name 'x' is not defined\" error message has been " +"removed. Patch by Ram Rachum." +msgstr "" + +#: ../../../Misc/NEWS:9348 +msgid "" +"`Issue #18080 `__: When building a C " +"extension module on OS X, if the compiler is overridden with the CC " +"environment variable, use the new compiler as the default for linking if " +"LDSHARED is not also overridden. This restores Distutils behavior " +"introduced in 3.2.3 and inadvertently dropped in 3.3.0." +msgstr "" + +#: ../../../Misc/NEWS:9353 +msgid "" +"`Issue #18113 `__: Fixed a refcount leak in " +"the curses.panel module's set_userptr() method. Reported by Atsuo Ishimoto." +msgstr "" + +#: ../../../Misc/NEWS:9356 +msgid "Implement PEP 443 \"Single-dispatch generic functions\"." +msgstr "" + +#: ../../../Misc/NEWS:9358 +msgid "" +"Implement PEP 435 \"Adding an Enum type to the Python standard library\"." +msgstr "" + +#: ../../../Misc/NEWS:9360 +msgid "" +"`Issue #15596 `__: Faster pickling of unicode " +"strings." +msgstr "" + +#: ../../../Misc/NEWS:9362 +msgid "" +"`Issue #17572 `__: Avoid chained exceptions " +"when passing bad directives to time.strptime(). Initial patch by Claudiu " +"Popa." +msgstr "" + +#: ../../../Misc/NEWS:9365 +msgid "" +"`Issue #17435 `__: threading.Timer's __init__ " +"method no longer uses mutable default values for the args and kwargs " +"parameters." +msgstr "" + +#: ../../../Misc/NEWS:9368 +msgid "" +"`Issue #17526 `__: fix an IndexError raised " +"while passing code without filename to inspect.findsource(). Initial patch " +"by Tyler Doyle." +msgstr "" + +#: ../../../Misc/NEWS:9371 +msgid "" +"`Issue #17540 `__: Added style parameter to " +"logging formatter configuration by dict." +msgstr "" + +#: ../../../Misc/NEWS:9373 +msgid "" +"`Issue #16692 `__: The ssl module now " +"supports TLS 1.1 and TLS 1.2. Initial patch by Michele Orrù." +msgstr "" + +#: ../../../Misc/NEWS:9376 +msgid "" +"`Issue #17025 `__: multiprocessing: Reduce " +"Queue and SimpleQueue contention." +msgstr "" + +#: ../../../Misc/NEWS:9378 +msgid "" +"`Issue #17536 `__: Add to webbrowser's " +"browser list: www-browser, x-www-browser, iceweasel, iceape." +msgstr "" + +#: ../../../Misc/NEWS:9381 +msgid "" +"`Issue #17150 `__: pprint now uses line " +"continuations to wrap long string literals." +msgstr "" + +#: ../../../Misc/NEWS:9384 +msgid "" +"`Issue #17488 `__: Change the subprocess." +"Popen bufsize parameter default value from unbuffered (0) to buffering (-1) " +"to match the behavior existing code expects and match the behavior of the " +"subprocess module in Python 2 to avoid introducing hard to track down bugs." +msgstr "" + +#: ../../../Misc/NEWS:9389 +msgid "" +"`Issue #17521 `__: Corrected non-enabling of " +"logger following two calls to fileConfig()." +msgstr "" + +#: ../../../Misc/NEWS:9392 +msgid "" +"`Issue #17508 `__: Corrected logging " +"MemoryHandler configuration in dictConfig() where the target handler wasn't " +"configured first." +msgstr "" + +#: ../../../Misc/NEWS:9395 +msgid "" +"`Issue #17209 `__: curses.window.get_wch() " +"now correctly handles KeyboardInterrupt (CTRL+c)." +msgstr "" + +#: ../../../Misc/NEWS:9398 +msgid "" +"`Issue #5713 `__: smtplib now handles 421 " +"(closing connection) error codes when sending mail by closing the socket and " +"reporting the 421 error code via the exception appropriate to the command " +"that received the error response." +msgstr "" + +#: ../../../Misc/NEWS:9402 +msgid "" +"`Issue #16997 `__: unittest.TestCase now " +"provides a subTest() context manager to procedurally generate, in an easy " +"way, small test instances." +msgstr "" + +#: ../../../Misc/NEWS:9405 +msgid "" +"`Issue #17485 `__: Also delete the Request " +"Content-Length header if the data attribute is deleted. (Follow on to issue " +"`Issue #16464 `__)." +msgstr "" + +#: ../../../Misc/NEWS:9408 +msgid "" +"`Issue #15927 `__: CVS now correctly parses " +"escaped newlines and carriage when parsing with quoting turned off." +msgstr "" + +#: ../../../Misc/NEWS:9411 +msgid "" +"`Issue #17467 `__: add readline and readlines " +"support to mock_open in unittest.mock." +msgstr "" + +#: ../../../Misc/NEWS:9414 +msgid "" +"`Issue #13248 `__: removed deprecated and " +"undocumented difflib.isbjunk, isbpopular." +msgstr "" + +#: ../../../Misc/NEWS:9417 +msgid "" +"`Issue #17192 `__: Update the ctypes module's " +"libffi to v3.0.13. This specifically addresses a stack misalignment issue " +"on x86 and issues on some more recent platforms." +msgstr "" + +#: ../../../Misc/NEWS:9421 +msgid "" +"`Issue #8862 `__: Fixed curses cleanup when " +"getkey is interrupted by a signal." +msgstr "" + +#: ../../../Misc/NEWS:9423 +msgid "" +"`Issue #17443 `__: imaplib.IMAP4_stream was " +"using the default unbuffered IO in subprocess, but the imap code assumes " +"buffered IO. In Python2 this worked by accident. IMAP4_stream now " +"explicitly uses buffered IO." +msgstr "" + +#: ../../../Misc/NEWS:9427 +msgid "" +"`Issue #17476 `__: Fixed regression relative " +"to Python2 in undocumented pydoc 'allmethods'; it was missing unbound " +"methods on the class." +msgstr "" + +#: ../../../Misc/NEWS:9430 +msgid "" +"`Issue #17474 `__: Remove the deprecated " +"methods of Request class." +msgstr "" + +#: ../../../Misc/NEWS:9432 +msgid "" +"`Issue #16709 `__: unittest discover order is " +"no-longer filesystem specific. Patch by Jeff Ramnani." +msgstr "" + +#: ../../../Misc/NEWS:9435 +msgid "" +"Use the HTTPS PyPI url for upload, overriding any plain HTTP URL in pypirc." +msgstr "" + +#: ../../../Misc/NEWS:9437 +msgid "" +"`Issue #5024 `__: sndhdr.whichhdr now returns " +"the frame count for WAV files rather than -1." +msgstr "" + +#: ../../../Misc/NEWS:9440 +msgid "" +"`Issue #17460 `__: Remove the strict argument " +"of HTTPConnection and removing the DeprecationWarning being issued from 3.2 " +"onwards." +msgstr "" + +#: ../../../Misc/NEWS:9443 +msgid "" +"`Issue #16880 `__: Do not assume _imp." +"load_dynamic() is defined in the imp module." +msgstr "" + +#: ../../../Misc/NEWS:9445 +msgid "" +"`Issue #16389 `__: Fixed a performance " +"regression relative to Python 3.1 in the caching of compiled regular " +"expressions." +msgstr "" + +#: ../../../Misc/NEWS:9448 +msgid "Added missing FeedParser and BytesFeedParser to email.parser.__all__." +msgstr "" + +#: ../../../Misc/NEWS:9450 +msgid "" +"`Issue #17431 `__: Fix missing import of " +"BytesFeedParser in email.parser." +msgstr "" + +#: ../../../Misc/NEWS:9452 +msgid "" +"`Issue #12921 `__: http.server's send_error " +"takes an explain argument to send more information in response. Patch " +"contributed by Karl." +msgstr "" + +#: ../../../Misc/NEWS:9455 +msgid "" +"`Issue #17414 `__: Add timeit, repeat, and " +"default_timer to timeit.__all__." +msgstr "" + +#: ../../../Misc/NEWS:9457 +msgid "" +"`Issue #1285086 `__: Get rid of the " +"refcounting hack and speed up urllib.parse.unquote() and urllib.parse." +"unquote_to_bytes()." +msgstr "" + +#: ../../../Misc/NEWS:9460 +msgid "" +"`Issue #17099 `__: Have importlib." +"find_loader() raise ValueError when __loader__ is not set, harmonizing with " +"what happens when the attribute is set to None." +msgstr "" + +#: ../../../Misc/NEWS:9463 +msgid "Expose the O_PATH constant in the os module if it is available." +msgstr "" + +#: ../../../Misc/NEWS:9465 +msgid "" +"`Issue #17368 `__: Fix an off-by-one error in " +"the Python JSON decoder that caused a failure while decoding empty object " +"literals when object_pairs_hook was specified." +msgstr "" + +#: ../../../Misc/NEWS:9469 +msgid "" +"`Issue #17385 `__: Fix quadratic behavior in " +"threading.Condition. The FIFO queue now uses a deque instead of a list." +msgstr "" + +#: ../../../Misc/NEWS:9472 +msgid "" +"`Issue #15806 `__: Add contextlib.ignore(). " +"This creates a context manager to ignore specified exceptions, replacing the " +"\"except SomeException: pass\" idiom." +msgstr "" + +#: ../../../Misc/NEWS:9475 +msgid "" +"`Issue #14645 `__: The email generator " +"classes now produce output using the specified linesep throughout. " +"Previously if the prolog, epilog, or body were stored with a different " +"linesep, that linesep was used. This fix corrects an RFC non-compliance " +"issue with smtplib.send_message." +msgstr "" + +#: ../../../Misc/NEWS:9480 +msgid "" +"`Issue #17278 `__: Fix a crash in heapq." +"heappush() and heapq.heappop() when the list is being resized concurrently." +msgstr "" + +#: ../../../Misc/NEWS:9483 +msgid "" +"`Issue #16962 `__: Use getdents64 instead of " +"the obsolete getdents syscall in the subprocess module on Linux." +msgstr "" + +#: ../../../Misc/NEWS:9486 +msgid "" +"`Issue #16935 `__: unittest now counts the " +"module as skipped if it raises SkipTest, instead of counting it as an " +"error. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:9489 +msgid "" +"`Issue #17018 `__: Make Process.join() retry " +"if os.waitpid() fails with EINTR." +msgstr "" + +#: ../../../Misc/NEWS:9491 +msgid "" +"`Issue #17223 `__: array module: Fix a " +"crasher when converting an array containing invalid characters (outside " +"range [U+0000; U+10ffff]) to Unicode: repr(array), str(array) and array." +"tounicode(). Patch written by Manuel Jacob." +msgstr "" + +#: ../../../Misc/NEWS:9495 +msgid "" +"`Issue #17197 `__: profile/cProfile modules " +"refactored so that code of run() and runctx() utility functions is not " +"duplicated in both modules." +msgstr "" + +#: ../../../Misc/NEWS:9498 +msgid "" +"`Issue #14720 `__: sqlite3: Convert datetime " +"microseconds correctly. Patch by Lowe Thiderman." +msgstr "" + +#: ../../../Misc/NEWS:9501 +msgid "" +"`Issue #15132 `__: Allow a list for the " +"defaultTest argument of unittest.TestProgram. Patch by Jyrki Pulliainen." +msgstr "" + +#: ../../../Misc/NEWS:9504 +msgid "" +"`Issue #17225 `__: JSON decoder now counts " +"columns in the first line starting with 1, as in other lines." +msgstr "" + +#: ../../../Misc/NEWS:9507 +msgid "" +"`Issue #6623 `__: Added explicit " +"DeprecationWarning for ftplib.netrc, which has been deprecated and " +"undocumented for a long time." +msgstr "" + +#: ../../../Misc/NEWS:9510 +msgid "" +"`Issue #13700 `__: Fix byte/string handling " +"in imaplib authentication when an authobject is specified." +msgstr "" + +#: ../../../Misc/NEWS:9513 +msgid "" +"`Issue #13153 `__: Tkinter functions now " +"raise TclError instead of ValueError when a string argument contains non-BMP " +"character." +msgstr "" + +#: ../../../Misc/NEWS:9516 +msgid "" +"`Issue #9669 `__: Protect re against infinite " +"loops on zero-width matching in non-greedy repeat. Patch by Matthew Barnett." +msgstr "" + +#: ../../../Misc/NEWS:9519 +msgid "" +"`Issue #13169 `__: The maximal repetition " +"number in a regular expression has been increased from 65534 to 2147483647 " +"(on 32-bit platform) or 4294967294 (on 64-bit)." +msgstr "" + +#: ../../../Misc/NEWS:9523 +msgid "" +"`Issue #17143 `__: Fix a missing import in " +"the trace module. Initial patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:9526 +msgid "" +"`Issue #15220 `__: email.feedparser's line " +"splitting algorithm is now simpler and faster." +msgstr "" + +#: ../../../Misc/NEWS:9529 +msgid "" +"`Issue #16743 `__: Fix mmap overflow check on " +"32 bit Windows." +msgstr "" + +#: ../../../Misc/NEWS:9531 +msgid "" +"`Issue #16996 `__: webbrowser module now uses " +"shutil.which() to find a web-browser on the executable search path." +msgstr "" + +#: ../../../Misc/NEWS:9534 +msgid "" +"`Issue #16800 `__: tempfile.gettempdir() no " +"longer left temporary files when the disk is full. Original patch by Amir " +"Szekely." +msgstr "" + +#: ../../../Misc/NEWS:9537 +msgid "`Issue #17192 `__: Import libffi-3.0.12." +msgstr "" + +#: ../../../Misc/NEWS:9539 +msgid "" +"`Issue #16564 `__: Fixed regression relative " +"to Python2 in the operation of email.encoders.encode_7or8bit when used with " +"binary data." +msgstr "" + +#: ../../../Misc/NEWS:9542 +msgid "" +"`Issue #17052 `__: unittest discovery should " +"use self.testLoader." +msgstr "" + +#: ../../../Misc/NEWS:9544 +msgid "" +"`Issue #4591 `__: Uid and gid values larger " +"than 2**31 are supported now." +msgstr "" + +#: ../../../Misc/NEWS:9546 +msgid "" +"`Issue #17141 `__: random.vonmisesvariate() " +"no longer hangs for large kappas." +msgstr "" + +#: ../../../Misc/NEWS:9548 +msgid "" +"`Issue #17149 `__: Fix random.vonmisesvariate " +"to always return results in [0, 2*math.pi]." +msgstr "" + +#: ../../../Misc/NEWS:9551 +msgid "" +"`Issue #1470548 `__: XMLGenerator now works " +"with binary output streams." +msgstr "" + +#: ../../../Misc/NEWS:9553 +msgid "" +"`Issue #6975 `__: os.path.realpath() now " +"correctly resolves multiple nested symlinks on POSIX platforms." +msgstr "" + +#: ../../../Misc/NEWS:9556 +msgid "" +"`Issue #13773 `__: sqlite3.connect() gets a " +"new `uri` parameter to pass the filename as a URI, allowing custom options " +"to be passed." +msgstr "" + +#: ../../../Misc/NEWS:9559 +msgid "" +"`Issue #16564 `__: Fixed regression relative " +"to Python2 in the operation of email.encoders.encode_noop when used with " +"binary data." +msgstr "" + +#: ../../../Misc/NEWS:9562 +msgid "" +"`Issue #10355 `__: The mode, name, encoding " +"and newlines properties now work on SpooledTemporaryFile objects even when " +"they have not yet rolled over. Obsolete method xreadline (which has never " +"worked in Python 3) has been removed." +msgstr "" + +#: ../../../Misc/NEWS:9567 +msgid "" +"`Issue #16686 `__: Fixed a lot of bugs in " +"audioop module. Fixed crashes in avgpp(), maxpp() and ratecv(). Fixed an " +"integer overflow in add(), bias(), and ratecv(). reverse(), lin2lin() and " +"ratecv() no more lose precision for 32-bit samples. max() and rms() no more " +"returns a negative result and various other functions now work correctly " +"with 32-bit sample -0x80000000." +msgstr "" + +#: ../../../Misc/NEWS:9573 +msgid "" +"`Issue #17073 `__: Fix some integer overflows " +"in sqlite3 module." +msgstr "" + +#: ../../../Misc/NEWS:9575 +msgid "" +"`Issue #16723 `__: httplib.HTTPResponse no " +"longer marked closed when the connection is automatically closed." +msgstr "" + +#: ../../../Misc/NEWS:9578 +msgid "" +"`Issue #15359 `__: Add CAN_BCM protocol " +"support to the socket module. Patch by Brian Thorne." +msgstr "" + +#: ../../../Misc/NEWS:9581 +msgid "" +"`Issue #16948 `__: Fix quoted printable body " +"encoding for non-latin1 character sets in the email package." +msgstr "" + +#: ../../../Misc/NEWS:9584 +msgid "" +"`Issue #16811 `__: Fix folding of headers " +"with no value in the provisional email policies." +msgstr "" + +#: ../../../Misc/NEWS:9587 +msgid "" +"`Issue #17132 `__: Update symbol for \"yield " +"from\" grammar changes." +msgstr "" + +#: ../../../Misc/NEWS:9589 +msgid "" +"`Issue #17076 `__: Make copying of xattrs " +"more tolerant of missing FS support. Patch by Thomas Wouters." +msgstr "" + +#: ../../../Misc/NEWS:9592 +msgid "" +"`Issue #17089 `__: Expat parser now correctly " +"works with string input when the internal XML encoding is not UTF-8 or US-" +"ASCII. It also now accepts bytes and strings larger than 2 GiB." +msgstr "" + +#: ../../../Misc/NEWS:9596 +msgid "" +"`Issue #6083 `__: Fix multiple segmentation " +"faults occurred when PyArg_ParseTuple parses nested mutating sequence." +msgstr "" + +#: ../../../Misc/NEWS:9599 +msgid "" +"`Issue #5289 `__: Fix ctypes.util.find_library " +"on Solaris." +msgstr "" + +#: ../../../Misc/NEWS:9601 +msgid "" +"`Issue #17106 `__: Fix a segmentation fault " +"in io.TextIOWrapper when an underlying stream or a decoder produces data of " +"an unexpected type (i.e. when io.TextIOWrapper initialized with text stream " +"or use bytes-to-bytes codec)." +msgstr "" + +#: ../../../Misc/NEWS:9605 +msgid "" +"`Issue #17015 `__: When it has a spec, a Mock " +"object now inspects its signature when matching calls, so that arguments can " +"be matched positionally or by name." +msgstr "" + +#: ../../../Misc/NEWS:9609 +msgid "" +"`Issue #15633 `__: httplib.HTTPResponse is " +"now mark closed when the server sends less than the advertised Content-" +"Length." +msgstr "" + +#: ../../../Misc/NEWS:9612 +msgid "" +"`Issue #12268 `__: The io module file object " +"write methods no longer abort early when one of its write system calls is " +"interrupted (EINTR)." +msgstr "" + +#: ../../../Misc/NEWS:9615 +msgid "" +"`Issue #6972 `__: The zipfile module no longer " +"overwrites files outside of its destination path when extracting malicious " +"zip files." +msgstr "" + +#: ../../../Misc/NEWS:9618 +msgid "" +"`Issue #4844 `__: ZipFile now raises " +"BadZipFile when opens a ZIP file with an incomplete \"End of Central " +"Directory\" record. Original patch by Guilherme Polo and Alan McIntyre." +msgstr "" + +#: ../../../Misc/NEWS:9622 +msgid "" +"`Issue #17071 `__: Signature.bind() now works " +"when one of the keyword arguments is named ``self``." +msgstr "" + +#: ../../../Misc/NEWS:9625 +msgid "" +"`Issue #12004 `__: Fix an internal error in " +"PyZipFile when writing an invalid Python file. Patch by Ben Morgan." +msgstr "" + +#: ../../../Misc/NEWS:9628 +msgid "" +"Have py_compile use importlib as much as possible to avoid code duplication. " +"Code now raises FileExistsError if the file path to be used for the byte-" +"compiled file is a symlink or non-regular file as a warning that import will " +"not keep the file path type if it writes to that path." +msgstr "" + +#: ../../../Misc/NEWS:9633 +msgid "" +"`Issue #16972 `__: Have site.addpackage() " +"consider already known paths even when none are explicitly passed in. Bug " +"report and fix by Kirill." +msgstr "" + +#: ../../../Misc/NEWS:9636 +msgid "" +"`Issue #1602133 `__: on Mac OS X a shared " +"library build (``--enable-shared``) now fills the ``os.environ`` variable " +"correctly." +msgstr "" + +#: ../../../Misc/NEWS:9639 +msgid "" +"`Issue #15505 `__: `unittest.installHandler` " +"no longer assumes SIGINT handler is set to a callable object." +msgstr "" + +#: ../../../Misc/NEWS:9642 +msgid "" +"`Issue #13454 `__: Fix a crash when deleting " +"an iterator created by itertools.tee() if all other iterators were very " +"advanced before." +msgstr "" + +#: ../../../Misc/NEWS:9645 +msgid "" +"`Issue #12411 `__: Fix to cgi.parse_multipart " +"to correctly use bytes boundaries and bytes data. Patch by Jonas Wagner." +msgstr "" + +#: ../../../Misc/NEWS:9648 +msgid "" +"`Issue #16957 `__: shutil.which() no longer " +"searches a bare file name in the current directory on Unix and no longer " +"searches a relative file path with a directory part in PATH directories. " +"Patch by Thomas Kluyver." +msgstr "" + +#: ../../../Misc/NEWS:9652 +msgid "" +"`Issue #1159051 `__: GzipFile now raises " +"EOFError when reading a corrupted file with truncated header or footer." +msgstr "" + +#: ../../../Misc/NEWS:9655 +msgid "" +"`Issue #16993 `__: shutil.which() now " +"preserves the case of the path and extension on Windows." +msgstr "" + +#: ../../../Misc/NEWS:9658 +msgid "" +"`Issue #16992 `__: On Windows in signal." +"set_wakeup_fd, validate the file descriptor argument." +msgstr "" + +#: ../../../Misc/NEWS:9661 +msgid "" +"`Issue #16422 `__: For compatibility with the " +"Python version, the C version of decimal now uses strings instead of " +"integers for rounding mode constants." +msgstr "" + +#: ../../../Misc/NEWS:9664 +msgid "" +"`Issue #15861 `__: tkinter now correctly " +"works with lists and tuples containing strings with whitespaces, backslashes " +"or unbalanced braces." +msgstr "" + +#: ../../../Misc/NEWS:9667 +msgid "" +"`Issue #9720 `__: zipfile now writes correct " +"local headers for files larger than 4 GiB." +msgstr "" + +#: ../../../Misc/NEWS:9670 +msgid "" +"`Issue #16955 `__: Fix the poll() method for " +"multiprocessing's socket connections on Windows." +msgstr "" + +#: ../../../Misc/NEWS:9673 +msgid "SSLContext.load_dh_params() now properly closes the input file." +msgstr "" + +#: ../../../Misc/NEWS:9675 +msgid "" +"`Issue #15031 `__: Refactor some .pyc " +"management code to cut down on code duplication. Thanks to Ronan Lamy for " +"the report and taking an initial stab at the problem." +msgstr "" + +#: ../../../Misc/NEWS:9679 +msgid "" +"`Issue #16398 `__: Optimize deque.rotate() so " +"that it only moves pointers and doesn't touch the underlying data with " +"increfs and decrefs." +msgstr "" + +#: ../../../Misc/NEWS:9682 +msgid "" +"`Issue #16900 `__: Issue a ResourceWarning " +"when an ssl socket is left unclosed." +msgstr "" + +#: ../../../Misc/NEWS:9684 +msgid "" +"`Issue #13899 `__: ``\\A``, ``\\Z``, and ``" +"\\B`` now correctly match the A, Z, and B literals when used inside " +"character classes (e.g. ``'[\\A]'``). Patch by Matthew Barnett." +msgstr "" + +#: ../../../Misc/NEWS:9688 +msgid "" +"`Issue #15545 `__: Fix regression in " +"sqlite3's iterdump method where it was failing if the connection used a row " +"factory (such as sqlite3.Row) that produced unsortable objects. (Regression " +"was introduced by fix for 9750)." +msgstr "" + +#: ../../../Misc/NEWS:9692 +msgid "fcntl: add F_DUPFD_CLOEXEC constant, available on Linux 2.6.24+." +msgstr "" + +#: ../../../Misc/NEWS:9694 +msgid "" +"`Issue #15972 `__: Fix error messages when os " +"functions expecting a file name or file descriptor receive the incorrect " +"type." +msgstr "" + +#: ../../../Misc/NEWS:9697 +msgid "" +"`Issue #8109 `__: The ssl module now has " +"support for server-side SNI, thanks to a :meth:`SSLContext." +"set_servername_callback` method. Patch by Daniel Black." +msgstr "" + +#: ../../../Misc/NEWS:9701 +msgid "" +"`Issue #16860 `__: In tempfile, use O_CLOEXEC " +"when available to set the close-on-exec flag atomically." +msgstr "" + +#: ../../../Misc/NEWS:9704 +msgid "" +"`Issue #16674 `__: random.getrandbits() is " +"now 20-40% faster for small integers." +msgstr "" + +#: ../../../Misc/NEWS:9706 +msgid "" +"`Issue #16009 `__: JSON error messages now " +"provide more information." +msgstr "" + +#: ../../../Misc/NEWS:9708 +msgid "" +"`Issue #16828 `__: Fix error incorrectly " +"raised by bz2.compress(b'') and bz2.BZ2Compressor.compress(b''). Initial " +"patch by Martin Packman." +msgstr "" + +#: ../../../Misc/NEWS:9711 +msgid "" +"`Issue #16833 `__: In http.client." +"HTTPConnection, do not concatenate the request headers and body when the " +"payload exceeds 16 KB, since it can consume more memory for no benefit. " +"Patch by Benno Leslie." +msgstr "" + +#: ../../../Misc/NEWS:9715 +msgid "" +"`Issue #16541 `__: tk_setPalette() now works " +"with keyword arguments." +msgstr "" + +#: ../../../Misc/NEWS:9717 +msgid "" +"`Issue #16820 `__: In configparser, `parser." +"popitem()` no longer raises ValueError. This makes `parser.clean()` work " +"correctly." +msgstr "" + +#: ../../../Misc/NEWS:9720 +msgid "" +"`Issue #16820 `__: In configparser, " +"``parser['section'] = {}`` now preserves section order within the parser. " +"This makes `parser.update()` preserve section order as well." +msgstr "" + +#: ../../../Misc/NEWS:9724 +msgid "" +"`Issue #16820 `__: In configparser, " +"``parser['DEFAULT'] = {}`` now correctly clears previous values stored in " +"the default section. Same goes for ``parser.update({'DEFAULT': {}})``." +msgstr "" + +#: ../../../Misc/NEWS:9728 +msgid "" +"`Issue #9586 `__: Redefine SEM_FAILED on " +"MacOSX to keep compiler happy." +msgstr "" + +#: ../../../Misc/NEWS:9730 +msgid "" +"`Issue #16787 `__: Increase asyncore and " +"asynchat default output buffers size, to decrease CPU usage and increase " +"throughput." +msgstr "" + +#: ../../../Misc/NEWS:9733 +msgid "" +"`Issue #10527 `__: make multiprocessing use " +"poll() instead of select() if available." +msgstr "" + +#: ../../../Misc/NEWS:9735 +msgid "" +"`Issue #16688 `__: Now regexes contained " +"backreferences correctly work with non-ASCII strings. Patch by Matthew " +"Barnett." +msgstr "" + +#: ../../../Misc/NEWS:9738 +msgid "" +"`Issue #16486 `__: Make aifc files act as " +"context managers." +msgstr "" + +#: ../../../Misc/NEWS:9740 +msgid "" +"`Issue #16485 `__: Now file descriptors are " +"closed if file header patching failed on closing an aifc file." +msgstr "" + +#: ../../../Misc/NEWS:9743 +msgid "" +"`Issue #16640 `__: Run less code under a lock " +"in sched module." +msgstr "" + +#: ../../../Misc/NEWS:9745 +msgid "" +"`Issue #16165 `__: sched.scheduler.run() no " +"longer blocks a scheduler for other threads." +msgstr "" + +#: ../../../Misc/NEWS:9748 +msgid "" +"`Issue #16641 `__: Default values of sched." +"scheduler.enter() are no longer modifiable." +msgstr "" + +#: ../../../Misc/NEWS:9751 +msgid "" +"`Issue #16618 `__: Make glob.glob match " +"consistently across strings and bytes regarding leading dots. Patch by " +"Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9754 +msgid "" +"`Issue #16788 `__: Add samestat to Lib/ntpath." +"py" +msgstr "" + +#: ../../../Misc/NEWS:9756 +msgid "" +"`Issue #16713 `__: Parsing of 'tel' urls " +"using urlparse separates params from path." +msgstr "" + +#: ../../../Misc/NEWS:9759 +msgid "" +"`Issue #16443 `__: Add docstrings to regular " +"expression match objects. Patch by Anton Kasyanov." +msgstr "" + +#: ../../../Misc/NEWS:9762 +msgid "" +"`Issue #15701 `__: Fix HTTPError info method " +"call to return the headers information." +msgstr "" + +#: ../../../Misc/NEWS:9764 +msgid "" +"`Issue #16752 `__: Add a missing import to " +"modulefinder. Patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:9766 +msgid "" +"`Issue #16646 `__: ftplib.FTP.makeport() " +"might lose socket error details. (patch by Serhiy Storchaka)" +msgstr "" + +#: ../../../Misc/NEWS:9769 +msgid "" +"`Issue #16626 `__: Fix infinite recursion in " +"glob.glob() on Windows when the pattern contains a wildcard in the drive or " +"UNC path. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9773 +msgid "" +"`Issue #15783 `__: Except for the number " +"methods, the C version of decimal now supports all None default values " +"present in decimal.py. These values were largely undocumented." +msgstr "" + +#: ../../../Misc/NEWS:9777 +msgid "" +"`Issue #11175 `__: argparse.FileType now " +"accepts encoding and errors arguments. Patch by Lucas Maystre." +msgstr "" + +#: ../../../Misc/NEWS:9780 +msgid "" +"`Issue #16488 `__: epoll() objects now " +"support the `with` statement. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9783 +msgid "" +"`Issue #16298 `__: In HTTPResponse.read(), " +"close the socket when there is no Content-Length and the incoming stream is " +"finished. Patch by Eran Rundstein." +msgstr "" + +#: ../../../Misc/NEWS:9787 +msgid "" +"`Issue #16049 `__: Add abc.ABC class to " +"enable the use of inheritance to create ABCs, rather than the more " +"cumbersome metaclass=ABCMeta. Patch by Bruno Dupuis." +msgstr "" + +#: ../../../Misc/NEWS:9791 +msgid "" +"Expose the TCP_FASTOPEN and MSG_FASTOPEN flags in socket when they're " +"available." +msgstr "" + +#: ../../../Misc/NEWS:9794 +msgid "" +"`Issue #15701 `__: Add a .headers attribute " +"to urllib.error.HTTPError. Patch contributed by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:9797 +msgid "" +"`Issue #15872 `__: Fix 3.3 regression " +"introduced by the new fd-based shutil.rmtree that caused it to not ignore " +"certain errors when ignore_errors was set. Patch by Alessandro Moura and " +"Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9801 +msgid "" +"`Issue #16248 `__: Disable code execution " +"from the user's home directory by tkinter when the -E flag is passed to " +"Python. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:9804 +msgid "" +"`Issue #13390 `__: New function :func:`sys." +"getallocatedblocks()` returns the number of memory blocks currently " +"allocated." +msgstr "" + +#: ../../../Misc/NEWS:9807 +msgid "" +"`Issue #16628 `__: Fix a memory leak in " +"ctypes.resize()." +msgstr "" + +#: ../../../Misc/NEWS:9809 +msgid "" +"`Issue #13614 `__: Fix setup.py register " +"failure with invalid rst in description. Patch by Julien Courteau and Pierre " +"Paul Lefebvre." +msgstr "" + +#: ../../../Misc/NEWS:9812 +msgid "" +"`Issue #13512 `__: Create ~/.pypirc securely " +"(CVE-2011-4944). Initial patch by Philip Jenvey, tested by Mageia and " +"Debian." +msgstr "" + +#: ../../../Misc/NEWS:9815 +msgid "" +"`Issue #7719 `__: Make distutils ignore ``." +"nfs*`` files instead of choking later on. Initial patch by SilentGhost and " +"Jeff Ramnani." +msgstr "" + +#: ../../../Misc/NEWS:9818 +msgid "" +"`Issue #13120 `__: Allow calling pdb." +"set_trace() from thread. Patch by Ilya Sandler." +msgstr "" + +#: ../../../Misc/NEWS:9821 +msgid "" +"`Issue #16585 `__: Make CJK encoders support " +"error handlers that return bytes per PEP 383." +msgstr "" + +#: ../../../Misc/NEWS:9824 +msgid "" +"`Issue #10182 `__: The re module doesn't " +"truncate indices to 32 bits anymore. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9827 +msgid "" +"`Issue #16333 `__: use (\",\", \": \") as " +"default separator in json when indent is specified, to avoid trailing " +"whitespace. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9830 +msgid "" +"`Issue #16573 `__: In 2to3, treat enumerate() " +"like a consuming call, so superfluous list() calls aren't added to filter(), " +"map(), and zip() which are directly passed enumerate()." +msgstr "" + +#: ../../../Misc/NEWS:9834 +msgid "" +"`Issue #16464 `__: Reset the Content-Length " +"header when a urllib Request is reused with new data." +msgstr "" + +#: ../../../Misc/NEWS:9837 +msgid "" +"`Issue #12848 `__: The pure Python pickle " +"implementation now treats object lengths as unsigned 32-bit integers, like " +"the C implementation does. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9841 +msgid "" +"`Issue #16423 `__: urllib.request now has " +"support for ``data:`` URLs. Patch by Mathias Panzenböck." +msgstr "" + +#: ../../../Misc/NEWS:9844 +msgid "" +"`Issue #4473 `__: Add a POP3.stls() to switch " +"a clear-text POP3 session into an encrypted POP3 session, on supported " +"servers. Patch by Lorenzo Catucci." +msgstr "" + +#: ../../../Misc/NEWS:9847 +msgid "" +"`Issue #4473 `__: Add a POP3.capa() method to " +"query the capabilities advertised by the POP3 server. Patch by Lorenzo " +"Catucci." +msgstr "" + +#: ../../../Misc/NEWS:9850 +msgid "" +"`Issue #4473 `__: Ensure the socket is " +"shutdown cleanly in POP3.close(). Patch by Lorenzo Catucci." +msgstr "" + +#: ../../../Misc/NEWS:9853 +msgid "" +"`Issue #16522 `__: added FAIL_FAST flag to " +"doctest." +msgstr "" + +#: ../../../Misc/NEWS:9855 +msgid "" +"`Issue #15627 `__: Add the importlib.abc." +"InspectLoader.source_to_code() method." +msgstr "" + +#: ../../../Misc/NEWS:9857 +msgid "" +"`Issue #16408 `__: Fix file descriptors not " +"being closed in error conditions in the zipfile module. Patch by Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9860 +msgid "" +"`Issue #14631 `__: Add a new :class:`weakref." +"WeakMethod` to simulate weak references to bound methods." +msgstr "" + +#: ../../../Misc/NEWS:9863 +msgid "" +"`Issue #16469 `__: Fix exceptions from float -" +"> Fraction and Decimal -> Fraction conversions for special values to be " +"consistent with those for float -> int and Decimal -> int. Patch by Alexey " +"Kachayev." +msgstr "" + +#: ../../../Misc/NEWS:9867 +msgid "" +"`Issue #16481 `__: multiprocessing no longer " +"leaks process handles on Windows." +msgstr "" + +#: ../../../Misc/NEWS:9869 +msgid "" +"`Issue #12428 `__: Add a pure Python " +"implementation of functools.partial(). Patch by Brian Thorne." +msgstr "" + +#: ../../../Misc/NEWS:9872 +msgid "" +"`Issue #16140 `__: The subprocess module no " +"longer double closes its child subprocess.PIPE parent file descriptors on " +"child error prior to exec()." +msgstr "" + +#: ../../../Misc/NEWS:9875 +msgid "" +"Remove a bare print to stdout from the subprocess module that could have " +"happened if the child process wrote garbage to its pre-exec error pipe." +msgstr "" + +#: ../../../Misc/NEWS:9878 +msgid "" +"The subprocess module now raises its own SubprocessError instead of a " +"RuntimeError in various error situations which should not normally happen." +msgstr "" + +#: ../../../Misc/NEWS:9881 +msgid "" +"`Issue #16327 `__: The subprocess module no " +"longer leaks file descriptors used for stdin/stdout/stderr pipes to the " +"child when fork() fails." +msgstr "" + +#: ../../../Misc/NEWS:9884 +msgid "" +"`Issue #14396 `__: Handle the odd rare case " +"of waitpid returning 0 when not expected in subprocess.Popen.wait()." +msgstr "" + +#: ../../../Misc/NEWS:9887 +msgid "" +"`Issue #16411 `__: Fix a bug where zlib." +"decompressobj().flush() might try to access previously-freed memory. Patch " +"by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9890 +msgid "" +"`Issue #16357 `__: fix calling accept() on a " +"SSLSocket created through SSLContext.wrap_socket(). Original patch by Jeff " +"McNeil." +msgstr "" + +#: ../../../Misc/NEWS:9893 +msgid "" +"`Issue #16409 `__: The reporthook callback " +"made by the legacy urllib.request.urlretrieve API now properly supplies a " +"constant non-zero block_size as it did in Python 3.2 and 2.7. This matches " +"the behavior of urllib.request.URLopener.retrieve." +msgstr "" + +#: ../../../Misc/NEWS:9898 +msgid "" +"`Issue #16431 `__: Use the type information " +"when constructing a Decimal subtype from a Decimal argument." +msgstr "" + +#: ../../../Misc/NEWS:9901 +msgid "" +"`Issue #15641 `__: Clean up deprecated " +"classes from importlib. Patch by Taras Lyapun." +msgstr "" + +#: ../../../Misc/NEWS:9904 +msgid "" +"`Issue #16350 `__: zlib.decompressobj()." +"decompress() now accumulates data from successive calls after EOF in " +"unused_data, instead of only saving the argument to the last call. " +"decompressobj().flush() now correctly sets unused_data and unconsumed_tail. " +"A bug in the handling of MemoryError when setting the unconsumed_tail " +"attribute has also been fixed. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9910 +msgid "" +"`Issue #12759 `__: sre_parse now raises a " +"proper error when the name of the group is missing. Initial patch by Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9913 +msgid "" +"`Issue #16152 `__: fix tokenize to ignore " +"whitespace at the end of the code when no newline is found. Patch by Ned " +"Batchelder." +msgstr "" + +#: ../../../Misc/NEWS:9916 +msgid "" +"`Issue #16284 `__: Prevent keeping " +"unnecessary references to worker functions in concurrent.futures " +"ThreadPoolExecutor." +msgstr "" + +#: ../../../Misc/NEWS:9919 +msgid "" +"`Issue #16230 `__: Fix a crash in select." +"select() when one of the lists changes size while iterated on. Patch by " +"Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9922 +msgid "" +"`Issue #16228 `__: Fix a crash in the json " +"module where a list changes size while it is being encoded. Patch by Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9925 +msgid "" +"`Issue #16351 `__: New function gc." +"get_stats() returns per-generation collection statistics." +msgstr "" + +#: ../../../Misc/NEWS:9928 +msgid "" +"`Issue #14897 `__: Enhance error messages of " +"struct.pack and struct.pack_into. Patch by Matti Mäki." +msgstr "" + +#: ../../../Misc/NEWS:9931 +msgid "" +"`Issue #16316 `__: mimetypes now recognizes " +"the .xz and .txz (.tar.xz) extensions. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:9934 +msgid "" +"`Issue #12890 `__: cgitb no longer prints " +"spurious

tags in text mode when the logdir option is specified." +msgstr "" + +#: ../../../Misc/NEWS:9937 +msgid "" +"`Issue #16307 `__: Fix multiprocessing.Pool." +"map_async not calling its callbacks. Patch by Janne Karila." +msgstr "" + +#: ../../../Misc/NEWS:9940 +msgid "" +"`Issue #16305 `__: Fix a segmentation fault " +"occurring when interrupting math.factorial." +msgstr "" + +#: ../../../Misc/NEWS:9943 +msgid "" +"`Issue #16116 `__: Fix include and library " +"paths to be correct when building C extensions in venvs." +msgstr "" + +#: ../../../Misc/NEWS:9946 +msgid "" +"`Issue #16245 `__: Fix the value of a few " +"entities in html.entities.html5." +msgstr "" + +#: ../../../Misc/NEWS:9948 +msgid "" +"`Issue #16301 `__: Fix the localhost " +"verification in urllib/request.py for ``file://`` urls." +msgstr "" + +#: ../../../Misc/NEWS:9951 +msgid "" +"`Issue #16250 `__: Fix the invocations of " +"URLError which had misplaced filename attribute for exception." +msgstr "" + +#: ../../../Misc/NEWS:9954 +msgid "" +"`Issue #10836 `__: Fix exception raised when " +"file not found in urlretrieve Initial patch by Ezio Melotti." +msgstr "" + +#: ../../../Misc/NEWS:9957 +msgid "" +"`Issue #14398 `__: Fix size truncation and " +"overflow bugs in the bz2 module." +msgstr "" + +#: ../../../Misc/NEWS:9959 +msgid "" +"`Issue #12692 `__: Fix resource leak in " +"urllib.request when talking to an HTTP server that does not include a " +"``Connection: close`` header in its responses." +msgstr "" + +#: ../../../Misc/NEWS:9962 +msgid "" +"`Issue #12034 `__: Fix bogus caching of " +"result in check_GetFinalPathNameByHandle. Patch by Atsuo Ishimoto." +msgstr "" + +#: ../../../Misc/NEWS:9965 +msgid "" +"Improve performance of `lzma.LZMAFile` (see also `issue #16034 `__)." +msgstr "" + +#: ../../../Misc/NEWS:9967 +msgid "" +"`Issue #16220 `__: wsgiref now always calls " +"close() on an iterable response. Patch by Brent Tubbs." +msgstr "" + +#: ../../../Misc/NEWS:9970 +msgid "" +"`Issue #16270 `__: urllib may hang when used " +"for retrieving files via FTP by using a context manager. Patch by Giampaolo " +"Rodola'." +msgstr "" + +#: ../../../Misc/NEWS:9973 +msgid "" +"`Issue #16461 `__: Wave library should be " +"able to deal with 4GB wav files, and sample rate of 44100 Hz." +msgstr "" + +#: ../../../Misc/NEWS:9976 +msgid "" +"`Issue #16176 `__: Properly identify Windows " +"8 via platform.platform()" +msgstr "" + +#: ../../../Misc/NEWS:9978 +msgid "" +"`Issue #16088 `__: BaseHTTPRequestHandler's " +"send_error method includes a Content-Length header in its response now. " +"Patch by Antoine Pitrou." +msgstr "" + +#: ../../../Misc/NEWS:9981 +msgid "" +"`Issue #16114 `__: The subprocess module no " +"longer provides a misleading error message stating that args[0] did not " +"exist when either the cwd or executable keyword arguments specified a path " +"that did not exist." +msgstr "" + +#: ../../../Misc/NEWS:9985 +msgid "" +"`Issue #16169 `__: Fix ctypes.WinError()'s " +"confusion between errno and winerror." +msgstr "" + +#: ../../../Misc/NEWS:9987 +msgid "" +"`Issue #16110 `__: logging.fileConfig now " +"accepts a pre-initialised ConfigParser instance." +msgstr "" + +#: ../../../Misc/NEWS:9990 +msgid "" +"`Issue #1492704 `__: shutil.copyfile() " +"raises a distinct SameFileError now if source and destination are the same " +"file. Patch by Atsuo Ishimoto." +msgstr "" + +#: ../../../Misc/NEWS:9993 +msgid "" +"`Issue #13896 `__: Make shelf instances work " +"with 'with' as context managers. Original patch by Filip Gruszczyński." +msgstr "" + +#: ../../../Misc/NEWS:9996 +msgid "" +"`Issue #15417 `__: Add support for csh and " +"fish in venv activation scripts." +msgstr "" + +#: ../../../Misc/NEWS:9998 +msgid "" +"`Issue #14377 `__: ElementTree.write and some " +"of the module-level functions have a new parameter - *short_empty_elements*. " +"It controls how elements with no contents are emitted." +msgstr "" + +#: ../../../Misc/NEWS:10002 +msgid "" +"`Issue #16089 `__: Allow ElementTree." +"TreeBuilder to work again with a non-Element element_factory (fixes a " +"regression in SimpleTAL)." +msgstr "" + +#: ../../../Misc/NEWS:10005 +msgid "" +"`Issue #9650 `__: List commonly used format " +"codes in time.strftime and time.strptime docsttings. Original patch by Mike " +"Hoy." +msgstr "" + +#: ../../../Misc/NEWS:10008 +msgid "" +"`Issue #15452 `__: logging configuration " +"socket listener now has a verify option that allows an application to apply " +"a verification function to the received configuration data before it is " +"acted upon." +msgstr "" + +#: ../../../Misc/NEWS:10012 +msgid "" +"`Issue #16034 `__: Fix performance " +"regressions in the new `bz2.BZ2File` implementation. Initial patch by " +"Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10015 +msgid "" +"`pty.spawn()` now returns the child process status returned by `os." +"waitpid()`." +msgstr "" + +#: ../../../Misc/NEWS:10017 +msgid "" +"`Issue #15756 `__: `subprocess.poll()` now " +"properly handles `errno.ECHILD` to return a returncode of 0 when the child " +"has already exited or cannot be waited on." +msgstr "" + +#: ../../../Misc/NEWS:10021 +msgid "" +"`Issue #15323 `__: Improve failure message of " +"`Mock.assert_called_once_with()`." +msgstr "" + +#: ../../../Misc/NEWS:10023 +msgid "" +"`Issue #16064 `__: ``unittest -m`` claims " +"executable is \"python\", not \"python3\"." +msgstr "" + +#: ../../../Misc/NEWS:10025 +msgid "" +"`Issue #12376 `__: Pass on parameters in " +"`TextTestResult.__init__()` super call." +msgstr "" + +#: ../../../Misc/NEWS:10027 +msgid "" +"`Issue #15222 `__: Insert blank line after " +"each message in mbox mailboxes." +msgstr "" + +#: ../../../Misc/NEWS:10029 +msgid "" +"`Issue #16013 `__: Fix `csv.Reader` parsing " +"issue with ending quote characters. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10032 +msgid "" +"`Issue #15421 `__: Fix an OverflowError in " +"`Calendar.itermonthdates()` after `datetime.MAXYEAR`. Patch by Cédric Krier." +msgstr "" + +#: ../../../Misc/NEWS:10035 +msgid "" +"`Issue #16112 `__: platform.architecture does " +"not correctly escape argument to /usr/bin/file. Patch by David Benjamin." +msgstr "" + +#: ../../../Misc/NEWS:10038 +msgid "" +"`Issue #15970 `__: `xml.etree.ElementTree` " +"now serializes correctly the empty HTML elements 'meta' and 'param'." +msgstr "" + +#: ../../../Misc/NEWS:10041 +msgid "" +"`Issue #15842 `__: The `SocketIO.{readable," +"writable,seekable}` methods now raise ValueError when the file-like object " +"is closed. Patch by Alessandro Moura." +msgstr "" + +#: ../../../Misc/NEWS:10044 +msgid "" +"`Issue #15876 `__: Fix a refleak in the " +"`curses` module: window.encoding." +msgstr "" + +#: ../../../Misc/NEWS:10046 +msgid "" +"`Issue #15881 `__: Fix `atexit` hook in " +"`multiprocessing`. Original patch by Chris McDonough." +msgstr "" + +#: ../../../Misc/NEWS:10049 +msgid "" +"`Issue #15841 `__: The readable(), writable() " +"and seekable() methods of `io.BytesIO` and `io.StringIO` objects now raise " +"ValueError when the object has been closed. Patch by Alessandro Moura." +msgstr "" + +#: ../../../Misc/NEWS:10053 +msgid "" +"`Issue #15447 `__: Use `subprocess.DEVNULL` " +"in webbrowser, instead of opening `os.devnull` explicitly and leaving it " +"open." +msgstr "" + +#: ../../../Misc/NEWS:10056 +msgid "" +"`Issue #15509 `__: `webbrowser.UnixBrowser` " +"no longer passes empty arguments to Popen when ``%action`` substitutions " +"produce empty strings." +msgstr "" + +#: ../../../Misc/NEWS:10059 +msgid "" +"`Issue #12776 `__, `issue #11839 `__: Call `argparse` type function (specified by " +"add_argument) only once. Before, the type function was called twice in the " +"case where the default was specified and the argument was given as well. " +"This was especially problematic for the FileType type, as a default file " +"would always be opened, even if a file argument was specified on the command " +"line." +msgstr "" + +#: ../../../Misc/NEWS:10065 +msgid "" +"`Issue #15906 `__: Fix a regression in " +"argparse caused by the preceding change, when ``action='append'``, " +"``type='str'`` and ``default=[]``." +msgstr "" + +#: ../../../Misc/NEWS:10068 +msgid "" +"`Issue #16113 `__: Added sha3 module based on " +"the Keccak reference implementation 3.2. The `hashlib` module has four " +"additional hash algorithms: `sha3_224`, `sha3_256`, `sha3_384` and " +"`sha3_512`. As part of the patch some common code was moved from " +"_hashopenssl.c to hashlib.h." +msgstr "" + +#: ../../../Misc/NEWS:10073 +msgid "" +"ctypes.call_commethod was removed, since its only usage was in the defunct " +"samples directory." +msgstr "" + +#: ../../../Misc/NEWS:10076 +msgid "" +"`Issue #16692 `__: Added TLSv1.1 and TLSv1.2 " +"support for the ssl modules." +msgstr "" + +#: ../../../Misc/NEWS:10078 +msgid "" +"`Issue #16832 `__: add abc.get_cache_token() " +"to expose cache validity checking support in ABCMeta." +msgstr "" + +#: ../../../Misc/NEWS:10084 +msgid "" +"`Issue #18429 `__: Format / Format Paragraph, " +"now works when comment blocks are selected. As with text blocks, this works " +"best when the selection only includes complete lines." +msgstr "" + +#: ../../../Misc/NEWS:10088 +msgid "" +"`Issue #18226 `__: Add docstrings and " +"unittests for FormatParagraph.py. Original patches by Todd Rovito and Phil " +"Webster." +msgstr "" + +#: ../../../Misc/NEWS:10091 +msgid "" +"`Issue #18279 `__: Format - Strip trailing " +"whitespace no longer marks a file as changed when it has not been changed. " +"This fix followed the addition of a test file originally written by Phil " +"Webster (the issue's main goal)." +msgstr "" + +#: ../../../Misc/NEWS:10095 +msgid "" +"`Issue #7136 `__: In the Idle File menu, \"New " +"Window\" is renamed \"New File\". Patch by Tal Einat, Roget Serwy, and Todd " +"Rovito." +msgstr "" + +#: ../../../Misc/NEWS:10098 +msgid "Remove dead imports of imp." +msgstr "" + +#: ../../../Misc/NEWS:10100 +msgid "" +"`Issue #18196 `__: Avoid displaying spurious " +"SystemExit tracebacks." +msgstr "" + +#: ../../../Misc/NEWS:10102 +msgid "" +"`Issue #5492 `__: Avoid traceback when exiting " +"IDLE caused by a race condition." +msgstr "" + +#: ../../../Misc/NEWS:10104 +msgid "" +"`Issue #17511 `__: Keep IDLE find dialog open " +"after clicking \"Find Next\". Original patch by Sarah K." +msgstr "" + +#: ../../../Misc/NEWS:10107 +msgid "" +"`Issue #18055 `__: Move IDLE off of imp and " +"on to importlib." +msgstr "" + +#: ../../../Misc/NEWS:10109 +msgid "" +"`Issue #15392 `__: Create a unittest " +"framework for IDLE. Initial patch by Rajagopalasarma Jayakrishnan. See Lib/" +"idlelib/idle_test/README.txt for how to run Idle tests." +msgstr "" + +#: ../../../Misc/NEWS:10113 +msgid "" +"`Issue #14146 `__: Highlight source line " +"while debugging on Windows." +msgstr "" + +#: ../../../Misc/NEWS:10115 +msgid "" +"`Issue #17838 `__: Allow sys.stdin to be " +"reassigned." +msgstr "" + +#: ../../../Misc/NEWS:10117 +msgid "" +"`Issue #13495 `__: Avoid loading the color " +"delegator twice in IDLE." +msgstr "" + +#: ../../../Misc/NEWS:10119 +msgid "" +"`Issue #17798 `__: Allow IDLE to edit new " +"files when specified on command line." +msgstr "" + +#: ../../../Misc/NEWS:10121 +msgid "" +"`Issue #14735 `__: Update IDLE docs to omit " +"\"Control-z on Windows\"." +msgstr "" + +#: ../../../Misc/NEWS:10123 +msgid "" +"`Issue #17532 `__: Always include Options " +"menu for IDLE on OS X. Patch by Guilherme Simões." +msgstr "" + +#: ../../../Misc/NEWS:10126 +msgid "" +"`Issue #17585 `__: Fixed IDLE regression. Now " +"closes when using exit() or quit()." +msgstr "" + +#: ../../../Misc/NEWS:10128 +msgid "" +"`Issue #17657 `__: Show full Tk version in " +"IDLE's about dialog. Patch by Todd Rovito." +msgstr "" + +#: ../../../Misc/NEWS:10131 +msgid "" +"`Issue #17613 `__: Prevent traceback when " +"removing syntax colorizer in IDLE." +msgstr "" + +#: ../../../Misc/NEWS:10133 +msgid "" +"`Issue #1207589 `__: Backwards-" +"compatibility patch for right-click menu in IDLE." +msgstr "" + +#: ../../../Misc/NEWS:10135 +msgid "" +"`Issue #16887 `__: IDLE now accepts Cancel in " +"tabify/untabify dialog box." +msgstr "" + +#: ../../../Misc/NEWS:10137 +msgid "" +"`Issue #17625 `__: In IDLE, close the replace " +"dialog after it is used." +msgstr "" + +#: ../../../Misc/NEWS:10139 +msgid "" +"`Issue #14254 `__: IDLE now handles readline " +"correctly across shell restarts." +msgstr "" + +#: ../../../Misc/NEWS:10141 +msgid "" +"`Issue #17614 `__: IDLE no longer raises " +"exception when quickly closing a file." +msgstr "" + +#: ../../../Misc/NEWS:10143 +msgid "" +"`Issue #6698 `__: IDLE now opens just an " +"editor window when configured to do so." +msgstr "" + +#: ../../../Misc/NEWS:10145 +msgid "" +"`Issue #8900 `__: Using keyboard shortcuts in " +"IDLE to open a file no longer raises an exception." +msgstr "" + +#: ../../../Misc/NEWS:10148 +msgid "" +"`Issue #6649 `__: Fixed missing exit status in " +"IDLE. Patch by Guilherme Polo." +msgstr "" + +#: ../../../Misc/NEWS:10150 +msgid "" +"`Issue #17114 `__: IDLE now uses non-strict " +"config parser." +msgstr "" + +#: ../../../Misc/NEWS:10152 +msgid "" +"`Issue #9290 `__: In IDLE the sys.std* streams " +"now implement io.TextIOBase interface and support all mandatory methods and " +"properties." +msgstr "" + +#: ../../../Misc/NEWS:10155 +msgid "" +"`Issue #5066 `__: Update IDLE docs. Patch by " +"Todd Rovito." +msgstr "" + +#: ../../../Misc/NEWS:10157 +msgid "" +"`Issue #16829 `__: IDLE printing no longer " +"fails if there are spaces or other special characters in the file path." +msgstr "" + +#: ../../../Misc/NEWS:10160 +msgid "" +"`Issue #16491 `__: IDLE now prints chained " +"exception tracebacks." +msgstr "" + +#: ../../../Misc/NEWS:10162 +msgid "" +"`Issue #16819 `__: IDLE method completion now " +"correctly works for bytes literals." +msgstr "" + +#: ../../../Misc/NEWS:10164 +msgid "" +"`Issue #16504 `__: IDLE now catches " +"SyntaxErrors raised by tokenizer. Patch by Roger Serwy." +msgstr "" + +#: ../../../Misc/NEWS:10167 +msgid "" +"`Issue #16511 `__: Use default IDLE width and " +"height if config param is not valid. Patch Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10170 +msgid "" +"`Issue #1207589 `__: Add Cut/Copy/Paste " +"items to IDLE right click Context Menu. Patch by Todd Rovito." +msgstr "" + +#: ../../../Misc/NEWS:10173 +msgid "" +"`Issue #16123 `__: IDLE - deprecate running " +"without a subprocess. Patch by Roger Serwy." +msgstr "" + +#: ../../../Misc/NEWS:10179 +msgid "" +"`Issue #1666318 `__: Add a test that shutil." +"copytree() retains directory permissions. Patch by Catherine Devlin." +msgstr "" + +#: ../../../Misc/NEWS:10182 +msgid "" +"`Issue #18273 `__: move the tests in Lib/test/" +"json_tests to Lib/test/test_json and make them discoverable by unittest. " +"Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10185 +msgid "Fix a fcntl test case on KFreeBSD, Debian #708653 (Petr Salinger)." +msgstr "" + +#: ../../../Misc/NEWS:10187 +msgid "" +"`Issue #18396 `__: Fix spurious test failure " +"in test_signal on Windows when faulthandler is enabled (Patch by Jeremy " +"Kloth)" +msgstr "" + +#: ../../../Misc/NEWS:10190 +msgid "" +"`Issue #17046 `__: Fix broken " +"test_executable_without_cwd in test_subprocess." +msgstr "" + +#: ../../../Misc/NEWS:10192 +msgid "" +"`Issue #15415 `__: Add new temp_dir() and " +"change_cwd() context managers to test.support, and refactor temp_cwd() to " +"use them. Patch by Chris Jerdonek." +msgstr "" + +#: ../../../Misc/NEWS:10195 +msgid "" +"`Issue #15494 `__: test.support is now a " +"package rather than a module (Initial patch by Indra Talip)" +msgstr "" + +#: ../../../Misc/NEWS:10198 +msgid "" +"`Issue #17944 `__: test_zipfile now " +"discoverable and uses subclassing to generate tests for different " +"compression types. Fixed a bug with skipping some tests due to use of " +"exhausted iterators." +msgstr "" + +#: ../../../Misc/NEWS:10202 +msgid "" +"`Issue #18266 `__: test_largefile now works " +"with unittest test discovery and supports running only selected tests. " +"Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10205 +msgid "" +"`Issue #17767 `__: test_locale now works with " +"unittest test discovery. Original patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10208 +msgid "" +"`Issue #18375 `__: Assume --randomize when --" +"randseed is used for running the testsuite." +msgstr "" + +#: ../../../Misc/NEWS:10211 +msgid "" +"`Issue #11185 `__: Fix test_wait4 under AIX. " +"Patch by Sébastien Sablé." +msgstr "" + +#: ../../../Misc/NEWS:10213 +msgid "" +"`Issue #18207 `__: Fix test_ssl for some " +"versions of OpenSSL that ignore seconds in ASN1_TIME fields." +msgstr "" + +#: ../../../Misc/NEWS:10216 +msgid "" +"`Issue #18094 `__: test_uuid no longer " +"reports skipped tests as passed." +msgstr "" + +#: ../../../Misc/NEWS:10218 +msgid "" +"`Issue #17992 `__: Add timeouts to asyncore " +"and asynchat tests so that they won't accidentally hang." +msgstr "" + +#: ../../../Misc/NEWS:10221 +msgid "" +"`Issue #17833 `__: Fix test_gdb failures seen " +"on machines where debug symbols for glibc are available (seen on PPC64 " +"Linux)." +msgstr "" + +#: ../../../Misc/NEWS:10224 +msgid "" +"`Issue #7855 `__: Add tests for ctypes/winreg " +"for issues found in IronPython. Initial patch by Dino Viehland." +msgstr "" + +#: ../../../Misc/NEWS:10227 +msgid "" +"`Issue #11078 `__: test___all__ now checks " +"for duplicates in __all__. Initial patch by R. David Murray." +msgstr "" + +#: ../../../Misc/NEWS:10230 +msgid "" +"`Issue #17712 `__: Fix test_gdb failures on " +"Ubuntu 13.04." +msgstr "" + +#: ../../../Misc/NEWS:10232 +msgid "" +"`Issue #17835 `__: Fix test_io when the " +"default OS pipe buffer size is larger than one million bytes." +msgstr "" + +#: ../../../Misc/NEWS:10235 +msgid "" +"`Issue #17065 `__: Use process-unique key for " +"winreg tests to avoid failures if test is run multiple times in parallel " +"(eg: on a buildbot host)." +msgstr "" + +#: ../../../Misc/NEWS:10238 +msgid "" +"`Issue #12820 `__: add tests for the xml.dom." +"minicompat module. Patch by John Chandler and Phil Connell." +msgstr "" + +#: ../../../Misc/NEWS:10241 +msgid "" +"`Issue #17691 `__: test_univnewlines now " +"works with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10244 +msgid "" +"`Issue #17790 `__: test_set now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10247 +msgid "" +"`Issue #17789 `__: test_random now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10250 +msgid "" +"`Issue #17779 `__: test_osx_env now works " +"with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10253 +msgid "" +"`Issue #17766 `__: test_iterlen now works " +"with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10256 +msgid "" +"`Issue #17690 `__: test_time now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10259 +msgid "" +"`Issue #17692 `__: test_sqlite now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10262 +msgid "" +"`Issue #11995 `__: test_pydoc doesn't import " +"all sys.path modules anymore." +msgstr "" + +#: ../../../Misc/NEWS:10264 +msgid "" +"`Issue #17448 `__: test_sax now skips if " +"there are no xml parsers available instead of raising an ImportError." +msgstr "" + +#: ../../../Misc/NEWS:10267 +msgid "" +"`Issue #11420 `__: make test suite pass with -" +"B/DONTWRITEBYTECODE set. Initial patch by Thomas Wouters." +msgstr "" + +#: ../../../Misc/NEWS:10270 +msgid "" +"`Issue #10652 `__: make tcl/tk tests run " +"after __all__ test, patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10273 +msgid "" +"`Issue #11963 `__: remove human verification " +"from test_parser and test_subprocess." +msgstr "" + +#: ../../../Misc/NEWS:10275 +msgid "" +"`Issue #11732 `__: add a new " +"suppress_crash_popup() context manager to test.support that disables crash " +"popups on Windows and use it in test_faulthandler and test_capi." +msgstr "" + +#: ../../../Misc/NEWS:10279 +msgid "" +"`Issue #13898 `__: test_ssl no longer prints " +"a spurious stack trace on Ubuntu." +msgstr "" + +#: ../../../Misc/NEWS:10281 +msgid "" +"`Issue #17283 `__: Share code between " +"`__main__.py` and `regrtest.py` in `Lib/test`." +msgstr "" + +#: ../../../Misc/NEWS:10284 +msgid "" +"`Issue #17249 `__: convert a test in " +"test_capi to use unittest and reap threads." +msgstr "" + +#: ../../../Misc/NEWS:10286 +msgid "" +"`Issue #17107 `__: Test client-side SNI " +"support in urllib.request thanks to the new server-side SNI support in the " +"ssl module. Initial patch by Daniel Black." +msgstr "" + +#: ../../../Misc/NEWS:10290 +msgid "" +"`Issue #17041 `__: Fix testing when Python is " +"configured with the --without-doc-strings." +msgstr "" + +#: ../../../Misc/NEWS:10293 +msgid "" +"`Issue #16923 `__: Fix ResourceWarnings in " +"test_ssl." +msgstr "" + +#: ../../../Misc/NEWS:10295 +msgid "" +"`Issue #15539 `__: Added regression tests for " +"Tools/scripts/pindent.py." +msgstr "" + +#: ../../../Misc/NEWS:10297 +msgid "" +"`Issue #17479 `__: test_io now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10300 +msgid "" +"`Issue #17066 `__: test_robotparser now works " +"with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10303 +msgid "" +"`Issue #17334 `__: test_index now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10306 +msgid "" +"`Issue #17333 `__: test_imaplib now works " +"with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10309 +msgid "" +"`Issue #17082 `__: test_dbm* now work with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10312 +msgid "" +"`Issue #17079 `__: test_ctypes now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10315 +msgid "" +"`Issue #17304 `__: test_hash now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10318 +msgid "" +"`Issue #17303 `__: test_future* now work with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10321 +msgid "" +"`Issue #17163 `__: test_file now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10324 +msgid "" +"`Issue #16925 `__: test_configparser now " +"works with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10327 +msgid "" +"`Issue #16918 `__: test_codecs now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10330 +msgid "" +"`Issue #16919 `__: test_crypt now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10333 +msgid "" +"`Issue #16910 `__: test_bytes, test_unicode, " +"and test_userstring now work with unittest test discovery. Patch by Zachary " +"Ware." +msgstr "" + +#: ../../../Misc/NEWS:10336 +msgid "" +"`Issue #16905 `__: test_warnings now works " +"with unittest test discovery. Initial patch by Berker Peksag." +msgstr "" + +#: ../../../Misc/NEWS:10339 +msgid "" +"`Issue #16898 `__: test_bufio now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10342 +msgid "" +"`Issue #16888 `__: test_array now works with " +"unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10345 +msgid "" +"`Issue #16896 `__: test_asyncore now works " +"with unittest test discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10348 +msgid "" +"`Issue #16897 `__: test_bisect now works with " +"unittest test discovery. Initial patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10351 +msgid "" +"`Issue #16852 `__: test_genericpath, " +"test_posixpath, test_ntpath, and test_macpath now work with unittest test " +"discovery. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10354 +msgid "" +"`Issue #16748 `__: test_heapq now works with " +"unittest test discovery." +msgstr "" + +#: ../../../Misc/NEWS:10356 +msgid "" +"`Issue #10646 `__: Tests rearranged for os." +"samefile/samestat to check for not just symlinks but also hard links." +msgstr "" + +#: ../../../Misc/NEWS:10359 +msgid "" +"`Issue #15302 `__: Switch regrtest from using " +"getopt to using argparse." +msgstr "" + +#: ../../../Misc/NEWS:10361 +msgid "" +"`Issue #15324 `__: Fix regrtest parsing of --" +"fromfile, --match, and --randomize options." +msgstr "" + +#: ../../../Misc/NEWS:10364 +msgid "" +"`Issue #16702 `__: test_urllib2_localnet " +"tests now correctly ignores proxies for localhost tests." +msgstr "" + +#: ../../../Misc/NEWS:10367 +msgid "" +"`Issue #16664 `__: Add regression tests for " +"glob's behaviour concerning entries starting with a \".\". Patch by " +"Sebastian Kreft." +msgstr "" + +#: ../../../Misc/NEWS:10370 +msgid "" +"`Issue #13390 `__: The ``-R`` option to " +"regrtest now also checks for memory allocation leaks, using :func:`sys." +"getallocatedblocks()`." +msgstr "" + +#: ../../../Misc/NEWS:10373 +msgid "" +"`Issue #16559 `__: Add more tests for the " +"json module, including some from the official test suite at json.org. Patch " +"by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10376 +msgid "" +"`Issue #16661 `__: Fix the `os." +"getgrouplist()` test by not assuming that it gives the same output as :" +"command:`id -G`." +msgstr "" + +#: ../../../Misc/NEWS:10379 +msgid "" +"`Issue #16115 `__: Add some tests for the " +"executable argument to subprocess.Popen(). Initial patch by Kushal Das." +msgstr "" + +#: ../../../Misc/NEWS:10382 +msgid "" +"`Issue #16126 `__: PyErr_Format format " +"mismatch in _testcapimodule.c. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10385 +msgid "" +"`Issue #15304 `__: Fix warning message when " +"`os.chdir()` fails inside `test.support.temp_cwd()`. Patch by Chris " +"Jerdonek." +msgstr "" + +#: ../../../Misc/NEWS:10388 +msgid "" +"`Issue #15802 `__: Fix test logic in " +"`TestMaildir.test_create_tmp()`. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10391 +msgid "" +"`Issue #15557 `__: Added a test suite for the " +"webbrowser module, thanks to Anton Barkovsky." +msgstr "" + +#: ../../../Misc/NEWS:10394 +msgid "" +"`Issue #16698 `__: Skip posix test_getgroups " +"when built with OS X deployment target prior to 10.6." +msgstr "" + +#: ../../../Misc/NEWS:10400 +msgid "" +"`Issue #16067 `__: Add description into MSI " +"file to replace installer's temporary name." +msgstr "" + +#: ../../../Misc/NEWS:10403 +msgid "" +"`Issue #18257 `__: Fix readlink usage in " +"python-config. Install the python version again on Darwin." +msgstr "" + +#: ../../../Misc/NEWS:10406 +msgid "" +"`Issue #18481 `__: Add C coverage reporting " +"with gcov and lcov. A new make target \"coverage-report\" creates an " +"instrumented Python build, runs unit tests and creates a HTML. The report " +"can be updated with \"make coverage-lcov\"." +msgstr "" + +#: ../../../Misc/NEWS:10410 +msgid "" +"`Issue #17845 `__: Clarified the message " +"printed when some module are not built." +msgstr "" + +#: ../../../Misc/NEWS:10412 +msgid "" +"`Issue #18256 `__: Compilation fix for recent " +"AIX releases. Patch by David Edelsohn." +msgstr "" + +#: ../../../Misc/NEWS:10415 +msgid "" +"`Issue #17547 `__: In configure, explicitly " +"pass -Wformat for the benefit for GCC 4.8." +msgstr "" + +#: ../../../Misc/NEWS:10418 +msgid "" +"`Issue #15172 `__: Document NASM 2.10+ as " +"requirement for building OpenSSL 1.0.1 on Windows." +msgstr "" + +#: ../../../Misc/NEWS:10421 +msgid "" +"`Issue #17591 `__: Use lowercase filenames " +"when including Windows header files. Patch by Roumen Petrov." +msgstr "" + +#: ../../../Misc/NEWS:10424 +msgid "" +"`Issue #17550 `__: Fix the --enable-profiling " +"configure switch." +msgstr "" + +#: ../../../Misc/NEWS:10426 +msgid "" +"`Issue #17425 `__: Build with openssl 1.0.1d " +"on Windows." +msgstr "" + +#: ../../../Misc/NEWS:10428 +msgid "" +"`Issue #16754 `__: Fix the incorrect shared " +"library extension on linux. Introduce two makefile macros SHLIB_SUFFIX and " +"EXT_SUFFIX. SO now has the value of SHLIB_SUFFIX again (as in 2.x and 3.1). " +"The SO macro is removed in 3.4." +msgstr "" + +#: ../../../Misc/NEWS:10432 +msgid "" +"`Issue #5033 `__: Fix building of the sqlite3 " +"extension module when the SQLite library version has \"beta\" in it. Patch " +"by Andreas Pelme." +msgstr "" + +#: ../../../Misc/NEWS:10435 +msgid "" +"`Issue #17228 `__: Fix building without " +"pymalloc." +msgstr "" + +#: ../../../Misc/NEWS:10437 +msgid "" +"`Issue #3718 `__: Use AC_ARG_VAR to set " +"MACHDEP in configure.ac." +msgstr "" + +#: ../../../Misc/NEWS:10439 +msgid "" +"`Issue #16235 `__: Implement python-config as " +"a shell script." +msgstr "" + +#: ../../../Misc/NEWS:10441 +msgid "" +"`Issue #16769 `__: Remove outdated Visual " +"Studio projects." +msgstr "" + +#: ../../../Misc/NEWS:10443 +msgid "" +"`Issue #17031 `__: Fix running regen in cross " +"builds." +msgstr "" + +#: ../../../Misc/NEWS:10445 +msgid "" +"`Issue #3754 `__: fix typo in pthread " +"AC_CACHE_VAL." +msgstr "" + +#: ../../../Misc/NEWS:10447 +msgid "" +"`Issue #15484 `__: Fix _PYTHON_PROJECT_BASE " +"for srcdir != builddir builds; use _PYTHON_PROJECT_BASE in distutils/" +"sysconfig.py." +msgstr "" + +#: ../../../Misc/NEWS:10450 +msgid "Drop support for Windows 2000 (changeset e52df05b496a)." +msgstr "" + +#: ../../../Misc/NEWS:10452 +msgid "" +"`Issue #17029 `__: Let h2py search the " +"multiarch system include directory." +msgstr "" + +#: ../../../Misc/NEWS:10454 +msgid "" +"`Issue #16953 `__: Fix socket module " +"compilation on platforms with HAVE_BROKEN_POLL. Patch by Jeffrey Armstrong." +msgstr "" + +#: ../../../Misc/NEWS:10457 +msgid "" +"`Issue #16320 `__: Remove redundant Makefile " +"dependencies for strings and bytes." +msgstr "" + +#: ../../../Misc/NEWS:10459 +msgid "" +"Cross compiling needs host and build settings. configure no longer creates a " +"broken PYTHON_FOR_BUILD variable when --build is missing." +msgstr "" + +#: ../../../Misc/NEWS:10462 +msgid "" +"Fix cross compiling issue in setup.py, ensure that lib_dirs and inc_dirs are " +"defined in cross compiling mode, too." +msgstr "" + +#: ../../../Misc/NEWS:10465 +msgid "" +"`Issue #16836 `__: Enable IPv6 support even " +"if IPv6 is disabled on the build host." +msgstr "" + +#: ../../../Misc/NEWS:10467 +msgid "" +"`Issue #16593 `__: Have BSD 'make -s' do the " +"right thing, thanks to Daniel Shahaf" +msgstr "" + +#: ../../../Misc/NEWS:10469 +msgid "" +"`Issue #16262 `__: fix out-of-src-tree " +"builds, if mercurial is not installed." +msgstr "" + +#: ../../../Misc/NEWS:10471 +msgid "" +"`Issue #15298 `__: ensure _sysconfigdata is " +"generated in build directory, not source directory." +msgstr "" + +#: ../../../Misc/NEWS:10474 +msgid "" +"`Issue #15833 `__: Fix a regression in 3.3 " +"that resulted in exceptions being raised if importlib failed to write byte-" +"compiled files. This affected attempts to build Python out-of-tree from a " +"read-only source directory." +msgstr "" + +#: ../../../Misc/NEWS:10478 +msgid "" +"`Issue #15923 `__: Fix a mistake in ``asdl_c." +"py`` that resulted in a TypeError after 2801bf875a24 (see #15801)." +msgstr "" + +#: ../../../Misc/NEWS:10481 +msgid "`Issue #16135 `__: Remove OS/2 support." +msgstr "" + +#: ../../../Misc/NEWS:10483 +msgid "" +"`Issue #15819 `__: Make sure we can build " +"Python out-of-tree from a read-only source directory. (Somewhat related to " +"`issue #9860 `__.)" +msgstr "" + +#: ../../../Misc/NEWS:10486 +msgid "" +"`Issue #15587 `__: Enable Tk high-resolution " +"text rendering on Macs with Retina displays. Applies to Tkinter apps, such " +"as IDLE, on OS X framework builds linked with Cocoa Tk 8.5." +msgstr "" + +#: ../../../Misc/NEWS:10490 +msgid "" +"`Issue #17161 `__: make install now also " +"installs a python3 man page." +msgstr "" + +#: ../../../Misc/NEWS:10495 +msgid "" +"`Issue #18351 `__: Fix various issues in a " +"function in importlib provided to help " +"PyImport_ExecCodeModuleWithPathnames() (and thus by extension " +"PyImport_ExecCodeModule() and PyImport_ExecCodeModuleEx())." +msgstr "" + +#: ../../../Misc/NEWS:10499 +msgid "" +"`Issue #15767 `__: Added " +"PyErr_SetImportErrorSubclass()." +msgstr "" + +#: ../../../Misc/NEWS:10501 +msgid "PyErr_SetImportError() now sets TypeError when its msg argument is set." +msgstr "" + +#: ../../../Misc/NEWS:10503 +msgid "" +"`Issue #9369 `__: The types of `char*` " +"arguments of PyObject_CallFunction() and PyObject_CallMethod() now changed " +"to `const char*`. Based on patches by Jörg Müller and Lars Buitinck." +msgstr "" + +#: ../../../Misc/NEWS:10507 +msgid "" +"`Issue #17206 `__: Py_CLEAR(), Py_DECREF(), " +"Py_XINCREF() and Py_XDECREF() now expand their arguments once instead of " +"multiple times. Patch written by Illia Polosukhin." +msgstr "" + +#: ../../../Misc/NEWS:10511 +msgid "" +"`Issue #17522 `__: Add the PyGILState_Check() " +"API." +msgstr "" + +#: ../../../Misc/NEWS:10513 +msgid "" +"`Issue #17327 `__: Add PyDict_SetDefault." +msgstr "" + +#: ../../../Misc/NEWS:10515 +msgid "" +"`Issue #16881 `__: Fix Py_ARRAY_LENGTH macro " +"for GCC < 3.1." +msgstr "" + +#: ../../../Misc/NEWS:10517 +msgid "" +"`Issue #16505 `__: Remove unused " +"Py_TPFLAGS_INT_SUBCLASS." +msgstr "" + +#: ../../../Misc/NEWS:10519 +msgid "" +"`Issue #16086 `__: PyTypeObject.tp_flags and " +"PyType_Spec.flags are now unsigned (unsigned long and unsigned int) to avoid " +"an undefined behaviour with Py_TPFLAGS_TYPE_SUBCLASS ((1 << 31). " +"PyType_GetFlags() result type is now unsigned too (unsigned long, instead of " +"long)." +msgstr "" + +#: ../../../Misc/NEWS:10524 +msgid "" +"`Issue #16166 `__: Add PY_LITTLE_ENDIAN and " +"PY_BIG_ENDIAN macros and unified endianness detection and handling." +msgstr "" + +#: ../../../Misc/NEWS:10530 +msgid "" +"`Issue #23006 `__: Improve the documentation " +"and indexing of dict.__missing__. Add an entry in the language datamodel " +"special methods section. Revise and index its discussion in the stdtypes " +"mapping/dict section." +msgstr "" + +#: ../../../Misc/NEWS:10534 +msgid "" +"`Issue #17701 `__: Improving strftime " +"documentation." +msgstr "" + +#: ../../../Misc/NEWS:10536 +msgid "" +"`Issue #18440 `__: Clarify that `hash()` can " +"truncate the value returned from an object's custom `__hash__()` method." +msgstr "" + +#: ../../../Misc/NEWS:10539 +msgid "" +"`Issue #17844 `__: Add links to encoders and " +"decoders for bytes-to-bytes codecs." +msgstr "" + +#: ../../../Misc/NEWS:10541 +msgid "" +"`Issue #14097 `__: improve the \"introduction" +"\" page of the tutorial." +msgstr "" + +#: ../../../Misc/NEWS:10543 +msgid "" +"`Issue #17977 `__: The documentation for the " +"cadefault argument's default value in urllib.request.urlopen() is fixed to " +"match the code." +msgstr "" + +#: ../../../Misc/NEWS:10546 +msgid "" +"`Issue #6696 `__: add documentation for the " +"Profile objects, and improve profile/cProfile docs. Patch by Tom Pinckney." +msgstr "" + +#: ../../../Misc/NEWS:10549 +msgid "" +"`Issue #15940 `__: Specify effect of locale " +"on time functions." +msgstr "" + +#: ../../../Misc/NEWS:10551 +msgid "" +"`Issue #17538 `__: Document XML vulnerabilties" +msgstr "" + +#: ../../../Misc/NEWS:10553 +msgid "" +"`Issue #16642 `__: sched.scheduler timefunc " +"initial default is time.monotonic. Patch by Ramchandra Apte" +msgstr "" + +#: ../../../Misc/NEWS:10556 +msgid "" +"`Issue #17047 `__: remove doubled words in " +"docs and docstrings reported by Serhiy Storchaka and Matthew Barnett." +msgstr "" + +#: ../../../Misc/NEWS:10559 +msgid "" +"`Issue #15465 `__: Document the versioning " +"macros in the C API docs rather than the standard library docs. Patch by " +"Kushal Das." +msgstr "" + +#: ../../../Misc/NEWS:10562 +msgid "" +"`Issue #16406 `__: Combine the pages for " +"uploading and registering to PyPI." +msgstr "" + +#: ../../../Misc/NEWS:10564 +msgid "" +"`Issue #16403 `__: Document how distutils " +"uses the maintainer field in PKG-INFO. Patch by Jyrki Pulliainen." +msgstr "" + +#: ../../../Misc/NEWS:10567 +msgid "" +"`Issue #16695 `__: Document how glob handles " +"filenames starting with a dot. Initial patch by Jyrki Pulliainen." +msgstr "" + +#: ../../../Misc/NEWS:10570 +msgid "" +"`Issue #8890 `__: Stop advertising an insecure " +"practice by replacing uses of the /tmp directory with better alternatives in " +"the documentation. Patch by Geoff Wilson." +msgstr "" + +#: ../../../Misc/NEWS:10574 +msgid "" +"`Issue #17203 `__: add long option names to " +"unittest discovery docs." +msgstr "" + +#: ../../../Misc/NEWS:10576 +msgid "" +"`Issue #13094 `__: add \"Why do lambdas " +"defined in a loop with different values all return the same result?\" " +"programming FAQ." +msgstr "" + +#: ../../../Misc/NEWS:10579 +msgid "" +"`Issue #14901 `__: Update portions of the " +"Windows FAQ. Patch by Ashish Nitin Patil." +msgstr "" + +#: ../../../Misc/NEWS:10582 +msgid "" +"`Issue #16267 `__: Better document the 3.3+ " +"approach to combining @abstractmethod with @staticmethod, @classmethod and " +"@property" +msgstr "" + +#: ../../../Misc/NEWS:10585 +msgid "" +"`Issue #15209 `__: Clarify exception chaining " +"description in exceptions module documentation" +msgstr "" + +#: ../../../Misc/NEWS:10588 +msgid "" +"`Issue #15990 `__: Improve argument/parameter " +"documentation." +msgstr "" + +#: ../../../Misc/NEWS:10590 +msgid "" +"`Issue #16209 `__: Move the documentation for " +"the str built-in function to a new str class entry in the \"Text Sequence " +"Type\" section." +msgstr "" + +#: ../../../Misc/NEWS:10593 +msgid "" +"`Issue #13538 `__: Improve str() and object." +"__str__() documentation." +msgstr "" + +#: ../../../Misc/NEWS:10595 +msgid "" +"`Issue #16489 `__: Make it clearer that " +"importlib.find_loader() needs parent packages to be explicitly imported." +msgstr "" + +#: ../../../Misc/NEWS:10598 +msgid "" +"`Issue #16400 `__: Update the description of " +"which versions of a given package PyPI displays." +msgstr "" + +#: ../../../Misc/NEWS:10601 +msgid "" +"`Issue #15677 `__: Document that zlib and " +"gzip accept a compression level of 0 to mean 'no compression'. Patch by " +"Brian Brazil." +msgstr "" + +#: ../../../Misc/NEWS:10604 +msgid "" +"`Issue #16197 `__: Update winreg docstrings " +"and documentation to match code. Patch by Zachary Ware." +msgstr "" + +#: ../../../Misc/NEWS:10607 +msgid "" +"`Issue #8040 `__: added a version switcher to " +"the documentation. Patch by Yury Selivanov." +msgstr "" + +#: ../../../Misc/NEWS:10610 +msgid "" +"`Issue #16241 `__: Document -X faulthandler " +"command line option. Patch by Marek Šuppa." +msgstr "" + +#: ../../../Misc/NEWS:10613 +msgid "" +"Additional comments and some style changes in the concurrent.futures URL " +"retrieval example" +msgstr "" + +#: ../../../Misc/NEWS:10616 +msgid "" +"`Issue #16115 `__: Improve subprocess.Popen() " +"documentation around args, shell, and executable arguments." +msgstr "" + +#: ../../../Misc/NEWS:10619 +msgid "" +"`Issue #13498 `__: Clarify docs of os." +"makedirs()'s exist_ok argument. Done with great native-speaker help from R. " +"David Murray." +msgstr "" + +#: ../../../Misc/NEWS:10622 +msgid "" +"`Issue #15533 `__: Clarify docs and add tests " +"for `subprocess.Popen()`'s cwd argument." +msgstr "" + +#: ../../../Misc/NEWS:10625 +msgid "" +"`Issue #15979 `__: Improve timeit " +"documentation." +msgstr "" + +#: ../../../Misc/NEWS:10627 +msgid "" +"`Issue #16036 `__: Improve documentation of " +"built-in `int()`'s signature and arguments." +msgstr "" + +#: ../../../Misc/NEWS:10630 +msgid "" +"`Issue #15935 `__: Clarification of " +"`argparse` docs, re: add_argument() type and default arguments. Patch " +"contributed by Chris Jerdonek." +msgstr "" + +#: ../../../Misc/NEWS:10633 +msgid "" +"`Issue #11964 `__: Document a change in v3.2 " +"to the behavior of the indent parameter of json encoding operations." +msgstr "" + +#: ../../../Misc/NEWS:10636 +msgid "" +"`Issue #15116 `__: Remove references to " +"appscript as it is no longer being supported." +msgstr "" + +#: ../../../Misc/NEWS:10642 +msgid "" +"`Issue #18817 `__: Fix a resource warning in " +"Lib/aifc.py demo. Patch by Vajrasky Kok." +msgstr "" + +#: ../../../Misc/NEWS:10645 +msgid "" +"`Issue #18439 `__: Make patchcheck work on " +"Windows for ACKS, NEWS." +msgstr "" + +#: ../../../Misc/NEWS:10647 +msgid "" +"`Issue #18448 `__: Fix a typo in Tools/demo/" +"eiffel.py." +msgstr "" + +#: ../../../Misc/NEWS:10649 +msgid "" +"`Issue #18457 `__: Fixed saving of formulas " +"and complex numbers in Tools/demo/ss1.py." +msgstr "" + +#: ../../../Misc/NEWS:10652 +msgid "" +"`Issue #18449 `__: Make Tools/demo/ss1.py " +"work again on Python 3. Patch by Févry Thibault." +msgstr "" + +#: ../../../Misc/NEWS:10655 +msgid "" +"`Issue #12990 `__: The \"Python Launcher\" on " +"OSX could not launch python scripts that have paths that include wide " +"characters." +msgstr "" + +#: ../../../Misc/NEWS:10658 +msgid "" +"`Issue #15239 `__: Make mkstringprep.py work " +"again on Python 3." +msgstr "" + +#: ../../../Misc/NEWS:10660 +msgid "" +"`Issue #17028 `__: Allowed Python arguments " +"to be supplied to the Windows launcher." +msgstr "" + +#: ../../../Misc/NEWS:10663 +msgid "" +"`Issue #17156 `__: pygettext.py now detects " +"the encoding of source files and correctly writes and escapes non-ascii " +"characters." +msgstr "" + +#: ../../../Misc/NEWS:10666 +msgid "" +"`Issue #15539 `__: Fix a number of bugs in " +"Tools/scripts/pindent.py. Now pindent.py works with a \"with\" statement. " +"pindent.py no longer produces improper indentation. pindent.py now works " +"with continued lines broken after \"class\" or \"def\" keywords and with " +"continuations at the start of line." +msgstr "" + +#: ../../../Misc/NEWS:10671 +msgid "" +"`Issue #11797 `__: Add a 2to3 fixer that maps " +"reload() to imp.reload()." +msgstr "" + +#: ../../../Misc/NEWS:10673 +msgid "" +"`Issue #10966 `__: Remove the concept of " +"unexpected skipped tests." +msgstr "" + +#: ../../../Misc/NEWS:10675 +msgid "" +"`Issue #9893 `__: Removed the Misc/Vim " +"directory." +msgstr "" + +#: ../../../Misc/NEWS:10677 +msgid "Removed the Misc/TextMate directory." +msgstr "" + +#: ../../../Misc/NEWS:10679 +msgid "" +"`Issue #16245 `__: Add the Tools/scripts/" +"parse_html5_entities.py script to parse the list of HTML5 entities and " +"update the html.entities.html5 dictionary." +msgstr "" + +#: ../../../Misc/NEWS:10682 +msgid "" +"`Issue #15378 `__: Fix Tools/unicode/" +"comparecodecs.py. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10684 +msgid "" +"`Issue #16549 `__: Make json.tool work again " +"on Python 3 and add tests. Initial patch by Berker Peksag and Serhiy " +"Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10687 +msgid "" +"`Issue #13301 `__: use ast.literal_eval() " +"instead of eval() in Tools/i18n/msgfmt.py. Patch by Serhiy Storchaka." +msgstr "" + +#: ../../../Misc/NEWS:10693 +msgid "" +"`Issue #18569 `__: The installer now adds .py " +"to the PATHEXT variable when extensions are registered. Patch by Paul Moore." +msgstr "" + +#: ../../../Misc/NEWS:10696 +msgid "**(For information about older versions, consult the HISTORY file.)**" +msgstr "" + +#: ../Doc/whatsnew/index.rst:5 +msgid "What's New in Python" +msgstr "" + +#: ../Doc/whatsnew/index.rst:7 +msgid "" +"The \"What's New in Python\" series of essays takes tours through the most " +"important changes between major Python versions. They are a \"must read\" " +"for anyone wishing to stay up-to-date after a new release." +msgstr "" + +#: ../Doc/whatsnew/index.rst:30 +msgid "" +"The \"Changelog\" is a HTML version of the file :source:`Misc/NEWS` which " +"contains *all* nontrivial changes to Python for the current version." +msgstr ""